8.5.45 Enhanced Uplink in CELL_FACH state and Idle mode (FDD only)
25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS
For this version of the specification, when a UE selects a cell, the uplink frequency to be used for the PRACH preamble (physical signal) and DPCCH/E-DPCCH/E-DPDCH transmission shall have a default duplex frequency spacing offset from the downlink frequency that the cell was selected on. The default duplex frequency separation to be used by the UE is specified in [21] for each frequency band.
If variable READY_FOR_COMMON_EDCH is set to TRUE the UE shall:
1> if the UE supports concurrent deployment and System Information Block type 22 includes the IE’s "Concurrent deployment of 2ms and 10ms TTI" and "PRACH preamble control parameters extension list Type 2 (for Enhanced Uplink)"; or
1> if the UE supports concurrent deployment and TTI alignment and Per HARQ process and System Information Block type 22 includes the IE’s "Concurrent deployment of 2ms and 10ms TTI", "PRACH preamble control parameters extension list Type 3 (for Enhanced Uplink)", and either of the IE’s "Coffset" or "Scheduled Transmission configuration":
2> configure the lower layers for concurrent deployment of 2ms and 10ms TTI in a cell;
2> perform common E-DCH TTI selection as described in subclause 8.5.72;
2> configure and use the MAC and the physical layer for the PRACH preamble transmission for both 2ms and 10ms common E-DCH TTI as described in subclause 8.5.73.
1> else if the IE "PRACH preamble control parameters extension list Type 1 (for Enhanced Uplink)" is included in System Information Block 22:
2> if the UE supports NodeB triggered HS-DPCCH transmission and System Information Block type 22 includes IE "NodeB triggered HS-DPCCH transmission"; or
2> if the UE supports HS-DSCH DRX operation with second DRX cycle and System Information Block type 22 includes IE "HS-DSCH DRX in CELL_FACH with second DRX cycle Information "; or
2> if the UE supports Fallback to R99 PRACH and System Information Block type 22 includes IE "Fallback R99 PRACH info":
3> configure and use the MAC and the physical layer for the PRACH preamble transmission as described in subclause 8.5.74.
2> else:
3> configure and use the MAC and the physical layer for the PRACH preamble transmission according to the parameters included in the selected "PRACH preamble control parameters (for Enhanced Uplink)" IE according to [15].
1> else:
2> configure and use the MAC and the physical layer for the PRACH preamble transmission according to the parameters included in the selected "PRACH preamble control parameters (for Enhanced Uplink)" IE according [15].
1> compile a list of candidate common E-DCH resource configuration in the order of appearance as contained in IE "Common E-DCH Resource Configuration information list" and, if present, in IE "Common E-DCH Resource Configuration Information List Extension".
If variable READY_FOR_COMMON_EDCH is set to TRUE, then after receiving the "E-DCH resource index" by MAC with the CMAC-STATUS primitive, the UE shall:
1> determine the value for the FALLBACK_R99_PRACH_ENABLED variable and take the corresponding actions as described in subclause 8.5.76.
1> if variable FALLBACK_R99_PRACH_ENABLED is set to FALSE:
2> the UE selects the Common E-DCH Resource Configuration from the list of candidate common E-DCH resource configuration as follows:
"Index of the selected Common E-DCH resource configuration" = "E-DCH resource index".
2> After selection of a common E-DCH resource configuration, the UE shall configure MAC and the physical layer for E-DCH and HSDPA transmission according to the following:
3> configure Uplink DPCH in accordance with the uplink DPCCH slot format 1 [26], the IE "Uplink DPCH code info" and IE "Uplink DPCH power control info";
3> if IE "ACK/NACK support on HS-DPCCH" is set to TRUE:
4> if any of the IE "ACK", "NACK", or "Ack-Nack repetition factor" is not included in the IE "Uplink DPCH power control info":
5> the UE behaviour is not specified.
4> else:
5> configure the HS-DPCCH in accordance with HS-DPCCH slot format [26], the HS-DPCCH code [28] and IE "Uplink DPCH power control info".
3> for NodeB triggered HS-DPCCH transmission:
4> if any of the IE "ACK", "NACK", or "Ack-Nack repetition factor" is not included in the IE "Uplink DPCH power control info", or if the IE "Measurement Feedback Info" is not included:
5> the UE behaviour is not specified.
4> else:
5> configure the HS-DPCCH in accordance with HS-DPCCH slot format [26], the HS-DPCCH code [28], the IE "Uplink DPCH power control info" and the IE "Measurement Feedback Info".
3> configure the common E-DCH MAC-d flows as described in subclause 8.6.5.24;
3> configure the UL E-DPCCH in accordance with the IE "E-DPCCH info" configuration;
3> if the UE supports concurrent deployment and System Information Block type 22 includes the IE’s "Concurrent deployment of 2ms and 10ms TTI" and "PRACH preamble control parameters extension list Type 2 (for Enhanced Uplink)"; or
3> if the UE supports concurrent deployment and TTI alignment and Per HARQ process and System Information Block type 22 includes the IE’s "Concurrent deployment of 2ms and 10ms TTI", "PRACH preamble control parameters extension list Type 3 (for Enhanced Uplink)", and either of the IE’s "Coffset" or "Scheduled Transmission configuration":
4> if the last selected common E-DCH TTI value in subclause 8.5.72 is 10ms TTI:
5> apply a TTI of 10ms on the E-DPDCH.
4> else:
5> if the "Index of the selected Common E-DCH resource configuration" is less than "Concurrent TTI partition index":
6> apply a TTI of 10ms on the E-DPDCH.
5> else:
6> apply a TTI of 2ms on the E-DPDCH.
6> if the UE supports TTI alignment and Per HARQ process and System Information Block type 22 includes the IE "PRACH preamble control parameters extension list Type 3 (for Enhanced Uplink)", and either of the IE’s "Coffset" or "Scheduled Transmission configuration":
7> if System Information Block type 22 includes the IE "Coffset":
8> configure the lower layers with the IE "Coffset";
7> if System Information Block type 22 includes the IE "Scheduled Transmission configuration":
8> enable "Per HARQ process" scope in the MAC.
8> configure the MAC with a list of HARQ processes on which grants are allowed using information contained in the IE "2ms HARQ process allocation".
3> else:
4> apply the TTI as signalled in the IE "E-DCH Transmission Time Interval" on the E-DPDCH;
3> use a redundancy version for each HARQ transmission as configured by the IE "HARQ RV Configuration";
3> use the same scrambling code for F-DPCH, E-RGCH, E-HICH and E-AGCH reception as configured for the Primary CPICH;
3> use a channelization code for F-DPCH reception as configured by IE "F-DPCH Code number";
3> configure F-DPCH with the F-DPCH slot format as specified in [26];
3> apply the DPC_Mode=0 for F-DPCH according to [29];
3> configure the MAC with the stored IE "E-DPDCH info" configuration;
3> configure the E-HICH in accordance with the IE "E-HICH info" configuration;
3> configure the E-AGCH in accordance with the IE "E-AGCH info" configuration;
3> configure the E-RGCH in accordance with the IE "E-RGCH info" configuration if an E-RGCH configuration has been provided with the system information;
3> configure the radio link as the serving E-DCH radio link;
3> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46.
3> if variable READY_FOR_COMMON_ERGCH is set to TRUE:
4> configure the E-RGCH for radio links other than the serving E-DCH radio link in accordance with the configuration in the stored IE "Common E-RGCH info FDD".
NOTE: If according to the above procedure, the TTI applied on E-DPDCH is different from the TTI signalled in the IE "E-DCH Transmission Time Interval", then the IE’s "Uplink DPCH power control info" and "Measurement Feedback Info" in fact refer the IE’s "Uplink DPCH power control info for Concurrent TTI" and "Measurement Feedback Info for Concurrent TTI" respectively if present in the IE "Common E-DCH system info parameters for Concurrent TTI" of System Information Block type 22.