8.6.6 Physical channel information elements

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

This subclause specifies the actions upon reception and/or non-reception of the physical channel information elements. The combination of the values of those information elements included in a given message shall follow the compatibility rules that are specified in the physical layer specifications. In case those rules are not followed, the UE shall set the variable INVALID_CONFIGURATION to TRUE.

8.6.6.1 Frequency info

If, after completion of the procedure, the UE will be in CELL_DCH state, the UE shall:

1> for 3.84 Mcps TDD and 7.68 Mcps TDD, if the IE "Frequency info" is included; or

1> for 1.28 Mcps TDD, if the IE "Frequency info" is included and the "Second Frequency info" is not included; or

1> for FDD, if the IE "Frequency info" is included in an IE other than the IE "Uplink secondary cell info FDD":

2> if the frequency is different from the currently used frequency:

3> store and use the frequency indicated by the IE "Frequency Info";

3> if the received message is used to perform a Timing-maintained hard handover (see subclause 8.3.5.2), and IE "Timing maintained Synchronization indicator" is included:

4> not perform any physical layer synchronisation procedure (FDD only);

3> else:

4> perform the physical layer synchronisation procedure A as specified in [29] (FDD only).

2> if the frequency is the same as the currently used frequency:

3> continue to use the currently used frequency;

3> perform the physical layer synchronisation procedure A as specified in [29] (FDD only).

1> for 1.28 Mcps TDD, if both the IE "Frequency info" and the IE "Second Frequency info" are included:

2> the frequency in IE "Frequency info" is used as the primary frequency, and the frequency in IE "Second Frequency info" is used as the secondary frequency;

2> store the primary frequency;

2> if the secondary frequency is different with the currently used frequency:

3> store and use the secondary frequency.

2> if the secondary frequency is the same as the currently used frequency:

3> continue to use the currently used frequency.

1> if the IE "Frequency info" is not included and the UE has a currently used frequency:

2> continue to use the currently used frequency;

NOTE If the received message is used to perform a Timing-reinitialised hard handover, and the IE "Frequency Info" is not included, the UE may perform the physical layer synchronisation procedure A as specified in [29] (FDD only).

For 1.28 Mcps TDD, if, after completion of the procedure, the UE will be in CELL_FACH state, the UE shall:

1> if the IE "Frequency info" is included and the "Second Frequency info" is not included:

2> store and use the frequency indicated by the IE "Frequency Info" as working frequency.

1> if both the IE "Frequency info" and the IE "Second Frequency info" are included:

2> the frequency in IE "Frequency info" is used as the primary frequency, and the frequency in IE "Second Frequency info" is used as the secondary frequency;

2> store the primary frequency;

2> if the secondary frequency is different with the currently used frequency:

3> store and use the secondary frequency as working frequency.

2> if the secondary frequency is the same as the currently used frequency:

3> continue to use the currently used frequency as working frequency.

8.6.6.2 Void

8.6.6.2a PNBSCH allocation

The UE shall consider the frame numbers fulfilling the following equation as "PRACH blocked frames" as specified in [33].

SFN = k * Repetition period 

for an integer k with k {0, 1, 2, 3, 4, … , value of IE "Number of repetitions per SFN period" – 1}, where:

Repetition period is: 4096 / value of IE "Number of repetitions per SFN period".

The UE shall configure the physical layer for the physical random access procedure accordingly.

8.6.6.3 Void

8.6.6.3a Downlink information per radio link list

If the IE "Downlink information per radio link list" is included in a received message, the UE shall:

1> if the active set resulting after the reception of the IE "Downlink information per radio link list" would contain radio links indicated by the IE "Downlink DPCH info for each RL" and radio links indicated by the IE "Downlink F-DPCH info for each RL":

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the active set resulting after the reception of the IE "Downlink information per radio link list" would contain radio links indicated by the IE "Downlink DPCH info for each RL" and the radio link is included in the table "Target cell preconfigurations" in the variable TARGET_CELL_PRECONFIGURATION:

2> clear all the entries from the variable TARGET_CELL_PRECONFIGURATION.

1> if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> for FDD, check whether the radio links included in the IE "Downlink information per radio link list" are part of the current active set considering that a radio link is uniquely identified by the downlink UARFCN and the primary scrambling code;

2> for TDD, check whether the radio links included in the IE "Downlink information per radio link list" are part of the current active set considering that a radio link is uniquely identified by the UARFCN and the primary CCPCH;

2> if all radio links included in the IE "Downlink information per radio link list" are part of the current active set:

3> for radio links part of the current active set, and present in the IE "Downlink information per radio link list":

4> update the downlink physical channel configuration according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4.

3> for radio links part of the current active set, and absent in the IE "Downlink information per radio link list":

4> not change its current downlink physical channel configuration;

4> For FDD, in case the IE "Serving HS-DSCH radio link indicator" is set to ‘TRUE’ for another radio link, no longer consider any of these absent radio links as serving HS-DSCH radio link;

4> For FDD, in case the IE "Serving E-DCH radio link indicator" is set to ‘TRUE’ for another radio link, no longer consider any of these absent radio links as serving E-DCH radio link.

2> if all radio links included in the IE "Downlink information per radio link list" are not part of the current active set:

3> perform a hard handover by replacing all the radio links in the current active set with the radio links in the IE "Downlink information per radio link list", each with a downlink physical channel configuration according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4;

3> perform the checks on the value of the IE "Default DPCH Offset Value" as specified in subclause 8.3.5.1.2 or 8.3.5.2.2;

3> act on the IE "Timing indication" and the IE "Default DPCH Offset Value", if included, as specified in subclause 8.5.15.2;

NOTE: UTRAN should not mix radio links which are part of the current active set and radio links which are not part of the current active set in the same IE "Downlink information per radio link list". In such cases the UE behaviour is unspecified.

1> otherwise:

2> if the message was received in CELL_FACH state and the UE would transit to CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

3> establish a downlink physical channel configuration for each of the included radio links according to the IE "Downlink information for each radio link" as specified in subclause 8.6.6.4.

8.6.6.3b Downlink information per radio link list on secondary UL frequency (FDD only)

If the IE "Downlink information per radio link list on secondary UL frequency" is included in a received message, the UE shall:

1> if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message; and

1> the secondary E-DCH active set prior to the reception of the message contains one or more radio links:

2> check whether the radio links included in the IE "Downlink information per radio link list on secondary UL frequency" are part of the current secondary E-DCH active set considering that a radio link is uniquely identified by the primary scrambling code;

2> if all radio links included in the IE "Downlink information per radio link list on secondary UL frequency" are part of the current secondary E-DCH active set:

3> for radio links part of the current secondary E-DCH active set, and present in the IE "Downlink information per radio link list on secondary UL frequency":

4> update the downlink physical channel configuration according to the downlink information for each radio link on secondary uplink frequency, as specified in subclause 8.6.6.4a.

3> for radio links part of the current secondary E-DCH active set, and absent in the IE "Downlink information per radio link list on secondary UL frequency":

4> not change its current downlink physical channel configuration;

3> keep the current activation status of the secondary uplink frequency and take the corresponding actions as described in subclause 8.5.58.

2> if all radio links included in the IE "Downlink information per radio link list on secondary UL frequency" are not part of the current secondary E-DCH active set:

3> replace all the radio links in the current secondary E-DCH active set with the radio links in the IE "Downlink information per radio link list on secondary UL frequency", each with a downlink physical channel configuration according to the downlink information for each radio link on secondary uplink frequency, as specified in subclause 8.6.6.4a;

3> consider the secondary uplink frequency as not activated and take the corresponding actions as described in subclause 8.5.58.

NOTE: UTRAN should not mix radio links which are part of the current secondary E-DCH active set and radio links which are not part of the current secondary E-DCH active set in the same IE "Downlink information per radio link list on secondary UL frequency". In such cases the UE behaviour is unspecified.

1> otherwise:

2> if the message was received in CELL_FACH state and the UE would transit to CELL_DCH state according to subclause 8.6.3.3 applied on the received message; or

2> if the message was received in CELL_DCH state and the secondary E-DCH active set prior to the reception of the message do not contain any radio link:

3> configure the downlink physical channel on the downlink frequency associated with the secondary uplink frequency for each of the included radio links as specified in subclause 8.6.6.4a;

3> consider the secondary uplink frequency as not activated and take the corresponding actions as described in subclause 8.5.58.

8.6.6.4 Downlink information for each radio link

If the IE "Downlink information for each radio link" is included in a received message, the UE shall:

1> if the UE would enter CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> if the UE is in TDD mode and shared transport channels are assigned to the UE:

3> start to receive the indicated Secondary CCPCH.

2> if the UE is in TDD mode and no shared transport channels are assigned to the UE:

3> set the variable UNSUPPORTED_CONFIGURATION to TRUE.

2> For FDD:

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving HS-DSCH radio link and no longer consider any other radio link as serving HS-DSCH radio link.

2> For FDD:

3> if the IE "Serving E-DCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving E-DCH radio link and no longer consider any other radio link as serving E-DCH radio link.

3> if the IE "E-AGCH Info" is included for the serving E-DCH radio link:

4> store the newly received E-AGCH configuration.

NOTE: The UTRAN should always include the IE "E-AGCH info" if the serving E-DCH radio link indicated in the message is another radio link than the serving E-DCH radio link prior to the procedure.

3> if the IE "E-ROCH Info" is included for the serving E-DCH radio link:

4> store the newly received E-ROCH configuration.

3> if the IE "E-HICH information" is included:

4> store this E-HICH configuration for the concerning radio link.

3> if the IE "E-HICH information" is included or previously stored:

4> store this E-RGCH configuration for the concerning radio link, if included.

3> if the IE "E-HICH release indicator" is present:

4> delete the stored E-HICH information;

4> if variable UPLINK_MIMO_TRANSMISSION is set to TRUE:

5> delete the stored E-HICH information for the secondary stream;

3> if the “Secondary TB E-HICH release indicator” is present:

4> delete the stored E-HICH information for the secondary stream;

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

3> if the IE "F-TPICH info" is included:

4> store this F-TPICH configuration for the concerning radio link.

3> determine the value for the variable UPLINK_CLTD_TRANSMISSION and take the corresponding actions as described in subclause 8.5.69.

3> if the IE "Radio Links without DPCH/F-DPCH info" is present:

4> store this IE and indicate to lower layers to start operation with Radio Links without DPCH/F-DPCH.

3> if the IE "Power Control Algorithm 3" is included in the IE "Downlink F-DPCH info for each RL":

4> if the variable DTX_DRX_STATUS is set to TRUE:

5> set the variable INVALID_CONFIGURATION to TRUE.

4> else:

5> indicate to lower layer to perform Power Control Algorithm 3 on the radio link indicated in this IE, as specified in [29].

NOTE: As a result of CELL UPDATE CONFIRM or any reconfiguration message, for those radio links on the same carrier configured with Power Control Algorithm 3, the same power control parameters shall be used; otherwise, the UE behaviour is unspecified.

2> for TDD:

3> if the IE "E-AGCH Info" is included:

4> store the newly received E-AGCH configuration.

3> if the IE "E-HICH information" is included:

4> store the E-HICH configuration.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link.

1> in addition, if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> For FDD:

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving HS-DSCH radio link;

4> if the serving HS-DSCH radio link was another radio link than this radio link prior to reception of the message and the IE "H-RNTI" is not included:

5> clear the variable H_RNTI.

3> if the IE "Serving HS-DSCH radio link indicator" is set to ‘FALSE’ and this radio link was considered the serving HS-DSCH radio link prior to reception of this message:

4> no longer consider this radio link as the serving HS-DSCH radio link.

3> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25;

3> if the IE "Serving E-DCH radio link indicator" is set to ‘TRUE’:

4> consider this radio link as the serving E-DCH radio link;

4> if the serving E-DCH radio link was another radio link than this radio link prior to reception of the message:

5> if the IE "New Primary E-RNTI" is not included:

6> clear the Primary E-RNTI stored in the variable E_RNTI.

5> if the IE "New Secondary E-RNTI" is not included:

6> clear the Secondary E-RNTI stored in the variable E_RNTI.

3> if the IE "Serving E-DCH radio link indicator" is set to ‘FALSE’ and this radio link was considered the serving E-DCH radio link prior to reception of this message:

4> no longer consider this radio link as the serving E-DCH radio link.

3> if the IE "E-HICH release indicator" is present:

4> delete the stored E-HICH, E-AGCH and E-RGCH (if any) configurations.

3> if the IE "E-RGCH release indicator" is present:

4> delete the stored E-RGCH configuration for this RL.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

3> if the IE "F-TPICH release indicator" is present:

4> delete the stored F-TPICH configuration for this RL.

3> determine the value for the variable UPLINK_CLTD_TRANSMISSION and take the corresponding actions as described in subclause 8.5.69.

2> For TDD:

3> if the IE "H-RNTI" is not included and the primary CCPCH has changed:

4> clear the variable H_RNTI.

3> determine the value for the HS-DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

2> for TDD:

3> if the IE "New Primary E-RNTI" is not included:

4> clear the variable E_RNTI.

3> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

2> for each optional IE part of the IE "Downlink information for each radio link" that is not present:

3> do not change its current downlink physical channel configuration corresponding to the IE, which is absent, if not stated otherwise elsewhere.

NOTE: The Release ’99 RADIO BEARER RECONFIGURATION message always includes at least one IE "Downlink information for each radio link" containing the mandatory IEs, even if UTRAN does not require the reconfiguration of any radio link.

1> if the UE would enter either the CELL_FACH, CELL_PCH or URA_PCH state according to subclause 8.6.3.3 applied on the received message:

2> if IEs other than the IE "Primary CPICH info" (for FDD) or the IE "Primary CCPCH info" (for TDD) are included in the IE "Downlink information for each radio link":

3> ignore these IEs.

2> act on the other IEs contained in the IE "Downlink information for each radio link" as specified in subclause 8.6 applied on this radio link.

2> for 1.28Mcps TDD:

3> if the IE "E-AGCH Info" is included:

4> store the newly received E-AGCH configuration.

3> if the IE "E-HICH information" is included:

4> store the E-HICH configuration.

3> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46.

8.6.6.4a Downlink information for each radio link on secondary UL frequency (FDD only)

For each of the IE "Downlink information for each radio link on secondary UL frequency" included in a received message, the UE shall:

1> if the UE would enter CELL_DCH state according to subclause 8.6.3.3 applied on the received message:

2> if the IE "Secondary serving E-DCH radio link indicator" is present:

3> consider the radio link, identified by the IE "Primary CPICH info" as the secondary serving E-DCH radio link, and no longer consider any other radio link as secondary serving E-DCH radio link.

2> else:

3> consider the radio link, identified by the IE "Primary CPICH info" in the first IE "Downlink secondary cell info FDD" as the secondary serving E-DCH radio link, and no longer consider any other radio link as secondary serving E-DCH radio link.

2> if the IE "E-AGCH Info" is included for the secondary serving E-DCH radio link:

3> store the newly received E-AGCH configuration.

NOTE: The UTRAN should always include the IE "E-AGCH info" if the secondary serving E-DCH radio link indicated in the message is another radio link than the secondary serving E-DCH radio link prior to the procedure.

2> if the IE "E-HICH information" is included:

3> store the E-HICH configuration for the concerning radio link.

2> if the IE "E-RGCH information" is included:

3> store the E-RGCH configuration for the concerning radio link.

2> if the IE "Radio Links without DPCH/F-DPCH indicator" is present:

3> store the IE "F-DPCH frame offset" and ignore all other IEs received in "Downlink F-DPCH info for each RL on secondary UL frequency";

3> indicate to lower layers to start operation with Radio Links without DPCH/F-DPCH.

2> if the IE "Power Control Algorithm 3" is included in the IE "Downlink F-DPCH info for each RL on secondary UL frequency":

3> if the variable DTX_DRX_STATUS is set to TRUE:

4> set the variable INVALID_CONFIGURATION to TRUE.

3> else:

4> indicate to lower layer to perform Power Control Algorithm 3 on the radio link indicated in this IE, as specified in [29].

2> act on the other IEs contained in the IE "Downlink information for each radio link on secondary UL frequency" as specified in subclause 8.6 applied on this radio link, according to the rules for primary uplink frequency.

1> in addition, if the message was received in CELL_DCH state and the UE remains in CELL_DCH state according to subclause 8.6.3.3 applied on the received message and the secondary E-DCH active set prior to reception of this message contains one or more radio links:

2> if the IE "E-RGCH release indicator" is present:

3> delete the stored E-RGCH configuration for this RL.

2> for each optional IE part of the IE "Downlink information for each radio link on secondary UL frequency", except the IE "Radio Links without DPCH/F-DPCH indicator", that is not present:

3> do not change its current downlink physical channel configuration corresponding to the IE, which is absent, if not stated otherwise elsewhere.

NOTE: UTRAN should configure the same value of IE "F-DPCH frame offset" for the serving E-DCH radio link and the secondary serving E-DCH radio link, otherwise the UE behaviour is unspecified.

8.6.6.5 Void

8.6.6.6 Uplink DPCH info

If the IE "Uplink DPCH info" is included, the UE shall:

For FDD:

1> release any active uplink physical channels and activate the given physical channels;

1> if the IE "Number of FBI bits" is not included:

2> use 0 FBI bits in the Uplink DPCH.

1> if the IE "Number of TPC bits" is not included:

2> use 2 TPC bits in the Uplink DPCH.

1> else:

2> if F-DPCH is not configured then the UE behaviour is unspecified.

1> use an SF equal to or greater than the minimum SF indicated in the IE "Spreading Factor" during uncompressed frames or compressed frames by HL scheduling;

1> use an SF equal to or greater than the minimum SF divided by 2 during compressed frames by SF reduction.

For TDD:

1> release the uplink physical channels associated with any CCTrCH that is removed or reconfigured and activate the physical channels assigned to any CCTrCH that is added or reconfigured;

1> for 3.84 Mcps TDD or 7.68 Mcps TDD use the IE "UL target SIR" specified for each added or reconfigured CCTrCH as described in subclause 8.5.7. For 1.28 Mcps TDD use the value of IE “UL target SIR” specified for each added or reconfigured CCTrCH for parameter PRX_DPCHdes as described in subclause 8.5.7;

1> for 1.28 Mcps TDD:

2> if "PLCCH Info" is included then store PLCCH Info parameters with respect to this uplink DPCH (overwriting parameter values previously stored);

2> if "PLCCH Info" is not included then delete the PLCCH Info stored with respect to this uplink DPCH.

1> use the parameters of the IE "Time info" for each added or reconfigured CCTrCH;

1> if present, use the IE "Uplink Timing Advance Control" as specified in subclause 8.6.6.26.

8.6.6.7 Void

8.6.6.8 Maximum allowed UL TX power

If the IE "Maximum allowed UL TX power" is included in the Handover to UTRAN Command, in any other dedicated message or in System Information Block type 3 or in System Information Block 4, the UE shall:

1> store and use the value until it is updated.

If the IE "Maximum allowed UL TX power" was not included in any dedicated message, the UE shall:

1> use the value previously stored, when received in an earlier dedicated message, Handover to UTRAN Command message or received in System Information Block type 3 or in System Information Block 4.

For all cases, the UE shall:

1> keep the UE uplink transmit power at or below the indicated power value;

1> if the current UE uplink transmit power is above the indicated power value:

2> decrease the power to a level at or below the power value.

The maximum UE TX power is defined as the lower of the maximum output power of the UE power class and the maximum allowed UL TX power indicated in this IE. The maximum UE TX power shall not be exceeded.

8.6.6.9 Void

8.6.6.10 Void

8.6.6.11 Uplink DPCH power control info

The UE shall:

1> in FDD:

2> if the IE "Uplink DPCH power control info" is included:

3> if a synchronisation procedure A in CELL_DCH is performed according to [29]; or

3> if a synchronisation procedure AA for Enhanced Uplink in CELL_FACH state or Idle mode is performed according to [29]:

4> calculate and set an initial uplink transmission power;

4> start inner loop power control as specified in subclause 8.5.3;

4> for the UL inner loop power control:

5> use the parameters specified in the IE.

3> else:

4> ignore the IEs "DPCCH Power offset", "PC Preamble" and "SRB delay";

4> act on the IE "Power control algorithm" and the IE "TPC step size", if included.

3> act on the IEs "_ACK", "_NACK" and "Ack-Nack repetition factor", if included;

3> if the IE "Ack-Nack repetition factor for Multiflow assisting cells" is included:

4> if Multiflow operation on two frequencies and three cells with MIMO or Multiflow operation on two frequencies and four cells (with or without MIMO) is configured:

5> act on the IE "Ack-Nack repetition factor for Multiflow assisting cells" for configured multiflow assisting cell(s).

4> else:

5> if the value in the IE "Ack-Nack repetition factor for Multiflow assisting cells" is not set to 1:

6> the UE behavior is unspecified.

5> else:

6> act on the IE "Ack-Nack repetition factor for Multiflow assisting cells" for configured multiflow assisting cell(s).

3> else:

4> act on the IE "Ack-Nack repetition factor" for configured Multiflow assisting cell(s).

3> use the procedure for transmitting HS-DPCCH preamble and postamble according to [29], if the IE "HARQ_preamble_mode" is set to 1.

1> in 3.84 Mcps TDD or 7.68 Mcps TDD:

2> if the IE "Uplink DPCH power control info" is included:

3> use the parameters specified in the IE for open loop power control as defined in subclause 8.5.7.

2> else:

3> use the current uplink transmission power.

1> in 1.28 Mcps TDD:

2> if the CHOICE UL OL PC info is set to ‘Broadcast UL OL PC info’:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> if the IE "Uplink DPCH power control info"is included in the UPLINK PHYSICAL CHANNEL CONTROL message:

3> use "Beacon PL Est. " and the TPC step size for the closed loop power control of the CCTrCH identified in the message, replacing the existing value used for the CCTrCH.

3> if the IE " UL target SIR " is included:

4> use this value for parameter PRX_DPCHdes for open loop power control of the CCTrCH identified in the message in the case of a transition from closed loop to open loop power control as specified in [33].

2> if the IE "Uplink DPCH power control info" is included in the IE "Uplink DPCH info":

3> use the "Beacon PL Est. " and TPC step size for the closed loop power control of all CCTrCH added or reconfigured by the IE replacing any existing values used for the CCTrCHs;

3> if the IE " UL target SIR " is included ignore the parameter.

1> both in FDD and TDD;

2> if the IE "Uplink DPCH power control info" is not included in a message used to enter CELL_DCH:

3> set the variable INVALID_CONFIGURATION to TRUE.

1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

8.6.6.12 Secondary CPICH info

If the IE Secondary CPICH info is included, the UE may:

1> use the channelisation code according to IE "channelisation code", with scrambling code according to IE "DL scrambling code" in the IE "Secondary CPICH info", for channel estimation of that radio link;

1> use the pilot bits on DPCCH for channel estimation.

If the IE Secondary CPICH info is not included, the UE shall:

1> not use any previously stored configuration corresponding to the usage of the Secondary CPICH info.

8.6.6.13 Primary CPICH usage for channel estimation

If the IE "Primary CPICH usage for channel estimation" is included and has the value "Primary CPICH may be used" the UE:

1> may use the Primary CPICH for channel estimation;

1> may use the pilot bits on DPCCH for channel estimation.

NOTE: If the IE "Primary CPICH usage for channel estimation" has the value "Primary CPICH shall not be used" and the IE "Secondary CPICH info" is not included for that radio link then the UE behaviour is not specified.

If the IE "Primary CPICH usage for channel estimation" is included and has the value "Primary CPICH shall not be used" the UE:

1> shall not use the Primary CPICH for channel estimation;

1> may use the Secondary CPICH for channel estimation;

1> may use the pilot bits on DPCCH for channel estimation.

8.6.6.14 DPCH frame offset (FDD Only)

If "DPCH frame offset" is included in a message that instructs the UE to enter CELL_DCH state:

1> UTRAN should:

2> if only one Radio Link is included in the message:

3> if the UE is configured for DPCH:

4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting the following relation:

(Default DPCH Offset Value) mod 38400 = DPCH frame offset

– where the IE values used are the Actual Values of the IEs as defined in clause 11.

3> if the UE is configured for F-DPCH:

4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting one of the following relations:

5> (Default DPCH Offset Value) mod 38400 = DPCH frame offset; or

5> (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset,

– where the IE values used are the Actual Values of the IEs as defined in clause 11.

2> if more than one Radio Link are included in the message:

3> if the UE is configured for DPCH:

4> set "Default DPCH Offset Value" and "DPCH frame offset" respecting the following relation:

(Default DPCH Offset Value) mod 38400 = DPCH frame offset_j

– where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.

3> if the UE is configured for F-DPCH:

4> set "Default DPCH Offset Value" and "DPCH frame offset_j" respecting one of the following relations:

5> (Default DPCH Offset Value) mod 38400 = DPCH frame offset_j; or

5> (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset_j,

– where j indicates the first radio link listed in the message and the IE values used are the Actual Values of the IEs as defined in clause 11.

1> The UE shall:

2> if only one Radio Link is included in the message:

3> if the UE is configured for DPCH:

4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value.

4> else:

5> set the variable INVALID_CONFIGURATION to TRUE.

3> if the UE is configured for F-DPCH:

4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value.

4> else if (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value + 256.

4> else:

5> set the variable INVALID_CONFIGURATION to TRUE.

2> if more than one Radio Links are included in the message:

3> if the UE is configured for DPCH:

4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset_j,

– where j indicates the first radio link listed in the message:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value.

4> else:

5> set the variable INVALID_CONFIGURATION to TRUE.

3> if the UE is configured for F-DPCH:

4> if (Default DPCH Offset Value) mod 38400 = DPCH frame offset_j,,

– where j indicates the first radio link listed in the message:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value.

4> else if (Default DPCH Offset Value+256) mod 38400 = DPCH frame offset_j,

– where j indicates the first radio link listed in the message:

5> set DOFF (see subclause 8.5.15.1) to Default DPCH Offset Value + 256.

4> else:

5> set the variable INVALID_CONFIGURATION to TRUE.

If the IE "DPCH frame offset" is included the UE shall:

1> use its value to determine the beginning of the DPCH or F-DPCH frame.

8.6.6.15 DPCH Compressed mode info

If the IE "DPCH compressed mode info" is included, and if the IE group "transmission gap pattern sequence configuration parameters" is included, the UE shall for each transmission gap pattern sequence perform the following consistency checks:

1> if the UE, according to its measurement capabilities, and for all supported bands of the UTRA mode or RAT associated with the measurement purpose indicated by IE "TGMP", requires UL compressed mode, and CHOICE ‘UL/DL mode’ indicates ‘DL only’:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the UE, according to its measurement capabilities, and for all supported bands of the UTRA mode or RAT associated with the measurement purpose indicated by IE "TGMP", requires DL compressed mode, and CHOICE ‘UL/DL mode’ indicates ‘UL only’:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the UE, according to its measurement capabilities, does not require UL compressed mode for any of supported band of the UTRA mode or RAT associated with the measurement purpose indicated by the IE "TGMP", and CHOICE ‘UL/DL mode’ indicates ‘UL only’ or ‘UL and DL’:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the UE, according to its measurement capabilities, does not require DL compressed mode for any supported band of the UTRA mode or RAT associated with the measurement purpose indicated by the IE "TGMP", and CHOICE ‘UL/DL mode’ indicates ‘DL only’ or ‘UL and DL’:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if UE already has an active transmission gap pattern sequence that, according to IE "TGMP", has the same measurement purpose, and both patterns will be active (according to the IE "Current TGPS Status Flag" in variable TGPS_IDENTITY) after the new configuration has been taken into use:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if there is any pending "TGPS reconfiguration CFN" or any pending "TGCFN":

2> the UE behaviour is unspecified.

If variable INVALID_CONFIGURATION has value FALSE after UE has performed the checks above, the UE shall:

1> if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag") in the variable TGPS_IDENTITY):

2> if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence:

3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use.

3> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "inactive" at the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use.

2> if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence:

3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use.

NOTE1: The temporary deactivation of pattern sequences for which the status flag is set to "activate" can be used by the network to align the timing of already active patterns with newly activated patterns.

NOTE2: The deactivation of pattern sequences only occurs as a result of RRC messages received by the UE, i.e. the UE does not set the "Current TGPS Status Flag" to "inactive" after the final gap of a finite length pattern sequence.

1> update each pattern sequence to the variable TGPS_IDENTITY according to the IE "TGPSI";

1> update into the variable TGPS_IDENTITY the configuration information defined by IE group" transmission gap pattern sequence configuration parameters ";

1> if an F-DPCH is configured:

2> not use the IEs "Downlink compressed mode method", "Downlink frame type", "DeltaSIR1", "DeltaSIRafter1", and if included, the IEs "DeltaSIR2", "DeltaSIRafter2".

1> after the instant in which the message is to be executed, as specified in subclause 8.6.3.1:

2> activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" in the variable TGPS_IDENTITY is set to "activate" at the time indicated by IE "TGCFN"; and

2> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "active".

NOTE1: If the pattern is activated with a message that includes the IE "Activation time", and if the CFN value indicated by the IE "Activation Time" and the CFN value indicated by the TGCFN are included in the same TTI (but not at the TTI boundary) common to all the transport channels that are multiplexed onto the reference CCTrCh (as defined in subclause 8.6.3.1), and if the CFN value indicated by the TGCFN is equal or higher than the CFN value indicated by the IE "Activation Time" (as defined in subclause 8.6.3.1) value, the UE behaviour is not specified.

NOTE2: If the pattern is activated with a message used to perform timing re-initialised hard handover, the UE can start evaluating the activation of the pattern (i.e. compare the value of the CFN in the new configuration with the value of the TGCFN) at any time between the message activation time and the completion of the synchronisation procedure A.

2> if the IE "DPCH compressed mode info" is included in a message used to perform a Hard Handover with change of frequency (see subclause 8.3.5); or

2> if the IE "DPCH compressed mode info" is included in a message used to transfer the UE from CELL_FACH to CELL_DCH, and the cell in which the UE transited from CELL_FACH state is not included in the active set for the CELL_DCH state (see subclause 8.4.1.7.2):

3> not begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence.

2> else:

3> begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence.

2> begin the inter-RAT measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence;

2> if the new configuration is taken into use at the same CFN as indicated by IE "TGCFN":

3> start the concerned pattern sequence immediately at that CFN.

1> monitor if the parallel transmission gap pattern sequences create an illegal overlap, and in case of overlap, take actions as specified in subclause 8.2.11.2.

If the IE "DPCH compressed mode info" is included, and if the IE group "transmission gap pattern sequence configuration parameters" is not included, the UE shall:

1> if, as the result of this message, UE will have more than one transmission gap pattern sequence with the same measurement purpose active (according to IEs "TGMP" and "Current TGPS Status Flag" in variable TGPS_IDENTITY):

2> set the variable CONFIGURATION_INCOMPLETE to TRUE.

1> if there is any pending "TGPS reconfiguration CFN" or any pending "TGCFN":

2> the UE behaviour is unspecified.

1> if pattern sequence corresponding to IE "TGPSI" is already active (according to "Current TGPS Status Flag" in the variable TGPS_IDENTITY):

2> if the "TGPS Status Flag" in this message is set to "deactivate" for the corresponding pattern sequence:

3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use;

3> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "inactive" at the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use.

2> if the "TGPS Status Flag" in this message is set to "activate" for the corresponding pattern sequence:

3> deactivate this pattern sequence at the beginning of the frame, indicated by IE "Activation time"(see subclause 8.6.3.1) received in this message, when the new configuration received in this message is taken into use.

1> after the instant in which the message is to be executed, as specified in subclause 8.6.3.1:

2> activate the stored pattern sequence corresponding to each IE "TGPSI" for which the "TGPS status flag" is set to "activate" at the time indicated by IE "TGCFN"; and

2> set the "Current TGPS Status Flag" for this pattern sequence in the variable TGPS_IDENTITY to "active";

2> if the IE "DPCH compressed mode info" is included in a message used to perform a Hard Handover with change of frequency (see subclause 8.3.5); or

3> not begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence.

2> else:

3> begin the inter-frequency measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence.

2> begin the inter-RAT measurement reporting corresponding to the pattern sequence measurement purpose of each activated pattern sequence;

2> if the new configuration is taken into use at the same CFN as indicated by IE "TGCFN":

3> start the concerned pattern sequence immediately at that CFN.

For transmission gap pattern sequences stored in variable TGPS_IDENTITY, but not identified in IE "TGPSI" (either due to the absence of the IE "DPCH compressed mode info" in the received message or due to not receiving the corresponding TGPSI value in the IE "DPCH compressed mode info"), the UE shall:

1> if the received message implies a timing re-initialised hard handover (see subclause 8.3.5.1):

2> deactivate such transmission gap pattern sequences at the beginning of the frame, indicated by IE "Activation time" (see subclause 8.6.3.1) received in this message; and

2> set IE "Current TGPS Status Flag" in corresponding UE variable TGPS_IDENTITY to ‘inactive’.

1> if the received message not implies a timing re-initialised hard handover (see subclause 8.3.5.1):

2> continue such transmission gap pattern sequence according to IE "Current TGPS Status Flag" in the corresponding UE variable TGPS_IDENTITY.

Uplink and downlink compressed mode methods are described in [27]. For UL "higher layer scheduling" compressed mode method and transport format combination selection, see [15].

8.6.6.16 Repetition period, Repetition length, Offset (TDD only)

In case the physical allocations of different channels overlap the following priority rules shall apply for common channels and shall be taken into account by the UE:

1> PICH takes precedence over Primary CCPCH;

1> PICH takes precedence over Secondary CCPCH;

1> MICH takes precedence over Primary CCPCH;

1> MICH takes precedence over Secondary CCPCH;

1> Secondary CCPCH takes precedence over Primary CCPCH.

The frame allocation can be derived by following rules:

If no IE "Offset" is explicitly given, the parameter "Offset" to be used is calculated by the following equation:

Activation time mod Repetition period = Offset.

Frames from CFN CFN_offto CFN_off + Repetition length – 1 belong to the allocation with CFN_off fulfilling the following equation:

CFN_off mod Repetition period = Offset.

Repetition length is always a multiple of the largest TTI within the CCTrCH fulfilling the following equation:

(largest TTI within CCTrCH) * X = Repetition Length

Example of usage:

Figure 8.6.6.16-1: Examples for frame allocations in TDD

8.6.6.16a Repetition period, Repetition length, Offset_sub(1.28 Mcps TDD only)

The subframes, i.e. TTI in 5ms, of non-scheduled E-PUCH allocated can be determined from "Activation Time", "Subframe number", "Resource Duration" and "Resource Periodicity", or of initial SPS E-PUCH and HS-PDSCH or Standalone midamble allocated can be determined from "Activation time","Subframe number", " Repetition period " and " Repetition length" as below:

The parameter "Offset_sub" is defined to denote the offset of assigned E-PUCH or HS-PDSCH physical resource within each Repetition period and numerated in subframe number.

"Offset_sub" to be used is calculated by the following equation:

(Activation time* 2+ Subframe number) mod Repetition period = Offset_sub.

Here, a new term subCFN is defined to represent the Subframe within a specified CFN, and subCFN within a specified CFN is counted as below:

CFN* 2+ Subframe number = subCFN.

SubFrames from subCFN_offto subCFN_off + Repetition length – 1 belong to the allocation with subCFN_off fulfilling the following equation:

subCFN_off mod Repetition period = Offset_sub.

Example of usage:

Figure 8.6.6.16a-1: Examples for subframe allocations in TDD

8.6.6.17 Primary CCPCH info

If the IE "Primary CCPCH info" is included, the UE shall:

1> use the information elements in this IE.

8.6.6.18 Primary CPICH info

If the IE "Primary CPICH info" in FDD is included, the UE shall:

1> use the value of this IE as the primary scrambling code for the downlink radio link.

8.6.6.19 Void

8.6.6.20 Void

8.6.6.21 Void

8.6.6.22 Secondary Scrambling Code, Code Number

The following description applies to FDD.

Code Number can be assigned by following rules:

1> When more than one DL DPDCH is assigned per RL, the segmented physical channel shall be mapped on to DL DPDCHs according to [27]. When p number of DL DPDCHs are assigned to each RL, the first pair of Secondary Scrambling Code and Code Number corresponds to "PhCH number 1", the second to "PhCH number 2", and so on until the pth to "PhCH number p".

8.6.6.23 PDSCH Power Control info

The UE shall:

1> if the IE "PDSCH Power Control info" is included:

2> configure PDSCH power control with the received values.

1> if the IE "PDSCH Power Control info" is not included:

2> continue to use the stored values.

8.6.6.24 Tx Diversity Mode

If the IE "Tx Diversity Mode" is included the UE shall:

1> if the value of the IE "Tx Diversity Mode" is STTD:

2> configure the Layer 1 to use the Tx diversity mode indicated in the IE "Tx Diversity Mode" for the radio links for which the IE "Closed loop timing adjustment mode" is included, ignoring the actual value of IE "Closed loop timing adjustment mode".

1> if the value of the IE "Tx Diversity Mode" is closed loop mode 1:

2> configure the Layer 1 to use the Tx diversity mode indicated in the IE "Tx Diversity Mode" for the radio links for which the IE "Closed loop timing adjustment mode" is included, using the actual value of the IE "Closed loop timing adjustment mode".

1> if the value of the IE "Tx Diversity Mode" is "none":

2> configure the Layer 1 not to use Tx diversity for all radio links in the active set.

If the IE "Tx Diversity Mode" is not included, the UE shall:

1> continue to use the already configured Tx diversity mode;

1> in case no Tx diversity mode has been configured:

2> do not apply Tx diversity.

For F-DPCH the UE shall:

1> if the IE "STTD indication" is included in the IE "Downlink F-DPCH info for each RL":

2> use STTD for F-DPCH on the radio links for which the IE "STTD indication" is set to TRUE.

For HS-SCCH, the UE shall:

1> if the DPCH associated with a HS-SCCH is using either open or closed loop transmit diversity on the radio link transmitted from the HS-DSCH serving cell:

2> use STTD for this HS-SCCH;

1> if the F-DPCH associated with an HS-SCCH is using open loop transmit diversity on the radio link transmitted from the HS-DSCH serving cell:

2> use STTD for this HS-SCCH.

1> otherwise:

2> not use Tx diversity for this HS-SCCH.

For E-AGCH, E-RGCH, and E-HICH from the same cell, the UE shall:

1> for each radio link:

2> if the DPCH associated with E-AGCH, E-RGCH, and E-HICH from the same cell is using either open or closed loop transmit diversity:

3> use STTD for these E-AGCH, E-RGCH, and E-HICH.

2> if the F-DPCH associated with E-AGCH, E-RGCH, and E-HICH from the same cell is using open loop transmit diversity:

3> use STTD for these E-AGCH, E-RGCH, and E-HICH.

2> otherwise:

3> not use Tx diversity for these E-AGCH, E-RGCH, and E-HICH.

For F-TPICH, the UE shall:

1> for each radio link:

2> if the DPCH associated with the F-TPICH is using either open or closed loop transmit diversity:

3> use STTD for the F-TPICH.

2> if the F-DPCH associated with the F-TPICH is using open loop transmit diversity:

3> use STTD for the F-TPICH.

2> otherwise:

3> not use Tx diversity for the F-TPICH.

NOTE: The IE "Tx Diversity Mode" shall be ignored with respect to the radio links that are in the secondary E-DCH active set.

8.6.6.25 Void

8.6.6.26 UL Timing Advance Control (TDD only)

If the IE "UL Timing Advance Control" is present, the UE shall:

1> if the IE "Uplink Timing Advance Control" has the value "disabled":

2> reset timing advance to 0;

2> disable calculated timing advance following handover;

2> in case of handover:

3> start uplink transmissions in the target cell without applying timing advance.

1> if the IE "Uplink Timing Advance Control" has the value "enabled":

2> in 3.84 Mcps TDD or 7.68 Mcps TDD:

3> in case of no cell change:

4> evaluate and apply the timing advance value for uplink transmission as indicated in the IE "Uplink Timing Advance" or the IE "Extended Uplink Timing Advance" at the CFN indicated in the IE "Activation Time".

3> in case of cell change:

4> use the IE "Uplink Timing Advance" or the IE "Extended UL Timing Advance" as TA_oldand apply TA_new for uplink transmission in the target cell at the CFN indicated in the IE "Activation Time" as specified in [33];

4> include the value of the applied timing advance in the IE "Timing Advance" or the IE "Extended UL Timing Advance" in the COMPLETE message.

2> in 1.28 Mcps TDD:

3> if the IE "Synchronisation parameters" is included:

4> initiate a sequence of UpPCH SYNC_UL code transmissions using a code selected from the set specified and continue until a timing correction is received in the specified FPACH (received for WT sub-frames following the sub-frame in which the transmission was made) or until Max SYNC_UL transmissions have been completed. The power used for each SYNC_UL transmission is as specified in subclause 8.5.7. Each transmission is made in the first sub-frame possible following the end of each FPACH reception interval using the timing specified in [33]. A new code is selected for each transmission. The detection that the FPACH relates to the transmitted SYNC_UL code is described in [33];

4> if a timing correction is received within Max SYNC_UL transmissions the procedure is completed. The assigned uplink resources may then be used, commencing at the first possible TTI boundary or the SFN in which the assignment commences, whichever is the later. The timing of the uplink transmission is described in [33];

4> if no timing correction has been received within Max SYNC_UL transmissions, the synchronisation procedure has failed. If the assigned resources are DCH, the UE should not transmit using these resources and should respond as if a physical channel failure has occurred as specified in subclauses 8.1.3.7 or 8.2.2.7 or 8.3.1.7, or 8.3.6.5. If the assigned resources are USCH then the UE should ignore the USCH allocation.

3> if the IE "Synchronisation parameters" is not included:

4> in case of no cell change:

5> continue to use the current uplink timing.

4> in case of cell change:

5> evaluate and apply the timing correction TA_new for uplink transmissions using the procedure as specified in [33].

8.6.6.26a Uplink synchronisation parameters (TDD only)

The UE shall apply uplink synchronisation using the values of the IEs "Uplink synchronisation step size" and "Uplink synchronisation frequency" as specified in [33].

8.6.6.27 Downlink information common for all radio links

If the IE "Downlink information common for all radio links " is included the UE shall:

1> if the IE "Downlink DPCH info common for all RL" is included:

2> perform actions as specified in subclause 8.6.6.28.

1> if the IE "Downlink F-DPCH info common for all RL" is included:

2> perform actions as specified in subclause 8.6.6.28a.

1> if the IE choice "mode" is set to ‘FDD’:

2> perform actions for the IE "DPCH compressed mode info" as specified in subclause 8.6.6.15;

2> perform actions for the IE "Tx Diversity mode" as specified in subclause 8.6.6.24.

1> if the IE "MAC-hs reset indicator" is included:

2> if the serving HS-DSCH radio link is the same radio link as prior to the reception of the message; and

2> if, as a result of the reconfiguration message where this IE is received, the MAC header type (i.e., either MAC-hs or MAC-ehs) is unchanged; and

2> if, as a result of the reconfiguration message where this IE is received, the UE does not perform a state transition between CELL_FACH state and CELL_DCH state:

3> the UE behaviour is unspecified.

2> if inter-Node B Multiflow operation is not configured:

3> reset the MAC-hs/ehs entity [15].

2> else:

3> reset the MAC-hs/ehs entity related to the serving cell [15].

1> if the IE "MAC-hs reset indicator for Multiflow assisting cells" is included:

2> if inter-Node B Multiflow operation is configured:

3> reset the MAC-hs/ehs entity related to the configured assisting cells [15].

2> else:

3> the UE behaviour is unspecified.

NOTE: If the MAC header type is changed, either from MAC-hs to MAC-ehs or from MAC-ehs to MAC-hs, UTRAN should include the IE "MAC-hs reset indicator" in order to ensure a reset of the MAC-hs/ehs entity in the UE prior to MAC-hs/ehs reconfiguration, otherwise the UE behaviour is unspecified.

8.6.6.28 Downlink DPCH info common for all radio links

If the IE "Downlink DPCH info common for all RL" is included the UE shall:

1> if:

2> the IE "Downlink DPCH info common for all RL" is included in a reconfiguration message; and

2> the UE was in CELL_DCH state upon reception of the message and remains in CELL_DCH state; and

2> the message is not used to perform a hard handover (as specified in subclause 8.6.6.3a) and the IE "Timing indication" is set to "initialise":

3> the UE behaviour is not specified.

1> if the IE "Downlink DPCH power control information" is included:

2> in the case of FDD:

3> perform actions for the IE "DPC Mode" according to [29].

2> in the case of TDD:

3> perform actions for the IE "TPC Step Size" according to [33].

1> if the IE choice "mode" is set to ‘FDD’:

2> if the IE "Downlink rate matching restriction information" is included:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> perform actions for the IE "spreading factor";

2> perform actions for the IE "Fixed or Flexible position";

2> perform actions for the IE "TFCI existence";

2> if the IE choice "SF" is set to 256:

3> store the value of the IE "Number of bits for pilot bits".

2> if the IE choice "SF" is set to 128:

3> store the value of the IE "Number of bits for pilot bits".

If the IE "Downlink DPCH info common for all RL" is included in a message used to perform a Timing re-initialised hard handover or the IE "Downlink DPCH info common for all RL" is included in a message other than RB SETUP used to transfer the UE from a state different from CELL_DCH to CELL_DCH, and ciphering is active for any radio bearer using RLC-TM, the UE shall, after having activated the dedicated physical channels indicated by that IE:

1> if any ciphering configuration for a radio bearer using RLC-TM has not been applied, due to that the activation time from a previous procedure has not elapsed:

2> apply the ciphering configuration immediately and consider the activation time from the previous procedure to be elapsed.

1> if the IE "MAC-d HFN initial value" is included in the IE "Downlink DPCH info common for all RL":

2> set the HFN component of COUNT-C for TM-RLC to the value of the IE "MAC-d HFN initial value", while not incrementing the value of the HFN component of COUNT-C at each CFN cycle.

NOTE: The UTRAN should choose a value for the IE "MAC-d HFN initial value" using the COUNT-C value of the RBs using RLC-TM indicated by the Source RNC to the Target RNC in the IE "SRNS Relocation Info" and include some margin in such a way that no values of COUNT-C are repeated after the handover.

1> else:

2> set the 20 MSB of the HFN component of COUNT-C for TM-RLC to the value of the latest transmitted IE "START" or "START List" for this CN domain, while not incrementing the value of the HFN component of COUNT-C at each CFN cycle; and

2> set the remaining LSBs of the HFN component of COUNT-C to zero.

1> start to perform ciphering on the radio bearer in lower layers while not incrementing the HFN;

1> include the IE "COUNT-C activation time" in the response message and specify a CFN value for this IE other than the default, "Now", that is a multiple of 8 frames (CFN mod 8 =0) and lies at least 200 frames ahead of the CFN in which the response message is first transmitted;

1> calculate the START value according to subclause 8.5.9;

1> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in the response message;

1> at the CFN value as indicated in the response message in the IE "COUNT-C activation time":

2> set the 20 MSB of the HFN component of the COUNT-C variable common for all transparent mode radio bearers of this CN domain to the START value as indicated in the IE "START list" of the response message for the relevant CN domain; and

2> set the remaining LSBs of the HFN component of COUNT-C to zero;

2> increment the HFN component of the COUNT-C variable by one even if the "COUNT-C activation time" is equal to zero;

2> set the CFN component of the COUNT-C to the value of the IE "COUNT-C activation time" of the response message. The HFN component and the CFN component completely initialise the COUNT-C variable;

2> step the COUNT-C variable, as normal, at each CFN value, i.e. the HFN component is no longer fixed in value but incremented at each CFN cycle.

8.6.6.28a Downlink F-DPCH info common for all radio links

If the IE "Downlink F-DPCH info common for all RL" is included the UE shall:

1> if the IE "Downlink F-DPCH info common for all RL" is included in a message used to perform a hard handover:

2> perform actions for the IE "Timing indication" as specified in subclause 8.5.15.2, and subclause 8.3.5.1 or 8.3.5.2.

1> if the IE "Downlink DPCH power control information" is included:

2> perform actions for the IE "DPC Mode" according to [29].

8.6.6.29 ASC setting

If the IE "ASC setting" is included, the UE shall:

1> establish the available signatures for this ASC as specified in the following:

2> separately renumber the list of available signatures specified in the IE "Available signature" included in the IE "PRACH info" and the IE "PRACH preamble control parameters (for Enhanced Uplink)" contained in the IE "Common E-DCH system info" from signature index 0 to signature index N-1, where N is the number of available signatures, starting with the lowest available signature number and continuing in sequence, in the order of increasing signature numbers;

2> for each occurrence in the IE "PRACH preamble control parameters extension list Type 1 (for Enhanced Uplink)", IE "PRACH preamble control parameters extension list Type 2 (for Enhanced Uplink)", and IE "PRACH preamble control parameters extension list Type 3 (for Enhanced Uplink)"

3> separately renumber the list of available signatures specified in the IE "Available signature" included in the IE "PRACH preamble control parameters (for Enhanced Uplink)" from signature index 0 to signature index N-1, where N is the number of available signatures, starting with the lowest available signature number and continuing in sequence, in the order of increasing signature numbers;

2> consider as available signatures for this ASC the signatures included in this renumbered list from the index specified by the IE "Available signature Start Index" to the index specified by the IE "Available signature End Index".

1> establish the available access slot sub-channels for this ASC as specified in the following:

2> if the IE "AICH transmission timing" included in the IE "AICH Info" is set to ‘0’;

3> ignore the leftmost (most significant) bit (bit b3) of the bit string specified by the IE "Assigned Sub-Channel Number";

3> repeat 4 times the 3 rightmost (least significant) bits (bits b2-b0) of the bit string specified by the IE "Assigned Sub-Channel Number" to form a resulting bit string ‘b2 b1 b0 b2 b1 b0 b2 b1 b0 b2 b1 b0’ of length 12 bits, where the leftmost bit is the most significant.

2> if the IE "AICH transmission timing" included in the IE "AICH Info" is set to ‘1’:

3> repeat 3 times the bit string (bits b3-b0) specified by the IE "Assigned Sub-Channel Number" to form a bit string ‘b3 b2 b1 b0 b3 b2 b1 b0 b3 b2 b1 b0’ of length 12 bits, where the leftmost bit is the most significant.

2> perform in both cases, for the resulting bit string (that includes the repetitions) bit-wise logical AND operation separately with the IE "Available Sub Channel number" included in IE "PRACH info (for RACH)" and "PRACH preamble control parameters (for Enhanced Uplink)";

2> consider as available sub-channels for this ASC the available sub-channels indicated in the resulting bit string, after logical AND operation i.e. each bit set to 1 or 0 indicates availability or non-availability, respectively, of sub-channel number x, with x from 0 to 11, for the respective ASC.

NOTE 1: In FDD, the list of available signatures is renumbered from signature index 0 to signature index N-1, where N is the number of available signatures, starting with the lowest available signature number and continuing in sequence, in the order of increasing signature numbers.

– List of available signatures: 16 or fewer signatures are available.
– Example: only signatures 0, 5, 10 and 15 are available, then :
– Signature 0 is: available signature index 0
– Signature 5 is: available signature index 1
– Signature 10 is: available signature index 2
– Signature 15 is: available signature index 3

NOTE 2: In 3.84 Mcps TDD, the list of available channelisation codes (defined in PRACH info) is renumbered from channelisation code index 0 to channelisation code index N-1, where N is the number of available channelisation codes, starting with the lowest available channelisation code number and continuing in sequence, in the order of increasing channelisation code numbers

List of available channelisation codes : 8 or less channelisation codes are available.

The i-th bit of the bitmap defined in the IE "Available Channelisation Code indices" defines whether the channelisation code with the available channelisation code index i is to be used for this ASC (bit set means used, bit unset means not used). Only the low N bits shall be used in the bitmap, where N is the number of available channelisation codes defined in PRACH info.

Ex : spreading factor 16, channelisation codes 16/1, 16/2, 16/5, 16/8 are available :

Channelisation code 16/1 is: available channelisation code index 0
Channelisation code 16/2 is: available channelisation code index 1
Channelisation code 16/5 is: available channelisation code index 2
Channelisation code 16/8 is: available channelisation code index 3

Available Channelisation Code indices has the value ‘00001100’ means: Channelisation Codes 16/5 and 16/8 are available for this ASC.

NOTE 2a: In 7.68 Mcps TDD, the list of available channelisation codes (defined in PRACH info) is renumbered from channelisation code index 0 to channelisation code index N-1, where N is the number of available channelisation codes, starting with the lowest available channelisation code number and continuing in sequence, in the order of increasing channelisation code numbers

List of available channelisation codes : 16 or less channelisation codes are available.

Ex : spreading factor 32, channelisation codes 32/1, 32/2, 32/5, 32/8 are available :

Channelisation code 32/1 is: available channelisation code index 0
Channelisation code 32/2 is: available channelisation code index 1
Channelisation code 32/5 is: available channelisation code index 2
Channelisation code 32/8 is: available channelisation code index 3

Available Channelisation Code indices has the value ‘0000000000001100’ means: Channelisation Codes 32/5 and 32/8 are available for this ASC.

NOTE 3: In TDD, the subchannel description is found in [33].

NOTE 4: In 1.28 Mcps TDD, the list of available SYNC_UL codes (defined in PRACH info) is numbered from SYNC_UL code index 0 to SYNC_UL code index N-1, where N is the number of available SYNC_UL codes, starting with the lowest available SYNC_UL code number and continuing in sequence, in the order of increasing SYNC_UL code numbers

The i-th bit of the bitmap defined in the IE "Available SYNC_UL codes indices" defines whether the SYNC_UL code with the available SYNC_UL code index i is to be used for this ASC (bit set means used, bit unset means not used). Only the low N bits shall be used in the bitmap, where N is the number of available SYNC_UL codes defined in PRACH info.

– List of available SYNC_UL codes: 8 or fewer SYNC_UL codes are available.

Example: only signatures 0, 5, 6 and 7 are available, then:

– SYNC_UL codes 0 is: available SYNC_UL codes index 0
– SYNC_UL codes 5 is: available SYNC_UL codes index 1
– SYNC_UL codes 6 is: available SYNC_UL codes index 2
– SYNC_UL codes 7 is: available SYNC_UL codes index 3

Available SYNC_UL codes indices has the value ‘00001100’ means: SYNC_UL codes 6 and 7 are available for this ASC.

8.6.6.30 SRB delay, PC preamble (FDD only)

When the IE "SRB delay" and IE "PC preamble" is received in a message that results in a configuration of uplink DPCH or E-DPCH, and synchronisation procedure A is being used as specified in [29], the UE shall:

1> store the received IE "SRB delay" and IE "PC preamble" in the variable LATEST_CONFIGURED_SRB_DELAY_AND_PC_PREAMBLE;

1> apply power control preamble according to [26] during the number of frames indicated in the IE "PC preamble"; and

1> then not send any data on signalling radio bearers RB0 to RB4 during the number of frames indicated in the IE "SRB delay" or while the physical channel is not considered established.

8.6.6.31 Void

8.6.6.32 Void

8.6.6.33 HS-SCCH Info

If the IE "HS-SCCH Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the received configuration.

1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall:

1> in the case of FDD:

2> receive the HS-SCCH(s) according to the IE "HS-SCCH channelisation code" on the serving HS-DSCH radio link applying the scrambling code as received in the IE "DL Scrambling code".

1> in the case of TDD:

2> receive the HS-SCCH(s) according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs.

2> transmit the HS-SICH according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs.

2> for HS-SCCH power control the UE shall use the "BLER target" signalled in the first occurrence of the "HS-SCCH Set Configuration", and the UE shall also use the IE "Power Control GAP" for 1.28 Mcps TDD.

2> in 3.84 Mcps TDD and 7.68 Mcps TDD:

3> use the parameters specified in the IE "HS-SICH power control info" for open loop power control as defined in subclause 8.5.7.

2> in 1.28 Mcps TDD:

3> use the IE " PRXHS-SICH " to calculate and set an initial uplink transmission power;

3> use the IE " TPC step size" upon reception of TPC commands for closed loop power control;

3> perform closed loop power control on HS-SICH within the interval indicated in the IE "Power Control GAP";

3> use the IE "Pathloss compensation switch" to determine if the pathloss compensation from the beacon channel estimation should be taken into account for closed loop power control on HS-SICH;

3> use default value of "Uplink synchronisation frequency" and same value of "Uplink synchronisation step size" in "Uplink DPCH info" for HS-SICH upon reception of SS commands for closed loop uplink synchronisation on HS-SICH.

For 1.28 Mcps TDD, if the IE "HS-SCCH Info" is included and the UE will be in CELL_FACH state after completion of this procedure, the UE shall:

1> store the received configuration;

1> determine the value for the HS_DSCH_RECEPTION_CELL_FACH_STATE variable and take the corresponding actions as described in subclause 8.5.36.

For 1.28 Mcps TDD, when the variable HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE the UE shall:

1> receive the HS-SCCH(s) according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs;

1> transmit the HS-SICH according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs;

1> for HS-SCCH power control the UE shall use the "BLER target" signalled in the first occurrence of the "HS-SCCH Set Configuration", and the UE shall also use the IE "Power Control GAP" for 1.28 Mcps TDD;

1> use the IE "PRX_HS-SICH" to calculate and set an initial uplink transmission power;

1> use the value of "TPC step size" in the IE "E-AGCH info" for HS-SCCH closed loop power control;

1> use the IE "TPC step size" upon reception of TPC commands for closed loop power control;

1> perform closed loop power control on HS-SICH within the interval indicated in the IE "Power Control GAP";

1> use the IE "Pathloss compensation switch" to determine if the pathloss compensation from the beacon channel estimation should be taken into account for closed loop power control on HS-SICH;

1> use default value of "Uplink synchronisation frequency" and same value of "Uplink synchronisation step size" in "Uplink DPCH info" for HS-SICH upon reception of SS commands for closed loop uplink synchronisation on HS-SICH.

8.6.6.34 Measurement Feedback Info

If the IE "Measurement Feedback Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the received configuration;

1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

1> if the IE "CQI repetition factor for Multiflow assisting cells" is included:

2> if Multiflow operation on single frequency and two cells without MIMO is configured:

3> if the value in the IE "CQI repetition factor for Multiflow assisting cells" is the same as the value in the IE "CQI repetition factor":

4> act on the IE "CQI repetition factor for Multiflow assisting cells" for configured multiflow assisting cell(s).

3> else:

4> the UE behavior is unspecified.

2> else:

3> act on the IE "CQI repetition factor for Multiflow assisting cells" for configured multiflow assisting cell(s).

1> else:

2> act on the IE "CQI repetition factor" for configured multiflow assisting cell(s).

When the variable HS_DSCH_RECEPTION is set to TRUE the UE shall:

1> use the information for the channel quality indication (CQI) procedure in the physical layer on the serving HS-DSCH radio link.

8.6.6.35 DPC Mode

If the IE "DPC Mode" is included, the UE shall:

1> apply the indicated DPC mode according to [29].

If the IE "DPC Mode" is not included, the UE shall:

1> continue with the currently used DPC mode.

8.6.6.36 Downlink HS-PDSCH Information

If the IE "Downlink HS-PDSCH Information" is included and the UE would be in CELL_DCH state after completion of this procedure, the UE shall:

1> for 1.28 Mcps TDD, if the HS-PDSCH has been configured by the IE "DL Multi-carrier information":

2> clear other stored carriers configuration in the IE "DL Multi-carrier information".

1> if the IE "HS-SCCH Info" is included:

2> act as specified in subclause 8.6.6.33.

1> if the IE "Measurement Feedback Info" is included:

2> act as specified in subclause 8.6.6.34.

1> if the IE "HS-DSCH Timeslot Configuration" or "HS-PDSCH Midamble Configuration" is included:

2> store the received configuration;

2> determine the value for the HS_DSCH_RECEPTION variable and take actions as described in subclause 8.5.25.

For 1.28 Mcps TDD, if the IE "Downlink HS-PDSCH Information" is included and the UE would be in CELL_FACH state after completion of this procedure, the UE shall:

1> if the IE "HS-SCCH Info" is included:

2> act as specified in subclause 8.6.6.33.

1> if the IE "HS-PDSCH Midamble Configuration" is included:

2> store the received configuration.

1> determine the value for the HS_DSCH_RECEPTION_CELL_FACH_STATE variable and take the corresponding actions as described in subclause 8.5.36.

8.6.6.36a DL Multi-carrier information (1.28 Mcps TDD only)

The IE "DL Multi-carrier information" is used in multiple carriers system.

NOTE: When only one frequency is configured to the UE, either the IE "DL Multi-carrier information" or the IE "Downlink HS-PDSCH Information" may be used but should use only one of them and the DPCH frequency shall be aligned with the IE "DL Multi-carrier information".

If the IE "DL Multi-carrier information" is included, the UE shall:

1> if the IE "TSN-Length" is included:

2> store the new TSN length indicated by the IE "TSN-Length".

1> if the IE "TSN-Length" is not included:

2> if the UE has stored TSN length:

3> use the stored content of the IE.

2> else:

3> set the TSN length to 6bits.

1> if the IE "Multi-Carrier number" is included:

2> store the new multiple carriers number indicated by the IE "Multi-Carrier number";

2> start reception procedure on the HS-SCCHs (refer to [33]).

1> if the IE "DL-HSPDSCH-MultiCarrier-Information" is included:

2> if the IE "HS-SCCH Set Configuration" is included:

3> perform processes described in subclause 8.6.6.33.

2> if the IE "HARQ-Info" is included:

3> perform processes described in subclause 8.6.5.6b.

2> if the IE "HS-PDSCH Midamble Configuration" is included:

3> store the HS-PDSCH midamble configureation indicated by the IE "HS-PDSCH Midamble Configuration";

3> perform processes described in subclause 8.5.25.

1> if the carrier which has been stored by the UE is not included in the IE "DL-HSPDSCH-MultiCarrier-Information", the UE should delete all the configurations related to this carrier.

8.6.6.37 E-DCH Info

If the IE "E-DCH Info" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> for FDD:

2> if the IE "E-DPCCH Info" is included:

3> store the newly received E-DPCCH configuration.

2> if the IE "E-DPDCH Info" is included:

3> store the newly received E-DPDCH configuration.

2> if the IE "Uplink MIMO info FDD" is included:

3> store the newly received UL MIMO configuration and perform actions as specified in sub-clause 8.5.81.

2> if the IE "UL 16QAM settings" is not included:

3> indicate to lower layers to stop any operation in 16QAM mode.

2> if the IE "UL 64QAM settings" is not included:

3> indicate to lower layers to stop any operation in 64QAM mode.

2> if both the IE "UL 16QAM settings" and IE "UL 64QAM settings" are included:

3> the UE behaviour is unspecified.

1> for TDD:

2> if the IE "E-RUCCH Info" is included:

3> store the newly received E-RUCCH configuration.

2> if the IE "E-PUCH Info" is included:

3> store the newly received E-PUCH configuration.

NOTE 1: The UTRAN should ensure the ordering of the E-TFCI table in strictly increasing order of transmission power prior to quantization, by correct setting of the reference E-TFCI power offsets otherwise the UE behaviour is unspecified.

NOTE 2: If a reference E-TFCI signalled to the UE is outside the UE physical channel capability, the UE behaviour is unspecified.

NOTE 2a: If E-TFCI boost is signalled to the UE and a reference E-TFCI <= E-TFCI Boost is signalled to the UE with a Reference E-TFCI PO of value 30 or 31, the UE behaviour is unspecified.

NOTE 2b: If the UE is configured with E-TFCI table 0 and 2ms TTI, and a reference E-TFCI =120 has been configured, the UE behavior is unspecified.

NOTE 2c: If the UE is configured with E-TFCI table 1 and 2ms TTI, and a reference E-TFCI =115 has been configured, the UE behavior is unspecified.

NOTE 2d: If the UE is configured with E-TFCI table 2 and 2ms TTI, and a reference E-TFCI =121 has been configured, the UE behavior is unspecified.

NOTE 2e: If the UE is configured with E-TFCI table 3 and 2ms TTI, and a reference E-TFCI =101 or a reference E-TFCI = 102 has been configured, the UE behavior is unspecified.

1> if the IE "MAC-es/e reset indicator" is included:

2> reset the MAC-es/e or MAC-i/is entity [15].

NOTE 3: If the IE "MAC-es/e reset indicator" is not set to TRUE in case the IE "E-DCH Transmission Time Interval" is reconfigured, the UE behaviour is unspecified.

NOTE 4: If the IE "MAC-es/e reset indicator" is not set to TRUE in case the UL MAC header type is reconfigured from MAC-es/e to MAC-is/i or from MAC-is/i to MAC-e/es, the UE behaviour is unspecified.

NOTE 5: If the IE "MAC-es/e reset indicator" is not included in the IE "E-DCH Info" and 16QAM or 64QAM operation starts or stops, the UE behaviour is unspecified.

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

When the variable E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> for FDD:

2> configure the UL E-DPCCH in accordance with the stored IE "E-DPCCH" configuration;

2> configure the MAC with the stored IE "E-DPDCH" configuration and/or the information contained in IE "Scheduled Transmission configuration".

1> for TDD:

2> configure the E-RUCCH with the stored E-RUCCH configuration;

2> configure the MAC with the stored E-PUCH configuration.

For 1.28 Mcps TDD, If the IE "E-DCH Info" is included and the UE will be in CELL_FACH state after completion of this procedure, the UE shall:

1> if the IE "E-RUCCH Info" is included:

2> store the newly received E-RUCCH configuration.

1> if the IE "E-PUCH Info" is included:

2> store the newly received E-PUCH configuration.

1> if the IE "MAC-es/e reset indicator" is included:

2> reset the MAC-es/e or MAC-i/is entity [15].

1> determine the value for the COMMON_E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.46.

For 1.28 Mcps TDD, when the variable COMMON_E_DCH_TRANSMISSION is set to TRUE the UE shall:

1> configure the E-RUCCH with the stored E-RUCCH configuration;

1> configure the MAC with the stored E-PUCH configuration.

8.6.6.38 DTX-DRX timing information (FDD only)

If the IE "DTX-DRX timing information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "timing" is set to "New timing":

2> use the newly received DTX-DRX timing configuration.

1> if the CHOICE "timing" is set to "Continue", and the message is used to perform a hard handover (as specified in subclause 8.6.6.3a); or

1> if the received message does not include the IE "DTX–DRX information" and this message will perform E-DCH TTI reconfiguration:

2> the UE behaviour is unspecified.

1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34.

8.6.6.39 DTX-DRX information (FDD only)

If the IE "DTX–DRX information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the contents of the IE in the variable DTX_DRX_PARAMS, replacing or clearing any previously stored "DTX Information" or "DRX Information";

1> determine the value for the DTX_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.34;

1> if the value of the IE "UE DTX cycle 2" is not an integer multiple of the value of the IE "UE DTX cycle 1"; or

1> if the value of the IE "UE DTX cycle 2" is not an integer multiple or a divisor of the value of the IE "CQI Feedback cycle, k" divided by 2; or

1> if the value of the IE "UE DPCCH burst 1" is greater than the value of the IE "UE DTX cycle 1"; or

1> if the value of the IE "UE DPCCH burst 2" is greater than the value of the IE "UE DTX cycle 2"; or

1> if the IE "UE DTX long preamble length" is set to 4 or 15 slots and the value of the IE "Inactivity Threshold for UE DTX cycle 2" is less than 4 TTIs (for 10ms E-DCH TTI) or 8 TTIs (for 2ms E-DCH TTI); or

1> if the IE "UE DRX cycle" is not an integer multiple or a divisor of the value of the IE "UE DTX cycle 1"; or

1> if the IE "UE DRX cycle 2" is not an integer multiple or a divisor of the value of the IE "UE DTX cycle 2"; or

1> if the value of the IE "UE DTX cycle 1" is not an integer multiple or a divisor of the value of the IE "MAC DTX cycle"; or

1> if the IE "UE DTX cycle 2 secondary" is present and the value of the IE "UE DTX cycle 2 secondary" is not an integer multiple of the value of the IE "UE DTX cycle 1 secondary"; or

1> if the IE "UE DPCCH burst 1 secondary" is present and the value of the IE "UE DPCCH burst 1 secondary" is greater than the value of the IE "UE DTX cycle 1 secondary"; or

1> if the IE "UE DPCCH burst 2 secondary" is present and the value of the IE "UE DPCCH burst 2 secondary" is greater than the value of the IE "UE DTX cycle 2 secondary"; or

1> if the IE "UE DTX long preamble length secondary" is present and set to 4 or 15 slots and the value of the IE "Inactivity Threshold for UE DTX cycle 2 secondary" is less than 8 TTIs (for 2ms E-DCH TTI); or

1> if the IE "UE DRX cycle" is present and is not an integer multiple or a divisor of the value of the IE "UE DTX cycle 1 secondary"; or

1> if the IE "UE DRX cycle 2" is present and is not an integer multiple or a divisor of the value of the IE "UE DRX cycle 2 secondary"; or

1> if the IE "UE DTX cycle 1 secondary" is present and is not an integer multiple or a divisor of the value of the IE "MAC DTX cycle"; or

1> if the IE "DTX-DRX timing information" is included in this message and if the CHOICE "timing" is set to "continue"; or

1> if the IE "Uplink DPCCH slot format information" is received in an ACTIVE SET UPDATE message and indicates different uplink DPCCH slot format from the one currently configured, and neither the indicated uplink DPCCH slot format nor the currently configured uplink DPCCH slot format are uplink DPCCH slot format 4; or

1> if the IE "E-DCH Transmission Time Interval for secondary UL frequency" is received and the IE "UE DTX cycle 1" or the IE "UE DTX cycle 2", or the IE "MAC DTX cycle" for E-DCH TTI length set to "2ms" is included in this message; or

1> if the IE "DTX Information" is not included in this message:

2> the UE behaviour is unspecified.

NOTE: If the IE "Uplink DPCH info" is included in this message, the UTRAN should ensure that the configuration of the uplink DPCH does not contradict the uplink DPCH configuration indicated in the IE "Uplink DPCCH slot format information".

8.6.6.40 HS-SCCH less information (FDD only)

If the IE "HS-SCCH less information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "HS-SCCH less operation" is set to "New HS-SCCH less operation":

2> store the contents of the IE in the variable HS_SCCH_LESS_PARAMS.

1> determine the value for the HS_SCCH_LESS_STATUS variable and take the corresponding actions as described in subclause 8.5.35.

8.6.6.41 MIMO parameters

If the IE "MIMO parameters" is included, the UE shall:

1> act as specified in clauses 8.5.32 and 8.5.33;

1> If the IE "MIMO operation" is set to "start":

2> If the MIMO_STATUS variable is set to FALSE:

3> the UE behaviour is undefined.

2> otherwise:

3> if the UE supports MIMO only with single stream restriction (FDD only); and

3> if the UE signalled HS-DSCH physical layer category 17 or 18 [35] and 64QAM is configured for downlink, or if the UE signalled other HS-DSCH physical layer category than 17 and 18:

4> indicate to lower layers to start operation in MIMO mode restricted to single stream transmission, using the parameter values stored in the variable MIMO_PARAMS.

3> else:

4> indicate to lower layers to start operation in MIMO mode, using the parameter values stored in the variable MIMO_PARAMS.

1> If the IE "MIMO operation" is set to "continue":

2> If the MIMO_STATUS variable is set to FALSE:

3> the UE behaviour is undefined.

1> for FDD, if the IE "Primary CPICH usage for Channel Estimation" is set to "Primary CPICH shall not be used":

2> the UE behavior is undefined.

1> for FDD, if the IE "Secondary CPICH Info" is included and if the IE "Channelisation code" in MIMO pilot configuration is different from the IE "Channelisation Code" in Secondary CPICH info:

2> the UE behavior is undefined.

1> for FDD, if the IE "Secondary CPICH Info" is included and if the IE "Power Offset for S-CPICH for MIMO" is provided, then pass the offset value received in the IE "Power Offset for S-CPICH for MIMO" to the lower layers.

1> determine the configuration of "TSN field extension" for MAC-ehs entity as specified in subclause 8.5.60.

1> for FDD, when MIMO only with single stream restriction is configured:

2> if MAC-ehs is not configured:

3> the UE behaviour is undefined.

NOTE: This subclause applies to FDD and 1.28 Mcps TDD only.

8.6.6.42 UL 16QAM settings

If the IE "UL 16QAM settings" is included, the UE shall:

1> indicate to lower layers to operate in 16QAM mode, using the parameters contained in the IE.

8.6.6.42b UL 64QAM settings

If the IE "UL 64QAM settings" is included, the UE shall:

1> indicate to lower layers to operate in 64QAM mode, using the parameters contained in the IE;

1> if MAC-i/is not configured:

2> the UE behaviour is unspecified.

8.6.6.43 Multi-frequency Info (1.28 Mcps TDD only)

Upon reception of the IE "Multi-frequency info", the UE shall:

1> If the IE "Second Frequency info" is included:

2> act as specified in section 8.6.6.1.

1> If the IE "FPACH Frequency info" is included:

2> store the FPACH frequency indicated in the IE "FPACH Frequency info".

1> else:

2> use the primary frequency as FPACH frequency.

1> If the IE "UpPCH Position Info" is included:

2> store and use the UpPCH position indicated by the IE "UpPCH Positon Info ". The calculation of the uplink access position is described in [33].

1> else:

2> use the UpPTS as the default UpPCH position.

8.6.6.44 Void

8.6.6.45 Downlink Secondary Cell Info FDD

In the following, any information in the "Downlink Secondary Cell Info FDD" is stored in the first entry of the variable DOWNLINK_SECONDARY_CELL_INFO. Any first (respectively second) IE "Downlink Secondary Cell Info FDD" in the "Additional downlink secondary cell info list FDD" IE, is stored in the second (respectively third) entry of the variable DOWNLINK_SECONDARY_CELL_INFO. Any first (respectively second, third and fourth) IE "Downlink secondary Cell Info FDD" in the "Additional downlink secondary cell info list FDD 2" IE, is stored in the fourth (respectively fifth, sixth and seventh) entry of the variable DOWNLINK_SECONDARY_CELL_INFO.

If the i-th IE "Downlink Secondary Cell Info FDD" is not included and the UE has a stored i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable, the UE shall:

1> clear the stored i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable.

For each included IE "Downlink Secondary Cell Info FDD", if the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the i-th IE "Downlink Secondary Cell Info FDD", replacing any stored i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable.

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has a stored i-th entry in the DOWNLINK_SECONDARY_CELL_INFO:

2> keep the stored i-th entry in the DOWNLINK_SECONDARY_CELL_INFO.

The UE shall:

1> determine the value for the SECONDARY_CELL_HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.51.

1> if the UE supports Multiflow operation:

2> determine the value for the MULTIFLOW_STATUS variable and take the corresponding actions as described in subclause 8.5.71.

For each entry in the variable SECONDARY_CELL_HS_DSCH_RECEPTION which is set to TRUE, the UE shall:

1> if the IE "Different Tx diversity mode configuration from serving HS-DSCH cell" is present in the i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable, and Tx diversity is configured in the serving HS-DSCH cell,

2> not configure Tx diversity for the i-th secondary serving HS-DSCH cell.

1> if the IE "Different Tx diversity mode configuration from serving HS-DSCH cell" is present in the i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable and Tx diversity is not configured in the serving HS-DSCH cell,

2> configure Tx diversity in the i-th secondary serving HS-DSCH cell.

1> if the IE "Different Tx diversity mode configuration from serving HS-DSCH cell" is not present in the i-th entry in the DOWNLINK_SECONDARY_CELL_INFO variable,

2> the Tx diversity mode configured in the i-th secondary serving HS-DSCH cell shall be the same as the Tx diversity mode configured in the serving HS-DSCH cell.

For each of the variables "Adjacent frequency info" and "Inter-band frequency info" that are stored in CELL_INFO_LIST, and for which the "UARFCN downlink (Nd)" is different from the "UARFCN downlink (Nd)" of any stored entry in the DOWNLINK_SECONDARY_CELL_INFO variable:

1> stop all inter-frequency measurement reporting on the cells that belong to the frequency derived from the stored variable. Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.

1> clear the stored variable.

If the variable "Frequency info list for enhanced measurement" is stored in CELL_INFO_LIST, then for each of the variable "Frequency info for enhanced measurement" included in the variable "Frequency info list for enhanced measurement":

1> if the "UARFCN downlink (Nd)" in the variable "Frequency info for enhanced measurement" is different from the "UARFCN downlink (Nd)" of any stored entry in the DOWNLINK_SECONDARY_CELL_INFO variable:

2> stop all inter-frequency measurement reporting on the cells that belong to the frequency derived from the variable "Frequency info for enhanced measurement". Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.

2> clear the variable "Frequency info for enhanced measurement".

8.6.6.46 Control Channel DRX information (1.28 Mcps TDD only)

If the IE "Control Channel DRX information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Control Channel DRX operation" is set to "New Control Channel DRX operation":

2> store the contents of the IE in the variable CONTROL_CHANNEL_DRX_PARAMS, replacing or clearing any previously stored "Control Channel DRX operation";

2> use the newly received Control Channel DRX configuration.

2> if the IE "E-AGCH DRX Information" is not included:

3> not perform E-AGCH discontinuous reception.

1> if the CHOICE "Control Channel DRX operation" is set to "Continue", and the message is used to perform a hard handover (as specified in subclause 8.6.6.3a):

2> the UE behaviour is unspecified.

1> determine the value for the CONTROL_CHANNEL_DRX_STATUS variable and take the corresponding actions as described in subclause 8.5.53.

1> if the IE "E-AGCH DRX Information" is included, and the variable E_DCH_TRANSMISSION is set to FALSE:

2> the UE behaviour is unspecified.

8.6.6.47 SPS information (1.28 Mcps TDD only)

If the IE "SPS information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the IE "E-DCH SPS Information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

2> if the CHOICE "E-DCH SPS operation" is set to "New E-DCH SPS operation":

3> after the UE has received IE "E-HICH Information":

4> if the CHOICE "Configuration Mode" is set to "Implicit":

5> if the IE "EI" is included:

6> consider the E-HICH has the same configuration as that in the IE "E-HICH Info" for 1.28Mcps TDD which has the same value of EI indicated by the IE "EI" in this message.

5> else:

6> use the same configuration as the E-HICH for non-schedule transmission.

4> else:

5> store the E-HICH configuration according to the IEs "Timeslot Number", "Channelisation Code" and midamble configuration IEs.

4> store and use the Signature Sequence indicated by the IE "Signature Sequence Group Index".

3> if the IE "Transmission Pattern List" is included:

4> store the contents of the IE in the variable E_DCH_SPS_PARAMS.

3> if the IE "Initial SPS info for E-DCH" is included:

4> perform E-DCH SPS operation on the semi-persistent E-PUCH resource configured by the IE at the CFN determined by the IE "Activation Time" and the IE "Subframe number".

2> determine the value for the E_DCH_SPS_STATUS variable and take the corresponding actions as described in subclause 8.5.54.

2> if the IE "Initial SPS info for E-DCH" is included, the calculation of assigned initial E-DCH SPS transmission grant is specified in subclause 8.6.6.16a

1> else if the IE "E-DCH SPS Information" is not included, the UE shall:

2> set the variable E_DCH_SPS_STATUS to FALSE;

2> clear the variable E_DCH_SPS_PARAMS;

2> stop all E-DCH SPS related activities.

1> if the IE "HS-DSCH SPS Information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

2> if the CHOICE "HS-DSCH SPS operation" is set to "New HS-DSCH SPS operation":

3> if the IE "Transport Block Size List" or the IE "Reception Pattern List" is included:

4> store the contents of the IE in the variable HS_DSCH_SPS_PARAMS.

3> if the IE "HARQ Info for Semi-Persistent Scheduling" is included:

4> calculate the size of each virtual IR buffer according to following equation:

Size of virtual IR soft buffer = Total buffer for HS-SCCH SPS operation / N_IR

where

– Total buffer for HS-SCCH SPS operation is signalled in the IE "Process Memory size", and the IE is the total size of the virtual IR buffers which could be used in HS-SCCH SPS operation;

– N_IR is the value of the IE "Number of Processes", and the IE is the number of HARQ processes which could be used in HS-SCCH SPS operation.

3> after the UE has received IE "HS-SICH List":

4> if the CHOICE "Configuration Mode" is set to "Implicit":

5> transmit the HS-SICH according to the configuration in the IE "HS-SCCH Configuration" for 1.28Mcps TDD, of which the position listed in the IE "HS-SCCH Set Configurationin" in acsending order is indicated by the IE "HS-SCCH Index" in this message.

4> else:

5> transmit the HS-SICH according to the IEs "Timeslot Number", "Channelisation Code" and Midamble configuration IEs.

3> if the IE "Initial SPS info for HS-DSCH" is included:

4> perform HS-SCCH SPS operation on the semi-persistent HS-PDSCH resource configured by the IE at the CFN determined by the IE "Activation Time" and the IE "Subframe number".

2> determine the value for the HS_DSCH_SPS_STATUS variable and take the corresponding actions as described in subclause 8.5.55.

2> if the IE "Initial SPS info for HS-DSCH" is included, the calculation of assigned initial HS-DSCH SPS transmission grant is specified in subclause 8.6.6.16a

1> else if the IE "HS-DSCH SPS Information" is not included, the UE shall:

2> set the variable HS_DSCH_SPS_STATUS to FALSE;

2> clear the variable HS_DSCH_SPS_PARAMS;

2> stop all HS-DSCH SPS related activities.

8.6.6.48 Secondary cell MIMO parameters

If the IE "Secondary cell MIMO parameters" is included, the UE shall:

1> Determine the value for the corresponding SECONDARY_CELL_MIMO_STATUS variable and take the corresponding actions as described in subclause 8.5.57;

1> determine the configuration of "TSN field extension" for MAC-ehs entity as specified in subclause 8.5.60.

NOTE: This subclause applies to FDD only.

8.6.6.49 Uplink Secondary Cell Info FDD (FDD only)

If the IE "Uplink Secondary Cell Info FDD" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> if the IE "Secondary serving E-DCH cell info" is included in the IE "Uplink Secondary Cell Info FDD":

3> if the IE "Frequency info" included in the IE "Secondary E-DCH info common" is different from the stored frequency info:

4> stop intra-frequency and inter-frequency measurement reporting on the downlink frequency associated with the current secondary uplink frequency. Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.

3> store the IE "Secondary serving E-DCH cell info", replacing any stored IE "Secondary serving E-DCH cell info".

2> if the IE "Secondary E-DCH info common" is included in the IE "Uplink Secondary Cell Info FDD":

3> store the IE "Secondary E-DCH info common", replacing any stored IE "Secondary E-DCH info common";

3> if the IE "Additional secondary cell info for mixed TTI configuration" is included in the IE "Secondary E-DCH info common" and the TTIs configured on the primary and secondary uplink frequencies are different:

4> store the IE "Additional secondary cell info for mixed TTI configuration".

2> if the IE "Downlink information per radio link list on secondary UL frequency" is included in the IE "Uplink Secondary Cell Info FDD":

3> act as specified in subclause 8.6.6.3b.

2> determine the value for the IMPLICIT_GRANT variable and take the corresponding actions as described in subclause 8.5.85;

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "Secondary E-DCH info common":

2> keep the stored IE "Secondary serving E-DCH cell info" and IE "Secondary E-DCH info common".

1> if SECONDARY_CELL_E_DCH_TRANSMISSION variable is set to TRUE:

2> if the IE "UARFCN downlink (Nd)" is present in the first IE "Downlink Secondary Cell Info FDD" and is different from the stored "Frequency info" in the IE "Secondary E-DCH info common":

3> UE behaviour is unspecified.

2> if the variable SECONDARY_CELL_E_DCH_TRANSMISSION was previously set to FALSE; or

2> if the IE "Frequency info" included in the IE "Secondary E-DCH info common" is different from the previously stored frequency info:

3> continue inter-frequency measurement reporting on the downlink frequency associated with the new secondary uplink frequency. The UE shall not require compressed mode to perform the measurement, regardless of the activation status of secondary uplink frequency.

If the IE "Uplink Secondary Cell Info FDD" is not included and the UE has any stored IE "Secondary E-DCH info common", the UE shall:

1> clear the stored IE "Secondary serving E-DCH cell info" and IE "Secondary E-DCH info common";

1> stop intra-frequency and inter-frequency measurements reporting on the downlink frequency associated with the current secondary uplink frequency. Each stopped measurement is restarted when a MEASUREMENT CONTROL message is received with the corresponding measurement identity.

8.6.6.50 Additional downlink secondary cell info list FDD

If the IE "Additional downlink secondary cell info list FDD" is included, the UE shall process its parameters as specified in 8.6.6.45.

If the IE "Additional downlink secondary cell info list FDD" is not included, the UE shall clear the second and third entries in the variables DOWNLINK_SECONDARY_CELL_INFO, SECONDARY_CELL_HS_DSCH_RECEPTION, SECONDARY_CELL_MIMO_STATUS and SECONDARY_CELL_MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_STATUS.

8.6.6.51 MU-MIMO info (1.28 Mcps TDD only)

If the IE "MU-MIMO info" is included, the UE shall:

1> act as specified in clauses 8.5.61;

1> if the CHOICE "Configuration MU-MIMO info" has the value "Continue":

2> continue using the stored parameters in the MU_MIMO_INFO variable;

1> otherwise:

2> store and perform MU-MIMO in the direction indicated by IE "MU-MIMO operation";

2> store and use the midamble indicated by IE "Midamble configuration", IE "Midamble shift" and IE "Timeslot information", the calculation of assigned Standalone midamble transmission grant is specified in subclause 8.6.6.16a.

8.6.6.52 Multi-carrier E-DCH Info for LCR TDD (1.28 Mcps TDD only)

The IE "Multi-carrier E-DCH Info for LCR TDD" is used in multiple carriers system.

If the IE "Multi-carrier E-DCH Info for LCR TDD" is included, the UE shall:

1> if a serving cell change will be caused by the received message:

2> clear the stored IE "Multi-carrier E-DCH Info for LCR TDD";

1> if the CHOICE "Configuration info" is set to "New configuration":

2> if the IE "TSN-Length" is included:

3> store and set the TSN length to 14bits.

2> else:

3> store and set the TSN length to 6bits.

2> for each carrier in the IE "UL-Multicarrier-EDCH- Information List":

3> store the value of "UARFCN" in the IE "UARFCN" for the additional E-DCH carrier:

3> store the E-PUCH configuration in the IE "E-PUCH info" for the additional E-DCH carrier;

3> store the E-AGCH configuration in the IE "E-AGCH Info" for the additional E-DCH carrier;

3> store the E-HICH configuration in the IE "E-HICH Info" for the additional E-DCH carrier;

2> for each carrier in the IE "UL-Multicarrier-EDCH-DeleteList":

3> delete the stored additional E-DCH carrier information indicated by the IE "UARFCN" ;

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "Multi-carrier E-DCH Info for LCR TDD":

2> keep the stored IE "Multi-carrier E-DCH Info for LCR TDD".

If the IE "Multi-carrier E-DCH Info for LCR TDD" is not included and the UE has any stored IE "Multi-carrier E-DCH Info for LCR TDD", the UE shall:

1> clear the stored IE "Multi-carrier E-DCH Info for LCR TDD";

8.6.6.53 Serving HS-DSCH cell information

If "Serving HS-DSCH cell information" IE is present, the UE shall:

1> act on received information elements as specified in subclause 8.6:

1> if the IEs "ACK", "NACK", and "HARQ_preamble_mode" are present, act on the received information elements;

2> if the new H-RNTI and "Primary CPICH info" are included:

3> consider the cell indicated in Primary CPICH as serving HS-DSCH cell and no longer consider any other radio link as serving HS-DSCH cell. If any IE "Downlink Secondary Cell Info FDD" is included for a cell associated with a serving HS-DSCH cell, consider that cell a secondary serving HS-DSCH cell on the appropriate frequency.

1> if the IE "MAC-hs reset indicator" is included:

2> if inter-Node B Multiflow operation is not configured:

3> reset the MAC-hs/ehs entity [15].

2> else:

3> reset the MAC-hs/ehs entity related to the serving cell [15].

1> if the IE "MAC-hs reset indicator for Multiflow assisting cells" is included:

2> if inter-Node B Multiflow operation is configured:

3> reset the MAC-hs/ehs entity related to the configured assisting cells [15].

2> else:

3> the UE behaviour is unspecified.

1> determine the value for the HS_DSCH_RECEPTION variable and take the corresponding actions as described in subclause 8.5.25.

8.6.6.54 E-DCH reconfiguration information

If the IE "E-DCH reconfiguration information" is included, the UE shall:

1> if the IE "E-DCH RL Info other cells" is present:

2> if the IE "E-HICH Information" is present:

3> store the E-HICH and E-RGCH information (if present), contained therein, for the indicated radio link.

2> if the IE "E-HICH release indicator" is present:

3> delete the stored E-HICH, E-AGCH and E-RGCH (if any) configurations;

3> if variable UPLINK_MIMO_TRANSMISSION is set to TRUE:

4> delete the stored E-HICH configuration for the secondary stream.

2> if the IE "Secondary TB E-HICH release indicator" is present:

3> delete the stored E-HICH configuration for the secondary stream.

2> if the IE "E-RGCH release indicator" is set present:

3> delete the stored E-RGCH configuration for this RL.

1> if the IE "E-DCH RL Info new serving cell" is present:

2> consider the cell indicated in "Primary CPICH info" as serving E-DCH radio link and no longer consider any other radio link as serving E-DCH radio link;

2> store the E-HICH and E-RGCH information (if present), contained therein, for the new serving E-DCH radio link;

2> if the IE "E-RGCH release indicator" is present:

3> delete the stored E-RGCH configuration for this RL.

2> store the newly received E-AGCH configuration;

2> if the IE "E-ROCH Info" is present:

3> store the newly received E-ROCH configuration;

2> if the IE "Serving Grant" is included, and if the IE "Serving Grant Value" is not included:

3> the UE behaviour is not specified.

1> if the IEs "E-DPCCH/DPCCH power offset" and/or "Reference E-TFCI PO" and/or "Power offset for scheduling info" are present, act on the received information elements.

1> if the serving E-DCH radio link was another radio link than this radio link prior to reception of the message:

2> if the IE "New Primary E-RNTI" is not included:

3> clear the Primary E-RNTI stored in the variable E_RNTI.

2> if the IE "New Secondary E-RNTI" is not included:

3> clear the Secondary E-RNTI stored in the variable E_RNTI.

1> determine the value for the E_DCH_TRANSMISSION variable and take the corresponding actions as described in subclause 8.5.28.

8.6.6.55 Additional downlink secondary cell info list FDD 2

If the IE "Additional downlink secondary cell info list FDD 2" is included, the UE shall process its parameters as specified in 8.6.6.45.

If the IE "Additional downlink secondary cell info list FDD 2" is not included, the UE shall clear the fourth, the fifth, the sixth and the seventh entries in the variables DOWNLINK_SECONDARY_CELL_INFO, SECONDARY_CELL_HS_DSCH_RECEPTION, and SECONDARY_CELL_MIMO_STATUS.

8.6.6.56 Uplink CLTD info FDD

If the IE "Uplink CLTD info FDD" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the IE "Uplink CLTD info FDD", replacing any stored IE "Uplink CLTD info FDD";

2> if the IE "Primary CPICH Info" is present:

3> if variable MULTIFLOW_STATUS is TRUE, but the value of IE "Primary CPICH Info" does not correspond to the assisting serving HS-DSCH cell:

4> the UE behaviour is unspecified.

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "Uplink CLTD info FDD":

2> keep the stored IE "Uplink CLTD info FDD".

If the IE "Uplink CLTD info FDD" is not included and the UE has any stored IE "Uplink CLTD info FDD", the UE shall:

1> clear the stored IE "Uplink CLTD info FDD".

Determine the value for the variable UPLINK_CLTD_TRANSMISSION and take the corresponding actions as described in subclause 8.5.69.

8.6.6.57 Uplink OLTD info FDD

If the IE "Uplink OLTD info FDD" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> store the IE "Uplink OLTD info FDD".

If the IE "Uplink OLTD info FDD" is not included and the UE has any stored IE "Uplink OLTD info FDD", the UE shall:

1> clear the stored IE "Uplink OLTD info FDD".

Determine the value for the variable UPLINK_OLTD_TRANSMISSION and take the corresponding actions as described in subclause 8.5.70.

8.6.6.58 F-TPICH reconfiguration info

If the IE "F-TPICH reconfiguration info" is included, the UE shall:

1> if the IE "F-TPICH info other cells" is present:

2> for each radio link:

3> if the IE "F-TPICH info" is present:

4> store the F-TPICH configuration, contained therein, for the indicated radio link.

3> if the IE "F-TPICH release indicator" is present:

4> delete the stored F-TPICH configuration, for the indicated radio link.

1> if the IE "F-TPICH info new cell that determines the precoding weights" is present:

2> store the F-TPICH configuration, contained therein, for the radio link transmitted from the serving HS-DSCH cell if HS-DSCH is configured or from the cell identified by the IE "Primary CPICH info" in the IE "Uplink CLTD info FDD" if only DCH is configured.

1> determine the value for the variable UPLINK_CLTD_TRANSMISSION and take the corresponding actions as described in subclause 8.5.69.

8.6.6.59 Common E-RGCH info FDD

If the IE "Common E-RGCH info FDD" is included and the UE will be in CELL_FACH or CELL_PCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the IE "Common E-RGCH info FDD", replacing any stored IE "Common E-RGCH info FDD".

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE " Common E-RGCH info FDD":

2> keep the stored IE "Common E-RGCH info FDD".

If the IE "Common E-RGCH info FDD" is not included and the UE has any stored IE "Common E-RGCH info FDD", the UE shall:

1> clear the stored IE "Common E-RGCH info FDD".

Determine the value for the variable READY_FOR_COMMON_ERGCH and take the corresponding actions as described in subclause 8.5.75.

8.6.6.60 MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS parameters (FDD only)

If the IE "MIMO mode with four transmit antennas parameters" is included, the UE shall:

1> act as specified in clauses 8.5.78 and 8.5.79;

1> If the IE "MIMO mode with four transmit antennas parameters " is set to "New configuration":

2> If the MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_STATUS variable is set to FALSE:

3> the UE behaviour is undefined.

2> otherwise:

3> if the UE supports MIMO mode with four transmit antennas only with dual stream restriction:

4> indicate to lower layers to start operation in MIMO mode with four transmit antennas restricted to dual stream transmission, using the parameter values stored in the variable MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_PARAMS.

3> else:

4> indicate to lower layers to start operation in MIMO mode with four transmit antennas, using the parameter values stored in the variable MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_PARAMS.

1> If the IE "MIMO mode with four transmit antennas parameters" is set to "continue":

2> If the MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_STATUS variable is set to FALSE:

3> the UE behaviour is undefined.

1> when MIMO mode with four transmit antennas is configured:

2> if MAC-ehs is not configured:

3> the UE behaviour is undefined.

1> if the IE "Primary CPICH usage for Channel Estimation" is set to "Primary CPICH shall not be used":

2> the UE behavior is undefined.

1> if the IE "Secondary CPICH Info" is included and if the IE "Channelisation code" in MIMO mode with four transmit antennas pilot configuration is different from the IE "Channelisation Code" in Secondary CPICH info:

2> the UE behavior is undefined.

1> if the IE "Secondary CPICH Info" is included and if the IEs "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2", "Common Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4" and "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4" are provided, then pass the offset value received in the IEs "Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna2", "Common Power Offset for S-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4", and "Common Power Offset for D-CPICH for MIMO mode with four transmit antennas on Antenna3 and 4" to the lower layers.

1> determine the configuration of "TSN field extension" for MAC-ehs entity as specified in subclause 8.5.60.

1> when MIMO mode with four transmit antennas only with dual stream restriction is configured:

2> if MAC-ehs is not configured:

3> the UE behaviour is undefined.

8.6.6.61 Secondary cell MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS parameters (FDD only)

If the IE "Secondary cell MIMO mode with four transmit antennas parameters" is included, the UE shall:

1> Determine the value for the corresponding SECONDARY_CELL_MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS_STATUS variable and take the corresponding actions as described in subclause 8.5.80;

1> determine the configuration of "TSN field extension" for MAC-ehs entity as specified in subclause 8.5.60.

8.6.6.62 Uplink MIMO info FDD

If the IE "Uplink MIMO info FDD" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the IE "Uplink MIMO info FDD", replacing any stored IE "Uplink MIMO info FDD".

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "Uplink MIMO info FDD":

2> keep the stored IE "Uplink MIMO info FDD".

If the IE "Uplink MIMO info FDD" is not included and the UE has any stored IE "Uplink MIMO info FDD", the UE shall:

1> clear the stored IE "Uplink MIMO info FDD".

Determine the value for the variable UPLINK_MIMO_TRANSMISSION and take the corresponding actions as described in subclause 8.5.81.

8.6.6.63 DPCCH2 info FDD

If the IE "DPCCH2 info FDD" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the IE "DPCCH2 info FDD", replacing any stored IE "DPCCH2 info FDD";

2> if the IE "TPC command error rate target" is present:

3> store the TPC command error rate target for F-DPCH.

2> if the IE "Extended E-DPCCH/DPCCH power offset" is present:

3> store the Extended E-DPCCH/DPCCH power offset.

2> if the IE "Designated non-serving HS-DSCH cell info" is present:

3> store the Designated non-serving HS-DSCH cell information;

3> if the Serving E-DCH cell decoupling is configured and the Designated non-serving HS-DSCH cell is not the serving E-DCH cell:

4> the UE behaviour is unspecified.

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "DPCCH2 info FDD":

2> keep the stored IE "DPCCH2 info FDD".

If the IE "DPCCH2 info FDD" is not included and the UE has any stored IE "DPCCH2 info FDD", the UE shall:

1> clear the stored IE "DPCCH2 info FDD".

Determine the value for the variable DPCCH2_TRANSMISSION and take the corresponding actions as described in subclause 8.5.83.

8.6.6.64 DCH Enhancements info FDD

If the IE "DCH Enhancements info FDD" is included, the UE shall:

1> if the CHOICE "Configuration info" is set to "New configuration":

2> store the IE "DCH Enhancements info FDD", replacing any stored IE "DCH Enhancements info FDD".

1> if the CHOICE "Configuration info" is set to "Continue" and the UE has any stored IE "DCH Enhancements info FDD":

2> keep the stored IE "DCH Enhancements info FDD".

If the IE "DCH Enhancements info FDD" is not included and the UE has any stored IE "DCH Enhancements info FDD", the UE shall:

1> clear the stored IE "DCH Enhancements info FDD".

8.6.6.65 Other TTI E-DCH Configuration Information

If the IE "Other TTI E-DCH Configuration Information" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the information received would result in a configuration which is considered to be invalid:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> else

2> if the current configured TTI length is 2ms TTI:

3> store the relevant information for the current TTI configuration in the IE "2ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION;

3> store the received preconfiguration information in the IE "10ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION.

2> else:

3> store the relevant information for the current TTI configuration in the IE "10ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION;

3> store the received preconfiguration information in the IE "2ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION.

2> if the IE "Activation delay" is included:

3> store the received value in the variable OTHER_TTI_EDCH_CONFIGURATION.

2> else:

3> set the value of the IE "Activation delay" in the variable OTHER_TTI_EDCH_CONFIGURATION to 0.

8.6.6.66 Other TTI E-DCH Configuration Information on secondary UL Frequency

If the IE "Other TTI E-DCH Configuration Information on secondary UL Frequency" is included and the UE will be in CELL_DCH state after completion of this procedure, the UE shall:

1> if the information received would result in a configuration which is considered to be invalid:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> else:

2> if the current configured TTI length is 2ms TTI on the secondary UL frequency:

3> store the relevant information for the current TTI configuration in the IE "2ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION_ON_SECONDARY_UL_FREQUENCY;

3> store the received preconfiguration information in the IE "10ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION_ON_SECONDARY_UL_FREQUENCY.

2> else:

3> store the relevant information for the current TTI configuration in the IE "10ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION_ON_SECONDARY_UL_FREQUENCY;

3> store the received preconfiguration information in the IE "2ms TTI Configuration Information" in the variable OTHER_TTI_EDCH_CONFIGURATION_ON_SECONDARY_UL_FREQUENCY.

8.6.6.1 Frequency info

8.6.6.2 Void

8.6.6.2a PNBSCH allocation

8.6.6.3 Void

8.6.6.3a Downlink information per radio link list

8.6.6.3b Downlink information per radio link list on secondary UL frequency (FDD only)

8.6.6.4 Downlink information for each radio link

8.6.6.4a Downlink information for each radio link on secondary UL frequency (FDD only)

8.6.6.5 Void

8.6.6.6 Uplink DPCH info

8.6.6.7 Void

8.6.6.8 Maximum allowed UL TX power

8.6.6.9 Void

8.6.6.10 Void

8.6.6.11 Uplink DPCH power control info

8.6.6.12 Secondary CPICH info

8.6.6.13 Primary CPICH usage for channel estimation

8.6.6.14 DPCH frame offset (FDD Only)

8.6.6.15 DPCH Compressed mode info

8.6.6.16 Repetition period, Repetition length, Offset (TDD only)

8.6.6.16a Repetition period, Repetition length, Offsetsub (1.28 Mcps TDD only)

8.6.6.17 Primary CCPCH info

8.6.6.18 Primary CPICH info

8.6.6.19 Void

8.6.6.20 Void

8.6.6.21 Void

8.6.6.22 Secondary Scrambling Code, Code Number

8.6.6.23 PDSCH Power Control info

8.6.6.24 Tx Diversity Mode

8.6.6.25 Void

8.6.6.26 UL Timing Advance Control (TDD only)

8.6.6.26a Uplink synchronisation parameters (TDD only)

8.6.6.27 Downlink information common for all radio links

8.6.6.28 Downlink DPCH info common for all radio links

8.6.6.28a Downlink F-DPCH info common for all radio links

8.6.6.29 ASC setting

8.6.6.30 SRB delay, PC preamble (FDD only)

8.6.6.31 Void

8.6.6.32 Void

8.6.6.33 HS-SCCH Info

8.6.6.34 Measurement Feedback Info

8.6.6.35 DPC Mode

8.6.6.36 Downlink HS-PDSCH Information

8.6.6.36a DL Multi-carrier information (1.28 Mcps TDD only)

8.6.6.37 E-DCH Info

8.6.6.38 DTX-DRX timing information (FDD only)

8.6.6.39 DTX-DRX information (FDD only)

8.6.6.40 HS-SCCH less information (FDD only)

8.6.6.41 MIMO parameters

8.6.6.42 UL 16QAM settings

8.6.6.42b UL 64QAM settings

8.6.6.43 Multi-frequency Info (1.28 Mcps TDD only)

8.6.6.44 Void

8.6.6.45 Downlink Secondary Cell Info FDD

8.6.6.46 Control Channel DRX information (1.28 Mcps TDD only)

8.6.6.47 SPS information (1.28 Mcps TDD only)

8.6.6.48 Secondary cell MIMO parameters

8.6.6.49 Uplink Secondary Cell Info FDD (FDD only)

8.6.6.50 Additional downlink secondary cell info list FDD

8.6.6.51 MU-MIMO info (1.28 Mcps TDD only)

8.6.6.52 Multi-carrier E-DCH Info for LCR TDD (1.28 Mcps TDD only)

8.6.6.53 Serving HS-DSCH cell information

8.6.6.54 E-DCH reconfiguration information

8.6.6.55 Additional downlink secondary cell info list FDD 2

8.6.6.56 Uplink CLTD info FDD

8.6.6.57 Uplink OLTD info FDD

8.6.6.58 F-TPICH reconfiguration info

8.6.6.59 Common E-RGCH info FDD

8.6.6.60 MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS parameters (FDD only)

8.6.6.61 Secondary cell MIMO_MODE_WITH_FOUR_TRANSMIT_ANTENNAS parameters (FDD only)

8.6.6.62 Uplink MIMO info FDD

8.6.6.63 DPCCH2 info FDD

8.6.6.64 DCH Enhancements info FDD

8.6.6.65 Other TTI E-DCH Configuration Information

8.6.6.66 Other TTI E-DCH Configuration Information on secondary UL Frequency

8.6.6.16a Repetition period, Repetition length, Offset_sub(1.28 Mcps TDD only)