...
- Streaming Call trace is being discussed in standards. It likely requires a different kind of interface to ONAP. Call Trace and Vendor extensions to call trace are very important to O-RAN Suppliers as a mechanism to get input to the Non-RT RIC. SA5 plans to complete specification in Release 16. Aligns well with G Release.
O-RAN A-1 Interface Support in ONAP:
ONAP needs to review work of O-RAN teams on A-1 Definition. Document to be available in September. Frankfurt release must at minimum architect the incorporation of the interface into ONAP and prototype.
Recommendations on Prioritization:
Recommendations on prioritization
1.a Update existing VES events so NF providers have up to date information
1.b Equally important to 1a add support for A-1 interface
Introduce simple missing functionality
Plan Use Case Discussions for more complicated scenarios like CM changes and SW Update to work through where components should change.
Development Status
Project | PTL | JIRA Epic / User Story* | Requirements |
---|---|---|---|
AAI |
| ||
APPC | Takamune Cho |
| |
CLAMP |
| ||
OOF | |||
Policy |
| ||
SDC | |||
SDNC | |||
SO | |||
VID | |||
VNFRQTS |
...