5.1a.30 Packet data block type 41 (DBS-11)

3GPP45.003GSM/EDGE Channel codingRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.1a.30.1 Block constitution

If the message delivered to the encoder does not include a PAN, it has a fixed size of 2249 information bits {d(0),d(1),…,d(2248)}. If the message delivered to the encoder includes a PAN, it has a fixed size of 2274 information bits {d(0),d(1),…,d(2273).

NOTE: The presence of the PAN is indicated by the PANI field in the header (see 3GPP TS 44.060).

The message is separated into the following parts:

u(k) = d(k) for k = 0,…,2

h(k-3) = d(k) for k = 3,…,64

i1(k-65) = d(k) for k = 65,…,610

i2(k-611) = d(k) for k = 611,…,1156

i3(k-1157) = d(k) for k = 1157,…,1702

i4(k-1703) = d(k) for k = 1703,…,2248

And if a PAN is included:

pn(k-2249) = d(k) for k = 2249,…,2273

5.1a.30.2 USF coding

The USF coding is the same as for DBS-10 as specified in subclause 5.1a.29.2.

5.1a.30.3 Header coding

The header {h(0),…,h(61)} is coded as defined in subclause 5.1a.1.1, with N=62, resulting in a block of 210 bits, {C(0),…,C(209)}.

The code is punctured in such a way that the following coded bits:

{C(30*k+j) for k = 0,…,6, j = 17, 20 and 28, and C(10)} are not transmitted

This results in a block of 188 bits, {hc(0),…,hc(187)}.

5.1a.30.4 Data coding

Each data part, {i1(0),…,i1(545)}, {i2(0),…,i2(545)}, {i3(0),…,i3(545)} and {i4(0),…,i4(545)}, is coded as defined in subclause 5.1a.1.3, with N=546, resulting in four coded blocks of 1686 bits, {C1(0),…,C1(1685)}, {C2(0),…,C2(1685)}, {C3(0),…,C3(1685)} and {C4(0),…,C4(1685)}.

Each coded block is punctured depending on the value of the CPS field as defined in 3GPP TS 44.060. Three puncturing schemes named P1, P2 or P3 are applied.

The parameter values used for rate matching are: swap=0, =562,=620 and =600.

P1 puncturing is generated according to 5.1a.1.3.5

P2 (Type 2) puncturing is generated according to 5.1a.1.3.5.

P3 puncturing is generated according to 5.1a.1.3.5.

If a PAN is not included, the result is four blocks of 620 bits, {c1(0),…,c1(619)}, {c2(0),…,c2(619)}, {c3(0),…,c3(619)} and {c4(0),…,c4(619)}.

If a PAN is included, the result is four blocks of 600 bits, {c1(0),…,c1(599)}, {c2(0),…,c2(599)}, {c3(0),…,c3(599)} and {c4(0),…,c4(599)}.

NOTE: C1 and c1 correspond to i1, C2 and c2 to i2, C3 and c3 to i3, and C4 and c4 to i4.

5.1a.30.5 PAN coding

The PAN coding is the same as for UBS-5 as specified in subclause 5.1a.8.4.

5.1a.30.6 Interleaving

a) Header

The header, {hc(0),…,hc(187)}, is interleaved as defined in subclause 5.1a.2.1, with N_C=188 and a=3, resulting in a block of 188 bits, {hi(0),…,hi(187)}.

b) Data and PAN

If a PAN is not included, the following definitions apply:

dc1(k) = c1(k) for k = 0,…,619

dc2(k) = c2(k) for k = 0,…,619

dc3(k) = c3(k) for k = 0,…,619

dc4(k) = c4(k) for k = 0,…,619

If a PAN is included, the following definitions apply:

dc1(k) = ac(4k) for k = 0,…,19

dc1(k) = c1(k-20) for k = 20,…,619

dc2(k) = ac(4k+1) for k = 0,…,19

dc2(k) = c2(k-20) for k = 20,…,619

dc3(k) = ac(4k+2) for k = 0,…,19

dc3(k) = c3(k-20) for k = 20,…,619

dc4(k) = ac(4k+3) for k = 0,…,19

dc4(k) = c4(k-20) for k = 20,…,619

The four blocks {dc1(0),…,dc1(619)}, {dc2(0),…,dc2(619)}, {dc3(0),…,dc3(619)} and {dc4(0),…,dc4(619)} are separately interleaved as defined in subclause 5.1a.2.2, with N_C=620 and a=141, resulting in the four blocks {di1(0),…,di1(619)}, {di2(0),…,di2(619)}, {di3(0),…,di3(619)} and {di4(0),…,di4(619)}, where di1 corresponds to dc1, di2 to dc2, di3 to dc3 and di4 to dc4.

The blocks are put together as one entity as described by the following rule:

di(k) = di1(k) for k = 0,…,619

di(k) = di2(k-620) for k = 620,…,1239

di(k) = di3(k-1240) for k = 1240,…,1859

di(k) = di4(k-1860) for k = 1860,…,2479

5.1a.30.7 Mapping on a burst

a) Straightforward mapping

The mapping is given by the rule:

For B=0,1,2,3, let

e(B,j) = di(620B+j) for j = 0,…,309

e(B,j) = hi(47B+j-310) for j = 310,…,339

e(B,j) = q(3B+j-340) for j = 340

e(B,j) = hi(47B+j-311) for j = 341

e(B,j) = q(3B+j-341) for j = 342,…,343

e(B,j) = hi(47B+j-313) for j = 344

e(B,j) = u’(20B+j-345) for j = 345,…,364

e(B,j) = hi(47B+j-333) for j = 365,…,379

e(B,j) = di(620B+j-70) for j = 380,…,689

where

q(0),q(1),…,q(11) = 1,1,1,1,1,1,1,1,1,1,1,1 identifies the coding scheme DBS-11 or DBS-12.

b) Bit swapping

After this mapping the following bits are swapped:

For B = 0,1,2,3,

Swap e(B,275+k) with e(B,311+k) for k=0, 3, 5, 8, 10, 13, 15, 18, 20, 23, 25, 28, 30, 33.

Swap e(B,260+k) with e(B,312+k) for k=0, 5, 10.

Swap e(B,263+k) with e(B,327+k) for k=0, 5, 10.

Swap e(B,380+k) with e(B,366+k) for k=0, 3, 5, 8, 10, 13.

Swap e(B,395+k) with e(B,372+k) for k=0, 5.

Swap e(B,398) with e(B,367).

In RTTI configuration, the bursts with B = 0,2 shall be mapped on the PDCH having the lower timeslot number, whereas the bursts with B = 1,3 shall be mapped on the PDCH having the higher timeslot number, see 3GPP TS 45.002.

c) PAN bit swapping

In case a PAN is included in the radio block, the following additional bits are swapped after the bit swapping in b):

For B = 0, 1, 2 and 3

Swap e(B,29) with e(B,110)

Swap e(B,114) with e(B,158)

Swap e(B,141) with e(B,80)

Swap e(B,199) with e(B,188)

Swap e(B,226) with e(B,98)

Swap e(B,381) with e(B,433)

Swap e(B,466) with e(B,480)

Swap e(B,634) with e(B,410)