4.1.3 Management deactivation

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

4.1.3.1 UTRAN deactivation mechanisms

When last Trace session is requested to be ended for an IMEI(SV) or a list of IMEI(SV), the RNC shall send the requested IMEI(SV)/list of IMEI(SV)s in ‘Uplink Information Exchange Request’ to the interacting MSC Server(s) and SGSN(s). The MSC Servers and SGSNs shall remove the requested IMEI(SV)s for the RNC in question.

4.1.3.2 PS Domain deactivation mechanisms

When a SGSN, GGSN or BM-SC receives a Trace Session Deactivation from its EM, the Trace Session identified by the Trace Reference, shall be deactivated in SGSN/GGSN/BM-SC.

If a Trace Recording Session is active at the time of receiving a Trace Session deactivation from the EM, the SGSN/GGSN/BM-SC may choose to continue the Trace Recording Session till it ends gracefully or may stop it immediately. In all cases, the SGSN/GGSN/BM-SC shall deactivate the requested Trace Session immediately at the end of the Trace Recording Session.

4.1.3.3 CS Domain deactivation mechanisms

When a MSC Server receives a Trace Session Deactivation from its EM, the Trace Session identified by the Trace Reference, shall be deactivated in MSC Server.

If a Trace Recording Session is active at the time of receiving a Trace Session deactivation from the EM, the MSC Server may choose to continue the Trace Recording Session till it ends gracefully or may stop it immediately. In all cases, the MSC Server shall deactivate the requested Trace Session immediately at the end of the Trace Recording Session.

4.1.3.4 IP Multimedia Subsystem deactivation mechanisms

When a S-CSCF/P-CSCF receives a Trace Session deactivation from the EM, the Trace Session identified by the Trace Reference, shall be deactivated.

If a Trace Recording Session is active at the time of receiving a Trace Session deactivation from the EM, the S-CSCF/P-CSCF may choose to continue the Trace Recording Session till it ends gracefully or may stop it immediately. In all cases, the S-CSCF/P-CSCF shall deactivate the requested Trace Session immediately at the end of the Trace Recording Session.

The following figure illustrates how the Trace Session is deactivated when a Trace Recording Session is going on (e.g. a SIP INVITE method is being traced in S-CSCF).

Figure 4.1.3.4.1: Trace session deactivation in IMS

4.1.3.5 E-UTRAN deactivation mechanisms

In E-UTRAN the Cell Traffic trace functionality can be deactivated when the eNodeB receives the Trace Session Deactivation message from the EM. At this time the eNodeB shall deactivate the Trace Session for those E-UTRAN Cells that have been indicated in the Trace Session Deactivation message received from the EM.

4.1.3.6 EPC Domain deactivation mechanisms

When a MME, SGW or PGW receives a Trace Session Deactivation from its EM, the Trace Session identified by the Trace Reference, shall be deactivated in the MME, SGW or PGW.

If a Trace Recording Session is active at the time of receiving a Trace Session deactivation from the EM, the MME may choose to continue the Trace Session and the Trace Recording Session till it ends gracefully or may stop it immediately. In all cases, the MME shall deactivate the requested Trace Session immediately at the end of the Trace Recording Session.

4.1.3.7 E-UTRAN deactivation mechanisms for MDT

When the eNodeB receives the indication from EM for MDT trace session deactivation, it shall deactivate the trace session for those E-UTRAN cells that have been indicated in the message. In case of immediate MDT trace session the eNodeB shall deactivate the corresponding MDT RRC measurements in the UEs that have been configured for immediate MDT as part of the given trace session.

4.1.3.8 Deactivation mechanisms at UE for MDT

The UE shall silently discard a logged MDT or Logged MBSFN MDT trace session when logging duration expires and shall indicate the availability of logged measurement results to the network next time it enters connected mode.

4.1.3.9 5GC Domain deactivation mechanisms

In 5GC the management trace deactivation utilizes the Services Based Management Architecture (SBMA) defined in TS 28.533 [48]. The NE Trace Control and Configuration parameters are removed via interaction between Provisioning MnS (see definitions in TS 28.532 [47]) consumer and Provisioning MnS producer. Figure 4.1.3.9-1 below illustrates the 5GC management deactivation where the role of a Provisioning MnS producer is played by the NE and the role of a Provisioning MnS consumer is played by the Management System.

Figure 4.1.3.9-1: Overview of management deactivation for 5GC

When an AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM receives a Trace Session Deactivation from its management system, the Trace Session identified by the Trace Reference, shall be deactivated in the AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM.

If a Trace Recording Session is active at the time of receiving a Trace Session deactivation from the management system, the AMF may choose to continue the Trace Session and the Trace Recording Session till it ends gracefully or may stop it immediately. In all cases, the AMF shall deactivate the requested Trace Session immediately at the end of the Trace Recording Session.

4.1.3.10 NG-RAN deactivation mechanisms

In NG-RAN the management trace deactivation utilizes the Services Based Management Architecture (SBMA) defined in TS 28.533 [48]. The Cell Traffic trace functionality can be deactivated when the NG-RAN node Trace Control and Configuration parameters are removed via interaction between Provisioning MnS (see definitions in TS 28.532 [47]) consumer and Provisioning MnS producer.. At this time the NG-RAN node shall deactivate the Trace Session for those NG-RAN Cells that have been indicated in the Trace Session Deactivation message received from the management system. Figure 4.1.3.10-1 below illustrates the NG-RAN management deactivation where the role of a Provisioning MnS producer is played by the NE and the role of a Provisioning MnS consumer is played by the Management System.

Figure 4.1.3.10-1: Overview of management deactivation for NG-RAN

4.1.3.11 NG-RAN deactivation mechanisms for MDT

When the gNB receives the indication from management system for MDT trace session deactivation, it shall deactivate the trace session for those NG-RAN cells that have been indicated in the message. In case of immediate MDT trace session, the gNB shall deactivate the corresponding MDT RRC measurements in the UEs that have been configured for immediate MDT as part of the given trace session.

In the case of split RAN architecture, If MDT trace session in gNB-CU-UP and/or gNB-DU has been activated by gNB-CU-CP, the responsible gNB-CU-CP shall deactivate the corresponding MDT trace sessions in gNB-CU-UP and/or gNB-DU.