Lines Matching refs:model

36    implemented by the :ref:`bluetooth_mesh_dfu_srv` model. A transfer may be targeting any number of
69 replace the Firmware Distribution Server model with a proprietary mechanism that will access the
70 Firmware Update Client model directly, e.g. over a serial protocol.
200 DFU. Depending on the availability of the Remote Provisioning Server model on the old and new image,
220 Update Server model calls the :c:member:`bt_mesh_dfu_srv_cb.check` callback, the application can
257 #. The Initiator's BLOB Transfer Client model transfers the firmware image to the Distributor's BLOB
299 The Distributor's Firmware Update Client model uses its BLOB Transfer Client model's broadcast
303 1. The Distributor's Firmware Update Client model generates a BLOB ID and sends it to each Target
304    node's Firmware Update Server model, along with the other BLOB transfer parameters, the Target
306    check and prepares their BLOB Transfer Server model for the transfer, before sending a status
309 #. The Distributor's BLOB Transfer Client model transfers the firmware image to all Target nodes.
313 #. The Distributor's Firmware Update Client model queries all Target nodes to ensure that they've
341 1. The Distributor's Firmware Update Client model instructs all Target nodes that have verified the
348 #. The Distributor's Firmware Update Client model requests the full list of firmware images from
355    Firmware Update Client model will send a request for the full firmware image list, and expect no