Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 ( JiraserverONAP JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyREQ-38) and Rel 7 - Guilin ( JiraserverONAP JIRAserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyREQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added.

...

TOPICInformation
Requirements Proposal
Architecture S/C info


Prior Project "Base" WikiONAP/3GPP & ORAN Alignment: A1 Adapter extensions (Guilin)
Requirements Jira (REQ-###) Ticket

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyREQ-457

Key Use Case Leads & Contacts

USE CASE LEAD:  John Keeney

USE KEY CONTACTS: Michela Bevilacqua

Meetings Register & Recordings

ONAP/O-RAN-SC/SMO Meetings

...

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 ( JiraserverONAP JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyREQ-38) and Rel 7 - Guilin ( JiraserverONAP JIRAserverId425b2b0a-557c-3c0c-b515-579789cceedbkeyREQ-352). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added.

...

Use cases define how different users interact with a system under design. 

O-RAN A1 Policy Functions


Enhancements for Honolulu Release

  • Add support for O-RAN Alliance A1-AP v2.0 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 manuipulation can be incorporated into other use cases (e.g. Slicing, OOF) - TBC

A1 Policies - Northbound Interface (REST & DMaaP) Proposed

  • Changes proposed for A1 Policy Management Service NBI (not-backward compatible)
    • Coming Soon!

Use Case Functional Definitions

Synchronize A1 Policy Information in RAN

Synchronize A1 Policy Information in RANImage Added

A1 Policy Type / Instance Operations

Image Added

A1 Policy Instance Status Operations

A1 Policy Instance Status OperationsImage Added

Other Impacts

Affected ONAP Functions:

  • SDNC / CCSDK only

Integration of bordering ONAP components:

  • TBC

Interfaces:

  • Northbound Interface – See earlier section
    • Add/Change SDNC NBI for A1 Policy Management (REST & DMaaP)
      • REST (New version)
      • DMaaP (New version)
  • Configuration
    • 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.0 (New)

Usage outside ONAP:

  • Used in O-RAN-SC NONRTRIC Project (Downstream)
  • Southbound Interface: O-RAN A1 Interface + Information Model is specified and maintained by O-RAN Alliance

Modelling Impacts:

  • TBC

Other:

  • Update Documentation with A1 interface aspects
  • Update Integration & Existing Test requirements

Testing

Test use-cases:

  • Synchronize A1 Policy Information in RAN
  • A1 Policy Type / Instance Operations
  • A1 Policy Instance Status Operations

Use Case Functional Definitions

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.

Use Case Title

A1 Adapter and Policy Management Extension

Actors (and System Components)

SDNC / CCSDK - A1 Adapter

Description

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 (

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId425b2b0a-557c-3c0c-b515-579789cceedb
key
Jira
serverONAP JIRA
serverId425b2b0a-557c-3c0c-b515-579789cceedb
key

Points of Contact


John Keeney Michela Bevilacqua


Preconditions

N/A

Triggers / Begins when

N/A

Steps / Flows (success)


Post-conditions


Alternate / Exception Paths


Related Use Cases

TBC

Assumptions

None

Tools / References / Artifacts

See additional information on this page

...