1 / 25

<<Technical Report>> Live E! Project in DUMBO

<<Technical Report>> Live E! Project in DUMBO. Hideya Ochiai, Hiroshi Esaki (The University of Tokyo) Satoshi Matsuura, Masato Yamanouchi, Hideki Sunahara ( NARA Institute of Schience and Technology ). DUMBO Technical Report. Review Architecture Implementation Evaluation Suggestion.

sierra
Download Presentation

<<Technical Report>> Live E! Project in DUMBO

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. <<Technical Report>> Live E! Project in DUMBO Hideya Ochiai, Hiroshi Esaki (The University of Tokyo) Satoshi Matsuura, Masato Yamanouchi, Hideki Sunahara ( NARA Institute of Schience and Technology )

  2. DUMBO Technical Report • Review • Architecture • Implementation • Evaluation • Suggestion

  3. DUMBO Review • An Event of Emergency OLSR Network • Laptops and PDAs • OLSR Node on Elephant • Application • Text Messaging • Video Communication • Elephant is a rescue partner in Thailand • Especially in Phuket • Elephants supported the rescue after the TSUNAMI disaster on 26th Dec in 2004.

  4. DUMBO Architecture • Two MANET sites (Disaster area) in Phuket • Head Command Center at AIT in Bangkok • These three networks were connected in L2 level by satellite links. Bangkok Phuket

  5. Live E! Architecture in DUMBO • Server Client Model (no resolution service) • Data centric system • Two kinds of sensor nodes • IP Routing-Based • Application Routing-Based (Proxy-Based)

  6. <<Architecture>>IP Routing Based Sensor Node (Node A) MANET (OLSR) 192.168.1.0/24 Sensor Unit 192.168.1.184/24 192.168.1.182/30 192.168.1.181/30 Subnet (Wired) 192.168.1.180/30 OLSR Node HNA 192.168.1.180/30

  7. <<Architecture>>Proxy Based Sensor Node(Node B) MANET (OLSR) 192.168.1.0/24 Sensor Unit 192.168.1.185/24 10.0.0.2/24 App Proxy Private Network 10.0.0.0/24 10.0.0.1/24 OLSR Node Sensor Data Proxy +

  8. Implementation • Live E! Data Server • IP Routing Based Sensor Node (Node A) • Proxy Based Sensor Node (Node B) Wireless AP OpenWrt (OLSR Node) Battery 16V 4800mAh DC-DC Converter 16V  3.3V Vaisala (WXT510) Armadillo

  9. Deployment (Node A)

  10. Deployment (Node B)

  11. System Differences between Node A and Node B • Node A == Hongo System (Ochiai) • Node B == NAIST System (Matsuura, Yamanouchi) • Implementation • Node A == BufferoAP (low spec) & OpenWrt & Armadillo • Node B == T43 (high spec) & Windows & Proxy • Deployment • Node A == in Jungle • 2 or 3 hops to the server • Node B == near the satellite modem. (because of power supply) • 1 hop to the server

  12. Evaluation • Load & Performance • Data Upload Stability • Sensor Data Availablity

  13. <<Evaluation>>(Load & Performance) @ 20 nodes Node A Routing Table Node B Routing Table

  14. <<Evaluation>>(Data Upload Stability Node A)

  15. <<Evaluation>>(Data Upload Stability Node B)

  16. <<Evaluation>>(Data Upload Stability Node A)

  17. <<Evaluation>>(Data Upload Stability Node B)

  18. Sensor Data Graph (Node A) Temperature Humidity WindDir Pressure RainFall WindSpeed

  19. Sensor Data Graph (Node B) Temperature Humidity WindDir Pressure RainFall WindSpeed

  20. Suggestions for those who are interested in... • Under MANET • Severe Condition • High packet loss • Low performance • Roughly connected • Characteristics on communication • Less transaction is better. • “Local Transaction” is better than “Long Reach Transaction”. • End-to-End Communication • End-to-End Reliability vs Hop-by-Hop Reliability • Contents Dissemination or Message Distribution • Single vs Multiple • “Make a Map” vs “Act first” (“Make a routing table” vs “Broadcast”)

More Related