Documente Academic
Documente Profesional
Documente Cultură
1
Chapter 1
GPRS Outline
2
GPRS
Objectives
On completion of this chapter the student will be able to:
Explain the difference between Circuit and Packet switching.
State how Virtual Circuits are created.
Explain the impact of Industry convergence toward Internet Protocol (IP).
Explain the GPRS Network Architecture, its functions plus the mobile station classes.
Describe the Packet Data Channels and their organization and meaning for GPRS.
Explain the different coding schemes.
3
GPRS
Industry Convergence
Voice and data are converging and starting to be carried on the same networks, but opinions vary
on how quickly this is happening and what impact it will have on the IT and telcos. Businesses are
wondering what benefits it will bring and how soon they should add voice to their data networks.
Today the volume of data in telecomms networks has surpassed voice, Within 4 years the big US
telcos are predicting that 99% of telecomms traffic will be data. Already there have been many
merges, acquisitions and alliances spanning telecomms and IT as leading companies jostle for
position, once such example is the partnership between Motorola & Cisco.
Many of the recent merges and acquisitions have been brought about by telecomms equipment
companies buying up the IT companies that make Internet Protocol (IP) telephony products. These
products allow data to be carried cheaply over networks based on the IP protocol used on the internet.
They can also be used to carry Voice over IP (VOIP) by converting it into small packets of data. In this
way more voice calls can be sent down a single line. Examples of such acquisitions include Alcatel
buying Xylan, Nortels purchase of Bay Networks, Lucent acquiring Ascend and Nokia buying Ipsilon.
Some of the mission elements include:
Voice gateways
End to end control
QoS support (except when sent over another standard e.g. ATM)
Network management facilities
One of the main benefits to the customer is that of reduced network infrastructure costs because
there will be no need for separate data and telecomms networks.
4
GPRS
Industry Convergence
Computer Media
internet access
electronic mail
streaming audio
video on demand
real time images
multimedia Mobility
interactive video services
TV/Radio / Data contribution
mobile computing High speed
services
& distribution
IP
Mobility
Mobility Personal
Wideband services
services
Telecommunication
ISDN services
video telephony
wideband data services
5
GPRS
6
GPRS
7
GPRS
Circuit Switching
The diagram shows separate paths (circuits) A-B and A-C that are created through a Circuit
Switched Data Network (CSDN). In this example, the paths are 64kb/s channels (timeslots)
provided within an E1 TDM frame that operates at 2.048 Mb/s; the timeslots are switched
at the switching nodes in order to create the required paths.
The circuits are permanently provisioned and operate at fixed data rates (64kb/s);
Nx64kb/s circuits could also be provisioned for higher bandwidth applications. Note
that a duplex path (i.e. A/B and B/A) is provided.
Circuit switching takes place at the OSI physical layer, and there is no provision for
error control or flow control. However, circuit switched paths are protocol transparent
- they provide basic pipes for transmission.
Circuit switched paths are generally suitable for applications that require a fixed, short delay
e.g. voice and video. The bandwidth available is permanently dedicated to the circuit and
the paths are non-blocking. However, this is wasteful for many data applications which are
bursty by nature, or which involve a short request / long response.
8
GPRS
Circuit Switching
A S S C
CSDN
9
GPRS
Packet Switching
In a Packet Switched Data Network (PSDN), data to be transmitted is first segmented by the source
DTE into message units called packets. Each packet includes the network addresses of the source
and destination DTEs. On receipt of each packet, the Packet Switch Exchange (PSE) stores it while
inspecting the destination address; each PSE has a routing table specifying the outgoing link(s) to be
used for each destination network address. The PSE then forwards the packet on the appropriate
link at the rate of that link. This method of working is known as store-and-forward.
A number of packets may arrive simultaneously at a PSE on different incoming links for
forwarding on the same outgoing link. Packets may therefore experience unpredictably long
delays. (To prevent this, a maximum length is specified for each packet).
The PSDN has a meshed topology that offers multiple alternate routes for packets. In
the diagram, there are two alternate routes between any pair of PSEs. The PSDN
therefore provides a resilient networking service.
As packet networks use store-and-forward, the two communicating DTEs can have different access
speeds to the network. The transmission links between PSEs are better utilised because users only
occupy bandwidth when data is being sent and a number of such users can therefore "share" the
available transmission bandwidth. This technique is known as statistical multiplexing - a statistical
gain is achieved because it is unlikely that all users will be transmitting at the same time.
On packet switched networks, error control and flow control are performed on each link. Error
control ensures that packets are delivered error-free and in sequence, and flow control provides
a method of reducing congestion during busy periods. Overheads for these functions are carried
by each packet and employed by each PSE at OSI Layers 2 and 3.
Packet switching can achieve equipment economies because many DTEs can be
connected to a single PSDN access equipment.
Packets switching matches the characteristics of many data applications (occasional, bursty transfer of
data). Its statistical nature means that it is efficient. It does not offer a constant, low-delay performance
and is not therefore suitable for delay sensitive applications e.g. voice and video.
10
GPRS
Packet Switching
a c
B Data Packet where:
c = destination address
PSE a = source address
PSDN
a c
a b a c
PSE PSE
A b c C
a d
PSE
Higher D Higher
Layers Layers
L3 L3 L3 L3 L3
L2 L2 L2 L2 L2
Physical Physical Physical Physical Physical
11
GPRS
Datagrams
The datagram service is normally used for the transmission of short, single-packet messages.
Each packet that enters the network is treated as a self-contained entity with no relationship
to other packets. The packets can be therefore be forwarded over different routes to the
same destination. Datagrams provide a connection-less service.
Virtual Circuit
The virtual circuit service is used when a message contains multiple packets. It
is a connection-oriented service.
Before any data packets are sent, the source DTE sends a call request packet to PSE1 (see
diagram) containing the network address of the destination DTE and a reference number called
the Virtual Circuit Identifier (VCI). PSE 1 notes the VCI and forwards the packet through
the network according to the information contained in its routing table. It assigns a new VCI
to the route PSE1 - PSE2, and updates its routing table as shown.
At PSE2, another VCI is assigned to the call request packet before it is forwarded on the outgoing
link to the destination DTE. Assuming that the call is accepted, an appropriate response packet
is returned to the calling DTE. At this point, a virtual circuit (VC) exists between the two DTEs.
During the subsequent data transfer phase, all data packets relating to the call DTE1 - DTE2
are assigned the same VCIs along the virtual circuit. In this way, the source and destination
DTEs can readily distinguish between packets arriving on the same link that relate to different
calls - multiple calls are thereby multiplexed on to the same link.
All packets take the same route across the network and should therefore arrive in sequence. The
network addresses are only required in the initial call request and call accept packets.
12
GPRS
PSE1 PSE2
1 2 1 2
DTE1 DTE2
VCI(1) VCI(2) VCI(3)
Virtual Circuit
13
GPRS
14
GPRS
G-Interface
HLR
D-Interface
D-Interface
A-Interface
B-Interface B-Interface
E-Interface
BTS
BSC MSC G-MSC
Air interface
F-Interface
EIR
15
GPRS
BG (Border Gateway)
The BG is required for inter-PLMN packet data traffic.
CG (Charging Gateway)
The CG collects charging data records for packet switched traffic.
GPRS Interfaces
All interfaces between GPRS specific network elements are packet-switched. However,
the interfaces between the SGSN or GGSN on one hand and the HLR, VLR, EIR
or MSC on the other hand are based on SS7.
Note that the Gs-interface and the Gc-interface are optional.
16
GPRS
VLR HLR
Abis-Interface
Gr-Interface
Gs-Interface
Gc-Interface
Gi-Interface
Gb-Interface Gn-Interface
BSC Packet Data Network
BTS PCU SGSN GGSN
Air interface
(IP/PPP)
Ga-Interface
Gd-Interface
Gn-Interface Gp-Interface
CG
Ga-Interface
SGSN BG BG Foreign
SMS-G-MSC Gp-Interface PLMN
SMS-IW-MSC
17
GPRS
18
GPRS
ta
da
d
he
itc
w
it-s
i cu
C
e
am
TR
AU-Fr
TRAU
BSC
TR G
AU DS
-F
ra
BTS me
PCU
Pa
cke
t- sw
it ch
ed
da
ta
19
GPRS
20
GPRS
RLC RLC
MAC MAC
PCU
21
GPRS
22
GPRS
PCU GGSN
SGSN
PCU GGSN
PCU GGSN
23
GPRS
24
GPRS
GPRS-Mobility Management
VLR
HLR
SGSN HLR
HLR
VLR
25
GPRS
26
GPRS
GPRS-Session Management
PDP-Context Activation
Modification
Deactivation
27
GPRS
28
GPRS
Ciphering
29
GPRS
30
GPRS
$
PLMN
Packet
GGSN
$ SGSN Data Network
Charging
Gateway
31
GPRS
V.44
V.44 is an alternative data compression algorithm in addition to V.42bis. V.44 has originally been
developed by the company Hughes Network Systems (HNS) in the US and was proposed as
more powerful alternative to V.42bis in the year 1999 to international standards bodies ( ITU-T).
The ITU-T adopted this new compression algorithm as V .44 which offers 12% - 230% better
compression performance and therefore higher throughput rate than V.42bis.
32
GPRS
or
V.44
33
GPRS
34
GPRS
RFC 1144 or
RFC 2507
35
GPRS
36
GPRS
PLMN
GGSN
37
GPRS
38
GPRS
SGSN
Packet
SGSN GGSN Data Network
SGSN
39
GPRS
40
GPRS
$ Packet
SGSN GGSN Data Network
$
$ $
Charging
Gateway
41
GPRS
42
GPRS
Belonging to
the PLMN
DNS DHCP
radius
Internet/Intranet
DHCP A GGSN
Internet
DNS
radius ISP function
(with DNS)
PLMN
B GGSN
GGSN
GGSN
Belonging to
an ISP C
Intranet of Volume
Customer
DNS DHCP
radius
43
GPRS
44
GPRS
PLMN BG BG PLMN
45
GPRS
46
GPRS
47
GPRS
48
GPRS
mail
Master
Smail
Return
call
49
GPRS
50
GPRS
MSC
SGSN
51
GPRS
52
GPRS
mail
Master
Smail
Return
call
Note that a mobile station class B which is both IMSI- and GPRS-attached needs to suspend GPRS
whenever a dedicated channel (DCCH) is established towards the circuit-switched domain.
53
GPRS
54
GPRS
mail
Master
Smail
Return
call
55
GPRS
56
GPRS
Max No of Max No of
Multislot Receive Transmit Sum Tta Ttb Tra Trb
Type Class Rx +Tx
Timeslots Timesl
1 1 1 1 2 3 2 4 2
1 2 2 1 3 3 2 3 1
1 3 2 2 3 3 2 3 1
1 4 3 1 4 3 1 3 1
1 5 2 2 4 3 1 3 1
1 6 3 2 4 3 1 3 1
1 7 3 3 4 3 1 3 1
1 8 4 1 5 3 1 2 1
1 9 3 2 5 3 1 2 1
1 10 4 2 5 3 1 2 1
1 11 4 3 5 3 1 2 1
1 12 4 4 5 2 1 2 1
2 13 3 3 N/A N/A 1 / 0 *) 3 1 / 0 *)
2 14 4 4 N/A N/A 1 / 0 *) 3 1 / 0 *)
2 15 5 5 N/A N/A 1 / 0 *) 3 1 / 0 *)
MSs with these multislot classes and the according time constraints can be developed, using
the dynamic / extended dynamic resourc allocation.
MSs with these multislot classes can only be developed with either two antennas or two
tranceivers
MSs with these multislot classes cannot operate using neither the dynamic nor the
extended dynamic resource allocation method (Time Constraints)
57
GPRS
Timing Constraints
Being involved in a multislot transmission and / or reception, a mobile phone has to
have sufficient time gaps between the allocated timeslots:
to get ready to receive ( Trb) and (conditionally) to perform adjacent cell signal level
measurements in between ( Tra = Trb + N timeslots)
to get ready to transmit ( Ttb) and (conditionally) to perform adjacent cell signal level
measurements in between ( Tta = Ttb + K Timeslots)
The term"conditionally" in the previous sentences refers to the fact that a mobile phone will perform
adjacent cell signal level measurements either while preparing for transmission or while preparing
for reception. Accordingly, the more stringent time constraints Tra and Tta will never apply together
during one flow. Rather Tra & Ttb will apply together or Tta & Trb will apply together.
Note that in half-duplex mode (only multislot classes 19 - 29) only the less stringent time constraints Ttb
& Trb may apply together, if the PCU has provided Measurement Mapping parameters.
*) 1 TS with frequency hopping or 0 TS without frequency hopping.
**) 1 TS with frequency hopping or change from receive mode to transmit mode. 0 TS without
frequency hopping and no change from receive mode to transmit mode.
***) 1 TS with frequency hopping or change from transmit mode to receive mode. 0 TS without
frequency hopping and no change from transmit mode to receive mode.
58
GPRS
Max No of Max No of
Multislot Receive Transmit Sum Tta Ttb Tra Trb
Type Class Rx +Tx
Timeslots Timesl
2 16 6 6 N/A N/A 1 / 0 *) 2 1 / 0 *)
2 17 7 7 N/A N/A 1 / 0 *) 1 0
2 18 8 8 N/A N/A 0 0 0
1 19 6 2 N/A 3 1 / 0 *) 2 1 / 0 *)
1 20 6 3 N/A 3 1 / 0 *) 2 1 / 0 *)
1 21 6 4 N/A 3 1 / 0 *) 2 1 / 0 *)
1 22 6 4 N/A 2 1 / 0 *) 2 1 / 0 *)
1 23 6 6 N/A 2 1 / 0 *) 2 1 / 0 *)
1 24 8 2 N/A 3 1 / 0 *) 2 1 / 0 *)
1 25 8 3 N/A 3 1 / 0 *) 2 1 / 0 *)
1 26 8 4 N/A 3 1 / 0 *) 2 1 / 0 *)
1 27 8 4 N/A 2 1 / 0 *) 2 1 / 0 *)
1 28 8 6 N/A 2 1 / 0 *) 2 1 / 0 *)
1 29 8 8 N/A 2 1 / 0 *) 2 1 / 0 *)
MSs with these multislot classes and the according time constraints can be developed, using
the dynamic / extended dynamic resourc allocation.
MSs with these multislot classes can only be developed with either two antennas or two
tranceivers
MSs with these multislot classes cannot operate using neither the dynamic nor the
extended dynamic resource allocation method (Time Constraints)
59
GPRS
60
GPRS
T____= T____=
NC NC
DL Receive on 4 TSs Monitoring Receive on 4 TSs Monitoring
Transmit on 1 TS Transmit on 1 TS
UL
61
GPRS
62
GPRS
T____= T____=
NC
DL Receive on 2 TSs Monitoring Receive on 2 TSs
63
GPRS
64
Chapter 2
Terrestrial Interfaces
65
GPRS
Objectives
On completion of this chapter the student should be able to:
State the GPRS Protocols.
Explain the functions of the GPRS Protocols.
66
GPRS
67
GPRS
IP/PPP IP/PPP
SMS SMS
GMM/SM GMM/SM
Lower Layers
LLC LLC UDP UDP
GSM RF GSM RF Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1
68
GPRS
GTP-U
The major use GTP-U is the exchange of user payload between GSNs and between
SGSN and RNC (Radio Network Controller). In addition, GTP-U supports a few signaling
messages to check the state of a GTP-U tunnel.
GTP
GTP is the recommended protocol for the transfer of CDRs between SGSN and GGSN
on one hand and the charging gateway on the other hand.
69
GPRS
Gn
SGSN GGSN
BSS
Ga Ga
Gn CG Gp
Ga
SGSN BG
Gp
BSS
GTP
GTP-C
GTP-U
GTP-U
(only)
70
GPRS
Path
There is at least one GTP-path between one SGSN and one GGSN or between two SGSNs, if at
least one PDP-context is active between these two GSNs. Each path allows the transmission
of G-PDUs and signaling messages between GSNs by means of UDP/IP.
Each path between two GSNs is identified through the combination of source / destination
IP-address and source / destination port number.
GTP-Tunnel
There are GTP-tunnels in the control plane and in the user plane of GTP. Each tunnel is unambiguously
identified through the TEID (Tunnel Endpoint Identifier), the UDP-port number and the IP-address
of the network node. The receiving end side of a GTP tunnel locally assigns the TEID value the
transmitting side has to use (i.e. for mobile originated PDP-context establishment the GGSN
assigns the TEID the SGSN has to use to identify the very PDP-context).
Several GTP-tunnels can be multiplexed on a single GTP-path.
Note: For each PDP-context the establishment of an independent tunnel for both,
the control plane and the user plane is required.
71
GPRS
GTP-C GTP-U
Tunnel
72
GPRS
Path Management
Path management relates to the optional alive check of an active path between two GSNs. A
path is alive, if at least one PDP-context is established between the two GSNs.
Tunnel Management
Tunnel management relates to the establishment, update and deletion of tunnels between
two SGSNs. Each tunnel serves exactly one PDP-context. Each tunnel is identified through
the tunnel identifier which is part of the GTP-message header.
Location Management
Mobility Management
Mobility management, in the context of the GTP, entirely relates to inter-SGSN communication. This is
applicable in two cases: The first case is the GPRS attachment when the mobile station has since last
detachment changed the SGSN and the new SGSN contacts the former SGSN to obtain subscriber
information (see GMM-chapter). The second case is the inter-SGSN Routing Area Update Procedure.
73
GPRS
GTP
Functions
74
GPRS
75
GPRS
PDU
IP/PPP
GTP PDU
GTP
UDP
UDP GTP PDU
UDP
IP IP GTP PDU
L2
L1
Gn GGSN
76
GPRS
77
GPRS
IP/PPP IP/PPP
SMS SMS
GMM/SM GMM/SM
Lower Layers
LLC LLC UDP UDP
GSM RF GSM RF Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1
78
GPRS
79
GPRS
N-PDU
NSAPI
SNDCP
SN-PDU
SAPI
LLC
80
SNDCP Service Functions
The following functions are performed by SNDCP:
Transmission and reception of N-PDUs in acknowledged and unacknowledged LLC mode. In
acknowledged mode, the receipt of data shall be confirmed at the LLC layer, and the data
shall be transmitted and received in order per NSAPI. In unacknowledged mode, the receipt
of data shall not be confirmed at the SNDCP layer nor at the LLC layer.
Transmission and reception between the MS and SGSN of variable-length N-PDUs.
Transmission and reception of N-PDUs between the SGSN and MS according
to the negotiated QoS profile.
Segmentation and reassemble. The outputs of the compression functions are segmented to the
maximum length of LL-PDU. This is independent of the particular Network Layer protocol being used.
Transfer of the minimum amount of data possible between the SGSN and
MS through compression techniques.
Compression of redundant protocol control information (e.g. TCP/IP header) at the transmitting
entity and decompression at the receiving entity. Compression may be performed independently
for each QoS delay class and precedence class. If several network layers use the same QoS delay
class and precedence class, then one common compressor may be used for these network layers.
81
GPRS
SNDCP Control
Compression
Data
Compression
SN-DATA PDU/
SNDCP SNDCP
Segmented N-PDU SN-UNIDATA PDU
Header
82
GPRS
Provision of a Logical Link between the SGSN and the Mobile Station for higher layer
PDU Transfer
The LLC-layer within the SGSN will distinguish LLC-PDUs destined for or coming from different mobile
stations by means of the TLLI (part of the primitives from/to RLC/MAC and BSSGP). In addition,
LLC introduces a SAPI to distinguish among different PDUs for the same mobile station.
Negotiation of Logical Link Characteristics between the SGSN and Mobile Station
Different mobile stations and different SGSNs may support different transfer characteristics.
Therefore, mobile station and SGSN can start data transmission either after negotiation of
these transfer characteristics or by accepting the default values.
83
GPRS
84
GPRS
The functions of GMM deal with paging and radio status requests, whilst the NM functions
deal with such aspects as flow control and resets.
At the BSS, a Relay (RL) provides the functions for controlling the transfer of LLC frames
between the RLC/MAC Layer and the BSSGP Layer.
BSSGP Virtual Connections (BVC) provide communication paths between the BSSGP entities at
the SGSN and the BSS. Each BVC is used in the transport of the BSSGP PDUs between peer
Point-To-Point (PTP) functional entities and peer signalling functional entities. A PTP functional entity is
responsible for PTP user data transmission and as such there is one PTP functional entity per cell.
Each BVC is identified by means of a BSSGP Virtual Connection Identifier (BVCI) which has end-to-end
significance across the Gb interface and as such, each BVCI is unique between two Network Service
(NS) entities. At the SGSN, the BVCIs associated with PTP functional entities are dynamically
configured where as for signalling functions, the BVCIs are configured statically and set to 0000 hex.
85
GPRS
86
GPRS
87
GPRS
88
GPRS
89
GPRS
90
GPRS
91
GPRS
92
GPRS
93
GPRS
94
GPRS
95
GPRS
96
GPRS
97
GPRS
Applications
Applications
NSAPI
IMSI
NSAPI NSAPI
TLLI IMSI
98
Chapter 3
Air Interface
100
GPRS
Objectives
On completion of this chapter the student should be able to:
Explain the Frame Hierarchy of GSM/GPRS.
State the GPRS Logical Channels.
State the GPRS coding Schemes.
State the types and explain the Resource Allocation methods.
Explain how Timing Advance is achieved in the GPRS system.
State the Quality of Service criteria.
102
GPRS
The 26-Multi-frame
Is exclusively used by circuit-switched traffic channels (TCH/X) and their associated control
channels (SACCH / FACCH). Each 26-Multiframe has a period of 120 ms.
The 51-Multi-frame
Is exclusively used by all other circuit-switched control channels (incl. the SACCH for
SDCCH). Each 51-Multiframe has a period of 235.38 ms.
The 52-Multi-frame
Is exclusively used by PDCHs. Each 52-Multiframe has a period of 240 ms.
At any given moment in time a timeslot may either operate 26-Multiframe, 51-Multiframe or 52-Multiframe.
103
GPRS
Hyperframe
2048 Superframes / Period - = 3 hr 28 min 53s 760 ms
Superframe
51 x 26 - Multiframe oe 26 x 51 Multiframe or 25,5 x 52-Multiframe
0 1 2 3 4 47 48 49 50 <= 26-Multiframes
0 1 2 24 25 <= 51-Multiframes
0 1 23 24 25 <= 52-Multiframes
26-Multiframe
26 TDMA-Frames
Period = 120ms
(for cicuit-swithced TCHs)
51-Multiframe
0 1 2 24 25 51 TDMA-Frames
Period = 235.38ms
(for cicuit-swithced signalling) 52-Multiframe
52 TDMA-Frames
0 1 2 48 49 50 Period = 240ms
(for GPRS and EGPRS)
TDMA-Frame 0 1 2 49 50 51
8 TSs
Period = 4.615ms
0 1 2 3 4 5 6 7 1 Burst (577 s)
104
GPRS
Each Radio Block consists of 4 con-secutive appear-ances of the same timeslot within
4 con-secutive TDMA-frames
One radio block represents the basic resource to be allocated to a GPRS mobile station. Within
240 ms up to 12 different mobile stations may use the same timeslot, if each mobile station only
gets one radio block assigned. Obviously, the throughput rate would be rather low in that case
but at least GPRS provides for the sharing of one timeslot among various users.
*) The mobile station shall decode the BSIC of each of the 6 strongest adjacent cells at least
once every 10 s. If a mobile station is not able to perform these BSIC measurements within
the search frames it shall rather use inactivity periods to do so.
105
GPRS
T T
Block 0 Block 1 Block 2 Block 4 Block 5 Block 8 A Block 9 Block 11 I
A Block 3 I Block 6 Block 7 Block 10
106
GPRS
The PACCH
Abbreviation for the bi-directional Packet Associated Control Channel.
The PTCCH
Abbreviation for Packet Timing Advance Control Channel. The PTCCH is divided into
the downlink PTCCH/D and the uplink PTCCH/U.
The PBCCH
Abbreviation for the optional Packet Broadcast Control Channel.
The PCCCH
Abbreviation for the optional Packet Common Control Channel that summarizes the PRACH
(Packet Random Access Channel), the PAGCH (Packet Access Grant Channel), the PNCH
(Packet Notification Channel) and the PPCH (Packet Paging Channel).
107
GPRS
PDCH
PDTCHs are
assigned
undirectionally
= Uplink only
= Downlink only
108
GPRS
Some PDCHs like the PCCCH and the PBCCH are optional
If PBCCH and PCCCH are not available in a cell, the mobile station shall use BCCH and
CCCH instead. On BCCH at least one of the SYS_INFOs 3, 4, 7 or 8 will indicate whether
SYS_INFO13 is also broadcast on BCCH [ GPRS-INDICATOR = RACC (3 Bits) + SYS_INFO
13 position (1 Bit)). The presence of SYS_INFO13 indicates to the surrounding mobile stations
whether or not a base station supports GPRS in the first place.
SYS_INFO 13 is broadcast either on BCCH normal ( Block 0 of 51-Multiframe) or BCCH ext. (
Block 1 of 51-Multiframe) at least once every 33 51-Multiframes (Period 7.75 s)
109
GPRS
Some PDCHs like the PCCCH and the PBCCH are optional
110
GPRS
111
GPRS
BS_PBCCH_BLKS = 2
0 1 2 3 4 5 6 7 8 9 10 11
BS_PAG_BLKS_RES = 3
(no paging on these blocks)
112
GPRS
113
GPRS
114
GPRS
115
GPRS
TS 0 PDCH TS 0 TS 0
TS 1 PDCH TS 1 TS 1
TS 2 TS 2 TS 2 TS 2
PDCH PDCH TS 3 TS 3
PDCH PDCH PDCH TS 4
PDCH PDCH PDCH TS 5
TS 6 TS 6 TS 6 TS 6
TS 7 NO PDCH OK TS 7 OK TS 7
116
GPRS
117
GPRS
PACCH
(Packet Associated
Control Channel)
PTCCH
(Packet Timing Advance
Control Channel)
118
GPRS
119
GPRS
120
GPRS
121
GPRS
CS-Paging and PS-Paging for GPRS Mobile Station Class A and Class B is done:
=> on PPCH (if configured and only in idle mode)
=> on PCH (if no PPCH is available and only in idle mode)
=> on PACCH (while involved in a packet data transfer) Circuit_Switched (CS) paging
=> on FACCH (call Waiting Indication while involved in a call)
VLR ISDN / PTSN
G-MSC
122
GPRS
123
GPRS
CS-Paging:
=> on PCH (considering the CS-DRX-parameters)
=> on FACCH (Call Waiting Indication during a call)
IMSI-Attach/Location Area Updating are performed SGSN is responsible only for PS-Paging
towards the VLR
PS-Paging:
=> on PCH (considering the PS-DRX-parameters)
=> on PACCH (while involved in a packet data transfer)
GPRS-Attach / Routing Area Updating are performed towards the SGSN
124
GPRS
125
GPRS
126
GPRS
127
GPRS
Protection
Mandatory
for the mobile station
CS-1
CS-2
Mandatory
for the BTS
CS-3
CS-4
Throughput
128
GPRS
Details of CS-1
Initial Situation
In case of CS-1, 184 bits are delivered to the encoder. These 184 bits are divided into 8
bits for the MAC-header plus 176 bits for the RLC-data or control block. Please note that in
any case the RLC-data or control block contains at least 16 bits of the RLC-header. While
in downlink direction the first three bits of the MAC-header are the USF (Uplink State Flag),
in uplink direction there are three different control bits ( MAC).
Step 3: Interleaving
After the channel coding process the 456 output bits are interleaved according to the rules of
the SACCH. Note that for GPRS only block interleaving is applicable because transmission
is based on radio blocks which represent 4 consecutive occurrences of the same timeslot.
Therefore, interleaving over more than 4 TDMA-frames is not possible.
129
GPRS
Details of CS-1
184 bits
MAC-Header
8 bits RLC - Data / Control Block
USF applicatble 3 bits
for downlink only
USF 5 bits 176 bits / (22 octets)
Fire Code
40 bits Tail
184 Data Bits Check Bits 0000
228 bits
1
/2 Rate Convolutional Coder
130
GPRS
Step 4: Puncturing
Puncturing will delete 132 bits / 220 bits of the output of the convolutional coder
to fit the 456 output bits into one radio block.
Step 5: Interleaving
After the channel coding process the 456 output bits are interleaved according to the rules of
the SACCH. Note that for GPRS only block interleaving is applicable because transmission
is based on radio blocks which represent 4 consecutive occurrences of the same timeslot.
Therefore, interleaving over more than 4 TDMA-frames is not possible.
131
GPRS
Pre-
Coding Tail
6 bits 16 bits
USF 268 / 312 Data Bits Parity Bits 0000
1
/2 Rate Convolutional Coder
132
GPRS
Puncturing
Puncturing in GSM
Puncturing is not a new technology with GPRS. Puncturing has already been used in GSM in the
channel coding process of the TCH/F 9.6 and the TCH/F 14.4. In GPRS, puncturing is used for CS-2
and CS-3 and for the channel coding process of access bursts with 11 information bits.
Introduction to Puncturing
Puncturing provides for more flexible code rates than the simple 1/2- or 1/3-convolutional
coders allow. Please remember: The code rate is the number of input bits to the
convolutional coder divided by the number of output bits.
In CS-2 we therefore calculate the code rate to 294 bits 456 bits = 0.645 2/3.
For CS-3 we apply the same formula and get 338 bits 456 bits = 0.741 3/4. For CS-1
we can do the same calculation and will figure out a code rate of 1/2.
Most importantly: Puncturing provides for the transmission of data blocks, encoded with
CS-2 and CS-3 with just one radio block of 456 bits.
133
GPRS
Puncturing
Puncturing in GSM
Introduction to Puncturing
The Perspective of the Receiver
Puncturing
134
GPRS
Details of CS-4
Initial Situation
In case of CS-4, 431 bits are delivered to the encoder. These 431 bits are divided into 8
bits for the MAC-header, 416 bits for the RLC-data block and 7 spare bits. Please note
that in any case the RLC-data block contains at least 16 bits of the RLC-header. While in
downlink direction the first three bits of the MAC-header are the USF (Uplink State Flag),
in uplink direction there are three different control bits ( MAC).
Step 4: Inter-leaving
After the channel coding process the 456 output bits are interleaved according to the rules of
the SACCH. Note that for GPRS only block interleaving is applicable because transmission
is based on radio blocks which represent 4 consecutive occurrences of the same timeslot.
Therefore, interleaving over more than 4 TDMA-frames is not possible.
Note: In CS-2 and CS-3 the already precoded USF ( 6 bits) is sent through the 1/2-rate convolutional
coder and is extended to 12 bits. The puncturing process will never affect these first 12 bits. In
CS-4 the precoding table simulates the behavior of the 1/2-rate convolutional coder being applied
two consecutive times to the three bits of the USF. Therefore, the first 12 bits of a channel coded
block in CS-2, CS-3 and CS-4 depend only on the USF but not on the coding scheme.
135
GPRS
Details of CS-4
431 bits
Pre-
Coding Tail
12 bits 16 bits
USF 428 Data Bits Parity Bits
No Convolutional Coding!
136
GPRS
137
GPRS
138
GPRS
139
GPRS
1 1
0 0 4 alternating bursts,
belonging to one
radio block
1 0
0 0
140
GPRS
141
GPRS
142
GPRS
143
GPRS
144
GPRS
Allocation of Resources
A cell supporting GPRS may allocate resources on one or several physical channels in order to support
the GPRS traffic. Those physical channels shared by the GPRS MSs are taken from a common pool of
physical channels available in the cell. This allocation of physical channels to circuit switched services
and GPRS is carried out dynamically according to the capacity on demand principles.
The capacity on demand principles refer to the fact that PDCHs need not be permanently allocated in
order to support GPRS and the way in which the network allocates available resources as required.
Common control signalling that is required by GPRS in the initial phase of packet transfer is conveyed
on the PCCCH, when allocated, or on the CCCH. This saves on GPRS specific capacity for the
operator. Should the last available PCCCH be allocated then the MS would perform cell re-selection.
At least one PDCH, acting as the master, carries the PCCCH as well as PDTCH and PACCH. Other
PDCHs, acting as slaves, are used for user data transfer and for dedicated signalling.
Release of PDCH
The fast release of PDCH is an important feature to enable the dynamic sharing of
the physical radio resources between packet and circuit switched servics. To enable
this three PDCH release options are available:
Wait for all assignments to terminate on that PDCH.
Individuaklly notify all the users that have assignments on that PDCH.
Broadcast the notification about de-allocation.
145
GPRS
146
GPRS
Dynamic Allocation
The dynamic allocation of Uplink resources is based upon the use of the Uplink State Flag (USF).
The USF forms part of each downlink Data or Control Block that is sent.
The USF is transmitted in the downlink to indicate an invitation to transmit to mobiles. A
mobile is allocated a number of uplink time-slots (shared with other mobiles) and each is
told when they may be allowed to transmit. Although up to the maximum 8 time-slots may
be allocated, this would require the phone to have a duplexer.
The USF has a fixed length of 3 bits, so that up to 7 MS can be distinguished on a particular timeslot. A
MS having multiple timeslots allocated may have different USFs allocated for each timeslot.
A USF value of 111 is used to denote that the next uplink block is reserved for PRACHs.
Once the MS detects its USF in the downlink RLC Data Blick it will transmit on the next uplink block
or the next 4 uplink blocks dependent upon the value of the USF_GRANULARITY.
The USF_GRANULARITY is also included in the Packet Uplink Assignment. The
USF_GRANULARITY has two values, 0 and 1.
If the USF_GRANULARITY is set to 0 the MS will transmit on the next uplink block
following the appearance of its USF value.
If the USF_GRANULARITY is set to 1 the MS will transmit on the next four uplink
blocks following the appearance of its USF.
In the diagram opposite two MSs have been allocated uplink resources dynamically.
MS 1 will look for a USF value of 5 on timeslot 6 and a USF value of 3 on timeslot 7.
MS 2 will look for a USF value of 4 on timeslot 6 and a USF value of 2 on timeslot 7.
Following the appearance of these respective values each MS will transmit on
the next available uplink block.
147
GPRS
LLC
RLC/MAC
BH Information BCS BH Information BCS BH Information BCS
NB NB NB NB
5 5 5 I 4 5 5 I 4 4 I I DL
TS6
5 5 I 5 4 5 I 5 4 4 I I UL
3 3 2 I 2 3 3 I 2 2 I I DL
TS7
3 3 I 2 2 3 I 3 2 2 I I
UL
148
GPRS
149
GPRS
DL 0 1 2 3 4 5 6 7
UL 5 6 7 0TA 1 2 3 4
Transmit
SYS101_ch03_148
150
GPRS
151
GPRS
152
GPRS
153
GPRS
DL 0 1 2 3 4 5 6 7
UL 5 6 7 0TA 1 2 3 4
Transmit
SYS101_ch03_148
154
GPRS
155
GPRS
Bit
8 7 6 5 4 3 2 1
Payload Type RRBP S/P USF MAC header
PR TFI FBI Octet 1
BSN E Octet 2
Length indicator M E Octet 3 (optional)
. .
. .
. .
Length indicator M E Octet M (optional)
Octet M+1
.
RLC data .
.
Octet N-1
Octet N
spare spare (if present)
Bit
8 7 6 5 4 3 2 1
Payload Type Countdown Value SI R MAC header
TFI TI Octet 1
BSN E Octet 2
Length indicator M E Octet 3 (optional)
. .
. .
. .
Length indicator M E Octet M (optional)
Octet M+1 \
Octet M+2 } (optional)
TLLI Octet M+3 /
Octet M+4 /
Octet M+5
.
.
RLC data .
Octet N-1
Octet N
spare spare (if present)
156
GPRS
157
GPRS
158
GPRS
159
GPRS
160
GPRS
Idle to Ready
When moving from an Idle State to a Ready State a mobile must first perform a GPRS
Attach. If successful this will make the mobile known to the network, i.e. SGSN. If
unsuccessful the mobile will fall back to the Idle State.
Following the attach sequence a MM context is said to be active at the MS and the SGSN.
Once in the Ready State, a PDP context may be activated which allows the MS to establish
a packet data session with the associated packet data networks (PDNs). In particular this
will associate a PDN address within the MS and the GGSN.
With a valid PDP context it is possible to transfer Protocol Data Units (PDUs). Once the transmission
of PDUs has finished then a Ready Timer is started (which starts with a default value, but may be
changed by the SGSN). Both the MS and SGSN should be using the same value.
Whilst in this state the MS will perform both Cell and Routing Area updates.
Ready to Standby
A move from a Ready State to Standby State will follow the expiry of the Ready Timer
or a Force to Standby from an MS or SGSN.
Alternatively if a problem is encountered on the RLC/MAC interface, then the
MS could enter the Standby State.
Whilst in this state only Routing Area Updates will be performed.
Standby to Idle
Once in the Standby Stat e a second timer is started and when this expires or a MAP message,
Cancel Location is received from the HLR, then the return to the Idle State is performed
and the MM context are removed from the MS, SGSN, and GGSN.
Ready to Idle
Either a GPRS detach or a Cancel location would change the state from Ready to Idle and in doing so,
both MM and PDP contexts would be removed as the MS is no longer connected to the GPRS network.
Standby to Ready
Once there are PDUs to transmit/receive the MS and SGSN will enter the Ready State.
To enable this a PDP context must have been activated.
161
GPRS
Idle Idle
GPRS
GPRS GPRS
GPRS detach
attach attach
detach or cancel
location
Ready Ready
Standby
Standby timer
timer expiry
expiry or cancel Ready timer expiry or
Ready timer location
expiry or force to standby or
abnormal RLC PDU
force to PDU
condition reception
standby transmission
Standby Standby
162
GPRS
Mobile Identity
The P-TMSI and the TLLI
The TLLI (Temporary Logical Link Identifier) is actually no GMM-parameter. However, at least two
(Local-TLLI and Foreign-TLLI) of the four defined TLLIs are built from the P-TMSI. The TLLI is used
between mobile station and SGSN for the identification of the logical link (LLC-protocol). Note that at
any moment in time there may be only one logical link between a mobile station and the SGSN.
Local TLLI
The Local TLLI is an exact copy of the P-TMSI. The mobile station shall use the Local TLLI for
logical link identification only a) in the routing area where the related P-TMSI was allocated
(unless the procedure to be performed is a GPRS Attach) or b) after a routing area update
scenario in the new routing area when no new P-TMSI was allocated during the routing area
update scenario or c) for a periodic routing area update scenario.
Foreign TLLI
The mobile station shall use the Foreign TLLI only during GPRS Attachment
and for Routing Area Updating (not periodic).
Random TLLI
The Random TLLI is used by the mobile station during anonymous PDP context activation
or when no P-TMSI is currently available in the mobile station.
Note: TMSI and the LAI need to be stored on the SIM mandatorily .However, the storage of P-TMSI
and RAC on the SIM is optional and not possible for older SIM cards (< Phase 2+). Therefore the
mobile equipment (ME) needs to be able to store P-TMSI and RAC in a non-volatile memory. In this
case the mobile equipment needs to check upon every power on whether or not the old SIM is still in
use. If this check indicates a new SIM (IMSI-check) then the ME needs to erase the stored P-TMSI and
RAC.Accordingly, there are many instances when a mobile station has no P-TMSI available.
Auxiliary TLLI
The Auxiliary TLLI is allocated by the SGSN upon reception of an anonymous PDP context
activation request by the mobile station. The use of the Auxiliary TLLI shall avoid ambiguities of
Random TLLIs for anonymous PDP contexts in one SGSN area. (R97 only)
163
GPRS
Mobile Identity
Identity
GPRS
IMSI Network
P-TMSI
TLLI
MS TLLI
"
"
P-TMSI
TLLI
164
GPRS
165
GPRS
IP/PPP IP/PPP
SMS SMS
GMM/SM GMM/SM
Lower Layers
LLC LLC UDP UDP
GSM RF GSM RF Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1 Layer 1
166
GPRS
167
GPRS
Application
IP/PPP PDU
Segmented / re-assembly
R
RLC L RLC DATA
C
R
MAC MAC L RLC DATA
C
168
GPRS
169
GPRS
QoS Applicability
170
GPRS
171
GPRS
Traffic Class
Guaranteed
Bitrate (UL/DL) Delivery Order
Traffic
Handling Delivery of
Priority erroneous SDU
Allocation / QoS
Retention Maximum
Priority Profile SDU size
Maximum
Transfer Delay Bitrate (UL/DL)
Residual
SDU error ratio
BER
172
Chapter 4
GPRS Signalling
173
GPRS
Objectives
On completion of this chapter the student should be able to:
Explain the GPRS MS Packet transfer procedure.
Explain the GPRS Attach/Detach signalling.
Explain the GPRS PDP Context activation procedure.
Explain the GPRS Network PDP Context activation procedure.
Explain the Allocation of the TEID during PDP-Context establishment
174
GPRS
175
GPRS
PCU PCU
Phase 1
Access Messa Access Messa Phase 1
ge ge
llocation
ACK / NAC
K Resource A Phase 2
Contention
Resolution:
Data Explicit Data
Data Data
Data Data
176
GPRS
Description
The mobile station will send an ATT_REQ-message to the SGSN and start T3310 ( 15s). If the
SGSN is unable to identify the mobile station ( P-TMSI unknown) it will request the GMM-context
of the mobile station from the former SGSN. The new SGSN will identify the former SGSN based
on the RAI that the mobile station has included in the ATT_REQ message.
If the former SGSN is inaccessible or doesnt know the mobile station either (e.g. the mobile
station has been purged by the former SGSN) the SGSN will retrieve the IMSI from the mobile
station by sending an IDENT_REQ]. Upon sending IDENT_REQ, the SGSN will start T3370 (
6 s). Accordingly the mobile station will respond by sending IDENT_RSP.
Based on the received IMSI in IDENT_RSP the SGSN will ask the HLR of the mobile
subscriber to provide authentication information.
177
GPRS
New Former
HLR
SGSN SGSN
T3310
= 15s Only if MS is unknown
in new SGSN
T3370 = 6s
to retrieve IMSI, if MS is also unknown in former SGSN
Only if Authentication
and/or Ciphering shall
be performed
178
GPRS
179
GPRS
180
GPRS
181
GPRS
New Former
SGSN SGSN
HLR
MA
MAP: END/
cancelLocation
[3]
riberData [7]
MAP: BEGIN / insertSubsc
3]
MAP: END / UpdateGprsLocation[2
T_ACC
GMM: AT
T3350 = 6s
GMM: A
TT_CO
M
Only if ATT_ACC contained new TMSI and/or P-TMSI
or new T3314 value and Force to Standby is not set.
182
GPRS
Description
The mobile station shall initiate the detachment by sending DET_REQ to the SGSN. If the DET_REQ
does not indicate Power Off, the mobile station shall start T3321 ( 15 s).
If there is one or more PDP-context existing the SGSN shall inform the respective GGSN(s)
of the detachment by sending DEL_PDP_CT_REQ. The GGSN(s) will delete this (these)
PDP-context(s) and reply to the SGSN by sending DEL_PDP_CT_RSP .
If the network is in NOM I and the mobile station (class A or B) is both IMSI- and
GPRS-attached and wants to either detach from circuit-switched GSM only or from GPRS
and circuit-switched GSM, the SGSN shall send a BSSAP+-IMSI-DETACH-IND-message ]
to the serving MSC/VLR and start timer T9 ( 4 s (1 - 30 s)).
The serving MSC/VLR shall reply with the BSSAP+-IMSI-DETACH-ACK-message [.
183
GPRS
only sent if a
PDP-context exists
T3321
T9 = 4s (1-30s)
184
GPRS
185
GPRS
T8 = 4s (1-30s)
CS-Paging
HLR
Time between Detachment
and Purge MS is adjustable
by the operator.
186
GPRS
Description
The SGSN shall initiate the detachment by sending DET_REQto the mobile station. The
SGSN shall start T3322 ( 6 s). Note that the Detach Type information element may indicate
that the mobile station shall immediately re-attach to the SGSN.
If there is one or more PDP-context existing the SGSN shall inform the respective GGSN(s)
of the detachment by sending DEL_PDP_CT_REQ message.
The GGSN(s) will delete this (these) PDP-context(s) and reply to the SGSN
by sending DEL_PDP_CT_RSP.
If the network is in NOM I and the mobile station (class A or B) is both IMSI- and GPRS-attached and
shall be detached from GPRS only, the SGSN shall send a BSSAP+-GPRS-DETACH-IND-message
to the serving MSC/VLR and start timer T8 ( 4s (1 - 30 s)).
The serving MSC/VLR shall reply with the BSSAP+-GPRS-DETACH-ACK-message . From
now on the MSC/VLR wont forward circuit-switched paging for that mobile station to the
SGSN for further processing but operate autonomously.
187
GPRS
T8 = 4s (1-30s)
188
GPRS
189
GPRS
T3322
190
GPRS
Description
The HLR shall initiate the detachment of a mobile station by sending the MAP cancelLocation-message
(Cause value: subscription withdrawn) to the SGSN. The SGSN shall initiate the detachment by
sending DET_REQ to the mobile station. The SGSN shall start T3322 ( 6 s).
If there is one or more PDP-context existing the SGSN shall inform the respective GGSN(s)
of the detachment by sending DEL_PDP_CT_REQ. The GGSN(s) will delete this (these)
PDP-context(s) and reply to the SGSN by sending DEL_PDP_CT_RSP.
191
GPRS
T3322 = 6s [3]
lLocation
IN / cance
MAP: BEG
T_REQ
GMM: DE
T_RSP
L_PDP_C
GTP: DE
192
GPRS
193
GPRS
T3322
T8 = 4 s (1-30s)
Only set in NOM 1 if MS
Class A/B remains IMSI
Attached after HLR
iniciated GPRS Detach.
In that case the VLR is
from now on responsible
for CS-Paging
194
GPRS
Description
The terminal equipment (e.g. laptop) first needs to define the
PDP-context to be established through the transfer of the AT-command
+CGDCONT . The mobile station shall confirm the reception of this AT-command.
Optionally, the terminal equipment may specify a specific QoS-profile to be requested for this
PDP-context. In this case, the terminal equipment shall send another AT-command to the mobile
station. The mobile station shall confirm the reception of this AT-command.
To initiate the PDP-context activation procedure, the terminal equipment will send another
AT-command to the mobile station. The mobile station shall confirm the reception of this
AT-command and start the PDP-context activation procedure.
After the dial command, the PPP (Point-to-Point Protocol) will establish a layer 2 connection
between terminal equipment and mobile station. This is done through the PPP LCP (Link Control
Protocol). In addition, terminal equipment and mobile station shall negotiate a PPP authentication
protocol (either CHAP or PAP with preference on CHAP), if user authentication to the PDN and
/ or between the terminal equipment and the mobile station is required.
195
GPRS
SGSN GGSN
Radius
AT +CGD
CONT PDP-Context Definition
OK
If Rel. 98 QoS
Parameters
are requested
AT +CGQ
REQ
If Rel. 99 QoS
Parameters
are requested If TE requests specific
AT +CGE
QREQ QoS profile
OK
ATD *99#
Connect
PPP/LCP: Link
Discussion
Authentication
196
GPRS
197
GPRS
SGSN GGSN
Radius
Broadcast
DHCP
DHCP
UDP/IP: DHCP
DHCPDIS
COVER
DHCP is used for
IP-address allocation
DHCP
DHCP
DHCP
UDP/IP: ER
F
DHCPOF
198
GPRS
199
GPRS
SGSN GGSN
Radius
T3380
UDP/IP: D
HCPREQU
EST
K
UDP/IP: DHCPAC
RSP
GTP: CT_PDP_CT_
ACT_PDP_CT_ACC
PPP/IPCP:ACK Internet/
E
CONFIGUR
Intranet
Provision of
IP-Address
Transfer of IP-Frames
200
GPRS
Description
The terminal equipment (e.g. laptop) first needs to define the Secondary
PDP-context to be established through the transfer of the AT-command
+CGDSCONT . The mobile station shall confirm the reception of this AT-command.
If there is one PDP-context without a TFT, the +CGDTFT is sent to the MS in order to activate a traffic
flow template which allows to support for different QoSs in the GGSN in downlink direction.
The terminal equipment may specify a specific QoS-profile to be requested for this PDP-context.
In this case, the terminal equipment shall send another AT-command to the mobile station.
The mobile station shall confirm the reception of this AT-command.
To initiate the PDP-context activation procedure, the terminal equipment will send another AT-command
to the mobile station. The mobile station shall confirm the reception of this AT-command and start the
PDP-context activation procedure. If the PDP-context identifier of the PDP context to be activated shall
be included then the command will be ATD *99**x# with x = cid in the +CGDSCONT command.
201
GPRS
Internet/
Intranet
SGSN GGSN
Secondary
AT +CGD PDP-Context Definition
SCONT
OK
Traffic Flow
AT +CGT Template Definition
F T
OK
QoS Request
AT +CGQ
R EQ
OK
ATD *99#
Connect
202
GPRS
203
GPRS
Internet/
Intranet
SGSN GGSN
PPP/LCP: Link
Discussion
PPP/CHAP/PAP Authentication
Authentification
PPP/IPCP
: CONFIGU
REQUEST RE
ACT_SEC
_PDP_CT_R
EQ
GTP: CT_P
D P_CT_REQ
T3380 = 30s
_RSP
GTP:CT_PDP_CT
_ACC
PPP/IPCP: ACT_SEC_PDP_CT
CONFIGURE ACK
Transfer of IP-Frames
204
GPRS
Initial Conditions
The mobile station is of any class A, B or C and has already established a GMM-context (
GPRS-attached). No PDP-context of type IP is established and the GGSN is receiving IP-frames
for that mobile station. The terminal equipment has previously setup the mobile station to
either automatic answering mode (ATS0 = 1) or not. In the latter case, manual interaction is
required to confirm the establishment of the respective PDP-context.
Note that the mobile station requires a static and public IP-address to allow for mobile terminating
PDP-context activation. Otherwise, the HLR has no means to obtain information about the HLR
of that subscriber (which needs to be obtained through some sort of DNS-server).
Description
The GGSN receives IP-frames for a specific mobile station. The mobile station is identified
by its static IP-address. If the GGSN does not have a Gc-interface, it needs to send a
SEND_ROUT_INFO_FOR_GPRS_REQ-message to a GSN ( SGSN or GGSN) with GTP
MAP conversion capability. This GSN will forward the GGSNs request to the HLR (MAP
sendRoutingInfoForGprs-procedure) of the requested subscriber to obtain information about
the SGSN that currently serves the subscriber. If the GGSN does have a Gc-interface, it
will directly contact the HLR through the indicated MAP-procedure.
If the subscriber is not detached from GPRS, the HLR will convey a positive response to the requesting
GSN which will relay it back to the GGSN within a SEND_ROUT_INFO_FOR_GPRS_RSP-message .
205
GPRS
IP-Frames for
n
Mobile Statio
FO
_ROUT_IN Only if no Gc-Interface
GTP:SEND PRS_REQ
/ send O R _G is equipped in this GGSN
MAP: BEGIN prs [24] _F
orG
RoutingInfoF
MAP: EN GTP:SEN
RoutingInfoFD / send D_R
orGprs [24] _FOR_GP OUT_INFO
RS_RSP
206
GPRS
207
GPRS
Internet
SGSN GGSN
Automatic answering
enabled
ATSO =
1
Q
GTP: PDU_NOT_RE
REQ_PDP_CT_ACT
RING
GTP: PDU
_NOT_RSP
CONNECT
T3385 = 8 s
PPP/LCP:
Link Discussion
Authentication
PPP/CHAP/PAP:
Authentification
208
GPRS
209
GPRS
SGSN GGSN
Radius
T3385 = 8 s
PPP/IPCP
CONFIGU :
RE_REQ UEST ACT_PDP
_CT_REQ
GTP: CT_P
D P_CT_REQ
UDP/IP: R
Access-R ADIUS:
T3380 = 30 s equest
Authentication
DIUS:
UDP/IP: RAccept
Access-A
RSP
GTP: CT_PDP_CT_
ACT_PDP_CT_ACC
PPP/IPCP:
CONFIGURE_ACK
Internet
Transfer of IP-Frames
210
GPRS
Description
The SGSN sends a CT_PDP_CT_REQ message to the GGSN, which is identified on the lower layer by
its IP address (mapping of APN IP address). The TEID in the header of the GTP-C message is set to
"0" since the TEID for the tunnel is not known yet by the SGSN. Further this message includes the TEIDs
for both, the GTP-C and GTP-U tunnel, which the GGSN shall use when communicating with the SGSN.
The GGSN includes in the header of the CT_PDP_CT_RESP message the TEID the SGSN has
chosen for the GTP-C tunnel. Further the GGSN informs the SGSN, which TEIDs to use for
the GTP-U and the GTP-C tunnel when sending data/signaling to the GGSN.
Both, the SGSN and the GGSN will use the allocated TEIDs for all data and control procedures
on the involved GTP-C- and GTP-U tunnels for each PDP-context.
211
GPRS
SGSN GGSN
SM: ACT_PD
P_CT_REQ
(APN)
Mapping of
APN IP Address
of GGSN
GTP-C: CT_P
Header TEID DP_CT_REQ
= "0" / TEID-D
(SGSN) / TEID
-C(SGS N)
DP_CT_RSP GSN)
GTP-C: CT_P N) / TEID-C(G
C( SG SN )" / TEID-D(GGS
ID = "T EI D-
Header TE
P_CT_RSP
SM: ACT_PD
GTP-U: G-PD
Header TEID U
= "TEID-D(GG
SN)"
U
GTP-U: G-PD
ID = "T EI D- D(SGSN)"
Header TE
SM: DEACT_
PDP_CT_REQ
GTP-C: DEL_
PDP_CT_REQ
Header TEID
= "TEID-C(GG
SN)"
PDP_CT_RSP
GTP-C: DEL_ )"
= "TEID-C(SGSN
Header TEID
PDP_CT_ACC
SM: DEACT_
212
GPRS
Description
The terminal equipment (e.g. laptop) will initiate the PDP-context deactivation by initiating
a tear-down of the PPP-link towards the mobile station. A graceful shutdown is achieved
through the transfer of a PPP LCP TERMINATE REQUEST-frame.
Consequentially, the mobile station will transmit a DEACT_PDP_CT_REQ-message to the SGSN.
The PDP-context to be deactivated is identified by means of the transaction identifier. The Tear down
indicator indicates whether all PDP contexts with the same IP Address shall be terminated or only
the one indicated in the TI. In addition, the mobile station will start timer T3390 = 8 s.
The SGSN will forward the request of the mobile station to the GGSN through the
transfer of a DEL_PDP_CT_REQ-message.
If a dynamic IP-address is linked to this PDP-context, the GGSN will release this dynamic IP-address
through the transfer of a UDP/IP: DHCPRELEASE-message to the DHCP-server.
The GGSN will confirm the deactivation of the PDP-context by sending a
DEL_PDP_CT_RSP to the SGSN.
Note: Between the SGSN and the GGSN, the PDP-context is identified through the TEID (Tunnel
Endpoint Identifier Data) and the NSAPI. Between mobile station and SGSN, different PDP-contexts
are distinguished by means of the transaction identifier (TI). The NSAPI in the DEL_PDP_CT_REQ
message indicates to the GGSN which PDP context shall be deactivated if there are more than one
PDP contexts per TEID. The Tear Down Indicator indicates whether all PDP-Contexts with the same
PDP-Address shall be deleted or only the one identified by the TEID and the NSAPI.
The SGSN will confirm the deactivation of the PDP-context by sending a
DEACT_PDP_CT_ACC-message to the mobile station. Finally the mobile station can
confirm the initial PPP LCP TERMINATE REQUEST-frame by sending a PPP LCP
TERMINATE ACK-frame to the terminal equipment.
213
GPRS
SGSN GGSN
DHCP
PP
TERMINATP/LCP:
E REQUES
T DEACT_P
DP_CT_RE
Q GTP: DEL_
PDP_CT_RE
Q UDP/IP: D
HCPRELE
ASE
T3390 = 30 s
_RSP
GTP: DEL_PDP_CT
CC
DEACT_PDP_CT_A
PPP/LCP:
TERMINATE_ACK
214
GPRS
Description
The SGSN will send a DEL_PDP_CT_REQ-message to the GGSN. Without waiting for the
reply from the GGSN, the SGSN may already send a DEACT_PDP_CT_REQ-message
to the mobile station and start timer T3395 = 8 s.
The mobile station will indicate the PDP-context deactivation to the terminal equipment
by initiating a tear-down of the PPP-link. A graceful shutdown is achieved through the
transfer of a PPP LCP TERMINATE REQUEST-frame.
The terminal equipment may confirm the tear-down by sending a PPP LCP
TERMINATE ACK-frame to the mobile station.
The mobile station will confirm the deactivation of the PDP-context by sending a
DEACT_PDP_CT_ACC-messageto the SGSN. The SGSN will stop T3395 upon
reception of DEACT_PDP_CT_ACC.
In the meantime the GGSN has initiated the release of the dynamic IP-address through the
transfer of a UDP/IP: DHCPRELEASE-message to the DHCP-server.
In addition the GGSN will confirm the deactivation of the PDP-context by sending
a DEL_PDP_CT_RSP to the SGSN.
215
GPRS
SGSN GGSN
DHCP
GTP: DEL_
PDP_CT_RE
Q UDP/IP: D
HCPRELE
ASE
EQ
PPP/LCP: DEACT_PDP_CT_R
UEST
TERMINATE_REQ
PPP/L
TERMINATCP:
E ACK
DEACT_P
DP_CT_AC
C
216
GPRS
Description
The GGSN will send a DEL_PDP_CT_REQ-message .to the SGSN.
The SGSN shall send a DEACT_PDP_CT_REQ-message to the mobile station
and start timer T3395 = 8 s.
The mobile station will indicate the PDP-context deactivation to the terminal equipment
by initiating a tear-down of the PPP-link. A graceful shutdown is achieved through the
transfer of a PPP-LCP TERMINATE REQUEST-frame.
The terminal equipment may confirm the tear-down by sending a PPP LCP
TERMINATE ACK-frame to the mobile station.
The mobile station will confirm the deactivation of the PDP-context by sending
a DEACT_PDP_CT_ACC-message to the SGSN. The SGSN will stop T3395
upon reception of DEACT_PDP_CT_ACC.
The SGSN will confirm the deactivation of the PDP-context by sending a
DEL_PDP_CT_RSPto the GGSN.
Finally, the GGSN has initiated the release of the dynamic IP-address through the transfer
of a UDP/IP: DHCPRELEASE-message to the DHCP-server.
217
GPRS
SGSN GGSN
DHCP
_REQ
EQ GTP: DEL_PDP_CT
PPP/LCP: DEACT_PDP_CT_R
UEST
TERMINATE_REQ
T3395 = 8 s
PPP/L
TERMINATCP:
E ACK
DEACT_P
DP_CT_AC
C GTP: DEL_
PDP_CT_RS
P
UDP/IP: D
HCPRELE
ASE
218