ETSI TS 132 445-2012 Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Trace Management Integration Reference Point (IRP) eXtensible Markup Languag.pdf

1、 ETSI TS 132 445 V9.2.0 (2012-03) Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Trace Management Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition (3GPP TS 32.445 version 9.2.0 Release 9) Technical Specification ETSI ET

2、SI TS 132 445 V9.2.0 (2012-03)13GPP TS 32.445 version 9.2.0 Release 9Reference RTS/TSGS-0532445v920 Keywords 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 Association but non lucratif

3、enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in c

4、ontents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the doc

5、ument 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/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi

6、.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2012. All rights reserved. DECTTM, PLUGTESTSTM,

7、 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 registered and owned by the GSM Association. ETSI

8、 ETSI TS 132 445 V9.2.0 (2012-03)23GPP TS 32.445 version 9.2.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and

9、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 available on the ETSI Web server (http:/ipr.etsi.org). Pu

10、rsuant 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, or may be, or may become, essential to the present d

11、ocument. 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 identities. These should be interpreted as being referenc

12、es 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. ETSI ETSI TS 132 445 V9.2.0 (2012-03)33GPP TS 32.445 version 9.2.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Fo

13、reword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Trace Management IRP XML Definitions . 7g34.1 Trace Management IRP notifications XML definition structure 7g34.2 Trace Management IRP XML Schema for notifications 7

14、g34.3 Trace Management IRP XML Schema for IOCs . 8g34.4 Trace IRP XML File Name Conventions . 10g3Annex A (normative): Void . 11g3Annex B (informative): Void . 12g3Annex C (informative): Change history . 13g3History 14g3ETSI ETSI TS 132 445 V9.2.0 (2012-03)43GPP TS 32.445 version 9.2.0 Release 9Fore

15、word 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 contents of the present document, it will be

16、 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 document under change control. y the secon

17、d 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 a TS-family covering the 3rdGeneration Partne

18、rship 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 (IRP): Information Service (IS)“ 32.443 “Trace M

19、anagement Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“ 32.445: “Trace Management Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“ The present document is part of a TS-family which describes the requ

20、irements and information model necessary for the Telecommunication Management (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 addi

21、tional information source to Performance Measurements and allows deeper investigations in problems solving or in case of optimization. ETSI ETSI TS 132 445 V9.2.0 (2012-03)53GPP TS 32.445 version 9.2.0 Release 91 Scope The present document is the eXtensible Markup Language (XML) file format definiti

22、on of Trace IRP for the IRP whose semantics is specified in Trace IRP: Information Service (3GPP TS 32.442 3). This XML Definitions specification defines the XML syntax of the Trace IRP XML Data File for the notifications related to Trace IRP. The XML file definitions for a trace data file can be fo

23、und in Annex A of 3GPP TS 32.423 4. This XML File Format Definition specification is related to 3GPP TS 32.442 V9.0.X. 2 References The following documents contain provisions that, through reference in this text, constitute provisions of the present document. References are either specific (identifi

24、ed 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 reference

25、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.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.342: “Telecommunication managem

26、ent; File Transfer (FT) Integration Reference Point (IRP): Information Service (IS)“. 4 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 5 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 6 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 7 W3C R

27、EC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 8 W3C REC-xml-names-19990114: “Namespaces in XML“. 10 3GPP TS 32.441: “Telecommunication management; Trace Management Integration Reference Point (IRP): Requirements“. 11 3GPP TS 32.442: “Telecommunication management; Trace Management Integrat

28、ion Reference Point (IRP): Information Service (IS)“. 12 3GPP TS 32.422: “Telecommunication management; Subscriber and equipment trace; Trace control and configuration management” 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and defini

29、tions apply: IRP: See 3GPP TS 32.101 1. IRPAgent: See 3GPP TS 32.102 2. ETSI ETSI TS 132 445 V9.2.0 (2012-03)63GPP TS 32.445 version 9.2.0 Release 9IRPManager: See 3GPP TS 32.102 2. XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration foll

30、owed by a root XML element, see 4. XML declaration: it specifies the version of XML being used, see 4. 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

31、element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements, see 4. 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 co

32、mposed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag, see 4. 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 be

33、tween its XML start-tag and its XML end-tag, see 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 4. XML end-tag: the end of a non-empty XML element is marked by an XML end

34、-tag containing the name of the XML element, see 4. 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 4. XML attribute specification: has a name and a value, see 4. DTD: defines structure and content

35、 constraints to be respected by an XML document to be valid with regard to this DTD, see 4. 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 use of XML namespaces several XML

36、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 5, 6 and 7. XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identifi

37、ed by different XML schemas, see 5, 6 and 7. 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 defines constraints for an XML element on its

38、XML attribute specifications and/or its XML content, see 5, 6 and 7. 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 attribute specifications and/or its XML content; ca

39、n also be the concrete type or the derivation base type for another XML element type, see 5, 6 and 7. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: EM Element Manager IRP Integration Reference Point IS Information Service (see 3GPP TS 32.101 1) Itf-N

40、Interface N NE Network Element TS Technical Specification XML eXtensible Mark-up Language ETSI ETSI TS 132 445 V9.2.0 (2012-03)73GPP TS 32.445 version 9.2.0 Release 94 Trace Management IRP XML Definitions 4.1 Trace Management IRP notifications XML definition structure This section provides XML defin

41、itions of Trace Management IRP notifications as defined in 3GPP TS 32.442 3. Editors Note; Diagram to be provided. 4.2 Trace Management IRP XML Schema for notifications ETSI ETSI TS 132 445 V9.2.0 (2012-03)83GPP TS 32.445 version 9.2.0 Release 94.3 Trace Management IRP XML Schema for IOCs ETSI ETSI

42、TS 132 445 V9.2.0 (2012-03)93GPP TS 32.445 version 9.2.0 Release 9ETSI ETSI TS 132 445 V9.2.0 (2012-03)103GPP TS 32.445 version 9.2.0 Release 94.4 Trace IRP XML File Name Conventions For Trace IRP XML File Name Conventions the generic file name definitions as specified by the FT IRP apply (see 3). E

43、TSI ETSI TS 132 445 V9.2.0 (2012-03)113GPP TS 32.445 version 9.2.0 Release 9Annex A (normative): Void ETSI ETSI TS 132 445 V9.2.0 (2012-03)123GPP TS 32.445 version 9.2.0 Release 9Annex B (informative): Void ETSI ETSI TS 132 445 V9.2.0 (2012-03)133GPP TS 32.445 version 9.2.0 Release 9Annex C (informa

44、tive): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Cat Old New Jun 2007 SA_36 SP-070290 - - Submitted to SA#36 for Approval - 1.0.0 7.0.0 Dec 2008 SA_42 SP-080846 0001 - Adding EPS related modifications to Trace IRP XML schema B 7.0.0 8.0.0 Sep 2009 SA_45 SP-090534 0002

45、- Alignment of Trace IRP XML definitions with TS 32.422 F 8.0.0 8.1.0 Sep 2009 SA-45 SP-090627 0003 - Updates to 32.445 for SOAP SS and to align with 32.422 and 32.442. C 8.1.0 9.0.0 Dec 2009 SA-46 SP-090719 0004 - Discontinue from Rel-9 onwards the XML schema extraction and storage, remove its refe

46、rence in the informative Annex containing the link to the XML schema folder F 9.0.0 9.1.0 March 2012 SA-55 SP-120044 0006 - Correct syntax error in XML schema tMIRPIOCs.xsd F 9.1.0 9.2.0 ETSI ETSI TS 132 445 V9.2.0 (2012-03)143GPP TS 32.445 version 9.2.0 Release 9History Document history V9.1.0 January 2010 Publication V9.2.0 March 2012 Publication