...
Status of CM Update
Notes
| Item | Who | Notes | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Meetings | AllMeeting Time | SON use case weekly calls moved to Thursdays as discussed: https://lists.onap.org/g/onap-meetings/viewevent?repeatid=32219&eventid=1290763&calstart=2021-10-21 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SDNR and CPSSandeep | 7/30: https://jira.onap.org/browse/CCSDK-3401 8/30 : Sandeep reported that there are some challenges in SDRN/CPS work. These are not hard REQ and so no impact to M3. 9/27 - Sent email to Sandeep asking for meeting to plan leftover JIRA items for J release. Presentation of CM Notify Use Case is relevant. See https://wiki.o-ran-sc.org/pages/viewpage.action?pageId=41453037 for use of new O1-aligned CM VES message format. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Yang models | Discussion on primary and secondary yang models. Idea continues to be "right" approach. On topic of geolocation of DU/RU:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PM message | All | 7/30 8/30 We have proposal to add JSON VES as option for PM Streaming. Also pointing out that we need convergence on best option for PM Streaming for SON. This topic was first presented in the Wed ONAP/O-RAN Harmonization call: Zipped file with slides and the sample CM/FM/PM message formats: This topic for PM Streaming was also covered in the input to Req. Call re. ONAP/ORAN Harmonization. See above ppt. 9/27: Discussed requirement to use PM Streaming 10/21: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CM/FM message | 8/16 Please see email chain about CM format. SON use case can change formats since it is generated from RAN-Sim. Need to ensure that DCAE VES collector can support the O1-aligned CM message. 8/30 No new discussion 9/27 - Use new message formats in J release | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| A1 and O1 | 8/9 Would like to have coordination of actions over A-1 and O-1. Question. How can ONAP components can invoke and use A-1 Adapter. DMaaP message on A1-P topic did not work with work done for Slicing use case. Follow up with Dan Timoney about how components in ONAP can talk to A-1 adapter. 8/16 Shankar presented factors involved in determining role of A1 in ONAP-SON use case. Good discussion. ONAP-SON use case has done a lot of work with O1 interface. We are discussing what is the right way to add A1 interface. Important to identify the SON function which is suitable for A1 (assuming some abstraction of A1-xApp-E2 flow). Current thoughts around handoff and neighbor relations as it relates to our work in PCI and ANR. 8/30: Note that we presented "Role of A1 and O1 in SON" in the Use Case Req. call. Meeting link: Use Case Realization Call: Aug 23, 2021 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| M3/M4RC 8/16 Ongoing: Functional testing going on for RAN-Sim. Switching to VES 7.2 Ongoing: Migration from ConfigDB to CPS for SON-Handler. Need to finalize xPath templates. 8/30: M3 was delayed by one week. SON Use case status looks good. Main REQ
M4 JIRAs created
| M4 is done. Integration testing underway 10/14 RC work complete. Jiras updated. |