8.6.5 Transport channel information elements

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

8.6.5.1 Transport Format Set

If the IE "Transport format set" is included, the UE shall:

1> if the transport format set is a RACH TFS received in System Information Block type 5 or System Information Block type 5bis or System Information Block type 6, and CHOICE "Logical Channel List" has a value different from "Configured":

2> ignore that System Information Block.

NOTE: The TFS added by the IE "Additional Dynamic Transport Format Information for CCCH" has no CHOICE "Logical Channel List" and can thus never be considered as different from "Configured".

1> if the transport format set for a downlink transport channel is received in a System Information Block, and CHOICE "Logical Channel List" has a value different from ‘ALL’:

2> ignore that System Information Block.

1> if the transport format set for a downlink transport channel is received in a message on a DCCH, and CHOICE "Logical Channel List" has a value different from ‘ALL’:

2> keep the transport format set if this exists for that transport channel;

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the value of any IE "RB identity" (and "Logical Channel" for RBs using two UL logical channels) in the IE "Logical channel list" does not correspond to a logical channel indicated to be mapped onto this transport channel in any RB multiplexing option (either included in the same message or previously stored and not changed by this message); or

1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is set to "Configured" while it is set to "All" or given as an "Explicit List" for any other RLC size; or

1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is set to "All" and for any logical channel mapped to this transport channel, the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is not set to "Configured"; or

1> if the "Logical Channel List" for any of the RLC sizes defined for that transport channel is given as an "Explicit List" that contains a logical channel for which the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is not set to "Configured"; or

1> if the "Logical Channel List" for all the RLC sizes defined for that transport channel are given as "Explicit List" and if one of the logical channels mapped onto this transport channel is not included in any of those lists; or

1> if the "Logical Channel List" for the RLC sizes defined for that transport channel is set to "Configured" and for any logical channel mapped onto that transport channel, the value of the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored) is also set to "Configured"; or

1> if the IE "Transport Format Set" was not received within the IE "PRACH system information list" and if the "Logical Channel List" for the RLC sizes defined for that transport channel is set to "Configured" and for any logical channel mapped onto that transport channel, the "RLC size list" (either provided in the IE "RB mapping info" if included in the same message, or stored ) is given as an "Explicit List" that includes an "RLC size index" that does not correspond to any RLC size in this "Transport Format Set"; or

1> if the IE "Transport Format Set" was not received within the IE "PRACH system information list", and if that RB is using AM and the set of RLC sizes applicable to the logical channel transferring data PDUs has more than one element not equal to zero:

2> keep the transport format set if this exists for that transport channel;

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the total number of configured transport formats for the transport channel exceeds maxTF:

2> keep the transport format set if this exists for that transport channel;

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the IE "Transport format set" is considered as valid according to the rules above:

2> remove a previously stored transport format set if this exists for that transport channel;

2> store the transport format set for that transport channel;

2> consider the first instance of the parameter Number of TBs and TTI List within the Dynamic transport format information to correspond to transport format 0 for this transport channel, the second to transport format 1 and so on;

2> if the IE "Transport format Set" has the choice "Transport channel type" set to "Dedicated transport channel":

3> calculate the transport block size for all transport formats in the TFS using the following

TB size = RLC size + MAC header size if "RLC size" <> 0,
TB size = 0 if "RLC size" = 0,

where:

– MAC header size is calculated according to [15] if MAC multiplexing is used. Otherwise it is 0 bits;

– ‘RLC size’ reflects the RLC PDU size.

2> if the IE "Transport format Set" has the choice "Transport channel type" set to "Common transport channel":

3> calculate the transport block size for all transport formats in the TFS using the following:

TB size = RLC size.

2> if the IE "Number of Transport blocks" <> 0 and IE "RLC size" = 0, no RLC PDU data exists but only parity bits exist for that transport format;

2> if the IE "Number of Transport blocks" = 0, neither RLC PDU neither data nor parity bits exist for that transport format;

2> perform the actions as specified in subclause 8.5.21.

For configuration restrictions on Blind Transport Format Detection, see [27].

8.6.5.2 Transport format combination set

If the IE "Transport format combination set" is included for the uplink, the UE shall for that direction:

1> store the new transport format combination set, or (if this exists) modify a previously stored transport format combination set according to IEs included in IE "Transport format combination set";

1> start to respect those transport format combinations;

1> if IE "Transport format combination subset" is received in this message:

2> perform the actions as specified in subclause 8.6.5.3.

1> if IE "Transport format combination subset" is not received in this message:

2> clear the IE "Duration" in the variable TFC_SUBSET;

2> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the value indicating "full transport format combination set".

If the IE "Transport format combination set" is included for the downlink, the UE shall for that direction:

1> store the new transport format combination set, or (if this exists) modify a previously stored transport format combination set according to IEs included in IE "Transport format combination set";

1> start to respect those transport format combinations.

If the IE "Transport format combination set" is not included for the uplink and if there is no addition, removal or reconfiguration of transport channels, the UE shall for that direction:

1> use a previously stored transport format combination set if this exists.

If the IE "Transport format combination set" is not included for the downlink and if there is no addition, removal or reconfiguration of transport channels, the UE shall for that direction:

1> use a previously stored transport format combination set if this exists.

If the IE "Transport format combination set" is not included for either the uplink or the downlink and for that direction after the reconfiguration there is one or more stored DCH configuration; and

1> if no transport format combination set is stored in the UE; or

1> if transport channels are added or removed in the message; or

1> if any transport channel is reconfigured in the message such that the size of the transport format set is changed:

the UE shall:

1> set the variable INVALID_CONFIGURATION to TRUE.

If the IE "Transport format combination set" is not included for either the uplink or the downlink and for that direction after the reconfiguration there is no stored DCH configuration, the UE shall:

1> remove any stored transport format combination set for dedicated channels for that direction.

In the uplink TFCS the minimum set of TFCs is the set of TFCs that is needed for the TFC selection algorithm defined in [15] to give a predictable result. Any configured TFCS or TFC subset shall satisfy the requirements as specified by the minimum set. In the definition of the minimum set of TFCs below, only logical channels for which the TFCS or the TFC subset include at least one TFC with non-empty TF for the corresponding transport channel should be considered.

The minimum set of TFCs consists of the following:

1> for each UM logical channel:

2> a TFC with one transport block for this transport channel and empty TFs (see [34]) for all the others. If more than one TFC fulfils these criteria, only the TFC with the lowest number of bits should be included in the minimum set of TFCs.

1> for each AM logical channel:

2> a TFC with a non-empty TF for the corresponding transport channel and empty TFs for all other transport channels, where the non-empty TF includes one transport block with "Configured RLC Size" equal to the RLC PDU size.

1> for each set of "synchronous" TM logical channels (see the definition below) and for each set of SDU sizes associated with it:

2> a TFC with TFs corresponding to any combination of SDU sizes that can be received in a TTI from higher layers on the corresponding transport channels and empty TFs for all other transport channels.

NOTE: In case an adaptive rate codec is used and the TFCS has been restricted by the IE "TFC subset", the minimum set consists of the set of TFCs with TFs corresponding to any combination of SDU sizes that can be received in a TTI respecting the restricted TFCS.

1> for each TM logical channel that is not part of a set of "synchronous" TM logical channels (see the definition below):

2> a TFC with non-empty TFs for the corresponding transport channel, and empty TFs for all other transport channels, where

3> for non-segmented mode TM-RLC logical channels the non-empty TFs include, for the smallest SDU size that can be received in a single TTI from higher layer:

4> a TF with non-zero number of transport blocks with "Configured RLC Size" equal to the corresponding SDU size. If more than one TFC fulfils these criteria, only the TFC with the lowest number of bits in the TFC is included in the minimum set of TFCs.

3> for segmented mode TM-RLC, the non-empty TFs include any TF such that the number of transport blocks multiplied by the "Configured RLC Size" is equal to the smallest SDU size that can be received in a single TTI from higher layer.

1> an "empty" TFC (see [34]).

Furthermore, the UTRAN should ensure that the uplink TFCS and any configured TFC Subset satisfies the following rules:

1> for each TTI length with which at least one transport channel is configured:

2> for each combination of TFs for the transport channels configured with this TTI length included in the TFCS:

3> a TFC with these TFs for the transport channels configured with this TTI length and empty TFs on all transport channels configured with shorter TTI lengths is also included in the TFCS.

For TDD, the TFCS of a CCTrCH should include those of the above combinations, which include a TF with one transport block for a transport channel used in that CCTrCH, and the "empty" TFC should be included in the TFCS of every CCTrCH.

Synchronous TM logical channels are logical channels on which higher layer traffic is generated in a perfectly correlated fashion (e.g. AMR RAB).

NOTE: The "Configured RLC Size" is defined as the transport block size minus the MAC header size.

8.6.5.3 Transport format combination subset

When configuring a TFC Subset, the UTRAN should follow the guidelines defined in subclause 8.6.5.2.

If a DCH is configured on the uplink and the IE "Transport format combination subset"("TFC subset") is included, the UE shall:

1> if the IE "Minimum allowed Transport format combination index" is included; and

2> if the value of the IE "Minimum allowed Transport format combination index" is greater than the highest TFCI value in the current transport format combination set:

3> consider the TFC subset to be incompatible with the current transport format combination set.

1> if the IE "Allowed transport format combination list" is included; and

2> if the value of any of the IEs "Allowed transport format combination" included in the IE "Allowed transport format combination list" does not match a TFCI value in the current transport format combination set:

3> consider the TFC subset to be incompatible with the current transport format combination set.

1> if the IE "Non-allowed transport format combination list" is included; and

2> if the value of any of the IEs "Non-allowed transport format combination" included in the IE "Non-allowed transport format combination list" does not match a TFCI value in the current transport format combination set:

3> consider the TFC subset to be incompatible with the current transport format combination set.

1> if the IE "Restricted TrCH information" is included:

2> if the value of any of the IEs "Uplink transport channel type" and "Restricted UL TrCH identity" included in the IE "Restricted TrCH information" do not correspond to any of the transport channels for which the current transport format combination set is valid:

3> consider the TFC subset to be incompatible with the current transport format combination set.

2> if the IE "Allowed TFIs" is included; and

3> if the value of each of the IEs "Allowed TFI" included in the IE "Allowed TFIs" corresponds to a transport format for that transport channel within the current transport format combination set:

4> allow all transport format combinations that include these transport formats for the transport channel;

4> restrict all other transport format combinations.

3> else:

4> consider the TFC subset to be incompatible with the current transport format combination set.

2> if the IE "Allowed TFIs" is not included:

3> restrict all transport format combinations where the transport channel has a transport format of non-zero rate.

1> if the UE considers the TFC subset to be incompatible with the current Transport format combination set according to the above:

2> keep any previous restriction of the transport format combination set;

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the UE does not consider the TFC subset to be incompatible with the current Transport format combination set according to the above:

2> if the IE "Transport format combination subset" is received in a message other than a TRANSPORT FORMAT COMBINATION CONTROL message:

3> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the IE "Transport format combination subset" (in case of TDD for the uplink CCTrCH specified by the IE "TFCS Id");

3> clear the IE "Duration" in the variable TFC_SUBSET;

3> apply the transport format combination subset in the IE "Current TFC subset" stored in the variable TFC_SUBSET.

1> if the IE "transport format combination subset" indicates the "full transport format combination set":

2> set both the IE "Current TFC subset" and the IE "Default TFC subset" in the variable TFC_SUBSET to the value indicating "full transport format combination set";

2> clear the IE "Duration" in the variable TFC_SUBSET;

2> if the IE "Transport format combination subset" is received in a TRANSPORT FORMAT COMBINATION CONTROL message, then at the CFN indicated by the IE "Activation time for TFC subset" any restriction on transport format combination set is released and the UE may use the full transport format combination set;

2> else:

3> any restriction on transport format combination set is released and the UE may use the full transport format combination set.

8.6.5.4 DCH quality target

When not operating with DCH Enhancements, if the IE "DCH quality target" is included, the UE shall:

1> set, at physical channel establishment, the initial downlink target SIR value based on the received IE "DCH quality target" for the transport channel with respect to all transport formats;

1> adjust the target SIR for the downlink power control to meet the quality target received in the IE "DCH quality target" for the transport channel. The UE shall not compensate for the fact that the required SIR to achieve a target BLER for a particular transport format may be different from the required SIR to achieve the target BLER for another transport format..

NOTE 1: Adjusting the target SIR is possible to do continuously by the UE if a CRC exists in all transport formats in the downlink TFS for a DCH. If a CRC does not exist in all transport formats, the UE can only adjust the target SIR when receiving transport formats containing a CRC and the UE has knowledge about the transport format according to [27].

NOTE 2: If the UTRAN configures a UE to use blind transport format detection and configures a transport channel such that single transport format detection [27] must be used to detect the TF, then it is not possible for the UE to maintain a quality target for that transport channel.

When operating with DCH Enhancements in DL FET Basic mode, the UE shall:

1> set, at physical channel establishment, the initial downlink target SIR value based on the received IE "DCH quality target" for the transport channel with respect to all transport formats;

1> when the selected uplink TFC is in 10ms Mode, adjust the target SIR for the downlink power control to meet the quality target received in the IE "DCH quality target" for the transport channel at the end of slot number 14 in a TTI;

1> when the selected uplink TFC is in 20ms Mode, adjust the target SIR for the downlink power control to meet the quality target received in the IE "DCH quality target" for the transport channel at the end of slot number 29 in a TTI;

1> reduce the target SIR for the downlink power control by 3dB reduction when switching transmission from 10ms Mode to 20ms Mode;

1> increase the target SIR for the downlink power control by 3dB reduction when switching transmission from 20ms Mode to 10ms Mode.

8.6.5.5 Added or Reconfigured UL TrCH information

If the IE "Added or Reconfigured UL TrCH information" is included then the UE shall:

1> for the transport channel identified by the IE "UL Transport Channel Identity" and IE "Uplink transport channel type":

2> perform the actions for the IE "Transport Format Set" as specified in subclause 8.6.5.1.

NOTE: The UE stores the UL transport channel configuration until it is explicitly deleted by a message containing the IE "Deleted UL TrCH information" or the UE leaves RRC Connected mode.

1> if the choice "UL parameters" is set to ‘E-DCH’:

2> for FDD:

3> if the IE "E-DCH Transmission Time Interval for secondary UL frequency" is not included:

4> apply the values of the IE "E-DCH Transmission Time Interval" and the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows.

3> else:

4> if the IE "E-DCH Transmission Time Interval for secondary UL frequency" has the same value as the IE "E-DCH Transmission Time Interval":

5> the UE behaviour is unspecified.

4> apply the value of the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows, and apply the value of the IE "E-DCH Transmission Time Interval" on the primary UL frequency, and apply the value of the IE " E-DCH Transmission Time Interval for secondary UL frequency" on the secondary UL frequency.

2> for TDD:

3> apply the value of the IE "HARQ info for E-DCH" to all E-DCH MAC-d flows.

2> for the IE "HARQ Info for E-DCH":

3> perform the actions specified in subclause 8.6.5.17.

2> if the IE "Added or Reconfigured E-DCH MAC-d Flow list " is included:

3> for each MAC-d flow identified by the IE "Mac-d flow identity":

4> perform the actions as specified in subclause 8.6.5.18.

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

NOTE: In case of multiple E-DCH MAC-d flows, IE "Added or Reconfigured UL TrCH information" is only included once. If the IE "Added or Reconfigured UL TrCH information" is included more than once with the IE "Uplink transport channel type" set to ‘E-DCH’, the UE behaviour is unspecified.

NOTE: In case the IE "Added or Reconfigured UL TrCH information" is included in a message that contains the IE "Deleted UL TrCH information" with a transport channel with the same identity as indicated by IE "UL Transport Channel Identity" and same type as indicated in the IE "Uplink transport channel type" then the UE behaviour is unspecified.

8.6.5.5a Added or reconfigured MAC-d flow

If the IE "Added or reconfigured MAC-d flow" is included, the UE shall:

1> if a MAC-hs queue (identified by the IE "MAC-hs queue Id") is included in both the IE "MAC-hs queue to add or reconfigure list" and the IE "MAC-hs queue to delete list":

2> set the variable INVALID_CONFIGURATION to TRUE.

1> for each MAC-hs queue included in the IE "MAC-hs queue to add or reconfigure" list:

2> if the UE has previously stored a mapping between this MAC-hs queue and a MAC-d flow:

3> delete the old mapping.

2> map the MAC-d flow indicated in the current message to this MAC-hs queue;

2> set the release timer for each of the MAC-hs queues in the MAC-hs entity to the value in the corresponding IE "T1";

2> set the MAC-hs receiver window size for each of the MAC-hs queues in the MAC-hs entity to the value in the corresponding IE "MAC-hs window size"; and

2> configure MAC-hs with the mapping between MAC-d PDU sizes index and allowed MAC-d PDU sizes as follows:

3> if a MAC-d PDU size has been stored for a MAC-d PDU size index for the corresponding MAC-hs queue and no mapping is provided in the current message for this MAC-d PDU index:

4> continue to use this mapping.

3> if a MAC-d PDU size has been stored for a MAC-d PDU size index for the corresponding MAC-hs queue and a mapping is provided in the current message for this MAC-d PDU index:

4> configure the MAC-hs entity with the mapping indicated in the current message.

1> for each MAC-hs queue included in the IE "MAC-hs queue to delete" list:

2> delete any information about the MAC-hs queue identified by the IE "MAC-hs queue Id".

1> if the IE "Added or reconfigured MAC-d flow" is considered valid according to the rules above:

2> perform the actions as specified in subclause 8.5.21.

8.6.5.6 Added or Reconfigured DL TrCH information

If the IE "Added or Reconfigured DL TrCH information" is included the UE shall:

1> for the transport channel identified by the IE "DL Transport Channel Identity":

2> if the choice "DL parameters" is set to ‘explicit’:

3> perform the actions for the IE "Transport Format Set" as specified in subclause 8.6.5.1.

2> if the choice "DL parameters" is set to ‘same as uplink’:

3> if the IE "UL Transport Channel Identity" indicates an existing or a new UL Transport Channel:

4> store as transport format for this transport channel the transport format associated with the transport channel identified by the IE "UL Transport Channel Identity".

3> else:

4> set the variable INVALID_CONFIGURATION to TRUE.

2> if the IE "DCH quality target" is included:

3> perform the actions specified in subclause 8.6.5.4.

1> if the choice "DL parameters" is set to "HSDSCH":

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

3> perform the actions specified in subclause 8.6.5.6b.

2> if the IE "Added or Reconfigured MAC-d Flow" is included:

3> perform the actions as specified in subclause 8.6.5.5a.

2> if the IE "Added or Reconfigured MAC-ehs reordering queue" is included:

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

4> perform the actions as specified in subclause 8.6.5.23 for both MAC-ehs entities.

3> else:

4> perform the actions as specified in subclause 8.6.5.23.

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

NOTE: The UE stores the DL transport channel configuration until it is explicitly deleted by a message containing the IE "Deleted DL TrCH information" or the UE leaves RRC connected mode.

NOTE: In case the IE "Added or Reconfigured DL TrCH information" is included in a message that contains the IE "Deleted DL TrCH information" with a transport channel with the same identity as indicated by IE "DL Transport Channel Identity" and same type as indicated in the IE "Downlink transport channel type" then the UE behaviour is unspecified.

8.6.5.6a Void

8.6.5.6b HARQ Info

If the IE "HARQ Info" is included, 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> determine the value for the HS_DSCH_RECEPTION_CELL_FACH_STATE variable and take the corresponding actions as described in subclause 8.5.36.

When the corresponding entry in the variable SECONDARY_CELL_HS_DSCH_RECEPTION is set to TRUE, the number of processes for the secondary serving HS-DSCH cell is derived from Table 8.6.5.6b:

Table 8.6.5.6b: "Number of Processes for a secondary serving HS-DSCH cell"

	The IE "Number of Processes" is set to a value between 1 and 5, inclusive	The IE "Number of Processes" is set to a value between 6 and 8, inclusive	The IE "Number of Processes" is set to 12,14 or 16	The IE "Number of Processes" is set to 24, 28 or 32
If MIMO or MIMO mode with four transmit antennas with dual stream restriction is configured for this secondary serving HS-DSCH cell	If Memory Partitioning is set to implicit, the UE behaviour is not specified. Else, the number of processes for the secondary serving HS-DSCH cell is equal to twice the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to twice the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to half the value of the IE "Number of Processes"
If MIMO or MIMO mode with four transmit antennas is not configured for this secondary serving HS-DSCH cell	If Memory Partitioning is set to implicit, the UE behaviour is not specified. Else, the number of processes for the secondary serving HS-DSCH cell is equal to the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to half the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to quarter the value of the IE "Number of Processes"
If MIMO mode with four transmit antennas is configured for this secondary serving HS-DSCH cell	If Memory Partitioning is set to implicit, the UE behaviour is not specified. Else, the number of processes for the secondary serving HS-DSCH cell is equal to four times the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to four times the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to twice the value of the IE "Number of Processes"	The number of processes for this secondary serving HS-DSCH cell is equal to the value of the IE "Number of Processes"

When the variable HS_DSCH_RECEPTION or HS_DSCH_RECEPTION_CELL_FACH_STATE is set to TRUE, or the corresponding entry in the variable SECONDARY_CELL_HS_DSCH_RECEPTION is set to TRUE the UE shall:

1> for 1.28 Mcps TDD, when variable HS_DSCH_RECEPTION_CELL_FACH_STATE is TRUE,

2> consider the UE capability "Total number of soft channel bits in HS-DSCH" equal to that of the HS-DSCH physical layer category 9 as specified in [35];

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

2> configure both MAC-ehs entities with the number of HARQ processes indicated in IE "Number of Processes" and in Table 8.6.5.6b.

1> else:

2> configure the MAC-hs/ehs entity with the number of HARQ processes indicated in IE "Number of Processes" and in Table 8.6.5.6b.

1> assign to each of these HARQ processes IDs going from 0 to "Number of Processes" – 1 per HS-DSCH;

1> if the IE "Memory Partitioning" is set to ‘Implicit’:

2> partition the soft memory buffer equally among the HS-DSCH transport channels, assuming that the number of HS-DSCH transport channels is equal to the "Total Number of serving/secondary serving HS-DSCH cells" (defined in Table 5.1a of [35]) for the category used by the UE in accordance to subclause 8.1.6.2. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

2> if MIMO is configured on some but not all HS-DSCH transport channels:

3> for each of the HS-DSCH transport channels configured with MIMO, partition the soft memory buffer equally among the processes configured above. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

3> for each of the HS-DSCH transport channels configured without MIMO, use the HARQ process memory buffer size calculated for the MIMO configured HS-DSCH transport channels above.

2> if MIMO mode with four transmit antennas is configured on some but not all HS-DSCH transport channels:

3> for each of the HS-DSCH transport channels configured with MIMO mode with four transmit antennas, partition the soft memory buffer in the MAC-ehs entity equally among the processes configured above. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

3> for each of the HS-DSCH transport channels configured without MIMO mode with four transmit antennas, use the HARQ process memory buffer size calculated for the MIMO configured HS-DSCH transport channels above.

2> else if multi-cell operation on more than two cells without MIMO is configured, and UE is capable of multi- cell MIMO operation on more than two cells:

3> partition the soft memory buffer equally among the processes configured above, as if MIMO is configured. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

2> else:

3> partition the soft memory buffer per HS-DSCH transport channels equally among the processes configured above. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

1> if the IE "Memory Partitioning" is set to ‘Explicit’:

2> if the UE capability "Total number of soft channel bits in HS-DSCH", as specified in [35], is exceeded with this configuration; or

2> if MIMO is not configured and if the IE "Process Memory size" is set to a value greater than the number of soft channel bits for an implicit memory partitioning with 6 processes per HS-DSCH transport channel, and the IE "Downlink secondary cell info FDD" is included; or

2> if MIMO is configured and the IE "Process Memory size" is set to a value greater than number of soft channel bits for an implicit memory partitioning with 12 processes per HS-DSCH transport channel, and the IE "Downlink secondary cell info FDD" is included; or

2> if MIMO mode with four transmit antennas is configured and the IE "Process Memory size" is set to a value greater than number of soft channel bits for an implicit memory partitioning with 24 processes per HS-DSCH transport channel, and the IE "Downlink secondary cell info FDD" is included:

3> set the variable INVALID_CONFIGURATION to TRUE.

2> else:

3> partition the soft memory buffer equally among the HS-DSCH transport channels. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearerst Integer value.

3> partition the soft memory buffer per HS-DSCH transport channel according to the IE "Process memory size" assuming that the order in the list follows the order in the HARQ process IDs.

3> if MIMO mode with four transmit antennas is configured partition the soft memory buffer per HS-DSCH transport channel in the MAC-ehs entity according to the IE "Process memory size" assuming that the order in the list follows the order in the HARQ process IDs.

3> If the IE "Process memory size" included in the IE "Memory size" different from the IE "Process memory size" included in the IE "Additional memory sizes for 4^th MIMO stream":

4> set the variable INVALID_CONFIGURATION to TRUE.

3> If the IE "Process memory size" included in the IE "Additional memory sizes for MIMO" different from the IE "Process memory size" included in the IE "Additional memory sizes for 3^rd MIMO stream":

4> set the variable INVALID_CONFIGURATION to TRUE.

8.6.5.6c Void

8.6.5.7 Deleted UL TrCH information

If the IE "Deleted UL TrCH information" is included the UE shall:

1> if an Uplink transport channel is requested to be deleted:

2> delete any information about the transport channel identified by the IE "UL TrCH identity" and the IE "Uplink transport channel type".

1> if an E-DCH MAC-d flow is requested to be deleted:

2> delete any information about the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity";

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

8.6.5.8 Deleted DL TrCH information

If the IE "Deleted DL TrCH information" is included the UE shall:

1> if a Downlink transport channel is requested to be deleted:

2> delete any information about the transport channel identified by the IE "DL TrCH identity".

1> if a DL MAC-d flow is requested to be deleted:

2> delete any information about the DL HS-DSCH MAC-d flow identified by the IE "MAC-d Flow Identity", i.e. delete any information about MAC-hs queue(s) mapped onto this MAC-d flow.

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

1> if a DL MAC-ehs reordering queue is requested to be deleted:

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

3> delete any information about the DL HS-DSCH DL MAC-ehs reordering queue identified by the IE "DL HS-DSCH MAC-ehs queue Id" from both MAC-ehs entities.

2> else:

3> delete any information about the DL HS-DSCH DL MAC-ehs reordering queue identified by the IE "DL HS-DSCH MAC-ehs queue Id".

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

8.6.5.9 UL Transport channel information common for all transport channels

If the IE "UL Transport channel information common for all transport channels" is included the UE shall:

1> perform actions for the IE "TFC subset" as specified in subclause 8.6.5.3;

1> if the IE "PRACH TFCS" is included:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> if the IE has the choice "mode" set to FDD:

2> perform actions for the IE "UL DCH TFCS" as specified in subclause 8.6.5.2.

1> if the IE has the choice "mode" set to TDD:

2> if the IE "Individual UL CCTrCH information" is included:

3> for each TFCS identified by IE "UL TFCS id":

4> perform actions for the IE "UL TFCS" as specified in subclause 8.6.5.2.

1> if the IE "TFC subset list" is included:

2> remove a previously stored TFC subset list if this exists in the IE "TFC subset list" in the variable TFC_SUBSET;

2> store the IE "TFC subset list" in the IE "TFC subset list" in the variable TFC_SUBSET;

2> consider the first instance of the IE "TFC subset" in the IE "TFC subset list" as Transport Format Combination Subset 0 (TFC subset identity = 0), the second instance as Transport Format Combination Subset 1 (TFC subset identity = 1) and so on;

2> if the IE"TFC subset list" contains greater than 8 elements then the UE behaviour is not specified.

NOTE: The UTRAN should not modify the TFC subset list when a temporary restriction of the TFC set is being applied, due to the reception of the IE "TFC Control Duration" in a TRANSPORT FORMAT COMBINATION CONTROL message is still being applied.

8.6.5.10 DL Transport channel information common for all transport channels

If the IE "DL Transport channel information common for all transport channels" is included the UE shall:

1> if the IE "SCCPCH TFCS" is included:

2> set the variable INVALID_CONFIGURATION to TRUE.

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

2> if the choice "DL parameters" is set to ‘explicit’:

3> if the IE "DL DCH TFCS" is included:

4> if the IE "SCCPCH TFCS" is included and the state the UE enters after handling the received information is other than CELL_DCH:

5> ignore the received IE "DL DCH TFCS".

NOTE: the IE "DL Transport channel information common for all transport channels" always includes a DL DCH TFCS configuration, either by including the IE "DL DCH TFCS " or by specifying that the TFCS is the same as in UL. If UTRAN does not require the reconfiguration of the concerned parameters, UTRAN may replace one TFC with the value that is already assigned for this IE.

4> else:

5> perform actions as specified in subclause 8.6.5.2.

1> if the IE choice "mode" is set to TDD:

2> if the IE "Individual DL CCTRCH information" is included:

3> for each DL TFCS identified by the IE "DL TFCS identity":

4> if the IE choice "DL parameters" is set to ‘independent’:

5> perform actions for the IE "DL TFCS" as specified in subclause 8.6.5.2.

4> if the IE choice "DL parameters" is set to ‘same as UL’:

5> if the IE "UL DCH TFCS identity" indicates an existing or a new UL TFCS:

6> store for that DL TFCS the TFCS identified by the IE "UL DCH TFCS identity".

5> else:

6> set the variable INVALID_CONFIGURATION to TRUE.

8.6.5.11 Void

8.6.5.12 TFCS Reconfiguration/Addition Information

If the IE "TFCS Reconfiguration/Addition Information" is included the UE shall:

1> store the TFCs to be reconfigured/added indicated in the IE "CTFC information" as specified below;

1> if the IE "Power offset information" is included:

2> perform actions as specified in [29].

In order to identify the TFCs included in this IE the UE shall calculate the CTFC as specified in subclause 14.10.

1> if the IE "Additional Dynamic Transport Format Information for CCCH" was included in the IE "RACH TFS":

2> ignore for the CTFC calculation any TF added by the IE "Additional Dynamic Transport Format Information for CCCH".

If the IE "TFCS Reconfiguration/Addition Information" is used in case of TFCS "Complete reconfiguration" the UE shall:

1> remove a previously stored transport format combination set if this exists;

1> consider the first instance of the IE "CTFC information" as Transport Format Combination 0 in FDD (TFCI=0) and 1 in TDD (TFCI=1), the second instance as Transport Format Combination 1 in FDD (TFCI=1) and 2 in TDD (TFCI=2) and so on. In TDD the TFCI value = 0 is reserved for physical layer use.

If the IE "TFCS Reconfiguration/Addition Information" is used in case of TFCS "Addition" the UE shall insert the new additional(s) TFC into the first available position(s) in ascending TFCI order in the TFCS.

8.6.5.12a Additional RACH TFCS for CCCH

If the IE "Additional RACH TFCS for CCCH " is included the UE shall:

1> if the IE "Power offset information" is included:

2> perform actions as specified in [29].

1> add to the TFCS as calculated in 8.6.5.12 for the corresponding PRACH the TFC which consists of the TF added by the IE "Additional Dynamic Transport Format Information for CCCH" into the next position in ascending order after the highest TFCI value already used.

NOTE: On PRACH only one transport channel can be multiplexed.

8.6.5.13 TFCS Removal Information

If the IE "TFCS Removal Information" is included the UE shall:

1> remove the TFC indicated by the IE "TFCI" from the current TFCS, and regard this position (TFCI) in the TFCS as vacant.

8.6.5.14 Void

8.6.5.15 TFCS Explicit Configuration

If the IE " TFCS Explicit Configuration" is included the UE shall:

1> if the IE choice "TFCS representation" is set to ‘complete reconfiguration’:

2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12.

1> if the IE choice "TFCS representation" is set to ‘addition’:

2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12.

1> if the IE choice "TFCS representation" is set to ‘removal’:

2> perform the actions for the IE "TFCS Removal Information" as specified in subclause 8.6.5.13.

1> if the IE choice "TFCS representation" is set to ‘replace’:

2> perform first the actions for the IE "TFCS Removal Information" as specified in subclause 8.6.5.13; and then

2> perform the actions for the IE "TFCS Reconfiguration/Addition Information" as specified in subclause 8.6.5.12.

8.6.5.16 E-DCH Transmission Time Interval (FDD only)

If the IE "E-DCH Transmission Time Interval" is included, the UE shall:

1> store the received TTI;

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> apply the TTI as signalled in the IE "E-DCH Transmission Time Interval" on the E-DPDCH.

If the received "E-DCH Transmission Time Interval" is 2 ms and the previously stored TTI was 10 ms:

1> not send any data on E-DPDCH in first 8 TTIs after activation time of new TTI.

8.6.5.17 HARQ Info for E-DCH

If the IE "HARQ Info for E-DCH" is included, the UE shall:

1> store the received configuration;

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> use a redundancy version for each HARQ transmission as configured by the IE "HARQ RV Configuration".

8.6.5.18 Added or reconfigured E-DCH MAC-d flow

If the IE "Added or reconfigured E-DCH MAC-d flow" is included, the UE shall:

1> if the IE "E-DCH MAC-d flow power offset" is included:

2> configure the power offset indicated in the IE "E-DCH MAC-d flow power offset" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> if the IE "E-DCH MAC-d flow maximum number of retransmissions" is included:

2> configure the maximum number of retransmissions indicated in the IE "E-DCH MAC-d flow maximum number of retransmissions" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> for 1.28 Mcps TDD, if the IE "E-DCH MAC-d flow retransmission timer" is included:

2> configure the retransmission timer for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity".

1> if the IE "E-DCH MAC-d flow multiplexing list" is included:

2> only multiplex MAC-d PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from E-DCH MAC-d flows with which multiplexing in the same MAC-e or MAC-i PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list".

1> else:

2> if previously the IE "E-DCH MAC-d flow multiplexing list" was already received for this E-DCH MAC-d flow:

3> continue to only multiplex E-DCH PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from E-DCH MAC-d flows with which multiplexing in the same MAC-e or MAC-i PDU is allowed according to the previously received IE "E-DCH MAC-d flow multiplexing list".

2> else (never received the IE "E-DCH MAC-d flow multiplexing list" for this E-DCH MAC-d flow):

3> allow multiplexing of MAC-d PDU’s from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDU’s from any other E-DCH MAC-d flow in the same MAC-e or MAC-i PDU.

