MCPC-TR008
Bluetooth Multi-Connection
Technical Reference
Version 1.2 Japanese
2009 年 12 月 24 日

モバイルコンピューティング推進コンソーシアム
技術委員会
Mobile Computing Promotion ConsortiumHistory / 変更履歴
日付
2008年 9月11日
2008年12月23日
2009年 3月25日

Version
1.00
1.00 R01
1.1

2009年12月24日

1.2

変更内容
Base version initial release.
SIG Feedback 反映
Terms and AbbreviationsへのCT、TG追記
4.2.7、4.3.7追加
7章にAppendix C (Halt Streaming) 追加
1.2章、5章Appendix Aに英訳追記
4.1.3、4.2.5、4.2.6、4.2.7、4.3.7にAGからの発呼を追加
4.2.7、4.3.7にStreaming再開までの手順追加
7章にAppendix D (Restore Streaming)追加
1章と2章の記載順入れ替え

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

ドキュメント発行者、および著作権者:〒105-0011
東京都港区芝公園3-5-12 長谷川グリーンビル
モバイルコンピューティング推進コンソーシアム (MCPC)
電話： 03-5401-1935
ＦＡＸ： 03-5401-1937
ＥＭＡＩＬ： office@mcpc-jp.org
WEB SITE: http://www.mcpc-jp.org

機密保持について:
MCPC会則、MCPC IP Policyを遵守

免責について:本ドキュメントはモバイルコンピューティングに関する標準仕様、推奨仕様などを提供するもので、モバイル
コンピューティング推進コンソーシアム（以下MCPCとする）は、本ドキュメントを使用した結果発生した損
害、第三者の特許、またはその他の権利の侵害に対して、一切の責任を負わない。また、本ドキュメントはMCPC、または第3三者が保持するいかなる権利のライセンスを許諾するものではない。

2©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 JapaneseContributors
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 Japanese

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 Japanese
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 ....................... 39
4.3.1 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDER
PACKET-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE THIRD
DEVICE.................................................................................................................................... 39
4.3.2 HFP+A2DP/VDP+AVRCP+DUN; DATA COMMUNICATION STARTING UNDERCIRCUIT-SWITCHED DATA MODE WHILE LISTENING TO MUSIC FROM THE THIRD
DEVICE.................................................................................................................................... 39
4.3.3 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONE UNDER
PACKET-SWITCHED DATA MODE ......................................................................................... 39
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................................................................................................................................................. 40

5

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

4.3.5 HFP-A2DP/VDP-AVRCP+DUN; OUTGOING CALL UNDER PACKET-SWITCHED DATAMODE ...................................................................................................................................... 40
4.3.6 HFP + A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER CIRCUIT-SWITCHED DATA MODE(IN CASE OF THE THIRD DEVICE) .................. 40
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)....................................................................................................................... 41
4.3.7.1 Pre-Conditions .................................................................................................................41
4.3.7.2 User Action ......................................................................................................................41
4.3.7.3 Post Conditions................................................................................................................41
4.3.7.4 Recommendation.............................................................................................................424.3.7.5 Message Sequence Charts..............................................................................................43

5. Appendix A (Multi Connection use cases).................................................................46
6. Appendix B （実装上の注意事項）..................................................................................48
7. Appendix C (HALT STREAMING Sub-scenarios) ......................................................49
8. Appendix D (RESTORE STREAMING Sub-scenarios) ..............................................50
9. LIST OF FIGURES ........................................................................................................51
10. LIST OF TABLES ........................................................................................................52

6

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 JapaneseTerms 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 Japanese

1. Document Terminology
・することができる
してもよい
(may)

推奨または要求に自由な選択肢を示す。

・すべきである(should)

必須ではないが強い推奨を示す。実施の際、必須ではないが考慮すべき。

・しなければならない(shall)必須要求を示す。接続性、仕様準拠のために必ず実施しなければならない。

2. Introduction / 概要
2.1 Scope
このドキュメントは、Bluetooth SIG発行のSimultaneous Use of HFP, A2DP and AVRCP_WP [9]を元に作成され、どのようにしてA2DPとAVRCPが一緒に使用されなければならないか、また、プロファイルの中で定義された全ての機能の中で、高い相互接続性を達成するために、A2DPとAVRCPが、他のプロファイ
ル(特にこのドキュメントではHFPとDUN)とどのようにして一緒に使用しなければならないかを記述する。本
ドキュメントで定義されているシナリオおよびシーケンスは必須ではないが、推奨されるものである。
このドキュメントでは、各ユースケースに直接関係のあるプロファイルの動作に関してのみ記載する。動作記載の無いプロファイルの使用は可能だが、接続の有無や動作ステータスは各社の実装に依存するものとする。例えば、4.2.1のケースではAVRCPは動作に直接関係しないので記載していないが、両機がAVRCPをサポートしている場合は、接続されていることを前提とする。

[注意]
本ドキュメントは、その内容を強制するものではなく、Bluetooth SIG Inc. の権利を侵害するものではない。
またその利用に関しては、利用者の責任において実施されるものとする。MCPC は本ドキュメントに関する
法的侵害、市場性、またあるいは特定の目的に対する整合性を含むいかなる明示的、または暗示的保証をしない。

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

2.2 System
The following Figure 2.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 Japanese

2.3 Role Switch
頻繁なRole切り替えの回避や、マルチ接続時に通信帯域を有効に活用するため、現在の接続状態において、自機のRoleをMasterあるいはSlaveに固定すべきではなく、どちらで動作しても問題ない場合は、接続相手機器からのRoleスイッチ切り替え要求を受け入れることが望ましい。

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

3. Basic Condition
3.1 Configuration and Roles
3.1.1 Audio Gateway with Gateway (AG_GW)
HFPに規定されるAGと、DUNに規定されるGWの両方の機能を併せ持つ機器であり、公衆網にアクセス可能な機器。代表的なものは携帯電話。
3.1.1.1 Recommendation
AG_GWは以下のRoleに対応する。
• HFP AG• DUN GW
3.1.1.2 Motivation
AG_GWはHFP AGとDUN GWの両方の機能を対応することにより、公衆網とHF/DTとの間で音声/データ
通信を可能とする。音声/データ通信共に、同時使用できることが望ましい。同時使用できない場合には、各機能を切り替えて使用する。

3.1.2 HandsFree with Data Terminal (HF_DT)
HFPに規定されるHFと、DUNに規定されるDTの両方のRoleを併せ持つ機器。代表的なものは車載機。
3.1.2.1 Recommendation
HF_DTは以下のRoleに対応する。
• HFP HF
• DUN DT3.1.2.2 Motivation
HF_DTはHFP HFとDUN DTの両方の機能を対応することにより、AG_GWとの間で音声/データ通信を可能とする。音声/データ通信は、同時に使用可能であること。

3.1.3 Media Player (MP)
メディアプレーヤーには、ポータブルメディアプレーヤー（MP3プレーヤー、ビデオプレーヤー、携帯電話）または据え置き型のメディアプレーヤー（ホームオーディオ/ビデオシステム, カーオーディオ/ビデオシステム）がある。
3.1.3.1 Recommendation
メディアプレーヤーは以下のRoleに対応する。
• A2DP SRCとVDP SRCの両方、またはどちらか一方• AVRCP1.3 TG、category 1に対応し、少なくともPlay StatusとPLAY/PAUSE / STOP コマンドをサポートする• A2DP SRC に 対 応 し て い る 場 合 は 、 AVRCP CT 、 category 2 に 対 応 し 、 少 な く と も ボ リ ュ ー ム
UP/DOWNコマンドをサポートする• A2DP SRCに対応している場合は、AVRCP TG category2に対応し、少なくともボリュームUP/DOWNコ
マンドをサポートする。
3.1.3.2 Motivation
MPはSNKデバイスへオーディオ/ビデオのストリーミングを行うため、A2DP/VDP SRCのRoleをサポートする。また、RDまたはRCからのPLAY , STOPやその他のコマンドを受信するためにAVRCP TGのRoleをサポートする。なお、MPはRDに、ボリュームアップ/ダウンコマンドを送信するためにAVRCP CTもサポートする。
全てのRDがローカルボリュームコントロール機能を持っているとは限らず、またユーザーの近くに設置されていないスピーカーのようなRDをMPからボリュームコントロールするために、上記推奨の3番目の項目が11©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 Japanese
重要である。MPがAVRCP TG category2になる理由は、RCがMPに接続してボリュームUP/DOWNコマン
ドを送信可能とするためである。

3.1.4 Rendering Device (RD)
RDには、ヘッドホン、スピーカ、カーオーディオ、オプショナルオーディオ機能付きビデオディスプレイなどのデバイスがある。
3.1.4.1 Recommendation
RDは、以下のRoleに対応する。
• A2DP SNKとVDP SNKの両方、またはどちらか一方• A2DP SNKに対応する場合はAVRCP1.3 TG、Category 2 に対応し、少なくともVolume Up/Downコ
マンドをサポートする。
• AVRCP1.3 CT、Category 1 に対応し、少なくともPLAY/PAUSE/STOP、GetPlayStatus コマンドとEVENT_PLAYBACK_STATUS_CHANGED notificationをサポートする。
3.1.4.2 Motivation
RDはMPからオーディオを受信する為にA2DP SNKに対応し、MPとの間でPLAY, PAUSE, STOP、
Forward 、 Backward 、 GetPlayStatus コ マ ン ド を 送 信 す る 為 に AVRCP CT に 対 応 す る 。
EVENT_PLAYBACK_STATUS_CHANGED notificationは、RDがMediaPlayerの再生状態を認識するために使用される。
さらにMPがAVRCPボリュームUP/Downコマンドを送ることにより、RDのボリュームを変えられるようにす
る為、RDはAVRCP TGに対応する。
ユーザ操作(例えばホームオーディオ・スピーカー)が出来無いRDは、AVRCP CTをサポートする必要はな
い。

3.1.5 Remote Controller (RC)
RCはリモートコントローラーの機能を持った機器であるが、他の機能を合わせ持った機器もある。
3.1.5.1 Recommendation
RCは以下の機能に対応する• AVRCP1.3 CTのカテゴリー1に対応し、少なくともPLAY、PAUSE、STOP、GetPlayStatusコマンドとEVENT_PLAYBACK_STATUS_CHANGED notificationに対応する。
• AVRCP CT category2に対応し、ボリュームUP/DOWNコマンドをサポートする。
3.1.5.2 Motivation
RCは、ボリュームアップダウン、PLAY、STOP、PAUSEやその他のコマンドをMPに送信するために、
AVRCP の CT に 対 応 す る 。 EVENT_PLAYBACK_STATUS_CHANGED notification は 、 RC がMediaPlayerの再生状態を認識するために使用される。

3.1.6 Audio Gateway with Media Player and Gateway (AG_MP_GW)
MP(3.1.3参照)と、HFPに規定されるAGと、DUNに規定されるGWの機能を併せ持つ機器である。代表的なものは携帯電話。
3.1.6.1 Recommendation
3.1.1.1および3.1.3.1と同様である。
3.1.6.2 Motivation
3.1.1.2および3.1.3.2と同様である。

12

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

3.1.7 Handsfree with Rendering Device and Data Terminal (HF_RD_DT)
RD(3.1.4参照)と、HFPに規定されるHFと、DUNに規定されるDTの機能を併せ持つ機器。代表的なものは車載機。
3.1.7.1 Recommendation
3.1.2.1および3.1.4.1と同様である。
3.1.7.2 Motivation
3.1.2.2および3.1.4.2と同様である。

3.2 Profile Architecture
Bluetooth SIGのAudio/Videoに関するプロファイル・プロトコルとしては以下が規定されている。
・ストリーミング系プロファイル、プロトコル
ProfileA2DP(Advanced Audio Distribution
GAVDPProfile)VDP

Protocol
AVDTP(Generic Audio/Video Distribution
Profile)(Audio/Video Distribution
Transport Protocol)(Video Distribution Profile)・コントロール系プロファイル、プロトコル
ProfileAVRCP
AVCTP(Audio/Video Remote Control
Profile)Protocol(Audio/Video Control Transport
Protocol)個々のプロファイルは規格書が個別に存在するが、ストリーミング系プロファイルとコントロール系プロファイ
ルの組み合わせ動作については規格書中に明確な規定がない。
これらのプロファイルを製品に実装しようとする場合は、まず、それぞれの規格書を参照する事が不可欠であり、それを理解した上で、本ガイドラインを参照する必要がある。
ストリーミング系の上位プロファイルでオーディオストリーミングに用いられるA2DPは、GAVDPの上位に位置
しAVDTPコマンドと共に用いられ、Bluetoothのリンク上でハイクオリティなステレオやモノラルの音声信号の伝播を実現する事を目的に策定されている。これらのプロファイル/プロトコルでは、音声信号伝播経路のセットア
ップ・確立・開放等の制御を目的とした機能を規定しており、AV機器のリモートコントロールを行う機能は含まれていない。よってストリーミング系プロファイルでは、AV機器の動作および状態変化を期待しているのではな
く、あくまでBluetoothのリンク上での音声信号伝播経路の制御を目的としているという事を認識する必要がある。
コントロール系プロファイルのAVRCPはAVCTPと共に用いられ、その名の通り”A/V機器のリモートコントロールを実現する”プロファイルである。このプロファイルを用いて、コマンド送信側機器はコマンド受信側機器に対し、伝送したコマンドの意図する動作・状態変化および情報交換を期待する。
基本的な考え方は各仕様書の2.1 Scopeに記載されている通りである。

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

Figure 3.2 Example of command procedure

Figure3.2は、RDからのAVRCP Playコマンドを受信したMPが、ストリーミングデータを転送する場合の一例である。AVRCP Playコマンドを受信したMPがストリーミングデータ転送を開始するかどうかは、プロファイル仕様に規定が無くアプリケーションの実装依存であるため、全てのMPが上記一例に当てはまるとは限らない。これらの動作規定を補完するために本書が存在する

14

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

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 Japanese

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 connection
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: 本ガイドラインはパケットデータ通信中の発呼が可能な携帯網での実装をもとに作成したものである。網側の仕様によりパケットデータ通信中の発呼が不可能で、ATDに対してErrorが返ってくる場合のHF
デバイス側での処理は実装依存である。

16

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

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 Japanese

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 Japanese

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_DT
HFP 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 AG機器操作による発呼で(e)SCOが接続されるかどうかは、AG機器の実装に依存する。例えば、AG機器の動作設定がハンドセットでの通話に設定されている場合、(e)SCOは接続されない。
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 Japanese

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 Japanese

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

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.1.3.5 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 Japanese

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 Japanese

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 Japanese
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 Japanese

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 Japanese
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 Japanese

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 Japanese

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: DUN Packet-Switched Data 通信中かつSameDeviceとのA2DP Idle状態で着信しても、DUN,
A2DPには影響を与えず、DUN/A2DP両ProfileのStateに変化はない。
また通話とデータ通信が同時使用できない網の場合、着信中または通話中はデータ通信はSuspendされるが、DUNのConnectionは維持される。
従って、HFP動作はHFP 1.5 Specの4.13 Answer an Incoming Callが参照される。

4.2.4 HFP+A2DP/VDP+AVRCP+DUN; INCOMING CALL WITHOUT HQ RING TONEUNDER PACKET-SWITCHED DATA MODE AND LISTENING TO MUSIC FROM A SAMEDEVICE
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: DUN Packet-Switched Data 通信中かつSameDeviceとのA2DP Streaming中に着信しても、DUNには影響を与えず、DUNのStateに変化はなく動作は継続される。
また通話とデータ通信が同時使用できない網の場合、着信中または通話中はデータ通信はSuspendされる が 、 DUN の Connection は 維 持 さ れ る 。 従 っ て HFP の 着 信 に よ り 影 響 を 受 け る の は A2DP であり、Steamingを中断、再開する手順はWhite Paperが参照される。

28

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

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

AG機器操作による発呼で(e)SCOが接続されるかどうかは、AG機器の実装に依存する。例えば、AG
機器の動作設定がハンドセットでの通話に設定されている場合、(e)SCOは接続されない。

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 Japanese

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 Japanese

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+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.5.5. HFP+A2DP/VDP+AVRCP+DUN；OUTGOING CALL UNDER PACKET-SWITCHED DATA
MODE.(User initiates a voice call on AG_MP_GW)

Note: 本ガイドラインはパケットデータ通信中の発呼が可能な携帯網での実装をもとに作成したものである。網側の仕様によりパケットデータ通信中の発呼が不可能で、ATDに対してErrorが返ってくる場合のHF
デバイス側での処理は実装依存である。

31

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

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 or selects “Outgoing call” on HF_RD_DT while DUN Data communication is
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

AG機器操作による発呼で(e)SCOが接続されるかどうかは、AG機器の実装に依存する。例えば、AG
機器の動作設定がハンドセットでの通話に設定されている場合、(e)SCOは接続されない。

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 Japanese
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 Japanese

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.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE DATA COMMUNICATIONUNDER 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 Japanese

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.1: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO
MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA 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
IDLE or OPEN
AVDTP State during call
(Suspended)
DUN connection established with
DUN （ CIRCUIT-SWITCHED DATA MODE ）State
HFP service level connection established with
HFP SCO connection established with duringcall

HF_RD_DT
AG_MP_GW
AG_MP_GW
IDLE or OPEN
(Suspended)

HF_RD_DT
N/A(Terminated)

AG_MP_GW
N/A(Terminated)

HF_RD_DT[HF_RD_DT] *1

AG_MP_GW[AG_MP_GW] *1

Table 4.2.7.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE DURING
CALL*1 AG機器操作による発呼で(e)SCOが接続されるかどうかは、AG機器の実装に依存する。例えば、AG
機器の動作設定がハンドセットでの通話に設定されている場合、(e)SCOは接続されない。

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.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE AFTER CALL

35

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

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 Japanese
4.2.7.5 Message Sequence Charts

HF_RD_DT

AG_MP_GW

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

Terminate a voice call

Subscenario : restore streaming

Figure 4.2.7.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.（HF_RD_DT initiated）

37

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

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.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE.（AG_MP_GW initiated）
Note: 本ガイドラインはパケットデータ通信中の発呼が可能な携帯網での実装をもとに作成したものである。網側の仕様によりパケットデータ通信中の発呼が不可能で、ATDに対してErrorが返ってくる場合のHF
デバイス側での処理は実装依存である。

38

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

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: ストリーミング元がThird DeviceでもSame DeviceでもDUN通信中はストリーミングが継続される
ため、DUNで使用するシーケンスは同一になる。

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: ストリーミング元がThird DeviceでもSame DeviceでもDUN通信中はストリーミングが継続される
ため、DUNで使用するシーケンスは、同一になる。

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: DUN Packet-Switched Data 通信中かつThird DeviceとのA2DP Idle状態で着信しても、DUN,
A2DPには影響を与えず、DUN/A2DP両ProfileのStateに変化はない。
また通話とデータ通信が同時使用できない網の場合、着信中または通話中はデータ通信はSuspendされるが、DUNのConnectionは維持される。
従って、HFP動作はHFP 1.5 [1] Specの4.13 Answer an Incoming Callが参照される。

39

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

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: DUN Packet-Switched Data 通信中かつThird DeviceとのA2DP Streaming中に着信しても、DUNには影響を与えず、DUNのStateに変化はなく動作は継続される。
また通話とデータ通信が同時使用できない網の場合、着信中または通話中はデータ通信はSuspendされるが、DUNのConnectionは維持される。従ってHFPの着信により影響を受けるのはA2DPであり、Steamingを中断、再開する手順はWhite Paper[9]が参照される。

4.3.5 HFP-A2DP/VDP-AVRCP+DUN; OUTGOING CALL UNDER PACKET-SWITCHEDDATA 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.640

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

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） State
communication
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.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.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 AG機器操作による発呼で(e)SCOが接続されるかどうかは、AG機器の実装に依存する。例えば、AG
機器の動作設定がハンドセットでの通話に設定されている場合、(e)SCOは接続されない。

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.3: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO
MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE AFTER CALL.

41

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 Japanese
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].

42©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 Japanese
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.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）

43

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

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
AVRCP Pause
AVRCP Pause Responce
request for (e)SCO

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.

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.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC DATACOMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE IN CASE OF THE THIRD DEVICE.
（AG_GW initiated）

44

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 Japanese
Note: 本ガイドラインはパケットデータ通信中の発呼が可能な携帯網での実装をもとに作成したものである。網側の仕様によりパケットデータ通信中の発呼が不可能で、ATDに対してErrorが返ってくる場合のHF
デバイス側での処理は実装依存である。

45

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

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
CSDM

*1

IDLE

Same as4.2.1
Same as
4.2.2

4.1.1

DUN
4.1.2
*2
Streaming*5(covered by
WP)

Third Device Scenario

Incoming
HFP
Outgoing

Same as4.3.1
Same as
4.3.2

PSDM
DUN
CSDM
IDLE
A2DP

*1

*2

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

*1

IDLE
A2DP

Event

Same Device Scenario

Incoming
HFP

CSDM
DATA

Same
deviceScenario
ThirddeviceScenario

HFP=Ongoing

A2DP=
Streaming

A2DP=
IDLE

PSDM

4.2.1

Same as 4.2.1

CSDM

4.2.2

Same as 4.2.2

A2DP=
Streaming

A2DP=
IDLE
Same as 4.1.1
Same as 4.1.2

*2
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

46*1

©Copyright 2008-2009 Mobile Computing Promotion Consortium (MCPC)
MCPC-TR008 Bluetooth Multi-Connection Technical Reference Version 1.2 Japanese(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 DATASame
deviceScenario
ThirddeviceScenario

A2DP=Streaming
DUN=
CSDM

DUN=
DATA

DUN=PSDM
DUN=
no DATA

DUN=
DATA

DUN=
CSDM

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

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 care because there isn't technical affection. Since the Pre-condition does notaffect 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.

47

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

6. Appendix B （実装上の注意事項）
この章はBluetooth無線通信の相互接続性を確保する上で、実装上注意すべき点をまとめたものである。

B-1 AVRCP パススルーコマンドに関する注意
AVRCPにおいては、PASS THROUGHのプレスコマンドが送られた後もボタンが押し続けられているならば、更なる
プレスコマンドを前のプレスコマンドの2秒以内に送らなければならない。これはボタンが離されるまで繰り返される必要がある。これはAVRCP Specification[5]が参照するAV/C Panel Subunit Specification[8]に従うものである。

48

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

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.

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

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 …).

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

9. LIST OF FIGURES
Figure 2.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.5. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE. （ HF_RD_DT
initiated）
Figure 4.3.7.56. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC ANDDATA 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.56. HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO MUSIC DATACOMMUNICATION 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 streaming

51

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

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.5: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENING TO
MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
Table 4.3.7.5: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
DURING CALL
Table 4.3.7.5: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
AFTER CALL
Table 4.3.7.51: Pre-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE
(IN CASE OF THE THIRD DEVICE
Table 4.3.7.5: Post-Conditions: HFP+A2DP/VDP+AVRCP+DUN; OUTGOING CALL WHILE LISTENINGTO MUSIC AND DATA COMMUNICATION UNDER CIRCUIT-SWITCHED DATA MODE

52

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

53

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

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

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

MCPC TR-008 ver.1.2 JapaneseBluetooth Multi-Connection Technical Reference

平成21 年 12月 24 日
発行元：モバイルコンピューティング推進コンソーシアム（ＭＣＰＣ）〒105-0011 東京都港区芝公園３－５－１２ 長谷川グリーンビル

本書の一部または全部を無断で複写（コピー）することは著作権及び出版者の権利侵害となります。
本書からの転載は原則禁止です。他の書籍等に転載する場合はモバイル
コンピューティング推進コンソーシアム（ＭＣＰＣ）の許可を必ず得てください。

55