BLUETOOTH QUALCOM more

Bluetooth Wireless Technology Profiles

To use Bluetooth wireless technology, a device must be able to interpret certain Bluetooth profiles. Bluetooth profiles are definitions of possible applications and specify general behaviors that Bluetooth enabled devices use to communicate with other Bluetooth devices. There are a wide range of Bluetooth profiles that describe many different types of applications or use cases for devices. By following the guidance provided by the Bluetooth specification, developers can create applications to work with other Bluetooth devices.At a minimum, each Bluetooth profile contains information on the following topics:Dependencies on other profilesSuggested user interface formats.Specific parts of the Bluetooth protocol stack used by the profile. To perform its task, each profile uses particular options and parameters at each layer of the stack and this may include, if appropriate



https://qualweb.bluetooth.org/apps/content/default.aspx?doc_id=236409


Select Language EnglishJapaneseKoreanSimplified ChineseSearch siteSearch 

Serial Port Profile (SPP)

SPP defines how to set up virtual serial ports and connect two Bluetooth enabled devices.

Usage Scenarios

A scenario would be using two devices, such as PCs or laptops, as virtual serial ports and then connecting the two devices via Bluetooth technology.

Example Products

Here are a few examples of the types of devices that you might find using the SPP:PCLaptop

Getting Technical

The SPP defines two roles, Device A and Device B.Device A – This is the device that takes initiative to form a connection to another device (initiator).Device B – This is the device that waits for another device to take initiative to connect (acceptor).


he Baseband, LMP and L2CAP are the OSI layer 1 and 2 Bluetooth protocols. RFCOMM is the Bluetooth adaptation of GSM TS 07.10, providing a transport protocol for serial port emulation. SDP is the Bluetooth Service Discovery Protocol.The port emulation layer shown in the figure to the left is the entity emulating the serial port, or providing an API to applications.The applications on both sides are typically legacy applications, able and wanting to communicate over a serial cable (which in this case is emulated). But legacy applications cannot know about Bluetooth procedures for setting up emulated serial cables, which is why they need help from some sort of Bluetooth aware helper application on both sides. (These issues are not explicitly addressed in this profile; the major concern here is for Bluetooth interoperability.)


anguage EnglishJapaneseKoreanSimplified ChineseSearch siteSearch 

Video Distribution Profile (VDP)

VDP defines how a Bluetoothenabled device streams video over Bluetooth wireless technology.

Usage Scenarios

Sample use cases include the streaming of a stored video from a PC media center to a portable player or streaming from a digital video camera to a TV.

Example Products

Here are a few examples of the types of devices that you might find using the VDP:PCPortable PlayerVideo CameraTVVideo monitor

Getting Technical

The VDP defines two roles, Source (SRC) and Sink (SNK).Source (SRC) – A device is the SRC when it acts as a source of a digital video stream that is delivered to the SNK of the piconet.Sink (SNK) – A device is the SNK when it acts as a sink of a digital video stream delivered from the SRC on the same piconet.The Baseband, LMP, L2CAP, SDP are Bluetooth protocols defined in the Bluetooth Core specifications. AVDTP consists of a signalling entity for negotiation of streaming parameters and a transport entity that can handle streaming itself.The Application layer shown in the figure to the left is the entity in which the device can set application service and transport service parameters. The entity also adapts the video streaming data into/from the defined packet format.For the shaded protocols/entities in the figure to the left, the GAVDP applies, except in those cases where this profile explicitly states deviations


https://qualweb.bluetooth.org/Building/HowTechnologyWorks/ProfilesAndProtocols/SPP.htm

https://qualweb.bluetooth.org/Building/HowTechnologyWorks/Architecture/HCI.htm

Host Controller Interface (HCI)

General Description

The HCI provides a command interface to the baseband controller and link manager, and access to configuration parameters. This interface provides a uniform method of accessing the Bluetooth baseband capabilities.

Lower Layers of the Bluetooth Software Stack

 The figure to the left provides an overview of the lower software layers. The HCI firmware implements the HCI Commands for the Bluetooth hardware by accessing baseband commands, link manager commands, hardware status registers, control registers and event registers. Several layers may exist between the HCI driver on the host system and the HCI firmware in the Bluetooth hardware. These intermediate layers, the Host Controller Transport Layer, provide the ability to transfer data without intimate knowledge of the data.The HCI driver on the Host exchanges data and commands with the HCI firmware on the Bluetooth hardware. The Host Control Transport Layer (i.e. physical bus) driver provides both HCI layers with the ability to exchange information with each other. The Host will receive asynchronous notifications of HCI events independent of which Host Controller Transport Layer is used. HCI events are used for notifying the Host when something occurs. When the Host discovers that an event has occurred it will then parse the received event packet to determine which event occurred. 

Host Controller Transport Layer

The host driver stack has a transport layer between the Host Controller driver and the Host. The main goal of this transport layer is transparency. The Host Controller driver (which interfaces to the Controller) should be independent of the underlying transport technology. Nor should the transport require any visibility into the data that the Host Controller driver passes to the Controller. This allows the interface (HCI) or the Controller to be upgraded without affecting the transport layer.  



Host Controller Interface (HCI)

General Description

The HCI provides a command interface to the baseband controller and link manager, and access to configuration parameters. This interface provides a uniform method of accessing the Bluetooth baseband capabilities.

Lower Layers of the Bluetooth Software Stack

 The figure to the left provides an overview of the lower software layers. The HCI firmware implements the HCI Commands for the Bluetooth hardware by accessing baseband commands, link manager commands, hardware status registers, control registers and event registers. Several layers may exist between the HCI driver on the host system and the HCI firmware in the Bluetooth hardware. These intermediate layers, the Host Controller Transport Layer, provide the ability to transfer data without intimate knowledge of the data.The HCI driver on the Host exchanges data and commands with the HCI firmware on the Bluetooth hardware. The Host Control Transport Layer (i.e. physical bus) driver provides both HCI layers with the ability to exchange information with each other. The Host will receive asynchronous notifications of HCI events independent of which Host Controller Transport Layer is used. HCI events are used for notifying the Host when something occurs. When the Host discovers that an event has occurred it will then parse the received event packet to determine which event occurred. 

Host Controller Transport Layer

The host driver stack has a transport layer between the Host Controller driver and the Host. The main goal of this transport layer is transparency. The Host Controller driver (which interfaces to the Controller) should be independent of the underlying transport technology. Nor should the transport require any visibility into the data that the Host Controller driver passes to the Controller. This allows the interface (HCI) or the Controller to be upgraded without affecting the transport layer.  




Overview of HCI Commands and Events

Generic Events

The generic events can occur due to multiple commands, or events that can occur at any time.

Device Setup

The device setup commands are used to place the Controller into a known state.

Controller Flow Control

The controller flow control commands and events are used to control data flow from the Host to the controller.

Controller Information

The controller information commands allow the Host to discover local information about the device.

Controller Configuration

The controller configuration commands and events allow the global configuration parameters to be configured.

Device Discovery

The device discovery commands and events allow a device to discover other devices in the surrounding area.

Connection Setup

The connection setup commands and events allow a device to make a connection to another device.

Remote Information

The remote information commands and events allow information about a remote device's configuration to be discovered.

Synchronous Connections

The synchronous connection commands and events allow synchronous connections to be created

Connection State

The connection state commands and events allow the configuration of a link, especially for low power operation.

Piconet Structure

The piconet structure commands and events allow the discovery and reconfiguration of piconet.

Quality of Service

The quality of service commands and events allow quality of service parameters to be specified.

Physical Links

The physical link commands and events allow the configuration of a physical link.

Host Flow Control

The Host flow control commands and events allow flow control to be used towards the Host.

Link Information

The link information commands and events allow information about a link to be read.

Authentication and Encryption

The authentication and encryption commands and events allow authentication of a remote device and then encryption of the link.

Testing

The testing commands and events allow a device to be placed into test mode.

 

HCI Flow Control

Host to Controller Data Flow Control

Flow control is used in the direction from the Host to the Controller to avoid overflowing the Controller data buffers with ACL data destined for a remote device (using a Connection Handle) that is not responding. The Host manages the data buffers of the Controller.

Controller to Host Data Flow Control

In some implementations, flow control may also be necessary in the direction from the Controller to the Host. The Set Host Controller To Host Flow Control command can be used to turn flow control on or off in that direction. 


https://qualweb.bluetooth.org/Building/HowTechnologyWorks/Architecture/HCI.htm


PRESS RELEASES

November 15, 2012

Qualcomm Atheros and Cisco Announce Indoor Location Technology Collaboration

Network and Mobile Technology Leaders Team to Deliver More Precise Service Discovery and Context Awareness for Indoor EnvironmentsSAN JOSE, Calif. – November 15, 2012 — Qualcomm Technologies, Inc. (QTI) today announced that its networking and connectivity subsidiary, Qualcomm Atheros, Inc., and Cisco, the worldwide leader in networking, are collaborating to accelerate indoor location services for public and private venues that utilize Cisco wireless infrastructure, to provide an unprecedented set of benefits to venue owners, application developers, mobile device and networking OEMs, and consumers. The combination of the Qualcomm IZat™ indoor location services platform and the Cisco "Connected Mobile Experience" solution will improve indoor location accuracy and enable service discovery and context awareness in some of the world's leading retail, travel and hospitality venues. The leadership positions of the Cisco enterprise wireless solution and Qualcomm mobile technology will accelerate market adoption and foster further technology innovation to grow the indoor location ecosystem.Many connected consumers rely on their mobile devices and location-based apps for information, interaction and context. However, the majority of these apps and services are challenged in urban environments and indoors, where satellite systems are unable to provide location data. Together, Qualcomm Atheros and Cisco are focused on accelerating more precise indoor location capabilities and ensuring interoperability between their respective solutions in order to enhance service discovery, provide greater contextual awareness, and deliver a better experience in the world's leading venues."Qualcomm Atheros is enhancing the mobile experience by providing more precise context about who, and what, is nearby – in any environment," said Cormac Conroy, vice president, location products and technology, Qualcomm Atheros. "Working with Cisco to build an ecosystem of interoperable positioning technologies, we are creating new opportunities for mobile OEMs, operators and venues to roll out location-based services that deliver relevant and timely information to the customers they serve, whenever a smartphone based on the Qualcomm Snapdragon™ processor is near or within a Mobile Services Engine powered Wi-Fi network."Qualcomm Atheros' location technologies have shipped in more than one billion devices operating in mobile networks worldwide. The company recently enhanced its IZat location platform to enable more precise positioning (within 3-5 meters) inside buildings to make indoor positioning more useful to consumers. Overcoming the traditional challenges of indoor positioning brings Qualcomm Atheros, Cisco and the industry one step closer to their goal of providing always-on location awareness in any environment.Cisco Connected Mobile Experiences offers the first Wi-Fi Passpoint (HotSpot 2.0) solution to integrate indoor location and real-time analytic technologies to deliver personalized mobile services and content. The solution is built upon the Cisco Mobility Services Engine, the industry's only available technology that can leverage an existing access point infrastructure to determine indoor location for mobile devices. This solution enables app developers to leverage this contextual information to deploy mobile applications and services that engage the customer more effectively."We want to take the current popularity and reach of conventional outdoor navigation and location apps and extend it to indoor venues all over the world," said Sujai Hajela, vice president and general manager, wireless networking business unit, Cisco. "Combining the strengths of the leader in mobile-based positioning — Qualcomm Atheros — and our position as the leader in WLAN networking, creates new and exciting opportunities for our customers across industries such as retail, hospitality, entertainment, travel, healthcare and more. Together, we allow businesses to leverage the intelligence in their network and uncover additional revenue opportunities."Working together, Cisco and Qualcomm Atheros will differentiate the indoor location experience in venues where Cisco network infrastructure and Qualcomm-enabled handsets are being used, and accelerate indoor location capabilities on mobile devices in popular venues around the world. For more information, please visit www.qca.qualcomm.com and www.cisco.com.

About Cisco

Cisco (NASDAQ: CSCO) is the worldwide leader in networking that transforms how people connect, communicate and collaborate. Information about Cisco can be found at www.cisco.com. For ongoing news, please go to newsroom.cisco.com.

About Qualcomm Technologies, Inc.

Qualcomm Technologies, Inc. (QTI), a wholly owned subsidiary of Qualcomm Incorporated (NASDAQ: QCOM), is redefining the way people incorpo-rate wireless devices and services into everyday life. QTI and its subsidiaries operate substantially all of Qualcomm's research and development activities, and product and services businesses, including Qualcomm's semiconductor business, QCT. QTI's developments enable opportunities across the wireless and wired value chains by making devices and networks faster, content richer and communications more personal and affordable to people everywhere. For more information, go to www.qualcomm.com.

NOTE ON FORWARD-LOOKING STATEMENTS:

Qualcomm Atheros is a trademark of Qualcomm Atheros Inc. Qualcomm, Snapdragon and IZat are trademarks of Qualcomm Incorporated. Wi-Fi is a registered trademark of the Wi-Fi Alliance. All other trademarks are the sole property of their respective owners.Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

For press inquires contact:

http://www.atheros.com/corporate/content.php?nav1=119&news=974