What is a cellular dead zone?

A dead zone is a place where a phone cannot get usable mobile service. Sometimes the phone has no network at all: Apple’s support page explains that when an iPhone shows “No Service” or “Searching”, it is not connected to a cellular network. Sometimes it is connected, but too weakly for calls to hold or for data to move. For an app, both look the same: requests time out.

Dead zones are not only remote valleys. They can be a basement, a lift, a concrete stairwell, the far end of a warehouse, or a train cutting a few minutes outside a city.

Radio signals weaken with distance, and anything between the cell site and the phone weakens them further. Three things account for this.

• Distance and missing sites. A phone too far from any cell site, on any network it is allowed to use, has nothing to connect to. Areas with few or no sites are the obvious case.
• Terrain. Hills, valleys and cuttings put ground between the phone and the nearest site. The FCC staff report on coverage maps lists terrain and clutter data among the inputs to the propagation models that providers use to predict coverage.
• Buildings. Walls, floors and windows weaken radio signals on their way in. The ITU publishes a dedicated recommendation, ITU-R P.2109, for predicting this building entry loss. NIST measured signal attenuation through brick, masonry block, eight concrete mixes, reinforced concrete, glass, lumber, plywood and drywall, at frequencies from 0.5 to 2 GHz and from 3 to 8 GHz, and reported loss as a function of thickness for each material.

There is also a direction to the problem. A phone can hear a cell site and still fail to send. The FCC report explains that mobile broadband needs uplink capacity, the phone’s transmission back to the antenna, as well as downlink, because protocols such as TCP/IP need the handset to acknowledge what it receives.

Coverage maps are predictions from propagation models, not measurements of every street. An FCC staff investigation into the 4G LTE coverage maps that providers submitted for the Mobility Fund Phase II programme tested them on the ground. Field agents ran 24,649 drive tests over nearly 10,000 miles and 5,916 stationary tests at 42 locations.

The staff found that the maps submitted by Verizon, U.S. Cellular and T-Mobile likely overstated actual coverage:

• Only 62.3% of staff drive tests achieved at least the minimum download speed the maps predicted.
• Staff could not obtain any 4G LTE signal in 38% of drive tests on U.S. Cellular’s network, 21.3% on T-Mobile’s and 16.2% on Verizon’s, despite each provider reporting coverage in those areas.

The report recommended that coverage data specify parameters such as minimum signal strength (RSRP), cell loading, terrain and clutter, and that providers back their models with on-the-ground test data. The practical lesson for anyone building an app is simpler: a map saying there is coverage is not evidence that a given spot works.

Not having a mobile network does not mean a phone can do nothing.

• Emergency calls. Apple notes that a phone showing “SOS” or “SOS only” can still make emergency calls.
• Satellite. iPhone 14 and later models can try Emergency SOS via satellite when there is no cellular or Wi-Fi coverage, with the phone outside and a clear view of the sky. How does direct-to-phone satellite messaging work? covers the options.
• Phone to phone. Bluetooth LE and other local radios do not use a cell site at all. Two phones near each other can exchange data with no tower; the Offline Protocol SDK, for example, carries local peer-to-peer traffic between nearby phones over Bluetooth LE. With relaying, as in a mesh of phones, a message can cross a site where no phone has a mobile signal.
• Later delivery. An app can keep a message or record on the device and send it once a connection returns, which is the idea behind store-and-forward.

If an app is used on the move, in buildings or outside cities, assume it will spend time in dead zones and plan for it:

• Keep what the user is doing on the device, and show clearly what has not yet been sent.
• Make retries safe to repeat, so work queued in a dead zone is not applied twice when the phone reconnects.
• Use a local path between nearby devices for tasks that only involve people in the same place.
• Test in the real places the app will be used, not from the coverage map.