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.
| 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) | 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 | Service Resolver | SDC (C), SO (C), AAI (TO) | Orange |
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
| 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) | 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) | Company Engagement | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Self Serve Control Loops | REQ-9 - Getting issue details... STATUS | SDC DCAE POLICY | Self Serve Control Loops | CLAMP | XL | SDC - 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 | AT&T, Ericsson | |||||||||||
| Policy Update Notifications | REQ-25 - Getting issue details... STATUS | DCAE POLICY | Policy Update Notifications | S | 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 | AT&T | ||||||||||||
| Integration of CDS as Actor in Control Loops | REQ-33 - Getting issue details... STATUS | CLAMP POLICY CDS | CDS actor support in Policy | L | CLAMP - C POLICY - C CDS - C | AT&T, Bell Canada, Ericsson | ||||||||||||
| Modeling: Network Slicing modeling | REQ-60 - Getting issue details... STATUS | Chuyi Guo | SDC SO OOF AAI External API | NETWORK SLICING in R6 Frankfurt | SDC | L | SDC-C AAI-C | CMCC Amdocs AT&T Wiprc Huawei | ||||||||||
| Modeling: Align service model with SDC implementation | Kevin Scaggs | SDC | SDC | M | AT&T | |||||||||||||
Modeling: VES model enhancement (relations, config management, Maria DB DM, status report) | SDC SO DCAE AAI Controller Modeling | 5G CONFIGURATION (RunTime DB) | L | AT&T Nokia | ||||||||||||||
| 5G / Network Topology Management. Network configuration tree structures | SO SDC AAI Controller ConfigDB Modeling | NETWORK TOPOLOGY MANAGEMENT (R7 GuiLin) | L | SO: SDC: AAI: Controller: ConfigDB: | AT&T | |||||||||||||
| 5G / Run-time data persistency (RunTime DB / CM) | SDC A&AI Controller SO Modeling | 5G CONFIGURATION (RunTime DB) | ||||||||||||||||
| Modeling: GeoLocation Model (and standards harmonization) | AAI PRH DCAE Modeling | PNF PLUG and PLAY in R6 Frankfurt | AAI | M | Ericsson Nokia | |||||||||||||
| PNF Software Upgrade using direct Netconf/Yang interface with PNF | REQ-84 - Getting issue details... STATUS | SDC VID SO CDS VNFRQTS Integration | PNF software upgrade in R6 Frankfurt | M | SDC: C SO: C CDS: C VID: C | Ericsson | ||||||||||||
| Enable Schema Update once PNF software is updated | REQ-88 - Getting issue details... STATUS | SDC VID SO CDS VNFRQTS Integration | PNF software upgrade in R6 Frankfurt | M | Ericsson | |||||||||||||
| LCM API Evolution | REQ-72 - Getting issue details... STATUS | SO SDC | PNF software upgrade in R6 Frankfurt | M | SDC: C SO: C CDS: C | Ericsson | ||||||||||||
| PNF / PNF Software Upgrade Using Ansible protocol with EM | REQ-53 - Getting issue details... STATUS | SDC VID SO CDS VNFRQTS Integration | PNF software upgrade in R6 Frankfurt | M | Huawei | |||||||||||||
| 5G / ORAN & 3GPP Standards Harmonization | REQ-38 - Getting issue details... STATUS | SDNC DCAE CDS Modeling | MOBILITY STANDARDS HARMONIZATION WITH ONAP | M | SDNC: C DCAE: C CDS: C | AT&T Nokia | ||||||||||||
| 5G / License Management | VNFREQ, after UCs agreed SDC(*) Modeling(*) ( *) No changes expected in R6 as an outcome of the proposed UC | LICENSING MANAGEMENT | SDC | M | AT&T Nokia Ericsson | |||||||||||||
| 5G / Bulk PM | AAI CLAMP DCAE SDC Integration | 5G Bulk PM in Frankfurt/R6 | Ericsson | |||||||||||||||
| 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 | ||||||||||||
| 5G / FM Meta Data | Marge Hillis | GAB Config file | FM META DATA & PM DICTIONARY in R6 Frankfurt | |||||||||||||||
| End to End Layer 1 Service Management. Modeling the Optical Service | REQ-37 - Getting issue details... STATUS | SDC SO AAI Controller DCAE Modeling | 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 | ||||||||||||
| PNF / Plug and Play | Benjamin Cheung | SO Modeling | PNF PLUG and PLAY in R6 Frankfurt | |||||||||||||||
| PNF / Configuration with NETCONF | REQ-76 - Getting issue details... STATUS | AAF SDNC Integration | Configuration with NETCONF in Frankfurt/R6 | Ericsson | ||||||||||||||
| PNF / PNF pre-onboarding onboarding | VNF-SDK Integration | PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt | ||||||||||||||||
| Modeling: Runtime instance model based on A&AI reverse engineering | James Forsyth | AAI | Reverse-engineering AAI data model to Papyrus information model | AAI | L | AT&T Ericsson Huawei | ||||||||||||
| Modeling: documentation of policy and allotted resource model | Kevin Scaggs | Policy SDC | Policy SDC | M | AT&T | |||||||||||||
| Scaling Extensions | REQ-42 - Getting issue details... STATUS | VID APPC SO | Scaling Use Case (Frankfurt) | S-M | AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra Orange | |||||||||||||
| Portal Security Enhancements | REQ-64 - Getting issue details... STATUS | Manoop Talasila | PORTAL | MUSIC | L | Policy: C VID: C SDC: C | AT&T Samsung | |||||||||||
| Portal Technology Stack Upgrade and New reporting features | REQ-68 - Getting issue details... STATUS | Manoop Talasila | PORTAL | XL | Policy: C VID: C SDC: C | AT&T Samsung |
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.