R8 5G Service Modeling
Use Case Overview & Description
(description of U/C)
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |
Architecture S/C info | Information on the Architecture sub-committee presentation | |
Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |
Requirements Jira (REQ) Ticket | Link to the REQ Jira ticket for this use case | |
Key Use Case Leads & Contacts | USE CASE LEAD: @Benjamin Cheung USE KEY CONTACTS: | |
Meetings Register & Recordings | Link to Use Case Team meetings. | |
R8 Release update Page |
BUSINESS DRIVER
This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.
Executive Summary - This requirement introduces platform information model enhancements to document new ISOMII experimental classes from 3GPP TS28.541, the 5G Network Resource Model (NRM). The purpose of this use case is to introduce the necessary changes into the ONAP platform architecture so that it can be prepared to accept and work with a real live 5G RAN DU (for a gNB). Presently, this may mean introducing a generic application model defined in CDS. This model would then integrate the 3GPP 5G NRM so that ONAP components and micro-services could access the information in a 3GPP format without needing to overhaul the Platform Information Model.
Business Impact - The requirement, is a critical because it will serve to lay the ground-work for actually "turning on" a real 5G DU (PNF) that might be installed by a Vendor.
Business Markets - This project applies to any domain (wireless, transport, optical, and wireline) that ONAP may manage..
Funding/Financial Impacts - Without the groundwork laid down for information model management of a 5G Service, operators will not be able to "turn on" a real live 5G network using "live" PNF resources. No Network. No Business. High OPEX impact.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
Development Status
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @William Reehil | NO IMPACT | |
AAF | @Jonathan Gathman | NO IMPACT | |
APPC | @Takamune Cho | NO IMPACT | |
CLAMP | @Gervais-Martial Ngueko | NO IMPACT | |
CC-SDK | @Dan Timoney | NO IMPACT | |
DCAE | @Vijay Kumar | NO IMPACT | |
DMaaP | @Mandar Sawant | NO IMPACT | |
External API | @Adrian OSullivan | NO IMPACT | |
HOLMES | @Guangrong Fu | NO IMPACT | |
MODELING | @Hui Deng | Model Presentations and discussions. The 5G Service Modeling use case: (1) Developed a solution for vendors to deliver 3GPP TS28.540/541 5G NRM driven xNF models to ONAP. (2) The modeling solution has now been integrated into the CPS architecture and has driven the ONAP platform information model evolution. (3) In R8, the architecture was defined for a registry service to expose on-boarded NRM & vendor data to coordinate across use cases. (4) A new resource app Model was introduced to allow for flexible vendor model management in R8. (5) Discussions for onboarding NRM artifacts was explored in R8. | This use case is focused on making sure that ONAP will be able to work with a live 5G gNB base station. Currently, use cases are using simulators. The objective is to try to get everything in place for a live gNB launch. In R8, the Configuration Persistence Service (CPS) PoC has been approved to become a new platform component. Much of the ground work in this project has now been incorporated into CPS. |
Multi-VIM / Cloud | @Bin Yang | NO IMPACT | |
OOF | @krishna moorthy | NO IMPACT | |
OOM | @Sylvain Desbureaux | NO IMPACT | |
POLICY | @James Hahn | NO IMPACT | |
PORTAL | @Sunder Tattavarada | NO IMPACT | |
SDN-C | @Dan Timoney | NO IMPACT | |
SDC | @ChrisC | NO IMPACT | |
SO | @Seshu Kumar Mudiganti | NO IMPACT | |
VID | @Ikram Ikramullah | NO IMPACT | |
VF-C | @Yuanhong Deng | NO IMPACT | |
VNFRQTS | @Steven wright | NO IMPACT | |
VNF-SDK | @victor gao | NO IMPACT | |
CDS | @Yuriy Malakov | NO IMPACT |