Specification of DAB Multiplexer system

Transcription

1 Specification of DAB Multiplexer system

2 Ensemble Provider Multiplexer System This section describes requirements for the ensemble multiplexer, including configuration and control/monitoring of the system units. General The ensemble multiplexer system shall support local input of audio programme and data services in the form of stream mode audio components, packet mode data components and stream mode data components. The ensemble multiplexer system shall support upstream entities, e.g. service provider multiplexer systems. The ensemble multiplexer system shall be based on industrial PC units in a 19 rack casing. It shall be 4 HU high and use a Intel Pentium III processor running at 1 GHz or higher. PC:s are equipped with a display of type VFD (Vacuum Fluorescent Display) on the front. The display indicates the status of the unit in the following way: If an error condition occurs, an error message will be displayed on the display. If several errors are active at the same time, the error messages will be scrolled one at a time. If a power supply fails, an error message will be displayed on the display. The PC is equipped with dual hot swappable power supplies. If one of the power units fails, a summer start beeping and the LED s in the front panel will indicate an alarm. To prevent data loss after a major disc failure this system is endowed with a RAID (Redundant Array of Inexpensive Discs) system. The RAID in this system has two mirrored redundant hard discs (RAID1). The system is equipped with a hot swappable disc system for easy replace of the discs. Each drive is mounted in a drive bay. The DAB Ensemble Multiplexer Provider System is formed by a combination of the DAB Ensemble Provider Controller and the DAB Ensemble Multiplexer. Configurations & Scheduling Configurations shall be created using a graphical user interface. The ensemble multiplexer system shall support scheduling of up to 100 configurations. The system shall be equipped with a tool to support weekly scheduling of configurations. The schedule tool shall provide the possibility to repeat a weekly configuration pattern forever until it is changed or replaced. It shall be possible to store defined configurations in a persistent way (i.e. not be depending on power supply). Dynamic service information and booking lists shall be persistently stored, automatically. FIG data (both SI and MCI) shall be generated automatically from defined configurations, also for upstream entities. FIG data (SI) shall be generated automatically from defined configurations. To ensure a smooth and uninterrupted service in the receiver end, the multiplexer shall use an intelligent sub-channel organisation algorithm that minimises the reallocation of sub-channel start addresses at a reconfiguration.

3 Audio settings reconfigurations shall be performed seamlessly. The ensemble multiplexer system shall support scheduling of up to 4000 reconfigurations. Service Information (SI) Service Information (SI) data shall be generated automatically from defined configurations and from user editable databases. Changes in time zone, daylight saving shall be detected and applied automatically. Announcements, national and regional shall be supported. The multiplexer system shall support the definition of announcement clusters. Announcements shall be performed using two methods: By using an existing audio sub-channel connected to an audio service, and insert the announcement information there. By using a dedicated audio sub-channel that not is used in any regular audio service. This method will not interrupt and disturb existing audio services, if for instance the user has disabled the announcement function in the receiver. Dynamic and static programme types (PTy) shall be supported. Dynamic and static Service Component Language shall be supported. Dynamic User Application Type shall be supported. The multiplexer system shall support service linking and frequency information of the following types: National and regional, explicit and implicit hard links to FM-RDS National and regional, explicit and implicit hard links to other ensembles National and regional, explicit and implicit hard links to FM. National and regional, explicit and implicit hard links to AM. Redundancy 1+1 ensemble multiplexer redundancy shall be supported. The ensemble multiplexer shall be equipped with dual redundant power supplies. It shall be possible to replace a failing redundant power supply unit during operation, without disturbing the to-air services. The PC platform shall be equipped with dual redundant hard disk drives. A failing hard disk shall be possible to replace during operation, without disturbing the to-air services. 1+1 redundancy for audio encoders shall be supported. If an audio encoder fails, the multiplexer system shall automatically and seamlessly switch to the backup encoder. Control & Monitoring Control and monitoring of the system shall be possible to perform remotely. A remote control tool or client running on a PC platform shall be provided (specified separately). Remote monitoring shall also be possible via SNMP (v2c). Remote monitoring shall also be possible via relay outputs The ensemble multiplexer system shall automatically control and monitor audio encoders.

4 The ensemble multiplexer system shall automatically control and monitor data servers. All events in the system shall be logged in an event database. The database shall be persistent, i.e. remain over power failures. When retrieving data from the event database, the user shall be able to select which type of events that are to be displayed. The following selections shall be possible: Date (either a specific date or a range of days) Event type (error, warning, message, etc) Source of the event (audio encoder, data server, etc) The multiplexer shall support generation of a PRBS sub-channel for testing purposes. Interfaces Hardware dongles must not be used for software licensing control in any part of the system. The output from the system shall be compliant with the Eureka 147 definition of ETI (Ensemble Transport Interface). The ETI output interface shall support the generation and insertion of Timestamp. The ETI output interface shall support static offsets of the Timestamp value to minimise transmission delays. In case of a failing PPS signal, the ETI output interface shall continue to generate time stamp with the same phase. A failing PPS signal shall be reported to logs and monitoring systems. The ETI interface shall support the use of a Multiplex Network Signalling Channel (MNSC). It shall be possible to input MPEG audio via X.21 or WG1/WG2. The MPEG input interface used must be non-proprietary and the implementation must follow an established international standard. It shall be possible to input packet mode data via G703, G704(E1) or V11. Reed-Solomon forward error correction shall be supported for G704 connections. Output interfaces shall generate and insert Reed-Solomon codes. Input interfaces shall check for errors and if possible- correct detected error using the inserted Reed-Solomon code. The logical format supported by packet mode data inputs shall be STI-D according to standard ETS STI-C communication with an upstream entity shall be performed via TCP/IP. Relays signalling system alarms shall be available. Different relays shall be used for different severity levels. Remote Control Tool Control and monitoring of the system shall be possible to perform remotely. A remote control tool or client running on a PC platform shall be provided. The remote tool shall communicate with the multiplexer system via TCP/IP. The remote tool shall be allowed to be freely copied. It shall be possible to install and use the remote tool in multiple locations free of license charges.

5 The remote tool shall support authentication of users. The remote tool shall allow different levels of access to the system. It shall be possible to pre-assign different levels of access to different users that can access the tool. It shall be possible to view current users and their access levels that are using the tool to access the multiplexer system. It shall be possible to via the tool search in and display contents of the multiplexer system event database. It shall be possible to via the tool edit and dynamically change service and service component labels. Web Server The multiplexer system shall be equipped with a built-in web server. It shall be a standard TCP/IP interface that can be accessed by e.g. a standard browser tool intended for the Internet. Minimum supported features shall be: View all local services and service components currently on air. Edit and dynamically change service and service component labels. Dynamic change of Program Type, Service Component Language and User Application Type. Application Programming Interfaces (API) The multiplexer system shall provide Application Programming Interfaces, which makes it possible for the user to integrate the DAB system with already existing systems and applications. API:s compatible with Microsoft.NET platform are preferred, especially API:s that are web service compliant. The multiplexer system API shall support external triggering of configuration changes (changes between already defined configurations).

6 Service Provider Multiplexer System This section describes requirements for the service multiplexer, including configuration and control/monitoring of the system units. General Service provider multiplexer systems shall be supported. The service multiplexer system shall support local input of audio programme and data services in the form of stream mode audio components, packet mode data components and stream mode data components. The service multiplexer system shall be based on industrial PC units in a 19 rack casing. It shall be 4 HU high and use a Intel Pentium III processor running at 1 GHz or higher. PC:s are equipped with a display of type VFD (Vacuum Fluorescent Display) on the front. The display indicates the status of the unit in the following way: If an error condition occurs, an error message will be displayed on the display. If several errors are active at the same time, the error messages will be scrolled one at a time. If a power supply fails, an error message will be displayed on the display. The PC is equipped with dual hot swappable power supplies. If one of the power units fails, a summer start beeping and the LED s in the front panel will indicate an alarm. To prevent data loss after a major disc failure this system is endowed with a RAID (Redundant Array of Inexpensive Discs) system. The RAID in this system has two mirrored redundant hard discs (RAID1). The system is equipped with a hot swappable disc system for easy replace of the discs. Each drive is mounted in a drive bay. The DAB Service Provider Multiplexer System is formed by a combination of the DAB Service Provider Controller and the DAB Service Multiplexer. In the following areas, the same requirements are valid for the Service Provider Multiplexer System as for the Ensemble Provider Multiplexer System (see above): Redundancy Control and Monitoring Remote Control Tool Web server Application Programming Interfaces (API) In particular, the following requirements shall be met: Dynamic and seamless reconfigurations of the service provider multiplexer shall be supported. Announcement switching shall be supported. STI-C communication between the service provider multiplexer and the ensemble multiplexer shall take place via TCP/IP).

7 Configuration parameters for the service provider multiplexer shall be restricted by a contract with the ensemble multiplexer system. The contract shall define the resources (bit capacity, service IDs etc) that the service provider is allowed to use. No configuration changes must be performed by the service multiplexer system, unless the granted permission from the ensemble multiplexer system. The request and grant of a configuration change shall be performed automatically via STI-C. Information about new configuration parameters shall be downloaded to the ensemble multiplexer system via STI-C. Interfaces Hardware dongles must not be used for software licensing control in any part of the system. The output from the system shall be compliant with the Eureka 147 definition of STI (Service Transport Interface: EN ). It shall be possible to input MPEG audio via X.21 or WG1/WG2. The MPEG input interface used must be non-proprietary and the implementation must follow an established international standard. It shall be possible to input packet mode data via G703, G704(E1) or V11. Reed-Solomon forward error correction shall be supported for G704 connections. Output interfaces shall generate and insert Reed-Solomon codes. Input interfaces shall check for errors and if possible- correct detected error using the inserted Reed-Solomon code. The logical format supported by packet mode data inputs shall be STI-D according to standard ETS STI-C communication with an downstream entity shall be performed via TCP/IP. Relays signalling system alarms shall be available. Different relays shall be used for different severity levels.

8 Audio encoder Audio encoders shall meet the following requirements: Encoding according to the MPEG-1 standard (ISO/IEC ) and MPEG-2 standard (ISO/IEC ). Only layer II is required. Encoding in 48 khz and 24 khz (LSF) shall be supported. Encoding in MPEG modes Stereo, Joint Stereo, Dual Channel and Single Channel shall be supported. The encoder shall be equipped with both analogue and digital audio inputs The encoder shall be able to perform on-the-fly seamless reconfigurations. It shall be possible to control the encoder remotely via a CAN bus. It shall be possible to control the encoder remotely via a RS232. To enable the equipment operator to distinguish which encoder that handles which audio service, the encoder shall be able to display, on its front, the current Service Component Label of the service it is encoding. The shown label shall be the same as the label currently defined in the presently valid ensemble configuration, and automatically reflect changes in the configuration. Specification of the analogue input: Input type: Balanced Input connector type: XLR female Input impedance: Selectable between 600 Ω and high impedance (>10 kω) The input impedance selection shall be possible to make from the front panel user interface. Specification of the digital input: Input type: AES/EBU and S/PDIF Input connector type: XLR female Input impedance: 120 Ω ±5% The encoder shall be equipped with a built-in sample rate converter (SRC). The analogue input shall have a built-in analogue to digital converter with the following features: Resolution: At least 20 bits ADC Level: Default value 18 dbfs for 0 dbu input level. The ADC level shall be adjustable from the front panel user interface. The adjustable range shall be at least ±10 db around the default level value, in steps of 0.1 db. The audio encoder shall be equipped with a PAD data port that supports the PAD protocol as recommended by IRT (DAB de-facto standard). It shall be possible to select the baudrate for the PAD data port. Possible values shall be at least and baud. The audio encoder shall be equipped with:

9 A 2,5 mm monitor jack for stereo headphones on the front panel. Dual X.21 MPEG output interfaces. WG1/WG2 MPEG output interface. Bar-graphs The logical output format of the MPEG encoder shall be selectable between STI-D formatting and normal raw MPEG. The physical output interface used for MPEG must be non-proprietary and the implementation must follow an established international standard. Software may easily be upgraded for future enhancements in algorithms as well as standards. Software upgrade shall be possible without removing the unit from the installation in the rack. The MPEG encoding algorithm shall be selectable between either Philips or Coding Technologies brands. It shall be possible to, as an option, equip the encoder with a cooling fan. Data server The multiplexer system shall support data input and encoding to support IP broadcasting and MOT data broadcasting according to the Eureka147 standard ETS Data input devices shall support NPAD data format. Data input devices shall perform MOT encoding when so is required, compliant with EN v1.2.1 (or later). Data input devices shall support a minimum of 16 PAD channels (simultaneous with NPAD services). Data input devices shall support IP tunnelling over DAB according to standard ETSI (packet mode). Dynamic range control (DRC) The multiplexer system shall support generation of DRC information according to the standard ETS The DRC generation algorithm shall be developed by the Swedish Broadcasting Corporation. The multiplexer system shall support audio level optimisation (compression & expansion). The compression algorithm shall be developed by the Swedish Broadcasting Corporation. Software may easily be upgraded for future enhancements in algorithms as well as standards. Software upgrade shall be possible without removing the unit from the installation in the rack. The DRC unit generator shall be equipped with a temperature measuring feature. High temperature shall trigger a relay alarm.