1> for FDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> if the TTI configured on the E-DCH equals 2ms, and the IE "2ms non-scheduled transmission grant HARQ process allocation" is configured for this MAC-d flow:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e or MAC-i PDU transmitted by HARQ processes allowed by the IE "2ms non-scheduled transmission grant HARQ process allocation", with a total contribution from this MAC-d flow (i.e. including MAC-e/es or MAC-i/is headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

3> else:

4> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall be included in a MAC-e or MAC-i PDU transmitted by any HARQ process, with a total contribution from this MAC-d flow (i.e. including MAC-e/es or MAC-i/is headers) not exceeding the size as signalled by the IE "Max MAC-e PDU contents size".

2> if the IE "Scheduled transmission grant info" is included:

3> transmission of MAC-d PDU’s for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH/E-RGCH (see [15]).

1> for TDD:

2> if the IE "Non-scheduled transmission grant info" is included:

3> MAC-d PDU’s for logical channels belonging to this MAC-d flow shall only be included in a MAC-e or MAC-i PDU transmitted by HARQ processes designated as non scheduled (Ids 4 – 7) in the TTIs indicated (for 3.84 Mcps TDD and 7.68 Mcps TDD, as determined from the IEs "Activation Time", "Resource Duration" and "Resource Periodicity"; for 1.28 Mcps TDD, as determined from the IEs "Activation Time", "Subframe number", "Resource Duration" and "Resource Periodicity", and the calculation of assigned Non-scheduled transmission grant is specified in subclause 8.6.6.16a).

2> if the IE "Scheduled transmission grant info" is included:

3> transmission of MAC-d PDUs for logical channels belonging to this MAC-d flow shall be in accordance with the received scheduled grant on E-AGCH (see [15]).

1> perform the actions as specified in subclause 8.5.21;

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

8.6.5.19 SRB1 mapping info (FDD and 1.28 Mcps TDD only)

When variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE and the UE is in CELL_FACH state, the UE shall:

1> if no MAC-ehs queue with identified by the "MAC-ehs queue identity" value as received in IE "SRB1 mapping info" of System Information Block type 5 or System Information Block type 5bis is configured:

2> the UE behaviour is unspecified.

1> else:

2> map the logical channel identified by the IE "Logical channel identity" to the MAC-ehs queue identified by the IE "MAC-ehs queue identity" as received in IE "SRB1 mapping info" of System Information Block type 5 or System Information Block type 5bis.

8.6.5.20 HARQ System Info (FDD and 1.28 Mcps TDD only)

When the UE is not in RRC Connected state and the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE, or when the UE is in CELL_FACH state or will be in CELL_FACH state at the completion of this procedure, the UE shall:

1> if IE "HS-DSCH common system information" is included in System Information Block type 5 or System Information Block type 5bis:

2> for 1.28 Mcps TDD, consider the UE capability "Total number of soft channel bits in HS-DSCH" equal to that of the HS-DSCH physical layer category 9 as specified in [35];

2> configure the MAC-ehs entity with the number of HARQ processes indicated in IE "Number of Processes";

2> assign to each of these HARQ processes IDs going from 0 to "Number of Processes" – 1;

2> if the IE "Memory Partitioning" is set to ‘Implicit’:

3> partition the soft memory buffer in the MAC-ehs entity equally among the processes configured above. In the event that the division of the soft memory buffer results in a non-Integer value the partition memory size is rounded down to the nearest Integer value.

2> if the IE "Memory Partitioning" is set to ‘Explicit’:

3> if the UE capability "Total number of soft channel bits in HS-DSCH", as specified in [35], is exceeded with this configuration:

4> the UE behaviour is unspecified.

3> else:

4> partition the soft memory buffer in the MAC-ehs entity according to the IE "Process memory size" assuming that the order in the list follows the order in the HARQ process IDs.

8.6.5.21 CCCH mapping info (FDD and 1.28 Mcps TDD only)

When the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE, the UE shall:

1> if no MAC-ehs queue with identified by the "MAC-ehs queue identity" value as received in IE "CCCH mapping info" of System Information Block type 5 or System Information Block type 5bis is configured:

2> set the variable INVALID_CONFIGURATION to TRUE.

1> else:

2> map the logical channel identified by the IE "Logical channel identity" to the MAC-ehs queue identified by the IE "MAC-ehs queue identity" as received in IE "CCCH mapping info" of System Information Block type 5 or System Information Block type 5bis.

1> if there is more than one multiplexing option applicable for logical channels to be used:

2> the UE behaviour is not specified.

8.6.5.22 Common MAC-ehs reordering queue (FDD and 1.28 Mcps TDD only)

When the variable HS_DSCH_RECEPTION_OF_CCCH_ENABLED is set to TRUE, the UE shall:

1> set the release timer for the MAC-ehs queue in the MAC-ehs entity to the value in the corresponding IE "T1";

1> set the reset timer for the MAC-ehs queue in the MAC-ehs entity to the value in te corresponding IE "Treset";

1> set the MAC-ehs receiver window size for the MAC-ehs queues in the MAC-ehs entity to the value in the corresponding IE "MAC-ehs window size".

8.6.5.23 Added or reconfigured MAC-ehs reordering queue

If the IE "Added or reconfigured MAC-ehs reordering queue" is included, the UE shall:

1> if the IE "Deleted DL TrCH information" is included in the received message; and

1> if a MAC-ehs queue (identified by the IE "MAC-ehs queue Id") is included in both the IE "MAC-ehs queue to add or reconfigure list" and the IE "DL HS-DSCH MAC-ehs reordering queue" within the IE "Deleted DL TrCH information":

2> the UE behaviour is unspecified.

1> for each MAC-ehs queue included in the IE "MAC-ehs queue to add or reconfigure" list:

2> set the release timer for each of the MAC-ehs queues in the MAC-ehs entity to the value in the corresponding IE "T1";

2> set the reset timer for the MAC-ehs queue in the MAC-ehs entity to the value in te corresponding IE "Treset";

NOTE: A UE that does not support reception of HS-DSCH in CELL_FACH state may ignore the IE "Treset".

2> set the MAC-ehs receiver window size for each of the MAC-ehs queues in the MAC-ehs entity to the value in the corresponding IE "MAC-ehs window size".

1> if the IE "Added or reconfigured MAC-ehs reordering queue" is considered valid according to the rules above:

2> perform the actions as specified in subclause 8.5.21.

8.6.5.24 Common E-DCH MAC-d flows (FDD and 1.28 Mcps TDD only)

The UE shall:

1> configure the power offset indicated in the IE "E-DCH MAC-d flow power offset" for the E-DCH MAC-d or MAC-c (for FDD) flow identified by the IE "E-DCH MAC-d flow identity";

1> configure the maximum number of retransmissions indicated in the IE "E-DCH MAC-d flow maximum number of retransmissions" for the E-DCH MAC-d flow identified by the IE "E-DCH MAC-d flow identity";

1> for 1.28 Mcps TDD, configure the maximum retransmission timer indicated in the IE "E-DCH MAC-d flow retransmission timer" for the E-DCH MAC-d or MAC-c (for FDD) flow identified by the IE "E-DCH MAC-d flow identity";

1> if the IE "E-DCH MAC-d flow multiplexing list" is included:

2> only multiplex MAC-d PDUs from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from E-DCH MAC-d flows with which multiplexing in the same MAC-i PDU is allowed in accordance to the IE "E-DCH MAC-d flow multiplexing list".

1> else (IE "E-DCH MAC-d flow multiplexing list" not included in the system information):

2> allow multiplexing of MAC-d PDUs from the E-DCH MAC-d flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from any other E-DCH MAC-d flow in the same MAC-i PDU.

2> for FDD, prohibit multiplexing of MAC-c PDUs from the E-DCH MAC-c flow indicated in the IE "E-DCH MAC-d flow identity" with MAC-d PDUs from any other E-DCH MAC-d flow in the same MAC-i PDU.

1> transmission of MAC-d PDUs or MAC-c PDUs for logical channels belonging to this MAC-d or MAC-c flow shall be in accordance with the serving grant (FDD only) (see [15]);

1> perform the actions as specified in subclause 8.5.21.

NOTE For FDD, if as per subclause 8.5.45, the TTI applied on E-DPDCH is different from the TTI signalled in the IE "E-DCH Transmission Time Interval" , then the IE’s "E-DCH MAC-d flow identity", "E-DCH MAC-d flow power offset" and "E-DCH MAC-d flow maximum number of retransmissions" in fact refer to the corresponding IE’s, if present, in "Common E-DCH MAC-d flow info for Concurrent TTI" in the IE "Common E-DCH system info parameters for Concurrent TTI" of System Information Block type 22.

8.6.5.25 Early DCH quality target

When operating with DCH Enhancements in DL FET Full mode, the UE shall:

1> set, at physical channel establishment, the initial downlink target SIR based on either the IE "Early DCH quality target" or the IE "DCH quality target" if included, whichever requires a higher value, for transport channel(s) undergoing concatenation at the physical layer as indicated in the IE "TrCh Concatenation Info";

1> adjust the downlink target SIR for the downlink power control to meet either the early quality target received in the IE "Early DCH quality target" at the end of the slot number received in the IE "Early DCH quality target slot" or the quality target received in the IE "DCH qualiy target" at the end of slot number 29, whichever requires a higher value, for those transport channel(s).