Data Communications

Concepts
Chapter 3, IOM Basic Training
March 2006
 Copyright Notice

iDirect Technologies Technical Training Manual

Copyright © 2002; 2004-2006, iDirect, Inc. All rights reserved. This training
material may not be reproduced, in part or in whole, without the permission of
iDirect, Inc.
All other brands or product names are trademarks or registered trademarks of
their respective holders.
Printed in the USA.
No part of this work covered by copyright may be reproduced in any form.
Reproduction, adaptation, or translation without prior written permission is
prohibited, except as allowed under the copyright laws.
This publication is provided by iDirect Technologies as-is without warranty of any
kind, either express or implied, including, but not limited to, the implied warranties
or conditions of merchantability or fitness for a particular purpose. iDirect
Technologies shall not be liable for any errors or omissions which may occur in
this publication, nor for incidental or consequential damages of any kind resulting
from the furnishing, performance, or use of this publication.
Information published here is current or planned as of the date of publication of
this document. Because we are improving and adding features to our products
continuously, the information in this document is subject to change without notice.

2
 Communications Concepts
Voice/Video/Data Traffic Comparison
Voice/Video Traffic Characteristics Data Traffic Characteristics
Real-time Applications Not Real-time

Time sensitive information High Speed Data (very

Error sensitive)
Sensitive to Delay and Not sensitive to Delay or
Delay Variation (Jitter) Delay Variation
Deliver information in Sensitive to even a single
real-time or not at all bit error (retransmissions)
Information content directly Information content
affected by delay (time) unaffected by time (delay)

Not sensitive to bit errors Very sensitive to bit errors

(uncompressed)
Information retransmitted
Information never retransmitted on bit error(s)

Multi-media Applications & Image Large file transfer (ftp, etc.)

Processing

3
 Communications Concepts
Generic OSI Model

Layer Open Source Interconnection (OSI) Model/Protocol Stack

APPLICATION The ‘Application’ layer performs common application services

Throw Sausage Pizza Away

7
and supports end-user processes, (Telnet, FTP, e-mail, etc.).
The ‘Presentation’ layer provides services to the Application layer.
PRESENTATION HTML Services provided for syntactical differences in data representation
6 within the end user systems.
The ‘Session’ layer manages interaction between end-user
SESSION HTTP application processes. It establishes check-pointing, adjournment,
5 termination and restart procedures.

The ‘Transport’ layer provides transparent transfer of data between

4 TRANSPORT TCP/UDP end users. It ensures complete data transfer.
The ‘Network’ layer provides the functional & procedural means of
transferring variable length data sequences from a source to a
3 NETWORK IP destination while maintaining the quality of service requested by the
Not

Transport layer. Performs network routing & error control functions.

Data Link Layer LLC Sublayer The ‘Data Link’ layer provides the functional and procedural means
2 to transfer data between network entities. Includes Media Access
Please Do

Ethernet MAC Sublayer Control (MAC) layer, which controls network access & Logical Link
Control (LLC) layer for frame sync, flow control and error checking.
MMF, SMF
Physical
1 Physical Media
UTP, STP, Coax The ‘Physical’ layer establishment & termination of a connection to
RF Frequency a communications medium. It is the ‘hardware’ layer providing
physical means for sending and receiving data.

4
 Communications Concepts
Ethernet Packet Encapsulation

TCP Packet
(Layer 4) IP Packet Ethernet Packet
(Layer 3) (Layer 2)
Packet
(Application)
Data
TCP, UDP, ICMP, etc.
Protocol Header

IP Header

Ethernet
Header

CRC
Layer 5 Layer 4 Layer 3 Layer 2

TCP Packet IP Packet

Information Ethernet Packet
Information
Field Information Field
Field

5
 Communications Concepts
Generic Frame Structure
OSI
Level

7 Application Application Data (1460 max.)

6 Presentation
5
Session

4 Transport (TCP) TCP Hdr (20) Application Data (1460)

TCP Packet – 1480 Bytes

IP Hdr (20) TCP Hdr (20) Application Data (1460)

3 Network (IP)
IP Packet – 1500 Bytes

2
Data MAC Hdr (14)
IP Hdr (20) TCP Hdr (20) Application Data (1460) CRC (4)
DA SA T/L VLAN* (4)
(MAC)
Ethernet Ethernet Frame – 1514 Bytes (1518 bytes w/VLAN)

1 Physical Physical Media Dependent Sub-layer MMF, SMF

(no packet manipulation/no additional header) UTP, STP,
Wireless

* Optionally Enabled
6
 Communications Concepts
iDirect Proprietary Satellite Link Layer
OSI Layer

7 APPLICATION
PC (Data)
Application
6 PRESENTATION

5 SESSION

OSI over
Satellite
TCP, RTP,
4 TRANSPORT UDP, ICMP

IP,
3 NETWORK IP Routing

Proprietary
iDirect Satellite Handling &
2
Link Layer Frame Format
Radio
1 Satellite Physical Frequency
Terminal

7
 Communications Concepts
iDirect Outroute Frame Structure
OSI Layer
7 Application Application Data (1460 max.)

6 Presentation
5 Session

TCP Hdr (20) Application Data (1460)

4 Transport (TCP) TCP Packet – 1480 Bytes

IP Hdr (20) TCP Hdr (20) Application Data (1460)

IP Packet – 1500 Bytes

3 Network (IP)
IP Hdr (20) TCP Hdr (20) Application Data (1460)

IP Packet – 1500 Bytes

