Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 32.423  Word version:  17.6.0

Top   Top   None   None   Next
0…   3…   5…

 

0  Introductionp. 5

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:
TS 32.421:
"Subscriber and equipment trace; Trace concepts and requirements";
TS 32.422:
"Subscriber and equipment trace; Trace control and configuration management ";
TS 32.423:
"Subscriber and equipment trace; Trace data definition and management";
Subscriber and MS 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 purpose
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 TRAN end to end 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) 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 MS Trace is the easy way to go deeper into investigation and network optimisation.
In order to produce this data, Subscriber and MS 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).
Up

1  Scopep. 6

The present document describes Trace data definition and management. It covers the trace records content, their format and transfer across UMTS networks, EPS networks or 5GS networks. GSM Trace is outside of the scope of this specification..
The present document also describes the data definition for Minimization of Drive Tests (MDT) across 3GPP networks.
The objectives of the present document are:
  • To provide the descriptions for a standard set of Trace and MDT data;
  • To define the common format of trace and MDT records; and
  • To define a method for the reporting of Trace and MDT results across the management interfaces.
Clause 4 details the various Trace records content, Clause 5 defines GPB trace format for NR, Annex A provides Trace and MDT report file format, Annex B provides the trace report file conventions and transfer procedure, Annex C provides the trace reporting functional architecture and Annex D provides some trace and MDT files examples, Annex G provides normative GPB trace record schema and examples.
Trace and MDT concepts and requirements are covered in TS 32.421 while Trace control and configuration management are described in TS 32.422.
The definition of Trace and MDT data is intended to result in comparability of Trace and MDT data produced in a multi-vendor wireless 3GPP networks.
The following is beyond the scope of the present document, and therefore the present document does not describe:
  • Any notification mechanisms or IRPs for trace. Only file transfer mechanism is specified for trace data transfer;
  • Any data compression mechanisms for trace data transfer;
  • Any Trace capability limitations (e.g. maximum number of simultaneous traced mobiles for a given NE).
Up

2  Referencesp. 6

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.
[1]
TS 32.101: "Telecommunication management; Principles and high level requirements".
[2]
TS 32.421: "Telecommunication management; Subscriber and equipment trace: Trace concepts and requirements."
[3]
TS 32.422: "Telecommunication management; Subscriber and equipment trace: Trace control and configuration management ".
[4]
TR 21.905: "Vocabulary for 3GPP Specifications".
[5]
W3C Recommendation "Extensible Markup Language (XML) 1.0" (Second Edition, 6 October 2000): http://www.w3.org/TR/2000/REC-xml-20001006
[6]
W3C Recommendation "Namespaces in XML" (14 January 1999): http://www.w3.org/TR/1999/REC-xml-names-19990114
[7]
W3C Recommendation "XML Schema Part 0: Primer" (2 May 2001): http://www.w3.org/TR/2001/REC-xmlschema-0-20010502
[8]
W3C Recommendation "XML Schema Part 1: Structures" (2 May 2001) http://www.w3.org/TR/2001/REC-xmlschema-1-20010502
[9]
W3C Recommendation "XML Schema Part 2: Datatypes" (2 May 2001) http://www.w3.org/TR/2001/REC-xmlschema-2-20010502
[10]
International Standard ISO 8601: 1988 (E) "Representations of dates and times" (1988-06-15) http://www.iso.ch/markete/8601.pdf
[11]
TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects".
[12]
3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[13]
TS 29.274: "3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3".
[14]
TS 29.212: "Policy and Charging Control (PCC); Reference points".
[15]
TS 29.273: "Evolved Packet System (EPS); 3GPP EPS AAA interfaces".
[16]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[17]
TS 36.423: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP)".
[18]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[19]
TS 23.502: "Procedures for the 5G System; Stage 2"
[20]
TS 38.300: "NR and NG-RAN Overall Description; Stage 2".
[21]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[22]
TS 38.401: "NG-RAN; Architecture Description".
[23]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[24]
TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[25]
TS 38.463: "NG-RAN; E1 Application Protocol (E1AP)".
[26]
TS 38.473: "NG-RAN; F1 Application Protocol (F1AP)".
[27]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[28]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[29]
TS 23.107: "Quality of Service (QoS) concept and architecture".
[30]
TS 25.331: "Radio Resource Control (RRC); Protocol specification".
[31]
TS 36.314: "Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements".
[32]
TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive Tests (MDT); Overall description; Stage 2".
[33]
TS 36.213: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures".
[34]
TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management".
[35]
TS 38.314: "NR; layer 2 measurements ".
[36]
TS 28.552: "Management and orchestration; 5G performance measurements".
[37]
TS 38.213: "NR; Physical layer procedures for control".
[38]
TS 36.214: "Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements".
[39]
TS 32.425: "Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN)".
[40]
RFC 6455:  "The WebSocket Procotol".
[41]
RFC 7692:  "Compression Extensions for WebSocket".
[42]
TS 38.215: "NR; Physical layer measurements".
[43]
TS 28.532: "Management and orchestration; Generic management services".
[44]
TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".
[45]
Up

Up   Top   ToC