ETSI TS 132 584 V17.0.0 (2022-04)

Universal Mobile Telecommunications System (UMTS); Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS) (3GPP TS 32.584 version 17.0.0 Release 17)

RTS/TSGS-0532584vh00

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 29-Apr-2022

Standards Content (Sample)

ETSI TS 132 584 V17.0.0 (2022-04)






TECHNICAL SPECIFICATION
Universal Mobile Telecommunications System (UMTS);
Telecommunication management;
Home Node B (HNB) Operations, Administration, Maintenance
and Provisioning (OAM&P);
XML definitions for Type 1 interface HNB to HNB Management
System (HMS)
(3GPP TS 32.584 version 17.0.0 Release 17)

---------------------- Page: 1 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 1 ETSI TS 132 584 V17.0.0 (2022-04)

Reference
RTS/TSGS-0532584vh00
Keywords
UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

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
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
https://portal.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
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure Program:
https://www.etsi.org/standards/coordinated-vulnerability-disclosure
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
and/or governmental
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
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 2022.
All rights reserved.

ETSI

---------------------- Page: 2 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 2 ETSI TS 132 584 V17.0.0 (2022-04)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are 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 Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
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.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its

Members. 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.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 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 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.584 version 17.0.0 Release 17 3 ETSI TS 132 584 V17.0.0 (2022-04)
Contents
Intellectual Property Rights . 2
Legal Notice . 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 CM data format definition . 6
4.1 File content description . 6
4.2 XML schema based CM data file format definition . 8
4.2.1 CM data file XML diagram . 8
4.2.2 CM data file XML schema . 10
4.2.3 CM data file XML header . 21
5 PM data format definition . 21
5.1 Mapping table . 21
5.2 XML schema based PM data file format definition . 23
5.2.1 PM data file XML diagram . 23
5.2.2 PM data file XML schema . 23
5.2.2 PM data file XML header . 23
Annex A (informative): Examples . 24
A.1 XML schema based CM data file . 24
A.2 XML schema based PM data file . 24
Annex B (informative): Void . 25
Annex C (informative): Change history . 26
History . 27

ETSI

