1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommSubscribTrace data d(3GPP TS 32.4TECHNICAL SPECIFICATION132 423 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; iber and equipment trace; a definition and management .423 version 13.0.0 Release
2、1316-02) hase 2+); (UMTS); t 13) ETSI ETSI TS 132 423 V13.0.0 (2016-02)13GPP TS 32.423 version 13.0.0 Release 13Reference RTS/TSGS-0532423vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562
3、00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any
4、 electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Forma
5、t (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status
6、/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including pho
7、tocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute
8、 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks r
9、egistered and owned by the GSM Association. ETSI ETSI TS 132 423 V13.0.0 (2016-02)23GPP TS 32.423 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs,
10、if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are availa
11、ble on the ETSI Web server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are,
12、 or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM iden
13、tities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“,
14、“should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ET
15、SI TS 132 423 V13.0.0 (2016-02)33GPP TS 32.423 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 8g33.3 Abbre
16、viations . 8g34 Trace Record Contents . 9g34.1 General . 9g34.2 MSC Server Trace Record Content 10g34.3 MGW Trace Record Content 17g34.4 SGSN Trace Record Content 18g34.5 GGSN Trace Record Content . 26g34.6 UTRAN Trace Record Content 29g34.7 S-CSCF Trace Record Content 36g34.8 P-CSCF Trace Record Co
17、ntent 36g34.9 HSS Trace Record Content 37g34.10 BM-SC Trace Record Content . 41g34.11 PGW Trace Record Content . 42g34.12 MME Trace Record Content 46g34.13 E-UTRAN Trace Record Content 54g34.14 SGW Trace Record Content . 59g34.15 EIR Trace Record Content . 63g34.16 LTE MDT Trace Record Content . 64g
18、34.16.1 Trace Record for Immediate MDT measurements 64g34.16.2 Trace Record for UE location information . 65g34.17 UMTS MDT Trace Record Content . 65g34.17.1 Trace Record for Immediate MDT measurements 65g34.17.2 Trace Record for UE location information . 66g3Annex A (normative): Trace Report File F
19、ormat . 67g3A.0 Introduction 67g3A.1 Parameter description and mapping table. 68g3A.2 XML file format definition . 71g3A.2.1 XML trace/MDT file diagram 71g3A.2.2 Trace data file XML schema 72g3Annex B (normative): Trace Report File Conventions and Transfer Procedure . 75g3B.0 Introduction 75g3B.1 Fi
20、le naming convention 75g3B.2 File transfer 76g3Annex C (informative): Trace Functional Architecture: Reporting 77g3C.1 Figure of Trace Reporting 77g3ETSI ETSI TS 132 423 V13.0.0 (2016-02)43GPP TS 32.423 version 13.0.0 Release 13Annex D (informative): Examples of trace files . 79g3D.1 Examples of tra
21、ce XML file . 79g3D.1.1 Example of XML trace file with the maximum level of details . 79g3D.1.2 Example of XML trace file with the minimum level of details 80g3D.1.3 Example of XML trace file for IMSI information from the MME . 80g3D.1.4 Example of MDT XML file . 81g3Annex E (informative): Void . 82
22、g3Annex F (informative): Change history . 83g3History 85g3ETSI ETSI TS 132 423 V13.0.0 (2016-02)53GPP TS 32.423 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to contin
23、uing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 pres
24、ented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial on
25、ly changes have been incorporated in the document. Introduction 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 equipm
26、ent 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
27、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
28、 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 Net
29、work and UTRAN end to end 3G 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) allows getting information which cannot be deduced from Performance Measurements such as perception of end-user QoS during
30、 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 value
31、s 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 3G network optimisation. In order to produce th
32、is 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). ETSI ETSI TS 132 423 V13.0.0 (2016-02)63GPP TS 32.423 version 13.0.0 Release 13
33、1 Scope The present document describes Trace data definition and management. It covers the trace records content, their format and transfer across UMTS networks or EPS networks GSM Trace is outside of the scope of this specification The present document also describes the data definition for Minimiz
34、ation of Drive Tests (MDT) across UMTS networks or EPS 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 a
35、cross the management interfaces. Clause 4 details the various Trace records content, 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 tr
36、ace and MDT files examples. Trace and MDT concepts and requirements are covered in TS 32.421 2 while Trace control and configuration management are described in 3GPP TS 32.422 3. The definition of Trace and MDT data is intended to result in comparability of Trace and MDT data produced in a multi-ven
37、dor wireless UMTS and/or EPS network. 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
38、 trace data transfer; Any Trace capability limitations (e.g. maximum number of simultaneous traced mobiles for a given NE). 2 References The following documents contain provisions, which, through reference in this text, constitute provisions of the present document. References are either specific (i
39、dentified 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 ref
40、erence implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.421: “Telecommunication management; Subscriber and equipment trace: Trace concepts and r
41、equirements.“ 3 3GPP TS 32.422: “Telecommunication management; Subscriber and equipment trace: Trace control and configuration management “. 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 5 W3C Recommendation “Extensible Markup Language (XML) 1.0“ (Second Edition, 6 October 2000) http:/www.
42、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 ETSI ETSI TS 132 423 V13.0.0 (2016-02)73GPP TS 32
43、.423 version 13.0.0 Release 138 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: 198
44、8 (E) “Representations of dates and times“ (1988-06-15) http:/www.iso.ch/markete/8601.pdf 11 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 12 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic ne
45、twork resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 13 3GPP TS 29.274: “3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3“. 14 3GPP TS 29.212: “Policy and Charging Control (PCC);Referen
46、ce points“. 15 3GPP TS 29.273: “Evolved Packet System (EPS); 3GPP EPS AAA interfaces“. 16 3GPP TS 36.413: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 17 3GPP TS 36.423 “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Pr
47、otocol (X2AP)“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.421 2 and 3GPP TS 32.422 3 apply. Minimum Level of detail: Allows for retrieval of a decoded subset of the IEs contained in the signalling
48、interface messages. Medium Level of detail: Allows for retrieval of the decoded subset of the IEs contained in the signalling interface messages in the Minimum Level plus a selected set of decoded radio measurement IEs. Maximum Level of detail: Allows for retrieval of signalling interface messages w
49、ithin the Trace Scope in encoded format. ETSI ETSI TS 132 423 V13.0.0 (2016-02)83GPP TS 32.423 version 13.0.0 Release 133.2 Symbols For the purposes of the present document, the following symbols apply: 3.3 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 4 and 3GPP TS 32.101 1 apply. xxx xxx 1 : Element named xxx The maximum number of occurrence is 1 : Element named xxx The maximum number of occurrence is unbounded : Global element The XML element has a val
