Customer Education Services

SKYEDGE II–C BACKHAULING OVERVIEW

CUSTOMER EDUCATION SERVICES

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.

SEII-c Backhauling Overview 1

Customer Education Services

AGENDA

Introduction

Operation modes

Backhauling concepts
o The Connection
o Connections Multiplexing
o Streams
o BW allocation algorithm
o Header compression
o Packet aggregation
o Delay control
o QoS

2 | Proprietary and Confidential

2

SEII-c Backhauling Overview 2

Customer Education Services

INTRODUCTION

3 | Proprietary and Confidential

SEII-c Backhauling Overview 3

Customer Education Services

CELLULAR BACKHAULING OVER SATELLITE

Introduction

Gilat pioneered the cellular backhauling over TDMA VSATs solution

SkyEdgeII-c is a 4th generation solution for backhauling offering by Gilat:

o Abis optimizers over SkyEdge native telephony technology
o Optimizers and IP based solution over SkyEdge data technology
o IP based and optimizers over SkyEdge-II C2P technology
o IP based high-performance SkyEdge-II-c C2P based technology with data acceleration

4 | Proprietary and Confidential

4

SEII-c Backhauling Overview 4

Customer Education Services

CELLULAR BACKHAULING OVER SATELLITE

Introduction

Cellular backhauling imposes unique requirements on the system:

o Tight RTT, jitter requirements
o Sensitivity to packet loss for specific streams
o Performance at a dynamic, wide range of data rates
o QoS requirements (Signalling, voice, data, video, Management…)
o High reliability
o Compatibility with a wide range of vendors

The SkyEdge II-c design takes into account these requirements and provides a dedicated solution

5 | Proprietary and Confidential

5

SEII-c Backhauling Overview 5

Customer Education Services

SATELLITE BACKHAUL FOR LTE

TDMA Solution architecture

6 | Proprietary and Confidential

6

SEII-c Backhauling Overview 6

Customer Education Services

BACKHAULING CONCEPTS - CONNECTION

7 | Proprietary and Confidential

SEII-c Backhauling Overview 7

Customer Education Services

C2P CONNECTIONS
Overview

Backhauling Virtual Circuits used for:

o IB allocation management
o IB+OB header compression on IP level
o Define BW allocation priority on a network level

Connection i

VSAT
Connection j

BackBone
traffic
8 | Proprietary and Confidential
8

Virtual circuit – the Backhauling traffic is isolated from other traffic types, it receives dedicated allocations, it
manages its own QoS.

SEII-c Backhauling Overview 8

Customer Education Services

C2P CONNECTIONS
Main Principles

C2P (Connection Control Protocol) is based DVB-RCS standard, used to establish connections

The VSAT is the master of the process. In charge of:

o Establishing the connection
o Terminating the connection
o BW requests and modify

Allocation requests sent reliably over C2P

The connection is established on both access

o L2: VSAT - HSP
o L3-4, Data – VSAT - DPS

9 | Proprietary and Confidential

9

SEII-c Backhauling Overview 9

Customer Education Services

C2P CONNECTIONS
Parameters

A connection is defined by a unique combination of the following parameters:

o VLAN
o eNodeB IP address
o Core entity IP address
o IP protocol (e.g. UDP, SCTP)

Each VSAT may hold a number of concurrent connections

A C2P allocation request receives the highest priority from the HSP

HSP allocates a low jitter allocation pattern for C2P, if the request can’t be met it is rejected

10 | Proprietary and Confidential

10

SEII-c Backhauling Overview 10

Customer Education Services

C2P CONNECTIONS
Connection Establishment

The connection is established by the VSAT which is the master of the connection

A connection may be established in one of the methods:

o Upon VSAT Logon
– Once VSAT establishes a BackBone connectivity with the hub, the configured C2P connections are established

C2P More
VSAT 1st Packet
connection packets
Logon arrives
established arrive

o Upon first matching packet

– Once a packet arrives at the VSAT matching the defines criteria for a connection, the VSAT establishes the
connection

C2P More
VSAT 1st Packet
connection packets
Logon arrives
established arrive

11 | Proprietary and Confidential

11

SEII-c Backhauling Overview 11

Customer Education Services

C2P CONNECTIONS
Connection Teardown

Each connection is monitored for the traffic it carries

Once a packet is detected on either OB or IB, a timer is started

If a new packet arrives, the timer is restarted

Once timer expires, the connection is torn down

The timer may be configured for infinity, in which the connection will never be torn down, unless the VSAT
loses Backbone connectivity

Timer Expired
Connection down
Packet Packet Packet Packet

t1 t1 t1 Inactivity timer

12 | Proprietary and Confidential

12

Why do we need to teardown the connection?

Example:

Consider a network with redundant servers. eNodeB attempts connection to server #1 which is down. The
packets sent create connection #1. eNoteB then tries connection #2, and succeeds. We now have 2 active
connections, one carries no traffic but may consume BW (If min BW is not zero) and C2P resources.

SEII-c Backhauling Overview 12

Customer Education Services

C2P CONNECTIONS
Connection Properties

The following properties are associated with a connection:

o Connection establishment method
o Connection teardown timer
o Bandwidth properties and parameters:
– Measured BW
– Extra BW
– Minimum BW
– Maximum BW
– Allocated BW
o Undefined stream behavior
o Internal streams

13 | Proprietary and Confidential

13

SEII-c Backhauling Overview 13

Customer Education Services

C2P MULTIPLEXING

14 | Proprietary and Confidential

14

SEII-c Backhauling Overview 14

Customer Education Services

C2P MULTIPLEXING
Introduction

As cellular network architecture is evolving it may require opening of high number of C2P connections
o Each connection requires reservation and allocation of resources that not always fully utilized without the
option of sharing the unused BW between single connections

There is an option to merge multiple connections into a single C2P connection

o Provides better BW utilization

15 | Proprietary and Confidential

15

As cellular network architecture is evolving it may require opening of high number of C2P connections. Each
connection requires reservation and allocation of resources that not always fully utilized without the option of
sharing the unused BW between single connections.

SEII-c Backhauling Overview 15

Customer Education Services

C2P MULTIPLEXING
Example

Single Connections Meta Connection

IP=1.1.1.12.2.2.2
UDP, VLAN=3023
Min=32
Extra=16

IP=1.1.1.13.3.3.3
UDP, VLAN=3023
Min=32
Extra=16 Meta
Min=32
IP=1.1.1.12.2.2.2 Extra=16
SCTP, VLAN=3023
Min=32
Extra=16

IP=1.1.1.12.2.2.2
SCTP, VLAN=3024
Min=32
Extra=16

16 | Proprietary and Confidential

16

In this example (on left), we have 4 C2P connections, each consumes 32[kbps] even before the first Byte is sent,
so the requested initial BW is 128[kbps].
In case all connections exceed the minimum BW, they ask for extra 16[kbps] each. This amounts to 64[kbps].
That are usually not used and are reserved to reduce the latency of the next increase in BW rate.
Some connections (e.g. those carrying SCTP) require BW far more than the actual throughput in order to
minimize latency.
Using Meta connection (on right), we keep the same Min, Extra as we had for each of the 4 connections and
apply it to a single connection. Since the assumption is that the extra BW is used to compensate for the next
call/throughput increase, and since not all of them will have an increase at the same time, the same Extra may
be used. The same logics goes for the minimum BW.
For SCTP signalling, where packets arrive in relatively large time intervals, multiplexing makes response time
better using the same values of overhead because the aggregated rate allows the VSAT to more accurately
measure the throughput and ask for appropriate resources.

SEII-c Backhauling Overview 16

Customer Education Services

C2P MULTIPLEXING
Introduction

The connection that multiplexes a number of single connections called Meta connection
o Connections from different IP address pairs, VLANs and protocols may be multiplexed into a single Meta
connection
o All the streams of the “child” connections become streams of their Meat connection
o The Meta connection manages the BW (RTN allocations) and common parameters to all of its child
connections
o The rate estimation algorithm applies to the entire Meta connection
o The connection establishment process is identical to the existing method
– By Login or By Traffic

17 | Proprietary and Confidential

17

SEII-c Backhauling Overview 17

Customer Education Services

STREAMS

18 | Proprietary and Confidential

18

SEII-c Backhauling Overview 18

Customer Education Services

BACKHAULING STREAMS
Overview

Streams are internal L3/L4 flows within a connection

Streams are established between the VSAT and the DPS, by the VSAT who is the master of the stream

Streams are used for handling different flows allowing individual:

o Header compression
o QoS

Stream are defined as a unique combination of:

o ToS value
o eNodeB-side UDP port
o EPC-side UDP port

Up to 255 streams in a connection

19 | Proprietary and Confidential

19

SEII-c Backhauling Overview 19

Customer Education Services

BACKHAULING STREAMS
Diagram

Traffic NOT complying with

C2P definitions (To BB)

Default Stream

Stream i

C2P Connection Stream j

Stream k
Traffic complying
Control Stream with C2P
definitions (To C2P)

20 | Proprietary and Confidential

20

SEII-c Backhauling Overview 20

Customer Education Services

BACKHAULING STREAMS
Features

It is possible to configure a stream to perform header compression on IP+UDP, on IP only or no header

compression at all

Streams allow individual QoS management:

o Each stream is assigned an internal priority level based on its ToS value, and UDP port combination

Slow Release is configured per-Stream

21 | Proprietary and Confidential

21

SEII-c Backhauling Overview 21

Customer Education Services

BACKHAULING STREAMS
Establishing

Stream are created based on packets detected only

During the establishment process, streams are sent over the default stream, without header compression, in
low priority

Streams are torn down based on inactivity timer expiry

Packets matching the connection filter, but not belonging to any configured stream may be treated, based on
connection-level configuration:
o As non-Backhauling packets, sent to BackBone
– No priority, no header compression, doesn’t consume connection resources
o In the default stream
– Low priority, no UDP header compression

22 | Proprietary and Confidential

22

SEII-c Backhauling Overview 22

Customer Education Services

BACKHAULING STREAMS

Each packet matching the stream filter will create a stream, if it is not yet established
o In some cases, this could lead to a very large number of streams, exceeding the available number of streams
o It is possible to configure a “trunk” of streams sharing the same ToS
o A Trunk consumes a single stream, but doesn’t allow UDP header compression

23 | Proprietary and Confidential

23

SEII-c Backhauling Overview 23

Customer Education Services

BANDWIGTH ALLOCATION

24 | Proprietary and Confidential

24

SEII-c Backhauling Overview 24

Customer Education Services

BW ALLOCATION ALGORITHM
Parameters

Each connection has the following parameters:

o Minimum BW (may be zero or more)
o Maximum BW
o Extra BW (may be zero or more)
o BW decrease guard time

The combination of these parameters ensures the availability of resources ahead of time

Each parameter is configurable allowing the user to decide on the tradeoff between user experience and BW
efficiency

25 | Proprietary and Confidential

25

SEII-c Backhauling Overview 25

Customer Education Services

BW ALLOCATION ALGORITHM
Minimum BW

Min BW
o Requested by the connection upon its establishment
o Connection never requests less than minimum BW
o When a packet arrives to an idle VSAT, the fact that the BW is already available reduces the response time
o When set to zero, if the measured BW is also zero, zero BW is requested

26 | Proprietary and Confidential

26

SEII-c Backhauling Overview 26

Customer Education Services

BW ALLOCATION ALGORITHM
Extra BW

Extra BW
o The extra BW bridges the gap between the detection of rate increase and the arrival of allocations (~ RTT)
o Assuming a given traffic pattern, in the next millisecond it may increase (e.g. one more call established). If no
extra BW is available, the packets will be delayed by at least RTT until the new allocations are available
o Without extra BW, jitter, delay and packet loss may occur
o When set to zero, no extra BW is requested leading to increased efficiency at the cost of voice quality

27 | Proprietary and Confidential

27

SEII-c Backhauling Overview 27

Customer Education Services

BW ALLOCATION ALGORITHM
Maximum BW

Maximum BW – prevents the VSAT from asking too much BW (e.g. asking for Extra when it is known the cell is
already at its maximum capacity)
o Example – a cell is limited to 5 Mbps
o The current measured BW is 5 Mbps, and the extra BW is 1 Mbps. Without the Max BW parameter, the
connection would ask for 6 [Mbps]

28 | Proprietary and Confidential

28

SEII-c Backhauling Overview 28

Customer Education Services

BW ALLOCATION ALGORITHM
BW Decrease Guard Time

BW decrease guard time

o Prevents the possibility that a momentary traffic reduction will lead to allocation decrease
o If the traffic returns to its previous level immediately, packet loss, jitter and delay may occur
o May be set to zero thereby increasing efficiency at the cost of possible packet loss, jitter and delay

29 | Proprietary and Confidential

29

SEII-c Backhauling Overview 29

Customer Education Services

BW ALLOCATION ALGORITHM
Operation

The VSAT measures the received bytes every 250 [msec]

o Based on the last 4 measurements, the VSAT calculates the bits-per-second
– If calculated bit rate > previous calculated bit rate, then the VSAT sends a BW modify request with the required BW =
measured BW + extra BW
– If calculated bit rate < previous calculated bit rate for more than guard time, then the VSAT sends BW modify request
with the required BW = measured BW + extra BW

30 | Proprietary and Confidential

30

Measurement starts when C2P connection is established. Until channel is established, packets are sent over
Backbone. When C2P is established, and measurement is large, but BW not yet granted, packets are queued,
subject to delay control.

SEII-c Backhauling Overview 30

Customer Education Services

BW ALLOCATION ALGORITHM
Operation Diagram

31 | Proprietary and Confidential

31

In this diagram we can follow the VSAT BW requests (red line) above the measured BW (blue line). The
requested BW is equal to Measured BW + Extra BW. The BW requests are always in limited by the Min and Max
values. When the measured BW exceeds the Maximum, VSAT will request for Max BW. From the moment that
the measured traffic will start decreasing, VSAT will continue requesting for the same BW until the decrease
guard timer is expired. After that VSAT will modify the request to a new measured + extra BW.

SEII-c Backhauling Overview 31

Customer Education Services

BW ALLOCATION ALGORITHM
BW Cases & VSAT Behavior

Measured BW = 0, min BW = 0  requested BW = 0

Measured BW = 0, min BW > 0  requested BW = max (Min BW, Extra BW)

Measured BW > 0; Measured BW + Extra BW < Min BW  Requested Min BW

Measured BW > 0; Measured BW + Extra BW > Min BW  Requested BW = Measured BW + Extra BW

Measured BW + Extra BW > Max BW  Requested BW = Max BW

Measured BW < previously measured BW for a time < guard time  Requested BW remains the same

Measured BW < previously measured BW for a time > guard time  Requested BW reduced to measured BW +
extra BW (limited by min and Mx)

32 | Proprietary and Confidential

32

SEII-c Backhauling Overview 32

Customer Education Services

HEADER COMPRESSION

33 | Proprietary and Confidential

33

SEII-c Backhauling Overview 33

Customer Education Services

HEADER COMPRESSION
Overview

Header compression is applied to IP packets

Per-stream configuration enables no compression, IP level only compression and UDP+IP header compression

Ethernet, IP and UDP headers are not carried over-the-air

An internal header is used to deliver end-to-end information

The internal header on the OB contains the connection index in addition to the information contained in the IB
header

The IB connection ID is carried in the ATM-level VPI/VCI parameters without any additional cost

Packets are associated with a stream in order to enable header decompression on the receiving side of the
satellite link

34 | Proprietary and Confidential

34