iDirect LL Hdr (6) SAR* (2) Encr* (2-9) VLAN* (2) IP Hdr (20) TCP Hdr (20) Application Data (1460) CRC (2) FEC (302)

iDirect Outroute (Large Block, 0.793 FEC) Frame

2 Link Layer (iDirect Satellite LL)
iDirect LL Hdr (6) SAR* (2) Encr* (2-9) VLAN* (2) IP Hdr (20) TCP Hdr (20) Application Data (1460) CRC (2) FEC (737)

iDirect Outroute (Large Block, 0.495 FEC) Frame

HDLC (<1) iDirect LL Hdr (6) SAR* (2) Encr* (2-9) VLAN* (2) IP Hdr (20) TCP Hdr (20) Application Data (1460) CRC (2) FEC (302) HDLC (<1)

iDirect Outroute (Large Block, 0.793 FEC) Frame

1 Physical (Physical Media Dependent Sub-layer)

HDLC (<1) iDirect LL Hdr (6) SAR* (2) Encr* (2-9) VLAN* (2) IP Hdr (20) TCP Hdr (20) Application Data (1460) CRC (2) FEC (737) HDLC (<1)

iDirect Outroute (Large Block, 0.495 FEC) Frame

* Optionally Enabled * SAR=Segmentation And Reassembly

8
 Communications Concepts
Protocol Stack - HDLC Packet Format

iDirect Outroute Packet Format

Physical iDirect Header IP Error Correction Physical

HDLC Link Layer IP Packet CRC FEC HDLC

<1 6 Variable 2 % <1 0.793 or

0.495

9
 Communications Concepts
Outroute Packet Format

iDirect Outroute Packet Format

Physical iDirect Headers IP (User Data) + Encr + VLAN Error Correction Physical

HDLC Link Layer SAR* Encr* VLAN* IP Packet CRC FEC HDLC

0.793 or
<1 6 2 2 2 IP Data Variable Len 2 % <1 0.495

Address Frame Tx Seq RxSeq Queue Packet Segment Last KEY Initial Encoding Priority CFI VLAN
Seq Num Type Num Num ID ID ID Indic ID Vector Offset ID

Link Layer SAR Encryption VLAN

Header Header Header Header

* Optionally Enabled

10
 Communications Concepts
iDirect Inroute Frame Structure
OSI Layer

7 Application Application Data (1460 max.)

6 Presentation
5 Session

TCP Hdr (20) Application Data (1460)

4 Transport (TCP) TCP Packet – 1480 Bytes

IP Hdr (20) TCP Hdr (20) Application Data (1460)

3 Network (IP) IP Packet – 1500 Bytes

IP Hdr (20) TCP Hdr (20) Application Data (1460)

IP Packet – 1500 Bytes

Demand (2) iDirect LL Hdr (6) PAD (2) SAR* (2) Encr* (2-9) VLAN* (2) Application Data (70) CRC (2) FEC (44)

iDirect Inroute (Small Block, 0.66 FEC) Frame

2 Link Layer (iDirect Satellite LL)
Demand (2) iDirect LL Hdr (6) PAD (2) SAR* (2) Encr* (2-9) VLAN* (2) Application Data (392) CRC (2) FEC (106)

iDirect Inroute (Large Block, 0.793 FEC) Frame

GB (<1) UW (8) Demand (2) iDirect LL Hdr (6) PAD (2) SAR* (2) Encr* (2-9) VLAN* (2) Application Data (70) CRC (2) FEC (44) GB (<1)

iDirect Inroute (Small Block, 0.66 FEC) Frame

1 Physical
GB (<1) UW (8) Demand (2) iDirect LL Hdr (6) PAD (2) SAR* (2) Encr* (2-9) VLAN* (2) Application Data (392) CRC (2) FEC (106) GB (<1)

iDirect Inroute (Large Block, 0.793 FEC) Frame

* Optionally Enabled * Packet Assembly and Disassembly UW=Unique Word

11
 Communications Concepts
Protocol Stack – TDMA Burst Format
iDirect Inroute Packet Format
Slot
User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

Unique
GB Demand Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB
Word
70

0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392

0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

125 Milli-second Frame (Typical) * Optionally Enabled

0.66 Ù 128 Byte (Small – 1kb) Block Turbo Product Code (TPC)
0.793 Ù 512 Byte (Large – 4kb) Block TPC
NOTE: Link Encryption Is Optionally Enabled. If enabled each IP packet
has an additional header, 2 to 9 bytes in length; (2 byte header plus 0-7
bytes of padding as required).
NOTE: VLAN tagging Is Optionally Enabled. If enabled each IP packet has
an additional header of 2 bytes.
Unique Word is 8 bytes pre-pended to the beginning of each slot; helps
hardware identify beginning of TDMA burst. Fixed, identifiable pattern.
12
 Communications Concepts
Inroute Packet Format

iDirect Inroute Packet Format

Slot
User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

Unique
GB Demand Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB
Word
70 (34%)

0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392 (20.7%)

0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

CIR RT Total
Priority CFI VLAN
Trigger Demand Demand ID
Demand Header
VLAN
Address Frame Tx Seq RxSeq KEY Initial Encoding
Offset
Header
Serial Num Type Num Num ID Vector

Link Layer Encryption

Header Header
Last Packet Seg Seg Queue Packet Segment Last
Flag ID Num Len ID ID ID Indic

PAD Header SAR Header

* Optionally Enabled

13
 Communications Concepts
Header Information - Details
TDMA Demand Header
CIR Trigger
• Indicates the presence of traffic which triggers a remotes CIR
Real Time Demand Metric
• Indicates the % of total demand which is classified as real time traffic.
Total Demand Metric
• Indicates the total demand requested from this remote.
Slot
User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

