Uploaded image for project: 'Release Requirements'
  1. Release Requirements
  2. REQ-440

E2E Network Slicing use case requirements for Honolulu release

    XMLWordPrintable

Details

    • Epic
    • Status: Done
    • High
    • Resolution: Done
    • None
    • Honolulu Release
    • None
    • E2E Network Slicing use case requirements for Honolulu release
    • Use Case
    • GO
    • Reduced Scope
    • M
    • GO
    • Green
    • GO
    • GO
    • Green

    Description

      Description of Use Case / Requirement:

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

      Important Notes for Honolulu:

      • We will focus on testing different combinations of the functionality implemented in Guilin, and address any issues/gaps. For the Test Only components (Policy and SDC), if there are any bugs specific to this use case, we will assign persons to resolve them.
      • We intend to make only small enhancements to most of the components (apart from addressing gaps and issues) in order to realize e2e network slicing in a better way.
      • For CPS only an MVP will be realized in Honolulu.

      The sub-requirements/tracks include:

      (a) Enhancements in E2E Slice level:

      • Allocation:  including slice subnet stitching (with endpoints), subnet capability report, slice selection optimization, service profile and slice profile enhancement and corresponding allocation enhancement in three domains
      • Termination: mainly testing and bug-fixing

      (b) RAN Slicing: 

      • More alignment with O-RAN by mapping Slice Profile to each Near-RT RIC
      • Use A1 interface for closed loop
      • Use CPS

      M3 update: A1 interface won't be completed, though we will make progress with it. CPS shall be used only for a limited part of the functionality, remaining parts shall continue to use Config DB in Honolulu release.

      (c) Core Slicing:  Slice-related (re)configuration of core slice subnet (i.e., Core NFs).

      M3 update: No updates done in Honolulu. It will be considered for Istanbul.

      (d) Transport Slicing: 

      • Endpoints based TN NSSI selection
      • Reuse of existing TN NSSI
      • TN model enhancements

      (e) KPI Monitoring 

      • KPI calculation implementation in DCAE (completion of work started in Guilin)
      • Align with TMF 628 for KPI Monitoring in Ext-API (Stretch goal)

      M3 update: TMF 628 work is deferred until the modernized TMF 628 APIs are available.

      (f) Closed Loop and AI/ML at e2e slice and slice subnet level for RAN & Core (Core, and e2e slice level are Stretch Goals): Minor enhancements to Guilin functionality

       M3 update: Only RAN is considered for Honolulu.

      Details of potential API impacts in H-release

      Note: No new APIs are foreseen in H-release for this use case (except possibly for CPS which is under discussion). The table below describes enhancements/updates to existing APIs (except CPS).

      Interacting components API changes foreseen? Remarks
      ExtAPI -> Northbound No M3 update: TMF 628 API implementation is deferred.
      UUI -> SO No  
      SO -> OOF Yes NSSI selection (attributes such as end points), NSI selection attributes
      OOF -> CPS Yes coverageArea -> coverageAreaTAList mapping
      SO (NSMF) -> SO (NSSMF) Yes Minor updates may be needed for NSSMF Adaptor APIs, and APIs from NSSMF Adaptor towards NSSMFs.
      SO -> SDN-C/SDN-R No  
      SO -> CDS No  
      Any component -> AAI No Details are still being checked, including any impacts due to schema updates
      DCAE Slice Analysis MS -> CPS No M3 update: This will be deferred to Honolulu.
      CCSDK/SDN-C -> CPS No M3 update: This will be deferred to Honolulu. 
      UUI -> DES No  
      ExtAPI -> DES No M3 update: TMF 628 work is deferred. 

       

      RC2 update:

      The foll. integration tests are carried over to Istanbul release (see REQ-721). Further details are documented in the child wiki pages of https://wiki.onap.org/display/DW/Integration+Test+details+for+Honolulu.+

      • 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.

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

      LINMENG

      swaminathans

      Link to HLD/LLD (if any):

      https://wiki.onap.org/display/DW/R8+E2E+Network+Slicing+use+case

       

      Dependency Relationships with Other Projects:

      U-UI:C

      EXT-API: C (Stretch goal)

      SO: C (See detailed note below for SO impacts)

      OOF: C

      DCAE: C

      SDN-C: C

      Policy: TO

      SDC: TO

      A&AI: Schema changes

      CPS: C (only an MVP will be realized)

      Notes:

      (a) The exact names of persons (Resources) are being worked out for some components and will be updated.

      (b) Details of NFRs are not yet fully clear. From our use case team, we can contribute to NFRs in SO, UUI and DCAE and possibly for AAI.

      U-UI: Project (ONAP Component #1) IMPACT: C

      • Impact Type: Code
      • Company Engagement: China Mobile
      • Resources: TBD xyz (People)
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      EXT-API: Project (ONAP Component #2) IMPACT: C (Stretch Goal)

      • Impact Type: Code
      • Company Engagement: Wipro
      • Resources: Sumithra
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      SO: Project (ONAP Component #3) IMPACT: C

      • Impact Type: Code
      • Company Engagement: China Mobile, Wipro, Huawei, Tech Mahindra
      • Resources: Zhang Min, Sanchita, Deepika, Henry
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Note: SO code shall be implemented locally to ensure use case functionality can be tested, however, its merging with the Master/Honolulu branch will be discussed with PTL after the SO code re-factoring and other non-functional aspects are addressed.

      OOF: Project (ONAP Component #4) IMPACT: C

      • Impact Type: Code
      • Company Engagement: Wipro, Huawei
      • Resources: Hariharan, Krishna, Mohammed Irshad
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      DCAE: Project (ONAP Component #5) IMPACT: C

      • Impact Type: Code
      • Company Engagement: China Mobile, Wipro, LTTS
      • Resources: Ahila, Niranjana, Lu Kai
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      SDN-C: Project (ONAP Component #6) IMPACT: C

      • Impact Type: Code
      • Company Engagement: IBM
      • Resources: Sandeep Shah
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      A&AI: Project (ONAP Component #7) IMPACT: C (Schema change)

      • Impact Type: Code
      • Company Engagement: Wipro, China Mobile
      • Resources: Hetengjiao
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      CPS: Project (ONAP Component #8) IMPACT: C

      • Impact Type: Code
      • Company Engagement: IBM, Wipro, Ericsson???
      • Resources: TBD xyz (People)
      • Support Status: PS (Partially Supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Note: Only an MVP will be realized in Honolulu.

      M3 update: Only 2 APIs will be fully supported for the E2E Network Slicing use case in Honolulu (details are documented in the use case wiki page). The CPS core work will continue, and many of the yang models needed for E2E Network Slicing may also be onboarded, however, the work will continue beyond Honolulu. The first version of TBDMT service which is part of CPS will be delivered, however, it shall have only limited functionality.

      Integration Leads (use @ notation): 

      swaminathans zm330 hyu2010
       

       

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              LINMENG LIN MENG
              swaminathans Swaminathan Seetharaman
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: