Lines Matching full:initiator

43    relies on an Initiator to give it a list of Target nodes and transfer parameters. The Distributor
46    with the Initiator, and the :ref:`bluetooth_mesh_dfu_cli` is responsible for distributing the
49 Initiator
50    The Initiator role is typically implemented by the same device that implements the Bluetooth Mesh
52    <bluetooth_mesh_models_cfg_cli>` roles. The Initiator needs a full overview of the potential
54    Initiator role is not implemented in the Zephyr Bluetooth Mesh DFU subsystem.
65 the Distributor and Initiator role can be combined by instantiating the
66 :ref:`bluetooth_mesh_dfu_cli` on the Initiator node and calling its API directly.
68 It's also possible to combine the Initiator and Distributor devices into a single device, and
83    phone or gateway (the Initiator). During the Upload stage, the Initiator transfers the firmware
86    Initiator. The time required to complete the upload process depends on the size of the image.
87    After the upload completes, the Initiator can disconnect from the network during the much more
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
97    Before the firmware image can be distributed, the Initiator transfers the list of Target nodes
99    start the firmware distributon process, which runs in the background while the Initiator and the
115    The firmware ID is used to identify a firmware image. The Initiator node may ask the Target nodes
118    enough information for an Initiator node with knowledge of the format to determine the type of
180    The firmware URI gives the Initiator information about where firmware updates for the image can
181    be found. The URI points to an online resource the Initiator can interact with to get new
234 The Initiator controls the Upload stage of the DFU protocol, and all Distributor side handling of
251 from the Initiator to the Distributor. The Upload Firmware procedure works in two steps:
253 1. The Initiator generates a BLOB ID, and sends it to the Distributor's Firmware Distribution Server
256    incoming transfer before it responds with a status message to the Initiator.
257 #. The Initiator's BLOB Transfer Client model transfers the firmware image to the Distributor's BLOB
260 When the BLOB transfer finishes, the firmware image is ready for distribution. The Initiator may
276 send the image to. The Initiator gets the full list of Target nodes either by querying the potential
277 targets directly, or through some external authority. The Initiator uses this information to
279 Target node. The Initiator may send one or more Firmware Distribution Receivers Add messages to
289 Once the Distributor has stored a firmware image and received a list of Target nodes, the Initiator
321    Initiator to request a list of failed Target nodes from the Distributor and initiate additional
327 The Initiator can also request the Distributor to suspend the firmware distribution. In this case,
335 If the Initiator requested it, the Distributor can initiate the Apply Firmware on Target Node
361 The firmware distribution can be cancelled at any time by the Initiator. In this case, the