TABLE OF CONTENTS:
Table of Contents |
---|
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.
...
5G Operational
Optimization
...
5G FCAPS
Discovery
5G Operational
R6 5G-SPECIFIC USE CASES (Frankfurt Release)
...
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 | PCI OOF (SON) in R5 El Alto, PCI OOF (SON) in R6 Frankfurt | ||||
Configuration & Persistency Service | Run-time configuration data persistency (Run Time Config DB/MariaDB). | 5G CONFIGURATION & 5G NETWORK TOPOLOGY | 5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB) | 5G CM (FCAPS) | 5G 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. Improvements will be made and carry - overs from R4 DublinThe 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 Bulk PM Management in Frankfurt/R6 Frankfurt | ||||
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 PoC in R6 Frankfurt (Obsolete) | ||||
MOBILITY STANDARDS | LICENSING MANAGEMENT | Licensing Management with ONAP and a PNF. The topics for how to create licenses, manage licenses and handling terms between a vendor and service providers. This will evolve beyond 5G but may start as a 5G U/C. | LICENSING MANAGEMENT | RAN 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) | MOBILITY STANDARDS HARMONIZATION WITH ONAPORAN- ONAP Alignment Use Case | |
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 |
...
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.
...
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.
...
TITLE | Requirement / Platform Enhancement vs E2E Use Case | 5G Specific | |||||
5G SERVICE MODELING | Requirement / Platform Enhancement | 5G Specific | PNF PRE-ONBOARDING & ONBOARDING Use Case | General | CONFIGURATION WITH NETCONF | Requirement / Platform EnhancementGeneral | |
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 SLICINGPNF PLUG AND PLAY | 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 | S/W UPGRADERequirement / Platform | Enhancement Enhancement | General | ||||
PNF / CONFIGURATION WITH NETCONF | Requirement / Platform Enhancement | 5G Specific | 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 - Controller LCM API Evolution
Use Case Realization Call: April 17, 2019
Use Case Realization Call: April 24, 2019 - Arch POB/OB Flow
Use Case Realization Call: May 1, 2019 - A&AI Graph Graph Visualizer
Use Case Realization Call: May 8, 2019 - A&AI Model Browser Demo
Use Case Realization Call: May 15, 2019 - A&AI Sparky (Run-time browser) Demo
Use Case Realization Call: May 22, 2019 - Edge Automation Overview
Use Case Realization Call: May 29, 2019 - Model, U/C, Arch WoW Discussion
Use Case Realization Call: June 5, 2019 - U/C discussion
Use Case Realization Call: June 19, 2019 - IoT Creation
Use Case Realization Call: July 10, 2019 - PNF S/W Upgrade
Use Case Realization Call: July 17, 2019 - U/C discussions
Use Case Realization Call: July 24, 2019 - OOF PCI Demo (Shankar)
Use Case Realization Call: July 31, 2019 - U/C discussions
Use Case Realization Call: August 7, 2019 - 5G NRM (YaoGuang Wang)
Use Case Realization Call: August 14, 2019 - ORAN/3GPP & ONAP Alignment (Marge, Vimal)
5G Use Case Meeting notes for August 8, 2019 - 5G U/C Network Slicing R6 Proposal (Shankar/Swami)
5G Use Case Meeting notes for August 15, 2019 - 5G U/C Meeting
SUPPORTING DOCUMENTS:
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 |
|
MEETING RECORDINGS
Use Case Overview & Summary for R6 |
|
|
View file | ||||
---|---|---|---|---|
|
View file | ||||
---|---|---|---|---|
|
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 |