CMS » TrackHandler

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 were received.
• One message to the SYSTEM_ALERT_TOPIC informing how many AIS Tracks were created.
• <N> messages to the SYSTEM_ALERT_TOPIC informing the MMSI and the AIS Message type processed.
• <N> messages to the AISMESSAGE_TOPIC containing the attributes from each of <N> AIS Messages received.

When receiving an AIS Message for a given AISTrack, two situations can occur:

• A new one will be created if the AISTrack has not existed.
• If the AISTrack already were in the system, for each AISTrack message received, the respective AIS Track attributes contained in that message will be updated. (The message type attribute will represent, therefore, the type of the last AIS message received for that AISTrack)

• When an AISTrack is created (or receives an update), a message will be published to AISMESSAGE_TOPIC containing a pair of :
  • The updated AISTrack representing the current composition (data-merged) from the different AIS Messages received for that AISTrack so far.
  • A list of all AISTrackMessages received for that AISTrack.

Epic Branch
https://gitlab.com/fernando.engineer/cms/TrackHandler/-/tree/20230328_systemalerttopic_aismessages