Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

DCAE impacts for 5G OOF SON use case in Jakarta release

Description

This epic is for enhancements related to 5G OOF SON use case in Jakarta release for the SON-Handler MS.

  1. Development of PM/FM/CM VES message formats which are aligned with O-RAN O1

  2. Modifications of SON-Handler MS to work with updated PM/FM message formats
    (This has been removed from scope. We have a dependency on RANSim enhancements)

  3. Check if any changes needed in VES Collector

Attachments

3
  • 02 Dec 2021, 12:31 PM
  • 02 Dec 2021, 12:31 PM
  • 02 Dec 2021, 12:31 PM
100% Done
0

Confluence content

mentioned on

Activity

Show:

Former user March 23, 2022 at 9:12 PM

 - As there was no changes required for J release, can this EPIC fixVersion be moved to Kohn release (i.e assuming there is code impact)? 

Former user March 23, 2022 at 4:22 PM
Edited

Former user December 13, 2021 at 9:11 PM

Note: DCAE PTL Vijay moved the child Jira from DCAEGEN2-2987 to VNFRQTS-1003. It is the same Jira but it is under the VES Req project now.

Former user December 9, 2021 at 11:08 PM

 - The schema-map within VESCollector can be overriden at deployment. Pls see here external-repository-schema-files-integration-with-ves-collector for details.  

From a quick glance on references provided, it appears there would be no VES specification change required for this usecase (as you are using existing VES domains) and overridding the default stndDefined domain schemas with Rel-17 draft versions. Could you confirm if my understanding is correct?

And if we need to switch default schemas to the latest in ONAP, changes will be required for VESCollector and OOM configmaps (possibly also OOM Utils repository if any OpenAPI schema issues need to be handled)

Former user December 9, 2021 at 6:33 PM
Edited

Link from Alex: 
See example of stndDefined PM message in OSC pasted below and copied from here:
https://wiki.o-ran-sc.org/display/SIM/Network+Slicing+Use+Case#NetworkSlicingUseCase-ExampleVESPMstndDefined 

 

[2021-12-08|17:26:10|http_client.c:103] POST-ing cURL to url="https://10.20.11.121:8443/eventListener/v7" with body="{ "event": { "commonEventHeader": { "domain": "stndDefined", "eventId": "pm1_1638984365", "eventName": "stndDefined_performanceMeasurementStreaming", "eventType": "performanceMeasurementStreaming", "sequence": 24, "priority": "Low", "reportingEntityId": "", "reportingEntityName": "O-RAN-O-DU-1", "sourceId": "", "sourceName": "O-RAN-O-DU-1", "startEpochMicrosec": 1638984365000000, "lastEpochMicrosec": 1638984370000000, "nfNamingCode": "SIM-O-DU", "nfVendorName": "O-RAN-SC SIM Project", "stndDefinedNamespace": "o-ran-sc-du-hello-world-pm-streaming-oas3", "timeZoneOffset": "+00:00", "version": "4.1", "vesEventListenerVersion": "7.2.1" }, "stndDefinedFields": { "stndDefinedFieldsVersion": "1.0", "schemaReference": "https://gerrit.o-ran-sc.org/r/gitweb?p=scp/oam/modeling.git;a=blob_plain;f=data-model/oas3/experimental/o-ran-sc-du-hello-world-pm-streaming-oas3.yaml", "data": { "id": "pm1_1638984365", "start-time": "2021-12-08T17:26:05.0Z", "administrative-state": "unlocked", "operational-state": "enabled", "user-label": "pm-1", "job-tag": "", "granularity-period": 5, "measurements": [{"measurement-type-instance-reference": "/o-ran-sc-du-hello-world:network-function/distributed-unit-functions[id='O-DU-1211']/cell[id='cell-1']/supported-measurements[performance-measurement-type='user-equipment-average-throughput-downlink']","value": 12355,"unit": "kbit/s"} ] } } } }"

The schema refers to a hello world yang model which is here:

https://gerrit.o-ran-sc.org/r/gitweb?p=scp/oam/modeling.git;a=blob;f=data-model/yang/working/o-ran-sc/o-ran-du/o-ran-sc-du-hello-world.yang 

 

The VES message uses a measurement type user-equipment-average-throughput-downlink which is mentioned in the hello-world yang model.

This metric needs to be combined/harmonized with the KPI table developed in WG-10 which is here:
https://oranalliance.atlassian.net/wiki/download/attachments/1608515800/PM-Counter-and-KPI-Repository.xlsx?api=v2 

This is part of the PM Coordination work in O-RAN
https://oranalliance.atlassian.net/wiki/spaces/OAMWG/pages/2227307301/PM+Coordination+Team 

Done

Details

Assignee

Reporter

Components

Fix versions

Priority

Epic Name

Created November 23, 2021 at 2:12 PM
Updated September 20, 2022 at 11:35 AM
Resolved May 10, 2022 at 8:52 AM

Flag notifications