M2M Device Triggering via SIP URI Translation Proxy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M communication in cellular networks faces challenges such as the inefficiency of using E.164 MSISDN for addressing M2M devices, which does not scale with the growing number of devices, and the overhead of signaling in mobile systems, as well as dependencies between PLMN and external M2M applications, leading to delayed response times and resource constraints.
Innovation Solution
The implementation of Session Initiation Protocol (SIP) and Uniform Resource Identifiers (URIs) to replace E.164 MSISDN for identifying M2M devices, decoupling PLMN identities from M2M applications, and using a combined SIP server and mapping function at the border between the Packet Data Network and the PLMN to translate SIP URIs to PLMN internal information, optimizing registration procedures and enabling direct communication through SIP signaling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If E.164 MSISDN is used for addressing M2M devices, then device identification is possible, but the system does not scale for large numbers of devices and identities will be exhausted
Solution Approach 1:
The patent changes the addressing parameter from E.164 MSISDN (telephony-based) to SIP URI (internet-based). This parameter change enables scalable addressing for billions of M2M devices by using a different identifier space that is not limited by telephony number allocations. The SIP URI format (sip:user@domain) provides a flexible, hierarchical naming structure that can accommodate massive numbers of devices without exhausting available identifiers.
2Reliability
If SMS-based communication is used for M2M devices, then device addressing is possible, but delay and response time requirements cannot be met
Solution Approach 1:
The patent replaces the SMS-based communication mechanism with SIP-based signaling. SMS operates through store-and-forward centers (SMSC) which introduce delays, while SIP uses real-time session initiation protocol designed for immediate communication establishment. This substitution enables M2M applications to meet strict delay and response time requirements by using a communication protocol optimized for real-time interaction rather than asynchronous message delivery.
3Ease of manufacture
If PLMN specific identifiers are used in M2M applications outside the PLMN, then device identification works within the network, but dependencies are created and development is slowed
Solution Approach 1:
The patent makes SIP URI a universal addressing mechanism that works both within PLMN and outside PLMN boundaries. Instead of using PLMN-specific identifiers that create domain dependencies, the SIP URI provides a domain-independent addressing scheme that can be used universally. This eliminates the need for separate PLMN-specific implementation considerations and enables M2M applications to develop once and deploy anywhere without PLMN-specific constraints.
4Productivity
If traditional attach and bearer procedures are used for M2M devices, then connection establishment is possible, but large amounts of signaling overhead occur
Solution Approach 1:
The patent enables M2M devices to perform partial attachment procedures or use simplified bearer establishment through SIP-triggered mechanisms. Instead of requiring full attach and bearer activation for every M2M communication, the SIP-based triggering allows devices to establish minimal connections only when needed, performing just enough attachment procedures to enable the specific M2M communication task. This reduces signaling overhead by avoiding excessive or unnecessary attachment steps.
Data Source
AI summary
A machine-to-machine communication proxy node is presented herein. The proxy node may be used as a translation device in machine-to-machine communications. For example, if an application server in a packet based network initiates communication with device in a mobile network, the proxy node may be utilized to translate application domain specific device identities coded in the format of Session Initiation Protocol (SIP) and Uniform Resource Identifier's (URI's) to mobile specific identities such as IMSI and establish communication connection in the mobile network. This identifying of mobile devices may be utilized to replace the commonly used E.164 Mobile Subscriber Integrated Services Digital Network (MSISDN) numbers for identifying mobile devices.


