Homepage / Wiki

Use Case Name

A1 Policy Function Extensions (R9 Istanbul)

 John Keeney Michela Bevilacqua Zu Qiang (Ericsson)

Use Case Overview & Description

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.

Use Case Key Information

TOPICInformation
Requirements ProposalA1 Policy Function Extensions (ORAN/ONAP/3GPP Harmonization)
Project WIKI pageO-RAN A1 Policies in ONAP & This Page
Prior Project "Base" Wiki

ONAP/3GPP & ORAN Alignment: A1 Adapter extensions (Guilin)

R8 A1 Adapter and Policy Management Extension (Honolulu)

Meetings Register & Recordings

ONAP/O-RAN-SC/SMO Meetings

Requirements Ticket

REQ-722 - Getting issue details... STATUS

Key Use Case Leads & Contacts

USE CASE LEAD:  John Keeney

OTHER KEY CONTACTS: Michela Bevilacqua Zu Qiang (Ericsson)

CCSDK Requirement/Epic

JIRA Ticket for Epic for A1 Policy Function Extensions in CCSDK Istanbul

CCSDK-3229 - Getting issue details... STATUS

ONAP Requirements
Subcommittee Review

Reviewed and approved by by Requirements Subcommittee 29 March 2021


Function/Integration
Test environment

Integration Tests


BUSINESS DRIVER


Executive Summary: 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.

Business Impact: Continuing the convergency between ONAP and ORAN for A1 interface to used by all service providers and avoid duplicate development efforts.

Business Markets: Enhanced A1 capabilities 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.

Key Contacts : John KeeneyMichela BevilacquaZu Qiang (Ericsson)


Development Status

PROJECTPTLUser Story / EpicRequirement
A&AI

William Reehil

N/A


AAF

Jonathan Gathman

N/A
APPC

Takamune Cho

N/A


CLAMP

Gervais-Martial Ngueko

N/A
CC-SDK

Dan Timoney

Extend existing A1 Adapter and A1 Policy Management functionality in CCSDK

CCSDK-3229 - Getting issue details... STATUS

DCAE

Vijay Venkatesh Kumar

N/A
DMaaP
Mandar Sawant
N/A
External API

Adrian OSullivan

N/A
HOLMES
Guangrong Fu
N/A
MODELING

Hui Deng

N/A

Multi-VIM / Cloud

Bin Yang

N/A
OOF

krishna moorthy

N/A
OOM

Sylvain Desbureaux

N/A
POLICY

Jim Hahn

N/A
PORTAL

Sunder Tattavarada

N/A
SDN-C
Dan Timoney

Extend existing A1 Adapter and A1 Policy Management functionality in SDNC deployments


SDC

Christophe Closset

N/A
SO

Seshu Kumar Mudiganti

N/A
VID

Ikram Ikramullah

N/A
VF-C

Yuanhong Deng

N/A
VNFRQTS
Steven Wright
N/A
VNF-SDK
Weitao Gao
N/A
CDS

Yuriy Malakov

N/A

List of PTLs: Approved Projects

*Each Requirement should be tracked by its own User Story in JIRA 

FEATURE USE-CASE DIAGRAM

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

Functional Architecture



Enhancements for Istanbul Release

  • O-RAN Alliance A1 Specification evolution (A1-AP & A1-TP)
  • A1 Policy State Management & Persistent Storage in A1 Policy Management Service
    • Support failover, restart, etc.
  • HTTP/HTTPS proxy support in A1 Adapter (A1 Southbound only)
  • Improved A1-REST response code transit through A1 Adapter
  • Support updated RESTCONF spec (RFC 8040 - used in ODL) between A1 Policy Management Service & A1 Adapter
  • Re-align OOM configuration for near-RT-RICs in A1 Policy Management Service config
  • Add more fine-grained near-RT-RIC in A1 Policy Management Service REST runtime config interface
  • Improved documentation & testing
  • A1 Policy Management participant for use in ONAP Control Loops (Stretch – TBC)
  • Support A1 Policy operations in SON usecases (RAN Slicing & PCI – TBC) (Stretch – TBC)

Use cases

Synchronize A1 Policy Information in RAN


A1 Policy Type / Instance Operations

A1 Policy Instance Status Operations

Other Impacts

Affected ONAP Functions:

  • SDNC / CCSDK only

Integration of bordering ONAP components:

  • Demonstrations with other Use cases, Components, PoCs
  • Integration with other use cases & functions (Stretch)

Interfaces:

  • 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 (See above)

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:

  • None

Other:

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

Use Case Functional Definitions

Use Case Title

A1 Policy Function Extensions (R9 Istanbul)

Actors (and System Components)

SDNC / CCSDK - A1 Adapter & A1 Policy Management Service

Description

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.

Points of Contact


John Keeney Michela Bevilacqua Zu Qiang (Ericsson)


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

TESTING

  • Test use-cases:

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

Current Status

  • None yet

End to End flow to be Tested

  • Currently being defined

Test Cases and Status

  • Currently being defined


  • No labels