RSRP vs RSRQ vs SINR: Understanding the Three Pillars of LTE and 5G Signal Quality

RSRP measures how strong the signal is, RSRQ measures how clean that signal is relative to everything else on the channel, and SINR measures how much interference is drowning it out. You need all three together because a phone can show full bars (good RSRP) and still deliver terrible throughput if RSRQ and SINR are poor. Treat them as a diagnostic hierarchy, not three interchangeable numbers on a dashboard, and your troubleshooting gets a lot faster.

RSRP, RSRQ, SINR: What Each One Actually Measures

Most engineers can recite that RSRP is signal strength and SINR is interference. Fewer can explain why you need both, or what RSRQ is actually doing in between. Let's fix that in one place instead of stitching together three forum answers.

RSRP: is the signal even here?

Reference Signal Received Power (RSRP) is the average power, in dBm, of the reference signals across the channel bandwidth. It is a pure coverage metric. It tells you nothing about congestion, interference, or whether the receiver can actually use that power to decode data. Per 3GPP TS 36.214, RSRP is measured on specific reference signal resource elements, which reduces (but does not fully eliminate) the influence of cell load and traffic conditions on the reading.

RSRQ: is the channel clean?

Reference Signal Received Quality (RSRQ) factors RSRP against RSSI, the total received power including interference and noise from every source on the channel. Expressed in dB, RSRQ answers a different question: is this channel crowded or noisy? A cell can deliver strong RSRP and still produce a mediocre RSRQ if neighboring sectors or heavy traffic load are chewing up the same spectrum.

SINR: can the receiver decode it?

Signal-to-Interference-plus-Noise Ratio compares wanted signal power to the sum of interference and noise. This is the number that most directly predicts whether a device can decode data cleanly and at what modulation order. Three questions, three answers: is the signal here (RSRP), is the channel congested or noisy (RSRQ), can the receiver decode it cleanly (SINR)?

The Formula: How RSRQ Relates to RSRP and RSSI

RSRQ stops feeling like an arbitrary second number once you see the formula: RSRQ = N x RSRP / RSSI, where N is the number of resource blocks over which RSSI is measured. RSSI includes interference, noise, and adjacent traffic, so RSRQ drops even when RSRP stays high, purely because the channel got busier.

This is exactly why two cell sites with identical RSRP can produce very different RSRQ readings depending on sector loading and neighbor interference. Take a hypothetical cell edge location reading -85 dBm RSRP in a quiet rural sector. It will likely show a healthier RSRQ than the same -85 dBm RSRP measured in a congested urban sector packed with overlapping small cells and heavy user traffic. Same coverage number, very different usable quality.

That distinction matters when you're reviewing logs. A drop in RSRQ without a corresponding drop in RSRP is a red flag for congestion or interference, not a coverage hole. Chasing it with a power boost won't help.

What Is a Good RSRP and RSRQ?

Here are the engineering reference ranges most RF teams use when scanning a drive test log or dashboard. These are commonly used rules of thumb, not hard 3GPP thresholds, and actual acceptable values vary by vendor, band, and deployment scenario.

RSRP alone cannot predict user experience. It only confirms the signal physically reached the device. A phone sitting at -78 dBm RSRP can still deliver a frustrating browsing experience if RSRQ and SINR tell a worse story.

What Is a Good SINR Number, and Why Does Yours Keep Dropping?

SINR is the metric most directly tied to achievable throughput and modulation scheme. Higher SINR allows higher-order modulation and a better CQI report, which is why it's the number engineers watch when a user complains about slow data despite full signal bars.

• Excellent: above 20 dB, supports highest-order modulation and peak throughput
• Good: 13 to 20 dB, solid throughput with occasional modulation step-down
• Fair: 0 to 13 dB, noticeably reduced throughput and higher retransmission rates
• Poor: below 0 dB, severe throughput loss, call quality and data sessions both suffer

Low SINR despite strong RSRP almost always points to interference rather than weak coverage: overlapping cells, high sector loading, co-channel interference, or physical obstructions causing multipath reflections. Dense urban environments packed with overlapping small cells are a classic SINR killer, even in locations where RSRP looks perfectly healthy. If your SINR keeps dropping at the same location, stop looking at power and start looking at what else is transmitting on that channel.

Coverage vs Quality vs Interference: How the Three Metrics Divide the Problem

The reason engineers get stuck on a single KPI is that they treat RSRP, RSRQ, and SINR as competing explanations instead of three layers of the same problem. As covered earlier, these layers divide cleanly into coverage, quality, and interference, and keeping that separation in mind is what prevents misdiagnosis.

Downstream service-level KPIs like throughput, CQI, BLER, and MOS all depend on these three layers, but they are not interchangeable with them. A good MOS score on a VoLTE call still needs a healthy RSRP, RSRQ, and SINR underneath it; the service-level number is the output, not the diagnosis.

This layered framework is also the basis for how 4G and 5G radio access networks are optimized, since the same coverage-quality-interference split applies across technologies.

The Classic Trap: Strong RSRP, Weak SINR, Bad Call Quality

Take a hypothetical drive test log showing RSRP at -75 dBm, well into the excellent range, paired with SINR at just 2 dB, solidly poor. Throughput and VoLTE MOS both suffer despite the strong bars the subscriber sees on their phone.

This pattern typically signals interference from overlapping cells, high network load, or in-building multipath rather than a coverage problem. The degradation comes from interference the receiver cannot cleanly separate from the wanted signal, not from a lack of signal strength.

Fixing it requires sector or antenna tuning and interference mitigation, not more transmit power. Boosting RSRP without addressing the interference source will not raise SINR, and in dense sectors it can even make things worse by adding to the noise floor other users experience. This is exactly the kind of correlation that automated and drive test platforms are built to capture across a route or building floor, logging RSRP, SINR, and throughput together so the interference pattern becomes visible on a map instead of buried in a spreadsheet.

From LTE to 5G NR: SS-RSRP, SS-RSRQ, SS-SINR

The same three-layer logic carries over to 5G NR, just measured on a different reference signal. 5G NR defines SS-RSRP, SS-RSRQ, and SS-SINR, measured on the Synchronization Signal block (SSB) instead of LTE's cell-specific reference signals.

Conceptually the roles are identical: SS-RSRP for coverage, SS-RSRQ for channel quality, SS-SINR for interference and noise ratio. In some deployments, operators also make use of CSI-RS based measurements as a general industry practice for finer-grained quality reporting alongside SSB-based measurements, though the specifics depend on vendor configuration and network design. These definitions are formalized in 3GPP TS 38.215, the NR counterpart to LTE's TS 36.214.

One wrinkle engineers run into during the 5G rollout phase: in Non-Standalone (NSA) deployments, the device still anchors to an LTE cell for control signaling while using NR for data. That means a test log in NSA mode can show both LTE RSRP/RSRQ/SINR and NR SS-RSRP/SS-RSRQ/SS-SINR simultaneously, and both frameworks need to be read together to understand the full picture. Standalone (SA) 5G testing simplifies this to NR metrics alone. This is a core part of the transformation of network testing from 4G to 5G.

How Field Engineers Capture and Correlate These KPIs in Practice

Reading these three metrics off a static table is one thing. Capturing them reliably across a moving vehicle, a multi-floor building, or a 24/7 monitoring window is a different challenge entirely.

Drive testing along defined routes logs RSRP, RSRQ, and SINR continuously alongside GPS location, letting engineers map weak zones geographically rather than guessing from a single snapshot. Drive testing in telecom has evolved specifically to support this kind of continuous, route-based correlation.

Indoor testing applies the same three metrics inside buildings, where multipath and wall attenuation create very different interference patterns than outdoor environments. A hospital corridor and a parking garage can produce wildly different RSRQ and SINR profiles even at similar RSRP levels.

Engineers then cross-reference RSRP, RSRQ, and SINR against CQI, BLER, and throughput logs to confirm whether a coverage, quality, or interference issue is the actual root cause. Automated and remote measurement approaches allow continuous KPI correlation over time instead of one-off snapshot tests, which matters when a problem only shows up during peak-hour congestion. Post-processing software is where this multi-KPI correlation, mapping, and benchmarking actually happens once raw logs are collected from the field.

Reading the Three Metrics Together: A Practical Takeaway

The decision rule is simple: check RSRP first to confirm coverage exists, then RSRQ to see if the channel is clean, then SINR to confirm the receiver can actually decode the signal. Skip any one of these three checks and you risk applying the wrong fix. Adding transmit power will not solve an interference problem, and tuning antenna tilt won't fix a genuine coverage hole.

For consistent, route-based or building-wide correlation of these KPIs with throughput, handover, and voice quality, purpose-built drive test and indoor measurement tools remove the guesswork of manual logging. Dingli provides mobile network testing and measurement solutions for telecommunications operators, network equipment manufacturers, engineering service providers, and enterprises, with indoor network testing applications covering commercial buildings, hospitals, schools, shopping malls, and other indoor environments where this exact RSRP-RSRQ-SINR correlation needs to happen systematically rather than metric by metric.

Browse Dingli's RAN solutions or explore the broader resource library for more on structured network measurement.

Frequently asked questions

What is a good RSRP and RSRQ?

As engineering rules of thumb, RSRP above -80 dBm and RSRQ above -10 dB are considered excellent. RSRP between -90 and -100 dBm with RSRQ between -15 and -20 dB is fair. These are not formal 3GPP thresholds, actual acceptable values vary by vendor and deployment.

What is a good SINR number?

SINR above 20 dB is excellent and typically supports the highest-order modulation and peak throughput. 13 to 20 dB is good, 0 to 13 dB is fair with reduced throughput, and below 0 dB is poor, usually causing severe throughput loss and degraded call quality.

Why is my SINR so low?

Low SINR despite strong RSRP almost always points to interference rather than weak coverage: overlapping cells, high sector loading, co-channel interference, or multipath from physical obstructions. Dense urban areas with many overlapping small cells are a common cause even where signal strength looks fine.

How much RSRP is good?

RSRP above -80 dBm is generally considered excellent coverage, -80 to -90 dBm is good, and below -100 dBm is poor. But RSRP alone only confirms the signal reached the device; it says nothing about channel quality or interference, so it can't predict actual user experience on its own.