2021-09-13 Meeting notes

Owned by N.K. Shankaranarayanan
Last updated: Sept 13, 2021
3 min read

Date

Sep 13, 2021

Attendees

  • @N.K. Shankaranarayanan

  • @krishna moorthy

  • @Martin Skorupski 

  • @Niranjana Y 

  • @Goutam Roy 

  • @Timo Perala 



Agenda

Istanbul Release M4

Planning for Jakarta Release

PoC Implementation questions



Notes

Item

Who

Notes

Item

Who

Notes

Meetings

All

8/9: SON use case weekly calls moved to Mondays as discussed:

https://lists.onap.org/g/onap-meetings/viewevent?repeatid=32219&eventid=1236181&calstart=2021-08-09
Will keep it short to 25 minutes on days when we have Use Case call at 9am EDT (alternate weeks)

8/30: Note that there was no call on 8/23 since we presented "Role of A1 and O1 in SON" in the Use Case Req. call.

Meeting link: Use Case Realization Call: Aug 23, 2021

Slides: https://lf-onap.atlassian.net/wiki/download/attachments/16481849/ONAP_SON_O1_A1_20210823.pptx?version=1&modificationDate=1629738791000&api=v2

9/13: Note that there was no call on 9/6 due to national holiday in US 

SDNR and CPS

Sandeep

7/30:
Proposal for SDNR work to have flexibility in using old and new apis for ConfigDB/CPS DB.
Consensus that this approach makes sense.

https://jira.onap.org/browse/CCSDK-3401
 
https://gerrit.onap.org/r/c/ccsdk/distribution/+/122981

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/13: Shankar to follow up with Sandeep

Yang models



Discussion on primary and secondary yang models. Idea continues to be "right" approach. 

On topic of geolocation of DU/RU:

  1. location of RU is needed for some use cases.

  2. If DU is cloud based, then location of DU is less critical.

  3. IETF/3GPP have location property for ManagedFunction.

  4. O-RAN O1 yang model does not have RU, only have DU.

  5. Options:

    1. Add location to secondary model for DU. Assume DU/RU are co-located in integrated GNB

    2. Include RU in secondary model in "simple" manner for PoC and inherit ManagedFunction to bring in location.

    3. Align with OR-RAN WG4 and use both O1 and FH yang models as primary - makes sense if use cases need to address RU.

PM message

All

7/30
PM message format options. Slicing use case uses the file-based approach. Intent is to
leverage commonality among use cases. Will follow up with Ahila.

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:

2021-08-25 Meeting notes (ONAP/O-RAN-SC/SMO - Meeting) - Agenda

Zipped file with slides and the sample CM/FM/PM message formats: (see 8/25 notes for files)

This topic for PM Streaming was also covered in the input to Req. Call re. ONAP/ORAN Harmonization. See above ppt.

9/13:
Tentative plan to have Jakarat Release feature to use a PM Streaming format which is aligned with O-RAN O1

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.

9/13: Release J to adopt latest CM, FM messages aligned to O-RAN O1.

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

Slides: https://lf-onap.atlassian.net/wiki/download/attachments/16481849/ONAP_SON_O1_A1_20210823.pptx?version=1&modificationDate=1629738791000&api=v2 

M3/M4



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.

9/13: Shankar and Krishna to work on M4 items offline

Rel J features/requirements



9/13:

Pursue alignment, synergy with O-RAN and OSC

Use a PM Streaming format which is aligned with O-RAN O1

Update CM, FM formats

Pursue joint testbed showing coordianated role of O1 and A1 interfaces 

Action items