4.6C Coding/Multiplexing for HS-SCCH type 3 (1.28 Mcps TDD only)
25.2223GPPMultiplexing and channel coding (TDD)Release 17TS
HS-SCCH shall be of type 3 when any of the following conditions is met:
– the variable HS_DSCH_SPS_STATUS is TRUE, and UE is not configured in MIMO mode;
– the variable HS_DSCH_SPS_STATUS is TRUE, and UE is configured in MIMO mode while the variable MIMO SF mode for HS-PDSCH dual stream is SF1.
HS-SCCH type 3 is used to allocate one subframe HS-PDSCH resources for retransmissions of HS-DSCH semi-persistent scheduling operation. The following information is transmitted by means of the HS-SCCH type 3 physical channels.
– Type flag 1 (2 bits): xflag1,1, xflag1,2
– Resource repetition pattern index (2bits): xrrpi,1, xrrpi,2
– Type flag 2 (2 bits): xflag2,1, xflag2,2
– Transport-block size information (2 bits): xtbs,1, xtbs,2
– Time slot information (5bits): xts,1, xts,2, …, xts,5
– Channelisation-code-set information (6 bits): xccs,1, xccs,2, …, xccs, 6
– Modulation scheme information (1 bit): xms,1
– Redundancy version information (2 bits): xrv,1, xrv,2
– Pointer to the previous transmission (4 bits): xptr,1, xptr,2, xptr,3, xptr,4
– HS-SCCH cyclic sequence number (3 bits): xhcsn,1, xhcsn,2, xhcsn,3
– Reserved (1 bit): xres,1
– UE identity (16 bits): xue,1, xue,2, …, xue,16
The following coding/multiplexing steps for HS-SCCH type 3 can be identified:
– multiplexing of HS-SCCH type 3 information (see subclause 4.6C.2)
– CRC attachment for HS-SCCH type 3 (see subclause 4.6C.3);
– channel coding for HS-SCCH type 3 (see subclause 4.6C.4);
– rate matching for HS-SCCH type 3 (see subclause 4.6C.5);
– interleaving for HS-SCCH type 3 (see subclause 4.6C.6);
– mapping to physical channels for HS-SCCH type 3 (see subclauses 4.6C.7 and 4.6C.8).
The general coding/multiplexing flow for HS-SCCH type 3 is shown in Figure 19B.
Figure 19B: Coding and Multiplexing for HS-SCCH type 3
4.6C.1 HS-SCCH type 3 information field mapping
4.6C.1.1 Type flag 1 mapping
The type flag 1 xflag1,1, xflag1,2 are mapped such that xflag1,1 =‘1’corresponds to the MSB and xflag1,2 =‘1’ to the LSB. The type flag 1 is used to distinguish HS-SCCH type 3 from other types.
4.6C.1.2 Resource repetition pattern index mapping
The resource repetition pattern index xrrpi,1, xrrpi,2 are mapped such that xrrpi,1corresponds to the MSB and xrrpi,2 to the LSB. The mapping xrrpi,1, xrrpi,2=’00’ is used to indicate one subframe HS-PDSCH resources assigned for retransmissions of semi-persistent scheduling operation.
4.6C.1.3 Type flag 2 mapping
The type flag 2 xflag2,1, xflag2,2 are mapped such that xflag2,1 =‘1’corresponds to the MSB and xflag2,2 =‘0’ to the LSB. The type flag 2 is used to distinguish HS-SCCH type 3 from other types.
4.6C.1.4 Transport block size index mapping
The transport-block size information xtbs,1, xtbs,2 is the unsigned binary representation of a reference to one of the four Transport-block sizes configured by higher layers. The mapping is performed according to section 4.6B.1.4.
4.6C.1.5 Timeslot information mapping
The mapping of the time slot information xts,1, xts,2, … xts,5 is performed according to section 4.6.1.2.1.
4.6C.1.6 Channelisation code set information mapping
The mapping of the channelisation code set information xccs,1, xccs,2, xccs,3, xccs,4, xccs,5, xccs,6 is performed according to section 4.6B.1.6.
4.6C.1.7 Modulation scheme information mapping
The mapping of the modulation scheme information xms,1 is performed according to table 17 in section 4.6.1.3.
4.6C.1.8 Redundancy version information mapping
The redundancy version (RV) parameters r, s and constellation version parameter b are mapped jointly to produce the value Xrv. Xrv is alternatively represented as the sequence xrv,1, xrv,2 where xrv,1 is the MSB. This is done according to the following tables according to the modulation mode used.
Table 18A: RV mapping for 16QAM and 64QAM
Xrv (value) |
Nsys / Ndata < 1/2 |
Nsys / Ndata ≥ 1/2 |
||||
s |
r |
b |
s |
r |
b |
|
0 |
1 |
0 |
0 |
1 |
0 |
0 |
1 |
1 |
1 |
1 |
0 |
1 |
1 |
2 |
1 |
0 |
2 |
0 |
0 |
0 |
3 |
1 |
0 |
3 |
1 |
0 |
2 |
Table 19A: RV mapping for QPSK
Xrv (value) |
Nsys / Ndata <1/2 |
Nsys / Ndata ≥ 1/2 |
||
s |
r |
s |
r |
|
0 |
1 |
0 |
1 |
0 |
1 |
1 |
1 |
0 |
1 |
2 |
1 |
2 |
0 |
3 |
3 |
1 |
3 |
1 |
2 |
4.6C.1.9 Pointer to the previous transmission mapping
Pointer to the previous transmission xptr,1, xptr,2, xptr,3, xptr,4 is the unsigned binary representation of s, such that the previous transmission of the same transport block started (4+s) subframes before the start of this transmission. And xptr,1 corresponds to the MSB and xptr,4 to the LSB.
4.6C.1.10 HS-SCCH cyclic sequence number
The HS-SCCH cyclic sequence number xhcsn,1, xhcsn,2, xhcsn,3 is mapped such that xhcsn,1 corresponds to the MSB and xhcsn,3 to the LSB.
4.6C.1.11 UE identity
The UE identity is the HS-DSCH Radio Network Identifier (H-RNTI) defined in [12]. This is mapped such that xue,1 corresponds to the MSB and xue,16 to the LSB, cf. [14].
4.6C.2 Multiplexing of HS-SCCH type 3 information
The information carried on the HS-SCCH type 3 is multiplexed onto the bits according to the following rule :
4.6C.3 CRC attachment for HS-SCCH type 3
The sequence of bits , is calculated according to subclause 4.6.3.
4.6C.4 Channel coding for HS-SCCH type 3
Channel coding for the HS-SCCH type 3 shall be done with the general method described in 4.2.3 with the following specific parameters:
The rate 1/3 convolutional coding shall be used for HS-SCCH type 3.
4.6C.5 Rate matching for HS-SCCH type 3
Rate matching for HS-SCCH type 3 shall be done with the general method described in 4.6.5.
4.6C.6 Interleaving for HS-SCCH type 3
Interleaving for HS-SCCH type 3 shall be done with the general method described in 4.2.11.1.
4.6C.7 Physical Channel Segmentation for HS-SCCH type 3
Physical channel segmentation for HS-SCCH type 3 shall be done with the general method described in 4.2.10. The HS-SCCH consists of two physical channels HS-SCCH1 and HS-SCCH2.
4.6C.8 Physical channel mapping for HS-SCCH type 3
Physical channel mapping for the HS-SCCH type 3 shall be done with the general method described in subclause 4.2.12.