RSRP vs RSRQ vs SINR
Three numbers show up on every drive-test scanner and field-test screen, and engineers mix them up constantly. RSRP is an absolute power — how strong the reference signals from a cell arrive at the UE, in dBm. It answers "is there coverage here?" RSRQ is a quality ratio that folds RSRP together with the total received power (RSSI), so it drops when the band gets loaded or interfered, even if RSRP stays high. SINR compares your wanted signal against interference plus noise, and it's the one that tracks throughput — high SINR means the scheduler can hand the UE a high-order modulation and coding scheme.
A quick naming note: in LTE these are RSRP and RSRQ (SINR isn't a 3GPP-reported quantity in LTE, but every tool computes it). In 5G NR the SS/PBCH-block versions are SS-RSRP, SS-RSRQ and SS-SINR, all defined in 3GPP TS 38.215.
| Aspect | RSRP | RSRQ | SINR |
|---|---|---|---|
| What it measures | Absolute received power of the reference signals from one cell | A quality ratio: reference-signal power relative to total received power | Wanted signal power versus interference plus noise |
| Formula / definition | Linear average of the power in the resource elements carrying the reference signal (CRS in LTE, SSS in NR) | RSRQ = N × RSRP / RSSI, where N is the number of resource blocks the RSSI is measured over | S / (I + N) — wanted signal divided by the sum of inter-cell interference and thermal noise |
| Typical unit | dBm (absolute power) | dB (a ratio) | dB (a ratio) |
| Typical good range | Better than about −80 dBm | Better than about −10 dB | Above roughly 20 dB |
| Typical poor range | Below about −110 dBm (cell edge / coverage hole) | Below about −15 dB | Below 0 dB (interference or noise dominates) |
| What it tells you | Coverage and signal strength — is there enough power here at all | Signal quality once load and interference are taken into account | How clean the link is, and therefore how much throughput is realistic |
| Affected by cell load? | No — it only looks at the reference signal, not traffic | Yes — more traffic raises RSSI, so RSRQ drops | Yes — neighbour-cell traffic shows up as interference |
| Mainly used for | Cell selection, reselection and handover (the A3/A5-style events) | Quality-triggered handover and gauging band loading/interference | Predicting MCS, link adaptation and achievable throughput |
| Reported by the UE? | Yes — in RRC measurement reports (RSRP/SS-RSRP) | Yes — in RRC measurement reports (RSRQ/SS-RSRQ) | NR reports SS-SINR; LTE has no standardised SINR report, so tools derive it |
| LTE vs 5G NR name | RSRP (LTE) / SS-RSRP or CSI-RSRP (NR) | RSRQ (LTE) / SS-RSRQ or CSI-RSRQ (NR) | Vendor-computed SINR (LTE) / SS-SINR or CSI-SINR (NR) |
Why RSRP alone isn't enough
RSRP is the first thing anyone checks because it's intuitive: a big negative number near zero (say −75 dBm) is strong, and a deep one (−115 dBm) is weak. It's the right metric for coverage questions — coverage holes, cell-edge boundaries, antenna tilt and link-budget work all live in RSRP.
The catch is that RSRP says nothing about what else is on the channel. The reference signal can land at −80 dBm while two neighbour cells dump interference on top of it, or while your serving cell is loaded with other users' traffic. RSRP won't move in either case, but your experience will. That's why a UE can sit on a strong cell and still crawl. Strength is necessary, not sufficient — you need a quality metric to see the rest of the picture.
How RSRQ folds in load and interference
RSRQ is built to catch what RSRP misses. The definition is RSRQ = N × RSRP / RSSI, where RSSI is the total wideband power the receiver sees — your cell, neighbour cells, and noise, across N resource blocks.
Because RSSI sits on the bottom, anything that raises the total received power drags RSRQ down. Load the cell with traffic and RSSI climbs, so RSRQ falls even though RSRP hasn't changed. Add a strong interfering neighbour and the same thing happens. That load-awareness is what makes RSRQ useful: a healthy RSRP with a poor RSRQ (worse than about −15 dB) is a classic fingerprint of a congested or interfered cell. One practical wrinkle for drive testing — RSRQ reads worse on a busy cell than an empty one, so compare like with like, and don't read too much into RSRQ on a lightly loaded test network.
SINR: the throughput predictor
If you only get to keep one metric for performance, keep SINR. It's the ratio of your wanted signal to interference plus noise, and the scheduler effectively uses it to decide how aggressive a modulation and coding scheme the UE can sustain. Higher SINR → higher-order MCS (up to 256-QAM and beyond) → more bits per resource element → more throughput.
Rough field intuition: below 0 dB you're in trouble, the link is dominated by interference or noise and throughput collapses. Around 0–13 dB is workable but modest. Above ~20 dB you're in the territory where high-order modulation and good throughput are on the table. Note that SINR and RSRQ usually move together — both react to interference and load — but SINR maps onto data rate far more directly. When someone reports "full bars, no speed," SINR is the number that explains it.
The bottom line
Pick the metric that matches the question. Coverage problem — dropped calls, dead spots, cell-edge access — read RSRP first; it tells you whether there's enough power to work with. Speed or quality problem on a cell that already has decent RSRP — read SINR (and RSRQ) to see whether interference or load is eating the link. In short: RSRP for is there signal, RSRQ for how clean is the channel under load, SINR for how fast can it actually go. Most real optimization work means looking at all three together — strong RSRP with poor SINR points at interference or congestion, while weak RSRP across the board points at a coverage gap.
Frequently asked questions
- What is a good RSRP value?
- As a rough guide, RSRP better than about −80 dBm is strong, −80 to −100 dBm is good to fair, −100 to −110 dBm is getting weak, and below −110 dBm is cell-edge or a coverage hole. These bands are typical, not standardised — operators and vendors set their own thresholds for handover and coverage, so treat the numbers as guidance rather than hard limits.
- RSRP vs RSRQ — what's the difference?
- RSRP is an absolute power in dBm: how strong the reference signal arrives, which tells you about coverage. RSRQ is a ratio in dB that divides RSRP by the total received power (RSSI), so it also reflects load and interference. RSRP can stay strong while RSRQ drops — that gap is exactly what RSRQ is there to expose: a busy or interfered cell with plenty of raw signal.
- Why is my RSRP good but speed bad?
- Strong RSRP only means the signal is loud, not clean. If SINR is low — say below a few dB — interference from neighbour cells or noise is swamping the wanted signal, so the scheduler drops to a low MCS and throughput tanks. High cell load does the same thing: it pushes RSSI up, drags RSRQ down, and forces lower data rates. Check SINR and RSRQ; a good RSRP with poor SINR or RSRQ is the usual cause of "full bars, slow data."
- What SINR do I need for good throughput?
- Higher is better, because SINR sets how high-order a modulation and coding scheme the link can carry. As a rough rule, above ~20 dB supports high-order modulation and strong throughput, roughly 0–13 dB is usable but limited, and below 0 dB throughput falls apart. Actual figures depend on bandwidth, MIMO layers, and vendor link adaptation, so use these as ballpark targets.
- Are RSRP, RSRQ and SINR the same in LTE and 5G NR?
- The concepts carry over but the names change. LTE uses RSRP and RSRQ (measured on CRS); SINR is computed by test tools rather than reported by the UE. 5G NR defines SS-RSRP, SS-RSRQ and SS-SINR measured on the SS/PBCH block, plus CSI-RSRP/CSI-RSRQ/CSI-SINR on CSI-RS, all specified in 3GPP TS 38.215.
Related terms
Go deeper than RSRP vs RSRQ vs SINR — free for 7 days.
Learn RSRP vs RSRQ vs SINR and the full 5G/6G stack with interactive lessons, labs and a TelcoMentor AI coach. Start a free 7-day Pro trial — no credit card.
- No credit card
- Full Pro access
- 21 verifiable certs
- TELCOMA since 2009
Get weekly 5G/LTE engineering deep-dives
One technical breakdown every Tuesday — plus first access to new tools and lessons. No spam, no marketing, just engineering. Unsubscribe in one click.