The page is intended to summarize all the requirements for Frankfurt Release.
These requirements will be prioritized by the TSC to realistically fit within the Frankfurt Release Timeline.
The Release Scope should be finalized during the M1 Release Planning milestone at the xxx.
TSC Prioritization (Ranking)
- RANK #0 – Special GO - fully covered by involved companies
- RANK #1 – GO “Must Have”
- RANK #2 - GO “Continuity of previous releases”
- RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched”
- RANK #4 – NO GO – Mostly new requirements/features/projects
Requirements Milestones Summary
See also Documenting Release Requirements in JIRA
| Epic Link | Fix For Versions (all) | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Frankfurt Release | Guilin Release | Honolulu Release | Istanbul Release | Jakarta Release | Kohn Release | London Release | Montreal Release | New Delhi Release | Istanbul Maintenance Release 1 | Unscheduled | T: | |
| 5G / OOF SON Enhancement | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| 5G / ORAN & 3GPP Standards Harmonization | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| 5G OOF SON use case requirements for Guilin release | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| 5G Service Modeling in R8 | 0 | 0 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 17 |
| 5G SON use case enhancements for Istanbul release | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
| 5G SON use case enhancements for Jakarta release | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 0 | 0 | 0 | 14 |
| 5G SON use case enhancements for Kohn release | 0 | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 0 | 0 | 14 |
| 5G SON use case enhancements for London release | 0 | 0 | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 2 | 16 |
| 5G SON Usecase R8 | 0 | 0 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 18 |
| A1 Adapter Extension & A1 Policy Management | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| A1 Policy Functions Extension - Istanbul | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
| A1 Policy Functions Extension - Jakarta | 0 | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
| A1 Policy Functions Extension - Kohn | 0 | 0 | 1 | 1 | 1 | 13 | 0 | 0 | 0 | 1 | 0 | 13 |
| A1 Policy Functions Extension - London | 0 | 0 | 0 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 13 |
| Add VSP Compliance and Verification Check feature Phase 2 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| Akraino Distributed Analytics use case | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| All Control Loop Policy Models should be TOSCA Compliant | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| APPC Ansible automation with VNF-C LCM support | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| Architecture - modelling alignment | 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 |
| ASD onboarding package IM / DM | 0 | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
| Bulk PM / PM Data Control Extension | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
| Bulk PM / PM Data Control Improvements | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 |
| Bulk PM / PM Data Control Improvements | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
| Bulk PM / PM Data Control Improvements | 0 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
| CCVPN-E-LINE Service over OTN NNI | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
| Total Unique Issues: | 196 | 22 | 248 | 184 | 189 | 107 | 187 | 1 | 1 | 1 | 84 | 1216 |
Use Cases
Release 6 (Frankfurt) proposed use cases and functional requirements
M1 Scorecard:
- Green: Use Case will be fully implemented and tested
- Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
- Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.
Architecture:
- Pink - NO GO
- Purple - GO
- Black - Considered OK not requireing architecture review
| Use Case | JIRA link (REQ) One issue per requirement. | Owner(s) | Projects or functional requirements impacted for this release | Priority | M1 Scorecard | TSC M1 Approval | M3 Scorecard | M3 TSC Approval | M4 Scorecard | TSC M4 Approval | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size | Project's Impact: Test Only (TO), Code (C) | Committed (C)/ Partially Committed (P) or not (N) per impacted project | If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Integration Lead | Company Engagement | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Third Party Operational Domain Manager | REQ-17 - Getting issue details... STATUS | SDC | Third-party Operational Domain Manager | S | SDC (C) SO (TO) AAI (TO) | Changes being done in local setup. | Will commit after review discussion with SDC PTL | Telstra | Complete company commitment for delivery of Frankfurt Scope for this use case | ||||||||||
| Service Resolver Features | REQ-13 - Getting issue details... STATUS | rene.robert@orange.com | SDC, SO, Policy | 4 | Service Resolver | SDC (C), SO (C), AAI (TO) | No SO decision | Orange | |||||||||||
| CMPv2 CA Plugin for AAF | REQ-140 - Getting issue details... STATUS | AAF Integration | XL - | AAF (C) Integration (C) | AAF: (C) Integration:(C) | AT&T Ericsson Nokia | Note: Nokia and Ericsson volunteered to work this. As PTL, I approved the path forward (create Client, build plugin, etc) but was unable to create actual REQ. Please consider this working item until them. (update : REQ-140 - Getting issue details... STATUS created, at the moment we do not expect multiple release impacts but it has to be further checked) ALSO... This MAY be a multi-release effort, which will not affect normal Operations in anyway, if CMPv2 isn't completed within Frankfurt. | ||||||||||||
CCVPN: E-LINE Service over OTN NNI | REQ-141 - Getting issue details... STATUS | LIN MENG | A&AI, SDN-C, OOF, U-UI, SO | XL (Multiple releases) | TO: SO; C: U-UI, A&AI, OOF, SDN-C | U-UI committed by ChinaMobile; A&AI committed by Huawei; OOF committed by Huawei; SDN-C committed by Huawei | China Mobile, Huawei | ||||||||||||
| Distributed Analytics use case on K8S regions | REQ-195 - Getting issue details... STATUS | Multi-Cloud | 3 | Depends on development progress of Multi-Cloud K8S work. | XL (Multiple releases) | TO | C | Intel, Aarna, TM |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Requirements
M1 Scorecard:
- Green: The requirement will be fully implemented and tested
- Yellow: The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
- Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Architecture:
- Pink - NO GO
- Purple - GO
- Black - Considered OK not requireing architecture review
| Requirement | JIRA link (REQ) One issue per requirement. | Owner | Project Impacted | Priority | M1 Scorecard | TSC M1 Approval | M3 Scorecard | M3 TSC Approval | M4 Scorecard | TSC M4 Approval | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL)  | Project's Impact: Test Only (TO), Code (C), Documentation Only (DO) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Integration Lead | Company Engagement | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Self Serve Control Loops | REQ-9 - Getting issue details... STATUS | CLAMP DCAE POLICY | Self Serve Control Loops v2 | CLAMP | XL | CLAMP - C DCAE - C POLICY - C | CLAMP - C DCAE - C POLICY - C | AT&T | |||||||||||
All Control Loop Policy Models should be TOSCA Compliant Operational, Guard Policies | REQ-21 - Getting issue details... STATUS | CLAMP POLICY | TOSCA Compliant Policy Types | SDC | M | CLAMP - C POLICY - C | CLAMP - C POLICY - C | AT&T, Ericsson | |||||||||||
| Policy Update Notifications | REQ-25 - Getting issue details... STATUS | DCAE POLICY | Policy Update Notifications | S | DCAE - C POLICY - C | DCAE - C POLICY - C | AT&T | ||||||||||||
| CLAMP Deployment of Policies to PDP Groups | REQ-29 - Getting issue details... STATUS | CLAMP POLICY | CLAMP Deployment of Policies to PDP Groups | M | CLAMP - C POLICY- C | CLAMP - C POLICY - C | AT&T | ||||||||||||
| Integration of CDS as Actor in Control Loops | REQ-33 - Getting issue details... STATUS | CLAMP POLICY CDS | CDS actor support in Policy | REQ-21 - Getting issue details... STATUS | L | CLAMP - C POLICY - C CDS - C | CLAMP - C POLICY - C CDS - C | AT&T, Bell Canada, Ericsson | |||||||||||
| Control Loop Tutorial Documentation | REQ-150 - Getting issue details... STATUS | DOC Integration | REQ-150 - Getting issue details... STATUS | CLAMP, DCAE, POLICY | M | Documentation - DO Integration - TO | DOC - C POLICY - C Need support from DCAE, CLAMP | Morgan Richomme | Bell Canada, AT&T, Orange | ||||||||||
| Component Upgrades to new Policy Lifecycle API | REQ-162 - Getting issue details... STATUS | SO SDNC OOF POLICY | M | SO - C SDNC - C OOF - C POLICY - C | POLICY - C OOF - C Need commitments from SDNC and SO | AT&T, Intel | |||||||||||||
| Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling | REQ-60 - Getting issue details... STATUS | SDC SO OOF AAI Modeling | NETWORK SLICING in R6 Frankfurt | SDC | L | SDC-C AAI-C External API | CMCC Amdocs AT&T Wiprc Huawei | ||||||||||||
| 5G / OOF SON Enhancement | REQ-154 - Getting issue details... STATUS | DCAE Policy Controller OOF VNF-RQTS | POLICY - C | POLICY - C | Wipro AT&T | ||||||||||||||
5G / Run-time data persistency (RunTime DB / CM): VES Model relations, VES CM model (CM Notify). | REQ-133 - Getting issue details... STATUS | A&AI Controller (RunTime DB component) Modeling DCAE | 5G CONFIGURATION (RunTime DB) | L | |||||||||||||||
| Modeling: GeoLocation Model (and standards harmonization) | Modeling work only | Modeling | PNF PLUG and PLAY in R6 Frankfurt | AAI | M | N/A | N/A | N/A | Ericsson Nokia | ||||||||||
| PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF | REQ-84 - Getting issue details... STATUS | SDC VID SO CDS VNFRQTS Integration Modeling | PNF software upgrade in R6 Frankfurt | M | SDC: C SO: C CDS: C VID: C Integration: C VNFRQTS: DO | SDC: (C) SO: (C) CDS: (C) VID: (C) Integration: (C) | Ericsson Huawei | ||||||||||||
| PNF / Enable Schema Update once PNF software is updated | REQ-88 - Getting issue details... STATUS | Modeling SDC Integration VNFRQTS | PNF software upgrade in R6 Frankfurt | PNF Software Upgrade using direct Netconf/Yang interface with PNF | M | SDC: C Integration: C VNFRQTS: DO | SDC: C Integration: C | Ericsson | |||||||||||
| LCM API Evolution | REQ-92 - Getting issue details... STATUS | Development in R6 will be part of REQ-84 | https://wiki.onap.org/download/attachments/50202249/2019-07-02%20ONAP_R6_Controller_Evolution_LCM_APIs.pptx?api=v2 | N/A | Development in R6 will be part of REQ-84 | N/A | N/A | Ericsson | Main goals:
| ||||||||||
| PNF / Enhancement on PNF Software Upgrade with EM with Ansible | REQ-53 - Getting issue details... STATUS | SO SDNC Integration | PNF software upgrade in R6 Frankfurt | LCM API Evolution | M | SO: C SDNC: C Integration:C | Huawei | ||||||||||||
| PNF / PNF Software Upgrade with EM with Netconf | REQ-96 - Getting issue details... STATUS | yaoguang wang | SO CDS Integration | PNF software upgrade in R6 Frankfurt | PNF Software Upgrade using direct Netconf/Yang interface with PNF | M | SO: C CDS: C Integration:C | Huawei | |||||||||||
| Modeling: 5G / ORAN & 3GPP Standards Harmonization | REQ-38 - Getting issue details... STATUS Modeling Only for Frankfurt | Modeling Only | MOBILITY STANDARDS HARMONIZATION WITH ONAP | M | SDNC: C DCAE: C CDS: C | AT&T Nokia Ericsson | |||||||||||||
| 5G / License Management | REQ-118 - Getting issue details... STATUS | VNFREQ, after UCs agreed SDC(*) Modeling ( *) No code or test impact expected in R6 as an outcome of the proposed UC | LICENSING MANAGEMENT | SDC | M | No code or test impact expected in R6 | N/A | AT&T Nokia Ericsson Orange | |||||||||||
| 5G / Bulk PM / PM Control | REQ-129 - Getting issue details... STATUS | SO CLAMP Policy DCAE Integration | 5G Bulk PM in Frankfurt/R6 | XL | SO: C CLAMP: C Policy: C DCAE: C Integration: C | POLICY: C Integration: C DCAE: C | user-3784d | Ericsson | |||||||||||
| 5G / Bulk PM / Secure Communication between xNFs and ONAP | REQ-136 - Getting issue details... STATUS | Pawel Baniewski | DCAE Integration | 5G Bulk PM in Frankfurt/R6 | AAF (REQ-140) | S | Nokia | ||||||||||||
| 5G / PM dictionary | REQ-80 - Getting issue details... STATUS | SDC: GAB Config file DCAE: VES Event Reg Spec | FM META DATA & PM DICTIONARY in R6 Frankfurt | S | Update GAB Config File and VES spec doc | AT&T Ericsson Nokia | |||||||||||||
End to End Layer 1 Service Management. Modeling the Optical Service Note: No principle issues from architecture, just requesting validation of alignment with CCVPN | REQ-37 - Getting issue details... STATUS | SDC SO AAI Controller DCAE Modeling | 4 | Multi-domain Optical Network Services | L | AT&T Orange Fujitsu | |||||||||||||
| 5G / 5G NRM Network Resource Model (Configuration Mgmt) | REQ-49 - Getting issue details... STATUS | yaoguang wang | SDC SO CDS Modeling | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | L | Huawei | |||||||||||||
| 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service | Modeling Work Only | Modeling | |||||||||||||||||
| PNF / Plug and Play | REQ-134 - Getting issue details... STATUS | Benjamin Cheung | DCAE SO Modeling | PNF PLUG and PLAY in R6 Frankfurt | AAF (REQ-140) | ||||||||||||||
| PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | REQ-76 - Getting issue details... STATUS | SDNC Integration | Configuration with NETCONF in Frankfurt/R6 | AAF (REQ-140) | M | SDNC: C Integration: C | SDNC: (C) Integration: (C) | Ericsson | |||||||||||
| PNF / PNF pre-onboarding onboarding | REQ-135 - Getting issue details... STATUS | VNF-SDK Integration | PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt | S | VNFSDK: C Integration: TO | Nokia Ericsson | |||||||||||||
| Modeling: Runtime instance model based on A&AI reverse engineering | Modeling Work Only REQ-170 - Getting issue details... STATUS | Modeling only. No new implementation requirements | Reverse-engineering AAI data model to Papyrus information model | AAI | S | AAI: C (one bug fix remaining in UML generation tooling) | AT&T Ericsson Huawei Orange | ||||||||||||
| Modeling: documentation of policy and allotted resource model | Modeling Work Only | Kevin Scaggs | Modeling only. No new implementation requirements | Policy SDC | M | AT&T | |||||||||||||
| Scaling Extensions | REQ-42 - Getting issue details... STATUS | APPC CCSDK | Scaling Use Case (Frankfurt) | APPC CCSDK | S-M | APPC - C CCSDK - TO | APPC - C CCSDK - C | Marco Platania | AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra Orange | ||||||||||
| APPC Ansible automation with VNF-C LCM support / CHM | REQ-191 - Getting issue details... STATUS | APPC Integration | Change Management Frankfurt Extensions | APPC Integration | S | APPC: C Integration: C | APPC and Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | ||||||||||
| vFW Traffic Distribution with Software Upgrade / CHM | REQ-187 - Getting issue details... STATUS | Integration | Change Management Frankfurt Extensions | Integration | XS | Integration: C | Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | ||||||||||
| Portal Security Enhancements | REQ-64 - Getting issue details... STATUS | Manoop Talasila | PORTAL | MUSIC | L | Policy: C VID: C SDC: C | Portal partially committed by AT&T, IBM | Partially committed by Samsung (to support OJSI tickets) | Dominik Mizyn (for OJSI tickets) | AT&T Samsung IBM | |||||||||
| Portal Technology Stack Upgrade and New reporting features | REQ-68 - Getting issue details... STATUS | Manoop Talasila | PORTAL | XL | Policy: C VID: C SDC: C | Portal committed by AT&T, IBM | Partially committed by Samsung (to support Springboot upgrade on "portal" repo) Partially committed by IBM for test automation GAPS: No resources to support portal/sdk repo for Springboot upgrade. | Sireesh Chintamani (Overall Integration Lead) Sunder Tattavarada (for Angular upgrade) Dominik Mizyn (for Springboot upgrade on "portal" repo) Leimeng Shi (for reporting feature) | AT&T Samsung IBM | ||||||||||
| ETSI Alignment Support | REQ-101 - Getting issue details... STATUS | SDC SO VFC VNF SDK | L | SDC: P SO: C VFC: C VNF SDK: P | Ericsson Verizon CMCC Samsung | ||||||||||||||
| Architecture - Modelling Alignment | REQ-110 - Getting issue details... STATUS | Stephen Terrill | SDC Modelling | L | |||||||||||||||
| Acumos-DCAE Integration | REQ-166 - Getting issue details... STATUS | DCAE | DCAE: C | AT&T Orange Others | |||||||||||||||
| Vertical Industry Oriented On-demand 5G Slice Service | REQ-146 - Getting issue details... STATUS | LIN MENG | Modeling, U-UI, SO, DCAE | 4 | China Mobile, Tencent, Huawei | ||||||||||||||
| Network Slicing | REQ-158 - Getting issue details... STATUS | SO, SDC, AAI, OOF, SDN-C, EXT-API, Policy | 4 | NETWORK SLICING in R6 Frankfurt | POLICY - T | POLICY - C | Wipro, AT&T, Amdocs, Verizon | ||||||||||||
| Remove Python2 dependencies | REQ-174 - Getting issue details... STATUS | David McBride | ALL projects using Python | 1 | M | ||||||||||||||
| Multicloud K8s Support (Continuation from R4) | REQ-178 - Getting issue details... STATUS | MultiCloud K8s SO SDC | 2 | K8S based Cloud region support (Continue from R4) | Multi-Cloud : C | Intel Aarna Tech Mahindra | |||||||||||||
| K8s CDS Support | REQ-182 - Getting issue details... STATUS | Multicloud K8s CDS Integration | S-M | MULTICLOUD: C CDS: C Integration: C SO: TO SDC: TO | CDS commited by Orange and Samsung MULTICLOUD commited by Samsung, Orange and Intel Integration commited by Samsung, Orange and Intel | Orange Samsung Intel | |||||||||||||
| K8s HPA Support | REQ-183 - Getting issue details... STATUS | Multicloud K8s, AAI/ESR, Policy, OOF, SO, SDC | 4 | MULTICLOUD: C OOF:TO Policy:TO AAI/ESR:TO SO: TO SDC: TO | Intel | ||||||||||||||
| K8s Security and traffic controller | REQ-171 - Getting issue details... STATUS | Multicloud K8s | Multicloud K8s | S - M | MULTICLOUD: C | Multicloud K8s | Intel | ||||||||||||
| VSP Compliance and Validation Check within SDC - Phase 2 | SDC-2482 - Getting issue details... STATUS | SDC | VSP Compliance and Validation Check within SDC | Vodafone |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
POC / Experimentation
POC Definition - (In Progress)
| Type | Requirement | Owner | Project Impacted | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL) | Project's Impact: Test Only (TO), Code (C) | Company Engagement | Notes | M4 Status |
|---|---|---|---|---|---|---|---|---|---|---|
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
4