Introduction
The Application Deployment use case is being defined to demonstrate how to deploy an application that is in a DEPLOYABLE state as either an xAPP or an rAPP.
Background and Goal of the Use Case
Applications represent an extension of a RAN Intelligent Controller. This can be either as an rAPP for the Non-RT RIC, or as an xAPP for the Near-RT RIC. Applications in these two different environments have different platform mechanisms however, they share a common behavior allowing an abstraction layer to provide the capability for the application to be developed such that it can be deployed to either environment from the same package. In this Use Case the SMO Network Function Orchestrator (NFO) will be simulated to draw out requirements for an SMO implementation. The flow developed as part of this Use Case should be able to be integrated to any SMO environment. Stereotypes are used to indicate which project and capability is being developed or used to provide the described role of the actor in the use case. The following actors are used to demonstrate the flow:
...
In addition, the use case documentation provides a mapping of the use case requirements to the EPICs defined for O-RAN Software Community (O-RAN SC) Cherry Release. The list below enumerates the EPICs to be added to the Cherry Release. Note that these Epics are of lower priority than RAN functionality required to support a UE to connect to the RANthe Application LCM Use Case as it is a prerequisite for this use case:
- <<RICAPP>> Provide a Helloworld or extend an existing xAPP to support the deployment and registration steps as either an rAPP or an xAPP
- <<RICPLT>> Provide a RIC API that can be used for RICAPP xAPP deployment scenario
- <<NRTRIC>> Provide a R1 API that can be used for RICAPP rAPP deployment scenario
- <<INT OTF>> Provide Test Strategy to simulate the orchestration of the deployment
- <<INF>> Provide the HELM and Kubernetes APIs to support the Application Deployment
- <<SMO>> Need the MVC for Instance Config and Virtual Inventory