1、 ETSI TS 132 604 V6.1.0 (2005-03)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);Telecommunication management;Configuration Management (CM);Basic CM Integration Reference Point (IRP)Common Management Information Protocol
2、 (CMIP)Solution Set (SS)(3GPP TS 32.604 version 6.1.0 Release 6)GLOBAL SYSTEM FOR MOBILE COMMUNICATIONSRETSI ETSI TS 132 604 V6.1.0 (2005-03) 1 3GPP TS 32.604 version 6.1.0 Release 6 Reference RTS/TSGS-0532604v610 Keywords GSM, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE
3、 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 Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be m
4、ade available in 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 k
5、ept 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.etsi.org/tb/status/status.asp If yo
6、u 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 except as authorized by written permission. The copyright and the foregoing restriction extend to reprodu
7、ction in all media. European Telecommunications Standards Institute 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM 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 Membe
8、rs. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 132 604 V6.1.0 (2005-03) 2 3GPP TS 32.604 version 6.1.0 Release 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have b
9、een declared to ETSI. The 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
10、“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.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 I
11、PRs not referenced in ETSI SR 000 314 (or 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 tech
12、nical specifications or reports using their 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/queryfo
13、rm.asp . ETSI ETSI TS 132 604 V6.1.0 (2005-03) 3 3GPP TS 32.604 version 6.1.0 Release 6 Contents Intellectual Property Rights2 Foreword.2 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Definitions, symbols and abbreviations .6 3.1 Definitions6 3.2 Abbreviations .6 4 Basic aspects 6 4.1 CMIP sp
14、ecific aspects 6 4.1.1 About Associations.6 4.1.2 About getContainment6 4.1.3 About getMoAttributes .6 4.1.4 About cancelOperation .7 4.1.5 About createMoOperation 7 4.1.6 About deleteMoOperation 7 4.1.7 About setMoAttributeOperation .7 4.2 Mapping .7 4.2.1 Mapping of Information Object Classes .7 4
15、.2.2 Mapping of Operations .8 4.2.3 Mapping of Operation Parameters 8 4.2.3.1 Parameter Mapping of the Operation getMoAttributes .8 4.2.3.2 Parameter Mapping of the Operation getContainment9 4.2.3.3 Parameter Mapping of the Operation cancelOperation 9 4.2.3.4 Parameter Mapping of the Operation creat
16、eMo9 4.2.3.5 Parameter Mapping of the Operation deleteMo 9 4.2.3.6 Parameter Mapping of the Operation setMoAttribute .10 4.2.3.7 Parameter Mapping of the Operation getBasicCmIRPVersion .10 4.2.3.8 Parameter Mapping of the Operation getBasicCmIRPOperationProfile 10 4.2.3.9 Parameter Mapping of the Op
17、eration getBasicCmIRPNotificationProfile10 5 GDMO Definitions.11 5.1 Information Object Classes 11 5.1.1 basicCmIRP 11 5.2 Packages.11 5.2.1 basicCmIRPIdPackage11 5.2.2 basicCmIRPVersionPackage 11 5.2.3 basicCmIRPProfilePackage 11 5.3 Actions .12 5.3.1 getBasicCmIRPVersion (M).12 5.3.2 getBasicCmIRP
18、NotificationProfile (O) 12 5.3.3 getBasicCmIRPOperationProfile (O) .13 5.4 Attributes13 5.4.1 basicCmIRPId.13 5.4.2 supportedBasicCmIRPVersions13 5.5 Parameters 14 6 ASN.1 Definitions15 Annex A (informative): Change history .17 History 18 ETSI ETSI TS 132 604 V6.1.0 (2005-03) 4 3GPP TS 32.604 versio
19、n 6.1.0 Release 6 Foreword 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 formal TSG approval. Should the TSG modify the contents of the presen
20、t 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 approval; 3 or greater indicates TSG approved document under chang
21、e 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. Introduction The present document belongs to the 32.600-series cover
22、ing the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Configuration Management (CM); as identified below: 32.601: “Basic CM Integration Reference Point (IRP): Requirements“; 32.602: “Basic CM Integration Reference Point (IRP): Information Service (IS)“
23、; 32.603: “Basic CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“; 32.604: “Basic CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS)“. A third generation telecommunication network is composed
24、 of a multitude of different network elements (NE). For a successful operation of the network the operator must be provided with mechanisms allowing him to manage the network. These management activities can be grouped into several areas: configuration management, fault management, performance manag
25、ement, and accounting management and security management. The present document is part of a set of technical specifications defining the telecommunication management (TM) of 3G systems. The TM principles are described in TS 32.101 1. The TM architecture is described in TS 32.102 2. The other specifi
26、cations define the interface (ITf-N) between the managing system (manager), which is in general the network manager (NM) and the managed system (agent), which is either an element manager (EM) or the managed NE itself. The Itf-N is composed of a number of integration reference points (IRPs) defining
27、 the information in the agent that is visible for the manager, the operations that the manager may perform on this information and the notifications that are sent from the agent to the manager. One of these IRPs is the Basic Configuration Management IRP. Each IRP is specified by four TSs: the requir
28、ements part, the Information Service (IS) part, the CORBA SS and the CMIP SS. ETSI ETSI TS 132 604 V6.1.0 (2005-03) 5 3GPP TS 32.604 version 6.1.0 Release 6 1 Scope The present document specifies the Common Management Information Protocol (CMIP) Solution Set (SS) for the Basic CM Integration Referen
29、ce Point (IRP): Information Service defined in TS 32.602 6. In detail: - Clause 4 provides the basic concept of the CMIP SS and the mapping between the IOCs, operations and notifications defined in TS 32.602 (Basic Configuration Management IRP: Information Service) 6 to the corresponding CMIP SS equ
30、ivalents. - Clause 5 contains the GDMO definitions for the Basic Configuration Management IRP over the CMIP interfaces, - Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5. This Solution Set specification is related to 3GPP TS 32.602 V6.1.X. 2 References Th
31、e 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, subsequent revisions do n
32、ot 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 32.101: “Telecommunic
33、ation management; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.304: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Sol
34、ution Set (SS)“. 4 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 5 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Concept and high-level requirements“. 6 3GPP TS 32.602: “Telecommunicatio
35、n management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. 7 ITU-T Recommendation X.710 (1991): “Common Management Information Service Definition for CCITT Applications“. 8 ITU-T Recommendation X.721 (02/92): “Information Technology - Open Sys
36、tems Interconnection Structure of Management Information: Definition of Management Information“. 9 ITU-T Recommendation X.730 (01/92): “Information Technology - Open Systems Interconnection Systems Management: Object Management Function“. 10 ITU-T Recommendation X.733 (02/92): “Information Technolog
37、y - Open Systems Interconnection - Alarm Reporting Function“. 11 ITU-T Recommendation M.3100 (07/95): “Maintenance Telecommunications Management Network Generic Network Information Model“. ETSI ETSI TS 132 604 V6.1.0 (2005-03) 6 3GPP TS 32.604 version 6.1.0 Release 6 3 Definitions, symbols and abbre
38、viations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 32.101 1, TS 32.102 2 and TS 32.600 5 apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation 1 CMIP Common Management
39、 Information Protocol DN Distinguished Name GDMO Guidelines for the Definition of Managed Objects IOC Information Object Class IRP Integration Reference Point IS Information Service ISO International Standards Organization ITU-T International Telecommunication Union, Telecommunication Sector MIB Man
40、agement Information Base NE Network Element NRM Network Resource Model TMN Telecommunications Management Network SS Solution Set 4 Basic aspects 4.1 CMIP specific aspects This clause describes some technical details specific to CMIP technology, which are not easy to be handled in the related GDMO de
41、finitions. 4.1.1 About Associations In the GDMO definitions, except the containment relations, all associations among different object classes and object instances are modelled with dedicated pointers of the concerned objects, i.e. various relation role attributes. These pointers are normal object a
42、ttributes and dont require any special treatment. The service operation getMoAttributes defined in TS 32.602 6 and mapped on M-GET in this CMIP solution set is applied for managers to retrieve the values of these association pointers and the notification attributeValueChange is applied for agents to
43、 report any change of the values of these association pointers. 4.1.2 About getContainment In the GDMO definition the containment relations of the Managed Object Classes and those of the managed object instances are described by the name bindings. The service operation getContainment is defined in T
44、S 32.602 6 to enable managers to retrieve the management information about the containment tree of the local MIB of an agent. This service operation is mapped to CMISE M-GET in this CMIP solution set. The information about the containment relation of a local MIB consists of all MOIs abstracted from
45、the output parameter AttributeList of a M-GET operation. 4.1.3 About getMoAttributes The service operation getMoAttributes defined in the Basic CM IRP IS (TS 32.602 6) provides the basic functionality required to retrieve managed objects and their attributes, which is a subset of the functionality p
46、rovided by the corresponding CMISE service operation M-GET. getMoAttributes is mapped to M-GET in this standard. This doesnt ETSI ETSI TS 132 604 V6.1.0 (2005-03) 7 3GPP TS 32.604 version 6.1.0 Release 6 mean any limitation for using M-GET. Users of this standard are encouraged to use the whole func
47、tionality provided by M-Get, especially the input parameter “Attribute Identifier List“ (see ITU-T X.710 7). 4.1.4 About cancelOperation The service operation cancelOperation defined in the Basic CM IRP IS (TS 32.602 6) provides the basic functionality required to cancel an on-going getContainment o
48、r getMoAttributes operation, which is a subset of the functionality provided by the corresponding CMISE service operation M-CANCEL-GET. cancelOperation is mapped to M-CANCEL-GET in this standard. This doesnt mean any limitation for using M-Cancel. Users of this standard are encouraged to use the who
49、le functionality provided by M-CANCEL-GET. 4.1.5 About createMoOperation The service operation createMoOperation defined in the Basic CM IRP IS (TS 32.602 6) provides the basic functionality to create a Managed Object instance within the MIB. This operation creates only one Managed Object instance and is a subset of the functionality provided by the corresponding CMISE service operation M-CREATE (see ITU-T X.710 7). createMoOperation is mapped to M-CREATE in this standard. 4.1.6 About deleteMoOperation The service
