Leveraging Bluetooth Direction Finding (AoA/AoD) for Indoor Asset Tracking: CTE Configuration in nRF52840 and Angle Calculation via MUSIC Algorithm

Leveraging Bluetooth Direction Finding (AoA/AoD) for Indoor Asset Tracking: CTE Configuration in nRF52840 and Angle Calculation via MUSIC Algorithm

Indoor asset tracking has long been a challenging domain for wireless technologies. While GPS provides reliable outdoor positioning, its signal is attenuated indoors, making it unsuitable for sub-meter accuracy. Bluetooth Low Energy (BLE) 5.1 introduced a pivotal feature: Direction Finding, enabling Angle of Arrival (AoA) and Angle of Departure (AoD) methods. This article delves into the technical implementation of AoA-based indoor asset tracking using the nRF52840 microcontroller, focusing on Constant Tone Extension (CTE) configuration and the application of the MUSIC (Multiple Signal Classification) algorithm for high-resolution angle estimation.

Understanding the Bluetooth Direction Finding Framework

The Bluetooth Core Specification Version 5.1 and later defines Direction Finding as a mechanism to determine the direction of a signal. This is achieved by measuring the phase difference of a received signal across an antenna array. The specification introduces two primary methods:

• Angle of Arrival (AoA): The receiver (e.g., a locator) uses an antenna array to measure the incoming signal's phase. The transmitter sends a special packet containing a Constant Tone Extension (CTE).
• Angle of Departure (AoD): The transmitter uses an antenna array to send CTE packets, and the receiver (e.g., a mobile device) measures the phase differences to determine the angle.

For indoor asset tracking, AoA is often preferred because the locator infrastructure can be designed with a known antenna array geometry, while the asset (a tag) can be a simple single-antenna transmitter. The Bluetooth SIG's Asset Tracking Profile (ATP), adopted in January 2021, standardizes the GATT-based service for connection-oriented AoA direction detection. This profile defines how devices advertise their Direction Finding capabilities and exchange configuration data.

CTE Configuration on nRF52840

The nRF52840 from Nordic Semiconductor is a popular SoC supporting BLE 5.1 Direction Finding. Configuring the CTE is critical for accurate phase measurements. The CTE is a continuous, unmodulated tone appended to the end of a BLE packet. Its duration and slot spacing (for antenna switching) are defined by the Host Controller Interface (HCI) commands.

Below is a code example for configuring the nRF52840 as an AoA receiver (locator) using the Zephyr RTOS. This configuration ensures the CTE is sampled with the correct parameters.

/* Zephyr-based CTE configuration for nRF52840 AoA receiver */

#include <bluetooth/bluetooth.h>
#include <bluetooth/direction.h>

void configure_cte_receiver(void)
{
    int err;

    /* Enable BLE Direction Finding */
    err = bt_enable(NULL);
    if (err) {
        printk("Bluetooth init failed (err %d)\n", err);
        return;
    }

    /* Set CTE receiver parameters */
    struct bt_df_adv_cte_rx_param cte_rx_param = {
        .enable = true,
        .slot_durations = BT_DF_CTE_SLOT_DURATION_1US, /* 1 microsecond slots */
        .num_ant_ids = 3, /* Number of antennas in array */
    };

    err = bt_df_set_adv_cte_rx_param(&cte_rx_param);
    if (err) {
        printk("CTE RX param set failed (err %d)\n", err);
        return;
    }

    /* Enable CTE sampling on a specific advertising set */
    struct bt_le_ext_adv *adv_set;
    err = bt_le_ext_adv_create(BT_LE_ADV_NCONN, NULL, &adv_set);
    if (err) {
        printk("Advertising set create failed (err %d)\n", err);
        return;
    }

    err = bt_df_adv_cte_tx_enable(adv_set, BT_DF_CTE_TYPE_AOA, 160, 1);
    if (err) {
        printk("CTE TX enable failed (err %d)\n", err);
    } else {
        printk("CTE configured: AoA, 160 us length, 1 us slot\n");
    }
}

Key parameters in the CTE configuration include:

• Slot Duration: Typically 1 µs or 2 µs. Shorter slots allow faster antenna switching but require precise timing.
• CTE Length: Ranges from 16 µs to 160 µs (in 8 µs steps). Longer CTEs provide more samples for averaging, improving angle accuracy.
• Antenna Switching Pattern: The locator must know which antenna is active at each sample. This pattern is often stored in a lookup table.

Angle Calculation Using the MUSIC Algorithm

Once IQ samples (In-phase and Quadrature) are collected from the CTE, the next step is to estimate the angle of arrival. Traditional methods like beamforming or phase interferometry work well in line-of-sight (LOS) conditions but degrade with multipath reflections. The MUSIC algorithm, a subspace-based method, offers superior resolution by separating signal and noise subspaces.

The MUSIC algorithm assumes an array of M antennas receiving signals from D sources (where D < M). The received signal vector x(t) can be modeled as:

x(t) = A(θ) s(t) + n(t)

where A(θ) is the steering matrix, s(t) is the signal vector, and n(t) is noise. The algorithm computes the covariance matrix R = E[x(t) x^H(t)], then performs eigenvalue decomposition to separate the signal and noise subspaces.

The pseudospectrum is computed as:

P_MUSIC(θ) = 1 / (a^H(θ) E_n E_n^H a(θ))

where a(θ) is the steering vector for direction θ, and E_n is the noise subspace matrix. Peaks in the pseudospectrum correspond to estimated angles.

Below is a simplified implementation in C for an nRF52840 with a 3-element antenna array (e.g., uniform linear array with half-wavelength spacing at 2.4 GHz).

