9 Node B controlled scheduling

25.3193GPPEnhanced uplinkOverall descriptionStage 2TS

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

9.1 General principle

The Node B controlled scheduling is based on uplink and downlink control together with a set of rules on how the UE shall behave with respect to this signaling.

In the downlink, a resource indication (Scheduling Grant) is required to indicate to the UE the maximum amount of uplink resources it may use. For FDD Dual Cell E-DCH operation, a resource indication (Scheduling grant) for each Activated Uplink Frequency is required to indicate to the UE the maximum amount of uplink resources it may use on the corresponding uplink frequency. For 1.28 Mcps TDD Multi-Carrier E-DCH operation, a resource indication (Scheduling grant) for each uplink carrier is required to indicate to the UE the maximum amount of uplink resources it may use on the same uplink carrier. When issuing Scheduling Grants, the Node B may use QoS-related information provided by the SRNC (see subclause 11.1.1) and from the UE in Scheduling Requests (see subclause 9.3.1). For FDD, the E-AGCH is used for collision resolution for UE’s in CELL_FACH. For FDD, the Node B uses a resource indication (Absolute Grant) for resource release of a common E-DCH resource for UEs in CELL_FACH. For 1.28Mcps TDD, the E-AGCH is used for common E-RNTI collision resolution for UEs in CELL_FACH.

Unless otherwise specified, the following procedures are run independently for each Activated Uplink Frequency. For each uplink frequency, the UE has a serving E-DCH cell, and a serving E-DCH RLS. It may also have non-serving E-DCH cells and non-serving E-DCH RL(s).

For 1.28 Mcps TDD Multi-Carrier E-DCH operation, unless otherwise specified, the following procedures are run independently for each uplink carrier. For all uplink carriers, the UE has a serving E-DCH cell.

The Scheduling Grants have the following characteristics:

– Scheduling Grants are only to be used for the E-DCH TFC selection algorithm (i.e. they do not influence the TFC selection for the DCHs);

– For FDD, Scheduling Grants control the maximum allowed E-DPDCH/DPCCH power ratio of the active processes. For the inactive processes, the power ratio is 0 and the UE is not allowed to transmit scheduled data;

– For TDD, Scheduling Grants control the maximum allowed rate to be used in E-TFC selection according to information received in the Absolute Grant;

– For FDD, Scheduling Grants provide collision resolution information and common E-DCH resource release commands for UEs in CELL_FACH.

– For 1.28Mcps TDD, Scheduling Grants provide common E-RNTI collision resolution information.

– All grants are deterministic;

– Scheduling Grants can be sent once per TTI or slower;

– There are two types of grants:

– The Absolute Grants provide an absolute limitation of the maximum amount of UL resources the UE may use. In CELL_FACH (FDD only), Absolute Grants also provide collision resolution information and common E-DCH resource release requests. In CELL_FACH (1.28Mcps TDD only), Absolute Grants also provide common E-RNTI collision resolution information.

– The Relative Grants (FDD only) increase or decrease the resource limitation compared to the previously used value;

– Absolute Grants are sent by the Serving E-DCH cell:

– They are valid for one UE;

– For FDD, in Dual Cell E-DCH operation, if Implicit Grant handling is configured on the secondary uplink frequency, the UE may consider the reception of a grant with a wrong CRC as a "Zero Grant";

– For FDD they may also be valid for a group of UEs or for all UEs;

– The UE identity to be used in the Serving E-DCH cell, the E-RNTI, is signalled to the UE via RRC;

– For 1.28Mcps TDD, a group of common E-RNTIs are allocated to each E-RUCCH for CCCH transmission. When initiating the CCCH transmission, UE selects an E-RUCCH and accordingly an E-RNTI related to the E-RUCCH.

– For FDD, the Absolute Grant contains:

– the identity (E-RNTI) of the UE (or group of UEs) for which the grant is intended (through an ID-specific CRC attachment);

– the maximum power ratio the UE is allowed to use, on 5 bits;

– in case of 2ms TTI an HARQ process activation flag indicating if the Primary Absolute Grant activates or deactivates one or all HARQ processes. That bit is also used to switch the UE from its primary E-RNTI to its secondary E-RNTI for both the 2ms and the 10ms TTI. When the E-DCH is configured with a 10ms TTI the flag shall always indicate that the Absolute Grant Scope is set to all HARQ processes. For Secondary Absolute Grants the flag shall always indicate that the Absolute Grant Scope is set to all HARQ processes in this version of the protocol;

