User's Manual

ASYNCHRONOUS NOTIFICATION - CAEN UHF RFID Readers Communication Protocol 26
3 ASYNCHRONOUS NOTIFICATION
The notification channels are implemented only with sockets.
All the messages notifications are composed by a header and a body. In all cases the body of the message is a list of
attribute-value pairs. The first AVP of the body is fixed and called NotifyMessage.
All the packets for notification channel share the same header format of other packet as described at § 3.
The first AVP (NotifyMessage) is followed by a list of AVPs, the number of which depends on how many tags should be
notified. Each AVP has the same format of the AVP described in § 3.
The NotifyMessage has the following fixed format:
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-------------------------------+------------------------------+
| RESERVED | 8 |
+-------------------------------+------------------------------+
| CommandName | ReportBuffer |
+-------------------------------+------------------------------+
After the NotifyMessage AVP we can receive:
a) a list of AVPs (as described in table 3) followed by an AVP with ‘Attribute Type’ ResultCode
b) a single AVP called KillMessage with the following fixed format:
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-------------------------------+------------------------------+
| RESERVED | 8 |
+-------------------------------+------------------------------+
| KillCommand | KillCommand |
+-------------------------------+------------------------------+
Description
TimeStamp: the timestamp of the notification
TagIDLen: the ID length of the tag.
TagID: the ID of the tag.
SourceName: the name of the source to use.
EventType: the type of the notified event
Tab. 3.3.1: Attribute types: Notification AVP List