Versions Compared

Version Old Version 4 New Version 5
Changes made by

Aravindhan Ayyanathan

Aravindhan Ayyanathan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

The rApp Manager integrated with the below components to support lifecycle managing the rApp.

ACM

Automation Composition Management (ACM) is a framework that supports Life Cycle Management of Automation Compositions. It supports deployment, monitoring, update and removal of Automation Compositions en-bloc, allowing users to manage their features, services, and capabilities as single logical units. More details about ACM can be found here.

ACM-R supports any number of participants and all the participants can be configured through the configuration in the rApp package.

List of participants used by rApp manager sample rApp.

  • A1PMS Participant - It interacts with A1PMS of NONRTRIC. It is capable of lifecycle managing A1PMS service.
  • Kserve Participant - It interacts with Kserve. It is capable of lifecycle managing Kserve inference service.
  • Kubernetes Participant - It interacts with Helm/Kubernetes. It is capable of lifecycle managing Helm charts.
  • DME Participant -  It interacts with DME(ICS) of NONRTRIC. It is capable of lifecycle managing DME entities.

ACM composition and instance details can be provided as part of rApp package and the package structure can be found here.

DME

The DME(Information Coordination Service (ICS)) is a generic service that maintains data subscriptions. Its main purpose is to decouple data consumers and data producers in a multi vendor environment. A data consumer does not need to know anything about the producers of the data. More details about DME can be found here.

It integrates with rApp manager to enable the rApp produce/consume specific type of data(Information Type in DME terms).

Information type, Data producer/consumer information can be provided as part of rApp package and the package structure can be found here.

SME

The SME(CAPIF) stands for Common API framework and it was developed by 3GPP to enable a unified Northbound API framework across 3GPP network functions, and to ensure that there is a single and harmonized approach for API development. More details about DME can be found here.

It integrates with rApp manager to enable the rApp expose/access/discover endpoints.

Service exposure/access related configurations can be provided as part of rApp package and the package structure can be found here.

...



  1. COMMISSIONED
    rApp will be in this state right after creation. and 
    once the DEPRIMING is completed
  2. PRIMING
    This is a transition state. rApp will be in this 
    state once the PRIMING requested for rApp
  3. PRIMED
    rApp will be in this state afteronce the PRIMING is 
    completed. 
    In this state rApp instances can be 
    created
  4. DEPRIMING
    This is a transition state. rApp will be 
    in this state once the DEPRIMING requested for rApp

...

The rApp Instance lifecycle contains 4 states. The state and transitions are as follows,



  1. UNDEPLOYED
    rApp instance gets created in this state and 
    once the rApp Instance undeploy is completed
  2. DEPLOYING
    This is the transition state. rApp instance will
    be in this state once DEPLOY is requested
  3. DEPLOYED
    rApp instance will be in this state once the 
    rapp instance deployment is completed.
  4. UNDEPLOYING
    This is a transition state. rApp instance will
    be in this state once UNDEPLOY requested for 
    rApp instance


Flows

rApp flow

Create rApp

:

  1. API user creates rApp by sending rApp package
  2. rApp Manager validates the rApp
  3. rApp Manager stores the rApp in the file system if the rApp is valid
  4. API user provided with the status of rApp creation.
  5. API user request to Prime the rApp
  6. rApp Manager fetches the ACM composition from rApp package and 
    creates the ACM composition in ACM-R
  7. rApp Manager gets the ACM composition creation status from ACM-R
  8. rApp Manager request ACM-R to prime the ACM composition 
  9. rApp Manager gets the ACM composition priming status from ACM-R
  10. rApp Manager checks with DME for the unknown information type from rApp package
  11. rApp Manager get the information type availability from DME
  12. API user provided with the status of rApp priming

Delete rApp

:

  1. API user request to Deprime rApp
  2. rApp Manager request ACM-R to deprime the ACM composition 
  3. rApp Manager get the status of ACM composition depriming.
  4. rApp Manager requests ACM-R to delete the ACM composition 
  5. rApp Manager gets the status of ACM composition deletion
  6. API user provided with the deprime rApp status.
  7. API user request to delete the rApp
  8. rApp Manager validates that the rApp is in COMMISSIONED state and 
    there is no rApp Instances are available.
  9. API User provided with delete rApp status

...