– in case of Implicit Grant handling configured for secondary uplink frequency, all the HARQ processes are always used and the HARQ process activation flag value is used to indicate if the Serving Grant can be implicitly set to zero.

– For TDD, the Absolute Grant contains:

– details of the physical resources to be used for transmission

– The grant value – maximum transmit power per resource unit (per slot). The grant value is indicated in form of the ratio of the maximum expected E-PUCH received power per resource unit (per slot) to P_e-base via E-AGCH from Node B.

– Timeslots

– Channelisation code

– Resource duration

– E-HICH Indicator(EI), which is used to inform UE which E-HICH the feedback info is carried on(1.28Mcps TDD only)

– E-UCCH Number Indicator(ENI), which is used to indicate the detailed number of E-UCCH(1.28Mcps TDD only)

– For FDD, Group Identities are supported. Group identities or dedicated identities are not distinguished by the UE. It is up to UTRAN to allocate the same identity to a group of UEs;

– For FDD, up to two identities (E-RNTIs), one primary and one secondary, can be allocated to a UE at a time. In that case, both identities shall use the same E-AGCH channel. The allocation is done by the Node-B and sent by the SRNC in RRC. No secondary E-RNTI is allocated in CELL_FACH.

– For TDD, one identity (E-RNTI) is allocated to a UE at any time. This allocation is performed by the Node B and is sent to the UE by the SRNC (via RRC).

– The identity consists of 16 bits;

– For FDD:

– Relative Grants (updates) may be sent by the Serving and Non-Serving Node-Bs as a complement to Absolute Grants:

– The UE behaviour is exactly the same for Relative Grants for one UE, for a group of UEs and for all UEs;

– The Relative Grant from the Serving E-DCH RLS can take one of the three values: "UP", "HOLD" or "DOWN";

– The Relative Grant from the Non-serving E-DCH RL can take one of the two values: "HOLD" or "DOWN". The "HOLD" command is sent as DTX. The "DOWN" command corresponds to an "overload indicator";

– For each UE, the non-serving Node-B operation is as follows:

– If the Node-B could not decode the E-DPCCH/E-DPDCH for the last n₁ TTIs (where n₁ is defined in [17]) because of processing issue, it shall notify the SRNC;

– The non-serving Node-B is allowed to send a "DOWN" command only for RoT reasons (see conditions for sending "DOWN" command in subclause 14.1) and not because of lack of internal processing resources.

– For TDD:

– An Absolute Grant is sent via one of a set of E_AGCHs

– For each frame, a UE is required to monitor a set of E-AGCHs

– An Absolute Grant is received by the UE if it decodes it using the E-RNTI that it has been allocated

– Details of the set of E-AGCHs to be monitored are signalled to the UE via RRC

9.2 UE scheduling operation

9.2.1 Grants from the Serving RLS

9.2.1.1 FDD

The UE shall be able to receive Absolute Grants from the Serving E-DCH cell and Relative Grants from the Serving E-DCH RLS. For Dual Cell E-DCH operation, the UE shall be able to receive Absolute Grants from the Serving E-DCH cell on each Activated Uplink Frequency and Relative Grants from the Serving E-DCH RLS on each Activated Uplink Frequency.

The following procedures are run independently for each Activated Uplink Frequency.

The UE shall handle the Grant from the Serving E-DCH RLS as follows:

– If the UE in CELL_FACH is transmitting DTCH/DCCH:

– If an Absolute Grant was received within the collision resolution phase after starting transmitting on the granted common E-DCH resource:

– stop including its E-RNTI in the MAC-i PDU;

– Else

– stop any E-DPCCH and E-DPDCH transmission, stops any E-AGCH and E-HICH reception, resets MAC-is/i, releases all E-DCH HARQ resources and no longer considers any radio link to be the serving E-DCH radio link.

– If an Absolute Grant was received with value set to ‘INACTIVE’:

– The UE maintains a "Serving Grant" (SG);

– The SG is used in the E-TFC selection algorithm as the maximum allowed E-DPDCH/DPCCH power ratio for the transmission of scheduled data in active HARQ processes;

– Each Absolute Grant and Relative Grant is associated with a specific uplink E-DCH TTI i.e. HARQ process and HARQ entity. This association is implicitly based on the timing of the E-AGCH and E-RGCH (see [3]). The timing is tight enough that this relationship is un-ambiguous;

– The SG is updated according to the following algorithm, regardless of the transmission/retransmission status of the HARQ process. The SG is not used for the E-TFC selection algorithm if the HARQ process is in retransmission;

– When receiving an "Absolute Grant" on the E-AGCH of the serving E-DCH cell:

– Primary Absolute Grants always affect the SG;

– Secondary Absolute Grants only affect the SG if the last Primary Absolute Grant was set to ‘INACTIVE’ and, in case of 2ms TTI, the process activation flag was set to ‘All‘ (transition trigger), or if the latest Absolute Grant that affected the SG was the Secondary one. When transition to the secondary E-RNTI is triggered, UE shall update the SG with the latest received Absolute Grant on the secondary E-RNTI (UE shall listen to both E-RNTIs in parallel, if both E-RNTIs are configured);

– In case of 10ms TTI, SG is set to the received value if the grant value is different from ‘INACTIVE’;

– In case of 2ms TTI and a Primary Absolute Grant was received:

– If the received value is different from ‘INACTIVE’, the SG is set to that value and the following activation mechanism is applied to processes that are not disabled as per L3 signalling:

– In case of an AG associated to an inactive process, the process activation flag indicates whether all processes or only this particular process becomes active;

– In case of an AG associated to an active process, the process activation flag will indicate whether all processes become active (‘all‘) or the activation status of the processes is not changed (‘single‘);

– If the received value is ‘INACTIVE’, the UE behaviour depends on the process activation flag:

– If the flag is set to ‘single‘, this active process becomes inactive;

– If the activation flag is set to ‘All‘ and the secondary E-RNTI is configured:

– All L3-enabled processes that are deactivated become active.

– If the activation flag is set to ‘All‘ and the secondary E-RNTI is not configured:

– All L3-enabled processes are deactivated (if a process was inactive it remains inactive, if a process was active it becomes inactive).

– In case of 2ms TTI and a Secondary Absolute Grant was received:

– In case the Secondary Absolute Grant affects the SG, the SG is set to the received value.

– If no "Absolute Grant" is received by the UE in a TTI and the last SG update was due to a Primary Absolute Grant from the E-AGCH or from RRC signalling, then the UE shall follow the "Relative Grant" of the Serving E-DCH RLS:

– A Serving Relative Grant is interpreted relative to the UE power ratio in the previous TTI for the same hybrid ARQ process as the transmission which the Relative Grant will affect (see figure 9.2.1-1);

Figure 9.2.1-1: Timing relation for Relative Grant

– If no data was transmitted at the same hybrid ARQ process in the previous TTI, the UE shall ignore the Relative Grant.

– Else

– The UE shall calculate its new SG by applying a Delta compared with its last used power ratio. See details in [4];

– When the UE receives a "HOLD" (i.e. DTX) from the Serving E-DCH RLS:

– SG remains unchanged.

9.2.1.2 TDD

The UE shall be able to receive Absolute Grant from the Serving E-DCH cell and shall select the maximum allowed rate in E-TFC selection according to information received in the Absolute Grant. For 1.28 Mcps TDD Multi-Carrier E-DCH operation, the UE shall be able to receive Absolute Grant from the Serving E-DCH cell for each uplink carrier and shall select the maximum allowed rate in E-TFC selection according to the information received in the Absolute Grant for each uplink carrier.

The following procedures are run independently for each uplink carrier.

The UE shall handle the Grant from the Serving E-DCH cell as follows:

– For 1.28Mcps TDD, if the UE in CELL_FACH state or Idle mode is transmitting CCCH:

– If an Absolute Grant is received within the common E-RNTI scheduling window after starting enhanced random access:

– select the maximum allowed rate in E-TFC selection according to information received in the Absolute Grant.

– else

– stop any E-AGCH and E-HICH reception, resets MAC-is/i.

– When the UE receives an Absolute Grant:

– if there are MAC-e / MAC-i PDUs awaiting retransmission and the resources assigned by the Grant enable transmission of a MAC-e / MAC-i PDU awaiting retransmission then it is used for a retransmission (oldest first) else it is used for a new transmission.

9.2.2 Grants from the Non-serving RL (FDD only)

Non-serving RLs may only send Relative Grants to the UE. For Dual Cell E-DCH operation, the UE may have Non-serving RLs for each Activated Uplink Frequency. The following procedure is run independently for each Activated Uplink Frequency.

The UE shall handle the RG from these non-serving E-DCH RLs as follows:

– When the UE receives a "DOWN" from at least one Non-serving E-DCH RL, it is interpreted relative to the UE power ratio in the previous TTI for the same hybrid ARQ process and entity as the transmission which the Relative Grant will affect (see figure 9.2.1-1). The UE shall calculate its new SG, see details in [4].;

– Following reception of a non-serving ‘DOWN’, UE shall ensure that its SG is not increased (due to E-AGCH or E-RGCH signalling) during one HARQ cycle.

9.2.3 Reception of Grants from both the Serving RLS and Non-serving RL(s) (FDD only)

In the case of a UE receiving grants from both the Serving RLS and Non-Serving RL(s), the UE behaviour is the following:

– When the UE receives a scheduling grant from the Serving E-DCH RLS and a "DOWN" command from at least one Non-Serving E-DCH RL:

– new SG is set to the minimum between the resulting SG from the non-serving E-DCH RL and the resulting SG from the serving RLS.

9.3 Signalling

9.3.1 Uplink

For the UE to request resources from the Node B(s), Scheduling Requests will be transmitted in the uplink in the form of Scheduling Information and Happy Bit (FDD only). The Scheduling information will be transmitted for the logical channels for which RRC configured that reporting needed to be made. For FDD, the Happy Bit shall always be included in the E-DPCCH, whenever the E-DPCCH is transmitted.

9.3.1.1 Scheduling information

9.3.1.1.1 Content

The UE includes the following in the Scheduling Information (only taking into account the logical channels for which RRC configured that reporting was required and always excluding logical channels mapped on non-scheduled MAC-d flows):

– Logical channel ID of the highest priority channel with data in buffer, on 4 bits. The logical channel ID field identifies unambigiouly the highest priority logical channel with available data and QoS information related to this indicated logical channel;

– UE Buffer occupancy (in Bytes):

– Buffer status for the highest priority logical channel with data in buffer, on 4 bits, as a fraction of the total reported buffer;

– Total buffer status, on 5 bits;

– UE Power Headroom (UPH): For FDD, the UPH field indicates the ratio of the maximum UE transmission power and the corresponding DPCCH code power defined in [7]. For TDD, the UPH field indicates the ratio of the maximum power and the calculated UE transmit power asdefined in [10] with _e = 0. The UPH field is 5 bits.

– For TDD: Path Loss:

– Information derived from measurements of serving cell and neighbour cell’s RSCP (5 bits);

9.3.1.1.2 Triggers

In the case where the UE is not allowed to transmit scheduled data (because it has no Serving Grant available or it has received an Absolute Grant preventing it from transmitting in any process) and it has Scheduled data to send on a logical channel for which Scheduling Information shall be reported:

– For FDD:

– Scheduling Information shall be sent to the Serving E-DCH RLS in a MAC-e / MAC-i PDU;

– Periodic reporting to protect against NACK-to-ACK misinterpretation;

– Scheduling Information could be sent alone, or with non-scheduled data, if such exist;

– Scheduling Information will also be triggered if higher priority data arrives in buffer.

– For 3.84 Mcps and 7.68 Mcps TDD:

– Scheduling Information shall be sent to the Node B on the E-RUCCH (E-DCH Random access Uplink Control Channel)

– Buffer Information, Physical Layer Information plus the E-RNTI is sent on the E-RUCCH

– Scheduling information may also be sent with non-scheduled data.

In the case where the UE is allowed to transmit scheduled data and it has Scheduled data to send on a logical channel for which Scheduling Information shall be reported:

– it shall send the Scheduling Information to the Serving E-DCH RLS in the MAC-e / MAC-i PDU;

– the Scheduling Information is sent periodically (period defined by RRC);

– For FDD and 1.28Mcps TDD, in CELL_FACH and IDLE mode, Scheduling Information shall be sent to report an empty buffer status.

– For FDD, in CELL_FACH state, if supported by the UE and configured by the network, Scheduling Information is sent to report that the UE with common E-DCH resource has met the cell reselection criteria.

