ETSI TS 132 655-2012 Digital cellular telecommunications system (Phase 2+) Telecommunication management Configuration Management (CM) GERAN network resources Integration Reference .pdf

《ETSI TS 132 655-2012 Digital cellular telecommunications system (Phase 2+) Telecommunication management Configuration Management (CM) GERAN network resources Integration Reference .pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 655-2012 Digital cellular telecommunications system (Phase 2+) Telecommunication management Configuration Management (CM) GERAN network resources Integration Reference .pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 655 V9.2.0 (2012-01) Digital cellular telecommunications system (Phase 2+); Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Bulk CM eXtensible Markup Language (XML) file format definition (3GPP TS 32.655 version 9.2

2、.0 Release 9) GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRTechnical Specification ETSI ETSI TS 132 655 V9.2.0 (2012-01)13GPP TS 32.655 version 9.2.0 Release 9Reference RTS/TSGS-0532655v920 Keywords GSM ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4

3、 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 than one elec

4、tronic 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 wit

5、hin 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 present docume

6、nt, 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. European Teleco

7、mmunications Standards Institute 2012. 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 an

8、d the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 655 V9.2.0 (2012-01)23GPP TS 32.655 version 9.2.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertain

9、ing 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 available from the ETSI Secretari

10、at. Latest updates are available on the ETSI Web server (http:/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

11、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 reports using their 3GPP identities,

12、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. ETSI ETSI TS 132 655 V9.2.0 (2012-01)33GPP TS 32.655

13、version 9.2.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 7g34 Structure and content of configuration data XML files 7g3Annex A (normative): Config

14、uration data file NRM-specific XML schema (file name “geranNrm.xsd“) . 8g3Annex B (informative): Void . 12g3Annex C (informative): Change history . 13g3History 14g3ETSI ETSI TS 132 655 V9.2.0 (2012-01)43GPP TS 32.655 version 9.2.0 Release 9Foreword This Technical Specification has been produced by t

15、he 3rdGeneration Partnership Project (3GPP). The contents 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 re

16、lease 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 greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e

17、. technical enhancements, corrections, updates, etc. z the 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 an

18、d System Aspects; Telecommunication management; as identified below: 32.651: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Requirements 32.652: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Model

19、 (NRM) 32.653: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.655: Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Bulk CM eXtensible Markup Lan

20、guage (XML) file format definition Configuration Management (CM), in general, provides the operator with 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 Elements (NEs)

21、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 requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain

22、 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 procedure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 655 V9.2.0 (2012-01)53GPP TS 32.655 version 9.2.0 Releas

23、e 91 Scope The present document provides the NRM-specific part related to the GERAN Network Resources IRP NRM 1 of the XML file format definition for the Bulk Configuration Management IRP IS 2. The main part of this XML file format definition is provided by 3GPP TS 32.615 3. Bulk CM XML file formats

24、 are based on XML 4, XML Schema 5 6 7 and XML Namespace 8 specifications. This File Format Definition specification is related to 3GPP TS 32.652 V9.2.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. Refer

25、ences 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 (including a GSM d

26、ocument), 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.652: “Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP): Network Resource Models

27、(NRM)“. 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; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); eXtensible Markup L

