How does Bluetooth technology work?

How does a measurement or audio reach another device without a cable?
Hello, Bluetooth enables devices to communicate using shared radio rules and compatible data formats. An antenna does not simply send temperature or sound: the information is converted into digital packets. The receiver decodes them and delivers data to the application. The basic process is discovering a device, establishing an appropriate communication path and transferring data according to defined rules. Not every application requires internet access, pairing or a continuous connection.
The radio layer: hopping channels is not how the data is encoded
Bluetooth uses radio frequencies in the 2.4 GHz ISM band. Licence-exempt operation does not exempt devices from power limits and technical requirements. The transmitter encodes digital information by changing properties of a carrier wave, a process called modulation. LE and Classic Basic Rate use GFSK; Classic EDR also uses different modulation schemes. The receiver extracts these changes from the radio wave to recover the bits.
First distinguish Classic from LE
Bluetooth Classic, or BR/EDR, is common in traditional audio and data links. Bluetooth LE supports applications ranging from sensors and keyboards to positioning and LE Audio. LE's low energy operation is particularly associated with short activity periods and sleep. Classic uses 79 channels spaced 1 MHz apart; LE uses 40 channels spaced 2 MHz apart. These are different radio arrangements: an LE-only device cannot communicate directly with a Classic-only receiver.
How do devices discover each other?
Classic uses inquiry for initial discovery and paging to establish a connection. Previously known devices need not repeat initial discovery every time. LE devices send advertising packets, while other devices listen by scanning. Advertisements can contain a name, service information or short measurements. Not every advertisement accepts connections: a broadcast-only beacon behaves differently from a connectable sensor.
LE channels 37, 38 and 39 are the primary advertising channels. Legacy advertisements use the selected primary channels. Extended advertising can carry additional information on secondary channels, so not all LE broadcasts are confined to three channels. Device pairing is a separate security procedure: appearing in a scan does not mean a device is paired.
What do devices agree when establishing a connection?
In a typical LE connection, the central discovers the advertisement and initiates a connection; the peripheral accepts it. Timing, the channel map and connection-identifying information let both sides know when and on which channel to communicate. Older documents may use master/slave terminology. Central does not mean transmit-only, and peripheral does not mean receive-only: the link can carry data in both directions.
Pairing, bonding and encryption
Pairing establishes or agrees security keys. Bonding stores appropriate keys for later connections. The pairing method depends on capabilities such as displays and keyboards; not every product shows matching numbers on two screens. Bluetooth security requires consideration of authentication and access permissions as well as encryption. Frequency hopping is not a substitute for encryption.
How does frequency hopping help the connection?
Instead of sending every data packet on one channel, the devices follow defined channel-selection rules. Adaptive frequency hopping can reduce use of problematic channels through the relevant mechanisms. This helps coexistence with Wi-Fi, but does not eliminate every collision. The Classic connection-state maximum of 1,600 hops per second must not be applied to every Bluetooth mode. LE uses different timing and channel selection; primary advertising is also different from hopping within a data connection.
How does the application find the data?
Many LE applications use the GATT data model. A service groups related functions; a characteristic represents a measurement, setting or status value. A UUID identifies the type of an item. The GATT server exposes the database, while the client initiates operations such as reads and writes. These roles are different from central/peripheral; a device can be both a client and a server.
For example, a custom IoT sensor might encode 23.50 °C as the number 2350. The receiving application needs the defined scale, numeric type, byte order and unit; Bluetooth does not infer the meaning automatically. A manufacturer's BLE UART service is not automatically the same as Classic SPP or a standard COM port. Radio compatibility and application-protocol compatibility are separate requirements.
Packet checks and application acknowledgements are different
Packets include error checking, with link-layer acknowledgements and retransmission mechanisms for applicable packets. In GATT, a read retrieves a value and a write changes one. A notification does not require an ATT confirmation for every update, while an indication does. Even a protocol acknowledgement does not prove that a machine physically executed a command. Control applications should separately define result status or application-level acknowledgement.
How do headphones carry audio?
Classic audio uses profiles such as A2DP and supported codecs; calls can use different profiles and transport arrangements, such as HFP. LE Audio uses separate components including isochronous transport and LC3. Reading a sensor's GATT characteristic is different from streaming audio to headphones. The Bluetooth version alone does not guarantee a codec, audio quality, microphone behaviour or LE Audio support.
How can the radio sleep while the connection remains active?
LE devices can exchange packets during scheduled connection events and enter suitable sleep states between them. The connection interval sets event spacing, peripheral latency allows eligible events to be skipped, and the supervision timeout determines when a link is considered lost. These settings affect energy consumption. Longer sleep can save battery energy, but must be balanced against responsiveness and data capacity.
Why do speed and range differ from the figures on the box?
Terms such as LE 1M and LE 2M describe physical-layer rates. Application throughput depends on headers, ATT MTU, link-layer data length, timing and retransmissions. With an ATT MTU of 23 bytes, a standard notification carries up to 20 bytes of value data; larger MTUs are possible, so this is not a universal limit. When comparing with Wi-Fi, distinguish PHY rate from usable throughput.
Actual range depends on transmit power, antennas, receiver sensitivity and the environment. Metal cabinets, the human body and busy radio traffic can affect a link. Options such as LE Coded PHY can improve operation at weaker signal levels in exchange for a lower data rate. Higher PHY speed, greater range and lower energy use are not guaranteed by the same setting.
The seven-device limit, piconets and mesh
A Classic piconet can contain one central and up to seven active peripherals. This does not promise simultaneous audio to seven headphones, nor impose a seven-device limit on every Bluetooth product. LE connection capacity depends on hardware, software and available airtime. Traffic also matters in networks with multiple devices. A scatternet describes relationships involving multiple piconets; Bluetooth Mesh requires separate networking layers and roles.
Industrial example: from a sensor to a PLC display
Suppose a sensor measures once a second and sends updates to a gateway over BLE. The gateway discovers the service, establishes security if needed, enables notifications and decodes the agreed format. It can then translate the value into a protocol understood by the PLC. Bluetooth does not automatically become Modbus or Ethernet. Gateway software handles mapping to the Ethernet side; the RF link is only one part of the chain.
Define measurement timestamps, sequence numbers and a stale-data timeout where appropriate. A last-known value remaining on screen after disconnection does not mean a fresh measurement arrived. For industrial remote control and other remote control applications, disconnection behaviour and applicable standards require separate consideration. This is a communication architecture example, not a complete safety-function design.
Visible but not working: where should troubleshooting start?
Separate Bluetooth connection problems into stages: is the device advertising, is the radio option supported, does connection succeed, is security completed, is the correct service found, and is the data decoded correctly? Then check battery voltage, antenna placement and Wi-Fi-related environmental problems. Discoverability, an established connection and correct application data are three different success criteria.
Related topics
Bluetooth fundamentals and performance: What is Bluetooth?, Bluetooth versions, Bluetooth LE, Range, Power consumption.
Compatibility, security and applications: Device pairing, Data security, Connection troubleshooting, Applications, Bluetooth and health.
Other networks and industrial applications: Bluetooth versus Wi-Fi, What is Wi-Fi?, Internet of Things, Industrial remote control, Remote control overview.
Sources
Bluetooth SIG: Classic and LE radio characteristics
Bluetooth SIG: LE protocol architecture and operation
Bluetooth SIG: Classic piconets, timing and frequency hopping
Texas Instruments: LE advertising and scanning
Texas Instruments: Examining LE connection packets
Nordic Semiconductor: Connection process and events
Nordic Semiconductor: Connection parameters and power consumption
Silicon Labs: GATT server and client roles
Silicon Labs: Acknowledged and unacknowledged GATT operations