D.1 Performance data streaming for starting measurement collection

28.5503GPPManagement and orchestrationPerformance assuranceRelease 18TS

D.1.1 Sequence flow

This annex shows the holistic sequence for performance data streaming, starting from starting the measurement collection (by job or configuration) to sending the performance data to the performance data streaming consumer (stream target).

Figure D.1.1-1

1. The consumer of MnS for measurement control requests the MnS producer to start the measurement collection by the following two alternatives:

1) by the measurement job control service

1a. The MnS consumer invokes the createMeasurementJob operation towards the MnS producer;

2) by the configurable measurement control service (a.k.a, NRM fragment-based measurement control service).

1b. The MnS consumer creates a new PerfMetricJob MOI, by invoking the createMOI operation towards the MnS producer; or

1c. The MnS consumer modifies an existing PerfMetricJob MOI to add new measurements to be collected, by invoking the modifyMOIAttributes operation towards the MnS producer.

2. The producer of MnS for measurement control configures the NF to collect the measurements. The mechanism of this step is vendor specific. If producer of MnS for measurement control is in the NF, this step can be skipped.

3. The NF triggers the producer of MnS for performance data streaming to set up the streaming information for the new measurements to be collected. The mechanism of this step is vendor specific. If producer of MnS for performance data streaming is in the NF, this step can be skipped.

4. The producer of MnS for performance data streaming communicates with the consumer to:

4a. establish the streaming (WebSocket) connection containing the stream information if it does not exist yet, by invoking the establishStreamingConnection operation;

4b. add the stream information for the new measurements if they will be reported by new streams, by invoking the addStreamInfo operation;

4c. update the stream information for the new measurements if they will be reported by existing streams, by invoking the updateStreamInfo operation.

5. The NF collects the measurements. This step is the internal behaviour of the NF.

6. The NF report the collected measurements to the producer of MnS for performance data streaming. The mechanism of this step is vendor specific. If producer of MnS for performance data streaming is in the NF, this step can be skipped.

7. The producer of MnS for performance data streaming sends the collected measurements to the consumer via performance data streams, by invoking the reportStreamData operation.

D.1.2 PlantUML codes

@startuml

skinparam shadowing false

skinparam monochrome true

hide footbox

participant "Consumer of MnS for\n measurement control" as MC

participant "Producer of MnS for\n measurement control" as MP

participant "NF" as NF

participant "Producer of MnS for\n performance data streaming" as SP

participant "Consumer of MnS for\n performance data streaming" as SC

alt Measurement job control service

else configurable measurement control service (i.e., NRM fragment based MnS)

alt create new MOI for collecting measurements

MC -> MP : 1b. createMOI\n(for PerfMetricJob IOC)

Else update existing MOI for collecting new measurements

MC -> MP : 1c. modifyMOIAttributes\n(for PerfMetricJob MOI) end

end

MP –> NF: 2. Configure measurement\n collection (proprietory)

activate NF

NF –> SP: 3. Set up streaming information\n for new measurements (proprietory)

alt No streaming(WebSocket) connection exists

SP->SC: 4a. establishStreamingConnection()

else Streaming (WebSocket) connection exists

alt add new stream(s)

SP->SC: 4b. addStreamInfo()

else update existing stream(s)

SP->SC: 4c. updateStreamInfo()

end

end

Loop while measurement collection\n is active

NF->NF: 5. Collect measurements

NF –> SP: 6. Report measurements\n (proprietory)

SP -> SC: 7. reportStreamData()

end

@enduml