ETSI TS 132 421-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Subscriber and e_1.pdf

《ETSI TS 132 421-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Subscriber and e_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 421-2018 Digital cellular telecommunications system (Phase 2+) (GSM) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Subscriber and e_1.pdf（48页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 421 V15.0.0 (2018-06) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements (3GPP TS 32.421 version 15.0.0 Release 15) TECHNICAL S

2、PECIFICATION ETSI ETSI TS 132 421 V15.0.0 (2018-06)13GPP TS 32.421 version 15.0.0 Release 15Reference RTS/TSGS-0532421vf00 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 00017 - NAF 742 C As

3、sociation 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 electronic and/or p

4、rint 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 Format (PDF) version kept

5、 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.asp

6、x 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 photocopying

7、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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTS

8、TMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks

9、registered and owned by the GSM Association. ETSI ETSI TS 132 421 V15.0.0 (2018-06)23GPP TS 32.421 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to t

10、hese essential IPRs, 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. Late

11、st updates are available 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 W

12、eb server) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property

13、 of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has be

14、en 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 identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross refer

15、ence 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“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in c

16、lause 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 ETSI TS 132 421 V15.0.0 (2018-06)33GPP TS 32.421 version 15.0.0 Release 15Contents Intellectual Property Rights 2

17、g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 6g31 Scope 7g32 References 8g33 Definitions, symbols and abbreviations . 9g33.1 Definitions 9g33.2 Abbreviations . 11g34 Trace concepts and high-level architecture 12g34.1 Trace concepts 12g34.2 Trace high level Architecture . 13g

18、34.3 Service Level Tracing for IMS high level Architecture . 15g35 Trace requirements . 17g35.1 General trace requirements . 17g35.2 Requirements for Trace data 18g35.3 Requirements for Trace activation . 19g35.3.1 Requirements for Trace Session activation . 19g35.3.2 Requirements for starting a Tra

19、ce Recording Session 22g35.4 Requirements for Trace deactivation 24g35.4.1 Requirements for Trace Session deactivation . 24g35.4.2 Requirements for stopping a Trace Recording Session 24g35.5 Requirements for Trace Data reporting 26g35.6 Requirements for Privacy and Security 28g35.7 Requirements for

20、Charging 28g35.8 Use cases for Trace. 29g36 Requirements for managing MDT . 30g36.1 Business Level Requirements. 30g36.2 Specification level requirements 31g36.2.1 Logged MDT and Immediate MDT requirements 31g36.2.2 Logged MBSFN MDT requirements 32g37 Requirements for managing RLF reports . 34g37.1

21、Business level requirements . 34g37.2 Specification level requirements 34g3Annex A (informative): Trace use cases . 35g3A.1 Use case #1: multi-vendor UE validation . 35g3A.1.1 Description . 35g3A.1.2 Example of required data for this use case . 35g3A.2 Use case #2: subscriber complaint . 35g3A.2.1 D

22、escription . 35g3A.2.2 Example of required data for this use case . 36g3A.3 Use case #3: malfunctioning UE 37g3A.3.1 Description . 37g3A.3.2 Example of required data for this use case . 37g3A.4 Use case #4: checking radio coverage 37g3A.4.1 Description . 37g3A.4.2 Example of required data to cover u

23、se case #4 . 37g3ETSI ETSI TS 132 421 V15.0.0 (2018-06)43GPP TS 32.421 version 15.0.0 Release 15A.5 Use case #5: testing a new feature 38g3A.5.1 Description . 38g3A.5.2 Example of required data to cover use case #5 . 38g3A.6 Use case #6: fine-tuning and optimisation of algorithms/procedures 38g3A.6.

24、1 Description . 38g3A.6.2 Example of required data to cover use case #6 . 40g3A.7 Use case #7: Automated testing of Service Provider services 40g3A.7.1 Description . 40g3A.8 Use case #8: Regression testing following a network fix . 40g3A.8.1 Description . 40g3A.9 Use case #9: Service fault localizat

