Tele-Operated Driving Triggers for Predictive Session Setup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current communication standards for tele-operated driving (ToD) lack triggers and APIs for initiating support from a vehicle to a remote driver, and do not adequately describe the communication of ToD requirements between the vehicle and remote driver, leading to inefficiencies in establishing ToD sessions.
Innovation Solution
The implementation of triggers and application programming interfaces (APIs) that allow vehicles to predict and adapt to upcoming ToD events, enabling the selection of remote drivers and quality of service (QoS) for network support, and facilitating communication between V2X service providers and mobile network operators to establish ToD sessions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If communication standards for tele-operated driving are established without triggers and APIs, then the system structure remains simple, but the efficiency of establishing ToD sessions deteriorates
Solution Approach 1:
The patent implements prediction functionality that identifies upcoming ToD events before they occur, allowing the system to prepare and establish communication sessions in advance. This preliminary action enables more efficient session establishment by proactively triggering ToD support rather than reactively responding to events.
Solution Approach 2:
The patent introduces triggers and APIs as intermediary components that mediate between vehicle systems and remote driver support systems. These intermediaries facilitate structured communication and session establishment, improving efficiency by providing standardized interfaces without requiring complex direct system-to-system integration.
2Reliability
If triggers and APIs are implemented for ToD support, then the reliability of communication between vehicles and remote drivers is improved, but the device complexity increases
Solution Approach 1:
The patent implements trigger mechanisms that provide feedback loops between vehicle conditions, prediction outcomes, and ToD session establishment. This feedback system ensures reliable communication by continuously monitoring system state and automatically initiating appropriate ToD support when conditions warrant, thereby improving reliability through structured feedback rather than ad-hoc communication.
3Productivity
If prediction and adaptation functionality is added to anticipate ToD events, then the efficiency of ToD service delivery is improved, but the loss of processing time increases
Solution Approach 1:
The prediction functionality operates in advance of actual ToD events, performing analysis and preparation during periods when processing time is available but not critical. By completing prediction and adaptation tasks preliminarily, the system delivers ToD services more efficiently when needed without incurring time losses during critical operational moments.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method is performed by a first server communicatively connected to a network for supporting tele-operated driving of a vehicle. The method includes receiving a request from a tele-operated driving application client by the client device in the vehicle for tele- operated driving support. The client processes the request and sends a trigger request for teleoperated driving to the first server. This request includes a trigger and information for supporting a tele-operated driving event. The first server processes the request to identify a second server for providing support for the Tele-operated driving event, wherein the processing is based on parameters of the network for providing tele-operated driving support. Finally the first server will set-up a tele-operated driving session between the second server and the application client. The first server may also predict whether a tele-operated driving event is likely in a future time period based on prediction information obtained from one or more of the vehicle, the second server, a network server, and a third party application server.