2 * Copyright (c) 2011 Samsung Electronics Co., Ltd All Rights Reserved
4 * Licensed under the Apache License, Version 2.0 (the License);
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
8 * http://www.apache.org/licenses/LICENSE-2.0
10 * Unless required by applicable law or agreed to in writing, software
11 * distributed under the License is distributed on an AS IS BASIS,
12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
13 * See the License for the specific language governing permissions and
14 * limitations under the License.
18 #ifndef __TIZEN_NETWORK_BLUETOOTH_DOC_H__
19 #define __TIZEN_NETWORK_BLUETOOTH_DOC_H__
22 * @defgroup CAPI_NETWORK_BLUETOOTH_MODULE Bluetooth
23 * @brief Bluetooth Service provides API to manage Bluetooth device.
24 * @ingroup CAPI_NETWORK_FRAMEWORK
26 * @section CAPI_NETWORK_BLUETOOTH_MODULE_HEADER Required Header
27 * \#include <bluetooth.h>
29 * @section CAPI_NETWORK_BLUETOOTH_MODULE_OVERVIEW Overview
30 * Bluetooth Service consists of @ref CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE, @ref CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE and @ref CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE.
33 * In order to use the above APIs, you must call #bt_initialize() in advance.
34 * In addition, #bt_deinitialize() should be called when Bluetooth Service is no longer needed.
35 * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
37 * Note on callbacks: All callbacks in this module are called in the main loop context.
39 * @section CAPI_NETWORK_BLUETOOTH_MODULE_FEATURE Related Features
40 * This API is related with the following features:\n
41 * - %http://tizen.org/feature/network.bluetooth\n
43 * It is recommended to design feature related codes in your application for reliability.\n
45 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
47 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
49 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
54 * @defgroup CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE Bluetooth Adapter
55 * @brief Bluetooth Adapter API provides functions for setting up Bluetooth and discovering other devices.
56 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
58 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_HEADER Required Header
59 * \#include <bluetooth.h>
61 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_OVERVIEW Overview
62 * This set of function is used to control a bluetooth adapter.
63 * You can also control visibility of the device, its appearance for others (adapter name).
64 * In addition, this api is used to discover neighboring bluetooth devices.
65 * This process is asynchronous, so it is up to you to build and hold list of devices in the neighborhood
66 * - the api does not provide this list.
67 * Before starting a device discovery, you can find a device from the connected devices.
68 * This functionality is implemented by foreach loop.
70 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_FEATURE Related Features
71 * This API is related with the following features:\n
72 * - %http://tizen.org/feature/network.bluetooth\n
74 * It is recommended to design feature related codes in your application for reliability.\n
76 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
78 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
80 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
82 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_ASYNCHRONOUS_OPERATIONS Asynchronous Operations
83 * <div><table class="doxtable" >
85 * <th><b>FUNCTION</b></th>
86 * <th><b>CALLBACK</b></th>
87 * <th><b>DESCRIPTION</b></th>
90 * <td>bt_adapter_set_name()</td>
91 * <td>bt_adapter_name_changed_cb()</td>
92 * <td>Used to set adapter name. </td>
95 * <td>bt_adapter_visibility_mode_changed_cb()</td>
96 * <td>Used to set visibility mode (#bt_adapter_visibility_mode_e). </td>
100 * <td>bt_adapter_start_device_discovery()<br>
101 * bt_adapter_stop_device_discovery()</td>
102 * <td>bt_adapter_device_discovery_state_changed_cb()</td>
103 * <td>Used to start or cancel device discovery. </td>
107 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_CALLBACK_OPERATIONS Callback(Event) Operations
108 * <div><table class="doxtable" >
110 * <th><b>REGISTER</b></th>
111 * <th><b>UNREGISTER</b></th>
112 * <th><b>CALLBACK</b></th>
113 * <th><b>DESCRIPTION</b></th>
116 * <td>bt_adapter_set_state_changed_cb()</td>
117 * <td>bt_adapter_unset_state_changed_cb()</td>
118 * <td>bt_adapter_state_changed_cb()</td>
119 * <td>Used to be notified of state change (enable or disable). </td>
122 * <td>bt_adapter_set_name_changed_cb()</td>
123 * <td>bt_adapter_unset_name_changed_cb()</td>
124 * <td>bt_adapter_name_changed_cb()</td>
125 * <td>Used to be notified of name change. </td>
128 * <td>bt_adapter_set_visibility_mode_changed_cb()</td>
129 * <td>bt_adapter_unset_visibility_mode_changed_cb()</td>
130 * <td>bt_adapter_visibility_mode_changed_cb()</td>
131 * <td>Used to be notified of change of visibility mode (#bt_adapter_visibility_mode_e). </td>
134 * <td>bt_adapter_set_device_discovery_state_changed_cb()</td>
135 * <td>bt_adapter_unset_device_discovery_state_changed_cb()</td>
136 * <td>bt_adapter_device_discovery_state_changed_cb()</td>
137 * <td>Used to be notified of change of device discovery state (#bt_adapter_device_discovery_state_e). </td>
141 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_MODULE_FOREACH_OPERATIONS Foreach Operations
142 * <div><table class="doxtable" >
144 * <th><b>FOREACH</b></th>
145 * <th><b>CALLBACK</b></th>
146 * <th><b>DESCRIPTION</b></th>
149 * <td>bt_adapter_foreach_bonded_device()</td>
150 * <td>bt_adapter_bonded_device_cb()</td>
151 * <td>Used to get bonded devices.</td>
156 * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
160 * @defgroup CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_MODULE Bluetooth LE Adapter
161 * @brief Bluetooth LE API provides functions for managing bonds with other devices for LE and searching for supported LE services.
162 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
164 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_MODULE_HEADER Required Header
165 * \#include <bluetooth.h>
167 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_MODULE_OVERVIEW Overview
168 * Bluetooth stack architecture has been changed. Thus, GATT APIs defined in Tizen 2.3 are deprecated and new GATT client APIs are defined.
170 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_MODULE_FEATURE Related Features
171 * This API is related with the following features:\n
172 * - %http://tizen.org/feature/network.bluetooth\n
173 * - %http://tizen.org/feature/network.bluetooth.le\n
175 * It is recommended to design feature related codes in your application for reliability.\n
177 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
179 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
181 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
186 * @defgroup CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_50_MODULE Bluetooth LE Adapter for Bluetooth 5.0
187 * @brief Bluetooth LE API provides functions for bluetooth 5.0 functionality such as 2M Phy and Coded Phy
188 * @ingroup CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_MODULE
190 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_50_MODULE_HEADER Required Header
191 * \#include <bluetooth.h>
193 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_50_MODULE_OVERVIEW Overview
194 * Bluetooth LE API provides functions for bluetooth 5.0 functionality such as 2M Phy and Coded Phy
196 * @section CAPI_NETWORK_BLUETOOTH_ADAPTER_LE_50_MODULE_FEATURE Related Features
197 * This API is related with the following features:\n
198 * - %http://tizen.org/feature/network.bluetooth\n
199 * - %http://tizen.org/feature/network.bluetooth.le\n
200 * - %http://tizen.org/feature/network.bluetooth.le.5_0\n
201 * It is recommended to design applications with regard to features, for reliability.\n
203 * You can check if the device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, and control your application's actions accordingly.\n
205 * To ensure your application is only running on devices with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
207 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>feature element description</b></a>.
213 * @defgroup CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE Bluetooth Device
214 * @brief Bluetooth Device API provides functions for managing bonds with other devices and searching for supported services.
215 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
217 * @section CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE_HEADER Required Header
218 * \#include <bluetooth.h>
220 * @section CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE_OVERVIEW Overview
221 * This set of functions is used to handle the connection with other devices.
222 * Connected devices exchange keys needed for encrypted communication,
223 * but each connection has to be approved by the latest application user.
224 * You can also set authorization of other devices.
225 * Authorized devices are connected, and it is connected automatically without the latest user
226 * being asked for authorization.
227 * In addition, this is used to search for services available on remote devices.
229 * @section CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE_FEATURE Related Features
230 * This API is related with the following features:\n
231 * - %http://tizen.org/feature/network.bluetooth\n
233 * It is recommended to design feature related codes in your application for reliability.\n
235 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
237 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
239 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
241 * @section CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE_ASYNCHRONOUS_OPERATIONS Asynchronous Operations
242 * <div><table class="doxtable" >
244 * <th><b>FUNCTION</b></th>
245 * <th><b>CALLBACK</b></th>
246 * <th><b>DESCRIPTION</b></th>
249 * <td>bt_device_create_bond()<br>
250 * bt_device_cancel_bonding()</td>
251 * <td>bt_device_bond_created_cb()</td>
252 * <td>Used to create bond or cancel creating bond. </td>
255 * <td>bt_device_destroy_bond()</td>
256 * <td>bt_device_bond_destroyed_cb()</td>
257 * <td>Used to destroy bond. </td>
260 * <td>bt_device_set_authorization()</td>
261 * <td>bt_device_authorization_changed_cb()</td>
262 * <td>Used to set as authorized or unauthorized device. </td>
265 * <td>bt_device_start_service_search()</td>
266 * <td>bt_device_service_searched_cb()</td>
267 * <td>Used to start or cancel service search. </td>
271 * @section CAPI_NETWORK_BLUETOOTH_DEVICE_MODULE_CALLBACK_OPERATIONS Callback(Event) Operations
272 * <div><table class="doxtable" >
274 * <th><b>REGISTER</b></th>
275 * <th><b>UNREGISTER</b></th>
276 * <th><b>CALLBACK</b></th>
277 * <th><b>DESCRIPTION</b></th>
280 * <td>bt_device_set_bond_created_cb()</td>
281 * <td>bt_device_unset_bond_created_cb()</td>
282 * <td>bt_device_bond_created_cb()</td>
283 * <td>Used to be notified of the result of creating bond. </td>
286 * <td>bt_device_set_bond_destroyed_cb()</td>
287 * <td>bt_device_unset_bond_destroyed_cb()</td>
288 * <td>bt_device_bond_destroyed_cb()</td>
289 * <td>Used to be notified of the result of destroying bond. </td>
292 * <td>bt_device_set_authorization_changed_cb()</td>
293 * <td>bt_device_unset_authorization_changed_cb()</td>
294 * <td>bt_device_authorization_changed_cb()</td>
295 * <td>Used to be notified of change of authorization. </td>
298 * <td>bt_device_set_service_searched_cb()</td>
299 * <td>bt_device_unset_service_searched_cb()</td>
300 * <td>bt_device_service_searched_cb()</td>
301 * <td>Used to be notified of change of service search state. </td>
306 * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
311 * @defgroup CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE Bluetooth Socket
312 * @brief Bluetooth Socket API provides functions for managing connections to other devices and exchanging data.
313 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
315 * @section CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE_HEADER Required Header
316 * \#include <bluetooth.h>
318 * @section CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE_OVERVIEW Overview
319 * This set of functions is used for exchanging data between two bluetooth
320 * devices, our device can have both roles as server (service provider) and client
322 * Depending on the role, there is difference in creating a connection.
323 * After that, processes of exchanging data and disconnection are same.
325 * To start communication, you should first register for #bt_socket_set_connection_state_changed_cb()
326 * and #bt_socket_set_data_received_cb().
327 * Next step depends on the role of your application.\n
328 * If you want to be \b server \b role, application should create socket
329 * (#bt_socket_create_rfcomm()), and start listening and accepting incoming connections
330 * (#bt_socket_listen_and_accept_rfcomm()).
331 * If you want to connect to specific device and use it's services (\a client \a role),
332 * you have to start connection with #bt_socket_connect_rfcomm() and wait for connection.\n
333 * After connection has been established (information is passed to your program with
334 * #bt_socket_connection_state_changed_cb() function call), you can exchange data by
335 * calling #bt_socket_send_data(). \n
336 * If you receive data from remote device, #bt_socket_data_received_cb() functions will be called.
337 * When you finish exchanging data, you should disconnect connection
338 * with #bt_socket_disconnect_rfcomm() and unregister callback functions (with using
339 * #bt_socket_unset_data_received_cb(), #bt_socket_unset_connection_state_changed_cb()).
341 * @section CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE_FEATURE Related Features
342 * This API is related with the following features:\n
343 * - %http://tizen.org/feature/network.bluetooth\n
345 * It is recommended to design feature related codes in your application for reliability.\n
347 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
349 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
351 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
353 * @section CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE_ASYNCHRONOUS_OPERATIONS Asynchronous Operations
354 * <div><table class="doxtable" >
356 * <th><b>FUNCTION</b></th>
357 * <th><b>CALLBACK</b></th>
358 * <th><b>DESCRIPTION</b></th>
361 * <td>bt_socket_listen_and_accept_rfcomm()<br>
362 * bt_socket_connect_rfcomm()</td>
363 * <td>bt_socket_connection_state_changed_cb()</td>
364 * <td>Used to connect a device. </td>
368 * @section CAPI_NETWORK_BLUETOOTH_SOCKET_MODULE_CALLBACK_OPERATIONS Callback(Event) Operations
369 * <div><table class="doxtable" >
371 * <th><b>REGISTER</b></th>
372 * <th><b>UNREGISTER</b></th>
373 * <th><b>CALLBACK</b></th>
374 * <th><b>DESCRIPTION</b></th>
377 * <td>bt_socket_set_data_received_cb()</td>
378 * <td>bt_socket_unset_data_received_cb()</td>
379 * <td>bt_socket_data_received_cb()</td>
380 * <td>Used to be notified of received data. </td>
383 * <td>bt_socket_set_connection_state_changed_cb()</td>
384 * <td>bt_socket_unset_connection_state_changed_cb()</td>
385 * <td>bt_socket_connection_state_changed_cb()</td>
386 * <td>Used to be notified when the state of connection changes. </td>
391 * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
395 * @defgroup CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE Bluetooth L2CAP Socket
396 * @brief Bluetooth L2CAP Socket API provides functions for managing connections to other devices and exchanging data.
397 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
399 * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_HEADER Required Header
400 * \#include <bluetooth.h>
402 * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_OVERVIEW Overview
403 * This set of functions is used for exchanging data between two bluetooth
404 * devices, our device can have both roles as server (service provider) and client
406 * Depending on the role, there is difference in creating a connection.
407 * After that, processes of exchanging data and disconnection are same.
409 * To start communication, you should first register for #bt_socket_set_l2cap_channel_connection_state_changed_cb()
410 * and #bt_socket_set_data_received_cb().
411 * Next step depends on the role of your application.\n
412 * If you want to be \b server \b role, application should create socket
413 * (#bt_socket_create_l2cap_channel()), and start listening and accepting incoming connections
414 * (#bt_socket_listen_and_accept_l2cap_channel()).
415 * If you want to connect to specific device and use it's services (\a client \a role),
416 * you have to start connection with #bt_socket_connect_l2cap_channel() and wait for connection.\n
417 * After connection has been established (information is passed to your program with
418 * #bt_socket_l2cap_channel_connection_state_changed_cb() function call), you can exchange data by
419 * calling #bt_socket_send_data_l2cap_channel(). \n
420 * If you receive data from remote device, #bt_socket_data_received_cb() functions will be called.
421 * When you finish exchanging data, you should disconnect connection
422 * with #bt_socket_disconnect_l2cap_channel() and unregister callback functions (with using
423 * #bt_socket_unset_data_received_cb(), #bt_socket_unset_l2cap_channel_connection_state_changed_cb()).
425 * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_FEATURE Related Features
426 * This API is related with the following features:\n
427 * - %http://tizen.org/feature/network.bluetooth.le.coc\n
429 * It is recommended to design feature related codes in your application for reliability.\n
431 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
433 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
435 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
437 * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_ASYNCHRONOUS_OPERATIONS Asynchronous Operations
438 * <div><table class="doxtable" >
440 * <th><b>FUNCTION</b></th>
441 * <th><b>CALLBACK</b></th>
442 * <th><b>DESCRIPTION</b></th>
445 * <td>bt_socket_listen_and_accept_l2cap_channel()<br>
446 * bt_socket_connect_l2cap_channel()</td>
447 * <td>bt_socket_l2cap_channel_connection_state_changed_cb()</td>
448 * <td>Used to connect a device. </td>
452 * @section CAPI_NETWORK_BLUETOOTH_L2CAP_SOCKET_MODULE_CALLBACK_OPERATIONS Callback(Event) Operations
453 * <div><table class="doxtable" >
455 * <th><b>REGISTER</b></th>
456 * <th><b>UNREGISTER</b></th>
457 * <th><b>CALLBACK</b></th>
458 * <th><b>DESCRIPTION</b></th>
461 * <td>bt_socket_set_data_received_cb()</td>
462 * <td>bt_socket_unset_data_received_cb()</td>
463 * <td>bt_socket_data_received_cb()</td>
464 * <td>Used to be notified of received data. </td>
467 * <td>bt_socket_set_l2cap_channel_connection_state_changed_cb()</td>
468 * <td>bt_socket_unset_l2cap_channel_connection_state_changed_cb()</td>
469 * <td>bt_socket_l2cap_channel_connection_state_changed_cb()</td>
470 * <td>Used to be notified when the state of connection changes. </td>
475 * Please refer Bluetooth Tutorial if you want to get more detailed usages and information of this api.
479 * @defgroup CAPI_NETWORK_BLUETOOTH_OPP_MODULE Bluetooth OPP
480 * @brief Bluetooth OPP(Object Push Profile) API provides functions for exchanging objects such as pictures.
481 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
483 * @section CAPI_NETWORK_BLUETOOTH_OPP_MODULE_HEADER Required Header
484 * \#include <bluetooth.h>
486 * @section CAPI_NETWORK_BLUETOOTH_OPP_MODULE_OVERVIEW Overview
487 * OPP profile let users exchange objects between two devices.
492 * @defgroup CAPI_NETWORK_BLUETOOTH_OPP_SERVER_MODULE Bluetooth OPP Server
493 * @brief Bluetooth OPP(Object Push Profile) Server API provides functions for accepting objects such as pictures.
494 * @ingroup CAPI_NETWORK_BLUETOOTH_OPP_MODULE
496 * @section CAPI_NETWORK_BLUETOOTH_OPP_SERVER_MODULE_HEADER Required Header
497 * \#include <bluetooth.h>
499 * @section CAPI_NETWORK_BLUETOOTH_OPP_SERVER_MODULE_OVERVIEW Overview
500 * This is OPP server APIs.
502 * @section CAPI_NETWORK_BLUETOOTH_OPP_SERVER_MODULE_FEATURE Related Features
503 * This API is related with the following features:\n
504 * - %http://tizen.org/feature/network.bluetooth.opp\n
506 * It is recommended to design feature related codes in your application for reliability.\n
508 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
510 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
512 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
517 * @defgroup CAPI_NETWORK_BLUETOOTH_OPP_CLIENT_MODULE Bluetooth OPP Client
518 * @brief Bluetooth OPP(Object Push Profile) Client API provides functions for pushing objects such as pictures.
519 * @ingroup CAPI_NETWORK_BLUETOOTH_OPP_MODULE
521 * @section CAPI_NETWORK_BLUETOOTH_OPP_CLIENT_MODULE_HEADER Required Header
522 * \#include <bluetooth.h>
524 * @section CAPI_NETWORK_BLUETOOTH_OPP_CLIENT_MODULE_OVERVIEW Overview
525 * This is OPP Client APIs.
527 * @section CAPI_NETWORK_BLUETOOTH_OPP_CLIENT_MODULE_FEATURE Related Features
528 * This API is related with the following features:\n
529 * - %http://tizen.org/feature/network.bluetooth.opp\n
531 * It is recommended to design feature related codes in your application for reliability.\n
533 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
535 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
537 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
543 * @defgroup CAPI_NETWORK_BLUETOOTH_PAN_MODULE Bluetooth PAN
544 * @brief Bluetooth PAN(Personal Area Networking) API provides functions for connecting to a higher level network and the Internet.
545 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
547 * @section CAPI_NETWORK_BLUETOOTH_PAN_MODULE_OVERVIEW Overview
548 * The PAN Profile describe how two or more Bluetooth enabled devices can form an ad-hoc network and how the same mechanism can be
549 * used to access a remote network through a network access point. But this API only supports network access point service.
551 * @section CAPI_NETWORK_BLUETOOTH_PAN_MODULE_FEATURE Related Features
552 * This API is related with the following features:\n
553 * - %http://tizen.org/feature/network.tethering.bluetooth\n
555 * It is recommended to design feature related codes in your application for reliability.\n
557 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE,thereby controlling the procedure of your application.\n
559 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
561 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
567 * @defgroup CAPI_NETWORK_BLUETOOTH_PAN_NAP_MODULE Bluetooth NAP
568 * @brief Bluetooth NAP(Network Access Point) API provides functions for an Ethernet bridge to support network services.
569 * @ingroup CAPI_NETWORK_BLUETOOTH_PAN_MODULE
571 * @section CAPI_NETWORK_BLUETOOTH_PAN_NAP_MODULE_HEADER Required Header
572 * \#include <bluetooth.h>
574 * @section CAPI_NETWORK_BLUETOOTH_PAN_NAP_MODULE_OVERVIEW Overview
575 * A Bluetooth device that supports the NAP service is a Bluetooth device that provides some of the features of an Ethernet bridge to support network services.
577 * @section CAPI_NETWORK_BLUETOOTH_PAN_NAP_MODULE_FEATURE Related Features
578 * This API is related with the following features:\n
579 * - %http://tizen.org/feature/network.tethering.bluetooth\n
581 * It is recommended to design feature related codes in your application for reliability.\n
583 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
585 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
587 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
593 * @defgroup CAPI_NETWORK_BLUETOOTH_PAN_PANU_MODULE Bluetooth PANU
594 * @brief Bluetooth PANU(Personal Area Networking User) API provides functions for client of both the NAP(Network Access Point).
595 * @ingroup CAPI_NETWORK_BLUETOOTH_PAN_MODULE
597 * @section CAPI_NETWORK_BLUETOOTH_PAN_PANU_MODULE_HEADER Required Header
598 * \#include <bluetooth.h>
600 * @section CAPI_NETWORK_BLUETOOTH_PAN_PANU_MODULE_OVERVIEW Overview
601 * In PAN Profile, PANU can uses either the NAP or GN service, but this API only supports NAP service.
603 * @section CAPI_NETWORK_BLUETOOTH_PAN_PANU_MODULE_FEATURE Related Features
604 * This API is related with the following features:\n
605 * - %http://tizen.org/feature/network.tethering.bluetooth\n
607 * It is recommended to design feature related codes in your application for reliability.\n
609 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
611 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
613 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
619 * @defgroup CAPI_NETWORK_BLUETOOTH_HID_MODULE Bluetooth HID
620 * @brief Bluetooth HID(Human Interface Device) API provides functions for connecting to Bluetooth HID such as keyboards and mouse.
621 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
623 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_HEADER Required Header
624 * \#include <bluetooth.h>
626 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_OVERVIEW Overview
627 * In HID Profile, there are two roles - @a Host and @a Device.
628 * The @a Host is a device that uses or requests the services of a HID. The @a Device is a device that provides the service of human data input and output to and from the @a Host.
629 * This API only supports @a Host role.
631 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_FEATURE Related Features
632 * This API is related with the following features:\n
633 * - %http://tizen.org/feature/network.bluetooth.hid\n
635 * It is recommended to design feature related codes in your application for reliability.\n
637 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
639 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
641 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
647 * @defgroup CAPI_NETWORK_BLUETOOTH_HID_MODULE Bluetooth HID
648 * @brief Bluetooth HID(Human Interface Device) API provides functions for connecting to Bluetooth HID such as keyboards and mouse.
649 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
651 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_HEADER Required Header
652 * \#include <bluetooth.h>
654 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_OVERVIEW Overview
655 * In HID Profile, there are two roles - @a Host and @a Device.
656 * The @a Host is a device that uses or requests the services of a HID. The @a Device is a device that provides the service of human data input and output to and from th
658 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_FEATURE Related Features
659 * This API is related with the following features:\n
660 * - %http://tizen.org/feature/network.bluetooth.hid\n
661 * - %http://tizen.org/feature/network.bluetooth.hid_device\n
663 * It is recommended to design feature related codes in your application for reliability.\n
665 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application
667 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK
669 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
676 * @defgroup CAPI_NETWORK_BLUETOOTH_HID_HOST_MODULE Bluetooth HID Host
677 * @brief Bluetooth HID(Human Interface Device) API provides functions for connecting to Bluetooth HID such as keyboards and mouse.
678 * @ingroup CAPI_NETWORK_BLUETOOTH_HID_MODULE
680 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_HEADER Required Header
681 * \#include <bluetooth.h>
683 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_OVERVIEW Overview
684 * In HID Profile, there are two roles - @a Host and @a Device.
685 * The @a Host is a device that uses or requests the services of a HID. The @a Device is a device that provides the service of human data input and output to and from th
686 * This API only supports @a Host role.
688 * @section CAPI_NETWORK_BLUETOOTH_HID_MODULE_FEATURE Related Features
689 * This API is related with the following features:\n
690 * - %http://tizen.org/feature/network.bluetooth.hid\n
692 * It is recommended to design feature related codes in your application for reliability.\n
694 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
696 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
698 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
704 * @defgroup CAPI_NETWORK_BLUETOOTH_HID_DEVICE_MODULE Bluetooth HID Device
705 * @brief The Bluetooth HID (Human Interface Device) API provides functions for connecting Bluetooth HID such as keyboards and mice.
706 * @ingroup CAPI_NETWORK_BLUETOOTH_HID_MODULE
708 * @section CAPI_NETWORK_BLUETOOTH_HID_DEVICE_MODULE_HEADER Required Header
709 * \#include <bluetooth.h>
711 * @section CAPI_NETWORK_BLUETOOTH_HID_DEVICE_MODULE_OVERVIEW Overview
712 * In HID Profile, there are two roles - @a Host and @a Device.
713 * The @a Host is a device that uses or requests the services of a HID. The @a Device is a device that provides the service of human data input and output to and from the @a Host.
714 * This API supports the @a Device role.
716 * @section CAPI_NETWORK_BLUETOOTH_HID_DEVICE_MODULE_FEATURE Related Features
717 * This API is related to the following features:\n
718 * - %http://tizen.org/feature/network.bluetooth.hid_device\n
720 * It is recommended to use features in your application for reliability.\n
722 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling your application's actions.\n
724 * To ensure your application runs only on devices with the required features, please declare the features in your manifest file using the manifest editor in the SDK.\n
726 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
732 * @defgroup CAPI_NETWORK_BLUETOOTH_AUDIO_MODULE Bluetooth Audio
733 * @brief Bluetooth Audio API provides functions for connecting to Bluetooth audio devices such as headset, hand-free and headphone.
734 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
736 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_MODULE_HEADER Required Header
737 * \#include <bluetooth.h>
739 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_MODULE_OVERVIEW Overview
740 * This API supports the HFP(Hands-Free Profile), HSP(Headset Profile) and A2DP(Advanced Audio Distribution Profile).
742 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_MODULE_FEATURE Related Features
743 * This API is related with the following features:\n
744 * - %http://tizen.org/feature/network.bluetooth.audio.call\n
745 * - %http://tizen.org/feature/network.bluetooth.audio.media\n
747 * It is recommended to design feature related codes in your application for reliability.\n
749 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
751 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
753 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
759 * @defgroup CAPI_NETWORK_BLUETOOTH_AUDIO_AG_MODULE Bluetooth AG
760 * @brief Bluetooth AG(Audio Gateway) API provides functions for controlling the remote audio device.
761 * @ingroup CAPI_NETWORK_BLUETOOTH_AUDIO_MODULE
763 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_MODULE_HEADER Required Header
764 * \#include <bluetooth.h>
766 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_MODULE_OVERVIEW Overview
767 * This API supports the @a Audio @a Gateway role in HSP and HFP.
768 * Audio Gateway is the device that is the gateway of the audio, both for input and output, typically a mobile phone or PC.
770 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_MODULE_FEATURE Related Features
771 * This API is related with the following features:\n
772 * - %http://tizen.org/feature/network.bluetooth.audio.call\n
773 * - %http://tizen.org/feature/network.bluetooth.audio.media\n
775 * It is recommended to design feature related codes in your application for reliability.\n
777 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
779 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
781 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
787 * @defgroup CAPI_NETWORK_BLUETOOTH_AUDIO_AG_CALL_MODULE Call List
788 * @brief Bluetooth AG(Audio Gateway) API provides functions for managing the handler of call list.
789 * @ingroup CAPI_NETWORK_BLUETOOTH_AUDIO_AG_MODULE
791 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_CALL_MODULE_HEADER Required Header
792 * \#include <bluetooth.h>
794 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_CALL_OVERVIEW Overview
795 * This set of functions is used for managing the handler of call list.
796 * This handler is used for notifying the call list to the remote bluetooth device which supports HFP(Hands-Free Profile).
798 * @section CAPI_NETWORK_BLUETOOTH_AUDIO_AG_CALL_MODULE_FEATURE Related Features
799 * This API is related with the following features:\n
800 * - %http://tizen.org/feature/network.bluetooth.audio.call\n
801 * - %http://tizen.org/feature/network.bluetooth.audio.media\n
803 * It is recommended to design feature related codes in your application for reliability.\n
805 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
807 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
809 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
814 * @defgroup CAPI_NETWORK_BLUETOOTH_AVRCP_MODULE Bluetooth AVRCP
815 * @brief Bluetooth AVRCP(Audio/Video Remote Control Profile) API provides functions for notifying the change of target device to the control device(@a Target role) and functions for controlling the remote device(@a Controller role).
816 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
818 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_MODULE_HEADER Required Header
819 * \#include <bluetooth.h>
821 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_MODULE_OVERVIEW Overview
822 * AVRCP profile let users send AV control signals and information between two devices.
827 * @defgroup CAPI_NETWORK_BLUETOOTH_AVRCP_TARGET_MODULE Bluetooth AVRCP Target
828 * @brief Bluetooth AVRCP(Audio/Video Remote Control Profile) Target API provides functions for notifying the change of target device to the control device.
829 * @ingroup CAPI_NETWORK_BLUETOOTH_AVRCP_MODULE
831 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_TARGET_MODULE_HEADER Required Header
832 * \#include <bluetooth.h>
834 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_TARGET_MODULE_OVERVIEW Overview
835 * This API supports the @a Target role in AVRCP spec.
836 * The @a Target is the device whose characteristics are being altered.
837 * In a "walkman" type media player scenario, the @a Control device may be a headset that allows tracks to be skipped and the @a Target device would be the actual medial player.
839 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_TARGET_MODULE_FEATURE Related Features
840 * This API is related with the following features:\n
841 * - %http://tizen.org/feature/network.bluetooth.audio.media\n
843 * It is recommended to design feature related codes in your application for reliability.\n
845 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
847 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
849 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
854 * @defgroup CAPI_NETWORK_BLUETOOTH_AVRCP_CONTROL_MODULE Bluetooth AVRCP Controller
855 * @brief Bluetooth AVRCP(Audio/Video Remote Control Profile) Control API provides functions for controlling the remote device.
856 * @ingroup CAPI_NETWORK_BLUETOOTH_AVRCP_MODULE
858 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_CONTROL_MODULE_HEADER Required Header
859 * \#include <bluetooth.h>
861 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_CONTROL_MODULE_OVERVIEW Overview
862 * This API supports the @a Controller role in the AVRCP spec.
863 * In a "walkman" type media player scenario, the @a Control device may be a headset that allows tracks to be skipped and the @a Target device would be the actual medial player.
865 * @section CAPI_NETWORK_BLUETOOTH_AVRCP_CONTROL_MODULE_FEATURE Related Features
866 * This API is related with the following features:\n
867 * - %http://tizen.org/feature/network.bluetooth.audio.controller\n
869 * It is recommended to create application with regard to features, to increase reliability.\n
871 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
873 * To ensure your application is only running on a device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
875 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
880 * @defgroup CAPI_NETWORK_BLUETOOTH_HDP_MODULE Bluetooth HDP
881 * @brief Bluetooth HDP(Health Device Profile) API provides functions for managing connections to health devices and exchanging data.
882 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
884 * @section CAPI_NETWORK_BLUETOOTH_HDP_MODULE_HEADER Required Header
885 * \#include <bluetooth.h>
887 * @section CAPI_NETWORK_BLUETOOTH_HDP_MODULE_OVERVIEW Overview
888 * The @a Source is a transmitter of application data that is to be transferred to a @a Sink. The @a Sink is a receiver of application data delivered from a @a Source.
889 * This API supports the @a Sink role in HDP spec.
891 * @section CAPI_NETWORK_BLUETOOTH_HDP_MODULE_FEATURE Related Features
892 * This API is related with the following features:\n
893 * - %http://tizen.org/feature/network.bluetooth.health\n
895 * It is recommended to design feature related codes in your application for reliability.\n
897 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
899 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
901 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
906 * @defgroup CAPI_NETWORK_BLUETOOTH_GATT_MODULE Bluetooth GATT
907 * @brief Bluetooth GATT (Generic Attribute Profile) API provides common functions for GATT client and GATT server.
908 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
910 * @section CAPI_NETWORK_BLUETOOTH_GATT_MODULE_HEADER Required Header
911 * \#include <bluetooth.h>
913 * @section CAPI_NETWORK_BLUETOOTH_GATT_MODULE_OVERVIEW Overview
914 * Two roles are defined for devices that implement GATT.
915 * The @a Server is the device that accepts incoming commands and requests from the client and sends responses, indications and notifications to a client.
916 * The @a Client is the device that initiates commands and requests towards the server and can receive responses, indications and notifications sent by the server.
917 * This API supports both @a Server role and @a Client role in GATT. \n
918 * Bluetooth stack architecture has been changed. Thus, GATT APIs defined in Tizen 2.3 are deprecated and new GATT client APIs are defined.
920 * @section CAPI_NETWORK_BLUETOOTH_GATT_MODULE_FEATURE Related Features
921 * This API is related with the following features:\n
922 * - %http://tizen.org/feature/network.bluetooth.le.gatt.server\n
923 * - %http://tizen.org/feature/network.bluetooth.le.gatt.client\n
925 * It is recommended to design feature related codes in your application for reliability.\n
927 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
929 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
931 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
936 * @defgroup CAPI_NETWORK_BLUETOOTH_GATT_SERVER_MODULE Bluetooth GATT Server
937 * @brief Bluetooth GATT (Generic Attribute Profile) Server API provides functions for modifying attributes and registering services, characteristics and descriptors.
938 * @ingroup CAPI_NETWORK_BLUETOOTH_GATT_MODULE
940 * @section CAPI_NETWORK_BLUETOOTH_GATT_SERVER_MODULE_HEADER Required Header
941 * \#include <bluetooth.h>
943 * @section CAPI_NETWORK_BLUETOOTH_GATT_SERVER_MODULE_OVERVIEW Overview
944 * Two roles are defined for devices that implement GATT.
945 * The @a Server is the device that accepts incoming commands and requests from a client and sends responses, indications and notifications to the client.
946 * The @a Client is the device that initiates commands and requests towards a server and can receive responses, indications and notifications sent by the server.
948 * @section CAPI_NETWORK_BLUETOOTH_GATT_SERVER_MODULE_FEATURE Related Features
949 * This API supports both @a Server role in GATT. \n
950 * This API is related with the following features:\n
951 * - %http://tizen.org/feature/network.bluetooth.le.gatt.server\n
953 * It is recommended to create an application with regard to features, to increase reliability.\n
955 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
957 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
959 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
964 * @defgroup CAPI_NETWORK_BLUETOOTH_GATT_CLIENT_MODULE Bluetooth GATT Client
965 * @brief Bluetooth GATT (Generic Attribute Profile) Client API provides functions for discovering attributes and registering services, characteristics and descriptors of the remote device.
966 * @ingroup CAPI_NETWORK_BLUETOOTH_GATT_MODULE
968 * @section CAPI_NETWORK_BLUETOOTH_GATT_CLIENT_MODULE_HEADER Required Header
969 * \#include <bluetooth.h>
971 * @section CAPI_NETWORK_BLUETOOTH_GATT_CLIENT_MODULE_OVERVIEW Overview
972 * Two roles are defined for devices that implement GATT.
973 * The @a Server is the device that accepts incoming commands and requests from a client and sends responses, indications and notifications to the client.
974 * The @a Client is the device that initiates commands and requests towards a server and can receive responses, indications and notifications sent by the server.
976 * @section CAPI_NETWORK_BLUETOOTH_GATT_CLIENT_MODULE_FEATURE Related Features
977 * This API supports both @a Client role in GATT. \n
978 * This API is related with the following features:\n
979 * - %http://tizen.org/feature/network.bluetooth.le.gatt.client\n
981 * It is recommended to create your application with regard to features, to increase reliability.\n
983 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, and control your application's actions accordingly.\n
985 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
987 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
992 * @defgroup CAPI_NETWORK_BLUETOOTH_IPSP_MODULE Bluetooth IPSP
993 * @brief Bluetooth IPSP(Internet Protocol Support Profile) API provides functions for supporting of exchanging IPv6 packets between devices over the BLE transport.
994 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
996 * @section CAPI_NETWORK_BLUETOOTH_IPSP_MODULE_HEADER Required Header
997 * \#include <bluetooth.h>
999 * @section CAPI_NETWORK_BLUETOOTH_IPSP_MODULE_OVERVIEW Overview
1000 * Two roles are defined for devices that implement IPSP.
1001 * The @a Router is used for devices that can route IPv6 packets.
1002 * The @a Node is used for devices that can originate or consume IPv6 application packets.
1004 * @section CAPI_NETWORK_BLUETOOTH_IPSP_MODULE_FEATURE Related Features
1005 * This API is related with the following features:\n
1006 * - %http://tizen.org/feature/network.bluetooth.le.ipsp\n
1008 * It is recommended to design feature related codes in your application for reliability.\n
1010 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling the procedure of your application.\n
1012 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
1014 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
1020 * @defgroup CAPI_NETWORK_BLUETOOTH_PBAP_MODULE Bluetooth PBAP
1021 * @brief Bluetooth PBAP (Phone Book Access Profile) API provides functions for managing connections to a phone book server and retrieving phone book data.
1022 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
1024 * @section CAPI_NETWORK_BLUETOOTH_PBAP_MODULE_HEADER Required Header
1025 * \#include <bluetooth.h>
1027 * @section CAPI_NETWORK_BLUETOOTH_PBAP_MODULE_OVERVIEW Overview
1028 * The PBAP involves two roles, @a Server and @a Client.
1029 * The @a Server is a device that has phone book data. The @a Client is a device that requests the phone book data from the @a Server.
1030 * This API only supports @a Client role.
1032 * @section CAPI_NETWORK_BLUETOOTH_PBAP_MODULE_FEATURE Related Features
1033 * This API is related to the following features:\n
1034 * - %http://tizen.org/feature/network.bluetooth.phonebook.client\n
1036 * It is recommended to use features in your application for reliability.\n
1038 * You can check if a device supports features related to this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, thereby controlling your application's actions.\n
1040 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
1042 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
1048 * @defgroup CAPI_NETWORK_BLUETOOTH_OOB_MODULE Bluetooth OOB
1049 * @brief Bluetooth OOB (Out of Band) API provides functions for exchanging some information used in the pairing process.
1050 * @ingroup CAPI_NETWORK_BLUETOOTH_MODULE
1052 * @section CAPI_NETWORK_BLUETOOTH_OOB_MODULE_HEADER Required Header
1053 * \#include <bluetooth.h>
1055 * @section CAPI_NETWORK_BLUETOOTH_OOB_MODULE_OVERVIEW Overview
1056 * This set of functions is used for exchanging the hash key and randomizer.
1057 * This API uses an external means of communication, such as near-field communication (NFC) to exchange some information used in the pairing process.
1059 * @section CAPI_NETWORK_BLUETOOTH_HDP_MODULE_FEATURE Related Features
1060 * This API is related with the following features:\n
1061 * - %http://tizen.org/feature/network.bluetooth.oob\n
1063 * It is recommended to use features in your application for reliability.\n
1065 * You can check if a device supports the related features for this API by using @ref CAPI_SYSTEM_SYSTEM_INFO_MODULE, and control your application's actions accordingly.\n
1067 * To ensure your application is only running on the device with specific features, please define the features in your manifest file using the manifest editor in the SDK.\n
1069 * More details on featuring your application can be found from <a href="https://docs.tizen.org/application/tizen-studio/native-tools/manifest-text-editor#feature-element"><b>Feature Element</b>.</a>
1073 #endif /* __TIZEN_NETWORK_BLUETOOTH_DOC_H__ */