MDN-less SMS Routing for M2M Telemetry via MSID Gateway
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M communication systems face challenges in supporting large-scale deployments due to the need for unique Mobile Directory Numbers (MDNs) for each device, which leads to finite numbering resource issues and regulatory complexities, making it impractical and costly to manage and allocate MDNs for millions of devices.
Innovation Solution
The system enables M2M communication through a mobile network using a Mobile Station Identifier (MSID) like MIN or IMSI instead of a valid telephone number for call routing, allowing data messages to be routed based on assigned identifiers without the need for MDNs, utilizing existing SMS infrastructure and leveraging short codes for addressing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a unique Mobile Directory Number (MDN) is assigned to each M2M device, then device identification and routing reliability is improved, but the finite numbering resources become insufficient and management complexity increases
Solution Approach 1:
The patent introduces a gateway as an intermediary component that translates between MDN-based routing and MSID-based device identification. The gateway receives messages routed to an MDN, resolves the MDN to the corresponding MSID through the HLR, and forwards the message to the correct M2M device. This intermediary layer allows the system to maintain reliable device identification without requiring unique MDNs for each device.
Solution Approach 2:
The patent segments the addressing function into two parts: MDN for routing purposes and MSID for device identification. By separating these functions, the system can use a limited set of MDNs for routing while maintaining a larger pool of MSIDs for device identification. The HLR maintains the mapping between MDNs and MSIDs, enabling this segmentation to work reliably.
2Adaptability or versatility
If MDNs are allocated to support large scale M2M deployments, then device coverage is improved, but regulatory compliance and allocation complexity worsen
Solution Approach 1:
The HLR acts as an intermediary that manages the mapping between MDNs and MSIDs. Instead of directly allocating and managing individual MDNs for each device, the system uses the HLR to resolve MDNs to MSIDs, simplifying the allocation management process while maintaining extensive device coverage.
3Speed
If SMS infrastructure is used for M2M communication, then real-time data transmission capability is improved, but the need for MDN-based routing creates resource constraints
Solution Approach 1:
The gateway serves as an intermediary that enables SMS-based M2M communication without consuming MDN resources. It receives SMS messages routed to an MDN, resolves the MDN to the corresponding MSID, and delivers the message to the appropriate M2M device. This allows the system to leverage the fast SMS infrastructure while avoiding the MDN resource constraints that would otherwise limit scalability.
Data Source
AI summary
Machine-to-Machine (M2M) communications, for various telemetry applications, such as meter reading, alarm applications or the like, utilize data communication service via a public mobile/wireless communication network, such as the short message service (SMS). However, such M2M communications may involve a large number of clients. To avoid the need to assign a telephone number, such as a mobile directory number (MDN) or the like, to each of the many remote M2M clients, routing through the network is based on another type of MSID (Mobile Station Identifier), such as the MIN (Mobile Identifier Number) or the IMSI (International Mobile Station Identifier) of the client. SMS messages transmissions originating at a client use a short code for the M2M application address, and SMS messages intended to terminate at a client use the MIN or IMSI as the routing address for the M2M device.