TABLE OF CONTENTS:
Table of Contents |
---|
...
R6 5G-SPECIFIC USE CASES
...
PNF Package delivery, Pre-onboarding and PNF Onboarding via SDC. In R5 El Alto focus will be on enhancements to the base functionality from R4 Dublin.
...
PNF Support
Discovery
...
PNF Support
Communications
5G FCAPS
...
PNF Support
(Carry Over)
Discovery
...
PNF Software Upgrade to update the software on a PNF, Dublin Carry-over items.
Goal 1: PNF S/W Upgrade Netconf support (PNF Generic)
Goal 2: 3GPP southbound based interfaces (controller to xNF or External Controller). An example API using 3GPP interfaces. (5G Specific)
...
PNF Support
5G FCAPS
...
(Frankfurt Release)
Release 6 will be a "normal" release but with an extended M1 from June to Aug 29.
...
5G SPECIFIC USE CASES:
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 | 5G RAN SERVICE MODELING & DEFINITION in |
R6 Frankfurt |
OOF SON ENHANCEMENTS | Optimization and |
OOF SON |
development. Dublin Carry-over items. OOF (SON). SDN-R Network. Policy Control Loop Coordination. | 5G Operational Optimization |
OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | |||
Configuration & Persistency Service | Run-time configuration data persistency (Run Time Config DB/MariaDB). | 5G CM (FCAPS) | CONFIGURATION & PERSISTENCY SERVICE |
NETWORK TOPOLOGY MANAGEMENT | 5G Network Topology Management. 5G Network representation and management. | 5G Operation | NETWORK TOPOLOGY MANAGEMENT (R7 GuiLin) |
PERFORMANCE MEASUREMENTS | Performance Measurements Use Cases (including Bulk PM, RT PM and PM Dictionary) | Data Collection 5G FCAPS | PERFORMANCE MEASUREMENTS USE CASES: Bulk, RT, Dictionary |
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 |
Bulk PM |
in |
Frankfurt/R6 |
|
5G FM META DATA &
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 | FM META DATA & PM DICTIONARY in |
R6 Frankfurt | |||
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 | FM META DATA & PM DICTIONARY in R6 Frankfurt |
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 | NETWORK SLICING |
5G USE CASE ASSESSMENT:
PoC in R6 Frankfurt (Obsolete) | |||
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 | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
FM PM Dict | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
OOF PCI | N/A | N/A | N/A | N/A | N/A | YES | YES | YES | YES | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
Slicing | YES | N/A | N/A | YES | YES | YES | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
ORAN Harmonize | N/A | N/A | N/A | N/A | N/A | YES | YES | N/A | N/A | N/A | YES | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
Licensing Managmt | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
5G NRM | N/A | N/A | N/A | YES | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | YES | N/A | N/A | N/A | N/A | N/A | N/A | |
RunTime DB | N/A | N/A | N/A | N/A | YES | YES | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
5G Service Modeling | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | N/A | YES | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
REQ = VNF Requirements Project. The VNF-RQTS project applies to both VNFs and PNFs. A "YES" here means that there are new requirements for the vendors.
Model S/C = Modelling Subcommittee. This U/C impacts the ONAP Platform Information and/or Data Model.
Ctrlr = This includes all of the controllers in ONAP including SDN-C, SDN-R, APP-C and VF-C
Stretch Goal (N/A) but if extra resources are available some changes may be made.
Note (1): x
Note (2): x
5G USE CASE ASSESSMENT:
The following table was to assess whether use cases are related to 5G (are 5G specific) or whether they are general PNF use cases.
The General PNF use cases have been moved to their own wiki: General PNF Support Use Cases
TITLE | Requirement / Platform Enhancement vs E2E Use Case | 5G Specific |
5G SERVICE MODELING | Requirement / Platform Enhancement | 5G Specific |
Requirement / Platform Enhancement
Requirement / Platform Enhancement
BULK PM | Requirement / Platform Enhancement * Could be evolved eventually to be PNF & domain generic. | 5G Specific * |
5G FM META DATA & 5G PM DICTIONARY | Requirement / Platform Enhancement * Could be evolved eventually to be PNF & domain generic. | 5G Specific * |
OOF SON ENHANCEMENTS | Requirement / Platform Enhancement | 5G Specific |
NETWORK SLICING |
E2E Use Case | 5G Specific | |
MOBILE SERVICE CHAINING | Requirement / Platform Enhancement | General |
PNF |
USE CASES: ( General PNF Support Use Cases ) | ||
PNF / PNF PRE-ONBOARDING & ONBOARDING Use Case | Requirement / Platform |
Enhancement | General |
PNF / CONFIGURATION WITH NETCONF | Requirement / Platform Enhancement |
General |
PNF / PNF PLUG AND PLAY |
E2E Use Case |
5G Specific
General | ||
PNF / PNF S/W UPGRADE | Requirement / Platform Enhancement | General |
...
5G Use Case MEETINGS:
Links to the Use Case Realization Calls:
Use Case Realization Call: April 10, 2019
5G Meetings & recordings:
SUPPORTING DOCUMENTS:
Document | File |
---|
Use Case Template | Use Case Tracking Template | ||||||
Use Case Analysis (from U/C realization Calls) / Sept 17 2019 |
| ||||||
Use Case Overview & Summary for R6 |
|
|
|
|
R5 El Alto Release
EUAG has decided that R5 El Alto will be a "maintenance/technical debt" release.
https://wiki.lfnetworking.org/display/LN/EUAG+2019-04-09+meeting+minutes
The El Alto release will be shortened (3-month cycle) and focused on internal (tech) debt and defect backlogs. And every 5th ONAP release will be a maintenance release.
PTLs had taken short cuts to meet deadlines, working but want to make the platform more robust. PTL driven code fixes and code hardening.
S/W Enhancements (e.g. GUI enhancements) would be pushed to R6. Feature enhancements would be pushed to R6
R5 will be focused on Refactoring, JIRA backlog reduction, vulnerability issues, Test Coverage, Test Automation (CI/CD pipeline), Deployment procedure, Documentation.
R5 - Security Scans, scan code reports sent to PTL for major things to fix. Vulnerabilities have been built. Vulnerability management process. Security gates checklist.
SUMMARY: There will be no new Software development for new functionality in R5; but there will be Jira tickets worked on (PCI/SON); and modeling work for 5G RAN.
TITLE | DESCRIPTION | CATEGORY | WIKI |
---|---|---|---|
PCI/SON ENHANCEMENTS | Optimization and PCI (SON) development. Dublin Carry-over items will be worked in R5. There are two Jira tickets open for SDN-C. | 5G Operational Optimization | OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt |
5G SERVICE MODELING | 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 |