Remote Driving Service Termination With User Consent Mediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current remote driving services face challenges in smoothly ending and charging for services that include tasks beyond reaching the destination, such as unloading or when occupants fail to exit the vehicle, leading to unnecessary service continuation and payment issues.
Innovation Solution
A remote driving service processing device that includes a server mediating consent between the service requester and driver to end the service when the vehicle arrives at the destination, and facilitates charging and payment through a dedicated terminal, ensuring services are concluded based on agreements between parties.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the vehicle arrives at the destination position, then the transportation service is completed, but the remote driving service cannot be ended if additional services (unloading, occupant exit) are required
Solution Approach 1:
The system performs preliminary actions by having the remote driver send an end service request upon vehicle arrival, and the management server proactively checks whether service termination conditions are met before the service naturally concludes. This allows the system to prepare for service termination in advance, preventing unnecessary continuation when additional services are not actually required.
Solution Approach 2:
The management server implements a feedback mechanism by continuously monitoring service status and comparing it against predefined termination conditions. When the vehicle arrives at the destination, the server receives location information and determines whether service ending conditions are satisfied, then provides feedback by either allowing service termination or requesting continuation based on the unloading status and occupant exit status.
2Reliability
If the service continues until all tasks are completed, then service quality is maintained, but charging and payment cannot be smoothly performed
Solution Approach 1:
The system performs preliminary determination of service termination by the management server before actual service conclusion. The server checks whether termination conditions are met and makes a preliminary decision on service ending, which enables the charging and payment processes to be initiated in advance rather than waiting for all tasks to fully complete.
Solution Approach 2:
The management server acts as an intermediary between the service execution (remote driving) and the billing system. It mediates the service termination decision by evaluating completion conditions and coordinating between the remote driver's requests, the service status, and the charging institution, enabling smooth transition to payment processing.
3Ease of operation
If the service ends automatically when vehicle arrives, then charging is simplified, but flexibility in service operation is reduced
Solution Approach 1:
The service termination mechanism is made dynamic rather than static. Instead of automatic termination upon arrival, the system adaptively determines whether to end service based on real-time conditions such as unloading status and occupant exit status. The management server dynamically evaluates termination conditions and adjusts the service end decision accordingly, providing both automation and flexibility.
Solution Approach 2:
The system changes the termination condition parameters from a simple location-based criterion (vehicle arrival) to a multi-parameter evaluation including unloading completion status and occupant exit status. This parameter transformation allows the service to maintain flexibility while enabling more accurate determination of when termination and charging should occur.
Data Source
AI summary
A remote driving service processing device includes a general user terminal by which a remote driving service is requested for moving a vehicle to a destination, a remote operation terminal by which the vehicle is remotely operated, and a server that, if the vehicle does not satisfy a requirement for ending the remote driving service when the vehicle arrives at the destination, sends an and permission request to end the remote driving service, which is received from the remote operation terminal, to the general user terminal, and, when receiving a consent to end the remote driving service from the general user terminal as a response to the end permission request, sends the consent to end to the remote operation terminal and ends the remote driving service.