Broadcast Terminal Resource Prioritization for Emergency Alerts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing broadcast receiving terminals face delays in notifying users of Emergency Alert System (EAS) alerts due to potential blocking of resource contention handlers, even when forced tuning is required, which can disrupt the conventional framework for resource management.
Innovation Solution
A broadcast receiving terminal with a processor-based system that includes a program executioner, resource contention detector, determiner, and notifier, which prioritizes resource reservations to ensure prompt execution of forced tuning without blocking, even when a resource contention handler is registered by a privileged Java program.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a resource contention handler is registered by a privileged Java program to manage resource reservations, then resource management follows the conventional framework, but forced tuning for EAS alerts may be blocked and delayed
Solution Approach 1:
The system performs preliminary classification of programs into normal programs and forced tuning programs (such as EAS alerts). The forced tuning program is pre-designated with highest priority status, ensuring that when resource contention occurs, the forced tuning program can preempt resources immediately without being blocked by the conventional resource contention handler registration mechanism.
Solution Approach 2:
The resource management system is segmented into different priority levels. The patent divides program execution into normal execution (subject to resource contention handlers) and forced tuning execution (with highest priority). This segmentation allows the EAS alert system to operate in a separate priority tier that bypasses the conventional resource contention resolution mechanism.
2Speed
If the system prioritizes forced tuning execution for EAS alerts, then alert notification speed improves, but the conventional resource contention handler framework may be disrupted
Solution Approach 1:
The system implements dynamic priority adjustment based on program type. While the conventional resource contention handler framework remains intact for normal programs, the system dynamically assigns highest priority to forced tuning programs (EAS alerts) when they need to execute. This dynamic adjustment allows the framework to adapt to urgent situations without structural changes or disruptions to the conventional resource management architecture.
3Ease of operation
If resource contention handlers are invoked for all program reservations, then resource allocation follows established protocols, but emergency alerts experience unexpected blocking
Solution Approach 1:
The system applies different resource allocation qualities to different program types. Normal programs follow the conventional resource contention handler protocol, while forced tuning programs (EAS alerts) are granted special local quality of highest priority status. This means the resource allocation protocol is not uniformly applied but rather adapted locally based on the program's designated priority level, allowing emergency alerts to bypass blocking.
Data Source
AI summary
Under a resource manager, unexpected blocking is prevented without calling a handler for resolving a resource contention, by assigning a priority level depending on the program that has requested for a reservation of a resource as well as by assigning a special priority level which permits a reservation of a resource without any conditions in the case of a program which is urgently needed such as an EAS module.