Broadcast Rate Events for MAPs and SPATs that stop being broadcasted #87
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds the ability to detect broadcast rates of 0, for example for RSUs that go offline that had previously been broadcasting MAPs and SPATs.
The existing Broadcast Rate Topologies count events in a window based on stream time to detect high or low rates, but do not work when there are no events coming in.
This PR adds
MapZeroRateCheckerandSpatZeroRateCheckerprocessors to the MAP and SPaT validation topologies that work by storing the latest timestamp for eachRsuIntersectionKeyreceived, and using a wall-clock time triggered punctuator to emit aBroadcastRateEventfor any key whose last timestamp is older than the current time by more than the rolling window period (default 10 seconds). The events are emitted at the configured output interval, which defaults to every 5 seconds, and continue being sent as long as the zero-broadcast-rate condition persists.