Unique Demand
GB Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB
Word Length
70

0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392

0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

CIR RT Total
Priority CFI VLAN
Trigger Demand Demand ID
Demand Header
VLAN
Address Frame Tx Seq RxSeq KEY Initial Encoding
Offset
Header
Serial Num Type Num Num ID Vector

Link Layer Encryption

Header Header
Last Packet Seg Seg Queue Packet Segment Last
Flag ID Num Len ID ID ID Indic

* Optionally Enabled PAD Header SAR Header

14
 Communications Concepts
Header Information - Details
Link Layer Header
Address (Serial Number)
• Functions as the satellite MAC
• All traffic is tagged with this destination (outroute) or source (inroute)
• Tied to the serial number stored in E2PROM on each remote (today)
• Will be dynamically assigned at acquisition time in the future.
Frame Type
• Specifies the meaning of each frame
–Control, Reliable Data (TCP), Unreliable Data Slot

Tx Sequence Number
User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

• Specifies the sequence GB

Unique
Word
Demand
Length
Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB

number of this link layer 70

frame if it’s reliable data 0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392

Rx Sequence Number 0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

• Specifies the sequence CIR RT Total

number of the last

Priority CFI VLAN
Trigger Demand Demand ID
Demand Header
VLAN
successfully received Address Frame Tx Seq
Serial Num Type Num
RxSeq
Num
KEY
ID
Initial Encoding
Vector Offset
Header

reliable link layer frame Link Layer Encryption

Header Header
Last Packet Seg Queue Packet Segment Last

* Optionally Enabled
Seg
Flag ID Num Len ID ID ID Indic

PAD Header SAR Header

15
 Communications Concepts
Header Information - Details
PAD Header
Last Segment Identifier
• Indicates if PAD packet is complete
Packet Identifier
• Identifier for the current PAD packet
Segment Identifier
Slot
• Identifier for the User Data (w/o SAR)

current segment Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

within the current GB Unique

Word
Demand
Length
Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB

PAD packet. 70

0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

• Utilized to 392
reconstruct the 0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1
original PAD
packet CIR RT Total
Trigger Demand Demand
Priority CFI VLAN
ID

Segment Length Demand Header

VLAN
Address Frame Tx Seq RxSeq KEY Initial Encoding Header
• Size of this Serial Num Type Num Num ID Vector Offset

Link Layer Encryption

segment in bytes Header Last Packet Seg Seg Queue Packet Segment Last
Header
Flag ID Num Len ID ID ID Indic

PAD Header SAR Header

* Optionally Enabled

16
 Communications Concepts
Header Information - Details
SAR Header
Queue Identifier
• Identifies QoS Service Level for packet
Packet Identifier
• Identifier for the current SAR packet
Segment Identifier
• Identifier for the current segment within the SAR packet.
• Utilized to reconstruct Slot

the original SAR packet User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical
Last Segment Unique Demand
Indicator
GB Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB
Word Length
70

• Indicates if this 0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

segment completes 392

a SAR packet. 0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

CIR RT Total
Priority CFI VLAN
Trigger Demand Demand ID
Demand Header
VLAN
Address Frame Tx Seq RxSeq KEY Initial Encoding
Offset
Header
Serial Num Type Num Num ID Vector

Link Layer Encryption

Header Header
* Optionally Enabled
Last Packet Seg Seg Queue Packet Segment Last
Flag ID Num Len ID ID ID Indic

PAD Header SAR Header

17
 Communications Concepts
Header Information - Details
Encryption Header
Key Identifier
• Serves as an index into the current key table.
• Facilitates dynamic key rolling capability.
Initialization Vector
• Serves as initialization vector into 3-DES algorithm
Encoding Offset
Slot
• Indicates the User Data (w/o SAR)

amount of Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

padding required GB
Unique
Word
Demand
Length
Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB

for this packet 70

Padding
0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392

• 0-7 Bytes of 0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

random padding
(CBC 3DES CIR RT Total
Trigger Demand Demand
Priority CFI VLAN
ID

Requirement) Demand Header VLAN

Address Frame Tx Seq RxSeq KEY Initial Encoding
Offset
Header
Serial Num Type Num Num ID Vector

Link Layer Encryption

Header Header
Last Packet Seg Seg Queue Packet Segment Last
Flag ID Num Len ID ID ID Indic

* Optionally Enabled PAD Header SAR Header

18
 Communications Concepts
Header Information - Details
VLAN Header
Priority
• Normal VLAN Priority
CFI
• Normal VLAN CFI bit
VLAN Identifier
• Normal VLAN Identifier
Slot
User Data (w/o SAR)

Physical iDirect Headers IP (User Data) +Encr + VLAN Error Correction Physical

Unique Demand
GB Link Layer PAD SAR* Encr* VLAN* IP Packet CRC FEC GB
Word Length
70

0.66 1 8 2 6 2 2 (2-9) (2) 2 44 1

392

0.793 1 8 2 6 2 2 (2-9) (2) 2 106 1

CIR RT Total
Priority CFI VLAN
Trigger Demand Demand ID
Demand Header
VLAN
Address Frame Tx Seq RxSeq KEY Initial Encoding
Offset
Header
Serial Num Type Num Num ID Vector

Link Layer Encryption

Header Header
Last Packet Seg Seg Queue Packet Segment Last
Flag ID Num Len ID ID ID Indic
* Optionally Enabled PAD Header SAR Header

19
 TDMA Time Plan Example

125 mSec Frame Length

Un-
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 80
used

Burstable Bandwidth

NetModem NetModem NetModem NetModem

500 mSec Frame Length

Un-
1 2 3 4 5 6 7 8 9 10 11 12 13 14 320
used

Burstable Bandwidth

NetModem NetModem NetModem NetModem

*Note: Frame Length is configurable. Frame Length, Transmission Rate and TPC block size,
determine available time slots and bandwidth per time slot.

20
 0.66 FEC – Configuration Example

718 kbps Upstream (TX) Rate

125* mSec Frame Length

Un-
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 80 used
138 2 2 2 2 64 64 35

½ Unique 1st Level Payload ½ Slot 80 (last slot) is the acquisition slot
GB Word GB Traffic Slot Guard and thus requires more bandwidth
1 8 1 Band = 2 bytes (<2x) and larger guard bands. This slot
128
is dedicated to remote acquisition only

C Block Size = 128 bytes

2nd Level Payload
Header R
C
FEC FEC = TPC 0.66
2 FEC = 128 * (1 - 0.66) = 44 bytes
8 74 44

P S
Useable Bandwidth =
A A User Data
D R 79 slots * 70 bytes * 8 bits = 353.92 kbps
125ms (= 8 frames per second)
2 2 70

All values shown are in bytes unless otherwise indicated

21
 0.66 FEC – Configuration Example

Each VSAT is guaranteed one slot out of 79 in the frame.

79 slots for traffic use
Slot 80 is the dedicated acquisition slot
• Acquisition time slot is slightly less than twice the bandwidth of a traffic slot
• Acquisition time slot also requires larger guard bands

Dynamic allocation will allow a VSAT to burst into unassigned slots

Slot = 4.48 kbps (353.92 kbps/79 slots = 4.48 kbps/slot) user data

With 20 VSATs in this network, the burst-able maximum usable

bandwidth is 264.32 kbps (59 remaining slots x 4.48 kbps/slot)
FEC overhead is given @ 34 % (1.00 - .66)*100
Total overhead is 50.8 % = (718 kbps -354 kbps)/718 kbps*100
iDirect overhead therefore <16 % (actually a bit more efficient)

Note: 125 ms is a nominal frame length, the exact length used for operation is
optimized to be slightly less, resulting in unused symbols/bytes in any time plan

22
 0.793 FEC – Configuration Example

718.750 kbps Upstream (TX) Rate

125* mSec Frame Length

Un-
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 21 used
522 2 2 2 2 64 64 49

½ Unique 1st Level Payload ½ Slot 21 (last slot) is the acquisition slot
GB Word GB Traffic Slot Guard and thus requires more bandwidth (2x)
1 8 1 Band = 2 bytes and larger guard bands. This slot is
512
dedicated to remote acquisition

C Block Size = 512 bytes

Header 2nd Level Payload R FEC FEC = TPC 0.793
C
FEC = 512 * (1 - 0.793) = 106 bytes
8 396 2 106

P S Useable Bandwidth =
A A User Data
D R 20 slots * 392 bytes * 8 bits = 501.76 kbps
125ms (= 8 frames per second)
2 2 392

23
 0.793 FEC – Configuration Example

Each VSAT is guaranteed one slot out of 21 in the frame

20 time slots for traffic use
Slot 21 is the dedicated Acquisition time slot
• Acquisition time slot is slightly less than twice the bandwidth of a traffic slot
• Acquisition time slot also requires larger guard bands

Dynamic allocation will allow a VSAT to burst into unassigned slots

Slot = 25.08 kbps (501.76 kbps/20 slots = 25.08 kbps)/slot user data

With 4 VSATs in this network, burst-able maximum is 401 Kbps (16

remaining slots * 25.08 kbps = 401 kbps)
FEC overhead is given @ 20.7% (1.00 - .793)*100
Total overhead is 30 % = (718 kbps - 502 kbps)/718 kbps*100
iDirect overhead therefore <9.3 % (actually slightly more efficient)

Note: 125 mSec is a nominal frame length, the exact length used for operation is
optimized to be slightly less, resulting in unused symbols/bytes in any time plan

24
Packet Flow in an iDirect TDMA Network
(Life of a Packet)
 Communications Concepts
Packet Flow in an iDirect TDMA Network

Network Management System,

iBuilder User Guide, Release 6.0.0

Source for Basic Architecture &

Protocol (in Appendices)

Included in Vol. II, IOM Training

Manual, (iBuilder User Guide)

Available on TAC web page,

‘Network Operator Documentation
Æ NMS’ link

Additional Application Throughput

Features Discussed

QoS Implementation Principles

Defined

26
 Communications Concepts
SAR – Segmentation and Reassembly

Packet Arrival Time

FTP Packets (1500 Byte)

5 4 3 2 1
RF Out
Dequeue b a 1

j i h g f e d c b a The Large FTP Packet

will delay voice in a
VoIP Packets (70 Byte) congested state
QoS Distributor

SAR not enabled

FTP Packets (1500 Byte)

6 5 4 4 4 4 3 3 3 3 2 2 2 2 1 1 1 1
RF Out
SAR Dequeue 1 d c b a 1

k j i h g f e d c b a As packets are divided

VoIP Packets (70 Byte) into equal sized
QoS packets, a voice packet
Distributor has to wait a maximum
of one burst.
SAR enabled

27
 Timeslot Feathering Allocation

Bandwidth allocated to R1

1 2 3 4 5 6 7 8 9 10 11 12 13 14 75

R1

VoIP Packets VoIP Packets VoIP Packets

Frame 1 Frame 2 Frame 3

Delay Delay

Significant variation in delay causes jitter.

