Content for TS 32.161 Word version: 18.0.0
D Example use cases p. 23
All these use cases have in common that one or more data nodes need to be identified. To these selected nodes a certain semantics is attached.
Notification subscription
1
Jex conditions allows to select notifications based on the values of notification parameters. Note that in a JSON document with the representation of a notification all notification parameters are on the top level just below the root node. The following example shows an alarm notification.
The following Jex expressions are examples for notification filters that can be applied to this notification. When the Jex expression evaluates to true, the notification is forwarded, otherwise it is discarded.
Subscribe to all alarm notifications of one specific "ManagedElement" instance below a specific "SubNetwork" instance. Note, for subscribing to alarm notifications the Jex expression identifies a set of managed objects.
2
Subscribe to all alarm notifications of all "ManagedElement" instances below a specific "SubNetwork".
3
Subscribe to all alarm notifications of the managed object tree whose root object is a specific "ManagedElement" instance.
4
Subscribe to all alarm notifications of all managed object trees whose root objects are "ManagedElement" instances below a specifc "SubNetwork" instance.
5
Subscribe to all alarm notifications of "ManagedElement" instances from vendor "Company XY" below a specific "SubNetwork" instance.
6
Subscribe to all alarm notifications of the object subtrees whose root objects are "ManagedElement" instances from vendor "Company XY".
7
Subscribe to attribute value change notifications of a specific attribute of a specific managed object.
8
Subscribe to attribute value change notifications of multiple specific attributes of a specific managed object.
Notification filtering
$ Change history p. 26
