7 Trace reporting

32.4223GPPRelease 17Subscriber and equipment traceTelecommunication managementTrace control and configuration managementTS

7.1 Single operator case

7.1.1 File-based trace reporting in single operator case

The traced data is recorded in the NE (e.g. RNC, SGSN, eNB, MME, NG-RAN node, AMF). The recorded data is saved to a Trace file. The Trace files are sent to the TCE

1) either directly, or

2) via the NE’s management system.

Alternative 1 may be used when supported by implementation and when the operator has no issue to set up and maintain direct connections between the NE and the TCE.
Alternative 2 may be used when supported by implementation and the operator wants to reuse the already set up and maintained connection between the NE and the management system for transport of the trace files to the TCE.

Figure 7.1.1-1 illustrates an example of the procedure for transferring the Trace Record from the NE to the TCE for alternative 1.

Figure 7.1.1-1 Direct transfer to the TCE

Figure 7.1.1-2 illustrates an example of the procedure for transferring the Trace file from the NE to the TCE for alternative 2.

Figure 7.1-2 Transfer to the TCE via management system

The time and the criteria when the Trace files are sent to the TCE is vendor specific.

7.1.2 Streaming trace reporting in single operator case

The traced data is captured in the NE (e.g. NG-RAN node, AMF). The captured trace data is streamed to the Trace Reporting MnS consumer (see TS 28.532 [x2])

1) either directly (NE plays the role of the Trace Reporting MnS producer), or

2) via the intermediate management function(s) (playing the roles of Trace Reporting MnS producers and/or consumers).

Alternative 1 may be used when supported by implementation and when the operator has no issue to set up and maintain direct connections between the NE and the Trace Reporting MnS consumer.

Alternative 2 may be used when supported by implementation and the operator wants to reuse the already set up and maintained connection between the NE and the management functions for streaming of the trace data to the Trace Reporting MnS consumer.

Figure 7.1.2-1 illustrates an example of the procedure for streaming the Trace Record from the NE to the Trace Reporting MnS consumer for alternative 1.

Figure 7.1.2-1 Direct streaming to the Trace Reporting MnS consumer

Figure 7.1.2-2 illustrates an example of the procedure for transferring the Trace Record from the NE to the Trace Reporting MnS consumer for alternative 2.

Figure 7.1.2-2 Indirect streaming to the Trace Reporting MnS consumer

7.2 Shared network case for Participating Operator

7.2.1 File-based trace reporting in shared network case for Participating Operator

The traced data for a Participating Operator are recorded in the NE (e.g. RNC, SGSN, eNB, MME, NG-RAN node, AMF). The recorded data is saved to a Trace file. The Trace files are sent to the TCE:

1) either directly from the Master Operator’s NE to the Participating Operator’s TCE, or

2) from the Master Operator’s NE’s via the Master Operator’s management system to the Participating Operator’s management system. The connection between the two operators may be a secure connection that is used for other (management) purposes. The secure connection is outside the scope of this specification.

Alternative 1 illustrated in Figure 7.2.1-1 may be used when supported by the implementation and when both operators have no issue to set up and maintain direct connections between the NE and the TCE.
Alternative 2 illustrated in Figure 7.2.1-2 may be used when supported by the implementation and both operators want to reuse the already set up and maintained connection between the Master Operator management system and the Participating Operation management system.

Figure 7.2-1 Transfer from the Master Operator NE to the Participating Operator’s TCE

Figure 7.2-2 Transfer from the Master Operator management system to the Participating Operator

The connection between the operators may be secured. How that is done is outside the scope of this specification.

The time and the criteria when the Trace files are sent to the TCE is vendor specific.

7.2.2 Streaming trace reporting in shared network case for Participating Operator

The traced data is captured in the NE (e.g. NG-RAN node, AMF). The captured trace data is streamed to the Trace Reporting MnS consumer (see TS 28.532 [47]):

1) either directly from the Master Operator’s NE to the Master Operator’s EGMF (see TS 28.533 [48]) and then to the Participating Operator’s Trace Reporting MnS consumer, or

2) from the Master Operator’s NE’s via the Master Operator’s intermediate management function(s) (playing the roles of Trace Reporting MnS producers and/or consumers) to the Master Operator’s EGMF and then to the Participating Operator’s Trace Reporting MnS consumer. The connection between the two operators may be a secure connection that is used for other (management) purposes. The secure connection is outside the scope of this specification.

Alternative 1 illustrated in Figure 7.2.2-1 may be used when supported by the implementation and when Master Operator has no issue to set up and maintain direct connections between the NE and the EGMF.

Figure 7.2.2-1 Direct streaming to the EGMF with exposure to the Trace Reporting MnS consumer of Participating Operator

Alternative 2 illustrated in Figure 7.2.2-2 may be used when supported by the implementation and when Master Operator wants to reuse the already set up and maintained connection between between the NE and the management functions for streaming of the trace data to the EGMF.

Figure 7.2.2-2 Indirect streaming to the EGMF with exposure to the Trace Reporting MnS consumer of Participating Operator