GENERAL PACKET RADIO SERVICE (GPRS)

Objectives
Understand the GPRS network architecture and fundamental concepts. Understand the nodes that make up the GPRS network. Understand the key interfaces between GPRS nodes. Examine usage scenarios to see how data is routed through the GPRS network Understand all the layers of the GPRS stack

Contents
Mobile Wireless data Introduction to GPRS General Aspects Quality Of Service Network Architecture GPRS Protocol Stack Physical Layer RLC/MAC (Radio Link Control/Medium Access Control) RRM (Radio Resource Management) Frame/Relay/Network Service BSSGP (Base Station Subsystem GPRS Protocol) LLC (Logical Link Control) SNDCP (SubNetwork Dependent Convergence Protocol) GTP (GPRS Tunneling Protocol) GMM (GPRS Mobility Management) SM (Session Management)

Mobile Wireless Data

What is Mobile Wireless data?

Transmission of data using wireless interface
Fixed User

Cellular Wireless Network

Wireline Data Network

Air Interface
Mobile Users Data Voice

Wireless data networks should provide the following functionalities:

Network access Radio resource management Logical link management Packet routing and transfer Mobility management Network management
5

Differences between wireless and wireline networks Air Interface

- Error prone medium - Spectrum is limited

Mobile Wireless Data

Wireless Network
- Link Layer must be established - Delay of data transmissions

User can move

- Mobile location not always known - Handoffs required

Wireless data terminal

- Power consumption - limited battery life - smaller devices

Additional security issues

6

Mobile Wireless Data

Access Requirements for Wireless Data

Radio Link Protocol (RLP) for error recovery
- L2 protocol over the air interface - Designed specifically to support data services - Provides reliable data links between mobile and wireless system

Fraud prevention - need stringent security Mobility support for wireless data Enhanced privacy for sensitive data Support for existing wireline protocols Compensation for slower data rates over wireless than wireline
7

Network Requirements for Wireless Data

How does network know about mobile?
- Registration

How does mobile originate/terminate a data session?

- Call setup/termination (circuit) - Packet delivery (packet)

What happens when user moves around?

- Nomadic computing: access the network from any fixed location. - Mobile computing: ability to be mobile while the data user is still connected to network.

Network Requirements contd

How are computing addresses mapped to MS addresses
- e.g. for IP, need IP address/IMSI mapping functionality

How does network deter fraud?

- Additional security and privacy mechanisms

How do data applications work over wireless? - Adaptation with WAP, etc

GPRS - General Aspects

10

Why GPRS ?
Provide true packet data on GSM networks

Faster data rates than Circuit Switched data More bandwidth efficient for asymmetric bursty traffic Allows for effective resource management (bandwidth and hardware) Use of existing GSM radio physical layer

Cost effective for network operator

Provides evolution path for the future

higher layers are independent of the radio technology

11

GPRS - Service

GPRS - General Aspects

GPRS is defined in the ETSI standards GPRS is an entirely new GSM service

Targeted toward computer applications (email, Web) 9.05 Kbps to 171.4 Kbps to one user Allows for higher speed and bandwidths

12

GPRS Service contd

Point to multipoint

broadcast services
traffic messaging weather conditions

subscribed services
market reports

support of different protocols

IP X.25

13

Classes of Mobile
Class A simultaneous execution of circuit switched and GPRS operation is possible Class B simultaneous execution of signalling for both circuit switched and GPRS operation is possible GPRS traffic will be suspended during a pending or an established circuit switched connection Class C

alternate use of circuit switched and GPRS operation

14

Network Modes of Operation

Network Mode I

paging coordination
same channel for circuit switched and packet switched services either CCCH or PCCH in idle mode packet data channel in transfer mode

combined procedures performed by Class A and B radios

no paging coordination always use CCCH PCCCH not present in the cell
15

Network Mode II

Network Modes contd

Network Mode III

no paging coordination circuit switched services always on CCCH packet switched services either on CCCH or packet data channel

16

Typical GPRS mobile operation

Power On - Carrier selection PLMN selection Cell selection Registration - GPRS Attach Connection set up - PDP context activation Traffic exchange or Data Transfer Connection termination - PDP context deactivation Power Off - GPRS detach
17

Call Flow Diagram

BSS
SGSN GGSN

PDN

Link Establishment

Registration (Authentication/Identification)

Session Activation

Data Transfer (Mobile to Network and Network to Mobile)

Session Deactivation

De-Registration Link Release

18

Basic GPRS operation

Attachment: mobile sends attach request to SGSN via the BSS SGSN performs authorization check, authenticates user, and determines if it is willing / able to provide requested QoS if attach request is accepted, SGSN must keep track of mobile as it moves around within the SGSNs coverage area PDP context activation: PDP addresses are anchored by a GGSN, i.e. all packet data traffic from the public PDN for a particular PDP address goes through the GGSN activating a PDP address sets up an association between the mobiles current SGSN and the GGSN that anchors that PDP address the record that the GSNs use to record this association is called a PDP context
19

Basic GPRS operation... contd

Data transfer Network to mobile: packets originating in the public PDN reach the GGSN that anchors the PDP address which was previously activated by the mobile the GGSN uses the PDP context information to route the packets to the mobiles serving SGSN the SGSN forwards the packets to the mobile Mobile to network: packets sent by the mobile are received by the serving SGSN the SGSN then forwards the packets to the GGSN which anchors the mobiles activated PDP address
20

Basic GPRS operation... contd

Data transfer Network to mobile: packets originating in the public PDN reach the GGSN that anchors the PDP address which was previously activated by the mobile the GGSN uses the PDP context information to route the packets to the mobiles serving SGSN the SGSN forwards the packets to the mobile Mobile to network: packets sent by the mobile are received by the serving SGSN the SGSN then forwards the packets to the GGSN which anchors the mobiles activated PDP address
21

Basic GPRS operation... contd

Inter-GSN communication is done using tunnelling Tunnelling involves wrapping network-layer packets inside another header so that they can be carried as normal IP traffic through the intra-PLMN backbone network Once received by the far-end GSN, the extra header is discarded an the packets are routed to their final destination based on the original header information Tunnelling takes place in both the MS to network and Network to MS directions

22

Mobile Identities
External Identities Internal Identities Global Over Radio Over Network

23

External Identities
Visible to user or external networks IPV4 Address or IPV4 logical name static or dynamic IPV6 Address or IPV6 logical name X.25 Address Phone number used for circuit switch call Other protocol address Access Point Name (APN) Defines GGSN that handles the context of MS In addition, a route from GGSN to external networks

24

Internal Identities Global

IMSI (International Mobile Subscriber Identity) Similar to GSM, stored in SIM Three parts MCC : Mobile Country Code (Identify country) MNC : Mobile Network Code (Identify PLMN) MSIN : Mobile Subscriber Identification Number (Identify subscriber) Used for generating other identities IMEI (International Mobile Equipment Identity) Similar to GSM, the identifier of the device IMEI-SV Similar to GSM, software version of the MS

25

Internal Identities over network

TID (Tunnel Identifier) GSN Number GSN Address GSN Name BSSGP Virtual Connection Identifier (BVCI) Network Service Virtual Connection Identifier (NS-VCI) Network Service Virtual Link Identifier (NS-VLI)

26

Mobile-originated packet transfer

Packet Channel Request (PRACH) Packet Uplink Assignment (PAGCH)

TBF RLC/MAC data block Packet Uplink ACK/NACK

27

Quality of Service

28

Quality of Service

QoS Parameters
QoS requirements of typical mobile packet data applications are very diverse (Eg. Real-time multimedia, web browsing, e-mail, chat, etc). GPRS allows defining QoS profiles by using the parameters:

Service precedence Reliability Delay Throughput

QoS profiles are negotiated between the MS and the network for each session, depending on the QoS demanded and the current available resources. Billing of the service is based on transmitted data volume, type of service and the chosen QoS profile.
29

Quality of Service

QoS Parameters - Service Precedence

It is the priority of a service in relation to another service. There exists 3 levels of priority: high, normal and low.

30

Quality of Service

QoS Parameters - Reliability

It indicates the transmission characteristics required by an application. Each reliability class guarantees certain max values for probability of loss, duplication, missequencing and corruption (undetected error) of packets.

31

Quality of Service

QoS Parameters - Delay

Delay is the end-to-end transfer time between two communicating MSs or between a MS and the Gi interface to an external PDN, it includes the delay for request and assignment of radio resources and the transit delay in the GPRS backbone network.

32

Quality of Service

QoS Parameters - Throughput

Throughput specifies the maximum/peak bit rate and the mean bit rate.

33

Network Architecture

34

Network Architecture
SMS-GMSC SMS-IWMSC

GPRS - Network Architecture

SM-SC C HLR

E Gd MSC/VLR A TE R MT Um BSS Gs Gb SGSN Gp D

Gr Gn

Gc GGSN Gi PDN TE

SGSN
Gn GGSN
Other PLMN

EIR
Gf Signaling Signaling & Data 35

GPRS Signaling Plane

GPRS - Network Architecture

Application IWU GMM/SM LLC R R M RLC MAC RLC MAC GSM RF Um BSS LLC Relay BSSGP Network Service L1bis Gb Relay GMM/SM GTP UDP / LLC TCP BSSGP IP Network Service L1bis SGSN L2 L1 Gn IP/X.25 GTP UDP / TCP IP L2 L1 GGSN Gi End node IP X.25

GSM RF MS

36

GPRS Data Transmission Plane

Application IP / X.25/IWU SNDCP LLC R R M RLC MAC RLC MAC GSM RF LLC Relay BSSGP Network Service L1bis G b Relay SNDCP GTP UDP / LLC TCP BSSGP IP Network Service L1bis SGSN L2 L1 IP/X.25 GTP UDP / TCP IP L2 L1 IP X.25

GPRS - Network Architecture

GSM RF

MS

Um

BSS

Gn

GGSN

Gi

End node

37

Existing Circuit Mode Entities

SMS-GMSC SMS-IWMSC

GPRS - Network Architecture

SM-SC C HLR

E Gd MSC/VLR A TE R SGSN Gn GGSN

Other PLMN

Gs Gb

Gr Gn

Gc GGSN Gi PDN TE

MT Um

BSS

SGSN Gp

EIR
Gf Signaling Signaling & Data 38

Mobile Switching Centre + VLR

Class 4 switch GSM Mobility Management GSM Supplementary Services Visiting Location Register (VLR)

GPRS - Network Architecture

Local cache of HLR data for users in MSC coverage area

Modem bank for circuit mode data service interworking into POTS network
39

Interworking Function (IWF)

Home Location Register - HLR

GPRS - Network Architecture

Database of User Account information GSM Mobility Management Generates Authentication challenge/response

VLR caches several challenge/response pairs to minimize VLR-HLR traffic

40

GPRS - Network Architecture

SMS-GMSC and SMS-IWMSC

SMS-GMSC

=> Short Message Service Gateway MSC

SMS-IWMSC => Short Message Service InterWorking MSC

Gateway between MSC and SMS Service Center

41

SMS Service Centre

GPRS - Network Architecture

Point-to-point SMS (not Cell Broadcast) Forwards and stores SMS messages Interface between GSM PLMN and rest of the world (email, Web, etc.) for SMS

42

GPRS - Network Architecture

Equipment Identity Register - EIR

Database of valid/invalid IMEIs

43

Base Station Subsystem - BSS

Base Transceiver Station (BTS)

GPRS - Network Architecture

Up to 250 per BSS, trend is towards more Abis is typically daisy chained to reduce costs

Base Station Control (BSC) Transcoder (XCDR)

BTS

BSC
BTS
Ater Abis

XDCR
A

44

Mobile Station MS Terminal Equipment - TE Mobile Station (MS)

GPRS - Network Architecture

MS consists of Mobile Equipment (ME) plus SIM ME contains IMEI SIM contains IMSI, TMSI, Kc and A3/8 algorithm
May be external to ME or internal External is typically a notebook computer, etc. Internal is Nokia 9000, etc.
45

Terminal Equipment (TE) is data terminal

Entities New for GPRS

SMS-GMSC SMS-IWMSC

GPRS - Network Architecture

SM-SC

E
Gd MSC/VLR A TE R SGSN MT Um BSS Gs D

C
HLR Gr Gn Gc GGSN Gi PDN TE

Gb
SGSN Gp

EIR

Gn

GGSN
Other PLMN

Gf Signaling Signaling & Data

46

Gateway GPRS Support Node - GGSN Gateway between GPRS PLMN and other packet data networks

GPRS - Network Architecture

IP networks / Internet X.25

to SGSN

to HLR Gc GGSN PDN

Functions

Message screening Gn Gi Billing data collection Relaying and Routing Address Translation and Mapping Encapsulation and Tunnelling (GTP) Mobility Management (PDP context management)

47

Serving GPRS Support Node - SGSN

GPRS - Network Architecture

Authentication and Admission Control Billing Data Collection Relay, Routing, Address Translation to SMS-GMSC and Mapping SMS-IWMSC Encapsulation and Tunnelling Gd HLR Domain Name Server Gr Gs to to Mobility Management SGSN BSS Gb Gn GGSN Ciphering (LLC Layer) Gn Logical Link Management (LLC) To SGSN (or GGSN in other PLMN) Compression (SNDCP Layer)
48

GPRS - Backbone
SMS-GMSC SMS-IWMSC

SM-SC
C HLR

E Gd MSC/VLR A TE R SGSN Gn GGSN

Other PLMN

Gs Gb

Gr Gn

Gc
GGSN Gi PDN TE

MT Um

BSS

SGSN Gp

EIR Gf Signaling 49 Signaling & Data

GPRS Backbone contd

Gn Interfaces

GPRS - Network Architecture

SGSN<->GGSN internal to PLMN SGSN<->SGSN internal to PLMN SGSN<->GGSN external to PLMN

Signaling Plane
Data Plane

Gp Interface

IP based

IP X.25 GTP TCP IP Lower Layer(s) UDP

TCP or UDP allowed

Tunneling (Data plane) Mobility Management (Signaling plane) GSM 09.60

GPRS Tunnel Protocol (GTP)NEW

50

GPRS - PROTOCOL STACK

Physical Layer Physical Link Layer RLC/MAC (Radio Link Control/Medium Access Control) RRM (Radio resource Management) LLC (Logical Link Control) SNDCP (SubNetwork Dependent Convergence Protocol) BSSGP (Base Station Subsystem GPRS Protocol) GTP (GPRS Tunneling Protocol) GMM (GPRS Mobility Management) SM (Session Management) Recap of the State Models.
51

The Protocol Suit

GPRS - Protocol Stack

IP

X.25

Subnetwork Dependent Convergence Protocol (SNDCP) Logical Link Control (LLC) Layer Radio Link Control/Medium Access Control (RLC/MAC) Layer GPRS Physical Layer

} }

Implemented in GGSN Implemented in SGSN

Implemented in BSS

52

Physical Layer

53

Logical Channels

PHYSICAL LAYER

CCCH used for initial access in some cells Packet Data Channel (PDCH) Packet Common Control Channel (PCCCH) 52 multiframe or existing CCCH 51 multiframe Packet Broadcast Control Channel (PBCCH) Packet Access Grant Channel (PAGCH) Packet Paging Channel (PPCH) Packet Data Traffic Channel (PDTCH) Packet Associated Control Channel (PACCH)

Packet Timing Control Channel (PTCCH)

54

Channel Combinations

PHYSICAL LAYER

3 additional packet channel combinations (multiframe types)

Type 11 : PBCCH+PDTCH+PACCH+PTCCH Type 12 : PBCCH+PCCCH+PDTCH+PACCH+PTCCH Type 13: PDTCH+PACCH+PTCCH

Type 13 is used for packet channel set up with CCCH.

55

52 Multiframe Structure

PHYSICAL LAYER

Similar to TCH multiframe but twice as long Blocks are rectangularly interleaved on 4 bursts as on CCCH and SDCCH No predefined substructure, contents of each block determines the logical channel type of the block
TCH 26 Multiframe

GPRS 52 multiframe

4 bursts = 1 block

Idle frame (used for measurements)

56

Multislot Mobile Stations

29 multislot classes Semi-duplex (12 classes)

PHYSICAL LAYER

TDMA frame

cannot TX and RX simultaneously but must TX and RX every TDMA frame

Similar multiplexing to GSM voice mobile Up to 4 TS downlink and 1 TS uplink, or 2 TS downlink and 2 TS uplink
TDMA frame

Full duplex (6 classes)

TX and RX are not coordinated Up to 8 TS downlink and 8 TS uplink Half duplex (11 classes)

cannot TX and RX simultaneously but can TX or RX continuously for long intervals Up to 8 TS downlink OR 8 TS uplink Cheaper and lower power than Full duplex and more throughput than Semi-duplex

TDMA frame

57

Channel Coding
4 new channel coding schemes defined

PHYSICAL LAYER

CS-1 is identical to CCCH and SDCCH coding CS-2 and CS-3 are punctured versions of CS-1 with precoded USF bits and a 16 bit CRC CS-4 has USF precoding and 16 bit CRC only, no coding
Coding Scheme CS-1 CS-2 CS-3 CS-4 Code Rate 1/2 ~2/3 ~3/4 1 Block Size (Octets) 23 33 39 53 Data Rate (Kbits/sec) 9.05 13.4 15.6 21.4

58

Cell Reselection

PHYSICAL LAYER

MS performs cell reselection in Idle Mode and in Transfer Mode

No handovers MS aborts data transfer when it decides to reselect to a new cell

MS monitors neighbour cell BCCH/PBCCH in Idle Mode and in Transfer Mode New reselection criteria are used when PBCCH is present in the cell
59

Radio Link Control/Medium Access Control [ RLC/MAC ]

60

Layered Overview
MM sublayer LLC sublayer
RR-SAP GMMRR-SAP GRR-SAP

RLC/MAC

RR sublayer RR management

non-RR

RR PD

RR

upper layers' PDUs

RLC/MAC
PBCCH PCCCH PACCH PDTCH

SAPI 0 RACH PCH SDCCH FACCH SACCH AGCH

SAPI 3 SACCH

BCCH

SDCCH

Data Link layer (signalling layer 2)

PDCH

Physical Link layer

61

Input-Output

RLC/MAC

UPPER LAYER PDU [ LLC FRAME ]

RLC/MAC

RLC/MAC BLOCK [ RADIO BLOCK ]

62

TBF : The K(ey) - word

RLC/MAC

A Temporary Block Flow (TBF) is a physical connection used by the two RR entities to support the unidirectional transfer of LLC PDUs on packet data physical channels The TBF is allocated radio resource on one or more PDCHs and comprises a number of RLC/MAC blocks carrying one or more LLC PDUs. A TBF is temporary and is maintained only for the duration of the data transfer Each TBF is assigned a Temporary Flow Identity (TFI) by the network that is unique among concurrent TBFs in the same direction (uplink or downlink) on all PDCHs used for the TBF

63

Idle<->Transfer Modes
PACKET IDLE MODE TBF does not exist

RLC/MAC

mobile does not occupy a radio resource mobile monitors PBCCH and PCCCH

No more blocks to transmit

Trigger from upper layer

PACKET TRANSFER MODE

mobile occupies a radio resource TBF exists mobile is transferring LLC frames

64

Functional Split
RLC Segmentation Re-assembly Sequencing Backward Error Correction

RLC/MAC

RLC/MAC

MAC

Procedures that enable multiple user equipment to share a common transmission medium. Contention resolution Queuing and scheduling of access attempts

65

Packet Data CHannel Characteristics

RLC/MAC

Shared

Channel

Assigned to one or more UEs

PDCH

One phase or Two phase access procedures Different Medium Access Modes Can be assigned for both uplink and downlink TBF

66

Initial Access

RLC/MAC

Nearly identical procedures are defined for the CCCH and PCCCH If PCCCH exists in a cell, these MAC procedures are performed on PCCCH If no PCCCH exists in a cell, these MAC procedures are performed on CCCH

67

Initiation of Packet Access Procedure

RLC/MAC

Mobile schedules PACKET CHANNNEL REQUEST on PRACH channel 8 bit or 11 bit format Indication of the purpose of radio resource like user data/ page response/ MM procedure/ measurement report Indication about the preferred access type Monitors PCCCH group for an assignment message

68

Packet Assignment Procedure

same PCCCH on which it has received PACKET CHANNEL REQUEST

RLC/MAC

On receipt of PACKET CHANNEL REQUEST, network sends PACKET UPLINK ASSIGNMENT on the On receipt of a PACKET CHANNEL REQUEST message with establishment cause indicating

Two Phase Access Request or Single block without TBF establishment, the network may
allocate a single radio block on an uplink PDCH In order to force the mobile station to make a two phase access, the network may allocate a single radio block on an uplink PDCH with any of the other access types If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT message and the mobile station has not indicated Single block without TBF establishment in the PACKET CHANNEL REQUEST message, the mobile station shall proceed with the two phase packet access procedure If the mobile station has been allocated a single block in the PACKET UPLINK ASSIGNMENT

message and the purpose of the packet access procedure is to send a Measurement Report
message and the mobile station has indicated Single block without TBF establishment in the PACKET CHANNEL REQUEST message, the mobile station shall proceed with measure report procedure 69

Channel Assignments

RLC/MAC

Uplink Assignment

A set of PDCHs to be used for the uplink transfer and the associated paramenters A unique Temporary Flow Identity A TBF Starting Time indication

Downlink Assignment

A set of PDCHs to be used for the downlink transfer and the associated parameters A unique Temporary Flow Identity A TBF Starting Time indication

70

Access + Transfer mode Parameters

Access Type

RLC/MAC

Access Mode

PDCH

TBF mode

RLC mode

71

Access Types
All the resource is Allocated at one step A defined contention Resolution mechanism One Phase Access

RLC/MAC

Two Phase Access

Resource is Allocated in two steps A defined contention Resolution mechanism

72

One Phase Access Contention Resolution

RLC/MAC

1. The UE shall send RLC data blocks with the extended RLC Header to include the TLLI of the user equipment. 2. The network shall respond by including the TLLI in the PACKET UPLINK ACK/NACK message after the first correctly received RLC data block that comprises the TLLI. 3. The contention resolution is completed on the network side when the network receives a TLLI value identifying the user equipment. 4. The contention resolution is completed on the user equipment side when the UE receives a PACKET UPLINK ACK/NACK message with the same TLLI as the user equipment has included in the RLC header of the first RLC data blocks. 5. if the user equipment receives a PACKET UPLINK ACK/NACK message with the right TFI but with another TLLI than the user equipment has included in the RLC header of the first RLC data blocks, the contention resolution is declared failed.

73

1 Phase Contention Resolution

MS
PACKET CHANNEL REQUEST
REF NO, CAUSE/ACCESS TYPE

RLC/MAC

NW

PRACH

PACKET UPLINK ASSIGNMENT

REF NO, PDCHS, TFI, TBF ST

PAGCH

RLC DATA PDTCH

TLLI

RLC DATA
TLLI

PDTCH

PACKET UPLINK ACK/NAK

TLLI

PACCH

74

Two Phase Access Contention Resolution

RLC/MAC

1. The network sends PACKET UPLINK ASSIGNMENT message with a Single Block allocation, denoting two phase access to the user equipment. 2. UE sends a PACKET RESOURCE REQUEST message in that single block PDPCH. In this message, the UE shall indicate TLLI value and the number of data octets it has to deliver. The value = 0 => an open ended TBF. 3. The network shall respond by sending PACKET UPLINK ASSIGNMENT message including the TLLI value. 4. The contention resolution is completed on the network side when the network receives a TLLI value identifying the user equipment. 5. The contention resolution is completed on the user equipment side when the user equipment receives a PACKET UPLINK ASSIGNMENT message with the same TLLI as the user equipment has included in the PACKET RESOURCE REQUEST message. 6. The contention resolution has failed on the user equipment side when the user equipment does not receive a PACKET UPLINK ASSIGNMENT message with its TLLI.
75

2 Phase Contention Resolution

MS NW

RLC/MAC

PACKET CHANNEL REQUEST

REF NO, CAUSE/ACCESS TYPE

PRACH

PACKET UPLINK ASSIGNMENT

SINGLE BLOCK ALLOC STRUCTURE

PAGCH

PACKET RESOURCE REQUEST

TLLI, ACCESS MODE, RLC MODE, OCTET COUNT

PACCH

PACKET UPLINK ASSIGNMENT

TLLI, PDCHs, TFI,

PACCH

76

(Medium)Access Modes
Fixed mode

RLC/MAC

Fixed Allocation characterised by fixed allocation of radio blocks and PDCHs in the assignment message without an assigned USF

Dynamic mode

Dynamic Allocation, characterised by that the mobile station detecting an assigned USF value for each assigned PDCH and block or group of four blocks that it is allowed to transmit on that PDCH

Extended Dynamic mode

Extended Dynamic Allocation characterised by the mobile station detecting an assigned USF value for any assigned PDCH allowing the mobile station to transmit on that PDCH and all higher numbered assigned PDCHs In the same block or group of four blocks

77

Fixed Access Mode

RLC/MAC

The network sends PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message containing a Fixed Allocation structure. The fixed allocation structure contains the TIMESLOT_ALLOCATION flag that indicates 1 to 8 time slots that are allocated for packet data transmission, taking into account the multi-slot restrictions of the user equipment. It also contains the ALLOCATION_BITMAP that indicates blocks/block periods that are assigned to the allocation. The user equipment shall transmit an RLC/MAC block on each assigned PDCH on those time slots indicated in the TIMESLOT_ALLOCATION flag field in each block period indicated in the ALLOCATION_BITMAP.

78

Fixed Allocation
TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7

RLC/MAC

B0 B1 B2 B3 B4
Indicates the allocated blocks

B5

.
B10 B11

.
Multi-frame blocks
79

Dynamic Access Mode

RLC/MAC

The network sends PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message containing a Dynamic Allocation structure.
The dynamic allocation structure contains one USF value / PDCH for all the PDCHs assigned to that UE.

Whenever the user equipment detects the assigned USF value, on an assigned PDCH, it shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH.
The time relation between the uplink block, which the mobile station shall use for transmission, and the occurrence of the USF value is pre-defined The number of RLC/MAC blocks to transmit is controlled by the USF_GRANULARITY parameter characterising the uplink TBF.

80

Dynamic Allocation

RLC/MAC

TS0

TS1

TS2 USF= MY_USF

TS3

TS4

TS5

TS6

TS7

B4

B5

MY DATA

81

Extended Dynamic Access Mode

Allocation medium access method to allow higher uplink throughput

RLC/MAC

The Extended Dynamic Allocation medium access method extends the Dynamic

The network sends PACKET UPLINK ASSIGNMENT that allocates to the mobile a
subset of 1 to N PDCHs based on the multislot class The mobile station shall monitor its assigned PDCHs starting with the lowest numbered PDCH, then the next lowest numbered PDCH, etc

Whenever the user equipment detects the assigned USF value, on an assigned
PDCH, it shall transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH and all the higher numbered PDCHs The time relation between the uplink block, which the mobile station shall use

for transmission, and the occurrence of the USF value is pre-defined

The number of RLC/MAC blocks to transmit is controlled by the USF_GRANULARITY parameter characterising the uplink TBF.
82

Extended Dynamic Allocation

RLC/MAC

TS0

TS1

TS2 USF= MY_USF

TS3

TS4

TS5

TS6

TS7

B4

TS0

TS1

TS2 MY DATA

TS3

TS4 MY DATA

TS5

TS6 MY DATA

TS7

B5

Allocated timeslots as PDCHs Sending data on all higher numbered PDCHs

83

TBF Modes

RLC/MAC

Open Ended

Close Ended

The UE can indicate in the PACKET RESOURCE REQUEST message, the number of data octets it has to deliver in the RLC_OCTET_COUNT field. The value = 0 => a request for open ended TBF. If the PACKET UPLINK ASSIGNMENT / PACKET TIMESLOT RECONFIGURE message contains the RLC_DATA_BLOCKS_GRANTED field, the TBF is a close-ended TBF. else, the TBF is open-ended. During a close-ended TBF the UE shall transmit only the number of RLC data blocks indicated in the RLC_DATA_BLOCKS_GRANTED field. RLC/MAC control blocks and retransmissions of RLC data blocks do not count towards the limit. If the number of RLC data blocks granted is not sufficient to empty the UEs send buffer, the UE shall attempt to establish a new uplink TBF by sending a PACKET RESOURCE REQUEST message

84

RLC Modes

RLC/MAC

Ack Mode

The transfer of RLC data blocks in the acknowledged mode uses selective retransmissions of RLC data blocks. The transmitting side numbers the RLC data blocks via the block sequence number BSN. The BSN is used for retransmission and for re-assembly. The receiving side sends PACKET Ack/Nack messages to request retransmission of RLC data blocks.

Unack Mode

The transfer of RLC data blocks in the unack mode does not include any retransmissions, except during the release of an uplink TBF where the last transmitted uplink block may be retransmitted. The block sequence number BSN in the RLC data block header is used to number the RLC data blocks for re-assembly. The receiving side sends Packet Ack/Nack messages to convey the necessary control signalling (e.g. monitoring of channel quality for downlink transfer or timing advance or transmit power correction for uplink transfers)

85

RLC ARQ Operation

RLC/MAC

MS
RLC Data Block RLC Data Block . . . RLC Data Block Packet Uplink Ack/Nack RLC Data Block

BSS
PDTCH PDTCH PDTCH PACCH PDTCH PDTCH PDTCH
86

RLC Data Block . . . RLC Data Block

ARQ Bit Map

Final

RLC/MAC

Start Sequence Number (SSN)

64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

Final Ack Indication 0 = entire TBF NACKed 1 = entire TBF ACKed

SSN-x, for x=1 to 64 0 = NACK 1 = ACK

87

General Procedures : UE side

RLC/MAC

System info on BCCH

Acquisition of SI

Discontinuous Reception

TLLI Management

System info on PBCCH

Cell reselection

Frequency Parameters

Measurement Reporting

88

General Procedures : N/W side

RLC/MAC

System info broadcasting on BCCH

System info On PACCH

Measurement procedure

System info Broadcasting on PBCCH

Cell change procedure

89

Paging Procedure

RLC/MAC

Paging for circuit mode establishment Sent on PCH or PPCH in Idle Mode Sent on PACCH in Transfer Mode Paging for downlink packet transfer MS is paged only if SGSN Ready Timer is expired MS BSS SGSN
Packet Paging Request LLC frame LLC frame LLC frame Packet Paging Request LLC frame LLC frame Paging PS LLC frame LLC frame LLC frame Paging PS LLC frame LLC frame
Ready Timer running 90

RLC/MAC Block Structure

RLC/MAC Block MAC Header RLC Header RLC/MAC control message

RLC/MAC

RLC/MAC Block MAC Header RLC Header RLC data unit spare

91

RLC/MAC Control Block

RLC/MAC

Downlink
MAC header RLC Header RLC Header 23 Control message E

Uplink

MAC header

optional

Control message

23

92

RLC/MAC Data Block

Downlink
MAC header
RLC Header RLC Header RLC Header E E optional

RLC/MAC

Uplink
MAC header
RLC Header RLC Header RLC Header E E

. . .
User Data

. . .
optional

TLLI

User Data
93

Radio Resource Management [RRM]

94

RRM

RRM
Between MS and BSS Asymmetric MS Cell Selection, reselection Measurement reporting Camping BSS channel allocation based on demand Handoff, command cell change load balance

95

RRM

Radio resource states

Mobile can be in one of two states: Packet idle: mobile does not occupy a radio resource TBF does not exist mobile monitors PBCCH and PCCCH LLC frames Set up TBF Packet transfer: mobile occupies a radio resource TBF exists mobile is transferring LLC frames

Packet Idle

No LLC frames to send

Packet transfer

96

Logical Link Control [ LLC ]

97

Functional Model
GPRS Mobility Management Layer 3
LLGMM LLGMM LL3 LL5 LL9 LL11 LLSMS

LLC

SNDCP

SMS

LLC layer
Logical Link Entity SAPI=7

Logical Link Management Entity

Logical Link Entity SAPI=1

Logical Link Entity SAPI=3

Logical Link Entity SAPI=5

Logical Link Entity SAPI=9

Logical Link Entity SAPI=11

Multiplex Procedure

LLC layer
GRR BSSGP

RLC/MAC layer RLC/MAC

MS

SGSN
BSSGP

BSSGP layer

Signalling Signalling and data transfer

98

LLC Basics
Operates between MS and SGSN Common signaling and data planes Provides framing for higher layer packets Addressing is provided by the lower layer RLC/MAC or BSSGP Acknowledged mode Optional Protects against LLC PDUs lost on Gb interface Protects against lost or duplicated LLC PDUs during cell change Unacknowledged mode Framing only, no reliability
99

LLC

LLC PDU
Address field SAPI 1 = GMM SAPI 2, 3, 9 and 11 = User Data SAPI 7 = SMS Control field Similar to LAPD control field SACK is bit field selective repeat acknowledgement Frame check sequence (24 bit CRC)

LLC

Address Control (SAPI)

1 octet variable (36 max)

Information Field
variable (1520 max)

FCS
3 octets

100

Subnetwork Dependent Convergence Protocol [SNDCP]

101

SNDCP - Purpose
Adapts IP or X.25 to ride on top of the GPRS air interface Multiplexing N-PDUs from one or several NSAPIs onto one LLC SAPI Compression of protocol control information and user data

SNDCP

TCP/IP header compression V.42 bis data compression

Segmentation and reassembly

102

SN - PDU

SNDCP

spare

C T M NSAPI DCOMP PCOMP Data Segment

spare

C T M NSAPI DCOMP PCOMP

N-PDU number (continued)

Segment Number N-PDU number

N-PDU number (extended)

SN-Data PDU
(acknowledged mode)

Data Segment
SN-Unitdata PDU
(unacknowledged mode)

103

SNDCP - Functionality

SNDCP

SNDC Primitive

Network Layer

SNDC Primitive

Compression SNDC Layer Segmentation

De-compression

Reassembly

LLC Primitive

LLC Layer

LLC Primitive

104

SNDCP Service Access Points

Control Entity PDP or Relay PDP or Relay

SNDCP

SNDCP users

...

15

NSAPI

SNDCP layer

SNDCP management entity

SNDCP entity

SNSM

Session Management entity

QoS 1

QoS 2

QoS 3

QoS 4

SAPI

LLC layer

105

SNDCP : XID Negotiation

Originator
SNDCP user SNDCP LLC LLC

SNDCP

Receiver
SNDCP SNDCP user

SN-XID.req LL-XID.req XID LL-XID.ind SN-XID.ind

SN-XID.res LL-XID.res XID SN-XID.cnf LL-XID.cnf

106

Acked Information Transfer

Originator
SNDCP user SNDCP LLC LLC

SNDCP

Receiver
SNDCP SNDCP user

SN-DATA.req LL-DATA.req

LL-DATA.ind SN-DATA.ind LL-DATA.res

LL-DATA.cnf

107

Unacked Information Transfer

SNDCP

Originator
SNDCP user SNDCP LLC LLC

Receiver
SNDCP SNDCP user

SN-UNITDATA.req LL-UNITDATA.req

LL-UNITDATA.ind SN-UNITDATA.ind

108

GPRS Tunneling Protocol [GTP]

109

GTP - Functionality
FTP
GTP TID 1

GTP

GTP TID 2

E-mail

GTP TID 3

Web Browsing

Protocol used to transfer information between SGSN and GGSN Creates tunnel between GPRS support nodes for user data and signaling messages Defined for inter-PLMN and intra-PLMN
110

GTP - Functionality contd

Allows multi-protocol packets to be tunneled through the GPRS backbone Tunnels are established on activation of PDP context and destroyed on deactivation of PDP context Each tunnel between two GSNs has a unique tunnel ID (TID) During handover queued packets stored in the old SGSN are tunneled to the new SGSN

GTP

111

GPRS Mobility Management [GMM]

112

GMM - Purpose
Administration of the MS in combination with Circuit Switched Services. Attach/Detach procedures Routing area updates Authentication Update HLR/VLR Paging

GMM

113

Mobility
SGSN SGSN

GMM
GGSN

BSC
LAI=3 BSC RAU-A

LAI=1

RAU-B

BSC LAI=2 114

Mobility Levels
Macro mobility

GMM

SGSN

SGSN

Micro mobility

RA

RA

RA
RA
Intra-SGSN
Inter-SGSN

Micro mobility intra-SGSN RA update no need to inform other network elements track the current RA or cell of the mobile station Macro mobility inter-SGSN RA update need to inform other network elements (e.g., GGSN, MSC/VLR, HLR) track the current SGSN of the mobile station
115

GMM State Model

IDLE IDLE

GMM

IDLE Routing Area update not required.

GPRS Attach

GPRS Detach

GPRS Attach

GPRS Detach or Cancel Location

READY
READY READY

Inform every movement to a new cell. Paging not required.

READY timer expiry or Force to STANDBY

PDU transmission

READY timer PDU expiry reception or Force to STANDBY or Abnormal RLC condition

STANDBY

STANDBY

STANDBY Inform every movement to a new RA (Routing Area). Paging required.

MM State Model of MS

MM State Model of SGSN

116

GMM States in MS
GMM-NULL GMM-ROUTINGAREA-UPDATINGINITIATED GMMDEREGISTEREDINITIATED

GMM

- enable GPRS mode

- RAU accepted - RAU failed

- DETACH accepted - Lower layer failure - disable GPRS mode - DETACH requested (not power off) - RAU requested

GMMDEREGISTERED

- RAU rejected - Network init. DETACH requested - implicit DETACH

GMMREGISTERED

- ATTACH requested

DETACH requested (power off)

- ATTACH rejected - Network init. DETACH requested - Lower layer failure - ATTACH accepted

Any state

GMMREGISTEREDINITIATED

117

GMM Procedures
GPRS Attach Detach P-TMSI Reallocation Authentication Identification Paging PDP Context Activation PDP Context Deactivation

GMM

118

GPRS Attach Procedure (normal)

MS BSS new SGSN old SGSN HLR

GMM

1. Attach Request 2. Identification Request 2. Identification Response 3. Identity Request 3. Identity Response 4. Authentication

5. Attach Accept

9. Attach Complete 10. TMSI Reallocation Complete

119

MS Initiated Detach Procedure

MS BSS SGSN GGSN MSC/VLR

GMM

1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. IMSI Detach Indication 4. GPRS Detach Indication 5. Detach Accept

120

Network Initiated Detach Procedure

GMM

MS

BSS

SGSN

GGSN

MSC/VLR

1. Detach Request 2. Delete PDP Context Request 2. Delete PDP Context Response 3. GPRS Detach Indication 4. Detach Accept

121

Routing Area Update Procedure

GMM

MS

BSS

SGSN

1. Routeing Area Update Request 2. Security Functions 3. Routeing Area Update Accept 4. Routeing Area Update Complete

122

GPRS Paging Procedure

GMM

MS

BSS

SGSN 1. PDP PDU

2. Paging Request 3. GPRS Paging Request 4. Any LLC Frame 5. Any LLC Frame

123

Session Management [SM]

124

SM - Purpose
Activate/Deactivate PDP contexts (MS and Network initiated) Assign/Negotiate QoS Create connection with GGSN

SM

125

PDP State Model

SM

INACTIVE

Activate PDP Conext

Deactivate PDP Context or MM state change to IDLE

ACTIVE

126

SM Procedures
AA PDP Context Activation AA PDP Context Deactivation Routing Area Update Combined Routing Area/Location Area Updates

SM

127

MO PDP Context Activation Procedure

SM

MS

SGSN

GGSN

1. Activate PDP Context Request 2. Security Functions 3. Create PDP Context Request 3. Create PDP Context Response 4. Activate PDP Context Accept

128

MT PDP Context Activation Procedure

MS SGSN HLR GGSN 1. PDP PDU 2. Send Routeing Info for GPRS 2. Send Routeing Info for GPRS Ack 3. PDU Notification Request 3. PDU Notification Response 4. Request PDP Context Activation 5. PDP Context Activation procedure

SM

129

PDP Context Modification Procedure

SM

MS

SGSN

GGSN

1. Update PDP Context Request 2. Update PDP Context Response 3. Modify PDP Context Request 4. Modify PDP Context Accept

130

MS Initiated PDP Context Deactivation Procedure

SM

MS

SGSN

GGSN

1. Deactivate PDP Context Request 2. Security Functions 3. Delete PDP Context Request 3. Delete PDP Context Response 4. Deactivate PDP Context Accept

131

NW Initiated PDP Context Deactivation Procedure

SM

MS

SGSN

GGSN

1. Delete PDP Context Request 1. Delete PDP Context Response 2. Deactivate PDP Context Request 2. Deactivate PDP Context Accept

132

REFERENCES

133