Message Routing Platform for IoT Devices with Non-Routable Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of IoT devices exceeds the capacity of current unique identifier assignment systems, leading to inefficiencies and resource wastage due to the need for multiple identifiers per device, making it difficult to route messages effectively.
Innovation Solution
A message routing platform translates non-routable identifiers to mapped device addresses, allowing for scalable machine-to-machine message delivery by verifying authorization and using active profiles to route messages through the telecommunications network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional unique identifier assignment systems are used for IoT devices, then message routing is straightforward with standard identifiers, but the system cannot scale to billions or trillions of IoT devices due to identifier exhaustion
Solution Approach 1:
The patent introduces a message routing platform as an intermediary between message senders and IoT devices. This platform uses non-routable identifiers (such as EUI-64 addresses or other standardized device identifiers) that do not require traditional telecommunication numbering resources. The platform translates these non-routable identifiers into routable addresses or routes messages through alternative paths, enabling message delivery without consuming limited MSISDN/IMSI resources while supporting massive device scales.
Solution Approach 2:
The patent changes the parameter space for device identification by moving from traditional telecommunication identifiers (MSISDN, IMSI with 15-digit limits) to alternative identifier systems such as EUI-64 addresses (64-bit identifiers) or other standardized device identifiers. This parameter change allows for 2^64 possible identifiers, providing sufficient address space for billions or trillions of devices while enabling new routing mechanisms that don't rely on conventional telecommunication numbering plans.
2Ease of manufacture
If multiple unique identifiers are assigned to each IoT device for activation and service profile download, then device provisioning is enabled, but identifier resources are wasted as the first identifier is used only once
Solution Approach 1:
The patent enables devices to use their own non-routable identifiers (such as EUI-64 addresses embedded in hardware) for message routing and communication. These identifiers are inherently available on the device without requiring separate provisioning steps. The message routing platform leverages these self-contained device identifiers directly, eliminating the need for separate activation identifiers and service profile download identifiers, thereby preventing resource wastage while maintaining provisioning capabilities.
3Productivity
If non-routable identifiers are used for message routing, then resource efficiency improves and scalability increases, but message delivery requires additional translation and routing infrastructure
Solution Approach 1:
The message routing platform is designed to handle multiple functions: receiving messages from various sources, translating non-routable identifiers to routable addresses, routing messages through appropriate networks, and delivering messages to target devices. By consolidating these diverse functions into a single universal platform, the system manages the complexity of identifier translation and routing infrastructure efficiently, enabling resource-efficient message routing at scale without requiring separate specialized systems for each function.
Data Source
AI summary
The disclosed system provides for machine-to-machine routing of messages (e.g., text messages, binary information, etc.) between devices (e.g., external applications, IoT devices, etc.) using non-routable identifiers. The systems and methods publish an application programming interface (API) configured to receive (non-routable) identification information of a target device from an external application (e.g., an IoT Service Provider) that calls the API, determines whether a target device associated with the identification information is a subscriber of a telecommunications service provider that provides telecommunications plans to subscribers of the telecommunications service provider, verifies that the external application is authorized to transmit messages to the target device, and translates the non-routable identification information to a mapped device address that can be used to determine a location of the target device so that the message can be delivered to the target device.