Cached CurrentAlarms list cannot be updated based on AlarmEventNotifications

[openBackhaul]

The CurrentAlarmType datatype contains the key attribute currentAlarmIdentifier.

The currentAlarmIdentifier is not communicated within the AlarmEventNotification.

Without the currentAlarmIdentifier key attribute value the CurrentAlarms list inside the cache cannot be updated based on the received AlarmEventNotification. This includes, for example:

• New entries cannot be created without the key attribute.
• Entries to be cleared (based on problemSeverity==alarm-1-0:SEVERITY_AND_CLEARED_TYPE_CLEARED) cannot be identified as the value of the key attribute is unknown.

Potential Proposal: The currentAlarmIdentifier is added to the attributes comprised in the AlarmEventNotification.

[demx8as6]

Maybe I don't get the use case of the "cache" but alarm-type-id, alarm-type-qualifier and the resource identifies an alarm instance. The currentAlarmIdentifier does not transport any useful information and must not be used by applications.

[openBackhaul]

Decision during the 5G-xhaul call on 6th of September 2023: The CurrentAlarmType::currentAlarmIdentifier shall be deleted from the modelling. The

• CurrentAlarmType::alarmTypeId shall become partOfObjectKey=1
• CurrentAlarmType::alarmTypeQualifier shall become partOfObjectKey=2
• CurrentAlarmType::resource shall become partOfObjectKey=3