E911 Call Trigger via Ut Interface for PSAP Callbacks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing systems fail to ensure callbacks from Public Safety Access Points (PSAPs) to user devices can be completed despite call restrictions, such as parental controls or 'do not disturb' settings, which can block essential emergency communications.
Innovation Solution
A method and system that use the Ut interface to generate a trigger to suspend call restrictions on user devices, allowing callbacks from PSAPs by transmitting a request through an XCAP message to a server, enabling temporary suspension of restrictions during emergency calls and logging the user device for subsequent callbacks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If call restrictions are implemented on user devices, then parental controls and do not disturb functionality are improved, but emergency callback communication from PSAP is blocked
Solution Approach 1:
The system performs preliminary action by proactively suspending call restrictions before the emergency callback is attempted. When an emergency call is detected, the network node sends a suspension trigger to the user device to disable restrictions in advance, ensuring the callback pathway is clear before it is needed.
Solution Approach 2:
The network node acts as an intermediary between the PSAP and the user device. It receives the suspension trigger from the PSAP, processes the restriction suspension request, and communicates with the user device to implement the suspension, thereby mediating the conflict between restrictions and emergency communication.
2Reliability
If call restrictions are suspended to allow PSAP callbacks, then emergency communication reliability is improved, but user device restriction settings are compromised
Solution Approach 1:
The call restriction settings are made dynamic rather than static. The system automatically adjusts the restriction state based on emergency conditions - suspending them during emergency calls and automatically restoring them afterward. This dynamic behavior allows the system to adapt to different operational contexts without permanent user intervention.
Solution Approach 2:
The system changes the parameter state of call restrictions from enabled to suspended temporarily during emergency communication. This parameter change is time-bound and condition-specific, allowing emergency callbacks while maintaining the original restriction parameters for normal operation. The automatic restoration after emergency calls ensures parameters return to their original state.
3Device complexity
If standard callback procedures are used, then system simplicity is maintained, but callbacks are blocked by existing call restrictions
Solution Approach 1:
The restriction suspension functionality is extracted as a separate, independent mechanism from the standard callback procedure. The network node handles restriction suspension as a distinct action triggered by emergency detection, separate from the normal callback routing and connection establishment processes.
Solution Approach 2:
The network node is given multi-functionality by integrating both the emergency detection capability and the restriction suspension control in a single component. This universal node handles both identifying emergency calls and managing the restriction state, eliminating the need for separate complex systems for each function.
Data Source
AI summary
A method includes initiating an emergency call, responsive to the initiating step, generating a trigger, wherein the trigger comprises a request to suspend a call restriction associated with a user device, and transmitting the trigger using a Ut interface to a server to suspend the call restriction.