Member Login
Home > Technology Overview > MAP

Message Access Profile (MAP)

MAP Use CasesThe Message Access Profile (MAP) specification defines a set of features and procedures to exchange messages between devices.

Usage Scenarios

MAP can be used:

  • to access in a car to a mobile phone, using the car's display or audio system to avoid cumbersome handling of the mobile phone while driving, providing acoustical announcements of email or SMS reception Text2Speech output of messages etc.,
  • to provide message access to a mobile messaging device using any available PC or notebook to leverage the superior display and input capabilities of the computer.
  • to enable messaging to any stationary or mobile devices with IO capability, e.g. TVs, message panels, digital picture frames, eBooks, pagers, portable navigation systems or wearable Bluetooth devices.

The main scenarios covered by this profile:

  • Notifying a remote device of the arrival of a new message on a messaging device.
  • Browsing messages in a messaging device.
  • Uploading messages onto a messaging device.
  • Deleting messages onto a messaging device.
  • Sending messages through a remote device.

Example Products

  • Car
  • Cellular phone
  • Personal computer
  • TV
  • Digital picture frame
  • eBooks
  • Portable navigation system
  • Wearable Bluetooth devices

Getting technical

The following roles are defined for this profile:

MAP Profile Stack
  • Message Server Equipment (MSE) – is the device that provides the message repository engine i.e. has the ability to provide a client unit with messages that are stored in this device and notifications of changes in its message repository.
  • Message Client Equipment (MCE) – is the device that uses the message repository engine of the MSE for browsing and displaying existing messages and to upload messages created on the MCE to the MSE.

The MCE device shall use the services of the MSE device only after successfully creating a secure connection. This includes exchanging of security initialization messages, creation of link keys, and enabling encryption. Security mode 2 or 3 shall be supported for devices implementing the Bluetooth 2.0+EDR, or earlier, specification. Security mode 4 shall be supported for devices implementing the Bluetooth 2.1+EDR, or later, specification.

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

© 2013 Bluetooth SIG, Inc. All rights reserved.