ETSI TS 132 776-2012 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Home Node B (HNB) Subs.pdf

1、 ETSI TS 132 776 V11.0.0 (2012-10) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) defini

2、tions (3GPP TS 32.776 version 11.0.0 Release 11) Technical Specification ETSI ETSI TS 132 776 V11.0.0 (2012-10)13GPP TS 32.776 version 11.0.0 Release 11Reference RTS/TSGS-0532776vb00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax

3、: +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 than o

4、ne 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 network dr

5、ive 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 present

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

7、 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 Organizational Partners.

8、 GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 776 V11.0.0 (2012-10)23GPP TS 32.776 version 11.0.0 Release 11Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The informati

9、on 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 the ETSI

10、 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 the updat

11、es 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 3GPP id

12、entities, 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 776 V11.0.0 (2012-10)33GPP

13、 TS 32.776 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 Solution Set .

14、 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 HNBGWFunction .

15、 9g3A.2.2.2 IOC HNBProfile . 9g3A.2.2.3 IOC HMSFunction 9g3A.2.2.4 IOC IuhSignLinkTp 9g3A.2.2.5 IOC EP_Iuh 10g3A.3 Solution Set definitions 10g3A.3.1 IDL definition structure 10g3A.3.2 IDL specification HnsNetworkResourcesNRMDefs.idl . 10g3Annex B (normative): XML Definitions 12g3B.1 Architectural f

16、eatures . 12g3B.1.1 Syntax for Distinguished Names 12g3B.2 Mapping . 12g3B.2.1 General mapping 12g3B.2.2 Information Object Class (IOC) mapping 12g3B.3 Solution Set definitions 12g3B.3.1 XML definition structure 12g3B.3.2 Graphical Representation . 12g3B.3.3 XML schema “hnsNrm.xsd“ 12g3Annex C (info

17、rmative): Change history . 15g3History 16g3ETSI ETSI TS 132 776 V11.0.0 (2012-10)43GPP TS 32.776 version 11.0.0 Release 11Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). The contents of the present document are subject to continuing work with

18、in 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 to TSG f

19、or 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 changes hav

20、e 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; Configuration Management (CM); as identified below: 32.771: Telecommu

21、nication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Requirements 32.772: Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS) 32.776: Telecommuni

22、cation management; Home Node B Subsystem (HNS) 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

23、 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 requested as part of an implementation programme

24、(e.g. additions 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 resource

25、s/objects in one or several NEs. ETSI ETSI TS 132 776 V11.0.0 (2012-10)53GPP TS 32.776 version 11.0.0 Release 111 Scope The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management

26、information to one or several IRPManagers concerning HNS resources. The HNS 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 HNS NRM IRP. This specificatio

27、n is related to 3GPP TS 32.772 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-specif

28、ic. 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 Release a

29、s the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 32.101: “Telecommunication management; Principles and high level requirements“. 3 3GPP TS 32.102: “Telecommunication management; Architecture“. 4 3GPP TS 32.600: “Telecommunication management; Configuration Man

30、agement (CM); Concept and high-level requirements“. 5 3GPP TS 32.772: “Telecommunication management; Home Node B Subsystem (HNS) Network Resource Model (NRM) Integration Reference Point (IRP): Information Service (IS)“. 6 3GPP TS 32.616: “Telecommunication management; Configuration Management (CM);

31、Bulk CM Integration Reference Point (IRP): Solution Set (SS) definitions“. 7 3GPP TS 32.606: “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Solution Set (SS) definitions“. 8 W3C REC-xml-20001006: “Extensible Markup Language (XML) 1.0 (Second

32、 Edition)“. 9 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“. 13 3GPP TS 32.300: “Telecommunication manage

33、ment; Configuration Management (CM); Name convention for Managed Objects“ ETSI ETSI TS 132 776 V11.0.0 (2012-10)63GPP TS 32.776 version 11.0.0 Release 113 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the fo

34、llowing apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. For terms and definitions please refer to 3GPP TS 32.101 2, 32.102 3, 32.600 4 and 32.772 5. XML file: file containing an XML document XML document: composed of the su

35、ccession of an optional XML declaration followed by a root XML element NOTE: 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 e

36、ither 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 8. empty XML element: having an empty XML content; an empty XML el

37、ement 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 8. XML content (of an XML element): empty if the XML element is

38、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 the set of XML attribute specifications of t

39、he XML element NOTE: See 8. 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 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 elemen

40、t NOTE: See 8. XML attribute specification: 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 constra

41、ints 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 schema for XML schemas ETSI ETSI TS 132 776 V11.0

42、.0 (2012-10)73GPP TS 32.776 version 11.0.0 Release 11NOTE: See 9, 10 and 11. XML namespace: enables qualifying element 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 typ

43、e: 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 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: Se

44、e 9, 10 and 11. XML element type: declared 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 ty

45、pe for another XML element type NOTE: See 9, 10 and 11. 3.2 Abbreviations For the purposes of the present document, the abbreviations 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, i

46、n TR 21.905 1. CM Configuration Management CORBA Common Object Request Broker Architecture DN Distinguished Name DTD Document Type Definition HNB Home Node B HNS Home Node B Subsystem HNB-GW Home Node B Gateway IDL Interface Definition Language IRP Integration Reference Point IS Information Service

47、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 specification defines the following 3GPP HNS NRM IRP Solution Set Definitions: 3GPP HNS NRM IRP CORBA SS (Annex A) 3GPP HNS

48、 NRM IRP XML Definitions (Annex B) ETSI ETSI TS 132 776 V11.0.0 (2012-10)83GPP TS 32.776 version 11.0.0 Release 11Annex A (normative): CORBA Solution Set This annex contains the CORBA Solution Set for the IRP whose semantics is specified in HNS NRM IRP: Information Service (TS 32.772 5). A.1 Archite

49、ctural features The overall architectural feature of HNS Network Resources IRP is specified in 3GPP TS 32.772 5. This clause specifies features that are specific to the CORBA SS. A.1.1 Syntax for Distinguished Names The syntax of a Distinguished Name is defined in 3GPP TS 32.300 13. 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 with