Lines Matching full:distribution

6 Bluetooth Mesh supports the distribution of firmware images across a mesh network. The Bluetooth
10 Bluetooth Mesh DFU implements a distribution mechanism for firmware images, and does not put any
32 distribution of firmware images:
59          distribution
69 replace the Firmware Distribution Server model with a proprietary mechanism that will access the
88    time-consuming Distribution stage. Once the firmware has been uploaded to the Distributor, the
89    Initiator may trigger the Distribution stage at any time.
92   Before starting the Distribution stage, the Initiator may optionally check if Target nodes can
94   firmware, are excluded from the firmware distribution process.
96 Distribution stage
191       The out-of-band distribution mechanism is not supported.
237 The Distribution stage is controlled by the Distributor, as implemented by the
253 1. The Initiator generates a BLOB ID, and sends it to the Distributor's Firmware Distribution Server
255    Distribution Server stores the information, and prepares its BLOB Transfer Server for the
260 When the BLOB transfer finishes, the firmware image is ready for distribution. The Initiator may
279 Target node. The Initiator may send one or more Firmware Distribution Receivers Add messages to
280 build the Distributor's receivers list, and a Firmware Distribution Receivers Delete All message to
286 Initiating the distribution
290 may initiate the distribution procedure. The BLOB transfer parameters for the distribution are
296 Firmware distribution  argument
300 subsystem to communicate with all Target nodes. The firmware distribution is performed with the
316 If the distribution procedure completed with at least one Target node reporting that the image has
317 been received and verified, the distribution procedure is considered successful.
320    The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the
324 Suspending the distribution  argument
327 The Initiator can also request the Distributor to suspend the firmware distribution. In this case,
328 the Distributor will stop sending any messages to Target nodes. When the firmware distribution is
353    During the metadata check in the distribution procedure, the Target node may have reported that
358 Cancelling the distribution
361 The firmware distribution can be cancelled at any time by the Initiator. In this case, the
364 request has timed out, the distribution procedure is cancelled. After this the distribution
365 procedure can be started again from the ``Firmware distribution`` section.