7 Coding and interleaving
3GPP45.001General descriptionGSM/EDGE Physical layer on the radio pathRelease 17TS
7.1 General
A brief description of the coding schemes that are used for the logical channels mentioned in clause 2, except packet traffic channels and packet control channels that can be found in sub clause 7.2, plus the synchronization channels (see subclause 5.2), is made in the following tables. For all the types of channels the following operations are made in this order:
– external coding (block coding);
– internal coding (convolutional or turbo coding);
– interleaving.
After coding, the different channels (except RACH, EC-RACH, SCH, EC-SCH, CTSBCH-SB and CTSARCH) are constituted by blocks of coded information bits plus coded header (the purpose of the header is to distinguish between TCH and FACCH blocks). These blocks are interleaved over a number of bursts. The block size and interleaving depth are channel dependent. All these operations are specified in 3GPP TS 45.003.
For the adaptive speech traffic channels, a signaling codeword is attached to the block of coded information bits before interleaving. The signaling codeword is a block code representation of a 2-bits inband information word (rate ¼ for the adaptive full rate speech traffic channels, ½ for the adaptive half rate speech traffic channels, rate 1/6 for the adaptive half rate 8-PSK speech and 8-PSK wideband speech traffic channels, and rate 1/12 for the adaptive full rate 8-PSK wideband speech traffic channels).
Type of channel |
bits/block data+parity+tail1 |
convolutional code rate |
coded bits per block |
interleaving depth |
---|---|---|---|---|
TCH/FS |
456 |
8 |
||
class I2 |
182 + 3 + 4 |
½ |
378 |
|
class II |
78 + 0 + 0 |
‑ |
78 |
|
TCH/EFS |
456 |
8 |
||
class I2 |
170 + 15 + 4 |
½ |
378 |
|
class II |
74 + 4 + 0 |
‑ |
78 |
|
TCH/HS |
228 |
4 |
||
class I3 |
95+3+6 |
104/211 |
211 |
|
class II |
17+0+0 |
17 |
||
TCH/AFS12.24 |
456 |
8 |
||
Class I5 |
244 + 6 + 4 |
127/224 |
448 |
|
TCH/AFS10.24 |
456 |
8 |
||
Class I6 |
204 + 6 + 4 |
107/224 |
448 |
|
TCH/AFS7.954 |
456 |
8 |
||
Class I7 |
159 + 6 + 6 |
171/448 |
448 |
|
TCH/AFS7.44 |
456 |
8 |
||
Class I8 |
148 + 6 + 4 |
79/224 |
448 |
|
TCH/AFS6.74 |
456 |
8 |
||
Class I9 |
134 + 6 + 4 |
9/28 |
448 |
|
TCH/AFS5.94 |
456 |
8 |
||
Class I10 |
118 + 6 + 6 |
65/224 |
448 |
|
TCH/AFS5.154 |
456 |
8 |
||
Class I11 |
103 + 6 + 4 |
113/448 |
448 |
|
TCH/AFS4.754 |
456 |
8 |
||
Class I12 |
95 + 6 + 6 |
107/448 |
448 |
|
TCH/AHS7.9513 |
228 |
4 |
||
Class I14 |
123 + 6 + 4 |
133/188 |
188 |
|
Class II |
36+0+0 |
36 |
||
TCH/AHS7.413 |
228 |
4 |
||
Class I15 |
120 + 6 + 4 |
65/98 |
196 |
|
Class II |
28+0+0 |
28 |
||
TCH/AHS6.713 |
228 |
4 |
||
Class I16 |
110 + 6 + 4 |
3/5 |
200 |
|
Class II |
24+0+0 |
24 |
||
TCH/AHS5.913 |
228 |
4 |
||
Class I17 |
102 + 6 + 4 |
7/13 |
208 |
|
Class II |
16+0+0 |
16 |
||
TCH/AHS5.1513 |
228 |
4 |
||
Class I18 |
91 + 6 + 4 |
101/212 |
212 |
|
Class II |
12+0+0 |
12 |
||
TCH/AHS4.7513 |
228 |
4 |
||
Class I19 |
83 + 6 + 6 |
95/212 |
212 |
|
Class II |
12+0+0 |
12 |
||
(continued) |
(continued) |
||||
Type of channel |
bits/block data+parity+tail1 |
convolutional code rate |
coded bits per block |
interleaving depth |
TCH/WFS12.654 |
456 |
8 |
||
Class I23 |
253 + 6 + 4 |
263/448 |
448 |
|
TCH/WFS8.854 |
456 |
8 |
||
Class I24 |
177 + 6 + 4 |
187/448 |
448 |
|
TCH/WFS6.64 |
456 |
8 |
||
Class I25 |
132 + 8 + 4 |
9/28 |
448 |
|
O-TCH/WFS23.8527 |
1368 |
8 |
||
Class I23 |
477 + 6 + 6 |
163/448 |
1344 |
|
O-TCH/WFS15.8527 |
1368 |
8 |
||
Class I23 |
317 + 6 + 6 |
47/192 |
1344 |
|
O-TCH/WFS12.6527 |
1368 |
8 |
||
Class I23 |
253 + 6 + 6 |
14/71 |
1344 |
|
O-TCH/WFS8.8527 |
1368 |
8 |
||
Class I24 |
177 + 6 + 6 |
9/64 |
1344 |
|
O-TCH/WFS6.627 |
1368 |
8 |
||
Class I28 |
132 + 6 + 6 |
3/28 |
1344 |
|
O-TCH/WHS12.6526 |
684 |
4 |
||
Class I23 |
253 + 6 + 6 |
265/672 |
672 |
|
O-TCH/WHS8.8526 |
684 |
4 |
||
Class I24 |
177 + 6 + 6 |
9/32 |
672 |
|
O-TCH/WHS6.626 |
684 |
4 |
||
Class I28 |
132 + 6 + 6 |
3/14 |
672 |
|
O-TCH/AHS12.226 |
684 |
4 |
||
Class I5 |
244 + 6 + 6 |
8/21 |
672 |
|
O-TCH/AHS10.226 |
684 |
4 |
||
Class I6 |
204 + 6 + 6 |
9/28 |
672 |
|
O-TCH/AHS7.9526 |
684 |
4 |
||
Class I7 |
159 + 6 + 6 |
57/224 |
672 |
|
O-TCH/AHS7.426 |
684 |
4 |
||
Class I8 |
148 + 6 + 6 |
5/21 |
672 |
|
O-TCH/AHS6.726 |
684 |
4 |
||
Class I9 |
134 + 6 + 6 |
73/336 |
672 |
|
O-TCH/AHS5.926 |
684 |
4 |
||
Class I10 |
118 + 6 + 6 |
65/336 |
672 |
|
O-TCH/AHS5.1526 |
684 |
4 |
||
Class I11 |
103 + 6 + 6 |
115/672 |
672 |
|
O-TCH/AHS4.7526 |
684 |
4 |
||
Class I12 |
95 + 6 + 6 |
107/672 |
672 |
|
TCH/F14.4 TCH/F9.6 |
290 + 0 + 4 4*60 + 0 + 4 |
294/456 244/456 |
294/456 456 |
19 19 |
TCH/F4.8 |
60 + 0 + 16 |
1/3 |
228 |
19 |
TCH/H4.8 |
4*60 + 0 + 4 |
244/456 |
456 |
19 |
TCH/F2.4 |
72 + 0 + 4 |
1/6 |
456 |
8 |
TCH/H2.4 |
72 + 0 + 4 |
1/3 |
228 |
19 |
(continued) |
(continued) |
||||
Type of channel |
bits/block data+parity+tail1 |
convolutional code rate |
coded bits per block |
interleaving depth |
FACCH/F |
184 + 40 + 4 |
½ |
456 |
8 |
E-FACCH/F |
184 + 40 + 4 |
½ |
456 |
4 |
FACCH/H |
184 + 40 + 4 |
½ |
456 |
6 |
O-FACCH/F |
184 + 40 + 6 |
1/6 |
1368 |
8 |
O-FACCH/H |
184 + 40 + 6 |
1/6 |
1368 |
6 |
SDCCHs, SACCHs20, BCCH, EC-BCCH, NCH, AGCH, PCH, CBCH |
184 + 40 + 4 |
½ |
456 |
4 |
EC-AGCH, EC-PCH |
88+18+0 |
106/116 |
116 |
1 |
EC-PICH31 |
88+18+0 |
106/116 |
116 |
1 |
EC-PACCH, downlink |
80+18+0 |
98/114 |
114 |
1 |
EC-PACCH, uplink30 |
64+18+0 |
82/116 |
116 |
1 |
EC-PACCH/48, uplink |
56+18+0 |
74/106 |
106 |
1 |
SACCH/TP SACCH/MP |
184 + 18 + 6 |
½ |
456 |
4 |
E-IACCH |
3 |
1/822 |
24 |
4 |
EPCCH |
3 |
¼22 |
12 |
1 |
RACH EC-RACH (CC1 to CC4) |
8 + 6 + 4 11 + 6 + 4 |
½ ½ |
36 36 |
1 1 |
EC-RACH (CC5), ESAB |
11 + 6 |
1/6 |
102 |
1 |
EC-RACH (CC5), EDAB |
11 + 6 + 4 |
½ |
30 |
1 |
EC-SCH29 |
30 + 10 + 4 |
½ |
78 |
1 |
SCH |
25 + 10 + 4 |
½ |
78 |
1 |
CTSBCH-SB |
25 + 10 + 4 |
½ |
78 |
1 |
CTSPCH |
184 + 40 + 4 |
½ |
456 |
4 |
CTSARCH |
25 + 10 + 4 |
½ |
78 |
1 |
CTSAGCH |
184 + 40 + 4 |
½ |
456 |
4 |
NOTE 1: The tail bits mentioned here are the tail bits of the convolutional code. |
||||
NOTE 2: The 3 parity bits for TCH/FS detect an error on 50 bits of class I. |
||||
NOTE 3: The 3 parity bits for TCH/HS detect an error on 22 bits of class I. |
||||
NOTE 4: For TCH/AFS and TCH/WFS an 8 bits in band signalling codeword is attached to the block of coded information before interleaving. |
||||
NOTE 5: The 6 parity bits for TCH/AFS12.2 and O-TCH/AHS12.2 detect an error on 81 bits of class I. |
||||
NOTE 6: The 6 parity bits for TCH/AFS10.2 and O-TCH/AHS10.2 detect an error on 65 bits of class I. |
||||
NOTE 7: The 6 parity bits for TCH/AFS7.95 and O-TCH/AHS7.95 detect an error on 75 bits of class I. |
||||
NOTE 8: The 6 parity bits for TCH/AFS7.4 and O-TCH/AHS7.4 detect an error on 61 bits of class I. |
||||
NOTE 9: The 6 parity bits for TCH/AFS6.7 and O-TCH/AHS6.7 detect an error on 55 bits of class I. |
||||
NOTE 10: The 6 parity bits for TCH/AFS5.9 and O-TCH/AHS5.9 detect an error on 55 bits of class I. |
||||
NOTE 11: The 6 parity bits for TCH/AFS5.15 and O-TCH/AHS5.15 detect an error on 49 bits of class I. |
||||
NOTE 12: The 6 parity bits for TCH/AFS4.75 and O-TCH/AHS4.75 detect an error on 39 bits of class I. |
||||
NOTE 13: For TCH/AHS a 4 bits in band signalling codeword is attached to the block of coded information before interleaving |
||||
NOTE 14: The 6 parity bits for TCH/AHS7.95 detect an error on 67 bits of class I. |
||||
NOTE 15: The 6 parity bits for TCH/AHS7.4 detect an error on 61 bits of class I. |
||||
NOTE 16: The 6 parity bits for TCH/AHS6.7 detect an error on 55 bits of class I. |
||||
NOTE 17: The 6 parity bits for TCH/AHS5.9 detect an error on 55 bits of class I. |
||||
NOTE 18: The 6 parity bits for TCH/AHS5.15 detect an error on 49 bits of class I. |
||||
NOTE 19: The 6 parity bits for TCH/AHS4.75 detect an error on 39 bits of class I. |
||||
NOTE 20: with the exception of SACCH/TP and SACCH/MP |
||||
NOTE 21: 40 uncoded dummy bits are inserted for the mapping of the enhanced power control signalling |
||||
NOTE 22: block code is applied |
||||
NOTE 23: The 6 parity bits for TCH/WFS12.65, O-TCH/WFS23.85, O-TCH/WFS15.85, O-TCH/WFS12.65 and O-TCH/WHS12.65 detect an error on 72 bits of class I. |
||||
NOTE 24: The 6 parity bits for TCH/WFS8.85, O-TCH/WFS8.85 and O-TCH/WHS8.85 detect an error on 64 bits of class I. |
||||
NOTE 25: The 8 parity bits for TCH/WFS6.60 detect an error on 54 bits of class I. |
||||
NOTE 27: For O-TCH/WFS a 24 bits in band signalling codeword is attached to the block of coded information before interleaving. |
||||
NOTE 28: The 6 parity bits for O-TCH/WFS6.6 and O-TCH/WHS6.6 detect an error on 54 bits of class I. NOTE 29: Two additional information bits available to the physical layer are encoded as a cyclic shift of the mapping of the burst on the physical channel as specified in in 3GPP TS 45.003. NOTE 30: Applies for EC-PACCH/U except EC-PACCH/U/48 using 2 or 4 consecutive PDTCHs. NOTE 31: For EC-PICH, CC3 and EC-PICH, CC4 the EC-CCCH/D coding scheme is used. |
Type of channel |
bits/block data+parity+tail1 |
Reed-Solomon code rate |
convolutional code rate |
coded bits per block |
interleaving depth |
---|---|---|---|---|---|
E-TCH/F43.2 E-TCH/F32.0 E-TCH/F28.8 |
870 + 0 + 6 640 + 0 + 6 580 + 0 + 6 |
N/A N/A 73/85 |
876/1368 646/1392 686/1368 |
1368 1392 1368 |
19 12 19 |
7.2 Packet Traffic and Control Channels
All packet traffic and control channels, except PRACH and EC-PACCH, use rectangular interleaving of one Radio Block over four bursts in consecutive TDMA frames of one PDCH. As an exception, in RTTI configuration, the PDTCH uses rectangular interleaving of one Radio Block over four bursts in two consecutive TDMA frames of a PDCH-pair.
7.2.1 Channel coding for PDTCH
7.2.1.1 Channel coding for GPRS PDTCH
Four different coding schemes, CS-1 to CS-4, are defined for the GPRS Radio Blocks carrying RLC data blocks. For the Radio Blocks carrying RLC/MAC Control blocks code CS-1 is always used. The exceptions are messages that use the existing Access Burst (see 3GPP TS 45.003, e.g. Packet Channel Request). An additional coding scheme is defined for the Access Burst that includes 11 information bits.
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 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 the table below, including:
– the length of each field;
– the number of coded bits (after adding tail bits and convolutional coding);
– the number of punctured bits;
– the data rate, including the RLC header and RLC information.
Scheme |
Code rate |
USF |
Pre-coded USF |
Radio Block excl. USF and BCS |
BCS |
Tail |
Coded |
Punctured |
CS-1 |
½ |
3 |
3 |
181 |
40 |
4 |
456 |
0 |
CS-2 |
»2/3 |
3 |
6 |
268 |
16 |
4 |
588 |
132 |
CS-3 |
»3/4 |
3 |
6 |
312 |
16 |
4 |
676 |
220 |
CS-4 |
1 |
3 |
12 |
428 |
16 |
– |
456 |
– |
CS-1 is the same coding scheme as specified for SDCCH. It consists of a half rate convolutional code for FEC and a 40 bit FIRE code for BCS (and optionally FEC). CS-2 and CS-3 are punctured versions of the same half rate convolutional code as CS-1 for FEC. CS-4 has no FEC.
The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header.
All coding schemes are mandatory for MSs supporting GPRS. Only CS-1 is mandatory for the network.
7.2.1.2 Channel coding for EGPRS and EGPRS2 PDTCH
Nine different modulation and coding schemes, MCS-1 to MCS-9, are defined for the EGPRS Radio Blocks (4 bursts, 20ms in case of BTTI configuration or 10ms in case of RTTI configuration) carrying RLC data blocks. Further, 16 more modulation and coding schemes, DAS-5 to DAS-12 and DBS-5 to DBS-12, are defined for EGPRS2 downlink radio blocks (4 bursts, 20ms in case of BTTI configuration or 10ms in case of RTTI configuration) carrying RLC data blocks and 13 more modulation and coding schemes, UAS-7 to UAS-11 and UBS-5 to UBS-12, are defined for EGPRS2 uplink radio blocks (4 bursts, 20ms in case of BTTI configuration or 10ms in case of RTTI configuration) carrying RLC data blocks. For the Radio Blocks carrying RLC/MAC Control blocks code CS-1 is always used, except in the case of RTTI configuration, when code MCS-0 may be used in the downlink (see subclause 7.2.2). The exceptions are messages that use the existing Access Burst (see 3GPP TS 45.003, e.g. Packet Channel Request). An additional coding scheme is defined for the Access Burst that includes 11 information bits.
To ensure strong header protection, the header part of the Radio Block is independently coded from the data part of the Radio Block (8 bit CRC calculated over the header -excl. USF- for error detection, followed by rate 1/3 convolutional coding – and possibly puncturing – for error correction). Additionally, for transmission using FANR, a PAN field is included which is independently coded from the header and data parts of the Radio Block (the coding is the same as for the header part).
For EGPRS (see 3GPP TS 44.060), the MCSs are divided into different families A, B and C. Each family has a different basic unit of payload (see 3GPP TS 43.064). Different code rates within a family are achieved by transmitting a different number of payload units within one Radio Block. For families A and B, 1, 2 or 4 payload units are transmitted, for family C, only 1 or 2 payload units are transmitted.
For EGPRS2 (see 3GPP TS 44.060), the coding schemes are divided into different families A, B and C. Each family has a different basic unit of payload (see 3GPP TS 43.064). Different code rates within a family are achieved by transmitting a different number of payload units within one Radio Block. For family A, 1, 2, 4, 6 or 8 payload units are transmitted, for family B, 1, 2, 3, 4, 6 or 9 payload units are transmitted, for family C, only 1 or 2 payload units are transmitted.
For EGPRS, when 4 payload units are transmitted (MCS-7, MCS-8 and MCS-9), these are splitted into two separate RLC blocks (i.e. with separate sequence numbers and block check sequences).
For EGPRS2, when 4 payload units are transmitted (UAS-7 to UAS-9, UBS-7, UBS-8, DAS-8, DAS-9, DBS-7 and DBS-8), these are split into two separate RLC blocks (i.e. with separate sequence numbers and block check sequences). When 6 payload units are transmitted (UAS-10, UAS-11, UBS-9, UBS-10, DAS-10, DAS-11, DBS-9 and DBS-10), these are split into three separate RLC blocks (i.e. with separate sequence numbers and block check sequences), except for DAS-10 for which they are split into two separate RLC blocks. When 8 payload units are transmitted (DBS-11, DBS-12, UBS-11 and UBS-12), these are split into four separate RLC blocks (i.e. with separate sequence numbers and block check sequences). When 9 payload units are transmitted (DAS-12), these are split into three separate RLC blocks (i.e. with separate sequence numbers and block check sequences).
The first step of the coding procedure is to add a Block Check Sequence (BCS) for error detection.
In case of convolutional coding, the second step consists of adding six tail bits (TB) and a 1/3 rate convolutional coding for error correction that is punctured to give the desired coding rate.
In case of turbo coding, the second step consists of 1/3 rate turbo coding for error correction (see 3GPP TS 45.003) that is punctured to give the desired coding rate.
The USF has 8 states, which are represented by a binary 3 bit field in the MAC Header. The USF is encoded to 12 symbols for bursts using legacy symbol rate and 16 symbols for bursts using higher symbol rate, (this results in12 bits for GMSK modes, 32 bits for QPSK modes, 36 bits for 8PSK modes, 48 bits for 16-QAM modes at legacy symbol rate (See 3GPP TS 45.004), 64 bits for 16-QAM at higher symbol rate (see 3GPP TS 45.004), 60 bits for 32-QAM at legacy symbol rate and 80 bits for 32-QAM at higher symbol rate).
MSs supporting EGPRS shall support MCS-1 to MCS-9 in downlink and MCS-1 to MCS-4 in uplink. In case an MS supporting EGPRS is 8-PSK capable in uplink, it shall also support MCS-5 to MCS-9 in uplink. A network supporting EGPRS may support only some of the MCSs.
MSs supporting EGPRS2 (see 3GPP TS 44.060) shall support EGPRS coding schemes MCS-1 to MCS-9 in downlink and uplink.
MSs supporting EGPRS2-A (see 3GPP TS 44.060) in the downlink shall support DAS-5 to DAS-12.
MSs supporting EGPRS2-B (see 3GPP TS 44.060) in the downlink shall support DAS-5 to DAS-12 and DBS-5 to DBS-12.
MSs supporting EGPRS2-A in the uplink shall support UAS-7 to UAS-11.
MSs supporting EGPRS2-B in the uplink shall support UAS-7 to UAS-11 and UBS-5 to UBS-12.
A network supporting EGPRS2-A in downlink (respectively uplink) may support only some of DAS-5 to DAS-12 (respectively UAS-7 to UAS-11).
A network supporting EGPRS2-B in downlink (respectively uplink) may support only some of DBS-5 to DBS-12 (respectively UBS-5 to UBS-12).
The details of the EGPRS coding schemes are shown in Table 7.2.1.2.1. An exhaustive description of the EGPRS coding schemes can be found in 3GPP TS 45.003.
Table 7.2.1.2.1 – Coding parameters for the EGPRS coding schemes
Scheme |
Code rate |
Header Code rate |
PAN Code rate |
Modulation |
RLC blocks per Radio Block (20ms) |
Raw Data within one Radio Block |
Family |
BCS |
Tail payload |
HCS |
PCS |
Data rate (Note 3) |
MCS-9 |
1,0 |
0,36 |
n/a |
8PSK |
2 |
2×592 |
A |
2×12 |
2×6 |
8 |
10 |
59,2 |
MCS-8 |
0,92 |
0,36 |
0,42 |
2 |
2×544 |
A |
54,4 |
|||||
MCS-7 |
0,76 |
0,36 |
0,42 |
2 |
2×448 |
B |
44,8 |
|||||
MCS-6 |
0,49 |
1/3 |
0,39 |
1 |
592 48+544 |
A |
12 |
6 |
29,6 27,2 |
|||
MCS-5 |
0,37 |
1/3 |
0,39 |
1 |
448 |
B |
22,4 |
|||||
MCS-4 |
1,0 |
0,53 |
n/a |
GMSK |
1 |
352 |
C |
17,6 |
||||
MCS-3 |
0,85 |
0,53 |
0,63 |
1 |
296 48+248 and 296 |
A |
14,8 13,6 |
|||||
MCS-2 |
0,66 |
0,53 |
0,63 |
1 |
224 |
B |
11,2 |
|||||
MCS-1 |
0,53 |
0,53 |
0,63 |
1 |
176 |
C |
8,8 |
|||||
Note 1: The italic caption indicates the 6 octets of padding when retransmitting MCS-8 block with MCS-3 or MCS-6. For MCS-3, the 6 octets of padding are sent every second block (see 3GPP TS 44.060). Note 2: The number in bracket indicates the coding rate for transmission using FANR, when the PAN is present. Note 3: These data rates are applicable for BTTI configuration. The data rates are doubled in case of RTTI configuration. |
The details of the EGPRS2 coding schemes are shown in the table below. An exhaustive description of the EGPRS2 coding schemes can be found in 3GPP TS 45.003.
Table 7.2.1.2.2: Coding parameters for the EGPRS2 coding schemes
Scheme |
Code rate (Note 5) |
Header Code rate |
PAN code rate (if present) |
Modulation |
RLC blocks per Radio Block (20ms) |
Raw Data within one Radio Block |
Family |
BCS |
Tail payload |
HCS |
PCS |
Data rate (Note 6) |
DAS-12 |
0,96 (0,99) |
0,38 |
0.38 |
32QAM (Note 4) |
3 |
658 |
B |
3×12 |
(Note 7) |
8 |
10 |
98,4 |
DAS-11 |
0,80 (0,83) |
038 |
0.38 |
3 |
546 |
A |
3×12 |
(Note 7) |
81,6 |
|||
DAS-10 |
0,64 (0,66) |
0,33 |
0.38 |
2 |
658 |
B |
2×12 |
(Note 7) |
65,6 |
|||
DAS-9 |
0,68 (0,70) |
0,34 |
0.38 |
16QAM (Note 4) |
2 |
546 |
A |
2×12 |
(Note 7) |
54,4 |
||
DAS-8 |
0,56 (0,58) |
0,34 |
0.38 |
2 |
450 |
B |
2×12 |
(Note 7) |
44,8 |
|||
DAS-7 |
0,54 (0,57) |
033 |
0.38 |
8PSK (Note 4) |
1 |
658 |
B |
12 |
(Note 7) |
32,8 |
||
DAS-6 |
0,45 (0,48) |
0,33 |
0.38 |
1 |
546 |
A |
12 |
(Note 7) |
27,2 |
|||
DAS-5 |
0,37 (0,39) |
0,33 |
0.38 |
1 |
450 |
B |
12 |
(Note 7) |
22,4 |
|||
DBS-12 |
0,98 (1,00) |
0,37 |
0.54 |
32QAM (Note 3) |
4 |
594 |
A |
4×12 |
(Note 7) |
118,4 |
||
DBS-11 |
0,91 (0,93) |
0,37 |
0.38 |
4 |
546 |
A |
4×12 |
(Note 7) |
108,8 |
|||
DBS-10 |
0,72 (0,75) |
0,34 |
0.38 |
3 |
594 |
A |
3×12 |
(Note 7) |
88,8 |
|||
DBS-9 |
0,71 (0,.73) |
0,34 |
0.38 |
16QAM (Note 3) |
3 |
450 |
B |
3×12 |
(Note 7) |
67,2 |
||
DBS-8 |
0,60 (0.63) |
0,31 |
0.38 |
2 |
594 |
A |
2×12 |
(Note 7) |
59,2 |
|||
DBS-7 |
0,47 (0,48) |
0,31 |
0.38 |
2 |
450 |
B |
2×12 |
(Note 7) |
44,8 |
|||
DBS-6 |
0,63 (069) |
0,31 |
0.38 |
QPSK (Note 3) |
1 |
594 |
A |
1×12 |
(Note 7) |
29,6 |
||
DBS-5 |
0,49 (0,53) |
0,31 |
0.38 |
1 |
450 |
B |
1×12 |
(Note 7) |
22,4 |
|||
UAS-11 |
0,95 (0,99) |
0,36 |
0.38 |
16QAM (Note 2) |
3 |
514 |
A |
3×12 |
3×6 |
76,8 |
||
UAS-10 |
0,84 (0,87 |
0,36 |
0.38 |
3 |
450 |
B |
3×12 |
3×6 |
67,2 |
|||
UAS-9 |
0,71 (0,74) |
0,36 |
0.38 |
2 |
594 |
A |
2×12 |
2×6 |
59,2 |
|||
UAS-8 |
0,62 (0,64) |
0,36 |
0.38 |
2 |
514 |
A |
2×12 |
2×6 |
51,2 |
|||
UAS-7 |
0,55 (0,57) |
0,36 |
0.38 |
2 |
450 |
B |
2×12 |
2×6 |
44,8 |
|||
UBS-12 |
0,96 (0,99) |
0,35 |
0.38 |
32QAM (Note 1) |
4 |
594 |
A |
4×12 |
4×6 |
118,4 |
||
UBS-11 |
0,89 (0,91) |
0,35 |
0.38 |
4 |
546 |
A |
4×12 |
4×6 |
108,8 |
|||
UBS-10 |
0,71 (0,73) |
0,35 |
0.36 |
3 |
594 |
A |
3×12 |
3×6 |
88,8 |
|||
UBS-9 |
0,70 (0,72) |
0,32 |
0.36 |
16QAM (Note 1) |
3 |
450 |
B |
3×12 |
3×6 |
67,2 |
||
UBS-8 |
0,60 (0,61) |
0,33 |
0.38 |
2 |
594 |
A |
2×12 |
2×6 |
59,2 |
|||
UBS-7 |
0,46 (0,47) |
0,33 |
0.38 |
2 |
450 |
B |
2×12 |
2×6 |
44,8 |
|||
UBS-6 |
0,62 (0,67) |
0,35 |
0.38 |
QPSK (Note 1) |
1 |
594 |
A |
12 |
6 |
29,6 |
||
UBS-5 |
0,47 (0,51) |
0,35 |
0.38 |
1 |
450 |
B |
12 |
6 |
22,4 |
|||
Note 1: These coding schemes use the higher symbol rate (See 3GPP TS 45.004) and are only available in the uplink Note 2: These coding schemes use the normal symbol rate (See 3GPP TS 45.004) and are only available in the uplink Note 3: These coding schemes use the higher symbol rate (See 3GPP TS 45.004) and are only available in the downlink Note 4: These coding schemes use the normal symbol rate (See 3GPP TS 45.004) and are only available in the downlink Note 5: The number in bracket indicates the code rate for transmission using FANR, when the PAN is present Note 6: These data rates apply in case of BTTI configuration, the data rates are doubled in case of RTTI configuration. Note 7: The turbo code is terminated using 2×3 tail bits resulting in 12 coded bits per RLC block. |
7.2.2 Channel coding for PACCH, PBCCH, PAGCH, PPCH, CPBCCH, CPAGCH, CPPCH, and CSCH
The channel coding for the PBCCH, PAGCH, PPCH, CPBCCH, CPAGCH, and CPPCH corresponds to the coding scheme CS-1. The channel coding for the PACCH corresponds to the coding scheme CS-1; in case of RTTI configuration, the channel coding for the downlink PACCH corresponds to the coding scheme MCS-0 if BTTI USF mode is used and may correspond to either CS-1 or MCS-0 if RTTI USF mode is used. The channel coding for the CSCH is identical to SCH.
7.2.3 Channel Coding for the PRACH and MPRACH
Two types of packet random access burst may be transmitted on the PRACH and MPRACH: an 8 information bits random access burst or an 11 information bits random access burst called the extended packet random access burst. The MS shall support both random access bursts. The channel coding used for the burst carrying the 8 data bit packet random access uplink message is identical to the coding of the random access burst on the RACH. The channel coding used for the burst carrying the 11 data bit packet random access uplink message is a punctured version of the coding of the random access burst on the RACH.
7.2.4 Channel coding for EC-PDTCH, EC-PACCH, EC-AGCH, EC-PCH, EC-PICH, EC-BCCH and EC-SCH
The channel coding for the EC-BCCH corresponds to the coding scheme CS-1. EC-SCH, EC-PACCH, EC-AGCH, EC-PICH and EC-PCH are all defined by separate coding schemes, see 3GPP TS 45.003. The channel coding for the EC-PDTCH for coverage classes CC1 to CC4 is identical to PDTCH for EGPRS, see subclause 7.2.1.2, except for a limitation in puncturing schemes used for MCS-1 to MCS-4. The channel coding for the EC-PDTCH for uplink coverage class CC5 is defined by a separate coding scheme MCS-1′ see 3GPP TS 45.003 [14].
7.2.5 Channel Coding for EC-RACH
For EC-RACH CC1 to CC4, the access burst is used and the coding is identical to the coding for PRACH. For EC-RACH CC5, either the extended synchronization access burst (ESAB) is used, where 11 information bits are encoded to 102 bits with 1/6 coding rate or the extended dual slot access burst (EDAB), where 11 information bits are encoded to 30 bits with 1/2 coding rate see 3GPP TS 45.003 [14].