eena.org
Open in
urlscan Pro
2606:4700:10::6816:1f4c
Public Scan
URL:
https://eena.org/our-work/eena-special-focus/public-warning/
Submission: On February 02 via api from EE — Scanned from DE
Submission: On February 02 via api from EE — Scanned from DE
Form analysis
3 forms found in the DOM<form>
<div>
<div class="nf-before-form-content"><nf-section>
<div class="nf-form-fields-required">Fields marked with an <span class="ninja-forms-req-symbol">*</span> are required</div>
</nf-section></div>
<div class="nf-form-content "><nf-fields-wrap><nf-field>
<div id="nf-field-1-container" class="nf-field-container textbox-container label-above ">
<div class="nf-before-field"><nf-section>
</nf-section></div>
<div class="nf-field">
<div id="nf-field-1-wrap" class="field-wrap textbox-wrap" data-field-id="1">
<div class="nf-field-label">
<label for="nf-field-1" id="nf-label-field-1" class=""> Name <span class="ninja-forms-req-symbol">*</span>
</label>
</div>
<div class="nf-field-element">
<input type="text" value="" class="ninja-forms-field nf-element" placeholder="Your name" id="nf-field-1" name="nf-field-1" aria-invalid="false" aria-describedby="nf-error-1" aria-labelledby="nf-label-field-1" aria-required="true"
required="">
</div>
</div>
</div>
<div class="nf-after-field"><nf-section>
<div class="nf-input-limit"></div>
<div id="nf-error-1" class="nf-error-wrap nf-error" role="alert"></div>
</nf-section></div>
</div>
</nf-field><nf-field>
<div id="nf-field-2-container" class="nf-field-container email-container label-above ">
<div class="nf-before-field"><nf-section>
</nf-section></div>
<div class="nf-field">
<div id="nf-field-2-wrap" class="field-wrap email-wrap" data-field-id="2">
<div class="nf-field-label">
<label for="nf-field-2" id="nf-label-field-2" class=""> Email <span class="ninja-forms-req-symbol">*</span>
</label>
</div>
<div class="nf-field-element">
<input type="email" value="" class="ninja-forms-field nf-element" id="nf-field-2" name="email" autocomplete="email" placeholder="Your email address" aria-invalid="false" aria-describedby="nf-error-2"
aria-labelledby="nf-label-field-2" aria-required="true" required="">
</div>
</div>
</div>
<div class="nf-after-field"><nf-section>
<div class="nf-input-limit"></div>
<div id="nf-error-2" class="nf-error-wrap nf-error" role="alert"></div>
</nf-section></div>
</div>
</nf-field><nf-field>
<div id="nf-field-11-container" class="nf-field-container hidden-container label-hidden ">
<div class="nf-before-field"><nf-section>
</nf-section></div>
<div class="nf-field">
<div id="nf-field-11-wrap" class="field-wrap hidden-wrap" data-field-id="11">
<div class="nf-field-label"></div>
<div class="nf-field-element">
<input type="hidden" id="nf-field-11" name="nf-field-11" class="ninja-forms-field nf-element" value="https://eena.org/our-work/eena-special-focus/public-warning/">
</div>
<div class="nf-error-wrap"></div>
</div>
</div>
<div class="nf-after-field"><nf-section>
<div class="nf-input-limit"></div>
<div id="nf-error-11" class="nf-error-wrap nf-error" role="alert"></div>
</nf-section></div>
</div>
</nf-field><nf-field>
<div id="nf-field-3-container" class="nf-field-container textarea-container label-above ">
<div class="nf-before-field"><nf-section>
</nf-section></div>
<div class="nf-field">
<div id="nf-field-3-wrap" class="field-wrap textarea-wrap" data-field-id="3">
<div class="nf-field-label">
<label for="nf-field-3" id="nf-label-field-3" class=""> Message <span class="ninja-forms-req-symbol">*</span>
</label>
</div>
<div class="nf-field-element">
<textarea id="nf-field-3" name="nf-field-3" aria-invalid="false" aria-describedby="nf-error-3" class="ninja-forms-field nf-element" placeholder="Your message" aria-labelledby="nf-label-field-3" aria-required="true"
required=""></textarea>
</div>
</div>
</div>
<div class="nf-after-field"><nf-section>
<div class="nf-input-limit"></div>
<div id="nf-error-3" class="nf-error-wrap nf-error" role="alert"></div>
</nf-section></div>
</div>
</nf-field><nf-field>
<div id="nf-field-4-container" class="nf-field-container submit-container label-hidden textbox-container">
<div class="nf-before-field"><nf-section>
</nf-section></div>
<div class="nf-field">
<div id="nf-field-4-wrap" class="field-wrap submit-wrap textbox-wrap" data-field-id="4">
<div class="nf-field-label"></div>
<div class="nf-field-element">
<input id="nf-field-4" class="ninja-forms-field nf-element " type="submit" value="Submit">
</div>
<div class="nf-error-wrap"></div>
</div>
</div>
<div class="nf-after-field"><nf-section>
<div class="nf-input-limit"></div>
<div id="nf-error-4" class="nf-error-wrap nf-error" role="alert"></div>
</nf-section></div>
</div>
</nf-field></nf-fields-wrap></div>
<div class="nf-after-form-content"><nf-section>
<div id="nf-form-errors-1" class="nf-form-errors" role="alert"><nf-errors></nf-errors></div>
<div class="nf-form-hp"><nf-section>
<label id="nf-label-field-hp-1" for="nf-field-hp-1" aria-hidden="true"> If you are a human seeing this field, please leave it empty. <input id="nf-field-hp-1" name="nf-field-hp" class="nf-element nf-field-hp" type="text" value=""
aria-labelledby="nf-label-field-hp-1">
</label>
</nf-section></div>
</nf-section></div>
</div>
</form>
GET https://eena.org/
<form action="https://eena.org/" method="get">
<div class="aux-search-input-form">
<input type="text" class="aux-search-field" placeholder="What are you looking for?" name="s" autocomplete="off">
</div>
<input type="submit" class="aux-black aux-search-submit aux-uppercase" value="Search">
</form>
GET https://eena.org/
<form action="https://eena.org/" method="get">
<div class="aux-search-input-form">
<input type="text" class="aux-search-field" placeholder="What are you looking for?" name="s" autocomplete="off">
</div>
<div class="aux-submit-icon-container auxicon-search-4 ">
<input type="submit" class="aux-iconic-search-submit" value="Search">
</div>
</form>
Text Content
EENA European Emergency Number Association * * * * * Home * Our work * EENA Special Focus * EENA Tech & Ops Committee * Policy & Advocacy * Certification & consultancy services * Standardisation work * AI Special Project * EU projects * Our community * Services to Members * Emergency Services * Industry * Emergency services & drones network * Researchers * Associations * Knowledge hub * Blog * Documents * Webinars * Press Releases * News * Events * EENA Events * EENA Conference * About 112 * What’s 112 all about? * Humans of 112 * Awareness partners * Awareness campaigns * Promotional material * About EENA * Mission and Vision * Meet our Team * Meet our Board * Contact & Visits PUBLIC WARNING Home » Our work » EENA Special Focus » Public Warning Share Recent terrorist attacks, natural disasters or health crises have highlighted the need for efficient Public Warning Systems. This allows public authorities to quickly alert the population and let them know of an ongoing crisis or imminent threat. TABLE OF CONTENTS * A Multi-Channel Approach * EU Legislation * EENA's stance * Strategy & planning * EENA's Support * Practical examples A MULTI-CHANNEL APPROACH Since one technology cannot instantly reach all the population, EENA believes that many different channels must be considered to maximise the chances of disseminating information to as many people as possible. Possible channels include using people’s phones, sirens, social media, TVs & radios, emails, variable message signs… You can learn more about these different channels in EENA’s document on Public Warning Systems. ALERTING THE POPULATION ON THEIR PHONES - MANDATORY IN EU LEGISLATION EENA has been advocating for the EU to mandate public alerting on phones since the early 2000s, including by supporting a Written Declaration on the matter in 2008 (see Written Declaration on early warnings for citizens). We are delighted that the European Electronic Communications Code (EECC) – which was adopted in December 2018 – makes it mandatory for all the Member States of the European Union to implement modern public warning systems. By June 2022, public authorities in all Member States must be able to send alerts to people’s phones in a determined area. Read more about how the EECC is affecting emergency communications in the EU here. Two technologies make it possible to reach everyone present in a specific area on their mobile phones and thus comply with EU legislation: * Cell Broadcast is a standardised technology that makes it possible to send alerts to a geo-targeted population, directly on their mobile phones. When people are present in an area (whether they are residents or visitors) where a disaster is ongoing or might happen in the near future, their phone would display an alert with a distinctive ringtone and vibration. Public authorities can use this technology to alert instantly (usually within 10 seconds) the population present near a disaster (possibility to narrow it down to a few meters) and in a privacy-friendly manner. * Location-Based SMS is another technology that can be used to alert all the population of a given area in near real-time. The main difference with cell broadcast is that alerts are transmitted to the users by regular SMS. Public authorities can use the cellular base stations to disseminate alerts to all the phones connected to these stations in an anonymised way. Authorities may also be able to access information on the country of origin of the users’ SIM cards, making it possible to send the alert in different languages to different phones and to get real-time situational awareness on the number of users around the disaster. EENA'S STANCE ON TECHNOLOGIES EENA remains technology-neutral and believes that it is up to Member States to assess whether they want to deploy Cell Broadcast and/or Location-based SMS (both have pros and cons), which are described in EENA’s document on Public Warning Systems. We have also added examples at the bottom of this page. This being said, EENA believes that using both technologies is the best solution to fully exploit their potential and making sure that citizens are appropriately informed of a developing disaster. EENA is however firmly against the use of smartphone apps as a substitution for Cell-Broadcast and/or Location-based SMS. This is primarily because apps require downloading: a high-penetration rate cannot be achieved based on voluntary downloads only. TECHNOLOGIES ...BUT NOT ONLY While modern technologies can help reach thousands of people in seconds, we believe that the organisational and human aspects of public warning and crisis communication should not be forgotten. In other words, technologies will not draft nor launch the alerts. Every country and responsible authority must ensure that they have a proper doctrine and procedure in place to use these public warning systems. These strategies should for instance address questions such as: who sends the alerts; at which administrative level (national, regional, municipal…); at what moment; with which content; in which language; using which channels (etc). HOW CAN EENA HELP YOU TO DEPLOY PUBLIC WARNING? EENA can: * Respond to any questions you may have about public warning * Put you in contact with other public safety officials who have already deployed Cell Broadcast and/or Location-based SMS * Put you in contact with several vendors * Co-organise a physical / online event for you to hear from public safety officials and vendors Feel free to contact Benoit Vivier at bv@eena.org USE OF TECHNOLOGIES BY COUNTRY IN EUROPE AS OF DECEMBER 2023: STANDARDISATION You can find a list of standards here that affect the implementation of public warning systems. To find out more about standardisation, head to our page. * Standards on Cell Broadcast:ETSI TS 102 900 – European Public Warning Systerm (EU-ALERT) using the Cell Broadcast Service: https://www.etsi.org/deliver/etsi_ts/102900_102999/102900/01.03.01_60/ts_102900v010301p.pdf * 3GPP TS22.268; release 18 – Public Warning System requirements: https://www.etsi.org/deliver/etsi_ts/122200_122299/122268/18.01.00_60/ts_122268v180100p.pdf * 3GPP TS23.041; release 18 – Technical realization of Cell Broadcast Service: https://www.etsi.org/deliver/etsi_TS/123000_123099/123041/18.00.00_60/ts_123041v180000p.pdf * Standard on Common Alerting Protocol: Common Alerting Protocol, version 1.2: https://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2.pdf USEFUL RESOURCES * EENA Blog: The End Isn’t Nigh – Why There is Nothing to Fear About Public Warning Systems * EENA Blog: FR-Alert, a European Reference Combining Cell Broadcast and Location-Based SMS * EENA Blog: 8 Recommendations to Get the Most Out of Public Warning Systems * EENA 2023 Conference: Ensuring Continuity of Emergency Comms and Public Warning with Satellite Applications * EENA 2023 Conference: The UN Early Warnings for All Action Plan * EENA 2023 Conference: Combining Different Technologies to Alert the Population: PWS in France * EENA 2023 Conference: Diversification of Public Warning Channels EXAMPLES - AUTHORITIES REACHING CITIZENS Netherlands: Location-based SMS to give instructions to citizens after a fire broke out at the Bergpoortstraat Sweden: Location-based SMS about a fire Romania: Use of a Cell Broadcast message to inform the population about the authorities’ measures to fight the spread of Covid-19 Belgium: Location-based SMS to inform of an ongoing fire in an electric plant with potential toxic smoke Netherlands: Cell-Broadcast alert about a fire New Zealand: Use of a Cell-Broadcast alert to inform the population about the spread of COVID-19 and the change of alert level Netherlands: Location-based SMS to give instructions to citizens after a fire broke out at the Bergpoortstraat Sweden: Location-based SMS about a fire Previous DRONES Next NEXT GENERATION 112 BENOIT VIVIER RELATED DOCUMENTS * Public Warning Systems – 2019 Update -------------------------------------------------------------------------------- * Public Warning in Chile: Resilient culture -------------------------------------------------------------------------------- * Data and Strategies per country on Emergency Calls & Public Warning during COVID-19 -------------------------------------------------------------------------------- RELATED WEBINARS * Data and strategies on emergency calls & public warning during COVID-19 outbreak -------------------------------------------------------------------------------- * Public warning -------------------------------------------------------------------------------- Contact us Stay up to date Contact us Fields marked with an * are required Name * Email * Message * If you are a human seeing this field, please leave it empty. Stay up to date Want to receive our news and updates? Get in touch with eena-news@eena.org to join our mailing list and receive our latest updates! CONTACT DETAILS Avenue de la Toison d’Or 79 1060 Brussels Belgium info@eena.org LEGAL NOTICES Site editor: EENA asbl Director of Publication: Dr Demetrios Pyrros Hosting company: Fastlane Read our full privacy policy & legal notices For any data privacy enquiries, please contact our DPO Jerome Paris at dpo@eena.org © EENA 2020. All rights reserved. Designed and coded by Fastlane. Shopping Basket We use cookies to ensure that we give you the best experience on our website.ContinueRefusePrivacy policy