Remote Assistance or Remote Driving: The Impact of Operational Design Domains on ADS-Supporting Systems Selection
Ole Hans, Benedikt Walter

TL;DR
This paper presents a structured approach for selecting between remote driving and remote assistance systems for automated driving, based on operational design domains and use case analysis, to improve decision-making in ADS support system deployment.
Contribution
It introduces a systematic framework utilizing the PEGASUS method to evaluate and choose the appropriate remote support system based on ODD and use case considerations.
Findings
Framework effectively guides system selection based on ODD analysis
Structured criteria improve decision consistency for ADS support systems
Application of PEGASUS enhances understanding of operational domains
Abstract
High level Automated Driving Systems (ADS) can handle many situations, but they still encounter situations where human intervention is required. In systems where a physical driver is present in the vehicle, typically SAE Level 3 systems, this intervention is relatively straightforward and is handled by the in-vehicle driver. However, the complexity increases for Level 4 systems, where, in most cases, no physical driver remains in the vehicle. The two common industry solutions for this challenge are the integration of a remote support system, such as a Remote Driving System (RDS) or Remote Assistance System (RAS). While it is clear that ADS will require one of these systems, it is less clear how the suitability of either system for a particular ADS application should be evaluated. Currently, the selection process often focuses on system architecture as well as its design and integration…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
