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

5G SON use case enhancements for London release

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: High High
    • London Release
    • None
    • None
    • 5G SON use case enhancements for London release
    • Use Case
    • GO
    • Original Scope
    • Not used for this release
    • Not used for this release

      Before editing please read instructions here.

       Description of Use Case / Requirement:

      This use case aims at realizing ONAP-based SON functionality for radio networks aligned with O-RAN. In the London release, it will focus on:

      • Configuration Management (CM) update notification VES messages from RAN-Sim
      • Processing of CM update notifications to update CPS DB
      • Carry-over work from Kohn release for CCSDK

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

      nkshankar

      Link to HLD/LLD (if any):

      Note: We don't know all the details of NFRs. 

      Dependency Relationships with Other Projects:

       RAN-Sim IMPACT: C (Simulation Repo, Not ONAP Project)

      • Impact Type: C
      • Company Engagement: CapGemini, Wipro
      • Resources: xyz (People)
      • Support Status: S

      Project DCAE IMPACT: No change to API

      • Impact Type: Part of test (VES Collector, VES parser)
      • Company Engagement: Capgemini, Wipro
      • Resources: xyz (People)
      • Support Status: 
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Project CPS IMPACT: Code change

      • Impact Type: Adaptation of NCMP/DMI. No change to API
      • Company Engagement: Ericsson, Capgemini
      • Resources: xyz (People)
      • Support Status: 
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Project CCSDK/SDN-C IMPACT: Merge/test only

      • Impact Type: Merge of carryover work. No API change (See CCSDK-3817)
      • Company Engagement: CapGemini, AT&T
      • Resources: xyz (People)
      • Support Status: S
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Project Policy IMPACT: None

      • Impact Type: Part of test
      • Company Engagement: AT&T, Ericsson
      • Resources: xyz (People)
      • Support Status: 
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Project OOF IMPACT: None

      • Impact Type: Part of Test
      • Company Engagement: TBD
      • Resources: xyz (People)
      • Support Status: 
      • Non-Functional Requirement Support: REQ-xxx, REQ-yyy

      Integration Leads (use @ notation): 

      TBD (vvarvate )
       

      API Impacts in I-release:

      Summary: We do not expect changes in APIs. The tasks involve completing carry-over work and creating configuration features for existing modules.

      Interacting components API changes foreseen? Remarks
      Within RANSim: No RANSim is part of INT and not a "ONAP Project"
      RANSim -> DCAE No Use existing DCAE VES Collector
      DCAE -> CPS No Use existing APIs. May need configuration or feature set up. 

            nkshankar nkshankar
            nkshankar nkshankar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: