1 / 23

Blue Tears Project

Blue Tears Project. Bluetooth Tracking: Distributed Information Systems. Introduction. Bluetooth tracking system Approximate tracking BT is limited to a 10m radius Transfer rate 3mb/s 90% of current cell phones & smartphones have Bluetooth tech built-in.

moira
Download Presentation

Blue Tears Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Blue Tears Project Bluetooth Tracking: Distributed Information Systems

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

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

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

  5. The Approach • Other tracking system use two way communication between client and server • Some send request to find current location only • Fairly simple, loss a lot of 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)

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

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

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

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

  10. Closest Neighbour Access Point n Access Point 3 Access Point 2 Access Point n’ Access Point 1 ap5 ap4

  11. Object Diagram Server Manager mySql ManagerInterface interfaces RMICommunication AccessPoint Interface Access Point 1 Access Point n ……..... Client 1 Client n ….

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

  13. Bluetooth Init Access Point • Client would registry their Bluetooth device, usually cell/smart phone • Client sets device to discovery for a minute and wait for conformation • Ap continues checking for new devices • Once discovered is then search to see what services as available • This could take upwards to 30 – 90 secs depending on demand and device transfer rate

  14. Bluetooth Init Access Point • Once the Ap gathers all the required information a update is sent to the Server using rmi communications • Ideally you need to register only once and your Bluetooth address is stored for future use

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

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

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

  18. Assumptions • The client is not sprinting across the Bluetooth Access points • Client within a access point range at all times • Access points don’t overlap (due to java constraints) • Bluetooth address attributes is not altered during the session • Access points are mapped by installer

  19. Crashes • No failsafe for failed AP • Possible solution then your fucked • Server fails • Possible solution cluster environment • Leader algorthim (AP fitted with central server services and fights for control)

  20. Bluetooth specs • 10 meters radius • Transfer 3mb/s • One tenth the power used for WIFI • Limited connection, 7 connection on home Bluetooth adapters • Industrial BT AP up to 24 connection

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

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

  23. Limitations -

More Related