VCC Modules Reused


ABOUT :

This page is about the modules and codes that are reused in NewTooth and GBI.

Modules reused by SBI (Symbol of Newtooth)

DESCRIPTION :

These are the full Bluetooth protocol layers that were implemented by last year's SLIP members on VCC. However, only the three rightmost modules are reused this year because there would be a "new" module that would run on top of L2CAP (the deep blue block) by making uses of its upper layer interface. This "new" module would be referred throughtout this report as GBI (Game Bluetooth Interface). GBI itself has also reused a lot of codes from RFCOMM (the yellow block). More about GBI below.

Behaviour of BluetoothInterface :
BluetoothInterface_behav
DESCRIPTION :

This symbol is a high level representation of the whole of the Bluetooth implemented and represented in the BluetoothInterface behaviour. But most importantly it represents a single Bluetooth or a Bluetooth enabled device. This is just like SBI (SLIP Bluetooth Interface). SBI is the symbol of my Bluetooth's behaviour, which is known as Newtooth. Newtooth is one of the main focus of my works. It consists of the GBI module on top of the reused modules as L2CAP, LMP and the PacketBaseband.

Symbol of BluetoothInterface :
BluetoothInterface_sym.jpg
DESCRIPTION :

These are the modules reused this year by me in Newtooth.

Lower Layers of Bluetooth reused :

Codes reusd by GBI (Behaviour of GBI)

ABOUT :

GBI is in a sense a modified and simplied version of RFCOMM. That is because much of RFCOMM's codes that deal with the interface of L2CAP could be reused in GBI. These reused codes don't need much modifications, apart from the implementation of the read and write events. GBI is simplied RFCOMM because RFCOMM also has to interact with some higher level protocol layers and that make its implementation more complex and longer. But GBI only needs a very simple interface with its upper layer, such as a game device that sends and receives strings.

RFCOMM :
RFCOMM

Next : Interfaces