SEII-c Backhauling Overview 34

Customer Education Services

HEADER COMPRESSION
IB Compression

UDP/IP packet (IB)

UDP header
IP header
20[B]
8[B] Payload

Internal
header Payload
4[B]

IP packet (IB) IP header

20[B]
Payload

Internal
header Payload
4[B]

35 | Proprietary and Confidential

35

SEII-c Backhauling Overview 35

Customer Education Services

HEADER COMPRESSION
OB Compression

UDP/IP packet (OB)

IP header UDP header

20[B] 8[B]
Payload

Internal
header Payload
5[B]

IP packet (OB)
IP header
20[B]
Payload

Internal
header Payload
5[B]

36 | Proprietary and Confidential

36

SEII-c Backhauling Overview 36

Customer Education Services

HEADER COMPRESSION
Compression Example

Typical values for 3G voice over RTP

o AMR 12.2 packet contains 35 Bytes of CODEC + 12 Bytes of RTP
– The packet size is 75 Bytes
– IP header compression saves 16 bytes, 21% savings
– IP+UDP header compression saves 24 bytes, 32% savings
o AMR 4.75 packet contains 17 Bytes of CODEC + 12 Bytes of RTP
– The packet size is 57 Bytes
– IP header compression saves 16 bytes, 28% savings
– IP+UDP header compression saves 24 bytes, 42% savings

37 | Proprietary and Confidential

37

AMR Packet 12.2 kbps:

35 Bytes Codec +12 Bytes RTP + 8 Bytes UDP + 20 Bytes IP = 75 Bytes

Note that in RTP mode we have a smaller header of 3 bytes, and the savings climbs to 50%

SEII-c Backhauling Overview 37

Customer Education Services

PACKET AGGREGATION

38 | Proprietary and Confidential

38

SEII-c Backhauling Overview 38

Customer Education Services

PACKET AGGREGATION
RTN Carrier

In the RNT carrier DVB-RCS ATM mode is used, each burst (TRF) contains 2 or 4 ATM cells

Packets are being collected so as to fill the burst, as much as possible, whether it is a 2-ATM or a 4-ATM burst

Best for small packets, as it shares burst overhead between multiple packets

Increased efficiency

Reduced processing load

1 2 n

H Payload H Payload …. H Payload OH

Burst
39 | Proprietary and Confidential
39

SEII-c Backhauling Overview 39

Customer Education Services

PACKET AGGREGATION
FWD Carrier

Applies on Backhauling compressed C2P traffic

Internal C2P header remains for each aggregated packet

The aggregation is configured per FWD Priority – High, Medium and Low
o For each CPE, packets of three FWD priorities may be aggregated and share one IP Neto header

Packets may be aggregated up to

o Maximal configured number of bytes
o Maximal configured delay
– The first threshold reached is applied

40 | Proprietary and Confidential

40

FWD BH packets aggregation is configured per BH FWD priority. For each priority the aggregation may be
enabled or disabled. In addition for each priority it’s possible to configure:

Aggregation Length in Bytes - maximum size of aggregated bytes

Maximum packet delay in ms – maximum time between transmission of aggregated data

SEII-c Backhauling Overview 40

Customer Education Services

DELAY CONTROL

41 | Proprietary and Confidential

41

SEII-c Backhauling Overview 41

Customer Education Services

DELAY CONTROL
Background

The VSAT has internal queues

It is possible that a traffic surge or resource unavailability will cause packets to stay for long duration in the
queues

In such cases, delay may be accumulated in the queues

42 | Proprietary and Confidential

42

SEII-c Backhauling Overview 42

Customer Education Services

DELAY CONTROL
Main Principles

Each packet is time-stamped upon entry to the VSAT

Once transmission opportunity occurs, the current time is compared with the packet arrival time

If the difference is equal the configured threshold, the packet is dropped

Most important for voice packets

If extra BW is large enough, packets should not be dropped due to delay Packet stays in line
too long. Drop!
The maximum delay is a configurable property of the connection

43 | Proprietary and Confidential

43

SEII-c Backhauling Overview 43

Customer Education Services

QOS

44 | Proprietary and Confidential

44

SEII-c Backhauling Overview 44

Customer Education Services

QOS
Allocations

All C2P connections, of all VSATs get the same priority

C2P priority is the highest in the network, compared with all levels of BackBone priority

Allocations are sent for a specific connection in a VSAT

Traffic from any other connection or from backhauling on that VSAT can’t interfere with the established
connection traffic

45 | Proprietary and Confidential

45

SEII-c Backhauling Overview 45

Customer Education Services

QOS
Main Principles

Once an allocation is granted to a C2P connection, it can’t be taken away

o If a connection needed BW and received it, it will not be taken for another connection
o That connection user experience will not suffer degradation
o Another connection needing new BW can’t get it

New passengers for which

there is no place, are not
allowed to degrade service for
passengers already in bus.
They are left outside the bus.

46 | Proprietary and Confidential

46

SEII-c Backhauling Overview 46

Customer Education Services

QOS
BW Management Options

Various Backhauling BW Management mechanisms are applicable for RTN and FWD carriers on several levels
o C2P level
– Each connection may only request up to its Max BW parameter
– Applicable for RTN allocations
o CPE Level
– The total requests in the CPE are limited by the CPE MIR
– Implemented in SLA profile
– Applicable for RTN allocation and FWD traffic
o MG Level
– The total allocations for all the CPEs in a MG are limited by the MG MIR
– Implemented in SLA profile
– Applicable for RTN allocation and FWD traffic

47 | Proprietary and Confidential

47

SEII-c Backhauling Overview 47

Customer Education Services

QOS
BW Management Cont.

Various Backhauling BW Management mechanisms are applicable for RTN and FWD carriers on several levels
o NS level
– The total FWD Backhauling traffic of the whole NS is limited to this value
– Applicable only for FWD traffic
o Priorities
– Applicable for RTN and FWD, different implementation

48 | Proprietary and Confidential

48

SEII-c Backhauling Overview 48

Customer Education Services

QOS
C2P BW Allocations

Each C2P connection may only request up to its Max BW parameter

The MIR is enforced on the BW allocation

Configured per BH connection

49 | Proprietary and Confidential

49

SEII-c Backhauling Overview 49

Customer Education Services

QOS
BW Management - CPE

The total requests of the CPE are limited by the CPE MIR

The MIR is enforced for the RTN BW allocation and for FWD traffic

Implemented in SLA profile

CPE may have a separated MIR for a Backhauling traffic according to configuration in the SLA profile
o Backhauling MIR may be included or excluded from the VSAT MIR
– Included is only applicable for the RTN direction

50 | Proprietary and Confidential

50

There are 2 models for Backhauling MIR to choose from per direction:

“Included” – There is one MIR for the VSAT. The Backhauling traffic is limited by the lower between the VSAT
MIR and Backhauling MIR. Setting the Backhauling MIR lower than the VSAT MIR ensures BackBone traffic not
completely oppressed by Backhauling. Applicable only for RTN traffic
“Excluded” – the Backhauling connections may not exceed Backhauling MR, all of the other traffic in the VSAT
may not Exceed VSAT MIR. Backhauling requests plus Backbone requests may be in total larger than VSAT
MIR

SEII-c Backhauling Overview 50

Customer Education Services

CBR and BH allocation have the same priority, so first comes, first served.
In case CPE is configured with CBR and the BH MIR mode is “Included”, the CBR allocation
will be reduced proportionally to the BH traffic when BH connection will become active.
In “Excluded” mode CBR is not affected by the BH traffic.

SEII-c Backhauling Overview 50

Customer Education Services

QOS
BW Management - MG

The total BW for all the CPEs in a managed group are limited by the MG MIR

The MIR is enforced for the RTN BW allocation and for FWD traffic

Implemented in the MG settings per each linked NS

Applicable for both, RTN and FWD

