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

Extend ORAN A1 support - Honolulu

    XMLWordPrintable

Details

    • Extend ORAN A1 support - Honolulu
    • Feature
    • GO
    • Original Scope
    • M
    • Green
    • GO
    • Green
    • Green
    • Green
    • GO
    • Green
    • GO
    • Green

    Description

      Required Information:

       Description of Use Case / Requirement:

      Planned enhancements for Rel 8 include: support of new A1 interface version in alignment to O-RAN alliance, common logging/audit. improved CSIT and OOM alignment, easier configuration, an improved NBI, and improved security cert management.

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

      JohnKeeney, micbev

      Link to HLD/LLD (if any):

      Dependency Relationships with Other Projects:

       CCSDK IMPACT: C (Code)

      • Impact Type: C (Code)
      • Company Engagement: Ericsson-EST, Others tbc.
      • Resources: JohnKeeney & team
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: tbc

      SDNC IMPACT: C (Code)

      • Impact Type: C (Code)
      • Company Engagement: Ericsson-EST, Others tbc.
      • Resources: JohnKeeney & team
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: tbc

       

      Integration Leads (use @ notation): 

      JohnKeeney & estsonsan

      Full Feature Description:

      https://wiki.onap.org/display/DW/R8+A1+Adapter+and+Policy+Management+Extension

      Further Information:

       Business Driver

      Key Contacts : John KeeneyMichela Bevilacqua

      Executive Summary:

      O-RAN has defined A1 interface specification in the context of the management of 5G RAN elements to provide intent based policies for optimization of the RAN network performance. This requirement enhances the support for Managing and Mediating O-RAN A1 Policies in ONAP.  This extends work contributed in Rel 6 - Frankfurt (REQ-38) and Rel 7 - Guilin (REQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added.

      Planned enhancements for Rel 8 include: support of new A1 interface version in alignment to O-RAN alliance, common logging/audit. improved CSIT and OOM alignment, easier configuration, an improved NBI, and improved security cert management.

      Business Impact: Continuing the convergence between ONAP and ORAN for A1 Policy interface to used by all service providers.

      Business Markets: Enhanced A1 Policy capabilities, once developed, will be usable by any service provider deploying and using ONAP.

      Funding/Financial Impacts: A1 interface provides a flexible way for the operator to manage wide area RAN network optimization, reducing capex investment needs.

      Organization Mgmt, Sales Strategies: There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.

       

      Enhancements for Honolulu Release

      • Add support for O-RAN Alliance A1-AP v2.1 specification (A1 Policy only)
      • Improve alignment with OOM deployment & configuration options
      • Improve alignment with CSIT way of working for function tests
      • New REST interface for configuration
      • New A1 Policy Management NBI (REST & DMaaP)
      • Improved security cert management
      • Stretch: Investigate if A1 Policy manipulation can be incorporated into other use cases (e.g. Slicing, OOF) - TBC

      Interface Impacts: API / SBI / NBI:

      • Northbound API Interfaces
        • Add/Change CCSDK A1 Policy Management Service NBI for A1 Policy Management (REST & DMaaP)
        • The new version of the PMS REST API complies with the ONAP REST API and Zalando style guidelines and fixes some naming inconsistencies.
          • REST (New version)
          • DMaaP (New version)
          • Ref: CCSDK-3077
      • Configuration Interfaces:
        • File based, supports dynamic refresh - including K8s ConfigMap (existing)
        • CBS/Consul (existing)
        • REST (New)
      • Southbound Interfaces – See earlier section
        • OSC A1 v2.1 (Existing)
        • O-RAN A1 v1.1 (Existing)
        • O-RAN A1 v2.1 (New)
          • (Will be added in A1 Policy Management Service. Ref O-RAN Alliance WG2 A1-AP v2.1 spec (not yet publicly released))

      Attachments

        Issue Links

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

          Activity

            People

              JohnKeeney John Keeney
              JohnKeeney John Keeney
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: