Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

MCPC TR-007
Bluetooth Audio
Technical Reference
Version 1.0
Revision 2
February. 9th, 2007

Mobile Computing Promotion Consortium(MCPC)

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

1

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Revision History
Version
V0.50
V0.51
V0.60
V0.70
V0.71
V0.80Draft
V0.89Draft1
V0.89Draft2
V0.89Draft3
D0.90r1
D0.90r2
D0.90r4
D0.90r5
D0.90r6
D1.00r0
V1.00
V1.00r1

V1.00r2

Date
2005/04/15
2005/06/14
2005/07/05
2005/10/11
2005/11/07
2005/11/28
2006/01/17
2006/02/16
2006/02/19
2006/02/21
2006/02/22
2006/02/23
2006/03/07
2006/03/08
2006/03/13
2006/03/14
2006/03/28

2007/2/7

Description
All
All
All
All
All
All

Details
New Document
Review
Translation.

Change numbering of document following to SIG

Obtaining Company ID
Fixing all issues.
Released
Modify following SIG AVRCP V.1.3 as below.
“Device Settings” is replaced with “Player
Application Settings”.
“GetPlayStatus” PDU ID is moved to “Notification
PDUs” from “Media Information PDUs”, and ischanged PDU ID to 0x30 from 0x21.
PDU ID of “RegisterNotification” is replaced with
0x31.
PDU ID of “SuspendNotify” is replaced with 0x32.
PDU ID of “ResumeNotify” is replaced with 0x33.
“5.6. PASS THROUGH COMMAND” is renamed to“Basic Group Navigation”, and the contents are
modified.
“5.1 Configuration PDUs” is replaced with “5.1Capabilities PDUs”.
Modify “Table 4.2.1 List of command”.
Modify “Table 4.2.2 List of PASS THROUGHCOMMAND”.
- Reflect a document of SIG AVRCP D16r03 to thisdocument.
- Remove command of SuspendNotify(5.4.3)- Remove command of ResumeNotify(5.4.4)- Modify “5.1.1 GetCapabilities”- Added Appendix 4- minor editorial changes.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

2

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Contributors
Masahiko Seki
Haruhiko Kaneko
Mitsuyoshi Yasuda
Akio Konishi
Masahiko Nakashima
Katsutoshi Arata
Kenji Kagami
Soichi Saito
Fusako Inotsume
Issei Sugawara
Seiichi Suzuki
Hiroyuki Morimoto
Kazuhiko Sawaki
Hiroshi Matsuya
Makoto Yamashita
Shuichi Sakurai
Baskar S.
K. A. Srinivasan
Ankit Jain

Sony Corporation
Sony Corporation
Sony Ericsson Mobile Communications Japan,
FUJITSU DEVICES INC.,
FUJITSU DEVICES INC.,
FUJITSU TEN LIMITED
FUJITSU TEN LIMITEDDENSO CORPORATION
Pioneer Corporation
Clarion Co., Ltd.
Clarion Co., Ltd.
Mitsubishi Electric Corporation
Johnson Control Inc.,TOSHIBA CORPORATIONTOSHIBA CORPORATIONTOSHIBA CORPORATION
Impulsesoft
Impulsesoft
Impulsesoft

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

3

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

MCPC Bluetooth Audio Sub Working Group Members (Alphabetical Order)
ALPINE ELECTRONICS, INC.
ALPS ELECTRIC CO., LTD.
Clarion Co., Ltd.
DENSO CORPORATIONELECOM CO., LTD.
e-w/you Inc.
FUJITSU LIMITED
FUJITSU DEVICES INC.,
FUJITSU TEN LIMITED

Nobuki Asai
Masanobu Ujiie, Talguk Kim
Issei Sugawara, Seiichi Suzuki
Hideaki Suzuki, Masashi Miura, Soichi Saito
Shuji Terakado
Shunsuke Matsuda, Y. Ohkubo
Yoshihiro Takamatsuya
Akio Konishi, Masahiko Nakashima
Katsutoshi Arata, Yoshitaka Hirashima,
Kenji Kagami
Motohisa Higuchi
Baskar S., K. A. Srinivasan, Ankit Jain
K. Akahori

Hitachi, Ltd.
Impulsesoft Private Limited.
Japan Automobile Manufacturers Association,
Inc. (JAMA)
Johnson Controls, Inc.
KDDI CORPORATIONMITSUBISHI ELECTRIC CORPORATION

Kazuhiko Sawaki
J. Ikeno, Y. Yamada
Hiroyuki Morimoto, Riko Yagiu,
Shuichi Nishikawa, Takanori Niwa
H. Abe, Hiroshi Fujikake,
K. Nakamori, Naoya Funakoshi
Kazuhiro Okada
Stephane Bouet, Tomoyuki Suzuki,
Toshiki Haga
Koichi Sawai, Kosuke Kakuno, Toru Tanaka
Shunsuke Nakajima, Yasuhiro Sakaguchi
Akinori Ohta
Fusako Inotsume
Hiroki Seyama
Haruhiko Kaneko, Masahiko Seki
Mitsuyoshi Yasuda

MITSUMI ELECTRIC CO., LTD.
Mobilecast Inc.
Murata Manufacturing Co., Ltd.
NISSAN MOTOR CO., LTD. Representative for
JAMA
NTT DoCoMo, Inc.
Open Interface Inc.
Panasonic Mobile Communications Co., Ltd.
Pioneer Corporation
SANYO Electric Co., Ltd.
Sony Corporation
Sony Ericsson Mobile Communications Japan,
Inc.
TAIYO YUDEN CO., LTD.

Daigo Kobayashi, Hiroshi Kato,
Terumichi Nakashima, Youjiro Shimizu
Hiroshi Matsuya, Makoto Yamashita,
Shuichi Sakurai
Satoshi Miyazaki, Shio Kubo

TOSHIBA CORPORATION
Vodafone K.K.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

4

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Document Terminology
The MCPC has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of
the words “shall”, “should”, “may” and “can” in the development of documentation, as follows.
z

The word shall is used to indicate mandatory requirements strictly to be followed in order toconform to the standard and from which no deviation is permitted (shall equals is required to).

z

The use of the word must is deprecated and shall not be used when stating mandatory
requirements; must is used only to describe unavoidable situations.

z

The use of the word will is deprecated and shall not be used when starting mandatory
requirements; will is only used in statements of fact.

z

The word should is used to indicate that among several possibilities on is recommended as
particularly suitable, without mentioning or excluding others; or that a certain course ofaction is preferred but not necessarily required; or that (in the negative form) a certain courseof action is deprecated but not prohibited (should equals is recommended that).

z

The word may is used to indicate a course of action permissible within the limits of thestandard (may equals is permitted).

z

The word can is used for statements of possibility and capability, whether material, physical or
causal (can equals is able to).

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

5

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Content
Revision History ..............................................................................................................................................2
Contributors ....................................................................................................................................................3
Document Terminology ...................................................................................................................................5
Content ............................................................................................................................................................61
Introduction .............................................................................................................................................8
1.1. Scope ....................................................................................................................................... 8
1.2. System..................................................................................................................................... 9
1.3. AVRCP Definition ................................................................................................................... 9
1.4. Basic concept......................................................................................................................... 10
2. Usage Model...........................................................................................................................................112.1. Basic usage model................................................................................................................. 11
3. Data Representation .............................................................................................................................123.1. Transfer Byte Order ............................................................................................................. 123.2. Protocol Data Unit Format .................................................................................................. 123.3. PASS THROUGH command (vendor unique) ..................................................................... 13
3.4. VENDOR-DEPENDENT Command.................................................................................... 14
4. List of command for support .................................................................................................................15
4.1. Feature Support ................................................................................................................... 15
4.2. List of commands for AVRCP Enhancement ....................................................................... 16
5. Function of each command and parameter..........................................................................................18
5.1. Capabilities PDUs ................................................................................................................ 18
5.1.1.
GetCapabilities (PDU ID: 0x10) ................................................................................... 18
5.2. Player Application Settings PDUs....................................................................................... 21
5.2.1.
ListPlayerApplicationSettingAttributes (PDU ID: 0x11)............................................ 21
5.2.2.
ListPlayerApplicationSettingValues (PDU ID: 0x12).................................................. 22
5.2.3.
GetCurrentPlayerApplicationSettingValue (PDU ID: 0x13) ...................................... 23
5.2.4.
SetPlayerApplicationSettingValue (PDU ID: 0x14) .................................................... 24
5.2.5.
GetPlayerApplicationSettingAttributeText (PDU ID: 0x15)....................................... 25
5.2.6.
GetPlayerApplicationSettingValueText (PDU ID: 0x16) ............................................ 26
5.2.7.
InformDisplayableCharacterSet (PDU ID: 0x17) ........................................................ 27
5.2.8.
InformBatteryStatusOfCT (PDU ID: 0x18) ................................................................. 29
5.3. Media Information PDUs ..................................................................................................... 30
5.3.1.
GetElementAttributes (PDU ID: 0x20) ........................................................................ 31
5.4. Notification PDUs................................................................................................................. 33
5.4.1.
GetPlayStatus (PDU ID: 0x30) ..................................................................................... 33
5.4.2.
RegisterNotification (PDU ID: 0x31)............................................................................ 34
5.5. Continuing PDUs.................................................................................................................. 39
5.5.1.
RequestContinuingResponse (PDU ID: 0x40).............................................................. 39
5.5.2.
AbortContinuingResponse (PDU ID: 0x41).................................................................. 40
5.6. Basic Group Navigation ....................................................................................................... 41
5.6.1.
Next Group (vendor unique id: 0x00) ........................................................................... 41
5.6.2.
Previous Group (vendor unique id: 0x01)..................................................................... 41
6. Error handling .......................................................................................................................................42
7. Error Status Code..................................................................................................................................427.1. Error Status Code................................................................................................................. 42

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

6

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

8. List of Figures........................................................................................................................................43
9. List of Tables..........................................................................................................................................44
10.
Appendix 1..........................................................................................................................................45
10.1.
Attribute IDs ..................................................................................................................... 45
11.
Appendix 2..........................................................................................................................................46
11.1.
PlayerApplicationSettingAttributeIDs ............................................................................ 46
12.
Appendix 3..........................................................................................................................................47
12.1.
Message Sequence Chart (MSC) ...................................................................................... 47
12.2.
Player Application Setting PDUs ..................................................................................... 48
13.
Appendix 4..........................................................................................................................................54
14.
Appendix 5..........................................................................................................................................55
14.1.
AV/C Transaction Rules................................................................................................... 55
14.2.
Timers and Counters ........................................................................................................ 55
15.
References ..........................................................................................................................................56

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

7

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

1

Introduction

1.1. Scope
A demand for wireless device has been increasing along with the growth of portable music
players in the market.
Wireless device is specialized for remote controlled function in AV profile that is regulated byBluetooth wireless communication technology.
However, most of wireless devices in the market have representational functions at remotecontroller to display music.
If specification for displaying or controlling application of AV profile is different from one toanother, it loses commonality of Bluetooth technology enabled device.
Also, MCPC holds concern about connecting of each product, which is manufactured by eachmanufacturer, cannot be ensured enough.
For above, MCPC has defined a technical reference to transfer the music data to be moreconvenient for users using Bluetooth Technology. It gives rise to an improvement in connectivity of
products such as portable music player and car-mounted devices (e.g. Headphone). In addition, it
enables to support users to implement AV profile correctly for the following items.
・Recommended sequence
・Recommended parameter of commands
・How to use vendor’s optional parts
This technical reference is applied to an application for AV PROFILE.
And Basic Commands and sequence is based on “AVRCP V.1.0 Adapted” which is published byBluetooth SIG Inc,.
[Note]
The contents of this document shall be non-binding, and shall not infringe any rights ofBluetooth®.
The use of this document or any of the contents thereof shall be made at the
responsibility of each user. MCPC makes no warranties whatsoever, whether expressed or
implied, with regard to any matters relating to this document or contents thereof, including,
without limitation, any infringement of legal right, marketability, or fitness for a particularpurpose.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

8

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

1.2. System
Following Figure 1 shows an example of system configuration defined by this technicalreference.

STEREO
Speaker(Sink unit)
Decoder・SBC(Std.)・other.(Opt.)(Source unit)
Encode・SBC(Std.)・other.(Opt.)

A2DP
AVRCP w/ Enhanced

Portable Music Player(CD , MD , HDD , Memory , Mobile Phone)

Controller
Switch and Display
e.g. Car Audio , Hoem Audio and Headphone(Controller)

e.g. Mobile Phone , Portable Player(Terget/Controller)

Figure 1 example system configuration

1.3. AVRCP Definition- Car audio/Home audio/Headphone/Mobile Phone are CT, and Mobile Phone/Portable audio
players are TG.
- CT supports operation_id that corresponds to Category 1(Player/Recorder).
**Does not support Recorder.
- Moreover, it is required to expand function depending on VENDOR DEPENDENT Command or
PASS THROUGH Command (VENDOR UNIQUE).
- MCPC applies for Vendor ID. ID owned by each vendor is defined by VENDOR DEPENDENT.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

9

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

1.4. Basic conceptz The purpose is to expand the area that cannot be covered by PASS THROUGH command /response of AVRCP.
z Expand without changing the basic part of AVRCP. Thus, CT is assigned to control, and TG
is assigned to be controlled as ROLE.
z Assume following items to be connected.
CT: Car audio / Home Audio / AV Headphone / Mobile Phone etc
TG: Mobile Phone / Portable audio player etc.
z Use Vendor Unique of PASS THROUGH command/response for key undefined by PASS
THROUGH command / response of AVRCP.
z Use VENDOR DEPENDENT command / response to send / receive data（Information ofmeta and status etc.）.
z TG gives a response as corresponding to command given by CT. This is considered as abasic operation for sequence. If change in the status is made and need to notify it from TG
actively, use NOTIFY command of AVRCP to register for issuing a defined NOTIFY
command tells the change from CT. When NOTIFY command is issued, status is sent to CT
with the use of INTERIM response from TG, CHANGED response is used to notify thechange made in the status later.
z Considering the case which VENDOR DEPENDENT command/response cannot stored in
MTU (512 bytes) of AVRCP in one time, MCPC provides for mechanism to continue sending
command / response, and to receive / send large data.
z Following an AVRCP disconnection, CT and TG shall not assume that any state from theprevious connection is valid (such as Player Application Setting, Character Set,
RegisterNotification).
z When you develop Bluetooth wireless technology enabled devices/products using thisTechnical Reference, you should refer the latest version of Bluetooth SIG publisheddocument during your development and before you release your devices/products toMarket.
z The “Company ID”, which is appearing in this documentation, is for this Technical
Reference, not same as “Company ID” for Bluetooth SIG.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

10

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

2. Usage Model
2.1.

Basic usage model.

The basic usage model is shown in Figure 2.

AV Headphone

DP P
A2 RC
AV

d
ce
an
h
En
w/

Portable Music Player(CD , MD , HDD , Memory , Mobile Phone)・Remote Control
・Commander
w/ LCD Panel<Indicating>Title , Artist
Album , Time , etc.

Figure 2 Basic usage model

The CT is a headphone with LCD display and the TG is a portable audio player like as
CD, HDD, Memory, and Mobile Phone.
The user can listen to the music with the headphone through A2DP connection andcan control the portable audio player through standard AVRCP connection.
In addition, the user also can see some information on the LCD display throughenhanced AVRCP connection that is defined in this document.
Types of information that can be displayed are Track Name, Artist Name, Album
Name, Time, etc.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

11

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

3. Data Representation
3.1. Transfer Byte OrderMultiple-byte fields are transferred in standard network byte order (Big Endian), with moresignificant (high-order) bytes being transferred before less-significant (low-order) bytes.
3.2. Protocol Data Unit Format
The vendor_dependent_data field in the vendor dependent command/response frames will be a
PDU (Protocol Data Unit). Every PDU consists of a PDU Identifier, length of all parameters(excluding the parameter length field) and the PDU-specific parameters.
Oct

MSB (7)

6

5

4

0
1

3

2

1

LSB (0)PDU ID
Reserved

Packet Type

2-3

Parameter Length4-nParameter (Number of parameters determined by Parameter Length)

PDU format

The PDU fields are briefly described below:
PDU ID: The PDU ID is used to identify the specific command/response with unique identifier foreach operation.
Packet Type: The Packet Type field qualifies each packet as either first (Packet Type=01), continue(Packet Type=10), or end packet (Packet Type=11). In the case of a non-fragmented message, thisfield (Packet Type=00) simply indicates that the message is sent in a single AV/C frame.
The packets are fragmented by the sender so as to be able to accommodate into the 512 bytes AV/C
packet size restriction. Receivers have the flexibility to request continuation packets at theirconvenience from the sender or abort the continuation request. Note: if the L2CAP MTU is lessthan 512 bytes, AVCTP will also apply fragmentation to each of the AV/C packets. All responsefragments shall have the same PDU ID as the original request.
A sender shall not interleave fragmented PDUs. Once a sender has sent a start fragment it shall
only send further fragments of that PDU until that PDU is completed or aborted. If a receiverreceives a start fragment or non-fragmented Metadata-Transfer message when it already has anincomplete fragment from that sender then the receiver shall consider the first PDU aborted. A
PASSTHROUGH command may be interleaved in fragmented Metadata-Transfer communication
without aborting it.
Parameter Length: The parameter Length field specifies the length of the all the parameters
following the Parameter Length field.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

12

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Parameter1 …n: These are the parameters for the specific operations performed and are describedin sections below.
An example command (GetCapabilities) PDU will be as follows:
Oct

MSB (7)

6

0

5

4

3

2

0x0

1

1

Ctype: 0x1 (STATUS)

Subunit_type:0x9 (PANEL)

Subunit_ID: 0x0

2

Opcode: 0x0 (VENDOR DEPENDENT)

3–5

Company ID: 0x0017A7 MCPC registered CompanyID

6

PDU ID (0x10 - Get Capabilities)

7

LSB (0)Reserved (0x00)

Packet Type (0x0)8–9Parameter Length (0x0001)

10

Capability ID (0x1 - PROFILE VERSION)
Table 3.2.1 An example command (GetCapabilities) PDU

The grayed portion in table above indicates the PDU inside an AV/C Vendor dependent command
frame.
3.3.

PASS THROUGH command (vendor unique)

PASS THROUGH Command (vendor unique) FrameOct

MSB (7)

6

0

5

3

0x0

1

2

1

LSB (0)

Ctype: 0x0 (CONTROL)

Subunit_type:0x9 (PANEL)2
3

4

Subunit_ID: 0x0

Opcode: 0x7C (PASS THROUGH)
State_flag *2

Operation_ID: 0x7E (VENDOR UNIQUE)

4Operation_data_field_length: 0x5

5-7

Company ID: 0x0017A7

8-9

Vendor_unique_id
Table 3.3.1 PASS THROUGH Command FramePASS THROUGH Response (vendor unique) FrameOct

MSB (7)

0

5

4

3

0x0

1

2

1

LSB (0)

Response *1

Subunit_type:0x9 (PANEL)2
3

6

Subunit_ID: 0x0

Opcode: 0x7C (PASS THROUGH)
State_flag*2

Operation_ID: 0x7E (VENDOR UNIQUE)

4Operation_data_field_length: 0x5

5-7

Company ID: 0x0017A7

8-9

Vendor_unique_id
Table 3.3.2 PASS THROUGH Response Frame*1 0x8(NOT_IMPLEMENTED), 0x9 (ACCEPTED), 0xA (REJECTED)*2 A CT sends a command frame with its state_flag field in value 0 when a button is pushed and in value 1 when
the button is released.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

13

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

3.4.

VENDOR-DEPENDENT Command(VENDOR DEPENDENT Command Frame)
Oct

MSB (7)

6

0

5

4

3

2

0x0

1

1
Ctype : *1

Subunit_type:0x9 (PANEL)

Subunit_ID: 0x0

2

Opcode: 0x0 (VENDOR－DEPENDENT)

3–5

Company ID: 0x0017A7

6

PDU ID7

LSB (0)

P_type : *2

Reserved (0x0)8–9Parameter Length

10 – nParameter(s)*1 0x0 (CONTROL), 0x1 (STATUS), 0x3 (NOTIFY)*2 Packet type : 00(Non_Fragmented), 01(First), 10(Continue), 11(End)

Table 3.4.1 VENDOR DEPENDENT Command Frame(VENDOR DEPENDENT Response Frame)
Oct0
1

MSB (7)

6

5

4

3

0x0

2

1

Response:*3

Subunit_type:0x9 (PANEL)

Subunit_ID: 0x0

2

Opcode: 0x0 (VENDOR－DEPENDENT)

3–5

Company ID: 0x0017A7

6

PDU ID7

LSB (0)

P_type : *2

Reserved (0x0)8–9Parameter Length

10 – nParameter(s)*3 0x8 (NOT_IMPLEMENTED), 0x9 (ACCEPTED), 0xA (REJECTED), 0xC (STABLE),
0xD (CHANGED), 0xF (INTERIM)

Table 3.4.2 VENDOR DEPENDENT Response Frame

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

14

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

4. List of command for support
4.1.

Feature Support

The table below shows the feature requirements for this profile. Note that a device may
have both CT and TG capabilities. In that case, features for both CT and TG are required.
FeatureSupport in

Support in

CT

TG

1.

Connection establishment for control

M

O

2.

Release connection for control

M

M

3.

Sending UNIT INFO command

O

X

4.

Receiving UNIT INFO command

X

M

5.

Sending SUBUNIT INFO command

O

X

6.

Receiving SUBUNIT INFO command

X

M
3

7.

Sending VENDOR DEPENDENT command

C*

X

8.

Receiving VENDOR DEPENDENT command

X

C*3

9.

Sending PASS THROUGH command

M

X

10.

Receiving PASS THROUGH command

X

M

11.

Capabilities

O

C*1

12.

Player Application Settings

O

O

13.

Metadata Attributes

O

C*1

14.

Notifications

C*2

C*2

15.

Continuation

C*2

C*2

16.

Basic Group Navigation

O

O

Table 4.1.1 Application Layer Features

C*1 – Mandatory if Target supports Category 1 or optional otherwise
C*2 – Mandatory if Controller supports Metadata Attributes or optional otherwise
C*3 – Mandatory if any of 11,12,13, 14, 15 features are supported or optional otherwise* Note that sending and receiving VENDOR DEPENDENT commands are Option in original AVRCP
document. However some VENDOR DEPENDENT commands in this document shall be Mandatory so thatthese supports also shall be Mandatory.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

15

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

4.2.
List of commands for AVRCP Enhancement
List of commands are given in Table 4.2.1

Section

PDU
ID

5.1
5.1.1

PDU Support in CT support in TG
Commands

AV/C Command
Type

CT

TG

TG
ResponseTime

STATUS

M

M

TMTP

Capabilities
0x10

5.2

GetCapabilities
Player Application Setting

5.2.1

0x11

ListPlayerApplicationSettingAttributes

STATUS

M

M

TMTP

5.2.2

0x12

ListPlayerApplicationSettingValues

STATUS

O

M

TMTP

5.2.3

0x13

GetCurrentPlayerApplicationSettingValueSTATUS

C*2

M

TMTP

5.2.4

0x14

SetPlayerApplicationSettingValueCONTROL

C*2

M

TMTC

5.2.5

0x15

GetPlayerApplicationSettingAttributeText

STATUS

O

C*1

TMTP

5.2.6

0x16

GetPlayerApplicationSettingValueText

STATUS

O

C*1

TMTP

5.2.7

0x17

InformDisplayableCharacterSet

CONTROL

O

O

TMTC

5.2.8

0x18

InformBatteryStatusOfCTCONTROL

O

O

TMTC

STATUS

M

M

TMTP

5.3
5.3.1

Media Attributes
0x20

5.4

GetElementAttributes
Notification

5.4.1

0x30

GetPlayStatus

STATUS

O

M

TMTP

5.4.2

0x31

RegisterNotification

NOTIFY

M

M

TMTP

5.5

Continuing

5.5.1

0x40

RequestContinuingResponse

CONTROL

M

M

TMTC

5.5.2

0x41

AbortContinuingResponse

CONTROL

M

M

TMTC

Table 4.2.1 List of command

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

16

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Notes
C*1 If player application setting attribute IDs for menu extension (Refer to Appendix 2) aresupported then mandatory or optional otherwise.
C*2 Either Get or Set player application settings shall be mandatory.
Requirements for CT refer to the ability to send a command.
Requirements for TG refer to the ability to respond to a command. The AV/C command type of the
response PDU shall be per the AV/C specification's definitions for responses.
For error response PDU the response parameter is always the error code independent of the
response format defined for ACCEPTED PDU response for the corresponding PDU command.
All strings passed in Technical reference PDUs are not null terminated.
TMTC is the time period before which TG is expected to generate a response frame for CONTROL
commands. (Refer to Appendix 5)
TMTP is the time period before which TG is expected to generate a response frame for interim
response for NOTIFY commands and final response for STATUS commands. (Refer to Appendix 5)

The Technical reference feature adds the following operations that shall be used with PASS
THROUGH command:

Section

VendorUniqueID

5.6

Operation Name

AV/C Command
Type

CT

TG

Basic Group Navigation

5.6.1

0x0000

Next GroupCONTROL

M

M

5.6.2

0x0001

Previous GroupCONTROL

M

M

Table 4.2.2 List of PASS THROUGH COMMAND

These PASS THROUGH commands shall use MCPC registered CompanyId as the opcode with thedefined vendor unique Id with the PANEL subunit-type.
Requirements for CT refer to the ability to send a command.
Requirements for TG refer to the ability to respond to a command.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

17

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5. Function of each command and parameter
5.1. Capabilities PDUs
5.1.1. GetCapabilities (PDU ID: 0x10)
Description:
This primitive gets the capabilities supported by remote device. This could be sent by CT to inquirecapabilities of the peer device.
Command format (GetCapabilities)
Parameters
Size(byte)
CapabilityID
1

Description
Specific
capability
requested.

Allowed Values
Defined CapabilityIDs
are:
PROFILE_VERSION(0x1): This requests
the profile version
supported by remotedeviceCOMPANY_ID (0x2):
This requests the listofCompanyID
supported by TG.
EVENTS_SUPPORTE
D (0x3): This requests
the list of events
supported by the TG.
TG is expected torespond with all theeventssupported
includingthemandatory
eventsdefinedinthisspecification.
Other CapabilityIDs
are reserved

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

18

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

GetCapabilities Response format for PROFILE_VERSION
ParameterscapabilityID

Size(byte)
1

Description
Specific capability requested

Allowed Values
PROFILE_VERSIONCapabilityCount (n)1Capability

1…nSpecifies the length of capability
value
returnedforaCapabilityID
Capability provided

Current
profileversion supported is“1_00”

GetCapabilities Response for COMPANY_ID
ParameterscapabilityID

Size(byte)
1

Description
Specific capability requested

CapabilityCount (n)1Capability

3…3*nSpecifies
thenumberCOMPANY_ID returned
List of COMPANY_ID

Allowed Values
COMPANY_ID
of

1-255
CompanyID
value
range as defined in
AV/C
VENDOR_DEPENDE
NT command frame.
Each CompanyID is 3
bytes long.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

19

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

GetCapabilities Response for EVENTS_SUPPORTEDParameterscapabilityID

Size(byte)
1

Description
Specific capability requested

CapabilityCount (n)1Capability

2…nSpecifies the number of events
supported returned
List of EventsIDs

Allowed Values
EVENTS_SUPPORTE
D
2-255
Minimumoftwomandatory EventIDs
defined in Appendix 4
is returned.
EventIDs are 1 byte
each.

NOTE: The CT should be aware that the capabilities supported by the TG may be subject tochange. This may occur if the application on the TG changes, or the application changes mode,
for instance different functionality may be available when the TG is playing locally stored audio
tracks to when it is acting as a radio. How this is handled by the CT is implementation
dependent. If the TG application changes to support less functionality the CT may receive error
responses indicating that the function requested is not implemented. The CT may then decide toreissue the GetCapabilities to get the most current capabilities. If the TG application changes tosupport more features the CT may be happy to continue using the original set of features
supported. If not it may choose to occasionally poll the TG with a GetCapabilities to determine
when further capabilities are available.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

20

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2. Player Application Settings PDUs
The player application settings PDU provides mechanism for controller devices to query player
application setting attributes, get and set specific setting value for these attributes.
It is assumed that all player application settings are available on the target as an <attribute,value> pair. It is assumed for each device attribute there shall be multiple possible values, with
one of them being the current set value.
The specification defines pre-defined attributes and values for some of the commonly used player
application settings. The PDUs allow for extensions to the pre-defined attributes and values
defined in the target and are accessible to the controller, along with displayable text. This willallow controllers without the semantic understanding of the target’s player application setting to
be able to display setting related text and provide users mechanism to operate on the player
application settings.
Each player application setting has a unique AttributeID and the attributes have values that havea valueID. Target-defined attributes and values have displayable text associated with them forallowing controllers to query for this information.
The following PDUs provide the needed functionality for controller devices to access and set
attribute value on the target device.
5.2.1. ListPlayerApplicationSettingAttributes (PDU ID: 0x11)
Description:
This primitive request the target device to provide target supported player application setting
attributes. The list of reserved player application setting attributes is provided in Appendix 2. It is
expected that a target device may have additional attributes not defined as part of this technicalreference.

Command format (ListPlayerApplicationSettingAttributes)
Parameters
Size(byte) Description
None
Response format (ListPlayerApplicationSettingAttributes)
Parameters
Size(byte) Description
NumPlayerApplicatio
1
Number of attributes provided
nSettingAttributes(N)PlayerApplicationSetti 1
Specifies the player application
ngAttributeID
setting attribute ID

Allowed Values

Allowed Values
0-255

See Appendix 2 for thelistofPlayer
Application
Setting
attribute IDs
And so on for the number of target defined player application setting attributes (N).

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

21

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.2. ListPlayerApplicationSettingValues (PDU ID: 0x12)
Description:
This primitive requests the target device to list the set of possible values for the requested player
application setting attribute. The list of reserved player application setting attributes and theirvalues are provided in Appendix 2. It is expected that a target device may have additional
attribute values not defined as part of this technical reference.

Command format (ListPlayerApplicationSettingValues)
Parameters
Size(byte)
Description
PlayerApplicationSetti 1
Player application setting attributengAttributeID
ID

Response format (ListPlayerApplicationSettingValues)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player application setting
nSettingValues (N)valuesPlayerApplicationSetti
ngValueID1

1

Specifies the player
setting value ID

application

Allowed Values
Playerapplication
setting attribute IDasdefinedinAppendix
2
orreceived from thetargetAllowed Values
1-255

See Appendix 2 forlistofreserved
playerapplication
setting values.
Additional
valuesmay
be provided by thetargetfortherequested
playerapplication
setting
attributeAnd so on for the number of target defined player application setting values (N).

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

22

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.3. GetCurrentPlayerApplicationSettingValue (PDU ID: 0x13)
Description:
This primitive requests the target device to provide the current set values on the target for theprovided player application setting attributes list.

Command format (GetCurrentPlayerApplicationSettingValue)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player application setting
nSettingAttributeID
attribute for which current set(N)values are requested
PlayerApplicationSetti
ngAttributeID1

1

Player application setting attribute
ID for which the corresponding
current set value is requested

Allowed Values
1-255

Valid
PlayerApplicationSet
tingAttributeIDvalues received fromthe target, or definedas part of Appendix 2

And so on for the number of target defined player application setting attributes in the requested
order (N).
Response format (GetCurrentPlayerApplicationSettingValue)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player
nSettingValues (N)settings value provided

application

Allowed Values
1-255

PlayerApplicationSetti
ngAttributeID1

1

Player application setting attribute
ID for which the value is returned

1-255

PlayerApplicationSetti
ngValueID1

1

Currently set player application
setting value on the target for thecorresponding requested player
application setting attribute ID

ValidPlayerApplicationSet
tingValueID values
received from thetarget, or defined aspart of Appendix 2

And so on for the number of target defined player application setting values in the requested order(N).

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

23

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.4. SetPlayerApplicationSettingValue (PDU ID: 0x14)
Description:
This primitive requests to set the player application setting list of player application setting values
on the target device for the corresponding defined list of PlayerApplicationSettingAttributes.

Command format (SetPlayerApplicationSettingValue)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player application setting
nSettingAttributes (N)attributes for which the player
application setting

Allowed Values
1-255

PlayerApplicationSetti
ngAttributeID1

1

Player application setting attribute
ID for which the value needs to be
set

Valid
PlayerApplicationSet
tingAttributeIDvalues received fromthe target, or definedas part of Appendix 2

PlayerApplicationSetti
ngValueID1

1

Player application setting value ID
forthecorresponding
playerapplication setting attribute ID

ValidPlayerApplicationSet
tingValueID values
received from thetarget, or defined aspart of Appendix 2

And so on for the number of target defined player application setting attributes and their values.
Response format (SetPlayerApplicationSettingValue)
Parameters
Size(byte)
Description

Allowed Values

None
NOTE: Setting of a value by CT does not implicitly mean that the setting will take effect on TG.
The setting shall take effect after a play command from CT. If currently playing, it is up to the
TG to decide when the setting shall take effect. There shall be an error response sent back if there
are errors in attribute and/or value.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

24

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.5. GetPlayerApplicationSettingAttributeText (PDU ID: 0x15)
Description:
This primitive requests the target device to provide supported player application setting attributedisplayable text for the provided PlayerApplicationSettingAttributeIDs.
NOTE: This command is expected to be used only for extended attributes for menu navigation. It is
assumed that all <attribute, value> pairs used for menu extensions are statically defined by TG.

Command format (GetPlayerApplicationSettingAttributeText)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player application
nSettingAttributes (N)setting attribute IDs for whichcorresponding string is needed
PlayerApplicationSetti
ngAttributeID1

1

Allowed Values
1-255

Player application setting attribute
ID for which the corresponding
attribute displayable text is needed

Valid
PlayerApplicationSet
tingAttributeIDvalues received fromthe target, or defined
attributeID as part ofAppendix 2
And so on for the number of needed player application setting attribute ID (N)Response format (GetPlayerApplicationSettingAttributeText)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of attributes provided
nSettingAttributes (N)PlayerApplicationSetti 1
Specified the player application
ngAttributeID1
setting attribute ID for which thedisplayable text is returned
CharacterSetID1

2

Specifies the character set ID to be
displayed on CT

PlayerApplicationSetti
ngAttributeStringLen
gth1 (n)PlayerApplicationSetti
ngAttributeString1

1

Length of the player application
setting attribute string

1-nSpecifies the player application
setting attribute string in specified
character set.

Allowed Values
1-255
1-255

Use
MIBenum
defined in IANA
characterset
document (Refer toInformDisplayableC
haracterSet)
1-255

Any string encodedin specified characterset

And so on for the number of target defined player application setting attributes in the requested
order (N).
Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

