Home  
|
Company 
|
Products 
|
News 
|
Support 
|
Careers 
|
Contact 
|
Downloads 
|
Location Map 
 
   Products
        Products Center
        Bluelet™ Stack & Profiles
        BlueSoleil™ for Windows
        BlueSoleil™ for WinCE
        BlueSoleil™-PTS
        Bluetooth
        Access Point Series
        Bluetooth CTP-GSM
        phone O100
        Reference Designs

Bluelet™ Host Protocol Stack & Profiles

Stack and Profiles Source Code
Stack and Profiles Object Code + API
Application Profiles SDK

IVT Bluelet™ is a full implementation of the Bluetooth? host protocol stack using ANSI C. The code, which is very efficient, reliable and small, is suitable for embedded applications as well as desktop applications. IVT performed protocol validation using the formal design technique, Specification Description Language (SDL), to assure that all protocols are logically correct before coding. Now Bluelet V6.0 is already qualified as a fully compliant v1.2 Bluetooth protocol stack.

    Major advantages of the IVT Bluelet™:
    • Based on validated SDL model
    • Library based ANSI C source Code, easy to port to different OSs
    • Support different OSs with the same core (Windows 98/ME/2000/XP, Windows CE, Linux, Nucleus, REX, COS-II, ITRON, OSE, VxWorks, pSOS+)
    • Small code size, ideal for embedded applications
    • Support many different Bluetooth chipsets (Cambridge Silicon Radio, Broadcom, Ericsson, Infineon, National Semiconductor, Philips, ST, OKI, Silicon Wave, TI, Waveplus, Zeevo)
    • Support different HCI transport layers (USB, UART, PCMCIA, BCSP)
    • BQB Qualified, compliant with latest Bluetooth Specification
IVT is working closely with Bluetooth chip manufacturers to ensure the interoperability of IVT Bluelet™ stack with Bluetooth chips through HCI. IVT Bluelet™ is used in IVT BlueSoleil-PTS as the reference implementation and used by many Bluetooth test houses and manufactures to perform conformance and interoperability testing against many different implementations. Therefore, IVT Bluelet™ can offer maximum interoperability with others.

IVT Bluelet™ protocol stack system can be divided into four parts, as shown in Figure 1:


  • The first part is the Bluelet System Module. Each protocol registers itself in the Bluelet System Module when it starts up. The Bluelet System Module maintains the Bluetooth host protocols' Finite State Machine (FSM) instance table. A Bluetooth host protocol can use this information to communicate with other Bluetooth host protocols. This module can vary on different platforms, as not all applications require all of these protocols.
  • The second part is the Bluelet Common Function Library Module. This module contains the common code used by the FSM of each protocol, such as the code for timer management and inter-process communications. It also contains all platform-dependent code in the system. When there are multiple requests from different Bluetooth host protocols' FSM instances for common resources, it provides scheduling for these requests.
  • The third part is the Bluelet Protocol Modules for each protocol in the Bluetooth host protocol stack. Each protocol module is implemented using ANSI C and can be easily ported to any platform without modification. It implements states, events and FSM matrices for each event stimulus in each state.
  • The fourth part is the Bluelet User Interface (UI). This part is a system-dependent module. Users can develop their own UI to meet specific requirements.

Based on the Bluelet™ Basic Host Protocol Stack, IVT also developed full range of Bluetooth application profiles which can be provided in source code, object code or SDK form for product manufacturers to develop their particular Bluetooth product such as cameras, printers, PDAs, CDAM phones, smart phones, and so on.

IVT Bluelet™ provides the following Bluetooth profiles:

Serial Port Profile
The scenario covered by this profile deals with legacy applications using Bluetooth as a cable replacement, through a virtual serial port. Any legacy application, such as Hyperterminal and Direct Cable Connection, may run on either Data Circuit Endpoint (DCE) or Data Terminal Endpoint (DTE), using the virtual serial port as if there were a real serial cable connecting the two devices (with RS232 control signalling).
Features:
* Support applications using conventional physical serial port
* Independent of DTE-DCE or DTE-DTE relationships between devices
* Establish and release emulated serial cable connection
* Transfer user's data, modem control signals and port configuration commands
LAN Access Profile
Aided by LAP (LAN Access Point) of Bluetooth, DT (Data Terminal) is able to access the services of a LAN. Once connected to LAP, the DT will operate as if it were connected to the LAN via dial-up networking. In the case that Multiple DTs use one LAP as a wireless means, connecting to a Local Area Network (LAN), the DTs can also communicate with each other via the LAP. As a special case, two Bluetooth devices can form a single connection with each other. This scenario is similar to a direct cable connection commonly used to connect two PCs. In this scenario, one of the devices will take the role of a LAP, the other will be a DT.
Features:
* Support any legacy application using PPP
* Establish PPP link between DTs
* Adopt some appropriate PPP authentication mechanism (e.g. CHAP)
* Transfer data packets and port configuration commands.
* Indicate PPP link losses
* Release PPP link from either DT or LAP
Dial-up Networking Profile
IVT implements Dial-up GW (Gateway) and DT (Data Terminal), allowing a DT access to the public networks through GW using PPP. Users can use a cellular phone or modem as a wireless modem for connecting to a dial-up Internet access server, or use other dial-up services to receive data calls.
Features:
* Scalable according to different AT command sets
* Support any legacy application using PPP
* Establish or release PPP link from either DT or GW
* Transfer PPP packets, modem control signals and AT commands between GW and DT
* Enable GW automatically to monitoring status after DT or GW releases the PPP connection
* Indicate PPP link loss
Headset Profile(Headset Control and Audio Gateway Control)
The headset can be wirelessly connected for the purposes of acting as the device's audio input and output mechanism, providing full duplex audio. The headset increases the user mobility while maintaining call privacy.
Features:
* Scalable according to different AT command sets
* Audio connection establish
* Audio connection release
* Audio connection transfer
* Support Park mode control
Cordless Telephony Profile & Intercom Profile
With these two Profiles, a cellular phone can be used as a cordless phone or a walkie-talkie when possible. In Cordless Phone Profile, the call is sent or received through a voice gateway which is connected to a fixed net. In Intercom Profile, voice connection is established directly between two cellular phones.
Features:
* Scalable according to different requirements
* Caller Line identification
* Dial type (Tone or Pulse) switchable
* Flash duration adjustable
* Volume control
* Call switch
OBEX File Transfer Profile
The profile is an application widely used on PCs, PDAs, which can transfer objects through a wireless OBEX connection. IVT provides a complete implementation including the client and the server application respectively.
OBEX Synchronization Profile
The profile is an application that allows you to synchronize your contacts, calendar, tasks and emails between your mobile devices and popular PC applications. Compared with other synchronization products, it is faster, more flexible, and easier to use.
OBEX Object Push Profile
The profile is an application that can exchange business objects between notebooks, PCs, PDAs, and other mobile devices.
Personal Area Networking Profile
The Profile makes two or more Bluetooth enabled devices form an ad-hoc network and access a remote network through a network access point with the same mechanism. It supports up to seven simultaneous PAN users. It makes use of standard Bluetooth facilities such as Service Discovery Profile to enable zero-configuration operation.
Features:
* Supports both GN and NAP roles of PAN profile.
* Supports multi-protocols: IPV4, IPV6, IPX, NetBIOS, NetBEUI.
* Supports MIBs for bridging devices and interfaces.
* Supports Bluetooth link level security.
* Supports authentication and access rights management.
* Easy to use, share files by using Network neighborhood between devices.
* Uses multi-slot packets for high data throughput.
* Up to seven active PAN users.
Fax profile
IVT implements fax GW (Gateway) and DT (Data Terminal) allowing a DT sending and receiving facsimile via GW. DT can use a cellular phone or modem as a wireless modem to exchange document facsimile with other fax terminals
Features:
* Scalable according to different AT command sets
* Establish or release data link from either DT or GW
* Transfer modem control signals and AT commands between GW and DT
* Enable GW automatically to monitoring status.
* Indicate data link loss on both DT and GW side.
Hands-Free Profile
A typical example of hands-free devices is a car Hands-free unit. It acts as a
wireless audio input/output device of a cellar phone and provides some remote control functions.
Features:
* Scalable according to different AT command sets
* Voice recognition dialer
* Full voice control for picking up or hanging off the phone
* Audio volume control
* Audio connection transfer
* Support Park mode control
Human Interface Device Profile
Bluetooth Human Interface Device (HID) Profile defines the protocols, procedures, and the features that shall be used by Bluetooth Human Interface Devices, such as keyboards, pointing devices, gaming devices, and remote monitoring devices.
Features:
* Support both HID host and HID device role, and a host can use up to seven simultaneous HID devices.
* Support Bluetooth link level security.
Hardcopy Cable Replacement Profile
This profile is used to replace the cable between hosts and peripheral devices (such as printers) with Bluetooth link. The data is rendered through device driver on the client side. The scenarios covered by this profile are:
* Printing any type of document.
* Scanning documents.
Features:
1.HCRP Client:
* Support printing and scanning
* Use the original driver of devices
* Support any legacy applications' printing functions, e.g. WORD, EXCEL, PDF
* Full implementation of HCRP spec, including optional control commands and notifications
2.HCRP Server:
* Support printing and scanning
* Support multiple clients simultaneously
* Server source codes are completely portable and need small ROM, configurable RAM size
* Full implementation of HCRP spec, including optional control commands and notifications
* Can be embedded into a printer or scanner adapter/dongle, into a printer or scanner directly, and also can be run directly on a normal PC with a printer
Basic Image Profile
The Basic Imaging profile, which uses the Generic Object Exchange profile (GOEP) as a base profile to define the interoperability requirements for the protocols needed by the application, provides the fundamental functions enabling Bluetooth devices to negotiate the size and encoding of imaging data to be exchanged, and to transfer the images based on the negotiation mechanism.
Features:
* Image Push
* Image Pull
* Advanced Image Printing
* Automatic Archive
* Remote Camera
* Remote Display
SIM Access Profile
 
Features:
 
Audio Video Remote Control Profile
 
Features:
 
Advanced Audio Distribution Profile
 
Features: