Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Attendees

Agenda

Role of RAN Simulator (RAN-Sim) in SON Use Case

Problem Statement: Honeycomb netconf server used in RAN-Sim project has been archived

Use Case with A1 adapter and PM kpis want to include O1

Description of OSC sim project


...

Agenda

Jakarta Requirements -

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-3532

Jakarta Requirements

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2986


Notes

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 
ItemWhoNotesMeeting Time



Jakarata Release 

11/08 - SON Use Case Jakarata plan presented in Requirements Subcommittee on 11/08/20201 call

Jakarta release - functional requirements proposed list#5GOOFSONUseCase 


Yang models

11/15 - Ideas on primary and secondary yang models for O1 and Use Case (ONAP, SMO) uploaded as a contribution to O-RAN WG2.

File: STL-AO-2021-11-15-WG2-C-ONAP-ORAN-Harmonization-O1-Input.pptx CCSDK-3532

Yashwanth clarified that he is working on one part of CCSDK-3532 - the DG in SDN-R which use the new yang model.
Created a separate JIRA

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyCCSDK-3544
as a task in CCSDK-3532

DCAEGEN2-2986
(PM VES formats)

Discussion focused on PM VES messages. Thanks to information from Martin and Alex.

There is very relevant work in O-RAN WG10. 

See https://oranalliance.atlassian.net/wiki/spaces/OAMWG/pages/2227307301/PM+Coordination+Team 

In particular, see the Excel table with a list of PM metrics relevant to O-RAN FCAPS

https://oranalliance.atlassian.net/wiki/download/attachments/

2216853530STLAO202111-15-WG2-C-ONAP-ORAN-Harmonization-O1-Input.pptx 
RANSim

Slides discussed during the meeting (with some added material from discussion)

ONAP_OOF_SON_R10_Requirements_2021117_v1.1.pptx

Recording of zoom call: 

SON_usecase_call_20211118.mp4

See slides for:

  • Role of RAN Simulator (RAN-Sim) in SON Use Case
  • Problem Statement: Honeycomb netconf server used in RAN-Sim project has been archived
  • Use Case with A1 adapter and PM kpis want to include O1
  • Description of OSC sim project
  • Discussion on RAN-Sim and OSC sim - comparison, and options for harmonization

SON Use Case and Slicing Use Case rely on RAN-Sim which used Honeycomb netconf servers.

Honeycomb project has been archived. May impact upgrades and fixes.

As we think of options, it is good to harmonize with O-RAN OSC sim project.

https://wiki.o-ran-sc.org/display/SIM/Architecture

and also work in ONAP and OSC for A1

https://wiki.onap.org/pages/viewpage.action?pageId=84672221
 
 Next steps: Evaluate work needed to use netopeer instead of Honeycomb in RAN-Sim, and harmonize two sims

There is consensus in ONAP/OSC/O-RAN to use VES stndDefined domain.

We believe that this will be acceptable to 3GPP and O-RAN. stndDefined domain
requires a schema.

Note that the sample PM message uploaded in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2986
does not have a schema and is thus incomplete.

Note that OSC smo project is using VES measurement domain now but wants to move to stndDefined.

Lot of detail about PM metrics and schema have been added in comments in

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-2986
 

There are two approaches to provide a reference to the metrics to the systems processing the PM VES message:

1) Current OSC approach: VES message refers to schema and yang model which points to the measurements in the VES message

payload

2) Current ONAP approach: VES message assumes that a PM Dictionary is loaded  initially and this provides a reference for the

measurements in the VES payload. This is supported by the ONAP VES Collector.

In either case, there is more work needed to align with the PM metrics being defined in O-RAN WG10 (based on 3GPP).