Apple Bluetooth Accessory Design Guidelines

Bluetooth Accessory Design Guidelines forApple ProductsRelease R5

2011-10-14

Apple Inc.© 2011 Apple Inc.All rights reserved.

No part of this publication may be reproduced,stored in a retrieval system, or transmitted, inany form or by any means, mechanical,electronic, photocopying, recording, orotherwise, without prior written permission ofApple Inc., with the following exceptions: Anyperson is hereby authorized to storedocumentation on a single computer forpersonal use only and to print copies ofdocumentation for personal use provided thatthe documentation contains Apple’s copyrightnotice.

The Apple logo is a trademark of Apple Inc.

Use of the “keyboard” Apple logo(Option-Shift-K) for commercial purposeswithout the prior written consent of Apple mayconstitute trademark infringement and unfaircompetition in violation of federal and statelaws.

No licenses, express or implied, are grantedwith respect to any of the technology describedin this document. Apple retains all intellectualproperty rights associated with the technologydescribed in this document. This document isintended to assist application developers todevelop applications only for Apple-labeledcomputers.

Every effort has been made to ensure that theinformation in this document is accurate. Appleis not responsible for typographical errors.

Apple Inc.1 Infinite LoopCupertino, CA 95014408-996-1010

Apple, the Apple logo, iPhone, iPod, iPod touch,Mac, Mac OS, and Numbers are trademarks ofApple Inc., registered in the United States andother countries.

iPad is a trademark of Apple Inc.

IOS is a trademark or registered trademark ofCisco in the U.S. and other countries and is usedunder license.

Simultaneously published in the United Statesand Canada.

Even though Apple has reviewed this document,APPLE MAKES NO WARRANTY OR REPRESENTATION,EITHER EXPRESS OR IMPLIED, WITH RESPECT TOTHIS DOCUMENT, ITS QUALITY, ACCURACY,MERCHANTABILITY, OR FITNESS FOR A PARTICULARPURPOSE. AS A RESULT, THIS DOCUMENT IS

PROVIDED “AS IS,” AND YOU, THE READER, AREASSUMING THE ENTIRE RISK AS TO ITS QUALITYAND ACCURACY.

IN NO EVENT WILL APPLE BE LIABLE FOR DIRECT,INDIRECT, SPECIAL, INCIDENTAL, ORCONSEQUENTIAL DAMAGES RESULTING FROM ANYDEFECT OR INACCURACY IN THIS DOCUMENT, evenif advised of the possibility of such damages.

THE WARRANTY AND REMEDIES SET FORTH ABOVEARE EXCLUSIVE AND IN LIEU OF ALL OTHERS, ORALOR WRITTEN, EXPRESS OR IMPLIED. No Appledealer, agent, or employee is authorized to makeany modification, extension, or addition to thiswarranty.

Some states do not allow the exclusion or limitationof implied warranties or liability for incidental orconsequential damages, so the above limitation orexclusion may not apply to you. This warranty givesyou specific legal rights, and you may also haveother rights which vary from state to state.

Contents

Introduction Introduction 7

Organization of This Document 7

Chapter 1 General Requirements 9

Conformity With Bluetooth Specifications 9Enhanced Data Rate 9Sniff Mode for Low Power Consumption 9Role and Topology Management 10Extended Inquiry Response 10Secure Simple Pairing 11

Profiles 11Device ID Profile (DID) 11Hands-Free Profile (HFP) 12Audio/Video Remote Control Profile (AVRCP) 13Advanced Audio Distribution Profile (A2DP) 15

Bluetooth Low Energy 16Role 16Advertising Channels 17Advertising PDU 17Advertising Data 17Advertising Interval 17Connection Parameters 18Privacy 18Permissions 18Pairing 19Services 19

Chapter 2 Apple Protocols and Developer Support 21

Apple Bluetooth Development Mailing List 21The iPod Accessory Protocol 21Headset Battery Level Indication 21

HFP Command AT+XAPL 22HFP Command AT+IPHONEACCEV 22

Document Revision History 23

32011-10-14 | © 2011 Apple Inc. All Rights Reserved.


CONTENTS

Tables

Chapter 1 General Requirements 9

Table 1-1 SubBand Codec Information Elements for Apple products 15Table 1-2 MPEG-2/4 AAC Codec Information Elements for iOS devices 16Table 1-3 AAC audio packet for iOS devices 16



TABLES

This document presents design guidelines for hardware accessories that use Bluetooth transport tocommunicate with Apple products, including Macs, iPhones, iPads, and iPod touch models.

To be compatible with Apple products, both current and future, Bluetooth accessories should follow thespecifications in this document.

IMPORTANT: This document uses the term “Apple product” to refer generically both to Macs (Apple computersthat run Mac OS X) and to iPods, iPhones, and iPads. Among the latter products, those that run iOS (Apple’smobile operating system) are also referred to as “iOS devices.” Specifications in this document that aredesignated for iOS devices apply only to those products.

Organization of This Document

The specifications in this document are presented in three chapters:

■ “General Requirements” (page 9) relates the design of hardware accessories that use Bluetooth transportto the general Bluetooth specification.

■ “Apple Protocols and Developer Support” (page 21) references an Apple protocol that can extendaccessory capabilities beyond those supported by standard Bluetooth profiles.

Organization of This Document 72011-10-14 | © 2011 Apple Inc. All Rights Reserved.

INTRODUCTION

Introduction

8 Organization of This Document2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

INTRODUCTION

Introduction

Conformity With Bluetooth Specifications

Every Bluetooth accessory that is compatible with an Apple product should support the Bluetooth CoreSpecification Version 2.1 + EDR or higher. This specification introduced the important security feature SecureSimple Pairing as well as Extended Inquiry Response.

Enhanced Data Rate

The Enhanced Data Rate (EDR) feature introduced in the Bluetooth 2.0 specification enables Bluetoothaccessories to communication more efficiently. To provide backward capability, the Bluetooth SIG made EDRan optional feature. Apple strongly recommends the use of EDR as much as possible for the following reasons:

■ It provides higher data rates compared to Basic Data Rate (BDR).

■ It communicates more efficiently, transferring more data bits per unit of time.

■ It reduces the power consumption used per bit transferred.

■ It coexists better with WiFi using a shared antenna because it frees up more air time for WiFi.

■ It improves performance in multipoint configurations.

Sniff Mode for Low Power Consumption

Minimizing power consumption is critical for all mobile devices. Therefore, every Bluetooth accessory that iscompatible with an Apple product:

■ Should support and should request Bluetooth Sniff Mode

■ Should accept requests for Sniff Mode and support all valid parameters listed in the Bluetooth specification.

Bluetooth accessories that are compatible with Apple products should also use Sniff Mode as much as possible,especially when there is little or no data being transmitted over the Bluetooth link. Besides its powerconsumption advantages, Sniff Mode enables better antenna sharing with WiFi.

The Sniff Mode parameters are specific to the usage model and Bluetooth Profile. The Apple product expectsthe accessory to request Sniff Mode with appropriate parameters for a specific usage. If the accessory doesnot send such a request, the Apple product may send a Sniff Mode request. When the Apple product sendsa request for Sniff Mode, the remote device should accept the request and its parameters without negotiation.

If it sets the Sniff Mode parameters, the Bluetooth accessory should set the sniff Interval to less than a thirdof the Bluetooth baseband Link Supervision Timeout. This makes the Bluetooth link less susceptible tointerference. To improve link robustness, the accessory should use a shorter sniff Interval instead of multiple

Conformity With Bluetooth Specifications 92011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1

General Requirements

sniff attempts. Links with a sniff Interval of 1 second or more make the slave device open up a large correlationwindow, which has to be taken into account when calculating the number of sniff attempts. With sniff intervalsshorter than 1 second, multiple sniff attempts can improve link robustness but will increase powerconsumption.

Role and Topology Management

Every Bluetooth accessory that is compatible with an Apple product should:

■ Accept a request for Role Switch from an Apple product.

■ Continue with the connection when the Apple product rejects a request for Role Switch.

In a Bluetooth connection, one device is the master and the other the slave. The master can have multipleslaves, thus forming a piconet. The master device can also be a slave role to another master, creating ascatternet. Such a scenario creates complications since the device has to alternate between the two piconetsand thus wastes valuable bandwidth. Managing the topology of the network is therefore important formaximum performance. The Apple product can request a Role Switch, depending on its current topology,and the remote device should accept the request. The Apple product may also reject a request for a RoleSwitch because of topology concerns. Having a suboptimal topology may degrade the audio quality and theuser’s experience.

Only when it is maintaining multiple links, either Bluetooth or WiFi, will the Apple product request or denyrole switches. Hence, it will grant a role switch if there is no reason for the Apple product to be master. It isexpected that the accessory will behave the same, only trying to be master when there is a legitimate reason.The accessory should not always request to be master by default if there is no need in the system topologyto do so. If later the accessory needs to be master in order to maintain multiple links, it should ask to bemaster at that time.

Extended Inquiry Response

Every Bluetooth accessory that is compatible with an Apple product should provide the following informationin its Extended Inquiry Response packet:

■ The Local Name of the product (Complete or Shortened).

■ The TX Power Level.

■ The Service Class UUID for the iAP protocol, if the product has this service. For information about iAP,see “The iPod Accessory Protocol” (page 21).

During the Bluetooth discovery process the, Apple product prefers to display the Friendly Name of discoveredBluetooth accessories. Before the 2.1 version of the Bluetooth specification the Apple product would haveto set up a connection to the accessory and do a Remote Name Request, which takes power, antenna time,and user’s time. The Extended Inquiry Response feature, introduced in Bluetooth 2.1, lets an accessory sendits Local Name and other information as part of the Inquiry Response and thereby increase the speed andefficiency of the discovery process.

10 Conformity With Bluetooth Specifications2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


Secure Simple Pairing


■ Use Secure Simple Pairing.

■ Use the Numerical Comparison method if it has a display and input device supporting it.

Secure Simple Pairing greatly increases security and is a mandatory security feature introduced in the Bluetooth2.1 specification. To protect against a man-in-the-middle attack, the Numerical Comparison association modelshould be used whenever feasible. See Volume 1, Section 5.4 in the Bluetooth Core Specification, Version 2.1+ EDR.

Profiles

The Apple knowledge base article support.apple.com/kb/ht3647 provides a complete list of the Bluetoothprofiles that certain Apple products support. The Bluetooth specifications are the starting point for designingBluetooth accessories that are compatible with these products. The following sections add information andrequirements for some profiles, which can help accessory developers achieve superior results.

Device ID Profile (DID)


■ Support the Bluetooth Device ID Profile, version 1.3 or higher.

■ Use the company identifier from the Assigned Numbers document assigned by the Bluetooth SIG as itsVendor ID value (VID). See www.bluetooth.org/Technical/AssignedNumbers/identifiers.htm (requireslogin). Bluetooth HID Profile accessories may use a VID assigned by the USB Implementers Forum (USB-IFat www.usb.org) if the manufacturer does not have a Bluetooth SIG company identifier.

■ Use its VID value for the end product manufacturer.

■ Use a ProductID value that uniquely identities the product.

■ Use a Version value that uniquely identifies the software version.

The Device ID profile lets the Apple product identify the implementation of the remote Bluetooth accessory.This is valuable information and can be used to bridge alternate interpretations of the Bluetooth specificationwhen communicating with a remote accessory. Therefore it is important that the information in the DeviceID record uniquely identify the implementation.

In the case of car kits, for instance, the same car kit might go into two different car models. Ideally the twocar kits should have different Product IDs. However, it is acceptable for them to have the same ProductID aslong as they have identical hardware, software, and features. If the implementations differ at all, they shouldhave different Product IDs.

Profiles 112011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


http://support.apple.com/kb/ht3647

https://www.bluetooth.org/Technical/AssignedNumbers/identifiers.htm

http://www.usb.org

Hands-Free Profile (HFP)

If a Bluetooth accessory supports the Bluetooth Hands-Free Profile specification, it should be version 1.5 orhigher.

Remote accessories can use the Bluetooth Hands-Free Profile for phone communications. To achieve thebest user experience, the remote accessory should support the following features, which are optional in theBluetooth specification.

Remote Audio Volume Control

Every Bluetooth accessory that is compatible with an Apple product and supports HFP should:

■ Support Remote Audio Volume Control so the speaker volume on the Hands-Free accessory can becontrolled from the Apple product as described in Section 4.28 in the Bluetooth Hands-Free Profilespecification version 1.5.

■ Set the Remote volume control bit in the Supported Features bitmap sent with the AT+BRSF= command.

In some situations it is easier for the user to control the output volume through the Apple product insteadof directly on the remote accessory. For example, a passenger (or—if the car is parked—the driver) in a carcould use the volume slider on the phone to control the audio volume. Volume control synchronization isoutlined in Section 4.48.2 in the Bluetooth Hands-Free Profile specification version 1.5.

Indicator Event Reporting

Every Bluetooth accessory that is compatible with an Apple product and supports HFP should use indicatorevents reporting and not perform repetitive polling of status.

Apple products support all mandatory and optional indicators specified in HFP version 1.5 (service, call,callsetup, callheld, signal, roam, battchg). To minimize unnecessary polling of status using the AT+CIND?command, the remote accessory should enable indicator events reporting by sending an AT+CMER command.The Apple product will then send a +CIEV event when there is a change in status of an indicator. The remoteaccessory should request the initial status using the AT+CIND=? and AT+CIND? commands, according tothe HFP specification.

Voice Recognition Activation


■ Support Voice Recognition Activation, both AG and HF initiated as described in Section 4.25 in theBluetooth Hands-Free Profile specification version 1.5.

■ Set the “Voice recognition activation” bit in the “SupportedFeatures” bitmap sent with the AT+BRSF=command.

Apple products support voice recognition initiated by remote (Hands-Free) accessories and iOS (AudioGateway) accessories.

12 Profiles2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


Echo Cancellation and Noise Reduction

When echo cancellation and noise reduction are performed locally on a Hands-Free Bluetooth accessory, itshould turn off echo cancellation and noise reduction on the Apple product by sending an AT+NREC command,as described in Section 4.24 in the Bluetooth Hands-Free Profile specification version 1.5.

Apple products support echo cancellation and noise reduction; these features are active by default. If aHands-Free accessory also does echo cancellation and noise reduction it needs to turn these features off onthe Apple product (the Audio Gateway). This avoids unnecessary degradation of audio quality due to doubleaudio processing.

In-Band Ringing

Every Bluetooth accessory that is compatible with an Apple product and supports HFP should also supportIn-Band Ringing as specified in Section 4.13.1 in the Bluetooth Hands-Free Profile specification version 1.5.If the user sets a ring tone on the Apple product, the same ring tone should sound on the hands-free accessory.

Synchronous Connection


■ Support eSCO parameter set S2 and S3 and accept requests for these settings. See Section 5.6 of theBluetooth Hands-Free Profile specification version 1.5.

■ Request eSCO parameter set S2 or S3 when setting up a Synchronous Connection. Note that eSCOparameter set S1 should not be requested.

■ Render audio within 40 ms after the SCO/eSCO connection has been set up.

The eSCO packet types offers retransmission of packets; traditional SCO packets are not retransmitted. Thisimproves audio quality and the user’s experience. The eSCO packet types 2-EV3 and 3-EV3 offer more timebetween packets, which can improve WiFi performance and allow for other concurrent Bluetooth connections.

Wide Band Speech

Every Bluetooth accessory that is compatible with an Apple product and supports HFP should support a WideBand Speech Connection as described in Section 5.7.4 of the Bluetooth Hands-Free Profile specification version1.6. If Wide Band Speech Connection is supported, it should support the T2 link parameter settings.

