In-Vehicle Data Control Part for Seamless Software Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing software updating process in in-vehicle systems requires redesigning the Virtual Functional Bus (VFB) each time a new software component is added, leading to increased development time and complexity, especially when updating software outside the development environment.
Innovation Solution
An in-vehicle apparatus with a data control part that includes a buffer, communication processing, and data relay components, allowing an application program to communicate with software components without modifying the VFB, enabling seamless addition of new software components without redesigning the VFB.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new software component is added to the in-vehicle system, then the functionality and adaptability of the system are improved, but the VFB must be redesigned which increases device complexity and development time
Solution Approach 1:
The patent introduces a gateway as an intermediary component between the application program and the VFB. This gateway handles data routing, buffering, and communication protocols, allowing new software components to be added without modifying the existing VFB structure. The gateway acts as a mediator that absorbs the complexity of integration, enabling independent software component addition while maintaining system stability.
2Adaptability or versatility
If the VFB is redesigned for each additional software component, then the system adapts to new functionality, but the development time and man-hours increase significantly
Solution Approach 1:
The gateway is designed with pre-configured communication interfaces and data routing capabilities that anticipate future software component additions. By establishing this flexible intermediary structure in advance, the system enables rapid integration of new software components without requiring time-consuming VFB redesign processes. The preliminary gateway architecture prepares the system for adaptability while minimizing future development time.
3Reliability
If full knowledge of VFB design and design tool operation is required, then the VFB can be designed appropriately, but the ease of operation decreases and software updates become difficult outside development environment
Solution Approach 1:
The patent extracts the complexity of VFB design and communication protocol management from the software component integration process by consolidating these functions into the gateway. This separation allows software components to be added and updated using simple configuration procedures without requiring deep knowledge of VFB design principles or specialized design tools. The gateway encapsulates the complex functionality, making the system easier to operate and update outside the development environment.
Data Source
AI summary
An ASL is associated with an APP module having as a communication target an existing APP SW-C(1). A buffer part accumulates data to the existing APP SW-C(1) and data from the existing APP SW-C(1). A communication processing part transmits the data to the existing APP SW-C(1) accumulated in the buffer part to the existing APP SW-C(1), receives data transmitted from the existing APP SW-C(1), and stores the received data in the buffer part. An API processing part receives as input from the APP module data to the existing APP SW-C(1), stores the data received as input in the buffer part, receives as input from the buffer part data from the existing APP SW-C(1), and outputs the data received as input to the APP module.