Lines Matching refs:transfer

9 transport method for the :ref:`bluetooth_mesh_dfu`, but may be used for other object transfer
13 bytes). The BLOB transfer protocol has built-in recovery procedures for packet losses, and sets up
14 checkpoints to ensure that all targets have received all the data before moving on. Data transfer
17 BLOB transfers are constrained by the transfer speed and reliability of the underlying mesh network.
19 BLOB to be transferred in 10-15 minutes. However, network conditions, transfer capabilities and
21 parameters of the transfer according to the application and network configuration, as well as
23 and reliability of the protocol. However, achieving transfer rates close to the ideal rate is
40 The BLOB transfer protocol introduces several new concepts to implement the BLOB transfer.
47 transfer through the mesh network. The BLOBs are continuous data objects, divided into blocks and
52 The BLOB transfer protocol does not provide any built-in integrity checks, encryption or
63 determined by the transfer's ``block_size_log`` parameter, and is the same for all blocks in the
64 transfer except the last, which may be smaller. For a BLOB stored in flash memory, the block size is
70 Each block is divided into chunks. A chunk is the smallest data unit in the BLOB transfer, and must
72 mechanism for transferring chunks depends on the transfer mode.
85 Read more about the transfer modes in :ref:`bluetooth_mesh_blob_transfer_modes` section.
92 In the BLOB Transfer models' APIs, the BLOB data handling is separated from the high-level transfer
93 handling. This split allows reuse of different BLOB storage and transfer strategies for different
94 applications. While the high level transfer is controlled directly by the application, the BLOB data
115 calls :c:member:`block_end <bt_mesh_blob_io.block_end>`. When the transfer is complete, the BLOB
132 Each BLOB Transfer Server may have different transfer capabilities. The transfer capabilities of
143 To ensure that the transfer can be received by as many servers as possible, the BLOB Transfer Client
144 can retrieve the capabilities of each BLOB Transfer Server before starting the transfer. The client
145 will transfer the BLOB with the highest possible block and chunk size.
152 BLOBs can be transferred using two transfer modes, Push BLOB Transfer Mode and Pull BLOB Transfer
153 Mode. In most cases, the transfer should be conducted in Push BLOB Transfer Mode.
157 any number of Target nodes, and should be the default transfer mode.
174 The timeout of the BLOB transfer is based on a Timeout Base value. Both client and server use the
177 The BLOB Transfer Server uses the following formula to calculate the BLOB transfer timeout::
186 where TTL is time to live value set in the transfer.