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

A1 Policy Functions - Kohn

XMLWordPrintable

    • A1 Policy Functions Extension - Kohn
    • Specification
    • 0
    • Not required
    • Original Scope
    • M
    • Not used for this release
    • Not used for this release

      Description of Use Case / Requirement:

      This feature requirement enhances A1 Policy Management for the O-RAN A1 interface capabilities provided in Rel 6, 7, 8, 9, 10. Work will continue by extending & evolving support for using A1 Policies to manage 5G RAN elements by providing intent based policies for optimization of the RAN network performance. Planned enhancements for Rel 11 include support of new A1 interface versions to align with new versions & improvements to O-RAN alliance specifications.

      Owners

      JohnKeeney ** 

      Link to HLD/LLD (if any):

      Dependency Relationships with Other Projects:

      CCSDK

      • A1 Policy Management Service and A1 Adapter are homed in CCSDK
      • Impact Type: C (Code)
      • Company Engagement: Ericsson
      • Resources: Ericsson team & others
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: tbc

      SDNC (No change in Kohn)

      • A1 Adapter is deployed as part of SDNC
      • A1 Policy Management Service is a standalone micro-service deployed with SDNC
      • Impact Type: none
      • Company Engagement: Ericsson
      • Resources: Ericsson team & others
      • Support Status: S (Supported)
      • Non-Functional Requirement Support: tbc

       

      Interfaces / APIs:

      • Northbound Interface

      • As before (Istanbul)
        • A1-PMS v2 NBI (REST & DMaaP) has existed since Honolulu
      • It is hoped that O-RAN Alliance will continue to specify the O-RAN R1 interface - which should expose a service for Non-RT-RIC interactions for A1 Policies.
        • A1-PMS NBI will evolve (backward compatible) to support this R1 Service once defined - perhaps during the lifetime of this REQ.

      • Southbound Interfaces

      • As before (Istanbul)
        • OSC A1 v2.1 (Existing)
        • O-RAN A1 v1.1 (Existing)
        • O-RAN A1 v2.0 (Existing)
        • O-RAN A1 v3+ (Small changes from v2.0)
          • If changes are approved by O-RAN Alliance during this lifetime of this REQ.
        • Add support for custom connector plug-ins to easily support new A1 connection profiles

      • Internal Interface (A1 Policy Management Service <-> A1 Adapter)

      Integration Leads

      JohnKeeney  estsonsan
       

       

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

              Created:
              Updated:
              Resolved: