Versions Compared

Version Old Version 34 New Version 35
Changes made by

Aravindhan Ayyanathan

Aravindhan Ayyanathan

Saved on

Key

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

Table of Contents


Introduction

...

Integrations

The rApp Manager is integrated with the below following 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 has the ability to support unlimited 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 is integrated 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 is integrated 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.

...

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



  1. COMMISSIONED
    rApp willget becreated 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 once 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

...

Tip

Ignore the below variables if the entire environment is being setup by the following installation scripts below


Variable NameDescriptionDefault Value
A1PMS_HOST
Address of the A1PMS. 
It will be accessed from A1PMS participant.
http://policymanagementservice.nonrtric:9080
CHART_REPO_HOST
Address of the chart repository. 
It will be used by Kubernetes participant.
http://IP_ADDRESS:8879/charts
IP_ADDRESS: IP of the host in which 
the installation scripts are running.

...

Code Block
languagebash
>./install-kserve.sh

To installs the NONRTRIC components.

...