VoIP Packets VoIP Packets VoIP Packets

Frame 1 Frame 2 Frame 3

Delay

Minimal variation in delay significantly reduces jitter.

28
 Communications Concepts
Upstream Packet Flow - Remote (TX) to Hub
Ethernet frames enter If enabled, processed
remotes LAN interface; 6 by 3DES module.
1
size up to 1514 bytes – Encrypts packet; adds
includes 14 byte header 2-9 byte header
NetModem II+ - Remote Site MAC Address recognized; If enabled, packet
2 7
Ethernet frame accepted segmented allowing
fine grain QoS control,
IPv4 TCP If ARP response, internal
3DES
(2 byte header)
5 Acceleration
tables updated. If IP packet,
(or cRTP) 6 Link Packets queued based
Encryption Ethernet header stripped 8
Quality of leaving IP packet for routing on a QoS service level
4 Service (QoS) Segmentation & held for distribution
Classifier 7 (And Route lookup performed
Reassembly, 3 9 Packs each packet into
using destination IP. Packet TDMA bursts efficiently
Network or SAR)
Address directed toward satellite
Translation Distributor Interface or internal stack Reliable stream for all
8
(NAT) TCP traffic. Adds 6 byte
Network Address Translation 10
3 TDMA header identifying this
IP (Router maintains translation table
Functions) 9 Packing unique remote to hub
if required
(PAD)
Address Packet ‘filtered’ & discarded 2 byte header with
or ‘classified’ by QoS service 11
Resolution iDirect 4 TDMA demand & other
Protocol 10 Link
Layer level setting & tagged (2 byte) QoS related info
(ARP)
TDMA Checked if TCP (accelerated) 12 FEC added, then TDMA
LLC 11 5
Transmit or UDP (cRTP processed); burst is buffered for
2
MAC otherwise passed through transmission by VSAT
RF
FEC
. Physical
RFT hardware
Ethernet
1 Physical 12 VSAT RFT
Hardware 12

29
 Communications Concepts
Upstream Packet Flow - Remote to Hub (RX)
TDMA bursts received by Checked if TCP (accelerated) iDirect Hub - Protocol Processor
Teleport/Hub RFT, then 7 or UDP (cRTP processed);
1
on to iDirect Hub Line otherwise passed through IPv4 TCP
Acceleration 7 3DES
Card (HLC) demodulator.
Route lookup performed (or cRTP) Link
FEC decoding processed; Decryption 6
against PP routing table.
packets forwarded (no Rx QoS
Packets routed to SAT Classifier) (Segmentation
2 Unmodified packets are interface or Upstream And)
Reassembly, 5
passed through to PP (gateway) Router
(no Rx NAT (or SAR)
via LAN ‘Tunnel’ layering 8
ARP adds correct module)
(no Rx
PP routes burst to destination & source Distributor)
correct receive stack for Ethernet MAC addresses. IP (Router
3 TDMA
this remote. Link Layer Packet then forwarded Functions)
Un-Packing 4
header removed directly to destination or
(PAD)
gateway (Upstream Router) 8
TDMA packing is undone Address
Resolution iDirect
4 and full packet is rebuilt Ethernet frames processed Link 3
9 Protocol
& passed up the stack & transmitted via eth0, Layer
(ARP)
Upstream LAN to correct
10 LLC
5 If enabled, SAR rebuilds destination 9
Ethernet
IP packet from constituent MAC (eth1) 2
Physical
segments & 2 byte QoS Ethernet (eth0)
header removed Upstream Physical
destination
10 T
6 If enabled, 3DES module U D
decrypts packet and iDirect Hub Line Card
N E
removes 2-9 byte header LLC LLC N M
MAC MAC E U
1 Teleport/Hub RF Ethernet L X
RFT Hardware 1 Physical FEC Physical 2

30
 Communications Concepts
Downstream Packet Flow - Hub (TX) to Remote
iDirect Hub - Protocol Processor
IPv4 TCP
Ethernet frames enter PP If enabled, packet
upstream LAN interface; 7
Acceleration 5 3DES 1 segmented allowing
(or cRTP) Link
size up to 1514 bytes – fine grain QoS control,
Encryption 6 includes 14 byte header
Quality of (2 byte header)
Service (QoS) 4 Segmentation MAC Address recognized;
Classifier
2 Packets queued based
(And Ethernet frame accepted 8 on a QoS service level
Reassembly, 7
(no Hub NAT & held for distribution
module) or SAR) If ARP response, internal
Distributor
tables updated. If IP packet, Reliable stream for all
8 Ethernet header stripped TCP traffic. Adds 6 byte
IP (Router 9
leaving IP packet for routing header identifying this
Functions) (no PAD 3
module on unique remote to hub
Route lookup performed
3 PP) using destination IP. Packet Ethernet frames are
Address 10
Resolution iDirect directed toward satellite ‘Tunnelled’ to the
Protocol Link 9 Interface or internal stack iDirect HLC for
(ARP) Layer
Packet ‘filtered’ & discarded transmission
LLC 4
2 Ethernet or ‘classified’ by QoS service Ethernet frames are
MAC
(eth1) level setting & tagged (2 byte) 11 transmitted via
Ethernet (eth0) Physical Teleport/Hub RFT
Physical 10 5 Checked if TCP (accelerated)
1 or UDP (cRTP processed); SCPC Outbound, or
T otherwise passed through Downstream carrier
iDirect Hub Line Card U M
N U If enabled, processed by
LLC LLC N X 6 3DES module. Encrypts
MAC MAC E packet; adds 2-9 byte header
RF Ethernet L
Physical FEC Physical 10
Teleport/Hub 11
11 RFT Hardware

