Vehicle control unit configuration word intelligent generation system and method based on graphical interface

Abstract

The invention relates to the technical field of automobile research and development management, and discloses an intelligent generation system and method for configuration words of a vehicle control unit based on a graphical interface, and the system comprises a graphical configuration interface module, a configuration rule engine module, a configuration word generation module, a project management module and an export module. When configuration words of the vehicle control unit are generated, classified display and interactive operation functions are provided through a graphical configuration interface, and a configuration rule engine performs real-time logic verification and conflict detection on configuration items selected by a user, so that the selection normalization of the configuration items of different controller types is ensured; meanwhile, configuration conflicts and dependency errors can be recognized in real time in the configuration process, control system function abnormity caused by the configuration errors is reduced, and the accuracy and reliability of configuration of the vehicle control unit are improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of automobile research and development management, in particular to a whole vehicle controller configuration word intelligent generation system and method based on a graphical interface. BACKGROUND

[0002] With the advent of the era of software-defined vehicles, under the background of vehicle intelligence and networking, intelligent controller software is increasingly applied on vehicles, and the development and iteration of vehicle controller software is becoming increasingly complex. The controller configuration word of a vehicle is a data format that can describe and control various parameters and functions of a vehicle system, and contains setting information of vehicle hardware and software, and defines the characteristics, performance and functions of a vehicle.

[0003] Currently, due to the involvement of various controller types and complex dependency relationships in the whole vehicle controller configuration process, when manually configuring configuration words, the traditional method cannot detect logical conflicts and dependency errors between configuration items in real time. When conflicts occur during the configuration process, they are not discovered in time, which causes the generated configuration words to have errors and inconsistencies, and cannot guarantee the configuration accuracy and reliability of the whole vehicle control system.

[0004] Therefore, the present application provides a whole vehicle controller configuration word intelligent generation system and method based on a graphical interface to solve the above problems. SUMMARY

[0005] In view of the deficiencies of the prior art, the present application provides a whole vehicle controller configuration word intelligent generation system and method based on a graphical interface to solve the problems of errors and inconsistencies in the configuration words, and to guarantee the configuration accuracy and reliability of the whole vehicle control system.

[0006] To achieve the above purpose, the present application provides the following technical solutions: S1, receiving a user's selection operation on a whole vehicle controller configuration item through a graphical configuration interface, and generating original configuration item data; S2, performing logical verification and conflict detection processing on the original configuration item data, and outputting verification result data; S3, automatically generating an initial configuration word in hexadecimal format according to the verification result data, and outputting configuration word original data; S4, providing a visual editing interface to receive a user's modification operation on the configuration word original data, and outputting final confirmed configuration word data; S5, performing version management and template application processing on the final configuration word data, and outputting project configuration package data; S6, convert the project configuration package data into an xlsx format file and perform encryption processing, and output an encrypted configuration file; S7, during the execution of the above steps, the permission verification and operation record are synchronized, and an audit tracking report is generated based on the whole process operation data.

[0007] Preferably, the selection operation of the controller configuration item in S1 includes the following steps: S11, an interactive configuration interface is provided through a Web-based graphical interface and a desktop application, the interface uses HTML5, CSS3 and JavaScript technology to realize responsive design, supports cross-platform access, including PC end and mobile end; S12, the configuration items are dynamically loaded and rendered according to the controller type, the controller type includes BCM, TBOX, IHU, FCM, GW and AWD, multiple levels of configuration items are set under each controller, a tree directory structure is used for organization, and expansion and folding operations are supported; S13, a configuration item search and filtering function is provided, users can quickly locate specific configuration items through keywords, and fuzzy matching and real-time prompting are supported; S14, an integrated configuration item description tool is provided, when a user hovers over a configuration item, a prompt box is popped up to display detailed instructions, value range and impact analysis of the configuration item, assisting user decision-making.

[0008] Preferably, the specific operation of dynamically loading configuration items according to the controller type in S12 includes the following steps: S121, a controller type database is established to store configuration metadata of each controller, including configuration item name, type, default value and dependency relationship; S122, according to the project type and vehicle model code selected by the user, the configuration item list of the corresponding controller is loaded from the database asynchronously, and the interface is updated in real time through AJAX technology; S123, virtual scrolling technology is used to dynamically load configuration item data in the visible area, and a block rendering mechanism is used to process the interface display of large-scale configuration item sets; S124, import and export functions of configuration items are supported, allowing users to update configuration items in batches through JSON and XML formats.

[0009] Preferably, the initial configuration word in hexadecimal format in S3 includes the following steps: S31, a built-in rule library of the configuration rule engine is configured, the rule library contains configuration constraint conditions, mutual exclusion relationships, dependency logic and business rules of each controller, rules are defined using DSL domain-specific language, and dynamic loading is supported; S32. A rule matching algorithm is used to perform real-time verification of the configuration items selected by the user, including forward verification and backward verification. When a configuration conflict is detected, the conflict source is automatically identified and a solution suggestion is generated. The solution suggestion is based on rule priority and historical data. S33. Provides a rule customization interface, allowing users to add, modify, and delete configuration rules through a graphical rule editor, and supports rule version management; S34. After performing the verification, generate a verification report, including pass items, warning items, and error items, and display the verification results in a visual chart format.

[0010] Preferably, the rule matching algorithm in S32 adopts an inference engine based on the Rete algorithm, including the following sub-steps: S321. Convert the user configuration items into fact objects and load them into the working memory; S322. Use a pattern matcher to compare fact objects with rule conditions in the rule base to identify conflicts and dependencies; S323. Implement conflict resolution strategies and select the optimal solution based on rule priority and context. S324. Output the verification result and record the algorithm execution log.

[0011] Preferably, the modification operation of the original configuration word data in S4 includes the following steps: S41. The configuration word generation module calls the configuration word generation algorithm based on the verified configuration items to automatically calculate the hexadecimal configuration word for each controller. The algorithm is based on the configuration item weight and offset. S42. Receive user input through the configuration word visual editor, modify the configuration word in binary and hexadecimal formats, perform real-time verification processing, and output the modified configuration word data and verification status. S43. Integrated configuration word preview function, displaying the allocation of configuration bits in tabular and graphical form, including bit field description and value range; S44. Supports configuration version comparison function, highlighting the differences between different versions to assist users in version management.

[0012] Preferably, the configuration word generation algorithm in S41 adopts a template-based filling method, including the following steps: S411. Predefine a configuration word template for each controller. The template includes fixed bits and configurable bits. S412. Map the user configuration items to the configurable bits of the template, and generate the original configuration word through bitwise operations; S413. Apply the CRC cyclic redundancy check algorithm to check and calculate the configuration word in order to perform data integrity verification processing; S414. Output the final configuration word and support simulation testing to verify the configuration word in a real environment.

[0013] Preferably, the version management and template application processing in S5 includes the following steps: S51, the project management module provides full lifecycle management of projects, supports the automatic generation of a unique project ID when a project is created, and associates it with vehicle model code, configuration version and creator information; S52. Implement version control functionality, automatically record configuration change history based on Git-like mechanism, support version tags, branch management, and difference comparison, and use a line-based comparison algorithm for difference comparison; S53. An integrated configuration template library allows users to save frequently used configurations as templates and supports importing, exporting, and applying templates. Template formats include JSON, YAML, and XML. S54 provides project collaboration features, supporting multiple users to edit the same project simultaneously, and resolves concurrency conflicts through an optimistic locking mechanism.

[0014] Preferably, the specific implementation of the version control function in S52 includes the following steps: S521. Create a version repository for each project to store snapshots of configuration data and change logs; S522. When a user modifies the configuration, a difference packet is automatically generated, and the SHA-256 hash value is calculated for data consistency verification. S523 provides a version rollback interface, allowing users to quickly restore to a previous version and generate a rollback report; S524 supports version comparison visualization, displays version differences in a side-by-side view, and supports exporting comparison results.

[0015] Preferably, the system includes: The graphical configuration interface module generates a controller type selection interface through the configuration item classification display unit, receives user configuration selections through the interactive operation acquisition unit, and outputs raw configuration item data through the configuration data preprocessing unit. The configuration rule engine module receives the original configuration item data, loads the configuration constraint rules through the rule base management unit, performs logical verification and conflict detection using the rule matching engine unit, and outputs the verification result data through the verification report generation unit. The configuration word generation module receives the verification result data, generates hexadecimal configuration words through the configuration word calculation unit, provides a visual display through the configuration word preview unit, and outputs the original configuration word data through the configuration word optimization unit. The project management module receives the final configuration data, manages the configuration change history through the version control unit, realizes configuration reuse through the template management unit, and outputs the project configuration package data through the collaborative editing unit. The export module receives the project configuration package data, generates an xlsx file through the format conversion unit, ensures data security through the encryption processing unit, and outputs the encrypted configuration file through the batch export unit.

[0016] Compared with the prior art, the present invention provides a vehicle controller configuration word intelligent generation system and method based on a graphical interface, which has the following beneficial effects: 1. In this invention, when generating configuration words for the vehicle controller, a graphical configuration interface is provided to offer categorized display and interactive operation functions, and a configuration rule engine performs real-time logical verification and conflict detection on the configuration items selected by the user, ensuring the standardization of configuration item selection for different controller types. At the same time, configuration conflicts and dependency errors can be identified in real time during the configuration process, reducing abnormal control system functions caused by configuration errors and improving the accuracy and reliability of vehicle controller configuration.

[0017] 2. In this invention, when generating configuration words for the vehicle controller, the configuration word generation module automatically generates configuration words in hexadecimal format and supports visual editing and version comparison functions. This enables the system to ensure the standardization and consistency of configuration word generation. Furthermore, if an anomaly occurs during the configuration word generation process, the configuration content can be corrected in real time through the visual interface, ensuring that the final generated configuration word meets the technical requirements of the vehicle control system and improving the efficiency and quality of the configuration process.

[0018] 3. In this invention, when managing the configuration words of the vehicle controller, the project management module realizes the functions of multi-project version tracking, template application and difference comparison. In the process of batch vehicle development, the configuration data of different projects can be managed in a unified manner, so that the system can support platform-based development and configuration reuse, reduce the complexity of multi-vehicle configuration management, further improve the standardization and maintainability of vehicle controller configuration, and meet the needs of large-scale automobile production. Attached Figure Description

[0019] Fig. 1 This is a flowchart of the intelligent generation method for vehicle controller configuration words based on a graphical interface according to the present invention; Fig. 2 This is a diagram illustrating the architecture of the intelligent generation system for vehicle controller configuration characters based on a graphical interface, as described in this invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] For specific implementation examples, please refer to: Figs. 1-2 A system and method for intelligent generation of vehicle controller configuration characters based on a graphical interface, characterized in that the method includes the following steps: S1. Receive user selections for vehicle controller configuration items through a graphical configuration interface and generate raw configuration item data; S2. Perform logical verification and conflict detection on the original configuration item data, and output the verification result data; S3. Automatically generate an initial configuration word in hexadecimal format based on the verification result data, and output the original configuration word data; S4. Provides a visual editing interface to receive user modifications to the original configuration word data and outputs the final confirmed configuration word data; S5. Perform version management and template application processing on the final configuration data, and output the project configuration package data; S6. Convert the project configuration package data into an xlsx format file and perform encryption processing to output an encrypted configuration file; S7. During the execution of the above steps, permission verification and operation recording are performed simultaneously, and an audit trail report is generated based on the full-process operation data.

[0022] The selection process for controller configuration items in S1 includes the following steps: S11. Provides an interactive configuration interface through a web-based graphical interface and desktop application. The interface uses HTML5, CSS3 and JavaScript technologies to achieve responsive design and supports cross-platform access, including PC and mobile devices. S12. Dynamically load and render configuration items according to controller type. Controller types include BCM, TBOX, IHU, FCM, GW, and AWD. Each controller has multiple levels of configuration items, organized in a tree-like directory structure, and supports expansion and collapse operations. S13. Provides configuration item search and filtering functions, allowing users to quickly locate specific configuration items using keywords, and supports fuzzy matching and real-time prompts; S14. An integrated configuration item description tool will pop up a prompt box when the user hovers over a configuration item, displaying a detailed description of the configuration item, its value range, and its impact analysis to assist the user in making decisions.

[0023] The specific steps for dynamically loading configuration items by controller type in S12 include the following: S121. Establish a controller type database to store the configuration metadata of each controller, including configuration item name, type, default value and dependency relationship; S122. Based on the project type and vehicle model code selected by the user, asynchronously load the configuration item list of the corresponding controller from the database and update the interface in real time using AJAX technology. S123. Virtual scrolling technology is used to dynamically load configuration item data in the visible area, and a segmented rendering mechanism is used to handle the display of large-scale configuration item sets. The specific implementation of virtual scrolling technology includes the following steps: S1231. Determine the configuration item index range within the current view range using the visible area calculation unit, and output the visible configuration item subset data. The formula for calculating the visible index range is: ; ; in, To end the index, For view height, As the starting index, For scroll position, For the height of the configuration item; S1232. Dynamically load a subset of visible configuration items into the rendering queue and reuse UI elements through the DOM element recycling mechanism to optimize memory usage. The memory usage optimization formula is as follows: ; in, Total memory usage The number of visible items. This refers to the memory usage of a single element. S1233. Listen for scrolling events, update the visible area index in real time, and load configuration item data as needed through the asynchronous data loading unit; The formula for handling scrolling events is as follows: ; in, Rolling displacement, For the scrolling speed, For time intervals; S1234. The configuration item data is divided into fixed-size blocks using a block rendering mechanism, and visible blocks are rendered sequentially, while non-visible block data is cached to improve response efficiency. The formula for calculating the block size is as follows: ; in, For block size, This represents the total number of items. Number of blocks; S124. Supports importing and exporting configuration items, allowing users to update configuration items in batches using JSON and XML formats.

[0024] The initial configuration word in hexadecimal format in S3 includes the following steps: S31. The configuration rule engine has a built-in rule library, which contains the configuration constraints, mutual exclusion relationships, dependency logic and business rules of each controller. The rules are defined in the domain-specific language of DSL and support dynamic loading. S32. The rule matching algorithm is used to perform real-time verification of the configuration items selected by the user, including forward verification and backward verification. When a configuration conflict is detected, the conflict source is automatically identified and a solution suggestion is generated. The solution suggestion is based on rule priority and historical data. S33. Provides a rule customization interface, allowing users to add, modify, and delete configuration rules through a graphical rule editor, and supports rule version management; S34. After performing the verification, generate a verification report, including pass items, warning items, and error items, and display the verification results in a visual chart format.

[0025] The rule matching algorithm in S32 uses an inference engine based on the Rete algorithm, and includes the following sub-steps: S321. Convert the user configuration items into fact objects and load them into the working memory. The general implementation of the rule matching algorithm includes the following steps: S3211. Convert user configuration items and rule conditions into fact objects in a unified format and load them into the working memory of the rule engine; The formula for converting fact objects is as follows: ; in, For the set of facts, For a single fact; S3212. Traverse the rule base using a pattern matcher, compare fact objects with rule conditions one by one, identify matching items and mark conflicts and dependencies; The formula for calculating the rule matching degree is as follows: ; in, For matching degree, For the set of rule conditions, A collection of facts; S3213. Execute the conflict resolution strategy, sort the matching results based on rule priority and historical data, and output the optimal solution suggestion; The conflict resolution formula is as follows: ; in, As the final priority, For rule priority, For historical weighting, These are the weighting coefficients. For the maximize operator; S3214. Generate verification report data, including matching details, conflict list and resolution path, and display it through a visualization interface; The formula for the amount of data reported is as follows: ; in, For the size of the report data, For the number of conflicts, Size for a single conflict record; S322. Use a pattern matcher to compare fact objects with rule conditions in the rule base to identify conflicts and dependencies; S323. Implement conflict resolution strategies and select the optimal solution based on rule priority and context. S324. Output the verification result and record the algorithm execution log.

[0026] The modification operation of the original configuration word data in S4 includes the following steps: S41. The configuration word generation module calls the configuration word generation algorithm based on the verified configuration items to automatically calculate the hexadecimal configuration word for each controller. The algorithm is based on the configuration item weight and offset. S42. Receive user input through the configuration word visual editor, modify the configuration word in binary and hexadecimal formats, perform real-time verification processing, and output the modified configuration word data and verification status. S43. Integrated configuration word preview function, displaying the allocation of configuration bits in tabular and graphical form, including bit field description and value range; S44. Supports configuration version comparison function, highlighting the differences between different versions to assist users in version management.

[0027] The configuration word generation algorithm in S41 adopts a template-based filling method, which includes the following steps: S411. Predefine a configuration word template for each controller. The template includes fixed bits and configurable bits. The specific calculation steps of the configuration word generation algorithm include the following steps: S4111. Assign a weight value to each configuration item. The weight is dynamically calculated based on the business importance and scope of influence of the configuration item. The formula for calculating the weights is as follows: ; in, For weight values, Assign importance ratings, Score the scope of influence. For coefficients; S4112. Based on the offset address of the configuration item in memory, map its specific bit position in the hexadecimal configuration word; The specific bit position mapping formula is as follows: ; in, For byte position, This is the offset address; S4113. Apply bitwise operations to combine the configuration item values ​​into the original configuration word data according to the weight and offset. The bitwise combination formula is as follows: ; in, For configuration words, For configuration item values, For byte position; S4114. Verify the integrity and boundary conditions of the configuration word data through the verification unit to ensure data integrity and prevent overflow and format errors; The boundary verification formula is as follows: ; in, For configuration item values, These are boundary values; S412. Map the user configuration items to the configurable bits of the template, and generate the original configuration word through bitwise operations; S413. Apply the CRC cyclic redundancy check algorithm to check and calculate the configuration word in order to perform data integrity verification processing; S414. Output the final configuration word and support simulation testing to verify the configuration word in a real environment.

[0028] Performing version management and template application processing in S5 includes the following steps: S51, the project management module provides full lifecycle management of projects, supports the automatic generation of a unique project ID when a project is created, and associates it with vehicle model code, configuration version and creator information; S52. Implement version control functionality, automatically record configuration change history based on Git-like mechanism, support version tags, branch management, and difference comparison, and use a line-based comparison algorithm for difference comparison; S53. An integrated configuration template library allows users to save frequently used configurations as templates and supports importing, exporting, and applying templates. Template formats include JSON, YAML, and XML. S54 provides project collaboration features, supporting multiple users to edit the same project simultaneously, and resolves concurrency conflicts through an optimistic locking mechanism.

[0029] The specific implementation of version control functionality in S52 includes the following steps: S521. Create a version repository for each project to store snapshots of configuration data and change logs. The specific operations of the Git-like mechanism include the following steps: S5211. Initialize the version repository, create the main branch and generate the initial commit snapshot, and store the configuration data baseline; The snapshot hash calculation formula is as follows: ; in, For hash value, For configuration data; S5212. When a user modifies the configuration, a change package is generated through the difference calculation unit, and a new commit record change history is created. The formula for the size of the difference packet is: ; in, To change the amount of data, For both old and new data; S5213 supports branch management operations, allowing the creation of feature branches for isolated development and the integration of changes through the branch merging unit; The branch merging formula is as follows: ; in, To merge branches, Main branches and feature branches; S5214. Provides a conflict resolution interface. When a configuration conflict is detected during the merge, it guides the user to manually and automatically resolve the conflict before completing the submission. The collision detection formula is as follows: ; in, For the number of conflicts, Main branches and feature branches; S522. When a user modifies the configuration, a difference packet is automatically generated, and the SHA-256 hash value is calculated for data consistency verification. S523 provides a version rollback interface, allowing users to quickly restore to a previous version and generate a rollback report; S524 supports version comparison visualization, displays version differences in a side-by-side view, and supports exporting comparison results.

[0030] The system includes: The graphical configuration interface module generates a controller type selection interface through the configuration item classification display unit, receives user configuration selections through the interactive operation acquisition unit, and outputs raw configuration item data through the configuration data preprocessing unit. The configuration rule engine module receives raw configuration item data, loads configuration constraint rules through the rule base management unit, performs logical verification and conflict detection using the rule matching engine unit, and outputs verification result data through the verification report generation unit. The configuration word generation module receives the verification result data, generates hexadecimal configuration words through the configuration word calculation unit, provides a visual display through the configuration word preview unit, and outputs the original configuration word data through the configuration word optimization unit. The project management module receives the final configuration data, manages the configuration change history through the version control unit, enables configuration reuse through the template management unit, and outputs the project configuration package data through the collaborative editing unit. The export module receives project configuration package data, generates xlsx files through the format conversion unit, ensures data security through the encryption processing unit, and outputs encrypted configuration files through the batch export unit.

[0031] The operation steps of the intelligent generation system and method for vehicle controller configuration words based on a graphical interface are as follows: Step 1: Graphical Configuration Interface and Data Acquisition The system first receives user selections for vehicle controller configuration items through a graphical configuration interface. This interface is web-based and desktop application-oriented, implementing a responsive design based on HTML5, CSS3, and JavaScript technologies, supporting cross-platform access. Users can browse controller types through a tree-like directory structure, including BCM, TBOX, IHU, FCM, GW, and AWD, and quickly locate configuration items using search and filtering functions. When a user hovers over a configuration item, the system pops up a prompt box displaying detailed descriptions and value ranges to assist in decision-making. This step generates raw configuration item data, providing basic input for subsequent processing. The interface's dynamic loading mechanism uses virtual scrolling technology, optimizing the display performance of large-scale configuration item sets by calculating the visible area index and using block rendering to maintain smooth interaction.

[0032] Step 2: Logic Verification and Conflict Detection Handling The original configuration data is transmitted to the configuration rule engine for logical verification and conflict detection. The rule engine has a built-in rule base containing the configuration constraints, mutual exclusion relationships, and dependency logic of each controller. The rules are defined using a domain-specific language (DSL). The system verifies the user's selection in real time through a rule matching algorithm and an inference engine based on the Rete algorithm, including forward and backward verification. When a configuration conflict is detected, the conflict source is automatically identified and a solution suggestion is generated. The suggestion is calculated based on rule priority and historical data weighting. The verification results are output in the form of visual charts, including pass items, warning items, and error items, to maintain the rationality and consistency of the configuration logic.

[0033] Step 3: Automatic Generation and Visual Editing of Configuration Fonts Based on the verification results, the system automatically generates an initial configuration word in hexadecimal format. The configuration word generation algorithm uses a template-based filling method, predefining a configuration word template for each controller, which includes fixed bits and configurable bits. The algorithm calculates based on configuration item weights and offsets, combines them into the original configuration word data through bitwise operations, and applies CRC cyclic redundancy check to improve data integrity. Subsequently, the system provides a visual editing interface, allowing users to modify the configuration word in binary and hexadecimal formats. During the editing process, the system verifies the modifications in real time and integrates a preview function, displaying the allocation of configuration bits in tabular and graphical formats to assist users in finally confirming the configuration word data.

[0034] Step 4: Version Management and Template Application The final confirmed configuration data enters the project management module for version management and template application processing. The system creates a unique ID for each project, associates it with the vehicle model code and configuration version, and automatically records the configuration change history based on a Git-like mechanism. The version control function supports branch management, difference comparison, and rollback operations. Difference calculation uses a row-based comparison algorithm. At the same time, the system integrates a configuration template library, allowing users to save commonly used configurations as templates, supporting JSON, YAML, and XML formats to achieve reuse across multiple vehicle models. The collaborative editing function resolves concurrency conflicts through an optimistic locking mechanism and outputs project configuration package data, improving the efficiency of platform-based development.

[0035] Step 5: Data Export and Security Processing The project configuration package data is converted into an xlsx format file by the export module and encrypted. The export process supports batch operations and custom paths. The encryption algorithm ensures that the data is securely transmitted to the downstream electrical inspection system. The system generates an encrypted configuration file to maintain the confidentiality and integrity of the configuration words during storage and transmission.

[0036] Step Six: Full-Process Access Verification and Audit Tracking During all the above steps, the system synchronously performs permission verification and operation recording. Permission management is based on a role-based access control model, which restricts users' editing and viewing permissions for configuration words. Operation logs record user behavior in real time, including configuration modifications, version changes, and export operations. Based on the full-process operation data, the system generates an audit trail report to provide traceability support and meet compliance requirements.

[0037] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0038] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for intelligent generation of vehicle controller configuration characters based on a graphical interface, characterized in that: The method includes the following steps: S1. Receive user selections for vehicle controller configuration items through a graphical configuration interface and generate raw configuration item data; S2. Perform logical verification and conflict detection processing on the original configuration item data, and output the verification result data; S3. Automatically generate an initial configuration word in hexadecimal format based on the verification result data, and output the original configuration word data; S4. Provides a visual editing interface to receive user modifications to the original configuration word data and outputs the final confirmed configuration word data; S5. Perform version management and template application processing on the final configuration data, and output the project configuration package data; S6. Convert the project configuration package data into an xlsx format file and perform encryption processing to output an encrypted configuration file; S7. During the execution of the above steps, permission verification and operation recording are performed simultaneously, and an audit trail report is generated based on the full-process operation data.

2. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 1, characterized in that: The selection operation of the controller configuration item in S1 includes the following steps: S11. Provide an interactive configuration interface through a web-based graphical interface and a desktop application. The interface is designed to be responsive using HTML5, CSS3 and JavaScript technologies and supports cross-platform access, including PC and mobile devices. S12. Dynamically load and render configuration items according to controller type. The controller type includes BCM, TBOX, IHU, FCM, GW, and AWD. Each controller has multiple levels of configuration items, which are organized in a tree-like directory structure and support expansion and collapse operations. S13. Provides configuration item search and filtering functions, allowing users to quickly locate specific configuration items using keywords, and supports fuzzy matching and real-time prompts; S14. An integrated configuration item description tool will pop up a prompt box when the user hovers over a configuration item, displaying a detailed description of the configuration item, its value range, and its impact analysis to assist the user in making decisions.

3. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 2, characterized in that: The specific operation of dynamically loading configuration items according to controller type in S12 includes the following steps: S121. Establish a controller type database to store the configuration metadata of each controller, including configuration item name, type, default value and dependency relationship; S122. Based on the project type and vehicle model code selected by the user, asynchronously load the configuration item list of the corresponding controller from the database and update the interface in real time using AJAX technology. S123. Use virtual scrolling technology to dynamically load configuration item data in the visible area, and use a block rendering mechanism to handle the interface display of large-scale configuration item sets; S124. Supports importing and exporting configuration items, allowing users to update configuration items in batches using JSON and XML formats.

4. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 1, characterized in that: The initial configuration word in hexadecimal format in S3 includes the following steps: S31. The configuration rule engine has a built-in rule library, which contains the configuration constraints, mutual exclusion relationships, dependency logic and business rules of each controller. The rules are defined in the domain-specific language of DSL and support dynamic loading. S32. A rule matching algorithm is used to perform real-time verification of the configuration items selected by the user, including forward verification and backward verification. When a configuration conflict is detected, the conflict source is automatically identified and a solution suggestion is generated. The solution suggestion is based on rule priority and historical data. S33. Provides a rule customization interface, allowing users to add, modify, and delete configuration rules through a graphical rule editor, and supports rule version management; S34. After performing the verification, generate a verification report, including pass items, warning items, and error items, and display the verification results in a visual chart format.

5. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 4, characterized in that: The rule matching algorithm in S32 uses an inference engine based on the Rete algorithm and includes the following sub-steps: S321. Convert the user configuration items into fact objects and load them into the working memory; S322. Use a pattern matcher to compare fact objects with rule conditions in the rule base to identify conflicts and dependencies; S323. Implement conflict resolution strategies and select the optimal solution based on rule priority and context. S324. Output the verification result and record the algorithm execution log.

6. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 1, characterized in that: The modification operation of the original configuration word data in S4 includes the following steps: S41. The configuration word generation module calls the configuration word generation algorithm based on the verified configuration items to automatically calculate the hexadecimal configuration word for each controller. The algorithm is based on the configuration item weight and offset. S42. Receive user input through the configuration word visual editor, modify the configuration word in binary and hexadecimal formats, perform real-time verification processing, and output the modified configuration word data and verification status. S43. Integrated configuration word preview function, displaying the allocation of configuration bits in tabular and graphical form, including bit field description and value range; S44. Supports configuration version comparison function, highlighting the differences between different versions to assist users in version management.

7. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 6, characterized in that: The configuration word generation algorithm in S41 adopts a template-based filling method, which includes the following steps: S411. Predefine a configuration word template for each controller. The template includes fixed bits and configurable bits. S412. Map the user configuration items to the configurable bits of the template, and generate the original configuration word through bitwise operations; S413. Apply the CRC cyclic redundancy check algorithm to check and calculate the configuration word in order to perform data integrity verification processing; S414. Output the final configuration word and support simulation testing to verify the configuration word in a real environment.

8. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 1, characterized in that: The version management and template application processing performed in S5 include the following steps: S51, the project management module provides full lifecycle management of projects, supports the automatic generation of a unique project ID when a project is created, and associates it with vehicle model code, configuration version and creator information; S52. Implement version control functionality, automatically record configuration change history based on Git-like mechanism, support version tags, branch management, and difference comparison, and use a line-based comparison algorithm for difference comparison; S53. An integrated configuration template library allows users to save frequently used configurations as templates and supports importing, exporting, and applying templates. Template formats include JSON, YAML, and XML. S54 provides project collaboration features, supporting multiple users to edit the same project simultaneously, and resolves concurrency conflicts through an optimistic locking mechanism.

9. The intelligent generation method for vehicle controller configuration characters based on a graphical interface according to claim 8, characterized in that: The specific implementation of the version control function in S52 includes the following steps: S521. Create a version repository for each project to store snapshots of configuration data and change logs; S522. When a user modifies the configuration, a difference packet is automatically generated, and the SHA-256 hash value is calculated for data consistency verification. S523 provides a version rollback interface, allowing users to quickly restore to a previous version and generate a rollback report; S524 supports version comparison visualization, displaying version differences in a side-by-side view, and supports exporting comparison results.

10. A graphical interface-based intelligent generation system for vehicle controller configuration characters, used to implement the graphical interface-based intelligent generation method for vehicle controller configuration characters as described in any one of claims 1-9, characterized in that: The system includes: The graphical configuration interface module generates a controller type selection interface through the configuration item classification display unit, receives user configuration selections through the interactive operation acquisition unit, and outputs raw configuration item data through the configuration data preprocessing unit. The configuration rule engine module receives the original configuration item data, loads the configuration constraint rules through the rule base management unit, performs logical verification and conflict detection using the rule matching engine unit, and outputs the verification result data through the verification report generation unit. The configuration word generation module receives the verification result data, generates hexadecimal configuration words through the configuration word calculation unit, provides a visual display through the configuration word preview unit, and outputs the original configuration word data through the configuration word optimization unit. The project management module receives the final configuration data, manages the configuration change history through the version control unit, realizes configuration reuse through the template management unit, and outputs the project configuration package data through the collaborative editing unit. The export module receives the project configuration package data, generates an xlsx file through the format conversion unit, ensures data security through the encryption processing unit, and outputs the encrypted configuration file through the batch export unit.

Images