V2X Spectrum and the Regulatory Landscape

Spectrum Is the Binding Constraint

The algorithms and architectures of the preceding sections are abundant. The binding constraint on V2X deployment is spectrum — the frequency bands allocated by regulators for vehicular use. This section is a brief tour of the global V2X spectrum landscape and its implications for OTFS-V2X deployment. It is not a legal document; it is a technical orientation.

Definition:
V2X Frequency Bands

V2X operates across five frequency tiers:

5.9 GHz ITS band: Allocated globally for V2V/V2I. Bandwidth: 75 MHz (US pre-2020), now 30-40 MHz after 2020 reallocation. Used by DSRC (legacy) and C-V2X. Regulation: FCC Part 95 (US), ECC Rec. 08(01) (Europe).

Sub-6 GHz cellular: 600 MHz, 700 MHz, 2.6 GHz, 3.5 GHz. Shared with cellular data. Used by 5G NR sidelink (Rel. 16+). Bandwidth: typical 20-100 MHz per operator.

mmWave V2X: 24 GHz, 28 GHz, 60 GHz, 77 GHz. 77 GHz is the automotive radar band — dual-use for radar + comms (ISAC) is regulatory-feasible. Bandwidth: up to 4 GHz (60 GHz ISM) or 1 GHz (77 GHz automotive).

Sub-THz: 100+ GHz. Experimental. Expected regulatory decisions 2028+.

Unlicensed: 2.4 GHz, 5.8 GHz, 6 GHz (Wi-Fi). Secondary use for vehicle infotainment. Not for safety.

Theorem: Spectrum-Bandwidth-Range Tradeoff

For a V2X link at carrier $f_0$ with bandwidth $W$ , the maximum range $r_{\max}$ at fixed link SNR is $r_{\max}^2 \;\propto\; \frac{P_t G_t G_r}{W} \cdot f_c^{-\alpha},$ where $\alpha = 2$ (free-space) to $4$ (in-vehicle dense urban) is the path-loss exponent.

Consequence. At constant $W$ , higher frequency gives shorter range. At constant $f_0$ , more bandwidth gives shorter range (more noise). Trading off:

5.9 GHz, 10 MHz: range 300 m at 20 dBm Tx. Legacy DSRC/C-V2X.
77 GHz, 1 GHz: range 200 m at 20 dBm Tx. Automotive radar range extended to V2X.
28 GHz, 200 MHz: range 500 m at 30 dBm Tx. BS-to-vehicle mmWave V2I.

Each V2X tier has a specific range regime — they complement rather than compete.

The spectrum-bandwidth-range triangle is a classic: you can have two, but not three. Low-band gives you range + large bandwidth but over crowded spectrum. mmWave gives you bandwidth but short range. The V2X deployment thus uses all three tiers: low-band for long- range safety, mmWave for short-range high-data-rate cooperative perception. No single band serves all use cases.

Proof

Link budget

Received SNR = $P_t G_t G_r / (kTW) / L$ , where $L$ is pathloss $\propto r^\alpha f_c^{-\alpha}$ (Friis + exponent).

Range for target SNR

$r^\alpha = P_t G_t G_r / (kTW \cdot \mathrm{SNR}_{\text{target}} \cdot f_c^\alpha)$ .

Squaring

$r^{2} =$ proportional to $1/W \cdot f_c^{-\alpha}$ . Tradeoff as stated. $\blacksquare$

Definition:
Regulatory Frameworks

V2X regulation spans several jurisdictional levels:

Spectrum allocation:

ITU (International Telecommunications Union): global allocation via WRC (World Radiocommunication Conferences). WRC-23 was the most recent for V2X.
Regional: FCC (US), Ofcom (UK), CEPT/ECC (Europe), NTIA (US DoD).

V2X-specific rules:

US: FCC Part 95 for 5.9 GHz V2X. Transition to C-V2X mandated 2023+.
Europe: ETSI EN 302 686 for DSRC; C-V2X under 3GPP governance.
China: YD/T 3077 for C-V2X. OTFS testbeds allowed under experimental licenses.
Japan: Ministry of Internal Affairs allocation for V2X 760 MHz band (unique to Japan).

Safety certifications:

FMVSS (US): Federal Motor Vehicle Safety Standards. 2023 NHTSA guidelines require V2V for new vehicles by 2028.
EU: EU-V2X; mandatory by 2025 for new vehicle types under Euro NCAP.
China: similar mandates emerging.

Privacy regulations:

GDPR (Europe): pedestrian tracking data classification as personal data. Anonymization required.
CCPA (California): similar restrictions on vehicle tracking.

Example: EU V2X Mandate: Timeline and Spec

EU's V2X deployment mandate timeline:

2022: recommendation for Euro NCAP safety assessment.
2025: mandatory V2V for new vehicle types.
2028: mandatory for all new vehicles.

Discuss the implications for OTFS-V2X deployment.

Solution

Pre-2028

OEMs deploy C-V2X (Rel. 16+) on 5.9 GHz sub-6 GHz. Safety-critical V2V operational. OTFS-V2X still experimental — no regulatory path yet.

2025-2028 transition

NR-V2X Rel. 17/18 rolls out (mmWave sidelink). Some cooperative perception prototypes. OTFS testbeds in premium automakers (Mercedes, BMW, etc.).

2028+

3GPP Rel. 21 includes OTFS-V2X for high-mobility (closing speed > 200 km/h). Mass deployment begins.

Regulatory path

EU V2X regulations will include OTFS once 3GPP formalizes it. Transition: existing C-V2X-equipped vehicles will migrate via OTA updates (for NR-V2X) or remain on legacy OFDM (pre-NR vehicles). OTFS-specific certification expected 2027-2028.

