Anonymous Call Session Routing With Callback Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In emergency communication scenarios, telecommunication systems struggle to identify and maintain contact with anonymous devices, such as roaming devices or those unable to register with the IMS, leading to disconnection issues and inability to reach the device when needed.
Innovation Solution
A server in the telecommunication network, such as a Proxy Call Session Control Function (PCSCF), uses a REST interface to request and append device information, like MSISDN or IMSI, to a communication session setup process, ensuring the anonymous device's contact information is included and available for subsequent communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the host telecommunication service provider configures communication as an anonymous call for roaming devices, then the device can be connected to emergency services, but the emergency service provider cannot reach the device if the call is disconnected
Solution Approach 1:
The server retrieves device information (MSISDN, IMSI) from the home telecommunication service provider before establishing the emergency call session. This preliminary retrieval ensures that contact information is available in the system even though the device appears anonymous during the call setup process.
Solution Approach 2:
The server acts as an intermediary between the host telecommunication service provider and the emergency service provider. It receives the anonymous call request, retrieves the actual device information through a REST interface from the home provider, and forwards the call with embedded contact information to the emergency service provider, thus mediating the information flow.
2Reliability
If the server requests and appends device information to the communication session setup, then reliable communication is enabled, but additional network interface and processing requirements are introduced
Solution Approach 1:
The server is designed with multi-functionality, serving both as a call session control function and as an information retrieval intermediary. It handles both anonymous and non-anonymous calls, and can optionally retrieve device information when needed, making the system adaptable without requiring separate dedicated components.
Solution Approach 2:
The REST interface acts as a standardized intermediary layer between different telecommunication service providers. This standardized interface simplifies the integration complexity by providing a uniform method for retrieving device information, regardless of the specific home provider's internal systems.
Data Source
AI summary
Techniques for determining contact information for an anonymous device on a telecommunications network are described herein. The telecommunications network can implement a server to determine data representing a callback number or other subscriber information for a user equipment (UE) associated with an anonymous status. The server can generate a request for the data based on identifying an anonymous status associated with a message from the UE. The server can request the data from a gateway mobile location center (GMLC) of the telecommunications network using a Representational State Transfer (REST) interface. The server can establish a communication session for the UE by sending the callback number and/or the subscriber information to an emergency service center (e.g., to enable a Public Service Answering Point to communicate with the UE if the communication session is lost).