common alerting protocol Archives — LIRNEasia


Join us at the CAP Code-fest REGISTER NOW   IT Industry teaming with Emergency Management Experts to experimentaly develop exciting warning/alerting software solutions. ANYONE CAN JOIN the CAP Code-fest and it is Free to Attend. Experiment with interchanging warning/alerting information with disparate software solutions and then build new interfaces between them. Play with various domain specific software designs, XML-based interoperable data structure, information interchanging Application Programming Interfaces (OData APIs), Databases, or simply be a Lurker and give a helping hand with researching concepts. A fun activity with outcomes expected to contribute towards IT tools in SAVING LIVES.
JOIN US IN SRI LANKA – Indian Ocean Tsunami 10th Year Anniversary (IOTX) – CAP WORKSHOP DOWNLOAD THE CAP WORKSHOP FLYER These are exciting times for alerting enabled by the Common Alerting Protocol (CAP) standard (ITU-T Recommendation X.1303), especially as major online media and technology companies continue their support and promotion of CAP. One theme is the emergent support for CAP-enabled alerting through advertising by online media. In that vein, we expect this Workshop will discuss the development of harmonized design guidelines for such emergency alerting, perhaps including aspects such as colours, fonts, languages, and sets of symbols. Earthquake and volcano alerting are also expected to be Workshop topics, as well as updates on progress for some of the many CAP implementations already in production and others in active development.

Symbols in Alerting

Posted on May 14, 2013  /  0 Comments

