3fl11830acaawbzza 03

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
3FL11830ACAAWBZZA3 Edition 03
TRAINING MANUAL
EVOLIUM - E-GPRS Radio Algorithms and Parameters Description B10

All rights reserved 2007, Alcatel-Lucent
Copyright 2007 by Alcatel-Lucent - All rights reserved Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved 2007, Alcatel-Lucent E-GPRS Radio Algorithms and Parameters Description B10 - Page 1
Legal Notice
2
Switch Safety Warning
to notes view!
Both lethal and dangerous voltages are present within the equipment. Do not wear conductive jewelry 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-Lucent. 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-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without EVOLIUM Alcatel-Lucents writtenParameters Description must include all copyright and other proprietary notices. No permission, and E-GPRS Radio Algorithms and All Rights Reserved Alcatel-Lucent 2007 other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to B10 any party in any manner whatsoever without prior written permission from Alcatel-Lucent. 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-Lucent. Alcatel-Lucent, The Alcatel-Lucent logo, MainStreet and Newbridge are registered trademarks of AlcatelLucent. All other trademarks are the property of their respective owners. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice. 2007 Alcatel-Lucent. All rights reserved. Disclaimer In no event will Alcatel-Lucent 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-Lucent products or services is for information purposes only and constitutes neither an endorsement nor a recommendation. Please refer to technical practices supplied by Alcatel-Lucent for current information concerning AlcatelLucent equipment and its operation.
Table of Contents
3
Switch to notes view!

1. Principles 2. Radio Resource management 3. Radio Link Control 4. Algorithms Dynamic Behaviors 5. Appendix
1. Radio Algorithms
All Rights Reserved Alcatel-Lucent 2007
Table of Contents [cont.]

4
This page is left blank intentionally
Course Objectives
5

Welcome to E-GPRS Radio Algorithms and Parameters Description B10
After successful completion of this course, you should understand :
How to describe the main (E)GPRS mechanisms and concepts How to describe the radio algorithms and the related parameters How to estimate qualitatively the impact of a parameter change in order to solve typical problems or enhance the GPRS performance
Course Objectives [cont.]

6
About this Student Guide

7
Conventions used in this guide Switch to notes view!

Note
Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or personal injury.
Where you can get further information
If you want further information you can refer to the following: Technical Practices for the specific product Technical support page on the Alcatel website: http://www.alcatel-lucent.com
About this Student Guide [cont.]

8
Self-Assessment of Objectives
9
Contract number : Course title :
At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training to notes view!
Dates from : Location : to :
Client (Company, Center) : Language : Switch
Number of trainees : Surname, First name :
Did you meet the following objectives ? Tick the corresponding box Please, return this sheet to the trainer at the end of the training
Yes (or globally yes) No (or globally no)
Instructional objectives
Comments
Self-Assessment of Objectives [cont.]

10

Instructional objectives Yes (or Globally yes) No (or globally no) Comments
Other comments
Thank you for your answers to this questionnaire
11
Do not delete this graphic elements in here:
Section 1 Radio Algorithms

Module 1 Principles
3JK10863AAAAWBZZA Issue 03
EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 3FL11830ACAAWBZZA3 Issue 03
All Rights Reserved Alcatel-Lucent 2008 3JK10863AAAAWBZZA Issue 02 Section 1 Module 1 Page 1
Blank Page
112
Radio Algorithms Principles EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Document History Edition 01 Date YYYY-MM-DD Author Last name, first name Remarks First edition
Module Objectives
Upon completion of this module, you should be able to:
Describe the main GPRS mechanisms and concepts
113
Module Objectives [cont.]
114
Table of Contents
1 Service Overview 2 Alcatel-Lucent GPRS Architecture 3 Main Transactions Page 7 14 21
115

116
1 Service Overview
117
1 Service Overview
Data Transfer with GSM: Circuit Switching
Air Interface
Access Node
GSM Network
Internet
118
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. High Speed Circuit Switched Data (HSCSD) 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-Lucent.
1 Service Overview
Data Transfer with GPRS: Packet Switching
Air Interface
GPRS Network Internet
119
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.
1 Service Overview
MS Classes
Three MS classes are defined:
class A:
simultaneous GPRS and GSM traffic (different from Class A DTM MS)
B10
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
1 1 10
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 A new feature called Dual Transfer Mode (DTM) has been introduced in 3GPP Standard and in the AlcatelLucent B10 release. Contrary to classical Class A MSs, Class A DTM MSs do not need two independent transmitter/receiver.
1 Service Overview
MS Multislot Class
B10
1 1 11
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. EDA The Extended Dynamic Allocation, is a new B10 feature that allows higher throughput in uplink for type 1 MS. Through the support of more than two radio TSs (e.g. MS multislot class 11)
1 Service Overview
MS Multislot Class [cont.]

New Multislot classes supported in B10 Activation with the flag EN_MULTISLOT_CLASS_30_33
Multislot class 30 31 32
B10
Rx 5 5 5
Tx 1 2 3
Sum 6 6 6
Tta 2 2 2
Ttb 1 1 1
Tra 1 1 1
Trb 1 1 1
PTM (5+1) (5+1), (4+2) (5+1), (4+2),
DTM
(4+2) (4+2),
(3+3)/EDA (3+3)/EDA (5+1), (4+2), (4+2), (3+3)/EDA, (3+3)/EDA, (2+4)/EDA (2+4)/EDA (5+1), (4+2), (3+3)/EDA, (2+4)/EDA,
33
34
(1+5)/EDA
1 1 12
Note that DTM multislot classes 30 and 34 do not exist PTM multislot class 34 can be supported as multislot class 33

Multislot 30-33 MS can support bi-directional transfer configurations with up to 5 DL TS. EDA necessary to fully support multislot classes 32 and 33 PTM high multislot classes defined in 3GPP release 5 and, DTM high multislot classes defined in 3GPP release 6 Main benefits : More downlink throughput PTM mode : up to 5 DL PDCHs instead of 4 (5+1 instead of 4+1) DTM mode : up to 3 DL PDCHs instead of 2 (4+2 instead of 3+2)
1 Service Overview
MS Multislot Class [cont.]

PTM Multislot Class 11 (4+1):
0 Rx DL Ttb Tx UL Tra 1 Rx 2 Rx 3 Rx 4 5 6 Mx 7
B10
Multislot Class 11 (2+3) EDA:
DTM Multislot Class 11 (2+3):
High Multislot Class (5+1):

0 Rx DL 1 Rx 2 Rx 3 Rx 4
Rx
7 Mx
Ttb Tx UL
Tra
1 1 13
Multislot class 11: EDA shall be used in UL for the 1+3, 2+3 and 1+2(1hole) configurations. DA (Dynamic Allocation) shall be used for all the other configurations (4+1, 3+2, 3+1, 2+2, 2+1, 1+2 and 1+1).
2 Alcatel-Lucent GPRS Architecture
1 1 14
General Architecture
1 1 15
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.
Main Entities - Interfaces
B10
MS
BSS with PCU
Um (Radio)
BSS with PCU
MS - BTS
LAPDm
(GSM specific)
SGSN
SGSN
MSC
Gb
BSS - SGSN
BSSGP
Gn
GGSN
Gs Gn Gn Gr Gc
HLR EIR
Gf
Gr Gc Gf Gs Gi
SGSN-SGSN SGSN-GGSN SGSN-HLR GGSN-HLR SGSN-EIR SGSN-MSC/VLR GGSN-Data Network
IP IP SS7 IP/SS7 SS7 SS7 IP
Data Network
1 1 16
Radio Algorithms Principles EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
-New Gb transport option (B10 MR2): Gb over UDP/IP/Ethernet as an optional feature Mixed Gb (mix IP/Frame Relay) allowed within one MFS, selection of the option per BSC Standardized (3GPP R6) -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).
Packet Control Unit

A PCU 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-Lucent choice:
PCU in a network element called the MFS smooth and cost-effective introduction of the GPRS
Abis BTS
CCU
Ater BSC GSL MFS

PCU
Gb SGSN
BSS
1 1 17
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-Lucent 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. MFS is just the name of the rack containing PCU functions
M-EGCH principle
An M-EGCH organizes the transmission resources (pool of Abis nibbles and Ater nibbles) given to a TRX for its PS traffic 3 types of nibbles are considered
BASIC nibbles shareable between all TREs of a given cell BONUS and EXTRA nibbles shareable between all TREs of a given BTS
Bonus Extra
TRX 3
Basic
M-EGCH 3 TRX 2
Abis
TRX 1
M-EGCH 2
Ater
M-EGCH 1
1 1 18
Basic Abis Nibbles One Basic Abis nibble is initially linked to one RTS. The number of Basic Abis nibble in a given cell corresponds to the number of RTS. They have the following characteristics: They carry either CS or PS traffic. They are shareable at cell level (among all the TREs). Bonus Abis Nibbles The basic Abis nibbles whose RTSs are currently used for BCCHs and static SDCCHs are called bonus Abis nibbles. They have the following characteristics: They only carry PS traffic. They are shareable at BTS level (among all the TREs). Extra Abis Nibbles Considering one (E)GPRS capable BTS, the Operator can defined additional GCHs: the Extra Abis nibbles. They have the following characteristics: They only carry PS traffic. They are shareable at BTS level (among all the TREs). 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.
Transmission Plane
B10
MS Application IP SNDCP LLC RLC MAC
BTS
MFS
SGSN
SNDCP LLC Relay RLC BSSGP MAC Relay L2-GCH GSM RF L1-GCH L2-GCH
FR
BSSGP
NS L1bis
UDP /IP FR L1
NS
UDP /IP L1bis
GSM-RF
L1-GCH
L1
Eth
Eth
Um
Abis/Ater(mux)
Gb
1 1 19
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. Gb Over IP: New Gb transport option (B10 MR2) Gb over UDP/IP/Ethernet as an optional feature Mixed Gb (mix IP/Frame Relay) allowed within one MFS, selection of the option per BSC Standardized (3GPP R6)
Signaling Plane
B10
MS GMM/SM LLC
BTS
BSC
MFS
RR/RRM
RLC RRM RR RR/GTTP Relay L2-RSL GSM RF L1-RSL Relay BSCGP L2-GSL L1-GSL
Relay BSSGP
GTTP
BSCGP NS L2-GSL
FR UDP
L2-RSL L1-RSL
GSM-RF
L1-GSL
/IP L1bis L1 Eth
Um
Abis
Ater
Gb
1 1 20
GTTP: GPRS Transparent Transport Protocol: MS-BSS protocol Allows GMM signaling between MS and SGSN, without TBF establishment With GTTP, GMM messages are conveyed on main DCCH between MS and BSC, and on BSCGP between BSC and MFS. GTTP possible only if : DTM capable MS in dedicated mode (but not in DTM) DTM enabled in the cell Signalling LLC PDU to be exchanged (Tbit set to signaling) LLC PDU length does not exceed MAX_LAPDm x (length of a LAPDm frame)
3 Main Transactions
1 1 21
3 Main Transactions
GMM: Attach Procedure

To access GPRS services, the MS must first make its presence known to the network by performing a GPRS attach procedure with the SGSN
HLR
Update_loc_ack()
Authent_info_respq
Insert_subs_data()
Authent_info_req()
Update_loc_req()
N7
BSS
Attach-Request (IMSI)
MS_authentication_procedure Attach_resp (P_TMSI) Attach_complete ()
SGSN
1 1 22
Attach Request. The attach_request message is placed in an LLC frame. The MS sends its IMSI. Authentication The SGSN gets the authentication triplets from the HLR: triplets request message triplets response message The SGSN performs the authentication procedure with the MS: triplets request message triplets response message Location Update The SGSN performs the location_update procedure with the HLR: location_update request message the HLR transfers the MS_subscription data to the SGSN the HLR terminates the location_update procedure Attach Complete The SGSN terminates the attach_procedure with the MS : attach_accept message (with a new P_TMSI allocation) attach_complete message (since a new P_TMSI has been allocated)
3 Main Transactions
GMM: Attach Procedure [cont.]

Attached MS:
a logical connection is established between the MS and the SGSN connection established between the peer LLC layers in the MS and the SGSN this connection is identified by the TLLI (Temporary Logical Link Identity) this logical connection remains established until the MS detaches the MS can now access to GPRS services and is reachable for GPRS services
TLLI
SGSN 1
SGSN 2
1 1 23
3 Main Transactions
GMM: Routing Area

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.
MFS SGSN
LA
RA1 RA2
GPU 1 GPU 2
LA
RA3
GPU 3
1 1 24
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.
3 Main Transactions
GMM: GMM States Idle

GP RS AT TA CH
SD GP R ET AC H
Ready
Location of MS tracked on a cell basis
Ex pir y
Da ta
Tr an s
fe
Location of MS
Standby
of T_ RE AD Y
tracked on a RA basis
1 1 25
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. All Rights Reserved Alcatel-Lucent 2008 3JK10863AAAAWBZZA Issue 02 Section 1 Module 1 Page 25
3 Main Transactions
SM: PDP Context Activation

To be able to send and receive GPRS data, the MS must activate the PDP Context
DNS
DHCP
Activate_PDP_req (PDN2)
SGSN 1 GPRS
backbone
GGSN
PDN 1
TLLI1
Activate_PDP_resp(@IP_MS) }
GGSN Create_PDP_req (PDN2) Create_PDP_resp (@IP_MS)
PDN 2
GSS
1 1 26
PDP context = set of information characteristic of a session Type of PDP (e.g. IP v4) PDP address (e.g. 129.187.24.18) for the mobile (static or dynamic) PDP state (active, idle) QoS Profile Address of GGSN which serves as a access point to external PDN PDP Context Activation MS requests for a PDP_context activation, providing the name of target Packet Data Network (PDN2 parameter). SGSN queries the backbone Name Server (here DNS) to identify the GGSN giving access to the Data Network PDN2 (here GGSN2). SGSN sends a Create_PDP message to the corresponding GGSN2, in order to setup a GTP tunnel. GGSN2 allocates an IP address to the MS (@IP_MS), using the backbone DHCP server. GGSN2 acknowledges the Create_PDP message to the SGSN, returning the @IP_MS allocated to the MS. SGSN acknowledges the Activate_PDP message to the MS, with the allocated @IP_MS.
3 Main Transactions
SM: PDP Context Activation [cont.]

Activated PDP Context
SGSN1
TLLI 1
TID 1 = IMSI + NSAPI 1

TID 2=
PDN 1 GGSN1
SGSN 2
IMGPRS IP SI backbone +N SA PI 2
PDN 2
GSS
GGSN2
1 1 27
User data transfer In order to achieve a proper transfer of User Data, two main protocols are used: GTP (between GGSN and SGSN) and LLC (between SGSN and MS), and two types of logical connections are established: MS <-> SGSN. Logical Link used for signaling and data transfer, created at GPRS attach (unique per MS), identified by a TLLI value; SGSN <-> GGSN. Created with the activation of PDP context = when opening a session (several per MS), identified each by a TID value. TLLI (Temporary Logical Link Identity) Identifies uniquely a MS attached to the GPRS core network (Standby or Ready state). TID (Tunnel Identity) Identifies a logical connection ("tunnel") between GGSN and SGSN (for each session of each MS). TID= IMSI+NSAPI.
3 Main Transactions
Dual Transfer Mode

DTM enables a user to run CS and PS services simultaneously.
B10
CS & PS Simultaneously
Bla CCCH Bla PSCN CCCH
Bla Air
Bla
CSCN
Like a class A mobile, but without the need of a dual receiver. Particular interest on 2G/3G dual mode handsets, for 3G to 2G continuity of service purpose.
1 1 28
3 GPP: Feature part of Rel.99 specifications Optional for MS, BSS, CN Impacts on MS, BSS, MSC Improvements in Release 4, 6 and 7 B10 implementation aligned with Release 4 definition of the feature. Release 6 and 7 improvements not implemented in B10.
3 Main Transactions
DTM Activation
Activation
The activation of the DTM is done by the cell parameter (optional):
EN_DTM = enabled Defaut value = Disabled
B10
Activation is possible:
In Evolium cells In cells with a minimum number of resources
MAX_PDCH_HIGH_LOAD > 1 (at least 2 TSs are needed for DTM resource allocation)
In non-extended cells (to simplify implementation)
Gs interface is highly recommended (but not strictly mandatory) for paging coordination.
1 1 29
3 Main Transactions
DTM Principles
B10
Dedicated
Cs Setup (2) Cs Release (7) Release Last TBF (6)
Packet Request (3)
Idle/PIM
Cs and Ps Release (4)
DTM
Release Last TBF (1) Packet Request (5)
PTM
1 1 30
Note that the system does not support a transition directly between packet transfer mode an DTM in either direction. Scenario 1: Entering the DTM mode for a Ms already in Packet Transfer receiving a Cs call request
1. Release of the TBF. 2. CS establishment. 3. A new TBF is established, the Ms enters into the DTM mode.
Scenario 2: Releasing the CS connection in DTM

1. Both CS and PS services are released. 2. New TBF is re established in Packet Transfer mode by the MS or by the network.
Scenario 3: Releasing the PS connection in DTM, then releasing the CS connection

1. When the last TBF is released for an Ms in DTM, the CS call continues in dedicated mode. 2. After releasing the CS call, the MS enters the idle mode.
3 Main Transactions
DTM Multislot lasses

Class 5 (2+2): 1 TCH + 1 PDCH
B10
DL Class 5
UL
Class 9 (3+2): 1 TCH + 2 PDCH

DL Class 9 UL
Timeslot for CS (TCH/F) Timeslot for PS

1 1 31
The usage of Extended Dynamic Allocation in UL together with DTM is only allowed in the case of a DTM [E]GPRS multislot Class 11. All the other configurations dont need usage of the Extended Dynamic Allocation
Note: C means configurations with contiguous TSs . Class 11 (2+3) with EDA: 1 TCH + 2 PDCH
3 Main Transactions
Support of GTTP
GTTP allows GMM signaling between MS and SGSN, without TBF establishment With GTTP, GMM messages are conveyed on main DCCH between MS and BSC, and on BSCGP between BSC and MFS. GTTP is possible if:
DTM capable MS in dedicated mode (but not in DTM) DTM enabled in the cell Signaling LLC PDU to be exchanged (i.e. RA update)
B10
LLC PDU length does not exceed MAX_LAPDm x (length of a LAPDm frame)
1 1 32
While in dedicated mode or in DTM, upper layers in the mobile station or in the BSS may request the transport of GPRS information transparently over the radio interface. This procedure is possible only if: the information from upper layers is signalling information the GTTP length of the message is below the maximum indicated by the network, iI.e. it can fit in less than MAX_LAPDm frames. In other case, the MS or the BSS shall initiate the establishment of a TBF (I.e. enter DTM mode). The information from upper layers shall be carried inside the GTTP Information message. The GTTP Information message contains: TLLI of the MS LLC PDU
3 Main Transactions
PS Paging for DTM MS in dedicated mode
B10
MS
(1)
BSC
MFS
SGSN
MS in dedicated mode
PS PAGING
(2) Packet notification
DTM Packet notification Start T_Wait_DTM DTM Packet notification Ack
(4)
GPRS Information[UL LLC PDU] DTM GPRS Information[UL LLC PDU]
Stop T_Wait_DTM
(3)
Signalling carried on GTTP if possible
(5)
UL LLC PDU (6)
1 1 33
1. The DTM MS is in dedicated mode. 2. As the MS is in GMM Standby state, the SGSN shall first page the MS before sending Data. 3. Upon receipt of the PS paging, the MFS checks wether the concerned MS is in dedicated mode. If it is
the case, the MFS sends to the BSC a BSCGP DTM Packet notification message providing the BSC with the reference of the MS (i.e. IMSI and BSC reference) and the contents of the 44.018 Packet Notification message and starts T_Wait_DTM, to monitor the reception of acknowledgement from BSC. The BSC forwards the Packet Notification message to the MS on the main DCCH, and sends a DTM Packet Notification Ack message to the MFS. The MFS stops T_Wait_DTM and delete the paging (paging is considered as being successfully sent to the MS). 4.to 6. On receipt of the Packet Notification message, the MS shall answer to the notification with a cell update procedure, I.e. by sending an LLC Frame. If the LLC frame does not convey user data information and can be transmitted through Gprs Transparent Transport Protocol (GTTP) in less than MAX_LAPDm frames, the MS uses the GTTP to send the UL LLC frame to the the SGSN. Otherwise the MS requests the establishment of an UL TBF with a 44.018 DTM request message and sends the UL LLC PDU on the established UL TBF
3 Main Transactions
GS Interface
The Gs interface carries signaling between SGSN and the MSC. The association supports the following actions:
IMSI attach/detach via the SGSN coordination of LA and RA update paging for a CS connection via the SGSN
CCCH
PCCCH
MSC/VLR A
DCCH
BSS
SGSN
Gs
PACCH
Um
1 1 34
Gb
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.
3 Main Transactions
Network Mode of Operation
B10
Mode
CS paging channel PCH PACCH
PS paging channel PCH NA Main DCCH NA PCH PPCH NA
Remarks Gs interface Gs interface Gs interface Gs interface no Gs interface no Gs interface no Gs interface

Packet idle mode Packet transfer mode Packet idle mode Packet transfer mode
I NA NA II PCH PCH III PCH

Dedicated mode Dual transfer mode
1 1 35
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. In case of DTM activation, Gs interface is highly recommended (but not strictly mandatory) for paging coordination. When the DTM feature is enabled, and when NETWORK_OPERATION_MODE = NMO I, the BSS shall use the following channels to page a DTM MS engaged in a CS or PS connection: The PACCH to page a DTM mobile for a CS connection if this mobile has already a PS connection ongoing. In this case, the MS is in Packet Transfer Mode. The main DCCH (FACCH or SDCCH) to page a DTM mobile for a PS connection if this mobile has already a CS connection on-going. In this case, the MS is in dedicated mode.
3 Main Transactions
CS/PS Paging During a Packet Transfer/Call

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
1 1 36
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.
3 Main Transactions
CS/PS Paging During a Packet Transfer/Call [cont.]

The Suspend/Resume feature is used for a Class A DTM MS in the following cases:
When a Class A DTM MS is handed over to a cell not supporting DTM
B10
After the Handover procedure is completed, the MS sends a suspend message with the suspension cause DTM not supported in the cell
When a GPRS attached MS is in a cell that does not support DTM and a Cs service is initiated
After the CS access to the cell, the MS sends a suspend message with the suspension cause DTM not supported in the cell
1 1 37
In case two, the GPRS suspension procedure is initiated by the mobile station by sending a GPRS suspend message with the suspension cause set to DTM not supported in the cell. This can be done as early as possible after access but shall be done afetr sending a CLASSMARK CHANGE message.
3 Main Transactions

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
1 1 38
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.
3 Main Transactions

Suspend/Resume for Class B MS:
The MS enters in GSM dedicated Mode (Ongoing GPRS
transfer or not)
End of on-going TBF DL LLC PDUs are discarded MFS SGSN
MS
BSC
1. Suspend (TLLI, RAI)
2 Suspend 3 Suspend (TLLI, RAI, suspend cause) 4 Suspend Ack (TLLI, RAI, SRN) 5 Suspend Ack
End of the GSM call 6 Resume (TLLI, RAI, SRN) 7 Resume
Normally, no more paging messages sent by the SGSN
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
1 1 39
8 Resume Ack
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-Lucent 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.
Self-assessment on the Objectives

Please be reminded to fill in the form Self-Assessment on the Objectives for this module The form can be found in the first part of this course documentation
1 1 40
End of Module Principles
1 1 41
12

Module 2 Radio Resource management
Blank Page
122
Radio Algorithms Radio Resource management EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Module Objectives
Describe the algorithms of Resource Management and the related parameters
123
124
Table of Contents
1 2 3 4 (E)GPRS Channels Autonomous Packet Resource Allocation TBF Radio Resources Allocation and Re-Allocation TBF Release Routine Page 7 21 52 73
125

Page
126
1 (E)GPRS Channels
127
1 (E)GPRS Channels
Overview
PTCCH
PDCH
Slave PDCH
PACCH
physical channel control channel Logical Channel traffic channel signaling associated control channel logical channel category
PTCH
PDTCH
128
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 (details are given in the annex). The use of GSM CCCH for the GPRS traffic offer can lead to QoS problem in GSM (PCH use more specifically). mCCCH Feature (B10): The multiple CCCH is required to support the increasing signalling load on the common channels, due to either big CS cells with high peak throughput or to PS traffic when no master PDCH is configured.
1 (E)GPRS Channels
Multiframe Structure
8PSK 171
0 1 2 3 4 5 6 7 0 1
171
2 3 4
57
5 6
57
7 0 1
GMSK
2 3 4 5 6 7 0 1 2 3 4 5 6 7
FRAME 0
FRAME 1
FRAME 2
FRAME 3
F00 F01 F02 F03 F04 F05 F06 F07 F08 F09 F10 F11 F12 F13 F14 F15 F16 F17 F18 F19 F20 F21 F22 F23 F24 F25
F50 F51
B0
B1
B2
B3
B4
B5
B6
B7
B8
B9
B10
B11
Frame 12
52 FRAMES then 52 TS x and 240 ms
Frame 38
1 PDCH
12 BLOCS
Frame 12 & 38: PTCCH Radio BLOC 3
129
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). 1 RLC Data Block uses 1 PDCH Radio Block, except in MCS-7 to MCS-9 where 2 RLC data block use 1 Radio BLock block
1 (E)GPRS Channels
RLC/MAC block and radio block
1 2 10
1 RLC Data Block uses 1 PDCH Radio Block, except in MCS-7 to MCS-9 where 2 RLC data block use 1 Radio BLock block
1 (E)GPRS Channels
GPRS Logical Channels
GPRS without Master
GPRS with Master
Direction Broadcast system information
Diffusion
BCCH
PBCCH
DL
RACH COMMON SIGNALING PCH AGCH PDTCH USER TRAFFIC PACCH
PRACH PPCH PAGCH PDTCH PACCH
UL DL DL DL/UL DL/UL
Random access Paging Access Grant User data transfer Associated signaling
1 2 11
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 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) 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.
1 (E)GPRS Channels
Timing Advance
ss Bu Acce
rst
TA M
e essag
BTS
PTCCH:
Bidirectional channel used by the continuous timing advance mechanism Timing Advance Index (TAI), used for the scheduling of the AB, is part of the radio resources allocated to an MS.
The TAI takes 16 values
1 2 12
the PTCCH (Packet Timing advance Control Channel) of one MS is carried by the PDCH carrying the PACCH The AB in the UL and the TAM 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 MS 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 MF-51 N N N+1 N+1 N+2 On PTCCH TS number 12 38 12 38 12 15 N+7 38 TAM 4 idem TAM 0 TAM 0 TAM 0 TAM 0 TAM 1 Idem 4 repetitions of the 16 TA values (4 TA values updated)
TAI value 0 1 2 3 4
TA Message
1 (E)GPRS Channels
Temporary Block Flow (TBF)

TBF: Unidirectional flow of data between the MS and the MFS for the transfer of one or more LLC PDUs
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)
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

1 2 13
TBF with TFI = 17
TBF with TFI = 24
Temporary Flow Identity (TFI): Each TBF is assigned a TFI by the MFS. 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.
1 (E)GPRS Channels
USF Dynamic Allocation

MS decodes all DL blocks USF value on the allocated PDCHi
DL PDCHi
In block B USF =T ?
Y
SEND on block B+1 (TFIk): PDTCH Or PACCH
TFIk
UL PDCHi
TFIk
TFIk
TFIk
TFIk
TFIk
If the USF is the one allocated to the MS, then the MS can transmit in the next radio block period
1 2 14
Radio Algorithms Radio Resource management EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
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. This is the principle of the Dynamic Allocation, which allows a maximum of two TSs in Uplink
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.
1 (E)GPRS Channels
Polling Mechanism
S/P=VALID RRBP = 3 TFI 24 USF=5 TFI 17 USF = 000 TFI 24
PDTCH B0
PDTCH B1
PDTCH B2
TFI 5 PDTCH B3
TFI 5
DL
PACCH B4
TFI 02
TFI 24
PDTCH B0 B1 B2
PDAN B3 B4
UL
RRBP indicates the number of Blocks the MS shall wait before transmitting its uplink RLC/MAC block.
Exercise
1 2 15
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.
1 (E)GPRS Channels
Extended Dynamic Allocation
B10
EDA allows higher throughput in uplink through the support of more than two TSs B10 MR2 Principles
The EDA feature is optional for the network.
Same basic principles as Dynamic Allocation (i.e. based on USF) Difference:

An Ms detecting its assigned USF value on one assigned PDCH is allowed to transmit on that PDCH and all higher numbered assigned PDCHs
Thus The mobile station needs not to monitor all the downlink PDCH corresponding to its uplink PDCH allocated
1 2 16
1 (E)GPRS Channels
Extended Dynamic Allocation [cont.]

USF scheduling for EDA mode
BP 1 BP 2
Tta=2 Trb=1
B10
BP 3 BP 4 BP 5 BP 6
1+4 Configuration
BP 7 BP 8 BP 9 BP 10 BP 11 BP 12
1 2 17
: uplink radio block where the mobile station is transmitting : downlink radio block monitored by the mobile station for USF detection : downlink radio block where the network sets the USF of the mobile station
1 (E)GPRS Channels
Extended Dynamic Allocation Usage [cont.]

Uplink Throughput increase
Class 11 (2+3):
0 1 RX 2 3 4 5 6 Mx 7
B10
DL
RX
Ttb
Tra TX 0 TX 1 TX 2 3 4 5 6 7
UL
Class 12 (1+4):
0 1 2 Mx 3 4 5 6 7
DL
RX
Tta
Trb TX 0 TX 1 TX 2 TX 3 4 5 6 7
UL
1 2 18
1 (E)GPRS Channels

EN_EDA: disabled (default Alcatel value).
Changeable at OMC-R on Cell level
B10
EDA_MS_ACTIVATION_LEVEL: activation level

Gives an artificial mean to limit the activation domain (inter-operability issues)
Possibility is given by the parameter ALLOW_DTM_EDA_COMBINATION to allow DTM and EDA combination
(i.e. support of 2+3 configuration for DTM multislot class 11)
1 2 19
EDA_MS_ACTIVATION_LEVEL and ALLOW_DTM_EDA_COMBINATION are relevant if EN_EDA = 1. EDA_MS_ACTIVATION_LEVEL=0 (Alcatel default value) and it can be set at the OMC-R (BSS Level) ALLOW_DTM_EDA_COMBINATION = 0 (Alcatel default value) and it can be set at the OMC-R ( BSS Level) Note : none of the combination of the three paramters allows activating EDA only in case of DTM operations The Ms is supporting EDA mode depending on the following PCC flag: EDA_Allowed_GPRS (respectively EDA_Allowed_EGRPS) which is set to true if: The cell belongs to an Evolium BTS The cell is not an extend cell EN_EDA parameter is activated EDA is supported by the MS in GPRS (respectively EGPRS) EDA is enabled in the BSS ( EDA_MS_ACTIVATION_LEVEL parameter) The N_UL_BIAS_FOR_EDA last observed biases since the transfer start are uplink There is no RT PFC associated to the MS
1 (E)GPRS Channels

Non-multiplexed EDA strategy
The UL PDCHs of the EDA TS configuration shall mandatory verify the following conditions:
Alone on its uplink timeslots Not in position of DL PACCH TS (except its own one) Not in position of DL EDGE TS, in case of GPRS TBF Configurations with hole(s) supported
1 2 20
The UL PDCHs of the EDA TS configuration shall mandatory verify the following conditions: Alone on its uplink timeslots The PDCHs shall not support any NRT/RT UL TBFs of other MSs (GPRS or EGPRS, DTM or non-DTM) Not in position of DL PACCH TS (except its own one) The PDCHs shall not support any PACCH TS of NRT/RT DL TBFs of other MSs (GPRS or EGPRS, DTM or nonDTM) Not in position of DL EDGE TS, in case of GPRS TBF The PDCHs shall not support any EGPRS NRT/RT DL TBFs of other MSs (DTM or non-DTM) Configurations with hole(s) supported T3 trigger used to perform this strategy (in PTM and in DTM).
2 Autonomous Packet Resource Allocation
1 2 21
SPDCH Group
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
1 2 22
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.
SPDCH Group [cont.]

Example: BBH is used, NB_TS_MPDCH=0
TRX_PREF_MARK
0
TRX1 SPDCH group1 BCCH
1
SDCCH
TRX2 SDCCH SPDCH group2 SPDCH group2 Null
TRX3
0
SPDCH group3
1 2 23
CAUTION: animated slide.
8-PSK High Power Capability

Q
GMSK
constant envelope (amplitude) modulation one bit per modulated symbol over the radio path
dB PN
8-PSK
Envelope modulation not constant 3 bits per modulated symbol over the radio path
(147 bits)
542.8 s
dB
0
0,1, 0 0,0, 0 0,0, 1
0,1, 1 1,1, 1
PN
-20
(147 bits)
1,0, 1
1,0, 0
1,1, 0
1 2 24
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 Modulation type Channel spacing Gross bit rate per carrier Carrier envelope Packet radio service 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.
8-PSK Phase modulation 200 KHz 810 Kbit/s Amplitude varies EGPRS
Frequency modulation 200 KHz 270 Kbit/s constant GPRS / EGPRS
8-PSK High Power Capability [cont.]

G4 TRE characteristics
TRAG TRAGE EDGE+ TAGH TAGHE EDGE+ TRAD TRADE EDGE+ TADH TADHE EDGE+
Type Frequency band GMSK output power 8-PSK output power
Medium power 900 45 W 46,53 dBm 15 W 41,76 dBm 30 W 44,77 dBm
High power
Medium power 1800
High power
60 W 47,78 dBm 25 W 43,98 dBm 30 W 44,77 dBm
35 W 45,44 dBm 12 W 40,79 dBm 30 W 44,77 dBm
60 W 47,78 dBm 25 W 43,98 dBm 30 W 44,77 dBm
1998 Evolium BTS TRX TRE

1 2 25
2000 Edge TRX TRA
2004 Edge+ TRX MP & HP
2006 TWIN 2x TRX
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.
8-PSK High Power Capability [cont.]

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
49 48 47 46 45 44 43 42 41 40 39 38 37 36 35
TRE 1 TRE 2 TRE 3
APD (dB) 8-PSK attenuation (dB) 8-PSK TRE power (dBm) GMSK TRE power (dBm) GMSK power in the cell (dBm) Max GMSK power in the cell (dBm) Max Power in the cell (dBm)
1 2 26
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. The modulation_delta_power = [Maximum output power in the cell] [8-PSK TRE output power] 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 And a possible attenuation, in order not to exceed the GMSK power in the cell (case of BS_TXPWR_MAX <> 0 dB)
TRX Ranking
Inputs Outputs
8-PSK High Power Capability (G4 HP, G4 MP, or G3) DR TRE capability (FR or DR) TRE Characteristics
TRX_PREF_MARK PS_PREF_BCCH_TRX E-GSM, P-GSM, GSM850 or DCS TRX Radio cell configuration (nb of SPDCHs per TRX)
TRX Ranking TRX Ranking function

TRX Rank
Table
TRX id (0,1,,14, or 15) TRX or cellCharacteristics
1 2 27
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.
TRX Ranking [cont.]

Ranking criteria
Concerns only PS capable TRX: TRX_PREF_MARK = 0 PS_PREF_BCCH_TRX
= 0 (no specific preference) then the BCCH TRX is managed as a non-BCCH TRX = 1 then the BCCH TRX has the highest preference = 2 then the BCCH TRX has the lowest preference (B9 MR4)
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 TRX(s) having the maximum SPDCH group size TRX having the lowest TRX index
Exercise
1 2 28
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 2, then the BCCH TRX has the highest rank in the TRX Ranking Table. This means that this TRX is selected last for PS allocations. 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 PGSM/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. All Rights Reserved Alcatel-Lucent 2008 3JK10864AAAAWBZZA Issue 02 Section 1 Module 2 Page 28
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

TRX
Air
PDCH
Abis
M-EGCH
AterMux
M-EGCH
BTS
1 2 29
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
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
Otherwise, the rule is MIN_PDCH NB_TS_MPDCH
1 2 30
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. 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
Principle
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
1 2 31
All the usable PS capable radio time slots are explicitly allocated to the MFS through the RR Allocation Indication message. A coordination is performed between the MFS and the BSC to allocate radio time slots for the PS traffic.
Principle [cont.]
B10
BSCGP
BSC RR Allocation Indication RR Usage Indication MFS
2x TCH_INFO_PERIOD(5) RR Usage Indication
TCH_INFO_PERIOD
RR Allocation Indication RR Usage Indication
1 2 32
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 4 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 SPDCHs_DTM_TCH_List bitmap: 1: this SPDCH is used as TCH for DTM. 0: this SPDCH is used as No TCH for DTM. 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. All Rights Reserved Alcatel-Lucent 2008
3JK10864AAAAWBZZA Issue 02 Section 1 Module 2 Page 32
Functional Entities
LOAD_EV_PERIOD_GPRS NB_USED_CS_TS NB_USED_PS_TS Load Evaluation MAX_PDCH_HIGH_LOAD MAX_PDCH MIN_PDCH NB_TS_MPDCH MIN_SPDCH MAX_SPDCH NB_TS Thresholds computation MAX_SPDCH_HIGH_LOAD Computation of MAX_SPDCH_LIMIT
B10
NB_TS_DEFINED NB_TS_SPDCH
AV_USED_CS_TS AV_USED_PS_TS AV_UNUSED_TS
MAX_SPDCH_LIMIT
MARGIN_PRIORITY_CS CS/PS Margin MARGIN_PRIORITY_PS
HIGH_TRAFFIC_LOAD_GPRS THR_MARGIN_PRIORITY_PS
1 2 33
The BSC peridically computes the number of Slave PDCHs that it can provide to the MFS. This number of SPDCHs is denoted MAX_SPDCH_LIMIT. In order to evaluate the value of this parameter, the BSC requires to compute a certain number of other parameters. This different steps to evaluate MAX_SPDCH_LIMIT are the following ones: Computation of MIN_SPDCH, MAX_SPDCH and MAX_SPDCH_HIGH_LOAD from O&M parameters and from NB_TS which has a changeable value (in case of TRX failure for example, seen later) Computation of MARGIN_PRIORITY_CS and of MARGIN_PRIORITY_PS Computation of MAX_SPDCH_LIMIT
Thresholds Computation
MAX CS traffic without PS traffic MAX PS traffic without CS traffic MAX PS traffic when High CS traffic
MIN_SPDCH MAX_SPDCH_LIMIT MAX_SPDCH_HIGH_LOAD MAX_SPDCH
1 2 34
MAX_SPDCH = Roundup [Min(MAX_PDCH ; NB_TS_SPDCH) x Availability_TS_Ratio] MAX_SPDCH_HIGH_LOAD = Roundup [Min(MAX_PDCH_HIGH_LOAD; NB_TS_SPDCH) x Availability_TS_Ratio] MIN_SPDCH = Roundup [MIN_PDCH 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_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).
Load Evaluation
The BSC computes 3 averaged values
B10
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
1 AV_USED_CS_TS(k) = LOAD_EV_PERIOD_GPRS
LOAD_EV_PERIOD_GPRS -1
NB_USED_CS_TS (k - i)
i= 0
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)]
1 2 35
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. SPDCH allocation state = allocated or de-allocating DTM mode = DTM TCH 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. DTM Mode = DTM TCH These variables are updated every TCH_INFO_PERIOD (5s). k-2 k-1 k k+1 k+2
TCH_INFO_PERIOD = 5s NB_USED_CS_TS(k) NB_USED_PS_TS(k) RR_ALLOC_PERIOD * TCH_INFO_PERIOD NB_USED_TS(k) AV_USED_CS_TS(k+2) AV_USED_CS_TS(k) NB_UNUSED_TS(k) AV_USED_PS_TS(k+2) AV_USED_PS_TS(k) AV_UNUSED_TS(k+2) AV_UNUSED_TS(k) LOAD_EV_PERIOD_GPRS = 3
Margins
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) THR_MARGIN_PRIO_CS = 100% - HIGH_TRAFFIC_LOAD_GPRS
B10
MARGIN_PRIORITY_PS = THR_MARGIN_PRIO_PS x MAX_SPDCH_HIGH_LOAD

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
1 2 36
These new margins, one for CS traffic and one for PS traffic are here introduced to guarantee that a certain number of timeslots are kept available for the arrival of new calls between two transmissions of RR Allocation Indication messages. MARGIN_PRIORITY_CS : dedicated to CS traffic. MARGIN_PRIORITY_PS : dedicated to PS traffic. These margins are re-evaluated every RR_ALLOC_PERIOD * TCH_INFO_PERIOD, before the computation of MAX_SPDCH_LIMIT.
MAX_SPDCH_LIMIT Computation [cont.]

LOAD_EV_PERIOD_GPRS NB_USED_CS_TS NB_USED_PS_TS Load Evaluation MAX_PDCH_HIGH_LOAD MAX_PDCH MIN_PDCH NB_TS_MPDCH MIN_SPDCH MAX_SPDCH NB_TS Thresholds computation MAX_SPDCH_HIGH_LOAD Computation of MAX_SPDCH_LIMIT MAX_SPDCH_LIMIT
NB_TS_DEFINED NB_TS_SPDCH
AV_USED_CS_TS AV_USED_PS_TS AV_UNUSED_TS
MARGIN_PRIORITY_CS CS/PS Margin MARGIN_PRIORITY_PS
HIGH_TRAFFIC_LOAD_GPRS THR_MARGIN_PRIORITY_PS
1 2 37
MARGIN_PRIORITY_CS
AV_USED_CS_TS AV_UNUSED_TS
Computation of MAX_SPDCH_LIMIT_CS MAX_SPDCH MAX_SPDCH_HIGH_LOAD
MAX_SPDCH_LIMIT_CS Computation of MAX_SPDCH_LIMIT MAX_SPDCH_LIMIT_PS MAX_SPDCH_LIMIT
Computation of AV_USED_PS_TS MAX_SPDCH_LIMIT_PS
MIN_SPDCH MARGIN_PRIORITY_PS
1 2 38
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.

MAX_SPDCH_LIMIT is equal to:
OR MAX_SPDCH_LIMIT_CS under normal load MAX_SPDCH_LIMIT_PS under high CS load
B10
AV_USED_CS(k) MARGIN_CS(k)
NB_TS(k) MAX_SPDCH_LIMIT_CS(k) MARGIN_PRIORITY_PS(k) AV_USED_PS_TS(k) MAX_SPDCH_LIMIT_PS(k)
1 2 39
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]

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]
B10
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
1 2 40
MAX_SPDCH_LIMIT Computation: Example

NB_TS=14 MAX_SPDCH=14 MIN_SPDCH=1 HIGH_TRAFFIC_LOAD_GPRS=80% MAX_SPDCH_HIGH_LOAD=2
14
12 10
CS Traffic
CS Traffic CS Traffic PS Traffic Normal load PS Traffic
6 4
PS Traffic High CS load High CS load with PS traffic Without PS traffic
High PS load Exercise
1 2 41
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.
PS Zones: Definition
MAX_SPDCH = 12, MIN_SPDCH = 1, MAX_SPDCH_LOAD = 8 MAX_SPDCH_LIMIT = 7
B10
PS
PS
PS
PS
CS
CS
BCCH SDCCH
CS
TRX3
Non pre-emptable zone MAX_SPDCH_HIGH_LOAD zone MAX_SPDCH_LIMIT zone PS traffic zone
TRX1
1 2 42
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. For a DTM request, the MFS will always allocate DTM TCH in this zone, and try to select the leftmost timeslot as DTM TCH. 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, or allocated to the MFS, not use, TCH for DTM. 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.
PS Zones: Selection of MAX_SPDCH_LIMIT TS

The MAX_SPDCH_LIMIT timeslot are selected within:
the non pre-emptable PS zone
It contains all the TS that can be or are allocated to the MFS
B10
the MAX_SPDCH_LIMIT zone

If the number of selected TS is still lower than MAX_SPDCH_LIMIT, the process continues outside this zone until this number reaches MAX_SPDCH_LIMIT.
Once MAX_SPDCH_LIMIT timeslot have been selected, the remaining TS are allocated to the BSC The TS carrying the TCH of a MS in DTM remains allocated to the MFS:
Even if they are outside the MAX_SPDCH_LIMIT zone It only concerns the TCH of the MS, not the TBF resources
1 2 43
The BSC shall not de-allocate a DTM TCH timeslot carrying CS traffic, even if the DTM TCH is outside of MAX_SPDCH_HIGH_LOAD value and MAX_SPDCH_LIMIT zone (in case of TRX failure, the BSC will adjust MAX_SPDCH_HIGH_LOAD value, so it is possible the DTM TCH timeslot is outside of non-emptable zone) until the DTM CS connection is released. When the DTM CS connection is released, the BSC notifies it to the MFS, the MFS changes the DTM TCH timeslot from TCH for DTM to no TCH for DTM and indicates this information to the BSC through the message RR Usage Indication, only then the BSC can de-allocate it.
PS Zones: Impact on CS Call
B10
PS
PS
PS
PS
CS
PS
PS
CS
BCCH SDCCH
CS
TRX3
Non pre-emptable zone MAX_SPDCH_HIGH_LOAD zone MAX_SPDCH_LIMIT zone PS traffic zone
TRX1
HO cause 30
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
1 2 44
Caution: animated slide. The BSC shall not de-allocate a DTM TCH timeslot carrying CS traffic, even if the DTM TCH is outside of MAX_SPDCH_HIGH_LOAD value and MAX_SPDCH_LIMIT zone. Cause 30 is not applied in case of TS carrying a DTM TCH. SPDCH allocation state is equal to TCH for DTM
SPDCH Allocation: Conclusion

Example of an SPDCHs_Allocation bitmap
MAX_SPDCH_LIMIT = 7
DTM MS
B10
PS
PS
PS
CS*
PS
CS
BCCH SDCCH
CS
TRX3
Non pre-emptable zone MAX_SPDCH_LIMIT zone
TRX1
CS* : DTM TCH
1 2 45
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.
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
B10
CS preemption takes place in two main steps:

Soft preemption Fast preemption
SPDCH de-allocation is based on GCH inactivity timers

Timers T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST are used to deallocate the unused GCHs
1 2 46
SPDCH De-allocation: Preemption Mechanism

Arrival of RR Allocation indication message Lock PDCHs
On TRXs with all its basic Abis nibbles impacted by CS preemption
T1 re-allocation
Soft preemption
No TBF candidate for T1 or T_PDCH_Preemption expiry
All T1 requests played successfully
Fast preemption
Unlock PDCHs
1 2 47
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. Thats 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: If some PDCHs were locked in step 1, they are unlocked. Indeed, the CS preemption process is over, so the existing M-EGCH links will no longer be disturbed by the release of some of their GCHs due to the fast preemption. All Rights Reserved Alcatel-Lucent 2008 3JK10864AAAAWBZZA Issue 02 Section 1 Module 2 Page 47
SPDCH De-allocation: Preemption Mechanism [cont.]

Case of resources allocated in DTM mode
Arrival of RR Allocation indication message Lock PDCHs
On TRXs with all its basic Abis nibbles impacted by CS preemption
B10
No T1 reallocation will be triggered during T_PDCH_Preemption
Soft preemption
Fast preemption
TBF resources of the MSs are released. TCH ressources shall not be deallocated
Unlock PDCHs
1 2 48
The preemption of a PDCH in the TCH state is controlled by the BSC Through arrival of RR Allocation Indication message That situation is rare as the TSs used for an MS in DTM mode are only allocated in the non preemptable PS zone A PDCH supporting a BE TBF for an MS in DTM mode can be preempted by the BSC. That situation can occur: if a RR Usage Indication message indicating the TSs used by the BE TBFs crosses a RR Allocation Indication message sent by the BSC which preempts some of those TSs. or due to a change of the non preemptable PS zone of the cell In such situation the following algorithm shall be applied: tep 1: Identical to non DTM case Step 2: The same conditions as non DTM ones apply If the DTM TBF resources are impacted by the CS preemption , the a notification message will be sent to RRM-PPCC. This notification message will be ignored by RRM-PCC and no T1 reallocation will be triggered by RRM-PCC. Step 3: fast preemption process The same conditions as non DTM ones apply RRM-PCC will release the TBF resources (both UL and DL) of the MSs. The TCH resources shall not be deallocated (TCH resource deallocation will happen on BSC-Shared-DTM-Info-Indication reception in the nominal case) Step 4: unlock the PDCHs: Identical to non DTM case
SPDCH De-allocation: Soft Preemption

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)
1 2 49
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).
SPDCH De-allocation: Soft Preemption [cont.]

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 TBF2 MCS7 PDCHs to be preempted
Bonus Bonus
. . .
TRX4 TRX3 TRX2 TRX1 Abis
TRX1
BCCH SD
TBF1 CS2 RSL OML

1 2 50
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
1 2 51
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.
3 TBF Radio Resources Allocation and Re-Allocation
1 2 52
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
TBF establishment (without concurrent) TBF establishment (with concurrent) T1 TBF reallocation T4 TBF reallocation T3 TBF reallocation (MS in PTM or in DTM DTM allocation request
Policy
ASAP ASAP ASAP ASAP Optimal ASAP
Nb_GCH_For_Estab
1 1 to 5 (Max_Allowed_(M)CS of concurrent TBF) 1 1 to 2 (Max_Allowed_CS of concurrent TBF) 1 to 5 (Max_Allowed_(M)CS of concurrent TBF) 1
New B10
1 2 53
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 1 2
Max_Allowed_CS CS-2 (UL) / CS-1 (DL) CS-4
Nb_GCH 1 2 3 4 5
Max_Allowed_MCS MCS-2 (UL) / MCS-1 (DL) MCS-5 MCS-6 MCS-7 MCS-9
1 2 54
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.
Functional Entities
RADIO RESOURCE ALLOCATION/REALLOCATION ALGORITHM
Best-effort TBF allocation/reallocation request (received from RRM-PCC or dequeued from an Li list) Multislot class, Bias, Traffic type
Transmission Resource Availability

Available_Nb_GCH
TRX list sorted by the BSC
DSP congestion state
TRX list computing Cf. session 2.2

TRX list
Number of radio TSs determination

n_MS_requested, n_MS_requested_concurrent Type of the TBF request
Best candidate allocation computation

Candidate TS allocation
No candidate TS allocation
Cell Transmission Equity

Available_Nb_GCH_With_Equity
Test if enough GCHs

Enough GCHs Not enough GCHs
PDCH capacity/TFI/TAI/USF allocation

AL LOC OK case AL LOC FAILED case
Transmission resource reservation
rejected request or L4 queuing or L5/L6 queuing or L7 queuing) or try to change TBF mode (EGPRS case)
TBF ESTABLISHMENT PROCESS
1 2 55
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.

Best -effort TBF allocation/reallocation reque st (received from RRM -PCC or dequeued from an Li list) Multislot class, Bias, Traffic type
B10

Available_Nb_GCH

TRX list



Test if enough GCHs


ALLOC OK case ALLOC FAILED case
- rejected request - or L4 queuing - or L5/L6 queuing - or L7 queuing ) - or try to change TBF mode (EGPRS case)
1 2 56
The transmission resource Availibility step determines the total number of new GCHs which can be established: with free Abis and Ater resources (only the non-CS pre emptable Abis ressources are considered for RT PFC) with inter-cell GCH preemptions This number is: Available_Nb_GCH in case of Best Effort TBF allocation Available_Nb_GCH_for_GBR in case of RT PFC allocation
Transmission Resource Availability: Example

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
Cell A
radio
Abis
Cell B Basic nibbles Cell C
6x4 extra nibbles
CS
1 2 57
Transmission Resource Availability: Example [cont.]

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 MS1
CS Cell A
1 2 58

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 Cell B
CS MS1 MS2
1 2 59

After GCH allocation of MS2 in cell B
In Cell A: Established_Nb_GCH = 16
Next Periodical GCH process in Cell A: Equity process

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 Cell B
CS MS1 MS2
1 2 60
Transmission Resource Availability: High Ater Usage
B10
Each time some radio resources are allocated on a new PDCH of a TRX
No radio resources were formerly allocated on this PDCH for some TBFs
If the Ater is in high usage

Percentage of used Ater nibbles, in a GPU > Ater_Usage_Threshold
Then, the number of GCHs targeted per PDCH is reduced

Target_Nb_GCH_per_PDCH x GCH_RED_FACTOR_High_Ater_Usage
In case of DTM:
Ater_Usage_Threshold is not taken into account
1 2 61
For other cases, each time some radio resources (for a TBF or for an RT PFC) are allocated on a new PDCH of a TRX (new PDCH means that no radio resources were formerly allocated on this PDCH for some TBFs or for some RT PFCs), then a value called alpha_HiAter shall be associated to this PDCH. The value of alpha_HiAter to be associated to a newly-used PDCH is computed as follows: If the Ater usage of the GPU is normal (nominal case): alpha_HiAter = 1, If the Ater usage of the GPU is high (high Ater usage situation): alpha_HiAter = GCH_RED_FACTOR_High_Ater_Usage, with GCH_RED_FACTOR_High_Ater_Usage the O&M parameter value. The value of alpha_HiAter is used in the Target_Nb_GCH computing. If the Ater usage of the GPU is high, this will have the effect of applying a GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) to the number of GCHs targeted per PDCH, when opening new PDCHs. Some consequences of this mechanism are: If the Ater usage of the GPU becomes high, then the Ater consumption will increase more slowly from this moment, If the Ater usage of the GPU stays high for a long time, and if the PDCH closure and (re)opening rate is sufficient in the GPU, then the GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) will tend to be applied on many of the TRXs managed by the GPU, which will lead to a pseudo-equity in the usage of the Ater resources of the GPU.
Transmission Resource Availability: High Ater Usage [cont.]

Example:
Considering an MEGCH link of a TRX supporting one 4-TS best-effort EGPRS TBF MAX_EGPRS_MCS = MCS-9 GCH_RED_FACTOR_High_Ater_Usage = 0.75 Target_Nb_GCH = 1*4.49+1*4.49+1*4.49+1*4.49 = 18 GCHs if Ater usage of the GPU is normal Target_Nb_GCH = 0.75*4.49+0.75*4.49+0.75*4.49+0.75*4.49 = 14 GCHs if Ater usage of the GPU is high
1 2 62
For other cases, each time some radio resources (for a TBF or for an RT PFC) are allocated on a new PDCH of a TRX (new PDCH means that no radio resources were formerly allocated on this PDCH for some TBFs or for some RT PFCs), then a value called alpha_HiAter shall be associated to this PDCH. The value of alpha_HiAter to be associated to a newly-used PDCH is computed as follows: If the Ater usage of the GPU is normal (nominal case): alpha_HiAter = 1, If the Ater usage of the GPU is high (high Ater usage situation): alpha_HiAter = GCH_RED_FACTOR_High_Ater_Usage, with GCH_RED_FACTOR_High_Ater_Usage the O&M parameter value. The value of alpha_HiAter is used in the Target_Nb_GCH computing. If the Ater usage of the GPU is high, this will have the effect of applying a GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) to the number of GCHs targeted per PDCH, when opening new PDCHs. Some consequences of this mechanism are: If the Ater usage of the GPU becomes high, then the Ater consumption will increase more slowly from this moment, If the Ater usage of the GPU stays high for a long time, and if the PDCH closure and (re)opening rate is sufficient in the GPU, then the GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) will tend to be applied on many of the TRXs managed by the GPU, which will lead to a pseudo-equity in the usage of the Ater resources of the GPU.
Number of Radio TS Determination


Available_Nb_GCH

TRX list



Test if enough GCHs


1 2 63
Number of Radio TS Determination [cont.]

The number of radio TSs is determined for:
The direction of the request (n_MS_requested) The concurrent direction (n_MS_requested_concurrent)
B10
Taken into account

The MS multislot class, (or DTM (E)GPRS 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
Extended Dynamic Allocation allowed or not (EN_EDA) The traffic type

Only 1 TS is allocated in case of GMM/SM signaling traffic
1 2 64
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 All Rights Reserved Alcatel-Lucent 2008 3JK10864AAAAWBZZA Issue 02 Section 1 Module 2 Page 64
Best Candidate Allocation Computation

B10

Available_Nb_GCH

TRX list



Test if enough GCHs


1 2 65
SPDCH States
GPRS
B10
MAX_XX_TBF_SPDCH
PDCH ALLOCATED
PDCH ACTIVE
PDCH FULL
PDCH TCH State
EGPRS
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 TCH State: If a TCH has been allocated by the MFS on this PDCH for a DTMcapable MS
1 2 66
Following states are defined for a PDCH: Allocated: the PDCH is an SPDCH which has been indicated as usable for PS traffic by the BSC. Active: an allocated PDCH is active if it supports at least one radio resource allocated for a TBF or for an RT PFC. Full: 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.
Available Throughput Computation

For a GPRS TBF, in case of only BE TBFs with the same priority
n
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
n
available_ throughput _candidate_XL = R_AVERAGE_EGPRS *

i =1
NB_TBF
PDCHi
+1
NB_TBFPDCHi represents the number of already allocated EGPRS TBFs on the PDCH i
Appendix
1 2 67
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
1 2 68
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).
Candidate TS Allocation Sorting [cont.]
B10
The criteria of the TBF radio resource allocation/reallocation algorithm in case of DTM mode are throughput-based:
DTM A/ The candidate time slot allocations, which have the lowest number of PDCHs in the EGPRS state are preferred DTM B/ the candidate time slot allocations, which have the highest available throughput in the direction of the bias are preferred DTM C/ the candidate time slot allocations, which have the highest available throughput in the direction opposite to the bias are preferred DTM TCH 1/ the candidate time slot allocations for which (Nb_BE_TBF_DL + Nb_BE_TBF_UL) Is the lowest on the TS supporting the TCH are preferred DTM D/ the candidate time slot allocations, which are on the TRX with the highest priority, are preferred DTM TCH 2/ for an MS class 11, the candidate time slot allocations whose TCH is located on TS(n), with n>=1 and with TS(n-1) valid to support TBFs resources in both UL and DL are preferred DTM TCH 3/ the candidate time slot allocations whose TCH has the lowest TS index (on a given TRX) is prefered
1 2 69
Criterion [DTM A]: The TS of a candidate timeslot allocation supporting the TCH shall not be taken into account in the evaluation of this criterion. This criterion is only relevant for: GPRS DTM allocation request T3 GPRS TBF reallocation request for an MS in DTM mode when considering the UL direction of a candidate timesolt allocation. Criterion [DTM TCH 1]: Nb_BE_TBF_XL indicates the total number of BE TBFs (GPRS or EGPRS) which have some radio resources allocated on the considered PDCH in a given direction. Criterion [DTM TCH 2]: This criterion is only applicable for an MS whose DTM [E]GPRS multislot class is 11. This criterion shall not be applied for an MS whose DTM [E]GPRS multislot class is 5 or 9. This criterion has for goal to allow (if possible) a future T3 reallocation of the UL TBF of the DTM MS from DA to EDA mode Example : If only TS0 and TS1 are allocated, a DTM request for a MS class 11 will be reserved on TS0 (DL and UL), TCH on TS1. If a third TS is allocated, a T3 reallocation of the UL TBF to EDA will be possible Criterion [DTM TCH 3]: For an MS whose DTM [E]GPRS multislot class is 11, criterion [DTM TCH 2] will have precedence over this criterion, thus preventing (if possible) the usage of the leftmost TS of the TRX of a TCH allocation.
Re-allocation
4 different TBF reallocations are permanently activated:
B10
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 Reallocate the UL TBFs established in the cell
From DA to EDA mode, or from EDA to DA mode
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
In case of DTM mode, reallocations are forbidden (MR1)
1 2 70
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). Note: the case where an UL TBF is established using EDA, the MS bias become equal DL and the DL TBF (concurrent of the UL TBF) is released is neglected. In this case, as there is no TBF established in the direction of the bias (DL), the MS will not be candidate for T3 reallocation, and the reallocation from EDA to DA will not operate for the UL TBF, even if the usage of EDA is no longer valid for this UL 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.
Re-allocation [cont.]
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%)
1 2 71
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.
Re-allocation: Example
Initial situation:
3 MSs (MSa, MSb, and MSc), all GPRS and (4+1)
0 1 2 3 4 5 6 MSb 7 0 1 2 3 4 5 6 7
UL DL
MSa MSc
UL DL
MSc MSc MSc MSc MSa MSa MSa MSa MSb MSb MSb MSb
MSC is the most impacted by the multiplexing in terms of throughput
Final Situation:
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 MSa 3 4 5 6 MSb 7 0 1 2 MSc 3 4 5 6 7
UL
UL
DL MSa MSa MSa MSa MSb MSb MSb MSb
DL MSc MSc MSc MSc
1 2 72
4 TBF Release Routine
1 2 73
Justification
Wap access to home page without any feature
UL DL
B10
With Delayed DL TBF Release (B7)
With Delayed DL TBF TBF Release & (I) Extended UL TBF Mode (B10)
Typical gain on Wap access to home page:

~8 seconds with Delayed DL TBF Release + ~2 seconds with Extended UL TBF Mode
New B10 feature to enhance MS battery saving
1 2 74
Delayed DL TBF Release
1 2 75
(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.
Delayed DL TBF Release [cont.]

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
1 2 76
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.

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)
1 2 77
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.

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
1 2 78
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).
DL TBF Extension
1 2 79
(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.
DL TBF Extension [cont.]

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
Exercise
1 2 80
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.
Fast DL TBF Re-establishment

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
1 2 81
T3192 = 500 ms (default value which can be set at OMC-R level).
Fast DL TBF Re-establishment [cont.]

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
1 2 82
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.
Non-DRX Mode after Packet Data Transfer

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)
1 2 83
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).
Non-DRX Mode after Packet Data Transfer [cont.]

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
1 2 84
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.
DL TBF Release: Summary

T_NETWORK_RESPONSE_TIME
DL TBF
TBF active TBF delayed T3192 Fast DL TBF establishment via PACCH
DL TBF
release T3192 DRX_TIMER_MAX Fast DL TBF establishment via AGCH or any PPCH
DL TBF
T3192
Non-DRX mode
DRX_TIMER_MAX
DL TBF
1 2 85
Non-DRX mode
DL TBF establishment 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.
Delayed UL TBF Release: Without Extended Mode

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
1 2 86
The UL Delayed TBF release (scheduling of additional USF) is only possible for a Rel-4 MS.
Delayed UL TBF Release: Without Extended Mode [cont.]

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 (lastLLC) (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 2 87
(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.
Delayed UL TBF Release: Without Extended Mode [cont.]

Delayed final PUAN, with DL TBF establishment
MS MFS SGSN
RLC/MAC block (BSN=n, CV=0) (1) LLC PDU (lastLLC) (2) P. UL Ack/Nack (FAI=0, SSN = n) (3) (4) T_DELAYED_FINAL_PUAN PACKET DOWNLINK ASSIGNMENT (6) DL LLC PDU (5)
T3180 Packet Control Ack (7) (8) final P. UL ACK/NACK + polling Packet Control Ack (9) (10)
T3180n
1 2 88
(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.
Delayed UL TBF Release: with Extended Mode

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 RLC/MAC block (BSN=n, CV=0) MFS start LLC PDU (last LLC) SGSN
P. UL Ack/Nack (FAI=0, SSN = n+1) USF Dummy RLC data block T_MAX_EXTENDED_UL
. . .
USF Dummy RLC data block final P. UL ACK/NACK + polling Packet Control Ack
expiry
1 2 89
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.
Delayed UL TBF Release: with Extended Mode [cont.]

The UL transfer can resume at any time during the extended phase
MS
Active UL data transfer
MFS RLC/MAC block (BSN=n, CV=0) start
SGSN
LLC PDU (last LLC)
P. UL Ack/Nack (FAI=0, SSN = n+1) USF
Extended UL data transfer
Dummy RLC data block USF Dummy RLC data block USF RLC/MAC block (BSN=n+1) stop T_MAX_EXTENDED_UL
Active UL data transfer
USF RLC/MAC block (BSN=n+2)
. . .
1 2 90
LLC PDU

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)
1 2 91
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 MSs 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.

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
1 2 92
Delayed UL TBF Release: Improved Extended Mode

Principle: make optional the MS answers to USF
BSS sends first USF at each block or every T_EXTENDED_UL_TBF_POL In case of no MS answer, N3101 is incremented
B10
When N3101 reaches N3101_POLLING_THR, BSS sends polling (PUAN with polling request) every T_UL_RLS_EUTM In case of no answer to the polling, N_POLLING_EUTM is incremented When N_POLLING_EUTM_LIMIT is reached, Tbf is abnormally released Regular USF sent allows MS to resume UL traffic at any time (but N3101 is no more incremented when no MS answer)
1 2 93
Principle is to make optional MS answers to USF in Extended UL phase When an MS enters Tbf UL releasing phase, BSS knows only if MS supports Extended UL (but can not know if the MS supports Improved or Normal Extended UL mode)
Delayed UL TBF Release: Improved Extended Mode [cont.] B10

UL transfer can resume at any time during the improved extended phase 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 NO ANSWER
. . .
N3101 ++
USF NO ANSWER P. UL ACK/NACK + polling USF Packet Control Ack USF P. UL ACK/NACK + polling USF Packet Control Ack
1 2 94
T_MAX_EXTENDED_UL N3101 ++ N3101_POLLING_THR
T_UL_RLS_EUTM
When an MS enters Tbf UL releasing phase, BSS knows only if MS supports Extended UL (but can not know if the MS supports Improved or Normal Extended UL mode)
UL TBF Release: Summary

Delayed final PUAN (without extended mode)
T_DELAYED_FINAL_PUAN
UL TBF
TBF active release
Extended UL TBF mode

T_MAX_EXTENDED_UL
UL TBF
TBF active TBF extended release
1 2 95
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.
5 Exercises
1 2 96
5 Exercises
(E)GPRS Channels
UL PDTCH and PACCH multiplexing on SPDCH:
UL transfer? DL transfer?
Back
DL RLC header Block number Block n Block n+1 Block n+2 Block n+3 Block n+4 Block n+5 Block n+6
1 2 97
ULBlock Content? MAC header USF USF j USF k USF j USF k ??? USF j USF k RRBP false false +3 false false false false ? ? ? ? ? ? ?
TFI PDTCH / PACCH a PDTCH / PACCH b PDTCH / PACCH a PDTCH / PACCH b PDTCH / PACCH b PDTCH / PACCH b PDTCH / PACCH a TFI a TFI b TFI a TFI b TFI b TFI b TFI a
5 Exercises
Autonomous Packet Resource Allocation

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
1 2 98
5 Exercises
Autonomous Packet Resource Allocation [cont.]

TRX_PREF_MARK
0
TRX1
3
RANK= ?
BCCH SDCCH TRE G4 MP FR
TRX2
SDCCH TRE G3
DR
RANK= ?
TRX3 TRE G4 MP FR RANK= ?

Back
TRX4 TRE G3 DR RANK= ?
1 2 99
5 Exercises
Autonomous Packet Resource Allocation [cont.]

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 MAX_SPDCH_LIMIT
Any Remark? Define a rule (relationship between some parameters) to fix this nonoptimal setting
1 2 100
Back
5 Exercises
TBF Radio Resources Allocation and Re-allocation

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:

1 2 101
Back
5 Exercises
TBF Radio Resources Allocation and Re-allocation [cont.]

Fill in the initial TBF allocation TS mapping UL/DL
DL
UL
1 2 102
5 Exercises

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 Default MS multislot class = 4 + 1 All the MSs are 4 + 1 MSs Time allowed: 20 minutes
1 2 103
Back
5 Exercises

MS constraints:
0 Rx 1 Rx 2 Rx 3 Rx 4 5 6 Mx 7 DL
Ttb UL 0 1 Tx 2 3
Tra
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 MSd: EGPRS UL TBF followed by DL TBF
Bias = DL
1 2 104
5 Exercises

Fill in the initial TBF allocation TS mapping UL/DL
PDCH 0 1 2 3 4 5 6 7 Rank
TRXa EGPRS
UL 1 DL
TRXb GPRS
UL
DL
1 2 105
5 Exercises
DL TBF Release Routine

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

1 2 106
5 Exercises
DL TBF Release Routine [cont.]
Back
1 2 107

1 2 108
End of Module Radio Resource management
1 2 109
13

Module 3 Radio Link Control
Blank Page
132
Radio Algorithms Radio Link Control EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Module Objectives
Describe the algorithms of Radio Link Control and the related parameters
133
134
Table of Contents
1 2 3 4 5 6 7 8 9 GPRS CS Adaptation EGPRS MCS Adaptation RLC Blocks Retransmission UL Power Control NC0 Cell Selection and Reselection NC2 Cell Reselection Flow Control at the Gb Interface Radio Link Supervision Exercises Page 7 22 37 46 50 63 89 96 106
135

Page
136
1 GPRS CS Adaptation
137
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
138
CS-1: 20 useful bytes per RLC block. CS-2: 30 useful bytes per RLC block. CS-3: 36 useful bytes per RLC block. CS-4: 50 useful bytes per RLC block. MCS-1: 22 useful bytes per RLC block. MCS-2: 28 useful bytes per RLC block. MCS-3: 37 useful bytes per RLC block. MCS-4: 44 useful bytes per RLC block. MCS-5: 56 useful bytes per RLC block. MCS-6: 74 useful bytes per RLC block. MCS-7: 2x56 useful bytes per RLC block. MCS-8: 2x68 useful bytes per RLC block. MCS-9: 2x74 useful bytes per RLC block. Only changes between consecutive CSs can occur, except in case of defense mechanism, see Defense procedure slide.
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
139
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 = STtn * 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 = LTtn * yn + 1, and LT = (1 - )(1 / CS_AVG_PERIOD_LT)
1 3 10
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 can be set at OMC-R level (cell level).
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 I_LEVEL_TNi I_LEVEL_TNi Etc. I_LEVEL_TNi I_LEVEL_TNi = 0 when CH > C = 1 when C-2dB < CH <= C = 2 when C-4dB < CH <= C-2dB = 14 when C-28dB < CH <= C-26dB = 15 when CH <= C-28dB
AV_SIR = average value of I_LEVEL_TNi of all assigned DL TS i
1 3 11
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. Default values is : N_AVG_I: 6 It Can be set at the OMC-R level (cell level). For more details about measurements and averages performed by the MS, see 3GPP 05.08.
DL CS Adaptation
Functional process
MS
Packet DL Ack/Nack (RXQUAL, I_Level_TNi)
MFS
Packet DL Ack/Nack (RXQUAL, I_Level_TNi) Averaging - AV_RXQUAL_ST - AV_RXQUAL_LT - AV_SIR Link adaptation new CS current CS
O&M threshold and hysteresis
1 3 12
DL CS Adaptation [cont.]
Threshold comparison when I_LEVEL_TNi are reported
Current coding scheme CS-1 Increasing the coding scheme number (CSi CSi+1) Decreasing the coding scheme number (CSi CSi-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 OR AV_RXQUAL_ST > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_ST AV_RXQUAL_LT > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT OR AV_RXQUAL_ST > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_ST
CS-2
AV_RXQUAL_LT < CS_QUAL_DL_2_3_X_Y AV_RXQUAL_LT < CS_QUAL_DL_3_4_X_Y AND AV_SIR > CS_SIR_DL_3_4_X_Y
CS-3
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

1 3 13
Radio Algorithms Radio Link Control EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
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
Threshold comparison when I_LEVEL_TNi are NOT reported
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 OR AV_RXQUAL_ST > CS_QUAL_DL_1_2_X_Y + CS_HST_DL_ST AV_RXQUAL_LT > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT OR AV_RXQUAL_ST > CS_QUAL_DL_2_3_X_Y + CS_HST_DL_ST CS4_BLER > CS_BLER_DL_4_3
CS-2
AV_RXQUAL_LT < CS_QUAL_DL_2_3_X_Y AV_RXQUAL_LT < CS_QUAL_DL_3_4_X_Y AND CS3_BLER < CS_BLER_DL_3_4 Not possible
CS-3
CS-4

1 3 14
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).
Summary
AV_RXQUAL_LT 7
CS-1
CS_QUAL_DL_1_2_X_Y+ CS_HST_DL_LT CS_QUAL_DL_1_2_X_Y CS-1 or CS-2 (hysteresis)
CS-2
CS_QUAL_DL_2_3_X_Y + CS_HST_DL_LT CS_QUAL_DL_2_3_X_Y CS-2 or CS-3 (hysteresis) C S_QUAL_DL_3_4_X_Y
CS-3
0 0 100%
1 3 15
CS-4
CS-3 or CS-4 (hysteresis) AV_SIR 15 BLER 0%
CS_SIR_DL_3_4_X_Y
CS_SIR_DL_3_4_X_Y + CS_SIR_HST_DL CS_BLER_DL_4_3
CS_BLER_DL_3_4
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.
UL CS Adaptation [cont.]
Functional process
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 adaptation new CS current CS
1 3 16
Threshold comparison
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 OR AV_RXQUAL_ST > CS_QUAL_UL_1_2_X_Y + CS_HST_UL_ST AV_RXQUAL_LT > CS_QUAL_UL_2_3_X_Y + CS_HST_UL_LT OR AV_RXQUAL_ST > CS_QUAL_UL_2_3_X_Y + CS_HST_UL_ST AV_RXQUAL_LT > CS_QUAL_UL_3_4_X_Y + CS_HST_UL_LT OR AV_RXQUAL_ST > CS_QUAL_UL_3_4_X_Y + CS_HST_UL_ST
CS-2
CS-3
CS-4
Not possible

1 3 17
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
Summary
AV_RXQUAL_LT 7
CS1
CS_QUAL_UL_1_2_X_Y + CS_HST_UL_LT CS_QUAL_UL_1_2_X_Y CS1 or CS2 (hysteresis)
CS2
CS_QUAL_UL_2_3_X_Y + CS_HST_UL_LT CS_QUAL_UL_2_3_X_Y CS2 or CS3 (hysteresis)
CS3
CS_QUAL_UL_3_4_X_Y + CS_HST_UL_LT CS3 or CS4 (hysteresis) CS_QUAL_UL_3_4_X_Y
CS4
0 0
1 3 18
AV_SIR 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.
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
1 3 19
Defense Procedure
B10
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
1 3 20
TBF_CS_DL = 8 (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.
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
1 3 21
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.
2 EGPRS MCS Adaptation
1 3 22
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 46 45 44 43 42 41 40 39 38 37 36 35
TRE 1
TRE output power (dBm)
APD (dB) 8-PSK attenuation (dB) 8-PSK TRE power (dBm) GMSK TRE power (dBm) GMSK power in the cell (dBm) Max GMSK power in the cell (dBm) Max Power in the cell (dBm)
TRE 1
TRE 2
TRE 2
TRE 3
TRE 3
1 3 23
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 nonconstant 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.
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 "8PSK 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 Max. output power=33 dBm GMSK: Power Class 2 Max. output power = 39 dBm GMSK: Power Class 3 Max. output power = 37 dBm GMSK: Power Class 4 Max. output power=33 dBm GMSK: Power Class 5 Max. output power = 29 dBm APD = 6 8-PSK: Power Class E2 Max. output power = 27 dBm APD = 10 8-PSK: Power Class E3 Max. output power = 23 dBm APD = 10
APD = 4
APD = 10
APD = 10
APD = 0
APD = 6
APD = 10
APD = 0
APD = 2
APD = 6
1 3 24
Measurement Reporting
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]
1 3 25
Measurement Reporting [cont.]

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 (default = 10)
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
1 3 26
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:
MEAN _ BEPblock =
1 4 BEPburst i 4 i =1
2
Coefficient of variation of the Bit Error Probability of a radio block:
CV _ BEPblock =
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
1 4 1 4 BEPburst k 4 BEPburst i 3 k =1 i =1 4 1 BEPburst i 4 i =1
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 (MCS1 to MCS4), 8-PSK (MCS5 to MCS9)) as follows:
MEAN_BEP_TN n = (1 e
xn x ) MEAN_BEP_TN n 1 + e n MEAN_BEPblock,n Rn Rn x x CV_BEP_TN n = (1 e n ) CV_BEP_TN n 1 + e n CV_BEPblock,n Rn Rn

(Rn gives the reliability of the averaged quality parameters)
with
R n = (1 e) R n 1 + e x n , R 1 = 0
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
DL MCS Adaptation
Functional process
MS
MFS
EGPRS Packet DL Ack/Nack (Mean_BEP, CV_ BEP) IR APD Modulation type
current MCS
Link adaptation
link adapatation tables
new MCS
1 3 27
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:
MEAN_BEPn =
R
j
(j) n
MEAN_BEP_TN (j) n
,
(j) Rn
CV_BEPn =
R
j
(j) n
CV_BEP_TN (j) n
R
j
(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.
DL MCS Adaptation [cont.]

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-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]
Each combination of these criteria corresponds to a specific LA table

1 3 28
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 0 0 1 2 3 4 5 6 7 8 9 10 11 12 13 MEAN_BEP 14 15 16 17 18 19 20 21 22 23 24 5 5 5 5 5 5 5 5 5 5 5 6 6 6 7 7 7 7 7 7 7 7 7 8 8 1 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 2 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 6 7 7 7 7 7 8 8 8 3 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 4 1 1 1 2 5 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 7 8 8 8 5 1 1 2 2 2 3 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 8 8 8 6 1 2 2 2 3 3 3 3 5 5 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 7 1 2 2 3 3 3 3 3 4 5 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8
If the effective APD (=max(0, modulation_delta_power |BS_TX_PWR_Max|) does not belong to the APD set which is described above, then the APD value in the set which is immediately higher than the received APD. e.g., if effective APD = 0.7 dB then APD = 1 dB
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
1 3 29
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.
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
1 3 30
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.
UL MCS Adaptation
Functional process
MS BTS MFS
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 adaptation
lin k adapatation tables
new MCS
1 3 31
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 = etn * 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.
UL MCS Adaptation [cont.]

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
APD of the MS: APD set = [0, 1, 3, 4, 5, 6, 8, 10] EN_IR_UL state Modified B10
= 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-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]
Each combination of those criteria corresponds to a specific LA table

1 3 32
The same tables apply in the uplink as in the downlink.
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
1 3 33
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)).
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
1 3 34
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
1 3 35
TBF_MCS_DL = 12 (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 = 12 (Alcatel recommended value) and it cannot be set at OMC-R level.
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 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
1 3 36
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.
3 RLC Blocks Retransmission
1 3 37
New Modulation and Coding Schemes

Data rate per radio TS (RLC payload)
Scheme Modulation GPRS GMSK GMSK GMSK GMSK EGPRS 8PSK 8PSK 8PSK 8PSK 8PSK GMSK GMSK GMSK GMSK Maximum rate (kbps) 20 14.4 12 8 59.2 54.4 44.8 29.6 / 27.2 * 22.4 17.6 14.8 / 13.6 * 11.2 8.8
CS-4 CS-3 CS-2 CS-1 MCS-9 MCS-8 MCS-7 MCS-6 MCS-5 MCS-4 MCS-3 MCS-2 MCS-1 * case of padding
8-PSK modulation to provide higher data rates GMSK modulation to ensure a certain level of performance in case of poor radio conditions
1 3 38
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).
New Modulation and Coding Schemes [cont.]

MCSs are divided into 4 families: A, A padding, B and C
GMSK MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 8-PSK MCS-7 MCS-8 MCS-9
Family C
22
22
22
Family B
28
28
28
28 28
28 28
Family A padding
34+3
34+3
34+3
34 34
34 34
Family A
37
37
37
37 37
37 37
Radio data block

1 3 39
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).
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
This applies only when the MS memory for IR is not full This can apply for both UL and DL EGPRS TBF
Appendix
1 3 40
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).
Type I ARQ Mechanism

MCS selection for retransmission of a DL or UL RLC data block
Commanded MCS (given by the link adaptation algorithm) MCS9 MCS9 MCS8 MCS7 Initial MCS MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS9 MCS8 MCS7 MCS9 MCS7 MCS4 MCS3 MCS2 MCS1 MCS8 MCS6 MCS8 MCS7 MCS6 MCS7 MCS4 MCS3 MCS2 MCS1 MCS7 MCS6 MCS6 (pad.) MCS7 MCS6 MCS7 MCS4 MCS3 MCS2 MCS1 MCS6 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS5 MCS3 MCS3 (pad.) MCS5 MCS3 MCS5 MCS4 MCS3 MCS2 MCS1 MCS4 MCS3 MCS3 (pad.) MCS2 MCS3 MCS2 MCS4 MCS3 MCS2 MCS1 MCS3 MCS3 MCS3 (pad.) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1 MCS2 MCS3 MCS3 (pad.) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1 MCS1 MCS3 MCS3 (pad.) MCS2 MCS3 MCS2 MCS1 MCS3 MCS2 MCS1
1 3 41
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.
Type I ARQ Mechanism [cont.]

Example of a UL EGPRS TBF
MS 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) UL RLC data block first part B1, MCS1 , PS1 UL RLC data block second part B1, MCS1 , PS1 Resegment bit set
1 3 42
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.
Type II ARQ Mechanism

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
B10
The DL resegmentation is allowed If EN_FULL_IR_DL = disabled Modified B10 The UL resegmentation is allowed If EN_RESEGMENTATION_UL= enabled Modified B10
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 2 EGPRS MCS Adaptation)
As IR is optional in UL, the feature can be enabled/disabled using the Cell parameter EN_IR_UL Modified B10
1 3 43
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. EN_FULL_IR_DL, parameter changed from BSS level in B9 to Cell Level in B10. EN_RESEGMENTATION_UL, parameter changed from BSS level in B9 to Cell Level in B10.
Type II ARQ Mechanism [cont.]

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 = disabled
Commanded MCS (given by the link adaptation algorithm) MCS9 MCS9 MCS8 MCS7 Initial MCS MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS9 MCS8 MCS7 MCS9 MCS7 MCS4 MCS3 MCS2 MCS1 MCS8 MCS6 MCS8 MCS7 MCS6 MCS7 MCS4 MCS3 MCS2 MCS1 MCS7 MCS6 MCS6 (pad.) MCS7 MCS6 MCS7 MCS4 MCS3 MCS2 MCS1 MCS6 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS5 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS4 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS3 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS2 MCS6 MCS6 (pad.) MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 MCS1 MCS6
B10
MCS5 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1
In all the other cases, the table used for Type I ARQ is applied
1 3 44
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.
EN_FULL_IR_DL, parameter changed from BSS level in B9 to Cell Level in B10. EN_RESEGMENTATION_UL, parameter changed from BSS level in B9 to Cell Level in B10.
RE W SE IT GM HO EN UT TA TI ON
MCS6 (pad.)

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 MCS9 New MCS MCS6 Previous PS PS1 or PS3 PS2 MCS6 MCS9 PS1 PS2 MCS7 MCS5 MCS5 MCS7 Any Any Any New PS PS1 PS2 PS3 PS2 PS1 PS2 PS1
All other combinations
PS1 is used in case of the first transmission of an RLC data block

Exercise
1 3 45
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.
4 UL Power Control
1 3 46
4 UL Power Control
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
1 3 47
The MS uses DL level measurements to determine the power: open loop PC.
4 UL Power Control
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) or 1/ (12 * T_AVG_T)
(BCCH) (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
1 3 48
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.
4 UL Power Control
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
1 3 49
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
5 NC0 Cell Selection and Reselection
1 3 50
Introduction
2 kinds of selection reselection are implemented in the Alcatel-Lucent 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
1 3 51
Further details concerning Cell selection and Cell reselection in case of PBCCH in the appendix.
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 in the serving cell
1 3 52
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).
Selection
Criteria computation:
Without PBCCH
C1 = (RLA_C RXLEV_ACCESS_MIN) max (0, MS_TXPWR_MAX_CCCH P) RLA_C: average DL level received
Cell choice: the best cell is the cell with the highest C1
1 3 53
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.
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
1 3 54
The same algorithm is used in case the MS is in GSM Idle Mode.
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
Cell choice: the best cell is the cell with the highest C2
1 3 55
The normal procedures apply in case of Cell reselection for a DTM capable MS in PTM.
Reselection During a UL TBF

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)
1 3 56
After a TBF release, it is up to the originator to reinitiate the transfer: the MS in the UL, the SGSN in the DL.
Reselection During a UL TBF [cont.]
?
SGSN
Cell Reselection
MFS
FLUSH LL
1 3 57
CAUTION: animated slide.
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
1 3 58
After a TBF release, it is up to the originator to reinitiate the transfer: the MS in the UL, the SGSN in the DL.
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
1 3 59
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.
NACC and (P)SI Status

2 features are available to reduce 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
B10
(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
1 3 60
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. NACC and (P)SI Status features are supported only if: The MS is neither in dedicated mode nor Dual Transfer Mode The MS is in NCO or NC1 mode The MS is in Packet Transfer Mode.
NACC and (P)SI Status [cont.]

NACC
The MS informs the system that it wants to select a neighboring cell The BSS transmits the partial SI of the neighboring cell
MS UL or DL TBF MFS Cell A MFS Cell B
Packet Cell Change Notification Retrieval of SI instances Packet Neighbor Cell Data (SI1) Packet Neighbor Cell Data (SI3) Packet Neighbor Cell Data (SI13) Packet Cell Change Continue
1 3 61
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.
NACC and (P)SI Status [cont.]

SI Status
The MS has resumed the data transfer in the neighboring cell Then, it asks the system to retrieve the missing Sys-info
MS MFS Cell A UL or DL TBF MFS Cell B
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

1 3 62
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.
6 NC2 Cell Reselection
1 3 63
Aim
Impact of reselection on data transfer
4 1
3 Data Transfer
: 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
1 3 64
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.
Functional Entities
The NC2 process for PS is similar to the HO process for CS
HO
MS - BTS BSC
HO Preparation Radio Link Measurements Active Channel Pre-processing HO Candidate Cell Evaluation HO management
HO Detection
NC2
MS - BTS MFS
NC cell reselection Preparation NC cell Reselection activation NC measurement Reporting and processing NC cell Reselection Detection NC cell Reselection Evaluation NC cell Reselection management
1 3 65
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.
NC Cell Reselection Activation / De-activation

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
B10
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
In case of Dual Transfer Mode, Cell Reselection will be ignored by the MS
1 3 66
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.
NC Cell Reselection Activation / De-activation [cont.]

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) READY MS in NC2 NC_REPORTING_PERIOD_T Packet Measurement Report / PACCH (6)
There is NC2 activation only at the beginning of a DL packet transfer
1 3 67
(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.
NC Cell Reselection Activation / De-activation [cont.]

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 3 68
(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.
NC Measurement Reporting and Processing

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
1 3 69
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)
NC Measurement Reporting and Processing [cont.]

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
1 3 70
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.

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
1 3 71
T_DL_GPRS_MeasReport and T_DL_EGPRS_MeasReport are defined by O&M on a per cell basis.

DL RXQUAL averaging
1 AV_DL_RXQU AL_NC 2p = 1 Up
tp
* AV_DL_RXQU AL_NC 2p 1 + 1 DL_RXQUAL Up
Up = NC 2
= 0.9
Up-1 +1
1/TNC2
forgetting factor: NC2 = (1-)
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
1 3 72
U0 = 0, consequently U1 = 1. In CS4, if RxQual = 7 is reported by the MS, then this measurement is tagged as invalid and so, not taken into account in the averaging.
NC Cell Reselection Detection

Trigger conditions
Priority Highest Lowest
Cause reference PT4 PT3 PT1 PT2
Name of the cause Too bad uplink radio quality Too bad downlink radio quality Too low downlink received signal level Detection of a better neighboring cell
Similar HO cause Cause 2 Cause 4 Cause 5 Cause 12
1 3 73
NC Cell Reselection Detection [cont.]

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
1 3 74
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. In CS4, if RxQual = 7 is reported by the MS, then this measurement is tagged as invalid and so, it will be not taken into account in the averaging and will not disturb the PT3 triggering.

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)
1 3 75

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
1 3 76
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.

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
1 3 77
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).
NC Cell Reselection Evaluation: Functional Entities

- cause reference - neighboring cell that checked the cause
Cell filtering process
Filtering cell list
Cell ranking process
Reference of the target cell
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) GPRS operational state of the neighbor cells
Cell ranking process

This process builds a Filtering Cell List depending on:
C31NC2 Load situation C1NC2 & C2NC2
1 3 78
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.
NC Cell Reselection Evaluation: Criteria Computation

Path loss criterion parameter C1NC2
C1NC2(n) = AV_RXLEV_NC2(n) RXLEV_ACCESS_MIN(n) - max(MS_TXPWR_MAX_CCH(n) P(n), 0)
Cell ranking criterion parameter C2NC2

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
1 3 79
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) is the minimum received signal level required to perform an access to the cell n. 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.
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 GPRS not activated

RA_COLOUR = -1
1 3 80
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.
NC Cell Reselection Evaluation: Cell Ranking Process

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
1 3 81
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.
NC Cell Reselection Evaluation: Cell Ranking Process [cont.]

Serving cell:
C31NC2(n) = AV_RXLEV_NC2(n) HCS_THR(n) HCS_THR(n), signal threshold for applying the load cell situation criterion. C31NC2 is used in serving cell, to differentiate the low loaded target
cells from the high loaded target cells.
1 3 82
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.
NC Cell Reselection Evaluation: Load Evaluation

Every 5 seconds, the MFS computes for each cell
NC2_Load (in %) =
MAX[UL_PS_Used_Bandwidth; DL_PS_Used_Bandwidth ] + CS_Used_Bandwidth 100 Total_PS_Bandwidth

N _ PDCH _ ALLOCATED i =1 N _ PDCH _ ALLOCATED
i =1
Where:
UL_PS_used_Bandwidth = DL_PS_used_Bandwidth = Nb of UL TBFs / MAX_UL_TBF_SPDCH Nb of DL TBFs / MAX_DL_TBF_SPDCH
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
1 3 83
UL_PS_Used_Bandwidth is the bandwidth used by PS traffic in the UL direction. DL_PS_Used_Bandwidth is the bandwidth used by PS traffic in the DL direction. CS_Used_Bandwidth is the bandwidth used by CS traffic.
NC Cell Reselection Evaluation: Load Evaluation [cont.]

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
1 3 84
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.
NC Cell Reselection Execution with NACC

MS 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) T_Wait_Flush Packet Control Acknowledgement / PACCH (5) 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 3 85
BSS Serving cell
BSS Target cell
SGSN
(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.
NC Cell Reselection Execution with LLC PDU Rerouting

MS On going DL TBF Packet Measurement Report / PACCH Packet Cell Change Order / PACCH Packet Control Acknowledgement / PACCH T_Ack_Wait T_Wait_Flush BSS Serving cell BSS Target cell SGSN
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]
1 3 86
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.
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
Old and new ell Flush LL information old BVCI + new BVCI only old BVCI old BVCI + new BVCI same RA different NSEs Yes only old BVCI only old BVCI No DL LLC PDU deletion DL LLC PDU rerouting SGSN Inter-NSE capability MFS behavior
same RA same NSE
DL LLC PDU rerouting DL LLC PDU deletion DL LLC PDU rerouting
1 3 87
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.
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
1 3 88
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).
7 Flow Control at the Gb Interface
1 3 89
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 FLOWCONTROL-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 MS flow control
Used to perform BVC flow control
1 3 90
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.
Flow Control Performed on SGSN Side

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
1 3 91
MS flow control
MS flow control
MS flow control
BVC flow control
BSS
Flow Control Performed on SGSN Side [cont.]

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)
1 3 92
Leaky bucket principle
?
Max bucket size (Bmax)
new LLC PDU
bucket size (B)
leaking rate (R)
Flow Control Performed on BSS Side

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
1 3 93
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.
Flow Control Performed on BSS Side [cont.]

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
1 3 94
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
Flow Control Performed on BSS Side [cont.]

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
1 3 95
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.
8 Radio Link Supervision
1 3 96
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
1 3 97
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 MFSs 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).
DL TBF
Scheduling of Packet DL Ack/Nack PACCH block Stop sending DL PDTCH blocks
DL ACK/NACK PERIOD blocks
PDTCH
PDTCH RRBP false
PDTCH
N3105>N3105_LIMIT
PACCH
N3105 = N3105+1
1 3 98
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 = 20 (Alcatel recommended value) and it can be set at OMC-R level (cell level). EGPRS_N3105_LIMIT = 20(Alcatel recommended value) and it can be set at OMC-R level (cell level).
DL TBF [cont.]
Scheduling of Packet DL Ack/Nack PACCH block Stop sending DL PDTCH blocks
DL ACK/NACK PERIOD blocks
PDTCH
PDTCH RRBP false
PDTCH
N_StagnatingWindowDL > NstagnatingWindowDL_LIMIT
PACCH
Packet DL Ack/Nack
N_StagnatingWindowDL = N_StagnatingWindowDL
+1
Same oldest RLC block Nack in the RBB
1 3 99
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 = 32 (Alcatel recommended value) and it canbe set at OMC-R level (cell level).
UL TBF - Abnormal Release with Random Access

Stop sending Packet UL ACK/NACK PACCH blocks
U S F
U S F
PACCH
N3101>N3101_LIMIT
PDTCH PDTCH
N consecutive
N3101 = N3101+N
Packet Random Access
1 3 100
N3101_LIMIT = 64 (Alcatel recommended value) and it can be set at OMC-R level (cell 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.
UL TBF - Abnormal Release with Random Access [cont.]

U S F
PACCH
U S F
PACCH
N_StagnatingWindowUL > NstagnatingWindowUL_LIMIT
PDTCH SI=1
PDTCH SI=1 N_StagnatingWindowUL = N_StagnatingWindowUL +1
Packet Random Access
1 3 101
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 = 10 (Alcatel recommended value) and it can be set at OMC-R level (cell level).
UL TBF - Abnormal Release with Cell Reselection
N3102
PAN_MAX
Packet UL Ack/Nack received OK
RESELECTION
0
PAN_DEC UL TBF Abnormal release Random Access
PAN_INC
1 3 102
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.
UL TBF - Abnormal Release with Cell Reselection [cont.]

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 5 NC0 Cell Selection and Reselection)
Else the normal reselection algorithm is applied (see 4)
After T_RESEL, the MS is allowed to reselect the serving cell
1 3 103
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 022), 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.
UL TBF in Ending Phase
U S F
PACCH U S F
Final Ack
PACCH
Scheduling of Packet Control Ack PDTCH PACCH
N3103>N3103_LIMIT
Final Block
N3103 = N3103+1
1 3 104
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 = 64 (Alcatel recommended value) and it can be set at OMC-R level (cell level).
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
1 3 105
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
TX _ EFFICIENCY = 100
i =1 NB _ SENT
i =1
i
ni
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. i = 0,40 for CS-1, 0,59 for CS-2, 0.68 for CS-3 and 0.94 for CS-4.
MCS-1 i 0.39 MCS-2 0.49 MCS-3 0.65 MCS-4 0.77 MCS-5 0.98 MCS-6 1.30 MCS-7 2.02 MCS-8 2.45 MCS-9 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 = 200 all can be set at OMC-R level.
9 Exercises
1 3 106
9 Exercises
GPRS CS Adaptation
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
1 3 107
9 Exercises
GPRS CS Adaptation [cont.]

Find which CS is used at each measurement
Measurement RXQUAL_DL AV_RXQUAL_DL_LT AV_RXQUAL_DL_ST 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 AV_RXQUAL_DL_ST
1 0 0,0 0,0
2 0 0,0 0,0
3 2 1,1 1,7
4 3 1,9 2,7
5 4 2,6 3,8
6 5 3,3 4,8
7 5 3,8 5,0
8 5 4,1 5,0
9 6 4,5 5,8
10 0 3,5 1,2
11 0 2,7 0,2
12 0 2,1 0,0
13 0 1,7 0,0
14 6 2,6 4,8
15 7 3,5 6,6
16 7 4,2 6,9
Back
RXQUAL_DL
1 3 108
AV_RXQUAL_DL_LT
Short term average is calculated with AlphaST = 0.2 Short term average is calculated with AlphaLT = 0.8
9 Exercises RLC ACK Mode: New DL MCS Value Determination (1/3)
APD=0dB, Type 2 ARQ, GMSK table: if MCScurrent belongs to {1,2,3,4}

CV_BEP 3 4 1 1 1 1 1 1 1 1 1 1 1 1 2 1 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 5 3 5 3 5 5 6 5 6 5 6 6 6 6 7 6 7 6 7 7 7 7 7 7
APD=0dB, Type 2 ARQ, 8PSK table: if MCScurrent belongs to {5,6,7,8,9}

CV_BEP 3 4 5 1 5 1 5 1 5 2 5 2 5 5 5 5 5 5 5 5 6 5 6 5 6 6 6 6 6 6 6 6 6 6 7 6 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9
0 4 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 1 1 1 1 1 2 2 5 5 5 5 5 5 5 5 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7
1 1 1 1 1 1 2 2 2 2 2 3 3 3 3 5 5 5 5 5 6 6 6 6 6 7 7 7 7 7 7 7 7
2 1 1 1 1 1 1 2 2 2 2 3 3 3 3 3 3 3 3 3 5 5 5 6 6 6 7 7 7 7 7 7 7
5 1 1 1 1 1 1 1 1 2 2 2 3 3 3 3 3 3 3 3 3 3 3 4 4 5 5 5 6 6 7 7 7
6 1 1 1 1 1 1 1 1 2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 4 5 5 5 5 6 6 7 7
7 1 1 1 1 1 1 1 1 2 2 2 3 3 3 3 3 3 3 3 4 4 4 4 4 4 5 5 5 6 6 7 9
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 5 5 5 5 5 5 5 5 5 7 7 7 7 7 7 7 7 7 7 7 7 7 8 8 8 8 8 8 9 9 9 9
1 5 5 5 5 5 5 5 5 5 6 6 6 6 6 6 7 7 7 7 7 7 8 8 8 8 8 8 8 9 9 9 9
2 5 5 5 5 5 5 6 6 6 6 6 6 6 6 6 6 7 7 7 7 8 8 8 8 8 8 8 8 8 8 8 9
5 1 1 2 2 2 3 3 5 3 5 5 5 6 6 6 6 6 7 7 7 7 7 8 8 8 8 9 9 9 9 9 9
6 1 2 2 3 3 3 3 3 3 5 5 5 5 5 5 6 6 7 7 7 7 7 8 8 8 8 9 9 9 9 9 9
7 1 2 2 3 3 3 3 3 4 4 5 5 5 5 6 6 6 6 7 7 7 7 8 8 8 8 9 9 9 9 9 9
MEAN_BEP
MEAN_BEP
9 Exercises
RLC ACK Mode: New DL MCS Value Determination [cont.]

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
1 3 110
9 Exercises
RLC ACK Mode: New DL MCS Value Determination [cont.]

Find which DL MCS is used at each measurement
1 2 20 4 2 2 24 3 2 24 4 3 18 5 7 9 6 5 8 7 3 5 8 0 8
CV_BEP MEAN_BEP MCSind New MCS
Back
1 3 111
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}
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
0 1 1 1 1 1 2 2 5 5 5 5 5 5 5 6 6 6 6 6 6 6 7 7 7 7 7 7 7 7 7 7 7
1 1 1 1 1 1 2 2 2 2 2 3 3 5 5 5 5 5 5 5 6 6 6 6 6 6 7 7 7 7 7 7 7
2 1 1 1 1 1 1 2 2 2 2 2 3 3 3 3 3 5 5 5 5 5 6 6 6 6 7 7 7 7 7 7 7
CV_BEP 3 4 1 1 1 1 1 1 1 1 1 1 1 1 2 1 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 5 3 5 5 5 5 5 5 6 5 6 6 6 6 6 6 7 6 7 6 7 7 7 7 7 7
5 1 1 1 1 1 1 1 2 2 2 2 3 3 3 3 3 3 3 3 3 3 4 5 5 5 5 5 6 6 7 7 7
6 1 1 1 1 1 1 1 2 2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 5 5 5 5 6 6 6 6 7
7 1 1 1 1 1 1 1 2 2 2 3 3 3 3 3 3 3 3 3 4 4 4 4 4 4 5 5 5 6 6 6 9
MEAN_BEP
9 Exercises
RLC ACK Mode: New UL MCS Value Determination [cont.]

Using the previous LA table and the following information, fill in the next table:
APD = 0 dB UL RLC mode = ACK EN_RESEGMENTATION_UL = enabled
1 3 113
9 Exercises
RLC ACK Mode: New UL MCS Value Determination [cont.]

Find which UL MCS is used every 12 radio blocks
CV_BEP MEAN_BEP MCSind N_inf N_sup New MCS 1 2 3 4 5 2 1 2 1 3 20 20 24 24 18 0 0 2 13 14 15 16 17 18 19 20 21 22 23 24 5 2 1 3 2 1 2 5 2 3 7 3 8 7 8 12 16 20 24 10 12 7 20 27 0 0
Back
6 7 9
7 5 8
8 3 5
9 0 8
10 11 12 2 5 7 10 18 8
CV_BEP MEAN_BEP MCSind N_inf N_sup New MCS

1 3 114
9 Exercises
Type II ARQ Mechanism

Replace the ? by the right values in the 6 next cases:
Cases 1a, 1b and 1c:
MS OUT OF MEMORY = Off EN_FULL_IR_DL = disabled
Case 2:
MS OUT OF MEMORY = Off EN_FULL_IR_DL = enabled
Cases 3a and 3b:

MS OUT OF MEMORY = On EN_FULL_IR_DL = disabled

Back
1 3 115
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 B3+B4, 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?
1 3 116
9 Exercises

Case 1b: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = disabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1 DL RLC data blocks B3+B4, MCS7, PS1 DL RLC data blocks B5+B6, MCS7, PS1, + polling request EGPRS Packet DL Ack/Nack (B2 not received) MCS5 commanded by the Link Adaptation algorithm DL RLC data block B2, MCS?, PS? DL RLC data block B7, MCS?, PS?
1 3 117
9 Exercises

Case 1c: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = disabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1 DL RLC data blocks B3+B4, MCS7, PS1 DL RLC data blocks B5+B6, MCS7, PS1, + polling request EGPRS Packet DL Ack/Nack (B2 and B4 not received) DL RLC data blocks B2+B4, MCS?, PS? DL RLC data blocks B7+B8, MCS?, PS?
1 3 118
9 Exercises

Case 2: MS OUT OF MEMORY = Off, EN_FULL_IR_DL = enabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1 DL RLC data blocks B3+B4, 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 B2, MCS?, PS? DL RLC data block B7, MCS?, PS?
1 3 119
9 Exercises

Case 3a: MS OUT OF MEMORY = On, EN_FULL_IR_DL = disabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1 DL RLC data blocks B3+B4, MCS7, PS1 DL RLC data blocks B5+B6, MCS7, PS1, + polling request EGPRS Packet DL Ack/Nack (B2 and B4 not received, MS OUT OF MEMORY = On) DL RLC data blocks B2+B4, MCS?, PS? DL RLC data blocks B7+B8, MCS?, PS?
1 3 120
9 Exercises

Case 3b: MS OUT OF MEMORY = On, EN_FULL_IR_DL = disabled
MS BSS
DL RLC data blocks B1+B2, MCS7, PS1 DL RLC data blocks B3+B4, MCS7, PS1 DL RLC data blocks B5+B6, MCS7, PS1, + polling request
EGPRS Packet DL Ack/Nack (B2 not received, MS OUT OF MEMORY = On) 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?
Back
MCS4 commanded by the Link Adaptation algorithm
1 3 121
9 Exercises
NC0 Cell Selection and Reselection

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
Cell 2 (8564,6169)
CI=6169 GSM900
CI=1964
GSM900
Cell 1 (8564, 1964)

1 3 122
9 Exercises
NC0 Cell Selection and Reselection [cont.]

Parameters settings
For all cells:
RX_LEV_ACCESS_MIN = -103 dBm MS_TXPWR_MAX_CCH_= 33 dBm PENALTY_TIME = 0 (20s) TEMPORARY_OFFSET = 0 dB CELL_RESELECT_OFFSET = 0 dB
CI=1823 GSM900
CI=6271 GSM900
Cell 3 (8557, 1823)

CI=6270 GSM900
CELL_RESELECT_HYSTERESIS
Cell 1: 4 dB Cell 2: 6 dB Cell 3: 6 dB
Cell 2 (8564,6169)
CI=6169 GSM900
CI=1964
GSM900
Cell 1 (8564, 1964)

1 3 123
9 Exercises
NC0 Cell Selection and Reselection [cont.]

Find the cell selected by the MS
Measurements RxLev (1) RxLev (2) RxLev (3)
1 2 3 4 5
-80 -84 -88 -88 -89
-96 -90 -90 -87 -85
-104 -100 -87 -82 -77

CI=6270 GSM900 CI=1823 GSM900 CI=6271 GSM900
Cell 3 (8557, 1823)
Cell 2 (8564,6169)
CI=6169 GSM900
Back
CI=1964
GSM900
Cell 1 (8564, 1964)

1 3 124
9 Exercises
NC2 Cell Reselection

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
Back
1 3 125
9 Exercises
NC2 Cell Reselection [cont.]

All the cells belong to the same BSS
Cell Type Load Average AV_Rxlev_NC2 HCS_THR CRO EN_OUTGOING_GPRS_REDIR C1NC2 C31NC2 Load situation C2NC2 Cell1 Micro 10% -78 dBm -75 dBm +20 dB disabled Cell2 micro 0% -70 dBm -75 dBm +20 dB enabled Cell3 umbrella 80% -82 dBm -90 dBm 0 dB disabled Cell4 umbrella 20% -85 dBm -90 dBm 0 dB disabled Cell5 umbrella 30% -88 dBm -90 dBm 0 dB disabled
1 3 126
9 Exercises
NC2 Cell Reselection [cont.]

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

Back
1 3 127
9 Exercises
Radio Link Supervision

List in the DL and UL the different cases of abnormal release.
1 3 128

1 3 129
End of Module Radio Link Control
1 3 130
14

Module 4 Algorithms Dynamic Behaviors
Blank Page
142
Radio Algorithms Algorithms Dynamic Behaviors EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Module Objectives
Estimate qualitatively the impact of a parameter change in order to solve the typical problems or enhance the GPRS performance
143
144
Table of Contents
1 Optimization of CS Adaptation 2 Optimization of Cell Reselection 3 Enhance the (E)GPRS Performance Page 7 10 17
145

146
1 Optimization of CS Adaptation
147
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?
148
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
149
2 Optimization of Cell Reselection
1 4 10
Cases
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
1 4 11
Case 1: Multilayer Network with PBCCH

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
Micro cell CRO=10dB PENALTY_TIME=60s TEMPORARY_OFFSET=40dB Micro cell
1 4 12
Case 1: Multilayer Network with PBCCH [cont.]

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
Micro cell PRIORITY_CLASS=? HCS_THR=? Micro cell
1 4 13
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_RESELECT_HYSTERESIS(micro, Macro) : NC_RESELECT_HYSTERESIS(Macro, micro)
NC_DL_RXLEV_LIMIT_THR=?
: NC_RESELECT_HYSTERESIS(micro, micro)
1 4 14
Case 3: NC2 Parameters Versus HO Parameters

Link the NC2 parameters to their equivalent HO parameters
NC2
NC_RXQUAL_AVG_PERIOD
HO
L_RXLEV_DL_H
NC_RXLEV_FORGETTING_FACTOR
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
1 4 15
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.
Case 3: NC2 Parameters Versus HO Parameters [cont.]

Fill in the table
Change Qualitative Impact
NC_RXQUAL_AVG_PERIOD
NC_RXLEV_FORGETTING_FACTOR
NC_UL_RXQUAL_THR
NC_DL_RXQUAL_THR
NC_DL_RXLEV_THR
NC_RESELECT_HYSTERESIS
1 4 16
3 Enhance the (E)GPRS Performance
1 4 17
GPRS Services
Always-on
Directories Mobile Office
Voice (!) E-mail Agenda IntraNet/InterNet Corporate Applications Database Access Yellow/White Pages International Directories Operator Services
Media
Fun
Games (Hangman, Poker, etc.) Screen Saver Ring Tone Horoscope Biorhythm
Music Transportation
Flight/train Schedule reservation Downloading of music files or video clips
News (general/specific)
International/National News Local News Sport News Weather Lottery Results Finance News, etc.
Location services
Traffic Conditions Itineraries Nearest Restaurant, Cinema, Chemist, Parking, ATM, etc.
Vertical application
Traffic Management Automation Mobile branches Health
M-commerce
Non physical
on-line Banking Ticketing Auction Gambling, etc.
Physical
On-line shopping On-line food
1 4 18
GPRS Services vs QoS Criteria

According to the service type, the QoS criteria to take into account are different
GPRS and EGPRS Services WAP WEB Browsing (http) Key QoS criteria Access delay Access delay - Throughput
-
Video streaming File transfer (ftp) E-mail (smtp)
Throughput BER BER
1 4 19
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 IP PPP PPP relay SNDCP P LLC RLC MAC RF RLC MAC RF SNDCP P LLC BSSGP NS L1 BSSGP NS L1 relay GTP UDP IP-Gn L2 L1 IP GTP UDP First IP router IP-Gn L2 L1 Last IP router relay IP IP relay IP IP relay
relay
(*)
BSS TE (PC ,PDA ) MS R Um Gb SGSN Gn
GGSN Gi
TCP data segment Possible repartition on the end to end path of the TCP flight size TCP acknowledgement
1 4 20
(*) 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 doesnt mean that simultaneous segments are being transmitted. All Rights Reserved Alcatel-Lucent 2008
PDU Lifetime and TCP Performance

Impact on TCP performance
Throughput
Congestion Window increase
CW decrease
CW increase
CW decrease
Time
1 4 21
PDU Lifetime and TCP Performance [cont.]
LLC frames
TCP/IP frames
SGSN
PDU Life Time
GGSN
TCP server TCP Window = 16 KB
MFS
LLC frames TCP/IP frames
SGSN
GGSN
TCP server TCP Window = 64 KB
MFS
1 4 22
Radio Algorithms Algorithms Dynamic Behaviors EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
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.
PDU Lifetime and TCP Performance [cont.]

Solution:
Increase the PDU Life Time (SGSN parameter) PDU Life Time = 63s
LLC frames
TCP/IP frames
SGSN
PDU Life Time
GGSN
FTP server TCP Window = 64 KB
MFS
1 4 23
TCP Window Size and FTP Performance

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).
1 4 24
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.
TCP Window Size and FTP Performance [cont.]
Maximum throughput obtained with MTU = 1500 bytes and TCP window size = 8 (x1460 bytes).
1 4 25
Radio Algorithms Algorithms Dynamic Behaviors EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
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 Integer 4 8 16 32 N* 1.391 2.681 3.812 3.813 3.808 1.628 2.952 3.877 3.878 3.88 2.95 4.016 4.045 4.043 4.051 2.91 4.111 4.113 4.125 4.092 MTU of 500 Bytes MTU of 576 Bytes MTU of1000 Bytes MTU of 1500 Bytes
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.

1 4 26
End of Module Algorithms Dynamic Behaviors
1 4 27
15

Module 5 Appendix
Blank Page
152
Radio Algorithms Appendix EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Module Objectives
Detect the main GPRS QoS problems of the Alcatel-Lucent BSS
153
154
Table of Contents
1 OMC-R B10 Screens Display 1.1 BSS 1.2 Cell 1.3 Adjacency 2 System Information Broadcasting 2.1 On BCCH 2.2 On PBCCH 2.3 On PACCH 3 MPDCH 4 Handovers for DTM MS 5 Detailed Available Throughput Computation 6 Examples of Puncturing Schemes 7 Extended Cell Overview 8 B10 Features Page 7 8 20 29 30 31 33 36 37 45 49 53 59 75
155

Page
156
1 OMC-R B10 Screens Display
157
1.1 BSS
B10
158
1.1 BSS [cont.]
B10
159
1.1 BSS [cont.]
B10
1 5 10
1.1 BSS [cont.]
B10
1 5 11
1.1 BSS [cont.]
B10
1 5 12
1.1 BSS [cont.]
B10
1 5 13
1.1 BSS [cont.]
B10
1 5 14
1.1 BSS [cont.]
B10
1 5 15
1.1 BSS [cont.]
B10
1 5 16
1.1 BSS [cont.]
B10
1 5 17
1.1 BSS [cont.]
B10
1 5 18
1.1 BSS [cont.]
B10
1 5 19
1.2 Cell
B10
1 5 20
1.2 Cell [cont.]
B10
1 5 21
1.2 Cell [cont.]
B10
1 5 22
1.2 Cell [cont.]
B10
1 5 23
1.2 Cell [cont.]
B10
1 5 24
1.2 Cell [cont.]
B10
1 5 25
1.2 Cell [cont.]
B10
1 5 26
1.2 Cell [cont.]
B10
1 5 27
1.2 Cell [cont.]
B10
1 5 28
1.3 Adjacency
B10
1 5 29
2 System Information Broadcasting
1 5 30
2.1 On BCCH
The BCCH indicates if GPRS is supported in the cell:
SI 3: RA_COLOUR field present if GPRS supported
B10
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
1 5 31
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.
2.1 On BCCH [cont.]

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
B10
GPRS MA: for hopping SPDCH group ACCESS_BURST_TYPE DTM_SUPPORT
1 5 32
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.
2.2 On PBCCH
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)
1 5 33
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.
2.2 On PBCCH [cont.]

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
1 5 34
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.
2.2 On PBCCH [cont.]

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)
1 5 35
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.
2.3 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, DTM_SUPPORT , etc.) Radio Link Supervision parameters, Power control information MS timers for TBF establishment (T3168, T3182, etc.)
B10
1 5 36
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.
3 MPDCH
1 5 37
3 MPDCH
Details on the MPDCH

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)
1 5 38
3 MPDCH
Details on the MPDCH [cont.]

Master channels configuration
On the BCCH TRX Starting from the left BCCH and SDCCH are not overwritten
Example
NB_TS_MPDCH = 4
1 5 39
3 MPDCH

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
1 5 40
3 MPDCH

Example of DL Primary Master Channel:
BS_PBCCH_BLKS=2 BS_PAG_BLKS_RES=6
1 5 41
3 MPDCH

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
1 5 42
3 MPDCH
Exercise
Fill in the blocks of a DL secondary MPDCH multiframe having the following criteria:
Fill in the blocks of a UL PDCH multi-frame having the following criterion:

BS_PRACH_BLKS=4
1 5 43
3 MPDCH
Exercise [cont.]
DL multiframe: secondary MPDCH
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 ?????
1 5 44
Radio Algorithms Appendix EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10 All Rights Reserved Alcatel-Lucent 2008
CAUTION: animated slide
4 Handovers for DTM MS
1 5 45
Characteristics
B10
Handover should be avoided as much as possible since they interrupt the PS connection for a while.If the MS is in DTM MODE( with both CS and PS service), see next slide. Low priority Inter-cell HO are forbidden for MS operating in DTM Scenario for CS handover
MS in DTM in the serving cell Handover CMD sent to the MS MS abnormally releases the TBF MS enters target cell in dedicated mode TBFs are re-established in the new cell in DTM
1 5 46
Characteristics [cont.]
Family Cause Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Better conditions Inter-cell HO Better conditions Inter-cell HO Better conditions Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Emergency Inter-cell HO Forced directed retry HO Better conditions Inter-cell HO Emergency Inter-cell HO Better conditions Inter-cell HO Better conditions Inter-cell HO Channel adaptation intra-cell HO Channel adaptation intra-cell HO Better conditions Inter-cell HO Resource management intra-cell HO Resource management intra-cell HO InterRat HO
1 5 47
B10
Inter-cell HO cause HO cause number cause 2 cause 3 cause 4 cause 5 cause 6 cause 7 cause 10 cause 11 cause 12 cause 13 cause 14 cause 15 cause 16 cause 17 cause 18 cause 20 cause 21 cause 22 cause 23 cause 24 cause 26 cause 27 cause 28 cause 29 cause 30 cause 31 Behavior when the MS is in DTM Enable Enable Enable Enable Enable Enable Disable Disable Enable Disable Disable Enable Enable Enable Enable Enable Disable Enable Disable Disable Disable Disable Disable Disable Disable Enable
Too low quality on the UL Too low level on the UL Too low quality on the DL Too low level on the DL Too long MS-BS distance Consecutive bad SACCH frames received in a microcell Too low level on the UL, inner zone Too low level in the DL, inner zone Power budget Too high level on the UL & DL, outer zone High level in neighbor lower or indoor cell for slow mobile Too high interference level on the UL Too high interference level on the DL Too low level on the UL in a microcell compared to a high threshold Too low level on the DL in a microcell compared to a high threshold Forced directed retry High level in neighbor cell in preferred band Too short MS-BS distance Traffic HO General capture HO HR-to-FR channel adaptation due to bad radio quality FR-to-HR channel adaptation due to good radio quality Fast traffic HO TFO HO Move from PS to CS zone 2G-3G HO
Handover Scenario
B10
MS
Old BTS
Meas Rep.
New BTS
Measurement Result
BSC
MFS
MSC
Dedicated mode [old SACCH]
Physical Context Req. Physical Context Conf.
HO decision
Chan. Act (new TCH) Chan. Act ACK [old FACCH] [new FACCH] HO CMD DR[HO CMD] HO Detect Est. Ind. DI[HO CMP]
Handover Access SABM UA HO Complete
Handover Performed BSC Shared DTM Info Ind (new cell) BSC Shared DTM Info Ind (old cell)
1 5 48
5 Detailed Available Throughput Computation
1 5 49
Formula
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
1 5 50
Formula [cont.]
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
1 5 51
Formula [cont.]
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
available_throughput_candidate_XL = R_AVERAGE_GPRS *
NB_TBF
i =1 n
PDCHi
+1
For a GPRS TBF, in case of only BE TBFs with the same priority
available_ throughput _candidate_XL = R_AVERAGE_EGPRS *
NB_TBF
i =1
PDCHi
+1
Back
1 5 52
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.
6 Examples of Puncturing Schemes
1 5 53
Puncturing Schemes and MCS

The 05.03 GSM recommendation (Channel coding) indicates for each MCS the available puncturing schemes
MCS switched from MCS switched to MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
1 5 54
PS of last transmission before MCS switch PS of first transmission after MCS switch PS1, PS2 PS1, PS2 PS1, PS2, PS3 PS1, PS2, PS3 PS1, PS2 PS1, PS2 PS1, PS2, PS3 PS1, PS2, PS3 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.
Coding and Puncturing for MCS-7

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 Hdr.
TB
E FBI Data = 448 bits BCS
TB
Rate 1/3 convolutional coding 36 bits 135 bits puncturing SB = 8 36 bits 124 bits 612 bits P1 1404 bits puncturing
Rate 1/3 convolutional coding 1404 bits puncturing
612 bits P2
612 bits P3
612 bits P1
612 bits P2
612 bits P3
1392 bits
1 5 55
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:
{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) for j = 0,1,...,77} are transmitted 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) for j = 0,1,...,77} are transmitted 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.
P1

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 Hdr.
FBI
Data = 56 octets = 448 bits
BCS
TB
Rate 1/3 convolutional coding 36 bits 99 bits +1 bit SB = 8 36 bits 100 bits 1404 bits puncturing P1 1248 bits P2 1248 bits
1392 bits
1 5 56

Coding and puncturing for MCS-4; uncoded GMSK, one RLC block per 20 ms 3 bits 36 bits 372 bits
USF
RLC/MAC HCS E Hdr.
FBI
BCS
TB
372 bits P2
372 bits P3
464 bits
1 5 57

Coding and puncturing for MCS-1; rate 0.53 GMSK, one RLC block per 20 ms 3 bits 36 bits 196 bits
USF
RLC/MAC HCS Hdr.
FBI
BCS
TB
Back
372 bits P2
464 bits
1 5 58
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
P2
{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 {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.
7 Extended Cell Overview
1 5 59
Presentation - General
One BTS (G3 or G4): 2 cells
INNER cell: range from 0 to 35 km OUTER cell: range from 33 to 70 km
1 5 60
The extended cell has up to 4 TRX in the inner cell and up to 4 TRX in the outer cell.
Presentation - Synchronization
Freq BCCH OUTER <> Freq BCCH INNER

MS reports measurements on both cells for the handover algorithms
BSICINNER = BSICOUTER
INNER cell can decode the RACH received on OUTER BCCH frequency
INNER cell always BARRED

MS always camps on OUTER cell
INNER cell
1 5 61
OUTER cell
At the border of the two cells, an overlapping area allows to provide a continuous coverage. When the MS moves from one cell to the other, a handover is triggered in the overlap zone. Two BCCH channels are needed (one for the inner cell, one for the outer cell), so that the MS reports measurements on both cells for the handover algorithms. The TRXs of the inner cell and of the outer cell are synchronised, but the reception of the outer cell is delayed by 60bits period to account for the propagation delay. In the inner cell, the MS can receive the BCCH inner frequency as wells as the outer BCCH frequency. To avoid to manage RACH reception on two different frequencies in the inner cell, the MS is forced to access the inner cell on the outer BCCH frequency. For this purpose, the RACH reception (BCCH TRX) of the inner cell is tuned to the outer BCCH frequency, and the inner cell is barred1. So on time slot 0 of the inner cell, transmission is done on the inner cell BCCH frequency, and reception is done on outer BCCH frequency. The chosen implementation allows to make use of all timeslots2 of the TDMA frame and to use the combined configuration for the CCCH channel.
Presentation - RF Interference
UL interference on TS0 of the INNER cell if
Access burst received in the INNER cell (on frequency BCCH OUTER) AND Call on TS7 of the OUTER cell
Then, TS7 of the OUTER cell is always set to IDLE (never used)
1 5 62
Radio Link Establishment - MS Located in the Outer Cell Area
1 5 63
The inner cell is always barred, so the MS cannot camp on the inner cell, even if located in the inner cell range. In the whole extended cell coverage, the MS has a good reception of the outer cell BCCH, so the MS will always be camping in the outer cell, whether in the inner cell or outer cell range. For this reason, a special radio and link establishment procedure is used to cope with this behaviour . It consists of receiving the CHANNEL REQUEST messages on outer BCCH frequency, and allocating the SDCCH channel according to the MS estimated position. The IMMEDIATE ASSIGNMENT COMMAND for an SDCCH is sent on the outer cell BCCH frequencies, but the SDCCH may be allocated in either inner or outer cell, depending on the MS position. (1) The MS camping on the outer cell sends an access burst on the RACH on outer cell BCCH frequency. These bursts will be received successfully in the inner cell by the BCCH TRE. In the outer cell, the access burst arrives too early and cannot be decoded. (2) The inner cell BCCH TRE sends a CHANNEL REQUIRED message to the BSC containing the random reference sent by the mobile, the TDMA frame number when the message was sent over the air and the measured TOA. (3) The TCU controlling this TRE allocates an SDCCH subchannel to the transaction in the inner cell and asks the BTS to activate this subchannel. (4) The BTS activates the requested channel and sends back and acknowledgement, once this is done. (5) The TCU sends the IMMEDIATE ASSIGNMENT COMMAND (which provides the description of the allocated SDCCH) to the BCCH TRE of the inner cell. The TCU controlling the inner cell BCCH sends a copy of the message to the TCU handling the BCCH of the outer cell. This is done if and only if the timing advance IE included in the CHANNEL REQUIRED is smaller than 60, thus indicating that the MS is strictly in the inner cell (in order to avoid that the MS receives two Immediate Assignment messages when located in the overlap zone). The TCU controlling the outer cell BCCH forwards the IMMEDIATE ASSIGNMENT COMMAND to the outer cell BCCH TRE. (6) The IMMEDIATE ASSIGNMENT message is sent over the air to the MS on the AGCH of the outer cell. (6') The IMMEDIATE ASSIGNMENT message sent by the inner cell is lost, because the MS listens to the outer cell frequency. (7) The mobile switches its transceiver to the SDCCH allocated in the inner cell and sends repeatedly an SABM frame to establish the layer 2 connection with the BTS. (8) The BTS acknowledges the establishment of the LapDm link to the MS with a UA frame sent on the SDCCH allocated to the MS.
Radio Link Establishment - MS Located in the Inner Cell Area
If TA < 60
1 5 64
The TCU sends the IMMEDIATE ASSIGNMENT COMMAND (which provides the description of the allocated SDCCH ) to the BCCH TRE of the inner cell. The TCU controlling the inner cell BCCH sends a copy of the message to the TCU handling the BCCH of the outer cell. This is done if and only if the timing advance IE included in the CHANNEL REQUIRED is smaller than 60, thus indicating that the MS is strictly in the inner cell (in order to avoid that the MS receives two Immediate Assignment messages when located in the overlap zone). The TCU controlling the outer cell BCCH forwards the IMMEDIATE ASSIGNMENT COMMAND to the outer cell BCCH TRE. (1) The MS in the outer cell sends an access burst on the RACH of the outer cell. This burst is successfully received by the outer cell BCCH TRE. In the inner cell, the access burst arrives too late to be successfully decoded. (2) The outer cell BCCH TRE sends a CHANNEL REQUIRED message to the BSC containing the random reference sent by the mobile, the TDMA frame number when the message was sent over the air and the measured TOA. (3) The TCU controlling this TRE allocates an SDCCH subchannel in the outer cell to the transaction and asks the BTS to activate this subchannel. (4) The BTS activates the requested channel and sends back an acknowledgement, once this is done. (5) The TCU then sends the description of the channel in the IMMEDIATE ASSIGNMENT COMMAND to the outer cell BCCH TRE. (6) The IMMEDIATE ASSIGNMENT message is sent over the air to the MS on the AGCH of the outer cell. (7) The mobile switches its transceiver to the required channel and sends repeatedly an SABM frame to establish the layer 2 connection with the BTS. (8) The BTS acknowledges the establishment of the LAPDm link to the MS with a UA frame sent on the SDCCH allocated to the MS.
Radio Link Establishment - MS Located in the Overlap Zone
1 5 65
Radio Link Establishment - MS Located in the Overlap Zone [cont.]
1 5 66
(1a&b) The MS camping on the outer cell sends an access burst on the RACH. This burst is correctly received by the inner cell BCCH TRE and outer cell BCCH TRE. (2a&b) The inner cell and outer cell BCCH TRE send a CHANNEL REQUIRED message to the BSC containing the random reference sent by the mobile, the TDMA frame number when the message was sent over the air and the measured TOA. (3a&b) Both TCUs controlling the TREs having BCCH allocate an SDCCH subchannel to the transaction and ask the BTS to activate this subchannel. (4a&b) The BTS activates the requested channels and sends back an acknowledgement for each, once this is done. (5b) The TCU controlling the outer cell, sends the IMMEDIATE ASSIGNMENT COMMAND with SDCCH description in the outer cell to the outer cell BCCH TRE. (5a&c)The TCU controlling the inner cell sends in the IMMEDIATE ASSIGNMENT COMMAND with SDCCH description in the inner cell. Two cases are possible: Access Delay IE > 59 the inner cell TCU will not send a copy of the IMMEDIATE ASSIGNMENT command to the outer cell TCU. This is the desired behaviour. Access Delay in [58,59] range, the inner cell TCU sends a copy of the IMMEDIATE ASSIGNMENT command to the outer cell TCU. This is not the desired behaviour (corresponds to inner cell scenario). This is due to the fact that the BSC definition of the overlap zone does not match the exact BTS overlap area (negative values of TOA in the outer cell up to 2, are clipped to 0). (6b) The IMMEDIATE ASSIGNMENT message describing the SDCCH allocation in outer cell, is sent to the MS on the outer cell BCCH frequency. In most cases this message should be received by the MS (except if 6c is received first) (6a) The IMMEDIATE ASSIGNMENT message describing the SDCCH allocation in inner cell is lost on the inner cell air interface, because the MS does not listen to that frequency. The unused SDCCH will be released by the BSC when the supervising timer expires6. (6c) Access Delay in [58,59] range: The IMMEDIATE ASSIGNMENT message describing the SDCCH allocation in inner cell is sent on the BCCH frequency of the outer cell. In most cases, the MS should have received message (6b) before and has already switched to the SDCCH in the outer cell, and so this message is lost. It is however possible, in case the message (6b) is delayed in the inner cell, that the message (6c) is received earlier by the MS. In this case establishment will occur on the SDCCH allocated in the inner cell (not drawn). (7b) The mobile receives the IMMEDIATE ASSIGNEMENT describing the SDCCH allocation in outer cell on the BCCH outer cell frequency. It then switches to the designated channel and sends repeatedly an SABM frame to establish the layer 2 connection with the BTS in the outer cell. If the message (6c) is received before (6b), then the establishment will occur in the inner cell. (8b) The BTS acknowledges the establishment of the LapDm link to the MS with a UA frame sent on the SDCCH allocated to the MS. (9) The unused SDCCH is released in the inner cell (double SDCCH allocation). If message 6c arrives first, then the unused SDCCH release will occur in the outer cell.
Handover - from the INNER cell to the OUTER Cell
CAUSE 6: Too long distance

AV_RANGE_HO > U_TIME_ADVANCE and EN_DIST_HO = ENABLE
U_TIME_ADVANCE = 62 EN_PBGT_FILTERING = Disable
1 5 67
In the extended cell , the handover procedure is purely controlled by settings of the handover detection parameters. Two special causes allow handover from the inner cell to the outer cell and handover from the outer cell to the inner cell. There is no change in the BSC handover algorithm either for handover preparation or execution. From the inner cell to the outer cell , the handover alarm is only triggered by the handover cause too long MS-BS distance. When this cause is triggered the extended outer cell is always a candidate cell. However the operator setting of the handover parameters must insure that this cause is only triggered when the distance from the serving inner cell BTS is greater than the limit of the overlap zone (TA > 62) by setting U_TIME_ADVANCE to 62. In order to avoid the extended outer cell to be filtered by the filtering process the flag EN_PBGT_FILTERING must be set to DISABLE. The candidate cell evaluation process is recommended to be the GRADE mode.
Handover - from the OUTER cell to the INNER Cell
CAUSE 22: Too short distance

AV_RANGE_HO < L_TIME_ADVANCE
L_TIME_ADVANCE = 0 EN_PBGT_FILTERING = Disable Cause 22 is only checked if

Cell_range(serving) = extended_outer
1 5 68
In the same way, from the outer cell to the inner cell , the handover alarm is only triggered by the handover cause too short MS-BS distance. When this cause is triggered the extended inner cell is always a candidate cell. However the operator setting of the handover parameters must insure that this cause is only triggered when the timing advance applied by the mobile reaches 0, this is achieved by setting L_TIME_ADVANCE to 0. In order to avoid the extended inner cell to be filtered by the filtering process the flag EN_PBGT_FILTERING must be set to DISABLE. The candidate cell evaluation process is recommended to be the GRADE mode.
Handover - from the OUTER or INNER Cell towards Another Cell
All the standard HO causes can be used

Emergency HO causes 2, 3, 4, 5 Better condition HO causes 12, 23, 24
The OUTER or INNER cell is always present in the Candidate Cell Evaluation
1 5 69
The setting of the handover parameter does not prevent any handover cause to trigger an alarm for a handover towards a third cell. It is possible to use exactly the same rules and parameters for handover towards a third cell as in the macro cellular normal cases. The synchronous handover does not work between the inner and the outer cell. In order to avoid call terminations due to directed retry into the inner or outer cell with an incorrect distance range it is recommended to disable the forced directed retry towards the inner and the outer cell. For this purpose, the parameter FREELEVEL_DR(n) is set to the maximum value (255) for the inner and the outer cell. But the Normal DR can be activated.
CS Parameters Setting
The Inner Cell shall always be BARRED If combined CCCH/SDCCH is used in the inner extended cell, then the same configuration is required in outer extended cell, and vice-versa (ie same in both cells) BSICINNER = BSICOUTER The TS 7 of BCCH TRX of outer cell must be set to IDLE The INNER cell and OUTER cell must belong to the same location area Synchronous handover must be disabled. U_TIME_ADVANCE = 62 L_TIME_ADVANCE = 0 EN_PBGT_FILTERING = DISABLE. CELL_EV = Grade FREELEVEL_DR(n) = 255 (this is done automatically, at configuration time) INNER cell and OUTER cell must be neighbour, handover relationship must exist in both directions
1 5 70
Packet Service
Activation of the PS service in an Extended cell
No specific parameter is foreseen
Same procedure as the one used for standard cell is applied
TRX_PREF_MARK = 0
If used, PS must be activated in both INNER and OUTER cell
Reselection
Because the INNER cell is barred
this cell should must not be declared in the neighbor cells reselection adjacencies NC2 is not allowed NACC and (P)SI STATUS are not allowed
The Master channel is not allowed in both INNER and OUTER cell
1 5 71
Packet Service [cont.]

Packet access procedure (1/2)
Same principle as in CS, since its performed on CCCH only
The MS always performs its access on the RACH of the outer BCCH frequency The BTS provides the BSC with the initial TA Depending on the TA value, the BSC chooses the suitable cell (INNER or OUTER)
In UL, whatever the multislot class of the MS, only one PDCH is allocated
Its right or left TS can not be allocated neither for PS nor for CS (see comment) This TS is considered as a restricted TS by the MSF The same constraint is applied in DL for the TS carrying the PACCH
OUTER INNER Allocated UL Restricted

1 5 72
Allocated
Restricted
When a MS passes from inner/outer cell to outer/inner cell, the TA estimated by the BTS stalls progressively. So the MS is not able to apply the suitable correction of its TA for its uplink transfer (data and/or signaling). This leads progressively to the impossibility for the BTS to decode the uplink radio blocks because they shift out of their allocated RTS. For a given MS, its uplink radio blocks progressively come out of its allocated RTS and jams the neighbor RTS. It jams the right RTS when the MS moves from inner to outer cell. This right RTS can also be the RTS0 of the next TDMA frame if the RTS7 is allocated to a TBF. It jams the left RTS when the MS moves from outer to inner cell. This left RTS can also be the TS7 of the previous TDMA frame if the RTS0 is allocated to a TBF. If the neighboring RTS is dedicated to other MS for PS or CS call, this jam causes interferences on these RTS and the BTS can not decode the radio blocks of those MS leading to the drop of these calls. This drawback only occurs for the uplink direction. The downlink direction does not raise any problem. To overcome this drawback, some radio resource allocation constraints are to be applied: An UL TBF is only allocated on one RTS. On BCCH or non BCCH inner TRX, A RTS is allocable to a UL TBF if its right RTS is allocated for PS traffic to the MFS, and is not used by a UL TBF. When a RTS is allocated, its right RTS cannot be allocated to PS call. On BCCH or non BCCH outer TRX, A RTS is allocable to a UL TBF if its left RTS is allocated for PS traffic to the MFS, and is not used by a UL TBF. When a RTS is allocated, its left RTS cannot be allocated to PS call.
Packet Service [cont.]

Miscellaneous
In the OUTER cell, the maximum MCS is limited to MCS-4 The Streaming TBFs (i.e. RT PFC) are not supported The INNER and OUTER cells must be mapped on the same GPU The INNER and OUTER cell must belong to the same routing area
1 5 73
PS Parameters Setting
NETWORK_CONTROL_ORDER = NC0 EN_NACC = Disable EN_PSI_STATUS = Disable NB_TS_MPDCH= Disable MAX_PDCH, MAX_PDCH_HIGH_LOAD and MIN_PDCH must be set to even values (see comments) EN_STREAMING = Disable
1 5 74
As in UL TBF allocation, the MFS uses at least 2 TS (a restricted one and the one allocated in UL) the number of PDCH allocable in the extended cells (MAX_PDCH, MIN_PDCH, MAX_PDCH_HIGH_LOAD ) must be even.
8 B10 Features
1 5 75
8 B10 Features
Summary
B10 MR1
All B9 MR4 Features Dual Transfer Mode (simultaneous CS and PS traffic)
GTTP usage
B10
Improved delayed UL TBF Release
B10 MR2
Extended Dynamic Allocation (more than 2 TS in UL)
1 5 76

1 5 77
End of Module Appendix
1 5 78
DRAFT
@@SECTIONTITLE - @@MODULETITLE
@@SECTION - @@MODULE - 1
@@PRODUCT @@COURSENAME
All Rights Reserved This page is left Alcatel-Lucent 2007 blank intentionally
Copyright 2007 by Alcatel-Lucent - All rights reserved Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel

3fl11830acaawbzza 03

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

3fl11830acaawbzza 03

Diunggah oleh

Hak Cipta:

Format Tersedia

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

EVOLIUM - E-GPRS Radio Algorithms and Parameters Description B10

Switch Safety Warning

Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

Table of Contents [cont.]

Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

Switch to notes view!

After successful completion of this course, you should understand :

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

Course Objectives [cont.]

Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

About this Student Guide

Conventions used in this guide Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

Where you can get further information

All Rights Reserved Alcatel-Lucent 2007

About this Student Guide [cont.]

Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

This page is left blank intentionally

Contract number : Course title :

Client (Company, Center) : Language : Switch

Number of trainees : Surname, First name :

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

Self-Assessment of Objectives [cont.]

Switch to notes view!

EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10

All Rights Reserved Alcatel-Lucent 2007

Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:

Section 1 Radio Algorithms

All Rights Reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2008

Module Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2008

Table of Contents [cont.]

All Rights Reserved Alcatel-Lucent 2008

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2008

Data Transfer with GSM: Circuit Switching

All Rights Reserved Alcatel-Lucent 2008

Data Transfer with GPRS: Packet Switching

GPRS Network Internet

All Rights Reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

All Rights Reserved Alcatel-Lucent 2008

MS Multislot Class [cont.]

MS_authentication_procedure Attach_resp (P_TMSI) Attach_complete ()