Lines Matching refs:transfer

14 models are divided into blocks, which are divided into chunks. As the transfer is controlled by the
42 A BLOB Transfer Server is capable of receiving a single BLOB transfer at a time. Before the BLOB
43 Transfer Server can receive a transfer, it must be prepared by the user. The transfer ID must be
45 transfer is started by the BLOB Transfer Client. The ID must be shared between the BLOB Transfer
47 transfer management model.
49 Once the transfer has been set up on the BLOB Transfer Server, it's ready for receiving the BLOB.
50 The application is notified of the transfer progress through the event handler callbacks, and the
64 The BLOB Transfer Server keeps a running timer during the transfer, that is reset on every received
65 message. If the BLOB Transfer Client does not send a message before the transfer timer expires, the
66 transfer is suspended by the BLOB Transfer Server.
72 The BLOB Transfer Client may resume a suspended transfer by starting a new block transfer. The BLOB
79 The state of the BLOB transfer is stored persistently. If a reboot occurs, the BLOB Transfer Server
80 will attempt to recover the transfer. When the Bluetooth Mesh subsystem is started (for instance by
83 callback, the user must provide a BLOB stream to use for the rest of the transfer. If the recover
84 callback doesn't return successfully or does not provide a BLOB stream, the transfer is abandoned.
87 After a transfer is successfully recovered, the BLOB Transfer Server enters the suspended state. It
88 will stay suspended until the BLOB Transfer Client resumes the transfer, or the user cancels it.
91    The BLOB Transfer Client sending the transfer must support transfer recovery for the transfer to
92    complete. If the BLOB Transfer Client has already given up the transfer, the BLOB Transfer Server