品牌产品

In the rapidly evolving landscape of wireless audio, the introduction of Auracast—a Bluetooth LE Audio broadcast feature—has unlocked unprecedented potential for public announcement systems in high-traffic environments like stadiums and airports. For the TWS Bluetooth headset industry, this technology represents a paradigm shift from traditional one-to-one audio streaming to one-to-many broadcast, enabling seamless, low-latency audio delivery to an unlimited number of listeners. This article delves into the technical architecture, design considerations, and future implications of Auracast-based public announcement systems, focusing on how they transform user experience in large venues.

Core Technology: Auracast and Bluetooth LE Audio

Auracast is a broadcast audio feature defined in the Bluetooth LE Audio specification, formally introduced in Bluetooth 5.2 and refined in subsequent versions. Unlike classic Bluetooth (BR/EDR), which supports point-to-point connections, Auracast enables a single transmitter (e.g., a stadium PA system) to broadcast audio streams to multiple receivers (e.g., TWS earbuds) simultaneously. This is achieved through the LE Isochronous Channel (LE-ISOC), which allocates time slots for synchronized data transmission, ensuring low latency (typically < 50 ms) and high reliability.

For TWS headsets, Auracast requires support for the LE Audio stack, including the LC3 codec, which provides superior audio quality at lower bitrates (e.g., 160-345 kbps) compared to SBC or AAC. This efficiency is critical for public announcement systems, where multiple audio streams—such as gate changes, emergency alerts, or multilingual translations—must be broadcast without overwhelming bandwidth. Additionally, Auracast supports encryption and authentication, allowing venue operators to control access to specific broadcasts (e.g., for staff-only channels).

Application Scenarios in Stadiums and Airports

The design of Auracast-based public announcement systems must address the unique challenges of large venues: acoustic noise, signal propagation, and user mobility. Below are key application scenarios, each requiring tailored implementation.

• Multilingual Announcements in Airports: In international airports, announcements often need to be delivered in multiple languages simultaneously. Auracast enables the transmitter to broadcast several audio streams (e.g., English, Mandarin, Arabic) on different channels. TWS headsets can scan for available broadcasts, and users select their preferred language via a companion app or on-device menu. For example, a gate change announcement in Terminal 3 can be broadcast on channel A (English) and channel B (Spanish), with each stream encoded at 192 kbps using LC3, ensuring clarity even in noisy terminal environments (ambient noise levels up to 75 dB SPL).
• Emergency Alerts in Stadiums: During emergencies (e.g., fire, security threats), traditional PA systems may be drowned out by crowd noise. Auracast can broadcast critical alerts directly to users' TWS earbuds, with priority overriding any ongoing audio playback. The system can leverage multiple BLE beacons placed around the stadium (e.g., one per section) to ensure coverage, using a mesh network for redundancy. Latency must be below 30 ms for real-time updates, which is achievable with LE-ISOC and proper scheduling. Additionally, the broadcast can include location-specific instructions (e.g., "Evacuate via Gate 12") by encoding metadata in the broadcast packet.
• Assistive Listening for Hearing-Impaired Users: Auracast can replace traditional FM or induction loop systems for assistive listening. TWS headsets with hearing aid profiles can receive a dedicated broadcast, with audio processed to enhance speech intelligibility (e.g., dynamic range compression). In a stadium with 50,000 seats, this eliminates the need for rental receivers, reducing cost and logistical complexity.
• Zone-Specific Audio for Retail and Wayfinding: In airports, Auracast can broadcast zone-specific information, such as duty-free promotions in Terminal B or boarding gate reminders in Terminal C. TWS headsets can automatically switch broadcasts as users move between zones, using BLE-based location tracking. This requires a network of Auracast transmitters (e.g., one per 50-meter radius) with overlapping coverage, managed by a central controller to avoid interference.

Design Considerations for TWS Headset Integration

To fully leverage Auracast in stadiums and airports, TWS headsets must incorporate several hardware and software features. First, the Bluetooth controller must support LE Audio and the Broadcast Audio Profile (BAP), which defines the broadcast sink role. Many current TWS chipsets (e.g., Qualcomm QCC5171, MediaTek MT2828) already include this support, but firmware updates may be needed for older models.

Second, power consumption is a critical factor. Auracast reception is more efficient than classic Bluetooth streaming, as the headset only needs to listen for scheduled isochronous packets rather than maintaining a continuous connection. However, scanning for available broadcasts can drain battery—optimized scanning intervals (e.g., 100 ms) and low-power listening modes (e.g., using a dedicated BLE core) are essential. Industry data suggests that Auracast-enabled TWS earbuds can achieve 8-10 hours of continuous broadcast listening with a 50 mAh battery, comparable to standard music playback.

Third, user interface design must be intuitive. For stadiums, users may need to select a broadcast channel via a simple tap on the earbuds (e.g., triple tap to cycle through languages). In airports, a companion app can provide a list of available broadcasts with metadata (e.g., "Gate A12 – English Announcement"). The headset should also support dynamic switching: if a user is listening to music and a priority broadcast (e.g., emergency alert) is detected, the headset should automatically pause music and route the broadcast audio, with a notification tone.

Future Trends and Challenges

The adoption of Auracast in public announcement systems is still nascent, but several trends will shape its evolution. One major trend is the integration with 5G and Wi-Fi 6E for hybrid broadcasting. While Auracast operates over BLE (2.4 GHz), stadiums may use 5G edge computing to aggregate and synchronize broadcasts across multiple Auracast transmitters, reducing latency for time-sensitive alerts. Another trend is the use of AI for personalized audio: for example, a TWS headset could use beamforming microphones to isolate a user's voice while receiving Auracast broadcasts, enabling two-way communication with venue staff.

Challenges remain, particularly in interference management. In a stadium with 100+ Auracast transmitters, the 2.4 GHz spectrum can become congested, especially with coexisting Wi-Fi and classic Bluetooth devices. Advanced channel hopping algorithms (e.g., adaptive frequency hopping with 40 channels) and transmit power control (e.g., -20 to +10 dBm) are necessary to minimize collisions. Additionally, privacy concerns arise: broadcasts may be intercepted by unauthorized receivers, but encryption (AES-128) and broadcast codes can mitigate this. Venues must also ensure compliance with local regulations (e.g., FCC Part 15 in the US) for BLE transmission power.

Finally, ecosystem interoperability is key. The Bluetooth SIG has defined the Public Broadcast Profile (PBP) to standardize broadcast metadata, such as language codes and announcement types. TWS headset manufacturers must adhere to these profiles to ensure seamless operation across different venues. As of 2025, major chipset vendors (e.g., Nordic, Infineon) are releasing reference designs for Auracast-capable TWS, and airports like Singapore Changi and stadiums like SoFi Stadium are piloting pilot systems.

Conclusion

Auracast-based public announcement systems represent a transformative leap for TWS Bluetooth headsets, enabling scalable, low-latency, and personalized audio delivery in stadiums and airports. By leveraging LE Audio's broadcast capabilities, venues can enhance accessibility, improve emergency response, and reduce infrastructure costs. However, successful deployment requires careful design of transmitter networks, power-efficient headset integration, and robust interference management. As the technology matures, Auracast will likely become a standard feature in TWS earbuds, bridging the gap between personal audio and public communication.

Auracast is revolutionizing public announcement systems by enabling TWS headsets to receive synchronized, low-latency broadcasts in large venues, with future advancements in hybrid connectivity and AI-driven personalization set to redefine the user experience.

1. Introduction: The Challenge of Static ANC in Dynamic TWS Environments

Active Noise Cancellation (ANC) in True Wireless Stereo (TWS) headsets has become a standard feature, but most commercial implementations rely on fixed-gain feedback or feedforward filters tuned during production. This static approach fails under real-world conditions: changing ear canal sealing due to movement, varying ambient noise profiles (e.g., wind vs. engine hum), and acoustic leakage from different ear tip sizes. Adaptive ANC addresses this by continuously adjusting filter parameters in real-time using the Bluetooth LE Audio (BLEA) isochronous channel for control data. This article presents a practical algorithm for adaptive ANC tuning that exploits the low-latency, bidirectional capabilities of BLEA's LC3 codec metadata and the Coordinated Set Identification Service (CSIS) to synchronize left and right earbud coefficients.

2. Core Technical Principle: Time-Domain LMS with BLEA Parameter Embedding

Our approach uses a normalized Least Mean Squares (NLMS) adaptive filter running on the earbud's DSP core, but the adaptation step-size and filter tap weights are modulated by a host controller (smartphone or dongle) via BLEA. The key innovation is embedding the adaptation parameters within the BLEA Audio Stream Control packets, specifically the Codec Specific Configuration (CSC) fields of the ISOAL (Isochronous Adaptation Layer) frames. The timing diagram below describes the interaction:

Timeline (0 to 10ms BLEA interval):
+-------+-------+-------+-------+-------+
| Host  | Earbud| Host  | Earbud| Host  |
| Tx    | Rx    | Tx    | Rx    | Tx    |
+-------+-------+-------+-------+-------+
| Frame | Frame | Frame | Frame | Frame |
| N     | N+1   | N+2   | N+3   | N+4   |
+-------+-------+-------+-------+-------+
| CSC   | CSC   | CSC   | CSC   | CSC   |
| (μ,α) | (μ,α) | (μ,α) | (μ,α) | (μ,α) |
+-------+-------+-------+-------+-------+

Where:
- μ: Adaptation step size (16-bit float, range 0.001 to 0.5)
- α: Leakage factor (8-bit fixed point, 0.0 to 1.0)
- Each CSC field is 4 bytes, piggybacked on isochronous audio data.

The mathematical foundation is the NLMS update equation, modified to include a leakage term for coefficient drift prevention:

w(n+1) = (1 - α·μ) · w(n) + μ · e(n) · x(n) / (||x(n)||² + δ)

Where:
- w(n): Filter coefficient vector (N taps)
- x(n): Reference noise signal from feedforward microphone
- e(n): Error signal from feedback microphone (residual noise)
- δ: Regularization constant (prevent division by zero)
- α: Leakage factor (set by host via BLEA)
- μ: Step size (set by host via BLEA)

The host determines optimal μ and α based on external context: e.g., μ is reduced during wind noise detection (to avoid divergence), and α is increased during high movement (to accelerate forgetting of stale coefficients). The earbud's DSP only performs the NLMS update; the host handles the meta-adaptation logic.

3. Implementation Walkthrough: BLEA Parameter Negotiation and DSP Integration

The implementation is split between a host-side application (e.g., running on a smartphone) and the earbud firmware. The host uses BLEA's Audio Stream Control Service (ASCS) to establish a Unidirectional Audio Stream with a dedicated Audio Stream Endpoint (ASE) for control data. The packet format for the control stream is defined as:

Packet Format (4 bytes):
Byte 0: Reserved (0x00)
Byte 1: μ (IEEE 754 half-precision float, 16 bits)
Byte 2: α (fixed-point Q8.8, 16 bits)
Byte 3: CRC8 (polynomial 0x07)

Below is a C-language snippet for the earbud's DSP that receives these parameters and applies them to the NLMS filter. The code assumes a dual-core architecture: one core for audio processing (Core 0) and one for BLEA stack (Core 1), with shared memory for parameter exchange.

// Earbud DSP Core 0: Adaptive ANC filter update
#include "anc_dsp.h"
#include "blea_payload.h"

// Shared memory region for BLEA parameters
volatile struct {
    float mu;
    float alpha;
    uint8_t update_flag;
} anc_params __attribute__((section(".shared_ram")));

// NLMS filter state (256 taps, 16 kHz sample rate)
#define TAPS 256
float w[TAPS] = {0};  // Filter coefficients
float x_buffer[TAPS] = {0}; // Reference input buffer

void anc_nlms_update(float ref_mic, float err_mic) {
    static int buffer_idx = 0;
    float error, denominator, step;
    int i;

    // Shift reference buffer
    x_buffer[buffer_idx] = ref_mic;
    buffer_idx = (buffer_idx + 1) % TAPS;

    // Compute filter output (convolution)
    float y = 0;
    for (i = 0; i < TAPS; i++) {
        y += w[i] * x_buffer[(buffer_idx - i + TAPS) % TAPS];
    }

    // Error signal
    error = err_mic - y;

    // Normalization factor
    denominator = 0;
    for (i = 0; i < TAPS; i++) {
        denominator += x_buffer[(buffer_idx - i + TAPS) % TAPS] *
                       x_buffer[(buffer_idx - i + TAPS) % TAPS];
    }
    denominator += 1e-10f; // δ regularization

    // Check for new BLEA parameters (atomic read)
    if (anc_params.update_flag) {
        float new_mu = anc_params.mu;
        float new_alpha = anc_params.alpha;
        anc_params.update_flag = 0;

        // Apply new parameters
        step = new_mu / denominator;
        // Update coefficients with leakage
        for (i = 0; i < TAPS; i++) {
            w[i] = (1.0f - new_alpha * new_mu) * w[i] +
                   step * error * x_buffer[(buffer_idx - i + TAPS) % TAPS];
        }
    } else {
        // Use previous parameters
        step = anc_params.mu / denominator;
        for (i = 0; i < TAPS; i++) {
            w[i] = (1.0f - anc_params.alpha * anc_params.mu) * w[i] +
                   step * error * x_buffer[(buffer_idx - i + TAPS) % TAPS];
        }
    }

    // Anti-aliasing clip (prevent coefficient explosion)
    for (i = 0; i < TAPS; i++) {
        if (w[i] > 1.0f) w[i] = 1.0f;
        if (w[i] < -1.0f) w[i] = -1.0f;
    }
}

// BLEA Core 1: Interrupt-driven parameter reception
void blea_csc_callback(uint8_t *data, uint16_t len) {
    if (len != 4) return; // Invalid packet

    uint16_t mu_half = (data[1] << 8) | data[0];
    uint16_t alpha_fixed = (data[3] << 8) | data[2];

    // Convert half-precision to float (simplified, use hardware FPU)
    float mu = half_to_float(mu_half);
    float alpha = (float)(alpha_fixed) / 256.0f;

    // Atomic write to shared memory
    anc_params.mu = mu;
    anc_params.alpha = alpha;
    anc_params.update_flag = 1;
}

The host-side algorithm (Python pseudocode) decides when to change μ and α based on sensor fusion:

# Host-side adaptation logic (Python)
import struct
from bluetooth_le_audio import IsochronousStream

class AdaptiveANCController:
    def __init__(self):
        self.stream = IsochronousStream()
        self.mu = 0.1  # Default step size
        self.alpha = 0.01  # Default leakage

    def on_audio_quality_event(self, residual_noise_db, motion_intensity, wind_level):
        # Rule-based parameter adjustment
        if wind_level > 0.7:  # Heavy wind
            self.mu = 0.01  # Slow adaptation to avoid divergence
            self.alpha = 0.1  # Aggressive leakage
        elif motion_intensity > 0.5:  # Running or head shaking
            self.mu = 0.05
            self.alpha = 0.05
        elif residual_noise_db < -30:  # Already quiet
            self.mu = 0.001  # Fine-tuning
            self.alpha = 0.001
        else:
            self.mu = 0.1  # Normal adaptation
            self.alpha = 0.01

        # Pack parameters into BLEA CSC field
        packet = struct.pack('

| Metric                | Static ANC | Adaptive ANC | Improvement |
|-----------------------|------------|--------------|-------------|
| Average attenuation   | 25 dB      | 32 dB        | +7 dB       |
| Convergence time      | 200 ms     | 50 ms        | -75%        |
| Wind noise rejection  | 5 dB       | 15 dB        | +10 dB      |
| Power consumption     | 8 mW       | 9.5 mW       | +19%        |
| Memory footprint      | 1.5 KB     | 3.5 KB       | +2 KB       |