Blue Tears Project Bluetooth Tracking: Distributed Information Systems

Introduction Bluetooth tracking system Bluetooth tracking system Approximate tracking Approximate tracking BT is limited to a 10m radius BT is limited to a 10m radius Transfer rate 3mb/s Transfer rate 3mb/s 90% of current cell phones & smartphones have Bluetooth tech built-in. 90% of current cell phones & smartphones have Bluetooth tech built-in. Not limited to just phones. Can track all BT devices Not limited to just phones. Can track all BT devices

Bluetooth Tracking System Approximate location tracking Approximate location tracking 4 major parts 4 major parts Bluetooth Discovery Access point, Bluetooth Access point, Central server and Data Base. Bluetooth Discovery Access point, Bluetooth Access point, Central server and Data Base. Uses a WIFI connection for RMI connection Uses a WIFI connection for RMI connection RMI used to communicate with Server and Access points RMI used to communicate with Server and Access points

Bluetooth Tracking System(cont) Tracking by floor levels Tracking by floor levels Scenarios which could use BTT system Scenarios which could use BTT system Tracking traffic in malls Tracking traffic in malls Distribution of man power Distribution of man power “finding babies” “finding babies” Data mining, commonly traveled routes Data mining, commonly traveled routes Clocking in/out system Clocking in/out system Locating medical devices/patients/doctors Locating medical devices/patients/doctors

Bluetooth Tracking System(cont) Coded in JAVA Coded in JAVA Using Bluecove Java library for Bluetooth Using Bluecove Java library for Bluetooth JSR-82 implementation JSR-82 implementation Bluecove provides interface to application profiles: Bluecove provides interface to application profiles: SDAP SDAP RFCOMM RFCOMM OBEX OBEX *information provided by Bluecove.org *information provided by Bluecove.org

The Approach Other tracking systems use two way communication between client and server Other tracking systems use two way communication between client and server Some send request to find current location only Some send request to find current location only Fairly simple, lose valuable data, and requires a lot of client input. Fairly simple, lose valuable data, and requires a lot of client input. Our approach keeps track of the client’s movements (currently up to the last 10 access points) Our approach keeps track of the client’s movements (currently up to the last 10 access points)

The Approach Closest neighbor algorthim Closest neighbor algorthim Avoid overloading the AP with devices to check Avoid overloading the AP with devices to check Guess the next possible AP the client could come across Guess the next possible AP the client could come across Client is transparent to tracking system, little to no input from end user Client is transparent to tracking system, little to no input from end user Uses registered Bluetooth address rather than continuous Device Discovery (upto 90sec to discover device) Uses registered Bluetooth address rather than continuous Device Discovery (upto 90sec to discover device) Majority of computation on the Server side, putting less stress on the client and AP Majority of computation on the Server side, putting less stress on the client and AP

Closest Neighbour Access Point 1 Access Point 1 Access Point 5 Access Point 5 Access Point 4 Access Point 4 Access Point 2 Access Point 2 Access Point 3 Access Point 3

Closest Neighbour Access Point 1 Access Point 1 Access Point 5 Access Point 5 Access Point 4 Access Point 4 Access Point 2 Access Point 2 Access Point 3 Access Point 3

Closest Neighbour Access Point 1 Access Point 1 Access Point 5 Access Point 5 Access Point 4 Access Point 4 Access Point 2 Access Point 2 Access Point 3 Access Point 3

Closest Neighbour Access Point 2 Access Point 2 Access Point 1 Access Point 1 Access Point n’ Access Point n’ Access Point n Access Point n Access Point 3 Access Point 3 ap 5 ap 4

Object Diagram mySql Server Manager RMI Communication interfaces Manager Interface Access Point Interface Access Point Interface Access Point 1 Access Point n ……..... Client 1 Client 1 Client n Client n ….

Components 4 major components 4 major components Bluetooth access points Bluetooth access points Bluetooth init access points Bluetooth init access points Central Server Central Server Data Base Data Base Future components Future components Client software Client software

Bluetooth Init Access Point Client would register their Bluetooth device, usually cell/smart phone Client would register their Bluetooth device, usually cell/smart phone Client sets device to discovery for a minute and waits for conformation Client sets device to discovery for a minute and waits for conformation Ap continues checking for new devices Ap continues checking for new devices Once discovered is then searched to see what services as available Once discovered is then searched to see what services as available This could take upwards to 30 – 90 secs depending on demand and device transfer rate This could take upwards to 30 – 90 secs depending on demand and device transfer rate Current version is not configured to run continuously. Current version is not configured to run continuously.

Bluetooth Init Access Point Once the Ap gathers all the required information an update is sent to the Database. Once the Ap gathers all the required information an update is sent to the Database. Ideally you need to register only once and your Bluetooth address is stored for future use Ideally you need to register only once and your Bluetooth address is stored for future use

Bluetooth Access Points Waiting for server to allocate bluetooth address for it to “ping” Waiting for server to allocate bluetooth address for it to “ping” Continues to try pinging bluetooth address Continues to try pinging bluetooth address If found it sends a response to server that it’s found the device at the ap location If found it sends a response to server that it’s found the device at the ap location Requires only one “ping” response. Requires only one “ping” response.

Central Server Consists of the AP manager, Server and Data base manager Consists of the AP manager, Server and Data base manager Server inits all services Server inits all services AP manager registers AP and delegates which AP to search which Bluetooth address AP manager registers AP and delegates which AP to search which Bluetooth address AP manager organizes all input information from AP AP manager organizes all input information from AP

Central Server Database Manager updates and extracts information from the DB Database Manager updates and extracts information from the DB Mapping AP Zones Mapping AP Zones Bluetooth Address and tracking history Bluetooth Address and tracking history

Assumptions The client is not sprinting across the Bluetooth Access points The client is not sprinting across the Bluetooth Access points Client within an access point range at all times Client within an access point range at all times Access points don’t overlap (due to java constraints) Access points don’t overlap (due to java constraints) Bluetooth address attribute is not altered during the session Bluetooth address attribute is not altered during the session Access points are mapped by installer and updated to the Database manually. Access points are mapped by installer and updated to the Database manually.

Crashes No failsafe for failed AP No failsafe for failed AP Possible solution: if hardware fails reach out to the downed AP’s neighbors. Possible solution: if hardware fails reach out to the downed AP’s neighbors. Software fail: thread is recreated if it dies. Software fail: thread is recreated if it dies. Server fails Server fails Possible solution Leader algorthim Possible solution Leader algorthim AP fitted with central server services and fights for control/leadership. AP fitted with central server services and fights for control/leadership.

Bluetooth specs 10 meters radius 10 meters radius Transfer 3mb/s Transfer 3mb/s One tenth the power and range used for WIFI One tenth the power and range used for WIFI Limited connection, 7 connection Limited connection, 7 connection Industrial BT AP up to 24 connection Industrial BT AP up to 24 connection

Constraints For the demo - Limited to 3 access points (ideally we would like to have 10s – 100s of access points spread across a large area) - Limited to 1 client - Bluetooth Adapters limited to one connection at a time. Hardware limitation can be resolved with industrial BT access points

Constraints (cont) Client software, different sdk for different phones. Client software, different sdk for different phones.

Difficulties Interface with JSR-82 Interface with JSR-82 Use bluecove java lib Use bluecove java lib Hardware requirements, not enough to test with Hardware requirements, not enough to test with No solution No solution Java can not detect range and signal strenght – Java can not detect range and signal strenght – lower level languages lower level languages AP overlapping while testing AP overlapping while testing Make sure no AP’s overlap Make sure no AP’s overlap

Demo