Infrastructure

Roadside units (RSUs) must support OTFS; some will upgrade from C-V2X. Cellular BS: 5G NR Release 18+ can add OTFS-V2X via software. Full infrastructure readiness: 2030.

V2X Spectrum Comparison

Band	Bandwidth	Range	Use Case	OTFS-Ready
5.9 GHz ITS	30-75 MHz	300 m	Safety V2V (DSRC/C-V2X)	Possible but low-gain
Sub-6 GHz cellular	20-100 MHz	5-10 km	V2I / V2N	Natural fit
24-28 GHz mmWave	100-200 MHz	500 m	V2I (BS-to-vehicle)	Natural fit
77 GHz radar	1-4 GHz	200 m	V2V ISAC + radar	Decisive win
60-120 GHz WiGig/6G	10-20 GHz	100 m	V2V cooperative perception	Decisive win

V2X Spectrum Usage Visualization

Plot the range-vs-bandwidth tradeoff across V2X bands (5.9 GHz to 120 GHz). Highlight OTFS-ready regions (where Doppler makes OFDM unreliable). Sliders: vehicle closing speed, target SNR.

Parameters

Closing velocity (km/h)200

Target SNR (dB)20

Theorem: mmWave V2X Adoption Bottleneck

For mmWave V2V deployment at scale, the bottleneck is not bandwidth (abundant in mmWave bands) but array cost. A cost- effective V2V transceiver with $N_t = N_r = 16$ - $32$ antennas at 77 GHz requires:

CMOS arrays ( $\leq \$50$ per unit at scale).
Integrated LNA/PA pre-calibrated.
Baseband with 100-Mbps DD-domain processing.
Total unit cost: $\sim \$300$ - $\$500$ in mass production.

Current 2024 cost: $\sim \$1{,}500$ - $\$2{,}000$ per unit (automotive radar front-end prices). Projected 2028 cost: $\sim \$500$ - $\$700$ . Below $\$500$ , OTFS-V2V becomes deployable in economy vehicles.

Consequence. The economic driver for OTFS-V2V is not performance (which is decisive at $\geq 200$ km/h) but cost — waiting for mmWave arrays to become affordable to mass-market. Expected: 2030+.

mmWave arrays are currently expensive because of manufacturing complexity — 16-32 phase shifters, calibration, thermal management. CMOS scaling has reduced costs by ~10× per decade; another 5-10× reduction is needed for OTFS-V2V mass deployment. The clock for this is set by semiconductor scaling, not wireless standards.

Proof

Cost components

RF array: $\$20$ - $\$30$ per unit in volume (CMOS). Baseband SoC: $\$50$ - $\$100$ . Housing + calibration: $\$100$ - $\$200$ . Total: $\$300$ - $\$500$ at scale.

Current state

2024 automotive radar front-ends: $\$1$ k- $\$2$ k. Reflects low production volume + complexity.

Scaling projection

Moore's law: ~30% cost reduction per year for CMOS. 4-year horizon: $\sim 50\%$ reduction. 2028 target: $\$500$ - $\$700$ .

Mass market

Below $\$500$ : OTFS-V2V deployable in all new vehicles. Timeline: 2030+. $\blacksquare$

🔧Engineering Note

V2X Deployment Playbook (2024-2030)

Operational timeline for V2X deployment (2024-2030):

2024-2025: C-V2X (Rel. 16) on 5.9 GHz. Safety V2V messages. Partial cooperative perception.

2025-2027: NR-V2X (Rel. 17/18) adds mmWave sidelink. 5G-V2X operator trials. OTFS-V2X prototypes at premium OEMs.

2028: 3GPP Rel. 21 includes OTFS-V2X. Regulatory frameworks update (FCC, CEPT). First commercial OTFS-V2X vehicles.

2028-2030: Mass mmWave array manufacturing drives cost below $\$500$ per unit. OTFS-V2X rollout in premium and mid-market.

2030+: OTFS-V2X in economy vehicles. 5G/6G V2X reaches maturity. Cooperative perception standard in all vehicles.

Beyond 2030: sub-THz V2X (100+ GHz) for cooperative perception in dense urban. Potentially new standards (OTFS++, or hybrid OFDM-OTFS frameworks). Research topic.

Observations:

Deployment lags standardization by 3-5 years.
Safety use case drives adoption; entertainment/commercial use cases follow.
Spectrum is the binding constraint; waveform choice secondary.

Practical Constraints

•
2024: C-V2X baseline
•
2028: OTFS-V2X standardization
•
2030+: mass mmWave + OTFS-V2X

Historical Note: IEEE 802.11p and the DSRC Saga

IEEE 802.11p (DSRC) was finalized in 2010 as an amendment to the WLAN standard, adding vehicular-specific features: lower latency, asymmetric power, outside-of-BSS operation. The FCC allocated 75 MHz at 5.9 GHz in 1999 for this purpose.

Deployment, however, was slow. Key factors:

Vehicle OEMs waited for industry-wide standards before committing.
Roadside infrastructure deployment was sparse (most highways had no RSUs).
Safety benefits were hard to quantify to insurance-driven OEMs.
Cellular operators competed with DSRC via C-V2X.

The 2020 FCC decision to reallocate 5.9 GHz (45 MHz for C-V2X, 30 MHz for unlicensed) effectively ended DSRC in the US. Europe continued with ITS-G5 (DSRC variant) for several more years but is now migrating to C-V2X.

Lesson for OTFS-V2X: incremental standardization tied to proven cellular success (as with C-V2X) is more successful than greenfield standards. OTFS will integrate into the 5G/6G sidelink framework — not stand alone.

Cooperative Perception via OTFS-ISAC Platooning and Intersection Management