Before editing please read instructions here.

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. 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 9 include support of new A1 interface versions to align with new versions & improvements to O-RAN alliance specifications.

Owners

JohnKeeney **  micbev  zuqiang

Link to HLD/LLD (if any):

• Wiki page: O-RAN A1 Policies in ONAP
• Proposal: 
  • A1 Policy Function Extensions 
  • A1 Policy Function Extensions (ORAN/ONAP/3GPP Harmonization) 
• Reviewed and approved by by Requirements Subcommittee 29 March 2021
  20210329 ONAP-Istanbul-REQ-A1Policy.pdf

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

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

Interfaces / APIs:

• Northbound Interface

• As before (Honolulu)
  • Continue deprecating A1-PMS v1 NBI (REST & DMaaP)

• Southbound Interfaces

• As before (Honolulu)
  • OSC A1 v2.1 (Existing)
  • O-RAN A1 v1.1 (Existing)
  • O-RAN A1 v2.0 (Existing)
• O-RAN A1 v3.0 (Planned – small evolution)

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

• RESTCONF: Add support for RFC 8040 RESTCONF version

Integration Leads

JohnKeeney  estsonsan