Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Use Case Name

Use Case Overview & 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 ( REQ-38 - Getting issue details... STATUS ) and Rel 7 - Guilin ( REQ-352 - Getting issue details... STATUS ). 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 Key Information

TOPICInformation
Requirements Proposal
Architecture S/C info


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

REQ-457 - Getting issue details... STATUS

Key Use Case Leads & Contacts

USE CASE LEAD:  John Keeney (Ericsson EST)

USE KEY CONTACTS: Michela Bevilacqua

Meetings Register & Recordings

ONAP/O-RAN-SC/SMO Meetings

BUSINESS DRIVER

This section describes Business Drivers needs. These business drivers are presented on the Requirements Sub-committee and should also be put into the release requirements sub-committee page.

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 - Getting issue details... STATUS ) and Rel 7 - Guilin ( REQ-352 - Getting issue details... STATUS ). 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.

Development Status

List of PTLs: Approved Projects

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

USE CASE DIAGRAM

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

O-RAN A1 Policy Functions

Use Case Functional Definitions

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 ( REQ-38 - Getting issue details... STATUS ) and Rel 7 - Guilin ( REQ-352 - Getting issue details... STATUS ). 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.


Points of Contact


John Keeney (Ericsson EST) 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

TESTING

  • Currently being defined

Current Status

  • None yet

End to End flow to be Tested

  • Currently being defined

Test Cases and Status

  • Currently being defined

  • No labels