MCPC-TR008
Bluetooth Multi-Connection
Technical Reference
Version 1.2 English
24th Dec. 2009

Mobile Computing Promotion ConsortiumHistoryDate
11th Sept. 2008
23rd Dec. 2008
25th Mar. 2009

Version1.00 for Review
1.00 R01
1.1

24thDec. 2009

1.2

Contents
Base version initial release.
Reflected SIG Feedback
Added postscript CT, TG in Terms and Abbreviations
Added Section 4.2.7, Section 4.3.7
Added Section7 Appendix C (Halt Streaming)
Added postscript in Section 1.2, Section5 Appendix A
Added MSCs outgoing call from AG in 4.1.3, 4.2.5, 4.2.6,
4.2.7, 4.3.7
Added new procedures to restart streaming in 4.2.7, 4.3.7
Added Appendix D (Restore Streaming) in the section 7
Renumbering of section numbers at Section 1 and Section2.

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
Published and copyrights owned by
Mobile Computing Promotion Consortium （MCPC）
Hasegawa Green Bldg.
5-12 Shiba-Koen 3-chome, Minato-ku, Tokyo, 105-0011 Japan
TEL: +81-(0)3-5401-1935
FAX: +81-(0)3-5401-1937
EMAIL: office@mcpc-jp.org
WEB SITE: http://www.mcpc-jp.org

Confidentiality:
The MCPC Rules and the MCPC IPR Policy shall apply.

Disclaimer:This document is intended to provide standard specifications, recommended specifications, etc. on
mobile computing. Mobile Computing Promotion Consortium (hereafter MCPC) shall not be liable forany damages or infringements of patents or other rights of third parties arising out of the use of thisdocument. This document shall not be construed to grant (a) license(s) under any rights held by MCPCor third parties.

2

書式変更: フランス語（フランス）©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

Contributors
Masashi Miura

DENSO CORPORATION

Akio Konishi

FUJITSU ELECTRONICS INC.,

Masahiko Nakashima

FUJITSU ELECTRONICS INC.,

Masashi Takada

Hitachi, Ltd.

Masamitsu Miyazaki

Hitachi, Ltd.

Naoki Shimizu

MITSUBISHI ELECTRIC CORPORATION

Riko Yagiu

MITSUBISHI ELECTRIC CORPORATION

Tomoyuki Suzuki

NISSAN MOTOR CO., LTD. for JAMA

Masahiko Seki

Sony Corporation

Mitsuyoshi Yasuda

Sony Ericsson Mobile Communications Japan

Hiroshi Matsuya

TOSHIBA CORPORATION

Makoto Yamashita

TOSHIBA CORPORATION

Shuichi Sakurai

TOSHIBA CORPORATION

Toshiya Tamura

TOSHIBA CORPORATIONMCPC Bluetooth Audio Sub Working Group Member Company (Alphabetical Order)
AISIN AW CO.,LTD.
ALPINE ELECTRONICS, INC
ALPS ELECTRIC CO., LTD.
CSR Ltd.
Clarion Co., Ltd.
DENSO CORPORATION
FUJITSU ELECTRONICS INC.,
FUJITSU LIMITED
FUJITSU TEN LIMITEDHARMAN / BECKER AUTOMOTIVE SYSTEMS
Hitachi, Ltd.
MITSUBISHI ELECTRIC CORPORATIONMITSUMI ELECTRIC CO., LTD.
Murata Manufacturing Co., Ltd.
NEC Corporation
NISSAN MOTOR CO., LTD. for JAMANTT DoCoMo, Inc.
Renesas Technology Corp.
SEIKO EPSON CORPORATIONSHARP CORPORATIONSOFTBANK MOBILE Corp.
Sony Corporation
Sony Ericsson Mobile Communications JapanTAIYO YUDEN CO., LTD.
TOSHIBA CORPORATION

3

書式変更: フランス語（フランス）©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

Table of Contents
1. Document Terminology .................................................................................................8
2. Introduction....................................................................................................................8
2.1 Scope ...................................................................................................................................... 8
2.2 System..................................................................................................................................... 9
2.3 Role Switch............................................................................................................................ 10

3. Basic Condition ........................................................................................................... 11
3.1 Configuration and Roles .........................................................................................................11
3.1.1 Audio Gateway with Gateway (AG_GW)..........................................................................11
3.1.1.1 Recommendation............................................................................................................. 11
3.1.1.2 Motivation ........................................................................................................................ 11
3.1.2 HandsFree with Data Terminal (HF_DT) ..........................................................................11
3.1.2.1 Recommendation............................................................................................................. 11
3.1.2.2 Motivation ........................................................................................................................ 11
3.1.3 Media Player (MP) ...........................................................................................................11
3.1.3.1 Recommendation............................................................................................................. 11
3.1.3.2 Motivation ........................................................................................................................ 11
3.1.4 Rendering Device (RD) ................................................................................................... 12
3.1.4.1 Recommendation.............................................................................................................123.1.4.2 Motivation ........................................................................................................................123.1.5 Remote Controller (RC) .................................................................................................. 12
3.1.5.1 Recommendation.............................................................................................................123.1.5.2 Motivation ........................................................................................................................123.1.6 Audio Gateway with Media Player and Gateway (AG_MP_GW) .................................... 12
3.1.6.1 Recommendation.............................................................................................................123.1.6.2 Motivation ........................................................................................................................123.1.7 Handsfree with Rendering Device and Data Terminal (HF_RD_DT) .............................. 13
3.1.7.1 Recommendation.............................................................................................................13
3.1.7.2 Motivation ........................................................................................................................13
3.2 Profile Architecture ................................................................................................................ 13

4. SCENARIOS .................................................................................................................15
4.1 Use Cases for HFP + DUN.................................................................................................... 15
4.1.1 HFP+DUN；STARTING DATA COMMUNICATION UNDER PACKET-SWITCHED DATAMODE DURING ONGOING CALL ........................................................................................... 15
4.1.1.1 Pre-Conditions .................................................................................................................15
4.1.1.2 User Action ......................................................................................................................15
4.1.1.3 Post Conditions................................................................................................................15
4.1.1.4 Recommendation.............................................................................................................15
4.1.1.5 Message Sequence Charts..............................................................................................16
4.1.2 HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATAMODE WHILE ONGOING CALL ............................................................................................. 17
4.1.2.1 Pre-Conditions .................................................................................................................17
4.1.2.2 User Action ......................................................................................................................17
4.1.2.3 Post Conditions................................................................................................................17
4.1.2.4 Recommendation.............................................................................................................17
4.1.2.5 Message Sequence Charts..............................................................................................18
4.1.3 HFP+DUN;OUTGOING CALL WHILE DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE ........................................................................................................ 19
4.1.3.1 Pre-Conditions .................................................................................................................194

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
4.1.3.2 User Action ......................................................................................................................19
4.1.3.3 Post Conditions................................................................................................................19
4.1.3.4 Recommendation.............................................................................................................19
4.1.3.5 Message Sequence Charts..............................................................................................20
4.2 Use Cases for HFP+A2DP/VDP+AVRCP+DUN WITH SAME DEVICE ................................ 22
4.2.1 HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC....................................... 22
4.2.1.1 Pre-Conditions .................................................................................................................224.2.1.2 User Action ......................................................................................................................224.2.1.3 Post Conditions................................................................................................................224.2.1.4 Recommendation.............................................................................................................224.2.1.5 Message Sequence Charts..............................................................................................23
4.2.2 HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC. ..................................... 25
4.2.2.1 Pre-Conditions .................................................................................................................25
4.2.2.2 User Action ......................................................................................................................25
4.2.2.3 Post Conditions................................................................................................................25
4.2.2.4 Recommendation.............................................................................................................25
4.2.2.5 Message Sequence Charts..............................................................................................26
4.2.3 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL UNDER PACKET-SWITCHED DATAMODE ...................................................................................................................................... 28
4.2.4 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONE UNDER
PACKET-SWITCHED DATA MODE AND LISTENING TO MUSIC FROM A SAME DEVICE... 28
4.2.5 HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHED DATAMODE ...................................................................................................................................... 29
4.2.5.1 Pre-Conditions .................................................................................................................29
4.2.5.2 User Action ......................................................................................................................29
4.2.5.3 Post Conditions................................................................................................................29
4.2.5.4 Recommendation.............................................................................................................29
4.2.5.5 Message Sequence Charts..............................................................................................30
4.2.6 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE ........................................................................... 32
4.2.6.1 Pre-Conditions .................................................................................................................32
4.2.6.2 User Action ......................................................................................................................32
4.2.6.3 Post Conditions................................................................................................................32
4.2.6.4 Recommendation.............................................................................................................32
4.2.6.5 Message Sequence Charts..............................................................................................33
4.2.7 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.................................. 35
4.2.7.1 Pre-Conditions .................................................................................................................35
4.2.7.2 User Action ......................................................................................................................35
4.2.7.3 Post Conditions................................................................................................................35
4.2.7.4 Recommendation.............................................................................................................36
4.2.7.5 Message Sequence Charts..............................................................................................37
4.3 Use Cases for HFP+A2DP/VDP+AVRCP+DUN WITH THE THIRD DEVICE ................... 4039
4.3.1 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE THIRD
DEVICE................................................................................................................................ 4039
4.3.2 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE THIRD
DEVICE................................................................................................................................ 4039
4.3.3 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONE UNDER
PACKET-SWITCHED DATA MODE ..................................................................................... 4039
4.3.4 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONE UNDER
PACKET-SWITCHED DATA MODE AND LISTENING TO MUSIC FROM THE THIRD DEVICE............................................................................................................................................. 4140

5

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.3.5 HFP-A2DP/VDP-AVRCP+DUN; OUTGOING CALL DURING NO DATA/DATACOMMUNICATION UNDER PACKET-SWITCHED DATA MODE........................................ 4140
4.3.6 HFP + A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE(IN CASE OF THE THIRD DEVICE) .............. 4140
4.3.7 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE (IN CASE OF THE
THIRD DEVICE)................................................................................................................... 4241
4.3.7.1 Pre-Conditions .............................................................................................................4241
4.3.7.2 User Action ..................................................................................................................4241
4.3.7.3 Post Conditions............................................................................................................4241
4.3.7.4 Recommendation.........................................................................................................4342
4.3.7.5 Message Sequence Charts..........................................................................................4443

5. Appendix A (Multi Connection use cases).............................................................4745
6. Appendix B (Notes on the implementation)...........................................................4947
7. Appendix C (HALT STREAMING Sub-scenarios) ..................................................5048
8. Appendix D (RESTORE STREAMING Sub-scenarios) ..........................................5149
9. LIST OF FIGURES ....................................................................................................5250
10.LIST OF TABLES .....................................................................................................5351

6

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

Terms and Abbreviations
A2DP

Advanced Audio Distribution Profile

AG

Audio Gateway (as in HFP)

AG_MP

Audio Gateway and Media Player

AG_MP_GW

Audio Gateway with Media Player and Gateway

AVDTP

Audio/Video Distribution Protocol

AVRCP

Audio Video Remote Control Profile

CSDM

Circuit Switched Data Mode (Data communication over Circuit switchedbearer service)CT

Controller (as in AVRCP)DT

Data Terminal (as in DUN)

DUN

Dial-Up Networking ProfileGAVDP

Generic Audio/Video Distribution Profile

GW

Gateway (as in DUN)

HF

HandsFree (as in HFP)

HFP

HandsFree Profile

HF_RD

HandsFree and Rendering Device

HF_RD_DT

HandsFree with Rendering Device and Data Terminal

HQ ringing tone

Any audio using A2DP for ringing

MP

Media Player

NA

Not Applicable

PSDM

Packet-Switched data mode (Data communication over Packet switchedbearer service)

RC

Remote Controller

RD

Rendering Device

SNK

Sink (as in A2DP/VDP)

SRC

Source (as in A2DP/VDP)TG

Target (as in AVRCP)

UI

User Interface (Some possibility for the user to interact with the system.
Can be just some buttons or a more complex UI may be e.g. a display withkeyboard or touch screen.)

VDP

Video Distribution Profile7

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

1. Document Terminology
The MCPC has adopted Section 13.1 of the IEEE Standards Style Manual, which dictates use of thewords “shall”, “should”, “may” and “can” in the development of documentation, as follows.
The word shall is used to indicate mandatory requirements strictly to be followed in order to conform to
the standard and from which no deviation is permitted (shall equals is required to).
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.
The use of the word will is deprecated and shall not be used when starting mandatory requirements; willis only used in statements of fact.
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 of action is preferred but notnecessarily required; or that (in the negative form) a certain course of action is deprecated but notprohibited (should equals is recommended that).
The word may is used to indicate a course of action permissible within the limits of the standard (mayequals is permitted).
The word can is used for statements of possibility and capability, whether material, physical or causal(can equals is able to).

2. Introduction
2.1 ScopeThis document is published based on Simultaneous Use of HFP, A2DP and AVRCP_WP [9] by
Bluetooth SIG and describes how A2DP and AVRCP should be used together and how A2DP,
AVRCP in conjunction with other profiles, especially HFP and DUN, should be used together toachieve high interoperability in all functions defined in the profiles. The scenarios and the sequencesof the procedures defined in this document are not mandatory but recommended.
This document describes how multiple profiles operate simultaneously in typical use cases. Theseuse cases is described in Appendix A. Multiple operations including profiles not mentioned in thisdocument are implementation dependent.
For instance AVRCP is not involved in scenario 4.2.1 but it assumes that AVRCP should beconnected in case that AVRCP is supported in both sides. The connection procedures should bereferred to Simultaneous Use of HFP, A2DP and AVRCP_WP [9] .

[Note]
The contents of this document shall be non-binding, and shall not infringe any rights of BluetoothInc. The use of this document or any of the contents thereof shall be made at the responsibility ofeach 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 particular purpose.

8©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

2.2 System
The following Figure2.1 and Figure 2.2 shows example of system configuration defined by thistechnical reference. In this document, Third Device Scenario is defined as the connection typedrawn in Figure 2.1 .also Same device Scenario is defined in Figure2.2.

Figure 2.1 example system configuration Case 1 (Third Device Scenario)

Figure 2.2 example system configuration Case 2 (Same Device Scenario)

9©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

2.3 Role Switch
To avoid the frequent role switches and utilize the band width efficiently on the multiple link connection,
the role of device should not be fixed to neither Master nor Slave under the current condition, and arequest of role switches should be accepted if there is no issue to be either Master or Slave role.

10©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

3. Basic Condition
3.1 Configuration and Roles
3.1.1 Audio Gateway with Gateway (AG_GW)
This kind of device has the capabilities defined in the HFP specification for AG and the capabilities
defined in the DUN specification for GW. This is the device that provides access to the public
network. Typical devices are cellular phones.

3.1.1.1 Recommendation
This kind of devices should support the following roles.
• HFP AG• DUN GW

3.1.1.2 Motivation
This kind of device should support HFP AG and DUN GW role to enable Voice and Data
communication between public network and HF/ DT device.

3.1.2 HandsFree with Data Terminal (HF_DT)
This kind of device has the capabilities defined in the HFP specification for HF and the capabilities
defined in the DUN specification for DT. Typical devices are In-car devices.
3.1.2.1 Recommendation
This kind of devices should support the following roles.
• HFP HF
• DUN DT3.1.2.2 Motivation
This kind of device should support HFP HF and DUN DT role to enable Voice and Data
communication to a AG_GW device. It should also enable both of capabilities at the same time.

3.1.3 Media Player (MP)The Media Player can among other devices be a portable media player (MP3 player, video player ormobile phone) or a fixed media player (home audio/video system or in-car audio/video system).
3.1.3.1 Recommendation
The Media Player should support the following roles• A2DP and/or VDP SRC• AVRCP 1.3 TG, category 1 and at least supporting PlayStatus and the Play , Pause and Stop
commands• AVRCP 1.3 CT, category 2 and at least supporting the Volume Up and Down commands if A2DPSRC is supported.
• AVRCP TG, category 2 and at least supporting the Volume Up and Down commands if A2DPSRC is supported.
3.1.3.2 Motivation
The Media Player should support A2DP/VDP SRC role to enable streaming of audio/video to a SNK
device, it should also support the AVRCP TG role to be able to receive incoming Play, Stop andother commands from the Rendering Device or the Remote Controller. Finally it should also support
the AVRCP CT role to be able to send volume up/down commands to the Rendering Device. The
last recommendation is important since not all Rendering Devices will have a local volume control or
the Rendering Device, e.g. loudspeakers, are not in the vicinity of the user.

11

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

3.1.4 Rendering Device (RD)The Rendering Device can among other devices be headphones, loudspeakers, in-car audio
systems or a video display with optional audio capabilities.
3.1.4.1 Recommendation
The Rendering Device should support the following roles• A2DP and/or VDP SNK• AVRCP 1.3 TG, category 2, supporting at least the Volume Up and Down commands in case
A2DP SNK is supported.
• AVRCP 1.3 CT, category 1, supporting at least the Play, Pause , Stop and GetPlayStatuscommands and EVENT_PLAYBACK_STATUS_CHANGED notification
3.1.4.2 Motivation
The Rendering Device should support A2DP SNK role to be able to receive audio from a Media
Player. It should also support the AVRCP CT role to be able to send AVRCP Play, Pause, Stop
commands, among others, to the Media Player. Finally it should also support the AVRCP TG role toallow the Media Player to change the volume on the Rendering Device by sending AVRCP volume
up/down commands to it.
Rendering Devices without possibility for user input, (e.g. home audio system loudspeakers) should
not support the AVRCP CT Role.

3.1.5 Remote Controller (RC)The Remote Controller can among other devices be a device that only has the functionality of a
Remote Controller; it can also be a multi functional device that supports other functionality as well.
3.1.5.1 Recommendation
The Remote Controller should support the following role
• AVRCP 1.3 CT, category 1 supporting at least the Play, Pause, Stop and GetPlayStatuscommands and the EVENT_PLAYBACK_STATUS_CHANGED notification.
• AVRCP 1.3 CT, category 2 supporting Volume Up and Down.

3.1.5.2 Motivation
The Remote Controller should support the AVRCP CT role to be able to send volume up/down, play,stop, pause, and other commands to the Media Player.
The remote controller should support the AVRCP CT Role to be able to send play, stop, pause, andother commands to the media player. The EVENT_PLAYBACK_STATUS_CHANGED notification
will ensure that the RC knows the play back state of the media player.

3.1.6 Audio Gateway with Media Player and Gateway (AG_MP_GW)
This kind of device has the capabilities defined in the HFP specification for AG, the capabilities for aMedia Player (see 3.1.3) and the capabilities defined in the DUN specification for GW. Typicaldevices are cellular phones.
3.1.6.1 Recommendation
The recommendation is the same as written in3.1.1.1 and 3.1.3.1.
3.1.6.2 Motivation
The motivation is the same as written in 3.1.1.2 and 3.1.3.2

12©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

3.1.7 Handsfree with Rendering Device and Data Terminal (HF_RD_DT)
This kind of device has the capabilities defined in the HFP specification for HF, the capabilities for a
Rendering Device (see 3.1.4) and the capabilities defined in the DUN specification for DT. Typicaldevices are In-car devices.
3.1.7.1 Recommendation
The recommendation is the same as written in 3.1.2.1 and 3.1.4.1.
3.1.7.2 Motivation
The motivation is the same as written in 3.1.2.2 and 3.1.4.2 .

3.2 Profile Architecture
The specified profiles and protocols by the Bluetooth SIG for Audio/Video are following.
・Profile/Protocol for Streaming
ProfileA2DP(Advanced Audio Distribution
GAVDPProfile)VDP

Protocol
AVDTP(Generic Audio/Video Distribution
Profile)(Audio/Video Distribution
Transport Protocol)(Video Distribution Profile)

・Profile/Protocol for Control
ProfileAVRCP(Audio/Video Remote Control
Profile)Protocol
AVCTP(Audio/Video Control Transport
Protocol)Each profile is defined in a separate document; remote control issues are defined in the AVRCP profile
whereas streaming aspects are handled by the A2DP profile. However, there is no detailed explanation
on how to use streaming and controlling capabilities simultaneously.
It is necessary to understand that you have to refer each profile specification document before
following this guideline when you implement these profiles into products.
A2DP profile is defined as upper layer profile of GAVDP to be used with AVDTP commands for
streaming high quality stereo or mono audio.
AVDTP and GAVDP define functions for setting-up, establishment and opening of streaming channel,
but doesn't include functions for remote-controlling of Audio Video devices. This means one has toclearly understand the purpose of the audio streaming profile, which is neither to operate nor to change
the mode of devices, but to control the audio path only.
AVRCP, along with AVCTP, is defined to remotely control Audio Video device. By sending thecommand specified in the profile the sender expects the receiver to operate, change
mode, and/or report information.
The concept of these profiles and protocols is written in 2.1 Scope of each documentation.

13

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

Figure 3.2 Example of command procedure

Figure 3.2 shows an example of command procedure between the RD and the MP where the MP
receives an AVRCP Play command and then starts streaming to the RD. It is not defined whether the
streaming is started or not after MP receives AVRCP_Play command from RD since there is no
definition in profile specification and It depends on the implementation for player application. This
document is to specify how to behave .

14

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4. SCENARIOS
4.1 Use Cases for HFP + DUN
4.1.1 HFP+DUN；STARTING DATA COMMUNICATION UNDER PACKET-SWITCHEDDATA MODE DURING ONGOING CALL
4.1.1.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DT
HFP SCO Connection established with
HF_DT
DUN connection established with
[HF_DT]
DUN (PACKET-SWITCHED DATA MODE) State
N/A

HF_DT
AG_GW
AG_GW
AG_GW
[AG_GW]
N/A

Table 4.1.1-1:Pre-conditions: HFP+DUN；STARTING DATA COMMUNICATION UNDER PACKETSWITCHED DATA MODE DURING ONGOING CALL.
Note: [ ] means that the connection is optional.

4.1.1.2 User Action
User turns on DUN functionality on the HF_DT system.
4.1.1.3 Post Conditions
In the table below the Post Conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DT
HFP SCO Connection established with
HF_DT
DUN connection established with
HF_DT
DUN (PACKET-SWITCHED DATA MODE) State
Data
Communication

HF_DT
AG_GW
AG_GW
AG_GW
AG_GW
Data
Communication

Table 4.1.1-2: Post-Conditions: HFP+DUN；STARTING DATA COMMUNICATION UNDER PACKETSWITCHED DATA MODE DURING ONGOING CALL.

4.1.1.4 Recommendation
The recommendation is to set SCO or eSCO Packet type to HV3 or EV3/2-EV3 as default.
If AG requests HV1 when SCO is established, it is recommended that HF requests HV3. However, if
AG supports only HV1, HF shall accept HV1. In this case simultaneous use of HFP voicecommunication and DUN data communication is not possible.

15

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.1.1.5 Message Sequence Charts

AG_GW

HF_DT

HFP Service Level Connection established

DUN Connection established

SCO/eSCO connection established
Ongoing voice call
Outgoing call for DUN(PSDM)
If no DUN connction
DUN connection Request
Acceptendif
ATDxxxxxxxxxx
OK
Data Start
If the response is OK
Resp, (OK)CONNECTDUN Data Communication under PSDM
else
Resp, (NG)NO CARRIER
endif

Figure 4.1.1.5 HFP+DUN；STARTING DATA COMMUNICATION UNDER PACKET-SWITCHED DATA MODE
DURING ONGOING CALL.

Note: This guideline is based on the assumption that the cellular network can work voice call anddata communication simultaneously. The sequence to apply when the cellular network can nothandle the above case ( i.e. an ATD error is returned ) is left implementation specific.

16

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.1.2 HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE WHILE ONGOING CALL .
4.1.2.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DT
HFP SCO Connection established with
HF_DT
DUN connection established with
[HF_DT]
DUN (CIRCUIT-SWITCHED DATA MODE) State
N/A

HF_DT
AG_GW
AG_GW
AG_GW
[AG_GW]
N/A

Table 4.1.2.1: Pre-Conditions: HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE WHILE ONGOING CALL HFP.
Note: [ ] means that the connection is optional.

4.1.2.2 User Action
User waits for voice call termination before user turns on DUN functionality on the HF_DT system.
4.1.2.3 Post Conditions
In the table below the Post Conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DT
HFP SCO Connection established with
DUN connection established with
HF_DT
DUN (CIRCUIT-SWITCHED DATA MODE) State
Data
Communication

HF_DT
AG_GW
AG_GW
AG_GW
Data
Communication

Table 4.1.2.3: Post-Conditions: HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE WHILE ONGOING CALL HFP.

4.1.2.4 Recommendation
Under the Circuit-Switched data mode, it is impossible to use both HFP and DUN at the same time.
Therefore voice call termination should be waited to start DUN communication.

17

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.1.2.5 Message Sequence Charts
AG_GW

HF_DT

HFP Service Level Connection established

DUN Connection established
HFP (e)SCO connection established
Ongoing Voice callTerminate a Voice callTerminate a Voicecall

by AG_GW or Remote Party

by HF_DT

Wait for a voice call termination(e)SCO link release
Outgoing call for DUN(CSDM)
If no DUN connection
DUN connection Request
Acceptendif
ATDxxxxxxxxxx
Resp. OK
DUN Data communication establishedunder CSDM

Figure 4.1.2.5 HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATAMODE WHILE ONGOING CALL HFPInformation : Under CIRCUIT-SWITCHED DATA MODE, dashed lines should be handled by
Application layer of HF_DT / AG_GW

18©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.1.3 HFP+DUN;OUTGOING CALL WHILE DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE
4.1.3.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DT
HFP SCO Connection established with
DUN connection established with
HF_DT
DUN(CIRCUIT-SWITCHED DATA MODE) State
Data
communication

HF_DT
AG_GW
AG_GW
AG_GW
Data
communication

Table 4.1.3.1: Pre-Conditions: HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATION UNDERCIRCUIT-SWITCHED DATA MODE

4.1.3.2 User Action
User initiates a voice call during DUN data communication under CIRCUIT-SWITCHED DATA
MODE.
4.1.3.3 Post Conditions
In the table below the Post Conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_DT
HFP service level connection established with
HF_DTHFP SCO Connection established with
[HF_DT] *1
DUN connection established with
HF_DT
DUN(CIRCUIT-SWITCHED DATA MODE) State
N/A

HF_DT
AG_GW
AG_GW
[AG_GW] *1
AG_GW
N/A

Table 4.1.3.3:Post-Conditions: HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATION UNDERCIRCUIT-SWITCHED DATA MODE

*1 The possibility to be made the (e)SCO connection by outgoing call from the AG device depends
on the implementation of AG. For example, the (e)SCO connection will not be establishedbetween HF and AG in case that the routing of audio path is set to AG.

4.1.3.4 Recommendation
Under the CIRCUIT-SWITCHED DATA MODE, it is impossible to make a phone call at the sametime.
It is recommended to provide a way of terminating an ongoing data connection on HF_DT (by menu,
button and so on) in case user wants to make a outgoing voice call.

HF_DT should not initiate outgoing call while DUN data communication is under CIRCUITSWITCHED DATA MODE because the application layer of HF_DT knows that DUN is under
CIRCUIT-SWITCHED DATA MODE.

19©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.1.3.5 Message Sequence Charts

AG_GW

HF_DT

HFP Service Level Connection established

DUN Connection establishedAnd Data communication under CSDM

Terminate a Data callTerminate a Data callby AG_GW

or Remote Party

by HF_DT

Terminate a Data call
Outgoing call for HFP

ATD<digits>OK+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.1.3.5. HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE (User initiates a voice call on HF_DT)

20

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

AG_GW

HF_DT

HFP Service Level Connection established

DUN Connection establishedAnd Data communication under CSDM

Terminate a Data callTerminate a Data callby AG_GW

or Remote Party

by HF_DT

Terminate a Data call
Outgoing call
+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3

Sequences about (e)SCO
are written by dashed line,
because these sequences
happened or not depend
on implementation of mobile
phone.
This part comes from *1 inthe Post Condition table.

・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.1.3.54.1.3.6 HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE (User initiates a voice call on AG_GW)

21©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2 Use Cases for HFP+A2DP/VDP+AVRCP+DUN WITH SAME DEVICE
4.2.1 HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.
4.2.1.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
HFP service level connection established with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP StateSTREAMING
DUN connection established with
[HF_RD_DT ]DUN (PACKET-SWITCHED DATA MODE) State
N/A

HF_RD_DT
AG_MP_GW
AG_MP_GW
AG_MP_GWSTREAMING[ AG_MP_GW]
N/A

Table 4.2.1.1: Pre-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING
UNDER PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.
Note: [ ] means that the connection is optional.

4.2.1.2 User Action
User turns on DUN functionality on HF_RD_DT system.
4.2.1.3 Post Conditions
In the table below the Post conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
HFP service level connection established with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP StateSTREAMING
DUN connection established with
HF_RD_DT
DUN (PACKET-SWITCHED DATA MODE) State
Data
communication

HF_RD_DT
AG_MP_GW
AG_MP_GW
AG_MP_GWSTREAMING
AG_MP_GW
Data
communication

Table 4.2.1.3: Post-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING
UNDER PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC

4.2.1.4 Recommendation
The recommendation is to support V.2.0 + EDR or later version for this scenario on both
AG_MP_GW and HF_RD_DT system to keep enough band width.

22

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.1.5 Message Sequence Charts
AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection Established
AVDTP State=IDLE

DUN Connection establishedGAVDP_Connection_Establishment ()GAVDP_Start_Streaming ()Outgoing call for DUN(PSDM)
If no DUN Connection
DUN connection Request
Resp, (OK)
endif
ATDxxxxxxxxxx
OK
Data Start
If Response is OK
Resp, (OK)CONNECTDUN Data Communication under PSDM

endif

(Continued)

23

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
If Response is not OK
Resp, (NG)NO CARRIER
Data Failure
endif

Figure 4.2.1.5. HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC

24

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.2 HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.
4.2.2.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
HFP service level connection established with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP StateSTREAMING
DUN connection established with
[HF_RD_DT ]DUN(CIRCUIT-SWITCHED DATA MODE) State
N/A

HF_RD_DT
AG_MP_GW
AG_MP_GW
AG_MP_GWSTREAMING[ AG_MP_GW]
N/A

Table 4.2.2.1: Pre-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING
UNDER CIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.
Note: [ ] means that the connection is optional.

4.2.2.2 User Action
User turns on DUN functionality on HF_RD_DT system.
4.2.2.3 Post Conditions
In the table below the Post conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
HFP service level connection established with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP StateSTREAMING
DUN connection established with
HF_RD_DT
DUN(CIRCUIT-SWITCHED DATA MODE) State
Data
communication

HF_RD_DT
AG_MP_GW
AG_MP_GW
AG_MP_GWSTREAMING
AG_MP_GW
Data
communication

Table 4.2.2.3: Post-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING
UNDER CIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.

4.2.2.4 Recommendation
The recommendation is to support V.2.0 + EDR or later version for this scenario on both
AG_MP_GW and HF_RD_DT system, at least.

25

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
4.2.2.5 Message Sequence Charts
AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection Established
AVDTP State=IDLE

DUN Connection establishedGAVDP_Connection_Establishment ()GAVDP_Start_Streaming ()Outgoing call for DUN(CSDM)
If no DUN Connection
DUN connection Request
Resp, (OK)
endif
ATDxxxxxxxxxx
OK
Data Start
If Response is OK
Resp, (OK)CONNECTDUN Data Communication under CSDM

endif(Continued)

26

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
If Response is not OK
Resp, (NG)NO CARRIER
Data Failure
endif

Figure 4.2.2.5. HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.

27

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.3 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL UNDER PACKET-SWITCHEDDATA MODE
Refer to 4.13 Answer an Incoming Call of HFP1.5.
Note: An incoming call received during an ongoing DUN Packet-Switched Data Connection with an
A2DP session in idle state between the same two devices does not modify neither DUN nor A2DP
state.
In case the cellular network does not support concurrent voice and data communication, data
communication is suspended when outgoing/incoming voice calls are to be carried out.

4.2.4 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONEUNDER PACKET-SWITCHED DATA MODE AND LISTENING TO MUSIC FROM A
SAME DEVICE
Refer to “ 6.2.5 HFP+A2DP/VDP+AVRCP INCOMING CALL WHEN LISTENING TO MUSICFROM THE SAME DEVICE, NO HQ RING SIGNAL“ in the document of “SIMULTANEOUS USE
OF HFP, A2DP, AND AVRCP PROFILES” published by Bluetooth SIG.
Note: An incoming call received during an ongoing DUN Packet-Switched Data Connection with an
A2DP session in streaming state between the same two devices does not affect DUN connection
state.
In case the cellular network does not support concurrent voice and data communication, data
communication is suspended. Therefore incoming HFP calls only affect the A2DP session byinterrupting any ongoing streaming. The sequence to resume streaming is described in the White
Paper.

28

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.5 HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHEDDATA MODE
4.2.5.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP StateIDLE
DUN connection established with
HF_RD_DT
DUN(PACKET-SWITCHED DATA MODE) State
Data
communication
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with-

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE
AG_MP_GW
Data
communication
AG_MP_GW-

Table 4.2.5.1: Pre-Conditions:HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKETSWITCHED DATA MODE.

4.2.5.2 User Action
User initiates a voice call or selects “Outgoing call” on HF_RD_DT while DUN No Data/Datacommunication is ongoing under PACKET-SWITCHED DATA MODE. And starting phone call.
4.2.5.3 Post Conditions
In the table below the post-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP State during callIDLE
DUN connection established with
HF_RD_DT
DUN(PACKET-SWITCHED DATA MODE) State
Data
communication
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with
[HF_RD_DT] *1

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE
AG_MP_GW
Data
communication
AG_MP_GW[AG_MP_GW] *1

Table 4.2.5.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKETSWITCHED DATA MODE.

*1 The possibility to be made the (e)SCO connection by outgoing call from the AG device depends
on the implementation of AG. For example, the (e)SCO connection will not be establishedbetween HF and AG in case that the routing of audio path is set to AG.
4.2.5.4 Recommendation
The recommendation is to set SCO or eSCO Packet type to HV3 or EV3/2-EV3 as default.
If AG requests HV1 when SCO is established, it is recommended that HF requests HV3. However, if
AG supports only HV1, HF shall accept HV1 and recognize that multi-connection is not available inthis case.

29

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.5.5 Message Sequence Charts

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection established
AVDTP State = IDLEDUN Connection establishedAnd Data communication under PSDM

Outgoing call for HFP

ATD<digits>OK+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.2.5.5. HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHED DATA
MODE. (User initiates a voice call on HF_RD_DT)

30

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection established
AVDTP State = IDLEDUN Connection establishedAnd Data communication under PSDM

User originate a voice call
+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established

Sequences about (e)SCO
are written by dashed line,
because these sequences
happened or not depend
on implementation of mobile
phone.
This part comes from *1 inthe Post Condition table.

+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.2.5.54.2.5.6. HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHEDDATA MODE.(User initiates a voice call on AG_MP_GW)

Note: This guideline is based on the assumption that the cellular network can work voice call anddata communication simultaneously. The sequence to apply when the cellular network can nothandle the above case ( i.e. an ATD error is returned ) is left implementation specific.

31©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.6 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
4.2.6.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP State during callIDLE
DUN connection established with
HF_RD_DT
Data
DUN （ CIRCUIT-SWITCHED DATA MODE ）communication
State
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with-

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE
AG_MP_GW
Data
communication
AG_MP_GW-

Table 4.2.6.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE

4.2.6.2 User Action
User initiates a voice call or selects “Outgoing call” on HF_RD_DT while DUN Data communicationis ongoing under CIRCUIT-SWITCHED DATA MODE.
4.2.6.3 Post Conditions
In the table below the post-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP State during callIDLE
DUN connection established with
HF_RD_DT
DUN （ CIRCUIT-SWITCHED DATA MODE ） N/A(Terminated)
State
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with
[HF_RD_DT] *1

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE
AG_MP_GW
N/A(Terminated)
AG_MP_GW[AG_MP_GW] *1

Table 4.2.6.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.

*1 The possibility to be made the (e)SCO connection by outgoing call from the AG device depends
on the implementation of AG. For example, the (e)SCO connection will not be establishedbetween HF and AG in case that the routing of audio path is set to AG.
4.2.6.4 Recommendation
Under the Circuit-Switched data mode, it is impossible to make a phone call at the same time.
It is recommended to provide a way of terminating an ongoing data connection on HF_RD_DT (bymenu, button and so on) in case user wants to make a outgoing voice call..
HF_RD_DT should not initiate outgoing call while DUN data communication is under CircuitSwitched data mode because the application layer of HF_RD_DT knows that DUN is under CircuitSwitched data mode.

32©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
4.2.6.5 Message Sequence Charts

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection established
AVDTP State = IDLEDUN Connection establishedAnd Data communication under CSDM

Terminate a Data callby AG_MP_GW

Terminate a Data callor Remote Party

by HF_RD_DT

Terminate a Data call
Outgoing call for HFP

ATD<digits>OK+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.2.6.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE. （HF_RD_DT initiated）

33

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established

AVDTP Connection established
AVDTP State = IDLEDUN Connection establishedAnd Data communication under CSDM

Terminate a Data callby AG_MP_GW

Terminate a Data callor Remote Party

by HF_RD_DT

Terminate a Data call

Outgoing call
+CIEV:<callsetup>,2
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3

Sequences about (e)SCO
are written by dashed line,
because these sequences
happened or not depend
on implementation of mobile
phone.
This part comes from *1 inthe Post Condition table.

・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing

Figure 4.2.6.54.2.6.6. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE. （AG_MP_GW initiated）

34

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.2.7 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICAND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
4.2.7.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP State
Streaming
DUN connection established with
HF_RD_DT
Data
DUN （ CIRCUIT-SWITCHED DATA MODE ）communication
State
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with-

HF_RD_DT
AG_MP_GW
AG_MP_GW
Streaming
AG_MP_GW
Data
communication
AG_MP_GW-

Table 4.2.7.14.2.7.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE

4.2.7.2 User Action
User initiates a voice call or selects “Outgoing call” on HF_RD_DT while DUN Data communicationis ongoing under Circuit-Switched data mode.
4.2.7.3 Post Conditions
In the table below the post-conditions for this scenario are listed.
DeviceAG_MP_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
HF_RD_DT
AVDTP State during call
IDLE or OPEN
(Suspended)
DUN connection established with
HF_RD_DT
DUN （ CIRCUIT-SWITCHED DATA MODE ） N/A(Terminated)
State
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with during [HF_RD_DT] *1
cal

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE or OPEN
(Suspended)
AG_MP_GW
N/A(Terminated)
AG_MP_GW[AG_MP_GW] *1

Table 4.2.7.34.2.7.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
DURING CALL.
*1 The possibility to be made the (e)SCO connection by outgoing call from the AG device depends
on the implementation of AG. For example, the (e)SCO connection will not be establishedbetween HF and AG in case that the routing of audio path is set to AG.

DevicePaired with
AVDTP Signaling channel established with
AVDTP State after call
DUN connection established with
DUN （ CIRCUIT-SWITCHED DATA MODE ）State
HFP service level connection established with
HFP SCO connection established with after call

AG_MP_GW
HF_RD_DT
HF_RD_DT
Streaming

HF_RD_DT
AG_MP_GW
AG_MP_GW
Streaming

HF_RD_DT
N/A(Terminated)

AG_MP_GW
N/A(Terminated)

HF_RD_DT-

AG_MP_GW-

Table 4.2.7.34.2.7.4: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE

35©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
AFTER CALL

4.2.7.4 Recommendation
Under the Circuit-Switched data mode, it is impossible to make a phone call at the same time.
It is recommended to provide a way of terminating an ongoing data connection on HF_RD_DT (bymenu, button and so on) in case user wants to make a outgoing voice call..
HF_RD_DT should not initiate outgoing call while DUN data communication is under CircuitSwitched data mode because the application layer of HF_RD_DT knows that DUN is under CircuitSwitched data mode.
The procedure of stop streaming at Outgoing call is same as 6.2.8 of SIG WP[9].

36©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
4.2.7.5 Message Sequence Charts

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established
AVDTP Connection established
AVDTP State = STREAMINGDUN Connection establishedAnd Data communication under CSDM
Terminate a Data callTerminate a Data callby AG_MP_GW

by HF_RD_DT

or Remote Party
Terminate a Data call
Outgoing call for HFP

ATD<digits>OK+CIEV:<callsetup>,2
Subscenario : halt streaming
request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing
Terminate a voice call

・・・
+CIEV:<call>,0close (e)SCO
Subscenario : restore streaming

37

Terminate a voice call©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
Figure 4.2.7.54.2.7.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICAND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.（HF_RD_DT
initiated）

AG_MP_GW

HF_RD_DT

HFP Service Level Connection established
AVDTP Connection established
AVDTP State = STREAMINGDUN Connection establishedAnd Data communication under CSDM
Terminate a Data callby AG_MP_GW

Terminate a Data callor Remote Party

by HF_RD_DT

Terminate a Data call
Outgoing call
+CIEV:<callsetup>,2
Subscenario : halt streaming
request for (e)SCO
accept (e)SCO(e)SCO established

Sequences about (e)SCO
are written by dashed line,
because these sequences
happened or not depend
on implementation of mobile
phone.
This part comes from *1 inthe Post Condition table.

+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing
Terminate a call

・・・
+CIEV:<call>,0close (e)SCO

Terminate a call

Subscenario : Restore streaming

Figure 4.2.7.54.2.7.6. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO
MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE. （ AG_MP_GW
initiated

38©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

Note: This guideline is based on the assumption that the cellular network can work voice call anddata communication simultaneously. The sequence to apply when the cellular network can nothandle the above case ( i.e. an ATD error is returned ) is left implementation specific.

39

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.3 Use Cases for HFP+A2DP/VDP+AVRCP+DUN WITH THE THIRD
DEVICE
4.3.1 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE
THIRD DEVICE.
In case the cellular network does not support concurrent voice and data communication, data
communication is suspended when outgoing/incoming voice calls are to be carried out.
Refer to 4.2.1
Note: Regardless of the Streaming source ( same device or third device ), streaming is notaffected by the DUN session. The sequence for DUN is therefore the same as in 4.2.1.

4.3.2 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE
THIRD DEVICE.
Refer to 4.2.2
Note: Regardless of the Streaming source ( same device or third device ), streaming is notaffected by the DUN session. The sequence for DUN is therefore the same as in 4.2.2.

4.3.3 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONEUNDER PACKET-SWITCHED DATA MODE
Refer to 4.13 Answer an Incoming Call of HFP1.5 [1].
Note: An incoming call received during an ongoing DUN Packet-Switched Data Connection withan A2DP session in idle state with the third device does not modify neither DUN nor A2DP state.
In case the cellular network does not support concurrent voice and data communication, data
communication is suspended when outgoing/incoming voice calls are to be carried out but the
DUN connection still exists.
Therefore, the sequence for HFP is as described in 4.13 Answer an Incoming Call of HFP1.5 [1]specification.

40

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.3.4 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONEUNDER PACKET-SWITCHED DATA MODE AND LISTENING TO MUSIC FROM
THE THIRD DEVICE
Refer to “ 6.2.6 HFP+A2DP/VDP+AVRCP INCOMING CALL WHEN LISTENING TO MUSICFROM A THIRD DEVICE, NO HQ RING SIGNAL[9]“ in the document of “SIMULTANEOUS USE
OF HFP, A2DP, AND AVRCP PROFILES” published by Bluetooth SIG
Note: An incoming call received during an ongoing DUN Packet-Switched Data session while an
A2DP session is streaming data from the third device, does not affect the DUN session.
In case the cellular network does not support concurrent voice and data communication, data
communication is suspended when outgoing/incoming voice calls are executed.
Therefore incoming HFP calls only affect the A2DP session by interrupting any ongoing streaming.
The sequence to resume streaming is described in the White Paper[9].

4.3.5 HFP-A2DP/VDP-AVRCP+DUN; OUTGOING CALL DURING NO DATA/DATACOMMUNICATION UNDER PACKET-SWITCHED DATA MODE
Refer to 4.2.5

4.3.6 HFP + A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE(IN CASE OF THE
THIRD DEVICE)
Refer to 4.2.6

41

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

4.3.7 HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICAND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE (IN
CASE OF THE THIRD DEVICE)
4.3.7.1 Pre-Conditions
In the table below the pre-conditions for this scenario are listed.
DEVICE
AG_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
AVDTP State
N/A
AVCTP Signaling channel established with
DUN connection established with
HF_RD_DT
Data
DUN （ CIRCUIT-SWITCHED DATA MODE ）communication
State
HFP service level connection established with
HF_RD_DT
HFP SCO connection established with-

HF_RD_DT
AG_GW, MPMPStreaming
MP
AG_GW
Data
communication
AG_GW
-

MP
HF_RD_DT
HF_RD_DT
Streaming
HF_RD_DT
N/A-

Table 4.3.7.14.3.7.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA
MODE

4.3.7.2 User Action
User initiates a voice call or selects “Outgoing call” on HF_RD_DT while DUN Data communicationis ongoing under Circuit-Switched data mode.
4.3.7.3 Post Conditions
In the table below the post-conditions for this scenario are listed.
Device
AG_GW
Paired with
HF_RD_DT
AVDTP Signaling channel established with
AVDTP State during call
N/A
AVCTP Signaling channel established with
DUN connection established with
HF_RD_DT
N/A(Terminated)
DUN（CIRCUIT-SWITCHED DATA MODE） StateHFP service level connection established with
HF_RD_DT
HFP SCO connection established with during call
[HF_RD_DT] *1

HF_RD_DT
AG_GW
MP
IDLE
MP
AG_GW
N/A(Terminated)
AG_GW[AG_GW] *1

MP
HF_RD_DT
HF_RD_DT
IDLE
HF_RD_DT
N/A-

Table 4.3.7.34.3.7.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
DURING CALL.
*1 The possibility to be made the (e)SCO connection by outgoing call from the AG device depends
on the implementation of AG. For example, the (e)SCO connection will not be establishedbetween HF and AG in case that the routing of audio path is set to AG.

DevicePaired with
AVDTP Signaling channel established with
AVDTP State after call
AVCTP Signaling channel established with
DUN connection established with
DUN（CIRCUIT-SWITCHED DATA MODE） StateHFP service level connection established with
HFP SCO connection established with after call

AG_GW
HF_RD_DT-

HF_RD_DT
AG_GW
MP

MP
HF_RD_DT
HF_RD_DT

N/A
HF_RD_DT
N/A(Terminated)
HF_RD_DT-

StreamingMP
AG_GW
N/A(Terminated)
AG_GW-

Streaming
HF_RD_DT
N/A-

Table 4.3.7.34.3.7.4: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE AFTER

42

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
CALL.

4.3.7.4 Recommendation
Under the Circuit-Switched data mode, it is impossible to make a phone call at the same time.
It is recommended to provide a way of terminating an ongoing data connection on HF_RD_DT (bymenu, button and so on) in case user wants to make a outgoing voice call..
HF_RD_DT should not initiate outgoing call while DUN data communication is under CircuitSwitched data mode because the application layer of HF_RD_DT knows that DUN is under CircuitSwitched data mode.
The procedure of stop streaming at Outgoing call is same as 6.2.7 of SIG WP[9].

43©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
4.3.7.5 Message Sequence Charts

AG_GW

HF_RD_DTMP

HFP Service Level Connection
established
AVDTP Connection established
AVDTP State = STREAMINGDUN Connection establishedAnd Data communication underTerminate a Data callTerminate a Data callby AG_GW

or Remote Party

by HF_RD_DT

Terminate a Data call
Outgoing call for HFP

AVRCP Pause
AVRCP Pause Responce
ATD<digits>OK+CIEV:<callsetup>,2

Subscenario :halt streaming

GAVDP Connection Release( )request for (e)SCO
accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing
・・・+CIEV:<call>,1+CIEV:<callsetup>,0
AVRCP PlayAVRCP Play Responce
Subscenario :Restore streaming
Figure 4.3.7.54.3.7.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE IN CASE OF THE THIRD
DEVICE. （HF_RD_DT initiated）

44

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

AG_GW

HF_RD_DTMP

HFP Service Level Connection
established
AVDTP Connection established
AVDTP State = STREAMINGDUN Connection establishedAnd Data communication underTerminate a Data callTerminate a Data callby AG_GW

or Remote Party

by HF_RD_DT

Terminate a Data call
Outgoing call
+CIEV:<callsetup>,2
Sequences about (e)SCO
are written by dashed line,
becausethese
sequences happened or
notdependon
implementation of mobile
phone. This part comesfrom *1 in the
Post
Condition table.

AVRCP Pause
AVRCP Pause Responce
request for (e)SCO

Subscenario :halt streaming
GAVDP Connection Release( )accept (e)SCO(e)SCO established+CIEV:<callsetup>,3・・・+CIEV:<call>,1+CIEV:<callsetup>,0Call Active
Call Ongoing
Terminate a voice call

・・・
+CIEV:<call>,0close (e)SCO

Terminate a voice call
AVRCP PlayAVRCP Play Responce
Subscenario :Restore streaming

Figure 4.3.7.54.3.7.6. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE IN CASE OF THE THIRD
DEVICE. （AG_GW initiated）

Note: This guideline is based on the assumption that the cellular network can work voice call and45©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
data communication simultaneously. The sequence to apply when the cellular network can nothandle the above case ( i.e. an ATD error is returned ) is left implementation specific.

46

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

5. Appendix A (Multi Connection use cases)
Multi connection use cases discussed in this document are described in the following tables.
(1) Combination of Two Applications
Pre-condition
HFP

DUN

A2DP

PSDM
SLC

OnGoing
no DATAStreaming*3*4(covered by
WP)*1
Outgoing

4.1.3

PSDM

Same as4.2.1
Same as
4.2.2

4.1.1

DUN
CSDM

*1

4.1.2

IDLE

*1

IDLE
A2DP

Event

Same Device Scenario

Incoming
HFP

CSDM
DATA

*2
Streaming*5(covered by
WP)

Third Device Scenario

Incoming
HFP
Outgoing

Same as4.3.1
Same as
4.3.2

PSDM
DUN
CSDM

*1

IDLE
A2DP

*1

*2

Streaming(2) Combination of Three Applications(2-1) in case DUN event occurred
Pre-condition

DUN Event

HFP=SLCHFP=Ongoing

A2DP=
Streaming

A2DP=
IDLE

A2DP=
Streaming

A2DP=
IDLE

Same
deviceScenario

PSDM

4.2.1

Same as 4.2.1

CSDM

4.2.2

Same as 4.2.2

ThirddeviceScenario

PSDM

4.3.1

Same as 4.3.1

Same as 4.1.1

CSDM

4.3.2

Same as 4.3.2

Same as 4.1.2

Same as 4.1.1
Same as 4.1.2*2

47

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English(2-2) in case A2DP event occured
Pre-condition
HFP=SLCA2DP Event

DUN=
no DATASame
deviceScenario

IDLE

Third
deviceScenarioIDLE

HFP=Ongoing
DUN=
DATA

DUN=
no DATADUN=
DATAStreaming*1*2

Streaming(2-3) in case HFP event occurred
Pre-condition
A2DP=IDLE
DUN=PSDM

HFP Event

DUN=
no DATAA2DP=Streaming
DUN=
CSDM

DUN=
DATA

DUN=PSDM
DUN=
no DATA

DUN=
DATA

DUN=
CSDM

Same
deviceScenario

Incoming

4.2.3(No HQ Ring)*3

4.2.4(No HQ Ring)*3

Outgoing

4.2.5

4.2.6

*6 (covered by WP)

4.2.7

Third
deviceScenario

Incoming

4.3.3(No HQ Ring)*3

4.3.4(No HQ Ring)*3

Outgoing

4.3.5

4.3.6

*7 (covered by WP)

4.3.7*1 This case should not be cared because there isn't technical affection. Since the Pre-condition does
not affect behavior of event, the message sequence charts when each profile (HFP, DUN, A2DP) is
operated independently are applied in this case. Then behavior shall be referred to sequences foreach profile.
*2 This case should not be cared because this combination of application is unusual.
*3 This case should not be cared because incoming call isn't available during CSDM data
communication.
*4 This case is covered by SIMULTANEOUS USE OF HFP, A2DP, AND AVRCP PROFILES [9], 6.2.8
HFP+A2DP/VDP+AVRCP INCOMING CALL WHEN LISTENING TO MUSIC TO THE SAMEDEVICE, NO HQ RING SIGNAL*5 This case is covered by SIMULTANEOUS USE OF HFP, A2DP, AND AVRCP PROFILES [9], 6.2.9
HFP+A2DP/VDP+AVRCP INCOMING CALL WHEN LISTENING TO MUSIC FROM A THIRD
DEVICE, NO HQ RING SIGNAL*6 Even if a call is received or triggered during A2DP streaming with a concurrent DUN session in No
Data or PSDM state, the DUN session is not affected. The sequence described in 6.2.8 of the
SIMULTANEOUS USE OF HFP, A2DP, AND AVRCP PROFILES [9] therefore applies.
*7 Even if a call is received or triggered during A2DP streaming with a concurrent DUN session in No
Data or PSDM state, the DUN session is not affected. The sequence described in 6.2.7 of the
SIMULTANEOUS USE OF HFP, A2DP, AND AVRCP PROFILES [9] therefore applies.

48

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

6. Appendix B (Notes on the implementation)
In this chapter, several points to be noticed on the implementation are summarized in order to keepinteroperability of Bluetooth communication.

B-1 Note on AVRCP Pass Through Command
In AVRCP, if a button remains pressed after a PASS THROUGH press command is sent a further
PASS THROUGH press command shall be sent within 2 seconds of the previous press
command. This must repeat until the button is released. This is according to AV/C Panel Subunit
Specification[8] which is referred by AVRCP Specification[5].

49©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

7. Appendix C (HALT STREAMING Sub-scenarios)
In the following message sequence chart some procedures of the GAVDP specification are used. For the
specific content of the procedures, please see the GAVDP specification.

INT

ACP

AVDTP in state STREAMINGIF SUSPEND supported

GAVDP_Suspend( )Signalingandmedia
channels remains open no
media data any more.

ELSE

GAVDP_Connection_Release( )Signaling channels
remains open

ENDIF

Figure 7.1: Sub-scenario halt streaming

Even if ACP supports SUSPEND, it shall be prepared that GAVDP_Connection_Release isused since AVDTP_SUSPEND is not a mandatory command.

50©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

8. Appendix D (RESTORE STREAMING Sub-scenarios)
In the following message sequence chart some procedures of the GAVDP specification are used. For the
specific content of the procedures, please see the GAVDP specification.

INT

ACP

AVDTP in state IDLE or OPEN

IF AVDTP state = IDLEGAVDP_Connection_Establis
hment( )ENDIF

GAVDP_Start_Streaming( )metadata transfer

Figure 8.1: Sub-scenario restore streaming

If streaming was halted with GAVDP_Connection_Release it depends on the source implementation,
how the stream is continued ( e.g. last position or next song or …)

51

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

9. LIST OF FIGURES
Figure2.1 example system configuration Case 1
Figure 2.2. example system configuration Case 2
Figure 3.2 Example of command procedure
Figure: 4.1.1.5. HFP+DUN ； STARTING DATA COMMUNICATION UNDER PACKET-SWITCHEDDATA MODE DURING ONGOING CALL
Figure: 4.1.2.5. HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE WHILE ONGOING CALL HFP
Figure: 4.1.3.5. HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE (User initiates a voice call on HF_DT)
Figure: 4.2.1.5. HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC
Figure: 4.2.2.5. HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC.
Figure 4.2.5.5. HFP+A2DP/VDP+AVRCP+DUN ； OUTGOING CALL UNDER PACKET-SWITCHEDDATA MODE (User initiates a voice call on HF_DT).
Figure 4.2.5.6. HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHED DATA
MODE. (User initiates a voice call on AG_MP_GW)
Figure 4.2.6.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE. (User initiates a voice call on HF_DT)
Figure 4.2.6.６. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE. (User initiates a voice call on
AG_MP_GW)
Figure 4.3.7.54.2.7.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICAND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.（HF_RD_DT
initiated）
Figure 4.3.7.54.2.7.6. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICAND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.（AG_MP_GW
initiated）
Figure 4.3.7.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE IN CASE OF THE THIRD
DEVICE. （HF_RD_DT initiated）
Figure 4.3.7.54.3.7.6. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSICDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE IN CASE OF THE
THIRD DEVICE. （AG_GW initiated）
Figure 7.1: Sub-scenario halt streaming
Figure 8.1: Sub-scenario restore streaming52©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

10. LIST OF TABLES
Table 4.1.1.1:Pre-conditions: HFP+DUN ； STARTING DATA COMMUNICATION UNDER PACKETSWITCHED DATA MODE DURING ONGOING CALL.
Table 4.1.1.3: Post-Conditions: HFP+DUN ； STARTING DATA COMMUNICATION UNDER PACKETSWITCHED DATA MODE DURING ONGOING CALL.
Table 4.1.2.1: Pre-Conditions: HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE WHILE ONGOING CALL HFP.
Table 4.1.2.3: Post-Conditions: HFP+DUN; STARTING DATA COMMUNICATION UNDER CIRCUITSWITCHED DATA MODE WHILE ONGOING CALL HFP.
Table 4.1.3.1: Pre-Conditions: HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE
Table 4.1.3.3:Post-Conditions: HFP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE
Table 4.2.1.1: Pre-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATIONSTARTING UNDER PACKET-SWITCHED DATA MODE WHILE LISTENING TO
MUSIC.
Table 4.2.1.3: Post-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATIONSTARTING UNDER PACKET-SWITCHED DATA MODE WHILE LISTENING TO
MUSIC
Table 4.2.2.1: Pre-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATIONSTARTING UNDER CIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO
MUSIC.
Table 4.2.2.3: Post-Conditions: HFP + A2DP/VDP + AVRCP + DUN; DATA COMMUNICATIONSTARTING UNDER CIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO
MUSIC.
Table 4.2.5.1: Pre-Conditions:HFP+A2DP/VDP+AVRCP+DUN ； OUTGOING CALL WITH NO
DATA/DATA COMMUNICATION UNDER PACKET-SWITCHED DATA MODE.
Table 4.2.5.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN ； OUTGOING CALL WITH NO
DATA/DATA COMMUNICATION UNDER PACKET-SWITCHED DATA MODE.
Table 4.2.6.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
Table 4.2.6.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.
Table

4.3.7.54.2.7.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE

Table 4.3.7.54.2.7.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE DURING CALL
Table 4.3.7.54.2.7.4: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE AFTER CAL
Table

4.3.7.54.3.7.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHEDDATA MODE (IN CASE OF THE THIRD DEVICE

Table 4.3.7.54.3.7.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE

53

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATAMODE DURING CALL.
Table 4.3.7.54.3.7.4: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE
LISTENING TO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATAMODE AFTER CALL.

54

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

References[1] HFP specification 1.5 or later from www.bluetooth.org[2] AVDTP specification 1.0 or later from www.bluetooth.org[3] A2DP specification 1.0 or later from www.bluetooth.org[4] AVCTP specification 1.0 or later from www.bluetooth.org[5] AVRCP specification 1.0 or later from www.bluetooth.org[6] VDP specification 1.0 or later from www.bluetooth.org[7] GAVDP specification 1.0 or later from www.bluetooth.org[8] DUN specification 1.0 or later from www.bluetooth.org[9] SIMULTANEOUS USE OF HFP, A2DP, AND AVRCP PROFILES from www.bluetooth.org

55©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 English

MCPC TR-008 version 1.2 English
Bluetooth® Multi-Connection Technical Reference
1.

24th December 2009

Mobile Computing Promotion Consortium
Hasegawa Green Bldg. 5-12 Shiba-Koen 3-chome, Minato-ku, Tokyo, 105-0011 Japan
Copying part or everything in this document without permission becomes copyright and bookmaker's
infringements of right. The reprint from this document is a principle prohibition. Please obtain thepermission of mobile computing promotion consortium (MCPC) when reprinting in other books, etc.

56