Autonomous Rechargeable Sensor Network Simulator

1. Autonomous Rechargeable Sensor Network Simulator Volodymyr Pryyma and Mustafa Ilhan Akbas University of Central Florida Orlando, FL

2. Overview • Introduction • Rechargeable Sensor Network • Project Information • Design Issues • Testing Scenarios • Simulation Results • Demonstration • Conclusion

3. Introduction • Miniaturization • Smaller sensors • Lower energy consumption • Micro-sensors • Very small devices • Limited functionality/resources • Rechargeable

4. Introduction • Applications • Various military operations • Natural disaster monitoring/recovery • Rescue operations • Simple environment monitoring • Need for autonomous architecture

5. Introduction • ANSWER • AutoNomouS netWorked sEnsoR system • Developed by Dr. Olariou et al. • Self-organizing architecture

6. Rechargeable Sensor Network • ANSWER Architecture • Large number of micro-sensors • A number of AFNs • Single mobile node • Unique dynamic coordinate system

7. Rechargeable Sensor Network • Dynamic coordinate system • Concentric coronas • Centered at training agent (TA) • Equiangular wedges • Self-organization • Easy clustering

8. Rechargeable Sensor Network Dynamic coordinate system

9. Rechargeable Sensor Network Communication schemes

10. Rechargeable Sensor Network • Coloring scheme • Coronas are further subdivided • Each node has a specific color • Colors are assigned based on signal strength • Allows for activation of nodes in subsets

11. Rechargeable Sensor Network Coloring scheme

12. Rechargeable Sensor Network Micro-sensor states

13. Current & Proposed System • Current System • No simulator is available to test performance of ANSWER • No rechargeable node concept • Our contribution with the simulator • Addition of rechargeable sensors • Performance evaluation rechargeable vs. non-rechargeable

14. Components of the System • The system is basically the simulator • Various scenarios can be created by • Different number of threat nodes with different movement patterns • Different number of micro-sensor nodes • Different number of AFNs • Different movement patterns for the mobile node

15. Expected Impact • Effective simulations of ANSWER • Improved system analysis by various simulations • Effective simulations for future research by add-ons or changes to the simulator

16. Project Management • Reference Documents • Papers related to ANSWER & YAES • Papers related to rechargeable sensors • Applicable Standards • Reusable Modules: YAES • Coding: Java • Version Control: SVN

17. Life Cycle & Tools • Process of Iteration • Incremental Approach • Specification is developed in conjunction with the software • More important services are given higher priority • Tools • YAES, Java, Eclipse, Internet Browser • Environment • Windows 2000/XP

18. Team • Project Team Organization • No hierarchy, equal work division, team control • Work is divided into two as programming and the rest • Project Team Communication • Laboratory meetings • E-mail • Phone

19. Risk Management • Technical Risks • Minimized development risk by working with familiar tools • Diverse testing scenarios • Reviews at each design increment • Project goals • Milestones

20. Testing • Modular tests • Full scenario tests • Documented bugs/errors • Regression testing

21. Requirements • The software is designed to simulate a specific network architecture • No required special training for using the software. The developers' manual may include an introduction to YAES • The simulation is to run reliably on any platform and OS supported by the Java Virtual Machine

22. Design Issues • Reusability • The program was developed in YAES which is developed in an OO fashion • Developed classes can be reused for future version or different application • Addition of future testing scenarios • Maintainability • Modular fashion of the design allows better maintainability • Individual parts of the program can be optimized or modified while maintaining the rest of the code

23. Design Issues • Portability • The program uses YAES Java libraries to run the simulation code • The whole program or any separate module can be ported to other YAES applications • Testability • OO structure of the code allows us to test and validate each class individually • Testing/Debugging were done continuously during the project

24. Testing Scenario • Scenario example: • Ten mobile threat nodes • Set to move randomly • 200 micro-sensor nodes • 6 AFNs • Mobile node • Move from top left corner to bottom right

25. Simulation Results • Metrics • Avg. failures vs. number of nodes • Avg. failures vs. mobility • Avg. energy consumption vs. number of nodes • Avg. energy consumption vs. mobility • Comparisons • Rechargeable vs. non-rechargeable nodes

26. Simulation Results Avg. failures vs. number of nodes

27. Demonstration YAES Screenshot

28. Conclusion • Simulator successfully works • ANSWER • Provides reliable architecture • Better results with dense network • All scenarios had similar results • Simulator • Portable across many platforms • User friendly • Modular design (easy to add scenarios)

29. Questions?