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 | R7 Use Case Realization Meetings 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. | |
| OOF SON Use Case | Optimization and SON functions for 5G RAN which provide for self-optimization, self-healing and self-configuration | |
| ONAP/3GPP & O-RAN Alignment: Standard Defined VES | The capability to receive, validate and process standards defined notifications encapsulated in VES events in ONAP. | |
| 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. | |
| xNF Software Upgrade | Improvements on xNF Software Upgrade in association to schema updates | |
| Bulk PM/ PM Data Control | Bulk PM / PM Data Control Improvements | |
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) | |
| Configuration Persistence Service | The Configuration Persistence Service is a Common Data Layer Service providing database functionality to persist network element run time information. It will be a new Platform Component in R8 | |
| ETSI Alignment | ETSI Alignment Use Case | |
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:
