M2M Server Notification via Connectionless UDP
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M data distribution systems face performance degradation and resource exhaustion due to maintaining numerous open connections with customer devices, especially when dealing with thousands or millions of devices, leading to increased resource strain and unfeasibility.
Innovation Solution
Implementing a system where a central M2M server stores received data and sends notifications to customer devices using a connectionless communication technique, such as UDP, allowing devices to request data on an as-needed basis, thereby conserving resources and reducing the need for constant connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the central M2M server maintains open connections with customer devices to deliver data in real-time, then data delivery reliability is improved, but resource consumption increases and system performance degrades
Solution Approach 1:
The server sends data to customer devices periodically rather than maintaining continuous connections. The system uses periodic notifications where the server pushes data at intervals, and devices pull data when needed, replacing constant connection maintenance with periodic communication cycles that reduce resource consumption while maintaining delivery reliability
Solution Approach 2:
Customer devices actively request data from the server rather than passively receiving it through maintained connections. The system allows devices to self-initiate data retrieval operations, reducing the server's burden of maintaining active connections and managing data transmission continuously
2Productivity
If the central M2M server maintains open connections with thousands or millions of customer devices, then real-time data distribution is enabled, but system complexity and operational difficulty increase
Solution Approach 1:
The system replaces continuous connection management with periodic data distribution cycles. Instead of managing thousands of persistent connections, the server periodically notifies devices of available data and transfers information in batches, significantly reducing the complexity of connection management while maintaining real-time distribution capability
Solution Approach 2:
The system extracts the data transmission function from continuous connection maintenance. By separating data availability notification from actual data transfer, the server can manage connections sparsely, only opening them when needed for data delivery, which reduces overall system complexity
3Reliability
If the central M2M server uses connection-based communication techniques, then data transmission reliability is improved, but network resource strain increases
Solution Approach 1:
The server uses periodic notifications to alert devices of available data rather than maintaining continuous network connections. This periodic approach reduces network resource strain by opening connections only when data needs to be transmitted, while still ensuring reliable delivery through acknowledged request-response cycles
Data Source
AI summary
A server device may be configured to store association information that associates a group of machine-to-machine (“M2M”) devices with a group of customer devices; identify, based on the association information, a particular customer device, of the group of customer devices, associated with one or more M2M devices from which M2M data was received by the server device; output, using a connectionless communication technique, a notification to the particular customer device, the notification being based on the received M2M data; receive a request for M2M data associated with the particular customer device; and output the received M2M data to the particular customer device.