ETSI TS 132 303-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

1、 ETSI TS 132 303 V9.0.0 (2010-02)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Telecommunication management;Configuration Management (CM);Notification Integration Reference Point (IRP);Common Object Request Broker

2、Architecture (CORBA)Solution Set (SS) (3GPP TS 32.303 version 9.0.0 Release 9)ETSI ETSI TS 132 303 V9.0.0 (2010-02)13GPP TS 32.303 version 9.0.0 Release 9Reference RTS/TSGS-0532303v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00

3、 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 made available in more th

4、an 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 networ

5、k 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 pre

6、sent 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. Euro

7、pean Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP

8、Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 303 V9.0.0 (2010-02)23GPP TS 32.303 version 9.0.0

9、 Release 9Intellectual 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: “Intellectua

10、l 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 investigatio

11、n, 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

12、 (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

13、 cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 132 303 V9.0.0 (2010-02)33GPP TS 32.303 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 6g32 Refer

14、ences 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Architectural features . 8g34.1 Notification services . 8g34.1.1 Support of Push and Pull Interface . 8g34.1.2 Support of multiple notifications in one push operation . 8g34.1.3 Support of filterable and non-fi

15、lterable notification parameters . 9g35 Mapping . 9g35.1 Operation mapping . 9g35.2 Operation parameter mapping 11g35.3 Notification parameter mapping . 14g36 IRPAgents Behaviour 15g36.1 Subscription 15g36.2 IRPAgent supports multiple categories of Notifications 15g36.3 IRPAgents integrity risk of a

16、ttach_push_b Method . 16g36.4 Quality of Service Parameters 16g3Annex A (normative): IDL specifications 17g3A.1 IDL specification (file name “ManagedGenericIRPConstDefs.idl“) . 17g3A.2 IDL specification (file name “ManagedGenericIRPSystem.idl“) 19g3A.3 IDL specification (file name “NotificationIRPCo

17、nstDefs.idl“) . 20g3A.4 IDL specification (file name “NotificationIRPSystem.idl“) . 22g3A.5 IDL specification (file name “NotificationIRPNotifications.idl“) 25g3Annex B (informative): Change history . 26g3History 27g3ETSI ETSI TS 132 303 V9.0.0 (2010-02)43GPP TS 32.303 version 9.0.0 Release 9Forewor

18、d 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 will

19、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 sec

20、ond 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 3rdGeneration Part

21、nership 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

22、 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.305: Configuration Management (CM); Notification Integration Reference Point (IRP): eXtensible Markup L

23、anguage (XML) definition 32.307: Configuration Management (CM); Notification Integration Reference Point (IRP): Simple Object Access Protocol (SOAP) Solution Set (SS) Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G

24、 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

25、 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 acti

26、ons 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

27、) 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

28、as specified in Basic CM IRP: Information Service 8 is another possible kind of event. ETSI ETSI TS 132 303 V9.0.0 (2010-02)53GPP TS 32.303 version 9.0.0 Release 9Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a ne

29、twork 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 ce

30、ntral 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

31、 one IRP. ETSI ETSI TS 132 303 V9.0.0 (2010-02)63GPP TS 32.303 version 9.0.0 Release 91 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). T

32、his Solution Set specification is related to 3GPP TS 32.302. 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

33、, 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

34、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 O

35、bject 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; Configurati

36、on 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

37、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 Manag

38、ement; 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“. ETSI ETSI TS 132 303 V9.0.0 (2010-02)73GPP TS 32.303 ve

39、rsion 9.0.0 Release 93 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: IRP document version number string (or “IRPVersion“): See 3GPP TS 32.311

40、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 ManagerIDL Interface Definition Language (OMG) IOR Interoperable Object Reference IS

41、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) ETSI ETSI TS 132 303 V9.0.0 (2010-02)83GPP TS 32.303 version 9.0.0 Release 94 Architectural features The

42、 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 Do

43、cument 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 Notificatio

44、n 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

45、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

46、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 invoca

47、tion, 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

48、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. The OMG Notification service (OMG TC Document telecom 2) defined IDL module

49、 is shown below. module CosNotifyComm Interface SequencePushConsumer : NotifyPublish void push_structured_events( in CosNotification:EventBatch notifications) raises( CosEventComm:Disconnected); ; / SequencePushConsumer ; / CosNotifyComm ETSI ETSI TS 132 303 V9.0.0 (2010-02)93GPP TS 32.303 version 9.0.0 Release 94.1.3 Support of filterable and non-filterable notification parameters The OMG Notification service defined IDL CosNotification:StructuredEvent and CosNotification:EventBatch data