Standardized Failsafe Attributes in CAN Database Files
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The lack of standardized failsafe documentation across different suppliers in in-vehicle CAN networks complicates OEMs' efforts to manage and analyze failsafe practices across multiple model years and suppliers, as each supplier documents their algorithms and logic differently, leading to inefficiencies in capturing and implementing failsafe operations.
Innovation Solution
Enhancing CAN database files with additional data attributes such as Safety Critical, Automotive Safety Integrity Level, Maturation Time, Warning Indicator, and Diagnostic Trouble Code allows for standardized failsafe details to be captured and analyzed, enabling OEMs to manage and track failsafe practices efficiently across multiple models and suppliers, and aiding suppliers in automatic code generation and reviews like SFMEA.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If each supplier defines their own failsafe algorithms and logic, then suppliers can implement failsafe operations according to their specific requirements, but the OEM cannot easily capture and analyze failsafe practices across multiple model years and suppliers
Solution Approach 1:
The patent introduces a standardized failsafe information structure as an intermediary layer between supplier-specific failsafe implementations and OEM analysis requirements. This structure includes standardized fields such as failsafe condition, response action, and timing parameters that mediate between the diversity of supplier implementations and the need for consistent OEM analysis across multiple models and suppliers.
Solution Approach 2:
The patent transforms varies failsafe documentation into a standardized parameter set including failsafe condition, response action, and timing parameters. By changing the representation of failsafe information into these standardized parameters, the system enables consistent capture and analysis across different suppliers while preserving the essential failsafe logic from each implementation.
2Ease of manufacture
If failsafe details are buried in supplier documents, then suppliers can document their failsafe practices in their own format, but the OEM must request and search through these documents which increases complexity and time consumption
Solution Approach 1:
The patent implements preliminary action by having suppliers pre-fill standardized failsafe information fields during the vehicle configuration process. Instead of requiring OEMs to search through supplier documents later, the failsafe details are prepared in advance in a standardized format that is automatically available for analysis, significantly reducing the time and effort required for OEM information gathering.
Solution Approach 2:
The patent replaces the mechanical process of manually searching through and requesting supplier documents with an automated information extraction system. The standardized failsafe fields are automatically captured from supplier configurations and made available for analysis, eliminating the need for manual document review and reducing the time investment required for failsafe information gathering.
3Reliability
If the OEM requests failsafe information from each supplier, then the OEM can obtain failsafe details, but the process becomes cumbersome and inefficient across multiple suppliers
Solution Approach 1:
The patent creates a universal failsafe information structure that serves multiple functions simultaneously: it captures supplier-specific failsafe logic, standardizes the representation for OEM analysis, and enables automated processing across multiple suppliers. This universal structure eliminates the need for separate handling of different supplier documentation formats, simplifying the overall management process while maintaining information completeness.
Solution Approach 2:
The system enables self-service by allowing suppliers to automatically provide failsafe information in a standardized format during their configuration process, without requiring active requests or manual data extraction by the OEM. The standardized fields are automatically populated and made available for analysis, reducing the operational complexity for the OEM while ensuring complete failsafe information capture.
Data Source
AI summary
Methods and systems for analyzing failsafe conditions. One method includes receiving, at a processor, a message transmitted over a vehicle bus, wherein the message includes a data field. The method further includes accessing at least one data attribute included in a database file associated with the vehicle bus. The at least one data attribute includes at least one of (a) a safety critical attribute, (b) an automotive safety integrity level attribute, (c) a maturation time attribute, (d) a warning indicator attribute, and (e) a diagnostic trouble code attribute. The method also includes converting the data field based on the at least one data attribute.