IoT File Update via MQTT Block Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
IoT event-driven architectures face challenges with protocol incompatibility, size limitations, and data communication reliability due to the inability of existing protocols like MQTT to support large file transfers and congestion control, especially in legacy devices configured for REST updates.
Innovation Solution
The system splits files into smaller portions to bypass protocol size limitations and manages their transmission through dynamically-allocated communication sessions, using a publish/subscribe broker service and local REST interactions to enable efficient updates in IoT devices, allowing for large file transfers and congestion control without modifying standard MQTT implementations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If MQTT protocol is used for file transmission in IoT devices, then communication efficiency is improved, but protocol size limitations prevent large file transfers
Solution Approach 1:
The patent divides large files into smaller blocks that fit within MQTT message size limits. Each block is transmitted separately through the MQTT publish/subscribe broker service, allowing large file transfers to be accomplished through multiple small messages rather than a single large message that would exceed protocol limitations.
2Quantity of substance
If REST interactions are used for update mechanisms, then large file transfers are supported, but protocol incompatibility with event driven architectures reduces communication efficiency
Solution Approach 1:
The patent introduces a publish/subscribe broker service as an intermediary between the management application and IoT devices. This broker enables event-driven architecture communication patterns while supporting the transfer of large files by coordinating block-by-block transmission, thus bridging the gap between REST capabilities and MQTT efficiency.
3Quantity of substance
If block-by-block transmission is implemented, then large file transfers are enabled, but data communication reliability must be ensured across multiple sessions
Solution Approach 1:
The patent implements an acknowledgment mechanism where the receiving IoT device sends confirmation messages back to the management application for each successfully received block. This feedback loop ensures reliable data communication by allowing the sender to verify receipt of each block and retransmit if necessary, maintaining reliability across multiple transmission sessions.
Data Source
AI summary
Example aspects include techniques for efficient updates in IoT event driven architectures. These techniques may include receiving, from a source application via a publish/subscribe broker service a first block using a first IoT messaging session, the first block including a first portion of a file and a first plurality of communication parameters, and transmitting a first acknowledgement corresponding to the first block, the first acknowledgement approving a proposed parameter of the first plurality of communication parameters. Further, the techniques may include receiving, based on the proposed parameter, from the source application via the publish/subscribe broker service, a second block using a second IoT messaging session, the second block including a second portion of the file and a second plurality of communication parameters, and transmitting a second acknowledgement corresponding to the second block.