1、 ETSI TS 1Universal Mobile TelTelecommHome Node B (HNMaintenance XML definitioto HNB Ma(3GPP TS 32.5TECHNICAL SPECIFICATION132 584 V13.0.0 (2016elecommunications System (munication management; ( NB) Operations, Administrate and Provisioning (OAMtions for Type 1 interface HNBanagement System (HMS) .5
2、84 version 13.0.0 Release 1316-02) (UMTS); ration, P); B 13) ETSI ETSI TS 132 584 V13.0.0 (2016-02)13GPP TS 32.584 version 13.0.0 Release 13Reference RTS/TSGS-0532584vd00 Keywords 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
3、Siret N 348 623 562 00017 - 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
4、. 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 only prevailing document is the print of the Por
5、table Document Format (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 http:/porta
6、l.etsi.org/tb/status/status.asp 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 mecha
7、nical, 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. European Telecommunications
8、 Standards Institute 2016. All rights 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 lo
9、go are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 584 V13.0.0 (2016-02)23GPP TS 32.584 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 th
10、ese 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. Lates
11、t 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 We
12、b server) which are, or may be, or may 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 id
13、entities 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “sh
14、all 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 dire
15、ct citation. ETSI ETSI TS 132 584 V13.0.0 (2016-02)33GPP TS 32.584 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 Abbreviat
16、ions . 6g34 CM data format definition 6g34.1 File content description 6g34.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 . 10g34.2.3 CM data file XML header . 21g35 PM data format definition 21g35.1 Mapping table . 21g35.2 XML
17、schema based PM data file format definition . 23g35.2.1 PM data file XML diagram . 23g35.2.2 PM data file XML schema 23g35.2.2 PM data file XML header . 23g3Annex A (informative): Examples . 24g3A.1 XML schema based CM data file . 24g3A.2 XML schema based PM data file . 24g3Annex B (informative): Vo
18、id . 25g3Annex C (informative): Change history . 26g3History 27g3ETSI ETSI TS 132 584 V13.0.0 (2016-02)43GPP TS 32.584 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
19、 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:
20、 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 edito
21、rial 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 Aspects, Telecommunication Management; as identified below: 32.581: “Telecommunications
22、management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM 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 Infor
23、mation 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 Procedure flows for Type 1 interface HNB to HNB Management System (HMS)“ 32.584: “Telecommunications managemen
24、t; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM XML definitions for Type 1 interface HNB to HNB Management System (HMS)“ ETSI ETSI TS 132 584 V13.0.0 (2016-02)53GPP TS 32.584 version 13.0.0 Release 131 Scope The present document describes the data format for Config
25、uration 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
26、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 refere
27、nce 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 hi
28、gh 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
29、, 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 Information model for
30、 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: “XM
31、L 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
32、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) ETSI ETSI TS 132 584 V13.0.0 (2016-02)63GPP TS
33、32.584 version 13.0.0 Release 1319 3GPP TS 22.220: Service requirements for Home Node B (HNB) and Home eNode B (HeNB) 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 docum
34、ent, 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 through
35、out 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 E
36、lement 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 Univ
37、ersal 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 th
38、e 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
39、 Item XML schema based XML tag Description 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 foo
40、ter (“configFileFooter“). ETSI ETSI TS 132 584 V13.0.0 (2016-02)73GPP TS 32.584 version 13.0.0 Release 13File Content Item XML schema based XML tag Description configFileHeader fileHeader This is the configuration data file header to be inserted in each file. It includes a version indicator, the sen
41、dor 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 contains the name of the NE (“nEId“) and the list of parameters to be created
42、,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 sen
43、ding 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 of this 3GPP document (see below). The abridged number and version of a
44、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, r
45、emoving 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
46、 DN of HMS whose name hierarchy is defined section 6.2.1 of TS 32.772 18. Example: “DC=panyNN.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.
47、 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 “vendorNam
48、e“ 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. neUserN
49、ame managedElement userLabel This is the user definable name (“userLabel“) defined for the NE 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 localDn This attribute shall hold the DN of HNB. See Note 1 of Table 5.1. See TS 32.30
