Searched refs:Client (Results 1 – 25 of 109) sorted by relevance
12345
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | srpl_cli.rst | 3 Solicitation PDU RPL Configuration Client
6 The Solicitation PDU RPL Configuration Client model is a foundation model defined by the Bluetooth
10 The Solicitation PDU RPL Configuration Client model was introduced in the Bluetooth Mesh Protocol
15 The Solicitation PDU RPL Configuration Client model communicates with a Solicitation PDU RPL
16 Configuration Server model using the application keys configured by the Configuration Client.
18 If present, the Solicitation PDU RPL Configuration Client model must only be instantiated on the
24 The Solicitation PDU RPL Configuration Client model behavior can be configured with the transmission
27 Configuration Client waits for a response message to arrive in milliseconds. This value can be
|
| D | cfg_cli.rst | 3 Configuration Client
6 The Configuration Client model is a foundation model defined by the Bluetooth Mesh
11 The Configuration Client model communicates with a
13 node. The Configuration Client model may communicate with servers on other
16 All configuration functions in the Configuration Client API have ``net_idx``
20 The Configuration Client model is optional, and it must only be instantiated on the
|
| D | op_agg_cli.rst | 3 Opcodes Aggregator Client
6 The Opcodes Aggregator Client model is a foundation model defined by the Bluetooth Mesh
10 The Opcodes Aggregator Client model is introduced in the Bluetooth Mesh Protocol Specification
14 The Opcodes Aggregator Client model communicates with an Opcodes Aggregator Server model using the
15 device key of the target node or the application keys configured by the Configuration Client.
17 If present, the Opcodes Aggregator Client model must only be instantiated on the primary element.
19 The Opcodes Aggregator Client model is implicitly bound to the device key on initialization. It
|
| D | od_cli.rst | 3 On-Demand Private Proxy Client
6 The On-Demand Private Proxy Client model is a foundation model defined by the Bluetooth Mesh
10 The On-Demand Private Proxy Client model was introduced in the Bluetooth Mesh Protocol Specification
15 The On-Demand Private Proxy Client model communicates with an On-Demand Private Proxy Server model
19 If present, the On-Demand Private Proxy Client model must only be instantiated on the primary
25 The On-Demand Private Proxy Client model behavior can be configured with the transmission timeout
27 :kconfig:option:`CONFIG_BT_MESH_OD_PRIV_PROXY_CLI_TIMEOUT` controls how long the Client waits for a
|
| D | priv_beacon_cli.rst | 3 Private Beacon Client
6 The Private Beacon Client model is a foundation model defined by the Bluetooth
10 The Private Beacon Client model is introduced in the Bluetooth Mesh Protocol
19 The Private Beacon Client model communicates with a
21 target node. The Private Beacon Client model may communicate with servers on
24 All configuration functions in the Private Beacon Client API have ``net_idx``
28 If present, the Private Beacon Client model must only be instantiated on the primary element.
|
| D | dfu_cli.rst | 3 Firmware Update Client
6 The Firmware Update Client is responsible for distributing firmware updates through the mesh
7 network. The Firmware Update Client uses the :ref:`bluetooth_mesh_blob_cli` as a transport for its
|
| D | health_cli.rst | 3 Health Client
6 The Health Client model interacts with a Health Server model to read out
9 All message passing functions in the Health Client API have ``cli`` as
15 The Health Client model is optional, and may be instantiated on any element.
16 However, if a Health Client model is instantiated on an element other than the
|
| D | brg_cfg_cli.rst | 3 Bridge Configuration Client
6 The Bridge Configuration Client is a foundation model defined by the Bluetooth Mesh
10 The Bridge Configuration Client model provides functionality for configuring the
15 If present, the Bridge Configuration Client model must only be instantiated on the primary
|
| D | lcd_cli.rst | 3 Large Composition Data Client
6 The Large Composition Data Client model is a foundation model defined by the Bluetooth Mesh
10 The Large Composition Data Client model was introduced in the Bluetooth Mesh Protocol Specification
15 The Large Composition Data Client model communicates with a Large Composition Data Server model
18 If present, the Large Composition Data Client model must only be instantiated on the primary
|
| D | sar_cfg_cli.rst | 3 SAR Configuration Client
6 The SAR Configuration Client model is a foundation model defined by the Bluetooth Mesh
10 The SAR Configuration Client model is introduced in the Bluetooth Mesh Protocol Specification
29 An element can send any SAR Configuration Client message at any time to query or change the states
30 supported by the SAR Configuration Server model of a peer node. The SAR Configuration Client model
34 If present, the SAR Configuration Client model must only be instantiated on the primary element.
|
| D | blob_srv.rst | 15 BLOB Transfer Client model, the BLOB Transfer Server must allow blocks to come in any order. The
21 BLOB Transfer Client.
45 transfer is started by the BLOB Transfer Client. The ID must be shared between the BLOB Transfer
46 Client and the BLOB Transfer Server through some higher level procedure, like a vendor specific
65 message. If the BLOB Transfer Client does not send a message before the transfer timer expires, the
72 The BLOB Transfer Client may resume a suspended transfer by starting a new block transfer. The BLOB
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
|
| D | rpr_cli.rst | 3 Remote Provisioning Client
6 The Remote Provisioning Client model is a foundation model defined by the Bluetooth
10 The Remote Provisioning Client model is introduced in the Bluetooth Mesh Protocol
16 The Remote Provisioning Client model communicates with a Remote Provisioning Server model
19 If present, the Remote Provisioning Client model must be instantiated on the primary
26 Provisioning Server. The Remote Provisioning Client starts a scan procedure by using the
63 Additionally, the Remote Provisioning Client model also supports extended scanning with the
72 The Remote Provisioning Client starts a provisioning procedure by using the
102 In addition to scanning and provisioning functionality, the Remote Provisioning Client also provides
|
| D | blob.rst | 34 The BLOB Transfer Client is instantiated on the sender node, and the BLOB Transfer Server is
61 in size. Each block is transmitted separately, and the BLOB Transfer Client ensures that all BLOB
75 BLOB Transfer Client to all targeted BLOB Transfer Servers. Once all chunks in a block have been
76 sent, the BLOB Transfer Client asks each BLOB Transfer Server if they're missing any chunks, and
78 Transfer Client gives up.
81 chunks from the BLOB Transfer Client at a time, and wait for the BLOB Transfer Client to send them
108 stream is always opened in write mode, and when used with a BLOB Transfer Client, it's always opened
141 Client and affects memory consumption by the BLOB Transfer Client model structure.
143 To ensure that the transfer can be received by as many servers as possible, the BLOB Transfer Client
155 In Push BLOB Transfer Mode, the send rate is controlled by the BLOB Transfer Client, which will push
[all …]
|
| D | blob_cli.rst | 3 BLOB Transfer Client
6 The Binary Large Object (BLOB) Transfer Client is the sender of the BLOB transfer. It supports
16 The BLOB Transfer Client is instantiated on an element with a set of event handler callbacks:
36 …struct:`bt_mesh_blob_cli_inputs` to determine how to perform the transfer. The BLOB Transfer Client
69 BLOB Transfer Client sends each message to all Target nodes at the same time. However, sending
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.
|
| D | cfg.rst | 12 Configuration Client can communicate with to change the node configuration. In some
13 cases, the mesh node can't rely on the Configuration Client to detect or determine
|
| /Zephyr-latest/subsys/bluetooth/mesh/shell/ |
| D | Kconfig | 71 bool "Support for Health Client shell commands"
75 This option enables support of Health Client shell commands.
78 bool "Support for Bridge Configuration Client shell commands"
82 This option enables support of Bridge Configuration Client shell commands.
85 bool "Support for Configuration Client shell commands"
89 This option enables support of Configuration Client shell commands.
99 bool "Support for Firmware Update Client shell commands"
103 Firmware Update Client shell support.
127 bool "Support for BLOB Transfer Client shell commands"
131 BLOB Transfer Client shell support.
[all …]
|
| /Zephyr-latest/samples/drivers/mbox_data/ |
| D | README.rst | 83 mbox_data Client demo started
84 Client send (on channel 3) value: 0
85 Client received (on channel 2) value: 1
86 Client send (on channel 3) value: 2
87 Client received (on channel 2) value: 3
88 Client send (on channel 3) value: 4
90 Client received (on channel 2) value: 95
91 Client send (on channel 3) value: 96
92 Client received (on channel 2) value: 97
93 Client send (on channel 3) value: 98
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | ccp.rst | 37 Call Control Client
39 The Call Control Client is a role that typically resides on resource constrained devices such as
42 Using the Call Control Client argument
44 The Client can control a remote CCP server device.
45 For example a remote device may have an incoming call that can be accepted by the Client.
50 ccp_call_control_client - Bluetooth CCP Call Control Client shell commands
|
| /Zephyr-latest/subsys/net/lib/tftp/ |
| D | Kconfig | 22 int "Maximum amount of time the TFTP Client will wait for a response from the server."
25 Maximum amount of time (in msec) that the TFTP Client will wait for
26 data from the TFTP Server. Once this time has elapsed, the TFTP Client
30 int "Number of times the TFTP Client will retransmit the request to the server."
33 Once the TFTP Client sends out a request, it will wait
|
| /Zephyr-latest/subsys/bluetooth/services/ias/ |
| D | Kconfig.ias | 31 #### Immediate Alert Service Client ################################
34 bool "Immediate Alert Service Client [Experimental]"
38 This option enables support for Immediate Alert Service Client
|
| /Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
| D | README.rst | 13 - Generic OnOff Client
15 - Generic Level Client
17 - Generic Default Transition Time Client
20 - Generic Power OnOff Client
23 - Light Lightness Client
26 - Light CTL Client
32 - Generic Level Client
47 * Button1 and Button2 are associated with gen. OnOff Client or Vendor Model which is part of Root e…
48 …Button3 and Button4 are associated with gen. Level Client / Light Lightness Client / Light CTL Cli…
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.ccp | 11 bool "Call Control Profile Client Support"
16 This option enables support for the Call Control Profile Client which uses the Telephone
27 The number of supported telephone bearers on the CCP Call Control Client
30 module-str = "Call Control Profile Client"
|
| D | Kconfig.mcs | 20 #### Media Control Client ################################
23 bool "Media Control Client Support"
28 This option enables support for the Media Control Client.
70 bool "Media Control Client support for Object Transfer Service"
73 Use this option to configure support in the Media Control Client for
118 bool "Media Control Client Shell Support"
121 This option enables shell support for the Media Control Client.
124 bool "Minimal Media Control Client without optional procedures"
126 This option disables all optional procedures in the Media Control Client.
|
| /Zephyr-latest/samples/bluetooth/hap_ha/ |
| D | README.rst | 5 Advertise and await connection from a Hearing Aid Unicast Client or Remote Controller.
11 Starts advertising and awaits connection from a Hearing Aid Unicast Client (HAUC)
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/audio/ |
| D | media.rst | 20 Media Control Client
|
12345
