Bluetooth Logical Transports : ACL vs. SCO vs. eSCO
By RF Wireless Expert Team
Advertisement
Based on the Bluetooth Core Specification and general Bluetooth architecture, the Bluetooth transport architecture uses Logical Transports to manage how different types of data (e.g. control signals, asynchronous data and synchronous voice) are carried over physical wireless links. Bluetooth supports three primary BR/EDR (Basic Rate / Enhanced Data Rate) logical transports viz. ACL, SCO and eSCO.
ACL (Asynchronous Connection Oriented)
The ACL logical transport is the foundational data link used in Bluetooth for general purpose, best effort data transfer.
- Establishment: An ACL logical transport (the “default ACL”) is automatically created between a Central and a Peripheral whenever a device joins a piconet.
- Traffic Type: It is designed for asynchronous and isochronous framed user data, as well as control signaling (LMP and L2CAP protocols).
- Reliability: It ensures high data integrity by using a 1-bit Automatic Repeat reQuest (ARQ) scheme. If a receiver detects an error using a Cyclic Redundancy Check (CRC), the sender will retransmit the packet until it is successfully acknowledged or a flush timeout expires.
- Bandwidth: It uses unreserved time slots. The piconet Central dynamically schedules ACL packets based on available bandwidth, making it ideal for variable rate data like file transfers, web browsing or control commands.
SCO (Synchronous Connection Oriented)
The SCO logical transport acts like a traditional circuit switched connection, designed specifically for time sensitive, constant rate data streams.
- Traffic Type: It carries unframed, synchronous data. It is predominantly used for standard quality voice data (typically at a constant rate of 64 kb/s).
- Slot Reservation: The Central reserves specific, evenly spaced time slots on the physical channel for SCO transmissions, guaranteeing strict timing and low latency.
- Reliability: Because maintaining strict timing is prioritized over data perfection, SCO does not support retransmissions. If a packet is corrupted by interference, it is simply lost, which might result in a brief crackle in an audio headset but prevents latency buildup.
- Symmetry & Rate: SCO links are strictly symmetric (same bandwidth in both directions) and only operate using Basic Rate (BR) modulation (1 Mbps over the air).
eSCO (Extended Synchronous Connection Oriented)
Introduced in later Bluetooth versions, eSCO is an evolution of SCO that provides greater flexibility, higher bandwidth and improved reliability for synchronous data.
- Traffic Type: Like SCO, it is used for time sensitive isochronous/synchronous data (like high quality voice or audio), but it allows for a wider variety of packet types and data payloads.
- Reliability (Limited Retransmission): Unlike SCO, eSCO features limited retransmission window. If an eSCO packet is lost or corrupted, the devices can attempt to retransmit the packet in the unreserved time slots immediately following the reserved eSCO slots, significantly improving audio quality in noisy RF environments without breaking strict latency requirements.
- Symmetry & Rate: eSCO links can be symmetric or asymmetric (different bandwidths for uplink and downlink). Crucially, eSCO supports Enhanced Data Rate (EDR) modulation (2 Mbps or 3 Mbps), allowing it to carry higher quality audio (like wideband speech) while consuming less over the air time.
Key Difference between ACL vs. SCO vs. eSCO
| Feature | ACL (Asynchronous Connection-Oriented) | SCO (Synchronous Connection-Oriented) | eSCO (Extended Synchronous Connection-Oriented) |
|---|---|---|---|
| Primary Use Case | General data, file transfers, control signals (L2CAP/LMP). | Standard voice calls (e.g., legacy headsets). | High quality voice, wideband speech, robust audio. |
| Traffic Nature | Asynchronous / Best effort. | Synchronous / Constant rate. | Synchronous / Constant rate. |
| Bandwidth Allocation | Dynamically scheduled (unreserved slots). | Circuit-switched (strictly reserved slots). | Circuit-switched (reserved slots + retransmission window). |
| Error Correction / Reliability | High: Uses ARQ (Automatic Repeat Request). Retransmits until acknowledged or flushed. | Low: Unreliable. No retransmissions; lost packets are dropped to maintain strict timing. | Medium: Supports limited retransmissions to balance reliability with low latency. |
| Link Symmetry | Can be highly asymmetric depending on data flow. | Strictly symmetric (equal data rate in both directions). | Can be symmetric or asymmetric. |
| Supported Data Rates | BR (1 Mb/s) and EDR (2 or 3 Mb/s). | BR only (1 Mb/s over the air, 64 kb/s payload). | BR (1 Mb/s) and EDR (2 or 3 Mb/s). |
| Default Piconet Presence | Yes (Default ACL is required to maintain the piconet connection). | No (Created on demand over an existing ACL). | No (Created on demand over an existing ACL). |
References & Further Reading
- Bluetooth SIG : Bluetooth Core Specification Version 6.3, May 5, 2026.
- Bluetooth SIG : Bluetooth Technology Overview
Continue Learning Bluetooth Basic Concepts
- What are new features in Bluetooth 6.3 Version
- Bluetooth GATT Vs. ATT Vs. GAP : Key Comparison
- Bluetooth Service Vs. Characteristic Vs. Descriptor
- Bluetooth pairing Vs. Bonding Phase
- Bluetooth Notifications Vs. Indications
- Bluetooth Channel Sounding Vs. RSSI
- Bluetooth Direction Finding Methods : AoA Vs. AoD
- Bluetooth Error Codes Guide : Meanings, Causes & Fixes
- Bluetooth L2CAP and HCI : Key Differences
Continue Learning Bluetooth Technology
- Bluetooth Basics Tutorial
- Bluetooth Low Energy (BLE) Basics Tutorial
- Bluetooth Protocol Stack & Device State Diagram
- Bluetooth Physical Layer Modules
- Bluetooth MAC Layer Overview
- Bluetooth Channel Frequency List
- Bluetooth Network Security
- Bluetooth Low Energy (BLE) Connection Establishment Procedure
- Bluetooth Profiles: HFP, HSP, A2DP, AVRCP, PBAP & MAP
- Bluetooth Mesh Node Types & Protocol Stack Layer Functions