Radio Block structure for data transfer for GPRS

Radio Block
MAC header RLC Header RLC Data BCS

Radio
Pre- Block Puncture Data rate Data rate
coded excl. USF d kb/s kb/s
Scheme Code rate USF USF and BCS BCS Tail Coded bitsbits (Note 1) (Note 2)
CS-1 1/2 3 3 181 40 4 456 0 9.05 8
CS-2 2/3 3 6 268 16 4 588 132 13.4 12
CS-3 3/4 3 6 312 16 4 676 220 15.6 14.4
CS-4 1 3 12 428 16 - 456 - 21.4 20

NOTE 1: This value includes the RLC header, the MAC header (excluding the USF), the spare bits and
RLC information.
NOTE 2: This value includes only RLC information.
Radio Block

USF BCS

rata 1&"/"&2 convolutional coding

Punctring

456 Bits

Radio Block structure for CS-1 to CS-3

Radio Block

USF BCS

no coding

456 Bits

Radio Block structure for CS-4

 456 bits of CS1 ~CS3

Encoding and puncture

Burst Burst Burst Burst

20 m sec

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.
As we see in previous figures the radio block length is 456 bits, if we see to the normal burst:

3 57 1 26 1 57 3
Guard
Tail

Tail
Payload/signaling Payload/signaling
training sequence Period

Stealinf flags

If we take the payload or data 57*2=114 for every burst so the whole radio block is:

RB= 114 *4 burst= 456 bits

Figure (A-a)
 Raw
Data
PAN within
Code RLC one
Code Header rate blocks Radio Tail Data rate
rate Code (if Modul per Radio Block payl PCS (if per PDCH
Scheme (Note 2) rate present) ation Block (Note 1) Family BCS oad HCS present) kb/s
MCS-9 1 0.36 n/a 2 2x592 A 59.2
0.92
MCS-8 0.36 0.42 2 2x544 A 54.4
(0.98) 2x12 2x6
0.76
MCS-7 0.36 0.42 2 2x448 B 44.8
(0.81) 8PSK
0.49 592 29.6
MCS-6 1/3 0.39 1 A
(0.52) 48+544 27.2
0.37
MCS-5 1/3 0.39 1 448 B 22.4
(0.40) 8 10
MCS-4 1 0.53 n/a 1 352 C 17.6
296
0.85 12 6 14.8
MCS-3 0.53 0.63 1 48+248 A
(0.96) 13.6
and 296
GMSK
0.66
MCS-2 0.53 0.63 1 224 B 11.2
(0.75)
0.53
MCS-1 0.53 0.63 1 176 C 8.8
(0.60)

TDMA frame structure for EGPRS

We know that 1 TS= 1 burst and 1 burst contains of 156.25 symbols (normal burst) 3GPP calculate the
time duration of this burst as (15/26=0.577 ms)

0.577 ms*8 timeslot = 4.616 ms

4.616 ms *26 TDMA frame = 120 ms

4.616 ms *52 TDMA frame = 240 ms

From Figure (A-a) we know that 52 TDMA frame contains of 12 radio blocks, so 240/12=20 ms for one
radio block.

In EGPRS the data bits or as mentioned here Encryption bits were given here 58 not as in GPRS 57.
where in EGPRS we add stealing flag with data bits.

If we take example with Coding and puncturing for MCS-7; rate 0.76 8PSK, two RLC blocks per radio
block, here the total bits after coding will be 1392 bits as in figure (A-a) the radio block consisting of 4
normal burst :

1 burst = 58 *2=116 bits

116 *3 symbols (since we using MCS7 with 8 PSK then23 =8) =348 bits /burst

1 Radio block =4 burst=4 *348= 1392 bits/Radio Block.3GPP ts_143064v100000p

If we tack another example with Coding and puncturing for MCS-4; uncoded GMSK, one RLC block per
radio block
1 burst = 58 *2=116 bits

116 *1 symbols (since we using c with GMSK then it will be 21 =2) =116 bits /burst

1 Radio block =4 burst=4 *116= 464 bits/Radio Block.

The different coding schemes are grouped into three classes or families which are referred to by letters,
as classes A, B and C. The coding schemes within a class are used together and complement each other.
Family A consists of MCS-3, MCS-6, MCS-8, and MCS-9. Family B consists of MCS-2, MCS-5, and MCS-7.
Finally family C consists of MCS-1, and MCS- 4. The advantage of grouping the families together in this
way is that if a block transmitted in one of the coding schemes is not acknowledged, then it can be sent
as two blocks, for example with a coding scheme in the same family. For example if a block transmitted
using MCS-7 is corrupted then it can be re-sent as two blocks using MCS-5 or four using MCS-2.
 MCS 3 37 bytes

Family A MCS 6 37 bytes 37 bytes

MCS 9 37 bytes 38 bytes 37 bytes 38 bytes

MCS 3 3+ 34 bytes

Family A' MCS 6 34+3 bytes 34+3 bytes

MCS 8 34 bytes 34 bytes 34 bytes 34 bytes

MCS 2 28 bytes

Family B MCS 5 28 bytes 28 bytes

MCS 7 28 bytes 28 bytes 28 bytes 28 bytes

MCS 1 22 bytes
Family C

MCS 4 22 bytes 22 bytes

LLC Frame:

The LLC layer performs an ARQ protocol Automatic Repeat re-Quest (ARQ), also known as Automatic
Repeat Query based on retransmission after timeouts or frame loss detection and optionally uses
bitmap-based selective acknowledgements.

The LLC frame consists of Address field with one octet containing SAPI and identifier of logical link,
control field contains of 36 Octets.

LLC frame can classify to:

Information frame (I frame) containing numbers for acknowledged data retransmission.

Unnumbered information frame (UI frames) for unacknowledged data transmission.
Supervisory frame (S frame).

Unnumbered frames (U frame).

The max length of information field depends on SAPI. The frame check sequence contains of 3 Octets
 8 7 6 5 4 3 2 1
Address Field (1 Octet)

Control field ( variable length, max 36 Octet)

Information fild (variable length, max. N201 Octets)

Frame check sequance Field (3 Octets)

From here we can see that LLC is important for user to know the exact data information sent by users
(network) where it will split it in to number of RLC in radio then send all RLC data blocks regarding to
radio environments to other part up or down weird, i.e. the system will know data information from LLC
and send it via Air by RLC and RLC will retransmit regarding to ARQ protocol till send all data correctly.

BS CV MAX:

The Countdown Value (CV) field is sent by the mobile station to allow the network to calculate the
number of RLC data blocks remaining for the current uplink TBF. The CV value shall be calculated
according to the citron process. The CV field is 4 bits in length and is encoded as a binary number with
range 0 to 15. The mobile station shall send the Countdown Value (CV) in each uplink RLC data block to
indicate to the network the absolute BSN (BSN') of the last RLC data block that will be sent in the uplink
TBF. The CV shall be calculated as follows.

1
Let integer x = round( ).

, __
Then, CV {
15,
Where:
TBC = total number of RLC data blocks that will be transmitted in the TBF.
BSN' = absolute block sequence number of the RLC data block, with range from 0 to (TBC - 1)
NTS = number of timeslots assigned to the uplink TBF in the assignment message, with range 1 to 8.
The function round () rounds upwards to the nearest integer, BS_CV_MAX is a parameter broadcast in
the system information, the division operation is non-integer and results in zero only for (TBC - BSN' - 1)
= 0.

The final RLC data block transmitted in the TBF (i.e., the RLC data block with BSN' = TBC - 1) shall have CV
set to the value '0'. No other RLC data blocks transmitted during the TBF shall have the value '0'.

Once the mobile station transmits a value of CV other than 15, the mobile station shall transmit exactly
(TBC - BSN' - 1) un-transmitted RLC data blocks. If the mobile station receives a change in the Channel
Coding Command in a PACKET UPLINK ACK/NACK message during the countdown procedure, the mobile
station shall act upon the new Channel Coding Command