ETSI TS 132 106-6-2003 Universal Mobile Telecommunications System (UMTS) Telecommunication management Configuration Management (CM) Part 6 Basic Configuration Management Integratio.pdf

《ETSI TS 132 106-6-2003 Universal Mobile Telecommunications System (UMTS) Telecommunication management Configuration Management (CM) Part 6 Basic Configuration Management Integratio.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 106-6-2003 Universal Mobile Telecommunications System (UMTS) Telecommunication management Configuration Management (CM) Part 6 Basic Configuration Management Integratio.pdf（38页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 106-6 V3.4.0 (2003-12)Technical Specification Universal Mobile Telecommunications System (UMTS);Telecommunication management;Configuration Management (CM);Part 6: Basic Configuration Management IntegrationReference Point (IRP): Common Object RequestBroker Architecture (CORBA) solution s

2、et(3GPP TS 32.106-6 version 3.4.0 Release 1999)ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 1 3GPP TS 32.106-6 version 3.4.0 Release 1999 Reference RTS/TSGS-0532106-6v340 Keywords UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret

3、 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 electronic version or

4、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 within ETSI Secretari

5、at. 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 document, send your comm

6、ent to: editoretsi.org 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 Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTS

7、TM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI

8、ETSI TS 132 106-6 V3.4.0 (2003-12) 2 3GPP TS 32.106-6 version 3.4.0 Release 1999 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI mem

9、bers 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 available on the ETSI Web server (http:/webapp.e

10、tsi.org/IPR/home.asp). 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 are, or may be, or may become, e

11、ssential 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 identities. These should be inte

12、rpreted 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 106-6 V3.4.0 (2003-12) 3 3GPP TS 32.106-6 version 3.4.0 Release 1999 Contents Intellectual

13、 Property Rights2 Foreword.2 Foreword.5 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .6 4 IRP Solution Set version 7 5 Architectural features .7 5.1 Notifications .7 5.2 Filter language7 5.3 Syntax for Distinguished Names and Versions 7

14、 6 Mapping .7 6.1 General mappings.7 6.2 Operation and Notification mapping 8 6.3 Operation parameter mapping 8 6.4 Notification attribute mapping .9 6.5 Network Resource Model (NRM) mapping .11 6.5.1 Generic NRM Managed Object Class (MOC) mapping .11 6.5.1.1 MOC G3SubNetwork11 6.5.1.2 MOC G3Managed

15、Element .11 6.5.1.3 MOC MeContext.12 6.5.1.4 MOC ManagementNode.12 6.5.1.5 MOC ManagedFunction .12 6.5.1.6 MOC IRPAgent.12 6.5.1.7 MOC NotificationIRP.12 6.5.1.8 MOC AlarmIRP.13 6.5.1.9 MOC BasicCmIRP13 6.5.2 UMTS NRM Managed Object Class (MOC) mapping.13 6.5.2.1 MOC RncFunction13 6.5.2.2 MOC UtranC

16、ell.13 6.5.2.3 MOC NodeBFunction.14 6.5.2.4 MOC IubLink .14 6.5.2.5 MOC MscFunction14 6.5.2.6 MOC HlrFunction14 6.5.2.7 MOC VlrFunction15 6.5.2.8 MOC AucFunction15 6.5.2.9 MOC EirFunction15 6.5.2.10 MOC SmsIwmscFunction.15 6.5.2.11 MOC SmsGmscFunction 15 6.5.2.12 MOC SgsnFunction16 6.5.2.13 MOC Ggsn

17、Function16 6.5.2.14 MOC BgFunction16 6.5.2.15 MOC GmscFunction16 7 Use of OMG Structured Event .17 8 Rules for management information model extensions .19 8.1 Allowed extensions 19 ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 4 3GPP TS 32.106-6 version 3.4.0 Release 1999 8.2 Extensions not allowed.19 Ann

18、ex A (normative): CORBA IDL, Access Protocol 20 Annex B (normative): CORBA IDL, Notification Definitions .26 Annex C (normative): CORBA IDL, NRM Definitions30 Annex D (informative): Change history .36 History 37 ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 5 3GPP TS 32.106-6 version 3.4.0 Release 1999 Fo

19、reword This Technical Specification (TS) 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 formal TSG approval. Should the TSG modify the contents of the present document, it

20、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 approval; 3 or greater indicates TSG approved document under change control. y th

21、e 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. Introduction The present document is part 6 of a multi-part TS covering the 3rdGene

22、ration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication Management; Configuration Management, as identified below: Part 1: “3G Configuration Management: Concept and Requirements“; Part 2: “Notification Integration Reference Point: Information Service

23、Version 1“; Part 3: “Notification Integration Reference Point: CORBA Solution Set Version 1:1“; Part 4: “Notification Integration Reference Point: CMIP Solution Set Version 1:1“; Part 5: “Basic Configuration Management IRP: Information Model Version 1“; Part 6: “Basic Configuration Management IRP CO

24、RBA Solution Set Version 1:1“; Part 7: “Basic Configuration Management IRP CMIP Solution Set Version 1:1“; Part 8: “Name Convention for Managed Objects“. Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G-network as i

25、t evolves. CM actions have the objective to control and monitor the actual configuration on 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 opti

26、misation programme (e.g. modifications), and to maintain the overall Quality of Service. 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 Managemen

27、t is built up by a number of Integration Reference Points (IRPs) and a related Name 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 d

28、efined herein, used by this as well as other technical specifications for telecom management produced by 3GPP. All these documents are included in Parts 2 and onwards of the 3GPP TS 32.106. This document constitutes 32.106 Part 6 - Basic Configuration Management IRP: CORBA Solution Set Version 1:1.

