W3C home > Mailing lists > Public > public-web-bluetooth@w3.org > November 2014

Automotive use-cases for bluetooth

From: Rees, Kevron <kevron.m.rees@intel.com>
Date: Mon, 3 Nov 2014 16:20:31 -0800
Message-ID: <CAFW5wYaqV67ESW6bko=28s1d1=bb+zxXxV_PHjx--pc_5J0_zw@mail.gmail.com>
To: public-web-bluetooth@w3.org
I'm working with the W3C automotive business group and have been
assigned to look at bluetooth APIs to see whether or not automotive
use-cases are covered.  After looking at the specification you have
produced, I have a few questions:

1) It is not clear whether or not the API includes the ability to pair devices.

2) the bluetooth device API has a generic "connect()" API.  It is not
clear to me which profiles will be connected when this method is
called.  In automotive, the headunit usually assumes the A2DP "sink"
role.  Sound is routed from the other device to the head unit's sound
system.  If connect() is called from a mobile phone, will the right
A2DP profile be connected as well as HFP, AVRCP, etc?

3) AVRCP API.  Many mobile devices expose AVRCP.  This allows mobile
media devices to be controlled from the vehicle headunit.  Is there a
planned API to cover this use-case?

Received on Tuesday, 4 November 2014 00:22:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 4 November 2014 00:22:17 UTC