The document discusses the implementation of Ro-Alert, Romania's public warning system. It describes how Ro-Alert was established following a 2017 tragedy to allow emergency agencies to quickly send alerts to the public via cell broadcast. The implementation process involved acquiring standards-compliant technology, testing with mobile network operators, and establishing regulatory frameworks. Since becoming operational, Ro-Alert has sent over 6,000 alerts about various hazards like flooding, storms, wild animals and the pandemic. The system provides a critical public warning capability in Romania.
2. AGENDA
The real need of Ro–Alert
Ro–Alert implementation process
The system operation
Other operational PWSs
Final remarks
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 2
3. The real need of Ro – Alert
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 3
17th of September, 2017 tragedy
– 8 deaths, 145 injured persons,
many cars and houses destroyed
4. The real need of Ro–Alert
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 4
18th of September 2017
Mr. Mihai Tudose, The Prime Minister
decided to setup the WG
NRA MNO CB activation
MoI GIES
system operation
STS
system implementation
5. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 5
• Standards Inventory
• Architecture Decision
• Acquisition Process
• Tests and Acceptance
• Regulatory actions
along the process of
implementation
CBE CBC
MNO 1
MNO 2
MNO n
Emergency
agencies
CBE
CBC MNO 1
MNO 2
MNO n
Emergency
agencies
CBC
CBC
6. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 6
CB
Specs
&
Standards
• TS 102 900 – European Public Warning system (EU-ALERT)
using the cell broadcast service
• TS 22.268 - Public Warning System (PWS) requirements
• TS 23.038 - Alphabets and language-specific information
• TS 23.041 - Technical realization of Cell Broadcast Service
(CBS)
• TS 25.419 - UTRAN Iu-BC interface Service Area Broadcast Protocol
(SABP)
• TS 29.168 - Cell Broadcast Centre interfaces with the Evolved Packet Core
• TS 36.413 - Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 Application Protocol (S1AP)
• TS 48.049 - Cell Broadcast Centre (BSC-CBC) interface specification; Cell
Broadcast Service Protocol (CBSP)
7. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 7
HA ARCHITECTURE
4 x MNO x
2G/3G/4G =
connectivity with
about 300.000
Network Elements
CBE CBC
Emergency
agencies
Geographical
redundant
CBC
Geographical
redundant
CBE
TCP/IP
Non 3GPP standard
(CAP)
TCP/IP
Non 3GPP standard
(CAP)
STS
Iu-BC
SBc
UMTS-RNC
MME-LTE
GSM-BSC
NodeB
BTS
eNodeB
MNOs 1 to 4
8. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 8
• Using enhanced CAP* 1.2 protocol, CBC
receives all the required parameters for
sending alerts, including:
• repetition interval
• numbers of repetitions
• the CAP payload is sent from CBE to CBC over
an HTTP connection and contains:
• one or more polygons
• a list of cells
• CBC API retrieves cells position, the status of
the alert and the list of cells that could not
broadcast the message
*CAP – Common Alerting Protocol
numbers of repetitions
ALERT FORM
repetition interval
No of polygons Interval
DESCRIPTION
9. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 9
SECURITY ASPECTS No Internet connection
VPN between
RO-ALERT, MNO
and GIES
Firewalls between
GIES and CBE
CBC and MNOs
PKI tokens and credentials for
authentications and non-repudiation
Logging of all activities
and error messages
24/7 NOC & SOC monitoring
10. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 10
CELLULAR REQUIREMENTS
No need for apps CB compatibility
CB should be imbedded on all smartphones
and customized for each country
Each alert is sent twice
Only CMAS 4371 and GSMA 919 so far
11. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 11
EMERGENCY ORDINANCE NO.
46/2019
Art. 18.
Obligation of operators and terminal dealers
to present information about capabilities of
terminals and how to activate the CB
Also, the information about the terminal will
be transmitted to STS for update of RO-
ALERT portal
Art. 19.
No terminal entry into the Romanian market if
CB can not be activated
LEGAL FRAMEWORK
12. Ro–Alert implementation process
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 12
Ro–Alert Implementation Timelines
Date Sep-17 Apr-18 Jun-19 Jun-20 Feb-21 TOTAL
Technical Side Acquisition,
implementation,
tests and
acceptance
3months
Operational Side Memorandum STS -
MOs, publishing
information on MO sites
and STS ro-alert.ro portal
8months
Regulatory Side Ordinance 72on
implementation
Ordinance 46on
operation, ANCOM
decision on MO
obligations
Interdiction of
mobiles not
compatible with
CB
Parliament Law
Approval
About 3
years
Ro–Alert Implementation Costs – 2.5 mil EUR
17. Ro–Alert operation
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 17
Type of Event No of Alerts
Freezing rain, blizzard 132
Flooding 339
Storms 1,122
Pandemic 1,233
Wild animals 3,315
Total 6,141
2% 6%
18%
20%
54%
No of Alerts
Freezing rain, blizzard Flooding
Storms Pandemic
Wild animals
20. Other operational PWSs
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 20
EWS OF EARTHQUAKES
✓ Stop high risk processes
✓ Protection of Critical Infrastructures
21. Final Remarks
10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 21
Ro-Alert is the most effective and useful PWS
The rules/legal framework harmonization take
longer than technical implementation
No technology shall be excluded from PWS type
systems– visual/auditory, fixed/mobile,
local/regional/national
We will enhance alerting mechanisms to radio & TV
broadcasters, IP public networks announcements
22. 10/12/2021 SPECIAL TELECOMMUNICATIONS SERVICE 22
Q&A
CONTACT
323A Splaiul Independenței, 6th District,
Bucharest, Romania, Post Code 060044
Telephone: +4021 202 21 88
Email: cabinet.prim-adjunct@sts.ro
www.sts.ro/en
HONOR
LOYALTY
PERFORMANCE
PROFESSIONALISM
Thank you for your attention!