Use Case Name
...
Use Case Key Information
| TOPIC | Information | |||||||||||
| Requirements Proposal | ArchitectureRequirements S/C | infoProposal: A1 Adapter and Policy Management Extension (ORAN/ONAP/3GPP Harmonization) | ||||||||||
| Project WIKI page | O-RAN A1 Policies in ONAP & This Page | |||||||||||
| Prior Project "Base" Wiki | ONAP/3GPP & ORAN Alignment: A1 Adapter extensions (Guilin) | |||||||||||
| Meetings Register & Recordings | ||||||||||||
| Requirements | Requirements Jira (REQ-###)Ticket |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: John Keeney USE KEY CONTACTS: Michela Bevilacqua | |||||||||||
| Meetings Register & Recordings |
BUSINESS DRIVER
...
| CCSDK Requirement/Epic | JIRA Ticket for Epic for A1 Policy Management in Honolulu
| ||||||||||||||||||||||
| ONAP Arch Committee Review | JIRA Ticket for Review in ArchCom
2020-12-01 ONAP Architecture Subcommittee Meeting - Approved Recording:
Slides:
| ||||||||||||||||||||||
| Function/Integration Test environment | Demo of OSC NONRTRIC & ONAP A1 functions at LFN Developer & Testing Forum - Feb 2021 Slides & Video: 2021-02-03 - ONAP: Demo: O-RAN A1 Policy & Non-RealTime-RIC automated test/demo environment | ||||||||||||||||||||||
| Integration Tests | JIRA Ticket for Epic for Integration Tests
|
BUSINESS DRIVER
Key Contacts : John Keeney, Michela Bevilacqua
...
| PROJECT | PTL | User Story / Epic | Requirement |
| A&AI | N/A | ||
| AAF | N/A | ||
| APPC | N/A | ||
| CLAMP | N/A | ||
| CC-SDK | Extend existing A1 Adapter and A1 Policy Management functionality in CCSDK | CCSDK-2991 | |
| DCAE | N/A | ||
| DMaaP | N/A | ||
| External API | N/A | ||
| HOLMES | N/A | ||
| MODELING | N/A | ||
Multi-VIM / Cloud | N/A | ||
| OOF | N/A | ||
| OOM | N/A | ||
| POLICY | N/A | ||
| PORTAL | N/A | ||
| SDN-C | Extend existing A1 Adapter and A1 Policy Management functionality in SDNC deployments | ||
| SDC | N/A | ||
| SO | N/A | ||
| VID | N/A | ||
| VF-C | N/A | ||
| VNFRQTS | N/A | ||
| VNF-SDK | N/A | ||
| CDS | N/A |
...
Use cases define how different users interact with a system under design.
Enhancements for Honolulu Release
- Add support for O-RAN Alliance A1-AP v2.0 1 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 manipulation 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
A1 Policy Type / Instance Operations
A1 Policy Instance Status Operations
Other Impacts
...
Interfaces:
- Northbound Interface – See earlier section
- Add/Change SDNC CCSDK A1 Policy Management Service NBI for A1 Policy Management (REST & DMaaP)
- The new version of the PMS REST API complies with the ONAP REST API and Zalando style guidelines and fixes some naming inconsistencies.
- REST (New version)
- DMaaP (New version)
- Ref: CCSDK-3077
- 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 1 (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
...
- 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
Use Case Title | |
Actors (and System Components) | SDNC / CCSDK - A1 Adapter & A1 Policy Management Service |
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) 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. |
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
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
...