A JSON-based vehicle attribute management method, device and terminal equipment

Abstract

The application discloses a JSON-based vehicle attribute management method and device and a terminal device, and relates to the technical field of vehicle attribute management. The method comprises the following steps: receiving a user's management operation on vehicle attributes through a user operation interface; checking the vehicle attributes to be managed according to the operation type of the management operation and a preset checking rule; and managing a preset JSON format database file according to the management operation and the vehicle attributes to be managed based on the checking result, wherein the JSON format database file is used for storing at least one vehicle attribute of at least one vehicle item. The technical scheme of the application can realize unified management of vehicle attributes of multiple items, and the items do not interfere with each other, thereby solving the problem that the attributes of the items are not synchronized.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a JSON-based method, apparatus, and terminal device for vehicle attribute management. Background Technology

[0002] Vehicle Properties define the communication attributes between the Android layer in the vehicle's infotainment system and the underlying VHAL (Vehicle Hardware Abstraction Layer), enabling the establishment of signal pathways between the Android layer and the underlying layer. Currently, the project uses over 500 Vehicle Property definitions, and this number continues to grow with the project's expansion. The project currently manages Vehicle Property attributes using an Excel spreadsheet (VHAL table). Each modification to the VHAL table requires developers to manually update the attribute values, and each change is documented in a text changelog.

[0003] However, in actual development, Vehicle Property attributes have platform requirements and are managed in parallel across multiple projects. There is a lot of content to manage, and the detailed attribute definitions differ between projects. This leads to the following problems when managing Vehicle Property attributes through VHAL tables: the parallel nature of projects is severe, the maturity levels of each project are inconsistent, and projects with higher maturity do not want to share VHAL tables with projects with lower maturity, requiring separate tables for management, which in turn leads to the problem of attribute inconsistency between tables. Summary of the Invention

[0004] The purpose of this invention is to provide a vehicle attribute management method, device, and terminal equipment based on JSON. By adopting a database file management method in JSON format, it is possible to achieve unified management of vehicle attributes of multiple items without interference between items, thereby solving the problem of attribute asynchrony between items.

[0005] To achieve the above objectives, embodiments of the present invention provide a JSON-based vehicle attribute management method, comprising:

[0006] The system receives user management commands for vehicle attributes through a user interface.

[0007] The vehicle attributes to be managed are checked according to the operation type and preset inspection rules of the management operation.

[0008] Based on the inspection results, a preset JSON-formatted database file is managed according to the management operation and the vehicle attributes to be managed; wherein, the JSON-formatted database file is used to store at least one vehicle attribute of at least one vehicle item.

[0009] Furthermore, the management operation type includes adding attribute operation, and the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user received through the user operation interface;

[0010] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0011] Based on the newly added vehicle function, query the database file in JSON format to determine whether there is a vehicle function in the database file that matches the newly added vehicle function;

[0012] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0013] When the check result is that the function does not exist, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read and write attributes and CAN signal name;

[0014] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0015] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0016] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0017] Furthermore, the method also includes:

[0018] If the CAN signal name does not exist in the DBC file, determine whether the CAN signal name was entered incorrectly.

[0019] If so, the system receives the CAN signal name re-entered by the user through the user interface and processes it accordingly.

[0020] If not, then the attribute addition operation ends.

[0021] Furthermore, the method also includes:

[0022] When the CAN signal name is not unique, the user interface displays the vehicle attribute information that has used the CAN signal name to the user, and determines whether it is necessary to continue adding the new vehicle function based on the vehicle attribute information that has used the CAN signal name.

[0023] If so, the system receives the attribute definition corresponding to the newly added vehicle function re-entered by the user through the user operation interface, and performs corresponding processing based on the attribute definition corresponding to the newly added vehicle function re-entered by the user.

[0024] If not, then the attribute addition operation ends.

[0025] Furthermore, the method also includes:

[0026] When the check result indicates that the function exists, the attribute definition of the matched vehicle function is displayed to the user through the user interface.

[0027] The user interface receives the user's judgment result regarding whether the newly added vehicle function and the matched vehicle function belong to the same function.

[0028] When the judgment result indicates that the functions do not belong to the same function, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read / write attributes and CAN signal name;

[0029] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0030] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0031] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0032] Furthermore, the method also includes:

[0033] When the determination result indicates that they belong to the same function, determine whether the newly added vehicle function and the matched vehicle function belong to the same vehicle item.

[0034] If not, the attribute synchronization function is used to migrate the vehicle attributes corresponding to the matched vehicle function to the newly added vehicle function, and the CAN signal name corresponding to the newly added vehicle function is configured. The obtained vehicle attributes corresponding to the newly added vehicle function are written into the JSON format database file.

[0035] If so, then the attribute addition operation ends.

[0036] Furthermore, the management operation type includes an attribute deletion operation, and the vehicle attribute to be managed is the vehicle attribute to be deleted;

[0037] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0038] The user interface receives the attribute ID and vehicle item information corresponding to the vehicle attribute to be deleted, input by the user.

[0039] Based on the attribute ID and the vehicle project information, query the JSON-formatted database file to determine whether the vehicle attribute to be deleted exists in the JSON-formatted database file;

[0040] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0041] When the check result is that the vehicle attribute to be deleted exists, the user inputs the reason for deletion through the user interface, writes the reason for deletion into the JSON format database file, and performs deletion processing on the vehicle attribute to be deleted.

[0042] If the check result is that the attribute does not exist, the attribute deletion operation ends.

[0043] Furthermore, the management operation type includes an attribute modification operation, and the vehicle attribute to be managed is the vehicle attribute to be modified.

[0044] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0045] The user interface receives the attribute ID corresponding to the vehicle attribute to be modified and the vehicle item information to be modified, which are input by the user.

[0046] Based on the attribute ID and the vehicle project information, query the database file in JSON format to determine whether the vehicle attribute to be modified exists in the project to be modified;

[0047] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0048] When the check result is positive, the user inputs the modified vehicle attributes and the reason for modification through the user interface, the vehicle attributes to be modified are modified accordingly based on the modified vehicle attributes, and the reason for modification is written into the JSON format database file.

[0049] If the check result is that the attribute modification operation is terminated.

[0050] Furthermore, the management operation type includes a query attribute operation, and the vehicle attribute to be managed is the vehicle attribute to be queried;

[0051] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0052] The user interface receives the attribute ID, vehicle item information, function description, and signal name corresponding to the vehicle attribute to be queried, input by the user.

[0053] Based on the attribute ID, vehicle project information, function description and signal name corresponding to the vehicle attribute to be queried, query the JSON format database file to determine whether the vehicle attribute to be queried exists in the JSON format database file;

[0054] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0055] When the check result is positive, the query result is displayed to the user through the user interface;

[0056] If the check result is that the attribute query operation does not exist, the query operation ends.

[0057] Furthermore, the method also includes:

[0058] After managing the JSON-formatted database file, the managed JSON-formatted database file is submitted to the Git repository for review, insertion, and synchronization.

[0059] To achieve the above objectives, embodiments of the present invention also provide a JSON-based vehicle attribute management device for implementing the JSON-based vehicle attribute management method described in any of the preceding claims, the device comprising:

[0060] The management operation receiving module is used to receive user management operations on vehicle attributes through the user interface.

[0061] The vehicle attribute checking module is used to check the attributes of the vehicles to be managed according to the operation type of the management operation and the preset checking rules.

[0062] The vehicle attribute management module is used to manage a preset JSON format database file based on the inspection results, the management operation, and the vehicle attributes to be managed; wherein the JSON format database file is used to store at least one vehicle attribute for at least one vehicle item.

[0063] This invention also provides a terminal device, including a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor implements the JSON-based vehicle attribute management method described above when executing the computer program.

[0064] Compared with existing technologies, embodiments of the present invention provide a JSON-based vehicle attribute management method, apparatus, and terminal device. The method receives user management operations on vehicle attributes through a user interface; checks the vehicle attributes to be managed according to the operation type of the management operation and preset check rules; and manages a preset JSON-formatted database file based on the check results, according to the management operation and the vehicle attributes to be managed. The JSON-formatted database file stores at least one vehicle attribute for at least one vehicle item. By employing a JSON-formatted database file management method, embodiments of the present invention can achieve unified management of vehicle attributes across multiple items, ensuring that each item does not interfere with the others, thereby solving the problem of attribute asynchrony between items. Attached Figure Description

[0065] Figure 1 This is a flowchart of a preferred embodiment of a JSON-based vehicle attribute management method provided by the present invention;

[0066] Figure 2 This is a structural block diagram of a preferred embodiment of a JSON-based vehicle attribute management device provided by the present invention;

[0067] Figure 3 This is a structural block diagram of a preferred embodiment of a terminal device provided by the present invention. Detailed Implementation

[0068] 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.

[0069] This invention provides a JSON-based vehicle attribute management method, see [link / reference]. Figure 1 The diagram shown is a flowchart of a preferred embodiment of a JSON-based vehicle attribute management method provided by the present invention, the method comprising steps S11 to S13:

[0070] Step S11: Receive user management operations on vehicle attributes through the user interface;

[0071] Step S12: Check the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules;

[0072] Step S13: Based on the inspection results, manage the preset JSON format database file according to the management operation and the vehicle attributes to be managed; wherein, the JSON format database file is used to store at least one vehicle attribute of at least one vehicle item.

[0073] In this embodiment of the invention, a user interface is pre-created, which is configured with a Vehicle Property attribute management tool. The Vehicle Property attributes of multiple vehicle projects are placed in the same JSON format database file. Using the user interface and the Vehicle Property attribute management tool, the JSON format database file can be managed, that is, the vehicle's Vehicle Property attributes stored in the JSON format database file can be managed.

[0074] Specifically, users (such as developers) can select to trigger vehicle attribute management operations on the user interface. When a user's management operation on vehicle attributes is received through the user interface, the vehicle attributes to be managed are first checked according to the operation type of the received management operation and the pre-set check rules. Then, based on the obtained check results, the pre-set JSON format database file is processed accordingly according to the received management operation and the vehicle attributes to be managed.

[0075] It should be noted that when users operate on the user interface, corresponding input boxes and / or prompts will be displayed to guide and restrict users' management operations on the JSON-formatted database file. Under normal circumstances, users can only modify the JSON-formatted database file through the interface and are prohibited from directly modifying the JSON-formatted database file. Through the content prompts and process control on the interface, scenarios in which users can directly modify all attributes can be prompted and restricted, preventing users from directly obtaining all attribute editing permissions.

[0076] The vehicle attribute management method based on JSON provided in this embodiment of the invention supports vehicle attribute management for all vehicle projects by adopting a database file management method in JSON format. It realizes unified and platform-based management of vehicle attributes for multiple projects, and the projects do not interfere with each other, thereby solving the problem of attribute asynchrony between projects. It also avoids the situation where users directly obtain all attribute editing permissions, which is beneficial to the development and management of multi-project vehicle control work.

[0077] In another preferred embodiment, the operation type of the management operation includes an attribute addition operation, wherein the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user through the user operation interface.

[0078] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0079] Based on the newly added vehicle function, query the database file in JSON format to determine whether there is a vehicle function in the database file that matches the newly added vehicle function;

[0080] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0081] When the check result is that the function does not exist, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read and write attributes and CAN signal name;

[0082] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0083] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0084] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0085] Specifically, in conjunction with the above embodiments, the management operation types include adding attribute operations. Correspondingly, the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user received through the user interface. When the user interface receives an operation to add a vehicle attribute, the user can enter a description of the new vehicle function in the content input box displayed on the user interface. Based on the received description of the new vehicle function, a JSON-formatted database file is queried to check if a vehicle function matching the new vehicle function exists in the JSON-formatted database file. If the check result is negative (i.e., no vehicle function matching the new vehicle function exists in the JSON-formatted database file), the query is successful. At this time, users can enter the basic attribute definition corresponding to the new vehicle function in the content input box displayed on the user operation interface. For example, they can add detailed function descriptions, enter read and write attributes, and enter the corresponding CAN signal name. Based on the received basic attribute definition corresponding to the new vehicle function, the uniqueness of the CAN signal name corresponding to the new vehicle function is first checked within the vehicle project to which the new vehicle function belongs. When the CAN signal name is determined to be unique, it is then checked against the DBC file. When the CAN signal name is found to exist in the DBC file, the attribute ID value corresponding to the new vehicle function is generated, and the basic attribute definition and attribute ID value corresponding to the new vehicle function are written to the database file in JSON format.

[0086] It should be noted that the function description mainly refers to a simple description of the vehicle function to be added. For example, assuming that the driver's side air conditioning temperature adjustment function already exists in the JSON format database file, its keywords can include air conditioning, driver's side, and temperature. When querying the JSON format database file for a search and matching based on the function description of the new vehicle function input by the user, if the function description of the new vehicle function input by the user does not contain these keywords, it means that there is no vehicle function in the JSON format database file that matches the new vehicle function. If the function description of the new vehicle function input by the user contains these keywords, it means that there is a vehicle function in the JSON format database file that matches the new vehicle function, and the vehicle attribute corresponding to the driver's side air conditioning temperature adjustment function will be output and displayed.

[0087] It should be noted that the supplementary detailed functional descriptions mainly include:

[0088] Functional classification: Classified into first-level functional modules;

[0089] Function Describe: This is a secondary function point.

[0090] Detailed Explanation: A complete description of the functional points;

[0091] The specific content of the attribute definition (i.e., detailed description) mainly includes:

[0092] Project: Project configuration, indicating which vehicle model project this attribute is used on;

[0093] Scope: The user, used to indicate whether the property is used internally or externally;

[0094] Ext property: Whether it is an extended property;

[0095] Area ID: Area attribute, indicating the target area of ​​this attribute in the software, such as GLOBAL (shared), WINDOW (window), etc.

[0096] Data Type: Data type, indicating the type of data used to store data in the code;

[0097] Min value: the minimum value;

[0098] Max value: Maximum value;

[0099] Default value: The default value;

[0100] Access mode: refers to the desired read and write capabilities for the data;

[0101] Change mode: Data change notification mode, which is generally used to notify users when data changes.

[0102] Property ID: The property ID value;

[0103] MCU UP: refers to the uplink signal involved in this attribute;

[0104] IVI DOWN: refers to the downlink signal involved in this attribute;

[0105] Received Signal Value: The range of values ​​for the transmitted signal;

[0106] Send Signal Value: The range of values ​​for the received signal.

[0107] It should be noted that the scope of a vehicle project is generally determined based on the vehicle model. One vehicle model corresponds to one vehicle project. The uniqueness of the CAN signal name refers to whether the CAN signal name within a vehicle model has been used by other attributes. The CAN signal name in a vehicle project is unique, and correspondingly, only one attribute can configure this CAN signal.

[0108] It should be noted that the DBC file is a dependency file used by the automotive CAN bus signal parsing tool to parse bus signals. Its function is to clearly identify the meaning of different bits in different byte arrays. The CAN signal name check is performed in the DBC file in this embodiment of the invention because: software developers define attributes through Word requirements documents, and the DBC file is a file that the hardware driver layer needs to rely on when configuring the path. However, the maintenance personnel of the two files are generally not the same, which may lead to misalignment of CAN signal names. Therefore, after determining that the CAN signal name corresponding to the newly added vehicle function is unique, it is also necessary to check whether it is aligned with the corresponding CAN signal name in the DBC file. If the CAN signal name entered by the user can be found in the DBC file, it means that the two are aligned.

[0109] It should be noted that the property ID value is generally 4 digits, and the value range is 0x0000 to 0xFFFF. Each vehicle function will occupy one property ID. When generating the property ID value corresponding to the new vehicle function, you can obtain the platform's unique property ID value by providing the ID values ​​that have not been used in sequence within the above value range.

[0110] Existing technologies that manage Vehicle Property attributes through VHAL tables have the following problems: Multiple table maintainers (e.g., developers unfamiliar with vehicle control content) may have differing understandings of requirements and vehicle control attributes, easily leading to issues such as duplicate attribute definitions and incorrect attribute definitions. Furthermore, the table format cannot identify content changes caused by typos. The JSON-based vehicle attribute management method provided in this invention can perform uniqueness and alignment checks on user-input CAN signal names. By configuring corresponding attribute management check functions, it can solve the problems existing in the prior art, thereby effectively preventing problematic vehicle attributes from entering the JSON format database file.

[0111] As a preferred embodiment, the method further includes:

[0112] If the CAN signal name does not exist in the DBC file, determine whether the CAN signal name was entered incorrectly.

[0113] If so, the system receives the CAN signal name re-entered by the user through the user interface and processes it accordingly.

[0114] If not, then the attribute addition operation ends.

[0115] Specifically, in conjunction with the above embodiments, when checking the CAN signal name corresponding to the newly added vehicle function according to the DBC file, if it is determined that the CAN signal name does not exist in the DBC file, it is further determined whether the CAN signal name is entered incorrectly. If so, the CAN signal name re-entered by the user is received through the user operation interface. Within the vehicle project to which the newly added vehicle function belongs, the uniqueness of the CAN signal name re-entered by the user is checked. When it is determined that the CAN signal name is unique, it is checked again according to the DBC file. When it is determined that the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the basic attribute definition (i.e., detailed function description, read / write attributes, and the CAN signal name re-entered by the user) and attribute ID value corresponding to the newly added vehicle function are written to a database file in JSON format; otherwise, the current attribute addition operation is directly terminated.

[0116] It should be noted that if the CAN signal names in the Word requirements document do not match the corresponding CAN signal names in the DBC file, it generally indicates a problem with the requirements definition in the Word requirements document. Engineers need to clarify and unify the signal names before further input can be made.

[0117] As a preferred embodiment, the method further includes:

[0118] When the CAN signal name is not unique, the user interface displays the vehicle attribute information that has used the CAN signal name to the user, and determines whether it is necessary to continue adding the new vehicle function based on the vehicle attribute information that has used the CAN signal name.

[0119] If so, the system receives the attribute definition corresponding to the newly added vehicle function re-entered by the user through the user operation interface, and performs corresponding processing based on the attribute definition corresponding to the newly added vehicle function re-entered by the user.

[0120] If not, then the attribute addition operation ends.

[0121] Specifically, in conjunction with the above embodiments, when performing a uniqueness check on the CAN signal name corresponding to the newly added vehicle function within the scope of the vehicle project, if it is determined that the CAN signal name is not unique, the user will be shown vehicle attribute information that has already used the CAN signal name through the user interface. Based on the vehicle attribute information that has already used the CAN signal name, it will be further determined whether to continue adding the user-inputted new vehicle function. If yes, the user will receive the attribute definition corresponding to the newly added vehicle function re-input through the user interface, and perform corresponding processing based on the attribute definition corresponding to the newly added vehicle function re-input by the user (the subsequent processing process is the same as the processing process after receiving the basic attribute definition corresponding to the newly added vehicle function input by the user in the above embodiments, and will not be repeated here). If no, the current attribute addition operation will end directly.

[0122] As a preferred embodiment, the method further includes:

[0123] When the check result indicates that the function exists, the attribute definition of the matched vehicle function is displayed to the user through the user interface.

[0124] The user interface receives the user's judgment result regarding whether the newly added vehicle function and the matched vehicle function belong to the same function.

[0125] When the judgment result indicates that the functions do not belong to the same function, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read / write attributes and CAN signal name;

[0126] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0127] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0128] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0129] Specifically, in conjunction with the above embodiments, the system checks whether a vehicle function matching the newly added vehicle function exists in the JSON-formatted database file. If the check result indicates existence (i.e., a vehicle function matching the newly added vehicle function exists in the JSON-formatted database file), the system displays the attribute definitions of the vehicle function matching the newly added vehicle function in the JSON-formatted database file to the user through the user interface. This allows the user to determine whether the newly added vehicle function and the matching vehicle function in the JSON-formatted database file belong to the same function, and the user's determination result is received through the user interface. When the determination result indicates that they do not belong to the same function, the process is the same as in the above embodiments, and the user can... The user interface displays the basic attribute definition for the newly added vehicle function in the input fields. For example, users can add detailed function descriptions, input read / write attributes, and input the corresponding CAN signal name. Based on the received basic attribute definition for the newly added vehicle function, the system first performs a uniqueness check on the CAN signal name within the vehicle project to which the newly added vehicle function belongs. If the CAN signal name is determined to be unique, the system then checks the CAN signal name against the DBC file. If the CAN signal name exists in the DBC file, the system generates the attribute ID value corresponding to the newly added vehicle function and writes the basic attribute definition and attribute ID value corresponding to the newly added vehicle function into a JSON format database file.

[0130] As a preferred embodiment, the method further includes:

[0131] When the determination result indicates that they belong to the same function, determine whether the newly added vehicle function and the matched vehicle function belong to the same vehicle item.

[0132] If not, the attribute synchronization function is used to migrate the vehicle attributes corresponding to the matched vehicle function to the newly added vehicle function, and the CAN signal name corresponding to the newly added vehicle function is configured. The obtained vehicle attributes corresponding to the newly added vehicle function are written into the JSON format database file.

[0133] If so, then the attribute addition operation ends.

[0134] Specifically, in conjunction with the above embodiments, when determining whether the newly added vehicle function and the matching vehicle function in the JSON format database file belong to the same function, if the determination result is that they belong to the same function, then it is further determined whether the newly added vehicle function and the matching vehicle function in the JSON format database file belong to the same vehicle project; if not, then the attribute synchronization function is used to migrate the vehicle attributes corresponding to the matching vehicle function in the JSON format database file to the newly added vehicle function (except for the CAN signal name which can be configured, other attributes are directly synchronized), and the CAN signal name corresponding to the newly added vehicle function is configured. The obtained vehicle attributes corresponding to the newly added vehicle function (i.e., all attributes other than the CAN signal name synchronized and the newly configured CAN signal name) are written to the JSON format database file; if yes, then the current attribute addition operation is directly terminated.

[0135] For example, assuming vehicle model A already has the function corresponding to attribute A, and vehicle model B also needs this function, the function description (i.e., Functional classification, Function Describe, and Detailed Explanation) and attribute definition (i.e., Project, Scope, Ext property, Area ID, DataType, Min value, Max value, Default value, Access mode, Change mode, and Property ID) of attribute A from vehicle model A's project can be migrated to vehicle model B's project. Then, by adding the CAN signal name used by vehicle model B, the attribute synchronization process is completed.

[0136] In another preferred embodiment, the operation type of the management operation includes a delete attribute operation, and the vehicle attribute to be managed is the vehicle attribute to be deleted;

[0137] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0138] The user interface receives the attribute ID and vehicle item information corresponding to the vehicle attribute to be deleted, input by the user.

[0139] Based on the attribute ID and the vehicle project information, query the JSON-formatted database file to determine whether the vehicle attribute to be deleted exists in the JSON-formatted database file;

[0140] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0141] When the check result is that the vehicle attribute to be deleted exists, the user inputs the reason for deletion through the user interface, writes the reason for deletion into the JSON format database file, and performs deletion processing on the vehicle attribute to be deleted.

[0142] If the check result is that the attribute does not exist, the attribute deletion operation ends.

[0143] Specifically, in conjunction with the above embodiments, the management operation types include attribute deletion operations. Correspondingly, the vehicle attributes to be managed are the vehicle attributes to be deleted. When a user's request to delete a vehicle attribute is received through the user interface, the user can enter the attribute ID and vehicle item information (e.g., vehicle model) corresponding to the vehicle attribute to be deleted in the content input box displayed on the user interface. Based on the received attribute ID and vehicle item information, the system queries a JSON-formatted database file to check if the vehicle attribute to be deleted exists in the JSON-formatted database file. If the check result indicates existence (i.e., the vehicle attribute to be deleted exists in the JSON-formatted database file), the system receives the deletion reason input by the user through the user interface and writes the deletion reason into the JSON-formatted database file, then deletes the vehicle attribute to be deleted from the JSON-formatted database file. If the check result indicates non-existence (i.e., the vehicle attribute to be deleted does not exist in the JSON-formatted database file), the current attribute deletion operation ends directly.

[0144] In another preferred embodiment, the operation type of the management operation includes an attribute modification operation, wherein the vehicle attribute to be managed is the vehicle attribute to be modified.

[0145] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0146] The user interface receives the attribute ID corresponding to the vehicle attribute to be modified and the vehicle item information to be modified, which are input by the user.

[0147] Based on the attribute ID and the vehicle project information, query the database file in JSON format to determine whether the vehicle attribute to be modified exists in the project to be modified;

[0148] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0149] When the check result is positive, the user inputs the modified vehicle attributes and the reason for modification through the user interface, the vehicle attributes to be modified are modified accordingly based on the modified vehicle attributes, and the reason for modification is written into the JSON format database file.

[0150] If the check result is that the attribute modification operation is terminated.

[0151] Specifically, in conjunction with the above embodiments, the management operation types include attribute modification operations. Correspondingly, the vehicle attribute to be managed is the vehicle attribute to be modified. When a user's attribute modification operation is received through the user interface, the user can enter the attribute ID corresponding to the vehicle attribute to be modified and the vehicle item information (e.g., vehicle model) to be modified in the content input box displayed on the user interface. Based on the received attribute ID and vehicle item information, the system queries a JSON-formatted database file to check if the vehicle attribute to be modified exists in the vehicle item to be modified. If the check result indicates existence (i.e., the vehicle attribute to be modified exists in the vehicle item to be modified), the system receives the modified vehicle attribute and the reason for modification input by the user through the user interface, and modifies the vehicle attribute to be modified accordingly based on the modified vehicle attribute input by the user, writing the reason for modification input by the user into the JSON-formatted database file. If the check result indicates non-existence (i.e., the vehicle attribute to be modified does not exist in the vehicle item to be modified), the current attribute modification operation ends directly.

[0152] In another preferred embodiment, the operation type of the management operation includes a query attribute operation, and the vehicle attribute to be managed is the vehicle attribute to be queried;

[0153] Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes:

[0154] The user interface receives the attribute ID, vehicle item information, function description, and signal name corresponding to the vehicle attribute to be queried, input by the user.

[0155] Based on the attribute ID, vehicle project information, function description and signal name corresponding to the vehicle attribute to be queried, query the JSON format database file to determine whether the vehicle attribute to be queried exists in the JSON format database file;

[0156] The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes:

[0157] When the check result is positive, the query result is displayed to the user through the user interface;

[0158] If the check result is that the attribute query operation does not exist, the query operation ends.

[0159] Specifically, in conjunction with the above embodiments, the management operation types include attribute query operations. Correspondingly, the vehicle attributes to be managed are the vehicle attributes to be queried. When a user's attribute query operation is received through the user interface, the user can enter the attribute ID, vehicle item information (e.g., vehicle model), function description, and signal name corresponding to the vehicle attribute to be queried in the content input boxes displayed on the user interface. Based on the received attribute ID, vehicle item information, function description, and signal name, the system queries a JSON-formatted database file to check if the vehicle attribute to be queried exists in the JSON-formatted database file. If the check result indicates existence (i.e., the vehicle attribute to be queried exists in the JSON-formatted database file), the system returns the configuration status of the vehicle attribute to be queried in all items and displays the attribute query result to the user through the user interface. If the check result indicates non-existence (i.e., the vehicle attribute to be queried does not exist in the JSON-formatted database file), the current attribute query operation ends directly.

[0160] It should be noted that the JSON-based vehicle attribute management method provided in this embodiment of the invention checks whether the information entered by the user is useful, i.e. whether it contains the required valid information (e.g., CAN signal name, attribute name, vehicle model value, etc.), according to certain rules when the user triggers an attribute query operation, before retrieving the database file in JSON format and outputting the results. This avoids the situation where developers directly obtain full attribute editing permissions.

[0161] In yet another preferred embodiment, the method further includes:

[0162] After managing the JSON-formatted database file, the managed JSON-formatted database file is submitted to the Git repository for review, insertion, and synchronization.

[0163] Specifically, in conjunction with the above embodiments, after performing the corresponding management operations on the JSON format database file, it is necessary to promptly submit the managed JSON format database file to the Git repository for Gerrit review, storage, and synchronization.

[0164] It should be noted that the use of a JSON-formatted database file in this embodiment of the invention facilitates Git repository version management and Gerrit auditing.

[0165] This invention also provides a JSON-based vehicle attribute management device for implementing the JSON-based vehicle attribute management method described in any of the above embodiments. See [link to related documentation]. Figure 2 The diagram shown is a structural block diagram of a preferred embodiment of a JSON-based vehicle attribute management device provided by the present invention. The device includes:

[0166] The management operation receiving module 11 is used to receive user management operations on vehicle attributes through the user operation interface;

[0167] The vehicle attribute checking module 12 is used to check the attributes of the vehicle to be managed according to the operation type of the management operation and the preset checking rules.

[0168] The vehicle attribute management module 13 is used to manage a preset JSON format database file based on the inspection results, the management operation, and the vehicle attributes to be managed; wherein the JSON format database file is used to store at least one vehicle attribute of at least one vehicle item.

[0169] Preferably, the management operation type includes adding attribute operation, and the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user received through the user operation interface;

[0170] Therefore, the vehicle attribute checking module 12 specifically includes:

[0171] An attribute checking unit is added to query the JSON-formatted database file based on the newly added vehicle function, and to determine whether a vehicle function matching the newly added vehicle function exists in the JSON-formatted database file.

[0172] The vehicle attribute management module 13 specifically includes a first attribute addition processing unit, used for:

[0173] When the check result is that the function does not exist, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read and write attributes and CAN signal name;

[0174] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0175] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0176] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0177] Preferably, the first attribute-adding processing unit is further configured to:

[0178] If the CAN signal name does not exist in the DBC file, determine whether the CAN signal name was entered incorrectly.

[0179] If so, the system receives the CAN signal name re-entered by the user through the user interface and processes it accordingly.

[0180] If not, then the attribute addition operation ends.

[0181] Preferably, the first attribute-adding processing unit is further configured to:

[0182] When the CAN signal name is not unique, the user interface displays the vehicle attribute information that has used the CAN signal name to the user, and determines whether it is necessary to continue adding the new vehicle function based on the vehicle attribute information that has used the CAN signal name.

[0183] If so, the system receives the attribute definition corresponding to the newly added vehicle function re-entered by the user through the user operation interface, and performs corresponding processing based on the attribute definition corresponding to the newly added vehicle function re-entered by the user.

[0184] If not, then the attribute addition operation ends.

[0185] Preferably, the vehicle attribute management module 13 further includes a second attribute processing unit, used for:

[0186] When the check result indicates that the function exists, the attribute definition of the matched vehicle function is displayed to the user through the user interface.

[0187] The user interface receives the user's judgment result regarding whether the newly added vehicle function and the matched vehicle function belong to the same function.

[0188] When the judgment result indicates that the functions do not belong to the same function, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read / write attributes and CAN signal name;

[0189] Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked;

[0190] When the CAN signal name is unique, the CAN signal name is checked according to the DBC file;

[0191] When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

[0192] Preferably, the second attribute-adding processing unit is further configured to:

[0193] When the determination result indicates that they belong to the same function, determine whether the newly added vehicle function and the matched vehicle function belong to the same vehicle item.

[0194] If not, the attribute synchronization function is used to migrate the vehicle attributes corresponding to the matched vehicle function to the newly added vehicle function, and the CAN signal name corresponding to the newly added vehicle function is configured. The obtained vehicle attributes corresponding to the newly added vehicle function are written into the JSON format database file.

[0195] If so, then the attribute addition operation ends.

[0196] Preferably, the management operation type includes an attribute deletion operation, and the vehicle attribute to be managed is the vehicle attribute to be deleted;

[0197] Therefore, the vehicle attribute checking module 12 specifically includes:

[0198] The deletion attribute receiving unit is used to receive the attribute ID and vehicle item information corresponding to the vehicle attribute to be deleted, input by the user through the user operation interface.

[0199] The deletion attribute checking unit is used to query the JSON-formatted database file based on the attribute ID and the vehicle project information to determine whether the vehicle attribute to be deleted exists in the JSON-formatted database file.

[0200] The vehicle attribute management module 13 specifically includes an attribute deletion processing unit, used for:

[0201] When the check result is that the vehicle attribute to be deleted exists, the user inputs the reason for deletion through the user interface, writes the reason for deletion into the JSON format database file, and performs deletion processing on the vehicle attribute to be deleted.

[0202] If the check result is that the attribute does not exist, the attribute deletion operation ends.

[0203] Preferably, the management operation type includes an attribute modification operation, and the vehicle attribute to be managed is the vehicle attribute to be modified.

[0204] Therefore, the vehicle attribute checking module 12 specifically includes:

[0205] The attribute receiving unit is used to receive the attribute ID corresponding to the vehicle attribute to be modified and the vehicle item information to be modified, which are input by the user through the user operation interface.

[0206] The attribute checking unit is used to query the database file in JSON format based on the attribute ID and the vehicle project information to determine whether the vehicle attribute to be modified exists in the project to be modified.

[0207] The vehicle attribute management module 13 specifically includes an attribute modification processing unit, used for:

[0208] When the check result is positive, the user inputs the modified vehicle attributes and the reason for modification through the user interface, the vehicle attributes to be modified are modified accordingly based on the modified vehicle attributes, and the reason for modification is written into the JSON format database file.

[0209] If the check result is that the attribute modification operation is terminated.

[0210] Preferably, the management operation type includes a query attribute operation, and the vehicle attribute to be managed is the vehicle attribute to be queried;

[0211] Therefore, the vehicle attribute checking module 12 specifically includes:

[0212] The attribute query receiving unit is used to receive the attribute ID, vehicle item information, function description and signal name corresponding to the vehicle attribute to be queried, input by the user through the user operation interface;

[0213] The query attribute checking unit is used to query the JSON format database file based on the attribute ID, vehicle project information, function description and signal name corresponding to the vehicle attribute to be queried, and to determine whether the vehicle attribute to be queried exists in the JSON format database file.

[0214] The vehicle attribute management module 13 specifically includes a query attribute processing unit, used for:

[0215] When the check result is positive, the query result is displayed to the user through the user interface;

[0216] If the check result is that the attribute query operation does not exist, the query operation ends.

[0217] Preferably, the device further includes:

[0218] The database file submission module is used to submit the managed JSON-formatted database file to the Git repository for review, storage, and synchronization after managing the JSON-formatted database file.

[0219] It should be noted that the JSON-based vehicle attribute management device provided in this embodiment of the invention can implement all the processes of the JSON-based vehicle attribute management method described in any of the above embodiments. The functions and technical effects of each module and unit in the device are the same as those of the JSON-based vehicle attribute management method described in the above embodiments, and will not be repeated here.

[0220] This invention also provides a terminal device, see [link to relevant documentation]. Figure 3 The diagram shown is a structural block diagram of a preferred embodiment of a terminal device provided by the present invention. The terminal device includes a processor 10, a memory 20, and a computer program stored in the memory 20 and configured to be executed by the processor 10. When the processor 10 executes the computer program, it implements the JSON-based vehicle attribute management method described in any of the above embodiments.

[0221] Preferably, the computer program can be divided into one or more modules / units (such as computer program 1, computer program 2, ...), and the one or more modules / units are stored in the memory 20 and executed by the processor 10 to complete the present invention. The one or more modules / units can be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program in the terminal device.

[0222] The processor 10 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor, or the processor 10 may be any conventional processor. The processor 10 is the control center of the terminal device, connecting various parts of the terminal device through various interfaces and lines.

[0223] The memory 20 mainly includes a program storage area and a data storage area. The program storage area can store the operating system, applications required for at least one function, etc., while the data storage area can store related data, etc. Furthermore, the memory 20 can be a high-speed random access memory, or a non-volatile memory, such as a plug-in hard disk, a smart media card (SMC), a secure digital card (SD), and a flash card, or other volatile solid-state storage devices.

[0224] It should be noted that the aforementioned terminal devices may include, but are not limited to, processors and memory, as will be understood by those skilled in the art. Figure 3 The structural block diagram is merely an example of the terminal device described above and does not constitute a limitation on the terminal device. It may include more or fewer components than shown in the diagram, or combine certain components, or use different components.

[0225] In summary, the vehicle attribute management method, apparatus, and terminal device based on JSON provided in this invention have the following beneficial effects:

[0226] (1) By adopting the database file management method in JSON format, it can support the management of vehicle attributes for all vehicle projects, realize the unified and platform-based management of vehicle attributes for multiple projects, and prevent interference between projects, thereby solving the problem of attribute asynchrony between projects.

[0227] (2) It can avoid the situation where users directly obtain full attribute editing permissions, which is beneficial to the development and management of multi-project vehicle control work;

[0228] (3) It can perform uniqueness and alignment checks on the CAN signal names entered by the user. By configuring the corresponding attribute management check function, it can solve the problems of duplicate attribute definition, incorrect attribute definition, and inability to identify content changes caused by operation errors based on the table format, thereby effectively preventing problematic vehicle attributes from entering the JSON format database file.

[0229] (4) Using a database file in JSON format is beneficial for Git repository version management and Gerrit auditing.

[0230] The above description is only a preferred embodiment of the present invention. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the technical principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A JSON-based vehicle attribute management method, characterized in that, include: The system receives user management commands for vehicle attributes through a user interface. The vehicle attributes to be managed are checked according to the operation type and preset inspection rules of the management operation. Based on the inspection results, the preset JSON format database file is managed according to the management operation and the vehicle attributes to be managed; wherein, the JSON format database file is used to store at least one vehicle attribute of at least one vehicle item; The management operation includes adding attribute operations, and the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user through the user operation interface. Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes: Based on the newly added vehicle function, query the database file in JSON format to determine whether there is a vehicle function in the database file that matches the newly added vehicle function; The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes: When the check result is that the function does not exist, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read and write attributes and CAN signal name; Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked; When the CAN signal name is unique, the CAN signal name is checked according to the DBC file; When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

2. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The method further includes: If the CAN signal name does not exist in the DBC file, determine whether the CAN signal name was entered incorrectly. If so, the system receives the CAN signal name re-entered by the user through the user interface and processes it accordingly. If not, then the attribute addition operation ends.

3. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The method further includes: When the CAN signal name is not unique, the user interface displays the vehicle attribute information that has used the CAN signal name to the user, and determines whether it is necessary to continue adding the new vehicle function based on the vehicle attribute information that has used the CAN signal name. If so, the system receives the attribute definition corresponding to the newly added vehicle function re-entered by the user through the user operation interface, and performs corresponding processing based on the attribute definition corresponding to the newly added vehicle function re-entered by the user. If not, then the attribute addition operation ends.

4. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The method further includes: When the check result indicates that the function exists, the attribute definition of the matched vehicle function is displayed to the user through the user interface. The user interface receives the user's judgment result regarding whether the newly added vehicle function and the matched vehicle function belong to the same function. When the judgment result indicates that the functions do not belong to the same function, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read / write attributes and CAN signal name; Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked; When the CAN signal name is unique, the CAN signal name is checked according to the DBC file; When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

5. The JSON-based vehicle attribute management method as described in claim 4, characterized in that, The method further includes: When the determination result indicates that they belong to the same function, determine whether the newly added vehicle function and the matched vehicle function belong to the same vehicle item. If not, the attribute synchronization function is used to migrate the vehicle attributes corresponding to the matched vehicle function to the newly added vehicle function, and the CAN signal name corresponding to the newly added vehicle function is configured. The obtained vehicle attributes corresponding to the newly added vehicle function are written into the JSON format database file. If so, then the attribute addition operation ends.

6. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The management operation includes the operation of deleting attributes, and the vehicle attributes to be managed are the vehicle attributes to be deleted. Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes: The user interface receives the attribute ID and vehicle item information corresponding to the vehicle attribute to be deleted, input by the user. Based on the attribute ID and the vehicle project information, query the JSON-formatted database file to determine whether the vehicle attribute to be deleted exists in the JSON-formatted database file; The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes: When the check result is that the vehicle attribute to be deleted exists, the user inputs the reason for deletion through the user interface, writes the reason for deletion into the JSON format database file, and performs deletion processing on the vehicle attribute to be deleted. If the check result is that the attribute does not exist, the attribute deletion operation ends.

7. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The management operation includes an attribute modification operation, and the vehicle attribute to be managed is the vehicle attribute to be modified. Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes: The user interface receives the attribute ID corresponding to the vehicle attribute to be modified and the vehicle item information to be modified, which are input by the user. Based on the attribute ID and the vehicle project information, query the database file in JSON format to determine whether the vehicle attribute to be modified exists in the project to be modified; The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes: When the check result is positive, the user inputs the modified vehicle attributes and the reason for modification through the user interface, the vehicle attributes to be modified are modified accordingly based on the modified vehicle attributes, and the reason for modification is written into the JSON format database file. If the check result is that the attribute modification operation is terminated.

8. The JSON-based vehicle attribute management method as described in claim 1, characterized in that, The management operation includes an attribute query operation, where the vehicle attribute to be managed is the vehicle attribute to be queried. Then, the step of checking the attributes of the vehicle to be managed according to the operation type of the management operation and the preset inspection rules specifically includes: The user interface receives the attribute ID, vehicle item information, function description, and signal name corresponding to the vehicle attribute to be queried, input by the user. Based on the attribute ID, vehicle project information, function description and signal name corresponding to the vehicle attribute to be queried, query the JSON format database file to determine whether the vehicle attribute to be queried exists in the JSON format database file; The management of a preset JSON-formatted database file based on the inspection results, the management operation, and the attributes of the vehicle to be managed specifically includes: When the check result is positive, the query result is displayed to the user through the user interface; If the check result is that the attribute query operation does not exist, the query operation ends.

9. The JSON-based vehicle attribute management method as described in any one of claims 1 to 8, characterized in that, The method further includes: After managing the JSON-formatted database file, the managed JSON-formatted database file is submitted to the Git repository for review, insertion, and synchronization.

10. A vehicle attribute management device based on JSON, characterized in that, For implementing the JSON-based vehicle attribute management method as described in any one of claims 1 to 9, the apparatus comprises: The management operation receiving module is used to receive user management operations on vehicle attributes through the user interface. The vehicle attribute checking module is used to check the attributes of the vehicles to be managed according to the operation type of the management operation and the preset checking rules. The vehicle attribute management module is used to manage a preset JSON format database file based on the inspection results, the management operation, and the vehicle attributes to be managed; wherein, the JSON format database file is used to store at least one vehicle attribute for at least one vehicle item. The management operation includes adding attribute operations, and the vehicle attribute to be managed is the vehicle attribute corresponding to the new vehicle function input by the user through the user operation interface. Therefore, the vehicle attribute checking module specifically includes: An attribute checking unit is added to query the JSON-formatted database file based on the newly added vehicle function, and to determine whether a vehicle function matching the newly added vehicle function exists in the JSON-formatted database file. The vehicle attribute management module specifically includes a first attribute addition processing unit, used for: When the check result is that the function does not exist, the user inputs the attribute definition corresponding to the newly added vehicle function through the user operation interface; wherein, the attribute definition includes detailed function description, read and write attributes and CAN signal name; Within the vehicle category to which the newly added vehicle function belongs, the uniqueness of the CAN signal name is checked; When the CAN signal name is unique, the CAN signal name is checked according to the DBC file; When the CAN signal name exists in the DBC file, the attribute ID value corresponding to the newly added vehicle function is generated, and the attribute definition and the attribute ID value are written into the JSON format database file.

11. A terminal device, characterized in that, The system includes a processor, a memory, and a computer program stored in the memory and configured to be executed by the processor, wherein the processor, when executing the computer program, implements the JSON-based vehicle attribute management method as described in any one of claims 1 to 9.

Images