Enterprise Bus Gateway Packet Processing for M2M Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M communication networks face challenges in managing millions of connected objects due to high energy consumption and data flow peaks, which existing protocols like LTE struggle to handle efficiently, leading to network overload.
Innovation Solution
Implementing a method that uses an Enterprise Bus (ESB) architecture to process packets by verifying integrity, eliminating duplicates, and integrating state and client identifiers, with idempotent filtering and messaging protocols like MQTT and XMPP, to manage data flow efficiently and reduce energy consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If LTE protocols are used for M2M communication, then communication speed is improved (up to 300Mbits/s), but electrical consumption increases significantly
Solution Approach 1:
The patent applies parameter changes by transitioning from high-speed LTE protocols to low-bit-rate protocols optimized for M2M applications. The system adjusts communication parameters to match the actual needs of M2M devices, which require only a few thousand bits per day rather than the high speeds LTE provides. This parameter optimization reduces electrical consumption while maintaining adequate communication performance for sensor data transmission.
2Use of energy by moving object
If radio communication means are switched off most of the time to save energy, then energy consumption is reduced, but data flow peaks occur when devices switch on
Solution Approach 1:
The patent applies preliminary action by implementing pre-processing operations at the gateway before data reaches the server. The gateway performs integrity checks, duplicate elimination, and packet formatting in advance, preparing data for efficient server processing. This preliminary preparation at the edge of the network prevents overwhelming the server during peak transmission periods while maintaining the energy-saving sleep schedule of M2M devices.
Solution Approach 2:
The gateway acts as an intermediary between M2M devices and the server. It buffers and pre-processes incoming packets, managing the data flow peaks that occur when devices wake up to transmit data. The gateway's pre-processing capabilities absorb the variability in traffic patterns, smoothing the load on the server and preventing system overload during peak periods.
3Productivity
If gateways pre-process packets to save server resources, then server processing load is reduced, but pre-processing complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the data processing function between the gateway and the server. The gateway handles pre-processing tasks (integrity checks, duplicate elimination, formatting), while the server focuses on higher-level data exploitation and application logic. This functional segmentation allows the gateway to manage packet preparation complexity locally, preventing it from overwhelming the server while maintaining efficient overall system processing.
Data Source
Figure 1
Figure 2
Figure 3a~3c
AI summary
The present invention relates to a method of processing a packet sent from a device (1a, 1b) comprising radio communication means (10), the method being characterized in that it comprises steps of: (a) reception of the packet by at least one gateway (2a, 2b) via radio communication, each gateway (2a, 2b) being connected to the internet network (40) via an Enterprise Bus (ESB) (3) implemented by at least one platform; (b) verification of the integrity of the packet and re-transmission of the data of the packet to an input connector (30) of the ESB (3); (c) reception of the said data of the packet by the input connector (30) and conversion of said data of the packet into an internal message inside the ESB (3) containing the data of the packet; (d) determination of a state identifier and of a client identifier of the device (1a, 1b) of origin of the packet by interrogation of a directory (32) of devices (1a, 1b) associated with the ESB (3), (e) modification by the ESB (3) of said internal message so as to integrate said state identifier and client identifier determined, and sending of the modified message to a queue of messages (33); (f) destacking of said message from said message stack (33), and modification by the ESB (3) of a data base (35) as a function of the data and of the identifiers contained in the message.