All iOS devices running iOS 5 or later support Wide Band Speech.

Audio/Video Remote Control Profile (AVRCP)

To support the Audio/Video Remote Control Profile, a Bluetooth accessory that is compatible with an Appleproduct should support the buttons and operations listed in this section.


CHAPTER 1


Supported Buttons

Every Bluetooth accessory that is compatible with an Apple product and supports the Audio/Video RemoteControl Profile should use separate button commands to play and pause instead of toggling the play orpause state.

Supported Operations

Apple products support the following operation_IDs in Pass Through commands:

PlayStopPauseFast ForwardRewindForwardBackward

Repeat and Shuffle Modes

Every iOS device supports Repeat and Shuffle modes in the role of an AVRCP target. An AVRCP controllermay use SetPlayerApplicationSettingValue to set a value on the iOS device andGetPlayerApplicationSettingValue to read a value, as described in Sections 6.5.4 and 6.4.3 of theBluetooth Audio/Video Remote Control Profile specification version 1.4.

Notifications

Every Bluetooth accessory that is compatible with an Apple product and supports the AVRCP profile shouldregister for notifications and not perform repetitive polling to determine the status of the Apple product.

Every iOS device supports registering for notifications in the role of an AVRCP Target, as described in Section6.7 of the Bluetooth Audio/Video Remote Control Profile specification version 1.4. The commandsRegisterNotification and GetPlayStatus are supported for these notifications:

EVENT_PLAYBACK_STATUS_CHANGEDEVENT_TRACK_CHANGEDEVENT_NOW_PLAYING_CONTENT_CHANGEDEVENT_AVAILABLE_PLAYERS_CHANGEDEVENT_ADDRESSED_PLAYER_CHANGEDEVENT_VOLUME_CHANGED

Volume Handling

Every Bluetooth accessory that is compatible with an Apple product and supports the AVRCP profile shouldsupport Absolute Volume, as described in Section 6.13 of the Bluetooth Audio/Video Remote Control Profilespecification version 1.4.

Every iOS device supports volume handling in the role of AVRCP Controller.

14 Profiles2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


iOS App-Provided Metadata

An audio app running on an iOS device may use the iOS MediaPlayer Framework APIs to provide metadataabout the current audio stream. The iOS device supplies this metadata to the accessory using AVRCP. Formore information, see the MPNowPlayingInfoCenter class in Apple’s MediaPlayer Frameworkdocumentation.

Advanced Audio Distribution Profile (A2DP)

Every Bluetooth accessory that is compatible with an Apple product and supports the Advanced AudioDistribution Profile should meet the requirements of the specification Bluetooth Advanced Audio DistributionProfile, Version 1.2. Additional Apple requirements are specified in this section.

SubBand Codec (SBC)

The SBC Codec Specific Information Elements, defined in Section 4.3.2 of the A2DP specification, that areapplicable to Apple products are listed in Table 1-1 (page 15).

Table 1-1 SubBand Codec Information Elements for Apple products

ValueElement

44,100 HzSampling Frequency

StereoChannel Mode

16Block Length

8Subbands

LoudnessAllocation Method

2 to 53. Bluetooth accessories for Apple products should support 53.Bitpool range

MPEG 2/4 AAC Codecs

iOS devices support the non-mandatory codec MPEG-2/4 AAC, as defined in Section 4.5 of the A2DPspecification, Version 1.2. It is recommended that accessories use the AAC codec in addition to SBC, becauseit provides higher audio quality for a given bit rate.

Note: The following specifications provide details of Apple’s implementation of the MPEG-2/4 AAC codec.In case of conflicts, the A2DP specification governs.

The MPEG 2/4 AAC Codec Specific Information Elements, defined in Section 4.5 of the A2DP specification,that are applicable to iOS devices are listed in Table 1-2 (page 16).


CHAPTER 1


Table 1-2 MPEG-2/4 AAC Codec Information Elements for iOS devices

ValueElement

MPEG-2 AAC LCObject Type

44,100 HzSampling Frequency

2Channels

131,072 bpsBit rate

0VBR

AAC audio stream packets in iOS devices have the structure shown in Table 1-3 (page 16).

Table 1-3 AAC audio packet for iOS devices

MPEG-4 AAC

Audio Payload

MPEG-4 LATM

AudioMuxElement

AVDTP

Header

L2CAP

Header

The AAC Media Payload Format, as defined in Section 4.5.4 of the A2DP specification, is formatted usingLATM, as defined in Section 4 of IETF RFC 3016. The following notes apply to the packet fields shown in Table1-3 (page 16):

■ The suggested L2CAP MTU value for each iOS device’s AAC streaming channel is 885 bytes.

■ The AVDTP Header is shown as the RTP header in Figure 4 of RFC 3016, and is the header defined inSection 7.2.1 of Audio/Video Distribution Transport Protocol, Version 1.2.

■ The AudioMuxElement is the same as the RTP payload in RFC 3016. It is defined in Section 1.7.3, Table1.32 in ISO/IEC 13818-3:2005, subpart 1. The muxConfigPresent argument to the AudioMuxElementis set to 1 (in-band mode), as recommended in Section 4.1 of RFC 3016. As recommended in Section 4.3of RFC 3016, only one AudioMuxElement is put into each AVDTP packet.

■ The audio payload is encoded using MPEG-4, as recommended in Section 4.5.4 of the A2DP specification.

Bluetooth Low Energy

The Bluetooth 4.0 specification introduces Bluetooth Low Energy, a new wireless technology targeted foraccessories with limited battery resources. If Bluetooth LE is supported, the accessory should follow theguidelines in this section.

Role

The Bluetooth accessory should implement either the Peripheral role as defined in the Bluetooth 4.0specification, Volume 3, Part C, Section 2.2.2.3 or the Broadcaster role, as defined in Section 2.2.2.1.

16 Bluetooth Low Energy2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


Advertising Channels

The Bluetooth accessory should advertise on all three advertising channels (37, 38, and 39) at each advertisingevent. See the Bluetooth 4.0 specification, Volume 6, Part B, Section 4.4.2.1.

Advertising PDU

The Bluetooth accessory should use one of the following advertising PDUs:

ADV_INDADV_NOCONN_INDADV_SCAN_IND

ADV_DIRECT_IND should not be used. See the Bluetooth 4.0 specification, Volume 6, Part B, Section 2.3.1.

Advertising Data

The advertising data sent by the Bluetooth accessory should contain at least the following information asdescribed in the Bluetooth 4.0 specification, Volume 3, Part C, Section 11:

FlagsTX Power LevelLocal NameServices

The accessory may put the Local Name and the TX Power Level data in the SCAN_RSP PDU if, for example,it needs to reduce power consumption or not all of the advertising data fit into the advertising PDU. Notethat, depending on its state, the Apple product may not always perform active scanning.

The primary services should always be advertised in the advertising PDU. Secondary services should not beadvertised. Services not significant to the primary use case of the accessory may be omitted if space is limitedin the Advertising PDU.

The advertising data and the scan response data in the SCAN_RSP PDU should comply with the formattingguidelines in the Bluetooth 4.0 specification, Volume 3, Part C, Section 18: it must start with a length field,followed by AD Type and AD Data.

Advertising Interval

The advertising interval of the Bluetooth accessory should be carefully considered, because it affects thetime to discovery and connect performance. For a battery-powered accessory, its battery resources must alsobe considered.

To be discovered by the Apple product, the Bluetooth accessory should first use the recommended advertisinginterval of 20 ms for at least 30 seconds. If it is not discovered within the initial 30 seconds, the accessorymay choose to save battery power and increase its advertising interval. Apple recommends using one of thefollowing longer intervals to increase chances of discovery by the Apple product:

Bluetooth Low Energy 172011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1


645 ms768 ms961 ms1065 ms1294 ms

Note: Longer advertising intervals usually result in longer discovery and connect times.