25、ion within a Service Provider network . 40g3A.9.1 Description . 40g3A.10 Use case #10: Service fault localization when a service is hosted by a third party Service Provider 40g3A.10.1 Description . 40g3A.11 Use case #11 Analysing drop calls in E-UTRAN 41g3A.11.1 Description . 41g3A.11.2 Example of r

26、equired data to cover use case #11 . 41g3A.12 Use case #12 Periodical sampling of network performance 41g3A.12.1 Description 41g3A.12.2 Example of required data to cover use case #12 41g3A.13 Use case #13 Differentiation of area based MDT data by terminal type 42g3A.13.1 Description . 42g3A.13.2 Exa

27、mple of required data to cover use case #13 . 42g3A.14 Use case #14 Subscriber complaint about MBMS service in the eUTRAN network 42g3A.14.1 Description . 42g3A.14.2 Example of required data to cover use case #14 . 42g3A.15 Use case #15 Check MBMS service quality and performance of the eUTRAN Networ

28、k . 42g3A.15.1 Description . 42g3A.15.2 Example of required data to cover use case #15 . 43g3Annex B (informative): Change history . 44g3History 47g3ETSI ETSI TS 132 421 V15.0.0 (2018-06)53GPP TS 32.421 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGenera

29、tion 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 contents of the present document, it will be re-released by the TSG with an identifying change of release date a

30、nd 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 document under change control. y the second digit is incremented for all changes of substance, i.e. technical

31、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 V15.0.0 (2018-06)63GPP TS 32.421 version 15.0.0 Release 15Introduction The present document is part of a TS-family covering the 3rd Gener

32、ation 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 managemen

33、t“; 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 mobile(s). This data is an additional source of information to Performance Measurements and allows going furth

34、er 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 cau

35、se of a malfunctioning mobile, advanced troubleshooting, optimisation of resource usage and quality, RF coverage control and capacity improvement, dropped call analysis, Core Network and Access Network end-to-end procedure validation. The capability to log data on any interface at call level for a s

36、pecific 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 of end-user QoS during his call (e.g. requested QoS vs. provided QoS), correlation between protocol messag

37、es and RF measurements, or interoperability with specific mobile vendors. Moreover, performance measurements provide values aggregated on an observation period; Subscriber and UE Trace give instantaneous values for a specific event (e.g. call, location update, etc.). If performance measurements are

38、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 network optimisation. In order to produce this data, Subscriber and UE Trace are carried out in the NEs, which comprise the network. The d

39、ata 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 V15.0.0 (2018-06)73GPP TS 32.421 version 15.0.0 Release 151 Scope The present document describes the requirements for the management of Trace and the re

40、porting of Trace data (including FDD mode and TDD mode) across UMTS, EPS or 5G 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 cell

41、s (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 management system, the network or User Equipment (UE) itself via signalling, the generati

42、on of Trace results in the Network Elements (NEs) and UE and the transfer of these results to one or more Operations Systems. GSM Trace 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)

43、across UMTS networks, EPS networks or 5G networks and Radio Link Failure (RLF) reporting across EPS networks and 5G networks. The present document is built upon the basic Subscriber and UE Trace concept described in clause 4. The high-level requirements for Trace data, Trace Session activation/deact

44、ivation 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 defines the requirements for managing MDT. Clause 7 defines the requirements for managing RLF reports.Trace control and configuration mana

45、gement 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 capability limitations within a NE (e.g. maximum number of simultaneous traced mobiles for a given NE) or any functionality related to t

46、hese 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 a standard set of Trace and MDT data; b) to produce a common description of the management technique for Trace, MDT and RLF administrati

47、on 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 of the present document, and therefore the present document does not describe: - tracing non-Subscriber or non-UE related events within a

48、n 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 parameters are traceable). The definition of Trace and MDT data is intended to result in comparability of Trace and MDT data produced in a multi

49、-vendor wireless UMTS, EPS and/or 5G network(s), for those Trace control and configuration parameters that can be standardised across all vendors implementations. Vendor 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 recorded information from the shared nodes is available to the Master Operator. Recorded information that i