1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommPerformance mea(3GPP TS 32.4TECHNICAL SPECIFICATION132 432 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; easurement: File format defin.432 version 13.0.0 Release 1316-02) hase 2+); (UMTS); fin
2、ition 13) ETSI ETSI TS 132 432 V13.0.0 (2016-02)13GPP TS 32.432 version 13.0.0 Release 13Reference RTS/TSGS-0532432vd00 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 Assoc
3、iation 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 prin
4、t 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 on
5、 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/status/status.asp If you find
6、 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 and microfilm
7、 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 Institute 2016. All rights reser
8、ved. 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 Marks registered and owned by
9、the GSM Association. ETSI ETSI TS 132 432 V13.0.0 (2016-02)23GPP TS 32.432 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 IPRs, if any, is publicly ava
10、ilable 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 available on the ETSI Web ser
11、ver (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 are, or may be, or may beco
12、me, 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 identities. These should be
13、 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“, “should not“, “may“, “n
14、eed 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 ETSI TS 132 432 V13.0.0 (
15、2016-02)33GPP TS 32.432 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 Measurement Report File Format
16、. 6g34.1 File Content description . 8g35 Measurement Report File Conventions and Transfer Procedure 10g35.1 Conventions 10g35.1.1 File generation 10g35.1.1.1 NE based approach 10g35.1.1.2 EM based approach . 10g35.1.2 File naming . 11g35.2 File transfer procedure 12g3Annex A (informative): The table
17、 oriented file format structure 13g3A.1 Graphical representation of the table structure . 13g3Annex B (informative): Change history . 14g3History 15g3ETSI ETSI TS 132 432 V13.0.0 (2016-02)43GPP TS 32.432 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGener
18、ation 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
19、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 second digit is incremented for all changes of substance, i.e. technical
20、 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 Partnership Project: Technical Specification Group Services and System As
21、pects; Telecommunication management, as identified below: TS 32.432: “Performance measurement; 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 d
22、efinition“. The present document is part of a set of specifications, which describe the requirements and information model necessary for the standardised Operation, Administration and Maintenance (OA Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architectu
23、re“. 3 3GPP TS 32.401: “Telecommunication management; Performance Management (PM); Concept and requirements“. 4 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 5 3GPP TS 25.442: “UTRAN Implementation Specific O Configuration Managem
24、ent (CM); Name convention for Managed Objects“. 7 3GPP TS 52.402: “Telecommunication management; Performance Management (PM); Performance measurements - GSM“. 8 Void. 9 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point
25、 (IRP): Network Resource Model (NRM)“. 10 ITU-T Recommendation X.680: “Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 11 ISO8601:2000(E) Data elements and interchange formats Information interchange Representation of dates and times“. 12 32.405: “Per
26、formance Management (PM); Performance measurements; Universal Terrestrial Radio Access Network (UTRAN)“. 13 32.406 : “Performance Management (PM); Performance measurements; Core Network (CN) Packet Switched (PS) domain“. 14 32.407: “Performance Management (PM); Performance measurements; Core Network
27、 (CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM“. ETSI ETSI TS 132 432 V13.0.0 (2016-02)63GPP TS 32.432 version 13.0.0 Release 1315 32.408 : “Performance Management (PM); Performance measurements; Teleservice“. 16 32.409: “Performance Management (PM); Performance measurements; IP Mult
28、imedia Subsystem (IMS)“. 17 32.425: “Performance Management (PM); Performance measurements; Evolved Universal Terrestrial Radio Access Network (E-UTRAN)“. 18 32.426: “Performance Management (PM); Performance measurements; Evolved Packet Core (EPC) network“. 19 32.452 : “Performance Management (PM);
29、Performance measurements; Home Node B (HNB) Subsystem HNS“. 20 32.453 : “Performance Management (PM); Performance measurements Home enhanced Node B (HeNB) Subsystem (HeNS)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions
30、apply: network Element Manager (EM): provides a package of end-user functions for management of 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
31、 are basically the same functions as supported by the corresponding local terminals. - Sub-Network 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 model e
32、nables additional 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,
33、 mainly as supported 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 managemen
34、t system, independent 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 NE Network ElementNM Network Manager PLMN Public
35、 Land Mobile Network PM Performance Management 4 Measurement Report File Format This clause describes the format of measurement result files that can be transferred from the network (NEs or EM) to the NM. ETSI ETSI TS 132 432 V13.0.0 (2016-02)73GPP TS 32.432 version 13.0.0 Release 13The following co
36、nditions have been considered in defining this file format: Since the files are transferred via a machine-machine interface, the files applying the format definitions should be machine-readable using standard tools. The file format should be independent of the data transfer protocol used to carry th
37、e file from one system to another. The file format should be generic across PLMN systems. The file format should be flexible enough to include all possible measurement types, i.e. those specified within clause 6 as well as measurements defined within other standards bodies, or vendor specific measur
38、ement types. The file format should not impose any dependency between granularity periods for the generation of measurement results and file upload cycles for the file transfer from the network to the NM. The file format should be flexible enough to support both the NE-based and the EM-based approac
39、hes, as discussed in Chapter 5, clause 5.1.1 of the present document. The file format should be usable for other interfaces than Itf-N if required. The measurement file header could be augmented to indicate this other usage, however this would be a non-standard extension. In the ASN.1 (see ITU-T Rec
40、ommendation X.680 10) file format definition this is accommodated by the use of the ellipsis notation. XML schema allows such additions through insertion of extra schema elements through the provider of the non-standard extension. ETSI ETSI TS 132 432 V13.0.0 (2016-02)83GPP TS 32.432 version 13.0.0
41、Release 134.1 File Content description Table 4.1 lists all the file content items. It also provides an explanation of the individual items. Table 4.1 File Content Description File Content Item Description measDataCollection This is the top-level tag, which identifies the file as a collection of meas
42、urement data. The file content is made up of a header (“measFileHeader“), the collection of measurement result items (“measData“), and a measurement file footer (“measFileFooter“). measFileHeader This is the measurement result file header to be inserted in each file. It includes a version indicator,
43、 the name, type and vendor name of the sending network node, and a time stamp (“collectionBeginTime“). measData The “measData“ construct represents the sequence of zero or more measurement result items contained in the file. It can be empty in case no measurement data can be provided. The individual
44、 “measData“ elements can appear in any order. Each “measData“ element contains the name of the NE (“nEId“) and the list of measurement results pertaining to that NE (“measInfo“). measFileFooter The measurement result file footer to be inserted in each file. It includes a time stamp, which refers to
45、the end of the overall measurement collection interval that is covered by the collected measurement results being stored in this file. fileFormatVersion This parameter identifies the file format version applied by the sender. The format version defined in the present document shall be the abridged n
46、umber and version of this 3GPP document (see below). The abridged number and version of a 3GPP document is constructed from its version specific full reference “3GPP (yyyy-mm)“ by: - removing the leading “3GPP TS“ - removing everything including and after the version third digit, representing editor
47、ial only changes, together with its preceding dot character - from the resulting string, removing leading and trailing white space, replacing every multi character white space by a single space character and changing the case of all characters to uppercase. senderName The senderName uniquely identif
48、ies the NE or EM that assembled this measurement file by its Distinguished Name (DN), according to the definitions in 3GPP TS 32.300 6. In the case of the NE-based approach, it is identical to the senders “nEDistinguishedName“. senderType This is a user configurable identifier of the type of network
49、 node that generated the file, e.g. NodeB, EM, SGSN. The string may be empty (i.e. string size =0) in case the “senderType“ is not configured in the sender. vendorName The “vendorName“ identifies the vendor of the equipment that provided the measurement file. The string may be empty (i.e. string size =0) if the “vendorName“ is not configured in the sender. collectionBeginTime The “collectionBeginTime“ is a time stamp that refers to the start of the first measurement collection interval (granularity period) that is
