1 / 26

Design and Prototype of intelligent Guard against Disasters (iGaDs)

Design and Prototype of intelligent Guard against Disasters (iGaDs). Advisor: Jane W.S. Liu Student: Wei-Pei Liao. Motivation. Advances in disaster detection/prediction technologies  Faster and more precise disaster information. 台灣地震速報系統. Earthquake Early Warning (EWW) in Japan.

latona
Download Presentation

Design and Prototype of intelligent Guard against Disasters (iGaDs)

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. Design and Prototype of intelligent Guard against Disasters(iGaDs) Advisor: Jane W.S. Liu Student: Wei-Pei Liao

  2. Motivation Advances in disaster detection/prediction technologies  Faster and more precise disaster information 台灣地震速報系統 Earthquake Early Warning (EWW) in Japan

  3. Motivation Maturity of Information Communication Technologies Make information handy for everyone

  4. Motivation According to Red Cross, major natural disasters killed more than 300 thousands people and caused estimated 123 billions US dollars damage in 2010. (Highest yearly death tolls of the decade!!!)

  5. Contributions intelligent Guard against Disasters (iGaDs) iGaDs are systems/devices/applications that can • Receive standard-conforming alerting messages • Process and take corresponding actions  Provide more time to prepare for disasters My work on iGaDs includes: • Use scenarios for iGaDs • Architecture of iGaDs • Prototypes of iGaDs (Embedded Linux and Smartphone)

  6. Related Works • [1] European Telecommunications Standards Institute (ETSI) technical specification, Emergency Communications (EMTEL); European Public Warning System (EU-Alert) using the Cell Broadcast Service • [2] Fire and Disaster Management Agency, http://www.fdma.go.jp/en/, and briefing of J-Alert (Japanese) • [3] CAP: Common Alerting Protocol, V1.2, http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.html • [4] CAP-EAS Implementation Guideline, CAP-EAS Industry Group, May 2010 • [5] Commercial Mobile Alert System (CMAS), http://www.fcc.gov/guides/commercial-mobile-alert-system-cmas • [6] National Weather Radio Specific Area Message Encoding (SAME) System Specification, http://www.nws.noaa.gov/directives/sym/pd01017012curr.pdf • [7] X-10 Communications Protocol and Power Line, http://www.x10pro.com/pro/pdf/technote.pdf • [8] Universal Powerline Bus (UPB) Version 1.1, http://www.smarthomeusa.com/Common/UPB/UPBdescription.pdf • [9] XML DOM, http://www.w3schools.com/dom/default.asp • [10] E. C. Chee, E. Mohd-Yasin, A. K. Mustaph, “RBStrex: Hardware XML parser for embedded systems,” International Conference for Internet Technology and Secure Transaction, 2009. • [11] B. Peuschel, W. Schäfer, "Concepts and implementation of a rule-based process engine", Proceeding of ICSE '92 Proceedings of the 14th international conference on Software engineering, pages 262 - 279 • [12] C. Choi, et al., “MiRE: a minimal rule engine for context-aware mobile devices,” Proceedings of the 3rd International Conference on Digital Information Management, November 2008 • [13] Japan disaster Mitigation and prevention information XML format (JMX) is in operation!, April 2011

  7. Standard-based Alerting Message • Common Alerting Protocol (CAP) • North America (USA, Canada) • IPAWS, Open standard, XML format • Japan disaster Mitigation and prevention information XML format (JMX) • Japan • J-Alert(全国瞬時警報システム) • Standard of EU-Alert • Europe • European Public Warning System

  8. Emergency Alert System • Part of IPAWS • National TV/radio warning system in USA • Specific Area Message Encoding (SAME)Common Alerting Protocol (CAP) • Similar to Commercial Mobile Alert System(CMAS) CAP messages

  9. Smart Home and Smart Building CAP messages X-10, Universal Powerline Bus (UPB)

  10. XML Parsers Document Object Model (DOM) Simple API for XML (SAX) CAP specific: CAP Library (Java), RCAP (Ruby) General purpose: libxml2 (C/C++), XML::Parser (Perl), NSXML(Obj-C),SAXParser (Android Java SDK), LINQ to XML (C#) SimpleXML(PHP), XML.ObjTree (JavaScript)

  11. Rule Engines Main_Program { ... } • Match fact and rules • Change program behavior without recompiling code • Change program behavior by editing rules • Used in many commercial business system • Open source rule engines: Drools (Java), JESS (Java), CLIPS, PHP Business Rules (PHP), JSRulez (JavaScript),Logician, MiRE (Embedded system) if (A) { then do something } if (B) { then do something } if (C) { then do something } …… // More if statements Rule Engine Rules

  12. Common Alerting Protocol v1.2 An open standard alerting message format designed for : • Both human readable and machine readable (XML format) • Automatically generated by sensors and send to information systems • Exchange between emergency information systems • Backward compatible to SAME(Specific Area Message Encoding) • Broadcast to general public through all possible communication path CAP is the standard in North America now (USA and Canada)

  13. CAP Message Delivery in USA

  14. Alert xmlns: … Sender: Central Weather Bureau Status: Actual MsgType: Alert Scope: Public Info Category: Geo Event: Earthquake Urgency: Immediate Severity: Strong Certainty: Observed Description: A strong earthquake measuring 7.2 occurred in … Parameters: Magnitude, depth, … Areas: Polygons specifying affected areas Resources: … … A Future Scenario

  15. ?xmlns version = “1.0” • <alert xmlns = … • … • <event>Earthquake</event> • <urgency>Immediate</urgency> • <severity>Strong</severity> • <certainty>Observed</certainty> • … • <parameter> • <valueName>Magnitude • </valueName> • <value>7.2</value> • </parameter> • … • <area> • <circle>32.9525 -115.5585 • 0</circle> • </area> • … ?xmlns version = “1.0” alert xmlns = … … <event>Earthquake</event> <urgency>Immediate</urgency> <severity>Strong</severity> <certainty>Observed</certainty> Alert extraction Alert extraction Action activation rule evaluation Action activation rule evaluation Device interface Device interfaces Elevator controller i GaDs An earthquake of magnitude 7.2 hits. Your area is safe now. Stay calm and … Elevator in normal building: (Event == Earthquake) AND (Magnitude >= 6) Elevator in Taipei 101: (Event == Earthquake) AND (Magnitude >= 7)

  16. General Architecture of iGaDs Device location Resources Affected areas Rule processor Activation parameters and rules Rule engine Modem Alert message buffer Signature validation XML parser • CAP Message Processor • Receives and authenticates CAP messages • Extracts needed information from CAP messages • Device Controller • Matches rules with extracted information and local sensor data by rule engine • Filters out messages not in affected areas • Controls devices according to matched rules CAP Message Processor Alert type & information Alert records Location filter Configuration files Device Controller Local data Device interfaces

  17. Prototypes of iGaDs Device location Resources Affected areas Rule processor Activation parameters and rules Rule engine Modem Alert message buffer Signature validation XML parser • CAP message publisher • Embedded Linux • Smartphone App CAP Message Processor Alert type & information Alert records Location filter Configuration files Device Controller Local data Device interfaces

  18. iGad CAP Message Publisher • Perl: Good for text processing • PubNub cloud service CAP Publisher CAP_PUBLISHER 1.capMsg ← Read a CAP file 2.capMsg ← Remove ‘\n’ in capMsg 3.Connect to PubNub cloud 4.Call publish() to push capMsg END

  19. iGaDs (Embedded Linux) CAP messages FirendlyARM Mini6410

  20. iGaDs (Embedded Linux) • PHP • SimpleXML, PHP Business Rules IGADS_LINUX 1.Connect to PubNub cloud and wait for message 2.capMsg ← Receive a CAP message from PubNub 3.Fork a process to run IGADS_LINUX 4.capDOM ← Call SimpleXML, convert capMsg to a DOM object 5.capDOM ← Extract Event, Parameters from capDOM 6.capDOM ← Load and add sensor data (local data) 7.Call FUNCTION RULE_ENGINE(capDOM) 8.Go back to 1. END FUNCTION RULE_ENGINE( capDOM ) 1.RE ← Create PHP Business Rule Engine Object 2.RE reads and parses rules from file 3.Insert capDOM to RE 4.Call RE->fireAll() to start rule matching END

  21. iGaDs (Smartphone App)

  22. iGaDs (Smartphone App) • jQuery Mobile and JavaScript (PhoneGap) • XML.ObjTree, JSRulez IGADS_SMARTPHONE 1.Connect to PubNub cloud and wait for message 2.capMsg ← Receive a CAP message from PubNub 3.capJS ← Call XML.ObjTree convert capMsg to a JavaScript object 4.capJS ← Extract Event, Parameter from capJS 5.Call RULE_ENGINE(capDOM) 6.Go back to 1. END FUNCTION RULE_ENGINE( capJS ) 1.RE ← Create JSRulez Rule Engine Object 2.RE reads and parses rules from file 3.Insert capJS to RE 4.Call RE->runAll() to start rule matching END

  23. Rule Format rule “Earthquake” priority=1 context Parameter $param if $param->event == ‘Earthquake’ && $param->valueName == ‘Magnitude’ && $param->value >= 6 then $action[‘LED_Earthquake’]->do_action(); end PHP Business Rule priority: 1, condition: function(cap){ return cap.event === “Earthquake” && cap.valueName === “Magnitude” && cap.value >=6 } action: function() { window.alert(“Huge earthquake coming!”); } JSRulez

  24. Demo Video

  25. Summary • iGaDs are systems/devices/applications receives standard-based alert messages and respond by corresponding actions for better preparation to disasters • iGaDs have flexible architecture and fit different situations and environments • Two proof-of-concept prototypes are implemented

  26. Thank You

More Related