-
Epic
-
Resolution: Done
-
High
-
None
-
None
-
E2E Network Slicing use case enhancements for Jakarta release
-
Use Case
-
4
-
GO
-
Reduced Scope
-
M
-
Not used for this release
-
Not used for this release
- Before editing please read instructions here.
Description of Use Case / Requirement:
This epic covers the J-release requirements for E2E Network slicing use case in the following tracks.
1. E2E Network slicing Solution
2. RAN Slicing
3. Transport Slicing
4. Closed Loop
5. Carry over testing from Istanbul Release
1. E2E Network slicing Solution
- Slice selection taking into consideration resource occupancy levels
- Dynamic Discovery of Core & RAN endpoints at NSMF
- M2 update: RAN endpoint in back haul is considered for J-release, Core endpoint discover is a stretch goal
- M4 update: It can be done in the future release, as more details need to be worked out.
- Activate, Deactivate scenarios support in external RAN NSSMF - Option2
- RC notes: Merge will be done in future release
- Use case Automation
- M4 update: Work in progress on the supporting SDK. May be extended beyond J-release
2. RAN Slicing
- Optimizing cm-handle registration with CPS-DMI Plugin to upload yang model
- CPS Integration with SDN-R for RAN Slice allocate and reconfigure scenarios
- CPS-TBDMT enhancement to integrate with NCMP
- M2 Update: This requirement will be implemented once the Caching is enabled in CPS
- M4 Update: Will be done in future releases
- CPS Integration Stabilization - RAN Slice activate/deactivate and terminate scenarios
- CSIT for RAN slicing
- RC notes: Deferred to future release due to a pending bug fix
3. Transport Slicing
- TN NSSMF enhancements according to IETF latest specification
- M4 update: Will be deferred to next release.
- Implementing the call to OOF for allocateNSSI (to enable TN NSSI reuse) in TN NSSMF
- Implementing the call to OOF for terminateNxi API to deallocate NSSI (to enable TN NSSI NOT terminated even when NSI is terminated) in TN NSSMF
- Transport Slicing enhancement to support IBN based E2E slicing
- M4 update: Will be deferred to next release
- Closed-loop enhancement in CCVPN to support Transport Slicing’s closed-loop
- CSIT for transport slicing
- M4 update: Will be deferred to next release
4. Closed Loop
- IBN based Closed loop for Network Slicing
- M2 Update - ML Prediction MS enhancements will be done as a POC work in this release.
- CPS Integration Stabilization
5. Carry over testing from Istanbul Release
Option-1
- E2E testing for activate/deactivate scenario
- RC notes: Deferred to future release due to a pending bug fix
- Complete the pending test cases for E2E Slice termination
NSMF driven TN slicing
- Complete the pending testing for activate/deactivate and terminate scenarios
- RC notes: Deferred to future release due to a pending bug fix
Potential API impacts in J-release:
Interacting components | API changes foreseen? | Remarks |
---|---|---|
ExtAPI -> Northbound | No | |
UUI -> SO | Yes | New interface for RAN,CN endpoints discovery |
SO -> OOF | May be | NSI/NSSI selection - additional inputs for capacity |
OOF -> CPS | No | |
SO (NSMF) -> SO (NSSMF) | No | |
SO (NSSMF Adapter) -> SO (External RAN NSSMF) | Yes | Activate, Deactivate flows support in external RAN NSSMF |
SO -> SDN-C/SDN-R | Yes | To fetch the RAN network Topology |
SO -> CDS | No | |
Any component -> AAI | Yes | SO invokes AAI to read the nexthopinfo |
DCAE Slice Analysis MS -> CPS | No | |
CCSDK/SDN-C -> CPS | Yes | Use CPS in place of Config DB |
UUI -> DES | No | |
ExtAPI -> DES | No | |
OOF -> DCAE | Yes | NSI/NSSI selection based on resource occupancy level |
Owners (one of these should be the Assignee - use @ notation):
Link to HLD/LLD (if any):
Dependency Relationships with Other Projects:
Project UUI IMPACT: C
Impact Type: C
Company Engagement: China Mobile
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: NA
Project SO IMPACT: C
Impact Type: C
Company Engagement: Wipro, TechMahindra, TIM
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: NA
Project DCAE IMPACT: C
Impact Type: C
Company Engagement: Wipro
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: REQ-xxx, REQ-yyy
Project OOF IMPACT: C
Impact Type: C
Company Engagement: Wipro, STL
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: REQ-xxx, REQ-yyy
Project CPS IMPACT: C
Impact Type: C
Company Engagement: Wipro (TBDMT) (CPS Core is covered by CPS team)
Resources: xyz (People)
Support Status: To be confirmed
Non-Functional Requirement Support: NA
Project CCSDK/SDN-C IMPACT: C
Impact Type: C
Company Engagement: Wipro
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: NA
Integration Leads (use @ notation):
deepikasatheesh, Niranjana
- clones
-
REQ-1 ONAP Requirement Template
- To Do
- is blocked by
-
CCSDK-3554 CCSDK impacts for Network slicing in Jakarta Release
- Closed
-
CPS-819 CPS impacts for Network slicing in Jakarta Release
- Closed
-
DCAEGEN2-3021 DCAE Impact for E2E Network Slicing in Jakarta release
- Closed
-
OPTFRA-1027 OOF impacts for Network slicing in Jakarta Release
- Closed
-
SO-3826 SO impacts for Network slicing in Jakarta Release
- Closed
-
USECASEUI-636 UUI impacts for E2E Network Slicing in Jakarta Release
- Closed
-
REQ-1149 Carryover Test Cases from Istanbul Release
- Done
-
REQ-1151 Integration Test of RAN NSSMF
- Done
-
REQ-1152 Integration Test of TN Sub-net Slicing
- Done
-
REQ-1153 Integration Test of Closed Loop for Network Slicing
- Done
-
REQ-1154 E2E Network Slicing Testing
- Done
- is cloned by
-
REQ-1215 E2E Network Slicing use case enhancements for Kohn release
- Done
- relates to
-
REQ-721 E2E Network Slicing use case enhancements for Istanbul release
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...