Document date / Year-Month-Day Approved Revision Document No 2010-August 13 Scott Hansen

Product Type Declaration

Software Overview

Application

Block Diagram

The diagram below illustrates the basic component layout. Areas bounded by the green boxes indicate components provided by the iAnywhere Blue SDK 4.x and Profile SDKs. Blue components are provided by a Blue SDK licensee building our SDK into a new environment. In addition to the Profile SDKs shown in this diagram, iAnywhere has many other Profile SDKs designed to work with the iAnywhere Blue SDK 4.x Stack.

Software Features

• 
  Communications protocol layers specified by the Bluetooth 3.0 + HS specification, including HCI (with support for HCI 5-Wire UART, HCI 3-Wire UART, BCSP, and USB transports), L2CAP, A2MP, SDP, RFCOMM, and OBEX (OBEX is currently packaged as a separate distribution).
  
• 
  Bluetooth 3.0 + HS L2CAP including fixed channels, Lockstep configuration, Extended Flow Specification, Enhanced Retransmission Mode, Streaming mode and Connectionless channels. This includes the L2CAP module called the L2capAgent. The L2capAgent manages the issues related to L2CAP channels running over AMP physical links.
  
• 
  The Management Entity (ME) component that helps to manage device connections, piconets, audio connections, and security for BR/EDR controllers.
  
• 
  AMP support including AMP additions to the Management Entity (MEAMP), the A2MP protocol, and AMP Manager API (AMPMGR).
  

• 
  The Audio/Video Distribution Transport Protocol (AVDTP) which complies with the AVDTP specification version 1.2.
  
• 
  A complete AVDTP API that can support profiles that rely on the Generic Audio/Video Profile.
  
• 
  Connection Management, Stream Management, and Signaling components
  
• 
  A media header parser/builder that simplifies the process of encoding and decoding AVDTP-formatted packet headers.
  
• 
  The Audio/Video Control Transport Protocol (AVCTP) which complies with the AVCTP specification version 1.3.
  
• 
  A complete AVCTP API.
  
• 
  Connection Management, Channel Management, and Messaging components
  
• 
  The Advanced Audio Distribution Profile (A2DP) which complies with the A2DP specification version 1.2.
  
• 
  An A2DP profile implementation, supporting stream configuration, content protection, and stream pause/resume features.
  
• 
  A portable “C” implementation of an SBC audio codec.
  
• 
  An implementation of all features described in the BNEP specification version 1.0.
  
• 
  An implementation of all mandatory features of the PANU, GN and NAP roles described in the PAN specification version 1.0.
  

Software Architecture

Interfaces

There are three interfaces that interact with the rest of the system:

1. 
   The Hardware Interface
   
2. 
   The Operating System Interface
   
3. 
   The Application Interface
   

The Hardware Interface

The iAnywhere Blue SDK 4.x and Profile SDKs relies on the published HCI specification. Therefore, the Blue SDK creates well-formed HCI commands and data, and expects well-formed HCI events and data in return.

HCI commands, events, and data are delivered as packets to a transport-specific layer called a “transport driver”. The transport driver, in turn, sends and receives streams of data through a “hardware driver” which communicates directly with the Bluetooth radio hardware.



The AMP High Speed HW Interface

The AMP Controller Layer provides a standardized way for AMP controller hardware to communicate with higher-level protocol stack implementations. The AMP Controller architecture allows both HCI based AMP Controllers and those with PALs running in the host to be easily integrated into the stack. The AMP controller architecture consists of the following modules:

The iAnywhere Blue SDK 4.x and Profile SDKs requires integration with a “host controller” (sometimes referred to generally as a “Bluetooth radio”). The host controller must include the following components:

• 
  Radio and antenna as per Bluetooth Core 3.0 + HS Specification Volume 2, Part A.
  
• 
  Baseband radio controller as per Bluetooth Core 3.0 + HS Specification Volume 2, Part B.
  
• 
  A Link Manager protocol implementation as per Bluetooth Core 3.0 + HS Specification Volume 2, Part C.
  
• 
  A Host Controller Interface as per Bluetooth Core Specification 3.0 + HS Volume 2, Part E.
  

An implementer is free to use several different transports to connect the host controller’s HCI layer to the Blue SDK’s HCI layer. For example, this may be done over UART, USB, any other Bluetooth-specified manner, or in any manner specific to the hardware (including a software-only HCI on a one-chip solutions). As long as the iAnywhere Blue SDK 4.x and Profile SDKs’ HCI API contract is met the system will behave in a compliant manner.

The Operating System Interface

The iAnywhere Blue SDK 4.x and Profile SDKs defines a set of OS-specific APIs that must be provided by the implementer. These APIs provide basic system services such as a timer, a semaphore to prevent reentrancy, memory copy routines, persistent storage for security link keys, and some debugging functions. The iAnywhere Blue SDK 4.x and Profile SDKs uses only those endpoints to access local operating system functionality.

The “operating system” must supply the following basic tools. Most embedded OS’s provide this level of basic functionality.

• 
  Memory copy/compare/set functions
  
• 
  String compare/length functions
  
• 
  Start/cancel functions for a single timer, and ability to check the current system time
  
• 
  Pre-emptive multitasking is optional, but when available the operating system must also supply:
  
• 
  Ability to prevent stack reentrance by applications (typically done with a mutex semaphore of some kind)
  
• 
  Ability to prevent stack reentrance by HCI layers (another mutex semaphore or an interrupt-suspend mechanism)
  
• 
  Ability to “schedule” the stack task when necessary
  

These features can also be easily provided when no actual operating system is present.

The Application Interface

When building an application that uses the iAnywhere Blue SDK 4.x and Profile SDKs, the implementer need only include the iAnywhere Blue SDK 4.x and Profile SDKs modules that are relevant to the target functionality. For example, a network access point implementer could include BNEP and PAN modules without including RFCOMM.

Once the relevant modules are included, the implementer has access to a large set of application APIs that provide access to stack functionality. The APIs are carefully designed so that if the user follows basic rules of usage published in the API specification, it is difficult or impossible for the API user to cause the component to violate the associated protocol specification.

Profiles are implemented by connecting protocol or profile APIs to a user interface. The implementer has considerable discretion about how the application’s user interface appears or works. The implementer may refer to our sample applications to get ideas about how an application could interact with the iAnywhere Blue SDK 4.x and Profile SDKs.

Application Requirements

As specified by section , “The Application Interface”, applications are responsible for fulfilling the API contract specified by the iAnywhere Blue SDK 4.x and Profile SDKs. This includes invoking API functions in the proper order, providing the appropriate arguments to function calls, and making proper responses to callback events. Applications are also responsible for presenting an application user interface to the end-user.

Sample Portings

For information about how to adapt or port the iAnywhere Blue SDK 4.x and Profile SDKs to a relevant environment where it is to be used so that the implementations execute without errors, refer to the following sections of this document:

Section Number	Section Text
	The Hardware Interface
	The Operating System Interface
	The Application Interface
	Application Requirements

Hardware / Software Reference Platforms

The following table lists the environment which was utilized in qualifying this design. (Not all of the combinations were used on all of the tests.)

Application	OS	Baseband HW	AMP HW
A2DP Sample Application	Windows XP	CSR Nanosira fw ver. 2.1_23_0711021204 USB Dongle	N/A
L2CAP Sample Application	Windows XP	Belkin Mini 2.1 USB Dongle	Marvell 8688
API Grinder AV Worker Test Application	Windows XP	CSR Nanosira fw ver. 2.1_23_0711021204 USB Dongle	N/A
API Grinder BNEP Worker Test Application	Windows XP	CSR Nanosira fw ver. 2.1_23_0711021204 USB Dongle	N/A
L2CAP Sample Application	Windows XP	Belkin Mini 2.1 USB Dongle	N/A
API Grinder Core Worker Test Application	Windows XP	CSR Nanosira fw ver. 2.1_23_0711021204 USB Dongle	N/A
QT BSM Sample Application	Windows 7	PTS Dongle, BT2.1+EDR	N/A
API Grinder Core Worker Test Application	Windows XP	CSR Nanosira fw ver. 2.1_23_0711021204 USB Dongle	TCP AMP
SBC Dencoder Sample Application	Windows Vista	CSR Nanosira USB Dongle	N/A
SBC Encoder Sample Application	Windows Vista	CSR Nanosira USB Dongle	N/A

Note that although this table does show some of the environments were the iAnywhere Blue SDK 4.x and Profile SDKs has been successfully ported, it is not a representative list of the numerous successful portings achieved by our customers, which include custom applications, embedded operating systems, and diverse hardware platforms.

Components in our iAnywhere Blue SDK 4.x and Profile SDKs are qualified running with samples for each of the external components illustrated in section , Block Diagram. Our design goal is to make all interfaces to each external component completely clear so that the components in the iAnywhere Blue SDK 4.x and Profile SDKs behave exactly as documented in a new implementation. This reduces the testing burden for new implementations that include our iAnywhere Blue SDK 4.x and Profile SDKs.

Contact Information

Use the following contact information to obtain additional details relevant to the support of this design:

iAnywhere Solutions

Mobile Device Solutions Group

bluesdk@ianywhere.com

RIN Datasheet 2010-08-03

Directory: tpg -> refnotes
tpg -> Course description

Download 60.69 Kb.

Share with your friends: