M2M Gateway Change Using Tree Data Structure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In machine-to-machine (M2M) systems, changing a gateway can lead to data loss and service interruptions due to the lack of efficient methods for managing and storing data from devices with constrained capabilities, and reconfiguring services across multiple devices and gateways is cumbersome, resulting in potential delays and service disruptions.
Innovation Solution
A method and device for efficiently changing a gateway in an M2M system by using a tree structure data structure to manage and store data from devices with constrained capabilities, where a trigger signal initiates a notification to the M2M server, and a processor handles the gateway change, ensuring seamless data retrieval and minimal service interruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If gateway change is performed in M2M system, then system adaptability is improved, but data loss occurs and service interruption happens
Solution Approach 1:
The patent applies preliminary action by notifying the M2M server of the gateway change before the actual switch occurs. The source gateway sends a gateway change notification message to the M2M server, which includes information about the target gateway. This allows the server to prepare for the transition by updating its routing information and ensuring data can be properly forwarded to the new gateway, preventing data loss during the transition.
Solution Approach 2:
The M2M server acts as an intermediary that manages the gateway change process. It receives notifications from the source gateway, processes the change information, and coordinates with both the source and target gateways to ensure seamless data transfer. The server maintains data integrity by acting as a central coordination point that prevents data loss during the gateway transition.
2Adaptability or versatility
If gateway change is performed in M2M system, then system adaptability is improved, but service interruption occurs
Solution Approach 1:
The system performs preliminary actions by pre-notifying the M2M server of the upcoming gateway change. The server uses this advance information to prepare routing tables and data forwarding paths before the actual gateway switch, enabling a smoother transition that minimizes service interruption time.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining data forwarding capabilities throughout the gateway transition. The M2M server continues to receive and process data from the source gateway while simultaneously preparing to forward data to the target gateway, ensuring that data flow remains continuous and service interruption is minimized.
3Productivity
If data is managed in tree structure by first layer gateway, then data retrieval efficiency is improved, but device complexity increases
Solution Approach 1:
The patent applies segmentation by organizing data into a hierarchical tree structure where the first layer gateway manages data from multiple second layer devices. Each device's data is stored as a separate branch in the tree, with clear hierarchical relationships. This segmentation allows efficient data retrieval by enabling the gateway to directly access specific device data through the tree structure without searching through all data, while the modular nature of the tree structure keeps management complexity manageable.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The present invention relates to a gateway changing method performed by a machine-to-machine (M2M) gateway which communicates with at least one M2M device having a constrained capability in an M2M system that includes a first layer and a second layer, and the a device therefor, the method comprising the steps of: receiving a trigger signal for indicating a gateway change through a first layer of the M2M gateway; and transmitting, to an M2M server, a first notification for indicating the gateway change through the first layer of the M2M gateway, wherein the M2M device having the constrained capability is a device that does not have the first layer, data generated in the second layer of the M2M device having the constrained capability is managed or stored in a data structure of a tree structure by the first layer of the M2M gateway, and the data structure that includes the data is retrieved by the M2M server after the notification has been transmitted to the M2M server.