1、 ETSI TS 132 786 V11.0.0 (2012-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set
2、(SS) definitions (3GPP TS 32.786 version 11.0.0 Release 11) Technical Specification ETSI ETSI TS 132 786 V11.0.0 (2012-10)13GPP TS 32.786 version 11.0.0 Release 11Reference RTS/TSGS-0532786vb00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 9
3、4 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 Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in
4、more than 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
5、 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.etsi.org/tb/status/status.asp If you find errors in
6、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 except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all medi
7、a. European Telecommunications 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 Organizationa
8、l Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 786 V11.0.0 (2012-10)23GPP TS 32.786 version 11.0.0 Release 11Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. Th
9、e 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 Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available fr
10、om the 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 (o
11、r 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 produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using th
12、eir 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. ETSI ETSI TS 132 786 V11.0.0 (20
13、12-10)33GPP TS 32.786 version 11.0.0 Release 11Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Solution Set Definitions . 7g3Annex A (normative) : CORBA So
14、lution Set 8g3A.1 Architectural features . 8g3A.1.1 Syntax for Distinguished Names 8g3A.1.2 Rules for NRM extensions . 8g3A.1.2.1 Allowed extensions . 8g3A.1.2.2 Extensions not allowed . 8g3A.2 Mapping . 9g3A.2.1 General mappings . 9g3A.2.2 Information Object Class (IOC) mapping 9g3A.2.2.1 IOC HeNBG
15、WFunction . 9g3A.2.2.2 IOC HeNBProfile . 9g3A.2.2.3 IOC HeMSFunction 9g3A.3 Solution Set definitions 9g3A.3.1 IDL definition structure 9g3A.3.2 IDL specification HensNetworkResourcesNRMDefs.idl . 10g3Annex B (normative): XML Definitions 11g3B.1 Architectural features . 11g3B.1.1 Syntax for Distingui
16、shed Names 11g3B.2 Mapping . 11g3B.2.1 General mapping 11g3B.2.2 Information Object Class (IOC) mapping 11g3B.3 Solution Set definitions 11g3B.3.1 XML definition structure 11g3B.3.2 Graphical Representation . 11g3B.3.3 XML schema “hensNrm.xsd“ 12g3Annex C (informative): Change history . 14g3History
17、15g3ETSI ETSI TS 132 786 V11.0.0 (2012-10)43GPP TS 32.786 version 11.0.0 Release 11Foreword 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 following form
18、al 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 TSG for a
19、pproval; 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 document. Int
20、roduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; Configuration Management (CM); as identified below: 32.781: Telecommunication management; Home enhanced Node
21、B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements 32.782: Telecommunication management; Home enhanced Node B Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) 32.786: Telecommunication management; H
22、ome enhanced Node B Subsystem (HeNS) Network Resource Model (NRM) Integration 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 h
23、ave 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 requested as part of an implementation programme (e.g. addi
24、tions 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 single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects
25、in one or several NEs. ETSI ETSI TS 132 786 V11.0.0 (2012-10)53GPP TS 32.786 version 11.0.0 Release 111 Scope The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management informati
26、on to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s). The present document specifies the Solution Sets for the HeNS NRM IRP. This Solution Set speci
27、fication is related to 3GPP TS 32.782 V11.0.X. 2 References The following documents contain 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
28、-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 document), a non-specific reference implicitly refers to the latest version of that document in the same Re
29、lease as the present document. 1 3GPP TR 21.905: Vocabulary for 3GPP Specifications. 2 3GPP TS 32.782: Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS). 3 3GPP TS 32.616: “Telecommunica
30、tion management; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Solution Set (SS) definitions“. 4 3GPP TS 32.606: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Solution Set (SS) definitions“. 5 W3C REC-xml-2000100
31、6: “Extensible Markup Language (XML) 1.0 (Second Edition)“. 6 W3C REC-xmlschema-0-20010502: “XML Schema Part 0: Primer“. 7 W3C REC-xmlschema-1-20010502: “XML Schema Part 1: Structures“. 8 W3C REC-xmlschema-2-20010502: “XML Schema Part 2: Datatypes“. 9 W3C REC-xml-names-19990114: “Namespaces in XML“.
32、 10 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. ETSI ETSI TS 132 786 V11.0.0 (2012-10)63GPP TS 32.786 version 11.0.0 Release 113 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms a
33、nd definitions given in TR 21.905 1 and the following apply. A term defined in the present document 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 followe
34、d by a root XML element NOTE: See 5; in the scope of the present document. XML declaration: it specifies the version of XML being used NOTE: See 5. 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 star
35、t-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 5. empty XML element: having an empty XML content; an empty XML element still possibly has a set of XML attribute
36、 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 5. XML content (of an XML element): empty if the XML element is simply composed of an XML empty-element tag; ot
37、herwise 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 5. XML end-tag: the en
38、d of a non-empty XML element is marked by an XML end-tag containing the name of the XML element NOTE: See 5. 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 5. XML attribute specification: has
39、 a name and a value NOTE: See 5. DTD: defines structure and content constraints to be respected by an XML document to be valid with regard to this DTD NOTE: See 5. XML schema: more powerful than a DTD, an XML schema defines structure and content constraints to be respected by an XML document to conf
40、orm 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 6, 7 and 8. ETSI ETSI TS 132 786 V11.0.0 (2012-10)73GPP TS 32.7
41、86 version 11.0.0 Release 11XML namespace: enables qualifying element and attribute names used in XML documents by associating them with namespaces identified by different XML schemas NOTE: See 9, in the scope of the present document. XML complex type: defined in an XML schema; cannot be directly us
42、ed 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 6, 7 and 8. XML element type: declared by an XML
43、 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: See 6, 7 and 8
44、. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name DTD Document Type Definition HeNB Home enhanced Node B HeNS Home enhanced Node B Subsystem HeNB-GW Home e
45、nhanced Node B Gateway IS Information Service IDL Interface Definition Language IRP Integration Reference Point MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SS Solution Set XML eXtensible Markup Language 4 Solution Set Definitions This specificati
46、on defines the following 3GPP HeNS NRM IRP Solution Set Definitions: 3GPP HeNS NRM IRP CORBA SS (Annex A) 3GPP HeNS NRM IRP XML Definitions (Annex B) ETSI ETSI TS 132 786 V11.0.0 (2012-10)83GPP TS 32.786 version 11.0.0 Release 11Annex A (normative) : CORBA Solution Set This annex contains the CORBA
47、Solution Set for the IRP whose semantics is specified in HeNS NRM IRP: Information Service (TS 32.782 2). A.1 Architectural features The overall architectural feature of HeNS Network Resources IRP is specified in 3GPP TS 32.782 2. This clause specifies features that are specific to the CORBA SS. A.1
48、.1 Syntax for Distinguished Names The syntax of a Distinguished Name is defined in 3GPP TS 32.300 10. A.1.2 Rules for NRM extensions This clause discusses how the models and IDL definitions provided in the present document can be extended for a particular implementation and still remain compliant wi
49、th 3GPP SA5s specifications. A.1.2.1 Allowed extensions Vendor-specific MOCs may be supported. The vendor-specific MOCs may support new types of attributes. The 3GPP SA5-specified notifications may be issued referring to the vendor-specific MOCs and vendor-specific attributes. New MOCs shall be distinguishable from 3GPP SA5 MOCs by name. 3GPP SA5-specified and vendor-specific attributes may be used in vendor-specific MOCs. Vendor-specific attribute names shall be distinguishable from existing
