7 Measurement & Trace Definitions

32.1033GPPIntegration Reference Point (IRP) overview and usage guideRelease 17Telecommunication managementTS

7.1 Performance Measurements

7.1.1 Overview and relationships to IRP Framework

Figure 7.1.1-1: PM-related Specifications

7.1.2 Performance Measurement Specifications

PS core Performance Measurements – 32.406 [96]

The purpose of this specification is to define performance measurements specific to Core Network Packet Switched Domain in a UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

CS core Performance Measurements – 32.407 [97]

The purpose of this specification is to define performance measurements specific to Core Network Circuit Switched Domain in a UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

Services Performance Measurements – 32.408 [98]

The purpose of this specification is to define performance measurements specific to teleservices(categorized by Multimedia Messageing Service, Short Message Service, Multimedia Calls, Voice Call and Intelligent Services) in a UMTS network or combined UMTS/GSM network, . The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

IMS Performance Measurements – 32.409 [99]

The purpose of this specification is to define performance measurements specific to an IMS (IP Multimdedia Subsystem) network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

EPC Performance Measurements – 32.426 [106]

The purpose of this specification is to define performance measurements specific to an EPC network or combined EPC/UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

GSM Performance Measurements – 52.402 [140]

The purpose of this specification is to define performance measurements specific to a GSM system. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

UTRAN Performance Measurements – 32.405 [95]

The purpose of this specification is to define performance measurements specific to a UTRAN in UMTS network or combined UMTS/GSM network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

E-UTRAN Performance Measurements – 32.425 [105]

The purpose of this specification is to define performance measurements specific to an E-UTRAN network. The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

HNB Performance Measurements – 32.452 [113]

The purpose of this specification is to define performance measurements specific to Home NodeB Subsystem(consists of HNB and HNB-GW). The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

HeNB Performance Measurements – 32.453 [114]

The purpose of this specification is to define performance measurements specific to Home enhanced NodeB Subsystem(consists of HeNB and optionally HeNB-GW). The standardized measurements result in comparability of measurement data produced in a multi-vendor network.

UMTS & GSM KPIs – 32.410 [100]

The purpose of this specification is to define Key Performance Indicators (KPIs) for GSM and UMTS. KPI definitions include high level KPIs that are a) common across GSM and UMTS networks; and b) specific to network techniques such as GSM and UMTS networks.

E-UTRAN KPIs – 32.451 [112]

This specification defines requirements (business level requirements, specification level requirements and use case descriptions) related to KPIs for E-UTRAN.

IMS KPIs – 32.454 [115]

This specification defines KPIs for the IP Multimedia Subsystem (IMS).

EPC KPIs – 32.455 [116]

This specification defines KPIs for the Evolved Packet Core (EPC).network.

PM File Format – 32.432 [107], 32.435 [108], 32.406 [109]

This set of specifications describe the general semantics of performance measurement result and collection. It defines the report file format, report file conventions, and the file transfer procedure.Performance measurements for Evolved Packet Core (EPC) and non-3GPP access interworking system – 28.402 [61]

This specification describes the measurements for EPC and non-3GPP access network interworking and is valid for all measurement types provided by an implementation of EPC and non-3GPP access Interworking System. Measurements related to "external" technologies (such as ATM or IP) as described by "external" standards bodies (e.g. ITU-T or IETF) are only be referenced within this specification, wherever there is a need identified for the existence of such a reference.

Performance measurements for Wireless Local Area Network (WLAN) – 28.403 [62]

This specification describes the measurements for WLAN and is valid for all measurement types provided by an implementation of a WLAN. Measurements related to "external" technologies (such as WLAN or IP) as described by "external" standards bodies (e.g. IEEE or IETF) are only referenced within the present document, wherever there is a need identified for the existence of such a reference.

7.2 Trace Specifications

7.2.1 Overview and relationships to IRP Framework

Figure 7.2.1-2: Trace-related Specifications

7.2.2 Trace Specifications

Trace Concepts and Requirements – 32.421 [37]

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 networks or EPS 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 Element Manager (EM), 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, i.e. EM(s) and/or Network Manager(s) (NM(s)).

Trace Control & Configuration – 32.422 [57]

This specification describes the mechanisms used for the control and configuration of the Trace functionality at the EMs, NEs and UEs. 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 Network Elements (NEs) and User Equipment (UE) and the transfer of these results to one or more EM(s) and/or Network Manager(s) (NM(s)).

Trace Data Definitions – 32.423 [104]

This specification describes Trace data definition and management. It covers the trace records content, their format and transfer.

Trace IRP – 32.441 1 [38], 32.442 [110], 32.446 [111]

The Trace IRP supports the operations that are required for the Subscriber and Equipment trace, the Cell Traffic Trace, Minimization of Drive Tests (MDT) functionalities across UMTS networks or EPS networks and Radio Link Failure (RLF) reporting functionalities across EPS networks. GSM Trace is outside of the scope of this specification.

7.3 QoE measurements

7.3.1 Overview and relationships to management services

Figure 7.3.1-1: QoE related Specifications

7.3.2 QoE specifications

QoE measurement collection – Concepts, use cases and requirements – TS 28.404 [58]

One main motivation of mobile network evolution is to improve the user experience why the evaluation of the user experience at the UE side is vital to network operators, especially when the operators provide some real-time services which require for example high date rate and low latency like streaming services (typically video services) , where even intermittent quality degradation is very annoying. Many of these streaming services are a significant part of the commercial traffic growth rate, therefore the focus is on the end users’ experience.

Quality of Experience (QoE) information collection provides detailed information at call level on a number of UEs.

The capability to log information within a UE, and in particular the QoE of an end user service, initiated by an operator, provides the operator with QoE information. The collected information (specified in 3GPP TS 26.247 [188]) cannot be deduced from performance measurements in the mobile network.

The QoE information is information collected by the end user application in the UE.

The collected QoE information is collected by the management system for analysis and/or KPI calculations.

QoE measurement collection – Control and Configuration – TS 28.405 [59]

TS 28.405 [59] addresses the mechanisms used for the function Quality of Experience (QoE) measurement collection in UMTS and LTE. The measurements that are collected are DASH and MTSI measurements.

The function includes collecting QoE information from UEs frequenting a specified area or an individual UE for a specified end user service/end user service type. The document describes the activation and deactivation of a network request session, UE request session and recording session and also the reporting of recorded information.

QoE measurement collection – Information definition and transport – TS 28.406 [60]

TS 28.406 [60] describes Quality of Experience (QoE) measurement collection record content definition and management. It covers the Quality of Experience (QoE) measurement data content, their format and transfer across UMTS networks and LTE networks.