4.2.4 Stopping a trace recording session – management based

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

4.2.4.1 UTRAN stopping mechanisms

The Trace Recording Session in the RNC shall be stopped when the last connection, which belongs to the traced subscriber/mobile, is released.

4.2.4.2 PS Domain stopping mechanisms

In SGSN, GGSN and BM-SC a Trace Recording Session shall be stopped when any of the defined stop triggering events occur. If Trace Session deactivation is received during the Trace Recording Session, the SGSN is allowed to finish tracing of the on-going procedures (e.g. session). In this case the Trace Recording Session shall be stopped between the reception of the Trace Session deactivation and the appropriate stop-triggering event.

The following figure illustrates the successful case in tracing a PDP context when a Trace Recording Session is stopped.

Figure 4.2.4.2.1: Stopping a Trace Recording Session for a PDP Context (Management Based) – PS domain

The following figure illustrates the successful case in tracing a MBMS context when a Trace Recording Session is stopped.

Figure 4.2.4.2.2: Stopping a Trace Recording Session for a MBMS Context (Management Based) – PS domain

4.2.4.3 CS Domain stopping mechanisms

In MSC Server a Trace Recording Session shall be stopped when any of the defined stop triggering events occur. If Trace Session deactivation is received during the Trace Recording Session, the MSC Server is allowed to finish tracing of the on-going procedures (e.g. calls). In this case the Trace Recording Session shall be stopped in MSC Server between the reception of the Trace Session deactivation and the appropriate stop-triggering event.

The following figure illustrates the successful case in tracing a call and the time of stopping a Trace Recording Session.

Figure 4.2.4.3.1: Stopping a Trace Recording Session (Management Based) – CS domain

4.2.4.4 Void

4.2.4.5 E-UTRAN stopping mechanisms

The Trace Recording Session in the eNodeB shall be stopped when the call/session is ended in the cell under trace or the call/session is haneded over to another cell. If the Trace Session is deactivated at a time when there are ongoing sessions the trace recording session may be stopped immediately or gracefully when the session ends.

4.2.4.6 EPC Domain stopping mechanisms

In MME, SGW and PGW a Trace Recording Session shall be stopped when any of the defined stop triggering events occur. If Trace Session deactivation is received from its EM during the Trace Recording Session, the MME, SGW and PGW are allowed to finish tracing of the on-going procedures (e.g. session). In this case the Trace Recording Session shall be stopped between the reception of the Trace Session deactivation and the appropriate stop-triggering event.

4.2.4.7 E-UTRAN stopping mechanisms for MDT

In case of immediate MDT, the eNodeB shall stop a trace recording session for a given UE when the UE changes cell or goes to idle mode or when the cell trace session is deactivated at the eNodeB from its EM. The eNodeB shall deactivate the corresponding MDT RRC measurements in the UE.

In case of logged MDT or Logged MBSFN MDT,, there is no stopping mechanism in the eNodeB. The eNodeB does not need to maintain a logged MDT or Logged MBSFN MDT, trace recording session once it has been configured in the UE.

4.2.4.8 Stopping mechanisms at UE for MDT

In case of logged MDT or Logged MBSFN MDT,, the UE shall stop an ongoing trace recording session when logging duration expires and it shall indicate the availability of logged measurement results to the network next time it enters connected mode.

The UE shall discard an ongoing logged MDT trace recording session when it receives a new logged MDT or Logged MBSFN MDT, trace recording session configuration from the network.

The UE shall discard an ongoing Logged MBSFN MDT trace recording session when it receives a new logged MDT or Logged MBSFN MDT trace recording session configuration from the network.

4.2.4.9 5GC Domain stopping mechanisms

In AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM a Trace Recording Session shall be stopped when any of the defined stop triggering events occur. If Trace Session deactivation is received from its management system during the Trace Recording Session, the AF, AMF, AUSF, NEF, NRF, NSSF, PCF, SMF, SMSF, UPF or UDM are allowed to finish tracing of the on-going procedures (e.g. session). In this case the Trace Recording Session shall be stopped between the reception of the Trace Session deactivation and the appropriate stop-triggering event.

4.2.4.10 NG-RAN stopping mechanisms

The Trace Recording Session in the NG-RAN node shall be stopped when the call/session is ended in the cell under trace or the call/session is haneded over to another cell. If the Trace Session is deactivated at a time when there are ongoing sessions the trace recording session may be stopped immediately or gracefully when the session ends.

4.2.4.11 NG-RAN stopping mechanisms for management based MDT

In case of immediate MDT, the gNB shall stop a trace recording session for a given UE when the UE changes cell or goes to idle mode or inactive state or when the cell trace session is deactivated at the gNB from its NG-RAN management system The gNB shall deactivate the corresponding MDT RRC measurements in the UE.

In case of logged MDT, there is no stopping mechanism in the gNB. The gNB does not need to maintain a logged MDT, trace recording session once it has been configured in the UE.