BGAN 9201 User Manual
93
PDP
C
ONTEXTS
O
VERVIEW
PDP
C
ONTEXTS
–
P
RIMARY AND
S
ECONDARY
Resource management for BGAN is based on PDP contexts, or connections. This means that in
congested networks each user needs his or her own context to ensure a fair allocation of
bandwidth from the network. Therefore, the Satellite Terminal creates a PDP context for each
connected computer that has traffic to send over the network. The multiple contexts can be
primary or secondary.
Primary contexts can connect to different APNs each with an individual username and
password. This is useful because each APN will only support a single set of subscribed Quality
of Service (QoS) values.
Primary contexts each get their own global IP address.
The total number of primary and secondary contexts that the Satellite Terminal can support is 11.
For example, it can support 5 primary and 6 secondary contexts, but not six primary and 6
secondary contexts. There is only a single primary context assigned to each computer
connected to the Satellite Terminal.
You can configure the Satellite Terminal to enable or disable automatic context activation. Even
if automatic context activation is used, you can still manually control contexts for flexibility and
exception conditions.
Primary Context
The Satellite Terminal creates a primary context with the entered information. If a primary
context already exists for your local IP address, you have to disconnect the current context
before creating the new one. This could happen if a context was created automatically and the
user wants to change to a different APN or QoS. Your BGAN LaunchPad or Web UI indicates
whether the context is successfully created or displays any errors. LaunchPad or Web UI also
allows you to disconnect any contexts.
Secondary Context
Secondary contexts can be set-up from the BGAN LaunchPad, and must always be associated
with an existing primary context. Secondary contexts are used when multiple applications on
your computer require different types of contexts.
Each secondary contexts requires a Traffic Flow Template to be configured, which defines how
the data for the secondary context should be routed. This is done through the BGAN
LaunchPad.
IP
A
DDRESSING
Connections between each TE and the terminal are achieved with private IP addresses, and
between the terminal and the BGAN network with global addresses.
Private addresses are dynamically assigned by the DHCP server in the terminal, starting
from192.168.128.101 and up to 192.168.128.199 if the TE is configured to obtain an IP address
automatically.
You can also manually configure the IP address of the TE with the operating system‟s
administrative tools. See the Automatic Context Section for the range of static and dynamic
addresses that can be used.
The global address of the terminal is assigned by the Network Service Provider, and can be
either static or dynamic. Dynamic global address configuration is automatically carried out by
the mechanism in the terminal that activates contexts. Static global addresses must be setup
with your Network Service Provider in advance.
