Summary
The Bluetooth specification that defines the Public Broadcast Announcement, the Standard Quality and High Quality stream classes, and the broadcast name used by Auracast transmitters.
Key findings
- Sections 2.1 and 3.1 define Public Broadcast Source, Public Broadcast Sink and Public Broadcast Assistant roles; a device must support at least one role and may support concurrent roles.
- Standard Quality means a stream using one of the settings that every Bluetooth LE Audio broadcast receiver must be able to decode (16 or 24 kHz in the Basic Audio Profile); High Quality means one of twelve listed 48 kHz settings.
- The Public Broadcast Announcement shows whether the streams are encrypted and whether Standard Quality and High Quality streams are configured, so a phone or hearing aid can skip a broadcast it cannot use without reading the full stream description.
- Encryption covers a whole broadcast group: either all its streams use the same Broadcast Code or none are encrypted.
- The broadcast name must be human-readable UTF-8 text of 4 to 32 bytes, and scanning devices must accept up to 128 bytes for backward compatibility. Several transmitters carrying the same audio may use the same name.
- An optional immediate-rendering flag lets receivers play audio as early as they can instead of at the transmitter's Presentation Delay; receivers worn as a set should act on it only if all of them can play at the same time.
- The profile sets no venue coverage, transmit-power or audio-level targets and no numeric limit for complete-path latency. Section 5.4 does define rendering behavior relative to Presentation_Delay when the optional immediate-rendering flag is set.
- Lets several broadcasters give the same Broadcast_Name to broadcasts carrying the same audio, so that a receiving device can identify alternative transmitters of the same stream (section 5.1).
- The Version History records Board adoption of version 1.0 on 5 July 2022, version 1.0.1 on 1 October 2024 and version 1.0.2 on 3 November 2025. The abstract describes announcements enabling discovery and rendering of public broadcast audio using commonly supported audio configurations.
- Section 1.1.1, Table 1.1, lists errata incorporated in version 1.0.1 affecting role requirements and advertising/metadata structures, including Broadcast_Name, Audio_Active_State and Broadcast_Audio_Immediate_Rendering_Flag.
- Section 1.1.2, Table 1.2, lists errata incorporated in version 1.0.2 affecting profile role support, Link Layer feature support, Public Broadcast Announcements and Broadcast_Name formatting. These tables identify affected sections, without demonstrating product performance changes.
- Section 2.5 states compatibility with Bluetooth Core Specification 5.2 or later. This profile-level statement does not establish that every Core 5.2 device supports public broadcast audio.
Limits
A product specification for interoperability, not an installation or venue standard. Rules for public transmitters, such as defaulting to Standard Quality, come from the SIG's separate transmitter guide.
Read the original
Cited in
- Which hearing devices can receive which systems?Open
- How do many transmitters share one broadcast across a large venue?Open
- How do listeners find and join the right broadcast?Open
- Open or protected: when should a venue broadcast need a code?Open
- Can venue broadcasts be spoofed, hijacked or jammed, and what protects them?Partly answered
- What does Auracast qualification and the Auracast logo cover, and what does it leave out?Partly answered
Cite this source
Bluetooth SIG Audio, Telephony, and Automotive Working Group. Public Broadcast Profile, version 1.0.2. Bluetooth SIG. 3 November 2025. https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/pbp_v1-0-2_1761252922/PBP_v1.0.2/out/en/index-en.html (accessed 13 October 2026).
Every finding here cites its source, and who funded each source is labelled. This site does not recommend products. Found an error or a missing study? Suggest a correction.