Providing Mesh with SkyEdge

1
 It’s all about …
Latency – Mesh connectivity between VSATs reduces the latency
by 50% !

An improved user experience due to lower latency

OPEX – Mesh connections save $$ by eliminating the need of

double hop

Test Case: 8
Star
7
• 500 VSATs, 4 lines per VSAT, G.723 Mesh
6
• ½ of the calls are between VSATs
5
• 0.2 Erlang per line (busy hour)
4
Star
3

• Star requires 20% more Bandwidth ! 2 Mesh

• Star requires 85% higher OB 1

Required OB [Mbps] Total BW [Mhz] 2
 SkyEdge Mesh principles
SkyEdge supports all three topologies: Star, Multi-Star and Mesh

Mesh

GSM

Star Multi
star

E1 PSTN

SkyEdge Gateway
PoP
Switch
WLL

SkyEdge Call
SkyEdge Pro

SkyEdge Family
Hub

Phone Fax

3
 SkyEdge Mesh principles
Voice and Data - I

Mesh is supported for data, native voice and managed VoIP

Direct Voice/data VSAT to VSATs one hop
DAMA or PAMA links

Voice:
 BW is assigned and managed centrally by the hub
 CDRs are created at the end of the call
 Using mesh card in the VSAT (SE Pro and SE Call)
 Supported on both Native voice and Managed VoIP.

4
 SkyEdge Mesh principles
Voice and Data - II

Data:
Up to 30 concurrent connections per VSAT (or Multislot-1)

PAMA links are initiated on startup

DAMA assignments are issued upon IP destination as configured
per VSAT

 Each Mesh definition in VSAT can be one of two policies:

Default – number of assigned time slots is static
Adaptive – The hub optimizes the number of assigned TS every few
seconds (according to real rate of traffic)
MIR and CIR per link.

TCP spoofing is supported on those links

5
 Required elements in SkyEdge
to support Mesh

In the hub – DCAS card (manages requests for Mesh

connections)
Mesh Card in the VSAT
SkyEdge Pro
SkyEdge Gateway
Verifying Link budget for VSAT to VSAT connections

6
7