Managing Networks

Managing Networks

INTRODUCTION 

Networks are a key feature of Icareus Playout platform. Each Network contains one or several  Actual  subnetworks and those in the system represents a individual transport stream with DVB Services, data services, configurations, tables, etc. It basically offers the possibility to get rid of the expensive remuxing of PSI/SI, EIT and data services by defining the (regional) networks/multiplexes/transponders at a single location. 
The management of the networks is done with intuitive  Networks  -tree, which gives easy access to all network parameters. 
Defining a Network is usually the first step to do when starting to work with Icareus Playout. 

ADDING A NETWORK 

A Network and it's Actual subnetworks are added using the Networks -tree by right clicking the root of the tree as shown in the image below. 

 

The  Actual  and  Other  network nodes are automatically created based on the configuration data. 

The  Actual and   Others  subnetworks can be added by right clicking the desired node in the  Networks  -tree. 

 

In the picture below two  Actual  subnetworks has been created with transport stream IDs 100 and 101.

 

3.  BASIC CONFIGURATION OF NETWORKS 

When adding the new network, three configuration parameters can be defined: 

  1. Netwirk name 
  2. Network id 
  3. Original network id 

These parameters can also be accessed later by right clicking the network name. 

 


This opens a Dialog with the above parameters that are explained below.

When adding the  Actual  subnetwork, several configuration parameters can be defined: 

  1. General (Name, Transport Stream ID, Network ID, ...) 
  2. Table Generation (PMT, PAT, EIT, ...) 
  3. Table output repetition rates (PAT, PMT, ...) 
  4. Output interfaces (IP, ASI) 

These parameters can also be accessed later by right clicking the  Actual  subnetwork name. 

 


This opens a Dialog with the above mentioned tabs. These tabs are explained below.


3.1. 
 NETWORK EDIT DIALOG

Network Name : The logical name for the network 
Network ID : Network id for the network 
Original Network ID : Original network id for the network

 


3.2. 
 ACTUAL SUBNETWORK EDIT DIEALOG, GENERAL -TAB


The general -tab defines basic network related parameters that are however critical to the operation of the receiver. 

Network Name : The logical name for the  Actual  subnetwork 

Transport Stream ID : Transport stream id for the  Actual  subnetwork 

Network bitrate : The maximum constant bitrate (CBR) for the selected  Actual  subnetwork, if null -packet insertion is activated the system will fill the output transport stream to meet this value. 

Otherwise the system will output a variable bitrate MPEG2 TS based on the PSI/SI and EIT tables and others. However the output may be higher than the defined bitrate if the combined PSI/SI and EIT table size is higher than the defined value. This approach ensures that the receivers will continue to receive valid signalling. There is no limitation set for the bitrates and thus the output purely depends on the capabilities of the hardware.



3.3. 
 TABLE GENERATION -TAB

Table Generation defines the PSI/SI and EIT tables that are generated for this network. 

From the tab, it is possible configure different PSI/SI tables generation. 
Generate PAT : Enables generating Program Association Table.

Generate PAT reference to NIT:  Add PAT reference to NIT 

Generate PMT:  Enables generation of Program Map Table. 

Generate NIT:  Enables generating Network Information Table. 

Generate NIT descriptors 
If this setting is enabled, the following descriptors will be generated automatically to Network Information Table:

  • Network name descriptor 
  • Delivery descriptor (requires that delivery settings have been set) 
  • Linkage descriptor with linkage type 0x0B for each IP platform 

Generate SDT : Enables generating Service Description Table. 

Generate SDT descriptors 
If this setting is enabled, the following descriptors will be generated automatically to Service Description Table:

  • Service descriptor for each DVB service 
  • Data broadcast descriptor for each MPE stream 

Generate BAT : Enables generating Bouquet Association Table. 

Generate TDT : Enables generating Time and Date Table. 

Generate TOT : Enables generating Time Offset Table. 

Generate EIT P/F : Enables generating the Event information table present/following 

Generate EIT Schedule : Enables generating the Event information table Schedule. Turning this off disables generating the schedule entirely, irrespective of the 2 following options. 

Generate EIT Schedule 0-3 : Enables partitioning of the Event information table Schedule for days 0-3. The partitioning is defined in the EIT Rates tab. The days 0-3 occupy the first EIT schedule subtable, with table id 0x50 for the actual schedule and 0x60 for the other schedule. 

Generate EIT Schedule 4-7 : Enables a partition of the Event information table Schedule for days 4-7, and another for the remaining days 8+. If the 0-3 option is selected, but the 4-7 option is not selected, then only days 0-3 will be generated into the schedule. The days 4-7 occupy the second EIT schedule subtable, with table id 0x51 for the actual schedule and 0x61 for the other schedule. 




3.4. 
 RATES -TAB

PAT repetition rate : Repetition rate for Program Association Table 
measured in milliseconds.

PMT repetition rate : Repetition rate for Program Map Table 
measured in milliseconds.

NIT repetition rate : Repetition rate for Network Information Table 
measured in milliseconds.

SDT repetition rate : Repetition rate for Service Description Table 
measured in milliseconds.

BAT repetition rate : Repetition rate for Bouquet Association Table 
measured in milliseconds.

TDT repetition rate : Repetition rate for Time and Date Table 
measured in milliseconds.

TOT repetition rate : Repetition rate for Time Offset Table 
measured in milliseconds.

AIT repetition rate : Repetition rate for Application Information Table 
measured in milliseconds.


 


3.5.  EIT RATES -TAB 

EIT P/F repetition rate :Repetition rate for Event Information Table Present/Following 
measured in milliseconds.

EIT Schedule repetition rate : Repetition rate for Event Information Table Schedule 
measured in milliseconds. Please note the  EIT Schedule bit rate per service  -value as repetition rate affects the total amount of EPG data that can be outputted. Also note that when the EIT schedule is partitioned and Generate EIT Schedule 0-3 is and Generate EIT Schedule 4-7 is enabled, this repetition rate is used for the events for days 8+ of the schedule.

EIT Schedule bit rate per service : Maximum output bit rate of service for Event Information Table Schedule 
measured in bits per second. If the EIT output exceeds this value, EPG events from the EIT Schedule table are dropped from the end to fit this bandwidth and repetition rate configuration. If value is set to 0, the output is unlimited.

EIT sch (0-3) Group Past repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for past Event Information Table Schedule events 
measured in milliseconds. In the current implementation, this option does nothing.

EIT sch (0-3) Group 1 repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for the first partition of the Event Information Table Schedule, 
measured in milliseconds. The schedule segments that are part of this group must be selected in right column. 8 segments equal one day, so e.g. to specify that the first partition should hold one days worth of EIT events, segments 0-7 must be selected. One segment equals 3 hours of events. To put the 2 first days of events in the first partition, specify segments 0-15. To put the 3 first days of events in the first partition, select 0-23. To put all the 4 first days (0-3) into this partition, select a range of 0-31. When group 1 segments have been configured by selecting from the menu, the focus will move to group 2 and so on. To get back to allocate group 1 again, one has to cycle through all the groups 1-5 after which group 1 segments can again be changed.

EIT sch (0-3) Group 2 repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for the second partition of the Event Information Table Schedule, 
measured in milliseconds. Like in group 1, a range of segments will specify which events will be part of the group. Only remaining segments, after the allocation of group 1 can be selected here as part of the second partition.

EIT sch (0-3) Group 3 repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for the 3rd partition of the Event Information Table Schedule, 
measured in milliseconds.

EIT sch (0-3) Group 4 repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for the 4th partition of the Event Information Table Schedule, 
measured in milliseconds.

EIT sch (0-3) Group 5 repetition rate : When Generate EIT Schedule 0-3 is enabled, this is the repetition rate for the 5th partition of the Event Information Table Schedule, 
measured in milliseconds. If there's any unallocated segments left for days 0-3 after groups 1-4 have been specified, those segments must be put in this group.

EIT sch (4-7) repetition rate : When Generate EIT Schedule 4-7 is enabled, this is the repetition rate for the partition holding days 4-7 of the Event Information Table Schedule, 
measured in milliseconds. 


 



3.6. 
 UDP OUTPUT 1 & 2 -TABS

UDP output -tab defines the transport stream output for the selected Network. Each Network's transport stream can be outputted as IP multicast/unicast from two separate network cards to get as redundant output from a single server as possible. 

For redundancy purposes it is recommended that the multicast addresses of the outputs are different as well as the Output devices. The outputs should be then connected to either an IP switch that can monitor the output or to a multiplexer that can do the same. An example is given below. 



Enable UDP output: 
USE RTP:  Use RTP protocol to envelope the UDP stream

IP Address:  Multicast address for the MPEG2 TS 

Port:  IP port in which the multicast should be transmitted 

TTL:  Time to Live for the IP packets 

Output device:  Defines the physical network interface card that is used to output the MPEG2 TS for this Network 


ASI/Modulator output Tab

ASI/Modulator tab defines a physical output via a supported ASI output card. The card has to be installed on the physical server. This functionality is not supported on virtual machines.
Enable ASI output: If selected the system generates the TS output to ASI output. Requires a compatible ASI card to be selected on the "output card model" -selection.
Enable Modulator output: If selected the system generates the TS output to Modulator output. Requires a compatible Modulator card to be selected on the "output card model" -selection.
Output card model: Lists the compatible output card models found in the system
Output card number (0-...): Defines the bus number of the output card
Output port number (1-...): Defines the port on the selected output card that is used for the generated output. Some cards may have upto 4 output ports and system needs to know which one to use.




4.  ADDING DVB SERVICES TO NETWORKS 

Once the Network is created it is time to add Services to that Network. Refer to chapter " Managing DVB Services " to learn how to add Services to Icareus Playout platform. 

A Service is added to a  Network  from the  DVB Services  -tree either by drag-and-dropping it to selected Network or by right clicking as illustrated in the image below. 



Once the Service has been added to a Network, its ID can be changed by right clicking it as illustrated in the below images. 




    • Related Articles

    • Managing Networks

      Introduction The multinetwork feature in Icareus Playout opens the possibility to output several Networks (or Transport Streams over IP) from a single Playout server. Each Network may have it's own set of configuration parameters as well as ...
    • Managing Applications

      Introduction Icareus Playout Carousel Server is a playout system for delivery of DSM-CC object carousels, DSM-CC data carousels and related tables (e.g. AIT) over DVB services. Object carousels can be used for delivering MHP, Hbbtv, tru2way or mheg-5 ...
    • Managing PSI-SI Generation

      INTRODUCTION Icareus Playout server’s PSI/SI generation generates all related tables: Program Association Table (PAT) Program Map Table (PMT) Bouquet Association Table (BAT) Event Information Table (EIT) IP/MAC Notification Table (INT) Network ...
    • Managing DVB Services

      Introduction DVB Services in Icareus Playout represent TV or radio channels that are broadcasted. Note, that service properties depend on the included features of the Playout server. The DVB Services tree includes services that have been configured ...
    • Managing DVB Services

      1. INTRODUCTION DVB Services in Icareus Playout represent TV or radio channels that are broadcasted. Note, that service properties depend on the included features of the Playout server. The DVB Services -tree includes Services that have been ...