Epic #2
Updated by Fernando Jose Capeletto Neto over 1 year ago
TrackHandler shall be able to consume NMEA messages published from Kafka Topic, decode those messages and create AIS Tracks according to each AIS message type.
Those tracks shall be persisted in the TrackHandler database.
TrackHandler shall publish TrackHandlerMessages to CMS through Kafka, informing the reception/decoding of those NMEA messages and about each AIS Track creation.
The following messages shall be published:
* One message to the SYSTEM_ALERT_TOPIC informing how many NMEA messages was received.
* One message to the SYSTEM_ALERT_TOPIC informing how many AIS Tracks was created.
* <N> messages to the SYSTEM_ALERT_TOPIC informing the MMSI and the AIS Message type processed.
* <N> messages to the AIS_TOPIC containing the attributes from each of <N> AIS Messages received.
When receiving an AIS Message about an already existing AIS Track in the CMS:
* In case of the same AIS Type message, the respective AIS Track attributes shall be updated.
* For a different AIS Type message, the attributes that already contain information from previous messages shall be updated, and the non-coincident attributes shall be added to the AIS Track structure. (Data-merge Capability)
* In this situation 2 messages shall be published to AIS_TOPIC :
** The original AIS Message received as described above, and
** One special AIS message (with a dedicated Type) representing the current composition from the different AIS Messages received for that AISTrack so far.