(E) GPRS - Radio Interface - Physical Link LayerB8

Site EVOLIUM SAS
VELIZY
(E)GPRS - Radio interface - Physical link layer
Originators
Stanislas Bourdeaut <RELEASE B8>
System : ALCATEL 900/BSS

Sub-system : SYS-TLA
Document Category : PRODUCT DEFINITION
ABSTRACT
This document describes the Physical Link Layer of the air interface for GPRS and EGPRS, covering
release B8.
Approvals
Name J. ACHARD R.Sabelleck E. Brigant
App. SYT CCM BTS CCM B8 SYT DPM
Name
App.
ED 04 Released (E)GPRS - Radio interface - Physical link layer
EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 1/81

10/12/2003
REVIEW
Ed. 01 Released 05/11/2002 Review in the MND/MRA/TD/SYT/SBO/203133 document.
Ed. 02 Released 17/01/2003 Review in the MND/MRA/TD/SYT/SBO/202251_1

document.
Ed 03 Released 27/05/2003 Integration of CR 3BKA20CBR126483_2
HISTORY
Ed. 01 Proposal 01 05/09/2002 Document Creation for B8.
Ed. 01 Proposal 02 30/10/2002 Corrections after email review
Alignment on EGCH primitives and procedures
Ed. 01 Released 05/11/2002 Corrections after email review: naming of EGCH

primitives and entities, editorial corrections, transmit
power and Packet Control Dummy block clarifications
(open points for Package 6)
Ed. 02 Proposal 01 06/12/2002 Introduction of TRE transmit power handling
Introduction of the mapping table from meanBEP to

RXQUAL
Clarification on the Page Mode IE.
Ed. 02 Released 17/01/2003 Email review
Alignment on the conclusions of the 18/12/2002

meeting, summarized in the
MND/MRA/TD/SYT/SBO/202251_1 document.
Ed. 03 Proposal 1 30/04/2003 Email review
Editorial corrections
Introduction of Package 5 CR, 3BKA20CBR123749:

CS4 RXQUAL estimation based on the CRC.
Ed 03 Released 27/05/2003 Replacement of the clauses changed in Package 5

CR, 3BKA20CBR123749 (CS4 RXQUAL estimation
based on the CRC) by the Package 6 CR
3BKA20CBR126483_2
Ed 04 Released 10/12/2003 CR 133427 is taken into account.

10/12/2003
TABLE OF CONTENTS
1 OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER......................................................... 7

1.1 Layer location ..................................................................................................................... 7
1.2 Layer characteristics .......................................................................................................... 8
1.2.1 GPRS ......................................................................................................................... 8
1.2.2 EGPRS..................................................................................................................... 11
1.3 Overview description of layer services ........................................................................... 14
1.3.1 Services provided by Physical RF layer .................................................................... 14
1.3.2 Services provided by Physical Link Layer ................................................................. 14
1.3.3 Services required from Layer Management Plane..................................................... 15
1.3.4 Physical Layer Performance ..................................................................................... 15
2 INTERFACES ............................................................................................................................ 15
2.1 Radio interface description.............................................................................................. 15
2.2 BTS-Relay ......................................................................................................................... 16
3 LAYER FUNCTIONS ................................................................................................................. 16
3.1 PDCH activation - Initial synchronisation ....................................................................... 16
3.1.1 PDCH activation and initial synchronisation in GCH mode ........................................ 16
3.1.2 PDCH activation and initial synchronisation in EGCH mode...................................... 17
3.2 Traffic handling ................................................................................................................ 18
3.2.1 Traffic handling in GCH mode................................................................................... 18
3.2.2 Traffic handling in EGCH mode ................................................................................ 20
3.2.3 BTS transmit power .................................................................................................. 23
3.3 Continuous synchronisation to the radio interface........................................................ 26
3.3.1 Continuous synchronisation in GCH mode ................................................................ 26
3.3.2 Continuous synchronisation in EGCH mode .............................................................. 27
3.4 Radio measurements........................................................................................................ 27
3.4.1 Uplink measurements in GCH mode ......................................................................... 28
3.4.2 Uplink measurements in EGCH mode....................................................................... 29
3.4.3 Timing advance estimation for the continuous update timing advance procedure...... 30
3.5 Continuous timing advance update procedure .............................................................. 30
3.6 Frequency offset correction............................................................................................. 30
4 PROTOCOL LAYER STRUCTURE ........................................................................................... 31
4.1 Layer structure model ...................................................................................................... 31
4.2 Overview of layer functional model ................................................................................. 33
4.3 Overview of layer interfaces............................................................................................. 34
5 SERVICE PRIMITIVE DEFINITION ........................................................................................... 36
5.1 List of service primitives provided by the layer.............................................................. 36
5.1.1 Primitives provided to the BTS-Relay entity (GCH mode and EGCH mode).............. 36
5.1.2 Mapping of PLL service primitives to EGCH primitives and messages...................... 36
5.1.3 Primitives provided to other (PLL) entities................................................................. 37
5.2 Detailed description of service primitives provided by the layer .................................. 37
5.2.1 Service primitives provided to the BTS-Relay entity (GCH mode and EGCH mode) . 37
6 DEFINITION OF LAYER PROTOCOL....................................................................................... 49
6.1 Peer to peer protocol description.................................................................................... 49
6.1.1 Continuous timing advance update procedure........................................................... 49
6.2 PDU definition................................................................................................................... 50
6.2.1 PTCCH downlink block format .................................................................................. 50
6.2.2 PTCCH uplink block formats ..................................................................................... 52
6.2.3 Dummy block transmission ....................................................................................... 52
7 LAYER DYNAMIC MODEL........................................................................................................ 54
7.1 Inter-entities communication ........................................................................................... 54

10/12/2003
7.1.1 Packet radio resource handling (GCH mode and EGCH mode)................................. 54
7.1.2 Data transfer (GCH mode) ........................................................................................ 55
7.1.3 Data transfer (EGCH mode)...................................................................................... 57
7.2 Entities detailed description ............................................................................................ 61
7.2.1 PRH detailed description........................................................................................... 61
7.2.2 TRN detailed description........................................................................................... 61
7.2.3 PCC detailed description........................................................................................... 64
8 SYSTEM PARAMETERS........................................................................................................... 75
10 GLOSSARY AND ABBREVIATIONS......................................................................................... 77

10/12/2003
INTERNAL REFERENCED DOCUMENTS
Not applicable
REFERENCED DOCUMENTS
Proprietary documents
[1] 3BK 11202 0xxx DSZZA GPRS Telecom presentation
[2] 3BK 11202 0370 DSZZA MFS-BTS interface: EGCH stack
[3] 3BK 11202 0369 DSZZA FBS GPRS Radio interface MAC sublayer
[4] 3BK 11202 0368 DSZZA FBS GPRS Radio Interface - RLC Sublayer
[5] 3BK 11202 0366 DSZZA FBS GPRS Radio interface - RRM sublayer (PRH)
[6] 3BK 11202 0367 DSZZA FBS GPRS Radio interface - RRM sublayer (PCC)
[7] 3BK 11202 0084 DSZZA BSS telecom parameters
[8] 3BK 11202 0083 DSZZA GPRS counters catalogue
[9] 3BK 11204 0298 DSZZA Interface O&M Abis Interface specification
3GPP documents
[10] 03.64 Overall description of the GPRS radio interface
[11] 05.01 Physical layer on the radio path; general description
[12] 05.03 Channel coding
[13] 05.05 Radio transmission and reception
[14] 05.10 Radio subsystem synchronization
RELATED DOCUMENTS
PREFACE

10/12/2003
OPEN POINTS / RESTRICTIONS
None.

10/12/2003
1 OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER
1.1 Layer location
Within the BSS: The Physical link layer is part of the Physical layer and located within the BTS
subsystem.
Within the BTS subsystem: the Physical link layer is located within the user and control plane. It
interfaces with:
(L2-GCH) or (EGCH) for communication with MFS.
With layer management plane for O&M interactions.
With the Physical RF layer for communication over the air interface.
Depending on the configuration and protocol stack chosen for the Abis link the BTS can be operated
in GCH or EGCH mode. In GCH mode, the GCH protocol stack defined in Ref [2]] is used on the Abis
interface. In addition to circuit switched services, it allows for the transmission of GPRS Step 1 (CS-1,
CS-2) traffic on the basis of 16 kbit/s nibbles on the Abis interface.
User & Control Plane
BTS-
RELAY
Physical L2-GCH
Link Layer
Physical L1-GCH
RF Layer
Fig. 1: BTS Layers, GCH mode

10/12/2003
In EGCH mode, packet switched traffic can be GPRS (CS-1 to CS-4) or EGPRS (CS-1, MCS-1 to
MCS-9) traffic. It is transmitted over several Abis 16 kbit/s nibbles.channels which are statically
allocated to the TREs: each set of Abis 16 kbit/s nibbles may be used by one and only one PDCH of a
TRE [2].
User & Control Plane
BTS-
RELAY
Physical L2-EGCH
Link Layer
Physical L1-EGCH
RF Layer
Fig. 2: BTS Layers, EGCH mode
In this document, only the Physical Link Layer (PLL) and BTS-Relay Functions are covered. For a
more detailed description of the physical RF layer see [13], for details on GCH and EGCH see [[2].
1.2 Layer characteristics
1.2.1 GPRS
In GPRS, packetised non-real-time data is served in addition to traditional GSM circuit-switched

services. Separation between packet-switched and circuit-switched traffic is based on the use of
different time slots. Time slots used for packet-switched traffic are called packet data channels
(PDCH).
Packets to be transmitted over the air interface are segmented into radio blocks which are transmitted
in 4 bursts in 4 subsequent TDMA frames over the air interface.

10/12/2003
1.2.1.1 Block structure
Different Radio Block structures for data transfer and control message transfer purposes are defined.
For GPRS, a Radio Block for data transfer consists of one MAC Header, one RLC header and one
RLC Data Block. It is always carried by four normal bursts.
Radio Block
MAC header RLC header RLC data BCS
Figure 3: Radio Block structure for data transfer for GPRS
The MAC header contains control fields which are different for uplink and downlink directions. The
MAC header has constant length, 8 bits.
The RLC header contains control fields which are different for uplink and downlink directions. The
RLC header has variable length.
The RLC data field contains octets from one or more LLC PDUs.
The Block Check Sequence (BCS) is used for error detection.
For GPRS (and EGPRS), a Radio Block for control message transfer consists of one MAC header
and one RLC/MAC Control Block. It is always carried by four normal bursts.
Radio Block
MAC header RLC/MAC Control Message BCS
Figure 4: Radio Block structure for control message for GPRS and EGPRS
The MAC header contains control fields which are different for uplink and downlink directions. The
MAC header has constant length, 8 bits.
The Block Check Sequence (BCS) is used for error detection.
The RLC/MAC Control message field contains one RLC/MAC control message.
1.2.1.2 Channel coding
Four coding schemes, CS-1 to CS-4, are defined for the GPRS packet data traffic channels. For all
other GPRS packet control channels than Packet Random Access Channel (PRACH) and Packet
Timing Advance Control Channel on Uplink (PTCCH/U), coding scheme CS-1 is always used. For
access bursts on PRACH, two coding schemes are specified.

10/12/2003
Radio Block
USF BCS
rate 1/2 convolutional coding
puncturing
456 bits
Figure 5: Radio Block structure for CS-1 to CS-3
Radio Block
USF BCS
block
no coding
code
456 bits
Figure 6: Radio Block structure for CS-4
The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection.
For CS-1 - CS-3, the second step consists of pre-coding USF (except for CS-1), adding four tail bits
and a half rate convolutional coding for error correction that is punctured to give the desired coding
rate.
For CS-4 there is no coding for error correction.
The details of the codes are shown in table 1.

Table 1: Coding parameters for the GPRS coding schemes.
Scheme Code rate USF Pre-coded Radio BCS Tail Coded Punctured Data rate
USF Block bits bits kb/s
excl. USF
and BCS
CS-1 1/2 3 3 181 40 4 456 0 9.05

CS-2 2/3 3 6 268 16 4 588 132 13.4
CS-3 3/4 3 6 312 16 4 676 220 15.6
CS-4 1 3 12 428 16 - 456 - 21.4

10/12/2003
1.2.1.3 Radio Measurements
A procedure shall be implemented in the BSS to monitor the uplink Rx signal level and quality on
each uplink PDCH.
1.2.2 EGPRS
1.2.2.1 Introduction
The EGPRS concept has been established for the purpose of enabling the support of data
transmission at a bit rate exceeding the capabilities of GPRS. Basically, EGPRS relies on new
modulation and coding schemes on the air interface allowing for a data throughput optimised with
respect to radio propagation condition ("Link Adaptation").
The basic principle of link adaptation is to change the Modulation and Coding Schemes (MCS)
according to the radio conditions. When the radio conditions worsen, a more protected MCS (more
redundancy) is chosen leading to a lower throughput. On the contrary, when the radio conditions
become better, a less protected MCS (less redundancy) is chosen leading to a higher throughput.
1.2.2.2 Block structure
The Radio Block structure for data transfer is different for GPRS and EGPRS, whereas the same
Radio Block structure is used for control messages.
For EGPRS, a Radio Block for data transfer consists of one RLC/MAC header and one or two RLC
Data Blocks. It is always carried by four normal bursts. The interleaving depends on the MCS used.
Radio Block
RLC/MAC header HCS RLC data BCS
Figure 7: Radio Block structure for data transfer for EGPRS
The RLC/MAC header contains control fields which are different for uplink and downlink directions.
The RLC/MAC header has variable length.
The RLC data field contains octets from one or more LLC PDUs.
The Block Check Sequence (BCS) is used for error detection of the data part.
The Header Check Sequence (HCS) is used for error detection of the header part.
The header part is independently coded from the data part and has its own check sequence. Tail
biting (i.e. no explicit tail bits are appended before encoding. The encoder is initialised with the last
information bits enabling tail biting decoding in the receiver) is used to reduce the size of the header.

10/12/2003
1.2.2.3 Modulation and coding
Nine modulation and coding schemes are proposed for enhanced packet data communications
(EGPRS), providing raw RLC data rates ranging from 8.8 kbit/s (minimum value under the worst radio
propagation conditions per timeslot) up to 59.2 kbit/s (maximum value achievable per timeslot under
the best radio propagation conditions). Data rates above 17.6 kbit/s require that 8-PSK modulation is
used on the air, instead of the regular GMSK.
Scheme Modulation Maximum rate [kbps]
MCS-9 8PSK 59.2

MCS-8 8PSK 54.4
MCS-7 8PSK 44.8
MCS-6 8PSK 29.6
MCS-5 8PSK 22.4
MCS-4 GMSK 17.6
MCS-3 GMSK 14.8
MCS-2 GMSK 11.2
MCS-1 GMSK 8.8
The choice of the modulation and coding scheme is based on measurements of the Bit Error
Probability (BEP). The highest packet data throughput can be achieved for CIR values in excess of
20 dB, which corresponds to a clear radio path (as a reminder, let's mention that radio network
planning is made with the objective to meet standard quality of service requirements for CIR values at
least equal to 9 dB).
In this release of the BSS, in uplink MCS-5, MCS-6, MCS-7, MCS-8, MCS-9 shall not be supported.
1.2.2.4 Incremental redundancy
An additional feature introduced in EGPRS is incremental redundancy, which was not used in GPRS.
Incremental redundancy is the ability to combine in the receiver decoder soft bit information from N
different transmissions of the same RLC block. For each retransmission of the same RLC block, the
transmitter uses a different puncturing scheme in a way to increase redundant information not carried
by the same bits. It is our choice that N is equal to the number of puncturing schemes available for
the respective MCS as there is little gain expected after 2 or 3 combinings.
The chances to decode the RLC block are increased.
In this release, in the uplink, the Incremental redundancy is not used (Alcatel choice). In the BTS
receiver, it will not be possible to make soft combining between RLC data blocks. The receiver has
then not to store the soft bit values for each RLC block transmission.

10/12/2003
Incremental redundancy is always used (Alcatel choice) in downlink for EGPRS data blocks in RLC
acknowledged mode. Incremental redundancy does not apply to signalling blocks, GPRS data blocks
or data blocks in RLC unacknowledged mode.
Incremental redundancy at the MS receiver side is mandatory.
1.2.2.5 Effective transmit power
Two types of EGPRS capable TREs may be mixed in a single cell: medium and high power TREs.
The nominal TRE capabilities (for GSM900) without any power attenuation are:
High Nominal Power: GMSK : 60 W, 8PSK : 25 W
Medium Nominal Power: GMSK : 45 W, 8PSK : 15 W
Indeed the 8PSK modulation induces an Average Power Decrease, which is mainly due to the
envelopp difference between 8PSK and GMSK.
Moreover, several power reductions apply to the nominal TRE transmit power:
TREs may be coupled on the antenna. Such coupling induces a power reduction.
Power balancing applies to several TRE on the same sector: the BTS sets all the TRE output
power at the same level which is the minimum value among the maximum TRE output power in a
sector and in a given band.
Cell shared levelling aligns the GMSK output transmission power of the secondary sector to the
main sector, provided that the secondary sector can afford it (otherwise an alarm is sent to the
OMC).
Static Power Reduction: the static power reduction (BS_TX_PowerMax) is set by the OMC.
The resulting, effective, transmit power determines whether the TRE is a High power or a Medium
power TRE: the BTS shall indicate to the BSC the TRE power capability in 8PSK, i.e. HP or MP.
The resulting Average Power Decrease between 8PSK and GMSK on the Sector, which is the
difference between the Sector transmit power in 8PSK and the Sector transmit power in GMSK., shall
also be transmitted to the BSC and MFS. The reported APD shall not take into account the static
power reduction which is induced by BS_TX_Power_Max but it shall take into account the cell shared
levelling.
The 8PSK output power shall be as high as possible, provided that this power does, obviously, not
exceed the maximum transmit power which is defined in the sector and in the band, in order to keep
the radio network planning.

10/12/2003
1.2.2.6 Radio Measurements
GPRS measurements are performed for CS-1 to CS-4, see section 7.2.3.2.1.
Specific measurements are introduced for EGPRS.
The BTS has to compute the BEP (Bit Error Probability) on a burst basis.
The measurements mean(BEP) and CV(BEP) (the variation coefficient of BEP std(BEP)/mean(BEP))
are deduced from the BEP measurements and are calculated for each radio block received with CS-1
and MCS-1 to MCS-4.
The mean(BEP) and the CV(BEP) are reported on a per radio block basis to the MFS. They are used
by the link adaptation algorithm.
RXLEV, shall also be reported tothe MFS..
1.3 Overview description of layer services
The Physical Layer can be subdivided into Physcial Link Layer and Physical RF Layer [10].
1.3.1 Services provided by Physical RF layer
The Physical RF Sublayer provides services for:
The transfer of radio blocks from BTS to MS and from MS to BTS
The provision of physical channels according to GSM carrier frequency characterisation and GSM
radio channel structures
Modulation / demodulation
1.3.2 Services provided by Physical Link Layer
The Physical Link Sublayer provides data transport services for:
Encoding / decoding
Interleaving / deinterleaving
The Physical Link Layer additionally provides control services for

10/12/2003
The support of synchronisation between the BTS and the MFS [Erreur! Source du renvoi
introuvable.,2]
The continuous timing advance procedure
The radio measurements
The support of power control
1.3.3 Services required from Layer Management Plane
There is no alarm notification or configuration linked specifically to the (E)GPRS. Alarm notification or
configuration are ensured by O&M as in circuit switched [1].
1.3.4 Physical Layer Performance
The Physical layer is subject to performance requirements given in [13].
2 INTERFACES
2.1 Radio interface description
A Packet Data Channel (PDCH) is a physical channel, i.e. air time slot, allocated to carry packet
logical channels.
Up to 8 PDCHs could be supported on a TDMA frame.
The multiframe structure linked to a PDCH is described on the following figure.
52 - multiframe (240 ms)
B0 B1 B2 X B3 B4 B5 I B6 B7 B8 X B9 B 10 B 11 I
0 4 8 12 13 17 21 25 26 30 34 38 39 43 47 51
B n : Radio block n
X: PTCCH frames
I: Idle frames

10/12/2003
The sharing of the physical channel is based on blocks of 4 consecutive interleaved bursts.
A PDCH is mapped dynamically on a 52-multiframe.
It consists of 12 blocks of 4 consecutive frames, 2 idle frames (frames 25 and 51) and 2 frames used
for the PTCCH (frames 12 and 38).
The PTCCH is a bi-directionnal channel used for the continuous timing advance mechanism.
2.2 BTS-Relay
The BTS-Relay performs functions to map EGCH primitives on PLL service primitives. As far as
parameters and formats are concerned, BTS-Relay is functionally transparent. For the format
description of relevant messages the reader is referred to [2] (GCH mode and EGCH mode).
The mapping performed between EGCH primitives and PLL service primitives is given in section
5.1.2.
3 LAYER FUNCTIONS
3.1 PDCH activation - Initial synchronisation
3.1.1 PDCH activation and initial synchronisation in GCH mode
This function handles the PDCH activation and the initial synchronisation in GCH mode, where a
fixed mapping between PDCH and Abis nibble is given. Therefore, PDCH activation and initial
synchronisation over GCH are performed at the same time using a single function.
The PDCH activation and the initial synchronisation between the PLL layer and the MFS is triggered
by the L2GCH layer.
As the RLC/MAC protocol is completely managed by the MFS, this last must be synchronised to the
radio interface timing of each BTS to which it is connected. This is needed for the scheduling of
downlink RLC/MAC blocks. It means that the PLL layer must provide its timing on the BTS-MFS
interface.

10/12/2003
The initial synchronisation principle at PLL layer side is the following:
On PDCH activation a default Block Number is provided to the PLL by the MFS (for instance
N=0). The PLL deduces from this time the Block Number on which the frame would have been
sent on the radio interface if it was a traffic frame.
The Block Number error is then reported to the MFS.
The MFS applies the correction to its internal block number clock and can start sending traffic
frame.
Once the PDCH is activated, the BTS starts sending no data frames to the L2GCH layer until the
block format control function is initialised. The no data frames are sent every 20ms corresponding to
an uplink block reception.
At the reception of the first downlink RLC/MAC block to transmit on the radio interface, the next uplink
block type which is going to be received on the radio interface is given and then the block format
control function is initialised.
3.1.2 PDCH activation and initial synchronisation in EGCH mode
The PDCH activation and the initial synchronisation in EGCH mode is handled as in GCH mode,
except that a fixed mapping between PDCH and Abis nibbles pool is given: an Abis nibble pool may
contain 1, 2, 3, 4, 5 Abis nibbles, depending on the indicated pool type, respectively type 1, 2, 3, 4, 5.
An Abis nibbles pool carries an EGCH; each Abis nibble carries one GCH.
Therefore, PDCH activation and initial synchronisation over EGCH are performed at the same time
using a single function. The PDCH activation and the initial synchronisation between the PLL layer
and the MFS is triggered by the EGCH layer.
The initial synchronisation principles at PLL layer side are the same as defined in 3.1 for GCH mode.
As specified in Ref [2], when there are multiple GCH composing the EGCH link, each segment of an
EGCH PDU may not arrive at the same time at the BTS , and if they were treated separately could
generate different values of BNE complexifying the MFS behaviour. However, what really matters to
compute the BNE is the arrival time of the latest segment (or NODATA if there are unused sub-GCH)
When the link is established, for each block number, the EGCH layer in the BTS has to wait for all
segments composing the radio block, reassemble the whole radio block and only then, forward it to
the relay function/RF part. In return, the relay will issue a unique block error to be returned to the
MFS. In the MFS, the BSE process applies the same compensation to all the GCHs.
Once the PDCH is activated, the BTS starts sending no data frames to the EGCH layer until the
block format control function is initialised. The no data frames are sent every 20ms corresponding to
an uplink block reception.

10/12/2003
At the reception of the first downlink RLC/MAC block to transmit on the radio interface, the next uplink
block type which is going to be received on the radio interface is given and then the block format
control function is initialised.
3.2 Traffic handling
3.2.1 Traffic handling in GCH mode
3.2.1.1 General remarks
This function deals with RLC/MAC PDUs transmission and reception on the radio interface in GCH
mode. In GCH mode PLL expects block transmissions in uplink and downlink every 20 ms.
Each RLC/MAC block is encoded on the radio interface using the coding scheme CS-1 or CS-2.
RLC/MAC control blocks are always encoded using the coding scheme CS-1.
3.2.1.2 Block format control
Each time a downlink RLC/MAC block is received from the BTS relay entity, it schedules the next
uplink block that is going to be received on the radio interface.
This information could be:
Normal block
Access block (8 bit or 11 bit format)
No block
This uplink block scheduling allows the correct reception of the uplink block and the scheduling of
radio measurement functions.
3.2.1.3 Normal block handling
After the reception of a block on the radio interface, PLL sends the block to L2GCH with the
information on the coding scheme that has been used and the radio measurements concerning this
block.
At the reception of a block from L2GCH, the PLL sends this block on the radio interface in the Block
Number and using the coding scheme that have been indicated.

10/12/2003
3.2.1.4 BTS transmit power selection
The maximum GMSK output power is a constant value related to the BTS platform.
BS_TXPWR_MAX is the maximum allowed transmit power in the cell. It is sent to the BTS in the
PRH-ESTABLISH.req command (BS_TXPWR is set to BS_TXPWR_MAX in this message).
BS_TXPWR_MAX is defined relative to maximum GMSK output power, in -2 dB steps, ranging from
0 dB to -30 dB. The transmit command TRN-DL-DATA.req carries BS_TXPWR values which define
the output power for the actual block to send. BS_TXPWR is also defined as power ratio relative to
maximum GMSK output power, in -2 dB steps, from 0 dB to -30 dB.
Transmit power setting:
- TA message on PTCCH:
The actual transmit power is obtained as
max. GMSK output power [dB] + BS_TXPWR_MAX
- GMSK block:
The actual transmit power is obtained as
MIN{max. GMSK output power [dB] + BS_TXPWR_MAX*,
max. GMSK output power [dB] + BS_TXPWR*}
* Note that BS_TXPWR_MAX and BS_TXPWR are negative logarithmic values here.
3.2.1.5 Access burst or extended access block handling
When an uplink access block is scheduled, on the next block period the PLL layer can receive up to 4
access bursts.
The access burst handling function has to group them in a way to transmit them with their respective
timing advance value in one frame on the MFS-BTS interface. (Note: This does not apply to the
access bursts sent on PTCCH for timing advance measurements).
Two access bursts formats are defined; the access burst containing 8 information bits and the
extended access burst containing 11 information bits. The access burst format is indicated in the
PRH-ESTABLISH.req primitive received from (L2GCH).

10/12/2003
3.2.1.6 No block handling
When no block on the uplink is scheduled, PLL has to indicate to L2GCH that no block has been
received at the end of the block period.
In case of bad reception when a normal block is awaited on the radio interface, PLL sends a no data
indication setting the bit BFI (Bad Frame Indicator, GCH mode) or the invalid bit(s) (EGCH mode).
If no block is scheduled in downlink or if an erroneous frame is received in downlink from the MFS,
PLL has to send a dummy block (USF value = USFNE no emission) on the radio interface and the
next uplink block type will be no block.
3.2.2 Traffic handling in EGCH mode
3.2.2.1 General remarks
This function deals with transmission and reception of RLC/MAC PDUs on the radio interface in
EGCH mode.
Each RLC/MAC block is encoded on the radio interface using one of the GPRS coding schemes CS-1
to CS-4 or the EGPRS modulation and coding schemes MCS-1 to MCS-9. RLC/MAC control blocks
are always encoded using the coding scheme CS-1.
3.2.2.2 Block format control
Each time a downlink RLC/MAC block is received from the BTS relay entity, it schedules the next
uplink block that is going to be received on the radio interface.
This information is:
Normal block GPRS
Normal block EGPRS
Access block (8 bit or 11 bit format since Packet Control Ack is sent in 8 bit format; Packet
Channel Request may be sent in either 8 or 11 bit format. Only the EGPRS Packet Channel
Request is always sent in 11 bit format)
No block
If no UL block format information is available (e.g. no DL information has been sent by MFS) then a
normal GPRS block is expected by default.

10/12/2003
Remark: The distinction between GPRS and EGPRS normal block helps to resolve ambiguities of
stealing bit settings between CS-4 and MCS-1 to 4.
This uplink block scheduling allows the correct reception of the uplink block and the scheduling of
radio measurement functions.
3.2.2.3 Normal block handling (Uplink)
After the reception of a block on the radio interface, PLL sends the block to EGCH with the
information on the modulation and coding scheme that has been used and the radio measurements
concerning this block.
During a EGPRS uplink trafic, erroneous blocks shall also be forwarded to EGCH with an error
indication if the block header can be decoded. This allows higher layers in unacknowledged mode of
EGPRS to obtain additional information about the transferred data stream.
In the acknowledged mode of EGPRS, incremental redundancy in uplink shall not be used (Alcatel
decision).
3.2.2.4 Normal block handling (Downlink)
At the reception of a block from EGCH, PLL sends this block on the radio interface in the given block
number (BN) and time slot (TS), using the (modulation and) coding scheme (and puncturing scheme)
that have been indicated.
In this release of he BSS, the RLC Data blocks shall not be stored in the BTS. Retransmissions are
handled by RLC/MAC layer.
3.2.2.5 Extended access block handling
When an uplink access block is scheduled, on the next block period the PLL layer can receive up to 4
access bursts. The access burst handling function has to group them in a way to transmit them with
their respective timing advance value and training sequence type in one frame on the MFS-BTS
interface. (Note: This does not apply to the access bursts sent on PTCCH for timing advance
measurements).
The current training sequence is used by GPRS and EGPRS MSs to request access in GPRS mode
or to carry PACKET CONTROL ACKNOWLEDGEMENT messages; 8-bit or 11-bit access bursts can
be used. Two alternative training sequence formats have been defined, for EGPRS MS, to request
access in EGPRS mode and to distinguish the MSs EGPRS capabilities (TS1: EGPRS with UL 8-
PSK and TS2: EGPRS without UL 8-PSK). The training sequence type is forwarded to RLC/MAC by
the G3 and the G4 TRE.

10/12/2003
3.2.2.6 No block handling and erroneous blocks
When no block on the uplink is scheduled, in contrast to GCH mode PLL does not indicate to EGCH
that no block has been received at the end of the block period.
For GPRS bad reception occurs if the CRC check fails. For EGPRS bad reception occurs, if the
RLC/MAC header CRC check fails or if one or two RLC data block CRC checks fail. There are
several cases of bad reception. The following table shows the posssibilities:
normal block EGPRS

cases normal block Access block
GPRS
Header nok Header ok
Invalid bit(s) Invalid bit(s)

Content of BFI (GCH) Measurements Measurements AB & data
message Data
Invalid (EGCH)
measurements
Inter entity L2EGCH-UNITDATA.req L2EGCH-UNITDATA.req

primitive in
BTS PLL-COMMAND. ind PLL-COMMAND.ind
Access burst
Message used UNITDATA(N EGCH- UNITDATA UL
for indication ODATA UL) NODATA
toward MFS
In case of bad reception when a normal block is awaited on the radio interface:
In GPRS, PLL sends a no data indication setting the bit BFI (Bad Frame Indicator, GCH mode)
or the invalid bit(s) (EGCH mode) and radio measurements,
In EGPRS:
if the RLC/MAC header is not decoded, PLL sends a no data indication setting the invalid bit(s)
bit and radio measurements as in GPRS,
if the RLC/MAC header is decoded, PLL sends the erroneously decoded block with an error
indication along with radio measurements,
Note that in EGPRS a second RLC block can be received in the same radio block (MCS-7
to 9) which might be received correctly.
If no DL block is received from EGCH for DL transmission, PLL sends a dummy block (USF value =
USFNE no emission and page mode included) on the air interface if the PDCH is active and nothing
otherwise. If the PDCH is active the next uplink block type will be a normal GPRS block.

10/12/2003
If an erroneous frame is received from the MFS at the BTS side, PLL has to send a dummy block
(USF value = USFNE no emission) on the radio interface and the next uplink block type will be a
normal GPRS block.
3.2.3 BTS transmit power
3.2.3.1 Effective transmit power (no change compare to B7)
3.2.3.2 Selection of Output transmit power
Levelling of GMSK Transmission sector power
The TRE output power is equal to the TRE GMSK maximum output power minus the coupling stages.
The Sector transmit power is equal to the minumum value for all TREs.
The sector transmit power therefore takes into account the coupling and the levelling on a Sector
inside the BTS.
TRE GMSK output power
TRE2 max power
TRE1 max power
TRE3 max power
TRE1max power - coupling
TRE2 max power - coupling

Pbts1 Pbts2
TRE3 max power - coupling

= Sector Transmit power
For each TRE, the BTS O&M (OMU) internally applies the necessary attenuation (Pts) in order to
reach Sector transmit power.
Levelling of 8PSK Output Transmission Power (new for B8)

10/12/2003
The 8PSK shall be as high as possible, but, the 8PSK output power of a TRE shall not exceed the
maximum transmit power which is defined in the sector and in the band, in order to keep the radio
network planning.
Then, in 8PSK, the only levelling which applies shall align, if necessary, the 8PSK Output power to
the GMSK output power in the sector and in the band.
The BTS shall compute the 8PSK delta power which is the difference between the Sector transmit
power and the 8 PSK power that can be reached by a given TRE.
The effective 8PSK power per TRE is the maximal 8PSK value minus coupling stages.
If this value is below than the Sector transmit power, the difference (in dB) shall be reported to the
BSC via the O&M (See Ref [9]) in the 8PSK delta power; then, the BTS shall internally apply an
attenuation to 8PSK in order to align 8PSK and Sector transmit power.
If the difference is above or equal to the Sector transmit power, the 8 PSK delta power is equal to 0.
The 8PSK delta power value therefore takes into account the coupling stages. The BTS internally
limits takes the necessary means to reduce the gap between 8PSK power and Sector GMSK power to
a minimum.
TRE 8PSK output power
TRE2 max power 8PSK
TRE1 max power 8PSK
TRE3 max power 8PSK
TRE1max power 8PSK - coupling
Sector Transmit power GMSK

1 2 TRE2 max power 8PSK - coupling
Delta power TRE3

TRE3 max power 8PSK - coupling
The 8PSK delta power which is reported to the BSC is the difference between the Sector transmit
power and the 8 PSK power that can be reached by a given TRE. In the above example, only for TRE
3, a delta power >0 would be reported.
The 8PSK delta power does not take into account the static power reduction but it takes into account
the cell sharing levelling.

10/12/2003
The 8PSK delta power (nominal APD per TRE) shall represent: Power in GMSK - Power in 8PSK. in
tenth of dB.
It can only be a positive or null value.
The BTS reports the 8PSK delta power (nominal APD per TRE) to the MFS (See Ref [2]).
Note that, taking into account the coding rules of BS_TXPWR_MAX, the OMC and the MFS compute
the effective APD with the following formula:
Effective APD = max(0, 8PSK delta power - 20xBS_TXPWR_MAX) in tenths of dBm.
3.2.3.3 Setting of 8PskHpCapability flag
A TRE shall indicate whether it is High Power or Medium Power. The 8PskHpCapability flag is set, if
the 8 PSK delta power determined is less than 3dB.
Note: the BTS reports the Sector transmit power, the delta power and the 8PskHpCapability flag in
HwCapabilityCU and TreHWCapability to BSC (which forwards it to MFS) and OMC, see Ref [9].
3.2.3.4 Cell shared
Levelling of GMSK Output Transmission Power (no change compare to B7)
To line up the transmission power of both sectors, the BTS sends (see Ref [9]) the absolute output
power in GMSK of each physical sector. Then on a secondary sector, the BSC informs the BTS (via
CONFIGURATION DATA MESSAGE BLOCK 2, see Ref [9]) of the absolute power in GMSK of the
main sector.
The BTS of the secondary sector shall compute the correction to be applied for lining up the
transmission power of both sectors.
Levelling of 8PSK Output Transmission Power
For a 8PSK block, a TRE shall use the minimum value between:
Its 8PSK Transmit Power
The GMSK Transmit Power of the sector and the band minus the potential attenuation requested
by BSC due to the main sector and minus the BS_TX_PWR_MAX sent by the MFS.
3.2.3.5 BTS command on a per burst basis

10/12/2003
The BTS shall adjust the 8PSK transmit power, on its own, ie without involving the MFS: the BTS
shall take into account the received BS_TX_Power_Max parameter, its coupling configuration, and its
TRE transmit powers constraints.
Since a GPRS TBF (GMSK modulated) and an EGPRS TBF (8PSK modulated) may be allocated on
the adjacent timeslots, the transmit power shall be adapted on a per burst basis.
The transmit power also needs to be adapted on a block by block basis: during transitory phases,
some 8PSK modulated PDTCHs and GMSK modulated PDTCHs may be carried and multiplexed on
the same PDCH.
Note that in the RLC/MAC header of each 8PSK downlink block, the PR field shall indicate the
effective power decrease. This power reduction is handled by RLC/MAC layers.
In order to cope with O&M and telecom desynchronisation, the TRE 8PSK power capability
parameters need to be transmitted by the BTS to the MFS, through EGCH.
3.3 Continuous synchronisation to the radio interface
3.3.1 Continuous synchronisation in GCH mode
For some networks the accuracy of the transmission clock is not enough for the radio performance of
the BTS. In this case, the BTS is not synchronised on the network and the difference of accuracy
between the A-bis clock and the PLL clock induces a shift in the synchronism of the two network
elements.
PLL must detect the loss of synchronisation on downlink with the MFS.
The two cases can happen:
Abis clock slower than BTS clock
As for initial synchronisation time, PLL continuously reports the error between the received Block
Number and the Bn on which it should be sent.
If the time of reception of a RLC/MAC block, marked with Block Number set to N, shifts until being
preferably sent in Bn+1 (to avoid buffer overflow), an error set to +1 is reported to the MFS.

10/12/2003
PLL shall report the error +1 and send received RLC/MAC blocks in the requested Bn, until it receives
a RLC/MAC block with the Block Number corrected. At the reception of the block, it has to insert a
dummy block in the previous position.
Abis clock faster than BTS clock
If the time of reception of a RLC/MAC block, marked with Block Number set to N, shifts until being
preferably sent in Bn-1 (to avoid buffer overflow), an error set to -1 is reported to the MFS.
PLL shall report the error -1 and send received RLC/MAC blocks in the requested Bn, until it receives
one no data frame with the same Block Number.
The complete description of the MFS-BTS synchronisation is described in [1].
3.3.2 Continuous synchronisation in EGCH mode
The synchronisation in EGCH mode is performed as in GCH mode.
3.4 Radio measurements
The radio measurements are performed in the BTS on a per PDCH and radio block basis.
They consist in:
- the carrying out of the uplink measurements,
- the estimation of the timing advance to be applied by each MS whose PACCH is carried by
the concerned PDCH.
The basic radio link parameters are:
- the signal strength

10/12/2003
- the signal quality (measured and reported only in GCH mode)
- the bit error probability (mean and cv, measured and reported only in EGCH mode)
- the MS-BS absolute distance.
3.4.1 Uplink measurements in GCH mode
According to the uplink block type scheduled, different radio link parameters are assessed and
reported to the MFS.
3.4.1.1 Normal block:
In case of normal block, PLL performs measurements on quality and received level.
The uplink signal strength (RXLEV) and the signal quality (RXQUAL) are assessed on an uplink block
(ie four consecutive normal bursts).
RXLEV is the mean of the signal strength on the four normal bursts that composed the block.
The RXQUAL measurement is related to a block on the radio interface.
For each block, the RXQUAL and RXLEV values are reported from PLL to RLC/MAC.
3.4.1.2 Access block or extended access block:
In the access block period, PLL can receive up to 4 consecutive access bursts.
On each access burst, PLL estimates the access delay. This timing advance value is sent to
RLC/MAC together with the information contained in the access burst.
On any PRACH occurrence, whether an access burst is decoded or not, the BTS measures the uplink
signal strength on this occurence (RXLEV) and reports it to the MFS (RXLEV is used for PRACH
collision detection, refer to [3]).
(Note: This does not apply to the access bursts sent on PTCCH for timing advance measurements).

10/12/2003
3.4.1.3 No block:
In case of no uplink block, PLL performs measurements on the received level.
RXLEV is the mean of the signal strength on the four bursts period.
3.4.2 Uplink measurements in EGCH mode
According to the uplink block type scheduled, different radio link parameters are assessed and
reported to the MFS.
3.4.2.1 Normal block
In case of normal block, PLL performs measurements on received level and bit error probability.
In GPRS, the uplink signal strength (RXLEV) and raw bit error rate (RXQUAL) are assessed on an
uplink block (ie four consecutive normal bursts). Indeed, GPRS is used in EGCH mode to carry CS3
or CS4 RLC data blocks, then RXQUAL values are required by RLC to perform link adaptation;
RXQUAL values shall be reported by the BTS to the MFS whatever the GPRS Coding Scheme is. For
CS-1 to CS-3, when a block is correctly decoded, the reported signal quality is computed as in GCH
mode, as described in section 7.2.3.2.1.1. For CS-4, if a radio block is correctly decoded, since there
is no error correcting code, the CRC success indicates that no error has been detected, then the best
channel quality shall be reported. When a block is not decoded correctly (Cyclic Redundancy Check
failed), a constant RXQUAL value shall be reported to the MFS, depending on the Coding Scheme
with which the radio block was encoded, as described in section 7.2.3.2.1.1.,
In EGPRS, the uplink signal strength (RXLEV) and mean and coefficient of variation of the bit error
probability (MEAN_BEP and CV_BEP) are assessed on an uplink block (ie four consecutive normal
bursts). For definition and computation of MEAN_BEP and CV_BEP see section 7.2.3.2.1.1.
RXLEV is the mean of the signal strength on the four normal bursts that composed the block.
Measurements are also made and reported to RLC/MAC in cases where the block header can be
decoded but the decoded block is erroneous. Even if decoding fails completely, measurements are
made and reported. However, if a normal GPRS block is expected by default (i.e. if no block handling
information had been received in DL) then unsuccessful decoding is not reported.
3.4.2.2 Extended access block
In the access block period, PLL can receive up to 4 consecutive access bursts.

10/12/2003
On each access burst, PLL estimates the access delay, and determines the tranining sequence type.
These values are sent to RLC/MAC together with the information contained in the extended access
burst.
signal strength on this occurence (RXLEV) and reports it to the MFS (RXLEV is used for PRACH
collision detection, refer to [3]).
3.4.2.3 No block
No processing is performed in this case.
3.4.3 Timing advance estimation for the continuous update timing advance procedure
PLL handles the continuous update timing advance function (see 3.5). This function needs the
computation of timing advance value for the access bursts sent on the uplink PTCCH.
3.5 Continuous timing advance update procedure
The continuous timing advance procedure operates on a per PDCH basis. It is activated as soon as
the PDCH is activated by the L2-GCH or EGCH layer.
PLL perform the continuous update timing advance procedure for all MS working in transfer state.
PLL monitors the delay of the access bursts sent by the MS on PTCCH and responds with timing
advance values for all MSs performing the procedure on that PDCH. These timing advance values
are sent via the downlink TA message on the PTCCH.
PLL shall update the timing advance values in the next downlink signalling TA message following the
access burst. The TA message is updated every four multiframes.
The new training sequence types defined for EGPRS are not used on PTCCH/UL.
3.6 Frequency offset correction
For frequency offset correction (FOC) a Short-term FOC (inside a burst) is performed for GMSK radio
blocks.
Note: Long-term FOC is not required for GPRS CS-1 to CS-4 not either for EGPRS MCS1 to MCS4.

10/12/2003
4 PROTOCOL LAYER STRUCTURE
4.1 Layer structure model
Note: in the following figure, BTS-Relay entity belongs to the same protocol level as Physical Link
Layer. Besides, the Layer Management entity belongs to the Layer Management Plane.
BTS Relay entity
T1
T2 C1 H1
T P P
R C R
N C H
C2
Physical Link Layer
Legend :
TRN : TRaNsport entity PRH : Packet Radio resource Handling
PCC : Packet Connection Control entity
SAP interface Internal EAP interface

External EAP interface O&M SAP interface

10/12/2003

10/12/2003
4.2 Overview of layer functional model
The functions implemented by this layer are depicted on the next figure.
Physical Link Layer
TRN PCC PRH
RF transport
Continuous PDCH
timing activation
advance deactivation
procedure
Block format
control
Radio
Access burst measurements
handling
TRN entity:
The PLL Transport entity supports the following functions:
RF transport: this function is in charge of:
Block encoding/emission on the radio interface
Block reception/decoding (with and without IR) from the radio interface
Reception and decoding of access bursts and detection of training sequence type (EGPRS)
Block reception from L2GCH or EGCH

10/12/2003
Block emission to the L2GCH or EGCH
Block format control: this function is in charge of the uplink block type control (access block,
normal block or no block) expected on the radio interface
Access burst handling: this function is in charge of the access bursts gathering over a block
period.
PCC entity:
The PLL Packet Connection Control supports the following functions:
Continuous timing advance update procedure: this function is in charge of the MSs timing
advance control.
Radio measurements: this function is in charge of radio measurements for each block received
(timing advance for access block, quality (RxQual (in GPRS) or BEP (in EGPRS)) and level
(RxLev) for normal block).
PRH entity:
The PLL Packet Radio Resource Handling supports the following function:
PDCH activation/deactivation: this function is in charge of the activation/deactivation of the

functions linked to the PDCH.
4.3 Overview of layer interfaces
Access Point Access Supporting entity Provided services

Identifier Point
Type
H1 SAP PRH Services for PDCH activation/deactivation and

initial synchronisation
C1 EAP PCC Services for packet control channel

activation/deactivation
C2 EAP PCC Services for block measurements
T1 SAP TRN Services for data transport

10/12/2003
T2 EAP TRN Services for initial synchronisation

10/12/2003
5 SERVICE PRIMITIVE DEFINITION
5.1 List of service primitives provided by the layer
5.1.1 Primitives provided to the BTS-Relay entity (GCH mode and EGCH mode)
SAP/EAP Primitive name Type Semantic
req ind rsp cnf
H1 PRH-ESTABLISH x x Indicates the activation of a PDCH
H1 PRH-RELEASE x x x Releases a PDCH
T1 TRN-UL-DATA x (PLL) TRN uses this primitive to

transfer one RLC/MAC PDU to (L2-
GCH)
T1 TRN-DL-DATA x (L2-GCH) uses this primitive to

transfer one downlink RLC/MAC
PDU
T1 TRN-ERROR x (L2-GCH) uses this primitive to

indicate an erroneous frame
T1 TRN-NO-DATA x x Indication of no uplink data
T1 TRN-ACCESS-BURST x Indication of data received as

access bursts
5.1.2 Mapping of PLL service primitives to EGCH primitives and messages
EGCH message
EGCH service primitive PLL service primitive
(BTS side)
EGCH-UNITDATA-ind L2EGCH-UNITDATA.ind PLL-SEND-COMMAND.req
EGCH-UNITDATA-req L2EGCH-UNITDATA.req (RLC PLL-RECV-COMMAND.ind

data block) (RLC data block)

10/12/2003
EGCH-ACCESS-BURST-req L2EGCH-UNITDATA.req PLL-RECV-COMMAND.ind
(Access Burst) (Access Burst)
EGCH-NODATA-req L2EGCH-UNITDATA.req PLL-RECV-COMMAND.ind
5.1.3 Primitives provided to other (PLL) entities
SAP/EAP Primitive name Type Semantic
req ind rsp cnf
C2 PCC-NEXT-BLOCK x Indicates the type of the next block

which will be received
C2 PCC-MEASUREMENT x x Indicates the measurement made

for the uplink block
T2 TRN- x x Indicates the block number

SYNCHRONISATION modification to apply to the
downlink block number in order to
synchronise GCH interface with the
radio interface
C1 PCC-START-TA- x Indicate the activation of the

PROCEDURE continuous update timing advance
procedure
Remark: Since these service primitives are internal to (PLL) they will not be described in detail in this
document.
5.2 Detailed description of service primitives provided by the layer
5.2.1 Service primitives provided to the BTS-Relay entity (GCH mode and EGCH mode)
5.2.1.1 PRH-ESTABLISH.req (GCH mode and EGCH mode)

Service definition:
The BTS relay entity uses this primitive to request activation of a PDCH.
Parameters:

10/12/2003
Parameters Presence Range Semantic
PDCHid M 1-8 Link identification (timeslot number on the TDMA
frame)
DBN M 0-47 Downlink Block Number: block number by which the
frame should be carried in the 52 multiframe on the
radio interface.
As synchronisation is not yet realised between GCH

and radio interface, DBN is set arbitrarily to 0 by MFS.
USFNE M 0-7 USF value indicating no emission
BS_TXPWR M Max - Maximum transmit power at BS side (relative value
30 dB with regard to BTS maximum output power)
to min (BS_TXPWR_MAX-Pb).
0dB
step This power is used for the transmission of the TA
size 2 message on the PTCCH downlink.
dB
TSC M 0-7 Training Sequence Code
AB M 0-1 Access burst format (8 or 11 bits format)
5.2.1.2 PRH-ESTABLISH.cnf (GCH mode and EGCH mode)

Service definition:
(PLL) PRH uses this primitive to confirm the activation of a PDCH.
Parameters:

frame)
Result M 0-1 OK: the request is accepted
NOK: the request is not accepted
Cause C 1-2 Present only when result = NOK
specifies the cause of the refusal
- radio interface disabled
- invalid parameters in the request

BN synchro C 0-11 Block Number synchronisation: specifies the
modification to apply to the downlink block number in
order to synchronise GCH interface with the radio
interface.
This field is only present when result is OK.

FN C 0- Frame Number on which the PRH-ESTABLISH.req
271564 would have been sent on the radio interface if it was
7 data.
UBN C 0 - 59 Uplink Block Number
block number with which primitive is synchronised on

the radio interface.
This field is only present when result is OK.

10/12/2003
5.2.1.3 PRH-RELEASE.req (GCH mode and EGCH mode)
Service definition:
The BTS relay entity uses this primitive to request the release of a PDCH.
Parameters:

frame)
5.2.1.4 PRH-RELEASE.cnf (GCH mode and EGCH mode)

Service definition:
(PLL) PRH uses this primitive to confirm the release of a PDCH.
Parameters:

frame)
5.2.1.5 PRH-RELEASE.ind (GCH mode and EGCH mode)

Service definition:
(PLL) PRH uses this primitive to indicate the release of a PDCH.
Parameters:

frame)
Cause M 1-2 Cause of the release
- radio interface disabled
- unexpected DBN.

10/12/2003
5.2.1.6 TRN-DL-DATA.req (GCH mode and EGCH mode)
Service definition:
The BTS relay entity uses this primitive to send a RLC/MAC PDU to the MS and to give the next
uplink block type.
GPRS format (CS1 to CS4):

frame)
radio interface
Radio block M GPRS, Set to GPRS for GPRS blocks
format EGPR
S
BS_TXPWR C (1) 0 31 BS transmit power
UB M 1-3 Uplink Block
It indicates the uplink burst type which will be received

on the radio interface on Block Number=DBN+1
- GPRS Normal block
- EGPRS Normal block
- Access block
- No block
-
CS M 1-2 Coding scheme
- CS1
- CS2
- CS3
- CS4
BS_TXPWR M 0-15 Transmit power for the block (relative value)
Max -30 dB
to min 0dB
step size 2 dB
RLC/MAC M RLC/MAC PDU
PDU
CS1 (184 bits)
CS2 (271 bits)
CS3 (315 bits), (EGCH mode only)
CS4 (431 bits), (EGCH mode only)

10/12/2003
EGPRS format (MCS1 toMCS9), (EGCH mode only)

frame)
radio interface
UB M 1-3 Uplink Block
It indicates the uplink burst type which will be received

on the radio interface on Block Number=DBN+1
- GPRS Normal block
- EGPRS Normal block
- Access block
- No block
-
Radio block M GPRS, Set to EGPRS for EGPRS blocks
format EGPR
S
BS_TXPWR C (1) 0 31 BS transmit power
CPS M 1 27 Coding and Puncturing Scheme indicator
RLC/MAC M
PDU 207 MCS-1
255 MCS-2
327 MCS-3
383 MCS-4
476 MCS-5
620 MCS-6
936 MCS-7
1128 MCS-8
1224 MCS-9
5.2.1.7 TRN-UL-DATA.ind (GCH mode and EGCH mode)

Service definition:

10/12/2003
(PLL) TRN uses this primitive to send a RLC/MAC PDU to the MFS and to report measurement
on quality and received level.
GPRS format (CS1 toCS4):

frame)
BN error M -1 to +1 Block Number error: specifies the modification to apply
step to the downlink block number in order to correct clock
size 1 drift.
UBN M 0-59 Uplink Block Number
Block number on the radio interface

CS M 1-4 Coding scheme used
- CS1
- CS2
- CS3
- CS4
RXLEV M 0-63 Received level
RXQUAL M 0-7 Quality
RLC/MAC M RLC/MAC PDU

PDU
CS1 (184 bits)
CS2 (271 bits)
CS3 (315 bits) (EGCH mode only)
CS4 (271 bits) (EGCH mode only)
EGPRS format (MCS1 toMCS9): (EGCH mode only)

frame)
size 1 drift.
Block number on the radio interface

MCS M 1-9 Modulation and Coding scheme used

10/12/2003
- MCS1
- MCS2
- MCS3
- MCS4
RXLEV M 0-63 Received level

10/12/2003
MEAN_BEP M 0 31
Average BEP measured on the radio interface

10/12/2003
CV_BEP M 07 Normalised BEP standard deviation measured on the
radio interface
RLC/MAC M
PDU 207 MCS-1
255 MCS-2
327 MCS-3
383 MCS-4
Erroneous M This flag is set to indicate that the conveyed RLC data
RLC data flag block has not been correctly decoded, whereas the
block header has been correctly decoded.
Note that in EGPRS, if the header is correctly decoded, the RLC data block shall be transmitted to
RLC layer, whether it is correct or not.
5.2.1.8 TRN-NO-DATA.req (GCH mode and EGCH mode)

Service definition:
This primitive is used by L2GCH to indicate that a no data frame has been received.
Parameters:

frame)
DBN M
0-47 Downlink Block number
5.2.1.9 TRN-NO-DATA.ind (GCH mode and EGCH mode)

Service definition:
(PLL) TRN uses this primitive in the following cases:
After having received an establishment request, this primitive is sent, every 20 ms, until
uplink block programmation by downlink traffic flow (BFI=0)
When the uplink block has been programmed with the no block value (BFI=0)
When the uplink block has been programmed either with the normal block or access block
value and the GPRS radio block has not been decoded or the EGPRS header has not been
decoded (BFI=1).
Parameters:

frame)

10/12/2003
BN error M
Block number modification to apply to the downlink
0-11 block number in order to synchronise GCH interface
with the radio interface in case of
-1/0/1
- initial synchronisation
- or clock drift
RXLEV O 0-63 Received level (Only in the third case)

BFI M 0-1 Bad Frame Indication
5.2.1.10 TRN-ERROR.req (GCH mode and EGCH mode)

Service definition:
This primitive is used by L2GCH to indicate that an erroneous frame has been received.
Parameters:

frame)
DBN M 0-47
Downlink Block Number: block number by which the
radio interface
Cause M 1-4 cause of the error
- erroneous CRC
- erroneous frame format
- frame pattern substitution failure

- synchronisation loss
5.2.1.11 TRN-ACCESS-BURST.ind (GCH mode and EGCH mode)

Service definition:
This primitive is used by (PLL) TRN to forward data received as access bursts.
Parameters:

frame)

10/12/2003
UBN M 0-59
Uplink Block Number: block number on the radio
interface
size 1 drift.
AB valid M indicates which access bursts are valid
0-1 -first burst significant
0-1 -second burst significant
0-1 -third burst significant
0-1 -fourth burst significant

AB M 0-1 Access burst format (8 or 11 bits format)
burst 1 M first burst data
FN1 M
Frame number of the first burst (format T1-T2-T3)
TAV1 M
Timing advance value of the first burst
TST1 C (EGCH 1-2
mode) Training Sequence Type
1: TS1: 8-PSK capability in uplink
2: TS2: no 8-PSK capability in uplink

burst 2 M
second burst data
FN2 M
Frame number of the second burst (format T1-T2-T3)
TAV2 M
Timing advance value of the second burst
TST2 C (EGCH 0-2
0: normal TS

burst 3 M
third burst data
FN3 M
Frame number of the third burst (format T1-T2-T3)
TAV3 M
Timing advance value of the third burst
TST3 C (EGCH 0-2
0: normal TS

10/12/2003
burst 4 M
fourth burst data
FN4 M
Frame number of the fourth burst (format T1-T2-T3)
TAV4 M
Timing advance value of the fourth burst
TST4 C (EGCH 0-2
0: normal TS

RXLEV1 M 0-63
Received level for the first PRACH occurrence
RXLEV2 M 0-63
Received level for the second PRACH occurrence
RXLEV3 M 0-63
Received level for the third PRACH occurrence
RXLEV4 M 0-63
Received level for the fourth PRACH occurrence
Note: (1) the 2 Training Sequences shall be decoded and indicated by both G3 and G4 TRE.
If a Radio timeslot is allocated by the BSC to a TCH (e.g. during a CS preemption), the BTS shall
then stop monitoring the corresponding EGCH link and act upon the BSC allocation.
It is then assumed that no mismatch is possible on the air timeslots, e.g due to CS preemption.

10/12/2003
6 DEFINITION OF LAYER PROTOCOL
6.1 Peer to peer protocol description
6.1.1 Continuous timing advance update procedure
The following peer-to-peer messages are defined between the MS and the BTS at (PLL) layer:
Access burst on PTCCH,
TA message.
These messages are used in the continuous timing advance update procedure.
The timing advance procedure is used to derive the correct value for timing advance that the MS has
to use for the uplink transmission of radio blocks.
MS in Transfer state shall use the continuous timing advance update procedure. The continuous
timing advance update procedure is carried only on the PDCH which carries PACCH.
For uplink packet transfer, within the Packet Immediate Assignment or Packet Resource Assignment
for Uplink , the MS is assigned resources on one or several uplink PDCHs with corresponding Uplink
State Flags (USF) and Timing Advance Index (TAI).
For downlink packet transfer, within the Packet Resource Assignment for Downlink, the MS is
assigned resources on one or several uplink PDCHs, Timing Advance Index (TAI) and the PDCH
used for the continuous timing advance update procedure. The TAI is 4 bits allowing 16 different
positions in groups of eight 52-multiframes (T0,T1,T15).
On the uplink, the MS shall send in assigned idle slots a special access burst, which is used by the
network to derive the timing advance. The position of the assigned idle slot is determined by the TAI
assigned to the MS on that PDCH.
The access burst format to be used by the MS on the uplink is indicated by the PRH-ESTABLISH.req
in GCH mode. In EGCH mode, always extended (11bit) access bursts are used.
The network analyses the received access burst on the PTCCH and determines new timing advance
values for all MSs performing the continuous timing advance update procedure on that PDCH. The
new timing advance values shall be sent via the TA-message mapped on the downlink PTCCH.

10/12/2003
At the initialisation of the procedure, each timing advance of the TA-message have the same value
1111111 indicating no timing advance value.
Each time an access burst is received on the uplink PTCCH with a block format different from the two
specified in the section 4.2, a no timing advance value must be sent in the next TA-message for the
corresponding PTCCH.
MS BSS
Continuous timing advance

procedure
Access burst on PTCCH
TA Message
Air interface
6.2 PDU definition
6.2.1 PTCCH downlink block format
The originally 184 bit (23 octets) blocks are used downlink in the following way:
<----------------------------------------------------------------------------------
8 7 6 5 4 3 2 1
Spare Ordered timing advance for MS assigned TAI = 0 Octet 1
Spare Ordered timing advance for MS assigned TAI = 1 Octet 2
: :
: :
: :
Spare Ordered timing advance for MS assigned TAI = 15 Octet

16
Octet
7 17
Octets
: :
: :
: :
fill octets:
"00101011" Octet 23

10/12/2003
Figure: PTCCH downlink block format
The field mapping convention in this sub-clause is that when a field is contained within a single octet,
the highest bit number of the field represents the highest order value and lowest bit number of the
field represents the lowest order value.
Spare bits are encoded with the binary value "0". Fill octets are encoded with the binary value
"00101011".

10/12/2003
6.2.2 PTCCH uplink block formats
Two alternative PTCCH uplink block formats are specified. The originally 8 bit (1 octet) blocks are
used uplink in the following way:
<----------------------------------------------------------------------------------
8 7 6 5 4 3 2 1
8 fixed bits: "01111111" Octet 1
Figure: PTCCH uplink block format
The originally 11 bit blocks are used uplink in the following way:
<----------------------------------------------------------------------------------
8 7 6 5 4 3 2 1
11 fixed bits: "11111111111" Octet 1
Octet 2
Figure: PTCCH uplink block format
The field mapping convention of sub-clause applies. In the addition, when a field spans more than
one octet, the order of bit values within each octet progressively decreases as the octet number
increases. In that part of a field contained in a given octet the lowest bit number represents the lowest
order value.
6.2.3 Dummy block transmission
The dummy block has the following format:
8 7 6 5 4 3 2 1
Payload type RRBP S/P USF octet 1 MAC
header
Message type Page mode octet 2 Message
type

10/12/2003
0 0 1 0 1 0 1 1 octet 3
: : : Spare
: : : padding
: : :
: : :
0 0 1 0 1 0 1 1 octet 21
Figure: Dummy block format
Case 1: No information is received from MFS
Payload type is set to 01 (Control block).
RRBP is set to 00.
S/P is set to 0.
USF is set to USFNE value (no emission) received in PRH-ESTABLISH.req (GCH mode and EGCH
mode) .
Page mode is set to Same as before (11).
Message type is set to 1 00101.

10/12/2003
7 LAYER DYNAMIC MODEL
7.1 Inter-entities communication
7.1.1 Packet radio resource handling (GCH mode and EGCH mode)
7.1.1.1 Establishment
Upon reception of a request to establish a PDCH from L2-GCH or EGCH, (PLL)PRH requests the
Block Number synchro to (PLL)TRN. After reception of the confirmation, (PLL)PRH sends the
confirmation to L2GCH or EGCH with the block number error, at an instant which minimises the
buffer delay in the BTS.
Note:
(PLL)TRN starts sending No data indication every 20 ms until it receives the first downlink RLC/MAC
PDU to transmit on the downlink.
(L2/EGCH) BTS relay (RF)PRH (RF)TRN (RF)PCC

i
PDCH
L2/EGCH-ESTABLISH.ind
PRH-
TRN-
TRN-
PRH- 20 ms
PCC-START-TA-
L2/EGCH-ESTABLISH.resp
TRN-NO-
L2/EGCH-NODATA.req 20 ms
TRN-NO-
L2/EGCH-NODATA.req
Note: L2/EGCH-xxx.yy stands for either L2GCH-xxx.yy or EGCH-xxx.yy, depending on the GCH
mode.
7.1.1.2 Link release
This procedure can be triggered by the BTS or by the MFS.
7.1.1.2.1 MFS triggering

10/12/2003
L2/EGCH BTS relay entity (RF)PRH
PDCH release
L2/EGCH-RELEASE.ind
PRH-RELEASE.req
PRH-RELEASE.cnf
L2/EGCH-RELEASE.resp
7.1.1.2.2 BTS triggering
L2/EGCH BTS relay entity (RF)PRH
Link release initiated by the BTS
PRH-RELEASE.ind
L2/EGCH-RELEASE.req
7.1.2 Data transfer (GCH mode)
7.1.2.1 Downlink PDU transfer (GCH mode)
Upon reception of a TRN-DL-DATA.req from L2GCH, (PLL)TRN indicates the next block the BTS is
going to receive on the uplink to (PLL)PCC.

10/12/2003
L2GCH BTS relay entity (RF)TRN (RF)PCC
Downlink PDU transfer
L2GCH-UNITDATA.ind
TRN-DL-DATA.req
Transmission of a radio block
Next UL block indication
PCC-NEXT-BLOCK.ind
7.1.2.2 Uplink PDU transfer
Upon reception of a block on the radio interface, (PLL)TRN requests to (PLL)PCC the measurements
made on this block and sends the data to L2GCH.
Uplink PDU transfer
Reception of a radio block
PCC-MEASUREMENT.req
PCC-MEASUREMENT.cnf
TRN-UL-DATA.ind
L2GCH-UNITDATA.req
7.1.2.3 No block received on the radio interface
In case of no block received on the uplink, (PLL)TRN requests the received level measurement made
during the block period and sends an indication to L2GCH.

10/12/2003
No block received on the

radio interface
End of a block period
PCC-MEASUREMENT.req
PCC-MEASUREMENT.cnf
TRN-NO-DATA.ind
L2GCH-NODATA.req
7.1.3 Data transfer (EGCH mode)
7.1.3.1 Downlink PDU transfer
7.1.3.1.1 Downlink PDU transfer: Normal case
Upon reception of a PLL-SEND-COMMAND.req from BTS Relay, (PLL) identifies the next block the
BTS is going to receive on the uplink (block format control).
MFS EGCH BTS L2EGCH BTS Relay BTS PLL
Downlink PDU transfer, block is sent by MFS

EGCHUNITDATA-ind
(RLC data block ) L2EGCH-UNITDATA.ind

(RLC data block ) PLL-SEND-COMMAND.req
(RLC data block)
Radio Block
Transmission

10/12/2003
7.1.3.2 Uplink PDU transfer
7.1.3.2.1 Uplink PDU transfer: Normal case
Upon reception of a block on the radio interface, (PLL) performs measurements made on this block
and sends data and measurements to (EGCH).
Uplink PDU transfer
Radio Block
Reception
PLL-RECV-COMMAND.ind
(RLC data,
L2EGCH-UNITDATA.req [Block, Air TS, Invalid=0,
(Received RLC data, RxLev, Mean(BEP), CV(BEP)])
EGCH-UNITDATA-req [Block, Air TS, Invalid=0,
[Block, Air TS, Invalid=0,
RxLev, Mean(BEP), CV(BEP)])
7.1.3.2.2 Uplink PDU transfer: Erroneous reception
If a block reception is scheduled in the uplink but the block and header cannot be decoded, (PLL)
sends a UNITDATA (NODATA UL) command including radio measurements to MFS.
Uplink PDU transfer, bad reception, bock header not decoded (GPRS, EGPRS)
Radio Block
Reception
Block cannot be
decoded (GPRS)
or
Block header cannot
be decoded (EGPRS)
(NODATA [Air TS, RxLev,
L2EGCH-UNITDATA.req Mean(BEP), CV(BEP),
EGCH-UNITDATA- (NODATA [Air TS, RxLev, cause])
req Mean(BEP), CV(BEP) ,
(NODATA [Air TS, RxLev, cause])
Mean(BEP), CV(BEP) ,
cause])

10/12/2003
7.1.3.2.3 Uplink PDU transfer: Erroneous reception, but block header can be decoded
(EGPRS)
In EGPRS, in case of no RLC block received on the uplink (i.e. BCS of RLC block(s) does not match)
and RLC/MAC header is received (i.e. HCS does match), (PLL) performs measurements on the
block, sends RLC/MAC header and measurements to (L2GCH) and the erroneous block(s) is (are)
also forwarded.
Note: indeed, in RLC unacknowledged mode, the erroneous SDUs shall be transmitted to upper
layers (if the header is correctly decoded).
Uplink PDU transfer, bad reception, block header can be decoded (EGPRS)
Radio Block
Reception
(Received RLC data
L2EGCH-UNITDATA.req [Erroneous block,
(Received RLC data, Air TS, Invalid=1,
EGCHUNITDATA-req
[Erroneous block, RxLev, Mean(BEP), CV(BEP)])
(Received RLC data, Air TS, Invalid=1,
[Erroneous block, RxLev, Mean(BEP), CV(BEP)])
Air TS, Invalid=1,
7.1.3.2.4 Uplink PDU transfer: No uplink block format available
In case of no uplink block format information available, a GPRS normal block is expected in the
uplink and forwarded to MFS if decoding is successful. If decoding fails, no indication is sent to MFS
to reduce signalling load on Abis/Ater.

10/12/2003
Uplink PDU transfer, no valid block format information available

successful decoding of GPRS normal block
Radio Block
Reception
GPRS normal
block is expected
and decoded
(Received RLC data,
L2EGCH-UNITDATA.req [Block, Air TS, Invalid=0,
EGCHUNITDATA-req [Block, Air TS, Invalid=0,
[Block, Air TS, Invalid=0,
Uplink PDU transfer, no valid block format information available

unsuccessful decoding of GPRS normal block
Radio Block
Reception
GPRS normal
block is expected
but not decoded
7.1.3.3 Access block
Access block reception (4 access bursts)
Access Burst
Reception
(PLL) groups four

access bursts into
an access block
(Access burst [...])
L2EGCH-UNITDATA.req
EGCHUNITDATA-req (Access burst [...])
(Access burst [...])

10/12/2003
7.2 Entities detailed description
7.2.1 PRH detailed description
The PRH entity is in charge of the link establishment over the air interface (PDCH).
7.2.1.1 Function description
7.2.1.1.1 PDCH activation-deactivation function (GCH mode)
This function manages the link establishment and the initial synchronisation of the MFS to the radio
interface timing of the BTS.
7.2.1.1.2 PDCH configuration function (EGCH mode)
Objectives:
This function manages the activation and deactivation of PDCHs (see Ref [2]).
7.2.2 TRN detailed description
The TRN entity is in charge of managing the uplink and downlink traffic.
7.2.2.1 Function description
7.2.2.1.1 RF transport
Objectives:
This function is in charge of the transmission of DL PDU towards the radio interface and UL PDU
towards (L2GCH) or (EGCH).
Procedures:
Measurements result request
Access burst handling
Continuous synchronisation

10/12/2003
Coding, interleaving, modulation and emission
Reception, demodulation, deinterleaving and decoding
7.2.2.1.2 Block format control
Objectives:
This function manages the uplink block format.
Procedures:
Block format control
7.2.2.1.3 Access burst handling
Objectives:
This function handles the gathering of the access bursts with their respective timing advance received
during a block period in one RLC/MAC PDU.
Procedures:
Measurements result request (for TOA)
Access burst handling
7.2.2.1.4 Continuous synchronisation (GCH mode and EGCH mode)
Objectives:
This function is in charge of monitoring at the reception of a downlink block the Bn on which it is
preferably send to avoid buffer overflow or underflow in the BTS.
Procedures:

10/12/2003
Continuous synchronisation
7.2.2.2 Procedures description
7.2.2.2.1 Measurements result request
The measurements result request procedure is in charge of collecting the measurements made on a
block period by the Radio measurements function in the PCC entity.
7.2.2.2.2 Access burst handling
Each time, an access block is scheduled on the uplink, up to four access bursts can be received
during the block period.
During an access block period, each time an access burst is received and well decoded, the
information it contains are stored with its corresponding access delay and the frame number on which
it was received.
signal strength on this occurence (RXLEV is used for PRACH collision detection, refer to [3]).
At the end of the access block period, a TRN-ACCESS-BURST.ind (GCH mode) or PLL-
COMMAND(Access Burst).ind (EGCH mode) is sent with the information of each access burst, their
respective access delay and the four RXLEV values corresponding to the four possible PRACH
occurences.
In EGCH mode, 8bits or 11 bits access bursts are used depending on the access burst type parameter
which is received from the MFS (see Ref [2]). The training sequence type is analysed to identify the
MSs 8-PSK capabilties: the MS may use 2 types of Training Sequences, which shall be decoded by
the G3 and the G4 TRE.
7.2.2.2.3 Continuous synchronisation (GCH mode and EGCH mode)
Each time, a TRN-DL-DATA.req is received from the BTS relay entity, the block number B on which
the block should preferably be sent on the radio interface to avoid buffer overflow is compared to the
Block Number on which the block has to be send.
If the B - Block Number = 1 then an error of +1 is reported with the block number error in the next
TRN-UL-DATA.ind.
If the B - Block Number = -1 then an error of -1 is reported with the block number error in the next
TRN-UL-DATA.ind.
An anticipation mechanism is introduced to take into account the correction loop between the BTS
and the MFS.

10/12/2003
However,if a block is received with a DBN which is incorrect : i.e. block received too late to be sent in
requested occurrence or block received to early (buffer overflow) (these cases correpond to BNE > +1
or BNE < -1), then a release of the link is triggered. If the block is received too late, a dummy block
has to be sent on the radio interface, then the GCH link is released.
7.2.2.2.4 Block format control
Each time, a TRN-DL-DATA.req (GCH mode) or a PLL-COMMAND(Send RLC data block).req

(EGCH mode) for the transmission of the block Bn is received from the BTS relay entity, the uplink
block format in which is going to be received the uplink block Bn+1 is indicated.
If no valid DL block information is available, a normal GPRS block is expected by default.
This mechanism allows the scheduling of the Radio measurements function and the Reception
demodulation, deinterleaving and decoding function.
At the PDCH initialisation, as long as no TRN-DL-DATA.req or PLL-COMMAND(Send RLC data

block).req has been received, the UL block which is scheduled is no block. The Block format control
function is initialised at the reception of the first TRN-DL-DATA.req or PLL-COMMAND(Send RLC
data block).req.
7.2.2.2.5 Coding, interleaving, modulation and emission
For these functions refer to [11], [12] and [13].
7.2.2.2.6 Reception, demodulation, deinterleaving and decoding
For these functions refer to [11], [12] and [13].
7.2.2.2.7 Demodulation and decoding of Access Bursts
Demodulation of access bursts is done according to [12]. In EGCH mode always extended (11 bit)
access bursts are used on PRACH. The training sequence type is analysed to identify the MSs 8-PSK
capabilties.
7.2.3 PCC detailed description
7.2.3.1 Functions description
7.2.3.1.1 Radio measurements function
Objectives:

10/12/2003
This function manages the uplink measurements.
Procedures:
Radio measurements
7.2.3.1.2 Continuous timing advance update function
Objectives:
This function manages the Continuous timing advance update procedure.
Procedures:
Radio measurements
Continuous update timing advance procedure
7.2.3.2 Procedures description
7.2.3.2.1 Radio measurements
The radio measurements are performed in the BTS on a per PDCH and radio block basis.
The following channels are concerned:
- packet data traffic channels and packet dedicated control channels,
- packet random access channel (PRACH),
- packet timing advance control channels.
The radio measurements function is using as input flow the radio signal received on the radio
interface for one timeslot duration. This signal is:
- either a GSM burst sent by an MS,

10/12/2003
- or random signal (noise) during idle frame of an active channel or during an unused
PRACH occurrence.
This function is controlled by the packet channel configuration.

Uplink block type : It corresponds to the block type on which measurements are going to be
done. Block type is indicating whether a normal block, four consecutive access bursts (8 bits
or 11 bits format) or no block is expected during the block period.
Radio measurements :
Uplink radio measurements (quality, level, and bit error probabilities) are performed by the BTS
during each block period on the packet data traffic channel. Uplink radio level measurements
are performed by the BTS on each PRACH occurrence. The parameters RXLEV_UL,
RXQUAL_UL, MEAN_BEP_UL, and CV_BEP_UL are forwarded with the GSM coding (see
section 7.2.3.2.1.1),
Timing advance : For an access burst on PRACH or on PTCCH, it estimates the access delay.
7.2.3.2.1.1 Radio link measurements parameters
Signal strength:
The received signal level is denoted as RXLEV by GSM.
Physical parameter
The BTS must measure the RMS signal level at the receiver input over the full range of -110 dBm to -
48 dBm with a relative accuracy of 1 dB within any 20 dB portion of the total measurement range
and an absolute accuracy of 4dB from -110 dBm to -70 dBm under normal condition and 6dB over
the full range under both normal and extreme conditions.
Statistical parameter
The reported parameter shall be:
For PDTCH: the average of the received signal level measurement samples in dBm taken within
the block period (ie 4 bursts). The actual averaging performed by the BTS is done with linear
values.
For PRACH: the received signal level measurement sample in dBm.

10/12/2003
The BS is required to make for any PDTCH a received signal level measurement.
Parameter range
The received signal level shall be mapped to an RXLEV value between 0 and 63 as shown in table 1:
RXLEV RMS received signal level RXLEV Assumed values of signal

level
0 < -110 dBm 0 -110 dBm
1 -110 dBm to -109 dBm 1 -109 dBm
2 -109 dBm to -108 dBm 2 -108 dBm
: : : : :
62 -49 dBm to -48 dBm 62 -48 dBm
63 > -48 dBm 63 -47 dBm
GSM TS 05.08 definition:Values assumed by the dynamic coding scheme adaptationin the ALCATEL
BSS.
Table 1: RXLEV range and coding
Signal quality:
The signal quality is denoted as RXQUAL in GSM.
By definition, there is no RXQUAL estimation for idle blocks.
Physical parameter
For CS-1 to CS-3 correctly decoded RLC data blocks, the received signal quality shall be measured
by the BTS in a manner that can be related to an equivalent average BER before channel decoding (ie
chip error ratio), assessed over a block period, by comparing re-encoded decoded bits with the
demodulated bits.

10/12/2003
For CS-4 correctly decoded RLC data blocks, the signal quality shall reflect that no error has been
detected.
For uncorrectly decoded radio blocks, a constant signal quality shall be reported. The reported signal
quality value depends on the CS with which the radio block was encoded.
Statistical parameter in case of correctly decoded radio block
The reported parameter (RXQUAL_UL) shall be the received signal quality assessed on a packet
signalling or traffic block.
Parameter range
The BTS estimated quality value is divided into eight quality bands.
For GPRS CS-1 to CS-3 uplink RLC data blocks, the following table gives the mapping of the
equivalent BER before channel decoding on the quality bands, when the CRC succeeds.
RXQUAL BER before channel decoding Assumed value of BER
0 less than 0.2% 0.14%
1 0.2% to 0.4% 0.28%
2 0.4% to 0.8% 0.57%
3 0.8% to 1.6% 1.13%
4 1.6% to 3.2% 2.26%
5 3.2% to 6.4% 4.53%
6 6.4% to 12.8% 9.05%
7 greater than 12.8% 18.10%
Table 2 : Signal quality bands for CS-1 to CS-3
For GPRS CS-4 uplink RLC data blocks, the BTS shall set RXQUAL value to RXQUAL=0, which
reflects that the CRC check was successfully passed i.e. no erroneous bit was detected.

10/12/2003
Parameter range in case of uncorrectly decoded radio block
In this case, a constant RXQUAL value shall be reported depending on the coding scheme which was
detected for the block (the detection through stealing bits, that are highly protected since positioned
right next to the synchronisation bits, should be correct in most cases). In turn, this means that the
RXQUAL value seen by RLC will be approximately: RXQUAL = (1-BLER).RXQUAL cor +
BLER.RXQUALCS where RXQUALcor corresponds to the RXQUAL value measured on correctly
decoded radio blocks and RXQUALCS corresponds to the RXQUAL value reported for uncorrectly
decoded radio blocks. Simulations have determined the most appropriate RXQUALCS value so that the
RXQUAL seen by RLC is as close as possible to the real RXQUAL.
The following table gives the relationship between the detected Coding Scheme and the reported
RXQUAL when the CRC check fails.
Detected CS RXQUAL
CS-1 RXQUAL_7
CS-2 RXQUAL_7
CS-3 RXQUAL_6
CS-4 RXQUAL_3
Table 3 : Signal quality bands for CS-1 to CS-4 uncorrectly decoded radio blocks
Both these mappings shall be supported by G3 and G4 TREs.
Bit Error Probabilities (BEP):
In EDGE, for the radio link quality control, two new radio measurements are introduced: MEAN_BEP
and CV_BEP. They reflect the impact of the C/I, the time dispersion and the velocity of the channel.
These values are derived from the bit error probability (BEP) which is a value that shall be estimated
burst by burst by the demodulator (BTS). Besides, for each received radio block a value for
MEAN_BEP and CV_BEP must be computed and reported to the MFS for uplink connections. Then,
the MFS filters these values for each connection for further RLC functions (e.g. link adaptation). For
downlink connections, filtered values of MEAN_BEP and CV_BEP are reported by the mobile in the
channel measurement report IE (available in the Packet downlink Ack/Nack message) on MFS
request.
Definition of BEP

10/12/2003
Actually, BEP is the expected bit error probability for a burst, given a particular channel impulse
response, receiver implementation, signal to noise ratio etc , but averaged over all realizations of
the noise and the transmitted data ([1]). BEP reflects the raw bit error probability and therefore shall
be independent on the coding scheme used on the air.
Definition of MEAN_BEP
MEAN_BEP is the average on a radio block of the BEP per burst. It is reported in a logarithmic scale.
1 4
MEAN _ BEP = log10 BEP
4 =1
i
i
MEAN_BEP is coded with 5 bits (32 steps). Two distinct tables are defined for GMSK and 8-PSK
modulations ([2]) but both table report BER values between 10-0.6 (i.e. 25%) down to 10-3.6 (i.e.
2.5 10-4).
MEAN_BEP can be seen as an extension of RX_QUAL. Indeed, for selecting the best MCS among
the 9 available, more that 8 different values reflecting channel quality are required.
Definition of CV_BEP
The purpose of CV_BEP is to describe the variation of the channel quality inside a radio block period
on a time slot. It is the standard deviation of the BEP per burst normalized by the average so that
CV_BEP is more dependant on the channel variation and less dependant on the Bit Error Probability
itself.
2
1 4 1 4
BEP BEP
3 =1 4 =1
k
CV _ BEP =
k i
1 4
4
BEP i
=1 i
Eight CV_BEP values are defined and each step represents the same range of CV_BEP values for
both modulations.
Parameter range
MEAN_BEP measurements are represented by 5 bits according to the following table
Bit pattern Range of Range of

log10(MEAN_BEP) log10(MEAN_BEP)
8PSK GMSK

10/12/2003
>-0.60
00000 (0) >-0.60
00001 (1) ]-0.64, -0.60] ]-0.70, -0.60]
00010 (15) ]-1.20, -1.16]
11101 (16) ]-1.36, -1.20]
11110 (30) ]-3.60, -3.44] ]-3.60, -3.50]
11111 (31) -3.60 -3.60
Table 4:MEAN_BEP quantization
CV_BEP measurements are represented by 3 bits according to the following table
Bit pattern Range of

CV_BEP
8PSK & GMSK
000 (0) [2.00, 1.75[
001 (1) [1.75, 1.50[
010 (2) [1.50, 1.25[
011 (3) [1.25, 1.00[
100 (4) [1.00, 0.75[
101 (5) [0.75, 0.50[
110 (6) [0.50, 0.25[
111 (7) [0.25, 0.00]
CV_BEP quantization
Absolute MS-BS distance:

10/12/2003
The absolute MS-BS distance is estimated by measuring the Time of Arrival (TOA) of the received
packet access burst at the BTS.
Note 1 : The absolute MS-BS distance as measured by the BTS may include internal delay within the
BTS (induced by the signal transmission in the radio chain from antenna to demodulator).
Physical parameter
The value is expressed by a number of bit periods on the radio interface. The bit rate on the radio
interface is 270.8 kbit/s therefore a symbol period lasts 3.69 s which corresponds to a distance of
1.1 km.
But due to the roundtrip delay between MS and BS, a bit period corresponds to a MS-BS distance of
(1.1/2) km ie around 550 m.
The GSM TS 05.10 [14] requires that the delay shall be assessed in such a way that the assessment
error (due to noise and interference) is less than 1/2 bit period.
Parameter range
The GSM TS 05.10 ([14]) requires that the maximum timing advance value shall be 63 bits. If the BS
measures a value larger than this, it shall set the timing advance to 63.
The TOA range is 0 to 63 transmission bit periods for access bursts (absolute value).
7.2.3.2.1.2 Channel measurements
TOA estimation:
The TOA estimation is only computed on Packet Access Burst or Extended Packet Access Burst. A
TOA estimation is done every occurrence of the uplink PTCCH for the continuous timing advance
update procedure (see 6.1.1).
The arrival time of the burst in a given timeslot is computed by a further evaluation of the channel
impulse response of the input signal.
Input flow
Uplink radio signal.
Control flows
Packet channel configuration, GSM time.

10/12/2003
Uplink block type:
If the uplink block type is set to no block or normal block, the TOA estimation is not performed. If
the uplink block type is set to access block or extended access block, the TOA estimation is
performed. TheTOA estimation is performed on each uplink PTCCH occurence.
Output flows
TOA.
RXQUAL computation:
It consists in the estimation of the received signal quality on the basis of a traffic or a signalling block.
The quality estimation corresponds to the bit error rate at the demodulation output (chip error rate).
The estimation of the average bit error rate done in the ALCATEL BTS is based on the error counting
method.
The decoded bits at the output of the convolutional decoder (Viterbi) are encoded again and the bit
error rate is obtained by comparison of the originally encoded bits as they have been received and
the re-encoded bits.
Input flow
Traffic frame/signalling block.
Control flows
Packet channel configuration:
Uplink block type : the function is not performed for the packet access burst, extended packet
access burst and the no block type.
Output flow
RXQUAL_UL : estimation of the BER before channel decoding performed on a set of bits
corresponding to a traffic block or to a signalling block. This parameter is coded with the GSM coding
(range : 0 to 7, see section 7.2.3.2.1.1).
Antenna diversity aspects

In case of antenna diversity, only one RXQUAL_UL value is computed.
RXLEV computation:
It consists in the estimation of the strength of the received signal at the receiver input.
They consist in the averaging, on a per channel and per block basis, of the RXLEV_UL parameter
received within the block period (ie four consecutive bursts).
Input flows
Control flow
Packet channel configuration.
Uplink block type:


10/12/2003
If the uplink block type scheduled is no block or normal block, the average RXLEV_UL is
computed.
If the uplink block type scheduled is an access block (8 bits or 11 bits format) or for access bursts
on PTCCH (8 bits or 11 bits format), RXLEV_UL is not computed.
Output flow
RXLEV_UL: RXLEV_UL assessed over the full set of TDMA frames within the block period,
pertaining to the packet data channel.
The RXLEV_UL parameters are coded with linear decimal values.
In case of antenna diversity, only one value of RXLEV_UL is computed (the RXLEV_UL values of
both RX paths are averaged together).
BEP computation:
It consists of the estimation of the mean and coefficient of variation of the bit error probability at the
demodulator output. Statistics are calculated over four consecutive burts belonging to one radio
block.
Input flows
Control flow
Packet channel configuration.
Uplink block type : the function is not performed for the packet access burst, extended packet
access burst and the no block type.
Output flow
MEAN_BEP_UL
CV_BEP_UL
For definition and encoding of MEAN_BEP and CV_BEP see 7.2.3.2.1.1)
7.2.3.2.2 Continuous update timing advance procedure
Refer to section 6.1.1.

10/12/2003
8 SYSTEM PARAMETERS
TSC
Access burst format
BS_TXPWR_MAX
USFNE

10/12/2003
9

10/12/2003
10 GLOSSARY AND ABBREVIATIONS
BSC Base Station Controller
BSCGP BSC GPRS Part
BSN Block Sequence Number
BTS Base Transceiver Station
CS Coding Scheme
EAP Entity Access Point
EGCH Enhanced GCH
FU Frame Unit
FUMO Frame Unit MOdule
GCH GPRS Channel
GPRS General Packet Radio Service
GSM-RF GSM Radio Frequency
IR Incremental Redundancy
LLC Logical Link Control
MAC Medium Access Control
MCS Modulation and Coding Scheme
MFS Multi Function Server
MS Mobile Station
PAGCH Packet Access Grant Channel
PACCH Packet Associated Control CHannel
PBCCH Packet Broadcast Control Channel
PCCCH Packet Common Control Channel
PCM Pulse Code Modulation
PCU Packet Control Unit
PDCH Packet Data Channel
PDU Protocol Data Unit
PDTCH Packet Data Traffic Channel


10/12/2003
PLL Physical Link Layer
PPCH Packet Paging Channel
PRACH Packet Random Access Channel
PTCCH Packet Timing Advance Control Channel
RF Radio Frequency
RLC Radio Link Control
RMS Root Mean Square
RRM Radio Resource Management
SAP Service Access Point
TBF Temporary Block Flow
TFI Temporary Flow Identity
TOA Time Of Arrival
TDMA Time Division Multiple Access
TRX Transceiver
END OF DOCUMENT

10/12/2003

(E) GPRS - Radio Interface - Physical Link LayerB8

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

(E) GPRS - Radio Interface - Physical Link LayerB8

Transféré par

Droits d'auteur :

Formats disponibles

Site EVOLIUM SAS

System : ALCATEL 900/BSS

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 1/81

Ed. 01 Released 05/11/2002 Review in the MND/MRA/TD/SYT/SBO/203133 document.

Ed. 02 Released 17/01/2003 Review in the MND/MRA/TD/SYT/SBO/202251_1

Ed 03 Released 27/05/2003 Integration of CR 3BKA20CBR126483_2

Ed. 01 Proposal 01 05/09/2002 Document Creation for B8.

Ed. 01 Proposal 02 30/10/2002 Corrections after email review

Alignment on EGCH primitives and procedures

Ed. 01 Released 05/11/2002 Corrections after email review: naming of EGCH

Ed. 02 Proposal 01 06/12/2002 Introduction of TRE transmit power handling

Introduction of the mapping table from meanBEP to

Clarification on the Page Mode IE.

Ed. 02 Released 17/01/2003 Email review

Alignment on the conclusions of the 18/12/2002

Ed. 03 Proposal 1 30/04/2003 Email review

Introduction of Package 5 CR, 3BKA20CBR123749:

Ed 03 Released 27/05/2003 Replacement of the clauses changed in Package 5

Ed 04 Released 10/12/2003 CR 133427 is taken into account.

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 2/81

1 OVERVIEW DESCRIPTION OF THE PROTOCOL LAYER......................................................... 7

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 3/81

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 4/81

[1] 3BK 11202 0xxx DSZZA GPRS Telecom presentation

[2] 3BK 11202 0370 DSZZA MFS-BTS interface: EGCH stack

[7] 3BK 11202 0084 DSZZA BSS telecom parameters

[8] 3BK 11202 0083 DSZZA GPRS counters catalogue

[10] 03.64 Overall description of the GPRS radio interface

[11] 05.01 Physical layer on the radio path; general description

[12] 05.03 Channel coding

[13] 05.05 Radio transmission and reception

[14] 05.10 Radio subsystem synchronization

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 5/81

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 6/81

1.1 Layer location

(L2-GCH) or (EGCH) for communication with MFS.

With layer management plane for O&M interactions.

User & Control Plane

Fig. 1: BTS Layers, GCH mode

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 7/81

User & Control Plane

Fig. 2: BTS Layers, EGCH mode

1.2 Layer characteristics

In GPRS, packetised non-real-time data is served in addition to traditional GSM circuit-switched

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 8/81

MAC header RLC header RLC data BCS

Figure 3: Radio Block structure for data transfer for GPRS

The Block Check Sequence (BCS) is used for error detection.

MAC header RLC/MAC Control Message BCS

The Block Check Sequence (BCS) is used for error detection.

1.2.1.2 Channel coding

ED 04 Released (E)GPRS - Radio interface - Physical link layer

EVOLIUM 0381_04.DOC 3BK 11202 0381 DSZZA 9/81

rate 1/2 convolutional coding

Figure 5: Radio Block structure for CS-1 to CS-3