I had a dream once – I was walking along a river in China and then an audible alarm emitting from my mobile phone got my attention. When I looked at the screen, surprisingly, a symbol with a red border showing rising water and a human figure running uphill towards shelter, was displaying. Later I realized, being illiterate in Mandarin, a text message would have done me no good. However, the symbol made perfect sense. It was an immediate threat of a sudden-onset flash flood (possibly caused by a damn burst).
Telcos are consciously gearing up to with stand the “flash-crowd” New Year’s Eve SMS loads. Pushing the SMS loads at the mean time of 00:00:00 plus or minus a minute is stressful. SMS Controllers (SMSC) have to handle the massive burst. How does this relate to mass alerting? LINREasia’s thinking, the same as the Sri Lanka Disaster Management Centre (DMC), has been, “if we can do it for tsunamis (meaning tsunami warnings), the we can do it for the rest (i.
The International Telecommunications Union – Development (ITU-D) sector recruited me to introduce ways in which the Common Alerting Protocol (CAP) interoperable emergency communication standard could be operationalized in the region. The audience comprised member state delegates from their respective telecommunications regulatory authorities and their emergency operations centres (or disaster management centres). The workshop: “Use of Telecomunications/ICT for Disaster Management” took place in Bangkok, Thailand; 20-23 December 2012. First, “CAP essentials” were introduced to the participants and then the policy and procedural steps for operationalizing CAP in one’s own country were explained. Thereafter, the participants assembled in to groups to experiment with the Sahana CAP- enabled Messaging Broker (SAMBRO).
LIRNEasia’s thinking, right along, has been, if one is prepared to appropriately warn of rapid onset tsunamis then they are quite ready for all-hazards. Then why did the already established warning centre fail on 2011 November 21. Preparation, Warning, and Response are three linked components of the Disaster Management life-cycle common to all-hazards. Development of systems for those three components in relation to tsunami warnings can be extended to all-hazard early warnings. Question is “how does one extend those capabilities to avoid missing deadly alarming events beyond tsunamis such as the 2011 November 21 Matara Mini Cyclone as well as reduce the false warnings?
Patrick Gannon (President & CEO, Board Director at OASIS), in an email, “You provide some very interesting information on the open source Sahana effort and examples of using citizen volunteers for disaster situation reporting. The issue is being highlighted in the 2012 CAP workshop FINAL REPORT.” Get more details on the voice-enabled alerting and situational reporting project from the video: “Do you hear me?” The Common Alerting Protocol (CAP) community has nick named us “CAP early adopter” (lol & \0/). This is because in 2005 when the CAP content standard was first released, LINREasia was quick to test it in the HazInfo project.
Every where Government agencies are territorial and fear losing their budgets and ability to stand ground. Therefore, choose to work as a silo with less lateral integration. Such structures are ineffective and lead to irresponsible behaviour at the expense of causing havoc on the citizens. Time and time again we hear of the shortcomings arising from unplanned and ad-hoc procedures carried out in the presence of hazard events. The past experience being the 2012 April 11 Sumatra earthquake.
Our findings from the recently concluded Interactive Voice-enabled alerting and situational reporting pilot revealed that Speech-To-Text and Text-To-Speech were impossible to apply with audio over low quality transmission networks (listen to this audio to get a sense how bad it can be). One could sample at much higher frequencies then that produces an extremely large mega byte file which may take hours to multi-cast; hence, not recommended for critical life-saving communications. Our conclusions drawn were mainly on the situational reporting functions. The U.S.
The usefulness and ease-of-use of interactive voice, with Freedom Fone, for Sarvodaya Community Emergency Response Team (CERT) members to supply incident information was blogged two weeks back. Now the question is “how is all that information put to use in responding to those incidents?”. In here we tell parts of that story. CERT members call one of the four telephone numbers to access Freedom Fone; then press the “reporting” menu item number on their phone keypad to record a “field observation report”.
We conducted controlled-exercises, with Lanka Jathika Sarvodaya Shramadana Sangamaya (Sarvodaya) Hazard Information Hub (HIH) Operators and Community Emergency Response Team (CERT) members. The HIH data center is in Moratuwa. The study using interactive voice, field tested the technology in  Colombo, Matara, Nuwara-eliya, and Ratnapura Districts. Figure to the left shows an average ease-of-use of 3.95 and usefulness of 4.
In our current emergency communication research aiming to enable interoperability between Freedom Fone and the Sahana Disaster Management System for disseminating Common Alerting Protocol messages and receiving Situational Reports over voice channels, we came a cross the situation where the 2N UMTS modem license had silently expired. During our silent-test this weekend, in preparation for a drill this week, we noticed that the license had abruptly expired. Unaware of the licensing dependency, the Sarvodaya Hazard Information Hub staff were scratching their heads trying to figure out what had happened. Even though the problem was identified, given that it is the weekend, getting any immediate support from the vendor is questionable. This project: FF4EDXL follows from LIRNEasia’s HazInfo and Biosurveillance research.

Voice for alerting and response

Posted on August 9, 2011  /  0 Comments

Why voice for Sarvodaya’s emergency communication? The experience from the 2011 Foods in Batticaloa and Ampara districts was that Sarvodaya was able to secure aid from various sources by providing the actual ground situation through their web portal. It had images and information of rescue operations, victims, camps, and the devastation. The images and stories came from Sarvodaya head office staff who were deployed to the area. They used cameras, phones, and the internet to relay the ground situation to the Hazard Information Hub (HIH).
Does this picture remind you of the default Windows XP desktop background? That’s what most of Mongolia looks like. Roughly 40% of the Mongolians live in Ulaanbaartar (UB). The rest are sparsely scattered in thinly populated communities in the vast open terrain. The cultures vary across the desert, meadows, and hills.
I had the opportunity attend the discussion by Tim Berners-Lee and Gordon Brown in Geneva, speak on the “future of the web“, a public lecture hosted by the Université de Genève, April 06, 2011. The two discussants didn’t have anything new to share; they were talking the same language of tapping in to the untapped through mobile phones; nothing new to LIRNEasia (see our Teleuse at the Bottom of the Pyramid studies). The WWW Foundation has realized the reach of the mobile phone to deliver the web to those 80% that have not yet been exposed. What we were more eager to hear was the defense on the claim that the “web is dead, long live the internet“. In defense – “No the web isn’t dead” with the success story pointing to the Wikipedia.
Those who know graphs theory are familiar with the “four color theorem“; an example being the world map (relaxed as a planar graph) can be colored with a minimum of four colors such that two countries sharing a border do not share the same color. Researchers at Queen Mary University of London use this theorem to color code cellular network base stations. The base stations are in abstract sense regarded as message Brokers (also termed as “Publisher Subscriber Message Oriented Middleware” – PSMOM) that channel the published message (SMS, Email, Voice packet, data packets, etc) to the Subscriber (or message recipient). Sometimes a subscriber and a publisher can be directly linked through a single broker or they may be linked through several intermediary brokers. The role of the Sahana Alerting Broker, essentially, is similar to that of a cellular base station; where decision-maker or decision-system published risk information is disseminated to the subscribers of the response systems in the form of public warnings or restricted and private alerts (also known as closed user group alerts typically applicable to first responders).