Road Usage Charging Validation via Certification Server
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current road usage charging systems lack effective validation methods to ensure accurate computation and verification of charges, particularly in complex geographic areas with varying fee structures, which can lead to inefficiencies and potential misuse of infrastructure funding.
Innovation Solution
A vehicle-based system that includes a human-machine interface and hardware processor to enter a testing mode, compute RUC charges based on map and fees information, and generate reports for verification, allowing for itemized reporting and validation across multiple charging domains, with the option to send reports directly to a certification server for validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If road usage charging systems are deployed to compute charges based on map and fees information across multiple charging domains, then the ability to fund infrastructure maintenance and operations is improved, but the complexity of validating charge computation accuracy and ensuring correct funding allocation worsens
Solution Approach 1:
The patent introduces a certification server as an intermediary between the RUC application and the RUC service provider. This server receives charge computation results from the vehicle's RUC application, validates them against expected values, and only then forwards validated charges to the service provider for funding allocation. This intermediary layer simplifies the validation complexity by centralizing verification functions.
Solution Approach 2:
The system implements feedback mechanisms where the certification server validates charge computations and provides verification results back to the system. This feedback loop ensures that charge computations are accurate before funding is allocated, creating a self-correcting system that maintains integrity without requiring complex external validation processes.
2Reliability
If RUC systems process charges for routes traversing multiple charging domains with varying fee structures, then the comprehensiveness of charge coverage is improved, but the difficulty of detecting and measuring computation accuracy worsens
Solution Approach 1:
The system performs preliminary actions by pre-configuring the certification server with expected charge values and validation rules before the vehicle begins its journey. The server is prepared with the fee structures of multiple charging domains, allowing it to validate computations in real-time without complex on-the-fly analysis.
Solution Approach 2:
The patent segments the charge validation process into distinct components: individual charge computations for each charging domain, itemized reports for each domain traversed, and aggregate validation at the certification server. This segmentation makes it easier to detect and measure accuracy by breaking down the complex multi-domain computation into verifiable discrete units.
3Ease of operation
If vehicles send charge reports directly to RUC service providers, then the simplicity of the reporting process is improved, but the risk of undetected computation errors and potential misuse of infrastructure funding worsens
Solution Approach 1:
The certification server acts as a mandatory intermediary between vehicles and RUC service providers. Vehicles still send reports through a straightforward process, but the certification server automatically validates each report before it reaches the service provider. This maintains ease of operation for vehicles while adding a reliability layer that prevents erroneous charges from reaching the funding system.
Data Source
AI summary
Performing validation of road usage charging (RUC) systems is provided. A hardware processor of a vehicle receives, from an HMI of the vehicle, input to enter into a testing mode in which a test of RUC functionality of the vehicle is to be performed. In the testing mode, RUC charges are computed for a route from a start location to an end location, based on map and fees information for the test. One or more reports of the charges are generated for verification of the RUC functionality, the charges being verifiable based on the route and the map and fees information being defined for the test.