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

E2E Network Slicing requirements for Guilin release

    XMLWordPrintable

Details

    • Epic
    • Status: Done
    • High
    • Resolution: Done
    • None
    • Guilin Release
    • None
    • E2E Network Slicing requirements for Guilin release
    • Use Case
    • 3
    • GO
    • Reduced Scope
    • XL
    • Green
    • GO
    • Green
    • GO
    • Green
    • GO
    • Yellow
    • GO

    Description

       

      Description of Use Case / Requirement:

       This Epic captures the requirements for E2E Network Slicing use case for Guilin release. It shall cover:

      1. Improvements/enhancements to the functionality implemented in Frankfurt release.
      2. RAN sub-net slicing with RAN NSSMF internal to ONAP
      3. Transport sub-net slicing with Transport NSSMF internal to ONAP
      4. Core sub-net slicing with Core NSSMF internal to ONAP
      5. RAN sub-net slicing with ONAP interacting with an External RAN NSSMF
      6. KPI Monitoring by tenant/operator
      7. Simple Closed Loop Control (stretch goal to complete the full part) (Note)
      8. Intelligent Slicing for KPI guarantee (initial steps) (stretch goal to complete the full part) (Note)

      Note: Though the intention is to complete (7) and (8) (and we have resources committed), given the short release timelines, we could have some practical challenges in completing the implementation/integration in components such as SO which is impacted across multiple tracks. In such a case, the missed out parts (if any) shall be shown as a PoC/Demo and officially completed in the next release.

      M4 updates:

      • The assumptions for Guilin release for the various topics are documented in https://wiki.onap.org/display/DW/Assumptions+for+Guilin+release.
      • The basic functionality for all topics except (6) will be delivered. For Closed Loop and Intelligent Slicing (topics 7 and 8), only RAN domain PM data and actions are considered for Guilin.
      • For topic (6) (KPI Monitoring), only a part of the functionality will be completed in this release. In particular, the impacts in PM-Mapper MS in DCAE will be delivered only in the next release.

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

      LINMENG

      swaminathans

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

      None in R7.

      Project Impact (Test Only (TO), Code (C)):

      1. AAI (C)

      2. UUI (C)

      3. ExtAPI (C)

      4. SO (C)

      5. OOF (C)

      6. DCAE (C)

      7. CCSDK/SDN-C (and SDN-R) (C)

      8. CDS (C)

      9. SDC (C)

      10. Policy (C)

      11. Modeling

      Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):

      Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.

      1. AAI (S)

      2. UUI (S)

      3. ExtAPI (S)

      4. SO (S)

      5. OOF (S)

      6. DCAE (S)

      7. CCSDK/SDN-C (and SDN-R) (S)

      8. CDS (S)

      9. SDC (S)

      10. Policy (S) 

       

      Integration Leads (use @ notation): 

      zm330

      dhebeha

      hyu2010

      wangyaoguang

      milindj

      Company Engagement:

      List of Companies provide code / test commitment: CMCC, Wipro, Huawei, Tech Mahindra, IBM, TIM.

      1. AAI - Huawei, CMCC, Wipro

      2. UUI - CMCC

      3. ExtAPI - Wipro

      4. SO - CMCC, Wipro, Tech Mahindra, Huawei, TIM

      5. OOF - Wipro, Huawei

      6. DCAE - CMCC, Wipro

      7. CCSDK/SDN-C (and SDN-R) - Huawei, IBM, Wipro, TIM

      8. CDS - Tech Mahindra, TIM

      9. SDC - CMCC

      10. Policy - Wipro

      (Modeling - CMCC, Amdocs)

      (RAN-Simulator - Wipro, Core-NF Simulator - LTTS, External RAN NSSMF Simulator - Huawei)

      Attachments

        Issue Links

          is blocked by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ONAPARC-583 Guilin-R7 ArchCom Review (AR-0011-R7-052020) E2E Network Slicing Architecture

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Task - A task that needs to be done. CCSDK-2919 5G Core Network Service CBA package

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Task - A task that needs to be done. REQ-436 Integration Test for E2E Network Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Done
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-2917 E2E Network Slicing: Transport Subnet Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-2919 E2E Network Slicing: Functional improvements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. AAI-3016 AAI impacts for E2E Network Slicing use case in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. AAI-3017 E2E Network Slicing: NST details

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CCSDK-2390 E2E Network Slicing: Core Subnet Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CCSDK-2391 E2E Network Slicing: Close Loop Control

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CCSDK-2533 CCSDK support of Network Slicing in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DCAEGEN2-1878 Support 5G slicing - E2E network slicing use case

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-2255 E2E Network Slicing: Closed Loop Control (Slice Analysis mS)

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-2258 E2E Network Slicing: KPI Monitoring - New DES MS

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-2259 E2E Network Slicing: Intelligent Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. DCAEGEN2-2338 E2E Network Slicing use case impacts in DCAE for Guilin Release

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DCAEGEN2-2339 E2E Network Slicing: KPI Monitoring - PM Mapper enhancements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-764 NST selection enhancements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-765 E2E Network Slicing: RAN Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-766 E2E Network Slicing: Transport Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-767 E2E Network Slicing: Core Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OPTFRA-797 OOF enhancements to Frankfurt contents for E2E Network Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OPTFRA-798 OOF functionality for RAN, Core and Transport Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-801 NSSI selection enhancements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OPTFRA-802 NSI selection enhancements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. POLICY-2586 E2E Network Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. POLICY-2701 This epic covers the work to enhance control loop for E2E networking slicing use case.

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SDC-3086 E2E Network Slicing: subnet slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SDNC-915 SDN-C (SDN-R) support of E2E Network Slicing in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SDNC-1198 E2E Network Slicing: RAN Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SDNC-1199 E2E Network Slicing: RAN Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2958 E2E Network Slicing: External NSSMF interface

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2959 E2E Network Slicing: Transport Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2960 E2E Network Slicing:Core Subnet Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2961 E2E Network Slicing: Intelligent Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2962 E2E Network Slicing: Functional improvements

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2963 E2E Network Slicing: Sub-net slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2964 E2E Network Slicing: RAN Sub-net Slicing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SO-2965 E2E Network Slicing: Closed Loop Control

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SO-3036 SO impacts for E2E Network Slicing use case in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. USECASEUI-444 CCVPN - Transport Slicing: UUI development

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CCSDK-2533 CCSDK support of Network Slicing in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SDNC-915 SDN-C (SDN-R) support of E2E Network Slicing in Guilin

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-347 CCVPN-Transport Slicing for Guilin Release

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Done

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. REQ-440 E2E Network Slicing use case requirements for Honolulu release

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

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

          Activity

            People

              swaminathans Swaminathan Seetharaman
              swaminathans Swaminathan Seetharaman
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: