Lines Matching refs:transfer

6 The Binary Large Object (BLOB) Transfer Client is the sender of the BLOB transfer. It supports
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.
64 not :c:macro:`BT_MESH_ADDR_UNASSIGNED`, the messages in the transfer will be sent to the group
68 Using group addresses for transferring the BLOBs can generally increase the transfer speed, as the
81 limit, the Target node is dropped from the transfer. The application can reduce the chances of this
84 time scales automatically with the transfer TTL.
86 Note that the BLOB Transfer Client only moves forward with the transfer in following cases:
94 BLOB transfer capabilities retrieval
97 It is generally recommended to retrieve BLOB transfer capabilities before starting a transfer. The
98 procedure populates the transfer capabilities from all Target nodes with the most liberal set of
99 parameters that allows all Target nodes to participate in the transfer. Any Target nodes that fail
100 to respond, or respond with incompatible transfer parameters, will be dropped.
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
120 The transfer runs until it either completes successfully for at least one Target node, or it is
121 cancelled. The end of the transfer is communicated to the application through the :c:member:`end