Dialog R2.4.1 ConfigurationUserGuide v1.3

Configuration User Guide
Newtec Dialog®
R2.4.1
Revision 1.3
September 1st, 2021
© 2021 ST Engineering iDirect (Europe) CY NV and/or its affiliates. All rights reserved.
Reproduction in whole or in part without permission is prohibited. Information contained herein is
subject to change without notice. The specifications and information regarding the products in this
document are subject to change without notice. While every effort has been made to ensure the
accuracy of the statements, information and recommendations in this document, they are provided
without warranty of any kind, express, or implied. Users must take full responsibility for their
application of any products. Trademarks, brand names and products mentioned in this document are
the property of their respective owners. All such references are used strictly in an editorial fashion
with no intent to convey any affiliation with the name or the product's rightful owner.
ST Engineering iDirect is a global leader in satellite communications (satcom) providing technology

and solutions that enable its customers to expand their business, differentiate their services and
optimize their satcom networks. Through the merger with Newtec, a recognized industry pioneer, the
combined business unites over 35 years of innovation focused on solving satellite’s most critical
economic and technology challenges, and expands a shared commitment to shaping the future of
how the world connects. The product portfolio, branded under the names iDirect and Newtec,
represents the highest standards in performance, efficiency and reliability, making it possible for its
customers to deliver the best satcom connectivity experience anywhere in the world. ST
Engineering iDirect is the world’s largest TDMA enterprise VSAT manufacturer and is the leader in
key industries including broadcast, mobility and military/government.
Company Website: www.idirect.net | Main Phone: +32 3 780 6500

Support Contact Information: Email: customersupport@idirect.net | Website:
www.idirect.net/support-and-training
Table of Contents
Table of Contents
1 About This Guide ............................................................................................ 1

1.1 Revision History ...................................................................................................................................... 1
1.2 Cautions and Symbols ............................................................................................................................ 1
2 What is Newtec Dialog® ................................................................................. 3
3 How to Access the NMS GUI .......................................................................... 8
4 Attributes ....................................................................................................... 10
5 Manage General Satellite Resources .......................................................... 11

5.1 How to Open the Satellite Resources Web Interface ............................................................................ 12
5.2 How to Create a Beam .......................................................................................................................... 12
5.3 How to Create a Satellite Network ......................................................................................................... 19
5.4 Manage GXT Files ................................................................................................................................ 23
5.4.1 How to Upload a GXT File ............................................................................................................... 23
6 Manage Forward Link Resources ................................................................ 25

6.1 Background Information ....................................................................................................................... 25
6.1.1 Adaptive Coding Modulation ........................................................................................................... 26
6.1.2 Time Slicing ..................................................................................................................................... 29
6.1.3 Encapsulation ................................................................................................................................. 31
6.1.4 Forward QoS Shaping ..................................................................................................................... 34
6.1.5 Shared Transport Stream ............................................................................................................... 37
6.1.6 Forward Link Encryption ................................................................................................................. 37
6.1.7 Frequencies .................................................................................................................................... 41
6.2 Setup of Forward Link Resources ......................................................................................................... 41
6.3 How to Open the Forward Resources Web Interface ........................................................................... 42
6.4 How to Create a Transponder for the Forward Link .............................................................................. 44
6.5 How to Create a Forward Carrier ........................................................................................................... 45
6.6 How to Create a Forward Link ............................................................................................................... 49
6.7 How to Save the Modulator Configuration ............................................................................................. 54
6.8 How to Open the Forward QoS Plan Interface ...................................................................................... 56
6.9 How to Edit the Root Pool ..................................................................................................................... 60
6.10 How to Create a Dedicated Transport Based Forward Pool ............................................................... 61
6.11 How to Create a Shared Transport Based Forward Pool .................................................................... 64
Configuration User Guide v1.3 3/361

Newtec Dialog R2.4.1
Table of Contents
6.12 How to Create a Dedicated Class Based Forward Pool ...................................................................... 65

6.13 How to Create a Shared Class Based Forward Pool .......................................................................... 68
6.14 How to Configure a Key Encryption Key ............................................................................................. 70
7 Manage Return Link Resources .................................................................. 73

7.1 Background Information ....................................................................................................................... 73
7.1.1 4CPM MF-TDMA ............................................................................................................................. 75
7.1.2 DVB-S2 and S2 Extensions ............................................................................................................ 79
7.1.3 High Resolution Coding™ ............................................................................................................... 80
7.1.3.1 HRC SCPC .................................................................................................................................. 81
7.1.3.2 HRC Mx-DMA .............................................................................................................................. 81
7.1.3.3 Capacity Troubleshooting ............................................................................................................ 82
7.1.4 MRC NxtGen Mx-DMA ................................................................................................................... 82
7.1.5 Adaptive Coding Modulation ........................................................................................................... 84
7.1.6 Return QoS Shaping ....................................................................................................................... 84
7.1.7 Frequencies .................................................................................................................................... 88
7.2 Setup of Return Link Resources ........................................................................................................... 89
7.3 How to Open the Return Resources Web Interface .............................................................................. 90
7.4 How to Create a Transponder for the Return Link ................................................................................. 92
7.5 How to Create a Return Link ................................................................................................................. 93
7.6 How to Open the Return Link Frequency Plan ...................................................................................... 95
7.7 How to Create an S2 Return Capacity Group ..................................................................................... 100
7.8 How to Create an HRC Return Capacity Group .................................................................................. 101
7.8.1 Create a Frequency Slot ............................................................................................................... 102
7.8.2 Create an HRC SCPC Return Capacity Group ............................................................................. 103
7.8.3 Create an HRC Mx-DMA Return Capacity Group ......................................................................... 105
7.9 How to Create an MRC Return Capacity Group ................................................................................. 110
7.10 How to Create 4CPM Resources ...................................................................................................... 114
7.10.1 How to Add a 4CPM Configuration .............................................................................................. 115
7.10.2 How to Add a CSC Carrier ........................................................................................................... 115
7.10.3 How to Add a Return Capacity Group ......................................................................................... 117
7.10.4 How to Add a Return Carrier Pool ............................................................................................... 118
7.10.5 How to Add a TRF Carrier ........................................................................................................... 119
7.11 How to Open the Return QoS Plan Interface ..................................................................................... 121
7.12 How to Edit the Root Pool ................................................................................................................. 125
7.13 How to Create a Dedicated Transport Based Return Pool ................................................................ 126
7.14 How to Create a Shared Transport Based Return Pool .................................................................... 128
7.15 How to Create a Dedicated Class Based Return Pool ...................................................................... 130
7.16 How to Create a Shared Class Based Return Pool ........................................................................... 132
7.17 How to Enable HRC Mx-DMA Universal Logon ................................................................................ 135

Table of Contents
7.17.1 Activate HRC Ulogon .................................................................................................................. 136

7.17.2 Configure Sufficient Maximum Logon Bandwidth ....................................................................... 137
7.17.3 Make Sure the Demodulator Capability is Available ................................................................... 138
7.17.4 Make Sure Sufficient HRC Demodulators are Available ............................................................. 139
7.18 How to Migrate Carrier ...................................................................................................................... 139
8 VNO and User Management ....................................................................... 143

8.1 How to Open the VNO and User Management Web Interface ........................................................... 143
8.2 How to Create a VNO .......................................................................................................................... 144
8.3 How to Create a New User .................................................................................................................. 148
9 Manage Network Resources ...................................................................... 151

9.1 Background Information ..................................................................................................................... 151
9.1.1 Layer 3 Network Resources .......................................................................................................... 151
9.1.1.1 Dedicated Subnet ...................................................................................................................... 153
9.1.1.2 Shared Subnet ........................................................................................................................... 153
9.1.1.3 Uplink Network Connectivity ...................................................................................................... 154
9.1.1.4 DNS ........................................................................................................................................... 154
9.1.1.5 Routing ...................................................................................................................................... 155
9.1.1.5.1 Static .................................................................................................................................... 155
9.1.1.5.2 OSPF ................................................................................................................................... 155
9.1.1.5.3 BGP ..................................................................................................................................... 156
9.1.1.6 Service Labels ........................................................................................................................... 158
9.1.1.6.1 Use of Service Labels for Dedicated Subnets ..................................................................... 158
9.1.1.6.2 Use of Service Labels for Shared Subnets .......................................................................... 159
9.1.1.6.3 Use of Service Label in Classification Profiles ..................................................................... 161
9.1.2 Layer 2 Network Resources .......................................................................................................... 162
9.1.3 Multicast Network Resources ....................................................................................................... 163
9.2 How to Open the Network Resources Web Interface ......................................................................... 164
9.3 How to Create Layer 3 Network Resources ........................................................................................ 164
9.3.1 How to Create a Hub Termination Point ........................................................................................ 165
9.3.2 How to Create a Dedicated Subnet ............................................................................................... 167
9.3.3 How to Create a Shared Subnet ................................................................................................... 173
9.3.4 How to Create IPv4 Pools ............................................................................................................. 180
9.3.5 How to Create IPv6 Pools ............................................................................................................. 183
9.4 How to Create Layer 2 Network Resources ........................................................................................ 185
9.4.1 How to Create a Hub Termination Point ........................................................................................ 186
9.4.2 How to Create a Layer 2 VC .......................................................................................................... 187
10 Manage Classification Profiles ................................................................ 188

Table of Contents
10.1 Background Information ................................................................................................................... 188

10.1.1 Classification ............................................................................................................................... 188
10.1.2 Inherit QoS Classification ............................................................................................................ 189
10.1.3 Marking ....................................................................................................................................... 189
10.2 How to Open the Classification Profiles Web Interface ..................................................................... 191
10.3 How to Create a Classification Profile ............................................................................................... 192
11 Manage Service Profiles ........................................................................... 198

11.1.1 Service Profile Types .................................................................................................................. 198
11.1.2 Queuing ...................................................................................................................................... 199
11.1.3 Allocation Type ........................................................................................................................... 200
11.1.4 ACM in HRC Mx-DMA and MRC NxtGen Mx-DMA .................................................................... 202
11.2 How to Open the Service Profiles Web Interface .............................................................................. 203
11.3 How to Create a Transport-based Service Profile ............................................................................. 204
11.4 How to Create a Class-based Service Profile ................................................................................... 209
12 Manage Attachment Profiles .................................................................... 213

12.1 How to Open the Attachment Profiles Web Interface ........................................................................ 213
12.2 How to Create an Attachment Profile ................................................................................................ 215
12.3 Batch Actions .................................................................................................................................... 219
13 Manage Firewall Profiles .......................................................................... 221

13.1 How to Open the Firewall Profiles Web Interface .............................................................................. 221
13.2 How to Create a Firewall Profile ........................................................................................................ 222
14 Manage BGP Profiles ................................................................................ 225

14.1 Introduction ....................................................................................................................................... 225
14.2 How to Open the BGP Profiles Web Interface ................................................................................... 225
14.3 How to Create a BGP Profile ............................................................................................................. 226
15 Manage Remote Configuration Profile .................................................... 229

15.1 How to Open the Remote Configuration Profiles Web Interface ....................................................... 229
15.2 How to Create a Remote Configuration Profile ................................................................................. 230
16 Manage Terminal Provisioning ................................................................ 232

16.1 Whitelisted Terminals ........................................................................................................................ 232
16.2 How to Create a Terminal ................................................................................................................. 234
16.2.1 How to Configure Modem Settings .............................................................................................. 235
16.2.2 How to Configure Service Settings .............................................................................................. 240

Table of Contents
16.2.3 How to Configure Mobility Settings ............................................................................................. 243

16.2.4 How to Configure Layer 3 Settings .............................................................................................. 246
16.2.4.1 Layer 3 Networks ..................................................................................................................... 247
16.2.4.1.1 Dedicated Subnet .............................................................................................................. 248
16.2.4.1.2 Shared Subnet ................................................................................................................... 254
16.2.4.2 Return Multicast ....................................................................................................................... 257
16.2.4.3 Route Advertisement ............................................................................................................... 257
16.2.5 How to Configure Layer 2 Settings .............................................................................................. 258
16.2.6 How to Configure Monitoring Settings ......................................................................................... 260
16.2.7 [optional] How to Configure Wi-Fi Settings .................................................................................. 262
16.3 Batch Actions .................................................................................................................................... 263
17 Manage Auto Attachment Prototype ....................................................... 266

17.1 How to Open the Auto Attachment Prototypes Web Interface .......................................................... 266
17.2 How to Create an Auto Attachment Prototype .................................................................................. 266
18 Manage Inventory ...................................................................................... 269

18.1 Gateway Provisioning ....................................................................................................................... 269
18.2 Hub Module Provisioning .................................................................................................................. 269
19 Updating Terminal Software ..................................................................... 271

19.1 How to Open the Software Multicast Web Interface ......................................................................... 271
19.2 How to Create a Software Multicast .................................................................................................. 273
20 Terminal Line Up ....................................................................................... 276

20.2 Procedure ......................................................................................................................................... 279
21 Return Link Calibration ............................................................................. 282

21.1 Measuring and Calculating the Values ............................................................................................. 283
21.2 Setting the Values ............................................................................................................................. 283
22 Equalink® ................................................................................................... 286

22.1 Introduction ....................................................................................................................................... 286
22.2 Procedure ......................................................................................................................................... 289
22.2.1 M6100 ......................................................................................................................................... 289
22.2.1.1 Satellite Link Analyzer Procedure ............................................................................................ 290
22.2.1.2 Automated Non-Linear Calibration Procedure on MDM6x00 .................................................. 292
22.2.1.3 Enable Non-Linear Predistortion on M6100 of Dialog Hub Module ........................................ 297
22.2.2 MCM7500 ................................................................................................................................... 302

Table of Contents
22.2.2.1 Calibration Setup ..................................................................................................................... 302

22.2.2.2 Log Initial Status ...................................................................................................................... 303
22.2.2.3 Calibration Configuration ......................................................................................................... 304
22.2.2.4 Measure Reference ALC Level ............................................................................................... 309
22.2.2.5 Optimize Drive Level ................................................................................................................ 309
22.2.2.6 Enable MCPRED ..................................................................................................................... 314
22.2.2.7 Optimize Settings ..................................................................................................................... 315
22.2.2.8 Restore Operational State ....................................................................................................... 318
22.2.2.9 Enable ALC ............................................................................................................................. 320
22.2.2.10 Remove Calibration Setup ..................................................................................................... 320
22.2.2.11 Expected MCPRED Improvement ......................................................................................... 320
22.2.2.12 How to Open the Web Interface ............................................................................................. 321
22.2.2.13 Where to Find the Measurements ......................................................................................... 324
22.2.2.14 List of MODCODs .................................................................................................................. 325
23 Automated Uplink Power Control ............................................................ 328

23.1 About AUPC ..................................................................................................................................... 328
23.2 Configuring AUPC ............................................................................................................................ 328
23.2.1 Range Setting ............................................................................................................................. 328
23.2.2 Output Power for 1 dB Compression Setting .............................................................................. 329
23.2.2.1 BUC ......................................................................................................................................... 329
23.2.2.2 iLB2220 MUC .......................................................................................................................... 331
23.2.3 Power Control Mode ................................................................................................................... 332
24 Certification ............................................................................................... 333

24.1 Background ....................................................................................................................................... 333
24.2 Procedure ......................................................................................................................................... 335
25 Multicast ..................................................................................................... 337

25.1 How to Create Multicast VLANs ........................................................................................................ 337
25.2 How to Create Hub Multicast ............................................................................................................. 340
25.3 How to Create Terminal Multicast ..................................................................................................... 345
26 GTP Optimization for Mobile Backhauling .............................................. 348

26.1 Create Mobile Backhaul Network ..................................................................................................... 348
26.2 Create Service Profile ....................................................................................................................... 349
26.3 Define QoS Plan ............................................................................................................................... 351
26.4 Create Classification Profile .............................................................................................................. 353
26.5 Provision Terminals ........................................................................................................................... 355

Table of Contents
27 Appendix .................................................................................................... 356
28 Acronyms ................................................................................................... 358

About This Guide
1 About This Guide

The Newtec Dialog Configuration User Guide provides detailed information about configuring the
Newtec Dialog® resources using the integrated graphical user interface.
The manual has been written from the perspective of the HNO user with Administrator
role. To know the access rights of the VNO user, refer to VNO User Permissions.
Resources can also be configured using the REST API. For more information about
using REST API, browse to http://<CMS-IP>/cms/doc/api.
A caution message indicates a hazardous situation that, if not avoided, may result in
minor or moderate injury. It may also refer to a procedure or practice that, if not
correctly followed, could result in equipment damage or destruction.
1.1 Revision History
Version Date Reason of new version
1.0 December, 2020 Initial version of this release.
1.1 May, 2021 MRC ACM Reactive behavior based on baseband frame
drops added.
Bugs fixed.
1.2 June 2021 MRC ACM Reactive behavior based on baseband frame
drops clarification added.
1.3 September 2021 Clarification on Candidate Forward Carrier feature added.

Clarification on multicast contribution for NPCI Dialog
systems.
1.2 Cautions and Symbols

The following symbols appear in this guide:
A caution message indicates a hazardous situation that, if not avoided, may result in
minor or moderate injury. It may also refer to a procedure or practice that, if not
correctly followed, could result in equipment damage or destruction.
A hint message indicates information for the proper operation of your equipment,
including helpful hints, shortcuts or important reminders.

About This Guide
A reference message is used to direct to a location in a document with related document

or a web-link.

What is Newtec Dialog®
2 What is Newtec Dialog®

Dialog® is a single-service and multi-service VSAT platform that allows operators and service
providers to build and adapt their infrastructure and satellite networking according to business or
missions at hand. Based on the cornerstones of flexibility, scalability and efficiency, the Dialog
platform gives the operator the power to offer a variety of services on a single platform.
Key characteristics are:
• Flexible service offering
• Flexible business models
• Multi-service operation
• Anywhere, anytime service
• Streamlined operations
The Dialog platform fully manages all aspects of a service: bandwidth usage, real-time
requirements, network characteristics and traffic classification. The platform offers these services
with carrier grade reliability through full redundancy of the platform components.
The Dialog platform supports multiple traffic types, such as the following:
• Video and audio
• Data
• Voice
• Data casting

The core of the Dialog platform is the Hub, which is located at a physical gateway site. A Dialog
platform can consist of one or more hubs, located at one or more gateways.
A hub consists of one or more Hub Modules. A hub module contains all hardware and software
required for aggregating and processing traffic of one or more satellite networks.
Following types of hub modules exist:
• The 1IF hub module serves one satellite network and is suited for small networks. It provides less
scalability and flexibility than the next hub modules. It is also referred to as HUB6501.
• The 4IF hub module serves up to four satellite networks and is suited for medium to large
networks. It provides flexibility and scalability. It is also referred to as HUB6504.
• The XIF hub module is suited for very large networks and provides full flexibility and scalability. It
can serve up to 18 satellite networks. It is the combination of one or two baseband hub modules
and one processing hub module. The combination of HUB7208 HUB7318 is referred to as an XIF
hub module.
– The XIF baseband hub module holds the RF devices. It is also referred to as HUB7208.
– The XIF processing hub module holds the processing servers. It is also referred to as
HUB7318. HUB7318 is deployed on the Newtec Private Cloud Infrastructure or NPCI.
Equipment redundancy is supported for all devices in the hub module. A hub module may be
implemented fully redundant, non-redundant or partially redundant.
The Terminal is the equipment located at the end-user’s site. It consists of the outdoor unit
(antenna, LNB and BUC) and the indoor unit, i.e. the modem.
Dialog R2.4.1 supports all modem types.

Do note that new features as described in the release notes of Dialog R2.4.1 and higher
are no longer supported on MDM2200, MDM2500 and MDM3x00.

A hub module is connected to an IP backbone at one side and to an RF interface at the other side,
establishing the Satellite Network.
A satellite network is associated with forward link capacity from one physical or virtual (in case of
DVB-S2X Annex M) forward carrier and with the corresponding return link capacity. The forward link
is based on one of the following technologies:
• DVB-S2
• DVB-S2X
• DVB-S2X Annex M.
The return link supports multiple return link technologies:
• 4CPM MF-TDMA
• DVB-S2 and S2-Extensions SCPC
• HRC SCPC and Mx-DMA
• MRC NxtGen Mx-DMA

Network Resources are configured on top of the physical satellite networks and are isolated from
each other using VLAN identifiers. Dialog provides end-to-end network connectivity for three types
of networks:
• Layer 3
• Layer 2
• Multicast
Layer 3 network resources consist of one or more virtual networks. A layer 3 virtual network is an
isolated IPv4 or IPv6 network. Devices within the same virtual network can directly communicate
with each other. A virtual network can independently use its own addressing scheme and the same
addressing schemes can be reused in different virtual networks.
Layer 2 network resources consist of one or more point-to-point virtual connections. A layer 2
point-to-point virtual connection can be considered as a virtual Ethernet pipe, which establishes
isolated communication between two devices.
A multicast network connects an uplink network on the hub side with one or more LAN networks on
the modem side. This consists of a single multicast routing instance providing unidirectional routing
of multicast IP traffic from the uplink network to the modem LAN networks. The MC network can
therefore be compared to a multicast router.

The Dialog platform is managed through a single Network Management System or NMS. The
NMS can be embedded in a hub module or it can be a standalone hub module, which is deployed on
a Private Cloud Infrastructure or NPCI. The standalone NMS on NPCI is referred to as HUB7318.
The NMS provides a unified management interface to monitor, manage and control the Dialog
platform. It serves as a single point of access and embeds the following configuration and
management interfaces:
• Satellite resources
• Network resources
• Service and classification profile management
• Terminal provisioning
• Fault (alarms) and performance (metrics) management

How to Access the NMS GUI
3 How to Access the NMS GUI

In this manual, you will use the Network Management System or NMS to configure the resources.
Alternatively, you can use REST API calls.
To access the NMS, execute the following steps:
1. Open the Internet Explorer browser and browse to http://CMS_VIP.
CMS_VIP is the virtual IP address of your NMS system. This IP address is set
during the installation of your hub module. For more information, refer to the
corresponding Newtec Dialog Hub Installation Guide.
Use Internet Explorer 10 or higher.

It is advised to add the URL as trusted site in the Security settings of Internet
Explorer.
2. Select the user at the left hand side and enter the password.
The NMS login credentials are set during the installation of the hub module. For
more information, refer to the corresponding Newtec Dialog Hub Installation Guide.
3. Click Log on. The NMS client application connects to the specified NMS server and the home
page of the NMS User Interface opens.
Select the Save my user name and password check box to save the logon
credentials. When selected, you will automatically log on the next time the Newtec
Dialog NMS client is started.
4. The NMS web interface has the following sections:

1. Header bar

How to Access the NMS GUI
2. Navigation pane
3. Card pane
4. Card navigation pane
5. Alarm console
5. To log off, click the user name at the right in the header bar and select Log off.

Attributes
4 Attributes
Some of the provisioning interfaces have an Attributes button in the upper right of the window.
Attributes allow you to set key value pairs to system resources. You can then query resources based
on these attributes.
For example, you can use the attributes of a terminal to specify the country in which a terminal is
located. The key is the country, the value is for example Belgium.
To set a key value pair, execute the following steps:
1. Click Attributes and then click + Add Attribute.
2. Enter the Key and Value.
3. Click to save the settings or to discard the attribute.

4. Click Confirm to validate or Cancel to discard the attribute.
Click in the Actions column to edit the attribute.
Click in the Actions column to delete the attribute.

Manage General Satellite Resources
5 Manage General Satellite Resources

A satellite network is the combination of:
• Specific forward and return link resources on which terminals can be provisioned.
• A Hub Processing Segment (HPS), which handles the data processing, such as encapsulation and
decapsulation, acceleration, demarcation etc.
All required hardware of a satellite network is enclosed in a hub module. During the installation of the
hub module, the Newtec Dialog system is informed about one or more satellite networks by defining
the modulators, demodulators and number of virtual machines or virtual network functions.
For more details about setting up the hub module hardware and server and device
configuration, refer to the specific hub module Newtec Dialog Hub Installation Guide.
When the physical satellite networks have been configured, they need to be linked to actual satellite
resources. The satellite resources correspond with a beam, which covers a geographical area in
which terminals are serviced. The intersection of a satellite beam with the earth's surface is referred
to as the (beam's) footprint.
Assuming that the hardware of the satellite network is installed and configured, following sequence
of steps should be executed:
1. Define a Beam.
2. Provision a logical satellite network and link it with the beam and the physical satellite network.

5.1 How to Open the Satellite Resources Web Interface

To open the web interface of the Satellite Resources, execute the following steps:
1. Access the NMS GUI. For more information, refer to How to Access the NMS GUI on page 8.
2. Click Newtec Dialog at the top of the surveyor tree.
3. Click Satellite Resources in the surveyor tree or in the visual overview.
Several Satellite Resource provisioning interfaces appear.
5.2 How to Create a Beam

To create a beam, execute the following steps:
1. Open the Satellite Resources web interface as described in
How to Open the Satellite Resources Web Interface on page 12.
2. Click Beam Provisioning in the surveyor tree or in the visual overview.

3. Enter the login credentials and wait for the user interface to open.
4. Click + Create New Beam.
Alternatively, you can click the copy icon in the Actions column of the overview to create
a new beam based on the settings of an existing one.
A window appears where you can configure the beam and the beam neighbors.
5. Configure the beam.
Set the parameters:

– Identifier: The identifier is the combination of the HNO domain name and an arbitrary
name. The arbitrary name should be unique within the domain and only support
alphanumerical characters, underscores and hyphens. Blank spaces are not allowed.

– Config ID: This is a unique number within the Newtec Dialog platform used to identify the
beam when configuring the Satellite Interface settings in the local modem GUI.
The Remote Forward Carrier feature only works if the Config ID parameter at the
NMS and the Beam ID parameter at the terminal side match. For more information
on Remote Forward Carrier, refer to How to Create a Forward Carrier on page 45.
– Signalled Name: This is the name that identifies the beam in NIT and RMT signaling.
– Orbital Position: This is the geosynchronous location of the satellite in degrees on which
the transponder that serves the beam resides.
– West East Flag: This defines the hemisphere, based on the prime meridian, where the
beam is located.
• EAST: The Eastern Hemisphere is a geographical term for the half of Earth which lies
east of the prime meridian (which crosses Greenwich, London, United Kingdom).
• WEST: The Western Hemisphere is a geographical term for the half of Earth which lies
west of the prime meridian (which crosses Greenwich, London, United Kingdom).
– Beacon Enabled: Click the button to enable or disable a beacon.
When enabled, pointing carrier 1 of the remote satellite configuration corresponds with the
following beacon settings:
• Frequency: This is the center frequency of the beacon. The value ranges between 3.4
GHz and 32 GHz.
• Bandwidth: This is the bandwidth of the beacon. The value ranges between 0.001
and 100 MHz.
• Polarisation Type: This is the polarization of the beacon signal. You can select:
• CircularLeft: Left circular polarisation.
• CircularRight: Right circular polarisation.
• LinearHorizontal: Horizontal linear polarisation.
• LinearVertical: Vertical linear polarisation.
When disabled, pointing carrier 1 corresponds with the settings of the forward link.
– Automatic Pointing Enabled: Click the button to enable or disable automatic pointing for
the beam.
When enabled, enter the following automatic pointing settings:
• Polarisation Skew: This is the angle of the satellite which indicates how much the
polarization direction of the received vertical/horizontal polarized signal is rotated with

respect to the earth station antenna vertical/horizontal axis. The value ranges between
-90 and 90 degrees. The default value is 0 degrees.
• Sat Latitude Variance: This is the maximum excursion in the satellite's latitude and is
used for inclined-orbit satellites. The value ranges between 0 and 90 degrees. The
default value is 0 degrees.
• Tx Frequency: This is the L-band frequency at which the terminal transmits. This
value is used by the antenna.
• Tx Bandwidth: This is the bandwidth at which the terminal transmits. This value is
used by the antenna.
The terminal sends these settings to the Antenna Control Unit or ACU using the OpenAMIP
protocol.
6. Configure mobility.
Set the parameters:

– AIBS Enabled: AIBS allows the modem to automatically select the best satellite beam
from the list of configured beams at startup of the modem.
Click the button to enable or disable AIBS or Automatic Initial Beam Selection for the beam.
When enabled, enter the following settings:
• Cost: The higher the beam cost, the less eligible the beam is. This parameter is
optional.
This beam cost applies to all terminals that are using the beam. You can override the
cost in the attachment profile and specify it per terminal type or another service criteria.
For more information, refer to How to Create an Attachment Profile on page 215.
• Automatic Pointing Timeout: This is the maximum time the system can try to point
on the beam. The value ranges between 1 and 1000 seconds. The default value is 20
seconds.
• GXT Beam Name: This is the name of the beam inside the linked GXT file.

– Exclusion Zones: Mobile terminals can be subject to local regulation that restricts
operation in certain geographical zones, which are called exclusion zones. In these zones:
• Transmission can be forbidden (no TX zones), but terminal can still receive. For
example in a radio silence zone.
• Operation is completely forbidden, no transmit, no receive.
The exclusion zones are defined as an area on the Earth's surface, using contour data.
Click + Add to add an exclusion zone and execute the following actions:
• Service Area Number: Enter the number of the exclusion zone inside the linked GXT
file.
• Tx Allowed: Enable the checkbox if a terminal is allowed to transmit in the exclusion
zone. Disable the checkbox if the terminal is not allowed to transmit. Transmission in
the exclusion zone is by default disabled.
• Rx Allowed: Enable the checkbox if a terminal is allowed to receive in the exclusion
zone. Disable the checkbox if the terminal is not allowed to receive. Reception in the
exclusion zone is by default disabled.
If both Tx and Rx Allowed are disabled, the terminal is not allowed to become
operational in that exclusion zone.
• Click to validate the range or click to discard the setting.

• You can add multiple exclusion zones.
Click in the Actions column to edit the zone.
Click in the Actions column to delete the zone.
– GXT File: Select or upload the GXT file that includes the contour information of the beam.
You can select the files that have been created via the GXT File Provisioning interface or
you can click > Show File Upload... to upload a GXT file from your local device. Any file
that you upload here will automatically appear in the GXT Files Provisioning interface. For
more information about the GXT File Provisioning interface, refer to Manage GXT Files on
page 23.
7. Configure the beam neighbors.
Select the beams that are neighbors of the beam that you are creating.
The operation will also be executed in reverse: if beam A is a neighbor of beam B,

beam B is also a neighbor of beam A.

Configuring beam neighbors is only required for fixed terminals, which can be
operational in multiple beams.

Example
A satellite has four beams: 1, 2, 3 and 4. Terminal T has coverage in three beams: 1, 2 and 3.
Each beam has its specific settings for (amongst others):

– NIT
– RMT
– Initial receive carrier
The terminal configuration contains an initial receive carrier, which is typically set in factory. This
can be the initial receive carrier of beam 1, 2 or 3. The terminal receives the signaling tables
(NIT, RMT) via this initial carrier. These signaling tables 'redirect' the terminal to its final traffic
carrier. Each forward traffic carrier has a data carrousel which contains the MAC addresses of
all terminals provisioned within the beam. If the terminal recognizes its MAC address it will
become operational on the traffic carrier of that specific beam.
Let's assume that the terminal is provisioned in beam 3 and that it uses the initial receive carrier
of beam 1. Once pointed to the satellite and locked on the forward link, it receives the NIT table
of beam 1 and it will parse RMT table 1 which directs it to traffic carrier A1 As terminal T is not
provisioned on beam 1, it will not become operational. By configuring beams 2 and 3 as
neighbors of beam 1, the RMT table of beam 1 will also contain the traffic carriers of
beams 2 and 3. After trying traffic carrier 1, it will try traffic carrier 2. Again the terminal will not
detect its MAC address within the carrousel of traffic carrier 2, so it will try forward carrier 3.
Now it will recognize its MAC address and become operational on the traffic carrier of beam 3.

8. Click Apply to save the settings or click Discard to cancel.
Click on the beam in the overview to edit the parameters.
Click in the Actions column to delete the beam.
5.3 How to Create a Satellite Network

To create a logical satellite network, execute the following steps:
2. Click SatNet Provisioning in the surveyor tree or in the visual overview.

4. Click + Create New Satellite Network.
a new satellite network based on the settings of an existing one.
The following window appears:
5. Set the parameters:

– Beam: This is the identifier of the beam that is used by the satellite network.
– Hub Module: This is the name of the hub module on which the satellite network resides.
– Enclosure: This is only available for the 4IF hub module and the XIF processing hub
module. This is the name of the enclosure hosting the blade servers for the satellite
network. The 4IF hub module has only one enclosure, the XIF processing hub module can
have up to three enclosures. For the XIF processing hub module deployed on NPCI the
enclosures correspond with the HPS Pools defined in the Hub Module Provisioning on
page 269 interface.
– HPS: This is the name of the HPS or Hub Processing Segment that handles the data
processing of the satellite network. This segment consists of the associated Edge/Data and
Satellite Channel Processing functions for a satellite network.
• The 1IF hub module has one HPS.
• The 4IF hub module has up to four HPSs.
• The XIF processing hub module has up to 18 HPSs: six HPSs per enclosure or per
HPS Pool in case of NPCI.
In case of the non-NPCI XIF processing hub module, slots 13 to 16 of the first
enclosure can be reserved for embedded NMS. In that case, maximum five
HPSs can be used within the first enclosure.
– Loopback Enabled: This parameter sets the RTT to zero. It is used for testing
environments.
– Hub Position: These are the latitude, longitude and altitude coordinates of the hub. The
exact location of the hub is relevant when using the 4CPM return link technology. When
loopback is enabled, the hub position cannot be set.
– Reference Terminal Position: These are the latitude, longitude and altitude coordinates of
a virtual reference terminal to determine the synchronization footprint for 4CPM. When
loopback is enabled, the terminal position cannot be set.
The mapping between the logical satellite network and the hardware of the satellite
network is done through the Hub Module, Enclosure and Hub Processing
Segment parameters, which have been defined during installation of the hub
module in the Inventory Management System (IMS).
– Expand the Advanced Settings for the following parameters:

• Enable Auto Attachment: Click the button to enable or disable the support of
whitelisted terminals on the satellite network. When enabled, modems that are not
provisioned on the satellite network are allowed to send 4CPM logon requests to the
hub. If the MAC address of the terminal is part of an Auto Attachment Prototype and
the terminal is in the correct beam, the NMS will provision the terminal. This setting is
by default disabled. For more information on whitelisted terminals, refer to
Whitelisted Terminals on page 232.
• Maximum Logon PSD: When Auto Attachment is enabled, the maximum power
spectral density to log on should be defined. The value ranges from -128 and 0
dBm/Hz. The default value is -87 dBm/Hz.

• Individual Tracking: Click the button to enable or disable individual tracking of the
transponder frequency offset. This setting is by default disabled. This parameter is only
relevant when using the 4CPM return link technology.
• Last Corrections Threshold: This is the maximum time in seconds without burst
reception before the 4CPM controller restarts the frequency offset search. This
parameter is only relevant when using the 4CPM return link technology.
• Return Idle Logoff Time: This is the timeout in seconds before an idle modem logs
out. This parameter is only relevant when using the 4CPM return link technology.
– Encrypt mgmt traffic HUB-Terminal: Click the button to enable or disable encryption of
the management traffic between the modem and the hub. Encryption of the management
traffic is by default enabled.
– Encrypt data traffic HUB-Terminal (ex. multicast): Click the button to enable or disable
encryption of the data traffic between the modem and the hub. Encryption of the data traffic
is by default enabled. When enabled, the eTCP sessions between the hub and the terminal
are encrypted. The encryption is handled by the TelliNet client software running on the
terminal and the TelliNet server deployed on the TAS within the hub. This settings can be
overridden per terminal during Terminal Provisioning: How to Configure Modem Settings on
page 235.
The encryption method for data and management traffic encryption is

Asynchronous Encryption Standard or AES. For more information on AES, refer to
Forward Link Encryption on page 37.
By default, Dialog terminals are shipped with encryption keys with effective 56 bit
key length for export control reasons. The full key length of 128 bit is an ordering
option on both hub module and terminal.
Signaling data is unencrypted. This includes ACM and the required signaling to
keep the link established. It is possible to encrypt the forward link, including the
signaling. For more information, refer to Forward Link Encryption on page 37.
– Terminal authentication with X.509 certificate: Click the button to enable or disable
authentication of the modem. Terminal authentication is by default enabled.
Modem authentication, when enabled, is done based upon X.509 certificates. ST
Engineering acts as Certification Authority or CA and generates master private/public key
pairs as well as individual X.509 certificates/private key pairs for every legitimate terminal
manufactured by ST Engineering. Consequently, an X.509 certificate and a public/private
key pair is permanently stored in memory on each modem during production.
During logon, a terminal encrypts its certificate using the public key of the hub and presents
it to the TCS (the IP address of the TCS is signaled to the terminal via the TIM message).
The TCS within the hub decrypts the received certificate using a private key which was
generated during hub installation.
The encryption is based on the AES algorithm, with an effective key length of 56
bits.
If the certificate is valid, the TCS sends an acknowledgement, which contains the user-key
to setup the eTCP association, to the terminal which is encrypted with the terminal public
key. The terminal decrypts this acknowledgement using its private key. If the TCS detects
that the certificate is wrong, it responds with an error code indicating that the request was
unauthorized.
After a successful authentication, the terminal can start with setting up the eTCP
association between the terminal and the hub. This is done based upon the user key it

received during the authentication phase. As soon as the eTCP association is

accomplished, the terminal is fully operational and ready to send and receive user traffic
over the satellite link.
– Enable Certification: Terminal certification helps to identify poorly pointed antennas. It
verifies the quality of the antenna installation in terms of received signal to noise ratio or
SNR and transmitted cross polar interference. Click the button to enable or disable
certification of the terminals within the satellite network. Certification is by default disabled.
This setting can be overridden per terminal during
Terminal Provisioning: How to Configure Modem Settings on page 235.
Certification requires a Terminal Installation Certification System or TICS, which

is an optional feature in Dialog.
Click in the Actions column to edit the parameters.
Click in the Actions column to delete the satellite network.
5.4 Manage GXT Files

A GXT file can contain information of multiple beams that are available on the same satellite. Every
beam has its specific beam identifier within that file. There is at least one GXT file per satellite. GXT
files are typically provided by the satellite operators. Transmit exclusions zones can be defined for
each beam to accommodate regulatory restrictions. If a terminal is located within an exclusion zone,
the beam is excluded from the AIBS or beam switch process.
GIMS is free software offered by ITU which allows you to visualize the beam contours
based on a GXT file.
The GXT files can be uploaded via a GXT Files Provisioning interface. The uploaded files can then
be selected in the Mobility tab when creating a beam. On the other hand, GXT files that are
uploaded in the Mobility tab when creating a beam, automatically appear in the GXT Files
Provisioning overview.
This section explains how to upload a GXT file via the GXT File Provisioning interface. For more
information about uploading a GXT file while creating a beam, refer to How to Create a Beam on
page 12.
5.4.1 How to Upload a GXT File

To upload a GXT file, execute the following steps:
2. Click GXT File Provisioning in the surveyor tree or in the visual overview.

4. Click + Create GXT File.
A window appears where you can upload a GXT file.
5. Enter the Identifier. The identifier is the combination of the HNO domain name and an arbitrary
name. The arbitrary name should be unique within the domain and only support alphanumerical
characters, underscores and hyphens. Blank spaces are not allowed. This is the name that will
appear in the drop-down list when selecting a GXT file in How to Create a Beam on page 12.
6. Click Select file to upload... to select a GXT file from your local device.
When applied, an entry is created in the GXT Files overview. If the file has not been selected
for a beam, the In Use column displays and the Beams column is empty. As soon as the
file is selected for a beam, the In Use column displays and the beam name is indicated in
the Beams column. For more information about how to select the GXT file for a beam, refer to
How to Create a Beam on page 12.
Click in the Actions column to download the GXT file.
Click in the Actions column to delete the file.

Manage Forward Link Resources
6 Manage Forward Link Resources
6.1 Background Information

The forward link is defined as the link from the hub over the satellite to the terminals. The forward
link can use the DVB-S2 and DVB-S2X standard as well as the DVB-S2X Annex M standard.
Annex M specifies the implementation of a DVB-S2 profile suitable for operation in

wideband mode, without requiring a full-speed decoding of the total carrier capacity, by
suitably mapping the transmitted services in time-slices.
Each satellite network uses one forward link. The forward link is segmented into forward pools,
which divide the total forward bandwidth into chunks of IP capacity.
DVB-S2/S2X forward carrier
In DVB-S2 and DVB-S2X, a physical forward carrier corresponds with one forward link.
DVB-S2X Annex M forward carrier (wideband)
In DVB-S2 X Annex M, the wideband forward carrier corresponds with one or more forward links or
virtual carriers.

6.1.1 Adaptive Coding Modulation

Adaptive Coding Modulation or ACM allows modification of the modulation parameters of a satellite
signal on the fly, without interrupting the transmission and without losing data. When combined with
a measurement of the instantaneous link conditions every few seconds and a system that
automatically adjusts the modulation parameters when needed, ACM allows using the highest
possible modulation scheme and the lowest possible level of error correction at all times. In some
instances the amount of data that can be transmitted in a given satellite segment can be doubled (on
average) compared to a fixed modulation system (CCM).
When the condition of the link gets worse because of for example rain fade, the system will
automatically change the parameters to avoid loss of signal reception.
The following forward Link ACM parameters are used to determine which MODCOD to use:
• Forward ACM Down: A lower MODCOD will be selected when the difference between the
measured Es/No and the Es/No threshold for this MODCOD drops below this margin + (DM plus
ML).
• Forward ACM In: This MODCOD will be selected when the difference between the measured
Es/No and the Es/No threshold for this MODCOD exceeds this margin + (DM plus ML).
• DM + ML: This is the sum of extra Distortion Margin used in case of non linear degradation and
extra Modulation Loss margin to counter the modulation loss.
• Es/NO: These threshold values are theoretical values. Theoretical Es/No value does not include
modem type dependent implementation losses, so be aware that modem GUI may show different
values.
• Spectral Efficiency: This is the amount of information that can be transmitted over satellite in a
given bandwidth. The larger the spectral efficiency, the more information that can be sent over the
satellite link in the same bandwidth
• Assigned: This indicates the MODCOD that can be used within the forward link.
You can configure Forward ACM Down, Forward ACM In and DM + ML via the Forward Link on
page 49 web interface. By adjusting these margins, you can optimize the system either for higher
efficiency (= smaller margins) or for less frame errors (= higher margins).

The default values of the parameters are carefully chosen in the Dialog system. We
strongly advise to keep the default values.
The resulting hysteresis loops, detailing the switch-overs between MODCODs, are visualized in the
figure.
Based on the ACM parameters, the terminal calculates two reference Es/No values:
• Es/No_IN = THR + Forward ACM In + (DM+ML)
• Es/No_DOWN = THR + Forward ACM Down + (DM+ML)
These reference values are used to decide when to move up or down to another MODCOD. The
terminal requests a higher MODCOD when its measured Es/No > Es/No_IN. The terminal requests a
lower MODCOD when the measured Forward Es/No < Es/No_DOWN.

It can occur that there are intermediate MODCODs when moving to another MODCOD. When
moving to a lower MODCOD, the intermediate MODCODs are skipped and the terminal immediately
uses the lowest MODCOD. When moving to a higher MODCOD, the modem skips all MODCODs for
which the measured Es/N0 is at least 2 dB higher than the Es/N0_IN value. From then on it
increases the MODCOD step by step, meaning that all remaining intermediate MODCODs (with an
Es/N0_IN value < measured Es/N0 + 2 dB) are used before reaching the highest MODCOD.
For individual terminal installations, there can be link degradation at higher MODCODs which is not
known to the ACM algorithm. For example, when WiMax signals at the terminal location are present
or when the used frequencies (typically C-band) are close to other mobile applications.
ACM implements two solutions to face unpredictable distortion:
• Reactive behavior based on baseband frame drops
For each available MODCOD the terminal monitors the errored baseband frames. Errored
baseband frames are dropped at the modem's decoder. A MODCOD becomes 'unavailable'
from the moment that errored frames occur and will remain 'unavailable' 120 seconds after the
last errored frame occurred.
When the modem notices a baseband frame drop for the MODCOD it has selected according to
the ACM algorithm described above, it will select a lower and error-free MODCOD. An error-free
MODCOD is a MODCOD where there has not been an errored baseband frame in the last 120
seconds.
This baseband frame-aware ACM behavior is only supported on the modem

10-series.
This behavior is not configurable.
For more information about the baseband frame-aware ACM behavior, refer to the
Newtec Dialog Functional Description.
• Static limit on the maximum modulation and coding

The terminal can be provisioned with a maximum MODCOD. The maximum MODCOD is
selected from the MODCOD list, which is ordered according to the ideal Es/N0 threshold, as
specified in the DVB-S2(X) standard. The configuration of the maximum MODCOD implies that
the modem will not use any MODCOD that has an ideal Es/N0 threshold higher than the one of

the maximum MODCOD. The maximum MODCOD for the modem is signaled in the POP-ID of
the FTB and in the POP-ID descriptor of the mobility TIM. Refer to
Manage Terminal Provisioning on page 232 to set the maximum MODCOD for the terminal.
If the defined maximum MODCOD is lower than the lowest MODCOD specified in the
ACM signaling, the modem will select the latter MODCOD.
6.1.2 Time Slicing
Time slicing is supported on MCM7500 modulators and MDMxx10 modems.
High Transport Satellites use wide transponders, which result in forward carriers that can go up to
480 Mbaud or reach a throughput of ~ 2 Gbps. The use of wide carriers require complex and
expensive receivers. To avoid this expense, Annex M of the DVB-S2X standard introduces the
concept of time slicing.
Time slicing is a way to split a wideband carrier into smaller Virtual Carriers or VCs. The smallband
VCs can be received by low-cost modems.
The wideband forward carrier is divided into frames which are marked with a slice identifier at
physical layer. The frames of the wideband carrier with the same slice ID correspond with one VC.
A terminal is linked to a virtual carrier through the satellite network where it is provisioned. The
terminal only processes frames with the corresponding slice ID, all other frames are ignored at
physical layer level. In the figure below, frames with slice id = 1 are processed, the other frames are
dropped. This results in the receiver/demodulator having more time to process the frames.

The table below provides the maximum symbol rates in Mbaud when using time slicing (Annex
M operation) for a number of satellite networks or VCs per physical carrier. It is assumed that:
• The VC sizes are equal;
• The highest MODCOD is the same per VC;
• The sum of VC sizes equals 0.997 times the physical carrier size.
# VCs Maximum Symbol Rate (Mbaud)
QPSK 8PSK 16APSK 32APSK 64APSK
1 148 148 132 106 88
2 144 144 110 79 NA
3 135 135 102 79 58
4 120 120 108 81 65
5 NA NA 96 86 69
6 NA NA NA 80 72
7 NA NA NA NA 68
The total symbol rates of the VCs must be smaller than or equal to the 0.997 times the
symbol rate of the physical carrier.

The table below shows the minimum number of equally sized VCs to achieve a certain physical
carrier symbol rate with a certain maximum MODCOD.
For example, for a physical carrier of 300 Mbaud:

• At least three equally large VCs must be transmitted if 16-ary MODCOD is the highest MODCOD.
• At least four equally large VCs must be transmitted if 32-ary MODCOD is the highest MODCOD.
• At least five equally large VCs must be transmitted if 64-ary modcods is the highest MODCOD.
Configuration of the maximum MODCOD is done via the Forward Link on page 49 web interface.
6.1.3 Encapsulation
All traffic sent through a Newtec Dialog system needs to be encapsulated in order to fit in baseband
frames. Baseband frames are the basic unit used in the DVB-S2(X) standard. It provides
(de)modulation and (de)coding services and a simple addressing scheme in the form of an 8-byte
Input Stream Identifier (ISI). Each baseband frame sent by a modulator has a MODCOD which
specifies the MODulation scheme (QPSK/8PSK/16APSK/32APSK/...) and CODing scheme (7/8,
9/10, ...).

In a Newtec Dialog system, you can use the following encapsulation protocols:
• MPE or Multi Protocol Encapsulation is an MPEG-based encapsulation protocol. The payload is
wrapped into an MPE section header. In case of a layer 2 payload, the extra 8-byte LLC/SNAP
header is added as well. Optional stuffing and a 4-byte CRC is added to the trailer. The complete
MPE section is wrapped up to the Transport Stream or TS cells (typically 188-byte). The TS
stream is fitted into baseband frames.
MPE encapsulation example for an IP packet
• GSE or Generic Stream Encapsulation is more efficient. GSE can use 0, 3 or 6-byte labels. Data
traffic is GSE-encapsulated and the GSE stream is fitted into baseband frames. The payload is
wrapped into a GSE header, which includes the Protocol Type field used to distinguish between
layer 3 (IPv4 or IPv6) and layer 2 (Ethernet) traffic.
GSE encapsulation example for an IP packet
GSE-encapsulated data and MPE-encapsulated data cannot co-exist in the same baseband frame.
The signaling sent by return link controllers is always MPEG-based, even when GSE encapsulation
is used. In case of MPE encapsulation, the signaling and payload MPEG-TS streams can be merged
into the same baseband frame. In case of GSE encapsulation, this is not the case and a separate
ISI (Input Stream Identifier) value in the baseband frame is used to distinguish between signaling
and data traffic.
In case of a low MODCOD, signaling traffic is typically low. When using GSE encapsulation, the
baseband frames with MPEG-TS signaling cannot be filled with the GSE-encapsulated data. They
will be padded instead. As a result, the filling efficiency of the baseband frames is rather low when
using GSE compared to MPE. On the other hand, the data itself is encapsulated more efficiently with
GSE.
The following table shows when it becomes more efficient to use GSE than MPE.

Average packet size Bitrate for which GSE is more Bitrate for which GSE is more
efficient than MPE for layer 3 efficient than MPE for layer 2
traffic traffic
Normal frames
50 bytes 37 Mbps 23 Mbps
Short frames
50 bytes 2.9 Mbps 1.8 Mbps

Configuration of the encapsulation protocol is done via the Forward Link on page 49 web interface.
The DVB tables and their corresponding (packet) identifiers are used for the signaling between hub
and terminals. These are shown in the Encapsulation on page 49 tab of the forward link. The Dialog
platform uses default values for these identifiers, however it is possible to edit these values. For
more details, refer to the DVB-S2 and DVB-S2X standard.
Only change the default parameters when you need a specific, tailored RMT signaling.
Setting incorrect Service Identifiers or Packet Identifiers may result in disruption of the
platform service!
6.1.4 Forward QoS Shaping

The forward link capacity is divided into different forward pools. The forward pools can be
class-based or transport-based, and dedicated to a VNO or shared by multiple VNOs. The
class-based pools are further divided into QoS pools. Terminals are either linked to a forward pool
(in case of a transport-based model) or to the QoS pools (in case of a class-based model).
For multicast traffic in the forward, the forward link has one multicast pool. The hub multicast circuits
are linked to this pool. The multicast pool has priority over any unicast class-based or
transport-based pools.
This results in the following forward shaping tree.
You can distinguish four shaping levels:

• Shaping Level 1: At this level the total capacity is represented, which corresponds with the
capacity of a forward link or one satellite network.
• Shaping Level 2: At this level the root pool or container capacity is divided over class-based
and/or transport-based forward pools. You can also have one multicast pool, which has priority
over the other pools.
• Shaping Level 3: In case the pool is class-based, shaping level 3 represents the QoS pools. In
case of transport-based pools, shaping level 3 represents the terminal circuits and hub multicast
circuits (if any).
• Shaping Level 4: This shaping level represents the QoS classes.

In the transport-based shaping model, you can have one extra level: CD aggregation node (not
displayed in the figure). This node allows you to aggregate two or more CD classes. The CD
classes inside the node compete with each other for bandwidth and the aggregation node competes
with the QoS classes outside the node for bandwidth.
From a configuration point of view, following provisioning interfaces are involved:

• The root pool, forward and QoS pools are configured in the Forward QoS Plan. This is explained
in this chapter.
• The multicast pool is a setting of the Forward Link. This is explained in this chapter.
• The terminal circuits and QoS classes are configured in the Service Profile. For more information
about service profiles, refer to Manage Service Profiles on page 198.
• The multicast circuits are configured as part of the Satellite Resources. For more information,
refer to How to Create Hub Multicast on page 340.
The parameters that are used to control the use of bandwidth at the different shaping levels are:
• PIR: The Peak Information Rate or PIR is the maximum unicast traffic rate.
• CIR: The Committed Information Rate or CIR is the guaranteed unicast traffic rate..
The Committed Information Rate can be overbooked, meaning that the sum of all CIR values of
the child nodes exceeds the CIR value of the parent node.
Always pay attention when using CIR overbooking as this can have an impact on
the data rate a terminal receives. By enabling CIR overbooking the rate is no longer
guaranteed and can be less than expected (see example below).
CIR overbooking should only be applied if one can predict the average number of
concurrent capacity requests.
• Weight: The weight is an integer value between 1 and 1000 and is used to define the Total
Weight, which equals PIR * Weight. The total weight is used to distribute the available bandwidth
among nodes at the same level and with the same priority.
Other fundamental shaping parameters are:
• Priority (static): Priority is defined by the QoS class.
– RT1 = prio 1 (highest)
– RT2 = prio 2
– RT3 = prio3
– CD1..14 = prio 5
– BE = prio 6 (lowest)
Prio 4 is used for control traffic.
• Shaping Volume (dynamic): This is the actual capacity need of a terminal. The capacity requests
are triggered by the ingress traffic on the modem's LAN interface.
At root pool level, you can set the Child Pool Shaping Mode. Two values exist:
• Bit Rate Shaping: The unit of CIR and PIR in both root pool and child pools is Mbps. In this case,
two terminals with the same IP rates but different MODCOD will consume different bandwidth.
• Symbol Rate Shaping: The unit of CIR and PIR in the child pools is Mbaud. In the root pool the
unit of PIR is still Mbps and CIR cannot be set.

When entering the shaping values, the impact of applied header compression and packet
size needs to be taken into account. For example: a terminal has a Best-Effort PIR of 1
Mbps defined in its service profile. When measuring the actual received bit rate, it can
differ from the value set in the service profile because of the impact of encapsulation
and/or compression. It is advised to use the IP rate calculator to determine the actual bit
rate which will be received.

6.1.5 Shared Transport Stream
This feature only works with a Dialog 4IF platform using M6100 modulators.
When enabled, only two satellite networks can be used instead of four.
The Shared Transport Stream feature allows to combine the DVB-S2 CCM forward carrier from the
Dialog system with a transport stream from another system. This is done by multiplexing a TV or
radio transport stream (TS) with MPE encapsulated IP data from the Dialog system. The modulator
interfaces with the external MUX using ASI interfaces. The CSE encapsulates IP packets into
MPEG2 transport stream packets and sends these over IP/UDP to the modulator. The modulator
sends the transport stream to the MUX over ASI. The external MUX adds the audio/video broadcast
transport stream and sends the multiplexed stream back to the modulator. The modulator then sends
the multiplexed stream over satellite to remote terminals using DVB-S2 CCM. A remote terminal can
then either receive the IP part of the multiplexed stream or the Audio/video broadcast part.
The total capacity of the forward carrier is divided between the Dialog system and the audio/video
broadcast service.
The capacity for the multiplexed transport stream is always reserved, even if nothing
has to be transmitted.
6.1.6 Forward Link Encryption
Only hubs operating with MCM7500 modulator support AES-256.

All modems in the satellite network must support decryption to allow AES-256 in the
forward link
Decryption is supported on the following modems:
• AMC5001
• SMB3310 *
• OEM5001 *
• MDM5010
* roadmap

Before the feature can be used on a Dialog system all modulators must have received
the feature license on the device.
Advanced Encryption Standard or AES is one of the most popular and secure encryption standard. It
comes in 128-bit, 192-bit and 256-bit implementations, with AES-256 being one of the most secure
encryption methods used nowadays in the industry. This encryption technic uses a 256-bit key to
encrypt and decrypt data. Hence, a hacker would need 2^256 different combinations to break in a
256-bit-keyed message.
AES is a symmetric key cipher. This means the same secret key is used for both encryption and
decryption, and both the sender and receiver of the data need a copy of the key. The advantage of
symmetric systems like AES is their speed, as symmetric key algorithms require less computational
power than asymmetric ones. AES is also characterized as a block cipher. In this type of cipher, the
information to be encrypted, known as plaintext, is divided into blocks. AES uses a 128-bit block
size, in which data is divided into a four-by-four array containing 16 bytes. Since there are eight bits
per byte, the total in each block is 128 bits. The size of the encrypted data remains the same: 128
bits of plaintext yields 128 bits of cipher text.
Dialog allows AES-256 encryption with GCM operation mode on the forward link. When enabled, the
following streams can be affected:
• The payload of MPE-encapsulated DVB-S2 baseband frames is encrypted. In this case, both the
control and data planes are encrypted.
• The payload of GSE-encapsulated baseband frames is encrypted. In this case, users can choose
to encrypt data or/and control planes.
For more information about how AES-256 works and the AES GCM mode, refer to the
NIST Special Publication 800-38D.
Dialog also allows to only encrypt the eTCP sessions between the hub and the terminal.
For more information, refer to Manage General Satellite Resources on page 11.
High-level End-to-End Process

Encryption is done by the modulator in the forward link or per virtual carrier in case of a wideband
carrier. The modulator encrypts the DVB-S2(X) baseband frames or BBFs, modulates them, and
then transmits them over the satellite link. At the terminal, the forward signal is demodulated,
decoded and then decrypted.
After encryption, two bit strings are obtained: a ciphertext and an authentication tag.
The ciphertext is the result of the encryption algorithm performed on the plain text.
A common key must be known at the hub and the terminal for encryption and decryption of the
ciphertext. This key, called Transport Key or TK, is set by the user during configuration of the
forward link. At least one TK per stream is needed. Dialog supports the configuration of four keys (an
odd and an even key per each stream) to allow key rotation. For more information to set the keys,
refer to How to Create a Forward Link on page 49.
Once the TK is set up at the hub, it must be stored securely within the devices. To that end, a Key
Encryption Key or KEK is used to encrypt the TK.
The installed keys are stored encrypted on the device. It is not possible to reuse the keys
by coping the configuration from one device to another.

Next to the keys, an Initialization Vector is needed. The initialization vector is a nonce. A nonce is an
arbitrary number which can be used just once in a cryptographic communication, to ensure that an
old communication can not be reused. The Initialization Vector is automatically generated by the
hub.
Next to confidentiality through encryption, integrity and authenticity of the data must be guaranteed.
To that end, a hash function is used. A hash function maps data of arbitrary size into fixed-size
values. The hash function produces as outcome an authentication tag.
The hash function used is the GHASH_H function, as defined in section 7.1 of NIST
SP-800-38D publication.
The implementation of Hash Key is compliant to the section 7.1 of the NIST SP-800-38D
publication.
The encryption process at hub-side is shown in the figure below.
At the terminal-side, the ciphertext and the authentication tag are decrypted after demodulation and
decoding. In case the authentication tag is not correct, the baseband frame is dropped.
The decryption process is summarized in the following image:

Encrypted Baseband Frames

When a DVB-S2(X) BBF is encrypted, the first 96 bits, corresponding to the signaled nonce, are
never encrypted:
• 46 bits are device specific.
• 50 bits are the BBF count. This field is incremented for every BBF frame. The same BBF count is
not repeated on the same device.
The encryption occurs in different parallel blocks per BBF. Every block uses a different value of the
BBF count. The BBF count is reset at the beginning of every BBF frame.
The BBF count is used accordingly to the AES GCM mode; NIST Special Publication
800-38D.
The nonce value is signaled every BBF frame. As the count is present in every BBF frame, a
decryption cycle can start with information present in every BBF frame.

6.1.7 Frequencies
When defining the transponder and forward carrier several frequencies need to be set.
The modulator transmits the forward signal at an L-band or IF-band frequency.
The M6100 modulator within a 1IF or 4IF hub module can transmit in L-band or
IF-band.
The MCM7500 modulator only transmits in L-band.
The Local Oscillator of the hub transmitter transforms the modulator frequency into an RF frequency,
which is received by the satellite transponder. The satellite applies a delta frequency to convert the
uplink frequency into the downlink frequency, which is received by the LNB of the remote terminal.
The LNB at the remote side transforms the downlink frequency into an L-band frequency used by
the remote modem.
Based upon these values, the system automatically calculates the remaining frequencies of the
forward link (modulator transmit frequency, hub RF uplink frequency).
6.2 Setup of Forward Link Resources


the modulators, demodulators and number of HPSs.
configuration, refer to the specific Newtec Dialog Hub Installation Guide.
which terminals are serviced.
For more information about how to create the logical satellite network and beam, refer to
Manage General Satellite Resources on page 11.
A satellite network is defined by a forward link. The forward link is linked to a forward carrier and the
forward carrier is linked to a transponder.
Assuming that the hardware of the satellite network is installed and configured, and that the beam
and logical satellite network have been created, following sequence of steps should be executed:
1. Create a transponder.
2. Create a forward carrier, which is linked with the previously created transponder.
3. Create a forward link and link it with the previously created forward carrier and logical satellite
network.
When the forward link has been created, the forward QoS plan can be defined.
Changing the Forward Link settings on a life platform causes a traffic interruption of
about 40 seconds because of a restart of the shaper process on the CSE.
6.3 How to Open the Forward Resources Web Interface

To open the provisioning interface of the Forward Resources, execute the following steps:

4. From here:
– You can click Transponder Provisioning and FW Carrier Provisioning in the surveyor
tree or visual overview.
– You can click General Overview in the surveyor tree or in the visual overview.

The general overview displays the satellite network, the forward resources and the return
resources. If there are multiple satellite networks, make sure to select the correct one in the
drop-down menu in the upper left of the pane.
6.4 How to Create a Transponder for the Forward Link

To create a transponder, execute the following steps:
1. Follow the steps as described in How to Open the Forward Resources Web Interface on page
42.
2. Click + Create New Transponder in the Transponder Provisioning interface. The following
window appears.

– Delta Frequency: This is the shift in MHz from uplink to downlink frequency within the
transponder. This value is typically provided by the satellite operator. To know which exact
frequency is meant, refer to Frequencies on page 41.
– Saturated Flux Density: This setting is only relevant for transponders used for the return
link.
– Input Back Off: This setting is only relevant for transponders used for the return link.
– Non Linear Predistortion: Enable this feature to counteract non-linear distortion effects of
the power amplifier (HPA) of the transponder and optimize the satellite link performance.
This feature can only be enabled for forward carriers, which are linked to an MCM7500.
When enabled, only one carrier can be linked to this transponder.
When enabled, enter the following parameters:
• AM/PM: This setting is measured during the calibration process of MCM7500. It is a

non-linear distortion effect of the power amplifier of the satellite transponder and it
quantifies the phase distortion as function of the amplitude of the input signal. The
value ranges between -4 and +4.
• AM/AM: This setting is measured during the calibration process of MCM7500. It is a
non-linear distortion effect of the power amplifier of the satellite transponder and it
quantifies the amplitude distortion as function of the amplitude of the input signal. The
value ranges between 0 and +4.
• Max Allowed Modulation Constellation: This setting is measured during the
calibration process of MCM7500. The highest MODCOD used for the forward carrier
should not exceed this MODCOD.
• Compression: This setting is measured during the calibration process of MCM7500. It
is a non-linear distortion effect of the power amplifier of the satellite transponder and it
quantifies the compression after saturation.
4. Click Apply to save the settings or click Discard to cancel. Check the log panel for validation
messages.
Click on the transponder in the overview to edit the parameters.
Click to delete the transponder.
6.5 How to Create a Forward Carrier

To create a forward carrier, execute the following steps:
1. Follow the steps as described in How to Open the Forward Resources Web Interface on page
42.

2. Click + Create New Forward Carrier in the FW Carrier Provisioning interface.
a new forward carrier based on the settings of an existing one.

– Transmission Standard: Select the forward carrier technology from the drop-down menu.
• DVB-S: Original DVB-S standard for satellite.
• DVB-S2 CCM: Each frame is transmitted using the same MODCOD.
• DVB-S2 ACM: Each frame can be transmitted using a different MODCOD based on
the feedback from remote terminals.
• DVB-S2X: Official extension of the DVB-S2 standard.
• DVB-S2X Annex_M: Option within DVB-S2X standard to use Time Slicing on page 29.

Click + Show Forward Links to view the forward links or virtual carriers which
have been configured within this wideband forward carrier. See Time Slicing on
page 29.
– Down-link Frequency: Enter the center frequency of the forward carrier in the downlink.
The downlink is the link from the transponder to the terminals. The value is between 3.4
GHz and 32 GHz.
– Symbol Rate: Enter the symbol rate of the forward carrier in MBaud. The value will
depend on the transmission standard and must be a value between:
• DVB-S: 1 and 63 MBd
• DVB-S2 ACM / CCM: 1 and 63 MBd
• DVB-S2X: 1 and 133 MBd
• DVB-S2X Annex_M: 1 and 500 MBd
– Down-link Polarisation Type: Select the polarization of the forward carrier in the
downlink. The forward downlink is the link from the satellite to the remote terminal.
– Enable Candidate Settings: Click the button to enable or disable settings of a candidate
forward carrier. In case a terminal is allowed to receive its satellite configuration from the
hub, these settings are used for initial carrier 2. Candidate settings are useful when
migrating the forward carrier. When enabled, the same parameters as for the actual forward
carrier should be defined. For more information about remote terminal satellite
configuration, refer to Manage Remote Configuration Profile on page 229.
The Remote Forward Carrier feature only works if the Config ID parameter of the
beam at the NMS and the Beam ID parameter at the terminal side match.
– Tx Interfaces: This setting is only available for XIF hub modules. Select the
transmission interfaces on the RF matrix, which are used for this forward carrier. The TX
interface is set during the hub module installation and can be checked via the
Hub Module Provisioning on page 269 interface.
– Modulator Role: Select a modulator from the drop down menu. The list is automatically
populated based on the modulators that you have entered in the Hub Module Provisioning
on page 269 interface during inventory management. An empty list means that no
modulators are available.
For more information about adding modulators in a Newtec Dialog Hub, refer to
the Newtec Dialog Hub Installation Guides
– Roll Off Factor: Select a value from the drop-down list. The roll-off factor allows for a
higher symbol rate in the same leased bandwidth. The occupied bandwidth of the forward
carrier is defined as Symbol Rate*(1+Roll Off Factor).

– Transmit Enabled: Click the button to enable or disable the transmission of this forward
carrier. Disabling transmission is useful when performing maintenance on the system.
Transmission is by default enabled.
– Hub Delta Frequency: This is the frequency shift performed in the hub module to convert
the modulator frequency (L-band or IF-band) into an RF frequency (C-band, Ku-band,
Ka-band). It corresponds with the BUC LO frequency.
– Spectrum Inversion: Click the button to enable or disable spectrum inversion. Spectrum
inversion has to be enabled in case an external RF block up converter inverts the spectrum.
– Pilot Insertion: Use pilots to increase the reliability of the receiver synchronization. When
enabled a pilot is injected after every 16 baseband FEC frame slots. Pilots are blocks of 36
non-modulated symbols, which can be received by any receiver. Pilots are by default
enabled.
– Pure Carrier: Click the button to enable or disable the transmission of a pure carrier by the
active modulator (using the power and frequency as set via the corresponding parameters).
A pure carrier signal is not modulated.
– Output Level: This is the transmit power of the modulator. The value must be between -35
dBm and 10 dBm. The default value is -15 dBm.
– Shared Transport Stream: Click the button to enable or disable the shared transport
stream feature. When enabled, part of the forward carrier capacity is used for another
transport stream. This transport stream is multiplexed with the MPE encapsulated IP data
from the Dialog system. For more information about this feature, refer to
Shared Transport Stream on page 37.
In order to use this feature, the following requirements apply:

• Your dialog hub module is a 4IF hub module with M6100 modulators.
• The forward carrier Transport Standard is set to DVB-S2 CCM.
• The forward link Encapsulation Type is set to MPE-GS. See
How to Create a Forward Link on page 49.
• Bit Rate: When the Shared Transport Stream feature is enabled, enter the bit rate of
the multiplexed transport stream.
This bit rate should be the exact same as the output bit rate of the MUX.
This portion of the forward carrier capacity is always reserved. The available
bit rate for the Dialog forward carrier equals the total bit rate of the forward
carrier minus this bit rate, even when there is no multiplexed transport
stream.
– Transponder: Select the identifier of the transponder, which is used by this forward carrier.
If the transponder has not yet been created, click and create a new transponder. For
more information, refer to How to Create a Transponder for the Forward Link on page 44.
messages.
Click on the forward carrier in the overview to edit the parameters.
Click to delete the forward carrier.

6.6 How to Create a Forward Link
You can only create a forward link if a forward carrier is configured.
To create a forward link, execute the following steps:

1. Open the Forward Resources web interface as described in
How to Open the Forward Resources Web Interface on page 42
2. Click + Create in the General Overview interface. Or click Forward in the General Overview
interface. If the forward link has not been created, the interface displays the available forward
carriers and transponders. You are only able to create a forward link when there is at least one
forward carrier and one transponder available. The interface also allows you to add forward
carriers and transponders.
3. Configure the forward link parameters.
Set the parameters:

– Satellite Network: This is the name of the satellite network that is served by this forward
link.
– Forward Carrier: Select the name of the forward carrier that defines this forward link.

– Slice Id: This parameter is only displayed when the forward link or virtual carrier is linked to
a wideband forward carrier (DVB-S2X Annex M). Enter a number to mark the frames for
this virtual carrier. The number should be unique for each virtual carrier within the wideband
forward carrier. For more information on the Slice Id, refer to Time Slicing on page 29.
– Max Symbol Rate: This parameter is only displayed when the forward link is linked to a
wideband forward carrier (DVB-S2X Annex M). Enter the maximum symbol rate of this
virtual carrier in MBaud. For more information on the maximum symbol rate, refer to
Time Slicing on page 29.
– Max Multicast Bandwidth: This is the maximum bit rate reserved for the multicast pool. If
no multicast is required, the value should be set to 0 Mbps. For more information about
multicast pools, refer to Forward QoS Shaping on page 34.
– Frame Type: This parameter defines if DVB-S2(X) should use normal (64800 bits) or short
(16200 bits) baseband frames.
– Merging Slicing Mode: Packets are encapsulated in baseband frames (BBF).
Encapsulation is done as efficiently as possible, meaning that packets can be merged or
sliced to fill up the BBFs as much as possible. Merging and slicing of packets to baseband
frames can be controlled:
• No Break Or Same ModCod: Merge packets of different MODCOD if possible, but
never slice packets to several baseband frames of different MODCOD (use padding
instead).
• No break: Merge packets of different MODCOD if possible, but never slice packets to
several baseband frames (use padding instead).
• Off: Never merge packets and never slice packets to several baseband frames (use
padding instead). This basically places the packets at the beginning of the baseband
frame.
• On: Merge packets of different MODCOD if possible and slice the packets to several
baseband frames instead of padding them.
• Same ModCod: Never merge packets of different MODCOD into the same baseband
frame, but slice packets instead of padding them.
– Encapsulation Type: This parameter defines which encapsulation protocol is used. You
can choose between GSE and MPE-GS. For more information, refer to Encapsulation on
page 31.
– AES 256 Encryption: Click the button to enable or disable AES-256 encryption of the
forward link data or signaling. When enabled, either:
• The payload of MPE-encapsulated DVB-S2 baseband frames is encrypted, therefore
control and data plane are encrypted.
• The payload of GSE-encapsulated baseband frames is encrypted. In this case, users
can choose to encrypt data, control and/or management planes.
The following parameters need to be configured, for the signaling or signaling and data
traffic, depending on the type of encapsulation:
• Even/Odd Key: Two different keys can be provided in order to allow key rotation
without traffic interruption.
• Used Key: Select the key(s) that will be used. When set to Disabled, there will be no
encryption.
Keys can be updated. In case an alternative key is installed, packets will be

lost until the new key is set at both ends. Switching between odd and even
keys or overwriting the same key do not introduce packet loss.

To enable AES-256 encryption of the forward link a Key Encryption Key must
be configured. For more information, refer to
How to Configure a Key Encryption Key on page 70.
– DSCP Values: This defines the internal DSCP values to use for traffic in the different traffic
classes. The values are used when the Packet Marking Mode on page 192 in the
classification profile is set to Mark.
If external DSCP marking on the forward link is already applied, it is advised to

set the internal DSCP values equal to the external DSCP values.
4. Configure the MODCODs.
For more information about forward MODCODs, refer to the Newtec Dialog
Functional Description.
– Click Show VL-SNR modcods to display the very low SNR MODCODs. A VL-SNR
MODCOD allows terminals with an Es/No value as low as -10 dB, typically mobile
terminals, to lock on the forward. The standard SNR operation range operates reliably at
symbol-energy per noise levels of slightly lower than Es/No = -2.5 dB.
VL-SNR is only supported on MCM7500.

VL-SNR is supported on AMC5001 and MDM5010.

MDM3310, SMB3310, SMB3315, MDM2510, MDM2210 and MDM5000 are
compatible with VL-SNR frames, meaning that they are able to recognize and
ignore VL-SNR frames.
The other terminals cannot be used on a forward link where VL-SNR MODCODs
are enabled.
– Click in the Actions column to assign the MODCOD to the forward link. Repeat this
step for every MODCOD that needs to be assigned. This is typically based on the link
budget.
– Click in the Actions column to unlink the MODCOD.
The icons represent the current state of the MODCOD.
– Click in the Actions column to change the ACM settings of a MODCOD. Click
to confirm the MODCOD ACM settings or click to cancel the changes.
The default values of the parameters are carefully chosen in the Dialog system.
We strongly advise to keep the default values.
5. Configure the encapsulation parameters.
It is advised to keep the default values. Only change the default parameters when
you need a specific, tailored RMT signaling. Setting incorrect service identifiers or
packet identifiers may result in disruption of the platform service!

If needed, modify the following parameters:

– Service IDs
• Network: The network identification used in the Network Information Table (NIT).
• Population: The population identifier referencing this forward link.
• Interactive Network: The interactive network identification in the RMT.
• FLS Service: The service identifier for the signaling of this forward link.
• Transport Stream: The transport stream identifier used on this forward link.
• RMT Service: The service identifier for the RCS mapping service in this network
– Program Identifiers (PIDS)
• PMT of RMT:The MPEG packet identifier used for the Program Map Table (PMT) of
the RCS Mapping Table (RMT).
• FCT: The MPEG packet identifier used for the Frame Composition Table.
• PMT of FLS: The MPEG packet identifier used for the Program Map Table (PMT) of
the Forward Link Signalling Service (FLS).
• TCT: The MPEG packet identifier used for the Timeslot Composition Table.
• RMT:The MPEG packet identifier used for the RCS Mapping Table.
• TBTP: The MPEG packet identifier used for the Terminal Burst Time Plan.
• NCR:The MPEG packet identifier used for the Network Clock Reference (NCR). This
value is hardcoded and cannot be changed.
• MPE: The MPEG packet identifier used for the Multi-Protocol Encapsulation (MPE).
This value is hardcoded and cannot be changed.
• SCT CPM: The MPEG packet identifier used for the Superframe Composition Table for
CPM.
• TIM: The MPEG packet identifier used for the Terminal Information Messages (TIM).
• SCT S2: The MPEG packet identifier used for the Superframe Composition Table
(SCT).
• WCT: The MPEG packet identifier used for the Waveform Composition Table.
• HRC: The MPEG packet identifier used for the HRC signaling.
• MRC Waveform PID: MPE PID of the MRC waveform signaling.
• MRC Allocation PID: MPE PIDs of the MRC allocation signaling.
messages.
Click in the General Overview interface to edit the parameters.
Click in the General Overview interface to delete the forward link.
Click in the General Overview interface to go to the forward QoS plan.

6.7 How to Save the Modulator Configuration
It is advised to save the configuration of the modulator whenever changing the settings
of the forward carrier or forward link. It will ensure that the modulator uses these
settings in case of reboot.
You can reach the modulator's web interface via the NMS GUI.
1. Select the modulator via the surveyor tree. The modulator can be found under the Physical
Devices / Device Pools.
2. Click webInterface in the upper left of the card navigation pane to open the modulator's web
interface.
3. Click the guest user in the upper right and select Switch User.
A login window is displayed where you should enter the following credentials:
– Username = operator
– Password = operatoroperator
Click Login.
4. Click Device in the menu at the left.

5. Click Configurations in the upper left. A pop-up window appears.

6. Click Save.... Another pop-up window appears.
Enter a name for your configuration or select a name from the drop-down menu. Click Save
Config.
The new configuration is listed in the Configurations overview.

7. Click Make Boot to make the new configuration the boot configuration.
The boot configuration is indicated as BOOT.

8. Repeat these steps for the redundant modulator (if present).
6.8 How to Open the Forward QoS Plan Interface

To open the provisioning interface of the Forward QoS plan, execute the following steps:
Following selections can be made in the surveyor tree or in the visual overview.
3. Click Satellite Resources.

4. From here, you can access the forward QoS plan in different ways.

Click next to Forward Link to open the forward QoS plan.

– You can select the beam identifier and Satellite Network that corresponds with the
forward link. Click Resource Provisioning and then click FW QoS Plan.

The provisioning interface is displayed. The root pool corresponds with the entire satellite
network.
– Click Detailed to show or hide the CIR/PIR details.

– Click Expand to collapse or expand the QoS tree.
– Click Legend to know the functionality of the icons and the applied color scheme.
Alternatively you can hover over the icons.

6.9 How to Edit the Root Pool

The forward root pool corresponds with the entire satellite network. To edit the QoS parameters of
the root pool, execute the following steps:
1. Open the provisioning interface of the FW QoS Plan as described in
How to Open the Forward QoS Plan Interface on page 56.
2. At root pool level, click .
3. Edit the general parameters:

– Child Pool Shaping Mode: This parameter defines whether the satellite link capacity is
expressed in Mbps or in Mbaud.
• Bit Rate Shaping: The unit of CIR and PIR in both root pool and child pools is Mbps.
In this case, two terminals with the same IP rates but different MODCOD will consume
different bandwidth.
• Symbol Rate Shaping: The unit of CIR and PIR in the child pools is Mbaud. In the
root pool the unit of PIR is still Mbps and CIR cannot be set.
– Access Rights: The root pool and underlying child pools can be dedicated to a specific
VNO or shared among multiple VNOs. Use the slider to select Dedicated or Shared.

– Dedicated to: This parameter appears when the Access Rights are set to Dedicated.
Select a VNO domain name from the drop-down list to whom this root pool is dedicated.
4. Enter the shaping parameters:
– CIR: CIR or Committed Information Rate defines the data rate that is always granted during
data rate distribution as long as the total available data rate is not exceeded. This
parameter is not available when the Child Pool Shaping Mode is set to Symbol Rate
Shaping.
– PIR: PIR or Peak Information Rate defines the upper data rate limit for this pool.
– Allow CIR Overbooking: Click the button to enable or disable CIR overbooking. CIR
overbooking is by default enabled. When enabled, the total CIR used by the child pools
may exceed the CIR rate of the root pool. This parameter is not available when the Child
Pool Shaping Mode is set to Symbol Rate Shaping.
5. Click Confirm to accept the changes or Cancel to discard the changes.
Click to view the details of the root pool.
Click to edit the parameters.
6.10 How to Create a Dedicated Transport Based Forward

Pool
To create a dedicated transport-based forward pool, execute the following steps:
A window pops-up.
Make sure to set:
– Type: Select Transport Based Service Pool from the drop-down list.
– Access Rights: Set this parameter to Dedicated using the slider.
The parameter Access Rights does not appear when the Access Rights of the
root pool have been set to Dedicated. In that case, the forward pool is
automatically dedicated to the VNO selected in the root pool.

3. Set the general parameters:

– Dedicated to: Select a VNO domain name from the drop-down list to whom this forward
pool is dedicated.
When the Access Rights of the root pool have been set to Dedicated, the
parameter Dedicated is automatically dedicated to the VNO selected in the root
pool.
4. Set the shaping parameters:

data rate distribution as long as the total available data rate is not exceeded.
– PIR: PIR or Peak Information Rate defines the upper data rate limit.
The selected shaping mode at root pool level will influence the unit used for
CIR/PIR: if Bit Rate Shaping is selected, then the unit is in Mbps; if Symbol Rate
Shaping is selected, the unit is Mbaud.
– Weight: This is the weight assigned to the pool. The weight is an integer value between 1
and 1000 and is used to define the Total Weight, which equals PIR * Weight. The total
weight is used as a ratio mechanism for "fair" distribution of additional capacity after CIR is
applied. The total weight is also used in case of CIR overbooking.
overbooking is by default disabled. When enabled, the total CIR used by the terminals may
exceed the CIR rate of the forward pool.
5. Click Confirm to accept the changes or Cancel to discard the settings.
When confirmed, the pool is added to the QoS plan.

Click to view the details of the forward pool.
Click to delete the forward pool.

6.11 How to Create a Shared Transport Based Forward Pool

To create a shared transport-based forward pool, execute the following steps:
A window pops-up.
Make sure to set:
– Type: Select Transport Based Service Pool from the drop-down list
– Access Rights: Set this parameter to Shared using the slider.
automatically dedicated and you cannot create shared pools.


– Domains: Select the VNO domains from the drop-down list who share this forward pool. At
least one VNO needs to be selected.
Click to view the details of the forward pool.
Click to delete the forward pool.
6.12 How to Create a Dedicated Class Based Forward Pool

To create a dedicated class-based forward pool, execute the following steps:

A window pops-up.
Make sure to set:
– Type: Select Class Based Service Pool from the drop-down list
automatically dedicated to the VNO selected in the root pool.


– Dedicated to: Select a VNO domain name from the drop-down list to whom this forward
pool is dedicated.
pool.

The rates can be set for the forward pool and per QoS pool within the forward pool. For the
real-time QoS pools, CIR equals PIR. The best-effort QoS pool only uses PIR.
When confirmed, the forward pool and QoS classes are added to the QoS plan.
Click to view the details of the forward pool or QoS class.
Click to edit the parameters of the forward pool or QoS class.
Click to delete the forward pool or a QoS class.

6.13 How to Create a Shared Class Based Forward Pool

To create a shared class-based forward pool, execute the following steps:
A window pops-up.
Make sure to set:
automatically dedicated and you cannot create shared pools.


– Domains: Select the VNO domains from the drop-down list who share this forward pool. At
The rates can be set for the forward pool and per QoS pool within the forward pool. For the
real-time QoS pools, CIR equals PIR. The best-effort QoS pool only uses PIR.

When confirmed, the forward pool and QoS classes are added to the QoS plan.
Click to view the details of the forward pool or QoS class.
Click to edit the parameters of the forward pool or QoS class.
Click to delete the forward pool or a QoS class.
Click on the forward pool to add a dedicated QoS class.
6.14 How to Configure a Key Encryption Key

When the AES-256 feature is active in the forward link, the involved keys are stored persistently and
encrypted in the modulator. It is not possible to re-use keys by copying them from a device to
another. To configure the Key Encryption Key or KEK, execute the following steps:
1. Open the web interface of the MCM7500.
Select the modulator via the surveyor tree of the NMS GUI. The modulator can be found
under the Physical Devices / DP-x. Click the MOD and then click WebInterface in the card
navigation pane or via the drop-down box at the top left corner of the card pane.
The following screen appears:

2. Log in as expert:
• Username = expert
• Password = expertexpert
3. Click Tree View. Click AES GCM Scrambler. The following screen appears:

4. Click the Edit button to set a KEK.
5. Set the correct KEK and click Update. The KEK is stored persistently on the modulator.
6. To change the KEK afterwards, it is mandatory to reboot the device to update the KEK.

Manage Return Link Resources
7 Manage Return Link Resources

The return link is defined as the link from the terminals over the satellite to the hub. The return link in
Newtec Dialog supports following access and coding & modulation technologies:
• 4CPM MF-TDMA
• DVB-S2 and S2-Extensions SCPC
• HRC SCPC and Mx-DMA
• MRC NxtGen Mx-DMA
A return link technology can be disabled during installation, or using the

customerconfig.yaml file. For more information about disabling return link technologies,
refer to the relevant Newtec Dialog Hub Module Installation Guide.
The access technology allocates the return link resources to the terminals. The coding and
modulation technology transforms the data into a satellite signal.
The Dialog platform allows terminals to easily switch from one return technology to another. Having
the choice between the return technologies in a network within a single modem guarantees network
operators a business model with maximum flexibility in supported applications, responsiveness to
new market opportunities and Service Level Agreement or SLA schemes that fit customers’ needs.

The supported return technologies depend on the type of modem:
Modem Type SCPC MF-TDMA Mx-DMA NxtGen Mx-DMA
MDM2010 X X
MDM2200 X
MDM2210 X
MDM2500 X
MDM2510 X X X
MDM3100 X X
MDM3300 X X X

MDM3310 X X X X
SMB3310 X X X X
SMB3315 X X X X
MDM5000 X X X
MDM5010 X X X X
7.1.1 4CPM MF-TDMA

4CPM or Quaternary Constant Phase Modulation is a return link technology that allows to
saturate the outdoor unit without generating distortion (in other words allowing a transmitter to
operate in full saturation).
MF-TDMA or Multi Frequency - Time Division Multiple Access is a bandwidth allocation
mechanism, dividing the return link capacity in frequency and time. Consequently remote terminals
are assigned time-slots spread over multiple frequencies which they use to send their data. Time-slot
assignment is regulated by a so called "burst time plan", which is calculated by a device in the hub
based upon capacity requests coming from the remote terminals.
As capacity requests are random or on-demand, MF-TDMA uses the concept of statistical
multiplexing. This means dynamic allocation of resources based on analyzed statistics such as peak
data rates and percentage of time a terminal is sending/receiving data. In other words a terminal is
assigned time-slots according to priority and need.
The return link resources are defined per satellite network. The MF-TDMA return traffic carriers in
the Dialog system are organized in return capacity groups. They are artificial frequency sections of
the total return link spectrum of the beam. A beam is a geographical area that sends its return signal
via a certain satellite transponder.
A Return Capacity Group (RCG) is segmented into Carrier Pools. Carrier pools are artificial
frequency sections of the total spectrum of the RCG. Each carrier pool consists of traffic or TRF
carriers with the same carrier spacing and associated modulation and coding (known as MODCOD)
and is characterized by a minimum and maximum C/N0 or Carrier to Noise ratio. The type and
number of TRF carriers depends on your link budget.
Each satellite network has a number of Common Signaling Channel or CSC carriers, which are
used to transmit the logon bursts from the terminals. When logging on to the network, there are no
specific CSC slots assigned to the terminal. The terminal chooses on which CSC slots to bursts.
It is advised to use the same type of CSC carrier per satellite network.

When using CPM as return technology, the synchronization coverage and the satellite position
determine the area in which terminals are able to logon to the network.
The Dialog platform has two TBTPs or Terminal Burst Time Plans:
• With a guard time for CSC bursts of 22 ms resulting in a normal synchronization coverage.
• With a guard time for CSC bursts of 45 ms resulting in an extended synchronization coverage
(also known as 'Extended Footprint').
Because of a larger guard time, the CSC slots are longer but then less CSC slots can be put in one
carrier. To have a same capacity (compared with the normal synchronization coverage) more
carriers are required, thus more satellite bandwidth is required, resulting in a higher cost for the Hub
Network Operator or HNO.
4CPM is sensitive to adjacent channel interference (ACI). This means that the slot assigned to
one terminal is interfered by another terminal bursting on a slot at the same time on an adjacent
carrier and vice-versa. The higher the difference in C/N0 of the two terminals, the higher the ACI.
Typically lower 4CPM MODCODs are less sensitive to ACI than higher MODCODs. To limit ACI, a
maximum C/N0 per return carrier pool should be defined. For each bandwidth/MODCOD
combination, default minimum and maximum C/N0 values are defined to find a balance between the
dynamic range of the carrier pool and the ACI degradation.
It is advised to use the default C/N0 thresholds for the carrier pools.
When changing the thresholds, keep in mind that:

• The different carrier pools defined in the RCG should form a contiguous region in the C/N0
domain.
• Setting the minimum C/N0 too low can lead to lost volume due to allocated time slots that "weak"
terminals cannot use.

• Setting the maximum C/N0 too high can lead to lost volume due to high ACI imposed on weaker
terminals.
Demodulation of the return link carriers is done by one or more Burst Demodulators (BDM). If
multiple BDMs are present in the satellite network, it is advised to spread the return carriers over
them.
Three types of BDMs are supported:
• NTC2291
• MCD7000
• MCD7500
A BDM has following configuration limitations:
NTC2291 / MCD7000 / MCD7500 24 MHz MCD7000/MCD7500

MCD7500 16 MHz 48 MHz
Processing 16 MHz 24 MHz 48 MHz

capability
Input frequency 950 - 2150 MHz 950 - 2150 MHz 950 - 2150 MHz
IP throughput 22.16 Mbps 33.24 Mbps 45.97 Mbps

capability per BDM
Max number of 80 144 144

carriers per BDM
Rx channels per 4 * 4.096 MHz 3 * 8 MHz 3 * 16 MHz

BDM
BDM 1 or 2, total max 4.096 1 or 2 or 3, total max 1,2 or 3

channels/carrier MHz 8 MHz 16 MHz when only
groups per RX TRF sots
channel 8 MHz when TRF +
CSC
Supported TRF carrier: MODCOD 0 TRF carrier: TRF carrier: MODCOD

MODCODs -5 MODCOD 0 - 5 0-5
CSC carrier: MODCOD CSC carrier: CSC carrier: MODCOD
0, 1 MODCOD 0, 1 0, 1

Carriers per carrier 10 carriers 128 kHz TRF 16 carriers 128 kHz 16 carriers 128 kHz
group, single or CSC TRF or CSC TRF or CSC
MODCOD 10 carriers 192 kHz TRF 16 carriers 192 kHz 16 carriers 192 kHz
10 carriers 256 kHz TRF TRF TRF
or CSC 16 carriers 256 kHz 16 carriers 256 kHz
10 carriers 384 kHz TRF or CSC TRF or CSC
8 carriers 512 kHz TRF or 16 carriers 384 kHz 16 carriers 384 kHz
CSC TRF TRF
5 carriers 768 kHz TRF 16 carriers 512 kHz 16 carriers 512 kHz
TRF or CSC TRF or CSC
4 carriers 1024 kHz TRF
or CSC 10 carriers 768 kHz 10 carriers 768 kHz
TRF TRF
2 carriers 1536 kHz TRF
8 carriers 1024 kHz 8 carriers 1024 kHz
2 carriers 2048 kHz TR or
CSC
1 carrier 2560 kHz TRF
TRF TRF
1 carrier 3072 kHz TRF
1 carrier 3584 kHz TRF TRF or CSC TRF or CSC
1 carrier 4096 kHz TRF 3 carriers 2560 kHz 3 carriers 2560 kHz
or CSC TRF TRF
TRF TRF
TRF TRF
Within a BDM channel, all carriers must have the same carrier type and should be adjacent in
frequency. The IP throughput per BDM may not be exceeded.
The more carrier types you have in a return capacity group, the more channels this will require,
potentially limiting the throughput of the return capacity group. Choosing less carrier types can
however lead to a less optimal MODCOD distribution.
All carriers of a return capacity group should be processed on the same BDM. One BDM can handle
one or more return capacity groups.
A terminal can be scheduled each super frame (every 1/6th of a second) to a traffic carrier in
another, optimal carrier pool.
Adaptive Return Link or ARL assigns terminals to a return link carrier with a symbol rate and
MODCOD, which are appropriate for the terminals' link condition
ARL uses a dynamic margin, which is dependent on the number and age of the C/N0 samples in the
return link. Measurements based on fewer or aged samples have a higher uncertainty and will
therefore result in a higher margin. This dynamic margin is configured via the ARL states.
For each ARL state it is possible to define:
1. Kalman gain K (averaging factor)
2. Margin for covering C/N0 measurement uncertainty
3. Min Interval (in superframes) for going up to next lower state
4. Max interval (in superframes) for going down to next higher state
We recommend using the default values.

A Return Carrier Pool also has a minimum and maximum C/N0 defined.
C/N0,min and C/N0,max depend on following values:
• System margin, typical values are:
– C-band: 0.5 dB
– Ku-band: 1 dB
– Ka-band: 1.5 dB
• C/N,allowed: C/N achieved for carrier with maximum allowed PSD (PEB = allocated BW), as
derived from link budget.
• C/N0,threshold: fixed specifications of a demodulator.
And should be calculated as follows:
• C/N0,min = C/N0,threshold + system margin + 0.5 dB
• C/N0,max = min{C/N0,min + 3 dB , C/N,allowed + 10log(carrier spacing)}
A terminal will only be allocated to carrier pool if: C/N0,min ≤ C/N0,calc ≤ C/N0,max, where
C/N0,calc equals the C/N0 value measured at the terminal (C/N0,meas) minus the dynamic margin.
For example: we have two terminals T1 and T2. Terminal 1 sends regular bursts, while Terminal 2
just sent his first burst. Both terminals have a measured C/N0 value that allows them to receive time
slots from Carrier Pool 1, but because the scheduler has a higher uncertainty for T2, it will apply a
bigger margin than T1. Consequently T1 will get time slots in Carrier pool 1, and T2 gets time slots
allocated in Carrier Pool 2 (which has a lower MODCOD than Carrier Pool 1). If T2 would send
regular bursts as well, the margin will become smaller and it will move up to Carrier pool 1.
7.1.2 DVB-S2 and S2 Extensions

For services requiring high speed return links from the terminals, such as broadcast contribution, IP
trunking or backhauling services, DVB-S2 and S2 Extensions can be used.
S2 Extensions is a bundle of improved candidate technologies prior to the launch of

DVB-S2X in February 2014. S2 Extensions has increased granularity in MODCODs, and
offers linear and non-linear MODCODs.
The access technology that is used with DVB-S2 and S2 Extensions is SCPC. A Single Channel Per
Carrier or SCPC carrier can be considered as an always-on, dedicated, high-bandwidth
communication channel that provides high efficiency. The symbol rate of an SCPC carrier ranges
can go from 1 Mbaud up to 20 Mbaud (MDM3x00), or up to 64 Mbaud (MDM3310 and MDM5000),
or up to 133 Mbaud (MDM5010).

In this mode terminals are assigned to an SCPC carrier with fixed center frequency and symbol
rate. The SCPC carrier must fit into the S2 return capacity group. The S2 return capacity group is
a continuous frequency slot defined by a minimum and maximum frequency. An S2 return capacity
group can have up to three SCPC carriers. The carrier should all fall within this slot and they should
not overlap.
Following demodulators support SCPC DVB-S2 and SCPC S2 Extensions:
• MCD6000
• MCD7000
7.1.3 High Resolution Coding™

High Resolution Coding™ technology has a similar efficiency as DVB-S2 but is optimized for lower
rate return links. Because of the small baseband frame size it does not add extra latency.
The demodulators that support HRC are listed below.
• MCD6000 with a maximum baudrate per carrier of 5 Mbaud and an input bandwidth of 36 MHz.
• MCD7000 with
– A maximum baudrate per carrier of 5 Mbaud and an input bandwidth of 36 MHz.
OR
• MCD7500_HRC with
OR
• MCD7500_HRC68 with a maximum baudrate per carrier of 68 Mbaud and an input bandwidth of
72 MHz.
HRC works with frequency slots. A frequency slot has a start and stop frequency and acts as a
frequency window in which HRC carriers are deployed. HRC demodulator are assigned to a
frequency slot. An HRC demodulator can only be assigned to one frequency slot, but multiple
demodulators can be assigned to the same frequency slot. A frequency slot can combine different
demodulator role types. The combinations are however limited to:
• HRC 5 Mbaud / 36 MHz only. In this case, the maximum frequency slot bandwidth is 36 MHz.
• HRC 20 Mbaud / 72 MHz and 68 Mbaud / 72 MHz. In this case, the maximum frequency slot
bandwidth is 72 MHz.
Within the HRC frequency slots, you will define the HRC return capacity groups.
HRC can be used with two types of access technologies:
• SCPC
• Mx-DMA
The main difference between SCPC and MxDMA is the frequency and symbol rate allocation. In
SCPC, the terminal gets a fixed transmit frequency and symbol rate during provisioning. In Mx-DMA,
the HRC return capacity group is further divided into return pools and the terminal is assigned to a
return pool during provisioning. The HRC controller decides which frequency and symbol rate the
terminal can use to transmit data. This resource allocation can change every frame (second).
It is possible to mix HRC SCPC and HRC Mx-DMA return capacity groups on the same HRC
demodulator.

7.1.3.1 HRC SCPC
In this mode terminals are provisioned in an HRC return capacity group and are assigned to an
SCPC carrier with fixed center frequency and symbol rate. Operation of the HRC SCPC mode is
similar to the DVB-S2 SCPC return mode. Compared to DVB-S2 and S2 extensions, the HRC
modulation in SCPC mode is perfectly suited for applications requiring low to medium return
throughput rates (for example professional VSAT, low/medium rate broadcast), while assuring
excellent delay and jitter performance.
The HRC SCPC return link can provide carrier symbol rates from:
• 30 kbaud up to 5 Mbaud, in 31 kbaud granularity steps for MCD6000/MCD7000/MCD7500_HRC
5 Mbd / 36 MHz.
• 30 kbaud up to 20 Mbaud, in 31 kbaud granularity steps for MCD7000/MCD7500_HRC 17 Mbd /
70 MHz.
• 30 kbaud up to 68 Mbaud, in 31 kbaud granularity steps until 20 Mbaud and in 123 kbaud steps
from 20 Mbaud onwards for MCD7500_HRC68.
Combined with a very extensive range of MODCODs from QPSK up-to 32APSK, this results in
carrier throughputs:
• Up to 20 Mbps for for MCD6000/MCD7000/MCD7500_HRC 5 Mbd / 36 MHz.
• Up to 70 Mbps for MCD7000/MCD7500_HRC 17 Mbd / 70 MHz.
• Up to 225 Mbps for MCD7500_HRC68.
7.1.3.2 HRC Mx-DMA
Mx-DMA return link technology brings together the best of 2 traditionally isolated worlds: it combines
the flexibility and statistical multiplexing of MF-TDMA access technologies and the efficiency of
SCPC technologies.
The key characteristics of Mx-DMA are:
• Carrier symbol rates from:
– 30 kbaud up to 5 Mbaud, in 31 kbaud granularity steps for
MCD6000/MCD7000/MCD7500_HRC 5 Mbd / 36 MHz.
– 30 kbaud up to 20 Mbaud, in 31 kbaud granularity steps for MCD7000/MCD7500_HRC 17
Mbd / 70 MHz.

– 30 kbaud up to 68 Mbaud, in 31 kbaud granularity steps until 20 Mbaud and in 123 kbaud
steps from 20 Mbaud onwards for MCD7500_HRC68.
and combined with a very extensive range of MODCODs from very low SNR (VL-SNR) QPSK
up to 32 APSK with 5% roll-off, resulting in carrier throughputs:
– Up to 20 Mbps for for MCD6000/MCD7000/MCD7500_HRC 5 Mbd / 36 MHz.
– Up to 70 Mbps for MCD7000/MCD7500_HRC 17 Mbd / 70 MHz.
– Up to 225 Mbps for MCD7500_HRC68.
• Dynamic and on-demand carrier bandwidth allocation, including advanced and flexible multi-level
QoS model by the central hub HRC scheduler results in very good statistical multiplexing,
optimized carrier configuration for each terminal and maximal throughput and efficiency of the
allocated satellite bandwidth.
• The dynamic carrier scheduling is combined with excellent jitter, delay and PER (Packet Error
Correction) performance.
• Includes AUPC, ACM (always enabled), ThiMM technologies resulting in very high link availability.
As a result the HRC Mx-DMA technology provides an efficient access scheme for many applications:
backhauling, enterprise/corporate networking, fast news gathering, government services,…
When using HRC Mx-DMA, the bandwidth resources are allocated to logged on terminals. Every PL
(physical layer) frame and for each logged in terminal, the HRC controller in the hub needs to
determine the following parameters:
• Symbol rate
• MODCOD
• Transmit power
• Transmit frequency
The PL frame has a fixed duration of 1 second.
7.1.3.3 Capacity Troubleshooting
It is recommended to provision a dedicated HRC SCPC return capacity group of at least 200 kHz for
troubleshooting purposes next to the operational HRC return capacity groups. This additional
amount of capacity also needs to fit in the HRC frequency slot.
You can use this troubleshooting RCG to:
• Take a closer look at malfunctioning terminals, which is otherwise difficult as every second a
terminal transmits at a different frequency. Creating an HRC SCPC RCG which has the same
bandwidth as the symbol rate of the transmitting terminal (which is advised to be set at 185 kbaud)
makes it a lot easier to troubleshoot a terminal (as it will not "jump" from one frequency to another
every second).
• Verify line up settings of a terminal in case the line up step via installation carrier by local installer
was never actually performed.
• Have a terminal transmit a pure carrier for a limited time (for example to verify cross-polar
components or frequency stability).
7.1.4 MRC NxtGen Mx-DMA
The MCD7500 demodulator supports MRC NxtGen Mx-DMA.

Next Generation Multiple Dimension Division Multiple Access - Multi Resolution Coding or
NxtGen Mx-DMA MRC is a Next Generation, flexible satellite return technology.
NxtGen Mx-DMA access technology cross-correlates and assigns frequency, symbol rate, power,
modulation and coding rate, transmission length and code length in real-time, basing on the return
traffic demand, QoS management parameters and channel conditions. Therefore, designing a
NxtGen Mx-DMA MRC link does not require precise knowledge of the traffic and terminal mix as the
link self-optimizes in real-time. The high efficiency enables bandwidth savings, higher throughput,
better network availability, and substantial terminal cost savings. NxtGen Mx-DMA is used with
MRC. In Multi Resolution Coding or MRC, multiple channel coding options are available per
setting. The MRC Controller chooses the optimal structure of a burst for each demand
In NxtGen Mx-DMA, the return link capacity is divided in time and frequency. Terminals are assigned
transmission slots, which they use to send data. This assignment is scheduled in a Time-Frequency
Plan, which is calculated by the MRC Controller or MRCCTL, based upon capacity requests from
the terminals, QoS parameters and channel conditions. The MRCCTL is a virtual machine in the
hub.
In the image below, a time-frequency plan example of a NxtGen Mx-DMA MRC signal is visualized.
Each NxtGen Mx-DMA frame of 40 ms is divided into time slots of 5 ms. Each 5 ms slot contains
multiple segments. A segment is a portion in the frequency domain. Hence, two different segments
can have the same time duration but a different frequency bandwidth.
A transmission slot from a terminal is denoted a burst. The shortest burst duration is the slot
duration.
This time-frequency usage per terminal is very adaptive and it can adjust to the characteristics of the
traffic:
• In the case of bursty traffic (T2 and T3 in the image), terminals transmit in time-frequency slots.
The duration of the burst is a multiple of a slot duration.
• In case of continuous traffic (T1 in the image), bursts can be expanded in time, avoiding the use
of multiple slots, and as a consequence, decreasing overhead. This is especially useful for
services which require low jitter. For example, mobility application and cellular backhaul.
Terminals which are not transmitting do not get any bandwidth allocated. Therefore, there can be
slots where no traffic is present. This flexible frequency grids prevents stuffing overhead. The carrier
size that can be allocated to a transmitting terminal is between 110 kHz and 20 MHz.
NxtGen Mx-DMA avoids padding of bursts. In order to fit any payload length in this granular time
grid without padding, different symbol rates can be chosen.

7.1.5 Adaptive Coding Modulation

Adaptive Coding Modulation or ACM allows modification of the modulation parameters (also known
as the MODCOD) of a satellite signal on the fly, without interrupting the transmission and without
losing data. When combined with a measurement of the instantaneous link conditions every few
seconds and a system that automatically adjusts the modulation parameters when needed, ACM
allows using the highest possible modulation scheme and the lowest possible level of error
correction at all times.
DVB-S2 or S2 Extensions
ACM can be enabled or disabled. This is done at terminal level during provisioning. When ACM is
disabled, the SCPC carrier settings (frequency, symbol rate, modcod and power) are configured
statically. The bit rate is fixed and determined by symbol rate and MODCOD. The power is not
adjusted if it is too high or too low. If the configured MODCOD needs a higher EsN0 than available,
there will be packet loss. When ACM is enabled, the S2 controller is will adjust the power and
MODCOD. The frequency and symbol rate are still statically configured. The bit rate will change as
the MODCOD changes.
HRC
ACM is always enabled for the HRC Mx-DMA return capacity group. ACM can be enabled or
disabled for the HRC SCPC return capacity group. It is disabled by default and the result is the same
as for DVB-S2 (Ext).
Next to setting the minimum and maximum MODCOD per HRC return capacity group, it is also
possible to set the maximum MODCOD on a terminal level. For more information, refer to
Manage Terminal Provisioning on page 232. When operating in HRC Mx-DMA you can also set the
minimum and maximum symbol on a terminal level. This is interesting for terminals operating
with VL-SNR or for keeping terminals, which suffer from phase noise (due to BUC frequency
instability for example) under control. For more information, refer to Manage Terminal Provisioning
on page 232 and Manage Service Profiles on page 198.
MRC
ACM is always enabled for NxtGen Mx-DMA MRC return capacity groups.
Next to setting the minimum and maximum MODCOD per MRC return capacity group, it is also
possible to set the maximum MODCOD on a terminal level. When operating in MRC NxtGen
Mx-DMA you can also set the minimum and maximum symbol on a terminal level. This is
interesting for terminals operating with VL-SNR or for keeping terminals, which suffer from phase
noise (due to BUC frequency instability for example) under control. For more information, refer to
Manage Terminal Provisioning on page 232 and Manage Service Profiles on page 198.
7.1.6 Return QoS Shaping

The shaping tree is different for the different return link technologies.
MF-TDMA 4CPM / Mx-DMA HRC / NextGen Mx-DMA MRC

The return capacity group is divided into different return pools. The return pools can be class-based
or transport-based, and dedicated to a VNO or shared by multiple VNOs. The class-based pools are
further divided into QoS pools. Terminals are either linked to a return pool (in case of a
transport-based model) or to the QoS pools (in case of a class-based model).
For multicast traffic in the return, the terminal multicast circuits are handled like QoS classes in case
of class-based shaping. In case of transport-based shaping, the multicast circuits are at the same
level as the terminal circuits.

This results in the following return shaping tree.

• Shaping Level 1: At this level the capacity of the return capacity group is represented.
• Shaping Level 2: At this level the return capacity group is divided over return pools. The return
pools can be class-based or transport-based, and dedicated to a VNO or shared by multiple
VNOs.
• Shaping Level 3: In case the return pool is class-based, shaping level 3 represents the QoS
pools. In case of transport-based return pools, shaping level 3 represents the terminal circuits and
terminal multicast circuits (if any).
• Shaping Level 4: This shaping level represents the QoS classes. At this level the class-based
terminal circuit is also defined by a PIR value.
In case of HRC Mx-DMA and NextGen Mx-DMA MRC, you also have a free capacity pool at
shaping level 2. This free capacity is the capacity of the return capacity group that is left after the
capacity requests of all terminals have been fulfilled. The distribution of free capacity can be enabled
or disabled for the return capacity group. When enabled, the return controller hands out the free
capacity and a terminal can get more bandwidth than requested. The terminal can even get more
capacity than its configured PIR as the free capacity is not taken into account for PIR. When disabled
only the requested capacity is distributed and any remaining capacity in the return capacity group is
not used and therefore lost. Free capacity distribution is by default enabled. The free capacity pool
has a CIR equal to 0 Mbps and has a configurable PIR between 0 and 250 Mbps (default value is
150 Mbps). The pool has lower priority (priority 99) than the class-based and transport-based pools
(priority 0).
SCPC HRC / SCPC S2

SCPC HRC and S2 do not use the concept of return pools. Terminals are linked to an SCPC circuit.
These circuits use the weight parameter in case of congestion.

• Shaping Level 1: At this level the capacity of the return capacity group is represented.
• Shaping Level 2: At this level the return capacity group is divided over always-on SCPC carriers.
One terminal is linked to one SCPC carrier.
• Shaping Level 3: In case of class-based shaping, shaping level 3 represents the QoS classes. In
case of transport-based shaping, shaping level 3 represents the terminal circuits. This shaping
level also represents the terminal multicast circuits.
• Shaping Level 4: In case of transport-based shaping, shaping level 4 represents the QoS
classes.
From a configuration point of view, following provisioning interfaces are involved:

• The root pool, return and QoS pools are configured in the Return QoS Plan. This is explained in
this chapter.
• The terminal circuits and QoS classes are configured in the Service Profile. For more information
about service profiles, refer to Manage Service Profiles on page 198.
• The terminal multicast circuits are configured during Terminal Provisioning. For more
information, refer to Multicast on page 337.
The parameters that are used to control the use of bandwidth at the different shaping levels are:
• PIR: The Peak Information Rate or PIR is the maximum unicast traffic rate.
• CIR: The Committed Information Rate or CIR is the guaranteed or minimum unicast traffic rate.
The Committed Information Rate can be overbooked, meaning that the sum of all CIR values of
the child nodes exceeds the CIR value of the parent node.

Always pay attention when using CIR overbooking as this can have an impact on
the data rate a terminal receives. By enabling CIR overbooking the rate is no longer
guaranteed and can be less than expected (see example below).
CIR overbooking should only be applied if one can predict the average number of
concurrent capacity requests.
• Weight: The weight is an integer value between 1 and 1000 and is used to define the Total
Weight, which equals PIR * Weight. The total weight is used to distribute the available bandwidth
among nodes at the same level and with the same priority.
Other fundamental shaping parameters are:
• Priority (static): Priority is defined by the QoS class.
– RT1 = prio 1 (highest)
– RT2 = prio 2
– RT3 = prio3
– CD1..14 = prio 5
– BE = prio 6 (lowest)
Prio 4 is used for control traffic.
• Shaping Volume (dynamic): This is the actual capacity need of a terminal. The capacity requests
are triggered by the ingress traffic on the modem's LAN interface.

7.1.7 Frequencies
When defining the transponder and return link several frequencies need to be set.
The modem transmits the return link signal at an L-band frequency. The Local Oscillator or LO of the
outdoor unit (ODU) of the remote terminal transforms the modem frequency into an RF frequency,
which is received by the satellite transponder. The satellite applies a delta frequency to convert the
uplink frequency into the downlink frequency, which is received by the LNB of the hub. The LNB
transforms the downlink frequency into an L-band frequency used by a demodulator within the hub.
The LO frequency value of the ODU of the remote terminal is visible and editable via
the GUI of the remote modem.

7.2 Setup of Return Link Resources


the modulators, demodulators and number of HPSs.
configuration, refer to the specific Newtec Dialog Hub Installation Guide.
which terminals are serviced.
For more information about how to create the logical satellite network and beam, refer to
Manage General Satellite Resources on page 11.
A satellite network is defined by a return resources.
Assuming that the hardware of the satellite network is installed and configured, that the beam and
logical satellite network have been created, following sequence of steps should be executed:
1. Create a transponder.
2. Create a return link, which is linked with the previously created transponder.
3. Link the return carrier with the logical satellite network.
When the return link has been created, the return frequency plan and QoS plan can be defined.
7.3 How to Open the Return Resources Web Interface

To open the provisioning interface of the Return Resources, execute the following steps:

4. From here:
– You can click Transponder Provisioning in the surveyor tree or visual overview.

7.4 How to Create a Transponder for the Return Link

To create a transponder, execute the following steps:
1. Follow the steps as described in How to Open the Return Resources Web Interface on page 90.
2. Click + Create New Transponder in the Transponder Provisioning interface. The following
window appears.

– Delta Frequency: This is the shift in MHz from uplink to downlink frequency within the
transponder. This value is typically provided by the satellite operator. To know which exact
frequency is meant, refer to Frequencies on page 88.
– Saturated Flux Density: Optional parameter. The Saturated Flux Density or SFD is the
Power Flux Density or PFD received by the transponder from a given point in the beam
coverage, which drives the transponder into saturation. This parameter is used to define a
transponder-specific transmit power during logon of mobile terminals using NxtGen
MX-DMA MRC or Mx-DMA HRC return technology.
– Input Back Off: Optional parameter. Back-off value in dB applied to the SFD to avoid
interference and distortion caused by multiple carriers. In the return link, transponders are
typically operated by multiple carriers. The maximum allowed total PFD at the transponder
is SFD - IBO. The IBO is determined by the HPA non-linear transfer characteristics. This
parameter is used to define a transponder-specific transmit power during logon of mobile
terminals using NxtGen MX-DMA MRC or Mx-DMA HRC return technology.
For more information about the transponder-specific transmit power during

logon of mobile terminals, refer to How to Configure Modem Settings on page
235.
– Non Linear Predistortion: This feature is not applicable to transponder used for the return
link.
messages.
Click on the transponder in the overview to edit the parameters.
Click to delete the transponder.
7.5 How to Create a Return Link
You can only create a return link if a transponder is configured.
To create a return link, execute the following steps:

1. Open the Return Resources web interface as described in
How to Open the Return Resources Web Interface on page 90.
2. Click + Create in the General Overview interface. Or click Return in the General Overview
interface. If the return link has not been created, the interface displays the available
transponders. You are only able to create a return link when there is at least one transponder
available. The interface also allows you to add transponders.
3. Configure the return link parameters.


– Satellite Network: This is the identifier of the satellite network that is served by this return
link.
– Transponder: Select the identifier of the transponder, which is used by this return link.
– Rx Interfaces: This setting is only available for XIF hub modules. Select the receiving
interfaces on the RF matrix, which are used for this return link. The RX interface is set
during the hub module installation and can be checked via the Hub Module Provisioning on
page 269 interface.
– Hub Delta Frequency: This is the difference between the frequency of the downlink signal
coming from the satellite and the L-band frequency entering the demodulator. To know
which exact frequency is meant, refer to Frequencies on page 88.
– Up-link Polarization Type: Select the polarization of the return link in the uplink. The
return uplink is the link from the remote terminal to the satellite.
– Spectrum Inversion: Click the button to enable or disable spectrum inversion. Spectral
inversion should typically be enabled if the Local Oscillator frequency of the BUC or LNB in
the hub is larger than the RF frequency. Spectrum inversion is B default disabled.
– Site Diversity: Click the button to enable or disable site diversity. Enable site diversity
when there are redundant antennas at the hub side. In that case, the time-slotted return

link technologies (like 4CPM MF-TDMA) become more resilient to signal interruption,
frequency offset changes and time jumps that occur due to switching between antennas.
Site diversity is by default disabled.
– ASI Delta: Set the level of allowed adjacent satellite interference, relative to regulatory limit
applicable for the return link. The value ranges between -20 dB and +20 dB.
– DSCP Values: This defines the internal DSCP values to use for traffic in the different traffic
classes. The values are used when the Packet Marking Mode on page 192 in the
classification profile is set to Mark.
If external DSCP marking on the return link is already applied, it is advised to set
the internal DSCP values equal to the external DSCP values.
messages.
Click in the General Overview interface to edit the parameters.
Click in the General Overview interface to delete the return link.
Click in the General Overview interface to go to the return QoS plan.
Click in the General Overview interface to go to the return frequency plan.
7.6 How to Open the Return Link Frequency Plan

To open the provisioning interface of the Return Link Frequency Plan, execute the following steps:

4. From here, you can access the frequency plan in different ways:

Click next to Return Link to open the return frequency plan.

– You can select the beam identifier and Satellite Network that is used by the return link.
Click Resource Provisioning and then click RN Frequency Plan.

The provisioning interface is displayed. When you have created a return frequency plan, you
can perform following actions in this window:
– Hover over the graphical overview to see details of the different return capacity groups or
carriers.

– Use the focus bar to zoom in on the frequency plan. Click the Focus check box to show or
hide the focus bar. When shown, select the area in the focus bar where you want to zoom
in on.
Alternatively, you can double-click on the frequency plan or use the scroll button to zoom
in.
– Click a check box within the legend to change the appearance of the selected item. The
appearance toggles between transparent and non-transparent.

7.7 How to Create an S2 Return Capacity Group

To create an S2 return capacity group, execute the following steps:
1. Open the Return Link Frequency Plan web interface as described in
How to Open the Return Link Frequency Plan on page 95.
2. Select S2 in the top menu bar.
3. Click + Add.
Alternatively, you can click the copy icon in the Actions column to create a new return
capacity group based on the settings of an existing one.

– Start/Stop Frequency: This is the frequency range of the S2 return capacity group or
RCG.
– Domains: Click Link Domains to link one or more VNO domain names to the S2 RCG.
Only VNO domains that are linked can use the S2 RCG for their terminals.

5. Click Confirm to create the return capacity group or Cancel to discard the settings.
6. Click Apply to save the settings or click Discard to discard the settings. Check the log panel for
validation messages.
Click in the Actions column to edit the return capacity group.

To edit the frequency range, you can also right-click on the frequency plan and select
Edit from the pop-up menu. Click and drag the dots to change the start and stop
frequency. Mind that the change is effective immediately.
To delete the RCG click , or right-click on the frequency plan and select Delete
from the pop-up menu.
Always click Apply to save the settings or click Discard to discard the settings.
To create a terminal that uses this RCG, right-click on the frequency plan and select
Add Terminal from the pop-up menu. You are redirected to the Terminal Provisioning
interface. For more information about this interface, refer to
Manage Terminal Provisioning on page 232.
7.8 How to Create an HRC Return Capacity Group

HRC works with frequency slots. A frequency slot has a start and stop frequency and acts as a
frequency window in which HRC carriers are deployed. HRC demodulator are assigned to a
frequency slot. An HRC demodulator can only be assigned to one frequency slot, but multiple
demodulators can be assigned to the same frequency slot. A frequency slot can combine different
demodulator role types. The combinations are however limited to:
• HRC 5 Mbaud / 36 MHz only. In this case, the maximum frequency slot bandwidth is 36 MHz.
• HRC 20 Mbaud / 72 MHz and 68 Mbaud / 72 MHz. In this case, the maximum frequency slot
bandwidth is 72 MHz.
Within the HRC frequency slots, you will define the HRC return capacity groups.
HRC can be used with two types of access technologies:
• SCPC
• Mx-DMA
It is possible to mix HRC SCPC and HRC Mx-DMA return capacity groups within the same frequency
slot.

7.8.1 Create a Frequency Slot

To create an HRC frequency slot, execute the following steps:
2. Select HRC in the top menu bar and then select Frequency Slots in the submenu.
3. Click + Add.

– Name: The arbitrary name should be unique within the domain and only support
– Start/Stop Frequency: This defines the frequency slot in MHz.
– Assigned MCDs: Select one or more HRC demodulator, which should be linked to this
frequency slot. The list is automatically populated based on the demodulators that you have
entered in the Hub Module Provisioning on page 269 interface. An empty list means that
no demodulators are available.

The number of demodulators that can be used per satellite network is limited to
eight.
– MCD Overbooking Allowed: Click the button to enable or disable MCD overbooking. An
HRC demodulator can simultaneously process a limited set of terminals. When enabling
MCD overbooking, you can provision more terminals on the HRC demodulator than the
limit allows. MCD6000, MCD7000 and MCD7500_HRC support a maximum of 24
terminals. The MCD7500_HRC68 supports 12 terminals. MCD overbooking is by default
disabled.
This parameter is typically enabled for beam roaming terminals. Beam roaming
terminals are provisioned in multiple beams but not all terminals will be online in
the same beam.
– Extra Dwell Time: This is an additional logon time for the demodulator to lock on the
PRBS logon sequence sent by the terminal during terminal initialization. This time is added
to the standard 7 seconds to increase the probability for terminals to successfully logon to
the network. This is useful for instance in noisy environments. The value ranges between 0
and 120 seconds. The default value is 0 seconds.
This parameter is only supported on MCD7000 and MCD7500.

–
Click in the Actions column to edit the frequency slot.

To delete the frequency slot click , or right-click on the frequency plan and select
Delete from the pop-up menu.
When you have created the frequency slot, you can create the return capacity group. Depending on
the return access technology, you can create an HRC SCPC return capacity group or an HRC
Mx-DMA return capacity group.
7.8.2 Create an HRC SCPC Return Capacity Group

When the frequency slot is created, you can create the HRC SCPC return capacity group:
1. Select HRC in the top menu bar and then select HRC Return Capacity Groups in the submenu.
2. Click + Add.
A window pops-up.

Make sure to set the Return Technology to HRC SCPC.

– Frequency Slot: Select a frequency slot from the drop-down list.
– Available Frequency Ranges: A frequency slot can be used by multiple HRC RCGs. The
system automatically shows which frequency ranges are still available within the frequency
slot for a new RCG. When you select a free frequency range, the start and stop frequency
are automatically entered.
– Start/Stop Frequency: This is the frequency range of the HRC SCPC return capacity
group. These frequencies must fit in the frequency slot assigned to this RCG. The start and
stop frequency are automatically entered if you have selected an available frequency range
using the previous parameter.
– ACM: Click the button to enable or disable ACM. ACM is by default enabled. When
enabled, the following parameters should be configured:
• Min/Max MODCOD: Select the minimum and maximum MODCOD that can be used
within the HRC return capacity group from the drop-down list.
• Static Margin: An extra margin in dB can be added on top of the nominal MODCOD
threshold, which is used to determine when to switch to another MODCOD. In case
return link efficiency is required, it is advised to set the static margin to zero dB.
• Error Performance Objective: This reflects the mean time between erroneous
seconds in the return link. In case an error-free (robust) link is required, then select the
highest value together with a static margin of for example 2 dB.
It is advised to disable ACM prior to calibration. For more details on return link
calibration, refer to Return Link Calibration on page 282.

– EIRP Tracking Static Margin: This parameter is relevant for terminals for which the Local
Power Control has been enabled. These are typically mobile terminals. A good default
value is 0 dB. This value can be increased in case the local power control limitations are
very jittery and hard to predict by the HRC controller.
– Domains: Click Link Domains to link one or more VNO domain names to the HRC SCPC
RCG. Only VNO domains that are linked can use the RCG for their terminals.

To delete the RCG, click in the Actions column, or right-click on the frequency
plan and select Delete from the pop-up menu.
To create a terminal that uses this RCG, right-click on the graphical view and select
Add Terminal from the pop-up menu. You are redirected to the Terminal Provisioning
interface.
7.8.3 Create an HRC Mx-DMA Return Capacity Group

When the frequency slot is created, you can create the HRC SCPC return capacity group:
1. Select HRC in the top menu bar and then select HRC Return Capacity Groups in the submenu.
2. Click + Add.
A window pops-up.
Make sure to set the Return Technology to HRC Mx-DMA.


– Frequency Slot: Select a frequency slot from the drop-down list.
– Available Frequency Ranges: A frequency slot can be used by multiple HRC RCGs. The
system automatically shows which frequency ranges are still available within the frequency
slot for a new RCG. When you select a free frequency range, the start and stop frequency
are automatically entered.
– Start/Stop Frequency: This is the frequency range of the HRC Mx-DMA return capacity
group. These frequencies must fit in the frequency slot assigned to this RCG. The start and
stop frequency are automatically entered if you have selected an available frequency range
using the previous parameter.
– Logon Mode: Select the logon mode of the terminals using HRC Mx-DMA.The following
logon modes exist:
• Single Carrier Logon
• Logon Bandwidth
Depending on the selected mode, different parameters should be set.
• Logon Symbol Rate: For both logon modes, the logon symbol rate should be
specified. The symbol rate is a multiple of 30.830 kBaud. The larger the symbol rate is,
the faster terminals can log on. However, this rate consumes a part of the overall
bandwidth of the RCG.

The recommended logon symbol rate depends on the use case as shown in the table
below.
Use Case Recommended Logon Symbol Rate (kBd)
Fixed VSAT terminals 123
Mobile maritime terminals 524
Mobile areo terminals 770
In case of Single Carrier Logon, the logon symbol rate becomes available again for
traffic when all terminals have logged on.
In case of Login Bandwidth, the logon symbol rate used depends on the Maximum
Logon Bandwidth and the number of terminals trying to logon. Logon symbol rate that
is not used is available for traffic.

• Maximum Logon Bandwidth: This parameter is only available when the Logon
Mode is Logon Bandwidth and indicates the maximum amount of bandwidth that a
modem can use to logon.
• Universal Logon: This parameter is available when the Logon Mode is Logon
Bandwidth and enables or disables the Ulogon functionality. For more information
about Ulogon, refer to How to Set-Up HRC Mx-DMA Ulogon. Ulogon is supported on
MCD7000/MCD7500_HRC 17 Mbd / 70 MHz demodulators and MCD7500_HRC68 68
Mbd / 72 MHz demodulators. When Ulogon is enabled, the following parameter should
be set:
• Ulogon Channel ID: This is the identifier of the Ulogon channel. The ID should be
unique over all HRC and MRC return capacity groups within a satellite network.
Only integer values are allowed. For more information about the MRC return
capacity group, refer to How to Create an MRC Return Capacity Group on page
110.
– Max Symbol Rate: Every second, which corresponds with the HRC scheduling interval,
Mx-DMA allocates a symbol rate to each terminal associated to the RCG. This symbol rate
is the result of a certain bit rate need, which is based on QoS, CIR and capacity requests,
and the available SNR (see Return Link Calibration on page 282). The system can hand
out “free capacity” if more bandwidth is available on the RCG than needed for the sum of
requested capacity. Terminal carrier sizes will inflate to offer more “free” bit rate to the
terminals. For some installations with ODU power limitations this may not always be a good
idea. The artificial bit rate may drive terminals to high symbol rates, and thus to high power
levels. These can sometimes become so high that the terminal is forced to operate in lower
modulation schemes (lower efficiency) in order to limit the out-of-band spectral regrowth. A
similar thing can happen if a terminal asks for more bit rate than is actually healthy given
the ODU power, the antenna size, the place of the terminal in the beam footprint etc.
For all of these reasons, it is possible to limit the maximum bandwidth that terminals can
consume. However, if you do not have any reason to limit the bandwidth it is good practice
to set the maximum symbol rate to:
• Close under 5 Mbaud if MCD6000/MCD7000/MCD7500_HRC 5 Mbd/32 MHz
demodulators are used;
• Close under 20 Mbaud if MCD7000/MCD7500_HRC 17 Mbd / 70 MHz demodulators
are used;
• Close under 68 Mbaud if MCD7500_HRC68 68 Mbd / 72 MHz demodulators are used;
and let the Mx-DMA HRC algorithms freely decide what symbol rates can be used.
The maximum symbol rate should be supported on the demodulator role type.
– Min/Max ModCod: These are ACM-related parameters and define the minimum and
maximum MODCOD that can be used within the RCG. ACM is always enabled for HRC
Mx-DMA.
The QPSK3/10 MODCODs with SF number are very low or VL-SNR MODCODs. VL-SNR
MODCODs allow HRC Mx-DMA terminals with an Es/No value as low as -6 dB to be
operational. The -6 dB limit is due to logon constraints. At terminal level, you can enable
Extended VL-SNR allowing to handle HRC Mx-DMA logons as low as -12 dB. Extended
VL-SNR requires that ulogon is enabled for the RCG. For more information about extended
VL-SNR, refer to Manage Terminal Provisioning: How to Configure Service Settings on
page 240.
When selecting a VL-SNR MODCOD as minimum MODCOD, the symbol rates in the GUI
refer to chip rates, and correspond with SF * n * 30.8 kBaud, with n an integer number. This
has an effect on the minimum value that you can select for the Logon Symbol Rate.

– Static Margin: An extra margin in dB can be added on top of the nominal MODCOD
threshold, which is used to determine when to switch to another MODCOD. In case return
link efficiency is required, it is advised to set the static margin to zero. This is an
ACM-related parameter. ACM is always enabled for HRC Mx-DMA.
– Error Performance Objective: This is an ACM-related parameter and reflects the mean
time between erroneous seconds in the return link. In case an error-free (robust) link is
required, select the highest value together with a static margin of e.g. 2 dB. ACM is always
enabled for HRC Mx-DMA.
– EIRP Tracking Static Margin: This parameter is relevant for terminals for which Local
Power Control has been enabled. These are typically mobile terminals. A good default
value is 0 dB. This value can be increased in case the local power control limitations are
very jittery and hard to predict by the HRC controller.
– Free Capacity: Click the button to enable or disable the distribution of free capacity. When
enabled, the HRC controller hands out the capacity of the RCG that is left after the capacity
requests of all terminals have been fulfilled and a terminal can get more bandwidth than
requested. The terminal can even get more capacity than its configured PIR as the free
capacity is not taken into account for PIR. When disabled only the requested capacity is
distributed and any remaining capacity in the return capacity group is not used and
therefore lost. Free capacity distribution is by default enabled.
We recommend to keep free capacity distribution enabled.

When disabled, the modem can experience packet loss at the start of return
transmission. This is the result of the modem data queue overflow caused by
the fact that the HRC controller needs several seconds to assign capacity to the
modem. When the capacity is assigned, the modem queue will be emptied in a
slow pace resulting in delays.
Only disable free capacity distribution in specific use cases.
The introduction of Flow Fairness may require customers upgrading from Dialog
R2.2.3 or lower to review and adapt the configuration to ensure that
time-sensitive applications are allocated with the right priority. For this reason it
is recommended to keep Free Capacity always enabled. It should only be
disabled for testing or troubleshooting purposes. For more information, refer to
the Newtec Dialog Functional Description.
The amount of free capacity to distribute is limited by a PIR value:

• Free Capacity PIR: This parameter is only available when free capacity distribution is
enabled. The Peak Information Rate or PIR value limits the amount of free capacity to
distribute. The value ranges from 0 Mbps to 250 Mbps. The default value is 150 Mbps.
Mind that the actual peak rate of the free capacity cannot exceed the peak rate of the
HRC return capacity group.
– Carrier Randomization: Click the button to enable or disable carrier randomization.
Carrier randomization can be used to spread the effect of a jammer in the return link over
multiple terminals in the HRC return capacity group. When carrier randomization is
enabled, the TX frequency of the terminal is regularly changed, making sure that a jammed
TX frequency is used by different terminals. Carrier randomization is disabled by default.
• Reordering Delay: When carrier randomization is enabled, the reordering delay can
be set to a value between 1 sec and 3600 sec. The reordering delay is the time
between two TX frequency changes. The default value is 5 seconds.


To delete the RCG, click in the Actions column, or right-click on the frequency
plan and select Delete from the pop-up menu.
Click in the Actions column to go to the return QoS plan.

7.9 How to Create an MRC Return Capacity Group

The return link resources are defined per Satellite network. The NxtGen Mx-DMA MRC return traffic
in the Dialog system is organized in Return Capacity Groups or RCG. RCG are artificial frequency
sections of the total return link spectrum of the beam. A beam is a geographical area that sends its
return signal via a certain satellite transponder.
MRC works with frequency slots. A frequency slot has a start and stop frequency and acts as a
frequency window in which MRC carriers are deployed. MRC demodulator are assigned to a
frequency slot. An MRC demodulator can only be assigned to one frequency slot, but multiple
demodulators can be assigned to the same frequency slot.
To create an MRC return capacity group:
2. Select MRC in the top menu bar.

3. Click + next to Return Link to add a return capacity group. The following window appears:

– Min/Max ModCod: These are ACM-related parameters and define the minimum and
maximum MODCOD that can be used within the RCG. ACM is always enabled for MRC.
Max MODCOD can be overridden in terminal provisioning.
The following modulation schemes are supported for MRC RCGs: QPSK,
8APSK, 16 APSK, 64APSK.
– ULogon Channel ID: Identifier of the Ulogon channel in the frequency range of this RCG.
Only supports integer values. The Channel IDs for the MRC RCGs must be different from
IDs used by the HRC RCGs in the same satnet. All MRC RCGs using the same MCD must
have the same ID. For more information about the HRC return capacity group, refer to
Create an HRC Mx-DMA Return Capacity Group on page 105.
• In case Ulogon is enabled in the Frequency Range, it sets an identifier to the Ulogon
channel in the frequency range of this RCG.
• In case Ulogon is disabled in the Frequency Range, it refers to a Ulogon channel of
another RCG, which will be used to logging on terminals into this RCG.
– Min Symbol Rate: This is an ACM-related parameter. Every 40 ms, which corresponds
with the MRC scheduling interval, NxtGen Mx-DMA allocates a symbol rate to each
terminal associated to the RCG. This symbol rate is the result of a certain bit rate need,
which is based on the return traffic demand, the QoS management parameters and the
channel conditions. Terminals suffering from phase noise have a high packet error ratio

value. Setting a minimum symbol rate of such a terminal, can decrease the packet error
ratio value. However, if you do not have any reason to bound the symbol rate, you can set
this parameter to the minimum allowed value, which is 100 kBaud.
The minimum symbol rate can be overridden in terminal provisioning.
– Max Symbol Rate: Every 40 ms, which corresponds with the MRC scheduling interval,
NxtGen Mx-DMA allocates a symbol rate to each terminal associated to the RCG. This
symbol rate is the result of a certain bit rate need, which is based on the return traffic
demand, the QoS management parameters and the channel conditions. The system can
hand out “free capacity” if more bandwidth is available on the RCG than needed for the
sum of requested capacity. Terminal carrier sizes will inflate to offer more “free” bit rate to
the terminals. For some installations with ODU power limitations this may not always be a
good idea. The artificial bit rate may drive terminals to high symbol rates, and thus to high
power levels. These can sometimes become so high that the terminal is forced to operate
in lower modulation schemes (lower efficiency) in order to limit the out-of-band spectral
regrowth. A similar thing can happen if a terminal asks for more bit rate than is actually
healthy given the ODU power, the antenna size, the place of the terminal in the beam
footprint, etc.
Also, setting a maximum symbol rate reduces the impact on other terminals within the
return capacity group. A terminal with a very robust MODCOD can consume a large amount
of bandwidth in order to keep its configured bit rate or CIR, resulting in large carriers /
symbol rates. This impacts other terminals that are using the same Return Capacity Group.
For all of these reasons, it is possible to limit the maximum bandwidth that terminals can
consume. However, if you do not have any reason to limit the bandwidth you can set this
parameter to the maximum allowed value, which is 25 MBaud.
The maximum symbol rate should be supported on the demodulator role type.
– Free Capacity: Click the button to enable or disable the distribution of free capacity. When
enabled, the MRC controller hands out the capacity of the RCG that is left after the
capacity requests of all terminals have been fulfilled and a terminal can get more bandwidth
than requested. The terminal can even get more capacity than its configured PIR as the
free capacity is not taken into account for PIR. When disabled only the requested capacity
is distributed and any remaining capacity in the return capacity group is not used and
therefore lost. Free capacity distribution is by default enabled.
We recommend to keep free capacity distribution enabled.

When disabled, the modem can experience packet loss at the start of return
transmission. This is the result of the modem data queue overflow caused by
the fact that the MRC controller needs several seconds to assign capacity to the
modem. When the capacity is assigned, the modem queue will be emptied in a
slow pace resulting in delays.
Only disable free capacity distribution in specific use cases.
The introduction of Flow Fairness may require customers upgrading from Dialog
R2.2.3 or lower to review and adapt the configuration to ensure that
time-sensitive applications are allocated with the right priority. For this reason it
is recommended to keep Free Capacity always enabled. It should only be
disabled for testing or troubleshooting purposes. For more information, refer to
The amount of free capacity to distribute is limited by the Free Capacity PIR value.
• Free Capacity PIR: This parameter is only available when free capacity distribution is
enabled. The Peak Information Rate or PIR value limits the amount of free capacity to

distribute. The value ranges from 0 Mbps to 250 Mbps. The default value is 150 Mbps.
Mind that the actual peak rate of the free capacity cannot exceed the peak rate of the
return capacity group.
– Static Margin: An extra margin in dB can be added on top of the nominal MODCOD
threshold, which is used to determine when to switch to another MODCOD. In case return
link efficiency is required, it is advised to set the static margin to zero dB.
– To avoid persistent loss of packets, an additional ACM margin (Errored Second Margin) is
added in case of errored bursts. When a burst is lost in a second, the Errored Second
Margin is increased with a configurable step size (Errored Second Margin Increase).
When multiple errored timeframes occur, this additional margin increases until a maximum
(Errored Second Margin Max). When no burst errors occur in a second, the Errored
Second Margin is decreased with the following step:
• Errored Second Interval Target: Default value is 1000 seconds. Values must be
between 10 and 1e7 seconds.
• Errored Second Margin Increase: Default value is 0 dB (therefore the mechanism is
disabled). Values must be between 0 and 0.5 dB.
• Errored Second Margin Maximum: This parameters guarantees that the margins
become too high so the system stops working. Values must be between 0 and 5 dB.
The default value is 4 dB.
For more information about the ACM algorithm in MRC NxtGen Mx-DMA RCG, refer to
– Frequency Ranges: This is the frequency range of the MRC return capacity group. Each
MRC RCG supports one frequency range. Click to add a frequency range and enter
the following parameters:
• Name: This is the name of the frequency range. The name of the frequency range
must be unique over the RCGs and only support alphanumerical characters,
underscores and hyphens. Blank spaces are not allowed.
• Start/Stop Frequency: This is the frequency range, expressed in GHz.
The MRC RCG bandwidth must be between 510 kHz and 72 MHz with Universal
Logon enabled, or between 200 kHz and 72 MHz with Universal Logon
disabled. The bandwidth of the Ulogon channel is 510 kHz.
• Universal Logon: Universal logon or Ulogon is the logon method for MRC RCGs.
Click the button to enable or disable Ulogon. In case Ulogon is disabled, the Ulogon
Channel ID parameter of the RCG must be equal to an already existing channel in
another MRC RCG.
• MCD Role Id: Demodulator pool used for the Return Capacity Group.
Click Confirm to accept the changes or Cancel to discard the settings of the frequency
range.
Click to edit the frequency range. Click to delete the frequency range.
5. Click Confirm to accept the changes or Cancel to discard the settings of the MRC RCG.

messages.
To edit the return capacity group, click Edit RCG.
To edit the frequency range only, click in the Actions column. Alternatively, you
can also right-click on the frequency plan and select Edit from the pop-up menu. Click
and drag the dots to change the start and stop frequency.
To delete the RCG, click .
Click in the Actions column to go to the return QoS plan.

7.10 How to Create 4CPM Resources

To create the 4CPM return resources, execute the following steps:
2. Select 4CPM in the top bar menu.
3. Define the 4CPM demodulator(s) on which the 4CPM resources should be hosted. For more
information, refer to How to Add a 4CPM Configuration on page 115.
4. Add one or more CSC carriers. For more information, refer to How to Add a CSC Carrier on
page 115.
5. Add one or more return capacity groups. For more information, refer to
How to Add a Return Capacity Group on page 117.
6. Add one or more return carrier pools. For more information, refer to
How to Add a Return Carrier Pool on page 118.
7. Add one or more traffic carriers. For more information, refer to How to Add a TRF Carrier on
page 119.
The figure below shows an example of configured 4CPM resources.

7.10.1 How to Add a 4CPM Configuration

To add a 4CPM configuration, execute the following steps:
1. Click next to Return Link. The button is only available when the platform has a free
4CPM demodulator role.
The maximum number of active 4CPM demodulators that can be assigned to the
satellite network is four, except for an XIF hub module deployed on the Newtec
Private Cloud Infrastructure or NPCI.
2. A window Add new CPM configuration pops up.

3. Click the radio button to select the type of demodulator (NTC2291 or MCD). Select the
demodulator role from the drop-down list.
4. Click Confirm to add the 4CPM demodulator or Cancel to discard the settings.
6. Repeat step 1 to 5 to add more demodulators. You can add up to four demodulators, except
when your hub module is an XIF hub module deployed on the Newtec Private Cloud
Infrastructure or NPCI. In that case, the satellite network supports only one 4CPM demodulator.
When the demodulator is selected in the tree menu at the left:
• Click to edit the CPM demodulator.
• Click to delete the CPM demodulator

Always click Apply to save the 4CPM resources settings or click Discard to discard the
settings.
7.10.2 How to Add a CSC Carrier

When the demodulator is added and the Return Link label in the tree menu at the left is selected,
the Extended Footprint toggle button is displayed. Click the button to extend the footprint timing
(ON) or not (OFF). Extending the footprint timing makes the guard times of a CSC carrier larger than
normal. The normal guard time is 22 ms, the extended guard time is 45 ms. The extended guard
time allows terminals that have a very large distance from the satellite to still login. However larger

guard times require more bandwidth, which cannot be used for the traffic carriers. By default the
footprint timing is not extended.
To create a CSC carrier, execute the following steps:
1. Select the demodulator in the tree menu at the left. Several buttons appear.
2. Click Add CSC Carrier.

– Carrier Type: Select the carrier type from the drop-down list. If you have activated the
extended footprint, you can select extended CSC carriers, which have larger guard times
than normal.
– Center Frequency: Enter the center frequency of the CSC carrier. Alternatively, click the
Adjacent to existing Carrier button and specify where the carrier is positioned in the
frequency spectrum using the drop-down lists that appear.
– Enabled: Click the button to enable or disable the CSC carrier.
4. Click Show Advanced Settings... to enter the following parameters:
– Number of Carriers: Specify the number of CSC carriers you want to create. All carriers
are the same type and are adjacent starting from the first carrier using the configured
center frequency. The number of carriers is by default set to 1.
– BDM Channel: A Burst Demodulator has eight (NTC2291) or nine (MCD7000/MCD7500)
channels. You can define which channel is used for the carrier type. By default the BDM
channel is selected automatically.
5. Click Confirm to add the CSC carrier(s) or Cancel to discard the settings.
7. Repeat step 2 to 5 to add more CSC carriers.
To edit the parameters of the CSC carrier, click in the Actions column, or click
on the CSC carrier in the frequency plan.
To edit only the center frequency, right-click on the CSC carrier in the frequency plan
and select Edit from the pop-up menu. Click and drag the dot to change the frequency.

Mind that the change is effective immediately.
To delete the CSC carrier, click in the Actions column, or right-click on the CSC
carrier in the frequency plan and select Delete from the pop-up menu.
Click or in the Actions column to enable or disable the CSC carrier.

7.10.3 How to Add a Return Capacity Group

Select the demodulator in the tree menu at the left. Several buttons appear.
To create a return capacity group, execute the flowing steps:
1. Click Add RCG.

– BDM: Select the demodulator that will process the return capacity group. This is only
applicable if multiple 4CPM demodulators have been added. By default, the BDM of the
selected 4CPM demodulator in the menu tree at the left is entered.
– Copy ARL States from: It is recommended to use the Newtec Defaults values for the ARL
states. Click in the Actions column to adapt the ARL states. For more information
on ARL, refer to 4CPM MF-TDMA on page 75.
3. Click Confirm to create the return capacity group. The RCG will appear in the tree menu at the
left, under the CPM demodulator menu item. Or click Cancel to discard the new RCG.

5. Repeat step 2 to 4 to add more return capacity groups.
When the return capacity group is selected in the tree menu at the left:
• Click Edit RCG to change the parameters.
• Click next to the RCG title to delete the RCG.
• Click next to the RCG title to go to the return QoS plan.

7.10.4 How to Add a Return Carrier Pool

Select the return capacity group in the tree menu at the left. Several buttons appear.
To create a return carrier pool, execute the following steps:
1. Click Add RCP.

– Name: This is an arbitrary name which should be unique within the return capacity group.
The name should only support alphanumerical characters, underscores and hyphens.
Blank spaces are not allowed.
– Min C/No and Max C/N0: These are ARL-related parameters. A terminal will only be
allocated to this return carrier pool if: Min C/N0 + margin (defined per RCG) ≤
C/N0,measured ≤ Max C/N0 + margin (defined per RCG). For more information about
ARL, refer to 4CPM MF-TDMA on page 75.
3. Click Confirm to create the return carrier pool. The pool will appear in the tree menu at the left,
under the RCG menu item. Or click Cancel to to discard the new return carrier pool.
5. Repeat step 2 to 4 to add more return carrier pools.

When the return capacity group is selected in the tree menu at the left:
• Click Edit RCP to change the parameters.
• Click next to the RCP title to delete the carrier pool.

7.10.5 How to Add a TRF Carrier

A traffic carrier can be added at different 4CPM resource levels from the tree menu at the left:
• At CPM demodulator level
• At RCG level
• At RCP level
Depending on the level and the resources already defined, parameters already have a value or not.
1. Click Add TRF Carrier.
The following window appears.

– BDM: Select the demodulator that will process the traffic carrier. This is only applicable if
multiple CPM demodulators have been added.
– Carrier Type: Select the carrier type from the drop-down list. Keep in mind that a return
carrier pool can only have traffic carriers of the same type.
– Return Capacity Group: There are several ways to set the RCG.
• If you have already added one or more return capacity groups, select the one you
need from the drop-down list.
• If you have already added one or more return capacity groups but you want to use a
new one, click , enter a name for the RCG and click to confirm.
• To edit the settings of the new RCG, select it in the tree menu and click Edit RCG. For
more information about the RCG parameters, refer to
• If no return capacity groups exist, enter a name for the RCG and click to confirm.

• To edit the settings of the new RCG, select it in the tree menu and click Edit RCG. For
more information about the RCG parameters, refer to
– Return Carrier Pool: There are several ways to set the RCP.
• If you have already added one or more return carrier pools, select the one you need
from the drop-down list.
• If you have already added one or more return carrier pools but you want to use a new
one, click , enter a name for the RCP and click to confirm.
To edit the settings of the new RCP, select it in the tree menu and click Edit RCP. For
more information about the RCP parameters, refer to
• If no return carrier pools exist, enter a name for the RCP and click to confirm.
To edit the settings of the new RCP, select it in the tree menu and click Edit RCP. For
more information about the RCP parameters, refer to
– Center Frequency: Enter the center frequency of the traffic carrier. Alternatively, click the
Adjacent to existing Carrier button and specify where the carrier is positioned in the
frequency spectrum using the drop-down lists that appear.
– Enabled: Click the button to enable or disable the CSC carrier.
3. Click Show Advanced Settings... to enter the following parameters:
– Number of Carriers: Specify the number of TRF carriers you want to create. All carriers
are the same type and are adjacent starting from the first carrier using the configured
center frequency. The number of carriers is by default set to 1.
– BDM Channel: A Burst Demodulator has eight (NTC2291) or nine (MCD7000/MCD7500)
channels. You can define which channel is used for the carrier type. By default the BDM
channel is selected automatically.
4. Click Confirm to create the TRF carrier(s) or click Cancel to discard the settings.
6. Repeat step 3 to 6 to add more TRF carriers. Keep in mind that a return carrier pool can only
have traffic carriers of the same type.
To edit the parameters of the TRF carrier, click in the Actions column, or click
on the TRF carrier in the frequency plan.
To edit only the center frequency, right-click on the TRF carrier in the frequency plan
and select Edit from the pop-up menu. Click and drag the dot to change the frequency.
Mind that the change is effective immediately.
To delete the TRF carrier, click in the Actions column, or right-click on the TRF
carrier in the frequency plan and select Delete from the pop-up menu.
Click or in the Actions column to enable or disable the TRF carrier.


7.11 How to Open the Return QoS Plan Interface

To open the provisioning interface of the Return QoS plan, execute the following steps:
4. From here, you can access the return QoS plan in different ways.

Click next to Return Link to open the return QoS plan.

– You can select the beam identifier and Satellite Network that corresponds with the return
link. Click Resource Provisioning and then click RN QoS Plan.

– Or you can open the RN Frequency Plan and then click next to the return capacity
group title.

The provisioning interface is displayed. There is a root pool per created 4CPM, HRC Mx-DMA
and MRC NxtGen MxDMA return capacity group. The SCPC return technology does not use the
concepts of return pools and is not displayed in the QoS plan.
– Click Detailed to show or hide the CIR/PIR details.

– Click Expand to collapse or expand the QoS tree.
– Click Legend to know the functionality of the icons and the applied color scheme.
Alternatively you can hover over the icons.

7.12 How to Edit the Root Pool

The root pool corresponds with the return capacity group. To edit the QoS parameters of the root
pool, execute the following steps:
1. Open the provisioning interface of the RN QoS Plan as described in
How to Open the Return QoS Plan Interface on page 121.

– Access Rights: The root pool and underlying child pools can be dedicated to a specific
VNO or shared among multiple VNOs. Use the slider to select Dedicated or Shared.
– Dedicated to: This parameter appears when the Access Rights are set to Dedicated.
Select a VNO domain name from the drop down list to whom this root pool is dedicated.
– PIR: PIR or Peak Information Rate defines the upper data rate limit for this pool.

overbooking is by default enabled. When enabled, the total CIR used by the child pools
may exceed the CIR rate of the root pool.
– Allow Own Classification Profiles: Click the button to allow VNOs to use their own
classification profiles. Refer to Manage Classification Profiles on page 188 for more
information.
5. Click Confirm to accept the changes or Cancel to discard the changes.
Click to view the details of the root pool.
7.13 How to Create a Dedicated Transport Based Return

Pool
To create a dedicated transport-based return pool, execute the following steps:
A window pops-up.
Make sure to set:
root pool have been set to Dedicated. In that case, the return pool is automatically
dedicated to the VNO selected in the root pool.


– Dedicated to: Select a VNO domain name from the drop-down list to whom this return pool
is dedicated.
pool.
4. Enter the shaping parameters:

– Weight: This is the weight assigned to the pool. The weight value ranges between 1 and
1000. The default value is 100. The total weight equals PIR * Weight. The total weight is
used as a ratio mechanism for "fair" distribution of additional capacity after CIR is applied.
The Total Weight is also used in case of CIR overbooking.
exceed the CIR rate of the return pool.
information.

Click to view the details of the return pool.
Click to delete the return pool.
7.14 How to Create a Shared Transport Based Return Pool

To create a dedicated transport-based return pool, execute the following steps:
A window pops-up.
Make sure to set:
dedicated and you cannot create shared pools.


– Domains: Select the VNO domains from the drop -down list who share this return pool. At
information.

Click to view the details of the return pool.
Click to delete the return pool.
7.15 How to Create a Dedicated Class Based Return Pool

To create a dedicated class-based return pool, execute the following steps:
A window pops-up.
Make sure to set:
dedicated to the VNO selected in the root pool.


– Dedicated to: Select a VNO domain name from the drop-down list to whom this return pool
is dedicated.
pool.


The rates can be set for the return pool and per QoS pool within the return pool. For the
real-time QoS pools, CIR equals PIR. The best-effort QoS pool only uses PIR. For the QoS
pools, you can also specify an average IP Packet Size. This value is used to allocate extra
bandwidth for encapsulation overhead.
information.
When confirmed, the return pool and QoS classes are added to the QoS plan.
Click to view the details of the return pool or QoS class.
Click to edit the parameters of the return pool or QoS class.
Click to delete the return pool or a QoS class.
7.16 How to Create a Shared Class Based Return Pool

To create a shared class-based return pool, execute the following steps:

A window pops-up.
Make sure to set:
dedicated and you cannot create shared pools.


– Domains: Select the VNO domains from the drop down list who share this return pool. At

The rates can be set for the return pool and per QoS pool within the return pool. For the
real-time QoS pools, CIR equals PIR. The best-effort QoS pool only uses PIR. For the QoS
pools, you can also specify an average IP Packet Size. This value is used to allocate extra
bandwidth for encapsulation overhead.
information.
Click to view the details of the return pool or QoS class.
Click to edit the parameters of the return pool or QoS class.
Click to delete the return pool or a QoS class.
Click on the return pool to add a dedicated QoS class.
7.17 How to Enable HRC Mx-DMA Universal Logon

Where the standard HRC Mx-DMA logon mechanism polls all off-line terminals in every beam where
they have been provisioned in via a solicited logon, universal logon or ulogon triggers solicited
logons only for terminals that want to come online and only in the beam where they are.
With ulogon, the terminal flags the hub that it wants to come online by answering a unicast ulogon
request. As a response the HRC controller sends its HRC Start Trigger to the specific modem using
the standard solicited logon mechanism.

The following chapters explain how to enable ulogon for a terminal. This requires actions both at the
hub and terminal side.
Ulogon is only supported on demodualtors MCD7000 and MCD7500_HRC with a

capability of 17 Mbd / 70 MHz and on MCD7500_HRC68.
7.17.1 Activate HRC Ulogon

To activate HRC Ulogon, execute the following steps:
2. Select HRC in the top menu bar.
3. Select HRC Return Capacity Groups in the submenu.
4. Click in the Actions column to open the configuration window of the HRC Mx-DMA
return capacity group for which HRC Ulogon should be enabled.
5. Set Logon Mode to Logon Bandwidth and activate Universal Logon.
6. HRC Ulogon should also be activated at the terminal side.

In the Surveyor tree, go to Newtec Dialog > Terminals > Terminals Provisioning. Select the
HRC Mx-DMA terminal for which you want to enable HRC Ulogon and click on it. The modem
provisioning interface opens.
7. Go to the Service tab and activate Universal Logon in the HRC Mx-DMA Settings section.

This button is only available for terminals that support universal logon.
Use the Batch Actions functionality to enable universal logon on a group of

terminals simultaneously.
7.17.2 Configure Sufficient Maximum Logon Bandwidth

The Maximum Logon Bandwidth that should be configured for the Logon Bandwidth mode,
should be higher than the total of:
• 510 kHz of the ulogon bandwidth.
• The bandwidth required for login using the standard mechanism, which equals 1.05 * Logon SR *
number of logon channels you want.
• Worst case bandwidth uncertainty: 103 kHz.
This results in the following behavior:
• Enabling ulogon on HRC Mx-DMA RCG results in 510 kHz less bandwidth available for user
traffic.
• Disabling ulogon on HRC Mx-DMA RCG results in freed up bandwidth for standard logon or
traffic. When all HRC terminals are logged on the standard method logon capacity becomes
available for traffic.
The system will check if the Maximum Logon Bandwidth provides space for at least one solicited
login channel.
The example shows a Maximum Login Bandwidth of 1.200 kHz, which is larger than 510 kHz + 103
kHz + 3*185 kBd*1.05, in case of three solicited login channels of 185 kBd.

7.17.3 Make Sure the Demodulator Capability is Available

The universal logon feature is only supported on the MCD7000 and MCD7500_HRC20 with a
capability of 17 MBd / 70 MHz, and on the MCD7500_HRC68.
The demodulator capability is set via the Hub Module provisioning interface during installation of the
demodulator.

7.17.4 Make Sure Sufficient HRC Demodulators are Available

The number of HRC return capacity groups supporting ulogon must be smaller than the number of
HRC demodulators. One HRC demodulator supports one ulogon channel. Make sure that the
number of ulogon enabled return capacity groups can be linked with a demodulator role within the
corresponding frequency slot used by the RCGs.
7.18 How to Migrate Carrier

The carrier migration feature can be used to reorganize the return resources after they were
created. This feature makes it possible to shift return resources that belong to a certain return link
technology within the frequency spectrum. This is for example useful when filling up gaps in the
frequency spectrum or to easily move return resources from Ku-band to Ka-band in a single
operation.
Terminals using the return resources, which are migrated, will be disconnected.
To apply carrier migration, execute the following steps:

2. Select Carrier Migration in the top menu bar.

3. Change one or more of the parameters (depending on the migration scenario):

– Hub Delta Frequency: This is the difference between the L-band input frequency of the
demodulators processing the carriers of the satellite spot beam and the downlink frequency
of the transponder servicing this beam. This parameter is typically edited when moving to
another satellite or frequency band. For more information about the frequency, refer to
Frequencies on page 88.
– Transponder Delta Frequency: This is the shift from uplink to downlink frequency within
the transponder, which is servicing this spot beam. This parameter is typically edited when
moving to another satellite or frequency band. For more information about the frequency,
refer to Frequencies on page 88.
Select the transponder settings of one of the already configured transponders from the
drop down list or click to change the value of this parameter.

– Frequency Offset: This is an offset value to move the return resources to the left or right in
the spectrum. The value can be positive (shift to the right) or negative (shift to the left). This
parameter is typically edited when filling up gaps in the frequency spectrum.
– Return Technologies: Select the return link resources, which will be migrated, from the
drop -down list. This parameter is typically edited when filling up gaps in the frequency
spectrum.
4. Click Save to save the changes or Cancel to discard the changes.
The following example shows how to fill the gap between the S2 and the 4CPM return capacity
group.We will move the S2 RCG frequency slot next to the 4CPM RCG frequency slot.
To shift the frequency slot, execute the following steps:
1. Define the offset between the two frequency slots. The offset equals start frequency of the S2
RCG - stop frequency of the 4CPM RCG.
Hover over the RCGs in the frequency plan to know the exact frequency.

In this example, the offset = 14.42 GHz - 14.416984 GHz = 0.003016 GHz.
2. Set the Frequency Offset and the Return Technologies in the Carrier Migration window. When
setting the offset, an arrow appears indicating the direction of the shift. Make sure that the
arrow points to the left. This will also turn the offset into a negative value.
3. Click Save.
A summary of the affected resources and the new frequency positions is shown, as well as any
terminal affected. Keep in mind that active terminals will be disconnected after applying the
changes.

4. Click Confirm if OK. The result of the migration is shown in the frequency plan.

VNO and User Management
8 VNO and User Management

It is possible to create multiple Virtual Network Operators (VNO) and corresponding User accounts
on a Newtec Dialog platform. This allows an HNO (Hub Network Operator) to grant access to a VNO
and its resources. We can distinguish following roles or definitions:
• Group (Role): Is a collection of permissions. The access (authorization) granted on Newtec
Dialog is based on the set of permissions. Groups can be defined as member of other groups
(known as subgroups or nested groups). Example: VNO-Administrator group, VNO-Operator
group, HNO-Administrator.
• Permission: Action or set of actions authorized in the system. The authorization is the act of
deciding if a user is allowed to perform certain actions and access to a resource. Example: Read
on Forward Pools.
• Domain (VNO): The domain (VNO) is used to grant or restrict access in Newtec Dialog to
resources like Return or Forward pools and terminals. The domain where the user belongs also
limits the view that the user has of the system. A user only sees his own resources, basically the
ones that are available for his domain. In the context of Newtec Dialog, the domain verification will
be required for every user. For example: domain = VNO-1.
• User: A user is a combination of name, credentials and other attributes. A user belongs to a
group/Role (VNO-Operator, HNO-Administrator, System Administrator) and to a domain (VNO).
Example: user John Doe belongs to the group (or has the role of) VNO-operator and is a member
of the VNO-1 domain.
8.1 How to Open the VNO and User Management Web

Interface
To open the web interface of the User and VNO Management, execute the following steps:
3. Click User/HNO/VNO Management in the surveyor tree or in the visual overview.

8.2 How to Create a VNO

To create a VNO, execute the following steps:
1. Open the User and VNO Management web interface as described in
How to Open the VNO and User Management Web Interface on page 143.
2. Click VNO Provisioning in the surveyor tree or in the visual overview.

4. Click + Create VNO.
A window appears where you can configure the VNO and the access rights.
5. Configure the VNO.

Set the parameters:

– Name: This is the name of the Virtual Network Operator (VNO). The name should be
unique within the Dialog platform and only support alphanumerical characters, underscores
and hyphens. Blank spaces are not allowed.
– Number of Advanced Modems: Advanced Modems are modems from which the hub
retrieves metrics at a high sampling rate. The metrics are trended as real-time. This type of
monitoring requires more CPU power than normal monitoring. It is therefore possible to limit
the number of modems that are "advanced" monitored.
– Capabilities: Capabilities allow the VNO to edit specific items during terminal provisioning.
You can select none, one or multiple capabilities. The following capabilities exist:
• Manage the modem line up settings.
• Manage the modem debug level. If debugging is enabled, more metrics are collected
by the system.
• Manage the modem forward maximum MODCOD.
• Manage the restricted properties (max. MODCOD / min. symbol rate) in the terminal
Mx-DMA and NxtGen Mx-DMA settings.
• Manage the power values in case of S2, HRC or MRC return technology.
– Certification Skipped: It is possible to disable certification at VNO level, even if certification
is enabled at satellite network level. This means that certification can be overruled for a
VNO. For more information about certification at satellite network level, refer to
How to Create a Satellite Network on page 19.
6. Configure the access rights.

Linking the VNO to profiles or resources is only possible when those profiles or
resources have been created.
Set the parameters:

– Profiles: Select the service profile(s) that the VNO can use. This list is automatically
populated with the currently created service profiles. For more information on how to create
service profiles, refer to Manage Service Profiles on page 198.
– Classification Profiles: Select the classification profile(s) that the VNO can use. This list
is automatically populated with the currently created classification profiles. For more
information on how to create a classification profile, refer to Manage Classification Profiles
on page 188. The "best-effort-only" classification profile is always selected.
– Default Classification Profile: If more than one classification profile is selected in the
previous step, then select which profile will be used as default classification profile for the
VNO during terminal provisioning.
– Satellite Network related Access Rights: Each configured satellite network is listed. The
choice of satellite network defines the forward link, return link, and network resources that
a VNO can use. Click to select following settings:

• Forward: Select the forward pool(s) to which this VNO should be linked. This list is
automatically populated with the currently created forward pools. For more information
on how to create forward pools, refer to Manage Forward Link Resources on page 25.
• Return: Select 4CPM return pool(s) to which this VNO should be linked. This list is
automatically populated with the currently created 4CPM return pools. For more
information on how to create return pools, refer to Manage Return Link Resources on
page 73.
• HRC Mx-DMA Return Pools: Select HRC Mx-DMA return pool(s) to which this VNO
should be linked. This list is automatically populated with the currently created HRC
Mx-DMA return pools. For more information on how to create return pools, refer to
Manage Return Link Resources on page 73.
• MRC Return Pools: Select MRC NxtGen Mx-DMA return pool(s) to which this VNO
should be linked. This list is automatically populated with the currently created MRC
NxtGen Mx-DMA return pools. For more information on how to create return pools,
refer to Manage Return Link Resources on page 73.
• S2 Return Capacity Groups: Select S2 return capacity group(s) to which this VNO
should be linked. This list is automatically populated with the currently created S2
return capacity groups. For more information on how to create return capacity groups,
refer to Manage Return Link Resources on page 73.
• HRC SCPC Retrun Capacity Groups: Select HRC SCPC return capacity group(s) to
which this VNO should be linked. This list is automatically populated with the currently
created HRC SCPC return capacity groups. For more information on how to create
return capacity groups, refer to Manage Return Link Resources on page 73.
• Network: Select IPv4 pool(s) to which this VNO should be linked. This list is
automatically populated with the currently created IPv4 pools. For more information on
how to create IP pools, refer to How to Create IPv4 Pools on page 180.
• IPv6 Pools: Select IPv6 pool(s) to which this VNO should be linked. This list is
automatically populated with the currently created IPv6 pools. For more information on
how to create IP pools, refer to How to Create IPv6 Pools on page 183.
• Dedicated Subnet: Select dedicated subnet(s) to which this VNO should be linked.
This list is automatically populated with the currently created dedicated subnets. For

more information on how to create dedicated subnets, refer to

How to Create a Dedicated Subnet on page 167.
7. Click Apply to create the VNO or click Discard to cancel. Check the log panel for validation
messages.
Click on the VNO in the overview to edit the parameters.
Click to delete the VNO.
8.3 How to Create a New User

To create a user, execute the following steps:
1. Open the User and VNO Management web interface as described in
How to Open the VNO and User Management Web Interface on page 143.
2. Click User Provisioning in the surveyor tree or in the visual overview.

4. Click + Create New User.


– Domain: Select the domain to which the user belongs. This can be the HNO domain or a
VNO domain.
– Username: Enter the user name, which is used to login. The name should be unique within
the domain and only support alphanumerical characters, underscores and hyphens. Blank
spaces are not allowed.
– Password: Enter a password, which is used to login. The password should have at least 6
characters.
– Confirm Password: Confirm the password.
– Role: Select the role assigned to the user. The role determines the user's access rights.
Possible roles are:
• Administrator: Can create and manage users for his domain and can also manage all
resources of his domain.
• Operator: Can manage all resources of his domain, except the user creation and
management.
• Observer: Has read-only access of the resources of his domain.
• Certifier: Can only manage the TICS feature and is allowed to certify, uncertify and
update line up settings of terminals.
– Active: Click the button to enable or disable access to the platform for this user.
The other parameters are not mandatory, but can provide additional information about the user.
6. Click Apply to create the user or click Discard to cancel. Check the log panel for validation
messages.
Click on the user in the overview to edit the parameters.

Click the button in the Active column to change the platform accessibility for the user.
The system will ask you to confirm this change.
Click to delete the user.

Manage Network Resources
9 Manage Network Resources

The Dialog network resources can be grouped into:
• Layer 3 networks
• Layer 2 networks
• Multicast networks
A network connects an uplink network on the hub side to one or more LAN networks behind the
modems.
An uplink network is identified by a customer-defined VLAN on a specific uplink interface. The uplink
interfaces are:
• Aggregated interfaces grouping multiple (typically two) physical interfaces for redundancy.
• Configured in Trunk mode allowing to define multiple VLANs on top of them.
The LAN network on the modem side is also identified by a VLAN. This can either be a native or
untagged VLAN.
The uplink part of the network is defined during the network resource provisioning (this chapter), the
LAN part of the network is defined during terminal provisioning on page 234.
9.1.1 Layer 3 Network Resources

A layer 3 or L3 network connects an uplink network (1 in the figure below) on the hub side to the
LAN network behind one or more modems (2 and 3 in the figure below). This consists of a single
routing instance (Virtual Routing and Forwarding or VRF) which provides bidirectional routing of IP
traffic between the uplink network and the LAN networks behind the modems. The L3 network can
therefore be compared to a router.

The L3 network is identified by a configurable VLAN tag on the uplink interface and on the LAN
interface of the modem.
You can configure multiple L3 networks in the same satellite network resulting in multiple VRF
instances. Each instance has an isolated routing and addressing context allowing to reuse private
address ranges for the different networks in the same satellite network. And you can terminate
multiple L3 networks on the same modem, also resulting in multiple VRF instances with isolation of
the routing and addressing context.
The number of virtual networks supported per satellite network depends on the type of hub module.
Hub Module Type Max. # of L3 Networks
1IF 50
4IF 128 (with servers GEN8)

256 (with servers GEN9 and up)
XIF 256
The number of virtual networks supported on a terminal depends on the type of terminal:
Modem Type Max. # of Virtual Networks
MDM2010 4
MDM2210 4
MDM2510 16
MDM3310 16
SMB3310 16
SMB3315 16

MDM5000 16
MDM5010 24
The L3 network supports two modes for assigning IP addresses or subnets to the LAN network of
the modem. The modes are:
• Dedicated Subnet
• Shared Subnet
9.1.1.1 Dedicated Subnet
In Dedicated Subnet mode, the modem receives a unique and dedicated range of IPv4 and/or IPv6
addresses. One IP address from this range is assigned to the modem's network interface. The
remaining addresses in the range are available for the hosts behind the modem. The modem can
serve as a DHCP server for the allocation of the IP addresses. If the modem is not used as a DHCP
server, another device in the LAN has to act as the DHCP server, or a static IP address on each host
has to be configured.
9.1.1.2 Shared Subnet
In Shared Subnet mode, the modem receives a single unique IP address for the host behind the
modem. This IP address is taken from a centrally managed IPv4 and/or IPv6 address pool. The IP
address of the modem's network interface in a shared subnet is always the first IP address of this
pool. This address is used as proxy IP address on each modem that receives an IP address from the
same address pool. The host behind the modem will behave as if it is part of a larger subnet. By
means of Proxy ARP on the modem, the host will be able to reach other hosts in the same subnet
but connected to different modems.

You can configure only one shared subnet per satellite network.
9.1.1.3 Uplink Network Connectivity
In order for an uplink network to connect to the hub, the uplink interface must be configured with a
forward link next -hop address and a return link default gateway.
The uplink interface is the interface from the hub towards the customer's edge router. The forward
link next-hop address is configured at the hub, more specifically on the DEM VM, the return link
default gateway is configured on the customer's edge router.
Because the uplink network is identified by a customer-defined VLAN on the uplink interface, it is
possible to reuse the uplink interface IP subnet for different layer 3 networks supported on the uplink
interface.
The example below shows an example of three networks configured on the same uplink interface
using the same uplink IP subnet.
9.1.1.4 DNS
Dialog can handle DNS request in two ways: proxy DNS and transparent DNS.
Proxy DNS
This is the standard DNS behavior.
DNS server(s) are configured per subnet. The modem announces its own IP address as the unique
name server to the hosts and captures all DNS lookup requests coming from the hosts. The modem
acts as a DNS client and forwards the DNS requests to the DEM. The DEM has a running DNS
proxy, which forwards the DNS requests to the DNS server(s) that are configured for the
corresponding subnet. The modem also has a DNS cache.

Transparent DNS
With the Transparent DNS feature, DNS servers are configured per terminal. This feature is
optional. If enabled, the terminal sends the configured DNS servers via DHCP to its hosts. The hosts
send their DNS requests to these servers. This is entirely transparent to Dialog and bypasses the
internal DNS proxy functionality. The DNS servers configured per subnet are ignored.
For more information about Transparent DNS, refer to How to Create a Terminal: Layer 3 Networks
on page 247.
Transparent DNS is only supported on the MDMxx10 series.
9.1.1.5 Routing
In order for the edge router to forward user data towards the terminals, it needs to know which
network resources are configured in the hub module. In order for the hub module to forward traffic
from the terminals towards the Internet, it needs to know the next-hop address.
The Dialog platform provides three ways to distribute routing information:
• Static routing
• OSPF or Open Shortest Path First
• BGP or Border Gateway Protocol
9.1.1.5.1 Static
In case of static routing, you manually set the default gateway IP address to which the traffic of the
virtual network and coming from the terminals is forwarded. This IP address should be the one that is
configured on the edge router and is part of the uplink IP subnet that you have defined before. It is
the return link default gateway address. For more information on this address, refer to
Uplink Network Connectivity on page 154.
On the edge router, you configure the route to this virtual network.
9.1.1.5.2 OSPF
OSPF or Open Shortest Path First is a routing protocol for IP networks. It uses a link state routing
(LSR) algorithm and falls into the group of interior gateway protocols (IGPs), operating within a single
autonomous system (AS).

When enabling OSPF for a virtual network, the virtual network is automatically advertised towards
the edge router(s). The default gateway is advertised towards the hub module.
OSPF needs to be implemented at the customer’s side. You can manage uplink
redundancy by assigning different OSPF link costs on the edge router.
The virtual network is part of an OSPF area (Not So Stubby Area). You can use the same area ID
for different virtual networks. The area ID should be configured on the edge router(s). Additionally,
you should configure the backbone OSPF area 0 on the edge router(s).
To route traffic correctly, it is necessary to prevent malicious or incorrect routing information from
getting introduced into the routing table. This can be done by authenticating the routing updates
exchanged between routers. OSPF in Dialog supports MD5 authentication (IPv4 only).
9.1.1.5.3 BGP
BGP is only supported for IPv4.
Border Gateway Protocol (BGP) is a standardized exterior gateway protocol designed to exchange
routing and reachability information among autonomous systems (AS) on the Internet. BGP cannot
discover neighbors dynamically. BGP neighbors, or peers, are manually configured among routers.
When BGP runs between two peers in the same autonomous system, it is referred to as Internal
BGP (iBGP or Interior Border Gateway Protocol). When it runs between different autonomous
systems, it is called External BGP (eBGP or Exterior Border Gateway Protocol). Routers on the
boundary of one AS exchanging information with another AS are called border or edge routers or
simply eBGP peers and are typically connected directly, while iBGP peers can be interconnected
through other intermediate routers.
At the hub side, a virtual network corresponds with an instance of a BGP router running on the DEM
virtual machine. The connectivity between the external router and the router in the hub can be eBGP
or iBGP. The router in the hub will typically learn the default gateway of the edge router (can be set)
and will advertise the subnets and IP pools towards the edge router.

In case of a dedicated virtual network, BGP is also supported at terminal level. Shared networks only
support BGP at the hub side.
BGP is only supported on MDM2510, MDM3310, SMB3310, SMB3315 and MDM5010.
When BGP is enabled at the terminal, a (dedicated) virtual network corresponds with an instance of
a BGP router running on the modem. The instance of the BGP router on the modem, runs in iBGP
mode towards the router in the hub and can run in eBGP or iBGP mode towards the external local
routers. Peering between the hub and the terminal is configured automatically.
Alternatively, you can provision static routes on the terminal. In that case, there's no BGP peering
between the modem and the external local router.
BGP uses a route reflector in the hub and a route reflector client at the terminal side. A route
reflector (RR) offers an alternative to the logical full-mesh requirement of internal border gateway
protocol (IBGP). A route reflector acts as a focal point for IBGP sessions. The BGP router running on
the DEM will learn routes of the terminals. These routes are advertised toward an external router,
but are never advertised toward other terminals.
You can also create BGP filters at hub and terminal level. Route filtering ensures that only routes
related to certain IP networks or AS numbers are exchanged across BGP peers.
At the customer’s side, BGP information needs to be configured as well: the autonomous system(s)
and the BGP neighbors for exchanging BGP information. The BGP neighbor towards the hub

module side corresponds with the uplink address, which is automatically the address of the BGP
router inside the hub module.
9.1.1.6 Service Labels
A service label can be used to group layer 3 subnets and/or IP pools, which are spread over multiple
satellite networks.
This chapter describes the following use cases with service labels:
• Use of Service Labels for Dedicated Subnets on page 158
• Use of Service Labels for Shared Subnets on page 159
• Use of Service Label in Classification Profiles on page 161
9.1.1.6.1 Use of Service Labels for Dedicated Subnets
You have a mobile terminal (refer to How to Configure Mobility Settings on page 243), which
potentially can operate in three satellite networks. You want this terminal to use the same IP range
on its LAN in every satellite network.
To implement this, execute the following steps:
1. Create a dedicated subnet on top of each satellite network. Every dedicated subnet should have
a unique name. For example: DATA-1, DATA-2 and DATA-3.
2. Enter the same service label for every subnet. This service label groups the dedicated subnets.
For example: DATA.
3. During terminal provisioning, set the DATA service label when assigning a dedicated subnet in
the Layer 3 Networks section. In that same interface, set the IP range of the modem's LAN. For
example: 192.168.100.1/29.

As a result, the Dialog platform links the terminal with the networks associated to this service label,
which are DATA-1, DATA-2 and DATA-3. The terminal will use 192.168.100.1/29 as its LAN network
where IP address 192.168.100.1 is assigned to its LAN interface.
9.1.1.6.2 Use of Service Labels for Shared Subnets
You have a mobile terminal (refer to How to Configure Mobility Settings on page 243), which
potentially can operate in two satellite networks. This terminal belongs to a shared subnet and you
(VNO1) want to assign an IP address to the terminal from a specific IP pool per satellite network.
For example, you want to use following IP ranges:
• 192.168.100.0/24 on satellite network 1 (SatNet1)
• 172.16.10.0/24 on satellite network 2 (SatNet2)
1. Create a shared subnet on top of each satellite network. The shared subnets should have
unique names. For example, PoolVNO1SN1 and PoolVNO1SN2. For more information on how
to create a shared subnet, refer to How to Create a Shared Subnet on page 173.
2. Create the IPv4 pools in the required satellite networks and enter the same service label for
both IP pools. This service label groups the pools. For example, VNO1IPs. For more
information on how to create IPv4 pools, refer to How to Create IPv4 Pools on page 180.

3. During terminal provisioning you set the VNO1IPs service label in the Layer 3 Network section.
4. During terminal provisioning, set the VNO1IPs service label when assigning a shared subnet in
the Layer 3 Networks section. Do not set the WAN address. This will make sure that the IP
address assigned to the host will be the next IP address available in the IPv4 pool(s).
As a result, your terminal will receive an IP address from the IP pool with the VNO1IPs service label
in every satellite network. In satellite network 1, the host gets an IP address from the IP range
192.168.100.0/24. In satellite network 2, the host gets an IP address from the IP range
172.16.10.0/24.

9.1.1.6.3 Use of Service Label in Classification Profiles
You can use the service label to classify traffic from specific subnets. This allows that traffic from the
specific subnets are handled differently from a quality of service point-of-view.
For example, all traffic from a dedicated subnet with service label voice should be treated as
real-time 1 traffic, and all traffic from a dedicated subnet with service label data should be treated as
best-effort.
1. Create a dedicated subnet with service label voice and one with service label data.
2. Create a classification profile (called 'data-voice' in the example) and add

– One rule which maps traffic belonging to the subnet with service label voice to Real Time 1
traffic.
– One rule which maps traffic belonging to the subnet with service label data to Best Effort
traffic.
For more information about creating a classification profile, refer to

Manage Classification Profiles on page 188.
3. Provision two terminals. For more information about terminal provisioning, refer to
– Assign the classification profile to both terminals.
– Assign both dedicated subnets to terminal 1.

– Assign dedicated subnet with service label data to terminal 2.
As a result, all traffic of the voice network within Dialog is treated as real-time 1 traffic and all traffic
of the data network within Dialog is treated as best-effort.
9.1.2 Layer 2 Network Resources

A layer 2 or L2 network is a point-to-point virtual connection and can be considered as a virtual
Ethernet pipe, which establishes isolated communication between two devices. A L2 network
connects an uplink network (1 in the figure below) on the hub side with a single LAN network on the
modem side (2 in the figure below). This consists of a single switching instance providing
bidirectional switching of Ethernet traffic between the uplink network and the modem LAN network.
The L2 network can therefore be compared to a switch with two ports connecting the uplink network
and the modem LAN network in a single broadcast domain.

The L2 network is identified by a configurable single or double VLAN tag on the uplink interface and
by a configurable single VLAN tag on the LAN interface of the modem. The supported VLAN tagging
is according to the IEEE802.1Q standard (0x8100). You can use the different VLAN tags on the hub
and modem for the same L2 network.
Uplink Input Modem LAN Output Actions
VLAN S + VLAN C VLAN C • Strip VLAN S

• Transparent forwarding
VLAN S + VLAN C VLAN C* • Strip VLAN S

• Translate VLAN C to VLAN C*
VLAN C VLAN C Transparent forwarding
VLAN C VLAN C* Translate VLAN C to VLAN C*
Untagged traffic on the modem LAN is not supported.

You can configure multiple L2 networks in the same satellite network and you can terminate multiple
L2 networks on the same modem.
Layer 2 point-to-point virtual connections are only supported on 4IF and XIF hub
modules with HP switches.
Layer 2 point-to-point virtual connections are not supported on mobile terminals.
9.1.3 Multicast Network Resources

For more information, refer to Multicast on page 337.

9.2 How to Open the Network Resources Web Interface

To open the web interface of the Satellite Resources, execute the following steps:
3. Click Network Resources in the surveyor tree or in the visual overview.
9.3 How to Create Layer 3 Network Resources

Configuring layer 3 network resources requires the following sequential steps:
• Create a Hub Termination Point. A hub termination point is the point where the customer’s network
ends and connects to the Dialog network. This is where you configure the customer-defined
VLANs.
• Create a network. This is where you configure the uplink part of the network.
• In case of a shared subnet, create one or more IP address pools.
The LAN part of the network is created during terminal provisioning. For more
information, refer to How to Create a Terminal on page 234.
The number of layer 3 networks supported per satellite network depends on the type of hub module.

Hub Module Type Max. # of L3 Networks
1IF 50
4IF 128 (with servers GEN8)

256 (with servers GEN9 and up)
XIF 256
9.3.1 How to Create a Hub Termination Point
Only the Hub Network Operator or HNO can create a hub termination point.
To create a Hub Termination Point, execute the following steps:

1. Open the Network Resources provisioning interface as described in
How to Open the Network Resources Web Interface on page 164.
2. Click Hub Termination Point Provisioning in the surveyor tree or in the visual overview.
3. Click + Create Hub Termination Point.

Alternatively, you can click the copy icon in the Actions column to create a new hub
termination point based on the settings of an existing one.
A window appears where you can configure the hub termination point and the VNO access
rights.
Make sure to set Type to Layer3.
4. Configure the hub termination point.
Set the parameters:

– Hub Module: The name of the hub module on which the hub termination point should be
defined.
– VLAN ID: This is the uplink VLAN identifier. Enter a value between 2-1001, 1006-2999 or
3501-4094. This VLAN ID should be unique within the hub module. At the customer’s side,
the Ethernet ports on the edge router should be configured in 'trunking' mode, containing
the uplink VLAN ID.
– MTU: This is the Maximum Transmit Unit. The MTU corresponds with the user IP data. The
Ethernet header and VLAN ID are not included. Enter a value between 1500 (default) and
1600 bytes.
The MTU settings will influence the size of the packets which will be generated by
the modem and hub towards the customer. Therefore, devices connected to the
modem and/or hub should use the configured MTU as well to ensure end-to-end
consistency, otherwise fragments can get dropped by these devices.
When IPsec is enabled, we recommend to set the MTU size to 1600 bytes. The
MTU size at the modem Ethernet interface is 1600 bytes - IPsec overhead, which
is 1500 bytes. An MTU size of 1500 bytes is a common value for IP data.
VPN IPsec is an optional feature on your modem. For more information about
IPsec, refer to the User Manual of your modem.
5. Link the VNO. You can link one or more VNO domain names to a hub termination point. Only
VNO domains that are linked are allowed to use the hub termination point for their subnets.

messages.
Click on the hub termination point in the overview to edit the parameters.
Click in the Actions column to delete the hub termination point.
9.3.2 How to Create a Dedicated Subnet

To create a dedicated subnet, execute the following steps:
2. Click Network Provisioning in the surveyor tree or in the visual overview.
3. Click + Create New Network.
Alternatively, you can click the copy icon in the Actions column to create a new subnet
based on the settings of an existing one.

A window appears where you can configure the network, uplink, routing protocol and the VNO
access rights.
Make sure to set Type to Dedicated Subnet.
4. Configure the network.
Set the parameters:

– Identifier: The identifier is the combination of a domain name and an arbitrary name. For a
dedicated subnet, you can select the HNO or a VNO domain name. The arbitrary name
should be unique within the domain and only support alphanumerical characters,
– Service Label: Label that allows to group subnets, which are spread over multiple satellite
networks. This label makes it easier to move terminals from one satellite network to
another. Refer to Service Labels on page 158 for more information. For a dedicated subnet,
the service label is mandatory. If it is not entered, the system will automatically use the
Name of the dedicated subnet as the service label.
– Hub Termination Point: Select the identifier of the hub termination point that applies to the
subnet.
– IPv4/IPv6 Uplink Enabled: Click the button to indicate which the IP version is supported
on the uplink between the DEM and the customer edge router. At least one uplink (IPv4 or
IPv6) is required.
– IPv4/IPv6 LAN Address Pingable: Click the button to indicate that the LAN IP address of
the modem can be pinged or not. This setting is the default setting for all modems using the
dedicated subnet. The value can be overridden per modem during provisioning. For more
information on how to change the default value for a modem, refer to Dedicated Subnet on
page 248.
– Mobile Backhaul Network: Enable this parameter to indicate that the subnet is used for
mobile connectivity and carries GTP traffic. Only when a network is marked as a mobile
backhaul network, the system will identify the traffic as GTP-U traffic and be able to perform
traffic optimization inside the GTP tunnel. For more information on how to perform GTP
optimization, refer to GTP Optimization for Mobile Backhauling on page 348.
• GTP-U is implemented on top of UDP. When the subnet is marked as a for mobile
backhaul network, the GTP Port needs to be specified. The default value is 2152.

– Internal Terminal to Terminal Communication: When enabled, communication between

terminals provisioned in the same subnet does not leave the hub. When disabled, the
communication is routed through the customer's edge router.
5. Configure the IPv4 uplink.
When the uplink supports IPv4, the IPv4 Uplink tab appears.
Set the parameters:

– Uplink IP Address: This IPv4 address is assigned to the uplink interface of the hub. It is
the forward link next-hop address to route traffic from the hub towards the terminal IP
subnets. For more information on uplink connectivity, refer to Uplink Network Connectivity
on page 154.
– Uplink IP Prefix: This is the size of the IP uplink subnet. The number is the count of
leading 1 bits in the subnet mask (CIDR notation). You need at least three host IP
addresses (two for the hub (redundant DEM VMs), one for your edge router), therefore the
minimal IPv4 prefix length is 29. For more information, refer to Uplink Network Connectivity
on page 154.
– Uplink DNS Proxy Addres: This IPv4 address is used by the DEM VM to send requests to
external DNS servers. For more information on DNS, refer to DNS on page 154.
– IPv4 DNS Servers: Click + Add to add the IPv4 DNS Server Address. This is the IPv6
address of an external DNS server, which is used by the DEM device to forward proxied
DNS requests. Refer to DNS on page 154 for more information. Click to validate the
IP address or click to discard the setting.

You can add multiple DNS server addresses. If multiple DNS servers are configured, click
and drag in the Actions column to change the order of the DNS servers. The DNS
servers are consulted based on their Index. When the first DNS server does not reply, the
next DNS server is consulted, and so on.
Click in the Actions column to edit the DNS server address.
Click in the Actions column to delete the DNS server address.

When Transparent DNS is enabled on the terminal, the DNS servers

configured per subnet are ignored and the internal DNS proxy functionality is
bypassed. For more information about Transparent DNS, refer to
Dedicated Subnet on page 248.
Set the parameters:

– Uplink IP Address: This IPv6 address is assigned to the uplink interface of the hub. It is
the forward link next-hop address to route traffic from the hub towards the terminal IP
subnets. For more information on uplink connectivity, refer to Uplink Network Connectivity
on page 154.
addresses (two for the hub (redundant DEM VMs), one for your edge router), therefore the
minimal IPv6 prefix length is 125. For more information, refer to
Uplink Network Connectivity on page 154.
– Uplink DNS Proxy Addres: This IPv6 address is used by the DEM VM to send requests to



7. Configure the routing protocol. The Dialog platform supports three routing methods. Select the
Type of routing in the drop-down list.
Type is Static.
The parameters displayed depend on the selected IP versions of the uplink.
Set the parameters:

– Default Gateway IPv4: This parameter is available when the uplink supports IPv4. It is the
default gateway for IP traffic coming from the terminals. This unique IPv4 address must be
in the range that is specified in the IPv4 Uplink configuration.
– Default Gateway IPv6: This parameter is available when the uplink supports IPv6. This is
the default gateway for the IP data coming from the terminals. This unique IPv6 address
must be in the range that is specified in the IPv6 Uplink configuration.
Type is OSPF.
Set the parameters:

– OSPF Router-ID: This is the IPv4 address used by DEM as identifier in the OSPF protocol
(useful for OSPF debugging).
– OSPF Area ID: This is the OSPF area identifier (integer value) used between the DEM
device and edge router(s).
Make sure that the OSPF area ID is configured on the edge router as well.
– OSPFv2 Password: This is the password used for OSPF authentication between the DEM
device and the edge router(s) (IPv4 only).

Type is BGP.
BGP is only supported for IPv4. Make sure to enable the IPv4 uplink in case you
want to use BGP.
Set the parameters:

– BGP Router-ID: This is the IPv4 address assigned to the uplink interface of the DEM. It is
automatically entered.
– Local AS: This is the BGP Autonomous System, which is used in the Newtec Dialog
platform.
– BGP Neighbors: Click + Add to add a BGP neighbor.
• Name: Give the BGP neighbor a name
• IP Address: This is the IPv4 address of the BGP neighbor.
• AS: When using iBGP, this number should be the same as the Local AS number.
• Password: This is the password used for BGP authentication between BGP
neighbors. The same password should be configured on the BGP neighbor itself.
Using a password is recommended when using eBGP.
• Keep Alive Time: When a BGP neighbor has no update messages to send, it
periodically sends keep alive messages to keep the BGP session alive.
• Hold Time: The hold time specifies how long a router will wait for incoming BGP
messages (update or keep alive) before it assumes the neighbor is dead.
• Preference: BGP routers typically receive multiple paths to the same destination. The
BGP Best Path selection algorithm makes basic decisions to select the best routes to
be installed into the routing table. To customize the Best Path selection process, you
can set a cost number value, which determines the preference for the path. The path
with the lowest value is preferred.
• Max Routes Learned: This is the maximum number of routes, which can be learned
from this neighbor. In case this maximum number is reached, DMA will report an
alarm.
Set the Export parameters, which allows you to configure the AS path prepend option.
Prepending means adding one or more AS numbers to the left side of the AS path. Since
BGP prefers a shorter AS path, you can influence the Best Path selection on the router of
your peer by using this option.
• Number of prepends Added: Defines the number of times the AS number should be
prepended. Value 0 disables AS path prepending.

• AS Path Prepend: Defines the AS number to prepend. The number should be

different from the BGP neighbor's AS.
Set the Import mode, which allows you to filter incoming paths for this BGP neighbor.
• Mode
• All: All routes are learned.
• Default Gateway only: Only a new default gateway is learned. This is the
configuration typically used at the hub side).
• Filtered: Select a predefined BGP profile. For more information about BGP profiles
and filters, refer to Manage BGP Profiles on page 225.
• None: No routes are learned.
Click Confirm to create the BGP neighbor or click Cancel to discard the settings.
You can add multiple BGP neighbors.
Click in the Actions column to edit the BGP neighbor.
Click in the Actions column to delete the BGP neighbor.
8. Link the VNO. When the identifier prefix is the HNO domain name (see Network Tab), you
should link the subnet to one or more VNO domain names. Only VNO domains that are linked
can use the subnets for their terminals. The VNO Linking tab is not available when the identifier
prefix of your network is a VNO domain name (see Network Tab). In this case the subnet is
automatically linked to that VNO domain.
9. Click Apply to create the subnet or click Discard to cancel. Check the log panel for validation
messages.
Click on the subnet in the overview to edit the parameters.
Click in the Actions column to delete the subnet.
9.3.3 How to Create a Shared Subnet
Only the Hub Network Operator (HNO) can create a shared subnet.
To create a shared subnet, execute the following steps:

2. Click Network Provisioning in the surveyor tree or in the visual overview.

3. Click + Create New Network.

A window appears where you can configure the network, uplink and routing protocol.
Make sure to set Type to Shared Subnet.
4. Configure the network.

Set the parameters:

– Service Label: Label that allows to group subnets, which are spread over multiple satellite
another. Refer to Service Labels on page 158 for more information. This parameter is
optional.
– Hub Termination Point: Select the identifier of the hub termination point that applies to the
subnet.
– IPv4/IPv6 Uplink Enabled: Click the button to indicate which the IP version is supported
on the uplink between the DEM and the customer edge router. At least one uplink (IPv4 or
IPv6) is required.
– Mobile Backhaul Network: Enable this parameter to indicate that the subnet is used for
mobile connectivity and carries GTP traffic. Only when a network is marked as a mobile
backhaul network, the system will identify the traffic as GTP-U traffic and be able to perform
traffic optimization inside the GTP tunnel. For more information on how to perform GTP
optimization, refer to GTP Optimization for Mobile Backhauling on page 348.
It is recommended that Mobile Backhaul is used only in dedicated networks.
• GTP-U is implemented on top of UDP. When the subnet is marked as a for mobile
backhaul network, the GTP Port needs to be specified. The default value is 2152.
– Internal Terminal to Terminal Communication: When enabled, communication between
terminals provisioned in the same subnet does not leave the hub. When disabled, the
communication is routed through the customer's edge router.

Set the parameters:

– Uplink IP Address: This IPv4 address is assigned to the uplink interface of the DEM. It is
used as next-hop address to route traffic from the hub towards the terminal IP subnets. For
more information on uplink connectivity, refer to Uplink Network Connectivity on page 154.
addresses (two for the DEMs, one for your edge router), therefore the minimal IPv4 prefix
length is 29. Refer to Uplink Network Connectivity on page 154.
– Uplink DNS Proxy Addres: This IPv4 address is used by the DEM to send requests to



Set the parameters:

– Uplink IP Address: This IPv6 address is assigned to the uplink interface of the DEM. It is
used as next-hop address to route traffic from the hub towards the terminal IP subnets.
addresses (two for the DEMs, one for your edge router), therefore the minimal IPv4 prefix
length is 125. Refer to Uplink Network Connectivity on page 154.
– Uplink DNS Proxy Addres: IP address used by the DEM device to send requests to
external DNS servers. Refer to DNS on page 154 for more information.


7. Configure the routing protocol. The Dialog platform supports three routing methods. Select the
Type of routing in the drop-down list.
Type is Static.

The parameters displayed depend on the selected IP versions of the uplink.
Set the parameters:

– Default Gateway IPv4: This parameter is available when the uplink supports IPv4. It is the
default gateway for IP traffic coming from the terminals. This unique IPv4 address must be
in the range that is specified in the IPv4 Uplink configuration.
– Default Gateway IPv6: This parameter is available when the uplink supports IPv6. This is
the default gateway for the IP data coming from the terminals. This unique IPv6 address
must be in the range that is specified in the IPv6 Uplink configuration.
Type is OSPF.
Set the parameters:

– OSPF Router-ID: This is the IPv4 address used by DEM as identifier in the OSPF protocol
(useful for OSPF debugging).
– OSPF Area ID: This is the OSPF area identifier (integer value) used between the DEM
device and edge router(s).
Make sure that the OSPF area ID is configured on the edge router as well.
– OSPFv2 Password: This is the password used for OSPF authentication between the DEM
device and the edge router(s) (IPv4 only).
Type is BGP.
BGP is only supported for IPv4. Make sure to enable the IPv4 uplink in case you
want to use BGP.

Set the parameters:

– BGP Router-ID: This is the IPv4 address assigned to the uplink interface of the DEM. It is
automatically entered.
– Local AS: This is the BGP Autonomous System, which is used in the Newtec Dialog
platform.
– BGP Neighbors: Click + Add to add a BGP neighbor.
• Name: Give the BGP neighbor a name
• AS: When using iBGP, this number should be the same as the Local AS number.
• Password: This is the password used for BGP authentication between BGP
neighbors. The same password should be configured on the BGP neighbor itself.
Using a password is recommended when using eBGP.
• Keep Alive Time: When a BGP neighbor has no update messages to send, it
periodically sends keep alive messages to keep the BGP session alive.
• Hold Time: The hold time specifies how long a router will wait for incoming BGP
messages (update or keep alive) before it assumes the neighbor is dead.
• Preference: BGP routers typically receive multiple paths to the same destination. The
BGP Best Path selection algorithm makes basic decisions to select the best routes to
be installed into the routing table. To customize the Best Path selection process, you
can set a cost number value, which determines the preference for the path. The path
with the lowest value is preferred.
• Max Routes Learned: This is the maximum number of routes, which can be learned
from this neighbor. In case this maximum number is reached, DMA will report an
alarm.
Set the Export parameters, which allows you to configure the AS path prepend option.
Prepending means adding one or more AS numbers to the left side of the AS path. Since
BGP prefers a shorter AS path, you can influence the Best Path selection on the router of
your peer by using this option.
• Number of prepends Added: Defines the number of times the AS number should be
prepended. Value 0 disables AS path prepending.
• AS Path Prepend: Defines the AS number to prepend. The number should be
different from the BGP neighbor's AS.
• Mode

• All: All routes are learned.

• Default Gateway only: Only a new default gateway is learned. This is the
configuration typically used at the hub side).
• Filtered: Select a predefined BGP profile. For more information about BGP profiles
and filters, refer to Manage BGP Profiles on page 225.
• None: No routes are learned.
Click in the Actions column to edit the BGP neighbor.
8. Click Apply to create the subnet or click Discard to cancel. Check the log panel for validation
messages.
Click on the subnet in the overview to edit the parameters.
Click in the Actions column to delete the subnet.
9.3.4 How to Create IPv4 Pools
Only the Hub Network Operator or HNO can create an IP pool.
To create an IPv4 pool, execute the following steps:

2. Click IPv4 Pools Provisioning in the surveyor tree or in the visual overview.

3. Click + Create New Pool.

A window appears where you can configure the IPv4 pool and the VNO access right.
4. Configure the IPv4 pool.
Set the parameters:

– Identifier: The identifier is the combination of a domain name and an arbitrary name. You
can select the HNO or a VNO domain name. The arbitrary name should be unique within

– Satellite Network: Select the satellite network from the drop-down list where the IP pool
can be used.
– Service Label: Label that allows to group IP pools which are spread over multiple satellite
another. Refer to Service Labels on page 158 for more information.
– IPv4 Address Ranges: Click + Add to add a range.
• Network Address: This is the IPv4 network address of the IP range.
• Prefix Length: This is the size of the IP range. The number is the count of leading 1
bits in the subnet mask (CIDR notation).
Click to validate the IP address or click to discard the setting.

You can add multiple ranges. If multiple address ranges are configured, click and drag
in the Actions column to change the order of the IP address ranges. Ranges are
iterated based on their Index. IP addresses are automatically picked from the top range
until this range has no more IP addresses to assign. When this occurs, the second range is
used until exhausted, and so on until the last range is exhausted.
Click in the Actions column to edit the address range. You cannot edit the
address range once the IPv4 pool has been created.
Click in the Actions column to delete the address range.
5. Link the VNO. When the identifier prefix is the HNO domain name, you should link the IPv6
pool to one or more VNO domain names. Only VNO domains that are linked can use the IPv4
pools for their terminals. The VNO Linking tab is not available when the identifier prefix of your
IP pool is a VNO domain name. In this case the IP pool is automatically linked to that VNO
domain.
messages.
The overview indicates the number of free addresses in the address range as well as
the number of total addresses available.
Click on the IP pool in the overview to edit the parameters. You cannot edit the
address range, you can only delete it.
Click in the Actions column to delete the IP pool.

9.3.5 How to Create IPv6 Pools
Only the Hub Network Operator or HNO can create an IP pool.
To create an IPv6 pool, execute the following steps:

2. Click IPv6 Pools Provisioning in the surveyor tree or in the visual overview.
3. Click + Create New Pool.

A window appears where you can configure the IPv6 pool and the VNO access right.
4. Configure the IPv6 pool.

Set the parameters:

– Identifier: The identifier is the combination of a domain name and an arbitrary name. You
can select the HNO or a VNO domain name. The arbitrary name should be unique within
– Satellite Network: Select the satellite network from the drop down list where the IP pool
can be used.
– Service Label: Label that allows to group IP pools, which are spread over multiple satellite
another. Refer to Service Labels on page 158 for more information.
– Terminal LAN Prefixes Length: This is the maximum prefix length of the IPv6 prefix
range(s) used within this IPv6 pool. Typically smaller sub networks from this prefix range
are distributed to all assigned terminals.
– Terminal Routed Prefixes Length: This is the maximum prefix length of the distributed
routed prefixes.
– IPv6 LAN Prefix Ranges: Click + Add to add a range.
• Network Address: This is the IPv6 network address of the LAN prefix range.
• Prefix Length: This is the size of the LAN prefix range. The number is the count of
leading 1 bits in the subnet mask (CIDR notation). This prefix length must be smaller
than the prefix length defined in the Terminal LAN Prefixes Length.
Click to validate the range or click to discard the setting.

in the Actions column to change the order of the ranges. Ranges are iterated
based on their Index. IP addresses are automatically picked from the top range until this
range has no more IP addresses to assign. When this occurs, the second range is used
until exhausted, and so on until the last range is exhausted.

Click in the Actions column to edit the address range. You cannot edit
the address range once the IPv6 pool has been created.
– IPv6 Routed Prefix Ranges: Click + Add to add a range.

• Network Address: This is the IPv6 network address of the routed prefix range.
• Prefix Length: This is the size of the routed prefix range. The number is the count of
leading 1 bits in the subnet mask (CIDR notation). This prefix length must be smaller
than the prefix length defined in the Terminal Routed Prefixes Length.
Click to validate the range or click to discard the setting.

in the Actions column to change the order of the ranges. Ranges are iterated
based on their Index. IP addresses are automatically picked from the top range until this
range has no more IP addresses to assign. When this occurs, the second range is used
until exhausted, and so on until the last range is exhausted.
Click in the Actions column to edit the address range. You cannot edit
the address range once the IPv6 pool has been created.
5. Link the VNO. When the identifier prefix is the HNO domain name, you should link the IPv6
pool to one or more VNO domain names. Only VNO domains that are linked can use the IPv6
pools for their terminals. The VNO Linking tab is not available when the identifier prefix of your
IP pool is a VNO domain name. In this case the IP pool is automatically linked to that VNO
domain.
messages.
The overview indicates the number of free addresses in the address range as well as
the number of total addresses available.
Click on the IP pool in the overview to edit the parameters. You cannot edit the
address range, you can only delete it.
Click in the Actions columnto delete the IP pool.
9.4 How to Create Layer 2 Network Resources
Layer 2 network resources can only be configured on a 4IF or XIF hub module with HP
switches.
Configuring layer 2 network resources require the following sequential steps:

• Create a Hub Termination Point. A hub termination point is the point where the customer’s network
ends and connects to the Newtec Dialog network. It corresponds with the demarcation point.
• Create a layer 2 point-to-point virtual connection.
9.4.1 How to Create a Hub Termination Point
Only the Hub Network Operator or HNO can create a hub termination point.
To create a Hub Termination Point, execute the following steps:

2. Click Hub Termination Point Provisioning in the surveyor tree or in the visual overview.
3. Click + Create Hub Termination Point.
termination point based on the settings of an existing one.

A window appears where you can configure the hub termination point and the VNO access
rights.
Make sure to set Type to Layer2.
4. Configure the hub termination point.
Set the parameters:

– Hub Module: The name of the hub module on which the hub termination point should be
defined.
– VLAN ID: This is the uplink VLAN identifier. Enter a value between 2-1001, 1006-2999 or
3501-4094. This VLAN ID should be unique within the hub module. At the customer’s side,
the Ethernet ports on the edge router should be configured in 'trunking' mode, containing
the uplink VLAN ID. The VLAN ID can be untagged.
When a VLAN ID value is entered, the layer 2 VC will be identified by 2 VLAN tags (dual
VLAN case or QinQ mode). When the VLAN ID is untagged, the layer 2 VC is identified by
1 VLAN (single VLAN case).
5. Link the VNO. You can link one or more VNO domain names to a hub termination point. Only
VNO domains that are linked are allowed to use the hub termination point for their subnets.
messages.
Click on the hub termination point in the overview to edit the parameters.
Click to delete the hub termination point.
9.4.2 How to Create a Layer 2 VC

A layer 2 point-to-point virtual connection is created during terminal provisioning. For more
information on how to create a layer 2 VC, refer to How to Configure Layer 2 Settings on page 258,
which is part of terminal provisioning.

Manage Classification Profiles
10 Manage Classification Profiles
10.1.1 Classification
Classification organizes ingress unicast traffic into QoS traffic classes. The ingress traffic is
classified based on rules. A rule is a set of one or more criteria such as protocol, source/destination
IP addresses, source/destination ports, network service labels, DSCP values, VLAN tag, ... The rule
which matches first is applied. If multiple criteria are defined in a rule, all criteria (AND functionality)
must match to apply that rule.
The rules are set in a classification profile. The terminal is configured with a forward and return
ingress classification profile during terminal provisioning. on page 232 The classification profiles for
the forward and return link do not need to be identical.
Different rules apply for layer 3 unicast traffic and layer 2 point-to-point traffic.
It is not possible to have a layer 2 and layer 3 classification rule for the same traffic class
within a classification profile.
The table below shows a typical mapping example between a service and traffic class.
Service Traffic Class Description
VoIP telephony Real Time Telephony has a maximum tolerable latency and jitter,
while it is immune to certain packet loss, therefore, VoIP
traffic must be classified as Real Time
Transactional Data Critical Data In transactional data, while certain delay and jitter is
and bulk data permitted, no packet loss is allowed, therefore, it must be
classified as Critical Data
Non-critical data Best Effort Non-critical data can be handled without priority,
therefore, it can be classified as Best Effort
A "best-effort-only" classification profile is by default defined on the system. This classification profile
classifies all ingress layer 3 traffic into the Best Effort traffic class. It cannot be removed from the
system.
Additionally, in any created classification profile there's always an implicit layer 3 rule, which
classifies layer 3 traffic that does not match the rules that you have created as Best Effort traffic.

10.1.2 Inherit QoS Classification

In some cases, a Deep Packet Inspection (DPI) device is placed between the Dialog system and the
Internet. A DPI device inspects traffic flows up to application level. Hence it can recognize a traffic
flow as an application and mark the DSCP value of the packets within this traffic flow.
It can take several packets before a flow is detected by the DPI device. The DPI device will re-mark
the packets and change the DSCP values of subsequent packets for that application. The Dialog
system will detect the change of the DSCP value and give the packet another QoS behavior.
DPI devices are rather expensive and it is very likely that such device is not used at the remote
modem side. However you want the remote modem to apply the same classification as set at the
hub side. In that case you can set the Remote Side QoS Classification parameter, which can be
found in the classification profile. When this parameter is set to Inherit QoS classification, QoS
classification at the remote (receiving) side applies the same QoS classification as the sending side
for a certain flow of packets.
Let's consider the following example. A VoIP call is setup towards an IP phone behind a modem.
The DPI device inspects the VoIP packets, however the first packets arrive at the Dialog hub before
any action of the DPI device occurs. The Dialog system applies classification based on the rules of
the Forward link classification profile that match the first incoming VoIP packet. In our example, the
first VoIP packet ends up in the Best Effort queue. A few packets later, the DPI device recognizes
the traffic flow as VoIP and marks this traffic with a DSCP value. The hub now receives marked VoIP
packets and applies the corresponding rule within the forward link classification profile. In our
example the VoIP packets now end up in the Real-time 1 queue.
There is no DPI device at the terminal side, so no marking is applied on the terminal side.
Consequently the VoIP packets sent via the return link get classified according the classification
profile of the return link. In our example, they end up in the Best-Effort queue. However, by setting
the Inherit QoS Classification parameter in the return link classification profile, the returned VoIP
packets end up in the real-time 1 queue and VoIP is treated the same as in the forward link.
Following guidelines must be considered when using this feature:

• Use separate classification profiles for the forward and return link. Using the same classification
profile with Inherit QoS Classification enabled on both forward and return link is not allowed, as
this could result in a loop.
• Make sure that the service profile has CIR and/or PIR for the inherited QoS Class.
10.1.3 Marking
After classification, ingress traffic is marked. The Dialog system supports marking based on
Differentiated Services or DiffServ. DiffServ is a method to mark packets in their 6-bit Differentiated
Services Code Point or DSCP field in the IP header. Each tag corresponds to a Class of Service or
CoS. Packets with the same CoS have the same QoS policies applied in the network nodes.

Marking can be done by an external device (for example a packet shaper) or inside the Newtec
Dialog system.
The marking policy is set in a classification profile.
Two policies exist:
• Transparent: Incoming traffic which is already marked, passes the Newtec Dialog system without
any modification. In other words, the same marking is still applied at egress.
When external DSCP marking is applied on the ingress traffic, you should define
rules that correspond to the applied DSCP marking.
• Mark: Incoming traffic, which is not yet marked, is marked by the Newtec Dialog system at egress
based upon the internal DSCP settings. Internal DSCP settings are set via the
Forward Link web interface on page 49 (advanced settings) or the Return Link web interface on
page 93.

10.2 How to Open the Classification Profiles Web Interface

To open the web interface of the Classification Profiles, execute the following steps:
3. Click Profiles in the surveyor tree or in the visual overview.
4. Click Classification Profiles Provisioning in the surveyor tree or in the visual overview.

10.3 How to Create a Classification Profile
A best-effort-only profile is defined on the system by default. It classifies all ingress

layer 3 traffic into the Best Effort traffic class. It is used as the "last-resort" profile in
case no other profiles match. This classification profile cannot be removed from the
system.
The introduction of Flow Fairness may require customers upgrading from Dialog R2.2.3
or lower to review and adapt the configuration to ensure that time-sensitive applications
are allocated with the right priority.
For this reason, mind that:
• RT1 and RT2 classes are built with smaller QoS queues sizes, and are meant to be
used for applications sensitive to latency and jitter, such as VoIP or SCADA, but not for

applications such as broadcast contribution.

• TCP traffic should not be used as RT1 or RT2.
• Depending on the application, UDP traffic must be prioritized over TCP traffic. In
previous Dialog releases, UDP always had priority over TCP. Customers must
configure QoS classification rules accordingly.
For more information, refer to the Newtec Dialog Functional Description Manual.
To create a Classification Profile, execute the following steps:

1. Open the Classification Profiles provisioning interface as described in
How to Open the Classification Profiles Web Interface on page 191.
3. Click + Create New Profile.
Alternatively, you can click the copy icon in the Actions column to create a new profile
A window appears where you can configure the profile, the rules and the VNO access rights.
4. Configure the classification profile.
Set the parameters:

– Identifier: The identifier is the combination of a domain name and an arbitrary name. The
domain name can be the HNO domain name or a VNO domain name. The arbitrary name
– Packet Marking Mode: This indicates which marking policy is applied on the classification
profile (and all of its rules).
• Transparent: Incoming traffic passes the Newtec Dialog system without any
modification. In other words, the same marking is still present at egress.
• Mark: Incoming traffic, which is not yet marked, gets marked by the Newtec Dialog
system at egress based upon the internal DSCP settings.
It is allowed to configure a forward ingress classification profile using

transparent marking, and a return ingress classification profile with the
marking policy set as Mark.
– Remote Side QoS Classification: Used to trigger the remote (receiving) side to apply the
same QoS classification as set at the sending side for certain flow of packets or not.
• No impact: Classification is based on the local settings, which are defined in the
applicable classification profiles. This is the default value. Behavior is the same as the
packet marking mode (mark or transparent).

• Inherit QoS Classification: QoS classification at the remote (receiving) side applies
the same QoS classification as the sending side for certain flow of packets. This
setting is typically used when a Deep Packet Inspection (DPI) device is used. For more
information, refer to Inherit QoS Classification on page 189.
5. Create layer 3 rules.
You should create at least one layer 3 or layer 2 rule.
– Click + Add.
– Enter the parameters:
• Traffic Class: Select the QoS traffic class to be used for the traffic when the traffic
matches the rule. If a traffic class is already used in layer 2 rules, it will not be available
for layer 3 rules.
The number of CD classes that you can use depends on the return link
technology used by the terminal and the shaping model.
You can use three critical-data classes (CD1..3) in the class-based shaping
model and in the transport-based shaping model with return link technology
MF-TDMA 4CPM. You can use 14 critical-data classes (CD1..14) in the
transport-based shaping model with return link technologies Mx-DMA HRC
and NxtGen Mx-DMA MRC.
• DSCP: Set the DSCP value. You can include (is) or exclude (is not) a DSCP value.
When included, the ingress traffic should have the same DSCP value in order to match
the rule. When excluded, the ingress traffic should have a different DSCP value in
order to match the rule.
When external DSCP marking is applied on the ingress traffic, you should
define rules that correspond to the applied DSCP marking. The marking
policy must also be set to Transparent in order to keep the DSCP values at
egress of the Dialog system. If the marking policy is set to Mark, the internal
DSCP values would override the external DSCP settings.
• Protocol: Set the Internet Communication Layer protocol of the ingress traffic.
• Source Port: Set a range of source ports. You can include or exclude the ports. When
included, the ingress traffic should have a source port within the range in order to
match the rule. When excluded, the ingress traffic should have a source port outside
the range in order to match the rule.
• Destination Port: Set a range of destination ports. You can include (is) or exclude (is
not) the ports. When included, the ingress traffic should have a destination port within

the range in order to match the rule. When excluded, the ingress traffic should have a
destination port outside the range in order to match the rule.
• Source IPv4 Address Range: Set the IPv4 source network address and prefix length.
You can include (is) or exclude (is not) source addresses. When included, the ingress
traffic should have an IPv4 source address within the range in order to match the rule.
When excluded, the ingress traffic should have an IPv4 source address outside the
range in order to match the rule.
• Destination IPv4 Address Range: Set the IPv4 destination network address and
prefix length. You can include (is) or exclude (is not) destination addresses. When
included, the ingress traffic should have an IPv4 destination address within the range in
order to match the rule. When excluded, the ingress traffic should have an IPv4
destination address outside the range in order to match the rule.
• Source IPv6 Address Range: Set the IPv6 source network address and prefix length.
You can include (is) or exclude (is not) source addresses. When included, the ingress
traffic should have an IPv6 source address within the range in order to match the rule.
When excluded, the ingress traffic should have an IPv6 source address outside the
range in order to match the rule.
• Destination IPv6 Address Range: Set the IPv6 destination network address and
prefix length. You can include (is) or exclude (is not) destination addresses. When
included, the ingress traffic should have an IPv6 destination address within the range in
order to match the rule. When excluded, the ingress traffic should have an IPv6
destination address outside the range in order to match the rule.
• Service Label: Select the service label. You can include (is) or exclude (is not) a
service label. When included, the ingress traffic should belong to the subnet, which
has the service label assigned, in order to match the rule. When excluded, the ingress
traffic should belong to a subnet that does not have the service label assigned, in order
to match the rule. For more information on how to use the service label, refer to
Use of Service Label in Classification Profiles on page 161.
Click the condition buttons (is / is not) to change the matching condition.
Keep in mind that all criteria must match in order to apply the rule.
– Click Confirm to create the rule or click Cancel to discard the settings.
– You can add multiple rules. If multiple rules are configured, click and drag in the
Actions column to change the order of the rules. Rules are checked based on their Index:
When the first rule does not match, the next rule is checked, and so on.
Click in the Actions column to edit the rule parameters.
Click in the Actions column to delete the rule.
6. Create layer 2 rules.
You should create at least one layer 3 or layer 2 rule.

– Click + Add.
– Set the parameters:
• Traffic Class: Select the QoS traffic class to be used for the traffic when the traffic
matches the rule. If a traffic class is already used in layer 3 rules, it will not be available
for layer 2 rules.
The number of CD classes that you can use depends on the return link
technology used by the terminal and the shaping model.
You can use three critical-data classes (CD1..3) in the class-based shaping
model and in the transport-based shaping model with return link technology
MF-TDMA 4CPM. You can use 14 critical-data classes (CD1..14) in the
transport-based shaping model with return link technologies Mx-DMA HRC
and NxtGen Mx-DMA MRC.
• DSCP: Set the DSCP value. You can include (is) or exclude (is not) a DSCP value.
When included, the ingress traffic should have the same DSCP value in order to match
the rule. When excluded, the ingress traffic should have a different DSCP value in
order to match the rule.
When external DSCP marking is applied on the ingress traffic, you should
define rules that correspond to the applied DSCP marking. The marking
policy must also be set to Transparent in order to keep the DSCP values at
egress of the Dialog system. If the marking policy is set to Mark, the internal
DSCP values would override the external DSCP settings.
• PCP: Set the Priority Code Point value for the ingress traffic in order to match the rule.
The PCP value is a 3-bit value in the Layer 2 VC VLAN tag.
• VLAN Tag: Set the Layer 2 VC VLAN tag for the ingress traffic in order to match the
rule. The value can be an integer between 1 and 4095.
• Layer 2 VC Group ID: Set the Layer 2 VC group ID. The ingress traffic should belong
to the Layer 2 VC, which has the group ID assigned, in order to match the rule. The
group ID is defined in the terminal provisioning interface and allows to identify a set of
Layer 2 VCs.
Layer 2 VC Group ID and VLAN Tag are mutually exclusive.
Keep in mind that all criteria must match in order to apply the rule.
– Click Confirm to create the rule or click Cancel to discard the settings.

– You can add multiple rules. If multiple rules are configured, click and drag in the
Actions column to change the order of the rules. Rules are checked based on their Index:
When the first rule does not match, the next rule is checked, and so on.
Click in the Actions column to edit the rule parameters.
7. Set the access rights.
When the identifier prefix is the HNO domain name (see Classification Profile Tab), you should
link the classification profile to one or more VNO domain names. Only VNO domains that are
linked can use the classification profiles for their terminals. When selecting a VNO domain, the
toggle button Domain Defaults appears. Enable the Domain Defaults parameter if you want to
use this classification profile as the default profile during terminal provisioning for that VNO.
When the identifier prefix of your classification profile is a VNO domain name you will not be
able to select another VNO and you will only see the Domain Defaults button.
8. When all tabs have a green check symbol, click Apply to create the classification profile or click
Discard to abort. Check the log panel for validation messages.
Click on the classification profile in the overview to edit the parameters.
Click in the Actions column to delete the classification profile.

Manage Service Profiles
11 Manage Service Profiles

A service profile specifies the shaping settings for the terminal circuits and QoS classes. The service
profile is part of the Dialog shaping model.
11.1.1 Service Profile Types

Two types of service profile exist: class-based pool and transport-based pool. The type defines the
shaping model. The service profile can be dedicated to a VNO or shared between VNOs.
• Class-based: In a class-based service offering, the service provider offers applications to
customers. On the individual terminal level, the applications are classified and mapped to QoS
classes and the QoS classes are shaped according to the terminal's service profile and the
individual QoS class priority. The class-based service profile defines the shaping settings of the
QoS classes. On an aggregate level, the applications of the terminals will contend for bandwidth in
case of congestion and the service provider will typically prioritize the higher priority applications
but also protect the lower priority applications from being starved. A part of the satellite resources
needs to be reserved for such class-based services.
• Transport-based: In a transport-based service, a customer rather buys a bandwidth pipe that has
a committed rate, sometimes burstable to a higher rate. The terminals are directly linked to the
forward/return pools and contention happens between terminals and not between applications.
Prioritization of customer hosted applications is managed within the bandwidth pipe by the
customer himself using the terminal's service profile and the individual QoS class priority. The
transport-based service profile defines the shaping settings of the terminal circuit and the
individual QoS classes. This type of service is comparable with the concept of a leased line
(except that unused bandwidth within a pipe can be distributed amongst other transport-based
customers if necessary).
Terminals are linked to a service profile and to forward and return resources during
terminal provisioning on page 232. The type of service profile determines which forward and return
resources can be assigned: you can only select transport-based forward and return pools with a
transport-based service profile and class-based forward and return pools with class-based service
profiles. For more information on how to create forward and return pools, refer to
Manage Forward Link Resources on page 25 and Manage Return Link Resources on page 73.
The shaping tree for both shaping models is shown in the figure below.


• Shaping Level 1: At this level the total capacity is represented. For the forward link the total
capacity corresponds with the entire satellite network; for the return link this corresponds with the
return capacity group.
• Shaping Level 2: At this level the root pool or container capacity is divided over forward/return
(and multicast) pools.
• Shaping Level 3: In case the pool is class-based, shaping level 3 represents the QoS pools. In
case of transport-based pools, shaping level 3 represents the terminal circuits. In case of multicast
pools, shaping level 3 represents the multicast circuits.
• Shaping Level 4: This shaping level represents the QoS classes.
In a class-based service offering, terminals are linked to QoS pools. In a transport-based service
offering, terminals are linked directly to the transport-based pool. In the class-based setup terminals
are at shaping level 4 and in the transport-based setup terminals are at shaping level 3.
In the transport-based shaping model, you can have one extra level: CD aggregation node. This
node allows you to aggregate two or more CD classes. The CD classes inside the node compete
with each other for bandwidth and the aggregation node competes for bandwidth with the QoS
classes outside the node.
The number of CD classes that you can use depends on the return link technology used by the
terminal and on the shaping model. You can use three critical-data classes (CD1..3) in the
class-based shaping model, and in the transport-based shaping model with return link technology
MF-TDMA 4CPM. You can use 14 critical-data classes (CD1..14) in the transport-based shaping
model with return link technologies Mx-DMA HRC and NxtGen Mx-DMA MRC.
When managing service profiles, it is important to keep the "parent/child" relationship between the
service profile and linked forward/return resources in mind. For example, if you create a service
profile that uses a forward CIR of 500 kbps which is linked to a forward pool of 1 Mbps CIR, you can
only assign this service profile to two terminals, unless CIR overbooking is allowed in the forward
pool.
11.1.2 Queuing
Each QoS class has a queue size and time. The queue time or shaping timeout is configurable.

QoS Class Max. Queue Size Default Queue Time
Forward Return Forward Return
Real Time 1, 2 50 MB 2.56 MB 50 ms 90 ms
Real Time 3 50 MB 2.56 MB 50 ms S2: 200 ms

4CPM: 2 s
HRC: 400 ms
MRC: 400 ms
Critical Data 1..14 2.56 MB 2.56 MB 200 ms S2: 200 ms

4CPM: 2 s
HRC: 400 ms
MRC: 400 ms
Best Effort 2.56 MB 2.56 MB 200 ms S2: 200 ms

4CPM: 2 s
HRC: 400 ms
MRC: 400 ms
The queue is filled with packets at the data rate of the customer application, but the packets are
queued only for the shaping timeout time and up to the maximum queue size. Therefore, for
applications with a data rate that exceeds the queue size and time, excess packets are dropped.
11.1.3 Allocation Type

For MRC NxtGen Mx-DMA, HRC Mx-DMA and 4CPM MF-TDMA you can define how bandwidth
should be allocated. There are three different types of allocation:
• Static: The terminal receives the configured CIR, even if the terminal did not send a request. A
use case for this allocation type is video streaming, for which a continuous channel needs to be
available.
• Dynamic Ingress Rate or DIR: The terminal receives only the amount of capacity it requests. This
allocation type can be used for traffic types which have the ability to buffer data. Hence the
capacity requests from one or more terminals are determined by the (variable) size of buffered
data. When using this allocation type, it is possible to specify a Request Margin. This is
considered as an extra amount of bandwidth a terminal always receives, on top of the requested
amount.
• Dynamic Full Rate or DFR: The terminal receives all of the configured capacity as soon as any
capacity is requested. This allocation type is useful for VoIP traffic, as the terminal needs to have
the CIR at the moment the call is ongoing. When the call is finished, the bandwidth becomes
available again for others (so no need for a "continuous" link as would be the case with a
permanent video streaming).
The allocation type is set in the service profile. It can be specified for:
• Transport-based service profiles;
• Real Time 1 and 2 return QoS classes in a class-based service profile. For the other QoS classes,
the allocation type is always DIR.
The example below show the effect and (dis)advantages of the allocation types.

The example assumes that the terminal has a CIR configured to support up to two simultaneous
voice calls, and that a second call sets up during an active first call.
In case of the static allocation type, the required bandwidth is always available, even when there are
no active calls. There is enough bandwidth available at the setup of each call and during
simultaneous calls. However this is not efficient bandwidth usage, as the bandwidth is allocated but
unused when no calls are active.
In case of the dynamic full rate allocation type, the full CIR capacity becomes available but only
after the first call setup. This has the disadvantage that at the start of the first call, there is no
bandwidth available yet (available bandwidth lags behind the call). The advantage of this allocation
type is that there is already bandwidth available when the second call needs to start. At the end of
the second call, the resources are no longer required and become available for other requests.
In case of the dynamic ingress rate allocation type, only the requested amount of capacity for the
first call becomes available after the first call setup. At the start of the call, there is no bandwidth
available yet. At the end of the second call, the resources are no longer required and become
available for other requests

The lack of bandwidth at the start of the call can be solved by using the request margin. The
request margin ensures that bandwidth is available at the setup of the first call as well as the second
call. At the end of the second call, the resources for the calls are no longer required and become
available for other requests. The requested margin however remains allocated and can be
considered as 'wasted' when no calls are active.
11.1.4 ACM in HRC Mx-DMA and MRC NxtGen Mx-DMA

The minimum and maximum MODCOD for ACM can be set per HRC Mx-DMA and MRC NxgGen
Mx-DMA Return Capacity Groups (for more information, refer to
How to Create an HRC Return Capacity Group on page 101 and
How to Create an MRC Return Capacity Group on page 110). Terminals that use this return capacity
group are bound to these MODCOD limits. However, it is possible to set the maximum MODCOD
and minimum and maximum symbol rate per terminal. This is interesting for terminals operating with
VL-SNR or for keeping terminals, which suffer from phase noise (due to BUC frequency instability
for example) under control.
The following parameters control the ACM behavior on terminal level:

• Max Symbol Rate (HRC MxDMA and MRC): Controls the maximum satellite bandwidth usage of
a terminal and reduces the impact on other terminals within the return capacity group. This is
relevant for terminals operating with very Low SNR feature (down to -10 dB). A terminal with a very
robust MODCOD (or a very low SNR MODCOD) can consume a large amount of bandwidth (in
order to keep its configured bit rate or CIR), resulting in large carriers / symbol rates. This impacts

other terminals that are using the same HRC Mx-DMA Return Capacity Group. The parameter is
set in the Service Profile.
• Min Symbol Rate / Max ModCod: Terminals suffering from phase noise have a high packet error
ratio value. Limiting the maximum MODCOD or increasing the minimum symbol rate of such a
terminal, can decrease the packet error ratio value. These parameters are set during terminal
provisioning.
11.2 How to Open the Service Profiles Web Interface

To open the web interface of the Service Profiles, execute the following steps:
4. Click Service Profiles Provisioning in the surveyor tree or in the visual overview.

11.3 How to Create a Transport-based Service Profile

For more information, refer to the Newtec Dialog Functional Description.
To create a transport-based Service Profile, execute the following steps:

1. Open the Service Profile provisioning interface as described in
How to Open the Service Profiles Web Interface on page 203.

3. Select Transport Based in the top menu bar. This also filters the overview to only show the
transport-based service profiles.
4. Click + Create New Service Profile.
A window appears where you can configure the profile and the access rights.
5. Configure the service profile settings.
– Set the general parameter.

• Identifier: The identifier is the combination of a domain name and an arbitrary name.
The domain name can be the HNO domain name or a VNO domain name. The
arbitrary name should be unique within the domain and only support alphanumerical
characters, underscores and hyphens. Blank spaces are not allowed.
– Set the terminal circuit parameters.
• PIR: PIR or Peak Information Rate is the maximum unicast traffic rate for the terminal.
The sum of the QoS class rates of the terminal is limited to this value. The value
should be entered for both the forward and return terminal circuit.
• CIR: CIR or Committed Information Rate is the guaranteed unicast traffic rate for this
terminal. The value should be entered for both the forward and return terminal circuit.

• Weight: The weight is an integer value between 1 and 1000 and is used to define the
Total Weight, which equals PIR * Weight. The total weight is used to distribute the
available bandwidth among the terminals that are linked to the same transport-based
pool. The value should be entered for both the forward and return terminal circuit.
• Allocation Type: The allocation type has an influence on how the satellite capacity is
assigned. Refer to Allocation Type on page 200 for more information.
• Max Symbol Rate (HRC Mx-DMA and MRC): This controls the maximum satellite
bandwidth usage of a terminal and reduces the impact on other terminals within the
HRC Mx-DMA or MRC NxtGen Mx-DMA return capacity group. This is relevant for
terminals operating with very low SNR feature (down to -10 dB). A terminal with a very
robust MODCOD (or a very low SNR MODCOD) can consume a large amount of
bandwidth (in order to keep its configured bit rate or CIR), resulting in large carriers /
symbol rates. This impacts other terminals that are using the same HRC Mx-DMA or
MRC NxtGen Mx-DMA Return Capacity Group). For more information, refer to
ACM in HRC Mx-DMA and MRC NxtGen Mx-DMA on page 202.
• HRC Mx-DMA Request Margin: When the allocation type is set to DIR you can
specify a request margin. The request margin is bandwidth that is always available to
the terminal and is on top of the requested bandwidth. For more information, refer to
Allocation Type on page 200.
• Mrc Keep Alive Timeout: This sets the minimum time for which a logged on terminal
transmits at least one burst. It is not advised to set this parameter to bigger values than
1000 ms.
• Mrc Idle Log Off Time: This sets the time it takes a non-transmitting terminal to
change its state to idle/logged off. This parameter is only meaningful when the MRC
NxtGen Mx-DMA return technology is being used.
Click Show Advanced Settings... to enter the following parameters:
• Average Packet Size: Enter a value in bytes for the average packet size in the return
link or keep the default value.
• External TelliShape Feedback: Click the button to enable or disable TelliShape
feedback to an external multicast source. The feedback contains information about the
TelliShape queues in the modem. Based on this information the source can adapt the
bit rate of the return multicast traffic to use the available return bandwidth.
– Select the QoS class or aggregation node that should be controlled by the service profile
from the drop-down menu. The selections appear as entries in a table.

Set the Forward or Return QoS class parameters.

• PIR (kbps): PIR or Peak Information Rate is the maximum unicast traffic rate for the
QoS class or aggregation node.
• CIR (kbps): CIR or Committed Information Rate is the guaranteed unicast traffic rate
for the QoS class or aggregation node. When the sum of the CIR values exceeds the
CIR value of the circuit, you will receive an overbooking warning. This will not block
the creation of the service profile, but keep in mind that, with CIR overbooking, the CIR
for the QoS classes or aggregation nodes might not be guaranteed.
available bandwidth among the QoS classes or aggregation nodes of the same priority.
• Child nodes: In case of an aggregation node, select a CD QoS class from the
drop-down menu. If a CD QoS class is already configured as a "standalone" QoS class
otr is part of another aggregation node, it can no longer be linked to this aggregation
node. The selected QoS class appears as an sub-entry of the aggregation node. The
parameters that need to be set are the same as described above.
Each QoS class and aggregation node has a fixed priority. The available
bandwidth is first distributed among the classes and nodes with the lowest
priority value.
Click to edit the advanced settings:
There are no advanced settings for Aggregation Nodes.
• Packet Aggregation Timeout: To maximize the use of the payload of an IP packet,

several smaller IP packets can be aggregated into a larger packet. This reduces the IP
overhead but introduces a delay. The value of this parameter is a trade-off between the
delay and the overhead. A smaller value decreases the delay because there is a
shorter waiting time to fill up the buffer but increases the overhead as the buffer may
not be completely full by timeout. For jitter-sensitive real-time applications (typically in
RT1 and RT2 QoS class) it is advised to set the timeout value to 1 ms. Mind that
disabling aggregation (0 ms) has a negative impact on performance and CPU usage.
• Packet Shaping Timeout: This is the maximum time that a packet stays in a QoS
shaping queue before it is dropped. The value defines the depth of the QoS class
queue. For more information, refer to Queuing on page 199.
• Ethernet / IP / UDP / TCP / RTP / GTP Header Compression: Click the button to
enable or disable the corresponding header compression. When header compression
for a particular protocol is applied, it is automatically applied to all underlying protocols
as well. Ethernet header compression only applies to layer 2 network traffic. When the
network is marked as a mobile backhaul network and GTP header compression is
enabled, the other header compression types also apply to the data inside the GTP
tunnel.
By default, header compression is disabled.

Applying header compression or not is a trade-off between performance

(header compression disabled) and bandwidth efficiency (header
compression enabled).
Applying header compression increases CPU load, hence the lower
performance.
• TCP Acceleration: TCP acceleration minimizes the drawbacks of TCP over high
latency networks. TCP acceleration is by default enabled for CD and BE classes. It is
by default disabled for RT classes. Disabling acceleration can be considered in case
traffic acceleration is performed by an external device.
The setting of TCP acceleration of a specific QoS class must be the same for
both the forward and the return link.
• TCP Payload Compression: TCP payload compression provides on-the-fly payload

compression of TCP traffic. The compression algorithm is lossless meaning that the
original data can be perfectly reconstructed from the compressed data. The parameter
is not available when TCP acceleration is disabled.
Many content types are already compressed by design. For example, a

program file which is packaged as a ZIP file is already compressed, any
state-of-the-art video (MPEG4, DivX, MPEG2) is already compressed, most
image formats (JPG, GIF, PNG) are already compressed. Those content
types cannot be further compressed.
• GTP Acceleration: GTP acceleration accelerates the TCP traffic inside a GTP-U
tunnel. GTP acceleration only works when the network is marked as a mobile backhaul
network. GTP acceleration is by default disabled.
6. Configure the VNO access rights.
When the identifier prefix is the HNO domain name (see Service Profile Settings Tab), you
should link the service profile to one or more VNO domain names. Only VNO domains that are
linked can use the service profiles for their terminals. The Access Rights tab is not available
when the identifier prefix is a VNO domain name. In this case the service profile is automatically
linked to that VNO domain.
7. Click Apply to create the service profile or click Discard to abort. Check the log panel for
Click on the service profile in the overview to edit the parameters.
Click in the Actions column to delete the service profile.

11.4 How to Create a Class-based Service Profile

To create a transport-based Service Profile, execute the following steps:

1. Open the Service Profile provisioning interface as described in
3. Select Class Based in the top menu bar.
4. Click + Create New Service Profile.
5. Configure the service profile settings.

– Set the general parameter.

• Identifier: The identifier is the combination of a domain name and an arbitrary name.
The domain name can be the HNO domain name or a VNO domain name. The
arbitrary name should be unique within the domain and only support alphanumerical
characters, underscores and hyphens. Blank spaces are not allowed.
– Set the terminal circuit parameters.
• PIR: PIR or Peak Information Rate is the maximum unicast traffic rate for the terminal.
The sum of the QoS class rates of the terminal is limited to this value. The value
should be entered for both the forward and return circuit.
• Max Symbol Rate (HRC Mx-DMA and MRC): This controls the maximum satellite
bandwidth usage of a terminal and reduces the impact on other terminals within the
HRC Mx-DMA or MRC NxtGen Mx-DMA return capacity group. This is relevant for
terminals operating with very Low SNR feature (down to -10 dB). A terminal with a very
robust MODCOD (or a very low SNR MODCOD) can consume a large amount of
bandwidth (in order to keep its configured bit rate or CIR), resulting in large carriers /

symbol rates. This impacts other terminals that are using the same HRC Mx-DMA or
MRC NxtGen Mx-DMA Return Capacity Group). For more information, refer to
ACM in HRC Mx-DMA and MRC NxtGen Mx-DMA on page 202.
• Mrc Keep Alive Timeout: This sets the minimum time for which a logged on terminal
transmits at least one burst. It is not advised to set this parameter to bigger values than
1000 ms.
• Mrc Idle Log Off Time: This sets the time it takes a non-transmitting terminal to
change its state to idle/logged off. This parameter is only meaningful when the MRC
NxtGen Mx-DMA return technology is being used.
• External TelliShape Feedback: Click the button to enable or disable TelliShape
feedback to an external multicast source. The feedback contains information about the
TelliShape queues in the modem. Based on this information the source can adapt the
bit rate of the return multicast traffic to use the available return bandwidth.
– Select the QoS classes that should be controlled by the service profile. When a QoS class
is selected, you can enter the following parameters:
• PIR (kbps): PIR or Peak Information Rate is the maximum unicast traffic rate for the
QoS class. PIR cannot be set for the real-time QoS classes.
• CIR (kbps): CIR or Committed Information Rate is the guaranteed unicast traffic rate
for the QoS class. CIR cannot be set for the best-effort QoS class.
available bandwidth among the QoS classes of the same priority. Weight cannot be set
for the real-time QoS classes.
• Allocation Type: This is only available for the return QoS classes and the value can
only be changed for the real-time 1 and 2 class. Refer to Allocation Type on page 200
for more information.
• HRC Mx-DMA Request Margin (kbps): This is only available for the return QoS
classes and the value can only be changed for the real-time 1 and 2 class when the
allocation type is set to DIR. The request margin is bandwidth that is always available
to the terminal and is on top of the requested bandwidth. For more information, refer to
Allocation Type on page 200.
– Packet Size (bytes): This is only available for the return QoS classes. Enter a value in
bytes for the average packet size in the return link or keep the default value.
– Packet Aggregation Timeout (ms): To maximize the use of the payload of an IP packet,
several smaller IP packets can be aggregated into a larger packet. This reduces the IP
overhead but introduces a delay. The value of this parameter is a trade-off between the
delay and the overhead. A smaller value decreases the delay because there is a shorter
waiting time to fill up the buffer but increases the overhead as the buffer may not be
completely full by timeout. For jitter-sensitive real-time applications (typically in RT1 or RT2
QoS class) it is advised to set the timeout value to 1 ms. Mind that disabling aggregation (0
ms) has a negative impact on performance and CPU usage.
– Packet Shaping Timeout (ms): This is the maximum time that a packet stays in a QoS
shaping queue before it is dropped. The value defines the depth of the QoS class queue.
For more information, refer to Queuing on page 199.
– Ethernet / IP / UDP / TCP / RTP / GTP Header Compression: Click the button to enable
or disable the corresponding header compression. When header compression for a
particular protocol is applied, it is automatically applied to all underlying protocols as well.

Ethernet header compression only applies to layer 2 network traffic. When the network is
marked as a mobile backhaul network and GTP header compression is enabled, the other
header compression types also apply to the data inside the GTP tunnel.
By default, header compression is disabled.
Applying header compression or not is a trade-off between performance (header

compression disabled) and bandwidth efficiency (header compression enabled).
Applying header compression increases CPU load, hence the lower performance.
– TCP Acceleration: TCP acceleration minimizes the drawbacks of TCP over high latency
networks. TCP acceleration is by default enabled for CD and BE classes. It is by default
disabled for RT classes. Disabling acceleration can be considered in case traffic
acceleration is performed by an external device.
The setting of TCP acceleration of a specific QoS class must be the same for both
the forward and the return link.
– TCP Payload Compression: TCP payload compression provides on-the-fly payload

compression of TCP traffic. The compression algorithm is lossless meaning that the original
data can be perfectly reconstructed from the compressed data. The parameter is not
available when TCP acceleration is disabled.
Many content types are already compressed by design. For example, a program
file which is packaged as a ZIP file is already compressed, any state-of-the-art
video (MPEG4, DivX, MPEG2) is already compressed, most image formats
(JPG, GIF, PNG) are already compressed. Those content types cannot be
further compressed.
– GTP Acceleration: GTP acceleration accelerates the TCP traffic inside a GTP-U tunnel.
GTP acceleration only works when the network is marked as a mobile backhaul network.
GTP acceleration is by default disabled.
When the identifier prefix is the HNO domain name (see Service Profile Settings Tab), you
should link the service profile to one or more VNO domain names. Only VNO domains that are
linked can use the service profiles for their terminals. The Access Rights tab is not available
when the identifier prefix is a VNO domain name. In this case the service profile is automatically
linked to that VNO domain.
7. Click Apply to create the service profile or click Discard to abort. Check the log panel for
Click on the service profile in the overview to edit the parameters.
Click in the Actions column to delete the service profile.

Manage Attachment Profiles
12 Manage Attachment Profiles

During terminal provisioning the terminal is attached to the satellite resources of a satellite network.
There are two types of attachments:
• Static attachment type: This implies that a terminal operates within a single beam.
– A terminal is linked to forward and return link resources of the satellite network, which is
linked to the beam, and it is only provisioned in one satellite network.
– A static attachment includes a beam, a satellite network, a forward resource (from that
satellite network) and a return resource (from that satellite network).
• Dynamic attachment type: This implies that a terminal can become operational in more than one
beam.
– A terminal is linked with the forward and return link resources of each satellite network in
which the terminal should exist via a dynamic attachment profile.
– A dynamic attachment profile contains one or more home network attachments and
optionally visited network attachments. The home network attachment defines the beam
resources of the operator that serves the terminal. The visited network attachment defines
the beam resources of the networks of another operator.
High Throughput Satellite (HTS) systems that focus on optimizing the capacity available for
interactive services, employ a lot of spot beams. This is in contrast to the traditional satellite systems
with a limited number of wide beams. One of the essential characteristics of spot beam networks is
that the service area of service providers is covered by multiple beams rather than a single beam.
When moving, a mobile terminal passes through the footprint of several spot beams. To configure a
modem for a single beam, you need to specify the satellite network, the forward pool and the return
pool. For a mobile terminal, you need to specify this for each spot beam it will potentially pass.
An attachment profile can contain the information for all spot beams. It is a group of attachments and
each attachment defines a beam, a satellite network, a forward resource and a return resource.
12.1 How to Open the Attachment Profiles Web Interface

To open the web interface of the Attachment Profiles, execute the following steps:

4. Click Attachment Profiles Provisioning in the surveyor tree or in the visual overview.

12.2 How to Create an Attachment Profile

To create an Attachment Profile, execute the following steps:
1. Open the Attachment Profile provisioning interface as described in
How to Open the Attachment Profiles Web Interface on page 213.
3. Click + Create New Attachment Profile.
4. Configure the attachment profile.

Set the parameters:

– Home Network Attachments: Click + Add to add an attachment.
You should create at least one home network attachment.
• Beam: This is the name of the beam to which the attachment applies.
• Satellite Network: This is the name of the satellite network to which the attachment
applies. Click the drop-down list to view the available satellite networks. The values for
the drop-down list are entered when the beam is selected.
• Forward Resource: This is the name of the forward pool to which the attachment
applies. Click the drop-down list to view the available forward pools. The values for the
drop-down list are entered when the satellite network is selected.
• Return Resource: This is the name of the return resource to which the attachment
applies. Click the drop-down list to view the available return resources. The values for
the drop-down list are entered when the forward resources have been selected.

All attachments in the same attachment profile should use the same return
technology.
Only return technologies MRC NxtGen Mx-DMA, HRC Mx-DMA, 4CPM
MF-TDMA are supported.
Click Show Advanced Settings... to enter automatic pointing settings. The terminal sends
these settings to the Antenna Control Unit or ACU using the OpenAMIP protocol.
• Max Skew: In case the skew angle of the antenna exceeds this maximum value the
modem is no longer allowed to transmit. The value ranges between 0 and 90 degrees.
• Acu X String: This is a free text field in which antenna specific OpenAMIP messages
can be entered. These are extra hunt parameters. The antenna vendor specifies the
string.
• Use for AIBS: AIBS allows the modem to automatically select the best satellite beam
from the list of configured beams at startup of the modem. Click the button to enable or
disable AIBS or Automatic Initial Beam Selection for the beam. AIBS is by default
enabled.
• Beam Cost: When the Use for AIBS button is enabled, you can set a beam cost. The
higher the beam cost, the less eligible the beam is. This beam cost overrides the cost
that is set when creating the beam. If the parameter is left blank, the value set when
creating the beam is used. In that case, the Beam Cost value in the Home Attachment
Networks overview is in bold. For more information about the cost at beam level, refer
to How to Create a Beam on page 12.
• Click Confirm to create the attachment or click Cancel to discard the settings.
• Add an attachment for each beam you want to assign to the terminal.
Click in the Actions column to edit the attachment.
Click in the Actions column to delete the attachment.
– Visited Network Attachments: Click + Add to add an attachment.

• Beam: This is the name of the beam of the operator with whom the current operator
has a roaming agreement.
• Forward Carrier: This is the name of the forward carrier within that beam.
• Return Polarisation Type: This is the polarization of the return link in the uplink. The
return uplink is the link from the remote terminal to the satellite.
Click Show Advanced Settings... to enter automatic pointing settings. The terminal sends
these settings to the Antenna Control Unit or ACU using the OpenAMIP protocol.
• Max Skew: In case the skew angle of the antenna exceeds this maximum value the
modem is no longer allowed to transmit. The value ranges between 0 and 90 degrees.
• Acu X String: This is a free text field in which antenna specific OpenAMIP messages
can be entered. These are extra hunt parameters. The antenna vendor specifies the
string.
• Click Confirm to create the attachment or click Cancel to discard the settings.
• Add an attachment for each beam you want to assign to the terminal.

Click in the Actions column to edit the attachment.
Click in the Actions column to delete the attachment.
When the identifier prefix is the HNO domain name (see Attachment Profile tab), you should
link the attachment profile to one or more VNO domain names. Only VNO domains that are
linked can use the attachment profiles for their terminals. The Access Rights tab is not available
when the identifier prefix is a VNO domain name. In this case the attachment profile is
automatically linked to that VNO domain.
6. Click Apply to create the classification profile or click Discard to abort. Check the log panel for
Click on the attachment profile in the overview to edit the parameters. The summary
shows:
• #Attached terminals: The number of terminals that have been provisioned with this
attachment profile.
• Forward Technologies: The forward link technologies that are used in the
attachments.
• Return Technology: The return link technology that is used in the attachments.
Click to delete the attachment profile.
Click to download the remote satellite configuration of the terminal. The

download is a .zip file including the satellite configuration object (config.json) and GXT
files. The satellite configuration object is generated using the information from the
beam and the forward carrier and includes:
• Beam ID;
• Initial carrier 1, which corresponds with the forward carrier of the related satellite
network;
• Initial carrier 2, which is empty or which corresponds with the candidate settings for
the forward carrier;

• Pointing carrier 1, which corresponds with a beacon or with the forward carrier if the
beacon is not enabled;
• Pointing carrier 2, which corresponds with the forward carrier if the beacon is
enabled, which is empty if the beacon is not enabled and there are no candidate
settings for the forward carrier, or which corresponds with the candidate settings for
the forward carrier;
• Orbital degrees;
• Hemisphere;
• Automatic pointing settings (optional);
• AIBS settings (optional). Note that AIBS cannot be enabled through the remote
terminal satellite configuration.
You can load this remote satellite configuration into the terminal using its local GUI.
Click to go to the Terminal Overview page.
12.3 Batch Actions

Batch actions are actions that can be performed on one or more attachments simultaneously.
Following batch actions exist:
• Edit Attachment Profile(s)
• Delete Attachment Profile(s)
Edit Attachment Profile(s)

To edit the attachment profile(s), execute the following steps:
1. Select one or more attachment profile in the overview on which the action must be performed
and click Batch Actions in the upper right of the window.
2. Select Edit Attachment Profile(s) from the drop-down menu. The pop-up window shown
below appears.
3. Click the action you want to perform: Add Attachment and/or Add Attribute and enter the
necessary parameters.
4. Click Edit (async) to execute the action or click Cancel to discard the action.

You have two options to execute the action, which are visible when you click the drop-down
arrow:
– Execute in background (async): All changes are applied in the background, allowing the
operator to do other tasks on the system in the meantime. This is the default setting. You
can see the progress via "Overview Asynchronous Tasks".
– Wait for results (sync): All changes are applied, but the operator cannot do other tasks in
the system and has to wait for the action to finish.
Delete Attachment Profile(s)

To delete the attachment profile(s), execute the following steps:
1. Select one or more attachment profile in the overview on which the action must be performed
and click Batch Actions in the upper right of the window.
2. Select Delete Attachment Profile(s) in the drop-down menu. A pop-up message appears
requesting you to confirm or cancel the action.
3. Click Confirm (async) to execute the action or click Cancel to discard the action.
arrow:
To consult the overview of asynchronous tasks, execute the following steps:

1. Click Batch Actions in the upper right of the window and select Overview Asynchronous
Tasks.
2. Click to view the details of a task.

Manage Firewall Profiles
13 Manage Firewall Profiles

A firewall profile allows you to block any incoming traffic, except the one that matches specific rules.
A firewall profile is linked to a terminal during terminal provisioning. For more information on how to
link a firewall profile to the terminal, refer to Terminal Provisioning Layer 3 Networks on page 247.
Firewall functionality is only supported for MDMxx10 terminals.
13.1 How to Open the Firewall Profiles Web Interface

To open the web interface of the Firewall Profiles, execute the following steps:
4. Click Firewall Profiles Provisioning in the surveyor tree or in the visual overview.

13.2 How to Create a Firewall Profile

To create a Firewall Profile, execute the following steps:
1. Open the Firewall Profile provisioning interface as described in
How to Open the Firewall Profiles Web Interface on page 221.
3. Click + Create New Profile.
A window appears where you can configure the profile and do the VNO linking.
4. Configure the firewall profile.

Set the parameters:

– Type: The firewall profile can apply to IPv4 or IPv6 traffic.
– Enabled: Click the button to enable or disable the firewall profile. When enabled, only
incoming traffic that matches the rules is forwarded, all other incoming traffic is blocked.
The profile is by default enabled.
– Rules: Click + Add to add a firewall rule.
• Description: Provide a short description of the rule.
• Protocol: Type any character in the field to view matching protocols. The list only
shows 10 protocols but there are many more. The incoming traffic should have the
same protocol value in order to match the rule.
• IPv4/IPv6 Address and IPv4/IPv6 Prefix Length: This is the network address and
size of the IP network. The size is the count of leading 1 bits in the subnet mask (CIDR
notation). The incoming traffic should have a source/destination address in the defined
network range in order to match the rule.
• Start Port and End Port: This is a port range. The incoming traffic should have a
source/destination port in the defined range in order to match the rule.
• Click Confirm to create the rule or click Cancel to discard the settings.
• You can create multiple rules.
Click in the Actions column to edit the rule.

When the identifier prefix is the HNO domain name (see Firewall Profile tab), you should link
the firewall profile to one or more VNO domain names. Only VNO domains that are linked can
use the firewall profiles for their terminals. The Access Rights tab is empty when the identifier
prefix is a VNO domain name. In that case the firewall profile is automatically linked to that VNO
domain.

6. When all tabs have a green check symbol, click Apply to save the settings or click Discard to
cancel. Check the log panel for validation messages.
Click on the firewall profile in the overview to edit the parameters.
Click in the Actions column to delete the firewall profile.

Manage BGP Profiles
14 Manage BGP Profiles
14.1 Introduction
When using BGP as the routing protocol for layer 3 network resources it is possible to filter the
routes which are exchanged across BGP peers. Filtering can be done on AS value and a set of host
addresses. The filters can be used both at hub and terminal level.
14.2 How to Open the BGP Profiles Web Interface

To open the web interface of the BGP Profiles, execute the following steps:
4. Click BGP Profiles Provisioning in the surveyor tree or in the visual overview.

Manage BGP Profiles
14.3 How to Create a BGP Profile

To create a BGP Profile, execute the following steps:
1. Open the BGP Profile provisioning interface as described in
How to Open the BGP Profiles Web Interface on page 225.
3. Click + Create New BGP Filter.
Alternatively, you can click the in the Actions column to create a new profile based on
the settings of an existing one.
A window appears where you can configure the filter and do the VNO linking.
4. Configure the BGP filter.

Manage BGP Profiles
Set the parameters:

– Allowed AS Number: Set the AS number of the route in order to match the filter. In case
of iBGP, this number should be different from the local AS number defined in the subnet.
Refer to How to Create a Dedicated Subnet on page 167 for more information on the local
AS.
– IPv4 Networks: Click + Add to set the IPv4 network address and prefix length of the route
in order to match the filter.
• IPv4 Network Address: This is the IPv4 network address of the IP range.
• Prefix: This is the size of the IP range. The number is the count of leading 1 bits in the
subnet mask (CIDR notation).

• You can add multiple ranges.
– IPv6 Networks: Click + Add to set the IPv6 network address and prefix length of the route
in order to match the filter.
• IPv6 Network Address: This is the IPv6 network address of the IP range.
• Prefix: This is the size of the IP range. The number is the count of leading 1 bits in the

• You can add multiple ranges.

Manage BGP Profiles
When the identifier prefix is the HNO domain name (see BGP Filter tab), you should link the
BGP profile to one or more VNO domain names. Only VNO domains that are linked can use the
BGP profiles for their terminals. The VNO Linking tab is not available when the identifier prefix is
a VNO domain name. In this case the BGP profile is automatically linked to that VNO domain.
messages.
Click on the BGP profile in the overview to edit the parameters.
Click in the Actions column to delete the BGP profile.

Manage Remote Configuration Profile
15 Manage Remote Configuration Profile

In the Remote Configuration Profile you define if remote configuration of the satellite interface on the
modem is allowed or not.
The satellite interface can be configured locally using the modem GUI or using the JSON API.
These local changes however are not checked against the settings in the hub. Changing the
settings locally is prone to error and you can potentially prevent the modem from becoming
operational. You will also have to perform this configuration terminal by terminal.
The Remote Terminal Satellite Configuration feature guarantees consistency between the
settings in the hub and the configuration on the modem. The remote satellite configuration is created
from the data in the central Network Management System or NMS, and is downloaded by the
terminal. The feature also allows easy management of the satellite interface configuration of a group
of modems.
The remote terminal satellite configuration is defined through the static attachment or the dynamic
attachment profile in NMS. From this attachment (profile) the satellite configuration object and GXT
files are derived.
For more information about the remote terminal satellite configuration feature, refer to
15.1 How to Open the Remote Configuration Profiles Web

Interface
To open the web interface of the Remote Configuration Profiles, execute the following steps:

4. Click Remote Configuration Profiles Provisioning in the surveyor tree or in the visual
overview.
15.2 How to Create a Remote Configuration Profile

To create a Remote Configuration Profile, execute the following steps:

1. Open the Remote Configuration Profile provisioning interface as described in

How to Open the Remote Configuration Profiles Web Interface on page 229.
3. Click + Create Remote Configuration Profile.
A window appears where you can configure the profile and do the VNO linking.
4. Configure the remote configuration profile.
Set the parameters:

– Remote Satellite Config Enabled: This parameter defines if the modem is allowed to
receive a satellite configuration from the hub. The satellite configuration contains
information such as the initial receive and pointing carrier settings, AIBS settings, GXT file
name, etc. Remote satellite configuration is by default disabled.
– GXT File Random Back Off: The back off value is used to load balance the GXT file
requests from terminals. The terminal will wait a random time between 0 seconds and this
back off value before downloading the GXT file. The back off value can be set between 0
and 10,000 seconds. The default value is 100 seconds.
When the identifier prefix is the HNO domain name (see BGP Filter tab), you should link the
BGP profile to one or more VNO domain names. Only VNO domains that are linked can use the
BGP profiles for their terminals. The VNO Linking tab is not available when the identifier prefix is
a VNO domain name. In this case the BGP profile is automatically linked to that VNO domain.
messages.
Click on the remote configuration profile in the overview to edit the parameters.
Click in the Actions column to delete the remote configuration profile.

Manage Terminal Provisioning
16 Manage Terminal Provisioning

To allow a remote terminal to be operational on the Dialog platform, it needs to be configured in the
system. This is done through the Terminal Provisioning interface. Once the remote terminal is
provisioned, a bi-directional circuit is automatically created between the terminal and the hub
module.
You can only provision terminals when forward on page 25 and return on page 73 resources,
network resources on page 151 , classification profiles on page 188 and service profiles on page
198 or attachment profiles on page 213 have been created.
16.1 Whitelisted Terminals

Whitelisted terminals can log on to a satellite network without being provisioned beforehand. This
feature is called Auto Attachment in Dialog.
Auto Attachment can be enabled or disabled per satellite network. For more information about this
configuration, refer to How to Create a Satellite Network on page 19.
When enabled, the FTB message in the forward link not only includes the pop-ID with the MAC
addresses of all provisioned terminals but also includes the auto attachment signaling. The signaling
contains the broadcast MAC address and the allowed Power Spectral Density or PSD for logon
requests.
The MAC address of whitelisted terminals are added to an Auto Attachment Prototype. This
prototype also has a modem template that is used to provision the whitelisted terminals when logging
on.
When a whitelisted terminal is installed and pointed, it locks on a forward carrier and parses the FTB
message. When it sees that auto attachment is enabled for the satellite network and its MAC
address is not included in the pop-ID (it is not provisioned), the terminal will send a 4CPM logon
request. This request is received by the 4CPM controller of that satellite network. The Hub Module
Management System or HMMS will periodically poll the 4CPM controller of each satellite network on
which auto attachment is enabled to get the "First Sign of Life" messages. From these messages, it
will filter out the provisioned MAC addresses and send the other (unknown) MAC address to the
NMS. If the NMS verifies that the MAC address is part of an Auto Attachment Prototype, it will
provision the terminal based on the modem template of the Auto Attachment Prototype to which it
belongs. It will also delete the terminal from the Auto Attachment Prototype.
For more information, refer to Manage Auto Attachment Prototype on page 266.
The terminal provisioning interface is used to create the template for the auto attachment prototype.
In this case, you should not enter a MAC address and the terminal is not provisioned.
To open the web interface of the terminal provisioning, execute the following steps:

3. Click Terminals in the surveyor tree or in the visual overview.
4. Click Terminals Provisioning in the surveyor tree or in the visual overview.

16.2 How to Create a Terminal

To provision a terminal, execute the following steps:
1. Open the Terminals Provisioning interface as described in
How to Open the Terminal Provisioning Web Interface
3. Click + Create New Terminal.
Alternatively, you can click the copy icon in the Actions column to create a new terminal
A window appears where you can configure the following settings.

– Modem settings. Refer to How to Configure Modem Settings on page 235.

– Service settings. Refer to How to Configure Service Settings on page 240.
– Mobility settings. Refer to How to Configure Mobility Settings on page 243.
– Layer 3 network settings. Refer to How to Configure Layer 3 Settings on page 246.
– Layer 2 VC settings. Refer to How to Configure Layer 2 Settings on page 258.
– Monitoring settings. Refer to How to Configure Monitoring Settings on page 260.
– [optional and only in case of MDM2210 and MDM2010] Wi-Fi settings. Refer to
[optional] How to Configure Wi-Fi Settings on page 262.
4. Once you have configured everything, click Apply to save the settings or click Discard to cancel.
Check the log panel for validation messages.
Click on the terminal in the overview to edit the parameters.
Click in the Actions column to delete the terminal.
Click or in the Actions column to lock or unlock the terminal. Locked

terminals cannot log on to the Dialog system, but they are configured in the
configuration database.
Click in the Actions column to go to the terminal's GUI. This is not available
when the terminal is locked.
Click in the Actions column to download the configuration of the modem. The
downloaded file is a .zip file containing the modem configuration in JSON format.
16.2.1 How to Configure Modem Settings

The interface of the Modem tab is shown in the screenshot below. As long as the required fields are
not set, the other tabs are unavailable.

Set the parameters:

• Auto Attachment Prototype: Select this check box to use the terminal settings as the modem
template for an Auto Attachment Prototype. When selected, no provisioning action is performed
when clicking the Apply button. Instead, a new Auto Attachment Prototype window opens where
you can enter the MAC addresses of whitelisted terminals. For more information about whitelisted
terminals, refer to Whitelisted Terminals on page 232. For more information about Auto
Attachment Prototypes, refer to Manage Auto Attachment Prototype on page 266.
In order for the auto attachment feature to work, make sure that the satellite
network of your modem template has the feature enabled. Refer to
The template configuration has the following restrictions:

• Only 4CPM and MRC supported;
• Only shared subnet supported;
• Only dynamic attachment supported.

When editing an existing terminal, the check box is not available.
• Identifier: The identifier is the combination of a VNO domain name and an arbitrary name. The
arbitrary name should be unique within the domain and only support alphanumerical characters,
• Description: This is a free format field to add descriptive information about the terminal.
• Modem Type: Click the drop-down menu to select the modem hardware type.
• MAC Address: This is a globally unique address embedded in the modem hardware. The mac
address can be found on a label at the bottom of the modem or via the modem GUI. The MAC
address of a Dialog modem always starts with 00:06:39.
• Local Power Control enabled: Click the button if you want the terminal to accept power control
message through the power control API or not. Local power control is used to compensate for
varying gain on antennas, reduce ASI and optimize performance. In case the modem is under
local power control, the local controller sends the maximum TX PSD and saturated power settings
to the modem API at regular intervals. The local controller calculates these settings based on the
selected beam and the antenna pointing data (elevation, skew). Local power control is by default
disabled.
This parameter is not applicable for static or fixed terminals.
• Encrypt data traffic HUB-Terminal: This value allows you to overrule the encryption setting of
the satellite network. When set to Default from SatNet, the terminal uses the encryption value of
the Satellite Network. When set to Disabled, traffic for that terminal is not encrypted even when
encryption is enabled for the satellite network the modem is in. When set to Enabled, traffic for
that terminal is encrypted, even when encryption is disabled for the satellite network the modem is
in. For more information on how to set the encryption for the satellite network, refer to
• Remote Configuration Profile: Click the drop down-menu to link a Remote Configuration Profile
to the terminal. In this profile you define if it is allowed to remotely configure the satellite interface
of the modem or not. For more information about the remote satellite configuration, refer to
Manage Remote Configuration Profile on page 229.
• Software Update Group: Modems belonging to a specific software group are allowed to
download a specific software. Refer to Updating Terminal Software on page 271 for more
information.
• The following parameters are related to the Line Up procedure. The line up procedure is used to
define the clear-sky terminal transmit power for a given carrier bandwidth. It is also used to get an
indication of the cable loss, BUC gain and antenna gain. During the procedure the terminal output
power is measured, verified and adjusted by the satellite operator or Hub Network Operator (HNO)
using an installation carrier. Based on the line up settings, a terminal transmit power is ensured
that avoids transponder saturation. Line up settings are not available for modem type MDM2200.
This type of modem will always transmit at iLNB saturated power.
– Nominal Occupied Bandwidth: This is the bandwidth of the installation carrier that is used
for the line-up procedure.
• If the installation carrier uses DVB-S2(X), the bandwidth of the carrier equals symbol
rate * (1 + roll-off).
• If the installation carrier uses HRC or MRC, the bandwidth equals the symbol rate *
1.05. We recommend using a typical symbol rate of 185 kBaud.

– Nominal Output Power: This is the terminal output power that has been measured and
approved by the satellite operator or HNO during the line up procedure. Refer to
Terminal Line Up on page 276 for more details.
• Output Power for 1dB Compression: This is an AUPC related setting. When AUPC or
Automatic Uplink Power Control is enabled, the Output Power for 1dB Compression defines the
maximum output power. The exact definition of the output power depends on the ODU type:
– For a BUC, it is the output power that a modem needs to transmit to the BUC to make sure
that the BUC transmits at the 1 dB compression output power.
– For the iLB2220 MUC, it is the maximum saturated output power of the MUC..
Refer to Configuring AUPC on page 328 for more details.
• The following parameters only appear for modems that use the HRC and MRC return
technologies. The optional parameters are used to define a transponder-specific transmit power
during logon of mobile terminals. Mobile terminals will typically logon on transponders different
from the reference transponder used for the line up procedure. A transmit output power solely
based on the reference transponder might cause issues of exceeding the maximum Power Flux
Density (PFD) allowed to be received at the logon transponder.
– Nominal Saturated Flux Density: This is the Saturated Flux Density (SFD) in dBW/m2 of
the transponder used for the line up procedure. The SFD is the Power Flux Density (PFD)
received by the satellite RX antenna from a given point in the beam coverage, which drives
the transponder in saturation.
– Nominal Input Back Off: This is the Input Back Off (IBO) in dB of the transponder used for
the line up procedure. In the return link, transponders are typically operated with multiple
carriers. To avoid interference and distortion caused by multiple carriers, a transponder is
operated with sufficient back off. Therefore, the maximum allowed total PFD at the satellite
equals SFD - IBO. The IBO is determined by the HPA non-linear transfer characteristics.
– Nominal Regulatory Power: This is the Nominal Regulatory Power in dBm of the
transponder/satellite used for the line up procedure. It is the maximum modem output
power allowed by regulation for off-axis radiation within nominal bandwidth and avoids
interference between adjacent satellites.
• BUC and Modem Frequency Synchronized: Click the button to enable or disable frequency
synchronization between the BUC and the modem. When enabled, the BUC is slaved to the
reference clock of the modem. When disabled the BUC uses an internal reference clock or is
slaved to a reference source other than the modem.
BUC and modem frequency synchronization is applicable for modem types that
support the use of a BUC. These include all modem types, except MDM2200 and
MDM2210, which only support an iLNB with MUC.
This parameter is not visible for MDM2200 and MDM2210 modems.
Enable this parameter when the modem uses MRC as return link technology.
Disable this parameter if the BUC uses an internal reference or is slaved to a

reference source other than the modem.
• When frequency synchronization between modem and BUC is disabled, a frequency uncertainty
is introduced. The Max Frequency Uncertainty can be retrieved from the BUC data sheet. The
value ranges from 0 to 100 with a precision of 3 digits (default 1.000 ppm). This value is used by

the return controller to calculate additional guard bands for the return carrier and protects the
network from the uncertainties introduced. This also has an impact on terminal logon times.
• Certification Skipped: Click the button to enable or disable certification of the terminal. The
status of the terminal certification is displayed in the Terminal Overview list. Refer to Certification
on page 333 for more details.

16.2.2 How to Configure Service Settings

The interface of the Service tab is shown in the screenshot below.
Set the parameters:

• Service Profile: Select the service profile the terminal will use. The list of available service
profiles is determined by VNO and modem type. Not all modem types support all return
technologies. Refer to Manage Service Profiles on page 198 for more information on service
profiles.
• Forward Ingress Classification Profile: Select the classification profile that contains the rules for
classifying the forward ingress traffic arriving at hub side into the QoS classes. Refer to
Manage Classification Profiles on page 188 for more information on classification profiles.
• Return Ingress Classification Profile: Select the classification profile that contains rules for
classifying the return ingress traffic arriving at the terminal LAN side into the QoS classes. Refer
to Manage Classification Profiles on page 188 for more information on classification profiles.
• Attachment Type: Choose Dynamic for terminals that can be operational in multiple beams;
choose Static for terminals that are operational in a single beam.
• When the attachment type is Dynamic, you should select an Attachment Profile. For more
information about attachment profiles, refer to Manage Attachment Profiles on page 213.
When an attachment profile is selected, you can click the information icon for an overview of the
beams that are linked with that attachment profile.

• When the attachment type is Static, enter the following:

– Satellite Network: This is the identifier of the satellite network to which the terminal should
belong. Click the drop-down list to view the available satellite networks.
– Forward Resource: This is the identifier of the forward pool that will be used for the
terminal's forward traffic. Click the drop-down list to view the available forward pools. The
values for the drop-down list are entered when the satellite network is selected.
– Return Resource: This is the identifier of the return pool that will be used for the terminal's
return traffic. Click the drop-down list to view the available return pools. The values for the
drop-down list are entered when the forward resources have been selected. The available
return pools are filtered based on the modem type:
Modem Type SCPC MF-TDMA Mx-DMA NxtGen Mx-DMA
MDM2010 X X
MDM2200 X
MDM2210 X
MDM2500 X
MDM2510 X X X
MDM3100 X X
MDM3300 X X X
MDM3310 X X X X
SMB3310 X X X X
SMB3315 X X X X
MDM5000 X X X
MDM5010 X X X X
The selected service profile determines which forward and return resources are
available. You can only link transport-based forward and return pools with a
transport-based service profile and class-based forward and return pools with
class-based service profiles.
• Max Forward ModCod: Set the maximum MODCOD that can be used by the terminal on the
forward link. This is a forward ACM improvement to face unpredictable distortion on terminal level.
The maximum MODCOD is selected from the MODCOD list, which is ordered according to the
ideal Es/N0 threshold, as specified in the DVB-S2(X) standard. The selection of the maximum
MODCOD implies that the modem will not use any MODCOD that has an ideal Es/N0 threshold
higher than the one of the maximum MODCOD.
• HRC Mx-DMA Settings (only visible when HRC Mx-DMA return technology is used)
Refer to HRC Mx-DMA on page 81 form more information.

– Extended VL-SNR: Click the button to allow the terminal to login with an EsN0 as low as
-12 dB. When enabled, universal logon is automatically enabled for that terminal. When
disabled, the minimum EsN0 to log on is -6 dB.
Extended VL-SNR is only supported on AMC5001 and MDM5010.

Extended VL-SNR is supported on MCD7000 and MCD7500.
When enabled, make sure that the HRC Mx-DMA return capacity group is
configured to support universal logon.
– Universal Logon: Click the button to enable or disable ulogon. For more information about
ulogon, refer to How to Enable HRC Mx-DMA Universal Logon on page 135.
– Min Symbol Rate: The minimum amount of satellite bandwidth that a modem can use
under any circumstance. This has an influence on the ACM behavior. Refer to
ACM in HRC Mx-DMA and MRC NxtGen Mx-DMA on page 202 for more information.
– Max Return MoDCoD: The maximum MODCOD that a modem can use under any
circumstance. This has an influence on the ACM behavior. Refer to
• MRC Mx-DMA Settings (only visible when NxtGen Mx-DMA MRC return technology is used)
– Max MODCOD: The maximum MODCOD that a modem can use under any circumstance.
This has an influence on the ACM behavior. Refer to
– Min Symbol Rate: The minimum amount of satellite bandwidth (in kbaud) that a modem
can use under any circumstance. This has an influence on the ACM behavior. Refer to
• SCPC settings (only visible when HRC SCPC return technology is used)
Refer to HRC SCPC on page 81 for more information.
– Max MODCOD: This parameter is only available when ACM is enabled. It is the maximum
MODCOD that the modem can use under any circumstance. The default value is
32APSK9/10.
– CCM ModCod: This parameter is only available when ACM is disabled. It is the MODCOD
that the modem should use. The QPSK3/10 MODCODs with SF number are very low or
VL-SNR MODCODs. VL-SNR MODCODs allow HRC SCPC CCM terminals with an Es/No
value as low as -12 dB to be operational.
– Center Frequency: This is the center frequency of the HRC SCPC carrier. The value must
be within the frequency range that was defined when creating the HRC Return Capacity
Group. Refer to Create an HRC SCPC Return Capacity Group on page 103 for more
information about the frequency range of the return capacity group.
– Symbol Rate: This is the symbol rate of the HRC SCPC carrier.
• S2 settings (only visible when DVB-S2 or S2 Extensions SCPC return technology is used)
Refer to DVB-S2 and S2 Extensions on page 79 for more information.
– Transport Mode: Define if the S2 carrier uses the DVB-S2 or S2 Extensions transport
mode.
– Nominal ModCod: The minimal MODCOD for the return link unicast traffic.
– Center Frequency: This is the center frequency of the S2 carrier. The value must be
within the frequency range that was defined when creating the S2 Return Capacity Group.

Refer to How to Create an S2 Return Capacity Group on page 100 for more information
about the frequency range of the return capacity group.
– Roll Off Factor: Select the roll-off factor of the S2 carrier from the drop-down list. The
roll-off factor impacts the occupied bandwidth, which is equal to Symbol Rate × (1+roll-off
factor).
– Symbol Rate: This is the symbol rate of the S2 carrier.
– ACM Enabled: It is possible to enable ACM. If ACM is enabled, then modification of the
MODCOD is possible based upon:
• ACM Min/Max ModCod: These parameters define the minimum and maximum
MODCOD that can be used within the RCG.
• ACM Margin: An extra margin in dB can be added on top of the nominal MODCOD
threshold, which is used to determine when to switch to another MODCOD. In case
return link efficiency is required, it is advised to set the static margin to zero.
Click + Show Advanced Settings... to enter the following parameters:
– Pilots: Pilots are inserted to increase the reliability of the receiver synchronization. Pilots
are by default inserted.
– Frame Type: This parameter determines if short or normal DVB-S2 baseband frames are
used. It is advised to use short frames if the data rate is smaller than 2 Mbit/s.
– Demodulator Role: The demodulator role determines which demodulator in the hub
receives this S2 carrier. This can be assigned automatically or manually. Only applies if
multiple S2 demodulators are present.
– Encapsulation Mode: If high throughput is required, you can set this parameter to
'Efficiency Optimized'. If little or no delay is required (for example, for real-time
applications), you can set this parameter to 'Jitter Optimized'.
• Output Power Type: This setting is only available for modem type MDM2510 and when using the
MF-TDMA 4CPM return technology. MDM2510 is the only modem type that can be deployed with
an iLNB or with a BUC. When the modem uses a BUC, this parameter should be set to Modem
Output Power. When the modem uses an iLNB, this parameter should be set to ODU Output
Power.
• Power Control Mode: Select how the output power of the modem should be controlled. In case
of Nominal (using Line Up Settings) the power is controlled by the values from the line up
procedure. In case of Absolute, the modem output power is set in the Absolute Output Power
field. For 4CPM only nominal power control mode is available.
• Absolute Output Power: This value defines the modem output power when the Power Control
Mode is set to Absolute.
• Automated Uplink Power Control Enabled: Click the button to enable or disable Automated
Uplink Power Control or AUPC. In order for AUPC to work, make sure that the Power Control
Mode is set to Nominal. AUPC is only available for modems working with MRC, HRC or 4CPM.
Refer to How to Manage AUPC on page 328 for more information.
• Range: When AUPC is enabled, this range limits the amount of uplink fade that will be
compensated by AUPC. It is the maximum increase of the modem output power to keep the same
C/N0 (4CPM) or C0/N0 (HRC and MRC) before ARL is activated. The value can be set between 0
and 20 dB.
16.2.3 How to Configure Mobility Settings

The interface of the Mobility tab is shown in the screenshot below.

The available Mobility parameters depend on the following settings in the Service tab:
• Attachment type
• Return link technology
The table below gives an overview.
Attachment Type Return link technology
Communications on the Move All All
Automatic Pointing Static All
HRC Mx-DMA and MRC

Mobility Orchestration Dynamic
Mx-DMA
Communication on the Move

Communication on The Mode is also known as COTM.
• Communications on the Move Enabled: Click the button to enable or disable COTM. COTM
should be enabled when you are provisioning a mobile terminal. When enabled, the following
parameters appear:
– Max Speed and Max Acceleration: These parameters are used to compensate the
Doppler effect for mobile terminals and specify the maximum speed and acceleration of the
vehicle in which the modem resides. The speed value ranges from 0 to 5,000 m/s, with a
precision of 1 digit (default 0.0 m/s). The acceleration value ranges from 0 to 36 m/s2, with
a precision of 1 digit (default 0.0 m/s2)
The speed and acceleration parameters have an impact on terminal logon times.
Return link controllers take these parameters into account and introduce a level of
uncertainty, which translates into longer logon times.
For more details about the impact on logon times, refer to the Newtec Dialog
Functional Description.
The following table provides rule of thumb values for the maximum speed and acceleration.

Application Max Max 4CPM HRC DVB-S2 MRC

Speed Acceleration /S2Ext
(m/s) (m/s 2)
Maritime rigs 1.5 2.0 ✔ ✔ ✔ ✔

(>2 Mbaud)
Maritime bulk 7.5 6.0 ✔ ✔ ✔ ✔

carrier (>2 Mbaud)
Maritime 15.0 6.0 ✔ ✔ ✔ ✔

cruise/container only in KU (>2 Mbaud)
or C-band
Aeronautical 350.0 6.0 ✖ ✔ ✔ ✖

airliner midflight (>2 Mbaud)
Aeronautical 17.0 ✖ ✔ ✔ ✖
airliner all (>10 Mbaud)
conditions
Automatic Pointing Settings

These parameters are only available when the terminal uses a static attachment type, which means
that the terminal can only operate in one beam. In case of a dynamic attachment type, these
parameters are defined per attachment in the attachment profile. The parameters are optional.
When the terminal uses automatic pointing, it can send the following parameters to the Antenna
Control Unit using the OpenAMIP protocol:
• Max Skew: In case the skew angle of the antenna exceeds this maximum value the modem is no
longer allowed to transmit. The value ranges between 0 and 90 degrees.
• Acu X String: This is a free text field in which antenna specific OpenAMIP messages can be
entered. These are extra hunt parameters. The antenna vendor specifies the string.
Mobility Orchestration
Beam roaming is only available when the terminal uses a dynamic attachment type, meaning that it
can operate in multiple beams, and HRC Mx-DMA or MRC NxtGen Mx-DMA as a return link
technology. Beam switching can be done manually by selecting the beam in the local modem GUI or
automatically using a mobility manager. The mobility manager implements the beam switching logic
to select a new target beam and sends this target beam to the mobility orchestrator in the hub. The
mobility orchestrator organizes the actual beam handover. When using a mobility manager, COTM
and beam roaming must be enabled.
• Beam Roaming: Click the button to enable or disable beam roaming. Beam roaming should be
enabled when the modem can move between beams. When beam roaming and COTM are
enabled, the following parameters appear:
– Position Timeout: This is the maximum time that a roaming terminal stays in the
operational/located state without feedback about its GPS coordinates. If this time has
expired, the terminal falls back to operational/unlocated state. Default value is 60 seconds.
– Switch Timeout: This is the maximum time that a roaming terminal stays in the switching
state without being logged on in the target beam. If this time has expired, the terminal falls
back to the operational/unlocated state. Default value is 60 seconds.

You must enable Automatic Initial Beam Selection or AIBS and Automatic Pointing
for the terminal to support automatic beam switches. This is enabled in the local modem
GUI.
Terminals can travel from one beam to another beam without being operational during
the travel. For example in case of Fast New Gathering or FNG and Satellite News
Gathering or SNG. To avoid that you have to re-provisioning the terminal from one
satellite network to another, you can enable beam roaming without enabling COTM.
Mobility Management
If communication on the move and beam roaming are enabled, you can specify the type of mobility
management.
The mobility manager decides if a terminal should perform a beam switch and to which beam it
should switch. This decision is based on the terminal's position and specific beam information, such
as contours, cost, load. Two types of mobility manager exist: The Central Mobility Manager is
located at the hub side and the modem will regularly send its GPS coordinates over the air to the
hub. The Remote Mobility Manager is integrated in the modem and periodically monitors the position
of the terminal. The GPS coordinates, which could be considered as sensitive information, of the
terminal are retrieved from the ACU and are not sent over the air.
• Remote Mobility Management: Click the button to enable or disable the remote mobility
manager for the terminal.
To ensure that the GPS coordinates are not sent you must also disable the Send Status
updates to DMM setting in the local modem GUI.
16.2.4 How to Configure Layer 3 Settings

The interface of the Layer 3 tab is shown in the screenshot below.
The interface has three sections, which are described in the following chapters.

• Layer 3 Networks on page 247

• Return Multicast on page 257
• Route Advertisement on page 257
16.2.4.1 Layer 3 Networks
You need to configure at least one layer 3 or layer 2 network.
A layer 3 or L3 network connects an uplink network (1 in the figure below) on the hub side to the
LAN network behind one or more modems (2 and 3 in the figure below).
The L3 network is identified by a configurable VLAN tag on the uplink interface and on the LAN
interface of the modem.
You can configure multiple L3 networks (up to 256) in the same satellite network resulting in
multiple VRF instances. Each instance has an isolated routing and addressing context allowing to
reuse private address ranges in the different networks in the same satellite network. And you can
terminate multiple L3 networks on the same modem, also resulting in multiple VRF instances with
isolation of the routing and addressing context. The maximum number of virtual networks supported
on a terminal depends on the type of terminal as shown in the table below.
Modem Type Max. # of Virtual Networks
MDM2010 4
MDM2210 4
MDM2510 16
MDM3310 16
SMB3310 16

SMB3315 16
MDM5000 16
MDM5010 24
The L3 network supports two modes for assigning IP addresses or subnets to the LAN network of
the modem. The modes are:
• Dedicated Subnet
• Shared Subnet
The uplink part of the network is defined during the network resource provisioning on page 164, the
LAN part of the network is defined during terminal provisioning (this chapter).
16.2.4.1.1 Dedicated Subnet
Configuring a dedicated subnet requires the following sequential steps:

• Define to which uplink part this network belongs. This is done through the service label.
• Define the VLAN used on the LAN network behind the modem.
• Assign an IP subnet to the LAN network of the modem.
The uplink part of the network is created during network resources provisioning. For
more information, refer to How to Create a Dedicated Subnet on page 167.
Click + Add to add a layer 3 network. A window appears.

Make sure to set Type to Dedicated Subnet.

General Parameters
• Service Label: This label specifies the dedicated subnet, which the modem can use. The label
can group one or more subnets. For more information on how to use service labels, refer to
Use of Service Labels for Dedicated Subnets on page 158.
• VLAN Tag: This parameter defines if traffic on the modem LAN is sent tagged or untagged. Using
a VLAN tag allows you to reuse IP addresses within the network.
• IP versions: Select the IP versions used on the modem LAN. You have to select at least one IP
version. When you select an IP version, the corresponding section appears at the bottom of the
screen. IPv4 is by default enabled.
• NAT/Firewall managed: Click the button to enable or disable management of the NAT and
firewall settings. When enabled, the NAT and Firewall settings can be configured in this interface.
When disabled, NAT and Firewall should be managed locally, through the modem GUI.
NAT and Firewall are only supported on MDM2010, MDM2210 Wi-Fi, MDM2510,
MDM3310, SMB3310, SMB3315 and MDM5010.
NAT is only supported for IPv4.
• BGP Support: Click the button to define if BGP routing is supported at terminal level or not.The
modem can use eBGP or iBGP towards the external local routers. Alternatively, you can provision
static routes on the terminal. In that case, there is no BGP peering between the modem and the
external local router. For more information about BGP, refer to BGP on page 156.
When BGP is enabled, the Static Routes parameter and the BGP Configuration section
appears, any NAT parameters and Next Hop Routes disappear.
BGP is only supported for IPv4. Make sure to enable the IPv4 version in case you
want to use BGP.
BGP is only supported on MDM2510, MDM3310, SMB3310, SMB3315 and

MDM5010.
BGP only works if it has been enabled on the routers behind the modem.
• Static Routes: This parameter appears when BGP Support is enabled. When activating static
routes, the BGP Configuration section disappears and you need to define static routes for BGP
(IPv4 Next Hop Routes).
IPv4 Configuration
This section is only available when IPv4 is selected as IP version.

The parameters to enter depend on modem type and some specific settings.
The following parameters are always available.

• Transparent DNS: This parameter allows you to configure a DNS server per terminal. When
enabled:
– Hosts connected to the modem send their DNS request to the configured DNS server. The
DNS request is entirely transparent to Dialog and bypass the internal DNS proxy
functionality. The DNS servers configured at network resource level are ignored. For more
information about DNS proxy, refer to How to Create a Dedicated Subnet on page 167.
– DHCP is automatically enabled and cannot be disabled. The terminal sends the configured
DNS servers via DHCP to its hosts.
– The DNS Servers window appears. Click to add an external DNS server IP address
and enter the IPv4 DNS Server Address. This is the IPv4 address of an external DNS
server which is used as the name server by the hosts connected to the terminal.
You can add up to four DNS server addresses. If multiple DNS servers are configured, click
next DNS server is consulted, and so on. To delete a DNS server, click in the
Actions column.
Although this parameter is always available, the Transparent DNS feature is only
supported on the MDMxx10 series. Enabling it for other the other modem types
will return an error when applying the configuration.
• DHCP: Click the button to enable or disable DHCP on the modem. When enabled, the modem will
act as the DHCP server for its hosts. When disabled, there should be another device in the LAN
acting as the DHCP server, or a static IP address on each host has to be configured.
It is advised to disable DHCP if you intend to use static IP addresses for hosts in
order to avoid IP address conflicts.
• Allow Ping: This parameter defines if the LAN IP address of the modem replies to ICMP requests
or not. All modems by default use the setting defined for the dedicated subnet. This is the Default
from network value. The parameter can be overridden here, on a terminal basis. Set the
parameter to Allow or Don't allow to allow or disallow the modem to reply to ICMP request,
regardless of the setting for the dedicated subnet. For more information on how to set the
parameter for the dedicated subnet, refer to How to Create a Subnet on page 167.
• SNMP: Click the button to enable or disable Simple Network Management Protocol or SNMP to
monitor the terminals. Keep in mind that this consumes satellite network resources. SNMP is by
default disabled.
The following parameters are only available for:
– MDMxx00 series;
– MDMxx10 series with the NAT/Firewall managed value set to No;
– MDMxx10 series with the NAT/Firewall managed value set to Yes and the NAT Enabled
value not checked.

• Modem Address: This is the IP address that will be assigned to the modem's network interface.
• Prefix: This is the size of the LAN network behind the modem. The number is the count of
leading 1 bits in the subnet mask (CIDR notation).
• IPv4 Next Hop Routes: These are static routes for networks behind a router in the modem LAN.
Click + Add to add a route and enter the following parameters:
– Network: This is the network address of the IPv4 network behind the router.
– Prefix: This is the size of the IPv4 network. The number is the count of leading 1 bits in the
– Gateway: This is the IPv4 address of the router or gateway located in the modem LAN,
and which acts as next hop for this network.
You can add multiple routes.
Click to delete the route.

The following parameter is only available for MDMxx10 series with the NAT/Firewall managed
value set to Yes and the NAT Enabled value not checked.
• Firewall Profile: Use this parameter to block the incoming traffic based on firewall policy rules.
The firewall policy rules are defined in a firewall profile. Select the profile that you want to apply.
For more information on how to create a firewall profile, refer to Manage Firewall Profiles on page
221.
The following parameter are only available for MDMxx10 series with the NAT/Firewall managed
value set to Yes and the NAT Enabled value checked.
• WAN Address: This is the publicly exposed IPv4 address that will be assigned to the modem's
network interface.
• WAN Prefix Length: This is the size of the NAT pool. The number is the count of leading 1 bits in
the subnet mask (CIDR notation). NAT pooling is the ability to randomly assign public IP
addresses to private internal IPs on a first come first serve basis from a pool of IPs.
• LAN Address: This is the private IP address that will be assigned to the modem's network
interface..
• LAN Prefix: This is the size of the private LAN network. The number is the count of leading 1 bits
in the subnet mask (CIDR notation).
• Port Forwarding: The port forwarding rules apply to the LAN network. Click + Add to add a rule
and enter the following parameters:
– Description: The description of the port forwarding rule.
– Public Port(s): This is the public port to which the rule applies. You can enter a port range
by separating the start and end port with a hyphen (for example 5000-6000).
– Local IP Address: This is the local IP address to which the rule applies. This IP address
should be part of the LAN network.
– Local Port(s): This is the local port to which the rule applies. You can enter a port range by
separating the start and end port with a hyphen (for example 5000-6000).
– Protocol: The protocol to which the rule applies can be UDP, TCP or both.
You can add multiple rules.
Click to delete the rule.
IPv6 Configuration


• LAN Address: This is the IP address that will be assigned to the modem's network interface.
• LAN Prefix: This is the size of the LAN network behind the modem. The number is the count of
leading 1 bits in the subnet mask (CIDR notation).
• Routed Prefix Address: This is the IPv6 network address of the routed prefix range.
• Routed Prefix: This is the size of the routed prefix range. The number is the count of leading 1
The routed prefix range is used for IPv6 prefix delegation to IPv6 routers
connected to the modem.
• Transparent DNS: .This parameter allows you to configure a DNS server per terminal. When
enabled:
– DHCP is automatically enabled and cannot be disabled. The terminal sends the configured
DNS servers via DHCP to its hosts.
Actions column.
• Allow Ping: This parameter defines if the LAN IP address of the modem replies to ICMP requests
or not. All modems by default use the setting defined for the dedicated subnet. This is the Default
from network value. The parameter can be overridden here, on a terminal basis. Set the
parameter to Allow or Don't allow to allow or disallow the modem to reply to ICMP request,
regardless of the setting for the dedicated subnet. For more information on how to set the
parameter for the dedicated subnet, refer to How to Create a Subnet on page 167.
• SNMP: Click the button to enable or disable Simple Network Management Protocol or SNMP to
monitor the terminals. Keep in mind that this consumes satellite network resources. SNMP is by
default disabled.
• IPv6 Next Hop Routes: These are static routes for networks behind a router in the modem LAN.
Click + Add to add a route and enter the following parameters:

– Network: This is the network address of the IPv6 network behind the router.
– Prefix: This is the size of the IPv6 network. The number is the count of leading 1 bits in the
– Gateway: This is the IPv6 address of the router or gateway located in the modem LAN,
and which acts as next hop for this network.
You can add multiple routes.
Click to delete the route.
BGP Configuration
For more information about BGP, refer to BGP on page 156.
This section is only available when BGP Support is enabled and Static Routes is
disabled.
Click + Add to add a BGP neighbor and enter the parameters:

• Name: Give the BGP neighbor a name.
• AS: This is the AS number of the BGP neighbor. When using iBGP, this number should be the
same as the Local AS number.
• Local AS: Optionally define a local AS number. This setting allows changing the AS of the Newtec
Dialog network without impact on the external router connected to the terminal. In case of an AS
value change of a Newtec Dialog network, you should enter the old AS value here.
• Password: This is the password used for BGP authentication between BGP neighbors. The same
password should be configured on the BGP neighbor itself. Using a password is recommended
when using eBGP.
• Keep Alive Time: When a BGP neighbor has no update messages to send, it periodically sends
keep alive messages to keep the BGP session alive.
• Hold Time: The hold time specifies how long a router will wait for incoming BGP messages
(update or keep alive) before it assumes the neighbor is dead.
• Preference: BGP routers typically receive multiple paths to the same destination. The BGP Best
Path selection algorithm makes basic decisions to select the best routes to be installed into the
routing table. To customize the Best Path selection process, you can set a cost number value,
which determines the preference for the path. The path with the lowest value is preferred.
• Max Routes Learned: This is the maximum number of routes, which can be learned from this
neighbor. In case this maximum number is reached, DMA will report an alarm.
Set the Export parameters, which allows you to configure the AS path prepend option. Prepending
means adding one or more AS numbers to the left side of the AS path. Since BGP prefers a shorter
AS path, you can influence the Best Path selection on the router of your peer by using this option.
• Number of Prepends Added: Defines the number of times the AS number should be prepended.
Value 0 disables AS path prepending.
• AS Path Prepend: Defines the AS number to prepend. The number should be different from the
BGP neighbor's AS.
• Mode
– All: All routes are learned.

– Default Gateway only: Only a new default gateway is learned. This is the configuration
typically used at the hub side).
– Filtered: Select a predefined BGP filter. Filtering can be done on AS value and a set of host
addresses.
– None: No routes are learned.
Click on the BGP neighbor in the overview to edit the parameters.
Click + Show Advanced Settings... to enter the following parameters:

• Replace AS: This setting allows replacing the AS value in outbound routing updates with a new
AS value.
• New AS: This value is applicable in case the Replace AS check box is selected.
• Network Address Redistribution: When this check box is selected, the network directly
connected to the modem's LAN interface is advertised toward the hub. This setting is by default
enabled. When disabled, the network will not be advertised. Note: A generic setting of the
terminal network is Allow ICMP and SNMP Support. Once the network is no longer advertised
toward the hub, these functions will no longer be available.
• Auto Summary: When this check box is selected, BGP will automatically advertise the classful
network if you have the classful network or a subnet of this network in your routing table.
16.2.4.1.2 Shared Subnet
Configuring a shared subnet requires at a minimum defining the VLAN used on the LAN network
behind the modem, and the IP version.
The satellite network in which the modem is provisioned and the VNO will define the IP pools to
which the modem has access. The host will automatically get the first available IP address from that
pool.
It is possible to select a specific pool and assign a specific IP address to the host behind the modem,
as long as the pool belongs to the satellite network and the IP address is available.
The uplink part of the network is created during network resources provisioning. For
more information, refer to How to Create a Shared Subnet on page 173.
Click + Add to add a layer 3 network. A window appears.

Make sure to set Type to Shared Subnet.

General Parameters
• VLAN Tag: This parameter defines if traffic on the modem LAN is sent tagged or untagged. Using
a VLAN tag allows you to reuse IP addresses within the network.
• IP versions: Select the IP versions used on the modem LAN. You have to select at least one IP
version.When you select an IP version, the corresponding section appears at the bottom of the
screen. IPv4 is by default enabled.
• NAT/Firewall managed: Click the button to enable or disable management of the NAT and
firewall settings. When enabled, the NAT and Firewall settings can be configured in this interface.
When disabled, NAT and Firewall should be managed locally, through the modem GUI.
NAT and Firewall are only supported on MDM2010, MDM2210 Wi-Fi, MDM2510,
MDM3310, SMB3310, SMB3315, and MDM5010.
NAT is only supported for IPv4.
IPv4 Configuration
The parameters to enter depend on modem type and some specific settings.

• Service Label: This label specifies the IPv4 address pool, which the modem can use. If you do
not specify the service label, pools are automatically assigned. For more information on how to
use service labels, refer to Use of Service Labels for Shared Subnets on page 159.
• WAN Address: This parameter allows you to manually set the IPv4 address of the host
connected to the modem. The address should be part of the available IPv4 pool(s). If not set, the
IP address assigned to the host will be the next IP address available in the IPv4 pool(s).
enabled:

– The terminal sends the configured DNS servers via DHCP to its hosts.
Actions column.
The following parameter is only available for MDMxx10 series with the NAT/Firewall managed
value set to Yes and the NAT Enabled value not checked.
• Firewall Profile: Use this paramtere to block the incoming traffic based on firewall policy rules.
The firewall policy rules are defined in a Firewall Profile. Select the profile that you want to apply.
For more information on how to create a firewall profile, refer to Manage Firewall Profiles on page
221.
The following parameters are only available for MDMxx10 series with the NAT/Firewall managed
value set to Yes and the NAT Enabled value checked.
• LAN Address: This is the IPv4 network address of the LAN network behind the modem.
• LAN Prefix: This is the size of the LAN network. The number is the count of leading 1 bits in the
• Port Forwarding: The port forwarding rules apply to the LAN network. Click + Add to add a rule
and enter the following parameters:
– Description: The description of the port forwarding rule.
– Public Port(s): This is the public port to which the rule applies. You can enter a port range
by separating the start and end port with a hyphen (for example 5000-6000).
– Local IP Address: This is the local IP address to which the rule applies. This IP address
should be part of the LAN network.
– Local Port(s): This is the local port to which the rule applies. You can enter a port range by
separating the start and end port with a hyphen (for example 5000-6000).
– Protocol: The protocol to which the rule applies can be UDP, TCP or both.
You can add multiple rules.
Click to delete the rule.
IPv6 Configuration


• Service Label: This label specifies the IPv6 address pool, which the modem can use. If you do
not specify the service label, pools are automatically assigned. For more information on how to
use service labels, refer to Use of Service Labels for Shared Subnets on page 159.
• LAN Address: This parameter allows you to manually set the IPv6 address of the host connected
to the modem. The address should be part of the available IPv6 pool(s). If not set, the IP address
assigned to the host will be the next IP address available in the IPv6 pool(s).
• LAN Prefix: This is the size of the IPv6 network. The number is the count of leading 1 bits in the
• Routed Prefix Address: This is the IPv6 network address of the routed prefix range.
• Routed Prefix: This is the size of the routed prefix range. The number is the count of leading 1
enabled:
– The terminal sends the configured DNS servers via DHCP to its hosts.
Actions column.
16.2.4.2 Return Multicast
In case hosts behind the modem need to send multicast traffic, you should define the corresponding
multicast circuits. For more information about multicast, refer to Multicast on page 345.
16.2.4.3 Route Advertisement
Select the route advertisement mode:

• Always: The modem is not allowed to log on to another satellite network. This is used for fixed
terminals.

• Logon state based: The modem is allowed to log on to another satellite network. Selecting this
value will make sure that the the terminal LAN is advertised to the satellite network via the OSPF
or BGP routing protocol when logged on. It also implies that the modem is provisioned on other
satellite networks as well.
The route advertisement is automatically Always in the following cases:

• Attachment type is dynamic;
• Return link technology is HRC Mx-DMA, MRC NxtGen Mx-DMA or 4CPM MF-TDMA;
• COTM and beam roaming are disabled.
The mode cannot be changed.
The route advertisement is automatically Logon state based in the following cases:
• Attachment type is dynamic;
• Return link technology is HRC Mx-DMA or MRC NxtGen Mx-DMA;
• Beam roaming is enabled.
The mode cannot be changed.
The Logon state based route advertisement is only supported with HRC and MRC
return link technology and dedicated subnets.
If you have configured a shared subnet, the system will notify you that the shared
subnets will be removed.
The Logon state based advertisement route can be selected in the following cases:
• Attachment type is static and the return link technology is HRC;
• Attachment type is dynamic, the return link technology is HRC Mx-DMA, COTM is
enabled but beam roaming is disabled.
16.2.5 How to Configure Layer 2 Settings
Layer 2 network resources can only be configured on a 4IF or XIF hub module with HP
switches.
The Layer 2 tab is not available for terminals with a dynamic attachment profile. For
more information about the attachment type, refer to How to Configure Service Settings
on page 240.
You need to configure at least one layer 3 or layer 2 network.
The terminal can be linked to one or more layer 2 networks.

A layer 2 or L2 network is a point-to-point virtual connection and can be considered as a virtual
Ethernet pipe, which establishes isolated communication between two devices. A L2 network
connects an uplink network (1 in the figure below) on the hub side with a single LAN network on the
modem side (2 in the figure below).

The L2 network is identified by a configurable single or double VLAN tag on the uplink interface and
by a configurable single VLAN tag on the LAN interface of the modem. The supported VLAN tagging
is according to the IEEE802.1Q standard (0x8100). You can use the different VLAN tags on the hub
and modem for the same L2 network.
Uplink Input Modem LAN Output Actions
VLAN S + VLAN C VLAN C • Strip VLAN S

• Transparent forwarding
VLAN S + VLAN C VLAN C* • Strip VLAN S

• Translate VLAN C to VLAN C*
VLAN C VLAN C Transparent forwarding
VLAN C VLAN C* Translate VLAN C to VLAN C*
• S-VLAN = Service Provider VLAN (can be untagged). This corresponds with the VLAN defined in
the Hub Termination Point. For more information, refer to How to Create a Hub Termination Point
on page 186.
• C-VLAN and C*-VLAN = Customer VLAN (C-VLAN and C*-VLAN can be the same). The C-VLAN
corresponds with the Hub VLAN Tag and C*-VLAN corresponds with the Terminal VLAN Tag.
Both VLANs are set in this interface. Untagged traffic on the modem LAN is not supported.
The interface of the Layer 2 tab is shown in the screenshot below.

Click + Add to add a layer 2 point-to-point connection and set the following parameters:
• Hub Termination Point: Select the identifier of the hub termination point that applies to the
subnet.
• HUB VLAN Tag: This is the VLAN tag used for traffic from the hub to the terminal. The tag should
be unique for layer 2 virtual connections (VCs), which are connected to the same hub termination
point. The value ranges between 1 and 4094. If the hub termination point uses an untagged VLAN,
the VLAN tag should not conflict with the VLAN IDs of other hub termination points.
• Terminal VLAN Tag: This is the VLAN tag used for traffic from the terminal to the hub. The tag
should be unique on terminal level across L3 networks and L2 VCs. The value ranges between 1
and 4094.
• MTU: This is the Maximum Transmission Unit and corresponds with the Ethernet packet including
the Ethernet header, Layer 2 VC VLAN tag and user IP data. Enter a value between 1518 and
1760 bytes.
• Group ID: The group ID allows to identify a set of layer 2 VCs. This ID can be used in the layer 2
rules specified in the classification profiles. For more information, refer to
How to Create a Classification Profile on page 192.
• Mobile Backhaul Network: Click the button to mark the virtual connection as a mobile backhaul
network or not. When enabled, the layer 2 network is considered to carry GTP traffic and traffic
optimization inside the GTP tunnel can be performed.
– When the VC is used for mobile backhauling, the GTP V1 UDP Port needs to be specified.
The default value is 2152.
• Click Confirm to create the layer connection or click Cancel to discard the settings.
• You can add multiple layer 2 connections.
Click in the Actions column to edit the layer 2 connection.
Click in the Actions column to delete the layer 2 connection.
16.2.6 How to Configure Monitoring Settings

The interface of the Monitoring tab is shown in the screenshot below.
Select the Monitoring Type:

• Advanced: Choose this type if you want to collect metrics in real-time. The polling interval for the
metrics is 30 seconds by default. This type of monitoring requires quite some CPU power,
because of the sampling rate and the amount of metrics that are being collected at every sample.
The number of terminals configured for advanced monitoring should therefore be limited.
The number of advanced modems can be hard limited per VNO. Refer to How to Create a VNO
on page 144 for more information.

This monitoring type automatically includes standard monitoring.

• Standard: Choose this type if you want to collect averaged metrics. The metrics are averaged
over 5 minutes. Less metrics are polled than the Advanced type but more terminals can be
monitored.
• None: Choose this type if you do not want to collect any metrics for this modem.
When the Monitoring Type is set to Advanced, the Monitoring Option appears. Select one of the
following values:
• Local: Only terminal related metrics from the hub are monitored. The extra terminal metrics are
not fetched over the satellite link. This is the default value.
• Remote: Additional terminal metrics, such as terminal errored frames, modem temperature, RX
level statistics, etc. are fetched over the satellite link every 10 seconds. Keep in mind that this
monitoring option consumes satellite resources.
In case you have a large number of mobile terminals (>2000) and satellite networks
(>25) Standard monitoring must be disabled. If standard monitoring is enabled, the
DMA will run into severe performance issues.
This means that you must not select the standard monitoring type and that, when you
select the advanced monitoring type, the standard monitoring part must be disabled.
Only ST Engineering's personnel can disable the standard monitoring part in advanced
monitoring. Contact ST Engineering's customer services to request the change.

16.2.7 [optional] How to Configure Wi-Fi Settings
Wi-Fi is an optional feature and only supported on the MDM2010 and MDM2210.
The interface of the Wi-Fi tab is shown in the screenshot below.
Set the parameters:

• Managed: If set to Yes, the Wi-Fi settings can be configured here. If set to No, the Wi-Fi settings
should be managed locally, through the modem GUI.
• Wi-Fi Enabled: Select the check box to enable Wi-Fi on the MDM2210.
• Country Code: Indicates in which country the Wi-Fi is activated.
• Channel Selection: By default the Wi-Fi channel is automatically selected. Switch the channel to
reduce interference and improve the Wi-Fi signal.
• Tx Power: Select the appropriate power from the drop down list. If necessary, reduce the
transmitted power to avoid interference with other surrounding Wi-Fi networks.
• SSID: The SSID and initial password key can be found on the product label. The label is located
on the modem’s side panel.
• WPS: Select the check box to enable WPS. Wi-Fi Protected Setup is a feature that allows you to
easily connect WPS-supported client devices. For example, the MDM2210 and a smartphone.
1. Press the WPS button on your MDM2210.
2. Within two minutes, press the WPS button on your client device. The MDM2210 and the
client device should be connected now.
• Encryption Type: Select your encryption protocol.

– None: No encryption is not recommended. Use this only in a secure and private
environment.

– WEP: WEP stand for Wired Equivalent Privacy.

• WEP 64: Encryption key is a hexadecimal value with a length of #10.
• WEP 128: Encryption key is a hexadecimal value with a length of #26.
– WPA: WPA stands for Wi-Fi Protected Access and is more robust than WEP.
• WPA: Can work with TKIP as well as CCMP.
• WPA 2: 802.11i, WPA2 only works with CCMP.
• WPA Mixed: Permits the coexistence of WPA and WPA2 clients on a common SID.
• Encryption Key: This parameter is only displayed when encryption is enabled (WEP or WPA).
The default encryption key can be found on the product label.
• WPA Cipher: Standard security ciphers are part of both WPA and WPA2 encryption. You choose
whether you want to apply either the newer CCMP, or TKIP, or both. Cipher suites dynamically
generate unique session keys for each session and periodically change the keys to reduce the
likelihood of a network intruder intercepting enough frames to decode a key.
– TKIP: Temporal Key Integrity Protocol.
– CCMP: Counter Mode with Cipher Block Chaining Message Authentication Code Protocol.
This protocol is more robust than TKIP. This encryption protocol is based on the Advanced
Encryption Standard or AES.
– TKIP + CCMP: This is a combination of the previous protocols.
16.3 Batch Actions

Batch actions are actions that can be performed on one or more terminals simultaneously. Following
batch actions exist:
• Lock Terminal(s)
• Unlock Terminal(s)
• Edit Terminal(s)
• Delete terminal(s)
Lock Terminal(s)
Terminals in locked state cannot log on to the Dialog system, although these terminals remain
configured in the configuration database.
To lock the terminal(s), execute the following steps:
1. Select one or more terminals on which the action must be performed and click Batch Actions in
the upper right of the window.
2. Select Lock Terminal(s) from the drop-down menu. A pop-up message appears requesting
you to confirm or cancel the action.
arrow:

Unlock Terminal(s)
To unlock the terminal(s), execute the following steps:
2. Select Unlock Terminal(s) from the drop-down menu. A pop-up message appears requesting
arrow:
Edit Terminal(s)
To edit the terminal(s), execute the following steps:
2. Select Edit Terminal(s) from the drop-down menu. The pop-up window shown below appears.
3. Select the check box of the setting you want to modify and enter the new value.
You cannot modify all settings. Only some general modem, service, HRC Mx-DMA
and mobility settings are editable.
4. Click Edit (async) to execute the action or click Cancel to discard the action.
arrow:

Delete Terminal(s)
This action removes the terminals from the configuration database.
To delete the terminal(s), execute the following steps:
2. Select Delete Terminal(s) from the drop-down menu. A pop-up message appears requesting
You have two options to execute the action, which are visible when you click the drop down
arrow:
To consult the overview of asynchronous tasks, execute the following steps:

1. Click Batch Actions in the upper right of the window and select Overview Asynchronous
Tasks.
2. Click to view the details of a task.

Manage Auto Attachment Prototype
17 Manage Auto Attachment Prototype

An Auto Attachment Prototype includes the MAC addresses of whitelisted terminals and a modem
template that is used to provision the whitelisted terminals when logging on. For more information,
refer to Whitelisted Terminals on page 232.
17.1 How to Open the Auto Attachment Prototypes Web

Interface
To open the web interface of the Auto Attachment Prototypes, execute the following steps:
3. Click Terminals in the surveyor tree or in the visual overview.

4. Click Auto Attachment Prototypes in the surveyor tree or in the visual overview.
17.2 How to Create an Auto Attachment Prototype

To create an Auto Attachment Prototype, execute the following steps:
1. Open the Auto Attachment Prototypes provisioning interface as described in
How to Open the Auto Attachment Prototypes Web Interface on page 266.
3. Click + Create New Auto Attachment Prototype.
4. Go to step 5.
OR
1. Open the Terminal Provisioning interface as described in
How to Open the Terminal Provisioning Web Interface.
3. Click + Create New Terminal and select the Auto Attachment Prototype check box in the
Modem tab. This modem configuration will be used as the modem template of an auto
attachment prototype.

4. Enter all parameters and click Apply.

5. The following window appears:
Set the parameters:

– MAC Addresses: Click + Add to add the MAC address of a whitelisted terminal. The MAC
address can be found on the label at the bottom of the modem or via the modem GUI. The
MAC address of a modem always starts with 00:06:39. Click to validate the range or
click to discard the setting.

You can add multiple MAC addresses.
Click in the Actions column to edit the MAC address.
Click in the Actions column to delete the MAC address.
Click in the Actions column to provision the modem using the modem
template.
6. Click Validate Prototype in the upper left of the window to verify the modem template. If the
template has missing or incorrect settings, the corresponding error messages display.
The template configuration has the following restrictions:

• The return link technology is 4CPM and MRC;
• The layer 3 network is a shared subnet;
• The attachment type is dynamic;
• The corresponding satnet should have the auto attachment feature enabled.
Mind that the Validate Prototype button will not verify upon these restrictions,
except for the last one.
7. Click Edit Modem Template to change the template settings. You are directed to the Terminal
Provisioning interface from where you can change the settings. Click Apply to save the
settings or click Discard to cancel. You return to the Auto Attachment Protoype provisioning
interface.
8. Click Apply to save the prototype or click Discard to cancel. Check the log panel for validation
messages.
Click on the prototype in the overview to edit the parameters.
Click in the Actions column to delete the prototype.

Manage Inventory
18 Manage Inventory
Inventory management informs the Dialog system about the physical hub module:
• Where is it located?
• How is it set up?
• How many satellite networks will it serve?
• What are the redundancy schemes?
There are two provisioning interface for managing the inventory: Gateway Provisioning on page 269
and Hub Module Provisioning on page 269.
The initial inventory management is done during the installation of the hub module.
For more information, refer to the corresponding Newtec Dialog Hub Installation Guide.
18.1 Gateway Provisioning

This is the provisioning interface where you define the gateway or physical location of your hub
module. Each provisioned gateway is a node in the surveyor tree.
A gateway is provisioned during the installation of a hub module. For more information,
refer to the corresponding Newtec Dialog Hub Installation Guide.
18.2 Hub Module Provisioning

This is the provisioning interface where you define the configuration of your Dialog hub module. A
hub module is linked to a gateway. Each provisioned hub module is a node in the surveyor tree. The
hub module node is located under the gateway node. If you are using a 4IF or XIF hub module, you

Manage Inventory
will also always find an NMS node, independent if the NMS is embedded or stand-alone. If you are
using a 1IF hub module, you will only find an NMS node when the NMS is stand-alone.
The initial provisioning of the hub module is performed during the installation of the hub module.
The provisioning of the hub module should be updated whenever a hardware change occurs, such
as adding demodulators for redundancy or devices for a new satellite network.
For more information about this interface, refer to the corresponding Newtec Dialog
Hub Installation Guide.

Updating Terminal Software
19 Updating Terminal Software

There are a number of cases where terminals in the field should receive new software:
• Enabling features.
• Fixing software bugs.
• Updating terminals that have an old factory software, for instance because they were kept in a
warehouse for a long time.
Terminals can receive new software from the hub over the satellite link. The hub "airs" the software
using a software multicast carousel. If a terminal is logged in and has a lower software version than
the one that is being aired, it will download the new software.
The hub can air multiple software streams and you can define which terminals are allowed to
download which software streams.
The terminal uses two flash software banks. The bank on which the oldest software version is
residing is erased once the complete firmware image has been downloaded. After erasing this old
version, the new version is copied to this bank. The other bank still has the previous software
version stored. It is possible to roll-back to the previous software if necessary. For example if a
Cyclic Redundancy Check (CRC)-check on the downloaded new firmware fails, an automatic
rollback to the previous firmware is triggered.
A terminal reboots automatically after downloading and installing the new firmware in the flash
memory. The whole process only takes a number of minutes.
When new firmware is being aired towards the terminals, a part of the forward link capacity is
consumed. This used amount is determined by the defined data packet rate and the number of
software multicasts that are being aired.
Via the Software Multicast web interface it is possible to:
• Start or stop the airing of terminal software.
• Create a software multicast or edit an existing software multicast.
• Delete a software multicast configuration.
19.1 How to Open the Software Multicast Web Interface

To open the web interface of the Attachment Profiles, execute the following steps:

3. Click Software Terminal Upgrade in the surveyor tree or in the visual overview.

19.2 How to Create a Software Multicast

To create a Software Multicast, execute the following steps:
1. Open the Software Terminal Upgrade provisioning interface as described in
How to Open the Software Multicast Web Interface on page 271.
3. Click + Create New Software Multicast.


– Identifier:The identifier is the combination of the HNO domain name and an arbitrary
– Satellite Network: This is the identifier of the satellite network that should air the software.
You can select multiple satellite networks.
– Data Packet Rate: This is the airing rate of the software in kbps. The rate ranges from 16
to 850 kbps. Make sure that the Data Packet Rate is not too high. The software multicast
stream uses the most robust MODCOD and having a high packet rate could consume quite
some bandwidth.
– Software Update Group: This number between 0 and 15 allows you to update a subset of
terminals. Only terminals that are instructed to use this software update group ID will be
able to download the aired software. A terminal is made aware of this ID during its
provisioning. For more information on how to provision the software update group ID, refer
to How to Configure Modem Settings on page 235. By default, terminals belong to software
update group 0. If no specific group should be used, it is sufficient that terminals are locked
on the forward in order to receive the software. If a specific software update group should
be used, terminals need to have established connectivity in the return link as well in order
to fetch the provisioned configuration.
– Minimal Version: This is the minimal version number of the software that terminals need
to have for being able to log in to the network. As long as the software version of the
terminal is lower than this minimal version, the terminal will not setup return link
connectivity.
For example: if a terminal is provisioned to use HRC as a return link technology, and the
currently installed software does not support HRC, it is advised to set the minimal software
version value to at least 3.0.1.2 and the software group value to 0. This implies that the
terminal locks on the forward link, downloads the new aired software (if present) and
doesn't establish return link connectivity during the whole terminal software update
process.
If it is OK to have return link connectivity during the software update process, then the
minimal software version value can be set to any value lower than the current software
version. The software update group value can be set to a value between [0-15], depending
on the situation.
– Firmware Image: Click Select a (.bin) file and browse for a firmware image on your
computer. Firmware images are available via our Customer Service department.
Click Show Advanced Settings... to enter the following parameter:

– Receiver Timeout: This is the time that a terminal waits after the last received software
data packet before discarding the download. The value ranges from 2,000 to 10,000 ms.
The default value is 2,000 ms. If the modem loses lock with the forward carrier during
software download (for example due to sudden change of weather conditions, or when
attempting to establish return link connectivity) and the timeout value is expired, the
download is discarded. When the forward lock is back, the download will start from the
beginning. This scenario can be avoided by increasing the timeout value.
messages.
In the Software Multicast overview, the Hardware ID Match corresponds with the
identifier of the hardware variant of the terminals which are targeted by this download.
This identifier is included in the firmware image.
Click on the software multicast in the overview to edit the parameters.

Click Start Airing or Stop Airing to start or stop airing of the software multicast.
Click Stop All to stop the airing of all software multicasts.
Click in the Actions column to delete the software multicast.

Terminal Line Up
20 Terminal Line Up
The goal of the line-up procedure is to determine the clear sky modem output power for a given
allocated bandwidth (which is equivalent to defining a power spectral density at the modem output).
It is also used to get an indication of the cable loss, BUC gain and antenna gain (as these can differ
per remote terminal). The terminal line-up procedure uses the 'installation carrier' feature.
The line-up settings are reusable over all return technologies, allowing to switch from one return
technology to another without violating emission constraints (PEB constraints).
The terminal line-up procedure is available for all modem types, except MDM2200 and MDM2210.
MDM2200 and MDM2210 will always transmit at iLNB saturated power.

To avoid saturation of the satellite transponders, it is important that transmitting terminals do not
exceed the power spectral density threshold. The same applies for the uplink, as described in
Return Link Calibration on page 282. Power spectral density (PSD) is defined as:
power spectral density [dBm/Hz] = nominal output power [dBm] -

10*log(Occupied bandwidth [Hz])
During terminal provisioning, there is the choice between two power control modes:
• Nominal
A nominal bandwidth and nominal output power are configured in the line up settings. The actual
modem output power is set in function of the transmitted carrier:
actual modem output power=nominal output power + 10*log(allocated

bandwidth/occupied bandwidth)
Where:
– Allocated bandwidth = symbol_rate*(1+roll_off) for S2 carriers
– Allocated bandwidth = max carrier bandwidth for 4CPM carriers (largest carrier bandwidth
of the Return Carrier Groups within the SatNet)
– Allocated bandwidth = symbol rate*1,05 for HRC and MRC
• Absolute
The actual modem output power is set to the configured absolute output power value. This mode
overrules the nominal settings if activated.

Terminal Line Up
Have a look at the following example:
A terminal uses a 1 Mbaud DVB-S2 installation carrier with a Roll-off of 20% transmitting at -30 dBm.
The Occupied Bandwidth is calculated as:
Occupied Bandwidth = Symbol Rate * (1 + Roll-Off

factor)
Hence the occupied bandwidth of this installation carrier = 1 * (1+0,2) = 1,2 MHz. Suppose the
operational carrier is a 2 Mbaud carrier with 10% roll-off. Consequently the allocated bandwidth = 2 *
(1+0,1) = 2,2 MHz.
Applying the above formula results in an actual modem output power of -30 dBm + 10 log(2,2/1,2) =
-30 dBm + 2,6 dBm = -27,4 dBm. In other words more power is required to maintain the same power
spectral density. The S2 Controller in the hub will inform the remote terminal to transmit at this
calculated power value.
Now suppose the modem switches from S2 to a 4CPM Return Capacity Group which contains three
return pools (1024 kHz MODCOD1, 512 kHz MODCOD0 and 256 kHz MODCOD0). The line up
settings that were set during terminal provisioning (and that were based on a DVB-S2 installation
carrier) remain the same.

Terminal Line Up
In clear conditions this results in an actual power of -30 dBm + 10 log(1024/1200) = -29,9 dBm. If it
then starts to rain causing a 6 dB rain fade of the signal, the smallest carrier bandwidth will be used
by the modem (due to ARL). But the modem output power remains at -29 dBm (the actual modem
output power is still calculated based on the highest configured carrier in the Return Capacity
Groups of the SatNet, which is 1024 kHz). On a spectrum analyzer at the modem output you would
notice a smaller carrier with a higher 'amplitude' than the clear sky 1024 kHz signal but at the
satellite the same spectral density will be measured (rain fade lowers the power of the transmitted
signal from the modem).

Terminal Line Up
20.2 Procedure
The terminal line up procedure is coordinated by the satellite operator or Hub Network Operator
(HNO). The operator needs access to the Terminal Provisioning web interface. Please refer to
Manage Terminal Provisioning on page 232 for more details.
Access to the remote terminal is either via an installer on site, or via an out-of-band connection. The
operator determines the installation carrier parameters such as frequency, installation carrier symbol
rate and installation carrier type (pure carrier / modulation). Installation carrier settings are entered
via the local modem GUI.
To enter the installation carrier settings on the remote terminal, login to the modem GUI as expert.
1. Type “?ilogin” behind the http://192.168.1.1/cgi-bin/index URL.
2. Enter the password in the text field.
The expert password can be obtained from your modem supplier.
3. Go to the installation carrier menu and set up an installation carrier. Use the parameters
received from the satellite operator or HNO. Set the output power to the lowest power possible.

Terminal Line Up
4. Click Start New to transmit the installation carrier. The operator will measure the transmitted
signal. Increase the transmit power level gradually until an approval from the satellite operator is
received.
5. When the line up procedure is finished, the Line Up Settings of can be configured:
– Nominal Occupied Bandwidth: This is the bandwidth in kHz of the installation carrier that
is used for the line up procedure.
• If the installation carrier uses DVB-S2 or S2 Extensions, the bandwidth of the carrier
equals symbol rate * (1 + roll-off).
• If the installation carrier uses HR or MRC, the bandwidth equals the symbol rate * 1.05.
We recommend using a typical symbol rate of 185 kBaud.
– Nominal Output Power: This is the terminal output power in dBm that has been measured
and approved by the satellite operator or HNO during the line-up procedure.
For more information on how to enter the line up settings, refer to

Finally, the line up values are used to calculate the operational carrier transmit level:
Return Link Operational Use of Line-Up Settings

Technology
4CPM Operational carrier TX level = nominal output power +10*log10(highest

configured 4CPM carrier BW / occupied bandwidth)

Terminal Line Up
S2 Operational carrier TX level = nominal output power +10*log10(1+roll-off)*

carrier_symbol_rate / occupied bandwidth)
HRC Login carrier level = nominal output power +10*log10(1.05*login carrier

symbol rate/occupied bandwidth)
MRC Login carrier level = nominal output power +10*log10(1.05*200000/occupied

bandwidth)

Return Link Calibration
21 Return Link Calibration

The operation of the HRC or MRC technology is controlled by the HRC/MRC controller which
resides in the hub. The controller needs an upfront knowledge of threshold values and parameters
to make correct decisions when assigning HRC/MRC-based return resources to remote terminals.
Therefore, a calibration procedure needs to be executed to allow proper operation. The goal of this
calibration procedure is to instruct the controller what the target power spectral density is for all
terminals associated to a particular MCD (as seen on that MCD L-Band input).
BEPD (Bandwidth Equivalent Power Density) is the signal power density at a given observation point
that corresponds to the authorized uplink signal level.
If the observation point is in the hub RX signal chain, the Actual BEPD level at that point varies with
estimated attenuation or gain changes in the downlink signal path upstream from the observation
point, for example due to a downlink fade. Actual BEPD level is displayed in Dialog as an attribute of
the MCD, the observation point implied here is the MCD input.
Essentially the calibration procedure is used to determine the clear sky downlink C/N value, and the
controller will keep track of that ratio to avoid the BEPD threshold to be exceeded during operation.
Running the calibration procedure is required for each satellite network (each IF), and for each
transponder used in that satellite network, since the downlink C/N can be different on each IF and
for each transponder.
A hub calibration is necessary:
• At initial hub installation.
• Whenever a new transponder is used on a satellite network.
• Whenever a change is made to the hub RX chain which has significant impact on the clear sky
down-link C/N (for example inserting/extracting splitters, LNAs, attenuators).
• When either the satellite operator or the HNO are not satisfied about the actual PEB.

21.1 Measuring and Calculating the Values

To perform the return link calibration procedure, execute the following steps:
1. Install the reference terminal and perform the Terminal Line Up on page 276 procedure during
clear sky conditions. During the transmission of the installation carrier, the satellite operator will
measure the power level and instruct the terminal operator to increase or decrease the
transmitted power until the terminal reaches the satellite operator approved Power Spectral
Density.
2. [Optional] Enter the following parameters in the Terminal Provisioning interface:
– Line up settings in the Modem tab, based upon the results of the line up procedure.
– Power Control Mode should be set to Nominal in the Service tab.
For more information about how to enter theses settings, refer to

How to Create a Terminal on page 234.
3. At the hub side, measure the difference between the noise floor and the installation carrier with
a spectrum analyzer or similar. Write down this value as "difference [dB]".
4. Calculate .
5. An arbitrary reference point for the N0 is chosen. For example, meanN0 = -130 dBm/Hz.
6. Calculate meanC0 = meanN0 + C0/No_target.
21.2 Setting the Values

1. Open the Return Link Calibration configuration interface.
– Access the NMS GUI. For more information, refer to How to Access the NMS GUI on page
8.
– Click Newtec Dialog at the top of the surveyor tree.

– Click Satellite Resources.
– Select the beam identifier and Satellite Network that corresponds with the return link.
Click Resource Provisioning and then click Return Link Calibration.
2. Click + Create New Return Link Calibration. The following entry appears in the overview.

3. Enter the C0 Mean and N0 Mean values that you have calculated in
Measuring and Calculating the Values on page 283.
Click in the Actions column to confirm or to discard the settings.
Click in the Actions column to link the return link calibration settings from the Satellite
Network
Click in the Actions column to unlink the return link calibration settings from the Satellite
Network.
Click in Actions column to delete the return link calibration entry.

Equalink®
22 Equalink®
22.1 Introduction
A satellite payload typically contains an input multiplexing or IMUX filter, a traveling wave tube
amplifier or TWTA, and an output multiplexing or OMUX filter. The IMUX filter selects the input
frequency band of the transponder, which is often slightly wider than your carrier. The TWTA
amplifies the signal. As a side effect, amplification increases the bandwidth of your carrier. The
OMUX filter cuts away the unwanted frequencies to avoid interference inside other frequency
bands.
Because the average power of the signal arriving at the TWTA varies, for example due to rain in the
uplink, most payloads also have a pre-gain stage, which performs automatic level control or ALC.
ALC ensures a constant drive level of the TWTA.
The goal of Equalink® is to achieve the most efficient communication link. An efficient
communication link means that the bandwidth and the power is used as efficiently as possible.
To get the most out of your transponder:
• Your carrier bandwidth should approach the bandwidth of the IMUX/OMUX filters. Because these
filters operate at very high frequencies in extreme conditions, imperfections in the filter response
introduce linear distortion into your signal. Linear Equalink will compensate for this linear
distortion so that you can further push your carrier bandwidth.
• Your carrier signal should get amplified as much as possible by the TWTA, which is achieved by
increasing the drive level of the TWTA. Non-linear Equalink can compensate for the non-linear
distortion that is introduced by the non-linear amplification, so that you can further push the drive
level.
In an nutshell, Equalink optimizes the satellite link performance by counteracting distortion effects in
a satellite link.

Equalink®
The following distortions can be present:

Linear Distortion
• Imperfections of the amplitude response of the transponder.
• Degradation caused by the phase response of the IMUX/OMUX filters lead to imperfections in the
group delay response.
Non-Linear Distortion
Non-linear distortion is characterized by two parameters:
• AM/AM (output amplitude versus input amplitude)
• AM/PM (output phase versus input amplitude)
These are caused by the non-linearity in the amplifier of the satellite.
The M6100 modulator is equipped with the linear and non-linear Equalink feature, which can be
individually enabled or disabled.
The MCM7500 modulator is equipped with the non-linear Equalink feature.
In a Dialog system you should only use the non-linear Equalink calibration procedure.
There is no need for linear Equalink predistortion as all Dialog VSAT modems have a
good linear equalizer on-board.
Equalink only has a benefit in case a single carrier per transponder is used and the
satellite transponder operates in saturated (non-linear) mode. In case of multiple
carriers per transponder, the satellite transponder typically operates in the linear,
non-saturated area (because of the applied backoff).
Enabling Equalink also has an impact on the distortion margin (DM), modulation loss (ML), Forward
ACM In and Forward ACM Down parameters. You can find these parameters in the Forward Link
web interface.

Equalink®
Following table shows the default DM + ML settings in case of a single forward carrier and a
saturated transponder. It is advised to use these default settings for correct Equalink behavior.
MODCOD DM+ML (dB) MODCOD DM+ML (dB)
QPSK 1/4 0.0 16APSK 2/3 0.7

QPSK 1/3 0.0 16APSK 3/4 0.7
QPSK 2/5 0.0 16APSK 4/5 0.9
QPSK 1/2 0.0 16APSK 5/6 0.9
QPSK 3/5 0.0 16APSK 8/9 1.3
QPSK 2/3 0.0 16APSK 9/10 1.3
QPSK 3/4 0.0 32APSK 3/4 1.3
QPSK 4/5 0.0 32APSK 4/5 1.5
QPSK 5/6 0.0 32APSK 5/6 1.5
8PSK 3/5 0.0
8PSK 2/3 0.1
8PSK 3/4 0.1
8PSK 5/6 0.1
It is not recommended to use the following MODCODs:

• QPSK8/9
• QPSK9/10
• 8PSK8/9
• 8PSK9/10
The performance of Equalink depends on many factors: the type of TWTA and its drive level, the
characteristics of the IMUX and OMUX filters, the uplink and downlink noise, the characteristics of
your signal, etc.

Equalink®
22.2 Procedure
22.2.1 M6100
To do a complete Equalink procedure, follow the steps in the presented order:
1. Satellite link analysis: on page 290 To verify the present conditions of the satellite transponder,
such as the TWTA drive level, uplink and downlink noise level. This step requires an MDM6000
or MDM6100 modem, typically located outside of the Dialog hub module.
2. Run an automated non-linear Equalink calibration procedure on page 292 using the same
MDM6000 or MDM6100 modem as in the previous step.
Make sure to disable Equalink on the modulator inside the hub module when
executing the calibration procedures.
3. Enter the results of the calibration procedure into the modulator inside the hub module.
4. Enable Equalink on the modulator.

Equalink®
22.2.1.1 Satellite Link Analyzer Procedure
Execute this procedure to know whether the transponder is in fixed gain mode (FGM) or automatic
level control (ALC).
• FGM: If your transponder is in FGM, calibration must be done under clear-sky conditions. It is
recommended to change the modulator output level for optimum link margin. Use the satellite link
analyzer to measure (search) the optimal modulator output level.
• ALC: In ALC mode, the gain of the transponder is fixed, regardless of uplink fading. Uplink
variations will not change the drive level of your transponder. If your transponder is in ALC mode,
the satellite link analyzer can tell you if the TWTA drive level is well configured. If not, it is
recommended to contact the satellite link operator to further increase the drive level by modifying
the ALC settings.
To execute this procedure, execute the following steps:
• It is assumed that the forward link can be received at the hub location (also known as
the Dialog gateway).
• It is recommended to do this procedure during clear weather conditions.
1. Power up a modem (MDM6000 or MDM6100). This modem is typically installed outside of the
Dialog hub module
2. Disconnect the TX cable from the M6100 modulator inside of the Dialog hub module and
connect it to the TX interface of the MDM6x00.
3. Use a VSAT antenna (similar to the one used for remote terminals) and connect its LNB to the
RX-interface of the MDM6x00. Default RX-interface is L-Band RX-A
4. Connect a PC with an Ethernet cable to the MGMT-1 interface of the MDM6x00. The default
management IP address of the MDM6x00 is 10.0.0.1/24. Make sure that the PC is part of the
10.0.0.0/24 IP range. If needed, you can re-configure the management IP address via the front
panel of the MDM6x00.
5. Open a web browser on the PC and enter the management IP address of the MDM6x00 in the
address bar. The Graphical User Interface (GUI) of the MDM6x00 opens.

Equalink®
It is advised to use Firefox 10 or Google Chrome as standard browser, but the GUI can
also run on other compatible browsers like Internet Explorer 9, Safari …
6. Log in as expert.
– Click Logged-in as .... The User options window is displayed.
– Click Switch User to change the user profile. The Login window is displayed.
Enter the credentials:

• User Name: expert
• Password: expertexpert
7. Click the Equalink menu item in the Tasks pane and select Satellite Link Analyzer. A pop-up
window appears.
Enter the following parameters:

– Demodulator Location: Select Local Demodulator from the drop down list
– Demod IP Address: Enter 0.0.0.0.
– Uplink Fade Simulation: Select the check box to get an indication if the satellite is in FGM
or ALC mode.
The IBO/OBO (Input Back-Off to Output Back-Off Ratio) is measured by temporarily
decreasing the modulator output level.
• When in FGM, the IBO/OBO varies when the modulator output level changes;
• When in ALC, the IBO/OBO does not vary when the modulator output level changes.

Equalink®
8. Click Start. A progress bar is displayed.
9. Click log file to view the ongoing analysis in a separate browser page. Refresh the page to see
the different measurements.
10. When the measurements are completed you can view the summary in the log file. Click log file
to view the summary. The summary shows whether the transponders in FGM or ALC mode.
11. Click Commit to complete the procedure.
22.2.1.2 Automated Non-Linear Calibration Procedure on MDM6x00
The goal of the procedure is to reach the highest link margin for the transponder.
Before starting this procedure it is advised to make a planning and contact your
Satellite Operator.
Make sure the Satellite Link Analyzer Procedure on page 290 is done.
• It is assumed that the forward link can be received at the hub location.
• It is recommended to do this procedure during clear weather conditions.
To execute this procedure, follow the steps below:

1. Make sure the TX cable from the M6100 modulator inside of the Dialog hub module is still
connected to the TX interface of the MDM6x00.
2. Make sure the LNB of a VSAT antenna (similar to the one used for remote terminals) is
connected to the RX interface of the MDM6x00. Default RX-interface is L-Band RX-A.
3. Connect a PC with an Ethernet cable to the MGMT-1 interface of the MDM6x00. The default
management IP address of the MDM6x00 is 10.0.0.1/24. Make sure that the PC is part of the
10.0.0.0/24 IP range. If needed, you can re-configure the management IP address via the front
panel of the MDM6x00.
4. Open a web browser on the PC and enter the management IP address of the MDM6x00 in the
address bar. The Graphical User Interface (GUI) of the MDM6x00 opens.

Equalink®

6. Go to the Tree View tab and select Modulator.
Parameters on the modulator part of the MDM6x00 must match with the settings
used on the M6100 modulator within the Dialog hub module!
You can reach the modulator's web interface via the NMS GUI.
• Select the modulator via the surveyor tree. The modulator can be found under
the Physical Devices / Device Pools.
• Click webInterface in the upper left of the card navigation pane to open the
modulator's web interface.
– Mode: Use same value as the M6100.

– Transmit: Select the check box to enable transmission on the MDM6x00.
– Output Frequency: Use same value as the M6100.
– Roll Off: Use same value as the M6100.
– Output Level: Use same value as the M6100.
– Symbol Rate: Use same value as the M6100.
– Transponder Operation Mode: Select Single Carrier per Transponder - Non-linear
from the drop down list
7. Go to the Tree View tab and select Demodulator and enter the following parameters:
– Enable: Select the check box to enable the demodulator of the MDM6x00.
– Mode: same value as the M6100.

Equalink®
– Input frequency: This can be calculated by subtracting the Local Oscillator (LO) value of
the LNB from the downlink frequency of the forward carrier. For ore information about this
frequency, refer to Frequencies on page 41.
– Symbol rate: same value as the M6100.
– Roll Off: same value as the M6100.
– Input Selection: Indicates which RX-interface (A or B) is used on the MDM6x00. Default
value = L-BAND Rx A.
– Transponder Operation Mode: Use Multiple Carrier per transponder.
– Equalink Client: Select to check box to enable the Equalink client on the MDM6x00.
8. Click the Equalink menu item in the Tasks pane and select Automated Non-Linear.... A
pop-up window appears.

– Demodulator Location: Select Local Demodulator from the drop-down list
– Demodulator IP Address: Set to 0.0.0.0.
– Demodulator ID: Select the demodulator identifier from the drop-down list.
– Calibration Traffic Source: Select Internal test traffic from drop-down list
– Calibration MODCOD: Select the highest MODCOD value linked to the forward link from
the drop-down list. To know this MODCOD, check the ModCods tab in the Forward Link
provisioning interface.

Equalink®
Click Start to save the settings. An information box is displayed, providing feedback on the
difference between Live Traffic and Internal Test Traffic.
9. Click Yes to start the calibration or No to cancel the calibration and change the settings if
needed.
During the calibration process, a progress bar is displayed:
– Click log file to follow the different steps that are performed during the calibration.
– When the measurements are performed, the link margin improvement is displayed.
10. Click Commit to confirm the link margin improvement.

Equalink®
11. Go to the Tree View tab and select Modulator. Scroll to the Equalink section and select the
check box to enable non-linear Equalink.
The AM/AM and AM/PM values to use on the M6100 modulator of the Dialog hub module are
now displayed.

Equalink®
22.2.1.3 Enable Non-Linear Predistortion on M6100 of Dialog Hub Module
To enter the AM/AM and AM/PM values that are the result of the automated calibration procedure
and to activate non-linear predistortion on the M6100, execute the following steps:
1. Open the modulator's web interface through the NMS GUI.
2. Select the modulator via the surveyor tree. The modulator can be found under the Physical
Devices / Device Pools.
3. Click webInterface in the upper left of the card navigation pane to open the modulator's web
interface.

5. Open the detailed modulator view.

Equalink®
6. Go to the Link Optimization section and click the pencil icon next to Transponder Operational
Mode.Select Single Carrier per Transponder - Non-linear from the drop-down list.
Click to save the setting.

7. Click the pencil icon next to Maximum modulation order and select the maximum modulation
order from the drop-down list. For example if you selected 32APSK as highest modulation
scheme within your forward link, select 32-Ary from the drop down list.
Click to save the setting.

To know which MODCODs are linked to the forward link, check the ModCods tab in the
Forward Link web interface.

Equalink®
8. Click the Equalink menu item in the Tasks pane and select Automated Non-Linear
Calibration.
Enter the AM/AM and AM/PM values that you have retrieved via the calibration procedure.

Equalink®
Click Manual Non-Linear to save the settings.

9. Go to the Transponder Provisioning interface in the NMS GUI. See
How to Open the Forward Resources Web Interface on page 42. Enable Non Linear
Predistortion and set the calibration values to the ones that have been measured.
• For correct Equalink usage, it is important that the modulator settings match the
Equalink applicability parameters. If this is not the case, restart the calibration
procedure.
• If Equalink is enabled, the modulator rejects changes to the following parameters:
– Center frequency
– Symbol rate
– Roll-off factor
There is no error message informing the operator about this rejection.
10. When the parameters have been changed, they are not directly saved into the active
configuration. To save the parameters in the active configuration, execute the following steps in
the M6100 GUI:
– Click the Device menu item in the Tasks pane.
– Click Configurations. A pop-up window appears.
– Click Save.... Another pop-up window appears.

Equalink®
– Enter a name for your configuration or select a name from the drop down menu.
By default, the selected configuration is overwritten upon saving. Enter a name

to save the configuration under a new configuration file.
– Click Save Config. The new configuration is listed in the Configurations overview.
– To make the new configuration the boot configuration, click on the new configuration and
select Make Boot....
The boot configuration is indicated as BOOT.

11. Repeat these steps for the redundant modulator (if present).

Equalink®
22.2.2 MCM7500
The procedure requires:

• Dialog release 2.2.2 or higher.
• MCM7500 release 2.0 or higher.
The procedure includes the following steps:

1. Prepare the calibration setup.
2. Log the initial status.
3. Set the calibration configuration.
4. Measure the reference ALC level.
5. Switch to FGM mode and optimize the transponder's drive level.
6. Enable MCPRED.
7. Optimize the calibration parameters, drive level and define the maximum MODCOD.
8. Restore the operational state.
9. Enable ALC on the satellite transponder.
10. Remove the calibration setup.
We recommend to use the report template MCM7500 Single Carrier Predistortion

Calibration Report Template to note down the results of the different steps.
The procedure will interrupt normal operation. The duration of the entire calibration
procedure is about 60 minutes.
22.2.2.1 Calibration Setup
At the Hub Side

The MCM7500 has an Ethernet connection to your management backbone and an RF connection
towards the antenna.
At the Terminal Side

1. Your test terminal should be located in the center of the beam.
2. Your test terminal is a terminal with the largest antenna available.
3. Your test terminal should be operational.
4. Install an MDM6000 demodulator.

Equalink®
1. Insert a splitter between the outdoor unit and the test modem.
2. Connect one output (OUT) from the splitter to the test modem and the other OUT to the
MDM6000.
If your hub module is located within the RX beam, you can install the MDM6000 in the RX path
at the hub side. In that case, make sure to adjust the internal downlink noise in the MDM6000 to
simulate the best performing remote terminal (center of beam, largest antenna).
5. Connect a PC to the management interface of the MDM6000.
Access the NMS GUI

Refer to How to Access the NMS GUI on page 8.
22.2.2.2 Log Initial Status
1. Open the web interface of the MCM7500. Make sure that you are logged in as expert. For more
information, refer to How to Open the Web Interface on page 321.
2. Save the operational configuration of the MCM7500. Execute the following steps:
1. Click the Device menu item in the Tasks pane.
2. Click Configurations. A pop-up window appears.
3. Click Save.... and enter a name for your configuration.
4. Click Save Config. The configuration is now saved.
Example: Save the configuration as "<yyyymmdd>_dialog_INIT".
3. Note down the demodulator performance of the test modem in the report.
Report Table: Initial Status Dialog Test Modem ALC1 ON => Term.Rx.level_ALC1.
For more information, refer to Where to Find the Measurements on page 324.

Equalink®
22.2.2.3 Calibration Configuration
1. Set the redundancy of the device pool to which the MCM7500 belongs to manual. Execute the
following steps:
Select REDCTL-0.Controller.bband_x in the surveyor tree of the NMS GUI. Select Device
redundancy in the card navigation pane or via the drop-down box at the top left corner of the
card pane. Scroll to the Device Pools section and edit the DevicePool Redundancy Selection
for the device pool where the MCM7500 belongs to. Select Manual.
2. Configure the MCM7500. Execute the following steps:

1. Open the web interface of the MCM7500. Make sure that you are logged in as expert. For
more information, refer to How to Open the Web Interface on page 321.
2. Set the carrier parameters. Execute the following steps:

• Click Modulator.

Equalink®
Click to expand the information.

• Scroll to the Configuration Table and make sure that:
• The Roll-off is set to 10%.

Equalink®
• If the operational symbol rate of the modulator is > 133 Mbaud, the calibration
Symbol Rate is set to 133 Mbaud.
OR
• If the OMUX filter bandwidth is < 230 MHz, the calibration Symbol Rate is set to
80% of the OMUX filter bandwidth.
• Scroll to the DVB-S2 Configuration Table and make sure that the Slicing check box
is not selected.
• Scroll to the Non-Linear Equalink Multi Carrier Config Table and make sure
McPred-1 is disabled.
3. Set the modulator in PRBS mode. Execute the following steps:
• Go to the Tree View tab and select Root / BBF Generator.
• In the Configuration Table, click (+) Add or (+) Click here to add a new entry to create
a new entry or click the pencil icon to edit the existing entry.

Equalink®
Enter the parameters:

• Name: You can keep the default name or enter your own name.
• Enable: Select the check box.
• Bit Rate: Set the rate to ~50% of the maximum throughput. The maximum
throughput depends on the configured MODCOD (refer to the next step). To know
the percentage used, check the Physical Layer Efficiency parameter in the
Modulator GUI.
• ISI: You can keep the default ISI value.

• Frame Specification Mode: Set the mode to Single.
Click Update to create or update the entry. This automatically creates an entry in the
Single Frame Mode Specification Configuration Table.
• Click the pencil icon to edit the entry in the Single Frame Mode Specification
Configuration Table.

Equalink®
• Modcod: Set it to a MODCOD that the MDM6000 can demodulate. Do not use a
linear MODCOD. The MODCOD can/will change when executing the calibration
procedure.
Adapt the bit rate if needed (refer to the previous step).
Example: In our calibration test, we start with the 16APSK2/3 MODCOD.
• Pilots: Select the check box to enable the pilots.
Click Update to save the change.
• Go to the Tree View tab and select Root / BBF Connectivity.
• In the Configuration Table, click (+) Add to create a new entry or click the pencil icon
to edit the existing entry.
Enter the parameters:

• From Type: BBF Generator.
• From Name: Select the name of the PRBS transport stream that you have
created in the previous step.
• To Type: Modulator.
• To Name: Select the name of your modulator.

Equalink®
Click Update to save the change.
22.2.2.4 Measure Reference ALC Level
This step is only required if your transponder is in ALC mode.
If the transponder is in ALC mode, the clear weather RX level of the MDM6000 is used as the
reference ALC value.
1. Save the configuration of the MCM7500. Give it a different name than the initial configuration.
Execute the following steps:
1. Click the Device menu item in the Tasks pane in the web interface of the MCM7500.
Example: Save the configuration as "<yyyymmdd>_mdm6000_MCPRED_OFF".
2. Note down the demodulator performance of the MDM6000 in the report.
Report Table: Initial Status MDM6000 ALC1 ON => MDM6000.Rx.level_ALC1.
22.2.2.5 Optimize Drive Level
Make sure the transponder is set in Fixed Gain mode.
It is recommended to load the operational configuration of the MCM7500 before you

request the satellite operator to set the transponder in Fixed Gain mode as the change
might take some time. This ensures that your network is operational during this change.
Example: Load the configuration "<yyyymmdd>_dialog_INIT".
When the transponder is set to Fixed Gain mode, load the MCM7500 configuration that you have
saved in the previous step:
2. Click Configurations. A pop-up window appears with the saved configurations.
3. Select the correct configuration and click Load Config....
4. The configuration is automatically loaded.
Example: Load "<yyyymmdd>_mdm6000_MCPRED_OFF_ALC_ON".
Change the Output Level of the modulator and optimize the C/ND values of the MDM6000.
1. Monitor the C/ND and Link Margin value in the MDM6000. Execute the following steps:
1. Open the web interface of the MDM6000. For more information, refer to
How to Open the Web Interface on page 321.
2. Open the detailed view of Demodulator 1.

Equalink®
3. Scroll down to the ModCodStatistics section. Monitor the C/ND and Link Margin value.
2. Start with the operational output level of the modulator and the MODCOD set during
Calibration Configuration on page 304. Check the C/ND and the Link Margin value in the
MDM6000.

Equalink®
Change the MODCOD if the link margin allows it. Refer to Calibration Configuration on page
304 to set the MODCOD. Use the Satellite Network Calculator or SNC for the list of possible
MODCODs or refer to List of MODCODs on page 325.
Change the modulator's output level and verify the impact on the C/ND value. To change the
output level, go to the Modulator tab of the MCM7500 GUI and edit the Output Level field in
the Configuration Table. Take steps of 0.5 dBm.
We recommend to note down your optimization steps in the report.

Report: MCPRED OFF in FGM.
Example: The following table gives the result of the optimization steps during our calibration test.
MCM7500 MDM6000
Output MODCOD Carrier Input Link C/ND Comment

Level Level (dBm) Margin (dB)
(dBm) (dB)
-11 16APSK2/3 -33 4.39 13.1 Higher MODCOD is possible,

link margin is large enough to
skip some MODCODs.
16APSK77/90 -33 1.39 13.1 Link margin is large enough to

use a higher MODCOD.

Equalink®
32APSK32/45 -33 < -0.5 NA MODCOD not possible
-12 16APSK77/90 -33.5 1.56 13.33 Link margin is large enough to

32APSK32/45 -33.5 -0.07 11.85 MODCOD not possible
-13 16APSK77/90 -33.9 1.54 13.43 Link margin is large enough to

32APSK32/45 -33.9 0.44 12.28 MODCOD is possible
-14 32APSK32/45 -34.5 0.72 12.54 This is the optimum MODCOD

and modulator's output level
when MCPRED is OFF.
-15 32APSK32/45 -35.2 0.52 12.41 C/ND decreases
-16 32APSK32/45 -36 0.05 12 C/ND decreases
A good way to find the optimum output level is to take the average value of the output
levels that result in the optimum C/ND - 0.5 dB value.
Save the configuration of your MCM7500. Execute the following steps:

Example: Save the configuration as "<yyyymmdd>_mdm6000_MCPRED_OFF".
Verify the performance of the test terminal with the optimized drive level with MCPRED OFF.
Execute the following steps:
1. Load the MCM7500 configuration that you have saved before starting the calibration procedure
onto the MCM7500.
Example: Load "<yyyymmdd>_dialog_INIT".
2. Go to the Modulator tab of the MCM7500 GUI and edit the Output Level field in the
Configuration Table. Set it to the optimum drive level found in the previous step and apply the
changes.This might take a while.

Equalink®
Example: Set the output level of the MCM7500 to -14 dBm.

3. Save this configuration. You can overwrite the previously saved configuration.
Example: Save the configuration as "<yyyymmdd>_dialog_MCPRED_OFF".
4. Note down the demodulator performance of the test modem in the report.
Report Table: Status Dialog Test Modem at Optimized Drive Level in FGM.
Verify if the uplink HPA has sufficient RF power. Execute the following steps:
1. Connect a spectrum analyzer behind the HPA output. Use a span of ~2x calibration baud rate.
2. Verify that the difference between the regrowth and the carrier level is equal or larger than the
limits in the table below.
Maximum Modulation Order Limit (dB)
8PSK 28
16APSK 32
32APSK 34
64APSK 37
Note that 26 dB is the absolute minimum value allowed by satellite operators to avoid adjacent
interference.
Example: In the spectrum plot below the difference between the regrowth and the carrier level
is 32 dB, which is sufficient for MCPRED with 16APSK carriers.
If the difference is lower than the limit, MCPRED should not be used.

Equalink®
22.2.2.6 Enable MCPRED
1. Load the MCM7500 configuration that you have saved after the drive level optimization onto the
MCM7500. Execute the following steps:
Example: Load "<yyyymmdd>_mdm6000_MCPRED_OFF".
2. Go to the Modulator tab of the MCM7500 GUI. Scroll down to the Link Optimization
Configuration Table and set the Maximum Modulation Order to the highest MODCOD that
seems feasible when MCPRED is enabled.
Example: In our calibration test, we start with 64-ary.

3. Click the Equalink menu item in the Tasks pane and select Manual Non-Linear.... A pop-up
window appears.
Enter the starting values of the calibration parameters:

Equalink®
– AM/PM: 0.0
– AM/AM: 2.0
– Compression After Saturation: Weak
Click Manual Non-Linear to save the changes.
4. Go to the Modulator tab of the MCM7500 GUI. Scroll down to the Non-Linear Equalink Multi
Carrier Config Table and enable McPred-1.
22.2.2.7 Optimize Settings
1. Change the calibration parameters, drive level and MODCOD of the MCM7500 to find the
optimal C/ND value in the MDM6000.
Always disable MCPRED first when changing a calibration parameter.

Re-enable MCPRED after the change.
1. First, change the AM/PM value until you find the best C/ND value.
2. Next, change the AM/AM value (use values until you find the best C/ND value. With this
setting, change the modulator's output level and verify if C/ND improves. If the link margin
allows it, try a higher MODCOD. Refer to Calibration Configuration on page 304 to set the
MODCOD. When you have reached the highest MODCOD, change the output level and
AM/AM value again to find the optimum C/ND value.
3. Finally, change the compression value until you find the best C/ND value. With this setting,
change the modulator's output level and verify if C/ND improves.

Equalink®
At the end of these steps, you have the optimal calibration parameter values, the maximal
MODCOD and the optimal output level of the modulator, which results in the optimal drive level
of the transponder.
2. If the previously configured Maximum Modulation Order is not in line with the measured
maximum MODCOD, go to the Modulator tab of the MCM7500 GUI, scroll down to the Link
Optimization Configuration Table and set the Maximum Modulation Order in line with the
measured maximum MODCOD. Repeat the optimization steps.

Report Table: MCPRED ON in FGM.
Example: The following table gives the result of the optimization steps during our calibration test.
MCM7500 Demodulator MDM6000
AM/PM AM/AM Compr. Output MODCOD Carrier Input Link C/ND

(dBm) (dB)
0 2 weak -14 32A32/45 -36.1 0.75 12.67
1 0.49 12.38
-1 0.82 12.71
-2 0.72 12.63
-1 3 weak 0.63 12.55
1 0.96 12.89
0 0.74 12.55
1 weak -13 -25 1.35 13.26
32A11/15 0.97 13.28
32A7/9 0.12 13.32
-12 0.2 13.37
2 weak -12 32A7/9 0.28 13.47
3 0.24 13.44
2 medium -12 0.09 13.26
2 none -12 0.29 13.48
-11 0.24 13.41
-13 -0.03 13.17
-1 2 none -11.7 32A7/9 -34.6 0.31 13.5

Equalink®
In our example, the Maximum Modulation Order (64-ary) is not in line with the maximum MODCOD
(32APSK7/9). Therefore, the optimization steps need to be repeated with the Maximum Modulation
Order set to 32-ary.
Go to the Modulator tab of the MCM7500 GUI. Scroll down to the Link Optimization
Configuration Table and set the Maximum Modulation Order to 32-ary.
Take the optimum values of the previous optimization round as a starting point.
The following table gives the result of our optimization steps.
MCM7500 Demodulator MDM6000
AM/PM AM/AM Compr. Output MODCOD Carrier Input Link C/ND

(dBm) (dB)
-1 2 none -11.7 32A7/9 0.25 13.44
-1 3 0.11 13.3
1 0.33 13.51
0 NA
-1 1 none -11.2 13.5
-10.7 13.39
-12.2 13.43
-11.5 0.34 13.52
weak -11.5 0.34 13.52
-2 1 13.39
0 13.41

Equalink®
-1 2 weak 13.48
-1 1 weak -11.5 32A7/9 -34.5 0.34 13.52

Report Table: MCPRED ON in FGM.
The gain of enabling MCPRED is shown in the table:
MODCOD Efficiency Link Margin (dB) C/ND (dB)

(bps/Hz)
MCPRED OFF 32APSK32/45 3.271 0.72 12.54
MCPRED ON 32APSK7/9 3.555 0.34 13.52
Save the configuration of the MCM7500. Execute the following steps:

Example: Save the configuration as "<yyyymmdd>_mdm6000_MCPRED_ON".
Note down the demodulator performance of the MDM6000 in the report.

Report Table: Final Status MDM6000 in FGM => MDM6000.Rx.level_FGM2.
22.2.2.8 Restore Operational State
1. Load the MCM7500 configuration with optimized drive level and MCPRED OFF onto the
MCM7500. Execute the following steps:
Example: Load "<yyyymmdd>_dialog_MCPRED_OFF".
2. Send traffic to the test terminal.
3. Go to the FW Carrier Provisioning interface in the NMS GUI and set the Output level of the
forward carrier to the optimal level.
Example: Output level = -11.5 dBm.
4. Go to the Transponder Provisioning interface, enable Non Linear Predistortion and set the
calibration values to the optimal ones that you have measured.

Equalink®
Example:
– AM/PM = -1
– AM/AM = 1
– Max Allowed ModCod constellation = 32APSK
– Compression = Weak
5. Save the configuration of the MCM7500. This configuration can be used in case you need to
iterate over the process. Execute the following steps:
Example: Save the configuration as "<yyyymmdd>_dialog_MCPRED_ON".
6. Note down the performance of the demodulator of the test modem in the report.
Report Table: Status Dialog Test Modem at Optimized Drive Level in FGM.
In clear weather conditions, the measured RX MODCOD and EsNo value should be aligned with
the previous test results.
Lower performance is possible if:
– The operational symbol rate is significantly higher than the test symbol rate. For example,
470 Mbaud versus 133 Mbaud.
– The modem uses an Oxford chip at 64APSK instead of the FPGA of MDM6000. This can
result in a 1 dB difference of the EsNo value.
– Degradation due to the presence of an ACM margin.
7. Set the redundancy of the device pool to which the MCM7500 belongs to automatic.
Select REDCTL-0.Controller.bband_x in the surveyor tree of the NMS GUI. Select Device
redundancy in the card navigation pane or via the drop-down box at the top left corner of the
card pane. Scroll to the Device Pools section and edit the DevicePool Redundancy Selection
for the device pool where the MCM7500 belongs to. Select Automatic.

Equalink®
22.2.2.9 Enable ALC
Ask your satellite operator to enable ALC on the transponder and to set the transponder gain such
that the nominal RX carrier level on the test modem reaches the optimum carrier input level
(Term.Rx.level_ALC2.target) +- 0.2 dB.
Term.Rx.level_ALC2.target = Term.Rx.level_ALC1 + (MDM6000.Rx.level_FGM2 -
MDM6000.Rx.level_ALC1)
Note down the demodulator performance of the test modem in the report.
Report Table: Final Status Test Modem ALC2 ON => Term.Rx.level_ALC2.
If the transponder does not support ALC, the operation remains in Fixed Gain mode.
If the satellite operator cannot implement the optimum IBO, the closest operation point
is used and Optimize Settings on page 315 should be repeated.
22.2.2.10 Remove Calibration Setup
If you have installed an MDM6000 at the terminal side, remove the splitter and reconnect the outdoor
unit to the modem.
If you have installed the MDM6000 at the hub side, remove it from the RX path.
22.2.2.11 Expected MCPRED Improvement
The chart displays the efficiency gain variation due to TWTA linearization type and FEC.

Equalink®
22.2.2.12 How to Open the Web Interface
• MCM7500 on page 321

• Test Modem on page 322
• MDM6000 on page 323
MDM7500
To open the web interface of the MCM7500, execute the following steps:
1. Select the modulator via the surveyor tree of the NMS GUI. The modulator can be found under
the Physical Devices / DP-x. Click the MOD and then click WebInterface in the card navigation
pane or via the drop-down box at the top left corner of the card pane.

Equalink®
– User Name = expert
– Password = expertexpert
Test Modem
To open the web interface of the test modem, execute the following steps:
1. Browse to the management IP address of your modem.
– Type "?ilogin" behind the http://<management IP address>/cgi-bin/index URL.
– Password = Check with your modem provider.

Equalink®
MDM6000
To open the web interface of the MDM6000, execute the following steps:
1. Browse to the IP address of the MDM6000. Make sure that your PC has an IP address in the
same subnet as the MDM6000.

Equalink®
22.2.2.13 Where to Find the Measurements
• MCM7500 on page 324

• Test Modem on page 325
• MDM6000 on page 325
MCM7500
For more information about how to open the web interface, refer to How to Open the Web Interface
on page 321.
Parameter Location
Output Level (dBm) Open the MCM7500 GUI and login as expert. Go to the Modulator
tab and check the Output Level field in the Configuration Table.
MODCOD Open the MCM7500 GUI and login as expert. Go to the Tree View
tab and select Root / BBF Generator. Scroll down to the Single
Frame Mode Specification Configuration Table.
AM/PM Open the MCM7500 GUI and login as expert. Click the Equalink
menu item in the Tasks pane and select Manual Non-Linear.... A
AM/AM Open the MCM7500 GUI and login as expert. Click the Equalink
menu item in the Tasks pane and select Manual Non-Linear.... A

Equalink®
Compression After Open the MCM7500 GUI and login as expert. Click the Equalink
Saturation menu item in the Tasks pane and select Manual Non-Linear.... A
Test Modem
on page 321.
Parameter Location
MODCOD Open the GUI of the test modem and log in as expert. Go to the
Statistics / Demodulator page. The MODCOD used is highlighted in
the table.
Carrier Input Level (dBm) Open the GUI of the test modem. Go to the Terminal Status page
and check the first value of the Satellite / Demodulator field.
EsNo (dB) Open the GUI of the test modem. Go to the Terminal Status page
and check the second value of the Satellite / Demodulator field.
Efficiency (bps/Hz) See List of MODCODs on page 325.
MDM6000
on page 321.
Parameter Location
MODCOD Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
and scroll down to the ModCodStatistics section.
Carrier Input Level (dBm) Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
and scroll down to the Monitor section.
EsNo (dB) Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
and scroll down to the Monitor section.
Efficiency (bps/Hz) See List of MODCODs on page 325.
Link Margin (dB) Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
C/ND (dB) Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
C/D (dB) Open the MDM6000 GUI. Open the Detailed View of Demodulator 1
22.2.2.14 List of MODCODs
(The table is ordered by EsNo)

Equalink®
MODCOD EsNo (dB) Efficiency Roll-Off Efficiency Roll-Off

5% (bps/Hz) 10% (bps/Hz)
QPSK 1/4 -2/92 0.456 0.435
QPSK 13/45 -2.16 0.528 0.504
QPSK 1/3 -1.58 0.610 0.583
QPSK 2/5 -0.55 0.734 0.701
QPSK 9/20 0.06 0.827 0.789
QPSK 1/2 0.84 0.919 0.878
QPSK 11/20 1.31 1.012 0.966
QPSK 3/5 2.07 1.105 1.055
QPSK 2/3 2.92 1.229 1.173
QPSK 3/4 3.88 1.383 1.320
QPSK 4/5 4.51 1.476 1.409
QPSK 5/6 5.02 1.538 1.468
8PSK 3/5 5.36 1.657 1.581
8PSK 23/36 6.04 1.765 1.685
QPSK 8/9 6.15 1.642 1.568
QPSK 9/10 6.36 1.663 1.587
8PSK 2/3 6.40 1.843 1.760
8PSK 25/36 6.94 1.919 1.832
16APSK 26/45 7.27 2.121 2.025
8PSK 13/18 7.41 1.997 1.906
16APSK 3/5 7.71 2.204 2.103
8PSK 3/4 7.82 2.074 1.980
16APSK 28/45 8.00 2.286 2.182
16APSK 23/36 8.21 2.347 2.241
16APSK 2/3 8.82 2.452 2.341
16APSK 25/36 9.13 2.347 2.437
8PSK 5/6 9.24 2.307 2.202
16APSK 13/18 9.63 2.656 2.535

Equalink®
16APSK 3/4 10.09 2.758 2.633
16APSK 7/9 10.57 2.861 2.731
8PSK 8/9 10.62 2.463 2.351
8PSK 9/10 10.89 2.494 2.380
16APSK 4/5 10.89 2.943 2.810
16APSK 5/6 11.47 3.068 2.929
32APSK 32/45 11.69 3.271 3.122
16APSK 77/90 11.93 3.149 3.006
32APSK 11/15 12.10 3.374 3.220
32APSK 3/4 12.64 3.451 3.294
16APSK 8/9 12.86 3.276 3.127
32APSK 7/9 13.01 3.579 3.417
16APSK 9/10 13.10 3.317 3.166
32APSK 4/5 13.56 3.682 3.515
32APSK 5/6 14.12 3.839 3.664
64APSK 11/15 14.79 4.039 3.855
64APSK 7/9 15.43 4.285 4.090
32APSK 8/9 15.64 4.098 3.912
64APSK 4/5 15.88 4.408 4.208
32APSK 9/10 15.94 4.149 3.961
64APSK 5/6 16.50 4.595 4.386

Automated Uplink Power Control
23 Automated Uplink Power Control
23.1 About AUPC

Automatic Uplink Power Control or AUPC is an automated feature intended to maintain a constant
receive level over a satellite return uplink that suffers from terminal uplink fading, while respecting
the contractual BEPD limit of the satellite. Especially Ku/Ka band satellite links suffer from varying
amounts of loss due to weather and rain conditions on one or both ends.
AUPC can be enabled or disabled during terminal provisioning.
When AUPC is enabled and (rain) fade occurs at the uplink of the terminal, the controller in the hub
will detect the fade and will command the remote terminal to increase its transmit power to
compensate for this fade. When AUPC is disabled, the terminal uplink rain fade is not compensated.
Only terminals with a BUC or iLB2220 MUC and which use MRC, HRC or 4CPM in the
return link can use AUPC.
Combination with other ODUs will ignore the AUPC related signaling from the hub.
23.2 Configuring AUPC
23.2.1 Range Setting

AUPC is defined by the Range parameter.
The range parameter indicates the maximum increase of the terminal output power to keep the
same C/N0 (4CPM) and C0/N0 (HRC and MRC) at the hub. The parameter can have a value
between 0 dB and 20 dB and depends on the ODU type used (BUC or iLB2220 MUC).
For example, if this value is set to 6 dB, the controller will only compensate for a rain fade up to 6 dB.
The parameter is set during terminal provisioning, see How to Configure Service Settings on page
240.

23.2.2 Output Power for 1 dB Compression Setting

The Output Power for 1dB Compression value defines a maximum output power for AUPC:
• In clear sky conditions, the maximum output power equals this value minus the value specified by
the range parameter.
• In rainy conditions, the clear sky output power is increased to compensate for the rain fade but
limited by the Output Power for 1dB Compression value.
The parameter is set during terminal provisioning, see How to Configure Modem Settings on page
235.
The exact definition and hence the value of the parameter depends on the ODU type: BUC or
iLB2220 MUC.
23.2.2.1 BUC
In case of a BUC, the value should be set to the output power that a modem needs to transmit to the
BUC to make sure that the BUC transmits at the 1 dB compression output power. This value can be
derived from the BUC 1dB compression output power (P(1dB)Out, see figure below), the BUC gain
(G, see BUC data sheet) and cable loss (L, see cable specifications).

The Output Power for 1 dB Compression equals P(1dB)In + L or P(1dB)Out - G + 1 + L.

The table below gives an example.
Name Description Example Value
P(1dB)Out RF output at 1dB 39 dBm
G BUC Gain 65 dB
L Cable Loss 20 dB
Name Formula Example
Output power for 1dB Compression (P) P = P(1dB)Out - G + 1 + L -5 dBm
The clear sky transmit power of the modem equals to Output Power for 1dB Compression -
Range.
When rain fade occurs, this output power will increase to maximally the Output Power for 1dB
Compression value.
When configuring an MDM2510 using a BUC and the MF-TDMA return link technology, make sure
to set the Output Power Type to Modem Output Power. See How to Configure Service Settings
on page 240.

23.2.2.2 iLB2220 MUC
In case of an iLB2220 MUC, the value should be set to the maximum saturated output power of the
iLNB (with MUC). This output power is always saturated.
The clear sky transmit power of the ODU (iLB2220) is the Output Power for 1dB Compression -
Range.
When rain fade occurs, this output power will increase to maximally the Output Power for 1dB
Compression value.
When configuring an MDM2510 using an iLB2220 and the MF-TDMA return link technology, make
sure to set the Output Power Type to ODU Output Power. See How to Configure Service Settings
on page 240.

23.2.3 Power Control Mode

The Power Control Mode should be set to Nominal (using Line Up Settings). This is done during
terminal provisioning, see How to Configure Service Settings on page 240.

Certification
24 Certification
Poorly pointed terminal antennas can cause interference towards other services on adjacent
satellites and have poor link quality.
Such terminals will use more satellite bandwidth for the same IP data rate than terminals with well
pointed antennas. Therefore the OPEX of the network increases, as the satellite resources are
inefficiently used. It is therefore important that terminal antenna pointing quality is verified during or
after installation.
The Terminal Installation Certification System (TICS) is an optional add-on system to a Newtec
Dialog platform, measuring and identifying these poorly pointed terminals by means of a validation
process.
Certification is the outcome of the validation process which is typically executed during terminal
installation.
A verification is executed at a later stage (after installation) to verify if the certification of a terminal is
still valid. A failed verification can result in a change of the terminal certification state.
24.1 Background
If certification is enabled, then the Dialog hub instructs the TICS to do measurements. The TICS
needs to handle terminal certifications as soon as possible, because the user installing the terminal
is waiting for certification feedback. The installation certification process takes into account the
terminal position and satellite coverage for this measurement. For this reason the end-user is
requested to provide the position via the modem GUI.
Two types of measurements are possible:
1. Forward Link Es/No measurement: The goal of this measurement is to verify the pointing of the
terminal.The TICS queries the forward link Es/No value from the terminal. The terminal
measures its forward link Es/No and reports it back to the TICS. The TICS then compares this
to an expected target value. This value is based upon the link budget, the terminal position in
the satellite footprint as well as the outdoor unit used by the terminal.
2. Cross polarization discrimination measurement:
The primary goal of this measurement is to verify the cross-polarized alignment of a terminal in
case of linear polarization. It can also be used to detect cross polar radiation of
circular-polarized antennas (for example poor quality antennas).
A common problem when deploying linearly polarized transmission is cross polarization
interference generated by terminals of which the polarization angle of the LNB is not well
aligned. Poorly pointed terminal antennas cause interference towards other services on
adjacent satellites. In addition these terminals will have poor link quality.

Certification
The Cross Polar Discrimination (XPD) is defined as the ratio between the co-polarized EIRP
and the cross-polarized EIRP of a terminal. To determine the XPD, the measured values are
compared with the calibrated values of a reference terminal. The XPD should exceed a
minimum value required by the satellite operator.
The following figure shows the effect of the LNB angle offset on the XPD.

Certification
24.2 Procedure
It is advised to skip certification for terminals which were already operational before
TICS installation or activation. Otherwise a certification enabled Dialog system will
consider such terminals as non-certified, preventing the terminals to become
operational.
If you do want to certify terminals which were installed before activation of TICS, repeat
the terminal installation procedure or contact our customer support to update the TICS
database.
The certification feature can be set at multiple levels within the Dialog system.
Satellite Network
If you want to do certification of terminals in a satellite network, you must enable the certification
feature at the satellite network level. Certification is by default disabled on a satellite network.
To enable certification on a satellite network, execute the following steps:
1. Go to the provisioning interface of the satellite network. For more information about how to
access the interface, refer to How to Create a Satellite Network on page 19.
2. Click the Enable Certification button to activate certification on the satellite network.
3. Click Apply.
VNO
It is possible to disable certification at VNO level, even if certification is enabled on satellite network
level. This means that certification can be overruled for a VNO.
To disable certification on VNO level:
1. Go to the provisioning interface for the VNO. For more information about how to access the
interface, refer to How to Create a VNO on page 144.
2. Click on the VNO in the overview
3. Click the Certification Skipped button to overrule certification for the VNO.
4. Click Apply.
Terminal
It is possible to disable certification on terminal level even if certification is enabled at satellite
network level and VNO level. This means that certification can be overruled on a per terminal basis.
To disable certification on terminal level:
1. Go to the provisioning interface of the terminal. For more information about how to access the
interface, refer to Manage Terminal Provisioning on page 232.
2. Click on the terminal in the overview.
3. In the Modem tab, click the Certification Skipped button to overrule certification for the
terminal.
The certification state of a terminal is reflected in the Terminal Overview.

Certification
In this example, certification is enabled on the satellite network and for VNO1, but disabled for
VNO2.
Terminal 1, 3 and 4 have certification enabled. Terminal 1 and 3 were successfully certified, terminal
4 is not yet certified. Terminal 2 has certification disabled and skips the certification imposed by the
satellite network. Terminal 5 has certification enabled but will skip certification because it belongs to
VNO2.
You cannot enable certification at a lower level when it is disabled at a higher level.
For example, when certification of the satellite network is disabled, the certification
setting for a VNO or terminal does not matter; certification will always be skipped.

Multicast
25 Multicast
The Dialog platform supports multicast traffic.
A Dialog hub module, except the baseband hub module HUB7208, has a pair of redundant multicast
interfaces. The multicast traffic is sent on dedicated multicast input VLANs. See
How to Create Multicast VLANs on page 337.
For more information about the redundant multicast interfaces on the hub module, refer
to the Newtec Dialog Installation Guide for the corresponding hub module.
The Dialog system supports two multicast scenarios:

• One or more hosts connected to the LAN of the terminal receive the multicast. The source of the
multicast is connected to the hub. The multicast stream is flowing in the forward direction. This is
called hub multicast circuit. This scenario is described in How to Create Hub Multicast on page
340.
• One or more hosts connected to the LAN of the terminal are the source of the multicast. The
receivers of the multicast are connected to the hub. The multicast stream is flowing in the return
direction. This is called contribution or a terminal multicast circuit. This is described in
How to Create Terminal Multicast on page 345.
25.1 How to Create Multicast VLANs

First, the multicast VLANs have to be created.
You can create only one hub VLAN and one terminal VLAN per satellite network.
To create a multicast VLAN, execute the following steps:


Multicast
4. Select the beam identifier and Satellite Network. Click Resource Provisioning and then click
Multicast Vlan.
6. Click + Create Multicast VLAN.

Multicast

– Type: Use the slider to indicate if the VLAN is used for the hub multicast circuits or the
terminal multicast circuits.
domain name is the HNO domain name. The arbitrary name should be unique within the
domain and only support alphanumerical characters, underscores and hyphens. Blank
– VLAN ID: Enter a VLAN identifier for the hub or terminal multicast VLAN. The same VLAN
ID must be used on your edge routers.
– IP Address: This parameter is only available when creating a hub multicast VLAN. Enter
the IPv4 address that the hub should use on the specified multicast uplink VLAN. This
needed to forward the multicast packets.
– Prefix length: This parameter is only available when creating a hub multicast VLAN. This
is the size of the multicast uplink network. The number is the count of leading 1 bits in the
– Click to create the multicast VLAN or click to discard the settings.
Click in the Actions column to edit the multicast VLAN.
Click in the Actions column to delete the multicast VLAN.

Multicast
25.2 How to Create Hub Multicast

Hub multicast or distribution implies that a source connected to the Dialog hub streams content
which can be received by one or more hosts located on the LAN of one or more remote modems.
To enable hub multicast, you should:

1. Create the hub multicast circuit.
2. Configure the modem to receive the hub multicast stream.
Create the Hub Multicast

To create the hub multicast, execute the following steps:
1. Make sure a Hub Multicast VLAN is created. Refer to How to Create Multicast VLANs on page
337.

Multicast
5. Click Hub Multicast Provisioning in the surveyor tree or in the visual overview.
7. Click + Create New Forward Hub Multicast.
multicast based on the settings of an existing one.
The following window appears.

Multicast

– Multicast Address: Enter a Multicast IP address
The allowed multicast range is 224.0.0.0 – 239.255.255.255 except for the following
addresses:
• 224.0.0.1
• 224.0.1.1
• 239.1.0.1
• 239.1.0.2
• 239.192.2.1
• 239.255.255.100
224.0.0.0/24 can be used in static multicast mode. It cannot be used with

dynamic IGMP on the terminal.
– CIR: Enter the Committed Information Rate or CIR for this multicast circuit. CIR specifies
the data rate, which is always granted during data rate distribution as long as the total
available data rate is not exceeded.
– Packet Shaping Timeout: This is the maximum time that a packet stays in the multicast
shaping queue before it is dropped.
– Satellite Networks: Select one or more satellite networks on which this hub multicast
circuit will be used.
– ModCod: When you select a satellite network, this parameter becomes available. Select
the MODCOD that will be applied for the multicast traffic from the drop-down list. The list of
available MODCODs is determined via the Forward Link on page 49.
messages.

Multicast
Click on the hub multicast in the overview to edit the parameters.
Click in the Actions column to delete the hub multicast.
Configure the Remote Terminal

To configure the remote terminal, execute the following steps:
1. Browse to the local modem's GUI. There are two ways to open the GUI:
– Via the NMS. Open the Terminal Provisioning interface (see
How to Open the Terminal Provisioning Web Interface) and click in the Actions
column of the terminal that you want to configure.
– Via local access. Connect your computer to the LAN port of the modem and make sure your
computer is set to DHCP. Enter the modem's IP address in the address bar of the browser.
The default address is 192.168.1.1.
2. Select the Multicast menu item at the left side of the screen.

Multicast
3. Set the Multicast Mode:

– Static: Enter the multicast IP address that is configured in the Forward Hub Multicast on
page 342 circuit. In this mode, the multicast data of the configured addresses is forwarded
to the modem LAN interface.
You can add up to 10 multicast IP addresses.
– Dynamic IGMP: In this mode, a JOIN message is initiated by the receivers on the modem
LAN.

Multicast
25.3 How to Create Terminal Multicast

Terminal multicast or contribution implies that one or more hosts behind the modem, streams
content which is received by receivers connected to the hub.
To create terminal multicast circuit, execute the following steps:

1. Make sure a Terminal Multicast VLAN is created. Refer to How to Create Multicast VLANs on
page 337.
2. Go to the Terminal Provisioning interface and select or create a terminal. Refer to
3. Click the Layer 3 tab.
4. Click + Add in the Return Multicast section.

Multicast

– Name: This is an arbitrary name to identify the terminal multicast circuit. The arbitrary name
– IP Address: This is the multicast IP address to route terminal LAN ingress traffic into this
multicast circuit.
– QoS Class: This is the QoS class to which the terminal multicast circuit traffic should be
mapped.
data rate distribution as long as the total available data rate is not exceeded. This
parameter is not available for the best-effort QoS class.
– PIR: PIR or Peak Information Rate defines the upper data rate limit. This parameter is not
available for the real-time QoS class.
– Weight: This is the weight assigned to the multicast circuit. The weight is an integer value
between 1 and 1000 and is used to define the Total Weight, which equals PIR * Weight.
The total weight is used as a ratio mechanism for "fair" distribution of additional capacity
after CIR is applied. This parameter is not available for the real-time QoS class.
– Packet Size: This is the average IP packet size used on this circuit.. This value is used by
the system to allocate extra bandwidth for encapsulation overhead.
– ModCod: This parameter is only available when DVB-S2 or S2 Extensions is used as
return technology and ACM is disabled. It defines the MODCOD used for the traffic of the
multicast circuit.
– ACM Enabled: This parameter is only available when DVB-S2 or S2 Extensions is used
as return technology and ACM is enabled for the S2 carrier. Click this check box to enable
ACM for the multicast circuit as well. The above ModCod parameter disappears.
– Allocation Type: This parameter is only available when 4CPM MF-TDMA or HRC Mx-DMA
is used as return technology, and is only applicable for the real-time 1 and real-time 2 QoS

Multicast
classes. The allocation type defines how the satellite capacity is assigned. For more
information, refer to Allocation Type on page 200. The following types exist:
• Dynamic Full Rate: The terminal receives all of the configured real-time capacity as
soon as any capacity is requested.
• Dynamic Ingress Rate: The terminal receives only the amount of capacity it requests
(from the total configured capacity).
• Static: The terminal receives the configured capacity (even if not requested).
– HRC Mx-DMA Request Margin: When the allocation type is set to DIR you can specify a
request margin, which is considered as an extra amount of bandwidth a terminal always
receives, on top of the requested amount. For more information, refer to Allocation Type on
page 200.
– Hub Forwarding: This is by default enabled for all return technologies. For DVB-S2(Ext) it
is possible to disable the forwarding of the multicast traffic on the uplink of the hub.
For NPCI Dialog systems, it is not possible for a hub to forward multicast traffic
contributed by a terminal.
– Click Confirm to create the terminal multicast circuit or click Cancel to discard the settings.
You can add up to four terminal multicast circuits.
Click in the Actions column to delete the forward link.

GTP Optimization for Mobile Backhauling
26 GTP Optimization for Mobile Backhauling

Dialog offers a satellite connection between the Radio Access Network and the Mobile Core Network
in mobile backhaul applications, as an alternative to point-to-point radio or terrestrial connections.
For that, a GTP-U tunnel is set up. Dialog allows to optimize the GTP traffic by accelerating the TCP
connection within.
For more information about GTP Acceleration, refer to the Newtec Dialog Functional
Description.
In order to successfully optimize GTP traffic, you must carefully configure different resources of the
system.
The resources that are involved are listed below and described in the next chapters.
1. Create Mobile Backhaul Network on page 348
2. Create Service Profile on page 349
3. Define QoS Plan on page 351
4. Create Classification Profile on page 353
5. Provision Terminals on page 355
26.1 Create Mobile Backhaul Network

When creating the network, make sure to enable the Mobile Backhaul Network parameter. Only
when a network is marked as a mobile backhaul network, the system will identify the traffic as
GTP-U traffic.
GTP-U is implemented on top of UDP. The UDP destination port is by default set to 2152 but can
be configured otherwise. TelliNet will identify UDP packets with a matching destination port as
GTP-U packets and will inspect the GTP header and payload.
The mobile backhaul network can be either a layer 2 point-to-point virtual connection or a layer 3
network.
Layer 2 Network
Enable the Mobile Backhaul Network setting when creating the layer 2 virtual connection as part of
the terminal provisioning. For more information, refer to .How to Create a Terminal on page 234.

Layer 3 Network
Enable the Mobile Backhaul Network setting when creating a layer 3 network as part of the network
resources provisioning. Set the Service Label to a name that easily identifies the network that
transports GTP-U traffic. In the example below, the service label is set to GTP. For more
information, refer to How to Create Layer 3 Network Resources.
26.2 Create Service Profile

The GTP optimization techniques that should be applied to the traffic are set in the Service Profile:

1. Open the Service Profile Web Interface. For more information, refer to
2. QoS information on the Class Based Service Profile must be set in the forward and return:
In the example above, BE class is set with a higher PIR than the real capacity, as BE packets
can be dropped. RT-2 class is typically used for VoIP, therefore it must have the same values in
the forward and return links.
3. Open the Advanced Settings Profile in the Forward QoS Class Settings and the Return QoS
Class Settings.

4. Enable GTP acceleration for the voice traffic.
26.3 Define QoS Plan

The QoS plan should be designed taking into account the parent-child dependencies.

The following procedure is described for the forward link. The sequence is analog for the return link.
1. Open the Forward QoS Plan. For more information, refer to
How to Open the Forward Resources Web Interface on page 42.
2. Create a dedicated class-based forward pool. For more information, refer to
How to Create a Dedicated Class Based Forward Pool on page 65.
– The CIR value of the QoS pool must serve the CIR value of the QoS classes. In the
example, 13 Mbps
– Avoid CIR overbooking.
3. Under the dedicated class-based pool, create a child dedicated pool

– The QoS settings in the service profile must correspond with the QoS information in the
QoS plan. For more information, refer to Create Service Profile

– The dedicated total QoS and shaping information of the pool must correspond with the
available CIR, which must in turn be sufficient for the CIR for both the dedicated and the
shared profiles.
– Avoid CIR overbooking.
26.4 Create Classification Profile

Dialog classifies packets based on the DSCP value.
1. Open the Classification Profile interface. For more information, refer to
How to Open the Classification Profiles Web Interface on page 191.
2. Control traffic must be prioritized over mobile data traffic. The first rule in the Classification
Profile used for mobile backhaul should therefore map to RT1 class the packets with IP protocol
132 – SCTP (Stream Control Transmission Protocol).

3. Voice packets (typically with DSCP 46) should get the next priority and should therefore be
mapped to the RT2 traffic class.

26.5 Provision Terminals

To provision a terminal to use in a mobile backhaul network, Follow these steps:
1. Open the Terminal Provisioning interface. For more information, refer to How to Open the
Terminal Provisioning Web Interface.
2. In the Service tab, select the service profile created for the mobile backhaul network in the steps
before. For more information, refer to Create Service Profile on page 349.
3. Set up the Layer 3 network.
4. Set up the Layer 2 network.
Click the Mobile Backhaul Network button to mark the virtual connection as a mobile backhaul
network. When enabled, the layer 2 network is considered to carry GTP traffic and traffic
optimization inside the GTP tunnel can be performed.
Specify the GTP V1 UDP Port. The default value is 2152.

Appendix
27 Appendix
The guide has been written from the perspective of the HNO user with Administrator role.
As VNO user, the access to the Dialog platform is limited. The read and write permissions of the
VNO user depend on the user role. Four roles exist: Administrator, Operator, Observer and
Certifier.
The following table indicates the permissions for the Administrator, Operator and Observer roles for
each action described in this guide.
It is not possible to perform any action on the GUI with a Certifier role.
Certifiers are only allowed to do REST API calls to certify and uncertify. Users with
certifier role are specifically designed for other components, such as like TICS.
Action VNO Administrator VNO Operator VNO Observer
Open the Satellite Resources Read Read Read

Web
• Create a Beam x x x
• Create a Satellite Network Read Read Read
Open the Forward Resources x x x

Web Interface
Open the Forward QoS Plan Read Read Read

Interface
Open the Return Resources x x x

Web Interface
Open the Return Link x x x

Frequency Plan
Open the Return QoS Plan Read Read Read

Interface
Open the VNO Web Interface x x x
Open the User Management Read and Write x x

Web Interface
• Create a New User Read and Write Only allowed to Only allowed to
change own change own
password password
Open the Network Resources x x x

Web Interface
• Create Layer 3 Network x x x

Resources
• Create a Subnet x x x

Appendix
• Create IPv4 Pools x x x
• Create IPv6 Pools x x x
• Create Hub Termination Point Read Read Read
• Create L2 Network Resources x x x
Open the Classification Read and Write Read an Write Read

Profiles Web Interface
• Create a Classification Profile Read and Write Read and Write x
Open the Service Profiles Web Read and Write Read and Write Read
Interface
• Create a Transport Based Read and Write Read and Write x

Service Profile
• Create a Class Based Service Read and Write Read and Write x
Profile
Open the Attachment Profiles Read and Write Read and Write Read
Web Interface
• Create an Attachment Profile Read and Write Read and Write x
• Create Batch Actions Read and Write Read and Write x
Open the Firewall Profiles Web Read and Write Read and Write Read
Interface
• Create a Firewall Profile Read and Write Read and Write x
Open the BGP Profiles Web Read and Write Read and Write Read
Interface
• Create a BGP Profile Read and Write Read and Write x
Open the Terminal Read and Write Read and Write Read
Provisioning Web Interface
• Create a Terminal Read and Write Read and Write x
Open the Software Multicast x x x

Web Interface
For more information about creating VNO users, refer to VNO and User Management on page 143.

Acronyms
28 Acronyms
Acronym Definition
AC Alternating Current
ACI Adjacent Channel Interference
ACM Adaptive Coding Modulation
AM Amplitude Modulation
API Application Programming Interface
APSK Amplitude and Phase-Shift Keying
ARL Adaptive Return Link
ARP Address Resolution Protocol
ASCII American Standard Code For Information Interchange
ASI Asynchronous Serial Interface
ASW Access Switch
AUPC Automated Uplink Power Control
AZ Azimuth
B2B Business-To-Business
BDM Burst Demodulator
BEPD Bandwidth Equivalent Power Density
BER Bit Error Rate
BSC Bootstrapper/System Configurator
BUC Block Up Converter
BW Bandwidth
C/N Carrier To Noise Ratio
CCI Co-Channel Interference
CCM Constant Coding and Modulation
CE Communications-Electronics
CIDR Classless Interdomain Routing (IETF)
CIR Committed Information Rate
CMS Configuration Management Server
CPE Customer Premise Equipment
CPM Continuous Phase Modulation
CPMCTL CPM Controller

Acronyms
Acronym Definition
CPU Central Processing Unit
CRC Cyclic Redundancy Check
CSC Common Signaling Channel
CSE Controller Shaper Encapsulator
dBm/Hz Decibels (reference to 1 milliwatt) per Hertz
DCP Decapsulator
DCSP Digital Control Signal Processor
DEM Demarcation Service
DHCP Dynamic Host Configuration Protocol
DM Distortion Margin
DNS Domestic Name System
DSCP Differentiated Services Code Point
DSW Distribution Switch
DVB Digital Video Broadcasting
DVB-S2 Digital Video Broadcasting - Satellite - version 2
EIRP Equivalent Isotropic Radiated Power
Es/No Energy per symbol / Noise spectral density
GUI Graphical User Interface
HNO Hub Network Operator
HRC™ High Resolution Coding
HSRP Hot Standby Router Protocol
IBO Input Back Off
ICMP Internet Control Message Protocol (IETF)
ID Identifier
IF Intermediate Frequency
IGMP Internet Group Management Protocol
IP Internet Protocol
IPsec Internet Protocol Security
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISI Input Stream Identifier
KHz Kilohertz
KPI Key Performance Indicator

Acronyms
Acronym Definition
LAN Local Area Network
LNA Low-Noise Amplifier
LNB Low Noise Block Downconverter
MAC Media Access Control
MCD Multi Carrier Demodulator
MF-TDMA Multi Frequency-Time Division Multiple Access
MHz Megahertz
ML Modulation Loss
MODCOD Modulation and Coding Combination
MPE Multi Protocol Encapsulation
MRC Multi Resolution Coding
MTU Maximum Transmission Unit (TCP)
MUX Multiplexer
Mx-DMA™ Cross-Dimensional Multiple Access™
N/A Not Applicable
NIT Network Information Table
NSSA Not So Stubby Area
NxtGen Next Generation Cross-Dimensional Multiple Access™

Mx-DMA™
ODU Outdoor Unit
OSPF Open Shortest Path First
PEB Power Equivalent Bandwidth
PER Packet Error Rate
PID Packet Identifier
PIR Peak Information Rate
PSD Power Spectral Density
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RCG Return Capacity Group
RCP Return Carrier Pool
RCS Return Channel over Satellite
REST Representational State Transfer
RF Radio Frequency

Acronyms
Acronym Definition
RMT RCS Map Table
RN Reference Noise
RSTP Rapid Spanning Tree Protocol
RTP Realtime Transport Protocol
RX Receive
SatNet Satellite Network
SCPC Single Channel Per Carrier
SNR Signal to Noise Ratio
STP Spanning Tree Protocol
TBTP Terminal Burst Time Plan
TCP Transmission Control Protocol
ThiMM Thin Margin Manager
THR Reference Threshold
TICS Terminal Installation Certification Server
TX Transmit
UDP User Data Protocol
URL Uniform Resource Locator
VLAN Virtual Local Area Network
VL-SNR Very Low Signal to Noise Ratio
VNO Virtual Network Operator
VoIP Voice over IP
VPN Virtual Private Network
VRF Virtual Routing Forwarding
VRRP Virtual Router Redundancy Protocol
VSAT Very Small Aperture Terminal
XPD Cross Polarization Discrimination

ST Engineering iDirect (Europe)
Laarstraat 5
9100 Sint-Niklaas Belgium
+32 3 780 6500
wwww.idirect.net

Dialog R2.4.1 ConfigurationUserGuide v1.3

Uploaded by

Document Information

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

Dialog R2.4.1 ConfigurationUserGuide v1.3

Uploaded by

Copyright:

Available Formats

Configuration User Guide

ST Engineering iDirect is a global leader in satellite communications (satcom) providing technology

Company Website: www.idirect.net | Main Phone: +32 3 780 6500

1 About This Guide ............................................................................................ 1

2 What is Newtec Dialog® ................................................................................. 3

3 How to Access the NMS GUI .......................................................................... 8

5 Manage General Satellite Resources .......................................................... 11

6 Manage Forward Link Resources ................................................................ 25

Configuration User Guide v1.3 3/361

6.12 How to Create a Dedicated Class Based Forward Pool ...................................................................... 65

7 Manage Return Link Resources .................................................................. 73

Configuration User Guide v1.3 4/361

7.17.1 Activate HRC Ulogon .................................................................................................................. 136

8 VNO and User Management ....................................................................... 143

9 Manage Network Resources ...................................................................... 151

10 Manage Classification Profiles ................................................................ 188

Configuration User Guide v1.3 5/361

10.1 Background Information ................................................................................................................... 188

11 Manage Service Profiles ........................................................................... 198

12 Manage Attachment Profiles .................................................................... 213

13 Manage Firewall Profiles .......................................................................... 221

14 Manage BGP Profiles ................................................................................ 225

15 Manage Remote Configuration Profile .................................................... 229

16 Manage Terminal Provisioning ................................................................ 232

Configuration User Guide v1.3 6/361

16.2.3 How to Configure Mobility Settings ............................................................................................. 243

17 Manage Auto Attachment Prototype ....................................................... 266

18 Manage Inventory ...................................................................................... 269

19 Updating Terminal Software ..................................................................... 271

20 Terminal Line Up ....................................................................................... 276

21 Return Link Calibration ............................................................................. 282

22 Equalink® ................................................................................................... 286

Configuration User Guide v1.3 7/361

22.2.2.1 Calibration Setup ..................................................................................................................... 302

23 Automated Uplink Power Control ............................................................ 328

24 Certification ............................................................................................... 333

25 Multicast ..................................................................................................... 337

26 GTP Optimization for Mobile Backhauling .............................................. 348

Configuration User Guide v1.3 8/361

27 Appendix .................................................................................................... 356

28 Acronyms ................................................................................................... 358

Configuration User Guide v1.3 9/361

1 About This Guide

1.1 Revision History

Version Date Reason of new version

1.0 December, 2020 Initial version of this release.

1.3 September 2021 Clarification on Candidate Forward Carrier feature added.

1.2 Cautions and Symbols

Configuration User Guide v1.3 1/361

A reference message is used to direct to a location in a document with related document

Configuration User Guide v1.3 2/361

2 What is Newtec Dialog®

Configuration User Guide v1.3 3/361

Dialog R2.4.1 supports all modem types.

Configuration User Guide v1.3 4/361

Configuration User Guide v1.3 5/361

Configuration User Guide v1.3 6/361

Configuration User Guide v1.3 7/361

3 How to Access the NMS GUI

Use Internet Explorer 10 or higher.

4. The NMS web interface has the following sections:

Configuration User Guide v1.3 8/361

Configuration User Guide v1.3 9/361

2. Enter the Key and Value.