Connection Parameters

The Bluetooth accessory is responsible for the connection parameters used for the LE connection. Theaccessory should request connection parameters appropriate for its use case by sending an L2CAP ConnectionParameter Update Request at the appropriate time. See the Bluetooth 4.0 specification, Volume 3, Part A,Section 4.20 for details.

The connection parameter request may be rejected if it does not comply with all of these rules:

Interval Max * (Slave Latency + 1) ≤ 2 seconds

Interval Min ≥ 20 ms

Interval Min + 20 ms ≤ Interval Max

Slave Latency ≤ 4

connSupervisionTimeout ≤ 6 secondsInterval Max * (Slave Latency + 1) * 3 < connSupervisionTimeout

The Apple product will not read or use the parameters in the Peripheral Preferred Connection Parameterscharacteristic. See the Bluetooth 4.0 specification, Volume 3, Part C, Section 12.5.

Privacy

The Bluetooth accessory should be able to resolve a Resolvable Private Address in all situations. Due to privacyconcerns, the Apple product will use a Random Device Address as defined in the Bluetooth 4.0 specification,Volume 3, Part C, Section 10.8.

Permissions

The Bluetooth accessory should not require special permissions, such as pairing, authentication, or encryptionto discover services and characteristics. It may require special permissions only for access to a characteristicvalue or a descriptor value. See the Bluetooth 4.0 specification, Volume 3, Part G, Section 8.1, fifth paragraph.


CHAPTER 1


Pairing

The Bluetooth accessory should not request pairing. If, for security reasons, the accessory requires a bondedrelationship with the Central, the Peripheral should reject the ATT request using either the InsufficientAuthorization or Insufficient Authentication error code, as appropriate. See the Bluetooth 4.0 specification,Volume 3, Part F, Section 4 for details.

As a result, the Apple product may proceed with the necessary security procedures.

Pairing may require user authorization depending on Apple product.

Services

Generic Access Profile Service

The Bluetooth accessory should implement the Device Name characteristic per the Bluetooth 4.0 specification,Volume 3, Part C, Section 12.1. The Device Name characteristic should be writeable.

Generic Attribute Profile Service

The Bluetooth accessory should implement the Service Changed characteristic only if the accessory has theability to change its services during its lifetime.

The Apple product may use the Service Changed characteristic to determine if it can rely on previously read(cached) information from the device. See the Bluetooth 4.0 specification, Volume 3, Part G, Section 7.1.

Device Information Service

The Bluetooth accessory should implement the Device Information Service. The service UUID for this serviceshould not be advertised in the Advertising Data. The following characteristics should be supported:

Manufacturer Name StringModel Number StringFirmware Revision StringSoftware Revision String

Bluetooth Low Energy 192011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 1



CHAPTER 1


This chapter describes Apple resources that can help you to get developer support for Apple-compatibleBluetooth accessory designs and to extend accessory capabilities beyond those supported by standardBluetooth profiles.

Apple Bluetooth Development Mailing List

Questions or comments regarding Bluetooth accessory development for Apple products can be posted tothe Apple mailing list for Bluetooth development, [email protected]. To become a member ofthis mailing list, visit lists.apple.com/mailman/listinfo/bluetooth-dev.

Engineers on the Apple Bluetooth development team monitor this mailing list and will try to answer yourquestions. Please search the archives first, to see if your topic has already been discussed.

The iPod Accessory Protocol

Third-party accessories can use the iPod Accessory Protocol (iAP) to access advanced features of iOS devices.One such feature is the ability to communicate securely with third-party iOS applications via the iOS ExternalAccessory Framework. For information about the External Accessory Framework, see External AccessoryProgramming Topics on the Apple iOS Developer site.

To incorporate iAP into an accessory design, the accessory developer must be a member of the Apple MFilicensing program and integrate specific MFi hardware into the accessory. For further information about MFi,see developer.apple.com/programs/mfi.

Headset Battery Level Indication

