3fl11830abaawbzza PDF

EVOLIUM Base Station Subsystem
GPRS & EGPRS Radio Algorithms Description / B9
TRAINING MANUAL
3FL11830ABAAWBZZA ed 1 – September 2005
© All rights reserved. Passing on and copying of this document,

use and communication of its contents not permitted without
written authorization from Alcatel.
© Alcatel 1
Safety Warning
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewellery while
working on the equipment. Always observe all safety precautions and do not work on the equipment alone.
Caution
The equipment used during this course is electrostatic sensitive. Please observe correct anti-static precautions.
Trade Marks
Alcatel and MainStreet are trademarks of Alcatel.
All other trademarks, service marks and logos (“Marks”) are the property of their respective holders including
Alcatel. Users are not permitted to use these Marks without the prior consent of Alcatel or such third party
owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service
name is not a Mark.
Copyright
This document contains information that is proprietary to Alcatel and may be used for training purposes only.
No other use or transmission of all or any part of this document is permitted without Alcatel’s written
permission, and must include all copyright and other proprietary notices. No other use or transmission of all
or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever
without prior written permission from Alcatel.
Use or transmission of all or any part of this document in violation of any applicable Canadian or other
legislation is hereby expressly prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes
or describes, and is expressly prohibited from modifying the information or creating derivative works without
the express written consent of Alcatel.
Alcatel, The Alcatel logo, MainStreet and Newbridge are registered trademarks of Alcatel.
All other trademarks are the property of their respective owners. Alcatel assumes no responsibility for the
accuracy of the information presented, which is subject to change without notice.
© 2004 Alcatel. All rights reserved.
Disclaimer
In no event will Alcatel be liable for any direct, indirect, special, incidental or consequential damages,
including lost profits, lost business or lost data, resulting from the use of or reliance upon the information,
whether or not Alcatel has been advised of the possibility of such damages.
Mention of non-Alcatel products or services is for information purposes only and constitutes neither an
endorsement nor a recommendation.
Please refer to technical practices supplied by Alcatel for current information concerning Alcatel equipment
and its operation.
© Alcatel 2
Product Line EVOLIUM Base Station Subsystem
Course Title GPRS and EGPRS Radio Algorithms Description / B9
Course Reference 3FL 11830 ABAA - ZZZZA
Audience Course content

Alcatel and Operator radio engineering team, BSS 1 Principles
optimization and quality system engineers. · 1.1 Service Overview
Objectives · 1.2 Alcatel GPRS Architecture
· 1.3 Main Transactions
During the course, the trainee will be able to
describe the GPRS and EGPRS radio
algorithms in order to improve the BSS 2 Radio Resource Management
performance. · 2.1 (E)GPRS Channels
By the end of the course, the participant will be · 2.2 Autonomous Packet Resource Allocation
able to:
· 2.3 TBF Radio Resources Allocation and Re-
- Describe the main (E)GPRS mechanisms and allocation
concepts.
· 2.4 TBF Release Routine
- Describe the radio algorithms and the related
· 2.5 Exercises
parameters.
- Estimate qualitatively the impact of a parameter
change in order to solve typical problems or 3 Radio Link Control
enhance the GPRS performance. · 3.1 GPRS CS Adaptation
Prerequisites · 3.2 EGPRS MCS Adaptation
Training module “Introduction to GPRS” · 3.3 RLC Blocks Retransmission
(3FL10472ABAA), “Introduction to GSM QoS and · 3.4 UL Power Control
Traffic Load Monitoring” (3FL10491ABAA) and · 3.5 NC0 Cell Selection and Reselection
“Introduction to Radio Fine Tuning” · 3.6 NC2 Cell Reselection
(3FL10493ABAA) or equivalent level.
· 3.7 Flow Control at the Gb Interface
Training Methods · 3.8 Radio Link Supervision
Theory / Practice. · 3.9 Exercises
Language
English, French 4 Algorithms Dynamic Behavior
· 4.1 Optimization of CS Adaptation
Duration
· 4.2 Optimization of Cell Reselection
5 Days
· 4.3 Enhance the (E)GPRS Performance
Location
Alcatel University or Customer Premises.
Number of participants
Maximum 12
© Alcatel 3
Page intentionally left blank
Note: Please print this document with comments pages
© Alcatel 4
1 PRINCIPLES
All rights reserved © 2004, Alcatel
© Alcatel 5
1 PRINCIPLES
Session Presentation
> Objective: to be able to describe the main GPRS
mechanisms and concepts
> Program:
1.1 Service Overview
1.2 Alcatel GPRS Architecture
1.3 Main Transactions
GPRS and E-GPRS Radio Algorithms Description / B9 6
© Alcatel 6
1 PRINCIPLES
© Alcatel 7
Data Transfer with GSM: Circuit Switching
Access Node
Air Interface
Internet
GSM
Network
> Circuit switching:

• Transaction is offered in connected mode.
• Allocation of a continuous radio resource UL/DL until the completion of the transfer.
• One circuit = one channel allocated per user.
• The traffic multiplexing is achieved inside the BSS, over the Ater interface.
> HSCSD: High Speed Circuit Switched Data
• A technology that allows the multislot allocation to one user.
• An important throughput can be achieved (up to 64 Kbit/s constant) but there is no optimization of the use of the
channel.
• (no dynamic allocation when data services are mainly carried in a bursty mode)
• The billing is time based like in GSM.
• Is likely to lead to an important congestion situation.
• Not offered by Alcatel.
© Alcatel 8
Data Transfer with GPRS: Packet Switching
Air Interface
GPRS
Internet
Network
> GPRS provides end-to-end packet-switched data transmission between MS users and fixed packet data networks.
> GPRS is a GSM feature.
> GPRS provides an efficient use of the radio resources:
• multislot operation,
• Flexible sharing of radio resources between MSs,
• Resources are allocated only when data are transmitted.
> Charging is based on the volume of data transmitted, not on connection time.
© Alcatel 9
MS Classes
> Three MS classes are defined:
• class A:
– simultaneous GPRS and GSM traffic
• class B:
– simultaneous GPRS and GSM attach but not simultaneous traffic
– an MS can be paged for a GSM call while performing a GPRS transfer
• class C:
– only GPRS
> Do not confuse with the multislot class of an MS, or the MS capacity, which characterizes the number of TSs one MS can
monitor in the UL and the DL simultaneously.
> For the detail of the MS multislot class, see the next slide.
> The main traffic class available on the market is Class B. Class C is preferred for PDA devices when Class A is not popular
in the phone industry.
© Alcatel 10
MS Multislot Class (1/2)
Multislot class Type Rx Tx Sum Ttb Tra Trb
1 1 1 1 2 2 4 2
2 1 2 1 3 2 3 1
3 1 2 2 3 2 3 1
4 1 3 1 4 1 3 1
5 1 2 2 4 1 3 1
6 1 3 2 4 1 3 1
7 1 3 3 4 1 3 1
8 1 4 1 5 1 2 1
9 1 3 2 5 1 2 1
10 1 4 2 5 1 2 1
11 1 4 3 5 1 2 1
12 1 4 4 5 1 2 1
13 2 3 3 NA 1 3 1
14 2 4 4 NA 1 3 1
15 2 5 5 NA 1 3 1
16 2 6 6 NA 1 2 1
17 2 7 7 NA 1 1 0
18 2 8 8 NA 0 0 0
19 to 29 like 10 1 x x NA
> MS type
• Type 1 are simplex MSs, i.e., without duplexer: they are not able to transmit and receive at the same time.
• Type 2 are duplex MSs, i.e., with duplexer: they are able to transmit and receive at the same time.
> Rx
• The maximum number of received time slots that the MS can use per TDMA frame. The received TSs shall be
allocated within window of size Rx, but they do not need to be contiguous. For SIMPLEX MS, no transmitted TS shall
occur between received TSs within a TDMA frame. This does not take into account the measurement window (Mx).
> Tx
• The maximum number of transmitted time slots that the MS can use per TDMA frame. The transmitted TS shall be
allocated within the window of size Tx, but they do not need to be contiguous. For SIMPLEX MS, no received TS shall
occur between transmitted TSs within a TDMA frame.
> SUM
• The maximum number of transmitted and received time slots (without Mx) per TDMA frame.
> The meaning of Ttb, Tra et Trb changes according to the MS type.
• For SIMPLEX MS (type 1):
– Ttb is the minimum time (in time slot) necessary between the Rx and Tx windows.
– Tra is the minimum time between the last Tx window and the first Rx window of the next TDMA in order to
be able to open a measurement window.
– Trb is the same as Tra without opening a measurement window.
• For DUPLEX MS (type 2):
– Ttb is the minimum time necessary between 2 Tx windows belonging to different frames.
– Tra is the minimum time necessary between 2 Rx windows belonging to different frames in order to be able
to open a measurement window.
– Trb is the same as Tra without opening a measurement window.
© Alcatel 11
MS Multislot Class (2/2)
> Class 4 (3+1):
0 1 2 3 4 5 6 7
Rx Rx Rx Mx
DL
Ttb Tra
Tx
UL
0 1 2 3 4 5 6 7
> Class 8 (4+1):

0 1 2 3 4 5 6 7
Rx Rx Rx Rx Mx
DL
Ttb Tra
Tx
UL
0 1 2 3 4 5 6 7
> Ttb is the minimum time (in time slot) necessary between the Rx and Tx windows.
> Tra is the minimum time between the last Tx window and the first Rx window of the next TDMA in order to be able to open
a measurement window.
> Trb is the same as Tra without opening a measurement window.
>All multislot classes are supported with the following limitations:

• type 1 MSs (simplex MSs) are limited to 2 UL slots and 4 DL slots.
• type 2 MSs (duplex MSs) are limited to 5+5 configuration.
• allocations with hole between slots of the same direction are not supported.
>The O&M parameters Max_PDCH_Per_TBF may limit the number of PDCHs allocated to a TBF.
© Alcatel 12
1 PRINCIPLES
© Alcatel 13
General Architecture
MSC/
TC VLR PSTN
HLR
BSC Gs Gr
BTS GSM Core Network
BTS MFS
Ater
Abis Mux GGSN
Gb Gn IP Gi Internet
SGSN Backbone Intranet
Radio Access Network
Charging Border
Gateway DNS/ Gateway
DHCP
GPRS & EGPRS Core Network
> The BSS is used for both circuit-switched and GPRS services.
> A GPRS core network (also called GSS, an IP backbone) offers the interconnection between the PDN and the BSS.
> The BSS has 2 clients:
• The MSC, for circuit-switched services (through the A interface).
• The GPRS backbone network, for packet-switched services (through the Gb interface).
> The A interface is unchanged.
> PDN X25 is not supported anymore by 3GPP.
© Alcatel 14
Main Entities - Interfaces
SMS-
Um BSS A MSC HLR
GMSC
Mobile Gs
Gb Gr Gd
GPRS
Gc
SGSN
Gn
Gi
SGSN GGSN PDN
Signaling + data
Pure Signaling GPRS Network
> GPRS network = IP network

> Note: Additional IP routers might be used to route the information between the GSNs (intra-PLMN backbone network).
All the elements connected to this backbone have private permanent IP addresses.
> Signaling protocols:

• MAP/TCAP/SCCP/MTP on Gr, Gd and Gc (through the SGSN for the latter),
• GTP/UDP/IP on Gn, BSSAP+/SCCP/MTP on Gs,
• GMM/SM/LLC on Gb/Um.
> Gc: for Network-Requested PDP contexts Activation (the GGSN asks the HLR for SGSN Routing Information).
> Gs: defines the Network Mode of Operation I. It allows to perform LA + RA combined Location Update, and PS and CS
Paging Coordination.
> Gr: exchange of Subscription Information at Attachment Phase.
> Additional interfaces:

• Gf (to the EIR).
• Gd to deliver the SMS to the mobiles via the GPRS network (SGSN option and subscriber feature).
© Alcatel 15
PCU
> A Packet Control Unit is defined by the GSM standard:
• It handles RLC/MAC functions
• It may be in the BTS, in the BSC or, in the SGSN
• Alcatel choice:
– PCU in a new network element called the MFS
– smooth and cost-effective introduction of the GPRS
BTS AterMux
BSC
BTS MFS SGSN
BSC
Gb
> The standard specifies that the PCU function shall be implemented in one of the 3 following entities:
• BTS,
• BSC,
• after the BSC (in the SGSN for instance)
> The implementation of the PCU functions determines the position of the Gb interface.
> ALCATEL chooses the MFS integration in order to offer a faster implementation inside the BSS as well as an easier
maintenance and supervision.
> MFS: Multi BSS Fast packet Server.
© Alcatel 16
B9
BSS
Radio Interface Abis Ater Gb
BTS BSC MFS SGSN

CCU RSL Radio GSL
PCU Gb
Resource
prot.
Management
CCU stack
M-EGCH
> GCH: the multiplexing capacity of the GCH link on the AterMux belongs to the granularity chosen. 1 Ater TS GPRS
dedicated = 1 GCH when allocated
> The number of 64 Kbit/s time slots assigned to PS traffic and signaling is configured by the Operator from the OMC-R,
with the following granularity: 4, 8, 15, 22, and 29 per PCM.
> The use of RSL is necessary as some GPRS originated signaling shall be carried over a CCCH, before the
establishment of a PDCH (PCH, AGCH).
© Alcatel 17
Transmission Plane
MS BTS MFS SGSN
Application
IP
SNDCP SNDCP
LLC LLC
Relay
RLC RLC
BSSGP BSSGP
MAC MAC
Relay
L2-GCH L2-GCH NS NS
GSM-RF GSM RF
L1-GCH L1-GCH L1bis L1bis
Um Abis/Ater(mux) Gb
>For the exact purposes of the tracing, please refer to “Introduction to GPRS & E-GPRS Quality of Service Monitoring”.
>It can be said from this protocol stacks diagram that after allocation of a GCH by the BSC to the MFS, the data carried
over the GCH are transparent for the BSC.
>The RLC function defines the procedures for segmentation and reassembly of LLC PDUs into RLC/MAC blocks and, in
RLC acknowledged mode of operation, for the Backward Error Correction (BEC) procedures enabling the selective
retransmission of unsuccessfully delivered RLC/MAC blocks. In RLC acknowledged mode of operation, the RLC function
preserves the order of higher layer PDUs provided to it.
>The RLC function also provides link adaptation.
>In EGPRS, in RLC acknowledged mode of operation, the RLC function may provide Incremental Redundancy (IR).
>The MAC function defines the procedures that enabled multiple mobile stations to share a common transmission
medium, which may consist of several physical channels. The function may allow a mobile station to use several physical
channels in parallel, i.e., use several time slots within the TDMA frame.
>For the mobile station originating access, the MAC function provides the procedures, including the contention
resolution procedures, for the arbitration between multiple mobile stations simultaneously attempting to access the
shared transmission medium.
>For the mobile station terminating access, the MAC function provides the procedures to queue and schedule access
attempts.
© Alcatel 18
Signaling Plane
MS BTS BSC MFS
GMM/SM
LLC
Relay
RLC
RRM BSSGP
RR/RRM
Relay
RR BSCGP BSCGP
NS
Relay
L2-RSL L2-RSL L2-GSL L2-GSL
GSM-RF GSM RF
L1-RSL L1-RSL L1-GSL L1-GSL L1bis
Um Abis Ater Gb
>2 GSLs at 64Kbit/s per GPU.

>RSL: refer to Dimensioning rules for GSM
© Alcatel 19
1 PRINCIPLES
© Alcatel 20
Session Management: Attach Procedure
> Aim: to access GPRS services, the MS must first make its presence
known to the network by performing a “GPRS attach” procedure with
the SGSN
> Results:
• a logical link between the MS and the SGSN is created
• the MS is in Standby state and may activate a PDP context
• the MS location is known (RA accuracy)
• the MS is available for PS paging via the SGSN
> A combined GPRS and IMSI attach is possible for class A/B MS
>Each signaling procedure taking place between the MS and the GSS involves UL and DL TBFs. Each GMM/SM
message triggers the establishment of a TBF. The complete attachment procedure in GPRS may involve up to 7 TBFs (4
UL and 3 DL).
>These TBFs are usually short (a few RLC blocks), thus the optimization of the TBF establishment time is very important,
as well as the TBF establishment success rate.
© Alcatel 21
Session Management: PDP Context Activation
> Aim:
• in order to send and receive GPRS data, the MS must activate the PDP
address it wants to use
> Results:
• the MS is known in the corresponding GGSN (the GGSN knows the
SGSN where the MS is located) and data transmission with external data
network can begin
>The PDP context activation procedure is fairly close to the call establishment of the GSM including the CCCH and the
SDCCH phases (between the Channel Request message of the MS on RACH to the Alert message).
>It is important to control the overall PDP context activation duration for a good overview of the GPRS QoS as it involves
MS, MFS, SGSN, GGSN. The duration is longer than the GSM call establishment.
© Alcatel 22
Mobility Management: Definitions
> For GPRS, as paging is more frequent than in GSM, RAs have been
defined smaller than LAs
> An RA is a subset of one and only one LA
> The MS location in Standby state is known in the SGSN at the RA level
> The MS is paged in its RA when MT traffic arrives at the SGSN
> One RA is served by only one SGSN
> 2 types of PCH/PPCH use shall be kept distinct for PS procedures:

• DL transfer establishment for MS in Ready State: mapping of the DL Immediate Assignment message
• DL transfer establishment for MS in Standby State (PS Paging Procedure): mapping of the Packet Paging Request
message
> The first type will obviously be used quite often but does not affect the dimensioning of the RA (the message is sent in
one cell only). The second type of paging message is sent over the RA and will occur more often that CS Paging as the
transfer mode of most external servers is bursty, so the rate of arrival of the PDU inside the SGSN is irregular. This is the
reason why an RA shall be dimensioned smaller than an LA if we want to achieve a battery use relative to GPRS Paging
procedures equivalent to the GSM one.
>For Mobility Management constraints in the CN, it is not recommended to split one RA over 2 LAs (the routing
information for a CN originated Paging Message being the BSC, a given BSC shall belong to a unique LA as well as a
unique RA).
© Alcatel 23
Mobility Management: MS States
MS MM states "Idle"
MS RR states
GPRS Attach GPRS Detach
Packet
Idle Mode
"Ready"
Packet
Transfer
Mode
PDU
T_READY expiry
Transmission
"Standby"
> Idle: the MS is not attached to the network: paging is not possible.
> Standby:
• the MS is attached to the network: paging is possible.
•The MS location is known in the CN with the RA accuracy.
> Ready:
• the MS location is known with the cell accuracy.
• timer T_READY keeps the MS in the Ready state just after data transfer.
> Packet Idle Mode:
• no Temporary Block Flow exists. Upper layers can require the transfer of an LLC PDU which, implicitly, may
trigger the establishment of TBF and transition to packet transfer mode.
• the MS listens to the PBCCH and to the paging sub-channel for the paging group the MS belongs to in idle
mode. If PCCCH is not present in the cell, the mobile station listens to the BCCH and to the relevant paging sub-
channels.
> Packet Transfer Mode:
• In packet transfer mode, the mobile station is allocated radio resource providing a Temporary Block Flow on one
or more physical channels. Continuous transfer of one or more LLC PDUs is possible. Concurrent TBFs may be
established in opposite directions. Transfer of LLC PDUs in RLC acknowledged or RLC unacknowledged mode is
provided.
• When selecting a new cell, the mobile station leaves the packet transfer mode, enters the packet idle mode where
it switches to the new cell, reads the system information and may then resume to packet transfer mode in the new
cell.
> The timers regulating the transition between states are SGSN timers, not tunable in the BSS.
> Caution: Idle mode in GPRS and Idle mode in GSM are two different states.
• A GSM MS in Idle mode is attached to an MSC and can be paged.
• A GPRS MS in Idle mode is NOT attached to an SGSN, so it cannot be paged but can monitor the GPRS
information broadcast in the SI13 of the BCCH.
> Standby is the closest GPRS MS state to Idle GSM.
> The MS state in the SGSN shall be considered apart from the Packet Transfer Mode in the BSS:
• MS in Standby mode can be in Packet Transfer Mode.
• MS in Ready mode can be in Packet Idle Mode.
> The detach procedure is usually triggered by the MS. Three other types of detach are triggered by the CN:
• HLR Detach,
• SGSN Detach upon SGSN overload,
• SGSN Detach upon timer.
© Alcatel 24
Mobility Management: MS Location Management
The MS enters a new

cell
New cell belongs to a new RA New cell belongs to a new LA

New cell inside the current RA
MS in Ready state
RA update RA/LA update

Only in NMO I
Cell update
>When the MS is in Ready State, it performs a “Cell Update”.

•The MS sends any LLC frame in the new cell with its TLLI in the header.
•The Cell and RAC information is added by the BSSGP at the programming of the BSSGP frame.
>RA Update:
•The MS sends an RA Update Request message containing the identity of the MS, the old RAI and the Update Type.
The update type is either enter a new RA or periodical RA update.
•The BSS adds the cell global Identity when transferring the message into a BSSGP frame towards the SGSN.
© Alcatel 25
Interactions Between the SGSN and the MSC/VLR
> The Gs interface between the MSC and the SGSN is needed
> Following actions are possible:
• IMSI attach/detach via the SGSN
• LA update via the SGSN
• CS paging via the SGSN
>The Gs interface carries signaling between the P-VLR (SGSN) and the VLR (MSC). Whether Gs is provided or not, it
does NOT belong to the BSS release as it is a CN feature.
>The presence of the Gs interface is given by the NMO information inside the SI13 and the CN feature in the PSI1.
>The Gs interface carries only MAP signaling between the P-VLR and the VLR of the MSC.
© Alcatel 26
Network Mode of Operation
Mode CS Paging Channel PS Paging Channel Remarks
PCH/PPCH PPCH Gs interface w MPDCH

Packet idle
mode
I PCH PCH Gs interface wo MPDCH
Packet
PACCH NA Gs interface transfer
mode
II PCH PCH no Gs interface
Packet idle
PCH PPCH no Gs interface mode
III
Packet
PCH NA no Gs interface transfer
mode
> All the possible combinations with the MPDCH are:

• NMOIII,
• NMOI with MPDCH.
> According to the NMO offered and the packet mode of the MS (Packet Transfer Mode or Packet Idle Mode), the
routing of the PS paging and the CS paging changes.
> The NMO setting is done from the OMC-R via the NETWORK_OPERATION_MODE parameter.
© Alcatel 27
CS/PS Paging During a Packet Transfer/Call (1/3)
> CS paging during packet transfer (class B MS):
• according to the GSM standard, a class B MS may or may not
(implementation dependent) listen to the PCH channel during a
packet transfer
• if the MS listens to the PCH channel:
– some RLC blocks are lost
– the MS receives all the CS paging messages
– the MS can start a CS call
– at the end of the call, the MS triggers an RA updating procedure
– Refer to Suspend/Resume for Class B MS
>The Class A and Class C GPRS mobiles do not face these problems. The former is able to handle simultaneously CS
and PS traffic (no traffic disruption), whereas the latter is not reachable in one domain while it is attached to the other
domain.
>The Class B situation is the most complex one and shall be considered since Class B GPRS mobiles are the most
popular for the manufacturers. It shall be remembered that the most important service in the GSM network where GPRS
is activated is the speech. Therefore, an MS shall be given the opportunity to listen to any CS paging. It is then up to the
operator and to the MS to decide whether or not the CS call shall be answered.
© Alcatel 28
End of on-going TBF
> Suspend/Resume for Class B MS: DL LLC PDUs are discarded
MS BSC MFS SGSN
The MS enters in
GSM dedicated
Mode (Ongoing GPRS 1. Suspend (TLLI, RAI)
2 Suspend
transfer or not)
3 Suspend (TLLI, RAI, suspend cause)
4 Suspend Ack (TLLI, RAI, SRN)

5 Suspend Ack
End of the GSM call Normally, no more paging

6 Resume (TLLI, RAI, SRN) messages sent by the SGSN
7 Resume
8 Resume Ack
9 Resume Ack
10 Channel Release
11 Routing Area Update Request

The MS leaves the GSM dedicated mode
The MS listens to “Channel Release” message content
>Suspend Reference Number (SRN)
>1) The GPRS suspension procedure is initiated by the MS by sending an RR Suspend (TLLI, RAI, suspension cause)
message to the BSC.
>2) The BSC sends a Suspend (TLLI, RAI, suspension cause) message to the MFS, via the GSL link. The BSC shall store
TLLI and RAI in order to be able to request the SGSN (via the MFS) to resume GPRS services when the MS leaves
dedicated mode.
>3) The MFS sends a Suspend (TLLI, RAI) message to the SGSN.
>4) The MFS receives a Suspend Ack from the SGSN, in which there is a Suspend Reference Number which will have to
be used in the resume step.
>5) The MFS sends a suspend acknowledgement to the BSC, with the Suspend Reference Number information.
>6) The BSC determines that the circuit-switched radio channel shall be released (typically upon circuit-switched call
completion). If the BSC is able to request the SGSN to resume GPRS services (i.e., the suspend procedure succeeded and
the BSC received the Suspend Reference Number, no external handover has occurred), the BSC shall send a Resume
(TLLI, RAI, Suspend Reference Number) message to the MFS.
>7) Upon receipt of a Resume message from the BSC, the MFS sends a Resume (TLLI, RAI, Suspend Reference Number)
message to the SGSN.
>8) The MFS receives a Resume Ack from the SGSN.
>9) Upon receipt of the Resume Ack from the SGSN, the MFS sends a Resume Ack message to the BSC.
>10) The BSC sends an RR Channel Release (GPRS Resumption) message to the MS and deletes its suspend/resume
context.
>11) The MS resumes GPRS services by sending a Routing Area Update Request message in the following cases:
• reception of a Channel Release with GPRS Resumption = NOK
• reception of a Channel Release without GPRS Resumption IE
• T3240 expiry
>Alcatel BSS does not support the suspend/resume procedure in case of inter-BSC reselection. In this case, MS shall
resume the GPRS service by sending a Routing Area Update Request message to the SGSN.
>When a mobile station operating in class B mode of operation suspends its GPRS activity during circuit-switched
activities, RRM forces the release of the on-going TBF(s). Once the TBF(s) has(ve) been released, the MS context is kept for
T_MS_Context_Lifetime seconds before being deleted.
>T_MS_Context_Lifetime is an MFS parameter. The default value is 120s and it cannot be set at OMC-R level.
© Alcatel 29
> CS paging during packet transfer (class B MS):
• if the MS does not listen to the PCH channel:
– CS paging messages are lost if the duration of the packet transfer is higher
than the duration of the repetition of CS paging messages
• if Gs interface is available:
– CS paging messages are sent via the PACCH channel
> PS paging during a GSM call (class B MS):

• the MS does not receive PS paging messages
>If CS paging repetitions are viewed as a GSM QoS problem, the situation shall be avoided.
>A missed PS Paging during a CS call is less of a problem as the traffic in GPRS is under the influence of the GSS
capacity to store the PDU originated from an external Packet Data Network. When the delay of transfer is not a
requirement for the service, there is no direct impact of a missed MS Paging.
© Alcatel 30
TBF Establishments
Data Transfer establishment
UL TBF establishment DL TBF establishment
MS in MM Ready state MS in MM Ready state MS in MM Standby state
PS Paging
MS in PIM MS in PTM MS in PIM MS in PTM
DL TBF UL TBF T3192

running running running
on CCCH on PCCCH on CCCH on PCCCH
DRX DRX
1 Phase 1 Phase
Non-DRX Non-DRX
2 Phase 2 Phase
> There are 5 types of UL TBF establishment:
1. 1-Phase access on CCCH when the MS is in Packet Idle Mode and no PCCCH is available in the cell and the
MS does not need more than 1 PDCH and wants to transfer blocks in RLC acknowledged mode.
2. 2-Phase access on CCCH: when the MS is in Packet Idle Mode and no PCCCH is available in the cell and the
MS needs more than 1 PDCH or wants to transfer blocks in RLC unacknowledged mode.
3. 1-Phase access on PCCCH: when the MS is in Packet Idle Mode and PCCCH is available in the cell and the MS
does not need more than 1 PDCH and wants to transfer blocks in RLC acknowledged mode.
4. 2-Phase access on PCCCH: when the MS is in Packet Idle Mode and PCCCH is available in the cell and the MS
needs more than 1 PDCH or wants to transfer blocks in RLC unacknowledged mode.
5. During a DL TBF: when the MS is in Packet Transfer Mode in the DL.
> There are 6 types of DL TBF establishment:
1. DRX mode on CCCH: when the MS is in Packet Idle Mode and no PCCCH is available in the cell and the MS is
listening to all PCH channels of its CS paging group.
2. Non-DRX mode on CCCH: when the MS is in Packet Idle Mode and no PCCCH is available in the cell and the
MS is listening to all AGCH channels.
3. DRX mode on PCCCH: when the MS is in Packet Idle Mode and a PCCCH is available in the cell and the MS is
listening to all PPCH channels of its PS paging group.
4. Non-DRX mode on PCCCH: when the MS is in Packet Idle Mode and a PCCCH is available in the cell and the
MS is listening to all PPCH channels of its PCCCH channel.
5. During a UL TBF: when the MS is in Packet Transfer Mode in the UL.
6. When T3192 is running: when a DL TBF has been released at the MS side and before the previously used radio
resources are released (at T3192 expiry).
© Alcatel 31
2 RADIO RESOURCE MANAGEMENT B9
© Alcatel 32
> Objective: to be able to describe the algorithms of Resource
Management and the related parameters
> Program:
2.1 (E)GPRS Channels
2.2 Autonomous Packet Resource Allocation NewB9
2.3 TBF Radio Resources Allocation and Re-allocation Modified B9
2.4 TBF Release Routine Modified B9
2.5 Exercises
© Alcatel 33
2 RADIO RESOURCE MANAGEMENT
© Alcatel 34
Overview
physical channel
PDCH
control channel
logical channel traffic channel
signaling associated control channel
logical channel category
Master PDCH Slave PDCH
Primary MPDCH Secondary MPDCH
PBCCH PCCCH PTCH PTCCH
PPCH PAGCH PRACH PDTCH PACCH
© Alcatel 35
GPRS Physical Channel, PDCH (1/2)
> Packet Data Channel (PDCH): a physical channel which carries GPRS
logical channels
1 TDMA frame = 4.615 ms
0 7 0 7 0 7
0 1 2 49 50 51
The 52-multiframe= 240 ms
0 4 8 12 13 17 21 25 26 30 34 38 39 43 47 51
Frame
B0 B1 B2 B3 B4 B5 X B6 B7 B8 B9 B10 B11 X Block
PTCCH
> PDCH frame:

• Made up of 52 TSs of the same rank belonging to 52 consecutive TDMA frames.
• The 52 TSs are divided into blocks of 4 consecutive TSs.
• 12 blocks are created and 4 single TSs:
– TS12 and TS38 for the Timing Advance,
– TS25 and TS51 are pseudo Idle TS for transmission purposes (synchronization with the occurrences of
SACCH on the GSM 26-multiframe).
> According to the PDCH design, a maximum of 8 PDCHs can be created with one TRX.
> A PDCH can be entirely allocated to a single user, which is close to the principle of circuit in GSM.
© Alcatel 36
GPRS Physical Channel, PDCH (2/2)
> 1 RLC PDU uses 1 PDCH block
• Except in MCS-7 to MCS-9 where 2 RLC PDUs use 1 PDCH block
> 2 kinds of physical channel PDCH
• master PDCH (MPDCH)
– A PDCH which carries the PCCCH and PBCCH logical channels
– For signaling purpose
• slave PDCH (SPDCH)
– A PDCH which carries PTCH logical channels
– For traffic purpose
> The MPDCH has been introduced with the B7 release.

>The use of GSM CCCH for the GPRS traffic offer can lead to QoS problem in GSM (PCH use more specifically).
© Alcatel 37
(E)GPRS Logical Channels (1/4)
> Different GPRS logical channels mapped on PDCH, which are shared
on a block basis:
• PTCH: PDTCH and PACCH
• Packet Timing advance Control Channel (PTCCH)
• Packet Broadcast Control Channel (PBCCH)
• Packet Common Control Channel (PCCCH)
© Alcatel 38
> Packet Traffic Channel (PTCH):
• used for user data and associated signaling transmission
• Packet Data Traffic Channel (PDTCH):

– unidirectional channel used for user data transmission
– mapped on one PDCH
– up to 8 PDTCHs may be allocated to an MS on different PDCHs with the
same frequency parameters
> Issue: the network shall control the multiplexing of several users on a unique UL PDCH avoiding collision occurrence. This
is achieved by the RLC/MAC functions and the use of USF, RRBP and TFI fields of the RLC/MAC header.
> The number of PDTCHs allocated to one MS belongs to:

• The MS capabilities (multislot class),
• The traffic in the BSS,
• Operator configuration of the BSS parameters.
> NB: max number of PDTCHs to one MS = 8 because the MS has to be allocated TSs on a unique TRX, and one TRX can
support 8 PDCHs max.
© Alcatel 39
> Packet Traffic Channel (PTCH):
• Packet Associated Control Channel (PACCH):
– A bidirectional channel used to transmit control and acknowledgement
messages
– Mapped on one PDCH:
– if a single PDTCH is allocated to an MS, the PACCH is allocated on
the PDCH carrying the PDTCH
– if multiple PDTCHs are allocated to an MS, the PACCH is allocated
on one of the PDCH carrying the PDTCHs (Alcatel BSS)
> Caution: PACCH blocks are used to carry the BSS signaling but not the GSS signaling.
> The scheduling of PACCH blocks in the UL and the DL is monitored by the MFS. The most frequent use of the PACCH
blocks is for “Packet Ack/Nack” messages.
> It can be used as well for CS Paging message when Master Channels are not available.
> It is necessary for the MS to update the PSI13 on a regular basis in order to achieve proper RLSs and Power Control
mechanisms. The PSI13 content can be sent to the MS in Packet Transfer Mode via a PACCH.
© Alcatel 40
t
B urs
e ss
A cc
e
s ag
M es
TA
MFS
> Packet Timing advance Control Channel (PTCCH):

• bidirectional channel (DL: TA messages; UL: Access Burst for TA calculation) used
by the continuous timing advance mechanism
• the PTCCH of one MS is carried by the PDCH carrying the PACCH
• Timing Advance Index (TAI), used for the scheduling of the AB, is part of the radio
resources allocated to an MS.
– The TAI is a PDCH parameter
– The TAI takes 16 values
>The Access Burst in the UL and the Timing Advance Messages in the DL are scheduled in time manner on TS12 and
TS38.
>The TAI is part of the GPRS radio resources allocated by the MFS to the MS. Each mobile needs to have a TAI.
>The TAI range value is a limitation to MS multiplexing on a same TS, as both MS in the UL transfer and MS in the DL
transfer send their AB in the UL and receive their TA value in the DL.
>16 values for TAI means that each MS sends an AB every 1.96 s, when the content of the TA Messages is updated every
480 ms (every 4 occurrences of TAM).
A.B. scheduled for On PTCCH TS

TAI value TA Message
MF-51 number
0 N 12 TAM 0
1 N 38 TAM 0 4 repetitions of the

16 TA values (4 TA
2 N+1 12 TAM 0 values updated)
3 N+1 38 TAM 0
4 N+2 12 TAM 1 Idem
………………
15 N+7 38 TAM 4 idem
© Alcatel 41
Multiplexing of (E)GPRS Logical Channels (1/3)
PDCH 1
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 2
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 3
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
TBF with TFI = 5 TBF with TFI = 17 TBF with TFI = 24
> Temporary Block Flow (TBF): a unidirectional flow of data between the MS
and the MFS for the transfer of one or more LLC PDUs (refer to GSM 04.60)
> Several TBFs can be transmitted on one PDCH (TFI 5)
> One TBF can be served on several PDCHs (TFI 17 & 24)
> A TBF is identified by a Temporary Flow Identity (TFI)
>Temporary Flow Identity (TFI):

• Each TBF is assigned a TFI by the MFS.
>Important:
• It is possible to establish 32 TBFs per TRX.
> TBF: a group of blocks dynamically allocated to one MS for one transfer of RLC blocks in one direction inside one
cell.
> A Temporary Block Flow is a temporary, unidirectional physical connection across the Um interface, between one
mobile and the BSS. The TBF is established when data units are to be transmitted across the Um interface and is
released as soon as the transmission is completed.
>There is still a 3 RTS shift between Rx and Tx, on the TDMA frame.
© Alcatel 42
> Downlink PDTCH and PACCH blocks multiplexing
PDTCH PDTCH PACCH
USF = 5
TFI24
TFI17
TFI24
DL PDCH N°2
+1
PDTCH
TFIUL
/
PACCH
UL PDCH N°2
> Uplink PDTCH and PACCH for a UL TBF multiplexing
> Downlink PDTCH and PACCH blocks multiplexing:

• The multiplexing of the different MSs is performed thanks to the TFI which is present in the RLC block header.
• An MS decodes all the blocks of all its allocated PDCHs and keeps the blocks carrying its TFI in the RLC header.
> Uplink PDTCH and PACCH for a UL TBF:

• At UL TBF establishment, an MS receives a USF (Uplink State Flag, 8 values, MAC header) per allocated PDCH.
• If the MS receives its USF on the downlink block n of PDCH i, it can transmit in uplink using the block n+1 of
PDCH i.
> NB: the values of the USF are entirely dedicated to PDTCH and PACCH transfers. See further (MPDCH and RRBP)
> The TFI is used in the UL as well: each mobile shall put its TFI in the UL header of the UL blocks during a UL TBF, as
well as in the RLC header of the UL PACCH blocks of a DL TBF.
> So we can say that the de-multiplexing of the blocks is achieved by the use of a TFI.
© Alcatel 43
> Uplink PACCH for a DL TBF scheduling:
USF = 000
S/P≠false
PDTCH PDTCH PACCH
USF = 5
TFIXX
TFI24
TFI17 DL PDCH N°2

RRBP = +3
Ø
PACCH
PDTCH
Packet DL
TFI24
/
TFIUL
PACCH Ack/NAck
message
UL PDCH N°2
Exercise
> RRBP: Relative Radio Block Period
> Allocation of a PACCH block for the sending of acknowledgements in the UL of blocks received in the DL:
• The MS has no USF because it is involved in a DL TBF
• Use of the RRBP field transmitted in the downlink (MAC header) in association with the TFI of the DL TBF in the
RLC header.
• At the exact occurrence of the RRBP, a special USF value is used for the UL TBF taking place on the same PDCH:
USF=no emission.
> It is a semi-boolean parameter. The RRBP field of an RLC/LAC block is checked each time by the MS whose TFI is
written in the RLC header.
– When S/P is false, no UL PACCH is scheduled.
– When the RRBP field is valid, the value gives the number of blocks to wait before sending its PACCH
block in the UL.
> S/P is false means the MS has to send an acknowledgement message to the MFS.
© Alcatel 44
MPDCH (1/5)
> Logical channels dynamically multiplexed:
• PBCCH, PCCCH
> Identified by the PCCCH group (used for paging purposes)
> Primary Master Channel
• PBCCH carrier, indicated in SI13
• Static allocation
> Secondary Master Channels: additional MPDCH
• PRACH, PPCH and PAGCH carrier
> NB_TS_MPDCH = Number of TSs reserved for MPDCHs (Primary +
Secondary)
> In order to configure the number of master channels (primary and secondary) in a cell, the operator sets the value of
NB_TS_MPDCH (Range 0 to 4) from the OMC-R.
> Primary MPDCH allocation:

• A PBCCH is scheduled by the MFS and SI13 is updated by the BSC indicating the PBCCH.
• The MS reads SI13 once every 30s (or on PSI 13 for MS in packet transfer mode). Once the MS is aware of the
establishment, it reads the complete PSI cycle (read PSI1 within 10s for MS in packet transfer mode).
• During this 30s period of time (to be achieved for a complete MPDCH alloc):
– Paging messages are mapped on both PCH and PPCH.
– UL TBF establishments are answered either by a AGCH or by an PAGCH (whether the request is sent on
RACH or on PRACH).
> Secondary MPDCH activation:

• Presence indicated on PS12. The MS must read the new PSI1 and the new PSI2.
• It can take the MS 30 s (establishment duration).
• A Paging reorganization procedure is triggered {PAGE MODE IE = (1,0)}. The MS recalculates its Packet Paging
Group.
© Alcatel 45
MPDCH (2/5)
> Master channels configuration
• On the BCCH TRX
• Starting from the left
• BCCH and SDCCH are not overwritten
> Example
• NB_TS_MPDCH = 4
0 1 2 3 4 5 6 7
BCCH SDCCH
: MPDCH
> In order to configure the number of master channels (primary and secondary) in a cell, the operator sets the value of
NB_TS_MPDCH (Range 0 to 4) from the OMC-R.
> The NB_TS_MPDCH radio time slots are then configured automatically on the TRX carrying the BCCH, starting from the
left. The BCCH and SDCCH time slots are not overwritten.
© Alcatel 46
MPDCH (3/5)
> MPDCH configuration
• Downlink multi-frame
– primary MPDCH: the first BS_PBCCH_BLKS blocks of the ordered list (B0,
B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11) are reserved for PBCCH
– Secondary MPDCH: the first BS_PBCCH_BLKS blocks of the ordered list
above are reserved for PAGCH
– BS_PAG_BLKS_RES: number of blocks reserved for PAGCH, after
reservation of PBCCH blocks
– remaining blocks are used for PPCH, PAGCH
>Switching from the PPCH to the PBCCH is always possible for an MS in Packet Idle Mode, since I frames (TS12 and
TS38 of the 52-multiframe) and X frames (TS25 and TS51 of the 52-multiframe) always precede a PBCCH block.
>Note: PDTCH and PACCH are not multiplexed on MPDCHs (to avoid problems of inconsistent assignments).
© Alcatel 47
MPDCH (4/5)
> Example of DL Primary Master Channel:
• BS_PBCCH_BLKS=2
• BS_PAG_BLKS_RES=6
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PBCCH blocks
PAGCH blocks
PPCH, PAGCH blocks
> CAUTION: animated slide.
> For PAGCH, the simple rule is that all blocks not reserved for PBCCH usage may be used for PAGCH purposes:
• Up to (12 - BS_PBCCH_BLKS) radio blocks on the Primary Master Channel.
• Up to 12 radio blocks on any Secondary Master Channel.
> Different rules apply to the PPCH:
• First, for proper operation of the Discontinuous Reception (DRX) mechanism, all Master Channels in the cell have the
same number of radio blocks allowed for the PPCH.
• Second, for configuration flexibility, the operator may decide to limit the PPCH to a subset of allowed blocks. As a
matter of fact, the GPRS standards rather define the number of blocks per multiframe where neither the PPCH nor the
PBCCH can be mapped.
•This is the BS_PAG_BLKS_RES parameter, under operator’s control from the OMC-R.
– It is defined per cell.
– Its value ranges from 0 to 11 blocks.
• As a result, the number of radio blocks allowed for the PPCH is:
– Up to (12 - BS_PBCCH_BLKS - BS_PAG_BLKS_RES) radio blocks on all Master Channels.
© Alcatel 48
MPDCH (5/5)
> MPDCH configuration
• Uplink multi-frame
– PRACHs occur on any PDCH carrying MPDCH
– PRACH blocks are statically allocated on the BS_PRACH_BLKS first blocks
of the ordered list:
B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11
– blocks are marked by USF=free
Exercise
> In the uplink path of each Master Channel, radio blocks have to be reserved for a PRACH, the remaining blocks being
available for signaling purposes.
> This is done through the BS_PRACH_BLKS parameter ranging from 1 up to 8 blocks per multiframe.
> There is the same amount of reserved PRACH blocks on all Master Channels present in the cell.
>There is no PRACH dynamic load control and the Packet Queuing Notification message is not handled (no UL PRACH
queuing).
> The USF is coded over 3 bits, so 8 values are available to traffic minus 1 (free) for PRACH blocks minus 1 (no emission)
for UL Ack of DL TBF with the RRBP mechanism. So, 6 USF values are available for PDTCH traffic on one PDCH.
© Alcatel 49
2.2 Autonomous Packet Resource Allocation
© Alcatel 50
Foreword: SPDCH Group: Definition (1/2)
> SPDCH group = time slots usable for PS traffic
• Only 1 SPDCH group per TRX
• contains TS
– belonging to the same TRX
– having the same frequency configuration
– without hole
• MPDCHs are not part of the SPDCH group
> Up to 16 PDCH groups per cell
> A TRX is PS/CS capable only if TRX_PREF_MARK = 0
• TRX_PREF_MARK <> 0 then the TRX is only CS capable
> Any TRX should possibly support one SPDCH group except for one case:
• Concentric cell or multi-band cell design, an SPDCH group can NOT belong to the inner zone.
> An SPDCH group can be supported by both hopping and non-hopping TRXs.
> Only one Mobile Allocation (MA) is supported in a cell.
© Alcatel 51
Foreword: SPDCH Group: Definition (2/2)
> Example: BBH is used, NB_TS_MPDCH=0
TRX_PREF_MARK
0 1 2 3 4 5 6 7
0 TRX1 BCCH SDCCH
SPDCH group1
1 TRX2 SDCCH
SPDCH group2 SPDCH group2 Null
0 TRX3
SPDCH group3
1 TRX4
SPDCH group4 SPDCH group4 Null
> CAUTION: animated slide.
© Alcatel 52
Foreword: Impact of the Output Power (1/3)
Q
> GMSK dB
• constant envelope PN
(amplitude) modulation
• one bit per modulated I
symbol over the radio
path (147 bits)
542.8 µs t
> 8-PSK
• Envelope modulation not
constant dB 0,1,0
• 3 bits per modulated 0 0,0,0 0,1,1
symbol over the radio PN

0,0,1 1,1,1
path -20
(147 bits)
1,0,1 1,1,0
1,0,0
> GMSK = the Gaussian Minimum Shift Keying belongs to a subset of phase modulations
> 8-PSK = 8-state Phase Shift Keying

• 8-PSK is not a constant envelope modulation. Part of the information is conveyed by the amplitude of the carrier
which varies over time.
• An 8-PSK signal carries three bits per modulated symbol over the radio path, which allows to triple the data
transmission rates.
GMSK 8-PSK
Modulation type Frequency modulation Phase modulation
Channel spacing 200 KHz 200 KHz
Gross bit rate per

270 Kbit/s 810 Kbit/s
carrier
Carrier envelope constant Amplitude varies
Packet radio service GPRS / EGPRS EGPRS
> Modulation gross bit rate

• The normal burst is divided into 156.25 symbol periods. A normal burst has a duration of 3/5.2 seconds (577
µs). (3GPP TS 05.02).
• For GMSK modulation, a symbol is equivalent to a bit (3GPP TS 05.04).
– A GMSK burst is composed of 156.25 bits (6 tail bits + 26 training sequence bits + 116 encrypted
bits + 8.25 guard period (bits)).
– Modulation gross bit rate = (156.25 bits) / (3/5.2 seconds) = 270 Kbit/s
• For 8-PSK modulation, one symbol corresponds to three bits (3GPP TS 05.04).
– An 8-PSK burst is composed of 156.25 x 3 = 468.75 bits (18 tail bits + 78 training sequence bits +
348 encrypted bits + 24.75 guard period (bits)).
– Modulation gross bit rate = (468.75 bits) / (3/5.2 seconds) = 810 Kbit/s
© Alcatel 53
> G4 TRE characteristics
TRAG TRAGE TAGH TAGHE TRAD TRADE TADH TADHE
EDGE+ EDGE+ EDGE+ EDGE+
Type Medium power High power Medium power High power
Frequency
900 1800
band
GMSK 45 W 60 W 35 W 60 W
output
power 46,53 dBm 47,78 dBm 45,44 dBm 47,78 dBm
8-PSK 25 W
15 W 30 W 25 W 30 W 12 W 30 W 30 W
output 43,98
power 41,76 dBm 44,77 dBm 43,98 dBm 44,77 dBm 40,79 dBm 44,77 dBm 44,77 dBm
dBm
> G3 TREs are not able to handle the 8-PSK modulation. Only G4 TREs (also called TRA) are EDGE capable.
> The TRA sensitivity is as follows:

• GMSK: - 111 dBm.
• 8-PSK: - 108 dBm for MCS5, - 99 dBm for MCS9.
© Alcatel 54
> The GMSK output power is:
• The minimum value among the maximum TRE output power in:
– One cell
– One frequency band
• The maximum output power in the cell
> The 8-PSK output power
• Is given for one TRE by the modulation_delta_power
– = [Maximum output power in the cell] – [8-PSK TRE output power]
• And a possible attenuation, in order not to exceed the GMSK power in the cell
(case of BS_TXPWR_MAX <> 0 dB)
> 8-PSK High Power Capability
• G4 HP TRE if the modulation_delta_power < 3dB
• G4 MP TRE if the modulation_delta_power > 3dB
• The 8-PSK High Power Capability is used in the TRX ranking process
> CAUTION: do not confuse “MP” and “HP” given as a TRE hardware characteristic and “MP” and “HP” defined by
the 8-PSK High Power Capability.
• The first ones represent the maximum power a TRE can transmit (in GMSK or 8-PSK).
• The second ones represent the capability of a TRE to emit with an 8-PSK power close to the maximum GMSK
power in a given cell.
© Alcatel 55
2.2 Autonomous Packet Resource Allocation B9
Foreword: TRX Ranking (1/2)
> Input / Output
Inputs Outputs
8-PSK High Power Capability (G4 HP, G4 MP, or G3)

TRE
Characteristics DR TRE capability (FR or DR)
TRX_PREF_MARK TRX Ranking TRX Ranking Table
PS_PREF_BCCH_TRX function TRX Rank
TRX or cell E-GSM, P-GSM, GSM850 or DCS TRX Modified B9

Characteristics
Radio cell configuration (nb of SPDCHs per TRX)
TRX id (0,1,…,14, or 15)
> Once the TRXs are mapped to the TREs (after a possible TRX adjustment), the TRX Ranking function is computed. This
function consists in ranking the TRXs in order to ensure that the CS and PS allocations will be consistent.
> HP means there is less than 3 dB of difference between the maximum power of the GMSK TRXs and the maximum power
of the 8-PSK TRXs in the cell. On the contrary, MP means the difference is more than 3 dB.
© Alcatel 56
Foreword: TRX Ranking (2/2)
> Ranking criteria (from the highest preference for PS allocation to the
lowest)
• Concerns only PS capable TRX: TRX_PREF_MARK = 0
• if PS_PREF_BCCH_TRX = 1 then
– The BCCH TRX has the highest preference
– Else, the rank of the BCCH TRX is determined by the remaining criteria
• HW TRE capability: G4 HP > G4 MP > G3
• DR TRE capability: FR > DR
• E-GSM TRX preference: E-GSM TRXs > P-GSM/GSM850/DCS TRXs Modified B9
• TRX(s) having the maximum SPDCH group size

• TRX having the lowest TRX index
Exercise
> The TRX with the lowest Rank value has the highest preference for PS allocations.
> Step 01: Separation of non-PS and PS capable TRXs

• The first step consists in removing the non-PS capable TRXs, i.e., the TRXs having a non-null TRX_PREF_MARK. Only
the PS capable TRXs are then kept for the TRX ranking.
> Step 02: Ranking of the PS capable TRXs
• First criterion: PS allocations preferred on the BCCH TRX
– If the BCCH TRX is a PS capable TRX and the parameter PS_PREF_BCCH_TRX is set to ‘1’, then the BCCH
TRX has the lowest rank (i.e., Rank 1) in the TRX Ranking Table. This means that this TRX is selected first for
PS allocations.
– If the parameter PS_PREF_BCCH_TRX is set to ‘0’, then the rank of the BCCH TRX is determined by the
remaining criteria.
• Second criterion: HW TRE capability
– The TRXs mapped on a G4HP TRE are ranked first, then they are followed by the TRXs mapped on a G4MP
TRE, finally by the TRXs mapped on a G3 TRE.
• Third criterion: DR TRE capability
– Among the TRXs having the same HW TRE capability, select first the FR TRX, then the DR TRX.
• Fourth criterion:E-GSM TRX preference
– Among the TRXs having the same HW TRE capability and the same DR TRE capability, select first the E-
GSM TRXs, then the P-GSM/GSM850/DCS TRXs.
• Fifth criterion: Maximum SPDCH group criterion
– Among the TRX having the same HW TRE capability, the same DR TRE capability and the same E-GSM TRX
preference, rank first the TRX having the maximum number of consecutive SPDCHs per TRX. Note that this is
a static information given by the O&M configuration of the TRX.
• Sixth criterion: TRX identity
– Among the remaining TRXs, select first the TRX having the lowest TRX id. This criterion aims at having a
deterministic criterion at the end of the TRX Ranking function.
> Note:
• The TRX ranking function does not take into account the current traffic load.
© Alcatel 57
Principle (1/2)
> The BSC indicates regularly to the MFS in the RR Allocation
Indication message:
• The number of TSs allocated for PS traffic
– MAX_SPDCH_LIMIT
• The location of those SPDCHs on the PS capable TRXs
– Using the SPDCHs_Allocation bitmap
> The MFS sends to the BSC the RR Usage Indication message to:
• Confirm the allocated / de-allocated TSs to the BSC (Acknowledgement)
• Indicate the PS usage state of those TSs
• This message is sent:
– Periodically
– After the reception of the RR allocation Indication from the BSC
> Contrary to the previous BSS releases, the MFS no longer needs to request additional SPDCH to the BSC, as
all the usable PS capable radio time slots are explicitly allocated to the MFS through the “RR Allocation Indication”
message.
> Nevertheless, a coordination is performed between the MFS and the BSC to allocate radio time slots for the PS traffic.
>The protocol between the MFS and the BSC to handle radio resources uses two BSCGP messages which are new in B9
release:
• They replace the Radio Allocation Request/Confirm and Radio Deallocation Command/Complete used in B8
release by the MFS and the BSC.
• Moreover the Load Indication message used in B8 release is no more used in B9 release.
© Alcatel 58
Principle (2/2)
> MFS / BSC Synchronization
BSC MFS
RR Allocation Indication
RR Usage Indication
RR_ALLOC_PERIOD (2)
x TCH_INFO_PERIOD (5s)
TCH_INFO_PERIOD RR Usage Indication
RR Allocation Indication TCH_INFO_PERIOD
RR Usage Indication
>The RR Allocation Indication message:

• Is sent from the BSC to the MFS to provide the MFS with the location of the allocated SPDCH.
• Is transmitted periodically every RR_ALLOC_PERIOD * TCH_INFO_PERIOD seconds = 2 * 5 seconds.
• Contains the SPDCH_Allocation bitmap which indicates whether available time slots in the cell are allocated
or not to the MFS.
> The RR Usage Indication message:

• Is sent from the MFS to the BSC periodically (every TCH_INFO_PERIOD seconds) or in response to a “Radio
Resource Allocation Indication” message.
• Contains 3 bitmaps:
– The SPDCHs_Confirmation bitmap. The role of this bitmap is to indicate the status of each SPDCH
from the point of view of the MFS and also to acknowledge the allocation of SPDCH newly granted by
the BSC and the deallocation of SPDCH given back to the BSC. The value of each bit in the
SPDCHs_Confirmation bitmap has the following meaning:
– 1: this SPDCH is allocated to the MFS (SPDCH allocation state is “allocated” or “de-
allocating”).
– 0: this SPDCH is not allocated to the MFS (SPDCH allocation state is “not allocated”).
– The SPDCHs_Usage bitmap:
– 1: this SPDCH is allocated to the MFS and “used” (one TBF, RT PFC or one UL block has
some radio resources allocated on it, and/or if its basic Abis nibble is being used by a GCH
channel or is still switched to an Ater nibble in the BSC).
– 0: this SPDCH is either allocated to the MFS and “unused” (*), or is not allocated to the MFS.
– The SPDCHs_RadioUsage bitmap:
– 1: this SPDCH is allocated to the MFS and there is at least one TBF allocated on it.
– 0: this SPDCH is either allocated to the MFS and there is no TBF allocated on it, or is not
allocated to the MFS.
> The bitmaps are present for all the available PS capable TRXs of a cell, even if no SPDCH is allocated to the MFS for
a given TRX.
© Alcatel 59
Functional Entities
LOAD_EV_PERIOD_GPRS
NB_USED_CS_TS
NB_USED_PS_TS
Load Evaluation
MAX_PDCH_HIGH_LOAD
MAX_PDCH AV_USED_CS_TS
NB_TS_DEFINED MIN_PDCH AV_USED_PS_TS
NB_TS_SPDCH NB_TS_MPDCH AV_UNUSED_TS
MIN_SPDCH
MAX_SPDCH
NB_TS Thresholds Computation of MAX_SPDCH_LIMIT
computation MAX_SPDCH_HIGH_LOAD MAX_SPDCH_LIMIT
MARGIN_PRIORITY_CS
CS/PS Margin
MARGIN_PRIORITY_PS
HIGH_TRAFFIC_LOAD_GPRS
THR_MARGIN_PRIORITY_PS
© Alcatel 60
Thresholds Computation (1/2)
LOAD_EV_PERIOD_GPRS
NB_USED_CS_TS
NB_USED_PS_TS
Load Evaluation
MAX_PDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
MARGIN_PRIORITY_CS
CS/PS Margin
MARGIN_PRIORITY_PS
© Alcatel 61
Thresholds Computation (2/2)
> MAX_SPDCH = Roundup [Min(MAX_PDCH – NB_TS_MPDCH ;
NB_TS_SPDCH) x Availability_TS_Ratio]
> MAX_SPDCH_HIGH_LOAD = Roundup
[Min(MAX_PDCH_HIGH_LOAD – NB_TS_MPDCH ; NB_TS_SPDCH) x
Availability_TS_Ratio]
> MIN_SPDCH = Roundup [(MIN_PDCH – NB_TS_MPDCH) x
Availability_TS_Ratio]
> Where Availability_TS_Ratio(k) = NB_TS(k) / NB_TS_DEFINED

• evaluated at instant tk, every RR_ALLOC_PERIOD x TCH_INFO_PERIOD
(10s)
• NB_TS(k) takes into account the possible TRX failures
> NB_TS_SPDCH is the total number of TCH/SPDCH time slots in the cell, without taking into account the possible
TRX failure. This parameter can be retrieved by the BSC from the O&M configuration of the cell.
> NB_TS_DEFINED is the total number of pure TCH, TCH/SDCCH, or TCH/SPDCH time slots, without taking into
account the possible TRX failure. This parameter can be retrieved by the BSC from the O&M configuration of the cell.
> NB_TS is the total number of pure TCH, TCH/SDCCH, or TCH/SPDCH time slots (evaluated every 10s), taking into
account possible TRX failures.
> A TCH/SPDCH is a TS which can be allocated for either CS traffic or PS traffic (i.e. mapped on a PS capable TRX
and inside the SPDCH group).
> A pure TCH is a TS which can be allocated only for CS traffic (i.e. outside the SPDCH group).
> A TCH/SDCCH is a dynamic SDCCH (can be allocated as either a TCH or an SDCCH).
© Alcatel 62
Load Evaluation (1/3)
LOAD_EV_PERIOD_GPRS
NB_USED_CS_TS
NB_USED_PS_TS
Load Evaluation
MAX_PDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
MARGIN_PRIORITY_CS
CS/PS Margin
MARGIN_PRIORITY_PS
© Alcatel 63
> The BSC computes 3 averaged values
• AV_USED_CS_TS(k), AV_USED_PS_TS(k) and AV_UNUSED_TS(k)
• For each cell
• At sampling instant tk, every RR_ALLOC_PERIOD x TCH_INFO_PERIOD
(10s)
• Using a sliding window, LOAD_EV_PERIOD_GPRS
LOAD_EV_PE RIOD_GPRS -1
1
> AV_USED_CS_TS(k) =
LOAD_EV_PERIOD_GPRS
∑
i= 0
NB_USED_CS_TS (k - i)
> Same formula for AV_USED_PS_TS(k) and AV_UNUSED_TS(k) based

on NB_USED_PS_TS(k) and NB_UNUSED_TS(k)
• NB_UNUSED_TS(k) = NB_TS(k) – NB_USED_CS_TS(k) –
MAX[MIN_SPDCH(k) ; NB_USED_PS_TS(k)]
> NB_USED_CS_TS(k): number of available time slots handled by the BSC and carrying CS traffic in the cell at
sampling instant tk. A time slot is taken into account in the evaluation of NB_USED_CS_TS(k) if:
• SPDCH allocation state = not allocated,
• Occupancy state = used.
> NB_USED_PS_TS(k): number of available time slots used for PS traffic in the cell at sampling instant tk. A time slot
is taken into account in the evaluation of NB_USED_PS_TS(k) if:
• SPDCH allocation state = allocated or de-allocating,
• Occupancy state = used.
> These variables are updated every TCH_INFO_PERIOD (5s).
© Alcatel 64
k-2 k-1 k k+1 k+2
TCH_INFO_PERIOD = 5s
NB_USED_CS_TS(k)
NB_USED_PS_TS(k)
NB_USED_TS(k)
NB_UNUSED_TS(k) RR_ALLOC_PERIOD * TCH_INFO_PERIOD
AV_USED_CS_TS(k) AV_USED_CS_TS(k+2)
LOAD_EV_PERIOD_GPRS = 3
AV_USED_PS_TS(k) AV_USED_PS_TS(k+2)
AV_UNUSED_TS(k) AV_UNUSED_TS(k+2)
© Alcatel 65
CS/PS Margins (1/2)
LOAD_EV_PERIOD_GPRS
NB_USED_CS_TS
NB_USED_PS_TS
Load Evaluation
MAX_PDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
MARGIN_PRIORITY_CS
CS/PS Margin
MARGIN_PRIORITY_PS
© Alcatel 66
CS/PS Margins (2/2)
> MARGIN_CS = MAX(MARGIN_PRIORITY_CS(k), AV_UNUSED_TS(k) /
2)
• Where:
– MARGIN_PRIORITY_CS = THR_MARGIN_PRIO_CS x (NB_TS –
MAX_SPDCH_HIGH_LOAD) / 100
– THR_MARGIN_PRIO_CS = 100% - HIGH_TRAFFIC_LOAD_GPRS
> MARGIN_PRIORITY_PS = THR_MARGIN_PRIO_PS x
MAX_SPDCH_HIGH_LOAD / 100
• Where:
– THR_MARGIN_PRIO_PS = 10%
> These 2 margins are used to ensure that a certain number of TSs is
kept available for the arrival of new calls / transfers between 2 RR
Allocation Indication messages
© Alcatel 67
MAX_SPDCH_LIMIT Computation
LOAD_EV_PERIOD_GPRS
NB_USED_CS_TS
NB_USED_PS_TS
Load Evaluation
MAX_PDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
MARGIN_PRIORITY_CS
CS/PS Margin
MARGIN_PRIORITY_PS
© Alcatel 68
MAX_SPDCH_LIMIT Computation: Functional Entities
MARGIN_PRIORITY_CS
AV_USED_CS_TS Computation of
AV_UNUSED_TS MAX_SPDCH_LIMIT_CS MAX_SPDCH
MAX_SPDCH_HIGH_LOAD
MAX_SPDCH_LIMIT_CS
Computation of MAX_SPDCH_LIMIT
MAX_SPDCH_LIMIT
MAX_SPDCH_LIMIT_PS
Computation of
AV_USED_PS_TS
MAX_SPDCH_LIMIT_PS
MIN_SPDCH
MARGIN_PRIORITY_PS
> The basic idea for the evaluation of MAX_SPDCH_LIMIT is to start from the number of unused time slots and to share
them between CS and PS traffic, taking into account 2 margins (one for CS, one for PS traffic) defined to guarantee a
certain number of time slots available to serve incoming calls/transfers.
© Alcatel 69
MAX_SPDCH_LIMIT Computation: Formulas (1/2)
> MAX_SPDCH_LIMIT is equal to:
• MAX_SPDCH_LIMIT_CS under normal load
OR
• MAX_SPDCH_LIMIT_PS under high CS load
> MAX_SPDCH_LIMIT_CS
• Represents the maximum number of SPDCHs that can be allocated to the
MFS ensuring the CS allocation is not degraded
• = RoundDown[NB_TS – AV_USED_CS_TS – MARGIN_CS]
> MAX_SPDCH_LIMIT_PS
• Represents the minimum number of SPDCHs that can be allocated to the
MFS ensuring the PS allocation is not degraded
• = RoundUp[AV_USED_PS_TS + MARGIN_PRIORITY_PS]
© Alcatel 70
MAX_SPDCH_LIMIT Computation: Formulas (2/2)
> Choice between MAX_SPDCH_LIMIT_CS and MAX_SPDCH_LIMIT_PS
• If MAX_SPDCH_LIMIT_CS >= MAX_SPDCH_HIGH_LOAD then
– MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_CS ; MAX_SPDCH]
• Else
– If MAX_SPDCH_LIMIT_CS > MAX_SPDCH_LIMIT_PS then
– MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_CS ;
MAX_SPDCH]
– Else
– MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_PS ;
MAX_SPDCH_HIGH_LOAD]
> MAX_SPDCH_LIMIT is always between MIN_SPDCH and MAX_SPDCH
© Alcatel 71
MAX_SPDCH_LIMIT Computation: Example
NB_TS=14 MAX_SPDCH=14 MIN_SPDCH=1
MAX_SPDCH_HIGH_LOAD=2 HIGH_TRAFFIC_LOAD_GPRS=80%
14
CS
12 Traffic
10
CS
8 Traffic
6
CS PS
Traffic Traffic
4
PS
2
Traffic PS
Traffic PS Traffic
Normal High CS load High CS load High PS
load with PS traffic Without PS traffic load
Exercise1
> Case “Normal Load”: The capacity is shared between CS and PS taking into account the associated margins.
> Case “High CS load”: When the CS traffic increases, MAX_SPDCH_LIMIT is reduced down to
MAX_SPDCH_HIGH_LOAD to ensure a minimum capacity for the PS traffic.
> Case “Very high CS load”: When the CS traffic increases and in the same time there is no PS traffic,
MAX_SPDCH_LIMIT is decreased down to MIN_SPDCH to ensure the maximum capacity for the CS.
> Case “High PS load”: MAX_SPDCH is not the only criterion taken into account to limit the PS capacity, the
CS_MARGIN is applied too.
© Alcatel 72
PS Zones: Definition
> MAX_SPDCH=12, MIN_SPDCH=1, MAX_SPDCH_LOAD=8
> MAX_SPDCH_LIMIT = 7
PS PS PS PS CS CS BCCH SDCCH CS
TRX3 TRX1
Non pre-emptable zone
MAX_SPDCH_HIGH_LOAD zone
MAX_SPDCH_LIMIT zone
PS traffic zone
> MAX_SPDCH_HIGH_LOAD zone: this zone corresponds to the MAX_SPDCH_HIGH_LOAD consecutive PS capable
time slots that are preferred for PS allocation. In this zone, allocated TBFs cannot be preempted. If the value of
MAX_SPDCH_HIGH_LOAD is not modified, this zone remains unchanged.
> Non pre-emptable PS zone: this zone is always inside the MAX_SPDCH_HIGH_LOAD zone. In this latter zone, we
search for the rightest time slot allocated to the MFS and used. Then, all time slots situated at its left define this non pre-
emptable PS zone.
> MAX_SPDCH_LIMIT zone: this zone corresponds to the MAX_SPDCH_LIMIT consecutive PS capable time slots that
are preferred for PS allocation.
> PS traffic zone: this zone corresponds to the larger zone between the non pre-emptable PS zone and the
MAX_SPDCH_LIMIT zone.
© Alcatel 73
PS Zones: Impact on CS Call
PS PS PS PS CS PS PS CS BCCH SDCCH CS
TRX3 TRX1
HO cause 30
MAX_SPDCH_HIGH_LOAD zone
PS traffic zone
> If EN_RETURN_CS_ZONE_HO = enabled

> AND a CS call is inside both
• The Non pre-emptable zone and
• The MAX_SPDCH_LIMIT_ZONE then
> An intra cell HO cause 30 is triggered
> Caution: animated slide.
© Alcatel 74
SPDCH Allocation: Conclusion
> Example of an SPDCHs_Allocation bitmap
• MAX_SPDCH_LIMIT = 7
PS PS PS PS CS CS BCCH SDCCH CS
TRX3 TRX1
1 1 1 1 1 1 0 0 0 0 1 0 0 0 0 0
> Caution: animated slide.

> The algorithm of selection of MAX_SPDCH_LIMIT TCH/SPDCH time slots to allocate to the MFS and of building of the
SPDCHs_Allocation bitmap is performed as follows:
•Initialization:
–Definition of the non pre-emptable PS zone and of the MAX_SPDCH_LIMIT zone,
–nb_selected = 0,
–Begin with the time slot having the lowest index and situated on the TRX having the lowest rank in the
TRX Ranking Table.
•Process on each TCH/SPDCH time slots available in the cell:
–First, begins with the non pre-emptable PS zone: analysis of all time slots within this zone. At the end of
this zone:
–If nb_selected >= MAX_SPDCH_LIMIT: stop the process and the remaining time slots are
allocated to the BSC,
–Otherwise: continue the process in the MAX_SPDCH_LIMIT zone. At the end of this zone:
»If nb_selected = MAX_SPDCH_LIMIT: stop the process and the remaining time slots
are allocated to the BSC,
»Otherwise: continue the process outside the MAX_SPDCH_LIMIT zone. When
nb_selected = MAX_SPDCH_LIMIT: stop the process and the remaining time slots are
allocated to the BSC.
© Alcatel 75
BSS Resources reservation
> Allocated PDCH: MIN_PDCH = 1
Air
PDCH
BTS BSC MFS

> Established TRX: MIN_PDCH = 1 and EN_FAST_INITIAL_GPRS_ACCESS
= enabled
Air TRX Abis AterMux
PDCH M-EGCH M-EGCH
BTS BSC MFS

> The 3 following states are handled, for a PDCH:

• allocated TS: timeslots allocated to the MFS.
• not-allocated TS: timeslots allocated to the BSC
• de-allocating TS: transitory state, TS allocated to the MFS but must be given back to the BSC
© Alcatel 76
Fast Initial PS Access
> If EN_FAST_INITIAL_GPRS_ACCESS = enabled
• 1 PDCH is always available for (E)GPRS traffic
• This PDCH is located
– on an established TRX
– with at least N_GCH_FAST_PS_ACCESS (=1) GCHs allocated on this TRX
> Mandatory rule:

– MIN_PDCH ≥ NB_TS_MPDCH + 1
– Since MIN_PDCH is the number of master and slave PDCHs that are
permanently allocated
> Otherwise, the rule is MIN_PDCH ≥ NB_TS_MPDCH
> The “first TRX of the cell having some allocated RTSs” is identified thanks to the latest RR Allocation Indication message
received from the BSC. When considering the sorted TRX list in the latest RR Allocation Indication message, it is the TRX
supporting the first RTS allocated to the MFS, according to the SPDCHs_Allocation bitmap.
© Alcatel 77
SPDCH De-allocation: Principle
> A preemption is triggered in the MFS
• At the reception of an RR Allocation Indication message from the BSC
• In case there is one or several PDCH to give back to the BSC
• It concerns only used PDCHs where:
– Its mapped basic Abis nibble is used in an M-EGCH link
OR – At least 1 TBF is allocated on it
• CS preemption takes place in two main steps:
– Soft preemption
– Fast preemption
> No more SPDCH de-allocation based on low load situation
• T_PDCH_INACTIVITY and T_PDCH_INACTIVITY_LAST removed in B9
• Replaced by T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST to de-
allocate the unused GCHs
> The SPDCH de-allocation based on low load situation is not used anymore in B9, since the allocated
SPDCHs are fully managed by the MFS.
•This is applicable only for G3 BTS.
•For the G2 BTS, the SPDCH de-allocation process remains the same as in B8.
© Alcatel 78
SPDCH De-allocation: Preemption Mechanism
Arrival of RR Allocation
indication message
On TRXs with all its basic Abis

Lock PDCHs
nibbles impacted by CS preemption
T1 re-allocation Soft preemption
No TBF candidate for T1 or

T_PDCH_Preemption expiry
Fast preemption
All T1 requests played
successfully
Unlock PDCHs
> Step 1: lock the PDCHs of the TRXs which are highly impacted by the CS preemption
• This step is only applicable to Evolium BTSs
• The basic Abis nibbles of the time slots preempted by the BSC may be currently used by some GCHs in the cell.
Thus, the TRXs (or M-EGCHs) using these GCHs will be impacted by the preemption, even if the preempted TSs are
not on these TRXs. That’s why the TRXs of the cell for which the 2 following conditions are fulfilled have all their
PDCHs locked by the preemption process, it means that they cannot accept anymore traffic:
– Nb_GCH_Impacted_By_CS_Preemption > 0
– Established_Nb_GCH – Nb_GCH_Impacted_By_CS_Preemption <= Min_Nb_GCH_GBR
– Where:
– Nb_GCH_Impacted_By_CS_Preemption is the number of established GCHs in the M-EGCH
link using a basic Abis nibble mapped onto a radio time slot that is being deallocated by the
BSC.
– Established_Nb_GCH is is the number of GCHs that are activated in the M-EGCH link and
that will be kept activated during a certain time.
– Min_Nb_GCH_GBR is an estimation of the minimum number of GCHs necessary in a given
M-EGCH link for the GBR (Guaranteed Bit Rate) traffic supported by the TRX in both directions
(UL and DL).
> Step 2: soft preemption process
• 2 kinds of TBF are candidate for the T1 re-allocation process:
– The TBFs whose PACCH is supported by a preempted time slot.
– The TBFs for which it will no longer be possible to serve their on-going max allowed (M)CS because of
the subsequent reduction of the M-EGCH link size of their TRX.
• In addition, in the case where the number of TBFs established on a TRX will become too high according to the
remaining number of GCHs in the M-EGCH link of the TRX, then some TBFs will be released.
> Step 3: fast preemption process
• At T_PDCH_Preemption timer expiry:
– The TBFs which could not be T1 reallocated are released.
– The locked PDCHs which do not carry PACCH are released (TBF throughput reduction).
– The GCHs using the basic Abis nibbles of the preempted radio TSs are released.
> Step 4: unlock the PDCHs:
© Alcatel • If some PDCHs were “locked” in step 1, they are unlocked. Indeed, the CS preemption process is over, so the79
existing M-EGCH links will no longer be disturbed by the release of some of their GCHs due to the fast preemption.
SPDCH De-allocation: Soft Preemption (1/2)
> The MFS locks all the PDCHs impacted by the CS preemption:
• i.e. The de-allocated PDCH indicated in the RR Allocation Indication
message sent by the BSC (the PDCHs to be preempted)
>The MFS locks also all the PDCHs of the TRX which have a GCH mapped on a RTS impacted by preemption and only
in case of all the GCHs of the TRX are impacted by the preemption (rare case).
© Alcatel 80
SPDCH De-allocation: Soft Preemption (2/2)
> 2 kinds of TBF are candidate for the T1 re-allocation process:
• The TBFs whose PACCH is supported by a preempted time slot.
• The TBFs for which it will no longer be possible to serve their on-going
max allowed (M)CS because of the subsequent reduction of the M-
EGCH link size of their TRX.
31
.
TBF2 is candidate for .
T1 re-allocation .
TRX3 TRX4 Abis
TBF2 – MCS7
PDCHs to be TRX3
preempted
TRX2
TRX1 BCCH SD
Bonus Bonus
TBF1 – CS2 TRX1
RSL
OML
© Alcatel 81
SPDCH De-allocation: Fast Preemption
> Fast preemption:
• At expiry of T_PDCH_PREEMPTION, the MFS de-allocates the TS before
TBF ending, having the following impacts:
– The TBFs whose PACCH is impacted (the corresponding PDCH is marked)
are released.
– The MFS sends a “Packet TBF release” message with polling (i.e
acknowledgement is requested)
– The TBFs whose PACCH is not impacted are not released but have a
throughput reduction.
– The MFS sends a “Packet PDCH release” message indicating the
preempted PDCHs
• T_PDCH_PREEMPTION = TCH_INFO_PERIOD –1 = 4s
– T_PDCH_PREEMPTION cannot be set at the OMC-R anymore
Modified B9
>The PACCH blocks are the most important blocks to monitor. Many GPRS features ensure that PACCH blocks are
always monitored by the MS:
•The PTCCH is carried by the same PDCH as the PACCH.
•The RXLEV measurements for the power control and CS adaptation are made on the PDCH that carries the
PACCH blocks.
•Some RLS mechanisms are based on whether or not the MS is able to send or listen to PACCH blocks.
© Alcatel 82
2.3 TBF Radio Resources Allocation and Re-

allocation
© Alcatel 83
2.3 TBF Radio Resources Allocation and Ae-allocation B9
Definition of the 2 TBF Allocation Policies
> ASAP: used for BE TBF establishment, T1, T2 and T4 reallocation. Its
goal is to serve the request as soon as possible.
> OPTIMAL: used for T3 reallocation. Its goal is to ensure that a significant
bandwidth will be offered to the MS upon T3 reallocation, even if it takes
some time to establish all the necessary GCHs
> Nb_GCH_For_TBF_Estab:
• Minimum number of GCHs, which are required on the TRX to serve the
request.
Type of request Policy Nb_GCH_For_Estab
TBF establishment (without concurrent) ASAP 1
TBF establishment (with concurrent) ASAP 1 to 5 (Max_Allowed_(M)CS of concurrent TBF)
T1 TBF reallocation ASAP 1
T4 TBF reallocation ASAP 1 to 2 (Max_Allowed_CS of concurrent TBF)
T3 TBF reallocation Optimal 1 to 5 (Max_Allowed_(M)CS of concurrent TBF)
© Alcatel 84
2.3 TBF Radio Resources Allocation and Re-allocation B9
Determination of the Max_Allowed_(M)CS of a TBF
> Depends on the type of TBF (GPRS / EGPRS) and of the direction of the
TBF (UL / DL)
> Is based on the number of established GCHs:
• Established_Nb_GCH – Nb_GCH_Impacted_CS_Preemption
> Is limited by:
• GPRS / EGPRS TRX capability,
• MAX_GPRS_CS and MAX_EGPRS_MCS
Nb_GCH Max_Allowed_CS Nb_GCH Max_Allowed_MCS

1 CS-2 (UL) / CS-1 (DL) 1 MCS-2 (UL) / MCS-1 (DL)
≥2 CS-4 2 MCS-5
3 MCS-6
4 MCS-7
≥5 MCS-9
> Established_Nb_GCH is is the number of GCHs that are activated in the M-EGCH link and that will be kept activated
during a certain time.
© Alcatel 85
Functional Entities
R ADIO RE SO URCE ALLOC AT ION/RE ALLO C AT ION Best-effort TBF allocation/reallocation request
(received from RRM-PCC or dequeued from an Li list)
ALGO RIT HM
M ultislot class,
Bias,
Traffic type
TRX list sorted
by the BSC
T ransm ission Resource T RX list Num ber
Availability comp uting o f radio TSs
Cf. session 2.2 d eterm ination
DSP
congestion state n_MS_requested,
Available_Nb_GCH TRX list
n_MS_requested_concurrent
Type of the TBF request

Best candid ate allocation computation
Candidate TS allocation No candidate TS alloc ation
Cell T ransm ission Equity
Available_Nb_GCH_W ith_Equity
Test if enough G CHs
“Enough GCH s” “Not enough GCH s”
PDCH capacity/TF I/T AI/USF

allocation
“AL LOC OK” case

“AL LOC F AILED” case
T ransmission resource - rejected request
reservatio n - or L4 queuing
- or L5/L6 queuing
- or L7 queuing )
- or try to c hange TBF m ode (EGPRS case)
T BF E ST ABLIS HM E NT PRO CE S S
> L4
• The list of DL TBFs which are still not served (due to a lack of resources).
• This list is sorted according to the PDU lifetime of the first DL LLC PDU of each queued request.
• On PDU lifetime expiry, the request is removed from the queue.
> L5
• The list of MSs with UL bias which are candidate for resource re-allocation due to trigger T3.
• This list is sorted according to the following criteria:
– The candidate MSs are processed according to a FIFO order: the first request posted in the list is the first
processed by RRM PRH.
– In case it is not possible to reallocate resources to a candidate MS, the MS is put back at the end of the list.
> L6
• The list of MSs with DL bias which are candidate for resource re-allocation due to trigger T3.
• This list is sorted in the same way as L5.
> L7
• The list of MSs which are candidate for resource re-allocation due to trigger T4.
• The candidate MSs are processed according to a FIFO order: the first request posted in the list is the first processed
by RRM PRH.
• In case it is not possible to reallocate resources to a candidate MS, the MS is put back at the end of the list.
© Alcatel 86
Transmission Resource Availability
ALGO RIT HM
M ultislot class,
Bias,
Traffic type
TRX list sorted
by the BSC
DSP


allocation

- or L5/L6 queuing
- or L7 queuing )
© Alcatel 87
Transmission Resource Availability: Example (1/4)
> 3 cells with 2 TRXs:
• Max_PDCH_High_Load = 4 => a maximum of 4 non CS preemptable
basic Abis nibbles can be established in the cell
• MAX_PDCH = 8, MAX_EGPRS_MCS = MCS-9, MAX_GPRS_CS = CS-4
• Max_SPDCH_Limit = 6 =>a maximum of 6 basic Abis nibbles can be
established in the cell
radio Abis
Cell A
Cell B
Basic 6x4 extra
nibbles nibbles
Cell C
CS
© Alcatel 88
> First EDGE MS1, class 8 in cell A -> Target_Nb_GCH = 18
• GCH Allocation for MS1
– 4 basic Abis nibbles in the Max_PDCH_High_Load zone
– 14 extra Abis nibbles
– Total = 18 GCHs
basic
Cell A
extra
Cell B
Cell C
CS CS
MS1 Cell A
© Alcatel 89
> Second EDGE MS2, class 8 in cell B -> Target_Nb_GCH = 18
• GCH Allocation for MS2
– 4 basic Abis nibbles in the Max_PDCH_High_Load zone
– 10 free extra Abis nibbles
– 2 basic Abis nibbles outside the Max_PDCH_High_Load zone
– Inter GCH preemption between Cell A and Cell B:
– 14 extra Abis in cell A, 10 extra Abis in cell B
– 2 extra Abis nibbles are preempted from Cell A to Cell B
– Total = 18 GCHs basic
Cell A
extra
Cell B
Cell C
CS
Cell A
CS Cell B
MS1
MS2
© Alcatel 90
> After GCH allocation of MS2 in cell B
• In Cell A: Established_Nb_GCH = 16
> Next Periodical GCH process in Cell A:
• 2 basic Abis nibbles outside the Max_PDCH_High_Load zone
• Total = 16 + 2 = 18 GCHs
basic
Cell A
extra
Cell B
Cell C
CS
Cell A
CS Cell B
MS1
MS2
© Alcatel 91
Number of Radio TS Determination (1/3)
ALGO RIT HM
M ultislot class,
Bias,
Traffic type
TRX list sorted
by the BSC
DSP


allocation

- or L5/L6 queuing
- or L7 queuing )
© Alcatel 92
2.3 TBF Radio Resources Allocation and Re-allocation
Number of Radio TS Determination (3/3)
> The number of radio TSs is determined for:
• The direction of the request (n_MS_requested)
• The concurrent direction (n_MS_requested_concurrent)
> Taken into account
• The MS multislot class
• Maximum number of PDCH allocated to a single (E)GPRS connection:
MAX_PDCH_PER_TBF
• The direction mainly used (in terms of throughput) by the on-going
application: the bias
– The MFS counts and averages the number of bytes transferred in both
directions
– By default bias = DL
– Except when the first TBF establishment is a “UL 2 phase access”
• The traffic type
– Only 1 TS is allocated in case of GMM/SM signaling traffic
> When allocating resources to an MS, both n_MS_requested and n_MS_requested_concurrent are considered, even when
only one TBF is established or being established, to take into account a potential future concurrent TBF, except in case of UL
TBF establishment without concurrent DL TBF (Immediate UL TBF establishment), where only n_MS_requested is taken into
account to allocate resources for the UL TBF.
>General purpose of the bias determination:

•GPRS MSs are often involved in consecutive UL/DL transfers for a unique service.
• The Bias determination shall identify the direction of the main flow of data (based on the quantity of data exchanged
at a specific moment) in order to prioritize:
–The initial allocation on the biased direction.
–The re-allocation process on the main direction (likely to carry the useful data).
>Each time n_received_octets_UL = N_BIAS_DETERMINATION or n_sent_octets_DL = N_BIAS_DETERMINATION
(whichever is reached first), RRM determines the bias as follows:
• if Av_n_received_octets_UL > Av_n_sent_octets_DL, the transfer is deemed uplink biased,
• else the transfer is deemed downlink biased.
> RRM then resets to 0 the counters n_received_octets_UL and n_sent_octets_DL.
> Where:
• n_received_octets_UL represents the number of octets received in the UL.
• n_sent_octets_DL represents the number of octets sent in the DL.
• Av_n_received_octets_UL represents an average number of octets received in the UL.
• Av_n_sent_octets_DL represents an average number of octets sent in the DL.
• Av_n_received_octets_UL (new) = WEIGHT_BIAS_DETERMINATION * Av_n_received_octets_UL (old) + (1 -
WEIGHT_BIAS_DETERMINATION) * n_received_octets_UL.
• Av_n_sent_octets_DL (new) = WEIGHT_BIAS_DETERMINATION * Av_n_sent_octets_DL (old) + (1 -
WEIGHT_BIAS_DETERMINATION) * n_sent_octets_DL.
>N_BIAS_DETERMINATION and WEIGHT_BIAS_DETERMINATION are MFS (DLS) parameters used to tune the bias
determination. The weighting factor is used in particular to avoid changing too quickly the bias of a transfer so that this
determination takes into account the number of octets exchanged in the past.
> Default values:
• N_BIAS_DETERMINATION = 3 KB
• WEIGHT_BIAS_DETERMINATION = 0,7
© Alcatel 93
Best Candidate Allocation Computation
ALGO RIT HM
M ultislot class,
Bias,
Traffic type
TRX list sorted
by the BSC
DSP


allocation

- or L5/L6 queuing
- or L7 queuing )
© Alcatel 94
SPDCH States
> GPRS
MAX_XX_TBF_SPDCH
PDCH PDCH PDCH FULL

ALLOCATED ACTIVE No additional TBF can
be established on
> EGPRS the PDCH
• The same states and parameters are used
• But, only EGPRS TBFs are taken into account
> specific state for GPRS UL TBF allocation: EGPRS PDCH
• PDCH used in the DL by an 8-PSK capable EGPRS TBF
> The parameter N_TBF_PER_SPDCH has been removed Modified B9
• The BUSY state is not considered anymore

>Following states are defined for a PDCH:

•Allocated:
–New definition in B9: the PDCH is an SPDCH which has been indicated as usable for PS traffic by the BSC.
–B8 definition: radio resource allocated to the MFS, but associated transmission resources are not allocated.
• Active:
–New definition in B9: an allocated PDCH is active if it supports at least one radio resource allocated for a TBF or for an
RT PFC.
–the B8 definition was considering the parameter N_TBF_PER_SPDCH which is removed in B9 release.
•Full:
–New definition in B9: an allocated PDCH is full in a given XL (XL = UL or DL) direction if and only if:
–for GPRS Best Effort TBF: Nb_RT_PFC_XL + Nb_BE_TBF_XL ≥ MAX_XL_TBF_SPDCH
–for EGPRS Best Effort TBF: Nb_RT_PFC_XL + Nb_BE_EGPRS_TBF_XL ≥ MAX_XL_TBF_SPDCH
–for RT resource allocation: Nb_RT_PFC_XL + Nb_BE_TBF_XL ≥ MAX_XL_TBF_SPDCH
–This is the same definition as in B8 release except that the concepts of RT PFC and best effort TBF are
introduced.
•EGPRS:
–An allocated PDCH is in the “EGPRS” state if some radio resources are allocated in the DL direction, for an EGPRS TBF
or an EGPRS RT PFC. This state is only used when running the radio resource allocation/reallocation algorithm in GPRS
mode and when considering the UL direction of the candidate TBF allocations.
–This is nearly the same definition as in B8 release except that the concept of RT PFC is introduced.
© Alcatel 95
Available Throughput Computation
> For a GPRS TBF, in case of only BE TBFs with the same priority (MR0)
n
1
• available_throughput_candidate_XL = R_AVERAGE_GPRS * ∑ NB_TBF
i =1 PDCHi +1
• NB_TBFPDCHi represents the number of already allocated GPRS and EGPRS
TBFs on the PDCH i
> For an EGPRS TBF, in case of only BE TBFs with the same priority (MR0)
n
1
• available_ throughput _candidate_XL = R_AVERAGE_EGPRS * ∑ NB_TBF
i =1 PDCHi +1
• NB_TBFPDCHi represents the number of already allocated EGPRS TBFs on
the PDCH i
© Alcatel 96
Candidate TS Allocation Sorting
> The criteria of the TBF radio resource allocation/reallocation algorithm
are “throughput-based”:
ALPHA/ For “ASAP” policy only: the candidate time slot allocations, which are on some
TRXs for which (Established_Nb_GCH - Nb_MPDCH) is greater than
Nb_GCH_For_TBF_Estab” are preferred
A/ For UL GPRS TBF establishment / reallocation only: the candidate time slot allocations,
which have the lowest number of PDCHs in the “EGPRS” state are preferred
B/ the candidate time slot allocations, which have the highest available throughput in the
direction of the bias are preferred
C/ the candidate time slot allocations, which have the highest available throughput in the
direction opposite to the bias are preferred
D/ the candidate time slot allocations, which are on the TRX with the highest priority, are
preferred
E/ for EGPRS TBFs establishments only: the candidate time slot allocations, which have the
lowest number of GPRS TBFs in the direction of the bias, are preferred
F/ combinations with the PDCHs that have the lowest index are preferred
Exercise1 Exercise2
> When evaluating criterion [F], the concurrence constraints imposed by the MS multislot class (if it is known) or by the
default multislot class (if the MS multislot class is not known) shall be taken into account. This will indeed avoid unnecessary
subsequent T2 TBF reallocations (after having established an incoming TBF without concurrent TBF).
© Alcatel 97
Re-allocation (1/2)
> 4 different TBF reallocations are permanently activated:
• T1: reallocation to maintain a TBF alive despite the CS preemption of
some RTSs or of some GCHs in the cell
• T2: reallocation of an on-going TBF when establishing a concurrent TBF
• T3: reallocation useful to
– Establish a new M-EGCH link for one of the TRXs of the cell
– Perform a “radio de-fragmentation” process
– Provide a higher throughput, if it is possible, to a TBF
• T4: reallocation to move a UL GPRS TBF sharing one PDCH with a DL
EGPRS TBF onto PDCHs which do not support a DL EGPRS TBF. It
concerns only GPRS TBFs
> The parameter EN_RES_REALLOCATION has been removed
>To be candidate to subsequent resource re-allocation (T3 and T4), the following conditions have to be met:
•the TBF established in the biased direction is marked with “subsequent allocation”.
•more than N_CANDIDATE_FOR_REALLOC bytes have been transferred for the TBF in the biased direction.
•T3192 is not running (specific to UL TBF re-allocation when T3192 is running for the DL TBF).
>The subsequent re-allocation is done whether or not the TBF corresponds to the bias transfer direction of the MS.
> N_CANDIDATE_FOR_REALLOC default value = 200 Bytes, it cannot be set at OMC-R level.
© Alcatel 98
Re-allocation (2/2)
> T3 TBF reallocation:
• A T3 TBF reallocation is based on the following principles:
– Computing of a THROUGHPUT_RATIO (= Allocated_Throughput /
Optimal_Throughput) to know “how sub-optimal a TBF allocation is”
– A T3 TBF reallocation will only be allowed if a significant
THROUGHPUT_RATIO gain is reached. The minimal gain is set by the
system parameter: MIN_THROUGHPUT_GAIN (= 40%)
> THROUGHPUT_RATIO:
•for each MS which is candidate for a T3 TBF reallocation, a “throughput ratio” is calculated.
•this “throughput ratio” is useful to:
–validate the candidate TBF allocations when playing the radio resource reallocation algorithm.
–sort the T3 TBF reallocation requests within the L5 and L6 lists: low value of the “throughput ratio” means
high priority of the request.
•THROUGHPUT_RATIO = ALLOCATED_THROUGHPUT / OPTIMAL_THROUGHPUT
–ALLOCATED_THROUGHPUT is the throughput currently allocated to the TBF in the direction of the bias and
is equal to potential_throughput_PDCH * available_capacity_candidate_XL.
–OPTIMAL_THROUGHPUT is the optimal throughput that could be potentially allocated to the TBF in the
direction of the bias by considering its multislot class and is equal to potential_throughput_PDCH *
n_MS_requested.
> best candidate allocation computation:

•a candidate TBF allocation shall fulfill the following conditions:
–NEW_THROUGHPUT_RATIO min(1, (1+MIN_THROUGHPUT_GAIN ) *
CURRENT_THROUGHPUT_RATIO).
–NEW_THROUGHPUT_RATIO is the “throughput ratio” of the candidate TBF allocation.
–CURRENT_THROUGHPUT_RATIO is the “throughput ratio” of the current TBF allocation.
–MIN_THROUGHPUT_GAIN is an O&M parameter.
© Alcatel 99
Re-allocation: example
> Initial situation:
• 3 MSs (MSa, MSb, and MSc), all GPRS and (4+1)
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
UL MSa MSc MSb UL

MSc MSc MSc MSc
DL MSa MSa MSa MSa MSb MSb MSb MSb DL
• MSc is the most impacted by the multiplexing in terms of throughput

> In B8: MSc is not candidate for T3 reallocation because its allocation is
optimal (4 TS in DL)
> In B9:
• MSc is candidate for T3 reallocation
• A new TRX will be established (cf. “Optimal” policy) and MSc will then be
reallocated on this new TRX
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
UL MSa MSb UL MSc
DL MSa MSa MSa MSa MSb MSb MSb MSb DL MSc MSc MSc MSc
© Alcatel 100
2.4 TBF Release Routine
© Alcatel 101
2.4 TBF Release Routine B9
Justification
> Wap access to home page without any feature
UL
DL
> With Delayed DL TBF Release (B7)
> With Delayed DL TBF TBF Release & Extended UL TBF Mode
– Typical gain on Wap access to home page :

– ~8 seconds with Delayed DL TBF Release
– + ~2 seconds with Extended UL TBF Mode
© Alcatel 102
Delayed DL TBF Release (1/4)
> Artificial extended DL TBF duration aiming at coping with jerky DL
traffic from the CN
> Procedure:
• the last DL RLC blocks are marked with FBI=0
• the TBF state goes from Active to Delayed
• periodical Dummy DL RLC blocks in polling (S/P=1) sent by the MFS to
trigger acknowledgement from the MS (FAI=0)
• when a new DL LLC PDU arrives at the MFS, the useful RLC Block
transfer is resumed
• the TBF state goes from Delayed to Active
> The MS does not take into account Dummy LLC PDU during the
delayed release phase
> Jerky LLC PDU delivery at MFS due to buffer capacities of servers, SGSN and MFS. A TCP segment can generate up to 3
LLC PDUs. Also called “Bursty traffic”. HTTP and WAP services are likely to benefit from this feature.
> FBI: Final Block Indicator (RLC header)

> FAI: Final Acknowledgement Indicator
> S/P: triggers polling (packet Ack/Nack message) when set to 1
> Periodical sending of DL RLC Blocks = polling period calculation: the MFS takes into consideration T3190 (guarding timer
between 2 valid data received from the Network) in addition to the requirement of receiving at least one block every 360 ms
(78 TDMA frames). (T3190n = 5 s (Alcatel recommended value), it cannot be set at OMC-R level).
> T3190n = Timer used in the procedure “DL TBF abnormal release”: when the DL TBF is cut due to the radio link quality or
loss of the MS, the TFI and TAI cannot be reallocated during T3190n. The default value is 5s and it cannot be set at the
OMC-R level.
>The UL Delayed TBF release (scheduling of additional USF) is only possible for Rel-4 MS.
© Alcatel 103
> End of delayed released period when T_Delayed_DL_TBF_Rel expires
• T_Delayed_DL_TBF_Rel = T_NETWORK_RESPONSE_TIME
• The MFS sends a Dummy UI command marked with FBI=1, S/P=1
• Acknowledged mode:
– The MS sends the last Packet DL Ack/Nack message (FAI=1)
• Non-Acknowledged mode:
– The MS sends the last Packet Control Ack message
• T3192n and T3192 are triggered (Fast DL re-establishment)
> T_NETWORK_RESPONSE_TIME corresponds to the time difference between a command sent to the SGSN and the
response received at the MFS. The default value is 700ms but it can be set at OMC-R level and can be tuned according to
Gb traces.
© Alcatel 104
> RRM periods on MFS side:
• T_DELAYED_DL_TBF_POL_INITIAL (=60ms): the time that the MFS shall wait
before sending the first RLC data block containing only LLC Dummy UI
• 2 timers are used to define the period between 2 DL Dummy UIs sent to the
MS:
– T_MIN_POLL (=60ms), in case of the MS is “alone” on the PDCH which carries
the PACCH
– T_DELAYED_DL_TBF_POL (=200ms) in case of the MS is “multiplexed” on the
PDCH which carries the PACCH
• T_DELAYED_DL_TBF_POL_UL (=2s): the period between 2 DL Dummy UIs
sent to the MS, when there is an on-going UL TBF
>Upon each expiry of T_DELAYED_DL_TBF_POL (the timer reaches T_DELAYED_DL_TBF_POL_INITIAL or

T_DELAYED_DL_TBF_POL), a new Dummy UI command is inserted and T_DELAYED_DL_TBF_POL is restarted.
> T_DELAYED_DL_TBF_POL_INITIAL = 60 ms
> T_DELAYED_DL_TBF_POL = 200 ms
> T_MIN_POLL = 60 ms
> T_DELAYED_DL_TBF_POL_UL = 2000 ms
> All these timer values are default ones and they cannot be set at OMC-R level.
> T_DELAYED_DL_TBF_POL is used to:

• give the opportunity to the MS to request a UL TBF through the Packet DL Ack/Nack acknowledging the polling,
without too much disturbing the other TBFs (data transfer for the DL and USF scheduling for the UL) multiplexed on the
same PDCH (--> not too short period for Dummy UI commands).
• maintain the DL TBF at MS level (re-activation of T3190 timer (5s) in the MS) (--> period for Dummy UI commands
< 5s).
> T_MIN_POLL is applied when the PDCH corresponding to the PACCH of the considered DL TBF is not shared with
another enabled DL TBF and when there is no activated UL TBF on this PDCH (ie, no UL TBF in enabled or extended mode,
for which USF may be scheduled).
© Alcatel 105
> (1): There is no more DL LLC PDU stored for the MS. The BSS sends the last segment of the last useful RLC block. This
block contains the last segment of the last useful DL LLC PDU, completed by a dummy LLC PDU in order to maintain the DL
TBF alive. The Final Block Indicator is not set (FBI=0) and a polling is requested to the MS. T_Delayed_DL_TBF_Pol_Initial is
activated (default value = 100 ms).
> (2): When the MS has acknowledged the last useful DL RLC block, T_Delayed_DL_TBF_Rel is activated (duration of the
delayed DL TBF release phase).
> (3): At T_Delayed_DL_TBF_Pol_Initial expiry, a new RLC block containing one or more dummy LLC PDUs is sent to the
MS. This RLC block contains a polling indication so that the MS can request a UL TBF establishment, if required.
T_Delayed_DL_TBF_Pol (default value = 200 ms) is activated.
> (4): At T_Delayed_DL_TBF_Rel expiry, a last DL RLC block is sent with the Final Block Indicator set (FBI = 1), indicating the
end of the DL TBF. The normal release procedure then applies.
© Alcatel 106
DL TBF Extension (1/2)
> When a UL TBF is established during a delayed DL TBF release:
• T_Delayed_DL_TBF_Rel is stopped and reset
• The delayed DL TBF release state is maintained during the UL TBF
• DL Dummy UIs are sent every T_DELAYED_DL_TBF_POL_UL
– The aim of this timer is just to maintain the DL TBF at MS level (must be lower
than T3190)
– Therefore T_DELAYED_DL_TBF_POL_UL > T_DELAYED_DL_POL
• At the end of the UL TBF, T_Delayed_DL_TBF_Rel is restarted
> The aim of this function is to avoid the case where a UL TBF is established on the PACCH of a DL TBF which is at the end
of its delayed DL TBF release phase.
> Indeed in this case, the subsequent DL LLC PDU (i.e., corresponding to a server response) may be received after the
release of the DL TBF.
© Alcatel 107
DL TBF Extension (2/2)
Exercise
> (1): The DL TBF is in delayed DL TBF release phase. Periodically Dummy UI Command messages are sent to the MS with
polling indication to give to the MS the opportunity to send a UL TBF request.
> (2): The MS uses a Packet DL Ack/Nack to request a UL TBF. The UL TBF is established and T_Delayed_DL_TBF_Rel is
stopped (the DL TBF remains in delayed DL TBF release state, during the UL TBF).
> (3): At UL TBF release, the timer T_Delayed_DL_TBF_Rel is re-activated.
> (4): When a DL LLC PDU is received, the first DL RLC data block can be immediately sent and T_Delayed_DL_TBF_Rel is
stopped.
> (5): T_Delayed_DL_TBF_Rel is stopped, when the first UL RLC data block is received.
© Alcatel 108
Fast DL TBF Re-establishment (1/2)
> After DL TBF release, the following timers are considered
> MS side
• T3192 started after sending of final Packet DL Ack/Nack message
(FAI=1)
• during T3192 the MS listens to the PDCH carrying the PACCH blocks of
its last DL TBF
>T3192 = 500 ms (default value which can be set at OMC-R level).
© Alcatel 109
Fast DL TBF Re-establishment (2/2)
> MFS side
• T3192n started after reception of final Packet DL Ack/Nack message
• Wait for reuse of MS radio resources (PDCHs, TAI, TFI)
• If a DL LLC PDU is received by the MFS, a fast DL TBF re-establishment
is triggered on the PACCH
• T3192n = T3192 – (T_Round_Trip_Delay + T_Fast_DL_Margin)
> During T3192n, a UL TBF establishment is not possible
> During the on-going of T3192n, no UL TBF establishment procedure can be proceeded. This is a limitation to fast
switching from DL TBF to UL TBF during the MS-GSS signaling procedure (location update for example). In order to avoid
a too long duration of these procedures, the MFS anticipates the UL TBF establishment by starting the procedure before
the end of the DL TBF release.
> T3192n takes into account the trip time needed for “Packet DL Ack/Nack” message from the MS to the MFS
(½T_Round_Trip_Delay + ½T_Fast_DL_Margin) AND trip time needed for “Packet DL Immediate Assignment ” message
from the MFS to the MS (½T_Round_Trip_Delay + ½T_Fast_DL_Margin).
> Round_Trip_Delay (MFS-MS) = 160 ms (default value which can be set at OMC-R level).
> T_Fast_DL_Margin = 50 ms (default value which cannot be set at OMC-R level).
> Note: during T3192n seconds, the Timing Advance is monitored. Even so, if TAI occurs, the MS must send its Access
Burst for the Timing Advance calculation by the BTS. The MS shall listen to the TA Messages in the DL.
© Alcatel 110
Non-DRX Mode after Packet Data Transfer (1/2)
> Discontinuous Reception (DRX mode):
• Used in GSM to increase the battery autonomy on an MS as in GSM CS:
the MS listens only to its Paging Group
• Downlink TBF establishment through PCH long as compared with the
TBF duration
• The MFS establishes a DL TBF on the first available PCH message of an
MS Paging group
> Non-DRX:
• Continuous monitoring of AGCH messages by the MS
• The MFS establishes a DL TBF on the first available AGCH block (without
MPDCH) or the first PPCH occurrence (with MPDCH)
>This feature outlines one of the major differences between the GPRS service (non connected mode) and the GSM
service (connected mode). The DRX mode is highly recommended in GSM to save the cell battery when it may be a
handicap in GPRS (where the paging is likely to occur more frequently).
© Alcatel 111
Non-DRX Mode after Packet Data Transfer (2/2)
> Non-DRX mode:
• Non-DRX period
– Min (NON_DRX_Timer; DRX_TIMER_MAX)
– Non-DRX period computed by the MFS and sent in “Packet DL Immediate
Assignment” message
• The DRX mode of an MS is evaluated each time the MFS receives DL LLC
PDU from the SGSN
• The MFS keeps the MS context until expiry of:
– DRX_TIMER_MAX if NON_DRX_Timer unknown for the MS
– Non-DRX period otherwise (provided within the DL LLC PDU)
• DRX_TIMER_MAX limited to 4 seconds, broadcast on SI13
>NON_DRX_Timer is unknown for the MFS when after the release of an uplink TBF, no DL concurrent TBF was
Established, or after the release of a downlink TBF when the DL LLC PDUs do not convey the DRX parameters.
>When the MFS assesses that the MS returns to the DRX mode during the transmission of the assignment message, the
message is sent to the PCH or PPCH channel. The MFS shall then take into account the 95% AGCH or PPCH queuing
time (about 400 ms) in addition to the round trip time delay measured at RRM level (about 160 ms).
>Assuming a Non-DRX period of 2 seconds, this means that the downlink LLC PDU shall be received within 1.4 second
to speed up the establishment of the DL TBF.
>DRX_TIMER_MAX = 2 s (Alcatel recommended value) and it can be set at OMC-R level.
© Alcatel 112
DL TBF Release: Summary
T_NETWORK_RESPONSE_TIME
DL TBF
TBF active TBF delayed Fast DL TBF
T3192
establishment via PACCH
DL TBF
release Fast DL TBF establishment
T3192 DRX_TIMER_MAX via AGCH or any PPCH
DL TBF Non-DRX mode
T3192 DRX_TIMER_MAX
DL TBF establishment
DL TBF Non-DRX mode via PCH or PPCH
of MS paging group
>The tables below indicate examples of the expected DL TBF establishment duration with or without the feature.
© Alcatel 113
Delayed UL TBF Release: Without Extended Mode (1/3)
> The UL TBF release is delayed when:
• T_DELAYED_FINAL_PUAN <> 0
• No concurrent DL TBF:
– Is established
– Is being established
– Is being Released
> During the delayed UL TBF release:
• The MFS can establish a DL TBF on the PACCH/DL of the UL TBF
• The DL TBF establishment is speeded up
> The UL Delayed TBF release (scheduling of additional USF) is only possible for a Rel-4 MS.
© Alcatel 114
> No DL LLC PDU is received during the delayed final PUAN phase
MS MFS SGSN
RLC/MAC block (BSN=n, CV=0) (1)

LLC PDU (last LLC) (2)
P. UL Ack/Nack (FAI=0, SSN = n) (3)
(4)
T3180 T_DELAYED_FINAL_PUAN
final P. UL ACK/NACK + polling (5)
T3180n
Packet Control Ack (6)

(7)
> (1): The last UL LLC PDU is received by the RLC. The RLC maintains the UL TBF alive since a normal end is not allowed.
> (2): The UL LLC PDU is sent to the RRM. A flag is set by the RLC, in order to notify the RRM that it is the last UL LLC PDU
of the TBF.
> (3): A Packet UL Ack/Nack is sent to the MS, without polling, with FAI=0.
This message does not acknowledge the last block (n).
> (4): Upon receipt of the last UL LLC PDU, the RRM starts an instance of the timer T_DELAYED_FINAL_PUAN. The UL LLC
PDU is forwarded to the SGSN.
> (5): At T_DELAYED_FINAL_PUAN expiry, the RRM requests the RLC to release the UL TBF, by sending a
PCC_RLC_Activate-req allowing the RLC to perform a normal TBF end.
The RLC sends the final packet UL Ack/Nack to the MS and waits for Packet Control Acknowledgement.
T3180n is activated (T3180n = T3180 - Round Trip Delay - T_DELAYED_FINAL_PUAN).
> (6): The MS acknowledges the receipt of the final PACKET UL Ack/Nack message.
> (7): The RLC notifies the RRM about the release of the UL TBF. The resources of the UL TBF are released. The RRM
informs the BSSGP layer about the release of the UL TBF, and the BSSGP de-allocates the corresponding throughput.
T3180n is stopped.
© Alcatel 115
> Delayed final PUAN, with DL TBF establishment
MS MFS SGSN
RLC/MAC block (BSN=n, CV=0) (1)

LLC PDU (last LLC) (2)
P. UL Ack/Nack (FAI=0, SSN = n) (3)
(4)
T_DELAYED_FINAL_PUAN
DL LLC PDU (5)
PACKET DOWNLINK ASSIGNMENT (6)
T3180
T3180n
final P. UL ACK/NACK + polling (8)

(10)
> (1): The last UL LLC PDU is received by the RLC. The RLC maintains the UL TBF alive since normal end is not allowed.
> (2): The UL LLC PDU is sent to the RRM. A flag is set by the RLC, in order to notify the RRM that it is the last UL LLC PDU
of the TBF.
> (3): A Packet UL Ack/Nack is sent to the MS, without polling, with FAI=0.
This message does not acknowledge the last block (n).
> (4): Upon receipt of the last UL LLC PDU, the RRM starts an instance of the timer T_DELAYED_FINAL_PUAN. The UL LLC
PDU is forwarded to the SGSN.
> (5): A DL LLC PDU is received by the MFS while the timer T_DELAYED_FINAL_PUAN is running.
> (6): Radio resources are requested to RRM-PRH. Upon RRM-PRH response, the RRM-PCC stops the timer
T_DELAYED_FINAL_PUAN, delays the release of the UL TBF until the completion of the DL TBF establishment procedure,
establishes the DL TBF on the PACCH/DL of the UL TBF.
• If T_DELAYED_FINAL_PUAN expires before the response of the RRM-PRH, then the RRM-PCC requests the RLC to
release the UL TBF, by sending a PCC_RLC_Activate-req allowing the RLC to perform a normal TBF end. In this case,
at RRM-PCC response, the DL TBF will be established on CCCH, at the end of the UL TBF release.
> (7): The MS acknowledges the receipt of the assignment message and listens to the DL resources. The BSS sends a Packet
Power Control and Timing Advance and then begins the DL data transfer.
> (8): Upon receipt of the PACKET CONTROL ACKNOWLEDGEMENT, the RRM immediately requests the RLC to release
the UL TBF, by sending a pcc-rlc-activate-req primitive allowing the RLC to perform a normal TBF end. The RLC sends the
final PACKET UL Ack/Nack to the mobile station and waits for a PACKET CONTROL ACKNOWLEDGEMENT.
> (9): The MS acknowledges the receipt of the final PACKET UL Ack/Nack message.
> (10): The RLC notifies the RRM about the release of the UL TBF. The RRM stops T3180n. The resources of the UL TBF are
released. The RRM informs the BSSGP layer about the release of the UL TBF, and the BSSGP de-allocates the corresponding
throughput.
© Alcatel 116
Delayed UL TBF Release: with Extended Mode (1/4)
> Principle
• At the end of the active phase (CV=0)
• The MFS continues to schedule some USFs
• To allow the MS to send some dummy RLC blocks
MS MFS SGSN
RLC/MAC block (BSN=n, CV=0)

start LLC PDU (last LLC)
P. UL Ack/Nack (FAI=0, SSN = n+1)
USF
T_MAX_EXTENDED_UL
Dummy RLC data block
..
.
USF
expiry
final P. UL ACK/NACK + polling

Packet Control Ack
> The aim of this feature is to extend the duration of the UL TBF in order:
•To quickly restart data transmission in UL if higher layers in the MS deliver new data, without having to re-establish a
new UL TBF, after the countdown procedure has started.
•To maintain the UL TBF established, some time after the last block (CV=0) has been acknowledged by the network.
>This feature allows to improve the access time to the GPRS network. It also improves the throughput in some cases.
>The feature is described in 3GPP TS 44.060 - V4.18.0. It applies for R4 MS.
© Alcatel 117
> The UL transfer can resume at any time during the extended phase
MS MFS SGSN
RLC/MAC block (BSN=n, CV=0)

Active UL start
data transfer
LLC PDU (last LLC)
P. UL Ack/Nack (FAI=0, SSN = n+1)
USF
Extended UL
data transfer USF T_MAX_EXTENDED_UL
USF
RLC/MAC block (BSN=n+1) stop
Active UL
data transfer
USF
RLC/MAC block (BSN=n+2)
.. LLC PDU
.
© Alcatel 118
> Conditions to operate
• EN_EXTENDED_UL_TBF = enabled
• Rel-4 MS
• The MS has to know if the BSS supports the feature
– The BSS capability (NW_EXT_UTBF) is broadcast on BCCH (SI13)
• The BSS has to know if the MS supports the feature
– The MS radio access capability is
– received at downlink TBF establishment in the first downlink PDU, or
– retrieved through the Radio Access Capability Update which involves the
SGSN
» If EN_RA_CAP _UPDATE = enabled
> If one of these 4 conditions is not fulfilled, the normal UL TBF release is
performed, as in B8 (T_DELAYED_FINAL_PUAN is applied)
> TLLI context retrieval procedure

•This procedure has been developed in B8 for the feature full intra PDU re-routing.
•The TLLI is known in the SGSN and by one GPU in the MFS. The TLLI retrieval procedure allows to retrieve
information linked to the TLLI, among which the Radio Access Capability from another GPU.
•This procedure can be triggered at uplink TBF establishment, as soon as the contention resolution is completed.
> Radio Access Capability Update

•Enabled or disabled the Radio Access Capability update on Gb by flag, EN_RA_CAP _UPDATE. It is recommended to
enabled this flag if EN_EXTENDED_UL_TBF is enabled and Radio Access Capability update is supported by the SGSN.
•At UL TBF establishment, immediately after the “contention resolution” procedure, the “radio access capability
update” procedure is triggered in the BSS. The BSS requests an MS’s current Radio Access capability and/or its IMSI by
sending to an SGSN an RA_CAPABILITY_UPDATE, which includes the TLLI of the MS and a Tag. Then it starts timer
T5_RA_CAP_UPDATE (value = 5s). In case of timer expiry, the BSS shall repeat the request up to
RA_CAPABILITY_UPDATE_RETRIES times (value = 3).
•The SGSN shall respond by sending an RA_CAPABILITY_UPDATE_ACK, which includes the TLLI of the MS, the Tag
received in the corresponding RA_CAPABILITY_UPDATE.
•When the SGSN answers, the MS Radio Access capability is updated and the Extended UL feature can be used if the
“GERAN Feature Package 1” bit is set. Otherwise, the MS does not support the extended uplink feature.
© Alcatel 119
> The way to schedule the USFs in extended UL TBF mode:
• Scheduled only on the PDCH which carries the PACCH
• IF the PDCH supports uplink TBFs which are all in extended mode AND
EN_FAST_USF_UL_EXTENDED = enabled THEN
– the throughput in radio blocks is equally shared between MSs
– So USFs are scheduled as follows:
– One MS in extended mode on PACCH: USF scheduled every 20ms
– Two MSs in extended mode on PACCH: USF scheduled every 40ms
– n MSs in extended mode on PACCH: USF scheduled every n x 20ms
• ELSE (if EN_FAST_USF_UL_EXTENDED = disabled OR if the PDCH supports at
least one MS which is in UL transfer)
– A period T_EXTENDED_UL_TBF_POL (200 ms) is used to schedule the USFs for all
the MSs in extended mode
– The remaining bandwidth is used for MSs in transfer
> RRBP mechanism has priority over USF scheduling
• This means the USF scheduling may be shifted if RRBP request from the RLC
© Alcatel 120
UL TBF Release: Summary
> Delayed final PUAN (without extended mode)
T_DELAYED_FINAL_PUAN
UL TBF
TBF active release
> Extended UL TBF mode NewB9

T_MAX_EXTENDED_UL
UL TBF
TBF active TBF extended release
> The UL TBF can be released before the expiry of the timer T_MAX_EXTENDED_UL: in case of a concurrent DL TBF is
present and after the completion of DL delayed phase, the expiry of T3192 triggers the release of the UL TBF.
> Consequently, the uplink TBF in extended mode is released when either T3192 expires or T_MAX_EXTENDED_UL expires.
© Alcatel 121
2 RADIO RESOURCE MANAGEMENT
2.5 Exercises
© Alcatel 122
2.5 Exercises
GPRS Channels (1/3)
> UL PDTCH and PACCH multiplexing on SPDCH:
> UL transfer? DL transfer?
Block number Downlink Uplink
RLC header MAC header Block Content?
TFI USF RRBP
Block n PDTCH / PACCH a TFI a USF j false ?
Block n+1 PDTCH / PACCH b TFI b USF k false ?
Block n+2 PDTCH / PACCH a TFI a USF j +3 ?
Block n+3 PDTCH / PACCH b TFI b USF k false ?
Block n+4 PDTCH / PACCH b TFI b ??? false ?

Block n+5 PDTCH / PACCH b TFI b USF j false ?
Block n+6 PDTCH / PACCH a TFI a USF k false ?
Back
© Alcatel 123
2.5 Exercises
GPRS Channels (2/3)
> Fill in the blocks of a DL secondary MPDCH
multiframe having the following criteria:
> BS_PBCCH_BLKS=2
> BS_PAG_BLKS_RES=6
> Fill in the blocks of a UL PDCH multi-frame

having the following criterion:
> BS_PRACH_BLKS=4
Time allowed:
10 minutes
© Alcatel 124
2.5 Exercises
GPRS Channels (3/3)
> DL multiframe: secondary MPDCH
– BS_PBCCH_BLKS=2
– BS_PAG_BLKS_RES=6
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
?????
PAGCH
?????
PAGCH
?????
PPCH, PAGCH
> UL multiframe:
– BS_PRACH_BLKS=4
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
?????
PRACH
?????
Back
>CAUTION: animated slide
© Alcatel 125
2.5 Exercises B9
Autonomous Packet Resource Allocation (1/3)
> Considering one cell with the following
configuration:
• 4 TRXs in the DCS1800 band
• PS_PREF_BCCH_TRX = 0
• NB_TS_MPDCH = 0
> In the next slide, find the rank of each TRX
Time allowed:
10 minutes
© Alcatel 126
2.5 Exercises B9
TRX_PREF_MARK
0 1 2 3 4 5 6 7
0 TRX1 BCCH SDCCH
TRE G4 MP FR RANK= ?
1 TRX2 SDCCH
TRE G3 DR RANK= ?
0 TRX3
TRE G4 MP FR RANK= ?
1 TRX4
TRE G3 DR RANK= ?
Back
© Alcatel 127
2.5 Exercises B9
> Inputs:
• NB_TS = 14, AV_USED_CS=0, AV_USED_PS=11
• MIN_SPDCH=0
• MAX_SPDCH=14
• MAX_SPDCH_HIGH_LOAD=2
• HIGH_TRAFFIC_LOAD_GPRS=80%
• THR_MARGIN_PRIO_PS=10%
> Find the value of
• MARGIN_CS, MARGIN_PRIORITY_PS
• MAX_SPDCH_LIMIT_CS, MAX_SPDCH_LIMIT_PS
Time allowed: • MAX_SPDCH_LIMIT
30 minutes > Any Remark?
> Propose some new parameter values to fix this
non-optimal setting
Back
> MARGIN_CS = Max[MARGIN_PRIORITY_CS ; AV_UNUSED_TS/2]

> Where
• AV_UNUSED_TS = NB_TS – AV_USED_CS_TS – Max[AV_USED_PS_TS ; MIN_SPDCH]
• MARGIN_PRIORITY_CS = THR_MARGIN_PRIO_CS*(NB_TS – MAX_SPDCH_HIGH_LOAD)/100
• Where
– THR_ MARGIN_PRIO_CS = 100 – HIGH_TRAFFIC_LOAD_GPRS
> MARGIN_PRIORITY_PS = THR_ MARGIN_PRIO_PS * MAX_SPDCH_HIGH_LOAD
> MAX_SPDCH_LIMIT_CS = RoundDown[NB_TS - AV_USED_CS_TS - MARGIN_CS]
> MAX_SPDCH_LIMIT_PS = RoundUp[AV_USED_PS_TS + MARGIN_PRIORITY_PS]
> If MAX_SPDCH_LIMIT_CS >= MAX_SPDCH_HIGH_LOAD then

• MAX_SPDCH_LIMIT = Min[MAX_SPDCH ; MAX_SPDCH_LIMIT_CS]
> Else
• if MAX_SPDCH_LIMIT_CS > MAX_SPDCH_LIMIT_PS then
– MAX_SPDCH_LIMIT = Min[MAX_SPDCH ; MAX_SPDCH_LIMIT_CS]
• Else
– MAX_SPDCH_LIMIT = Min[MAX_SPDCH_HIGH_LOAD ; MAX_SPDCH_LIMIT_PS]
© Alcatel 128
2.5 Exercises B9
TBF Radio Resources Allocation and Re-allocation (1/5)
> GPRS allocation on BCCH TRX (7 PDCHs are allocated)
• UL TBFs 1 to 11 are established one after the other
• It is assumed that a concurrent DL TBF is established
after the UL, and before the next UL
• All transfers are deemed DL biased
• Inputs:
– BCCH TRX, 1 unique SPDCH group
– NB_TS_MPDCH = 0
– MAX_XX_TBF_PER_SPDCH = 5
– En_Fast_Initial_GPRS_Access = disabled
– The MS GPRS multislot class is given below:
Time allowed:
20 minutes
Back
© Alcatel 129
2.5 Exercises B9
> Fill in the initial TBF allocation TS mapping UL/DL
DL
UL
© Alcatel 130
2.5 Exercises B9
> GPRS/EGPRS allocation case:
• Cell with 2 PS capable TRXs:
– TRXa: EGPRS capable, SPDCH group = TS0 to TS7
– TRXb: non-EGPRS capable, SPDCH group = TS0 to TS7
– Ordered TRX list: TRXa > TRXb
• En_Fast_Initial_GPRS_Access = enabled
• MIN_PDCH = 1
• NB_TS_MPDCH = 0
• MAX_GPRS_CS = CS-3;
• MAX_EGPRS_MCS = MCS-6
Time allowed: • Default MS multislot class = 4 + 1
20 minutes • All the MSs are 4 + 1 MSs
Back
© Alcatel 131
2.5 Exercises B9
• MS constraints:
0 1 2 3 4 5 6 7
Rx Rx Rx Rx Mx
DL
Ttb Tra
Tx
UL
0 1 2 3 4 5 6 7
• Consecutive establishments:
– MSa: GPRS UL TBF followed by DL TBF
– MSb: EGPRS UL TBF followed by DL TBF
– MSc: GPRS UL TBF followed by DL TBF
Time allowed: – MSd: EGPRS UL TBF followed by DL TBF
• Bias = DL
20 minutes
© Alcatel 132
2.5 Exercises B9
> Fill in the initial TBF allocation TS mapping UL/DL
PDCH 0 1 2 3 4 5 6 7 Rank
TRXa UL
1
EGPRS
DL
TRXb UL 2
GPRS
DL
© Alcatel 133
2.5 Exercises
DL TBF Release Routine (1/2)
> DL TBF routine in acknowledged mode
• Fill in the blanks in the diagram of a DL TBF
displayed on the next slide:
– name of the timers “T_?????”
– states of the DL TBF? ACTIVE, DELAYED,
RELEASED
Time allowed:
10 minutes
© Alcatel 134
2.5 Exercises
DL TBF Release Routine (2/2)

Back
© Alcatel 135
3 RADIO LINK CONTROL B9
© Alcatel 136
> Objective: to be able to describe the algorithms
of Radio Link Control and the related parameters
> Program:
3.1 GPRS CS Adaptation
3.2 EGPRS MCS Adaptation Modified B9
3.3 RLC Blocks Retransmission Modified B9
3.4 UL Power Control
3.5 NC0 Cell Selection and Reselection Modified B9
3.6 NC2 Cell Reselection Modified B9
3.7 Flow Control at the Gb Interface
3.8 Radio Link Supervision
3.9 Exercises
© Alcatel 137
3 RADIO LINK CONTROL
© Alcatel 138
Introduction – GPRS and EGPRS
> The MFS decides the UL and DL changes of coding scheme
> CS adaptation is enabled by means of 2 parameters:
• EN_CS_ADAPTATION_ACK
• EN_CS_ADAPTATION_NACK
> These parameters apply to both GPRS and EGPRS TBFs
> GPRS
• 4 coding schemes: CS-1 to CS-4
• Only changes between consecutive CSs can occur
• Based on RXQUAL and I_LEVEL_TNi (interference level)
> EGPRS
• 9 modulation and coding schemes: MCS-1 to MCS-9
• Changes between any MCS can occur
• Based on MEAN_BEP and CV_BEP
> CS-1: 20 useful bytes per RLC block.

> MCS-1: 22 useful bytes per RLC block.

> MCS-7: 2x56 useful bytes per RLC block.
> Only changes between consecutive CSs can occur, except in case of defense mechanism, see “Defense procedure”
slide.
© Alcatel 139
Principle
> The CS is adapted according to
• QUALITY reporting
• I_LEVEL_Tni, only for DL TBF
– based on a comparison between the received level and the interference level
• BLER, only for DL TBF
– when I_LEVEL_Tni is not available
> for DL TBF:
• The MS makes measurements on all the received blocks on all the PDCHs
• The MS reports measurements in the “Packet DL Ack/Nack” messages
• Then, the MFS computes long term and short term averages
> for UL TBF:
• The BTS makes quality measurements on all TSs for each block sent by the MS
• Then the MFS computes long term and short term averages on all TSs
© Alcatel 140
QUALITY Averaging in the MFS
> DL / UL TBF = 2 averages are computed:
• Short term average AV_RXQUAL_ST
AV_RXQUAL_STn+1 = (1 - 1 / zn+1) * AV_RXQUAL_STn + (1 / zn+1) *
RXQUALn,
with zn+1 = αST∆tn * zn + 1,
and αST = (1 - β)(1 / CS_AVG_PERIOD_ST)
• Long term average AV_RXQUAL_LT

AV_RXQUAL_LTn+1 = (1 - 1 / yn+1) * AV_RXQUAL_LTn + (1 / yn+1) *
RXQUALn,
with yn+1 = αLT∆tn * yn + 1,
and αLT = (1 - β)(1 / CS_AVG_PERIOD_LT)
>In the formula above:

•RXQUALn is the RXQUAL value reported by the MS in the nth PACKET DL ACK/NACK message.
•∆tn is the time difference in seconds between the (n-1)th and the nth PACKET DL ACK/NACK messages, therefore
depending on DL_ACK_PERIOD parameter value, on the nb of PDCHs used by the MS and on the traffic of the other
MSs multiplexed on these PDCHs.
•AV_RXQUAL_STn (respectively AV_RXQUAL_LTn) is the value of AV_RXQUAL_ST (respectively AV_RXQUAL_LT) after

the nth PACKET DL ACK/NACK message.
•β is a hard coded end equal to 0.9.
>Remark: the initial value of yn and zn is 0.
> 1/CS_AVG_PERIOD_LT and 1/CS_AVG_PERIOD_ST correspond to forgetting factors: number of seconds in the past
above which Quality measurements are considered as too old to be taken into account in the average.
> Default values are: CS_AVG_PERIOD_ST = 0.32 s
CS_AVG_PERIOD_LT = 2 s
both of them cannot be set at OMC-R level.
© Alcatel 141
AV_SIR Computation in the MFS
> Interference level averaged by the MS
• γCH,n = (1-d) * γCH,n-1 + d * SSCH,n
• d is the forgetting factor = d = 1/ MIN(n, N_AVG_I)
• SSCH,n is the interference measurement at iteration n
> I_LEVEL_TNi computed by the MS and sent to the MFS
• I_LEVEL_TNi = 0 when γCH > C
• I_LEVEL_TNi = 1 when C-2dB < γCH <= C
• I_LEVEL_TNi = 2 when C-4dB < γCH <= C-2dB
• Etc.
• I_LEVEL_TNi = 14 when C-28dB < γCH <= C-26dB
• I_LEVEL_TNi = 15 when γCH <= C-28dB
> AV_SIR = average value of I_LEVEL_TNi of all assigned DL TS i
> C_VALUE and I_LEVEL_TNi measurements are already averaged with an exponential filter in the MS. Therefore,
additional averaging is not needed, which reduces the complexity, i.e., AV_SIRn = I_LEVEL_TNin where n is the number of
the packet downlink Ack/Nack message.
>For more details about measurements and averages performed by the MS, see 3GPP 05.08.
© Alcatel 142
DL CS Adaptation (1/4)
> Functional process
MS MFS
Packet DL Ack/Nack
(RXQUAL, I_Level_TNi)
Packet DL Ack/Nack
(RXQUAL, I_Level_TNi)
Averaging
- AV_RXQUAL_ST
- AV_RXQUAL_LT
- AV_SIR
O&M threshold
and hysteresis Link current CS
adaptation
new CS
© Alcatel 143
> Threshold comparison when I_LEVEL_TNi are reported
Current Increasing the coding scheme number Decreasing the coding scheme number
coding
scheme (CSi ◊ CSi+1) (CSi ◊ CSi-1)
CS-1 AV_RXQUAL_LT < CS_QUAL_DL_1_2_X_Y Not possible
AV_RXQUAL_LT > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_LT

CS-2 AV_RXQUAL_LT < CS_QUAL_DL_2_3_X_Y OR
AV_RXQUAL_ST > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_ST
AV_RXQUAL_LT < CS_QUAL_DL_3_4_X_Y AV_RXQUAL_LT > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT
CS-3 AND OR
AV_SIR > CS_SIR_DL_3_4_X_Y AV_RXQUAL_ST > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_ST
CS-4 Not possible AV_SIR < CS_SIR_DL_3_4_X_Y + CS_SIR_HST_DL
• X = FH or NFH
• Y = ACK or NACK
>AV_RXQUAL_ST is a short term average whereas AV_RXQUAL_LT is a long term average. The short term average is
used to react quickly in case of fast degradation of the radio conditions.
>X = FH or NFH: two thresholds are available for hopping and non-hopping TRXs.
>Y = ACK or NACK: two thresholds are available for RLC acknowledged and unacknowledged modes.
> The thresholds should be chosen so that:

• CS_HST_DL_ST > CS_HST_DL_LT > 0
© Alcatel 144
> Threshold comparison when I_LEVEL_TNi are NOT reported
coding
CS-1 AV_RXQUAL_LT < CS_QUAL_DL_1_2_X_Y Not possible
AV_RXQUAL_LT > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_LT

CS-2 AV_RXQUAL_LT < CS_QUAL_DL_2_3_X_Y OR
AV_RXQUAL_ST > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_ST
AV_RXQUAL_LT < CS_QUAL_DL_3_4_X_Y AV_RXQUAL_LT > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT
CS-3 AND OR
CS3_BLER < CS_BLER_DL_3_4 AV_RXQUAL_ST > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_ST
CS-4 Not possible CS4_BLER > CS_BLER_DL_4_3
• X = FH or NFH
• Y = ACK or NACK
> As it has been observed (in the Alcatel labs during the B8 release validation) that some MSs do not report any
interference measurements when the BCCH carrier is included in the frequency hopping sequence of the allocated
PDCH, the algorithm described above is slightly modified in the MR2 version of the B8 release.
> A new triggering condition is used for the CS change between CS3 and CS4. This new triggering condition shall be
applied only to the TBF that do not report any interference level measurements. Each time a Packet DL Ack/Nack
message is received:
• either it contains no interference measurement and the new algorithm is applied,
• or it contains interference measurements and the standard algorithm is applied.
> With the new algorithm, the interference level is replaced by the BLER (RLC BLock Error Rate):
• the CS3 BLER is used for a CS change from CS3 to CS4,
• the CS4 BLER is used for a CS change from CS4 to CS3.
> Remarks:
• Case of a DL TBF with PDCH allocated on the BCCH TRX and no frequency hopping on the BCCH TRX: the MS
does not report any interference level measurement in the Packet DL Ack/Nack message (no interference
measurement on the BCCH carrier).
• Case of a DL TBF with PDCH having the BCCH carrier belonging to the frequency hopping sequence: depending
on MS implementation, some MSs may not report any interference measurement (behavior observed in the Alcatel
labs during the B8 release validation).
© Alcatel 145
AV_RXQUAL_LT
> Summary
7
CS-1
CS_QUAL_DL_1_2_X_Y+ CS_HST_DL_LT
CS-1 or CS-2 (hysteresis)
CS_QUAL_DL_1_2_X_Y
CS-2
CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT
CS_QUAL_DL_2_3_X_Y
C S_QUAL_DL_3_4_X_Y
CS-3
CS-4
CS-3 or
0 CS-4 AV_SIR
(hysteresis)
0 15
CS_SIR_DL_3_4_X_Y CS_SIR_DL_3_4_X_Y
+ CS_SIR_HST_DL
BLER
100% CS_BLER_DL_3_4 CS_BLER_DL_4_3 0%
> The change from CS-3 to CS-4 is not only based on AV_RXQUAL_LT for the two following reasons:
• RXQUAL range only goes down to 0.2%. However, the change of the coding scheme from CS-3 to CS-4 will
probably have to be done for even lower values. Indeed, when the coding scheme is CS-4, in static (AWGN), a
BLER of 0.1 (typical value of the BLER threshold to change from CS-3 to CS-4) is obtained for a raw BER of 1-(1-
0.1)1/456 = 2.10-4. This raw BER would be larger in multipath channels but is likely to remain below 0.2%. This
means that CS_QUAL_DL_3_4 should be close to 0 and that a condition based on RXQUAL is not sufficient to
change the coding scheme from CS-3 to CS-4.
• If the changes from CS-3 to CS-4 and from CS-4 to CS-3 are based on different metrics, a Ping-Pong effect may
occur. Indeed, it may happen that the conditions to change from CS-3 to CS-4 and CS-4 to CS-3 are
simultaneously true in some situations.
© Alcatel 146
UL CS Adaptation (1/3)
MS BTS MFS
UL RLC block (RXQUAL)
UL RLC block
RXQUAL
measurement
UL RLC block (RXQUAL)
Averaging
- AV_RXQUAL_ST
- AV_RXQUAL_LT
O&M threshold
and hysteresis Link current CS
adaptation
new CS
© Alcatel 147
> Threshold comparison
coding
CS-1 AV_RXQUAL_LT < CS_QUAL_UL_1_2_X_Y Not possible
AV_RXQUAL_LT > CS_QUAL_UL_1_2_X_Y + CS_HST_UL_LT

CS-2 AV_RXQUAL_LT < CS_QUAL_UL_2_3_X_Y OR
AV_RXQUAL_ST > CS_QUAL_UL_1_2_X_Y + CS_HST_UL_ST
CS-3 AV_RXQUAL_LT < CS_QUAL_UL_3_4_X_Y OR
CS-4 Not possible OR
• X = FH or NFH
• Y = ACK or NACK
>AV_RXQUAL_ST is a short term average whereas AV_RXQUAL_LT is a long term average. The short term average is
used to react quickly in case of fast degradation of the radio conditions.
>X = FH or NFH: two thresholds are available for hopping and non-hopping TRXs.
>Y = ACK or NACK: two thresholds are available for RLC acknowledged and unacknowledged modes.
> The thresholds should be chosen so that:

• CS_HST_UL_ST > CS_HST_UL_LT > 0
© Alcatel 148
> Summary
AV_RXQUAL_LT
CS-1
CS_QUAL_UL_1_2_X_Y + CS_HST_UL_LT
CS_QUAL_UL_1_2_X_Y
CS-2
CS_QUAL_UL_2_3_X_Y
CS-3
CS_QUAL_UL_3_4_X_Y
CS-4
0 AV_SIR
0 15
> In the uplink, the RXQUAL is available in CS-4 and the SIR measurements are not reported by the BTS to the MFS so
far. Therefore, it is also possible to use RXQUAL measurements to change the coding scheme from CS-3 to CS-4 or from
CS-4 to CS-3, contrary to the downlink algorithm, where the SIR was used.
© Alcatel 149
Execution
> UL TBF:
• the CS to be used is indicated to the MS during the establishment phase
• if a CS adaptation is decided by the MFS during the transfer phase, a
PACKET UL ACK/NACK message is sent immediately to the MS
> DL TBF:
• if a CS adaptation is decided by the MFS during the transfer phase, the
MFS modifies the CS
© Alcatel 150
Defense Procedure
> In a DL TBF:
If the number of PACKET DL ACK/NACK messages consecutively lost from
the MS on the radio interface goes over TBF_CS_DL, the coding scheme is
changed to CS-1
> In a UL TBF:
If the number of radio blocks consecutively not decoded goes over the
threshold Nb_allocated_TS x TBF_CS_UL, the coding scheme is changed to
CS-1
> In both cases, the CS must not be changed again before

TBF_CS_PERIOD RLC blocks are transmitted
>TBF_CS_DL = 6 (Alcatel recommended value) and it can be set at OMC-R level.

>TBF_CS_UL = 32 (Alcatel recommended value) and it can be set at OMC-R level.
>TBF_CS_PERIOD = 20 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 151
Initial Coding Scheme
> The initial CS at TBF establishment is given by the cell parameters:
• TBF_DL_INIT_CS for a DL TBF & TBF_UL_INIT_CS for a UL TBF
– Range = CS-1, CS-2, CS-3, CS-4
– Default value = CS-2
• T_DL_GPRS_MeasReport: the time period to request for a “Packet
Downlink Ack/Nack” with measurements
– Range: from 60 to 3000 ms
– Default value = 400 ms
> The initial CS and CS changes are limited by the cell parameter
MAX_GPRS_CS
– Range = CS-2, CS-3, CS-4
– Default value = CS-2
Exercise
> Rules:
• TBF_DL_INIT_CS < MAX_GPRS_CS
• TBF_UL_INIT_CS < MAX_GPRS_CS
> When a new LLC PDU is received and the downlink transfer is resumed, the timer defined by CS_MAX_IDLE_PERIOD
shall be checked. If it has not expired, then the coding scheme or modulation and coding scheme of the previous DL TBF
shall be re-used.
© Alcatel 152
3.2 EGPRS MCS Adaptation
© Alcatel 153
Impact of the Output Power – DL case
> The Average Power Decrease (APD)
• = max(0, modulation_delta_power - |BS_TXPWR_MAX|)
• Used in the MCS adaptation
49
48
47
TRE output power (dBm)
46
45 APD (dB)
44 8-PSK attenuation (dB)
43 8-PSK TRE power (dBm)
42 GMSK TRE power (dBm)
41 GMSK power in the cell (dBm)
40 Max GMSK power in the cell (dBm)
39 Max Power in the cell (dBm)
38
37
36
35
TRE
TRE 1
1 TRE
TRE 22 TRE
TRE 3
3
>CAUTION: animated slide.

>APD: Average Power Decrease
• The back-off between average GMSK and 8-PSK output power comes from physics since 8-PSK is a non-
constant envelope modulation unlike GMSK.
• As a consequence, power amplifiers can not be used at their maximum power. This results in a difference
between mean output powers for GMSK and 8-PSK modulations.
> Output power handling

• The BTS sets all the TREs which transmit GMSK output powers at the same level which is the minimum value
among the maximum TRE output power in a sector and in a given band.
• On a TRE, the maximum GMSK output power is higher than the maximum 8-PSK output power.
• An O&M parameter (BS_TXPWR_MAX) allows a static power reduction of the maximum GMSK output power of
the sector.
• The TRE transmit power in 8-PSK shall not exceed the GMSK transmit power in the sector.
• The BTS determines for each TRE, the difference between the 8-PSK output power of the TRE and the GMSK
output power of the sector (8-PSK delta power).
• According to the 8-PSK delta power value, a TRE is called “High Power” or “Medium Power”.
• When a GCH channel is activated, the BTS sends the 8-PSK delta power to the MFS.
Together with BS_TXPWR_MAX (static power reduction), the 8-PSK delta power allows the MFS to
determine:
– a possible attenuation (BS_TX_PWR) for the 8-PSK DL RLC block emission, in order not to exceed the
GMSK power of the sector (for GMSK DL RLC block, the attenuation is BS_TXPWR_MAX).
– an Average Power Decrease which is the difference between the 8-PSK output power and the GMSK
output power after having taken into account BS_TXPWR_MAX. The Average Power Decrease is
taken into account in the link adaptation tables.
© Alcatel 154
Impact of the Output Power – UL case
> The APD of a mobile station is the difference between the maximum
output power in GMSK and the maximum output power in 8-PSK
> The maximum output powers are known by "GMSK Power Class" and "8-
PSK Power Class" fields of the MS Radio Access capability
> Examples of APD in case of GSM 900 and GSM 850:
8-PSK: Power Class E1 8-PSK: Power Class E2 8-PSK: Power Class E3
Max. output power = 33 dBm Max. output power = 27 dBm Max. output power = 23 dBm
GMSK: Power Class 2

APD = 6 APD = 10 APD = 10
Max. output power = 39 dBm
GMSK: Power Class 3

APD = 4 APD = 10 APD = 10
GMSK: Power Class 4

APD = 0 APD = 6 APD = 10
GMSK: Power Class 5

APD = 0 APD = 2 APD = 6
© Alcatel 155
Measurement Reporting (1/2)
> MEAN_BEP
• Average Bit Error Probability
• Range
– From 0 to 31
– MEAN_BEP = 0 means actual BEP > 25%
– MEAN_BEP = 31 means actual BEP < 0.025%
> CV_BEP
• Average coefficient of variation of the Bit Error Probability
• Range
– From 0 to 7
– CV_BEP = 0 means [1.75 < actual CV_BEP < 2.00]
– CV_BEP = 7 means [0.00 < actual CV_BEP < 0.25]
>CV_BEP0: 2.00>CV_BEP>1.75 CV_BEP4: 1.00>CV_BEP>0.75

© Alcatel 156
Measurement Reporting (2/2)
> The MCS is adapted according to MEAN_BEP and CV_BEP reporting
(based on the Bit Error Probability)
• For a DL TBF:
– The MS makes MEAN_BEP and CV_BEP measurements on all the received
blocks the header of which has been well decoded
– The MS computes MEAN_BEP and CV_BEP averages
– Based on the forgetting factor principle
» The BEP_PERIOD cell parameter is used to compute the
forgetting factor
– The MS reports MEAN_BEP and CV_BEP averages in the “EGPRS Packet DL
Ack/Nack” messages
• For a UL TBF:
– The BTS makes MEAN_BEP and CV_BEP measurements on all the received
blocks the header of which has been well decoded
> For more details about MEAN_BEP and CV_BEP averages performed by the MS, refer to 3GPP 05.08.
> Raw measurements on a radio block basis

• For EGPRS (that is during an EGPRS DL TBF), the MS shall calculate the following values, for each radio block (1
radio block = 4 bursts) addressed to it (the DL TBF TFI contained in the radio block must be decoded):
– Mean Bit Error Probability (BEP) of a radio block:
1 4
MEAN _ BEPblock = ∑ BEPburst i
4 i =1
• Coefficient of variation of the Bit Error Probability of a radio block:
2
1 4  1 4 
∑ 
3 k =1 
BEPburst k − ∑
4 i =1
BEPburst i 

CV _ BEPblock = 4
1
∑ BEPburst i
4 i =1
• In the above equations, the BEP is measured on a burst basis by the MS before channel decoding.
> Averaging of the raw measurements on a TS basis

• The raw measurements made by the MS on a radio block basis are averaged by the MS per TS (TN in the below
equations) and per modulation type (GMSK
x n (MCS1 to MCS4), 8-PSK (MCS5
x n to MCS9)) as follows:
MEAN_BEP_TN n = (1 − e ⋅ ) ⋅ MEAN_BEP_TN n −1 + e ⋅ ⋅ MEAN_BEPblock, n
– Rn Rn
xn x
CV_BEP_TNn = (1 − e ⋅ ) ⋅ CV_BEP_TNn −1 + e ⋅ n ⋅ CV_BEPblock,n
– Rn Rn
R n = (1 − e) ⋅ R n −1 + e ⋅ x n , R −1 = 0
– with (Rn gives the reliability of the averaged quality
parameters)
• In the above equations:

– n is the iteration index, incremented for each DL radio block,
– e is a forgetting factor and is calculated according to the BEP_PERIOD cell parameter,
SEE NEXT SLIDE
© Alcatel 157
DL MCS Adaptation (1/2)
MS MFS
EGPRS Packet DL Ack/Nack

(Mean_BEP, CV_BEP)
IR APD Modulation
type
current MCS Link link adapatation

adaptation tables
new MCS
– xn denotes the existence of quality parameters for the nth block, i.e. if the radio block is intended for
this MS. xn values 1 and 0 denote the existence and absence of quality parameters, respectively.
> Measurements reporting

• An MS shall report the overall MEAN_BEP and CV_BEP (instead of reporting the RXQUAL and SIGN_VAR
values) per modulation type (that is GMSK_MEAN_BEP, GMSK_CV_BEP and/or 8-PSK_MEAN_BEP, 8-
PSK_CV_BEP depending on the received blocks since the last channel quality report sent to the network) averaged
over all allocated channels (time slots) as follows:
∑R (j)
n ⋅ MEAN_BEP_TN (j)
n ∑R (j)
n ⋅ CV_BEP_TN (j)
n
= =
j j
– MEAN_BEPn , CV_BEPn
∑ j
(j)
Rn ∑Rj
(j)
n
– where n is the iteration index at reporting time and j the TS number.
• The MS reports the Mean_BEP and CV_BEP values to the MFS in the Channel Quality Report included in the
EGPRS Packet DL Ack/Nack and Packet Resource Request messages.
•The MS can report 32 different Mean_BEP values (MEAN_BEP_0 to MEAN_BEP_31). The mapping between the
calculated Mean_BEP value (linear scale) and the reported Mean_BEP value (logarithmic scale) depends on the
used modulation (two mapping tables are given in the 05.08 GSM recommendation: one for GMSK and one for
8-PSK).
•The MS can report 8 different CV_BEP values (CV_BEP_0 to CV_BEP_7). The mapping between the calculated
and the reported values is identical for the GMSK and 8-PSK modulations.
> Measurements and reporting at BTS side

• The BTS measures for each UL burst the BEP and calculates for each UL radio block (4 bursts) the Mean_BEP
and the CV_BEP = Std_BEP / Mean_BEP. The Mean_BEP and the CV_BEP are reported on a radio block basis by
the BTS to the MFS.
© Alcatel 158
DL MCS Adaptation (2/2)
> In RLC acknowledged mode, the MFS applies a given MCS taking into
account:
• Current MCS:
– MCS-1 to MCS-4 in GMSK
– MCS-5 to MCS-9 in 8-PSK
• Average Power Decrease: APD set = [0, 1, 3, 4, 5, 6, 8, 10]
• MS OUT OF MEMORY state
– = Off then LA tables with IR are used
– = On then LA tables without IR (Type I ARQ) are used
> In RLC unacknowledged mode, the MFS applies a given MCS taking into
account:
• Current MCS:
– MCS-5 to MCS-9 In 8-PSK
> Each combination of these criteria corresponds to a specific LA table
> LA = Link Adaptation. IR = Incremental Redundancy, also called Type II ARQ (Automatic ReQuest for repetition).
>Extract of an LA table when APD=0dB, Type 1 ARQ, 8-PSK table: if the current MCS belongs to {5,6,7,8,9}
CV_BEP If the effective APD (=max(0,
0 1 2 modulation_delta_power
3 4 5 6 7 - |BS_TX_PWR_Max|) does not
belong to the APD set which is described above, then the APD
0 5 5 5 5 1 1 1 1
value in the set which is immediately higher than the
1 5 5 5 received
5 1 APD. 1 2 2
2 5 5 5 5 1 2 2 2 e.g., if effective APD = 0.7 dB then APD = 1 dB
3 5 5 5 5 2 2 2 3
4 5 5 5 5 5 2 3 3
5 5 5 5 5 5 3 3 3
6 5 5 6 5 5 5 3 3
7 5 5 6 5 5 5 3 3
8 5 5 6 6 5 5 5 4
9 5 6 6 6 5 5 5 5
10 5 6 6 6 6 5 5 5
11 6 6 6 6 6 6 5 5
12 6 6 6 6 6 6 5 5
13 6 6 6 6 6 6 5 5
MEAN_BEP
14 7 6 6 6 6 6 6 6
15 7 6 6 6 6 6 6 6
16 7 7 6 7 6 6 6 6
17 7 7 7 7 7 6 6 6
18 7 7 7 7 7 7 7 7
19 7 7 7 7 7 7 7 7
20 7 7 7 7 7 7 7 7
21 7 7 7 7 7 7 7 7
22 7 8 8 8 8 8 8 8
23 8 8 8 8 8 8 8 8
24 8 8 8 8 8 8 8 8
© Alcatel 159
RLC ACK Mode: New DL MCS Value Determination
> Evaluated every “EGPRS Packet DL Ack/Nack” message
> If MCS indicated by LA tables <= current MCS
• Then New MCS = MCS indicated by LA tables
> Else New MCS = MCS indicated by LA tables with the modified criteria
• MEAN_BEP = max[(current MEAN_BEP)-2, 0]
• CV_BEP = current CV_BEP
> Example:
• The TBF mode is acknowledged: use of the RLC acknowledged mode algorithm and tables,
• MS OUT OF MEMORY = On: use of the group of tables for Type I ARQ (without IR),
• APD = 0 dB: use of the group of tables for APD = 0 dB (for each APD value, there is a GMSK table (for MCS =
MCS1, … , MCS4) and a 8_PSK table (for MCS = MCS5, …, MCS9)),
• current MCS = MCS6: use of the 8_PSK table for APD = 0 dB.
•If the MS reports the (MEAN_BEP = 3, CV_BEP = 2) values in the last Packet DL Ack/Nack message, the link
adaptation table indicates MCS5. As MCS5 < MCS6, the commanded MCS is MCS5.
•If the MS reports the (MEAN_BEP = 23, CV_BEP = 3) values in the last Packet DL Ack/Nack message, the link
adaptation table indicates MCS8. As MCS8 > MCS6, the commanded MCS is the MCS corresponding to the
(MEAN_BEP = 23 – 2 = 21, CV_BEP = 3) couple in the link adaptation table, that is MCS7.
© Alcatel 160
RLC NACK Mode: New DL MCS Value Determination
> Evaluated every “EGPRS Packet DL Ack/Nack” message
> If MCS indicated by LA tables <= current MCS
• Then New MCS = MCS indicated by LA tables
> Else New MCS = MCS indicated by LA tables with the following criteria
• MEAN_BEP = max[(current MEAN_BEP)-8, 0]
• CV_BEP = current CV_BEP
> Exception: if
– Current MEAN_BEP = 31
– AND Current CV_BEP = 7
– AND Current MCS belongs to {MCS-1, MCS-2, MCS-3, MCS-4)
• Then New MCS = MCS5
Exercise
> The margin of 8 for the hysteresis has been chosen to have a long term average weighted BER close to 0.001. With
this value, the MCS selected can never be higher than 7 in good radio conditions.
© Alcatel 161
UL MCS Adaptation (1/2)
MS BTS M FS
UL RLC b lock (CV_ BEP, Mean_BEP)
UL RLC b lock
CV_BEP, M ean_BEP
computation
UL RLC b lock (CV_ BEP, Mean_BEP)
Aver aging
APD
current MCS Link lin k adapatation

adaptation tables
new MCS
> The MFS calculates average values (Mean_BEP and CV_BEP) each time a radio block is received from the BTS. Then
the MFS checks if an MCS change is needed using internal tables. However, the first decision shall only be taken when
TBF_MCS_Period radio blocks have been received.
> The measurements performed by the BTS are averaged by the MFS as follows:
• yn+1 = e∆tn * yn +1 where e (forgetting factor) is equal to (1 - 0.9)(1 / MCS_AVG_PERIOD),
• Mean_BEPn+1 = (1 - 1 / yn+1) * Mean_BEPn + (1 / yn+1) * Mean_BEPblock n,
• CV_BEPn+1 = (1 - 1 / yn+1) * CV_BEPn + (1 / yn+1) * CV_BEPblock n
• MCS_AVG_PERIOD = 0,1s (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 162
3.2 EGPRS MCS Adaptation B9
UL MCS Adaptation (2/2)
> In RLC acknowledged mode, the MFS applies a given MCS taking into
account:
• Current MCS:
– MCS-5 to MCS-9 in 8-PSK
• APD of the MS: APD set = [0, 1, 3, 4, 5, 6, 8, 10]
• EN_IR_UL state
– = enabled then LA tables with IR are used
– = disabled then LA tables without IR (Type I ARQ) are used
> In RLC unacknowledged mode, the MFS applies a given MCS taking into
account:
• Current MCS:
– MCS-5 to MCS-9 In 8-PSK
> Each combination of those criteria corresponds to a specific LA table
> The same tables apply in the uplink as in the downlink.
© Alcatel 163
RLC ACK Mode: New UL MCS Value Determination
> Evaluated every 12 radio blocks (decision window)
> For each radio block, the MFS computes an indicated MCS (MCSind) according
to MEAN_BEP, CV_BEP and the appropriate LA table
> During the decision window:
• If MCSind > current MCS then N_sup = N_sup + 1
• If MCSind <= current MCS then N_inf = N_inf + 1
> At the end of the decision window:
• If N_inf > 6 and MCSindlast_block < current MCS
– Then New MCS = MCSindlast_block
• Else if N_sup > 6 and MCSindlast_block > current MCS
– Then New MCS = Max[current MCS, MCSindlast_block modified]
– Where MCSindlast_block modified is computed with the following criteria
» MEAN_BEP = Max[MEAN_BEPlast_block-2, 0]
» CV_BEP = CV_BEPlast_block
• Else, New MCS = current MCS
> The following complex algorithm is used by the MFS to determine the MCS to be used in RLC acknowledged mode:
• the MFS determines the MCS to be used every 12 radio blocks (decision window),
• during the decision window, for each received measurement (that is for each received radio block), the
averaged (Mean_BEP, CV_BEP) couple indicates a best MCS (called MCSind) according to the appropriate link
adaptation table. This best MCS is compared to the current MCS, and 2 counters (N_sup, N_inf) are maintained
(N_sup (respectively N_inf), is incremented by one when MCSind is higher (respectively lower) than the current
MCS) that gives, for the current decision window, the number of MCSind that are higher or equal to the current
MCS,
• at the end of the decision window, the decision process is as follows:
– the new MCS is determined according to the trend observed during the decision window (that is trend
towards upper MCS or trend towards lower MCS). It is considered that a trend towards upper
(respectively lower) MCS is observed if strictly more than half (that is 6) of the MCSind are higher
(respectively lower) than the current MCS,
– moreover, the new MCS is applied only if the last MCSind of the decision window corresponds to the
trend observed during the decision window (that is MCSindlast block > current MCS for a trend towards
upper MCS or MCSindlast block < current MCS for a trend towards lower MCS),
– finally, the new MCS is the MCSind of the last block (MCSindlast block) in case of trend towards a
lower MCS. In case of trend towards upper MCS, an hysteresis is applied on the measurements as the
new MCS in that case is equal to max(current MCS, MCSindlast block (max(Mean_BEP - 2, 0), CV_BEP)).
© Alcatel 164
RLC NACK Mode: New UL MCS Value Determination
> Evaluated every 12 radio blocks (decision window)
• If MCSindlast_block <= current MCS
– Then New MCS = MCSindlast_block
• Else
– Then New MCS = Max[current MCS, MCSindlast_block modified]
– Where MCSindlast_block modified is computed with the following criteria
» MEAN_BEP = Max[MEAN_BEPlast_block-8, 0]
» CV_BEP = CV_BEPlast_block
Exercise
© Alcatel 165
Defense Procedure
> In a DL TBF:
If the number of EGPRS PACKET DL ACK/NACK messages consecutively lost
from the MS on the radio interface goes over TBF_MCS_DL, the modulation
and coding scheme are changed to MCS-1
> In a UL TBF:
If the number of radio blocks consecutively not decoded goes over the
threshold Nb_allocated_TS x TBF_MCS_UL, the modulation and coding
scheme are changed to MCS-1
> In both cases, the MCS must not be changed again before
TBF_MCS_PERIOD RLC blocks are transmitted
>TBF_MCS_DL = 4 (Alcatel recommended value) and it can be set at OMC-R level.

>TBF_MCS_UL = 32 (Alcatel recommended value) and it can be set at OMC-R level.
>TBF_MCS_PERIOD = 20 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 166
Initial MCS
> The initial MCS at TBF establishment is given by the cell parameters:
• TBF_DL_INIT_MCS for a DL TBF & TBF_UL_INIT_MCS for a UL TBF
– Range for a DL TBF = from MCS-1 to MCS-9
– Range for a UL TBF = from MCS-1 to MCS-9 Modified B9
– Default value = MCS-3

• T_DL_EGPRS_MeasReport: the time period to request for a “EGPRS Packet
Downlink Ack/Nack” with measurements
– Values: from 60 to 3000 ms
– Default value = 200 ms
> The initial MCS and MCS changes are limited by the cell parameter
MAX_EGPRS_MCS
– Range = from MCS-2 to MCS-9
– Default value = MCS-9
>Rules:
•TBF_DL_INIT_MCS < MAX_EGPRS_MCS
•TBF_UL_INIT_MCS < MAX_EGPRS_MCS
> When a new LLC PDU is received and the downlink transfer is resumed, the timer defined by CS_MAX_IDLE_PERIOD
shall be checked. If it has not expired, then the coding scheme or modulation and coding scheme of the previous DL TBF
shall be re-used.
© Alcatel 167
3.3 RLC Blocks Retransmission
© Alcatel 168
New Modulation and Coding Schemes (1/2)
> Data rate per radio TS (RLC payload)
Scheme Modulation Maximum rate
(kbps)
GPRS
CS-4 GMSK 20
CS-3 GMSK 14.4
CS-2 GMSK 12
CS-1 GMSK 8
EGPRS
8-PSK modulation to MCS-9 8PSK 59.2
provide MCS-8 8PSK 54.4
higher data rates MCS-7 8PSK 44.8
MCS-6 8PSK 29.6 / 27.2 *
MCS-5 8PSK 22.4
GMSK modulation to ensure MCS-4 GMSK 17.6
a certain level of MCS-3 GMSK 14.8 / 13.6 *
performance in case of poor MCS-2 GMSK 11.2
radio conditions MCS-1 GMSK 8.8
* case of padding
> MCSs are defined only for the EGPRS packet data traffic channels (PDTCH). For all the EGPRS packet control
channels, the corresponding GPRS control channel coding is used (that is CS1 for the PACCH, PBCCH, PAGCH, PPCH
and downlink PTCCH).
© Alcatel 169
New Modulation and Coding Schemes (2/2)
> MCSs are divided into 4 families: A, A padding, B and C
GMSK 8-PSK
MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
Family
C 22 22 22
28 28 28 28 28
Family
B 28 28
Family 34+3 34+3 34+3 34 34

A
padding 34 34
37 37 37 37 37
Family
A
37 37
RLC data block 28 unit of payload (in bytes)
> The main GPRS imperfections are linked to:

• the design of the GPRS coding schemes which were designed independently from the others with their own data
unit.
• the fact that once the information contained in a radio block has been transmitted with a certain CS, it is not
possible via the Automatic ReQuest for repetition (ARQ) mechanism to retransmit with another CS.
–This could lead to the release of the TBF and to the establishment of a new one in order to transmit the
LLC frame.
> EGPRS coding schemes have been designed to offset this problem. Four MCS families have been created with for
each of them a basic unit of payload.
• This allows the re-segmentation of the RLC data blocks when changing of modulation and coding schemes
(within the same family).
–Example: if one MCS-6 radio block has not been received correctly by the receiver and if radio
conditions have degraded in the meantime, it is possible to re-send the same information in two radio
blocks with MCS-3 (more protection).
• The level of protection applied (MCS usage) in case of retransmissions is in line with the radio conditions.
> The different code rates within a family are achieved by transmitting a different number of payload units within one
radio block.
>When 4 payload units are transmitted, these are split into 2 separate RLC blocks (i.e., with separate sequence
numbers).
© Alcatel 170
3.3 RLC Blocks Retransmission B9
Automatic ReQuest for Repetition (ARQ)
> In RLC ACK mode, the retransmission can be performed using:
• Selective type I ARQ mechanism.
– The blocks which are not decoded are simply retransmitted
– Available since B6 release
– Another MCS from the same family can be used
• Type II hybrid ARQ mechanism (also called Incremental Redundancy (IR))
– The blocks which are not decoded are retransmitted
– Using or not another MCS of the same family
– Using a different Puncturing Scheme (PS)
– The non decoded block and the retransmitted one(s) are “soft
combined” to retrieve the right information
Appendix
– This applies only when the MS memory for IR is not full
– This can apply for both UL and DL EGPRS TBF Modified B9
> The type 2 ARQ mechanism or incremental redundancy (IR) is an ETSI function, mandatory for the EGPRS MS
receiver (downlink path) and optional for the BTS receiver (uplink path).
>The incremental redundancy is not used for the signaling blocks, the GPRS data blocks and the data blocks in RLC
unacknowledged mode. It is only used for the EGPRS data blocks in RLC acknowledged mode.
> In the type II ARQ mechanism (IR):

• the first emission of an RLC data block is done using a first puncturing scheme (PS1),
• in case of re-transmission of this RLC block, the transmitter uses the same MCS or an MCS of the same family
as the one used for the initial block. The re-segmentation of the RLC block may be performed or not,
• at the output of the demodulator, the receiver combines the information of soft bits corresponding to the first
transmission of the block and its different re-transmissions, thus increasing the decoding probability of the RLC
block.
• Remark: according to the 04.60 (RLC/MAC layers) GSM recommendation, the soft combining inside the MS
receiver is only performed between:
–an MCSx block and an MCSx block (that is the same MCS is used for the re-transmission),
–an MCS9 block and an MCS6 block (in that case the RLC data blocks carry the same number of
payload units),
–an MCS7 block and an MCS5 block (in that case the RLC data blocks carry the same number of
payload units).
© Alcatel 171
Type I ARQ Mechanism (1/2)
> MCS selection for retransmission of a DL or UL RLC data block
Commanded MCS (given by the link adaptation algorithm)
MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
MCS9 MCS9 MCS6 MCS6 MCS6 MCS3 MCS3 MCS3 MCS3 MCS3
(pad.) (pad.) (pad.) (pad.) (pad.) (pad.) (pad.)
Initial MCS6 MCS9 MCS6 MCS6 MCS6 MCS3 MCS3 MCS3 MCS3 MCS3
MCS MCS5 MCS7 MCS7 MCS7 MCS5 MCS5 MCS2 MCS2 MCS2 MCS2
>With the type 1 ARQ mechanism, the decoding of a re-transmitted RLC block does not use the previously transmitted
versions (not correctly received) of this RLC block. The decoding of an RLC data block is only based on the current
transmission.
>The type 1 ARQ mechanism is always used for the GPRS.
© Alcatel 172
Type I ARQ Mechanism (2/2)
> Example
MS
of a UL EGPRS TBF BSS
UL RLC data block B1, MCS4, PS1

B1 block not decoded by the BTS
Packet UL Ack/Nack (B1 not decoded)
Resegment bit set
UL RLC data block first part B1, MCS1, PS1
UL RLC data block second part B1, MCS1, PS1

Second part of B1 block not decoded by the BTS
Packet UL Ack/Nack (B1 not decoded) Resegment bit set
UL RLC data block first part B1, MCS1 , PS1
UL RLC data block second part B1, MCS1 , PS1
> The picture above shows the case of a UL EGPRS TBF where one block is not decoded by the BTS and is then re-
transmitted by the MS with a lower MCS in the same MCS family. In this example, the second part of the re-transmitted
block is not correctly decoded by the BTS. As it is not possible to indicate separately in the Packet Uplink Ack/Nack
message whether the first part of the block or the second part has been decoded, if one part is not received the MS will
retransmit again the two parts of the block.
© Alcatel 173
Type II ARQ Mechanism (1/3)
> The MCS used to re-transmit a DL RLC data block depends on:
• The initial MCS used to send this RLC data block
• The resegmentation allowed or not
– The DL resegmentation is allowed If EN_FULL_IR_DL = disabled
Modified B9 – The UL resegmentation is allowed If EN_RESEGMENTATION_UL= enabled
• The possible memory shortage in the MS (case of a DL EGPRS TBF)
– MS OUT OF MEMORY = On, in the EGPRS packet DL Ack/Nack message
• The MCS commanded by the link adaptation algorithm (refer to session
3.2 EGPRS MCS Adaptation)
> As IR is optional in UL, the feature can be enabled/disabled using the

BSS parameter EN_IR_UL NewB9
> The TRX manages the IR UL. Indeed, the TRX decodes the RLC/MAC header of all the UL RLC/MAC data blocks
received on each PDCH to know which TBF the RLC data block(s) pertain.
> For each TBF, the maximum number of different RLC data blocks stored is equal to the window size which depends
on the maximum number of RTSs used in uplink (512 for 4 TS).
> The TRX is able to store 4,000 RLC data blocks which have not been correctly decoded. If an RLC data block is
received with the same PS as an already received RLC data block belonging to the same TBF, only the last instance is
taken into account.
© Alcatel 174
> The following table is used to select the MCS if
• In DL, EN_FULL_IR DL = enabled and MS OUT OF MEMORY = off
• In UL, EN_RESEGMENTATION_UL = enabled
Commanded MCS (given by the link adaptation algorithm)
MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
N
IO
(pad.) (pad.) (pad.) (pad.) (pad.) (pad.) (pad.)
NT T
AT
ME OU
EG ITH
W
Initial
MCS MCS5 MCS7 MCS7 MCS7 MCS5 MCS5 MCS5 MCS5 MCS5 MCS5
S
RE
> In all the other cases, the table used for Type I ARQ is applied
>“In all the other cases” means:

•In DL, EN_FULL_IR_DL=disabled or MS OUT OF MEMORY=on.
•In UL, EN_RESEGMENTATION_UL=disabled.
© Alcatel 175
> The PS used to re-transmit an RLC data block depends on:
• If the selected MCS has not changed then
– The PS is changed in a cyclic way: PS1, PS2, PS3, PS1, etc.
• Else, the PS to be used is indicated in the table below:
Previous MCS New MCS Previous PS New PS
MCS9 MCS6 PS1 or PS3 PS1
PS2 PS2
MCS6 MCS9 PS1 PS3
PS2 PS2
MCS7 MCS5 Any PS1
MCS5 MCS7 Any PS2
All other combinations Any PS1
> PS1 is used in case of the first transmission of an RLC data block
Exercise
> If the selected MCS has not changed: if all the different punctured versions of the data block have been sent, the
procedure shall start over and PS1 shall be used, followed by PS2, then by PS3 (if available for the considered MCS), so
that the PS selection is cyclic.
© Alcatel 176
© Alcatel 177
Measurements
> The MS makes level measurements defined by the 05.08 GSM
recommendation:
• in Packet Idle Mode:
– BCCH of the serving cell (paging blocks monitored by the MS);
– if MPDCH established, measurement on PCCCH = received signal on
each paging block monitored, according to its DRX mode and paging
group
• in Packet Transfer Mode:
– behavior defined by the parameter PC_MEAS_CHAN broadcast on the
PBCCH (PSI1)
– PBCCH of the serving cell (or BCCH if no MPDCH)
– on all the blocks of the PDCH carrying the PACCH
>The MS uses DL level measurements to determine the power: open loop PC.
© Alcatel 178
Averaging
> Cn = a * (SSn + Pb) + (1-a) * Cn-1
• a is the forgetting factor:
– Packet Idle Mode: 1 / min(n, max(5, T_AVG_W / TDRX))
– TDRX = BS_PA_MFRMS (number of 51 multi-frame between 2 paging)
– Packet Transfer Mode: 1/ (6 * T_AVG_T) (BCCH)
or 1/ (12 * T_AVG_T)(PDCH)
• SSn is the measurement at iteration n:
– average level of block n in Packet Idle Mode and Packet Transfer Mode
(PDCH)
– level of the sample in Packet Transfer Mode (BCCH)
• Pb is a correcting factor relating to the power reduction value applied by
the BTS on a PCCCH and/or PDCH, to be compared with the output
power used on the BCCH
>Use of a recursive filtering to obtain an average level.
>Average levels calculated in Packet Idle Mode used in Packet Transfer Mode and vice versa: a proper average level is
available at the beginning of the transfer
>The respective values of the T_AVG_T and T_AVG_W averaging windows are broadcast on PSI1.
© Alcatel 179
MS Power
> The MS uses the same power during a radio block (4 bursts)
> MS power = min(Γ0 - Γch - α * (C + 48), Pmax)
• Γ0 = 39 dBm in GSM 900, 36 dBm in GSM 1800
• α and Γch are sent to the MS (α: SI 13, α and Γch: Packet UL and DL
assignment) and are tuned in order to obtain a given behavior
• Pmax is the maximum transmitted power, and is equal to:
– GPRS_MS_TXPWR_MAX_CCH if there is a PBCCH
– MS_TXPWR_MAX_CCH otherwise
• C is the average DL level calculated by the MS
> The MS power access on an RACH can be MS_TXPWR_MAX_CCH. In fact, the MS will use the first of the 2 values
listened on the cell broadcast information.
> The 05.08 GSM recommendation suggests to:
• use α = 1
• tune Γch in order to reach a given UL level (LEVUL) at the BTS side: Γch = Γ0 - 48 - LEVUL - PBTS (PBTS: BTS
power)
• explanation:
– Pm = Γ0 - Γch - α * (C + 48)
– Pm = LEVUL - LEVDL + PBTS
• When you fix α=1, you get a specific value for Γch, which is not usable for any value of α.
• Proceed by dichotomy to find the proper value of Γch
> Another possibility:

• if path balance: PBTS - Pm = Sm - SBTS (S: sensitivity)
• therefore: LEVDL - LEVUL = Sm - SBTS
• and Pm = Γ0 - Γch - α * (LEVUL + Sm - SBTS + 48)
• example with G3 BTS: Pm = Γ0 - Γch - α * (LEVUL + 57)
• possibility of tuning:
– power reduction when the UL level is higher than U_RXLEV_UL_P
– MS power not lower than 13/4 dBm in GSM 900/1800
© Alcatel 180
3.5 NC0 Cell Selection and Reselection
© Alcatel 181
Introduction
> 2 kinds of selection – reselection are implemented in the Alcatel BSS:
• NC0
– The MS performs autonomous cell reselection
– All the algorithms (criteria computation, triggering, target cell choice) are
implemented in the MS
– No measurement reporting
• NC2
– The network (MFS) controls the cell reselection
– All the algorithms (criteria computation, triggering, target cell choice) are
implemented in the MFS
– The MS sends periodically measurement reports
> The main important parameters involved in the cell selection and
reselection are broadcast in PSI3 & PSI3bis (if PBCCH) or in SI3 (if
BCCH)
> The GPRS neighboring cells list is identical to the GSM one
© Alcatel 182
Principles
> Procedures defined in the 05.08 GSM recommendation
> Cell selection:
• made using the C1 criterion as for GSM
> Cell reselection:
• made using the C1 and C2 criteria as for GSM if MPDCH not available
in the serving cell
• otherwise a specific C1 criterion as well as C31 & C32 criteria are
computed during the reselection procedure
– C31: signal level threshold criterion for Hierarchical Cell Structures (HCSs)
– C32: cell-ranking criterion
> In GSM
> C1 = A - Max (0,B) with:
• A = RLA_C - RXLEV_ACCESS_MIN
• B = MS_TXPWR_MAX_CCH - MS_TXPWR_MAX + POWER_OFFSET(1800)
> C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET(T) when Penalty_time<31
> C2 = C1 - CELL_RESELECT_OFFSET when Penalty_Time=31
> In GPRS ready and standby states, cell reselection is performed by the MS except for a class A MS while in dedicated
mode of a circuit-switched connection, in which case the cell is determined by the network according to the handover
procedures.
> For a class B MS which can combine GSM and GPRS states, C1 criterion is used when the MS simultaneously
attached to both the network and the MS is in Packet Idle Mode (refer to GSM 05.08).
© Alcatel 183
Selection
> Criteria computation:
• Without PBCCH
– C1 = (RLA_C – RXLEV_ACCESS_MIN) – max (0, MS_TXPWR_MAX_CCCH –
P)
– RLA_C: average DL level received
• With PBCCH
– C1 = (RLA_P – GPRS_RXLEV_ACCESS_MIN) – max (0,
GPRS_MS_TXPWR_MAX_CCCH – P)
– RLA_P: average DL level received
– P: power class of the MS
> Cell choice: the best cell is the cell with the highest C1
> C1 is the same as in GSM except that:

• A = RLA_P – GPRS_RXLEV_ACCESS_MIN: “listening capacity of MS in the cell”
• B = GPRS_MS_TXPWR_MAX_CCH – P: “talking capacity of MS in the cell”
• C1 shall be positive and as high as possible
> In Packet Idle Mode, the MS shall make one measurement for each BCCH carrier monitored every 4 seconds, as well
as more than one sample per second for each BCCH carrier.
> A list of 6 strongest cells shall be kept updated at a rate of at least one update per running average period.
>In Packet Transfer Mode, the MS shall monitor a list of 6 strongest non-serving cell BCCH carriers. It shall attempt to
check the BSIC for each of these 6 strongest cells at least once every 10 seconds.
© Alcatel 184
Reselection Criteria Computation Without PBCCH
> If CELL_RESELECT_PARAM_IND=not present then C2=C1 else:
• C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET(T)
(if PENALTY_TIME <> 31)
– if T > PENALTY_TIME, TEMPORARY_OFFSET(T)=0
– used to avoid locating on “transient cell”
– CELL_RESELECT_OFFSET used to favor a cell among others (e.g., micro-
cell vs. umbrella, once T > PENALTY_TIME)
• C2 = C1 - CELL_RESELECT_OFFSET
(if PENALTY_TIME = 31)
– CELL_RESELECT_OFFSET used to handicap some cells among others
>The same algorithm is used in case the MS is in GSM Idle Mode.
© Alcatel 185
Target Cell Choice Without PBCCH
> The MS triggers a cell reselection if:
• C1(serving) <0
and/or
• In Standby Mode
– C2(neighbor) > C2(serving) if cells belong to a same RA
– C2(neighbor) > C2(serving)+CELL_RESELECT_HYSTERESIS if cells from
different RAs
• In Ready Mode
– C2(neighbor) > C2(serving)+CELL_RESELECT_HYSTERESIS even if cells
belong to a same RA
© Alcatel 186
Reselection Criteria Computation with PBCCH (1/2)
> Serving cell:
• C31(serving) = RLA_P(serving) – HCS_THR(serving)
• C32(serving) = C1(serving)
> Neighboring cell:
• If C31_HYST=Yes,
– C31(neighbor)=RLA_P(neighbor) – HCS_THR(neighbor) – TO(neighbor)x
L(neighbor) - GPRS_CELL_RESELECT_HYSTERESIS
• else
– C31(neighbor) =RLA_P(neighbor) – HCS_THR(neighbor) – TO(neighbor)x
L(neighbor)
• C32 (neighbor) = C1 (neighbor) +
GPRS_RESELECTION_OFFSET(neighbor) – TO(neighbor)x (1-L(neighbor))
>C1 is the same as in GSM except that

•A = RLA_P – GPRS_RXLEV_ACCESS_MIN: “listening capacity of MS in the cell”
•B = GPRS_MS_TXPWR_MAX_CCH – P: “talking capacity of MS in the cell”
•C1 shall be positive and as high as possible
>C32:
•if C32_QUAL=1, positive GPRS_RESELECTION_OFFSET value shall only be applied to the neighboring cell
with the highest RLA_P value of those cells for which C32 is compared above.
•If GPRS_RESELECTION_OFFSET (neighbor) >0, the cell has a bonus to reselection.
•If GPRS_RESELECTION_OFFSET (neighbor) <0, the cell has a handicap for reselection.
>In Packet Idle Mode, the MS shall make one measurement for each BCCH carrier monitored every 4 seconds, as well
as more than one sample per second for each BCCH carrier.
>A list of 6 strongest cells shall be kept updated at a rate of at least one update per running average period.
>In Packet Transfer Mode, the MS shall monitor a list of 6 strongest non-serving cell BCCH carriers. It shall attempt to
check the BSIC for each of these 6 strongest cells at least once every 10 seconds.
© Alcatel 187
Reselection Criteria Computation with PBCCH (2/2)
> TO(neighbor) = GPRS_TEMPORARY_OFFSET(neighbor) x
H(GPRS_PENALTY_TIME(neighbor) – T(neighbor) )
dB
GPRS_TEMPORARY_OFFSET
> L(neighbor): GPRS_PENALTY_TIME Time
• Its value belongs to the relative PRIORITY_CLASS of the GPRS cell

• L=0 if PRIORITY_CLASS(neighbor) = PRIORITY_CLASS(serving)
• L=1 if PRIORITY_CLASS(neighbor) <> PRIORITY_CLASS(serving)
>Note: do not confuse the TO (T) Temporary Offset function and the GPRS_TEMPORARY_OFFSET parameter.
>The L factor is used to cancel the Temporary handicap given to the cell the MS is coming from when the cell has a
different priority class.
> PRIORITY_CLASS (HMI name) = GPRS_PRIORITY_CLASS (parameter name).

> PRIORITY_CLASS: Higher the parameter value, higher the priority.
© Alcatel 188
Target Cell Choice with PBCCH (1/2)
> The MS triggers a cell reselection if:
• C1(serving) <0
and/or
• the neighboring cell has better radio conditions (see next slide)
• among those cells that have the highest PRIORITY_CLASS
• among those cells that fulfill the criterion C31>=0
OR
• all the neighboring cells (if C31<0 for all cells)
>C1<0: both the talking and the speaking capacities of MS are not sufficient.
>PRIORITY_CLASS:
> As far as the reselection procedure is made in NC0 (the MS reselects itself in a new best cell without reporting it to
the BSS), it is intended to control the reselection process through the set of GPRS cells available by 2 means:
•The list of GPRS neighboring cells that the MS shall monitor to select a set of 6 best cells.
•The tuning of PRIORITY_CLASS for multi-layered networks where Macro cells shall be treated in a distinct way
from the micro cells. The GPRS priority shall be high in cells where GPRS traffic is expected to be supported (i.e.,
according to operator configuration and radio resource planning).
© Alcatel 189
Target Cell Choice with PBCCH (2/2)
> A neighboring cell has better radio conditions if:
• the neighboring cell belongs to the same RA
– In Standby State
– C32(neighbor)>C32(serving)
– In Ready State
– C32(neighbor)>C32(serving)+ GPRS_CELL_RESELECT_HYSTERESIS
• the neighboring cell belongs to a NEW RA
– In Standby State or Ready state
– C32(neighbor)>C32(serving)+ RA_RESELECT_HYSTERESIS
>When evaluating the best cell, the following hysteresis values shall be subtracted from the C32 value for the
neighboring cells:
•in standby state, if the new cell belongs to the same RA: 0.
•in ready state, if the new cell belongs to the same RA: GPRS_CELL_RESELECT_HYST.
•in standby or ready state, if the new cell belongs to a different RA: RA_RESELECT_HYSTERESIS.
•in case of a reselection occurred within the past 15 seconds: 5 dB.
© Alcatel 190
Reselection During a UL TBF (1/2)
> UL TBF:
• MFS: after a cell reselection, the MFS receives no more data in the UL
blocks allocated to the MS => TBF release
• MS: in the new cell, after the SI messages acquisition, a new UL TBF is
established
• SGSN: the SGSN is informed of the cell change when receiving an LLC
unit from the MS in the new cell. Then the SGSN notifies the BSS about
the cell change (FLUSH PDU)
>After a TBF release, it is up to the originator to reinitiate the transfer: the MS in the UL, the SGSN in the DL.
© Alcatel 191
Reselection During a UL TBF (2/2)
SGSN
Cell Reselection FLUSH LL
MFS
>CAUTION: animated slide.
© Alcatel 192
Reselection During a DL TBF
> DL TBF:
• MFS: after a cell reselection, the MFS receives no more
acknowledgements from the MS => abnormal TBF release
• MS: in the new cell, after the SI messages acquisition, a UL TBF is
established to send a cell update to the SGSN (MS in Ready state)
• SGSN: when the SGSN is informed of a cell change it sends a message
to the MFS to discard LLC units stored for the MS in the old cell (FLUSH
PDU)
• The SGSN resumes the DL transfer by sending a DL LLC unit => DL TBF
establishment in the new cell
>After a TBF release, it is up to the originator to reinitiate the transfer: the MS in the UL, the SGSN in the DL.
© Alcatel 193
Reselection During a DL Transfer: Example
MFS « aware » of a radio problem
Cell update (new BVCI)

SGSN aware of the cell reselection
MFS aware of the cell reselection
Exercise
> MFS: after a cell reselection, the MFS receives no more acknowledgement from the MS ⇒ TBF release.
> MS: in the new cell, after the SI messages acquisition, a UL TBF is established to send a cell update to the SGSN (MS in
Ready state).
> SGSN: when the SGSN is informed of a cell change, it sends a message to the MFS to discard LLC units stored for the
MS in the old cell. The SGSN resumes the DL transfer by sending a DL LLC unit ⇒ DL TBF estab in the new cell.
> The MFS is always aware of a successful cell change afterwards, upon reception of the flush LL message from the
SGSN.
> If the cell change is unsuccessful, the TBF release is counted as abnormal.
> DL_UDT = DL user data

> RAD_STATUS = radio status message sent by the MFS to the SGSN (BSSGP signaling).
> FLUSH_LL = BSSGP message sent by the SGSN to the MFS to notify a successful change of cell by the MS.
© Alcatel 194
3.5 NC0 Cell Selection and Reselection B9
NACC and (P)SI Status
> 2 features are available to improve the duration of the reselection
• NACC: Network Assisted Cell Change
– If EN_NACC = enabled then
– before the cell reselection,
– in the serving cell,
– the network sends to the MS a part of the SI messages of the new cell
• (P)SI Status: (Packet) System Info Status
– If EN_PSI_STATUS = enabled then
– after the transfer resumption,
– in the target cell,
– the MS can ask the network to send it:
» the remaining PSI messages if PBCCH is present
» the remaining SI messages otherwise
>The NACC procedure is a new feature standardized in Release 4, mandatory for Release 4 onwards mobile stations
supporting GERAN Feature Package 1.
>The Packet PSI Status procedure is a feature standardized from Release 97 onwards, optional for Release 97, Release 98
and Release 99 MS, and mandatory for Release 4 onwards MS supporting GERAN Feature Package 1.
>The Packet SI Status procedure is a new feature standardized in Release 4, mandatory for Release 4 onwards mobile
stations supporting GERAN Feature Package 1.
© Alcatel 195
> NACC
• The MS informs the system that it wants to select a neighboring cell
• The BSS transmits the partial SI of the neighboring cell
MFS MFS
MS Cell A Cell B
UL or DL TBF
Packet Cell Change Notification
Retrieval of SI
instances
Packet Neighbor Cell Data (SI1)
Packet Cell Change Continue
> When the MS detects a need of cell reselection in transfer mode, it sends a "Packet Cell Change Notification" message to
the MFS (on PACCH):
• If the MFS knows the (P)SI of the target cell:
– If there is no PBCCH in the target cell, it sends SI1, SI3, SI13 in (several) "Packet Neighbor Cell Data"
messages, followed by a "Packet Cell Change Continue" message.
– If there is a PBCCH in the target cell, it sends PSI1, PSI2, PSI14 in (several) "Packet Neighbor Cell Data"
messages, followed by a "Packet Cell Change Continue" message.
• If the MFS does not know the (P)SI of the target cell, it sends only a "Packet Cell Change Continue" message.
>If no PBCCH is present, the BSC sends SI1, SI3, SI13 messages to the MFS in a "System Information Update" message.
© Alcatel 196
> SI Status
• The MS has resumed the data transfer in the neighboring cell
• Then, it asks the system to retrieve the missing Sys-info
MFS MFS
MS Cell A Cell B
UL or DL TBF
Packet SI Status (SI2, SI2bis, SI2ter msg type missing)
Packet Serving Cell Data (SI2)
Packet Serving Cell Data (SI2bis)
Packet Serving Cell Data (SI2ter)
UL or DL TBF
> This mechanism is applied in both NC0 and NC2
> When accessing a new cell, the MS must get SI13, SI3, SI1, or PSI1 and PSI2 (if not already known through NACC).
>If the Packet (P)SI Status is offered in the cell, it can start PTM and send:
•a "Packet SI Status" message (when there is no PBCCH), with the list of missing SI messages.
•a "Packet PSI Status" message (when there is a PBCCH), with the list of missing PSI messages.
>The MFS shall then send:
•the SI instances required by the MS (the MS is the only addressee) in one or several "Packet Serving Cell Data"
messages in case there is no PBCCH in the target cell.
•the PSI instances required by the MS (all MSs listening to this PDCH will get the information) directly on a PACCH in
case a PBCCH is present in the target cell.
>The MS can request updated (P)SI instances whenever it wants, provided it is in PTM.
© Alcatel 197
3.6 NC2 Cell Reselection
© Alcatel 198
Aim
> Impact of reselection on data transfer
4 1
3 2
Data 4
Transfer 1 2 3
: TBF establishment
: Reselection
: TBF release due to cell reselection
> NC2 aims at reducing the number of cell reselections triggered when the MS is
in Packet Transfer Mode
> The lower the number of cell reselections, the better the end-user QoS
> Each time the MS performs a cell reselection, the data transfer is interrupted and a retransmission of some LLC PDUs
may be required:
• The on-going TBF is released in the old cell.
• The MS performs the PSI or SI acquisition in the new cell.
• Then, the MS establishes a new UL TBF in this cell to send a Cell Update message to the SGSN.
• The MFS deletes or reroutes towards the new cell the LLC PDUs stored in the old cell.
– if they are deleted, a retransmission is needed.
• Finally, the data transfer is re-started (after a DL TBF establishment, in case of DL transfer).
> All these steps degrade the data throughput or the page access time perceived by the end user.
© Alcatel 199
3.6 NC2 Cell Reselection B9
Functional Entities
> The NC2 process for PS is similar to the HO process for CS
• HO
MS - BTS BSC
HO Preparation
Radio HO Candidate
Active HO
Cell Evaluation
Link Channel HO Detection management
Measurements Pre-processing Modified B9
• NC2
MS - BTS MFS
NC cell reselection Preparation
NC cell NC measurement NC cell NC cell NC cell

Reselection Reporting and Reselection Reselection Reselection
activation processing Detection Evaluation management
> The RRM layer is in charge of the measurement processing. It is also in charge of the selection of the target cell, as it
is the layer having the knowledge of the network topology and parameters. The RRM layer is actually in charge of
managing the overall NC cell reselection procedure.
> The RLC layer is in charge of forwarding the packet measurements to the RRM layer. Finally, the RLC layer is in
charge of the RXLEV and RXQUAL measurements processing (per TBF) and of the corresponding NC cell reselection
detection.
© Alcatel 200
NC Cell Reselection Activation / De-activation (1/3)
> Activation
• NETWORK_CONTROL_ORDER has 3 possible values:
– NC0 mode of operation for all MSs
– NC2 mode of operation for R99 onwards MSs
– NC2 mode of operation for all MSs
> NC2 cell reselection can be used only when the MS is in READY state,
otherwise NC0 is used
> De-activation
• NC2_DEACTIVATION_MODE has 2 possible values:
– NC2 deactivation at the end of the packet transfer
– NC2 deactivation at T_READY (GMM Ready timer) expiry
>NETWORK_CONTROL_ORDER is a cell parameter tunable at OMC-R level.
>The R97 and R98 MSs are differentiated from the other MSs. Indeed, all the MSs shall support the NC2 mode,
however since no network manufacturer has implemented the NC2 mode, the R97 and R98 MSs may not have been
sufficiently tested and therefore there is a risk of interoperability with these MSs.
>The “Packet Measurement Order” message is used to activate and de-activate the NC2 mode of operation for a
given MS.
• Activation
–The “Packet Measurement Order (NC2)” message is sent when:
– establishing the first Downlink TBF of the Packet Transfer Mode or when re-establishing the
DL TBF while T3192 is running and there is not any on-going UL TBF.
– no measurement report has already been received for that MS during its on-going packet
transfer(s) (UL and/or DL).
– the MS has not been forced to operate in NC2 mode by a Packet Cell Change Order
message (during an intra-RA cell reselection).
•De-activation
–The “Packet Measurement Order (RESET)” message is sent at the end of the data transfer, in case of
NC2_DEACTIVATION_MODE = “NC2 deactivation at the end of the packet transfer”.
– When the MS goes back to the STANDBY state, in case of NC2_DEACTIVATION_MODE = “NC2
deactivation at GMM Ready timer expiry”.
© Alcatel 201
> Activation
MS BSS
On-going UL TBF (1)

DL LLC PDU
Packet Downlink Assignment / PACCH (2)
READY MS in NC0
Packet Control Acknowledgement (3)
Packet Measurement Order [NC2] / PACCH (4)

T_WAIT_PMR
Packet Measurement Report / PACCH (5)
NC_REPORTING_PERIOD_T
READY MS in NC2 Packet Measurement Report / PACCH (6)
> There is NC2 activation only at the beginning of a DL packet transfer
> (1) It is assumed the MS has just initiated the establishment of a UL TBF, but no DL TBF is on-going. If there is no UL
TBF on-going, the NC2 activation is also done on receipt of the acknowledgement of the DL TBF establishment
performed on the (P)CCCH.
>(2) The receipt of a DL LLC PDU triggers the establishment of the DL TBF on the PACCH of the UL TBF.
>(3) The MS acknowledges the Packet Downlink Assignment message by a Packet Control Acknowledgement message.
>(4) Upon receipt of the Packet Control Acknowledgement message, the BSS sends to the MS on the PACCH of the on-
going DL TBF a Packet Measurement Order message forcing the MS to operate in NC2 mode and starts the timer
T_WAIT_PMR. The Packet Measurement Order message is sent without a polling indication. The Packet Measurement
Order message provides the MS with the following NC measurement parameters NETWORK_CONTROL_ORDER,
NC_NON_DRX_PERIOD, NC_REPORTING_PERIOD_I, NC_REPORTING_PERIOD_T. The timer T_WAIT_PMR monitors
the reception of the Packet Measurement Report messages.
> (5)-(6) On the allocated UL RLC blocks, the MS sends a Packet Measurement Report message every
NC_REPORTING_PERIOD_T seconds. The timer T_WAIT_PMR is stopped at the receipt of the first Packet Measurement
Report message. At T_WAIT_PMR expiry, if MAX_RETRANS_SIG ≠ 0 a new Packet Measurement Order is sent to the MS
and the timer T_WAIT_PMR is started. Such mechanism is applied MAX_RETRANS_SIG attempts.
© Alcatel 202
> De-activation at the end of the packet transfer
MS BSS
On-going DL TBF
READY MS in NC2 Last DL RLC data block with a polling indication (1)
Packet Downlink Ack/Nack / PACCH (2)
Packet Measurement Order [Reset] / PACCH (3)
STANDBY MS in NC0
> There is NC2 de-activation at the normal end of a DL Packet Transfer

Mode
> (1) It is assumed that a DL TBF is on-going. The BSS sends to the MS the last useful data block (case of normal TBF
release) or the RLC block containing the last dummy UI command (case of a delayed TBF release).
> (2)The MS acknowledges the received block by sending the final Packet Downlink Ack/Nack message to the BSS.
•Note: When an RLC mode change is detected, the BSS waits for the final Packet Downlink Ack/Nack message
before re-establishing the DL TBF with the new RLC mode. As the fast DL TBF establishment occurs on receipt of
the final Packet Downlink Ack/Nack message, a Packet Measurement Order [Reset] message would be
immediately followed by a Packet Measurement Order [NC2] message. In order to avoid that useless message
exchange, the NC2 mode is not deactivated in this case.
>(3) If there is no on-going UL TBF, upon receipt of the final Packet Downlink Ack/Nack message, the BSS sends
to the MS on the PACCH of the DL TBF a Packet Measurement Order message with a Reset command. The Reset
command forces the MS to realign its behavior on the parameters broadcast in the (packet) system information
messages on (P)BCCH (i.e., return to NC0). To ensure a high probability of correct reception by the MS, the RRM orders
MAC to repeat the Packet Measurement Order (Reset) message several times. The number of repetitions is defined by
the O&M parameter N_SIG_REPEAT. In case the Packet Measurement Order (Reset) message is not received by the MS
although repeated, the MS will remain in NC2 mode for the whole duration of the Ready timer, while the operator
requested the network to deactivate NC2 at the end of the Packet Transfer Mode. Because repetitions should ensure
that this happens very scarcely, the Alcatel BSS will not handle those rare events. Then, if a Packet Measurement Report
is received in Packet Idle Mode, it will be discarded.
> There is no NC2 deactivation at the end (normal or abnormal) of the UL Packet Transfer Mode, and
at the abnormal end of the DL Packet Transfer Mode.
© Alcatel 203
NC Measurement Reporting and Processing (1/4)
> DL RXLEV
• The MS sends a “Packet Measurement Report” message containing the
RXLEV measured on the serving cell and the 6 best neighbor cells
• The “Packet Measurement Report” message is sent every:

– NC_REPORTING_PERIOD_T ms, in case of Packet Transfer Mode
– NC_REPORTING_PERIOD_I ms, in case of Packet Idle Mode
> On the one hand the NC_REPORTING_PERIOD_T parameter is defined by O&M on a per cell basis. On the other
hand, the NC_REPORTING_PERIOD_I is set on a BSS cell basis without OMC-R access (default value = max value =
61.44 s i.e., 256 52-multiframes).
> These parameters are provided to the MS either in a Packet Measurement Order message or in a Packet Cell
Change Order message. They are never broadcast on (packet) system information messages.
> Packet Measurement Report message contents

•TLLI of the MS
•NC_MODE (Set to NC2)
•RXLEV_SERVING_CELL (RXLEV measured on the serving cell)
•NUMBER_OF_NC_MEASUREMENTS (Number of measurements reported for the neighboring cells)
•FREQUENCY_N (Refer to the ARFCN or ARFCN and BSIC of a neighboring cell)
•BSIC (BSIC of the indexed neighboring cells)
•RXLEV_N (RXLEV of the indexed neighboring cells)
© Alcatel 204
> DL RXLEV averaging for serving cell and neighbor cell
• AV_DL_RXLEV_NC2p = (1-f)* AV_DL_RXLEV_NC2p-1 + f*RXLEV_Np
– RXLEV_Np is the RXLEV sample reported by the MS in the incoming Packet
Measurement Report message
– f is the averaging forgetting factor and is derived from the parameter
NC_RXLEV_FORGETTING_FACTOR
– p is the iteration index
> NC_RXLEV_FORGETTING_FACTOR = 0.13 ((Alcatel recommended value) and it can be set at OMC-R level).
> If the neighboring cell n was not reported in the precedent Packet Measurement Report but just in the last one:
•AV_DL_RXLEV_NC2p(n) = (1-f) *AV_DL_RXLEV_NC2p-1(n) + (1-(1-f) ) *RXLEV_Np(n)
– = (p –1) – i
–The index i represents the last time an NC measurement for that neighboring cell has been reported in
a Packet Measurement Report message.
© Alcatel 205
> RXQUAL for a GPRS TBF
• In the DL, the MS sends a “Packet DL Ack/Nack” message containing the
RXQUAL measured on the serving cell every T_DL_GPRS_MeasReport ms
• In the UL, the MFS assesses the RXQUAL for each RLC block received
> MeanBEP for an EGPRS TBF
• In the DL, the MS sends an “EGPRS Packet DL Ack/Nack” message
containing the MeanBEP measured on the serving cell every
T_DL_EGPRS_MeasReport ms
• In the UL, the MFS assesses the MeanBEP for each RLC block received
> T_DL_GPRS_MeasReport and T_DL_EGPRS_MeasReport are defined by O&M on a per cell basis.
© Alcatel 206
> DL RXQUAL averaging  
1
• AV_DL_RXQU AL_NC 2 p =  1−  * AV_DL_RXQU AL_NC 2 p −1
 U 
1  p 
+ DL_RXQUAL
Up
Δtp
• U p = α NC 2 U p-1 +1
• forgetting factor: αNC2 = (1-β )1/TNC2
– β = 0.9
– ∆t p is the time between 2 DL RXQUAL samples
– TNC2 set to the parameter NC_RXQUAL_AVG_PERIOD
> UL RXQUAL and MeanBEP (UL & DL) are averaged using the same
formula and the same parameter
> U0 = 0, consequently U1 = 1.
© Alcatel 207
NC Cell Reselection Detection (1/5)
> Trigger conditions
Cause Similar
Priority Name of the cause
reference HO cause
Highest PT4 Too bad uplink radio quality Cause 2
… PT3 Too bad downlink radio quality Cause 4
… PT1 Too low downlink received signal level Cause 5
Lowest PT2 Detection of a better neighboring cell Cause 12
© Alcatel 208
> Cause PT3 for a GPRS TBF
• AV_DL_RXQUAL_NC2 > NC_DL_RXQUAL_THR
• If NC_DL_RXQUAL_THR = 7 (Never), the cause PT3 is disabled
> Cause PT3 for an EGPRS TBF
• AV_DL_MeanBEP_NC2 < NC_DL_MeanBEP_THR_xxSK_yyyyyy
– xxSK: GMSK or 8-PSK
– yyyyy:
– type1: type 1 ARQ (no Incremental Redundancy)
– type2: type 2 ARQ (with Incremental Redundancy)
• If NC_DL_MeanBEP_THR_xxSK_yyyyyy = 0, the cause PT3 is disabled
> Cause PT3 is checked only for the serving cell each time an (EGPRS) Packet Downlink Ack/Nack message is received
provided that the DL TBF is not in delayed release state and provided that the T_NC_RXQUAL_VALID seconds have
elapsed since the receipt of the first Packet Downlink Ack/Nack message of the DL TBF.
> T_NC_RXQUAL_VALID aims at not triggering false alarms at the beginning of the TBF and not triggering an NC cell
reselection for a very short TBF.
© Alcatel 209
> Only one NC_DL_MeanBEP threshold is applied for cause PT3 during an
EGPRS TBF, and derived from NC_DL_RXQUAL_THR
• NC_DL_MeanBEP_THR_xxSK_yyyyyy = NC_DL_MeanBEP
• NC_DL_MeanBEP = (23-3* NC_DL_RXQUAL_THR)
• If NC_DL_RXQUAL_THR = 7 then NC_DL_MeanBEP = 0
– i.e., the cause PT3 is disabled
> Same behavior for cause PT4 in the UL

• NC_UL_MeanBEP = (23-3* NC_UL_RXQUAL_THR)
© Alcatel 210
> Cause PT4 for a GPRS TBF
• AV_UL_RXQUAL_NC2 > NC_UL_RXQUAL_THR
• If NC_UL_RXQUAL_THR = 7 (Never), the cause PT4 is disabled
> Cause PT4 for an EGPRS TBF
• AV_UL_MeanBEP_NC2 < NC_UL_MeanBEP_THR_xxSK_yyyyyy
– xxSK: GMSK or 8-PSK
– yyyyy:
– type1: type 1 ARQ (no Incremental Redundancy)
– type2: type 2 ARQ (with Incremental Redundancy)
• NC_UL_MeanBEP_THR_xxSK_yyyyyy = NC_UL_MeanBEP
• NC_UL_MeanBEP = (23-3* NC_UL_RXQUAL_THR)
• If NC_UL_RXQUAL_THR = 7 then NC_UL_MeanBEP = 0
– i.e., the cause PT4 is disabled
> Cause PT4 is checked only for the serving cell whenever one UL RLC data block is correctly received for the on-going
UL TBF provided that T_NC_RXQUAL_VALID seconds have elapsed since the computation of the first UL samples of the
UL TBF.
> T_NC_RXQUAL_VALID aims at not triggering false alarms at the beginning of the TBF and not triggering an NC cell
reselection for a very short TBF.
© Alcatel 211
> Cause PT1
• AV_DL_RXLEV_NC2 < NC_DL_RXLEV_THR + Max(BNC2,0)
– without PBCCH, BNC2 = MS_TXPWR_MAX_CCH – P
– with PBCCH BNC2 = GPRS_MS_TXPWR_MAX_CCH – P
• If NC_DL_RXLEV_THR = -110dBm (Never), the cause PT1 is disabled
> Cause PT2
• C2NC2(n) - C2NC2(s) > NC_RESELECT_HYSTERESIS(s,n)
– If PBCCH is present in the serving cell, C2NC2 is replaced with C32NC2
AND
• AV_DL_RXLEV_NC2 <= NC_DL_RXLEV_LIMIT_THR
• If NC_RESELECT_HYSTERESIS(s,n) = 128dB (Never), the cause PT2 from s
to n is disabled
>The cause PT1 is equivalent to check the condition C1NC2 < 0 assuming that the (GPRS_)RXLEV_ACCESS_MIN
threshold is replaced with NC_DL_RXLEV_THR threshold.
>Cause PT2 is checked among the neighboring cells n upon receipt of a Packet Measurement Report message. It is
triggered if the value C2NC2 or C32NC2 of one neighboring cell n exceeds the value C2NC2 or C32NC2 of the serving cell
s by at least the O&M hysteresis NC_RESELECT_HYSTERESIS(s,n) defined per cell adjacency link (respectively whether or
not there is a PBCCH in the serving cell).
© Alcatel 212
NC Cell Reselection Evaluation: Functional Entities
- cause reference
- neighboring cell Filtering cell Cell ranking Reference of the
that checked the Cell filtering list target cell
cause
process
process
Modified B9
• Cell filtering process

– This process builds a Filtering Cell List depending on:
– The content of the Rejected Cell list
– EN_OUTGOING_GPRS_REDIR
– C1NC2(n)
• Cell ranking process
– This process builds a Filtering Cell List depending on:
– C31NC2
– Load situation NewB9
– C1NC2 & C2NC2 if no PBCCH or C1NC2 & C32NC2 with PBCCH
> The Cell Filtering process is computed on receipt of an NC Cell Reselection Evaluation Request message. Before
processing the cell ranking, all the candidate neighboring cells are gathered in the Raw Cell List. The serving cell is
always included in this latter list.
> The contents of the Raw Cell List depend on the cause reference that triggered the NC cell reselection evaluation:
• If Cause PT1, or PT3, or PT4 is checked, then the Raw Cell List regroups the cells reported in the Packet
Measurement Report message provided that the cells are configured by O&M. The serving cell is always included
in the list.
• If only Cause PT2 is checked, then the Raw Cell List regroups all the neighboring cells that verify Cause PT2 and
that are reported in the Packet Measurement Report message. The serving cell is always included in the list.
>The Raw Cell List is then filtered according to the contents of a Rejected Cell List, according to the flag
EN_OUTGOING_GPRS_REDIR of the serving cell and of the neighboring cells, and according to the C1NC2 parameter
of the neighboring cells. The output cell list is here called the Filtering Cell List.
© Alcatel 213
NC Cell Reselection Evaluation: Criteria Computation (1/2)
> Path loss criterion parameter C1NC2
• If PBCCH is present:
– C1NC2(n) = AV_RXLEV_NC2(n) – GPRS_RXLEV_ACCESS_MIN(n) -
max(GPRS_MS_TXPWR_MAX_CCH(n) – P(n), 0)
• Else
– C1NC2(n) = AV_RXLEV_NC2(n) – RXLEV_ACCESS_MIN(n) -
max(MS_TXPWR_MAX_CCH(n) – P(n), 0)
> Cell ranking criterion parameter C2NC2 (used when the PBCCH is not present)
• If PENALTY_TIME <> 31:
– C2NC2(n) = C1NC2(n) + CELL_RESELECT_OFFSET(n)
• Else
– C2NC2(n) = C1NC2(n) - CELL_RESELECT_OFFSET(n)
• If the T_NC_PING_PONG timer is running, the anti-ping-pong offset
NC_PING_PONG_OFFSET is subtracted from the C2NC2 of the neighboring cells
>The cell n denotes either the serving cell or a neighboring cell.
>In the above equations, the following notations mean:

• AV_RXLEV_NC2(n) is the average received signal level measured by the MS on the BCCH of the cell n.
•RXLEV_ACCESS_MIN(n) or GPRS_RXLEV_ACCESS_MIN(n) is the minimum received signal level required to
perform an access to the cell n.
• MS_TXPWR_MAX_CCH(n) or GPRS_MS_TXPWR_MAX_CCH(n) is the maximum transmit power of the MS when
accessing the cell n.
>P(n) is the maximum output RF power of the MS in the BCCH frequency band of the cell n. P(n) gives the MS Radio
Access Capability Information Element provided in the Packet Resource Request message or in the DL LLC PDU. In the
NC cell reselection procedure, the parameter P(n) shall always refer to the RF power capability of the GMSK
modulation.
>Note that all values are expressed in dBm.
>The cell ranking criterion parameter C2NC2 is used to order the candidate cells on a radio criterion. This criterion
applies only in serving cells where there is no PBCCH established.
•CELL_RESELECT_OFFSET(n) is a positive offset which favors or disfavors the cell n.
•PENALTY_TIME(n) indicates whether the cell reselection offset shall be positive or negative.
© Alcatel 214
NC Cell Reselection Evaluation: Criteria Computation (2/2)
> Signal level threshold criterion parameter C31NC2
• C31NC2(n) = AV_RXLEV_NC2(n) – HCS_THR(n)
> Cell ranking criterion parameter C32NC2
• serving cell
– C32NC2(n) = C1NC2(n)
• neighboring cell
– C32NC2(n)=C1NC2(n)+GPRS_RESELECTION_OFFSET(n)
– If T_NC_PING_PONG(s) is running
– C32NC2(n)=C1NC2(n)+GPRS_RESELECTION_OFFSET(n) -
NC_PING_PONG_OFFSET(s)
> The signal level threshold criterion parameter C31NC2 is used in hierarchical cellular networks to determine whether
the signal level received from a neighboring cell n is sufficient to redirect the MS towards cell n based on a non-radio
priority criterion. This criterion parameter is used only if there is a PBCCH established in the serving cell.
> HCS_THR(n) defines a signal threshold for applying the prioritized hierarchical GPRS cell reselection criterion. The
cell n denotes either the serving cell or a neighboring cell.
> Contrary to the C31 criterion implemented in the MS, the Alcatel BSS does not manage the timer T implemented for
each cell to monitor the time a neighboring cell is present in the list of the strongest carriers. Therefore, the Alcatel BSS
always assumes that GPRS_TEMPORARY_OFFSET(n) = 0.
> As the GPRS_CELL_RESELECT_HYSTERESIS, RA_RESELECT_HYSTERESIS and C31_HYST are used to control the
triggering conditions of a cell reselection. They are not taken into account in the criterion C31NC2 and C32NC2
parameters.
> The cell ranking criterion parameter C32NC2 is used to order the candidate cells on a radio criterion. This criterion
applies only in serving cells where there is a PBCCH established.
> GPRS_RESELECTION_OFFSET(n) applies a positive or negative offset which favors or disfavors the neighboring cell n.
The cell n denotes either the serving cell or a neighboring cell.
> If the parameter C32_QUAL is set, the determination of C32NC2 is modified so that the neighboring cell n having
the highest AV_DL_RXLEV_NC2 among all the neighboring cells is applied a GPRS_RESELECTION_OFFSET (only if the
offset is positive) and no GPRS_RESELECTION_OFFSET is applied to the other neighboring cells.
> The MFS shall take care of avoiding ping-pong effects between the old cell and the new cell (i.e., circular NC cell
reselections). For that purpose, the MFS handles an anti ping-pong timer and an anti ping-pong offset, respectively
called T_NC_PING_PONG and NC_PING_PONG_OFFSET. While the timer T_NC_PING_PONG is running, the
neighboring cells are disfavored by the offset NC_PING_PONG_OFFSET (expressed in dB) in the cell ranking process.
> The MFS starts the anti ping-pong timer at the creation of the NC2 context for the MS.
> The MFS stops the anti ping-pong timer at the deletion of the NC2 context.
© Alcatel 215
NC Cell Reselection Evaluation: Cell Filtering Process
> A candidate neighboring cell n is filtered out when:
• A previous NC cell reselection failed toward this cell and
T_NC_REJ_CELL[n] is running
– The timer T_NC_REJ_CELL[n] is started or restarted each time the new cell n is inserted
in the Rejected Cell List
– At expiry of T_NC_REJ_CELL[n], the rejected cell is removed from the Rejected Cell List
– One T_NC_REJ_CELL by cell (and not by MS)
• EN_OUTGOING_GPRS_REDIR(n) = enabled
• C1NC2(n) < 0
> The notation T_NC_REJ_CELL[n] refers to the timer associated to the cell n.
>For the purpose of filtering cells towards which a previous NC cell reselection failed, the RRM manages a Rejected
Cell List. Each neighboring cell n of the list is guarded by the timer T_NC_REJ_CELL[n]. While T_NC_REJ_CELL[n] is
running, the neighboring cell n shall not be selected for any NC cell reselection.
>The Rejected Cell List shall be able to contain up to 32 neighboring cells. If the Rejected cell List is full, the oldest cell
is discarded and the new one is stored.
>In addition, if the flag EN_OUT_GOING_GPRS_REDIR(s) of the serving cell is set to “Enabled”, the serving cell is
removed from the Raw Cell List. Indeed, in such cells, the neighboring cells do not need to be better than the serving
cell as a GPRS redirection is not triggered due to a bad radio link, but is triggered in order to redirect the MS towards a
more appropriate neighboring cell to carry PS traffic.
© Alcatel 216
NC Cell Reselection Evaluation: Cell Ranking Process (1/2)
> Without PBCCH
• The best candidate cell is the cell for which the following ordered criteria
are fulfilled:
1. C31NC2 >= 0
2. Load situation = low
3. Best C2NC2
• If all the candidate cells have their criterion C31NC2 < 0, then
– The best candidate cell is the cell which has the best C2NC2
> Once the best candidate cell has been found, the MFS checks whether or not the best cell is the serving cell:
• If the best cell is not the serving one, the NC cell reselection evaluation function sends an NC Cell Reselection
Alarm Indication message to the NC cell reselection execution function in order to trigger the execution of the NC
cell reselection.
• If the best cell is the serving cell, the NC cell reselection procedure is stopped.
© Alcatel 217
NC Cell Reselection Evaluation: Cell Ranking Process (2/2)
> With PBCCH
• The best candidate cell is the cell for which the following ordered criteria
are fulfilled:
1. C31NC2 >= 0
2. Load situation = low
3. Highest PRIORITY_CLASS
4. Best C32NC2
• If all the candidate cells have their criterion C31NC2 < 0, then
– The best candidate cell is the cell which has the best C32NC2
© Alcatel 218
NC Cell Reselection Evaluation: Load Evaluation (1/2)
> Every 5 seconds, the MFS computes for each cell
MAX[UL_PS_Used _Bandwidth ; DL_PS_Used _Bandwidth ] + CS_Used_Ba ndwidth
NC2_Load (in %) = × 100
Total_PS_Bandwidth
> Where:
N _ PDCH _ ALLOCATED
• UL_PS_used_Bandwidth = ∑ Nb of UL TBFs / MAX_UL_TBF_SPDCH
i =1
N _ PDCH _ ALLOCATED
• DL_PS_used_Bandwidth = ∑ Nb of DL TBFs / MAX_DL_TBF_SPDCH
i =1
• Total_PS_Bandwidth = MAX_PDCH – NB_TS_MPDCH
• CS_Used_Bandwidth = Total_PS_Bandwidth – N_PDCH_ALLOCATED

– N_PDCH_ALLOCATED = Number of SPDCHs currently allocated to the MFS
© Alcatel 219
NC Cell Reselection Evaluation: Load Evaluation (2/2)
> NC2_Load is averaged using the sliding window
NC2_LOAD_EV_PERIOD (=3)
> This load average is then compared to the threshold
THR_NC2_LOAD_RANKING as followed:
• If Load average <= THR_NC2_LOAD_RANKING then
– Load situation = low
• Else (Load average > THR_NC2_LOAD_RANKING)
– Load situation = high
• Case of the external cells (inter BSC)

– If THR_NC2_LOAD_RANKING < 100% then Load situation = low
– Else (THR_NC2_LOAD_RANKING = 100%) then Load situation = high
Exercise
> The MFS shares the NC2 load situation information among the different cells of the BSS (or at least between the cells
having a cell reselection link with the serving cell).
> In case of an external cell, the load evaluation is different since the load situation of such cells is unknown in the
serving cell.
© Alcatel 220
NC Cell Reselection Execution with NACC
MS BSS BSS SGSN
Serving cell Target cell
On going UL or DL TBF (1)
Packet Measurement Report / PACCH (2)
Packet Neighbour Cell Data (S1) / PDCH

Packet Neighbour Cell Data (SI3) / PDCH
Packet Neighbour Cell Data (SI13) / PDCH
Packet Cell Change Order / PACCH (3) T_Ack_Wait

(4)
Packet Control Acknowledgement / PACCH (5) T_Wait_Flush
Packet Channel Request / PRACH (6)
Packet Uplink Assignment / PCCCH (7)
On going UL TBF (8)

UL LLC PDU [TLLI] (9)
FLUSH-LL PDU [TLLI, old BVCI] (10)
FLUSH-LL-ACK PDU [TLLI, “deleted”] (11)
> (1) A UL or DL TBF is assumed to be on-going.

>(2) The MS sends a Packet Measurement Report message on one of the allocated UL blocks on the PACCH.
>(3) Upon receipt of the Packet Measurement Report message, the BSS detects that an NC cell reselection must be
triggered and therefore orders the MS to reselect a new cell by sending a Packet Cell Change Order message on the
PACCH of the DL or UL TBF. If both a UL and a DL TBF are on-going, the message is preferentially addressed by a DL
TFI. The Packet Cell Change Order message is sent in acknowledged mode and contains the ARFCN and the BSIC of
the target cell plus the NC parameters of the target cell (if the MS can operate in NC2 mode in the target cell). When
sending the Packet Cell Change Order message, the BSS starts the timer T_ACK_WAIT to monitor the receipt of the
Packet Control Acknowledgement message.
>(4)-(5) Upon receipt of the Packet Cell Change Order message, the MS aborts its on-going TBF in the serving cell and
sends the Packet Control Acknowledgement message. Once the MS has sent the Packet Control Acknowledgement
message, the MS switches to the new cell. Upon receipt of the Packet Control Acknowledgement message, the BSS
starts the timer T_WAIT_FLUSH (which monitors the reception of the FLUSH-LL PDU) and requests the release of the on-
going TBF(s) (if any). The radio resources are immediately released, i.e., without freezing them. In case the radio
resources are already frozen, the freezing timer is stopped and the radio resources are immediately released.
>(6)-(8) After acquiring the full PSI cycle and successfully decoding the PSI1 and PSI2 messages of the target cell, the
MS initiates a UL TBF establishment in the new cell.
>(9) The target BSS sends to the SGSN the first UL LLC PDU containing the TLLI of the MS.
>(10) By comparing the previous couple and the new one (BVCI; NSEI), the SGSN detects that the MS has changed of
cell and sends a FLUSH-LL PDU to the old cell.
>(11) Upon receipt of the FLUSH-LL PDU, the BSS stops the timer T_WAIT_FLUSH, and either transfers the pending DL
LLC PDUs to the new cell (if the old and new cells belong to the same routing area and the same NE) or deletes them.
The BSS acknowledges the FLUSH-LL PDU by sending a FLUSH-LL-ACK PDU to the SGSN. When the feature “full intra-
RA LLC PDU rerouting” is implemented, a rerouting will be possible between 2 different NSEs.
© Alcatel 221
NC Cell Reselection Execution with LLC PDU Rerouting
MS BSS BSS SGSN

Serving cell Target cell
On going DL TBF
Packet Measurement Report / PACCH
Packet Cell Change Order / PACCH T_Ack_Wait
Packet Control Acknowledgement / PACCH T_Wait_Flush
Packet Channel Request / PRACH

Packet Uplink Assignment / PCCCH
On going UL TBF
UL LLC PDU [TLLI]
FLUSH-LL [TLLI, old BVCI, new BVCI, (new NSEI)]

LLC PDU(s) rerouting
FLUSH-LL-ACK [TLLI, “transferred”]
> In Packet Transfer Mode, it happens that Downlink LLC PDU frames, which have been transmitted by the SGSN to
the BSS, are not received by the MS because the MS performs a cell reselection. Indeed, these PDUs are discarded by
the BSS. The BSS informs the SGSN that it has discarded these PDUs, and the SGSN has to send them again. With the
feature Downlink LLC PDU rerouting, the BSS keeps in memory these PDUs, and transmits them to the MS in the target
cell, after the cell reselection.
> EN_DL_LLC_PDU_REROUTING is the OMC-R parameter that activates the DL rerouting on a per BSS basis.
> If the SGSN supports the INR option (Inter-NSE Rerouting), a rerouting is requested by providing the BVCI and the
NSEI of the new cell in the FLUSH-LL message in case of a cell change between two different NSEs. Otherwise (same
NSE) only the BVCI of the new cell is provided.
© Alcatel 222
Full Intra-RA LLC PDU Rerouting
> Available whatever the NETWORK_CONTROL_ORDER: NC0 or NC2
> If EN_DL_LLC_PDU_REROUTING = enabled
• If the SGSN requests a rerouting (new BVCI included in Flush LL)
– The MFS can perform an intra-RA intra-NSE rerouting
• If the SGSN does not support Inter-NSE rerouting
– The MFS performs an autonomous intra-RA inter-NSE rerouting
> Summary
Flush LL SGSN Inter-NSE
Old and new ell MFS behavior
information capability
same RA old BVCI + new BVCI DL LLC PDU rerouting

same NSE
only old BVCI DL LLC PDU deletion
old BVCI + new BVCI DL LLC PDU rerouting

same RA Yes
only old BVCI DL LLC PDU deletion
different NSEs
only old BVCI No DL LLC PDU rerouting
> In case of MS cell change, the control of the rerouting of DL LLC PDUs from one cell to another is left to the
SGSN
> In case of MS cell change, the SGSN sends a Flush-LL PDU to the BSS, in order:
• either to delete the outstanding PDUs in the old cell buffer,
• or to reroute them to the new cell.
>When the MS operates in NC2 mode, the “old” and the “new” cells are known by the BSS.
Consequently an autonomous rerouting can be performed at Flush-LL receipt.
> When the MS operates in NC0 mode, the BSS does not know the link between the “old” and the “new” cells. To find
this link, the BSS uses the TLLI of the cell Update.
• As this message cannot be identified as such, it is checked that the TLLI of a UL TBF:
– does not exist in any of the MS contexts stored in the cell.
– is not a foreign or a random TLLI.
• A “TLLI retrieval” process is started to try to find a cell of the same RA, on any GPU, in which this TLLI exists.
• When the search is successful, the rerouting can be performed at Flush-LL receipt.
© Alcatel 223
Outgoing GPRS Redirection
> Useful in multilayer and multiband networks, in order to reduce the
number of reselections
> If EN_OUTGOING_GPRS_REDIR(s) = enabled
• As soon as the MS is in Packet Transfer Mode, it is redirected from the cell
• Then, the cell ranking process is started to find the best candidate cell
– According to the operator strategy
– See session 4 for a strategy example
Exercise
> An outgoing GPRS redirection is an NC cell reselection which is triggered when the MS enters the packet transfer
mode in the serving cell even if the radio link is good.
> The intention of GPRS redirections is to redirect the MS towards a target cell more appropriate to carry PS traffic (for
instance a macro cell).
© Alcatel 224
© Alcatel 225
BSSGP
> Only DL flow control is performed between the BSS and the SGSN
> Principle of the DL flow control mechanism:
• the BSS sends to the SGSN the flow control parameters in the FLOW-
CONTROL-MS/BVC messages
• the flow control parameters allow the SGSN to locally control its
transmission towards the BSS
BSSGP frame
LLC frame
BVCI TLLI Payload
Used to perform BVC flow control Used to perform MS flow control
> Caution: LLC frames are encapsulated 1:1 into BSSGP frames. This is the reason why we can say that
there is an LLC frame flow control mechanism at BSSGP level.
© Alcatel 226
Flow Control Performed at SGSN Side (1/2)
> The SGSN shall perform flow control on each BVC and on each MS
> The flow control is performed on each LLC PDU first by the MS flow
control mechanism and then by the BVC flow control mechanism:
• if an LLC PDU is passed by the MS flow control then the SGSN applies
the BVC flow control to the LLC PDU
• if an LLC PDU is passed by both flow control mechanisms, the entire LLC
PDU is delivered to the BSS
MS flow control MS flow control MS flow control
BVC flow control
BSS
© Alcatel 227
Flow Control Performed at SGSN Side (2/2)
> Leaky bucket algorithm:
• An LLC PDU is passed as long as the bucket counter (B) plus the length
of the LLC PDU does not exceed the bucket size (Bmax)
• When the LLC PDU is passed, its length is added to B
• Any LLC PDU not passed is delayed until B plus the LLC PDU length is
less than Bmax
• The algorithm takes into account the leak rate of the bucket (R)
> Leaky bucket principle
? new LLC PDU
Max bucket size (Bmax)
bucket size (B)
leaking rate (R)
© Alcatel 228
Flow Control Performed at BSS Side (1/3)
> The BSS controls the DL transmission of the SGSN by sending the
parameters Bmax and R in the flow control PDU:
• after the sending of a FLOW_CONTROL_BVC PDU, the BSS cannot send
a new FLOW_CONTROL_BVC PDU before T_Flow_Ctrl_Cell seconds
– T_Flow_Ctrl_Cell is a BSS parameter
– Default value = 0
– By default, the BVC flow control is disabled
• after the sending of a FLOW_CONTROL_MS PDU, the BSS cannot send
a new FLOW_CONTROL_MS PDU before T_Flow_Ctrl_MS seconds
– T_Flow_Ctrl_MS is a BSS parameter
– Default value = 10 s
> NB: the cell flow control is performed more frequently than the MS flow control because:
• The radio resource availability for a TBF is always shorter than the guarding time of a PDCH,
therefore the MS individual traffic is less of an influence on the leaking rate.
• The radio resource available for one MS may change from one TBF to another.
• The combined traffic of all the GPRS MSs in the cell exchanging data with the SGSN has to be
mapped onto a BVC, which may become the blocking factor as the BVC is mapped on an NSVC,
which is mapped on a PVC, carried by a BC which has a fixed maximum capacity.
© Alcatel 229
> FLOW_CONTROL_BVC PDU:
• BVC_Bucket_Size: the maximum size of the cell buffer in the MFS
• BVC_Bucket_Leak_Rate: the measured throughput in the cell from the
RRM to the RLC
• Bmax_default_MS: the default value of the maximum size of the MS
buffer in the MFS
• R_default_MS: the default value of the measured throughput for the MS
from the RRM to the RLC
> Formulas:
• The BVC_Bucket_Size (value expressed in octet) is calculated as follows:
– Case T_Flow_Ctrl_Cell ≠ 0:
– BVC_Bucket_Size = Flow_Dim_safety_MS * Max_PDCH * Max_Rate_PDCH *
(1/8) * Max_Rate_Safety * T_Flow_Ctrl_Cell
– Case T_Flow_Ctrl_Cell = 0:
– BVC_Bucket_Size = Flow_Dim_safety_MS * Max_PDCH * Max_Rate_PDCH *
(1/8) * Max_Rate_Safety * Def_value_T_Flow_Ctrl_Cell
• The BVC_Bucket_Leak_Rate (value expressed in 100 bits/sec) is calculated as follows:

– Case T_Flow_Ctrl_Cell ≠ 0:
– IF B_BVC < BVC_Bucket_Size
» BVC_Bucket_Leak_Rate = [(BVC_Bucket_Size - B_BVC )*8] /
[T_Flow_Ctrl_Cell * Flow_Dim_safety_BVC * 100]
– ELSE
» BVC_Bucket_Leak_Rate = 0
– Case T_Flow_Ctrl_Cell = 0
– BVC_Bucket_Leak_Rate = (Max_PDCH * Max_Rate_PDCH *
Max_Rate_Safety)/100
• The Bmax_default_MS (value expressed in octet) is calculated as follows:

– Case T_Flow_Ctrl_MS ≠ 0:
– Bmax_default_MS = Flow_Dim_safety_MS * Max_Rate_PDCH * (1/8) *
Max_Rate_Safety * T_Flow_Ctrl_MS
– Case T_Flow_Ctrl_MS = 0:
– Bmax_default_MS = Flow_Dim_safety_MS * Max_Rate_PDCH * (1/8) *
Max_Rate_Safety * Def_value_T_Flow_Ctrl_MS
• The R_default_MS (value expressed in 100 bits/sec) is calculated as follows:

– R_default_MS = (Flow_Dim_safety_MS * Max_Rate_PDCH * Max_Rate_Safety)/100
© Alcatel 230
> FLOW_CONTROL_MS PDU:
• MS_Bucket_Size: the maximum size of the MS buffer in the MFS
• MS_Bucket_Leak_Rate: the measured throughput for the MS from the
RRM to the RLC
> Formula:
• The MS_Bucket_Size (value expressed in octet) is calculated as follows:
– MS_Bucket_Size = n * Max_Rate_PDCH * (1/8) * Max_Rate_Safety * T_Flow_Ctrl_MS
• The MS_Bucket_Leak_Rate (value expressed in 100 bit/sec) is calculated as follows:
– MS_Bucket_Leak_Rate = B_MS * 100 / MS_Bucket_Size
> Explanation:
• Max_PDCH
– O&M parameter indicating the maximum number of PDCHs that can be established in the cell.
• Max_Rate_PDCH
– maximum rate of one PDCH in the considered cell (value in bits/s)
• Max_Rate_Safety
– Safety factor to compensate the Max_Rate_PDCH in the calculation of BVC_Bucket_Size and
MS_Bucket_Size
• Flow_Dim_safety_BVC
– O&M safety factor, used to tune the BVC bucket value
• Flow_Dim_safety_MS
– O&M safety factor, used to tune the MS bucket value
• MAX_LLC_PDU
– maximum length of a DL LLC PDU (the SGSN has to be able to send at least one DL LLC PDU)
• B_BVC
– value in octet of the current bucket size at MFS side for the cell. It corresponds to the amount of LLC
waiting frames for this BVC (cell)
• T_Flow_Ctrl_Cell
– sending period of NM-FLOW-CONTROL-CELL-req
• T_Flow_Ctrl_MS
– sending period of NM-FLOW-CONTROL-MS-req
• Def_value_T_Flow_Ctrl_Cell
– default value forT_Flow_Ctrl_Cell (set to 5 sec)
• Def_value_T_Flow_Ctrl_MS
– default value for T_Flow_Ctrl_MS (set to 10 sec)
• B_MS
– Value in octets of the current bucket size at MFS side for the MS. It corresponds to the amount of LLC
PDUs waiting to be transmitted for this MS.
•n
– Maximum number of PDCHs that can be allocated to the MS according to its multislot class.
© Alcatel 231
© Alcatel 232
Principles
> During a UL or DL packet transmission, the corresponding TBF can be
released due to an abnormal situation:
• no acknowledgement or data received
• the transmission is stalled
• too low transmission efficiency
> The abnormal release is always followed by the re-establishment of the

TBF in case of an uplink transfer (initiative of the MS)
> In case of a downlink transfer, most of the SGSNs do not take the
initiative to re-establish the TBF
>The RLS mechanisms processes in the MFS are based on the following assumption:
>« in a specific transfer situation, the MFS is expecting the MS to behave in a specific way »:
• In a UL TBF, the MFS schedules a USF for UL blocks and expects the MS to understand the MFS’s
acknowledgements.
• In a DL TBF, the MFS sends blocks to the MS and expects them to be acknowledged when scheduled by the
MFS (use of RRBP).
© Alcatel 233
DL TBF (1/2)
Scheduling of “Packet DL Ack/Nack”
DL ACK/NACK PERIOD blocks PACCH block
Stop sending DL
PDTCH PDTCH PDTCH blocks
RRBP PDTCH
≠ false
N3105>N3105_LIMIT
PACCH
Ø N3105 = N3105+1
> The MFS counts the number of consecutive PACKET DL ACK/NACK not received due to loss on the radio interface:
• For a GPRS TBF, if the counter is above the threshold TBF_CS_DL and CS-4, CS-3 or CS-2 is used, the MFS
switches to CS-1.
• For an EGPRS TBF, if the counter is above the threshold TBF_MCS_DL and MCS-9, MCS-8…, MCS-3 or MCS-2
is used, the MFS switches to MCS-1.
• If the counter is above the threshold N3105_LIMIT, the DL TBF is abnormally released:
– the MFS stops sending packets to the MS and sends a message to the SGSN (Radio Status).
– it is up to the SGSN to re-establish the DL TBF.
– the MS releases the TBF on its side.
> If N3105_LIMIT < TBF_CS_DL then the loss of consecutive packet DL ACK/NACK will not trigger a link adaptation but
a TBF release.
> For an EGPRS TBF, the MFS considers EGPRS_N3105_LIMIT.
> N3105_LIMIT = 4 (Alcatel recommended value) and it cannot be set at OMC-R level.
> EGPRS_N3105_LIMIT = 6 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 234
DL TBF (2/2)
Scheduling of “Packet DL Ack/Nack”
DL ACK/NACK PERIOD blocks PACCH block
Stop sending DL
PDTCH PDTCH PDTCH blocks
RRBP PDTCH
≠ false
N_StagnatingWindowDL > NstagnatingWindowDL_LIMIT
PACCH N_StagnatingWindowDL =
Packet DL N_StagnatingWindowDL
Ack/Nack +1
Same oldest RLC block

Nack in the RBB
> Other Abnormal DL TBF release: DL window stalled

• In GPRS acknowledged mode, NstagnatingWindowDL counter shall be incremented when the same oldest RLC
data block in the transmit window is not acknowledged by the last received bitmap.
• If N_StagnatingWindowDL exceeds its limit, then the network shall terminate the TBF.
• NstagnatingWindowDL_LIMIT = 6 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 235
UL TBF - Abnormal Release with Random Access (1/2)
Stop sending “Packet UL
ACK/NACK” PACCH blocks
U U
S S PACCH
F F
N3101>N3101_LIMIT
PDTCH PDTCH
Ø Ø N3101 = N3101+N
N consecutive
Packet Random Access
> N3101_LIMIT = 48 (Alcatel recommended value) and it cannot be set at OMC-R level.
> The MFS manages several counters:

•N3101: number of RLC PDUs consecutively lost since the last reception of a UL RLC PDU:
–N3101 is incremented each time a UL radio block is allocated to the MS and no data is received.
–if N3101 is above N3101_LIMIT, the UL TBF is abnormally released: the MFS stops sending PACKET UL
ACK/NACK to the MS.
•the MS waits for PACKET UL ACK/NACK and then releases the TBF on its side.
•then the MS sends a random access to re-establish the UL TBF.
© Alcatel 236
UL TBF - Abnormal Release with Random Access (2/2)
U PACCH U
S S PACCH
F F
N_StagnatingWindowUL > NstagnatingWindowUL_LIMIT
PDTCH PDTCH
N_StagnatingWindowUL =
SI=1 SI=1 N_StagnatingWindowUL
+1
Packet Random Access
> Other Abnormal UL TBF release: UL window stalled

• SI=1 in a UL RLC DATA BLOCK indicates that the MS transmit window is stalled.
• Upon detection of a stall condition, the network sends a Packet Uplink Ack/Nack message and after a round trip
delay has elapsed, it increments N_ULStagnatingWindow.
• If N_StagnatingWindowUL exceeds its limit, then the network shall terminate the TBF.
• NstagnatingWindowUL_LIMIT = 6 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 237
UL TBF - Abnormal Release with Cell Reselection (1/2)
N3102
PAN_MAX
Packet UL Ack/Nack
received OK RESELECTION
0
UL TBF
PAN_DEC Abnormal
release
PAN_INC Random
Access
>Abnormal release with cell reselection:

•procedure linked to the counter N3102 internal to the MS and initialized to PAN_MAX after each reselection:
–each time the MS performs an abnormal release with random access, it decreases N3102 by PAN_DEC.
–each time the MS receives a PACKET UL ACK/NACK, it increases N3102 by PAN_INC.
–if N3102 reaches 0, the MS performs an abnormal release with cell reselection.
•the MS triggers a cell reselection procedure but nothing allows it to change its serving cell (need of a Master PDCH to
be able to re-select a new cell).
•after the cell reselection, the MS sends a random access to re-establish the UL TBF.
© Alcatel 238
UL TBF - Abnormal Release with Cell Reselection (2/2)
> If a Master PDCH is available in the serving cell
AND
> If RANDOM_ACC_RETRY = Allowed
• Then the following reselection algorithm is applied:
– The MS re-selects the cell with the highest RLA among the 6 best levels
– In this cell, if the MS cannot decode the PBCCH data block, it reselects the
next highest Received Level Average
– If the cells with the 6 strongest RLAs have been tried but cannot be used,
the MS performs a normal reselection (see 3.5 NC0 Cell Selection and
Reselection)
• Else the normal reselection algorithm is applied (see 3.4)
> After T_RESEL, the MS is allowed to reselect the serving cell
> RLA = Received Level Average.
> T_RESEL = 5s (default value).
> Extract of the 05.08 GSM standard:

> In the event of an abnormal release with cell reselection (see 3GPP TS 04.60) when PBCCH exists, an abnormal cell
reselection based on BA(GPRS) shall be attempted. The MS shall perform the following algorithm to determine which
cell to be used for this cell reselection attempt.
> If access to another cell is not allowed, i.e., RANDOM_ACCESS_RETRY bit is not set on the serving cell:
• i) The abnormal cell reselection attempt shall be abandoned.
> If access to another cell is allowed, i.e., RANDOM_ACCESS_RETRY bit is set on the serving cell:
• i) The received level measurement samples taken on the carriers indicated in the BA (GPRS) received on the
serving cell in the last 5 seconds shall be averaged, and the carrier with the highest Received Level Average
(RLA) with permitted BSIC, i.e., the same as broadcast together with BA (GPRS), shall be taken.
• ii) On this carrier, the MS shall attempt to decode the PBCCH data block containing the parameters affecting
cell selection.
• iii) If the cell is suitable (see 3GPP TS 03.22), abnormal cell reselection shall be attempted on this cell.
• iv) If the MS is unable to decode the PBCCH data block or if the conditions in iii) are not met, the carrier with
the next highest Received Level Average (RLA) with permitted BSIC shall be taken, and the MS shall repeat steps
ii) and iii) above.
• v) If the cells with the 6 strongest Received Level Average (RLA) values with permitted BSICs have been tried but
cannot be used, the abnormal cell reselection attempt shall be abandoned.
> The MS is under no circumstances allowed to access a cell to attempt abnormal cell reselection later than 20 seconds
after the detection within the MS of the abnormal release causing the abnormal cell reselection attempt. In the case
where the 20 seconds elapse without a successful abnormal cell reselection, the attempt shall be abandoned.
© Alcatel 239
UL TBF in Ending Phase

U PACCH
U Final PACCH
S S
F F Ack
Scheduling of
“Packet Control Ack”
N3103>N3103_LIMIT
PDTCH PACCH
Final
Block
Ø N3103 = N3103+1
>The MFS can also trigger an abnormal release at the end of a UL TBF:
•the MFS counts the number of PACKET CONTROL ACK not received in response to the PACKET UL ACK/NACK
which indicates the end of the TBF.
•if the counter is above N3103_LIMIT, the UL TBF is abnormally released: the MFS stops sending PACKET UL
ACK/NACK to the MS.
>N3103_LIMIT = 1 (Alcatel recommended value) and it cannot be set at OMC-R level.
© Alcatel 240
UL and DL TBF
> A (E)TX_Efficiency is computed every
• TX_EFFICIENCY_PERIOD transmitted RLC data blocks for a GPRS TBF
• E_TX_EFFICIENCY_PERIOD transmitted RLC data blocks for an EGPRS
TBF
> and compared to the following thresholds:
• TX_EFFICIENCY_ACK_THR in Acknowledged mode
• TX_EFFICIENCY_NACK_THR in Non-Acknowledged mode
> If the TX_Efficiency is below these thresholds, the TBF must be released
> It is done as an abnormal release by the MFS:
• the MFS stops sending DL RLC PDUs in case of a DL TBF
• the MFS stops sending PACKET UL ACK/NACK in case of a UL TBF
Exercise
>Radio Link Supervision based on TX_Efficiency monitoring

•It was proposed since B7 to use the transmission efficiency, i.e., the ratio of the average net bit rate over the gross bit
rate.
•This transmission efficiency can be computed approximately as:
NB _ RECEIVED
ρi
∑
i =1 ni
TX _ EFFICIENCY = 100 NB _ SENT
∑
1
i =1 ni
Where:
NB_SENT is the number of transmitted RLC data blocks,
NB_RECEIVED is the number of correctly received RLC data blocks (i.e., blocks such that a positive
acknowledgment is reported),
ρi is equal to the number of information bits in the i-th correctly received RLC data block divided by the
number of bits per RLC data block with GMSK modulation (456 in GPRS). This ratio only depends on the
coding scheme used for the i-th correctly received RLC data block and is between 0 and 1 in GPRS and
between 0 and 3 in EGPRS (3 because there are 3 information bits per 8-PSK symbol).
ni is the number of RLC data blocks in the i-th radio block. Therefore, this number is always equal to 1 for
GPRS and EGPRS for MCS-1 to MCS-6, and is equal to 2 in EGPRS for MCS 7 to MCS 9.
MCS-
–ρi = 0,40 for CS-1, 0,59
MCS-1 for CS-2,
MCS-2 0.68 forMCS-4
MCS-3 CS-3 andMCS-5
0.94 for CS-4.
MCS-6
7
MCS-8 MCS-9
ρi 0.39 0.49 0.65 0.77 0.98 1.30 2.02 2.45 2.60
• TX_EFFICIENCY is computed during a fixed window of TX_EFFICIENCY_PERIOD data blocks and then compared to
threshold (TX_EFFICIENCY_ACK_THR if Ack mode and TX_EFFICIENCY_NACK_THR if Nack).
Then if TX_EFFICIENCY < Tx_efficiency_threshold then the TBF is release (abnormally).
• TX_EFFICIENCY_ACK_THR = 10%, TX_EFFICIENCY_NACK_THR = 15%, TX_EFFICIENCY_PERIOD = 50

all can be set at OMC-R level.
© Alcatel 241
3.9 Exercises
© Alcatel 242
3.9 Exercises
GPRS CS Adaptation (1/2)
> CS adaptation / DL measurements
• Network parameters:
– MAX_GPRS_CS = CS-2
– TBF_DL_INIT_CS = CS-1
– CS_QUAL_DL_1_2_X_Y = 2
– CS_HST_DL_LT = 2
– CS_HST_DL_ST = 4
• Objective: Find CS used in the DL
Time allowed:
10 minutes
© Alcatel 243
3.9 Exercises
GPRS CS Adaptation (2/2)
> Find which CS is used at each measurement
Measurement 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
RXQUAL_DL 0 0 2 3 4 5 5 5 6 0 0 0 0 6 7 7
AV_RXQUAL_DL_LT 0,0 0,0 1,1 1,9 2,6 3,3 3,8 4,1 4,5 3,5 2,7 2,1 1,7 2,6 3,5 4,2
AV_RXQUAL_DL_ST 0,0 0,0 1,7 2,7 3,8 4,8 5,0 5,0 5,8 1,2 0,2 0,0 0,0 4,8 6,6 6,9
CS ?
7
6
5
4
3
2
1
0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
RXQUAL_DL AV_RXQUAL_DL_LT AV_RXQUAL_DL_ST

Back
>Short term average is calculated with AlphaST = 0.2

>Short term average is calculated with AlphaLT = 0.8
© Alcatel 244
> 3.9 Exercises
RLC ACK Mode: New DL MCS Value Determination (1/3)
> APD=0dB, Type 2 ARQ, GMSK table: APD=0dB, Type 2 ARQ, 8PSK table:
if MCScurrent belongs to {1,2,3,4} if MCScurrent belongs to {5,6,7,8,9}
CV_BEP CV_BEP
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
0 1 1 1 1 1 1 1 1 0 5 5 5 5 1 1 1 1
4 1 1 1 1 1 1 1 1 1 5 5 5 5 1 1 2 2
2 1 1 1 1 1 1 1 1 2 5 5 5 5 1 2 2 2
3 1 1 1 1 1 1 1 1 3 5 5 5 5 2 2 3 3
4 1 1 1 1 1 1 1 1 4 5 5 5 5 2 2 3 3
5 2 2 1 1 1 1 1 1 5 5 5 5 5 5 3 3 3
6 2 2 2 2 1 1 1 1 6 5 5 6 5 5 3 3 3
7 5 2 2 2 2 1 1 1 7 5 5 6 5 5 5 3 3
8 5 2 2 2 2 2 2 2 8 5 5 6 5 5 3 3 4
9 5 2 2 2 2 2 2 2 9 7 6 6 6 5 5 5 4
10 5 3 3 2 2 2 2 2 10 7 6 6 6 5 5 5 5
11 5 3 3 3 3 3 3 3 11 7 6 6 6 6 5 5 5
12 5 3 3 3 3 3 3 3 12 7 6 6 6 6 6 5 5
13 5 3 3 3 3 3 3 3 13 7 6 6 6 6 6 5 5
MEAN_BEP
MEAN_BEP
14 5 5 3 3 3 3 3 3 14 7 6 6 6 6 6 5 6
15 6 5 3 3 3 3 3 3 15 7 7 6 6 6 6 6 6
16 6 5 3 3 3 3 3 3 16 7 7 7 7 6 6 6 6
17 6 5 3 3 3 3 3 3 17 7 7 7 7 7 7 7 6
18 6 5 3 3 3 3 3 3 18 7 7 7 7 7 7 7 7
19 6 6 5 3 3 3 3 4 19 7 7 7 7 7 7 7 7
20 6 6 5 5 3 3 3 4 20 7 7 8 7 7 7 7 7
21 7 6 5 5 3 3 4 4 21 7 8 8 8 8 7 7 7
22 7 6 6 5 5 4 4 4 22 8 8 8 8 8 8 8 8
23 7 6 6 6 5 4 4 4 23 8 8 8 8 8 8 8 8
24 7 7 6 6 5 5 5 4 24 8 8 8 8 8 8 8 8
25 7 7 7 6 6 5 5 5 25 8 8 8 8 8 8 8 8
26 7 7 7 6 6 5 5 5 26 8 8 8 8 9 9 9 9
27 7 7 7 7 6 6 5 5 27 8 8 8 9 9 9 9 9
28 7 7 7 7 6 6 6 6 28 9 9 8 9 9 9 9 9
29 7 7 7 7 7 7 6 6 29 9 9 8 9 9 9 9 9
30 7 7 7 7 7 7 7 7 30 9 9 8 9 9 9 9 9
31 7 7 7 7 7 7 7 9 31 9 9 9 9 9 9 9 9
© Alcatel 245
3.9 Exercises
> Using the previous LA tables and the following
information, fill in the next table:
• APD = 0 dB
• DL RLC mode = ACK
• MS OUT OF MEMORY = Off
Time allowed:
10 minutes
© Alcatel 246
3.9 Exercises
> Find which DL MCS is used at each measurement
1 2 3 4 5 6 7 8
CV_BEP 2 2 2 3 7 5 3 0
MEAN_BEP 20 24 24 18 9 8 5 8
MCSind
New MCS 4

Back
© Alcatel 247
B9
> 3.9 Exercises
RLC ACK Mode: New UL MCS Value Determination (1/3)
> APD=0dB, Type 1 ARQ, GMSK table:

if MCScurrent belongs to {1,2,3,4}
CV_BEP
0 1 2 3 4 5 6 7
0 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1
2 1 1 1 1 1 1 1 1
3 1 1 1 1 1 1 1 1
4 1 1 1 1 1 1 1 1
5 2 2 1 1 1 1 1 1
6 2 2 2 2 1 1 1 1
7 5 2 2 2 2 2 2 2
8 5 2 2 2 2 2 2 2
9 5 2 2 2 2 2 2 2
10 5 3 2 2 2 2 2 3
11 5 3 3 3 3 3 3 3
12 5 5 3 3 3 3 3 3
13 5 5 3 3 3 3 3 3
MEAN_BEP
14 6 5 3 3 3 3 3 3
15 6 5 3 3 3 3 3 3
16 6 5 5 3 3 3 3 3
17 6 5 5 3 3 3 3 3
18 6 5 5 3 3 3 3 3
19 6 6 5 5 3 3 3 4
20 6 6 5 5 5 3 3 4
21 7 6 6 5 5 4 4 4
22 7 6 6 5 5 5 4 4
23 7 6 6 6 5 5 5 4
24 7 6 6 6 6 5 5 4
25 7 7 7 6 6 5 5 5
26 7 7 7 6 6 5 5 5
27 7 7 7 7 6 6 6 5
28 7 7 7 7 6 6 6 6
29 7 7 7 7 7 7 6 6
30 7 7 7 7 7 7 6 6
31 7 7 7 7 7 7 7 9
© Alcatel 248
3.9 Exercises B9
> Using the previous LA table and the following
information, fill in the next table:
• APD = 0 dB
• DL RLC mode = ACK
Time allowed:
20 minutes
© Alcatel 249
3.9 Exercises B9
> Find which UL MCS is used every 12 radio blocks
1 2 3 4 5 6 7 8 9 10 11 12
CV_BEP 2 1 2 1 3 7 5 3 0 2 5 7
MEAN_BEP 20 20 24 24 18 9 8 5 8 10 18 8
MCSind
N_inf 0
N_sup 0
New MCS 2
13 14 15 16 17 18 19 20 21 22 23 24
CV_BEP 5 2 1 3 2 1 2 5 2 3 7 3
MEAN_BEP 8 7 8 12 16 20 24 10 12 7 20 27
MCSind
N_inf 0
N_sup 0
New MCS

Back
© Alcatel 250
3.9 Exercises
> Replace the ‘?’ by the right values in the 6 next
cases
> Cases 1a, 1b and 1c:
• EN_FULL_IR_DL = disabled
> Case 2:
• EN_FULL_IR_DL = enabled
> Cases 3a and 3b:
• MS OUT OF MEMORY = On
Time allowed: • EN_FULL_IR_DL = disabled
20 minutes

Back
© Alcatel 251
3.9 Exercises
> Case 1a: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = disabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1
DL RLC data blocks B5+B6, MCS7, PS1, + polling request
EGPRS Packet DL Ack/Nack (B2 not received) MCS4 commanded by

the Link Adaptation
algorithm
DL RLC data block first part B2, MCS?, PS?
DL RLC data block second part B2, MCS?, PS?
DL RLC data block B7, MCS?, PS?
© Alcatel 252
3.9 Exercises
> Case 1b: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = disabled
MS BSS

the Link Adaptation
algorithm
© Alcatel 253
3.9 Exercises
> Case 1c: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = disabled
MS BSS
EGPRS Packet DL Ack/Nack (B2 and B4 not received)
DL RLC data blocks B2+B4, MCS?, PS?
© Alcatel 254
3.9 Exercises
> Case 2: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = enabled
MS BSS

the Link Adaptation
algorithm
© Alcatel 255
3.9 Exercises
> Case 3a: MS OUT OF MEMORY = On, EN_FULL_IR_DL = disabled
MS BSS
EGPRS Packet DL Ack/Nack (B2 and B4 not received,

MS OUT OF MEMORY = On)
© Alcatel 256
3.9 Exercises
> Case 3b: MS OUT OF MEMORY = On, EN_FULL_IR_DL = disabled
MS BSS
EGPRS Packet DL Ack/Nack (B2 not received,

MCS4 commanded by
MS OUT OF MEMORY = On)
the Link Adaptation
algorithm
DL RLC data block first part B2, MCS?, PS?
DL RLC data block second part B2, MCS?, PS?

Back
© Alcatel 257
3.9 Exercises
NC0 Cell Selection and Reselection (1/3)
> Master Channel is NOT used
> Network configuration is explained hereafter
> The MS (2W, class B) is selecting a first cell and
immediately starts a transfer
• Objective: Find cells selected by the MS
CI=1823
GSM900 CI=6271
GSM900
Cell 3 (8557, 1823)
CI=6270
GSM900
Time allowed:
Cell 2 (8564,6169)
10 minutes
CI=6169
GSM900
CI=1964
GSM900

Cell 1 (8564, 1964)
© Alcatel 258
3.9 Exercises
> Parameters settings
• For all cells:
– RX_LEV_ACCESS_MIN = -103 dBm
– MS_TXPWR_MAX_CCH_= 33 dBm
– PENALTY_TIME = 0 (20s) CI=1823
GSM900 CI=6271
GSM900
Cell 3 (8557, 1823)
– TEMPORARY_OFFSET = 0 dB
– CELL_RESELECT_OFFSET = 0 dB
CI=6270
GSM900
• CELL_RESELECT_HYSTERESIS
– Cell 1: 4 dB
– Cell 2: 6 dB Cell 2 (8564,6169)
– Cell 3: 6 dB
CI=6169
GSM900
CI=1964
GSM900
Cell 1 (8564, 1964)

© Alcatel 259
3.9 Exercises
> Find the cell selected by the MS
Measurements RxLev (1) RxLev (2) RxLev (3)
1 -80 -96 -104

2 -84 -90 -100 CI=1823
GSM900 CI=6271
GSM900
Cell 3 (8557, 1823)
3 -88 -90 -87
CI=6270
4 -88 -87 -82 GSM900
5 -89 -85 -77
Cell 2 (8564,6169)
CI=6169
GSM900
CI=1964
GSM900
Cell 1 (8564, 1964)

Back
© Alcatel 260
3.9 Exercises B9
NC2 Cell Reselection (1/3)
> Parameters settings
• For all cells:
– RX_LEV_ACCESS_MIN = -103 dBm
– MS_TXPWR_MAX_CCH_= P = 33 dBm
– PENALTY_TIME = 0 (20s)
– T_NC_PING_PONG = 0s
– NC_PING_PONG_OFFSET = 0 dB
– THR_NC2_LOAD_RANKING = 70 %
> Objectives:
• Fill in the following table
• Find the best candidate cell
Time allowed:
20 minutes

Back
© Alcatel 261
3.9 Exercises B9
> All the cells belong to the same BSS
Cell1 Cell2 Cell3 Cell4 Cell5
Cell Type
Micro micro umbrella umbrella umbrella
Load Average 10% 0% 80% 20% 30%
AV_Rxlev_NC2 -78 dBm -70 dBm -82 dBm -85 dBm -88 dBm
HCS_THR -75 dBm -75 dBm -90 dBm -90 dBm -90 dBm
CRO +20 dB +20 dB 0 dB 0 dB 0 dB
EN_OUTGOING_GPRS_REDIR disabled enabled disabled disabled disabled
C1NC2
C31NC2
Load situation
C2NC2
© Alcatel 262
3.9 Exercises
> GPRS redirection
> Find a parameter setting ensuring that when the
MS enters the Packet Transfer Mode, it is
redirected towards a macro cell
Macro cell
GPRS
Redirection
Micro cell Micro cell
Time allowed:
10 minutes

Back
© Alcatel 263
3.9 Exercises
Radio Link Supervision
> List in the DL and UL the different cases of
abnormal release
Time allowed:
10 minutes

Back
© Alcatel 264
4 ALGORITHMS DYNAMIC BEHAVIOR
© Alcatel 265
> Objective: to be able to estimate qualitatively the impact of a
parameter change in order to solve the typical problems or
enhance the GPRS performance
> Program:
4.1 Optimization of CS Adaptation
4.2 Optimization of Cell Reselection
4.3 Enhance the (E)GPRS Performance
© Alcatel 266
© Alcatel 267
Quiz
> Why CS_QUAL_XX_I_J_X_NACK <
CS_QUAL_XX_I_J_X_ACK, by default?
> What is the meaning of

CS_SIR_DL_3_4_FH_NACK = 15?
> What is the meaning of

CS_QUAL_UL_3_4_FH_NACK = 0?
Time allowed:
15 minutes
© Alcatel 268
Qualitative Impact
> Fill in the table
Change Qualitative Impact
N_AVG_I
CS_QUAL_DL_1_2_X_Y
CS_SIR_DL_3_4_X_Y
CS_HST_UL_LT
© Alcatel 269
© Alcatel 270
> Case 1: Multilayer network with PBCCH

• Use NC0 with C31 and C32
> Case 2: Multilayer network without PBCCH

• Use Outgoing GPRS redirection
– Tuning of NC2 parameters
> Case 3: NC2 parameters versus HO parameters
© Alcatel 271
Case 1: Multilayer Network with PBCCH (1/2)
> Cell reselection for CS traffic
• Aim: favor cell reselection on micro cells for slow mobiles
CRO=0dB
PENALTY_TIME=20s
TEMPORARY_OFFSET=0dB
Macro cell
Slow
mobiles
CRO=10dB
PENALTY_TIME=60s
TEMPORARY_OFFSET=40dB
© Alcatel 272
Case 1: Multilayer Network with PBCCH (2/2)
> Cell reselection for PS traffic
• Aim: favor cell reselection on macro cells for all mobiles
• Use C31 and C32 PRIORITY_CLASS=?
HCS_THR=?
Macro cell
PS
traffic
PRIORITY_CLASS=?
HCS_THR=?
© Alcatel 273
Case 2: Multilayer Network Without PBCCH
> Cell reselection for PS traffic
• Aim: favor cell reselection on macro cells for all mobiles
• Use Outgoing GPRS redirection
NC_DL_RXLEV_LIMIT_THR=?
Macro cell
Macro cell
LOADED
GPRS
redirection ? ? ? ? ?
Micro cell Micro cell Micro cell
NC_DL_RXLEV_LIMIT_THR=?
? ?
: NC_RESELECT_HYSTERESIS(micro, Macro) : NC_RESELECT_HYSTERESIS(micro, micro)
: NC_RESELECT_HYSTERESIS(Macro, micro)
© Alcatel 274
Case 3: NC2 Parameters Versus HO Parameters (1/2)
> Link the NC2 parameters to their equivalent HO parameters
NC2 HO
NC_RXQUAL_AVG_PERIOD
L_RXLEV_DL_H
A_QUAL_HO
NC_UL_RXQUAL_THR
L_RXQUAL_DL_H
NC_DL_RXQUAL_THR
HO_MARGIN
NC_DL_RXLEV_THR
A_LEV_HO
NC_RESELECT_HYSTERESIS
L_RXQUAL_UL_H
> L_RXLEV_DL_H
• Downlink level threshold for handover.
> A_QUAL_HO
• Window size for quality averages for handover.
> L_RXQUAL_DL_H
• Downlink quality threshold for handover for non AMR calls.
> HO_MARGIN
• Difference in power budget (PBGT) between cell(0) and cell(n) which is required for a power budget HO.
> A_LEV_HO
• Window size for level averages for handover.
> L_RXQUAL_UL_H
• Uplink quality threshold for handover for non-AMR calls.
© Alcatel 275
Case 3: NC2 Parameters Versus HO Parameters (2/2)
> Fill in the table
Change Qualitative Impact
NC_RXQUAL_AVG_PERIOD
NC_UL_RXQUAL_THR
NC_DL_RXQUAL_THR
NC_DL_RXLEV_THR
NC_RESELECT_HYSTERESIS
© Alcatel 276
© Alcatel 277
GPRS Services
Always-on Media Fun

• Games (Hangman, Poker, etc.)
Directories • Screen Saver
• Yellow/White Pages
• Ring Tone
Mobile Office • International Directories
• Horoscope
• Voice (!) • Operator Services
• Biorhythm
• E-mail
• Agenda Music
• IntraNet/InterNet • Downloading of
• Corporate Applications Transportation music files or
• Database Access • Flight/train Schedule video clips
• reservation News
(general/specific)
• International/National News Location services
• Local News • Traffic Conditions
Vertical application • Sport News • Itineraries
• Weather • Nearest Restaurant,
•Traffic Management • Lottery Results Cinema, Chemist,
•Automation • Finance News, etc. Parking, ATM, etc.
•Mobile branches
•Health
M-commerce
Non physical
• on-line Banking Physical
• Ticketing • On-line shopping
• Auction • On-line food
• Gambling, etc.
© Alcatel 278
GPRS Services vs QoS Criteria
> According to the service type, the QoS criteria to take into account are
different
GPRS and EGPRS Key QoS criteria
Services
WAP Access delay
WEB Browsing (http) - Access delay

- Throughput
Video streaming Throughput
File transfer (ftp) BER
E-mail (smtp) BER
© Alcatel 279
Examples
> Data applications use TCP/IP protocol layers which have a great
impact on the end user QoS
FTP above TCP/IP layers
FTP
TCP relay relay relay
IP relay relay IP IP IP IP IP
PPP PPP SNDCP SNDCP GTP GTP

P P
LLC relay LLC UDP UDP
First IP router Last IP router
RLC RLC BSSGP BSSGP IP-Gn IP-Gn
MAC MAC NS NS L2 L2
RF RF L1 L1 L1’ L1’
(*)
BSS GGSN
TE (PC MS SGSN
,PDA …) R Um Gn Gi
Gb
TCP data segment
Possible repartition on the end to end path of the TCP flight size TCP acknowledgement
(*) this graphical representation is used to

express the fact that many data segments are
currently waiting to be transmitted on the
represented link and are stored in buffers of the
device handling the link . It doesn’t mean that
simultaneous segments are being transmitted.
© Alcatel 280
PDU Lifetime and TCP Performance (1/3)
> Impact on TCP performance
Throughput
Time
Congestion Window increase CW CW increase CW
decrease decrease
© Alcatel 281
LLC frames TCP/IP frames
SGSN GGSN
TCP
PDU Life server
Time
TCP Window = 16 KB
MFS
SGSN GGSN
TCP
server
TCP Window = 64 KB
MFS
>We observe a break within each FTP transfer.
>We observe within the Gb traces several "LLC Discarded" messages, just before the TCP starts retransmissions. Those "LLC
discarded" messages show that several kilobytes of data are discarded by the BSS.
>This LLC frame discarding is caused by a "PDU lifetime" timer expiry: indeed this parameter is set by the SGSN to ** 8
seconds **.
>Clearly this value is not enough as the RTT (TCP Round Trip Time) with a TCP window of 64 KB is roughly 12.3 seconds.
>As most of the RTTs are composed of queuing in the BSS buffers, this inevitably causes PDU lifetime expiry.
>This is a normal behavior as at the beginning of a transfer, the FTP server increases continuously its congestion window.
The BSS has to send more and more data with the same radio bandwidth.
© Alcatel 282
> Solution:
• Increase the PDU Life Time (SGSN parameter)
• PDU Life Time = 63s
SGSN GGSN
FTP
PDU Life server
Time
TCP Window = 64 KB
MFS
© Alcatel 283
TCP Window Size and FTP Performance (1/2)
> TCP/IP packet:
40 bytes
TCP/IP
Header
MSS
MTU
• MSS: The maximum number of user data bytes that can be included in
the packet without fragmentation.
• MTU: The maximum number of bytes that can be sent in a single
packet.
• TCP window size: the period used for acknowledgment. Its value is a
multiple of the MSS (x4, 8, 16, 32). The maximum value is 65.535 (64
KB).
> MSS: Maximum Segment Size.
> MTU: Maximum Transfer Unit.
> A too large MTU size may mean retransmissions if the packet encounters a router that cannot handle that size of packet.
A too small MTU size means relatively more header overhead and more acknowledgements that have to be sent and
handled.
© Alcatel 284
TCP Window Size and FTP Performance(2/2)
> Maximum throughput obtained with MTU = 1500 bytes and

TCP window size = 8 (x1460 bytes).
>The throughput has been calculated at the application layer.
>N* is the number which permits to reach, by multiplying the MSS, a Window Size close to the maximal allowable value of
65.535 Bytes.
> The downloaded file has a size of 1 MB.
> The table below illustrates the results:

MSS Multiplying MTU of 500 Bytes MTU of 576 Bytes MTU of1000 Bytes MTU of 1500 Bytes
Integer
4 1.391 1.628 2.95 2.91
8 2.681 2.952 4.016 4.111
16 3.812 3.877 4.045 4.113
32 3.813 3.878 4.043 4.125
N* 3.808 3.88 4.051 4.092
> 1500 Bytes is the best MTU size because it permits to reach the maximum throughput value. But it is important to note
that even if the MTU size is set to 500 Bytes, the throughput can reach a high value close to the maximum.
>The asymptote characterizing the graph can be explained by the fact that the GPRS network limits the throughput. Even if
the client can receive many TCP packets without acknowledging them, the file downloading can not be faster.
>The recommended value of MTU size should be 1500 Bytes. This value is the best because the TCP window size, which
permits to reach the maximum throughput, is the smallest. In fact, with a small TCP window size, retransmission can be
avoided.
© Alcatel 285
END OF SESSION
© Alcatel 286
5 APPENDIX
© Alcatel 287
Appendix B9
> Content:
5.1 OMC-R B9 Screens Display
5.2 System Information Broadcasting
5.3 Detailed Available Throughput Computation
5.4 Examples of Puncturing Schemes
5.5 B9 Features Summary
5.6 Training Exercises Solutions
© Alcatel 288
Appendix B9
5.1 OMC-R B9 Screens Display (BSS)
© Alcatel 289
Appendix B9
© Alcatel 290
Appendix B9
© Alcatel 291
Appendix B9
© Alcatel 292
Appendix B9
© Alcatel 293
Appendix B9
© Alcatel 294
Appendix B9
© Alcatel 295
Appendix B9
© Alcatel 296
Appendix B9
© Alcatel 297
Appendix B9
© Alcatel 298
Appendix B9
5.1 OMC-R B9 Screens Display (Cell)
© Alcatel 299
Appendix B9
© Alcatel 300
Appendix B9
© Alcatel 301
Appendix B9
© Alcatel 302
Appendix B9
© Alcatel 303
Appendix B9
© Alcatel 304
Appendix B9
© Alcatel 305
Appendix B9
© Alcatel 306
Appendix B9
© Alcatel 307
Appendix B9
© Alcatel 308
Appendix B9
© Alcatel 309
Appendix B9
5.1 OMC-R B9 Screens Display (Adjacency)
© Alcatel 310
Appendix
5.2 System Information Broadcasting on BCCH (1/2)
> The BCCH indicates if GPRS is supported in the cell:
• SI 3: RA_COLOUR field present if GPRS supported
> If GPRS is supported:

• SI13 is broadcast on the BCCH
• SI13 broadcast instead of retransmission of SI 1
> SI 4 content:
• SI13_PBCCH_LOCATION: gives SI 13 schedule or PBCCH location
>Note: do not confuse RA_COLOUR and RA Code. The former is used as a flag which has two uses for the MS entering
a new cell:
•To know if the GPRS service is supported in the cell (RA_COLOUR has a value different from -1).
•To trigger an RA update when the value of the RA_COLOUR changes. It is easy to monitor because it is broadcast
often.
>The Routing Area Code is necessary for the RA update procedure (message content).
>The SI13 takes the place of a few SI1 occurrences.
© Alcatel 311
Appendix
5.2 System Information Broadcasting on BCCH (2/2)
> SI 13 content (non-exhaustive list):
• RA_CODE: routing area code
• NMO: Network Mode of Operation
• PAN_DEC, PAN_INC, PAN_MAX: radio link supervision
• ALPHA: uplink power control
• T_AVG_T, T_AVG_W: MS calculation of average levels
• PC_MEAS_CHAN: level measurements on BCCH / PDCH
• NETWORK_CONTROL_ORDER:
– if set to NC0 = MS controlled cell reselection, no measurement reporting
– If set to NC2 = Network controlled cell reselection, thanks to measurement
reporting from the MS
• GPRS MA: for hopping SPDCH group
• ACCESS_BURST_TYPE
> The MS has to get SI13 information on a regular basis:

•each time the SI13 content is updated (PSI field = SI13_CHANGE_MARK set to 1).
•every 30 seconds max (even if the TBF has to be interrupted).
> Through 2 different ways: SI13 on the BCCH or PSI13 in a PACCH block.
> The MS has always the time to switch on PSI13 in NMOIII and/or NMOI with a Master PDCH because PBCCH blocks
are always after an I or X TS within the 52 multiframe.
>Access Burst Type: it defines the access burst (8 bits or 11 bits) to be used on the PRACH, PTCCH and the “Packet
Control Ack” on a PACCH.
>When the Master Channel is present in the cell, the System Information Type 13 message has different contents from
those described above. It mainly consists of:
•The radio description of the Primary Master Channel (in terms of time slot number, training sequence code and
frequency parameters).
•One GPRS Mobile Allocation (MA), if frequency hopping is used for GPRS. This is the GPRS MA of the Primary
Master Channel, if hopping. If the Primary Master Channel is not hopping, the MA corresponds to the hopping
TRX(s) used for GPRS, if any.
>Three modes of cell reselection have been defined by the 3GPP Standard for GPRS MSs. These Network Control (NC)
modes, known as the NC0, NC1 and NC2, are shortly described below:
•NC0: the GPRS MS performs autonomous cell reselection without sending measurement reports to the network.
•NC1: the GPRS MS performs autonomous cell reselection. Additionally it sends measurement reports to the
network.
•NC2: the GPRS MS shall not perform autonomous cell reselection. It sends measurement reports to the network.
The network controls the cell reselection.
© Alcatel 312
Appendix
5.2 System Information Broadcasting on PBCCH (1/3)
> If a primary MPDCH is available, a GPRS MS monitors the PBCCH
> PSI blocks available: PSI1, PSI2, PSI3, PSI3bis, PSI8, PSI13
> PSI1, PSI2 and PSI13 (=SI13 on BCCH) can be sent in a PACCH block
for an MS in Packet Transfer Mode
> PSI1 content:
• Cell and BSS parameters
• PRACH access control parameters
• PCCCH organization parameters
• Power Control parameters
• CN features (MSC Release, SGSN Release)
>Cell Parameters = NMO, MS Timers, DRX info, RLS parameters, etc.

>PRACH access control parameters = access burst type, access control class, etc.
>PCCCH organization parameters = BS_PBCCH_BKLS, BS_PAGCH_BLKS_RES, BS_PRACH_BLKS
>The GPRS cell adjacencies are the same for an MS in Packet Idle Mode as for an MS in Packet Transfer Mode.
>The GPRS cell adjacencies are equal to CS cell adjacencies.
© Alcatel 313
Appendix
> PSI2 content:
• Cell identification (PLMN Id, LAC, RAC, Cell Id)
• Non-GPRS O&M parameters (BS_PA_MFRMS, BS_AG_BLKS_RES)
• PCCCH information (TS and frequencies)
• Cell allocation information (HSN, BCCH band, frequency channels)
> PSI3 /PSI3bis content:
• BCCH allocation in neighboring cells
• Serving cell parameters (GPRS_RXLEV_ACCESS_MIN,
GPRS_MS_TXPWR_MAX_CCH)
• General reselection parameters of serving and neighboring cell
• Neighbor cell parameters
>PSI3, PSI3bis:
•One PSI3 instance shall be sent and, as a minimum, one PSI3bis instance shall be sent as well
•There may be up to 16 PSI3bis instances.
• Reselection parameters: C31_HYST, C32_HYST, GPRS_CELL_RESELECT_HYST, PRIORITY_CLASS, HCS_THR,
RA_RESELECT_HYSTERESIS
• Neighboring cell parameters: BSIC, BCCH frequency, SI13 PBCCH location, GPRS_RXLEV_ACCESS_MIN,
GPRS_MS_TXPWR_MAX_CCH, GPRS_TEMPORARY_OFFSET, GPRS_PENALTY_TIME,
GPRS_RESELECTION_OFFSET.
•Up to 32 neighboring cells may be defined. The field Same_RA_As_Serving_Cell provides complementary
information for the reselection process.
© Alcatel 314
Appendix
> PSI8 content:
• Optionally sent on the PBCCH
• Cell broadcast information
– CBCH channel description (TS number)
– Frequency parameters for hopping CBCH
– Frequency parameters for non-hopping CBCH (TSC, ARFCN)
> TSC: the Training Sequence Code used for CBCH is the BCC value.
> MAIO: Mobile Allocation Index Offset.
> HSN: Hopping Sequence Number (law for frequency hopping).
> MA_bitmap: MA_Bitmap is related to the BCCH band location.
> MA_length: the length of the MA_bitmap, giving the number of frequency to hop on.
© Alcatel 315
Appendix
5.2 System Information Broadcasting on PACCH
> PSI broadcast on PACCHs is controlled at MAC layer by the O&M
parameters T_PSI_PACCH
> PSI13 content:
• GPRS cell access information (RA_CODE, NCO, ACCESS_BURST_TYPE,
etc.)
• Radio Link Supervision parameters, Power control information
• MS timers for TBF establishment (T3168, T3182, etc.)
>When there is no Master Channel, the GPRS mobiles have to read the System Information Type 13 message at least
once every 30 seconds. Because of this, GPRS mobiles in data transfer may lose data. In order to avoid this, the Packet
System Information Type 13 message is sent to each MS doing data transfer, via its assigned downlink Packet Associated
Control Channel (PACCH). This message provides the same information as the System Information Type 13 message on
BCCH. The PSI Type 13 message is not used when there is a Master Channel.
>The GPRS cell information as well as the Radio Link Supervision and the Power Control information are similar to the
one included in the SI13 on the BCCH.
>T3168, T3164, T3182, T3190, T3180: refer to their use for TBF establishment and Radio Link Control (causes of TBF
releases at the MS side). We can note that the MS timer names use even numbers when the BSS one uses odd numbers.
>T_PSI_PACCH = 14s (Alcatel recommended value) but it can be set at OMC-R level.
© Alcatel 316
Appendix B9
> available_throughput_candidate_XL is
• the overall throughput provided by its PDCHs
• It depends on:
– the potential throughput of its PDCHs
– potential_throughput_PDCH
– the available capacity on each of its PDCHs
– available_capacity_PDCH_XL
> For a GPRS TBF
• Potential_throughput_PDCH = R_AVERAGE_GPRS
• Available_capacity_PDCH_XL = (1 – USED_CAPACITY_GBR_XL * (1 +
QOS_SAFETY_MARGIN/100)) /
(Nb_BE_TBF_HIGHER_PRIOR_XL*SCHEDULING_PRIORITY_FACTOR +
Nb_BE_TBF_SAME_PRIOR_XL + 1)
> Same formulas are used for an EGPRS TBF with R_AVERAGE_EGPRS and
only the EGPRS TBFs are considered
© Alcatel 317
Appendix B9
> USED_CAPACITY_GBR_XL
• total PDCH capacity that has already been allocated to RT PFCs (both
GPRS and EGPRS) on the PDCH in the XL direction
• RT PFCs: Real Time Packet Flow Context
> Nb_BE_TBF_HIGHER_PRIOR_XL (respectively
Nb_BE_TBF_SAME_PRIOR_XL)
• total number of Best Effort TBFs (GPRS or EGPRS)
– which have some radio resources allocated on the considered PDCH in the
XL direction
– and whose priority (combination of THP and Precedence) is strictly higher
than (respectively equal to) the priority of the TBF to establish / reallocate
– THP: Traffic Handling Priority
» QoS parameter used for the interactive traffic class
© Alcatel 318
Appendix B9
> For a given candidate time slot allocation with n PDCHs
• available_capacity_candidate_XL = ∑i=1 to n available_capacity_PDCHi_XL
> available_throughput_candidate_XL = potential_throughput_PDCH *

available_capacity_candidate_XL
> For a GPRS TBF, in case of only BE TBFs with the same priority
n
1
• available_throughput_candidate_XL = R_AVERAGE_GPRS * ∑ NB_TBF
i =1 PDCHi +1
> For a GPRS TBF, in case of only BE TBFs with the same priority
n
1
• available_ throughput _candidate_XL = R_AVERAGE_EGPRS * ∑ NB_TBF
i =1 PDCHi +1
>NB_TBFPDCHi represents the number of already allocated GPRS and EGPRS TBFs on the PDCH i, in case of GPRS
allocation.
>NB_TBFPDCHi represents the number of already allocated EGPRS TBFs on the PDCH i, in case of EGPRS allocation.
© Alcatel 319
Appendix
> The 05.03 GSM recommendation (Channel coding) indicates for each
MCS the available puncturing schemes
MCS switched from PS of last transmission before MCS switch
MCS switched to PS of first transmission after MCS switch
MCS-1 PS1, PS2
MCS-2 PS1, PS2
MCS-3 PS1, PS2, PS3
MCS-4 PS1, PS2, PS3
MCS-5 PS1, PS2
MCS-6 PS1, PS2
MCS-7 PS1, PS2, PS3
MCS-8 PS1, PS2, PS3
MCS-9 PS1, PS2, PS3
> The puncturing process consists of transmitting only some of the coded bits obtained after the rate 1/3 convolutional
coding. Depending on the considered puncturing scheme, different coded bits are transmitted. Therefore, when the
receiver receives two versions of the same RLC block sent with two different puncturing schemes, it obtains additional
information leading to an increased decoding probability.
© Alcatel 320
Appendix
> Coding and puncturing for MCS-7; rate 0.76 8PSK, two RLC blocks
per 20ms 3 bits 45 bits 468 bits 468 bits
USF RLC/MAC HCS E FBI Data = 448 bits BCS TB E FBI Data = 448 bits BCS TB
Hdr.
Rate 1/3 convolutional coding Rate 1/3 convolutional coding
36 bits 135 bits 1404 bits 1404 bits
puncturing puncturing
puncturing
SB = 8 36 bits 124 bits 612 bits 612 bits 612 bits 612 bits 612 bits 612 bits
P1 P2 P3 P1 P2 P3
1392 bits
> For MCS-7, the data part of the RLC block contains 468 bits. The rate 1/3 convolutional coding gives 1404 bits: C(0),
C(1), ..., C(1403). The code is then punctured depending on the value of the CPS field as defined in the 04.60 GSM
recommendation. Three puncturing schemes named P1, P2 and P3 are applied in such a way that the following coded
bits are transmitted:
P1 {C(18j), C(1+18j), C(4+18j), C(8+18j), C(11+18j), C(12+18j), C(13+18j), C(15+18j)
for j = 0,1,...,77} are transmitted
except {C(k) for k = 1,19,37,235,415,595,775,955,1135,1351,1369,1387} which are not transmitted
P2 {C(2+18j), C(3+18j), C(5+18j), C(6+18j), C(10+18j), C(14+18j), C(16+18j), C(17+18j)
except {C(k) for k = 16,34,52,196,376,556,736,916,1096,1366,1384,1402} which are not transmitted
P3 {C(2+18j), C(5+18j), C(6+18j), C(7+18j), C(9+18j), C(12+18j), C(13+18j), C(16+18j)
except {C(k) for k = 13,31,49,301,481,661,841,1021,1201,1363,1381,1399} which are not
transmitted
> The result is a block of 612 (8*78 - 12) coded bits.
© Alcatel 321
Appendix
> Coding and puncturing for MCS-5; rate 0.37 8PSK, one RLC block per
20 ms 3 bits 33 bits 468 bits
USF RLC/MAC HCS E FBI Data = 56 octets = 448 bits BCS TB

Hdr.
Rate 1/3 convolutional coding
36 bits 99 bits 1404 bits
puncturing
+1 bit
P1 P2
SB = 8 36 bits 100 bits 1248 bits 1248 bits
1392 bits
© Alcatel 322
Appendix
> Coding and puncturing for MCS-4; uncoded GMSK, one RLC block
per 20 ms 3 bits 36 bits 372 bits

Hdr.
puncturing
puncturing
SB = 12 12 bits 68 bits 372 bits 372 bits 372 bits
P1 P2 P3
464 bits
© Alcatel 323
Appendix
> Coding and puncturing for MCS-1; rate 0.53 GMSK, one RLC block
per 20 ms 3 bits 36 bits 196 bits

Hdr.
puncturing
puncturing
SB = 12 12 bits 68 bits 372 bits 372 bits
P1 P2
464 bits

Back
> For MCS-1, the data part of the RLC block contains 196 bits. The rate 1/3 convolutional coding gives 588 bits: C(0),
C(1), ..., C(587). The code is then punctured depending on the value of the CPS (Coding and Puncturing Scheme
indicator) field (EGPRS RLC/MAC header) as defined in the 04.60 GSM recommendation (RLC/MAC). Two puncturing
schemes named P1 and P2 are applied in such a way that the following coded bits are not transmitted:
P1 {C(2+21j), C(5+21j), C(8+21j), C(10+21j), C(11+21j), C(14+21j), C(17+21j), C(20+21j) for j =

0,1,...,27} are not transmitted except {C(k) for k = 73,136,199,262,325,388,451,514} which are
transmitted
P2 {C(1+21j), C(4+21j), C(7+21j), C(9+21j), C(13+21j), C(15+21j), C(16+21j), C(19+21j) for j =
0,1,...,27} are not transmitted except {C(k) for k = 78,141,204,267,330,393,456,519} which are
transmitted
> The result is a block of 372 (588 - 8*28 + 8) coded bits.
© Alcatel 324
Appendix B9
5.5 B9 Features Summary
> M-EGCH link
> Autonomous packet resource allocation
• The MFS fully manages the SPDCH use
• The TBF allocation is directly based on the throughput
> Extended UL TBF mode
> 8-PSK in UL
> IR in UL
> NACC and PSI status
• NC0
• NC2
> Enhanced packet cell reselection
• Load criterion
© Alcatel 325
www.alcatel.com
© Alcatel 326

3fl11830abaawbzza PDF

Uploaded by

Document Information

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

3fl11830abaawbzza PDF

Uploaded by

Copyright:

Available Formats

EVOLIUM Base Station Subsystem

GPRS & EGPRS Radio Algorithms Description / B9

© All rights reserved. Passing on and copying of this document,

Audience Course content

Note: Please print this document with comments pages

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 6

All rights reserved © 2004, Alcatel

1.1 Service Overview

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 8

All rights reserved © 2004, Alcatel

> Circuit switching:

GPRS and E-GPRS Radio Algorithms Description / B9 9

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 10

All rights reserved © 2004, Alcatel

All rights reserved © 2004, Alcatel

> Class 8 (4+1):

GPRS and E-GPRS Radio Algorithms Description / B9 12

All rights reserved © 2004, Alcatel

>All multislot classes are supported with the following limitations:

1.2 Alcatel GPRS Architecture

All rights reserved © 2004, Alcatel

Radio Access Network

GPRS & EGPRS Core Network

GPRS and E-GPRS Radio Algorithms Description / B9 14

All rights reserved © 2004, Alcatel

> PDN X25 is not supported anymore by 3GPP.

Pure Signaling GPRS Network

GPRS and E-GPRS Radio Algorithms Description / B9 15

All rights reserved © 2004, Alcatel

> GPRS network = IP network

> Signaling protocols:

> Additional interfaces:

GPRS and E-GPRS Radio Algorithms Description / B9 16

All rights reserved © 2004, Alcatel

Radio Interface Abis Ater Gb

BTS BSC MFS SGSN

GPRS and E-GPRS Radio Algorithms Description / B9 17

All rights reserved © 2004, Alcatel

MS BTS MFS SGSN

GPRS and E-GPRS Radio Algorithms Description / B9 18

All rights reserved © 2004, Alcatel

MS BTS BSC MFS

GPRS and E-GPRS Radio Algorithms Description / B9 19

All rights reserved © 2004, Alcatel

>2 GSLs at 64Kbit/s per GPU.

1.3 Main Transactions

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 21

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 22

All rights reserved © 2004, Alcatel

GPRS and E-GPRS Radio Algorithms Description / B9 23

All rights reserved © 2004, Alcatel

> 2 types of PCH/PPCH use shall be kept distinct for PS procedures:

GPRS Attach GPRS Detach

GPRS and E-GPRS Radio Algorithms Description / B9 24

All rights reserved © 2004, Alcatel

The MS enters a new

New cell belongs to a new RA New cell belongs to a new LA

RA update RA/LA update