Homepage / Wiki
Use Case Name
...
| TOPIC | Information | ||||||||||
| Requirements Proposal | A1 Policy Function Extensions (ORAN/ONAP/3GPP Harmonization) | ||||||||||
| Project WIKI page | O-RAN A1 Policies in ONAP & This Page | ||||||||||
| Prior Project "Base" Wiki | |||||||||||
| Meetings Register & Recordings | |||||||||||
| Requirements Ticket |
| ||||||||||
| Key Use Case Leads & Contacts | USE CASE LEAD: John Keeney (Ericsson EST) USE OTHER KEY CONTACTS: Michela Bevilacqua Zu Qiang | ||||||||||
| CCSDK Requirement/Epic | JIRA Ticket for Epic for A1 Policy Function Extensions in CCSDK Istanbul
| ||||||||||
| ONAP Requirements Subcommittee Review | Reviewed and approved by by Requirements Subcommittee 29 March 2021
| ||||||||||
| Function/Integration Test environment | |||||||||||
Integration Tests |
...
Key Contacts : John Keeney (Ericsson EST)Michela BevilacquaZu Qiang
Development Status
...
- 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
- RFC 8040 : https://tools.ietf.org/html/rfc8040
- Older RESTCONF (https://tools.ietf.org/html/draft-bierman-netconf-restconf-02) being phased out.
- 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
...
Use Case Title | |
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 | |
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