Vehicle Actuator Request Arbitration Without Application IDs
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing vehicle control systems require re-specification of identification information for applications whenever a new application is added, leading to increased costs and inflexibility.
Innovation Solution
A control system and method for a vehicle that allows specification of the application generating a request reflected in actuator control without assigning identification information to applications, using a system with request generation devices, an arbitrator, and an actuator control apparatus to identify and notify the relevant application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If pieces of identification information are assigned to individual applications respectively, then the application that has generated a request can be specified properly, but the specification of the entire control system needs to be changed every time a new application is added, leading to increased costs
Solution Approach 1:
The system divides the identification function into two segments: the arbitrator identifies which request generation device output the final request, and the specified request generation device identifies which application within it generated the request. This segmentation allows each component to have a simpler, more focused identification task without requiring global reconfiguration.
Solution Approach 2:
The arbitrator acts as an intermediary that receives the final request from the actuator control apparatus and compares it with self-output requests to identify the requesting device. This intermediary mechanism enables indirect identification without requiring direct assignment of identification information to applications.
2Ease of operation
If pieces of identification information are assigned to applications, then application execution can be controlled properly, but the number of applications varies by vehicle specification requiring re-specification of the entire control system
Solution Approach 1:
The identification mechanism is designed to be universal across different vehicle specifications and application combinations. The arbitrator and request generation devices use a standardized comparison process that works regardless of how many applications are present, making the system adaptable to different vehicle configurations without re-specification.
Solution Approach 2:
The system dynamically adapts to different numbers of applications through its identification process. Rather than being statically configured with fixed identification information for each application, the system dynamically determines which application generated the request by comparing the final request against currently active requests from mounted applications.
3Loss of information
If identification information is assigned to each application, then the application generating the request can be specified, but this increases system cost and reduces flexibility when adding new applications
Solution Approach 1:
The request generation device performs self-identification by comparing the final request received from the arbitrator with its own self-output requests. This self-service mechanism eliminates the need for external identification information assignment, allowing the system to automatically track request sources without increasing manufacturing complexity.
Data Source
AI summary
A control system includes a plurality of request generation devices each of which outputs first and second requests based on a request generated by at least one application, an arbitrator that arbitrates the first and second requests and that outputs a single first request and a single second request, and a control apparatus that controls an actuator based on a final request obtained by arbitrating the first and second requests from the arbitrator and a request made by a driver. The arbitrator specifies the request generation device that has output a request corresponding to the final request based on the final request, the self-output first request, and the self-output second request. The request generation device specified by the arbitrator specifies the application that has generated the request corresponding to the final request based on the self-output first request, the self-output second request, and the request made by the driver.