1、 ETSI TS 132 646 V12.0.0 (2014-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions (3GP
2、P TS 32.646 version 12.0.0 Release 12) TECHNICAL SPECIFICATION ETSI ETSI TS 132 646 V12.0.0 (2014-10)13GPP TS 32.646 version 12.0.0 Release 12Reference RTS/TSGS-0532646vc00 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
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 The present document can be downloaded from: http:/www.etsi.org The present document may be made available in electronic versions and/or in print. The
4、 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 prevailing document is the print of the Portable
5、 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 documents is available at http:/portal.ets
6、i.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 any means, electronic or mechanical, includ
7、ing 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 In
8、stitute 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 Partners. GSM and the GSM logo are Trade
9、Marks registered and owned by the GSM Association. ETSI ETSI TS 132 646 V12.0.0 (2014-10)23GPP TS 32.646 version 12.0.0 Release 12Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential
10、 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 Secretariat. Latest updates are
11、 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 ETSI Web server) which
12、 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, UMTS identities or GSM
13、 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 present document “shall“, “shall not“, “shou
14、ld“, “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 ETSI deliverables except when used in
15、direct citation. ETSI ETSI TS 132 646 V12.0.0 (2014-10)33GPP TS 32.646 version 12.0.0 Release 12Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbre
16、viations . 8g34 Solution Set Definitions . 8g3Annex A (normative): CORBA Solution Set . 9 g3A.1 Architectural features . 9g3A.1.1 Syntax for Distinguished Names 9g3A.1.2 Rules for NRM extensions . 9g3A.1.2.1 Allowed extensions . 9g3A.1.2.2 Extensions not allowed . 9g3A.2 Mapping . 10g3A.2.1 General
17、mapping 10g3A.2.2 Information Object Class (IOC) mapping 10g3A.2.2.1 IOC RncFunction 10g3A.2.2.2 IOC UtranGenericCell 11g3A.2.2.3 IOC NodeBFunction . 12g3A.2.2.4 IOC IubLink 12g3A.2.2.5 IOC ExternalUtranGenericCell . 13g3A.2.2.6 Void 14g3A.2.2.7 IOC ExternalRncFunction 14g3A.2.2.8 UtranCellFDD . 15g
18、3A.2.2.9 UtranCellTDD 15g3A.2.2.10 UtranCellTDDLcr . 16g3A.2.2.11 UtranCellTDDHcr 16g3A.2.2.12 ExternalUtranCellFDD . 17g3A.2.2.13 ExternalUtranCellTDD . 17g3A.2.2.14 ExternalUtranCellTDDHcr . 18g3A.2.2.15 ExternalUtranCellTDDLcr . 18g3A.2.2.16 Void 18g3A.2.2.17 IOC UtranRelation 19g3A.2.2.18 IOC EP
19、_IuCS 19g3A.2.2.19 IOC EP_IuPS 19g3A.2.2.20 IOC EP_Iur . 19g3A.3 Solution Set definitions 20g3A.3.1 IDL definition structure 20g3A.3.2 IDL specification “UtranNetworkResourcesNRMDefs.idl“ . 20g3Annex B (normative): XML Definitions 27g3B.1 Architectural features . 27g3B.1.1 Syntax for Distinguished N
20、ames 27g3B.2 Mapping . 27g3ETSI ETSI TS 132 646 V12.0.0 (2014-10)43GPP TS 32.646 version 12.0.0 Release 12B.2.1 General mapping . 27g3B.2.2 Information Object Class (IOC) mapping . 27g3B.3 Solution Set definitions 28g3B.3.1 XML definition structure 28g3B.3.2 Graphical Representation . 28g3B.3.3 XML
21、schema “utranNrm.xsd“ . 29g3Annex C (informative): Change history . 51g3History 52g3ETSI ETSI TS 132 646 V12.0.0 (2014-10)53GPP TS 32.646 version 12.0.0 Release 12Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present docu
22、ment 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: Version x.y.z where:
23、 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 the third digit is inc
24、remented 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 identified below: 32.641:
25、“Configuration Management (CM); UTRAN Network Resources Integration Reference Point (IRP); Requirements“. 32.642: “Configuration Management (CM); UTRAN Network Resources Integration Reference Point (IRP); Network Resource Model (NRM)“. 32.646: Configuration Management (CM); UTRAN Network Resources I
26、ntegration Reference Point (IRP); Solution Set (SS) definitions 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 o
27、n the NEs and NRs, and they may be initiated by the operator or functions in the 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 (Q
28、oS). The CM actions are initiated either as a single action on a Network Element (NE) of the 3G-network or as part of a complex procedure involving actions on many NEs. The Itf-N interface for Configuration Management is built up by a number of Integration Reference Points (IRPs) and a related Name
29、Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in 3GPP TS 32.101 1 and 3GPP TS 32.102 2. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other technical specifications for telecom ma
30、nagement produced by 3GPP. ETSI ETSI TS 132 646 V12.0.0 (2014-10)63GPP TS 32.646 version 12.0.0 Release 121 Scope The present document specifies the Solution Sets for the UTRAN NRM IRP. This Solution Set specification is related to 3GPP TS 32.642 V11.4.X 4. 2 References The following documents conta
31、in provisions 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-specifi
32、c reference, 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.101: “Telecommunication management; Principle
33、s and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 4 3GPP TS 32.642: “Telecommunication management; Configuration Management (CM); UTRAN
34、network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 5 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 6 3GPP TS 32.306: “Telecommunication management; Configuration Management (CM); Notification Integ
35、ration Reference Point (IRP); Solution Set (SS) definitions“. 7 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP); Solution Set (SS) definitions“. 8 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 9
36、W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 10 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 11 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 12 W3C REC-xml-names-19990114: “Namespaces in XML“. 3 Definitions and abbreviations 3.1 Definitions For terms
37、and definitions please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3 and 3GPP TS 32.642 4. XML file: file containing an XML document XML document: composed of the succession of an optional XML declaration followed by a root XML element ETSI ETSI TS 132 646 V12.0.0 (2014-10)73GPP TS 3
38、2.646 version 12.0.0 Release 12NOTE: See 8; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 8. 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 X
39、ML 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 8. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML at
40、tribute 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 8. XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element
41、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 element NOTE: See 8. XML end-tag:
42、 the end of a non-empty XML element is marked by an XML end-tag containing the name of the XML element NOTE: See 8. 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 8. XML attribute specificat
43、ion: has a name and a value NOTE: See 8. DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD NOTE: See 8. XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document
44、 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 9, 10 and 11. XML namespace: enables qualifying element
45、 and attribute names used in XML documents by associating them with namespaces identified by different XML schemas NOTE: See 12, 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 ba
46、se 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 9, 10 and 11. XML element type: declared by an XML schema; can be directly used in an XML document; as the concrete
47、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 ETSI ETSI TS 132 646 V12.0.0 (2014-10)83GPP TS 32.646 version 12.0.0 Release 12NOTE: S
48、ee 9, 10 and 11. For additional terms and definitions please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.600 3 and 3GPP TS 32.642 4. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Brok
49、er Architecture DN Distinguished Name DTD Document Type Definition EDGE Enhanced Data for GSM Evolution GERAN GSM/EDGE Radio Access Network GSM Global System for Mobile communication IS Information Service IDL Interface Definition Language (OMG) IOC Information Object Class IRP Integration Reference Point IS Information Service MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SIPTO Selected IP Traffic Offload SS Solution SetUMTS Universal
