Gprs RPL

FUNDAMENTALS
NOKIA
GPRSRPL.PPT / 28-04-2003 / PPa
GSM Evolutionary Steps
NOKIA
GPRS versus GSM Fundamental Differences

3+1 versus 1+1 GPRS MS can use up to 3 TS in DL, in CSW this is 'not' possible Up to 9 users may share the same time slot in DL separation based on MAC header, affect to data speed GPRS do not have handovers because MS is not sending measurement reports to network GPRS 'do not' have power control because MS is not sending measurement reports to network, PC only in UL Radio resources are allocated to a user on level of 5 seconds (DL TBF) this depends heavily on applications generates massive signaling, ref. Mobility management stages
NOKIA
GPRS Network - Overview
Host 131.44.15.3
MSC
PSTN
BTS
BSC
GPRS Core GPRS Backbone IP Network
Host 155.222.33.55
SGSN
GGSN
Internet
Shared GSM and GPRS Infrastructure

4 NOKIA GPRSRPL.PPT / 28-04-2003 / PPa
GPRS Infrastructure
IP World
GPRS Entry Network and Network Elements

LIG SS7
(Legal Interception Gateway)
DNS
(Domain Name Server)
BSS
FR Network SGSN
(Serving GPRS Support Node)
LAN switch
CG
(Charging Gateway)
BG
(Border Gateway)
GGSN
(GPRS Gateway Support Node)
Firewall OMC Inter-PLMN network
Firewall Internet or Intranet
NOKIA
GPRS Interfaces
TE R MT Um BSS A MSC/VLR D HLR E C SMS-GMSC SMS-IWMSC SM-SC
Gb
Gs
Gr Gd LAN SW / IP BB Gn DNS Gn CG Gc DNS
SGSN
Gn Gp GGSN
SGSN Gf
Gn
Gn Gn
GGSN FW Gi DHCP LIG
APN
PDN
TE
EIR
Other PLMN
Signaling Interface Signaling and Data Transfer Interface

GPRS Network Elements and Primary Functions

SGSN Mobility Management MS Authentication Ciphering Interaction with VLR/HLR Charging and statistics GTP tunnelling to other GSNs Border Gateway GGSN GTP tunnelling to other GSNs Secure interfaces to external networks Charging & statistics IP address management
Charging Gateway
Domain Name Server Translates IP host names to IP addresses Makes IP network configuration easier In GPRS backbone SGSN uses DNS to get GGSN and SGSN IP addresses Two DNS servers in the backbone to provide redundancy
Legal Interception Gateway Interconnects different CDR consolidation Enables authorities to intercept GPRS operators' subscriber data and signaling Forwarding CDR information to billing Chasing criminal activity backbones center Operator personnel has very Enables GPRS limited access to LI functionality roaming LI is required when launching the Standard Nokia IP GPRS service router family
Temporary Block Flow

A Temporary Block Flow (TBF): is a one-way session for packet data transfer between MS and BSC (PCU) uses either uplink or downlink but not both (except for associated signaling) can use one or more TSLs. 2 TBF's (UL & DL) to allow bidirectional communication. Compare with circuit-switched: normally one connection uses both the uplink and the downlink timeslot(s) for traffic In two-way data transfer: uplink and downlink data are sent in separate TBFs - as below Uplink TBF (+ PACCH for downlink TBF)
Downlink TBF (+ PACCH for uplink TBF)
BSC
PACCH (Packet Associated Control Channel): Similar to GSM CSW SACCH


Uplink TBF Uplink data Signalling
Downlink TBF
Signalling Downlink data
Simultaneous Downlink TBF and Uplink TBF
Uplink data Downlink data
NOKIA
Temporary Block Flow (TBF)

Defined in GSM 04.60 as stated below:
"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. The mobile station shall assume that the TFI value is unique among concurrent TBFs in the same direction (uplink or downlink) ) on all PDCHs used for the TBF. The same TFI value may be used concurrently for TBFs on other PDCHs in the same direction and for TBFs in the opposite direction.
Identify ETSI Specification References folder ~\References\ETSI Specifications\
10
NOKIA
Temporary Block Flow (TBF)

A physical connection between MS and BSS An allocated radio resource with certain QoS parameters (e.g. radio priority, peak throughput) and transfer mode (ack/unack)
Unidirectional separate TBFs needed for uplink and downlink transfer

TBF parameters can be changed Channel coding and QoS parameters can be changed during a TBF Each TBF has a unique Temporary Flow Identifier (TFI) used to address the peer RLC entities included in all radio blocks to correctly associate them with the the mobile station
11
NOKIA
TLLI / TBF Concept

HLR
IMSI
VLR
TMSI
MS
BTS
BSS
PCU
SGSN
P-TMSI
GGSN
GPRS CORE
Internet or Intranet
TBF (TFI + TSL) TBF (RLC / MAC Flow)
TBF (LLC Flow)
TLLI (SNDCP Flow)
12
NOKIA
TBF Flow
Start of TBF Slow TBF Full Speed TBF Ending Slow down Gb SGSN (LLC) Buffer PCU (LLC -> RLC/MAC) Gb SGSN (LLC) Buffer PCU (LLC -> RLC/MAC)
Air Interface (RLC/MAC) MS Re-assembly (RLC/MAC -> LLC) Application
Air Interface (RLC/MAC) MS Re-assembly (RLC/MAC -> LLC) Application
13
NOKIA

DL TBF Network starts and releases TBFs FBI (Final Block Indicator) indicates the last block in a DL TBF
Uplink TBF Close-ended: limited number of octets Open-ended: an arbitrary number of octets MS may request either close-ended or open-ended TBF NW decides the type in PACKET UPLINK ASSIGNMENT MS can ask network to give more resources if needed
14
NOKIA
Protocols and Framestructure
15
NOKIA
GPRS System understanding: signaling multiframe structure (51 TDMA frames)

BCCH + CCCH (downlink) F S B C F S C C F S C C F S C C F S C C BCCH + CCCH (uplink) R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R 51 frames 235.38 ms 8 SDCCH/8 (downlink) D0 D0 D1 D1 D2 D2 D3 D3 D4 D4 D5 D5 D6 D6 D7 D7 A0 A4 A1 A5 A2 A6 A3 A7 - - - - -
8 SDCCH/8 (uplink)
A5 A1
A6 A2
A7 A3
- - - - -
D0 D0
D1 D1
D2 D2
D3 D3
D4 D4
D5 D5
D6 D6
D7 D7
A0 A4
BCCH + CCCH 4 SDCCH/4 (downlink)
F S F S
B B
C C
F S F S
C C
C C
F S F S
D0 D0
D1 D1
F S F S
D2 D2
D3 D3
F S F S
A0 A2
A1 A3
BCCH + CCCH 4 SDCCH/4 (uplink) F: B: D: R:

16 NOKIA
D3 D3
R R R R
A2 A0
A3 A1
R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R R
D0 D0
D1 D1
R R R R
D2 D2
TDMA frame for frequency correction burst TDMA frame for BCCH TDMA frame for SDCCH TDMA frame for RACH
S: TDMA frame for synchronization burst C: TDMA frame for CCCH A: TDMA frame for SACCH/C
Bursts on the Air Interface

RLC Blocks
RLC/MAC Blocks
1 TDMA frame = 4.615 ms = BURST PERIOD
0 70 70 70
TDMA Bursts
7
4 x TDMA Frames = 4 Bursts = 1 RLC/MAC block = 18.46 ms

0 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 4 4 5 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 P T C C H I D L E P T C C H I D L E
B0(0..3)
B1(4..7)
B2 (8..11)
B3(13..16)
B4(17..20)
B5(21..24)
B6(26..29)
B7(30..33)
B8(34..37)
B9(39..42)
B10(43..46)
B11(47..50)
52 T DMA F rames (240 ms)
12 x RLC/MAC Blocks = 1 x 52 PDCH MultiFrame = 240 ms 12 RLC/MAC Blocks / 0.240 s = 50 RLC/MAC Blocks / s
Data Block Format

AP P TC P IP
N-PDU SN-DATA PDUs LLC Frames RLC Blocks
SNDCP
LLC
RLC
MAC
RLC/MAC Blocks
TDMA Bursts
GSM RF
18
NOKIA
Data Block Format

IP
data
h h h h h h h h h h h Data + h BCS 456 bits
114 bits 114 bits 114 bits 114 bits
TC P
IP
data data *
data
*compression
SNDCP
data data h FCS Data + h BCS
LLC
RLC/MA C GSM RF convolution coding GSM RF bursts (TS)
GSM RF
19
interleaving
57 3 8.25
3
NOKIA GPRSRPL.PPT / 28-04-2003 / PPa
57
1 26 1
GSM and GPRS Multiframe

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 GSM Signalling timeslot TDMA frame TS 0 TS 1 FCCH SCH BCCH BCCH BCCH BCCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH FCCH SCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH FCCH SCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH FCCH SCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH FCCH SCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH PCH+AGCH IDLE GSM Traffic TS TS 2 TS 3 TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH SACCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH IDLE TS 4 TS 5 GPRS traffic TS TS 6 TS 7 Radio Block 0
Radio block 1
Radio Block 2 PTCCH
Radio Block 3
Radio Block 4
Radio Block 5 IDLE
Radio Block 6
Radio Block 7
Radio Block 8 PTCCH
Radio Block 9
Radio Block 10
Radio Block 11 IDLE
20
NOKIA
The Protocols
User information transfer
IP GPRS Bearer Relay IP L2 L1 GGSN
Um
APP TCP/UDP IP SNDCP LLC RLC MAC GSM RF MS
Gb
Gn
Gi
APP TCP/UDP IP L2 L1
Compression, segmentation Ciphering and reliable link RLC BSSGP MAC NW sr GSM RF L1bis BSS
Relay SNDCP GTP LLC BSSGP NW sr L1bis SGSN UDP IP L2 L1
USER PAYLOAD GTP UDP IP L2 L1 GGSN
FIXED HOST
GPRS IP Backbone
Internet
21
NOKIA
MS-SGSN Protocol layers

APP TCP/UDP
IP
SNDCP LLC SNDCP LLC RLC MAC GSM RF BSSGP NW sr L1bis BSSGP NW sr L1bis
RLC
MAC GSM RF
MS
Um
BSS
Gb
SGSN
22
NOKIA
SNDCP (Subnetwork Dependent Convergence Protocol) Layer

APP
TCP/UDP IP
Multiplexer/demultiplexer for different network layer entities onto LLC layer Compression of protocol control information (e.g. TCP/IP header) Compression of data content (if used) Segmentation/de-segmentation of data to/from LLC layer
SNDCP LLC RLC
MAC
GSM RF
23
NOKIA
Logical Link Control (LLC) Layer

Reliable logical connection between SGSN and MS
APP
Independent of underlying radio interface protocols

LLC Frame
TCP/UDP IP
SNDCP LLC RLC
Addres s
Control
Information 140-1520
FCS
1-3
3 Octets
MAC
GSM RF
24
NOKIA
Radio Link Control (RLC)/ Medium Access Control (MAC) Layers

APP
RLC Reliable transmission of data across air interface Segmentation/de-segmentation of data from/to LLC layer MAC Control of MS access to common air-interface medium Flagging of PDTCH/PACCH occupancy
TCP/UDP IP
SNDCP LLC RLC
MAC
GSM RF
25
NOKIA
GPRS Coding Schemes

Coding Scheme Nokia GPRS Release 1
CS1 CS2 CS3 CS4
Payload (bits) per RLC block

181 268 312 428
Data Rate (kbit/s)

Error Correction Data
9.05 13.4 15.6 21.4
CS1 & CS2 - Implemented in ALL Nokia BTS without HW change
More Data = Less Error Correction
26
NOKIA
Coding Schemes
CS-1
USF 3 Header & Data 181
4 tail bits +1/2 rate convolutional coding
BCS 40 224 bits
456 bits
181bits/20ms = 9.05kbit/s
USF- Uplink State Flag BCS - Block Check Sequence

Coding Schemes
CS-2
28
NOKIA
Signalling
29
NOKIA
GPRS Signaling Overview

GPRS Air Interface Logical Channels
CCCH Common Control Channels
DCH Dedicated Channels
PCH Paging CH
AGCH Access Grant CH
RACH Random Access CH
PACCH Packet Associated Control CH
PDTCH Packet Data TCH
Existing GSM Channels