25

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.6. GetPlayerApplicationSettingValueText (PDU ID: 0x16)
Description:
This primitive request the target device to provide target supported player application setting
value displayable text for the provided player application setting attribute values.
NOTE: This command is expected to be used only for extended attributes for menu navigation. It is assumed
that all <attribute, value> pairs used for menu extensions are statically defined by TG.

Command format (Get PlayerApplicationSettingValueText)
Parameters
PlayerApplicationSetti
ngAttributeID

Size(byte)
1

Description
Player application setting attribute
ID

NumPlayerApplicatio
nSettingValue(N)1PlayerApplicationSetti
ngValueID1

1

Number of player application setting
values for which corresponding
string is needed
Player application setting value ID
for which the corresponding value
string is needed

Allowed Values
Playerapplication
setting attribute IDasdefinedinAppendix
2
orreceived from thetarget1-255

Valid ValueID values
received from thetarget, or defined
ValueID as part ofAppendix 2

And so on for the number of target defined player application setting values in the requested order(N).
Response format (GetPlayerApplicationSettingValueText)
Parameters
Size(byte)
Description
NumPlayerApplicatio
1
Number of player
nSettingValues (N)settings value provided
PlayerApplicationSetti
ngValueID1
CharacterSetID1

1

PlayerApplicationSetti
ngValueStringLength1(n)PlayerApplicationSetti
ngValueString1

1

2

1-n

application

Player application setting value ID
for which the text is returned
Specifies the character set ID to be
displayed on CT
Length of the player application
setting value string
Specifies the player application
setting value string in specified
character set.

Allowed Values
1-255

1-255
Refer to section 5.2.7
for allowed values
1-255

Any string encodedin specified characterset

And so on for the number of target defined player application setting values in the requested order(N).
Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

26

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.7. InformDisplayableCharacterSet (PDU ID: 0x17)
Description:
This primitive informs the list of character set supported by CT to TG. This shall allow TG to send
responses with strings in the character set supported by CT.
When the TG receives this command, the TG can send a string in the character set that is specified
in this command. If there is no character set which CT has, the TG will send a string in UTF-8. By
default TG shall send strings in UTF-8 if this command has not been sent by CT to TG.
Command format (InformDisplayableCharacterSet)
Parameters

Size(byte)

Description

Allowed Values

NumCharacterSet(N)1

Number of displayable character sets

1-255

CharacterSetID

2*N

Specifies the character set ID to be

Use MIBenumdisplayed on CT.

defined in IANA
character set
document.
3: ISO 646(ASCII)
4: ISO_8859-1
15: JIS_X0201
17: Shift_JIS
36:
KS_C_5601-1987
106: UTF-8
1013: UTF-16BE
2025: GB2312
2026: Big5
(in Decimal)

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

27

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Response format (InformDisplayableCharacterSet)
Parameters
Size(byte)
Description

Allowed Values

None
Note:
If this command is not issued, UTF-8 shall be used for any strings as default character set. It is
mandatory for CT to send UTF-8 as one of the supported character set in the PDU parameters.
The CT should send this command before it sends any commands that support multiple character
sets as follows,・ GetPlayerApplicationSettingAttributeText (0x15)
・ GetPlayerApplicationSettingValueText (0x16)
・ GetElementAttributes (0x20)
CharacterSetID parameter in all the above listed PDUs including this PDU is MIBenum value ofthe character set defined in IANA character set document [8].

CTTG
InformDisplayableChacterSet command
InformDisplayableCharacterSet
commandshould be sent before sending any string
request command.

InformDisplayableChacterSet response

Any string request command

Any string request response

Figure 3 example of using InformDisplayableCharacterSet

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

28

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.2.8. InformBatteryStatusOfCT (PDU ID: 0x18)
Description:
This command frame is being sent by the CT to TG whenever the CT's battery status has beenchanged.
Command format (InformBatteryStatusOfCT)
Parameters
Size(byte)
Description
Battery status
1
Battery status

Allowed Values
0x0 – NORMAL –Battery operation is innormal state
0x1 – WARNING Unable to operate soon.
Specified when battery
going down.
0x2 – CRITICAL –Can not operate any
more.
Specified when battery
going down.
0x3 – EXT ERNAL –Connecting to external
power supply.
0x4 - FULL_CHARGE –
When

the

devicecompletely charged.

Response Format (InformBatteryStatusOfCT)
Parameters
Size(byte)
Description
None

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

29

Allowed ValuesisBluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.3.

Media Information PDUs

The Media Information PDU’s are used to obtain detailed information on a particular media file
like song information including title, album, artist, composer, year etc.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

30

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.3.1.

GetElementAttributes (PDU ID: 0x20)

Description:
These primitive requests the TG to provide the attributes of the element specified in theparameter.
Command format (GetElemenAttributes)
Parameters
Size(byte) Description
Identifier
8Unique identifier to identify anelement on TG

NumAttributes (N)1

Number of Attributes provided

AttributeID1

4

Specifies the attribute ID for theattributes to be retrieved

And so on for each attribute (1…N).

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

31

Allowed Values
PLAYING (0x0): Thisshouldreturnattribute information
for the element which
is current track in the
TG device.
All other values otherthan 0x0 are currently
reserved.
If NumAttributes is set
to zero, all attributeinformation shall be
returned, else attributeinformation for the
specified attribute IDs
shall be returned by theTG
See Appendix 1 for listof possible attribute
IDs

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Response Format (GetElementAttributes)
Parameters
NumAttributes(N)AttributeID1

Size(byte)
1
4

Description
Number of attributes provided
Specifies the attribute ID to be
writtenCharacterSetID1

2

Specifies the character set ID to be
displayed on CT

AttributeValueLength
1 (n1)
AttributeValue121-n1

AttributeID2

4

Length of the value of theattribute
Attribute Name in specified
character set
Specifies the attribute ID to be
writtenCharacterSetID2

2

AttributeValueLength
2 (n2)
AttributeValue2

2

Specifies the character set ID to be
displayed on CT

Length of the value of theattribute
1-n2
Attribute value in specified
character set.
And so on for all the attributes provided (1…N)

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

32

Allowed Values
1-255
See Appendix 1 for listof possible attribute
IDs
Use MIBenum definedin IANA character set
document (Refer toInformDisplayableCharacterSet)
0-65535 (0, if no nameis provided)
Any text encoded in
specified character set
See Appendix 1 for listof possible attribute
IDs
Use MIBenum definedin IANA character set
document (Refer toInformDisplayableCharacterSet)
0-65535 (0, if no nameis provided)
Any text encoded in
specified character set

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.4.

Notification PDUs

The Notification PDUs are used to obtain asynchronous updates from the TG based on change ofstatus at the target’s side. For example, when CT might be interested to know when media track
gets changed, so that new media information can be displayed on the controllers display. The CT
registers with the TG to receive one or more notifications. The TG sends a notification PDU when astatus change happens if the CT had registered for that change.
5.4.1.

GetPlayStatus (PDU ID: 0x30)

Description:
This primitive is used by the CT to get the status of the currently playing media at the TG.
Command format (GetPlayStatus)
Parameters
Size(byte)
None

Description

Allowed Values

Description
The total length of the playing songin milliseconds
The current position of the playing
in milliseconds elapsed
Current Status of playing

Allowed Values
0-(232 – 1)

Response Format (GetPlayStatus)
Parameters
SongLength

Size(byte)
4

SongPosition

4

PlayStatus

1

0-(232 – 1)
0x00 : STOPPED
0x01 : PLAYING
0x02 : PAUSED
0x03: FWD_SEEK
0x04: REV_SEEK
0xFF : ERROR

Note:
If TG does not support SongLength And SongPosition on, TG then TG shall return 0xFFFFFFFF.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

33

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.4.2.

RegisterNotification (PDU ID: 0x31)

Description:
This primitive registers with the TG to receive notifications asynchronously based on specific
events occurring. A registered notification gets changed on receiving CHANGED event notification.
This is as per 1394 AV/C protocol specification. Only one EventID shall be used per notification
registration. The INTERIM response for this command must be a Notify command with current
status or REJECTED response.
Parameters
EventID

Size(byte)
1

Description
Event for which the CT requires
notifications

Allowed Values
The
event
ID
followingare

EVENT_PLAYBACK_ST
ATUS_CHANGED(0x01): Event for change
in playback status
EVENT_TRACK_CHAN
GED (0x02): Event forchange in track
EVENT_TRACK_REAC
HED_END (0x03): Eventfor reach to end of thecurrent track.
EVENT_TRACK_REAC
HED_START(0x04):
Event for reach to startof the current track.
EVENT_PLAYBACK_P
OS_CHANGED (0x05):
Event for change inplayback position
EVENT_BATT_STATUS_CHANGED(0x06):
Event for change inbattery status
EVENT_SYSTEM_STAT
US_CHANGED (0x07):
Event for change insystem status

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

34

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Playback interval

