From fd434b45c1c8e6c8a91288a4f3fdd8d2807f3c0d Mon Sep 17 00:00:00 2001 From: beutel Date: Thu, 21 Jun 2007 18:23:44 +0000 Subject: [PATCH] added testbed tep draft as tep130 --- doc/index.html | 4 ++ doc/txt/tep130.txt | 162 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 166 insertions(+) create mode 100644 doc/txt/tep130.txt diff --git a/doc/index.html b/doc/index.html index bf256ffa..155ac2e9 100644 --- a/doc/index.html +++ b/doc/index.html @@ -108,6 +108,10 @@
  • TEP 124: Link Estimation Exchange Protocol (LEEP) [HTML] [TXT]
  • TEP 125: TinyOS 802.15.4 Frames [HTML] [TXT]
  • TEP 126: CC2420 Radio Stack [HTML] [TXT]
    • +
  • TEP 127: Packet Link Layer [HTML] [TXT]
    • +
  • TEP 128: Platform Independent Non-Volatile Storage Abstractions [HTML] [TXT]
    • +
  • TEP 129: Basic Platform Independent Non-Volatile Storage Layers [HTML] [TXT]
    • +
  • TEP 130: Testbeds - Setup and Interfaces [HTML] [TXT]


    • diff --git a/doc/txt/tep130.txt b/doc/txt/tep130.txt new file mode 100644 index 00000000..c353b21a --- /dev/null +++ b/doc/txt/tep130.txt @@ -0,0 +1,162 @@ +================================= +Testbeds - Setup and Interfaces +================================= + +:TEP: 130 +:Group: Testbeds Working Group +:Type: Documentary +:Status: Draft +:TinyOS-Version: All +:Author: Jan Beutel + +:Draft-Created: 14-Jun-2007 +:Draft-Version: $Revision$ +:Draft-Modified: $Date$ +:Draft-Discuss: TinyOS Testbed WG > + +.. Note:: + + This document specifies a Best Current Practices for the + TinyOS Community, and requests discussion and suggestions for + improvements. Distribution of this memo is unlimited. + +Abstract +==================================================================== + +This memo describes the structure and interfaces required for TinyOS compliant +testbeds. + +1. Introduction +==================================================================== +The testing and validation of embedded code on real hardware is key to +successful development of TinyOS applications. Although popular and powerful for +high level analysis, current simulation methods lack in terms of level of +detail and accuracy when used accross multiple system layers where abstractions +and models used are inherently imperfect and impair results. Methods such as +hardware emulation commonly used in embedded system development allow the +execution of code on a hardware platform and therefore can guarantee timing but +are very limited in terms of scalability and often confined to a lab usage only. + +Sensor network testbeds try to overcome these deficiencies by allowing to execute +software code under realistic operating conditions on real hardware embedded in +a target environment. This approach allows to generate a level of detail especially +in respect to the whole system (radio. processor, storage, sensors, interfaces) +and the wireless environment (noise, fading, shading, errors, failures) while +maintaining a certain degree of scalability. Remote programming as well as a +feedback of status and debugging information from the nodes using testbed +infrastructure alleviates the need for integrated services in sensor network +applications. Additionally testbeds allow to operate a set of nodes in a +controlled environment, i.e. using temperature variations or a controlled +wireless environment. + +A typical testbed is made up of a number of nodes (?do we state amounts here?) +connected to a central resource for control and logging that are deployed in a +physical space (testing area). Typically the central resource is a server with +integrated datalogging capability. + +MISSING: Difference of a testbed vs. a desktop test (e.g. single nodes with a +programmer or a simple usb grid) + +Examples of current sensor network testbeds are MoteLab [1_] and the +Deployment-Support Network [2_]. + + +2. Testbed Usage +==================================================================== + +Modes of Operation: + +- Single Shot + +- Continuous Integration + +- Long Term Operation (Profiling) + +Other Topics: + +- Federated Testbeds (in multiple environments) + +- Access/Resource Arbitration + + +3. Testbed Services +==================================================================== + +- identification of target devices (presence, type, hw rev) +- programming of target devices +- resetting of target devices +- logging of target response +- versioning/identification of uploaded software +- identification/versioning/archiving of testing jobs + +- testbed status information +- identification of testbed services +- authentification + + +4. Implementation +==================================================================== + +- Server, DB/Storage, Interface XMLRPC + +- Connection fabric + +- On- and offline logging + +- Supplied Power + +- Mote Hardware + + +THINGS TO DISCUSS + +- ?Do we state minimum requirements? +- number of nodes +- power supply (fixed/batt) +- power profiling +- power on/off of targets? is simple reset/erasing enough? +- feedback channel capabilities (delay, errors, lost packets...) +- target control? is control of (writing to) targets required or is it an optional feature? +- scheduling of actions (time synched???) + + +5. Reference +==================================================================== + + + +6. Acknowledgments +==================================================================== + + + +7. Author's Address +==================================================================== + +| Jan Beutel +| Gloriastr 35 +| ETH Zurich +| 8092 Zurich +| Switzerland +| +| phone - +41 44 632 7032 +| +| email - j.beutel@ieee.org + +8. Citations +==================================================================== + +.. [1] G. Werner-Allen, P. Swieskowski, and M. Welsh. MoteLab: A wireless sensor + network testbed. In Proc. 4th Int'l Conf. Information Processing Sensor + Networks (IPSN '05), pages 483-488. IEEE, Piscataway, NJ, April 2005. + +.. [2] M. Dyer, J. Beutel, L. Thiele, T. Kalt, P. Oehen, K. Martin, and P. Blum. + Deployment support network - a toolkit for the development of WSNs. In Proc. + 4th European Workshop on Sensor Networks (EWSN 2007), volume 4373 of Lecture + Notes in Computer Science, pages 195-211. Springer, Berlin, January 2007. + + +Appendix A. Example Appendix +==================================================================== + +This is an example appendix. Appendices begin with the letter A. -- 2.39.2