Transforming Video Delivery: User Manual

Transforming Video Delivery
User Manual
Version 1.4
Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

78140 Vélizy-Villacoublay RCS Versailles B 382 231 991
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Copyright © 2017 ATEME.
These materials, ATEME products and all related documentation are protected by copyright and other
laws, international treaties and conventions. All rights, title and interest in the materials, ATEME products
and related documentation shall remain with ATEME and its licensors. All registered or unregistered
trademarks in these materials are the sole property of their respective owners. No part of this document
or related ATEME products may be reproduced in any form, or by any means without written authorization
of ATEME Corporation.
THESE MATERIALS ARE PROVIDED "AS-IS." ATEME MAKES NO WARRANTIES, STATED OR IMPLIED, AS TO,
THE INFORMATION CONTAINED HEREIN. IN ADDITION, ATEME MAKES NO STATED OR IMPLIED
WARRANTIES OF MERCHANTABILITY OR WORKING CONDITION FOR A PARTICULAR PURPOSE OR USE WITH
RESPECT THE INFORMATION CONTAINED IN THESE MATERIALS.
IN NO EVENT SHALL ATEME BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR INCIDENTAL
DAMAGES, INCLUDING, BUT NOT LIMITED TO, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING
FROM THE USE OF THESE MATERIALS, EVEN IF ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH
DAMAGES.
Copyright (c) ATEME
Trademarks
ATEME, the ATEME logo, TITAN® and the TITAN logo are all trademarks or registered trademarks of ATEME
Corporation. The TITAN clustering technology -as well as other technologies included in TITAN - are
protected by patents or pending patent applications in the U.S. and other countries. All other trademarks
or registered trademarks are property of their respective owners.
Changes
The material in this document is for information only and subject to change without notice. While
reasonable efforts have been made in the preparation of this document to assure its accuracy, ATEME
assumes no liability resulting from errors or omissions in this document, or from the use of the information
contained herein. ATEME reserves the right to make changes or revisions in the product design or the
product manual without reservation and without obligation to notify any person of such revisions and
changes.
Important Notice
The TITAN Mux is not designed or intended to violate any other entity’s copyright or other IP (Intellectual
Property) rights. Each ATEME TITAN user may only use their ATEME TITAN in conjunction with materials
legally owned or licensed by such user, and only to the extent that such ownership or license rights permit
such use.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Table of contents
I. Introduction ..................................................................................................................................... 6
II. Installation ....................................................................................................................................... 7
A. ISO installation on a Bare Metal server ......................................................................................... 7
1. Setting IP network in console mode.......................................................................................... 9
2. Setting IP network in USB mode ............................................................................................. 11
B. VM installation on a vSphere ESXi server .................................................................................... 12
C. Run Titan Mux as a Docker Container ......................................................................................... 16
D. TITAN Mux shell upgrade............................................................................................................ 17
III. TITAN Mux design ...................................................................................................................... 18
IV. Input .......................................................................................................................................... 19
A. Dashboard.................................................................................................................................. 19
B. Monitoring ................................................................................................................................. 19
C. Declaring an IP MPTS input......................................................................................................... 22
1. IP Input................................................................................................................................... 22
2. Redundancy ........................................................................................................................... 24
3. ASI Input................................................................................................................................. 25
D. Virtual Services........................................................................................................................... 26
1. Use case 1: input stream has no PAT ...................................................................................... 27
2. User case 2: input stream has no PMT .................................................................................... 28
E. Declaring an external PSI input ................................................................................................... 30
V. Output ........................................................................................................................................... 31
A. Dashboard.................................................................................................................................. 31
1. Monitoring ............................................................................................................................. 31
B. Declaring a MPTS output ............................................................................................................ 33
C. Clock Selection ........................................................................................................................... 36
D. Program edition ......................................................................................................................... 37
1. Offline editing......................................................................................................................... 38
2. Adding streams ...................................................................................................................... 38
3. Enabling/Disabling service ...................................................................................................... 38

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
E. Statmux...................................................................................................................................... 39
1. Overview ................................................................................................................................ 39
2. Group types............................................................................................................................ 40
3. Creating statmux groups......................................................................................................... 40
1. Adding programs to a statmux group ...................................................................................... 41
2. Editing statmux parameters.................................................................................................... 41
F. Component rules........................................................................................................................ 42
1. User-Defined rules.................................................................................................................. 42
2. Component identification ....................................................................................................... 42
3. Component Rules ................................................................................................................... 42
4. Component tracking/mapping example .................................................................................. 43
5. Automatic component rules ................................................................................................... 43
G. Program Edition ......................................................................................................................... 44
1. Program Information .............................................................................................................. 44
2. Rate Control ........................................................................................................................... 45
H. PMT Edition................................................................................................................................ 45
1. Changing the PMT PID ............................................................................................................ 47
2. Blocking Descriptors ............................................................................................................... 47
3. Adding Descriptors ................................................................................................................. 47
I. Deleting a program..................................................................................................................... 48
J. SI Edition .................................................................................................................................... 48
1. Output conformance .............................................................................................................. 48
2. MPEG ..................................................................................................................................... 48
3. DVB ........................................................................................................................................ 50
4. ATSC ....................................................................................................................................... 57
VI. Simulcrypt Scrambling ................................................................................................................ 58
A. Dashboard.................................................................................................................................. 59
B. SCS Configuration ....................................................................................................................... 60
C. Declaring an ECM Generator ...................................................................................................... 63
D. Declaring an ECM stream ........................................................................................................... 65
E. Declaring an EMM/PD Generator ............................................................................................... 67
F. Declaring an EMM/PD Stream .................................................................................................... 69
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
G. Creating Scrambling Groups (SCG) .............................................................................................. 71
H. Inserting EMM Streams .............................................................................................................. 72
VII. BISS-1 Scrambling ....................................................................................................................... 73
VIII. System ....................................................................................................................................... 74
A. ASI Management ........................................................................................................................ 74
B. Network Management ............................................................................................................... 75
1. Physical interface ................................................................................................................... 76
2. VLAN management ................................................................................................................. 76
3. Gateway configuration ........................................................................................................... 77
C. Alarm Management ................................................................................................................... 77
1. SNMP Configuration ............................................................................................................... 77
2. Alarms configuration .............................................................................................................. 78
D. System Information .................................................................................................................... 81
1. System Information ................................................................................................................ 82
2. Diagnostic package ................................................................................................................. 82
E. System Management.................................................................................................................. 82
1. Set Titan Mux name................................................................................................................ 83
2. Export and Import a configuration .......................................................................................... 83
3. System Time setting ............................................................................................................... 84
IX. Logging Configuration............................................................................................................. 85

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
I. Introduction
TITAN Mux is a scalable stream processing solution for broadcast, cable, satellite, over the top and network
applications. TITAN Mux can be easily incorporated into any existing headend for supporting digital
turnaround services. The TITAN Mux scalable design reduces deployment time, enables adding new
services on the fly and support any video, audio and data service.
TITAN Mux can be controlled by ATEME Management System, and easily integrate with any NMS using a
REST API. TITAN Mux is a true software and OS agnostic solution running on any server, any form factor,
bare-metal OS and Virtual Machines.
TITAN Mux includes support for IP input-output and support for legacy ASI headend using PCIe ASI cards;
it eliminates operational headaches and ensures high scalability, flexibility and availability.
Figure 1: TITAN Mux ecosystem

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
II. Installation
TITAN Mux can be installed as a bare-metal server from an ISO binary, or as a Virtual Machine on a VMware
vSphere ESXi server from and OVA file.
A. ISO installation on a Bare Metal server

To install TITAN Mux on a bare-metal server from the ISO binary file:
Download and install Win32DiskImager on a Windows PC. The tool is available at

http://sourceforge.net/projects/win32diskimager. Once installed, launch the application
Win32DiskImager, choose the ISO file, select the destination USB key and click on Write to validate
Figure 2: ISO to USB
On success, a Write Successful pop-up will appear. Click on OK, then Exit. The USB key is ready. If needed,
configure the server Bios to boot on USB. Then insert the USB key into one of the server USB socket. Follow
the steps through the interactive menu items to select installation hard drive and configure management
interface:
Figure 3: ISO installation – start menu

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 4: ISO installation – confirm install
Figure 5: ISO installation – select hard drive
Figure 6: ISO installation – network configuration
Figure 7: Figure 8: ISO installation – setting IP address

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 9 Figure 10: ISO installation – setting Netmask
Figure 11: ipconfig – setting eth0 gateway
/!\ Important: since version 1.4.4.0 at the end of the installation process the server will reboot
automatically. An additional automated reboot will be done after the very first boot in order to ensure a
proper NIC port numbering.
1. Setting IP network in console mode

Once TITAN Mux is installed, it is possible to log on through a console with the credentials support/support
to set up an initial network configuration. By default the first network interface eth0 is assigned the static
IP address 192.168.0.1. Typing command ipconfig will open an interactive network configuration utility
that enables changing all network interfaces IP parameters.
Choose the interface to configure:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 12: ipconfig – interface selection
Choose static of DHCP mode:
Figure 13: ipconfig – interface mode
Figure 14: ipconfig – IP address
Set the interface netmask:
Figure 15: ipconfig – Netmask

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Typing command routeconfig will open an interactive gateway configuration utility. First choice is to
enable gateway:
Figure 16: routeconfig – gateway enabling
Enter gateway address:
Figure 17: routeconfig – gateway address
2. Setting IP network in USB mode

It is possible to configure the management interface and its gateway from a specially formatted USB key.
 Format a USB flash disk in FAT32,

 Create the file atememux-network-interface which contains the network configuration. An
example configuration is shown in the figure below:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 18: USB network - file creation
address and netmask are mandatory, the gateway field is optional.
Plug this USB key into TITAN Mux whose interface you want to reconfigure. Once inserted the new
configuration is applied. Wait 5 seconds before unplugging the USB key from the server. To verify if the
operation has been successful, plug the USB key on a Desktop machine and read the name of the file
present.
- Success: the file has been renamed atememux-network-interface.success, the network interface
eth0 has been reconfigured according to the file network settings. TITAN Mux Web GUI is now
reachable from a Web browser on the specified IP address.
- Failure: the file has been renamed atememux-network-interface.failure , additional log
information can be read in the file atememux-network-interface.log
B. VM installation on a vSphere ESXi server

The following steps describe the installation procedure of the TITAN Mux on a VMware vSphere ESXi server
with a vSphere client.
On vSphere client, go to File -> Deploy OVF template…, select the TITAN Mux OVA file and click on the Next
button twice.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 19: VM installation - Source
Rename the Titan Mux VM according to your needs.
Figure 20: VM installation – Name
Map TITAN Mux virtual network interface (Destination) to your server physical interface (Source).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 21: VM installation – Network Mapping
Once completed, TITAN Mux VM is ready to deploy.
Figure 22: VM installation – Ready to deploy
To configure the network and gateway settings, open the TITAN Mux VM console on the vSphere client,
log on with the credentials support / support and follow the steps described in section A.1

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 23: VM installation - Console

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
C. Run Titan Mux as a Docker Container
Titan Mux application is available as a Docker image, under the form of a “tar” file.
Ex: “titanmux-1_4_2_4-x64-debian8.tar”, or « titanmux.rar ».
To run Titan Mux container, the steps below shall be followed:
- Copy the TitanMux Docker image (“tar” file) onto the host running docker engine
- Connect to the host with root privileges
- Load the Docker image with command
“docker load < titanmux.rar”
- Run the Docker image with command:
“docker run --privileged -d -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -v /dev:/dev --net=host titanmux”
- Check the docker container is running with command
“docker ps”
Then, the Mux GUI is accessible though port 80.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
D. TITAN Mux shell upgrade
Step 0: Back up TITAN Mux configuration
 Before going any further you may want to back up TITAN Mux configuration
 You can do it with the Export feature on the Service Management page
Step 1: Add R/W rights to TITAN Mux destination folder if needed
Before you can transfer the new Debian packages to the Titan Mux, you may be need to increase titan
user rights in order to be able to write in the destination folder:
 Log on as titan/titan
 Enter the command su to become root, enter tebu3Ure as password
 Enter chmod a+w /home/titan
Step 2: transfer the Debian packages
From an external machine connected to the same network as TITAN Mux, use secure copy to transfer the
Debian packages to TITAN Mux /home/titan folder:
scp *.deb titan@titan_mux_ip_address:/home/titan
If the previous command fails, you may need to increase user rights on folder /home/titan beforehand.
Go to step 1 to do so.
Step3: update TITAN Mux
Once the Debian packages are copied, update TITAN Mux:
 Log on as titan/titan
 Enter the command su to become root, enter tebu3Ure as password
 dpkg --purge digital_muxer
 dpkg --purge system_management
 dpkg -i system_management-x.x.x.x-mux-1.deb
 dpkg -i digital_muxer-x.x.x.x-1.deb
TITAN Mux is now updated!

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
III. TITAN Mux design
The TITAN Mux is a full software Multiplexer; it is meant to ingest and egress transport streams.
From a configuration point of view, the Multi Program Transport Stream (MPTS) in output of TITAN Mux
are formed as collections of input services. Thus, the first thing to do when defining an output Transport
Stream is to define the inputs that will carry the services forming the output. Once these inputs are
defined, the resulting MPTS can of course be edited so as to adapt to any specific requirements, in terms
of tables, descriptors, bitrates, etc.
The following sections are organized following that scheme:
- Input stream declaration is detailed in section IV

- Output stream declaration is detailed in section 0
- Scrambling is detailed in section VI

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
IV. Input
Any number of input streams can be declared. Note that these inputs may or may not be associated to a
MPTS output. In the TITAN Mux, an input stream can be:
- A MPTS or SPTS, that will carry services to be re-muxed

- A PSI table coming from a PSI Generator
This type of input stream is handled like a standard input
A. Dashboard
The TITAN Mux offers a high level input view, which is meant to have an overview of all the declared input
streams. The streams are identified by their GUI identifier (refer to section IV.C), and will show the
detected services that were found inside the MPTS.
Input
Overview
Input Edition /
Monitoring
Figure 24: Input overview
B. Monitoring
The TITAN Mux can monitor the incoming MPTS, by clicking on the “Monitoring” button, in the right panel
of the input dashboard. As shown in Figure 25, this monitoring allows for:
- IP Level monitoring
o Detected protocol and / or FEC
o Detected network bitrate (including UDP network headers)
- TS level monitoring
o Detected PCR Bitrate
o Total TS bitrate, which is detected packet bitrate (can be identical to network bitrate in
case there are no additional UDP headers)
o Effective TS bitrate (same as total TS bitrate, but without NULL packets)
o Detected TS/UDP layout

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
o Detected conformance (DVB, MPEG, ATSC)1
o RMS jitter, in microsecond
- Service Level Monitoring
o Service bitrate
o Service ID
- PID level monitoring
o PID bitrate
o Stream types
o Additional descriptors that may be present in the PMT
Program
Level
IP Level PID Level

monitoring monitoring
TS Level
monitoring
PID / Program
detailsmonitor
Figure 25: Input Monitoring
1
The TITAN Mux will detect the conformance according to the T-STD descriptors (when present), or to the discovered
tables when missing. The conformance can be enforced when declaring the input.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Clicking on a program will display its details in the bottom frame of the monitoring page:
- PCR PID indicates the PID carrying the PCR clock

- PMT PID
- Service Name, when present in SDT (DVB)
- Service Provider, when present in SDT (DVB)
- Table descriptors (PMT, SDT …)
Clicking on a PID will display its details in the bottom frame of the monitoring page:
- Type: table type (PAT, PMT, SDT …) or Elementary Stream

- Stream Type
- PMT descriptors

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
C. Declaring an IP MPTS input
A new input is declared by clicking on the “New input” button, from the input dashboard menu (sub-menu
“Streams Input”). The menu shown in Figure 26 will be displayed. Once created, the input can be deleted
or modified by clicking the appropriate button on the right panel of the input dashboard.
The top-right drop selection box on the top-right hand corner of the central frame provides the possibility
to choose between configuring an IP or an ASI input.
1. IP Input
Figure 26: MPTS IP Input creation
All the parameters are hereinafter described:
ID Description Range
Defines the input name. This name is only used internally as an identifier
Enter Name String
in the web GUI, it is not related to any MPEG/DVB/ATSC Parameter.
Type Defines the type of redundancy None-Failover
If case of Failover redundancy, defines the failover recovery behavior.

- Failover-active: Mux joins both main and redundant multicasts Automatic-Toggle-
Mode
simultaneously Manual
- Failover-passive: Mux joins redundant multicast only on failure
Trigger Period Failover Trigger Period in ms. 50-5000
Transmission Defines the address family Unicast – multicast

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the listening multicast group; only used when the address family
IP Address IPv4 Address
is set to “multicast”
Port Defines the listening port [0; 65536]
Defines the listening interface. Note that the interface named after their
Interface Logical Name (alias), as defined in the system pages (please refer tosection Interface list
VIII.A)
When enabled: allows to filter input streams according to their source IP

Source Filtering enable - diable
address
When enabled, the TITAN Mux will dejitter the input stream based on the
incoming PCRs. When disabled, only the packet arrival time on the physical
Dejitter enable – disable
interface will be taken into account, yielding PCR inaccuracy.
Recommended value is “enable”.
Defines the input bitrate regulation mode, in bps. When in VBR, the
Mode CBR or VBR
maximum input bitrate must be specified.
For RTP input streams with FEC:

- When set to “disable” (default): FEC latency is 2*L*D
Low Latency FEC - When set to “enable”, FEC latency is L*[D+1] Enable - disable
L: nb of columns
D: nb of lines
The Maximum input bitrate must be specified when VBR mode is selected,
VBR Maximum Bitrate [0-50000000]
in bps.
Defines the input conformance. When left to “auto”, the TITAN Mux will
infer the standard based on the presence of tables in the stream. Can be
Auto, MPEG, DVB or
Standard overridden to MPEG, ATSC or DVB.
ATSC
Note: the conformance detection will be based on the presence of the
SDT/VCT table.
Table 1: MPTS IP Input creation parameters
Once the input is created, the TITAN Mux immediately joins the group (in case of Multicast address,
through emission of an IGMP “join” request) and starts reception of the stream. Note that the group will
only be left when the input is deleted.
After its creation, monitoring becomes available; the detected streams will also be present in the “output”
panel, and can be used to create an output. Please refer to section 0.
a) ST2022-1/2 detection
The TITAN Mux will automatically detect the RTP header and switch to RTP stack when required. In
addition, the TITAN Mux will listen to “Port+2/Port+4” so as to detect FEC extensions, and will
automatically apply Forward Error Correction whenever the streams are present.
Note: UDP reception will infer a 100ms additional input buffer
Note: FEC will infer an additional latency of 2*L*D IP frames, where L and D are the length of depth of the
FEC matrix, respectively.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
2. Redundancy
The titan Mux support the Failover redundancy. The primary source will automatically switch to the
secondary source when the first source disappears after a timeout period called “trigger period”.
2 types of failover modes are available:
- Failover-active: Mux joins both main and redundant multicasts simultaneously
- Failover-passive: Mux joins redundant multicast only on failure

This allows to reduce the amount of traffic on the input network interface
The behavior of the switching back to primary source is configurable by the mode:
- Automatic: the switch back is done when the primary source becomes available
- Toggle: the switch back is done when the secondary source disappears
- Manual: the switch back is done with a user action
The active source currently used can be seen in the general input page in the Redundancy section:
Active source
Manual trigger for switching

back to primary
Figure 27 Redundancy information

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
3. ASI Input
Figure 28: MPTS ASI Input creation
All the parameters are hereinafter described:
Defines the input name. This name is only used internally as an identifier
Enter Name String
Select the ASI port used to probe input. It must have been configured as
Port ASI input port list
Input ASI in order to appear in the selection list.
Defines the input conformance. When left to “auto”, the TITAN Mux will
infer the standard based on the presence of tables in the stream. Can be
Auto, MPEG, DVB or
Standard overridden to MPEG, ATSC or DVB.
ATSC
Note: the conformance detection will be based on the presence of the
SDT/VCT table.
Table 2: MPTS ASI Input creation parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
D. Virtual Services
Virtual services are used when input streams lack PAT and/or PMT. This allows to consider and remux
those streams just like normal TS.
Note that defining virtual services won’t prevent alarms such as “Pat missing” and “PMT missing”.
Virtual services configuration may be done for each input stream, by clicking on the “Virtual Services” link.
This main screen for virtual services allows to define the Pat transport stream ID. This is mainly used to
display on the input and input monitoring pages, as output will set its own value afterward.
A new virtual service can be defined by clicking on the “Add” button as explained below, and existing ones
can be edited/erased through action buttons (pen and trash)
Important note: Virtual services configuration is only saved and applied when the “Save” button is clicked.
The add/edit virtual service screen contains many parameters, explained hereafter:
- Program Number / PMT Pid / PCR Pid: labels are explicit. These decimal data are
mandatory. 0 can be used for PCR.
- New component sub-section:
 Type: hexadecimal format, 2 digits. The type of the component to be added
 Pid: new component pid (decimal).
 Descriptor: Add a new descriptor to the new component
 Tag: hexadecimal format, 2 digits
 Value: hexadecimal format, up to 100 digits. Only data, must not contains
tag nor descriptor length
 Add component button: Click on this button once the new component is fully
described
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- Components sub-section : contains the list of all defined components. They can be erased
by clicking on the cross on the right
- New outer descriptor sub-section: Defined a new descriptor (tag and value as described
above), to be added to the service.
- Outer descriptors sub-section: contains the list of all defined outer descriptors. They can
be erased by clicking on the cross on the right
1. Use case 1: input stream has no PAT

After being added, this input stream has a bit rate, and the monitoring page shows all the included pids.
However, the type of those pids and the services are unknown.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Once services and their components are declared on the virtual services page, there are visible on the
input monitoring, and can be remuxed like any other program.
Note that it is not possible to only define PAT and try to use already existing PMT info. All the services
and component must be redefined. However, if SDT is present in the stream and program numbers are
coherent, service name will be retrieved.
2. User case 2: input stream has no PMT

With this kind of streams, the main input page shows the services names and program number, as they
are recovered from PAT and SDT, but the monitoring cannot associate any pids with them.
When virtual services are created, the stream monitoring will show both virtual and original programs,
whereas only virtual ones will have associated pids/bitrates and are remuxable.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
If the same program number is chosen during virtual input configuration, virtual services will simply
override the previous one (and SDT info are used if coherent).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
E. Declaring an external PSI input
External PSI servers are typically used to mux tables that are generated at the back office level rather than
at the headend level, such as the EPG (carried by the EIT). In addition, the PSI Server can be used to define
all the stream tables. In such case, the Mux will only pass-through those tables and will not output
internally generated tables.
The TITAN Mux can accept external PSI tables for PAT, CAT, PMT, SDT, TDT, TOT, NIT and EIT. It will receive
the external tables through a multicast connection.
Declaring a new PSI input is done by clicking on the “New Input” button, from the input dashboard menu.
A PSI input is declared like a stream input.
Note: any stream can be used for external PSI ingest. For instance, one can use the tables from a given
MPTS by declaring one MPTS as a PSI server.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
V. Output
Any number of output streams can be declared. In the TITAN Mux design, an output is a MPTS output,
which can be mapped to any number of physical outputs. For instance, one MPTS can be output on 2
different Ethernet interfaces, for redundancy purposes.
A. Dashboard
The TITAN Mux offers a high level output view, which is meant to have an overview of all the configured
output streams. The streams are identified by their GUI identifier (refer to section V.B), and will show the
services that were configured inside the MPTS.
Figure 29: output overview
1. Monitoring
The TITAN Mux can monitor the output MPTS, by clicking on the “Monitoring” button, in the right panel
of the output dashboard. The monitoring will report a very similar information to the input monitoring
described in section IV.B. This is useful to ensure that the configuration precisely matches what is intended
before going “on air”. This monitoring will be active even though the output is stopped (meaning that no
packet are emitted). The typical workflow for creating an output would be:
- Output declaration
- Click on the Stop button in the right panel (by default, a newly created output has all its physical
outputs enabled)
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- Configuration of the input services
- Edition of the tables, descriptors, remapping, etc
- Monitoring of the output
- Once all the parameters have been checked in the output monitoring, turn the output on by
clicking on the start button in the right panel
Program
Level
IP Level
monitoring
PID Level
monitoring
TS Level
monitoring
PID / Program
detailsmonitor
Figure 30: Output monitoring
The monitoring parameters are hereinafter listed:
- IP Level monitoring
o Configuration reminder
- TS level monitoring
o Configured TS bitrate
o Total TS bitrate (measured; can be slightly varying around the configured value)
o Effective TS bitrate (same above, but without NULL packets)
o Clock reference PID: the PCR PID that is used to lock the output on2
- Service Level Monitoring
o Service bitrate
o Service ID
2
In version 1.1, the TITAN Mux will use an incoming PCR to lock its clock on.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
o Service Name, when present in SDT (DVB)
- PID level monitoring
o PID bitrate
o Stream types
o Additional descriptors that may be present in the PMT
Clicking on a program will display its details in the bottom frame of the monitoring page:
- PCR PID indicates the PID carrying the PCR clock

- PMT PID
- Service Name, when present in SDT (DVB)
- Service Provider, when present in SDT (DVB)
- Table descriptors (PMT, SDT …)
Clicking on a PID will display its details in the bottom frame of the monitoring page:
- Type: table type (PAT, PMT, SDT …) or Elementary Stream

- Stream Type
- PMT descriptors
B. Declaring a MPTS output

A new output is declared by clicking on the “New output” button, from the output dashboard menu. The
menu shown in Figure 31 will be displayed. Once created, the output can be deleted or modified by clicking
the appropriate button on the right panel of the output dashboard.
Figure 31: output creation

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the TS output name. This name is only used internally as an identifier in the web
N/A String
GUI, it is not related to any MPEG/DVB/ATSC parameter.
Bitrate Defines the total TS bitrate, in bits per second 0-210e6
Defines the TS ID, as defined in “ITU Information technology – Generic coding of moving
pictures and associated audio information: Systems-T H222.0“
Note: A program is denoted by a program_number which has significance only within a
ID transport stream. Where several transport streams are available to the decoder (e.g., in [0; 65536]
a cable network), in order to successfully demultiplex a program, the decoder must be
notified of both the transport_stream_id (to find the right multiplex) and the
program_number of the service (to find the right program within the multiplex).
(Original)
Defines the Network ID, as written in the Network Information Table, per ETSI 300468.
Note: The combination of original_network_id and transport_stream_id allow each TS to
be uniquely identified. Networks are assigned individual network_id values, which serve
as unique identification codes for networks. The allocation of these codes may be found [0; 65536]
in TS 101 162. The network_id and the original_network_id can take the same value, or
may have to take different values subject to the allocation constraints for
original_network_id and network_id as per TS 101 162.
Table 3: output creation parameters
Once all these parameters have been defined, a physical output must be declared. This can be done by
clicking on the “+ ADD” button on Figure 31
Figure 32: Physical output creation

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
This is the output IP address. If multicast, defines the multicast group. Otherwise, the
IP address IPv4 Address
destination address must be used for unicast
Port Defines the streaming port [0; 65535]
Defines the streaming interface. In case unicast is used, the destination address
Interface must be accessible from that interface. Note that the interfaces are named after [0; 65535]
their Logical Name (alias), as defined inVIII.A.
Defines the number of TS packets that will be carried by one Ethernet frame. 7 is a
Packets/Fram
very common value as it fits into the standard 1500 bytes MTU. [1; 7]
. That value will be the same for all interfaces of the output.
The ToS field (also known as DS field and ECN from RFC 2474) of the IPv4 header can
TOS be specified. Will typically be used when defining QoS rules on a downstream 0-255
switch/router.
Defines the network 'Time To Live' of multicast datagrams, to allow packet forwarding
TTL through all the network equipment. This field has no effect when streaming to a 0-255
unicast address
RTP Defines if RTP headers will be added to the output stream Enable/disable
Defines if the SSRC written in the RTP header is automatic or user-defined. This field
SSRC
is typically used by receivers to determine the source of the RTP packets.
When Enabled, additional SMPTE 2022 FEC streams will be output (on Dst Port + 2,
FEC Enable/Disable
Dst Port + 4) to allow error correction on error-prone networks
Scheme FEC Scheme. In 1D, only 1 stream will be output. 1D/2D
Defines the FEC matrix length and depth (parameters “L” and “D” in the ST2022-1/2
Dimension
standards)
Controls how the FEC packets are applied to media packets (i.e. the matrix shape).
Setting this parameter to '0' will lead to a square FEC matrix
Step 0-1
Figure 33: Square (step = 0) matrix (left) and on-square (step = 1) matrix (right)
Table 4: IP output parameters
In the current TITAN Mux version, the egress will not start right after an output has been declared: the
TITAN Mux needs at least one input service to be associated with the output before the streaming starts.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
This is because the TITAN Mux needs to re-create a precise clock from one of the input PCR streams before
it starts streaming.
C. Clock Selection
Add New
Clock

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
D. Program edition
Program edition allows to select the program (services) that will be muxed inside an output. The menu can
be accessed by clicking “Edit Programs” in the output dashboard. As depicted in Figure 34, the program
edition is divided in 3 panels:
- The left panel recaps all the configured inputs; it is basically an extract from the input dashboard.
- The middle panel recaps the programs that are included in a given output. Services can be dragged
and dropped from the left panel to the middle panel
- The right panel offers a program oriented view, with a recap of the program and the ability to edit
the program parameters.
Important: since version 1.4.5.0 streams added or modified to an output are not committed to the MUX
in real time. Thus the user can add or change a set of services and apply these modification at once using
the ‘Save’ button. Modifications can be discarded using the ‘Cancel’ button. This is called ‘Offline editing’
mode.
List of inputs
Per service
overview
List of services
in the MPTS
Figure 34: Program edition

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
1. Offline editing
The program edition is edited in offline mode. This means the user will have to commit its modifications
to the mux to take them in account. This is done by click on the ‘Save’ button. This button will be displayed
only if at least one modification has been done on the configuration. Multiple modifications can be done
before applying them to the MUX. Modification can be discarded by clicking on the ‘Cancel’ button.
Non committed modifications will be lost when leaving the edit program page. Moreover some action are
prohibited when an offline configuration is pending:
- Statmux group creating/editing/deletion.

- Pid merging
2. Adding streams
Input streams can be added to the output by using drag and drop from the “Input” list to the “Output”
column. Streams must be dropped onto the dashed rectangle named “Drop programs here”.
Once the stream has been dropped, the TITAN Mux will keep this new stream in a pending configuration.
Thus ‘Save/Cancel’ buttons will appear on the top of the page until the pending configuration is committed
or discarded. When the pending configuration is committed to the MUX it will immediately starts using
the new or modified services in the output, by updating all the necessary tables. This is completely
seamless and will not interrupt any other services.
Each new or modified services will be displayed on the UI with an orange indicator until they are
committed to the MUX. The meaning of the indicators colors are:
- Green: service is committed and enabled on the MUX

- Orange: service is modified in the pending configuration (new or modified)
- Grey: service is disabled (more details in Enabling/Disabling service section)
While an already committed service is under modification these modifications are not committed to the
MUX until the user save them by clicking on the ‘Save’ button.
The pending configuration will be lost when leaving the ‘Edit program‘ page.
The right panel will give information on the stream origination, and give the ability of quick editing a few
parameters on the output stream.
3. Enabling/Disabling service
Services added to an output can be enabled or disabled. By default when a service is added it will be
enabled when committed to the mux. The following figure illustrates the different use cases:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
1- An already committed running service. No pending modification on this service. To disable it, click
‘stop’ and save the configuration
2- An already committed stopped service. No pending modification on this service. To enable it, click
‘start’ and save the configuration
3- An already committed or new service under modification. When committed to the mux the service
will be enabled (default behavior)
4- An already committed or new service under modification. When committed to the mux the service
will be disabled
Enabling or disabling an already running service will not take effect immediately: the user have to commit
the pending configuration by clicking the ‘Save’ button.
E. Statmux
1. Overview
The goal of the statistical multiplexing is to optimize perceived video quality of a group of programs, by
allocating a bandwidth to each program in proportion to its complexity.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
The Titan Mux does dynamic statistical multiplexing: the incoming bandwidth is analyzed, and all the
remaining bandwidth is allocated to VBR/opportunistic pids, thus keeping the bitrate of the MPTS constant
and inserting as little null packets as possible.
2. Group types
In order to benefit from statistical multiplexing, programs should be placed in a statmux group. There are
2 types of groups: dynamic and static.
In the dynamic group, the bandwidth allocated to the group will change dynamically to adapt to changes
in the MPTS in order to keep the null packet rate very low. This is the typical use case for statistical
multiplexing.
In addition to the dynamic group, static groups can be created. In a static group, the bandwidth allocated
to the group is fixed to a user-defined bitrate. Note: the non-video pids of the programs are included in
the static group bandwidth, so the video bandwidth within a statmux group may vary to accommodate
non-video pids.
Dynamic and static groups can be combined, but only one dynamic group can be created within an MPTS.
3. Creating statmux groups

By default, a group named “Main group” appears in the “Edit programs” page. Programs added to the
main group will not be statmuxed.
New groups can be created by clicking the “Create group” button in the “Edit programs” page.
Name Logical name for the group (optional)
In a “dynamic” group, the bitrate of video streams will take all the available bandwidth in
the MPTS, dynamically adjusted according to the bitrate of generated SI tables, audio
Type streams… Note: only one dynamic group is allowed within an MPTS. Dynamic/Static
In a “static” group, the bitrate of video streams is adjusted so that the total bitrate of
programs (audio and video streams) in the group is always equal to the specified bitrate.
Group Only for static groups: specifies a constant bitrate for the statmux group. In bit/s. Must be
[10; 210000]
bitrate smaller than the MPTS bitrate.
Multicast The address of the multicast used for statmux communication. Should be the same as
IPv4 address
address configured in the Titan Live encoder.
Multicast The port number of the multicast used for statmux communication. Should be the same
[0; 65535]
port as configured in the Titan Live encoder.
Physical or logical
The physical interface used for statmux communication. Should be on the same network
Interface name of an existing
as the interface set in the Titan Live encoder.
interface or VLAN

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
The alternate physical interface used for statmux communication, that must be used when Physical or logical
Backup
communication is lost on the main interface. Should be on the same network as the name of an existing
interface
backup interface set in the Titan Live encoder. interface or VLAN
1. Adding programs to a statmux group

Once group are created, input streams can be added to groups by using drag & drop from “Input” list to
the “Drop programs” zone displayed for each group.
User will be asked for channel Id. This a common communication parameter shared between Titan Live
encoder & Mux to identify a regulated encoded program. Therefore it is mandatory to use same parameter
value between both products.
This parameter can also be found in Titan Live “MPEG TS muxer parameter”.
2. Editing statmux parameters
It is possible to have access to more parameters by highlighting the already added stream in a group and
then by clicking on “Statmux” icon in the right block column.
Shared parameter between Titan Live & Mux to identify a regulated service, used for
Channel ID
communication between both product.
Min bitrate User minimum video regulated bitrate

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Max bitrate User maximum video regulated bitrate
Quality Used to assign different weights to programs within a statmux group [0-100]
CBR enable When enabled, fixed the video TS bitrate to the specified CBR bitrate [enable/disable]
CBR bitrate Constant video TS bitrate in bps when CBR mode is enabled
F. Component rules
Component tracking/mapping is used to provide a static (PID-wise) output, even if PIDs dynamically change
in input. This tracking is only performed at the service level. Input PIDs within a service can thus be blocked,
passed or remapped, depending on a number of rules that apply hierarchically.
1. User-Defined rules
Figure 35: Component Rules
2. Component identification
Component can be identified, in that order:
- By their type (namely audio, video, subtitles, teletext, SCTE35 PID, MPE PID). Type can be wild
carded.
- By their codec. Codec can be wild carded.
- By their language, whenever applicable. Language can be wild carded.
- By their PID, whenever applicable. PID can be wild carded.
3. Component Rules
It must be possible to create rules:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- to pass-through an incoming component (pass-thru means that the output PID will follow the
input PID)
- to block an incoming component (the component will not appear in the output service (deleted
from the PMT)
- to remap an incoming component (the component will be passed to the output, but its output
PID will be modified)
Note: When several rules apply, the first (in ascending order) is considered.
Note: When no rules apply, the default one is considered: pass-thru everything.
4. Component tracking/mapping example

One wants to have a fixed PID output: one video on PID 1500, a French audio on PID 1600 and a French
dvb-sub component on the incoming PID. The input program layout dynamically changes between day-
time and prime-time.
Rule # Type Codec Language PID Type Output PID

1 Video * * * Remap 1500
2 * AC3 Fre * Remap 1600
3 * DVB-SUB * 710 Pass-Through n/a
4 * DVB-SUB Eng * Block n/a
5 * AC3 Eng * Block n/a
Default * * * * Pass-Through n/a
Input Output
Video: MPEG2, PID 500
Audio: AC3, PID 600, fre
Channel1, day
Audio: AC3, PID 601, eng
DVB-SUB, PID 710, fre Video: MPEG2, PID1500
Video: H.264, PID 510 Audio: AC3, PID 1600, fre
Audio: AC3, PID 610, fre DVB-SUB, PID 710, fre
Channel1, prime-time Audio: AC3+, PID 611, eng
DVB-SUB, PID 710, fre
DVB-SUB, PID 711, eng
5. Automatic component rules

The TITAN Mux may automatically create component rules, if needed by the output configuration. For
instance, if the same service is used twice in a given MPTS, the TITAN Mux will create PID based component
rules so as to remap the second service to other PIDs.3 Automatic remapping is done by selecting, for every
component for which a PID conflict exists, the first unused PID starting at PID value 1000.
Such remapping rules will appear in the main list, mixed with user-defined rules. Automatic rules can be
edited or deleted just like any other rules. But when deleting an automatic rule leads to a conflict, the
automatic rule is re-applied. This means that the only way to “merge” components in a single PID is to
force the remapping by creating a user-defined rule.
3
The tables will be merged rather than remapped.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
G. Program Edition
Programs inside a MPTS can be edited by clicking on “Edit Program” on the main output view. 2 sets of
parameters can be edited:
- SDT descriptors
- Rate limiting
Figure 36: Program Edition
1. Program Information
This section basically provides shortcuts to the Service Descriptor of the SDT, and allows to override the
service name, type, provider name and program number. The parameters of this section can be edited or
left to the input values.
Service Name Service Name, per ETSI 300468 SDT Service Descriptor. String
Provider Name Provider Name, per ETSI 300468 SDT Service Descriptor. String
Corresponds to the “service_type” field of the ETSI 300468 SDT Service

Service Type [0; 255]
Descriptor. Typical values can be found in the ETSI 300468 standard.
Program Number Corresponds to the program_number field of the program_map_section (PMT) [0; 65535]
Table 5: Program Information Parameter

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
2. Rate Control
In the current TITAN Mux version, rate limited can be enforced, on a per input service basis. The purpose
of rate limiting is to maintain the input bitrate of a given program under a user-defined threshold. This is
meant to ensure that the Mux will output a valid transport stream, even though one or several services
are exceeding their nominal rate.
Figure 37: Rate Limitation
Pass-Through,
Mode Defines the rate control mechanism.
Limited
TS bitrate, in bps, (without any IP headers) above which the mechanism will limit
Bitrate limit integer
the packets.
Table 6: Rate Limitation Parameters
H. PMT Edition
The PMT of a given input program can be fully edited. More specifically, it is possible to block/add all the
PMT descriptors, both in the inner or outer loop of the PMT, as described in the figure below. The inner
loop pertains to a given component (PID), while the outer loop is common for all components.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Outer loop
Inner Loop
Figure 38: PMT loop descriptions
Figure 39: PMT Edition

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Blocking/adding a descriptor is made through a menu that allows to preview the changes before applying
them. Once the blocking/edition rules have been setup, click on “Apply” to save and apply the changes to
the output stream.
1. Changing the PMT PID

The PID of the PMT (as declared in the PAT) can be changed; by default, it is left to the input value. When
the same PMT PID value is set for several programs, the TITAN Mux will automatically create a multi-
service PMT.
2. Blocking Descriptors
Figure 40: Descriptors PopUp
PMT descriptors can be blocked based on the PID they apply to and on the descriptor tag. Click on the
“New” button under the “Block Descriptors” to make the selection. Please note that the PID value must
be left empty to block an outer loop descriptor.
3. Adding Descriptors
Figure 41: Adding Descriptors PopUp
Descriptors can be added based on the PID they apply to, the descriptor tag and the descriptor
hexadecimal data.
Note: The TITAN Mux will not create descriptors for PIDs that do not exist. But one can create the rule,
which will be applied as soon as the PID becomes present in the service.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
I. Deleting a program
It is very easy to delete a program from an output MPTS, by clicking on the “delete program” label of the
main output view.
J. SI Edition
The TITAN Mux allows for in-depth edition of all the tables forming a MPTS. All the tables can be generated
internally, pass-thru, or disabled. In addition, external tables (that are not known by the TITAN Mux in that
version) can be muxed as well. Note that this section pertains to TS parameters. For per service
configuration, please refer to section V.H.
1. Output conformance
Only MPEG and DVB conformance can be selected in this version of the TITAN Mux.
- In MPEG conformance, only the PAT, PMT and CAT will be output.
- In DVB conformance, the PAT, CAT, PMT, SDT, TDT, TOT, NIT and EIT may be output.
The main SI edition window gives an overview of the table parameters, while the per-table settings can be
edited by clicking on the “Edit” label for every row.
Figure 42: SI Tables Edition
2. MPEG
a) PAT Edition
For each service in the multiplex, the PAT indicates the location (the Packet Identifier (PID) values of the
Transport Stream (TS) packets) of the corresponding Program Map Table (PMT). It also gives the location
of the Network Information Table (NIT).
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 43: PAT Edition
Defines the PAT generation mode.

