1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelTelecommSubscribTrace con(3GPP TS 32.4TECHNICAL SPECIFICATION132 421 V13.0.0 (2016mmunications system (Phase elecommunications System (LTE; munication management; iber and equipment trace; o cepts and requirements .421 version 13.0.0 Release 131
2、6-03) e 2+) (GSM); (UMTS); 13) ETSI ETSI TS 132 421 V13.0.0 (2016-03)13GPP TS 32.421 version 13.0.0 Release 13Reference RTS/TSGS-0532421vd00 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 421 V13.0.0 (2016-03)23GPP TS 32.421 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 421 V13.0.0 (2016-03)33GPP TS 32.421 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 6g31 Scope 7g32 References 8g33 Definitions, symbols and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 11g3
16、4 Trace concepts and high-level architecture 12g34.1 Trace concepts 12g34.2 Trace high level Architecture . 14g34.3 Service Level Tracing for IMS high level Architecture . 17g35 Trace requirements . 19g35.1 General trace requirements . 19g35.2 Requirements for Trace data 21g35.3 Requirements for Tra
17、ce activation . 22g35.3.1 Requirements for Trace Session activation . 22g35.3.2 Requirements for starting a Trace Recording Session 24g35.4 Requirements for Trace deactivation 26g35.4.1 Requirements for Trace Session deactivation . 26g35.4.2 Requirements for stopping a Trace Recording Session 26g35.
18、5 Requirements for Trace Data reporting 28g35.6 Requirements for Privacy and Security 30g35.7 Requirements for Charging 30g35.8 Use cases for Trace. 31g36 Requirements for managing MDT . 32g36.1 Business Level Requirements. 32g36.2 Specification level requirements 33g36.2.1 Logged MDT and Immediate
19、MDT requirements 33g36.2.2 Logged MBSFN MDT requirements 34g37 Requirements for managing RLF reports . 36g37.1 Business level requirements . 36g37.2 Specification level requirements 36g3Annex A (informative): Trace use cases . 37g3A.1 Use case #1: multi-vendor UE validation . 37g3A.1.1 Description .
20、 37g3A.1.2 Example of required data for this use case . 37g3A.2 Use case #2: subscriber complaint . 37g3A.2.1 Description . 37g3A.2.2 Example of required data for this use case . 38g3A.3 Use case #3: malfunctioning UE 39g3A.3.1 Description . 39g3A.3.2 Example of required data for this use case . 39g
21、3A.4 Use case #4: checking radio coverage 39g3A.4.1 Description . 39g3ETSI ETSI TS 132 421 V13.0.0 (2016-03)43GPP TS 32.421 version 13.0.0 Release 13A.4.2 Example of required data to cover use case #4 . 39g3A.5 Use case #5: testing a new feature 40g3A.5.1 Description . 40g3A.5.2 Example of required
22、data to cover use case #5 . 40g3A.6 Use case #6: fine-tuning and optimisation of algorithms/procedures 41g3A.6.1 Description . 41g3A.6.2 Example of required data to cover use case #6 . 42g3A.7 Use case #7: Automated testing of Service Provider services 42g3A.7.1 Description . 42g3A.8 Use case #8: Re
23、gression testing following a network fix . 42g3A.8.1 Description . 42g3A.9 Use case #9: Service fault localization within a Service Provider network . 42g3A.9.1 Description . 42g3A.10 Use case #10: Service fault localization when a service is hosted by a third party Service Provider 42g3A.10.1 Descr
24、iption . 42g3A.11 Use case #11 Analysing drop calls in E-UTRAN 43g3A.11.1 Description . 43g3A.11.2 Example of required data to cover use case #11 . 43g3A.12 Use case #12 Periodical sampling of network performance 43g3A.12.1 Description 43g3A.12.2 Example of required data to cover use case #12 43g3A.
25、13 Use case #13 Differentiation of area based MDT data by terminal type 44g3A.13.1 Description . 44g3A.13.2 Example of required data to cover use case #13 . 44g3A.14 Use case #14 Subscriber complaint about MBMS service in the eUTRAN network 44g3A.14.1 Description . 44g3A.14.2 Example of required dat
26、a to cover use case #14 . 44g3A.15 Use case #15 Check MBMS service quality and performance of the eUTRAN Network . 45g3A.15.1 Description . 45g3A.15.2 Example of required data to cover use case #15 . 45g3Annex B (informative): Change history . 46g3History 48g3ETSI ETSI TS 132 421 V13.0.0 (2016-03)53
27、GPP TS 32.421 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 continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the c
28、ontents 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 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved
29、 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 only changes have been incorporated in the document. ETSI ETSI TS 132 421 V13.0.0 (2016-03)63GPP TS
30、32.421 version 13.0.0 Release 13Introduction 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 co
31、ncepts 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 equipment trace provide very detailed information at call level on one or more specific
32、 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 ti
33、me 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 UT
34、RAN end-to-end UMTS 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
35、 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 ins
36、tantaneous 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 UMTS network optimisation. In o
37、rder 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). ETSI ETSI TS 132 421 V13.0.0 (2016-03)73GPP TS 32.421 version
38、 13.0.0 Release 131 Scope 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 trac
39、ing (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 act
40、ivation/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). GSM Trace
41、 is outside of the scope of this specification (see 7). The present document also describes the requirements for the management of Minimization of Drive Tests (MDT) across UMTS networks or EPS networks and Radio Link Failure (RLF) reporting across EPS networks. The present document is built upon the
42、 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 de
43、fines the requirements for managing MDT. Clause 7 defines the requirements for managing RLF reports.Trace control and configuration management are described in 3GPP TS 32.422 2, and Trace data definition and management are described in 3GPP TS 32.423 3. The present document does not cover any Trace
44、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: a) to provide the descriptions for
45、a standard set of Trace and MDT data; b) to produce a common description of the management technique for Trace, MDT and RLF administration and result reporting; c) to define a method for the reporting of Trace, MDT and RLF results across the management interfaces. The following is beyond the scope o
46、f 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 paramete
47、rs 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 and/or EPS network(s), for those Trace control and configuration parameters that can be standardised across all vendors implementations. Vendo
48、r specific extensions to the Trace control and configuration parameters and Trace and MDT data are discussed in 3GPP TS 32.422 2 and 3GPP TS 32.423 3. All functions (trace, MDT etc.) specified in this specification support Network Sharing, with the following conditions: - It is accepted that the rec
49、orded information from the shared nodes is available to the Master 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 addresse
