1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelTelecommTrace Management Solutio(3GPP TS 32.4TECHNICAL SPECIFICATION132 446 V13.0.1 (2017mmunications system (Phase elecommunications System (LTE; munication management; nt Integration Reference Pointtion Set (SS) definitions .446 version 13.0.1
2、 Release 1317-01) e 2+) (GSM); (UMTS); int (IRP); 13) ETSI ETSI TS 132 446 V13.0.1 (2017-01)13GPP TS 32.446 version 13.0.1 Release 13Reference RTS/TSGS-0532446vd01 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
3、 Siret N 348 623 562 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 prin
4、t. The content of 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 Po
5、rtable Document Format (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 https:/por
6、tal.etsi.org/TB/ETSIDeliverableStatus.aspx 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, electron
7、ic or mechanical, including 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 Telecom
8、munications Standards Institute 2017. 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
9、 the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 446 V13.0.1 (2017-01)23GPP TS 32.446 version 13.0.1 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information perta
10、ining to these 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 Secreta
11、riat. Latest 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
12、the ETSI Web server) which are, 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 identiti
13、es, UMTS identities or GSM identities. 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 “
14、shall“, “shall not“, “should“, “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 u
15、sed in direct citation. ETSI ETSI TS 132 446 V13.0.1 (2017-01)33GPP TS 32.446 version 13.0.1 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.
16、2 Abbreviations . 8g34 Solution Set definitions 8g3Annex A (normative): CORBA Solution Set . 9g3A.1 Architectural features . 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Notification Services 9g3A.1.3 Push and Pull Style . 9g3A.1.4 Support multiple notifications in one push operation . 9g3A.1.5
17、Trace Management Notification Interface 9g3A.1.5.1 Method push (M) 9g3A.2 Mapping . 10g3A.2.1 Operation and Notification mapping 10g3A.2.2 Operation parameter mapping 10g3A.2.3 Notification parameter mapping . 12g3A.3 Solution Set definitions 18g3A.3.1 IDL definition structure 18g3A.3.2 IDL specific
18、ation (file name “TraceIRPConstDefs.idl“) 19g3A.3.3 IDL specification (file name TraceIRPSystem.idl) . 23g3A.3.4 IDL specification (file name TraceIRPNotifications.idl) 25g3Annex B (normative): XML definitions . 27g3B.1 Architectural Features 27g3B.1.1 Syntax for Distinguished Names 27g3B.1.2 Notifi
19、cation Services 27g3B.1.3 IOC definitions . 27g3B.2 Mapping . 27g3B.3 Solution Set definitions 27g3B.3.1 XML definition structure 27g3B.3.2 Graphical Representation . 28g3B.3.3 XML Schema tMIRPNotif.xsd . 30g3B.3.4 XML Schema tMIRPIOCs.xsd . 32g3Annex C (normative): SOAP Solution Set . 37g3C.1 Archi
20、tectural features . 37g3C.1.1 Syntax for Distinguished Names 37g3C.1.2 Notification Services 37g3C.1.3 Supported W3C specifications . 37g3C.1.4 Prefixes and namespaces 37g3ETSI ETSI TS 132 446 V13.0.1 (2017-01)43GPP TS 32.446 version 13.0.1 Release 13C.2 Mapping . 38g3C.2.1 Operation and notificatio
21、n mapping . 38g3C.2.2 Operation parameter mapping 38g3C.2.3 Notification parameter mapping . 40g3C.3 Solution Set definitions 41g3C.3.1 WSDL definition structure . 41g3C.3.2 Graphical Representation . 41g3C.3.3 WSDL specification TraceIRPSystem.wsdl 42g3Annex D (informative): Change history . 48g3Hi
22、story 49g3ETSI ETSI TS 132 446 V13.0.1 (2017-01)53GPP TS 32.446 version 13.0.1 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 followin
23、g 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 presented to TSG for information; 2 presented to TSG
24、 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 only changes have been incorporated in the documen
25、t. Introduction The present document is part of 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
26、“Trace Management Integration Reference Point (IRP): 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 information service necessary for the Telecommunication Manageme
27、nt (TM) of 3G systems. The TM principles 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 inv
28、estigations in problems solving or in case of optimization. ETSI ETSI TS 132 446 V13.0.1 (2017-01)63GPP TS 32.446 version 13.0.1 Release 131 Scope The present document specifies the Solution Set definitions for the IRP whose semantics are specified in Trace Management IRP: Information Service (3GPP
29、TS 32.442 5). This specification is applicable to UMTS networks and EPS networks. GSM Trace is outside of the scope of this specification. The conditions for supporting Network Sharing are stated in 3GPP TS 32.441 6. This Solution Set specification is related to 3GPP TS 32.442 V12. 0.X. 2 References
30、 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 revisio
31、ns 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 3GPP TR 21.905: “Voc
32、abulary 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.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 5 3
33、GPP TS 32.442: “Telecommunication management; Trace Management Integration Reference Point (IRP): Information Service (IS)“. 6 void. 7 3GPP TS 32.311: “Telecommunication management; Generic Integration Reference Point (IRP): Requirements“. 8 void. 9 3GPP TS 32.300: “Telecommunication management; Con
34、figuration Management (CM); Name convention for Managed Objects“. 10 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set definitions“ 11 void. 12 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:
35、/www.omg.org/technology/documents/ 13 3GPP TS 32.342: “Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 14 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 15 W3C REC-xmlschema-0-20010502: “XML Schema Part 0:
36、 Primer“. 16 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. ETSI ETSI TS 132 446 V13.0.1 (2017-01)73GPP TS 32.446 version 13.0.1 Release 1317 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 18 void. 19 void. 20 void. 21 W3C SOAP 1.1 specification (http:/www.w3.org/TR/20
37、00/NOTE-SOAP-20000508/) 22 W3C XPath 1.0 specification (http:/www.w3.org/TR/1999/REC-xpath-19991116) 23 W3C WSDL 1.1 specification (http:/www.w3.org/TR/2001/NOTE-wsdl-20010315) 24 W3C SOAP 1.2 specification (http:/www.w3.org/TR/soap12-part1/) 3 Definitions and abbreviations 3.1 Definitions For the p
38、urposes of the present document, the terms and definitions given in TR 21.905 1, 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. IRP document version number string (or “I
39、RPVersion“): See 3GPP TS 32.311 7. IRP: See 3GPP TS 32.101 2. IRPAgent: See 3GPP TS 32.102 3. IRPManager: See 3GPP TS 32.102 3. XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element, see 14. XML declaration: i
40、t specifies the version of XML being used, see 14. XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simp
41、ly of an XML empty-element tag; each XML element may contain other XML elements, see 14. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag direct
42、ly followed by an XML end-tag, or composed simply of an XML empty-element tag, see 14. XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag, see 1
43、4. XML start-tag: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML element, see 14. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element, see
44、 14. XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element, see 14. XML attribute specification: has a name and a value, see 14. ETSI ETSI TS 132 446 V13.0.1 (2017-01)83GPP TS 32.446 version 13.0.1 Release 13
45、DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD, see 14. XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conform with this XML schema; through the
46、 use of XML namespaces several XML schemas can be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas, see 15, 16 and 17. XML namespace: enables qualifying element and attribute names used in XML documents by ass
47、ociating them with namespaces identified by different XML schemas, see 15, 16 and 17. XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concrete type or the derivation base type for an XML element type or for another XML complex type; ultimately defin
48、es constraints for an XML element on its XML attribute specifications and/or its XML content, see 15, 16 and 17. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribu
49、te specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type, see 15, 16 and 17. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1, in 3GPP TS 32.101 2, 3GPP TS 32.102 3, 3GPP TS 32.150 4, and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation,