28、anguage (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: “XML Schema Part 1: Structures“. 7 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Da

29、tatypes“. 8 W3C REC-xml-names-19990114: “Namespaces in XML“. 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 decl

30、aration followed by a root XML element NOTE: See 4; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 4. ETSI ETSI TS 132 655 V9.2.0 (2012-01)63GPP TS 32.655 version 9.2.0 Release 9XML element: has a type, is identified by a name, may have a

31、set of XML attribute specifications 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 NOTE: See 4. empty XML element:

32、having an empty XML 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 NOTE: See 4. XML content (of a

33、n XML element): empty if the XML 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: the beginning of a non-empty XML element is marked by an XML start-tag containing the name and

34、the set of XML attribute specifications of the XML element 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 XM

35、L attribute specifications of the XML element NOTE: See 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

36、schema defines structure and content constraints to be 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 schem

37、a for XML schemas NOTE: See 5, 6 and 7. XML namespace: 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

38、 directly used in an XML document; can be the concrete 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: declar

39、ed by an XML schema; can be directly used in an XML document; 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: Se

40、e 5, 6 and 7. ETSI ETSI TS 132 655 V9.2.0 (2012-01)73GPP TS 32.655 version 9.2.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

41、Access Network GSM Global System for Mobile communication 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 confi

42、guration data XML files The overall description of the file format of configuration data XML files is provided by 3GPP TS 32.615 3. Annex A of the present document defines the NRM-specific XML schema geranNrm.xsd for the GERAN Network Resources IRP NRM defined in 3GPP TS 32.652 1. XML schema geranNr

43、m.xsd explicitly declares NRM-specific XML element types for the related NRM. The definition of those NRM-specific XML element types complies with the generic mapping rules defined in 3GPP TS 32.615 3. ETSI ETSI TS 132 655 V9.2.0 (2012-01)83GPP TS 32.655 version 9.2.0 Release 9Annex A (normative): C

44、onfiguration data file NRM-specific XML schema (file name “geranNrm.xsd“) The following XML schema geranNrm.xsd is the NRM-specific schema for the GERAN Network Resources IRP NRM defined in 3GPP TS 32.652 1: ETSI ETSI TS 132 655 V9.2.0 (2012-01)93GPP TS 32.655 version 9.2.0 Release 9ETSI ETSI TS 132

45、 655 V9.2.0 (2012-01)103GPP TS 32.655 version 9.2.0 Release 9ETSI ETSI TS 132 655 V9.2.0 (2012-01)113GPP TS 32.655 version 9.2.0 Release 9ETSI ETSI TS 132 655 V9.2.0 (2012-01)123GPP TS 32.655 version 9.2.0 Release 9Annex B (informative): Void ETSI ETSI TS 132 655 V9.2.0 (2012-01)133GPP TS 32.655 ver

46、sion 9.2.0 Release 9Annex C (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Cat Old New Jun 2002 SA_16 SP-020298 - - Submitted to TSG SA #16 for Information - 1.0.0 Sep 2002 SA_17 SP-020463 - - Submitted to TSG SA #17 for Approval - 2.0.0 5.0.0 Jun 2003 SA_20

47、SP-030283 0001 - Deletion of GERAN attribute relationType in XML Schema. F 5.0.0 5.1.0 Jun 2003 SA_20 SP-030287 0002 - Correction of GERAN NRM XML schema namespace URIs F 5.0.0 5.1.0 Jun 2003 SA_20 SP-030288 0003 - Generic NRM XML schema dependencies removal F 5.0.0 5.1.0 Sep 2003 SA_21 SP-030418 00

48、04 - Inclusion of External BSS Function in GERAN XML Schema - Alignment with 32.652 F 5.1.0 5.2.0 Oct 2003 - - - - Attached to this TS the normative XML schema electronic files corresponding to Sept 2003 TS 32.655 - 5.2.0 5.2.1 Dec 2003 SA_22 SP-030646 0005 - Correction of the number of possible URA

49、s from 1 to 8 F 5.2.1 5.3.0 Mar 2004 SA_23 SP-040131 0006 - Add the capability to contain instances of VsDataContainer to some MOs - Align with the IS 32.652 F 5.3.0 5.4.0 Jun 2004 SA_24 SP-040259 0007 - Removal of XML schema URI dependencies F 5.4.0 5.5.0 Jun 2004 SA_24 SP-040258 0008 - Correction of the annex related to XML schema electronic files publication F 5.4.0 5.5.0 Jun 2004 SA_24 SP-040254 0009 - The specification does not support all UMTS frequency bands F 5.4.0