User's Manual

AVIATOR 200S/700S
User Manual
COBHAM PRIVATE
Document:
98-158752
Page:
54 of 105
Revision:
B
Level:
COM
CC:
1
(T: 99-161853-F)
Table 9-1: PPPoE Service Name Options
IP Service
Service Name Option
Description
IP Background
SBB:BACKGROUND
Places a Primary Background PDP Context
8 kbps Streaming
SBB:STREAM8K
Places a Primary Streaming class PDP Context at the
data rate of 8 kbps.
16 kbps Streaming
SBB:STREAM16K
Places a Primary Streaming class PDP Context at the
data rate of 16 kbps.
32 kbps Streaming
SBB:STREAM32K
Places a Primary Streaming class PDP Context at the
data rate of 32 kbps.
64 kbps Streaming
SBB:STREAM64K
Places a Primary Streaming class PDP Context at the
data rate of 64 kbps.
128 kbps Streaming
SBB:STREAM128K
Places a Primary Streaming class PDP Context at the
data rate of 128 kbps.
BGAN X-Stream
SBB:XSTREAM
Places a Primary Streaming class PDP Context with a
dedicated 200 kHz bearer. Elevation angle dependant,
with max data rate of 512 kbps.
HDR Half symmetric
N/A
No SBB Option Name defined. Use AT-Commands.
HDR Full symmetric
N/A
No SBB Option Name defined. Use AT-Commands.
HDR Half asymmetric
N/A
No SBB Option Name defined. Use AT-Commands.
HDR Full asymmetric
N/A
No SBB Option Name defined. Use AT-Commands.
9.2.4 Connection Control using TELNET
9.2.4.1 Primary PDP Contexts
Primary PDP contexts must be created through the establishment of a PPPoE connection between the
AVIATOR S system and the Client.
9.2.4.2 Secondary PDP Contexts
Secondary PDP contexts are used if differentiated QoS characteristics are desired for different traffic types.
Although they share the APN and IP address of the primary PDP context to which they have been associated,
each secondary PDP context may be specified to have a different QoS. A Traffic Flow Template (TFT) must be
specified for each secondary PDP context to inform both the network and the Satcom System about the
different types of traffic filter to each PDP context. All traffic that is not explicitly filtered (tied) into a secondary
PDP context is sent via the associated primary PDP context by default. Different traffic types are typically
identified by application (strictly protocol type), although filtering by IP address and TCP/UDP port numbers is
also possible.
Secondary PDP Contexts and associated Traffic Flow Template (TFT) may be created, modified, activated and
de-activated using the out-of-band control interface.