W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2012

[ACTION-530] Use cases for Bluetooth API

From: Jungkee Song <jungkee.song@samsung.com>
Date: Mon, 16 Apr 2012 17:22:58 +0900
To: 'DAP' <public-device-apis@w3.org>
Message-id: <002a01cd1baa$21c34cd0$6549e670$%song@samsung.com>
Hi,

Regarding Bluetooth (BT) API (ACTION-530 gather use cases for Bluetooth), I
described the functionalities and collected the use cases below. BT already
has promising use cases in practice including call and keyboard/mouse
control, but I think the following cases are more feasible in web app
context.

Comments on the use cases and the way how we deal with BT in DAP would be
appreciated.

1. BT functionality (BT profiles)
  - Requisite but hard part
    [Connectivity] Scan / Pairing / Service Discovery
  - Required
    [Data Transfer] OPP (Object Push profile)
    [Play Music] A2DP / AVRCP (Advanced Audio Distribution Profile / Audio
and Video Remote Control Profile)
    [Phonebook Sync w/ Car-Kit] PBAP (Phone Book Access Profile)
    [Serial Communication] SPP (Serial Port Profile)
  - Not required (in web app context)
    [Call] HSP (Headset profile), HFP (Hands-Free profile)
    [Keyboard/Mouse] HID (Human Interface Device)
    [Tethering] PAN (Personal Area Networking)
    [Print] BPP (Basic Printing Profile)
    [BT Low Energy] ATT (Attribute Profile), GATT (Generic ATT)

2. Use cases
[Data Transfer] Jake meets Aileen at the commuter train in the morning. He
comes to remember that he should have sent the package of photos that they
took in the company picnic two weeks ago. Jake asks Aileen to turn on the
bluetooth connectivity and search his mobile phone. Jake's phone is
successfully scanned from Aileen's phone. They pair each other's phone, and
Aileen downloads 10MB of the photo package using file transfer application.

[Play Music] Aileen and Clementine comes over to Jake's home. They would
like to listen to music and talk about songs each of them wants to listen
to. Having a bluetooth speaker, all of them turn on the bluetooth
connectivity of their smartphones. Then, they load the web app,
http://example.com/btmusicplayer/ and login. In the web app, they scan and
pair with the bluetooth speaker in the room and place the song files they
want to listen to. The web app makes the playlist and play them via
bluetooth connection.

[Phonebook Sync] While driving for an appointment to dentist, Jake finds
that he left his phone at work. He has to call the dentist to have them know
he will be little late. Jake comes to remember that he brought his tablet
and, fortunately, has the same contact list in the bluetooth car-kit in his
car. He turns on the bluetooh connectivity in his tablet, pairs it with the
car-kit and syncs the phonebook up to date. Using the car-kit, he calls the
dentist to inform he is late.

[Serial Communication#1: toy control] Jake buys a bluetooth doll for his
daughter to celebrate her birthday. The bluetooth doll has functions
including, "speaking", "laughing" and "waving hands." The doll is also
provided with many controllers developed as web applications. Jake loads one
of the web app, http://examples.com/dolltoplay/. He turns the bluetooth
connectivity of his smartphone and pairs it with the doll. His daughter
controls the doll using the menus in the web app.
  e.g.
  > Robotic ball:
http://www.youtube.com/watch?feature=player_embedded&v=gRzO_FRAGV4
  > Car control:
http://www.youtube.com/watch?feature=player_detailpage&v=sKWMFsT-bts
  > Speaking doll (Dolly):
http://www.youtube.com/watch?feature=player_detailpage&v=dyr0fWE4uyo

[Serial Communication#2: p2p gaming] After a long day, Jake and Aileen get
on the commuter train. Jake tells Aileen to play chess with him on the way.
Aileen scans Jake's device using bluetooth connectivity, and pairs her
device with Jake's device. They load the online chess web app,
http://example.com/chessonline/, and play chess sitting next to each other.

Regards, Jungkee

Jungkee Song
Samsung Electronics
Received on Monday, 16 April 2012 08:23:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:53 UTC