Member Login
Home > Technology Overview > PBAP

Phone Book Access Profile (PBAP)

MAP Use CasesThe Phone Book Access Profile (PBAP) specification defines the procedures and protocols to exchange Phone Book objects between devices.

Usage Scenarios

The main scenarios covered by this profile:

  • The Phone Book Client Equipment (PCE) to access the list of phone book entries stored in the Phone Book Server Equipment (PSE).
  • The PCE to down load one or several phone book entries from the PSE.
  • The PCE to access the call histories stored in the PSE.
  • The PCE to access the Subscriber number information stored in the PSE.

Example Products

  • Cellular phone
  • Car
  • Personal computer

Getting technical

The Phone Book Access Profile (PBAP) specification defines the procedures and protocols to exchange Phone Book objects between devices.

PBAP Profile Stack
  • Phone Book Server Equipment (PSE) – This is the device that contains the source phone book objects.
  • Phone Book Client Equipment (PCE) – This is the device that retrieves phone book objects from the Server Equipment.

The Baseband, LMP and L2CAP are the physical and data link layers of the Bluetooth protocols. RFCOMM is the Bluetooth serial port emulation entity. SDP is the Bluetooth Service Discovery Protocol.

Compatibility to the current Bluetooth Core specification 1.2 and later is mandated.

The PBAP session is defined as the underlying OBEX session between the client and the server opened with the PBAP Target UUID.

For even greater detail, access this in-depth PDF: Phone Book Access Profile Specification.

© 2013 Bluetooth SIG, Inc. All rights reserved.