Exercises
ex-otfs-ch15-01
EasyDefine V2X and list the four link types. For each, give one typical use case.
V2I, V2V, V2P, V2N.
Definition
V2X = Vehicle-to-Everything: an umbrella for vehicular wireless links.
Link types and use cases
V2I: vehicle-to-infrastructure. Example: traffic signal coordination, RSU-based tolling. V2V: vehicle-to-vehicle. Example: platooning, cooperative braking. V2P: vehicle-to-pedestrian. Example: collision warning to smartphone. V2N: vehicle-to-network. Example: cellular OTA software updates, streaming.
ex-otfs-ch15-02
EasyCompute the V2V closing Doppler at 77 GHz for two vehicles each traveling at 100 km/h directly toward each other.
, .
Relative velocity
km/h = 55.6 m/s.
Wavelength
mm.
Doppler
Hz = 14.3 kHz.
Comparison
14.3 kHz vs 120 kHz (5G NR mmWave subcarrier): of subcarrier. Significant ICI for OFDM.
ex-otfs-ch15-03
EasyList three reasons V2V mobile is harder than V2I mobile.
Both endpoints moving, Doppler doubles, LOS/NLOS transitions.
Doubled Doppler
: Doppler doubles (relative to V2I where BS is stationary).
Bidirectional maneuver
Either vehicle can change trajectory; prediction harder.
NLOS frequency
Vehicles pass each other, adjacent trucks, signs β rapid LOS-NLOS transitions.
ex-otfs-ch15-04
MediumState the string stability condition for an OTFS-V2V platoon and verify it for vehicles, ms, reliability .
s.
Condition
.
Compute
s.
Compare
s. Condition: ? FALSE. Platoon is NOT string-stable for and .
Remediation
Need tighter reliability. For stability: , i.e. . Trivially satisfied at . Actually the inequality is reversed: smaller is worse. Condition is that is bounded β which for a safe aero constant requires . For our case: need . Our holds marginally. Actually the physical stability requires that packet losses do not accumulate β bound , i.e. : vs . Violated.
Interpretation
is too loose for 5-vehicle platoon. Need or better loss-handling (retransmission).
ex-otfs-ch15-05
MediumFor a 77-GHz V2V link at 20-m range, estimate the link budget: computed Tx power, antenna gain, pathloss, received SNR.
Use Friis. .
Pathloss
= 96 dB.
Link budget
Tx power: 20 dBm. Tx antenna gain (8-element): 12 dB. Rx antenna gain: 12 dB. Pathloss: -96 dB. Noise floor (100 MHz): -174 + 80 + 3 = -91 dBm (incl. 3 dB NF). SNR = 20 + 12 + 12 - 96 - (-91) = 39 dB.
Feasibility
Ample SNR for high-order modulation (64-QAM at 20+ dB), supporting 1 Gbps data rate at 100 MHz bandwidth.
Range limitation
Range is set not by noise but by obstacles. At 20 m, LOS probability > 95%. Beyond 100 m: NLOS probability rises sharply, link may degrade.
ex-otfs-ch15-06
MediumCompute the bandwidth needed for cooperative perception at a T-intersection with 10 vehicles, each broadcasting DD-scene at 100 Hz.
Per-vehicle scene: ~7 kbps. Total: K Γ 7 kbps / SE.
Per-vehicle
Each vehicle: 7 kbps.
Total
10 vehicles: 70 kbps.
Bandwidth
With SE 4 bps/Hz: 70 kbps / 4 = 17.5 kHz.
Context
Tiny compared to 100 MHz V2V allocation. CP has negligible bandwidth overhead; constraint is latency and reliability.
ex-otfs-ch15-07
MediumA pedestrian is occluded from vehicle A by a parked truck but visible to vehicle B. Describe how OTFS-ISAC + V2V CP resolves this scenario.
Think about the data flow and fusion.
Vehicle B senses
Vehicle B's OTFS-ISAC detects pedestrian with standard algorithm: position, velocity, class.
V2V broadcast
B broadcasts DD-scene with pedestrian entry.
Vehicle A receives
A's V2V receiver decodes B's scene. Transforms pedestrian position to A's coordinate system using B's location + timestamp. Fuses with A's own sensing (which shows no pedestrian). Flags pedestrian as "remote-only" / "unconfirmed".
A's decision
A slows or changes lane to avoid potential pedestrian. Does not rely on unconfirmed target for aggressive maneuvers. Full confirmation when truck clears and A sees pedestrian.
Gain
Without CP: A sees pedestrian only at LOS range (~10 m), emergency braking required. With CP: A's decision happens at ~50 m range, smooth avoidance.
ex-otfs-ch15-08
MediumExplain why V2X safety message reliability must be (one failure per messages) rather than just .
Think about the number of vehicles and the duration of typical drives.
Message frequency
V2V safety messages: 100 Hz frame rate. Each vehicle sends 100 messages per second.
Per-hour messages
3600 seconds Γ 100 = 360{,}000 messages per vehicle per hour.
Catastrophic-outcome threshold
Collision risk tolerable if in hours of driving. Conservatively: per message failure.
Required reliability
Per-message: . Factoring in multiple messages needed for a collision event (several frames), per-message reliability of is the practical engineering target.
Consequence
OFDM at high mobility achieves - reliability β unsafe. OTFS at - β safe.
ex-otfs-ch15-09
MediumDerive the range-bandwidth tradeoff for a V2X link at different carrier frequencies.
Friis + path-loss exponent.
Link equation
, where is environmental loss factor.
SNR
.
Target SNR bound
For target SNR = : . .
Tradeoff
. Doubling frequency halves range; doubling bandwidth reduces range by .
Examples
- 5.9 GHz, 10 MHz: range 1 km.
- 77 GHz, 1 GHz: range 90 m.
- 28 GHz, 100 MHz: range 400 m. Each band has specific range regime.
ex-otfs-ch15-10
HardFor a 4-truck platoon, derive the aerodynamic drag reduction as a function of inter-truck distance.
Drag reduction follows a saturating curve vs spacing.
Empirical model
Drag reduction , where (25% at zero spacing), m (characteristic scale).
Per-truck
Truck 1 (lead): no savings. Truck 2: = 0.25 Β· 0.86 = 22% (if d = 5 m). Trucks 3, 4: similar.
Platoon average
Average savings: (0 + 22 + 22 + 22)/4 = 16.5%.
Verified number
Matches industry reports of ~15-20% fuel savings for 4-truck platoons at 5-10 m spacing.
ex-otfs-ch15-11
HardShow that OTFS-V2V is necessary (not just sufficient) for string- stable platooning at closing speeds above 200 km/h.
Compare OFDM's error floor to the required reliability.
Required reliability
For platoon, s, ms (baseline OFDM): , i.e. .
OFDM reality
At 200 km/h closing, OFDM BER floor ~ at 20 dB SNR. Packet reliability (100-byte packet, uncoded): . Way below 0.29.
OTFS
BER at same SNR (due to DD diversity). .
Conclusion
OFDM cannot achieve required platoon reliability at 200+ km/h. OTFS can. Hence OTFS is necessary.
ex-otfs-ch15-12
HardA 4-way intersection has 10 vehicles approaching. Design the decision protocol for collision-free crossing using OTFS-V2V cooperative perception.
Priority based on: arrival time, emergency vehicle status, pedestrian presence.
Broadcast
Each vehicle broadcasts: position, velocity, intended path (straight/turn), ETA at intersection center.
Conflict detection
Protocol: if two vehicles' intended paths conflict (cross at same time within tolerance), resolution needed. Detect via geometric check: do trajectories intersect within 1-2 s window?
Priority rule
First-come-first-served baseline. Override: (i) Emergency vehicle (lights/siren): immediate priority. (ii) Pedestrian in crosswalk: all vehicles yield. (iii) Larger vehicle: smaller yields (for safety).
Execution
Prioritized vehicle accelerates normally. Yielding vehicles slow to give -second separation. RSU monitors compliance; overrides if vehicles violate.
Failure mode
If V2V messages lost or ambiguous: all vehicles default to stop-sign behavior. Safety margin: second.
ex-otfs-ch15-13
HardFor an OTFS-V2V link, derive the required SNR to achieve packet reliability for a 100-byte safety message.
Use the OTFS BER formula and packet-reliability relationship.
Packet reliability
100-byte packet = 800 bits. Assuming uncoded BPSK, packet error rate = for small BER.
BER requirement
For packet reliability: BER .
OTFS BER formula
. For : . . . . .
SNR in dB
10 log(7.2) = 8.6 dB. Required SNR: ~9 dB. Coding (rate 0.5): relaxes to ~5 dB. Comfortable margin at typical V2V SNR of 20-30 dB.
Comparison to OFDM
OFDM diversity = 1: BER . For same packet reliability: dB. Impossible at V2V link margin. Hence OFDM cannot deliver at high mobility.
ex-otfs-ch15-14
HardAnalyze the spectral efficiency impact of V2V sidelink on V2I uplink in a shared mmWave band. Compute the interference.
V2V transmits at nearby spectrum; interference to BS at V2I uplink.
Scenario
BS serving V2I at 28 GHz. Vehicle transmits V2V sidelink to another vehicle on adjacent channel or overlapping band.
Interference
V2V Tx power dBm. BS receives V2V signal at distance : dBm. For m: dBm β well above BS noise floor (-91 dBm/MHz).
Isolation
Without isolation, V2V interferes severely with V2I. Mitigation: frequency division (V2V on separate channel), code division (different scrambling), spatial separation (BS beamforming nulls toward V2V).
Design rule
In shared-spectrum deployments, adjacent-channel isolation must exceed dB. Achievable with proper filter design. Or use separate bands: V2V on 77 GHz (automotive), V2I on 28 GHz (cellular mmWave) β frequency-isolated by band design.
ex-otfs-ch15-15
HardCompare the energy consumption (Watts) of a vehicle's V2V transceiver running OTFS vs OFDM.
OTFS has higher baseband compute but lower PA peak power.
Baseband compute
OFDM: ops/s at mmWave. OTFS: ops/s (3Γ more due to DD-grid processing). Baseband SoC: 1-2 W for OFDM; 2-4 W for OTFS.
RF/PA
Target radiated power 20 dBm (100 mW) average. OTFS PAPR ~7 dB; OFDM PAPR ~8-10 dB. OFDM requires 10-12 dB back-off; OTFS requires 7 dB. PA efficiency: 30% at back-off. OTFS: 100/0.3 Γ 5 dB = ~500 mW PA input. OFDM: ~800 mW PA input.
Total
OFDM: 1-2 W (BB) + 0.8 W (PA) = 1.8-2.8 W. OTFS: 2-4 W (BB) + 0.5 W (PA) = 2.5-4.5 W.
Comparison
OTFS uses more power than OFDM. However: OTFS requires no re-transmission (high reliability), while OFDM at high mobility requires re-transmissions. Net energy per delivered packet: OTFS is roughly equal or less.
ex-otfs-ch15-16
HardDesign a hybrid V2X architecture using OTFS for safety-critical V2V and OFDM for infotainment V2N. Specify the protocol stack.
Think about layering and service classification.
Service tiers
Tier 1 (safety): V2V BSM, EEBL, platooning control. Latency ms, reliability . Tier 2 (cooperative perception): V2V scene sharing. Latency 10 ms, reliability . Tier 3 (infotainment): V2N streaming, software updates. Latency 100 ms, reliability .
Waveform assignment
Tier 1: 77 GHz OTFS sidelink. Tier 2: 77 GHz OTFS sidelink or cellular OTFS-V2X. Tier 3: 28 GHz 5G NR OFDM uplink/downlink.
Protocol stack
PHY: per-tier waveform. MAC: 5G NR-V2X sidelink for T1/T2, 5G NR uplink for T3. Network: IPv6 for all. Transport: UDP for T1 (low overhead), TCP for T3. Application: DENM/BSM (ETSI ITS) for T1, HTTP for T3.
Transitions
Vehicle software selects tier per application. Runtime reallocation if link quality changes. Fallback: if OTFS sidelink fails, T1 drops to C-V2X OFDM (with latency penalty but graceful degradation).