NGCS Emergency Call Rerouting for PSAP Failure Continuity
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing emergency call systems in NG911/NG112 environments fail to efficiently re-establish calls after PSAP failures without manual intervention, especially in catastrophic scenarios, and lack scalability and redundancy without requiring redundant systems that double the component count.
Innovation Solution
A method and system that dynamically reroutes emergency calls to a fallback PSAP using the Next Generation Core Services (NGCS) to identify and register with a fallback server, allowing seamless call continuation without manual steps, leveraging the ESInet architecture for scalability and redundancy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundancy is implemented inside the PSAP with redundant servers sharing call state, then call continuity is improved, but device complexity and cost increase due to requiring double the number of components
Solution Approach 1:
The patent introduces a fallback PSAP as an intermediary system that receives call state information from the failed PSAP and assumes its role. This mediator approach allows the primary PSAP to have a backup without requiring the backup to mirror all system state, thereby reducing complexity while maintaining reliability.
Solution Approach 2:
Instead of creating a full redundant copy of the PSAP system, the patent uses a simplified fallback PSAP that copies only the necessary call state information and assumes the role of the failed PSAP. This selective copying reduces the component count while maintaining essential functionality for call continuity.
2Reliability
If redundant servers share all call state to enable seamless failover, then call continuity is improved, but scalability is worsened as the approach cannot be extended to multiple PSAPs
Solution Approach 1:
The patent segments the PSAP functionality into independent units, where each PSAP can fail over to its own dedicated fallback PSAP. This segmentation allows the system to scale horizontally by adding more PSAPs without requiring a monolithic redundant system, as each PSAP-fallback pair operates independently.
Solution Approach 2:
The system dynamically assigns fallback PSAPs to primary PSAPs based on real-time failure detection. When a PSAP fails, the system dynamically routes its calls to the designated fallback PSAP. This dynamic behavior enables scalability across multiple PSAPs without requiring static pre-configured redundancy for all possible failure scenarios.
3Reliability
If the system is designed to handle 200% of maximum load to accommodate component failure, then reliability is improved, but cost increases due to requiring double the number of components
Solution Approach 1:
Instead of designing the fallback PSAP to handle all possible call loads (excessive action), the patent implements a partial action approach where the fallback PSAP handles only the calls that fail over from the primary PSAP. This partial capacity approach reduces the total component count while maintaining adequate reliability for failure scenarios.
Data Source
AI summary
A method and system for re-establishing a disconnected emergency call to an emergency call network for emergency call continuation in case of Public Safety Answering Point (PSAP) failure(s) can be utilized without the need of any manual steps taken by the caller and/or the call taker. Embodiments can be configured to detect a failure in the PSAP operating the emergency call by a Next Generation Core Services (NGCS), which thereupon will not release the emergency call to the failed PSAP but will send it to a dynamically identified fallback PSAP.