Extended Dynamic Allocation (EDA)

not permitted without written authorization from Evolium.
All rights reserved. Passing on and copying of this

document, use and communication of its contents
Site EVOLIUM SAS
VELIZY
Originators Extended Dynamic Allocation (EDA)
SYT
System : ALCATEL GSM BSS

Sub-system : SYS-TLA
Document Category : PRODUCT DEFINITION
ABSTRACT
This SFD describes the "Extended Dynamic Allocation" feature.
The Extended Dynamic Allocation is an extension of the basic Dynamic Allocation (E)GPRS MAC mode to
allow higher throughput in uplink for type 1 mobile stations (supporting the feature) through the support of
more than two radio transmission time-slots.
The Extended Dynamic Allocation (EDA) feature is optional in the B10 release from a commercial point of
view.
Approvals
Name R. MAUGER / G. DAEL E. ZORN J.-P. GRUAU
App. SYT Manager / OSY Manager TPL PM
REVIEW
Ed. 01 Proposal 01 <2005/10/27> SYT document 205382_2 (review report) available at the following
address:
ftp://bssb7:bseven7@bcv68s07.vz.cit.alcatel.fr/projects_ftp/BSS_
B10/B10_SpecTaskForce/WG2_Tel_nonIP/Extended%20Dynami
c%20Allocation/SFD/
Ed. 01 Proposal 02 <2005/12/02> SYT document 205416_2 (mail review report) available at the
address above.
Ed. 01 Proposal 03 <2005/12/22> SYT document 205430 (mail review report) available at the
address above.
Ed. 01 Proposal 04 <2006/01/31> SYT document 206044 (mail review report) available at the
address above.
Ed. 01 Proposal 05 <2006/02/08> No comment received.
Ed. 02 Proposal 01 <2007/03/29> No comment received.
HISTORY
ED 02 RELEASED Extended Dynamic Allocation

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 1/77
Ed. 01 Proposal 01 <2005/10/14> First proposal contains the main impacts of the feature at MAC
level. It is principally based on the following SYT memos:
- 205151: B10 DR0 Extended Dynamic Allocation (EDA)
- 205252: Examples of scheduling methods for TBF in EDA
mode.
Ed. 01 Proposal 02 <2005/11/18> Changes compared to proposal 1:

- Updates taking into account the review report of the first
proposal (dealing with the MAC impacts),
- RRM impacts,
- Annex about PDCH allocation reduction.
Ed. 01 Proposal 03 <2005/12/09> Some editorial changes.

It is clarified that the PDCH allocation reduction is not supported.
Clarifications about NACC/PSI operations. Eventually impacts on
MAC only.
Management of configurations with hole in the assignment (RRM-
PRH and MAC levels).
Support of DTM multislot class 11 (not complete).
Additional precisions about MAC scheduling.
Clarifications about detection of:
- The EDA support by the MS,
- The release of the MS.
Clarifications about assignment strategy.
PMU-PTU interface impacts.
Extension of the EN_EDA OMC-R parameter.
Drafts of MFS PM counters have been added.
Rough impacts on ping performances.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 2/77
Ed. 01 Proposal 04 <2006/01/11> Some editoral changes.
Support of DTM multislot class 11.
Correction of the EN_EDA OMC-R parameter, introduction of new

parameters and correction of existing parameters.
Clarifications about the reading of the MS release and about EDA

MS activation level in RRM-PCC.
Clarifications about the assignment strategy. An annex about

examples of non-multiplexed-EDA strategy has been added.
Introduction of the mechanism based on the

N_UL_BIAS_FOR_EDA to avoid degradations of ping
performances.
Validation part completed.
Introduction of counters and indicators.
The annex about uplink scheduling examples has been updated

(correction of an error in scenario II and addition of a new scenario
related to DTM).
Impacts on step 2 MEGCH and step 2 BSS traffic model capacity

(PS part) added.
Ed. 01 Proposal 05 <2006/01/31> A few editorial changes.
Mechanism based on the N_UL_BIAS_FOR_EDA changed.
The N_UL_BIAS_FOR_EDA parameter is changed from constant

in the DLS to parameter changeable at the OMC-R.
EDA is not supported in extended cells.
Some changes and clarifications in the RRM-PCC and RRM-PRH

sections.
Ed. 01 Released <2006/02/08> Slight change in the wording of the validation part about the tuning
of the N_UL_BIAS_FOR_EDA parameter.
Footnotes are now real footnotes (contents have not been

changed).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 3/77
Ed. 02 Proposal 1 <2007/03/17> Updates taking into account the changes and further
investigations since the first edition:
- It has been added that the feature will be enhanced by the

support of multislot classes 30-33 (RFD
3BKA55CBR195440).
- The issues about BSIC decoding have been clarified.
- One reallocation criterion in case of GPRS UL TBF in

EDA mode / EGPRS DL TBF coexistence has been
removed. The corresponding tests have been removed.
- The checking about Extended and non-Evolium cells is

performed at OMC level (instead of RRM-PCC level).
- The policy for transmission of Packet PDCH release

messages has been changed.
- It has been clarified that, when playing a T3 TBF

reallocation request for an MS having currently an
established UL TBF using EDA, it shall be checked if the
existing TS allocation of the MS can be handled in DA
mode instead of EDA mode. A consequence is that, in
some scenarios, a re-configuration message can be sent
to change the MAC mode without changing the
configuration.
- It has been clarified that, in rare scenarios, an UL TBF can

be established directly in EDA mode.
- Various updates and clarifications about counters and

BTP parameters.
- Various minor updates and clarifications.
- Editorial changes.
Ed. 02 Released <2007/03/29> A few syntax corrections.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 4/77
TABLE OF CONTENTS
1 INTRODUCTION .........................................................................................................................................10
1.1 Scope ..................................................................................................................................................10
1.2 Document Structure ..........................................................................................................................10
1.3 Definitions and pre-requisite ............................................................................................................10
1.3.1 What is the EDA mode? ............................................................................................................10
1.3.1.1 Reminder of the principle of the DA mode................................................................... 11
1.3.1.2 Type 1 mobile stations and limits of the DA mode....................................................... 11
1.3.1.3 Principle / basic rules of the EDA mode ...................................................................... 12
1.3.1.4 Main consequences of the EDA mode ........................................................................ 14
1.3.1.4.1 New radio configurations supported .................................................................... 14
1.3.1.4.2 Additional constraints at MAC level ..................................................................... 15
1.3.1.4.3 Output power reduction issues ............................................................................ 16
1.3.1.5 Paradox of the EDA / When using EDA?..................................................................... 16
1.3.1.6 Availability of the EDA mode........................................................................................ 16
2 HIGH-LEVEL DESCRIPTION .....................................................................................................................18
2.1 Functional Requirements..................................................................................................................18
2.1.1 EDA, an attractive feature for increasing the uplink throughputs ..........................................18
2.1.2 EDA, the restrictions ..............................................................................................................18
2.2 Overall description of the proposed solutions...............................................................................18
2.3 Compliance to the Marketing Requirements ..................................................................................19
2.4 Compliance to 3GPP standard .........................................................................................................20
2.5 Working Assumptions.......................................................................................................................20
2.6 Dependencies ....................................................................................................................................20
2.7 HW Coverage......................................................................................................................................21
2.8 Decision criteria .................................................................................................................................22
2.8.1 Standardisation..........................................................................................................................23
2.8.2 Competition ...............................................................................................................................23
2.8.3 Customer ...................................................................................................................................23
2.8.4 Gains .........................................................................................................................................23
2.8.4.1 Telecom gains.............................................................................................................. 23
2.8.4.2 Operational gains......................................................................................................... 24
2.8.5 Risks ..........................................................................................................................................24
2.8.5.1 Backward compatibilities / R97 mobile stations........................................................... 24
2.8.5.2 Remaining ambiguities of the 3GPP standard before Rel-6........................................ 24
2.8.5.3 Sub-optimal behaviour in case of transmission resource congestion ......................... 24
2.8.5.4 BSIC decoding (for information) .................................................................................. 24
2.8.5.5 Possible slight increase of call drop in case of EDA operations.................................. 25
2.8.5.5.1 PTM operations ................................................................................................... 25
2.8.5.5.2 DTM operations ................................................................................................... 25
2.8.5.6 Possible uncorrect behaviour of the uplink EGPRS link adaptation............................ 25
3 SYSTEM IMPACTS.....................................................................................................................................26
3.1 Telecom ..............................................................................................................................................26
3.1.1 Functional-level description.......................................................................................................26
3.1.1.1 Activation of the EDA feature....................................................................................... 26
3.1.1.2 New configurations supported (in EDA mode) ............................................................ 27
3.1.1.2.1 Multi-slot class 3 .................................................................................................. 27
3.1.1.2.2 Multi-slot class 11 ................................................................................................ 28
3.1.1.2.3 Multi-slot class 12 ................................................................................................ 28
3.1.1.2.4 DTM multi-slot class 11 ....................................................................................... 30
3.1.1.3 EDA operations ............................................................................................................ 30
3.1.1.3.1 Non-multiplexed-EDA strategy ...................................................................... 30

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 5/77
3.1.1.3.2 Making ............................................................................................................... 31

3.1.1.3.3 Limits.................................................................................................................... 33
3.1.1.4 Transmission resource issues ..................................................................................... 34
3.1.1.5 MAC scheduling ........................................................................................................... 34
3.1.1.5.1 Optimal scheduling in case of polling .................................................................. 35
3.1.1.6 Restrictions to avoid bad ping performances .............................................................. 35
3.1.2 Telecom Specification impacts..................................................................................................36
3.1.2.1 Step 2 RRM PCC ......................................................................................................... 36
3.1.2.1.1 Detect if the EDA mode is allowed for a mobile station....................................... 36
3.1.2.1.2 Indicate to PRH if the mobile station supports EDA ............................................ 37
3.1.2.1.3 Bias ...................................................................................................................... 38
3.1.2.1.4 Polling constraints................................................................................................ 38
3.1.2.1.5 Indicate to the mobile station the MAC mode to use........................................... 38
3.1.2.1.6 Indicate to PTU the MAC mode to use ................................................................ 39
3.1.2.1.7 Transmission of NACC/PSI messages................................................................ 39
3.1.2.1.8 Note about Uplink Control Timeslot..................................................................... 39
3.1.2.2 Step 2 RRM-PRH......................................................................................................... 39
3.1.2.2.1 Take into account new radio configurations ........................................................ 39
3.1.2.2.2 Determine the target configuration to try to set-up .............................................. 39
3.1.2.2.3 Determine the best radio allocation ..................................................................... 41
3.1.2.2.4 Impacts on T3 reallocation trigger ....................................................................... 42
3.1.2.2.5 Transmission resource considerations................................................................ 42
3.1.2.2.6 Packet PDCH release policy ............................................................................... 42
3.1.2.2.7 Management of DTM multislot class 11 .............................................................. 42
3.1.2.3 Step 2 MAC.................................................................................................................. 43
3.1.2.3.1 MAC mode to apply ............................................................................................. 43
3.1.2.3.2 Uplink scheduling................................................................................................. 43
3.1.2.3.3 EDA-DA re-configuration ..................................................................................... 49
3.1.2.4 Step 2 RLC................................................................................................................... 49
3.1.2.4.1 MS context ........................................................................................................... 49
3.1.2.4.2 RLC window sizes ............................................................................................... 49
3.1.2.4.3 Link adaptation .................................................................................................... 49
3.1.2.4.4 Transmission of NACC/PSI messages................................................................ 49
3.1.2.4.5 Note about the support of configurations with hole in the assignment................ 50
3.1.2.5 Step 2 BSS traffic model and capacity: PS part .......................................................... 50
3.1.2.6 Step 2 MEGCH ............................................................................................................ 50
3.1.2.7 Interfaces ..................................................................................................................... 50
3.1.2.7.1 PMU-PTU interfaces............................................................................................ 50
3.1.2.8 Radio interface (05.02, 04.06, 04.60, 04.18, 24.008, etc) ........................................... 50
3.1.2.9 Abis interface (08.58)................................................................................................... 50
3.1.2.10 A interface (08.08) ............................................................................................... 50
3.1.2.11 Gb interface (08.18)............................................................................................. 50
3.1.2.12 BSCGP interface ................................................................................................. 50
3.1.2.13 GCH interface ...................................................................................................... 50
3.1.3 Simulations ................................................................................................................................50
3.2 Operation and maintenance .............................................................................................................51
3.2.1 OMC-R parameters ...................................................................................................................51
3.2.1.1 New parameters........................................................................................................... 51
3.2.1.1.1 EN_EDA............................................................................................................... 51
3.2.1.1.2 EDA_MS_ACTIVATION_LEVEL ......................................................................... 51
3.2.1.1.3 ALLOW_DTM_EDA_COMBINATION ................................................................. 52
3.2.1.1.4 N_UL_BIAS_FOR_EDA ...................................................................................... 53
3.2.1.2 Parameters modified.................................................................................................... 53
3.2.2 Modelisation of OMC-R parameters..........................................................................................53
3.2.3 Other parameters ......................................................................................................................53
3.2.3.1 New parameters........................................................................................................... 53
3.2.3.1.1 N_MAX_PERIODIC_REALLOC_SUCCESS_T3 ................................................ 53

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 6/77
3.2.3.2 Parameters modified.................................................................................................... 54

3.2.3.2.1 N_MAX_PERIODIC_REALLOC_T3.................................................................... 54
3.2.3.2.2 N_MAX_PERIODIC_REALLOC_T4.................................................................... 54
3.2.3.2.3 T_CANDIDATE_TBF_REALLOC ........................................................................ 54
3.2.4 PM counters ..............................................................................................................................54
3.2.4.1 Counters in the BSC .................................................................................................... 54
3.2.4.2 Counters in the MFS .................................................................................................... 54
3.2.4.2.1 New counters....................................................................................................... 54
3.2.4.2.2 Existing counters ................................................................................................. 55
3.2.5 PM indicators.............................................................................................................................56
3.2.6 Migration ....................................................................................................................................56
3.2.7 Java scripts................................................................................................................................56
3.2.8 Fault Management.....................................................................................................................56
3.2.9 O&M Specification impacts .......................................................................................................56
3.3 Validation............................................................................................................................................56
3.3.1 Testing tools ..............................................................................................................................56
3.3.2 Test strategy ..............................................................................................................................57
3.3.2.1 System tests coverage................................................................................................. 57
3.3.2.2 Overall strategy for system tests.................................................................................. 57
3.3.2.2.1 Overview .............................................................................................................. 57
3.3.2.2.2 PTM mode ........................................................................................................... 58
3.3.2.2.3 DTM mode (DTM multislot class 11) ................................................................... 59
3.4 Methods ..............................................................................................................................................60
3.5 GCDs ...................................................................................................................................................60
3.6 Engineering rules ..............................................................................................................................60
4 SUBSYSTEM IMPACTS .............................................................................................................................61
4.1 BTS......................................................................................................................................................61
4.2 BSC .....................................................................................................................................................61
4.3 Transcoder .........................................................................................................................................61
4.4 MFS .....................................................................................................................................................61
4.5 OMC-R.................................................................................................................................................61
4.6 LASER.................................................................................................................................................61
4.7 MPM/NPO............................................................................................................................................61
4.8 Polo .....................................................................................................................................................61
4.9 OEF......................................................................................................................................................61
5 PERFORMANCE & SYSTEM DIMENSIONING.........................................................................................62
5.1 Traffic model ......................................................................................................................................62
5.2 Performance .......................................................................................................................................62
5.3 Load constraints................................................................................................................................62
6 OPEN POINTS AND ACTION POINTS......................................................................................................63
6.1 Open points ........................................................................................................................................63
6.2 Action points ......................................................................................................................................63
7 IMPACTS SUMMARY.................................................................................................................................64
8 GLOSSARY ................................................................................................................................................65
8.1 Abbreviations .....................................................................................................................................65
8.2 Terminology .......................................................................................................................................65
9 ANNEXES ...................................................................................................................................................66
9.1 3GPP Standard Reminder .................................................................................................................66
9.1.1 Extracts from 44.060 v6.14.0 Rel-6...........................................................................................66
9.1.1.1 Basic principle .............................................................................................................. 66
9.1.1.2 PACCH operations....................................................................................................... 66
9.1.3 Extracts from 43.064 v6.9.0 Rel-6.............................................................................................67

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 7/77
9.1.4.1 Mobile Station Radio Access Capability Information Element..................................... 68

9.2 List of the TSG GERAN documents concerning EDA and output power reduction ..................70
9.3 Example of uplink scheduling with one TBF in EDA mode ..........................................................70
9.4 Example of radio resource assignment in case of EDA ................................................................70
9.5 PDCH allocation reduction ...............................................................................................................70
9.5.1 B10 context................................................................................................................................73
9.5.1.1 Application domain....................................................................................................... 73
9.5.1.2 Interest ......................................................................................................................... 73
9.5.1.3 Possible implementations ............................................................................................ 73
9.5.1.4 Decision ....................................................................................................................... 73
9.6 Output power reduction....................................................................................................................73
9.6.1 R99 and Rel-4 ...........................................................................................................................73
9.6.1.1 A simple approach ....................................................................................................... 73
9.6.1.2 Extract of the 05.05 (respectively 45.005 for Rel-4) .................................................... 74
9.6.1.3 Expected gain of EDA for a mobile station alone on its PDCH ................................... 74
9.6.1.4 Impacts......................................................................................................................... 75
9.6.2 Rel-5 and beyond ......................................................................................................................75
9.6.2.1 Extract of the 45.005 Rel-5 .......................................................................................... 76
9.7 Overview of impacts on ping performances (compared to B9)....................................................76
9.7.1 Short ping performances ...........................................................................................................77
9.7.2 Long ping performances............................................................................................................77
INTERNAL REFERENCED DOCUMENTS

Not applicable.
REFERENCED DOCUMENTS
Alcatel references
[1] SYT memo 205151 B10 DR0 - EDA
[2] SYT memo 205252 B10 DR0 - Examples of scheduling methods for TBF in EDA
mode
3GPP references
[3] 3GPP TS 44.060 RLC/MAC protocol (Rel-6)
[4] 3GPP TS 45.002 Multiplexing and multiple access on the radio path (Rel-6)
[6] 3GPP TS 24.008 Core network protocols; stage 3 (Rel-6)
[7] 3GPP TS 43.064 Overall description of the GPRS radio interface (Rel-6)
[8] 3GPP TS 51.010-1 Mobile Station Conformance Specification Part 1
RELATED DOCUMENTS

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 8/77
Alcatel documents
[5] 3BK 10204 0026 DTZZA RLC/MAC new scheduling algorithm
[6] 3BKA55CBR195440 (RFD) Support of the 30-33 Multislots classes
3GPP CRs
3GPP CR nb Rev Title Author Accepted?

TS
(Y/N)
44.060 684 / GP- Revised and Clarification of EDA operation Alcatel, Y

Rel-6 051578 merged with in case of polling. NEC
(TSG CR 672 in
GERAN #25) GP-51723 Discussion Paper: GP-51577.
PREFACE
This document is the input paper for the feature Extended Dynamic Allocation inside TD. It will further on
be used as reference for the development of that feature in each subsystem.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 9/77
1 INTRODUCTION
1.1 Scope
The present document aims to be the basis for decision of a proposed change to be made on the BSS
system. It provides all necessary information related to functional description, gains, description of the
system impacts and subsystem impacts.
1.2 Document Structure
The section 2 of this document presents:

The functional requirements,
An overall description of the features,
The compliance to marketing requirements and to the 3GPP standard,
Which working assumptions have been made
And the dependencies,
As well as some decision criteria such as the risk, the gain, etc associated to the features addressed by
the present SFD.
The section 3 identifies the system impacts: it gives the principles and presents the functional split of the
feature between subsystems. The interactions within the BSS between the various modules, layers, etc are
shown as well as the interaction with the other Network Elements. Impacts on telecom and O&M Step2
specifications are also given in this section. The validation strategy is presented as well as the impacts on
GCD, methods and engineering rules.
The section 4 recaps the impacts for each subsystem.
The section 5 addresses the performance and system dimensioning concerns.
The section 6 identifies and describes the open points that have been raised in the various reviews.
The section 7 is a sum up of the system impacts.
The section 8 contains the glossary of the present document.
Annex A contains a description of the 3GPP standard features that meet the functional requirements
expressed in section 2.
1.3 Definitions and pre-requisite
1.3.1 What is the EDA mode?
The Extended Dynamic Allocation (EDA) uplink RLC data transfer mode is an extension of the Dynamic
Allocation (DA) uplink RLC data transfer mode.
This part aims to give an overall view of the EDA mode and of its associated issues without special focus on
B10 context. The reading of this part is necessary to fully understand the solution proposed to support this
feature this time in the B10 context.
Reminder: fixed and exclusive allocation modes are not supported in Alcatel BSS.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 10/77
1.3.1.1 Reminder of the principle of the DA mode

When an uplink TBF is established for a mobile station, the network provides to the mobile station the list of
the uplink PDCHs assigned for that TBF and the list of the USF identifiers of this TBF. One unique USF is
assigned per TBF per assigned PDCH.
During the lifetime of the TBF, the mobile listens to the downlink PDCHs corresponding to its uplink assigned
PDCHs. On one assigned PDCH, whenever the mobile station detects its USF (note that we consider here
that there is only one TBF established per mobile station per direction, i.e. that there is no multiple TBF
feature), this means that it is allowed to transmit on the same uplink PDCH in the next Block Period. The
following figure illustrates the principle of the DA mode in case of an uplink TBF assigned on two PDCHs:
The figure represents successive block periods truncated each time to the two
assigned time-slots of the first TDMA frame (downlink and uplink) (reminder: there
is a shifting of 3 timeslots between DL and UL frames):
DL
UL
DL
UL
DL
UL
DL
UL
LEGEND:
: radio block
: 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 corresponding USF of the
mobile station
Figure 1: Example of DA operation in case of 2 uplink timeslots assigned
In this way, the network can perform the uplink scheduling (i.e. the sharing of the radio resources between
the uplink TBFs).
Note that each PDCH can be allocated independently (one-to-one relation).

1.3.1.2 Type 1 mobile stations and limits of the DA mode
All (E)GPRS mobile stations available today on the market are type 1 mobile stations, i.e. that they cannot
transmit and receive at the same time.
For a type 1 mobile station, the number of possible assignment configurations is given by its multislot class
and by the constraints of measurements relative to that multislot class (see [4] for more details). Indeed, the
mobile station shall perform neighbour cell measurements during any unused PDCH or group of unused
PDCHs where the MS's Measurement Capabilities indicate that the mobile station is capable of making a
neighbour cell measurement. Moreover, the mobile station need a minimum non-null time to switch from
reception to transmission and inversely.
Thus, the network shall ensure when assigning the PDCHs that there are sufficient gaps to allow the
necessary number of measurements based upon the MS's Measurement Capabilities.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 11/77
The figure represents the constraints of measurements per TDMA frame (Ttb and Tra
gaps) in case of a multi-slot class 12 in 3+2 radio assignment configuration (i.e. 3

downlink timeslots and 2 uplink timeslots assigned):
Ttb = 1 Tra = 2
DL
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
UL
0 1 2 3 4 5 6 7 0 1 2 3 4
Figure 2: Constraints of measurements for multi-slot class 12 in 3+2 configuration
Because of these constraints and because the mobile station shall listen to the downlink PDCHs
corresponding to its uplink PDCHs assigned for USF monitoring, the number of uplink PDCHs assignable is
strongly limited. In the example above, we can see that we cannot support more than two uplink timeslots
otherwise the constraints of measurements (here Ttb and Tra gaps) are no more respected.
1.3.1.3 Principle / basic rules of the EDA mode
The EDA mode is characterised by the mobile station detecting an assigned USF value for any assigned
uplink PDCH allowing the mobile station to transmit on that PDCH and all higher numbered assigned PDCHs
(one-to-several relation). Thus, the mobile station does not need to monitor all the downlink PDCH
corresponding to its uplink PDCH allocated, what allows the type 1 mobile station to support configurations
with more uplink timeslots (and thus with less downlink timeslots).
According to the 44.060 Rel6: The mobile station shall ignore the USF on those higher numbered PDCHs
during the block period where the assigned USF value is detected and during the block period(s) in which
the mobile station has been granted permission to transmit.
The following figure illustrates the principle of the EDA mode in case of an uplink TBF assigned on four
PDCHs:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 12/77
The figure represents successive block periods truncated each time to the
four assigned time-slots of the first TDMA frame (downlink and uplink):
The MS detects its USF on the first

downlink time-slot.
The UL allocation is cut off for (at

least) one block period for
decreasing the number of time-slots
allocated per block period (from
four to three in this case).
The UL allocation is reduced to one

time-slot per block period.
Shifting USF to the left increases

UL allocation.
Note: in case a downlink TBF exists, it can be assigned only the first timeslot.
LEGEND:
: radio block
: uplink radio block where the mobile station is transmitting
: downlink radio block where the network sets the USF of the mobile station
Figure 3: Example of EDA operation in case of multi-slot class 12 in 1+4 radio configuration
In this scenario, the constraints of measurements are fulfilled thanks to the EDA mode:
The figure represents the constraints of measurements (Tta and Trb time lags) in case of a
multi-slot class 12 in 1+4 radio assignment configuration (i.e. 1 downlink timeslots and 4
uplink timeslots assigned):
Tta = 2 Trb = 1
DL
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
UL
6 7 0 1 2 3 4 5 6 7 0 1 2 3 4
Figure 4: Constraints of measurements for multi-slot class 12 in 1+4 configuration

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 13/77
1.3.1.4 Main consequences of the EDA mode

1.3.1.4.1 New radio configurations supported
Taking into account the considerations above, the EDA mode allows the support of radio configurations with
more uplink timeslots.
For example, the following table gives the new configurations (four new optimal ones and two new sub-
optimal ones) with consecutive time-slots in an RX (Reception) or TX (Transmission) window that can be
supported thanks to the EDA mode for multi-slot classes 1-12:
Supported GPRS packet connection
Multi Rx Tx
Sum configurations
slot [1] [1] Tta Ttb Tra Trb
[4]
class [2] [3]
Sub-optimal Optimal
(1+1)
1 1 1 2 3 2 4 2 No
2 2 1 3 3 2 3 1 (1+1) (2+1)
(2+1),
3 2 2 3 3 2 3 1 (1+1)
w/ EDA: (1+2)
4 3 1 4 3 1 3 1 (1+1), (2+1) (3+1)
5 2 2 4 3 1 3 1 (1+1), (1+2), (2+1) (2+2)
6 3 2 4 3 1 3 1 (1+1), (1+2), (2+1) (2+2), (3+1)
(3+1), (2+2)
7 3 3 4 3 1 3 1 (1+1), (2+1), (1+2)
[5]
2
8 4 1 5 3 1 1 (1+1), (2+1), (3+1) (4+1)
(1+1), (2+1), (3+1),

9 3 2 5 3 1 2 1 (3+2)
(1+2), (2+2)
10 (1+1), (2+1), (3+1),

4 2 5 3 1 2 1 (3+2), (4+1)
(2+2), (1+2)
(1+1), (2+2), (2+1),

(3+2), (4+1)
(3+1), (1+2)
11 4 3 5 3 1 2 1
w/ EDA: (2+3)
w/ EDA: (1+3)C
(1+1), (2+2), (2+1),

(3+2), (4+1)
(3+1), (1+2)
12 4 4 5 2 1 2 1
w/ EDA: (2+3), (1+4)
w/ EDA: (1+3)C
Table 1: New possible GPRS packet connection configurations supported with consecutive timeslots
for multi-slot classes 1-12
Notes:
1. For type 1 MS, RX or TX window shall not be spread over 2 different TDMA frames and transmit TS do not occur between
receive TS within a TDMA frame.
2. RX: Maximum number of received timeslots that the MS can use per TDMA frame.
3. TX: Maximum number of transmitted timeslots that the MS can use per TDMA frame.
4. Sum: Maximum number of transmit and receive timeslot (without Mx) per TDMA frame
5. In the class 7, the 1+3 configuration cannot be supported (shifted-USF operation would have been necessary) because of the
requirement to have the USF transmitted on the DL time slot with the same TN than the 1st allocated UL TS.
=> with the Tra and Ttb constraints there is not enough turnaround time between the last uplink TS and the downlink TS which
should contain the USF in the next frame (TS#0 in our example):

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 14/77
x 4 = 1 RB Expected USF
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
DL
Ttb Tra
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
UL
x 4 = 1 RB
Note: shifted-USF operations would have allowed the network to set the USF of the first PDCH on
the second PDCH so that the mobile station can transit on the three assigned uplink timeslots.
However, shifted-USF operation are not supported for multislot class 7 (see 3GPP 45.002).
Figure 5: illustration of needs on shifted-USF operations.

1.3.1.4.2 Additional constraints at MAC level
On the other side, due to the rules of EDA operation, strong constraints at scheduling level appear
(compared to the DA mode), especially the two following ones:
- In a given BP, radio blocks can be dynamically allocated only from the right to the left (i.e. from the
highest PDCH assigned),
- In some radio configurations, the reduction of the number of allocated PDCHs (except to 0 PDCH)
from one block period to the following one is not possible.
These two strong constraints make the flexibility of EDA operations reduced. The multiplexing on the same
time-slots of several mobile stations, some using EDA and some not, may lead to complex scheduling
problems especially in terms of fairness and in terms of resource wasting if the resource assignment and the
radio resource scheduling are not complementary. The following example illustrates this possible problem:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 15/77
Let us assume two uplink TBFs:

- The blue one assigned on the four timeslots available (EDA mode required),
- The yellow one assigned on the fourth timeslot (DA mode).
The following scheme represents an example of scheduling cycle considering that the TBFs must be
served according to their number of timeslots assigned. The figure represents successive block periods
truncated each time to the four time-slots of the first TDMA frame (downlink and uplink):
In BPs n+1 and n+3, the allocation of the

BP n UL
blue TBF cannot be reduced due to the Scheduling
EDA constraints (allocation from the right pattern/cycle
to the left). BP n+1 UL
Indeed, in BPs n and n+2, the mobile
station can listen only to the first downlink BP n+2 UL
PDCH since it has to transmit on four
timeslots in BPs n and n+2 (see figures 3 BP n+3 UL
and 4).
Thus radio resources are wasted Etc
LEGEND:
: radio block assigned but not allocated, i.e. wasted
: uplink radio block where the blue mobile station is transmitting
: uplink radio block where the yellow mobile station is transmitting
Figure 6: illustration of possible radio resource wasting during EDA operations in case assignment
and scheduling are not complementary
1.3.1.4.3 Output power reduction issues
The first mobile stations supporting the feature on the market may be unable to simultaneously provide the
maximum output power and the maximum number of TS assigned principally because of possible
overheating of the transmitter circuitry. This restriction might make the feature less efficient than expected
(see 9.6 for more information).
1.3.1.5 Paradox of the EDA / When using EDA?
The EDA mode is useful to increase the uplink bandwidth of a mobile station through the allocation of
several time-slots. However, in scenarios when multiplexing of several TBF has to be performed:
- Transmission slots will be shared among several users, and the bandwidth per user will be reduced.
- There are some significant risks to be unable to allocate the total available radio bandwidth (due to
the scheduling constraints of the TBF in EDA mode),
- The allocated bandwidth might be used with lower efficiency because of output power reduction
(based on the number of timeslots assigned).
Taking into account these considerations, there is a high interest in terms of performances and in terms of
system complexity (and thus in terms of costs) to have simplified EDA operation, i.e. to allow EDA operation
only if the TBF is alone on its PDCHs and if the transfer is uplink-biased. In this way, the MAC scheduling
should be less complex, but to the detriment of the assignment processes.
1.3.1.6 Availability of the EDA mode
According to the 3GPP standard:
- The DA mode shall be supported in all mobile stations that support GPRS,
- The support of EDA is optional for the network,

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 16/77
- R97-Rel-5 mobile stations: the support of EDA is optional (except for multislot classes 22, 24, 25
and 27 for which the support of EDA is mandatory but this case is not applicable for B10).
- Rel-6 mobile stations: same as for R97-Rel-5 except that the support of EDA is mandatory for
multislot class type 1 mobile stations that can transmit on three or more timeslots (either PDCH or
TCH).
Note also that DTM multislot class 11 (that requires EDA to be fully supported) has been introduced in Rel-4.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 17/77
2 HIGH-LEVEL DESCRIPTION
2.1 Functional Requirements
2.1.1 EDA, an attractive feature for increasing the uplink throughputs
Since the uplink-biased transfers (e.g. MMS services) represent today a significant part of the overall
number of PS (Packet Switched) transfers, there is a high interest for Alcatel to implement features that can
offer better throughputs in uplink (the support of 8PSK and IR in uplink was a new step in B9).
All mobile stations available on the market today are type 1 mobile stations. They cannot transmit and
receive at the same time (1-12 and 19-45 multislot classes). In B9, those mobile stations are limited to two
transmission timeslots through the DA (E)GPRS MAC mode.
The EDA mode is an extension of this DA mode enabling transmission on more than two time-slots for the
type 1 mobile stations (supporting the feature), with the benefit of keeping the basic principle of the dynamic
allocation via USF. Since the fixed allocation has been removed from the standards, the EDA becomes the
sole MAC mode enabling such function. Moreover, EDA is required to fully support DTM multislot class 11.
Thus, the interest of EDA is obvious and looks as an attractive feature for the operators. This is all the more
relevant that the specification of this feature has been recently simplified in the 3GPP standard to allow
mobile manufacturers to implement rather quickly mobiles supporting EDA.
Some mobile manufacturers have announced quick support of EDA.
2.1.2 EDA, the restrictions
However, there are some restrictions about this feature:
- The first mobile stations supporting the feature may be unable to simultaneously provide the
maximum output power and the maximum number of TS assigned principally because of possible
overheating of the transmitter circuitry.
- There are new strong constraints (compared to the DA) at MAC level for mobile stations using the
EDA mode making the feature principally useful only whenever the mobile station is alone on its
resources.
- There are some risks of interoperability problems due to the fact that some remaining ambiguities in
the 3GPP standard (in Rel 6) have been only just recently clarified whereas the feature is initially an
R97 feature.
Thus, the challenge is to propose a solution that is a trade-off between complexity (and thus costs) and
performances.
2.2 Overall description of the proposed solutions

The solution proposed is to support the EDA mode in the network for multi-slot classes 1-12 (i.e. without
shifted-USF operations) in case of Packet Transfer Mode and in case of Dual Transfer Mode (DTM multislot
class 11) so that the following new radio configurations are supported:
Supported GPRS packet connection
Multi
configurations
slot
class
Sub-optimal Optimal
3 (1+1) (2+1),

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 18/77
1
w/ EDA: (1+2)
(1+1), (2+2), (2+1),

(3+1), (1+2) (3+2), (4+1)
11
2 w/ EDA: (2+3)
w/ EDA: (1+3), (1+2)/1H
(3+2)
DTM
(2+2)
11
w/ EDA: (2+3)
(1+1), (2+2), (2+1),

(3+1), (1+2) (3+2), (4+1)
12
w/ EDA: (1+3), (1+2)/2H, w/ EDA: (2+3), (1+4)
(1+2)/1H, (1+3)/1H (2x)
Table 2: New GPRS packet connection configurations supported
The EDA mode will be used only for configurations that require the EDA mode to be supported and without
PDCH allocation reduction capabilities (see section 9.5.1.4).
Due to the possible power reduction issues, due to the reduced flexibility of EDA operations (that may lead
to unfairness and radio resource wasting issues), these radio configurations will be used only if the uplink
TBF (in EDA mode) can be alone on its assigned uplink timeslots and not in front of downlink timeslots
supporting the PACCH channel of at least one downlink TBF not belonging to the same mobile station. Since
only USF granularity-1 is supported in Alcatel BSS (USF granularity-4 is not supported), the solution
proposed is compatible only with USF granularity-1.
The EDA mode will not be supported in case of RT TBF or RT PFC.
The EDA mode will be supported in Evolium cells and not supported in extended cells.
The activation of the feature and thus the availability of these new configurations for the mobile stations
supporting the feature will be optional and accessible to the operator.
To limit the problems of interoperability, the feature activation will be limited to mobile stations onward a
given 3GPP release, and the simultaneous usage of DTM and EDA will be desactivable.
The management of output power reduction will not be managed since the link adaptation can react to radio
quality degradation but this might be to the possible detriment of Circuit Switch transmission (see sections
2.8.5.5 and 9.6 for more details).
2.3 Compliance to the Marketing Requirements

This section shall identify the compliance of each feature item to one or more marketing requirements. In
case a feature item, as described in the previous section, bears some limitations/restrictions, they shall
clearly be stated in the Comments part.
Feature Item Compliance Comments
1
Note that this configuration is supported whereas it is foreseen that few multi-slot class 3 mobile stations will support
EDA mode. Nevertheless the additional complexity introduced to manage this new configuration is very low.
2
/nH means that the configurations has n holes in the assignment.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 19/77
2.4 Compliance to 3GPP standard

The proposed solution is compliant with Rel-6 3GPP standard that unofficially acts as implementation and
test reference for mobile and infrastructure manufacturers for EDA. Indeed, the feature has been partially
clarified in R99, Rel-4 and Rel-5 and completely clarified in Rel-6.
The proposed solution is inline with the standard but does not fully exploit the capabilities of the EDA mode
as defined in Rel-6. Note the three following main limitations:
- The solution proposed does not fully exploit the EDA capabilities in case of polling scenarios in order
to simplify the implementation (actually so that the MAC layer need not to consider the radio
configuration capabilities of the mobile station) (see 3.1.2.3.2.2.1 for more information).
- Recent clarifications (TSG GERAN#26) that improve EDA operations through PDCH allocation
reduction capabilities (see 9.5 for more details) are not considered. This improvement is optional
and the fact to not implement it cannot lead to inter-operability issues. The drawback leads only to a
lower flexibility of the feature. This improvement is not implemented to simplify the implementation
and because it is expected that the first generation of mobile stations supporting EDA will not
support this option.
- The standard allows recovering some information about the possible power reduction applied by
some mobile stations in EDA mode (especially from Rel-5, see 9.6 for more information). This
information is not used in the solution proposed.
2.5 Working Assumptions

This study is valid only in the following context:
- Only multislot classes 1-12 are supported. That means especially that shifted-USF operation is not
necessary.
- EDA operations are supported in case of DTM multislot class 11.
- EDA operations are not supported in case of RT TBF and RT PFC3.
- RT TBF and RT PFC are not supported in case of DTM operations.
- Reallocations of DTM calls are allowed only if TCH remains at the same position (in other terms only
the TBF can be re-allocated).
- The faulty GPRS terminals are still managed. The solution retained is equivalent to the B9 MAC
solution additionally with direct mapping between dummy downlink TBF and uplink TBF associated
(see ref [5] for more information).
- The majority of the traffics experienced by a mobile station are mono-directional (i.e. either downlink-
biased or uplink-biased).
2.6 Dependencies
The Extended Dynamic Allocation feature (including support of DTM multislot class 11):
requires
3
Such operations are not supported to simplify the solution proposed for the support of EDA (especially at radio resource
management level). The two main issues are the fact that a TBF in EDA mode may be highly jeopardized by another
uplink TBF (due to possible radio resource wasting when using EDA) and the fact that the re-configuration of a RT TBF is
currently not supported (but would be necessary).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 20/77
Feature Dependency
Dual Transfer Mode Required to support DTM multislot class 11 (Rel-4-onwards).
is enhanced by
Feature Dependency
is incompatible with
Feature Dependency
will be enhanced by the following future evolutions
Feature Dependency
Management of output power A priori low

reduction (see section 9.6)
PDCH allocation reduction (see Medium

section 9.5)
Scheduling on lowest PDCH in Mobile stations supporting EDA and IEUTM could be scheduled
case of Improved Extended on their lowest assigned PDCH during extended phases,
Uplink TBF Mode (IEUTM) leading to more flexibility and efficiency during extended phases
(see section 3.1.2.3.2.2.2). This is not done to simplify the
implementation since it is not foreseen that all EDA-capable
mobile stations will support IEUTM.
Multislot classes 30-33 (see More configurations with EDA could be supported (e.g. 2+4).
reference [5])
decreases the interest of
Feature Dependency
2.7 HW Coverage
This section defines the HW coverage of the feature(s). A synthetic and exhaustive table shall be provided
where the different HW generation of each subsystem are listed.
The HW coverage of the feature(s) shall be given on a per implementation step basis where needed.
System:
Y/N
GSM 900
DCS 1800 / DCS1900 Y/N
GSM 850 Y/N

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 21/77
Network element:
In the following tables, indicate :
Xsw if feature supported by the NE with software impact,
Xhw if feature supported by the NE with hardware impact
Xsw+hw if feature supported by the NE with software and hardware impact.
X: The feature is supported on the NE without hardware or software impacts.
-: The feature is not supported by the NE or the NE is not concerned by the feature
Impact
BTS Generation: BTS G2 with DRFU -
(frozen at B7.2 level)
BTS Mk2 with DRFU -
(frozen at B7.2 level)
A9100 (Evolium standard) -
A9110 (M4M) -
A9110-E (M5M) -
BSC Generation: BSC G2 -
MFS: MFS Xsw
Transmission: Alcatel TSC -
Transcoder: TRAU G2 with DT16 -

TRAU G2 with MT120
TRAU G2.5 (with MT120) -
MSC: MSC -
SGSN: SGSN -
Data IWF: Data IWF -
HLR: HLR -
O&M: OMC-R Xsw

POLO -
OEF -
LASER -
MPM/NPO Xsw
MSTS: MSTS Xsw
2.8 Decision criteria

In this section, the criteria relevant for deciding whether or not to implement the feature(s) shall be provided
(except the cost since it will be derived from the SFD).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 22/77
2.8.1 Standardisation
See sections 2.4, 2.8.5.1, 2.8.5.2 and 9.2.
2.8.2 Competition
The two following points are clear indications that it is very likely that Alcatel competitors will also implement
EDA in the coming years:
- The specification of this feature has been recently simplified in the 3GPP standard to allow mobile
manufacturers to implement rather quickly mobiles supporting EDA. Numerous companies have
contributed to this work. Tests for mobile stations have been recently approved.
- Some mobile manufacturers have clearly announced quick support of EDA (among them Nokia and
Philips).
2.8.3 Customer
There is today a clear consensus for operators that EDA can bring significant improvements of uplink
(E)GPRS throughputs. However, they are maybe not completely aware today of the constraints linked to the
usage of the EDA mode. Among Alcatel customers, France Telecom and T-mobile have shown high interest
for EDA.
2.8.4 Gains
2.8.4.1 Telecom gains
The gains shown in this section compare what can be achieved if the feature(s) described in the present
SFD are implemented to the B10 Alcatel BSS release performance.
Without the With the Comments

feature feature
Ping performances (see No impact (provided that the

section 9.7 for more N_UL_BIAS_FOR_EDA
information) parameter is correctly tuned).
WAP access duration No impact.
WAP page download duration No impact.

Web page download duration
Throughput improvement for large
page sizes4.
DL FTP throughput No impact.
UL FTP throughput Significant throughput

improvement5 (directly linked to
the additional number of uplink
timeslots) for large transfer sizes6.
Cell re-selection duration No impact. However, the

(intra-RA / inter-RA if any preparation phase can be slightly
4
Due to the N_UL_BIAS_FOR_EDA mechanism, EDA cannot be used from the transfer start. Thus, the larger a transfer
is in terms of data size, the higher the throughput gain is.
5
Gain will be observed only if conditions presented in section 3.1.1.3.1 can be reached.
6
Due to the N_UL_BIAS_FOR_EDA mechanism, EDA cannot be used from the transfer start. Thus, the larger a transfer
is in terms of data size, the higher the throughput gain is.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 23/77
Without the With the Comments

feature feature
difference, 2G-2G or 2G-3G) slown down since less downlink
timeslots are available in case of
uplink-biased configurations to
transmit the NACC/PSI
messages.
2.8.4.2 Operational gains
None.
2.8.5 Risks
2.8.5.1 Backward compatibilities / R97 mobile stations
Some recent corrections concerning adjacent cell measurements have been made in the standard from
Release 99, in particular for supporting operation with four TX slots with multi-slot class 12 mobile stations.
As EDA is a R97 feature, there could be some backward compatibility problems with R97 mobile stations
supporting EDA.
However, the number of cases should be very low.

2.8.5.2 Remaining ambiguities of the 3GPP standard before Rel-6
EDA operation has been partially clarified from R99 to Rel-5 and has been completely clarified in Rel-6
(clarification of the monitoring of the downlink PDCHs): the CR GP-040701 approved at GERAN 19 clarifies
that the assignment based approach is not applicable to USF monitoring, and that the general rule specified
in 44.060, that the mobile needs to support USF monitoring on all assigned uplink PDCHs, does also apply
in case of EDA. This CR was introduced for Release 6 only.
For earlier releases (R99, Rel-4 and Rel-5), it is not clear in the current state of the specifications which
behaviour is required for the mobile. This could lead to interoperability issues.
That means that some un-correctly implemented mobile stations would support only the EDA mode on a
pure assignment basis that could lead to un-capability for such mobile to monitor some PDCH and thus their
USF. To note that mobile stations that support the Rel-6 EDA mode should support also the EDA mode on a
pure assignment basis.
However, it is assumed that EDA implementations in the mobile stations are compliant to Rel-6 EDA
operations (see section 2.4).
2.8.5.3 Sub-optimal behaviour in case of transmission resource congestion
In the solution proposed, no dedicated consideration about transmission resource issues is perfomed when
triggering the EDA mode for an uplink TBF. That means that the performances of a TBF in EDA mode in
case of transmission resource congestion may be significantly impacted and even worse than the
performances of DA mode in few scenarios. These degradations may be all the more significant that the
PDCH allocation reduction feature is not supported.
2.8.5.4 BSIC decoding (for information)
According to the 45.002, normal BSIC decoding is not possible for 1+4 configurations.
Indeed, the mobile station has to regularly (when FN [mod 26] = 25, i.e. in the search frames) open a window
for BSIC decoding (whose size is around 9 bursts). The standard allows the mobile station to skip reception
or transmission burst (see reference 45.008 for more details) so that the mobile station can correctly perform
this BSIC decoding:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 24/77
TDMA frame Search frame

DL 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1
P P
UL 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6
P
BSIC window
Tta = 2 (measure + ready Tx) Used timeslot

P PACCH (used) timeslot
Timeslot possibly discarded
Figure 7: illustration of the blocks possibly discarding for BSIC decoding.
In case of RLC acknowledged mode, this could lead to a decrease of the maximum reachable throughput. In
case of RLC unacknowledged mode, the impacts may be significantly higher (due to a high corruption level
of higher layer frames) if the mobile station does not delay the transmission of the whole burst (see
reference 45.008 for more details).
The discarding probability depends on a lot of parameters (network profile, etc) and is also highly
dependent on the implementation in mobile stations (standards lets some flexibility for implementation).Thus,
downlink and uplink frames may be lost. However, the probability should be low enough to not be taken into
account.
2.8.5.5 Possible slight increase of call drop in case of EDA operations
2.8.5.5.1 PTM operations
Due to possible output power reduction when switching to the EDA mode, a slight increase of PS dropping
rate might be observed. In the same way, the distribution of the coding schemes used might be impacted.
2.8.5.5.2 DTM operations
When switching from the 3+2 configuration to the 2+3 configuration in case of DTM multislot class 11, power
reduction might be applied also on the CS transmission. For more information, see section 9.6.1.4. That
means that a slight increase of the CS dropping rate might also be observed for DTM multislot class 11
mobile stations.
2.8.5.6 Possible uncorrect behaviour of the uplink EGPRS link adaptation
Due to the averaging performed in RLC on several measurements received in the same block period, the
performances of the link adaptation algorithm might be impacted.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 25/77
3 SYSTEM IMPACTS
3.1 Telecom
3.1.1 Functional-level description
This section describes for each feature the use scenarios including both the nominal case and the error
cases. This is where diagrams should appear showing the interactions within the Alcatel BSS (e.g. between
the various layers/modules within the MFS) and with the other Network Elements / MS for realising the
features. If the SFD should contain several features, each feature should be described when possible in a
dedicated section.
3.1.1.1 Activation of the EDA feature
The EDA feature is optional for the network.
The feature is activable through the EN_EDA O&M parameter (cell level):
- EDA not activated7,
- EDA activated.
When activated, EDA can be allowed at the following mobile station levels through the
EDA_MS_ACTIVATION_LEVEL O&M parameter (BSS level):
- For all mobile stations (supporting the feature)8,
- For R99-onwards mobile stations (supporting the feature),
- For Rel-4-onwards mobile stations (supporting the feature)9.
This MS activation level is an artificial mean to limit the inter-operability risks presented in sections 2.8.5.1
and 2.8.5.2. Indeed, it is assumed that: the more recent a mobile station is, the more chances there are that
it has correct implementation of EDA. Further releases (Rel-5, Rel-6 and Rel-7) have not been considered
since there is unfortunately no safe mean to detect if a mobile station is compliant with them (especially due
to early implementations)10.
EDA can be forbidden in case of DTM operations through the ALLOW_DTM_EDA_COMBINATION O&M
parameter (BSS level):
- 0: simultaneous usage of DTM and EDA is not allowed,
- 1: simultaneous usage of DTM and EDA is allowed.
In case of DTM multislot class 11, that means that the 2+3 configuration can be forbidden.
7
Note that the possibility to not activate the feature is of usual practice to be able to migrate from a release to the other
at same functional level. Note that the EDA feature is optional in B10 release from a commercial point of view.
8
Remind that EDA has been introduced in R97.
9
It is assumed that a mobile station supporting the GERAN Feature Package 1 is at least Rel-4-compliant.
10
Further step would have been to detect the mobile station behaviour at MAC level to assess the level of EDA
implementation. However, it has been considered as tricky.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 26/77
3.1.1.2 New configurations supported (in EDA mode)

The activation of the feature makes available for multislot class 1-12 mobiles stations supporting EDA (and
for DTM multislot class 11 mobile stations) and compliant with the MS activation level (see 3.1.1.1) the
radio configurations requiring EDA (to be supported) according to their multi-slot class.
All optimal configurations requiring the EDA mode are supported.
Moreover, to reach better usage of radio resources, some sub-optimal configurations in EDA mode need
also to be supported. Among them, some configurations with hole in the assignment11. However, so as to
limit the risks of interoperability (especially at MAC level), only the sub-optimal configurations with first
common timeslots are supported.
Only the configurations that require the EDA mode to be supported are supported with the EDA mode. Other
configurations are supported with the DA mode. That implies for example that: when a sub-optimal
configuration can be supported in both modes, the DA mode is favoured (e.g. the symmetric 2+2
configuration may be seen as a sub-optimal case of 3+2 or 2+3 optimal configurations in case of multislot
class 11 or 12).
The PACCH shall be set on the first timeslot (that is always common to downlink and uplink assignments
due to the restrictions chosen). As a consequence, the PACCH TSs of a DL TBF and of its concurrent UL
TBF handled in EDA will always be the same.
The list of the optimal and sub-optimal configurations to be supported in the EDA mode is defined below for
each multislot class. On the figure, Rx means Reception (i.e. downlink), Tx means Transmission (i.e. uplink),
Mx means Measurements (for more information, see 3GPP 45.002). The PDCH supporting the PACCH is in
bold underlined.
3.1.1.2.1 Multi-slot class 3
3.1.1.2.1.1 Optimal configuration(s)
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Ttb = 2 Tra = 3
0 1 2 3 4 5 6 7
UL Tx Tx
Figure 8: multi-slot class 3 / 1+2 optimal configuration
3.1.1.2.1.2 Sub-optimal configuration(s)
No sub-optimal configuration.
11
In this SFD, it is not proposed to extend the support of the configurations with hole in the assignment to the DA
configurations so as to limit the additional complexity and possible drawbacks at implementation level. The management
of such configurations would have improved the radio management performances especially in case some resources
possibly assignable to the PS domain would have surrounded a TCH. To note that such configurations may already
happen today as a result of the assignment of a DTM configuration.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 27/77

0 1 2 3 4 5 6 7 0 1 2
DL Rx Rx Mx
Ttb = 1 Tra = 2
0 1 2 3 4 5 6 7
UL Tx Tx Tx
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Ttb = 1 Tra = 2
0 1 2 3 4 5 6 7
UL Tx Tx Tx
Figure 10: multi-slot class 11 / 1+3 sub-optimal configuration
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Ttb = 1 Tra = 2
0 1 2 3 4 5 6 7
UL Tx Tx
Figure 11: multi-slot class 11 / 1+2 sub-optimal configuration

Same optimal configurations as for multi-slot class 11 are supported plus the following ones:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 28/77
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Tta = 2 Trb = 1
0 1 2 3 4 5 6 7
UL Tx Tx Tx Tx
Same sub-optimal configurations as for multislot class 11 are supported plus the following ones:
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Tta = 2 Trb = 1
0 1 2 3 4 5 6 7
UL Tx Tx Tx
Figure 13: multislot class 12 / 1+3 sub-optimal configuration
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Tta = 2 Trb = 1
0 1 2 3 4 5 6 7
UL Tx Tx Tx
Figure 14: multislot class 12 / 1+3 bis sub-optimal configuration
0 1 2 3 4 5 6 7 0 1 2
DL Rx Mx
Tta = 2 Trb = 1
0 1 2 3 4 5 6 7
UL Tx Tx
Figure 15: multislot class 12 / 1+2 sub-optimal configuration

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 29/77
3.1.1.2.4 DTM multi-slot class 11

0 1 2 3 4 5 6 7 0 1 2
DL Rx C Mx
S
Ttb = 1 Tra = 2
0 1 2 3 4 5 6 7
UL Tx C Tx
S
Figure 16: DTM multislot class 11 optimal configuration
Note that the configuration with the TCH on the left is not allowed (see reference [1] for more information).
No sub-optimal configuration.
3.1.1.3 EDA operations
3.1.1.3.1 Non-multiplexed-EDA strategy
Due to the constraints brought by the EDA mode (that are summarized in section 1.3.1.5), a dedicated
assignment strategy will apply in PTM and in DTM modes to the configurations requiring the EDA mode:
For a mobile station allowed to use the EDA mode, the configurations requiring the EDA mode will be used
only if the bias of the transfer is uplink (in almost all cases) and if the uplink TBF (in EDA mode) can be
assigned:
- Alone on its uplink timeslots,
- And not in front of downlink timeslots supporting the PACCH channel of at least one downlink TBF
(or downlink RT PFC) not belonging to the same mobile station.
Let us call non-multiplexed-EDA this strategy.
The following figure illustrates possible results of the non-multiplexed-EDA strategy in three different
scenarios (4, 5 and 7 timeslots available for PS respectively) with two EGPRS multi-slot class 12 mobile
stations supporting EDA, the mobile station A performing a downlink transfer and the mobile station B
performing an uplink transfer:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 30/77
P P P
P P P
DL DL DL
0 1 2 3 0 1 2 3 4 0 1 2 3 4 5 6
P P P P P P
UL UL UL
0 1 2 3 0 1 2 3 4 0 1 2 3 4 5 6
: timeslot assigned to the EGPRS mobile station A
: timeslot assigned to the EGPRS mobile station B
P : PACCH timeslot
Figure 17: illustration I of assignment strategy for TBF in EDA mode
And the same scenario this time with two DTM multislot class 11 mobile stations:
NOT ALLOWED
ALLOWED CS P
P CS CS P P CS
DL DL
0 1 2 3 4 0 1 2 3 4
CS P
P CS CS P P CS
UL UL
0 1 2 3 4 0 1 2 3 4
: timeslot assigned to the EGPRS mobile station A
P : PACCH timeslot
Figure 18: illustration II of assignment strategy for TBF in EDA mode
To be inline with B9 strategy in terms of GPRS/EGPRS multiplexing, an uplink GPRS TBF in EDA mode
should not be assigned in front of downlink timeslots supporting at least one downlink EGPRS TBF.
Nevetheless, this will not be done since the probability of such scenario is very low. Indeed:
- In case both GPRS and EGPRS are allowed on a TRX, a GPRS- and EGPRS-capable mobile
station will be preferentially assigned in EGPRS mode by RRM,
- An operator cannot restrict a GPRS- and EGPRS-capable mobile station to use only GPRS,
- It is very likely that an EDA-capable mobile station will be also EGPRS-capable (even if the EDA
capabilities can be indicated distinctely in both GPRS and EGPRS modes).
3.1.1.3.2 Making
EDA operations are seen as nice-to-have operations, i.e. that the EDA mode has lower priority at
assignment level than the DA mode so that the current (B9) assignment algorithms (valid for TBFs in DA
mode) are not brought into questions due to the introduction of the EDA feature.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 31/77
That means that the non-multiplexed-EDA strategy (see section 3.1.1.3.1) is tried to be achieved by the
radio resource management procedure only when considering a configuration requiring the EDA mode but
not when considering a configuration in DA mode (actually a TBF in EDA mode is seen by other TBFs as a
TBF in DA mode). Thus, a new uplink TBF (or RT uplink PFC) in DA mode may be assigned on the uplink
timeslots of an uplink TBF in EDA mode. Also, a new downlink TBF (or RT downlink PFC) may be assigned
whereas its PACCH is in front of the uplink timeslots of an uplink TBF in EDA mode. If this scenario
happens, the non-multiplexed-EDA strategy will be further performed through a (T3) reallocation of the TBF
in EDA mode.
The following figure illustrates this strategy in case a EGPRS mobile station B performing a downlink transfer
is arriving while a EGPRS mobile station A is already performing an uplink transfer in 1+4 configuration (5
timeslots available for PS):
Due to the arrival of the mobile station B in 4+1 configuration, the mobile station A is re-assigned
through a T3 reallocation.
P
P P P P
DL DL DL
0 1 2 3 4 0 1 2 3 4 0 1 2 3 4
P
P P P P
UL UL UL
0 1 2 3 4 0 1 2 3 4 0 1 2 3 4
Resulting
: timeslot assigned to the EGPRS mobile station A assignment
scheme
P : PACCH timeslot
Figure 20: illustration I of (re-)assignment strategy for TBF in EDA mode
And the inverse case (i.e. if the mobile station A arrives after the mobile station B):

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 32/77
Due to the arrival of the mobile station A in 1+3 configuration, both mobile stations are successively re-
assigned.
P P P
P P P P
DL DL DL DL
0 1 2 3 4 0 1 2 3 4 0 1 2 3 4 0 1 2 3 4
P P
P P P P P
UL UL UL UL
0 1 2 3 4 0 1 2 3 4 0 1 2 3 4 0 1 2 3 4
Resulting
: timeslot assigned to the EGPRS mobile station A assignment
scheme
P : PACCH timeslot
Figure 21: illustration II of the (re-)assignment strategy for TBF in EDA mode
See section 9.4 for more examples.

3.1.1.3.3 Limits
3.1.1.3.3.1 Scenarios of sub-optimal assignment schemes
This strategy is simple but has drawbacks due to the fact that the non-multiplexed-EDA strategy (see
section 3.1.1.3.1) is tried to be achieved by the radio resource management procedure only when
considering a configuration requiring the EDA mode but not when considering a configuration in DA mode.
The following figures illustrate one example of drawback (different resulting schemes are observed
depending on the arrival order of the TBFs). A EGPRS mobile station B supporting EDA and performing an
uplink transfer is arriving while a EGPRS mobile station A not supporting EDA is already performing an
uplink transfer in 3+2 configuration (5 timeslots available for PS):
P
P P
DL DL
0 1 2 3 4 0 1 2 3 4
P P P
UL UL
0 1 2 3 4 0 1 2 3 4
: timeslot assigned to the EGPRS mobile station (non-

A optimal)
: timeslot assigned to the EGPRS mobile station Resulting
B assignment
P : PACCH timeslot scheme
Figure 22: illustration of the limits of the (re-)assignment strategy for TBF in EDA mode / part I

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 33/77
And the reverse case:

P P P
DL DL
0 1 2 3 4 0 1 2 3 4
P P P
UL UL
0 1 2 3 4 0 1 2 3 4
: timeslot assigned to the EGPRS mobile station (optimal)

A Resulting
: timeslot assigned to the EGPRS mobile station assignment
B scheme
P : PACCH timeslot
Figure 23: illustration of the limits of the (re-)assignment strategy for TBF in EDA mode / part II
These limits have been considered as acceptable (trade-off costs/performances). See section 9.4 for more
examples.
3.1.1.3.3.2 Transition phases
Since the non-multiplexed-EDA strategy (see section 3.1.1.3.1) is tried to be achieved (at the assignment of
EDA configurations and) at the re-assignment of EDA configurations thanks to the T3 reallocation trigger,
some transition states during which the strategy will not be reached are expected. The duration of these
transition phases are expected to be in the order of a few seconds.
According to the section 3.1.1.2, only the configurations that require the EDA mode to be supported are
supported with the EDA mode. However, transition phases during which configurations that would not need
EDA to be supported are supported in EDA mode may happen after a timeslot pre-emption for CS (for
example whenever the third timeslot of a 2+3 configuration is pre-empted by CS, the resulting 2+2
configuration is still supported in EDA mode until the next reallocation).
All these transition phases will be supported.

3.1.1.4 Transmission resource issues
No dedicated consideration about transmission resource issues is perfomed when triggering the EDA mode
for an uplink TBF. That means that the performances of a TBF in EDA mode in case of transmission
resource congestion may be significantly impacted.
3.1.1.5 MAC scheduling
Dedicated scheduling shall apply for TBF in EDA mode. Indeed, the constraints linked to the EDA mode (see
1.3.1.4.2) must be taken into account.
A TBF in EDA mode in Extended Uplink TBF Mode is scheduled only on its highest assigned PDCH12.
When transmited on a TBF in EDA mode, PXCD messages shall be sent on the PACCH (i.e. on the first
PDCH).
12
This strategy is valid because the uplink control timeslot is not used in B10 (see section 3.1.2.1.8).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 34/77
3.1.1.5.1 Optimal scheduling in case of polling

In the block period preceeding the block period in which an answer to a polling request is awaited from a
mobile station, the standard allows the setting of the USF of the mobile station on the PDCH on which the
answer is awaited so that the mobile station can be scheduled on higher PDCHs. The following figure
illustrates this scenario:
The figures represent successive block periods truncated each time to the
four assigned timeslots of the first TDMA frame (downlink and uplink):
The USF is set on the associated

downlink block in the previous block
period.
LEGEND:
: radio block
: downlink radio block when the network sets the USF of the mobile station
: uplink radio block where the mobile station is transmitting (UL TBF)
: downlink radio block sent by the network (DL TBF)
: downlink radio block containing a polling request / uplink radio block

containing the answer to a polling request (DL TBF)
Figure 24: optimal scheduling in case of polling
For that, MAC shall be able to correlate the awaited polling answers of a mobile station to its TBF in EDA
mode (if any), i.e. the polling requests:
- From RLC (e.g. requests for PDAN),
- From RRM (e.g. PCA to confirm DL TBF establishment, Packet Timeslot Reconfigure, re-
assignment or cell change messages).
3.1.1.6 Restrictions to avoid bad ping performances
EDA could have degraded the ping performances (see section 9.7) and other ping-like application
performances. To avoid this critical issue, EDA is allowed for a mobile station supporting the feature (if the
basic conditions are fulfilled and) only if it has a significant amount of uplink data to transmit (characterized in
the proposed solution by a number of consecutive uplink biases observed). In this way, EDA will not be used
in case of typical ping tests.
The interest of EDA will thus be observed only in case of significant uplink transfers (in terms of amount of
data). The following figure shows an illustration of the mechanism:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 35/77
The figure represents the two established TBF of a multislot class 12 rel-4-compliant EDA-capable mobile station
alone on its radio resources and making two-phase access (thus default bias is uplink and the mobile station is
known as supporting EDA from uplink TBF establishment). Let us assume that EDA is allowed for the mobile station
and that the number of consecutive uplink biases for EDA (N_UL_BIAS_FOR_EDA parameter) is set to 3.
Note that the behavior would be the same whatever the fact that T is superior to T_MS_CONTEXT_Lifetime or not.
UL UL DL DL UL UL UL UL UL UL UL UL DL UL
Bias estimations
Radio configuration
3+2 4+1 3+2 1+4 3+2 1+4 4+1 3+2
UL TBF
DL TBF
Time
T
(inter-transfer time)
MS context creation
Figure 25: example of behaviour in case of bias oscillations
3.1.2 Telecom Specification impacts

3.1.2.1 Step 2 RRM PCC
3.1.2.1.1 Detect if the EDA mode is allowed for a mobile station
The EDA mode is allowed for a mobile station in PTM mode if this mobile station supports the EDA mode
and if the feature is activated at BSS level for the release of this mobile station (see 3.1.1.1). For a mobile
station in DTM mode, in addition to these two same conditions, the EDA mode is allowed if combination of
DTM and EDA operations is allowed in the BSS.
3.1.2.1.1.1 Detect if the mobile supports the EDA mode
PCC shall read in case of PTM operations or in case of DTM operations13 the Radio Access Capability to
detect if the mobile station supports the EDA mode. The MS Radio Access Capability of the mobile is
provided to the BSS, either by the mobile in THE PACKET RESOURCE REQUEST message (PTM only), or
by the SGSN in the DL LLC PDUs and in the RA CAPABILITY UPDATE-ACK message.
The support of EDA by a mobile station is indicated through the two following bits in the RAC structure (see
3GPP TS 24.008):
- GPRS Extended Dynamic Allocation Capability,
- EGPRS Extended Dynamic Allocation Capability.

From R97 to Rel-5, the support of EDA is mandatory for mobile stations of multislot classes 22, 24, 25 and
27 (not applicable for B10). The support of EDA for mobile stations of all other multislot classes is optional
and shall be indicated in the mobile stations Radio Access Capability (RAC).
For Rel-6 onwards, the support of EDA is mandatory for mobile stations of multislot classes 22, 24, 25 and
27 (not applicable for B10), and for multislot class type 1 mobile stations that can transmit on three or more
13
Note that the BSS will not use the classmark 3 (see 3GPP TS 24.008 or section 9.1.4) to detect if a mobile supports
the EDA mode, so that the RRM-PCC behaviour is the same in PTM mode and in DTM modes (i.e. by reading of the
RAC), since EDA is not allowed from the TBF start in the proposed solution, and since it would be not so easy to report
this information from the BSC to the MFS.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 36/77
timeslots (either PDCH or TCH)14. The support of Extended Dynamic Allocation for mobile stations of all
other multislot classes is optional and shall be indicated in the mobile stations Radio Access Capability.
PCC shall keep in the MS context the fact that the mobile station supports (or not) EDA.
3.1.2.1.1.2 Detect if the mobile station is compliant with the activation level
PCC shall be able by reading the Radio Access Capability of a mobile station to detect if this mobile station
is at least compliant with the following 3GPP releases: R99 and Rel-4.
PCC shall consider that a mobile station is at least:
- R99-compliant if its Revision Level Indicator bit is set to 1 (see section 9.1.4)
- Rel-4-compliant if it its GERAN Feature Package 1 bit is set to 115.
3.1.2.1.1.3 Activation of the EDA feature

As explained in section 3.1.1.1, the EN_EDA and EDA_MS_ACTIVATION_LEVEL O&M parameters enable
the operator to activate the EDA feature at a given level (more precisely for certain releases of mobiles).
Moreover the ALLOW_DTM_EDA_COMBINATION O&M parameter allows the simultaneous usage of EDA
and DTM. The case when EDA is supported in case of DTM operations and not supported in case of PTM
operations is not managed.
3.1.2.1.2 Indicate to PRH if the mobile station supports EDA
Upon PRH request (i.e. when playing the radio resource (re-)allocation algorithm), PCC should let it know if
the mobile should be considered as supporting EDA or not.
This is done through the positioning of two new parameters (flags): EDA_Allowed_GPRS and
EDA_Allowed_EGPRS.
The value of the EDA_Allowed_GPRS flag (respectively EDA_Allowed_EGPRS) is set to true if:
- EDA is activated in the cell (EN_EDA parameter),
- EDA is supported by the MS in GPRS (respectively EGPRS) (RAC structure),
- EDA is enabled in the BSS for the release of the MS (EDA_MS_ACTIVATION_LEVEL parameter),
- EDA and DTM combination is allowed in the BSS (ALLOW_DTM_EDA_COMBINATION parameter)
if the mobile station is in DTM mode16,
- The N_UL_BIAS_FOR_EDA last observed biases since the transfer start17 are uplink (see Figure 25
for illustration). This guarantees especially that EDA will only be used once the MS bias has a
relevant value at transfer start (the default MS bias value is indeed not always relevant) and that
EDA will not be used in case of ping scenarios (see sections 3.1.1.6 and 9.7).
- There is no RT PFC associated to the MS.
RRM-PCC shall update for a given mobile station the value of the EDA_Allowed_GPRS and
EDA_Allowed_EGPRS flags each time at least one of the conditions mentioned above changes (e.g.
possibly when reading the Radio Access Capability, at each new bias evaluation, if the EN_EDA parameter
14
PCC shall not detect the support of EDA for a Rel-6 multislot class type 1 mobile station through this way since the bits
mentioned above should be relevant also in this case (see 3GPP TS 24.008 or section 9.1.4) and since there is no safe
mean to detect that a mobile station is Rel-6-compliant.
15
It is assumed that a mobile station supporting the GERAN Feature Package 1 is at least Rel-4-compliant.
16
In this scenario, it is assumed that DTM is activated in the cell. Dedicated mode is not considered since EDA cannot
be used from the start of first uplink TBF.
17
A transfer is assumed starting when the first of the two TBFs is established for the given mobile station. The
information that the N_UL_BIAS_FOR_EDA last biases are uplink for a given mobile station shall be for example reset
each time the first of the two TBFs is requested or when a downlink bias is observed.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 37/77
or the EDA_MS_ACTIVATION_LEVEL parameter or the ALLOW_DTM_EDA_COMBINATION parameter is

changed, etc).
Note that it is acceptable not to have an immediate re-evaluation of the state of radio resources in case of
flag state change. The change for a given TBF will be considered thus by RRM-PRH at the next evaluation
of re-configuration (if any).
The two new parameters (EDA_Allowed_GPRS and EDA_Allowed_EGPRS) are needed at CellT/MS
interface in the getCurrentMsInfoForAlgo message.
3.1.2.1.3 Bias
3.1.2.1.3.1 Computation in DTM mode
PCC shall compute also the bias for mobile stations in DTM mode.
3.1.2.1.3.2 Detect a bias change and subscribe to a T3 reallocation
There is no change compared to B9: when PCC (MS module) observes a change of bias, it informs PRH
(CellT) via a T3 reallocation subscription (via the Resource-Request message).
It is to be noted that whenever a reallocation of the TBF takes place, after exchange of
N_Candidate_For_Realloc octets, if there is a TBF established in the direction of the bias, and if T3192 is
not running, PCC also subscribes to a T3 reallocation.
3.1.2.1.4 Polling constraints
As mentioned in section 3.1.1.5.1, MAC shall be able to correlate the awaited polling answers of a mobile
station to its TBF in EDA mode (if any). This is done thanks to a MS context in MAC that keep in memory the
fact that two TBFs (DL and UL) belong to the same mobile station (see section 3.1.2.3.2.2.4).
For that, PCC shall transmit:
- In the PCC-RLC-ESTABLISH-req, PCC-RLC-REALLOC-req and PCC-RLC-MODIFY-req messages

the index of the concurrent TBF (if any). However, this field shall be only set to a meaningful value in
PCC-RLC-ESTABLISH-req message. Note that the index does not change in case of re-assignment
and it is a priori not necessary to transmit the index in case of TBF release.
- In the PCC-DL-CONTROL-req from RRM to MAC the index of the TBF for which the control is for.
3.1.2.1.5 Indicate to the mobile station the MAC mode to use
PCC (CellT) indicates to the mobile station the MAC mode to be used through the
EXTENDED_DYNAMIC_ALLOCATION bit (equal to 1 if EDA is active) located in the dynamic allocation
structure (present in Packet Uplink Assignment or in Packet Timeslot Reconfigure).
For backward compatibility reasons, the MAC_MODE field in the Packet Downlink Assignment message
shall be set to EDA if there is an ongoing uplink TBF in EDA mode (see CR30924-30927). Otherwise, it shall
be set to DA. Note that Rel-5 onwards the mobile station will ignore this field.
The value of the MAC mode may be changed (by the PRH) between DA and EDA (and vice versa) while the
mobile station is in Packet Transfer Mode (PTM) or Dual Transfer Mode (DTM). Note that, in rare scenarios,
an UL TBF can be established directly in EDA mode.
Since EDA will not be used for configurations that does not require this mode to be supported, the MAC
mode change (between DA and EDA and vice versa) will be always associated to a TBF re-configuration (re-
allocation in Alcatel langage) message. Nevertheless, due to some transition scenarios, it can happen that a
re-configuration message changes the MAC mode without changing the configuration (for example,
whenever the third timeslot of a 2+3 configuration is pre-empted by CS, the resulting 2+2 configuration is still
supported in EDA mode until a re-configuration to 2+2 in DA mode happens).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 38/77
Since all TBF re-configuration messages (except the Packet Uplink ASsignment) are required to be
acknowleged (through a PCA), it is not necessary to specify the case where the BSS and the mobile station
do not operate in the same mode (DA/EDA).
3.1.2.1.6 Indicate to PTU the MAC mode to use
PCC shall indicate to MAC the MAC mode to use (DA or EDA). This will be done through a new parameter
(EDA_mode) added in PCC-RLC-ESTABLISH-req and PCC-RLC-REALLOC-req messages and thus used
to indicate whether the EDA mode should be used by MAC or not for this mobile.
3.1.2.1.7 Transmission of NACC/PSI messages
To simplify and avoid dependence between USF setting and transmission of NACC/PSI messages for a TBF
in EDA mode, same policy as in B9 shall apply for transmitting NACC/PSI messages for a mobile station:
- If both TBFs are existing, the messages are sent on the DL TBF,
- Otherwise the messages are sent on the existing (DL or UL) TBF.
This policy is complementary to the one used at MAC level (see section 3.1.2.3.2.2.5).
3.1.2.1.8 Note about Uplink Control Timeslot
PCC shall not use the uplink control timeslot (see ref [3]) so that the policy proposed for TBF in EDA mode in
extended uplink TBF mode (see section 3.1.2.3.2.2.2) can be used. Indeed, if the uplink control timeslot is
not used, all assigned PDCH are seen as possible PACCH for the uplink TBF by the mobile station (the
mobile station can thus for example send a Packet Resource Request on its highest assigned PDCH while in
extended uplink TBF mode).
3.1.2.2 Step 2 RRM-PRH
In this section, it is supposed that the mobile station is allowed to use the EDA mode as specified in section
3.1.2.1.1.
3.1.2.2.1 Take into account new radio configurations
3.1.2.2.1.1 Supported TS configurations in EDA
In the Alcatel BSS, EDA (Extended Dynamic Allocation) will only be supported for mobile stations (compliant
with the activation level, see section 3.1.1.1) whose:
- GPRS (respectively EGPRS) multislot class is 3, 11 or 12,
- GPRS (respectively EGPRS) DTM multislot class is 11.
All configurations to be supported in EDA mode are defined in section 3.1.1.2. All other configurations shall
be supported in DA mode.
All rules to apply about the configurations to be supported in EDA mode are defined in section 3.1.1.2.
The TS configurations for which EDA shall be used in uplink shall only be considered by RRM-PRH if the
flag EDA_Allowed_GPRS or EDA_Allowed_EGPRS is positioned to true by RRM-PCC (see section
3.1.2.1.2). If EDA is not allowed, then only the TS configurations in DA shall be considered by RRM-PRH.
3.1.2.2.2 Determine the target configuration to try to set-up
PRH should determine the target configuration for a mobile (choose one of the configurations (x+y) that the
algorithm should try to set-up).
The solution described hereafter has been chosen. Some more complex solutions based on the ratio
amount of data transmitted in downlink over amount of data transmitted in uplink have been proposed in
reference [1].

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 39/77
In case of one phase uplink access, it is assumed that:

- The bias is downlink,
- The multislot class to use is the default one.
In case of two phase uplink access, it is assumes that:
- The bias is uplink,
- The DA mode is used.
As explained before, once N_Candidate_For_Realloc octets have been exchanged, PCC subscribes to a T3
reallocation. As long as the N_UL_BIAS_FOR_EDA condition is not met, PCC does not indicate to PRH that
EDA can be used for this TBF (i.e. that DA shall be used). When the condition is met, then PCC indicates
that the EDA mode can be used. PRH can then choose one of the EDA configurations.
Let us take the example of multislot class 12 mobile station making a two-phase uplink access. At TBF
establishment, a (3+2) configuration will be chosen. After the exchange of N_Candidate_For_Realloc octets,
PCC subscribes to T3. When playing the radio resource allocation algorithm, CellT asks for the EDA mode
to use to MS, which will answer with DA as long as the N_UL_BIAS_FOR_EDA condition is not met. When
this condition is met, then MS can tell to CellT that the EDA mode can be used (EDA_Allowed_(E)GPRS can
be set to EDA). The target configuration is then either 4+1 or 1+4, depending on the bias.
The other configurations (e.g. 3+2 or 2+3) will only be chosen if the 4+1 and 1+4 configurations cannot be
reached.
The following table indicates the number of slots targeted for downlink and uplink (i.e. the values of
n_MS_requested and of n_MS_requested_concurrent) depending on the multislot class and on the bias of
the mobile station.
The number of slots targeted also depends on whether EDA is allowed for the service being considered
(GPRS or EGPRS). In the following table with EDA means EDA_Allowed_(E)GPRS = true, and w/o
EDA means EDA_Allowed_(E)GPRS = false:
Multi R Tx Sum Supported GPRS packet Targeted number of slots

slot x connection configurations
class (DL, UL)
Sub-optimal Optimal UL bias DL bias
1 1 1 2 No (1+1) (1,1)
2 2 1 3 (1+1) (2+1) (2,1)
(2+1), (2,1) w/o EDA (2,1)

3 2 2 3 (1+1) w/ EDA: (1,2) with
(1+2) EDA
4 3 1 4 (1+1), (2+1) (3+1) (3,1)
5 2 2 4 (1+1), (1+2), (2+1) (2+2) (2,2)
6 3 2 4 (1+1), (1+2), (2+1) (2+2), (3+1) (2,2) (3,1)
7 3 3 4 (1+1), (2+1), (1+2) (3+1), (2+2) (2,2) (3,1)
8 4 1 5 (1+1), (2+1), (3+1) (4+1) (4,1)

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 40/77
(1+1), (2+1),
9 3 2 5 (3+2) (3+2)
(3+1), (1+2), (2+2)
(1+1), (2+1),
10 4 2 5 (3+2), (4+1) (3+2) (4+1)
(3+1), (2+2), (1+2)
(1+1), (2+2), (3,2) w/o EDA (4,1)

(3+2), (4+1)
(2+1), (3+1), (1+2)
11 4 3 5 (2,3) with
w/ EDA:
w/ EDA: (1+3), EDA
(2+3)
(1+2)/1H
(3+2) (3,2) w/o EDA (3,2)

DTM
4 3 5 (2+2) w/ EDA: (2,3) with
11
(2+3) EDA
(1+1), (2+2), (3,2) w/o EDA (4,1)

(2+1), (3+1), (1+2)
(3+2), (4+1) (1,4) with
12 4 4 5 w/ EDA: (1+3), EDA
w/ EDA:
(1+2)/1H ,
(2+3), (1+4)
(1+3)/1H (2x),
(1+2)/2H
Table 3: number of targeted timeslots
Notes:
- The definition of the bias is unchanged in RRM-PCC.
- RRM-PRH shall take into account the bias computed by PCC also for mobile stations in DTM
mode.
- For multislot class 12, the TS combination 2+3 is never targeted a priori.
3.1.2.2.3 Determine the best radio allocation
PRH should determine the best radio allocation for a mobile, i.e. should try to allocate TSs that enable to
best fulfill the target configuration and potentially switch to another configuration that gives a better
throughput.
Optimal and sub optimal configurations that can be used are described in section 3.1.1.2.
Depending on the chosen configuration, the EDA mode will be indicated or not to MAC18.
The following constraints should be taken into account by the PRH radio resource allocation algorithm:
When examining a TS configuration for which EDA shall be used in uplink, a PDCH on a given TRX must
verify the following conditions in order to be included in a candidate timeslot allocation (non-multiplexed-EDA
strategy, see section 3.1.1.3.1):
The PDCH shall not support any (GPRS or EGPRS) Best-Effort UL TBFs of other MSs,
18
Note that according to the section 3.1.1.3.3.2, some transition phases may happen during which a configuration is
supported at MAC level with the EDA mode whereas the usage of this mode is not necessary. In such scenario, RRM-
PRH shall not forget that the configuration is supported with the EDA mode. Moreover, RRM-PRH shall be able to trigger
a reallocation with only a change in the MAC mode.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 41/77
The PDCH shall not support any resources allocated to (GPRS or EGPRS) RT PFCs in the UL

direction for other MSs,
The PDCH shall not support any PACCH TS of (GPRS or EGPRS) Best-Effort DL TBFs of other
MSs,
The PDCH shall not support any PACCH TS of (GPRS or EGPRS) RT PFCs in the DL direction for
other MSs.
The PDCH shall not support any EGPRS DL TBFs if the candidate TS allocation is a GPRS
allocation.
Note: that implicitly means that the non-multiplexed-EDA strategy is played before the throughput
computation and that the MIN_THROUGHPUT_GAIN mechanism is not considered when switching from
EDA to DA mode.
RRM-PRH may favour a DA configuration when DA and EDA configurations are equivalent.
3.1.2.2.4 Impacts on T3 reallocation trigger
When playing a T3 TBF reallocation request for an MS having currently an established UL TBF using EDA,
it shall be checked if the usage of EDA is still valid for this UL TBF or not. This includes the rules of the non-
multiplexed-EDA strategy (see section 3.1.1.3.1) and the case where the existing TS allocation of the MS
can be handled in DA mode.
In order to perform more rapidly the non-muliplexed-EDA strategy in some scenarios, the maximum number
of successful T3 radio resource reallocation attempts that can be performed upon expiry of the
T_CANDIDATE_TBF_REALLOC timer is changed from 1 (in B9) to a value given the
N_MAX_PERIODIC_REALLOC_SUCCESS_T3 parameter (see section 3.2.3.1.1).
3.1.2.2.5 Transmission resource considerations
To simplify and to keep the B9 behaviour (in terms of interactions between radio and transmission
resources), no dedicated consideration about transmission resource issues is perfomed when triggering the
EDA mode for an uplink TBF. That means that when RRM decides to apply to a MS a configuration requiring
the EDA mode, RRM does not check if there are enough transmission resources to fully use the capability of
EDA.
This simplification may lead to non-optimal behaviour of TBF in EDA mode in case of transmission resource
congestion19.
3.1.2.2.6 Packet PDCH release policy
Since a mobile station using EDA mode cannot necessarily listen to all downlink PDCHs corresponding to its
uplink PDCHs assigned, when a PDCH is released the Packet PDCH Release message shall also be sent
on the PDCHs supporting at least one PACCH of an UL TBF in EDA mode that is assigned on the PDCH
released.
3.1.2.2.7 Management of DTM multislot class 11
Same procedures (especially the non-multiplexed-EDA strategy and the T3 reallocation schemes) shall
apply for the TBF of a DTM call except for the following point:
Due to the fact that the reallocation of a DTM call is allowed only at constant TCH position, RRM-PRH shall
favour the initial allocations of a DTM call that cannot lead to a blocking situation in terms of switching to the
EDA mode. This can be performed by favouring the assignment scheme with the TCH on the right in case of
DTM multislot class 11.
Remind that only T3 reallocation is allowed in DTM mode (no T1, T2 and T4 trigger).
19
Note that the PDCH allocation reduction capability would have been useful for TBF in EDA mode in such scenarios.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 42/77
3.1.2.3 Step 2 MAC

3.1.2.3.1 MAC mode to apply
The mode to apply (DA or EDA) is transmitted from RRM-PCC to MAC through the TBF configuration and
re-configuration messages (see section 3.1.2.1.6). Since EDA will not be used for configurations that does
not require this mode to be supported, the MAC mode change (between DA and EDA) will be always
associated to a TBF radio re-configuration (i.e. reallocation in Alcatel language).
3.1.2.3.2 Uplink scheduling
The global principles of the B9 scheduling are kept (except that the Weighted Round Robin is now
supported):
- TBF Round Robin (managed through a chained list).
- A TBF is pushed at the end of the TBF list whenever at least one PDCH has been allocated to it.
3.1.2.3.2.1 TBF in DA mode
3.1.2.3.2.1.1 TBF in DA mode in active phase
Same scheduling as in B9 is kept, i.e. that a PDCH round robin for TBF in DA mode is performed with only
one PDCH scheduled per step (keeping in memory the last PDCH scheduled).
3.1.2.3.2.1.2 TBF in DA mode in extended uplink phase
Same scheduling as in B9 is kept, i.e. that a TBF in DA mode in EUTM shall be scheduled on the PDCH
supporting its PACCH.
3.1.2.3.2.2 TBF in EDA mode
All MAC principles used for TBF in DA mode also apply for TBF in EDA mode (e.g. scheduling depending on
the weight, a TBF is pushed at the end of the list if it has been scheduled, downlink EGPRS / uplink GPRS
constraints shall be taken into account, etc). The only exceptions are the ones that are exposed in all this
section about TBF in EDA mode.
No assumption considering that the non-multiplexed-EDA strategy (see section 3.1.1.3.1) will be always
reached and thus leading to implementation simplification shall be done. The transition phases (see section
3.1.1.3.3.2) shall be supported (that means for example that the EDA mode shall be supported even for TBF
with only one assigned timeslot).
3.1.2.3.2.2.1 TBF in EDA mode in active phase
MAC shall support uplink TBFs with hole in the assignment in order to manage sub-optimal radio
configurations and DTM multi-slot class 11 configurations.
It is assumed in this part that MAC is able to identify all answers to polling dedicated to a mobile station that
has a current uplink TBF in EDA mode (see 3.1.2.3.2.2.4 for more information).
Important notice: according to the basic rules of DA, uplink PDCH allocations in a given BP are performed
through setting of USFs in downlink blocks of the previous BP. In this section, it is only mention PDCH
allocation to simplify. The reader shall interpret PDCH allocation or PDCH scheduling in a given BP actually
as setting of the corresponding USFs in the previous BP.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 43/77
3.1.2.3.2.2.1.1 Variable needed per TBF

3.1.2.3.2.2.1.1.1 Global (i.e. during the TBF lifetime)
For each TBF in EDA mode, the lowest PDCH allocated in the previous BP shall be kept in memory to take
into account constraints of EDA operations from a BP to the following one. Let us call this variable
Lowest_PDCH_allocated.
When a TBF goes to the EDA mode, the Lowest_PDCH_allocated of the TBF shall be set to the highest
PDCH assigned to the TBF.
3.1.2.3.2.2.1.1.2 Local to a given block period
During the building of the (uplink) scheduling pattern within a given BP, the following variables shall be used
for each TBF in EDA mode:
- Lowest_PDCH_to_analyse,
- Highest_PDCH_to_analyse
- Scheduled,
- Schedulability (of the TBF).
Lowest_PDCH_to_analyse and Highest_PDCH_to_analyse delimit the domain of assigned PDCHs to

analyse. Scheduled (0/1) describes the fact that at least one PDCH has already been allocated to this TBF
(within the block period). Schedulability (0/1) describes the schedulability of the TBF (e.g. it becomes not
schedulable when all its assigned PDCHs have been analysed).
3.1.2.3.2.2.1.2 Algorithm
At each new BP start (i.e. before the building of the (uplink) scheduling pattern) for each TBF in EDA mode:
- If an answer to a polling is awaited from the mobile station (thus on the uplink PDCH supporting the
PACCH), Lowest_PDCH_to_analyse shall be set to MIN(Lowest_PDCH_allocated, PDCH where
the answer is awaited)20. Otherwise Lowest_PDCH_to_analyse shall be set to the
Lowest_PDCH_allocated21. Relatively to the notice above and to avoid misunderstanding about the
BP concerned, please find an illustration below in case of a 2+3 configuration:
20
Due to the fact that Ttb and Tta are inferior to 3 for the multi-slot classes from 1 to 12 supporting configurations
requiring EDA mode, this condition is sufficient to guarantee that there is no collision between reception (USF monitoring)
and the transmission of a polling answer and thus to avoid to consider measurement capabilities of the mobile stations at
MAC level. Due to the fact that the polling answer will be always transmitted on the first (bi-directional) PDCH,
Next_PDCH_to_analyse could be set in this scenario to the lowest timeslot assigned to simplify.
21
Note that the management of the block period in which a polling answer is awaited might be also performed at
implementation level in the previous block period provided that the scheduling result is the same. For example: in the BP
n+2 in the figure above. One solution would be: when the TBF becomes non schedulable in BP n+2,
Lowest_PDCH_allocated might be set to MIN(current value of Lowest_PDCH_allocated, PDCH where the answer is
awaited but this time in the next BP).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 44/77
Let us consider:
- A MS in 2+3 configuration using MCS9,
- A MEGCH size (e.g. 9) enough to transmit 2 MCS9 radio blocks but no more
(i.e. that 2 MCS9 radio blocks plus 1 CS1 block do not fit).
The figure represents successive block periods truncated each time to the three
assigned timeslots of the first TDMA frame (downlink and uplink):
In BP n, a polling is sent on the first

(common) assigned timeslot. Thus an BP n
answer to polling is awaited from the mobile
station in BP n+3 on the first PDCH.
BP n+1
In BP n+2, the USF cannot be set
because 2 radio blocks in MCS9 plus 1
CS-1 block do not fit in the MEGCH and BP n+2
because the reduction is not supported.
In BP n+3, an answer to polling is BP n+3

awaited from the mobile station on the
first PDCH. Thus its USF cannot be set BP n+4
on the third PDCH. It also cannot be
set on the second one since PDCH
allocation reduction is not supported. BP n+5
It also cannot be set on the first one
because of MEGCH constraints.
Thus it cannot be set at all.
LEGEND:
: radio block not used or used for other mobile stations
: downlink radio block in which the network sets the USF of the mobile station
: downlink radio block sent by the network (DL TBF) for the mobile station
: downlink radio block containing a polling request for the mobile
: uplink radio block containing the answer to a polling request (DL TBF) from
the mobile station
Figure 26: illustration of polling issues for TBF in EDA mode
- Highest_PDCH_to_analyse shall be set to the highest PDCH assigned.
- Schedulability shall be set to 1 (means that the TBF is schedulable at the start of this BP).
- Scheduled shall be set to 0.
Each times a TBF in EDA mode is considered in the (uplink) scheduling list, the following procedure shall
apply (instead of the one used for TBF in DA mode) (note that this processus has been specified to support
assignment with hole):

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 45/77
YES Condition A? NO
Allocation YES Scheduled==1? NO

Lowest_PDCH_allocated=
Lowest_PDCH_to_analyse
Scheduled=1
Lowest_PDCH_allocated=
highest PDCH assigned
Lowest_PDCH_to_analys
YES e==lowest PDCH NO
assigned? Schedulability=0
Schedulability=0 Lowest_PDCH_to_analyse=
next lower PDCH assigned
Highest_PDCH_to_analyse=
Lowest_PDCH_to_analyse
The TBF is pushed at the end of the list
Figure 27: diagram of the scheduling of TBF in EDA mode
With:
Condition A = Among the PDCH(s) assigned to the TBF from the one numbered
Lowest_PDCH_to_analyse to the one numbered Highest_PDCH_to_analyse (both included), all are free
or already allocated for a polling answer for the mobile station. And there is enough transmission resources
to serve among these PDCHs the ones that are free22.
Allocation = The PDCH(s) tested during the condition A shall be allocated to the uplink TBF. The RT or
NRT credit of the TBF shall be decremented by the number of new free PDCHs allocated (negative credits
are allowed whatever the scheduling phase)23. Please see 3.1.2.3.2.2.3 to see the impacts on the USF
setting and on the burst type setting.
Note that a TBF in EDA mode shall be analysed at least one time per BP so that the
Lowest_PDCH_allocated may be reset to the highest timeslot assigned in case the TBF is not scheduled at
all in a BP.
Note that the solution proposed with scheduling per step is necessary to manage scenarios of transmission
resource congestion and to manage scenarios of TBF multiplexing.
22
We assume in this part that the B9 processus reserving at the BP start the amount of transmission resources needed
for transmitting all answers to polling requests awaited in this BP is kept.
23
Note that the other WRR rules apply but are not mentioned here.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 46/77
Some examples of uplink scheduling with TBF in EDA mode are given in 9.3.
3.1.2.3.2.2.2 TBF in EDA mode in extended uplink phase
The scheduling processus defined above applies also for TBF in EDA mode in extended UL mode
(especially the constraint about polling answers) except that they shall be scheduled at the maximum on only
one PDCH: not on the PDCH supporting their PACCH but on their highest assigned PDCH (see section
3.1.2.1.8).
Note that one of the consequences is that a TBF in EDA mode in extended uplink mode could not be
scheduled in a block period following a block period where a polling answer is awaited from the mobile
station.
3.1.2.3.2.2.3 Setting of USFs and uplink burst types
According to the notice in 3.1.2.3.2.2.1, PDCH allocations correspond actually to setting of USF (in the
previous BP).
The MAC layer shall set the USFs and the burst types expected as in B9 on all PDCHs where an uplink
block is awaited. Note that, according to the standard (see 3GPP 43.064 or section 9.1.3), the setting of the
USF on all allocated PDCHs is mandatory although a mobile station in EDA mode will actually not listen or
ignore the USF in some scenarios.
The burst types shall be set as if each PDCH had been scheduled independently.
The only change compared to B9 comes from the following fact: when an answer to a polling is awaited in a
BP, a USF can be set in the corresponding downlink PDCH in the previous BP in some scenarios. In this
case, MAC shall not set of course the USFNE (USF No Emission). Note that MAC shall set in this case the
burst type (normal burst or access burst) as in B9 i.e. according to the type of polling anser awaited.
The following example illustrates the setting of the USFs. Let us take a TBF in EDA mode assigned on the
uplink PDCHs 1, 2, 3 and 4 with the following corresponding USFs: 2, 3, 4, 5.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 47/77
The figures represent successive block periods truncated each time to the four assigned timeslots of the first
TDMA frame (downlink and uplink):
Let us assume that the USF2 USF3 USF4 USF5

first downlink block
contains a polling 1 2 3 4
request for the mobile
station
1 2 3 4
The USFs shall be set on
all PDCH scheduled even USF2 USF3 USF4 USF5
if the mobile station will
not listen to them on 1 2 3 4
PDCH 2, 3 and 4.
The USF2 is set on the first

1 2 3 4
PDCH (although the
answer to the polling is
awaited in the next block USF2 USF3 USF4 USF5
period) so that no PDCH
allocation reduction is
needed.
1 2 3 4
USF2 USF3 USF4 USF5
1 2 3 4
LEGEND:
: radio block
: downlink radio block containing a polling request / uplink radio block

containing the answer to a polling request (DL TBF)
Figure 28: illustration of USF setting for TBF in EDA mode
3.1.2.3.2.2.4 MS context
To optimize the throughput of TBF in EDA mode (relatively to the above figure), MAC shall be able to identify
all answers to polling dedicated to a mobile station that has a current TBF in EDA mode. There are two kinds
of such answers to polling (see section 3.1.2.1.4):
- Answers to polling triggered by RLC (e.g. for PDAN),
- Answers to polling triggered by RRM (e.g. PCA). These ones are transparent for RLC.
To be able to identify all answers to polling dedicated to a mobile station, a MS (Mobile Station) context per
mobile station is necessary in MAC layer so that MAC can correlate downlink TBF, downlink control blocks
from RRM and uplink TBFs (in EDA mode) belonging to the same mobile station.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 48/77
In the concern of this feature, the MS context is useful only in case a TBF in EDA mode exists for a mobile
station. However, in order to anticipate further features like e.g. multiple TBF, it seems necessary to create
this MS context if at least one TBF is established for a given mobile station.
A MS context shall be created as soon as there is a (downlink or uplink) TBF created for a new mobile
station and destroyed if there is no more TBF for this mobile station. Each times a TBF context is created,
updated or deleted at MAC level, the corresponding MS context shall be created, updated or removed.
The MS context is actually composed of the TBF_index of the DL TBF (if any) and of the TBF_index of the
UL TBF (if any). Note that the TBF index is not changed by RRM in case of re-allocation.
MAC shall create a new MS context or update the MS context concerned (if necessary) each times it
receives a valid concurrent TBF index in a PCC-RLC-ESTABLISH-req message (see section 3.1.2.1.4).
MAC shall update/remove the MS context concerned if one of both TBFs is released.
In case MAC checks on a given PDCH whether the USF of a TBF in EDA mode can be set in the previous
block period to a block period in which a polling answer is awaited, it shall check whether this polling answer
is dedicated to the mobile station for which the TBF in EDA mode belongs to, i.e. whether the current TBF
index in the downlink control block from RRM is:
- Either the one of the concurrent downlink TBF of the TBF in EDA mode,
- Or the one of the TBF in EDA mode.
Same procedure shall apply for polling answers triggered by RLC.
The MS context shall also be used to limit the position of the USF in block period in which a polling answer is
awaited (see section 3.1.2.3.2.2.1.2).
3.1.2.3.2.2.5 Transmission of NACC/Packet [P]SI messages

Same policy as in B9 shall apply for transmitting NACC/PSI messages on a given TBF except for uplink
TBFs in EDA mode. For this kind of TBFs, the messages shall be transmitted on the PACCH (i.e. on the first
PDCH).
This policy is complementary to the one used at RRM-PCC level (see section 3.1.2.1.7).
3.1.2.3.3 EDA-DA re-configuration
Note that an uncorrect decoding of an uplink TBF reconfiguration from EDA to DA mode by a mobile station
might lead to significant radio errors because a mobile station in EDA mode might significantly
corrupt/pollute a great domain of PDCHs.
However, this is not really probable since all re-configuration messages are required to be acknowleged
through a PCA (see section 3.1.2.1.5).
3.1.2.4 Step 2 RLC
3.1.2.4.1 MS context
See 3.1.2.3.2.2.4.
3.1.2.4.2 RLC window sizes
Correct RLC window sizes for 3 and 4 timeslots assigned shall be indicated to the mobile station.
Note that the current TBF instance in RLC can already manage RLC window sizes up to 4 timeslots per
uplink TBF.
3.1.2.4.3 Link adaptation
3.1.2.4.4 Transmission of NACC/PSI messages
Editoral changes needed to be inline with policy defined in sections 3.1.2.1.7 and 3.1.2.4.4.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 49/77
3.1.2.4.5 Note about the support of configurations with hole in the assignment
It should be checked if the way RLC computes the number of assigned PDCHs for a TBF is correct (this
number is used for example to compute the maximum RLC window size). Indeed, for example RLC shall not
compute this number by considering only the first assigned PDCH and the last assigned PDCH because of
possible configurations with hole in the assignment.
3.1.2.5 Step 2 BSS traffic model and capacity: PS part
Since EDA allows supporting more uplink timeslots, the mean number of timeslots to consider for uplink
transfers shall be increased (as a function of the percentage of EDA-capable mobile stations).
3.1.2.6 Step 2 MEGCH
In the B9 solution, MEGCH indicates to MAC the maximum MCS and CS for which a block can fit in the
remaining MEGCH size in the current block period.
This mechanism shall be changed so that more than one block in a given (M)CS can be requested in one
step to fit in the remaining MEGCH size. Indeed, due to the constraints linked to the EDA mode, following
case may happen: MAC tests if several radio blocks or none can be allocated. This function can be
performed either in MAC or in MEGCH.
3.1.2.7 Interfaces
This section gives the details of the signalling changes on the various interfaces connected to the BSS. If the
SFD should contain several features, the impacts of each feature on a given interface should be clearly
indicated.
3.1.2.7.1 PMU-PTU interfaces
Additional field (EDA mode) needed in PCC-RLC-ESTABLISH-req and PCC-RLC-REALLOC-req messages

(see section 3.1.2.1.6).
Additional field (concurrent TBF index) needed in PCC-RLC-ESTABLISH-req message (see section
3.1.2.1.4).
Additional field (current TBF index) needed in PCC-DL-CONTROL-req message (see section 3.1.2.1.4).
3.1.2.8 Radio interface (05.02, 04.06, 04.60, 04.18, 24.008, etc)
3.1.2.9 Abis interface (08.58)
3.1.2.10 A interface (08.08)
3.1.2.11 Gb interface (08.18)
3.1.2.12 BSCGP interface
3.1.2.13 GCH interface
3.1.3 Simulations
Simulations have been performed to confirm the proposed MAC scheduling algorithm.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 50/77
Simulations have been performed to evaluate the performances of the non-multiplexed-EDA strategy (see
section 3.1.1.3.1).
3.2 Operation and maintenance
3.2.1 OMC-R parameters

3.2.1.1 New parameters
3.2.1.1.1 EN_EDA
Definition: Enables Extended Dynamic Allocation (EDA).
Sub-system: MFS.
Instance: Cell.
Category: Site (CAE).
OMC-R access: Changeable.
Type: Flag.
Unit: None.
Min: 0.
Max: 1.
Default: 0.
Coding rules:
- 0: EDA not activated,
- 1: EDA activated.
External comment: when EDA is activated, its activation level is given by the
EDA_MS_ACTIVATION_LEVEL and ALLOW_DTM_EDA_COMBINATION parameters.
Mandatory rules: EN_EDA shall be forced to 0 in extended cells and in non-evolium cells.
Spec reference: RRM sublayer (PCC).

3.2.1.1.2 EDA_MS_ACTIVATION_LEVEL
Definition: Activation level of Extended Dynamic Allocation (EDA).
Sub-system: MFS.
Instance: BSS.
Type: Number.
Unit: None.
Min: 0.
Max: 2.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 51/77
Default: 0.
Coding rules:
- 0: EDA activated for all mobile stations (supporting the feature),
- 1: EDA activated for R99-onwards mobile stations (supporting the feature),
- 2: EDA activated for Rel-4-onwards mobile stations (supporting the feature).
Internal comment: Further releases have not been considered since there is no same mean to detect if a
mobile station is compliant with them.
External comment:
- This parameter is relevant only if EDA is activated (EN_EDA parameter).
- The activation level may provide an artificial mean to limit the inter-operability risks due to mobile
stations with uncorrect EDA implementation (EDA is a R97 feature but has been completely clarified
in Rel-6). R99 is detected through the Revision Level Indicator. A mobile station is assumed to be
Rel-4-compliant if it supports the GERAN Feature Package 1 (theoretically it is not possible to
precisely identify a Rel-4-compliant mobile station).

3.2.1.1.3 ALLOW_DTM_EDA_COMBINATION
Definition: Allows EDA operations for mobile stations in DTM mode.
Sub-system: MFS.
Instance: BSS.
Type: Flag.
Unit: None.
Min: 0.
Max: 1.
Default: 0.
Coding rules:
- 0: the usage of EDA for mobile stations in DTM mode is not allowed,
- 1: the usage of EDA for mobile stations in DTM mode is allowed.
Internal comment:
- This flag provides a mean to disable the usage of EDA in case of DTM operations. Indeed some
mobile stations might not correctly support the combination of these two features.
- None of the combination of the EN_EDA, EN_DTM, EDA_MS_ACTIVATION_LEVEL and

ALLOW_DTM_EDA_COMBINATION parameters allows activating EDA only in case of DTM
operations.
External comment: this flag is relevant only if DTM and EDA are both activated.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 52/77

3.2.1.1.4 N_UL_BIAS_FOR_EDA
Definition: Minimum number of consecutive uplink biases observed to allow a mobile station to use Extended
Dynamic Allocation.
Sub-system: MFS.
Instance: BSS.
Type: Number.
Unit: None.
Min: 1.
Max: 64.
Default: 5.
Internal comment: A default value of 5 (in case N_BIAS_DETERMINATION is set to 3 and

WEIGHT_BIAS_DETERMINATION to 70%) allows avoiding the usage of EDA in case of ping scenarios.
Indeed EDA can degrade the performances in such scenarios, especially in case of long ping with extended
uplink TBF mode.
External comment: this mechanism/condition allows using EDA only when really necessary (i.e. in case of
long uplink transfer) so as to limit the constraints associated to the usage of the EDA mode. Note that this
condition can trigger the usage of the EDA mode only if the other conditions are also fulfilled. Parameter set
to 1 corresponds to a desactivation of the N_UL_BIAS_FOR_EDA mechanism.

3.2.1.2 Parameters modified
None.
3.2.2 Modelisation of OMC-R parameters
3.2.3 Other parameters

3.2.3.1 New parameters
3.2.3.1.1 N_MAX_PERIODIC_REALLOC_SUCCESS_T3
Definition: Maximum number of successful T3 radio resource reallocation attempts that can be performed
upon expiry of the T_CANDIDATE_TBF_REALLOC timer.
Sub-system: MFS.
Instance: MFS.
Category: System (CST).
OMC-R access: None (DLS).
Type: Number.
Unit: None.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 53/77
Min: 1.
Max: 500.
Default: 2.
Internal comment:
- This parameter is linked to the N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 parameter.
- A default value of 1 leads to B9 behaviour.
- A default value of 2 allows performing more rapidly the non-muliplexed-EDA strategy in some
scenarios.
External comment: the maximum number of successful T3 radio resource reallocation attempts that can be
performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer is limited by the Round Trip Delay.
Mandatory rules: N_MAX_PERIODIC_REALLOC_SUCCESS_T3 <=

N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 if N_MAX_PERIODIC_REALLOC_ATTEMPT_T3 > 0.
Spec reference: RRM sublayer (PRH).

3.2.3.2 Parameters modified
3.2.3.2.1 N_MAX_PERIODIC_REALLOC_T3
The parameter shall be renamed in N_MAX_PERIODIC_REALLOC_ATTEMPT_T3.
Definition and internal comment shall be updated accordingly.

3.2.3.2.2 N_MAX_PERIODIC_REALLOC_T4
The parameter shall be renamed in N_MAX_PERIODIC_REALLOC_ATTEMPT_T4.
The internal comment shall be updated accordingly.

3.2.3.2.3 T_CANDIDATE_TBF_REALLOC
Defintion and external comment shall be updated according to the two previous changes.
3.2.4 PM counters
3.2.4.1 Counters in the BSC
None.
3.2.4.2 Counters in the MFS
3.2.4.2.1 New counters
3.2.4.2.1.1 NB_EDA_MS_CONTEXT_GPU
Definition: number of EDA-capable GPRS and EGPRS MS contexts.
Trigger (RRM-PCC): for a MS context, the MS Radio Access Capability indicates the support of EDA either
in GPRS mode or in EGPRS mode or in both modes. If EDA is supported in both modes, the counter shall
be incremented only by one.
Instance: BSS.
3.2.4.2.1.2 NB_EDA_ALLOWED_UL_TBF
Definition: number of uplink TBF belonging to mobile stations allowed to use the EDA mode.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 54/77
Trigger (RRM-PCC):
- At uplink TBF establishment, it is known that the mobile station is allowed to use the EDA mode (that
implies that the RAC are already known).
- When reading the RAC of a mobile station while its uplink TBF is already established, it is known
that the mobile station is allowed to use the EDA mode.
Notes:
- A mobile station is known as allowed to use the EDA mode according to the rules defined in section
3.1.2.1.2. However the N_UL_BIAS_FOR_EDA condition shall not be taken into account for this
counter.
- The counter shall be incremented at most by one per uplink TBF.
Instance: Cell.
3.2.4.2.1.3 NB_EDA_USED_UL_TBF
Definition: number of uplink TBF that have used at least one time the EDA mode during their lifetime.
Trigger (RRM-PCC or RRM-PRH): an uplink TBF is (re-)allocated in the EDA mode at least one time during
its lifetime. The counter shall be incremented at the most by one per uplink TBF.
Instance: Cell.
3.2.4.2.1.4 CUMULATED_TIME_ACTIVE_UL_CONNECTED_TIME_EDA_MODE
Definition: cumulated overall time of uplink TBF in active state operating in EDA mode.
Counter start (RRM-PCC): when an UL TBF in active phase and in DA mode is reallocated in EDA mode, or
when an UL TBF in EDA mode and in Extended Uplink TBF Mode wakes up or when an UL TBF is
established directly in EDA mode.
Counter stop (RRM-PCC): when an uplink TBF in EDA mode goes to Extended Uplink TBF Mode, or when
an uplink TBF in active phase and in EDA mode is realocated in DA mode, or when an uplink TBF in EDA
mode ends (normally or not).
Notes: this counter applies to both acknowledged and unacknowledged RLC modes. An uplink TBF released
due to a NC cell reselection is managed as an abnormal uplink TBF release.
Instance: Cell.
3.2.4.2.1.5 NB_DA_EDA_REALLOC_UL_TBF
Definition: number of reallocations between DA and EDA modes for uplink TBF. Note that that means that
such TBF have necessarily used at least one time the EDA mode during their lifetime.
Trigger (RRM-PCC or RRM-PRH): an uplink TBF is re-allocated from DA mode to EDA mode (or inversely).
Instance: Cell.
3.2.4.2.2 Existing counters
3.2.4.2.2.1 CUMULATED_TIME_UL_BIASED_AND_OPTIMAL_UL_ALLOCATION (for information)
The counter is not changed. Nevertheless it will be probably impacted due to the non-multiplexed-EDA
strategy (see section 3.1.1.3.1).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 55/77
3.2.5 PM indicators
Mnemonic Definition Formula
Percentage of mobile stations supporting 100*NB_EDA_MS_CONTEXT_GPU/NB_A

EDA (either in GPRS or in EGPRS or in LL_MS_CONTEXT_GPU
both modes). BSS level.
Percentage of overall time during which 100*CUMULATED_TIME_ACTIVE_UL_CO

uplink TBF in active state have used the NNECTED_TIME_EDA_MODE/(CUMULAT
EDA mode. Cell level. ED_TIME_ACTIVE_UL_CONNECTED_TI
ME_GPRS_ACK+CUMULATED_TIME_AC
TIVE_UL_CONNECTED_TIME_GPRS_NA
CK+CUMULATED_TIME_ACTIVE_UL_CO
NNECTED_TIME_EGPRS_ACK+CUMULA
TED_TIME_ACTIVE_UL_CONNECTED_TI
ME_EGPRS_NACK)
Mean number of reallocations between DA NB_DA_EDA_REALLOC_UL_TBF/NB_ED

and EDA modes per uplink TBF that have A_USED_UL_TBF
used at least one time the EDA mode
during their lifetime. Cell level.
Percentage of uplink TBF belonging to 100*NB_EDA_USED_UL_TBF/NB_EDA_A

mobile stations allowed to use EDA that LLOWED_UL_TBF
have been allocated in EDA at least one
time during their lifetime. Cell level.
3.2.6 Migration
3.2.7 Java scripts
3.2.8 Fault Management
3.2.9 O&M Specification impacts
3.3 Validation
The Extended Dynamic Allocation feature test strategy will be covered in detail during Test-Task Force
(TTF). The objective of the task-force will be to define, per feature, the test strategy and the tests list for
different test phases. This means sub-system integration, system pre-integration, System integration and
System Validation, for functional, performances and load tests. The TTF will have in mind to implement the
best compromise between test effort and test coverage and the right repartition between the test activities.
3.3.1 Testing tools
The table below gives a list of tools planned to be used for B10 sub-system integration, system integration,
and system validation. For each of them, it is indicated if the tool is a new one, or if this is an evolution of an
existing tool, or if the tool is just reused.
Tool Evolution Provider Comment
K1205 Yes Tektronix Stack adaptations are needed
Agilent Agilent

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 56/77
SGSN emulator Yes Ercom or For System Integration

K1297 or
Reverse GPU
MSTS Yes BTS-team For System Integration. MSTS needs to support

EDA mobiles
Pm check Yes BSC-team For System Integration and Validation
MFS Traces + Yes MFS team

HTTP server
Compass (Gb) No NetTest For Performance tests
LSU Yes Prisma See document LOAD tools Requirements

Specification
MDT Yes VAL-team To check/trace BSC internal messages
Tradeb-Mx Yes BSC-team Macros to check BSC DLS changes.
EDA-capable MS No ? For System Validation

(multislot class
324, 11 and 12)
EDA-capable MS Yes ? For System Validation; for mixed DTM-EDA tests

supporting DTM
multislot class
1125
3.3.2 Test strategy

3.3.2.1 System tests coverage
The Extended Dynamic Allocation feature can be validated only at system integration (functional system
tests) and completed at system validation level (end-to-end tests).
However, subsystem and system pre-integration tests should be achieved with a high level of quality.
Note that all IP features, GPRS improvement features (including Weighted Round Robin), 1000 TRX feature,
etc are out of the scope of this SFD. See referenced documents for the concerned tests.
3.3.2.2 Overall strategy for system tests
3.3.2.2.1 Overview
The functional tests (System Integration) will use MS, MSC and SGSN simulators to validate the EDA basic
scenarios and the error cases that will not be reached during end-to-end tests. It has to be underlined that
since CORE network equipments are quite expensive, that since there is a strong wish to have early
detection of the problems, it will be proposed during TTF to push as much as possible the sub-system tests
(validation of new SW).
24
It is not sure today that multislot classes 3 mobile stations supporting EDA will be available on the market.
25
The support of EDA for DTM multislot class 11 mobile stations is mandatory only from Rel-6. However, it is expected
that such mobile stations (Rel-4) will support EDA.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 57/77
The end-to-end tests (System Validation) will demonstrate that, when put in front of Alcatel CORE network,
the BSS will be compliant for both interoperability and end user point of view.
Telecom load tests will allow checking that the feature does not jeopardize the global BSS behaviour and
that performances in load are conformed to awaited performances.
O&M load tests and migration tests are not relevant for this feature.
Other tests depending on the mode (PTM or DTM) are described in the two next sub-sections (3.3.2.2.2 and
3.3.2.2.3).
Some special difficult points for system integration and validation can be raised now:
- Availability of EDA mobiles to be confirmed in addition to the risks of MS instability and unmaturity
(test at the same time BSS and MS) (see section 2.8.5).
- Management of two different softwares RLC/MAC in the BTS (case IP mode) and in the MFS (case
TDM mode), and probably two MAC behaviours not equivalent interaction with MEGH layer.
- Difficulty to evaluate new traffic model (which percentage of EDA mobiles is relevant) in load
conditions to test correctly possible side effect of the EDA feature.
Due to the important number of possible configurations (BTS HW, TPGSM boards, connectivity, BTS
connection, link, TDM/IP mode, MFS HW), the most representative platform configurations will be defined
precisely during the TTF.
3.3.2.2.2 PTM mode
First tests will demonstrate that there is no regression when EDA feature is not activated (EN_EDA
parameter at MFS level set to EDA_not_activated value).
Main tests can be split in the following separated domains:
- O&M domain:
o Six different modes are defined through the EN_EDA and EDA_MS_ACTIVATION_LEVEL
parameters.
- Telecom domain (functional domain):
o Check if EDA is correctly allowed according to the EDA_MS_ACTIVATION_LEVEL

parameter (this test is relevant only if R97 or R99 (see section 3.1.1.1) EDA-capable mobile
stations are available).
o Check MAC scheduling with one mobile station, especially the following points:
Polling policy (see section 3.1.1.5.1) (the behaviour is correct if no radio resource
are wasted, i.e. if maximum throughput reached corresponding to the maximum
number of uplink timeslots supported by the mobile station is reached).
TBF is scheduled on its highest PDCH in Extended Uplink TBF Mode.
Correct behaviour in case of transmission resource congestion (one example is

given in scenario II of section 9.3).
o Check behaviour of one mobile station in case of cell reselection in the following scenarios:
The mobile station was in EDA mode in the old cell and EDA is still possible in the
new cell.
The mobile station was not in EDA mode in the old cell but EDA is now possible in
the new cell.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 58/77
The mobile station was in EDA mode in the old cell and EDA is not possible in the
new cell.
o Check the non-multiplexed-EDA strategy (RRM-PRH level) at least in the scenarios below
(described in section 9.4). For each case, check also that the transition phases are correctly
managed.
3.a and 3.b,
4.a and 4.b,
4.c and 4.d,
4.e,
5.a and 5.b,
5.c and 5.d,
5.e and 5.f,
6.a and 6.b,
6.g and 6.h,
7.a and 7.b,
8.a and 8.b.
o Check the behaviour in case of bias changes: in case of long ping 0s with Extended Uplink
TBF Mode with N_UL_BIAS_FOR_EDA set to 1 (non-default value), check that the
allocation periodically changes (e.g. from 4+1 to 1+4 (and reversely) for a multislot class 12
mobile station).
- Telecom domain (performance domain) with one mobile station:
o Ping performances: tune the N_UL_BIAS_FOR_EDA parameter to the minimum value that
ensures that the performances of all ping types (see sections 3.1.1.6 and 9.7) are the same
whenever EDA is activated or not. The value found shall be set as the default value in the
BTP catalog.
o Uplink FTP transfer: check that the throughput is inline with the maximum number of uplink
timeslots supported by the mobile station (no radio resource wasting shall be observed (note
that in the 1+4 configuration case the maximum throughput might not be reached due to
BSIC decoding issues, see section 2.8.5.4 for more details).
- Telecom domain (load domain): low need since EDA will be used only at low load.
3.3.2.2.3 DTM mode (DTM multislot class 11)
DTM tests are described in DTM SFD. The main functional tests shall be performed again for DTM multislot
class 11.
Moreover, specific tests dedicated to DTM multislot class 11 shall be perfomed.
First tests will demonstrate that there is no regression when EDA is not allowed in DTM operations.
Main tests can be split in the following separated domain:
- O&M domain:
o Several modes are defined through the EN_EDA, EDA, MS_ACTIVATION_LEVEL,

EN_DTM and ALLOW_DTM_EDA_COMBINATION parameters.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 59/77
- Telecom domain (functional domain):

o Check if EDA is correctly allowed according to the parameters mentioned above (note that
the EDA_MS_ACTIVATION_LEVEL parameter should not have any impact since DTM
multislot class 11 has been introduced in Rel-4).
o Check MAC scheduling with one mobile station by checking that the maximum throughput is
reached on the PS part.
o Check the specific assignment strategy for DTM multislot class 11 and the non-multiplexed-
EDA strategy (RRM-PRH level).
o Check the behaviour in case of bias changes.
o Telecom domain (performance domain) with one mobile station in case of uplink FTP
transfer: check that the throughput is inline with the maximum number of uplink PS timeslots
supported by the mobile station.
- Telecom domain (load domain): low need since EDA will be used only at low load.
3.4 Methods
Network Reconfiguration Recommendation document is impacted.
3.5 GCDs
BSS System Description and BSS O&M Parameters documents are impacted.
3.6 Engineering rules

BSS Configuration Rules document is impacted.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 60/77
4 SUBSYSTEM IMPACTS
4.1 BTS
4.2 BSC
4.3 Transcoder
4.4 MFS
RRM-PCC shall detect if a mobile station is allowed to use the EDA mode in PTM and DTM modes.
Radio Resource Management algorithms are changed to take into account radio configurations that require
EDA to be supported. Dedicated assignment strategy applies for TBF in EDA mode.
Dedicated MAC uplink scheduling algorithm applies for TBF in EDA mode.
4.5 OMC-R
New parameters have been defined. Some existing parameters have been changed.
4.6 LASER
4.7 MPM/NPO
New counters and indicators have been defined.
4.8 Polo
4.9 OEF

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 61/77
5 PERFORMANCE & SYSTEM DIMENSIONING
5.1 Traffic model

No impact.
5.2 Performance
No impact (TBC).
5.3 Load constraints

No impact.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 62/77
6.2
6.1
ED 02 RELEASED
Open points
Action points
OPEN POINTS AND ACTION POINTS
30/03/2007
0025_02.doc
3BK 10204 0025 DTZZA
Extended Dynamic Allocation
63/77
7 IMPACTS SUMMARY
Equipments:
BTS BSC MFS TC OMC-R LASER MPM/NPO OEF Polo
x x x
Interfaces:
Telecom
Radio Abis A Ater BTS-TC MFS-BTS MFS-BSC PMU- Gb

PTU
O&M
Abis-O&M BSC-O&M TC-O&M MFS-O&M Q3
List of impacted Step2:
RRM-PCC, RRM-PRH, RLC, MAC, MEGCH, BSS traffic model and capacity (PS part).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 64/77
8 GLOSSARY
8.1 Abbreviations
- MAC: Medium Access Control (layer).
- DA: Dynamic Allocation (MAC mode).
- EDA: Extended Dynamic Allocation (MAC mode).
- USF: Uplink Status Flag.
- BP: Block Period.
- TBF: Temporary Block Flow.
- PTM: Packet Transfer Mode.
- DTM: Dual Transfer Mode.
- TBF: Temporary Block Flow.
- DL: Downlink.
- UL: Uplink.
- EUTM: Extended Uplink TBF Mode.
8.2 Terminology
Give, when necessary an unambiguous definition of terms and concepts used in the present document.
Reference to standards is allowed.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 65/77
9 ANNEXES
9.1 3GPP Standard Reminder
9.1.1 Extracts from 44.060 v6.14.0 Rel-6

9.1.1.1 Basic principle
The mobile station shall monitor the downlink PDCHs corresponding to (i.e. with the same timeslot number
as) its assigned uplink PDCHs starting with the lowest numbered PDCH, then the next lowest numbered
PDCH, etc., up to the one corresponding to the highest numbered assigned uplink PDCH.
[]
Whenever the mobile station detects an assigned USF value on an assigned PDCH, the mobile station shall
transmit either a single RLC/MAC block or a sequence of four RLC/MAC blocks on the same PDCH and all
higher numbered assigned PDCHs. The time relation between an uplink block, which the mobile station shall
use for transmission, and the occurrence of the USF value is defined in 3GPP TS 45.002. The number of
RLC/MAC blocks to transmit on each PDCH is controlled by the USF_GRANULARITY parameter
characterising the uplink TBF.
[]
The mobile station shall, during a block period in which it has been granted permission to transmit, monitor
for the assigned USF the downlink PDCHs corresponding to its assigned uplink PDCHs starting with the
lowest numbered assigned PDCH up to the highest numbered PDCH which the mobile is able to monitor,
taking into account the PDCHs allocated for transmission in the block period and the switching requirements
of the mobile station multislot class (see 3GPP TS 45.002).
If the network wishes to reduce the number of PDCHs allocated to a mobile station per block period, the
network may do so, provided that this is compatible with the mobile stations ability to monitor for the
assigned USF the downlink PDCH corresponding to the lowest numbered uplink PDCH in the new
allocation. Otherwise, the network shall not allocate any resources to that mobile station for one block period
following the block period with the higher number of PDCHs allocated.
During the block period where an uplink radio block is allocated on a PDCH via the polling mechanism (see
sub-clause 10.4.4), the mobile station shall monitor for the assigned USF on the downlink PDCHs
corresponding to its assigned uplink PDCHs starting with the lowest numbered assigned PDCH up to the
highest numbered PDCH which is feasible when taking into account the PDCHs allocated for transmission
in the block period and the switching requirements of the mobile station multislot class (see 3GPP TS
45.002).
9.1.1.2 PACCH operations
The mobile station shall attempt to decode every downlink RLC/MAC block on the lowest numbered timeslot
in the PDCH allocation. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC
control block, the mobile station shall attempt to interpret the message contained therein. If the message
addresses the mobile station, the mobile station shall act on the message.
The network shall transmit all PACCH messages on the PDCH carried on the lowest numbered timeslot in
the allocation. Additionally for the concurrent TBF case, the network may transmit PACCH messages on any
of the common timeslots assigned to the downlink and uplink PDCH allocation.
Whenever the mobile station detects an assigned USF value on any assigned PDCH, the mobile station may
transmit a PACCH block on the same PDCH in the next block period. The mobile station shall not transmit
an RLC data block in any uplink radio block allocated via the polling mechanism (see sub-clause 10.4.4).

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 66/77
[]
In the case of simultaneous uplink and downlink TBFs, the transmission of the polling response takes
precedence over the transmission of allocated uplink radio blocks.
[]
After receiving an RLC/MAC block containing a valid RRBP field the mobile station need not monitor the
USF in the associated downlink RLC/MAC block appearing just before the uplink block it shall transmit.
However, when Extended Dynamic Allocation or Shifted USF operation is used, the corresponding USF
monitoring procedure shall apply as described in sub-clause 8.1.1.2.1 and sub-clause 8.1.1.2.4 respectively.
[]
In case of simultaneous uplink and downlink TBFs and extended dynamic allocation (see sub-clause
8.1.1.2), the network may apply polling in downlink RLC data blocks only when sent on a PDCH common for
both reception and transmission (see 3GPP TS 45.002). A mobile station operating with extended dynamic
allocation need to respond to polling in downlink RLC data blocks only when received on a PDCH common
for both reception and transmission.
In A/Gb mode, an MS may be allocated several PDTCH/Us or PDTCH/Ds for one mobile originated or one
mobile terminated communication respectively. The total number of allocated PDTCH/Us and PDTCH/Ds
shall not exceed the total number of uplink and downlink timeslots that can be used by the MS per TDMA
frame (i.e., the parameter Sum specified in Annex B). In this context allocation refers to the list of PDCH
given in the assignment message and that may dynamically carry the PDTCHs for that specific MS.
[]
Note: In case of extended dynamic allocation, the MS needs to support USF monitoring on the downlink
PDCHs corresponding to (i.e. with the same timeslot number as) all assigned uplink PDCHs as defined in
3GPP TS 44.060.
The Packet Uplink Assignment, the Multiple TBF Uplink Assignment, Packet Timeslot Reconfigure and the
Multiple TBF Timeslot Reconfigure messages include the list of PDCHs and the corresponding USF value
per PDCH for each uplink TBF they allocate resources for. A unique TFI is allocated and is thereafter
included in each RLC Data and Control Block related to that Temporary Block Flow. The MS monitors the
USFs on the downlink PDCHs corresponding to (i.e. with the same timeslot number as) the uplink PDCHs
allocated for each TBF and transmits Radio blocks on those PDCHs which currently bear the USF value
reserved for the usage of the MS on each TBF.
If the resource assigned by the network in the case of extended dynamic allocation does not allow the
multislot MS (see 3GPP TS 45.002 [11]) to monitor the USF on all the assigned PDCHs, the following rules
shall apply:
- Whenever the MS receives its USF on one downlink PDCH (e.g. on timeslot 0 while timeslots 0, 2 and
3 were assigned), it shall consider the corresponding uplink block and all subsequent ones from the
list of assigned PDCHs as allocated (e.g. on 0, 2 and 3). Hence, if the network allocates a block to this
MS on an assigned PDCH, it shall also allocate blocks to this MS on all subsequent PDCHs in the list.
For each allocated block, the network shall set the USF to the value reserved for the usage of that
MS. These rules apply on a block period basis.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 67/77
- During block periods where it is transmitting, the MS shall monitor the USF on each downlink PDCH in
the list of PDCHs corresponding to the assigned uplink PDCHs, up to and including the last PDCH
that the MS is capable of receiving, according to the current uplink timeslot allocation and the
switching requirements of its multislot class (see 3GPP TS 45.002 [11]). This rule applies on a block
period basis. For example, if timeslots 0, 2 and 3 have been assigned and blocks are currently
allocated on timeslots 2 and 3, then during this block period a MS for which Tta=1 or Ttb=1 monitors
USF on timeslots 0, 2 and 3. If the reserved value of USF is found on timeslot 0, then the next
allocated blocks shall be on timeslots 0, 2 and 3 (thus increasing the timeslot allocation); if the
reserved value of USF is found on timeslot 2, then the next allocated blocks shall be on timeslots 2
and 3 (thus maintaining the timeslot allocation unchanged); if the reserved value of USF is found on
timeslot 3, then the next allocated block shall be on timeslot 3 (thus reducing the timeslot allocation by
one timeslot). And so on for the subsequent block periods. MSs for which Tta>1 or Ttb>1 are unable to
monitor the USF on timeslot 3; for these MSs, in order to reduce the timeslot allocation, the network
needs to leave at least one block period with no blocks allocated to the MS. Because each Radio
Block includes an identifier (TFI), all received Radio blocks are correctly associated with a particular
LLC frame and a particular MS, thus making the protocol highly robust. By altering the state of USF,
different PDCHs can be "opened" and "closed" dynamically for certain MSs thus providing a flexible
reservation mechanism. Additionally, packets with higher priority and pending control messages can
temporarily interrupt a data transmission from one MS.
- In the case of dual transfer mode, if the mobile station supports DTM high multislot class capability,
the network may assign uplink PDCHs whose corresponding downlink PDCH can never be monitored
by the mobile station because of the presence of the uplink dedicated channel. In this case, the mobile
station shall monitor only those downlink PDCHs that are feasible when taking into account the
position of the uplink dedicated channel and the switching requirements of its multislot class (see
3GPP TS 45.002 [11]).
If a multislot class type 1 MS indicates in the GPRS Multi Slot Class field the support of a multislot class for
which three or more uplink timeslots can be assigned, Extended Dynamic Allocation for GPRS shall be
implemented in the mobile station.
[]
If a multislot class type 1 MS indicates in the EGPRS Multi Slot Class field the support of a multislot class for
which three or more uplink timeslots can be assigned, Extended Dynamic Allocation for GPRS shall be
implemented in the mobile station.[]
If a multislot class type 1 MS indicates the support of a DTM GPRS multislot class for which three uplink
timeslots can be assigned, the mobile station shall support Extended Dynamic Allocation.
[]
If a multislot class type 1 MS indicates the support of a DTM EGPRS multislot class for which three uplink
timeslots can be assigned, the mobile station shall support Extended Dynamic Allocation.
9.1.4.1 Mobile Station Radio Access Capability Information Element

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 68/77
<MS RA capability value part : < MS RA capability value part struct >>
<spare bits>**; -- may be used for future enhancements
<MS RA capability value part struct >::= --recursive structure allows any number of Access technologies
{ { < Access Technology Type: bit (4) > exclude 1111
< Access capabilities : <Access capabilities struct> > }
| { < Access Technology Type: bit (4) == 1111 > -- structure adding Access technologies with same
capabilities
< Length : bit (7) > -- length in bits of list of Additional access technologies and spare bits
{ 1 < Additional access technologies: < Additional access technologies struct > > } ** 0
<spare bits>** } }
{ 0 | 1 <MS RA capability value part struct> } ;
< Additional access technologies struct > ::=

< Access Technology Type : bit (4) >
< GMSK Power Class : bit (3) >
< 8PSK Power Class : bit (2) > ;
< Access capabilities struct > ::=

< Length : bit (7) > -- length in bits of Content and spare bits
<Access capabilities : <Content>>
<spare bits>** ; -- expands to the indicated length
-- may be used for future enhancements
< Content > ::=

< RF Power Capability : bit (3) >
{ 0 | 1 <A5 bits : <A5 bits> > } -- zero means that the same values apply for parameters as in the immediately
preceding Access capabilities field within this IE
< ES IND : bit >
< PS : bit >
< VGCS : bit >
< VBS : bit >
{ 0 | 1 < Multislot capability : Multislot capability struct > } -- zero means that the same values for multislot
parameters as given in an earlier Access capabilities field within this IE apply also here
-- Additions in release 99
{ 0 | 1 < 8PSK Power Capability : bit(2) >} -- '1' also means 8PSK modulation capability in uplink.
< COMPACT Interference Measurement Capability : bit >
< Revision Level Indicator : bit >
< UMTS FDD Radio Access Technology Capability : bit > -- 3G RAT
< UMTS 3.84 Mcps TDD Radio Access Technology Capability : bit > -- 3G RAT
< CDMA 2000 Radio Access Technology Capability : bit > -- 3G RAT
< UMTS 1.28 Mcps TDD Radio Access Technology Capability: bit > -- 3G RAT
< GERAN Feature Package 1 : bit >
{ 0 | 1 < Extended DTM GPRS Multi Slot Class : bit(2) >
< Extended DTM EGPRS Multi Slot Class : bit(2) > }
< Modulation based multislot class support : bit >
{ 0 | 1 < High Multislot Capability : bit(2) > }
{ 0 | 1 < GERAN Iu Mode Capabilities > } -- '1' also means support of GERAN Iu mode
< GMSK Multislot Power Profile : bit (2) >
< 8-PSK Multislot Power Profile : bit (2) >
< Multiple TBF Capability : bit >

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 69/77
< Downlink Advanced Receiver Performance : bit(2) >

< Extended RLC/MAC Control Message Segmentation Capability : bit >

< DTM Enhancements Capability : bit >
{0|1 < DTM GPRS High Multi Slot Class : bit(3) >
{ 0 | 1 < DTM EGPRS High Multi Slot Class : bit(3) > } }
< PS Handover Capability : bit >;
-- error: struct too short, assume features do not exist
-- error: struct too long, ignore data and jump to next Access technology
9.2 List of the TSG GERAN documents concerning EDA and output power
reduction
See [1].
9.3 Example of uplink scheduling with one TBF in EDA mode
Examples_of_EDA_s
cheduling_v2.xls
9.4 Example of radio resource assignment in case of EDA
Examples_of_non-m
x-EDA_strategy_v1.xls
9.5 PDCH allocation reduction

In this section, let us call PDCH allocation recution the feature.
In the basic rules of EDA, the uplink allocation of a TBF in EDA mode needs to be cut off for (at least) one
block period for decreasing the number of time-slots allocated per block period (see Figure 1 for illustration)
whereas it is possible in some scenarios to reduce the allocation because the mobile station can listen to
further downlink timeslots.
This is for example the case for a multi-slot class 12 mobile station in 2+3 configuration:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 70/77
three assigned timeslots of the first TDMA frame (downlink and uplink):
The USF of the MS is set on the downlink

timeslot corresponding to the first assigned
uplink time-slot. 0 1 2 3 4 5 6 7
However, in this block period, the MS can
nevertheless listen to the downlink timeslot
corresponding to the second uplink Ttb Tra
assigned timeslot.
In this block period, the basic rules of EDA

does not allow to set the USF of the MS on
the downlink timeslot corresponding to the 0 1 2 3 4 5 6 7
second assigned uplink time-slot whereas
the MS can listen to it in this configuration
Ttb Tra
LEGEND:
Figure 29: PDCH allocation reduction issue
Recent clarifications (GP-052251 TSG GERAN#26) have been introduced so as to improve EDA operations
through PDCH allocation reduction capabilities. This feature is mandatory in Rel-6 onwards. However, the
fact to not implement it cannot lead to inter-operability issues.
Thus, allocation can be reduced in some scenarios. Taking again the example above, the following figure
illustrates this capability for a Rel-6 multi-slot class 12 in 2+3 configuration:

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 71/77
three assigned timeslots of the first TDMA frame (downlink and uplink):
0 1 2 3 4 5 6 7
Ttb Tra
The USF is set on the second timeslot
so that the allocation is reduced by one
timeslot. Note that the USF could not be 0 1 2 3 4 5 6 7
set on the third timeslot.
Ttb Tra
The USF is set on the third timeslot so
that the allocation is reduced by one
timeslot. 0 1 2 3 4 5 6 7
Ttb Tra
The USF is set on the first timeslot to re-

increase the allocation to three timeslots.
0 1 2 3 4 5 6 7
Ttb Tra
LEGEND:
Figure 30: PDCH allocation reduction capability
It is expected that some mobile stations supporting EDA and compliant with an older release than Rel-6 will
support this feature (PDCH allocation reduction). Thus, three categories of mobile stations (supporting EDA)
are expected:
- Mobile stations compliant with Rel-6 onwards. For these mobile stations, this improvement is
mandatory. Thus dedicated scheduling with allocation reduction capabilities might be applied for
such mobile stations.
- Mobile stations compliant with an older release than Rel-6 but aligned with Rel-6 implementation in
terms of EDA implementation thus supporting the feature.
- Compliant with an older release than Rel-6 but not supporting the feature.
For the two last categories, the network should detect for each MS the fact that it supports (or not) the
feature by looking if it can transmit blocks in Block Periods where a reduction has been triggered (this is
especially difficult for GPRS MSs). Indeed, no dedicated signalling has been defined in the standard to know
if a MS supports this feature or not.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 72/77
9.5.1 B10 context

9.5.1.1 Application domain
Considering multi-slot classes 3, 11 and 12, this improvement would be useful only for multi-slot class 11
and 12 in case of three assigned uplink timeslots (0+3, 1+3 or 2+3 configurations): it allows the reduction of
the PDCH allocation from one block period to the following one by step of one PDCH (i.e. from three
timeslots to two timeslots, and from two timeslots to one timeslot).
9.5.1.2 Interest
Due to the non-multiplexed-EDA strategy (see section 3.1.1.3.1), the interest of this improvement is limited
to the few following cases:
- Commanded MCS increase. Every 12*20ms=240ms at the maximum. Thus that should happen
rarely.
- In block periods in which polling answer is awaited and if transmission resources are enough to
convey 2 RB (respectively 1) but not enough to convey 2 RB+1 polling answer (in CS1) (respectively
1RB+1 polling answer).
- In the short transition phases in which the non-multiplexed-EDA strategy cannot be guaranteed.
9.5.1.3 Possible implementations
The algorithm proposed in this SFD does not allow reducing the allocation to simplify the implementation
(see section 3.1.2.3.2.2.1.2). It is based on the basic rules of EDA (the Last_PDCH_allocated variable in the
algorithm allows to guaranty the constraint from one block period to the next one).
To support the "PDCH allocation redcution", MAC should be able to dectect which mobile stations support
this capability. That may be performed by assuming that the mobile station supports the improvement, and
by identifying the capability (or the un-capability) of the mobile station to send radio blocks in block period in
which an allocation reduction has been experienced.
If a mobile station is supposed to support the improvement, the two simplest ways to manage this
improvement are:
- To apply at each BP start Last_PDCH_allocated=MIN(Last_PDCH_allocated+1;highest PDCH

assigned) but only in case of UL TBF with three assigned timeslots. However, in terms of evolutivity,
it seems to be not very suitable.
- To apply at each BP start Last_PDCH_allocated=MAX(Last_PDCH_allocated, highest PDCH

assigned to the downlink TBF if any) at each BP start thanks to the MS context. Indeed, if there is a
downlink TBF (belonging to the same MS) on a PDCH. That means that the MS will always listen to
the downlink PDCH. However, this solution allows only a reduction from three timeslots to two
timeslots (but not from two to one).
9.5.1.4 Decision
Taking into account the low interest and the difficult detection (although the strict support of PDCH allocation
reduction at MAC level seems to be easy), the best way seems to be not to support that feature.
9.6 Output power reduction
9.6.1 R99 and Rel-4

9.6.1.1 A simple approach
The 3GPP solution specifies a heuristic rule for reducing maximum mobile transmitter output power based
on the multislot assignment made by the network. There is no modification of protocols or signalling
specifications.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 73/77
9.6.1.2 Extract of the 05.05 (respectively 45.005 for Rel-4)

In order to manage mobile terminal heat dissipation resulting from transmission on multiple uplink timeslots,
the mobile station shall reduce its maximum output power by the following values on a per-assignment
basis:
Number of Permissible nominal
timeslots in uplink reduction of maximum
assignment output power, (dB)
1 0
2 0 to 3,0
3 1,8 to 4,8
4 3,0 to 6,0
The supported maximum output power for each number of uplink timeslots shall form a monotonic
sequence. The maximum reduction of maximum output power from an allocation of n uplink timeslots to an
allocation of n+1 uplink timeslots shall be equal to the difference of maximum permissible nominal reduction
of maximum output power for the corresponding number of timeslots, as defined in the table above.
As an exception, in case of a multislot uplink assignment, the first power control step down from the
maximum output power is allowed to be in the range 02 dB.
In case the MS transmits on more uplink slots than assigned (e.g. due to a polling response, see 3GPP TS
04.60), the MS may reduce uplink power as above for a multislot uplink configuration but as a function of the
number of active uplink slots on a TDMA frame basis.
9.6.1.3 Expected gain of EDA for a mobile station alone on its PDCH
The throughput gain brought by the EDA mode for a single mobile station is roughly a trade-off between the
throughput gain due to the higher number of timeslots used and the throughput loss due to the output power
reduction.
The following curves show a estimation of the gain brought by the EDA mode as a function of the SIR
(Signal to Interference Ratio) in case APD=0dB and for the following radio channel profiles: TU03_nofh_IR
and TU50_nofh_IR (radio link performance curves from R&I Stuttgart). Ideal link adaptation is assumed.
This gain is computed by comparing a nominal case and a second case with more timeslots but with output
power reduction (-1.8dB from 2 to 3 timeslots, and 3dB from 2 to 4 timeslots):

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 74/77
Throughput gain from 2 to 3 timeslots Throughput gain from 2 to 4 timeslots
50% 100%
40%
80%
30%
60%
20%
40%
10%
20%
0%
0 10 20 30 40
-10% 0%
0 10 20 30 40
-20% -20%
(C/I)dB (C/I)dB
TU03_nofh_IR TU50_nofh_IR TU03_nofh_IR TU50_nofh_IR
Figure 31: expected gain of EDA in case of power reduction

9.6.1.4 Impacts
The way the output power reduction has been specified (constant power reduction based on the number of
timeslots assigned):
- It has no impact on the link adaptation except in case of TBF re-configuration (Indeed, in case of re-
configuration, the last (M)CS is used as init (M)CS for the re-configured TBF. However, these
impacts should not be significant).
- The network may have knowledge of the mobile terminals maximum output power capability before
making an uplink assignment, and may subsequently use this knowledge to apply an offset value
against its mobile station power control range. This might be used if GPRS uplink power control is
implemented in B10.
Due to the characteristics of the ideal throughput curve slope, the gain of the EDA mode decreases when
the mean radio quality decreases what may jeopardize some PS transfers and/or CS calls (in case of DTM)
that are in borderline radio conditions when switching to EDA mode (e.g. at border cell). In this kind of
scenario, the power control offset correction is a priori not helpful because there are a lot of chances to be
already at the maximum output power.
The solution would be to avoid switching to configurations with high numbers of uplink timeslots for mobile
stations in bad radio conditions.
To note that this output power reduction might already happen in B9 when switching from a configuration
with one uplink timeslot to a configuration with two uplink timeslots.
9.6.2 Rel-5 and beyond
A more advanced approach for Rel-5 and beyond has been specified. This solution adds a signalling
technique of informing the network of the incremental control over maximum output power by the mobile
terminal. The multislot power profile of the mobile station is indicated in the MS Classmark 3 IE.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 75/77
9.6.2.1 Extract of the 45.005 Rel-5

In order to manage mobile terminal heat dissipation resulting from transmission on multiple uplink timeslots,
the mobile station may reduce its maximum output power by up to the following values:
Number of Permissible nominal

timeslots in uplink reduction of maximum
assignment output power, (dB)
1 0
2 3,0
3 4,8
4 6,0
5 7,0
6 7,8
7 8,5
8 9,0
Table 4: permissible nominal power reduction / Rel-5
The actual supported maximum output power shall be in the range indicated by the parameters
XXX_MULTISLOT_POWER_PROFILE (See 3GPP TS 24.008) for n allocated uplink timeslots:
a MS maximum output power min(MAX_PWR, a + b)
Where:
a = min (MAX_PWR, MAX_PWR + XXX_MULTISLOT_POWER_PROFILE 10log(n));
MAX_PWR equals to the MS maximum output power according to the relevant power class;
XXX_MULTISLOT_POWER_PROFILE refers either to GMSK_MULTISLOT_POWER PROFILE or

8-PSK_MULTISLOT_POWER_PROFILE depending on the modulation type concerned, and
XXX_MULTISLOT_POWER_PROFILE 0 = 0 dB;
XXX_MULTISLOT_POWER_PROFILE 3 = 6 dB.
For DCS 1800 and PCS 1900 frequency bands b = 3 dB, for all other bands b = 2 dB.
The supported maximum output power for each number of uplink timeslots shall form a monotonic
sequence. The maximum reduction of maximum output power from an allocation of n uplink timeslots to an
allocation of n+1 uplink timeslots shall be equal to the difference of maximum permissible nominal reduction
of maximum output power for the corresponding number of timeslots, as defined in the table above.
As an exception, in case of a multislot uplink assignment, the first power control step down from the
maximum output power is allowed to be in the range 02 dB.
In case the MS transmits on more uplink slots than assigned (e.g. due to a polling response, see 3GPP TS
44.060), the MS may reduce uplink power as above for a multislot uplink configuration but as a function of
the number of active uplink slots on a TDMA frame basis.
9.7 Overview of impacts on ping performances (compared to B9)

Warning: this part takes into account only the changes introduced by the EDA feature in B10 and thus does
not take into account changes brought by other features.

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 76/77
9.7.1 Short ping performances

Short ping performances are not impacted especially since the number of assigned PDCHs in downlink and
in uplink has quasi no impact on the time to transfer the data on the air interface (indeed a few radio blocks
at the maximum are needed to transmit the request and the answer).
9.7.2 Long ping performances
Long ping 15 s performances are not impacted.
Long ping 0s performances (with or without extended uplink TBF mode) are not impacted thanks to the
N_UL_BIAS_FOR_EDA mechanism provided that this parameter is correctly tuned.
Without this mechanism, long ping 0 s performances with extended uplink TBF mode would have been
significantly badly impacted. In B9, regular changes between uplink and downlink bias are observed in such
scenarios. Thus, the configuration used e.g. for a multislot lass 12 changes between 3+2 and 4+1.
If N_UL_BIAS_FOR_EDA is not correctly tuned, the degradation with the proposed solution is due to the
transfer time of the data on the air interface (downlink transfer plus uplink transfer time). The following table
compares roughly the time needed to transfer request and answer ping messages (D size) considering that
the throughput per radio block is the same in uplink and in downlink and not taking into account the ping
improvements introduced in B10:
Bias Downlink Uplink
Release B9 B10 B9 B10
Configuration 4+1 4+1 3+2 1+4
Uplink transfer time D/1 D/1 D/2 D/4

needed for the ping
request
Downlink transfer D/4 D/4 D/3 D/1

time needed for the
ping answer
Total transfer time 5D/4 5D/4 5D/6 5D/4

on the air interface
Difference (B10 0% +50%

compared to B9)
Table 5: comparison of cumulated transfer time on the air interface (only) between B9 and B10 with
an uncorrect tuning of the N_UL_BIAS_FOR_EDA parameter
END OF DOCUMENT

0025_02.doc
30/03/2007
3BK 10204 0025 DTZZA 77/77

Extended Dynamic Allocation (EDA)

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Extended Dynamic Allocation (EDA)

Încărcat de

Drepturi de autor:

Formate disponibile

not permitted without written authorization from Evolium.

All rights reserved. Passing on and copying of this

Site EVOLIUM SAS

Originators Extended Dynamic Allocation (EDA)

System : ALCATEL GSM BSS

Ed. 01 Proposal 05 <2006/02/08> No comment received.

Ed. 02 Proposal 01 <2007/03/29> No comment received.

ED 02 RELEASED Extended Dynamic Allocation

Ed. 01 Proposal 02 <2005/11/18> Changes compared to proposal 1:

Ed. 01 Proposal 03 <2005/12/09> Some editorial changes.

ED 02 RELEASED Extended Dynamic Allocation

Ed. 01 Proposal 04 <2006/01/11> Some editoral changes.

Support of DTM multislot class 11.

Correction of the EN_EDA OMC-R parameter, introduction of new

Clarifications about the reading of the MS release and about EDA

Clarifications about the assignment strategy. An annex about

Introduction of the mechanism based on the

Validation part completed.

Introduction of counters and indicators.

The annex about uplink scheduling examples has been updated

Impacts on step 2 MEGCH and step 2 BSS traffic model capacity

Ed. 01 Proposal 05 <2006/01/31> A few editorial changes.

Mechanism based on the N_UL_BIAS_FOR_EDA changed.

The N_UL_BIAS_FOR_EDA parameter is changed from constant

EDA is not supported in extended cells.

Some changes and clarifications in the RRM-PCC and RRM-PRH

Footnotes are now real footnotes (contents have not been

ED 02 RELEASED Extended Dynamic Allocation

- It has been added that the feature will be enhanced by the

- The issues about BSIC decoding have been clarified.

- One reallocation criterion in case of GPRS UL TBF in

- The checking about Extended and non-Evolium cells is

- The policy for transmission of Packet PDCH release

- It has been clarified that, when playing a T3 TBF

- It has been clarified that, in rare scenarios, an UL TBF can

- Various updates and clarifications about counters and

- Various minor updates and clarifications.

Ed. 02 Released <2007/03/29> A few syntax corrections.

ED 02 RELEASED Extended Dynamic Allocation

ED 02 RELEASED Extended Dynamic Allocation

3.1.1.3.2 Making ............................................................................................................... 31

ED 02 RELEASED Extended Dynamic Allocation

3.2.3.2 Parameters modified.................................................................................................... 54

ED 02 RELEASED Extended Dynamic Allocation

9.1.4.1 Mobile Station Radio Access Capability Information Element..................................... 68

INTERNAL REFERENCED DOCUMENTS

[1] SYT memo 205151 B10 DR0 - EDA

[3] 3GPP TS 44.060 RLC/MAC protocol (Rel-6)

[6] 3GPP TS 24.008 Core network protocols; stage 3 (Rel-6)

[8] 3GPP TS 51.010-1 Mobile Station Conformance Specification Part 1

ED 02 RELEASED Extended Dynamic Allocation

[5] 3BK 10204 0026 DTZZA RLC/MAC new scheduling algorithm

[6] 3BKA55CBR195440 (RFD) Support of the 30-33 Multislots classes

3GPP CR nb Rev Title Author Accepted?

44.060 684 / GP- Revised and Clarification of EDA operation Alcatel, Y

ED 02 RELEASED Extended Dynamic Allocation

1.2 Document Structure

The section 2 of this document presents:

The section 4 recaps the impacts for each subsystem.

The section 5 addresses the performance and system dimensioning concerns.

The section 7 is a sum up of the system impacts.

The section 8 contains the glossary of the present document.

1.3 Definitions and pre-requisite

1.3.1 What is the EDA mode?