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 (
) and Rel 7 - Guilin (Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-38
). A1 Adapter functionality was introduced in Frankfurt. In Guilin The A1 adapter was improved and a A1 Policy Management Service was added. Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key REQ-352
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
| TOPIC | Information | ||||||||||
| Requirements Proposal | |||||||||||
| Architecture S/C info | |||||||||||
| Prior Project "Base" Wiki | ONAP/3GPP & ORAN Alignment: A1 Adapter extensions (Guilin) | ||||||||||
| Requirements Jira (REQ-###) Ticket |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: John Keeney USE KEY CONTACTS: Michela Bevilacqua | ||||||||||
| Meetings Register & Recordings |
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.
...
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
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | |||
| AAF | |||
| APPC | |||
| CLAMP | |||
| CC-SDK | |||
| DCAE | |||
| DMaaP | |||
| External API | |||
| HOLMES | |||
| MODELING | |||
Multi-VIM / Cloud | |||
| OOF | |||
| OOM | |||
| POLICY | |||
| PORTAL | |||
| SDN-C | |||
| SDC | |||
| SO | |||
| VID | |||
| VF-C | |||
| VNFRQTS | |||
| VNF-SDK | |||
| CDS |
...
*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.
Use Case Functional Definitions
Use Case Title | |||||||||||||||||||
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 ( 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 | |||||||||||||||||||
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