Before editing please read instructions here.

 Description of Use Case / Requirement:

 This Epic captures the requirements for E2E Network Slicing use case for Istanbul release.

 In this release, we will be making only small enhancements to most of the impacted components. The requirements are split across the foll. tracks.

(a) Carryover integration tests from Honolulu release

• NSMF: Option 2 testing, remaining regression testing and service termination testing for NSMF
• RAN NSSMF: RAN NSSI termination, interactions with TN NSSMF for FH/BH NSSI reuse and some minor aspects related to SDN-R <-> RAN interaction
• TN NSSMF: Checking some minor aspects in SO for modifying TN NSSI.
• Core NSSMF: Modifying and deallocating a Core NSSI, reusing an existing Core NSSI
• KPI Computation, Closed Loop & Intelligent Slicing: Some minor aspects on SDN-R <-> RAN-Sim interface alone needs to be addressed.

Note: In the following tracks, "Integration testing" refers to scenarios not covered by the above as well as in Honolulu release.

(b) E2E Network Slice

• Testing of scenario combinations of Slice LCM from an e2e perspective M3 update - support for mMTC and uRLLC slices will be taken care in J-release

• Start with use case test automation M3 update - deferred to J-release
• Slice selection taking into consideration resource occupancy levels (stretch goal)

(c) RAN Slicing

• RAN Configuration enhancements
• Complete integration with CPS for all Network Slicing related config M3 update: CPS integration with SDN-R for activate, reconfigure and terminate scenarios will be done in J-release
  M4 update: SDNR-CPS integration for instantiateRANSlice-allocate and reconfigure scenarios will be taken care in the Jakarta release
• Integration testing of different scenario combinations with TN (FH and MH)
  RC update: Integration with ACTN simulator for different combinations are in progress and it will be continued to the J-release
• Support of Option 2 (stretch goal)
• Instantiation of RAN NFs and initial configuration (stretch goal)

(d) Core Slicing enhancements

• Reuse of part of core sub-net (covered as separate requirement)
• Integration testing of different scenario combinations
  RC update: Few test cases for Core NSSI Deallocation are deferred to J-release
• Use of ETSI-SOL005 aligned for Core NS creation by Core NSSMF (stretch goal, likely to be taken up beyond I-release)

(e) Transport Slicing enhancements

• Integration testing of different scenario combinations for BH, FH and MH
• Other TN slicing enhancements will be covered by CCVPN use case (and not tracked here)

(f) KPI Monitoring, Closed Loop

• Closed Loop updates over A1 M3 update: This is not completed by M3, we will continue to work post M3 to complete it by I-release
  M4 update: This activity is done at POC level and completed before M3. It will be enhanced with the comments received from John Keeny.

• KPI computation enhancements (stretch goal)
  M4 update: Two requirements agreed for I-release are completed on time before M3 timeline. Remaining requirements will be done in Jakarta release

(g) Modeling (stretch goal)

• Service and Slice Profile enhancements – perfReq per slice ‘type’
• RAN slice sub-net modeling enhancements (including front-haul and mid-haul)
• Use of service reference (iso Allotted Resource)

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

SaravananAyyadurai LINMENG

Link to HLD/LLD (if any):

Potential API impacts in I-release:

Note: No new APIs are foreseen in I-release for this use case except possibly for CPS and OOF->DCAE (stretch goal). The table below summarizes potential API impacts.

Dependency Relationships with Other Projects:

Note: We don't know all the details of NFRs. From our use case team, we can contribute to NFRs in DCAE and OOF.

Project SO IMPACT: C

• Impact Type: C
• Company Engagement: Wipro, TechMahindra, TIM
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

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
• 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: REQ-xxx, REQ-yyy
  M1 update: Exact details of CPS scope & associated impacts for Istanbul are still being worked out. Based on the progress and discussions in next 1-2 weeks, we will update the scope if needed before M2.

+Project CCSDK/SDN-C IMPACT: C

• Impact Type: C
• Company Engagement: IBM, Wipro
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project Modeling IMPACT: NA

• Impact Type: NA
• Company Engagement: Amdocs
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Integration Leads (use @ notation): 

krishnaa96 deepikasatheesh