Service Discovery Protocol

Description

The Service Discovery Protocol (SDP) is a core protocol in the Bluetooth specification, defined in the 3GPP context primarily for interoperability and testing references (e.g., in 3GPP TS 36.579 for LTE-WLAN interworking tests involving Bluetooth). SDP provides a mechanism for Bluetooth devices to discover services available on other Bluetooth devices and to retrieve the attributes of those services without prior knowledge. It operates in a client-server model: the device seeking services acts as an SDP client, while the device providing services acts as an SDP server. Each service is characterized by a set of attributes stored in an SDP server's service record database. The most fundamental attribute is a Universally Unique Identifier (UUID) which identifies the service class (e.g., Serial Port, Object Push, Headset Audio Gateway). SDP uses a request-response protocol over a dedicated L2CAP channel. A client can search for services based on service class UUIDs or browse an unspecified list of services offered by a server. Once a service of interest is discovered, the client can retrieve its attributes, which include information like the RFCOMM channel number or L2CAP Protocol Service Multiplexer (PSM) needed to actually connect to and use the service. SDP itself does not provide access to the services; it only provides the information needed to establish a connection using the appropriate protocol (e.g., RFCOMM for serial emulation, L2CAP for data channels). This design allows for a dynamic environment where devices can join and leave a piconet, advertising and discovering available capabilities on the fly. It is essential for the plug-and-play user experience associated with Bluetooth technology.

Purpose & Motivation

SDP was created to address a key challenge in ad-hoc wireless personal area networks (PANs): how can two Bluetooth devices, potentially from different manufacturers and with different capabilities, automatically determine what they can do together? Without a standardized discovery mechanism, users would need to manually configure connections, severely limiting usability and the potential for seamless interoperability. The purpose of SDP is to enable this automatic service discovery, which is the foundation for Bluetooth's goal of replacing cables. It solves the problem of service identification and description in a low-power, short-range, dynamic networking environment. Before establishing a data or voice connection, devices use SDP to answer questions like 'Does the other device offer a hands-free profile?' or 'Can it receive a business card?'. This allows applications to present users with meaningful options (e.g., 'Send File' or 'Use as Audio Output') only when the remote device supports them. Its creation was motivated by the need for a simple, efficient protocol that could run on resource-constrained devices and support the wide variety of services envisioned for Bluetooth, from file transfer to telephony control. By providing this discovery layer, SDP enabled the proliferation of interoperable Bluetooth profiles and the rich ecosystem of connected devices we see today.

Key Features

• Client-server protocol for discovering services on remote Bluetooth devices
• Uses UUIDs to uniquely identify service classes and attributes
• Operates over a dedicated L2CAP channel for reliable communication
• Supports service search and service browsing requests
• Retrieves service attributes necessary for establishing a connection (e.g., RFCOMM channel, L2CAP PSM)
• Enables dynamic ad-hoc networking without pre-configuration

Evolution Across Releases

Defining Specifications