pbap_pce
Overview
This example demonstrates the PBAP PCE basic functionality, the PCE support be connected to a PSE like a mobile phone or a board running a PSE application.
Prepare the Demo
Open example’s project and build it.
Connect a USB cable between the PC host and the OpenSDA USB port on the target board.
Open a serial terminal on PC for OpenSDA serial device with these settings:
115200 baud rate
8 data bits
No parity
One stop bit
No flow control
Download the program to the target board.
Either press the reset button on your board or launch the debugger in your IDE to begin running the example.
Run the Demo
This demo runs fully automatic. The user needs to place the PSE device that wants to be connected as close as possible to the PCE. Here’s a log of a sample run. PSE is a mobile phone.
Bluetooth PBAP PCE demo start… Bluetooth initialized BR/EDR set connectable and discoverable done
Discovery started. Please wait … BR/EDR discovery complete [1]: A0:CD:F3:77:F2:DC, RSSI -72 [2]: 04:6C:59:78:5E:DC, RSSI -71 NXL53507 [3]: F8:E5:CE:19:75:D3, RSSI -69 Chang [4]: 24:2E:02:C3:75:45, RSSI -41 test [5]: CC:EB:5E:10:3E:79, RSSI -70 Redmi K700000 [6]: 30:BB:7D:8F:43:34, RSSI -61 AlisaS [7]: 94:87:E0:83:99:61, RSSI -70 AnChangMI 8 SE [8]: 98:43:FA:27:41:CD, RSSI -93
Connect 4 Connection pending
bt_connected SDP discovery started
sdp success callback pbap version is 101 pbap pse supported repositories is 1 supported feature not found, use default feature_config : 3 rfcomm channel found. Connecting … Successfully START PBAP PCE entities Security changed: 24:2E:02:C3:75:45 level 2 PABP CONNECT SUCCESS
============== BODY ============== BEGIN:VCARD VERSION:2.1 FN;CHARSET=UTF-8:descvs N;CHARSET=UTF-8:descvs END:VCARD BEGIN:VCARD VERSION:2.1 N:;cc;;; FN:cc TEL;CELL:154555845 END:VCARD BEGIN:VCARD VERSION:2.1 N:;qwe;;; FN:qwe X-ANDROID-CUSTOM:vnd.android.cursor.item/nickname;147;1;;;;;;;;;;;;; TEL;CELL:151865216 TEL;CELL:153464856 EMAIL;HOME:wudhxjsjd@qq.com ADR;HOME:;;123456789;;;; NOTE:old BDAY:1904-05-24 X-AIM:@qq.com END:VCARD ============ END BODY ============
pbap pse path set success
============== BODY ==============
pbap pse path set success
============== BODY ============== BEGIN:VCARD VERSION:2.1 FN: N: TEL;X-0:1155 X-IRMC-CALL-DATETIME;DIALED:20220913T110607 END:VCARD ============ END BODY ============
pbap pse path set success
PABP DISCONNECT SUCCESSL : a0 Disconnected (reason 0x13)
Specific implementation steps:
Step 1：Initialize Bluetooth log: Bluetooth PBAP PCE demo start… Bluetooth initialized BR/EDR set connectable and discoverable done
Step 2: Device Discovery After successful Bluetooth initialization, the PCE automatically discovers the device. log： Discovery started. Please wait … BR/EDR discovery complete [1]: A0:CD:F3:77:F2:DC, RSSI -72 [2]: 04:6C:59:78:5E:DC, RSSI -71 NXL53507 [3]: F8:E5:CE:19:75:D3, RSSI -69 Chang [4]: 24:2E:02:C3:75:45, RSSI -41 test [5]: CC:EB:5E:10:3E:79, RSSI -70 Redmi K700000 [6]: 30:BB:7D:8F:43:34, RSSI -61 AlisaS [7]: 94:87:E0:83:99:61, RSSI -70 AnChangMI 8 SE [8]: 98:43:FA:27:41:CD, RSSI -93
Step 3: create ACL connection The PCE finds the device with the strongest RSSI to connect from the device which cod is computer or phone. log： Connect 4 Connection pending
Step 4: sdp_find After ACL connect successfully, PCE perform an SDP operation to find the PSE service class in the connected device. log: bt_connected SDP discovery started
Step 5: create pbap connection After sdp callback successfully, PCE will parse to get the peer_feature, GOEP_L2CAP_PSM and rfcomm channel etc. Prioritizes the establishment of pbap connections based on GOEP_L2CAP_PSM if supported by the PSE. Otherwise the connection is established based on the rfcomm channel. log： sdp success callback pbap version is 101 pbap pse supported repositories is 1 supported feature not found, use default feature_config : 3 rfcomm channel found. Connecting … Successfully START PBAP PCE entities Security changed: 24:2E:02:C3:75:45 level 2 PABP CONNECT SUCCESS
Step 6: pull phonebook object. for example : telecom After pbap connect successfully, pce active pull phonebook object from pse. for example telecom/pb.vcf. Parse the acquired information and print. log: ============== BODY ============== BEGIN:VCARD VERSION:2.1 FN;CHARSET=UTF-8:descvs N;CHARSET=UTF-8:descvs END:VCARD BEGIN:VCARD VERSION:2.1 N:;cc;;; FN:cc TEL;CELL:154555845 END:VCARD BEGIN:VCARD VERSION:2.1 N:;qwe;;; FN:qwe X-ANDROID-CUSTOM:vnd.android.cursor.item/nickname;147;1;;;;;;;;;;;;; TEL;CELL:151865216 TEL;CELL:153464856 EMAIL;HOME:wudhxjsjd@qq.com ADR;HOME:;;123456789;;;; NOTE:old BDAY:1904-05-24 X-AIM:@qq.com END:VCARD ============ END BODY ============
Step 7: set path to telecom Need to set the path before getting vcardlisting. log： pbap pse path set success.
Step 8： pull vcard listing object After set path successfully, pce pull vcard listing object from pse. for example : cch. Parse the acquired information and print. log： ============== BODY ==============
Step 9： set path to cch Need to set the path before getting vcardentry. log: pbap pse path set success.
Step 10: pull vcard entry object. After set path successfully, pce pull vcard entry object from pse. for example : 4.vcf. Parse the acquired information and print. log: ============== BODY ============== BEGIN:VCARD VERSION:2.1 FN: N: TEL;X-0:1155 X-IRMC-CALL-DATETIME;DIALED:20220913T110607 END:VCARD ============ END BODY ============
Step 11: set path to root log： pbap pse path set success.
step 12: pbap disconnect log： PABP DISCONNECT SUCCESSL : a0
Note: 1: If you don’t want to display the acquired information, set the macro CONFIG_BT_PRINTF_VALUE to 0 in app_pbap_pce.c.
2: When connecting to PSE which is a moblie phone, please pay attention to the phone alert messages. In particular, please turn on the permission to allow “Shared Phonebook”. If PSE is a apple iphone, after connecting for the first time, need to actively turn on the “Share Contacts Permission” on phone and then re-run the demo.
3: PCE will only select the device with the strongest RSSI among those with COD of phone or computer for connection. Please place the PSE as close as possible to the PCE. You can lift this restriction by blocking the relevant code in the app_discover.c.