1TRANSPORTS 2========== 3 4The Hosts and Controllers communicate over a transport, which is responsible for sending/receiving 5HCI packets. 6Several types of transports are supported: 7 8 * In Process: HCI packets are passed via a function call 9 * [Serial](serial.md): interface with a controller over a serial port (HCI UART, like a development board or serial Bluetooth dongle) 10 * [USB](usb.md): interface with a controller over USB (HCI USB, like a Bluetooth USB dongle) 11 * [UDP](udp.md): packets are sent to a specified host/port and received on a specified port over a UDP socket 12 * [TCP Client](tcp_client.md): a connection to a TCP server is made, after which HCI packets are sent/received over a TCP socket 13 * [TCP Server](tcp_server.md): listens for a TCP client on a specified port. When a client connection is made, HCI packets are sent/received over a TCP socket 14 * [WebSocket Client](ws_client.md): a connection to a WebSocket server is made, after which HCI packets are sent/received over the socket. 15 * [WebSocket Server](ws_server.md): listens for a WebSocket client on a specified port. When a client connection is made, HCI packets are sent/received over the socket. 16 * [PTY](pty.md): a PTY (pseudo terminal) is used to send/receive HCI packets. This is convenient to expose a virtual controller as if it were an HCI UART 17 * [VHCI](vhci.md): used to attach a virtual controller to a Bluetooth stack on platforms that support it. 18 * [HCI Socket](hci_socket.md): an HCI socket, on platforms that support it, to send/receive HCI packets to/from an HCI controller managed by the OS. 19 * [Android Emulator](android_emulator.md): a gRPC connection to an Android emulator is used to setup either an HCI interface to the emulator's "Root Canal" virtual controller, or attach a virtual controller to the Android Bluetooth host stack. 20 * [File](file.md): HCI packets are read/written to a file-like node in the filesystem. 21