The details on how Scheduling Information is included in the MAC-e / MAC-i PDU can be found in [4].

– For 1.28 Mcps TDD:

– In the case where the UE has no Grant and it has data to send, or an E-DCH serving cell change occurs with the TEBS larger than zero:

– Buffer Information and Physical Layer Information plus the E-RNTI shall be sent to the Node B on the E-RUCCH (E-DCH Random access Uplink Control Channel).

– In the case where the UE has a Grant and has data to send:

– It shall send Buffer Information and Physical Layer Information to the Node B in the MAC-e / MAC-i PDU.

– if the higher priority data arrives:

– if there is a Grant available for a new MAC-e / MAC-i PDU transmission, the Scheduling Information should be sent and included in the MAC-e / MAC-i PDU.

– otherwise, the Scheduling Information should be sent on the periodic reporting mechanism.

– In the case where UE transits from having a Grant to not having a Grant and has data to send, a timer T_WAIT is provided as a delay time to send buffer information mapped on E-RUCCH (T_WAIT is configured by RRC,default value is 8TTIs):

– When UE has sent data on E-PUCH in the last TTI before the current Grant expires:

– The timer T_WAIT shall be started.

– When a grant is received before the timer expires:

– The timer shall be stopped.

– When the timer T_WAIT expires:

– A new E-RUCCH transmission shall be made (the timer T_WAIT shall be stopped).

– In the case where the UE is only configured with non-scheduled transmission and without scheduled transmission, the Scheduling Information shall be included in MAC-e / MAC-i PDU due to the quantization of the transport block sizes that can be supported or upon the expiration of the timer T-SI-NST if configured, details in [4].

For UE in CELL_FACH state with E-DCH transmission, control of E-RUCCH transmission procedure triggered by different events shall be co-operated as below:

– In case Cell Reselection Indication via E-RUCCH is involved:

– During the E-RUCCH transmisson procedure triggered by Cell Reselection Indication ongoing, E-RUCCH transmission triggered by any event shall not be initiated and the corresponding events shall be ignored.

– During the E-RUCCH transmisson procedure triggered by events other than Cell Reselection Indication ongoing, if Cell Reselection Indication via E-RUCCH needs to be sent, any event which would initiate E-RUCCH transmission shall be cancelled.

– Else

– During the E-RUCCH transmisson procedure triggered by Scheduling Information reporting ongoing, E-RUCCH transmission triggered as a response to synchronization establishment command shall not be initiated and the newly triggered event shall be ignored.

– During the E-RUCCH transmisison procedure triggered as response to synchronization establishment command, if Scheduling Information reporting via E-RUCCH is needed, the E-RUCCH transmission shall be cancelled and Scheduling Information reporting via E-RUCCH shall be initiated with newly updated field of Scheduling Information according to the UE’s current status.

9.3.1.1.3 Transmission and Reliability scheme

Two transmission mechanisms are defined, depending on whether the Scheduling Information is transmitted alone, or with data (scheduled and/or non-scheduled):

1. When the Scheduling Information is sent alone:

For FDD:

– The power offset is configured by RRC and the maximum number of re-transmissions is defined by the standard;

– HARQ (re)transmissions are performed until an ACK from the RLS containing the serving cell is received or until the max number of transmissions is reached.

For TDD:

– Scheduling Information sent via the E-RUCCH (no Scheduling Grant) is transmitted at appropriate power and forward error correction, as defined by physical layer specifications. If the UE does not receive a response in the form of an Absolute Grant is received then the UE is required to resend Scheduling Information.

– For 1.28 Mcps TDD, Scheduling Information sent via MAC-e / MAC-i PDU alone is transmitted by applying the power offset, the retransmission timer and the maximum number of re-transmissions configured by RRC. HARQ (re)transmissions are performed until an ACK is received, or until the max number of transmissions is reached or the retransmission timer expires.

2. When Scheduling Information is sent with data:

– Use the HARQ power offset attribute of the highest priority data, and the maximum number of transmissions among all the considered HARQ profiles associated to the MAC-d flows for the MAC-e / MAC-i PDU to be transmitted;

– HARQ (re)transmissions are performed until an ACK is received, or until the max number of transmissions is reached.

– For FDD, if the UE receives an ACK from an RLS not containing the serving cell for a packet that includes scheduling information which was triggered by an event or a timer as per section 9.3.1.1.2, it flushes the packet and includes the scheduling information with new data payload in the following packet.

