Technopedia

The technologist’s encyclopedia

Wireless interfaces

Wireless interfaces use electromagnetic waves in free space to carry data between devices. They are relevant whenever a physical cable is impractical: mobile phones, laptops, sensors, satellites. At the cm–10⁴ km scale, the dominant physics is path loss, multipath, and diffraction; the design disciplines are RF/antenna design, spectrum management, and MIMO/OFDM signal processing. All five interface families below are applications of the same link-budget physics, so start with Wireless link fundamentals before diving into a specific family.

The protocol stacks above the physical layer (association, IP, TCP, HTTP, TLS) are covered once, here, by Networks; the Shannon-capacity limit that bounds every link’s data rate is covered by Communication, and the underlying wave physics by Electromagnetism and Wave propagation.

Authoritative sources

Definition. Every wireless link is a power budget. Free-space path loss is FSPLdB=20log⁡10(dkm)+20log⁡10(fMHz)+32.44\mathrm{FSPL_{dB}} = 20\log_{10}(d_{\mathrm{km}}) + 20\log_{10}(f_{\mathrm{MHz}}) + 32.44, and the received power is Prx=Ptx+Gtx+Grx−FSPLP_{rx} = P_{tx} + G_{tx} + G_{rx} - \mathrm{FSPL} (all in dB/dBm). The achievable data rate is then bounded by Shannon: C=Blog⁡2(1+SNR)C = B\log_2(1 + \mathrm{SNR}).

Details

Step 1 — The link budget. A transmitter radiates power PtxP_{tx}; the wave spreads over a sphere of radius dd, so the power density falls as 1/d21/d^2 (the inverse-square law of wave propagation). Antennas focus the energy: a gain GtxG_{tx} on the transmit side and GrxG_{rx} on the receive side. Collecting the terms in decibels gives the link budget: Prx=Ptx+Gtx+Grx−FSPLP_{rx} = P_{tx} + G_{tx} + G_{rx} - \mathrm{FSPL}. The Friis equation behind the FSPL formula also carries a 20log⁡10(f)20\log_{10}(f) term: at higher frequencies, the same aperture antenna captures less power, which is why mmWave links are short-range.

Step 2 — A worked example. A Wi-Fi access point at 2.4 GHz, 1 m from a laptop: FSPL = 32.44 + 20·log₁₀(0.001) + 20·log₁₀(2400) = 32.44 − 60 + 67.6 ≈ 60 dB. With P_tx = 20 dBm (100 mW) and 0 dB gains, the receiver gets −40 dBm — comfortably above a typical −80 dBm sensitivity. At 100 m the path loss is 80 dB and the received power −60 dBm: still workable, but with much less margin.

distance (m, log scale) path loss (dB) 1 10 100 40 60 80 5 GHz (+6 dB) 2.4 GHz +20 dB per decade of distance

Step 3 — Modulation versus range. A receiver needs a minimum signal-to-noise ratio (SNR) per modulation: QPSK carries 2 bits/symbol at ~10 dB SNR; 256-QAM carries 8 bits/symbol but needs ~28 dB; 1024-QAM needs ~35 dB. Since SNR falls with distance, real systems use adaptive modulation: full speed close to the access point, dropping to QPSK at the cell edge. This is the fundamental throughput-versus-range trade-off of every wireless interface below.

Step 4 — Multipath fading. In indoor and urban environments the wave reaches the receiver by many reflected paths of different lengths. The copies add constructively or destructively depending on frequency and position, so the received power fluctuates (fading) rather than following a clean inverse-square curve. Two standard mitigations: OFDM splits the band into many narrow sub-carriers so that each experiences only flat fading, and MIMO uses multiple antennas so that several independent fading paths exist simultaneously.

Step 5 — Explore it interactively. The simulator below computes the link budget and Shannon-limited data rate for five real interfaces. Move the distance slider and watch the achievable modulation fall as the SNR drops.

Step 6 — Sources and limits. The Shannon bound C=Blog⁡2(1+SNR)C = B\log_2(1+\mathrm{SNR}) is derived in Communication; the wave phenomena (reflection, diffraction, inverse-square spreading) in Wave propagation and Electromagnetism.

Example problem

A 5G small cell transmits at 3.5 GHz with 30 dBm, 5 dB transmit antenna gain and 0 dB receive gain. What is the received power at 200 m, and is a 256-QAM link (needs −78 dBm received power for adequate SNR in 100 MHz) feasible?

Solution

FSPL = 32.44 + 20·log₁₀(0.2) + 20·log₁₀(3500) = 32.44 − 14.0 + 70.9 ≈ 89.3 dB. P_rx = 30 + 5 + 0 − 89.3 = −54.3 dBm. −54.3 dBm is 23.7 dB above −78 dBm, so 256-QAM is feasible with a healthy margin — the link is SNR-rich, and the operator would rather reuse the frequency in a neighbouring cell than raise power.

Wi-Fi (IEEE 802.11)

Definition. Wi-Fi is a shared-medium, OFDM-based wireless LAN. Wi-Fi 6 (802.11ax, 2019) operates at 2.4 GHz and 5 GHz; its 9.6 Gb/s peak PHY rate requires 8 spatial streams × 160 MHz × 1024-QAM (MCS11, rate 5/6): 8 × 1201 Mb/s ≈ 9.6 Gb/s. Wi-Fi 6E (2021) adds the 6 GHz band. Wi-Fi 7 (802.11be, 2024) adds 320 MHz channels and 4096-QAM.

Details

Step 1 — Sharing the medium. All devices in a cell share the same frequency band. Classic Wi-Fi coordinates access with CSMA/CA (Carrier Sense Multiple Access with Collision Avoidance): listen before transmitting, back off a random time if busy. Wi-Fi 6 adds OFDMA (Orthogonal Frequency-Division Multiple Access): the access point schedules groups of OFDM sub-carriers to several users simultaneously, which is far more efficient for many small packets.

Step 2 — OFDM sub-carriers. The channel is divided into many narrow sub-carriers (78.125 kHz each in 802.11ax), modulated independently. Because each sub-carrier is narrow compared with the channel’s frequency-selective fading, each experiences only flat fading — this is the multipath defence from Wireless link fundamentals. The diagram shows an OFDMA frame: the AP assigns sub-carrier groups (resource units) to different users.

20 MHz channel = 242 data sub-carriers (78.125 kHz each) — 40 shown ■ user A (8 sub-carriers) ■ user B ■ user C ■ user D ■ pilot / null Each sub-carrier sees flat fading; a deep fade kills one narrow sub-carrier, not the whole 20 MHz channel. Forward error correction repairs the lost bits. Per-stream rate = sub-carriers × bits/symbol × code rate × symbols/s. MIMO multiplies this by the number of spatial streams.

Step 3 — The bands and channels. 2.4 GHz: three non-overlapping 20 MHz channels (11 channels defined in North America, 13 in Europe). 5 GHz: up to 25 non-overlapping 20 MHz channels depending on region, aggregable into 40/80/160 MHz. 6 GHz (Wi-Fi 6E/7): 7 × 160 MHz channels, or 3 × 320 MHz channels for Wi-Fi 7. Wider channels raise the data rate proportionally but concentrate interference and reduce the number of non-overlapping networks.

Step 4 — MIMO. Multiple antennas at both ends create independent spatial streams: spatial multiplexing multiplies throughput by the stream count, while beamforming focuses energy toward a client and extends range (see the 5G section for the beamforming diagram — the principle is identical).

Step 5 — Worked example (the 9.6 Gb/s peak). The standard’s table value for HE160 MCS11 (1024-QAM, rate 5/6) is 1201 Mb/s per stream at 400 ns guard interval (after pilots, training fields and overhead). Eight spatial streams: 8 × 1201 = 9608 ≈ 9.6 Gb/s. Real throughput is ~60–70% of PHY rate after framing, ACKs and retransmissions.

Step 6 — Sources. IEEE 802.11ax defines the rate tables used above; 802.11be (Wi-Fi 7) adds 320 MHz and 4096-QAM.

Example problem

A Wi-Fi 6 client uses 2 spatial streams, an 80 MHz channel, 256-QAM with coding rate 5/6 (MCS9). What is the PHY data rate?

Solution

From the 802.11ax rate table, HE80 MCS9 (256-QAM, 5/6) is 573.5 Mb/s per stream at 800 ns guard interval. Two spatial streams: 2 × 573.5 = 1147 Mb/s ≈ 1.15 Gb/s PHY rate. (Note the coding rate is 5/6 — 802.11 has no 7/8 rate; its rates are 1/2, 2/3, 3/4 and 5/6.)

Bluetooth

Definition. Bluetooth is a short-range (1–100 m), low-power, point-to-point or point-to-multipoint personal-area interface at 2.4 GHz. Bluetooth Low Energy (LE) hops once per connection event, with a connection interval from 7.5 ms to 4 s (up to ~133 hops/s); classic BR/EDR hops 1600 times per second. Data rates: up to 2 Mb/s (LE 2M PHY) or 3 Mb/s (BR/EDR).

Details

Step 1 — Design goals. Bluetooth targets personal-area networking: headphones, keyboards, mice, wearables. The driving constraints are power (µW in sleep, mW transmitting) and cost, not peak throughput — a sensor that must run a year on a coin cell accepts 100 ms of latency to save radio-on time.

Step 2 — Frequency hopping. The 2.4 GHz band is crowded (Wi-Fi, microwave ovens, Zigbee). Bluetooth defends itself with FHSS: 79 × 1 MHz channels (BR/EDR) or 40 × 2 MHz channels (LE), hopping pseudo-randomly. A narrowband interferer only corrupts the occasional hop; the link retransmits and adapts the channel map. The animation below shows a BLE connection hopping across its 37 data channels (37–39 are reserved for advertising); the red channels are corrupted by a fixed Wi-Fi network.

Channel —

Step 3 — Connection events and power. A BLE connection exchanges data only during short connection events, separated by the connection interval (7.5 ms – 4 s, negotiated). One frequency hop occurs per connection event. A longer interval means fewer hops, less radio-on time, lower power, more latency — the central trade-off of BLE scheduling.

Step 4 — Worked example. A BLE mouse with a 100 ms connection interval wakes for ~2 ms per event: a duty cycle of ~2%, averaging tens of µW. A BR/EDR audio link instead streams continuously at 1600 hops/s, accepting ~1 mW for constant throughput.

Step 5 — Sources. The Bluetooth Core Specification defines the hopping sequences, channel map and connection intervals.

Example problem

A Bluetooth LE audio stream (LC3 codec) requires 200 kbps. The BLE LE 1M PHY rate is 1 Mbps. What fraction of the airtime is used for audio?

Solution

200 kbps / 1 Mbps = 20%. The remaining 80% goes to protocol overhead (headers, ACKs, retransmissions) and idle time. With connection events batching the audio every 7.5 ms, the radio is on only during those events, so the energy duty cycle is far lower than the 20% airtime figure suggests.

NFC (Near Field Communication)

Definition. NFC is a short-range (≤ 4 cm), contactless, 13.56 MHz wireless interface for data exchange and payment. It uses inductive coupling (magnetic near field) rather than radiative propagation, with data rates of 106–424 kbps (ISO/IEC 14443).

Details

Step 1 — Near field versus far field. Every antenna has two regions. In the far field, energy radiates away as waves and power falls as 1/r21/r^2. In the near field (within roughly one wavelength: 22 m at 13.56 MHz), the dominant interaction is magnetic coupling between loop antennas, and the coupled energy falls as 1/r31/r^3. That extra power of rr is what confines NFC to centimetres — a security feature as much as a limitation: eavesdropping or relay attacks require proximity.

distance r (cm) coupled power (relative) r = 1 cm radiative 1/r² inductive 1/r³ 4 cm NFC limit: the 1/r³ curve has already fallen ~30 dB below 1/r²

Step 2 — Load modulation. The tag is passive: it has no battery. The reader’s 13.56 MHz field induces a current in the tag’s loop antenna, which powers the tag’s chip. The tag then answers by loading its antenna slightly, which the reader senses as a tiny change in the reader’s own field current — speaking by modulating the reader’s power, not by transmitting.

Step 3 — Worked example. A contactless payment: the phone is held within 4 cm of the terminal. The reader polls at 13.56 MHz; the card responds with its UID and payment data (EMV). The whole transaction takes under a second; the RF exchange itself is a few milliseconds.

Step 4 — Relation to RFID. NFC is a subset of RFID (Radio-Frequency Identification). The distinction: NFC supports peer-to-peer mode (two powered devices take turns as reader and tag), while classic RFID is strictly reader→tag.

Step 5 — Sources. ISO/IEC 14443 defines the A/B modulation and framing; the NFC Forum defines the higher-level modes (P2P, card emulation, NDEF data exchange).

Example problem

An NFC tag answers at 106 kbps. How long does a 16-byte (128-bit) UID take to transmit?

Solution

128 bits / 106 kbps = 128 / 106000 ≈ 1.2 ms. In practice the frame adds a start bit, parity and a 16-bit CRC, so the on-air time is ~2 ms — negligible next to the ~300 ms of the surrounding payment protocol.

Zigbee (IEEE 802.15.4)

Definition. Zigbee is a low-power, low-rate (250 kb/s) mesh networking interface at 2.4 GHz (also 868/915 MHz), built on the IEEE 802.15.4 PHY/MAC: 16 × 5 MHz channels, DSSS with OQPSK, ~10–100 m per hop, designed for years of battery life in building automation and sensor networks.

Details

Step 1 — Niche. Zigbee sits between Bluetooth (higher rate, fewer devices, star topology) and LoRa (kilometre range, bits per second). Its niche: hundreds of battery-powered sensors (lights, locks, thermostats) forming a self-healing mesh in a home or building, each message a few dozen bytes.

Step 2 — The mesh. Three node types: a coordinator (one per network), routers (mains-powered, forward packets), and end devices (battery-powered, sleep almost always, talk only to their parent router). Routing over multiple hops extends coverage far beyond a single 10–100 m radio hop; if a router dies, packets reroute — the dashed link below.

ZC ZR ZR Coordinator Router (mains) Router (mains) End device End device End device End device dashed: alternate route if a router dies (self-healing mesh)

Step 3 — Power discipline. End devices sleep > 99% of the time and wake on a beacon or a schedule. A sensor sending 20 bytes every 60 s at 250 kb/s is on the air for 20×8/250000 = 0.64 ms per minute — a duty cycle of ~0.001%, which is how a coin cell lasts years.

Step 4 — Coexistence. Zigbee shares 2.4 GHz with Wi-Fi and Bluetooth. Its 5 MHz DSSS channels are narrow and low-power; deployments place the network on a 2.4 GHz channel between the Wi-Fi channels (e.g. Zigbee channels 15, 20 or 25 sit between the popular Wi-Fi 1, 6 and 11).

Step 5 — Related low-power and wide-area interfaces. UWB (802.15.4z, ~500 MHz bandwidth at 6–8 GHz) trades range (~10 m) for centimetre-precision ranging — used for digital car keys and asset trackers. LoRa uses sub-GHz ISM bands with chirp spread spectrum to trade rate (kb/s) for kilometres of range in IoT telemetry. GNSS (GPS, Galileo: L-band 1.1–1.6 GHz) is a receive-only wireless interface: one-way satellite broadcasts, position computed from the time-of-arrival of four or more satellites.

Step 6 — Sources. IEEE 802.15.4 defines PHY and MAC; the Connectivity Standards Alliance defines the Zigbee routing and application layers on top.

Example problem

A Zigbee door sensor reports 20 bytes every 60 s. Including a 2× protocol overhead factor, what is its radio-on duty cycle, and why does this matter for battery life?

Solution

Payload on-air time: 20 × 8 / 250000 = 0.64 ms; with 2× overhead ≈ 1.3 ms per 60 s. Duty cycle ≈ 1.3 ms / 60 s ≈ 0.002%. A sensor drawing ~5 mA while transmitting and ~2 µA asleep averages ≈ 5 mA × 0.00002 + 2 µA ≈ 2.1 µA — a 220 mAh coin cell lasts ~12 years in the ideal case, and realistically 2–5 years accounting for polling and retransmissions.

Cellular (5G NR)

Definition. 5G NR (New Radio, 3GPP) is a wide-area cellular wireless interface operating at sub-6 GHz (FR1) and mmWave (FR2: 24–71 GHz). The IMT-2020 peak downlink requirement is 20 Gb/s (and 100 Mb/s for mid-band cell-edge users), reached with wide aggregated bandwidths and 8-layer MIMO.

Details

Step 1 — Flexible OFDM numerology. 5G NR uses OFDM (downlink) and DFT-s-OFDM (uplink, lower peak-to-average power for handsets) with scalable sub-carrier spacing: 15, 30, 60, 120 or 240 kHz. The spacing sets the slot length: a slot is 14 OFDM symbols, so at 15 kHz a slot is 1 ms, at 30 kHz 0.5 ms, at 120 kHz 0.125 ms — finer spacing for wide coverage, coarser for low latency and mmWave.

Step 2 — Massive MIMO and beamforming. Base stations use 64–256 antenna elements. Driving each element with a controlled phase shift makes the wavefronts add constructively in one direction and cancel elsewhere: a steerable beam with ~10·log₁₀(N) dB of array gain (18 dB for 64 elements) aimed at each user. This is what lets the same spectrum serve many users simultaneously without interfering.

64-element array (8 shown), phase-steered beams array user A user B constructive addition in the beam direction: array gain ≈ 10·log₁₀(64) ≈ 18 dB cancellation elsewhere → little inter-user interference

Step 3 — mmWave and slicing. FR2 (24–71 GHz) offers up to 400 MHz per carrier but suffers the frequency term of the path-loss formula plus atmospheric absorption: ~100–200 m cells, suited to stadiums and dense urban hotspots. Network slicing lets one physical network carry multiple virtual networks with different QoS (IoT, URLLC, eMBB).

Step 4 — Worked example. A mid-band deployment: 3.5 GHz, 100 MHz, 4-layer MIMO. Per stream, 100 MHz at 30 kHz spacing gives 273 resource blocks × 12 = 3276 sub-carriers; at 256-QAM (8 bits/symbol) with 14 symbols per 0.5 ms slot, that is 3276 × 8 × 14 / 0.0005 ≈ 734 Mb/s per stream, ≈ 2.9 Gb/s for 4 streams before overhead — consistent with real-world mid-band 5G measurements of 1–2 Gb/s.

Step 5 — Sources. 3GPP TS 38.211 defines the OFDM numerology and resource grid; ITU-R M.2150 (IMT-2020) sets the 20 Gb/s peak-rate requirement.

Example problem

A 5G NR cell uses 100 MHz at 3.5 GHz with 30 kHz sub-carrier spacing. How many sub-carriers are in the channel, and how long is a slot?

Solution

Raw division gives 100 MHz / 30 kHz ≈ 3333, but the resource grid is quantised in resource blocks of 12 sub-carriers with guard bands reserved: 100 MHz at 30 kHz SCS = 273 RBs = 3276 sub-carriers. The slot length scales inversely with the sub-carrier spacing: 14 OFDM symbols give 1 ms at 15 kHz, 0.5 ms at 30 kHz, 0.125 ms at 120 kHz.

Satellite

Definition. Satellite communication links ground stations to satellites in LEO (~550 km), MEO (~8000–20000 km) or GEO (35786 km), typically at 2–50 GHz. LEO constellations (Starlink, OneWeb) deliver broadband internet with 20–60 ms latency; GEO delivers broadcast coverage with ~119 ms one-way propagation.

Details

Step 1 — The geometry sets the latency. One-way propagation delay is slant range / c. The diagram shows the three regimes and the slant range from a ground terminal to a satellite (longer than the altitude, except directly overhead).

Earth ground terminal slant range LEO 550 km slant ≈ 1100–1900 km, one-way ≈ 4–6 ms MEO ~8000–20000 km one-way ≈ 27–70 ms (GNSS lives here) GEO 35786 km one-way ≈ 119 ms, fixed over the equator Orbit radii not to scale. Latency = slant range / c.

Step 2 — Path loss and Doppler. At 12 GHz over a 1200 km LEO slant range, FSPL = 32.44 + 20·log₁₀(1200) + 20·log₁₀(12000) ≈ 169.6 dB; at 20 GHz over 550 km it is ≈ 173 dB. Both ends answer with high-gain antennas: the Starlink user terminal is a phased array (~1280 elements) that steers its beam electronically as satellites cross the sky. A LEO satellite moves at ~7.5 km/s, so the Doppler shift is Δf = v·f/c = 7500 × 20×10⁹ / 3×10⁸ ≈ 500 kHz at 20 GHz — three orders of magnitude beyond a terrestrial mobile cell’s Doppler, and the terminal must track and compensate it continuously.

Step 3 — Latency and TCP. LEO one-way is ~4–6 ms of pure propagation per hop (20–60 ms end-to-end with multiple hops and processing); GEO is ~119 ms one-way, so a single-hop echo (terminal → satellite → gateway) round-trips in ~238 ms, and a user-to-user connection across two GEO hops sees ~480–600 ms RTT. Long RTT inflates the bandwidth-delay product, so TCP needs large windows (or satellite-specific proxies) to keep the pipe full — see Networks.

Step 4 — Worked example. A Starlink user terminal links to a LEO satellite in Ku-band: downlink 10.7–12.7 GHz, uplink 14.0–14.5 GHz (the Ka-band 20/30 GHz links connect satellites to the gateways). The phased array (~1280 elements) hands the beam from satellite to satellite every few minutes as LEO satellites pass overhead; per-user downlink rates are ~50–250 Mbps.

Step 5 — Sources. ITU-R regulates the Ku/Ka spectrum allocations; the CCSDS defines the space-link protocols used above them.

Example problem

A GEO satellite at 35786 km provides a 100 Mbps downlink to a single-hop connection (terminal → satellite → gateway). What is the bandwidth-delay product, and how does a user-to-user GEO connection change the picture?

Solution

One-way propagation: 35786 km / 3×10⁸ m/s ≈ 119 ms. A single-hop echo round-trip is ~238 ms, giving BDP = 100 Mbps × 238 ms ≈ 23.8 Mbit ≈ 3 MB — the TCP window must exceed 3 MB to keep the pipe full. A user-to-user connection crosses two satellite hops (up, down, up, down), so the real RTT is ~480–600 ms and the effective BDP roughly doubles; this is why interactive applications (video calls, gaming) feel poor on GEO and why LEO constellations exist.

Quiz

Example problem

A Wi-Fi 6 router (4×4 MIMO, 160 MHz, 256-QAM, rate 5/6) and a 5G NR cell (4-layer MIMO, 100 MHz, 256-QAM, 30 kHz sub-carrier spacing) both serve a single user. Which provides the higher peak PHY rate, and by what factor?

Solution

Wi-Fi 6: from the 802.11ax rate table, HE160 MCS9 (256-QAM, 5/6, 800 ns GI) is 1147 Mb/s per stream. Four streams: 4 × 1147 ≈ 4.6 Gb/s. (The often-quoted 9.6 Gb/s peak needs 8 streams × 1024-QAM: 8 × 1201 Mb/s.)

5G NR: 100 MHz at 30 kHz SCS = 273 RBs = 3276 sub-carriers. A slot at 30 kHz SCS is 0.5 ms with 14 OFDM symbols. Per stream: 3276 × 8 bits × 14 / 0.5 ms ≈ 734 Mb/s. Four streams: ≈ 2.9 Gb/s.

Wi-Fi 6 is ≈ 4.6 / 2.9 ≈ 1.6× faster in this configuration. The gap is modest because both are OFDM at the same modulation: Wi-Fi wins on channel width per stream, and 5G closes the gap (and exceeds it) with carrier aggregation, wider total bandwidth and 8-layer MIMO to meet its 20 Gb/s IMT-2020 peak requirement.