- Enabled is internal generation. PAT will then be generated according to
the MPTS configuration.
- Disables means no PAT will be output. This is highly deprecated as it will
Enabled,
Mode yield an invalid output
Disabled, PSIG
- PSIG means that a PSI server, defined in section 0, is used for PAT
generation. Note that in such case, the TITAN Mux will not analyze the
PAT content to check that it is coherent with the current MPTS
configuration.
Period of occurrence of the PAT in the output stream. Default is 200ms. Applies
Period Integer
only when mode is set to “enabled.”
Table 7: PAT edition Parameters
b) CAT Edition
The CAT provides information on the CA systems used in the multiplex; the information is private and
dependent on the CA system, but includes the location of the EMM stream, when applicable.
Figure 44: CAT Edition
Defines the CAT generation mode.

- Enabled is internal generation. Note that the CAT will be empty if no
scrambling is defined.
- Disables means no PAT will be output. This is highly deprecated when
scrambling is defined, as a downstream equipment may use the CAT to Enabled,
Mode
perform descrambling. Disabled, PSIG
- PSIG means that a PSI server, defined in section 0, is used for CAT
CAT content to check that it is coherent with the current MPTS
configuration.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Period of occurrence of the CAT in the output stream. Default is 500 ms. Applies
Period Integer
Table 8: CAT Edition Parameters
c) PMT Edition
The PMT identifies and indicates the locations of the streams that make up each service, and the location
of the Program Clock Reference fields for a service. The PMT is related to a service; as such, edition of the
individual PMT can be made in the program edition, while the parameters that can be configured here will
be common to all the PMTs.
Figure 45: PMT Edition
Defines the PMT generation mode.

- Enabled is internal re-generation. PMT will then be generated according
to the services configuration/remapping rules/descriptor edition, as
defined in section V.E. By default, all the input descriptors will be
passed.
Enabled,
Mode - Disables means no PMT will be output. This is highly deprecated as this
Disabled, PSIG
will yield to an invalid output.
- PSIG means that a PSI server, defined in section 0, is used for PMT
PMT content to check that it is coherent with the current MPTS
configuration.
Period Period of occurrence of the PMT in the output stream. Default is 200 ms. Integer
3. DVB
a) SDT Edition
The SDT contains data describing the services in the system e.g. names of services, the service provider,
etc.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 46: SDT Edition
Defines the SDT generation mode.

- Enabled is internal re-generation. SDT will then be re-generated
according to the services configuration defined in section V.J.3. By
default, all the input descriptors will be passed (meaning that the
Enabled,
Mode service names/providers etc will be passed)
Disabled, PSIG
- Disables means no SDT will be output.
- PSIG means that a PSI server, defined in section 0, is used for SDT
SDT content to check that it is coherent with the current configuration.
Period Period of occurrence of the PMT in the output stream. Default is 200 ms. Integer
(1) Blocking Descriptors

SDT descriptors can be blocked based on the service they apply to and on the descriptor tag. Click on the
“New” button under the “Block Descriptors” to make the selection. Please note that the service value must
be left empty to block an outer loop descriptor.
(2) Adding Descriptors

Descriptors can be added based on the service they apply to, the descriptor tag and the descriptor
hexadecimal data.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Note: The TITAN Mux will not create descriptors for services that do not exist. But one can create the rule,
which will be applied as soon as the service becomes present in the MPTS.
b) TDT Edition
The TDT gives information relating to the present time and date. This information is given in a separate
table due to the frequent updating of this information.
The TITAN Mux uses its system clock (as defined in section VIII.E.3) to insert information in the TDT.
Figure 47: TDT Edition
Defines the TDT generation mode.

- Enabled is internal generation. TDT will then be generated according to
the time configuration defined in section VIII.E.3. Enabled,
Mode
- Disables means no TDT will be output. Disabled, PSIG
- PSIG means that a PSI server, defined in section 0, is used for TDT
generation.
Period of occurrence of the TDT in the output stream. Default is 15000 ms. Applies
Period Integer
Table 11: TDT Edition Parameters
c) TOT Edition
The TOT gives information relating to the present time and date and local time offset. This information is
given in a separate table due to the frequent updating of the time information.
The TITAN Mux uses its system clock (as defined in section VIII.E.3) to insert information in the TOT.
Figure 48: TOT Edition

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the TOT generation mode.
- Enabled is internal generation. TOT will then be generated according to
Enabled,
Mode the time configuration defined in section VIII.E.3.
Disabled, PSIG
- Disables means no TOT will be output.
- PSIG means that a PSI server, defined in 0, is used for TDT generation.
Period of occurrence of the TOT in the output stream. Default is 15000 ms.
Period Integer
Applies only when mode is set to “enabled.”
Table 12: TOT Edition Parameters
In addition, the TITAN Mux allows for edition of several local time offset descriptors, as per ETSI 300468;
the country_code, country_region, local_time_offset_polarity, local_time_offset, time_of _change and
next_time_offset can be editd for several different regions.
Figure 49: Time Offset Descriptor
d) NIT Edition
The NIT is intended to provide information about the physical network. In addition of offering an easy
configuration of the delivery descriptor and of the logical channel numbering descriptor4, the NIT allows
for adding additional descriptors to the generated NIT.
The TITAN Mux will automatically insert the “service list descriptor” in all the MPTS that share the same
network ID. It means that if several MPTS are declared in the Mux, the NIT of each of these MPTS will carry
4
This descriptor is outside of the ETSI 300468 recommendation, but is commonly used to provide an association
between the program number (declared in the PMT) and a channel number, as seen by the user on its TV set.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
information related to the other declared MPTS. For instance, if two MPTS A and B are declared as sharing
the same network ID, the NIT of service A will contain the service list descriptor both for MPTS A and B.
Figure 50: NIT Edition
Defines the NIT generation mode.

- Enabled is internal generation. Enabled,
Mode
- Disables means no NIT will be output. Disabled, PSIG
- PSIG means that a PSI server, defined in 0, is used for NIT generation.
Period of occurrence of the TOT in the output stream. Default is 15000 ms.
Period Integer
Applies only when mode is set to “enabled.”
Should be set to “auto”. In such case, the TITAN Mux will be responsible for
automatically defining the version number of the NIT. This version number is used
by the receiver to easily detect changes in the table.
Version Number
The version number can be overridden by a user-configurable value. In such case,
it will only change on configuration change. This can lead to unexpected receiver
behavior and is deprecated.
Defines the Delivery System Descriptor that will be inserted in the NIT. Can be
Cable, Satellite or Terrestrial. Each of those descriptors can be fully specified by
clicking on “details”.
Delivery Descriptors Note: the delivery descriptor will be inserted in the NITs of all the MPTS that share
the same network ID. For instance, if two MPTS A and B are declared as sharing
the same network ID, the NIT of service A will contain the delivery descriptor both
for MPTS A and B.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
This descriptor is outside of the ETSI 300468 recommendation. It is used to
provide an association between a TS program number and the channel number,
as seen by the user on its TV set or Set Top Box.
Logical Channel Its description can be found in “Free TV Australia Operational Practice OP-41”
Descriptor Note: several services can share the same logical channel, or several logical
channels can be used the same service. The TITAN Mux allows all of these
configurations.
Please
Table 13: NIT Edition Parameters
Figure 51: Logical Channel Descriptor edition
(1) Adding Descriptors

Descriptors can be added based on the service they apply to, the descriptor tag and the descriptor
hexadecimal data.
e) EIT Edition
The EIT contains data concerning events or programs such as event name, start time, duration, etc. TITAN
mux allows for passing/filtering EIT data, or using an external PSI server.
- In the case where an external PSI server is used, the TITAN Mux will only allow for a pure pass-
through of the incoming EIT.
- When passing incoming EIT, the TITAN Mux will aggregate and filter EIT so as to output an EIT that
only contains data that pertain to services that are present in the output MPTS.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 52: EIT Edition
Defines the EIT generation mode.

- Enabled is aggregation/filtering of the incoming EIT Enabled,
Mode
- Disables means no EIT will be output. Disabled, PSIG
- PSIG means that a PSI server, defined in 0, is used for EIT generation.
Period of occurrence of the EIT in the output stream. Default is 1000 ms. Applies
Period Integer
When mode is “Enabled”, this section will allow to select the services for which
Blocked Services
the EIT will be present in output.
When mode is “Enabled”, this section will allow to select tables to block according
Table Id
to their table Id, in addition of blocking on a service basis.
Scrambling Table 14: EIT Edition Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
4. ATSC
a) VCT
TO DO
b) MGT
TO DO
c) STT
TO DO
d) RRT
TO DO
e) EIT
TO DO
f) ETT
TO DO

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
VI. Simulcrypt Scrambling
The TITAN Mux is a fully DVB-CSA5 compliant mux, with a strict respect of the ETSI 103197 (“Simulcrypt”)
standard to achieve interaction with all the headend equipment.
The figure below shows which part of the SimulCrypt standard are performed by the TITAN Mux.
Figure 53: DVB-Simulcrypt overview
The TITAN Mux achieves scrambling through interaction with an ECM (Entitlement Control Message)
Generator and and EMM (Entitlement Management Messages) Generator, plus an optional PD (Private
Data) Generator. The communication between the Mux and these components is made through IP, and
by respecting the appropriate interfaces, as defined in ETSI 103197.
In concepts, the scrambling configuration in the Mux has to be done in several steps:
1. Configure connection to one/several ECMG servers

2. Configure connection to one/several EMMG/PDG servers
3. Configure ECM streams (by referring to an ECMG server)
4. Configure EMM/PD streams (by referring to an EMMG/PDG server)
5. Configure Scrambling Groups (SCG) by selecting output Services or PIDs that below to the
Scrambling Group, and associating the ECM PIDs. Scrambling will start as soon as the SCG is
5
Version 1.1 fully supports DVB-CSA2 encryption. Please contact the ATEME support team for availability of other
standards.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
created. The scrambling groups can be created either manually via the Mux GUI, or with an
external automation system (EIS).
A. Dashboard
The “scrambling” panel allows for:
- Have an overview of the SCS parameters and select options (Common scrambling
configuration, EIS parameters)
- Have an overview of the declared SCG (Scrambling Groups) and declare new ones
- Have an overview of the declared ECM Generators and declare new ones
- Have an overview of the declared ECM streams declare new ones
- Have an overview of the declared EMM/PD Generators and declare new ones
- Have an overview of the declared EMM/PD streams and declare new ones
Figure 54: Scrambling dashboard

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
B. SCS Configuration
This panel allows to configure common scrambling parameters on the Mux.
Settings defined in this “SCS configuration” are used for all scrambling operations performed on the Mux.
Table 15: SCS configuration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Pause all scrambling

This will suspend scrambling for all scrambled services on the Mux
 All scrambled services go to clear
Pause all
scrambling
Pause/Resume all Resume all scrambling
Scrambling This will resume all suspended scrambling.
Resume all
 All scrambled services go back to scrambled.
scrambling
NB: scrambling will not resume for services that have been deprovisioning by
EIS while in “pause”.
Whole service
Service scrambling “Whole service” permits to scrambled all PIDs or selecting only audio/video PIDs
Audio/Video only
In “Automatic” mode, repetition rate is given by ECMG.

ECM repetition rate It’s possible to force value by selecting value in the list (from 100ms to 500ms by 100ms to 500ms
step of 100ms)
When “enabled”, the Mux will use the specified delay_start value for all newly
User delay start instantiated scrambling operations.
When “diabled”, the Mux will use the delay_start value provided by ECMG
When “enabled”, the Mux will use the specified transition_delay_start value for
User transition delay all newly instantiated scrambling operations.
start When “diabled”, the Mux will use the transition_delay_start value provided by
ECMG
This button allows to purge all provisionning (current and pending events) done
EIS purge by EIS. A pop-up of confirmation will appear to confirm or cancel operation
N/A
provisionning
After this action, communication with EIS will be disconnected
Enable
communication with If sets, the EIS can be able to connect to Mux and sending events N/A
EIS
EIS mode EIS mode communication : DVB or OPENCAS String
Port Port that will be used to communicate to the ECMG server N/A
Interface Interface on which the TITAN Mux will listen to incoming EIS messages Network Interface
If enable, the CP duration will be set to the user value.

This parameter is not dynamic. If CP duration is changed, it will not impact CP
duration on already existing SCGs.
Set CP duration Integer
- Only new SCGs will use updated CP duration.
- For all SCGs to use updated CP duration, Mux application shall be
restarted.
If select, for incoming scheduling event, the Ecm pid will correspond to the ECM
Pid follows ECM ID N/A
ID

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Scrambling Start When “enabled”, the Mux will delay the activation time from the specified offset
Offset for all SCG provisioning messages received from EIS.
Scrambling Stop When “enabled”, the Mux will delay the activation time from the specified offset
Offset for all SCG deprovisioning messages received from EIS.
Table 16: SCS parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
C. Declaring an ECM Generator
The TITAN Mux allows declaration of 8 different ECMGs. A new ECMG is declared by clicking on the “New
ECMG” button.
Figure 55: ECM Generator declaration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the ECMG name. This name is only used internally as an identifier
N/A String
Corresponds to the CA_system_id field of the ETSI 103197 and ETR 162
CA System ID 16 bits integer
douments
CA_subsystem_id: system which handles multiple connections to ECMGs

with the same CA_system_id value
CA Subsystem ID 16 bits integer
Note: The combination of CA_system_id and CA_subsystem_id is called
super_CAS_id.
Application specific ID, allowing the association of application specific

Channel ID parameters with a given ECMG TCP connection. Integer
Note: Channels correspond on a one to one basis to TCP connections.
In case Channel ID is already used by ECMG, the ECMG will return an error
at channel establishment. In this case, if “auto increment” checkbox is
Auto increment Integer
toggled, then the Mux will increment the Channel ID value set in the GUI,
and try to establish a channel with this new value.
Channel_test Defines the emission period of channel_test messages from the Mux to
Integer
messages period ECMG (when channel test messages are enabled)
Defines the protocol version of the exchanged messages between Mux and
Protocol version Integer
ECMG
Use conformed
Use 48bit control word instead of 64bit
control word
SPF Bit When enabled, bit 54 of control word is set to 0
Declare 1 or more ECMG servers. If many ECMG servers are configured,

ECMG servers then it forms a pool of redundancy servers. Titan Mux will try to connect to
server with the highest level of priority.
IP IP address of the ECMG server IP
Port Port that will be used to communicate to the ECMG server Integer
Interface Network interface to use for communication to the ECMG server. Interface
CA Descriptors Allows to manually add CA descriptors in the PMT.
Table 17: ECM Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
D. Declaring an ECM stream
An ECM stream is a component that will be generated by the ECMG server, and that carries the control
word in a secure manner (plus private entitlement information). This content of this component is not
controlled by the TITAN Mux, but by the ECMG itself. Additional configuration is required for the ECMG to
send the appropriate component.
Figure 56: ECM Stream declaration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the ECM stream name. This name is only used internally as an identifier in the
N/A String
web GUI, it is not related to any MPEG/DVB/ATSC Parameter.
Corresponds to ECM_stream_id in ETSI 103197 standard. It uniquely identifies an ECM

ECM Stream ID Integer
stream within a channel (the channel being defined in the ECMG identification)
Corresponds to ECM_id in ETSI 103197 standard. It uniquely identifies an ECM stream

for a Super_CAS_id (which is the combination of CA_system_id and
ECM ID Integer
CA_subsystem_id). The combination of the « ECM » type, the Super_CAS_id and the
ECM_id identifies uniquely an ECM stream in the whole system.
Defines the ECMG server to use for generating the ECM component. The server must
ECMG have been previously defined
CA system specific information needed by the ECMG. In this version of the TITAN Mux,
Access Criteria this has to be manually entered and cannot be provisioned through the EIS  SCS String
interface.
Data to be inserted in the CA_Descriptors of the PMT. Corresponds to the

Private Data String
private_data_byte of the CA Descriptor, as described in ITU-T H.222.
Corresponds to nominal_cp_duration in ETSI 103197. This parameter indicates the

Crypto-period Integer
nominal duration of Crypto periods for the particular stream.
PID PID Value on which the ECM stream will be transmitted Integer
Table 18: ECM Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
E. Declaring an EMM/PD Generator
Entitlement Management Messages and Private Data are generated by the same equipment. Up to 8
EMM/PD generators can be declared in the TITAN Mux, by clicking on the “New EMM/PDG” button.
Figure 57: EMMG/PDG server declaration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the EMMG/PDG name. This name is only used internally as an identifier
N/A String
Corresponds to the CA_system_id field of the ETSI 103197 and ETR 162 douments.
Note: this setting is only used to check that the EMM/PD Generator that will
CA System ID Integer
connect to the TITAN Mux is using a CA System ID value defined in one the
declared ECMG. The connection will otherwise be rejected.
CA_subsystem_id: system which handles multiple connections to ECMGs with the

same CA_system_id value
CA Subsystem ID Note: this setting is only used to check that the EMM/PD Generator that will Integer
connect to the TITAN Mux is using a CA Subsystem ID value defined in one the
declared ECMG. The connection will otherwise be rejected.
This defines the expected maximum delay between the reception of 2 EMM
Max delay between
packets. If the Mux does not receive any EMM packet during this time duration, Integer
EMMs
then an alarm is raised.
Network control Allows to configure TCP connection with EMMG
Port Network port to use for listening to incoming EMM/PD generators connections Integer
Interface on which the TITAN Mux will listen to incoming EMM/PD Generators
Interface Network Interface
connections
Network dataflow Allows to configure EMM dataflow connection: either via UDP, or TCP
Transmission TCP or UDP TCP/UDP
(For UDP only) Interface on which the TITAN Mux will listen to incoming EMM
Address IP
data
Port (For UDP only) Network port to use for listening to incoming EMM data Integer
(For UDP only) Interface on which the TITAN Mux will listen to incoming EMM
Interface Network Interface
data
Table 19: EMM Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
F. Declaring an EMM/PD Stream
EMM streams are components that carry private Conditional Access information which, for example,
specifies the authorization levels of subscribers or groups of subscribers for services or events. Private
Data streams component are additional streams that are Conditional Access specific.
Figure 58: EMM/PD Stream declaration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the EMM/PD stream name. This name is only used internally as an
N/A String
identifier in the web GUI, it is not related to any MPEG/DVB/ATSC Parameter.
Must correspond to the data_id in ETSI 101397 recommandation.

Data ID The data_id is allocated by the CAS and uniquely identifies an EMM/private data Integer
stream of a client_id.
Defines if the declared stream will be an Entitlement Management Message

Data Type N/A
component or a private data component
Defines the EMMG/PDG server to use for generating the ECM component. The
EMM/PDG server must have been previously defined (refer to VI.E Declaring an EMM/PD Server
Generator)
Data to be inserted in the CA_Descriptors of the CAT. Corresponds to the

Private Data String
private_data_byte of the CA Descriptor, as described in ITU-T H.222.
PID PID Value on which the EMM/PD stream will be transmitted Integer
Maximum bitrate Bitrate (in bps) at which the EMM/PD streams will be transmitted. Integer
Table 20: EMM Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
G. Creating Scrambling Groups (SCG)
A Scrambling Group is a group of components (PIDs or services) that are scrambled with the same control
word.
Each Scrambling Group is associated with an ECM stream, or several ECM streams in the case of Simulcrypt.
Table 21: Scrambling Group parameters
To create a new SCG, click on “New SCG” button. The SCG ID and Crypto Period has to be filled:
Table 22: SCG creation
Then on the Scrambling Group configuration page:
- Drag and Drop components or services from “Outputs” (left pane) to the “Drop services or pids”
drag and drop zone (central pane).
- Drag and Drop ECMs from the “ECM Streams” (right pane) to the “Drop ecms” drag and drop zone.
Once a SCG is defined, scrambling for this SCG starts immediately. SimulCrypt operations can be done by
assigning several ECM streams to the SCG.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
H. Inserting EMM Streams
These operations are performed in the “Outputs” panel, by clicking “Configure Scrambling” after selection
of a given output MPTS.
EMM/PD streams are associated to a whole MPTS rather than to a single service. Hence, EMM/PD streams
can be added to an output simply by dropping a defined stream onto the output. The EMM/PD stream will
be muxed as soon as it is dropped on the output. Note that several EMM/PD streams can be multiplexed
inside a given output (typically for SimulCrypt).
Table 23: EMM insertion

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
VII. BISS-1 Scrambling
Titan Mux can scramble services according to BISS Mode 1, as specified in standard EBU Tech 3292 rev.2.
BISS-1 is activated per service on the "OUTPUTS > PROGRAMS > PROGRAM EDITION" page.
2 parameters must be configured by the user:
- BISS Mode (0 or 1)
By default, a service is not scrambled (BISS Mode 0).
When Mode 1 is selected, then service is scrambled with DVB CSA algorithm.
- Session Word (12 hexadecimal digits).

This is the fixed Key used to scramble the service.
To scramble with DVB-CSA algorithm, Mux derives a 64-bit key from the Session Word
A BISS-1 scrambled service is identified by a "lock" icon in the Output Monitoring page.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
VIII. System
The System panel allows setting parameters linked to the network and the underlying Operating system:
- Management of ASI interfaces

- Management of network interfaces and VLAN
- Configuration of Alarms and SNMP
- Configuration Import and Export
- Time setting, manual or through access to an NTP external server
A. ASI Management
TITAN Mux detects the number of physical ASI interfaces available on the System and lists them on the ASI
Management sub-page.
ASI interfaces
Figure 59: ASI Management
TITAN Mux lists the ASI interfaces detected on the system6. It is not mandatory to have any ASI interface
available on the system, as only a minimum of one IP interface is needed in order for it to be functional.
Each interface row reports information about the associated interface.
Parameter Read / Write Description Range
Interface connectivity status. Grey

Port R/W when disabled, Red when Link is down, Green, Red, Grey
Green when link is established.
6
TITAN Mux does not limit the number of ASI interfaces on the system.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Interface identification in the
Logical Name R/W eth0/1/.…/N
underlying Linux system
Input Informs about the possibility to

R Green, Red
Capability configure the interface as an Input
Output Informs about the possibility to

R Green, Red
Capability configure the interface as an Output
Configure Interface as an Input or

I/O Select R/W Input, Output
Output, depending on capabilities
Table 24: ASI interface information and configuration
B. Network Management
TITAN Mux detects the number of physical Ethernet interfaces available on the System and lists them in
the top-hand side table of the ‘Network Management’ sub-page. This page also offers the possibility to
create and manage VLAN, as well as set a gateway address.
Physical
Interfaces
VLAN
configuration
Gateway
configuration
Figure 60: Network Management

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
1. Physical interface
The Titan Mux lists the network interfaces detected on the system7. A minimum of one interface is needed
in order for the system to be functional. Each interface row reports information about the associated
interface.
Parameter Description Range
Interface connectivity status. Grey when disabled, Red when Link is down,
Status Green, Red, Grey
Green when link is established.
Interface Interface identification in the underlying Linux system eth0/1/.…/N
MAC MAC address of the detected interface. Mac address
Version of the IGMP protocol. This indicates the detected version, i.e. the
IGMP V2
version declared by the IGMP querier inside the interface network.
Table 25: Physical interface information
Each row also offers the possibility to configure its interface according the following parameters.
State Enables or disables the interface. Up, Down
Choose the method to set the IP address and netmask: either static or from
Method Static, DHCP
a DHCP server.
Address IP address in IPv4 format (static method only) Unicast IP address
Netmask Netmask in IPv4 format (Static method only) IP netmask
Label to indicate the purpose of the interface, for example “Management’,

Logical Name ‘Input, ‘Output’, ‘InOut’. Logical names will be listed in selectable interfaces String
when creating/editing an input or an output.
Auto, 10/Half, 10/Full,

Method to initiate the negotiation mode (half/duplex) and speed with the
Link Speed 100/Half, 100/Full,
connected network device. Auto
1000/Half, 1000/Full
Table 26: Physical interface configuration
2. VLAN management
VLAN (Virtual LAN) are used to create virtual sub-networks on a physical infrastructure, without additional
equipment. Any number of virtual interfaces can be created. Virtual interfaces can then be used exactly
like the physical interfaces for receiving or sending IP transport stream. The only difference in configuring
VLANs is that three other parameters need to be specified:
- The associated physical interface,

- The VLAN ID (12-bit field specifying the VLAN to which the frame belongs, and that will be used to
“tag” the frames)
7
The TITAN Mux does not limit the number of physical interfaces on the system.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- The VLAN priority indicates the frame priority level; values are from 0 (best effort) to 7 (highest).
These values can be used to prioritize between different classes of traffic.
3. Gateway configuration
Setting up the Gateway is done on the bottom of the ‘Network Management’ page by entering the default
gateway address, ticking the ‘Route is enabled’ checkbox and validating with the ‘SAVE’ button. Although
this is primarily meant for granting access to the management interface, this gateway applies to all the
interfaces, physical or virtual.
C. Alarm Management
Figure 61: Alarm Management
Alarm management is divided in two parts: the left side is related to the SNMP configuration, while the
second one allows the configuration of each individual alarms.
1. SNMP Configuration
The TITAN Mux allows to change the SNMP community strings for Read-Only (default string: public) and
Read/Write communities (default string: private).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Traps can be enabled at a system level by clicking the “Enable traps” checkbox; when enabled, all the
alarms defined in the right panel may or may not trigger the emission of a trap, depending on the per-
alarm configuration.
Traps can be sent to up to four receivers; please note that the TITAN Mux will automatically select the
appropriate combination or interface/route to reach the recipients that are defined here.
2. Alarms configuration
The right panel allows for configuration of individual alarms. An event that occurs on the TITAN Mux can
trigger an alarm on the GUI and emission of a trap (if enabled at a system level). The TITAN Mux offers the
ability to enable/disable the traps individually.
Alarm name Description
Will be raised when a given configuration exceeds the pre-computed processing capability of the
machine. The input configuration will be rejected but the current services must not be stopped.
Not enough CPU
Note: This alarm is never raised in version 1.4 of the TITAN Mux.
Will be raised when the measured CPU usage exceeds 80% of the total available CPU.
CPU alert
Will be raised when the input configuration is invalid (bitrate out of range, PID out of range, etc.)
Invalid Configuration
Will be raised when the NTP/PTP server cannot be reached.

NTP/PTP alarm
Will be raised when the incoming configuration makes use of a licensed feature for which the license
could not be found.
License missing
Raised when the input is missing (no received packet)

UDP Packet missing
Will be raised when UDP Packet missing is not raised (UDP frames are received), but when the
TS packet missing module failed to lock on TS packets (0x47 missing)
Will be raised when TS packet missing is not raised (TS packets are detected), but when TS packets
Unaligned TS packet are not aligned on UDP frame.
Will be raised when TS packet missing is not raised (TS packets are detected), but when the number
Unstable TS packet of TS packets per IP frame varies over time.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Will be raised when no PCR PID was found in the input stream, or when the user-specified PID does
PCR missing not carry any PCR.
Will be raised when the software PLL fails to lock. Will typically be the case when network jitter
PCR unlock exceeds 100ms or when the PCR values are invalid.
Will be raised when at least one UDP frame is missing in any of the inputs. Note that the TITAN Mux
IP frame missing
can detect UDP and RTP missing frames.
Will be raised when the detected offset between the two incoming ST2022-7 streams exceed the
configured skew (resulting in the stream being unprotected)
Invalid skew
Will be raised when no TS level alarm are raised, but when no PAT was found in the incoming
transport stream.
PAT missing
Will also be raised when configuring an external PAT that can’t be found.
Will be raised when the PMT of a service which is configured for output is not found in input.
PMT missing
Will also be raised when configuring external PMTs that can’t be found.
SDT missing Will be raised when an external SDT has been defined, but could not be found.
Will be raised when an external EIT has been defined, but could not be found.
EIT missing
Will be raised when an external VCT has been defined, but could not be found.
VCT missing
Will be raised when an external ETT has been defined, but could not be found.
ETT missing
Will be raised when a PID that was configured in output (and which is referenced by the PMT) cannot
PID missing
be found.
Input stream link down Will be raised when an Ethernet link, used for stream ingest, is detected as down.
Output stream link down Will be raised when an Ethernet link, used for stream egress, is detected as down
Will be raised when the sum of the streams forming an output exceeds the total bitrate defined for
TS Output overflow
that output.
Will be raised when a given input exceeds the bitrate that was configured in the rate limiting
Rate limiting overflow
configuration of that input.
CC error Will be raised when continuity counter errors are detected on the input.
Will be raised when the PIDs to be merged do not share the same clock source.
Unsync PID

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Will be raised when the round trip time for statmuxed encoder communication exceeds 50ms.
High RTT
Will be raised when the TITAN Mux received a statistic from the encoder at a time that prevents the
TITAN Mux from emitting an appropriate bitrate order.
Late statistic
Will be raised by the TITAN Mux when it did not receive a statistic report from one encoder.
Lost statistic
Reported by the TITAN Mux when one encoder reports that it received a bit rate order that could
not be applied because it was too late.
Late bitrate order
Reported by the TITAN Mux when one encoder reports that it detected a missing bitrate order.
Lost bitrate order
Raised when communication is lost with a statmuxed encoder, but stream is still received
Communication error
Raised when communication is lost with an encoder, and no stream is received

Encoder error
Raised when some IP frames are discarded because the link is full. This will typically be the case
IP output overflow when the link is at 100 mbps but the total of the outgoing transport stream exceeds 100 mbps.
Raised when descrambling has been enabled on a stream that is not scrambled.
Already unscrambled Note: the TITAN Mux relies on the “scrambled bits” inside the TS packet header to detect
scrambling.
Raised when scrambling has been enabled on a stream that is already scrambled.
Already scrambled
Note: the TITAN Mux relies on the “scrambled bits” inside the TS packet header to detect
scrambling.
Raised when there was no control word update for more than 60 seconds.
Missing SCG update
A control word arrived but its starting point elapsed.

SCG update late

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
ECMG communication Communication with ECMG server has been lost.
error
Alarm reported by the ECMG module.

ECMG alarm
EMMG communication Communication with EMMG server has been lost.

error
Alarm reported by the EMMG module.

EMMG alarm
Communication with EIS server has been lost.

EIS Communication error
Alarm reported by the EIS module.

EIS alarm
Input interface redundancy was triggered.

Input interface switch
Input Transport Stream redundancy was triggered.

TS redundancy
Input Service redundancy was triggered.

Service redundancy
Unit became active/inactive.

Unit redundancy
Will be raised when the RIP alarm was triggered, resulting in changing the RIP metric.
RIP redundancy
Figure 62: Alarm list
D. System Information
This section is divided in two sub panels: the left panel gives hardware related information, while the right
one is dedicated to the troubleshooting of the unit.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 63: System Information
1. System Information
Those information are gathered from the hardware, or from the virtualization layer.
- CPU information include the CPU type, its frequency, the number of cores (note that this
information can be biased in case of virtualization), and the real CPU usage, as reported by the
underlying Linux system.
- Memory information include the total amount of RAM and the amount of RAM that is currently
used.
- Virtualization type reports the kind of detected hypervisor.
2. Diagnostic package
Those package are meant to ease the troubleshooting of the system/configuration; hence, it must only be
used upon ATEME support team request.
E. System Management
The System Management page offers the possibility to manage Titan Mux configuration through import,
export and clear functions, set the time configuration manually or through an NTP server and update the
TITAN name.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 64: System Management
1. Set Titan Mux name

The TITAN Mux name displayed on the GUI can be modified. To do so, update the field “Set Titan Mux
name” and apply the modifications. The number of characters is limited to 24 for a human readable
display. The TITAN name is now available on the banner and the web browser tab.
Figure 65: Setting TITAN name
2. Export and Import a configuration

It is possible to Import and export a JSON-format text file describing the “Processing” configuration of the
Titan Mux. The “Processing” configuration covers the comprehensive configuration of inputs (stream,
It is possible to Import and export a JSON-format text file describing the “Processing” configuration of the
Titan Mux. The “Processing” configuration covers the comprehensive configuration of inputs (stream,
PSIG, …) and outputs (declared output TS and associated features).
Exporting the current configuration is done by clicking on the ‘Export Configuration’ button. A JSON file
with formatted-name ‘Titan_Mux_Conf_AAA_MM_DDTHH_MM_SS+GMT.json’ is saved if the current
download folder. Example: Titan_Mux_2016_03_25T11_01_55+01.json.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 66: Configuration Export
By default, no EIS provisioning configuration is exported. To export pending provision, “With Pending Eis
provisioning” have to be selected. To export active provision, “With Active Eis provisioning” have to be
selected. Both options can also be selected in order to export all Eis provision.
To import a previously saved configuration file, click on “Import Configuration”. A file-browsing window
opens up. Select the appropriate JSON file and validate.
It is also possible to clear the current Titan Mux configuration to get back to an initial state with an empty
configuration. This is done by clicking on the ‘Clear Configuration’ button which leads to a validation box.
This does not restart the Titan Mux and will only clear its processing configuration, e.g. Inputs and Outputs.
System configuration, including network interfaces, will be left unchanged. Alarm history will also be
preserved.
Figure 67: Clear Configuration
3. System Time setting

The System time can be set either manually or through an external NTP server with the parameters offered
on the ‘Time Configuration’ frame located on the right-hand side of the ‘System Management’ page.
Defines the time setting mode, either manually, or through an external

Configuration mode NTP, Manual
NTP server.
Time Zone Selects the Time Zone, in both Manual and NTP modes. Time zone list
NTP server address IP address of the external NTP server (NTP mode only) Unicast IP address
Date Date string (Manual mode only) AAA-MM-DD
Time Time edition boxes (Manual mode only) Hours, Minutes, Seconds
Table 27: Time Configuration parameters
Once the configuration has been properly set, click on the “APPLY CONFIGURATION” button to validate.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
IX. Logging Configuration
This page offers the possibility to configure a connection with a remote client which will be forwarded
syslog messages.
Logging
Configuration
Figure 68: logging configuration
Checked = enabled,
Enable log forwarding Checkbox to enable or disable syslog forwarding to a remote client.
Unchecked = disabled
Syslog protocol Selects the protocol used for syslog connection with remote client. UDP or TCP
Syslog client address IP address of remote syslog client Unicast IP address
Syslog client port Port of remote syslog client [0; 65536]

Figure 69: Logging configuration parameters
Once parameters have been set, click on the ‘Apply Configuration’ button validates the new logging
configuration.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com

Transforming Video Delivery: User Manual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Transforming Video Delivery: User Manual

Uploaded by

Copyright:

Available Formats

Transforming Video Delivery

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Copyright (c) ATEME

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Figure 1: TITAN Mux ecosystem

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

A. ISO installation on a Bare Metal server

Download and install Win32DiskImager on a Windows PC. The tool is available at

Figure 2: ISO to USB

Figure 3: ISO installation – start menu

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Figure 5: ISO installation – select hard drive

Figure 6: ISO installation – network configuration

Figure 7: Figure 8: ISO installation – setting IP address

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Figure 11: ipconfig – setting eth0 gateway

1. Setting IP network in console mode

Choose the interface to configure:

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Choose static of DHCP mode:

Figure 13: ipconfig – interface mode

Figure 14: ipconfig – IP address

Set the interface netmask:

Figure 15: ipconfig – Netmask

Figure 16: routeconfig – gateway enabling

Enter gateway address:

Figure 17: routeconfig – gateway address

2. Setting IP network in USB mode

 Format a USB flash disk in FAT32,

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

address and netmask are mandatory, the gateway field is optional.

B. VM installation on a vSphere ESXi server

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Rename the Titan Mux VM according to your needs.

Figure 20: VM installation – Name

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Once completed, TITAN Mux VM is ready to deploy.

Figure 22: VM installation – Ready to deploy

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Ex: “titanmux-1_4_2_4-x64-debian8.tar”, or « titanmux.rar ».

To run Titan Mux container, the steps below shall be followed:

Then, the Mux GUI is accessible though port 80.

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

Step 0: Back up TITAN Mux configuration

Step 1: Add R/W rights to TITAN Mux destination folder if needed

Step 2: transfer the Debian packages

scp *.deb titan@titan_mux_ip_address:/home/titan

Step3: update TITAN Mux

Once the Debian packages are copied, update TITAN Mux:

TITAN Mux is now updated!

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

The following sections are organized following that scheme:

- Input stream declaration is detailed in section IV

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

- A MPTS or SPTS, that will carry services to be re-muxed

Figure 24: Input overview

Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

IP Level PID Level

Figure 25: Input Monitoring

- PCR PID indicates the PID carrying the PCR clock