The following page describes the major use cases and key requirements targeted to the Honolulu Release
HISTORY OF USE CASE PORTAL PAGES
| RELEASE | WIKI PAGE |
|---|---|
| R6 Frankfurt Release Use Case Portal | Release 6 (Frankfurt) proposed use cases and functional requirements |
| R7 Guilin Release Use Case Portal | Guilin (R7) - Use Cases (and Requirements in Use Cases) |
| Use Case Realization R6 Portal Page | Release 6 (Frankfurt) proposed use cases and functional requirements |
| Use Case Realization R6 Portal Page | Use Case Realization Meeting Register MoM |
5G USE CASES & REQUIREMENTS IN R8 (HONOLULU)
5G Use Case Team (Monthly) Meeting Notes & recordings: 5G Use Case Team Meetings
| USE CASE / REQUIREMENT | DESCRIPTION | WIKI LINK |
|---|---|---|
| 5G Service Modeling | Defining and modeling a 5G Service (in Design Time) and the associated Modeling (Platform information & data model). This is driven by 3GPP TS28.540 and TS28.541, the 5G NRM. Development of a concept of a Registry Service used in CPS | R8 5G Service Modeling |
| 5G SON Use Case | Optimization and SON functions for 5G RAN which provide for self-optimization, self-healing and self-configuration | R8 5G SON use case |
| ONAP/3GPP & O-RAN Alignment: Standard Defined VES | The capability to receive, validate and process standards defined notifications encapsulated in VES events in ONAP. VES 7.2 | R8 ONAP/3GPP & O-RAN Alignment: Standard Defined VES |
| End to End Network Slicing | 5G Network Slicing defines slices to be used in 5G RAN systems. Network Slicing is a long-lead multi-release development. | R8 E2E Network Slicing use case |
Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support | A lightweight and high-cohesion Nature Language Processing (NLP) function is proposed to add in the UUI project, in order to translate the network operation engineers’ text/voice intents to the suitable slicing parameters quickly and decrease the manual configurations. | Smart Operator Intent Translation in UUI based on IBN - R8 5G Slicing Support |
| Intent Based Networking | Support for Vertical Industry. Intent framework is a system that helps to implement and operate networks that can improve network availability and agility. It takes a high-level business goal (intent) as input, converts it to the necessary network configurations and applies the network changes via network automation and/or network orchestration. Continuously monitoring the status of the network under control, the system validates in real time that the intent is being met, and can take corrective actions when desired intent is not met. | Support for Vertical Industry |
| Intent Based Networking | Support for Intent Framework and Intent Modeling. (add description) | Support for Intent Framework and Intent Modeling |
| ONAP/3GPP & O-RAN Alignment: A1 Adapter and Policy Management Extension | A1 Adapter and Policy Management Extension. This requirement enhances the A1 interface capabilities provided in Rel 6 as part of 5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management. O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. Planned enhancements for Rel 8 include support of new A1 interface version in alignment to O-RAN alliance and common logging/audit. | |
MAJOR USE CASES & REQUIREMENTS IN R8 (HONOLULU)
| USE CASE / REQUIREMENT | DESCRIPTION | WIKI LINK |
|---|---|---|
| PNF Plug and Play | The PNF Plug and Play Use Case allows a PNF to register with ONAP using a pnfRegistration VES Event. This is expected to be used for installation & commissioning a network that is to be managed by ONAP. When this event is received, the PNF Registration Handler (PRH) processes this event to complete the registration by updating the corresponding A&AI entry for the expectant PNF. The PRH was developed specifically for this use case. Once registered, ONAP can interoperate with the PNF and perform LCM or FCAPS (OA&M) operations in addition to other actions. This Use Case was originally started in in R2 Beijing and functionality has been continually improved since then. | R8 PNF Plug and Play Use Case |
| Certificate Management Protocol v2 | The Certificate Management Protocol (CMP) is an Internet protocol used for obtaining X.509 digital certificates in a public key infrastructure (PKI). It is described in RFC 4210 and is one of two protocols so far to use the Certificate Request Message Format (CRMF), described in RFC 4211, with the other protocol being Certificate Management over CMS (CMC), described in RFC 5273. An obsolete version of CMP is described in RFC 2510, the respective CRMF version in RFC 2511. CMP messages are encoded in ASN.1, using the DER method and usually transported over HTTP. CMP (Certificate Management Protocol) Server & Client (completed in R6) | R8 Certificate Management Protocol |
| Configuration Persistence Service | The Configuration Persistence Service is a Common Data Layer Service providing database functionality to persist network element run-time information. CPS will perform key DB operations such as syncing data with xNFs. CPS enables OSS configuration, optimization and E2E LCM operations. It will be a new Platform Component in R8. Team meeting page: Configuration Persistence Service Meeting Notes & Recordings | Configuration Persistence Service (CPS) for R8 Honolulu |
| ETSI Alignment | ETSI Alignment Use Case | R8 ETSI Alignment |
xNF Software Upgrade | PNF Software Upgrade enhancement In Rel 6 (REQ-84) and Rel 7 (REQ-324), PNF sw upgrade requirement in ONAP has progressed covering both with/without schema updates. A schema update in relation to a xNF software upgrades is a routine for network upgrade to support new xNF features, improve efficiency or increase xNF capacity on the field, and to eliminate bugs. This use case provides to ONAP an advantage in orchestrating and managing the Life Cycle of a Network Services in-line with business and service objectives. In Rel 8, the feature will be enhanced with PNF sw version management during sw upgrade procedure. | |
| Bulk PM/ PM Data Control | Bulk PM / PM Data Control Improvements PM data collection control provides 5G network operators with a dynamic and more efficient way to configure performance measurement collection on a selected subset of PNFs/VNFs in the network and complements the existing PM data collection and processing capabilities in ONAP/DCAE. An initial version has been delivered in Rel 6 (REQ-129) then enhanced in Rel 7 (REQ-381). Planned enhancements for Rel 8 intend to improve the (PMSH) subscription management about subscription update. | |
SUPPORTING DOCUMENTATION & PRESENTATION
| Description | File or Wiki Link |
|---|---|
OVERVIEWS, DEMOS & SLIDES
The following are Links to Overviews, Demos and Summary Slides for each of the major use cases:
USEFUL LINKS
The following table has useful links:
