©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)MCPC-TR-010

Bluetooth
Phonebook Access Profile
Implementation Guideline
Version 1.10(E)Nov/28/2013

Mobile Computing Promotion Consortium
Technical Committee1©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Change History
Date
Jan/07/2008
Nov/28/2013

Version
1.00
1.10

Descriptions
Base version initial release.
Updated “Furigana” usage to be corresponded with TR-015.

Published and copyrights owned by:
Mobile Computing Promotion Consortium (MCPC)
Hasegawa Green Building,
5-12 Shiba-Koen 3-chome, Minato-ku, Tokyo, 105-0011 Japan
TEL: +81-3-5401-1935
FAX: +81-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 for any
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.

How we distinguish binary, decimal and hexadecimal numbers：• For binary numbers, we append a small letter “b” (e.g. 10b))• For binary numbers, we insert a space after every four bits. (e.g.：1000 0101 0010b)• For hexadecimal numbers, we append a small letter “h” (e.g.：FFFFh and 80h)
• All other numbers shall be considered to be written in decimal

Key Words• “May” means that something is recommended or optional at the free discretion of the vendor.
• “Should” means that although something is not essential, it is strongly recommended. When
implementing, the vendor shall take this requirement into consideration and determine whether this isessential or not.
• “Shall” means that something is an essential requirement. For connectivity and specification
compliance, the feature must be implemented, and is mandatory.

Trademark Notes
2©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)• Company names, product names, service names and the like described in this document are generally
trademarked or are registered trademarks of their respective owners.
• In general, the usage of ™ marks, © marks, and ® marks has been omitted in this document.
• In general “ Inc.,” “Corporation,” “Co., Ltd.,” have been excluded from company names.

3©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Contributors
Nobuki Asai
Masanobu Ujiie
Shigeru Ota
Seiichi Suzuki
Masashi Miura
Shuji Terakado
Toshiya Tamura
Takashi Yamazaki
Shigetoshi Hara
Hiroyuki Morimoto
Riko Yagiu
Tomoyuki Suzuki
Toshiyuki Suzuki
Sadamitsu Kanamori
Masatoshi Hino
Shio Kubo
Satoshi Miyazaki
Hiroyuki Hayashi
Yasuho Egawa
Masahiko Seki
Yoshihisa Takahashi
Mitsuyoshi Yasuda
Hiroshi Kato
Hiroshi Matsuya

ALPINE ELECTRONICS, INC.
ALPS ELECTRIC CO., LTD.
Clarion Co., Ltd.
Clarion Co., Ltd.
DENSO CORPORATIONELECOM CO., LTD.
Fujitsu CORPORATION
Harman International
Johnson Controls
Mitsubishi Electric Corporation
Mitsubishi Electric Corporation
NISSAN MOTOR CO., LTD. for JAMANTT DoCoMo, Inc.
Renesas Solutions Corporation
Sharp Corporation
SOFTBANK MOBILE Corp.
SOFTBANK MOBILE Corp.
SOFTBANK MOBILE Corp.
Sony Corporation
Sony Corporation
Sony Corporation
Sony Mobile Communications Japan, Inc.
TAIYO YUDEN CO., LTD.
TOSHIBA CORPORATION

4©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Bluetooth
Phonebook Access Profile
Implementation Guideline

Version 1.10
28th Nov 20135©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Contents
1 Phonebook Access Profile Use Cases Description ................................. 8
1.1

Summary of the use cases .................................................................................. 8

1.1.1
1.1.2
1.1.3
1.1.4

1.2

Introduction .................................................................................................................... 8
Target system .................................................................................................................. 8
Example of the system .................................................................................................... 9
Table of the Use Cases .................................................................................................... 9Standalone use cases ....................................................................................... 10

1.2.1
Phonebook download..................................................................................................... 10
1.2.1.1
Download of the main phonebook .......................................................................... 10
1.2.1.2
Download of call history information .................................................................... 11
1.2.1.3
Usage of “cch” repository ....................................................................................... 12
1.2.2
Phonebook browsing ..................................................................................................... 13
1.2.2.1
Retrieve selected entries ........................................................................................ 13
1.2.2.2
Caller name lookup upon incoming call ................................................................ 15
1.2.2.3
Dial ......................................................................................................................... 16

1.3

Multi-profile use cases ..................................................................................... 17

1.3.1
1.3.2
1.3.3

Caller name lookup upon incoming call ....................................................................... 17
Consultation of the Phonebook during a conversation ................................................. 17
Consultation of the Phonebook during a DUN session ................................................ 19

2 General Implementation Issues .......................................................... 20
2.1
2.2

Link establishment .......................................................................................... 20
vCard format .................................................................................................... 20

2.2.1
2.2.2
2.2.3

2.3
2.4
2.5
2.6

Properties ...................................................................................................................... 20
Owner’s vCard............................................................................................................... 23
Call history.................................................................................................................... 23

Handles ............................................................................................................ 24
Folder Structure .............................................................................................. 25
Attributes filtering ........................................................................................... 26
Example of the usage for MaxListCount and ListStartOffset ......................... 26

3 Phonebook Download Implementation Issues .....................................28
3.1
3.2

Download of the main phonebook .................................................................... 28
Download of call history information ............................................................... 29

4 Phonebook Browsing Implementation Issues ......................................30
4.1

Generic issues .................................................................................................. 30

4.1.1
4.1.2

SetPhoneBook Function................................................................................................ 30
Search Function ............................................................................................................ 30

6©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)
4.1.3

4.2

Retrieve selected entries .................................................................................. 31

4.2.1
4.2.2

4.3

Retrieve selected entries w/o search parameter ........................................................... 31
Retrieve selected entries with search parameter ......................................................... 33

Caller name lookup upon incoming call ........................................................... 35

4.3.1
4.3.2

4.4

Sorting Function ........................................................................................................... 30

Caller name lookup upon incoming call (“telecom/pb”) ................................................ 35
Caller name lookup upon incoming call (“SIM1/telecom/pb”) ...................................... 37

Dial .................................................................................................................. 39

4.4.1
Dialing from retrieved phonebook entry ...................................................................... 39
4.4.2
Dialing from incoming call history (PSEs entries are modified during an active PBAP
session) 42

7

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)

1 Phonebook Access Profile Use Cases Description
1.1 Summary of the use cases
1.1.1 Introduction
The Car-Communication-Application-Promotion group (CCAP) is concerned that
Car-WG profiles may not provide sufficient definition to assure interoperability ofBluetooth devices supporting these profiles. CCAP believes that this application
guide for the Bluetooth PhoneBook Access applications will improve interoperability
between handheld devices and the car, and help implementers understand thePhonebook Access Profile for user convenience. This guideline provides:- Recommended values of parameters- Recommended sequence charts- Typical use cases- Implementation issues
The intent is that this guideline be applied to the application layer above thePhonebook Access Profile (PBAP). CCAP may also provide additional guidelines in
the future such as the Message Access Profile (MAP) etc. and future versions of these
profiles.
1.1.2 Target system
The figure below shows a system diagram that this guideline specifies. PBAP and
HFP (HandsFree Profile) may be operated together in some use cases. In this casethe minimum functionality of the PhoneBook Client Equipment (PCE) or Handsfree
Unit (HF) is a speaker, microphone, control switch and display. The Sound Generator
is optional.
There might be a case of only PCE operation, without HF role such as PC. It shouldbe also covered in this guideline.
Display (std.)

Name: Ichiro Suzuki
No.090-xxxx-xxxx

Car kitBluetoothSpeaker(std.)

Sound
Generator(opt.)

Microphone(std.)
Control Switch(std.)

Switch[PCE/HF]

8

Phone[PSE/AG]©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.1.3 Example of the system
Microphone
Display
Name: Ichiro
No.090-xxxx-

SwitchSpeakerPhone [PSE/AG]

1.1.4 Table of the Use Cases

Category
1.2 Standalone use cases
1.2.1 Phonebook download

1.2.2 Phonebook browsing

Use Case

Description

PBAP
Sect.

1.2.1.1 Download of the main phonebook

Download the entire content of the main phone book object in "pb"4.2

1.2.1.2 Download of call history information

Download the entire content of the call history object in "ich", "och", and "mch"4.2

1.2.1.3 Usage of “cch” repository

Download the entire content of the call history object in "cc"4.2

1.2.2.1 Download of selected entries
1.2.2.2 Caller name lookup upon incoming call
1.2.2.3 Dial

Browse the content of each folder, select and download entry/entries
Search the caller name from "pb" with CLI of an incoming call via HFPBrowse the content of each folder and dial a number via HFP

4.3
4.3
4.3

1.3.1 Caller name lookup upon incoming call
1.3.2 Consultation of the Phonebook during a
conversation
1.3.3 Consultation of the Phonebook during a DUN
sessionSearch the caller name from "pb" with CLI of an incoming call via HFP

4.3

Browse the content of each folder during a conversation via HFP

4.3

Browse the content of each folder during data transfer via DUN

4.3

1.3 Multi-profile use cases

9©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2 Standalone use cases
1.2.1 Phonebook download
1.2.1.1 Download of the main phonebook
The PCE can download the PSE's main phone book object.
- Main phone book object: pb
Figure 1 shows the example of the use case.
(PCE,HF)
Car navigation system, Hands-Free
device with display equipment, etc.

(PSE,AG)
Mobile Phone

The PCE download the PSE's
main phone book object.

-- Name: pb.vcf-- Application parameters:<MaxListCount>: A value between “0” and “65535”.
“0” means PSE shall return only the number of entries registered in the phonebook or callhistories, without the body of entries. If PCE specifies the "MaxListCount" parameter to“65535”, PSE can then return all entries even if there are more than “65535”.
(5.1.4.3 MaxListCpunt)<ListStartOffset>: This header shall be used to indicate the offset of the first entry of the object.
(The offset shall be ０ if this header is not specified.)(5.1.4.4 ListStartOffset)

vCard
NAME: Abe
TEL: 090-XXXX-XXXX
EMAIL: abe@a.com
ADD:XXX,XXX-456
BDAY:2006/01/01

Main phone book of vCard
form.

Figure 1: Download of the main phonebook<Owner card>
The special handle 0.vcf in the pb folder is reserved for the owner card. It shall always be present
and contain at least the mobile number of the PSE, whenever the PSE has the knowledge of thisnumber. When the owner card is not known, handle 0.vcf can be an empty vCard, or a vCard that
contains the mobile number of the PSE, if the PSE has a mobile number and does know it. The 0.vcf
shall always be present in the pb.vcf file.

10©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2.1.2 Download of call history information
The PCE can download the PSE's history information object.
- Incoming Calls History object: ich- Outgoing Calls History object: och- Missed Calls History object: mch- Combined Calls History object: cch
Figure 2 shows the example of the use case.
(PCE,HF)
Car navigation system, Hands-Free
device with display equipment, etc.

(PSE,AG)
Mobile Phone

The PCE download the PSE's
main phone book object.

-- Name: ich.vcf or och.vcf or mch.vcf or cch.vcf- Application parameters:<MaxListCount>: A value between “0” and “65535”.
“0” means PSE shall return only the number of entries registered in the phonebook or callhistories, without the body of entries. If PCE specifies the "MaxListCount" parameter to“65535”, PSE can then return all entries even if there are more than “65535”.
(5.1.4.3 MaxListCount)<ListStartOffset>: This header shall be used to indicate the offset of the first entry of the object.
(The offset shall be ０ if this header is not specified.)(5.1.4.4 ListStartOffset)･ When there is NAME
vCard
NAME: Abe
TEL: 090-XXXX-XXXX
DATE: 2006/01/01
TIME: HHMM/Dialed

history information of vCard
form.

･ When there is no NAME
vCard
NAME:
TEL: 090-XXXX-XXXX
Figure 2: Download of call history information
DATE: 2006/01/01
TIME:HHMM/Missed11©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2.1.3 Usage of “cch” repository
The integrated list of incoming call history, outgoing call history, andmissed call history is stored in the combined call history (cch) repository. It
depends on the implementation of PSE, how it integrates and how it indexes
the entries. For example, PCE can display the entries in “cch” as thefollowing order.
- By time stamp, call history is able to be arranged in call sequence.
- To be arranged with the frequency of call.

12©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2.2 Phonebook browsing
1.2.2.1 Retrieve selected entries
The PCE can retrieve the PSE's Phonebook-listing object and retrieve
selected entries.
Figure 1 shows the example of the use case.
(PCE,HF)
Car navigation system, Hands-Free
device with display equipment, etc.

(PSE,AG)
Mobile Phone

The PCE retrieves the PSE's
Phonebook-listing object.

・ (Alphabetical/Indexed/Phonetical) can be specified for an orderof the Phonebook-listing object.
・ The text string to search for the record that matched to thevalue of the (Name/Number/Sound) attribute can be specified.
・ According to the ability of PCE ,the List-Start-Offset and
Max-List-Count can be additionally specified.
Phonebook(PSE)・Abe・Barfield
・Chiba・Delacruz
・Egawa>Next

Phonebook-listing object

The following
Phonebook-listing object can beacquired specifying
List-Start-Offset.

All lists are acquired repeatingprocessing.

Phonebook(PSE)
・Fujita
・Galvez・Hara・Ishii・JohbePrev<

Phonebook-listing object

13

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)(PCE,HF)

PCE can selectone or more
Phonebookentries andretrieveselected
entries.

Phonebook(PSE)
・Fujita
・Galvez・Hara・Ishii・JohbePrev<

AttributeMask can be specified
for filtered vCard.
vCard
NAME: Galvez
TEL:090-XXXX-XXXX
EMAIL:Chiba@def.com
ADD:XXX,XXX-123
BDAY:2006/11/11

vCard
NAME: Ishii
TEL:090-XXXX-XXXX
EMAIL:Tokyo@t.com
ADD:XXX,XXX-789
BDAY:2006/12/12(PSE,AG)The PCE retrieves selected
Phonebook entry from thePSE.

Phonebook entry of vCard
form.

The PCE retrieves selected
Phonebook entry from thePSE.
Phonebook entry of vCard
form.

Retrieving selected entries is done.

Figure 1: Retrieve Selected entries

14

Two or more
Phonebookentries can beacquired byrepeatingprocessing.

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2.2.2 Caller name lookup upon incoming call
The PCE searches the phonebook entry from the PSE, and can retrieve it.
Figure 2 shows the example of the use case.

(PCE,HF)
Car navigation system, Hands-Free
device with display equipment, etc.

Incoming call

Caller ID notification.(HFP)(PSE,AG)
Mobile Phone

090-XXXX-XXXX
The PCE retrieves thephonebook of the PSE by
Caller ID.(PBAP)
Phonebook-listing object<card handle = “nn.vcf”
name = “XXXX”>

The PCE displays
caller name “XXXX”.

Figure 2: Caller name lookup upon incoming call15

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.2.2.3 Dial
The PCE can dial it from the telephone book with HFP.
The PCE can store Phonebook entries in PCE's Phonebook.
Figure 3 shows the example of the use case.
(PSE,AG)
Mobile Phone(PCE,HF)Car navigation system, Hands-Free
device with display equipment, etc.

The PCE retrieves the
Phonebook entries of the PSE.
(see 1.2.2.1)

Store
vCard
NAME: Galvez
TEL:090-XXXX-XXXX
EMAIL:Chiba@def.com
ADD:XXX,XXX-123
BDAY:2006/11/11
The PCE can execute thefollowing functions for the
retrieved Phone book entries.
・ The PCE can store
Phonebook entries in PCE's
Phonebook.
・ The PCE can dial number of
the Phonebook entry.

Phonebook entry of vCard form.

Dial 090-XXXX-XXXX.(HFP)
Outgoing callvoice communication

Figure 3: Dial

16©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.3 Multi-profile use cases
1.3.1 Caller name lookup upon incoming call
Refer to 1.2.2.2.
1.3.2 Consultation of the Phonebook during a conversation
The PCE can consult the Phonebook during a conversation with HFP if the PSE
supports the multi-profile.
Figure 4 shows the example of the use case.
(PSE,AG)
Mobile Phone(PCE,HF)Car navigation system, Hands-Free
device with display equipment, etc.

HFP session

The user wants to refer the
PSE’s phonebooks while calling.

voice communication

The PCE retrieves the PSE’s
Phonebook listing object.
Phonebook(PSE)・Abe・Barfield
・Chiba・Delacruz
・Egawa>Next

Phonebook-listing object.
The following Phonebook-listing
object can be acquired specifying
List-Start-Offset
All lists are acquired repeatingprocessing.

Phonebook(PSE)
・Fujita
・Galvez・Hara・Ishii・JohbePrev<

Phonebook-listing object

17

Incoming call©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)(PCE,HF)

PCE can selectone or more
Phonebookentries andretrieveselected
entries.

Phonebook(PSE)
・Fujita
・Galvez・Hara・Ishii・JohbePrev<

AttributeMask can be specified
for filtered vCard.
vCard
NAME: Galvez
TEL:090-XXXX-XXXX
EMAIL:Chiba@def.com
ADD:XXX,XXX-123
BDAY:2006/11/11(PSE,AG)The PCE retrieves selected
Phonebook entry from thePSE.

Phonebook entry of vCard
form.

The PCE retrieves selected
Phonebook entry from thePSE.
Phonebook entry of vCard
form.

vCard
NAME: Ishii
TEL:090-XXXX-XXXX
EMAIL:Tokyo@t.com
ADD:XXX,XXX-789
BDAY:2006/12/12

Retrieving
selected
entriesis done.
Figure 4: Consultation of
the Phonebook
duringa conversation18

Two or more
Phonebookentries can beacquired byrepeatingprocessing.

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)1.3.3 Consultation of the Phonebook during a DUN session
The PCE can retrieve the PSE's Phonebook-listing object and retrieve selected
entries during a DUN session.
Figure 5 shows the example of the use case.
(PCE,HF,DT)
Car navigation system, Hands-Free
device with display equipment, etc.

(PSE,AG,GW)
Mobile Phone

HFP session
The DT retrieves the data of
the weather forecast.

The user wants to acquire
the data of the weather
forecast of the destination.

The GW communicateswith the server.

DUN session(Establish DUN session when
DUN session has not been
established)
The data of the weather
forecast
A DUN session is continuously
and periodically connected.

Weather forecast
Japan
Tokyo
20℃
Osaka
22℃
Fukuoka 23℃
Okinawa 28℃

Incoming call
The DT displays theinformation of the weather
forecast.

Caller ID notification.(HFP)
090-XXXX-XXXX
The PCE retrieves thephonebook of the PSE by
Caller ID.(PBAP)

Phonebook-listing object
The
PCE displays
Figure5: Consultation of the Phonebook during a DUN session<card handle = “nn.vcf”
caller name “XXXX”.
name = “XXXX”>

19©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)2 General Implementation Issues
2.1 Link establishment
The PSE and the PCE shall create a sure connection specified in section 2.5 “Bluetooth
Security” of PBAP. This Procedure may include entering a Passkey and will include
creation of link leys. A fixed Passkey may also be used during the GAP authentication
procedure. The PBAP mandates the use of several Bluetooth security features:(2.5 Bluetooth Security)
Security features
Security mode
Encryption
Passkey
Link keys
Encryption key length
User confirmation

Recommendation
2 or 3 shall be used.
Mandatory
A zero-length passkey shall be prohibited.
Combination keys shall be used.
At least 64 bits. Maximum length is recommended.
The PSE user shall have to confirm at least the first PBAP
connection from each new PCE.

Either the PSE or the PCE may initiate bonding. As a minimum the PSE shall support
Inquiry in order to initiate bonding. Both the PSE and the PCE shall support Inquiry
Scan Mode in order to accept bonding. (2.4 Profile fundamental)
The SDP record for the PCE can be ignored for current Bluetooth V2.0, however, it will
be effective if QoS is applied in the future. The PSE will be able to prepare for connecting
PBAP from the PCE in anytime.

2.2 vCard format
The format of the phonebook should be followed ver.2.1 of vCard. However, especiallyconsidering in Japanese situation, the PCE has to handle some of the ver.3.0 of vCard
because the property of “Sort-String” is used for information of “Furigana” in vCard 3.0.
The following requirements or attentions should be considered for implementation.

2.2.1 Properties
Properties of vCard for a standard cellular phone, which shall be careful to be
implemented, are listed below. Multiple phone numbers for a name entry of vCard
can be stated. However, this guideline does not specify the number of phone
numbers.
The PSE shall support VERSION, TEL and N as mandatory. In case of vCard 3.0,
FN shall be also mandatory. SOUND for ver. 2.1 or Sort-String for ver. 3.0 is
recommended to be Mandatory in Japanese implementation. (*1)

20©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Bit

Property

Name

SupportNote

0

VERSION

VersionM

vCard 2.1 or vCard 3.0

1

FN

Formatted nameM

Mandatory for vCard 3.0

2

N

Name

M

3

PHOTO

Associated Image or Photo

O

4

BDAY

Birthday

O

5

ADR

Address

O

6

LABEL

Delivery

O

7

TEL

Phone number

M

Allow multiple entries

8

EMAIL

Electronic Mail address

O

Allow multiple entries

9

MailerElectronic Mail

O

Type of email software

10

TZ

Time ZoneO

Offset from UTC

11

GEO

Geographic PositionO

Longitude and latitude

12

TITLE

Job

O

Job title

13

Role

Role within the Organization

O

14

LOGO

Organization LogoO

Image or graphic

15

AGENT

vCard of Person Representing

16
17
18

ORG
NOTE

Name of Organization
Comments

O
O

Company name

REV

Revision

O

Sound
URL
UID
KEY
NICKNAME
CATEGORIES
PROID
CLASS
Sort-String
X-IRMC-CALL-DATETIME

Pronunciation of name
Uniform Resource Locator
Unique ID
Public Encryption Key
Nickname
Categories
Product ID
Class Information
String used for sorting operations
Time stamp
Reserved for future use
Indicates the usage of a proprietary
filterReserved for proprietary filter usage

M
O
O
O
O
O
O
O
*1
M
O

19
20
21
22
23
24
25
26
27
28
29-38
39
40-63

Proprietary Filter*1O(5.4.4.1 Filter {AttributedMask(64-bit value)} Table 5.2 Attributed Mask)

21

Date and time of the last
Update to the vCard
Furigana (for vCard 2.1)

Furigana (for vCard 3.0)

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)(1) Character code settings: CHARSET, ENCODING- CHARSET: UTF-8- ENCODING: Quoted-Printable
PBAP mandates UTF-8 as default and does not allow other character sets to be used.
However, some legacy devices have implemented to send Japanese characters with
Shift-JIS character sets. Therefore it recommends for the PCE to decode Shift-JIS
character sets to keep higher interoperability.
(2) Version information: VERSION- vCard 2.1 / vCard 3.0 (3.1.4 Phone Book Entries Format)(3) Formatted name: FN- This property specifies the formatted name string associated with the vCard object. Thisis the way that the name is to be displayed. It can contain desired honorific prefixes,
suffixes, titles, etc. For example, “Mr. John Q. Public, Jr.”, Dr. Ann Tyler, or Hon. Judge
Blackwell. This property is based on the semantics of the X.520 Common Nameattribute.
The following is an example of the Formatted Name property:
FN:Mr. John Q. Public, Esq.
(4) Name: N- When the delimiter between the first name and the last name is needed, ‘;’ shall be used.
The first Name shall be set in Field-2 and the last name in Field-1.
When the delimiter is not needed, the first name and the last name shall be set in
Field-1.
If the PSE uses no structure of name representation, the PSE should provide everything
as a LastName field of the N attribute. Other more advanced internal representations
should be able to map correctly the name information into a structured N vCard
attribute. (3.1.6.1 Name attribute format)(5) Address: ADR- Each field of ADR is shown below:
Field-1
Postal address (Not popular in Japan.)
Field-2
Extension address (Room No. of apartment, dormitory etc.)
Field-3
Street (House No., Block No. etc.)
Field-4
Minor district (Town, City etc.)
Field-5
Major district (State, Prefecture etc.)
Field-6
Postal code
Field-7
Country- If the address cannot be classified, it shall be described in Field-2.
(6) Telephone number: TEL- Multiple TEL shall be able to be included in a vCard.
- Type of TEL shall be supported at least 5, general, cellular, home, work and FAX.
- Multiple TEL shall be able to be set for a type of TEL.
- Example of type of TEL and the parameter:
General -> VOICE [default]
Cellular -> CELL
Home-> HOME;VOICEWork-> WORK;VOICE
FAX-> FAX
22

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)(7) E-mail address: EMAIL- Multiple EMAIL shall be able to be included in a vCard.
- Multiple EMAIL shall be able to be set for the same address type of e-mail.
- The parameter shall be supported at least INTERNET [default].
(8) Company name: ORG- Company name shall be set in Field-1.
- Section name shall be set in Field-2(9) Furigana: SOUND (for 2.1) or Sort-String (for 3.0)
- The extended parameter shall be used to indicate which property of “Furigana” is.
- Default parameter shall be X-IRMC-N.
Extended parametername of property adding X-IRMC-“Furigana”
Field etc.
Same field shall exist as described after X-IRMC-[Property].
CHARSET, ENCODING CHARSET: UTF-8, ENCODING: Quoted-Printable- Using the extended parameter X-IRMC-N, this shall be “Furigana” of N and have five
fields as same as N.
(10) Time stamp: X-IRMC-CALL-DATETIME- The time of each call found in och, ich, mch and cch folder, can be shown using the IrMC
defined X-IRMC-CALL-DATETIME property that extends the vCard specification. This
attribute can be used in combination with three newly created property parameters:
MISSEDRECEIVEDDIALED
These are used to indicate the nature of the call that is time-stamped with
X-IRMC-CALL-DATETIME.
For instance, a call that was missed on March 20th, 2005 at 10 am would be stamped:
X-IRMC-CALL-DATETIME;MISSED:20050320T100000
It is strongly recommended to use this property parameter whenever possible. They areespecially useful in vCards that are retrieved from the cch folder.
Note that it is legal to use this property with no data ie,
X-IRMC-CALL-DATETIME;MISSED:This scenario may occur if the device did not have the time/date set when the call wasreceived. The phone number would be recorded but no date/time could be attached to it.
It will still need to be added to the vCard as the cch log needs it to indicate the type ofcall that the record identifies. (3.1.4.1 Call History extension)
Time stamp should be used UTC or local time in combination with TZ, Time Zone so thatcall histories can be sorted in time order.
2.2.2 Owner’s vCard
The special handle 0.vcf in the pb folder shall be reserved for the owner's card. It
shall always be present. When the owner card is not known, index 0 can be an empty
vCard, or a vCard that contains the mobile number of the PSE, if the PSE has amobile number and does know it. The 0.vcf shall be present in the pb.vcf file.
(3.1.5.2 Local Phone Books: PB and SIM1)
2.2.3 Call history
For call history items, only the phone number used for the call shall be included in23©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)the TEL vCard field, rather than every number. (3.1.5.3 Call Histories)
The X-IRMC time stamp attribute shall be always present even if no time
information is available for a given history item, since it conveys the nature of themissed, outgoing and incoming call history.
Regarding the vCard format for call histories which does not have phone number
information because of an errata is proposed. This will be defined as X-IRMC
extensions, CLI_BARRED, CLI_UNAVAILABLE and CLI_PUBLICPHONE.

2.3 Handles
All the vCards of the PSE are identified by their handle (<handle.vcf>). The
handles are 32 bit values, represented as up to 8 hexadecimal digits. The length of
the handles can be variable.
PBAP has been developed on the assumption that the handles are not modified
during the lifespan of a given PBAP session i.e. that the internal index and theactual content of each vCard does not change. If for some reason the implementation
allows for handle modifications (including possibly deletion operations) during anactive PBAP session, it shall support either of the following 2 behaviours:
Error reporting: If any of the handles are modified/deleted during an active
PBAP session, then the PSE shall return Error "Precondition failed" to all readrequests until the PCE has updated the vCard-listing.
Change tracking: The PSE keeps track of all the changes that are brought tothe handles during the active PBAP session.
(3.1.5.1 Handles)

24©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)2.4 Folder Structureroot

telecom

pb

0.vcf
1.vcf
n.vcf

pb.vcf

ich

1.vcf
2.vcf
3.vcf
m.vcf

ich.vcfochtelecom

SIM1

pb.vcfichoch.vcf
1.vcf
2.vcf
3.vcf

1.vcf
2.vcf
3.vcf
m.vcf

ich.vcf

q.vcf

och

mch.vcf

cch

0.vcf
1.vcf
n.vcf

1.vcf
2.vcf
p.vcf

mch

pb

1.vcf
2.vcf
3.vcf

1.vcf
2.vcf
p.vcf

och.vcf

r.vcf

mch

cch.vcf

1.vcf
2.vcf
3.vcf
q.vcf

mch.vcf

cch

1.vcf
2.vcf
3.vcf
r.vcf

cch.vcf

Figure 6: PBAP virtual folders architecture(3.1.5 PBAP virtual folders structure)
OBEX SetPath Command (the basis for the SetPhoneBook function) allows only for
setting the current folder to the root, parent or a child folder. For example in order to
set the current phone book folder to "pb", from the root, it is necessary to apply
SetPath twice: the first is necessary to change into "telecom" and the second isnecessary to change into "pb". (5.2 SetPhoneBook Function)

25

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)

2.5 Attributes filteringWith the exception of the mandatory attributes, the attributes that are requestedby the PCE can be ignored by the PSE in case the PSE does not support them.
However, all the attributes that are supported by the PSE shall be returned,
provided that their value is not null for the current phone book entry. For instance, if
the PSE supports EMAIL, and TITLE (in addition to VERSION, N and TEL) and the
PCE requests the EMAIL and BDAY attributes, the PSE shall include EMAIL in thevCard objects that are returned to the PCE for which the value of EMAIL is not null(in addition to the mandatory VERSION, N and TEL fields).
The basic rules are:- Absence of "Filter" means that all the attributes shall be returned.
- Filter = 0x00000000 means that all the attributes shall be returned.
- It is mandatory for the PSE to support and be capable of returning N and TEL
in the case of vCard2.1, FN and TEL in the case of vCard3.0. Also SOUND or
Sort-String shall be supported in Japanese implementation.
- Besides N, FN and TEL, the PSE can ignore the attributes that it does notsupport.
- All the attributes that are supported by the PSE and are requested by the
PCE shall be returned to the PCE.
(5.1.4.1 Filter {AttributeMask (64-bit value)})

2.6 Example of the usage for MaxListCount and ListStartOffset<Case 1>
offset0123:n<Case 2>
offset0

vCard in “pb”
0.vcf

vCard in “pb”
7.vcf

1.vcf

1

2.vcf

2.vcf

2

5.vcf

3.vcf

3

0.vcf

…..

:

…..

n.vcf

m

xx.vcf

Case 1:- PullPhoneBook/PullvCardListing result with MaxListCount=0
The PSE shall return a value ‘n’, the number of vCard.
- PullPhoneBook/PullvCardListing result with MaxListCount=3, ListStartOffset=0
The PSE shall return 0.vcf, 1.vcf and 2.vcf.
- PullPhoneBook/PullvCardListing result with MaxListCount=3, ListStartOffset=1
The PSE shall return 1.vcf, 2.vcf and 3.vcf.
Case 2:- PullPhoneBook/PullvCardListing result with MaxListCount=0
The PSE shall return a value ‘m’, the number of vCard.
26

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)- PullPhoneBook/PullvCardListing result with MaxListCount=3, ListStartOffset=0
The PSE shall return 7.vcf, 2.vcf and 5.vcf.
- PullPhoneBook/PullvCardListing result with MaxListCount=3, ListStartOffset=1
The PSE shall return 2.vcf, 5.vcf and 0.vcf.

27

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)

3 Phonebook Download Implementation Issues
3.1 Download of the main phonebook

Download of phone book entries
Car Equipment (HF)
HMI
PCE

Cellular Phone (AG)PSE
HMI

Cellular Network

select devicelink establishment(GAP7.1)
pagingauthentication using
the link key
and link
establishment

connection
established

PBAP connection
establishment

if user selects call history, in case of
Incoming calls
Name header = "telecom/ich.vcf"
Outgoing calls
Name hearder = "telecom/och.vcf"
Missed calls
Name hearder = "telecom/mch.vcf"
Combined calls
Name hearder = "telecom/cch.vcf"

Get
Type = "x-bt/phonebook"
Name header = "telecom/pb.vcf"
success with phonebook entries
if user selects SIM
card.

repeat if user selectmultiple folders

Get
Type = "x-bt/phonebook"
Name header = "SIM1/telecom/pb.vcf"
success with phonebook entries

download complete
PBAP connection
releaseIf PCE specifies the “MaxListCount” parameter to 0, PSE shall return only the number ofentry registered in the phonebook or call history without the body of entries.
65535 is the maximum possible size for “MaxListCount”. However, if PCE specifies the“MaxListCount” parameter to 65535, PSE can then return all entries even if there are morethan 65535.

28

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)3.2 Download of call history information
PSE shall return only one telephone number related to “incoming call” or “outgoing call” in avCard.
When requesting for the call history, PSE returns a set of entries with each entry containing atelephone number from the call history list together with the name of the owner of this number
based on the phonebook. This is instead of sending the original phonebook entry which may
contain several other phone numbers.

CallHistory
1. 090-aaaa-bbbb

Get “Incoming Call History”
Response
linkedName:AAATELL1 090-aaaa-bbbb

Local PB
Name:AAATEL1 :090-aaaa-bbbb
TEL2: 080-cccc-dddd

When PCE requests for the "Missed Call” history, PSE shall return the entries together with
the number of recent missed call using the “NewMissedCalls” parameter.
You have 2 newmissed calls !!

Get “Missed Call”
MissedCall Entries and“NewMissedCall = 2”

In the event when PSE cannot confirm the exact number of recent missed calls but it is definitethat there is at least 1 missed call; it would set the variable “NewMissedCalls” to 65535.
The integrated list of incoming call history, outgoing call history, and missed call history is
stored in the combined call history (cch) repository. It depends on the implementation of PSE,
how it integrates and how it indexes the entries.

29©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)

4 Phonebook Browsing Implementation Issues
4.1 Generic issues
4.1.1 SetPhoneBook Function
Usages of the SetPhoneBook Function are allowed only three types: (1) Go back toroot, (2) Go down 1 level, and (3) Go up 1 level. The Name header doesn’t use
absolute path name for this function. The usage of the flags and Name header is asfollows: (5.2 SetPhoneBook Function)(1) Go back to root (2) Go down 1 level (3) Go up 1 level
0
0
1
1
1
1
0
0
0
name of the child
Name header
EMPTY
optional
folder
Flags bit 0
Flags bit 1
Flags bit 2-7

Example: Going to “SIM1/telecom/ich” from “SIM1/telecom/pb”
Case 1Case 2type

current folder

1

Go up 1 level"SIM1/telecom"2

Go down 1 level"SIM1/telecom/pb"

typecurrent folder

1

Go back to root"" (root)2

Go down 1 level"SIM1"

3

Go down 1 level"SIM1/telecom"

4

Go down 1 level"SIM1/telecom/pb"

In both cases, PCE can set the current folder, but in the Case1, PCE has to know apath name of the current folder without asking PSE. There is no command to
retrieve the path name from PSE.
4.1.2

Search Function
The header of “Search Attribute” shall be used to indicate to the PSE, which vCard
attribute the search operation shall be carried out on. If this header is not specified,
the search shall be performed on the “Name” attribute. (5.3.4.2 SearchAttribute)
This header of “Search Value” shall be used to indicate to the PSE, which vCards
shall be contained in the object. All the vCards shall be returned if this header is not
specified. The UTF-8 character set shall be used for <text_string> in this header.
(5.3.4.3 SearchValue)
4.1.3 Sorting Function
The sorting algorithm is implementation dependent. UTF-8 conversion should be
performed before the sorting.
The sorting algorithm should be based on UTF-8 representation of the Sound
attribute. Note that sorting on the Sound attribute makes sense only when theSound attribute values of the phonebook objects on the PSE are in textual form.
(5.3.4.1 Order)30

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.2 Retrieve selected entries
4.2.1 Retrieve selected entries w/o search parameter

Retrieve of selected phone book objects
Car Equipment
HMI

Cellular Phone
PCE

PSE

HMI

Cellular
Network

select device
Session Establishment(PBAP)
SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
listing folder
select phonebook
in the phone's
memoryif user selects
SIM card.

SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success

if PCE wants to know
the number of entries.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 0
Success withvcard-listing object(with PhonebookSize)
Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5
Success withvcard-listing object

listing phonebook

if user selects call history, for
Incoming calls : Name header = "ich"Outgoing calls : Name header = "och"Missed calls :Name header = "mch"Combined calls : Name header = "cch"Parameters of vcard-listing
Max List Count
number of entries PCE wants to retrieve
List Start Offset
offset of the first entry of the retrieved object
Ex) PCE wants to retrieve 5 entries every time.
1st ： MaxListCount = 5, ListStartOffset = 0
2nd ： MaxListCount = 5, ListStartOffest = 5

select next list31©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5

repeat to findtargeted phonebook.

Success withvcard-listing object
listing phonebook

select phonebook
SetPath (Go down 1 level)
Flags = 0x02
Name header = "pb"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success with vcard object
display phonebook
select next
phonebook
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success with vcard object
display phonebook
exit phonebook
browsing

Session Release(PBAP)

32

Set "List Start Offset"©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.2.2 Retrieve selected entries with search parameter

Retrieve of selected phone book objects
Car Equipment
HMI

Cellular Phone
PCE

PSE

HMI

select device

Session Establishment(PBAP)
SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
listing folder
select phonebook
in the phone's
memoryif user selects
SIM card.

SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success

input "search value"
and / orselect "search type"and ordering

if PCE wants to know
the number of entries.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 0
Order = 0x01
Search Value = "<value>"
Search Attribute = 0x00
Success withvcard-listing object(with PhonebookSize)
Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5
Order = 0x01
Search Value = "<value>"
Search Attribute = 0x00
Success withvcard-listing object

listing phonebook

33

if user selects call history, for
Incoming calls : Name header = "ich"Outgoing calls : Name header = "och"Missed calls : Name header = "mch"Combined calls : Name header = "cch"
Order is 0x00 : indexed
0x01 : alphabetical
0x02 : phonetical
Search Attribute is 0x00 : Name
0x01 : Number
0x02 : Sound
Search Value is text of word.

Cellular
Network©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)select other list

repeat to find targeted
phonebook.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5
Order = 0x01
Search Value = "<value>"
Search Attribute = 0x00
Success withvcard-listing object

listing phonebook

select phonebook
SetPath (Go down 1 level)
Flags = 0x02
Name header = "pb"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success with vcard object
display phonebook
select next
phonebook
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success with vcard object
display phonebook
exit phonebook
browsing

Session Release(PBAP)

34

Set "List Start Offset"©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.3 Caller name lookup upon incoming call
4.3.1 Caller name lookup upon incoming call (“telecom/pb”)
PCE retrieves caller name from incoming call number, so AG (PSE) has to send HF(PCE) caller number.
At the following MSC, PBAP session is established after the +CLIP message. If
PBAP session is established before incoming call, the displayed caller name may beincorrect. The phonebook entry may be modified at the incoming call.

Caller name lookup upon incoming call
HMI

Car Equipment
PCE

HF

AG

Cellular Phone
PSE

HMI

Service Level Connection(HFP)

AG needs to send thecaller number.

AT+CLIP = 1
OK

incoming call
+CIEV : (callsetup = 1)

alert theincoming call

RING ALERT+CLIP : nnn

Session Establishment(PBAP)

SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success

It is assumed that thehandles are not modified
during this period.

SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success
Get
Type = "x-bt/vcard-listing"Name = "pb"
MaxListCount = 1
Search Value = nnn
Search Attribute = 0x01

35"nnn" is the caller numberof +CLIP message.

Cellular
Network©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Success withvcard-listing object

SetPath (Go down 1 level)
Flags = 0x02
Name header = "pb"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"

Success with vcard object
displayphonebook

After the caller namedisplayed, PBAP session
should be released
Session Release(PBAP)

acceptATA
OK
if audioconnection
is notpresent

audio
connection
establishedaudio connection
setup(HFP 4.11)

audio
connection
establishedstart the call establishment procedureand the call established+CIEV : (call = 1)
+CIEV : (callsetup = 0)
call active

voice communication

36

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.3.2 Caller name lookup upon incoming call (“SIM1/telecom/pb”)
In this chart, PSE can’t find the caller name in the folder “telecom/pb”. PSE tries tolook up another folder “SIM1/telecom/pb”, and find the caller name in this folder.
At the following MSC, PBAP session is established after the +CLIP message. If PBAP session isestablished before incoming call, the displayed caller name may be incorrect. The phonebook entry
may be modified at the incoming call.

Caller name lookup upon incoming call
HMI

Car Equipment
PCE

HF

AG

Cellular Phone
PSE

HMI

Cellula
Network

Service Level Connection(HFP)

AG needs to send thecaller number.

AT+CLIP = 1
OK

incoming call
+CIEV : (callsetup = 1)

alert theincoming call

RING ALERT+CLIP : nnn