31
 Communications Concepts
Downstream Packet Flow - Hub to Remote (RX)

SCPC Downstream carrier Network Address NetModem II+ - Remote Site

1 received, decoded & Translation maintains
demodulated by VSAT translation table if required
RFT as remote achieves IPv4 TCP
TDM Frame lock Route lookup performed 5 Acceleration 3DES
against remote’s routing (or cRTP) 4 Link
iDirect Link Layer receives table. Packets routed to Decryption
(no Rx QoS
2 packets for this remote. LAN interface or internal Classifier) (Segmentation
Link Layer header TCP/IP stack 3 And)
removed 6 Reassembly,
ARP adds correct Network (or SAR)
destination & source Address
3 If enabled, SAR rebuilds Translation
IP packet from constituent Ethernet MAC addresses. (NAT) (no Remote
segments & 2 byte QoS Packet then forwarded Distributor)
6 IP (Router
header removed directly to destination or
downstream Router Functions)
4 If enabled, 3DES module (no Remote
Ethernet frames processed Address
decrypts packet and 7 Resolution receive PAD)
removes 2-9 byte header & transmitted via remote
Protocol
8 LAN port to Downstream (ARP)
Checked if TCP (accelerated) LAN to correct destination iDirect
5 or UDP (cRTP processed); LLC
2 Link
7 Layer
otherwise passed through
MAC RF
FEC
. Physical
Ethernet
Downstream 8 Physical
destination

1 VSAT RFT
Hardware 1

32
Network Layer
IP Protocol
Layer 3
 Communications Concepts
Internet Protocol (IP)
OSI Model
OSI
Layer
7 APPLICATION Application (News, Email, Telnet, NMS etc)

6 PRESENTATION HTML

5 SESSION HTTP
The Network layer provides the functional and
procedural means of transferring variable length
4 TRANSPORT TCP/UDP data sequences from a source to a destination
while maintaining the quality of service requested
by the Transport layer. The Network layer performs
3 NETWORK IP network routing and error control functions.
LLC Sublayer Link Layer Control
2 Link Layer
MAC Sublayer Ethernet HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
MMF, SMF
TCP Transmission Control Protocol
1 Physical UTP, Coax
UDP User Datagram Protocol
Physical Media RF Frequency
IP Internet Protocol
LLC Link Layer Control
STS Synchronous Transport System
STM Synchronous Transport Module
MMF MultiMode Fiber
UTP Unshielded Twisted Pair

34
 Communications Concepts
Internet Protocol (IP)

IP Protocol
Specifies Best Effort delivery
Unreliable packet delivery
No retransmission of IP packets
Packets discarded if network resources are insufficient
Called connectionless because Source and Destination IP
Facilities do not handshake
All packets are treated independently
Packets may take different paths through network
Specifies the format of all data as it passes across the
internet
IP Software performs the routing function

35
 Communications Concepts
Internet Protocol (IP)

Connectionless Packet Delivery

Provides packet delivery service to Transport Layer protocols
IP provides common, consistent, universal addressing
IP defines set of rules that embody packet transmission & delivery
IP rules specify how
Routers should process packets (Routing, ToS, precedence,
fragmentation)
Specifies when and how to generate error messages (ICMP)
Conditions that govern discard and/or duplication of packets
(multicast)
TCP and UDP
IP Packets are the delivered packets
IP Packets are the single packet that traverses the network
In a routed network Layer 2 packets live only point-to-point
Ethernet Packets live only between adjacent ports

36
 Communications Concepts
iDirect Hub Logic Diagram/Subnets
Upstream

Upstream Router is the gateway

Upstream Switch 192.168.0.62

Tunnel Switch 192.168.0.126

ROUTER
device for all network throughput Eth0 interface IP: 192.168.0.1
Eth1 interface IP: 192.168.0.65

Network (User) Traffic

M&C (NMS) Traffic

Two subnets assigned for hub Win2000 PC for NMS

GUI (typically CFE)
Chassis S/N: 00021 ,

components
IP: 192.168.0.2
Network 1 HLCs
Slot 9 Rx Only S/N: II+.7994 ,
‘Upstream’ & ‘Tunnel’ Utility PC
IP:
Slot 10 Tx/Rx S/N:
192.168.0.101
II+.7979 ,

Typically full class ‘C’ for each; Eth0 IP: IP: 192.168.0.100
192.168.0.dhcp Network 2 HLCs

minimum .248 subnet mask

Slot 1 Rx Only S/N: II+.15370 ,
IP: 192.168.0.111
Slot 2 Tx/Rx S/N: II+.15385 ,
IP: 192.168.0.110

Upstream subnet = network traffic Slot 5 Standby S/N:

IP:
II+.15396 ,
192.168.0.112
Network 3 HLCs
Slot 13 Tx/Rx S/N: M1D1.13088 ,

Tunnel subnet = M & C traffic NMS Online

Eth0 IP: 192.168.0.3
IP:
Slot 14 Rx Only S/N:
192.168.0.120
M1D1.13147 ,
IP: 192.168.0.121
Only Hub Line Cards IP’d with
Tunnel subnet address NMS Backup PP Blade
Eth0 IP: 192.168.0.4 Eth0 IP: 192.168.0.5
HLC default Gateway = Upstream Eth1 IP: 192.168.0.66

Router Tunnel Interface PP Blade

Eth0 IP: 192.168.0.6
Eth1 IP: 192.168.0.67

Subnet A (Upstream- Eth0) Subnet B (Tunnel-Eth1)

