Vehicle Gateway Inspection System for Usage-Stage Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing inspection systems for vehicle control devices only consider design-stage information and do not account for updates or changes during the usage stage, which can lead to security-related abnormalities and inadequate inspection of gateways, potentially causing false determinations of abnormalities or failing to detect actual issues.
Innovation Solution
An inspection system that generates security inspection information based on both design and usage-stage information, using a gateway control unit to convert this information into inspection data for other control devices, which are then compared against determination references to assess normal or abnormal operation, allowing for robust determination of vehicle control device functionality.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If inspection is performed using only design-stage information, then the inspection system is simple and easy to implement, but it cannot detect abnormalities caused by usage-stage updates or changes
Solution Approach 1:
The system pre-acquires usage-stage information (actual communication data, state data) before the inspection process. This preliminary collection of real-world operational data enables the inspection to account for usage-stage updates and changes, improving detection accuracy without requiring complex real-time adaptation mechanisms during the inspection itself
Solution Approach 2:
The inspection device acts as an intermediary that collects and processes both design-stage information and usage-stage information. By gathering actual communication data and state data from the control devices during usage, the system creates a comprehensive inspection database that bridges the gap between theoretical design specifications and real-world operational variations
2Measurement precision
If the inspection system considers usage-stage updates and changes, then the inspection accuracy improves, but the system complexity increases
Solution Approach 1:
The inspection system divides information collection into distinct segments: design-stage information (functional requirements, specifications) and usage-stage information (actual communication data, state data). This segmentation allows the system to process different types of data through appropriate methods and store them in separate databases, reducing overall processing complexity while maintaining comprehensive inspection capability
Solution Approach 2:
The system creates copies of inspection data from multiple sources (design specifications copied into inspection database, actual communication data copied from network traffic, state data copied from control devices). These copied data sets are then analyzed independently and integrated, enabling precise abnormality detection without requiring direct modification of the original systems
3Reliability
If the gateway conversion function is inspected, then the gateway functionality is verified, but the inspection system cannot self-inspect without external devices
Solution Approach 1:
The inspection device is configured to collect actual communication data and state data directly from the control devices through their existing communication interfaces. The control devices themselves provide the inspection data by normalizing and transmitting their operational information, enabling the system to self-inspect without requiring additional external inspection equipment or complex external device configurations
4Adaptability or versatility
If design information is updated during usage stage, then the system adapts to new requirements, but existing inspection data becomes outdated and may cause false abnormality determinations
Solution Approach 1:
The inspection system dynamically updates its database by continuously acquiring new usage-stage information (actual communication data, state data) during the usage period. This dynamic data collection ensures that the inspection criteria remain current and reflect the latest system configurations and operational patterns, preventing false abnormality determinations while maintaining adaptability to updates
Data Source
AI summary
Provided is an inspection system capable of inspecting whether or not a control device mounted to a vehicle normally operates also during usage. An inspection information generation unit of a server generates security inspection information for use in inspection of a function of an ECU on the basis of ECU design information and security information, and the security inspection information is transmitted to an ECU_GW. In the ECU_GW having received the security inspection information, an ECU_GW control unit performs a conversion process, and transmits information obtained by the conversion process to an ECU_A and an ECU_B. When receiving the information, each of the ECU_A and the ECU_B determines, with use of a determination reference held in advance, whether the received information is normal or abnormal.