(Shared with GPRS Signalling in GPRS Release 1)
NEW GPRS Channels
Signalling Load
Cell Update Paging Existing GSM Load
Routing Area Update
Random Access Access Grant Paging Channel
GPRS Attach/ Detach
PDP Content Activation
GPRS Data Transfer (Application)
31
NOKIA
Signalling Load - Data Session Load

MS BSS SGSN
CHANNEL REQUEST RACH IMMEDIATE ASSIGNMENT AGCH
PACKET RESOURCE REQUEST (OPTIONAL)
PACCH
PACKET UPLINK ASSIGNMENT (OPTIONAL)
PACCH
MS
BSS
SGSN
Packet Paging Request Packet Paging Request

CHANNEL REQUEST PCH
RACH
IMMEDIATE ASSIGNMENT
AGCH
UL/DL load ratio 0.5, E-mail and WWW data
DATA BLOCK (last) PACKET UPLINK ACK/NACK PACKET CONTROL ACK LLC PDU
PDTCH PACCH PACCH
RACH and AGCH load will be heavily dependent on the application
32
NOKIA
Session & Mobility Management Load

RACH AGCH 3 5 2 2 2 1 2 5 3 6-8 3
NW Config Data Transfer Session GPRS Events Offered Load Application
GPRS Attach (No Authenication) GPRS Attach (Athenication) GPRS Detach (MO) PDP Context Activation (MO) PAGING CELL UPDATE ROUTING AREA UPDATE
2 2 1 1 1 1 1 2 1 3-4 2
Offered Traffic (Kbps) 5 10 15 20 25 30 35
Channel Requests (/s) 1.2 1.5 1.8 2.5 3.1 4.2 4.4
Packet Assignments (/s) 1.5
SMS (MT) (WITH PAGING) SMS (MT) (WITHOT PAGING) SMS (MO) (WITH STATS REPORT)
2.1 2.8 4.2 5.6 6.1 7.8
SMS (MO) (WITHOUT STATS REPORT)
33
NOKIA
Offered Capacity v Load

Combined Configuration - UPLINK
MS BSS
7
CHANNEL REQUEST RACH
IMMEDIATE ASSIGNMENT
ts0= RACH = 27 TDMA Frames = 115 times/s
AGCH
RACH LOAD
Offered Traffic 5 Kbits 20 Kbits 35 Kbits GPRS GPRS Load 1.2 2.5 4.4 RACH Utilisation 1% 2% 4% Available for Speech 99% 98% 96%
34
NOKIA
CHANNEL CONFIGURATIONS Configuration of Signalling Channels

Combined Configuration - Downlink NumberofBlocksForAccessGrant = 1
0 7
AGCH = 1 Block/235 ms = 4.25 blocks
ts0=PCH/AGCH (3 Blocks) Separated Configuration - Downlink

0 7
4.25 Blocks * 1.8 Messages = 7.65 /s NumberofBlocksForAccessGrant = 3
AGCH = 3 Block/235 ms = 12.8 blocks/ 12.8 Blocks * 1.8 IMM ASS = 23 /s
ts0=PCH/AGCH ( 9 Blocks)
35 NOKIA
ts1=SDCCH/8
AGCH Load
MS BSS
CHANNEL REQUEST RACH
Combined AGCH
IMMEDIATE ASSIGNMENT AGCH
7.65/s
NumberofBlocksForAccessGrant
Paging Capacity
36
NOKIA
DL TBF ASSIGNMENT (GPRS,EGPRS), MS on CCCH,

MS BTS BSC SGSN MS on ready state
P-Immediate Assignment
TBF per priority 90000(S10) /c72084(S9) packet_immed_ass_msg DL TBF Establ. 72005(S9) Max sim. DL TBF .72007(S9)
Sent on the PDTCH to find out the MS Timing Advance. In Nokia implementation, always sent when DL TBF Assignment is from CCCH. Not sent when DL TBF is assigned on PACCH
If requested and available Only 1 TCH is allocated first.
EGPRS DL TBF EGPRS DL TBF UNACK 72089(S10) Possibly72091(S10) Possibly
Req 1 tsl DL 72039(S9)
Alloc 1 tsl DL 72049(S9)
Immediate Assignment (CCCH)
P-Immediate Assignment Ack Packet Polling Request
/c72085(S9) packet_immed_ass_ack_msg DL RLC MAC /c72077(S9)
Packet Polling Request (PACCH)
Alternatively, Packet Downlink Assignmnet may be sent if more timeslots are required
Packet Control Ack (PACCH) Packet Power Control/Timing Advance
Packet Control Ack Packet Power Control/Timing Advance

DL RLC MAC /c72077(S9)
37
NOKIA
UL TBF ASSIGNMENT, MS on CCCH , 1 phase access

04.08 specifies that one phase access shall be used for all signalling S10: no QoS information in 1 ph.access. Fixed priority (best effor) used.
MS
UL TBF ASSIGNMENT, MS ON CCCH. 1 phase access.
BTS
BSC
SGSN
Channel Request (RACH) Establ.cause '1-ph.access'
P-Channel Required P-Immediate Assignment Cmd (CCCH) Only 1 TCH can be allocated.
RACH p-ch.req. /c72082(S9) packet_ch_req CCCH p- imm.ass. /c72084(S9) packet_immed_ass_msg
Sent 6 TDMA frames before the Imm Ass goes to air. Includes the air-if TDMA frame number of the Imm Ass message
UL TBF Establ. 72000(S9)
Max.sim.UL TBF 72002(S9)
Req 1 tsl UL 72034(S9)
Alloc 1 tsl UL 72044(S9)
Immediate Assignment (CCCH)
P-Immediate Assignment Ack

CCCH p- imm.ass. ack /c72085(S9) packet_immed_ass_ack_msg
UL TBF IS PROPERLY ESTABLISHED ONLY AFTER CONTENTION RESOLUTION, I.e. the MS sends the first data blocks with TLLI included in the RLC headers, and the Network (PCU) returns the same TLLI in the Packet UL Ack/Nack
38
NOKIA
MS
UL TBF ASSIGNMENT, MS on CCCH. 2 phase access.

BTS BSC SGSN UL TBF ASSIGNMENT, MS ON CCCH. 2 phase access.
Channel Request (RACH) Establ.cause '2-ph.access' P_Channel Required
/c72082(S9) packet_ch_req /c72084(S9) packet_immed_ass_msg
P-Immediate Assignment Cmd

NOTE: BTS does not send Imm Ass Ack for Single block Immediate Assignment Packet Resource Request
Single block
Immediate Assignment (CCCH) Packet Resource Request (PACCH)

Including TLLI for contention resolution
UL RLC MAC /c72076(S9) DL RLC MAC /c72077(S9) UL TBF Establ. 72000(S9) Max.sim.UL TBF 72002(S9)
Packet Uplink Assignment (PACCH)

Packet Uplink Assignment

TBF per priority 90000(S10)
UL TBF UNACK Max.sim.UL TBF UNACK 72010(S9)Possibly 72012(S9) Possibly
More than 1 TCH Req X tsl UL can be allocated. 72034(S9) RLC Data block RLC Data Block Packet Uplink Ack/Nack Packet Uplink Ack/Nack (specs)
UL RLC CS1 /c72062(S9)
Alloc X tsl UL 72044(S9) The Contention resolution was already done above. The PCU does not immediately send Packet Uplink Ack/Nack (as it does in one phase access for contention resolution) but only after a certain amount of blocks or after Final UL Data Block.
or /c72064(S9)
UL RLC CS2
39
NOKIA
Establishment of UL TBF when DL TBF is ongoing

MS BTS BSC SGSN
The MS may request UL TBF by including a Channel Request Description IE in a Packet Downlink Ack/Nack message
New TBF is established in the same mode (GPRS, EGPRS) than the ongoing TBF.
Packet_DL_Ack/Nack (Channel Request Description)
UL RLC MAC /c72076(S9) UL TBF DUR. DL /c72074(S9)
UL TBF Establ. 72000(S9)
Max.sim.UL TBF 72002(S9)
UL TBF UNACK Max.sim.UL TBF UNACK 72010(S9)Possibly 72012(S9) Possibly Req X tsl UL 72034(S9) Alloc X tsl UL 72044(S9)
Packet Uplink Assignment (PACCH)
UL RLC Data Block
UL RLC CS1 /c72062(S9)
or /c72064(S9)
UL RLC CS2
40
NOKIA
Establishment of (GPRS,EGPRS) DL TBF when UL TBF is ongoing

MS BTS BSC
LLC PDU DL TBF DUR. UL /c72075(S9)
SGSN
New TBF is established in the same mode (GPRS, EGPRS) than the ongoing TBF.
DL TBF Establ. 72005(S9)
Max sim. DL TBF .72007(S9)
If UL TBF is EGPRS
EGPRS DL TBF 72089(S10)
EGPRS DL TBF UNACK 72091(S10)
Req x tsl DL 72039(S9)
Alloc x tsl DL 72049(S9)
Packet Downlink Assignment (PACCH)
DL RLC Data Block
DL RLC ACK MSC19 /c79000(S10)
or
DL RLC UNACK MSC19 /c79001(S10)
41
NOKIA
DYNAMIC ALLOCATION and ONE PHASE ACCESS USED. 04.08 specifies that one phase access shall be used for all signalling, I.e. if the access is for Layer 3 signalling only, and not for a Layer 3 data transfer. OPEN ENDED TBF only in Release 1. NOTE: Despite of the case presented below in GMM signalling most of the TBF establishments can be done on PACCH.
GPRS/IMSI ATTACH. BSS DETAIL 1/5

MS BTS
UL TBF ASSIGNMENT 1-ph.access
BSC
All GMM signalling is RLC data blocks between MS and BSC and UL/DL_unitdata between BSC and SGSN:
SGSN
Sending of the Attach Request takes 2 radio if blocks (2*4 TDMA frames) = appr 40 ms. If UL TBF is longer than 1 block and 1-phase acces is in question then PCU has to send Packet Uplink Ack/Nack after the first block Start T3310 Start T3166 and counter N3104 Attach Request (PDTCH)
Including TLLI for contention resolution Including TLLI for contention resolution
Attach Request/Accept/Complete, Identity Request/Response, Authentication, Authentication Response, Detach Request, RAU Request/Accept/Complete, Activate/Deactivate PDP context Request/Accept
Attach Request (in data blocks)
UL RLC block counter

Attach Request
Packet Uplink Ack/Nack (PACCH)

Packet Uplink Ack/Nack

Including TLLI for contention resolution DL RLC MAC /c72077(S9)
Stop T3166 and Counter N3104
Packet Uplink Ack/Nack, Final Packet control ack (PACCH)
Packet Uplink Ack/Nack, Final Packet control ack
Identity Request (IMSI)
UL TBF release counter group

PCU waits for Packet Control Ack before it starts DL TBF establishment

MS BTS BSC SGSN
DL TBF ASSIGNMENT
SECURITY FUNCTIONS Identity Request (IMSI) (in data blocks) Identity Request (IMSI) (PDTCH) Packet Downlink Ack/Nack (PACCH) Packet Downlink Ack/Nack T3192 on, MS monitors DL channel T3192 default 500ms
UL RLC MAC /c72076(S9)
DL RLC block counter
Final block
DL TBF release counter group

UL TBF ASSIGNMENT
Identity Response (IMSI) (PDTCH) Identity Response (IMSI)

Including TLLI for contention resolution Including TLLI for contention resolution

Identity Response (IMSI)

DL RLC MAC /c72077(S9) Including TLLI for contention resolution
Authentication Packet control ack

Packet control ack (PACCH)
43
NOKIA

MS
SECURITY FUNCTIONS
BTS
BSC
SGSN
DL TBF ASSIGNMENT
Authentication (PDTCH) Packet Downlink Ack/Nack (PACCH)
Authentication
Packet Downlink Ack/Nack


UL TBF ASSIGNMENT
Authentication Response (PDTCH)

Authentication Response

Authentication Response


Identity Request (IMEI) Packet control ack (PACCH) Packet control ack
44
NOKIA

MS
SECURITY FUNCTIONS
BTS
BSC
SGSN
DL TBF ASSIGNMENT
Identity Request (IMEI)
Identity Request (IMEI)(PDTCH)
Packet Downlink Ack/Nack (PACCH) Packet Downlink Ack/Nack


UL TBF ASSIGNMENT
Identity Response (IMEI) (PDTCH)

Identity Response (IMEI)

Identity Response (IMEI) Packet Uplink Ack/Nack (PACCH)


Packet Uplink Ack/Nack (PACCH) Packet control ack (PACCH)
Packet Uplink Ack/Nack, Final Packet control ack
Attach Accept
45
NOKIA

MS BTS BSC SGSN
DL TBF ASSIGNMENT
Attach Accept
Stop T3310, when was this?
Attach Accept (PDTCH)


UL TBF ASSIGNMENT,
Attach Complete (PDTCH)

Attach Complete
Attach Complete is sent only in case P-TMSI was allocated in Attach Accept Packet Uplink Ack/Nack (PACCH)

Including TLLI for contention resolution DL RLC MAC /c72077(S9)
Attach Complete
Succ_combined_attach /c1002
Packet control ack
46
NOKIA
MS-Initiated Combined GPRS/IMSI Detach.

DYNAMIC ALLOCATION and ONE PHASE ACCESS USED. 04.08 specifies that one phase access shall be used for all signalling, I.e. if the access is for Layer 3 signalling only, and not for a Layer 3 data transfer. OPEN ENDED TBF only in Release 1. NOTE: In GMM signalling most of the TBF establishments can be done on PACCH.
MS
BTS
UL TBF ASSIGNMENT
BSC
SGSN
Detach Request (PDTCH)

Detach Request

Detach Request


Packet control ack
Detach Accept
UL RLC MAC /c72076(S9) Succ_mo_combined_ detach /c1036
If Detach is because of MS Switched off, the network does not send Detach Accept. If Det is because of any other reason, network send Detach Accept
DL TBF ASSIGNMENT
Detach Accept Detach Accept (PDTCH) Packet Downlink Ack/Nack (PACCH) Packet Downlink Ack/Nack

PDP CONTEXT ACTIVATION.

DYNAMIC ALLOCATION and ONE PHASE ACCESS USED. 04.08 specifies that one phase access shall be used for all signalling, I.e. if the access is for Layer 3 signalling only, and not for a Layer 3 data transfer. OPEN ENDED TBF only in Release 1. NOTE: In GMM signalling most of the TBF establishments can be done on PACCH. Start from MS Packet Idle Mode
MS
BTS
UL TBF ASSIGNMENT, MS ON CCCH 1-ph.access
BSC
SGSN
Activate PDP context Request (PDTCH)

Activate PDP context Request


Activate PDP Context Request


Packet control ack
SECURITY FUNCTIONS AS SET BY THE OPERATOR
Activate PDP Context Accept

DL TBF ASSIGNMENT, MS ON CCCH
Succ_mo_pdp_context_act /c2000


PDP CONTEXT DEACTIVATION.

DYNAMIC ALLOCATION and ONE PHASE ACCESS USED. OPEN ENDED TBF only in Release 1. NOTE: In GMM signalling most of the TBF establishments can be done on PACCH.
MS
BTS
UL TBF ASSIGNMENT, MS ON CCCH, 1-ph.access
BSC
SGSN
Deactivate PDP context Request (PDTCH) Deactivate PDP context Request

Deactivate PDP Context Request Packet Uplink Ack/Nack (PACCH)


Packet control ack
SECURITY FUNCTIONS AS SET BY THE OPERATOR
Deactivate PDP Context Accept

DL TBF ASSIGNMENT, MS ON CCCH, 1-ph.access
Succ_mo_pdp_context_deact /c2004
Deactivate PDP Context Accept

Deactivate PDP Context Accept Packet Downlink Ack/Nack (PACCH) Packet Downlink Ack/Nack

GPRS PAGING & DL DATA TRANSFER.

DYNAMIC ALLOCATION USED. 04.08 specifies that one phase access shall be used for all signalling, I.e. if the access is for Layer 3 signalling only, and not for a Layer 3 data transfer. DOWNLINK ASSIGNMENT is sent when downlink data transfer starts. OPEN ENDED TBF only in Release 1. NOTE: In GMM signalling most of the TBF establishmentsIfcan done on (timer PACCH. MSbe in standby def.44sec after TBF release) location not known exactly Pagings come from => paging needed for first GSSGP DL packet (about 1.5k) GIP or GMG
MS
P-TMSI used in paging.
BTS
BSC
Paging Request (P-TMSI)
PS pages on PPCH /c91019 (S10)
SGSN
Paging Request (CCCH PCH) Packet Paging Request (PCCCH PPCH)
Paging Request (CCCH PCH) Packet Paging Request (PCCCH PPCH)

To all MS in SEG
To all SEG in paging area

Packet paging req msgs /c91020 (S10)
PS pages on PCH /c3057 (S9)
Ra_level_pagings /c5000
or
UL TBF ASSIGNMENT, MS ON CCCH
Any LLC frame (PDTCH)

Any LLC frame

GPRS in BSC (DN99565086) says: The MS's paging response to the SGSN is handled in the PCU as any other uplink TBF.

Any LLC frame
Empty LLC frame


Downlink Data Packets

Gtp_packets_sent_in_dl /c3001 Gtp_data_in_bytes_sent_in_dl /c3003 NSCV_passed_data_in_bytes /c3017
Packet control ack


The data sent by SGSN can not be sent further until the DL TBF is established.
DL DATA TRANSFER (see chart later)
The LLC frame is already ciphered The SGSN encrypts each DL packet according to parameters negotiated in PDP context activation
Header compr. Data compr.
bytes_in_of_vjhc_in_sndcp /c3008 bytes_out_of_vjhc_in_sndcp /c3009 bytes_in_of_v42bis_in_sndcp /c3010 bytes_out_of_v42bis_in_sndcp /c3011
50
NOKIA
DATA TRANSFER DL with Intra-PCU Cell Change.

MS BTS1 BTS2 BSC SGSN
DL TBF ASSIGNMENT, MS ON CCCH, via BTS 1
DL Data Packets DL Data Packets DL Data Packets (PDTCH)

PCU buffers LLC pdu's in RLC ACK-moode until all RLC blocks of the LLC pdu are acknowledged. In RLC UNACK-mode PCU buffers until all RLC blcks of LLC pdu are sent.
The MS notices a need for a cell change (measurement strategy in 05.08). The MS stops receiving the DL Data Packets and tunes to the new frequency. While doing the neighboring measurement, the MS also checks for a possible RA change; if the cell change results in RA change, a RA update is performed instead of a cell update.
The SGSN encrypts each DL packet according to paramete rs negortiate d in PDP context activation
UL TBF ASSIGNMENT, MS ON CCCH, via BTS 2
03.60:: "LLC frame of any type, including MS identity"

03.60:: "LLC frame of any type", BSS adds CGI 08.18:
If MS is in UL data transfer it starts UL TBF in the new cell to transfer data. Cell Update is performed, too.
Queued BSSGP signalling, e.g. pages, shall not be affected by Flush. These will thus go wasted if Cell Change happens. DL TBF ASSIGNMENT, MS ON CCCH, via BTS 2
DL Data Packets (PDTCH)
Flush-LL PDU( Old BVCI+MS TLLI) The SGSN DL Data Packets does not wait for Flush-LL Ack Flush-LL ack before it forwards new DL Data DL Data Packets Packets towards If new BVCI is given in Flush-LL, and the new new BVCI is served by the same NSE, In Flush-LL Ack the PCU tells BVCI the queued data packets are forwarded to whether the queued data packets the new BVCI. In the Intra-PCU case the were deleted or forwarded to NSE is the same, since In the Nokia new BVCI implementation each PCU represents one and only one Network Service Entity (NSE).
DL flush /c72059 (S9) UL flush /c72058 (S9)
51
NOKIA
DATA TRANSFER DL with Inter-PCU/Intra BSC Cell Change

MS BTS1 BTS2 BSC SGSN
DL Data Packets DL Data Packets DL Data Packets (PDTCH)
The SGSN encrypts each DL packet according to parameters negortiated in PDP context activation
The MS notices a need for a cell change (measurement strategy in 05.08). The MS stops receiving the DL Data Packets and tunes to the new frequency. While doing the neighboring measurement, the MS also checks for a possible RA change; if the cell change results in RA change, a RA update is performed instead of a cell update.
PCU buffers until RLC/MAC ack?? SGSN buffers until LLC ack???
UL TBF ASSIGNMENT, MS ON CCCH, via BTS 2
03.60:: "LLC frame of any type, including MS identity"

03.60:: "LLC frame of any type", BSS adds CGI
DL flush /c72059(S9) UL flush /c72058(S9)
Flush-LL PDU( Old BVCI+MS TLLI) DL Data Packets Flush-LL Ack
DL Data Packets DL Data Packets (PDTCH) In Flush-LL Ack the PCU tells whether the queued data packets were deleted or forwarded to new BVCI
In Nokia implementation, the inter-PCU cell change is also a inter-NSE cell change, thus the PCU destroys queued data packets after a Flush that follow s inter-PCU cell change.
Thus if PCU is sending DL data when MS makes an inter PCU cell change, data is probably lost and retransmissions rely on the LLC layer acknowlegements
52
NOKIA
INTER SGSN ROUTING AREA UPDATE 1/2.

MS
BTS
UL TBF ASSIGNMENT
BSC
Routeing Area Update Request
New SGSN
Routeing Area Update Request (PDTCH)


Routeing Area Update Request


Packet control ack

SECURITY FUNCTIONS AS SET BY THE OPERATOR DL TBF ASSIGNMENT
Routeing Area Update Accept

53
NOKIA
INTER SGSN ROUTING AREA UPDATE 2/2.

MS
BTS
BSC
New SGSN
UL TBF ASSIGNMENT
Routeing Area Update Complete (PDTCH)

Routeing Area Update Complete

Routeing Area Update Complete Packet Uplink Ack/Nack

Including TLLI for contention resolution Succ_inter_sgsn_ra_updat /c1019

54
NOKIA
Functionality issues
55
NOKIA
Connecting to the GPRS Network

GPRS Attach
Attach Request Attach Accepted
Connects to the GSM network checking authentication and updating mobile location. Subscriber Information is downloaded from the HLR to the SGSN
Normal Attach, Detach procedures should occur within 5 seconds each.

Establishing a PDP Context

PDP (Packet Data Protocol) Context Activation
PDP Context Request 155.131.33.55
Gets an IP address from the network

Initiated by the MS Contains QoS and routing information enabling data transfer between MS and GGSN
PDP Context Activation and Deactivation should occur within 2 seconds.
PDP Context Activation - 1

(1) MS sends "Activate PDP Context Request" to SGSN (2) SGSN checks against HLR
HLR BTS BSC
2.
SS7
1.
APN= "Intranet.Ltd.com"
SGSN
DNS GPRS Backbone IP Network
Access Point
Intranet GGSN Internet
Access Point Name = Reference to an external packet data network the user wants to connect to
58
NOKIA

Finding the GGSN
(1) SGSN gets the GGSN IP address from DNS (2) SGSN sends "Create PDP Context Request" to GGSN
BTS
BSC
SGSN
1.
GPRS Backbone IP Network
DNS
2.
Access Point
Intranet GGSN Internet
DNS = Domain Name System = mechanism to map logical names to IP addresses
59
NOKIA

Access Point Selection
Access Point Name refers to the external network the subscriber wants to use
BTS
BSC
SGSN
DNS GPRS Backbone IP Network GGSN Internet APN= "Intranet.Ltd.com"
Intranet
60
NOKIA

Context Activated
User (dynamic) IP address allocated (1) GGSN sends "Create PDP Context Response" back to SGSN (2) SGSN sends "Activate PDP Context Accept" to the MS
BTS
BSC
2.
SGSN
GPRS Backbone IP Network GGSN Intranet
1.
Internet
61
NOKIA
GPRS Mobile States

GPRS Attach/ Detach
Idle
READY Timer Expiry
Ready
STANDBY Timer Expiry
Standby
Packet TX/RX
MS location not known. Subscriber is not reachable by the GPRS NW.
MS location known to SGSN level. MS is capable of recieving Point-to-Multipoint data and being paged for Point-to-Point data
MS location known to cell level. MS is transmitting or has just been transmitting. MS is capable of receiving Point-to-Point data and Point-to-Multipoint data.
62
NOKIA
GPRS Mobility Management Mobile States

GPRS Attach/ Detach
Idle
"Off"
READY Timer Expiry STANDBY Timer Expiry
Ready
"Active"
Standby
"Idle"
Packet TX/RX MS location known to Cell Level. MS is transmitting or has just been transmitting. MS is capable of receiving Point-to-Point data and Point-to-Multipoint data.
MS location known to RA Level. MS is capable of receiving Point-to-Multipoint data and being paged for Point-to-Point data
63
NOKIA
GPRS System understanding: Mobility Management

GPRS Attach / Detach
GPRS MM is based on States State Transition occurs when a pre-defined transaction takes place For example, via GPRS Attach the MS makes itself known to the network: State transition Idle to Ready Mobility Management before Session Management: GPRS attach needs to happen before PDP context activation READY Timer default value: 44 s MOBILE REACHABLE Timer default value: 60 min Timer values are configurable with SGSN Parameter Handling
Idle
READY Timer Expiry
Ready
MOBILE REACHABLE Timer Expiry
Standby
Packet TX/RX
MS location known to Routing Area level. MS is capable of recieving Point-to- Multipoint data and being paged for Point-to-Point data
MS location known to cell level. MS is transmitting or has just been transmitting. MS is capable of receiving Point-to-Point data and Point-to- Multipoint data.
64
NOKIA
Session Management GTP Tunnel and PDP Context

GTP - GPRS Tunneling Protocol PDP - Packet Data Protocol MS BSS SGSN
GPRS CORE
GGSN
Internet or Intranet
GTP Tunnel
PDP Context Data transfer and PDP Context Activation is always via the GGSN. GPRS R1, R1.5, and R2 support MS initiated PDP contexts (NW initiated PDP contexts may be supported in GPRS R3).
GPRS Mobile Terminal Classes

Class C Class B Class A
GPRS only
(or manually switched between GPRS and speech modes)
GPRS and Speech (not at same time)

(Automatically switches between GPRS and speech modes)
BSC
GPRS and Speech at the same time
BTS
66
NOKIA
GPRS Multislot Classes

Type 1
Multislot Classes 1-12 - Max 4 DL or 4 UL TSL (not at same time) DL - Up to 5 TSL shared between UL and DL UL - Minimum 1 TSL for F Change - 2-4 TSL F Change used when idle measurements required Multislot Classes 19-29 - Max 8 downlink or 8 uplink (not required at same time) - 0-3 TSL F Change 1 TSL for Measurement
1 TSL for F Change
DL UL
Type 2
Multislot Classes 13-18 - simultaneous receive & transmit - max 8 downlink and 8 uplink (Not available yet, difficult RF design) DL
UL
67
NOKIA
MS multislot example
Multislot class 5 MS in circuit switched configuration Five basic configurations of channels are possible
Tt = Rx=2 1 Tx=2 Rx Tx Tra=3 Rx Tx Tt Tx = < Rx=2 1 2 Tra>3
All possible timeslots used
Downlink biased assymetry
Tx < Rx=2 Tt>1 2 Tra=3 Rx Tx Alternative downlink biased assymetry Rx
Rx < 2 Tt>1 Tx=2 Tra=3
Tx
Uplink biased assymetry (not prohibited by multislot class)
Rx Tt < = 2 1 Tx=2 Tra>3 Rx Tx These five combinations can be repeated at the six other positions that can be fitted within the same TDMA frame
Ref: TS 05.02
68 NOKIA
Alternative uplink biased assymetry (not prohibited by multislot class)
GPRS Cell Selection and Reselection

GPRS mobile cell selection / reselection the same as the Circuit Switched idle mode cell selection
Cell is selected autonomously by the mobile

MS uses C1 and C2 parameters for cell selection/reselection Cell reselection can be done during the data connection
C1 C2
69
NOKIA
Cell Selection with C1 Radio Criteria

C1 = (A - Max(B,0))
A
= Average Received Level - p1 system
p1 = rxLevelAccessMin - Min. received level at the MS required for access to the B

= p2 - Maximum RF Output Power of the Mobile Station the system
p2 = msTxPowerMaxCCH - Max. Tx power level an MS may use when accessing
70
NOKIA
Cell Re-selection with C1

cellReselectHysteresis (0 14 dB)
(mentioned in RR Management in IDLE mode Control)
CELL 1 in LA1/RA1
CELL 2 in LA2/RA2
CELL 1
B C
CELL 2
A = 4 dB B = 6 dB C = 8 dB
Signa l Level
RX Lev from CELL 2
RX Lev from CELL 1

MS Moving
Cell Reselection with C2

Cell Attractiveness
Microcell
Macrocell
Time
BCCH
BCCH
Fast Moving Mobile
Slow Moving Mobile
72
NOKIA
Cell Reselection with C2, continues

Parameter cellReselectParamInd Value Y N C2 reselection parameters are broadcast C2 reselection parameters are not broadcast
if penaltyTime <
C1 + cellReselectOffset - temporaryOffset*H(penaltyTime-T)
640
C2 = C1 - cellReselectOffset 1 H(x) = 0 0 cellReselectOffset temporaryOffset penaltyTime

for T < = penaltyTime for T > penaltyTime for all T on Serving Cell if penaltyTime = 640
0 ... 126 (dB) 2 dB step 0 ... 70 (dB) 10 dB step (this value is negative) 20 ... 640 (s) 20 s step
73
NOKIA

Macro 900 "C"
Road =30 Cell "A" (Serving Cell) Cell "B"
C1
Macro 1800 "B" Micro 900 "D"
=25
=5
=50
Cell "C"
Cell "D"
C2 = C1 + cellReselectOffset temporaryOffset*H(penaltyTimeT) =30 + 0 (H(x)=0, serving cell) Cell "A"
Mobile Location Macro 900 "A" Cell "A" cellReselectOffset 0 dB 0 dB 20 s
C2
=25 + 20 - 30*H(20 - T)
=5 + 0 - 0*H(20 - T) Cell "C"
Cell "B"
Cell "B" 20 dB 30 dB 20 s
=50 + 0 - 30*H(40 - T) Cell "C" Cell "D" 0 dB 0 dB 20 s 0 dB 30 dB 40 s
Cell "D"
Parameters
temporaryOffset penaltyTime
74
NOKIA

Macro 900 "C"
Road =30 Cell "A" (Serving Cell) Cell "B" =25
C1
Macro 1800 "B" Micro 900 "D"
=5
=50
Cell "C"
Cell "D"
C2 = C1 + cellReselectOffset temporaryOffset*H(penaltyTimeT) =30 + 0 (H(x)=0, serving cell) Cell "A"
Mobile Location Macro 900 "A"
C2
=25 + 20 - 30*H(20 - T)
=5 + 0 - 0*H(20 - T) Cell "C" =50 + 0 - 30*H(40 - T)
Cell "B"
Cell "D"
Time T: (0 - 19 s)
C2 =30
C2 =15 C2 =5 C2 =20
75 NOKIA
Time T: (20 - 39 s)
C2 =30
C2 =45 C2 =5 C2 =20
Time T: (> 40 s)
C2 =30
C2 =45 C2 =5 C2 =50
Cell "A"
Cell "B" Cell "C" Cell "D"
Cell "A"
Cell "A"
GPRS Territory
76
NOKIA
GPRS and GSM Resource Sharing

TRX 1 TRX 2
CCCH TS TS TS TS TS TS TS
Circuit Switched Territory Packet Switched Territory
TS
TS
TS
TS
TS
TS
TS
TS
Additional GPRS Capacity
Dedicated GPRS Capacity Default GPRS Capacity
Recommended to use Only for Congested Cells
Territory border moves Dynamically based on both Circuit and Packet Switched traffic load
Intra-cell HO used to keep Default GPRS Territory Free
Circuit Switched traffic has priority Packet Switched territories are defined for each cell GPRS territories consist of consecutive timeslots
GPRS and GSM Resource Sharing

