Modem Cache Clearing for Wireless Emergency Alert Duplication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Wireless Emergency Alert (WEA) systems face issues where users may miss alerts due to duplication checking by the modem subsystem, which prevents rebroadcasts from being forwarded to the WEA messaging client if user settings or location changes occur after the initial message is cached, leading to incomplete or delayed alert presentation.
Innovation Solution
The WEA messaging client is configured to detect changes in user settings and device location, instructing the modem subsystem to clear its cache, thereby resetting duplication checking and ensuring that new alerts are presented based on current settings and conditions, allowing appropriate alerts to be displayed even if the user has opted in later or moved into a relevant geographic area.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the modem subsystem performs duplication checking by caching message identifiers, then duplicate alerts are filtered out, but legitimate rebroadcasts are incorrectly blocked when user settings or location changes occur
Solution Approach 1:
The system performs preliminary duplication checking by caching message identifiers in the modem subsystem. This preliminary filter operates before alerts reach the WEA messaging client, efficiently blocking duplicates while allowing the system to adapt when change indicators are detected, at which point the cache is cleared to permit legitimate rebroadcasts.
2Productivity
If the modem subsystem caches all received message identifiers for duplication checking, then processing speed increases, but memory usage increases
Solution Approach 1:
The system applies different quality characteristics to different parts of the alert processing system. The modem subsystem maintains a localized cache of message identifiers for rapid duplication detection, while the WEA messaging client handles more complex processing. This localized caching provides fast processing without requiring the entire system to maintain large memory buffers.
Solution Approach 2:
The system dynamically changes the state of the message identifier cache based on detected parameters. When change indicators are detected (user settings changes, location changes, or client requests), the cache parameter is reset to clear stored identifiers. This allows the system to optimize between memory usage and alert delivery accuracy by clearing the cache only when necessary.
3Reliability
If the system clears the message identifier cache frequently to ensure all alerts are delivered, then alert completeness improves, but duplication checking effectiveness decreases
Solution Approach 1:
The WEA messaging client provides feedback to the modem subsystem about its processing needs. When the client detects that it may have missed alerts or needs to reprocess messages (through change indicators or explicit requests), it sends a request to clear the cache. This feedback mechanism ensures alert completeness while maintaining duplication filtering efficiency during normal operation.
Data Source
AI summary
Cellular communication networks may be configured to broadcast wireless emergency alert (WEA) messages to multiple receiving communication devices. A communication device has physical-layer components, such as a modem subsystem, that receive broadcast alert messages. The modem subsystem uses a cache to record received alert messages and references the cache to perform duplication checking for newly received messages. Newly received messages that are not duplicates are provided to application-layer software for further processing. The application-layer software notifies a device user of the alert message if the alert message satisfies certain criteria. In addition, the application-layer detects changes in device properties that could potentially affect the criteria and in response causes the cache of the modem subsystem to be cleared so that the modem subsystem will not declare a subsequently received alert message to be a duplicate.