The page is intended to summarize all the requirements for Frankfurt Release.
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
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) | 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 | 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 | 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) | 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 | 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 | CLAMP POLICY | TOSCA Compliant Policy Types | SDC | M | CLAMP - C POLICY - C | AT&T, Ericsson | ||||||||||||
Policy Update Notifications | DCAE POLICY | Policy Update Notifications | S | DCAE - C POLICY - C | AT&T | |||||||||||||
CLAMP Deployment of Policies to PDP Groups | CLAMP POLICY | CLAMP Deployment of Policies to PDP Groups | M | CLAMP - C POLICY- C | AT&T | |||||||||||||
Integration of CDS as Actor in Control Loops | CLAMP POLICY CDS | CDS actor support in Policy | L | CLAMP - C POLICY - C CDS - C | AT&T, Bell Canada, Ericsson | |||||||||||||
Modeling: Network Slicing modeling | 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 / PNF S/W Upgrade | SDC VID SO CDS Modeling VNFRQTS Integration | PNF software upgrade in R6 Frankfurt | S | Ericsson Huawei | ||||||||||||||
5G / ORAN & 3GPP Standards Harmonization | 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 | GAB Config file | 5G Bulk PM in Frankfurt/R6 | ||||||||||||||||
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 | SDC SO AAI Controller DCAE Modeling | Multi-domain Optical Network Services | L | AT&T Orange Fujitsu | ||||||||||||||
5G / 5G NRM Network Resource Model (Configuration Mgmt) | 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 | 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 | VID APPC SO | Scaling Use Case (Frankfurt) | S-M | AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra 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.
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.