ETSI TS 132 303 V6.6.0 (2005-12) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) (3GPP TS 32.303 version 6.6.0 Release 6) R GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS 3GPP TS 32.303 version 6.6.0 Release 6 1 ETSI TS 132 303 V6.6.0 (2005-12) Reference RTS/TSGS-0532303v660 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 2005. 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.303 version 6.6.0 Release 6 2 ETSI TS 132 303 V6.6.0 (2005-12) 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.303 version 6.6.0 Release 6 3 ETSI TS 132 303 V6.6.0 (2005-12) Contents Intellectual Property Rights................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................4 Introduction........................................................................................................................................................4 1 Scope........................................................................................................................................................6 2 References................................................................................................................................................6 3 Definitions and abbreviations...................................................................................................................6 3.1 Definitions..........................................................................................................................................................6 3.2 Abbreviations.....................................................................................................................................................7 4 Architectural features...............................................................................................................................7 4.1 Notification services...........................................................................................................................................7 4.1.1 Support of Push and Pull Interface...............................................................................................................7 4.1.2 Support of multiple notifications in one push operation.............................................................................7 4.1.3 Support of filterable and non-filterable notification parameters...................................................................8 5 Mapping...................................................................................................................................................9 5.1 Operation mapping.............................................................................................................................................9 5.2 Operation parameter mapping..........................................................................................................................11 5.3 Notification parameter mapping.......................................................................................................................14 6 IRPAgent's Behaviour............................................................................................................................15 6.1 Subscription......................................................................................................................................................15 6.2 IRPAgent supports multiple categories of Notifications..................................................................................15 6.3 IRPAgent's integrity risk of attach_push_b Method.................................................................................15 6.4 Quality of Service Parameters..........................................................................................................................16 Annex A (normative): IDL specifications..........................................................................................17 A.1 IDL specification (file name "ManagedGenericIRPConstDefs.idl").....................................................17 A.2 IDL specification (file name "ManagedGenericIRPSystem.idl")..........................................................19 A.3 IDL specification (file name "NotificationIRPConstDefs.idl").............................................................20 A.4 IDL specification (file name "NotificationIRPSystem.idl")...................................................................22 A.5 IDL specification (file name "NotificationIRPNotifications.idl")..........................................................25 Annex B (informative): Change history...............................................................................................26 History..............................................................................................................................................................27 ETSI 3GPP TS 32.303 version 6.6.0 Release 6 4 ETSI TS 132 303 V6.6.0 (2005-12) Foreword This Technical Specification (TS) 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.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS) 32.303: Configuration Management (CM); Notification Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS) 32.304: Configuration Management (CM); Notification Integration Reference Point (IRP): Common Management Information Protocol (CMIP) Solution Set (SS) 32.305: Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup Language (XML) definition. 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 a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs. The Itf-N interface 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 [5] and 3GPP TS 32.102 [6]. Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information. For instance a new alarm as specified in Alarm IRP: Information Service [1], is one possible kind of event, an object creation as specified in Basic CM IRP: Information Service [8] is another possible kind of event. ETSI 3GPP TS 32.303 version 6.6.0 Release 6 5 ETSI TS 132 303 V6.6.0 (2005-12) Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to IRPAgent for receiving notifications. This IRP bases its design on work captured in ITU-T Recommendation X.734 [2], OMG Notification Service [4]. The central design ideas are: • Separation of notification Consumers (IRPManagers) from Producers (IRPAgents); • Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications. Common characteristics related to notifications in all other IRPs are gathered in one IRP. ETSI 3GPP TS 32.303 version 6.6.0 Release 6 6 ETSI TS 132 303 V6.6.0 (2005-12) 1 Scope The present document specifies the Common Object Request Broker Architecture (CORBA) Solution Set (SS) for the IRP whose semantics is specified in Notification IRP: Information Service (3GPP TS 32.302 [5]). This Solution Set specification is related to 3GPP TS 32.302 V6.2.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-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] ITU-T Recommendation X.736: "Information technology - Open Systems Interconnection - Systems Management: Security alarm reporting function". [2] OMG TC Document telecom (98-11-01): "Summary of responses to real time survey". [3] OMG CORBA services: Common Object Services Specification, Update: November 22, 1996. (Clause 4 contains the Event Service Specification). [4] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)". [5] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)". [6] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)". [7] 3GPP TS 32.101: "Telecommunication management; Principles and high level requirements". [8] 3GPP TS 32.102: "Telecommunication management; Architecture". [9] 3GPP TS 32.301: "Telecommunication Management; Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements". [10] 3GPP TS 32.111-3: "Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)". [11] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP) management: Requirements". 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [7], 3GPP TS 32.102 [8] and 3GPP TS 32.301 [9] and the following apply: ETSI 3GPP TS 32.303 version 6.6.0 Release 6 7 ETSI TS 132 303 V6.6.0 (2005-12) IRP document version number string (or "IRPVersion"): See 3GPP TS 32.311 [11]. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CORBA Common Object Request Broker Architecture (OMG) EC Event channel (OMG) EM Element Manager IDL Interface Definition Language (OMG) IOR Interoperable Object Reference IS Information Service NC Notification Channel (OMG) NE Network Element NV Name and Value pair OMG Object Management Group QoS Quality of Service SS Solution Set UML Unified Modelling Language (OMG) 4 Architectural features The overall architectural feature of Notification IRP is specified in 3GPP TS 32.302 [5]. This clause specifies features that are specific to the CORBA Solution Set (SS). 4.1 Notification services In the CORBA Solution Set, notifications are emitted by IRPAgent using CORBA Notification service (OMG TC Document telecom [2]) and Structured Events. CORBA Event service (OMG CORBA services [3]) provides event routing and distribution capabilities. CORBA Notification service provides, in addition to Event service, event filtering and support for Quality of Service (QoS) as well. A subset of CORBA Notification services shall be used to support the implementation of notification. This CORBA Notification service subset, in terms of OMG Notification service (OMG TC Document telecom [2]) defined methods, is identified in the present. 4.1.1 Support of Push and Pull Interface The IRPAgent shall support the OMG Notification push interface model. Additionally, it may support the OMG Notification pull interface model as well. 4.1.2 Support of multiple notifications in one push operation For efficiency, IRPAgent uses the following OMG Notification Service (OMG TC Document telecom [2]) defined interface to pack multiple notifications and push them to IRPManager using one method push_structured_events. The method takes as input a parameter of type EventBatch as defined in the OMG CosNotification module (OMG TC Document telecom [2]). This data type is a sequence of Structured Events (see clause 4). Upon invocation, this parameter will contain a sequence of Structured Events being delivered to IRPManager by IRPAgent to which it is connected. The maximum number of events that will be transmitted within a single invocation of this operation is controlled by IRPAgent wide configuration parameter. The amount of time IRPAgent will accumulate individual events into the sequence before invoking this operation is controlled by IRPAgent wide configuration parameter as well. IRPAgent may push EventBatch with only one Structured Event. ETSI 3GPP TS 32.303 version 6.6.0 Release 6 8 ETSI TS 132 303 V6.6.0 (2005-12) The OMG Notification service (OMG TC Document telecom [2]) defined IDL module is shown below. module CosNotifyComm { … Interface SequencePushConsumer : NotifyPublish { void push_structured_events( in CosNotification::EventBatch notifications) raises( CosEventComm::Disconnected); … }; // SequencePushConsumer … }; // CosNotifyComm 4.1.3 Support of filterable and non-filterable notification parameters The OMG Notification service defined IDL CosNotification::StructuredEvent and CosNotification::EventBatch data types are shown below. struct StructuredEvent { EventHeader header; FilterableEventBody filterable_data; any remainder_of_body; }; // StructuredEvent typedef sequence<StructuredEvent> EventBatch; Notification IS parameters are mapped: - either to the Structured Event header, i.e. above IDL StructuredEvent data structure field header; - or to the Structured Event body, and in this case: - when defined in the IS as filterable, to the Structured Event filterable body fields, i.e. above IDL StructuredEvent data structure field filterable_data; - when defined in the IS as non-filterable, to the Structured Event remaining body, i.e. above IDL StructuredEvent data structure field remainder_of_body. The OMG Notification service defined IDL CosNotification::FilterableEventBody data type and its supporting types are shown below. struct Property { PropertyName name; PropertyValue value; }; typedef sequence<Property> PropertySeq; typedef PropertySeq FilterableEventBody; In order to ensure uniform implementation for notification IS parameters mapped to Structured Event Name-Value pairs whether defined in the IS as filterable or as non-filterable, IDL StructuredEvent data structure field remainder_of_body of type any shall be mapped to the IDL data structure NotificationIRPNotifications::NonFilterableEventBody defined in annex clause A.5: struct NonFilterableEventBody { CosNotification::PropertySeq name_value_pairs; any remainder_of_non_filterable_body; }; ETSI 3GPP TS 32.303 version 6.6.0 Release 6 9 ETSI TS 132 303 V6.6.0 (2005-12) 5 Mapping 5.1 Operation mapping Notification IRP: IS (3GPP TS 32.302 [5]) defines semantics of operations visible across this IRP. These operations are the operations of the IOCs defined in 3GPP TS 32.302 [5]. Table 1 maps the operations defined in Notification IRP: IS (3GPP TS 32.302 [5]) to their equivalents (methods) in this Solution Set (SS). Specifically, the table 1 maps the operations of the IOCs defined in 3GPP TS 32.302 [5] to their equivalents in this SS. Since one of the IOCs, the NotificationIRP IOC, inherits from the ManagedGenericIRP IOC [4], the table 1 also maps the operations of ManagedGenericIRP IOC to their equivalents (methods) in this SS. Table 1 also qualifies if a method is Mandatory (M) or Optional (O). ETSI