User Manual

Packet switched services
99-137719-D Confidential - For internal use 7-19
7777
Data interfaces
7.6 Packet switched services
The following subsections introduces the packet switched services supported by the
BGAN XL Radio Module and describes how they are controlled.
7.6.1 Brief introduction to PDP contexts and Traffic Flow Templates
A PDP context is a data pipe towards the Internet through the BGAN network. PDP
contexts come in two types; primary and secondary, and are grouped in families. A
PDP family consists of exactly one primary PDP context and zero or more secondary
PDP contexts. The total number of PDP contexts (primary as well as secondary) in all
families must not exceed 11. The primary PDP context in a PDP family holds the IP
address and APN name assigned from the Core Network.
Inside a given PDP family, PDP contexts are equipped with Traffic Flow Templates
(TFTs), which control what data flows in which PDP context, based on
source/destination IP address and/or port. The TFTs are transmitted across the BGAN
air interface so the core network knows what data goes where, in the direction of core-
network-to-terminal. Maximum one PDP context in a PDP family can be without a TFT,
and a maximum of eight TFTs per PDP context are supported. TFTs can be configured
by AT commands (see section 7.6.5 on page 7-22).
7.6.2 The PPPoE-to-PDP-family mapping
To initiate a primary PDP context (and thereby a PDP family) a PPPoE connection into
the RM is established. This can be done multiple times, for multiple PDP context
families. The PPPoE connection can either start in the AP or outside the AP, at an end
user computer, with the AP just passing the PPPoE connection through. The case with
the PPPoE connection starting in the AP is illustrated in Figure 7-2 on page 7-20. Both
cases appear identical from a RM point of view.
7.6.3 PPPoE service names
The PPPoE Service Name indicates which connection type is established, with regard to
QoS. They are meant as a shorthand version for commonly used connection types. The
service names and their parameters are described in Table 7-16. A connection can be
made using a service name and used as is, or this can be the starting point for a
connection which is then later manipulated via AT commands.
Alternatively, if more fine grained control is desired, the service name can be a string
of AT commands that specifies the connection parameters.
Example:
XBB:AT+CGDCONT=2,ip,bgan.inmarsat.com;+CGEQREQ=2,3