Infotainment Software Verification Flow Map
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software verification methods for in-vehicle infotainment systems are inefficient and fail to adequately verify software updates based on actual user scenarios, particularly for newly added or changed screens.
Innovation Solution
A software verification method and apparatus that generates a flow map based on internal logs and state information, updates it with new software specifications, and reconfigures it to estimate usage frequency of new screens, allowing for random tests to verify software changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional software verification methods are used, then verification can be performed based on design specifications, but verification efficiency is low and actual user scenarios are not adequately covered
Solution Approach 1:
The patent creates a virtual flow map that copies and models actual user operation scenarios from big data, allowing verification to be performed on this virtual model rather than requiring extensive real-world testing. This copying approach maintains scenario authenticity while improving verification efficiency
Solution Approach 2:
The patent performs preliminary analysis of big data to extract user operation patterns and construct flow maps before actual software verification. This preliminary action prepares verification scenarios in advance, making the verification process more efficient and targeted
2Reliability
If user big data is used for verification, then actual user scenarios can be captured, but newly added or changed screens cannot be verified
Solution Approach 1:
The patent dynamically updates the flow map by integrating information about newly added or changed screens into the existing user scenario models. This dynamic adaptation allows the verification system to evolve with software updates while maintaining accuracy in representing actual user behaviors
Solution Approach 2:
The patent introduces an intermediary process that bridges existing user data and new software features. This intermediary mechanism infers usage patterns for new screens based on similar existing screens and user behavior patterns, enabling verification of new features without direct user data
3Reliability
If random testing is performed on all screens, then system stability can be assessed, but verification time increases significantly
Solution Approach 1:
The patent applies local quality by performing random testing selectively on specific screens and pathways identified as high-risk or frequently used in the flow map. Rather than uniformly testing all screens, verification resources are concentrated on critical areas, reducing overall verification time while maintaining stability assessment quality
Solution Approach 2:
The patent changes verification parameters dynamically based on the flow map analysis, adjusting testing intensity, scope, and focus according to user scenario frequencies and software change priorities. This parameter adaptation optimizes the balance between verification thoroughness and time consumption
Data Source
AI summary
A method and apparatus for verifying updated software may be associated with an infotainment platform of a vehicle. The software verification method includes receiving data for software verification from an external server or external device, generating a flow map based on the received data, updating the flow map based on updated change specifications of software, reconfiguring the updated flow map based on estimated usage frequency of a display identifier (ID) added in the updated change specifications of the software, and verifying the changed specifications of the software by performing tests on the reconfigured flow map, where the display ID is a unique identifier assigned to each screen displayable during a software execution process.