Notifications
The following call flow explains the procedure followed in message notification.
Figure 2-29 Notifications Call Flow

Note:
Subscription with device have more priority than the subscription without device, if it is for the same topic. For information, refer to Figure 2-37Example 1
Two subscriptions have been created for the same SCSAS for the same External ID. The first subscription is created for the Tracking/Test/# topic and the second subscription is created for the Tracking/Test/Battery/# topic. Then, Device Published data to Tracking/Test/Battery/Level.
Figure 2-30 Tracking/Test/# for the Same SCSAS

Figure 2-31 Tracking/Test/Battery/# for the Same SCSAS

Figure 2-32 Tracking/Test/Battery/Level Topic for the Same SCSAS

Example 2
Two subscriptions have been created for two different SCSAS for the same External ID and same topic. Then, Device published data to the topic.
The following image displays the entry from table for a subscription created on the Tracking/Test/Battery/# topic:
Figure 2-33 Tracking/Test/Battery/# Topic

The following image displays the entry from table for a subscription created on the Tracking/Test/Battery/# topic for different SCSAS:
Figure 2-34 Tracking/Test/Battery/# Topic for the Different SCSAS

Figure 2-35 Subscription 1

Figure 2-36 Subscription 2

Example 3
Two subscriptions are created. One subscription is with topic for a device, and the other subscription is only for topic.
Figure 2-37 Tracking/Test/Battery Topic with Device

The following image displays the entry from table for a subscription created on the Tracking/Test/Battery/# topic without a device. Ensure that the deviceid is null.
Figure 2-38 Tracking/Test/Battery Topic without Device

The device publishes data to the topic. Notification is sent for the subscription with the device.
Figure 2-39 Subscription Notification
