LE Audio BAP

BAP

<\/script>\n
'; }, get iframeSnippet() { const domain = '{ SITE_DOMAIN }'; const type = '{ embed_type }'; const slug = '{ embed_slug }'; return ''; }, get activeSnippet() { return this.method === 'script' ? this.scriptSnippet : this.iframeSnippet; }, copySnippet() { navigator.clipboard.writeText(this.activeSnippet).then(() => { this.copied = true; setTimeout(() => { this.copied = false; }, 2000); }); } }" @keydown.escape.window="open = false" @click.outside="open = false">

Embed This Widget

Theme


      
    


    
    

      Widget powered by
      .
      Free, no account required.
    

  





    
    

    
    

      
Basic Audio Profile -- the foundational LE Audio profile defining unicast and broadcast audio streams.

    


    
    
    

      다른 명칭:
      
      Basic Audio Profile
      
    

    
  


  




  
  

    
Basic Audio Profile (BAP)


BAP (Basic Audio Profile) is the foundational profile in the LE Audio architecture. It defines the procedures for discovering, configuring, and controlling unicast and broadcast audio streams between BLE devices.


Role in the LE Audio Stack


BAP sits above the transport layer (Isochronous Channels) and below higher-level profiles like CAP, Hearing Access Profile (HAP), and Telephony and Media Audio Profile (TMAP). It provides the core procedures that all LC3 codec and Auracast." data-category="LE Audio">LE Audio implementations must support.


BAP defines two roles:


    

  • Unicast Client / Server: For point-to-point audio using CIS. The Client (typically a phone) discovers the Server's audio capabilities via PACS (Published Audio Capabilities Service), configures streams via ASCS, and manages the CIS lifecycle
    • 

  • Broadcast Source / Sink / Assistant: For one-to-many audio using BIS. The Source creates Auracast broadcasts, Sinks receive them, and Assistants help Sinks discover and connect to broadcasts
    • 



Discovery and Configuration


The unicast workflow follows a structured sequence. The Client first reads PACS to discover what codecs and audio locations the Server supports. It then writes to ASCS to configure codec parameters (LC3 settings), QoS parameters (interval, latency, retransmissions), and enable the stream. The Controller establishes the underlying CIS, and audio begins flowing.


For broadcast, the Source sets up a BIG and advertises it via Periodic Advertising. The Sink discovers the broadcast by scanning for extended advertisements, synchronizing to the periodic train, and then synchronizing to the BIG to receive audio.


Mandatory GATT Services


A BAP Unicast Server must implement:
- PACS (Published Audio Capabilities Service) -- advertises supported codecs and audio contexts
- ASCS (Audio Stream Control Service) -- manages stream endpoint state machines


A BAP Broadcast Source uses advertising-based discovery without ATT">GATT services.


Implementation Guidance


BAP is typically provided as a library within the chip vendor's SDK. Application developers implement callbacks for audio data handling and UI, while BAP handles the protocol-level negotiation. Testing BAP interoperability requires the Bluetooth SIG's PTS (Profile Tuning Suite) to validate conformance with the specification.

  

  

  
  
  




  
  
Related Terms

  

  

    
    LE Audio
    
    CIS
    
    BIS
    
    CAP
    
  





  

  
  

  
  

  
  
  

    
Related Content

    

      
      
        

          
          
LE Audio: The Next Generation of Bluetooth Audio

          
          Mesh & Audio
          
        

        
        
        
…public broadcast audio, defined in the Bluetooth SIG's BAP (Basic Audio Profile) . A venue (airport, cinema, gym,…

        
      
      
    

  

  

  
  




  
자주 묻는 질문


  

    
    

      
      

        
Our glossary covers 90+ BLE technical terms organized by category. Each term includes a definition, related terms, and links to relevant chips and guides.