(Copy this Page in the → ... → select COPY)
Use Case Overview & Description
(description of U/C)This requirement enhances the A1 interface capabilities provided in Rel 6 as part of 5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management. 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. Planned enhancements for Rel 8 include support of new A1 interface version in alignment to O-RAN alliance and common logging/audit.
Use Case Key Information
TOPIC | DESCRIPTION | WIKI PAGE |
Requirements Proposal | This is a link to the requirements proposal made on the Requirements Sub-committee | |
Architecture S/C info | Information on the Architecture sub-committee presentation | |
Prior Project "Base" Wiki | Link to the "base" wiki for the Use Case, or work from a prior release. | |
Requirements Jira (REQ-###) Ticket | Link to the REQ Jira ticket for this use case | |
Key Use Case Leads & Contacts | USE CASE LEAD: @xyz USE KEY CONTACTS: | |
Meetings Register & Recordings | Link to Use Case Team meetings. |
...
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 Keeney, Michela Bevilacqua
Executive Summary - (Give a short description of your Use Case, the "Executive 2 min elevator pitch", this describes the "WHAT")
Business Impact - (This is the Business Impact which describes why this use case is important from a business perspective, this describes the "WHY").
Business Markets - (This is the marketing analysis, which can include but not limited to applicable markets, domains, marketing projections, this can describe the "WHERE").
Funding/Financial Impacts - (The Funding requirements and Financial impacts can describe the financial savings, or CAPEX, OPEX impacts for a Use Case): This requirement enhances the A1 interface capabilities provided in Rel 6 as part of 5G/ORAN & 3GPP Standards Harmonization requirement ( REQ-38) and extended in Rel 7 with the introduction of A1 policy management. 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. Planned enhancements for Rel 8 include support of new A1 interface version in alignment to O-RAN alliance and common logging/audit.
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, once developed, will be useable 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- (It is suggested that you use the following wording):: 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. (This would typically describe the "WHO", but because use cases are all deployed with ONAP itself, these two areas come with the actual ONAP deployment and uses the organizational management and sales strategies of a particular service provider's ONAP deployment)
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 |
...