Service Control Device for MTC IP Message Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The interworking between the M2M platform and the PLMN of 3GPP specifications faces challenges due to the complexity and cost of implementing SMS-based message reception, particularly with Network Address Translation (NAT) requiring additional functionalities like ICE, which are not suitable for compact and inexpensive MTC-UE devices.
Innovation Solution
A communication system that includes a gateway device for converting private to public IP addresses and a service control device that maps and retains public IP addresses with device identifiers, enabling IP packet processing to deliver messages from an IP-based application server to MTC user devices without relying on SMS or ICE, thereby simplifying the protocol stack and reducing costs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SMS is used to receive incoming messages from AS to MTC-UE, then message reception is enabled, but implementation cost and protocol complexity increase
Solution Approach 1:
The patent extracts the SMS protocol handling from the MTC-UE device by introducing a gateway device that performs SMS-to-IP message conversion. The gateway device contains an SMS message receiving unit that receives SMS messages and an IP packet generating unit that converts them to IP packets, thereby removing the need for MTC-UE to implement complex SMS client functionality while maintaining message reception capability
Solution Approach 2:
The gateway device acts as an intermediary between the SMS-based messaging system and the IP-based MTC-UE. It receives SMS messages from the network, converts them to IP packets, and forwards them to the MTC-UE, thereby enabling IP-native communication without requiring the endpoint device to support SMS protocols
2Adaptability or versatility
If NAT functionality is implemented in GGSN/P-GW for IP address conversion, then external AS can communicate with MTC-UE, but additional functionalities like ICE are required increasing device complexity
Solution Approach 1:
The patent applies preliminary action by having the MTC-UE notify the service control device of its public IP address in advance. The service control device stores this mapping information and uses it when routing incoming messages, eliminating the need for complex runtime NAT traversal mechanisms like ICE while enabling external AS to communicate with the MTC-UE
Data Source
AI summary
In a communication system 10, an IN-CSE 200 maps and retains a public IP address acquired from an MTC-UE 100 and an UE-ID, and receives an incoming message addressed to the MTC-UE 100 from an AS 40A. The IN-CSE 200, upon receiving the incoming message, sets the public IP address mapped with the retained UE-ID in a destination address, and delivers to a GGSN/PGW 310 an IP packet containing the corresponding UE-ID. The GGSN/PGW 310 identifies a private IP address assigned to the MTC-UE 100, based on the UE-ID included in the IP packet received from the IN-CSE 200.