ETSI TS 132 615-2011 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

《ETSI TS 132 615-2011 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 615-2011 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf（37页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 615 V9.2.0 (2011-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Bulk CM Integration Reference Point (IRP):eXtensible Markup Language (XML) f

2、ile format definition (3GPP TS 32.615 version 9.2.0 Release 9)ETSI ETSI TS 132 615 V9.2.0 (2011-01)13GPP TS 32.615 version 9.2.0 Release 9Reference RTS/TSGS-0532615v920 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 6

3、5 47 16 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 Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electroni

4、c version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within E

5、TSI 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 you find errors in the present document, p

6、lease send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommuni

7、cations Standards Institute 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational P

8、artners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 615 V9.2.0 (2011-01)23GPP TS 32.615 version 9.2.0 Release 9Intell

9、ectual 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 publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Right

10、s (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 (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR

11、 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. Foreword This Technical Specification (TS) has been p

12、roduced 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

13、 between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 615 V9.2.0 (2011-01)33GPP TS 32.615 version 9.2.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Defin

14、itions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Structure and content of configuration data XML files 8g34.1 Global structure 8g34.2 XML elements fileHeader and fileFooter . 10g34.2.1 XML element fileHeader . 10g34.2.2 XML element fileFooter . 10g34.3 XML element configData

15、. 12g34.3A NRM-specific XML elements 13g34.3A.1 NRM-specific XML schemas . 13g34.3A.2 Generic mapping rules 13g34.4 XML attribute specification modifier . 16g34.5 XML elements VsDataContainer, vsData and vsDataFormatVersion . 20g35 Structure and content of session log XML files . 21g35.1 Global stru

16、cture 21g35.2 XML elements fileHeader and fileFooter . 22g35.3 XML element activity . 22g36 BulkCMIRP Notification XML Definitions . 24g3Annex A (normative): Configuration data file base XML schema (file name “configData.xsd“) 25g3Annex B (normative): Void . 28g3Annex C (informative): Configuration

17、data file vendor-specific XML schema example 29g3Annex D (normative): Session log file XML schema (file name “sessionLog.xsd“) 30g3Annex E (normative): BulkCMIRP Notification XML schema (file name “bulkCMIRPNotif.xsd“) . 32g3Annex F (informative): Void . 34g3Annex G (informative): Change history . 3

18、5g3History 36g3ETSI ETSI TS 132 615 V9.2.0 (2011-01)43GPP TS 32.615 version 9.2.0 Release 9Foreword 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 follow

19、ing 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 T

20、SG 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 docum

21、ent. 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.611: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP

22、): Requirements“. 32.612: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 32.613: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.615: “Configurat

23、ion Management (CM); Bulk CM Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“. 32.617: “Configuration Management (CM); Bulk CM Integration Reference Point (IRP): SOAP Solution Set (SS)“. Configuration Management (CM), in general, provides the operator with

24、the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Element (NEs) and Network Resources (NRs), and they may be initiated by the operator or functions in the Operations Syst

25、ems (OSs) or NEs. CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as a single action on a NE of the

26、3G network or as part of a complex procedure involving actions on many NEs. ETSI ETSI TS 132 615 V9.2.0 (2011-01)53GPP TS 32.615 version 9.2.0 Release 91 Scope The present document provides the main part of the XML file format definition for the Bulk Configuration Management IRP IS in 3GPP TS 32.612

27、 1. The other parts of this XML file format definition are NRM-specific parts. Those NRM-specific parts are provided by 3GPP TS 32.625 11, 32.635 12, 32.645 13, 32.655 14, 32.695 16, 32.715 17, 32.735 18, 32.745 15, 32.755 20, 32.765 19, 32.525 21, 32.175 22, 32.725 23, 32.775 24 and 32.785 25. Bulk

28、 CM XML file formats are based on XML 2, XML Schema 3 4 5 and XML Namespace 6 standards. This File Format Definition specification is related to 3GPP TS 32.612 V9.1.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present

29、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 (in

30、cluding 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.612: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“

31、. 2 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 3 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 4 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 5 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 6 W3C REC-xml-names-1999011

32、4: “Namespaces in XML“. 7 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 8 3GPP TS 32.622: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource

33、Model (NRM)“. 9 Void. 10 Void. 11 3GPP TS 32.625: “Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. 12 3GPP TS 32.635: “Telecommunication management; Configurati

34、on Management (CM); Core network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. ETSI ETSI TS 132 615 V9.2.0 (2011-01)63GPP TS 32.615 version 9.2.0 Release 913 3GPP TS 32.645: “Telecommunication management; Configuration Management (CM);

35、 UTRAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. 14 3GPP TS 32.655: “Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Language

36、 (XML) file format definition“. 15 3GPP TS 32.745: “Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) Interface Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. 16 3GPP TS 3

37、2.695: “Telecommunication management; Inventory Management (IM) Network Resource Model (NRM); Integration Reference Point (IRP): eXtensible Markup Language (XML) file format definition“. 17 3GPP TS 32.715: “Telecommunication management; Configuration Management (CM); Transport Network (TN) interface

38、 Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format definition“. 18 3GPP TS 32.735: “IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP): Bulk CM eXtensible Markup Language (XML) file format de

39、finition“. 19 3GPP TS 32.765: “Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 20 3GPP TS 32.755: “ Telecommunication management; Evolved Packet C

40、ore (EPC) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 21 3GPP TS 32.525: “Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language

41、(XML) file format definition“. 22 3GPP TS 32.175: “Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Markup Language (XML) definition“. 23 3GPP TS 32.725: “Telecommunication management; Configuration Management (CM)

42、; Repeater network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition“. 24 3GPP TS 32.775: “Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Bulk CM eXtensible M

43、arkup Language (XML) file format definition“. 25 3GPP TS 32.785: “Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition“. 3 Definitions and abbreviat

44、ions 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. XML file: a file containing an XML document. XML document: see 2; in the scope of this specification, an XML document is composed of the succession of an optional XML declaration followed by a r

45、oot XML element. ETSI ETSI TS 132 615 V9.2.0 (2011-01)73GPP TS 32.615 version 9.2.0 Release 9XML declaration: see 2; it specifies the version of XML and the character encoding being used. XML element: see 2; an XML element has a type, is identified by a name, may have a set of XML attribute specific

46、ations and is either composed of the succession of an XML start-tag followed by the XML content of the XML element followed by an XML end-tag, or composed simply of an XML empty-element tag; each XML element may contain other XML elements. empty XML element: see 2; an XML element having an empty XML

47、 content; an empty XML element still possibly has a set of XML attribute specifications; an empty XML element is either composed of the succession of an XML start-tag directly followed by an XML end-tag, or composed simply of an XML empty-element tag. XML content (of an XML element): empty if the XM

48、L element is simply composed of an XML empty-element tag; otherwise the part, possibly empty, of the XML element between its XML start-tag and its XML end-tag. XML start-tag: see 2; the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribut

49、e specifications of the XML element. XML end-tag: see 2; the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element. XML empty-element tag: see 2; an empty XML element is composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element. XML attribute specification: see 2; an XML attribute specification has a name and a value. DTD: see 2; a DTD defines structure a