Showing posts with label SR. Show all posts
Showing posts with label SR. Show all posts

LTE: PUCCH Frequency Resource Calculator

             Bandwidth(MHz)         ExtendedCP


How this tool works?

This tool can be used to calculate the Physical Resource Block number (nPRB) to be used for transmission of PUCCH in the Even and Odd slots for PUCCH Formats 1x, 2x, and 3.
Bandwidth must be selected in order to calculate nPRB for all PUCCH formats.
For all PUCCH Format 1x, checkbox ‘ExtendedCP’ can be used to toggle between normal and extended cyclic prefix, the nPRB calculation depends on this selection. For PUCCH Formats 2x and 3, it has no effect.
For all PUCCH Format 1x, deltaPUCCH-Shift, nRB-CQI, and nCS-AN are to be taken from PUCCH-ConfigCommon .

PUCCH formats 1a, 1b, and 1b with channel selection (and no collision with SR) need n1PUCCH-AN (from PUCCH-ConfigCommon) and nCCE (the number of the first (lowest) CCE index).
For the cases where a positive SR is scheduled, sr-PUCCH-ResourceIndex shall be taken from SchedulingRequestConfig .

Use PUCCH Format 1 for calculating nPRB for the following scenarios:
1.    1. Only SR transmission
2.    2. SR and HARQ-ACK collision. The actual PUCCH format used is either 1a or 1b depending upon the number of HARQ-ACK bits but for the calculation of resources in this tool one can use ‘PUCCH Format 1’.
3.    3. SR and HARQ-ACK collision with format 1b for up to 4-bit HARQ-ACK with channel selection. The actual PUCCH format used is 1b with channel selection but for the calculation of resources in this tool one can use ‘PUCCH Format 1’.
In order to calculate nPRB for PUCCH Format 2/2a/2b, cqi-PUCCH-ResourceIndex should be taken from CQI-ReportPeriodic.
For PUCCH Format 3, one n3PUCCH-AN value out of 4 (n3PUCCH-AN-List-r10) should be selected based on the TPC field in the DCI format of the corresponding PDCCH on the SCell.

Similarly, for PUCCH Format 1b with channel selection, one n1PUCCH-AN value out of 4 (n1PUCCH-AN-CS-List) should be selected based on the TPC field in the DCI format of the corresponding PDCCH on the SCell. If Transmission Mode on the SCell is either TM1 or TM2 then n1PUCCH_j is sufficient, but if TM3 or TM4 is used for the SCell, then n1PUCCH_j+1 should also be provided.

For PUCCH formats which transmits HARQ feedback for a PDSCH transmission on the primary cell where there is not a corresponding PDCCH detected (SPS case), instead of nCCE and n1PUCCH-AN, N1PUCCH-AN-Persistent should be used. It is one value out of 4 N1PUCCH-AN-PersistentList which is based on TPC command received in the DCI format indicates a semi-persistent downlink scheduling activation.

Reference: 3GPP TS 36.321, 36.213, 36.331, 36.133, and 36.300

LTE: Scheduling Request Timing Calculator for FDD and TDD


SR configuration table is given below (Table 10.1.5-1 from 3GPP TS 36.213). SR transmission instances are the uplink subframes satisfying (10*SFN + subframe Noffset,SR) mod SRperiodicity = 0
Scheduling Request procedure in detail is presented here
SR configuration Index ISR
SR Periodicity (ms)
SRperiodicity
SR subframe offset Noffset,SR
0 4
5
ISR
5 14
10
ISR  5
15 34
20
ISR  15
35 74
40
ISR  35
75 154
80
ISR  75
155 156
2
ISR  155
157
1
ISR  157

One can use the below ‘SR calculator’ to calculate subframes for transmitting SR on PUCCH

sr-ConfigIndex (0-157):          TDD UL-DL Config:

         Is TDD?

SR timing will be displayed here

Full details of Scheduling Request subframes within one full SFN cycle

LTE: Scheduling Request Procedure


The Scheduling Request (SR) is used for requesting UL-SCH resources for new transmission.
UE’s MAC triggers scheduling request when a regular BSR is triggered and UE doesn’t have uplink resources for transmission of at least the regular BSR. Regular BSR is triggered when data becomes available for transmission in the uplink.
eNodeB needs to configure the UE with SR configuration via RRC signalling in order for the UE to transmit SR on PUCCH. The SR configuration structure is as given below


sr-PUCCH-ResourceIndex indicates the UE with the frequency domain resources whereas sr-ConfigIndex determines the time domain resources of PUCCH which carriers SR. eNodeB controls the maximum number SR transmissions from each UE on PUCCH using the parameter dsr-TransMax
If the UE has no valid PUCCH resources (SR is either not configured or released), then the UE initiates Random Access procedure
Once SR is triggered, the UE calculates the SR periodicity and offset (explained at the end of this post) which is based on sr-ConfigIndex IE. After transmitting the first SR on PUCCH, if the UE doesn’t receive uplink resources from the eNodeB, then based on the periodicity, the UE re-sends SR on PUCCH. This process continues till UE transmits SR for dsr-TransMax number of times on PUCCH if the UE doesn’t receive uplink resources from the eNodeB. After transmitting SR for maximum (dsr-TransMax) number of times, the UE releases SR resources (frequency as well as time), initiates random access procedure and cancels all pending (triggered) SRs
SR periodicities of 5, 10, 20, 40, and 80 ms are initially proposed in release-8. In release-9, short SR periodicities of 1 and 2 ms are introduced which reduces the latency.
When a short SR period is configured or when running VoIP traffic, the SR can be retransmitted unnecessarily. To avoid unnecessary SR transmissions, in release-9, an SR prohibit timer (sr-ProhibitTimer-r9) is introduced to reduce the load on PUCCH.
sr-ProhibitTimer-r9 IE is under mac-MainConfig and it can take values from 0 to 7. SR prohibit timer value is in number of SR period(s). Value 0 means no timer for SR transmission on PUCCH is configured. Value 1 corresponds to one SR period, Value 2 corresponds to 2*SR periods and so on. The UE starts this timer after transmitting an SR. When this timer is running, the UE is not supposed to be transmitting SR on PUCCH.
UE uses PUCCH Format 1 for transmitting SR alone. When SR and HARQ feedback in uplink happens to coincide in the same subframe, the UE shall transmit HARQ feedback on SR's frequency resource using PUCCH Format 1a/1b. Since PUCCH received is on SR resource, the eNodeB can easily understand that HARQ feedback and SR are present in the same subframe
If the UE is not configured for simultaneous PUSCH and PUCCH transmission or, if the UE is configured for simultaneous PUSCH and PUCCH transmission and not transmitting PUSCH, in case of collision between CSI and SR in a same subframe, CSI is dropped
UE release SR resources in the following cases
  • When UE has transmitted SR for maximum amount times (dsr-TransMax)
  • After timeAlignmentTimer expiry
  • During MAC reset procedure
  • During Handover (during Handover, MAC reset is performed)
During Handover, the source eNodeB has to provide the UE with a new SR configuration to be used in target eNodeB as the UE releases the existing SR resources in source eNodeB
SR configuration table is given below (Table 10.1.5-1 from 3GPP TS 36.213). SR transmission instances are the uplink subframes satisfying (10*SFN + subframe Noffset,SR) mod SRperiodicity = 0


SR configuration Index ISR
SR Periodicity (ms)
SRperiodicity
SR subframe offset Noffset,SR
0 ‒ 4
5
ISR
5 ‒ 14
10
ISR ‒ 5
15 ‒ 34
20
ISR ‒ 15
35 ‒ 74
40
ISR ‒ 35
75 ‒ 154
80
ISR ‒ 75
155 ‒ 156
2
ISR ‒ 155
157
1
ISR ‒ 157

One can also calculate SR instances from the below 'SR Calculator'

sr-ConfigIndex (0-157):          TDD UL-DL Config:

                     Is TDD?

SR timing will be displayed here

Full details of Scheduling Request subframes within one full SFN cycle