8.2.7 Physical Shared Channel Allocation [TDD only]

25.3313GPPProtocol specificationRadio Resource Control (RRC)Release 17TS

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

Figure 8.2.7-1: Physical Shared Channel Allocation

8.2.7.1 General

The purpose of this procedure is to allocate radio resources to USCH and/or DSCH transport channels in TDD mode, for use by a UE. This procedure can also be used to indicate to the UE, that a PUSCH allocation is pending, in order to prevent further capacity requests from the UE.

UEs are not required to receive FACH and DSCH simultaneously, i.e. if resources are allocated to DSCH the FACH reception may be suspended.

8.2.7.2 Initiation

To initiate the Physical Shared Channel Allocation procedure, the UTRAN sends the "PHYSICAL SHARED CHANNEL ALLOCATION" message on the downlink SHCCH or on the downlink DCCH using UM RLC. The DSCH-RNTI shall be included for UE identification, if the message is sent on the SHCCH.

8.2.7.3 Reception of a PHYSICAL SHARED CHANNEL ALLOCATION message by the UE

Upon reception of a "PHYSICAL SHARED CHANNEL ALLOCATION" message, if the message is received on the downlink SHCCH the UE shall:

1> check the DSCH-RNTI to see if the UE is addressed by the message;

1> if the UE is addressed by the message, or if the message is received on the downlink DCCH:

2> perform the following actions.

1> otherwise:

2> ignore the message.

1> act upon all received information elements as specified in subclause 8.6, unless specified otherwise in the following:

1> if the IE "ISCP Timeslot list" is included:

2> store the timeslot numbers given there for future Timeslot ISCP measurements and reports in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION.

1> if the IE "PDSCH capacity allocation info" is included:

2> configure the physical resources used for the downlink CCTrCH given by the IE "TFCS ID" according to the following:

3> if the CHOICE "Configuration" has the value "Old configuration":

4> if the UE has stored a PDSCH configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION with the identity given by the IE "PDSCH Identity":

5> configure the physical resources according to that configuration.

4> otherwise:

5> ignore the IE "PDSCH capacity allocation info".

3> if the CHOICE "Configuration" has the value "New configuration":

4> configure the physical resources according to the information given in IE "PDSCH Info". If IE "Common timeslot info" or IE "PDSCH timeslots and codes" IE are not present in IE "PDSCH Info":

5> reuse the configuration stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION for this CCTrCH.

4> if the IE "PDSCH Identity" is included:

5> store the new configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION using that identity.

2> start using the new configuration at the CFN specified by the IE "Allocation activation time", and use that for the duration given by the IE "Allocation duration";

2> if the IE "Confirm request" has the value "Confirm PDSCH" and IE "PDSCH Identity" is included in IE "PDSCH capacity allocation info":

3> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8.

1> if the IE "PUSCH capacity allocation info" is included:

2> stop the timer T310, if running;

2> if the CHOICE "PUSCH allocation" has the value "PUSCH allocation pending":

3> start the timer T311.

2> if the CHOICE "PUSCH allocation" has the value "PUSCH allocation assignment":

3> stop the timer T311, if running;

3> configure the physical resources used for the uplink CCTrCH given by the IE "TFCS ID" according to the following:

4> if the CHOICE "Configuration" has the value "Old configuration":

5> if the UE has stored a PUSCH configuration with the identity given by the IE "PUSCH Identity" in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION:

6> configure the physical resources according to that configuration.

5> otherwise:

6> ignore the IE "PUSCH capacity allocation info".

4> if the CHOICE "Configuration" has the value "New configuration", the UE shall:

5> configure the physical resources according to the information given in IE "PUSCH Info". If IE "Common timeslot info" or IE "PUSCH timeslots and codes" is not present in IE "PUSCH Info":

6> reuse the configuration stored in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION for this CCTrCH.

5> if the IE "PUSCH Identity" is included:

6> store the new configuration in the variable PHYSICAL_SHARED_CHANNEL_CONFIGURATION using that identity.

3> if the IE "PUSCH power control info" is present in this message and includes the parameter "UL target SIR" for 3.84 Mcps TDD or 7.68 Mcps TDD, or the parameters "PRX_PUSCHdes" and "Beacon PL Est. " and "TPC Step Size" for 1.28 Mcps TDD, or the parameters are stored in the variable PHYSICAL SHARED CHANNEL CONFIGURATION for this CCTrCH:

4> start using the new configuration at the CFN specified by the IE "Allocation activation time", and use that for the duration given by the IE "Allocation duration".

3> otherwise:

4> ignore the IE "PUSCH capacity allocation info".

3> if the IE "PUSCH power control info" is present in this message and includes the parameter "UL target SIR" for 3.84 Mcps TDD or 7.68 Mcps TDD, or the parameters "PRX_PUSCHdes" and/or "Beacon PL Est. " and/or "TPC Step Size" for 1.28 Mcps TDD:

4> replace the parameters "UL target SIR" or "PRX_PUSCHdes" or "TPC Step Size" stored in the variable PHYSICAL SHARED CHANNEL CONFIGURATION for this CCTrCH with the signalled values.

3> if the IE "Traffic volume report request " is included:

4> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8 at the time indicated by the IE "Traffic volume report request".

3> if the IE "Confirm request" has the value "Confirm PUSCH" and IE "PUSCH Identity" is included in IE "PUSCH capacity allocation info":

4> initiate the PUSCH CAPACITY REQUEST procedure as described in subclause 8.2.8.

3> determine the TFCS subset and hence the TFCI values which are possible given the PUSCH allocation for that CCTrCH;

3> configure the MAC-c/sh in the UE with this TFCS restriction if necessary;

3> transmit USCH Transport Block Sets as required, within the TFCS limits given by the PUSCH allocation.

NOTE: If the UE has just entered a new cell and System Information Block Type 6 has not yet been scheduled, PUSCH/PDSCH information should be specified in the allocation message.

The UE shall:

1> clear the entry for the PHYSICAL SHARED CHANNEL ALLOCATION message in the table "Accepted transactions" in the variable TRANSACTIONS;

1> and the procedure ends.

8.2.7.4 Invalid PHYSICAL SHARED CHANNEL ALLOCATION message

If the UE receives a PHYSICAL SHARED CHANNEL ALLOCATION message, which contains a protocol error causing the variable PROTOCOL_ERROR_REJECT to be set to TRUE according to clause 9, the UE shall perform procedure specific error handling as follows. The UE shall:

1> ignore the invalid PHYSICAL SHARED CHANNEL ALLOCATION message;

1> submit the PUSCH CAPACITY REQUEST message for transmission on the uplink SHCCH, setting the information elements in the message as specified in subclause 8.2.8.3;

1> reset counter V310;

1> start timer T310;

1> proceed as described in subclause 8.2.8.