Driver Control Device Segments Unsupported Functions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing universal driver solutions require significant labor hours for verifying system environments and updating function tables every time a new driver is installed, leading to increased labor costs and unnecessary complexity.
Innovation Solution
A driver controlling device with a supporting function storing unit, function obtaining unit, determining unit, registering unit, and preventing unit that stores information of unsupported functions in an un-supporting function list, preventing the use of unsupported functions and reducing the need for labor-intensive verification processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a universal driver is used to support all functions through a driver core section with a function table, then the number of driver installations is reduced, but labor hours for verifying and updating the function table increase significantly
Solution Approach 1:
The patent segments driver functions into two categories: supported functions (stored in the function table) and unsupported functions (stored in the un-supporting function list). This segmentation allows the system to efficiently manage driver compatibility by clearly distinguishing between functions that can be handled by the universal driver core and those that require specific driver implementations, thereby reducing verification overhead while maintaining adaptability.
Solution Approach 2:
The patent introduces an intermediary mechanism (the determining unit and un-supporting function list) that mediates between the universal driver core and specific driver requirements. This intermediary identifies and isolates unsupported functions before they reach the verification stage, preventing unnecessary verification labor while preserving the universal driver's adaptability for supported functions.
2Adaptability or versatility
If the function table is updated to support all new driver functions, then driver versatility is improved, but the complexity of driver management increases
Solution Approach 1:
The patent divides driver functions into supported and unsupported categories, with each category managed separately. The function table manages supported functions while the un-supporting function list manages unsupported functions. This segmentation simplifies driver management by preventing the function table from becoming overloaded with every possible driver function, thereby reducing management complexity while maintaining comprehensive function support coverage.
Solution Approach 2:
The patent extracts unsupported functions from the function table and places them in a separate un-supporting function list. This extraction prevents the function table from accumulating unnecessary entries for functions that cannot be supported by the universal driver core, thereby reducing driver management complexity while preserving the ability to support all necessary functions through the combined system.
3Productivity
If labor hours for verifying new driver functions are reduced, then productivity improves, but the risk of using unsupported functions increases
Solution Approach 1:
The patent performs preliminary identification of unsupported functions through the determining unit before the driver is fully installed or used. By identifying and registering unsupported functions in advance (in the un-supporting function list), the system prevents reliability issues from arising during actual driver operation, thereby maintaining high productivity without compromising function support reliability.
Solution Approach 2:
The patent implements a feedback mechanism where the determining unit continuously checks whether driver functions are supported by comparing against the function table and un-supporting function list. This feedback loop ensures that unsupported functions are identified and prevented from being used, maintaining reliability while allowing rapid driver installation and reducing verification productivity overhead.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A driver controlling device is disclosed. A UI module stores information of supportable functions of drivers in a function table, and obtains information of functions of a model of a new driver to be used described in model dependent data of the new driver. The UI module determines whether the obtained information of the functions of the new driver has been stored in the information of the supportable functions. When the obtained information of the functions of the new driver has not been stored in the information of the supportable functions, the UI module stores the information of the functions of the new driver which has not been stored in the information of the supportable functions in a un- supporting function list and prevents the new driver from using the information of the functions in the un-supporting function list.