29、ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 6 3GPP TS 32.106-6 version 3.4.0 Release 1999 1 Scope The purpose of this Basic Configuration Management (CM) IRP: Information Service CORBA Solution Set is to define the mapping of the IRP information model (see 3GPP TS 32.106-5 4) to the protocol specific de

30、tails necessary for implementation of this IRP in a CORBA/IDL environment. The present document does not describe any Network Resource Model (NRM) this is described in 3GPP TS 32.106-5 4. Please note that 3GPP TS 32.106-5 4 defines an IRP Information Model, which comprises both an IS and NRM definit

31、ion. 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-specific. For a specific reference, subse

32、quent 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 as the present document. 1 3GPP TS 3

33、2.101: “Telecommunication management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.106-1: “3G Configuration Management“. 4 3GPP TS 32.106-5: “Basic Configuration Management IRP: Information Model“. 5 3GPP TS 32.106-8: “Name Con

34、vention for Managed Objects“. 6 OMG Notification Service, Version 1.0. 7 OMG CORBA services: Common Object Services Specification, Update: November 22, 1996. 8 The Common Object Request Broker: Architecture and Specification (for specification of valid version, see 1). 9 3GPP TS 32.106-3: “Notificat

35、ion IRP: CORBA Solution Set, Version 1:1“. 10 3GPP TS 32.111-3: “Alarm IRP: CORBA Solution Set, Version 1:1“. 3 Definitions and abbreviations 3.1 Definitions For terms and definitions please refer to 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.106-1 3 and 3GPP TS 32.106-5 4. 3.2 Abbreviations For

36、 the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 7 3GPP TS 32.106-6 version 3.4.0 Release 1999 DN Distinguished Name IS Information Service IDL Interface Definition Language (OMG) IRP Int

37、egration Reference Point MO Managed Object MOC Managed Object Class NRM Network Resource Model OMG Object Management Group SS Solution Set 4 IRP Solution Set version The version of this CORBA Solution Set (SS) is 1:1, where the first “1“ means that it corresponds to the Information Model version 1,

38、and the second “1“ means that it is the first CORBA Solution Set corresponding to Information Model version 1. 5 Architectural features The overall architectural feature of Basic Configuration Management IRP is specified in 3GPP TS 32.106-5 4. This clause specifies features that are specific to the

39、CORBA SS. 5.1 Notifications Notifications are sent according to the Notification IRP: CORBA SS (see 3GPP TS 32.106-3 9). The contents of the Basic CM IRP notifications are defined in the present document. 5.2 Filter language The filter language used in the SS is the Extended Trader Constraint Langua

40、ge (see OMG Notification Service 6). IRPAgents may throw a FilterComplexityLimit exception when a given filter is too complex. However, for 3GPP Release 99 an “empty filter“ shall be used i.e. a filter that satisfies all MOs of a scoped search (this does not affect the filter for notifications as de

41、fined in the Notification IRP see 3GPP TS 32.106-3 9). 5.3 Syntax for Distinguished Names and Versions The format of a Distinguished Name is defined in 3GPP TS 32.106-8 5. The Version of this IRP is represented as a string. The value of this version is defined by a constant in Annex A. 6 Mapping 6.1

42、 General mappings The IS parameter name managedObjectInstance is mapped into DN. Attributes modelling associations as defined in the NRM (here also called “reference attributes“) are in this SS mapped to attributes. The names of the reference attributes in the NRM are mapped to the corresponding att

43、ribute names in the MOC. When the cardinality for an association is 01 or 11 the datatype for the reference attribute is defined as an MOReference. The value of an MO reference contains the distinguished name of the associated MO. When the cardinality for an association allows more than one referred

44、 MO, the reference attribute will be of type MOReferenceSet, which contains a sequence of MO references. ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 8 3GPP TS 32.106-6 version 3.4.0 Release 1999 If a reference attribute is changed, an AttributeValueChange notification is emitted. 6.2 Operation and Notif

45、ication mapping The IS part of Basic CM IRP: IM (see 3GPP TS 32.106-5 4) defines semantics of operation and notification visible across the Basic Configuration Management IRP. Table 1 indicates mapping of these operations and notifications to their equivalents defined in this SS. Table 1: Mapping fr

46、om IS Notification/Operation to SS equivalents IS Operation/ notification (3GPP TS 32.106-5 4) SS Method Qualifier getMoAttributes BasicCmIrpOperations:find_managed_objects BasicCmInformationIterator:next_basicCmInformations BasicCmInformationIterator:destroy M getContainment BasicCmIrpOperations:fi

47、nd_managed_objects BasicCmInformationIterator:next_basicCmInformations BasicCmInformationIterator:destroy O getBasicCmIRPVersion get_basicCm_IRP_version M notifyObjectCreation ( to convey of a new Managed Object created) See Notification IRP: CORBA SS 9 O notifyObjectDeletion ( to convey of a new Ma

48、naged Object deleted) See Notification IRP: CORBA SS 9 O notifyAttributeValueChange (to convey of a change of one or several attributes of a Managed Object) See Notification IRP: CORBA SS 9 O 6.3 Operation parameter mapping The IS part of Basic CM IRP: IM (see 3GPP TS 32.106-5 4) defines semantics o

49、f parameters carried in operations across the Basic Configuration Management IRP. Tables 2, 3 and 4 indicate the mapping of these parameters, as per operation, to their equivalents defined in this SS. The SS operation find_managed_objects is equivalent to the IS operation getMoAttributes when called with ResultContents set to NAMES_AND_ATTRIBUTES. Iterating the BasicCmInformationIterator is used to fetch the result. ETSI ETSI TS 132 106-6 V3.4.0 (2003-12) 9 3GPP TS 32.106-6 version 3.4.0 Release 1999