192.168.0.0/26 192.168.0.64/26

37
 Transport Layer
Transmission Control Protocol
(TCP)
Layer 4
 Communications Concepts
Transmission Control Protocol (TCP)
OSI Model
OSI
Layer
7 APPLICATION Application (News, Email, Telnet, NMS etc)

6 PRESENTATION HTML

5 SESSION HTTP

The ‘Transport’ layer provides transparent

4 TRANSPORT TCP/UDP transfer of data between end users. It
ensures complete data transfer.

3 NETWORK IP TCP – Connection oriented Guaranteed Delivery

UDP – Connectionless not guaranteed delivery
LLC Sublayer LL Control
2 Link Layer
MAC Sublayer Ethernet HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
MMF, SMF
TCP Transmission Control Protocol
1 Physical UTP, Coax
UDP User Datagram Protocol
Physical Media RF Frequency
IP Internet Protocol
LLC Link Layer Control
STS Synchronous Transport System
STM Synchronous Transport Module
MMF MultiMode Fiber
UTP Unshielded Twisted Pair

39
 Communications Concepts
Transmission Control Protocol (TCP)

TCP is a Connection Oriented protocol

Source and Destination MUST agree to the transmit and

receive information PRIOR to the transfer of user traffic

Provides guaranteed end to end delivery

Destination must agree to receive the information

Similar to a standard telephone call

All transmissions are acknowledged

Retransmission is REQUIRED if acknowledgement is not

received
in the event of a lost or corrupted packet

40
 Communications Concepts
Transmission Control Protocol (TCP)

TCP Provides the following functions

Mechanism for 2 machines to initiate an information transfer
Procedures to agree when transfer is complete
Specifies the format of the information
Specifies acknowledgements that the information was received
Specifies method to ensure information was received correctly
Specifies how a machine distinguishes between multiple
destinations
Specifies how to recover from errors, lost & duplicated packets
Flow Control
TCP & IP operate over dial-up, LAN, Optic, high & low speed WANs
Satellite links (if inherent of ‘round-trip’ latency can be overcome)
Successfully done when required acknowledgements are ‘spoofed’

41
 Communications Concepts
Transmission Control Protocol (TCP)

TCP Multiplexes and Demultiplexes data to/from applications

Must be able to distinguish data flows between destinations
TCP uses Port IDs & destination IP address to distinguish flow
TCP Port is a queue into which TCP protocol places datagrams
TCP uses connection abstractions
Destination Port
Source Port
Host Address:Port and/or Source Address:Port pairings
Source (65.168.20.1:port 100) – Destination (10.10.200.1:port 200)
• Source and Destination pairing to identify a data flow
Requires only one local port to accommodate many data flows for
many local applications

42
 Communications Concepts
Transmission Control Protocol (TCP)

TCP Connection Establishment

Host A Router 1 Host B

TCP TCP/UDP TCP

IP IP IP
LLC LLC LLC LLC LLC LLC
Ethernet Ethernet Ethernet Ethernet Ethernet Ethernet

UTP/STP UTP/STP UTP/STP UTP/STP UTP/STP UTP/STP

MMF/SMF MMF/SMF MMF/SMF MMF/SMF MMF/SMF MMF/SMF

Port 1 Port 2 Port 1 Port 2 Port 1 Port 2

SEND SYNC
RECV SYNC
SYNC bit: Set SYNC bit: Set
Seq Num: Asn Seq Num: Asn
ACK bit: NOT Set ACK bit: NOT Set
RECV SYNC SEND SYNC
SYNC bit: Set SYNC bit: Set
Seq Num: Bsn Seq Num: Bsn
ACK: Asn+1 ACK: Asn+1

SEND ACK RECV ACK

Seq Num: Asn1 Seq Num: Asn1
ACK: Bsn+1 ACK: Bsn+1

43
 Communications Concepts
User Datagram Protocol (UDP)

User Datagram Protocol (UDP)

Connectionless Service

Best effort packet delivery service

How good is “best”?

Not guaranteed delivery; no acknowledgements ever provided

Source sends information without respect to agreement by

destination to receive the information

Similar to an announcement over a public address system

Transmissions are unacknowledged
If not ‘received’, missing transmissions are never resent

44
 Communications Concepts
TCP Acceleration

TCP requires destination to acknowledge receipt of packet

This can result in delay when Satellite ‘round-trip’ LATENCY
(~500msec) is introduced into the data path

iDirect solution acknowledges TCP packet receipt for the

machine (or ‘Host’) that requested the information
Remote site thinks the iDirect customer has received packets
and sends more data
Sometimes referred to as “Spoofing” elsewhere in the industry

iDirect remote only tells Hub if it did NOT get a data packet
Faster data transmissions
Increases overall data throughput
Maximizes available bandwidth

45
 Communications Concepts
TCP Acceleration

TCP Acceleration

Server PC Server Hub NM II PC

SYN SYN
SYN-ACK SYN-ACK
Request Request
Data Data
Data Data
ACK ACK ACK
Data Data
Data Data
ACK ACK ACK
Data Data
Data Data
ACK ACK
ACK
Data Data
Data Data
ACK ACK ACK
Data Data
Data Data
ACK ACK ACK

Data Data
Data Data
ACK ACK ACK
FIN FIN

46
 Communications Concepts
TCP Acceleration

3-Way Handshake Acceleration

TCP Acceleration

Server PC Server Hub NM II PC

SYN SYN
SYN-ACK 3 Way SYN-ACK SYN-ACK
3 Way
Request Handshake Request Request
Handshake
Acceleration
Data
Data
ACK
TCP ACK ACK
Acceleration
FIN
FIN