Parameters
Parameters for Territory management: An example GPRSenabled (BTS-level)= Y GPRSenabledTRX (TRX-level)=Y ( on BCCH TRX) DedicatedGPRScapacity (BTS-level, %)= 1 TSL DefaultGPRScapacity (BTS-level, %)= 3TSL PreferBCCHfreqGPRS (BTS-level)=Y TerritoryUpdateGuardTimeGPRS (BSC-level)=5 sec MaxGPRScapacity(BTS-level,%)=100 freeTSLsforCSUpgrade(BSC-level,sec=4 freeTSLsforCSDowngrade(BSC-level,%)=95%
Circuit Switched traffic has priority outside dedicated territory GPRS dedicated time slots (% of total cell capacity) can be defined.
can use, no CSW
GPRS Territory Parameters
effect of introducing GPRS on NW Quality & Capacity

Only GPRS
Dedicated TSL is subset of Default TSL Territories consists of consecutive timeslots GPRS can be set to favour the BCCH Transceiver -> minimum interference
Extra GPRS capacity TRX 1 TRX 2 Free time slots in Circuit Switched territory Territory upgrade in interval of Territory Upgrade Guard Time
Default GPRS capacity threshold

TS TS TS TS TS TS TS
BCCH
Circuit Switched Territory Circuit / Packet Switched Territory
TS
TS
TS
TS
TS
TS
TS
TS
Default GPRS Capacity (%)
Territory downgrade forced by the Circuit Switched traffic
Dedicated GPRS Capacity (%)
Territory Considerations
Dedicated GPRS capacity
TSLs reserved exclusively for GPRS use
Default GPRS capacity

TSLs always allocated to GPRS when circuit-switched load permits. Keeps GPRS timeslots consecutive (important for multislot operation) Upgrade/downgrade controlled by CSW RRM
80
NOKIA
Territory Considerations
Additional GPRS capacity
When default GPRS capacity is allocated to GPRS, and the GPRS load is increasing, the PS RRM can request additional TCHs. CSW RRM controls allocation of additional TCHs based on the circuitswitched load. Downgrade of additional GPRS capacity can be initiated by CSW or PS RRM.
effect of introducing GPRS on NW Quality & Capacity
81
NOKIA
Dedicating GPRS Timeslots

Circuit blocking probability vs no. of dedicated GPRS TCHs per TRX 0.2 0.18
Blocking probability
0.16 0.14 0.12 0.1 0.08 0.06 0.04 0.02 0 1 2 3 4 5 6 7 8 No. TRXs 1 TCH 2 TCH 3 TCH
Dedicating TSLs to GPRS increases CSW blocking
82
NOKIA
Free Timeslots
Where possible, free timeslots should be present between GPRS and CSW territory (also known as GPRS Territory Margin):

Allows fast TCH allocation to incoming CS call Free timeslots are hard coded in BTS
Number of free timeslots has been calculated based on:

Expected upgrade/downgrade rate Number of TRXs per cell
Impact:
Reduced overall PDTCH availability per carrier
83
NOKIA
Free Timeslots in CSW Territory

How many free timeslots are defined for different BTS configurations?
No. of T RXs / BT S 1 2 3 4 5 6 7 8 9 10 11 12 Free T SLs (after Free T SLs (after GPRS downgrade) GPRS upgrade) 1 1 1 2 1 2 2 3 2 4 2 4 2 4 3 5 3 5 3 6 3 6 3 6 Mean free T SL in CSW 1 1.5 1.5 2.5 3 3 3 4 4 4.5 4.5 4.5
CSW "Push"
Free TSL "Pull" - TSL must be free after GPRS upgrade - Will upgrade after "Upgrade Guard Time"
84
NOKIA
GPRS Territory Upgrade

The Territory Upgrade/Downgrade procedure uses the following three parameters to help redistribute TBFs across available TSLs:
X1: 1.5
X2: 1
X3: 0.5
The PS RRM request an upgrade when the average number of TBF's per TSL in the GPRS territory is greater than X1 (and Default territory is already allocated)
The target average number of TBFs in the GPRS territory is defined by X2

When the average number of TBF per TSL in the GPRS territory is less than X3, the PS RRM will request a GPRS downgrade. (but only as far as the default boundary)
85
NOKIA
TBF Allocation Improvement (CD 2.4 FEA)

Why these changes?
A territory upgrade was requested only if:

more than 1.5 TBF/TSL (X1) no upgrade was requested for a single MS (1TBF/TSL) even if its full multislot capability was not utilised the Default GPRS Territory setting needed to be at least 2-3 TSLs depending on the MS this was a problem for small configurations (intra-cell HOs)
No reallocations of existing TBFs:
in an upgrade, new capacity is waiting for new TBFs when TBFs finish, TSLs can be shared very unevenly
86
NOKIA
Improvements in Requesting Additional Channels

When allocating TSLs to a TBF: Upgrade requested even for 1 TBF/TSL
advantage for small configurations where 1 default channel is optimal

full capacity is allocated whenever possible
Multislot class of MS taken into account
Target is always 1 TBF/TSL
87
NOKIA

If TSL7 = Default Territory + 3 TSL capable MS:
GPRS Territory Boundary
Configuration
T S L0
T S L1
T S L2
T S L3
T S L4
T S L5
T S L6
T S L7
T BF 1 T S L7
Mobile allocted 1 TS
TBF reallocted to 3 TS
T S L0
T S L1
T S L2
T S L3
T S L4
T S L5
T S L6
T S L0
T S L1
T S L2
T S L3
T S L4
T BF 1 T S L5
T BF 1 T S L6
T BF 1 T S L7
Default GPRS Territory
88
NOKIA

When PCU gets more TSLs: Multislot capability of MS is checked Reallocation of existing "long" TBFs (>100 datablocks sent) Threshold = average number of TBFs / TSL If number of TBFs in a TSL is larger than threshold
load will be distributed more evenly with reallocations
89
NOKIA
Channel Allocation Improvements - Example

Configuration 2* 2+1 Mobile allocted GPRS Territory reduced to 1 TS due to CSW CSW traffic reduced & default territory back
T S L0 T S L1 T S L2 T S L3 T S L4 T BF2 T S L0 T S L1 T S L2 T S L3 T S L4 T S L5 T BF2 T S L5 T S L6 T BF1 T S L6 T S L7 T BF1 T S L7
T BF2 T BF1 T S L0 T S L1 T S L2 T S L3 T S L4 T S L5 T S L6 T S L7
T BF2 T BF1 T S L0 T S L1 T S L2 T S L3 T S L4 T S L5 T S L6 T S L7
Reallocation of TBF's
T BF2 T S L0 T S L1 T S L2 T S L3 T S L4
T BF2 T S L5
T BF1 T S L6
T BF1 T S L7


(Release of a simultaneous UL & DL TBF)
1 Multislot Class 6 Mobile

(Max 3 DL / 2 UL TSL, Total 4 TSL)
Uplink

T S L4 T S L5 T S L6 T S L7
Configuration
Downlink
T S L0
T S L1
T S L2
T S L3
T S L0
T S L1
T S L2
T S L3
T S L4
T S L5
T S L6
T S L7
Both UL & DL TBFs established 2TSL allocated (Total 4) UL TBF finished DL TBF reallocated to 3 TSL (if DL TBF is "long")
Uplink
T S L0 T S L1 T S L2 T S L3 T S L4 T S L5
T BF2 T S L6
T BF2 T S L7
Downlink
T S L0 T S L1 T S L2 T S L3 T S L4 T S L5
T BF1 T S L6
T BF1 T S L7
Uplink
T S L0 T S L1 T S L2 T S L3 T S L4 T S L5 T S L6 T S L7
Downlink
T S L0 T S L1 T S L2 T S L3 T S L4
T BF1 T S L5
T BF1 T S L6
T BF1 T S L7

PCU gets TSL2
Threshold Calculated = (0+1+1+1+3+2)/6 = 8/6 TBF/TSL

For TSL6 number of TBFs is 3 > 8/6 (round up to 2)
Reallocation attempted for one of the TBFs in TSL6 as the above calculations indicate that load is not evenly spread
TBF 4 Gets Re-allocated to TSLs 2 and 3
TBF4 TBF3 TBF1 TSL2 TSL3 TBF1 TSL4 TBF3 TSL5 TBF2 TSL6 TBF4 TBF2 TSL7
92
NOKIA
Channel Allocation Improvements

(Release of a simultaneous UL & DL TBF)
If MS has UL and DL TBFs simultaneously When one of them is released
PCU checks if the remaining one is "long"
Re-allocation will be attempted for the "long" TBF if:

multislot class capability not fully utilised or the TSL (of the remaining TBFs) has 2 TBFs more than another TSL
Re-allocation is attempted only for the MS that had simultaneous TBFs
93
NOKIA
Upgrade and downgrade

Upgrade is requested in two cases:
1. Upgrade request back to the Default territory (c1180) 2. Upgrade request beyond Default territory for additional resources, which can be rejected because of (c1174): 1. PCU capacity limitation( 256 GPRS TSL per PCU) 2. High CSW load 3. No GPRS capable resorce left ( No GPRS enable TRX)
Downgrade is requested in two cases: 1. 2. Downgrade request back to the Default territory when there is no need for additional channels anymore(c1181) Downgrade request below Default territory because of rising CSW (c1179)
Default territory
2 1174 1181
4 1179
1180
94
NOKIA
Upgrade and downgrade Counters
Update timer TerritoryUpdateGuardTimeGPRS supervises:

Any upgrade request Downgrade request back to Default territory by PCU
Update timer TerritoryUpdateGuardTimeGPRS does not affect Downgrade request below Default territory because of rising CSW traffic
95
NOKIA
Determination of CDEF
Too high value leads to frequent territory downgrades triggered by CSW load, and subsequently to territory upgrades and GPRS triggered handovers. Too low value leads to frequent territory upgrades triggered by GPRS load, and thus GPRS triggered handovers. Also, delay in allocating full resources to the MS. Normal rule: CDEF = max(MS capability, GPRS traffic in cell)
96
NOKIA
Link Adaptation
Call starts with coding scheme 2 Link Adaptation algorithm is used to select the optimum coding scheme The coding scheme will change based on the BLER Retransmissions always occur with the same coding scheme CS selection can use link adaptation (LA), or can be fixed (using PRFILE parameters) to either CS-1 or CS-2 at all times.
RLC
CS2
BLER ok
CS2
RLC
CS2
RLC
BLER under the crosspoint
CS1
CS1
RLC
BLER CS2 above the crosspoint CS2
CS2
97
NOKIA
Link Adaptation Algorithm

The coding scheme will change based on set BLER Thresholds. The BLER thresholds are defined by simulations and change from hopping to non hopping networks Frequency Hopping
From CS1 to CS2

= 1- (X kbps/8 kbps) CS1 FH 14% CS1 NFH 69%
CS1 & CS2 Crosspoint Throughput
X
From CS2 to CS1
= 1 - (X kbps/12kbps) CS2 FH 43% CS2 NFH 79%
C/I
98
NOKIA
Link Adaptation (Hopping)

25 20
CS-2 BLER=43%
User Data Throughput ( Kbit /s)
15
10
CS- 1 5 CS- 2
CS-1 BLER=14%
0 4 6 8 10 12 14 16 18 20 22 24
CS- 3 CS- 4
26
28
30
C/I = 6.5 dB
C / I ( dB )
99
NOKIA
Power Control Parameters

Parameter Binary representation ALPHA Recommended value 7 (GSM900) 8 (GSM1800) Binary representation GAMMA 34 (GSM900) 36 (GSM1800) Idle mode signal strength filter period (IFP) 9 Transfer mode signal strength filter period (TFP) 13
100
NOKIA
Uplink Power Control

PCH = min(G0 - GCH - a*(C + 48),PMAX)
G 0, GCH
sets the maximum MS power level Default 39 (GSM900) 36 (GSM1800 / 1900)
Ms Output Power (dBm)
Uplink Power Control

35
sets the minimum MS power level Range 062 Default 34 (GSM900) 36 (GSM1800 / 1900) sets the slope for the uplink power level Range 010 (equivalent 0.0.1.0) Default 7 (GSM900) 8 (GSM1800 / 1900) is the received signal level
30
25
20
0.3
15
10
PMAX max MS power allowed in the cell
Signal Strength (dBm)
PC parameters for MS are transmitted on BCCH (SI13)

-9 8 -1 00 -1 02 -1 04 -1 06 -1 08 -1 10
-4 8
-5 0
-5 2
-5 4
-5 6
-5 8
-6 0
-6 2
-6 4
-6 6
-6 8
-7 0
-7 2
-7 4
-7 6
-7 8
-8 0
-8 2
-8 4
-8 6
-8 8
-9 0
-9 2
-9 4
-9 6
Power Control Parameters example

Power Control (GSM900) with different (alpha - gamma) values
35 30
MS TX Pwr
25 20 15 10 5 0
(0.7 - 17) (0.7 - 34)
-94
-86
-78
-70
-62
-54
-46
-38
-30
-22
-110
-102
DL Level
102
NOKIA
-14
-6
Power Control Parameters

Gamma range is 0 dB to 62 dB. It is transmitted in a 5-bit field, ie 32 combinations: 00000 ~ 0 dB 00001 ~ 2 dB 00010 ~ 4 dB 11111 ~ 62 dB MML range is 0 dB to 62 dB in steps of 2 dB NMS DB range is 0 to 31 corresponding to 0 to 62 dB
103
NOKIA
Uplink Power Control Averaging Parameters

Packet Transfer / Idle Mode Signal Strength Filter Period = 25
Mobile Output Power
40
Packet Transfer / Idle Mode Signal Strength Filter Period = 1

Mobile Output Power
40
20
20
0
105 118 131 144 157 170 183 196 209 222 235 248 261 274 287 300 313 326 339 352 365 378 391 404 417 430
106
121
136
151
166
181
196
211
226
241
256
271
286
301
316
331
346
361
376
391
406
421
436
451
-20
SS P_IDLE P_TRANSFER
Power
Power
-20
-40
-40
-60
-60
-80
-80
104
NOKIA
443
14
27
40
53
66
79
92
16
31
46
61
76
91
Uplink Power Control Averaging Parameters

Measuremen t Mode Mobile State Packet Transfer Mode Ready Packet Idle Mode Standby
Parameter
Range Default
9 025
Packet Idle Mode Signal Strength Filter Period 025 Packet Transfer Mode Signal Strength Filter Period 13
105
NOKIA
Charging in the GPRS Network

Um BTS BSC
Gb
SGSN
Billing System
charging info flow

Charging Gateway
GPRS backbone network (IP based)
Gn
GGSN
Gi
dataflow
106
NOKIA
GPRS Charging introduces new billing concepts

GSM traffic GPRS traffic
Access Point Name IP Address Allocation
Data Volume Context duration SMS transaction Necessary
Rating based on:

Usage based on: Intermediate records:
Dialed digits
Call duration SMS transaction
Not needed
107
NOKIA
Why consolidation of charging data is necessary ?

Voice calls are Continuous and have a relatively short duration
GPRS users are "always connected"

GPRS Attach/ Activate PDP
Intermediate CDR
GPRS Detach/ Deactivate PDP
7AM
108 NOKIA
8AM
9AM
10AM
11AM
12PM
1PM
2PM
3PM
Dimensioning
109
NOKIA
TSL Sharing
TSL sharing reduces data pipeline capacity if there is not enough TSL available for GPRS. As GPRS traffic increases there will the need to introduce new TRX's in order to avoid excessive TSL sharing.
Peak throughput
12 Kbps (GPRS CS1-2)
C/I distribution
TSL Capacity
TSL sharing
User throughput per allocated TSL
1 TSL
Reduces data pipeline capacity
Traffic Model - Assumptions

Total Traffic Load GPRS Traffic Load Circuit Switched
00:00 06:00 12:00 18:00 23:59
Time of Day
00:00
06:00
12:00
18:00
23:59
Time of Day
111
NOKIA
Delay Vs Load
Increasing the system GPRS territory occupancy (more occupied TSLs on average)
decreased data rates per user increased transmission delay per user Evolution of Throughput and LLC Frame Delay (1 TSL MS)
13
12 11 10 9 Mean Net Session Throughput (kbps) 8 7 6 5 4 3 0 1 2 3 4 5 6 7 8 13 12 11 10 9
LLC Frame Delay (s)

8 7 6 5 4 3
Offered Load (Mbps)

Rate Reduction (1)

CSW and GPRS traffic levels (offered loads) vary dynamically.
TRX 1 CCCH
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
A)
Circuit Switched
Packet Switched
TRX 2
TS
Time = T1 GPRS Territory = 6 TSLs
Two 3 TS mobiles each achieve 3*12kb/s = 36kb/s DL (CS-2 @ 10% BLER)
TRX 1 CCCH
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
B)
TRX 2
TS
Circuit Switched Packet Switched
Two 3 TS mobiles now each achieve 12/2 kb/s = 6kb/s DL
Time = T2 GPRS Territory = 1 TSL
113
NOKIA
Rate Reduction (2)

GPRS traffic levels (offered loads) vary dynamically
TRX 1 CCCH
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
TS
A)
TRX 2
TS
Time = T1 GPRS Territory = 3 TSLs
A single 3 TS mobile achieves 3*12kb/s = 36kb/s DL (CS-2 @ 10% BLER)
TRX 1 CCCH
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
TS TS
B)
TRX 2
TS
Time = T2 GPRS Territory = 3 TSL
Each 3 TS mobile now achieves 12/9 kb/s = 1.3 kb/s DL (all 3 TLSs full with 3*9 = 27 MSs)
114
NOKIA
Rate Reduction (3)

Occupancy
A level of service guarantee to users requires reasonable blocking levels:

CSW - e.g. 2% Erlang B blocking PSW - e.g. 70-80% of resources used on average = Occupancy
If average occupancy is low:
High user data rates most of the time (typically sole access of 1 or more TS)
115
NOKIA
Rate Reduction (4)

Rate Reduction
If average occupancy is high and CSW traffic level increases above average all users get reduced data rates due to TS sharing rate reduction When GPRS traffic peaks, increased sharing will occur rate reduction Performance is therefore a compromise between user level of service (rate reduction) and system throughput (occupancy).
116
NOKIA
Rate Reduction (5)- Rate Table

Mean GP R S territory T ypical data rate achieved occupancy (%) (% of maximum rate) 10-20 95 20-30 90 30-40 85 40-50 80 50-60 75 60-70 70 70-80 65 80-90 57 90-100 50 Average usage of GPRS Average user data rate system resources (Rate "Efficiency / Reduction")
(Occupancy Factor)
NOTE: The above approximations to user data rate values versus average GPRS territory occupancy values were obtained from simulation results. These values are very dependent upon the traffic models etc. and WILL change depending on the inputs!
117
NOKIA
Traffic Dimensioning
Capacity Available (TSL) - TRX
Load CSW - (Erlang-B)
Margin
GPRS Load
Total Capacity = CSW + Margin+ (GPRS Traffic * Territory Occupancy)
118
NOKIA
Free capacity for GPRS (Cell Usage Efficiency)

CSW traffic 1TRX 41 59 68 73 77 79 % of cell capacity Territory margin 44 31 25 19 15 14 GPRS capacity
2TRX 3TRX
4TRX
5TRX 6TRX
119
NOKIA
Traffic Dimensioning Guidelines (1)

Find number of TCH per cell (NTCH) Define CSW traffic (NCSW) Estimate Free TSLs for CSW(Territory margin) (NTEM) Calculate mean number of GPRS TSLs, NGPRS, as
NGPRS = NTCH - NCSW - NTEM
120
NOKIA
Traffic Dimensioning Guidelines (2)

Estimate number of occupied GPRS TSLs, NGPRS_USED, as NGPRS_USED = NGPRS * Territory Occupancy where the Territory Occupancy is obtained from rate reduction table Calculate total cell throughput as NGPRS_USED * Mean data rate/TSL
121
NOKIA
Capacity Planning
Erlang B model Based on average use of voice time slots. Not suitable for bursty data such as in packet systems. However, can be used to derive average available timeslots for GPRS.
No of T R X (T C H)
G S MT raffic (offered) @ 2% blocking (E rl) 2.9 8.2 14.9 21.9 29.2 36.5 43.9 51.5
MF T S
Mean free T C H for G P R S (2% blocking) 3.1 4.3 5.6 5.6 5.8 6.5 7.1 6.5
G S MT raffic (offered) @1% blocking (E rl) 2.5 7.4 13.7 20.3 27.3 34.3 41.5 48.7
Mean free T C H for G P R S (1% blocking) 3.5 5.1 6.8 7.2 7.7 8.7 9.5 9.3
1 (7) 2 (14) 3 (22) 4 (30) 5 (38) 6 (46) 7 (54) 8 (62)
1 1.5 1.5 2.5 3 3 3 4
2 TRX = 14 TCH EXAMPLE: CSW uses 8.2 TCH - 1.5 free TSL = 4.3 TSL available for GPRS (on average)
BSC Dimensioning
Dimensioning Rules
PCU Dimensioning Criteria is based on the following maximum criteria: PDCH capacity (e.g. 256) BTS capacity (e.g. 64) Data processing capacity (e.g. 2 Mbit/s) TRX capacity (e.g. 128) Confirm actual PCU limitations with latest version of NED.
123
NOKIA
BSC Dimensioning
Simple Dimensioning Example (PCU)
# BSCs and # TRXs # TCHs/cell used by GPRS on average Estimate GPRS traffic: (Total User traffic) Mbit/s + Overhead + Burst Margin - Based on # bytes packet size Input Calculations Result
124
1. Minimum requirement: # BSC = # PCUs required 2. # TCHs/cell used by GPRS => PCU supports 64 cells (256/#TC Calculate PCUs required based on number of cells / BSC. 3. GPRS traffic: (Total User Traffic) / 2 Mbit/s = # PCUs required
Take the biggest of the results above
NOKIA
Core Network Terminology

BTS Physical Abis Link BSC
Packet Control Unit
SGSN Gb Link
Packet Processing Unit
PCU
PAP U
Logical
BTS_I D
Base Station Virtual Circuit ID
NSEI
Network Services Equipment ID Network Services Virtual Circuit ID
Virtual
BVCI = BTS ID + 10000
NSVCI NSVCI NSVCI
125
NOKIA
Gb Interface Protocol Stack

SNDCP LLC
RELAY RLC BSSGP
BSSGP NS FR Gb SGSN
MAC GSM RF BSS
NS FR
Physical layer : PCM frame of 32 or 24 TSL, each 64kbit/s FR layer : end to end logical virtual circuit are created for data transmission (PVC, SVS). They addressed by e-to-e PVCI and node to node DLCI. FR provides NS with DLCI & FR bearer channel. NS :
Gb, Logical Structure

SGSN
PAPU 1
NSEI_1
BVCI_0 NS-VCI_7
Bearer Channel_1
DLCI_16
BSS 1
PCU 1
NS-VCI_7
NSEI_1
BVCI_0 BVCI_3
DLCI_17 NS-VCI_2
BVCI_3
NS-VCI_2
Bearer Channel_2
DLCI_16 DLCI_17
LA
PCU 2
NS-VCI_5
RA 1
BTS_3
NSEI_2 NS-VCI_5
BVCI_0 NS-VCI_8 BVCI_6 NS-VCI_3
NSEI_2
BVCI_0 BTS_6
DLCI_18
Bearer Channel_3
DLCI_16
DLCI_17
NS-VCI_8 BVCI_6 NS-VCI_3
RA 2
BTS_8
PCU 3 PAPU 2
NSEI_3 NS-VCI_4
BVCI_8 BVCI_0 BVCI_22 NS-VCI_1
Bearer Channel_4
NS-VCI_4 DLCI_16 NS-VCI_1
BTS_22
NSEI_3
BVCI_8 BVCI_0 BVCI_22
NS-VCI_11
NS-VCI_11
Bearer Channel_5
DLCI_16
PAPU 3
NSEI_7
BVCI_0 BVCI_22 NS-VCI_6
DLCI_17
BSS 2
PCU 3
NSEI_7
NS-VCI_6 BVCI_0 BVCI_22
Bearer Channel_6
LA RA
BTS_22
NS-VCI_9
BSSGP NS FR
Data Signal Data & Signal
NS-VCI_9
Logical Channels in Physical Link
BVCs NS-VCs, CIR=162048 kbit/s FR bearer channels, 132 TSL

PCM Link 32 TSL
PCU
FR bearer channels run on PCM links (642048 kbit/s) Max. 4 NS-VCs configured on FR bearers (CIR of each 162048 kbit/s) Max. 4 NS-VCs per NSE (PCU), and 256 NS-VCs per PAPU
128
NOKIA
Gb Link Dimensioning
Gb Frame Relay Connection in a Nutshell
Frame Relay traffic is carried in logical 64 kbit/s PCM time slots. Each active PCU has its own separate Gb interface connection, I.e. FR connection Capacity: n * 64 kbit/s, where n = 131. 64 kbit/s 1.984 Mbit/s (E1 speed)
At least one 64 kbit/s PCM TSL is required per active PCU
129
NOKIA
Dimensioning Rules
Dimensioning criteria for the number of 64kbit/s links:
1. At least two 64 kbit/s channels per BSC is recommended (due to bursty nature of data) 2. At least one 64 kbit/s channel per active PCU 3. Dimensioning is based on estimated GPRS traffic levels during the Busy Hour + the estimated protocol overhead on the Gb interface traffic
130
NOKIA
Simple Dimensioning Example (Gb links)
Calculations Input
131 NOKIA
Total GPRS Traffic
1. At least two 64 kbit/s links per BSC 2. One 64 kbit/s links per PCU 3. GPRS traffic: (Total GPRS Traffic) Mbit/s / 64 kbit/s / link
Result
Take the larger of the results above
SGSN Dimensioning
Nokia SGSN in a Nutshell
Investments can be matched with operators needs Flexible configurations with modular expansion steps
0
PDFU 0
PDFU 1
PDFU 0
PDFU 1
CLBU 0
PAPU 0
GSW 0
GSW 1
SMMU 0 2
SMMU 1
CLBU 1
CLSU
One fully equipped SGSN element has the following design targets concerning connectivity: 120 physical 2Mbps E1-PCMs PCMs are freely selectable between Gbinterface and SS7 based interfaces (Gs, Gr, Gd, Gf) 96 SS7 signalling links (24 per SMMU) 1024 64kbps Frame Relay links for Gbinterface use (64 in each PAPU) E.g 100 BSCs each having 8x64kbps Gbinterface connection could be connected into one SGSN 16 100-baseTX Ethernet connections for Gn-interface use (one in each PAPU) Maximum of 16 000 Routing Areas, 2 000 Location Areas
MCHU 0
SD MCHU 0
SD MCHU 1
3 MCHU 1 4 SMMU 2 SMMU 3 SMMU 4
OMU 0
SD OMU 0
SD OMU 1
5 OMU 1 6 PAPU 5 PAPU 6 PAPU 7 PAPU 8
7 ET 0 ( 32 * ET2E/A) ET 1 ( 28 * ET2E/A) 8 PAPU 9 PAPU 10 PAPU 11 PAPU 12
9 PAPU 1 PAPU 2 PAPU 3 PAPU 4 10 PAPU 13 PAPU 14 PAPU 15 PAPU 16
132
NOKIA
SGSN Dimensioning
SGSN SG1 Capacities
Data processing capacity of fully equipped SGSN: 48 Mbit/s Subscriber capacity: 120 000 Active PDP contexts: 240 000 1024 64kbit/s FR links for Gb-interface use (64 in each PAPU) 96 SS7 signalling link interfaces (@ 64 kbit/s, 24 in each SMMU)
Fully equipped SGSN contains: 16+1 PAPUs (Packet Processing Unit) 4+1 SMMUs (Signalling & Mobility Management Unit)
133
NOKIA
SGSN Dimensioning
SGSN SG1 Configuration Levels
Capacities: SGSN
12 Mbit/s 30 000 subscr. 256 Gb IF (64kbit/s) 24 Mbit/s 60 000 subscr. 512 Gb IF (64kbit/s) 36 Mbit/s 90 000 subscr. 768 Gb IF (64kbit/s) 48 Mbit/s 120 000 subscr. 1024 Gb IF (64kbit/s)
Basic Unit
4 PAPUs, 1 SMMU 4 PAPUs, 1 SMMU
Extension Units
4 PAPUs, 1 SMMU 4 PAPUs, 1 SMMU
GSN can be configured in four steps. The right configuration level for each case is determined by the dimensioning rules.
SGSN Dimensioning
Dimensioning Rules
Dimensioning criteria for the number of SGSN per basic/extension units: 1. Subscriber capacity: 30 000 subscribers simultaneously 2. Data processing capacity: 12 Mbit/s 3. Capacity of 64 kbit/s Gb interfaces: 256 ie. increment the number of units if any one of the above figures is exceeded until SGSN is fully equipped.
135
NOKIA
SGSN Dimensioning
Simple Dimensioning Example (SGSN)
Input Estimated subscriber volume: # subscribers
(simultaneously attached during the BH) Estimated total GPRS traffic during the BH: # Mbit/s with the overhead correction: # Mbit/s Number of 64kbit/s Gb links:
Calculations
136 NOKIA
1. Subscriber cap: # SGSN with Basic Unit 2. Data cap: # SGSN with Basic Unit 3. Gb I/F cap: # SGSN with Basic Unit
Take the biggest of the results above
Result
GPRS Radio Case Study - Traffic Dimensioning
137
NOKIA
Radio Case Study - Available Capacity

BTS
TRX 1 TRX 2
BSC BTS
CCCH SDCCH TS
TS
TS
TS
TS
TS
TS
TS
TS
T S
TS
TS
TS
TS
TS TS CCCH
= GPRS Traffic
TS
= Free TSL for CSW
= CSW Traffic
= Signaling
2 TRX Cell (16) - Signaling Channels (2)- 2% Blocking CSW (8.2 ) - Free TSL (1.5) = TSL Available for GPRS (4.3)
138
NOKIA
Radio Case Study - Network Quality

Planning Tool
25
Simulation Results (Hopping Network)
20
User Data Throughput (Kbit/s)
15
10
CS- 1 5 CS- 2 CS- 3 CS- 4 0 4 6 8 10 12 14 16 18 20 22 24 26 28 30 C / I ( dB )
Network C/I v Simulation results = Throughput per TS (13.1 Kbit/s with CS2)
Radio Case Study - Dimensioning

Mean G P R S territory occupancy in Network (%) 10-20 20-30 30-40 40-50 50-60 60-70 70-80 80-90 90-100 T ypical User Data rate achieved (% of maximum rate) 95 90 85 80 75 70 65 57 50
BTS
TSL Available for GPRS (4.3)
Rate Reduction - Occupancy (65%)
4.3 * 65%*13.1Kbit/s = 36.6 kbit/s
Planning Tool - TSL (13.1 kbit/s)
140
NOKIA
Radio Case Study - Network Example

BSC
Characteristics
% (< C/I dB)
Macro_m icro_CI_stats_10x10km 70.00 60.00 50.00
93 Cells 209 Transceivers 1122 TCH 389 Default GPRS TSLs
40.00 %(<) 30.00 20.00 10.00 0.00 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 C/I (dB)
Quality = 13.1 kbits (Frequency Hopping) 1122 TSL Available = 733 CSW + 389 GPRS 389 * 65%(Occupancy) * 13.1kbit/s = 3.31 Mbit/s @ BSC
PCU Capacity = 256 TSL or 64 Cells or 2Mbit/s = 2 PCU required for this BSC BSC 2*256-389 = 123 TSL for Additional Capacity
Performance
142
NOKIA
Impact of C/I on GPRS Throughput (Frequency Hopping Case, TU3 FH)

25 20
15
LA follows CS1 & CS2 "Envelope"
10
CS- 1 5 CS- 2 CS- 3 CS- 4 0 4 6 8 10 12 14 16 18 20 22 24 26 28 30 C / I ( dB )
CS1 achieves higher user throughput when radio conditions are poor (<6.5dB C/I)
Link adaptation ensures highest user data rate in Frequency Hopping networks
Impact of C/I on Throughput (Non-Hopping Case, TU3 NH)

25 20
Data Throughput (kb/s)
LA follows CS2 "Envelope"

CS-1 CS-2 CS-3
15
10
CS-4
0 -8 -6 -4 -2 0 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 C/I (dB)
Link Adaptation has no impact for CS-1 and CS-2
144
NOKIA
GPRS Frequency Planning

Urban areas are interference limited Interference directly influences achievable data rates
Overall system performance is dictated by C/I (carrier-to-interference) values
145
NOKIA
GPRS User Throughput
25 20
IMPROVEMENT
15
10
CS- 1 5 CS- 2 CS- 3 CS- 4 0 4 6 8 10 12 14 16 18 20 22 24 26 28 30 C / I ( dB )
Network Changes Microcells Picocells Dual Band Allocation Radio Features IUO (Regular Only) /FH Optimization Antenna Tilting Parameter Optimization Effective Fault & Performance Management
User Throughput - User Perceived Data Rate BSS Dimensioning - Less Throughput > Capacity
146
NOKIA
Coverage Planning
Rural areas are noise-limited Noise directly influenses achievable data rates at the cell edge (i.e. cell range at a given QoS, 10 % BLER for GPRS) Overall coverage area is dictated by C/N (carrier-to-noise ratio) values
147
NOKIA
Coverage Planning
C/N values for GPRS Coding Schemes
Coding Scheme
QoS
C/N Non Hopping [dB]
C/N Frequency Hopping [dB]
CS-1
CS-2 CS-3 CS-4
BLER < 10 %
BLER < 10 % BLER < 10 % BLER < 10 %
10.3
12.6 14.0 18.3
7.5
11.1 13.3 20.6
148
NOKIA
Relative Coverage Ranges

Percieved Cell Radius of Different GPRS Coding Schemes proportional to CS1 (Hopping) 100 100 84 80
81 74 71 67
60 52 45 40 Hopping Non Hopping
20
0 CS1 CS2 CS3 CS4
Coding Scheme 1 provides best coverage with both hopping and non hopping. Coding Schemes 2 and 3 provide comparable coverage Ideal Hopping gives an effective coverage gain (Except CS4 - no FEC)
149
NOKIA
GPRS Link Budget

TU50, non-hopping
GENERAL INFO Frequency (MHz): RECEIVING END: RX RF-input sensitivity Interference degr. Margin Cable loss + connector Rx antenna gain Diversity gain Body loss Isotropic power Field strength TRANSMITTING END: TX RF output peak power (mean power over RF cycle) Isolator + combiner + filter RF-peak power, combiner output Cable loss + connector TX-antenna gain Body loss Peak EIRP (EIRP = ERP + 2dB) Isotropic path loss
900
System:
Voice BS -108.00 3.00 3.00 18.00 4.00 0.00 -124.00 12.28 MS 1.00 30.00 0.00 30.00 0.00 0.00 3.00 0.50 27.00 151.00
900 MS -104.00 3.00 0.00 0.00 0.00 3.00 -98.00 38.28 BS 14.13 41.50 3.50 38.00 3.00 18.00 0.00 199.53 53.00 151.00
CS-1 BS -107.80 3.00 3.00 18.00 4.00 0.00 -123.80 12.48 MS 1.00 30.00 0.00 30.00 0.00 0.00 0.00 1.00 30.00 153.80
GPRS MS -104.00 3.00 0.00 0.00 0.00 0.00 -101.00 35.28 BS 13.49 41.30 3.50 37.80 3.00 18.00 0.00 190.55 52.80 153.80
CS-2 BS -104.00 3.00 3.00 18.00 4.00 0.00 -120.00 16.28 MS 1.00 30.00 0.00 30.00 0.00 0.00 0.00 1.00 30.00 150.00
GPRS MS -100.00 3.00 0.00 0.00 0.00 0.00 -97.00 39.28 BS 14.13 41.50 3.50 38.00 3.00 18.00 0.00 199.53 53.00 150.00
dBm dB dB dBi dB dB dBm dBV/m
W dBm dB dBm dB dBi dB W dBm dB
Key Performance Indicators (KPI)

OPERATORS USER GROUPS Users finally decide what are KPI when they define the contents REPORTS of the report
KPI
PI
MANAGEMENT MARKETING
PI KPI a PI PI
a b c
PLANNING O&M CUSTOMER CARE
KPI b
. . .
DISTRIBUTION
. . .
. . .
PI GENERATION KPI xx
. . .
zz
PI=Performance Indicator (counter, formulae, figure from MML output)

WORK PROCESS KNOW - HOW TOOLS KNOW - HOW FORMULAE KNOW - HOW
PERFORMANCE STATISTICS SERVICE OF NOKIA CUSTOMER SERVICES
151
NOKIA
Performance Indicators - Air Interface

Data Connectio n Setup Success Rate AGCH Success Ratio RACH Success Ratio Paging Throughput Release Rate
PDTCH
Ratio
Flush
Blocking
Requested vs Allocated Territory Upgrade Request Territory Utilisation
CS1 / CS2
Retransmission Ratio No Response Suspend
Success Ratio
From MS
CSW Load
152
NOKIA
Performance Indicators - Air Interface

MO Uplink TBF
Ready State send RACH Establish Immediate Assignment PDTCH Availability Either PCU or TRX Get PDCH Available Capacity Requested TSL to Allocated TBF Session Release phase
AGCH Availability
Data Connection Success
TBF Session Success
MT Downlink TBF(MS in Standby)

In Standby Paging From Network Paging Success Rate Availability Establish Uplink TBF Uplink TBF Establishment Immediate Assignment Requested TSL to Allocated TBF Session Release Phase
Available Capacity
Data Connection Success

TBF Session Success
New GPRS-Related Counters in Existing BSC Measurements
Resource Availability
GPRS Territory Counters (001174-001181)
Traffic
GPRS Occupancy(002061-002068)
Resource Access
AGCH,PCH counters (003046-003058)
Handover
GPRS initiated Intracell Handover (004130)
154
NOKIA
GPRS-related S9 Measurements
Packet Control Unit Measurement
Provides information about TBFs
RLC Blocks per cell measurement
Provides cell specific information about the RLC/MAC data blocks
Frame Relay measurement
Provides bearer-specific information about the proper working in the frame relay
155
NOKIA
GPRS related BSC counters 1/4

General TBF counters: 72000 Number of established uplink TBFs (note 1) 72001 Maximum duration of normally released uplink TBFs 72002 Maximum number of simultaneous uplink TBFs 72003 Average duration of normally released uplink TBF 72005 Number of established downlink TBFs 72006 Maximum duration of normally released downlink TBFs 72007 Maximum number of simultaneous downlink TBFs 72008 Average duration of normally released downlink TBF 72010 Number of established uplink TBFs in unack mode 72011 Maximum duration of normally released uplink TBFs in unack mode 72012 Maximum number of simultaneous uplink TBFs in unack mode 72013 Average duration of normally released uplink TBF in unack mode 72015 Number of established downlink TBFs in unack mode 72016 Maximum duration of normally released downlink TBFs in unack mode 72017 Maximum number of simultaneous downlink TBFs in unack mode 72018 Average duration of normally released downlink TBF in unack mode Coding scheme performance: 72062 Number of valid RLC data blocks in uplink with CS1 coding scheme 72063 Number of new RLC data blocks in downlink with CS1 coding scheme 72064 Number of valid RLC data blocks in uplink with CS2 coding scheme 72065 Number of new RLC data blocks in downlink with CS2 coding scheme 72066 Number of valid RLC data blocks in uplink in unack mode 72067 Number of new RLC data blocks in downlink in unack mode 72068 Number of bad frame indications in uplink with CS1 coding scheme in acknowledged mode (note 1) 72069 Number of bad frame indications in uplink with CS2 coding scheme in acknowledged mode (note 1) 72070 Number of retransmitted nacked RLC data blocks in downlink with CS1 coding scheme in acknowledged mode 72071 Number of retransmitted nacked RLC data blocks in downlink with CS2 coding scheme in acknowledged mode 72072 Number of ignored RLC data blocks in uplink due to BSN in acknowledged mode (note 2) 72073 Number of bad frame indications in uplink in unacknowledged mode (note 1)
156
NOKIA

TBF Establishment and Allocation: 72034 Number of 1 TSL requested for one TBF in uplink allocation 72035 Number of 2 TSLs requested for one TBF in uplink allocation 72036 Number of 3 TSLs requested for one TBF in uplink allocation 72037 Number of 4 TSLs requested for one TBF in uplink allocation 72038 Number of 5 - 8 TSLs requested for one TBF in uplink allocation 72039 Number of 1 TSL requested for one TBF in downlink allocation 72040 Number of 2 TSLs requested for one TBF in downlink allocation 72041 Number of 3 TSLs requested for one TBF in downlink allocation 72042 Number of 4 TSLs requested for one TBF in downlink allocation 72043 Number of 5 - 8 TSLs requested for one TBF in downlink allocation 72044 Number of 1 TSL allocated for one TBF in uplink allocation 72045 Number of 2 TSLs allocated for one TBF in uplink allocation 72046 Number of 3 TSLs allocated for one TBF in uplink allocation 72047 Number of 4 TSLs allocated for one TBF in uplink allocation 72048 Number of 5 - 8 TSLs allocated for one TBF in uplink allocation 72049 Number of 1 TSL allocated for one TBF in downlink allocation 72050 Number of 2 TSLs allocated for one TBF in downlink allocation 72051 Number of 3 TSLs allocated for one TBF in downlink allocation 72052Number of 4 TSLs allocated for one TBF in downlink allocation 72053 Number of 5 - 8 TSLs allocated for one TBF in downlink allocation 72082 Number of packet channel requests 72084 Number of Packet Immediate Assignment messages sent 72085 Number of Packet Immediate Assignment ack -messages 72086 Number of Packet Immediate Assignment nack -messages 72087 Number of Packet Immediate Assignment reject messages sent
72083 Number of Packet Paging Request -messages sent for CS paging in PACCH
157
NOKIA

TBF Re-allocation: Radio resource management territory upgrade and downgrade: 001174 GPRS territory upgrade requests 001175 Incompletely served GPRS territory upgrade requests 001176 GPRS upgrade requests rejected due to CSW traffic 001177 GPRS upgrade requests rejected due to lack of PSW 001178 GPRS upgrade requests rejected due to lack of PCU 001179 GPRS downgrades due to increase in CSW traffic 001180 GPRS upgrades due to decrease in CSW traffic 001181 GPRS territory downgrade requests 72027 Number of uplink TBF re-allocations 72028 Number of downlink TBF re-allocations 72029 Number of reallocations due to territory downgrade 72030 Number of uplink TBF reallocations due to establishment of simultaneous downlink TBF 72031 Number of downlink TBF reallocations due to establishment of simultaneous uplink TBF 72032 Number of uplink TBF reallocation failures 72033 Number of downlink TBF reallocation failures
TBF release: 72054 Number of uplink TBF release due to CSW traffic 72055 Number of downlink TBF release due to CSW traffic 72056 Number of uplink TBF release due to no response from MS 72057 Number of downlink TBF release due to no response from MS 72058 Number of uplink TBF release due to flush 72059 Number of downlink TBF release due to flush 72060 Number of uplink TBF release due to suspend 72061 Number of downlink TBF release due to suspend
158
NOKIA

Traffic: Available Cell TCH Resource: 002059 Ave Available Tch Timeslot Speech: 002046 Ave Busy Full Rate Tch 002048 Ave Busy Half Rate Tch 002050 Peak Busy Full Rate Tch 002051 Peak Busy Half Rate Tch Gprs: 002061 Ave Gprs Channels 002063 Peak Gprs Channels 002064 Ave Permanent Gprs Ch 002066 Peak Permanent Gprs Ch 002067 Ave Add Gprs Ch Hold Time
159
NOKIA
SGSN Measurements (1)

GPRS Mobility Management Measurement
Successful and failed GPRS attaches
GPRS Session Management Measurement
PDP context activations and deactivations

GTP packets sent in uplink and downlink
Data Measurement
User Measurement
Average and peak amount of attached users in SMMUs

Loads of different computer units
Load Measurement
160
NOKIA
SGSN Measurements (2)

Paging Measurement
Successful and unsuccessful RA and SGSN level paging
DNS Measurement
DNS inquiries Received S-CDRs and M-CDRs Successfully sent and received SMSs BSSGP functionality
CDR Measurement
SMS Measurement
Cell data Measurement
161
NOKIA
SGSN measurements & counters

Measurement type Counter GPRS Mobility Management GPRS Session Management Data Measurement User Measurement Paging Measurement Numbering 001xxx 002xxx 003xxx 004xxx 005xxx Measured object Cell Cell PAPU SGSN PAPU
Load Measurement
DNS Measurement CDR Measurement SMS Measurement
006xxx
007xxx 008xxx 009xxx
Computer unit
PAPU SGSN Cell
Cell Data Measurement
010xxx
Cell
162
NOKIA
SGSN measurements descriptions

Measurement of GPRS mobility management provides information on, for example, successful and failed GPRS attaches, PAPU and SGSN area updates. The mobility management functions are used to keep track of the current location of an MS within the public land mobile network (PLMN) or within another PLMN. This measurement collects one set of results for each cell. Measurement of GPRS session management provides information on, for example, different PDP context activations and deactivations. This measurement collects one set of results for each cell. Data measurement provides information on, for example, the number of GPRS tunneling protocol (GTP) packets sent in uplink and downlink direction. This measurement collects one set of results for each PAPU. User measurement provides information on, for example, average and peak number of attached users in signalling and mobility management units (SMMUs). This measurement collects one set of results for each SGSN. Paging measurement provides information on RA and SGSN level pagings and unsuccessful pagings. This measurement collects one set of results for each PAPU. Load measurement provides information on different computer units' load. This measurement collects one set of results for each computer unit. DNS measurement provides information on domain name server inquiries. This measurement collects one set of results for each PAPU. CDR measurement provides information on, for example, received S-CDRs and M-CDRs. This measurement collects one set of results for each SGSN. Measurement of short message services (SMS) provides information on, for example, successfully sent and received SMS. This measurement collects one set of results for each cell. Cell data measurement provides information on base station system GPRS protocol (BSSGP) functionality. BSSGP is the protocol used between SGSN and BSS. This measurement collects one set of results for each cell.
Useful Network Doctor GPRS Reports

229 GPRS KPI 051 Find cells having GPRS enabled TRXs 103 Routing areas 228 Cells by multislot allocations 213 Cell Doctor. Most GPRS counters in PCU measurement. 235 PCU measurement counters 202 Cells having most Delete indications and P-Imm.Ass.Nack 237 UL PTCH traffic 238 DL PTCH traffic 239 Territory upgrades and downgrades 240 Frame Relay 700 Cell related SGSN counters
164
NOKIA
Updates / interworking
165
NOKIA
Extended Cell
BTS
Extended cell coverage
GPRS is NOT supported in the extended cell range (i.e. E-TRX cannot carry GPRS traffic channels) If the MS moves out of normal cell area to the area of an extended
cell area, the TBF is released
166
NOKIA
DTX
GPRS does not use DTX - TBFs only exist when there is data to be sent The use of DTX for voice can improve system C/I and therefore improve GPRS performance
167
NOKIA
Frequency Hopping (1)

CS-1, CS-2 with SFH (8)
16 14 12 10 CS-1 FH CS-1 NH CS-2 NH CS-2 FH
kb/s
8 6 4 2 0 4 6 8 10 12 14 16 18 20 22 24 26 28 30 C/I (dB)
Shows that throughput is better for FH when C/I is > 8 dB
CS-1, CS-2 perform differently in a hopping environment

(different hopping gains for the same C/I)
Frequency Hopping (2)

Baseband Hopping Typically less frequencies in hopping list, so less hopping gain (but no gain for GPRS for number > 4). MS hops over all frequencies, including BCCH PreferBCCHforGPRS not relevant TS0 can not be used for GPRS - different hopping group RF Hopping Typically more frequencies so higher hopping gain BCCH does not hop PreferBCCHforGPRS can be used to move GPRS traffic onto nonhopping carrier.
169
NOKIA
AMH (TRHO)
Cell load = number of timeslots occupied by CS calls / (number of timeslots in the cell - number of timeslots in the dedicated PS territory) Triggering can be configured to support the default GPRS territory
GSM1800
Normal dominance area
GSM900
Dominance area in high load
Micro Cell
GPRS and Other Features

IUO/IFH:

GPRS MS doesn't have access to the IUO/IFH super layer Release1 does not support network requested cell re-selection No C/I estimation since GPRS MS never goes on SDCCH or SACCH Dual Band layer can be allocated as data layer In Idle mode, the C2 parameter can be used to pull the traffic to the dual band layer. Has priority over GPRS but can be controlled by HSCSD load parameters
Dual Band:

HSCSD:
171
NOKIA
GPRS and Other Features

GPRS rel2: More features and improvements coming, e.g: PBCCH (C31, C32, own neighbour lists for GPRS user, dedicated signalling for GPRS) Improved QoS MultiBCF/Common BCCH Segment concept New parameters EGPRS (EDGE): GPRS and EDGE MSs can use same TSLs but this kind of situation should be avoided (segmentation, parameters, new algorithms etc..) to enable the EDGE MS to use faster data rates Requires of checking dimensioning and configuration of the network (GPRS and EDGE at different territories at the same cell, Gb dimensioning etc..) DAP (Dynamic Abis Pool at Abis)
172
NOKIA

Gprs RPL

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Gprs RPL

Uploaded by

Copyright:

Available Formats

FUNDAMENTALS

GPRSRPL.PPT / 28-04-2003 / PPa

GSM Evolutionary Steps

GPRSRPL.PPT / 28-04-2003 / PPa

GPRS versus GSM Fundamental Differences

GPRSRPL.PPT / 28-04-2003 / PPa

GPRS Network - Overview

GPRS Core GPRS Backbone IP Network

Shared GSM and GPRS Infrastructure

GPRS Entry Network and Network Elements

Firewall OMC Inter-PLMN network

Firewall Internet or Intranet

GPRSRPL.PPT / 28-04-2003 / PPa

Gr Gd LAN SW / IP BB Gn DNS Gn CG Gc DNS

GGSN FW Gi DHCP LIG

Signaling Interface Signaling and Data Transfer Interface

GPRS Network Elements and Primary Functions

Temporary Block Flow

Downlink TBF (+ PACCH for uplink TBF)

PACCH (Packet Associated Control Channel): Similar to GSM CSW SACCH

Temporary Block Flow

Signalling Downlink data

Simultaneous Downlink TBF and Uplink TBF

Uplink data Downlink data

GPRSRPL.PPT / 28-04-2003 / PPa

Temporary Block Flow (TBF)

Identify ETSI Specification References folder ~\References\ETSI Specifications\

GPRSRPL.PPT / 28-04-2003 / PPa

Temporary Block Flow (TBF)

Unidirectional separate TBFs needed for uplink and downlink transfer

GPRSRPL.PPT / 28-04-2003 / PPa

TLLI / TBF Concept

TBF (TFI + TSL) TBF (RLC / MAC Flow)

TBF (LLC Flow)

TLLI (SNDCP Flow)

GPRSRPL.PPT / 28-04-2003 / PPa

Air Interface (RLC/MAC) MS Re-assembly (RLC/MAC -> LLC) Application

Air Interface (RLC/MAC) MS Re-assembly (RLC/MAC -> LLC) Application

GPRSRPL.PPT / 28-04-2003 / PPa

Temporary Block Flow

GPRSRPL.PPT / 28-04-2003 / PPa

Protocols and Framestructure

GPRSRPL.PPT / 28-04-2003 / PPa

GPRS System understanding: signaling multiframe structure (51 TDMA frames)

BCCH + CCCH 4 SDCCH/4 (downlink)

BCCH + CCCH 4 SDCCH/4 (uplink) F: B: D: R:

GPRSRPL.PPT / 28-04-2003 / PPa

Bursts on the Air Interface

4 x TDMA Frames = 4 Bursts = 1 RLC/MAC block = 18.46 ms

52 T DMA F rames (240 ms)

Data Block Format

N-PDU SN-DATA PDUs LLC Frames RLC Blocks

GPRSRPL.PPT / 28-04-2003 / PPa

Data Block Format

data data h FCS Data + h BCS

RLC/MA C GSM RF convolution coding GSM RF bursts (TS)

GSM and GPRS Multiframe

Radio Block 2 PTCCH

Radio Block 5 IDLE

Radio Block 8 PTCCH

Radio Block 11 IDLE

GPRSRPL.PPT / 28-04-2003 / PPa