Adaptive Inbound Coding

Adaptive Inbound Coding
January 2011
Document No. DC-002265(A)
Gilat Satellite Networks Ltd.
This document contains information proprietary to Gilat Satellite Networks Ltd. and may not be
reproduced in whole or in part without the express written consent of Gilat Satellite Networks Ltd. The
disclosure by Gilat Satellite Networks Ltd. of information contained herein does not constitute any
license or authorization to use or disclose the information, ideas or concepts presented. The contents of
this document are subject to change without prior notice.
Contents
1. Introduction ................................................................................................................... 1
1.1 Document Contents ................................................................................................ 1
1.2 Overview and History .............................................................................................. 1
1.3 General .................................................................................................................. 2
1.4 Feature Description ................................................................................................ 2
1.5 Specifications ......................................................................................................... 3
1.6 Limitations .............................................................................................................. 3
1.7 Network Downtime .................................................................................................. 5
2. Configuring Adaptive Inbound ..................................................................................... 6

2.1 Prerequisites .......................................................................................................... 6
2.2 Verifying the License .............................................................................................. 6
2.2.1 Verifying License Installation ........................................................................ 6
2.3 Verifying the Hub Receiver Card Hardware Version ................................................ 7
2.4 Enabling Adaptive Inbound ..................................................................................... 7
2.4.1 Enabling License .......................................................................................... 8
2.4.2 Configuring HSP .......................................................................................... 8
2.4.3 Configuring Access Template ......................................................................10
2.4.4 Resetting VSATs .........................................................................................13
3. Example Scenarios ......................................................................................................15

3.1 Upgrading Existing Network ...................................................................................15
3.2 Collecting Inbound Es/N0 Measurements without Using Adaptive Inbound Coding 15
4. Appendix A - Telemetries ............................................................................................16

4.1 Fade Statistics / Fade Statistics + Reset ................................................................17
4.2 Fade Telemetry .....................................................................................................19

January, 2011 i
Proprietary and Confidential
Figures
Figure 1: Outbound vs Inbound Signal Quality Dynamics ............................................... 2

Figure 2: License Report ................................................................................................ 6
Figure 3: Hardware Version Number .............................................................................. 7
Figure 4: Adaptive Inbound License Configuration ......................................................... 8
Figure 5: Inbound Bands Instances ................................................................................ 9
Figure 6: Fade Mode Selection ...................................................................................... 9
Figure 7: HSP Context Menu - Reboot Command .........................................................10
Figure 8: Access Template Selection ............................................................................11
Figure 9: Adaptive Inbound License Activation ..............................................................11
Figure 10: Inbound Configuration Pane .........................................................................12
Figure 12: VSATs Reset Confirmation Request .............................................................12
Figure 13: Resetting Multiple VSATs .............................................................................14
Figure 14: VSAT Telemetries Expanded Tree View (Partial View) .................................16
Figure 15: Fade Statistics Parameters (Partial View) ......................................................17
Figure 16: Fade Statistics Parameters – General pane ..................................................17
Figure 17: Fade Statistics – RA / CRA / GA, DA and Star Voice Panels (Partial View) .. 18
Figure 18: VSAT Fade Telemetry – Inbound EsNo Histogram ........................................19

January, 2011 ii
1. Introduction
This document provides a brief description of the Adaptive Inbound feature and
describes in detail its configuration.
CAUTION
This document is intended for Gilat Technical Support personnel.
Incorrect implementation of the procedures described in this document
may damage the system.
1.1 Document Contents
This document includes the following sections:
Introduction
Configuring Adaptive Inbound
Example Scenarios
Appendix A - Telemetries
1.2 Overview and History
Adaptive link techniques dynamically change the transmission characteristics

(power, rate, modulation, FEC, etc) in order to mitigate the signal degradation caused
by changing link conditions (attenuation / fade, echo, etc).
Historically, satellite networks link-budget used to take into account safety margins
for rain fade occurrences. This resulted in increased ODU power requirements or
larger antenna sizes – all aimed to mitigate the worst case scenario and provide site
availability throughout the year.
Adaptive transmission techniques are used to keep the same uptime without the extra
equipment costs. Instead, the site suffers temporary service degradation (bandwidth
drop) when its link is affected by rain fade or other transient interference.
NOTE
The Adaptive Inbound solution increases the site connectivity up-time,
but does not ensure the site/customer service level agreement (SLA).
This means that during rain fade, the SkyEdge system does not
guarantee to provide the VSAT throughput of MIR or even its CIR, and
the IP connectivity will be retained in a somewhat degraded manner.

January, 2011 1
1.3 General
The SkyEdge Adaptive Inbound solution is based on a baseline (reference) power

reading from the hub: when the VSAT does not generate Inbound traffic, its signal
strength is assessed indirectly - by measuring the received Outbound signal strength
relative to the last explicit power reading received, and without feedback from the
hub based on continuous VSAT transmissions.
This mechanism is illustrated in Figure 1.
A VSAT transmits a burst to the hub.
The hub provides a signal strength reading regarding this transmission.
The VSAT remembers this signal strength reading and starts monitoring changes
over the Outbound.
The assumption is that changes in the signal strength of the received Outbound
signal cause comparable changes in the signal strength of the Inbound signal.
Figure 1: Outbound vs Inbound Signal Quality Dynamics
The VSAT uses more than one explicit Inbound Es/N0 reading from the hub to filter
out false low Es/N0 readings caused by RA collisions.
1.4 Feature Description
The SkyEdge Adaptive Inbound Coding solution is based on a semi-closed power

loop with the hub. This power loop provides the VSAT with information regarding
its received signal quality at the hub.

January, 2011 2
The VSAT uses this information as a baseline and monitors changes in its Outbound
reception quality. As it is assumed that both Outbound and Inbound are affected by
rain fade, the Outbound quality changes allow the VSAT to estimate its Inbound
signal quality, even if the VSAT is currently idle.
The transmission adjustment is performed by switching into a highly robust code-rate

(FEC) when rain fade conditions are detected. Although this FEC is not very
efficient, it still manages to maintain the VSAT-to-hub connectivity while causing a
temporary degradation of the VSAT throughput.
When the rain fade conditions clear up, the VSAT switches back to the regular link
FEC (strong-turbo coding). Other types of coding are not supported.
1.5 Specifications
Strong-turbo minimal received Es/N0: 6.5 dB.
Robust-turbo minimal received Es/N0: 3 dB.
Nominal Es/N0 gain by change of FEC (or, acceptable rain fade): 3.5 dB.
Time-slot duration and symbol-rate are kept the same as in clear sky.
All Access schemes are usable both in clear sky and rain fade; multiple rates are
supported.
Network-wise, no additional resources are required to mitigate rain fade. This is

due to the fact that VSATs burst-rate in fade mode does not increase, hence
network space segment requirements are not affected, and rain fade conditions
affect the performance of specific VSATs only.
This assumption is based on a limited amount of VSATs concurrently suffering

from rain fade (under 5% of the sites) hence their overall effect on network
space-segment is negligible.
Adaptive Inbound Coding mode is set per Inbound band and per VSAT’s Access
template. Other Inbound bands are not affected.
1.6 Limitations
Adaptive Inbound Coding solution is acceptable only for applications that can
tolerate link degradation. Most IP applications fit into this requirement.
Enabling/disabling Adaptive Inbound Coding mode per specific VSAT is not

supported.

January, 2011 3
Adaptive Inbound Coding cannot run properly without using an uplink power
control (ULPC) mechanism for the Outbound hub transmission. ULPC ensures
proper rain fade estimation by restricting the changes to the link conditions to the
satellite-to-VSAT segment only.
Adaptive Inbound Coding does not support mesh links, because VSATs running
Adaptive Inbound Coding drop mesh links as soon as the links stop running due
to rain fade.
Adaptive Inbound Coding requires symbol-rates of 153.6 Ksps or higher. Access

modes configured with lower symbol rates will not enter fade mode or switch to
FEC. Low symbol rates are usually less susceptible to rain fade. While in fade
mode (robust-turbo FEC), the VSAT MI is limited to 662 bytes (even if the time-
slot duration is longer).
Adaptive Inbound Coding is only applicable if the clear sky MI is at least 164
bytes when using strong-turbo coding, or 197 bytes when using fast-turbo
coding.
Adaptive Inbound Coding is currently incompatible with the Multi-Line VSAT

configuration, because these sites always assume clear sky conditions. These
sites cannot run Adaptive Inbound coding, and ignore any Adaptive Inbound
configuration.
Adaptive Inbound Coding is incompatible with SkyAbis sites because changing

link bandwidths conflicts with the Abis application.
Adaptive Inbound Coding is incompatible with Cisco Network Module VSAT

operation because these modules ignore the Adaptive Inbound settings.
Access detail records (ADRs) disregard rain fade situations and count
transmitted/allocated slots based on clear sky MI.
During rain fade, the VSAT burst usable payload (MI) is reduced in proportion to
the stronger FEC in use. As a result, while in rain fade, the VSAT throughput is
reduced to about 1/3 of the clear sky usable bitrate.
While in rain fade, a VSAT may not be able to meet its SLA (CIR, full MIR even
if the network is not overloaded, etc.). During rain fade the VSAT bitrate
decreases, but its transmission burst-rate does not increase as compensation.
While in rain fade, telephony and VoIP sessions require additional slot allocation
to maintain the session. The allocation adjustment is performed on the fly.

January, 2011 4
1.7 Network Downtime
Network downtime is limited to the time it takes for the HSP to reboot.
The VSAT reset time must also be taken into account.

January, 2011 5
2. Configuring Adaptive Inbound
2.1 Prerequisites
Before configuring the feature, verify that:
The Receiver Cards installed at the hub are P/N 434730-15.
The Receiver Cards have the new PALS version (for more information, refer to
the Reprogramming HBR Receiver Cards guide, DC-4201-10)
The Adaptive Inbound license is installed (see Section 2.2)
The ULPC mechanism is enabled on the hub transmission chain
HSP and VSATs have been upgraded to SkyEdge version 5.0 or higher
2.2 Verifying the License
Adaptive Inbound requires a separate license to be obtained from Gilat, installed and
enabled in the system.
2.2.1 Verifying License Installation
To verify that the Adaptive Inbound license is installed:
1. In the NMS Browser, click Administration→License Report.
Result: The License Report window is displayed.
Figure 2: License Report
2. Verify that the ADAPTIVE INBOUND license (Code: SF004610) is installed in

the system.

January, 2011 6
2.3 Verifying the Hub Receiver Card Hardware Version
To verify the hub receiver card hardware version:
1. Log in to the HSP console.
Result: The HSP console prompt is displayed.
2. Type tele receiver X cage Y, and press Enter.
NOTE
X is the Receiver card index number: 0, 2, 4, etc. (each card consists of
two receivers);
Y is the Receiver cage index number: 1, 2, 3, etc.
Result: The hardware version number is displayed.
Figure 3: Hardware Version Number
3. Verify that Hardware version: 36 is displayed in the Hardware version line.
4. Repeat the procedure for every card on the system.
2.4 Enabling Adaptive Inbound
The Adaptive Inbound configuration procedure includes the following sections:
Enabling License
Configuring HSP
Configuring Access Template
Resetting VSATs

January, 2011 7
2.4.1 Enabling License
To enable the Adaptive Inbound license:
1. In the NMS Browser Hub View window, double-click the HSP icon.
Result: The HSP Configuration window is displayed.
2. In the tree view, select License Management.
Result: The Adaptive Inbound License Configuration field is displayed.
3. From the Adaptive Inbound drop-down list, select Activate.
Figure 4: Adaptive Inbound License Configuration
4. Click Save.
2.4.2 Configuring HSP
This section describes how to configure the Adaptive Inbound settings for the
Inbound band. If more than one Inbound band is planned to use the Adaptive
Inbound feature, this procedure should be performed for each Inbound band
separately.
To configure the Adaptive Inbound settings for the relevant Inbound band:
1. In the tree view of the HSP Configuration window, expand Inbound, and select
Inbound Bands Instances.
Result: The Inbound Bands Instances table is displayed.

January, 2011 8
Figure 5: Inbound Bands Instances
2. In the Inbound Instances configuration table, select the row containing the
relevant Inbound band.
3. Scroll to the right, until the Coding Type column becomes visible.
4. In the Fade Mode cell, select Turbo-Robust from the drop-down list.
Figure 6: Fade Mode Selection
5. Perform steps 2 through 4 for each Inbound band that is planned to be using the
Adaptive Inbound feature.
6. Click Save.
7. Click Commit.
Result: The Commit Element Changes confirmation request is displayed.
8. Click Yes.

January, 2011 9
9. In the NMS Browser Hub View, right-click the HSP icon, and select
Commands→Reboot for a non-redundant HSP, or
Commands→Reboot Active Standby for a redundant HSP.
Figure 7: HSP Context Menu - Reboot Command
Result: The Reset confirmation request is displayed.
10. Click Yes.
Result: The HSP is reset.
NOTE
At this point, the network downtime begins.
2.4.3 Configuring Access Template
This section describes how to configure the Adaptive Inbound settings in the VSAT
Access template parameters. If more the Adaptive Inbound feature is used on more
than one Access template, perform this procedure for all Access templates in the
system.
To configure the Access template of the desired Inbound Band:
1. In the NMS Browser Toolbar, click Templates.
Result: The VSAT Template Configuration window is displayed.
2. In the VSAT Software column, select the desired software version.
3. In the VSAT RPs column, select Access.
Result: The corresponding Access template is displayed in the Template

Name column.

January, 2011 10
Figure 8: Access Template Selection
4. In the Template Name column, double-click the active template name.
Result: The Access Template Configuration window is displayed.
5. In the tree view, select License Management.
Result: The Adaptive Inbound License Configuration field is displayed.
Figure 9: Adaptive Inbound License Activation
6. From the Adaptive Inbound drop-down list, select Activate.
7. In the tree view, select Inbound.
Result: The Inbound Configuration pane is displayed.

January, 2011 11
Figure 10: Inbound Configuration Pane
8. In the Fade Coding field, select Turbo-Robust from the drop-down list.
9. Click Save.
10. Click OK.
11. Click Commit.
Result: The VSATs Reset confirmation request is displayed.
Figure 11: VSATs Reset Confirmation Request

January, 2011 12
12. Click Yes to reset the VSATs associated with this Access template, or No to
complete the procedure without resetting the VSATs.
NOTE
VSATs must be reset in order for the configuration changes to take effect.
If the procedure is performed on a group of active VSATs, the reset step
can be postponed so as to minimize the VSAT downtime.
13. Close the Access Template Configuration window.
2.4.4 Resetting VSATs
If No was selected during step 12, above, the VSATs associated with the Access
template must be reset later, following these guidelines.
VSAT can be reset one at a time.
VSATs can also be reset in groups. The VSATs that are currently offline can be
reset immediately after the Access template configuration has been completed;
the VSATs that are currently online can be reset later when they go offline.
2.4.4.1 Resetting a Single VSAT
To reset a single VSAT:
1. In the NMS Browser Toolbar, click VSATs View.
Result: The VSAT View window is displayed.
2. Select and right-click the desired VSAT from the VSAT list, and select
Commands→Access→Reset from the context menu.
Result: The Reset confirmation request is displayed.
3. Click Yes to reset the selected VSAT.
Result: The VSAT is reset.
4. Once the VSAT completes its power-up cycle, verify that it has returned to the
Online state.

January, 2011 13
2.4.4.2 Resetting a Group of VSATs
NOTE
It is recommended to reset VSATs in groups of up to 100.
To reset a group of VSATs:
1. In the NMS Browser Toolbar, click VSATs View.
Result: The VSAT View window is displayed.
2. Select and right-click the desired VSATs from the VSAT list, and select
Multiple Reset from the context menu.
Figure 12: Resetting Multiple VSATs
Result: The VSAT Reset confirmation request is displayed.
3. Click Yes to reset the VSATs associated with this Access template.
Result: The VSATs are reset.
4. Once the VSATs complete the power-up cycle, verify that each VSAT has
returned to the Online state.

January, 2011 14
3. Example Scenarios
3.1 Upgrading Existing Network
Adaptive Inbound Coding may provide some advantages when upgrading an older
Gilat network to the SkyEdge system.
In most cases, the customer’s network is tailored to fit the current network link-
budget. When upgrading, it is reasonable for the customer to expect higher Inbound
bitrate requirements. Running such bitrates with the customer’s installed Outdoor
equipment will result in no fade margins and unacceptably low availability.
If the upgrade is combined with enabling the Adaptive Inbound coding, it can be
performed without replacing/re-installing Outdoor equipment: the extra 3.5 dB that
this feature provides is enough to increase the VSATs bitrate for clear sky
conditions. Under rain fade conditions, VSATs will switch to a lower bitrate but will
retain network connectivity and availability for most applications, including
telephony sessions and IP.
3.2 Collecting Inbound Es/N0 Measurements without Using Adaptive Inbound Coding
It may be useful to collect Inbound Es/N0 measurements without actually running the
feature.
The HSP holds detailed Inbound Es/N0 information per each Inbound. The analysis
of the collected information, together with the statistics of retry attempts, may
provide indicators that by enabling Adaptive Inbound coding on the network, the
operator might improve the network availability and reduce retry attempts (on GA
and DA).

January, 2011 15
4. Appendix A - Telemetries
This section describes VSAT Access telemetries relevant to Adaptive Inbound

Coding performance.
To display the desired VSAT's Access telemetry:
1. In the NMS Browser VSATs View window, right-click the desired VSAT icon
and select TelemetriesTelemetries.
Result: The VSAT Telemetries window is displayed.
2. In the VSAT Access Telemetry tree view, expand the

AccessLAPU and Access Schemes nodes.
Result: The VSAT Telemetries expanded tree view is displayed.
Figure 13: VSAT Telemetries Expanded Tree View (Partial View)
3. Proceed to the desired Section:
Section 4.1 Fade Statistics / Fade Statistics + Reset or
Section 4.2 Fade Telemetry.

January, 2011 16
4.1 Fade Statistics / Fade Statistics + Reset
To review Fade Statistics:
1. In the expanded VSAT Access Telemetry tree view, select

Fade Statistics / Fade Statistics + Reset.
Result: VSAT Fade Statistics are displayed.
Figure 14: Fade Statistics Parameters (Partial View)
2. The following parameters are displayed:
Figure 15: Fade Statistics Parameters – General pane

January, 2011 17
General pane
− Minimum Inbound Es/No – Minimum recorded Inbound channel Es/N0, in

decibels
− Maximum Inbound Es/No – Maximum recorded Inbound channel Es/N0, in

decibels
− Average Inbound Es/No – Average recorded Inbound Es/N0, in decibels
− Bursts in Clear Sky – number of bursts sent in clear sky mode
− Bursts in Fade Mode – Number of bursts sent in fade mode
RA / CRA / GA pane, DA pane, Star Voice pane
Figure 16: Fade Statistics – RA / CRA / GA, DA and Star Voice Panels (Partial View)
− Fade Enable – Indicates if fade is enabled for access scheme group. Fade
mode may be disabled since no appropriate license is available, or because
symbol-rate or time-slot duration cannot be supported in fade mode
− Current mode – Mode the VSAT is currently using. Values: clear sky or
fade mode.
− Fade occurrences – Number of fade events in the access scheme group.
− Minimum fade duration –In seconds in the access scheme group.
− Maximum fade duration –In seconds in the access scheme group.
− Total fade duration –In seconds in the access scheme group.
− Fade duration out of total time – Percentage of total time in which the
VSAT was in fade mode

January, 2011 18
4.2 Fade Telemetry
To review Fade Telemetry:
1. In the expanded VSAT Access Telemetry tree view, select Fade Telemetry.
Result: VSAT Fade Telemetry is displayed.
Figure 17: VSAT Fade Telemetry – Inbound EsNo Histogram
2. The histogram provides Inbound channel reception level (Es/N0) time

distribution in the range 0 to 22 dB. Calculation is based on RA symbol-rate. The
information provides tools to monitor the VSAT installation and link-budget
quality over time.

January, 2011 19

Adaptive Inbound Coding

Uploaded by

Document Information

Original Description:

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

Adaptive Inbound Coding

Uploaded by

Copyright:

Available Formats

Adaptive Inbound Coding

Document No. DC-002265(A)

Gilat Satellite Networks Ltd.

2. Configuring Adaptive Inbound ..................................................................................... 6

3. Example Scenarios ......................................................................................................15

4. Appendix A - Telemetries ............................................................................................16