Egprs Is 1.4.0

ENHANCED GPRS IN PCU S10.
5 ED
Implementation Specification
Nokia Networks
Company Confidential
_____________________________________________________________________________________
Version Author/Checked by Approved by Feature Number Pages

DRAFT 1.4.0 / 09744 82
_____________________________________________________________________________________
EGPRS IN PCU 2 (82)
NET/IMN Implementation Specification 1.4.0
Jouni Marjamki 14 Jun 2002 COMPANY CONFIDENTIAL
Change Record
Issue Date Chapters Description of Change
affected
Draft 0.0.0 2.6.2000 All Initial issue
Draft 0.0.1 9.6.2000 All Modified after internal review

Draft 0.1.0 19.6.2000 4,5 Modified after RAS review, Egprs TBF creation chapters moved to PBCCCH IS
documentation
CHM specific chapters modified and updated
Draft 0.2.0 23.8.2000 4 CHM territory updated modified

Egprs Packet Transfer Link Adaptation chapters updated
27.9.2000 8.1.1 New PCU counters added
04.10.2000 8.1.2 Coding Scheme counters updated
Draft 0.2.1 06.10.2000 4.3.2 MAC Uplink control message interface modification proposed by S.Aaltonen
10.10.2000 4.9.1 RLC Window size use
Draft 0.3.0 10.10.2000 Version for review updated
Draft 0.3.1 11.10.2000 4 TBF resource change to MS removal proposed by P. Gronberg

12.10.2000 4.1 4.15 Egprs CHM modified
16.10.2000 4.17,5.1,5.2, Chapters removed
26.10.2000 5.3 New Egprs message definitions added
6.3 EGPRS Specific ETSI references added
6.3.18 Internal algorithms and constants explained
11.2 ETSI CR requests added
Draft 0.4.0 26.10.2000 11.4 Version for review updated
Draft 0.4.1 07.11.2000 4.8 Territory procedures modified

4.13.2 Territory balance added
4.3.4 Egprs measurement request added
4.8.2.1 Two phase access
4.8.2.2 Single block allocation
4.8.2.3 Rx-lev measurement use in BTS selection
4.13 BTS Timeslot reallocation activation
4.14.1 Territory upgrade/downgrade..................................................................................................................
4.14.2 Territory balance
5.4 Downlink interface to BTS
Draft 0.4.2 Link Adaptation operator parameters updated

4.6 Chapter indendation changed
4.10.1.5 MSC use and Egprs RLC block selection added
4.7.2 BCCH TSL 7 use added
4.10.7 RLC Window size use
4.11 Packet Data Handling interface modified
4.6.2.3 CHM Reallocation procedures added
Draft 0.4.3 13.12.00 Version for review updated

6.3 Interface modifications
4.6.1.1 Downlink
4.6.1.2 Uplink
4.6.2.2 Selecting BTS in Reallocation
4.8 CHM / MAC parameters
4.10.4.4 MS out of Memory modified for LA
4.11.1 Downlink interface
Draft 0.4.4 15.01.2001 Version for review
19.01.2001 6.3 CHM allocation interfaces, MAC->RLC interface bts_id added. Proposed by S.Aaltonen
4.10.4.4 MS Out of memory updated
11.3.1 Remarks, MS out of memory solution
4.10.3 Downlink retransmission procedure updated for first-next polling method
Draft 0.4.5 13.02.2001 11.5 Open items chapter added
Author Approved by
344727344.doc Jouni Marjamki
EGPRS IN PCU 3 (82)
1.0.0 16.02.2001 4.6.1.1 BTS selection chapters modified

4.6.1.2
4.6.2.2
1.1.0 8.3.2001 4.7.3 Territory balance modified

4.1 Interfaces updated to use Netlib
4.10.1.1 Link adaptation updated to use BEP values in MAC control messages
1.2.0 Interfaces to BSSGP modified
1.3.0 12.10.2001 4.11.1 BTS retransmit functionality modified, new Metro document 0.0.6 received
Draft 1.4.0 14 Jun 2002 All Updated

Jouni Marjamki
Author Approved by
EGPRS IN PCU 4 (82)
Contents
1. Introduction................................................................................................................................... 8
1.1 Abbreviations.......................................................................................................................... 8
1.2 References............................................................................................................................. 9
2. Architecture Specification........................................................................................................... 10
3. Selection of the Architecture Alternative......................................................................................11
4. Implementation Description........................................................................................................ 12
4.1 EGPRS interface to BSSGP................................................................................................12
4.2 Message encoding and decoding........................................................................................12
4.3 EGPRS Packet Control Messages.......................................................................................12
4.4 Scheduling........................................................................................................................... 13
4.4.1 MS synchronization.......................................................................................................13
4.4.2 GPRS and EGPRS TBF multiplexing............................................................................13
4.5 MS RX-lev update................................................................................................................ 13
4.5.1 Downlink........................................................................................................................ 13
4.5.2 Uplink............................................................................................................................ 13
4.6 GPRS/EGPRS BTS selection..............................................................................................13
4.6.1 Initial BTS selection.......................................................................................................14
4.6.2 Reallocation BTS selection...........................................................................................16
4.6.3 Initial BTS Selection......................................................................................................20
4.6.3.1 Downlink.................................................................................................................... 20
4.6.3.2 Uplink......................................................................................................................... 20
4.6.4 Reallocation of a TBF....................................................................................................20
4.6.4.1 Reallocation activation...............................................................................................20
4.6.4.2 Selecting BTS in reallocation.....................................................................................20
4.6.4.3 CHM Reallocation procedures...................................................................................20
4.6.4.4 TBF Rx-lev Reallocation............................................................................................20
4.6.4.5 BTS Load Reallocation..............................................................................................20
4.6.4.6 GPRS TBF in EGPRS territory reallocation...............................................................20
4.6.4.7 BTS Timeslot reallocation..........................................................................................20
4.7 Territory procedures.............................................................................................................. 20
4.7.1 Territory upgrade/downgrade........................................................................................20
4.7.2 BCCH TSL 7 use........................................................................................................... 20
4.7.3 Territory balance update................................................................................................20
4.8 Multi BCF and Common BCCH............................................................................................20
4.9 EGPRS Packet transfer........................................................................................................20
4.9.1 Introduction to RLC layer operational modes................................................................20
4.9.2 Introduction to Retransmission Control.........................................................................21
4.9.3 Introduction to MCS Selection.......................................................................................21
4.9.3.1 Introduction to MCS Selection in Retransmission......................................................22
4.9.4 Introduction to MCSs.....................................................................................................22
4.9.5 Introduction to RLC/MAC header types.........................................................................24
4.10 EGPRS TBF establishment, uplink and downlink.............................................................26
4.11 EGPRS TBF release, uplink and downlink.......................................................................26
4.12 EGPRS RLC Window size, uplink and downlink..............................................................26
4.13 EGPRS downlink packet transfer.....................................................................................27
4.13.1 Downlink MCS selection phases................................................................................27
4.13.1.1 Data block and MCS prediction phase by RLC.........................................................28
4.13.1.2 MCS limiting phase by CHM......................................................................................28
4.13.1.3 Dynamic Abis allocation phase by DAM....................................................................29
4.13.1.4 Final data block and MCS selection phase by RLC...................................................29
Author Approved by
EGPRS IN PCU 5 (82)
4.13.2 Data block selection...................................................................................................29

4.13.3 MCS selection for data block.....................................................................................30
4.13.3.1 Initial transmission (new block)..................................................................................30
4.13.3.2 Retransmission in RLC acknowledged mode (NACKed or PENDING block)............31
4.13.3.3 Retransmission MCS of last block in RLC unacknowledged mode...........................32
4.13.4 RLC radio block construction.....................................................................................32
4.13.4.1 RLC/MAC header construction..................................................................................32
4.13.4.2 RLC data block construction......................................................................................32
4.13.5 Downlink acknowledgement procedure.....................................................................33
4.13.5.1 Downlink Acknowledged mode..................................................................................33
4.13.5.2 Downlink Unacknowledged mode..............................................................................33
4.13.5.3 EGPRS Packet downlink ack/nack polling.................................................................34
4.13.5.4 Interpretation of EGPRS Packet Downlink Ack/Nack message.................................35
4.13.5.5 Time stamping of sent data blocks............................................................................38
4.13.6 Delayed release of downlink EGPRS TBF.................................................................39
4.14 EGPRS downlink retransmission using BTS buffering.....................................................39
4.14.1 Introduction to downlink pointer retransmission.........................................................39
4.14.2 Implementation description of downlink pointer retransmission.................................40
4.14.2.1 Basic function............................................................................................................ 40
4.14.2.2 Half block indication...................................................................................................41
4.14.2.3 BPN overflow............................................................................................................. 41
4.14.2.4 TRX reallocation........................................................................................................ 42
4.14.2.5 Abis transmission error..............................................................................................42
4.15 EGPRS uplink packet transfer..........................................................................................43
4.15.1 Uplink commanded MCS selection............................................................................43
4.15.1.1 Uplink Dynamic Abis allocation..................................................................................44
4.15.2 LLC PDU assembly...................................................................................................44
4.15.3 Uplink acknowledgement procedure..........................................................................45
4.15.3.1 Uplink Acknowledge mode.........................................................................................45
4.15.3.2 Uplink Unacknowledged mode..................................................................................45
4.15.3.3 Packet uplink ack/nack sending................................................................................45
4.15.3.4 Packet uplink Ack/Nack message content.................................................................46
4.15.4 Invalid content in uplink data block............................................................................46
4.15.5 ITFI............................................................................................................................ 46
4.16 EGPRS Link Adaptation....................................................................................................46
4.16.2 Downlink Link Adaptation...........................................................................................48
4.16.3 Uplink Link Adaptation...............................................................................................49
4.16.4 Uplink Averaging........................................................................................................49
4.16.4.1 Decoding L1 data......................................................................................................50
4.16.4.2 Averaging................................................................................................................... 51
4.16.4.3 BEP value calculating................................................................................................52
4.16.5 Link Adaptation algorithm..........................................................................................54
4.16.5.1 Handling of missing BEP values of one modulation, ack/unack mode......................55
4.16.5.2 Handling of user define offsets, ack/unack mode......................................................55
4.16.5.3 MCS selection based on BLER limits, ack/unack mode............................................56
4.16.5.4 Optimal MCS selection for initial transmission, ack mode.........................................56
4.16.5.5 MCS selection downlink for retransmission, ack mode..............................................58
4.16.5.6 MCS reducing for downlink transmission if MS out of memory (IR), ack mode.........58
4.16.5.7 MCS limiting for CX3.2 BTS software........................................................................59
4.17 Packet Data Handling Interface........................................................................................59
4.18 Dependencies on other features......................................................................................60
4.19 Capasity............................................................................................................................ 60
Author Approved by
EGPRS IN PCU 6 (82)
5. Scenarios.................................................................................................................................... 61
5.1 Uplink link adaptation........................................................................................................... 61
5.2 Downlink link adaptation.......................................................................................................62
5.3 Scheduling, MCS selection and Dynamic Abis allocation.....................................................63
6. Service Descriptions................................................................................................................... 65
6.1 New services........................................................................................................................ 65
6.1.1 Services between CHM and RLC..................................................................................65
6.1.1.1 rlc_get_ul_tbf_mcs__r...............................................................................................65
6.1.1.2 rlc_get_dl_tbf_mcs__r...............................................................................................65
6.1.1.3 Rlc_get_dl_rlc_data_items__r...................................................................................65
6.1.2 Services between CHM and DAM.................................................................................65
6.1.2.1 Dam_allocate_ul_items_req__r.................................................................................65
6.1.2.2 Dam_allocate_dl_items_req__r.................................................................................66
6.1.2.3 Dam_set_dynabis_c_bits_req__r..............................................................................66
6.2 New interfaces...................................................................................................................... 67
6.3 New messages..................................................................................................................... 67
6.4 Interface modifications......................................................................................................... 67
6.5 EGPRS message definitions................................................................................................67
6.5.1 Starting sequence number SSN....................................................................................67
6.5.2 Determination of SSN...................................................................................................67
6.5.3 Received block bitmap RBB..........................................................................................67
6.5.4 Block sequence EGPRS BSN number..........................................................................67
6.5.5 Two RLC Radio Block Sequence number.....................................................................67
6.5.6 Split Block Indicator.......................................................................................................67
6.5.7 More (M) bit................................................................................................................... 67
6.5.8 Length Indicator LI........................................................................................................ 67
6.5.9 Receive state array V(N) in EGPRS TBF......................................................................67
6.5.10 Acknowledge State Array V(B) for EGPRS TBF Mode..............................................67
6.5.11 RLC/MAC control blocks............................................................................................67
6.5.12 EGPRS RLC data blocks and RLC/MAC headers.....................................................67
6.5.13 Downlink RLC/MAC control block..............................................................................67
6.5.14 Uplink RLC/MAC control block...................................................................................68
6.5.15 EGPRS Downlink RLC/MAC headers........................................................................68
6.5.15.1 Header type 1: header for MCS-7, MCS-8 and MCS-9.............................................68
6.5.15.2 Header type 2: header for MCS-6 and MCS-5..........................................................68
6.5.15.3 Header type 3: header for MCS-4, MCS-3, MCS-2 and MCS-1................................68
6.5.16 EGPRS Downlink RLC data block.............................................................................68
6.5.17 EGPRS Uplink RLC/MAC headers............................................................................68
6.5.17.1 Header type 1: header for MCS-7, MCS-8 and MCS-9.............................................68
6.5.17.2 Header type 2 : header for MCS-6 and MCS-5.........................................................68
6.5.17.3 Header type 3 : header for MCS-4, MCS-3, MCS-2 and MCS-1...............................68
6.5.18 EGPRS Uplink RLC data block..................................................................................68
6.5.19 RLC Window size for Egprs.......................................................................................68
6.5.20 RLC receive window..................................................................................................68
6.5.21 Bitmap generation.....................................................................................................68
6.5.22 Egprs editorial clarifications.......................................................................................68
6.5.23 EGPRS Specific ETSI references..............................................................................68
6.5.23.1 New messages [Kangas]...........................................................................................68
6.5.23.2 Changes on messages..............................................................................................68
6.5.23.3 New information elements.........................................................................................68
6.5.23.4 Changes on information elements.............................................................................68
7. Handling of Exception Conditions...............................................................................................69
Author Approved by
EGPRS IN PCU 7 (82)
7.1 Alarm Descriptions............................................................................................................... 69

8. Counter and Observation Descriptions.......................................................................................70
8.1 EGPRS specific statistics.....................................................................................................70
8.1.1 PCU counters................................................................................................................ 70
8.1.2 Coding Scheme counters..............................................................................................70
9. File and Data structure Descriptions...........................................................................................71
9.1 New datatypes / ABATOR level............................................................................................71
9.1.1 mcs__t........................................................................................................................... 71
9.1.2 edge_trx_sch_data_ul__t..............................................................................................72
9.1.3 edge_trx_sch_data_dl__t..............................................................................................72
10. Operator Interface................................................................................................................ 73
10.1 Operator parameters........................................................................................................ 73
10.1.1 CHM / MAC parameters.............................................................................................73
11. Installing and testing............................................................................................................. 75
11.1 Configuration requirements..............................................................................................75
11.2 Implementation instructions..............................................................................................75
11.2.1 Measurement mode...................................................................................................75
11.2.2 Reallocation parameters............................................................................................75
11.3 User operations and parameters used.............................................................................75
11.4 Remarks............................................................................................................................ 75
11.4.1 Documentation change requests to ETSI..................................................................75
11.4.2 ITU T.4 compression table........................................................................................75
11.4.3 Performance notes....................................................................................................75
11.4.3.1 Timer use in reallocation activation............................................................................75
11.5 Open items....................................................................................................................... 75
11.5.1 BTS selection in segment..........................................................................................75
11.5.2 Uplink Rx-lev reallocation..........................................................................................75
11.5.3 Uplink initial MCS.......................................................................................................75
11.6 Testing and verification.....................................................................................................75
Author Approved by
EGPRS IN PCU 8 (82)
1. INTRODUCTION
EGPRS is an extension feature to GPRS packet transfer with new radio channel
modulation and data transfer rates. The feature is operator controlled and has lower
priority to CS traffic and load. EGPRS packet service load is shared utilizing territory
method between CS and packet data, Enhanced GPRS 1.2, [Kangas].
Enhanced GRPS feature is optional and used together in parallel with current GPRS
functionality.
Red texts unclear things
1.1 Abbreviations
CHM Channel Management, CHM program block
CS Circuit Switched
CCU Channel Coded Unit
BEP Bit Error Probability
TBF Temporary Block Flow. There can be one uplink and one downlink TBF at a
time for a MS.
TLLI Temporary Logical Link Identity. Identifies the MS.

Can be changed during the existence of a TBF.
LLC Logical Link Layer
MAC Medium Access Control, MAC program block
RLC Radio Link Control, RLC program block
RLC Radio Block RLC data with RLC/MAC header included
RLC Data Block RLC data without RLC/MAC header
PFH Packet Frame Handler, PFH program block
ITFI Internal Temporary Flow Identifier
TFI Temporary Flow Identifier.Assigned for TBF by the network.

Unique among concurrent (=same channel, simultaneous) TBFs in each
direction. Can be changed during the existence of a TBF.
TBF_ID TBF identifier inside PCU. Unique among all TBFs of a PCU in each
direction.
Does not change during the existence of a TBF.
Author Approved by
EGPRS IN PCU 9 (82)
More complete glossary is described in PCU S10 Glossary
1.2 References
[05.08]
[PBCCHIS] PBCCH/PCCCH IN PCU, Implementation Specification,

ver 1.1.1, Mika Rantanen
[Kangas] Enhanced GPRS Requirement specification,

ver1.2.0, Arto Kangas
[DXEGPRS] PBCCH/PCCCH in BSC & EGPRS in DX, Implementation Specification,

ver 1.7-0, Harri Tervonen, Miikka Mielonen, Tarja Vihanti:
[DAM IS] Dynamic Abis in PCU S10 Implementation Specification,

ver 1.03, Tommi Palonen
[04.60] 04.60 ver 8.10-0
[CX3.2] CX3 BTS SW, CX3.2 CHDSP SW Incremental Redundancy,

Functional Specification, H6S S601D71E, 0.1.0, Eric Belote
[AbisL1] GPRS/EGPRS Abis L1, Interface Specification,

H6S 071290AE, ver 2.0.1, Pasi Ylinen
[PCUIF] PCU S10 Interface document
[CX3.2] CX3.2 CHDSP SW, INCREMENTAL REDUNDANCY FUNCTIONAL

SPECIFICATION, ver 0.0.10, Eric Belote
[RLCS9DD] 09774_3 GPRS PCU RLC SW Design Specification,

v0.0.8, Pasi Seittenranta
[RLCS9IS] GPRS PCU RLC, Implementation Specification,

v1.5.0, Pasi Seittenranta
[RLCWin2] Simulation results for 8-TS EGPRS mobile, Petri Grnberg, RLCWin2.pdf, 22
May 2002
[S10LA] S10 Link Adaptation: Algorithm and Parameters,

M.Moisio, J.Sipola 24.11.2000
Author Approved by
EGPRS IN PCU 10 (82)
2. ARCHITECTURE SPECIFICATION
DX 200
GUPDAT GUPDAT
PUBDAT PUBDAT
ABIPRB PXRECE, PXSEND FRCMAN
RRMPRB ABIPRB
RC0PRB RC0PRB GBADMI FRADMI
PCU telecom
ABATOR GBHTOR
CHM RLC
RELAY BSSGP
PSWRRM SIGNALING BVC
MS MS
DL TBF UL TBF
CHANNEL NS
PSCH
ALLOCATOR LOAD SHARING
MAC/PABI
COMMON
MS NSVC
CTRL
SCHEDULER
FRHTOR
PFH
DAM DSP TRX FR
PVC
DSP data PCU

ABIS messaging
Pool
Pool
netFrames
DSP driver HDLC driver

DSP O&M
messaging DSP SW
Gb
Abis interface
interface
Figure 1 PCU S10 telecom SW architecture. DAM is new block in the S10 and it is needed for
EGPRS. Other red colored blocks are modified for EGPRS. This document does not cover DAM, DSP
driver and DSP implementation.
Author Approved by
3. SELECTION OF THE ARCHITECTURE ALTERNATIVE
Author Approved by
4. IMPLEMENTATION DESCRIPTION
4.1 EGPRS interface to BSSGP
Egprs RLC data block can have larger data content than Gprs. Uplink interface from RLC
to LLC protocol layer shall be based on using maximum of 1560 octet LLC block size and
RLC shall construct each uplink LLC frame when needed LLC size of RLC data is
received.
The RLC headers shall be removed from each RLC radio block and the RLC data units re-
assembled into an LLC PDU and passed to the next higher layer. The size of the LLC
PDU delivered to the higher layer shall not exceed 1560 octets.
Any octet received beyond this maximum limit and until the next identified LLC PDU
boundary shall be discarded when Gbn_ul_data_req_s message sent to BSSGP.
S9 interfaces are used between RLC and BSSGP with modification of LLC PDU
frame.
During RLC acknowledged and unacknowledged mode operation, received LLC PDUs
shall be delivered to the higher layer in the order in which they were originally transmitted.
The interface between RLC and BSSGP is done using netframes and netlib functions????
4.2 Message encoding and decoding
Control and data message send and receive mechanism has to encode and decode also
EGPRS specific messages in downlink and uplink. The EGPRS message encode and
decode apply to
Abis L3 interface
RLC data messages frames. RLC data frames have EGPRS specific format de-
pending on MCS used. The RLC data message encode and decode shall need MCS
value in conversion, see Table 3 MCS / RLC header types.
EGPRS RLC/MAC control blocks shall have GPRS format and be sent using CS-1
coding scheme. Control blocks shall be scheduled before sending, control block
encoding and decoding shall be done by MAC. The use of encoded message fields is
described in [04.60] 11.
Note: In S9 control messages are not segmented. In S10 the size of downlink control
messages has to be calculated to check if segmentation is needed. MAC doesnt support
control message segmentation, it is added. Possible use with assignment messages and
frequency parameters is described in [PBCCHIS].
4.3 EGPRS Packet Control Messages
Egprs control messages are sent between MS and network when connection
establishment is done or current connection properties are changed. Network specific
resources, parameters and messages updating connection state are used for
Author Approved by
TBF creation [PBCCHIS]
TBF reallocations
RLC acknowledges
4.4 Scheduling
4.4.1 MS synchronization
For synchronization purpose, the network shall ensure that each MS with an active TBF in
uplink or downlink receives at least one block transmitted with a coding scheme and a
modulation that can be decoded by that MS every 360 millisecond interval (78 TDMA
frames). [05.08, 10.2.2 BTS output power].
This function is implemented in the CHM. Timeslot scheduling algorithm in the CHM
ensures that there is on each timeslot on downlink at least one Radio Block at least every
360 ms using MCS-1 or CS-1 coding scheme.
4.4.2 GPRS and EGPRS TBF multiplexing
GPRS and EGPRS TBFs can be multiplexed dynamically on the same timeslot.
When USF is addressed to GPRS TBF the downlink RLC radio block carrying the USF
must use GMSK coding scheme, that is MCS-1 to MCS-4 if the DL RLC radio block is
addressed to EGPRS TBF or CS-1 to CS-2, if the DL RLC radio block is addressed to
GPRS TBF [04.60] 5.2.4a.
If there are uplink GPRS TBF and downlink EGPRS TBF multiplexed on the same
timeslot then the CHM restricts the EGPRS TBF to use MCS1-4. If EGPRS TBF is
allocated several timeslots the TBF uses MCS1-4 on all timeslots even though only
one of the timeslots is multiplexed with GPRS TBF. This way the RLC may retransmit
RLC data block in any timeslot and USF can still be directed to GPRS TBF.
NOTE: CHM scheduling order for TBFs is changed to cover the case when GPRS TBF is
multiplexed with EGPRS TBF in same timeslot. New scheduling order is
First uplink
Next downlink
This reversed order is used to check if USF is allowed in uplink for the TBF.
4.5 MS RX-lev update
4.5.1 Downlink
Author Approved by
4.5.2 Uplink
4.6 GPRS/EGPRS BTS selection
Now in S10.5 level?, some EGPRS things is missing??
Author Approved by
4.6.1 Initial BTS selection
START READY
Select the BTS that

concurrent is already serving
TBF type?
the MS
UL or DL
Select BTSs whose frequency band is included in the MS RAC

band information. => BTS_LIST_1
Note1: If MS RAC band is not known then BCCH band BTSs are
selected.
Note2: BTS that dont have PSW territory or channels for PSW
are not selected.
MS is EGPRS capable MS is not EGPRS capable

MS RAC?
Is there any EGPRS Is there any EGPRS

enabled BTS in the No No disabled BTS in the
BTS_LIST_1? BTS_LIST_1?
Yes Yes

disabled BTS in the enabled BTS in the
No BTS_LIST_1? BTS_LIST_1?
No
Yes Yes
RETURN: No BTS found RETURN: No BTS found
Remove EGPRS Remove EGPRS

disabled BTSs enabled BTSs
from BTS_LIST_1 from BTS_LIST_1
Figure. Initial BTS selection, phase 1: frequency band & TBF type checks
Author Approved by
UL TBF
TBF type?
DL TBF
C-value is C-value ? C-value is not

known known
Select from BTS_LIST_1 the BTSs whose Select from BTS_LIST_1 the BTSs whose
(C-value - non_bcch_layer_offset) is non_bcch_layer_offset is less than
bigger than gprs_non_bcch_rxlev_up direct_gprs_access_bts
=> BTS_LIST_2 => BTS_LIST_2
BTS_LIST_2
empty?
No
Yes
Select the BTS who has the smallest QoS Select the BTS who has smallest
load of the BTSs in the BTS_LIST_2 non_bcch_layer_offset value of the BTSs
in the BTS_LIST_1
READY
Figure. Initial BTS selection, phase 2: signal level checks
Author Approved by
4.6.2 Reallocation BTS selection
START
Select BTSs whose frequency band is included in the MS RAC

band information. => BTS_LIST_1
Note1: If MS RAC band is not known then BCCH band BTSs are
selected.
Note2: BTS that dont have PSW territory or channels for PSW
are not selected.
EGPRS TBF GPRS TBF

TBF mode?

enabled BTS in the No No disabled BTS in the
BTS_LIST_1? BTS_LIST_1?
Yes Yes
Is there any EGPRS

RETURN: No BTS found enabled BTS in the
BTS_LIST_1?
No
Yes
RETURN: No BTS found
Remove EGPRS Remove EGPRS

disabled BTSs enabled BTSs
from BTS_LIST_1 from BTS_LIST_1
2a
Figure. Reallocation BTS selection, phase 1: frequency band & TBF type checks
Author Approved by
2a
UL TBF Concurrent TBF

2b TBF type? 2c
DL TBF

known known
Select from BTS_LIST_1 the BTSs whose Select from BTS_LIST_1 the BTSs whose
(C-value - non_bcch_layer_offset) is non_bcch_layer_offset is less than
bigger than gprs_non_bcch_rxlev_up direct_gprs_access_bts
=> BTS_LIST_2 => BTS_LIST_2
BTS_LIST_2 BTS_LIST_2
empty? empty?
Yes No No Yes
Select the BTS who has the smallest QoS

load of the BTSs in the BTS_LIST_2
Select the BTS that is Select the BTS who has smallest
serving the TBF non_bcch_layer_offset value of the BTSs
in the BTS_LIST_1
READY
Figure. Reallocation BTS selection, phase 2a: signal level checks, downlink TBF
Author Approved by
Search BTSs from BTS_LIST_1whose

2b UL_sign_level is less than
gprs_non_bcch_rxlev_low
=> BTS_LIST_2
BTS_LIST_2
empty?
No Yes
Select the BTS who has the smallest QoS Select the BTS who has biggest
load of the BTSs in the BTS_LIST_2 gprs_nonbcch_rxlev_low value in the
BTS_LIST_1
Select the BTS that is READY

serving the TBF ???
Figure. Reallocation BTS selection, phase 2b: signal level checks, uplink TBF
Author Approved by
2c

known known
Search BTSs from BTS_LIST_1 whose Select from BTS_LIST_1 the BTSs whose
non_bcch_layer_offset is less than
(UL_sign_level is less than direct_gprs_access_bts
gprs_non_bcch_rxlev_low)
AND UL_sign_level tsekit???
((C-value - non_bcch_layer_offset) is
bigger than gprs_non_bcch_rxlev_up) => BTS_LIST_2
=> BTS_LIST_2
BTS_LIST_2 BTS_LIST_2
empty? empty?
Yes No No Yes
Select the BTS who has the smallest QoS

load of the BTSs in the BTS_LIST_2
Select NULL ??? Select the BTS who has smallest

non_bcch_layer_offset value of the BTSs
in the BTS_LIST_1
READY
Figure. Reallocation BTS selection, phase 2c: signal level checks, concurrent TBF
Author Approved by
4.6.3 Initial BTS Selection
4.6.3.1 Downlink
4.6.3.2 Uplink
4.6.4 Reallocation of a TBF
4.6.4.1 Reallocation activation
4.6.4.2 Selecting BTS in reallocation
4.6.4.3 CHM Reallocation procedures
4.6.4.4 TBF Rx-lev Reallocation
4.6.4.5 BTS Load Reallocation
4.6.4.6 GPRS TBF in EGPRS territory reallocation
4.6.4.7 BTS Timeslot reallocation
4.7 Territory procedures
4.7.1 Territory upgrade/downgrade
4.7.2 BCCH TSL 7 use
4.7.3 Territory balance update
4.8 Multi BCF and Common BCCH
4.9 EGPRS Packet transfer
4.9.1 Introduction to RLC layer operational modes
RLC layer has two operational modes, acknowledged and unacknowledged. RLC layer is
mainly responsible of processing packet transfer, data retransmissions and updating
acknowledgement information.
Acknowledged RLC mode controls packet retransmission using confirmations received

from receiving end of transfer. The packet transmitting state is kept up using Acknowledge
State array, Send and Receive State arrays which contains TBF BSN numbered packet
states.
Author Approved by
Unacknowledged RLC mode doesnt use packet retransmission, the end of transmission
is detected in countdown process [04.60] 9.3.1. Acknowledge messages are used
however in unacknowledge mode link adaptation.
CHM shall inform MAC of default TBF type (EGPRS/GPRS) and EGPRS timeslots
allocated using cha_*_alloc_req__r function. TBF:n luonnissa
RLC shall return default MCS/CS parameter value in the TBF initialization phase using
MAC rlc_mac_tfi_change_ind__r.
4.9.2 Introduction to Retransmission Control
Acknowledged RLC mode uses selective packet confirmation where the receiving side
confirms incoming packets. RLC packets are BSN numbered within TBF in use, and the
BSN numbers are used to identify packets not received correctly.
Receiving side sends confirmations either EGPRS PACKET DOWNLINK ACK/NACK or

PACKET UPLINK ACK/NACK depending on TBF transfer direction. The EGPRS PACKET
DOWNLINK ACK/NACK confirmation packet is sent by the MS when requested by the
network. The PACKET UPLINK ACK/NACK confirmation packet is sent by the network
whenever the network decides to do so.
Within downlink EGPRS TBF the network can query the MS send different ack/nack
bitmaps with or without Channel Quality Report.
First partial bitmap is without channel quality report. EGPRS Channel Quality Report
IE is, however, included if there is space in the EGPRS PACKET DOWNLINK
ACK/NACK message.
Next partial bitmap can be requested with or without Channel Quality Report.
This bitmap contains group of confirmations on packets to be re-sent and packets

successfully received.
Channel Quality Report information is used as input value to EGPRS Link Adaptation
algorithm and in CHM updating signal level values.
In DL data transfer a bitmap is received in EGPRS PACKET DOWNLINK ACK/NACK

message from MS, and in uplink case MAC/RLC can send PACKET UPLINK ACK/NACK
acknowledge to MS.
4.9.3 Introduction to MCS Selection
RLC selects MCS coding depending on radio link quality and amount of available dynamic
abis channels.
The MCS value for UL data transfer is sent to MS in PACKET UPLINK ASSIGNMENT or in
PACKET TIMESLOT RECONFIGURE if the properties of the concurrent DL TBF are
changed, [04.60] 11.2.31. The two MCS values, MCS-5-7 and MCS-6-9, are not used.
Author Approved by
Initial TBF MCS preference is set by the operator and CHM shall inform the parameter to
MAC when MAC requests for an allocation.
4.9.3.1 Introduction to MCS Selection in Retransmission
EGPRS RLC acknowledged mode can be controlled by a selective acknowledge

mechanism with or without Incremental Redundancy.
For DL data retransmission the RLC selects MCS using the same or another in the MCS
family in such a way that Incremental Redundancy is possible in the MS.
In UL data transfer the MS is either allowed or forbidden to use resegmentation for

retransmissions. This is determined by the network and indicated by the re-segment bit in
messages PACKET UPLINK ACK/NACK, PACKET UPLINK ASSIGMENT, PACKET
TIMESLOT RECONFIGURE. The re-segment field is used in accordance with
acknowledge mode of ARQ I or ARQ II (Incremental redundancy) for uplink TBF direction.
For retransmissions setting re-segment active 1 requires MS using same

MCS within the initial MCS family and payload may be split. [04.60] 8.1.1.
For retransmissions setting re-segment non-active 0, requires MS use MCS

within the initial family without payload split even if the MS is commanded to
use MCS-1, MCS-2 or MCS-3 for subsequent RLC data blocks, [04.60] 9.3.2.
The RLC sets resegmentation always to non-active in the MS, supporting Incremental
Redundancy in the BTS.
Resegmentation is PRFILE parameter (EGPRS_RE_SEGMENTATION) but its value is

always non-active. RLC shall update the resegmentation PRFILE value into RLC TBF
structures received from CHM when TBF created using rlc_mac_tfi_change_ind__r.???
The uplink ARQ II mode (Incremental redundancy) decoding is done in the BTS CCU unit
and RLC receives full encoded RLC data blocks together with information of MCS used in
uplink for RLC header decoding purposes.
4.9.4 Introduction to MCSs
Nine different modulation and coding schemes, MCS-1 to MCS-9, are defined for the
EGPRS Radio Blocks (4 bursts, 20ms) carrying RLC data blocks.
The block structures of the coding schemes are shown in Table 4 EGPRS coding
schemes. A general description of the MCSs is given in figure 2 Egprs RLC block MCS
use.
Author Approved by
Scheme Code Header Modulation RLC data Raw Data Family BCS Tail HCS Data
rate Code rate blocks per within one payload rate
Radio Block Radio Block kb/s
(20ms)
MCS-9 1.0 0.36 2 2x592 A 2x12 2x6 59.2
8PSK
8
MCS-8 0.92 0.36 2 2x544 A 54.4
MCS-7 0.76 0.36 2 2x448 B 44.8
MCS-6 0.49 1/3 1 592 A 29.6
544+48 27.2
12 6
MCS-5 0.37 1/3 1 448 B 22.4
MCS-4 1.0 0.53 1 352 C 17.6
GMSK
MCS-3 0.80 0.53 1 296 A 14.8
272+24 13.6
MCS-2 0.66 0.53 1 224 B 11.2
MCS-1 0.53 0.53 1 176 C 8.8
NOTE: the italic captions indicate the padding.
Table 4 EGPRS coding schemes
The MCSs are divided into different families A, B and C. Each family has a different basic
unit of payload: 37 (and 34), 28 and 22 octets respectively. Different code rates within a
family are achieved by transmitting a different number of payload units within one Radio
Block. For families A and B, 1, 2 or 4 payload units are transmitted, for family C, only 1 or
2 payload units are transmitted.
When 4 payload units are transmitted using MCS-7, MCS-8 or MCS-9, two separate RLC
data blocks with separate sequence numbers and BCS Block Check Sequences are
packed into one EGPRS Radio Block.
The data blocks for MCS-8 and MCS-9 are interleaved over two bursts whereas the data
blocks for MCS-7 are interleaved over four bursts. For other MCSs one RLC radio block
carries one RLC data block which is interleaved over four bursts. When switching to MCS-
3 or MCS-6 from MCS-8, 3 or 6 padding octets, respectively, are added to the data octets.
[03.64] 6.5.5.1.2.
All the other MCSs carry one RLC block which is interleaved over four bursts. When
switching to MCS-3 or MCS-6 from MCS-8, 3 or 6 padding octets, respectively, are added
to the data octets. [03.64] 6.5.5.1.2.
Author Approved by
MCS-3
Family A 37 octets 37 octets 37 octets 37 octets
MCS-6
MCS-9
MCS-3
34+3 octets 34+3 octets

Family A
padding MCS-6
34 octets 34 octets 34 octets 34 octets
MCS-8
MCS-2
Family B 28 octets 28 octets 28 octets 28 octets
MCS-5
MCS-7
MCS-1
Family C 22 octets 22 octets
MCS-4
Figure 2 Egprs RLC block MCS use. The PCU does not switch to grey shaded MCSs.
4.9.5 Introduction to RLC/MAC header types
Three different header formats are used, one for MCS-7, MCS-8 and MCS-9, one for
MCS-5 and MCS-6 and one for MCS-1 to MCS-4.
The two first formats are for 8PSK modes, the difference being in the number of
Sequence Numbers carried (2 for MCS-7, -8 and -9, 1 for MCS-5 and 6).
The third format is common to all GMSK modes.
The RLC/MAC header type and the CPS field in the RLC/MAC header indicates the MSC
change. [04.60] 10.4.8a. CPS field has different content depending on MCS used,
selected MCS defines also different RLC header content in downlink and uplink in Table 3
MCS RLC header types, [04.60] 10.3a.3, [04.60] 10.3a.4.
Author Approved by
MCS class RLC header type

MCS-9,MCS-8, MCS-7 Header 1
MCS-6,MCS-5 Header 2
MCS-4,MCS-3,MCS-2, MCS-1 Header 3
Table 3 MCS / RLC header types
RLC shall use CPS field in RLC header to make MCS change in downlink packet
transfer
Author Approved by
4.10 EGPRS TBF establishment, uplink and downlink
EGPRS TBF establishment is described in [PBCCHIS]. It covers all cases: one phase
access, two phase access and short access.
Ent initial BTS selection ?
4.11 EGPRS TBF release, uplink and downlink
EGPRS TBF release, including countdown procedure, is described in [PBCCHIS].
4.12 EGPRS RLC Window size, uplink and downlink
In RLC unacknowledged mode window size 64 is used.
In RLC acknowledged mode different window sizes are used depending on how many
radio time slots have been allocated for the TBF. See the table below. If the number of
TSLs is changed to larger value than what has been used during the TBF the window size
is increased according the table below. The window size is not changed if the number of
TSLs decreases during the TBF.
Time slots Window size in

allocated RLC
acknowledged
mode
1 192
2 256
3 384
4 384 *)
5 384 *)
6 384 *)
7 384 *)
8 384 *)
Table. RLC window sizes in acknowledged mode.
*) This is based on simulation results [RLCWin2].
The window size may be set independently on uplink and downlink.
The selected window size is indicated to the MS within PACKET UL/DL ASSIGNMENT and
PACKET TIMESLOT RECONFIGURE using the coding defined in [04.60, Table 9.1.9.2.1].
If the RLC changes the window size the RLC informs MAC about it using
mac_tfi_change_ind__r and the MAC sends the new window size to the MS.
Author Approved by
In case of reallocations of acknowledged mode TBF RLC window size shall be processed
as follows:
a) TBF is reallocated and more TSLs are allocated to the TBF
RLC Window size shall increase
RLC Window size shall be determined by RLC using timeslot allocation
New timeslot and RLC window size TBF resources shall be sent to MS by MAC
b) TBF is reallocated and fewer TSLs are allocated to the TBF
RLC Window size shall remain the same

New timeslot and RLC window size TBF resources shall be sent to MS by MAC
4.13 EGPRS downlink packet transfer
4.13.1 Downlink MCS selection phases
RLC / Downlink TBF
LA
Init MCS ?
write
MCSs
read
CHM
MCS
selection
DAM
Selected MCS for

downlink radio block
Figure. Downlink MCS selection context for RLC data blocks
Author Approved by
Downlink MCS selection is done every time when the RLC sends a RLC data block to the
MS. There are four phases when defining MCS for a DL data block as described in the
figure below and in the following paragraphs.
The CHM has

allocated the
TSLs of one TRX START
to DL TBFs
Data block and MCS prediction by RLC
MCS limiting by CHM
Dynamic Abis allocation by DAM
Data block and MCS selection by RLC
READY
Figure. DL TBF: MCS selection for TSLs of one TRX
The data between CHM, RLC and DAM is transferred using the edge_trx_sch_data_dl__t.
See Appendix A.
4.13.1.1 Data block and MCS prediction phase by RLC
The RLC selects data blocks for each TSL of the TRX and MCSs for the data blocks. In
the case of MCS7-9 the RLC selects two data blocks per TSL.
The RLC selects data blocks and MCSs as described in Data block selection and MCS
selection for the data block paragraphs below.
The DAM needs MCS information when allocating dynamic abis capacity for TSLs of the
TRX.
This phase starts when the RLC receives rlc_get_dl_tbf_mcs__r call from the CHM.
4.13.1.2 MCS limiting phase by CHM
At this phase the CHM may limit MCS for each TSL of the TRX.
Generally the CHM accepts the MCS from the RLC. Exceptions:
- If the RLC has selected 8-PSK MCS and the USF is meant to a MS in GPRS TBF
mode then the CHM reduces the MCS to MCS-4.
Author Approved by
Exception:
If the RLC is retransmitting a (NACKed??) data block using 8-PSK MCS the CHM
does not reduce the MCS, and does not give USF to GPRS TBF at this time.
See appendix A.
- Only for downlink: If there has not been any MCS-1 or CS-1 transmission during last
340 milliseconds then the CHM sets MCS to MCS-1. (There must be MCS-1 or CS-1 at
least once in 360 milliseconds).
- Short access MCS-1??RLC/MAC?
- Only for downlink: If the RLC has selected 8-PSK MCS for TSL7 of BCCH TRX and
BCCH power level is 0 then the CHM reduces the MCS to MCS-4. ???
If power level differs from 0 then also 8-PSK MCS is allowed for the TSL7.
The CHM performs this phase before calling dam_allocate_dl_items_req__r.
4.13.1.3 Dynamic Abis allocation phase by DAM
The DAM allocates Abis slave channels for the TRXs TSLs based on the MCS that the
RLC/CHM has selected. If there are not so many slave channels as the MCS needs, the
DAM allocates fewer slaves and informs the RLC about next lower MCS that fits on the
allocated Abis capacity. See [DAM IS].
This phase starts when the DAM receives dam_allocate_dl_items_req__r call from the
CHM.
4.13.1.4 Final data block and MCS selection phase by RLC
The RLC selects again data blocks for TSLs and a MCSs for the data blocks based on the
MCSs given by the DAM.
If the DAM returns exactly the same MCSs that the RLC predicted the RLC selects same
data blocks as in the prediction phase.
If the RLC cannot use MCS given by the DAM the RLC decreases the MCS or selects no
block for the TSL.
The RLC selects data blocks and MCSs as described in Data block selection and MCS
selection for the data block paragraphs below.
This phase starts when the RLC receives rlc_get_dl_rlc_data_items__r call from the CHM.
4.13.2 Data block selection
The RLC selects RLC data blocks as specified in [04.60, 9.1.3.2 Acknowledge State Array
V(B) for EGPRS TBF Mode].
The following principle is used. See details from [04.60].
1) The oldest NACKed state block is selected (In BSN order)
Author Approved by
2) If no NACKed state block exists then a new block is generated
3) If no NACKed state block exists and transmit window is stalled or there is not
new data then the oldest PENDing state block is selected
The block state structure is described in [RLCS9DD, in 3.3 State structure paragraph].
START
Yes No No
End of
NACKed blocks exists? window?
Yes
Select the oldest Select the oldest Select new block.

NACKED block. PENDING block.
Is it possible to send the

block within MCS limit
given by CHM/DAM?
Yes No
CHM makes dummy

READY control block
Figure. DL TBF data block selection
4.13.3 MCS selection for data block
The RLC selects MCS for a data block.
At the MCS prediction phase the RLC selects MCS freely. At the final MCS selection
phase the RLC has to take account limitations set by the CHM/DAM.
The max MCS is MCS-7 if DX has told MCS-7 is highest MCS allowed. DX does so if there
is CX3.2 SW running in the UltraSite base station.
4.13.3.1 Initial transmission (new block)
Generally MCS from LA algorithm is used.
Exceptions:
- If MCS would be MCS-7 but the RLC could generate only one block (Note1) then
the RLC selects MCS-5
- If MCS would be MCS-8 or MCS-9 but the RLC could generate only one block
(Note1) then the RLC selects MCS-6
- The CHM or the DAM has required a lower MCS. The RLC must not select higher
MCS than the CHM/DAM says.
Author Approved by
- Operator defined initial MCS is used at the beginning of TBF. This function is
embedded in the link adaptation algorithm.
The selected MCS must fulfil all the rules above.
Note1: The RLC can generate only one block if there is not PENDING block and there is
not new data to be used as the second block.
Note2: At the end of TBF a lower MCS could carry all the data but this function is not
implemented in the RLC. The RLC does not select lower MCS in this situation.
4.13.3.2 Retransmission in RLC acknowledged mode (NACKed or PENDING block)
Resegmentation is not used but the PCU selects MCS so that downlink IR is possible in
the MS [04.60]. Generally the same MCS is used as that used for the previous
transmission of the block.
Exceptions:
- If previous transmission used MCS-7 but the RLC can generate only one MCS-7
half block then MCS-5 is used.
half block then MCS-6 padding is used.
half block then MCS-6 is used.
- A block whose previous transmission used MCS-5 is retransmitted using MCS-7 if

the RLC can generate another MCS-7 half block too. For example when there are
two NACKED MCS-5 blocks that can be sent together using MCS-7.

the RLC can generate another MCS-9 half block too. For example when there are
two NACKED MCS-6 blocks that can be sent together using MCS-9.
Note: A block whose previous transmission used MCS-6 padding is retransmitted

using MCS-6 padding. It is not retransmitted using MCS-8.
- Retransmission MCS from LA is lower than MCS used in previous transmission:
- The retransmission MCS from LA is MCS-7. Then instead of MCS-9 or MCS-8 the
RLC selects MCS-6 or MCS-6 padding, respectively
- The retransmission MCS from LA is MCS-6. Then instead of MCS-9, MCS-8 or

MCS-7 the RLC selects MCS-6, MCS-6 padding or MCS-5, respectively
- The CHM has required so low MCS that it cannot be used basing on the rules
above. Then a dummy control block is transmitted.
- There is not room enough in Dynamic Abis, The DAM has limited the MCS:

the DAM states there is room for MCS-6 but not for MCS-9 in Dynamic Abis.
Author Approved by
- A block whose previous transmission used MCS-8 is retransmitted using MCS-6

padding if the DAM states there is room for MCS-6 but not for MCS-8 in Dynamic
Abis.

the DAM states there is room for MCS-5 but not for MCS-7 in Dynamic Abis.
- DAM states there is so few room in Dynamic Abis that it cannot be used for the
block. Then a dummy control block is transmitted.
The selected MCS must fulfil all the rules above.
4.13.3.3 Retransmission MCS of last block in RLC unacknowledged mode
Retransmission of last block is done with MCS-6 if the initial transmission was done with
MCS-8 or MCS-9.
Retransmission of last block is done with MCS-5 if the initial transmission was done with
MCS-7.
Retransmission of the last block is done with the same coding as the initial transmission if
the MCS was 1-6.
4.13.4 RLC radio block construction
4.13.4.1 RLC/MAC header construction
4.13.4.2 RLC data block construction
The RLC constructs EGPRS data block as defined in [04.60].
Some notes:
- The RLC fills E=1 and sets no extension octets when there is no LLC boundary in
the block.
- BSN1 refers to the earlier block in transmit window and BSN2 is relative to BSN1
when MCS-7, 8 or 9 is used.
- The RLC fills TFI, BSN, SPB=0 and FBI in the header.
- The RLC fills CPS in the header: PS should be 1 in initial transmission. In

retransmission the RLC selects PS according to [04.60, 9.3.2.1]
- MCS-6 padding: There are six padding octets in the front of RLC data when MCS-6
padding is used. The RLC does not initialize the padding octets. They can have any
value
Length indicator (LI):
- The RLC inserts extension octet with LI=0 and E=1 if the previous LLC PDU ends in
the previous data block without LI.
Author Approved by
- The RLC inserts LI for each LLC end usually. No LI is used for last LLC frame if it
fills precisely the final block of TBF. (FBI=1)
- The RLC uses LI=127 only in the last block of downlink TBF, to indicate last LLC
PDU. The RLC uses filler octet 2B after LLC data.
LI=30, E=0
LI=127, E=1
--- 30 data bytes ---
2B2B2B2B2B2B2B2B......2B
LI usage at the end of TBF
LI=30
LI=36
--- 30 data bytes ---
43 C0 01 + 33 x 2B
LI usage at the middle of TBF (MCS-6)
4.13.5 Downlink acknowledgement procedure
As two MCS-7-9 RLC data blocks can be sent in one RLC radio block, the RLC shall
update RLC block state and MCS used according to RLC data blocks sent
4.13.5.1 Downlink Acknowledged mode
Downlink EGPRS packet transfer is controlled by RLC by using acknowledges and

retransmission. Downlink acknowledges are polled from MS by RLC to keep up data link
quality and packet transfer, and acknowledge data compression can be used.
The RLC retransmits downlink RLC packets requested by MS.
4.13.5.2 Downlink Unacknowledged mode
The transfer of RLC data blocks in the RLC unacknowledged mode does not include any
retransmissions, except during the release of a downlink TBF where the last transmitted
downlink RLC data block may be retransmitted (max four times).
The MS sends Packet Ack/Nack messages in order to convey the necessary other control
signalling (e.g. monitoring of channel quality for downlink transfer).
Author Approved by
4.13.5.3 EGPRS Packet downlink ack/nack polling
In downlink transmission the RLC requests EGPRS PACKET DOWNLINK ACK/NACK

messages from MS using RLC data packet and valid Egprs Supplementary / Polling ES/P
and RRBP?? fields in RLC data header.
S/P Feedback Request (Poll) Description

00 Nothing (RRBP field invalid)
01 EGPRS PACKET DOWNLINK ACK/NACK message containing FPB (First
Partial Bitmap), drop channel quality report
10 EGPRS PACKET DOWNLINK ACK/NACK message containing NPB (Next
Partial Bitmap), drop channel quality report
11 EGPRS PACKET DOWNLINK ACK/NACK message containing NPB and
Channel Quality Report
Table 5 Format of EGPRS Supplementary/Polling (ES/P) field within each EGPRS RLC
radio block [04.60]
For GPRS TBFs in EGPRS territory the RLC request polling using the
edge_trx_sch_data_dl__t. See Appendix A.
For EGPRS TBFs the RLC request polling using chm_poll_req__r. ?? Or by filling ESP to
DL frame?
The acknowledge message can contain EGPRS BEP Link Quality Measurements IE
depending on the polling strategy (ES/P field) and RLC block size available, [04.60]
12.5.1.
The RLC polls downlink EGPRS TBF as follows:
- When predefined count of downlink RLC data block are sent, as in S9 [RLCS9IS]
except EGPRS specific PRFILE parameters are used
(PR_NR_T_EGPRS_DOWNLINK_PENALTY, PR_NR_T_EGPRS_DWNLINK_THRESHOLD).
- The first block is polled, as in S9 [RLCS9IS].
- The last block is polled, as in S9 [RLCS9IS].
- Dummy LLC block is polled (delayed TBF), as in S9 [RLCS9IS].
- When all blocks have been retransmitted once, as in S9 [RLCS9IS]. Only in RLC
acknowledged mode.
- After TBF reallocation, as in S9 [RLCS9IS].
- When the CHM wants the MS to send Packet measurement report.
Every third poll requests first partial bitmap (FPB). Polling start from FPB. Polling order is
FBP -> NPB -> NPB + measurement report. If the CHM has requested polling then the
RLC requests NPB + measurement report and the next polls are FBP -> NPB -> NPB +
measurement report.
If the RLC must poll but polling is not possible then the CHM generates a dummy control
block.
Author Approved by
4.13.5.4 Interpretation of EGPRS Packet Downlink Ack/Nack message
4.13.5.4.1 Downlink Ack/Nack compression
Acknowledge message received in Egprs Packet Downlink Ack/Nack message can

contain compressed acknowledge. The compression shall done using ITU T.4 run length
limiting algorithm if compressed data length is shorter than uncompressed data length.
[04.60] 9.1.10.
4.13.5.4.2 Interpretation of compressed Acknowledgment
If the compressed acknowledge is received which is indicated non-zero length in EGPRS

Ack/Nack Description field. [04.60] 9.1.8.2.3. The bit encoded BSN numbers shall be used
as RLC packets acknowledge information.
The compressed acknowledge is constructed using predefined table equivalents for runs
lengths either 1 or 0. The conversion table has unique fields and sequences in either
of One run length or Zero run length columns.
Author Approved by
Table 1 Terminating T.4 code words

One run length Code word Zero run length Code word
0 00110101 0 0000110111
1 000111 1 10
2 0111 2 11
3 1000 3 010
4 1011 4 011
5 1100 5 0011
6 1110 6 0010
7 1111 7 00011
8 10011 8 000101
9 10100 9 000100
10 00111 10 0000100
11 01000 11 0000101
12 001000 12 0000111
13 000011 13 00000100
14 110100 14 00000111
15 110101 15 000011000
16 101010 16 0000010111
17 101011 17 0000011000
18 0100111 18 0000001000
19 0001100 19 00001100111
20 0001000 20 00001101000
21 0010111 21 00001101100
22 0000011 22 00000110111
23 0000100 23 00000101000
24 0101000 24 00000010111
25 0101011 25 00000011000
26 0010011 26 000011001010
27 0100100 27 000011001011
28 0011000 28 000011001100
29 00000010 29 000011001101
30 00000011 30 000001101000
31 00011010 31 000001101001
32 00011011 32 000001101010
33 00010010 33 000001101011
34 00010011 34 000011010010
35 00010100 35 000011010011
36 00010101 36 000011010100
37 00010110 37 000011010101
38 00010111 38 000011010110
39 00101000 39 000011010111
40 00101001 40 000001101100
41 00101010 41 000001101101
42 00101011 42 000011011010
43 00101100 43 000011011011
44 00101101 44 000001010100
45 00000100 45 000001010101
46 00000101 46 000001010110
47 00001010 47 000001010111
48 00001011 48 000001100100
49 01010010 49 000001100101
50 01010011 50 000001010010
51 01010100 51 000001010011
Table (continued): Terminating codes (reproduced from ITU-T T.4); T.4 code words used for
representing run lengths of 1 zero and 3 zeros are interchanged.
Author Approved by
52 01010101 52 000000100100
53 00100100 53 000000110111
54 00100101 54 000000111000
55 01011000 55 000000100111
56 01011001 56 000000101000
57 01011010 57 000001011000
58 01011011 58 000001011001
59 01001010 59 000000101011
60 01001011 60 000000101100
61 00110010 61 000001011010
62 00110011 62 000001100110
63 00110100 63 000001100111
When run length is between 063 it shall be encoded using terminating run length value
only.
If the run length is longer than 63 it is encoded using make-up code which is equal or
shorter than that required. This is followed by terminating code, which is difference
between the required run length and the run length represented by the make-up code in
table.
Table 2 Make-up codes

One run length Code word Zero run length Code word
64 11011 64 0000001111
128 10010 128 000011001000
192 010111 192 000011001001
256 0110111 256 000001011011
320 00110110 320 000000110011
384 00110111 384 000000110100
448 01100100 448 000000110101
512 01100101 512 0000001101100
576 01101000 576 0000001101101
640 01100111 640 0000001001010
704 011001100 704 0000001001011
768 011001101 768 0000001001100
832 011010010 832 0000001001101
896 011010011 896 0000001110010
960 011010100 960 0000001110011
Example of acknowledges run of 1111000 shall be encoded to the result code

1011010 taken from terminating code table evaluated from the left, Table 1.
Encoding and decoding shall be done when acknowledgement messages are processed.
The compression algorithm execution time shall be minimized.
The decoding shall start using the table values for direct indexing from the left of the
codeword, and using table fields as indexes to represent the lengths of runs of 1 or 0.
This may take quite many iteration steps depending on actual run length value spread.
Among many alternatives obtaining short process time are the use of hash-table search or
binary-tree where the tree leaf shall contain terminating code value and the path to
terminating code is expressed as code word in Table 1. The search time of binary tree or
hash-table is small compared to linear seach using table indexing.
Author Approved by
Dedicated part of binary-tree decoding run length starting the evaluation from the left of
codeword values 3,5,6,7 is described in Figure 3.
The default decoding / encoding order shall be to use codeword evaluation from left to
right in table columns.
Details of decompression algorithm shall be described in RLC design document. But in

both the hash-table or binary-tree cases the processing time could be minimized which is
benefit as the encoding / decoding can be repeatedly processed.
0
1
0
1
0
0 1
0
0
7
3 6
5
Figure 3 Decoding search-tree in the RLC
4.13.5.5 Time stamping of sent data blocks
The RLC uses timestamps for RLC data bocks to prevent unnecessary retransmissions
between periodic downlink polling used. (There may be several polls during round trip
delay). Timestamp consists of block period number and time slot number used for the RLC
data block. The RLC saves time stamp internally for each data block on RLC
acknowledged mode.
When the RLC receives EGPRS Packet Downlink Ack/Nack message the RLC decides
what PENDING blocks are NACKED. The not acknowledged blocks whose time stamp is
newer than the transmission moment of the acknowledge message are not set to
NACKed. In other words the RLC keeps PENDING_ACK state although RB value is 0 if
block has been sent after poll of this acknowledgement.
CHM/Scheduler sends block period number (BPNsent) and TSL number (TSLsent) to the
RLC when requesting downlink RLC data blocks in both GPRS and EGPRS TBFs. The
RLC saves them as time stamp. The MAC sends to the RLC block period number
(BPNpoll) and TSL number (TSLpoll) that were used for the poll request with EGPRS
Packet Downlink Ack/Nack message. The RLC ignores the NACK for a RLC data block
if BPNsent > BPNpoll, or if (BPNsent = BPNpoll) but (TLSsent > TSLpoll).
Author Approved by
PCU MS
Block 1
Block 2
Block 3, poll req
Block 1 retr
Block 2 retr
EGPRS Packet
Downlink Ack/Nack
If the EGPRS Packet Downlink ACK/NACK message

NACKs the blocks 1 and 2 the PCU ignores it and keeps
the blocks in PENDING state
Figure. Benefit of Time stamp
4.13.6 Delayed release of downlink EGPRS TBF
Delayed release of downlink EGPRS TBF is implemented same way as it has been
implemented for GPRS TBF [RLCS9IS], [44.060, CR 009 r2, GP-010947]. The RLC sends
dummy LLC blocks using MCS-1. See Appendix B. In the last dummy LLC block the RLC
sets LI=127 and FBI=1. Delay time is 1s. It is set in PCU and can be changed with MIPC
message.
4.14 EGPRS downlink retransmission using BTS buffering
4.14.1 Introduction to downlink pointer retransmission
To minimize Dynamic Abis use in retransmission situations of the EGPRS RLC data the
BTS buffers the data of EGPRS DL radio blocks per TSL for certain time. In the
retransmission situation the PCU checks whether the pointer to the BTSs memory can still
be used or whether the RLC data frame must be sent over the Abis. If retransmission can
be performed from BTS memory, only master Abis channel is needed and resources from
the EDAP are not allocated. Every BTS supporting dynamic abis supports also pointer
retransmission.
This mechanism is used for MCS-1MCS-9 but not for CS1 and CS2. The PCU can
select MCS and PS as if the data were retransmitted from the PCU. The following table
shows the permitted cases of retransmission. The PCU is not allowed to use the cells that
are shaded grey for the CX3.2 software release but the PCU can use them for the CX3.3
software release.
Author Approved by
MCS on previous transmission Possible MCSs for

pointer retransmission
MCS-9 MCS-9
MCS-6
MCS-8 MCS-8
MCS-6(pad)
MCS-7 MCS-7
MCS-5
MCS-6 MCS-9
MCS-6
MCS-6(pad) MCS-6(pad)
MCS-5 MCS-7
MCS-5
MCS-4 MCS-4
MCS-3 MCS-3
MCS-2 MCS-2
MCS-1 MCS-1
Table 1: DL Pointer MCS Retransmission Table [CX3.2]
MCS-6(pad) refers to an MCS-8 half-block (575 bits) that is padded to 622 bits according
to GSM 05.03. The PCU does padding if the PCU transmits the data over Abis. The BTS
does padding if the data for MCS-6(pad) block is taken from the BTS memory and it is not
already padded.
For more information see [AbisL1] and [CX3.2].
4.14.2 Implementation description of downlink pointer retransmission
4.14.2.1 Basic function
When the RLC is going to retransmit a EGPRS RLC block the RLC checks if the block is
still in the BTS buffer. The block is in the BTS buffer if
BPN(current) - BPN(previous transmit) < BTS buffer size

BPN = Block Period Number. PCU internal expression for TDMA Frame Number. Calculated by PFH from
Coded Frame Number (T1, T2, T3 which are found from Control Bits of PCU Frames).
If the block is in the BTS buffer then the RLC uses pointer expression for retransmission
and informs the DAM about it:
- The RLC fills RLC/MAC header (D1-D48 [AbisL1]) and the pointer information bits (C7,
D49-D72 [AbisL1]) in PCU downlink RLC data frame.
- The DAM fills C-bits (C46-C63 [AbisL1]) in PCU downlink RLC data frame.
- The data between the RLC and DAM is transferred using the
edge_trx_sch_data_dl__t. See Appendix A, usage of pointer field is described there.
Author Approved by
The RLC does not use pointer retransmission for retransmissions of unacknowledged
mode TBF.
4.14.2.2 Half block indication
The RLC saves the half block information when transmitting RLC radio block (initial or
retransmission) so the RLC knows if the data to be retransmitted is located in the first or
second half at the BTS memory.
The RLC may ask the BTS to retransmit a data block that has already been retransmitted,
by pointing to the re-transmitted block.
If the retransmitted radio block has two data blocks (MCS7-9) both data blocks have to be
found from BTS memory if pointer method is used. It is not possible to send one half block
on Abis and pick the other half block from BTS memory.
4.14.2.3 BPN overflow
Here BPN overflow means that TBF wait sending turns so long that BPN has gone
through the complete cycle before the RLC sends poll request. Then the RLC erroneously
thinks that the oldest block in the RLC window is still in the BTS memory.
To avoid this problem some kind of protection mechanism is built into the RLC. For
example the RLC could maintain additional bits to increase BPN number space.
Is BPN overflowing possible?
BTS buffer, 96 BPNs
... 98 ... 9791 0 ... 99 ...
The block was If the block is retransmitted until here,

transmitted here, BPN=99, the RLC thinks the block is
BPN=98 still in the BTS memory
(99 minus 98 is less than 96)
If there are 16 downlink TBFs in a TSL then the worst case is that there are 15 gold users
and one with lowest priority. The gold users get max 12 transmission turns each and then
the lowest priority user get one turn. So the lowest priority TBF gets every 181 st turn. It
means a turn in every 3.62 nd second.
3.62 second is possible because the MS waits block 5 seconds. If the MS does not
receive a valid RLC data block in 5 seconds (T3190) the MS performs an abnormal
release for the TBF. [04.60]
Author Approved by
The RLC asks the MS to send acknowledgements after

EGPRS_DWNLINK_THRESHOLD blocks. EGPRS_DWNLINK_THRESHOLD is PFILE
parameter, range 1-255. So maximum difference between the oldest block in the RLC
memory and the current BPN can be 181 x 255 = 46155 when Control messages and
Round trip delay are not taken into account. BPN runs between 09791, so BPN
overflowing is possible. (?)
4.14.2.4 TRX reallocation
Here TRX reallocation means that the CHM reallocates TBF to other TRX.
The BTS buffer cannot be used for retransmission of the blocks sent before the TRX
reallocation.
The CHM informs the RLC about TRX reallocation using the edge_trx_sch_data_dl__t.
See appendix A. RLC could use the information for example:
- The RLC could store the BPN value of the reallocation moment (=reallocation BPN).
The BTS saves the TBF's blocks starting from the reallocation BPN in the buffer of the
new TRX. If the RLC is going to retransmit a block using BTS buffer the RLC checks
also if the BPN(previous transmit) of the block is newer than the reallocation BPN. If it
is newer then pointer retransmission is possible. The RLC shall not perform the check
after the TBF has been on the new TRX 96 block periods because after that the
reallocation BPN has no meaning.
4.14.2.5 Abis transmission error
The PCU retransmits data using "Pointer Present" maximum two consecutive times. Third
consecutive retransmission of the data is done using "Data Present". After that pointer can
be used again
This is because it is possible that the Master Data Frame is corrupted during Abis
transmission (CRC error). In such cases if "Data Present" then the BTS does not store
the data blocks in BTS memory. The PCU is not informed about the CRC error. If the PCU
then retransmits the data using "Pointer Present" then the BTS transmits an idle packet on
air.
Note: The pointer retransmission function derives its timing from the TDMA frame number
(T1,T2,T3 counters), and not from the Abis timing, so it should survive any temporary loss
of synchronization of Abis frames.
Author Approved by
4.15 EGPRS uplink packet transfer
4.15.1 Uplink commanded MCS selection
RLC / Uplink TBF
Init MCS LA
write
MCS
read
Commanded MCS for
CHM uplink is sent to MS
Commanded
MCS selection
DAM
MS
MCS
selection
Figure. Uplink MCS selection context for RLC data blocks
Uplink MCS selection is done by MS. It is based on the commanded MCS but the MS may
select lower MCS too.
The PCU sends commanded MCS to the MS in EGPRS Modulation and Coding Scheme
IE. Resegment bit is set to 0 always. MCS-5-7 and MCS-6-9 are not used. Generally
MCS from LA algorithm is used.
Exceptions:
- Short access, then MCS-1 is used????
- If MS is not 8-PSK capable in uplink then only MCSs 1-4 are commanded to MS. This
limitation is embedded in the LA algorithm.
- Operator defined initial MCS is used at the beginning of TBF. This function is
embedded in the link adaptation algorithm.
Author Approved by
4.15.1.1 Uplink Dynamic Abis allocation
The RLC returns in rlc_get_ul_tbf_mcs__r the maximum MCS that has been commanded
to the MS during the TBF lifetime. The DAM allocates that amount of uplink abis channels
for the TBF. If the DAM cannot allocate so many channels as needed then the DAM tell it
to the CHM (dam_allocate_ul_items_req__r) and the CHM does not allocate USF for the
MS at this time.
4.15.2 LLC PDU assembly
The RLC performs this phase according to [04.60].
Some notes:
- The RLC decodes BSN, CPS, PI, TI and E fields of blocks
- The RLC detects the LLC PDU end according to LI values, special case LI=0
- The RLC detects end of last LLC PDU of TBF, special case LI=127
- The RLC detects last LLC PDU of TBF, special case when it has no length indicator.
- The RLC discards data exceeding 1560 bytes in LLC PDU
- In the uplink TBF the LI=127 may appear also in the middle of the TBF.
In RLC unacknowledged mode:
- if the RLC data block header is correctly decoded but the data block is bad, the
output of decoder is inserted to the LLC PDU.
- if header is not correctly received then 0 fill bits are inserted to the LLC PDU.
Commanded MCS determines the number of fill bits [04.60, 9.1.12, table 9b].
Author Approved by
4.15.3 Uplink acknowledgement procedure
4.15.3.1 Uplink Acknowledge mode
The RLC requests packet re-sending in uplink transfer from MS for the packets not
received correctly. The RLC sends uplink acknowledgements within PACKET UPLINK
ACK/NACK messages to MS. The PCU sends Packet Ack/Nack messages also in order to
update the necessary other control signalling (e.g. timing advance correction for uplink
transfers).
To allow MS to send unacknowledged PENDING_ACK RLC data blocks the

PRE_EMPTIVE_TRANSMISSION shall be allowed, i.e. Value 0 shall be used in the
Packet Uplink Ack/Nack field. [04.60] 11.2.28.
4.15.3.2 Uplink Unacknowledged mode
The transfer of RLC data blocks in the RLC unacknowledged mode does not include any
retransmissions, except during the release of an uplink TBF where the last transmitted
uplink RLC data block may be retransmitted [04.60] 9.3.3.3.
The PCU sends Packet Ack/Nack messages in order to update the necessary other
control signalling (e.g. timing advance correction for uplink transfers).
4.15.3.3 Packet uplink ack/nack sending
PACKET UPLINK ACK/NACK messages are sent to MS using RLC threshold and counting
received/failed uplink RLC radio blocks. The weight is used to reach the threshold faster
when failure rate grows. Algorithm for Egprs uplink retransmission is equal to used in S9
[RLCS9IS] with the exception of retransmit threshold and weight values used (PRFILE,
PR_NR_T_EGPRS_UPLINK_PENALTY and PR_NR_T_EGPRS_UPLINK_THRESHOLD).
The RLC sends Packet UL Ack/Nack message in the same situations as in S9 [RLCS9IS],
except MCS change is not a trigger for sending the message.
Similarly to S9 Gprs implementation, RLC initiates the Egprs uplink acknowledgement by

sending mac_ack_req__s to MAC. MAC reserves a radio block for the PACKET UPLINK
ACK/NACK message but doesn't encode the contents yet. MAC forwards this dummy
block to the scheduler with sch_schedule_rat_control__r.
When it is time to send this message, the scheduler calls the new function
mac_p_ul_ack__r in order to encode the PACKET UPLINK ACK/NACK contents to this
dummy block before sending it. The function mac_p_ul_ack__r gets the latest EGPRS
Ack/Nack Description information from RLC with the new function rlc_egprs_ack_info__r.
RLC shall receive available data size to use for EGPRS Ack/Nack Description in the
input parameters.
S9: PFH
Author Approved by
S10: MAC EGPRS TBF:lle, ja PFH GPRS TBF:lle sek EGPRS ett GPRS territorioissa
4.15.3.4 Packet uplink Ack/Nack message content
The PCU does not use compressed acknowledge mechanism for EGPRS in Packet
Uplink Ack/Nack message to MS.
4.15.4 Invalid content in uplink data block
The RLC ignores uplink RLC data block if :
- sum of LI values is too big
- it has wrong TFI
- there is no E=1 value in the block.
- splitted block is received (MCS-3+padding)
- block has reserved CPS value.
4.15.5 ITFI
4.16 EGPRS Link Adaptation
Link adaptation function gives the highest allowed MCS. To maintain good throughput the
goal for the link adaptation algorithm is to adapt to situations where signal strength
compared to interference level is changing within time. The EGPRS link adaptation
implementation in the PCU is based on [S10LA].
Link adaptation is done independently for each UL TBF and DL TBF.
In downlink case EGPRS link adaptation is based on BEP measurement data in EGPRS
Channel Quality Report received in EGPRS PACKET DOWNLINK ACK/NACK message.
The PCU activates Link adaptation in downlink transfer when the PCU receives EGPRS
Packet Downlink Ack/Nack message.
In uplink case EGPRS link adaptation is based on the respective BEP measurement
values that are received within the UL PCU frames. The PCU averages the BEP
measurement values every time the PCU has received a new UL PCU frame. The PCU
activates Link adaptation in uplink when the PCU sends Packet Uplink Ack/Nack
message.
Link Adaptation algorithm is same for uplink and downlink.
Link Adaptation algorithm works differently for acknowledged mode and unacknowledged
mode.
Author Approved by
Link adaptation function is implemented in the RLC.
DOWNLINK UPLINK
PCU receives
Uplink radio block
Uplink averaging
Averaged BEPs
PCU receives EGPRS PCU decides to send
Packet Downlink Packet Uplink Ack/Nack
Ack/Nack message. message.
The BEPs from the The BEPs from

message are delivered averaging are delivered
to adaptation algorithm. to adaptation algorithm.
Link Adaptation algorithm
Downlink case outputs: Uplink case output:

- MCS for initial transmission - MCS that is sent to MS in Packet
- MCS for retransmission Uplink Ack/Nack message
Figure. Link Adaptation in the PCU
4.16.1.1.1 BEP measurement and TBF initialization
Egprs TBF creation procedures for uplink and downlink are described in detail in
[PBCCHIS] together with system messages sent to MS.
Sys infos
BEP_PERIOD is broadcast on PBCCH or, if PBCCH does not exist, on BCCH

[DXEGPRS].
Author Approved by
Downlink
BEP measurements are initiated to MS in downlink using IMMEDIATE ASSIGNMENT or

PACKET DOWNLINK ASSIGNMENT [04.60] 11.2.7 messages when TBF is created
[PBCCHIS]
The parameters are
LINK_QUALITY_MEASUREMENT_MODE can be 00 from LA point of view since per-

slot measurements are not needed
BEP PERIOD2, not used
Operator setting for Initial MCS is used until first BEPs measured by MS are received in
EGPRS Packet Downlink Ack/Nack message.
Uplink
When uplink TBF is created PACKET UPLINK ASSIGNMENT is used to set TBF properties
[04.60] 11.2.29.
The parameters are
EGPRS Channel Coding Command, operator setting for initial MCS is used
RESEGMENT, always 0 = Retransmitted RLC data blocks shall not be re-segmented
BEP_PERIOD2, not used
Operator setting for Initial MCS is used until the first Packet Uplink Ack/Nack is sent after
the first uplink measurement has become available.
4.16.2 Downlink Link Adaptation
The RLC requests downlink acknowledges using ES/P field in RLC radio block.
Input parameters for downlink link adaptation algorithm are the BEP values in the EGPRS
Packet Downlink Ack/Nack message as follows:
- GMSK_MEAN_BEP
- 8-PSK_MEAN_BEP
- GMSK_CV_BEP
- 8-PSK_CV_BEP
The RLC gets the values in the mac_ack_ind__r. The RLC activates Link adaptation for
downlink TBF when the RLC receives the mac_ack_ind__r for the TBF. The link
adaptation algorithm is described in subclause Link Adaptation algorithm.
Downlink Link Adaptation algorithm produces two MCS values, a MCS for initial
transmission and a MCS for retransmission. MCS for initial transmission is max MCS to be
used for initial transmission. MCS for retransmission is max MCS to be used in downlink
retransmission in ack mode.
Author Approved by
If the mac_ack_ind__r does include neither GMSK nor 8-PSK BEPs the RLC does not
execute link adaptation algorithm but previous MCSs stay valid. If no BEP s have arrived
during the entire TBF, the MCS from parameter initial MCS is used.
4.16.3 Uplink Link Adaptation
Input parameters for uplink link adaptation algorithm are the BEP values from averaging
as follows:
- GMSK_MEAN_BEP
- 8-PSK_MEAN_BEP
- GMSK_CV_BEP
- 8-PSK_CV_BEP
The RLC activates Link adaptation for uplink TBF when the RLC decides to send ack to
the MS. The link adaptation algorithm is described in subclause Link Adaptation algorithm.
Uplink Link Adaptation algorithm produces one MCS value that is sent to MS in the Packet
Uplink Ack/Nack message.
Support of 8-PSK in uplink direction is optional for the EGPRS MS. The algorithm does
not give 8-PSK MCS if the MS is not 8-PSK capable in uplink direction.
4.16.4 Uplink Averaging
Input parameters for averaging are the BEP values that the BTS sends to the PCU in the
Abis L1 frame. The BEP values are:
- VAR_BEP
- MEAN_BEP
The RLC reads the BEPs from the uplink RLC data block. In the case of uplink control
block the MAC sends the BEPs to the RLC using rlc_ul_ctrl_bep_ind__r.
The RLC activates averaging for TBF when the RLC receives the rlc_mac_data_ind__r or
rlc_ul_ctrl_bep_ind__r for the TBF.
Uplink averaging produces BEP values for link adaptation algorithm.
Uplink averaging consists of three phases as follows
- Decoding L1 data
- Averaging of the decoded L1 data
- BEP value calculating from the averaged data
Author Approved by
Uplink radio block is received
START
Decode L1 data
Do averaging
Calculate BEPs
READY
Figure. Uplink averaging
4.16.4.1 Decoding L1 data
During EGPRS uplink TBF transfer, the BTS measures the received signal quality and
reports the measurement data to the PCU in Abis L1 inband signaling. Before the reported
values can be used for averaging the RLC converts them as follows [AbisL1]:
VAR_BEP CV_BEP
received from BTS
0 0.25
1 0.75
2 1.25
3 1.75
Table. An incoming VAR_BEP value is converted into CV_BEP.
MEAN_BEP MEAN_BEP_gmsk MEAN_BEP_8psk

received from BTS (if GMSK MCS used) (if 8-PSK MCS used)
0 0.0002 0.00025
1 0.0005 0.00075
2 0.0008 0.0015
3 0.0015 0.0035
4 0.0025 0.0075
5 0.0035 0.0155
6 0.0050 0.0325
7 0.0080 0.0565
8 0.0130 0.076
9 0.0205 0.0915
10 0.0325 0.11
Author Approved by
11 0.0515 0.13
12 0.0815 0.155
13 0.1300 0.19
14 0.2050 0.23
15 0.2900 0.275
Table. An incoming MEAN_BEP value is converted for GMSK or 8-PSK depending on
MCS used.
4.16.4.2 Averaging
The PCU performs the same averaging as specified in 05.08 for the MS. [05.08, 10.2.3
and 10.2.4]
The PCU averages the quality parameters of the block individually per TBF and per
modulation type as follows [05.08]:
R n (1 e) R n 1 e
e e
MEAN_BEP_TN n (1 ) MEAN_BEP_TN n 1 MEAN_BEPblock,n
Rn Rn
e e
CV_BEP_TN n (1 ) CV_BEP_TN n 1 CV_BEPblock,n
Rn Rn
Where: n is the iteration index, incremented per each uplink radio block for TBF.
Rn denotes the reliability of the filtered quality parameters.

In the PCU R-1 = 0.25.
e is the forgetting factor. The PCU defines e using BEP_PERIOD [05.08].

The PCU receives BEP_PERIOD from DX as bep_period_t, which range is
0..10. The PCU defines e using the table below.
Value from DX 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
BEP_PERIOD Reserved 25 20 15 12 10 7 5 4 3 2 1
e - 0.08 0.1 0.15 0.2 0.25 0.3 0.4 0.5 0.65 0.8 1
4.16.4.2.1 Error cases
Error cases:
- block with bad header = block without quality parameters

- block with wrong TFI
- block with wrong TLLI
- block with invalid data content (LI field etc)
In the error cases listed above only the R of current modulation is calculated per TBF as
follows [05.08]:
R n (1 e) R n 1
Author Approved by
Note1: If current modulation cannot be read from the frame then the modulation is defined
as the last commanded MCS.
Note2: a block with bad frame indicator (BFI=1) is used for averaging. It is not an error
case.
4.16.4.3 BEP value calculating
If GMSK MCS was used then new GMSK_MEAN_BEP and GSMK_CV_BEP are defined
from the averaged values using the table below [05.08, 8.25].
Log10(MEAN_BEP_TN) GMSK_MEAN_BEP
-0.6 < log 0
-0.7 < log <= -0.6 1
-0.8 < log <= -0.7 2
-0.9 < log <= -0.8 3
-1.0 < log <= -0.9 4
-1.1 < log <= -1.0 5
-1.2 < log <= -1.1 6
-1.3 < log <= -1.2 7
-1.4 < log <= -1.3 8
-1.5 < log <= -1.4 9
-1.6 < log <= -1.5 10
-1.7 < log <= -1.6 11
-1.8 < log <= -1.7 12
-1.9 < log <= -1.8 13
-2.0 < log <= -1.9 14
-2.1 < log <= -2.0 15
-2.2 < log <= -2.1 16
-2.3 < log <= -2.2 17
-2.4 < log <= -2.3 18
-2.5 < log <= -2.4 19
-2.6 < log <= -2.5 20
-2.7 < log <= -2.6 21
-2.8 < log <= -2.7 22
-2.9 < log <= -2.8 23
-2.0 < log <= -2.9 24
-3.1 < log <= -3.0 25
-3.2 < log <= -3.1 26
-3.3 < log <= -3.2 27
-3.4 < log <= -3.3 28
-3.5 < log <= -3.4 29
-3.6 < log <= -3.5 30
log <= -3.6 31
Table. GMSK_MEAN_BEP [05.08]
If 8-PSK MCS was used then new 8-PSK _MEAN_BEP and 8-PSK _CV_BEP are defined
from the averaged values using the table below [05.08, 8.25].
Author Approved by
Log10(MEAN_BEP_TN) 8-PSK _MEAN_BEP

-0.6 < log 0
-0.64 < log <= -0.60 1
-0.68 < log <= -0.64 2
-0.72 < log <= -0.68 3
-0.76 < log <= -0.72 4
-0.80 < log <= -0.76 5
-0.84 < log <= -0.80 6
-0.88 < log <= -0.84 7
-0.92 < log <= -0.88 8
-0.96 < log <= -0.92 9
-1.00 < log <= -0.96 10
-1.04 < log <= -1.00 11
-1.08 < log <= -1.04 12
-1.12 < log <= -1.08 13
-1.16 < log <= -1.12 14
-1.20 < log <= -1.16 15
-1.36 < log <= -1.20 16
-1.52 < log <= -1.36 17
-1.68 < log <= -1.52 18
-1.84 < log <= -1.68 19
-2.00 < log <= -1.84 20
-2.16 < log <= -2.00 21
-2.32 < log <= -2.16 22
-2.48 < log <= -2.32 23
-2.64 < log <= -2.48 24
-2.80 < log <= -2.64 25
-2.96 < log <= -2.80 26
-3.12 < log <= -2.96 27
-3.28 < log <= -3.12 28
-3.44 < log <= -3.28 29
-3.6 < log <= -3.44 30
log <= -3.6 31
Table. 8-PSK_MEAN_BEP [05.08]
CV_BEP_TN 8-PSK/GMSK CV_BEP

1.75 < cv <= 2.00 0
1.50 < cv <= 1.75 1
1.25 < cv <= 1.50 2
1.00 < cv <= 1.25 3
0.75 < cv <= 1.00 4
0.50 < cv <= 0.75 5
0.25 < cv <= 0.50 6
0.00 < cv <= 0.25 7
Table. CV_BEP [05.08]
Author Approved by
4.16.5 Link Adaptation algorithm
DOWNLINK UPLINK
The BEPs from the The BEPs from Uplink

EGPRS Packet averaging are delivered
Downlink Ack/Nack to adaptation algorithm.
message are delivered
to adaptation algorithm.
Adaptation algorithm
START
Handle missing modulation data
Add user defined mean_bep_offsets
ack unack Define MCS

Define MCS candidate A RLC basing on
basing on BLER limits *) mode? BLER limits *)
Define MCS candidate B *) when defining uplink MCS

using optimal MCS method *) the output of these phases is
a GMSK MCS if the MS is not
8-PSK capable in uplink
Select the smaller of the candidates A and B
Downlink only:
Define retransmission MCS
For CX3.2 only:
Change MCS8/9 to MCS7
Downlink only:
If MS IR memory full then restrict MCSs
READY
Downlink case outputs:

- MCS for initial transmission
- MCS for retransmission
Uplink case output:
- MCS for initial transmission
Figure. Link Adaptation algorithm

Author Approved by
Inputs for algorithm are the BEP values as follows:
- GMSK_MEAN_BEP
- 8-PSK_MEAN_BEP
- GMSK_CV_BEP
- 8-PSK_CV_BEP
Link adaptation algorithm selects MCS using predefined conversion tables based on link
level simulation results [S10LA].
Link adaptation output MCS values are initialized with operator settings for Initial MCS.
If the operator has disabled EGPRS link adaptation then the Link adaptation algorithm
does not change the output MCS values.
If the operator setting for Initial MCS is bigger than max MCS then Initial MCS is replaced
with max MCS.
4.16.5.1 Handling of missing BEP values of one modulation, ack/unack mode
If BEP for only one modulation is available, the RLC estimates BEP for the other
modulation. The table below is used to convert the MEAN_BEP value to the other
modulation. The same CV_BEP value can be used for both modulations.
Reported Estimation for Reported Estimation for

GMSK 8-PSK 8-PSK GMSK
MEAN_BEP MEAN_BEP MEAN_BEP MEAN_BEP
07 0 0 3
89 1 1 8
10 11 2 2 10
12 13 3 3 12
14 15 4 4 14
16 18 5 5 17
19 20 6 6 19
21 23 7 7 22
24 25 8 8 24
26 28 9 9 27
29 30 10 10 29
31 20 11-31 31
Table. Relationship of GMSK and 8PSK mean BEP.
4.16.5.2 Handling of user define offsets, ack/unack mode
The user defined offsets are added to the mean bep values.
GMSK_MEAN_BEP = GMSK_MEAN_BEP + MEAN_BEP_OFFSET_GMSK;
8-PSK_MEAN_BEP = 8-PSK_MEAN_BEP + MEAN_BEP_OFFSET_8-PSK;
Author Approved by
4.16.5.3 MCS selection based on BLER limits, ack/unack mode
There is a table per MCS that maps the pair (MEAN_BEP, CV_BEP) to BLER. The BLER
values for each MCS are searched and compared to the operator parameters "Maximum
BLER acknowledged mode" or "Maximum BLER unacknowledged mode" on whether
the mode is ACKed or UNACKed. The highest MCS that satisfies the BLER limit is
chosen.
The GMSK _MEAN_BEP and GMSK _CV_BEP are used with GMSK BLER tables and 8-
PSK _MEAN_BEP and 8-PSK _CV_BEP are used with 8-PSK BLER tables.
If MS does not support 8-PSK in the uplink, a GMSK MCS is chosen in the uplink.
For UNACKed mode, this is the selected MCS used for all transmissions.
For ACKed mode, the minimum of this value and the value from optimal MCS selection is
the selected MCS for initial transmissions of each new RLC block.
4.16.5.4 Optimal MCS selection for initial transmission, ack mode
START
Modulation
GMSK selection 8-PSK
Get optimal_MCS Get optimal_MCS

from GMSK table from 8-PSK table
READY
Figure. Optimal MCS
4.16.5.4.1 Modulation selection
Modulation is selected first. Modulation selection is based on 8-PSK MEAN_BEP, 8-PSK

CV_BEP and GMSK_MEAN BEP according to the table below. If MS does not support 8-
PSK in the uplink, GMSK is chosen in the uplink.
Author Approved by
8PSK CV_BEP 0 1 2 3 4 5 6 7
8PSKMEAN_BEP
0 4 4 4 4 4 4 4 4
1 6 6 6 6 6 6 5 5
2 9 9 9 9 9 9 7 6
3 31 31 31 31 21 12 11 8
4 31 31 31 31 31 20 13 12
5 31 31 31 31 31 24 21 21
6 31 31 31 31 31 31 31 31 31
Table. GMSK mean BEP limits for modulation selection.
The items in the table above are the 8PSK MEAN_BEP and CV_BEP values. The table is
used as follows: the algorithm locates an entry in the table based on measured 8PSK
MEAN_BEP and CV_BEP values. This entry is compared to the measured to GMSK
MEAN_BEP value. If the measured value is larger GMSK is chosen, otherwise 8PSK is
chosen.
4.16.5.4.2 Optimal MCS selection
After the modulation has been selected the MCS is selected. MCS selection is based on
the MEAN_BEP and CV_BEP of the selected modulation. The tables below are used for
MCS selection.
GMSK_CV_BEP 0 1 2 3 4 5 6 7
GMSK_MEAN_BEP
03 1 1 1 1 1 1 1 1
4 2 2 1 1 1 1 1 1
5 2 2 2 1 1 1 1 1
6 2 2 2 2 2 2 1 1
79 2 2 2 2 2 2 2 2
10 19 3 3 3 3 3 3 3 3
20 31 4 4 4 4 4 4 4 4
Table. MCS selection table for GMSK.
8-PSK_CV_BEP 0 1 2 3 4 5 6 7
8-PSK_MEAN_BEP
03 5 5 5 5 5 5 5 5
4 6 5 5 5 5 5 5 5
5 6 6 5 5 5 5 5 5
6 6 6 6 5 5 5 5 5
7 6 6 6 5 5 5 5 5
8 6 6 6 6 5 5 5 5
9 6 6 6 6 6 5 5 5
10 16 6 6 6 6 6 6 6 6
17 21 7 7 7 7 7 7 7 7
22 25 8 8 8 8 8 8 8 8
26 31 9 9 9 9 9 9 9 9
Table. MCS selection table for 8-PSK.
Author Approved by
4.16.5.5 MCS selection downlink for retransmission, ack mode
For 8-PSK modulation, the table below shows the maximum MCS used for
retransmissions.
8-PSK_CV_BEP 0 1 2 3 4 5 6 7
8-PSK_MEAN_BEP
03 6 6 6 6 6 6 6 6
4 7 7 7 7 7 7 7 7
5 31 9 9 9 9 9 9 9 9
Table. Selection of maximum MCS for retransmissions (only for 8-PSK).
4.16.5.6 MCS reducing for downlink transmission if MS out of memory (IR), ack mode
There is a PRFILE parameter that controls this function. The

PR_NR_T_MEMORY_OUT_FLAG_SUM parameter is used to activate the MS Out of
Memory exception procedure in RLC to reduce the number of MCSs used. Allowed values
for PR_NR_T_MEMORY_OUT_FLAG_SUM are 0 - 7. Value 0 deactivates algorithm use.
During IR operation in downlink packet transfer, MS may report MS Out of Memory

condition in EGPRS PACKET DOWNLINK ACK/NACK Message. If there has been such
report in PR_NR_T_MEMORY_OUT_FLAG_SUM or more consecutive EGPRS PACKET
DOWNLINK ACK/NACK Message the RLC reduces the MCSs given by link adaptation.
The RLC reduces MCSs using the tables below. The reduction is done until MS reports it
has enough memory.
MCS from LA algorithm Reduced MCS

1 1
2 1
3 2
4 3
5 5
6 5
7 6
8 7
9 7
Table. MCS for initial downlink transmission (MS Out of Memory)
MCS from LA algorithm Reduced MCS

6 6
7 6
9 7
Table. MCS for downlink retransmission (MS Out of Memory)
The RLC has internal MEMORY_OUT_FLAG_SUM parameter that is used as follows:
Author Approved by
if (MS reports MS Out of Memory condition) and

(MEMORY_OUT_FLAG_SUM < PR_NR_T_MEMORY_OUT_FLAG_SUM) then
MEMORY_OUT_FLAG_SUM = MEMORY_OUT_FLAG_SUM + 1
if (MS reports MS has enough memory) then

MEMORY_OUT_FLAG_SUM = 0
if (MEMORY_OUT_FLAG_SUM = PR_NR_T_MEMORY_OUT_FLAG_SUM) then

reduce downlink MCSs
4.16.5.7 MCS limiting for CX3.2 BTS software
The CX3.2 software does not support MCS-8 and MCS-9.
The DX SW (PUB/GUP)informs the PCU about max MCS that the RLC is allowed to use
in a cell. In the case of UltraSite CX3.2 the DX sets max MCS to MCS-7, otherwise to
MCS-9. The parameter max MCS is used for this purpose.
If the LA has given bigger MCS than the max MCS then the RLC replaces the MCS with
max MCS. The RLC does it for both initial transmission MCS and retransmission MCS.
If the operator setting for Initial MCS is bigger than max MCS then Initial MCS is replaced
with max MCS.
4.17 Packet Data Handling Interface
New PCU frame types are introduced for EGPRS to be used internally in the PCU for
TBFs in EGPRS territory. The frames are PCU downlink RLC data frame and PCU uplink
RLC data frame. ???
In uplink MCS value is used in RLC radio block decoding phase as the RLC radio block
header format depends on MCS family used in uplink TBF [0460] 10.3a.3. The RLC reads
the MCS from PCU uplink RLC data frame.
In GPRS territory the S9 interfaces are used for data transfer.
4.18 Dependencies on other features
Multi BCF, cell parameters are for SEG
Common BCCH
Author Approved by
Dynamic Abis.
System Level Trace: RLCs TBF release + MCS change are information to trace
Qos
4.19 Capasity
Author Approved by
5. SCENARIOS
5.1 Uplink link adaptation
RLC MAC BTS
uplink data frame, MCS-7

mac_data_ind__r
If bad header or wrong

RLC does TFI then RLC does not
averaging and average beps but RLC
define BEPs updates only R of both
modulations. uplink data frame, MCS-7
mac_data_ind__r
RLC does
averaging and
define BEPs uplink control frame, CS-1
control_bep_ind__r
IIf bad header or wrong

RLC does TFI then RLC does not
averaging and average beps but RLC
define BEPs updates only R of both
(GMSK.) modulations.
Normally RLC sends

LA MCS to MAC.
When RLC
decides to send
In the case of the
ack to MS then
first ack of one phase
RLC runs uplink
access RLC sends
LA procedure to
the user defined initial
define new LA
MCS.
MCS for UL.
mac_ack_req__s
Packet Uplink Ack/Nack, (MCS-5)
uplink data frame, MCS-5
MCS of the frames are shown as an example where the MCS change takes place
Author Approved by
5.2 Downlink link adaptation
RLC MAC BTS
downlink data frame, MCS 6
EGPRS Packet Downlink Ack/Nack

mac_ack_ind__r
RLC runs
downlink LA
procedure to
define new LA
MCSs for DL.
- curr_MCS
- retransmit_MCS
MCS of the frames are shown as an example where the MCS change takes place
Author Approved by
5.3 Scheduling, MCS selection and Dynamic Abis allocation
RLC MAC DAM CHM PFH DSP BTS MS

(scheduler)
Wake-
up
1. sch_init_trx_scheduling__r
MAC messages
are scheduled
2. sch_get_dl_edge_trx_blocks__r
PCCCH 1 tsl per cell,

messages are except PSI1 at
scheduled 650 block
intervals ?????
3. rlc_get_ul_tbf_mcs__r
4. rlc_get_dl_tbf_mcs__r
5. dam_allocate_dl_items_req__r
6. rlc_get_dl_rlc_data_items__r
7. dam_allocate_ul_items_req__r
8. dam_set_dynabis_c_bits_req__r
Author Approved by
1. PFH initializes scheduling of a TRX.
2. PFH asks downlink RLC data frames from CHM.
3. UL/DL scheduling has started. CHM has allocated UL TBFs and DL TBFs on a TRX.
CHM asks RLC the CS/MCS values on UL TSLs of the TRX. The UL MCS the RLC
returns is the highest MCS used during TBF lifetime.
4. CHM asks RLC what are the CS/MCS values RLC wants to use on DL TSLs of the
TRX.
5. CHM asks DAM to allocate DL Abis slave resources for the TRX.
6. CHM asks RLC to make data frame to be sent.
CHM makes dummy control block or idle block for those tsls that are not used by RLC
7. DAM schedules UL Abis pool resources for the TBFs of the TRX. UL transmission turn
is granted only for the TBFs, whose requested Abis pool capacity can be successfully
allocated.
8. DAM fills dynamic Abis C-bits in the frame based on the mcs and pointer_retransmit
fields of the edge_trx_sch_data_dl__t. If pointer_retransmit = TRUE then DAM fills the
bit to indicate only master frame. If pointer_retransmit =FALSE then DAM fills the bits
to indicate master frame + slave frames based on MCS.
See appendix A.
Author Approved by
6. SERVICE DESCRIPTIONS
6.1 New services
6.1.1 Services between CHM and RLC
6.1.1.1 rlc_get_ul_tbf_mcs__r
Primitive: rlc_get_ul_tbf_mcs__r
Direction: CHM/sch calls
Description: Function that returns the CS/MCSs of the UL_TBFs of a TRX.
The returned CS/MCS must be highest possible the MS may use because the DAM uses the information for
uplink dynamic Abis scheduling.
Parameters: Pointer to edge_trx_sch_data_ul__t
- tbf_id
Return value RLC fulfils the edge_trx_sch_data_ul__t
- mcs
6.1.1.2 rlc_get_dl_tbf_mcs__r
Primitive: rlc_get_dl_tbf_mcs__r
Description: Function that returns the MCSs of the DL_TBFs of a TRX. See appendix A.
Parameters: Bpn
Pointer to edge_trx_sch_data_dl__t
Return value RLC fulfils the edge_trx_sch_data_dl__t
6.1.1.3 Rlc_get_dl_rlc_data_items__r
Primitive: rlc_get_dl_rlc_data_items__r
Description: Function that informs RLC about granted MCS for scheduled TBFs. RLC takes granted resources into
account when building RLC data messages. RLC returns pointers to RLC data messages and informs SCH
about the used MCSs. NULL pointers shall be returned for TSLs where RLC couldnt give any radio blocks for
granted resources. See appendix A.
Parameters: Bpn
Return value RLC fulfils the edge_trx_sch_data_dl__t
6.1.2 Services between CHM and DAM
6.1.2.1 Dam_allocate_ul_items_req__r
Primitive: Dam_allocate_ul_items_req__r
Description:
Parameters: Bpn
PCU_TRX_id
Pointer to edge_trx_sch_data_ul__t
- tbf_id
- mcs
Return value Tsls allowed to use (U_int_8, one Bit per tsl)
Author Approved by
6.1.2.2 Dam_allocate_dl_items_req__r
Primitive: Dam_allocate_dl_items_req__r
Description: See appendix A.
Parameters: PCU_TRX_id
Return value DAM fulfils the edge_trx_sch_data_dl__t
6.1.2.3 Dam_set_dynabis_c_bits_req__r
Primitive: Dam_set_dynabis_c_bits_req__r
Description:
Parameters: Bpn
PCU_TRX_id
Pointer to mcs of edge_trx_sch_data_dl__t
Pointer to dl_rlc_data_items of edge_trx_sch_data_dl__t
Return value Success (T/F)
Author Approved by
6.2 New interfaces
6.3 New messages
6.4 Interface modifications
6.5 EGPRS message definitions
6.5.1 Starting sequence number SSN
6.5.2 Determination of SSN
6.5.3 Received block bitmap RBB
6.5.4 Block sequence EGPRS BSN number
6.5.5 Two RLC Radio Block Sequence number
6.5.6 Split Block Indicator
6.5.7 More (M) bit
6.5.8 Length Indicator LI
6.5.9 Receive state array V(N) in EGPRS TBF
6.5.10 Acknowledge State Array V(B) for EGPRS TBF Mode
6.5.11 RLC/MAC control blocks
6.5.12 EGPRS RLC data blocks and RLC/MAC headers
6.5.13 Downlink RLC/MAC control block
Author Approved by
6.5.14 Uplink RLC/MAC control block
6.5.15 EGPRS Downlink RLC/MAC headers
6.5.15.1 Header type 1: header for MCS-7, MCS-8 and MCS-9
6.5.15.2 Header type 2: header for MCS-6 and MCS-5
6.5.15.3 Header type 3: header for MCS-4, MCS-3, MCS-2 and MCS-1
6.5.16 EGPRS Downlink RLC data block
6.5.17 EGPRS Uplink RLC/MAC headers
6.5.17.1 Header type 1: header for MCS-7, MCS-8 and MCS-9
6.5.17.2 Header type 2 : header for MCS-6 and MCS-5
6.5.17.3 Header type 3 : header for MCS-4, MCS-3, MCS-2 and MCS-1
6.5.18 EGPRS Uplink RLC data block
6.5.19 RLC Window size for Egprs
6.5.20 RLC receive window
6.5.21 Bitmap generation
6.5.22 Egprs editorial clarifications
6.5.23 EGPRS Specific ETSI references
6.5.23.1 New messages [Kangas]
6.5.23.2 Changes on messages
6.5.23.3 New information elements
6.5.23.4 Changes on information elements
Author Approved by
7. HANDLING OF EXCEPTION CONDITIONS
Alarm:
No alarms used)
7.1 Alarm Descriptions
Not applicable
Author Approved by
8. COUNTER AND OBSERVATION DESCRIPTIONS
8.1 EGPRS specific statistics
8.1.1 PCU counters
8.1.2 Coding Scheme counters
Author Approved by
9. FILE AND DATA STRUCTURE DESCRIPTIONS
9.1 New datatypes / ABATOR level
9.1.1 mcs__t
typedef u_int8_t mcs__t;
/*
mcs__t: edge_trx_sch_data_dl__t and edge_trx_sch_data_ul__t uses mcs__t
which contains only information/index of CS or MCS. This is possible
because EDAP resource needs for both CSs and MCSs with the same indecies
are the same. Slave channel needs for CSs and MCSs using same indecies:
CS-1 0 no slaves
CS-2 1 1 slave
CS-3 2 1 slave
CS-4 3 1 slave
MCS-1 0 - no slaves
MCS-2 1 1 slave
MCS-3 2 1 slave
MCS-4 3 1 slave
MCS-5 4
MCS-6 5
MCS-7 6
MCS-8 7
MCS-9 8
*/
/* Coding Schemes and EGPRS Modulation and Coding Schemes */

#define CS_1 0
#define CS_2 1
#define CS_3 2
#define CS_4 3
#define CS_INVALID 0xff
#define MCS_1 0
#define MCS_2 1
#define MCS_3 2
#define MCS_4 3
#define MCS_5 4
#define MCS_6 5
#define MCS_7 6
#define MCS_8 7
#define MCS_9 8
#define MCS_5_7 9
#define MCS_6_9 10
Author Approved by
9.1.2 edge_trx_sch_data_ul__t
typedef struct {
tbf_id__t tbf_id[MAX_NR_OF_TSLS_IN_TRX__C];
/* PCU_INVALID_TBF_ID__C if no TBF for that tsl */
mcs__t mcs[MAX_NR_OF_TSLS_IN_TRX__C];
} edge_trx_sch_data_ul__t;
9.1.3 edge_trx_sch_data_dl__t
typedef struct {
tbf_id__t tbf_id[MAX_NR_OF_TSLS_IN_TRX__C];
/* PCU_INVALID_TBF_ID__C if no TBF for that tsl */
u_int8_t retransmit[MAX_NR_OF_TSLS_IN_TRX__C];
/* 0 = no retransmission;
initial transmission or no transmission
1 = retransmission of NACKED block
2 = retransmission of PENDING block */
boolean__t pointer_retransmit[MAX_NR_OF_TSLS_IN_TRX__C];
/* False = initial/retransmission from PCU
True = retransmission from BTS
*/
mcs__t mcs[MAX_NR_OF_TSLS_IN_TRX__C];
boolean__t poll_allowed[MAX_NR_OF_TSLS_IN_TRX__C]; /* Poll allowed in RLC
True = allowed
False = not allowed */
poll_req__t* poll_req[MAX_NR_OF_TSLS_IN_TRX__C]; /* Poll data description.
Not used with EGPRS TBF */
rat_id__t rat_id[MAX_NR_OF_TSLS_IN_TRX__C]; /* S9 */
byte meas_req[MAX_NR_OF_TSLS_IN_TRX__C];
/* Rx lev measurement request
0 = not requested
1 = requested */
boolean__t trx_realloc[MAX_NR_OF_TSLS_IN_TRX__C];
/* True = TBF allocated to other TRX
False = TBF is on the same TRX as last time */
byte* dl_rlc_data_frames[MAX_NR_OF_TSLS_IN_TRX__C];
/* Pointers to DL RLC data frames,
NULL if no RLC data block for that tsl */
} edge_trx_sch_data_dl__t;
Author Approved by
10. OPERATOR INTERFACE
10.1 Operator parameters
The PCU receives operator settings as DX messages.
Link adaptation related MML parameters [DXEGPRS]. The DX sends them to PCU in
pcu_seg_params_rnwdb_s message:
- BEP PERIOD
- Initial MCS for acknowledged mode
- Initial MCS for unacknowledged mode
- Maximum BLER in acknowledged mode
- Maximum BLER in unacknowledged mode
- mean BEP offset GMSK
- mean BEP offset 8PSK
- EGPRS link adaptation enabled
PRFILE parameters. The DX sends them to PCU/CHM in pcu_parameters_s message:
- PR_NR_T_MEMORY_OUT_FLAG_SUM, allowed values are 0-7. (For link adaptation)

class 46 PRFILE parameters
Parameter Default
Parameter number value
PR_NR_T_EGPRS_UPLINK_PENALTY 47 1
PR_NR_T_EGPRS_UPLINK_THRESHOLD 48 25
PR_NR_T_EGPRS_DOWNLINK_PENALTY 49 1
PR_NR_T_EGPRS_DWNLINK_THRESHOLD 50 25
10.1.1 CHM / MAC parameters
GPRS and EGPRS operator defined parameters shall be received to PCU CHM using
pcu_bts_params_rnwdb message from PUBDAT. [Tervonen,Mielonen, Vihanti] 7.1.6.
BSC level parameters shall be received to PCU CHM using pcu_bsc_params_rnwdb_s

message from PUBDAT, [Tervonen,Mielonen, Vihanti] 7.1.4.
Confirmation message is sent to DX PUBDAT after CHM updated received data context using
pcu_bts_params_rnwdb_ack_s or pcu_bsc_params_rnwdb_ack_s with confirmation status, [Tervonen,
Mielonen, Vihanti] 7.1.3.
Author Approved by
S9: DX -> MAC

S10: DX -> CHM -> MAC & RLC
Author Approved by
11. INSTALLING AND TESTING
11.1 Configuration requirements
11.2 Implementation instructions
11.2.1 Measurement mode
11.2.2 Reallocation parameters
11.3 User operations and parameters used
11.4 Remarks
11.4.1 Documentation change requests to ETSI
11.4.2 ITU T.4 compression table
11.4.3 Performance notes
11.4.3.1 Timer use in reallocation activation
11.5 Open items
11.5.1 BTS selection in segment
11.5.2 Uplink Rx-lev reallocation
11.5.3 Uplink initial MCS
11.6 Testing and verification
Author Approved by
APPENDIX A. Usage of the edge_trx_sch_data_dl__t
CHM reserves space for the data structure. RLC and DAM use the structure via pointer
given by CHM. Also PFH reads dl_rlc_data_frames and MAC writes dl_rlc_data_frames.
1. CHM owns space for the data structure and initializes parts of it before calling
rlc_get_dl_tbf_mcs__r.
Field VALUE CHM

tbf_id[8] TBF_id or write
PCU_INVALID_TBF_ID__C
retransmit[8] - -
Pointer_retransmit[8] - -
mcs[8] - -
poll_allowed[8] TRUE / FALSE write
Poll_req[8] - -
rat_id[8] Rat-id write
Meas_req Requested or not write
Trx_realloc[8] TRUE / FALSE write
dl_rlc_data_frames[ 8] NULL Write
Tbf_id: Tbf_id = TBF_ID if the TSL is allocated for a TBF.
Tbf_id = PCU_INVALID_TBF_ID__C if the TSL is allocated

for control message.
In case where TBF_ID for RTSL is set to

PCU_INVALID_TBF_ID__C value, other RTSL specific field
shall not be used as valid information for EGPRS data
scheduling. Same procedure applies for both
edge_trx_sch_data_dl__t and edge_trx_sch_data_ul__t. For
example dl_rlc_items field of RTSL containg DL frame
pointer must not be set to NULL. Otherwise information
filled by CHM for example DL control block may get lost
Poll_allowed:
TRUE if RLC is allowed to poll. FALSE if CHM has

scheduled the uplink TSL for some other purpose.
Meas_req:
Meas_req=1 if CHM wants measurement report from MS. The

RLC remembers if meas_req has been 1 and the RLC asks the
report when polling next time.
Trx_realloc:
TRUE, if the TBF is reallocated to other TRX starting

from current BPN. It is TRUE only in the reallocation
moment.
Pointer retransmission feature in the RLC needs this

information.
dl_rlc_data_frames:
CHM initializes with NULL
Author Approved by
2. RLC operations during rlc_get_dl_tbf_mcs__r
Field VALUE RLC

tbf_id[8] TBF_id or Read
retransmit[8] NO / NACK / PENDING write
pointer_retransmit [8] TRUE / FALSE write
mcs[8] MCS wanted to use write
poll_allowed[8] TRUE / FALSE Read
Poll_req[8] - -
rat_id[8] Rat-id
Meas_req Requested or not Read
Trx_realloc[8] TRUE / FALSE read
dl_rlc_data_frames[ 8] NULL -
Retransmit:
The RLC fills NO / NACK / PENDING.
Pointer_retransmit:
The RLC sets pointer_retransmit = TRUE if the block is

transmitted from the BTS memory. Otherwise the sets
pointer_retransmit = FALSE. By setting pointer_retransmit =
TRUE the RLC indicates to the DAM that no EDAP resources shall
be allocated for the RTSL in the DAM.
Mcs: range 0..8
MCS selected by RLC. RLC fills this field also when

pointer_retransmit =TRUE.
If polling is not allowed and RLC need to poll, the RLC sets
MCS to MCS-1. By setting MCS to MCS-1 the RLC indicates to DAM
that no EDAP resources shall be allocated for the RTSL in DAM.
Meas_req:
When active ( > 0) measurement request received, RLC requests

measurement data in next DL ack message.
Trx_realloc:
If the TBF is reallocated to other TRX then the RLC cannot use
pointer retransmission for the blocks sent before the
reallocation.
Author Approved by
3. CHM operations before calling dam_allocate_dl_items_req__r
Field VALUE CHM

tbf_id[8] TBF_id or read
retransmit[8] NO / NACK / PENDING read
Pointer_retransmit [8] TRUE / FALSE -
mcs[8] MCS Read/writ
e
poll_allowed[8] TRUE / FALSE -
Poll_req[8] - -
rat_id[8] Rat-id -
Meas_req Requested or not -
Trx_realloc[8] TRUE / FALSE -
Mcs: range 0..8
CHM limits MCS if needed. For example if there is a GPRS

TBF in uplink then the CHM sets MCS-4.
In the case of retransmitted 8-PSK NACK block, the CHM

should not limit MCS to GMSK because the RLC cannot
perform retransmission of RLC data originally sent with
8-PSK MCS with GMSK MCS in any situation.
Author Approved by
4. DAM operations during dam_allocate_dl_items_req__r
Field VALUE DAM

retransmit[8] NO / NACK / PENDING Read
Pointer_retransmit [8] TRUE / FALSE read
mcs[8] MCS fitted on Abis Read/writ
e
Poll_req[8] - -
rat_id[8] Rat-id -
Retransmit & pointer_retransmit:
DAM priorizes retransmissions of NACKED blocks over other

transmissions - No special handling for retransmissions of PENDING
blocks.
In case where the RLC requires retransmission for NACKED block(s)

using MCS-7 and pointer_retransmit = FALSE the DAM shall try to
allocate at least MCS-5 for RTSL(s). In case where the RLC requires
retransmission for NACKED block(s) using MCS-8 or MCS-9 and
pointer_retransmit = FALSE the DAM shall try to allocate at least
MCS-6 for RTSL(s). Otherwise RLC cannot perform retransmission at
all and no data can be sent on the specific RTSL.
If pointer_retransmit = TRUE the DAM allocates only master and does

not modify the mcs field.
Mcs:
Input:
Wanted MCS set by RLC or CHM.
Output:
If pointer_retransmit =FALSE then MCS selected by DAM. DAM must not

select a higher MCS than the input mcs is.
If pointer_retransmit =TRUE then the MCS selected by RLC.
Author Approved by
5. RLC operations during rlc_get_dl_rlc_data_items__r
field VALUE RLC

retransmit[8] NO / NACK / PENDING read?
pointer_retransmit [8] TRUE / FALSE Read/writ
e
mcs[8] Selected MCS Read/writ
e
poll_allowed[8] TRUE / FALSE read
Poll_req[8] Not/normal/access/extra write
rat_id[8] Rat-id read
dl_rlc_data_frames[ 8] pointer to frame / NULL write
Mcs:
Input:
Highest MCS that can be used based on Abis resources.
Exception: If pointer_retransmit =TRUE and the RLC does not use

pointer retransmission then RLC can use only MCS-1.
Output:
MCS selected by RLC. RLC must not select a higher MCS than the input
mcs is. If RLC cannot send any data the RLC does not update mcs.
Then mcs value is undefined.
Pointer_retransmit:
The RLC updates pointer_retransmit field. The RLC writes C7 bit in

the PCU downlink RLC data frame.
Poll allowed:
Poll allowed = TRUE if RLC is allowed to poll. Poll allowed = FALSE

if CHM has scheduled the uplink TSL for some other purpose.
Poll_req:
GPRS: If RLC requests polling then CHM fills SP bit in DL

frame, and ULST bit in UL frame.
EGPRS: If RLC requests polling then CHM fills ULST bit in UL

frame. RLC fills ESP bits itself in DL frame.
Rat_id:
RLC need this when calling some CHM functions.
dl_rlc_data_frames:
This is pointer to PCU downlink RLC data frame if RLC sends data.
Author Approved by
It is NULL if RLC cannot send any data, for example because the mcs
allowed is too low, or polling is not allowed.
If it is NULL then CHM does a dummy control block or idle block. CHM
must set mcs=MCS-1 so that DAM can fill C-bits for dynamic abis
correctly. CHM does not update tbf-id= PCU_INVALID_TBF_ID__C. For
control and idle blocks, CHM fills C7 = 0 in the PCU downlink RLC
data frame.
6. DAM operations during dam_set_dynabis_c_bits_req__r
field VALUE DAM

tbf_id[8] TBF_id or -
retransmit[8] NO / NACK / PENDING -
pointer_retransmit [8] TRUE / FALSE -
mcs[8] Selected MCS Read
Poll_req[8] Not/normal/access/extra -
rat_id[8] Rat-id -
dl_rlc_data_frames[ 8] pointer to frame / NULL Read/writ
e
Mcs:
MCS selected by RLC or CS-1 selected by CHM.
DAM fills C46-C54 in the PCU downlink RLC data frame:
If mcs = MCS-1/CS-1 then DAM fills C46-C54 with zeroes.
If (mcs = MCS-2..9) and (C7 = pointer_present) then DAM fills

C46-C54 with zeroes
else DAM fills C46-C54 according to amount of slave channels
used.
DAM fills C55-C63 UL dynabis allocations according to the previous

block period scheduling information due to the BTS UL decoding
delay.
Author Approved by

Egprs Is 1.4.0

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Egprs Is 1.4.0

Transféré par

Droits d'auteur :

Formats disponibles

ENHANCED GPRS IN PCU S10.

Version Author/Checked by Approved by Feature Number Pages

Draft 0.0.1 9.6.2000 All Modified after internal review

Draft 0.2.0 23.8.2000 4 CHM territory updated modified

Draft 0.3.0 10.10.2000 Version for review updated

Draft 0.3.1 11.10.2000 4 TBF resource change to MS removal proposed by P. Gronberg

Draft 0.4.1 07.11.2000 4.8 Territory procedures modified

Draft 0.4.2 Link Adaptation operator parameters updated

Draft 0.4.3 13.12.00 Version for review updated

1.0.0 16.02.2001 4.6.1.1 BTS selection chapters modified

1.1.0 8.3.2001 4.7.3 Territory balance modified

1.2.0 Interfaces to BSSGP modified

Draft 1.4.0 14 Jun 2002 All Updated

4.13.2 Data block selection...................................................................................................29

7.1 Alarm Descriptions............................................................................................................... 69

Red texts unclear things

CHM Channel Management, CHM program block

CCU Channel Coded Unit

BEP Bit Error Probability

TLLI Temporary Logical Link Identity. Identifies the MS.

LLC Logical Link Layer

MAC Medium Access Control, MAC program block

RLC Radio Link Control, RLC program block

RLC Radio Block RLC data with RLC/MAC header included

RLC Data Block RLC data without RLC/MAC header

PFH Packet Frame Handler, PFH program block

ITFI Internal Temporary Flow Identifier

TFI Temporary Flow Identifier.Assigned for TBF by the network.

More complete glossary is described in PCU S10 Glossary

[PBCCHIS] PBCCH/PCCCH IN PCU, Implementation Specification,

[Kangas] Enhanced GPRS Requirement specification,

[DXEGPRS] PBCCH/PCCCH in BSC & EGPRS in DX, Implementation Specification,

[DAM IS] Dynamic Abis in PCU S10 Implementation Specification,

[04.60] 04.60 ver 8.10-0

[CX3.2] CX3 BTS SW, CX3.2 CHDSP SW Incremental Redundancy,

[AbisL1] GPRS/EGPRS Abis L1, Interface Specification,

[PCUIF] PCU S10 Interface document

[CX3.2] CX3.2 CHDSP SW, INCREMENTAL REDUNDANCY FUNCTIONAL

[RLCS9DD] 09774_3 GPRS PCU RLC SW Design Specification,

[RLCS9IS] GPRS PCU RLC, Implementation Specification,

[S10LA] S10 Link Adaptation: Algorithm and Parameters,

DAM DSP TRX FR

DSP data PCU

DSP driver HDLC driver

3. SELECTION OF THE ARCHITECTURE ALTERNATIVE

4.1 EGPRS interface to BSSGP

4.2 Message encoding and decoding

4.3 EGPRS Packet Control Messages

TBF creation [PBCCHIS]

4.4.2 GPRS and EGPRS TBF multiplexing

4.5 MS RX-lev update

4.6 GPRS/EGPRS BTS selection

Now in S10.5 level?, some EGPRS things is missing??

4.6.1 Initial BTS selection

Select the BTS that

Select BTSs whose frequency band is included in the MS RAC

MS is EGPRS capable MS is not EGPRS capable

Is there any EGPRS Is there any EGPRS

Is there any EGPRS Is there any EGPRS

RETURN: No BTS found RETURN: No BTS found

Remove EGPRS Remove EGPRS

C-value is C-value ? C-value is not

=> BTS_LIST_2 => BTS_LIST_2