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

CCVPN - Transport Slicing use case requirements for Honolulu release

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Medium Medium
    • Honolulu Release
    • None
    • None
    • CCVPN - Transport Slicing use case requirements for Honolulu release
    • Use Case
    • GO
    • Original Scope
    • M
    • GO
    • GO
    • Green
    • GO
    • GO
    • Green

      Description of Use Case / Requirement:

      This Epic captures the requirements for the Transport Slicing use case for Hononlulu release. The use case extends its functionality from Guilin release, and it shall cover:

      (a) Support the reuse and modification of existing TN NSSI

      (b) Support inter-domain connections of three network domains (CCVPN in previous releases can only connect two domains)

      Note that Honolulu can be considered as a continuation of Guilin, and the scope of changes are also smaller comparing to Guilin. 

       

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

      hyu2010

      LINMENG

       

      Link to HLD/LLD (if any):

       

      Dependency Relationships with Other Projects:

      SO: C

      SDN-C: C

      CCSDK: C

      A&AI: C

       

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

      • Impact Type: Code
      • Company Engagement: Huawei, China Mobile, Wipro
      • ResourcesTBD xyz (People)
      • Support Status: TBD S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

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

      • Impact Type: Code
      • Company Engagement: Huawei
      • ResourcesTBD xyz (People)
      • Support Status:TBD  S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      CCSDK: Project (ONAP Component #6) IMPACT: C

      • Impact Type: Code
      • Company Engagement: Huawei
      • Resources: TBD xyz (People)
      • Support Status:TBD  S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

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

      • Impact Type: Code
      • Company EngagementHuawei
      • ResourcesTBD xyz (People)
      • Support Status:TBD  S/P/N (Supported/Partially supported/Not supported)
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Details of potential API impacts in H-release

      Note: No new APIs are foreseen in H-release for this use case.

      Interacting components API changes foreseen? Remarks
      SO (NSMF) -> SO (NSSMF) Yes Minor updates may be needed for NSSMF Adaptor APIs, and APIs from NSSMF Adaptor towards NSSMFs.
      SO -> SDN-C Yes  Minor updates to generic-api to support modifiy TN NSSI. i.e., adding a new enum value

       

      Integration Leads (use @ notation): 

      hyu2010

      hesam.rahimi

      aihuaguo
       

       

            hyu2010 hyu2010
            hyu2010 hyu2010
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: