Manualshelf

User Manual

ManualsBrandsSensize ManualsElectronicsSensize Tracker v2 CAT-M
121122123124125126127128129130
Table Of Contents
SARA-R4 series-AT commands manual
UBX-17003787 - R16
13Packet switched data services
Page 128 of 401
13Packet switched data services
13.1PDP contexts and parameter definition
13.1.1Primary and secondary PDP contexts
A PDP context can be either primary or secondary. In LTE, PS data connections are referred to as EPS bearers:
EPS bearers are conceptually equivalent to the legacy PDP contexts, which are often referred to for sake of
simplicity. Similarly to a PDP context, the EPS bearer can be a default (primary) or dedicated (secondary) one.
The initial EPS bearer established during LTE attach procedure is actually a default EPS bearer. A secondary
PDP context uses the same IP address of a primary PDP context (the usual PDP context activated e.g. via
dial-up). The Traffic Flow Filters for such secondary contexts shall be specified according to 3GPP TS 23.060
[10].
The typical usage of the secondary PDP contexts is in VoIP calls, where RTP (speech) packets are conveyed on
one PDP context (e.g. the primary one) with a given QoS (e.g. low reliability) whereas SIP signalling is routed on
a different PDP context (e.g. the secondary one, with the same IP address but different port numbers) with a
more reliable QoS.
A Traffic Flow Template (i.e. a filter based on port number, specifying relative flow precedence) shall be
configured for the secondary context to instruct the GGSN to route down-link packets onto different QoS flows
towards the TE.
PDP context type Activation procedure
Primary Used to establish a logical connection through the network from the UE to the GGSN with a
specifically negotiated Quality of Service (QoS).
The UE initiates the PDP context activation: it changes the session management state to active,
creates the PDP context, obtains the IP address and reserves radio resources. After the activation,
the UE is able to send IP packets over the air interface.
Secondary Used to establish a second PDP context with the same IP address and the same APN as the
primary PDP context.
The two contexts may have different QoS profiles, which makes the feature useful for applications
that have different QoS requirements (e.g. IP multimedia); QoS is applied based on port number
addressing.
SARA-R4 / SARA-N4
Mobile originated activation of secondary PDP contexts is not supported.
13.1.2Multiple PDP contexts
Two PDP context types are defined:
• "external" PDP context: IP packets are built by the DTE, the MT's IP instance runs the IP relay function only;
• "internal" PDP context: the PDP context (relying on the MT's embedded TCP/IP stack) is configured,
established and handled via the data connection management AT commands.
Multiple PDP contexts are supported. The DTE can access these PDP contexts either alternatively through
the physical serial interface, or simultaneously through the virtual serial ports of the multiplexer (multiplexing
mode MUX), with the following constraints:
• Using the MT's embedded TCP/IP stack, only a internal PDP context is supported. This IP instance supports
up to 7 sockets;
• The sum of active external and internal PDP contexts cannot exceed the maximum number of active PDP
contexts indicated in the <cid> parameter description;
• Using external PDP contexts via dial-up, it is usually possible to have at most 3 PPP instances
simultaneously active.
SARA-R404M / SARA-R410M-01B / SARA-R410M-63B / SARA-R410M-73B / SARA-R410M-83B / SARA-N4
Using external PDP contexts via dial-up, it is possible to have a PPP instance active.
SARA-R410M-02B / SARA-R410M-52B / SARA-R412M