A brief introduction to Bluetooth – Project topics materials

Get Complete Project Material File(s) Now! »

Software tool

The source code was written in a NetBeans IDE 6.0[9]. NetBeans Mobility Pack 6.0 is very easy to write, test, and debug applications for Java technology enabled mobile devices. It integrates support for the Mobile Information Device Profile (MIDP) 2.0, the Connected, Limited Device Configuration (CLDC). It simplifies coding with templates for MIDlet and MIDlet suites. Net Beans has its ability to show JavaDoc for suggested methods during code completion. It solves device fragmentation problems by enabling us to edit and compile custom configurations for each device. we can easily integrate third-party emulators for a robust testing environment.

Features of NetBeans IDE 6.0
• Over-The-Air (OTA) Download Testing
• Support for J2ME MIDP 2.0 and CLDC 1.1 standards.
• Support for MIDP localization
• Integration with the J2ME Wireless Toolkit 2.2

Datalogger architecture

The chip which we used in Data logger is Free2move Bluetooth. Free2move Bluetooth modules is an easy and efficient way to integrate Bluetooth functionality into your Datalogger product. These modules are available with a number of different firmware versions. The Wireless UART firmware is an embedded single processor solution that implements the Serial Port Profile (SPP). Other firmware versions are Headset, HCI, RFCOMM and the possibility to get customized standalone
applications implemented as an one chip solution.

Smartphones

During the work with this thesis one smartphone were used to test JABWT applications, the Nokia N73. The processor in the N73 is an ARMv1024 at 200MHz 40 MB internal memory AND Up to 2GB miniSD Card. During the work with this thesis JABWT applications were deployed to the 6600
using Bluetooth links. However, the N73 provide HTTP connectivity by both GSM and GPRS, and includes both a WAP browser and the Opera web-browser. Java applications can be downloaded from the Internet.

MIDP 2.0 (JSR 118)

MIDP 2.0 is a revised version of the MIDP 1.0 specification. MIDP 2.0 includes new features such as an enhanced user interface, multimedia and game functionality, greater connectivity, over-the-air (OTA) provisioning, and endto- end security. MIDP 2.0 is backward compatible with MIDP 1.0.
MIDP 2.0 provides greater extensibility. In the course of the ABB Media support has been added. ABB enables developers the ability to add tones, tone sequences and WAV files even if the Mobile Media API (MMAPI) optional package is not available.
Game API is added in MIDP 2.0 which provides standard foundation for building game. MIDP game API includes game-specific functionality which provides greater control over graphics and performance. MIDP 2.0 adds support connectivity standards outside HTTP, such as HTTPS, datagram, sockets, server sockets, and serial port communication. When the device receives information from server, push registry makes possible to activate the midlet. Using carrier networks we can develop even driven applications.
MIDP 2.0 has the ability to deploy and update applications over the air (OTA). The MIDP specification defines how MIDlet suites are discovered, installed, updated and removed on mobile information devices. MIDP allow a service provider to discover which MIDlet suites will work on a given device, and we can get status reports from the device following installation, updates or
removal.
HTTPS and SSL/TLS protocol provides end-to-end security access over the IP (Internet Protocol) network. The ability to set up secure connections is a increase advance for MIDP programming. A wide range of application models require encryption of data and may now utilize the security model of MIDP 2.0 based on open standards.

READ Detection of Mobile-Specific Code Smells

1 Introduction .
1.1 PURPOSE/OBJECTIVES
1.2 THESIS OUTLINE
2 A brief introduction to Bluetooth
2.1 BACKGROUND
2.2 BLUETOOTH ARCHITECTURE
2.3 PICONET
2.4 L2CAP (LOGICAL LINK CONTROL AND ADAPTATION PROTOCOL) LAYER
2.5 RFCOMM
2.5.2 MULTIPLE EMULATED SERIAL PORTS
2.5.3 LIMITATIONS OF USING RFCOMM
2.5.4 CLIENT CONNECTIONS USING RFCOMM PROFILE
2.6 DEVICE DISCOVERY
2.7 SERVICE DISCOVERY
2.8 BLUETOOTH PROFILES
3 Development tools
3.1 J2ME
3.1.1 CONFIGURATIONS AND PROFILES
3.1.2 CONNECTED LIMITED DEVICE CONFIGURATION (CLDC)
3.3 MIDLET
3.3.1 MIDLETS DEPLOYMENT
3.3.2 LOCAL DEPLOYMENT
3.3.3 REMOTE DEPLOYMENT
3.3.4 OTA OVER THE AIR
4 Implementation
4.1 SOFTWARE TOOL
4.2 DATALOGGER ARCHITECTURE
4.3 SMARTPHONES
4.4 SENDING DATA TO WEB SERVER FROM MIDLETS
5 Demonstration and some test results
5.1 DEMOSTRATION
5.2 NETWORKING DISTANCE
6 Conclusion and discussions
References