ebook img

TS 132 662 - V6.3.0 - Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS) (3GPP TS 32.662 version 6.3.0 PDF

0.15 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview TS 132 662 - V6.3.0 - Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS) (3GPP TS 32.662 version 6.3.0

ETSI TS 132 662 V6.3.0 (2004-06) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Configuration Management (CM); Kernel CM; Information service (IS) (3GPP TS 32.662 version 6.3.0 Release 6) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS 3GPP TS 32.662 version 6.3.0 Release 6 1 ETSI TS 132 662 V6.3.0 (2004-06) Reference RTS/TSGS-0532662v630 Keywords GSM, 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 N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture 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 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 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 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 Telecommunications Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTM and 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 3GPP TS 32.662 version 6.3.0 Release 6 2 ETSI TS 132 662 V6.3.0 (2004-06) 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 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 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 IPRs 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 technical 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/queryform.asp . ETSI 3GPP TS 32.662 version 6.3.0 Release 6 3 ETSI TS 132 662 V6.3.0 (2004-06) Contents Intellectual Property Rights................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................5 Introduction........................................................................................................................................................5 1 Scope........................................................................................................................................................6 2 References................................................................................................................................................6 3 Definitions and abbreviations...................................................................................................................7 3.1 Definitions..........................................................................................................................................................7 3.2 Abbreviations.....................................................................................................................................................8 4 System overview......................................................................................................................................9 4.1 System context...................................................................................................................................................9 4.2 Compliance rules................................................................................................................................................9 5 Modelling approach................................................................................................................................10 5.1 IRP Information Service modelling approach..................................................................................................10 6 Information Object Classes (IOCs)........................................................................................................10 6.1 Imported Information entities and local labels.................................................................................................10 6.2 Class diagram...................................................................................................................................................11 6.2.1 Attributes and relationships........................................................................................................................11 6.2.2 Inheritance..................................................................................................................................................11 6.3 Information Object Class Definitions...............................................................................................................12 6.3.1 KernelCmIRP.............................................................................................................................................12 6.3.1.1 Definition..............................................................................................................................................12 6.3.2 ManagedEntity............................................................................................................................................12 6.3.2.1 Definition..............................................................................................................................................12 6.4 Information relationship definitions.................................................................................................................12 6.4.1 containment (M).........................................................................................................................................12 6.4.1.1 Definition..............................................................................................................................................12 6.4.1.2 Role.......................................................................................................................................................12 6.4.1.3 Constraint..............................................................................................................................................12 7 Interface Definition................................................................................................................................13 7.1 Class diagram...................................................................................................................................................13 7.2 Generic rules....................................................................................................................................................13 7.3 Interface KernelCmIRPOperations...................................................................................................................14 7.3.1 Operation getNRMIRPVersion (M)......................................................................................................14 7.3.1.1 Definition..............................................................................................................................................14 7.3.1.2 Input parameters....................................................................................................................................14 7.3.1.3 Output parameters.................................................................................................................................14 7.3.1.4 Pre-condition.........................................................................................................................................14 7.3.1.5 Post-condition.......................................................................................................................................14 7.3.1.6 Exceptions.............................................................................................................................................15 7.4 Interface KernelCmIRPNotifications_1...........................................................................................................15 7.4.1 notifyObjectCreation (O)............................................................................................................................15 7.4.1.1 Definition..............................................................................................................................................15 7.4.1.2 Input Parameters...................................................................................................................................15 7.4.1.3 Triggering Event...................................................................................................................................15 7.4.1.3.1 From-state........................................................................................................................................15 7.4.1.3.2 To-state............................................................................................................................................16 7.5 Interface KernelCmIRPNotifications_2...........................................................................................................16 7.5.1 notifyObjectDeletion (O)............................................................................................................................16 7.5.1.1 Definition..............................................................................................................................................16 7.5.1.2 Input Parameters...................................................................................................................................16 ETSI 3GPP TS 32.662 version 6.3.0 Release 6 4 ETSI TS 132 662 V6.3.0 (2004-06) 7.5.1.3 Triggering Event...................................................................................................................................17 7.5.1.3.1 From-state........................................................................................................................................17 7.5.1.3.2 To-state............................................................................................................................................17 7.6 Interface KernelCmIRPNotifications_3...........................................................................................................17 7.6.1 notifyAttributeValueChange (O)................................................................................................................17 7.6.6.1 Definition..............................................................................................................................................17 7.6.6.2 Input Parameters...................................................................................................................................18 7.6.6.3 Triggering Event...................................................................................................................................18 7.6.6.3.1 From-state........................................................................................................................................18 7.6.6.3.2 To-state............................................................................................................................................18 7.7 Interface KernelCmIRPNotifications_4...........................................................................................................19 7.7.1 notifyCMSynchronizationRecommended (O)............................................................................................19 7.7.1.1 Definition..............................................................................................................................................19 7.7.1.2 Input Parameters...................................................................................................................................20 7.7.1.3 Triggering Event...................................................................................................................................20 7.7.1.3.1 From-state........................................................................................................................................20 7.7.1.3.2 To-state............................................................................................................................................20 7.8 Interface KernelCmIRPNotifications_5...........................................................................................................21 7.8.1 notifyStateChange (O)................................................................................................................................21 7.8.1.1 Definition..............................................................................................................................................21 7.8.1.2 Input parameters....................................................................................................................................21 7.8.1.3 Triggering Event...................................................................................................................................21 7.8.1.3.1 From-state........................................................................................................................................21 7.8.1.3.2 To-state............................................................................................................................................22 Annex A (normative): Notification/Event Types...............................................................................23 Annex B (informative): Change history...............................................................................................24 History..............................................................................................................................................................25 ETSI 3GPP TS 32.662 version 6.3.0 Release 6 5 ETSI TS 132 662 V6.3.0 (2004-06) Foreword This Technical Specification has been produced by the 3rd Generation 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 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 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 is part of a TS-family covering the 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.661 Configuration Management (CM); Kernel CM requirements 32.662 Configuration Management (CM); Kernel CM Information Service (IS) 32.663 Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.664 Configuration Management (CM); Kernel CM Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) 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 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. 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 resources/objects in one or several NEs. ETSI 3GPP TS 32.662 version 6.3.0 Release 6 6 ETSI TS 132 662 V6.3.0 (2004-06) 1 Scope The present document defines Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management related information to one or several 'IRPManagers' (typically Network Managers). The function of this Kernel CM IRP Information Service is to define an interface that provides the essential CM services. While it is not expected that the Kernel CM IRP alone will provide adequate CM capability, The Kernel CM IRP is expected to provide the common supporting capability required for other IRPs such as the Basic CM IRP or the Bulk CM IRP, each of which require the Kernel CM IRP. 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, 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 as the present document. [1] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements". [2] 3GPP TS 32.102: "Telecommunication management; Architecture". [3] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)". [4] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)". [5] 3GPP TS 32.622: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Network Resource Model (NRM)". [6] 3GPP TS 32.672: "Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP): Information Service (IS)". [7] ITU-T Recommendation X.710 (1997): "Information technology - Open Systems Interconnection - Common Management Information Service". [8] ITU-T Recommendation X.721 (1992): "Information technology - Open Systems Interconnection - Structure of Management Information: Definition of management information". [9] ITU-T Recommendation X.730 (1992): "Information technology - Open Systems Interconnection - Systems Management: Object Management Function". [10] ITU-T Recommendation X.733 (1992): "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function". [11] - [12] Void. [13] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name convention for Managed Objects". [14] 3GPP TS 32.600: "Telecommunication management; Configuration Management (CM); Concept and high-level requirements". ETSI 3GPP TS 32.662 version 6.3.0 Release 6 7 ETSI TS 132 662 V6.3.0 (2004-06) [15] ITU-T Recommendation X.720: "Information technology - Open Systems Interconnection - Structure of management information: Management information model". [16] 3GPP TS 32.623: "Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)". [17] 3GPP TS 32.643: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)". [18] 3GPP TS 32.642: "Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP): Network Resource Model (NRM)". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. For terms and definitions not found here, please refer to TS 32.101 [1], TS 32.102 [2] and TS 32.600 [14]. association: In general it is used to model relationships between Managed Objects. Associations can be implemented in several ways, such as: (1) name bindings, (2) reference attributes, and (3) association objects. This IRP stipulates that containment associations shall be expressed through name bindings, but it does not stipulate the implementation for other types of associations as a general rule. These are specified as separate entities in the object models (UML diagrams). Currently however, all (non-containment) associations are modelled by means of reference attributes of the participating MOs. Managed Element (ME): instance of the Managed Object Class G3ManagedElement Managed Object (MO): In the context of the present document, a Managed Object (MO) is a software object that encapsulates the manageable characteristics and behaviour of a particular Network Resource. The MO is instance of a MO class defined in a MIM/NRM. An MO class has attributes that provide information used to characterize the objects that belong to the class. Furthermore, an MO class can have operations that represent the behaviour relevant for that class. An MO class may support notifications that provide information about an event occurrence within a network resource. Management Information Base (MIB): A MIB is an instance of an NRM and has some values on the defined attributes and associations specific for that instance. In the context of the present document, an MIB consists of: (1) a Name space (describing the MO containment hierarchy in the MIB through Distinguished Names), (2) a number of Managed Objects with their attributes, and (3) a number of Associations between these MOs. Also note that TMN (ITU-T Recommendation X.710 [7]) defines a concept of a Management Information Tree (also known as a Naming Tree) that corresponds to the name space (containment hierarchy) portion of this MIB definition. Figure 3.1 depicts the relationships between a Name space and a number of participating MOs (the shown association is of a non-containment type). ETSI 3GPP TS 32.662 version 6.3.0 Release 6 8 ETSI TS 132 662 V6.3.0 (2004-06) Namespace (containment hierarhy) MO MIB Association Figure 3.1: Relationships between a Name space and a number of participating MOs Management Information Model (MIM): Also referred to as NRM – see the definition below. Name space: A name space is a collection of names. The IRP name convention (see TS 32.300 [13]) restricts the name space to a hierarchical containment structure, including its simplest form - the one-level, flat name space. All Managed Objects in a MIB shall be included in the corresponding name space and the MIB/name space shall only support a strict hierarchical containment structure (with one root object). A Managed Object that contains another is said to be the superior (parent); the contained Managed Object is referred to as the subordinate (child). The parent of all MOs in a single name space is called a Local Root. The ultimate parent of all MOs of all managed systems is called the Global Root. Network Resource Model (NRM): A model representing the actual managed telecommunications network resources that a System is providing through the subject IRP. An NRM describes Managed Object Classes, their associations, attributes and operations. The NRM is also referred to as "MIM" (see above), which originates from the ITU-T TMN. Node B: A logical node responsible for radio transmission/reception in one or more cells to/from the User Equipment. It terminates the Iub interface towards the RNC. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CMIP Common Management Information Protocol CMIS Common Management Information Service CN Core Network CORBA Common Object Request Broker Architecture DN Distinguished Name (see TS 32.300 [13]) EM Element Manager FM Fault Management IDL Interface Definition Language IRP Integration Reference Point ITU-T International Telecommunication Union, Telecommunication Sector ME Managed Element MIB Management Information Base MIM Management Information Model MO Managed Object MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network Manager NR Network Resource NRM Network Resource Model PM Performance Management RDN Relative Distinguished Name (see TS 32.300 [13]) SNMP Simple Network Management Protocol SS Solution Set TMN Telecommunications Management Network UML Unified Modelling Language UMTS Universal Mobile Telecommunications System VSE Vendor Specific Extensions ETSI 3GPP TS 32.662 version 6.3.0 Release 6 9 ETSI TS 132 662 V6.3.0 (2004-06) 4 System overview 4.1 System context Figures 4.1 and 4.2 identify system contexts of the IRP defined by the present specification in terms of its implementation called IRPAgent and the user of the IRPAgent, called IRPManager. For a definition of IRPManager and IRPAgent, see TS 32.102 [2]. The IRPAgent implements and supports this IRP. The IRPAgent can reside in an Element Manager (EM) or a Network Element (NE) (see also [2] clause 8). In the former case, the interfaces (represented by a thick dotted line) between the EM and the NEs are not the subject of this IRP. An NE can be managed via System Context A or B. The criterion for choosing System Context A or B, to manage a particular NE, is implementation dependent. An IRPAgent shall support one of the two System Contexts. By observing the interaction across the Itf-N, an IRPManager cannot deduce if the EM and NE are integrated in a single system or if they run in separate systems. IRPManager IRPAgent NEs NM EM Itf-N Notification IRP Kernel CM IRP Figure 4.1: System Context A IRPManager IRPAgent NM NE Itf-N Notification IRP Kernel CM IRP Figure 4.2: System Context B 4.2 Compliance rules For general definitions of compliance rules related to qualifiers (Mandatory/Optional/Conditional) for operations, notifications and parameters (of operations and notifications) please refer to TS 32.102 [2]. ETSI

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.