TitanMUX-UM-v1 5 9

I.
Transforming Video Delivery

simulcrypt
User Manual
Version 1.5.9
Green Plaza, 6 rue Dewoitine Société Anonyme au capital de 1.410.903,62 €

78140 Vélizy-Villacoublay 1 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. simulcrypt .............................................................................................................................................. 1
II. Introduction ......................................................................................................................................... 10
III. Installation ....................................................................................................................................... 11
A. ISO installation on a Bare Metal server ........................................................................................... 11
1. Setting IP network in console mode ................................................................................... 13
2. Setting IP network in USB mode ......................................................................................... 15
B. VM installation on a vSphere ESXi server ........................................................................................ 16
C. Run Titan Mux as a Docker Container ............................................................................................. 20
D. TITAN Mux shell upgrade ................................................................................................................ 21
IV. TITAN Mux design............................................................................................................................ 22
V. Input .................................................................................................................................................... 23
A. Dashboard ....................................................................................................................................... 23
B. Monitoring ....................................................................................................................................... 23
C. Declaring an IP MPTS input ............................................................................................................. 26
1. IP Input ............................................................................................................................. 26
2. Redundancy ...................................................................................................................... 29
3. ASI Input ........................................................................................................................... 33
D. Virtual Services ................................................................................................................................ 34
1. Use case 1: input stream has no PAT .................................................................................. 35
2. User case 2: input stream has no PMT ................................................................................ 37
E. Declaring an external PSI input ....................................................................................................... 38
VI. Output ............................................................................................................................................. 39
A. Dashboard ....................................................................................................................................... 39
1. Monitoring ........................................................................................................................ 39
B. Declaring a MPTS output ................................................................................................................. 41
C. Clock Selection................................................................................................................................. 45
D. VBR (Variable Bit Rate) Bandwidth Shaping .................................................................................... 46
1. Bandwidth shaping without statmux (statistical multiplexing) ............................................ 46
2. Statmux output with VBR external components ................................................................. 46

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
E. EAS (Emergency Alert System) Output Configuration..................................................................... 49
F. Program edition............................................................................................................................... 50
1. Offline editing ................................................................................................................... 51
2. Adding streams.................................................................................................................. 52
3. Enabling/Disabling service ................................................................................................. 52
G. Component rules ............................................................................................................................. 53
1. User-Defined rules ............................................................................................................. 54
2. Component identification .................................................................................................. 54
3. Component Rules .............................................................................................................. 54
4. Component tracking/mapping example ............................................................................. 55
5. Automatic component rules ............................................................................................... 55
H. Program Edition ............................................................................................................................... 55
1. Program Information ......................................................................................................... 56
2. BISS Scrambling ................................................................................................................. 56
3. PCR ................................................................................................................................... 56
4. Rate Control ...................................................................................................................... 57
5. Define SCTE35 triggers ....................................................................................................... 57
I. Configure Slate ................................................................................................................................ 58
J. Configure Service Replacement ...................................................................................................... 58
K. PMT Edition ..................................................................................................................................... 65
1. Changing the PMT PID ....................................................................................................... 67
2. Changing the PID ordering ................................................................................................. 67
3. Overriding the stream_type value of components .............................................................. 67
4. Blocking Descriptors .......................................................................................................... 68
5. Adding Descriptors ............................................................................................................ 70
L. Deleting a program .......................................................................................................................... 70
M. SI Edition ...................................................................................................................................... 70
1. Output conformance ......................................................................................................... 70
2. MPEG Table ....................................................................................................................... 71
3. DVB Table.......................................................................................................................... 74
4. ATSC Table ........................................................................................................................ 86
N. PSIP Generator ................................................................................................................................ 93
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
O. SIMULCRYPT PSIG Generator .......................................................................................................... 94
VII. Statmux ........................................................................................................................................... 97
A. Overview.......................................................................................................................................... 97
B. Group types ..................................................................................................................................... 97
1. Creating statmux groups .................................................................................................... 97
C. Adding programs to a statmux group ............................................................................................. 99
D. Editing statmux parameters .......................................................................................................... 100
E. Troubleshoot Channel ID conflicts ................................................................................................ 100
F. Using static statmux group for bitrate reservation ....................................................................... 102
G. Configuration of meta encoder in a statmux pool ........................................................................ 102
H. Seamless service switch in time-share multiplex .......................................................................... 106
I. Statmux bitrate monitoring ........................................................................................................... 107
VIII. Simulcrypt Scrambling ................................................................................................................... 109
A. Dashboard ..................................................................................................................................... 110
B. SCS Configuration .......................................................................................................................... 111
C. Declaring an ECM Generator ......................................................................................................... 113
D. Declaring an ECM stream .............................................................................................................. 117
E. Declaring an EMM/PD Generator ................................................................................................. 118
F. Declaring an EMM/PD Stream....................................................................................................... 121
G. Creating Scrambling Groups (SCG) ................................................................................................ 122
H. Inserting EMM Streams ................................................................................................................. 123
I. Pause / Resume scrambling .......................................................................................................... 124
1. Pause All Scrambling processing ....................................................................................... 124
2. Resume all scrambling ..................................................................................................... 124
3. Pause Scrambling by output ............................................................................................. 125
4. Pause Scrambling by service............................................................................................. 126
IX. BISS-1 Scrambling .......................................................................................................................... 127
X. System ............................................................................................................................................... 128
A. ASI Management ........................................................................................................................... 128
B. Network Management .................................................................................................................. 129
1. Physical interface............................................................................................................. 130
2. VLAN management .......................................................................................................... 130
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
3. Gateway configuration .................................................................................................... 131
C. Alarm Management....................................................................................................................... 131
1. SNMP Configuration ........................................................................................................ 131
2. Alarms configuration ....................................................................................................... 132
3. Additional alarms from hardware sensors ........................................................................ 135
D. System Information ....................................................................................................................... 135
1. System Information ......................................................................................................... 136
2. Diagnostic package .......................................................................................................... 137
3. Hardware monitoring ...................................................................................................... 137
E. System Management..................................................................................................................... 137
1. Set Titan Mux name ......................................................................................................... 137
2. Export and Import a configuration ................................................................................... 138
3. System Time setting......................................................................................................... 138
F. Logging Configuration ................................................................................................................... 140
G. Hardware monitoring .................................................................................................................... 140

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Table of figures
Figure 1: TITAN Mux ecosystem .................................................................................................................. 10
Figure 2: ISO to USB..................................................................................................................................... 11
Figure 3: ISO installation – start menu ........................................................................................................ 11
Figure 4: ISO installation – confirm install................................................................................................... 12
Figure 5: ISO installation – select hard drive ............................................................................................... 12
Figure 6: ISO installation – network configuration...................................................................................... 12
Figure 7: Figure 8: ISO installation – setting IP address .............................................................................. 12
Figure 9 Figure 10: ISO installation – setting Netmask ............................................................................... 13
Figure 11: ipconfig – setting eth0 gateway ................................................................................................. 13
Figure 12: ipconfig – interface selection ..................................................................................................... 14
Figure 13: ipconfig – interface mode .......................................................................................................... 14
Figure 14: ipconfig – IP address................................................................................................................... 14
Figure 15: ipconfig – Netmask ..................................................................................................................... 14
Figure 16: routeconfig – gateway enabling ................................................................................................. 15
Figure 17: routeconfig – gateway address .................................................................................................. 15
Figure 18: USB network - file creation ........................................................................................................ 16
Figure 19: VM installation - Source ............................................................................................................. 17
Figure 20: VM installation – Name .............................................................................................................. 17
Figure 21: VM installation – Network Mapping .......................................................................................... 18
Figure 22: VM installation – Ready to deploy ............................................................................................. 18
Figure 23: VM installation - Console ........................................................................................................... 19
Figure 24: Input overview............................................................................................................................ 23
Figure 25: Input Monitoring ........................................................................................................................ 24
Figure 26: MPTS IP Input creation ............................................................................................................... 26
Figure 27 Redundancy information ............................................................................................................. 30
Figure 28: MPTS ASI Input creation ............................................................................................................. 33
Figure 29: output overview ......................................................................................................................... 39
Figure 30: Output monitoring ..................................................................................................................... 40
Figure 31: output creation........................................................................................................................... 42
Figure 32: Physical output creation............................................................................................................. 43
Figure 33: Square (step = 0) matrix (left) and on-square (step = 1) matrix (right)...................................... 45
Figure 34: Program edition.......................................................................................................................... 51
Figure 35: Component Rules ....................................................................................................................... 54
Figure 36: Program Edition.......................................................................................................................... 56
Figure 37: Rate Limitation ........................................................................................................................... 57
Figure 38: PMT loop descriptions ................................................................................................................ 65
Figure 39: PMT Edition ................................................................................................................................ 66
Figure 40: Program PSI edition .................................................................................................................... 68
Figure 41: Descriptors PopUp...................................................................................................................... 69
Figure 42: Adding Descriptors PopUp ......................................................................................................... 70

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 43: SI Tables Edition ......................................................................................................................... 71
Figure 44: PAT Edition ................................................................................................................................. 71
Figure 45: CAT Edition ................................................................................................................................. 72
Figure 46: PMT Edition ................................................................................................................................ 73
Figure 47: SDT Edition ................................................................................................................................. 75
Figure 48: SDT Carouseling from a Multicast source .................................................................................. 76
Figure 49: TDT Edition ................................................................................................................................. 76
Figure 50: TOT Edition ................................................................................................................................. 77
Figure 51: Time Offset Descriptor ............................................................................................................... 78
Figure 52: TOT Carouseling from a Multicast source .................................................................................. 79
Figure 53: NIT Edition .................................................................................................................................. 80
Figure 54: Logical Channel Descriptor edition............................................................................................. 81
Figure 55: NIT Carouseling from a Multicast source ................................................................................... 82
Figure 56: EIT Edition ................................................................................................................................... 83
Figure 57: EIT Carouseling from a Multicast source .................................................................................... 84
Figure 58: BAT Edition ................................................................................................................................. 85
Figure 59: VCT Editing ................................................................................................................................. 86
Figure 60: MGT Editing ................................................................................................................................ 87
Figure 61: STT Editing .................................................................................................................................. 88
Figure 62: RRT Editing.................................................................................................................................. 89
Figure 63: EIT Editing ................................................................................................................................... 91
Figure 64: ETT Editing .................................................................................................................................. 93
Figure 65: PSIP Generator configuration ..................................................................................................... 94
Figure 66: DVB-Simulcrypt overview ......................................................................................................... 109
Figure 67: Scrambling dashboard .............................................................................................................. 110
Figure 68: SCS configuration ..................................................................................................................... 111
Figure 69: ECM Generator declaration...................................................................................................... 113
Figure 70: ECM Stream declaration........................................................................................................... 117
Figure 71: EMMG/PDG server declaration ................................................................................................ 119
Figure 72: EMM/PD Stream declaration ................................................................................................... 121
Figure 73: Scrambling Group parameters ................................................................................................. 122
Figure 74: SCG creation ............................................................................................................................. 122
Figure 75: EMM insertion .......................................................................................................................... 123
Figure 76: Pause/Resume all scrambling................................................................................................... 124
Figure 77: Pause/Resume scrambling by output ...................................................................................... 125
Figure 78: Pause/Resume scrambling by service ...................................................................................... 126
Figure 79: ASI Management ...................................................................................................................... 128
Figure 80: Network Management ............................................................................................................. 129
Figure 81: Alarm Management.................................................................................................................. 131
Figure 82: Alarm list................................................................................................................................... 135
Figure 83: System Information .................................................................................................................. 136
Figure 84: System Management ............................................................................................................... 137
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 85: Setting TITAN name .................................................................................................................. 138
Figure 86: Configuration Export ................................................................................................................ 138
Figure 87: Clear Configuration .................................................................................................................. 138
Figure 88: logging configuration................................................................................................................ 140
Figure 89 - hardware monitoring .............................................................................................................. 141

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
II. 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
III. 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_5_5_1-0-official-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-1_5_5_1-0-official-x64-debian8.tar”
- Run the Docker image with command: (see below for –shm-size option value)
“docker run --privileged -d -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro --shm-size=XXX --net=host
titanmux-1_5_5_1-0-official-x64-debian8”
- Check the docker container is running with command
“docker ps”
Then, the Mux GUI is accessible though port 80.
NB:
Option "--shm-size" refers to the size of /dev/shm in the container. The size of /dev/shm is dependent on
the Mux configuration (nb of inputs and outputs).
It can be computed as follows: ShmSize = 8m * NbInputs + 70m * NbOutputs
For example: for 1 MPTS out and 8 multicast in mux input, this is 8 * 8 + 70 = 131m
Docker run command line would then be:
“docker run --privileged -d -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro --shm-size=131m --net=host titanmux”

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
IV. 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 Streams (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 V

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

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
V. 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 V.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
IP Level TS Level
monitoring monitoring
Program
Level
monitoring
PID Level
monitoring PID / Program
details
monitoring
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:
- Program number
- 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

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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
Criteria Defines the criteria the TITAN Mux uses to take failover decisions TsPresency-ETR101290
Trigger Period Failover Trigger Period in milliseconds. TsPresency criteria only 50-5000 ms
Automatic switch Health Period, in s, during which the inactive source must be healthy
1-3600 s
delay before triggering the failover or switching back to the primary.
CC errors can cause failover (ETR101290 criteria only).

The following parameters can be set:
CountinuityCount
- Timeframe : time interval on which to count CC errors Enable-disable
failover
- Threshold : number of CC errors to see on the time frame before taking
the failover decision
Transmission Defines the address family Unicast – multicast
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 to Interface list
section X.A)
When enabled: allows to filter input streams according to their source IP

Source Filtering enable - disable
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”.
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

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines how PCR pids are used for computing packet timestamping and
dejittering
- Default : All found PCR pids are used Default,

Input PCR ref - Forced PCR PID : only one pid is used, that must be defined in Forced PCR,
the “Pid” Parameter PID-Auto
- Auto : one pid is used, if pid becomes no longer reliable, it
switches automatically on a more reliable pid belonging to the
MPTS
Pid PCR Pid to be used when Input PCR ref is set to “Forced PCR PID”
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 VI.
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 failover redundancy of the titan Mux can be configured choosing different type:
Active/Passive/Manual based on different criteria: TS loss or ETR 101290 errors.
3 types of failover types are available:
- Failover-active: The Mux analyses both primary and secondary multicasts simultaneously.
In TS Loss configuration the primary will switch to the secondary if the TS disappears during the
“Trigger period” and the secondary was present during the last “Automatic switch delay” period.
In ETR 101290 configuration the primary will switch to the secondary if the criteria are not
respected on the active source while they are on the secondary during the last “Automatic switch
delay” period.
- Failover-passive: Mux joins redundant multicast only on failure.

This allows to reduce the amount of traffic on the input network interface.
- Failover-manual: Failover and switch back are only trigged manually.
The behavior of the switching back to primary source is configurable by the mode:
- Automatic: The switch back is automatically triggered:

When in TS Loss criteria, if the primary source was available during the last “Automatic switch
delay” period.
When in ETR101290 criteria, if no errors have been detected on the primary source during the last
“Automatic switch delay” period.
- Toggle: The switch back is done only when the secondary is not more eligible according to similar
triggering policy of Automatic mode.
- Manual: the switch back is done by user action

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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
1+3 Redundancy support

When redundancy is using “TS Loss” trigger, it is possible to add up to 3 secondary IP sources by clicking
on “Add secondary IP source”
Each secondary IP source can be configured independently for its address, port, interface and filtering
options. When more than one secondary source is present, each source can be removed individually.
Reconfiguring secondary sources may introduce a short interruption of service when the input is being
updated.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
The table below summarizes the semantics of the different redundancy modes when multiple secondary
sources are configured
Redundancy Type Redundancy mode Criteria Source switch sequence

Failover-Active Automatic TS Loss Input source will switch automatically from
primary to secondary when TS loss is
detected in the primary source. If the
secondary source is down, input switches to
another secondary source automatically in
the sequence secondary 1..N. If the primary
source returns, input switches back to
primary automatically. User intervention is
not possible in this mode.
Toggle TS Loss Input source automatically switches from

primary -> secondary 1..N -> primary -> …
whenever a TS loss is detected for the
currently active source. User can manually
switch source in the same loop sequence.
Manual TS Loss Input source will switch automatically from

the sequence secondary 1..N. There is no
automatic switch to primary even if it is
available. The user must intervene to switch
back to primary.
Failover-Passive Toggle TS Loss Input source automatically switches from

primary -> secondary 1..N -> primary -> …
whenever a TS loss is detected for the
currently active source. User can manually
switch source in the same loop sequence.
Manual TS Loss Input source will switch automatically from

the sequence secondary 1..N. There is no
automatic switch to primary even if it is
available. The user must intervene to switch
back to primary.
Failover-Manual No automatic source switch. User can cycle

through primary -> secondary 1..N -> primary
->…

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
When input redundancy is configured, the main input page will display the list of configured secondary
sources and highlight the active secondary source if the primary is no longer the active source.
First secondary source is active

(source #0 highlighted)
Secondary source pool information
3. ASI Input
Figure 28: MPTS ASI Input creation

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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
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 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.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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
- 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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.
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
VI. 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 VI.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 V.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
IP Level
monitoring
TS Level
monitoring
Program
Level
monitoring
PID Level
monitoring
PID / Program
details
monitoring
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
o Service Name, when present in SDT (DVB)
- PID level monitoring
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 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 31: output creation
Defines the TS output 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.
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
ID [0; 65536]
within a transport stream. Where several transport streams are available to the
decoder (e.g., in 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

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
multiplex) and the program_number of the service (to find the right program within
the multiplex).
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
Original
serve as unique identification codes for networks. The allocation of these codes may [0; 65536]
Network ID
be found 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.
Can be one of the following values

Fixed PCR: only PCR in the PID defined in the ‘ClockSource Pid’ field is used
Clock [Fixed PCR,
Auto PCR : Titan Mux tries to find another PCR PID when the current one fails
Reference Auto PCR, NTP]
NTP : Use the NTP source defined in the ‘Ntp source’ field as the clock reference. (See
C for NTP source creation)
Clock Source
Pid / Ntp Pid or Ntp source, when clock reference is Fixed PCR or NTP
source
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 with [0; 65535]
their Logical Name (alias), as defined in X.A.
None; Failover-
Defines the output redundancy. If enabled, TITAN Mux automatically switches to the
Passive -Auto;
Redundancy backup interface when a link-down occurs (aka interface bonding). The switch back
Failover-Passive-
strategy can be automatic or manual
Manual
Backup Applies only when Redundancy is set to Failover-Passive.

interface Defines the backup ethernet port
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]
e
. 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
1D-Column
Scheme FEC Scheme. In 1D, only 1 stream will be output. 1D-Row
2D
Defines the FEC matrix length and depth (parameters “L” and “D” in the ST2022-1/2
Dimension
standards)

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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.
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. VBR (Variable Bit Rate) Bandwidth Shaping
It is possible to reshape the output bandwidth of externally merged components to a bitrate different from
their input bitrate. There two possible use cases:
1. Bandwidth shaping without statmux (statistical multiplexing)

Static bandwidth shaping can be applied to VBR external components if the output is not
subject to statistical multiplexing.
2. Statmux output with VBR external components

In the presence of statmux, we can configure both static and dynamic bandwidth shaping.
In dynamic bandwidth shaping, the mux adapts the bandwidth reservation dynamically to
ensure that the external components are evacuated within a specified delay.
The Bandwidth shaping configuration page is visible in the “Edit Output” page when creating or updating
an output.
Bandwidth shaping in the multiplexer uses an opportunistic approach to replace null stuffing packets with
the externally merged components. In the absence of a dynamic statmux pool, only static shaping is
available. The output configuration must allocate enough output bandwidth to accommodate the rate
specified in the bandwidth reservation. When a dynamic statmux pool is present, bandwidth reservation
for shaping is determined automatically by the configured nominal and maximum bandwidth.
Each external VBR component has a specific output delay. This is the additional delay applied to the
component on top of the default mux latency. A component with a lower delay has priority over other
components with a higher delay

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
a) Configuring static bandwidth shaping
In static bandwidth shaping, the nominal rate and maximum rate must be identical. All components listed
in the configuration page will be evacuated in an opportunistic manner. In the absence of a dynamic
statmux pool, the bandwidth of the output must be configured with an additional stuffing rate equal to
the specified shaping rate. When used in the presence of a dynamic statmux pool, the stuffing rate is
allocated automatically.
b) Configuring dynamic bandwidth shaping

Dynamic bandwidth shaping requires an active dynamic statmux pool to automatically reserve bandwidth
between the nominal and maximum rate. In this mode of operation, the nominal rate is always reserved
regardless of presence of VBR components. The nominal rate can be zero because the bandwidth shaping
algorithm will automatically adapt to incoming VBR components
c) Estimation of configuration values

Due to the variable rate nature of external components, it is not always possible to know the true bitrate
of each VBR component. A more reliable measure would be the payload size of these components and the
duration of their transit. As an example, if we need to transmit bursts of 400 packets of EMM within a 10
second period, we are expected to evacuate 400 * 188 * 8 = 601600 bits in 10 seconds. For a standard mux
configuration with a default latency of 500ms and a nominal statmux delay of 2000ms, we can configure
a nominal rate of 0 and a maximum bitrate of
(601600 / (10 – 2.5)) * 2 = 160426 bps
Bitrate reservation in a statmux pool is not immediate. There is a total delay of 2000ms plus the mux end
to end delay before the rate changes. This constraint limits dynamic bandwidth shaping to values of
maximum delay of at least 2.5 seconds. Scaling the maximum bitrate reservation by 2 ensures that the

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
reservation ramps up and down in a progressive manner to avoid sudden changes in video quality for the
statmux pool (cf diagram below).
t b’
Area under rectangle = t * b
Area under triangle = t * b’ / 2 b
Areas are identical if b’ = 2 * b
For shorter delays, it would be necessary to configure a nominal rate to reserve a static rate. In the
above example, we can try to evacuate the same payload in 2 seconds if we allocate a nominal rate of:
601600 / 2 = 300800 bps
It is not necessary to scale static nominal rate reservation because bandwidth is fixed and doesn’t change
with respect to incoming VBR components.
An alternative configuration is possible if we consider nominal rate and maximum rate together. If the
nominal bitrate is set to 50000, we can estimate the maximum rate as:
(601600 – 2.5 * 50000) / (10 – 2.5) * 2 = 127093 bps
Depending on the specific requirements and characteristics of the VBR components, the configuration
values can be estimated by considering the following parameters:
• Total payload of all external components

• Maximum delay admissible for these components
• Maximum bandwidth reduction admissible for video statmux
• Nominal static bandwidth reduction admissible for video statmux
The delay can be specified individually for each VBR component. Components are evacuated in order of
priority of their maximum delay since arrival. i.e. a component with a maximum delay of 10s that arrived
8 seconds ago (2s left before obsolete) will be evacuated in priority compared to a component with a
delay of 4s that just arrive 1s ago (3s before obsolete).
d) Bandwidth shaping alarms

When a component is not evacuated within the specified delay, a data shaping overflow alarm will be
raised. It is necessary to increase either the nominal, the maximum or both nominal and maximum rate to
evacuate the component in time. Alternatively, the delay for the component should be increased if it is
not possible to increase the bandwidth.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
E. EAS (Emergency Alert System) Output Configuration
Titan Mux supports EAS service override, allowing broadcasters to replace the configured services contents
with an EAS content automatically. This feature requires the configuration of an EAS input source and
attaching this input source to a specific output. When input content is detected in the EAS input, the output
automatically replaces all output services with the EAS contents with full PMT update to signal the
replacement. This feature is accessed via the “Edit EAS” configuration item in the output configuration
page:
The configuration item opens a new page that allows setting the EAS input source for triggering EAS service
override. The user is strongly advised to set up EAS input sources using the Virtual Services feature (see
chapter V.D Virtual Services on page 34). Only inputs with a virtual service configure will be proposed by
the EAS configuration page.
The input dropdown list allows the user to choose from the list of declared Virtual Service as the EAS trigger
input. The program ID, PCR PID and Slate PIDs will be retrieved from the Virtual Service. It is possible to
override these values but is not advised because doing so disables the automatic update if the Virtual
Service is reconfigured after configuring the output.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
When an output is configured with EAS service override, the Program Slate feature (see chapter H.5 on
page 57) will no longer be available. Additionally, all programs in the output with EAS will have additional
PIDs that are tagged EAS to indicate the alternate content.
The input that is used as an EAS source will not raise alarms for missing input because this is the normal
condition. When input content is detected in the EAS source, the output will trigger service override to
replace the original service PIDs by the EAS content PIDs. An alarm “EAS service override active” will be
raised for each output. When the EAS input stops receiving, the output will switch back to the original
service and clear the “EAS service override active” alarm.
To delete EAS from the output, simply select None for the EAS input in the configuration page.
F. 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.
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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.
Per service
overview
List of inputs
List of services
in the MPTS
Figure 34: Program edition
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

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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. active service
2. deactivated service
3. Uncommitted modifications
Committed states
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- The services have been modified and pending a commit. In the above screenshot, “France 2 HD”
has been modified and will be stopped when committed while “Statmux_Ch1” will be active when
committed.
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.
G. 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
1. User-Defined rules
Figure 35: Component Rules
2. Component identification
Component can be identified, in that order:
- By their type (namely audio, video, dvbsub, scte35, other). 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:
- 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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.
H. 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
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
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
2. BISS Scrambling
See chapter IX
3. PCR
PCR can be extracted to an independent PID. In this case PCR is copied into a new generated PID, and
previous PID carrying the PCR is automatically blocked.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
As an example, it’s a way to create a Radio service from a TV service where the PCR is carried by video.
4. 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
5. Define SCTE35 triggers

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
In the “Trigger Sources” panel, select the input sources on which the service is waiting for SCTE35 triggers.
It can be itself or not.
On the “Trigger Actions” panel, define the different actions to be applied when the trigger is detected.
Only blocking pid actions are currently available.
Associated meta-encoder can also switch from VBR to CBR in regional mode, and from CBR to VBR in
national mode, in reaction to trigger change, if the option is set in meta-encoder options
I. Configure Slate
Slate configuration can be edited by clicking on “Configure Slate” on the output view.
Service mode can be selected on this screen, and can take two values:
- Active: pids defined as ‘Slate pids’ in the list below are blocked
- Slate: All pids except those defined as ‘Slate pids’ in the list below are blocked
In the ‘Slate pids’ input area, define pids blocked in ‘Active’ mode., separated by semicolons.
The slate mode in pids is applied after component rules. For instance, if a pid remapping is defined on a
slate pid, the output pid must be written here.
J. Configure Service Replacement

Service Replacement can be used to replace at the output one incoming service by another one, by keeping
the output PID values unchanged.
Attached to a primary output service, one or more services can be added to act as backup services.
Components PIDs belonging to the backup services are remapped to the primary one.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Trigger that make TITAN Mux switch from the primary service to the backup one can be manual or
automatic.
Manual trigger can be done through the graphical interfaces or through the REST API.
Automatic trigger occurs when the TS input of the output service is lost. If the main input service is lost,
TITAN Mux automatically switches and re-multiplexes at the output the first backup input service. If this
one also disappears from the input, TITAN Mux switches to the second backup input service and so on.
Once the main input service is back, TITAN Mux automatically switches back to it.
This capability can also address the EAS requirements.
For proper functioning of Service Replacement capability, attention must be paid to the configuration.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
a) Output Edition
Output shall be configured with “Pid auto remapping” disabled
b) Program Edition
Disable follow input mode

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
c) Program PSI edition
Disable PMT PID “Same PID as input” and fix PMT output program’s PID
d) Configure backup services

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Add backup services
e) Configure Remapping of component PID

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Remapping rules can be built with an input PID available on selected input or with a custom PID.
Do not forget to save configuration

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
f) Select switching mode
g) Manual switching
Click on one of the inactive services to replace the active service

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
K. 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.
Outer loop
Inner Loop
Figure 38: PMT loop descriptions

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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. Changing the PID ordering

By default, when a service is remuxed, Titan Mux uses the same PID ordering as in the input service PMT.
It is possible to modify the PID ordering, using the up/down arrows in front of each PID:
To revert to the default PID ordering, use “DEFAULT PID ORDERING” button. This will discard all ordering
operations performed by the operator.
3. Overriding the stream_type value of components

It is possible to force the stream_type value for each PID/component (to replace original stream_type
value).
To prepare a stream_type override configuration:
- Check the “Override stream type value” checkbox for the PID(s) to be obfuscated
- Set the stream_type value to be used ( in decimal)
Then, to enable/disable the stream_type overriding:
- If “Activate stream type ordering” is checked: strem_type overriding configuration is ENABLED

- If “Activate stream type ordering” is unchecked: strem_type overriding configuration is DISABLED

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
4. Blocking Descriptors
The list of PMT descriptor available output are displayed on the bottom of the Program PSI edition page
Figure 40: Program PSI edition

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
There is an enhanced parsing for Conditional Access descriptor to display the Conditional Access System
Identifier and ECM PID that it describes.
PMT descriptors can be blocked based on the PID they apply to and on the descriptor tag. For
Conditional Access descriptors (Descriptor Tag: 0x9), the configuration can be more precise by specifying
CA System ID and/or ECM Pid.
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.
For CAS descriptor if CA System ID and ECM Pid are left empty then all CAS Descriptor will be blocked.
Otherwise, only the one which matches the exact defined value will be blocked.
Figure 41: Descriptors PopUp

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
5. Adding Descriptors
Figure 42: 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.
L. 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.
M. 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 VI.H.5.
1. Output conformance
MPEG, DVB and ATSC 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. Some table
can be computed internally or can be received from a PSIG generator, see chapter O
- In ATSC conformance, the PAT, CAT, PMT, STT, MGT, VCT, RRT, ETT and EIT may be output. Some
table can be computed internally or can be received from a PSIP generator, see chapter N
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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 43: SI Tables Edition
2. MPEG Table
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).
Figure 44: PAT Edition

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

- “Carouseling” means that TITAN Mux carousels by itself the PAT table,
with a configurable period.
- “Disabled” means that TITAN Mux does not output any PAT. This is
Carouseling,
highly not recommended as it yields an invalid output.
Mode Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through a PAT table
Through
coming from a live input feed, without any modification (external
carouseling mode). Note that in such case, TITAN Mux does not analyze
the PAT content to check that it is coherent with the current output
multiplex configuration.
Applies only when mode is set to “Carouseling”.

Defines the source of the PAT information:
- “Internal” means that the PAT is internally built according to the
output multiplex configuration.
Internal
- “PSIP Generator” means that the PAT table is received from an
Source PSIP Generator
external PSIP Generator. Available only in ATSC compliance if PSIP
PSIG Generator
source is selected
- “PSIG Generator” means that the PAT table is received from an
external PSIG Generator. Available only in DVB compliance if PSIG
source is selected
Period of occurrence of the PAT in the output stream. Default is 200ms.

Period Integer
An additional PMT can be referenced in the PAT, based on a program number and
Additional PMT a PMT PID value
Applies only when mode is set to Internal Carouseling.
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 45: CAT Edition

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

- “Carouseling” means that TITAN Mux carousels by itself the CAT table,
- “Disabled” means that TITAN Mux does not output any CAT. This is
definitively not recommended as a downstream equipment may use Carouseling,
Mode the CAT to perform descrambling. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through a CAT table Through
the PAT content to check that it is coherent with the current output

Defines the source of the CAT information:
- “Internal” means that the CAT is internally built according to the
Internal, PSIP
Source output multiplex configuration. Note that the CAT is empty if no
Generator
scrambling is defined.
- “PSIP Generator” means that the CAT table is received from an
external PSIP Generator.
Period of occurrence of the CAT in the output stream. Default is 500 ms.
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 PMT’s.
Figure 46: PMT Edition

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

- “Carouseling” means that TITAN Mux carousels by itself the PMT table,
- “Disabled” means that TITAN Mux does not output any PMT. This is
definitively not recommended as it produces an invalid output. Enabled,
Mode
- “Pass-through” means that TITAN Mux passes through a PMT table Disabled, PSIG
the PMT content to check that it is coherent with the current output

Defines the source of the PMT information:
- “Internal” means that the PMT is internally built according to the
services configuration/remapping rules/descriptor edition, as defined
in section VI.G. By default, all the input descriptors are passed. Internal,
Source - “PSIP Generator” means that the PMT table is received from an PSIP Generator
external PSIP Generator. Available only in ATSC compliance if PSIP PSIG Generator
source is selected
- “PSIG Generator” means that the PMT table is received from an
external PSIG Generator. Available only in DVB compliance if PSIG
source is selected
Period of occurrence of the PMT in the output stream. Default is 200 ms.
Period Integer
Table 9: PMT Edition Parameters
3. DVB Table
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 47: SDT Edition
Defines the SDT generation mode.

- “Carouseling” means that TITAN Mux carousels by itself the SDT table,
- “Disabled” means that TITAN Mux does not output any SDT. Carouseling,
Mode - “Pass-through” means that TITAN Mux passes through an SDT table Disabled, Pass-
coming from a live input feed, without any modification (external Through
carouseling mode). Note that in such case, the TITAN Mux does not
analyze the SDT content to check that it is coherent with the current
service configuration.

Defines the source of the SDT information:
- “Internal” means that the SDT is internally built according to the
Internal,
Source services configuration defined in section VI.M.3. It also merges all the
Multicast
corresponding descriptors coming from the input(s)
- “Multicast” means that the SDT table is received from an input TS over
IP stream.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Period Integer
Period of occurrence of the SDT in the output stream. Default is 200ms.
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
Blocked Descriptors the selection. Please note that the service value must be left empty to block an
outer loop descriptor.
Applies only when mode is set to “Carouseling” and source to “Internal”.
Descriptors can be added based on the service they apply to, the descriptor tag
Added Descriptors and the descriptor hexadecimal data
Applies only when mode is set to “Carouseling” and source to “Internal”.
Applies only when mode is set to “Carouseling” and source “Multicast”
Defines the input TS over IP stream, which provides the Incoming SDT tables to
Input carousel. This section also allows restamping the SDT table ID (to convert an SDT
actual in an SDT other or inversely) or blocking the SDT tables based on their
table ID.
Table 10: SDT Edition Parameters
Figure 48: SDT Carouseling from a Multicast source
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 X.E.3) to insert information in the TDT.
Figure 49: TDT Edition

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

- “Carouseling” means that TITAN Mux carousels by itself the TDT table,
with a configurable period. Carouseling,
Mode - “Disabled” means that TITAN Mux does not output any TDT. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through an TDT table Through
carouseling mode).

Defines the source of the TDT information:
Source Internal
- “Internal” means that the TDT is internally built generated according to
the time configuration defined in section X.E.3

Period Integer
Period of occurrence of the TDT in the output stream. Default is 15000ms.
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 X.E.3) to insert information in the TOT.
Figure 50: TOT Edition
Defines the TOT generation mode.

- “Carouseling means that TITAN Mux carousels by itself the TOT table,
with a configurable section rate. Carouseling,
Mode - “Disabled” means that TITAN Mux does not output any TOT. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through a TOT table Through
carouseling mode).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the source of the TOT information to merge in the TOT output table
- “Internal” means that the TOT is internally built generated according to Internal,
Source
the time configuration defined in section X.E.3 Multicast
- “Multicast” means that the TOT table is received from an input TS over
IP stream.

Period Integer
Period of occurrence of the TOT in the output stream. Default is 15000ms.
Allows the addition of one or multiple local time offset descriptors, as per ETSI
300468; the country_code, country_region, local_time_offset_polarity,
Descriptors
local_time_offset, time_of_change and next_time_offset can be edited for
several different regions.

Defines the input TS over IP stream, which provides the Incoming TOT tables to
Input
carousel. This section also allows restamping the TOT table ID or blocking the
tables based on their table ID.
Table 12: TOT Edition Parameters
Figure 51: Time Offset Descriptor

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 52: TOT Carouseling from a Multicast source
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
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.
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
Figure 53: NIT Edition
Defines the NIT generation mode.

- “Carouseling means that TITAN Mux carousels by itself the NIT table,
Mode - “Disabled” means that TITAN Mux does not output any NIT. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through the NIT tables Through
carouseling mode).

Defines the source of the NIT information:
Internal, PSIP
Source - “Internal” means that the NIT is internally built.
Generator
- “Multicast” means that the NIT tables are received from an input TS
over IP stream.
Period of occurrence of the NIT in the output stream. Default is 2000ms.

Period Integer
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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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”.
Note: the delivery descriptor will be inserted in the NITs of all the MPTS that share
Delivery Descriptors
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.
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.
User Descriptors and the descriptor hexadecimal data.

Defines the input TS over IP stream, which provides the Incoming NIT tables to
Input
carousel. This section also allows restamping the NIT table ID (to convert an NIT
actual in an NIT other or inversely) or blocking the tables based on their table ID.
Table 13: NIT Edition Parameters
Figure 54: Logical Channel Descriptor edition

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 55: NIT Carouseling from a Multicast source
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 56: EIT Edition
Defines the EIT generation mode.

- “Carouseling means that TITAN Mux carousels by itself the EIT tables,
Mode - “Disabled” means that TITAN Mux does not output any EIT. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through the EIT tables Through
carouseling mode).

Defines the source of the EIT information:
- “Internal” means that TITAN Mux cherry-picks from the input(s) the EIT
Internal,
Source associated to the services, which are re-multiplexed at the output
Multicast
(according to the configuration defined in section VI.M.3).
- “Multicast” means that the EIT tables are received from a TS over IP
input stream.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Period Integer
Period of occurrence of the EIT in the output stream. Default is 1000ms.
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.

Defines the input TS over IP stream, which provides the Incoming EIT tables to
Input carousel. This section also allows restamping the EIT table ID (to change the EIT
type), blocking the tables based on their table ID and customizing the repetition
period based on the table ID.
Table 14: EIT Edition Parameters
Figure 57: EIT Carouseling from a Multicast source
f) BAT Edition
The BAT table provides information regarding bouquets. A bouquet is a collection of services, which may
traverse the boundary of a network.

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

- “Carouseling means that TITAN Mux carousels by itself the BAT table, Carouseling,
Mode
with a configurable section rate. Disabled
- “Disabled” means that TITAN Mux does not output any BAT.

Defines the source of the BAT table to generate at the output:
Source Multicast
- “Multicast” means that the BAT table is received from an input TS over
IP stream.

Period Integer
Period of occurrence of the TOT in the output stream. Default is 10000.

Defines the input TS over IP stream, which provides the incoming BAT tables to
Input
carousel. This section also allows restamping the BAT table ID or blocking the
tables based on their table ID.
Table 15: BAT 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 Table
a) VCT Edition
The Virtual Channel Table (VCT) contains a list of attributes for virtual channels carried in the Transport
Stream. The basic information contained in the VCT table body includes Transport Stream ID, channel
number (major and minor), short channel name, program number, access-controlled flag, location field
for extended text messages, and service type.
Figure 59: VCT Editing
Defines the SDT generation mode.

- “Carouseling” means that TITAN Mux carousels by itself the VCT
table, with a configurable period.
- “Disabled” means that TITAN Mux does not output any VCT. Carouseling,
Mode - “Pass-through” means that TITAN Mux passes through a VCT table Disabled, Pass-
coming from a live input feed, without any modification (external through
carouseling mode). Note that in such case, the TITAN Mux does not
analyze the VCT content to check that it is consistent with the current
Applies only when mode is set to “Carouseling”. Internal, PSIP

Source
Defines the source of the VCT information: Generator

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- “Internal” means that the SDT is internally built according to the
services configuration defined in section V.K.3. It also merges all the
corresponding descriptors coming from the input(s)
- “PSIP Generator” means that the SDT table is received from an
external PSIP Generator. See section N for more details.

Period Integer
Period of occurrence of the VCT in the output stream. Default is 400ms.
VCT Profile Defines the type of the VCT table to output Terrestrial, Cable
VCT descriptors can be blocked based on the service they apply to and based
on the descriptor tag. Click on the “New” button under the “Block Descriptors”
Blocked Descriptors to make the selection. Please note that the service value must be left empty to
block an outer loop descriptor.
Added Descriptors and the descriptor hexadecimal data.
Table 16: VCT Edition Parameters
b) MGT Edition
The Master Guide Table (MGT) lists version numbers, length in bytes, and PIDs for all the PSIP tables with
the exception of the STT which works independently from the other tables.
Figure 60: MGT Editing

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the MGT generation mode.
- “Carouseling” means that TITAN Mux carousels by itself the MGT
table, with a configurable period.
Carouseling,
- “Disabled” means that TITAN Mux does not output any MGT.
- “Pass-through” means that TITAN Mux passes through an MGT table
through
carouseling). Note that in such case, the TITAN Mux does not analyze
the MGT content to check that it is consistent with the other tables.

Defines the source of the MGT information:
- “Internal” means that the MGT is internally built according to the Internal, PSIP
Source
multiplex configuration and the other signalization tables. Generator
- “PSIP Generator” means that the MGT table is received from an
external PSIP Generator.

Period Integer
Period of occurrence of the MGT in the output stream. Default is 150ms.
Descriptors can be added based on the table type they apply to, the descriptor
Added Descriptors tag and the descriptor hexadecimal data
Table 17: MGT Edition Parameters
c) STT Edition
The System Time Table (STT) provides the current date and time of day information.
The TITAN Mux uses its system clock (as defined in section X.E.3) to insert information in the TDT.
Figure 61: STT Editing
Defines the STT generation mode.

- “Carouseling” means that TITAN Mux carousels by itself the STT
table, with a configurable period. Carouseling,
Mode - “Disabled” means that TITAN Mux does not output any STT. Disabled, Pass-
- “Pass-through” means that TITAN Mux passes through an STT table through
carouseling). See section N for more details.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Defines the STT generation mode.
- Carouseling means that TITAN Mux manages the carousel of the STT
table, at its own pace. The STT source can be either “Internal” (the
MGT is internally built according to the system clock configuration, as
defined in section IX.E.3) or “PSIP Generator” (the STT is injected from
a PSIP generator connection and stamped with the current time).
- “Disabled” means that TITAN Mux does not output any STT.
- “Pass-through” means that TITAN Mux passes through an STT table
carouseling).

Defines the source of the STT information:
- “Internal” means that the STT is internally built according to the Internal, PSIP
Source
system clock configuration, as defined in section IX.E.3). Generator
- “PSIP Generator” means that the STT table is received from an
external PSIP Generator and re-stamped with the current time

Period Integer
Period of occurrence of the STT in the output stream. Default is 1000ms.
Set the current offset in whole seconds between GPS and UTC time standards
GPS UTC Offset
Table 18: STT Edition Parameters
d) RRT Edition
The Rating Region Table (RRT) carries rating information for multiple geographical regions.
Figure 62: RRT Editing
Defines the RRT generation mode. Carouseling,

Mode - Carouseling means that TITAN Mux carousels by itself the RRT table, Disabled, Pass-
with a configurable period. through

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- “Disabled” means that TITAN Mux does not output any RRT.
- “Pass-through” means that TITAN Mux passes through an RRT table
carouseling).

Defines the source of the RRT information:
Internal, PSIP
Source - “Internal” means that the RRT is internally built.
Generator
- “PSIP Generator” means that the RRT table is received from an

Period Integer
Period of occurrence of the RRT in the output stream. Default is 60000ms.
Table 19: RRT Edition Parameters
e) EIT Edition
The Event Information Table (EIT) contains information (titles, start times, etc.) for events on defined
virtual channels. An event is, in most cases, a typical TV program.
TITAN mux allows for passing/filtering EIT data or using an external PSI server.
- In the case where the EIT tables are generated by an external PSIP Generator, the TITAN Mux only
allows a pure pass-through of the incoming EIT.
- In the case where the EIT tables come from an input TS, the TITAN Mux aggregates and filters the
tables to output the EIT that only pertain to the services, which 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 63: EIT Editing

- Carouseling means that TITAN Mux manages the carousel of the EIT
tables, at its own pace. The EIT source can be either “Internal” (TITAN
Mux aggregates the EIT tables coming from the appropriate inputs) or
“PSIP Generator” (the EIT are injected from a PSIP generator
connection).
- “Disabled” means that TITAN Mux does not output any EIT. Carouseling,
- “Pass-through” means that TITAN Mux passes through the EIT tables
through
carouseling). Note that in such case, the TITAN Mux will not analyze
the EIT contents to check that it is coherent with the current service
configuration.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- “Carouseling means that TITAN Mux carousels by itself the EIT tables,
with a configurable section rate.
- “Disabled” means that TITAN Mux does not output any EIT.
- “Pass-through” means that TITAN Mux passes through the EIT tables
carouseling mode). Note that in such case, the TITAN Mux will not
analyze the EIT contents to check that it is coherent with the current

- “Internal” means that TITAN Mux cherry-picks from the input(s) the
EIT associated to the services, which are re-multiplexed at the output Internal,
Source Multicast,
PSIP Generator
- “Multicast” means that TITAN mux gets EIT from a multicast input
- “PSIP Generator” means that the EIT tables are received from an

Period of occurrence of the EIT in the output stream.
Default is 1000ms when source is internal.
Default value when source is Multicast depend on EIT type :
EIT/a p/f 2000ms
Period Integer
EIT/o p/f 10000ms
EIT/a sch 0 à 1 10000ms
EIT/a sch 2 à F 30000ms
EIT/o sch 0 à 1 10000ms
EIT/o sch 2 à F 30000ms
EIT tables can be filtered, based on the services they apply to.
When mode is “Enabled”, this section will allow to select the services for which
Blocked Services
the EIT will be present in output.
EIT tables can be filtered, based on their table ID.

When mode is “Enabled”, this section will allow to select tables to block
Blocked Table ID
according to their table Id, in addition of blocking on a service basis.
Table 20: EIT Edition Parameters
f) ETT Edition
The Extended Text Table (ETT) contains Extended Text Message (ETM) streams, which are optional and are
used to provide detailed descriptions of virtual channels (channel ETM) and events (event ETM). An ETM
is a multiple string data structure, and thus, it may represent a description in several different languages
(each string corresponding to one language).

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

- Carouseling means that TITAN Mux carousels by itself the ETT tables,
with a configurable section rate.
- “Disabled” means that TITAN Mux does not output any ETT. Carouseling,
Mode - “Pass-through” means that TITAN Mux passes through the ETT tables Disabled, Pass-
coming from a pre-defined live input feed, without any modification Through
(external carouseling). Note that in such case, the TITAN Mux will not
analyze the EIT contents to check that it is coherent with the current

- “Internal” means that TITAN Mux cherry-picks from the input(s) the
ETT associated to the services, which are re-multiplexed at the output Internal, PSIP
Source
Generator
- “PSIP Generator” means that the ETT tables are received from an

Period Integer
Period of occurrence of the ETT in the output stream. Default is 60000ms.
Table 21: ETT Edition Parameters
N. PSIP Generator
TITAN Mux can interface with an external PSIP Generator and get from it all or part of the PSIP tables to
output in an ATSC terrestrial multiplex. The PSIP Generator provides the tables when the connection
initiates and then provides table updates as necessary. TITAN Mux manages the output table carousels
and continuously outputs the last version of the received tables.
The eligible PSIP tables are the PAT, PMT, VCT, MGT, EIT, ETT and RRT tables (TITAN Mux takes over the
continuous update of the SST content by using its own clock). To activate the injection of these table, it is
necessary to select the appropriate multiplex in the “Outputs” view, and go to the SI Edition menu, as
described in section M).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
To guarantee the consistency of the tables being generated, two configurations are possible: either the
external PSIP Generator provides TITAN Mux with all the tables (PAT, PMT and ATSC tables) or TITAN Mux
generates the PAT and PMT tables, while the PSIP Generator produces all the remaining ATSC tables.
To connect an external PSIP generator to TITAN Mux, please proceed as follows.
1- Open the “PSIP Management” page from the “Outputs” tab.

2- Click the “+ Add” button.
3- A new line appears in the PSIP Generator Server List
4- Fill out a PSIP generator name (logical name used to identify each generator)
5- Set the Ethernet port, on which TITAN Mux will receive the metadata from the generator
6- Set the connection port
7- Set the Generator Server IP address
8- Set the Proxy IP address, if applicable
9- Click the green tick
Figure 65: PSIP Generator configuration
O. SIMULCRYPT PSIG Generator

TITAN Mux can interface with an external Simulcrypt PSIG Generator and receive from it a part of the
MPEG PSI tables to output in a DVB/ISO multiplex. Titan Mux acts as a server and listens messages from
PSIG Generator. When the connection is initiated, PSI generator provides table updates as necessary.
TITAN Mux manages the output table carousels and continuously outputs the last version of the received
tables.
The eligible MPEG PSI tables are the PAT and PMT. To activate the injection of these table, it is necessary
to select the appropriate multiplex in the “Outputs” view, and go to the SI Edition menu, as described in
section M.
To connect an external PSIG generator to TITAN Mux, please proceed as follows.
1- Open the “PSIG Management” page from the “Outputs” tab.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
2- Click the “+ Add” button.
3- A new line appears in the Simulcrypt PSIG list
4- Fill out a PSIG generator name (logical name used to identify each generator)
5- Set the Ethernet port, on which TITAN Mux will receive the metadata from the generator
6- Set the connection port
7- Enable Channel test and set period (optional)
8- Set the PSIG IP address to filter other connection (optional)
9- Click the green tick
Name Allow to identify a PSIG generator
Connection port, on which TITAN Mux will receive the metadata from the
Port Integer
generator
Ethernet port, on which TITAN Mux will receive the metadata from the
Interface
generator
If it is enabled, Titan Mux send to PSIG generator every period (millisecond) a

Channel test period
channel_test message to check if the connection is still alive and error free.
Ip address of PSIG generator, if it is set then Titan Mux only take into account
IP address
message from this address.
Received MPEG PSI tables are displayed after

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
VII. Statmux
A. 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.
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.
B. 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.
1. Creating statmux groups

In the statmux page, you can create groups (dynamic or static) by clicking on the “New Group” on the top
right.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
The group creation dialog will present the following configuration items:
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
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
Apart from the group type, it is possible to edit these parameters any time by selecting the group and
clicking on “Edit Group” in the right column.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
C. Adding programs to a statmux group
A newly created group is not associated with an output yet. The orange circle next to the group name is a
reminder that the group is unattached. Bandwidth regulation will only be effective after attaching the
statmux group to an output. It is possible to attach an empty group to an output by selecting it. A drop
down list will propose all known outputs on the right column. Alternatively, the first service added to a
group will attach the group to its output. Once a group is attached, it is forbidden to add a service from a
different output. Changing outputs of a group requires removing all services from the group.
Drop zone to add

service to group Unattached empty
groups can be
attached to an output
in the drop down list
To add a service, drag items from the “Output programs” list to the “Drop programs to create encoder”
zone displayed for each group.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
D. Editing statmux parameters
It is possible to have access to more parameters by selecting a service in a group to display an action item
for editing the service parameters
Click to edit all

statmux service
parameters
Click on an existing service to
display action items on the
right
Min bitrate User minimum video regulated bitrate
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
Shared parameter between Titan Live & Mux to identify a regulated service, used for
communication between both product. By default Titan Live automatically configures
Channel ID 0-4294967295
the channel ID. When using older versions of Titan Live that does not support
automatic configuration, you may set the channel ID manually here.
E. Troubleshoot Channel ID conflicts

All statmuxed programs within the same pool shall have a unique channel id value. This value is given by
Titan Live but could be set manually if an older version of Titan Live is used. If two or more encoders have
the same channel id value their configuration will be rejected by Titan Mux raising the following alarm for
each misconfigured encoder :
The user will see encoders in conflict on the General Statmux page:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
In the above example two encoders are using the same channel id : 0x08. Here an hexadecimal value
indicates that the channel id is coming from Titan Live. The user can spot the bad encoder here and
configure Titan Live accordingly.
It’s possible the see the received channel id on the Titan MUX input monitoring page. If available the
channel id will be shown in the “PMT descriptors” zone.
• First click on the related service

• If available, the descriptor appears in the PMT descriptors.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
F. Using static statmux group for bitrate reservation
In addition to using a static statmux group as a fixed bandwidth regulation, it is also possible to use it to
insert stuffing to an output. In this specific usage, the static statmux group is empty but attached to a
specific output. When attached, the group will reserve bandwidth equal to its configured bitrate and the
mux output will insert stuffing to fill the reserved bandwidth. To proceed to attach an output to a static
statmux group, select the group and choose from the drop down list the appropriate output.
Select empty static

statmux group
Choose output
to attach
To detach the output from an empty static statmux group, select on the attached output again in the drop
down list to toggle the attachment to none.
G. Configuration of meta encoder in a statmux pool

In the context of service regionalization, a statmux group may contain one or more distinct services that
are part of one or more different output multiplex. In the service configuration above, Service A and
Service B belongs to two different output multiplexes while participating in the same bandwidth sharing
pool as Service C and Service D. In this mode of operation, the total bandwidth for both multiplexes are
identical. The meta encoder behaves as if it was a single service sharing the total bandwidth with Service
C and Service D. One of the member service in the meta encoder group is a designated master whose
complexity dictates the bandwidth distribution algorithm. The restriction that a statmux group must
contain services of the same output no longer apply in the case of meta encoder. In the regionalization of
services, it is inevitable that services inside a meta encoder belongs to different output multiplex.
Region 1 Multiplex
Service A
Statmux Pool
Meta encoder Service C
Service A
Service D
Service B
Region 2 Multiplex
Service C
Service B
Service D
Green Plaza, 6 rue Dewoitine Société Anonyme
ServiceauCcapital de 1.410.903,62 €
France NII: FR 09 382 231 991
Code APE Service
7112B D
Tel. +33 (0)1 69 35 89 89
www.ateme.com
The creation of a meta encoder is accessible through the statmux configuration page when a statmux
group is selected. When a statmux group is selected, an action item to create a new meta encoder is
proposed. Upon creation, a new service drop zone appears that allows the user to drop services in the
meta encoder.
1. Select statmux group to

activate action item on the right 2. Create new
meta encoder
3. Drag services into meta

encoder drop zone
Service drop zone to add services into meta encoder group
When one or more services are added into a meta encoder group, it is possible to move the service in and
out of a meta encoder or between meta encoder groups. The free movement by drag and drop is possible
provided that the following two conditions are satisfied:
1. The service’s output is the same as the destination group’s output;

2. The destination is a meta encoder, regardless of service’s output.
NB: During drag and drop, if a meta encoder becomes empty, it will be automatically removed. Empty
meta encoder can only exist in their pristine condition. Once an encoder is added, it can no longer exists
in its empty state. Removing the last encoder deletes the meta encoder. On the other hand, they can be
recreated freely as they have no identity. Their role is to serve as a container for identifying encoder
aggregation within a statmux group.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Set selected
service as master
Select service to
set as master
Moving a service out of a meta encoder to the

statmux group’s main list requires that the
service’s output is the same as the group output.
The master in a meta encoder is highlighted by a green circle. It is possible to switch master by selecting a
non-master service and clicking on “Set as master” on the right.
Services can be removed by clicking on “Delete encoder”. It is worth noting that a master in a meta encoder
cannot be deleted. This restriction will result in an impossibility to remove a singular service in a meta
encoder due to the constraint of the meta encoder to ensure the presence of a master. On the other hand,
removing the meta encoder will remove the master. The user can remove a meta encoder by first selecting
the meta encoder and clicking on “Delete meta encoder”. Deleting a non-empty meta encoder will remove
all the services in the meta encoder from the statmux pool. Such actions will first trigger a confirmation
dialog to avoid inadvertently losing configuration by accident.
Click in the meta encoder drop zone

to select meta encoder and enable
removal action item
The user can change the meta-encoder settings (name, min/max bitrate, CBR forced, quality). Thus all the
encoders belonging to the meta-encoder will automatically use these settings:

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
10- Select the meta-encoder by clicking on the last line of its description
11- Click on “Edit Meta Encoder”
Set the settings as desired in the popup and click ‘Save’ to confirm. The GUI is now updated with the new
settings for all the encoders belonging to the meta.
Note that if you remove an encoder from the meta it will fall back to the statmux pool as a standard
encoder with its own settings (those used before adding it to the meta).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
H. Seamless service switch in time-share multiplex
One additional possibility of the meta encoder feature is to allow seamless switching between services in
a time-share multiplex as illustrated by the deployment configuration below:
Statmux Pool
Meta encoder Multiplex
Switch master
Service A Time shared Service A
slot Service B
Service B
Service C Service C
Service D Service D
To fully benefit from this feature, it is necessary to configure slates in the output to complete the switch
logic (see chapter VI.H.5 Define SCTE35 triggers
In the “Trigger Sources” panel, select the input sources on which the service is waiting for SCTE35 triggers.
It can be itself or not.
On the “Trigger Actions” panel, define the different actions to be applied when the trigger is detected.
Only blocking pid actions are currently available.
Associated meta-encoder can also switch from VBR to CBR in regional mode, and from CBR to VBR in
national mode, in reaction to trigger change, if the option is set in meta-encoder options
Configure Slate on page 57).

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
I. Statmux bitrate monitoring
In the STATMUX page, once a pool is selected, the “MONITORING” feature allows to monitor the bitrate
of the statmuxed services of the pool.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Monitoring page:
By default, monitoring is not active.
Togggle on the “Activate statmux monitoring” checkbox to start monitoring.
Then, the following information will be logged and displayed:
- Min, Max, Average video bitrate for each service of the pool.
The integration period for these min, max and average bitrate values is 7 days maximum (sliding
time window)
- Bitrate history service by service:
o When a service is selected, a graphic representation of its video bitrate is represented
o Up to 7 days of history are logged. Graphic is displayed on a day per day basis: the user
can select to display the bitrate graph for the last 24h, day-1, day-2, …. up to day-6
o The user can zoom into the graphic. The sampling frequency is 2 seconds (1 bitrate value
every 2 seconds)

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
VIII. 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 66: DVB-Simulcrypt overview
The TITAN Mux achieves scrambling through interaction with an ECM (Entitlement Control Message)
Generator 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 to:
- 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 67: 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.
Figure 68: 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
Pause all
- All scrambled services go to clear
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”.
When scrambling is defined per service (see Creating Scrambling Groups (SCG)),
“Whole service” makes the Mux to scramble all PID of the services and
“Audio/video PIDs only” makes the Mux to scramble only audio/video PIDs Whole service
Service scrambling
according to their stream_type. Audio/Video only
This parameter has no effect when scrambling is defined per PID
In “Automatic” mode, repetition rate is given by ECMG.

ECM repetition rate It’s possible to force value by selecting in the list (from 100ms to 500ms by step 100ms to 500ms
of 100ms)
This button allows to purge all provisioning (current and pending events) done by
EIS purge EIS. A pop-up of confirmation will appear to confirm or cancel operation
N/A
provisioning
After this action, communication with EIS will be disconnected
Enable
communication with If sets, the EIS will be able to connect to the Mux and send 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 of 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
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 22: 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 69: 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 in the
N/A String
web GUI, it is not related to any MPEG/DVB/ATSC Parameter.
CA System ID Corresponds to the CA_system_id field of the ETSI 103197 and ETR 162 douments 16 bits integer
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 parameters

Channel ID 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 toggled, then
Auto increment Integer
the Mux will increment the Channel ID value set in the GUI, and try to establish a
channel with this new value.
DVB-CSA
Channel Algorithm Defines the encryption algorithm
ATIS IDSA
Channel_test Defines the emission period of channel_test messages from the Mux to ECMG
Integer
messages period (when channel test messages are enabled)
When “disabled”, the Mux will use the delay_start value provided by ECMG When
User delay start “enabled”, the Mux will use the specified delay_start value for all newly
instantiated scrambling operations.
When “disabled”, the Mux will use the transition_delay_start value provided by
User transition delay
ECMG.
start
When “enabled”, the Mux will use the specified transition_delay_start value for all
newly instantiated scrambling operations.
Protocol version Defines the protocol version of the exchanged messages between Mux and ECMG Integer
This parameter allows to control the position of CA descriptors in the PMT. When
set to default, if scrambling is defined per PID (see Creating Scrambling Groups
(SCG)) then the position of CA descriptors is the inner loop (PID level), if scrambling
default
is defined per Service then the position of CA descriptors is the outer loop (service
CA descriptors inner
level).
position in PMT outer
When set to inner, CA descriptors position is the inner loop (PID level)
none
When set to outer, CA descriptors position is the outer loop (Service level)
When set to none, CA descriptors is not inserted
Available only for Nagravision and Viacces CAS