4Specifies the time interval (inseconds) at which the change inplayback position will be notified.
If the song is being forwarded /rewound, a notification will bereceived whenever the playback
position will change by this value.
(Applicable only for EventID
EVENT_PLAYBACK_POS_CHA
NGED.
For other events , value of thisparameter is ignored)

EVENT_PLAYER_APP
LICATION_SETTING_
CHANGED(0x08):
Event for change inplayerapplication
setting
0 < Playback interval
Don’t use 0.

*Note that TG may send reject response when CT re-register events with RegisterNotificationcommand to TG.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

35

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Response Format (RegisterNotification)
Response Data format for EVENT_PLAYBACK_STATUS_CHANGED
Parameters
Size(byte) Description
EventID
1
Specific EventID

Allowed Values
EVENT_PLAYBACK_STA
TUS_CHANGED(0x01)PlayStatus

1

Indicates the current status of playback

0x00: STOPPED
0x01: PLAYING
0x02: PAUSED
0x03: FWD_SEEK
0x04: REV_SEEK
0xFF: ERROR

Response Data format for EVENT_TRACK_CHANGED

Parameters
EventID

Size(byte)
1

Description
Specific EventID

Allowed Values
EVENT_TRACK_CHA
NGED(0x02)

Identifier

8

Index of the current trackIf

noselected,

track

currently

then

0xFFFFFFFF

returninthe

INTERIM response.

Response Data format for EVENT_TRACK_REACHED_END

Parameters
EventID

Size(byte)
1

Description
Specific EventID

Allowed Values
EVENT_TRACK_REAC
HED_END(0x03)

None

Response Data format for EVENT_TRACK_REACHED_START

Parameters
EventID

Size(byte)
1

Description
Specific EventID

None

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

36

Allowed Values
EVENT_TRACK_REAC
HED_START (0x04)

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Response Data format for EVENT_ PLAYBACK_POS_CHANGED

Parameters
EventID

Size(byte)
1

Description

Playback position

4

Current playback
millisecond

Allowed Values
EVENT_PLAYBACK_P
OS_CHANGED (0x05)

Specific EventID

position

in

If

no

track

selected,

currently

then

0xFFFFFFFF

returninthe

INTERIM response.

EVENT_PLAYBACK_POS_CHANGD shall be notified in the following conditions:- TG has reached the registered playback Interval time.
- Changed PLAY STATUS.
- Changed Current Track.
- Reached end or beginning of track.
Response Data format for EVENT_BATT_STATUS_CHANGED

Parameters
EventID

Size(byte)
1

Description
Specific EventID

Allowed Values
EVENT_BATT_STATUS_CHANGED (0x06)

Battery status

1

Battery status

0x0 – NORMAL –Battery operation is innormal state
0x1 – WARNING Unable to operate soon.
Isprovidedbattery

when

the

is

going

level

down.
0x2 – CRITICAL –Can not operate any more.
Is

providedbattery

when

the

is

going

level

down.
0x3 – EXT ERNAL –Connecting

toexternal

power supply
0x4 - FULL_CHARGE –
When

the

deviceiscompletely charged fromthe external power supply.

NOTE: Battery status notification defined in this specification is expected to be replaced by
Attribute profile specification in the future.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

37

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Response Data format for EVENT_SYSTEM_STATUS_CHANGED

Parameters
EventID

Size(byte)
1

Description
Specific EventID

Allowed Values
EVENT_SYSTEM_STATU
S_CHANGED (0x07)

SystemStatus

1

Indicates
status.

thecurrent

SystemPOWER_ON (0x00)
POWER_OFF (0x01)
UNPLUGGED (0x02)

POWER_OFF and UNPLUGGED are used for Bluetooth Accessories which attach to Media
Players. In this case, it will happen that Audio Player's power state is "POWER OFF" or Audio
Player is detached from Bluetooth Adapter (UNPLUGGED)
Response Data format for EVENT_PLAYER_APPLICATION_SETTING_CHANGED

Parameters
EventID

Size(byte)
1

Description
Specific EventID

Allowed Values
EVENT_PLAYER_APPLICATION_SETTING_CHA
NGED (0x08)

NumPlayerApplicatio
nSettingAttributes(N)PlayerApplicationSetti
ngAttributeID1

1

PlayerApplicationSetti
ngValueID1

1

1

Number of player application
setting attributes that follow
Playerapplication
setting
attribute ID for which the value isreturned

1-255

Currently set player application
setting value on the target for thecorresponding
requested
PlayerApplicationSettingAttribute
ID

Valid
PlayerApplicationSetti
ngValueIDvalues, or defined aspart of Appendix 2

1-255

And so on for the number of target defined player application setting values.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

38

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.5.
5.5.1.

Continuing PDUs
RequestContinuingResponse (PDU ID: 0x40)

Description:
This primitive is used by CT to request continuing response that has not completed. If it
requested, a series of part is responded by operational command. This command will be invoked by
CT after receiving a response with <Packet Type – First (0x01) or Continue (0x10)>.
Command format (RequestContinuingResponse)
Parameters
ContinuePDU_ID

Size(byte)
1

Description
Target PDU_ID
commandforcontinue

Allowed Values
PDU_ID

Response Format (RequestContinuingResponse)
The response for this command is the pending data for the previous command invoked by CT.
(Refer to Figure 4)

CT

TG

VENDOR DEPENDENT command（XX command）

Request to continue
to send a response

VENDOR DEPENDENT response（XX command）
VENDER DEPENDENT command（RequestContinuingResponse）

