|
TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Performance measurement: File format definition
(3GPP TS 32.432 version 15.1.0 Release 15)
---------------------- Page: 1 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 1 ETSI TS 132 432 V15.1.0 (2019-04)
Reference
RTS/TSGS-0532432vf10
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
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
The present document can be downloaded from:
The present document may be made available in electronic versions and/or in print. 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 prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
If you find errors in the present document, please send your comment to one of the following services:
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic 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.
© ETSI 2019.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM TM
3GPP and LTE are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
---------------------- Page: 2 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 2 ETSI TS 132 432 V15.1.0 (2019-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
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 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 updates 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 being 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 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 references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
.
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 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
---------------------- Page: 3 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 3 ETSI TS 132 432 V15.1.0 (2019-04)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 4
Introduction . 4
1 Scope . 5
2 References . 5
3 Definitions and abbreviations . 6
3.1 Definitions . 6
3.2 Abbreviations . 6
4 Measurement Report File Format . 7
4.1 File Content description . 8
5 Measurement Report File Conventions and Transfer Procedure . 10
5.1 Conventions . 10
5.1.1 File generation . 10
5.1.1.1 NE based approach . 10
5.1.1.2 EM based approach . 10
5.1.2 File naming . 11
5.2 File transfer procedure . 12
Annex A (informative): The table oriented file format structure . 13
A.1 Graphical representation of the table structure . 13
Annex B (informative): Change history . 14
History . 15
ETSI
---------------------- Page: 4 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 4 ETSI TS 132 432 V15.1.0 (2019-04)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project: Technical Specification
Group Services and System Aspects; 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 definition".
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&M) of a multi-vendor PLMN.
During the lifetime of a PLMN, its logical and physical configuration will undergo changes of varying degrees and
frequencies in order to optimise the utilisation of the network resources. These changes will be executed through
network configuration management activities and/or network engineering, see 3GPP TS 32.600 [4].
Many of the activities involved in the daily operation and future network planning of a PLMN network require data on
which to base decisions. This data refers to the load carried by the network and the grade of service offered. In order to
produce this data performance measurements are executed in the NEs, which comprise the network. The data can then
be transferred to an external system, e.g. an Operations System (OS) in TMN terminology, for further evaluation. The
purpose of the present document and the other related 3GPP TSs listed above is to describe the mechanisms involved in
the collection of the data.
ETSI
---------------------- Page: 5 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 5 ETSI TS 132 432 V15.1.0 (2019-04)
1 Scope
The present document describes the general semantics of performance measurement result and collection. It defines the
report file format, report file conventions and the file transfer procedure. Clause 4 specifies the file format for the bulk
transfer of performance measurement results to the NM, while clause 5 discusses the file transfer procedure utilised on
that interface.
The present document does not give the definition of any specific file format – such as XML and ASN.1, which will be
given in Performance Measurement eXtensible Markup Language (XML) File Format Definition 3GPP TS 32.435 and
Performance Measurement Abstract Syntax Notation 1 (ASN.1) File Format Definition 3GPP TS 32.436.
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, 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 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.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&M Transport".
[6] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[7] 3GPP TS 52.402: "Telecommunication management; Performance Management (PM);
Performance measurements - GSM".
[8] Void.
[9] Void.
[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] 3GPP TS 32.405: "Performance Management (PM); Performance measurements; Universal
Terrestrial Radio Access Network (UTRAN)".
[13] 3GPP TS 32.406 : "Performance Management (PM); Performance measurements; Core Network
(CN) Packet Switched (PS) domain".
[14] 3GPP TS 32.407: "Performance Management (PM); Performance measurements; Core Network
(CN) Circuit Switched (CS) domain; UMTS and combined UMTS/GSM".
[15] 3GPP TS 32.408 : "Performance Management (PM); Performance measurements; Teleservice".
ETSI
---------------------- Page: 6 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 6 ETSI TS 132 432 V15.1.0 (2019-04)
[16] 3GPP TS 32.409: "Performance Management (PM); Performance measurements; IP Multimedia
Subsystem (IMS)".
[17] 3GPP 32.425: "Performance Management (PM); Performance measurements; Evolved Universal
Terrestrial Radio Access Network (E-UTRAN)".
[18] 3GPP TS 32.426: "Performance Management (PM); Performance measurements; Evolved Packet
Core (EPC) network".
[19] 3GPP TS 32.452 : "Performance Management (PM); Performance measurements; Home Node B
(HNB) Subsystem HNS".
[20] 3GPP TS 32.453 : "Performance Management (PM); Performance measurements Home enhanced
Node B (HeNB) Subsystem (HeNS)".
[21] 3GPP 28.552: "Management and orchestration; 5G performance measurements”.
[22] 3GPP 32.404: "Performance Management (PM); Performance measurements; Definitions and
template".
[23] 3GPP TS 28.622: "Telecommunication management; Generic Network Resource Model (NRM)
Integration Reference Point (IRP); Information Service (IS)".
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 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-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 enables 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, 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 management system, independent of its location level within the management
hierarchy.
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
rd
3G 3 Generation
5GC 5G Core network
EM Element Manager
GSM Global System for Mobile communications
NE Network Element
NM Network Manager
PLMN Public Land Mobile Network
PM Performance Management
ETSI
---------------------- Page: 7 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 7 ETSI TS 132 432 V15.1.0 (2019-04)
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.
The following conditions 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 the 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 measurement 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 approaches, 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 Recommendation 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
---------------------- Page: 8 ----------------------
3GPP TS 32.432 version 15.1.0 Release 15 8 ETSI TS 132 432 V15.1.0 (2019-04)
4.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 measurement 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, 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 "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 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 number 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 editorial 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 identifies 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 sender's "nEDistinguishedName".
senderType This is a user configurable identifier of the type of network 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 covered by the collected measurement results that
are stored in this file.
neId The unique identification of the NE in the system. It includes the user name ("nEUserName"),
the distinguished name ("nEDistinguishedName") and the software version
("nESoftwareVersion") of the NE.
neUserName This is the user definable name (
...