Damian Barker
January 2016
Contents
1.System Definition
2.General Alert Dissemination Method Requirements
3.CAP and Atom File Formatting
4.Custom Parameters
4.1.Inhibit Parameter
4.1.1.Inhibit Parameter Description and Methodology
4.1.2.Structure
4.1.3.Format
5.RDS Controller Technical Specifications
6.RDS Warning Receivers
6.1.RDS Warning Receivers Technical Specifications
7.Installation Details
1.System Definition
The Radio Data Service(RDS) encoder is a Common Alerting Protocol (CAP) v1.2 device which will poll at least two defined CAP sources for CAP alerts and activate RDS warning devices if required. The RDS encoder is installed into FM broadcast stations and generates specially encoded RDS signals containing the data from the CAP alert to inject into the FM signal in the mixing stage.
The RDS receivers are FM radio devices which receive traditional FM broadcast stations. The RDS warning devices activate their warning functions when they receive the specially encoded RDS messages from the RDS encoder.
2.General Alert Dissemination Method Requirements
The requirements in this section are applicable for ALL dissemination methods. Where differences are necessary for an individual dissemination method this will be indicated in the section titled “Technical Specifications Siren Controller.”
(a)Devices receive CAP v 1.2 alerts by “POLLING” the CAP servers and processing the Atom file containing the list and URI’s of active alerts. The format of the Atom file is described in section titled “CAP AND ATOM FILE FORMATTING”
(b)Devices will process unique CAP messages and disregard any identical duplicated alerts which may be received from multiple CAP server sources.
(c)Devices must be able to poll a list of at least two (2) CAP servers for active alerts at least once every sixty (60) seconds. Where an alternate polling interval is required the individual technical specifications will indicate this.
(d)Devices will be designed to use a dynamic IP address (such as common with ADSL internet service) and MUST include a self-contained Dynamic DNS client.
(e)Devices will be designed to utilise standard ADSL internet access with standard RJ45 interfaces.
(f)Devices will keep a completely auditable log of all alerts received, disseminated and disregarded.
(g)Devices will be fully compatible with the requirements set out in the section titled “CUSTOM PARAMETERS” in this document.
(h)Devices will feature a web interface accessible from the internet (with appropriate security and authentication) from which all dissemination options can be configured.
(i)Devices will implement all necessary self diagnostic and internet connectivity status tests and a reporting facility via an HTTP “GET” or “POST” mechanism of device status. A HTTP response of “OK” indicating normal function and “FAIL – xxxxxxx” where xxx is an error code defined in user documentation or a textual description of an error condition if a malfunction or otherwise unexpected condition arises.
3.CAP and Atom File Formatting
(a)CAP alerts generated by the CAP Server describe the affected area by using the geospatial CAP polygon and circle elements as well as defined geocode values to define alerting zone definitions. The list of geocodes can be expanded at any time using the Administration interface to define new alerting zone definitions.
(b)CAP messages containing sensor or other operational data not intended for public dissemination is identified by populating the CAP scope element with a value of “Private.” Such messages are NOT included in the general publication Atom index.
(c)CAP messages containing technical information about alerting device or system status or errors are identified by populating the CAP status element with the value of “System.” Such messages are NOT included in the general publication Atom index.
(d)The Atom-formatted index entry block for each alert on the CAP Server publication interface includes the following elements:
- The Atom link element includes the URL of the corresponding CAP XML file in the href attribute.
- The Atom title element contains the value of the CAP message’s headline element.
- The Atom updated element contains the value of the CAP message's sent element. \
- The following CAP elements are included in the Atom file with a namespace prefix of “cap” (which prefix is bound in the XML preamble to the OASIS CAP 1.2 namespace):
A. status
B. msgType
C. language
D. category
E. urgency
F. severity
G. certainty
H. areaDesc
I. geocode
(e)In the case of CAP messages containing an expires element, the message is considered unexpired until after the latest expires time in any included CAP info block. If no expires element is present in a CAP message that message is considered unexpired until one hour after its sent time value.
4.Custom Parameters
The following CAP parameter values must be supported by the alert dissemination device for this application.
4.1.Inhibit Parameter
4.1.1.Inhibit Parameter Description and Methodology
The inhibit parameter is included to provide the utmost granularity of alert dissemination methods to be activated for a particular alert. The presence of a “TRUE” inhibit parameter in an alert for a particular dissemination mechanism means that mechanism will NOT activate regardless of any other activation criteria being met. The absence of an inhibit parameter or a value of “FALSE”indicates that the dissemination method will determine its activation based on its filters, i.e. normal operation.
4.1.2.Structure
The inhibit tag is a parameter value in CAP.
4.1.3.Format
<Parameter>
<Valuename>inhibit-rds</Valuename>
<Value>True/False<Value>
</Parameter>
1
5.RDS Controller Technical Specifications
Table 1: RDS Controller Technical Specifications
S/N / 1Specifications / 2
Specifications Offered / 3
Notes, remarks, ref to documentation
Feature / Description
1 / General Description / The device monitors CAP 1.2 sources for CAP alerts and based on user defined activation “filters” and custom parameters activates the RDS receivers to disseminate warnings
2 / Function / Uses its LAN connection to receive CAP 1.2 and CAP 1.1 alerts (either pulled from a server by the unit or pushed to the device or both). It will then use internal “filters” and custom parameters as described to determine the required action. If needed, it will then:
- Activate the RDS receivers by sending a custom formatted RDS signal containing the CAP alert message.
3 / System Feed / As described in section titled “General Alert Dissemination Method Requirements”
- Polling interval : Monitor two CAP sources once every 10 seconds.
- Self Contained Dynamic DNS client.
4 / Activation Profiles / There will be a web based configuration allowing the creation/ editing and removal of Activation Profiles.
Activation profiles are activated when the activation criteria are met as described in section 5.
The successful activation of an Activation Profile will result in the activation of the RDS receivers in one of the following ALERT MODES.
ALERT MODE : HIGH
The following behaviours are expected from the RDS alert receivers in this Alert Mode.
-Maximum Alert Mode. RDS receivers will activate all possible means of alerting at the maximum level.
-SIREN activated at MAXIMUM volume
-Automatic Tuning to station broadcasting alert
-Automatic PowerON from Power OFF position
-New Message indicator activated
ALERT MODE : MEDIUM
The following behaviours are expected from the RDS alert receivers in this Alert Mode.
-SIREN activated at MEDIUM volume
-Automatic Tuning to station broadcasting alert
-Automatic PowerON from Power OFF position
-New Message indicator activated
ALERT MODE : LOW
The following behaviours are expected from the RDS alert receivers in this Alert Mode.
-SIREN activated at LOW volume
-Automatic PowerON from Power OFF position
-New Message indicator activated
ALERT MODE : SILENT
The following behaviours are expected from the RDS alert receivers in this Alert Mode.
-SIREN NOT activated.
-Automatic PowerON from Power OFF position
-New Message indicator activated
5 / Activation Criteria (filter) / User creates “Activation profiles” based on defining criteria for alerts based on the following parameters of the incoming CAP message :
- Status
- msgType (one or more)
- info.eventCode (SAME=a SAME event codes, multiple codes can be selected for multiple options)
- info.urgency (minimum and above)
- info.severity (minimum and above)
- info.certainty (minimum and above)
- areaDesc (multiple entries can be selected for multiple options)
- area.polygon (describes coverage polygon, incoming messages will be filtered by comparing areas. Multiple polygons can be listed locally and may appear in the incoming message.)
- Headline – A keyword / keyphrase filter will be made available for this element. Users will be able to setup an activation profile based on the contents of this field.
A “contains” comparison will compare the Headline field to the entirety of the comparison string and evaluates as TRUE if the corresponding comparison string appears in contiguous form in the Headline field.
An “exactly” comparison will compare the Headline field to the comparison string and evaluates as TRUE if the two strings are identical.
e.g Users will be able to setup an activation profile “TSUNAMI WARNING” which will activate RDS receivers in “HIGHT ALERT MODE” if the Headline is EXACTLY the following keyphrase : “A TSUNAMI WARNING IS IN EFFECT”
- Description – A keyword / keyphrase filter will be made available for this element. Users will be able to setup an activation profile based on the contents of this field.
A “contains” comparison will compare the Description field to the entirety of the comparison string and evaluates as TRUE if the corresponding comparison string appears in contiguous form in the Description field.
e.g Users will be able to setup an activation profile “TSUNAMI WARNING” which will activate RDS receivers in “HIGHT ALERT MODE” if the Description contains the following keyphrase : “A TSUNAMI WARNING IS IN EFFECT”
An “exactly” comparison will compare the Description field to the comparison string and evaluates as TRUE if the two strings are identical.
- For each activation profile the user will be allowed to select a combination of the parameters above including filters for both Description and Headline.
6 / Required Equipment / Equipment to be provided with all components ready to install, in a self install kit. Installation will be done by local staff. Telephone support will be required by the provider under this RFQ, and should be included for at least two hours.
7 / Protocol of activating message / CAP 1.1 and CAP 1.2 XML file with digital signature based software. The unit will report the results of a downloaded message: download ok, passed filter, activation result.
8 / Network / Connectivity 100 Base-T LAN support, RJ45 connector
9 / Memory / Totally solid state memory storage for reliable operation – no hard disk drive.
10 / Unit Control / Web-Based control – all settings and functions can be performed from anywhere on the internet, including initiating or forwarding alerts, and changing configuration.
11 / Security / HTTPS/SSL/digital signature security.
12 / Log files / Text logs are available via the web interface page.
13 / Time sync / Time Synchronized to national standards via NTP protocol.
14 / Mounting / Rack mount2U or less enclosure.
15 / LED Indicators / Front panel status LEDs indicating Power On and Connection to Server OK.
16 / LCD Display / LCD Display which can display the current text of the CAP alert and used in configuration of the device
17 / Power / 120-240 V AC 50/60 Hz
18 / Documentation / Full user and installer documentation to be provided in both hard and electronic copy.
6.RDS Warning Receivers
The RDS Warning Receivers function as normal FM radios when there is no alert. Once an alert is received depending on the level of the alert the Warning Receivers activate in one of several alert modes to inform the user. The RDS warning receiver MUST have at a minimum an LCD Display which can display the contents of the alert and a loud siren for notification.
Other required features:
- Battery Backup (Rechargeable battery : User replaceable)
- Automatic scanning of radio frequencies to find EWS signal.
- Allows user to manually select EWS frequency if necessary.
- Backlit dot matrix LCD display.
* The vendor will provide photos of the RDS warning receivers and exact physical dimensions in their response to the Request For Proposal.
6.1.RDS Warning Receivers Technical Specifications
Table 2: RDS Warning Receivers Technical Specifications
S/N / 1Specifications / 2
Specifications Offered / 3
Notes, remarks, ref to documentation
Function / Details
1 / RDS Warning Receiver / FM radio monitors RDS of FM broadcast stations for alert information and activates in one of several alert modes as defined on the encoder interface to warn user.
2 / Standard / Fully meets or exceeds specifications as in CEA-2009-B, "consumer equipment" category.
3 / FM Reception / Standard FM commercial broadcast range 88-108MHz
4 / "Public Alert" certified / Provide CEA registration for the radio proposed
5a / Power supply (Battery) / Rechargeable batteries, (user replaceable)
5b / Power supply (AC) / 120V-240V AC 50/60 Hz power supply
6 / Display Language / English
7 / External Battery / Socket for external battery
8 / RF Sensitivity / 0.25 microvolt or less (see CEA standard for definition)
9 / Display / LCD type, backlit, dot matrix.
10 / New Message Indicator (Visual) / Either a character on LCD display or a flashing LED light to give visual feedback of reception of an alert.
11 / Audio Output / Siren capable of alerting at different volume levels.
FM Stereo playback through integrated loudspeaker
Stereo 3.5mm Headphone jack.
12 / Languages / English
13 / Documentation / Full user documentation to be provided in both hard and electronic copy.
14 / Physical Dimensions / Easily portable, size of a standard clock radio, not to exceed (8 inches x 6 inches x 3 inches)
1
7.Installation Details
The installation of the RDS Encoder devices will be performed by the equipment vendor with assistance provided by local contractors.
The equipment vendor is responsible for the installation, initial configuration and testing of all equipment to be installed under this RFQ and will:
(1)Provide an installation document detailing installation and configuration procedure, required local resources as well as resources provided by the vendor for use during the installation procedure.
(2)Work closely with local contractors during the installation phase in order to build in country capacity regarding installation and maintenance procedures.
(3)Provide a detailed test plan which demonstrates the fulfillment of all technical operation requirements in this RFQ at least one month before scheduled installation.
(4)Install and configure devices as necessary during the agreed upon installation timeframe.
(5)Provide both electronic and hard copies of installation, maintenance and configuration manuals.
(6)Produce a test report detailing the results of the testing of the installed equipment as specified in the test plan.
(7)Provide support by telephone and or email for a maximum of twelve (12) hours over a period of three (3) months immediately following the installation of devices.
The intended recipient is responsible for the overall coordination and scheduling of the installation processes and will:
(1)Schedule the installation in conjunction with the equipment vendor and beneficiary countries.
(2)Provide and organise accommodation and local transportation to and from installation sites where necessary for equipment installers.
(3)Assume responsibility for auditing the installation and test processes and ensuring installation meets the desired standards and operability.
(4)Assume responsibility for securing written agreements with broadcast entities to facilitate the installation process.
1