Versions Compared

Key

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

...

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.

...

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.

...

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


State Transitions

rApp States

...

Create rApp Instance

  1. API user request to create rApp Instance with the resource details from rApp package
  2. API user get the rApp instance creation response

Deploy rApp Instance

  1. API user request to deploy rApp instance
  2. rApp Manager fetches the rApp package from file system and fetches the 
    resources mentioned in the rApp instance.
  3. rApp Manager request ACM-R with the necessary details from rApp package to 
    Instantiate ACM instance
  4. rApp Manager gets instantiate ACM instance response
  5. rApp Manager request ACM-R to deploy ACM instance
  6. ACM-R deploys the A1PMS instance if it is configured in the ACM instance
  7. ACM-R gets the A1PMS deployment status
  8. ACM-R deploys the Kserve instance if it is configured in the ACM instance
  9. ACM-R gets the Kserve deployment status
  10. ACM-R deploys the Kubernetes instance if it is configured in the ACM instance
  11. ACM-R gets the Kubernetes deployment status
  12. ACM-R deploys the DME instance if it is configured in the ACM instance
  13. ACM-R gets the DME deployment status
  14. rApp Manager gets ACM deployment status
  15. rApp Manager request SME to create the entities in rApp instance
  16. SME creates the entities provided by rApp Manager
  17. rApp manager get the response of SME entities creation
  18. API user provided with the status of rApp instance deployment. rApp Manager combines 
    the status of ACM deployment and SME deployment to provide the rApp instance status.

Undeploy rApp Instance

  1. API user request to undeploy rApp instance
  2. rApp Manager fetches the rApp and rApp instance details
  3. rApp Manager request ACM-R to undeploy the ACM instance
  4. ACM-R undeploy the A1PMS instance if it is already deployed
  5. ACM-R gets the A1PMS undeploy status
  6. ACM-R undeploy the Kserve instance if it is already deployed
  7. ACM-R gets the Kserve undeploy status
  8. ACM-R undeploy the Kubernetes instance if it is already deployed
  9. ACM-R gets the Kubernetes undeploy status
  10. ACM-R undeploy the DME instance if it is already deployed
  11. ACM-R gets the DME undeploy status
  12. rApp Manager get ACM undeploy status
  13. rApp Manager request ACM-R to delete the ACM instance
  14. rApp Manager get response of ACM instance deletion
  15. rApp Manager request SME to delete SME entities
  16. SME deletes the entities created as part of rApp
  17. rApp Manager get the response of SME entities deletion
  18. API user get the status of undeploy rApp instance

Delete rApp Instance

  1. API user request rApp Manager to delete rApp Instance
  2. API user gets delete rApp instance response



Sample rApp package structure

...

This is a prototype and subject to change

...

The sample rApp package structure shown below and the location of relevant files for each integration is provided.

...