1、 ETSI TS 132 584 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); Telecommunication management; Home Node B (HNB) Operations, Administration, Maintenance and Provisioning (OAM XML definitions for Type 1 interface HNB to HNB Management System (HMS) (3GPP TS 32.584 version 14.0.0 R
2、elease 14) TECHNICAL SPECIFICATION ETSI ETSI TS 132 584 V14.0.0 (2017-04)13GPP TS 32.584 version 14.0.0 Release 14Reference RTS/TSGS-0532584ve00 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 Siret N 348 623 562 00017
3、- 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. The content of any elect
4、ronic 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 Portable Document Format (PDF
5、) 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 https:/portal.etsi.org/TB/ETSIDeliver
6、ableStatus.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 Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including
7、 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 Standards Insti
8、tute 2017. 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. oneM2M logo is protected for the b
9、enefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 584 V14.0.0 (2017-04)23GPP TS 32.584 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared t
10、o 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 av
11、ailable 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 S
12、R 000 314 (or the updates on the ETSI Web 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 repo
13、rts 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 http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminol
14、ogy 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 ET
15、SI deliverables except when used in direct citation. ETSI ETSI TS 132 584 V14.0.0 (2017-04)33GPP TS 32.584 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviatio
16、ns . 6g33.1 Definitions 6g33.2 Abbreviations . 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 definit
17、ion 21g35.1 Mapping table . 21g35.2 XML 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 d
18、ata file . 24g3Annex B (informative): Void . 25g3Annex C (informative): Change history . 26g3History 27g3ETSI ETSI TS 132 584 V14.0.0 (2017-04)43GPP TS 32.584 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The content
19、s 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:
20、 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 t
21、he 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 Aspects, Telecommunication Management; as identi
22、fied below: 32.581: “Telecommunications 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,
23、 Maintenance and Provisioning (OAM 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 Procedure flows for Type 1 interface HNB to HNB Management System (HMS
24、)“ 32.584: “Telecommunications management; 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 V14.0.0 (2017-04)53GPP TS 32.584 version 14.0.0 Release 141 Scope The present docum
25、ent 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, thr
26、ough 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 l
27、atest 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: “T
28、elecommunication 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
29、 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, Maintenan
30、ce and Provisioning (OAM 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: Str
31、uctures“. 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.62
32、2: “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
33、)” 19 3GPP TS 22.220: “Service requirements for Home Node B (HNB) and Home eNode B (HeNB)” ETSI ETSI TS 132 584 V14.0.0 (2017-04)63GPP TS 32.584 version 14.0.0 Release 1420 3GPP TS 32.432: “Telecommunication management; Performance measurement: File format definition” 3 Definitions and abbreviations
34、 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 deriv
35、ations 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 abbrev
36、iation, 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
37、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, provide
38、s 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
39、Mapping of File Content Items to XML tags File Content 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 co
40、nfiguration 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 ETSI TS 132 584 V14.
41、0.0 (2017-04)73GPP TS 32.584 version 14.0.0 Release 14File Content Item XML schema based XML tag Description 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 th
42、e 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, wh
43、ich 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 of this 3GPP docum
44、ent (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
45、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 fi
46、le 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=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 Not
47、e 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 ba
48、sed 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 sof
49、tware version (“nESoftwareVersion“) of the NE. neUserName 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 HN