/* MUSIC algorithm for 3-element ULA (uniform linear array) */
#include <math.h>
#include <arm_math.h>  /* CMSIS-DSP for matrix operations */

#define M 3       /* Number of antennas */
#define D 1       /* Number of sources (single tag) */
#define N_SAMPLES 64  /* IQ samples per antenna */

float32_t music_angle(float32_t iq_samples[M][N_SAMPLES])
{
    /* Step 1: Compute covariance matrix (M x M) */
    float32_t R[M][M];
    memset(R, 0, sizeof(R));

    for (int n = 0; n < N_SAMPLES; n++) {
        for (int i = 0; i < M; i++) {
            for (int j = 0; j < M; j++) {
                R[i][j] += iq_samples[i][n] * iq_samples[j][n];
            }
        }
    }

    /* Normalize by number of samples */
    for (int i = 0; i < M; i++) {
        for (int j = 0; j < M; j++) {
            R[i][j] /= N_SAMPLES;
        }
    }

    /* Step 2: Eigenvalue decomposition (using CMSIS-DSP arm_mat_eigen_f32) */
    float32_t eigenvalues[M];
    float32_t eigenvectors[M][M];
    arm_matrix_instance_f32 R_mat = {M, M, (float32_t *)R};
    arm_matrix_instance_f32 V_mat = {M, M, (float32_t *)eigenvectors};
    arm_mat_eigen_f32(&R_mat, eigenvalues, &V_mat);

    /* Step 3: Identify noise subspace (smallest M-D eigenvalues) */
    float32_t noise_subspace[M][M-D];
    for (int col = 0; col < M-D; col++) {
        /* Find index of smallest eigenvalue not yet used */
        int min_idx = 0;
        for (int i = 1; i < M; i++) {
            if (eigenvalues[i] < eigenvalues[min_idx]) min_idx = i;
        }
        for (int row = 0; row < M; row++) {
            noise_subspace[row][col] = eigenvectors[row][min_idx];
        }
        eigenvalues[min_idx] = INFINITY; /* Mark as used */
    }

    /* Step 4: Scan angles from -90 to +90 degrees */
    float32_t theta, best_theta = 0.0, max_power = 0.0;
    float32_t d = 0.0625; /* Half wavelength at 2.4 GHz (in meters) */
    float32_t lambda = 0.125; /* Wavelength (in meters) */

    for (int deg = -90; deg <= 90; deg++) {
        theta = deg * M_PI / 180.0;

        /* Steering vector a(theta) for ULA */
        float32_t a[M];
        for (int i = 0; i < M; i++) {
            a[i] = expf(-I * 2 * M_PI * i * d * sinf(theta) / lambda);
            /* Use real part only for simplicity; full complex needed for accuracy */
        }

        /* Compute pseudospectrum: P = 1 / (a^H * E_n * E_n^H * a) */
        float32_t temp1[M-D], temp2 = 0.0;
        for (int j = 0; j < M-D; j++) {
            temp1[j] = 0.0;
            for (int i = 0; i < M; i++) {
                temp1[j] += conjf(a[i]) * noise_subspace[i][j];
            }
            temp2 += temp1[j] * conjf(temp1[j]);
        }

        float32_t power = 1.0 / (temp2 + 1e-10); /* Avoid division by zero */
        if (power > max_power) {
            max_power = power;
            best_theta = deg;
        }
    }

    return best_theta;
}

Performance Analysis and Practical Considerations

The accuracy of the MUSIC algorithm depends on several factors:

• Number of Antennas (M): More antennas improve angular resolution but increase computational complexity. For nRF52840, a 3-element array is a good balance, offering resolution of about 5-10 degrees under line-of-sight.
• Number of IQ Samples: Increasing N_SAMPLES reduces noise variance. With 64 samples per antenna, the standard deviation of angle error is typically below 3 degrees in LOS conditions.
• Multipath Environment: MUSIC excels in resolving multiple paths, but the number of sources D must be known a priori. In asset tracking, D=1 is common, but reflections can create virtual sources. Advanced techniques like spatial smoothing can mitigate this.

The nRF52840's Arm Cortex-M4F can handle the MUSIC algorithm with a 3-element array in real time (approximately 5-10 ms per angle calculation). However, for larger arrays (e.g., 8 elements), the eigenvalue decomposition becomes computationally intensive, and hardware accelerators or offloading to a host processor may be necessary.

Integration with Bluetooth Profiles and Services

The Bluetooth SIG's Asset Tracking Profile (ATP) and Ranging Service (RAS) provide a standardized framework for exchanging Direction Finding data. The RAS, adopted in November 2024, defines how to read ranging data and configure parameters. For a practical asset tracking system, the locator:

• Advertises its capability using the Indoor Positioning Service (IPS) (adopted in May 2015), which exposes coordinates and location information.
• Uses ATP to establish a connection-oriented AoA session with the asset tag.
• Configures CTE parameters via GATT write commands, as defined in the RAS.

By combining CTE configuration, the MUSIC algorithm, and standardized Bluetooth profiles, developers can build robust indoor asset tracking systems with sub-meter accuracy. The nRF52840 serves as an excellent platform for prototyping and deployment, offering a mature SDK and hardware support for Direction Finding.

In conclusion, Bluetooth Direction Finding, when paired with advanced signal processing like MUSIC, transforms BLE from a simple proximity technology into a precise indoor positioning tool. The key lies in careful CTE configuration and efficient algorithm implementation, ensuring real-time performance even on constrained embedded devices.

💬 欢迎到论坛参与讨论： 点击这里分享您的见解或提问