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

1、 ETSI TS 132 675 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);State Management Integration Reference Point (IRP);Bulk CM eXtensible Markup

2、 Language (XML) file format definition (3GPP TS 32.675 version 9.0.0 Release 9)ETSI ETSI TS 132 675 V9.0.0 (2010-01)13GPP TS 32.675 version 9.0.0 Release 9Reference RTS/TSGS-0532675v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 0

3、0 Fax: +33 4 93 65 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 t

4、han one electronic 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 netwo

5、rk 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 you find errors in the pr

6、esent document, please 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. Eur

7、opean Telecommunications Standards Institute 2010. 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

8、 Organizational Partners. 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 675 V9.0.0 (2010-01)23GPP TS 32.675 version 9.0.

9、0 Release 9Intellectual 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: “Intellectu

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

11、on, 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. Foreword This Technical Specificatio

12、n (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 should be interpreted as being references to the corresponding ETSI deliverables. Th

13、e cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 675 V9.0.0 (2010-01)33GPP TS 32.675 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 Refe

14、rences 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 7g34 Structure and content of configuration data XML files 7g3Annex A (normative): Configuration data file NRM-specific XML schema (file name “stateManagementIRP.xsd“) . 8g3Annex B (informative): Void . 10g3Annex C

15、 (informative): Change history . 11g3History 12g3ETSI ETSI TS 132 675 V9.0.0 (2010-01)43GPP TS 32.675 version 9.0.0 Release 9Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing wo

16、rk 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 t

17、o 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 chan

18、ges 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.671 Configuration Management (CM); Sta

19、te Management Integration Reference Point (IRP); Requirements 32.672 Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) 32.673 Configuration Management (CM); State Management Integration Reference Point (IRP); Common Object Request Broker Arch

20、itecture (CORBA) Solution Set (SS) 32.675 Configuration Management (CM); State Management Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition Configuration Management (CM), in general, provides the operator with the ability to assure correct and effecti

21、ve operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be r

22、equested as part of a deployment program (e.g. additions and deletions), as part of an optimisation program (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as single actions on single NEs of the 3G network, or as part of a complex proce

23、dure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 675 V9.0.0 (2010-01)53GPP TS 32.675 version 9.0.0 Release 91 Scope The present document specifies the XML file format definition for the Bulk Configuration Management IRP IS 2 for the IRP whose semantics is spec

24、ified in State Management IRP: Information Service (IS) (3GPP TS 32.672 1). Bulk CM XML file formats are based on XML 4, XML Schema 5 6 7 and XML Namespace 8 standards. This File Format Definition specification is related to 3GPP TS 32.672 V9.0.X. 2 References The following documents contain provisi

25、ons, 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 referen

26、ce, 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 TS 32.672: “Telecommunication management; Configuration Mana

27、gement (CM); State Management Integration Reference Point (IRP): Information Service (IS)“. 2 3GPP TS 32.612: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Information Service (IS)“. 3 3GPP TS 32.615: “Telecommunication management; Configura

28、tion Management (CM); Bulk CM Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition“. 4 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 5 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 6 W3C REC-xmlschema-1-20010502: “XM

29、L Schema Part 1: Structures“. 7 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 8 W3C REC-xml-names-19990114: “Namespaces in XML“. 9 ITU-T Recommendation X.721: “Information technology - Open Systems Interconnection - Structure of management information: Definition of management inform

30、ation“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element NOTE: See 4; i

31、n the scope of the present document. XML declaration: it specifies the version of XML being used ETSI ETSI TS 132 675 V9.0.0 (2010-01)63GPP TS 32.675 version 9.0.0 Release 9NOTE: See 4. XML element: has a type, is identified by a name, may have a set of XML attribute specifications and is either com

32、posed 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 NOTE: See 4. empty XML element: having an empty XML content; an empty XML element sti

33、ll 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 NOTE: See 4. XML content (of an XML element): empty if the XML element is simply co

34、mposed 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: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and the set of XML attribute specifications of the XML el

35、ement NOTE: See 4. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element NOTE: See 4. XML empty-element tag: composed simply of an empty-element tag containing the name and the set of XML attribute specifications of the XML element NOTE: S

36、ee 4. XML attribute specification: has a name and a value NOTE: See 4. DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD NOTE: See 4. XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to b

37、e respected by an XML document to conform with this XML schema; through the use of XML namespaces several XML schemas can be used together by a single XML document; an XML schema is itself also an XML document that shall conform with the XML schema for XML schemas NOTE: See 5, 6 and 7. XML namespace

38、: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas NOTE: See 8, in the scope of the present document. XML complex type: defined in an XML schema; cannot be directly used in an XML document; can be the concret

39、e type or the derivation base type for an XML element type or for another XML complex type; ultimately defines constraints for an XML element on its XML attribute specifications and/or its XML content NOTE: See 5, 6 and 7. XML element type: declared by an XML schema; can be directly used in an XML d

40、ocument; as the concrete type of an XML element, directly or indirectly defines constraints on its XML attribute specifications and/or its XML content; can also be the concrete type or the derivation base type for another XML element type NOTE: See 5, 6 and 7. ETSI ETSI TS 132 675 V9.0.0 (2010-01)73

41、GPP TS 32.675 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management DTD Document Type Definition EDGE Enhanced Data for GSM Evolution GERAN GSM/EDGE Radio Access Network GSM Global System for Mobile communica

42、tion IRP Integration Reference Point IS Information Service NRM Network Resource Model UMTS Universal Mobile Telecommunications System UTRAN Universal Terrestrial Radio Access Network XML eXtensible Markup Language 4 Structure and content of configuration data XML files The overall description of th

43、e file format of configuration data XML files is provided by 3GPP TS 32.615 3. Annex A of the present document defines the XML schema stateManagementIRP.xsd for the State Management IRP: Information Service (IS) defined in 3GPP TS 32.672 1. The definition of the XML element types complies with the g

44、eneric mapping rules defined in 3GPP TS 32.615 3. ETSI ETSI TS 132 675 V9.0.0 (2010-01)83GPP TS 32.675 version 9.0.0 Release 9Annex A (normative): Configuration data file NRM-specific XML schema (file name “stateManagementIRP.xsd“) The following XML schema stateManagementIRP.xsd is the specific sche

45、ma for the State Management IRP: Information Service (IS) defined in 3GPP TS 32.672 1. ETSI ETSI TS 132 675 V9.0.0 (2010-01)93GPP TS 32.675 version 9.0.0 Release 9ETSI ETSI TS 132 675 V9.0.0 (2010-01)103GPP TS 32.675 version 9.0.0 Release 9Annex B (informative): Void ETSI ETSI TS 132 675 V9.0.0 (201

46、0-01)113GPP TS 32.675 version 9.0.0 Release 9Annex C (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Cat Old New Dec 2006 SA_34 SP-060732 0003 - Add element definitions for states F 6.2.0 7.0.0 Mar 2007 - - - - Delete reference to the 32.674 CMIP SS. Reason: S

47、A#35 endorsed the SA5 decision to not propagate the CMIP Solution Sets to Rel-7 (TS 32.3x4, TS 32.4x4, TS 32.6x4) - 7.0.0 7.0.1 Jun 2007 - - - - Updated Scope on reference to 32.672 IS V6.1.X to V7.0.X which was automatically upgraded to R7 at SA#36 - 7.0.1 7.0.2 Dec 2008 SA_42 - - - Upgrade to Release 8 - 7.0.2 8.0.0 Dec 2009 SA_46 SP-090719 0004 - Discontinue from Rel-9 onwards the XML schema extraction and storage F 8.0.0 9.0.0 ETSI ETSI TS 132 675 V9.0.0 (2010-01)123GPP TS 32.675 version 9.0.0 Release 9History Document history V9.0.0 January 2010 Publication