For 3.84 Mcps and 7.68 Mcps TDD:

– A timer value T-RUCCH is used to control retransmission of buffer information if there has been no grant received. The timer T_R manages retransmission of scheduling information if the UE does not receive a grant following an E-RUCCH transmission.

– Even when the scheduling information is sent on E-PUCH it is possible that the Node B may send a NACK (indicating that the buffer information was not correctly decoded) which the UE wrongly interprets as an ACK. Therefore, timers are also required to control retransmission of scheduling information sent on E-PUCH.

(T-RUCCH is configured by RRC, in Radio Bearer Setup Request, default value is 200 ms).

– When the aggregate buffer volume transitions from zero to greater than zero or the scheduling information delay timer ≥ T-SCHED + T-RUCCH / 2:

– E-RUCCH shall be sent (carrying scheduling information) and T_R shall be started/restarted.

– When timer T_R ≥ T-RUCCH a new E-RUCCH transmission shall be made (the timer is restarted) once a successful draw has been made using the E-RUCCH persistence value.

– Timer T_R is stopped (if running) when a grant is received.

– The scheduling information delay timer is restarted whenever scheduling information is sent on the E-PUCH.

For 1.28 Mcps TDD

– A timer T_RUCCH and a maximum number of transmissions N_RUCCH are used to control the retransmission of scheduling information, if there has been no Grant received following an E-RUCCH transmission. The maximum number of transmissions N_RUCCH is a mechanism to prevent the redundant transmission. T_RUCCH and N_RUCCH will be configured by higher layer and act as follows.

– A periodic Timer T-SI (defined by RRC) is used to avoid long pause duration of scheduling information reporting when scheduling information is sent on E-PUCH.

– When the timer T_WAIT expires or when the SI is triggered and there is no Grant available for new MAC-e / MAC-i PDU transmission in current TTI or in Extended Estimation Window (if configured by RRC):

– the UE sends information mapped on E-RUCCH;

– the timer T_RUCCH shall be started and a counter is set to 1.

– When a grant is received:

– the timer T_RUCCH shall be stopped and not be restarted, the counter shall be reset.

– When the timer T_RUCCH expires:

– if the counter is not greater than N_RUCCH:

– a new E-RUCCH transmission shall be made (restart the timer and increment the counter).

– else

– the timer T_RUCCH shall be stopped and not be restarted, the counter shall be reset.

– Another hysteresis Timer with the value of N-RUCCH times of T-RUCCH period shall be started, upon the hysteresis Timer expires and still no Grant has been received for the whole time duration since the last E-RUCCH transmission, a "Radio link failure" shall be triggered and reported.

– A periodic timer T-SI-NST (optionally defined by RRC) may be used to avoid long pause duration of scheduling information reporting when the UE is only configured with non-scheduled transmission and without scheduled transmission.

9.3.1.2 Happy bit of E-DPCCH (FDD only)

One bit of the E-DPCCH is used to indicate whether or not the UE is satisfied (‘happy’) with the current Serving Grant. This bit shall always be present during uplink transmission of E-DPCCH.

The UE shall indicate that it is ‘unhappy’ if the following criteria are met:

1) UE is transmitting as much scheduled data as allowed by the current Serving Grant; and

2) UE has enough power available to transmit at higher data rate; and

3) Total buffer status would require more than Happy_Bit_Delay_Condition ms to be transmited with the current Serving_Grant × the ratio of active processes to the total number of processes.

The first criteria is always true for a deactivated process and the ratio of the third criteria is always 1 for 10ms TTI.

Otherwise, the UE shall indicate that it is ‘happy’.

9.3.2 Downlink

For each UE, there can only be one Absolute Grant transmitted by the serving E-DCH cell using the E-AGCH.

For 1.28 Mcps TDD Multi-Carrier E-DCH operation, for each UE, there can be one Absolute Grant transmitted by the serving E-DCH cell using the E-AGCH for each uplink carrier.

For FDD:

– For each UE, there can be one Relative Grant transmitted per Serving RLS and one per Non-serving RL from the E-DCH active set cells.

– The channel(s) (one per cell) on which the Relative Grant is transmitted is(are) signalled separately to each UE (this allows for the same channel to be monitored by multiple UEs if UTRAN decides so).