M2M Parameter Control via DNS Addressing for Network Load Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing demand for M2M communications poses challenges such as network overload, inefficient resource utilization, and difficulties in establishing connections between M2M devices and application servers, particularly due to unknown full IPv6 addresses in GGSN/PGW and MTC Server/SCS/MTC Application.
Innovation Solution
A method for determining and transmitting M2M application-specific parameters between network nodes during communication sessions, using protocol configuration options (PCO) to control M2M device behavior and provide IPv6 address information, allowing operators to manage resources and initiate Mobile Terminated Communication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If M2M devices simultaneously access the network, then communication coverage is improved, but network overload occurs
Solution Approach 1:
The patent segments the network architecture by introducing dedicated MTC servers and application servers that handle M2M communications separately from general mobile communications. This segmentation allows M2M devices to access the network while preventing general network overload, as the MTC server specifically manages M2M traffic and uses efficient IP address allocation mechanisms.
2Adaptability or versatility
If full IPv6 addresses are allocated to all M2M devices, then addressing capability is improved, but system resources are consumed
Solution Approach 1:
The patent extracts the IP address management function from the core network by implementing a DNS-based addressing mechanism. Instead of allocating and managing full IPv6 addresses in the GGSN/PGW, the system uses DNS names that resolve to M2M device addresses. This extraction reduces system resource consumption while maintaining full addressing capability through the DNS infrastructure.
Solution Approach 2:
The patent changes the addressing parameter from full IPv6 addresses to DNS-based identifiers. The MTC server stores and manages DNS names rather than complete IPv6 addresses, reducing the amount of data that needs to be stored and transmitted in the core network while maintaining the ability to uniquely identify and communicate with any M2M device.
3Ease of operation
If MTC Server initiates communication without knowing full IPv6 address, then connection establishment is simplified, but communication reliability deteriorates
Solution Approach 1:
The patent introduces the DNS system as an intermediary between the MTC server and M2M devices. The MTC server uses DNS names to initiate communication without needing full IPv6 addresses, and the DNS system resolves these names to the appropriate addresses. This intermediary mechanism simplifies connection establishment for the MTC server while ensuring communication reliability through proper address resolution.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Example embodiments disclosed herein may be directed towards a system, and corresponding method, for sending machine-to-machine (M2M) application specific parameters. These parameters may allow a network operator to guide M2M application behaviour in accordance with potentially limited recourses in the network. These parameters mayalso be used to provide IPv6 address information to a gateway node and/or M2M server and/or Service Capability Server (SCS).