Protocol Endpoints for Secure Cloud Emergency Call Latency Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Cloud-based solutions for emergency call handling face challenges in providing secure, real-time bidirectional digital communications between private networks and cloud applications without exposing the private networks to the public Internet, as existing solutions like VPNs introduce latency and call-affinity issues.
Innovation Solution
Implementing protocol endpoints that execute locally within private networks to perform transport-related operations of application-layer protocols, while cloud applications handle non-transport-related operations, enabling secure and efficient communication without the need for VPNs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If VPNs are used to connect cloud-based emergency call systems with private emergency services networks, then secure communication is achieved, but latency and call-affinity issues occur
Solution Approach 1:
The patent extracts the security function from the VPN infrastructure and implements it natively within the Private Network. Protocol endpoints are deployed inside the Private Network to handle SIP signaling and media streams directly, eliminating the need for VPN encapsulation and decryption/encryption cycles that cause latency. This allows secure communication without the time penalty of VPN processing.
Solution Approach 2:
The patent introduces protocol endpoints as intermediary components within the Private Network that facilitate direct communication between emergency services systems and cloud-based PSAPs. These endpoints act as local SIP proxies that manage call signaling and media routing without requiring external VPN tunnels, thereby maintaining security while minimizing latency through localized processing.
2Reliability
If VPNs are used to connect cloud-based emergency call systems with private emergency services networks, then secure communication is achieved, but call-affinity issues occur
Solution Approach 1:
The patent extracts call-affinity management from the VPN layer and implements it natively within the Private Network through protocol endpoints. These endpoints maintain local state information about active calls and can directly route subsequent media streams and signaling messages without VPN intervention, eliminating call-affinity issues while preserving secure communication through network segmentation and authentication mechanisms.
3Loss of time
If protocol endpoints are deployed locally within private networks, then latency and call-affinity issues are reduced, but device complexity increases
Solution Approach 1:
The patent designs protocol endpoints as multi-functional components that simultaneously handle SIP signaling, media stream routing, call-affinity management, and security authentication within the Private Network. By consolidating these functions into single endpoints rather than requiring separate systems for each function, the overall system complexity is managed while achieving low-latency communication.
Solution Approach 2:
The protocol endpoints are designed to autonomously manage call state information and routing decisions without requiring constant external control. They self-configure based on registered emergency services systems and automatically handle call-affinity requirements, reducing the operational complexity despite the added infrastructure.
4Productivity
If protocol endpoints are deployed locally within private networks, then real-time bidirectional communication is enabled, but ease of operation decreases
Solution Approach 1:
The protocol endpoints autonomously discover and register emergency services systems within the Private Network, automatically establishing call-affinity relationships and configuring routing rules. This self-configuration capability enables real-time bidirectional communication while minimizing the operational burden on system administrators, as the endpoints adapt to network changes without manual intervention.
Data Source
AI summary
Systems, devices, and methods described herein provide protocol endpoints that execute locally within private networks and perform a set of transport-related operations specified an application-layer protocol to which messages exchanged between local applications executing within private networks and cloud applications executing in cloud computing systems conform. However, systems, devices, and methods described herein also leverage computing resources of the cloud by having the cloud applications (rather than the protocol endpoints) perform a second set of operations specified by the application-layer protocol. By functioning in this manner, systems, devices, and methods described herein facilitate real-time bidirectional communication flow between local applications executing within private networks and cloud applications without exposing the private networks to the public Internet and without using a VPN (thereby avoiding the problematic overhead of a VPN) with respect to real-time communications.