Académique Documents
Professionnel Documents
Culture Documents
Training manual
8 AS 90164 0001 VH ZZA 10
Edition 2004
Page intentionally left blank
2 GPRS Operation 17
2.1 Main Entities 19
2.2 MS Mobility Management States 24
2.3 MS Radio Resource Operating Modes 25
2.4 Basic procedures 26
2.5 Charging 37
2.6 Security 39
4 Alcatel Solution 62
4.1 GPRS Network Overview 64
4.2 Alcatel 9135 MFS 65
4.3 Packet Switched Core Network 67
4.4 GPRS Network Management 69
4.5 Alcatel QoS offer 70
Other comments
1
© Alcatel University - 8AS 90164 0001 VT ZZA Ed.10
A PSTN
NSS
BSS
GPRS PDN
Gb Core Network IP / PPP
IP
Gi
▼ Routing Function
Data transmission between GPRS Support Node (GSN), may occur across external data networks that provide their own
internal routing functions, for example X.25 [34], Frame Relay or ATM networks.
▼ IP interworking
The GPRS Core Network supports interworking with networks based on the Internet protocol (IP). The GPRS Core Network
may provide compression of the TCP/IP header when an IP datagram is used within the context of a TCP connection.
▼ X.25
X.25 PDP Type have been removed from the standard since R99.
▼ Class A
l Operates GPRS and other GSM services simultaneously.
▼ Class B
l Monitors control channels for GSM GPRS and other GSM
services simultaneously,
l but can only operate one set of services at one time.
▼ Class C
l Exclusively operates GPRS services.
▼ Classes A and B
Require dual scanning by the mobile for both GSM and GPRS service requests. Class A or B mobiles are "attached"
simultaneously to both networks.
▼ Class B
The exchange of packets is suspended to answer to an incoming GSM call (the GPRS subscriber is considered to be in the
"busy" or “on hold" state).
The PDP contexts are still active on the SGSN side until the Purge_Timer elapses.
▼ Class C
Exclusively operates GPRS services.
▼ MS type
l Type 1 are simplex MS, i.e. without duplexer: they are not able to transmit and receive at the same time
l Type 2 are duplex MS, i.e. with duplexer: they are able to transmit and receive at the same time
▼ Rx
l Maximum number of received timeslots that the MS can use per TDMA frame. The receive TS shall be allocated
within window of size Rx, but they need not be contiguous. For SIMPLEX MS, no transmit TS shall occur between
receive TS within a TDMA frame. This does not take into account measurement window (Mx).
▼ Tx
l Maximum number of transmitted timeslots that the MS can use per TDMA frame. The transmit TS shall be allocated
within window of size Tx, but they need not be contiguous. For SIMPLEX MS, no receive TS shall occur between
transmit TS within a TDMA frame.
▼ SUM
l Maximum number of transmit and receive timeslot (without Mx) per TDMA frame
Radio timeslot
GSM
network PDN
CS PS
Radio interface
Radio timeslot
GPRS PDN
network
PS
PS
▼ Bit rate
Maximum instantaneous bit rate provides 171,2 kb/s by the allocation of eight RTSs to one subscriber. The stated maximum
bit rates are different, because different coding schemes are used, which impacts the bit rate over a RTS. (see Annex)
GPRS network
Radio timeslot
Radio
Block
10
▼ Caution: Animated slide that does not make sense if not in the slide-show mode.
▼ Optimized use
A radio resource (set of Radio Blocks over one or several RTS) is allocated only when data is being transferred, by
establishing and releasing Temporary Block Flow (TBF), that can be presented as micro-connections, each time a data
transfer has to be sent over the radio interface.
▼ GPRS benefits
l BSS hardware (included OMC-R) is re-used from GSM
l Smooth GPRS introduction
l Higher data throughput thanks to EGPRS (EDGE)
l Data transfers can billed by volume instead of time
l An MS can exchange data by GPRS in parallel with a
conventional GSM call (if MS Class A)
11
▼ BSS is re-used
The same Radio Access Network is re-used, and a Packet Control Unit (PCU) function is implemented in the BSS.
12
▼ Shared = in other words: "the radio resources are shared by statistical multiplexing". As in GSM, no subscriber has their own
permanent radio resource.
▼ High or low bit rates = more than one time slot per MS or conversely, more than MS on the same TS (one TDMA frame
occupies 4.615 ms and is divided into 8 TS or channels).
▼ Maximum instantaneous bit rate provided = 171,2 kbps through the allocation of eight TSs to one subscriber. The stated
maximum bit rates are different (according to the BSS release), because different ways of encoding the data, or "coding
schemes", are used, which impacts the bit rate over a TS. (cf Annex)
▼ Optimized use:refer to Radio resource allocation in the slides to come + radio resource management in the BSS Chapter.The
radio resource allocation is suitable for variable, bursty traffic (downloading Web pages).
▼ Up link (UL) and downlink (DL): It is possible to use a different bandwidth (bit rate) in each transmission direction, whereas in
CS (circuit switching) mode, there is a maximum limit of 9,6 kbps, in both directions and at all times.
▼ QoS: Henceforth, QoS parameters are part of subscription data, according to the wide range of services provided to a
subscriber.
Reliability Class
5 classes acknowledgement of packets
Delay Class
4 classes total delay measured between R or S point and Gi
Precedence Class
3 classes relative importance of service under congestion
13
▼ Precedence class
According to the class, user data packet can be discarded during the transfer due to a congestion state.
3 classes are defined : any, normal, high
▼ Delay class
The delay class depends on the operator network because a measurement is done between the R or S interface (between
the Mobile Terminal and the Terminal Equipment) and the Gi interface. For each operator, delay values are different so delay
classes are a reference not a strict value.
4 classes are defined : best effort, 1, 2, 3
▼ Reliability class
The reliability means that user data packets are acknwoledged during the transfer. The reliability classes are defined
according to the acknowledgement or not of the packet.
5 classes are defined
▼ Throughput class
The throughput class is defined by the 2 following parameters:
l Mean Throughput : 9 classes are defined (from best effort to 111 Kb/s)
l Peak Throughput : 19 classes are defined (from 8 Kb/s to 2048 Kb/s)
14
▼ Retrieval services
Provide the capability of accessing information stored in data base centers. The information is sent to the user on demand
only. An example of one such service in the Internet's World Wide Web (WWW).
▼ Messaging services
Offer user-to-user communication between individual users via storage units with store-and-forward mailbox, and/or message
handling (e.g., information editing, processing and conversion) functions;
▼ Conversational services
Provide bi-directional communication by means of real-time (no store-and-forward) end-to-end information transfer from user
to user. An example of such a service is the Internet's Telnet application;
▼ Tele-action services
Characterized by low data-volume (short) transactions, for example credit card validations, lottery transactions, utility meter
readings and electronic monitoring and surveillance systems.
▼ Distribution services
Characterized by the unidirectional flow of information from a given point in the network to other (multiple) locations.
Examples may include news, weather and traffic reports, as well as product or service advertisements;
▼ Dispatching services
Characterized by the bi-directional flow of information from a given point in the network (dispatcher) and other (multiple)
users. Examples include taxi and public utility fleet services;
▼ Conferencing services
Provide multi-directional communication by means of real-time (no store-and-forward) information transfer between multiple
users.
è True or False ?
15
16
17
© Alcatel University - 8AS 90164 0001 VT ZZA Ed.10
18
▼ Overview NSS
PSTN
MSC/VLR
BSS HLR
with PCU
GPRS
Internet
Core Network
SGSN
GPRS IP
Backbone
GGSN
MS
DNS BG
DHCP
NTP
19
▼ PCU functions
l LLC PDU segmentation / re-assembly into RLC/MAC PDU
l PDCH scheduling (resource multiplexing)
l Channel access control (access requests and grants)
l ARQ function (RLC block Ack / Nak, buffering and retransmission of RLC blocks)
l Radio channel management (power control, congestion control, broadcast control information).
▼ DNS (Domain Name Server) and DHCP (Dynamic Host Convergence Protocol)
▼ NTP server (Network Time Protocol) for GSN synchronization. In general an NTP application does not run on a dedicated
server. The OMC-G can play this role.
▼ HLR (Home Location Register) is involved in MS attachment to the GPRS network (authentication + services subscribed to)
SGSN1
BSS1 GGSN1 IP network 2
IP
backbone
IP network 3
IP network 5
GGSN3
20
▼ The GGSN (Gateway GPRS Support Node) stores subscriber data received from the HLR and the SGSN:
l Subscription information
è IMSI
è zero or more PDP addresses
l Location information
è the SGSN address of the SGSN where the MS is registered
It also manages:
l the allocation and use of dynamic @IP for MS,
l the tunneling and encryption of user data at Gi interface,
l the transfer of user data packets,
l the charging data.
▼ Servers
SGSN
GPRS IP Backbone
GGSN
DNS
DHCP NTP
Name
IP
IP address
address
21
▼ DNS
l Resolve a name into an IP address
l Use in Mobility procedure
▼ DHCP
l Provide dynamically IP addresses
l Split Users into pool of IP addresses
▼ NTP
l Provide one time reference for all the network
l Have a very precise time reference
l Synchronization from satellite
▼ Border gateway
MS
BG
Inter-PLMN
network
BG
GGSN
SGSN HPLMN IP backbone PDN
HPLMN
22
▼ Choice of GGSN
If a subscriber wants to access an Intranet (PDN) in his home country, from the visited PLMN, the selected GGSN is the one
from the home PLMN
For Internet access a GGSN in the visited country could be used.
▼ Interfaces
SMS-
Um BSS A MSC HLR
GMSC
Gs
Mobile Gb Gr Gd
GPRS
Gc
SGSN
Gn
Gi
SGSN GGSN PDN
Signaling + data
23
▼ Signaling protocols
l MAP/TCAP/SCCP/MTP on Gr, Gd and Gc,
l GTP/UDP/IP on Gn,
l BSSAP+/SCCP/MTP on Gs,
l GMM/SM/LLC on Gb/Um.
▼ Gc interface
Used for network-requested PDP contexts activation (GGSN asks the HLR for SGSN routing information).
▼ Gs interface
Defines the Network Mode of Operation I (NMOI). It allows to perform LA + RA combined Location Update, and PS and CS
paging coordination (refer to ANNEX).
▼ Gr interface
Exchange of subscription information at GPRS attachment phase
▼ Additional interfaces
l Gf (to the EIR)
l Gd to deliver the SMS to the mobiles via the GPRS network (SGSN option and subscriber feature)
▼ MS MM states
Stand-by
READY timer expiry
PDU transmission
Ready
GPRS Attach
GPRS Detach
Idle
24
▼ STANDBY State
In STANDBY state, the subscriber is attached to GPRS mobility management. Pages for data or signalling information
transfers may be received. It is also possible to receive pages for the CS services via the SGSN. Data reception and
transmission are not possible in this state.
The MS performs GPRS Routeing Area (RA) and GPRS cell selection and re-selection locally. The MS executes mobility
management procedures to inform the SGSN when it has entered a new RA. The MS does not inform the SGSN on a change
of cell in the same RA. Therefore, the location information in the SGSN MM context contains only the GPRS RAI for MSs in
STANDBY state.
The MS may initiate activation or deactivation of PDP contexts while in STANDBY state. A PDP context shall be activated
before data can be transmitted or received for this PDP context.
▼ READY State
In READY state, the SGSN MM context corresponds to the STANDBY MM context extended by location information for the
subscriber on the cell level. The MS performs mobility management procedures to provide the network with the actual
selected cell. GPRS cell selection and re-selection is done locally by the MS, or may optionally be controlled by the network.
An identifier of the cell, the Cell Global Identity including RAC and LAC, is included in the BSSGP header of the data packet
from the MS; see GSM 08.18 [21].
The MS may send and receive PDP PDUs in this state. The network initiates no GPRS pages for an MS in READY state.
Pages for other services may be done via the SGSN. The SGSN transfers downlink data to the BSS responsible for the
subscriber's actual GPRS cell.
The MS may activate or deactivate PDP contexts while in READY state.
MM Ready Standby
25
▼ IP overview
gtp
tcp 1 tcp 1
Routers
ip ip ip ip ip
SGSN IP network
GGSN
26
GMM/SM SMS IP
NSAPIi
SNDCP NSAPI
Radio layers
27
▼ Transmission plane
Application
Application
IP IP IP
relay
SNDCP GTP GTP
SNDCP
28
▼ GTP (GPRS Tunnelling Protocol) tunnels user data between GPRS Support Nodes in the backbone network. The GPRS
Tunnelling Protocol shall encapsulate all PDP PDUs.
▼ UDP (User Datagram Protocol) carries GTP PDUs for protocols that do not need a reliable data link (e.g., IP), and provides
protection against corrupted GTP PDUs.
▼ IP (Internet Protocol) is the backbone network protocol used for routing user data and control signalling. The backbone
network may initially be based on the IPv4. Ultimately, IPv6 shall be used.
▼ SNDCP (SubNetwork Dependent Convergence Protocol ) maps network-level characteristics onto the characteristics of
the underlying network.
▼ LLC (Logical Link Control) provides a highly reliable ciphered logical link. LLC shall be independent of the underlying radio
interface protocols in order to allow introduction of alternative GPRS radio solutions with minimum changes to the NSS.
▼ Relay. In the BSS, this function relays LLC PDUs between the Um and Gb interfaces. In the SGSN, this function relays PDP
PDUs between the Gb and Gn interfaces.
▼ BSSGP (Base Station System GPRS Protocol) conveys routing and QoS-related information between the BSS and the
SGSN. BSSGP does not perform error correction.
▼ (NS) Network Service transports BSSGP PDUs. NS is based on the Frame Relay connection between the BSS and the
SGSN, and may - multi-hop and traverse a network of Frame Relay switching nodes.
▼ RLC/MAC (Radio Link Control / Medium Access Control). The Radio Link Control function provides a radio-solution-
dependent reliable link. The Medium Access Control function controls the access signalling (request and grant) procedures
for the radio channel, and the mapping of LLC frames onto the GSM physical channel.
29
▼ PDP address
Almost always empty. The network then dynamically assigns (using a DHCP server) an IP address to the subscriber when he
activates his PDP context (seen later).
▼ PDP contexts
Each PDP context can be considered as a BS (basic service = telephony, fax, etc). A PDP context is a dialog session with an
external IP network, identified with an APN. It is not always mandatory to subscribe (in the HLR) to PDP contexts, access to
some networks is free. For a user, the traffic of his different sessions will be recognized in the messages by the use of
different NSAPIs. A user can declare one of his PDP contexts as the default.
▼ Valid APN
Boolean, if YES, indicates that this APN can be reached through the GGSN of the visited FPLMN.
▼ GPRS attachment
HLR
Authent_info_respq)
➁ ⑤
Update_loc_ack()
Insert_subs_data()
Authent_info_req()
Update_loc_req()
SS7
network
⑦
➂ ⑥
Attach-Request (IMSI) ➀
PLMN
MS_authentication_procedure ➃ GGSN
SGSN GPRS IP
backbone
⑧ Attach_resp (P_TMSI)
Attach_complete () ⑨
BSS
30
▼ Attach Request.
l The attach_request message is placed in an LLC frame. ①
l The MS sends its IMSI.
▼ Authentication
The SGSN gets the “authentication triplets” from the HLR:
l triplets request message ②
l triplets response message ③
The SGSN performs the “authentication procedure” with the MS: ④
l triplets request message ②
l triplets response message ③
▼ Location Update
The SGSN performs the “location_update procedure” with the HLR:
l location_update request message ⑤
l the HLR transfers the MS_subscription data to the SGSN ⑥
l the HLR terminates the location_update procedure ⑦
▼ Attach Complete
The SGSN terminates the attach_procedure with the MS :
l attach_accept message ⑧ (with a new P_TMSI allocation)
l attach_complete message ⑨ (since a new P_TMSI has been allocated)
▼ GPRS attachment
SGSN1
TLLI1 PDN1
GGSN1
GPRS IP
backbone
SGSN2
GGSN2 PDN2
GPRS - CN
LLC layer
31
▼ Attached MS
After running the attach procedure, the MS is “GPRS_attached”:
l a logical connection is established between the MS and the SGSN
l connection established between the peer LLC layers in the MS and the SGSN
l this connection is identified by the TLLI (Temporary Logical Link Identity)
l this logical connection remains established until the MS detaches
l the MS can now access to GPRS services and is reachable for GPRS services
GGSN1
PLMN Activate_PDP_req (PDN2) ➀ 4 PDN1
GGSN2
PDN2
BSS
Create_PDP_req (PDN2) 3
5 Create_PDP_resp (@IP_MS)
32
▼ MS IP address
In case of IP PDP_type access with no additional mobile authentication procedure, the MS IP address is provided by the
PLMN, using either the subscription data, or the backbone DHCP server. No additional user authentication is needed on top
of the GPRS authentication mechanisms (i.e. using IMSI and authentication triplets)
GGSN1
PLMN Activate_PDP_req (PDN1) ➀
4
PDN1
TLLI1 SGSN GPRS
backbone Intranet/ISP
⑦ Activate_PDP_resp(@IP_MS)
GGSN2
BSS
Create_PDP_req (PDN1) 3 DHCP
5
6 Create_PDP_resp (@IP_MS)
Address allocation
GPRS Core Network
33
▼ MS address
IP PDP_type access with mobile authentication via a RADIUS. The address allocation server (i.e. DHCP) and/or
authentication server (i.e. RADIUS) may be located within the PLMN or in the ISP/Intranet network. Non-transparent access
is aimed for corporate intranet access, where additional user authentication is often required.
SGSN1
TID1=IMSI+ NSAPI1
TLLI1 PDN1
GGSN1
TID
2=
IM
SI+ IP
GPRS
NS
backbone AP
I2
SGSN2
GGSN2 PDN2
GPRS - CN
34
SGSN1
TID1=IMSI+ NSAPI1
TLLI1 PDN1
GGSN1
TID
2=
IM
SI+ IP
GPRS
NS
backbone AP
I2
SGSN2
GGSN2 PDN2
GPRS - CN
35
U-data @ MS @ MS
U-data
@server @server
MS
U-data @ MS GTP UDP @sgsn
@server PDN
header header @ggsn
within the MS
@ggsn UDP GTP @server U-data
@sgsn header header @ MS
server
36
ftp
MS CG
S_CDR G_CDR
M_CDR GTP’
GPRS
backbone
PDN
SGSN GGSN
BSS
37
CDRs, generated by the xGSN, are then sent to the CG (Charging Gateway) :
l periodically,
l using reliable transfers (GTP over TCP)
The CG forwards those CDRs to external CCBS (Customer Care and Billing System)
▼ CDR content
Here are the main information in the CDR :
l IMSI
l location information (LAC + RAC + Cell)
l APN
l PDP-context identifier
l PDP-context start time and duration
l negotiated QoS
l volume of data sent / received
l source and destination PDP addresses,
l ….
▼ Charging process
SGSN VPLMN
backbone VPLMN
MS
BG
S-CDR CG CCBS
Inter-PLMN
network
BG
CCBS
HPLMN GGSN
CG backbone
PDN
HPLMN G-CDR
38
GPRS Network
Public Internet
39
▼ Encryption
The LLC frame is encrypted, so encryption from the MS to the SGSN and not just on Um.
▼ Firewall
Filtering function installed on routers (ex: GGSN). Packets are rejected by filtering at application level (for example: in http,
some URLs are barred). Also makes it possible to hide the IP addresses of MSs and backbone entities from external hosts
(Network Address Translation function).
▼ Tunneling
Several ways:
l by IPsec (Secured IP) = IP version in which the user data is encrypted (IP datagrams payload but not their header).
Or by Generic Routing Encapsulation (GRE)
l by PPTP (Point-To-Point Tunneling Protocol). Refer to ANNEX for PPP Tunneling.
è True or False?
40
è True or False ?
41
Time allowed :
5 minutes
42
43
44
© Alcatel University - 8AS 90164 0001 VT ZZA Ed.10
▼ Objectives :
l To be able to briefly describe the data
interchange mechanisms through the BSS
▼ Program :
l 3.1 3GPP Position
l 3.2 Alcatel’s Choice
l 3.3 Layered Model
l 3.4 Gb Interface
l 3.5 Radio Interface
45
▼ PCU function
CCU
PCU BSC SGSN
BTS
CCU
Gb
Um
BSC
CCU SGSN
BTS PCU
CCU
CCU Gb
BTS BSC PCU
CCU
Abis
CCU = Channel Control Unit SGSN
PCU = Packet Control Unit
46
▼ PCU functions
RLC and MAC layers: LLC frame transportation (segmentation/reassembly),
l Gb interface end point,
l network access functions (radio resource management),
l radio channel management (power control, congestion control, etc).
▼ CCU functions
l encoding suited to radio channels,
l radio measurements (receive quality, signal level, "timing advance" management).
▼ PCU function
MFS
TRE
BTS BSC
PCU
TRE SGSN
MFS
GSL PCU
Gb
PCU
TRE BSC
BTS
TRE Ater
Abis
mux
Um
47
▼ User plane
IP
LLC LLC
PCU
RLC BSSGP
relay BSS
RLC GP
MAC Frame Frame
MAC relay relay
relay
Physical L2-GCH Physical Physical
Physical L2-GCH
layer layer L1-GCH L1-GCH layer layer
48
▼ For GPRS TRAFFIC, the BSS simply relays the LLC frames between the MS and the SGSN.
▼ BSSGP = BSS Gprs Protocol. Functions:
l to relay LLC frame over the Gb, with no guarantee of integrity (relaying user data and GMM / SM messages : session,
RA_update and paging procedures). Conceals the FR layers for the LLC layer.
l SGSN-MFS signaling = management of Gb interface objects (flush, paging, resume suspend, LLC-discarded and
other procedures).
l cell-SGSN traffic management (identified by BssgpVCs): in particular cell update management (in the same RA): the
BSSGP header always indicates the current cell so if a "ready" MS moves into a new cell, then the SGSN stores this
new cell and sends all the unacknowledged LLC_PDUs to it (DL).
▼ The concept of handover has no meaning in packet switching (GPRS). There is no "circuit" to re-establish!
▼ RLC = Radio Link Control. (Provides a safe link for transporting LLC-PDUs in acknowledged or unacknowledged mode, LLC-
PDU segmentation into blocks and reassembly, management of TBF contexts. RLC depends on the physical bearer: data
encoding, error control and flow control suited to GSM channels.
▼ MAC = Medium Access Control. Multiplexing of RLC frames onto PDCH (transfer of blocks over the different PDCHi).
Including traffic sharing over several TSs or, conversely, the use of one TS for several users.
▼ Signaling plane
BSCGP
BSCGP
L2-GSL L2-GSL
L1-GSL L1-GSL
RRM RRM
relay relay
physical physical
layer layer
Gb
MS Um BTS Abis BSC Ater MFS
49
▼ BSCGP protocol
l administration interface of Radio Resource management :
è (de)allocation of PDCH and MPDCH within a cell
è activation / release of PDCH
l System control information:
è BSC reset procedure
è cell and GIC group state management
l Radio signalling :
è GSM / GPRS paging,
è GPRS access procedure
▼ RMM protocol
l dynamic allocation of Radio Resources to a MS :
è radio blocks from one or several PDCH
è for uplink or downlink data transfers
▼ Managed entities
BSS side GPRS Core Network side
BVCI=2
BVCI=2 PCM
BC NSVC1 PCM
PVC
BC BVCI=1
BVCI=1
BSC1 NSE1 NSE1
BVCI=3
PCM
BC NSVC2 PCM
PVC
BC
BVCI=3
F.R
Network
BVCI=5
BVCI=5 PCM
BC NSVC3 PCM
PVC
BC BVCI=4
BVCI=4
BSC2 NSE2 NSE2
BVCI=6
PCM
BC NSVC4 PCM
PVC
BC
BVCI=6
SGSN
50
▼ For GPRS TRAFFIC, the BSS simply relays the LLC frames between the MS and the SGSN.
▼ BSSGP = BSS Gprs Protocol. Functions:
l to relay LLC frame over the Gb, with no guarantee of integrity (relaying user data and GMM / SM messages : session,
RA_update and paging procedures). Conceals the FR layers for the LLC layer.
l SGSN-MFS signaling = management of Gb interface objects (flush, paging, resume suspend, LLC-discarded and
other procedures).
l cell-SGSN traffic management (identified by BssgpVCs): in particular cell update management (in the same RA): the
BSSGP header always indicates the current cell so if a "ready" MS moves into a new cell, then the SGSN stores this
new cell and sends all the unacknowledged LLC_PDUs to it (DL).
▼ The concept of handover has no meaning in packet switching (GPRS). There is no "circuit" to re-establish!
▼ RLC = Radio Link Control. (Provides a safe link for transporting LLC-PDUs in acknowledged or unacknowledged mode, LLC-
PDU segmentation into blocks and reassembly, management of TBF contexts. RLC depends on the physical bearer: data
encoding, error control and flow control suited to GSM channels.
▼ MAC = Medium Access Control. Multiplexing of RLC frames onto PDCH (transfer of blocks over the different PDCHi).
Including traffic sharing over several TSs or, conversely, the use of one TS for several users.
▼ Protocols
BSS side GPRS Core Network side
BVCI=2
BVCI=1
BVCI=3
BSC1
51
▼ For GPRS TRAFFIC, the BSS simply relays the LLC frames between the MS and the SGSN.
▼ BSSGP = BSS Gprs Protocol. Functions:
l to relay LLC frame over the Gb, with no guarantee of integrity (relaying user data and GMM / SM messages : session,
RA_update and paging procedures). Conceals the FR layers for the LLC layer.
l SGSN-MFS signaling = management of Gb interface objects (flush, paging, resume suspend, LLC-discarded and
other procedures).
l cell-SGSN traffic management (identified by BssgpVCs): in particular cell update management (in the same RA): the
BSSGP header always indicates the current cell so if a "ready" MS moves into a new cell, then the SGSN stores this
new cell and sends all the unacknowledged LLC_PDUs to it (DL).
▼ The concept of handover has no meaning in packet switching (GPRS). There is no "circuit" to re-establish!
▼ RLC = Radio Link Control. (Provides a safe link for transporting LLC-PDUs in acknowledged or unacknowledged mode, LLC-
PDU segmentation into blocks and reassembly, management of TBF contexts. RLC depends on the physical bearer: data
encoding, error control and flow control suited to GSM channels.
▼ MAC = Medium Access Control. Multiplexing of RLC frames onto PDCH (transfer of blocks over the different PDCHi).
Including traffic sharing over several TSs or, conversely, the use of one TS for several users.
Maximum rate
Coding Scheme Modulation
per PDCH (kb/s)
GPRS
CS3 GMSK 15.6
CS2 GMSK 13.4
CS1 GMSK 9.05
52
53
▼ Transmission and reception data flows are the same for GPRS and EGPRS, except for EGPRS MCS-9, MCS-8 and MCS-
7, where 4 normal bursts carry 2 RLC blocks (1 RLC block within 2 bursts for MCS-9 and MCS-8).
▼ Radio blocks are transported on the air interface (Um) over 4 consecutive normal bursts of the TDMA frame.
▼ The GMSK normal burst is composed of 156.25 symbols (1 bit for 1 symbol):
è 6 tail symbols,
è 26 training sequence symbols,
è 114 encrypted symbols,
è 2 stealing flags (2 symbols),
è 8.25 guard period (symbols).
l For GMSK, the radio blocks are transported by 114 x 4 = 456 symbols.
▼ The 8-PSK normal burst is composed of 156.25 symbols (3 bits for 1 symbol):
è 6 tail symbols,
è 26 training sequence symbols,
è 116 encrypted symbols (there is stealing flags),
è 8.25 guard period (symbols).
l For 8-PSK, the radio blocks are transported by 116 x 4 = 456 symbols.
Multi-frame (52)
0 to 3
47 to 50
TS0 51
Block0 Block11
PDCH0
0 1 2 3 4 5 6 7 8 9 10 11
8 physical
channels
PDCH7
54
▼ One TDMA frame = eight TSs, each of 156.25 bits (!). The structure of the bits forms a "burst". One TDMA frame = 4.615 ms.
One 52 multi-frame = 52 * 4.615 = 240 ms
▼ The succession of TSi on a frequency fi forms a channel (UL or DL).
▼ A channel used for GPRS is called a Packet Data CHannel.
▼ Division into blocks: One block = four TS of the same rank on 4 consecutive TDMA frames. This is the radio resource
allocation unit. One block = four TS of 156.25 bits = 625 bits.
▼ In each cell, CS Adaptation according to the radio environment is part of the QoS. It is based on the received signal strength
and its BER. CS3 and CS4 will be available with the B8 BSS release.
▼ Note: A physical channel on a frequency fi in practice includes two frequencies: fi DL and fi UL.
▼ GPRS channels
Um Abis AterMux Gb
MFS
BTS BSC SGSN
(PCU)
Channel
Coding LLC PDUs
Radio blocks RLC/MAC PDU (1600 bytes max)
PDTCH 1 EGCH 1
0 11
PDTCH n EGCH n
0 11
Radio blocks
GMSK: 456 symbols
8-PSK: 464 symbols
55
▼ EGCH
The BSC connects several Abis terrestrial channels (from 1 to 5) to several Atermux terrestrial channels (from 1 to 5) upon
request from the MFS.
This connection is called a EGCH channel, which is controlled by the GCH layer in the BTS and in the MFS.
An EGCH is made up of a pool of GCH (from 1 to 5) ): One main GCH and a pool of auxiliary GCH.
(GCH uses the basic 16k Abis nibble)
PDCH
PBCCH
PCCCH = PPCH + PAGCH + PRACH
MPDCH
PTCH = PDTCH + PACCH
56
▼ For each cell, it is possible to define the MINIMUM and MAXIMUM number of channels reserved for GPRS + the maximum
number of channels reserved for GPRS in case of high traffic load (when the BSC sends "Load indication" to the MFS
through BSCGP protocol).
▼ There are two types of PDCH : MPDCH and SPDCH
l MPDCH = Master PDCH = PBCCH + PCCCH (PPCH + PAGCH + PRACH) -> carries GPRS signaling and system
information.
l SPDCH = Slave PDCH -> carries the user traffic.
▼ Benefits of the Master Channel :
l Preserves CCCH capacity for speech services
l Higher GPRS signaling capacity, in line with GPRS traffic growth
l Differentiated cell re-selection strategy between GPRS and non GPRS MS. When GPRS attached, a MS listen to PSI
broadcast on PBCCH. It allows a finer tuning of GPRS re-selection algorithms, for example in hierarchical networks
(C31 and C32 criteria). Otherwise, MS applies the basic Cell-reselection as in GSM Idle-Mode using the C1 and C2
GSM criteria
▼ UL transfer
start
of TBF1 end of
TBF1
MS network
TBF2 TBF3
TBF4
fULi time
Packet Channel Request
DL PDCHi Ø Ø T T Ø T Ø T T T Ø
in block b
N token =T ?
Y
SEND on block b+1 (TFIk)
57
▼ This slide demonstrate that the radio resources (blocks) are used only when data need to be transferred (LLC-PDU) :
dynamic radio resource allocation. As a matter of fact, an MS shall specify its radio resource request at initiation of each TBF
for a better optimization of radio resource & MS capabilities.
▼ Temporary (Block) Flow Identity = TLLI + sequential number, used by the network to recognize data from different MSs.
Identifies uniquely a TBF in one direction within a cell.
l The blocks are dynamically allocated upon the use of a token (Uplink State Flag) allocated to the MS at TBF
establishment. Any DL block includes a USF in the header.
l The mobile "listens" to the PDCHi assigned, when block b (in DL) contains USF = T, the MS shall send one PDTCH in
UL on block b+1 on the UL PDCHi.
▼ The theoretical maximum of 160 kbit/s is given for one MS which would have 8 PDCHs of 21.4 kbit/s each. Those MS are yet
to be available on the market place.
▼ DL transfer
MFS SGSN MS PDU
DL PDCHj Ø Ø Z Z Ø Z Ø Z Z
N
in block b, TFI=TFIz ?
Y
58
▼ In DL, each time an LLC-PDU is received, if there is no TBF in progress, it is essential to “establish" one.
▼ To respond to the paging, the MS needs to send a "paging response" to the SGSN (GMM) encapsulated in an LLC_PDU.
This response is carried by an UL TBF.
▼ Upon reception of the Paging response, the SGSN can send the DL PDU (LLC frame) to the MS through the MFS.
The MFS shall establish a DL TBF with the MS.
▼ DL TBF: each block of the DL TBF are identified by the DL TFI = TFIz
▼ After completion of the TBF establishment phase, the MS listen to all the DL blocks on the allocated PDCHs and keeps the
blocks tagged with the TFIz.
è True or False?
59
è True or False?
60
61
62
© Alcatel University - 8AS 90164 0001 VT ZZA Ed.10
63
HLR
MSC SCP SMS-C GSM/GPRS common servers
BSS1
B Radio subsystem
T
S BSC
GPRS Core Network
RADIUS
B server
T
S
GGSN1
A9135
SGSN Firewall server
BSS2 MFS
B Intranet
T
S BSC GGSN2
GPRS IP Access router
B Frame
T
backbone
Relay
S
network
external Internet
BSS-- DNS Border
B SGSN Gateway
T
S BSC A9135 NTP server
MFS Inter-PLMN
B
T backbone
S Charging PLMN
Gateway DNS/DHCP server
64
l Existing Alcatel BTS and BSC from GSM are reused for GPRS :
▼ The HLR, MSC, SCP and SMS-C are reused from the GSM-NSS
▼ Functional architecture
Control Subsystem
OMC-R
Ethernet LANs
B
T
S BSC1
GPU 1
B
T
S
GPU 2
SGSN
B GPU x
T
S BSC2
B GPU y
T
S
A-ter interface Telecom Subsystem Gb interface
65
▼ The duplex "Control subsystem" (two DS10 in active/standby mode, with 2 shared disks) :
l only one GPU board supporting each BSC (in the B6.2 release)
l multiple GPU boards supporting each BSC (from the B7 release)
▼ Rack layout
11 BSXTU
BSXTU
11
11 GPU
GPU (+1)
(+1)
maxi
maxi
11 BSXTU
BSXTU
11
11 GPU
GPU (+1)
(+1)
maxi
maxi
22 DS
DS 10
10
Control
Control
sub-rack
sub-rack
22 or
or 44
Switches
Switches
33 COM
COM 3300
3300
++ IOLAN
IOLAN module
module
66
▼ One JBGPU board (= 1 PCU) offers 480 PDCH. Two uses of JBGPUs :
l One JBGPU for each BSC, (Ater interface), so one MFS serves a maximum of 22 BSCs.
l With 240 PDCH per GPU, a BSC can offer up to 6*240 = 1440 PDCH
l To be connected to the FR network (Gb interface).
▼ Fast ethernet Switches (100 Mb/s) made by 3COM: 2 or 4 (as needed) to build LANs to which are connected
l the Nectar stations (DS10)
l GPU boards
l printers and craft terminals (for local management, the terminal is called IMT = Installation & Maintenance
Terminal)
▼ SGSN architecture
CCS
CCSN7
N7 DS10
Gr
DS10 towards
CCS
CCSN7
N7 IP
SGSN router
towards backbones
SS7
DS10
GPU DS10
Pilot servers
GPU
DS10
E1
GPU
towards LSN DS10
Gb SGSN server LAN/IO
67
▼ The SGSN main functions are processed by DS10 Nectar servers, other hardware equipments performing the physical
interfaces towards the networks accessed by the SGSN :
▼ The equipments are gathered around two duplicated LAN at 10/100 Mbits/s:
l LAN I/O (Local Area Network for Input/Output) = 2 fast Ethernet switches :
è communication through IP/Ethernet between the DS10 servers and the SGSN routers
LAN Gi Gp
NS500
GPU Non-pilot Firewall Server
NS500
servers
KVM Switch
Screen Keyboard
PLMN
LSN Ethernet DNS/DHCP
LANIO/Gn
switches switches
68
▼ The E configuration is the smallest one available. It can be software-blocked to 25K, 50K or 75 K MM contexts. Above, the
configuration with co-located GGSN.
lEquipment Quantity
lCMIC couplers 2 to 4
lGPU boards 2 to 6
lGb PCM links Up to 96
lDS10 servers 4 (2 Pilots et 2 non Pilots with SS7 adapter)
lShared Disks 2x18 Gbytes
lRouters 2 or 3
▼ G configuration is the largest one available.
lEquipment Quantity
lCMIC couplers 2 to 4
lGPU boards 8
lGb PCM links 128
lDS10 servers 12 to 14 (2 Pilots, 10 to 12 Non Pilots with SS7 adapter)
lShared Disks 2x18 Gbytes
lRouters 2 or 3
▼ Power Supply:
l48V DC by a Top Rack Unit inside Each rack (GPU sub-rack, Fans, CMIC sub-rack, SGSN router).
l230V AC in Direct Link for each Non Pilot DS10, secured link for the Pilot DS10, Fast Ethernet Switches and RS232
concentrators.
▼ Dedicated OMCs B
T
BSC1 S
B
T
Radio part S
BSC2 B
T
OMC S
-R
MFS
NMC
Q3
SGSN
Core Network part
OMC
-G
Charging
DNS/DHCP NTP BG Gateway
GGSN
69
70
▼ These QoS attributes are associated with a PDP context performed by a R97/98 MS
▼ The five QoS parameters of the standard define more than 60 combinations ! Which is too much and leeds to simplification :
▼ Best effort = inexpensive, comparable to the Internet (no commitment). Ideal for foraging on the internet.
R99 Traffic class Traffic handling priority R97/98 Bearer QoS class
conversational - Premium
streaming - Premium
interactive 1 Premium
interactive 2 Normal
interactive 3 Normal
71
▼ The mapping of R97/98 QoS attributes to R99 QoS is applicable in the following cases :
m hand-over of PDP context from GPRS R97/R98 SGSN to GPRS R99 or UMTS SGSN
m when a R99 MS performs a PDP context activation in a R99 SGSN with a R97/98 GGSN
m when the SGSN has received R97/98 QoS subscribed profile, but the MS is R99
▼ The mapping of R99 QoS attributes to R97/98 QoS is applicable in the following cases :
m when a R99 MS performs a PDP context activation in a R99 SGSN while the GGSN is R97/98
m when the SGSN sends user data to the BSS for a R99 MS
m when the SGSN has received R99 QoS subscribed profile but the MS is R97/98
m in the new SGSN, during an inter-SGSN RA_update procedure, or inter-system change, on receipt of the R99 QoS
attributes from the old SGSN
è True or False?
72
è True or False?
Time allowed :
5 minutes
73
74
75
© Alcatel University - 8AS 90164 0001 VT ZZA Ed.10
20 CS4
Channel rate (kbps)
CS3
15
CS2
10
CS1
0
0 10 20 30 C/I (dBm)
76
l for CS-1: PDCH data rate = 9.05 kbit/s (poor radio conditions or BSS signaling)
l for CS-2: PDCH data rate = 13.4 kbit/s (better radio conditions)
l for CS-3: PDCH data rate = 15.6 kbit/s
l for CS-4: PDCH data rate = 21.4 kbit/s.
Technology
CS data - SMS, 9.6Kbps
HSCSD
GPRS
EDGE
UMTS
1998 1999 2000 2001 2002 2003 2004
77
▼ SMS : With GPRS, the 160-character barrier for short messages will be able to be broken (when SMS over GPRS is
implemented).
▼ High Speed Circuit-Switched Data : This still involves circuit switching, meaning that, with a continuous use of radio
resources, so billed by time. HSCSD is based on the assignment of several traffic channels (TCH) to a single MS to offer a
higher bit rate. HSCSD is suited for services requiring a minimum bandwidth guaranteed.
▼ EDGE : (Enhanced data rates for GSM evolution) is a technology previously developed by Ericsson, based on TDMA and
offering a maximum theoretical speed of 384 kbit/s (8 channels, each 48 kbit/s, using a new modulation scheme: 8-PSK,
eight-phase shift keying, instead of GMSK for GSM and GPRS).
▼ EDGE-specific MTs are required! The BSS remains the same, except for the implementation of EDGE TRX (Evolium product
line).
Alcatel will offer EDGE from release B8 onwards. This is an important step towards UMTS
CCCH
PCCCH
A
MSC/VLR
BSS Gs
(a)
PACCH
SGSN
(b) Um Gb
CS paging for GPRS-attached MS in idle state (a), or in data transfer state (b)
CS paging for non GPRS-attached MS
GPRS paging
78
▼ In this mode, the Gs interface is present in the core network. As far as GPRS-attached MS are concerned, the BSS receives
both GPRS and circuit-switched paging messages from the Gb interface.
▼ There is paging co-ordination because all paging messages towards GPRS-attached mobile stations are sent either on the
Master Channel, if present, or on the CCCH otherwise.
▼ In addition, whilst involved in a packet data transfer the GPRS mobiles receive the circuit-switched paging messages via the
GPRS traffic channel currently used.
▼ NMO II :
l There is neither Gs interface nor Master Channel. There Paging coordination over the CCCH of GSM. Also, GPRS
Mobile Stations operating in Class B may lose CS Paging message if they are not able to monitor CCCH at the same
time.
▼ NMO III:
l In this mode, there is no Paging coordination because Gs interface is not present while the Master Channel is.
Therefore, CS Paging is transmitted over CCCH when PS Paging is transmitted over PCCCH. Class C Mobile are not
able to manage both type of channels.
SGSN HLR
Attach_request (IMSI)
Triplet request
Authentication
Update_location
IMSI ↔ current SGSN
Insert_subscriber_data
Update_location_ack
IMSI ↔ TLLI + current RA + subscription data
Attach_accept (TLLI)
MS ↔ TLLI
79
▼ TLLI: This is allocated to the subscriber on his attachment to the network. In reality, the SGSN allocates the MS a P-TMSI,
from which the MS and the SGSN itself derive the TLLI.
Insert_subscriber_data
Update_location_ack
Location_Update_accept
80
▼ Location-Update-request: The SGSN determines the MSC/VLR based on the RA where the subscriber is located.
▼ At the HLR: If the MS was declared in another MSC, the HLR sends it a Cancel_Location before doing ISD to the new MSC.
▼ Attach-accept: In practice, the SGSN sends the MS the P-TMSI (and not the TLLI) and the V-TMSI (TMSI of the VLR),
designated TMSI here.
▼ Once this combined-attach is done, the MS can make combined LA/RA update procedures (see GSM 03.60)..
new old
SGSN2 SGSN GGSN
Routing_Area_update_req (RA1)
SGSN_context_ack
transfer of stored packets
81
▼ SGSN_context_req:To obtain any PDP contexts and the MM contexts (IMSI, RA, cell, IMEI, etc) = all the data stored in the
old SGSN concerning the MS, including the address of the GGSN related to each PDP context activated.
▼ SGSN_ctxt _ack: This message is sent only if the subscriber has PDP contexts activated. Used to inform the old SGSN that
receives and stores datagrams for the MS.
▼ Update_PDP_context_req: Mainly to inform the GGSN of the address of the new current SGSN for this MS. Thus, any new
packet arriving from the PDP network is routed to the new SGSN.
This operation is carried out in parallel with the retrieval of the old SGSN packets, and not afterwards as the figure above
seems to indicate.
cancel_location (IMSI)
cancel_location_ack
insert_subscriber_data (+ack)
Update_location_ack
Routing_Area_update_accept (TLLI)
Routing_Area_update_complete
82
▼ The tunnel (SGSN-GGSN) moves with the subscriber: The GGSN is always the same and the SGSN is variable (same
TID).
▼ RA update accept: The SGSN allocates the subscriber a P-TMSI or TLLI, as mentioned (derived from the P-TMSI).
HLR SMS-SC
SGSN SMS-GMSC
SM transfer
SRI_for_SM ([GPRS supported])
forward_SM (SM)
SM transfer
forward_SM_res
report
report
83
▼ If the delivery through the GSS fails, the HLR sets the MNRG flag and stores the address of the SMS-GMSC.
GPRS_Attach_request
If MNRG=1
Ready_for_SM (IMSI)
MNRG ← 0
Alert_Service_Center
Alert_Service_Center_ack
84
▼ Mobile user activity procedure: When the MS is reattached, the HLR indicates this to the SMS-GMSC (conventional GSM
"alerting" procedure) and to all the GGSNs which had tried in vain to activate PDP contexts to this MS.
▼ The SGSN sends Ready-for-SM to the HLR before sending the “update location” message.
▼ The SMS-GMSC obviously alerts the SMSC which makes a new attempt to deliver the SM to the mobile (as in the previous
slide).
- @ MS + IP/X25
NSAPI1 + PDP context1 - APN
IMSI ↔TLLI - QoS
NSAPI2 + PDP context2
85
▼ The SGSN even knows the current cell, if the mobile is in the ready state by looking at the routing over the Gb interface of the
PDU originated by the MS. For further explanation, please refer to the sub-chapter “The Base Station Sub-System, The Gb
interface”
access line
PVC DLCI
DLCIm =p
DLCIp
DLC
DLCI=0 (Sig) =m
I
Frame
DLCIb
Relay
DLCIa
PVC
PVC
access line
86
▼ Data Loss: all frames have a CRC field used to determine if the data (payload) is correct or not. The network discards any
frame with an erroneous payload.
PCU1
BSSGP
BSSGP
NSC BC1 = TSa, TSb,...
Frame
Relay BC2 = TSu, TSv,…
SNS NSC
BCa = all TS
Physical
layer SNS
PCMa
Physical
BSSGP PCM1
Frame layer
NSC Relay PCMb
SGSN
Gb BCb
SNS
Physical
Gb
layer PCM2
BC3 = TSi, TSj,… PCM
PCU2 BC4 = TSx, TSy,… Bearer Channel
87
▼ If no FR network, the declarations of the physical and SNS layers must be the same at both ends.
PCU1
BSSGP
BSSGP
Frame Relay NSC
BC1
SNS DLCIm BCa NSC
Physical PVC1 DLCIp
layer
Frame SNS
PVC2 Relay DLCIr
BSSGP Physical
PVC3 PVC4 layer
NSC
DLCIo Gb SGSN
SNS
Gb
Physical BC4 PVC
layer Bearer Channel
PCU2
88
▼ The FR layer is part of the layer 2 in OSI model = Sub-Network Service layer (2.1). On top of this layer, and for telecom and
quality of service purposes was added the Network Service Control layer (2.2).
▼ The "Bearer Channel" object of GPRS corresponds to the notion of FR access line. On a BC, there can be several PVCs
(Permanent Virtual Circuits), each identified by a DLCI, which may be different at each end.
▼ Alcatel has set the limit on the BSS (MFS) side, to one PVC per BC.
▼ There is also, on each BC, a virtual link (with DLCI=0) for signaling with the FR switch.
PCU1
BSSGP
NS-VCI= 11
NSC
BSC1 BSSGP
NSEI=x
SNS
NS-VCI=12
Physical
layer Frame NSC
Relay
BSSGP NS-VCI=13
SNS
Physical Gb Gb SGSN
layer
PCU2 NS-VC
NSE
89
▼ NSE = Network Service Entity, identified by its NSEI, representing the packet traffic to/from a given BSC. The NSE = ΣNS-
VCs dedicated to the packet traffic for one BSC. NSEI is information included in the messages between SGSN and MFS.
BVCI=i PCU1
BVCI=j
BVCI=k
BSC1 BVC
I=i, B
NSC V CI=j,
BVC
I =k
SNS
Physical BSSGP
layer
p
V CI=
n, B
VCI=
, B NSC
BVCI=m I=m
B VC
BVCI=n SNS
BSC2
NSC Physical
BVCI=p
layer
SNS
Physical
cell layer SGSN
BVC PCU2 Gb
NSE
90
▼ NSEI and BVCI are information items included in all messages between SGSN and MFS. This information must be consistent
on either sides of the Gb interface.
1 High priority Service commitments shall be maintained ahead of precedence classes 2 and 3.
3 Low priority Service commitments shall be maintained after precedence classes 1 and 2.
91
92
93
94
95