---------------------- Page: 4 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 4 ETSI TS 132 584 V17.0.0 (2022-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:
32.581: "Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and
Provisioning (OAM&P); Concepts and requirements for Type 1 interface HNB to HNB Management System
(HMS)"
32.582: "Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and
Provisioning (OAM&P); Information model for Type 1 interface HNB to HNB Management System (HMS)"
32.583: "Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and
Provisioning (OAM&P); Procedure flows for Type 1 interface HNB to HNB Management System (HMS)"
32.584: "Telecommunications management; Home Node B (HNB) Operations, Administration, Maintenance and
Provisioning (OAM&P); XML definitions for Type 1 interface HNB to HNB Management System (HMS)"
ETSI

---------------------- Page: 5 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 5 ETSI TS 132 584 V17.0.0 (2022-04)
1 Scope
The present document describes the data format for Configuration Management and Performance Management for
Home Node B (HNB). The XML definitions captured in this document shall be met via Type 1 interface between HNB
and HNB Management System (HMS).
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 TR 21.905: "Vocabulary 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.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[5] Void.
[6] 3GPP TR R3.020, Home (e)NodeB
[7] TR-069 Amendment 2, CPE WAN Management Protocol v1.1, Broadband Forum
[8] 3GPP TS 32.435: "Telecommunication management; Performance measurement: eXtensible
Markup Language (XML) file format definition"
[9] 3GPP TS 32.582: "Telecommunications management; Home Node B (HNB) Operations,
Administration, Maintenance and Provisioning (OAM&P); Information model for Type 1 interface
HNB to HNB Management System (HMS)"
[10] W3C REC-xml-20001006: "Extensible Markup Language (XML) 1.0 (Second Edition)".
[11] W3C REC-xmlschema-0-20010502: "XML Schema Part 0: Primer".
[12] W3C REC-xmlschema-1-20010502: "XML Schema Part 1: Structures".
[13] W3C REC-xmlschema-2-20010502: "XML Schema Part 2: Datatypes".
[14] W3C REC-xml-names-19990114: "Namespaces in XML".
[15] TR-157 Amendment 1 “Component Objects for CWMP”, Broadband Forum.
[16] TR-098 Amendment 2, "Internet Gateway Device Data Model for TR-069", Broadband Forum
[17] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic
network resources Integration Reference Point (IRP): Network Resource Model (NRM)".
[18] 3GPP TS 32.772: ”Telecommunication management; Home Node B (HNB) Subsystem (HNS); Integration
Reference Point (IRP); Information Service (IS)”
[19] 3GPP TS 22.220: “Service requirements for Home Node B (HNB) and Home eNode B (HeNB)”
ETSI

---------------------- Page: 6 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 6 ETSI TS 132 584 V17.0.0 (2022-04)
[20] 3GPP TS 32.432: “Telecommunication management; Performance measurement: File format definition”

3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Home NodeB, 3G Home NodeB: These terms, their derivations and abbreviations are used synonymously throughout
this document.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
DM Domain Manager
EM Element Manager
FFS For Further Study
HNB Home Node B
HMS HNB Management System
IP Internet Protocol
LTE Long Term Evolution
MME Mobile Management Entity
NGMN Next Generation Mobile Networks
PnP Plug and Play
SAE System Architecture Evolution
SON Self-Organising Networks
TBD To Be Discussed
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Radio Access Network
4 CM data format definition
This clause describes the format of Configuration Management data.
4.1 File content description
Table 4.1 lists all the file content items, provides and explanation of the individual items, and maps the file content
items to those used in the XML schema based file format definitions. XML tag attributes are useful where data values
bind tightly to its parent element. They have been used where appropriate.
Table 4.1 File Content Description and Mapping of File Content Items to XML tags
File Content Item XML schema based Description
XML tag
configDataCollection configDataFile This is the top-level tag, which identifies the file as a collection of
config data. The file content is made up of a header
("configFileHeader"), the collection of configuration items
("configData"), and a configfile footer ("configFileFooter").
configFileHeader fileHeader This is the configuration data file header to be inserted in each
file. It includes a version indicator, the sendor name, and vendor
name of the sending network node.
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 7 ETSI TS 132 584 V17.0.0 (2022-04)
File Content Item XML schema based Description
XML tag
configData configData The "configData" construct represents the sequence of zero or
more configuration parameter items contained in the file.
Each "configData" element contains the name of the NE ("nEId")
and the list of parameters to be created,modified or deleted
which pertaining to that NE
The "configData" consists of DeviceData, DiagnosticsData, and
FAPServiceData
configFileFooter fileFooter The configuration data file footer to be inserted in each file. It
includes a time stamp, which refers to the time when the file is
closed for sending to the NE.
fileFormatVersion fileHeader This parameter identifies the file format version applied by the
fileFormatVersion 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.
e.g. "32.584 V8.0"
senderName fileHeader senderName If this is a downloaded file from HMS to HNB, then this attribute
shall hold the DN of HMS whose name hierarchy is defined
section 6.2.1 of TS 32.772 [18].

Example:
"DC=a1.companyNN.com,SubNetwork=1,ManagementNode=6,
HMSFunction=H3WT2"
If this is an uploaded file from HNB to HMS, then this attribute
shall hold the DN of HNB. See Note 1 of Table 5.1.

See TS 32.300 [4] for definition of DN.
vendorName fileHeader 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.

For the XML schema based XML format, XML attribute
specification "vendorName" may be absent in case the
"vendorName" is not configured in the sender.
neId managedElement 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 managedElement This is the user definable name ("userLabel") defined for the NE
userLabel in 3GPP TS 32.622 [17]. The string may be empty (i.e. string
size =0) if the "nEUserName" is not configured in the CM
applications.

For the XML schema based XML format, XML attribute
specification "userLabel" may be absent in case the
"nEUserName" is not configured in the CM applications.
neDistinguishedName managedElement This attribute shall hold the DN of HNB. See Note 1 of
localDn Table 5.1.

See TS 32.300 [4] for definition of DN.
.
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 8 ETSI TS 132 584 V17.0.0 (2022-04)
File Content Item XML schema based Description
XML tag
neSoftwareVersion managedElement
This is the software version ("swVersion") defined for the NE in
swVersion
3GPP TS 32.622 [17].
This is an optional parameter which allows post-processing
systems to take care of vendor specific measurements modified
between software versions.

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.
Modifier configData modifier This element is present if the HMS is required to inform the NE
whether the parameter information should be used to create,
update or delete an specific object instance on the HNB.
If not present the NE will assume the modification action is
update
HNBDataParameters configData DeviceInfo
These elements are present if the HMS requires to modify the
configData
specific configuration parameters
ManagementServer
configData Time
The XML file format definitions implement the configuration
FAPService DNPrefix
structure and parameter definitions defined in broadband forum
FAPService
3GPP TS 32.582 [9] and TR-098 Amendment 2 [16].
FAPControl
FAPService
AccessMgmt
FAPService CellConfig
FAPService Transport
FAPService REM
FAPService GPS
timestamp fileFooter dataTime

A vendor MAY extend the standardized parameter list with vendor-specific parameters and objects. Vendor-specific
parameters and objects MAY be defined either in a separate naming hierarchy or within the standardized naming
hierarchy of the XML File Format.
The name of a vendor-specific parameter or object not contained within another vendor-specific object MUST have the
following form to align with the Vendor Specific Parameter Definition of TR-098 Amendment 2 [16].
• X__VendorSpecificName

4.2 XML schema based CM data file format definition
4.2.1 CM data file XML diagram
Figure 4.1 describes the XML element structure of the CM data file.
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 9 ETSI TS 132 584 V17.0.0 (2022-04)

Figure 4.1: XML diagram of the configuration data file

ETSI

---------------------- Page: 10 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 10 ETSI TS 132 584 V17.0.0 (2022-04)
4.2.2 CM data file XML schema
The following XML schema configData.xsd is the schema for CM data XML files:



xmlns="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.3gpp.org/ftp/specs/archive/32_series/32.584#configData"
elementFormDefault="qualified">


 
 
  
  
  
 
 


 
 
  
  
  
  
 
 


 
 
  
  
 
 


 
 
  
  
 
 


 
 
  
  
  
 
 


 
 
  
  
  
 
 


 
 
  
  
  
 
 
ETSI

---------------------- Page: 11 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 11 ETSI TS 132 584 V17.0.0 (2022-04)


 
 
  
  
  
  
  
  
 
 


 
 
  
  
  
  
  
  
  
  
 
 


 
 
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
 
 


 
 
  
  
 
 


 
 
  
  
 
 


 
 
  
  
  
  
  
  
 
 


ETSI

---------------------- Page: 12 ----------------------
3GPP TS 32.584 version 17.0.0 Release 17 12 ETSI TS 132 584 V17.0.0 (2022-04)
 
 
  
  
  
  
  
  
  
  
 
 


 
 
  
  
  
 
 


 
 
  
 
 


 
 
  
  
  
 
 


 
 
  
  
  
  
   ...