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

E2E Network Slicing use case enhancements for London release

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: High High
    • London Release
    • None
    • None
    • E2E Network Slicing use case enhancements for London release
    • Use Case
    • 4
    • GO
    • Reduced Scope
    • M
    • Not used for this release
    • Not used for this release

      • Before editing please read instructions here.

      Description of Use Case / Requirement:

      Below is a list of the London release requirements for E2E Network slicing use case:

      1. Mainstreaming the ML prediction MS. https://jira.onap.org/browse/DCAEGEN2-3067  M4 update: This will be PoC delivery and not to be included for the official London release since no further support available. Please see 5/3/2023 comments in https://jira.onap.org/browse/DCAEGEN2-3067
      2. Storing KPI in DB via DL admin UI to complete KPI reporting from Slice Analysis MS to UUI for IBN based slicing. Has dependency on https://jira.onap.org/browse/DCAEGEN2-2882  M2 update:  due to a resource crunch, this will be deferred to future releases.
        • End-to-end intent loop integration testing will be done in M release by IBN team
      3. Supporting 3GPP 28.532 APIs for network slicing - enhancement to SO macro flow to support 3GPP 28.532 APIs for network slicing along with the existing 3GPP 28.531 APIs. https://jira.onap.org/browse/SO-4037   M4 update: on track
      4. Carry-over test cases from previous releases https://jira.onap.org/browse/REQ-1377  M2 update:  due to a resource crunch, this will be deferred to future releases. 

       

      Potential API impacts in Kohn release:

      Interacting components API changes foreseen? Remarks
      ExtAPI -> Northbound    
      UUI -> SO    
      SO -> OOF Yes Supporting 3GPP 28.532 APIs for network slicing.
      OOF -> CPS    
      SO (NSMF) -> SO (NSSMF)    
      SO (NSSMF Adapter) -> SO (External RAN NSSMF)    
      SO -> SDN-C/SDN-R    
      SDN-R -> RAN Simulator    
      Any component / SO -> AAI    
      DCAE Slice Analysis MS -> CPS    
      CCSDK/SDN-C -> CPS    
      UUI -> DCAE    
      AAI -> DCAE    
      Policy -> DCAE    
      Policy -> SO    

      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 DCAE IMPACT: C

      Impact Type: C
      Company Engagement: Wipro, China Telecom
      Resources: Deepika S
      Support Status: S
      Non-Functional Requirement Support: Non

      Project SO IMPACT: C

      Impact Type: C
      Company Engagement: DT
      Resources: Sanchita Pathak
      Support Status: S
      Non-Functional Requirement Support: NA

      Project OOF IMPACT: C

      Impact Type: C
      Company Engagement: DT
      Resources: Sanchita Pathak 
      Support Status: S
      Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Integration Leads (use @ notation): 
      deepikasatheesh, sanchitapathak 
       
       

       

            kevin.tang kevin.tang
            kevin.tang kevin.tang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: