The present document is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management, as identified below: Subscriber and equipment trace provide very detailed information at call level on one or more specific mobile(s). This data is an additional source of information to Performance Measurements and allows going further in monitoring and optimisation operations. Contrary to Performance measurements, which are a permanent source of information, trace is activated on user demand for a limited period of time for specific analysis purposes. Trace plays a major role in activities such as determination of the root cause of a malfunctioning mobile, advanced troubleshooting, optimisation of resource usage and quality, RF coverage control and capacity improvement, dropped call analysis, Core Network and Access Network end-to-end procedure validation. The capability to log data on any interface at call level for a specific user (e.g. IMSI) or mobile type (e.g. IMEI or IMEISV), or service initiated by a user allows getting information which cannot be deduced from Performance measurements such as perception of end-user QoS during his call (e.g. requested QoS vs. provided QoS), correlation between protocol messages and RF measurements, or interoperability with specific mobile vendors. Moreover, performance measurements provide values aggregated on an observation period; Subscriber and UE Trace give instantaneous values for a specific event (e.g. call, location update, etc.). If performance measurements are mandatory for daily operations, future network planning and primary trouble shooting; Subscriber and UE Trace is the easy way to go deeper into investigation and network optimisation. In order to produce this data, Subscriber and UE Trace are carried out in the NEs, which comprise the network. The data can then be transferred to an external system (e.g. an Operations System (OS) in TMN terminology, for further evaluation).

The present document describes the requirements for the management of Trace and the reporting of Trace data (including FDD mode and TDD mode) across UMTS, EPS or 5G networks as it refers to subscriber tracing (tracing of IMSI or Public User Identity) and equipment tracing (tracing of IMEI or IMEISV). Trace also includes the ability to trace all active calls in a cell or multiple cells (Cell Traffic Trace). The present document also includes the description of Service Level Tracing (tracing of a specific service). It defines the administration of Trace Session activation/deactivation by the management system, the network or User Equipment (UE) itself via signalling, the generation of Trace results in the Network Elements (NEs) and UE and the transfer of these results to one or more Operations Systems. GSM Trace is outside of the scope of this specification (see TS 52.008). Furthermore, it describes requirements for Random Access (RA) Report, Successful Handover Report (SHR), Successful PSCell Change Report (SPR), Mobility History Information (MHI) Report and VisitedCellInfoList reporting for 5G networks. The present document also describes the requirements for the management of Minimization of Drive Tests (MDT) across UMTS networks, EPS networks or 5G networks and Radio Link Failure (RLF) and RRC Connection Establishment Failure (RCEF) reporting across EPS networks and 5G networks. The present document is built upon the basic Subscriber and UE Trace concept described in clause 4. The high-level requirements for Trace data, Trace Session activation/deactivation and Trace reporting are defined in clause 5. Clause 5 also contains an overview of use cases for Trace (the use cases are described in Annex A). Clause 6 defines the requirements for managing MDT. Clause 7 defines the requirements for managing RLF, RCEF, RA, SHR, SPR, MHI and VisitedCellInfoList reports. Trace control and configuration management are described in TS 32.422, and Trace data definition and management are described in TS 32.423. The present document does not cover any Trace capability limitations within a NE (e.g. maximum number of simultaneous traced mobiles for a given NE) or any functionality related to these limitations (e.g. NE aborting a Trace Session due to resource limitations). The objectives of the Trace specifications are:

1. to provide the descriptions for a standard set of Trace and MDT data;
2. to produce a common description of the management technique for Trace, MDT, RLF, RCEF, RA, SHR, SPR, MHI and VisitedCellInfoList administration and result reporting;
3. to define a method for the reporting of Trace, MDT, RLF, RCEF, RA, SHR, SPR, MHI and VisitedCellInfoList results across the management interfaces.

The following is beyond the scope of the present document, and therefore the present document does not describe:

• tracing non-Subscriber or non-UE related events within an NE;
• tracing of all possible parties in a multi-party call (although multiple calls related to the IMSI specified in the Trace control and configuration parameters are traceable).

The definition of Trace and MDT data is intended to result in comparability of Trace and MDT data produced in a multi-vendor wireless UMTS, EPS and/or 5G network(s), for those Trace control and configuration parameters that can be standardised across all vendors' implementations. Vendor specific extensions to the Trace control and configuration parameters and Trace and MDT data are discussed in TS 32.422 and TS 32.423. All functions (trace, MDT etc.) specified in this specification support Network Sharing, with the following conditions:

• It is accepted that the recorded information from the shared nodes is available to the Primary Operator. Recorded information that is collected in a non shared node or cell will only be available to the operator managing the non shared node or cell.
• It is accepted that the recorded information from the shared network shall be delivered to the Participating Operator whose PLMN recording is requested, taking user consent into account. Operators must also agree on sharing the information, but how that agreement is done is outside the scope of this specification. The mapping of TCE IP addresses and TCE addresses must be coordinated among the operators that shares the network. How that coordination is done is outside the scope of this specification.
• It is accepted that the inter-PLMN recorded information for Logged MDT from the non-shared nodes of Participating Operators may be available to the Primary Operator.
• For signalling based activation, the operators that share a network must coordinate the TCE IP addresses and the TCE address mapping must be coordinated. How that coordination is done is outside the scope of this specification.

For UMTS and EPS the 3GPP Management reference model, TS 32.101 is followed. For 5GS the 3GPP Services Based Management Architecture, TS 28.533 is followed.

The following documents contain provisions, which, through reference in this text, constitute provisions of the present document.

• References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.