Exploring Bluetooth Device Testing Methodologies and Techniques

Earlier, we covered product testing for all major domains such as Modbus validation in industrial, displays in consumer domain, UDS in automotive domain, Wi-Fi in consumer domain etc. Bluetooth is also one of the key technologies used in consumer, automotive, medical, and industrial domains. There are several factors in Bluetooth design that may influence overall performance such as antenna design, power supplies, other wireless communications chips, or the final housing. Therefore, it is necessary to test the Bluetooth device to verify its performance and ensure conformance with the Bluetooth Special Interest Group (SIG) standards and regulatory requirements. This is especially important because Bluetooth operates in the unlicensed spectrum and has to work seamlessly with other radio technologies that use the same spectrum. Proper application profile testing and physical level testing are essential to confirm both compliance and functional correctness. Embien's cross-domain embedded services include Bluetooth Low Energy (BLE) solutions for consumer devices covering end-to-end application profile testing and physical level testing.

Bluetooth device testing is governed by regulatory compliance for radio operation in the 2.4 GHz band and compliance with the Bluetooth specification. There are primarily 2 types of Bluetooth interfaces in use — Bluetooth classic and Bluetooth Low Energy. Testers need to know the specific tests to perform for each type as discussed below.

Bluetooth Classic Physical Layer Testing

In Bluetooth classic device, physical layer supports 2 transport schemes (SCO and ACL) to support data transfer. Physical level testing for Bluetooth Classic, also referred to as BR/EDR, can be performed via vendor-specific control interface and used for fully automated tests. The Bluetooth SIG has specified a test mode and interface that should be used to control the Device under test (DUT) during compliance physical level testing. This uses the link management protocol (LMP) to control the DUT over the Bluetooth radio link.

Bluetooth Testing Classic

During physical level testing, the tester and the Device under test (DUT) form a Bluetooth piconet, where the tester acts as the central device and has full control over the test sequence via a control interface using the link management protocol (LMP). The DUT acts as peripheral and is set at the beginning via a DUT-specific local interface in test mode (TM) for testing.

Few test cases that can be run during physical level testing are:

Bluetooth physical level testing items comprise transmitter tests covering transmit power, power density spectrum, spurious emission, and modulation accuracy, as well as receiver tests for sensitivity and blocking performance.

Bluetooth LE Physical Layer Testing

Standalone battery-operated low-power devices are the main use cases for Bluetooth Low Energy (BLE) solutions for consumer devices. Some of the devices that use BLE include home automation systems, fitness trackers, and fleet tracking devices. Physical level testing of Bluetooth Low Energy (BLE) solutions for consumer devices involves RF testing and power consumption validation.

Bluetooth SIG standardized Direct Test Mode (DTM) to test transmitter and receiver with control facilitated test commands — this is the standard protocol for Bluetooth DTM direct test mode protocol testing. This mode enables physical level testing of the Bluetooth LE transmitter and receiver, with control facilitated through a dedicated wired test interface. For the wired interface, two specified options include a USB or RS232 connection to the host control interface (HCI) of the DUT. Bluetooth DTM direct test mode protocol testing is the baseline validation step for any Bluetooth Low Energy (BLE) solutions for consumer devices.

Bluetooth LE Testing

Application Profile Testing

Apart from the above physical level tests, Bluetooth devices are to be validated for application functionality through application profile testing. Classic devices are verified if the profiles being implemented are in conformance with the specifications. For BLE, services and characteristics implementation have to be validated. Application profile testing typically covers:

1. Peripheral advertising interval and channels
2. Central pairing with Peripheral
3. Peripheral pairing with Central
4. Connection Stability
5. Multiple Connections
6. Power consumption during active connection
7. Power consumption during idle state
8. Battery life
9. Handling Multiple bonded devices
10. Audio quality test

For application profile testing, additional tools and applications are required. Since the edge device is mostly going to communicate with consumer devices such as smartphones, automotive clusters, infotainment systems etc., it will be complex to test against a wide range of smartphones and devices. A proper set of tools need to be identified for thorough application profile testing. These tools could be a Client Emulator for functional validation or a Sniffer for non-invasive validation. Bluetooth Low Energy (BLE) solutions for consumer devices require application profile testing to verify that all services and characteristics conform to the published profile specifications. BLE app development teams use application profile testing to validate characteristic read/write behavior and notification delivery before product release.

Client Emulator

Essentially PC-based or Mobile Apps, these tools help interact with and test the target Bluetooth devices. They are also very helpful for testing out new changes during BLE app development. These apps allow testers to scan for nearby advertising Bluetooth Low Energy devices, connect to them, discover services and characteristics, and read from/write to the characteristic values — enabling comprehensive application profile testing.

Two well-known examples are:

• Nordic nRF Connect app (iOS, Android, Desktop)
• TestBot (Desktop)

Nordic Semiconductor's nRF Connect is a robust tool for application profile testing of Bluetooth Low Energy BLE devices. It allows reading available characteristics, writing to them, and registering for notifications. However, being a non-customizable tool, performing specific communication operations such as multi-sequence operations or file transfer will be a challenge.

TestBot from Embien is a PC-based tool that allows testers to create a mock peripheral device and simulate its behavior during application profile testing. This method is much more flexible than the nRF Connect app, as testers can program the peripheral device to behave in certain ways. Configuring TestBot-based automation may take more time initially, but once set up, it can be used for both unit testing and integration testing of Bluetooth Low Energy (BLE) solutions for consumer devices.

Bluetooth Sniffer

A Bluetooth sniffer (or protocol analyzer) is one of the most useful tools for application profile testing. The difference between a Bluetooth sniffer and Client Emulator apps is that sniffers can spy on the communication between central and peripheral devices non-invasively. While a client emulator is used to act as a central device for application profile testing, the sniffer acts in the background without modifying system behavior.

In general, a BLE sniffer captures packets in two main scenarios:

• Advertising mode: It captures advertising packets (mainly on the primary advertising channels 37, 38, and 39)
• Connection mode: It captures raw packet data exchanged between two Bluetooth LE devices during a connection (the remaining 37 channels: 0 through 36)

There are 2 types of sniffers.

• Low-Cost Development kit based BLE sniffers
• Professional BLE sniffers

Though the low-cost sniffers usually suffer from a few limitations — such as the lack of advanced features and not being able to scan all three primary advertising channels simultaneously — they are good enough for most application profile testing tasks.

Conclusion

Bluetooth technology continues to be a cornerstone of wireless communication, enabling a wide array of devices to connect seamlessly. By adhering to best practices and leveraging advanced testing tools such as sniffers, emulators, and Bluetooth DTM direct test mode protocol testing, testers can validate both physical level testing compliance and application profile testing functionality. Comprehensive application profile testing for Bluetooth Low Energy (BLE) solutions for consumer devices ensures that BLE app development deliverables meet Bluetooth SIG specifications before product launch.