14.9 Subscriber and equipment trace

23.2053GPPBearer-independent circuit-switched core networkRelease 17Stage 2TS

For the subscriber and equipment trace the MSC server may be activated for tracing (see 3GPP 32.421 [34]). Besides performing trace record generation, if Signalling based activation the MSC server shall forward the Trace Session activation to GERAN with BSSAP signaling, UTRAN with RANAP signaling (see 3GPP TS 25.413) and if the trace control and configuration parameters are defined so, the MGW. For detailed description of trace session activation mechanism see 3GPP TS 32.422 [35]. The activation to the MGW is sent using a trace package which is included either to the Add or Modify command(s) in mobile originated call or mobile terminating call. In the case of handovers where new termination is created the trace package is also included into the Add command. If the MSC does not receive the optional trace interface list IE in the trace activation request it shall request tracing on all terminations that support the total MGW trace interfaces as defined in TS 32.422. The MSC Server shall only set the trace interface list value that is associated to the interface that the termination supports and optionally the Mc interface trace value if requested from the HLR. The content of the trace records generated in the MSC server and the MGW will follow the rules of 3GPP TS 32.421[34] and 3GPP TS 32.422[35], 3GPP TS 32.423 [36]. The content of the MGW and MSC Server trace record is described in TS 32.423 [36].