Supervisor: Mr. Hai Vortman

1. Supervisor: Mr. HaiVortman

2. The ultimate goal • Creating a wireless sensor network using Bluetooth technology.

3. The project Goals • Developing software for the sensor and for the server. • Developing a work area in order to testing various wireless network protocol such as Gradient Algorithm PIF,CT3 and CT2. • Testing our WSN using several computers and comparing reliability with the expectation. • Suggesting solutions to save energy using this kind of already very low power sensor consumers.

4. Why our project is very interesting • Practical • Very low effort for usage in real system simulation • Can be used from labs that would like to test any event detection system. • Can be easily developed for other devices such as (mobile)

5. Overview • The Bluetooth Special Interest Group was founded in September 1998. • The SIG has more than 11,000 member companies. • Last decade:1.5 billion Bluetooth enabled devices have been shipped. “The first ten years of Bluetooth development has been amazing to watch,” said Michael Foley, Ph.D., executive director, the Bluetooth SIG. “From prototypes in 1998 to more than 1.5 billion devices on the market today, no other consumer technology has grown as fast in such a short period of time.”

6. Bluetooth Stack

7. Bluetooth Piconet and Scatternet

8. Bluetooth + and - • Advantages: • Power ! • Commonness : more than 1.5 billion Bluetooth devices. • Low cost. • Disadvantages: • Little bandwidth • Low Security • The network is constructed from several piconets. Each piconets compound from master & up to 7 slaves.

9. BT vs. Wi-Fi • Wi-Fi differs from Bluetooth in that it provides higher throughput and covers greater distances, but requires more expensive hardware and may present higher power consumption. • Wi-Fi enables a faster connection, better range from the base station, and better security than Bluetooth although….

10. WSN Technology • A wireless sensor network (WSN) is a computer network consisting of distributed autonomous devices using sensors to detect events and spread data. • There are several main obstacles that need to be overcome before when designing a wireless sensor network: • Energy. • Computation • Communication

11. Wireless Sensors Network Tradeoff • Usually the main trade-off that are taken under consideration when designing a wireless sensor networks is between energy and communication overhead saving in every routing solution.

12. WSN – our implementation • Basic constrains: • A unique Base Station • Can be any number of sensors • Message sent only one way • Maximum sons (7) - (Hardware constrain)

13. State machine for BS

14. State machine for sensor

15. Initialization F ∞ A ∞ D ∞ G ∞ B ∞ BS 0 E ∞ C ∞

16. Initialization F ∞ A ∞ D ∞ G ∞ B ∞ BS 0 E ∞ C ∞

17. Initialization F ∞ A ∞ D ∞ G ∞ B ∞ BS 0 E ∞ C ∞

18. Initialization F ∞ A 1 D ∞ G ∞ B 1 BS 0 E ∞ C 1

19. Initialization F ∞ A 1 D 2 G ∞ B 1 BS 0 E ∞ C 1

20. Initialization F ∞ A 1 D 2 G ∞ B 1 BS 0 E ∞ C 1

21. Initialization F ∞ A 1 D 2 G ∞ B 1 BS 0 E 2 C 1

22. Initialization F ∞ A 1 D 2 G ∞ B 1 BS 0 E 2 C 1

23. Initialization F 3 A 1 D 2 G ∞ B 1 BS 0 E 2 C 1

24. Initialization F 3 A 1 D 2 G 3 B 1 BS 0 E 2 C 1

25. Initialization F 3 A 1 D 2 G 3 B 1 BS 0 E 2 C 1

26. Detection transmission F 3 A 1 D 2 G 3 B 1 BS 0 E 2 C 1

27. The System • System Requirements (briefly ) • The Sensor entity (henceforth called the system) is a software application responsible to implement a pre-defined state machine in order to enable event identification and reliable communication with other sensors entities. • Such a system could be very useful and helpful in buildings security and administration, army systems, event propagation systems etc…

28. System Context • The system will run on every machine that has the following requirements: • 512K minimum of total memory available • Bluetooth wireless network connection • Compliant implementation of the J2ME Connected Limited Device Configuration • The system shall provide a GUI for controlling and configuring each sensor.

29. Functional Requirements • Communication • The application should be able to gathering data on the environment and decide his responsibilities. • The application should be able to receive information from the slaves and transfer to the master/server and vice versa. • The application should check for new potential connection from time to time. • Given an event the application should transmit it to his master.

30. …. Continue… (Functional Requirements) • Event Detection • The software should be designed independently from the kind of event.

31. …. Continue… (Functional Requirements) • Environment changes support • The system should be able (considering that is possible) to rebuild itself in case of environment “little” changes: • Example: some sensors stop working. Note: The system is not design for support a moveable network.

32. Software component

33. Demonstration…..

34. Disconnection case Two different approach • The device is not always connected. That means that there is a check from time to time + a transmission that can reveal a failure(Power saving) • The device is always connected so that the failure is in reveal in real time.(Better for demonstration and less time to rebuild the network)

35. Future possible implementation • Implement other kind of WSN algorithms: PI (Routing via Broadcast),PIF • Implementation of Connectivity Test algorithms: CT2, CT3 • System improvement • Usage of more than one BS • Ranking system improvement • Mobile adaption

36. Thank you