8.3.1 Radio Link Addition

25.4333GPPRelease 17TSUTRAN Iub interface Node B Application Part (NBAP) signalling

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

8.3.1.1 General

This procedure is used for establishing the necessary resources in the Node B for one or more additional RLs towards a UE when there is already a Node B Communication Context for this UE in the Node B.

The Radio Link Addition procedure shall not be initiated if a Prepared Reconfiguration exists, as defined in subclause 3.1.

8.3.1.2 Successful Operation

Figure: 28 Radio Link Addition procedure, Successful Operation

The procedure is initiated with a RADIO LINK ADDITION REQUEST message sent from the CRNC to the Node B using the Communication Control Port assigned to the concerned Node B Communication Context.

Upon reception, the Node B shall reserve the necessary resources and configure the new RL(s) according to the parameters given in the message. Unless specified below, the meaning of parameters is specified in other specifications.

The Node B shall prioritise resource allocation for the RL(s) to be established according to Annex A.

If the UE Aggregate Maximum Bit Rate IE is contained in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, store the received UE Aggregate Maximum Bit Rate parameters to control the aggregate data rate of non GBR traffic for this UE.

Physical Channels Handling:

[TDD – If the [3.84Mcps TDD – UL DPCH Information IE] [1.28Mcps TDD – UL DPCH Information LCR IE] [7.68Mcps TDD – UL DPCH Information 7.68Mcps IE] is present, the Node B shall configure the new UL DPCH(s) according to the parameters given in the message.]

[TDD – If the [3.84Mcps TDD – DL DPCH Information IE] [1.28Mcps TDD – DL DPCH Information LCR IE] [7.68Mcps TDD – DL DPCH Information 7.68Mcps IE] is present, the Node B shall configure the new DL DPCH(s) according to the parameters given in the message.]

[1.28Mcps TDD – If the UL Timeslot Information LCR IE includes the PLCCH Information IE, the Node B shall transmit TPC /SS bits on a PLCCH according to the parameters given in the message.]

[FDD – Compressed Mode]:

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Compressed Mode Deactivation Flag IE with value ”Deactivate”, the Node B shall not activate any compressed mode pattern in the new RLs. In all the other cases (Flag set to ”Maintain Active” or not present), the ongoing compressed mode (if existing) shall be applied also to the added RLs.]

[FDD – If the Node B Communication Context is configured to use DPCH in the downlink and if the RADIO LINK ADDITION REQUEST message contains the Transmission Gap Pattern Sequence Code Information IE for any of the allocated DL Channelisation Codes, the Node B shall apply the alternate scrambling code as indicated for each DL Channelisation Code for which the Transmission Gap Pattern Sequence Code Information IE is set to "Code Change".]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Active Pattern Sequence Information IE, the Node B shall use the information to activate the indicated Transmission Gap Pattern Sequence(s) in the new RL. The received CM Configuration Change CFN refers to the latest passed CFN with that value The Node B shall treat the received TGCFN IEs as follows:]

– [FDD – If any received TGCFN IE has the same value as the received CM Configuration Change CFN IE, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]

– [FDD – If any received TGCFN IE does not have the same value as the received CM Configuration Change CFN IE but the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE has already passed, the Node B shall consider the concerned Transmission Gap Pattern Sequence as activated at that CFN.]

– [FDD – For all other Transmission Gap Pattern Sequences included in the Active Pattern Sequence Information IE, the Node B shall activate each Transmission Gap Pattern Sequence at the first CFN after the CM Configuration Change CFN with a value equal to the TGCFN IE for the Transmission Gap Pattern Sequence.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE, the concerned Transmission Gap Pattern Sequence shall be applied to HS-DSCH serving cells associated with C-ID IE included in Affected HS-DSCH serving cell List IE. Otherwise the concerned Transmission Gap Pattern Sequence shall be applied to all the configured serving cells.]

[FDD – DL Code Information]:

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

[TDD – CCTrCH Handling]:

[TDD – If the UL CCTrCH Information IE is present, the Node B shall configure the new UL CCTrCH(s) according to the parameters given in the message.]

[1.28Mcps TDD – If the UL CCTrCH Information IE includes the TDD TPC UL Step Size IE, the Node B shall configure the uplink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]

[TDD – If the DL CCTrCH Information IE is present, the Node B shall configure the new DL CCTrCH(s) according to the parameters given in the message.]

[TDD – If the DL CCTrCH Information IE includes the TDD TPC DL Step Size IE, the Node B shall configure the downlink TPC step size according to the parameters given in the message, otherwise it shall use the step size configured in other radio link.]

[1.28 Mcps TDD – The Node B shall configure the HS-SCCH TPC step size to the same value as the TDD TPC DL Step Size IE of the lowest numbered DL CCTrCH whose DL CCTrCH Information IE includes the TDD TPC DL Step Size IE. If no DL CCTrCH Information IE includes the TDD TPC DL Step Size IE, it shall use the step size configured in other radio link.]

[1.28 Mcps TDD – If the TDD TPC DL Step Size IE is not included in the DL CCTrCH Information IE, the Node B shall use the E-AGCH TPC step size IE in the E-PUCH Information LCR IE in the E-DCH Information 1.28Mcps IE for HS-SCCH inner loop power control related operation.]

[FDD – UL CLTD Handling]:

[FDD – If the UL CLTD Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested UL CLTD resources for the concerned Node B Communication Context in the cell to determine the precoding weights and then :]

– [FDD – If there is neither serving E-DCH RL nor the HS-DSCH RL configuration in the concerned Node B Communication Context, the C-ID IE shall be included in the UL CLTD Information IE, and the Node B shall configure this cell to determine the precoding weights for the concerned Node B Communication Context.]

– [FDD – If the UL CLTD Activation Information IE is included in the UL CLTD Information IE, then the Node B shall use this value to configure the state of UL CLTD for the concerned Node B Communication Context.]

[FDD – UL MIMO Setup]:

[FDD – If the UL MIMO Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate UL MIMO operation for the radio link according to the information provided in the IE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B]

– [FDD – The Node B shall allocate a Secondary Transport Block E-RNTI for the corresponding RL and include the E-RNTI identifier together with the corresponding E-ROCH Channelization Code in the UL MIMO DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message. The E-ROCH Channelization code shall be allocated from the pool of E-AGCH channelization codes configured for that cell.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-ROCH Power Offset IE in the UL MIMO Information IE, then the Node B may use this value to determine the E-ROCH power. The E-ROCH Power Offset should be applied for any E-ROCH transmission to this UE.]

– [FDD – The Node B may include the the Secondary Transport Block E-HICH Signature Sequence IE in UL MIMO DL Control Channel Information IE in the RADIO LINK ADDITION RESPONSE message for every RL indicated by the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE and it should include it for the Serving E-DCH RL.]

Radio Link Handling:

Diversity Combination Control:

The Diversity Control Field IE indicates for each RL whether the Node B shall combine the new RL with existing RL(s) or not.

– If the Diversity Control Field IE is set to "May", the Node B shall decide for any of the alternatives.

– If the Diversity Control Field IE is set to "Must", the Node B shall combine the RL with one of the other – RL.

– If the Diversity Control Field IE is set to "Must not", the Node B shall not combine the RL with any other existing RL.

[FDD – The signalled Diversity Control Field IE is only applicable for DCHs. In case of E-DCH, if any UARFCN(s) of the cells in the added RL(s) is not equal to at least one of the UARFCN(s) of the cells in the existing RL(s) in the Node B Communication Context, the Diversity Control Field, for those RL(s) shall be assumed to be set to "May", otherwise it shall be assumed to be set to "Must".]

When a new RL is to be combined, the Node B shall choose which RL(s) to combine it with.

In the case of not combining a RL with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or a RL previously listed in the RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that no combining is done. In this case, the Node B shall:

– include in the DCH Information Response IE both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DCH of the RL in the RADIO LINK ADDITION RESPONSE message. [FDD – for which the Transport Bearer Not Requested Indicator IE was not included].

– [FDD – include in the RADIO LINK ADDITION RESPONSE message the Transport Bearer Not Setup Indicator IE for every DCH for which establishment of a transport bearer has not taken place as a result of information in the Transport Bearer Not Requested Indicator IE in the RADIO LINK ADDITION REQUEST message.]

– [FDD – For E-DCH, include in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for the transport bearers to be established for each E-DCH MAC-d flow of this RL for which the Transport Bearer Not Requested Indicator IE was not included.]

In the case of combining with a RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, the Node B shall indicate with the Diversity Indication in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message that the RL is combined and if the ALCAP is not used [FDD – and the transport bearer for this DCH is already established], the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE included in the RL Information IE for a specific RL in the RADIO LINK ADDITION REQUEST message, shall not be used. In this case, the RL ID IE indicates (one of) the previously established RL(s) or a RL previously listed in this RADIO LINK ADDITION RESPONSE message with which the new RL is combined.

[FDD – In the case of combining with an E-DCH RL established with a previous Radio Link Setup or Radio Link Addition Procedure or with a RL previously listed in this RADIO LINK ADDITION RESPONSE message, one of the previously established RLs or a RL previously listed in this RADIO LINK ADDITION RESPONSE message including the E-DCH FDD Information Response IE shall be regarded as the RL with which the concerned E-DCH RL is combined. In case E-DCH RL is established for the first time, the Node B shall include E-DCH FDD Information Response IE instead of using the Diversity Indication of DCH RL in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. It shall include in the E-DCH FDD Information Response IE the Binding ID IE and Transport Layer Address IE for the transport bearers to be established for each E-DCH MAC-d flow of this E-DCH RL for which the Transport Bearer Not Requested Indicator IE was not included.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information RL Add Req IE, then:]

– [FDD – if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "Separate Iub Transport Bearer Mode" the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]

– [FDD – if the Multicell E-DCH Transport Bearer Mode IE for an Additional E-DCH to be Setup is set to "UL Flow Multiplexing Mode" the Node B shall use this mode in the new configuration and multiplex MAC-d flows on the transport bearers.]

– [FDD – if Separate Iub Transport Bearer Mode is used in the new configuration, then:]

– [FDD – the Node B shall follow the rules defined in this procedure for single carrier mode of operation for establishment of the transport bearer for a MAC-d flow and use the Transport Bearer Not Requested Indicator IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE to determine the transport bearer configuration in the new configuration for the MAC-d flow of the Secondary Uplink Frequency.]

– [FDD – If the Transport Layer Address IE and Binding ID IE is included for an E-DCH MAC-d flow in the Additional E-DCH MAC-d Flows Specific Information IE in the Additional E-DCH FDD Information IE, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow. If the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE in the Additional E-DCH MAC-d Flow Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response IE for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

In the case of a set of co-ordinated DCHs, the Binding ID IE and the Transport Layer Address IE shall be included for only one of the DCHs in a set of coordinated DCHs [FDD – for which the Transport Bearer Not Requested Indicator IE was not included].

[TDD – The Node B shall include in the RADIO LINK ADDITION RESPONSE message both the Transport Layer Address IE and the Binding ID IE for the transport bearer to be established for each DSCH and USCH.]

[FDD – Transmit Diversity]:

[FDD – If the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall activate/deactivate the Transmit Diversity for each new Radio Link and/or secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE and/or Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE and the already known diversity mode for the physical channel.]

DL Power Control:

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall apply the given power to the transmission on each DL DPCH or on the F-DPCH of the RL when starting transmission until either UL synchronisation on the Uu interface is achieved for the RLS or Power Balancing is activated. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RLs for this Node B Communication Context. No inner loop power control or balancing shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.214 [10], subclause 5.2.1.2) with DPC MODE currently configured for the relevant Node B Communication Context and the downlink power control procedure (see subclause 8.3.7).]

[3.84 Mcps TDD and 7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Initial DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the initial CCTrCH DL power, otherwise the initial CCTrCH DL power is the Initial DL Transmission Power IE included in the RL Information IE. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included (even if CCTrCH Initial DL Transmission Power IEs are included), the Node B shall use any transmission power level currently used on already existing CCTrCHs for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 4.2.3.4).]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Initial DL Transmission Power IE is included in the DL Timeslot Information LCR IE, then the Node B shall use that power for the initial DL power and ignore the DL Time Slot ISCP info LCR, otherwise the initial DL power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL DPCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall store this value and not transmit with a higher power on any DL DPCH or on the F-DPCH of the RL. If no Maximum DL Power IE is included, any Maximum DL power stored for already existing RLs for this Node B Communication Contextshall be applied. If the Node B Communication Context is configured to use DPCH in the downlink, during compressed mode, the P_curr, as described in ref. TS 25.214 [10] subclause 5.2.1.3, shall be added to the maximum DL power for the associated compressed frame.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall store this value and never transmit with a lower power on any DL DPCH or on the F-DPCH of the RL. If no Minimum DL Power IE is included, any Minimum DL power stored for already existing RLs for this Node B Communication Context shall be applied.]

[3.84 Mcps TDD and 7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the maximum CCTrCH DL power, otherwise the maximum CCTrCH DL power is the Maximum DL Power IE included in the RL Information IE. If no Maximum DL Power IE is included (even if CCTrCH Maximum DL Transmission Power IEs are included), any maximum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]

[3.84 Mcps TDD and 7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum CCTrCH DL power for each DCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE is included for that CCTrCH, then the Node B shall use that power for the minimum CCTrCH DL power, otherwise the minimum CCTrCH DL power is the Minimum DL Power IE included in the RL Information IE. If no Minimum DL Power IE is included (even if CCTrCH Minimum DL Transmission Power IEs are included), any minimum DL power stored for already existing DCH type CCTrCHs for this Node B Communication Context shall be applied.]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Maximum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable DL DPCH. If no Maximum DL Power IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum DL power for each timeslot within a DCH type CCTrCH by the following rule: If the Minimum DL Power IE is included in the DL Timeslot Information LCR IE for that timeslot, then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable DL DPCH. If no Minimum DL Power IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]

[3.84Mcps TDD and 7.68Mcps TDD – The initial power, maximum power, and minimum power for DSCH type CCTrCH shall be determined as follows:

– If the DSCH type CCTrCH is paired with an uplink CCTrCH(s) for inner loop power control, the minimum, maximum and initial power for each PDSCH is determined in the same way as described above for DCH type CCTrCHs.

– If the DSCH type CCTrCH is not paired with an uplink CCTrCH(s) for inner loop power control, the PDSCH transmission power is DSCH Data Frame Protocol signalled (TS 25.435 [24]), with the maximum value determined in the same way as described above for DCH type CCTrCHs. The minimum and initial powers, however, are subject to control by the CRNC via the frame protocol].

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Initial DL Transmission Power IE, the Node B shall determine the initial DL power for each timeslot within a DSCH type CCTrCH by the following rule: If both the CCTrCH Initial DL Transmission Power IE, included in the DL CCTrCH Information IE, and the DL Time Slot ISCP Info LCR IE, included in the RL Information IE, are included then the Node B shall use that power for the PDSCH and ignore the Initial DL Transmission Power IE included in the RL Information IE, otherwise the initial DL Power is the Initial DL Transmission Power IE included in the RL Information IE and if DL Time Slot ISCP info LCR IE is present, the Node B shall use the indicated value when deciding the initial DL TX Power for each timeslot as specified in TS 25.224 [21], it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged. The Node B shall apply the given power to the transmission on each DL PDSCH and on each Time Slot of the CCTrCH when starting transmission until the UL synchronisation on the Uu interface is achieved for the CCTrCH. If no Initial DL Transmission Power IE is included, the Node B shall use any transmission power level currently used on already existing RL/timeslots for this Node B Communication Context. No inner loop power control shall be performed during this period. The DL power shall then vary according to the inner loop power control (see ref. TS 25.224 [21], subclause 5.1.2.4).]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum DL Power IE, the Node B shall determine the maximum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Maximum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the maximum DL power, otherwise the maximum DL power is the Maximum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a higher power on any applicable PDSCH. If no Maximum DL Power IE is included, any maximum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Minimum DL Power IE, the Node B shall determine the minimum DL power for each timeslot within a DSCH type CCTrCH by the following rule: If the CCTrCH Minimum DL Transmission Power IE, included in the DL CCTrCH Information IE, is included then the Node B shall use that power for the minimum DL power, otherwise the minimum DL power is the Minimum DL Power IE included in the RL Information IE. The Node B shall store this value and not transmit with a lower power on any applicable PDSCH. If no Minimum DL Power IE is included, any minimum DL power stored for already existing RL/timeslots for this Node B Communication Context shall be applied.]

[3.84Mcps TDD and 7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the DL Time Slot ISCP Info IE, the Node B shall use the indicated value when deciding the DL TX Power for each timeslot as specified in ref. TS 25.224 [21], i.e. it shall reduce the DL TX power in those downlink timeslots of the radio link where the interference is low, and increase the DL TX power in those timeslots where the interference is high, while keeping the total downlink power in the radio link unchanged.]

[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. P_initshall be set to the power level indicated by the Initial DL Transmission Power IE (if received) or the decided DL TX power level on each DL channelisation code of a RL based on power level of existing RLs.]

[1.28Mcps TDD – Uplink Synchronisation Parameters LCR]:

[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message contains the Uplink Synchronisation Parameters LCR IE, the Node B shall use the indicated values of Uplink Synchronisation Stepsize IE and Uplink Synchronisation Frequency IE when evaluating the timing of the UL synchronisation.]

[1.28Mcps TDD – Power Control GAP:]

[1.28Mcps TDD – If the Power Control GAP IE is included in the RADIO LINK ADDITION REQUEST message, the Node B may use the value for the power control for HS-SCCH and HS-SICH according to TS 25.224 [21].]

[1.28Mcps TDD – E-UTRAN Inter-RAT measurement:]

[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Idle Interval Information IE, if supported, the Node B shall use the value for E-UTRAN Inter-RAT measurement according to TS 25.331 [18].

[1.28Mcps TDD – Inter-frequency/ Inter-RAT measurement:]

[1.28Mcps TDD – If the RADIO LINK ADDITON REQUEST message includes the Measurement occasion pattern sequence parameters IE in the DCH Measurement Occasion Information IE, the Node B shall store the information about the Measurement occasion pattern sequences and use the value(s) to calculate the Inter-frequency/Inter-RAT measurement occasion according to TS 25.331 [18].]

[FDD – HS-DSCH Preconfiguration for Enhanced HS Serving Cell Change]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Preconfiguration Setup IE in the RL Information IE for a Radio Link not indicated by the HS-PDSCH RL ID IE in the HS-DSCH Serving Cell Change Information IE the Node B shall if supported preconfigure the indicated cells or Enhanced HS Serving Cell Change acoording to [49.]:]

– [FDD – The Node B shall preconfigure sets of HS-SCCH codes on the cells preconfigured for HS-DSCH, primary serving HS-DSCH cell, as well as on the secondary serving HS-DSCH cells. The primary serving HS-DSCH cell is designated through the C-ID IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message. The list of secondary serving HS-DSCH cells is designated by the list of Secondary C-IDs in the HS-DSCH Preconfiguration Setup IE part of the RL Information IE in the RADIO LINK ADDITION REQUEST message.]

– [FDD – The number of HS-SCCH codes to preconfigure for each cell may be optionally specified:]

– [FDD – – by the Num Primary HS-SCCH Codes IE in the HS-DSCH Preconfiguration Setup IE, for the primary serving HS-DSCH cell]

– [FDD – – by the Num Secondary HS-SCCH Codes IE in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE for each of the secondary serving HS-DSCH cells]

– [FDD – If Num Primary HS-SCCH Codes IE or Num Secondary HS-SCCH Codes IE is not included in the message the number and distribution of codes on primary and any secondary cells shall be preconfigured to satisfy any limitations in TS 25.214 [10].]

– [FDD – The Node B shall return these codes in the Sets of HS-SCCH Codes IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE of the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message.]

– [FDD – The Node B shall use the first in the numbered list of the primary serving HS-DSCH cell’s HS-SCCH codes in the HS-SCCH Preconfigured Codes IE sent to the RNC to signal the Target Cell HS-SCCH Order defined in TS 25.331 [18].]

– [FDD – The Node B shall include, in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message, IEs according to the rules defined for HS-DSCH Setup at Serving HS-DSCH Radio Link Change and:]

– [FDD – – if HARQ Preamble Mode IE is included in the HS-DSCH Preconfiguration Setup IE the HARQ Preamble Mode Activation Indicator IE]

– [FDD – – if MIMO Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]

– [FDD – if Ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]

– [FDD – if MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]

– [FDD – if Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE the MIMO N/M Ratio IE]

– [FDD – if Multiflow ordinal number of frequency IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE]

– [FDD – – if HS-DSCH MAC-d PDU Size Format IE is included in the HS-DSCH Preconfiguration Setup IE and set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used for the cell in the preconfigured configuration the HS-DSCH TB Size Table Indicator IE for each preconfigured cell]

– [FDD – – if Sixtyfour QAM Usage Allowed Indicator IE is included in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE or in the HS-DSCH Preconfiguration Setup IE the SixtyfourQAM DL Usage Indicator IE for each preconfigured cell]

– [FDD – – if Continuous Packet Connectivity HS-SCCH less Information IE is included in the HS-DSCH Preconfiguration Setup IE the Continuous Packet Connectivity HS-SCCH less Information Response IE]

– [FDD – – If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B shall store this information in the preconfigured configuration.]

– [FDD – – If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE, then the Node B may store this information in the preconfigured configuration.]

– [FDD – If the UE Support Indicator Extension IE is included in the HS-DSCH Preconfiguration Setup IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B shall include in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information containing the preconfigured configuration of the E-DCH serving cell according to the rules defined for Serving E-DCH Radio Link Change as follows:]

– [FDD – The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]

– [FDD –-The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

– [FDD –If the HS-DSCH Preconfiguration Setup IE includes the E-DCH Indicator IE for a secondary cell, the Node B shall include in the Additional E-DCH Preconfiguration Information IE in the HS-DSCH Preconfiguration Info IE in the RL Information Response IE in the RADIO LINK ADDITION RESPONSE message or in the Successful RL Information Response IE of the RADIO LINK ADDITION FAILURE message the E-DCH FDD DL Control Channel Information IE containing the preconfigured configuration of the Additional E-DCH serving cell, corresponding to the cell indicated with the E-DCH Indicator IE, according to the rules defined for Serving Additional E-DCH Radio Link Change as follows:]

– [FDD –The Node B shall allocate for the preconfigured configuration a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving Additional E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE.]

– [FDD – The Node B may configure for the preconfigured configuration the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the serving Additional E-DCH RL and include these values in the E-DCH FDD DL Control Channel Information IE.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the Multiflow Information IE, then the Node B shall allocate resources for the preconfigured Multiflow for the concerned Node B Communication Context.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the F-TPICH Information IE, then the Node B shall allocate resources for the preconfigured F-TPICH channel for the concerned Node B Communication Context.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL CLTD Information IE, then the Node B shall allocate resources for the preconfigured UL CLTD for the concerned Node B Communication Context.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the UL MIMO Information IE, then the Node B shall allocate resources for the preconfigured UL MIMO for the concerned Node B Communication Context.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixteenQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixteen QAM for the concerned Node B Communication Context.]

– [FDD – If the HS-DSCH Preconfiguration Setup IE includes the SixtyfourQAM UL Operation Indicator IE, then the Node B shall allocate resources for the preconfigured UL Sixtyfour QAM for the concerned Node B Communication Context.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Non-Serving Preconfiguration Setup IE in the RL Information IE and:]

– [FDD – if the choice of new Serving RL is "New Serving RL in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE and/or New non-serving RL E-DCH FDD DL Control Channel Information B IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – if the choice of new Serving RL is "New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information C IE in the Non-Serving RL Preconfiguration Info IE for the RL in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – if the choice of new Serving RL is "New Serving RL in the Node B or New Serving RL Not in the Node B", the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C for the RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – if the Additional E-DCH Non-Serving RL Preconfiguration Setup IE is included, the Node B may include the New non-serving RL E-DCH FDD DL Control Channel Information A IE, the New non-serving RL E-DCH FDD DL Control Channel Information B IE and/or the New non-serving RL E-DCH FDD DL Control Channel Information C IE according to the choice of new Serving RL in Additional E-DCH New non-serving RL E-DCH FDD DL Control Channel Information IE for the additional non serving E-DCH RL in the Non-Serving RL Preconfiguration Info IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD –If the F-TPICH Information IE is included, the Node B shall use this information to allocate resources for the preconfigured F-TPICH channel for this RL in the serving RLS according to TS 25.211 [7].]

[1.28 Mcps TDD –Multi-Carrier E-DCH:]

[1.28Mcps TDD – If the Multi-Carrier E-DCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then the Multi-Carrier E-DCH Information IE defines the new configuration and then:]

– [1.28Mcps TDD – The Node B shall setup the requested E-DCH resource on the uplink frequecies indicated by the the Multi-Carrier E-DCH Information LCR IE.]

– [1.28Mcps TDD – The Node B shall use the corresponding PRXdes_base IE for power control on each uplink frequency according to TS 25.331 [18].]

– [1.28Mcps TDD – If the SNPL Carrier Group Indicator IE is present in the Multi-Carrier E-DCH Information LCR IE, the Node B shall use the information to determine which SNPL Carrier Group each frequency indicated by the UARFCN IE belongs to.]

– [1.28Mcps TDD – If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "Separate Iub transport bearer mode", the Node B shall use this mode in the new configuration and apply separate transport bearers for the MAC-d flows.]

– [1.28Mcps TDD – If the Multi-Carrier E-DCH Transport Bearer Mode LCR IE is set to "E-DCH UL flow multiplexing mode", the Node B shall use this mode in the new configuration and multiplex MAC-d flow received on the different carriers on one Iub transport bearer.]

– [1.28Mcps TDD – If the Separate Iub transport bearer mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the Multi-Carrier E-DCH Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

– [1.28Mcps TDD – If the E-DCH UL flow multiplexing mode is used in the new configuration, then the Node B shall include the Binding ID IE and Transport Layer Address IE in the E-DCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for establishment of a transport bearer for every E-DCH MAC-d flow being established.]

[FDD – UL DPCCH2:]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the UL DPCCH2 Information IE, then:]

– [FDD – if the serving HS-DSCH RL is in the Node B then the Node B shall configure the concerned Node B Communication Context to use a second F-DPCH in the downlink, i.e. with transmission of only the TPC field and a DPCCH2 in the uplink, i.e. with the transmission of only the second pilot and the TPC field on the Serving HS-DSCH Radio Link and the Node B shall activate UL DPCCH2 operation for the radio link according to the information provided in the IE according to ref TS 25.214 [10].]

– [FDD – If the UL DPCCH2 Information IE includes the Extended E-DPCCH Power Offset IE and if the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message, the Node B shall use the value to calculate the E-DPCCH gain factor.]

[FDD – Downlink TPC enhancements:]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Downlink TPC enhancements Information IE, then:]

– [FDD – The NodeB shall, if supported, use the Decimation factor for primary frequency IE and/or the Decimation factor for secondary frequency IE to configure all the radio links using F-DPCH on the related frequency with power control Algorithm 3.]

[FDD – If the TPC slot position in the RL Information is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]

[FDD – If the TPC slot position in the Additional E-DCHCell Information RL Add Req is included in the RADIO LINK ADDITION REQUEST message, the Node B shall, if supported, use it for power control Algorithm 3.]

General:

If the RADIO LINK ADDITION REQUEST message includes the RL Specific DCH Information IE, the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the DCH or the set of co-ordinated DCHs [FDD – for which the Transport Bearer Not Requested Indicator IE was not included].

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for a DCH, then the Node B shall not establish a transport bearer for the concerned DCH and shall include the Transport Bearer Not Setup Indicator IE for every corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for a DCH and:]

– [FDD – if the Node B establishes a transport bearer for the concerned DCH, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the DCH being established.]

– [FDD – if the Node B does not establish a transport bearer for the concerned DCH, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding DCH in the RADIO LINK ADDITION RESPONSE message.]

If the RADIO LINK ADDITION REQUEST message includes the RL Specific E-DCH Information IE, the Node B may use the transport layer addresses and the binding identifiers received from the CRNC when establishing transport bearers for the MAC-d flows of the E-DCHs.

The Node B shall start reception on the new RL(s) after the RLs are successfully established.

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Initial DL DPCH Timing Adjustment Allowed IE, then the Node B may perform an initial DL DPCH Timing Adjustment (i.e. perform a timing advance or a timing delay with respect to the SFN timing) on a Radio Link. In this case, the Node B shall include, for the concerned Radio Link(s), the Initial DL DPCH Timing Adjustment IE in the Radio Link Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Synchronisation Indicator IE, set to "Timing Maintained Synchronisation", the Node B shall use synchronisation procedure B according to subclause 4.3.2.4 in TS 25.214 [10]. The Node B shall select the TPC pattern as if "first RLS indicator" is set to "first RLS" according to subclause 5.1.2.2.1.2 in TS 25.214 [10].]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the F-DPCH Slot Format IE and if the Node B Communication Context is configured to use F-DPCH in the downlink, then the Node B shall use this information to configure the F-DPCH slot format of each RL according to TS 25.211 [7].]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the F-TPICH Information IE in the RL Information IE, the Node B shall use this information to configure the F-TPICH of the RL according to TS 25.211 [7] and TS 25.214 [10].]

[FDD – Radio Link Set Handling]:

[FDD – For each RL not having a common generation of the TPC commands in the DL with another RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH related information for RLs in different RL Sets shall not be common.]

[FDD – For all RLs having a common generation of the TPC commands in the DL with another new or existing RL, the Node B shall assign the RL Set ID IE included in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. In case of E-DCH, the generation of E-HICH information for all RLs in a RL Set shall be common.]

[FDD – After addition of the new RL(s), the UL out-of-sync algorithm defined in TS 25.214 [10] shall, for each of the previously existing and newly established RL Set(s), use the maximum value of the parameters N_OUTSYNC_IND and T_RLFAILURE that are configured in the cells supporting the radio links of the RL Set. The UL in-sync algorithm defined in TS 25.214 [10] shall, for each of the established RL Set(s), use the minimum value of the parameters N_INSYNC_IND, that are configured in the cells supporting the radio links of the RL Set.]

[FDD – For each E-DCH RL which has or can have a common generation of E-RGCH information with another RL (current or future) when the Node B would contain the E-DCH serving RL, the Node B shall include the E-DCH RL Set ID IE in the RADIO LINK ADDITION RESPONSE message. The value of the E-DCH RL Set ID IE shall allow the RNC to identify the E-DCH RLs that have or can have a common generation of E-RGCH information.]

[FDD – Serving HS-DSCH Radio Link Change]:

[FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE, then HS-PDSCH RL ID IE indicates the new Serving HS-DSCH Radio Link:]

– [FDD – In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Serving HS-PDSCH Radio Link.]

– [FDD – The Node B may include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE may contain the HARQ Memory Partitioning Information Extension For MIMO IE.]

– [FDD – The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Information Response IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]

– [FDD – If the Node B Communication Context is configured with Sixtyfour QAM allowed for the serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new configuration, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – HS-DSCH Setup on a New Radio Link at Serving HS-DSCH Radio Link Change:]

[FDD – If the HS-DSCH Information IE is present in the HS-DSCH Serving Cell Change Information IE, then:]

– [FDD – The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]

– [FDD – the HS-DSCH Information IE defines the new HS-DSCH configuration in the Node B to be used on the new HS-DSCH Radio Link.]

– [FDD – The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message. The HARQ Memory Partitioning IE shall either contain the HARQ Memory Partitioning Information Extension For MIMO IE or the Number of Processes IE set to a value higher than "8", if the MIMO Activation Indicator IE or the MIMO with four transmit antennas Activation Indicator IE, or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH Information IE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Puncturing Handling in First Rate Matching Stage IE in the HS-DSCH Information IE , then the Node B shall, if supported, apply the puncturing during first stage rate matching according to the Puncturing Handling in First Rate Matching Stage IE.]

– [FDD – The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any HS-SCCH transmission to this UE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Measurement Power Offset IE in the HS-DSCH Information IE, then the Node B shall use the measurement power offset as described in ref TS 25.214 [10], subclause 6A.2.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HARQ Preamble Mode IE in the HS-DSCH Information IE, then the Node B shall use the indicated HARQ Preamble Mode as described in TS 25.214 [10], if HS-DPCCH ACK/NACK preamble and postamble is supported. Then, in this case, if the mode 1 is applied, the Node B shall include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message. If the HARQ Preamble Mode IE is not included or if the mode 0 is applied, then the Node B shall not include the HARQ Preamble Mode Activation Indicator IE in the HS-DSCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).]

– [FDD – If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the HS-DSCH Radio Link.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size" and if Sixtyfour QAM will not be used, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]

– [FDD – If the UE with enhanced HS-SCCH support indicator IE is included in the HS-DSCH FDD Information IE, then the Node B may use:]

– [FDD – a different HS-SCCH in consecutive TTIs for this UE.]

– [FDD – HS-SCCH orders for the case of HS-SCCH-less operation to this UE.]

– [FDD – If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE the Node B may use the supported HSDPA functions for this UE.]

– [FDD – If the UE Support Indicator Extension IE is included in the HS-DSCH FDD Information IE with the bit UE DTXDRX related HS-SCCH orders uniform behavior indicator set to 0, then the Node B shall, if supported, include the Support of dynamic DTXDRX related HS-SCCH order IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the Priority Queue Information IE in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall, if supported, consider the data of the HSDPA Priority Queue for UE Aggregate Maximum Bit Rate Enforcement.]

– [FDD – If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE, then the Node B shall activate the Single Stream MIMO mode for the HS-DSCH Radio Link.]

– [FDD – If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the Precoder weight set restriction IE in the HS-DSCH FDD Information Response IE in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the CQI Feedback Cycle2 k IE and the CQI Cycle Switch Timer IE is included in HS-DSCH FDD Information IE, then the Node B may use the indicated CQI Feedback Cycle2 k value, the CQI Cycle Switch Timer in HSDPA resources allocation for the UE.]

– [FDD – If the Serving Cell Change CFN IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]

– [FDD – If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.]

– [FDD – If the Serving Cell Change CFN IE is not included into the RADIO LINK ADDITION REQUEST message, then the Node B shall include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the HS-DSCH Information IE is present in the HS-DSCH Serving Cell Change Information IE, then the Node B shall include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Node B needs a bearer re-arrangement, then the Node B may include the Transport Layer Address IE and the Binding ID IE for HS-DSCH MAC-d flow for the serving HS-PDSCH RL into the HS-DSCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If a reset of the MAC-hs is not required the Node B shall include the MAC-hs Reset Indicator IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the requested Serving HS-DSCH Radio Link Change was successful or unsucessful, the Node B shall indicate this in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity HS-SCCH less Information IE, then:]

– [FDD – The Node B shall configure the new Serving HS-DSCH Radio Link for Continuous Packet Connectivity HS-SCCH less operation according to TS 25.214 [10].]

– [FDD – The Node B shall allocate the HS-PDSCH codes needed for HS-SCCH less operation and include the Continuous Packet Connectivity HS-SCCH less Information Response IE in the HS-DSCH Serving Cell Change Information Response IE.]

– [FDD – If at least one of HS-PDSCH Second Code Support IE is set to "True", then the Node B shall include HS-PDSCH Second Code Index IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the HS-DSCH Serving Cell Change Information IE includes the Continuous Packet Connectivity DTX-DRX Information IE, then:]

– [FDD – The Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DTX operation according to TS 25.214 [10].]

– [FDD – If DRX Information IE is included in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

– [FDD – If UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

– [FDD – If Inactivity Threshold for UE DRX Cycle 2 IE is included in the DRX Information IE in the Continuous Packet Connectivity DTX-DRX Information IE, then the Node B shall configure the concerned Node B Communication Context for Continuous Packet Connectivity DRX operation according to TS 25.214 [10].]

[FDD – Secondary Serving HS-DSCH Radio Link Change]:

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Additional HS Cell Information RL Addition IE, then HS-PDSCH RL ID IE indicates the new secondary serving HS-DSCH Radio Link:]

– [FDD – In the new configuration the Node B shall allocate the HS-PDSCH resources for the new Secondary Serving HS-PDSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]

– [FDD – If the Ordinal Number Of Frequency IE is included in the HS-DSCH FDD Secondary Serving Information IE, and the new configuration contains more than one secondary serving HS-DSCH Radio Link, then the Node B shall use this value in the physical layer.]

– [FDD – The Node B shall allocate HS-SCCH codes corresponding to the HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Node B Communication Context is configured with Sixtyfour QAM allowed for the secondary serving HS-DSCH Radio Link and not used in the current configuration and then if the Node B decides to use 64 QAM in the new secondary serving HS-DSCH Radio Link, then it shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the Additional HS Cell Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – Secondary Serving HS-DSCH Setup on a New Radio Link at Secondary Serving HS-DSCH Radio Link Change:]

– [FDD – The Node B shall setup the requested HS-PDSCH resources on the secondary serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]

– [FDD – The HS-DSCH FDD Secondary Serving Information IE defines the new secondary serving HS-DSCH configuration in the Node B to be used on the new secondary serving HS-DSCH Radio Link. Non cell specific secondary serving Radio Link and non cell specific HS-DSCH parameters take the same values as for the serving HS-DSCH cell.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-SCCH Power Offset IE in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may use this value to determine the HS-SCCH power. The HS-SCCH Power Offset should be applied for any secondary serving HS-SCCH transmission to this UE.]

– [FDD – The Node B shall allocate HS-SCCH codes corresponding to the secondary serving HS-DSCH and include the HS-SCCH Specific Secondary Serving Information Response IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Single Stream MIMO Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the Single Stream MIMO mode for the secondary serving HS-DSCH Radio Link.]

– [FDD – If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B may if the value is set to "allowed" use 64 QAM for the secondary serving HS-DSCH Radio Link, and the Node B shall include the SixtyfourQAM DL Usage Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Sixtyfour QAM Usage Allowed Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE with value set to "not allowed", then the Node B shall not use 64 QAM for the secondary serving HS-DSCH Radio Link.]

– [FDD – If Sixtyfour QAM will not be used for the secondary serving HS-DSCH Radio Link, the Node B shall include the HS-DSCH TB Size Table Indicator IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message if it decides to use the octet aligned table defined in TS 25.321 [32] for HS-DSCH Transport Block Size signalling.]

– [FDD – If the Diversity Mode IE is included in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE in the RADIO LINK ADDITION REQUEST message the Node B shall apply cell specific transmit diversity configuration and if the Diversity Mode IE is not set to "None" the Node B shall activate/deactivate the Transmit Diversity for the secondary serving HS-DSCH Radio Link in accordance with the Transmit Diversity Indicator IE in the HS-DSCH FDD Secondary Serving Information IE.]

– [FDD – If the Serving Cell Change CFN IE is included into the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new secondary serving HS-DSCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the HS-PDSCH resources of the old Serving HS-PDSCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]

– [FDD – If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving HS-PDSCH Radio Link, and shall keep active the resources that are allocated for the previous serving HS-PDSCH Radio Link.]

– [FDD – If the requested Secondary Serving HS-DSCH Radio Link Change was successful or unsucessful, the Node B shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the MIMO with four transmit antennas Activation Indicator IE or the Dual Stream MIMO with four transmit antennas Activation Indicator IE is included in the HS-DSCH FDD Secondary Serving Information IE, then the Node B shall activate the MIMO with four transmit antennas mode or Dual Stream MIMO with four transmit antennas mode for the secondary serving HS-DSCH Radio Link and the Node B shall decide the UE reporting configuration (N/M ratio) according to TS 25.214 [10] for MIMO and include the MIMO N/M Ratio IE in the HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – Node B may include the Precoder weight set restriction IE in HS-DSCH FDD Secondary Serving Information Response IE in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – Additional Serving E-DCH Radio Link Change:]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Additional E-DCH Cell Information Addition IE in the Additional E-DCH Cell Information RL Add Req IE and HS-PDSCH RL ID IE the Additional HS Cell Information RL Addition IE, the HS-PDSCH RL ID IE indicates the new Additional Serving E-DCH Radio Link:]

– [FDD – In the new configuration the Node B shall allocate the E-DCH resources for the new additional serving E-DCH Radio Link on the secondary UL frequency. Non cell specific E-DCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]

– [FDD – If the old Additional Serving E-DCH RL is within this Node B, the Node B shall de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link at the activation of the new configuration.]

– [FDD – The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Additional Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message the Serving Grant Value IE and Primary/Secondary Grant Selector IE for the initial grant for the additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE]

– [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE in the Additional E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE.]

– [FDD – If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC, or earlier. In this case, in the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Additional Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the RNC.]

– [FDD – If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.]

– [FDD – If the addition of the requested Additional Serving E-DCH Radio Link was successful but the Additional Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the Additional E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – Multiflow Setup]:

[FDD – If the Multiflow Information IE is present in HS-DSCH FDD Information IE in the RADIO LINK ADDITION REQUEST message, then the Node B shall setup the requested Multiflow operation and then:]

– [FDD – Use Total number of HS-DSCH cells IE to apply the HS-DPCCH format at the physical layer based on the total number of cells provided in this IE.]

– [FDD – Use Role IE to know whether Multiflow cells configured at this Node B are assisting ones or not, for which Node B must read the correspondent part of the HS-DPCCH feedback channel.]

– [FDD – Use MIMO IE to decide whether to apply the MIMO HS-DPCCH format at the physical layer.]

– [FDD – If Timing IE is included, then Node B shall use this information to decide whether Multiflow cells configured at this Node B follow a different HS-DPCCH timing with an offset indicated by this IE.]

– [FDD – If the Max number of HS-SCCH sets per Node B IE is included, then Node B shall use this information on the upper limit for the number HS-SCCH sets allocated and reported back to CRNC.]

– [FDD – If the Assisting Repetition Factors IE is included, then the Node B shall use the values indicated in this IE within the Multiflow configuration.]

[FDD – E-DCH]:

[FDD – If the RADIO LINK ADDITION REQUEST message contains the E-DCH RL Indication IE, set to "E-DCH", in the RL Information IE, then for every such RL:]

– [FDD – The Node B shall setup the E-DCH resources as configured in the Node B Communication Context.]

– [FDD – The Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE for every RL indicated by the E-DCH RL Indication IE, set to “E-DCH” in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]

[FDD – Serving E-DCH Radio Link Change:]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE, then Serving E-DCH RL IE indicates the new Serving E-DCH Radio Link:]

– [FDD – If the new Serving E-DCH RL is in this Node B:]

– [FDD – The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the new Serving E-DCH Radio Link and include these E-RNTI identifiers along with the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the new serving E-DCH RL.]

– [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new/changed configuration and include the new/changed configuration in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK ADDITION RESPONSE message for the new serving E-DCH RL.]

– [FDD – The Node B may include the E-RGCH/E-HICH Channelisation Code IE and/or the E-HICH Signature Sequence IE and/or the E-RGCH Signature Sequence IE or may alternatively include the E-RGCH Release Indicator IE in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message for any of the other E-DCH Radio Links in the Node B Communication Context that have not been included in the E-DCH FDD DL Control Channel Information IE in RL Information Response IE.]

– [FDD – If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. In the new configuration the Node B shall, if applicable, de-allocate the E-AGCH resources of the old Serving E-DCH Radio Link. The Node B shall deactivate those resources at the next coming CFN with a value equal to the value requested by the SRNC.]

– [FDD – If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new serving E-DCH Radio Link.]

– [FDD – If the addition of the requested Serving E-DCH Radio Link was successful but the Serving E-DCH Radio Link change was unsuccessful, the Node B shall indicate this in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – E-DPCH Handling]:

[FDD – If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE it defines the new E-DPCH configuration in the Node B to be used on the new E-DCH Radio Link and, the Node B shall use the new parameters for the related resource allocation operations.]

[FDD – If the E-TFCS Information IE in the E-DPCH Information IE contains the E-DPDCH Power Interpolation IE, the Node B shall use the value to determine the applicable E-DPDCH power formula defined in TS 25.214 [10]. If the E-DPDCH Power Interpolation IE is not present, the Node B shall use the E-DPDCH power extrapolation formula defined in TS 25.214 [10].]

[FDD – If the E-TFCS Information IE in the E-DPCH Information IE contains the E-TFCI Boost Information IE, the Node B shall use the information according to TS 25.214 [10]. If the E-TFCI Boost Information IE is not present, the Node B shall use the E-TFCI BetaEC Boost value "127" in the algorithm defined in TS 25.214 [10].]

[FDD – If the RADIO LINK ADDITION REQUEST message includes an E-DPCH Information IE, which contains the Minimum Reduced E-DPDCH Gain Factor IE, then the Node B shall use the value to determine the applicable minimum gain factor (β_{ed,k,reduced,min}) defined in TS 25.214 [10]. For the case the Minimum Reduced E-DPDCH Gain Factor IE is not available for the Node B Communication Context, the Node B may use the default value defined in TS 25.331 [18].]

[FDD – E-DCH Setup on a new Radio Link:]

[FDD – If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message:]

– [FDD – the E-DCH FDD Information IE defines the new E-DCH FDD configuration in the Node B to be used on the new E-DCH Radio Link.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel information IE in the E-DCH FDD Information IE, then the Node B shall use this information to optimise MAC-e scheduling decisions.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes UE Aggregate Maximum Bit Rate Enforcement Indicator IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE, then the Node B shall, if supported, consider the data of the related E-DCH Logical Channel for UE Aggregate Maximum Bit Rate Enforcement.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32])

– [FDD – If the TNL QoS IE is included for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the Node B shall use this information for the related resource allocation operation.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE indicating that the Serving E-DCH RL is in this Node B:]

– [FDD – The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the E-DCH HARQ process allocation for 2ms TTI for scheduled and/or non-scheduled transmission shall be changed, the Node B shall allocate resources according to the new configuration and include the new configuration in the E-DCH FDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the Default Serving Grant in DTX Cycle 2 IE in the RADIO LINK ADDITION RESPONSE message for the serving E-DCH RL.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow the Node B shall use this information for the related resource allocation operation.]

– [FDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Non-Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants being configured for that E-DCH MAC-d flow and shall use the information within the HARQ Process Allocation For 2ms Non-Scheduled Transmission Grant IE, if included, for the related resource allocation operation.]

– [FDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type is indicated as being "E-DCH Scheduled Transmission Grant" for an E-DCH MAC-d flow the Node B shall assume scheduled grants being configured for that E-DCH MAC-d flow.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Bundling Mode Indicator IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flow Specific Information IE in the E-DCH FDD Information IE and the Bundling Mode Indicator IE is set to "Bundling" and the E-TTI IE is set to "2ms", then the Node B shall use the bundling mode for the E-DCH UL data frames for the related MAC-d flow, otherwise the Node B shall use the non-bundling mode for the E-DCH UL data frames for the related MAC-d flow.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Maximum Bitrate IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE, then if the Node B could not decode the E-DPCCH/E-DPDCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Reference Power Offset IE, then the Node B may use this value as a default HARQ power offset if it is not able to decode the MAC-e PDU and to determine the value of the actual HARQ power offset.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-AGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-AGCH power. The E-AGCH Power Offset should be applied for any E-AGCH transmission to this UE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-RGCH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-RGCH power for the RL. The E-RGCH Power Offset should be applied for any E-RGCH transmission to this UE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-HICH Power Offset IE in the RL Specific E-DCH Information IE, then the Node B may use this value to determine the E-HICH power for the RL. The E-HICH Power Offset should be applied for any E-HICH transmission to this UE.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE, then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the UPH Filtering Measurement Forwarding Request IE, then the Node B shall use this instruction to handle the UE UPH filtering measurement forwarding.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the SixteenQAM UL Operation Indicator IE, the Node B shall activate/deactivate SixteenQAM UL Operation for the RL in accordance with the SixteenQAM UL Operation Indicator IE.]

– [FDD – If SixteenQAM UL Operation is activated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 2 according to (TS 25.321 [32]. If SixteenQAM UL Operation is deactivated, then the Node B shall base the handling of the Relative Grant signalling on Scheduling Grant Table 1 according to (TS 25.321 [32].]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer shall not be Established" for an E-DCH MAC-d flow, then the Node B shall not establish a transport bearer for the concerned E-DCH MAC-d flow and shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE set to "Transport Bearer may not be Established" for an E-DCH MAC-d flow and:]

– [FDD – if the Node B establishes a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of a transport bearer for the E-DCH MAC-d flow being established.]

– [FDD – if the Node B does not establish a transport bearer for the concerned E-DCH MAC-d flow, the Node B shall include the Transport Bearer Not Setup Indicator IE for the corresponding E-DCH MAC-d flow in the RADIO LINK ADDITION RESPONSE message.]

[FDD – Additional E-DCH Setup:]

[FDD – If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is "Setup", then the Additional E-DCH Cell Information Setup IE defines the new configuration and then:]

– [FDD – If the C-ID IE is included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the C-ID IE indicates the cell in which the additional E-DCH shall be setup]

– [FDD – The Node B shall setup the Additional E-DCH on the secondary uplink frequency and setup the requested Additional E-DCH resources on the Radio Links and in the cells indicated by the E-DCH Additional RL ID IE and the C-ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE.]

– [FDD – If the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the E-DCH Additional RL ID IE indicates the existing RL on which the Additional E-DCH shall be setup.]

– [FDD – The Node B shall setup the Additional E-DCH on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE]

– [FDD – The Node B shall use for the non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters the same values as for the corresponding cell of the Primary uplink frequency. The Node B shall, if supported, use the Dual Cell E-DCH Operation Enhancements Information IE for the Secondary uplink frequency if it is included in the Additional E-DCH FDD Information IE in the Additional E-DCH FDD Setup Information IE.]

– [FDD – If the DL Power Balancing Information IE and/or the Minimum Reduced E-DPDCH Gain Factor IE are present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If the Secondary UL Frequency Activation State IE is present in the Multicell E-DCH Information IE in the Additional E-DCH FDD Setup Information IE, the Node B shall use the information as initial activation state of the Radio Links on the secondary uplink frequency.]

– [FDD – If the F-DPCH Slot Format IE is present in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If the Primary CPICH Usage For Channel Estimation IE, the Secondary CPICH Information IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Setup IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Maximum Bitrate IE, the E-DCH Processing Overload Level IE, the E-DCH Minimum Set E-TFCI IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information2 IE are present in the Additional E-DCH FDD Information IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If activation of power balancing for the Additional E-DCH RL by the RADIO LINK ADDITION REQUEST message is supported by the Node B, the Node B shall include the DL Power Balancing Activation Indicator IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – For each Additional E-DCH RL not having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message a value that uniquely identifies the RL Set within the Node B Communication Context. And the generation of E-HICH related information for Additional E-DCH RLs in different RL Sets shall not be common.]

– [FDD – For all Additional E-DCH RLs having a common generation of the TPC commands in the DL with another Additional E-DCH RL, the Node B shall assign the RL Set ID IE included in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message the same value. This value shall uniquely identify the RL Set within the Node B Communication Context. And the generation of E-HICH information for all Additional E-DCH RLs in a RL Set shall be common.]

– [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – If the Additional Serving E-DCH Radio Link is configured in the Node B, then:]

– [FDD – The Node B shall allocate a primary E-RNTI identifier or a secondary E-RNTI identifier or both for the corresponding RL and include these E-RNTI identifiers and the channelisation code of the corresponding E-AGCH in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – The Node B may include the Serving Grant Value IE and Primary/Secondary Grant Selector IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message for the initial grant for the Additional serving E-DCH RL and may include the Default Serving Grant in DTX Cycle 2 IE.]

– [FDD – If the Serving Cell Change CFN IE is included in the RADIO LINK ADDITION REQUEST message, then the Node B shall activate the resources that are allocated for the new additional serving E-DCH Radio Link at the next coming CFN with a value equal to the value requested by the RNC. If the Serving Cell Change CFN IE is not included then the Node B shall activate immediately the resources that are allocated for the new additional serving E-DCH Radio Link.]

[FDD – Additional E-DCH RL Addition:]

[FDD – If the Additional E-DCH Cell Information RL Add Req IE is present in the RADIO LINK ADDITION REQUEST message and the choice of Setup Or Addition Of E-DCH On Secondary UL Frequency is "Addition", then the Additional E-DCH Cell Information Addition IE defines the new configuration and then:]

– [FDD – The Node B shall setup the requested E-DCH resources as requested, or as configured in the Node B Communication Context, on the Radio Links indicated by the E-DCH Additional RL ID IE in the Additional E-DCH RL Specific Information To Add IE. Non cell specific Radio Link related parameters and non cell specific E-DPCH, UL DPCH, E-DCH and F-DPCH parameters shall take the same values as for the corresponding cell of the Primary uplink frequency.]

– [FDD – if the Multicell E-DCH Information IE is included and contains the Minimum Reduced E-DPDCH Gain Factor IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.]

– [FDD – I f the Additional E-DCH FDD Information IE is included and contains the HARQ Process Allocation For 2ms Scheduled Transmission Grant IE, the E-DCH Minimum Set E-TFCI IE, the E-DCH Maximum Bitrate IE, the E-DCH Processing Overload Level IE, the Implicit Grant handling IE, the Minimum TEBS threshold IE and/or the DTX Information IE, the Node B shall use the information in the same way as for the information used on the Primary uplink frequency.]

– [FDD – If the Initial DL Transmission Power IE, the Maximum DL Power IE, the Minimum DL Power IE and/or the F-DPCH Slot Format IE are present in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If the DL Reference Power IE, the E-AGCH Power Offset IE, the E-RGCH Power Offset IE and/or the E-HICH Power Offset IE are present in the Multicell E-DCH RL Specific Information IE in the Additional E-DCH RL Specific Information To Add IE, the Node B shall use the information same way as in the information is used on Primary uplink frequency.]

– [FDD – If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing Additional E-DCH RL(s) and the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IE, the Node B shall activate the power balancing and use the DL Reference Power IE for the power balancing procedure in the new Additional E-DCH RL(s), if activation of power balancing by the RADIO LINK ADDITION REQUEST message is supported, according to subclause 8.3.7. In this case, the Node B shall include the DL Power Balancing Activation Indicator IE in the E-DCH Additional RL Specific Information Response IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message. If the Node B starts the DL transmission and the activation of the power balancing at the same CFN, the initial power of the power balancing, i.e. P_initshall be set to the power level indicated by the Initial DL Transmission Power IE (if received) in the Additional E-DCH RL Specific Information To Add IE or the decided DL TX power level on each DL channelisation code of an Additional E-DCH RL based on power level of existing Additional E-DDCH RLs.]

– [FDD – For each Additional E-DCH RL which has or can have a common generation of E-RGCH information with another Additional E-DCH RL (current or future) when the Node B would contain the Additional E-DCH serving RL, the Node B shall set a same value to the E-DCH RL Set ID IE for the Additional E-DCH RL in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

– [FDD – For every additional E-DCH RL indicated in the Additional E-DCH RL Specific Information To Add IE in the Additional E-DCH FDD Setup Information IE the Node B may include the E-AGCH And E-RGCH/E-HICH FDD Scrambling Code IE and shall include the E-RGCH/E-HICH Channelisation Code IE and the corresponding E-HICH Signature Sequence IE and the Node B may include the corresponding E-RGCH Signature Sequence IE for each Additional E-DCH RL in the E-DCH FDD DL Control Channel Information IE in the Additional E-DCH FDD Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION RESPONSE message.]

[FDD – E-DCH decoupling operation]

[FDD – If the E-DCH Decoupling Indication IE is present in the RADIO LINK ADDITION REQUEST message, then the Node B shall if supported use this indication for the E-DCH decoupling operation.]

[FDD – Radio Links without DPCH/F-DPCH operation]

[FDD – If the Radio Links without DPCH/F-DPCH Indication IE is present in the RADIO LINK ADDITION REQUEST message:]

– [FDD – The Node B shall if supported start operation with Radio Links without DPCH/F-DPCH.]

[TDD – HS-DSCH Setup]:

[TDD – If the HS-DSCH Information IE is present in the RADIO LINK ADDITION REQUEST message, then]:

– [TDD – The Node B shall setup the requested HS-PDSCH resources on the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE.]

– [TDD – The Node B shall include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE, then the Node B shall use the indicated format in user plane frame structure for HS-DSCH channels (TS 25.435 [24]) and MAC-hs (TS 25.321 [32]).]

– [TDD – The Node B shall include in the RADIO LINK ADDITION RESPONSE message the Binding ID IE and Transport Layer Address IE for establishment of transport bearer for every HS-DSCH MAC-d flow being established.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the HS-DSCH Information IE for an HS-DSCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned HS-DSCH MAC-d flow. If the TNL QoS IE is included for a MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink between the Node B and the CRNC for the related MAC-d flow.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the MAC-hs Guaranteed Bit Rate IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to optimise MAC-hs scheduling decisions for the related HSDPA Priority Queue.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the Discard Timer IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall use this information to discard out-of-date MAC-hs SDUs from the related HSDPA Priority Queue.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, then the Node B shall ignore the SID IE and MAC-d PDU Size IE in the MAC-d PDU Size Index IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related HSDPA Priority Queue.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE, the DL RLC PDU Size Format IE may be used by the Node B to determine the allocated capacity on user plane as described in TS 25.435 [24].]

– [TDD – The Node B shall include the HS-DSCH Initial Capacity Allocation IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message for every HS-DSCH MAC-d flow being established, if the Node B allows the CRNC to start transmission of MAC-d PDUs before the Node B has allocated capacity on user plane as described in TS 25.435 [24]. If RADIO LINK ADDITION REQUEST message includes HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE set to "Flexible MAC-d PDU Size", then Node B shall only set in the HS-DSCH Initial Capacity Allocation IE the values for the peer of Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE to the values of the corresponding peer received in RADIO LINK ADDITION REQUEST in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE for a Priority Queue including Scheduling Priority Indicator IE and Maximum MAC-d PDU Size Extended IE.]

– [TDD – The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD – HS-SCCH Specific Information Response IE] [1.28Mcps TDD – HS-SCCH Specific Information Response LCR IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the TSN-Length IE is included in the HS-DSCH TDD Information IE, then the IE is used to indicate the TSN bits applied to the MAC-hs PDU frame.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Number of Supported Carriers IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information to allocate HSDPA resources over multiple carriers for the UE.]

– [1.28Mcps TDD – For a multi-frequency cell, if the RADIO LINK ADDITION REQUEST message includes the Multi-carrier HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B shall use this information together with the HS-DSCH Physical Layer Category IE in the UE Capabilities Information IE in the HS-DSCH Information IE to allocate HSDPA resources over multiple carriers for the UE.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE, the Node B may use this information in HSDPA resources allocation for the UE.]

– [1.28Mcps TDD – If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH over multiple carriers and include the HS-SCCH Specific Information Response LCR per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B shall include the HARQ Memory Partitioning per UARFCN IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the Node B allows UE to apply HSDPA resources distributed over multiple carriers, the Node B may indicate the number of carriers actually used by the UE and include the Multi-Carrier number IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UsedFrequency IE in the HS-SCCH Specific Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the Node B allows UE to use HSDPA resources distributed over multiple carriers, the Node B may include the UARFCN IE in the HS-SCCH Specific Information Response LCR per UARFCN IE in the RADIO LINK ADDITION RESPONSE message.]

[1.28 Mcps TDD – If the MIMO Activation Indicator IE is included in the HS-DSCH TDD Information IE, then, the Node B shall activate the MIMO mode for the HS-DSCH Radio Link, decide the SF mode for HS-PDSCH dual stream and include the MIMO SF Mode for HS-PDSCH dual stream IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[TDD – Intra-Node B Serving HS-DSCH Radio Link Change]:

[TDD – If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL ID IE, this indicates the new Serving HS-DSCH Radio Link]:

– [TDD – The Node B may include the HARQ Memory Partitioning IE in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [TDD – The Node B shall allocate HS-SCCH parameters corresponding to the HS-DSCH and include the [3.84Mcps TDD – HS-SCCH Specific Information Response IE] [1.28Mcps TDD – HS-SCCH Specific Information Response LCR IE] [7.68Mcps TDD – HS-SCCH Specific Information Response 7.68Mcps IE] in the HS-DSCH TDD Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[TDD – E-DCH]:

[TDD – If the [3.84Mcps TDD – E-DCH Information IE][1.28Mcps TDD – E-DCH Information 1.28Mcps IE] [7.68Mcps TDD – E-DCH Information 7.68Mcps IE] is present in the RADIO LINK ADDITION REQUEST message:]

– [TDD – The Node B shall setup the requested E-DCH resources on the Radio Link indicated by the E-DCH Serving RL IE.]

– [TDD – If the TNL QoS IE is included in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow and if ALCAP is not used, the TNL QoS IE may be used by the Node B to determine the transport bearer characteristics to apply in the uplink for the related MAC-d flow.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and Binding ID IE in the E-DCH MAC-d Flows Information TDD IE for an E-DCH MAC-d flow, then the Node B may use the transport layer address and the binding identifier received from the CRNC when establishing a transport bearer for the concerned E-DCH MAC-d flow.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH MAC-d Flow Multiplexing List IE for an E-DCH MAC-d flow in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation.]

– [TDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Non-scheduled" for an E-DCH MAC-d flow the Node B shall assume non-scheduled grants are configured for that E-DCH MAC-d flow and shall use the information within the [3.84Mcps TDD – E-DCH Non-scheduled Grant Information TDD IE] [1.28Mcps TDD – E-DCH Non-scheduled Grant Information LCR TDD IE] [7.68Mcps TDD – E-DCH Non-scheduled Grant Information 7.68Mcps TDD IE], if included, for the related resource allocation operation.]

– [TDD – If in the RADIO LINK ADDITION REQUEST message the E-DCH Grant Type IE in the E-DCH MAC-d Flows Information TDD IE is set to "Scheduled" the Node B shall assume that it may issue scheduled grants for the concerned E-DCH MAC-d flow.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the MAC-es Guaranteed Bit Rate IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, then the Node B shall use this information to optimise MAC-e scheduling decisions for the related queue.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the MAC-es Maximum Bit Rate LCR IE in the E-DCH Logical Channel Information IE in the E-DCH MAC-d Flows Information TDD IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a E-DCH Logical Channel in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, then the Node B shall ignore the MAC-d PDU Size IE in the MAC-d PDU Size List IE and use Maximum MAC-d PDU Size Extended IE to optimise capacity allocation for the related E-DCH Logical Channel and use the indicated format in user plane frame structure for E-DCH channels (TS 25.435 [24]) and MAC (TS 25.321 [32]).]

– [3.84Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate IE in the E-DCH TDD Information IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Physical Layer Category LCR IE or Extended E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

– [7.68Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH TDD Maximum Bitrate 7.68Mcps IE in the E-DCH TDD Information 7.68Mcps IE for an E-DCH, the Node B shall use this information for the related resource allocation operation, and when applicable, for E-DCH scheduling.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Processing Overload Level IE in the [3.84Mcps TDD – E-DCH TDD Information IE] [7.68Mcps TDD – E-DCH TDD Information 7.68Mcps IE] [1.28Mcps TDD – E-DCH TDD Information LCR IE], then if the Node B could not decode the E-PUCH for the last consecutive number of TTIs, indicated in the E-DCH Processing Overload Level IE, because of processing issue, the Node B shall notify the RNC by initiating the Radio Link Failure procedure.]

– [TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Power Offset for Scheduling Info IE in the [3.84Mcps TDD – E-DCH TDD Information IE] [1.28Mcps TDD – E-DCH TDD Information LCR IE] [7.68Mcps TDD – E-DCH TDD Information 7.68Mcps IE], then the Node B shall use this value as a power offset for the transmission of scheduling information without any MAC-d PDUs.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Maximum Number of Retransmission for Scheduling Info LCR IE and the E-DCH Retransmission timer for Scheduling Info LCR IE in the E-DCH TDD Information LCR IE, then the Node B shall use these parameters for the transmission of scheduling information without any MAC-d PDUs.]

– [TDD – The Node B shall allocate an E-RNTI identifier and include the E-RNTI identifier and the E-AGCH(s) assigned in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Multi-Carrier E-DCH Physical Layer Category LCR IE in the E-DCH TDD Information LCR IE, the Node B shall use this information for the related resource allocation operation, and when applicable, for multi-carrier E-DCH scheduling.]

– [1.28Mcps TDD – If the UE TS0 Capability LCR IE in the UE Capabilities Information IE in the HS-DSCH Information IE is not present and if the RADIO LINK ADDITION REQUEST message includes the UE TS0 Capability LCR IE in the E-DCH TDD Information LCR IE, the Node B can use this information to allocate the downlink resources for the UE according to TS 25.306 [33].]

[TDD – Intra-Node B Serving E-DCH Radio Link Change]:

[TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE, this indicates the new Serving E-DCH Radio Link]:

– [TDD – The Node B shall allocate E-AGCH parameters [1.28Mcps TDD – E-HICH parameters] corresponding to the E-DCH and include the E-AGCH Specific Information Response TDD IE, [1.28Mcps TDD – E-HICH Specific Information Response 1.28Mcps TDD IE] in the E-DCH Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

[1.28 Mcps TDD – Continuous Packet Connectivity Handling]:

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the Continuous Packet Connectivity DRX Information LCR IE, then the Node B shall take account into these parameters to decide the DRX operation related parameters and configure the concerned Node B Communication Context for DRX operation according to TS 25.224 [21] and include the parameter(s) in the Continuous Packet Connectivity DRX Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]

[1.28 Mcps TDD – If the Inactivity Threshold for UE DRX Cycle Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the Inactivity Threshold for UE DRX Cycle according to TS 25.224 [21].]

[1.28 Mcps TDD – If the Enabling Delay Ext IE is included in the Continuous Packet Connectivity DRX Information LCR IE, then the Node B may use this value to determine the beginning of uplink transmission in the new configuration according to TS 25.224 [21].]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Semi-Persistent scheduling Information LCR IE, then:]

– [1.28 Mcps TDD – The Node B shall configure the Serving HS-DSCH Radio Link indicated by the HS-PDSCH RL ID IE for HS-DSCH Semi-Persistent scheduling operation according to TS 25.224 [21].]

– [1.28 Mcps TDD – The Node B shall allocate the HS-SICH information needed for HS-DSCH Semi-Persistent scheduling operation and include the HS-DSCH Semi-Persistent scheduling Information Response LCR IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28 Mcps TDD – If the HS-DSCH Semi-Persistent Resource Reservation Indicator IE is included in the HS-DSCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated HS-PDSCH Semi-persistent resource IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28 Mcps TDD – The Node B shall include the Buffer Size for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]

– [1.28 Mcps TDD – The Node B shall include the Number of Processes for HS-DSCH Semi-Persistent scheduling IE in the RADIO LINK SETUP RESPONSE message.]

[1.28 Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Semi-Persistent scheduling Information LCR IE, then:]

– [1.28 Mcps TDD – The Node B shall configure the Serving E-DCH Radio Link indicated by the E-DCH Serving RL IE for E-DCH Semi-Persistent scheduling operation according to TS 25.224 [21].]

– [1.28 Mcps TDD – If the E-DCH Semi-Persistent Resource Reservation Indicator IE is included in the E-DCH Semi-Persistent scheduling Information LCR IE, then the Node B shall include Allcoated E-DCH Semi-persistent resource IE in the RADIO LINK ADDITON RESPONSE message.]

[1.28 Mcps TDD – MU-MIMO Handling:]

[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message includes the MU-MIMO Information IE, then:]

– [1.28 Mcps TDD – The Node B can activate MU-MIMO operation on Uplink and/or Downlink indicated by the MU-MIMO indicator IE and shall include the MU-MIMO Information Response IE in the RADIO LINK ADDITION RESPONSE message.]

– [1.28 Mcps TDD – If the Standalone Midamble Channel Information IE is included in the MU-MIMO Information IE, then the Node B shall configure the concerned Node B Communication Context for standalone midamble related operation according to TS 25.224 [21].]

– [1.28 Mcps TDD – If the Standalone Midamble Channel Information request IE is included in the MU-MIMO Information IE, if the Node B will use MU-MIMO and if the Node B can allocate the standalone midamble resource, then the Node B shall include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK ADDITION RESPONSE message, else the Node B shall not include the Standalone Midamble Channel Information IE in the MU-MIMO Information Response IE in the RADIO LINK ADDTION RESPONSE message].

[1.28Mcps TDD – Non-rectangular resource operation:]

[1.28Mcps TDD – If the RADIO LINK ADDITION REQUEST message contains the UE support of non-rectangular resource allocation IE, the Node B shall, if supported, use this information to determine whether includes the Non-rectangular resource allocation indicator IE and the Non-rectangular resource timeslot set IE or not.]

Response Message:

If all requested RLs are successfully added, the Node B shall respond with a RADIO LINK ADDITION RESPONSE message.

After sending the RADIO LINK ADDITION RESPONSE message, the Node B shall continuously attempt to obtain UL synchronisation on the Uu interface.

For each RL for which the Delayed Activation IE is not included in the RADIO LINK ADDITION REQUEST message, the Node B shall:

– [FDD – start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16].]

– [TDD – start transmission on the new RL immediately as specified in TS 25.427 [16].]

For each RL for which the Delayed Activation IE is included in the RADIO LINK ADDITION REQUEST message, the Node B shall:

– if the Delayed Activation IE indicates "Separate Indication":

– not start any DL transmission for the concerned RL on the Uu interface;

– if the Delayed Activation IE indicates "CFN":

– [FDD – start transmission on the DL DPDCH(s) of the new RL as specified in TS 25.427 [16], however never before the CFN indicated in the Activation CFN IE.]

– [TDD – start transmission on the new RL at the CFN indicated in the Activation CFN IE as specified in TS 25.427 [16].]

8.3.1.3 Unsuccessful Operation

Figure 29: Radio Link Addition procedure: Unsuccessful Operation

If the establishment of at least one radio link is unsuccessful, the Node B shall respond with a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the Cause IE.

[FDD – If some RL(s) were established successfully, the Node B shall indicate this in the RADIO LINK ADDITION FAILURE message in the same way as in the RADIO LINK ADDITION RESPONSE message.]

[FDD – If the RADIO LINK ADDITION REQUEST contains a C-ID IE indicating that a Radio Link must be established on a Cell where DPC Mode change is not supported and DPC Mode can be changed for the relevant Node B Communication Context, the Node B shall consider the procedure as failed for the concerned Radio Link and shall respond with a RADIO LINK ADDITION FAILURE with the appropriate cause value ("DPC Mode change not supported").]

[FDD – If the requested Serving HS-DSCH Radio Link Change was successful, or if the addition of the requested serving HS-DSCH Radio Link was successful or existed already but the Serving HS-DSCH Radio Link change was unsucessful, the Node B shall indicate this in the HS-DSCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.]

[FDD – If the requested secondary serving HS-DSCH Radio Link Change was successful, or if the addition of the requested secondary serving HS-DSCH Radio Link was successful or existed already but the secondary serving HS-DSCH Radio Link change was unsucessful, the Node B shall indicate this in the HS-DSCH Secondary Serving Cell Change Information Response IE in the Additional HS Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.]

[FDD – If the requested Serving E-DCH Radio Link Change was successful, or if the addition of the requested serving E-DCH Radio Link was successful or existed already but the Serving E-DCH Radio Link change was unsucessful, the Node B shall indicate this in the E-DCH Serving Cell Change Information Response IE in the RADIO LINK ADDITION FAILURE message.]

[FDD – If the requested additional serving E-DCH Radio Link Change was successful, or if the addition of the requested additional serving E-DCH Radio Link was successful or existed already but the additional serving E-DCH Radio Link change was unsucessful, the Node B shall indicate this in the Additional E-DCH Serving Cell Change Information Response IE in the Additional E-DCH Cell Information Response RL Add IE in the RADIO LINK ADDITION FAILURE message.]

Typical cause values are as follows:

Radio Network Layer Cause

– Combining not supported

– Combining Resources not available

– Requested Tx Diversity Mode not supported

– UL SF not supported

– DL SF not supported

– Reconfiguration CFN not elapsed

– CM not supported

– [FDD – DPC Mode change not supported]

– Delayed Activation not supported

– [FDD – Continuous Packet Connectivity DTX-DRX operation not available]

– [FDD – Continuous Packet Connectivity UE DTX Cycle not available]

– [FDD – MIMO not available]

– [FDD – SixtyfourQAM DL and MIMO Combined not available]

– [FDD – Multi Cell operation not available.]

– [1.28Mcps TDD- MIMO not available]

– [1.28Mcps TDD – SixtyfourQAM DL and MIMO Combined not available]

– [FDD – TX diversity for MIMO UE on DL Control Channels not available]

– [FDD – Single Stream MIMO not available]

– [FDD – Multi Cell operation with MIMO not available.]

– [FDD – Multi Cell operation with Single Stream MIMO not available.]

– [FDD – Cell Specific Tx Diversity Handling For Multi Cell Operation Not Available]

– [FDD – Multi Cell E-DCH operation not available]

– [FDD – Frequency Specific Compressed mode operation not available]

– [FDD – UL CLTD operation not available]

– [FDD – MIMO with four transmit antennas not available]

– [FDD – Dual Stream MIMO with four transmit antennas not available]

– [FDD – Multiflow operation not available]

– [FDD – SixtyfourQAM UL operation not available]

– [FDD – UL MIMO operation not available]

– [FDD – UL MIMO and SixteenQAM operation not available]

– [FDD – UL MIMO and SixtyfourQAM operation not available]

– [FDD – E-DCH decoupling operation not available]

– [FDD – Radio Links without DPCH/F-DPCH operation not available]

– [FDD – UL DPCCH2 operation not available]

– [FDD – Downlink TPC enhancements operation not available]

– [FDD – Dual Cell E-DCH operation enhancements with 10ms and 10ms TTI operation not available]

– [FDD – Dual Cell E-DCH operation enhancements with different TTI operation not available]

Transport Layer Cause

– Transport Resources Unavailable

Miscellaneous Cause

– O&M Intervention

– Control processing overload

– HW failure

8.3.1.4 Abnormal conditions

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Compressed Mode Deactivation Flag IE with the value ”Deactivate” when compressed mode is active for the existing RL(s), and at least one of the new RL is added in a cell that has the same UARFCN (both UL and DL) of at least one cell with an already existing RL and frequency specific compressed mode is not supported, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM settings".]

[FDD – If the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Individual" in the existing RL(s) and if the DL Reference Power IEs are included in the RL Information IE but the DL Reference Power IE is not present for each RL in the RL Information IE, the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the DL Reference Power IEs in the RL Information IE but the power balancing is not active in the existing RL(s) or the power balancing is active with the Power Balancing Adjustment Type of the Node B Communication Context set to "Common" in the existing RL(s), the Node B shall regard the Radio Link Addition procedure as failed and shall respond with a RADIO LINK ADDITION FAILURE message with the cause value "Power Balancing status not compatible".]

If the RADIO LINK ADDITION REQUEST message includes the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE or RL Specific E-DCH Information IE included in the RL Information IE for a specific RL [FDD – and the E-DCH RL is already configured in the Node B] and the Diversity Control Field IE is set to "Must", the Node B shall regard the Radio Link Addition procedure as failed and respond with the RADIO LINK ADDITION FAILURE message.

If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "May", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.

If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in the RL Specific DCH Information IE in the RL Information IE for a specific RL and the Diversity Control Field IE is set to "Must Not", the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.

If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE in [FDD – the RL Specific E-DCH Information IE in the RL Information IE for the first E-DCH RL][TDD – the E-DCH MAC-d Flows Information TDD IE], the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK SETUP FAILURE message.

If ALCAP is not used, if the RADIO LINK ADDITION REQUEST message does not include the Transport Layer Address IE and the Binding ID IE for an HS-DSCH MAC-d Flow in the HS-DSCH MAC-d Flows Information IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.

If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

[1.28Mcps TDD – For a multi-frequency cell, if the RADIO LINK ADDITION REQUEST message does not include the UARFCN IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.]

[1.28Mcps TDD – For a single frequency cell, if the RADIO LINK ADDITION REQUEST message includes the UARFCN IE, the Node B shall reject the Radio Link Addition procedure and respond with the RADIO LINK ADDITION FAILURE message.]

[FDD – If the concerned Node B Communication Context is configured to use DPCH in downlink and if a transmission gap pattern sequence is active with an SF/2 downlink compressed mode method and the RADIO LINK ADDITION REQUEST message does not contain the transmission gap pattern sequence code information for any new radio link, the Node B shall reject the Radio Link Addition procedure using the RADIO LINK ADDITION FAILURE message with the cause value "Invalid CM Settings".]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the HS-DSCH Serving Cell Change Information IE but not the HS-DSCH FDD Information IE and the Node B Communication Context is not configured for HS-DSCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Serving E-DCH RL IE but the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Serving Cell Change CFN IE but neither the Serving E-DCH RL IE nor HS-DSCH Serving Cell Change Information IE is included into, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the E-DCH FDD Information IE is present in the RADIO LINK ADDITION REQUEST message, but the E-DPCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH RL Indication IE set to "E-DCH", but no E-DCH FDD Information IE, and the Node B Communication Context is not configured for E-DCH, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH FDD Information IE but no E-DCH RL Indication IE set to "E-DCH", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message includes the HS-PDSCH RL-ID IE not equal to the RL ID IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message includes the E-DCH Serving RL IE not equal to the RL ID IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message contains the HS-DSCH Information IE and if the Priority Queues associated with the same HS-DSCH MAC-d Flow ID IE have the same Scheduling Priority Indicator IE value, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

If the RADIO LINK ADDITION REQUEST message includes the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information] and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information] has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information] and the HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information] has the value "Flexible MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

[FDD – If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message contains, for at least one logical channel, the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE, and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information TDD IE in the E-DCH Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for HS-DSCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[TDD – If the RADIO LINK ADDITION REQUEST message contains the Transport Layer Address IE or the Binding ID IE when establishing a transport bearer for E-DCH MAC-d flow being added, and not both are present for a transport bearer intended to be established, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

If the RADIO LINK ADDITION REQUEST message does not contain the E-DCH Decoupling Indication IE but contains the HS-PDSCH RL ID IE [FDD – in the HS-DSCH Serving Cell Change Information IE] and/or Serving E-DCH RL IE, and if both HS-DSCH and E-DCH are configured in the Node B but the Serving HS-DSCH Radio Link and the Serving E-DCH Radio Link are not in the same cell, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

[FDD – If the RADIO LINK ADDITION REQUEST message contains the HS-DSCH Serving Cell Change Information IE and the E-DPCH Information IE which includes the HS-DSCH Configured Indicator IE set as “HS-DSCH not configured” then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Transport Bearer Not Requested Indicator IE for a DCH but the DCH is configured to be included as a part of the downlink CCTrCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the MIMO Activation Indicator IE, Sixtyfour QAM Usage Allowed Indicator IE set to "Allowed", the Additional HS Cell Information RL Addition IE, the Single Stream MIMO Activation Indicator IE, the MIMO with four transmit antennas Activation Indicator IE and/or the Dual Stream MIMO with four transmit antennas Activation Indicator IE but does not contain the HS-DSCH MAC-d PDU Size Format IE set to "Flexible MAC-d PDU Size", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Serving E-DCH RL ID IE but contains the Transport Bearer Not Requested Indicator IE or there is at least one E-DCH MAC-d flow which transport bearer was not configured in the Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message includes the Transport Bearer Not Requested Indicator IE for a DCH for a specific RL and the specific RL is combined with the existing RL which the transport bearer is established for the DCH in Node B, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and if the HS-DSCH is not configured in the Node B Communication Context and the HS-DSCH Information IE is not present, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

If the RADIO LINK ADDITION REQUEST message includes DL RLC PDU Size Format IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information IE] set to “Flexible RLC PDU Size”, HS-DSCH MAC-d PDU Size Format IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information IE] has the value "Indexed MAC-d PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

If the RADIO LINK ADDITION REQUEST message does not include the Maximum MAC-d PDU Size Extended IE for a Priority Queue in the HS-DSCH MAC-d Flows Information IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information IE] and the DL RLC PDU Size Format IE in the HS-DSCH Information IE [FDD – in the HS-DSCH Serving Cell Change Information IE] has the value "Flexible RLC PDU Size", the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.

[FDD – If the RADIO LINK ADDITION REQUEST message contains a MIMO Activation Indicator IE and a Single Stream MIMO Activation Indicator IE in the HS-DSCH FDD Information IE in the HS-DSCH Serving Cell Change Information IE or in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Diversity Mode IE in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE and the secondary serving HS-DSCH is already configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the secondary serving HS-DSCH is not configured in the Node B Communication Context and if the RADIO LINK ADDITION REQUEST message contains in the HS-DSCH FDD Secondary Serving Information IE in the Additional HS Cell Information RL Addition IE the Diversity Mode IE not set to "None" but not the Transmit Diversity Indicator or contains the Transmit Diversity Indicator but not the Diversity Mode IE not set to "None", then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and if the E-DPCH Information IE is not present or the E-DPCH Information was not configured in the Node B Communication Context, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and there exist a logical channel for which the Maximum MAC-d PDU Size Extended IE in the E-DCH MAC-d Flows Information IE in the E-DCH FDD Information IE is not present, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional E-DCH Cell Information RL Add Req IE and the C-ID IE is not included in the Additional E-DCH RL Specific Information To Setup IE in the Additional E-DCH FDD Setup Information IE in the Additional E-DCH Cell Information Setup IE, and the Radio Link indicated by the E-DCH Additional RL ID IE is not configured in the current Node B Communication Context as a Secondary Serving HS-DSCH radio link without any configured Additional E-DCH, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL and all secondary serving HS-DSCH RLs in the new configuration will not be assigned consecutive ordinal numbers starting with the value "1", which are previously assigned to the RL or received in the Ordinal Number Of Frequency IE in the HS-DSCH FDD Secondary Serving Information IE, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Additional HS Cell Information RL Addition IE and the new configuration contains more than one secondary serving HS-DSCH RL, the new configuration also contains an Additional E-DCH Serving Radio Link and the secondary serving HS-DSCH Radio link, which is configured in the same cell as the Additional E-DCH Serving Radio Link does not have Ordinal Number Of Frequency value “1, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the Affected HS-DSCH serving cell List IE in the Active Pattern Sequence Information IE and theTransmission Gap Pattern Sequence for affected HS-DSCH Serving Cells is activated on the HS-DSCH Primary Serving Cell but not for all the other serving cells, the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message with the cause value “Invalid CM settings”.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the UL CLTD Information IE but does not contain the F-TPICH Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL CLTD Information IE but without F-TPICH Information IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains the UL MIMO Information IE in E-DCH FDD Information IE but does not contain the UL CLTD Information IE, or if it contains HS-DSCH Preconfiguration Setup IE with UL MIMO Information IE but without UL CLTD Information IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the RADIO LINK ADDITION REQUEST message contains more than one of a MIMO Activation Indicator IE, a MIMO with four transmit antennas Activation Indicator IE, a Dual Stream MIMO with four transmit antennas Activation Indicator IE in HS-DSCH Preconfiguration Setup IE or in the Secondary Cells IE in the HS-DSCH Preconfiguration Setup IE, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the Dual Cell E-DCH operation enhancements configuration is setup but the Dual Cell E-DCH Operation Enhancements Information IE is not included in the RADIO LINK ADDITION REQUEST message, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the Dual Cell E-DCH operation enhancements configuration is setup and if the Continuous Packet Connectivity DTX-DRX Information IE in the HS-DSCH Serving Cell Change Information IE is included in the RADIO LINK ADDITION REQUEST message, but the DTX Information IE does not contain any of the value defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]

[FDD – If the Dual Cell E-DCH operation enhancements configuration is setup and if the DTX related Information is not signalled but the currently used value is not from the set of values defined for 10ms TTI, then the Node B shall reject the procedure using the RADIO LINK ADDITION FAILURE message.]