How does a weak handset signal reach a satellite without changing the phone? The satellite system needs enough receive gain and transmit capability, while its timing and frequency handling must stay compatible with the handset's cellular behavior.

This page develops the radio mechanisms introduced in Technology. All numerical examples are illustrative engineering calculations, not measurements or proprietary design parameters from a commercial constellation.

• Start with the Handset Uplink
  • Worked Example: Uplink Received Power
• Why Use a Large Satellite Array ?
  • Beamwidth and Reuse
• Doppler and Residual Frequency Error
• Propagation Delay and Differential Delay
• Coding, Scheduling and Retransmissions
• What Should a Radio Test Show ?
• References

Start with the Handset Uplink

A strong satellite downlink does not prove that the phone can answer. Calculate the two directions separately. The handset power limit and antenna pattern can make uplink reception a different problem from delivering synchronization signals to the phone.

Worked Example: Uplink Received Power

Assume 23 dBm handset transmit power, -3 dBi effective handset antenna gain, 160 dB free-space loss, 35 dBi satellite receive gain and 3 dB of other losses. These assumptions define a service-link example only.

The noise calculation assumes a 290 K thermal reference and the stated receiver noise figure. It treats all received signal power as falling inside the illustrative 180 kHz measurement bandwidth. It is not an LTE transport-block throughput prediction.

If the same total signal power were spread across 1.08 MHz, six times the bandwidth, thermal noise would rise by 7.78 dB. Under those assumptions, SNR would fall to about 2.67 dB. Actual scheduling, power control, interference and coding determine whether a payload can be decoded.

Why Use a Large Satellite Array ?

A larger effective aperture can collect more uplink energy and concentrate downlink energy. A phased array also allows electronic steering, so the satellite can direct its service toward selected ground areas as it moves.

The diagram separates three effects that are easy to mix together. Receive gain helps the link budget, beam steering follows the service area, and spatial reuse can increase aggregate capacity when interference is controlled.

Figure 1 : A large antenna helps the radio link but does not remove resource limits

Beamwidth and Reuse

For a comparable aperture shape, beamwidth scales roughly with wavelength divided by aperture size. A narrower beam can reduce the number of unrelated users received together, but requires appropriate pointing and coverage planning.

Two beams can reuse a frequency only with acceptable mutual interference. Sidelobes, edge users, scan angle and power allocation affect that isolation. Doubling the number of beams does not automatically double useful capacity if power or feeder throughput is already the limiting resource.

Doppler and Residual Frequency Error

The satellite's radial velocity changes the received carrier frequency. The relevant quantity is motion along the radio path, rather than the full orbital speed. Different ground positions generally have different radial velocities.

For a 2 GHz carrier and 6 km/s radial speed, the first-order Doppler magnitude is 2 GHz x 6/300000 = 40 kHz. If a conceptual network correction removes 39 kHz at a reference location, 1 kHz remains there. This subtraction illustrates residual error; it is not a disclosed compensation algorithm.

At another location the uncorrected shift might be 42 kHz, leaving 3 kHz under the same correction. Beam geometry and receiver tracking therefore matter even after common correction. Oscillator error and the time variation of Doppler add further tracking demands.

Propagation Delay and Differential Delay

At a slant range of 1,200 km, the one-way service-link delay is 4 ms using c = 300,000 km/s. A second phone 150 km farther away adds 0.5 ms of one-way delay.

The network must handle both the large common delay and the difference among users. The handset still follows its supported access and uplink timing behavior. Arbitrarily increasing a phone timer is not an available network-side solution for an unchanged device.

Where the radio endpoint sits matters. An onboard base station receives the phone after the service link. A ground base station behind a relay also waits for the feeder path. The geometric round trip is only part of the timing problem; processing and configured protocol relationships still have to fit. See Architecture.

Coding, Scheduling and Retransmissions

A robust modulation and coding choice trades information rate for a greater chance of successful decoding. Giving a weak phone more radio resources can improve its delivery probability while reducing the resources left for others.

Repeated attempts also consume airtime and battery energy. For an illustrative independent success probability of 0.8 per attempt, the expected number of attempts until success is 1/0.8 = 1.25. Real failures can be correlated by blockage, so repeated attempts may be much less effective than this simple model suggests.

Radio feedback loops require time. Network implementations must work within the handset's supported HARQ behavior; conventional D2C does not imply that a phone implements satellite-specific HARQ extensions. Public high-level descriptions rarely reveal all scheduling and compensation details, so do not fill those gaps with invented parameter values.

What Should a Radio Test Show ?

Test the intended elevation range, handset orientations and beam locations. Record both uplink and downlink results, not just a phone screenshot showing reception. A weak uplink can fail after the downlink looks healthy.

The January 2024 engineering update describes large arrays and network design choices for ordinary LTE phones. It supports the overall approach, not the illustrative gains, frequencies or correction values used here. Compare results using the definitions in Performance.

References

• SpaceX - First Text Update, January 2024 : Historical LTE handset and satellite implementation example.