Charger-Based Vehicle Update Validation With Iterative Rollback
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle software validation methods are limited by the availability of test vehicles and chargers, failing to cover all in-market variations, leading to potential defects in software and charging capabilities.
Innovation Solution
An iterative software updating approach using a charger monitoring server to identify vehicles for updates, send software updates in cycles, and revert if success thresholds are not met, ensuring statistically relevant samples from diverse market populations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional test fleet methods are used for software validation, then testing can be performed with controlled environments, but the number of test vehicles and chargers is limited to fewer than a dozen, failing to cover all in-market variations
Solution Approach 1:
The patent transforms consumer vehicles into self-testing units that automatically perform software validation during normal charging operations. The vehicles and chargers serve themselves by conducting mutual software version verification and defect reporting without requiring dedicated test fleet infrastructure, thereby achieving comprehensive market coverage using the existing consumer vehicle population
Solution Approach 2:
The patent enables consumer vehicles and chargers to perform dual functions: their primary charging/charging-providing roles plus software validation testing. This multi-functionality allows the same vehicles and chargers to serve both operational and testing purposes simultaneously, eliminating the need for separate test fleets and achieving broad validation coverage
2Reliability
If iterative software updating cycles are implemented with comprehensive testing, then software defects can be identified early across diverse market conditions, but the update validation process becomes more complex
Solution Approach 1:
The patent segments the software validation process into distinct automated phases: software version identification, compatibility verification, defect detection, and iterative update cycling. Each phase is handled independently by the charger monitoring server, which manages multiple vehicles through standardized procedures, thereby reducing overall process complexity while maintaining comprehensive validation
Solution Approach 2:
The patent implements continuous feedback loops where test results from each software update cycle automatically inform subsequent validation decisions. The charger monitoring server receives defect reports from vehicles and chargers, analyzes the feedback data, and uses it to determine whether to proceed with further updates or revert changes, creating a self-regulating validation system that reduces manual intervention complexity
Data Source
AI summary
Iterative software updating using consumer vehicles includes sending update requests to perform software updates to vehicles and charging stations in a cycle of testing, wherein the vehicles are included on an update list; receiving testing reports from the vehicles and charging stations; responsive to the testing reports indicating success above a minimum success threshold, continuing to roll out the software update in an additional cycle of testing; and otherwise, sending reversion update requests to roll back the software update to the vehicles and the charging stations.