ETSI TS 132 111-3-2012 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par_1.pdf

《ETSI TS 132 111-3-2012 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 132 111-3-2012 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Fault Management Par_1.pdf（45页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 132 111-3 V9.1.0 (2012-09) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Soluti

2、on Set (SS) (3GPP TS 32.111-3 version 9.1.0 Release 9) Technical Specification ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)13GPP TS 32.111-3 version 9.1.0 Release 9 Reference RTS/TSGS-0532111-3v910 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94

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

4、ore 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

5、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 t

6、he 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

7、. European Telecommunications Standards Institute 2012. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational

8、 Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)23GPP TS 32.111-3 version 9.1.0 Release 9 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. T

9、he 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 f

10、rom the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/ipr.etsi.org). 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 (

11、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 t

12、heir 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 ETSI TS 132 111-3 V9.1.0 (

13、2012-09)33GPP TS 32.111-3 version 9.1.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 4g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g33.3 IRP document version number string . 6g34 Architectural

14、 Features 6g34.1 Notification Services 6g34.2 Push and Pull Style . 6g34.3 Support multiple notifications in one push operation . 6g34.4 Filter . 6g35 Mapping . 8g35.1 Operation and Notification mapping 8g35.2 Operation parameter mapping 9g35.3 Notification parameter mapping . 17g36 AlarmIRPNotifica

15、tions Interface . 27g36.1 Method push (M) 27g3Annex A (normative): IDL specifications 28g3A.1 IDL specification (file name “AlarmIRPConstDefs.idl“) . 28g3A.2 IDL specification (file name AlarmIRPSystem.idl) . 36g3A.3 IDL specification (file name “AlarmIRPNotifications.idl“) . 39g3Annex B (informativ

16、e): Change history . 43g3History 44g3ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)43GPP TS 32.111-3 version 9.1.0 Release 9 Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work with

17、in 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 f

18、or 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 hav

19、e been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.111-1 “Fault Management; Part 1: 3G fault man

20、agement requirements“. 32.111-2 “Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)“. 32.111-3 “Fault Management; Part 3: Alarm Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set (SS)“. 32.111-5 “Fault Management

21、; Alarm Integration Reference Point (IRP): eXtensible Markup Language (XML) definitions“. 32.111-7 “Fault Management; Alarm Integration Reference Point (IRP): SOAP Solution Set (SS)“. 1 Scope The present contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Informati

22、on Service (TS 32.111-2 6). Clause 1 to 3 provides background information. Clause 4 provides key architectural features supporting the SS. Clause 5 defines the mapping of operations, notification, parameters and attributes defined in IS to their SS equivalents. Clause 6 describes the notification in

23、terface containing the push method. Annex A contains the IDL specification. This Solution Set specification is related to TS 32.111-2 V7.1.X. ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)53GPP TS 32.111-3 version 9.1.0 Release 9 2 References The following documents contain provisions which, through refere

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

25、lies. 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 OMG TC Document telecom/98-11-01: “OMG Notification Service“. http:/www.omg.org/technology/

26、documents/ 2 OMG CORBA Services: “Common Object Services Specification, Update: November 22, 1996“ (Clause 4 contains the Event Service specification). http:/www.omg.org/technology/documents/ 3 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed

27、Objects“. 4 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.303: “ Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Common

28、 Object Request Broker Architecture (CORBA) Solution Set (SS)“. 6 3GPP TS 32.111-2: “Telecommunication management; Fault Management; Part 2: Alarm Integration Reference Point: Information Service (IS)“. 7 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) manage

29、ment; Information Service (IS)“. 8 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 TS 32.111-2 6 apply. 3.2

30、 Abbreviations For the purposes of the present document, the following abbreviations apply: CORBA Common Object Request Broker Architecture IDL Interface Definition Language IRP Integration Reference Point MOC Managed Object Class MOI Managed Object Instance NE Network Element OMG Object Management

31、Group TMN Telecommunications Management Network UML Unified Modelling Language ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)63GPP TS 32.111-3 version 9.1.0 Release 9 3.3 IRP document version number string The IRP document version number (sometimes called IRP version or version number) string is used to id

32、entify the present document. The definition of IRP document version number string in 3GPP TS 32.311 8 provides the rule to derive such a string. This string is used for the return value of get_alarm_irp_versions(). It is used as return value of get_notification_categories() if the Notification IRP s

33、upports the emission of notifications defined by this Alarm IRP version. It is also used in the domain_name attribute of a structured event carrying alarm information defined by this Alarm IRP version. 4 Architectural Features The overall architectural feature of Alarm IRP is specified in 3G TS 32.1

34、11-2 6. This clause specifies features that are specific to the CORBA SS. 4.1 Notification Services In implementations of CORBA SS, IRPAgent conveys Alarm Information to IRPManager via OMG Notification Service (OMG Notification Service 1). OMG Event Service 2 provides event routing and distribution

35、capabilities. OMG Notification Service provides, in addition to Event Service, event filtering and Quality Of Service (QOS) as well. A necessary and sufficient sub set of OMG Notification Services shall be used to support AlarmIRPNotifications notifications as specified in 3G TS 32.111-2 6. 4.2 Push

36、 and Pull Style OMG Notification Service defines two styles of interaction. One is called push style. In this style, IRPAgent pushes notifications to IRPManager as soon as they are available. The other is called pull style. In this style, IRPAgent keeps the notifications till IRPManager requests for

37、 them. This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O). 4.3 Support multiple notifications in one push operation For efficiency reasons, IRPAgent may send multiple notifications using one single push operation. To pack multiple notif

38、ications into one push operation, IRPAgent may wait and not invoke the push operation as soon as notifications are available. To avoid IRPAgent to wait for an extended period of time that is objectionable to IRPManager, IRPAgent shall implement an IRPAgent wide timer configurable by administrator. O

39、n expiration of this timer, IRPAgent shall invoke push if there is at least one notification to be conveyed to IRPManager. This timer is re-started after each push invocation. 4.4 Filter IRPAgent shall optionally support alarm filtering based on IRPManager“s supplied alarm filter constraints (e.g. a

40、s parameter in subscribe() of 3G TS 32.302 4. Alarm filtering can be applied in the following cases: - It is applicable to alarms emitted by IRPAgent via AlarmIRPNotifications. IRPManager supplies alarm filter constraint via the subscribe method. This filter is effective during the period of subscri

41、ption. - It is applicable to alarms returned by IRPAgent via the out parameter of get_alarm_list method. IRPManager supplies alarm filter constraint via the get_alarm_list method. This filter is effective only for this method invocation. ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)73GPP TS 32.111-3 versi

42、on 9.1.0 Release 9 - It is applicable to the calculation of alarm counts returned by IRPAgent via the out parameters of get_alarm_count method. IRPManager supplies alarm filter constraint via the get_alarm_count method. This filter is effective only for this method invocation. This SS shall use of f

43、ilter constraint grammar specified by reference OMG Notification Service 1. The name of the grammar is called “EXTENDED_TCL“. See clause 2.4, Default Filter Constraint Language in OMG Notification Service 1. This SS shall use this grammar only. ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)83GPP TS 32.111-

44、3 version 9.1.0 Release 9 5 Mapping 5.1 Operation and Notification mapping Alarm IRP: IS 3G TS 32.111-2 6 defines semantics of operation and notification visible across the Alarm IRP. Table 1 indicates mapping of these operations and notifications to their equivalents defined in this SS. Table 1: Ma

45、pping from IS Notification/Operation to SS equivalents IS Operation/ notification 3G TS 32.111-2 6 SS Method Qualifier acknowledgeAlarms acknowledge_alarms MunacknowledgeAlarms unacknowledge_alarms O getAlarmList get_alarm_list M getIRPVersion (note) get_alarm_irp_versions M getAlarmCount get_alarm_

46、count OsetComment comment_alarms OclearAlarms clear_alarms O getOperationProfile (note) get_alarm_irp_operations_profile O getNotificationProfile (note) get_alarm_irp_notification_profile O notifyNewAlarm push_structured_eventNote that OMG Notification Service OMG Notification Service 1 defines this

47、 method. See clause 6.1 M notifyClearedAlarm push_structured_eventSee clause 6.1 M notifyChangedAlarm push_structured_eventSee clause 6.1 M notifyAckStateChanged push_structured_event See clause 6.1 M notifyAlarmListRebuilt push_structured_eventSee clause 6.1 M notifyComments push_structured_eventSe

48、e clause 6.1 O notifyPotentialFaultyAlarmList push_structured_event See clause 6.1 O NOTE: This operation is of ManagedGenericIRP IOC specified in 7. The AlarmIRP IOC of 6 inherits from it. ETSI ETSI TS 132 111-3 V9.1.0 (2012-09)93GPP TS 32.111-3 version 9.1.0 Release 9 5.2 Operation parameter mappi

49、ng Reference 3G TS 32.111-2 6 defines semantics of parameters carried in operations across the Alarm IRP. The following set of tables indicates the mapping of these parameters, as per operation, to their equivalents defined in this SS. Table 2: Mapping from IS acknowledgeAlarms parameters to SS equivalents IS Operation parameter SS Method parameter Qualifier alarmInformationAndSeverityReferenceList AlarmIRPConstDefs:AlarmInformationIdAndSevSeq alarm_information_id_and_sev_list Note: perceivedSeverity is optional