VENDER DEPENDENT response( XX command）
Request to continue
to send a response

XX command is responded＜Packet Type - First＞

Part where XX command iscontinuously responded<Packet Type - Continue>

VENDER DEPENDENT command（RequestContinuingResponse）

VENDER DEPENDENT response( XX command）

Part where XX command iscontinuously responded<Packet Type - End>

Figure 4 Request for sending a response continuously

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

39

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.5.2. AbortContinuingResponse (PDU ID: 0x41)
Description:
This primitive is used by CT to abort continuing response. This command will be invoked by CT
after receiving a response with <Packet Type – First (0x01) or Continue (0x10)>.
(Refer to Figure 5)
Command format (AbortContinuingResponse)
Parameters
ContinueAbortPDU_ID

Size(byte)
1

Description
Target PDU_ID for abort continuecommand

Allowed Values
PDU_ID

Response Format (AbortContinuingResponse)
Parameters
NoneSize(byte)

Description

CT

Allowed Values

TG

VENDOR DEPENDENT command（XX command）

Request to abort theongoing response

VENDOR DEPENDENT response（XX command）
VENDOR DEPENDENT command（AbortContinuing）

VENDER DEPENDENT response( AbortContinuing）

Figure 5 AbortContinuingResponse

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

40

XX command is responded＜Packet Type - First＞

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

5.6.

Basic Group Navigation

Basic group navigation PDUs are defined to support a logical one dimensional group structure of
media content on the TG to CT for easier navigation purpose. The definition of groups on the TG is
implementation dependent. The group structure can consist of parts of, or a mix of playlists andartist/album/genre folders etc that are used by the media player applications in the TG.
The basic group navigation PDUs have a similar behavior as the Forward and Backward
commands, but instead of navigating to the next/previous song they are used to navigate to thefirst song in the next/previous group.
The Basic Group Navigation PDUs are transported as vendor unique PASS THROUGH
commands.
5.6.1. Next Group (vendor unique id: 0x00)
Description:
This function is used to move to the first song in the next group. The definition of group on TG is
implementation dependent.
5.6.2. Previous Group (vendor unique id: 0x01)
Description:
This function is used to move to the first song in the previous group. The definition of group on TG
is implementation dependent.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

41

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

6. Error handlingz If CT sent a PDU with nonexistent PDU ID or a PDU containing only one parameter withnonexistent parameter ID, TG shall return REJECTED response with Error Status Code. TG
may return REJECTED response also in other situations (See 7. Error Status Code).
z If CT sent a PDU with multiple parameters where at least one ID is existent and the others arenonexistent, TG shall proceed with the existent ID and ignore the non-existent IDs.
Note, that CT can always have complete information which IDs were accepted by TG: in case of
STATUS PDUs the response will contain information for the IDs which were understood, whensetting values for Player application settings; TG will return notification response with the list of
AttributeIDs for which values have been set.

7. Error Status Code7.1. Error Status CodeAn error status code is added to the REJECTED response if TG rejected the command. It is useful
for CT to know why the command is rejected by TG. Table 7.1.1 below shows the error status code.
Error Code Value
0x00
0x01

0x02

0x03

Description
Invalid command, sent if TG received a
PDU not it did not understand.
Invalid parameter, sent if the TG
received a PDU with a parameter ID
that it did not understand. Sent if there
is only one parameter ID in the PDU.
Specified parameter not found, sent if
the parameter ID is understood, butcontent is wrong or corrupted.
Internal Error, sent if there are othererror conditions.

Table 7.1.1 List of Error Status CodeAn example of response packet format for REJECTED will be as below.
Oct01

MSB (7)

6

5

4

3

0x0

2

1

Response: 0xA(REJECTED)

Subunit_type:0x9 (PANEL)

Subunit_ID: 0x0

2

Opcode: 0x0 (VENDOR DEPENDENT)

3–5

Company ID: 0x0017A7 [MCPC registered CompanyID]

6

PDU ID (of the command for which this response is sent)

7

LSB (0)Reserved (0x00)

8–9

Parameter Length (0x0001)

10Error Code (0x02 – Specified parameter not found)

Packet Type (0x0)

Table 7.1.2 An example of response packet format for REJECTED

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

42

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

8. List of Figures
Figure 1 example system configuration........................................................................................ 9
Figure 2 Basic usage model......................................................................................................... 11
Figure 3 example of using InformDisplayableCharacterSet ..................................................... 28
Figure 4 Request for sending a response continuously.............................................................. 39
Figure 5 AbortContinuingResponse............................................................................................ 40
Figure 6 Example Message Sequence Chart ............................................................................. 47

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

43

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

9. List of Tables
Table 3.2.1 An example command (GetCapabilities) PDU ........................................................ 13
Table 3.3.1 PASS THROUGH Command Frame........................................................................ 13
Table 3.3.2 PASS THROUGH Response Frame ......................................................................... 13
Table 3.4.1 VENDOR DEPENDENT Command Frame ............................................................ 14
Table 3.4.2 VENDOR DEPENDENT Response Frame ............................................................. 14
Table 4.1.1 Application Layer Features...................................................................................... 15
Table 4.2.1 List of command ....................................................................................................... 16
Table 4.2.2 List of PASS THROUGH COMMAND..................................................................... 17
Table 7.1.1 List of Error Status Code ......................................................................................... 42
Table 7.1.2 An example of response packet format for REJECTED.......................................... 42
Table 10.1.1 Attribute IDs........................................................................................................... 45
Table 11.1.1 PlayerApplicationSettingAttributeIDs .................................................................. 46
Table 12.2.1 example device setting of TG ................................................................................. 48
Table 12.2.2 example MSC to handle device setting using PlayerApplicationSettings PDUs. 52
Table 12.2.3 example MSC to follow the device setting of TG................................................... 53

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

44

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

10.

Appendix 1

10.1. Attribute IDs
The table below provides the list of IDs for Attributes. These IDs are used to uniquely identify
media information.

Attribute
ID
0x0
0x1

Description

Allowed values

Illegal , Should not be used
Title of the media

0x2

Name of the artist

0x3

Name of the album

0x4

0x6

Number of the media(ex. Track number of the CD)
Total number of the media(ex. Total track number of the
CD)
Genre

Any text encoded in specified
character set
Any text encoded in specified
character set
Any text encoded in specified
character set
Numeric ASCII text with zero
suppresses
Numeric ASCII text with zero
suppresses

0x7

Playing time in millisecond

0x8-0xFFF
FFFFF

Reserved for future use

0x5

Any text encoded in specified
character set
Numeric ASCII text
(Ex. 2min30sec Æ 150000)-

Mandatory/ Optional

M
O
O
O
O

O
O

Table 10.1.1 Attribute IDs

NOTE: If the track title is not available the TG shall try to identify the track in other ways or send
information about the media. If no information is available an empty string of zero length may be
sent.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

45

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

11.

Appendix 2

11.1. PlayerApplicationSettingAttributeIDs
The table below provides the list of IDs for device settings. These IDs are used to uniquely identify
and exchange information on player application settings between the TG and the CT.
PlayerApplicationSetting
Attribute
0x00

Attribute Description
Illegal , Should not be
usedDefined Values

None
PlayerApplicationSettingValueID
ValueID
Description

0x01

Equalizer
status

ON/OFF0x01
0x02
0x03-0xFF

OFF
ON
Reserved for future use

PlayerApplicationSettingValueID
ValueID
Description
0x02

0x01
0x02
0x03
0x04
0x05-0xFF

Repeat Mode status

OFF
Single track repeat
All track repeat
Group repeat
Reserved for future use

PlayerApplicationSettingValueID
ValueID
Description
0x03

Shuffle ON/OFF status

0x01
0x02
0x03
0x04-0xFF

OFF
All tracks shuffleGroup shuffle
Reserved for future use

PlayerApplicationSettingValueID
ValueID
Description
0x04

Scan ON/OFF status

0x05 – 0x7F

Reserved for future use

0x80 – 0xFF

Vendor specified

0x01
0x02
0x03
0x04-0xFF

OFF
All tracks scanGroup scan
Reserved for future use

Table 11.1.1 PlayerApplicationSettingAttributeIDs

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

46

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

12.

Appendix 3

12.1. Message Sequence Chart (MSC)
Below is an example MSC how to follow to track information on CT in case track change isoccurred by PASSTHROUGH command.
(NOTE) THIS MSC IS JUST A ONE OF EXAMPLES. ALL BEHAVIORS BOTH OF CT AND TG
are IMPLEMENTATION DEPENDENT.

CT

TG
RegisterNotification command(TRACK_CHANGED)
RegisterNotification response(INTERIM, TRACK_CHANGED)

User action(FWD Key Press)

PassThrough command (FWD,PRESSED)

PassThrough response (FWD,PRESSED）
User action（FWD Key Release）

PassThrough command (FWD,RELEASED)
PassThrough response (FWD,RELEASED)

RegisterNotification response(CHANGED, TRACK_CHANGED)
RegisterNotification command(TRACK_CHANGED)
RegisterNotification response(INTERIM, TRACK_CHANGED)
GetElementAttributes command(PLAYING)

GetElementAttributes response…
Figure 6 Example Message Sequence Chart

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

47

Internal track change eventBluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

12.2. Player Application Setting PDUs
Below is an example MSC how to manipulate player application settings using Player Application
Setting PDUs.
The table below is an example player application setting of TG.
PlayerAp
plication
SettingAt
tributeID
0x01

PlayerApplicationSettingAtt
ributeText

PlayerApplicationSettingValueID“Equalizer”

PlayerApplication
SettingValueID
0x01
0x02

PlayerApplicationSe
ttingValueText
“OFF”
“ON”

0x03

“Shuffle Mode”

PlayerApplication
SettingValueID
0x01
0x02

PlayerApplicationSe
ttingValueText“OFF”“All tracks shuffle”

0x80"Language Setting"PlayerApplication
SettingValueID
0x01
0x02
0x03

PlayerApplicationSe
ttingValueText
"eng"
"jpn"
"fra"

0x81

“Sleep Timer”

PlayerApplication
SettingValueID
0x01
0x02

PlayerApplicationSe
ttingValueText“OFF”“20 min.”

Table 12.2.1 example device setting of TG

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

48

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

MSC are described as follows.
CT

TG[Get a player application setting list and retrieve text labels for each.]
GetListPlayerApplicationSettingAttributes(Command)
None

GetListPlayerApplicationSettingAttributes(Response)
NumPlayerApplicationSettingAttributes

0x04

PlayerApplicationSettingAttributeID1

0x01

PlayerApplicationSettingAttributeID2

0x03

PlayerApplicationSettingAttributeID3

0x80

PlayerApplicationSettingAttributeID4

0x81

GetPlayerApplicationSettingAttributeText(Command)
NumPlayerApplicationSettingAttribute

0x04

PlayerApplicationSettingAttributeID1

0x01

PlayerApplicationSettingAttributeID2

0x03

PlayerApplicationSettingAttributeID3

0x80

PlayerApplicationSettingAttributeID4

0x81

GetPlayerApplicationSettingAttributeText(Response)
NumPlayerApplicationSettingAttribut

0x04

es
PlayerApplicationSettingAttributeID1

0x01

CharacterSetID10x006a (UTF-8)

PlayerApplicationSettingAttributeStri

0x09

ngLength1
PlayerApplicationSettingAttributeStri“Equalizer”

ng1
PlayerApplicationSettingAttributeID2

0x03

CharacterSetID20x006a (UTF-8)

PlayerApplicationSettingAttributeStri0x0c

ngLength2
PlayerApplicationSettingAttributeStri“Shuffle Mode”

ng2
PlayerApplicationSettingAttributeID3

0x80

CharacterSetID30x006a (UTF-8)

PlayerApplicationSettingAttributeStri

0x10

ngLength3
PlayerApplicationSettingAttributeStri"Language

ng3

Setting"

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

49

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

PlayerApplicationSettingAttributeID4

0x81

CharacterSetID40x006a (UTF-8)

PlayerApplicationSettingAttributeStri0x0b

ngLength4
PlayerApplicationSettingAttributeStri“Sleep Timer”

ng4[Get a value of all settings and get text labels of each value.]
ListPlayerApplicationSettingValues(Command)PlayerApplicationSettingAttributeID

0x01(Equalizer)

ListPlayerApplicationSettingValues (Response)
NumPlayerApplicationSettingValues

0x02

PlayerApplicationSettingValueID1

0x01

PlayerApplicationSettingValueID2

0x02

ListPlayerApplicationSettingValues(Command)PlayerApplicationSettingAttributeID

0x03(Shuffle

Mode)

ListPlayerApplicationSettingValues (Response)
NumPlayerApplicationSettingValues

0x02

PlayerApplicationSettingValueID1

0x01

PlayerApplicationSettingValueID2

0x02

ListPlayerApplicationSettingValues(Command)PlayerApplicationSettingAttributeID

0x80 (Language
Setting)

ListPlayerApplicationSettingValues (Response)
NumPlayerApplicationSettingValues

0x03

PlayerApplicationSettingValueID1

0x01

PlayerApplicationSettingValueID2

0x02

PlayerApplicationSettingValueID3

0x03

ListPlayerApplicationSettingValues(Command)PlayerApplicationSettingAttributeID

0x81(SleepTimer)

ListPlayerApplicationSettingValues (Response)
NumPlayerApplicationSettingValues

0x02

PlayerApplicationSettingValueID1

0x01

PlayerApplicationSettingValueID2

0x02

GetPlayerApplicationSettingValueText
Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

50

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9(Command)PlayerApplicationSettingAttributeID

0x01(Equalizer)

NumPlayerApplicationSettingValue

0x02

PlayerApplicationSettingValueID1

0x01

PlayerApplicationSettingValueID2

0x02

GetPlayerApplicationSettingValueText(Response)
NumPlayerApplicationSettingValues

0x02

PlayerApplicationSettingValueID1

0x01

CharacterSetID10x006a (UTF-8)

PlayerApplicationSettingValueStringL

0x03

ength1
PlayerApplicationSettingValueString1“OFF”

PlayerApplicationSettingValueID2

0x02

CharacterSetID20x006a (UTF-8)

PlayerApplicationSettingValueStringL

0x02

ength2
PlayerApplicationSettingValueString2“ON”(similar sequence will continue to retrieve all PlayerApplicationSettingValueString)[Get current device setting values.]
GetCurrentPlayerApplicationSettingValue(Command)
NumPlayerApplicationSettingAttributeI

0x04

D
PlayerApplicationSettingAttributeID1

0x01

PlayerApplicationSettingAttributeID2

0x03

PlayerApplicationSettingAttributeID3

0x80

PlayerApplicationSettingAttributeID4

0x81

GetCurrentPlayerApplicationSettingValue(Response)
NumPlayerApplicationSettingValues

0x04

PlayerApplicationSettingAttributeID1

0x01(Equalizer)

PlayerApplicationSettingValueID1

0x02 (ON)

PlayerApplicationSettingAttributeID2

0x03(Shuffle Mode)

PlayerApplicationSettingValueID20x01 (OFF)PlayerApplicationSettingAttributeID30x80 (Language
Setting)

PlayerApplicationSettingValueID3
PlayerApplicationSettingAttributeID40x01 (eng)
0x81(SleepTimer)
PlayerApplicationSettingValueID4

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

51

0x01 (OFF)Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9[Set device setting values.]
SetPlayerApplicationSettingValue (Command)
NumPlayerApplicationSettingAttributeI

0x04

D
PlayerApplicationSettingAttributeID1

0x01(Equalizer)

PlayerApplicationSettingValueID1

0x02 (ON)

PlayerApplicationSettingAttributeID2

0x03(Shuffle

Mode)
PlayerApplicationSettingValueID2

0x02
(All

track

shuffle)PlayerApplicationSettingAttributeID30x80 (Language
Setting)

PlayerApplicationSettingValueID3

0x02 (jpn)

PlayerApplicationSettingAttributeID4

0x81(SleepTimer)
PlayerApplicationSettingValueID40x02 (20 min.)

SetPlayerApplicationSettingValue (Response)
None

Table 12.2.2 example MSC to handle device setting using PlayerApplicationSettings PDUs

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

52

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

Register Notification to follow the device setting of TG.
CT
RegisterNotificaion (Command)
EventID

0x08(EVENT_DEVICE_SETTING_CHANGED

Playback

Any (this value is ignored)TGinterval

RegisterNotificaion (Response) - INTERIM
EventID

0x08

NumDeviceAttribute

0x04

PlayerApplicationSettingAttributeID1

0x01 (Equalizer)

PlayerApplicationSettingValueID1

0x01 (OFF)PlayerApplicationSettingAttributeID2

0x03(Shuffle

Mode)
PlayerApplicationSettingValueID20x01 (OFF)PlayerApplicationSettingAttributeID3

0x80

PlayerApplicationSettingValueID30x01 (eng)PlayerApplicationSettingAttributeID4

0x81(Language

Setting)(SleepTimer)
PlayerApplicationSettingValueID40x01 (OFF)[Player Application settings are changed by user action.]
Equalizer “OFF” Æ “ON”
RegisterNotificaion (Response) - CHANGED
EventID

0x08

NumPlayerApplicationSettingAttribute

0x04

PlayerApplicationSettingAttributeID1

0x01 (Equalizer)

PlayerApplicationSettingValueID1

0x02 (ON)

PlayerApplicationSettingAttributeID2

0x03(Shuffle

Mode)
PlayerApplicationSettingValueID20x01 (OFF)PlayerApplicationSettingAttributeID30x80 (Language
Setting)

PlayerApplicationSettingValueID30x01 (eng)PlayerApplicationSettingAttributeID4

0x81(SleepTimer)
PlayerApplicationSettingValueID4

Table 12.2.3 example MSC to follow the device setting of TG

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

53

0x01 (OFF)Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

13.

Appendix 4

The table below gives the list of EventIDs defined in this specification to be supported by TG.

EventID

Description

EVENT_PLAYBACK_STATUS_CHANGED(0x01)
EVENT_TRACK_CHANGED(0x02)EVENT_TRACK_REACHED_E
ND (0x03)
EVENT_TRACK_REACHED_ST
ART (0x04)
EVENT_PLAYBACK_POS_CHA
NGED (0x05)

Change in playback status of the M
current track.
Change of current track
M

Mandatory/ Optional

Reached end of a trackO

Reached start of a track

O

Change in playback position. Returned O
after the specified playback notification
change notification interval
Change in battery status
O

EVENT_BATT_STATUS_CHAN
GED (0x06)
EVENT_SYSTEM_STATUS_CH Change in system status
ANGED (0x07)
EVENT_PLAYER_APPLICATIO Change in player application setting
N__SETTING_CHANGED(0x08)
0x09-0xFF
Reserved for future use

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

54

O
O

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

14.

Appendix 5

14.1. AV/C Transaction Rules
An AV/C transaction consists of one message containing a command frame addressed to the TG
and zero or more messages containing a response frame returned to the CT by the TG. The TG is
required to generate a response frame within specified time periods
All transactions except VENDOR DEPENDENT commands shall comply with the following time
period. TG shall respond to any command within a time period of T RCP (100) counting from themoment a command frame is received.
For some transactions, the TG may not be able to complete the request or determine whether it ispossible to complete the request within the T RCP (100) allowed. In this case, the TG shall return an
initial response code in INTERIM with the expectation that the final response follow later.
14.2. Timers and Counters
The following timer is required by AVRCP.
Timer

Proposed Value

Description

100 milliseconds

A TG shall return its response frame within 100 milliseconds

Name
T RCP (100)counting from the receipt of the command frame.
T MTC (200)200 milliseconds

A TG shall return its response frame within 200 milliseconds
counting from the receipt of the command frame.

TMTP(1000)

1000 milliseconds

A TG shall return its response frame within 1000 milliseconds
counting from the receipt of the command frame.

There are no AVRCP specific counters.

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

55

Bluetooth Audio Technical Reference 007 Ver.1.0, 2007.2.9

15.

References[1] Bluetooth SIG, Specification of the Bluetooth System, Core, Version 1.0, Audio/Video Control
Transport Protocol (http://www.bluetooth.org)[2] Bluetooth SIG, Specification of the Bluetooth System, Core, Version 1.0, Audio/Video Remote
Control Profile (http://www.bluetooth.org)[3] 1394 Trade Association, AV/C Digital Interface Command Set - General Specification, Version
4.0, Document No. 1999026 (http://www.1394ta.org)[4] 1394 Trade Association, AV/C Panel Subunit, Version 1.1, Document No. 2001001(http://www.1394ta.org)[5] IANA (Internet Assigned Numbers Authority) CHARACTER SETS
(http://www.iana.org/assignments/character-sets)[6] ISO Standard ISO/FDIS 639-2 from the technical committee/subcommittee TC 37 / SC 2
(http://www.id3.org/iso639-2.html)[7] ID3 tag version 2.4.0 (http://www.id3.org/id3v2.4.0-frames.txt)[8] http://www.iana.org/assignments/character-sets

Copyright(C) Mobile Computing Promotion Consortium (MCPC), 2005-2006

56