o Backhauling MIR may be included or excluded from the MG MIR
– Included is only applicable for the RTN direction

51 | Proprietary and Confidential

51

There are 2 models for Backhauling MIR to choose from per direction:

“Included” – There is one MIR for the MG. The Backhauling traffic is limited by the lower between the MG MIR
and MG Backhauling MIR. Applicable only for RTN traffic
“Excluded” – the Backhauling connections may not exceed Backhauling MR, all of the other traffic in the VSAT
may not Exceed VSAT MIR. Backhauling requests plus Backbone requests may be in total larger than VSAT
MIR

SEII-c Backhauling Overview 51

Customer Education Services

QOS
BW Management - NS

The total Backhauling BW may be separated from the Backbone BW for the whole NS
o Applicable only for FWD traffic

52 | Proprietary and Confidential

52

SEII-c Backhauling Overview 52

Customer Education Services

QOS
RTN Priority Mechanism

Absolute priority mechanism – higher priority sent first, no weight mechanism

When a transmit opportunity arrives, the VSAT will start emptying the queues starting with the highest priority

As long as the higher priority queue is not empty, the lower priority queues are not served

This may lead to packet accumulation in the lower priority queues

Delay control kicks in ones delay exceeds a threshold, and drops the packets

Delay is being evaluated on each Tx opportunity

There is no other method of dropping packets due to priority

Each configured stream may be assigned one of the 13 priority levels

Default (lowest) priority assigned to unclassified TOS values

53 | Proprietary and Confidential

53

SEII-c Backhauling Overview 53

Customer Education Services

QOS
FWD Priority Mechanism and MIR

The streams are classified into 3 absolute priority levels, based on configuration sent to DPS upon stream
establishment
o The High priority is sent without delay or jitter, and is not dropped
– Typically used only for signaling
o The Medium priority is sent without delay
– Typically used for voice traffic so should be very jitter sensitive.
– If the MIR value is reached, packets are dropped
o The low priority traffic is allowed a small queueing delay in order to absorb traffic spikes
– Typically used for Backhauling data traffic
– If the medium priority consumed all of the MIR, by the end of a timer, the traffic in the queue is discarded

54 | Proprietary and Confidential

54

SEII-c Backhauling Overview 54

Customer Education Services

QOS
FWD Priority Mechanism and MIR

55 | Proprietary and Confidential

55

FWD Backhauling traffic may be classified with three absolute priorities:

The High priority is sent without delay or jitter, and is not dropped. It is assumed high priority is used mostly for
signalling, hence constitutes a small portion of the network BW. The high priority traffic is deducted from MIR,
leaving a smaller MIR for the remainder of the traffic
The Medium priority is sent without delay. It represents typically voice traffic so should be very jitter sensitive. If
the MIR value is reached, packets are dropped
The low priority traffic is allowed a small queueing delay in order to absorb traffic spikes. If the medium priority
consumed all of the MIR, by the end of a timer, the traffic in the queue is discarded

SEII-c Backhauling Overview 55

Customer Education Services

QOS
FWD Priority Mechanism and MIR

All MIR values are static configuration values

What happens in case of OB fade?

o IPM receives 3 priority queues for the Backhauling traffic
o It empties each queue according to the priority
o If the current spin doesn’t hold sufficient capability to carry all traffic, packets are left in the queues
o If there are packets in the queues within a timer (10 ms) of their arrival, the queues are flushed

BackBone traffic is a lower priority than the lowest Backhauling priority, so Backhauling and Backbone may
share the same outbound, but Backhauling has priority

MIR enforcement for BackBone and for Backhauling are two completely separate processes (like the
“Excluded” mode in IB)

56 | Proprietary and Confidential

56

SEII-c Backhauling Overview 56

Customer Education Services

QOS
FWD Priority Mechanism and MIR

57 | Proprietary and Confidential

57

SEII-c Backhauling Overview 57

Customer Education Services

THANK YOU

Gilat Satellite Networks | [email protected] | www.gilat.com

58

SEII-c Backhauling Overview 58