BLE Firmware Upload for Faster Bluetooth Mesh Distributor Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Bluetooth Mesh specification's firmware update method is time-consuming, requiring over 20 minutes for a 400 kB image due to the Binary Large Object (BLOB) transfer procedure, which divides data into blocks and chunks, resulting in a transfer rate of only 1.2 KB/s, and additional overheads.
Innovation Solution
The method utilizes Bluetooth Low Energy (BLE) protocol data units (PDUs) for firmware image transfer between an initiator node and a distributor node, using a GATT database to bypass constraints of mesh messages, and complies with the Bluetooth Mesh specification's Out of Band (OOB) procedure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the Binary Large Object (BLOB) transfer procedure defined in the Bluetooth Mesh specification is used to upload firmware images, then the upload process complies with existing standards, but the transfer rate is limited to only 1.2 KB/s resulting in over 20 minutes for a 400 kB image
Solution Approach 1:
The patent introduces an intermediary BLE connection between the initiator node and distributor node to bypass the constrained mesh message protocol. By using BLE as an intermediate communication channel, the system achieves faster transfer rates while maintaining compliance with Bluetooth Mesh specifications through the Out of Band (OOB) procedure. The BLE connection acts as a mediator that enables efficient data transfer without being subject to mesh message segmentation constraints.
Solution Approach 2:
The patent changes the communication parameters by switching from mesh network messages with segment intervals of at least 10 ms to BLE protocol data units that allow continuous transmission. This parameter change includes using BLE's larger payload capacity and eliminating the mandatory segmentation delays, thereby increasing the transfer rate from 1.2 KB/s to over 100 KB/s while maintaining protocol compliance through OOB procedures.
2Ease of operation
If the direct approach is used where the initiator node transmits the new firmware image directly to the mesh devices, then the user can exit the premises after uploading, but the process requires the user to remain in listening range of the distributor node for the entire upload duration
Solution Approach 1:
The BLE connection serves as an intermediary that decouples the user's physical presence requirement from the upload process. By establishing a BLE connection between the initiator node (user device) and distributor node, the system enables fast local transfer that completes before the user needs to leave, eliminating the constraint of remaining in listening range while also reducing the total time the user must stay connected.
3Reliability
If mesh messages with segment intervals are used for firmware transfer, then the data is divided into manageable blocks and chunks, but the segmented transmission every 10 ms or more reduces the effective transfer rate to only 1.2 KB/s
Solution Approach 1:
The patent uses BLE as an intermediary transport layer that maintains reliability through its own acknowledgment and retransmission mechanisms while eliminating the problematic segmentation constraints of mesh messages. The BLE connection allows larger data units to be transmitted without the 10 ms interval constraint, achieving both reliability and high speed by combining BLE's robust protocol with the OOB firmware upload procedure.
Data Source
AI summary
A system and method for uploading a new firmware image to a distributor node is disclosed. The distributor node is part of a Bluetooth mesh network. In some embodiments, one of an initiator node or the distributor node includes a GATT database. A GATT client (which may be the distributor node or the initiator node) connects with the GATT database and BLE messages are used to transmit the firmware image. These BLE messages do not have the constraints that are imposed on mesh messages, and therefore the upload occurs much more quickly. This technique is compliant with the Upload Firmware Out of Band (OOB) procedure defined in the Bluetooth Mesh specification. In another embodiment, the firmware image is transmitted from the initiator node to the distributor node using a L2CAP channel.