1、 ETSI TS 1TelecommHome enhanced Node Maintenance XML definitionto HeNB Ma(3GPP TS 32.5TECHNICAL SPECIFICATION132 594 V13.0.0 (2016LTE; munication management; e B (HeNB) Operations, Admine and Provisioning (OAMions for Type 1 interface HeNBManagement System (HeMS) .594 version 13.0.0 Release 1316-02)
2、 inistration, P); NB 13) ETSI ETSI TS 132 594 V13.0.0 (2016-02)13GPP TS 32.594 version 13.0.0 Release 13Reference RTS/TSGS-0532594vd00 Keywords LTE 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
3、 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 electronic and/o
4、r 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 (PDF) version k
5、ept 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 http:/portal.etsi.org/tb/status/status.asp If yo
6、u 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, including photocopying and mic
7、rofilm 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
8、 reserved. 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 own
9、ed by the GSM Association. ETSI ETSI TS 132 594 V13.0.0 (2016-02)23GPP TS 32.594 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 public
10、ly 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 W
11、eb 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 ma
12、y become, 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 sho
13、uld be 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“, “ma
14、y“, “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 ETSI TS 132 594 V13
15、.0.0 (2016-02)33GPP TS 32.594 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 CM data format definition
16、 7g34.1 File content description 7g34.2 XML schema based CM data file format definition . 8g34.2.1 CM data file XML diagram 8g34.2.2 CM data file XML schema . 8g34.2.3 CM data file XML header . 8g35 PM data format definition 9g35.1 Mapping table . 9g35.2 XML schema based PM data file format definiti
17、on . 10g35.2.1 PM data file XML diagram . 10g35.2.2 PM data file XML schema 10g35.2.3 PM data file XML header . 10g3Annex A (informative): Examples . 11g3A.1 XML schema based CM data file . 11g3A.2 XML schema based PM data file . 11g3Annex B (informative): Change history . 12g3History 13g3ETSI ETSI
18、TS 132 594 V13.0.0 (2016-02)43GPP TS 32.594 version 13.0.0 Release 13Foreword 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 approva
19、l. 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
20、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 The
21、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: 32.591: Concepts and requirements for Type 1 interface HeNB to HeNB Management System (HeMS) 32.592: In
22、formation model for Type 1 interface HeNB to HeNB Management System (HeMS) 32.593: Procedure flows for Type 1 interface HeNB to HeNB Management System (HeMS) 32.594: Data definitions for Type 1 interface HeNB to HeNB Management System (HeMS) ETSI ETSI TS 132 594 V13.0.0 (2016-02)53GPP TS 32.594 vers
23、ion 13.0.0 Release 131 Scope The present document describes the data format for Configuration Management, Fault Management, and Performance Management for Home eNodeB (HeNB). The Stage 3 definitions captured in this document shall be met via type 1 interface between HeNB and Home eNodeB Management S
24、ystem (HeMS). 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 referen
25、ce, 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
26、3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 Void. 3 Void. 4 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 5 7 Void. 8 3GPP TS 32.435: “Telecommunication management; Performance measurement: eXtensible Markup Language (
27、XML) file format definition“ 9 3GPP TS 32.592: “ Information model for Type 1 interface HeNB to HeNB Management System (HeMS) “ 10-12 Void. 13 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 14 Void. 15 WT-157, Component Objects for CWMP, Broadband Forum 16 TR-098 Amendment 2, Internet
28、 Gateway Device Data Model for TR-069“, Broadband Forum 17 Void. 18 TR-196i2, “Femto Access Point Device Data Model“. Broadband Forum, Issue 2 November 2011 http:/www.broadband-forum.org/technical/download/TR-196_Issue-2.pdf . 19 ISO 8601:2004(E) “Data elements and interchange formats Information in
29、terchange Representation of dates and times“, ISO. ETSI ETSI TS 132 594 V13.0.0 (2016-02)63GPP TS 32.594 version 13.0.0 Release 133 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 d
30、efined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Home eNodeB, 3G Home eNodeB: These terms, their derivations and abbreviations are used synonymously throughout this document. 3.2 Abbreviations For the purposes of the present document, the
31、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. CM Configuration Management DM Domain Manager DTD Document Type Definition EM Element Manager HMS Home No
32、deB Management System HeMS Home eNodeB Management System HNB Home NodeB HeNB Home eNodeBIP Internet Protocol LTE Long Term Evolution MME Mobility Management Entity NGMN Next Generation Mobile Networks OAM Operations, Administration and Maintenance PM Performance Management PnP Plug and Play SAE Syst
33、em Architecture Evolution SON Self-Organising Networks UMTS Universal Mobile Telecommunications System UTC Universal Time Coordinated UTRAN UMTS Radio Access Network XML eXtensible Markup Language ETSI ETSI TS 132 594 V13.0.0 (2016-02)73GPP TS 32.594 version 13.0.0 Release 134 CM data format definit
34、ion 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 att
35、ributes 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 XML tag Description configDataCollection configDataFile This is the top-
36、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 heade
37、r to be inserted in each file. It includes a version indicator, the sender name, and vendor name of the sending network node. configData configData The “configData“ construct represents the sequence of zero or more configuration parameter items contained in the file. Each “configData“ element contai
38、ns 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
39、 a time stamp, which refers to the time when the file is closed for sending to the NE. fileFormatVersion fileHeader 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 o
40、f 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, t
41、ogether 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.594 V9.0“ senderName fileHeader senderName The sende
42、rName uniquely identifies the NE or EM that assembled this alarm reporting file by its Distinguished Name (DN), according to the definitions in 3GPP TS 32.300 4. In the case of the NE-based approach, it is identical to the senders “nEDistinguishedName“. vendorName fileHeader vendorName The “vendorNa
43、me“ 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 no
44、t configured in the sender. neId managedElement ETSI ETSI TS 132 594 V13.0.0 (2016-02)83GPP TS 32.594 version 13.0.0 Release 13File Content Item XML schema based XML tag Description neUserName managedElement userLabel “userLabel“ may be absent in case the “nEUserName“ is not configured in the CM app
45、lications. neDistinguishedName managedElement localDn The DN is split into the DN prefix and the Identifier of the Managed Object (see 3GPP TS 32.592 9). “localDn“ may be absent in case the Identifier of the Managed Object is not configured in the CM applications neSoftwareVersion managedElement swV
46、ersion “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 inst
47、ance on the HNB If not present the NE will assume the modification action is update HNBDataParameters configData DeviceInfo configData ManagementServer configData Time FAPService DNPrefix FAPService FAPControl FAPService AccessManagementParameters FAPService CellConfig FAPService TransportParameters
48、 FAPService LTEREMParameters FAPService GPS FAPService SecurityParameters FAPService LocationManagementParameters These elements are present if the HMS requires to modify the specific configuration parameters The XML file format definitions implement the configuration structure and parameter definit
49、ions defined in 3GPP TS 32.592 9 and broadband forum TR-098 Amendment 2 16. 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 w