Any Hands-Free Bluetooth headset accessory can show its battery level to the user as an indicator icon inthe iOS device status bar. This feature is supported on all iOS devices that support the Hands-Free Profile,including iPhone, iPod touch, and iPad.

Headset battery indication is implemented by two iOS-specific Bluetooth HFP AT commands, “HFP CommandAT+XAPL” (page 22) and “HFP Command AT+IPHONEACCEV” (page 22)

Apple Bluetooth Development Mailing List 212011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 2

Apple Protocols and Developer Support

http://[email protected]

http://lists.apple.com/mailman/listinfo/bluetooth-dev

http://developer.apple.com/library/ios/#featuredarticles/ExternalAccessoryPT/Introduction/Introduction.html%23//apple_ref/doc/uid/TP40009502

http://developer.apple.com/library/ios/#featuredarticles/ExternalAccessoryPT/Introduction/Introduction.html%23//apple_ref/doc/uid/TP40009502

http://developer.apple.com/programs/mfi

HFP Command AT+XAPL

Description: Enables custom AT commands from a headset.

Initiator: Headset.

Format: AT+XAPL=[vendorID]-[productID]-[version]-[features]

Parameters:

■ vendorID:A string representation of the hex value of the USB vendor ID from the manufacturer, withoutthe 0x prefix.

■ productID: A string representation of the hex value of the USB product ID from the manufacturer,without the 0x prefix.

■ version: The revision of the software.

■ features: A base-10 representation of a bit field. Available features are:

❏ 1 = the headset supports battery reporting.

❏ 2 = the headset is docked or powered.

❏ All other values are reserved.

Example: AT+XAPL=ABCD-1234-0100,3

Response: +XAPL=iPhone,[features]

HFP Command AT+IPHONEACCEV

Description: Reports a headset state change.

Initiator: Headset.

Format: AT+IPHONEACCEV=[Number of key/value pairs],[key1],[val1],[key2],[val2],...

Parameters:

■ Number of key/value pairs: The number of parameters coming next.

■ key: the type of change being reported.

❏ 1 = battery level.

❏ 2 = dock state.

■ val: the value of the change.

❏ Battery events: A string value between '0' and '9'.

❏ Dock state: 0 = undocked, 1 = docked.

Example: AT+IPHONEACCEV=1,1,3

22 Headset Battery Level Indication2011-10-14 | © 2011 Apple Inc. All Rights Reserved.

CHAPTER 2

Apple Protocols and Developer Support

This table describes the changes to Bluetooth Accessory Design Guidelines for Apple Products.

NotesDate

Revision R5:2011-10-14

Moved “Headset Battery Level Indication” section to Apple Protocols chapter.

Moved Low Energy chapter to Chapter 2.

Added new section “Wide Band Speech” (page 13).

Added new section “Apple Bluetooth Development Mailing List” (page 21).

Added new section “Headset Battery Level Indication” (page 21).

Added new material to section “Audio/Video Remote Control Profile(AVRCP)” (page 13).

Clarified Remote Audio Volume Control and added Low Energy section.

Made other corrections and updates.

Revision R4: Changed specification language from requirements to guidelines.2011-04-04

Revision R3: Added Macs as Apple products covered by this specification.2011-03-04

Changed title of document from “Bluetooth Accessory Design Guidelines foriOS Devices” to “Bluetooth Accessory Design Guidelines for Apple Products.”

Revised definition of Vendor ID source in “Device ID Profile (DID)” (page 11).

Revision R2: Retitled document from Designing Bluetooth Acccessories for iOSDevices.

2010-11-30

Corrected generic references to Apple devices, iOS devices, and iPods throughoutthe document; see “IMPORTANT” (page 7).

Expanded specifications in section “Advanced Audio Distribution Profile(A2DP)” (page 15).

Made minor other corrections and updates.

Revision R1: First release.2010-09-08


REVISION HISTORY

Document Revision History


REVISION HISTORY

Document Revision History

Apple Bluetooth Accessory Design Guidelines

Documents

Transcript of Apple Bluetooth Accessory Design Guidelines