Lines Matching full:blob
3 BLOB Transfer Client
6 The Binary Large Object (BLOB) Transfer Client is the sender of the BLOB transfer. It supports
7 sending BLOBs of any size to any number of Target nodes, in both Push BLOB Transfer Mode and Pull
8 BLOB Transfer Mode.
16 The BLOB Transfer Client is instantiated on an element with a set of event handler callbacks:
35 Both the transfer capabilities retrieval procedure and the BLOB transfer uses an instance of a
36 :c:struct:`bt_mesh_blob_cli_inputs` to determine how to perform the transfer. The BLOB Transfer Cli…
57 Note that all BLOB Transfer Servers in the transfer must be bound to the chosen application key.
66 Target nodes having the BLOB Transfer Server model subscribe to this group address.
69 BLOB Transfer Client sends each message to all Target nodes at the same time. However, sending
73 losing Target nodes. Using group addresses for BLOB transfers will generally only pay off if the
80 If a Target node fails to respond to an acknowledged message within the BLOB Transfer Client's time
82 by giving the BLOB Transfer Client extra time through the context structure. The extra time may be
86 Note that the BLOB Transfer Client only moves forward with the transfer in following cases:
90 * The BLOB Transfer Client times out.
94 BLOB transfer capabilities retrieval
97 It is generally recommended to retrieve BLOB transfer capabilities before starting a transfer. The
109 for the BLOB transfer.
111 BLOB transfer
114 The BLOB transfer is started by calling :c:func:`bt_mesh_blob_cli_send` function, which (in addition
115 to the aforementioned transfer inputs) requires a set of transfer parameters and a BLOB stream
116 instance. The transfer parameters include the 64-bit BLOB ID, the BLOB size, the transfer mode, the
117 block size in logarithmic representation and the chunk size. The BLOB ID is application defined, but
118 must match the BLOB ID the BLOB Transfer Servers have been started with.