Cross-Carrier Device Identification via Shared Registry
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Multiple carrier networks face challenges in identifying application devices (e.g., A2P and M2M devices) that transmit messages across different networks, leading to difficulties in applying appropriate policies, such as spam filtering, due to the lack of device identification and policy implementation across network boundaries.
Innovation Solution
Implementing a shared registry system between sending and receiving carrier networks, where an access platform server assigns a device identifier to application devices, and a shared directory server stores this information along with associated policies, enabling network message processing entities to query and apply policies during message transmission.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If carrier networks use traditional isolated identification methods, then each network maintains its own security policies, but receiving networks cannot identify devices from sending networks
Solution Approach 1:
The patent implements a universal device identifier (MDN) that functions across multiple carrier networks, allowing a single identifier to serve identification purposes in both home and visited networks. The shared registry system provides multi-functional service by storing device information accessible to all participating networks, eliminating the need for network-specific identification mechanisms.
Solution Approach 2:
The patent introduces a shared registry system as an intermediary between carrier networks, which stores and manages device identifier mappings. This intermediary enables receiving networks to resolve foreign device identifiers without direct access to sending network systems, facilitating cross-network identification while maintaining network independence.
2Adaptability or versatility
If carrier networks implement shared device identification, then receiving networks can identify application devices and apply policies, but network security and privacy risks increase
Solution Approach 1:
The patent implements location-aware policy application where the receiving network applies policies specific to its local security requirements while respecting the device's home network identifiers. The system tailors policy enforcement to the local network context rather than applying uniform policies across all networks, allowing customized security measures at each network boundary.
Solution Approach 2:
The patent performs preliminary device identification and policy determination at the point of message receipt, before messages are routed or processed further. By identifying the application device early in the message flow and applying relevant policies upfront, the system prevents unauthorized messages from propagating through the network, reducing security risks before they can affect other networks.
3Measurement precision
If carrier networks query shared registry for device identification, then accurate device identification is achieved, but message transmission latency increases
Solution Approach 1:
The patent performs device identifier resolution in advance during message routing setup, before the actual message content is transmitted. By resolving the foreign device identifier to the home network identifier upfront, the system avoids repeated registry queries during message processing, reducing latency for subsequent message handling while maintaining accurate identification.
Data Source
AI summary
A first server device, associated with a first carrier network, may provide a first identifier of a first application device to a second server device to cause the second server device to store the first identifier. The second server device may be accessible from the first carrier network and from a different second carrier network. The first server device may receive a first message from the first application device; transmit the first message and the first identifier of the first application device towards a client device via the first carrier network and the second carrier network; receive, from a second application device associated with the second carrier network, a second message; identify the second application device based on information, maintained by the second server, associating the second application device with the second identifier; identify a set of policies based on the second identifier; and apply the set of policies.