Date
There was no meeting on 4/12..
Attendees
Agenda
- RAN-Sim changes
Notes
Item | Who | Notes |
---|---|---|
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 2/1 We are presenting SON Use Case in the Arch Comm meeting today 2/1 at 10:30am ET. M3 Update: We have reduced scope in SON Use case. Following have been removed from Jakarta We had a good discussion about overall objective of SON use case. ONAP use cases are primarily involved for functions in the SMO.
Also discussed email (forwarded to Niranjana Y ) from Michał Jagiełło to Malarvizhi Paramasivam about automation of test cases for SON use case. Changes are already made to https://wiki.onap.org/display/DW/Setup+details+-+Integration+test+for+SON+use+case+in+Istanbul 3/15: 3 new REQ 1128, 1129, 1130 for M4. | |
CCSDK-3532 | 12/09: Yashwanth clarified that he is working on one part of CCSDK-3532 - the DG in SDN-R which use the new yang model. 12/16: Good discussion on mapping of SDNR messages to O-RAN yang model and modification of the SDNR DGs. Details are document in Mapping netconf edits to O-RAN yang model 3/1: Changes to SDNR are ongoing. Changes are committed for edit-config change in SDNR Started making changes in RAN-Sim and re-use models (gnbsim) from Slicing use case and ensure it works for SON Use Case edit-config. 3/15 SDNR code changes committed and merged. | |
DCAEGEN2-2986 (PM VES formats) | 12/09 notes: 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 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 Note that the sample PM message uploaded in - DCAEGEN2-2986Getting issue details... STATUS 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 - DCAEGEN2-2986Getting issue details... STATUS 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). 12/16 notes: We are making progress on the PM VES message formats. Comments are tracked in and - VNFRQTS-1003Getting issue details... STATUS The child JIRA for VES has been moved under VNFRQTS project. At this time, we believe there is no impact on DCAE VES. Wipro team has said that they are not able to support
-
DCAEGEN2-2988Getting issue details...
STATUS
for Jakarta release. So this req (2988) is at risk for this release. 2/1 - We have reduced scope and modified requirements since DCAEGEN2-2988 cannot be supported for Jakarta. | |
A1 - based action | Good discussion on including A1-based action. Vishal Varvate is interested in contributing. He will work with John Keeney .
| |
RAN-Sim | 3/8 Further discussion on including netopeer in RAN-Sim. See slides 2-6 in ppt attached here. 3/30 Vishal presented slides below. We had a good discussion. Option 2 gives a little more flexibility for future use. John said they are willing to help with the A1 termination. |