1、 ETSI TS 132 435 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Performance measurement; eXtensible Markup Language (XML) file format definition (3GPP TS 32.435 version 15.0.0 Releas
2、e 15) TECHNICAL SPECIFICATION ETSI ETSI TS 132 435 V15.0.0 (2018-07)13GPP TS 32.435 version 15.0.0 Release 15Reference RTS/TSGS-0532435vF00 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 000
3、17 - 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 el
4、ectronic 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 Format (
5、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:/portal.etsi.org/TB/ETSIDeli
6、verableStatus.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, electronic or mechanical, includ
7、ing 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. ETSI 2018. All rights reserved. DECTTM,
8、PLUGTESTSTM, UMTSTMand 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 log
9、o are trademarks registered and owned by the GSM Association. ETSI ETSI TS 132 435 V15.0.0 (2018-07)23GPP TS 32.435 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 informatio
10、n pertaining 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
11、Secretariat. 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 upda
12、tes on the ETSI Web 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 b
13、eing the property 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 Specific
14、ation (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 references to the corresponding ETSI deliverables
15、. 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“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted
16、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 ETSI TS 132 435 V15.0.0 (2018-07)33GPP TS 32.435 version 15.0.0 Release 15Contents Intellectual
17、Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 XML file format definition . 6g34.1 Mapping table . 6g34.2 XML schema based XML file format definition
18、 8g34.2.1 Measurement collection data file XML diagram 8g34.2.2 Measurement collection data file XML schema . 9g34.2.3 Measurement collection data file XML header . 11g3Annex A (informative): Examples . 12g3A.1 XML schema based XML measurement report file without use of optional positioning attribut
19、es on measurement types and results 12g3A.2 XML schema based XML measurement report file with use of optional positioning attributes on measurement types and results . 13g3A.3 XML schema based XML measurement report file with use of optional measInfoId attribute . 14g3Annex B (informative): Void . 1
20、5g3Annex C (informative): Change history . 16g3History 17g3ETSI ETSI TS 132 435 V15.0.0 (2018-07)43GPP TS 32.435 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to conti
21、nuing 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 and an increase in version number as follows: Version x.y.z where: x the first digit: 1 pre
22、sented 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 enhancements, corrections, updates, etc. z the third digit is incremented when editorial o
23、nly changes have been incorporated in the document. 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: TS 32.432: “Performance measureme
24、nt: File format definition“; TS 32.435: “Performance measurement: eXtensible Markup Language (XML) file format definition“; TS 32.436: “Performance measurement: Abstract Syntax Notation 1 (ASN.1) file format definition“. The present document is part of a set of specifications, which describe the req
25、uirements and information model necessary for the standardised Operation, Administration and Maintenance (OA Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Concept
26、and requirements“. 4 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 5 3GPP TS 32.432: “Telecommunication management; Performance measurement: File format definition “. 6 3GPP TS 32.300: “Telecommunication management; Configuration
27、Management (CM); Name convention for Managed Objects“. 7 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 8 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 9 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 10 W3C REC-xmlschema-2-20010502: “XML
28、Schema Part 2: Datatypes“. 11 W3C REC-xml-names-19990114: “Namespaces in XML“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: network Element Manager (EM): provides a package of end-user functions for management of
29、 a set of closely related types of Network Elements. These functions can be divided into two main categories: - Element Management Functions for management of Network Elements on an individual basis. These are basically the same functions as supported by the corresponding local terminals. - Sub-Netw
30、ork Management Functions that are related to a network model for a set of Network Elements constituting a clearly defined sub-network, which may include relations between the Network Elements. This ETSI ETSI TS 132 435 V15.0.0 (2018-07)63GPP TS 32.435 version 15.0.0 Release 15model enables additiona
31、l functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning). Network Manager (NM): provides a package of end-user functions with the responsibility for the management of a network, mainly as suppo
32、rted by the EM(s) but it may also involve direct access to the Network Elements. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi-technology Network Elements. Operations System (OS): generic management system, indepe
33、ndent of its location level within the management hierarchy. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: 3G 3rdGeneration EM Element Manager GSM Global System for Mobile communications IRP Integration Reference Point NE Network Element NM Network Ma
34、nagerPLMN Public Land Mobile Network PM Performance Management 4 XML file format definition This clause describes the format of measurement result files that can be transferred from the network (NEs or EM) to the NM. The XML file format definition is based on XML schema (see 8, 9, 10 and 11). The XM
35、L file format definitions implement the measurement result structure and parameters defined in clauses 5.2 and 5.3 of 3GPP TS 32.401 3. 4.1 Mapping table Table 4.1 maps the file content items in the 3GPP TS 32.432(5) document to those used in the XML schema based file format definitions. XML tag att
36、ributes are useful where data values bind tightly to its parent element. They have been used where appropriate. Table 4.1 Mapping of File Content Items to XML tags File Content Item XML schema based XML tag Description measDataCollection measCollecFile measFileHeader fileHeader measData measDatameas
37、FileFooter fileFooter fileFormatVersion fileHeader fileFormatVersion senderName fileHeader dnPrefix and fileSender localDn For the XML schema based XML format, the DN is split into the DN prefix and the Local DN (LDN) (see 3GPP TS 32.300 6). XML attribute specification “dnPrefix“ may be absent in ca
38、se the DN prefix is not configured in the sender. XML attribute specification “localDn“ may be absent in case the LDN is not configured in the sender. senderType fileSender elementType For the XML schema based XML format, XML attribute specification “elementType“ may be absent in case the “senderTyp
39、e“ is not configured in the sender. vendorName fileHeader vendorName For the XML schema based XML format, XML attribute specification “vendorName“ may be absent in case the “vendorName“ is not configured in the sender. collectionBeginTime measCollec beginTime neId managedElementETSI ETSI TS 132 435
40、V15.0.0 (2018-07)73GPP TS 32.435 version 15.0.0 Release 15File Content Item XML schema based XML tag Description neUserName managedElementuserLabel For the XML schema based XML format, XML attribute specification “userLabel“ may be absent in case the “nEUserName“ is not configured in the CM applicat
41、ions. neDistinguishedName fileHeader dnPrefix and managedElement localDn For the XML schema based XML format, the DN is split into the DN prefix and the Local DN (LDN) (see 3GPP TS 32.300 6). XML attribute specification “localDn“ may be absent in case the LDN is not configured in the CM applications
42、. neSoftwareVersion managedElement swVersion For the XML schema based XML format, XML attribute specification “swVersion“ may be absent in case the “nESoftwareVersion“ is not configured in the CM applications. measInfo measInfo measInfoId measInfoIdmeasTimeStamp granPeriod endTime jobId job jobIdgra
43、nularityPeriod granPeriod duration For the XML schema based XML format, the value of XML attribute specification “duration“ shall use the truncated representation “PTnS“ (see 10). reportingPeriod repPeriod duration For the XML schema based XML format, the value of XML attribute specification “durati
44、on“ shall use the truncated representation “PTnS“ (see 10). measTypes measTypes or measType For the XML schema based XML format, depending on senders choice for optional positioning presence, either XML element “measTypes“ or XML elements “measType“ will be used. measValues measValue measObjInstId m
45、easValue measObjLdn measResults measResults or r For the XML schema based XML format, depending on senders choice for optional positioning presence, either XML element “measResults“ or XML elements “r“ will be used. suspectFlag suspect timeStamp measCollec endTime There is no corresponding File Cont
46、ent Item. measType p An optional positioning XML attribute specification of XML element “measType“ (XML schema based), used to identify a measurement type for the purpose of correlation to a result. The value of this XML attribute specification is expected to be a non-zero, non-negative integer valu
47、e that is unique for each instance of XML element “measType“ that is contained within the measurement data collection file. There is no corresponding File Content Item. r p An optional positioning XML attribute specification of XML element “r“, used to correlate a result to a measurement type. The v
48、alue of this XML attribute specification should match the value of XML attribute specification “p“ of the corresponding XML element “measType“ (XML schema based). ETSI ETSI TS 132 435 V15.0.0 (2018-07)83GPP TS 32.435 version 15.0.0 Release 154.2 XML schema based XML file format definition 4.2.1 Meas
49、urement collection data file XML diagram Figure 4.1 describes the XML element structure of the measurement collection data file. Figure 4.1: XML diagram of the measurement collection data file ETSI ETSI TS 132 435 V15.0.0 (2018-07)93GPP TS 32.435 version 15.0.0 Release 154.2.2 Measurement collection data file XML schema The following XML schema measCollec.xsd is the schema for measurement collection data XML files: ETSI ETSI TS 132 435 V15.0.0 (2018-07)103GPP TS 32.435 version 15.0.0 Release 15ETSI ETSI TS 132 435 V15.0.0 (2018-07)113G
