Difference between revisions of "Traffic information"
From OpenDigitalRadio
Jump to navigationJump to search| Line 1: | Line 1: | ||
=Traffic Information= | =Traffic Information= | ||
| + | ===General=== | ||
DAB has got functionalities for traffic information as it existed for FM. | DAB has got functionalities for traffic information as it existed for FM. | ||
| Line 12: | Line 13: | ||
FIG 0/19 should be triggered by an external signal (via ZMQ ? or telnet ?) or forced as always on in the config (useful for some case for emergency mux). | FIG 0/19 should be triggered by an external signal (via ZMQ ? or telnet ?) or forced as always on in the config (useful for some case for emergency mux). | ||
| − | |||
TO BE ADDED | TO BE ADDED | ||
guidelines for implementation, FIG rates | guidelines for implementation, FIG rates | ||
| + | |||
| + | |||
| + | |||
| + | ===Reference=== | ||
| + | |||
| + | Page 101 of [http://www.etsi.org/deliver/etsi_en/300400_300499/300401/01.04.01_40/en_300401v010401o.pdf EN 300 401] | ||
Latest revision as of 17:51, 2 August 2015
Traffic Information
General
DAB has got functionalities for traffic information as it existed for FM.
The equivalent of the Traffic Programm (TP) (flag for station having traffic information in the program) is implemented in FIG 0/18.
The equivalent for the Traffic Announcement (TA) (flag activated when the announcement happens, interrupt listeners) is implemented in FIG 0/19
As of today (31/7/2015) these functionalities are not implemented in ODR-DabMux.
FIG 0/18 is static and can be added as an option in the config file.
FIG 0/19 should be triggered by an external signal (via ZMQ ? or telnet ?) or forced as always on in the config (useful for some case for emergency mux).
TO BE ADDED
guidelines for implementation, FIG rates
Reference
Page 101 of EN 300 401
