Notifications explained
The notifications provided to you for events recognized in video streams or uploaded files are triggered in two different situations. The first group of notifications is sent directly after an event happens – these notifications are only triggered for the matching event. The second group of notifications is sent after information about the event has been stored in the database. The following figure displays the main types of notifications.
Writing the information about the recognized events in the database may take a different time, which can cause notifications to be published in a different order than the original sequence of recognized events. This may particularly apply for notifications about matching as these notifications aren't triggered when information is written into the database, but directly after the matching result is available.
Notifications topics
There are several types of notifications SmartFace Platform provides to you. These types are called topics. You can subscribe to topics listed in the following two tables.
Direct notifications
Notifications sent directly after the event happens:
|
Topic |
Trigger |
|
matchResults.match |
The detected face from the processed input was matched with a watchlist member. The match result isn't saved into the database yet. This notification contains also the result of the spoof check. |
|
matchResults.nomatch |
The detected face from the processed input wasn't matched with a watchlist member. The match result isn't saved into the database. |
Database notifications
Notifications sent when the event is stored in the database:
|
Topic |
Trigger |
|
faces.insert |
The detected face has been saved into the database. Some properties haven't been extracted yet. |
|
faces.extracted |
Face properties (such as age, gender and presence of a face mask) were extracted and updated in the database. |
|
matchResults.match.insert |
The detected face from the processed input was matched with a watchlist member and this information has been saved into the database. |
|
tracklets.completed |
The tracked face or pedestrian has been lost from tracking and this information has been updated in the database. |
|
heartbeat |
The notification is triggered automatically every second and contains a time stamp (current UTC). The notification can be used as an indication that communication is online. |
|
videoRecords.update |
The notification is used when SmartFace Platform is processing uploaded video files. The state of the video file is changed. State: Ready = 0, // Processing did not start yet Processing = 1, // VideoRecord is processing Processed = 2, // VideoRecord was successfully processed Error = 3 // Processing error occurred |
|
grouping_progress.info |
Frames uploaded to RecordGrouping are being processed. ProgressStatus: // RecordGrouping contains some unprocessed framers. Processing = 1, // All frames in RecordGrouping were processed. Ready = 2 |
|
pedestrians.insert |
The detected pedestrian was saved into the database. |
ZeroMQ messaging
SmartFace Platform is currently using ZeroMQ messaging library for the notification API. ZeroMQ uses sockets for communication, thus the host and a port needs to be specified. SmartFace Platform uses by default TCP port 2406.
If you want to listen to notifications from a different machine, please make sure that the port used on the host machine is not blocked by the firewall or is not used by any other software.