5.3 Common physical channels
25.2213GPPPhysical channels and mapping of transport channels onto physical channels (TDD)Release 17TS
5.3.1 Primary common control physical channel (P-CCPCH)
The BCH as described in subclause 4.1.2 is mapped onto the Primary Common Control Physical Channel (P-CCPCH). The position (time slot / code) of the P-CCPCH is known from the Physical Synchronisation Channel (PSCH), see subclause 5.3.4.
5.3.1.1 P-CCPCH Spreading
The P-CCPCH uses fixed spreading with a spreading factor SF = 16 as described in subclause 5.2.1.1. The P-CCPCH always uses channelisation code 
.
5.3.1.2 P-CCPCH Burst Types
The burst type 1 as described in subclause 5.2.2 is used for the P-CCPCH unless the entire carrier is dedicated to MBSFN then burst type 4 is used for P-CCPCH. No TFCI is applied for the P-CCPCH.
5.3.1.3 P-CCPCH Training sequences
The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the P-CCPCH.
5.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.
5.3.2.1 S-CCPCH Spreading
The S-CCPCH uses fixed spreading with a spreading factor SF = 16 as described in subclause 5.2.1.1. When S-CCPCH is used for MBSFN operation the spreading factor may be SF = 16 or SF = 1.
5.3.2.2 S-CCPCH Burst Types
The burst types 1,2 or 4 as described in subclause 5.2.2 are used for the S-CCPCHs. TFCI may be applied for S-CCPCHs.
5.3.2.2A S-CCPCH Modulation
When S-CCPCH is used for MBSFN operation, burst type 4 shall be used and the modulation may be QPSK or 16QAM, see table 5A for slot formats. When S-CCPCH is used for all other purposes the modulation shall be QPSK.
5.3.2.3 S-CCPCH Training sequences
The training sequences, i.e. midambles, as described in subclause 5.2.3 are used for the S-CCPCH.
5.3.3 The physical random access channel (PRACH)
The RACH as described in subclause 4.1.2 is mapped onto one uplink physical random access channel (PRACH).
5.3.3.1 PRACH Spreading
The uplink PRACH uses either spreading factor SF=16 or SF=8 as described in subclause 5.2.1.2. 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).
5.3.3.2 PRACH Burst Type
The UEs send uplink access bursts of type 3 randomly in the PRACH. TFCI and TPC are not applied for the PRACH.
5.3.3.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 for burst type 3 are shown in Annex A. The necessary time shifts are obtained by choosing either all k=1,2,3…,K’ (for cells with small radius) or uneven k=1,3,5,…K’ (for cells with large radius). Different cells use different periodic basic codes, i.e. different midamble sets.
For cells with large radius additional midambles may be derived from the time-inverted Basic Midamble Sequence. Thus, the second Basic Midamble Code m2 is the time inverted version of Basic Midamble Code m1.
In this way, a joint channel estimation for the channel impulse responses of all active users within one time slot can be performed by a maximum of two cyclic correlations (in cells with small radius, a single cyclic correlator suffices). The different user specific channel impulse response estimates are obtained sequentially in time at the output of the cyclic correlators.
5.3.3.4 PRACH timeslot formats
For the PRACH the timeslot format is only spreading factor dependent. The timeslot formats 60 and 66 of table 5b are applicable for the PRACH.
5.3.3.5 Association between Training Sequences and Channelisation Codes
For the PRACH there exists a fixed association between the training sequence and the channelisation code. The generic rule to define this association is based on the order of the channelisation codes cQ(k) given by k and the order of the midambles mj(k) given by k, firstly, and j, secondly, with the constraint that the midamble for a spreading factor Q is the same as in the upper branch for the spreading factor 2Q. The index j=1 or 2 indicates whether the original Basic Midamble Sequence (j=1) or the time-inverted Basic Midamble Sequence is used (j=2).
– For the case that all k are allowed and only one periodic basic code m1 is available for the RACH, the association depicted in figure 12 is straightforward.
– For the case that only odd k are allowed the principle of the association is shown in figure 13. This association is applied for one and two basic periodic codes.
Figure 12: Association of Midambles to Channelisation Codes in the OVSF tree for all k
Figure 13: Association of Midambles to Channelisation Codes in the OVSF tree for odd k
5.3.4 The synchronisation channel (SCH)
In TDD mode code group of a cell can be derived from the synchronisation channel. In order not to limit the uplink/downlink asymmetry the SCH is mapped on one or two downlink slots per frame only.
There are two cases of SCH and P-CCPCH allocation as follows:
Case 1) SCH and P-CCPCH allocated in TS#k, k=0….14
Case 2) SCH allocated in two TS: TS#k and TS#k+8, k=0…6; P-CCPCH allocated in TS#k.
Only case 1 is supported in the case that the entire carrier is dedicated to MBSFN.
The position of SCH (value of k) in frame can change on a long term basis in any case.
Due to this SCH scheme, the position of P-CCPCH is known from the SCH.
Figure 14 is an example for transmission of SCH, k=0, of Case 2.
Figure 14: Scheme for Synchronisation channel SCH consisting of one primary sequence Cp and 3 parallel secondary sequences Cs,i in slot k and k+8 (example for k=0 in Case 2)
As depicted in figure 14, the SCH consists of a primary and three secondary code sequences each 256 chips long. The primary and secondary code sequences are defined in [8] clause 7 ‘Synchronisation codes for the 3.84 Mcps option’.
Due to mobile to mobile interference, it is mandatory for public TDD systems to keep synchronisation between base stations. As a consequence of this, a capture effect concerning SCH can arise. The time offset toffset,n enables the system to overcome the capture effect.
The time offset toffset,n is one of 32 values, depending on the code group of the cell, n, cf. ‘table 6 Mapping scheme for Cell Parameters, Code Groups, Scrambling Codes, Midambles and toffset‘ in [8]. Note that the cell parameter will change from frame to frame, cf. ‘Table 7 Alignment of cell parameter cycling and system frame number’ in [8], but the cell will belong to only one code group and thus have one time offset toffset,n. The exact value for toffset,n, regarding column ‘Associated toffset‘ in table 6 in [8] is given by:
5.3.5 Physical Uplink Shared Channel (PUSCH)
The USCH as desribed in subclause 4.1.2 is mapped onto one or more physical uplink shared channels (PUSCH). Timing advance, as described in [9], subclause 4.3, is applied to the PUSCH.
5.3.5.1 PUSCH Spreading
The spreading factors that can be applied to the PUSCH are SF = 1, 2, 4, 8, 16 as described in subclause 5.2.1.2.
5.3.5.2 PUSCH Burst Types
Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for PUSCH. TFCI and TPC can be transmitted on the PUSCH.
5.3.5.3 PUSCH Training Sequences
The training sequences as desribed in subclause 5.2.3 are used for the PUSCH.
5.3.5.4 UE Selection
The UE that shall transmit on the PUSCH is selected by higher layer signalling.
5.3.6 Physical Downlink Shared Channel (PDSCH)
The DSCH as described in subclause 4.1.2 is mapped onto one or more physical downlink shared channels (PDSCH).
5.3.6.1 PDSCH Spreading
The PDSCH uses either spreading factor SF = 16 or SF = 1 as described in subclause 5.2.1.1.
5.3.6.2 PDSCH Burst Types
Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI can be transmitted on the PDSCH.
5.3.6.3 PDSCH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the PDSCH.
5.3.6.4 UE Selection
To indicate to the UE that there is data to decode on the DSCH, three signalling methods are available:
1) using the TFCI field of the associated channel or PDSCH;
2) using on the DSCH user specific midamble derived from the set of midambles used for that cell;
3) using higher layer signalling.
When the midamble based method is used, the UE specific midamble allocation method shall be employed (see subclause 5.6), and the UE shall decode the PDSCH if the PDSCH was transmitted with the midamble assigned to the UE by UTRAN. For this method no other physical channels may use the same time slot as the PDSCH and only one UE may share the PDSCH time slot within one TTI.
Note: From the above mentioned signalling methods, only the higher layer signalling method is supported by higher layers in this release.
5.3.7 The Paging Indicator Channel (PICH)
The Paging Indicator Channel (PICH) is a physical channel used to carry the paging indicators.
5.3.7.1 Mapping of Paging Indicators to the PICH bits
Figure 15 depicts the structure of a PICH burst and the numbering of the bits within the burst. The same burst type is used for the PICH in every cell. NPIB bits in a normal burst of type 1 or 2 are used to carry the paging indicators, where NPIB depends on the burst type: NPIB=240 for burst type 1 and NPIB=272 for burst type 2. The bits sNPIB+1,…, sNPIB+4 adjacent to the midamble are reserved for possible future use.
Figure 15: Transmission and numbering of paging indicator carrying bits in a PICH burst
Each paging indicator Pq in one time slot is mapped to the bits {s2Lpi*q+1,…,s2Lpi*(q+1)} within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each paging indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part, as exemplary shown in figure 16 for a paging indicator length LPI of 4 symbols.
Figure 16: Example of mapping of paging indicators on PICH bits for LPI=4
The setting of the paging indicators and the corresponding PICH bits (including the reserved ones) 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 and the burst type, which are both known by higher layer signalling. In table 7 this number is shown for the different possibilities of burst types and paging indicator lengths.
Table 7: Number NPI of paging indicators per time slot for the different burst types and paging indicator lengths LPI
|
LPI=2 |
LPI=4 |
LPI=8 |
|
|
Burst Type 1 |
NPI=60 |
NPI=30 |
NPI=15 |
|
Burst Type 2 |
NPI=68 |
NPI=34 |
NPI=17 |
5.3.7.2 Structure of the PICH over multiple radio frames
As shown in figure 17, the paging indicators of NPICH consecutive frames form a PICH block, NPICH is configured by higher layers. Thus, NP=NPICH*NPI paging indicators are transmitted in each PICH block.
Figure 17: Structure of a PICH block
The value PI (PI = 0, …, NP-1) calculated by higher layers for use for a certain UE, see [15], is associated to the paging indicator Pq in the nth frame of one PICH block, where q is given by
q = PI mod NPI
and n is given by
n = PI div NPI.
The PI bitmap in the PCH data frames over Iub contains indication values for all possible higher layer PI values, see [17]. Each bit in the bitmap indicates if the paging indicator Pq associated with that particular PI shall be set to 0 or 1. Hence, the calculation in the formulas above is to be performed in Node B to make the association between PI and Pq.
5.3.7.3 PICH Training sequences
The training sequences, i.e. midambles for the PICH.are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the PICH.
– If no antenna diversity is applied the PICH the midambles can be allocated as described in subclause 5.6.
– If SCTD antenna diversity is applied to the PICH the allocation of midambles shall be as described in [9].
5.3.8 The physical node B synchronisation channel (PNBSCH)
In case cell sync bursts are used for Node B synchronisation the PNBSCH shall be used for the transmission of the cell sync burst [8]. The PNBSCH shall be mapped on the same timeslot as the PRACH acc. to a higher layer schedule. The cell sync burst shall be transmitted at the beginning of a timeslot. In case of Node B synchronisation via the air interface the transmission of a RACH may be prohibited on higher layer command in specified frames and timeslots.
5.3.9 High Speed Physical Downlink Shared Channel (HS-PDSCH)
The HS-DSCH as desribed in subclause 4.1.2 is mapped onto one or more high speed physical downlink shared channels (HS-PDSCH).
5.3.9.1 HS-PDSCH Spreading
The HS-PDSCH shall use either spreading factor SF = 16 or SF=1, as described in 5.2.1.1.
5.3.9.2 HS-PDSCH Burst Types
Burst types 1 or 2 as described in subclause 5.2.2 can be used for PDSCH. TFCI shall not be transmitted on the HS-PDSCH. The TF of the HS-DSCH is derived from the associated HS-SCCH.
5.3.9.3 HS-PDSCH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the HS-PDSCH.
5.3.9.4 UE Selection
To indicate to the UE that there is data to decode on the HS-DSCH, the UE id on the associated HS-SCCH shall be used.
5.3.9.5 HS-PDSCH timeslot formats
An HS-PDSCH may use QPSK or 16QAM modulation symbols. The time slot formats are shown in table 7A.
Table 7A: Time slot formats for the HS-PDSCH
|
Slot Format # |
Spreading Factor |
Midamble length (chips) |
NTFCI code word (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field (bits) |
|---|---|---|---|---|---|---|
|
0 (QPSK) |
16 |
512 |
0 |
244 |
244 |
122 |
|
1 (16QAM) |
16 |
512 |
0 |
488 |
488 |
244 |
|
2 (QPSK) |
16 |
256 |
0 |
276 |
276 |
138 |
|
3 (16QAM) |
16 |
256 |
0 |
552 |
552 |
276 |
|
4 (QPSK) |
1 |
512 |
0 |
3904 |
3904 |
1952 |
|
5 (16QAM) |
1 |
512 |
0 |
7808 |
7808 |
3904 |
|
6 (QPSK) |
1 |
256 |
0 |
4416 |
4416 |
2208 |
|
7(16QAM) |
1 |
256 |
0 |
8832 |
8832 |
4416 |
5.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.
5.3.10.1 HS-SCCH Spreading
The HS-SCCH shall use spreading factor SF = 16, as described in 5.2.1.1.
5.3.10.2 HS-SCCH Burst Types
Burst type 1 as described in subclause 5.2.2 can be used for HS-SCCH. TFCI shall not be transmitted on the HS-SCCH.
5.3.10.3 HS-SCCH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the HS-SCCH.
5.3.10.4 HS-SCCH timeslot formats
The HS-SCCH always uses time slot format #0 from table 5a, see section 5.2.2.6.1.
5.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. 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.
5.3.11.1 HS-SICH Spreading
The HS-SICH shall use spreading factor SF = 16, as described in 5.2.1.2.
5.3.11.2 HS-SICH Burst Types
Burst type 1 as described in subclause 5.2.2 can be used for HS-SICH. TFCI shall not be transmitted on the HS-SICH, however, the HS-SICH shall carry TPC information.
5.3.11.3 HS-SICH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the HS-SICH.
5.3.11.4 HS-SICH timeslot formats
The HS-SICH shall use time slot format #90 from table 5b, see section 5.2.2.6.2.
5.3.12 The MBMS Indicator Channel (MICH)
The MBMS Indicator Channel (MICH) is a physical channel used to carry the MBMS notification indicators. The UE may use multiple MICH within the MBMS modification period in order to make decisions on individual MBMS notification indicators.
5.3.12.1 Mapping of MBMS Indicators to the MICH bits for burst types 1 and 2
Figure 17a depicts the structure of a MICH burst and the numbering of the bits within the burst. The same burst type is used for the MICH in every cell. NNIB bits in a normal burst of type 1 or 2 are used to carry the MBMS notification indicators, where NNIB depends on the burst type: NNIB=240 for burst type 1 and NNIB=272 for burst type 2. The bits sNNIB+1,…, sNNIB+4 adjacent to the midamble are reserved for possible future use.
Bits for Notification Indication
Reserved Bits
Bits for Notification Indication
s
1
s
3
s
NNIB-1
s
NNIB+1
s
NNIB+3
s
NNIB+2
s
NNIB+4
s
2
s
4
s
NNIB
…..
Midamble
…..
Guard Period
1 Time Slot
Figure 17a: Transmission and numbering of MBMS notification indicator carrying bits in a MICH burst using burst types 1 and 2
Each notification indicator Nq in one time slot is mapped to the bits {s2LNI*q+1,…,s2LNI*(q+1)} within this time slot. Thus, due to the interleaved transmission of the bits half of the symbols used for each MBMS notification indicator are transmitted in the first data part, and the other half of the symbols are transmitted in the second data part: an example is shown in figure 17b for a MBMS notification indicator length LNI of 4 symbols.
Midamble
(256 Chips)
GP
2560T
C
N
0
N
33
2 unused
symbols
….
….
Midamble
(512 Chips)
GP
2560T
C
N
0
N
29
2 unused
symbols
….
….
Figure 17b: Example of mapping of MBMS notification indicators on MICH bits for LNI=4 for burst types 2 and 1 respectively
The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
Nn MBMS notification indicators of length LNI=2, LNI=4 or LNI=8 symbols are transmitted in each MICH. The number of MBMS notification indicators Nn per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7B this number is shown for burst types 1 and 2 and differing MBMS notification indicator lengths.
Table 7B: Number Nn of MBMS notification indicators per time slot for the different burst types 1 and 2 and differing MBMS notification indicator lengths LNI
|
LNI=2 |
LNI=4 |
LNI=8 |
|
|
Burst Type 1 |
Nn=60 |
Nn=30 |
Nn=15 |
|
Burst Type 2 |
Nn=68 |
Nn=34 |
Nn=17 |
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 should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
5.3.12.1A Mapping of MBMS Indicators to the MICH bits for burst type 4
When an entire carrier is dedicated to MBSFN operation, the MICH shall use burst type 4. In this case NNIB=256 and there are 8 reserved/unused bits adjacent to the midamble reserved for possible future use. The transmission and numbering of MBMS notification indicator carrying bits in a MICH burst is similar to that of figure 17a with the exception of 4 reserved bits either side of the midamble as opposed to 2 for burst types 1 and 2. An example mapping is shown in figure 17ba for a MBMS notification indicator length LNI of 4 symbols.
Figure 17ba: Example of mapping of MBMS notification indicators on MICH bits for LNI=4 for burst type 4
The setting of the MBMS notification indicators and the corresponding MICH bits (including the reserved ones) is described in [7].
Nn MBMS notification indicators of length LNI=2, LNI=4 or LNI=8 symbols are transmitted in each MICH. The number of MBMS notification indicators Nn per MICH is given by the MBMS notification indicator length and the burst type, which are both known by higher layer signalling. In table 7BA this number is shown for the different possibilities of burst types and MBMS notification indicator lengths.
Table 7BA: Number Nn of MBMS notification indicators per time slot for burst type 4 and differing MBMS notification indicator lengths LNI
|
LNI=2 |
LNI=4 |
LNI=8 |
|
|
Burst Type 4 |
Nn=64 |
Nn=32 |
Nn=16 |
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 should be set to 1 during the corresponding modification period; all other indicators shall be set to 0.
5.3.12.2 MICH Training sequences
The training sequences, i.e. midambles for the MICH, are generated as described in subclause 5.2.3. The allocation of midambles depends on whether SCTD is applied to the MICH.
– If no antenna diversity is applied the MICH the midambles can be allocated as described in subclause 5.6.
– If SCTD antenna diversity is applied to the MICH the allocation of midambles shall be as described in [9].
Note that when the entire carrier is dedicated to MBSFN operation MICH employs burst type 4 as described in subclause 5.3.12.1A. Burst type 4 supports a single midamble and hence SCTD is precluded from operation in such a scenario.
5.3.13 E-DCH Physical Uplink Channel (E-PUCH)
One or more E-PUCH 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. No other physical channels may be transmitted by a UE in an E-PUCH timeslot.
Timing advance, as described in [9], subclause 4.3, is applied to the E-PUCH.
5.3.13.1 E-UCCH
The E-DCH Uplink Control Channel (E-UCCH) carries uplink control information associated with the E-DCH and is carried within indicator fields mapped to E-PUCH. Depending on the configuration by higher layers, 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.
Higher layers shall indicate the maximum number of timeslots (NE-UCCH) that may contain E-UCCH/TPC in the E-DCH TTI. For an allocation of nTS E-PUCH timeslots, the UE shall transmit E-UCCH and TPC on the first m allocated timeslots of the E-DCH TTI, where m = min(nTS , NE-UCCH).
The E-UCCH comprises two parts, E-UCCH part 1 and E-UCCH part 2.
E-UCCH part 1:
– is of length 32 physical channel bits
– is mapped to the TFCI field of the E-PUCH (16 bits either side of the midamble)
– is spread at SF=16 using the channelisation code in the branch with the highest code numbering of the allowed OVSF sub tree, as depicted in [8]
– uses QPSK modulation
E-UCCH part 2:
– is of length 32 physical channel bits
– is spread using the same spreading factor as the data payloads
– uses the same modulation as the data payloads
Figures 17c and 17d show the E-PUCH data burst with and without the E-UCCH/TPC fields.
Figure 17c: Location of E-UCCH part 1, E-UCCH part 2 and TPC in the E-PUCH data burst
Figure 17d: E-PUCH data burst without E-UCCH/TPC
5.3.13.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 5.2.1.2.
5.3.13.3 E-PUCH Burst Types
Burst types 1, 2 or 3 as described in subclause 5.2.2 can be used for E-PUCH. E-UCCH and TPC can be transmitted on the E-PUCH.
5.3.13.4 PUSCH Training Sequences
The training sequences as desribed in subclause 5.2.3 are used for the E-PUCH.
5.3.13.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.
5.3.13.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 7c.
Table 7c: Timeslot formats for E-PUCH
|
slot format # |
SF |
Midamble Length (chips) |
GP (chips) |
NEUCCH1 (bits) |
NEUCCH2 (bits) |
NTPC (bits) |
Bits/slot |
Ndata/slot (bits) |
Ndata/data field(1) (bits) |
Ndata/data field(2) (bits) |
|---|---|---|---|---|---|---|---|---|---|---|
|
0 (QPSK) |
16 |
512 |
96 |
0 |
0 |
0 |
244 |
244 |
122 |
122 |
|
1 (16QAM) |
16 |
512 |
96 |
0 |
0 |
0 |
488 |
488 |
244 |
244 |
|
2 (QPSK) |
16 |
512 |
96 |
32 |
32 |
2 |
244 |
178 |
90 |
88 |
|
3 (16QAM) |
16 |
512 |
96 |
32 |
32 |
2 |
454 |
388 |
196 |
192 |
|
4 (QPSK) |
16 |
256 |
96 |
0 |
0 |
0 |
276 |
276 |
138 |
138 |
|
5 (16QAM) |
16 |
256 |
96 |
0 |
0 |
0 |
552 |
552 |
276 |
276 |
|
6 (QPSK) |
16 |
256 |
96 |
32 |
32 |
2 |
276 |
210 |
106 |
104 |
|
7 (16QAM) |
16 |
256 |
96 |
32 |
32 |
2 |
518 |
452 |
228 |
224 |
|
8 (QPSK) |
8 |
512 |
96 |
0 |
0 |
0 |
488 |
488 |
244 |
244 |
|
9 (16QAM) |
8 |
512 |
96 |
0 |
0 |
0 |
976 |
976 |
488 |
488 |
|
10 (QPSK) |
8 |
512 |
96 |
32 |
32 |
2 |
454 |
388 |
196 |
192 |
|
11 (16QAM) |
8 |
512 |
96 |
32 |
32 |
2 |
874 |
808 |
408 |
400 |
|
12 (QPSK) |
8 |
256 |
96 |
0 |
0 |
0 |
552 |
552 |
276 |
276 |
|
13 (16QAM) |
8 |
256 |
96 |
0 |
0 |
0 |
1104 |
1104 |
552 |
552 |
|
14 (QPSK) |
8 |
256 |
96 |
32 |
32 |
2 |
518 |
452 |
228 |
224 |
|
15 (16QAM) |
8 |
256 |
96 |
32 |
32 |
2 |
1002 |
936 |
472 |
464 |
|
16 (QPSK) |
4 |
512 |
96 |
0 |
0 |
0 |
976 |
976 |
488 |
488 |
|
17 (16QAM) |
4 |
512 |
96 |
0 |
0 |
0 |
1952 |
1952 |
976 |
976 |
|
18 (QPSK) |
4 |
512 |
96 |
32 |
32 |
2 |
874 |
808 |
408 |
400 |
|
19 (16QAM) |
4 |
512 |
96 |
32 |
32 |
2 |
1714 |
1648 |
832 |
816 |
|
20 (QPSK) |
4 |
256 |
96 |
0 |
0 |
0 |
1104 |
1104 |
552 |
552 |
|
21 (16QAM) |
4 |
256 |
96 |
0 |
0 |
0 |
2208 |
2208 |
1104 |
1104 |
|
22 (QPSK) |
4 |
256 |
96 |
32 |
32 |
2 |
1002 |
936 |
472 |
464 |
|
23 (16QAM) |
4 |
256 |
96 |
32 |
32 |
2 |
1970 |
1904 |
960 |
944 |
|
24 (QPSK) |
2 |
512 |
96 |
0 |
0 |
0 |
1952 |
1952 |
976 |
976 |
|
25 (16QAM) |
2 |
512 |
96 |
0 |
0 |
0 |
3904 |
3904 |
1952 |
1952 |
|
26 (QPSK) |
2 |
512 |
96 |
32 |
32 |
2 |
1714 |
1648 |
832 |
816 |
|
27 (16QAM) |
2 |
512 |
96 |
32 |
32 |
2 |
3394 |
3328 |
1680 |
1648 |
|
28 (QPSK) |
2 |
256 |
96 |
0 |
0 |
0 |
2208 |
2208 |
1104 |
1104 |
|
29 (16QAM) |
2 |
256 |
96 |
0 |
0 |
0 |
4416 |
4416 |
2208 |
2208 |
|
30 (QPSK) |
2 |
256 |
96 |
32 |
32 |
2 |
1970 |
1904 |
960 |
944 |
|
31 (16QAM) |
2 |
256 |
96 |
32 |
32 |
2 |
3906 |
3840 |
1936 |
1904 |
|
32 (QPSK) |
1 |
512 |
96 |
0 |
0 |
0 |
3904 |
3904 |
1952 |
1952 |
|
33 (16QAM) |
1 |
512 |
96 |
0 |
0 |
0 |
7808 |
7808 |
3904 |
3904 |
|
34 (QPSK) |
1 |
512 |
96 |
32 |
32 |
2 |
3394 |
3328 |
1680 |
1648 |
|
35 (16QAM) |
1 |
512 |
96 |
32 |
32 |
2 |
6754 |
6688 |
3376 |
3312 |
|
36 (QPSK) |
1 |
256 |
96 |
0 |
0 |
0 |
4416 |
4416 |
2208 |
2208 |
|
37 (16QAM) |
1 |
256 |
96 |
0 |
0 |
0 |
8832 |
8832 |
4416 |
4416 |
|
38 (QPSK) |
1 |
256 |
96 |
32 |
32 |
2 |
3906 |
3840 |
1936 |
1904 |
|
39 (16QAM) |
1 |
256 |
96 |
32 |
32 |
2 |
7778 |
7712 |
3888 |
3824 |
|
40 (QPSK) |
16 |
512 |
192 |
0 |
0 |
0 |
232 |
232 |
122 |
110 |
|
41 (16QAM) |
16 |
512 |
192 |
0 |
0 |
0 |
464 |
464 |
244 |
220 |
|
42 (QPSK) |
16 |
512 |
192 |
32 |
32 |
2 |
232 |
166 |
90 |
76 |
|
43 (16QAM) |
16 |
512 |
192 |
32 |
32 |
2 |
430 |
364 |
196 |
168 |
|
44 (QPSK) |
8 |
512 |
192 |
0 |
0 |
0 |
464 |
464 |
244 |
220 |
|
45 (16QAM) |
8 |
512 |
192 |
0 |
0 |
0 |
928 |
928 |
488 |
440 |
|
46 (QPSK) |
8 |
512 |
192 |
32 |
32 |
2 |
430 |
364 |
196 |
168 |
|
47 (16QAM) |
8 |
512 |
192 |
32 |
32 |
2 |
826 |
760 |
408 |
352 |
|
48 (QPSK) |
4 |
512 |
192 |
0 |
0 |
0 |
928 |
928 |
488 |
440 |
|
49 (16QAM) |
4 |
512 |
192 |
0 |
0 |
0 |
1856 |
1856 |
976 |
880 |
|
50 (QPSK) |
4 |
512 |
192 |
32 |
32 |
2 |
826 |
760 |
408 |
352 |
|
51 (16QAM) |
4 |
512 |
192 |
32 |
32 |
2 |
1618 |
1552 |
832 |
720 |
|
52 (QPSK) |
2 |
512 |
192 |
0 |
0 |
0 |
1856 |
1856 |
976 |
880 |
|
53 (16QAM) |
2 |
512 |
192 |
0 |
0 |
0 |
3712 |
3712 |
1952 |
1760 |
|
54 (QPSK) |
2 |
512 |
192 |
32 |
32 |
2 |
1618 |
1552 |
832 |
720 |
|
55 (16QAM) |
2 |
512 |
192 |
32 |
32 |
2 |
3202 |
3136 |
1680 |
1456 |
|
56 (QPSK) |
1 |
512 |
192 |
0 |
0 |
0 |
3712 |
3712 |
1952 |
1760 |
|
57 (16QAM) |
1 |
512 |
192 |
0 |
0 |
0 |
7424 |
7424 |
3904 |
3520 |
|
58 (QPSK) |
1 |
512 |
192 |
32 |
32 |
2 |
3202 |
3136 |
1680 |
1456 |
|
59 (16QAM) |
1 |
512 |
192 |
32 |
32 |
2 |
6370 |
6304 |
3376 |
2928 |
5.3.14 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. The characteristics of the E-RUCCH physical channel are identical to those of PRACH (see subclause 5.3.3).
Physical resources available for E-RUCCH are configured by higher layers. E-RUCCH may be mapped to the same physical resources that are assigned for PRACH.
5.3.15 E-DCH Absolute Grant Channel (E-AGCH)
The E-DCH Absolute Grant Channel (E-AGCH) is a downlink physical channel carrying the uplink E-DCH absolute grant control information. E-AGCH carries a TPC field (located immediately after the midamble and spread using SF16) which is used to control the E-PUCH power. Figure 17e illustrates the burst structure of the E‑AGCH.
Figure 17e: Burst structure of E-AGCH
One E-DCH absolute grant for a UE shall be transmitted over one E-AGCH.
5.3.15.1 E-AGCH Spreading
The E-AGCH shall use spreading factor SF = 16, as described in 5.2.1.1.
5.3.15.2 E-AGCH Burst Types
Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-AGCH. TPC shall be transmitted on E-AGCH whereas TFCI shall not be transmitted.
5.3.15.3 E-AGCH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the E-AGCH.
5.3.15.4 E-AGCH timeslot formats
The E-AGCH uses the timeslot formats of Table 7d. These augment downlink slot formats 0…19 of table 5a, see subclause 5.2.2.6.1.
Table 7d: Time slot formats for E-AGCH
|
Slot Format # |
SF |
Midamble length (chips) |
NTFCI code word (bits) |
NTPC (bits) |
Bits/slot |
NData/Slot (bits) |
Ndata/data field (1) (bits) |
Ndata/data field (2) (bits) |
|---|---|---|---|---|---|---|---|---|
|
20 |
16 |
512 |
0 |
2 |
244 |
242 |
122 |
120 |
|
21 |
16 |
256 |
0 |
2 |
276 |
274 |
138 |
136 |
5.3.16 E-DCH Hybrid ARQ Acknowledgement Indicator Channel (E-HICH)
The E-DCH HARQ Acknowledgement indicator channel (E-HICH) is defined in terms of a SF16 downlink physical channel and a signature sequence. The E-HICH carries the uplink E-DCH hybrid ARQ acknowledgement indicator. Figure 17f illustrates the structure of the E-HICH.
Figure 17f – E-HICH Structure
A single channelisation code may carry one or multiple signature sequences. Each signature sequence conveys a HARQ acknowledgement indicator. A maximum of one indicator may be transmitted to a UE. Each acknowledgement indicator is coded to form a signature sequence of 240 bits (b0, b1, … , b239) as defined in [7] and is transmitted within a single E-HICH timeslot. The E-HICH also contains U spare bit locations, where U=4 for burst type 1 and U=36 for burst type 2. The spare bit values are not defined.
5.3.16.1 E-HICH Spreading
Signature sequences (including spare bits inserted) that share the same channelisation code are combined and spread using spreading factor SF=16 as described in [8].
5.3.16.2 E-HICH Burst Types
Burst types 1 and 2 as described in subclause 5.2.2 can be used for E-HICH. Neither TFCI nor TPC shall be transmitted on the E-HICH.
5.3.16.3 E-HICH Training Sequences
The training sequences as described in subclause 5.2.3 are used for the E-HICH.