How can a phone designed for a terrestrial cell tower communicate with a satellite? Conventional D2C keeps the phone's supported cellular radio behavior and adapts the satellite system around it. This page focuses on that compatibility problem.
The satellite link introduces three problems at the same time: a weak received signal, a long propagation delay and a changing Doppler shift. The network must handle them without assuming new satellite-specific assistance procedures in the conventional phone.
Start with D2C Overview for terminology. D2C Architecture shows where the base station and core network sit. Here, let's look at the radio technology and the mechanisms behind the connection.
- Which Radio Technology Does Conventional D2C Use ?
- Who Handles the Satellite Motion ?
- How Does the Weak Phone Signal Reach Space ?
- Why Does a Decodable Signal Still Need a Compatible Network ?
- How to Compare Two D2C Technologies
- References
Which Radio Technology Does Conventional D2C Use ?
The handset uses a supported conventional cellular interface. LTE is a concrete example, but conventional D2C is not limited to LTE: a September 2023 demonstration established cellular 5G connectivity using an unmodified smartphone.
The common feature is the existing handset interface. The satellite payload, beamforming and ground network can be highly specialized even though the phone transmits and receives familiar cellular signals.
Standardized NR NTN and IoT NTN instead add satellite-specific device and network capabilities. Their detailed procedures are outside this page. See D2C versus standardized NTN for the terminology distinction.
How Can an Existing LTE Phone Connect ?
The network must present a signal that the phone can acquire, decode and answer using its supported LTE behavior. The engineering problem moves toward the satellite system: receive a weak uplink, transmit a usable downlink, and keep the timing and frequency behavior within what that phone can handle.
A January 2024 demonstration used unmodified LTE phones with an onboard LTE modem and a large satellite phased array. Its design also considered altitude, beam size and elevation angle to meet LTE constraints. This is a concrete example of the approach, not a description of every D2C implementation. See the January 2024 implementation example in References.
?Unmodified phone? does not mean every LTE phone can use every service. Band support, firmware configuration, subscription and network authorization still have to match. Also, a network cannot remove the physical travel time of the signal. It has to accommodate that delay within the procedures available to the device.
Who Handles the Satellite Motion ?
A satellite moves relative to many UEs at once. The distance and radial velocity are different for each UE. A correction suitable for the beam center therefore leaves a residual error elsewhere in the beam. The system has to keep that residual within the receiver's acquisition and tracking capability.
The diagram below shows the compatibility objective: the satellite and ground network handle the unusual geometry, while the phone uses its supported cellular procedures. It does not prescribe a vendor's compensation algorithm.
Figure 1 : Network adaptation preserves the conventional handset interface
Timing: Arrive at the Right Time
Suppose the service-link slant range is 1,200 km. Using c = 300,000 km/s, the one-way propagation time is 1,200 / 300,000 = 0.004 s, or 4 ms. A signal going out and back over that same distance needs 8 ms before processing is counted.
Now place another UE 300 km farther from the satellite. Its one-way service-link delay is 1 ms longer. Two UEs transmitting at the same local instant would not arrive together. Timing advance addresses arrival alignment, while scheduling offsets address when a grant or response can take effect. These are related problems, but their parameters are not interchangeable.
These values describe only the service link. A relay payload also carries the radio signal over a feeder link. The network has to fit the resulting delay into the phone's supported random-access and timing behavior; the calculation alone does not establish compatibility.
Doppler: Arrive at the Right Frequency
For a simple first-order estimate, the Doppler magnitude is |fD| = |vr| / c x fc. Here vr is radial velocity along the radio path. It is not automatically equal to the satellite's orbital speed.
Take fc = 2 GHz and |vr| = 6 km/s. The magnitude is 6 / 300,000 x 2,000,000,000 = 40,000 Hz, or 40 kHz. Whether the received frequency increases or decreases depends on whether the distance is shrinking or growing. This is an illustrative geometry, not a specified maximum.
A frequency correction must change as the geometry changes. Correcting the beam center once cannot eliminate every UE's residual Doppler for an entire satellite pass. Beam size, network frequency correction and receiver tracking have to work together.
How Does the Weak Phone Signal Reach Space ?
The phone cannot simply increase its power until the satellite hears it. The system must combine satellite receive gain, a workable path-loss budget and transmission settings that the handset already supports.
Satellite Antenna and Beamforming
The handset has limited transmit power and antenna gain. The satellite can use a larger antenna aperture to improve reception and concentrate downlink energy. A phased array can steer beams electronically, but it still has finite power, aperture and processing resources.
Beam design also affects frequency reuse and the number of users sharing resources. A wide coverage footprint is not the same as high capacity for everyone inside it. Beam steering must follow the intended ground coverage as the satellite moves.
A Small Path-Loss Example
Free-space path loss in dB is approximately 92.45 + 20 log10(f_GHz) + 20 log10(d_km). At 2 GHz and 1,200 km, this gives 160.05 dB. Doubling the distance to 2,400 km gives 166.07 dB, about 6 dB more loss.
If every other term stayed the same, the received power would become about one quarter of its previous value. The system needs enough margin to absorb this change, or it must change how it transmits. This calculation excludes blockage, polarization mismatch, atmospheric losses and implementation losses. The uplink and downlink need separate budgets using their own transmit powers and antenna gains.
Coding, Repetition and the Cost in Resources
More robust modulation and coding can help decode a weaker signal, at the cost of fewer information bits per resource. Repetition sends additional copies that a receiver can combine when the radio procedure supports it. Those copies consume time and energy.
For example, assume a fixed payload occupies one resource allocation without repetition. Sending four copies uses four such allocations before any extra control overhead. Even if this makes the payload decodable, it does not create four times the useful throughput. The correct comparison is successful payload delivery per unit of radio resource.
Why Does a Decodable Signal Still Need a Compatible Network ?
Receiving synchronization signals is only the beginning. The phone must complete random access, exchange control messages and keep its connection while the geometry changes. A service can pass one step and fail at the next.
Problem | What the D2C network must accommodate |
|---|---|
Cell detected but access fails | Weak uplink, residual timing/frequency error and response windows supported by the handset |
Long radio round trip | Grant timing, feedback and retransmission behavior within the actual cellular implementation |
Serving coverage moves away | Beam steering, cell continuity or ordinary cellular handover/reselection supported by the phone |
No satellite path is usable | Service interruption, later reacquisition and application retry behavior |
For example, stronger downlink power may let a phone detect the cell while its uplink remains too weak to finish access. Increasing satellite receive gain can address that power imbalance, but it does not extend a response timer inside the phone. Each stage needs its own check.
A complete test therefore includes acquisition, access, authentication, sustained traffic and mobility. Test over the intended elevation range and with multiple active users. A successful connection near the center of one beam is useful evidence, but does not establish operation at the edge of every beam.
How to Compare Two D2C Technologies
Keep the following choices separate when comparing two services. They interact, but one choice does not uniquely determine the others. In particular, using the same handset RAT does not imply the same payload architecture or capacity.
Choice | Question to ask |
|---|---|
Radio interface | Which conventional cellular RAT and operating mode does the actual handset use? |
Spectrum | Which actual band and channel? Does the phone RF hardware support it? Distinguish the phone's cellular service-link band from the satellite feeder-link band. |
Payload | Transparent relay or onboard base-station processing? Identify the radio endpoint before calculating its RTT. |
Device and access | Which modem features, firmware, subscription and network permissions are needed? |
Service performance | At what elevation, blockage condition and traffic load? Is the figure for one user, one beam or the whole satellite? |
A successful short message proves a useful service, but it does not establish continuous coverage, voice quality or broadband capacity. To assess those claims, ask for the measurement conditions and the actual service being tested.
References
The dated examples below describe conventional cellular handset access. They support the stated implementation examples, rather than claims about current commercial coverage or compatibility with every phone.
- Direct to Cell First Text Update, January 2024 : SpaceX; existing LTE handset access, onboard LTE processing and transport to mobile operators.
- Cellular connectivity demonstration, September 2023 : AST SpaceMobile; an unmodified smartphone using a cellular 5G connection through BlueWalker 3.