Page History

Scope

This page discusses the possibilities for PM streaming. In D-Release a use case and effort driven PM streaming of non-standardized VES message  was implemented.

Forward looking a (more) standardized way of PM streaming should be evaluated.

O-RAN OAM Interface Specification

The O-RAN Operation and Maintenance Interface Specification v10.00 from June 2023 refers  in chapter 6.3.2 Performance Data Streaming to the websocket protocol based on the requirements documented in 3GPP TS 28.550 v17.1.0 clause 5.2.3. With respect to the data model the specification references 3GPP TS 28.532  v17.3.0 clause 11.5.1.1.2. 

Idea

• Data Model
  • SerializationFormat : GPB ( > /[Google] Protocol Buffers ) 
  • yang to GPB (https://en.wikipedia.org/wiki/Protocol_Buffers)
  • 3GPP-xml > yang > GPB
    • (fallback for O-DU (if needed) 3GPP-xml → yang → JSON → VES-stndDefined)

file-based

• file ready
• filtered message based on the rApp Subscription 

Info: xml to sTree s3 and kafka for control

• Flow 
  • MNS (SMO) - does the subscription on the node
    • node starts streaming
    • messages to SMO as GPB
      • GPB termination
        •  <here the magic happens>
        • → send json to kafka

AI Martin Skorupski 

• description and explain PM- job
• show example of the GPB data format

• Protocol
  • HTTP2
  • websocket

References

• https://github.com/openconfig/ygot/blob/master/docs/yang-to-protobuf-transformations-spec.md
• gRPC → combines transport protocol HTTP2 with data format "Protocol Buffer" for serialize data
• https://datatracker.ietf.org/meeting/101/materials/slides-101-netconf-grpc-network-management-interface-gnmi-00
• https://datatracker.ietf.org/doc/html/draft-openconfig-rtgwg-gnmi-spec-01