47
 Communications Concepts
iDirect Network Accelerator (NA)

48
 Communications Concepts
iDirect Network Accelerator (NA)

iDirect Network Accelerator

NA was designed to overcome the limitations of TCP when operating
over ‘third party’ VPN-enabled satellite networks (NOT 3DES or AES)
Simultaneously supports end-to-end QoS for real-time applications,
such as Voice-over-IP, or VoIP, streaming video, etc.
The iDirect Network Accelerator accomplishes these goals by
Providing a configurable TCP acceleration module, as well as a set of
QoS capabilities, that . . .
• allow vital QoS information to cross into the encrypted portion of the satellite
network.
• enables customers to deploy networks that are both encrypted & accelerated
over satellite.
Each Network Accelerator is configured with one or more peer NA’s.
Possible to configure direct remote-to-remote NA peers allowing the
deployment of a pseudo-mesh topology.

49
Quality of Service (QoS) &
Traffic Engineering
 Communications Concepts
Quality of Service (QoS)

Quality of Service is a technique for providing CONSISTENT delivery of

traffic across a network
QoS effort is to impart delay on data flows that can tolerate delay
Reduce delay on those flows that can not tolerate delay

Quality of Service is required due to the differences of traffic

characteristics such as
Real-time applications like VoIP and streaming video
Real-time DATA applications
nonReal-time data applications
Priority users - QoS can be applied to a connection rather than to a packet
Applies to all packets in that connection (data flow)

QoS is implemented through a consistent method of granting first (or

early) access to the TRANSMIT Queue (Class Based Weighted Fair
Queuing – CBWFQ algorithm)

Type of Service (TOS) applies to a specific packet (as in IP header

field)

51
 Communications Concepts
Quality of Service

Typically required to support Service Level Agreements (SLA)

Provides ability to distinguish between different traffic types

Designed to enable one user to be favored over another

Implemented through the management of resources such as

Bandwidth allocation
Packet Loss, reliability
Latency and jitter

Will not eliminate or reduce network congestion

A heavily over-subscribed network may simply require more
bandwidth to be allocated
QoS capabilities will not improve service if host is overloaded

52
 Communications Concepts
Quality of Service

Application QoS - Enables real-time classification, and

prioritization of data traffic

Traffic prioritization can be performed using

Source and/or Destination IP Address LAN Traffic

Source and/or Destination IP Subnet

Source and/or Destination Port Number Service
Queues

Source and/or Destination Port Range

Diffserv and ToS Bits
VLAN ID
Protocol (TCP, UDP, HTTP, ICMP, IGMP)
Satellite
Network
Configurable Queue Lengths For Each Service Level

A percentage of bandwidth assigned to each service level

Configurable drop policy

Traffic can be rate limited in both directions

53
 Communications Concepts
Network QoS

Hierarchical Prioritization Capability

Most Flexible QoS Capability in Industry
Most Comprehensive Prioritization Capability
Network QoS - Coupled with CIR guarantees service at the
network level
Prioritize real-time traffic over non-real-time traffic across
shared satellite bandwidth
Allocates traffic demand for each remote appropriately

Network

Inroute 1 Inroute 2 Inroute 3 Inroute 4

Prioritization rt nrt rt nrt rt nrt rt nrt

rt - Real-
Real-time Traffic (e.g. VoIP)
nrt - Non-
Non-Real-
Real-time Traffic (e.g. FTP)

Prevents non real time traffic from one remote impacting

Real Time Traffic on a different and unrelated remote

54
 Communications Concepts
Quality/Class/Type of Service

Quality of Service
Capability to provide delivery of information across a network
connection with consistent performance characteristics
Class of Service
The ability to establish categories of QoS (Gold, Silver, Bronze)
A method of specifying and grouping applications and traffic
into QoS categories
Type of Service
Sometimes referred to as IP Precedence
Generally unused, but important QoS setting for iDirect Network
Accelerator (NA)
Provides the ability to indicate to network devices that this packet
should be afforded highly reliable transport (no drops) or low delay

55
 Communications Concepts
Traffic Engineering

Traffic Engineering designed to optimize operation

of networks

Traffic Engineering is composed of:

Measurement
Reporting
Control

Traffic Engineering is the umbrella terminology of

network QoS

Traffic Engineering is classified as:

Traffic Oriented
Resource Oriented

56
 Communications Concepts
Traffic Engineering

Traffic Oriented
Quality of Service related issues
Packet Loss Minimization
Delay Minimization
Throughput Maximization
Enforcement of Service Level Agreements

Resource Oriented
Ensure areas of Network are properly utilized
Limit the Under / Over Utilization of network areas
Optimum Bandwidth Utilization
Congestion Control

57
 Communications Concepts
Traffic Engineering

Congestion Control is the most important objective of Traffic

Engineering
Permits enforcement of service level agreements

Traffic Engineering is designed to limit long duration Congestion

Transient Congestion not addressed

Primary causes of network congestion

Network resources insufficient to handle the load
Traffic streams are inefficiently mapped to available resources

58
 Communications Concepts
Traffic Engineering

Insufficient network resources addressed by

Capacity Expansion
Flow Control Techniques
• Rate Limiting
• Router Queue Management
• Window Flow Control

Efficient mapping of traffic flows addressed by Traffic

Engineering Architecture and load balancing policies

Traffic Engineering policies are implemented through other

specifications
Reservation Protocol (RSVP)
Differentiated Services (Diff-Serv)

59
Data Communications Concepts

*** Thank You ***