Distributed M2M Status Checking to Avoid Server Single-Point Failure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M device health checking methods rely on a single server, which is a single point of failure and inefficiently manages resource and energy consumption, especially as the number of devices increases, leading to resource wastage and network strain.
Innovation Solution
A distributed method where M2M devices within a network perform operational status checks on each other and report back to a server, using Lightweight Machine to Machine (LWM2M) objects to configure and enable health checks, reducing the server's workload and eliminating single-point failures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a single server checks the health of all M2M devices, then the server can centralize management and control, but the server becomes a single point of failure and experiences excessive workload and resource consumption
Solution Approach 1:
The patent segments the health checking function from the central server and distributes it to M2M devices themselves. Each device performs health checks on its neighbors, transforming a centralized monolithic function into distributed modular operations, thereby eliminating the single point of failure while maintaining management effectiveness
Solution Approach 2:
M2M devices perform health checking on themselves and on neighboring devices autonomously without requiring continuous server intervention. This self-service mechanism reduces the server's workload to minimal coordination and data collection, while devices handle the bulk of health monitoring independently
2Ease of operation
If a single server checks the health of all M2M devices, then centralized control is maintained, but resource consumption and energy usage increase significantly
Solution Approach 1:
The health checking workload is segmented and distributed across multiple M2M devices rather than concentrated on a single server. Each device handles only its assigned neighbors' health monitoring, proportionally distributing computational and energy resources across the network
Solution Approach 2:
Devices autonomously perform health checks using their own computational resources, eliminating the need for the server to expend energy on detailed health monitoring. The server only consumes minimal energy for receiving and processing health status reports
3Reliability
If the server wakes up all M2M devices before communication, then complete device availability is ensured, but message overhead and network strain increase
Solution Approach 1:
M2M devices perform health checks proactively before the server needs to communicate with them, ensuring device availability is established in advance. This preliminary action eliminates the need for server-initiated wake-up messages and reduces overall message overhead
Solution Approach 2:
Devices self-manage their availability status by performing autonomous health checks and reporting their state, eliminating the need for the server to send repeated wake-up or availability-checking messages to ensure device readiness
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method performed by a machine-to-machine, M2M, server for establishing an operational status of a M2M device in a M2M network is disclosed. The method comprising configuring a first M2M device to perform an operational status check on a second M2M device, and receiving from the first M2M device the operational status check of the second M2M device.