4.6H Coding/Multiplexing for HS-SCCH type 8 (1.28 Mcps TDD only)
25.2223GPPMultiplexing and channel coding (TDD)Release 17TS
HS-SCCH shall be of type 8 when any of the following conditions is met:
– The UE is configured in MIMO mode, and the variable MIMO SF mode for HS-PDSCH dual stream is SF1/SF16.
– The UE is configured in MU-MIMO mode, and the UE is configured in MIMO mode with the variable MIMO SF mode for HS-PDSCH dual stream being SF1/SF16.
HS-SCCH type 8 is used for single stream transmission in MIMO mode or in MU-MIMO mode. The following information is transmitted by means of the HS-SCCH type 8 physical channels.
– Channelisation-code-set information (4 bits): xccs,1, xccs,2…, xccs,4
– Transport-block size information (6 bits ): xtbs,1, xtbs,2, …, xtbs,6
– Modulation scheme information (1 bit): xms,1
– Time slot information (5bits): xts,1, xts,2, …, xts,5
– Redundancy version information (2 bits): xrv,1, xrv,2
– Type flag 1 (6 bits): xflag1,1, xflag1,2, xflag1,3, xflag1,4, xflag1,5, xflag1,6,
– Field flag 2 (1 bit): xflag2,1
– Special Information (2 bits): xinfo,1, xinfo,2
– Hybrid-ARQ process information (4 bits): xhap,1, xhap,2, xhap,3, xhap,4,
– HS-SCCH cyclic sequence number (3 bits): xhcsn,1, xhcsn,2, xhcsn,3
– UE identity (16 bits): xue,1, xue,2, …, xue,16
The following coding/multiplexing steps for HS-SCCH type 8 can be identified:
– multiplexing of HS-SCCH type 8 information (see subclause 4.6H.2)
– CRC attachment for HS-SCCH type 8 (see subclause 4.6H.3);
– channel coding for HS-SCCH type 8 (see subclause 4.6H.4);
– rate matching for HS-SCCH type 8 (see subclause 4.6H.5);
– interleaving for HS-SCCH type 8 (see subclause 4.6H.6);
– mapping to physical channels for HS-SCCH type 8 (see subclauses 4.6H.7 and 4.6H.8).
The general coding/multiplexing flow for HS-SCCH type 8 is shown in Figure 19G.
Figure 19G: Coding and Multiplexing for HS-SCCH type 8
4.6H.1 HS-SCCH type 8 information field mapping
4.6H.1.1 Channelisation code set information mapping
HS-PDSCH channelisation codes are allocated contiguously from a signalled start code to a signalled stop code, and the allocation includes both the start and stop code.
If the field flag xflag2,1=‘0’, the special information xinfo,1, xinfo,2 are comprised of the channelisation code set extended information xccs,5, xccs,6 and xinfo,1= xccs,5, xinfo,2= xccs,6. The start code kstart is signalled by the bits xccs,1, xccs,2, xccs,5 and the stop code kstop by the bits xccs,3, xccs,4, xccs,6. The mapping in Table 16Ba below applies.
If a value of kstart = 5 and kstop = 2 is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, kstart > kstop are not used.
If the field flag xflag2,1=‘1’, the bits xinfo,1, xinfo,2 are comprised of the special default midamble pattern indicator (xmpi,1, xmpi,2) and xinfo,1= xmpi,1 and xinfo,2= xmpi,2. The mapping in Table 16Bb below applies. The start code kstart is signalled by the bits xccs,1, xccs,2 and the stop code kstop by the bits xccs,3, xccs,4. The mapping in Table 16Bc below applies.
If a value of kstart =13 and kstop = 4 is signalled, a spreading factor of SF=1 shall be used for the HS-PDSCH resources. Other than this case, kstart > kstop are not used
Table 16Ba: Channelisation code set information mapping
|
kstart |
xccs,1 |
xccs,2 |
xccs,5 |
kstop |
xccs,3 |
xccs,4 |
xccs,6 |
|
1 |
0 |
0 |
0 |
2 |
0 |
0 |
0 |
|
3 |
0 |
0 |
1 |
4 |
0 |
0 |
1 |
|
5 |
0 |
1 |
0 |
6 |
0 |
1 |
0 |
|
7 |
0 |
1 |
1 |
8 |
0 |
1 |
1 |
|
9 |
1 |
0 |
0 |
10 |
1 |
0 |
0 |
|
11 |
1 |
0 |
1 |
12 |
1 |
0 |
1 |
|
13 |
1 |
1 |
0 |
14 |
1 |
1 |
0 |
|
15 |
1 |
1 |
1 |
16 |
1 |
1 |
1 |
Table 16Bb: Special default midamble pattern mapping
|
Special default Mid-amble pattern |
xmpi,1 |
xmpi,2 |
|
pattern 1A |
0 |
0 |
|
pattern 1B |
0 |
1 |
|
pattern 2A |
1 |
0 |
|
pattern 2B |
1 |
1 |
Table 16Bc: Channelisation code set information mapping
|
kstart |
xccs,1 |
xccs,2 |
kstop |
xccs,3 |
xccs,4 |
|
1 |
0 |
0 |
4 |
0 |
0 |
|
5 |
0 |
1 |
8 |
0 |
1 |
|
9 |
1 |
0 |
12 |
1 |
0 |
|
13 |
1 |
1 |
16 |
1 |
1 |
If NON_RECTANGULAR_RESOURCE_ALLOCATION_STATUS is FALSE, HS-PDSCH channelization codes of all the allocated timeslots are indicated by channelisation-code-set information field.
If NON_RECTANGULAR_Resource_ ALLOCATION_STATUS is TRUE and non-rectangular resource specific timeslot set is not configured via higher layer signalling, the specific timeslot refers to the timeslot with the maximal timeslot index among all the timeslots scheduled to the UE and HS-PDSCH channelisation codes of the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of timeslot 0 are signalled via higher layer signalling if timeslot 0 is scheduled to the UE. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of each timeslot is scheduled to the UE with SF=1.
If NON_RECTANGULAR_RESOURCE_ALLOCATION_STATUS is TRUE and non-rectangular resource specific timeslot set is configured via higher layer signalling, HS-PDSCH channelisation codes in the specific timeslot is indicated by channelisation-code set information field. The HS-PDSCH channelisation codes of other scheduled timeslots are predefined, i.e. the entire resource of the timeslot is scheduled to the UE with SF=1.
4.6H.1.2 Transport block size index mapping
The transport-block size information xtbs,1, xtbs,2, …, xtbs,6 is the unsigned binary representation of the transport block size index where xtbs,1 is MSB. The mapping is performed according to section 4.6.1.8.
4.6H.1.3 Modulation scheme information mapping
The mapping of the modulation scheme information xms,1 is performed according to section 4.6.1.3.
4.6H.1.4 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.6H.1.5 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. The mapping is performed according to section 4.6C.1.8. If Xrv =0, the UE shall treat the corresponding transport block as an initial transmission.
4.6H.1.6 Type flag mapping
The type flag xflag1,1, xflag1,2, xflag1,3, xflag1,4, xflag1,5, xflag1,6 is mapped as ‘000000’. The type flag is used to distinguish HS-SCCH type 8 from other types.
4.6H.1.7 Field flag mapping
The field flag is used to distinguish the mapping of special information xinfo,1, xinfo,2.
If xflag2,1=‘0’ , the special information x,info,1, xinfo,2 are comprised of the channelisation code set extended information xccs,5, xccs,6 and xinfo,1= xccs,5, xinfo,2= xccs,6.
If xflag2,1=‘1’ , the special information x,info,1, xinfo,2 are comprised of the special default midamble pattern indicator (xmpi,1, xmpi,2).
4.6H.1.8 Special Information mapping
The special information x,info,1, xinfo,2 is mapped such that x,info,1 corresponds to the MSB and xinfo,2 to the LSB.
If xflag2,1=‘0’ , the special information x,info,1, xinfo,2 are comprised of the channelisation code set extended information xccs,5, xccs,6 and xinfo,1= xccs,5, xinfo,2= xccs,6.
If xflag2,1=‘1’ , the special information x,info,1, xinfo,2 are comprised of the special default midamble pattern indicator (xmpi,1, xmpi,2).
4.6H.1.9 HARQ process identifier mapping
The hybrid-ARQ process information xhap,1, xhap,2, xhap,3, xhap,4 is unsigned binary representation of the HARQ process identifier where xhap,1 is MSB.
4.6H.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.6H.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.6H.2 Multiplexing of HS-SCCH type 8 information
The information carried on the HS-SCCH type 8 is multiplexed onto the bits according to the following rule:
4.6H.3 CRC attachment for HS-SCCH type 8
The sequence of bits , is calculated according to subclause 4.6.3.
4.6H.4 Channel coding for HS-SCCH type 8
Channel coding for the HS-SCCH type 8 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 8.
4.6H.5 Rate matching for HS-SCCH type 8
Rate matching for HS-SCCH type 8 shall be done with the general method described in 4.6.5.
4.6H.6 Interleaving for HS-SCCH type 8
Interleaving for HS-SCCH type 8 shall be done with the general method described in 4.2.11.1.
4.6H.7 Physical Channel Segmentation for HS-SCCH type 8
Physical channel segmentation for HS-SCCH type 8 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.6H.8 Physical channel mapping for HS-SCCH type 8
Physical channel mapping for the HS-SCCH type 8 shall be done with the general method described in subclause 4.2.12.