Location Services Gateway Server Emergency Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless communication systems lack a centralized component for managed control over the delivery of mobile device location information to external systems, leading to inefficiencies in access control and privacy management.
Innovation Solution
The Location Services Gateway server (XLSG) directs location requests based on emergency status, data plan, device type, application type, and fallback mechanisms, acting as a proxy to manage access and privacy for location information, providing configurable access controls and integrating with Location Servers and Online Charging Systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a centralized location services gateway server is implemented to manage access control and privacy, then security and control over location information is improved, but system complexity increases
Solution Approach 1:
The Location Services Gateway Server (XLSG) is introduced as an intermediary component between location servers and external systems. It receives location requests, evaluates access control policies, and forwards requests to appropriate location servers. This mediator approach centralizes security management while maintaining system modularity, resolving the contradiction by adding a dedicated control layer without requiring fundamental architectural changes throughout the entire system.
2Productivity
If location requests are steered to different location servers based on multiple criteria (emergency status, data plan, device type), then access control efficiency is improved, but routing decision complexity increases
Solution Approach 1:
The system changes the parameters used for routing decisions based on the type of location request. For emergency requests, the gateway steers to location servers optimized for rapid response without strict access control. For non-emergency requests, it applies full access control policies. This parameter-based differentiation allows efficient routing while managing complexity by applying simple rules for simple cases and complex rules only when necessary.
Solution Approach 2:
Access control policies and routing rules are pre-configured and evaluated before location requests are processed. The gateway server maintains a database of access control decisions and routing preferences that are prepared in advance. This preliminary action allows rapid routing decisions during operation without requiring complex real-time calculations, improving productivity while keeping decision logic manageable.
3Speed
If emergency location requests are handled separately from non-emergency requests, then response time for emergency services is improved, but system processing complexity increases
Solution Approach 1:
The location request processing system is segmented into distinct handling paths based on emergency status. The gateway server identifies emergency requests through priority indicators and routes them to dedicated location servers with simplified processing logic. Non-emergency requests follow a separate processing path with full access control evaluation. This segmentation enables fast emergency response by eliminating unnecessary processing steps while containing complexity within isolated processing streams rather than requiring complete system complexity.
Data Source
AI summary
A method and apparatus for steering location requests to a serving one of a plurality of possible location positioning devices. A location request may be steered base on an emergency status of the location request, whether or not the subscriber device has a valid data plan established, based on the device type of the wireless device, or based on the type of application running on the wireless device. A location request may also be steered to a fallback location device if a steering to a primary selected location device fails and sufficient time remains to locate via the fallback location device.