Bad RSRQ Dowlink

Hi Everyone,
I’m analizing a specific zone in a mall where there’s a very low RSRQ arround -16dBm.
There is no a very high volume of serving cells so there’s is no pollution.
But most of all have bad values of RSRQ and good values of RSRP.

I have checked RachRootSequence and PCI problems but it don’t seems to be the problem.

RSSI problems only affects to Uplink, right?

Any idea about what else I can check in order to imporve the RSRQ?
Any feature or parametrizaction?

Regards
Have a good day everyone!

Admin note: this post was updated with image below.

Hello,

To understand LTE Signal Strength, see below chart.

It shows what values are considered good and bad for the LTE signal strength values.

image

And here are the meanings of these values (and also RSSI in relation to LTE):

  • SINR/SNR – The signal-to-noise ratio of the given signal.

  • RSRP – The average power received from a single Reference signal, and Its typical range is around -44dbm (good) to -140dbm(bad).

  • RSRQ – Indicates quality of the received signal, and its range is typically -19.5dB(bad) to -3dB (good).

  • RSSI – Represents the entire received power including the wanted power from the serving cell as well as all cochannel power and other sources of noise and it is related to the above parameters through the following formula:

  • RSRQ=N(RSRP/RSSI)*

    Where N is the number of Resource Blocks of the E-UTRA carrier RSSI measurement bandwidth.
    

Hope that helps.

3 Likes

Hi, thanks for your answer.
I would also like to know what are the main reasons for Bad RSRQ values and how to improve them.
Regards
Iñaki

There is a relation ship between RSRQ and RSSI also. Bad RSSI also can impact RSRQ.
Poor RSRQ reasons:

  1. Bad RSRP.
  2. Overshooting from neighbor cell.
  3. Less intersector seperation of the same site.(65deg is good)
    4.High utilization of the cell( If the utilization increases the RSSI increases which degrade the RSRQ).

Read the below blog:

3 Likes

What can be reason for Poor RSRQ in LTE if sites are not overloaded, but still value lies in range of -10 to -15? @irreyes , @Tech_Spoon

PCI collision.

I find SINR not poor but still RSRQ poor.
PCI collision means mod3 clashes that impact SINR?

Yes, correct.

-10 to -15 rsrq is still considered to be good RSRQ and very common to see in this range in good SINRs (greater than 6). Specially in 10 Mhz n lower bandwidths.

Also SINR vs RSRQ relation is exponential, for SINR increases to better values, RSRQ marginally improves.

For RSRQ based mobility used for inter Freq/inter RAT
A2: used -12
A1 : used -10
Threshold 1 serving : - 14
Threshold 2 neighbour : - 12

Is it ok or you find some fine tuning needed with current RF?

From which to which band?

Band 40 to band 3.

It depends on your network and how traffic balancing to be done accross bands.

In our network Band 40 has 2 carriers of 20 Mhz each, so we keep most of data traffic in Band 40.
So our A2 is -18 RSRQ or A2 is -116 RSRP whichever triggers earlier.

In VoLTE we don’t want to keep traffic. In Band 40 is A2 is -4 dB RSRQ only.

1 Like

Any specific reason to offload VoLTE from b40 having more capacity in term of BW and PRB as compared to b3?

B3 is low frequency band and have better coverage.

But that not look reason to offload VoLTE users from more capacity band which can cater user easily.

In B40 certain features doesn’t work like tti bundling etc.

In general globally Operator avoid VoLTE in TDD.

TTI bundling can work with TDD as well, no such limitation from UE point of view.
We can use TTI bundling now with TDD config 2, 3 as well in rel14, which was limitation earlier.

I agree earlier tti bundling with FDD only before r14.

In our network we enabled service based HO from TDD to FDD.
No VoLTE on TDD.
Muting improved.

Better the coverage, better the VoLTE performance.
Moreover, spectral efficiency is affected if VoLTE users are more.
Band 40 is mainly being used for data.