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: Additionally, there is a GSM only Subscriber and Equipment Trace specification: TS 52.008. 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, UTRAN, EPC, 5GC, E-UTRAN and NG-RAN procedure validation. The capability to log data on any interface at call level for a specific user (e.g. IMSI or SUPI) or mobile type (e.g. IMEI or IMEISV), or service initiated from a UE 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 Equipment 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 Equipment Trace is the easy way to go deeper into investigation and network optimisation. In order to produce this data, Subscriber and Equipment 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 mechanisms used for the control and configuration of the Trace, Minimization of Drive Test (MDT) in E-UTRAN/NG-RAN, Radio Link Failure (RLF) and RRC Connection Establishment Failure (RCEF) reporting functionality, and 5GC UE level measurements collection at the management system (at the Element Manager (EM) and or Network Manager (NMs) in UMTS, EPS and NR), Network Elements (NEs) and User Equipment (UEs). For Trace functionality, it covers the triggering events for starting/stopping of subscriber/UE activity traced over 3GPP standardized signalling interfaces, the types of trace mechanisms, configuration of a trace, level of detail available in the trace data, the generation of Trace results in the NEs and UE and the transfer of these results to management system. For MDT, it also covers logged MDT and immediate MDT mechanisms in both management based and signalling based scenarios. GSM is excluded from the RAT systems which the present document can be applied to. For 5GC UE level measurements collection, it also covers management based and signalling based scenarios. The mechanisms for Trace, MDT, RLF and RCEF reporting, and 5GC UE level measurements activation/deactivation are detailed in clause 4; clause 5 details the various Trace, MDT, RLF and RCEF reporting, and 5GC UE level measurements control and configuration parameters and the triggering events that can be set in a network. Trace, MDT, RLF and RCEF reporting concepts and requirements are covered in TS 32.421 while Trace and MDT data definition and management is covered in TS 32.423. The 5GC UE level measurements definitions and use cases are covered in TS 28.558. The conditions for supporting Network Sharing are stated in TS 32.421. The condition for supporting user consent handling for MDT does not apply to Standalone Non-Public Network, i.e., SNPN as per TS 23.501.

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.