5G Use Cases in R6 Frankfurt
- Benjamin Cheung
- Takeshi Usui
- Timo Perala
TABLE OF CONTENTS:
R6 5G-SPECIFIC USE CASES (Frankfurt Release)
Release 6 will be a "normal" release but with an extended M1 from June to Aug 29.
TITLE | DESCRIPTION | CATEGORY | WIKI |
5G SERVICE MODELING & CREATION | Defining and Modeling a 5G Service for Design Time and use by other 5G Use Cases. Defining the Platform Data & Information model and PNF Resource for a 5G RAN. | 5G FCAPS Discovery 5G Operational | |
OOF SON ENHANCEMENTS | Optimization and OOF SON development. Dublin Carry-over items. OOF (SON). SDN-R Network. Policy Control Loop Coordination. | 5G Operational Optimization | |
Configuration & Persistency Service | Run-time configuration data persistency (Run Time Config DB/MariaDB). | 5G CM (FCAPS) | |
NETWORK TOPOLOGY MANAGEMENT | 5G Network Topology Management. 5G Network representation and management. | 5G Operation | |
PERFORMANCE MEASUREMENTS | Performance Measurements Use Cases (including Bulk PM, RT PM and PM Dictionary) | Data Collection 5G FCAPS | |
BULK PM (PERFORMANCE MEASUREMENTS) | Performance Measurements 5G RAN Bulk Upload. The main proposed addition is PM control capability. Partially 5G Specific, and Partially "Generic". Can be evolved for use with generic PNFs (beyond 5G) | Data Collection 5G FCAPS | |
5G PM DICTIONARY (PERFORMANCE MEASUREMENTS) | Support for handling & support for PM Dictionary & PM Schema (from standards). Eventually other PNFs will support faults, but right now 3GPP specific formatting is used in the PM artifact. Can be evolved for use with generic PNFs (beyond 5G) | PNF Support Data Collection 5G FCAPS | |
5G FM META DATA (FAULT MANAGEMENT) | Support for handling FM Meta Data. Eventually other PNFs will support faults but right now 3GPP specific formatting is used in the FM. Can be evolved for use with generic PNFs (beyond 5G) | PNF Support Data Collection 5G FCAPS | |
NETWORK SLICING END-TO-END NETWORK SLICING MANAGEMENT | Advanced 5G functionality, for Network Slicing development and early steps in long-lead development. (CMCC) @LIN MENG @Lingli Deng Advanced 5G functionality, Management of Network Slicing development | 5G Operational Optimization | |
MOBILITY STANDARDS STANDARDS HARMONIZATION WITH ONAP | There are many standards ORAN and 3GPP harmonization with ONAP. O1, A1 definitions. Encoding protocol to use. ORAN repository (proprietary to ORAN) | ||
5G NRM (Network Resource Model) CONFIGURATION | Configuration Management (CM Notify/ Update) using RESTful (HTTPS) Interface. | 5G CM (FCAPS) | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt |
5G U/C COMMITMENTS BY PROJECT:
The following table indicates commitment by project. The impacts have been accepted and are supported by the PTL of each ONAP Platform component and corresponding Jira Tickets are in place. There are three states:
N/A = A "N/A" means that there is no interaction, no dependency, and no work for that Use Case for that component.
? = A "?" means that there is not final commitment from the PTL for that project, and no Jira ticket exists yet.
YES = This means that (1) PTL INFORMED & COMMITTED - has agreed to support the changes needed for that Use Case, (2) DEVELOPMENT SUPPORT - there is development (company) support (3) JIRA TICKETS - and a Jira ticket exists. Please see the corresponding WIKI page for that Use Case to find out more details on impact, PTL support and Jira Ticket(s).
NOTE: The CTRLR column includes CC-SDK, CDS, SDN-C, APP-C. Including what used to be SDN-R has been under the SDN-C "umbrella".
Use Case | SDC | VID | Portal | SO | AAI ESR | CTRLR | DCAE | OOF | Policy | CLAMP | DMaaP | AAF | VNF SDK | REQTS | Model S/C | OOM | VIM | Pomba | CIA | CLI | Consul | VF-C |
Bulk PM | N/A | N/A | N/A | YES | N/A | N/A | YES | N/A | YES | YES | N/A | YES | N/A |