This chapter covers Bluetooth profiles and versions, a key topic for the CompTIA A+ 220-1101 exam under Mobile Devices (Objective 1.3). Understanding Bluetooth is essential for troubleshooting connectivity issues with peripherals like mice, keyboards, headsets, and smartphones. Expect approximately 5-10% of exam questions to touch on wireless technologies, with Bluetooth being a significant subset. This chapter will equip you with the technical details needed to identify Bluetooth versions, their speeds, and the common profiles used in mobile devices.
Jump to a section
Imagine two people meeting at a secure facility. They must perform a specific secret handshake to prove they are authorized. First, one person extends their hand (inquiry and paging). The other sees the hand and responds with a unique gesture (device address and clock). They then exchange a secret code word (PIN or passkey) to confirm identity. Once the handshake is complete, they agree on a shared secret phrase (link key) that they will use for all future communications. Now, when they meet again, they just need to recall the secret phrase without repeating the full handshake (bonding). Each time they talk, they use a temporary code based on the shared secret (encryption key) to ensure no one else can listen. This mirrors Bluetooth pairing: devices discover each other, authenticate using a PIN or numeric comparison, generate a link key stored for future connections, and then use encryption keys for secure data transfer. The handshake ensures that only trusted devices can communicate, just as Bluetooth's pairing process prevents unauthorized access.
What is Bluetooth?
Bluetooth is a short-range wireless communication technology operating in the 2.4 GHz ISM band (2.400-2.4835 GHz). It uses frequency-hopping spread spectrum (FHSS) to avoid interference, hopping across 79 channels (40 in Bluetooth 4.0+ Low Energy) at a rate of 1600 hops per second. The technology is defined by the Bluetooth Special Interest Group (SIG) and is backward compatible across versions.
Bluetooth Versions and Their Key Differences
Bluetooth versions are numbered 1.x through 5.x, with major leaps in speed, range, and power consumption. For the 220-1101 exam, focus on versions 4.0, 4.2, 5.0, and 5.1, as these are common in modern devices.
Bluetooth 4.0 (2010): Introduced Bluetooth Low Energy (BLE) for low-power applications. Classic Bluetooth (BR/EDR) remains for high-throughput uses. BLE uses 40 channels (3 advertising, 37 data) and consumes significantly less power. Data rates: Classic up to 3 Mbps (EDR), BLE up to 1 Mbps.
Bluetooth 4.2 (2014): Improved data capacity for BLE (up to 251 bytes per packet) and enhanced privacy with LE Secure Connections. Also introduced Internet Protocol Support Profile (IPSP) for IPv6 over BLE.
Bluetooth 5.0 (2016): Doubled BLE speed to 2 Mbps, increased range up to 4x (via coded PHY), and introduced Advertising Extensions for more efficient broadcasting. Classic Bluetooth unchanged.
Bluetooth 5.1 (2019): Added direction finding (Angle of Arrival/Departure) for precise location tracking. Also improved advertising and GATT caching.
Bluetooth Profiles: What They Are and Why They Matter
A Bluetooth profile is a specification that defines how a device uses Bluetooth to perform a specific function. Profiles ensure interoperability between devices from different manufacturers. Each profile defines required protocols, procedures, and features. Devices must support the same profile to communicate.
Common Bluetooth Profiles for A+ 220-1101
HFP (Hands-Free Profile): Used for hands-free calling in cars and headsets. Requires SCO (Synchronous Connection-Oriented) link for audio. Version 1.6 supports wideband speech (HD Voice).
A2DP (Advanced Audio Distribution Profile): For streaming high-quality stereo audio from a source (phone) to a sink (headset/speaker). Uses AVDTP (Audio/Video Distribution Transport Protocol). Supports codecs like SBC (mandatory), AAC, aptX, LDAC.
AVRCP (Audio/Video Remote Control Profile): Allows remote control of media playback (play, pause, skip, volume). Often paired with A2DP. Version 1.6 supports absolute volume control.
HID (Human Interface Device Profile): For keyboards, mice, game controllers. Low latency and low power. BLE HID (HID over GATT) is common for modern peripherals.
SPP (Serial Port Profile): Emulates a serial cable connection (RS-232). Used for legacy devices like GPS receivers, barcode scanners. Often replaced by BLE GATT-based services.
PAN (Personal Area Network Profile): Enables network connectivity (e.g., Bluetooth tethering). Uses BNEP (Bluetooth Network Encapsulation Protocol).
PBAP (Phone Book Access Profile): Allows access to phone contacts from a car kit. Often used with HFP.
MAP (Message Access Profile): Enables access to SMS and email messages from a car or wearable.
How Bluetooth Pairing and Bonding Work
Pairing is the process of establishing a shared link key. Bonding stores that key for future connections. The classic pairing process involves: 1. Inquiry: Device sends inquiry requests to discover nearby devices. 2. Paging: Initiator pages the target device using its BD_ADDR (Bluetooth Device Address). 3. Authentication: Devices authenticate using a PIN or passkey (legacy pairing) or numeric comparison (Secure Simple Pairing). 4. Link Key Generation: A shared link key is generated and stored. 5. Encryption: Encryption keys are derived from the link key for secure communication.
Secure Simple Pairing (SSP) introduced in Bluetooth 2.1 uses four association models: - Numeric Comparison: Both devices display a six-digit number; user confirms if they match. Resistant to MITM. - Passkey Entry: One device displays a passkey, user enters it on the other. - Just Works: No user interaction; used for headsets, but vulnerable to MITM. - Out of Band (OOB): Uses NFC or other means to exchange information.
Bluetooth Low Energy (BLE) Pairing uses: - Just Works (no MITM protection) - Passkey Entry - Numeric Comparison - OOB
Pairing in BLE generates a Long Term Key (LTK) for encryption.
Bluetooth Security Considerations
Bluetooth has several security features: - Encryption: AES-CCM (in BLE 4.2+) or E0 (classic). - Authentication: Based on link key. - Privacy: BLE uses random resolvable addresses to prevent tracking. - Secure Connections: Mandatory in Bluetooth 4.2+ for BLE, uses ECDH key exchange.
Common vulnerabilities: - Bluejacking: Sending unsolicited messages. - Bluesnarfing: Unauthorized access to data. - Bluebugging: Taking control of a device.
Bluetooth Range and Power Classes
Bluetooth devices are classified by power output: - Class 1: 100 mW, range up to 100 meters. - Class 2: 2.5 mW, range up to 10 meters (most common in mobile devices). - Class 3: 1 mW, range up to 1 meter.
BLE typically operates at Class 2 power levels.
Troubleshooting Bluetooth Issues
Common issues: - Device not discoverable: Ensure device is in pairing mode; check Bluetooth is enabled. - Pairing fails: Wrong PIN, incompatible profiles, interference. - Audio stuttering: Interference from Wi-Fi (same 2.4 GHz band), distance, obstacles. - Battery drain: BLE devices should have low power; check for constant scanning.
Configuration and Verification Commands
On Windows:
- bluetooth command in PowerShell (limited).
- Device Manager to check Bluetooth adapter properties.
- Control Panel > Devices and Printers.
On Linux:
- hciconfig to list Bluetooth adapters.
- hcitool scan to discover devices.
- bluetoothctl interactive shell for pairing and connection.
On macOS:
System Preferences > Bluetooth.
bluetooth command line tool (limited).
On Android/iOS:
Settings > Bluetooth.
Developer options may show advanced info.
Interaction with Other Technologies
Bluetooth often coexists with Wi-Fi in the 2.4 GHz band. Adaptive Frequency Hopping (AFH) helps avoid interference by marking channels as bad. Bluetooth can also be used for Wi-Fi Direct pairing (Wi-Fi Protected Setup via Bluetooth).
Device Discovery (Inquiry)
The initiator device sends inquiry requests on the inquiry hop sequence (32 channels in classic Bluetooth). Devices in discoverable mode respond with an FHS packet containing their BD_ADDR, clock, and supported features. This process takes 10.24 seconds to scan all 32 channels. In BLE, the scanner listens on three advertising channels (37, 38, 39) for advertising packets from peripherals. The peripheral sends advertising packets at intervals (e.g., 20 ms to 10.24 s). The scanner can request additional data via scan requests.
Connection Establishment (Paging)
After discovery, the initiator pages the target using the target's BD_ADDR and clock estimate from the inquiry. The paging process uses the paging hop sequence and sends ID packets. The target, if in page scan mode, responds with an ID packet, then the initiator sends an FHS packet with its own clock and BD_ADDR. The target responds with an ID packet, and the connection is established as both devices switch to a channel hopping sequence derived from the master's clock. In BLE, the scanner can initiate a connection by sending a CONNECT_REQ packet specifying connection parameters (e.g., connection interval from 7.5 ms to 4 s, latency, supervision timeout).
Pairing and Authentication
Once connected, the devices may initiate pairing. In classic Bluetooth, the initiator sends a pairing request. The authentication method depends on the IO capabilities and security requirements. For SSP with numeric comparison, both devices display a six-digit number; the user confirms they match. For passkey entry, one device displays a passkey, the user enters it on the other. For Just Works, no user interaction. The pairing process generates a link key (128-bit) using ECDH key exchange (Secure Connections) or legacy algorithms. In BLE, pairing generates a Short Term Key (STK) or Long Term Key (LTK) using the pairing algorithm. After authentication, encryption is enabled using the generated key.
Profile Connection and Service Discovery
After encryption is established, the devices perform service discovery. For classic Bluetooth, this uses SDP (Service Discovery Protocol) to list supported profiles and service attributes. For BLE, the Generic Attribute Profile (GATT) is used to discover services (e.g., Battery Service, Heart Rate Service) and characteristics. The client device can then connect to specific profiles. For example, a headset supporting HFP and A2DP will have separate service records. The device can then establish additional L2CAP channels for the specific profile. For HFP, an SCO link is established for audio. For A2DP, a streaming channel is set up using AVDTP.
Data Transfer and Connection Maintenance
Once profiles are connected, data transfer proceeds. For classic Bluetooth, data is sent over ACL (Asynchronous Connection-Less) links for general data, and SCO/eSCO links for isochronous audio. The master controls the channel hopping and timing. The connection is maintained by periodic transmissions; if no data is sent, the link may enter hold or sniff mode to save power. In BLE, data is sent in connection events at the negotiated connection interval. The slave can request a connection parameter update. If the connection is lost (e.g., out of range), the devices may attempt to reconnect using stored bonding information. The supervision timeout (default 20 seconds for BLE) determines when the connection is considered lost.
In an enterprise environment, Bluetooth is commonly used for wireless headsets for call center agents, wireless keyboards and mice for office workers, and for connecting smartphones to car infotainment systems. For example, a company deploys Bluetooth headsets supporting HFP and A2DP for their remote workforce. They need to ensure that the headsets are paired with the company-provided laptops. A common issue is that the headsets might pair but not stream audio due to incorrect profile selection. The IT admin must ensure that the headset and laptop both support the same profile version. For instance, if the headset supports HFP 1.6 but the laptop's Bluetooth stack only supports HFP 1.5, wideband audio may not work. Another scenario is using Bluetooth for file transfer between mobile devices. The admin may need to enable SPP or OBEX profile. In a hospital, Bluetooth medical devices (e.g., blood pressure cuffs) use BLE with specific health profiles (HDP). The IT team must ensure that the BLE devices are properly bonded and that the connection parameters (e.g., connection interval) are set to ensure reliable data transmission without interfering with other equipment. Performance considerations include the number of simultaneous connections (classic Bluetooth supports up to 7 active slaves in a piconet, BLE supports many more but with lower throughput). Interference from Wi-Fi can cause audio dropouts; using Bluetooth 5.0's 2 Mbps PHY can reduce time on air but may reduce range. Misconfiguration often occurs when devices are not in pairing mode, or when the user selects 'Just Works' pairing for sensitive data, exposing the connection to man-in-the-middle attacks. In production, IT should enforce the use of Secure Simple Pairing with numeric comparison or passkey entry for sensitive connections. Also, Bluetooth should be disabled when not in use to prevent unauthorized access.
The 220-1101 exam tests Bluetooth under Objective 1.3: 'Given a scenario, install and configure laptop hardware and components.' Specifically, you need to understand Bluetooth versions and profiles to troubleshoot connectivity issues. The exam will ask about the characteristics of different Bluetooth versions, especially 4.0, 4.2, 5.0, and 5.1. Common wrong answers include: 1) Confusing Bluetooth 4.0 with 5.0 regarding range – some think 4.0 has longer range, but 5.0 can achieve 4x range with coded PHY. 2) Thinking that all Bluetooth profiles work with all versions – actually, some profiles require specific versions (e.g., LE Audio requires Bluetooth 5.2). 3) Believing that Bluetooth and Wi-Fi cannot coexist – they can, using AFH. 4) Assuming that BLE is just a lower-power version of classic Bluetooth – BLE is a completely different protocol stack. The exam loves specific numbers: Bluetooth 4.0 BLE data rate is 1 Mbps, Bluetooth 5.0 BLE data rate is 2 Mbps (or 125 kbps with coded PHY for long range). Range for Class 2 is 10 meters. The number of channels: 79 for classic, 40 for BLE. Also, know that Bluetooth 5.1 introduced direction finding. For profiles, know that A2DP is for high-quality audio, HFP for hands-free calling, HID for input devices, and PAN for networking. The exam will present scenarios like: 'A user's Bluetooth keyboard is not connecting. Which profile is likely not supported?' Answer: HID. Or 'A user wants to stream music from phone to car. Which profiles are needed?' Answer: A2DP and AVRCP. Another common trap: 'Which Bluetooth version introduced Low Energy?' Answer: 4.0, not 5.0. To eliminate wrong answers, focus on the specific feature mentioned: if the question mentions 'low power', think BLE and version 4.0+. If it mentions 'longer range', think Bluetooth 5.0 with coded PHY. If it mentions 'direction finding', think 5.1.
Bluetooth 4.0 introduced Bluetooth Low Energy (BLE) with 1 Mbps data rate.
Bluetooth 5.0 doubled BLE speed to 2 Mbps and increased range up to 4x using coded PHY.
Bluetooth 5.1 added direction finding (AoA/AoD) for location services.
Common profiles: A2DP (audio streaming), HFP (hands-free calling), HID (input devices), PAN (network tethering).
Class 2 Bluetooth has a range of approximately 10 meters (33 feet).
Secure Simple Pairing (SSP) includes Numeric Comparison, Passkey Entry, Just Works, and Out of Band.
Bluetooth uses Adaptive Frequency Hopping (AFH) to avoid interference with Wi-Fi.
BLE uses 40 channels (3 advertising, 37 data) while Classic Bluetooth uses 79 channels.
These come up on the exam all the time. Here's how to tell them apart.
Bluetooth 4.0
Introduced BLE with 1 Mbps data rate
Range up to 100 meters (Class 1) or 10 meters (Class 2)
40 channels (3 advertising, 37 data)
No support for coded PHY or direction finding
Maximum advertising data per packet: 31 bytes
Bluetooth 5.0
BLE data rate up to 2 Mbps (or 125 kbps with coded PHY)
Range up to 4x that of 4.0 with coded PHY (e.g., 400 meters line-of-sight)
Same 40 channels but with Advertising Extensions
Supports coded PHY for long range and direction finding (5.1)
Maximum advertising data per packet: 255 bytes (with extended advertising)
Mistake
Bluetooth 5.0 is five times faster than Bluetooth 4.2.
Correct
Bluetooth 5.0 doubles the BLE data rate from 1 Mbps to 2 Mbps, not five times. The '5' in the version number does not indicate speed.
Mistake
Bluetooth Low Energy (BLE) is just a power-saving mode of classic Bluetooth.
Correct
BLE is a completely different protocol stack with a simpler design optimized for low power consumption. It is not backward compatible with classic Bluetooth.
Mistake
All Bluetooth devices are backward compatible with all previous versions.
Correct
While Bluetooth is designed for backward compatibility, some features may not work if not supported by both devices. For example, a Bluetooth 5.0 device can connect to a 4.0 device but will operate at 4.0 speeds.
Mistake
Bluetooth and Wi-Fi cannot operate simultaneously because they use the same frequency.
Correct
Bluetooth uses Adaptive Frequency Hopping (AFH) to avoid Wi-Fi channels, and many devices support simultaneous operation. Interference can occur but is managed.
Mistake
Bluetooth pairing always requires a PIN or passkey.
Correct
Secure Simple Pairing (SSP) introduced 'Just Works' model which requires no user interaction, though it is less secure. Also, BLE pairing can use 'Just Works' without a passkey.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Bluetooth 5.0 offers double the BLE data rate (2 Mbps vs 1 Mbps), up to 4x the range with coded PHY, and increased advertising capacity (255 bytes vs 31 bytes). It also introduced Advertising Extensions for more efficient broadcasting. However, classic Bluetooth (BR/EDR) remains unchanged. For the exam, remember that 5.0 is backward compatible with 4.0 but features require both devices to support the version.
The Human Interface Device (HID) profile is used for keyboards, mice, game controllers, and other input devices. Modern keyboards often use BLE HID (HID over GATT) for lower power consumption. When troubleshooting, ensure the device supports HID and that the host has the appropriate driver.
Yes, most devices support simultaneous Bluetooth and Wi-Fi operation. Bluetooth uses Adaptive Frequency Hopping (AFH) to avoid channels used by Wi-Fi. However, heavy Wi-Fi traffic can cause interference, leading to reduced Bluetooth range or audio stuttering. Bluetooth 5.0's 2 Mbps PHY reduces time on air, mitigating interference.
Bluetooth range depends on the power class. Class 1 (100 mW) up to 100 meters, Class 2 (2.5 mW) up to 10 meters (most common in mobile devices), Class 3 (1 mW) up to 1 meter. Bluetooth 5.0 with coded PHY can achieve up to 4x the range of 4.0, potentially over 400 meters line-of-sight for Class 1 devices.
Pairing involves discovery, connection, authentication, and key generation. Devices first discover each other via inquiry (classic) or advertising (BLE). Then they connect and authenticate using a method like numeric comparison or passkey entry. A link key (classic) or LTK (BLE) is generated and stored for future connections (bonding). After pairing, encryption is enabled.
Bluetooth Classic (BR/EDR) is designed for continuous data streaming (e.g., audio) with higher power consumption. BLE is designed for low-power, intermittent data transmission (e.g., sensor readings). They use different protocol stacks and are not directly compatible. Many devices support both (dual-mode). BLE was introduced in Bluetooth 4.0.
Bluetooth 5.1 introduced direction finding using Angle of Arrival (AoA) and Angle of Departure (AoD). This allows for precise location tracking (e.g., indoor navigation). It requires specific hardware (antenna arrays) and is not supported by all Bluetooth 5.1 devices.
You've just covered Bluetooth Profiles and Versions — now see how well it sticks with free 220-1101 practice questions. Full explanations included, no account needed.
Done with this chapter?