Safety, Fallback and Teleoperation

fallback · remote assistance · standards · security

Driverless does not mean unattended: every robotaxi fleet runs a remote assistance center behind it. Most remote help is advice, not driving, and a security failure in that link becomes a safety failure.

Escalation ladder when autonomy cannot continue, from most to least frequent: onboard autonomy handles routine driving and most edge cases; the vehicle reaches a minimal risk condition by slowing, pulling over or stopping in lane; remote assistance, where a person advises and the vehicle still drives; remote driving at low speed in constrained zones only; and field response, where staff reach the vehicle and drive or tow it. Security threats apply at every step: GNSS spoofing, loss of the remote link, tampering with over-the-air updates and depot network intrusion. ESCALATION LADDER WHEN AUTONOMY CANNOT CONTINUE Onboard autonomy routine driving, edge cases Minimal risk condition slow, pull over or stop Remote assistance person advises; car drives Remote driving low speed, fenced zones only Field response staff drive or tow it Threats GNSS spoofing, link loss, OTA tampering, depot intrusion
Default fallback
Minimal risk stop
Main remote role
Assistance
China cyber rule
GB 44495
Hub
Autonomy

Finding

Robotaxi operators rarely drive vehicles remotely; remote staff advise, and the vehicle stays responsible for driving

Waymo, Zoox, Tesla and Baidu Apollo Go all run remote assistance centers, but their staff mostly answer questions such as which lane to take around a blockage; the vehicle keeps control. True remote driving is limited to low speeds and constrained areas, such as Vay's rental delivery service in Las Vegas, depots, yards and mines, because network latency and dropouts make it unsafe at road speed.

When a vehicle cannot continue and help is slow, it falls back to a minimal risk condition: slowing, pulling over or stopping in lane. That fallback is designed by the AV developer, but the fleet operator decides where it happens. Depot approaches with designated pull-over spots, one-way flows and protected zones keep a stalled vehicle from blocking everyone else. Power outages are the stress case: when traffic signals fail across a district, many vehicles may request help at once and the remote center becomes the bottleneck.

Security belongs in the same plan. The remote-assistance link, OTA update channel, depot chargers and edge servers are all paths into the vehicle, and GNSS spoofing can push a vehicle off its expected position. The US connected-vehicle rule bars Chinese and Russian automated-driving software from model year 2027, and China's GB 44495 sets mandatory vehicle cybersecurity requirements of its own. See Software-Defined Systems Security for the vehicle side.

Remote modes

Remote operation modes

Teleoperation modes
ModeWhat the operator doesWho uses itTypical use
Remote assistanceOperator answers questions or suggests a path; the vehicle decides and drivesWaymo fleet response, Zoox, Tesla, Baidu Apollo GoMost robotaxi escalations
Remote approvalOperator authorizes or vetoes a maneuver such as entering a work zoneMost robotaxi and trucking operatorsWork zones, closures, police direction
Remote drivingOperator drives the vehicle over a network linkVay (Las Vegas rental delivery); yard and mine operatorsLow-speed yards, depots, mines; latency-limited
Field responseStaff travel to the vehicleAll operatorsCollisions, stalls, failed recoveries

Standards

Safety and security standards

Autonomy safety and cybersecurity standards
AreaStandard or ruleCovers
Functional safetyISO 26262Hardware and software faults
Safety of the intended functionISO 21448 (SOTIF)Hazards from performance limits, not faults
Autonomous product safety caseUL 4600Safety argument for driverless operation
Vehicle cybersecurityISO/SAE 21434; UNECE R155Cyber risk management across the vehicle life
Software updatesUNECE R156Secure, logged OTA updates
China vehicle cybersecurityGB 44495 and GB 44496Mandatory cybersecurity and OTA rules for new types since January 2026
US crash reportingNHTSA Standing General OrderReports of crashes involving ADS and Level 2 systems
US supply-chain securityCommerce connected-vehicle ruleBars Chinese and Russian ADS software from model year 2027 and hardware from model year 2030

Operator levers

What fleet operators control

Fleet operator safety and security levers
LeverActionsEffect
Depot and route designSpeed limits, one-way flows, protected zones, designated pull-over spotsFewer conflict points; safe places to stop
Operating limitsWeather, visibility and hours thresholds; when to suspend serviceKeeps vehicles inside their ODD
ContractsSafety, remote-assistance and security service levels with the OEM or AV partnerVisibility into remote-assist activity and response times
Network securitySegmented depot networks; strong authentication on remote consoles; vendor access controlsLimits how far an intrusion can spread
Incident practiceSynchronized logs, incident definitions, joint drills including link-loss scenariosSingle events become system fixes

Sources

Sources and scope

Scope
Fleet Autonomy Safety, Fallback, Teleoperation and Security
Sources
ISO; UL; UNECE; China MIIT and SAMR (GB 44495, GB 44496); NHTSA; US Commerce Department (January 2025); operator disclosures
Updated
October 2026