Carrier-to-Noise Density Ratio

Carrier-to-noise density ratio, usually written C/N0, compares received carrier power with noise power spectral density. It is a link-budget metric, not a normal bandwidth-limited SNR. Because the denominator is per hertz, C/N0 is commonly reported in dB-Hz.

The metric is useful when the same received carrier may support different bit rates, coding rates or receiver bandwidths. It keeps the carrier and the receiver noise density visible before converting to C/N, SNR or Eb/N0.

Basic Definition

In linear form:

has units of hertz because C is carrier power and N_0 is noise power per hertz. In decibel form:

If carrier power is available in dBm, convert consistently or subtract a noise density in dBm/Hz; the result is still dB-Hz.

Link-Budget Form

For a satellite, telemetry or long-range RF link, a common expression is:

where:

• EIRP is effective isotropic radiated power;
• L_path includes propagation and implementation losses at the stated boundary;
• G/T is receiver antenna gain-to-system-noise-temperature ratio;
• k is Boltzmann’s constant in dBW/K/Hz.

A common value is:

The expression works only when all terms use compatible reference planes and signs.

Conversions

For a receiver noise bandwidth B, carrier-to-noise ratio is:

For bit rate R_b, available bit-energy ratio is:

These conversions are why C/N0 is useful: bandwidth and bit rate are selected later, while the carrier and noise-density budget remains traceable.

Worked Example

An uplink budget gives:

Path loss and implementation losses are:

The receive system has:

The available carrier-to-noise density is:

If the receiver noise bandwidth is:

then:

For transmitted bit rate:

the bit-rate term is:

so:

If the modem requirement is:

and validation allowance is:

the guarded margin is:

Boundary With SNR and Eb/N0

SNR depends on a chosen bandwidth. Eb/N0 depends on a chosen bit-rate basis. C/N0 sits before those choices and is therefore useful in link budgets, modem telemetry and satellite operations. It does not remove the need to check interference, fading, phase noise, coding basis or implementation loss.

If interference is comparable with thermal noise, a carrier-to-noise-density result alone may be optimistic. The release decision may need C/(N+I), SINR, packet-error evidence or measured modem margins.

Measured modem C/N0 and calculated link-budget C/N0 should also be reconciled carefully. A modem may estimate the value after synchronization, filtering, equalization or implementation losses, while a budget may reference the antenna terminal or receiver input. The numbers are comparable only after the boundary and included impairments are understood.

Validation Evidence

A defensible C/N0 statement includes received carrier boundary, EIRP basis, path loss, atmospheric and feeder losses, antenna gain, system noise temperature or G/T, polarization and pointing losses, bandwidth or bit-rate conversions, weather state, calibration, timestamp, receiver configuration and uncertainty allowance.

Field evidence should preserve modem-reported C/N0 if available, spectrum measurements with RBW and detector settings, received power, error-rate statistics, adaptive-coding logs and any fade or interference events observed during the test window.

Common Mistakes

Common mistakes include treating C/N0 as ordinary SNR, subtracting bit rate with the wrong units, mixing dBm and dBW references, using clear-sky G/T during a rain event, forgetting implementation losses, and comparing modem-reported C/N0 from different vendors without checking the reporting boundary.

The practical rule is to use C/N0 to keep carrier power and noise density explicit, then convert to the bandwidth or bit-rate metric required by the decision.