hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1a382157d5a45af8b664bdd32c73890e | 104 090 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI EN 300 401 (V2.1.1): "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers". ETSI ETSI TS 104 090 V1.1.2 (2025-02) 8 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3 Definition of terms, symbols and abbreviations | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3.1 Terms | For the purposes of the present document, the following terms apply: band scan: function to scan the whole of the tuning range to update the stored service list when required EWS ensemble: DAB ensemble with FIG 0/7 and FIG 0/15 receiver: any device designed to receive digital radio signals tuning memory: stored information for previously tuned ensembles and services |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3.2 Symbols | Void. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding DAB Digital Audio Broadcasting DUT Device Under Test EEP Equal Error Protection EId Ensemble Identifier ETI Ensemble Transport Interface EWS Emergency Warning System FIB Fast Information Block FIC Fast Information Channel FIG Fast Information Group FM Frequency Modulation GNSS Global Navigation Satellite System MP2 MPEG layer 2 NI Network Independent OE Other Ensemble RF Radio Frequency UEP Unequal Error Protection UI User Interface |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 4 EWS Certification Mark | The present document comprises the requirements and test specifications by which radio receivers can qualify to carry an Emergency Warning System (EWS) Certification Mark ("the Mark") for emergency warnings. The purpose of the Mark is to ensure that consumers can readily identify products which are suitable for reception of an Emergency Warning System using DAB and which provide features at a sufficiently high level of performance to ensure that the product meets the relevant criteria to provide dependable information to the general public in case of emergencies. In order to qualify for use of the Mark, products shall meet the requirements set out for the type of product, either: • minimum requirements for domestic Emergency Warning System receivers (see clause 5); or • minimum requirements for in-vehicle Emergency Warning System receivers (see clause 6). ETSI ETSI TS 104 090 V1.1.2 (2025-02) 9 In order to prove compliance against the requirements, products shall pass the test specifications, below: • test specification for domestic products meeting minimum requirements for Emergency Warning System receivers (see clause 7); or • test specification for in-vehicle products meeting minimum requirements for Emergency Warning System receivers (see clause 8). The test specifications are designed to complement the testing described in ETSI TS 103 461 [1]. The process for applying for certification to use the Mark is beyond the scope of the present document, but national and international schemes are expected to be in place. 5 Minimum requirements for domestic Emergency Warning System receivers |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.1 Introduction | The minimum requirements for domestic EWS receivers are set out in this clause 5. The minimum requirements for in- vehicle EWS receivers are the subject of clause 6. Domestic products comprise many types of receiver, including portable and larger devices. Domestic products may be mains or battery powered, or both. They may have a telescopic antenna, a flexible wire antenna, an earphone antenna, an antenna integrated into the receiver, or they may be supplied without an antenna. A key feature of domestic products is the ability to automatically play alert messages even when the product is not playing audio. Products may include additional features beyond the minimum requirements, or capabilities beyond the minimum requirements. However, such additional features or capabilities shall not prevent the requirements stated being met. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.2 Basic requirements | Domestic products shall comply with the requirements set out in ETSI TS 103 461 [1], clause 5. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.3 Initialization | Domestic products shall provide an initialization mechanism which identifies all receivable EWS ensembles. This shall be carried out as a complete band scan and ensembles carrying FIG 0/15 shall be identified and recorded. As long as at least one EWS ensemble is identified, the initialization mechanism shall invite the user to enter the receiver location code using the presentation format specified in ETSI TS 104 089 [2], annex A. The checksum shall be calculated and if in error, the user shall be invited to check and re-enter until successful. The product shall select an EWS ensemble to monitor based on criteria as recommended in ETSI TS 104 089 [2], clause 7.2.3. If no EWS ensembles are identified, the product shall indicate via the user interface that the EWS function is not available. The user manual for the product shall include an instruction to reinitialize the product whenever it is moved to a different building. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.4 EWS ensembles | The receiver shall provide a facility to keep the tuning memory aligned with EWS signals on-air. Domestic products shall perform a full band scan at regular intervals, whilst the product is not tuned to a specific service. It is recommended to perform a band scan at a minimum once per week. Ensembles carrying FIG 0/15 shall be identified and recorded. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 10 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.5 Operational modes | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.5.1 Sleep/monitor duty cycle | Products shall implement a sleep/monitor duty cycle, synchronized to the time provided in FIG 0/10, that shall be operational whenever the product is not outputting audio. The sleep mode shall be according to ETSI TS 104 089 [2], clause 7.2.2.2. The monitor mode shall be fully operational and able to decode the FIC of the chosen EWS ensemble immediately prior to the minute's edge. The product shall react according to ETSI TS 104 089 [2], clause 7.2.2.3. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 5.5.2 Audio mode | Domestic products, when put into operation, shall tune to an EWS ensemble and select a service (this may be the last tuned service, a service allocated to a preset, or some other service that the user has shown previous interest in). Products shall react according to ETSI TS 104 089 [2], clause 7.2.2.4. 6 Minimum requirements for in-vehicle Emergency Warning System receivers |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 6.1 Introduction | The minimum requirements for in-vehicle EWS receivers are set out in this clause 6. The minimum requirements for domestic EWS receivers are the subject of clause 5. In-vehicle products are those products designed specifically for use within a vehicle. In-vehicle products comprise many types of receiver, including those integrated into the dashboard, and aftermarket products mounted in the dashboard, behind the dashboard, to the vehicle windscreen or elsewhere. Aftermarket products designed to be self-installed by the consumer should ensure that proper consideration is given to ensuring that power adapters, etc., do not cause interference in the FM and DAB broadcast bands. In-vehicle products may be supplied with or without an antenna. Products may include additional features beyond the minimum requirements, or capabilities beyond the minimum requirements. However, such additional features or capabilities shall not prevent the requirements stated being met. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 6.2 Basic requirements | In-vehicle products shall comply with the requirements set out in ETSI TS 103 461 [1], clause 6. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 6.3 Tuner capability | In-vehicle products shall have a minimum of two DAB tuners. This allows them to play out audio and at the same time monitor other DAB ensembles for alert signalling and to determine whether a matched alert message is receivable. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 6.4 Location awareness | In-vehicle products shall have the means to know their geographical location to a precision of at least 100 m. Typically, a GNSS receiver will be suitable. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 6.5 Operation | In-vehicle products shall behave according to ETSI TS 104 089 [2], clause 7.3.3. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 11 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7 Test specification for domestic EWS receivers | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.1 Introduction | Clause 7 provides the test specifications for domestic receivers to comply with EWS requirements. Domestic receivers shall comply with all tests in clause 7. The Device Under Test (DUT) will be exposed to the test streams and the behaviour of the DUT will be verified. The test streams described in annex A are used for these tests. The following equipment is needed: • Two Ensemble Transport Interface (ETI) file players and signal generators suitable for playing ETI files and for generating an RF output of -50 dBm. • Suitable means to couple the output of the signal generators to the input of the DUT; direct cable or antenna. • A timing device showing minutes and seconds (m:ss) which can be started when an ETI file starts playing. The tests are performed using a conducted or radiated method as the receiver allows. The test setup is shown in Figure 1. Any band III channels may be used - three are needed. The signal level shall be set to -50 dBm unless otherwise specified. For radiated testing, the output of the R.F. combiner shall be connected to an antenna. The signal generators shall be set to different frequencies. Figure 1: Test set-up |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.2 Basic checks | All EWS products are required to have been tested for compliance against ETSI TS 103 461 [1]. Therefore, the controls, display device and audio device are known to be working properly, and the selection mechanism delivers the right audio stream to the audio output. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.3 Test 1 - Set-up behaviour | • Objective: - To check the behaviour of the DUT as delivered out-of-the-box before the user has entered the receiver location code. • Method: - Set signal generator 1 to an unused DAB channel and the signal level to -50 dBm. - Signal generator 2 remains switched off. R.F. signal generator 2 Baseband encoder 1 R.F. signal generator 1 Baseband encoder 2 R.F. combiner DUT ETSI ETSI TS 104 090 V1.1.2 (2025-02) 12 - Turn on the DUT. - Setup baseband encoder 1 and play stream EWS1.eti. Start the timing device. - Perform the necessary steps to perform a factory reset (the service list shall be cleared and the receiver location code shall be deleted; a band scan shall be performed) but do not enter a location code. If the receiver enforces entry of a receiver location code, enter the code 1255-4467-1352 and restart playout of stream EWS1.eti and restart the timing device. - Select "Service 5". - Listen to the audio and look at the display whilst monitoring the timing device. - When timing device shows 1:40, put the DUT to sleep. - Continue to listen and look at the display and monitor the timing device. - When timing device shows 3:30, the test is complete. NOTE: The location code 1255-4467-1352 is also known as Z1:91BB82 (see Table A.19). • Required result: - The audio output and display of the service label shall be as described in Table 1. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 1: Required response for test 1 Time displayed by the timing device (m:ss) Required response when no location code has been entered Required response when location code 1255-4467-1352 has been entered After service selection Display shows "Service 5" Audio is a mix of tones at 660 Hz and 770 Hz Display shows "Service 5" Audio is a mix of tones at 660 Hz and 770 Hz 1:05 to 1:14 Display changes to "Alert 1" Audio changes to a mix of tones at 440 Hz and 550 Hz Display changes to "Alert 1" Audio changes to a mix of tones at 440 Hz and 550 Hz 1:15 to 1:24 Display changes to "Service 5" Audio changes to a mix of tones at 660 Hz and 770 Hz Display changes to "Service 5" Audio changes to a mix of tones at 660 Hz and 770 Hz 1:25 to 1:34 No change to display No change to audio Display changes to "Alert 2" Audio changes to a mix of tones at 1 100 Hz and 1 210 Hz 1:35 to 1:39 No change to display No change to audio Display changes to "Service 5" Audio changes to a mix of tones at 660 Hz and 770 Hz 1:40 to 1:54 DUT sleeps DUT sleeps 1:55 to 2:04 Display changes to "Alert 1" Audio changes to a mix of tones at 440 Hz and 550 Hz Display changes to "Alert 1" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:05 to 2:54 DUT sleeps DUT sleeps 2:55 to 3:04 DUT sleeps Display changes to "Alert 2" Audio changes to a mix of tones at 1 100 Hz and 1 210 Hz 3:05 to 3:59 DUT sleeps DUT sleeps |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.4 Test 2 - Tuned ensemble alert area matching | • Objective: - To check the behaviour of the DUT with different alert area settings. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 13 • Method: - Turn on the DUT. - Navigate the UI to allow entry of the receiver location code. Set the code to 1255-4467-1352. - Do not alter the settings of signal generator 1. - Setup baseband encoder 1 and play stream EWS2.eti. Start the timing device. - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 2. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 2: Required response for test 2 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 0:50 to 0:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:00 to 1:09 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:20 to 1:29 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:40 to 1:59 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 2:00 to 2:09 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:10 to 2:19 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:20 to 2:29 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:30 to 3:59 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.5 Test 3 - Tuned ensemble alert stages | • Objective: - To check the behaviour of the DUT with different alert stage settings. • Method: - Do not alter the settings of signal generator 1. - Setup baseband encoder 1 and play stream EWS3.eti. Start the timing device. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 14 - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 3. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 3: Required response for test 3 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 0:50 to 0:59 Display changes to "Level 1 Update" Audio changes to mix of tones at 880 Hz and 990 Hz 1:00 to 1:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 Display changes to "Level 1 Repeat" Audio changes to mix of tones at 1 320 Hz and 1 430 Hz 1:20 to 1:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 Display changes to "Level 1 Critical" Audio changes to mix of tones at 1 760 Hz and 1 870 Hz 1:40 to 1:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:50 to 1:59 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 2:00 to 2:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:10 to 2:19 Display changes to "Level 2 Update" Audio changes to mix of tones at 1 100 Hz and 1 210 Hz 2:20 to 2:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:30 to 2:39 Display changes to "Level 2 Repeat" Audio changes to mix of tones at 1 540 Hz and 1 650 Hz 2:40 to 2:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:50 to 2:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 3:00 to 3:09 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 3:10 to 3:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.6 Test 4 - Other ensemble alerts | • Objective: - To check the behaviour of the DUT for other ensemble alerts. • Method: - Do not alter the settings of signal generator 1. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 15 - Set signal generator 2 to an unused DAB channel and the signal level to -50 dBm. - Setup baseband encoder 2 with stream EWS4.eti and simultaneously play stream EWS3.eti on baseband encoder 1 and EWS4.eti on baseband encoder 2. Start the timing device. - Perform the necessary steps to clear the service list and perform a band scan. - Select "Service 11". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 4. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 4: Required response for test 4 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 11" Audio is a tone at 300 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 0:50 to 0:59 Display changes to "Level 1 Update" Audio changes to mix of tones at 880 Hz and 990 Hz 1:00 to 1:09 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:10 to 1:19 Display changes to "Level 1 Repeat" Audio changes to mix of tones at 1 320 Hz and 1 430 Hz 1:20 to 1:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:30 to 1:39 Display changes to "Level 1 Critical" Audio changes to mix of tones at 1 760 Hz and 1 870 Hz 1:40 to 1:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:50 to 1:59 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 2:00 to 2:09 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:10 to 2:19 Display changes to "Level 2 Update" Audio changes to mix of tones at 1 100 Hz and 1 430 Hz 2:20 to 2:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:30 to 2:39 Display changes to "Level 2 Repeat" Audio changes to mix of tones at 1 540 Hz and 1 650 Hz 2:40 to 2:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:50 to 2:59 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz 3:00 to 3:09 Display shows "Service 11" Audio is a tone at 300 Hz 3:10 to 3:19 Display is permitted to blank, shows "Service 11" Audio is permitted to mute, only a tone at 300 Hz is permitted 3:20 to 3:29 Display shows "Service 11" Audio is a tone at 300 Hz 3:30 to 3:39 Display is permitted to blank, shows "Service 11" Audio is permitted to mute, only a tone at 300 Hz is permitted ETSI ETSI TS 104 090 V1.1.2 (2025-02) 16 Time displayed by the timing device (m:ss) Required response 3:40 to 3:49 Display shows "Service 11" Audio is a tone at 300 Hz 3:50 to 3:59 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.7 Test 5 - Sleep mode EWS selection | • Objective: - To check the behaviour of the DUT when selecting suitable ensembles to monitor in sleep mode. • Method: - Do not alter the settings of signal generator 1 or signal generator 2. - Setup baseband encoders 1 and 2 and simultaneously play stream EWS5.eti on encoder 1 and EWS6.eti on encoder 2. Start the timing device. - Perform the necessary steps to clear the service list and perform a band scan. - Select "Service 11". - Put the DUT to sleep. - Listen to the audio and look at the display whilst monitoring the timing device. - When timing device shows 2:20, set signal generator 1 to signal level of -85 dBm. - When timing device shows 2:45, turn on the DUT. - Perform the necessary steps to clear the service list and perform a band scan. - Select "Service 1". - Put the DUT to sleep, ensuring this happens before the timing device shows 3:45. - Listen to the audio and look at the display whilst monitoring the timing device. - When timing device shows 4:30, turn off signal generator 2. - Continue to listen and look at the display and monitor the timing device. - When timing device shows 6:30, change the DAB channel of signal generator 1. - Continue to listen and look at the display and monitor the timing device. - When timing device shows 9:30 test 5 is complete and test 6 shall be immediately started. • Required result: - The audio output and display of the service label shall be as described in Table 5. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 17 Table 5: Required response for test 5 Time displayed by the timing device (m:ss) Required response After service selection and until DUT put to sleep Display shows "Service 11" Audio is a tone at 300 Hz Non-EWS indicator is present From sleep time until 1:59 DUT sleeps 2:00 to 2:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:15 to 2:44 DUT sleeps 2:45 until DUT put to sleep Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz From sleep time until 3:59 DUT sleeps 4:00 to 4:14 DUT wakes up Display changes to "Service 12" Audio changes to a tone at 600 Hz 4:15 to 5:59 DUT sleeps 6:00 to 6:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 6:15 to 7:59 DUT sleeps 8:00 to 8:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 8:15 to 8:59 DUT sleeps 9:00 to 9:14 DUT wakes up Display changes to "Alert 3" Audio changes to a mix of tones at 2 420 Hz and 2 530 Hz 9:15 to 9:59 DUT sleeps NOTE: The signalling provided by the test files does not contain OE alert signalling in order to allow the determination of the EWS ensemble selection behaviour: in the real world OE signalling is required for EWS ensembles that have overlapping coverage areas. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.8 Test 6 - Sleep mode alert response | • Objective: - To check the behaviour of the DUT in sleep mode. • Method: - Begin this test immediately at the end of test 5. - Do not alter the settings of signal generator 1 or signal generator 2. - Setup baseband encoder 1 and play stream EWS7.eti. Start the timing device. - Do not turn on the DUT. - Listen to the audio and look at the display whilst monitoring the timing device. • Required result: - The audio output and display of the service label shall be as described in Table 6. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 18 Table 6: Required response for test 6 Time displayed by the timing device (m:ss) Required response 0:00 to 0:59 DUT sleeps 1:00 to 1:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 1:15 to 1:59 DUT sleeps 2:00 to 2:14 DUT wakes up Display changes to "Level 1 Update" Audio changes to a mix of tones at 880 Hz and 990 Hz 2:15 to 2:59 DUT sleeps 3:00 to 3:14 DUT wakes up Display changes to "Level 1 Repeat" Audio changes to a mix of tones at 1 320 Hz and 1 430 Hz 3:15 to 3:59 DUT sleeps 4:00 to 4:14 DUT wakes up Display changes to "Level 1 Critical" Audio changes to a mix of tones at 1 760 Hz and 1 870 Hz 4:15 to 8:59 DUT sleeps 9:00 to 9:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 9:15 to 9:59 DUT sleeps |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 7.9 Test 7 - Concurrent alerts | • Objective: - To check the behaviour of the DUT with concurrent alert signalling. • Method: - Set signal generator 1 to a signal level of -50 dBm. - Set signal generator 2 to a signal level of -50 dBm. - Turn on the DUT. - Setup baseband encoders 1 and 2 and simultaneously play stream EWS8.eti on baseband encoder 1 and stream EWS9.eti on baseband encoder 2. Start the timing device. - Perform the necessary steps to clear the service list and perform a band scan. - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - When the timing device shows 3:00, put the DUT to sleep. - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 7:30, turn on the DUT. - Select "Service 11". - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 7:55, cancel the alert playback. - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 8:40, cancel the alert playback. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 19 - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 9:30, test 7 is complete. • Required result: - The audio output and display of the service label shall be as described in Table 7. Changes to audio shall occur within the first 5 s of each timing period (except where otherwise stated). Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 7: Required response for test 7 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 0:50 to 1:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 Display changes to "Service 12" Audio changes to a tone at 600 Hz 1:20 to 1:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 1:40 to 1:49 Display changes to "Service 12" Audio changes to a tone at 600 Hz 1:50 to 2:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:10 to 2:19 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:20 to 2:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:30 to 2:39 Display changes to "Level 2 Start" Audio changes to a mix of tones at 660 Hz and 770 Hz 2:40 to 2:59 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 3:00 to 5:59 DUT sleeps 6:00 to 6:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 6:15 to 6:29 Display changes to "Service 12" Audio changes to a tone at 600 Hz 6:30 to 6:59 DUT sleeps 7:00 to 7:14 DUT wakes up Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz within 7 s 7:15 to 7:29 DUT sleeps 7:30 to 7:44 Display changes to "Service 11" Audio changes to a tone at 300 Hz 7:45 to 7:54 Display changes to "Service 14" Audio changes to a tone at 1 000 Hz 7:55 to 8:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz; no other tones are heard 8:30 to 8:39 Display changes to "Level 2 Start" Audio changes to a mix of tones at 660 Hz and 770 Hz 8:40 to 9:59 Display changes to "Service 11" Audio changes to a tone at 300 Hz; no other tones are heard ETSI ETSI TS 104 090 V1.1.2 (2025-02) 20 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8 Test specification for in-vehicle EWS receivers | |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.1 Introduction | Clause 8 provides the test specifications for in-vehicle receivers to comply with EWS requirements. In-vehicle receivers shall comply with all tests in Clause 8. The testing provides only very basic location testing in a static location. Additional testing of location capability is strongly recommended! The DUT will be exposed to the test streams and the behaviour of the DUT will be verified. The test streams described in annex A are used for these tests. The following equipment is needed: • Two ETI file players and signal generators suitable for playing ETI files and for generating an RF output of -50 dBm. • Suitable means to couple the output of the signal generators to the input of the DUT, either direct cable or antenna. • GNSS simulator to provide location information. • A timing device showing minutes and seconds (m:ss) which can be started when an ETI file starts playing. The tests are performed using a conducted or radiated method as the receiver allows. The test setup is shown in Figure 2. Any band III channels may be used - three are needed. The signal level shall be set to -50 dBm unless otherwise specified. The GNSS simulator shall indicate the location is 13,377699°E, 52,516338°N. For radiated testing, the output of the R.F. combiner shall be connected to an antenna. The signal generators shall be set to different frequencies. Figure 2: Test set-up |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.2 Basic checks | All EWS products are required to have been tested for compliance against ETSI TS 103 461[1]. Therefore, the controls, display device and audio device are known to be working properly, and the selection mechanism delivers the right audio stream to the audio output. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.3 Test 1 - Set-up behaviour | Not required. R.F. signal generator 2 Baseband encoder 1 GNSS simulator R.F. signal generator 1 Baseband encoder 2 R.F. combiner DUT ETSI ETSI TS 104 090 V1.1.2 (2025-02) 21 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.4 Test 2 - Tuned ensemble alert area matching | • Objective: - To check the behaviour of the DUT with different alert area settings. • Method: - Set signal generator 1 to an unused DAB channel and the signal level to -50 dBm. - Signal generator 2 remains switched off. - Turn on the DUT. - Setup baseband encoder 1 and play stream EWS2.eti. Start the timing device. - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 8. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 8: Required response for test 2 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 0:50 to 0:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:00 to 1:09 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:20 to 1:29 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 1:40 to 1:59 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 2:00 to 2:09 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:10 to 2:19 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:20 to 2:29 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:30 to 3:59 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz ETSI ETSI TS 104 090 V1.1.2 (2025-02) 22 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.5 Test 3 - Tuned ensemble alert stages | • Objective: - To check the behaviour of the DUT with different alert stage settings. • Method: - Do not alter the settings of signal generator 1. - Setup baseband encoder 1 and play stream EWS3.eti. Start the timing device. - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 9. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 9: Required response for test 3 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 0:50 to 0:59 Display changes to "Level 1 Update" Audio changes to mix of tones at 880 Hz and 990 Hz 1:00 to 1:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 Display changes to "Level 1 Repeat" Audio changes to mix of tones at 1 320 Hz and 1 430 Hz 1:20 to 1:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 Display changes to "Level 1 Critical" Audio changes to mix of tones at 1 760 Hz and 1 870 Hz 1:40 to 1:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:50 to 1:59 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 2:00 to 2:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:10 to 2:19 Display changes to "Level 2 Update" Audio changes to mix of tones at 1 100 Hz and 1 210 Hz 2:20 to 2:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:30 to 2:39 Display changes to "Level 2 Repeat" Audio changes to mix of tones at 1 540 Hz and 1 650 Hz 2:40 to 2:49 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:50 to 2:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz 3:00 to 3:09 Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 3:10 to 3:59 No change to display: Display shows "Service 1" No audio interruption: Audio is a mix of tones at 220 Hz and 330 Hz ETSI ETSI TS 104 090 V1.1.2 (2025-02) 23 |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.6 Test 4 - Other ensemble alerts | • Objective: - To check the behaviour of the DUT for other ensemble alerts. • Method: - Do not alter the settings of signal generator 1. - Set signal generator 2 to an unused DAB channel and the signal level to -50 dBm. - Setup baseband encoder 2 with stream EWS4.eti and simultaneously play stream EWS3.eti on baseband encoder 1 and EWS4.eti on baseband encoder 2. Start the timing device. - Select "Service 11". - Listen to the audio and look at the display whilst monitoring the timing device. - Leave the DUT switched on. • Required result: - The audio output and display of the service label shall be as described in Table 10. Changes to audio shall occur within the first 5 s of each timing period. Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. Table 10: Required response for test 4 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 11" Audio is a tone at 300 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 0:50 to 0:59 Display changes to "Level 1 Update" Audio changes to mix of tones at 880 Hz and 990 Hz 1:00 to 1:09 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:10 to 1:19 Display changes to "Level 1 Repeat" Audio changes to mix of tones at 1 320 Hz and 1 430 Hz 1:20 to 1:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:30 to 1:39 Display changes to "Level 1 Critical" Audio changes to mix of tones at 1 760 Hz and 1 870 Hz 1:40 to 1:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 1:50 to 1:59 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 2:00 to2:09 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:10 to 2:19 Display changes to "Level 2 Update" Audio changes to mix of tones at 1 100 Hz and 1 210 Hz 2:20 to 2:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:30 to 2:39 Display changes to "Level 2 Repeat" Audio changes to mix of tones at 1 540 Hz and 1 650 Hz 2:40 to 2:49 Display changes to "Service 11" Audio changes to a tone at 300 Hz 2:50 to 2:59 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz 3:00 to 3:09 Display shows "Service 11" Audio is a tone at 300 Hz ETSI ETSI TS 104 090 V1.1.2 (2025-02) 24 Time displayed by the timing device (m:ss) Required response 3:10 to 3:19 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz 3:20 to 3:29 Display shows "Service 11" Audio is a tone at 300 Hz 3:30 to 3:39 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz 3:40 to 3:49 Display shows "Service 11" Audio is a tone at 300 Hz 3:50 to 3:59 No change to display: Display shows "Service 11" No audio interruption: Audio is a tone at 300 Hz |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.7 Test 5 - Sleep mode EWS selection | Not required. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.8 Test 6 - Sleep mode alert response | Not required. |
1a382157d5a45af8b664bdd32c73890e | 104 090 | 8.9 Test 7 - Concurrent alerts | • Objective: - To check the behaviour of the DUT with concurrent alert signalling. • Method: - Set signal generator 1 to a signal level of -50 dBm. - Set signal generator 2 to a signal level of -50 dBm. - Setup baseband encoders 1 and 2 and simultaneously play stream EWS8.eti on baseband encoder 1 and stream EWS9.eti on baseband encoder 2. Start the timing device. - Select "Service 1". - Listen to the audio and look at the display whilst monitoring the timing device. - When the timing device shows 3:00, select "Service 11". - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 7:55, cancel the alert playback. - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 8:40, cancel the alert playback. - Continue to listen and look at the display and monitor the timing device. - When the timing device shows 9:30, test 7 is complete. • Required result: - The audio output and display of the service label shall be as described in Table 11. Changes to audio shall occur within the first 5 s of each timing period (except where otherwise stated). Changes to the audio that include a period of silence between the stated tones are normal and expected. If audio artefacts (squawks, chirps, etc.) are heard, the test is failed. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 25 Table 11: Required response for test 7 Time displayed by the timing device (m:ss) Required response After service selection Display shows "Service 1" Audio is a mix of tones at 220 Hz and 330 Hz 0:30 to 0:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 0:40 to 0:49 Display changes to "Level 2 Start" Audio changes to mix of tones at 660 Hz and 770 Hz 0:50 to 1:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:10 to 1:19 Display changes to "Service 12" Audio changes to a tone at 600 Hz 1:20 to 1:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 1:30 to 1:39 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 1:40 to 1:49 Display changes to "Service 12" Audio changes to a tone at 600 Hz 1:50 to 2:09 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:10 to 2:19 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 2:20 to 2:29 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 2:30 to 2:39 Display changes to "Level 2 Start" Audio changes to a mix of tones at 660 Hz and 770 Hz 2:40 to 2:59 Display changes to "Service 1" Audio changes to a mix of tones at 220 Hz and 330 Hz 3:00 to 5:04 Display changes to "Service 11" Audio changes to a tone at 300 Hz 5:05 to 5:14 Display changes to "Service 12" Audio changes to a tone at 600 Hz 5:15 to 5:59 Display changes to "Service 11" Audio changes to a tone at 300 Hz 6:00 to 6:14 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz 6:15 to 6:29 Display changes to "Service 12" Audio changes to a tone at 600 Hz 6:30 to 6:59 Display changes to "Service 11" Audio changes to a tone at 300 Hz 7:00 to 7:14 Display changes to "Level 1 Start" Audio changes to a mix of tones at 440 Hz and 550 Hz within 7 s 7:15 to 7:44 Display changes to "Service 11" Audio changes to a tone at 300 Hz 7:45 to 7:54 Display changes to "Service 14" Audio changes to a tone at 1 000 Hz 7:55 to 8:29 Display changes to "Service 11" Audio changes to a tone at 300 Hz; no other tones are heard 8:30 to 8:39 Display changes to "Level 2 Start" Audio changes to a mix of tones at 660 Hz and 770 Hz 8:40 to 9:59 Display changes to "Service 11" Audio changes to a tone at 300 Hz; no other tones are heard ETSI ETSI TS 104 090 V1.1.2 (2025-02) 26 Annex A (normative): Product test streams A.1 EWS1.eti This file contains a 4-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 1", the EId is D001 and the ensemble contains the services shown in Table A.1. The alert schedule is shown in Table A.2. The location code sets are described in Table A.19. EWS1.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • b0b4787b212d4a1e79aabf2627c62d9e34f555ad296c949e43f476eb7d0c6ece Table A.1: Services in EWS1.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 1 96k AAC EEP-3A 220 330 Alert 1 D002 2 96k AAC EEP-3A 440 550 Service 3 D003 3 96k AAC EEP-3A 880 990 Alert 2 D004 4 96k AAC EEP-3A 1 100 1 210 Service 5 D005 5 160k MP2 UEP-3 660 770 Table A.2: Alerts in EWS1.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 1m05 SubChId = 2 10 2 L1Start 9 1m25 SubChId = 4 10 2 L1Start 9 LC1 1m55 SubChId = 2 10 2 L1Start 9 2m55 SubChId = 4 10 2 L1Start 9 LC1 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:00:05,120 (UTC) at the start of the file. A.2 EWS2.eti This file contains a 4-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 2", the EId is D001 and the ensemble contains the services shown in Table A.3. The alert schedule is shown in Table A.4. The location code sets are described in Table A.19. EWS2.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • 609a155c4e47d84929452b1d6736c18da210e2ef2a4ca6f2bccccef477c0da99 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 27 Table A.3: Services in EWS2.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 0 128k AAC EEP-3A 220 330 Level 1 Start D002 1 136k AAC EEP-3A 440 550 Level 1 Update D003 2 64k AAC EEP-3A 880 990 Level 1 Repeat D004 3 80k AAC EEP-3A 1 320 1 430 Level 1 Critical D005 4 96k AAC EEP-3A 1 760 1 870 Level 2 Start D006 5 56k AAC EEP-3A 660 770 Level 2 Update D007 6 72k AAC EEP-3A 1 100 1 210 Level 2 Repeat D008 7 88k AAC EEP-3A 1 540 1 650 Test D009 8 192k AAC EEP-3A 1 980 2 090 Table A.4: Alerts in EWS2.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m30 SubChId = 1 10 2 L1Start 0 LC1 0m50 SubChId = 1 10 2 L1Start 1 LC2 1m10 SubChId = 1 10 2 L1Start 2 LC3 1m30 SubChId = 1 10 2 L1Start 3 LC4 2m00 SubChId = 1 3 5 5 2 L1Start 4 LC5 2m20 SubChId = 1 10 2 L1Start 5 LC6 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:05:00 (UTC) at the start of the file. A.3 EWS3.eti This file contains a 4-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 3", the EId is D001 and the ensemble contains the services shown in Table A.5. The alert schedule is shown in Table A.6. EWS3.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • 0c73b2c7bb057abc370310a370913afee6b501ac4e269c107c2da19e69f1bc3f ETSI ETSI TS 104 090 V1.1.2 (2025-02) 28 Table A.5: Services in EWS3.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 0 128k AAC EEP-3A 220 330 Level 1 Start D002 1 136k AAC EEP-3A 440 550 Level 1 Update D003 2 64k AAC EEP-3A 880 990 Level 1 Repeat D004 3 80k AAC EEP-3A 1 320 1 430 Level 1 Critical D005 4 96k AAC EEP-3A 1 760 1 870 Level 2 Start D006 5 56k AAC EEP-3A 660 770 Level 2 Update D007 6 72k AAC EEP-3A 1 100 1 210 Level 2 Repeat D008 7 88k AAC EEP-3A 1 540 1 650 Test D009 8 192k AAC EEP-3A 1 980 2 090 Table A.6: Alerts in EWS3.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m30 SubChId = 1 10 2 L1Start 7 0m50 SubChId = 2 10 2 L1Update 7 1m10 SubChId = 3 10 2 L1Repeat 7 1m30 SubChId = 4 10 2 L1Critical 7 1m50 SubChId = 5 10 2 L2Start 7 2m10 SubChId = 6 10 2 L2Update 7 2m30 SubChId = 7 10 2 L2Repeat 7 2m50 SubChId = 8 10 2 Test 7 3m10 SubChId = 9 10 2 L1Start 7 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:15:00 (UTC) at the start of the file. NOTE 4: The alert at 3m10 points to a subchannel that does not exist in the configuration. A.4 EWS4.eti This file contains a 4-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 4", the EId is D002 and the ensemble contains the services shown in Table A.7. The alert schedule is shown in Table A.8. EWS4.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • 42c413395ac1048bb39c5e2d45b88e0accd61a8413483e6effe43561a35499b8 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 29 Table A.7: Services in EWS4.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 11 D011 1 96k AAC EEP-3A 300 300 Service 12 D012 2 96k AAC EEP-3A 600 600 Service 13 D013 3 128k AAC EEP-3A 1 200 1 200 Service 14 D014 4 88k AAC EEP-3A 1 000 1 000 Service 15 D015 5 80k MP2 UEP-3 2 000 2 000 Table A.8: Alerts in EWS4.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m30 EId = D001 10 L1Start 7 0m50 EId = D001 10 L1Update 7 1m10 EId = D001 10 L1Repeat 7 1m30 EId = D001 10 L1Critical 7 1m50 EId = D001 10 L2Start 7 2m10 EId = D001 10 L2Update 7 2m30 EId = D001 10 L2Repeat 7 2m50 EId = D001 10 Test 7 3m10 EId = D001 10 L1Start 7 3m30 EId = D001 10 L1Update 7 3m50 EId = D0FA 10 L1Repeat 7 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:15:00 (UTC) at the start of the file. A.5 EWS5.eti This file contains a 10-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 5", the EId is D001 and the ensemble contains the services shown in Table A.9. The alert schedule is shown in Table A.10. EWS5.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • f42c83a967874a693b077834dff45aa685a9e7e201cffbead2b4b2190bd68c12 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 30 Table A.9: Services in EWS5.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 0 128k AAC EEP-3A 220 330 Level 1 Start D002 1 136k AAC EEP-3A 440 550 Level 1 Update D003 2 64k AAC EEP-3A 880 990 Level 1 Repeat D004 3 80k AAC EEP-3A 1 320 1 430 Level 1 Critical D005 4 96k AAC EEP-3A 1 760 1 870 Level 2 Start D006 5 56k AAC EEP-3A 660 770 Level 2 Update D007 6 72k AAC EEP-3A 1 100 1 210 Level 2 Repeat D008 7 88k AAC EEP-3A 1 540 1 650 Test D009 8 192k AAC EEP-3A 1 980 2 090 From 9m00 to 9m18 reconfigurations introduce and then remove two services Service 2 D00A 9 64k AAC EEP-3A 2 200 2 310 Alert 3 D00B 10 96k AAC EEP-3A 2 420 2 530 Table A.10: Alerts in EWS5.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 2m00 SubChId = 1 3 5 10 2 L1Start 2 4m00 SubChId = 1 3 5 10 2 L1Start 4 6m00 SubChId = 1 3 5 10 2 L1Start 6 8m00 SubChId = 1 3 5 10 2 L1Start 8 9m00 SubChId = 10 3 10 5 2 L1Start 10 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:20:00 (UTC) at the start of the file. NOTE 4: The alert at 9m00 uses a subchannel introduced at the reconfiguration. A.6 EWS6.eti This file contains a 10-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 6", the EId is D002 and the ensemble contains the services shown in Table A.11. The alert schedule is shown in Table A.12. EWS6.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • a091832114451e7eec8915e7de0ce5207668eaea0b0a05829994bfc84b8d37d4 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 31 Table A.11: Services in EWS6.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 11 D011 1 96k AAC EEP-3A 300 300 Service 12 D012 2 96k AAC EEP-3A 600 600 Service 13 D013 3 128k AAC EEP-3A 1 200 1 200 Service 14 D014 4 88k AAC EEP-3A 1 000 1 000 Service 15 D015 5 80k MP2 UEP-3 2 000 2 000 Table A.12: Alerts in EWS6.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m00 ** No EWS ** 2m30 ** EWS ** 4m00 SubChId = 2 3 5 10 2 L1Start 5 6m00 SubChId = 2 3 5 10 2 L1Start 7 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:20:00 (UTC) at the start of the file. A.7 EWS7.eti This file contains a 10-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 7", the EId is D001 and the ensemble contains the services shown in Table A.13. The alert schedule is shown in Table A.14. EWS7.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • 4108c9f8a39762016c8896b516661613d4b4bf0ae8db31b7f8a9bbf5d32a263f Table A.13: Services in EWS7.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 0 128k AAC EEP-3A 220 330 Level 1 Start D002 1 136k AAC EEP-3A 440 550 Level 1 Update D003 2 64k AAC EEP-3A 880 990 Level 1 Repeat D004 3 80k AAC EEP-3A 1 320 1 430 Level 1 Critical D005 4 96k AAC EEP-3A 1 760 1 870 Level 2 Start D006 5 56k AAC EEP-3A 660 770 Level 2 Update D007 6 72k AAC EEP-3A 1 100 1 210 Level 2 Repeat D008 7 88k AAC EEP-3A 1 540 1 650 Test D009 8 192k AAC EEP-3A 1 980 2 090 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 32 Table A.14: Alerts in EWS7.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 1m00 SubChId = 1 3 5 10 2 L1Start 7 2m00 SubChId = 2 3 5 10 2 L1Update 7 3m00 SubChId = 3 3 5 10 2 L1Repeat 7 4m00 SubChId = 4 3 5 10 2 L1Critical 7 5m00 SubChId = 5 3 5 10 2 L2Start 7 6m00 SubChId = 6 3 5 10 2 L2Update 7 7m00 SubChId = 7 3 5 10 2 L2Repeat 7 8m00 SubChId = 8 3 5 10 2 Test 7 8m45 SubChId = 1 3 20 10 2 L1Start 7 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:30:00 (UTC) at the start of the file. A.8 EWS8.eti This file contains a 10-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 8", the EId is D001 and the ensemble contains the services shown in Table A.15. The alert schedule is shown in Table A.16. The location code sets are described in Table A.19. EWS8.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • 5e76c55ab51770d449b525560bb163dbf68fcd87e3ff5b334b9b7b26300bab5c Table A.15: Services in EWS8.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 1 D001 0 128k AAC EEP-3A 220 330 Level 1 Start D002 1 136k AAC EEP-3A 440 550 Level 1 Update D003 2 64k AAC EEP-3A 880 990 Level 1 Repeat D004 3 80k AAC EEP-3A 1 320 1 430 Level 1 Critical D005 4 96k AAC EEP-3A 1 760 1 870 Level 2 Start D006 5 56k AAC EEP-3A 660 770 Level 2 Update D007 6 72k AAC EEP-3A 1 100 1 210 Level 2 Repeat D008 7 88k AAC EEP-3A 1 540 1 650 Test D009 8 192k AAC EEP-3A 1 980 2 090 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 33 Table A.16: Alerts in EWS8.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m30 SubChId = 1 3 5 5 L1Start 7 0m40 SubChId = 5 3 5 5 2 L2Start 7 1m10 SubChId = 1 3 10 2 L1Start 6 LC2 1m10 EId = D002 10 L1Start 13 1m30 SubChId = 1 3 5 5 2 L1Start 7 1m40 EId = D002 10 L2Start 7 2m10 SubChId = 1 3 5 5 2 L1Start 13 2m10 EId = D002 5 L1Start 6 2m30 SubChId = 5 3 10 L2Start 7 2m40 SubChId = 1 3 25 65 2 L1Start 4 LC4 4m00 EId = D0FA 5 L1Start 2 4m52 SubChId = 5 3 10 2 L2Start 4 LC8 4m52 EId = D002 10 L1Start 3 LC8 5m00 EId = D0FA 5 L1Start 6 LC7 5m00 EId = D0FB 5 L1Start 7 LC6 5m05 SubChId = 1 3 10 2 L1Start 11 5m05 EId = D002 10 L1Start 10 6m00 SubChId = 1 3 5 10 2 L1Start 7 LC1 6m15 EId = D002 15 L1Start 14 LC5 6m15 EId = D0FA 10 L2Repeat 12 LC7 6m15 EId = D0FB 20 L1Update 13 LC6 7m00 SubChId = 1 3 5 10 2 L1Start 4 LC6 7m00 EId = D002 5 L2Repeat 14 LC7 7m45 EId = D002 30 L2Start 9 8m30 SubChId = 5 3 30 2 L2Start 1 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:40:00 (UTC) at the start of the file. NOTE 4: There are deliberate FIB errors for alert signalling from 7m00 to 7m02 which will delay receiver response and which are to test the capability to deal with this scenario. A.9 EWS9.eti This file contains a 10-minute long ETI (NI) test stream. The ensemble label is "EWS Stream 9", the EId is D002 and the ensemble contains the services shown in Table A.17. The alert schedule is shown in Table A.18. EWS9.eti is available at https://docbox.etsi.org/Broadcast/Open/EWSv1_1.zip. Checksum, SHA256: • e85540843defcb91df6487fcfeef82ffc70a2f3e2c89480f48ac7762c1471dd1 Table A.17: Services in EWS9.eti Service label SId SubChId Bit rate / codec Protection Audio (Hz, left channel) Audio (Hz, right channel) Service 11 D011 1 96k AAC EEP-3A 300 300 Service 12 D012 2 96k AAC EEP-3A 600 600 Service 13 D013 3 128k AAC EEP-3A 1 200 1 200 Service 14 D014 4 88k AAC EEP-3A 1 000 1 000 Service 15 D015 5 80k MP2 UEP-3 2 000 2 000 ETSI ETSI TS 104 090 V1.1.2 (2025-02) 34 Table A.18: Alerts in EWS9.eti Time point Alert Id Duration (s) Stage IId Location code set P T S E 0m30 EId = D001 5 L1Start 7 0m40 EId = D001 5 L2Start 7 1m10 SubChId = 2 3 10 2 L1Start 13 1m10 EId = D001 10 L1Start 6 LC2 1m30 EId = D001 5 L1Start 7 1m40 SubChId = 2 3 10 2 L2Start 7 2m10 SubChId = 2 3 5 5 2 L1Start 6 2m10 EId = D001 5 L1Start 13 2m30 EId = D001 10 L2Start 7 2m40 EId = D001 25 L1Start 4 LC4 4m00 EId = D0FA 5 L1Start 2 4m52 SubChId = 2 3 10 2 L1Start 3 LC8 4m52 EId = D001 10 L2Start 4 LC8 5m00 EId = D0FA 5 L1Start 6 LC7 5m00 EId = D0FB 5 L1Start 7 LC6 5m05 SubChId = 2 3 10 2 L1Start 10 5m05 EId = D001 10 L1Start 11 6m00 EId = D001 5 L1Start 7 LC1 6m15 SubChId = 2 3 15 2 L1Start 14 LC5 6m15 EId = D0FA 10 L2Repeat 12 LC7 6m15 EId = D0FB 20 L1Update 13 LC6 7m00 SubChId = 2 3 5 10 2 L2Repeat 14 LC7 7m00 EId = D001 5 L1Start 4 LC6 7m45 SubChId = 4 3 30 2 L2Start 9 8m30 EId = D001 30 L2Start 1 NOTE 1: The time points given are the time from the start of the file in minutes and seconds to the beginning of the Trigger signalling. NOTE 2: The durations given are for the Pre-trigger, Trigger (or OE Trigger), Sustain and End phases of each alert in seconds. NOTE 3: Ensemble time as provided by FIG 0/10 is 12:40:00 (UTC) at the start of the file. NOTE 4: There are deliberate FIB errors for alert signalling from 7m00 to 7m02 which will delay receiver response and which are to test the capability to deal with this scenario. ETSI ETSI TS 104 090 V1.1.2 (2025-02) 35 A.10 Location code sets This location code sets used in the ETI files are described in Table A.19. Location codes that correspond with the receiver location code are highlighted. Sub-coding is shown by hexadecimal digits within square brackets. Table A.19: Location code sets Set Location codes NFF Num bytes Encoding LC1 Receiver location Z1:91BB82 0 5 Z1:91BB82 LC2 Eight L6 codes surrounding the receiver location Z1:91BB81, Z1:91BB85, Z1:91BB86, Z1:91BB87, Z1:91BB83, Z1:91BB4D, Z1:91BB4E, Z1:91BB4F 0 12 Z1:91BB8[76531], Z1:91BB4[FED] LC3 Eight L6 codes, digits identical to the receiver location, but in different zones Z0:91BB82, Z10:91BB82, Z2:91BB82, Z41:91BB82, Z19:91BB82, Z20:91BB82, Z11:91BB82, Z12:91BB82 1 25 Z0:91BB82, Z10:91BB82, Z2:91BB82, Z41:91BB82, Z19:91BB82 0 15 Z20:91BB82, Z11:91BB82, Z12:91BB82 LC4 Eight L3 codes surrounding the receiver location. Z1:91A, Z1:916, Z1:917, Z1:924, Z1:928, Z1:92C, Z1:91F, Z1:91E 0 10 Z1:91[FEA76], Z1:92[C84] LC5 Nine L4 codes, including the receiver location. Z1:9288, Z1:9289, Z1:928C, Z1:928D, Z1:92C0, Z1:92C1, Z1:91F3, Z1:91BF, Z1:91BB 0 19 Z1:928[DC98], Z1:92C[10], Z1:91F3, Z1:91B[FB] ETSI ETSI TS 104 090 V1.1.2 (2025-02) 36 Set Location codes NFF Num bytes Encoding LC6 132 L5 codes, including the receiver location Z1:91B76, Z1:91B77, Z1:91B69, Z1:91B6A, Z1:91B78, Z1:91B79, Z1:91B7A, Z1:91B7B, Z1:92848, Z1:91B5E, Z1:91B5F, Z1:91B6C, Z1:91B6D, Z1:91B6E, Z1:91B6F, Z1:91B7C, Z1:91B7D, Z1:91B7E, Z1:91B7F, Z1:9284C, Z1:91B91, Z1:91B92, Z1:91B93, Z1:91BA0, Z1:91BA1, Z1:91BA2, Z1:91BA3, Z1:91BB0, Z1:91BB1, Z1:91BB2, Z1:91BB3, Z1:92880, Z1:92881, Z1:92882, Z1:91B95, Z1:91B96, Z1:91B97, Z1:91BA4, Z1:91BA5, Z1:91BA6, Z1:91BA7, Z1:91BB4, Z1:91BB5, Z1:91BB6, Z1:91BB7, Z1:92884, Z1:92885, Z1:92886, Z1:92887, Z1:92894, Z1:91B99, Z1:91B9A, Z1:91B9B, Z1:91BA8, Z1:91BA9, Z1:91BAA, Z1:91BAB, Z1:91BB8, Z1:91BB9, Z1:91BBA, Z1:91BBB, Z1:92888, Z1:92889, Z1:9288A, Z1:9288B, Z1:92898, Z1:91B9C, Z1:91B9D, Z1:91B9E, Z1:91B9F, Z1:91BAC, Z1:91BAD, Z1:91BAE, Z1:91BAF, Z1:91BBC, Z1:91BBD, Z1:91BBE, Z1:91BBF, Z1:9288C, Z1:9288D, Z1:9288E, Z1:9288F, Z1:9289C, Z1:9289D, Z1:9289E, Z1:91BD0, Z1:91BD1, Z1:91BD2, Z1:91BD3, Z1:91BE0, Z1:91BE1, Z1:91BE2, Z1:91BE3, Z1:91BF0, Z1:91BF1, Z1:91BF2, Z1:91BF3, Z1:928C0, Z1:928C1, Z1:928C2, Z1:928C3, Z1:928D0, Z1:928D1, Z1:928D2, Z1:928D3, Z1:91BD4, Z1:91BD5, Z1:91BD6, Z1:91BD7, Z1:91BE4, Z1:91BE5, Z1:91BE6, Z1:91BE7, Z1:91BF4, Z1:91BF5, Z1:91BF6, Z1:91BF7, Z1:928C4, Z1:928C5, Z1:928C6, Z1:928C7, Z1:928D4, Z1:928D5, Z1:928D6, Z1:91BF8, Z1:91BF9, Z1:928CA, Z1:928CB, Z1:928D8, Z1:928D9, Z1:928CF, Z1:928DC 3 24 Z1:91B7[FEDCBA9876], Z1:91B6[FEDCA9], Z1:9284[C8], Z1:91B5[FE] 2 24 Z1:91B9[FEDCBA9765321], Z1:91BA, Z1:91BB, Z1:9288[FEDCBA987654210], Z1:928DC 1 24 Z1:9289[EDC84], Z1:91BD[76543210], Z1:91BE[76543210], Z1:91BF[9876543210] 0 16 Z1:928C[BA76543210], Z1:928D[986543210], Z1:928CF LC7 As LC6 but excluding the receiver location -:- Z1:91BB8 -:- 3 24 Z1:91B7[FEDCBA9876], Z1:91B6[FEDCA9], Z1:9284[C8], Z1:91B5[FE] 2 22 Z1:91B9[FEDCBA9765321], Z1:91BA, Z1:91BB[FEDCBA976543210], Z1:9288[FEDCBA987654210] 1 24 Z1:9289[EDC84], Z1:91BD[76543210], Z1:91BE[76543210], Z1:91BF[9876543210] 0 20 Z1:928C[BA76543210], Z1:928D[986543210], Z1:928CF, Z1:928DC ETSI ETSI TS 104 090 V1.1.2 (2025-02) 37 Set Location codes NFF Num bytes Encoding LC8 As LC6 but all codes are Zone 7 not Zone 1 Z1:- Z7:- 3 24 Z7:91B7[FEDCBA9876], Z7:91B6[FEDCA9], Z7:9284[C8], Z7:91B5[FE] 2 24 Z7:91B9[FEDCBA9765321], Z7:91BA, Z7:91BB, Z7:9288[FEDCBA987654210], Z7:928DC 1 24 Z7:9289[EDC84], Z7:91BD[76543210], Z7:91BE[76543210], Z7:91BF[9876543210] 0 16 Z7:928C[BA76543210], Z7:928D[986543210], Z7:928CF ETSI ETSI TS 104 090 V1.1.2 (2025-02) 38 History Document history V1.1.1 September 2024 Publication V1.1.2 February 2025 Publication |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 1 Scope | The present document defines an Emergency Warning System (EWS) for DAB which features an additional FIG for signalling the identity, status and location of an emergency with the ability for suitably equipped receivers to wake from a low-power sleep mode to provide an audio alert message targeted to the specific geographical area of concern. The rules of implementation ensure that a reliable and consistent experience will be delivered for digital radio listeners; they provide implementation details for how the Fast Information Channel (FIC) signalling is used and how receivers will interpret and behave in response to receiving the FIC signalling. The present document is complemented by ETSI TS 104 090 [i.1], which sets out the testing required to be performed on receivers to demonstrate conformance to correct operation. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 2 References | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at https://docbox.etsi.org/Reference/. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI EN 300 401 (V2.1.1): "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile, portable and fixed receivers". |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 104 090: "Digital Audio Broadcasting (DAB); Emergency Warning System (EWS); Minimum requirements and test specifications for receivers". [i.2] OASIS Standard: "Common Alerting Protocol, V1.2, 01 July 2010". |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 3 Definition of terms, symbols and abbreviations | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 3.1 Terms | For the purposes of the present document, the following terms apply: alert: information about a situation or incident with the potential of affecting life and well-being of humans ETSI ETSI TS 104 089 V1.1.1 (2024-09) 8 alert area: geographic area to which an alert applies alert audio: short audio element containing information about an emergency situation alert group: collection of FIG 0/15 instances that comprise the Trigger phase signalling for all simultaneous alerts alert message: alert audio and optional associated multimedia data service components describing the emergency situation alert set: collection of FIG 0/15 instances that comprise the Trigger or Pre-trigger phase signalling for one alert Change Event Indication (CEI): set of FIG fields with particular values to indicate a change of database content for certain service information features database entry: part of the service information addressed by a database key database key: set of FIG fields that sub-divide a database for certain service information features Emergency Warning System (EWS): infrastructure forming a signal chain to provide emergency warnings to the general public incident: cause and subject of one or several alerts, possibly long-lived and evolving over time ongoing alert: alert that is no longer providing switching information power mode: power-on state of a receiver NOTE: Power modes are "sleep", "monitor" and "audio". tuning memory: information stored in a receiver from previous tuning actions providing details of ensembles, tuning frequencies and services service list: feature of a radio receiver where a list of service elements is used for service selection synchronized alert message: alert message timed to enable sleeping receivers to respond at the beginning of the alert message NOTE: These alert messages start when the seconds count is 0. tracked incident: incident that is recognized from the source data, either directly or indirectly, and so can support user controls for alert dismiss user controls: all elements of a user interface of a radio receiver that are used to display service information and provide for user control |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 3.2 Symbols | Void. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: C/N Current/Next CEI Change Event Indication DAB Digital Audio Broadcasting EId Ensemble Identifier EWS Emergency Warning System FIB Fast Information Block FIC Fast Information Channel FIG Fast Information Group Id Identifier IId Incident Identifier MCI Multiplex Configuration Information ETSI ETSI TS 104 089 V1.1.1 (2024-09) 9 OE Other Ensemble P/D Process/Discard SId Service Identifier SIV Service Information Version |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 4 Overview | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 4.1 Introduction | Emergency warning systems take many forms, originating with the ringing of bells, messages from town criers and activation of warning sirens. In the modern age with extensive communication networks seemingly providing endless connectivity, it is easy to forget that natural disasters often play havoc with infrastructure that is not specifically designed to withstand the onslaught. Alerting the public to situations that represent a danger to health and well-being has long been a feature of broadcasting - the reach and immediacy of the medium, particularly the radio medium which is consumed both in the home and workplace, and on the move - along with generally high levels of trust, particularly for public service media, and very high reliability, make radio an excellent platform for alerting the public. The DAB EWS defined in the present document provides an effective way to provide a critical public warning function by utilizing the inherent reliability of DAB transmission infrastructure. The DAB EWS provides alert messages which consist primarily of audio information about the nature and extent of the emergency and instructions on how to react. The alert message may also include textual information, as the dynamic label, and optionally additional multimedia content when linked to the audio service. The alert message can be targeted to a specific geographic area such that receivers within the signalled alert area will respond, even when tuned to other DAB services, other media or when in a very low-power sleep mode, yet receivers outside the signalled alert area will not respond, allowing the user to continue with their chosen activity. The source and format of emergency information that feeds into the DAB EWS is outside the scope of the present document. It is expected that the source information for the alert messages will come from an appropriate safety authority, and that the services that carry the alert messages will be managed by appropriately trained and authorized providers. The DAB EWS works best when all DAB ensembles participate in the system. The design makes that straightforward because communication between ensembles is provided over-the-air to permit the relaying of EWS signalling. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 4.2 System architecture | The DAB EWS consists of one or more DAB ensembles that carry specific signalling that both identifies the ensembles as participating in an EWS and also provides the signalling information to allow receivers to respond. Some ensembles will carry services that provide emergency alert messages, whilst others will carry only signalling information to redirect receivers to the ensemble carrying an alert message. In order for the geographic filtering to work, every receiver needs to know where it is. The DAB EWS is designed to use a specifically designed location coding system that is light weight and highly efficient. It allows the user to provide the receiver with its location when it is set up. More sophisticated receivers may be able to derive their location themselves, for example using a wireless link, a GNSS receiver, or some other means. The location coding system permits even the simplest receiver to be able to determine if it is in or out of an emergency alert area by a simple comparison of integers. An example of the use of location codes to describe and alert area is given in annex C. The content of the alert messages is not standardized but will typically include a description of the geographic area affected, the nature of the emergency and instructions on what to do and when to expect changes. Alert messages will be heard both by listeners who were already listening to the service before the alert message began and by those who have been redirected to it. The content of the alert message should therefore be crafted to take account of these different audience segments. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 10 Because an emergency situation will generally develop over time, each incident is likely to consist of a number of alert messages. This sequence of messages can be linked together using an identifier, and this linking permits receiver manufacturers to offer user options to restrict responding to alert messages in specific ways, for example, not playing an alert message that has already been heard. These user options will only be available for a particular incident if the signalling permits it. To reduce the chances that portions of alert messages will be missed by receivers that have a very low-power sleep mode, the DAB EWS requires that receivers are synchronized to DAB time. This means that all sleeping receivers will check for emergency alerts at the same time, every minute. Therefore, the system performs best when alert messages begin when sleeping receivers are checking for alerts. The system is optimized for this mode of operation. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 4.3 Receiver behaviour | The required receiver behaviour is defined in clause 7 of the present document. Manufacturers are able to check that their products conform to the requirements by performing the tests specified in ETSI TS 104 090 [i.1]. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 5 EWS ensembles | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 5.1 Baseline requirements | An ensemble that participates in an EWS shall conform to the requirements of ETSI EN 300 401 [1]. It shall signal the date and time using FIG 0/10 in the long form. The date-time information provided in FIG 0/10 shall be accurate, which requires connection to a reliable source of real-time, such as GNSS or NTP. The time signalled by FIG 0/10, known as ensemble time, shall be the basis for all EWS signalling, which uses FIG 0/15. The participating ensemble shall provide FIG 0/15 (see annex E) in order to signal the status of alerts in the ensemble and in other ensembles, as defined in clause 6.6. The content of the FIG 0/15 shall be appropriate to the alert requirements. When no alert messages are being signalled, the ensemble signals its participation in an EWS with FIG 0/15 heartbeat signalling. The P/D flag in the type 0 header of FIG 0/15 is used for fine synchronization of receivers with a sleep function. The P/D flag of FIG 0/15 shall be set to 0 (Process) for every FIG 0/15 sent when the ensemble time has a seconds count of 0 to 29 and shall be set to 1 (Discard) for every FIG 0/15 sent when the ensemble time has a seconds count of 30 to 59. The null symbol of the transmission frame provides the time reference for the time carried in FIG 0/10 (see ETSI EN 300 401 [1], clause 14.3.3). All the 12 FIBs of a transmission frame shall be considered to relate to the same time reference (i.e. the seconds count for FIG 0/15 is the seconds value of the time reference). An ensemble that provides alert messages shall provide FIG 0/15 signalling for each alert message it carries. A participating ensemble that overlaps the coverage area of another participating ensemble shall provide FIG 0/15 signalling for every alert message in the overlapping other ensembles. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 5.2 Information sources | An EWS ensemble that carries alert messages takes responsibility for the content and status settings of alert messages. The source or sources of information that are used to create an alert message and its signalling are not defined by the present document, but the following types of information are typically required: • alert area; • severity of alert; • description of the current event; • recommended actions; • timeframe for development. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 11 The ensemble shall make available the information about an alert message to other EWS ensembles with overlapping coverage areas. The present document defines a standardized way for the information exchange to take place using the FIC, but other methods are also permitted. An EWS ensemble that provides signalling of alert messages in other ensembles shall use the information provided by the EWS ensemble that carries the alert message. This may be done by receiving and processing the FIC of the ensemble that carries the alert message, or by another method. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 5.3 Receiver considerations | Ideally, all ensembles covering a particular location will participate in the DAB EWS. However, it is recognized that there may be reasons why this does not happen. The services carried in ensembles that do not participate should not be excluded from the receiver's service list, but the user shall be made aware when tuned to such services if the EWS function is inoperable (e.g. if the receiver has only a single tuner). |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6 Alert signalling | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.1 Introduction | The need to signal emergency warning alerts is unpredictable, and it is possible for there to be different incidents occurring in the same geographical location at the same time. However, although these incidents may be simultaneous, only one alert message can be carried in an ensemble at a time: therefore management of the timing of the alert messages is needed. Alert messages are carried in one ensemble but shall be signalled in all ensembles that participate in the EWS that provide coverage of the alert area. Since receivers can only play back one alert message at a time, consideration should be given as to whether coordination of alerts amongst ensembles is needed, and if so, how such coordination is managed. Such considerations are outside the scope of the present document. The signalling rules and receiver behaviour rules mean that receivers will play an alert in the tuned ensemble in preference to any alerts in other ensembles that are signalled at the same time. A given ensemble may have more than one incident active at any given time, but it shall have only one alert message active at a time. It may signal one or more alerts that are occurring in other ensembles at any time, including when it is signalling an alert message of its own. Alert providers have complete editorial freedom in the composition of the alert message and are encouraged to provide dynamic labels alongside the audio. SlideShows and other multimedia content is also possible, although the likely short duration of the alert message should be considered when allocating bitrate to such additional features. The impact and intelligibility of an alert message is likely to reduce if users connect to it part-way through. For this reason, alert providers are able to indicate at which point after the first 5 seconds of the alert message that receivers will no longer evaluate it for selection. Domestic EWS receivers are designed to respond to certain alerts even when they are in a low-power sleep state. To minimize power consumption, such receivers only monitor the DAB signal once per minute. In order to ensure that alert messages can be heard in full, even by sleep state receivers, the EWS has been designed to use real time to synchronize the evaluation of alerts by sleep state receivers. This means that all receivers use the time, as provided by FIG 0/10, to set their monitoring cycle and all receivers will be ready to evaluate EWS signalling at the beginning of every minute, i.e. when the seconds count is equal to 0. Alert providers are therefore strongly encouraged to begin their alert messages at the very beginning of the minute in order that the maximum population of receivers will react and play back the entire alert message: these alerts are termed synchronized alerts. Not all alert messages may be deemed of sufficient severity to wake-up receivers that are in a sleep state. Alerts are classified into two severity levels: Level 1 alerts are evaluated by all receivers, whereas Level 2 alerts are only evaluated by receivers that are awake. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 12 The EWS system allows alert messages to begin at any time and receivers that are awake and tuned to an EWS ensemble, or which have an additional tuner to monitor other ensembles within the alert area, will respond in a timely way. However, receivers that are in a sleep state will only respond at the start of each minute to Level 1 alerts that are providing the necessary signalling: they will ignore all Level 2 alerts. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.2 Source data | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.2.1 Introduction | The data for an EWS may come from many different types of agency. There may be a single national emergency centre, or there may be multiple agencies providing different kinds of data concerning weather events, security events, industrial accidents, etc. Wherever the data come from, they need to include sufficient detail for the composition of a coherent audio message and to set the values of the various data fields in the FIG 0/15 signalling. Emergency situations tend to develop over time. After a situation has been reported initially it may evolve and warrant further alert messages over the course of several hours or days. Different users will react differently to the content of the alert messages: for some, the information is very relevant and they will want to follow every development; for others, the information may be considered not relevant at some point due to particular circumstances. Provision is therefore made to allow users some control over the way that their receiver evaluates alerts. This provision comprises two parts: the Stage and the Incident Identifier. The Stage is used by the alert provider to signal the severity and development of the incident; the Incident Identifier to link together all the alerts that comprise a single incident. Emergency situations are relevant to a specific geographical area and provision is made to provide alert area information to allow receivers to respond to relevant alerts. When alert area information is provided, receivers outside the alert area will not respond to the signalling. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.2.2 Incident identification | The ensemble that carries an alert message is responsible for setting the Incident Identifier. It is expected that in some cases, the source data will provide a reliable source of incident identification and the alert provider can use this information to allocate and maintain the Incident Identifier. In other cases, the alert provider may be able to use contextual information from the source data to associate different alerts to the same incident and so allocate and maintain the value. For these cases, known as tracked incidents, each subsequent alert provided for the same incident shall have the same Incident Identifier, and all stages (except Test) can be assigned to a particular alert. Each ensemble can have a maximum of 16 tracked incidents due to the limit of the signalling. If all 16 values of the IId have been allocated and a 17th incident begins, the alert provider shall decide which of the existing incidents shall cease to be tracked and the IId used for that incident shall be reused. If alerts cannot be associated to an incident, then the Incident Identifier shall be assigned an arbitrary unused value, and each alert shall be signalled using only the stages Level 1 Start or Level 2 Start. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.2.3 Incident stage | When incident identification is supported by the alerting ensemble, users may be able to instruct their receiver to ignore alerts which are signalled as a repeat or update of an ongoing incident. This may be an appropriate action if the user considers that whilst the alert is geographically close to them, they are not in danger, for example, by being on high ground despite a localized flooding incident. An incident may develop such that its severity decreases or increases, and provision is made to allow alert providers to control the response of the receiver. Typically, all receivers within the alert area will be targeted, regardless of the power state of the receiver, but an incident may develop in such a way that using the wake-up function is seen to be overly invasive. Alternatively, the incident may develop such that it is imperative to ensure that all receivers will evaluate the alert. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 13 To support user functionality and different levels of alert severity, the stage of the alert is signalled. Incidents begin at Level 1 Start if they are targeted at all receivers, or Level 2 Start if they are targeted at only those receivers that are already outputting audio. The Incident Identifier associated with this Start stage is then used for all subsequent alert messages for this incident. When a Start stage is received, receivers clear the alert user controls for that Incident Identifier. Incidents may move between Levels as they develop. An alert provider may use a Repeat stage to indicate that the same information has already been provided by the previous alert message associated with this Incident Identifier. Receivers with user control functionality can then identify repeated alert messages. An alert provider may use an Update stage to indicate that new information about an incident that is ongoing is contained in the alert message. Receivers with user control functionality that permits entire incidents to be skipped can then act appropriately. The choice of whether a Repeat stage or Update stage is appropriate to an ongoing incident is an editorial decision by the alert provider, but whenever the information about an incident changes, the Update stage should be signalled. The Level 1 Critical stage overrides all user alert controls and ensures that the alert message is evaluated by all receivers, regardless of their power state. However, it does not clear the user alert controls: for this function the Level 1 Start stage is used. EXAMPLE 1: An unexploded wartime bomb is discovered during construction of a new building. The device is found in the early afternoon. After examination by police and bomb disposal experts, it is decided to evacuate only a part of the city, but to inform the whole city as traffic disruption will result. The first alert of the incident is signalled as Level 1 Start with location codes covering the whole city. As the situation develops and more knowledge is gained, alerts at stages Level 1 Update and Level 1 Repeat are signalled. Listeners that feel they are not affected - because they live in another part of the city and do not plan to leave their home for a while - can use the dismiss function of their receiver to stop further interruptions. As night falls, the incident is still ongoing, but the majority of city inhabitants have been informed and so know to stay away from the evacuation area. It is decided at 21:00 to only provide alerts to those already listening to the radio, whichever service they choose, and so subsequent alerts are signalled using Level 2 Update or Level 2 Repeat stages. At 07:30 the following morning, further checking of the site by bomb disposal experts reveals a second device. It is decided that this warrants a change back to alert all receivers, even those whose owners had dismissed the incident, and so an alert is signalled using the Level 1 Critical stage. After two hours, the decision is taken to move to Level 2 alerts again. EXAMPLE 2: In a low mountain range, the weather forecast predicts heavy rainfall for the next 3 days. There is a risk of local flooding. In the following days, the radio warns about the upcoming weather situation as part of the normal news broadcasts without EWS signalling. The population is called upon to pay greater attention. Towards midday on the third day it becomes clear that the heavy rainfall will lead to widespread flooding, particularly in settlements at the confluence of side valleys. The first alert for this weather event occurs at 15:00, signalled as Level 1 Start with location codes that include the affected settlements. As precipitation continues to increase, several Level 1 Update and Level 1 Repeat messages are sent. Towards the evening, the weather situation seems to ease somewhat, and further alert messages use Level 2 Update and Level 2 Repeat stages. Evacuations have so far only been necessary in a few parts of the affected settlements and have taken place in good time before localized flooding occurred. At 02:00 the threat situation suddenly increases dramatically. Several water waves enter a reservoir at the same time, and a technical failure of a weir gate together cause the water level in the reservoir to rise dangerously. There is imminent danger of a dam bursting, which would result in a 10 m-high flood-wave downstream. A new alert message is issued for the immediate evacuation of the endangered valleys as Level 1 Critical and with a significantly expanded alert area using a bigger location code set. There is a risk of widespread flooding along all downstream valleys, which could result in numerous deaths. The situation remains very critical for the next 10 hours, and all alert messages are issued and repeated at regular intervals as Level 1 Critical. The situation is later mitigated as it becomes possible to reduce the water pressure in the reservoir by controlled release of water. Once this is complete, further alert messages are signalled as Level 2 Update and Level 2 Repeat, which provide further information about the current status of the danger until the situation changes back to normal. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 14 EXAMPLE 3: At around 21:00, simultaneous suicide terror attacks take place at three entrance gates to a fully occupied football stadium. Initially, a Level 1 Start message with location codes for the area of the stadium and the immediate surroundings is sent. It reports the current situation and asks the population to avoid the area around the stadium or to remain in the stadium until further notice. The developing situation in the area around the stadium is then reported at short intervals of a few minutes as Level 1 Update or Level 1 Repeat messages with unchanged location codes. At 21:20, in another, more distant part of the city, further attacks take place at the same time in several places, including a theatre. For these new events, the authority triggers a new warning Level 1 Start message with location codes that match these attack locations. Since a direct connection to the previous events at the football stadium is not immediately apparent, the new warning message is sent under a different Incident Id. Here too, Level 1 Update or Level 1 Repeat messages are sent out at regular intervals as the situation develops. As the night progresses, more terror attacks occur at various locations in the city, making it clear to the authorities that all the events are connected. Therefore, the next warning message is sent as Level 1 Start using a new Incident Id, and with location codes that cover the entire city area. The following alert messages are sent as Level 1 Update and Level 1 Repeat. As the situation eases, further warnings are sent as Level 2 Update and Level 2 Repeat until the warning situation has reduced to such an extent that alert messages no longer need to be sent. A final Level 2 Update message is issued informing the population that there is no longer an immediate risk of attacks, but that they should continue to remain vigilant. An additional stage, the Test stage, may be used to indicate that the alert message is part of a test exercise for special receivers. These alerts are not evaluated by consumer receivers. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.2.4 Alert area | By default, the alert area is the entire coverage area of the ensemble carrying the alert message: in this case no location codes are signalled. However, a specific alert area can be signalled by including location codes. To permit complex alert areas to be signalled, multiple location codes can be provided: the alert area is the sum of all the areas described by the set of location codes signalled. There is a limit to the total number of location codes that can be provided for an alert, which is limited by the maximum number of bytes that the location codes can occupy in a single FIG 0/15 instance and the maximum of four FIG 0/15 instances that are permitted in an alert set. The alert area provided in the source data has to be transformed from its incoming format to the DAB location code format and within the limits of capacity. Annex D provides a generic method to make the transformation. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3 Forms of FIG 0/15 | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3.1 Introduction | FIG 0/15 is used for all aspects of signalling the EWS. The definition of the structure of FIG 0/15 is given in annex E. The P/D flag shall be set according to clause 5.1. An alert message is carried in one of the subchannels of the ensemble. The audio content of the alert message, the timing and the setting of all the control and information fields of the FIG 0/15 signalling is the responsibility of the alert provider and is derived from the incoming alert source data. Other ensembles that also carry signalling for the same alert derive the timing and setting of all the control and information fields of their FIG 0/15 signalling from that given by the alert provider, either through an EWS management system or from off-air monitoring. The signalling of an alert message has four phases, although some phases may be omitted in specific circumstances. The phases are as follows: • Pre-trigger: may be used to deliver alert signalling to other ensembles, not evaluated by consumer receivers; • Trigger: used to provide the identity, status and location information of the alert so that receivers can evaluate whether the alert message shall be played; • Sustain: used to signal the continuation of the alert message after the Trigger phase has ended; • End: used to signal the end of the alert message. For other ensembles, only the Trigger phase signalling is provided. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 15 When there are no alerts active in the ensemble and no alerts in Trigger phase in other ensembles with overlapping coverage areas, the "no alert" form, known as the Heartbeat, is signalled. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3.2 Heartbeat form | In the Heartbeat form, the type 0 field of FIG 0/15 is empty. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3.3 Trigger form | In the Trigger form, the type 0 field of FIG 0/15 contains the Id field and the Status field and may contain a number of Location codes. Up to four FIG 0/15 instances of the Trigger form may be used to fully describe the alert area: the content of the Id field and Status field (except for the Last flag) shall be identical for each instance. Collectively these instances are known as an alert set. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3.4 Pre-trigger form | The Pre-trigger form may be used for inter-ensemble communication. It is identical to the Trigger form except for an additional field to define the start second. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.3.5 Sustain and End form | In the Sustain and End form, the type 0 field of FIG 0/15 contains the Id field only. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.4 Describing an alert message carried in the ensemble | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.4.1 Introduction | Signalling is used to provide Trigger phase information that allows receivers to evaluate whether the alert message shall be played. Trigger signalling is provided for a minimum of 5 seconds for every alert. Alert providers can decide the point where receivers will stop evaluating whether an alert will be played. At this point, the signalling changes from Trigger phase to Sustain phase. At the end of the alert message, End phase signalling is provided. To permit other ensembles to provide correctly timed OE Trigger phase signalling, Pre-trigger phase signalling may be provided. Alternatively, an EWS management system may be used. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.4.2 Id field | The Id field contains the 2-bit phase field and the 6-bit SubChId field. It is present for all signalling phases. For the "Pre-trigger" phase only, it contains two additional fields, the 2-bit Rfa field and the 6-bit Sec field. The Phase field shall indicate the phase of the alert. The SubChId field shall indicate the subchannel in the ensemble that carries the alert message. If the subchannel is introduced in a reconfiguration preceding an alert, the reconfiguration shall be completed by the time the Trigger phase signalling starts. The Rfa field, when present, shall be set to 0. The Sec field, when present, shall indicate the seconds count at which OE Trigger phase signalling shall start. The special value 63 shall be used to indicate an alert starting at seconds count 0 with a Trigger phase duration of 5 seconds. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 16 |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.4.3 Status field | The Status field shall only be present when the Phase field is set to "Pre-trigger" or "Trigger". The Status field contains the Last flag, the Stage field and the Incident Identifier (IId) field. The Last flag provides a control function and is not part of the alert information: it shall be set according to clause 6.6. The Stage field indicates the stage of an incident. The first alert of an incident shall set the stage to either Level 1 Start, which targets all receivers, or Level 2 Start, which targets only receivers already outputting audio. If the alert is part of a tracked incident, then subsequent alerts for the same incident, identified by the IId, may set the Stage field to any value except Test (see clause 6.2.3). The Stage field is also used to indicate a test alert: the stage Test shall only be used for specific test activities. The Incident Identifier (IId) provides the reference to an incident. The IId shall remain constant throughout the entire lifecycle of the incident as it permits receivers to provide users with options to ignore repeated and/or updated alert messages in an ongoing incident. The ensemble provider shall manage the use of IIds in the ensemble (see clause 6.2.2). The Incident Identifier has no meaning for test alerts and may be used as private data by the test provider. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.4.4 Location codes | Location codes shall only be present when the Phase field is set to "Pre-trigger" or "Trigger". The alert area is signalled using zero (complete ensemble coverage area) or more location codes, as defined in annex F. Location codes are of variable length. Location codes shall occupy a maximum of 25 bytes in any given FIG 0/15 instance. An alert area may require between one and four FIG 0/15 instances to describe, known as an alert set. The FIG 0/15 coding of location codes allows for efficient transport by the use of sub-coding: the translation of an alert area into a set of location codes that fulfil the limit of four FIG 0/15 instances is illustrated in annex D. The NFF field is not part of the location code but is used to help receivers determine the completeness of the alert set; the last FIG 0/15 instance in an alert set has NFF = 0. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.5 Describing an alert message in other ensembles | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.5.1 Introduction | Other ensembles signalling is used to provide Trigger phase information that allows receivers to evaluate whether the alert message in the other ensemble shall be played. Only Trigger phase signalling is provided for alerts in other ensembles with coverage areas that overlap the coverage area of the ensemble. The information to generate the Trigger phase signalling may come from an EWS management system or it may come from off-air monitoring device(s) tuned to other ensembles and decoding their Pre-trigger and Trigger phase signalling. An ensemble that monitors the signal of another ensemble can use the received Pre-trigger phase FIG 0/15 information, when available, to construct the FIG 0/15 OE signalling and provide it from the seconds count indicated in the Sec field. OE Trigger phase signalling shall continue to be provided whilst Trigger phase signalling for the alert is being received. NOTE: Due to processing delays, OE Trigger phase signalling may be provided for a short period longer than the Trigger phase signalling in the ensemble carrying the alert message. If an EWS management system is used, the information is provided by the management system ahead of time instead of providing Pre-trigger phase signalling and precise timing can be assured. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.5.2 Id field | The Id field is set to the Ensemble Identifier (EId) of the ensemble that carries the alert message. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 17 |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.5.3 Status field | The Stage field and the Incident Identifier (IId) shall be set to exactly the same values as provided by the ensemble carrying the alert message. The Last flag provides a control function and shall be set according to clause 6.6. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.5.4 Location codes | The Location codes shall be set to exactly the same values as provided by the ensemble carrying the alert message. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.6 Insertion rules for FIG 0/15 | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.6.1 Introduction | The EWS provides a low-power monitoring function for receivers which is synchronized to real time. The insertion rules for FIG 0/15 are designed to allow receivers to evaluate alerts as efficiently as possible. The nominal repetition rate of FIG 0/15 is all information once per second, but due to the variable number of simultaneous alerts at any given time, and the variable number of FIG 0/15 instances needed to signal each alert, the FIC capacity used by FIG 0/15 may vary considerably. One or more FIBs might be used per transmission frame to carry FIG 0/15, and these FIBs can contain one or more FIG 0/15 instances. The timing of FIG 0/15 at the minute's edge is important as this is the time when sleeping receivers enter monitor mode. It is strongly recommended that transmission equipment ensures that FIG 0/15 is inserted into the first transmission frame that starts at or after the minute's edge in order to allow receivers in monitor mode to evaluate the alert situation as quickly as possible. More generally, inserting FIG 0/15 into the first transmission frame of each second is recommended. A new alert message can only begin in an ensemble when there is no alert message already active; alerts may begin in other ensembles at any time. Alerts may provide Pre-trigger phase signalling, which shall begin 5 seconds before the start of the Trigger phase signalling for the alert, to allow other ensembles to provide OE Trigger phase signalling from the start of the alert message. Pre-trigger and Trigger phase signalling is provided using alert sets of between one and four instances of FIG 0/15. At any given moment, there may be an alert message being carried in the ensemble (in either Trigger phase or Sustain phase), an alert message about to start (in Pre-trigger phase), an alert message just ended (in End phase), or no alert message at all. Similarly, in other ensembles with overlapping coverage areas, there may be one or more alert messages in Trigger phase that need signalling in this ensemble as OE alerts. Alerts in Trigger phase in the tuned ensemble and in overlapping other ensembles shall be composed into an alert group. The first alert set of the alert group shall be the alert set corresponding to the tuned ensemble (if it exists), with the alert sets from other ensembles following in any order. The alert group will be empty whenever there are no alerts in Trigger phase. The alert group shall be composed at the start of each minute, and alert groups are generally composed at the start of each subsequent second, corresponding with the nominal repetition rate. However, for the first 5 seconds of any alert, the signalling of alert groups is continuous: in this case the next alert group shall be composed immediately after the final FIG 0/15 of the previous alert group has been signalled. It is recommended to allocate sufficient space in the FIC for alert groups to be completely signalled in less than one second, but if this is not possible, for example when the number of concurrent alerts is high, the alert group may require more than one second to transmit: in this case the next alert group shall be composed immediately after the final FIG 0/15 of the previous alert group has been signalled. Once the alert group is able to be completely signalled in less than one second again, the composition of the alert group returns to the start of each second. For every composed alert group, FIG 0/15 signalling shall be provided according to the rules described in this clause 6.6. Examples of FIG 0/15 insertion are given in annex B. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 18 |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.6.2 Alert group is empty | When the alert group is empty it means that there are no alerts that require evaluation by receivers and consequently no Trigger phase signalling to provide (tuned or other ensembles). If there is an ongoing alert message in the ensemble, then Sustain phase signalling shall be provided at a nominal repetition rate of once per second. The C/N flag shall be set to 1. If an alert message has just ended, then End phase signalling shall be provided at a nominal repetition rate of once per transmission frame for 2 seconds. The C/N flag shall be set to 1. If neither of these situations exists, then the Heartbeat form of FIG 0/15 is signalled at a nominal repetition rate of once per second. In addition, if signalling is used for inter-ensemble communication and an alert message will begin in the ensemble, then Pre-trigger phase signalling shall be provided at a nominal repetition rate of the complete alert set once per second for three seconds and at an insertion rate of one FIG 0/15 instance per transmission frame. The Last flag of the last instance of FIG 0/15 of the alert set shall be set to 1; the Last flag of all other instances of FIG 0/15 of the alert set shall be set to 0. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.6.3 Alert group is not empty | When the alert group is not empty it means that there are alerts that require evaluation by receivers and consequently Trigger phase signalling shall be provided (tuned and/or other ensembles). Except when the seconds count is 59, the alert group shall be signalled completely. When the seconds count is 59, alert group signalling shall be terminated before the end of the second, regardless of whether the entire alert group has been signalled to ensure that receivers entering monitor mode operate correctly. The Last flag of the last instance of FIG 0/15 of the alert group shall be set to 1; the Last flag of all other instances of FIG 0/15 of the alert group shall be set to 0. The alert group shall be signalled at a minimum insertion rate of one FIG 0/15 instance per transmission frame. In addition to the alert group signalling, the following signalling shall also be provided as required: • if there is an ongoing alert message in the ensemble, then Sustain phase signalling shall be provided at a nominal repetition rate of once per second. The C/N flag shall be set to 0; • if an alert message has just ended, then End phase signalling shall be provided at a nominal repetition rate of once per transmission frame for 2 seconds. The C/N flag shall be set to 0; • if signalling is used for inter-ensemble communication and an alert message will begin in the ensemble, then Pre-trigger phase signalling shall be provided at a nominal repetition rate of the complete alert set once per second for three seconds and at an insertion rate of one FIG 0/15 instance per transmission frame. The Last flag of the last instance of FIG 0/15 of the alert set shall be set to 1; the Last flag of all other instances of FIG 0/15 of the alert set shall be set to 0. NOTE: If Sustain phase or End phase is provided when the alert group is not empty, it means that only OE Trigger phase alerts are signalled. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 6.7 Signal chain tests | If testing of the EWS is required in a similar way to a fire alarm drill, then the same kind of procedure for planning and informing the public is required so as not to cause unnecessary alarm. In this case an alert with the Stage field set to either Level 1 Start or Level 2 Start shall be used, with the alert message describing clearly that this is a test. To permit testing of the EWS without causing consumer receivers to respond, a test alert message can be provided. The Stage field shall be set to Test with all other fields set as required. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 19 Since the test message will be carried in a normal service component (even if carried in a temporary service), the test message will be selectable for listening on consumer receivers, but consumer receivers will not evaluate the test message as an alert. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7 Receiver behaviour and response | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.1 Receiver types | It is envisaged that the addition of EWS functionality in a receiver does not reduce the design options manufacturers may use. Therefore, many types of receivers are feasible. The minimum requirements for receivers are the subject of ETSI TS 104 090 [i.1]. Different types of receivers will have different operating models and capabilities. Whenever the EWS signals location codes to describe alert areas, receivers need to know their location in order to determine if the alert is relevant: the method by which the receiver acquires and maintains its location is not defined, but as a minimum it needs to know the DAB location code that corresponds to its current position on the earth's surface. For a domestic receiver this may be achieved via a set-up procedure in the user interface or via a wireless data transfer protocol; for a mobile receiver this is most likely to be achieved through a GNSS receiver. The conversion of a WGS84 coordinate pair to a DAB location code is described in annex F. Annex A describes the format for a manually entered receiver location code. Receivers with a single DAB tuner need to be aware of all receivable ensembles by performing regular scans. This is because in order to respond to an alert message they need to be tuned to an EWS ensemble: if the alert message is carried by another EWS ensemble then the receiver needs to know whether that ensemble is receivable before retuning - otherwise listening may be unnecessarily interrupted resulting in a poor user experience. Receivers with more than one DAB tuner can perform background scans to enable them to be aware of which ensembles are receivable. A minimum of two DAB tuners is essential for mobile receivers to be able to play one service whilst remaining aware of all receivable ensembles. Fixed and portable receivers shall implement a set of power modes that allow the receiver to respond to alert messages even when the device is not being used. The operation and timing of the transition of these power modes are specified by the present document. In-vehicle receivers are not expected to react to alert messages when the vehicle is unoccupied. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2 Fixed and portable receivers | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.1 Single DAB tuner receivers | Single tuner receivers can only respond to EWS alert messages when they are tuned to an EWS ensemble. This means that if the user selects a DAB service carried on an ensemble that does not participate in the EWS, no alert signalling will be received and so the receiver will be unaware of alerts. This also applies if the same tuner is used for reception of other broadcast services. Users shall be advised via the user interface of EWS capable receivers whenever the user makes a service selection that disables the EWS alert functionality. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.2 Power modes | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.2.1 Introduction | DAB receivers come in many forms - some are DAB only, whilst others include clock functions, FM reception, and other audio playback. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.2.2 Sleep mode | In this mode the receiver is not outputting audio. This is the lowest power mode. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 20 During sleep mode, the receiver shall ensure that a timer operates, synchronized to the time provided by FIG 0/10. The function of the timer is to initiate a transition to monitor mode such that the receiver is able to decode the FIC of the selected EWS ensemble at the beginning of each minute. The receiver shall begin the transition in sufficient time, according to its own architecture. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.2.3 Monitor mode | In this mode the receiver is not outputting audio. The DAB tuner is tuned to an EWS ensemble and is able to decode the FIC. If FIC reception errors are experienced, the receiver shall not return to sleep mode prematurely: Trigger phase signalling repeats continuously for 5 seconds and during this period the receiver shall endeavour to capture a complete alert group (unless a matching alert is found). If FIC reception errors continue, the receiver shall behave as if no FIG 0/15 has been received (see below). During monitor mode, which shall be fully operational when the seconds count changes from 59 to 0, the receiver shall check that it is still aligned to the minute's edge by reference to the CIF count contained in FIG 0/0, which is present in every transmission frame. If alignment has been lost, it shall be reestablished by resynchronising to the time provided by FIG 0/10. All FIG 0/15 instances containing Pre-trigger phase signalling shall be ignored. The receiver shall examine the content of the FIG 0/15 instances it receives that have the P/D flag in the FIG type 0 header set to 0 (Process). It shall ignore any FIG 0/15 instances it receives that have the P/D flag in the FIG type 0 header set to 1 (Discard). If a FIG 0/15 instance containing the Heartbeat is examined, it tells the receiver that there are no alerts to be evaluated: the receiver shall return to sleep mode. If a FIG 0/15 instance containing Sustain phase or End phase signalling is examined and the C/N flag is set to 1, it tells the receiver that there are no alerts to be evaluated: the receiver shall return to sleep mode. If a FIG 0/15 instance containing Sustain phase or End phase signalling is examined and the C/N flag is set to 0, it tells the receiver that there are OE alerts to be evaluated: the receiver shall wait for the next instance of FIG 0/15. If a FIG 0/15 instance containing Trigger phase signalling is examined, it shall be evaluated. If an alert match is found (see clause 7.5), the receiver shall transition to alert mode (see clause 7.6) and play out the alert message. If an alert match is not found, then if the last flag is set to 0, the receiver shall evaluate the next instance of FIG 0/15, else it shall return to sleep mode. If no FIG 0/15 is received within 10 seconds, then the ensemble has ceased to be an EWS ensemble and it shall be removed from the list of EWS ensembles. The receiver shall retune to the next best candidate EWS ensemble and determine if this new ensemble provides FIG 0/15: if so the receiver synchronizes its sleep timer using the time provided by FIG 0/10 and returns to sleep mode with the new EWS ensemble as its monitoring ensemble; if not, the process of finding a new EWS ensemble shall continue until either a new EWS ensemble has been found, or all candidates have been exhausted. If no EWS ensemble is found, the receiver shall rescan the whole DAB band: for the purpose of the rescan the setting of the P/D flag is ignored. If no EWS ensemble is found on rescan, the receiver shall repeat the scan process after one hour. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.2.4 Audio mode | In this mode the receiver is outputting audio. The receiver enters audio mode as a response to a user action. In audio mode, the receiver shall as far as possible use the DAB tuner to evaluate FIG 0/15 for matching alert messages. If access to the DAB tuner is not available, or if the user has selected a DAB service which is not carried in an EWS ensemble, then the receiver shall indicate to the user that the EWS function is inoperable. If a FIG 0/15 instance containing Trigger phase signalling is received, it shall be evaluated. If an alert match is found (see clause 7.5), the receiver shall transition to alert mode (see clause 7.6) and play out the alert message. If an alert match is not found, then the receiver continues with its current audio playback. If no FIG 0/15 is received within a period of 10 seconds, then the ensemble has ceased to be an EWS ensemble and it shall be removed from the list of EWS ensembles. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 21 If FIG 0/15 is received and the ensemble is not on the list of EWS ensembles, it shall be added to the list. When the receiver leaves audio mode as a response to a user action, and the tuned ensemble is an EWS ensemble, that ensemble should be selected as the EWS ensemble to monitor. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.2.3 Initialization procedure | When the receiver is switched on for the first time (or after a system reset), it shall determine its location, either by requesting the user to input the corresponding DAB location code (see annex A), or by another means. If the only means the receiver has for knowing its location is via a user entered location code, and the user does not enter such a code, the receiver shall only evaluate alerts that are signalled without location codes, i.e. whole ensemble alerts. It is recommended that the receiver reminds the user to enter the code whenever the receiver is put into use. The receiver shall scan all DAB frequencies and acquire the service list and using the status of FIG 0/15 signalling in each ensemble, mark all ensembles with FIG 0/15 signalling as EWS ensembles. Since the nominal repetition rate of FIG 0/15 signalling is once per second or faster, the determination can be made in a timely fashion. Metrics of signal quality should also be made in order to determine a suitable EWS ensemble to monitor whenever the receiver is in monitor mode: stronger signals should be preferred. The initial selection of the EWS ensemble to monitor shall be made according to quality metrics, but a user option to select which EWS ensemble is preferred may be offered by providing the ensemble label to the user of each EWS ensemble that meets the minimum reception quality. Such user preference may be due to administrative boundaries, language, or other factors. If no EWS ensembles are found, then the receiver is unable to respond to EWS alerts and the receiver shall indicate to the user that the EWS function is inoperable. Once the EWS ensemble has been selected, it shall be tuned to, and the sleep timer shall be synchronized to the time provided by FIG 0/10. The CIF count, provided in every transmission frame by FIG 0/0, shall be recorded for the first transmission frame that corresponds to the seconds count of zero: this allows for a simple alignment check at each monitoring period as 1 minute contains exactly 2 500 CIFs. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.3 Mobile receivers | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.3.1 Tuner capability | An EWS mobile receiver requires a minimum of two DAB tuners. This allows it to play out audio and at the same time monitor other DAB ensembles for alert signalling and to determine whether a matched alert message is receivable. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.3.2 Location awareness | A mobile receiver shall have a means to know its geographical location to a precision of at least 100 m. Typically, a GNSS receiver will be suitable. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.3.3 Audio mode | An in-vehicle receiver shall be active whenever the vehicle is occupied. A mobile receiver that is not an in-vehicle receiver may offer options for availability of the EWS function. The receiver shall monitor the FIC of an EWS ensemble on a regular cycle to evaluate FIG 0/15 for matching alert messages. If the EWS ensemble is no longer receivable, the receiver shall seek another EWS ensemble for monitoring. The monitoring period shall include the time at which the seconds count is 0 as this is when synchronized alert messages will begin and FIG 0/15 with Trigger phase information is most likely to be present. Receivers shall also monitor the FIC of an EWS ensemble at other times, since an alert message might not be synchronized and so begin at any time. If a FIG 0/15 instance containing Trigger signalling is received, it shall be evaluated. If an alert match is found (see clause 7.5), the receiver shall transition to alert mode (see clause 7.6) and play out the alert message. If an alert match is not found, then the receiver continues with its current function. ETSI ETSI TS 104 089 V1.1.1 (2024-09) 22 If no FIG 0/15 is received within 10 seconds, then the ensemble has ceased to be an EWS ensemble and it shall be removed from the list of EWS ensembles: another EWS ensemble shall be selected to monitor. If FIG 0/15 is received and the ensemble is not on the list of EWS ensembles, it shall be added to the list. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.4 User settings | |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.4.1 Alert message playback control | Receivers may offer user settings to allow users to control the playback of certain alert messages. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.4.2 Dismiss user controls | A "dismiss repeats" function may be offered which when engaged by the user will prevent the playing of alert messages for the same incident that have the stage Level 1 Repeat or Level 2 Repeat. A "dismiss incident" function may be offered which when engaged by the user will prevent the playing of further alert messages for the same incident that have the stage Level 1 Update, Level 1 Repeat, Level 2 Update, or Level 2 Repeat. By default, or if these user settings are not offered via the user interface, then the user settings are false and playback will be unaffected. The user settings are applicable to the incident identified by the combination of the Ensemble Id (EId) and the Incident Identifier (IId). For alert messages carried in the tuned ensemble, the EId is provided by FIG 0/0; for alert messages carried in other ensembles the EId is provided in the Id field of FIG 0/15. When an alert message with the stage Level 1 Start or Level 2 Start is received, the user settings corresponding to that EId + IId are reset to "false" because this indicates a new incident. Since IIds are periodically reused, consideration should be given to a time-out period for user controls for an incident: if the IId has not been received for a certain period of time (perhaps one week), then the user controls should be reset for that EId + IId combination. |
786b8d411b7b8adcb03f93d3f4b741b4 | 104 089 | 7.4.3 Monitor mode user controls | A user function may be offered to users to instruct a receiver with sleep mode to evaluate a Level 2 alert as if it was signalled as the corresponding Level 1 alert. This could be linked to the time of day, so that Level 2 alerts signalled during certain hours only are evaluated when the receiver is in monitoring mode. By default, or if this user setting is not offered via the user interface, then the user setting is false and playback will be unaffected (i.e. the receiver will react according to the signalled stage). A user function may be offered to users to prefer an EWS ensemble to use in monitor mode. The user is offered the list of EWS ensembles currently receivable by displaying their Ensemble Labels. The ordering of the list could be made by such metrics as signal quality and ECC + country code. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.