-
Notifications
You must be signed in to change notification settings - Fork 0
Deduplication
Deduplication is near-real-time stream suppression. It is not persistent storage and does not provide long-term replay history.
AISMixer applies deduplication to accepted NMEA output sentences after multipart completion and before outbound TAG construction. Duplicate state is kept in a TTL-based in-memory cache. The currently exposed configuration does not provide an operator-facing duration setting for that cache.
Legacy broadcast mode uses one global deduplication scope.
A repeated sentence is forwarded once to the broadcast output set during the active TTL window. Unnamed forwarders remain valid in legacy broadcast mode.
Routing mode uses one deduplication scope per target_id.
The same sentence may be delivered once to udp:aishub and once to udp:local_debug. Overlapping routes to the same target do not cause duplicate delivery to that target.
Matched target IDs come from the routing decision captured for the IngressEvent. Deduplication does not perform a new routing lookup.
Deduplication compares output sentence identity within the active in-memory cache. It does not compare geographic position semantically, decode vessels, detect spoofing, or provide long-term history.
See also Data Plane, Routing Model, Multipart NMEA Assembly, and Known Limitations.