For Nagravision CAS it defines the way access criteria is sent to the ECMG through
Parameter
Ecmg mode the control word provision message.
Reference
For Viaccess CAS, if it is set as Parameter then the content of ECM criteria is parsed
to fill the additional data that are added to CA descriptor in the PMT

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Add Mediaguard CA Available only for Nagravision CAS.
descriptors When enabled, Mediaguard CA descriptors are added in the PMT.
Mediaguard CA
Available only if Mediaguard CA descriptors insertion is enabled
System Id 256..511
Control the value of Mediaguard CA System ID set in Mediaguard CA descriptors.
(decimal)
Available only if Mediaguard CA descriptors insertion is enabled

This parameter allows to control the position of Mediaguard CA descriptors in the
PMT.
When set to default, if scrambling is defined per PID (see Creating Scrambling Default
Mediaguard
Groups (SCG)) then the position of CA descriptors is the inner loop (PID level), if Inner
CA descriptors
scrambling is defined per Service then the position of CA descriptors is the outer Outer
position in PMT
loop (service level). none
When set to inner, CA descriptors position is the inner loop (PID level)
When set to outer, CA descriptors position is the outer loop (Service level)
When set to none, CA descriptors is not inserted
Use only one Available only if Mediaguard CA descriptors insertion is enabled

Mediaguard If enabled, only one Mediaguard CA descriptor is added for all ECM other else one
CA descriptor Mediaguard CA descriptor for each ECM
Use conformed
Use 48bit entropy reduction control word instead of 64bit
control word
Send conformed Available only if “Use conformed control word”.

control word to ECMG If enabled, the control word sent to ECMG use the 48bit entropy reduction.
SPF Bit When enabled, bit 54 of control word is set to 0
Data to be inserted in the CA_Descriptors of the PMT.

Private Data Corresponds to the private_data_byte of the CA Descriptor, as described in ITU-T
H.222.
Available only if MediaGuard CA descriptor insertion is enabled

Mediaguard Data to be inserted in the Mediaguard CA descriptor of the PMT.
Private Data Corresponds to the private_data_byte of the CA Descriptor, as described in ITU-T
H.222.
Declare 1 or more ECMG servers. If many ECMG servers are configured, then it
ECMG servers 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 23: ECM Parameters

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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). The 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 70: 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 web
N/A String
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 CA_subsystem_id). The
ECM ID Integer
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 have
ECMG been previously defined
Access Criteria CA system specific information needed by the ECMG. String
Data to be inserted in the CA_Descriptors of the PMT.

Corresponds to the private_data_byte of the CA Descriptor, as described in ITU-T H.222.
Private Data This Private Data overwrite Private Data defined in ECMG configuration and possibly String
overwrites also the private data that could be deduced from the Access Criteria if this
one is defined by parameter as per ECMG configuration.
Available only for Nagravision ECMG

Data to be inserted in the Mediaguard CA descriptor of the PMT.
Mediaguard Corresponds to the private_data_byte of the CA Descriptor, as described in ITU-T H.222.
String
Private Data This Mediaguard Private Data overwrite Mediaguard Private Data defined in ECMG
configuration and overwrites also the private data that could be deduced from the
Access Criteria if this one is defined by parameter as per ECMG configuration.
PID PID Value on which the ECM stream will be transmitted Integer
Table 24: ECM Parameters
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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 71: 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 25: 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 72: EMM/PD Stream declaration
Defines the EMM/PD stream name. This name is only used internally as an identifier
N/A String
Must correspond to the data_id in ETSI 101397 recommendation.

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 server
EMM/PDG Server
must have been previously defined (refer to VIII.E Declaring an EMM/PD 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 26: 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.
Figure 73: Scrambling Group parameters
To create a new SCG, click on “New SCG” button. The SCG ID and Crypto Period must be filled:
Figure 74: SCG creation
The partial scrambling offset is used to configure partial scrambling with DVB CSA2 and ATIS-ISDA. By
default, partial scrambling is deactivated (i.e. offset to first scrambled packet is 0). This feature is activated
by setting the partial scrambling offset to a value in the range of 2 through 5. The offset is measured from
the packet unit start indicator (PUSI) in a TS packet. Setting a value of 3 will start scrambling the third
packet from the PUSI packet.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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).
o If a service is dragged and dropped: scrambling is defined “per service”. According to the
configuration of SCS screen (see SCS Configuration), all the components are scrambled, or
only audio/video ones.
o If components (pids) are dragged and dropped: scrambling is defined “per pid”. According
the configuration of SCS screen, CA descriptors position may be set to inner or outer loop.
- 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.
Note that it is not possible to put a slave service in a scrambling group. This one will inherit scrambling
properties of the master service.
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).
Figure 75: EMM insertion

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
I. Pause / Resume scrambling
There are several ways to pause the scrambling processing less or more finely.
1. Pause All Scrambling processing
Figure 76: Pause/Resume all scrambling
This will suspend scrambling for all scrambled services on the Mux
- All scrambled services go to clear
2. Resume all scrambling

This will resume all suspended scrambling.
NB: scrambling will not resume for services that have been deprovisioning by EIS while in “pause”.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
3. Pause Scrambling by output
Figure 77: Pause/Resume scrambling by output
STOP SCRAMBLING will suspend scrambling for all scrambled services belonging to the selected output
- All scrambled services belonging to the selected output go to clear
RESUME SCRAMBLING will resume scrambling for all suspended scrambled services belonging to the
selected output
-
NB: While the scrambling was in “pause” for the selected output, if some services were deprovisioned
manually or by EIS or if the SCG to which some services belong were themselves set in “pause”, then the
scrambling will not resume for these services.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
4. Pause Scrambling by service
Figure 78: Pause/Resume scrambling by service
STOP SCRAMBLING will suspend scrambling for selected service inside the SCG
- Service go to clear
RESUME SCRAMBLING will resume scrambling for selected service inside the SCG
- Service go back to scrambled

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
IX. 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
X. 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 79: 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 27: 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 80: 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 28: 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 29: 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 81: 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.5.9 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
License missing could not be found.1.5.9
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.
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.

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 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.
EIT missing Will be raised when an external EIT has been defined but could not be found.
VCT missing Will be raised when an external VCT has been defined but could not be found.
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
Will be raised when the round trip time for statmuxed encoder communication exceeds 50ms.
High RTT

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 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
ECMG communication Communication with ECMG server has been lost.

error
Alarm reported by the ECMG module.

ECMG alarm

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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 82: Alarm list
3. Additional alarms from hardware sensors

In addition to the alarms described above you will here alarms related to hardware sensors. Those alarms
will be available for configuration here once the have been enabled in the dedicated “Hardware
monitoring” page. You will find more details in the section G “Hardware monitoring”.
Note: you can set the severity of those alarm but no traps will be sent even if it’s checked.
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 83: 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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.
3. Hardware monitoring
All sensors values are displayed here. More details about sensors are available in section G “Hardware
monitoring”.
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.
Figure 84: 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
Figure 85: 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,
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.
Figure 86: 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 87: 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.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
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 30: 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
F. Logging Configuration
This page offers the possibility to configure a connection with a remote client which will be forwarded
syslog messages.
Logging
Configuration
configuration
Figure 88: 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]

Table 31: Logging configuration parameters
Once parameters have been set, click on the ‘Apply Configuration’ button validates the new logging
configuration.
G. Hardware monitoring
This page offers the possibility configure hardware sensors used to monitor and to generate the following
items:
- ‘Log FS’: Filesystem usage for the Log partition. When enabled an alarm is raised if the filesystem
usage of the logging partition is above 70% of partition space. The alarm is cleared when the usage
goes below 63%. Both thresholds are configurable here.

France NII: FR 09 382 231 991
Code APE 7112B
Tel. +33 (0)1 69 35 89 89
www.ateme.com
- ‘Root FS’: Filesystem usage for the Root partition. When enabled an alarm is raised if the filesystem
usage of the root partition is above 70% of partition space. The alarm is clear when the usage goes
below 63%. Both thresholds are configurable here.
- FanXX : internal server fans speed. The number of fans depends on the server hardware. When
enabled an alarm is raised when the speed is lower than 10 RPM. The alarm is cleared when the
speed goes above 50 RPM.
- PSx: power supply status. When enabled an alarm is raised if the power supply is not detected.
The alarm is cleared when the power supply is back.
- CPUx Temp: temperature of CPUs. When enabled an alarm is raised if the CPU temperature
exceeds 87°C. It’s cleared when the CPU temperature goes below 82°C. Both thresholds are
configurable here.
Figure 89 - hardware monitoring
When a sensor is enabled alarms are available for configuration on the “Alarm Management” page.

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

TitanMUX-UM-v1 5 9

Uploaded by

Copyright:

Available Formats

You might also like

TitanMUX-UM-v1 5 9

Uploaded by

Document Information

Original Description:

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

TitanMUX-UM-v1 5 9

Uploaded by

Copyright:

Available Formats

I.

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 €

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

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

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_5_5_1-0-official-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.

It can be computed as follows: ShmSize = 8m * NbInputs + 70m * NbOutputs

Docker run command line would then be:

“docker run --privileged -d -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro --shm-size=131m --net=host titanmux”

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