Session Establishment(PBAP)
SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"

It is assumed that the handles are
not modified during this period.

Success
Get
Type = "x-bt/vcard-listing"Name = "pb"
MaxListCount = 1
Search Value = nnn
Search Attribute = 0x01
Not Foundchange folder to"SIM1/telecom"

SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY

37"nnn" is the caller numberof +CLIP message

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name heaer = "telecom"
Success
Get
Type = "x-bt/vcard-listing"Name = "pb"
MaxListCount = 1
Search Value = nnn
Search Attribute = 0x01

"nnn" is the caller numberof +CLIP message

Success withvcard-listing object
SetPath (Go down 1 level)
Flags = 0x02
Name header = "pb"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"

displayphonebo

Success withvcard object
After the caller namedisplayed, PBAP session
should be released
Session Release(PBAP)

acceptATA
OK

if audioconnection
is notpresent

audio
connection
establishedaudio connection
setup(HFP 4.11)

audio
onnection
establishedstart the call establishment procedureand the call established+CIEV : (call = 1)
+CIEV : (callsetup = 0)
call active

voice communication

38

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.4 Dial
4.4.1 Dialing from retrieved phonebook entry

Dialing
Car Equipment
PCE

HMI

HF

AG

Cellular Phone
PSE

HMI

Cellular
Network

Service Level Connection(HFP)
select device

Session Establishment(PBAP)
SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
listing folder
select phonebook
in the phone's
memoryif user selects
SIM card.

SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success

if PCE wants to know
the number of entries.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 0
Success withvcard-listing object(with PhonebookSize)
Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5
Success withvcard-listing object

listing
phonebook39

if user selects call history, for
Incoming calls : Name header = "ich"Outgoing calls : Name header = "och"Missed calls :Name header = "mch"Combined calls : Name header = "cch"©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)select other list

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 5

repeat to findtargeted
phonebook.

Success withvcard-listing object

listing
phonebookselectphonebook

SetPath (Go down 1 level)
Flags = 0x02
Name header = "pb"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success withvcard object
displayphonebookselect next
phonebook

Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"

repeat to findtargeted
phonebook.

Success withvcard object
displayphonebookdialing

After select phonebook for
dialing, PBAP session
should be released
Session Release(PBAP)
ATD dddddd…;
OK+CIEV : (callsetup = 2)

if audioconnection
is notpresent

if the AG
enables totransfer ringback tone
over audio

audio connection
setup(HFP 4.11)

audio
connection
establishedaudio
connection
stablishedstart the call establishment procedure using
the phone number ddddd

ring back tone40©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)+CIEV : (callsetup = 3)
the call established+CIEV : (call = 1)
+CIEV : (callsetup = 0)
call active

voice communication

41

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)4.4.2 Dialing from incoming call history (PSEs entries are modified during an active
PBAP session)
If any of the PSEs entries are modified/deleted during an active PBAP session, thenthe PSE shall return Error "Precondition failed" to all read requests until the client
has updated the vCard-listing. When the PCE receive Error “Precondition failed”,
PCE shall go back to root folder and retry to retrieve Phonebook entries.
If PSE has “Change tracking” function, PSE does not return Error. In this case, theMSC is similar to section 4.4.1.

Dialing
HMI

Car Equipment
PCE

HF

AG
Service Level
Connection

select device

Session Establishment(PBAP)
SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
listing folder
select phonebook
in the phone's
memoryif user selects
SIM card.

SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success

if PCE wants to know
the number of entries.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 0
Success withvcard-listing object(with PhonebookSize)
Get
Type = "x-bt/vcard-listing"Name header = "ich"
MaxListCount = 5

42

Cellular Phone
PSE

HMI

Cellular
Network©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Success withvcard-listing object
listing
phonebookselect other list
repeat to findtargeted
phonebook.

Get
Type = "x-bt/vcard-listing"Name header = "ich"
MaxListCount = 5
Success withvcard-listing object

listing
phonebookincoming callmodeified incoming call history (ich)selectphonebookor dialing

SetPath (Go down 1 level)
Flags = 0x02
Name header = "ich"Success

SetPath command is
not "read requests".

Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Error code
"Precondition Failed"

PCE must retrybrowsing from root
folder.

if user selects
SIM card.

SetPath (Go back to root)
Flags = 0x02
Name header = EMPTY
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "SIM1"
Success
SetPath (Go down 1 level)
Flags = 0x02
Name header = "telecom"
Success

if PCE wants to know
the number of entries.

Get
Type = "x-bt/vcard-listing"Name header = "pb"
MaxListCount = 0
Success withvcard-listing object(with PhonebookSize)

43

PSE shall return Error"Precondition Failed" toall read requests.

©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)Get
Type = "x-bt/vcard-listing"Name header = "ich"
MaxListCount = 5
Success withvcard-listing object
listing
phonebookselect other list
repeat to findtargeted
phonebook.

Get
Type = "x-bt/vcard-listing"Name header = "ich"
MaxListCount = 5
Success withvcard-listing object

listing
phonebookselectphonebookor dialing

SetPath (Go down 1 level)
Flags = 0x02
Name header = "ich"Success
Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success withvcard object

displayphonebookselect next
phonebook
repeat to findtargeted
phonebook.
displayphonebook

Get
Type = "x-bt/vcard"
Name = "<handle>.vcf"
Success withvcard object

dialing

After select phonebook for
dialing, PBAP session
should be released
Session Release(PBAP)

ATD dddddd…;
OK+CIEV : (callsetup = 2)
if audioconnection
is notpresent

audio
connection
establishedaudio connection
setup(HFP 4.11)

44

audio
connection
established©Copyright 2007-2013 Mobile Computing Promotion Consortium (MCPC)MCPC TR-010 Bluetooth Phonebook Access Profile Implementation Guideline Version 1.10(E)start the call establishment procedure using
the phone number ddddd

ring back tone

if the AG
enables totransfer ringback tone
over audio+CIEV : (callsetup = 3)
the call established+CIEV : (call = 1)
+CIEV : (callsetup = 0)
call active

voice communication

45