1、 ETSI TS 132 765 V9.6.0 (2014-07) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP);
2、eXtensible Markup Language (XML) definitions (3GPP TS 32.765 version 9.6.0 Release 9) TECHNICAL SPECIFICATION ETSI ETSI TS 132 765 V9.6.0 (2014-07)13GPP TS 32.765 version 9.6.0 Release 9Reference RTS/TSGS-0532765v960 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex -
3、FRANCE Tel.: +33 4 92 94 42 00 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 The present document can be downloaded from: http:/www.etsi.org The present document may be made available i
4、n electronic versions and/or in print. 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 prevai
5、ling document is the print of the Portable 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
6、documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present 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 or utilized in any form or by a
7、ny means, electronic or mechanical, 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
8、. European Telecommunications Standards Institute 2014. 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
9、 Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 765 V9.6.0 (2014-07)23GPP TS 32.765 version 9.6.0 Release 9Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The in
10、formation 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 available from t
11、he ETSI Secretariat. 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 th
12、e 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 reports using their
13、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 terminology In the prese
14、nt document “shall“, “shall not“, “should“, “should not“, “may“, “may not“, “need“, “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
15、 ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 765 V9.6.0 (2014-07)33GPP TS 32.765 version 9.6.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions, symbols and ab
16、breviations . 6g33.1 Definitions 6g33.2 Symbols 7g33.3 Abbreviations . 7g34 Architectural Features 7g35 Mapping . 8g35.1 General . 8g35.2 Information Object Class (IOC) mapping 8g3Annex A (normative): XML schema (file name “eutranNrm.xsd“) . 9g3Annex B (informative): Void . 15g3Annex C (informative)
17、: Change history . 16g3History 17g3ETSI ETSI TS 132 765 V9.6.0 (2014-07)43GPP TS 32.765 version 9.6.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 a
18、nd 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 to TSG for informati
19、on; 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 changes have been incor
20、porated 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: TS 32.761 Evolved Universal Terrestrial Radio Access Network
21、 (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements TS 32.762 Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) TS 32.763 Evolved Universal Terrestrial Radio Access
22、 Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) TS 32.765 Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): eXtensible Mar
23、kup Language (XML) definitions ETSI ETSI TS 132 765 V9.6.0 (2014-07)53GPP TS 32.765 version 9.6.0 Release 91 Scope The present document provides the XML definitions for the E-UTRAN Network Resource Model IRP IS 2. An application of these XML definitions is to build a configuration file for transfer
24、with the Bulk CM IRP using either CORBA Solution Set of 3GPP TS 32.613 3 or the SOAP Solution Set of 3GPP TS 32.617 5. For this application, the basic part of the XML file format definition is provided by 3GPP TS 32.615 4. Other applications of these XML definitions are the SOAP solution sets of oth
25、er IRPs that perform operations on managed objects, for example the Basic CM IRP SOAP SS of 3GPP TS 32.607 6. This specification is related to 3GPP TS 32.762 V9. 5.X. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present d
26、ocument. 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 (inc
27、luding 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 21.905: Vocabulary for 3GPP Specifications. 2 3GPP TS 32.762: “ Telecommunications management; Evolved Universal Terrestrial Radio Access N
28、etwork (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 3 3GPP TS 32.613: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Common Object Request Broker Architecture (CORBA) Solution Set (SS)“.
29、 4 3GPP TS 32.615: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); eXtensible Markup Language (XML) file format definition“. 5 3GPP TS 32.617: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (I
30、RP); SOAP Solution Set (SS)“. 6 3GPP TS 32.607: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP); SOAP Solution Set (SS)“. 7 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 8 W3C REC-xmlschema-0-20010502: “XML Sch
31、ema Part 0: Primer“. 9 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures. 10 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes. 11 W3C REC-xml-names-19990114: “Namespaces in XML“. 12 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention fo
32、r Managed Objects“. ETSI ETSI TS 132 765 V9.6.0 (2014-07)63GPP TS 32.765 version 9.6.0 Release 93 Definitions, symbols and abbreviations 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 doc
33、ument takes precedence over the definition of the same term, if any, in TR 21.905 1. 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 7; in the scope of the present document. XML declaration: it
34、 specifies the version of XML being used NOTE: See 7. XML element: has a type, is identified by a name, may have a 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 s
35、imply of an XML empty-element tag; each XML element may contain other XML elements NOTE: See 7. empty XML element: 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
36、 directly followed by an XML end-tag, or composed simply of an XML empty-element tag NOTE: See 7. XML content (of an 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
37、-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 element NOTE: See 7. XML end-tag: the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML elemen
38、t NOTE: See 7. 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: See 7. XML attribute specification: has a name and a value NOTE: See 7. DTD: defines structure and content constraints to be respecte
39、d by an XML document to be valid with regard to this DTD NOTE: See 7. XML schema: more powerful than a DTD, an XML 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 to
40、gether 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 8, 9 and 10. ETSI ETSI TS 132 765 V9.6.0 (2014-07)73GPP TS 32.765 version 9.6.0 Release 9XML namespace: enables qualifying element and attribute names used i
41、n XML documents by associating them with namespaces identified by different XML schemas NOTE: See 11, 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 concrete type or the derivation base type for an XML element
42、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 8, 9 and 10. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete type of an XML element, dire
43、ctly 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 8, 9 and 10. 3.2 Symbols - 3.3 Abbreviations For the purposes of the present document, the abbreviations
44、 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. CM Configuration Management GSM Global System for Mobile communication IRP Integration Reference Point IS Information
45、Service NRM Network Resource Model XML eXtensible Markup Language XSD XML Schema Definition 4 Architectural Features The overall architectural feature of E-UTRAN Network Resource Model IRP is specified in 3GPP TS 32.762 2. This clause specifies features that are specific to the XML definitions. The
46、XML definitions of this document specify the schema for a configuration content. When using the XML definitions for a configuration file transfer with the Bulk CM IRP, using either CORBA Solution Set of 3GPP TS 32.613 3 or SOAP Solution Set of 3GPP TS 32.617 5, the basic part of the XML file format
47、definition is provided by 3GPP TS 32.615 4. The XML definitions of this document provide the schema for the configuration content to be included in such a configuration file. When using the XML definitions with a SOAP solution set of any interface IRP that perform operations on managed objects, for
48、example the Basic CM IRP SOAP SS of 3GPP TS 32.607 6, the XML definitions of this document provides the schema for the configuration content operated on by the interface IRP. Such configuration content can be name of managed object and, if applicable, IOC attributes. ETSI ETSI TS 132 765 V9.6.0 (201
49、4-07)83GPP TS 32.765 version 9.6.0 Release 95 Mapping 5.1 General An IOC maps to an XML element of the same name as the IOCs name in the IS. An IOC attribute maps to a sub-element of the corresponding IOCs XML element, and the name of this sub-element is the same as the attributes name in the IS. 5.2 Information Object Class (IOC) mapping Annex A of the present document defines the NRM-specific XML schema eutranNrm.xsd for the E-UTRAN Network Resources IRP NRM defined in 3GP
