• Before editing please read instructions here.

 Description of Use Case / Requirement:

This epic covers the Kohn release requirements for E2E Network slicing use case in the following tracks.

1. E2E Network slicing Solution
2. RAN Slicing
3. Transport Slicing
4. Carry over testing from Jakarta Release

1. E2E Network slicing Solution

• Dynamic Discovery of Core & RAN endpoints at NSMF (carry-over requirement from Jakarta)
  • NSMF discovers the Core and RAN endpoints of back haul dynamically at the time of slice allocation/reuse
  • Front haul and mid haul end points discovery is a stretch goal
  • Only design is considered in Kohn release. Implementation will be done in future release
  • M4 update: Likely to be pushed to future releases beyond Kohn. 

• IBN driven E2E Network Slicing
  • Integration of ML prediction MS with DCAE (covered by both IBN and network slicing use cases)
    M4 update: Mainstreaming the ml-prediction-ms and enhancements are moved to next release
  • Enhancement to intent creation and update workflow - Enhancement to Slice Analysis MS to use DCAE SDK dmaap-client lib for real-time intent listening posted by AAI (covered by IBN use case)
  • Enhancement to Slice Analysis MS to report slice KPI to UUI to support IBN
• mIoT slice support
  • Support Slice creation, activation, deactivation and termination for mIoT applications
  • Solution design and offline implementation to main branch is considered in Kohn release. Implementation will be done in future release

• New network slicing KPI monitoring in UUI
  • KPI Computation MS to store the KPIs of Network Slice, invoke Datalake API
    M4 update: KPI computation is done, storing to data lake will be deferred
  • UUI to fetch the new KPIs from DES, fit and display the additional KPIs on the screen
    M4 update: UUI changes done and tested with mock data
• Use case test automation (carry-over requirement from Jakarta) 
  • Carry out test automation for slicing use case in phases over multiple releases
  • Target to accomplish test automation for manual configurations
  • M2 update: Due to the lack of resources, integration team is uncertain about supporting the automation in K-release. Automation will be taken care based on the resources availability. Marking it as a stretch goal.
  • M4 update: will be deferred to future releases 

2. RAN Slicing - M4 update: Deferred to future releases

• RAN slice O-RAN A1-based action flow over A1 interface
  • Only design is considered in Kohn release. Implementation will be done in future release
  • M4 update: Will be deferred to future releases due to limited bandwidth
• xNF configuration data update to CPS via ONAP DMI Plugin for RAN slice allocation - M4 update: Scope will be reduced to partial implementation including CM notification but excluding data to CPS via DMI plugin API. End to end implementation will be done in future releases.
• CSIT for RAN slicing - M4 update: Will be deferred to future releases.

3. Transport Slicing (covered by CCVPN use case)

• Align TN interface with latest IETF TN slice model
• CSIT for transport slicing

4. Carry-over requirements from Jakarta Release

• DCAE functional requirements - KPI Computation Enhancements
  • Changes to accommodate following review comments in https://jira.onap.org/browse/DCAEGEN2-2801
    • Define KPI spanning multiple resources
    • Error handling to manage if a particular counter needed for a calculation is unavailable

• DCAE R11 Global requirements Contribution - https://wiki.onap.org/display/DW/R11+Global+requirements+Contribution 
• DCAE non-functional requirements
  • DCAEGEN2-2907: No root (superuser) access to database from application container (Stretch goal)
  • DCAEGEN2-2882   DL Admin UI access via HTTPS
  • DCAEGEN2-2976   Support 7.2.1 VES in TCAGEN2 

• Fix to Core Slicing issues SO-3810, SO-3835, SO-3838
• Carry-over tests from Jakarta
  • https://wiki.onap.org/display/DW/Carry-over+Test+Cases+from+Jakarta+Release 

Potential API impacts in Kohn release:

Owners (one of these should be the Assignee - use @ notation):

kevin.tang, ahilap

Link to HLD/LLD (if any):

Dependency Relationships with Other Projects:

Project UUI IMPACT: C

Impact Type: C
Company Engagement: TBD (China Telecom? China Mobile?)
Resources: xyz (People)
Support Status: 
Non-Functional Requirement Support: NA
 
Project SO IMPACT: C

Impact Type: C
Company Engagement: Wipro, TIM
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: NA

Project DCAE IMPACT: C

Impact Type: C
Company Engagement: Wipro, China Telecom
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

Project RAN-Sim IMPACT: C

Impact Type: C
Company Engagement: CapGemini, Ericsson, Wipro
Resources: xyz (People)
Support Status: S
Non-Functional Requirement Support: NA

Project Policy IMPACT: TBD

• Impact Type: C
• Company Engagement: TBD (Ericsson?)
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Integration Leads (use @ notation): 
deepikasatheesh, malar