1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelTelecommTrace Management (3GPP TS 32.4TECHNICAL SPECIFICATION132 441 V13.0.0 (2016mmunications system (Phase elecommunications System (LTE; munication management; nt Integration Reference PointRequirements .441 version 13.0.0 Release 1316-03) e
2、2+) (GSM); (UMTS); int (IRP); 13) ETSI ETSI TS 132 441 V13.0.0 (2016-03)13GPP TS 32.441 version 13.0.0 Release 13Reference RTS/TSGS-0532441vd00 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 5
3、62 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
4、any 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 Fo
5、rmat (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/sta
6、tus/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
7、photocopying 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 Instit
8、ute 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 Mark
9、s registered and owned by the GSM Association. ETSI ETSI TS 132 441 V13.0.0 (2016-03)23GPP TS 32.441 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 IPR
10、s, 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 ava
11、ilable 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 a
12、re, 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 i
13、dentities. 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
15、 ETSI TS 132 441 V13.0.0 (2016-03)33GPP TS 32.441 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Trace
16、 Concepts . 6g35 Trace Requirements 7g35.1 Trace Management and Itf-N . 7g35.2 Managing Trace Sessions . 8g35.3 Management of trace record files . 9g35.3.1 General 9g35.3.2 Managing trace records for roaming cases (inter-operator cases) . 9g35.3A Void 9g35.4 Overview of IRPs related to Trace . 9g36
17、Requirements specific for managing MDT 10g36.2 Logged MBSFN MDT requirements 11g37 Requirements specific for managing RLF reporting 11g3Annex A (informative): Use Cases 12g3A.1 General . 12g3A.2 Use case #1: Centralized place for Trace Session Activation in case of Management Based Activation . 12g3
18、A.3 Use case #2: Centralized place to collect trace records in case of Signalling Based Activation 13g3A.4 Use case #3: Centralized place to collect trace records in case of Signalling Based Activation 14g3Annex B (informative): Change history . 15g3History 16g3ETSI ETSI TS 132 441 V13.0.0 (2016-03)
19、43GPP TS 32.441 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
20、 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 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approv
21、ed 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. Introduction The present document is part of
22、a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.441 “Trace Management Integration Reference Point (IRP); Requirements“. 32.442 “Trace Management Integration Reference Point (I
23、RP); Information Service (IS)“. 32.446 “Trace Management Integration Reference Point (IRP); Solution Set (SS) definitions“. The present document is part of a TS-family which describes the requirements and information model necessary for the Telecommunication Management (TM) of 3G systems. The TM pri
24、nciples and TM architecture are specified in 3GPP TS 32.101 2 and 3GPP TS 32.102 3. Trace provides very detailed information on call level for a specific subscriber or MS. This data is an additional information source to Performance Measurements and allows deeper investigations in problems solving o
25、r in case of optimization. ETSI ETSI TS 132 441 V13.0.0 (2016-03)53GPP TS 32.441 version 13.0.0 Release 131 Scope The present document specifies the overall requirements for the Trace Management Integration Reference Point (TraceIRP) as it applies to Itf-N. The Trace IRP supports the operations that
26、 are required for the Subscriber and Equipment trace, the Service Level 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
27、of this specification All functions (trace, MDT etc.) specified in this specification supports Network Sharing, with the following condition: 1. It is accepted that the recorded information from the shared network can be sent to any of the operators sharing the network, taking user consent into acco
28、unt. 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 addresses and TCE addresses must be coordinated among the operators that shares the network. How that coordination is done is outside the scope
29、of this specification 2. For signalling based activation, the operators that share a network must coordinate the TCE IP addresses and the TCE address mapping must be coordinated. How that coordination is done, is outside the scope of this specification. 3. The 3GPP Managment reference model, 3GPP TS
30、 32.101 2 is followed. Editors note: The requirements for Service Level Tracing are FFS. 2 References 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, ed
31、ition 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 late
32、st version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.421:
33、 “Telecommunication management; Subscriber and equipment trace; Trace concepts and requirements“. 5 void. 6 3GPP TS 32.423: “Telecommunication management; Subscriber and equipment trace; Trace data definition and management“. 7 3GPP TS 32.341: “Telecommunication management; File Transfer (FT) Integr
34、ation Reference Point (IRP): Requirements“. 8 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. ETSI ETSI TS 132 441 V13.0.0 (2016-03)63GPP TS 32.441 version 13.0.0 Release 139 void. 10 3GPP TS 32.150: “Telecommunication m
35、anagement; Integration Reference Point (IRP) Concept and definitions“. 11 3GPP TS 32.301: “Notification Integration Reference Point (IRP): Requirements“. 12 3GPP TS 32.302: “Notification Integration Reference Point (IRP): Information Service (IS)“. 13 void. 14 void 15 3GPP TS 32.346: “Telecommunicat
36、ion management; File Transfer (FT) Integration Reference Point (IRP): Solution Set (SS) definitions“. 16 3GPP TS 32.306: “Notification Integration Reference Point (IRP): Solution Set (SS) definitions“ 17 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terre
37、strial Radio Access Network (E-UTRAN); Overall description; Stage 2“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1 apply. NOTE: A term defined in the present document takes precedence over the definition
38、 of the same term, if any, in 3GPP TR 21.905 1. MBSFN Area: See 3GPP TS 36.300 17 MBSFN Area Reserved Cell: See 3GPP TS 36.300 17 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 apply. An abbreviation defined in the present document takes prece
39、dence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 1. MBMS Multimedia Broadcast Multicast Services MBSFN MBMS over a Single Frequency Network MDT Minimization of Drive Tests 4 Trace Concepts Trace Concepts are defined in 3GPP TS 32.421 4. ETSI ETSI TS 132 441 V13.0.0 (2016
40、-03)73GPP TS 32.441 version 13.0.0 Release 135 Trace Requirements 5.1 Trace Management and Itf-N The Itf-N may connect the Network Management system to the EM, which can be located in either the DM (system context A) or in the NE (system context B). This is done by means of Integration Reference Poi
41、nts (IRPs). This clause describes the properties of an interface enabling a NM to monitor a 3G-telecommunication network including - if necessary - the managing EMs. To provide to the NM the Trace Management capability for the network implies that the NM and the EM have to agree on the following: Th
42、e identification of the NEs and UE where the Trace Session Activation is requested. The identification of the files containing the trace records for retrieval by a Trace Collection Entity. The identification of the subscriber or equipment shall be provided in the trace record files in case of subscr
43、iber and equipment trace. In case of Cell Traffic trace the cell identity shall be provided in the trace record file. In the case of trace in E-UTRAN, as neither the subscriber identity nor the equipment identity are provided to eNodeB, none of these identifiers are provided in the trace record file
44、s from the eNodeB. The connection to which subscriber or equipment is traced is made by the node that triggers the trace recording session to a Trace Collection Entity which collects the trace logs (indicated by the IP address in the Trace Sessions configuration parameters). The connection is done b
45、y the triggering node providing the identifier of the subscriber or equipment together with the Trace Reference and the Trace Recording Session Reference in a trace log file or a notification (as the Trace Reference and the Trace Recording Session Reference are included in the trace record files fro
46、m the eNodeBs). Notification of available files containing trace records for retrieval by a collection point indicated by an IP address. The Trace Collection Entity may be part of the NM. The network configuration (see the NRM IRPs in 3GPP TS 32.6xy and 32.7xy). ETSI ETSI TS 132 441 V13.0.0 (2016-03
47、)83GPP TS 32.441 version 13.0.0 Release 135.2 Managing Trace Sessions The IRPManager shall be able to request the IRPAgent to: Activate a Trace Session for a specific subscriber or equipment in a specific NE. The trace session activation shall be possible both for management based activation and for
48、 signalling based activation. The NM may schedule the activation. Note that no scheduling functionality is supported by the IRPAgent. The trace session activation shall also be possible for for cell traffic trace. Make the Trace Records in a file available to a Trace Collection Entity. The data form
49、at of the file shall be specified in the 3GPP defined trace specifications (See 3GPP TS 32.423 6). Emit a notification when a Trace Session is activated from the EM directly. Emit a notification when a Trace Recording Session was not started in the NE for any reason. Interrogate the configuration parameters and other information of a specific Trace Session. Interrogate the list of activated Trace Sessions in a specific NE. The Trace Session is identified by the Trace Reference. In case of ce
