Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Responsive Alert Delivery over IP Network Yi-Zong Ou Institute of Information Science Academia Sinica, R.O.C (Taiwan) C. M. Huang, C. T. Hu, E. T. H. Chu, C. S. Shih, J. W. S. Liu CPSNA-2013 Taipei,Taiwan, August 19-20th Imagine that… Earthquake 7.0 2 iGaDs and Qpid CAP message Authorized alert sender Broadcast pathways ?xmlns version = “1.0” <alert xmlns = … … <event>Earthquake</event> <urgency>Immediate</urgency> <severity>Strong</severity> … <parameter> <valueName>Magnitude </valueName> <value>7.3</value> </parameter> … PuSH PuSH IP Network Message processor iGaD Action activation rule evaluation Device interface iGaD PuSH To diverse devices: Gas regulator, door or windows controller…… iGaD Qpid Service Network Client Client Qpid Broker Qpid Broker Qpid Broker Qpid Broker PuSH Qpid Broker Qpid Broker Client PubSubHubbub (PuSH) A server-to-server web-hook-based Pub/Sub protocol as an extension to Atom and RSS (topic: feed URL). The subscriber subscribes to the Topic URL from the Topic URL's declared Hub(s). Publisher Announce new alert Ping Data Push Subscribe notification Alert PuSH subscribers Information Message Hub Fetch data Subscriber Notifications Update! 5 Qpid Apache Qpid™ is a cross-platform Enterprise Messaging system which implements the Advanced Message Queuing Protocol (AMQP) Prioritized message delivery Feasible use to restore network during disaster. Messages with routing key Exchange Bindings Queues Priority queues Decreasing Priority Earth -quake Debris Tsunami Flow 6 PQ Node Notification to local subscribers Hub Requests from publishers PubSubHubbub Data Bridge Downstream data Upstream data Cached data Messages from other Qpids Exchange Priority Queues Messages to other Qpids Bindings Decreasing Priority 7 PQ Node – Downstream Requests from publishers Notifications to local subscribers Hub Data PubSubHubbub Data Update Monitor (DUM) Work item (Earthquake) Call DataBridgeNotifyDataUpdate( Highest Topic,RelativeDeadline, ...); Priority Data Transfer Service (DTS) Data Bridge data Data Exchange High Priority Queues Low Bindings Route to other Qpids Decreasing Priority 8 PQ Node – Upstream Notifications to local subscribers Hub PubSubHubbub Data Retrieval Service (DRS) Work item Messages from other Qpids Data Priority Queues Cached Data High Incoming Data Monitor (IDM) Register long pollsLow Data Bridge Route to other Exchange Qpids Bindings Decreasing Priority 9 Sequence of interactions and End-to-end delay Local Subs Data Bridge Publisher Hub DUM DTS Ping DRS IDM Qpid Other Qpids Long poll Request Data Push data Push data Notify Notify Downstream Data Data Upstream 10 Sequence of interactions and End-to-end delay Local Subs Data Bridge Publisher Hub Ping A1 Push data Push data DRS IDM Qpid Long poll Request Data DUM DTS Other Qpids A2 t1 Notify t4 A3 t2 Notify Downstream Data t3 Data Upstream 11 Experiment setup 12 Experiment result 0.9 0.8745 1+1 Threads Residence time 0.8 0.7 1+1 Threads Service time 0.6998 0.7601 1+7 Threads Residence time 1+7 Threads Service time Time (ms) 0.6 0.5 0.4 0.1 0.6781 0.5528 1+1 Threads Residence time 0.5840 0.4343 0.4497 0.4743 0.4760 0.4049 0.5380 0.4530 0.4923 1+7 Threads Residence time 0.5073 0.4173 0.3320 0.3853 Latency Overhead 0.3 0.2 0.6031 0.2557 0.1612 0.1847 0.2099 1+7 Threads 0.2816 Service time 0.2251 0.1247 0.1370 1K 5K 0.1575 1+1 Threads Service time 0.0 10K 25K Message size 50K 75K 100K 13 Throughput of PQ node (1+1 threads) 160 Megabyte per second 143.83 140 115.78 120 100 90.76 80 Throughput 52.82 60 40 22.98 11.79 20 2.51 Over 2000 10 KB messages per second. The throughout is more than adequate for pushing alert messages. 0 1KB 5KB 10KB 25KB Message size 50KB 75KB 100KB 14 Summary and Future work Our work provides: Asynchronous prioritized messaging delivery service over internet High throughput messages deliverer service. We will investigate: How system resources of each node are allocated to tasks that move data within the node? What are other message sources or message deliver services can adopt our middleware? 15 Thank you very much! This work is supported by the Academia Sinica, Republic of China (Taiwan) Open Information Systems for Disaster Management project. Hub Data buffer Call DataBridgeNotifyDataUpdate ( Topic, RelativeDeadline, ...); Data Bridge DTS work dispatcher Notification events DUM DTS Work Queues Thread pool DTS Qpid Priority Queues Thread pool Topic exchange Earthquake Debris Tsunami Decreasing priorities Flow Data buffer Hub HTTP interface Data buffer Data Bridge DRS work Queues DRS IDMonitor IDM Qpid Priority Queues call Incoming data events QpidLongPollAll (QueueIdentifiers) Data buffer Earth- Debris quake Flow Tsunami Three configurations of PQ node For publishers For both publishers and subscribers For subscribers Downstream Two-way stream Upstream PuSH Hub PuSH Hub PuSH Hub Data Bridge Data Bridge Data Bridge 19