ETSI TS 132 111-6 V16.0.0 (2020-08)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Fault Management; Part 6: Alarm Integration Reference Point (IRP): Solution Set (SS) definitions (3GPP TS 32.111-6 version 16.0.0 Release 16)

RTS/TSGS-0532111-6vg00

General Information

• Status: Not Published
• Technical Committee: 3GPP SA 5 - Telecom Management
• Current Stage: 12 - Completion
• Completion Date: 13-Aug-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
Telecommunication management;
Fault Management;
Part 6: Alarm Integration Reference Point (IRP):
Solution Set (SS) definitions
(3GPP TS 32.111-6 version 16.0.0 Release 16)

3GPP TS 32.111-6 version 16.0.0 Release 16 1 ETSI TS 132 111-6 V16.0.0 (2020-08)

Reference
RTS/TSGS-0532111-6vg00
Keywords
GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners. ®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 2 ETSI TS 132 111-6 V16.0.0 (2020-08)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables 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 (https://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 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
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. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 3 ETSI TS 132 111-6 V16.0.0 (2020-08)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 7
4 Solution Set Definitions . 7
Annex A (normative): CORBA Solution Set . 8
A.0 General . 8
A.1 Architectural Features . 8
A.1.0 Introduction . 8
A.1.1 Syntax for Distinguished Names . 8
A.1.2 Notification Services . 8
A.1.3 Push and Pull Style . 8
A.1.4 Support multiple notifications in one push operation . 8
A.1.5 AlarmIRPNotifications Interface . 8
A.1.5.1 Method push (M) . 9
A.1.6 Filter . 9
A.2 Mapping . 10
A.2.1 Operation and Notification mapping . 10
A.2.2 Operation parameter mapping . 11
A.2.3 Notification parameter mapping . 20
A.3 Solution Set definitions . 32
A.3.1 IDL definition structure . 32
A.3.2 IDL specification "AlarmIRPConstDefs.idl" . 32
A.3.3 IDL specification “AlarmIRPSystem.idl” . 39
A.3.4 IDL specification "AlarmIRPNotifications.idl" . 42
Annex B (normative): XML Definitions . 49
B.0 General . 49
B.1 Architectural Features . 49
B.1.0 Introduction . 49
B.1.1 Syntax for Distinguished Names . 49
B.1.2 Notification Services . 49
B.1.3 IOC Definitions . 49
B.2 Mapping . 49
B.3 Solution Set definitions . 49
B.3.1 XML definition structure . 49
B.3.2 Graphical Representation . 50
B.3.3 XML Schema “alarmIRPNotif.xsd” . 55
B.3.4 XML Schema “alarmIRPIOCs.xsd” . 59
Annex C (normative): SOAP Solution Set . 66
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 4 ETSI TS 132 111-6 V16.0.0 (2020-08)
C.0 General . 66
C.1 Architectural features . 66
C.1.0 Introduction . 66
C.1.1 Syntax for Distinguished Names . 66
C.1.2 Notification Services . 66
C.1.3 Supported W3C specifications . 66
C.1.4 Prefixes and namespaces . 66
C.2 Mapping . 67
C.2.1 Operation and notification mapping . 67
C.2.2 Operation parameter mapping . 68
C.2.2.1 Operation acknowledgeAlarms . 68
C.2.2.1.1 Input parameters . 68
C.2.2.1.2 Output parameters . 68
C.2.2.1.3 Fault definition . 68
C.2.2.2 Operation getAlarmList . 68
C.2.2.2.1 Input parameters . 68
C.2.2.2.2 Output parameters . 69
C.2.2.2.3 Fault definition . 69
C.2.2.3 Operation getAlarmCount . 69
C.2.2.3.1 Input parameters . 69
C.2.2.3.2 Output parameters . 69
C.2.2.3.3 Fault definition . 70
C.2.2.4 Operation unacknowledgeAlarms . 70
C.2.2.4.1 Input parameters . 70
C.2.2.4.2 Output parameters . 70
C.2.2.4.3 Fault definition . 70
C.2.2.5 Operation setComment . 71
C.2.2.5.1 Input parameters . 71
C.2.2.5.2 Output parameters . 71
C.2.2.5.3 Fault definition . 71
C.2.2.6 Operation clearAlarms . 71
C.2.2.6.1 Input parameters . 71
C.2.2.6.2 Output parameters . 72
C.2.2.6.3 Fault definition . 72
C.3 Solution Set definitions . 73
C.3.1 WSDL definition structure . 73
C.3.2 Graphical Representation . 73
C.3.3 WSDL specification “AlarmIRPSystem.wsdl” . 74
Annex D (informative): Change history . 81
History . 82

ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 5 ETSI TS 132 111-6 V16.0.0 (2020-08)
Foreword
rd
This Technical Specification has been produced by the 3 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
rd
The present document is part of a TS-family covering the 3 Generation Partnership Project: Technical Specification
Group Services and System Aspects; Telecommunication management; as identified below:
32.111-1 "Fault Management; Part 1: 3G fault management requirements".
32.111-2 "Fault Management; Part 2: Alarm Integration Reference Point (IRP): Information Service (IS)".
32.111-6 "Fault Management; Alarm Integration Reference Point (IRP); Solution Set (SS) definitions".
The present document is part of a TS-family, which describes the requirements and information model necessary for
Telecommunications Management (TM). The TM principles and TM architecture are specified in 3GPP TS 32.101 [1]
and 3GPP TS 32.102 [2].
A communications system is composed of a multitude of Network Elements (NE) of various types and, typically,
different vendors, which inter-operate in a coordinated manner in order to satisfy the network users' communication
requirements.
The occurrence of faults in an NE may cause deterioration or loss of this NE's function. Fault Management is the
functional area, which allows the operator to detect the occurrence of faults in the network in real-time. Configuration
Management and Performance Management are two more functional areas, which require the operator to be alerted to
certain conditions in the network.
A standard general-purpose mechanism for the management of logs containing selected notifications from the network
is required to provide an ability to perform historical analysis on faults and conditions, which occurred in the network.
The TS 32.33x-series, constituting the Notification Log IRP, sets forth such a mechanism - and Annex B of the present
document contains the XML definition related to Alarm IRP notifications.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 6 ETSI TS 132 111-6 V16.0.0 (2020-08)
1 Scope
The present document contains the Solution Sets for the IRP whose semantics is specified in Alarm IRP: Information
Service (TS 32.111-2 [4]).
These Solution Set specifications are related to 3GPP TS 32.111-2 V14. 0.X [4].
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.111-1: "Telecommunication management; Fault Management; Part 1: 3G fault
management requirements".
[4] 3GPP TS 32.111-2: "Telecommunication management; Fault Management; Part 2: Alarm
Integration Reference Point: Information Service (IS)".
[5] 3GPP TS 32.150: "Telecommunication management; Integration Reference Point (IRP) Concept
and definitions".
[6] 3GPP TS 32.300: "Telecommunication management; Configuration Management (CM); Name
convention for Managed Objects".
[7] 3GPP TS 32.302: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Information Service (IS)".
[8] 3GPP TS 32.306: "Telecommunication management; Configuration Management (CM);
Notification Integration Reference Point (IRP): Solution Set (SS) definitions".
[9] 3GPP TS 32.311: "Telecommunication management; Generic Integration Reference Point (IRP)
management; Requirements".
[10] 3GPP TS 32.312: "Telecommunication management; Generic Integration Reference Point (IRP)
management; Information Service (IS)".
[11] 3GPP TS 32.316: "Telecommunication management; Generic Integration Reference Point (IRP)
management: Solution Set (SS) definitions".
[12] 3GPP TS 32.331: "Telecommunication management; Notification Log (NL) Integration Reference
Point (IRP): Requirements".
[13] 3GPP TS 32.336: "Telecommunication management; Notification Log (NL) Integration Reference
Point (IRP): Solution Set (SS) definitions".
[14] OMG TC Document telecom/98-11-01: "OMG Notification Service".
http://www.omg.org/technology/documents/
[15] OMG CORBA Services: "Common Object Services Specification, Update: November 22, 1996"
(Clause 4 contains the Event Service specification). http://www.omg.org/technology/documents/
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 7 ETSI TS 132 111-6 V16.0.0 (2020-08)
[16] W3C SOAP 1.1 specification (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/)
[17] W3C SOAP 1.2 specification (http://www.w3.org/TR/soap12-part1/)
[18] W3C WSDL 1.1 specification (http://www.w3.org/TR/2001/NOTE-wsdl-20010315)
[19] W3C XPath 1.0 specification (http://www.w3.org/TR/1999/REC-xpath-19991116)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2],
3GPP TS 32.111-1 [3], 3GPP TS 32.111-2 [4], 3GPP TS 32.150 [5] and 3GPP TS 32.331 [12] apply.
IRP document version number string
The IRP document version number (sometimes called “IRP version” or “version number”) string is used to identify
the present document. The definition of “IRP document version number string” in 3GPP TS 32.311 [9] 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 supports 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.
3.2 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
IS Information Service
MOC Managed Object Class
MOI Managed Object Instance
NE Network Element
NL Notification Log
OMG Object Management Group
SS Solution Set
TMN Telecommunications Management Network
UML Unified Modelling Language
WSDL Web Service Description Language
XML eXtensible Markup Language
4 Solution Set Definitions
This specification defines the following 3GPP Alarm IRP Solution Set Definitions:
Annex A provides the CORBA Solution Set.
Annex B provides the XML Definitions.
Annex C provides the SOAP Solution Set.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 8 ETSI TS 132 111-6 V16.0.0 (2020-08)
Annex A (normative):
CORBA Solution Set
A.0 General
This annex contains the CORBA Solution Set for the IRP whose semantics is specified in Alarm IRP: Information
Service (TS 32.111-2 [4]).
A.1 Architectural Features
A.1.0 Introduction
The overall architectural feature of Alarm IRP is specified in 3G TS 32.111-2 [4]. This clause specifies features that are
specific to the CORBA SS.
A.1.1 Syntax for Distinguished Names
The syntax of a Distinguished Name is defined in 3GPP TS 32.300 [6].
A.1.2 Notification Services
In implementations of CORBA SS, IRPAgent conveys Alarm Information to IRPManager via OMG Notification
Service (OMG Notification Service [14]).
OMG Event Service [15] provides event routing and distribution 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 [4].
A.1.3 Push 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 them.
This CORBA SS specifies that support of Push style is Mandatory (M) and that support of Pull style is Optional (O).
A.1.4 Support multiple notifications in one push operation
For efficiency reasons, IRPAgent may send multiple notifications using one single push operation. To pack multiple
notifications 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. On 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.
A.1.5 AlarmIRPNotifications Interface
OMG CORBA Notification push operation is used to realise the notification of AlarmIRPNotifications. All the
notifications in this interface are implemented using this push_structured_event method.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 9 ETSI TS 132 111-6 V16.0.0 (2020-08)
A.1.5.1 Method push (M)
module CosNotifyComm {
…
Interface SequencePushConsumer : NotifyPublish {
void push_structured_events(
in CosNotification::EventBatch notifications)
raises( CosEventComm::Disconnected);
…
}; // SequencePushConsumer
…
}; // CosNotifyComm
NOTE 1: The push_structured_events method takes an input parameter of type EventBatch as defined
in the OMG CosNotification module (OMG Notification Service [14]). This data type is the same
as a sequence of Structured Events. Upon invocation, this parameter will contain a sequence of Structured
Events being delivered to IRPManager by IRPAgent to which it is connected.
NOTE 2: The maximum number of events that will be transmitted within a single invocation of this operation is
controlled by IRPAgent wide configuration parameter.
NOTE 3: The amount of time the supplier (IRPAgent) of a sequence of Structured Events will accumulate
individual events into the sequence before invoking this operation is controlled by IRPAgent wide
configuration parameter as well.
NOTE 4: IRPAgent may push EventBatch with only one Structured Event.
A.1.6 Filter
IRPAgent shall optionally support alarm filtering based on IRPManager’s supplied alarm filter constraints (e.g. as
parameter in subscribe() of 3G TS 32.302 [7]. 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 subscription.
- 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.
- 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 filter constraint grammar specified by reference OMG Notification Service [14]. The name of the
grammar is called "EXTENDED_TCL". See clause 2.4, Default Filter Constraint Language in OMG Notification Service
[14]. This SS shall use this grammar only.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 10 ETSI TS 132 111-6 V16.0.0 (2020-08)
A.2 Mapping
A.2.1 Operation and Notification mapping
Alarm IRP: IS 3G TS 32.111-2 [4] defines semantics of operation and notification visible across the Alarm IRP. Table
A.2.1.1 indicates mapping of these operations and notifications to their equivalents defined in this SS.
Table A.2.1.1: Mapping from IS Notification/Operation to SS equivalents
IS Operation/ notification 3G TS 32.111- SS Method Qualifier
2 [4]
acknowledgeAlarms acknowledge_alarms M
unacknowledgeAlarms unacknowledge_alarms O
getAlarmList get_alarm_list M
getIRPVersion (note) get_alarm_irp_versions M
getAlarmCount get_alarm_count O
setComment comment_alarms O
clearAlarms clear_alarms O
getOperationProfile (note) get_alarm_irp_operations_profile O
getNotificationProfile (note) get_alarm_irp_notification_profile O
notifyNewAlarm push_structured_event M
Note that OMG Notification Service OMG Notification Service [14]
defines this method.
See clause A.3.1
notifyClearedAlarm push_structured_event M
See clause A.3.1
notifyChangedAlarm push_structured_event M
See clause A.3.1
notifyChangedAlarmGeneral push_structured_event O
See clause A.3.1
notifyAckStateChanged push_structured_event M
See clause A.3.1
notifyAlarmListRebuilt push_structured_event M
See clause A.3.1
notifyComments push_structured_event O
See clause A.3.1
notifyPotentialFaultyAlarmList push_structured_event O
See clause A.3.1
notifyCorrelatedNotificationChanged push_structured_event O
See clause A.3.1
NOTE: This operation is of ManagedGenericIRP IOC specified in [10]. The AlarmIRP IOC of [4] inherits from it.

ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 11 ETSI TS 132 111-6 V16.0.0 (2020-08)
A.2.2 Operation parameter mapping
Reference 3G TS 32.111-2 [4] 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 A.2.2.1: Mapping from IS acknowledgeAlarms parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
alarmInformationAndSeverityReferenceList AlarmIRPConstDefs::AlarmInformationIdAndSevSeq M
alarm_information_id_and_sev_list
Note: perceivedSeverity is optional
{ alarmId - Mandatory;
perceivedSeverity - Optional
}
ackUserId string ack_user_id M
ackSystemId ManagedGenericIRPConstDefs::StringOpt ack_system_id O
badAlarmInformationReferenceList AlarmIRPConstDefs::BadAcknowledgeAlarmInfoSeq M
bad_ack_alarm_info_list
status ManagedGenericIRPConstDefs::Signal M
Exceptions:
AcknowledgeAlarms,
ManagedGenericIRPSystem::ParameterNotSupported,
ManagedGenericIRPSystem::InvalidParameter

Table A.2.2.2: Mapping from IS unacknowledgeAlarms parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
alarmInformationReferenceList AlarmIRPConstDefs::AlarmInformationIdSeq alarm_information_id_list M
ackUserId string ack_user_id M
ackSystemId ManagedGenericIRPConstDefs::StringOpt ack_system_id O
badAlarmInformationReferenceList AlarmIRPConstDefs:: BadAlarmInformationIdSeq M
bad_alarm_information_id_list
status ManagedGenericIRPConstDefs::Signal M
Exceptions:
UnacknowledgeAlarms,
ManagedGenericIRPSystem::OperationNotSupported,
ManagedGenericIRPSystem::ParameterNotSupported,
ManagedGenericIRPSystem::InvalidParameter

Table A.2.2.3: Mapping from IS getAlarmList parameters to SS equivalents
IS Operation parameter SS Method parameter Qualifier
alarmAckState, filter ManagedGenericIRPConstDefs::StringOpt filter O
baseObjectClass, AlarmIRPConstDefs::DNOpt base_object O
baseObjectInstance (Note 1)
alarmInformation List Return value of type AlarmIRPConstDefs::AlarmInformationSeq (Note 2) M
status Exceptions: M
GetAlarmList,
FilterComplexityLimit,
ManagedGenericIRPSystem::ParameterNotSupported,
ManagedGenericIRPSystem::InvalidParameter
Note 1: If notification notifyAlarmListRebuilt supports indicating that only a part of the alarm list has been
rebuilt then this parameter shall be supported.

Note 2: Each Structured Event of AlarmIRPConstDefs::AlarmInformationSeq shall have the fields defined in
Table A.2.2.4 or Table A.2.2.5.

ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 12 ETSI TS 132 111-6 V16.0.0 (2020-08)
Table A.2.2.4: Definition of a Structured Event of AlarmIRPConstDefs::AlarmInformationSeq for
alarms not related to security
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 13 ETSI TS 132 111-6 V16.0.0 (2020-08)
IS Parameters OMG CORBA Qualifier Comment
Structured
Event attribute
There is no domain_name
corresponding IS
attribute.
notificationType type_name M The parameter carries
• - NOTIFY_FM_NEW_ALARM of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has not yet changed and has not yet been
cleared.
• - NOTIFY_FM_CHANGED_ALARM of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has changed but has not yet been cleared.
• - NOTIFY_FM_CHANGED_ALARM_GENERAL of
interface NotificationType of module AlarmIRPConstDefs
in case the alarm has changed but has not yet been
cleared.
• - NOTIFY_FM_CLEARED_ALARM of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has been cleared but not yet acknowledged.
alarmType See Table M See Table A.2.3.1
A.2.3.1
There is no variable Header
corresponding SS
attribute.
objectClass, See Table M See Table A.2.3.1
objectInstance A.2.3.1
notificationId See Table M See Table A.2.3.1
A.2.3.1
eventTime See Table O Value of NV pair is a IRPTime of module
A.2.3.1 ManagedGenericIRPConstDefs.

The parameter carries the
• alarmRaisedTime in case notificationType carries
NOTIFY_FM_NEW_ALARM
• alarmChangedTime in case notificationType carries
NOTIFY_FM_CHANGED_ALARM
• alarmChangedTime in case notificationType carries
NOTIFY_FM_CHANGED_ALARM_GENERAL
• alarmClearedTime in case notificationType carries
NOTIFY_FM_CLEARED_ALARM
systemDN See Table M See Table A.2.3.1
A.2.3.1
alarmId See Table M See Table A.2.3.1
A.2.3.1
alarmRaisedTime One NV pair of M Name of NV pair is the ALARM_RAISED_TIME of interface
filterable_ AttributeNameValue of module AlarmIRPConstDefs.
body_fields
Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
alarmChangedTime One NV pair of O Name of NV pair is the ALARM_CHANGED_TIME of interface
filterable_ AttributeNameValue of module AlarmIRPConstDefs.
body_fields
Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
alarmClearedTime One NV pair of M present if related alarm was cleared; not present if related alarm
filterable_ was not cleared
body_fields
Name of NV pair is the ALARM_CLEARED_TIME of interface
AttributeNameValue of module AlarmIRPConstDefs.

Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
probableCause See Table M See Table A.2.3.1
A.2.3.1
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 14 ETSI TS 132 111-6 V16.0.0 (2020-08)
IS Parameters OMG CORBA Qualifier Comment
Structured
Event attribute
perceivedSeverity See Table M See Table A.2.3.1
A.2.3.1
rootCauseIndicator See Table O See Table A.2.3.1
A.2.3.1
specificProblem See Table O See Table A.2.3.1
A.2.3.1
backedUpStatus See Table O See Table A.2.3.1
A.2.3.1
trendIndication See Table O See Table A.2.3.1
A.2.3.1
thresholdInfo See Table O See Table A.2.3.1
A.2.3.1
stateChangeDefinition See Table O See Table A.2.3.1
A.2.3.1
monitoredAttributes See Table O See Table A.2.3.1
A.2.3.1
proposedRepairActions See Table O See Table A.2.3.1
A.2.3.1
additionalText See Table O See Table A.2.3.1
A.2.3.1
additionalInformation See Table O See Table A.2.3.1
A.2.3.1
ackTime See Table M present if related alarm was acknowledged or unacknowledged;
A.2.3.3 not present if related alarm was not acknowledged or
unacknowledged
See Table A.2.3.3
ackUserId See Table M present if related alarm was acknowledged or unacknowledged;
A.2.3.3 not present if related alarm was not acknowledged or
unacknowledged
See Table A.2.3.3
ackSystemId See Table O optionally present if related alarm was acknowledged or
A.2.3.3 unacknowledged; not present if related alarm was not
acknowledged or unacknowledged

See Table A.2.3.3
ackState See Table M present if related alarm was acknowledged or unacknowledged;
A.2.3.3 not present if related alarm was not acknowledged or
unacknowledged
See Table A.2.3.3
clearUserId See Table O optionally present if related alarm was cleared; not present if
A.2.3.4 related alarm was not cleared

See Table A.2.3.4
clearSystemId See Table O optionally present if related alarm was cleared; not present if
A.2.3.4 related alarm was not cleared

See Table A.2.3.4
backUpObject See Table O See Table A.2.3.1
A.2.3.1
correlatedNotifications See Table O See Table A.2.3.1
A.2.3.1
comments See Table M present if related alarm was commented; not present if related
A.2.3.7 alarm was not commented

See Table A.2.3.7
There is no remaining_ body
corresponding IS
attribute.
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 15 ETSI TS 132 111-6 V16.0.0 (2020-08)
Table A.2.2.5: Definition of a Structured Event of AlarmIRPConstDefs::AlarmInformationSeq for
alarms related to security
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 16 ETSI TS 132 111-6 V16.0.0 (2020-08)
IS Parameters OMG CORBA Qualifier Comment
Structured
Event attribute
There is no domain_name
corresponding IS
attribute.
notificationType type_name M See Table A.2.3.1

The parameter carries
• NOTIFY_FM_NEW_ALARM of interface NotificationType
of module AlarmIRPConstDefs in case the alarm has not
yet changed and has not yet been cleared.
• NOTIFY_FM_CHANGED_ALARM of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has changed but has not yet been cleared.
• NOTIFY_FM_CHANGED_ALARM_GENERAL of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has changed but has not yet been cleared.
• NOTIFY_FM_CLEARED_ALARM of interface
NotificationType of module AlarmIRPConstDefs in case
the alarm has been cleared but not yet acknowledged.
alarmType See Table M See Table A.2.3.1
A.2.3.1
There is no variable Header
corresponding SS
attribute.
objectClass, See Table M See Table A.2.3.1
objectInstance A.2.3.1
notificationId See Table M See Table A.2.3.1
A.2.3.1
eventTime See Table O See Table A.2.3.1
A.2.3.1
The parameter carries the
• alarmRaisedTime in case notificationType carries
NOTIFY_FM_NEW_ALARM
• alarmChangedTime in case notificationType carries
NOTIFY_FM_CHANGED_ALARM
• alarmChangedTime in case notificationType carries
NOTIFY_FM_CHANGED_ALARM_GENERAL
• alarmClearedTime in case notificationType carries
NOTIFY_FM_CLEARED_ALARM
systemDN See Table M See Table A.2.3.1
A.2.3.1
alarmId See Table M See Table A.2.3.1
A.2.3.1
alarmRaisedTime One NV pair of M Name of NV pair is the ALARM_RAISED_TIME of interface
filterable_ AttributeNameValue of module AlarmIRPConstDefs.
body_fields
Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
alarmChangedTime One NV pair of O Name of NV pair is the ALARM_CHANGED_TIME of interface
filterable_ AttributeNameValue of module AlarmIRPConstDefs.
body_fields
Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
alarmClearedTime One NV pair of M present if related alarm was cleared; not present if related alarm
filterable_ was not cleared
body_fields
Name of NV pair is the ALARM_CLEARED_TIME of interface
AttributeNameValue of module AlarmIRPConstDefs.

Value of NV pair is a IRPTime of module
ManagedGenericIRPConstDefs.
probableCause See Table M See Table A.2.3.1
A.2.3.1
perceivedSeverity See Table M See Table A.2.3.1
A.2.3.1
ETSI
3GPP TS 32.111-6 version 16.0.0 Release 16 17 ETSI TS 132 111-6 V16.0.0 (2020-08)
IS Parameters OMG CORBA Qualifier Comment
Structured
Event attribute
rootCauseIndicator See Table O See Table A.2.3.1
A.2.3.1
specificProblem See Table O See Table A.2.3.1
A.2.3.1
additionalText See Table O See Table A.2.3.1
A.2.3.1
additionalInformation See Table O See Table A.2.3.1
A.2.3.1
ackTime See Table M present if related alarm was acknowledged or unacknowledged; not
A.2.3.3 present if related alarm was not acknowledged or unacknowledged

See Table A.2.3.3
ackUserId See Table M present if related alarm was acknowledged or unacknowledged; not
A.2.3.3 present if related alarm was not acknowledged or unacknowledged

See Table A.2.3.3
ackSystemId See Table O optionally present if related alarm was acknowledged or
A.2.3.3 unacknowledged; not present
...