Lines Matching refs:nodes

31 The Bluetooth Mesh DFU subsystem defines three different roles the mesh nodes have to assume in the
37    Target nodes, and they will all be updated concurrently.
42    nodes as the Distributor. The Distributor does not select the parameters of the transfer, but
43    relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
47    image to the Target nodes.
53    Target nodes and their firmware, and will control (and initiate) all firmware updates. The
58    :alt: Graphic overview of the DFU roles mesh nodes can have during the process of image
92   Before starting the Distribution stage, the Initiator may optionally check if Target nodes can
97    Before the firmware image can be distributed, the Initiator transfers the list of Target nodes
101    nodes, the Distributor may ask them to apply the firmware image immediately and report back with
115    The firmware ID is used to identify a firmware image. The Initiator node may ask the Target nodes
130    Target node after the metadata check, as other nodes will never request the metadata from the
276 Before the Distributor can start distributing the firmware image, it needs a list of Target nodes to
277 send the image to. The Initiator gets the full list of Target nodes either by querying the potential
290 Once the Distributor has stored a firmware image and received a list of Target nodes, the Initiator
293 Distributor should request that the firmware is applied on the Target nodes or not. The Distributor
295 nodes.
301 subsystem to communicate with all Target nodes. The firmware distribution is performed with the
310 #. The Distributor's BLOB Transfer Client model transfers the firmware image to all Target nodes.
311 #. Once the BLOB transfer has been received, the Target nodes' applications verify that the firmware
314 #. The Distributor's Firmware Update Client model queries all Target nodes to ensure that they've
321    The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the
322    Initiator to request a list of failed Target nodes from the Distributor and initiate additional
323    attempts to update the lost Target nodes after the current attempt is finished.
329 the Distributor will stop sending any messages to Target nodes. When the firmware distribution is
337 procedure on all Target nodes that successfully received and verified the firmware image. The Apply
342 1. The Distributor's Firmware Update Client model instructs all Target nodes that have verified the
343    firmware image to apply it. The Target nodes' Firmware Update Server models respond with a status
363 Distributor starts the cancelling procedure by sending a cancelling message to all Target nodes. The
364 Distributor waits for the response from all Target nodes. Once all Target nodes have replied, or the