5A.3 Common physical channels
25.2213GPPPhysical channels and mapping of transport channels onto physical channels (TDD)Release 17TS
5A.3.1 Primary common control physical channel (P-CCPCH)
The BCH as described in section 4.1.2 ‘Common Transport Channels’ is mapped onto the Primary Common Control Physical Channels (P-CCPCH1 and P-CCPCH2). The position (time slot / code) of the P-CCPCHs is fixed in the 1.28Mcps TDD. The P-CCPCHs are mapped onto the first two code channels of timeslot#0 with spreading factor of 16. When the entire carrier is dedicated to MBSFN, the P-CCPCH is mapped onto the first two code channels of MS timeslot with spreading factor of 16. The P-CCPCH is always transmitted with an antenna pattern configuration that provides whole cell coverage.
In a multi-frequency cell the carrier which transmits P-CCPCH is called the primary frequency and the others are called secondary frequencies. A multi-frequency cell has only one primary frequency.
5A.3.1.1 P-CCPCH Spreading
The P-CCPCH uses fixed spreading with a spreading factor SF = 16. The P-CCPCH1 and P-CCPCH2 always use channelisation code 
and 
respectively.
5A.3.1.2 P-CCPCH Burst Format
The burst format as described in section 5A.2.2 is used for the P-CCPCH. No TFCI is applied for the P-CCPCH.
5A.3.1.3 P-CCPCH Training sequences
The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for the P-CCPCH. When the entire carrier is dedicated to MBSFN, the training sequences, i.e. preambles, as described in subclause 5A.2.3.a are used for the P-CCPCH.
5A.3.2 Secondary common control physical channel (S-CCPCH)
PCH and FACH as described in subclause 4.1.2 are mapped onto one or more secondary common control physical channels (S-CCPCH). In this way the capacity of PCH and FACH can be adapted to the different requirements. The time slot and codes used for the S-CCPCH are broadcast on the BCH.
In a multi-frequency cell S-CCPCH shall be transmitted only on the primary frequency.
5A.3.2.1 S-CCPCH Spreading
Except for physical channels in MBSFN time slot, the S-CCPCH uses fixed spreading with a spreading factor SF = 16. as described in subclause 5A.2.1. And the S-CCPCH in MBSFN time slot may use spreading with spreading factor SF =1, 2 or 16.
Note: SF=2 is only used on dedicated MBSFN frequency.
5A.3.2.2 S-CCPCH Burst Format
The burst format as described in section 5A.2.2 is used for the S-CCPCH. TFCI may be applied for S-CCPCHs.
5A.3.2.3 S-CCPCH Training sequences
The training sequences, i.e. midambles, as described in the subclause 5A.2.3 are also used for the S-CCPCH.
5A.3.3 Fast Physical Access CHannel (FPACH)
The Fast Physical Access CHannel (FPACH) is used by the Node B to carry, in a single burst, the acknowledgement of a detected signature with timing and power level adjustment indication to an user equipment. FPACH makes use of one code with spreading factor 16, so that its burst is composed by 44 symbols. The spreading code, training sequence and time slot position are configured by the network and signalled on the BCH.
In a multi-frequency cell the FPACH is transmitted on the primary frequency. The FPACH may also be also transmitted on the secondary frequency in case of handover or E-DCH procedure.
5A.3.3.1 FPACH burst
The FPACH burst contains 32 information bits. Table 8J reports the content description of the FPACH information bits and their priority order:
Table 8J: FPACH information bits description
|
Information field |
Length (in bits) |
|
Signature Reference Number |
3 (MSB) |
|
Relative Sub-Frame Number |
2 |
|
Received starting position of the UpPCH (UpPCHPOS) |
11 |
|
Transmit Power Level Command for RACH message |
7 |
|
Extended part of Received starting position of the UpPCH (UpPCHPOS) |
2 |
|
Reserved bits (default value: 0) |
7 (LSB) |
The use and generation of the information fields is explained in [9].
5A.3.3.1.1 Signature Reference Number
The reported number corresponds to the numbering principle for the cell signatures as described in [8].
The Signature Reference Number value range is 0 – 7 coded in 3 bits such that:
bit sequence(0 0 0) corresponds to the first signature of the cell; …; bit sequence (1 1 1) corresponds to the 8th signature of the cell.
5A.3.3.1.2 Relative Sub-Frame Number
The Relative Sub-Frame Number value range is 0 – 3 coded such that:
bit sequence (0 0) indicates one sub-frame difference; …; bit sequence (1 1) indicates 4 sub-frame difference.
5A.3.3.1.3 Received starting position of the UpPCH (UpPCHPOS)
The size of UpPCHPOS is extended to be 13bits and the received starting position of the UpPCH value range is 0 – 8191 coded such that:
The 11 least significant bits (LSB) of UpPCHPOS are transmitted in the Received starting position of the UpPCH information field and the 2 most significant bits (MSB) of UpPCHPOS are transmitted in the first 2bits of the Reserve bits information field. Bit sequence (0 0 … 0 0 0) indicates the received starting position zero chip; …; bit sequence (1 1 … 1 1 1) indicates the received starting position 8191*1/8 chip.
5A.3.3.1.4 Transmit Power Level Command for the RACH message
The transmit power level command is transmitted in 7 bits.
5A.3.3.2 FPACH Spreading
The FPACH uses only spreading factor SF=16 as described in subclause 5A.3.3. The set of admissible spreading codes for use on the FPACH is broadcast on the BCH.
5A.3.3.3 FPACH Burst Format
The burst format as described in section 5A.2.2 is used for the FPACH.
5A.3.3.4 FPACH Training sequences
The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for FPACH.
5A.3.3.5 FPACH timeslot formats
The FPACH uses slot format #0 of the DL time slot formats given in subclause 5A.2.2.4.1.1.
5A.3.4 The physical random access channel (PRACH)
The RACH as described in subclause 4.1.2 is mapped onto one or more uplink physical random access channels (PRACH). In such a way the capacity of RACH can be flexibly scaled depending on the operators need.
In a multi-frequency cell the PRACH shall be transmitted only on the primary frequency.
5A.3.4.1 PRACH Spreading
The uplink PRACH uses either spreading factor SF=16, SF=8 or SF=4 as described in subclause 5A.2.1. The set of admissible spreading codes for use on the PRACH and the associated spreading factors are broadcast on the BCH (within the RACH configuration parameters on the BCH).
5A.3.4.2 PRACH Burst Format
The burst format as described in section 5A.2.2 is used for the PRACH.
5A.3.4.3 PRACH Training sequences
The training sequences, i.e. midambles, of different users active in the same time slot are time shifted versions of a single periodic basic code. The basic midamble codes as described in subclause 5A.2.3 are used for PRACH.
5A.3.4.4 PRACH timeslot formats
The PRACH uses the following time slot formats taken from the uplink timeslot formats described in sub-clause 5A.2.2.4.1.2:
|
Spreading Factor |
Slot Format # |
|
16 |
0 |
|
8 |
10 |
|
4 |
25 |
5A.3.4.5 Association between Training Sequences and Channelisation Codes
The association between training sequences and channelisation codes of PRACH in the 1.28McpsTDD is same as that of the DPCH.
5A.3.5 The synchronisation channels (DwPCH, UpPCH)
There are two dedicated physical synchronisation channels —DwPCH and UpPCH in each 5ms sub-frame of the 1.28Mcps TDD. The DwPCH is used for the down link synchronisation and the UpPCH is used for the uplink synchronisation.
The position and the contents of the DwPCH are equal to the DwPTS as described in the subclause 5A.1., while the position and the contents of the UpPCH are equal to the UpPTS or other uplink access position indicated by the higher layers.
The DwPCH is transmitted at each sub-frame with an antenna pattern configuration which provides whole cell coverage. Furthermore it is transmitted with a constant power level which is signalled by higher layers.
In a multi-frequency cell the DwPCH shall be transimitted only on the primary frequency. The UpPCH is transmitted on the primary frequency. The UpPCH may also be transmitted on the secondary frequencies in case of handover and the E-RUCCH procedure.
The burst structure of the DwPCH (DwPTS) is described in the figure 18I.
Figure 18I: burst structure of the DwPCH ( DwPTS)
Note: ‘GP’ for ‘Guard Period’
The burst structure of the UpPCH (UpPTS) is described in the figure 18J.
Figure 18J: burst structure of the UpPCH ( UpPTS)
The SYNC-DL code in DwPCH and the SYNC-UL code in UpPCH are not spreaded. The details about the SYNC-DL and SYNC-UL code are described in the corresponding subclause and annex in [8].
5A.3.6 Physical Uplink Shared Channel (PUSCH)
For Physical Uplink Shared Channel (PUSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PUSCH provides the possibility for transmission of TFCI, SS, and TPC in uplink.
The PUSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.5 Physical Uplink Shared Channel (PUSCH)].
5A.3.7 Physical Downlink Shared Channel (PDSCH)
For Physical Downlink Shared Channel (PDSCH) the burst structure of DPCH as described in subclause 5A.2 and the training sequences as described in subclause 5A.2.3 shall be used. PDSCH provides the possibility for transmission of TFCI, SS, and TPC in downlink.
The PDSCH is common with 3.84 Mcps TDD with respect to Spreading and UE selection, cf. [5.3.6 Physical Downlink Shared Channel (PDSCH)].
5A.3.8 The Page Indicator Channel (PICH)
The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators.
The PICH may be associated with
– an S-CCPCH to which a PCH transport channel is mapped, or
– an HS-SCCH associated with the HS-PDSCH(s) to which an HS-DSCH transport channel is mapped, or
– an HS-PDSCH to which an HS-DSCH transport channel carrying paging message is mapped.
In a multi-frequency cell the PICH shall be transmitted only on the primary frequency.
5A.3.8.1 Mapping of Paging Indicators to the PICH bits
Figure 18K depicts the structure of a PICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 ‘Burst Format’] is used for the PICH. NPIB bits are used to carry the paging indicators, where NPIB=352.
Figure 18K: Transmission and numbering of paging indicator
carrying bits in the PICH bursts
Each paging indicator Pq (where Pq, q = 0, …, NPI-1, Pq {0, 1}) in one radio frame is mapped to the bits {s2LPI*q+1,…,s2LPI*(q+1)} in subframe #1 or subframe #2.
The setting of the paging indicators and the corresponding PICH bits is described in [7].
NPI paging indicators of length LPI=2, LPI=4 or LPI=8 symbols are transmitted in each radio frame that contains the PICH. The number of paging indicators NPI per radio frame is given by the paging indicator length, which signalled by higher layers. In table 8K this number is shown for the different possibilities of paging indicator lengths.
Table 8K: Number NPI of paging indicators per radio frame for
different paging indicator lengths LPI
|
LPI=2 |
LPI=4 |
LPI=8 |
|
|
NPI per radio frame |
88 |
44 |
22 |
5A.3.8.2 Structure of the PICH over multiple radio frames
The structure of the PICH over multiple radio frames is common with 3.84 Mcps TDD, cf. [5.3.7.2 Structure of the PICH over multiple radio frames]
5A.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH)
The HS-DSCH as described in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH). In a multi-frequency HS-DSCH cell, HS-PDSCHs may be transmitted on one or more carriers in CELL_DCH state and on only one carrier in CELL_FACH, CELL_PCH and URA_PCH state in a TTI to a UE and the carriers allocated to the UE shall be on contiguous frequencies. In CELL_FACH state, the HS-PDSCHs shall be transmitted on a same carrier as the one on which the uplink transmission resources are allocated to the UE. This carrier can be the primary frequency or the secondary frequency. In CELL_PCH and URA_PCH state, HS-PDSCHs can only be transmitted on the primary frequency. For UE not supporting multi-carrier HS-DSCH reception, the HS-PDSCHs shall be allocated on a same carrier as the one on which the associated DPCH or the uplink transmission resources is allocated.
5A.3.9.1 HS-PDSCH Spreading
For the UEs not configured in MIMO mode, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1.
For the UEs configured in MIMO mode, if SF=16 is configured by higher layers [19] to be not supported for dual stream transmission, the HS-PDSCH shall use spreading factor SF=1 only. Otherwise, the HS-PDSCH shall use either spreading factor SF = 16 or SF=1.
Spreading of the HS-PDSCH is common with 3.84 Mcps TDD, cf. [5.3.9.1HS-PDSCH Spreading]
5A.3.9.2 HS-PDSCH Burst Format
The burst format as described in section 5A.2.2 shall be used for the HS-PDSCH.
5A.3.9.3 HS-PDSCH Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the HS-PDSCH.
5A.3.9.4 UE Selection
UE selection is common with 3.84 Mcps TDD, cf. [5.3.9.4 UE selection].
5A.3.9.5 HS-PDSCH timeslot formats
An HS-PDSCH may use QPSK, 16QAM or 64QAM modulation symbols. The time slot formats are shown in table 8KA.
Table 8KA: Time slot formats for the HS-PDSCH
|
Slot Format # |
SF |
Midamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
0 (QPSK) |
16 |
144 |
0 |
0 & 0 |
88 |
88 |
44 |
44 |
|
1 (16QAM) |
16 |
144 |
0 |
0 & 0 |
176 |
176 |
88 |
88 |
|
2 (QPSK) |
1 |
144 |
0 |
0 & 0 |
1408 |
1408 |
704 |
704 |
|
3 (16QAM) |
1 |
144 |
0 |
0 & 0 |
2816 |
2816 |
1408 |
1408 |
|
4(64QAM) |
16 |
144 |
0 |
0 & 0 |
264 |
264 |
132 |
132 |
|
5 (64QAM) |
1 |
144 |
0 |
0 & 0 |
4224 |
4224 |
2112 |
2112 |
|
6(QPSK) |
16 |
144 |
0 |
2 & 2 |
88 |
84 |
44 |
40 |
|
7(16QAM) |
16 |
144 |
0 |
2 & 2 |
172 |
168 |
88 |
80 |
|
8(QPSK) |
1 |
144 |
0 |
2 & 2 |
1408 |
1404 |
704 |
700 |
|
9(16QAM) |
1 |
144 |
0 |
2 & 2 |
2812 |
2808 |
1408 |
1400 |
Note: Time slot format 6-9 are exclusively used for semi-persistent HS-PDSCH resources. Whether data field is QPSK or 16QAM modulated, QPSK modulation is used for SS and TPC symbols.
5A.3.9.6 Transmission of SS and TPC
For the transmissions on the semi-persistent HS-PDSCH resources without an HS-SCCH, the SS and TPC command for HS-SICH can be conveyed in HS-PDSCH. The transmission of SS and TPC is done in the data parts of the traffic burst. Hence the midamble structure and length is not changed. The TPC information is to be transmitted directly after the SS information, which is transmitted after the midamble. The SS and TPC are transmitted using the physical channel with the lowest physical channel number and the timeslot with the lowest timeslot number.
5A.3.10 Shared Control Channel for HS-DSCH (HS-SCCH)
The HS-SCCH is a DL physical channel that carries higher layer control information for HS-DSCH. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SCCH the structure of which is described below. A number of HS-SCCH types are defined for different purpose, and the actual description is given in [7].
The information on the HS-SCCH is carried by two separate physical channels (HS-SCCH1 and HS-SCCH2). The term HS-SCCH refers to the ensemble of these physical channels.
In CELL_FACH or CELL_PCH state, HS-SCCH order may carry an uplink synchronization establishment command. The structure is the same as described above.
In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is associated with its respective HS-SCCHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier.
5A.3.10.1 HS-SCCH Spreading
Spreading of the HS-SCCH is common with 3.84 Mcps TDD, cf. [5.3.10.1 HS-SCCH Spreading].
5A.3.10.2 HS-SCCH Burst Format
The burst format as described in section 5A.2.2 shall be used for the HS-SCCH.
5A.3.10.3 HS-SCCH Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the HS-SCCH.
5A.3.10.4 HS-SCCH timeslot formats
HS-SCCH1 shall use time slot format #5 and HS-SCCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. HS-SCCH shall carry TPC and SS but no TFCI.
5A.3.11 Shared Information Channel for HS-DSCH (HS-SICH)
The HS-SICH is a UL physical channel that carries higher layer control information and the Channel Quality Indicator CQI for HS-DSCH. If there is associated HS-SICH to an HS-SCCH order, the HS-SICH carries the acknowledgement to the HS-SCCH order command. The HS-SICH may also used as the acknowledgement for an HS-SCCH allocating semi-persistent HS-PDSCH resources. The physical layer will process this information according to [7] and will transmit the resulting bits on the HS-SICH the structure of which is described below.
In case of multi-carrier HS-DSCH reception, the HS-DSCH transmission on each allocated carrier is related to its respective HS-SICHs. The HS-SCCHs and HS-SICHs controlling the same HS-DSCH transmission on a carrier for the same UE shall be allocated on a same carrier.
5A.3.11.1 HS-SICH Spreading
The HS-SICH shall use spreading factor SF = 16, as described in 5.2.1.2.
When MIMO dual-stream is transmitted, the HS-SICH shall use spreading factor SF=8 which shall utilize an additional SF=16 channelisation code along the branch with the higher code numbering of the allowed OVSF sub tree.
5A.3.11.2 HS-SICH Burst Format
The burst format as described in section 5A.2.2 shall be used for the HS-SICH.
5A.3.11.3 HS-SICH Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the HS-SICH.
5A.3.11.4 HS-SICH timeslot formats
The HS-SICH Type 1 shall use time slot format #5 while HS-SICH Type 2 shall use time slot format #20 from table 8G, see section 5A.2.2.4.1.2, i.e., it shall carry TPC and SS but no TFCI. For HS-SICH type 2, two identical TPC symbols denoting one TPC command are transmitted directly after the two identical SS symbols denoting one SS command, which are transmitted after the midamble.
5A.3.12 The MBMS Indicator Channel (MICH) type1
The MBMS Indicator Channel (MICH) type1 is a physical channel used to carry the MBMS notification indicators on a non MBSFN dedicated carrier. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
5A.3.12.1 Mapping of MBMS Indicators to the type1 MICH bits
Figure 18L depicts the structure of a type1 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2 ‘Burst Format’] is used for the MICH. NNIB bits are used to carry the MBMS notification indicators, where NNIB=352.
Figure 18L: Transmission and numbering of MBMS notification indicator carrying bits in a type1 MICH burst
Each notification indicator Nq (where Nq, q = 0, …, Nn-1, Nq {0, 1}) in one radio frame is mapped to the bits {s2LNI*q+1,…,s2LNI*(q+1)} in subframe #1 or subframe #2.
The setting of the MBMS notification indicators and the corresponding type1 MICH bits is described in [7].
Nn MBMS notification indicators of length LNI=2, LNI=4 or LNI=8 symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators NNI per radio frame is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KB this number is shown for the different possibilities of MBMS notification indicator lengths.
Table 8KB: Number NNI of MBMS notification indicators per radio frame on type1 MICH for
different MBMS notification indicator lengths LNI
|
LNI=2 |
LNI=4 |
LNI=8 |
|
|
Nnper radio frame |
88 |
44 |
22 |
The value NI (NI = 0, …, NNI-1) calculated by higher layers, is associated to the MBMS notification indicator Nq, where q = NI mod Nn.
The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on MICH type1 should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
5A.3.12a The MBMS Indicator Channel (MICH) type 2
The MBMS Indicator Channel (MICH) type 2 is a physical channel used to carry the MBMS notification indicators and system information change indicator on a MBSFN dedicated carrier only. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
5A.3.12.1 Mapping of MBMS Indicators to the type 2 MICH bits
Figure 18La depicts the structure of a type 2 MICH transmission and the numbering of the bits within the bursts. The burst type as described in [5A.2.2a ‘MS Burst Format’] is used for the type 2 MICH. 2*LNI bits are used to carry the system information change indicators and NNIB – 2*LNI bits are used to carry the MBMS notification indicators, where NNIB=128 for 10ms long MICH type 2.
Figure 18La: Transmission and numbering of MBMS notification indicator carrying bits in a type 2 MICH burst
Each notification indicator Nq (where Nq, q = 0, …, Nn-1, Nq {0, 1}) in one radio frame is mapped to the bits {s2LNI*q+1,…,s2LNI*(q+1)} in subframe #1 or subframe #2.
The setting of the MBMS notification indicators and the corresponding MICH bits is described in [7].
Nn MBMS notification indicators of length LNI=2, LNI=4 or LNI=8 symbols are transmitted in each radio frame that contains the MICH. The number of MBMS notification indicators NNI per MICH length is given by the MBMS notification indicator length, which is signalled by higher layers. In table 8KBa this number is shown for the different possibilities of MBMS notification indicator lengths.
Table 8KBa: Number NNI of MBMS notification indicators per radio frame on type 2 MICH for
different MBMS notification indicator lengths LNI
|
LNI=2 |
LNI=4 |
LNI=8 |
|
|
Nnper radio frame |
31 |
15 |
7 |
The value NI (NI = 0, …, NNI-1) calculated by higher layers, is associated to the MBMS notification indicator Nq, where q = NI mod Nn.
The set of NI passed over the Iub indicates all higher layer NI values for which the notification indicator on type 2 MICH should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
5A.3.13 Physical Layer Common Control Channel (PLCCH)
The Physical Layer Common Control Channel (PLCCH) is a Node B terminated channel which may be used to carry dedicated (UE-specific) TPC and SS information to multiple UEs. The PLCCH carries TPC and SS information only. No higher layer data is mapped to PLCCH. Each uplink CCTrCH is controlled either by PLCCH or by other appropriate downlink physical channels, under the control of higher layer signalling.
5A.3.13.1 PLCCH Spreading
The PLCCH uses only spreading factor SF=16 as described in subclause 5A.2.1. The spreading codes for use on the PLCCH are indicated by higher layers.
5A.3.13.2 PLCCH Burst Type
The burst format as described in section 5A2.2 is used for the PLCCH.
5A.3.13.3 PLCCH Training Sequence
The training sequences as described in subclause 5A.2.3 are used for PLCCH.
5A.3.13.4 PLCCH timeslot formats
The PLCCH shall use time slot format #0 from table 8G, see section 5A.2.2.4.1.2.
5A.3.14 E-DCH Physical Uplink Channel
UE may have E-PUCH on each carrier. The E-PUCH on one carrier has at least one E-UCCH and one TPC on it. The TPC on the E-PUCH is used to carry the TPC command for the associated downlink control channel on the same carrier. The E-PUCH on one carrier and the E-UCCH and TPC mapped on it obey the following description.
One or more E-PUCH on one carrier are used to carry the uplink E-DCH transport channel and associated control information (E-UCCH) in each E-DCH TTI. In a timeslot designated by UTRAN for E-PUCH use, up to one E-PUCH may be transmitted by a UE.
5A.3.14.1 E-UCCH
The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is mapped to E-PUCH on the same carrier. Depending on the configuration of the number of E-UCCH instances and the number of E-PUCH timeslots, an E-PUCH burst may or may not contain E-UCCH and TPC. When E-PUCH does contain E-UCCH, TPC is also transmitted. When E-PUCH does not contain E-UCCH, TPC is not transmitted.
One E-UCCH instance :
– is of length 32 physical channel bits
– is mapped to the data field of the E-PUCH
– is spread at SF appointed by CRRI
– uses QPSK modulation
There shall be at least one E-UCCH and TPC in every E-DCH TTI. Multiple instances of the same E-UCCH information and TPC can be transmitted within an E-DCH TTI, the detailed number of instances can be set by NodeB MAC-e/i for scheduled transmissions and signalled by higher layers for non-scheduled transmissions. When an E-DCH data block is transmitted on multiple (N) timeslots in one TTI, there will be multiple E-PUCH timeslots. All repetitions of E-UCCH and TPC are evenly distributed on multiple E-PUCH timeslots. N is the number of timeslots of the E-PUCH, M is the number of E-UCCH and TPC instances in one TTI; K is the integral part of M/N; L is the residue of M/N. S is the number of E-UCCHs and TPCs in one E-PUCH timeslot. S equals K+1 for the first L E-PUCH timeslots and equals K for the last (N-L) E-PUCH timeslots.
The mapping relationship between the TPC commands on the Non-scheduled E-PUCH and the DL timeslot and CCTrCH pairs is the same as that between the TPC commands on the UL DPCH and the DL timeslot and CCTrCH pairs (see subclause 5A.2.2.2).
The burst composition of the E-UCCH information and the E-DCH data is shown in figure 18M.
Figure 18M: Multiplexing structure of E-DCH and E-UCCH
An E-UCCH is composed of 32 bits: k0, k1… k31. It is segmented evenly into two parts shown in figure 18N.
Figure 18N: E-UCCH code composition
Figures 18O and 18P show the E-PUCH data burst with and without the E-UCCH/TPC fields.
Figure 18O: E-PUCH data burst with E-UCCH/TPC
Figure 18P: E-PUCH data burst without E-UCCH/TPC
5A.3.14.2 E-PUCH Spreading
The spreading factors that can be applied to the E-PUCH are SF = 1, 2, 4, 8, 16 as described in subclause 5A.2.1. All E-PUCH use the same spreading factor within an E-DCH TTI. For scheduled transmissions, E-PUCHs use the spreading factor indicated by CRRI on E-AGCH.
5A.3.14.3 E-PUCH Burst Types
The burst types as described in subclause 5A.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH.
In case that TPC on non-scheduled E-PUCH is not used to adjust transmitting power level of downlink DPCH, Node B should not apply TPC commands received from non-scheduled E-PUCH.
5A.3.14.4 E-PUCH Training Sequences
The training sequences as desribed in subclause 5A.2.3 are used for the E-PUCH.
5A.3.14.5 UE Selection
UEs that shall transmit on the E-PUCH are selected by higher layers. The UE id on the associated E-AGCH shall be used for identification.
5A.3.14.6 E-PUCH timeslot formats
An E-PUCH may use QPSK or 16QAM modulation symbols and may or may not contain E-UCCH/TPC. The time slot formats are shown in table 8KC.
Table 8KC: Time slot formats for the E-PUCH
|
Slot Format # |
0 (QPSK) |
1 (16QAM) |
2 (QPSK) |
3 (16QAM) |
4 (QPSK) |
5 (16QAM) |
6 (QPSK) |
7 (16QAM) |
8 (QPSK) |
9 (16QAM) |
10 (QPSK) |
11 (16QAM) |
12 (QPSK) |
13 (16QAM) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Spreading Factor |
16 |
16 |
16 |
16 |
16 |
16 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
8 |
|
Midamble length (chips) |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
|
Bits/slot |
88 |
176 |
88 |
142 |
88 |
108 |
176 |
352 |
176 |
318 |
176 |
284 |
176 |
250 |
|
NData/Slot (bits) |
88 |
176 |
54 |
108 |
20 |
40 |
176 |
352 |
142 |
284 |
108 |
216 |
74 |
148 |
|
Ndata/data field(1) (bits) |
44 |
88 |
28 |
56 |
12 |
24 |
88 |
176 |
72 |
144 |
56 |
112 |
40 |
80 |
|
NEUCCH8_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH3_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NEUCCH2_part1(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NEUCCH1_part1(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC1(bits) |
0 |
0 |
2 |
2 |
2 |
2 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH1_part2(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC2(bits) |
0 |
0 |
0 |
0 |
2 |
2 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
|
NEUCCH2_part2(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NTPC3(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
|
NEUCCH3_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NTPC4(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC5(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC6(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC7(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC8(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH8_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
Ndata/data field(2) (bits) |
44 |
88 |
26 |
52 |
8 |
16 |
88 |
176 |
70 |
140 |
52 |
104 |
34 |
68 |
|
Slot Format # |
14 (QPSK) |
15 (16QAM) |
16 (QPSK) |
17 (16QAM) |
18 (QPSK) |
19 (16QAM) |
20 (QPSK) |
21 (16QAM) |
22 (QPSK) |
23 (16QAM) |
24 (QPSK) |
25 (16QAM) |
26 (QPSK) |
27 (16QAM) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Spreading Factor |
8 |
8 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
4 |
|
Midamble length (chips) |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
|
Bits/slot |
176 |
216 |
352 |
704 |
352 |
670 |
352 |
636 |
352 |
602 |
352 |
568 |
352 |
534 |
|
NData/Slot (bits) |
40 |
80 |
352 |
704 |
318 |
636 |
284 |
568 |
250 |
500 |
216 |
432 |
182 |
364 |
|
Ndata/data field(1) (bits) |
24 |
48 |
176 |
352 |
160 |
320 |
144 |
288 |
128 |
256 |
112 |
224 |
96 |
192 |
|
NEUCCH8_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NEUCCH4_part1(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NEUCCH3_part1(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH2_part1(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH1_part1(bits) |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC1(bits) |
2 |
2 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH1_part2(bits) |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC2(bits) |
2 |
2 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH2_part2(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC3(bits) |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH3_part2(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC4(bits) |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
|
NEUCCH4_part2(bits) |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NTPC5(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
|
NEUCCH5_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NTPC6(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC7(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC8(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH8_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
Ndata/data field(2) (bits) |
16 |
32 |
176 |
352 |
158 |
316 |
140 |
280 |
122 |
244 |
104 |
208 |
86 |
172 |
|
Slot Format # |
28 (QPSK) |
29 (16QAM) |
30 (QPSK) |
31 (16QAM) |
32 (QPSK) |
33 (16QAM) |
34 (QPSK) |
35 (16QAM) |
36 (QPSK) |
37 (16QAM) |
38 (QPSK) |
39 (16QAM) |
40 (QPSK) |
41 (16QAM) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Spreading Factor |
4 |
4 |
4 |
4 |
4 |
4 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
Midamble length (chips) |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
|
Bits/slot |
352 |
500 |
352 |
466 |
352 |
432 |
704 |
1408 |
704 |
1374 |
704 |
1340 |
704 |
1306 |
|
NData/Slot (bits) |
148 |
296 |
114 |
228 |
80 |
160 |
704 |
1408 |
670 |
1340 |
636 |
1272 |
602 |
1204 |
|
Ndata/data field(1) (bits) |
80 |
160 |
64 |
128 |
48 |
96 |
352 |
704 |
336 |
672 |
320 |
640 |
304 |
608 |
|
NEUCCH8_part1(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part1(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH3_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NEUCCH2_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NEUCCH1_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC1(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH1_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC2(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
|
NEUCCH2_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NTPC3(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
|
NEUCCH3_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NTPC4(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC5(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC6(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC7(bits) |
0 |
0 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part2(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NTPC8(bits) |
0 |
0 |
0 |
0 |
2 |
2 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
NEUCCH8_part2(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
|
Ndata/data field(2) (bits) |
68 |
136 |
50 |
100 |
32 |
64 |
352 |
704 |
334 |
668 |
316 |
632 |
298 |
596 |
|
Slot Format # |
42 (QPSK) |
43 (16QAM) |
44 (QPSK) |
45 (16QAM) |
46 (QPSK) |
47 (16QAM) |
48 (QPSK) |
49 (16QAM) |
50 (QPSK) |
51 (16QAM) |
52 (QPSK) |
53 (16QAM) |
54 (QPSK) |
55 (16QAM) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Spreading Factor |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
1 |
1 |
1 |
1 |
|
Midamble length (chips) |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
|
Bits/slot |
704 |
1272 |
704 |
1238 |
704 |
1204 |
704 |
1170 |
704 |
1136 |
1408 |
2816 |
1408 |
2782 |
|
NData/Slot (bits) |
568 |
1136 |
534 |
1068 |
500 |
1000 |
466 |
932 |
432 |
864 |
1408 |
2816 |
1374 |
2748 |
|
Ndata/data field(1) (bits) |
288 |
576 |
272 |
544 |
256 |
512 |
240 |
480 |
224 |
448 |
704 |
1408 |
688 |
1376 |
|
NEUCCH8_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part1(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part1(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH3_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH2_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NEUCCH1_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
|
NTPC1(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
2 |
2 |
|
NEUCCH1_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
16 |
16 |
|
NTPC2(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH2_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC3(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH3_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC4(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH4_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC5(bits) |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH5_part2(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC6(bits) |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH6_part2(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC7(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH7_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
0 |
0 |
0 |
0 |
|
NTPC8(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
0 |
0 |
0 |
0 |
|
NEUCCH8_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
0 |
0 |
0 |
0 |
|
Ndata/data field(2) (bits) |
280 |
560 |
262 |
524 |
244 |
488 |
226 |
452 |
208 |
416 |
704 |
1408 |
686 |
1372 |
|
Slot Format # |
56 (QPSK) |
57 (16QAM) |
58 (QPSK) |
59 (16QAM) |
60 (QPSK) |
61 (16QAM) |
62 (QPSK) |
63 (16QAM) |
64 (QPSK) |
65 (16QAM) |
66 (QPSK) |
67 (16QAM) |
68 (QPSK) |
69 (16QAM) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Spreading Factor |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
1 |
|
Midamble length (chips) |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
144 |
|
Bits/slot |
1408 |
2748 |
1408 |
2714 |
1408 |
2680 |
1408 |
2646 |
1408 |
2612 |
1408 |
2578 |
1408 |
2544 |
|
NData/Slot (bits) |
1340 |
2680 |
1306 |
2612 |
1272 |
2544 |
1238 |
2476 |
1204 |
2408 |
1170 |
2340 |
1136 |
2272 |
|
Ndata/data field(1) (bits) |
672 |
1344 |
656 |
1312 |
640 |
1280 |
624 |
1248 |
608 |
1216 |
592 |
1184 |
576 |
1152 |
|
NEUCCH8_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
NEUCCH7_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NEUCCH6_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH5_part1(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH4_part1(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH3_part1(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH2_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NEUCCH1_part1(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC1(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH1_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC2(bits) |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH2_part2(bits) |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC3(bits) |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH3_part2(bits) |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC4(bits) |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH4_part2(bits) |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC5(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH5_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC6(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
2 |
2 |
|
NEUCCH6_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
16 |
16 |
|
NTPC7(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
2 |
2 |
|
NEUCCH7_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
16 |
16 |
|
NTPC8(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
2 |
2 |
|
NEUCCH8_part2(bits) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
16 |
16 |
|
Ndata/data field(2) (bits) |
668 |
1336 |
650 |
1300 |
632 |
1264 |
614 |
1228 |
596 |
1192 |
578 |
1156 |
560 |
1120 |
5A.3.15 E-DCH Random Access Uplink Control Channel (E-RUCCH)
The E-RUCCH is used to carry E-DCH-associated uplink control signalling when E-PUCH resources are not available. It shall be mapped to the same random access physical resources defined by UTRAN.
For multi-carrier E-DCH transmission, each UE is configured with only one carrier for the E-RUCCH transmission. The E-RUCCH on the configured carrier shall be mapped to the same random access physical resources defined by UTRAN on the same carrier.
5A.3.15.1 E-RUCCH Spreading
The E-RUCCH uses spreading factor SF=16 or SF=8 as described in subclause 5A.2.1. The set of admissible spreading codes used on the E-RUCCH are based on the spreading codes of PRACH.
5A.3.15.2 E-RUCCH Burst Format
The burst format as described in section 5A.2.2 is used for the E-RUCCH.
5A.3.15.3 E-RUCCH Training sequences
The training sequences, i.e. midambles, as described in subclause 5A.2.3 are used for E-RUCCH.
5A.3.15.4 E-RUCCH timeslot formats
The timeslot format depends on the spreading factor of the E-RUCCH:
|
Spreading Factor |
Slot Format # |
|
16 |
0 |
|
8 |
10 |
5A.3.16 E-DCH Absolute Grant Channel (E-AGCH)
The E-DCH Absolute Grant Channel (E-AGCH) on one carrier is a downlink physical channel carrying the uplink E-DCH absolute grant control information of the same carrier. The E-AGCH on one carrier uses two separate physical channels (E-AGCH1 and E-AGCH2). The term E-AGCH refers to the ensemble of these physical channels. The detailed description of the E-AGCH on one carrier is given below.
5A.3.16.1 E-AGCH Spreading
Spreading of the E-AGCH is common with 3.84Mcps TDD, cf. [5.3.15.1 E-AGCH Spreading].
5A.3.16.2 E-AGCH Burst Types
The burst structures for E-AGCH1 and E-AGCH2 are shown in figure 18Q and 18R.
Figure 18Q: E-AGCH1 burst structure
Figure 18R: E-AGCH2 burst structure
5A.3.16.3 E-AGCH Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the E-AGCH.
5A.3.16.4 E-AGCH timeslot formats
E-AGCH1 shall use time slot format #5 and E-AGCH2 shall use time slot format #0 from table 8F, see section 5A.2.2.4.1.1, i.e. E-AGCH shall carry TPC and SS for E-PUCH power control and synchronization but no TFCI.
Table 8KD: Timeslot formats for the E-AGCH
|
Slot Format # |
Spreading Factor |
Midamble length (chips) |
NTFCI code word (bits) |
Nss&NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field (1) (bits) |
Ndata/data field (2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
0 |
16 |
144 |
0 |
0&0 |
88 |
88 |
44 |
44 |
|
5 |
16 |
144 |
0 |
2&2 |
88 |
84 |
44 |
40 |
5A.3.17 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)
The E-DCH HARQ Acknowledgement indicator channel (E-HICH) on one carrier is defined in terms of a SF16 downlink physical channel and a signature sequence on the same carrier.
The E-HICH on one carrier carries one or multiple users’ acknowledgement indicator on the same carrier. The detailed description of the E-HICH on one carrier is given below.
Figure 18S illustrates the structure of the E-HICH on one carrier. The E-HICH contains 8 spare bit locations. The spare bit values are undefined. The power of each user’s acknowledgement indicator may be set independently by the Node-B. The number of E-HICHs in a cell is configured by the system.
The acknowledgement indicators for the E-PUCH semi-persistent scheduling operation can be transmitted on the same E-HICH carrying indicators for scheduled traffic or the E-HICH carrying indicators for non-scheduled traffic.
Figure 18S: E-HICH Structure
For Scheduled transmissions, at most four E-HICHs can be configured for one user’s scheduled transmission. Which E-HICH is used to convey the HARQ acknowledgment indicator is indicated by the 2-bit E-HICH indicator on E-AGCH. A single E-HICH may carry one or multiple HARQ acknowledgement indicator(s) which are decided by the Node-B.
For Non-Scheduled transmissions, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. The 80 signature sequences are divided into 20 groups while each group includes 4 sequences. Every non-scheduled user is assigned only one group which are signalled by higher layer. Among the 4 sequences, the first one is used to indicate ACK/NACK, and the other three are used to indicate the TPC/SS commands. The three sequences and their three reverse sequences are the six possible sequences used to indicate the TPC/SS combination state. The reverse sequence is constructed by reverse every bit of the sequence from 0 to 1 or from 1 to 0. The mapping between the index and the TPC/SS command is shown in table 8KE . The index is calculated according to the equation: index=2*A+B, (A=0,1,2; B=0,1). A is the relative index of the selected sequence among the three assigned sequences and B equals to 1 when the reverse sequence is chosen, otherwise, B equals to 0. The power of the sequence used for TPC/SS indication can be set differently from the one used to indicate ACK/NACK.
Table 8KE: Mapping between the index and TPC/SS command
|
index |
TPC command |
SS command |
|
0 |
‘DOWN’ |
‘DOWN’ |
|
1 |
‘UP’ |
‘DOWN’ |
|
2 |
‘DOWN’ |
‘UP’ |
|
3 |
‘UP’ |
‘UP’ |
|
4 |
‘DOWN’ |
‘Do Nothing’ |
|
5 |
‘UP’ |
‘Do Nothing’ |
For the E-DCH semi-persistent scheduling operation, E-HICHs carry not only the HARQ acknowledgement indicators but also TPC and SS commands. Each user is also assigned one signature sequence group including 4 sequences whose usage is completely complying with the definition in non-scheduled transmissions.
The acknowledgement indicator for an E-DCH transmission in TTI "N" is carried by the E-HICH in TTI "N+[TA]"(TA is determined according to the value of nE-HICH). The E-HICH is thus synchronously related to those E-DCH transmissions for which it carries acknowledgement information.
5A.3.17.1 E-HICH Spreading
Multiple users’ signature sequences (including the inserted spare bits) sharing the same channelisation code are combined and spread using spreading factor SF=16 as described in [8].
5A.3.17.2 E-HICH Burst Types
The burst structures for E-HICH are shown in figure 18D.
5A.3.17.3 E-HICH Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the E-HICH.
5A.3.17.4 E-HICH timeslot formats
E-HICH shall use time slot format #0 from table 8F.
5A.3.18 Standalone midamble channel
5A.3.18.1 Standalone midamble channel Burst Format
A standalone midamble channel traffic burst consists of a midamble of 144 chips only. The burst format is shown in Figure 18T. The contents of the traffic burst fields are described in table 8KF.
Table 8KF: The contents of the standalone midamble channel traffic burst format fields
|
Chip number (CN) |
Length of field in chips |
Contents of field |
|
0-351 |
352 |
NULL |
|
352-495 |
144 |
Midamble |
|
496-863 |
368 |
NULL |
Figure 18T: Burst structure of the standalone midamble channel traffic burst format
5A.3.18.3 Standalone midamble channel Training Sequences
The training sequences as described in subclause 5A.2.3 are used for the standalone midamble channel.
5A.3.18.4 Standalone midamble channel timeslot formats
The timeslot formats for the standalone midamble channel are shown in table 8KG.
Table 8KG: Timeslot formats for the standalone midamble channel
|
Slot Format # |
Midamble length (chips) |
NTFCI code word (bits) |
NSS & NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|
|
0 |
144 |
0 |
0 & 0 |
0 |
0 |
0 |
0 |