Updating method, device and equipment for CAN database file and storage medium

Abstract

The application relates to the technical field of data processing, in particular to a development CAN database file updating method, device and equipment and a storage medium. The updating method comprises the following steps: obtaining a new CAN database file, an old CAN database file and a development CAN database file; analyzing the new CAN database file and the old CAN database file to obtain a new object list dictionary database and an old object list dictionary database; performing string splicing on attribute parameters of each object in the new object list dictionary database and the old object list dictionary database to obtain a new object list string and an old object list string; comparing the new object list string and the old object list string based on a preset comparison rule to obtain an object update log; and updating the development CAN database file based on the object update log. The updating method can quickly and accurately update the development CAN database file.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and specifically to a method, apparatus, device, and storage medium for updating CAN database files for development. Background Technology

[0002] As the core carrier describing network communication protocols, the CAN database file's change management is a crucial link in the entire development and maintenance process. With the widespread adoption of agile development and continuous integration / continuous deployment (CI / CD) concepts, project iteration speeds have accelerated, leading to a significant increase in the frequency of CAN database file changes. In actual development, the CAN database file ultimately used for software deployment is built based on a specific older version of the CAN database file released by the vehicle manufacturer. This version is optimized, tailored, and supplemented with diagnostic, calibration, and special agreement messages according to the vehicle's own software architecture and functional requirements. Therefore, the new version of the CAN database file released by the vehicle manufacturer cannot be used directly for development. When it is necessary to use a new version of the CAN database file to update the CAN database file used for development, traditional update methods expose many inherent defects. For example, update conflict detection is often not accurate enough, and it is easy to miss important changes in the message or signal layer, such as start bit, length, precision, offset, and numerical range, which leads to potential errors being carried into subsequent stages. At the same time, the update operation is inefficient, relying heavily on manual intervention for conflict arbitration and version alignment, which is not only time-consuming and labor-intensive, but also increases the risk of human error. In addition, existing update methods lack the ability to conduct a global review of the overall database structure, making it difficult to systematically assess the impact of a local change on the compatibility of the entire communication protocol, signal mapping relationships, and network load. Moreover, tracing the update history is also difficult, making it difficult to quickly locate the source of differences between specific versions or restore the intention of the change. Summary of the Invention

[0003] To address the aforementioned problems in the prior art, the present invention aims to provide a method, apparatus, device, and storage medium for updating CAN database files for development, which can quickly and accurately update CAN database files for development.

[0004] To address the above problems, this invention provides a method for updating a CAN database file for development, comprising:

[0005] Obtain the new version of the CAN database file, the old version of the CAN database file, and the CAN database file for development;

[0006] The new and old versions of the CAN database file are parsed to obtain the new and old object list dictionary databases, respectively. Each of the new and old object list dictionary databases contains multiple objects.

[0007] Concatenate the attribute parameters of each object in the new version of the object list dictionary database and the old version of the object list dictionary database to obtain the new version of the object list string and the old version of the object list string respectively;

[0008] The new version of the object list string and the old version of the object list string are compared based on preset comparison rules to obtain the object update log;

[0009] Update the CAN database file used for development based on the object update log.

[0010] Furthermore, the new and old CAN database files are parsed to obtain the new and old object list dictionary databases, respectively, including:

[0011] Text parsing is performed on both the new and old CAN database files to construct a global object database. The global object database includes the new attribute set corresponding to each object in the new CAN database file and the old attribute set corresponding to each object in the old CAN database file.

[0012] Based on preset attribute fields, the new attribute set is traversed to determine the new definition line corresponding to each object in the new CAN database file, and the old attribute set is traversed to determine the old definition line corresponding to each object in the old CAN database file.

[0013] Based on the new definition line, obtain the new attribute parameters corresponding to each object in the new attribute set, and based on the old definition line, obtain the old attribute parameters corresponding to each object in the old attribute set.

[0014] Based on a preset data structure, the new version of attribute parameters are constructed into a new version of the object list dictionary database, and the old version of attribute parameters are constructed into an old version of the object list dictionary database.

[0015] Furthermore, the attribute parameters corresponding to each object in the new version of the object list dictionary database and the old version of the object list dictionary database are concatenated to obtain the new version of the object list string and the old version of the object list string, respectively, including:

[0016] Iterate through the dictionary database of new object lists, and concatenate the new attribute parameters of each object into a new object list string;

[0017] Iterate through the dictionary database of old object lists, and concatenate the old attribute parameters corresponding to each object into a string representing the old object list.

[0018] Furthermore, the new version of the object list string and the old version of the object list string are compared based on preset comparison rules to obtain the object update log, including:

[0019] Get the unique identifier of the new version from the list string of new objects, and the unique identifier of the old version from the list string of old objects;

[0020] Based on the new and old unique identifiers, the new object list string and the old object list string are compared using preset comparison rules to determine the objects to be added and the objects to be deleted.

[0021] An object update log is constructed based on the new version of the attribute parameters corresponding to the object to be added and the old version of the attribute parameters corresponding to the object to be deleted.

[0022] Furthermore, the preset comparison rules include:

[0023] If the new version of the unique identifier is the same as the old version of the unique identifier, compare the new version of the object list string corresponding to the new version of the unique identifier with the old version of the object list string corresponding to the old version of the unique identifier;

[0024] If any character in the new object list string is different from the old object list string, the object corresponding to the old object list string is determined as an object to be deleted, and the object in the new object list string is determined as an object to be added.

[0025] Furthermore, the preset comparison rules also include:

[0026] If the new version unique identifier is inconsistent with the old version unique identifier of each old version object list string, the object corresponding to the new version object list string containing the new version unique identifier is determined as the object to be added;

[0027] If the old version unique identifier is inconsistent with the new version unique identifier of each new version object list string, the object corresponding to the old version object list string containing the old version unique identifier is identified as the object to be deleted.

[0028] Furthermore, the development CAN database file is obtained, and based on the object update log, the development CAN database file is updated, including:

[0029] The CAN database file used for development is parsed to build a development list database;

[0030] Based on the object update log, obtain the dictionary database of objects to be deleted and the dictionary database of objects to be added, corresponding to the objects to be deleted and the objects to be added.

[0031] Based on the dictionary database of objects to be deleted, delete the old attribute parameters corresponding to the objects to be deleted from the development list database;

[0032] Based on the dictionary database of objects to be added, new attribute parameters corresponding to the objects to be added are added to the development list database;

[0033] Write the development list database to the development CAN database file to complete the update of the development CAN database file.

[0034] Furthermore, based on the dictionary database of objects to be deleted, the old attribute parameters corresponding to the objects to be deleted are deleted from the development list database, including:

[0035] Based on the dictionary database of objects to be deleted, determine the old version unique identifier and old version attribute parameters for each object to be deleted;

[0036] Based on the old version unique identifier and old version attribute parameters of the object to be deleted, obtain the features to be matched and deleted;

[0037] Based on the feature to be matched and deleted, traverse the development list database and delete the old attribute parameters in the development list database that match the feature to be matched and deleted.

[0038] Furthermore, the objects to be added include message objects to be added, the dictionary database of objects to be added includes a database of messages to be added, and the database of messages to be added includes the new message attribute parameters corresponding to the message objects to be added, and

[0039] Based on the dictionary database of objects to be added, new attribute parameters corresponding to the objects to be added are added to the development list database, including:

[0040] Traverse the development list database to determine the first insertion position for the new message attribute parameters corresponding to the new message object to be added;

[0041] Based on the database of messages to be added, insert the new message attribute parameters corresponding to the message object to be added at the first insertion position.

[0042] Furthermore, the objects to be added also include signal objects to be added, the dictionary database of objects to be added includes a database of signals to be added, and the database of signals to be added includes a dictionary of new signal attribute parameters corresponding to the signal objects to be added; and

[0043] Based on the dictionary database of objects to be added, new attribute parameters corresponding to the objects to be added are added to the development list database, including:

[0044] When the object to be added is a signal object to be added, the new CAN database file is parsed to construct the original configuration list database;

[0045] Based on the new version of the signal attribute parameter dictionary, the original configuration list database is traversed to obtain the original configuration list database to be added. The original configuration list database to be added includes the attribute configuration information to be added corresponding to the new version of the signal attribute parameters.

[0046] Traverse the development list database to determine the second insertion position for inserting the new attribute configuration information corresponding to the new signal object;

[0047] Based on the database of the original configuration list to be added, insert the attribute configuration information corresponding to the signal object to be added at the second insertion position.

[0048] Furthermore, the development of update methods using CAN database files also includes:

[0049] Before concatenating the attribute parameters of each object in the new version of the object list dictionary database and the old version of the object list dictionary database, a preset whitelist is obtained. The preset whitelist includes the identifiers of objects that do not need to be updated.

[0050] Based on a preset whitelist, objects corresponding to identifiers are filtered out from both the new and old object list dictionary databases.

[0051] Another aspect of the present invention provides an apparatus for updating a CAN database file for development, comprising:

[0052] The acquisition module is used to acquire both the new and old versions of the CAN database file.

[0053] The parsing module is used to parse the new version of the CAN database file and the old version of the CAN database file, and obtain the new version of the object list dictionary database and the old version of the object list dictionary database respectively. The new version of the object list dictionary database and the old version of the object list dictionary database each contain multiple objects.

[0054] The string concatenation module is used to concatenate the attribute parameters of each object in the new version of the object list dictionary database and the old version of the object list dictionary database, and obtain the new version of the object list string and the old version of the object list string respectively;

[0055] The comparison module is used to compare the new version of the object list string with the old version of the object list string based on preset comparison rules in order to obtain the object update log;

[0056] The update module is used to obtain the CAN database file for development and update the CAN database file based on the object update log.

[0057] In another aspect, the present invention provides an electronic device comprising a processor and a memory, wherein the memory stores at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the method for updating a CAN database file for development as described above.

[0058] In another aspect, the present invention provides a computer-readable storage medium storing at least one instruction or at least one program, which is loaded and executed by a processor to implement the method for updating a CAN database file for development as described above.

[0059] The above-described technical solution of the present invention has at least one of the following beneficial effects:

[0060] The update method for the development CAN database file according to an embodiment of the present invention parses the new and old versions of the CAN database file separately, converting them into an object list dictionary database. Then, it concatenates the attribute parameters of each object into strings and compares them one by one according to preset rules. This comprehensively obtains all object-level changes between the new and old versions of the CAN database file and generates a structured object update log. Based on this, the development CAN database file is accurately updated according to the object update log. This avoids omissions and errors that may occur during manual comparison and eliminates the need for a full merge of the two complete databases, effectively simplifying the update process and improving the update efficiency and reliability of the development CAN database file. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of the implementation environment provided in one embodiment of the present invention;

[0062] Figure 2 This is a flowchart illustrating a method for developing an update method using a CAN database file, as described in one embodiment of the present invention.

[0063] Figure 3 This is a flowchart illustrating the process of obtaining a new version of the object list dictionary database and an old version of the object list dictionary database in one embodiment of the present invention;

[0064] Figure 4 This is a flowchart illustrating the process of obtaining the new version of the object list string and the old version of the object list string in one embodiment of the present invention;

[0065] Figure 5 This is a flowchart of obtaining object update logs in one embodiment of the present invention;

[0066] Figure 6 This is a flowchart illustrating the updating of the CAN database file for development in one embodiment of the present invention;

[0067] Figure 7 This is a schematic diagram of the structure of an update device for a CAN database file developed in one embodiment of the present invention;

[0068] Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of the present invention. Detailed Implementation

[0069] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, 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, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention are within the scope of protection of the present invention.

[0070] The following describes, with reference to the accompanying drawings, a method for updating a CAN database file for development according to an embodiment of the present invention.

[0071] Reference manual attached Figure 1 , Figure 1 A schematic diagram illustrating the implementation environment of the CAN database file update method for the development of this invention is shown. For example... Figure 1 As shown, the implementation environment may include computing device 1000. The computing device 1000 may be, but is not limited to, various servers, personal computers, laptops, smartphones, tablets, and portable wearable devices. The server may be a standalone server, a server cluster composed of multiple servers, or a distributed computing device 1000. It may also be an edge server or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0072] The computing device 1000 first acquires the new CAN database file 1001, the old CAN database file 1002, and the development CAN database file 1003. Then, the computing device 1000 parses the new CAN database file 1001 and the old CAN database file 1002, obtaining a new object list dictionary database and an old object list dictionary database, respectively. Each of these databases contains multiple objects. After acquiring these databases, the computing device 1000 further concatenates the attribute parameters corresponding to each object in both databases, obtaining new and old object list strings. These strings are then compared based on a preset comparison rule to obtain the object update log. This allows for a comprehensive and accurate acquisition of all object-level changes between the old and new CAN database files. Finally, the computing device 1000 updates the development CAN database file 1003 according to the object update log. This avoids potential omissions and errors from manual comparison and eliminates the need for a full merge of the two complete databases, effectively simplifying the update process and improving the efficiency and reliability of updating the CAN database files used in development.

[0073] Below, please refer to the attached instruction manual. Figure 2 This illustrates a method for updating a CAN database file for development provided by an embodiment of the present invention, which can be applied to... Figure 1 The method is implemented in computing device 1000. Specifically, the method may include the following steps:

[0074] S100: Obtain the new version of the CAN database file, the old version of the CAN database file, and the CAN database file for development.

[0075] In this embodiment, the computing device can first acquire the new version and the old version of the CAN database file that need to be compared, and simultaneously acquire the development CAN database file currently being used in the project development process. The new version of the CAN database file represents the latest design version released by the vehicle developer, the old version represents a historical version, and the development CAN database file represents the target file that ultimately needs to be updated. By acquiring these three database files simultaneously, a data foundation can be provided for subsequent identification of database version differences and automatic updating of the development CAN database file.

[0076] S200: Parse the new version of the CAN database file and the old version of the CAN database file to obtain the new version of the object list dictionary database and the old version of the object list dictionary database respectively.

[0077] In this embodiment, both the new and old versions of the object list dictionary database include multiple objects. Objects can include message objects and signal objects. A message object typically contains one or more signal objects. Messages are used to complete data transmission on the CAN bus, while signals represent specific data fields within the message. Each signal is organized and managed according to its corresponding message. By constructing the new and old versions of the object list dictionary database, the computing device can convert the database file into a unified and easily searchable data organization format. This allows objects in different versions of the database to establish corresponding relationships, providing a unified data foundation for quickly identifying added, deleted, and modified objects, and improving the efficiency and accuracy of database difference analysis.

[0078] S300. Concatenate the attribute parameters corresponding to each object in the new version object list dictionary database and the old version object list dictionary database to obtain the new version object list string and the old version object list string respectively.

[0079] In this embodiment, the computing device can concatenate the attribute parameters of each object into strings according to a preset order, forming an object list string that uniquely represents the object's content. Since the object's attribute parameters are uniformly converted into string form, it avoids comparing different attributes item by item, improving the comparability of different versions of the object's content. Furthermore, when any attribute changes, the corresponding object list string also changes, thus accurately reflecting the actual modifications to the object and improving the accuracy and efficiency of subsequent version difference identification.

[0080] S400: Compare the new version of the object list string with the old version of the object list string based on the preset comparison rules to obtain the object update log.

[0081] In this embodiment, the computing device can compare the new and old object list strings item by item according to preset string comparison rules to identify whether objects have been added, deleted, or had their attributes modified, and generate corresponding object update logs. The object update logs not only record the objects that have changed, but also the specific update type and content, providing a complete update basis for subsequent automatic updates of the CAN database file used for development. Compared to manually checking database differences item by item, this method can quickly locate all changed objects, reduce omissions and misjudgments, and improve the reliability of version management.

[0082] S500 updates the CAN database file used for development based on the object update log.

[0083] In this embodiment, the computing device can perform corresponding add, delete, and modify operations on the development CAN database file based on the update content recorded in the object update log, so that the development CAN database file is automatically synchronized to the data status corresponding to the new version of the CAN database file. By using the object update log for automatic updates, the workload of manual maintenance can be effectively reduced, configuration errors caused by human operation can be minimized, and the consistency between the development CAN database file and the new version of the CAN database file can be ensured.

[0084] Below, each step will be explained in detail.

[0085] (a) Obtain the new version of the CAN database file, the old version of the CAN database file, and the CAN database file for development.

[0086] Specifically, the new CAN database file is the latest released or maintained CAN database file, containing object information added, modified, or deleted in the current version; the old CAN database file is the previous version database file corresponding to the new CAN database file, used as a benchmark for version difference analysis; the development CAN database file is the CAN database file currently maintained and used by developers, which is based on the old CAN database file and has undergone customized modifications during project development, therefore it is not entirely equivalent to the old CAN database file. Since the development CAN database file often contains newly added messages, signals, or attribute configurations during the project development phase, the new CAN database file cannot be directly overwritten with the development CAN database file, otherwise existing configurations may be lost during development. Therefore, this application first obtains the new CAN database file, the old CAN database file, and the development CAN database file simultaneously, providing a data foundation for subsequent analysis of changes in the new database compared to the old database, and accurately synchronizing the corresponding changes to the development CAN database file, thereby achieving automatic updates to the development CAN database file.

[0087] (ii) Obtain the new version of the object list dictionary database and the old version of the object list dictionary database.

[0088] The following describes the steps (i.e., step S200) for parsing the new and old CAN database files to obtain the new and old object list dictionary databases, respectively. Figure 3 As shown, in one embodiment of the present invention, step S200 may include the following steps S210-S240:

[0089] S210. Perform text parsing on both the new and old CAN database files to construct a global object database.

[0090] In this embodiment, the computing device first performs text parsing on both the new and old CAN database files, identifying various definition information within them, and constructs a global object database according to the database hierarchy. This global object database includes the new attribute set corresponding to each object in the new CAN database file and the old attribute set corresponding to each object in the old CAN database file. Specifically, the global object database is used to completely store all objects and their corresponding attribute information in both the new and old CAN database files. Objects can include message objects and signal objects. Message objects describe a CAN message frame and include message-level attributes such as message name, CAN ID, data length (DLC), transmission period, transmitting node, message type, and transmission method. Each message object can also be associated with one or more signal objects. Each signal object describes a data field in the message and includes signal-level attributes such as signal name, start bit, data length, byte order, data type, scale factor, offset, unit, value table, and comments. Therefore, the global object database is organized using a hierarchical data structure. The outermost layer records basic database information, the middle layer records each message object, and each message object is further associated with multiple corresponding signal objects and their respective attribute information. This fully preserves the object organization relationships and attribute information in both the new and old versions of the CAN database file, providing a unified data foundation for subsequent object parsing and version comparison.

[0091] S220. Based on preset attribute fields, traverse the new attribute set to determine the new definition line corresponding to each object in the new CAN database file, and traverse the old attribute set to determine the old definition line corresponding to each object in the old CAN database file.

[0092] In this embodiment, after constructing the global object database, the computing device can traverse both the new and old attribute sets. Based on pre-configured attribute field identification rules, it categorizes attribute information belonging to the same object and determines the new definition line for each object in the new CAN database file and the old definition line for each object in the old CAN database file. The new and old definition lines represent the starting definition position of an object, and by combining the ending position or the next object definition position, all attribute information belonging to the same object can be associated. By determining the definition lines corresponding to each object, the attribute ranges of different objects can be accurately divided, ensuring that the attribute information of both the message object and its associated signal object can be completely extracted. This avoids confusion between attributes of different objects and provides accurate positioning basis for subsequent attribute parameter extraction.

[0093] S230. Based on the new version definition line, obtain the new version attribute parameters corresponding to each object in the new version attribute set, and based on the old version definition line, obtain the old version attribute parameters corresponding to each object in the old version attribute set.

[0094] In this embodiment, the computing device can obtain the new version attribute parameters corresponding to each object in the new version attribute set based on the determined new version definition line, and obtain the old version attribute parameters corresponding to each object in the old version attribute set based on the determined old version definition line. Specifically, for message objects, the computing device can extract attribute parameters such as CAN ID, message name, transmission period, data length, transmission node, message type, transmission method, and message comments; for signal objects, it can extract attribute parameters such as signal name, start bit, length, byte order, data type, scale factor, offset, unit, value range, and comments. Since all objects are parsed according to a unified preset attribute field, objects of the same type in different version databases can form a consistent attribute parameter structure, providing a unified data source for subsequent attribute comparisons between objects of different versions, while ensuring good compatibility when adding new attribute fields or extending attribute parameters.

[0095] S240. Based on a preset data structure, construct a new version of the object list dictionary database for the new version of the attribute parameters, and construct an old version of the object list dictionary database for the old version of the attribute parameters.

[0096] In this embodiment, the computing device can organize the extracted new and old attribute parameters according to a preset data structure to construct a new object list dictionary database and an old object list dictionary database. Both the new and old object list dictionary databases use objects as the basic storage unit. Each object corresponds to an object dictionary entry, which stores the object's unique identifier and all its corresponding attribute parameters. Objects can include message objects and signal objects. Different types of objects are stored using a unified data organization method, thus forming a standardized object list. For signal objects, information about their associated message object can also be recorded to maintain the hierarchical relationship between messages and signals. By constructing the new and old object list dictionary databases, the text descriptions in the original CAN database file can be converted into a unified, easily indexable, and quickly accessible data structure. This allows objects in different versions of the database to quickly establish a correspondence based on their unique identifiers, providing a data foundation for subsequent object attribute string generation, version difference analysis, and automatic updates of the CAN database file for development.

[0097] (iii) Obtain the new version object list string and the old version object list string respectively.

[0098] The following describes the steps (i.e., step S300) to concatenate the attribute parameters of each object in the new and old object list dictionary databases to obtain the new and old object list strings respectively. Figure 4 As shown, in one embodiment of the present invention, step S300 may include the following steps S310-S320:

[0099] S310. Traverse the dictionary database of new object list and concatenate the new attribute parameters corresponding to each object into a new object list string.

[0100] In this embodiment, the computing device can traverse the new object list dictionary database, sequentially read the attribute parameters corresponding to each object, and concatenate the strings according to a pre-set attribute arrangement order and a unified delimitation rule to generate a new object list string that corresponds one-to-one with each object. Specifically, for a message object, the message-level attributes such as message name, CAN ID, data length (DLC), transmission period, transmitting node, message type, transmission method, and message comment can be concatenated into a new object list string. For a signal object, the signal-level attributes such as the message name, CAN ID, signal name, start bit, data length, byte order, data type, scale factor, offset, unit, value table, signal comment, and transmission method can be concatenated into a new object list string. Each object ultimately corresponds to a unique new object list string. Thus, by uniformly encoding multiple discrete attributes into a standard format string, not only can the complete attribute information of the object be preserved, but it also facilitates the rapid identification of whether the object has changed using string comparison methods, reducing the complex processing process brought about by field-by-field comparison.

[0101] S320. Traverse the dictionary database of old object lists and concatenate the old attribute parameters corresponding to each object into the old object list string.

[0102] In this embodiment, the computing device can traverse the old version of the object list dictionary database using the same attribute arrangement rules and string concatenation rules as the new version of the object list dictionary database, sequentially concatenating the attribute parameters corresponding to each object into the corresponding old version object list string. Since the new and old version object list strings use completely consistent attribute order, data format, and delimiter rules, the string content corresponding to the same object remains consistent when the attributes do not change. However, when any attribute of an object is added, deleted, or modified, its corresponding string will also change. Therefore, complex multi-attribute comparisons between objects can be transformed into comparisons between standard strings, enabling rapid location of changed objects and accurate identification of changed content. This provides a unified data foundation for subsequent object update log generation, while improving the efficiency and automation capabilities of difference analysis between different versions of the CAN database file.

[0103] (iv) Obtain the object update log.

[0104] The following describes the steps (i.e., step S400) for comparing the new and old versions of the object list string based on preset comparison rules to obtain the object update log. Figure 5 As shown, in one embodiment of the present invention, step S400 may include the following steps S410-S430:

[0105] S410. Obtain the new version unique identifier from each new version object list string, and the old version unique identifier from each old version object list string.

[0106] In this embodiment, the computing device can traverse both the new and old object list strings to obtain a unique identifier for each object corresponding to a new or old object list string. This unique identifier uniquely represents an object, and different object types use different unique identifier rules. For example, for message objects, the message name, CAN ID, or a combination of both can be used as the unique identifier; for signal objects, a combination of the associated message identifier and the signal name can be used as the unique identifier, ensuring that each object can be uniquely located. After obtaining the unique identifier, a correspondence between the new and old objects can be established, providing an index for subsequent object matching and difference analysis. Compared to directly comparing all objects item by item, object location using unique identifiers significantly narrows the comparison range, improves version comparison efficiency, and avoids mismatches between different objects.

[0107] S420. Based on the new version unique identifier and the old version unique identifier, compare each new version object list string and each old version object list string using preset comparison rules to determine the objects to be added and the objects to be deleted.

[0108] In this embodiment, the computing device can first perform object matching based on the new and old unique identifiers. Specifically, when the new and old objects have the same unique identifier, they can be identified as the same object, and the corresponding object list strings can be compared as a whole.

[0109] Since both the new and old object list strings are formed by concatenating all the object's attribute parameters according to a unified rule, any difference in any single character in the string indicates that at least one attribute parameter has changed. In this case, the new object is identified as the object to be added, and the corresponding old object is identified as the object to be deleted, so that the new object can be used to replace the original object and achieve a complete update of the object's attributes. Specifically, when the object is a message object, if any message attribute such as message name, CAN ID, data length (DLC), transmission period, transmitting node, transmission mode, message type, or message comment changes, the corresponding message object list string will change, thus identifying the new version message object as the object to be added and the corresponding old version message object as the object to be deleted. When the object is a signal object, if any signal attribute such as signal name, associated message, start bit, data length, byte order, data type, scale factor, offset, unit, value table, signal comment, or transmission mode changes, the corresponding signal object list string will also change, thus identifying the new version signal object as the object to be added and the corresponding old version signal object as the object to be deleted.

[0110] When the new version unique identifier does not match the old version unique identifier in each old version object list string, it indicates that the object corresponding to the new version object list string containing the new version unique identifier is a newly added object in the new version CAN database file, and this object can be directly identified as the object to be added. For example, if a new message frame or a signal under a certain message is added to the new version CAN database file, and the corresponding unique identifier does not exist in the old version CAN database file, then the corresponding message object or signal object can be directly identified as the object to be added.

[0111] Furthermore, if the old version's unique identifier does not match the new version's unique identifier in each object list string, it indicates that the object has been deleted from the new version's CAN database file, and the object can be directly identified as an object to be deleted. For example, if a message or signal in the old version's CAN database file has been deleted from the new version's CAN database file, since there is no corresponding unique identifier in the new version's object list string, the corresponding message or signal object can be directly identified as an object to be deleted.

[0112] Therefore, by using the above-mentioned overall string comparison rules, all attributes of an object are treated as a whole for consistency judgment, without the need to analyze the changes of each attribute item by item. As long as any attribute changes, the object update can be accurately identified, thereby achieving unified detection of changes in various types of objects such as message objects and signal objects, and improving the completeness and accuracy of database version difference identification.

[0113] S430. Based on the new version of the attribute parameters corresponding to the object to be added and the old version of the attribute parameters corresponding to the object to be deleted, construct the object update log.

[0114] In this embodiment, the computing device can extract the new attribute parameters corresponding to the objects to be added from the new version object list dictionary database and the old attribute parameters corresponding to the objects to be deleted from the old version object list dictionary database, based on the determined objects to be added and deleted, and generate an object update log. The object update log can record update information for message objects and signal objects separately according to object type. Each log entry corresponds to one object and completely saves all attribute parameters of that object, while also recording the update type, such as addition or deletion. For object updates caused by attribute changes, the object update log records both the corresponding objects to be deleted and the objects to be added, thus fully reflecting the attribute information before and after the object update. For added or deleted objects, the attribute information of the corresponding objects is recorded separately.

[0115] In one specific embodiment, the object update log can be further organized according to object type and update type, such as including new message object logs, deleted message object logs, new signal object logs, and deleted signal object logs. Specifically, the new message object log records the new version of the message attribute parameters corresponding to the message object to be added, and the deleted message object log records the old version of the message attribute parameters corresponding to the message object to be deleted; similarly, the new signal object log records the new version of the signal attribute parameters corresponding to the signal object to be added, and the deleted signal object log records the old version of the signal attribute parameters corresponding to the signal object to be deleted. Each object update log can be stored with one log record per object, facilitating subsequent reading of the corresponding object's attribute parameters to perform add, delete, and other update operations on the CAN database file used for development. It also allows developers to easily view the update status of different types of objects, enabling historical tracing of the database version change process.

[0116] Therefore, by constructing an object update log, it can not only serve as a data source for subsequent automatic updates of the CAN database file, but also completely save the historical record of each database version change. This makes it easier for developers to track object changes, locate version differences, and verify update results, thereby improving the traceability and reliability of the CAN database automatic update process.

[0117] (v) Update the CAN database file used for development.

[0118] The following describes the steps for obtaining the CAN database file for development and updating it based on the object update log (i.e., step S500). Figure 6 As shown, in one embodiment of the present invention, step S500 may include the following steps S510-S550:

[0119] S510: Perform text parsing on the CAN database file used for development to construct a development list database.

[0120] In this embodiment, the computing device can first parse the development CAN database file and construct a development list database according to the original text order in the development CAN database file. Specifically, the development list database is used to store all configuration information in the development CAN database file. Each line of data corresponds to a line of configuration information in the development CAN database file, and the sequential relationship between the configuration information is maintained, thus completely preserving the organizational structure of the development CAN database file. For example, for message objects, the development list database stores message definition information and the message attribute configuration information associated with the message. For signal objects, it stores signal definition information and the corresponding signal attribute configuration information. By constructing the development list database, the development CAN database file can be converted into a data structure that is easy to traverse, delete, insert, and modify, providing a data foundation for subsequent automatic updates of the development CAN database file based on object update logs, while avoiding the processing complexity caused by directly manipulating the original file, and improving the stability and reliability of the update process.

[0121] S520. Based on the object update log, obtain the dictionary database of objects to be deleted and the dictionary database of objects to be added.

[0122] In this embodiment, the computing device can classify and organize the object update information recorded in the object update log, and construct separate databases for objects to be deleted and objects to be added. The database for objects to be deleted stores the old version's unique identifier and attribute parameters for each object to be deleted, while the database for objects to be added stores the new version's unique identifier and attribute parameters for each object to be added. Both objects to be deleted and objects to be added can include message objects and signal objects. Different types of objects are organized according to a unified data structure, and all attribute information corresponding to the objects is retained. By establishing separate databases for objects to be deleted and objects to be added, the object deletion and addition operations can be decoupled, providing a unified data input for subsequent update processes and improving the processing efficiency of automatic updates to the CAN database file used for development.

[0123] S530. Based on the dictionary database of objects to be deleted, delete the old attribute parameters corresponding to the objects to be deleted from the development list database.

[0124] In this embodiment, the computing device can first traverse the dictionary database of objects to be deleted, obtain the old version unique identifier and old version attribute parameters corresponding to each object to be deleted, and generate corresponding features to be matched and deleted based on the old version unique identifier and old version attribute parameters. Then, it traverses the development list database, searches for attribute configuration information corresponding to the old version attribute parameters that match the features to be matched and deleted, and deletes the successfully matched attribute configuration information from the development list database.

[0125] Specifically, for message objects, the message definition information and all corresponding message attribute configuration information can be deleted; for signal objects, the signal definition information and all corresponding signal attribute configuration information, such as signal comments, signal values, and signal transmission methods, are deleted. For objects to be deleted due to attribute changes, the same method is used to delete all attribute configuration information corresponding to the original object. This ensures that no old version configurations remain in the development list database, providing a complete and clean data environment for subsequent insertion of new attribute parameters and improving the consistency of updates to the CAN database file used in development.

[0126] In one specific embodiment, the computing device can obtain the old version attribute parameters corresponding to the object to be deleted based on the deleted message object log or deleted signal object log, and generate corresponding matching deletion features based on the old version unique identifier. Then, it traverses the development list database to locate the attribute configuration information corresponding to the matching deletion feature, and deletes all attribute configuration information associated with the corresponding object. For example, when the object to be deleted is a message object, the message definition information can be located based on the message unique identifier, and message attribute configuration information such as message type, sending method, sending period, message format, and message comments associated with the message can be further deleted; when the object to be deleted is a signal object, the signal definition information can be located based on the associated message and signal unique identifier, and corresponding signal attribute configuration information such as signal comments, signal sending method, signal initial value, and signal value description can be further deleted, thereby ensuring that no historical configurations corresponding to the object to be deleted are retained in the development list database.

[0127] S540. Based on the dictionary database of objects to be added, add the new version of the attribute parameters corresponding to the objects to be added to the development list database.

[0128] In this embodiment, after the computing device completes the deletion of the object to be deleted, it can obtain the new version attribute parameters corresponding to the object to be added from the dictionary database of objects to be added, determine the attribute configuration information to be added based on the new version attribute parameters, and then insert the corresponding attribute configuration information into the development list database.

[0129] Specifically, when the object to be added is a message object, the development list database is first traversed to determine the first insertion position corresponding to the message object, and then the new version message attribute parameters corresponding to the message object to be added are inserted into the first insertion position as a whole, thereby completing the addition of the message object.

[0130] In one specific embodiment, the computing device can obtain the new message attribute parameters corresponding to the message object to be added based on the new message object log, and traverse the development list database to determine the first insertion position corresponding to the message definition area and the message attribute configuration area. Subsequently, following the order of message definition information first and message attribute configuration information last, the message definition information, message type, transmission method, transmission period, message format, and other message attribute configuration information are sequentially inserted into the corresponding first insertion position, so that the new message object maintains a data organization structure consistent with the CAN database file used for development.

[0131] When the object to be added is a signal object, since signal objects typically contain multiple interrelated attribute configuration information, it is necessary to further parse the new version of the CAN database file to construct an original configuration list database. Based on the new version of the signal attribute parameters, all original attribute configuration information corresponding to the signal is obtained, forming the original configuration list database to be added. Subsequently, the development list database is traversed to determine the second insertion position corresponding to the signal object, and all attribute configuration information from the original configuration list database to be added is inserted into the second insertion position, ensuring that the new signal object maintains a consistent configuration relationship with the new version of the CAN database file.

[0132] In one specific embodiment, the computing device can obtain the new signal attribute parameters corresponding to the signal object to be added from the new signal object log, and then traverse the original configuration list database according to the new signal attribute parameters to extract the signal definition information, signal transmission method, signal initial value, signal value description, signal annotation, and other related attribute configuration information corresponding to the signal, forming the original configuration list database to be added. Subsequently, the development list database is traversed, and the second insertion position is determined according to the position of the message to which the signal object to be added belongs. Then, according to the organization order in the new CAN database file, the attribute configuration information in the original configuration list database to be added is sequentially inserted into the second insertion position, thereby ensuring that all related configurations of the new signal object can be synchronized to the development CAN database file at one time.

[0133] Therefore, by determining the insertion positions corresponding to message objects and signal objects respectively, and directly referencing the original configuration information in the new CAN database file for insertion, it is possible to ensure that all attribute configuration information corresponding to the newly added objects is complete and consistent, while maintaining the original data organization structure of the CAN database file used for development, thereby improving the accuracy and standardization of automatic update results.

[0134] S550. Write the development list database to the development CAN database file to complete the update of the development CAN database file.

[0135] In this embodiment, after deleting objects to be deleted and inserting new objects, the computing device can rewrite the updated development list database into the development CAN database file according to the original file format, generating an updated development CAN database file. Since the entire update process is completed within the development list database, it can maintain the overall structure and original development configuration of the development CAN database file while only deleting and adding objects corresponding to the object update logs, achieving automatic synchronization between the development CAN database file and the new version of the CAN database file. Compared to manually modifying the development CAN database file item by item, this method effectively reduces manual maintenance workload, minimizes human configuration errors, improves the update efficiency and version consistency of the development CAN database file, and facilitates subsequent development and maintenance.

[0136] In a preferred embodiment, during the deletion and addition processes of the development CAN database file based on the object update log, the computing device can also record and track the entire update process. Specifically, during the deletion of message objects and signal objects, the computing device can record the deleted message attribute configuration information and signal attribute configuration information in real time, and simultaneously record the execution status of the corresponding deletion operation. During the addition or merging of message objects and signal objects, the computing device can record the added or merged message attribute configuration information and signal attribute configuration information in real time, and simultaneously record the execution status of the corresponding operation, such as whether the insertion was successful, whether a conflict occurred, or whether secondary adjustments are needed. By uniformly recording the operation information of the deletion and addition / merging processes, a merging result record information reflecting the entire update process of the development CAN database file can be generated. This facilitates users in viewing and verifying the automatic update process of the development CAN database file, thereby achieving traceability and verifiability of the update process and improving the transparency and reliability of database version synchronization.

[0137] Furthermore, the development of update methods using CAN database files also includes:

[0138] Before concatenating the attribute parameters of each object in the new version of the object list dictionary database and the old version of the object list dictionary database, a preset whitelist is obtained. The preset whitelist includes the identifiers of objects that do not need to be updated.

[0139] Specifically, before concatenating object attribute parameter strings, the computing device can first obtain a preset whitelist. This whitelist stores the identification information of objects that do not require version comparison and update processing, such as the unique identifiers of message or signal objects that have reached fixed agreements with external systems or vehicle control strategies. By setting a whitelist mechanism, certain specific objects can be protected, excluding them from processing during subsequent object parsing, string concatenation, and difference comparison. This avoids accidental modification or deletion of these agreed-upon objects due to version updates, improving the controllability and security of the CAN database update process.

[0140] Furthermore, the computing device can filter out objects corresponding to identifiers from both the new and old object list dictionary databases based on a preset whitelist. Specifically, after obtaining the preset whitelist, the computing device iterates through both the new and old object list dictionary databases, filtering objects in both databases according to the identifiers of the objects in the preset whitelist, and removing objects matching the whitelist identifiers from the set of objects to be processed. Specifically, objects matched by the preset whitelist are no longer processed in subsequent string concatenation, object comparison, and update log generation processes, thus maintaining their original configuration in the development CAN database file and remaining unaffected by the current version update process. This filtering mechanism effectively protects critical or agreed-upon objects, improves overall update processing efficiency, and avoids impacting stable configurations.

[0141] In summary, the update method for the development CAN database file according to embodiments of the present invention parses the new and old versions of the CAN database file separately, converting them into an object list dictionary database. Then, it concatenates the attribute parameters of each object into strings and compares them one by one based on preset rules. This comprehensively obtains all object-level changes between the new and old versions of the CAN database file and generates a structured object update log. Based on this, the development CAN database file is accurately updated according to the object update log. This avoids omissions and errors that may occur during manual comparison and eliminates the need for a full merge of the two complete databases, effectively simplifying the update process and improving the update efficiency and reliability of the development CAN database file.

[0142] Reference manual attached Figure 7 This illustrates the structure of an update apparatus 1100 for a development CAN database file according to an embodiment of the present invention, comprising:

[0143] Module 1110 is used to acquire both the new and old versions of the CAN database file.

[0144] The parsing module 1120 is used to parse the new version of the CAN database file and the old version of the CAN database file to obtain the new version of the object list dictionary database and the old version of the object list dictionary database respectively. The new version of the object list dictionary database and the old version of the object list dictionary database each include multiple objects.

[0145] The string concatenation module 1130 is used to concatenate the attribute parameters corresponding to each object in the new version object list dictionary database and the old version object list dictionary database, and obtain the new version object list string and the old version object list string respectively.

[0146] The comparison module 1140 is used to compare the new version of the object list string and the old version of the object list string based on a preset comparison rule in order to obtain the object update log;

[0147] Update module 1150 is used to obtain the CAN database file for development and update the CAN database file for development based on the object update log.

[0148] It should be noted that the apparatus provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the apparatus provided in the above embodiments and the corresponding method embodiments belong to the same concept, and the specific implementation process can be found in the corresponding method embodiments, which will not be repeated here.

[0149] In another aspect, the present invention provides an electronic device comprising a processor and a memory, wherein the memory stores at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the method for updating a CAN database file for development as described above.

[0150] Memory can be used to store software programs and modules. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory. Memory can primarily include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for the functions, etc.; the data storage area can store data created based on the use of the device, etc. Furthermore, memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, memory can also include a memory controller to provide the processor with access to the memory.

[0151] In one specific embodiment Figure 8 A schematic diagram of the hardware structure of an electronic device for implementing the update method for a development CAN database file provided in an embodiment of the present invention is shown. The electronic device can be a computer terminal, a mobile terminal, or other devices. The electronic device can also participate in or include the anomaly detection device provided in an embodiment of the present invention. Figure 8 As shown, the electronic device 800 may include a memory 810 with one or more computer-readable storage media, a processor 820 with one or more processing cores, an input unit 830, a display unit 840, a radio frequency (RF) circuit 850, a wireless fidelity (WiFi) module 860, and a power supply 870, among other components. Those skilled in the art will understand that... Figure 8 The electronic device structure shown does not constitute a limitation on the electronic device 800, and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0152] The memory 810 can be used to store software programs and modules. The processor 820 performs various functional applications and data processing by running or executing the software programs and modules stored in the memory 810 and by calling data stored in the memory 810. The memory 810 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc.; the data storage area may store data created based on the use of the electronic device, etc. In addition, the memory 810 may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 810 may also include a memory controller to provide the processor 820 with access to the memory 810.

[0153] The processor 820 is the control center of the electronic device 800. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 810, and by calling data stored in the memory 810, it performs various functions and processes data of the electronic device 800, thereby providing overall monitoring of the electronic device 800. The processor 820 can be a central processing unit, 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. A general-purpose processor can be a microprocessor or any conventional processor.

[0154] The input unit 830 can be used to receive input numerical or character information, and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control. Specifically, the input unit 830 may include a touch-sensitive surface 831 and other input devices 832. Specifically, the touch-sensitive surface 831 may include, but is not limited to, a touchpad or a touch screen, and other input devices 832 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick.

[0155] The display unit 840 can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of electronic devices. These graphical user interfaces can be composed of graphics, text, icons, videos, and any combination thereof. The display unit 840 may include a display panel 841, which may optionally be configured as a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0156] The RF circuit 850 can be used for receiving and sending signals during information transmission or calls, and the electronic device 800 provides users with wireless broadband internet access through the WiFi module 860. Although Figure 8 WiFi module 860 is shown, but it is understood that it is not a necessary component of electronic device 800 and can be omitted as needed without changing the nature of the invention.

[0157] The electronic device 800 also includes a power supply 870 (such as a battery) to supply power to various components. Preferably, the power supply can be logically connected to the processor 820 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 870 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0158] It should be noted that, although not shown, the electronic device 800 may also include a Bluetooth module, etc., which will not be described in detail here.

[0159] In another aspect, the present invention provides a computer-readable storage medium storing at least one instruction or at least one program, which is loaded and executed by a processor to implement the method for updating a CAN database file for development as described above.

[0160] Optionally, in embodiments of the present invention, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0161] One embodiment of the present invention also provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the update method for the development CAN database file provided in the various optional implementations described above.

[0162] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, specific embodiments have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired result. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0163] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0164] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0165] Based on the various embodiments of this application described above, in the absence of explicit denial or conflict, the technical features of one embodiment may be advantageously combined with one or more other embodiments.

[0166] Unless otherwise defined, the technical or scientific terms used in this invention shall have the ordinary meaning understood by one of ordinary skill in the art to which this invention pertains. The terms "first," "second," and similar terms used in this invention do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, the terms "an" or "a" and similar terms do not indicate a quantity limitation, but rather indicate the presence of at least one. The terms "connected" or "linked" and similar terms are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up," "down," "left," "right," etc., are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship also changes accordingly.

[0167] The above are preferred embodiments 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 principle 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 method for updating a CAN database file for development, characterized in that, include: Obtain the new version of the CAN database file, the old version of the CAN database file, and the CAN database file for development; The new CAN database file and the old CAN database file are parsed to obtain the new object list dictionary database and the old object list dictionary database, respectively. The new object list dictionary database and the old object list dictionary database each include multiple objects. The attribute parameters corresponding to each object in the new version object list dictionary database and the old version object list dictionary database are concatenated to obtain the new version object list string and the old version object list string respectively; The new version of the object list string and the old version of the object list string are compared based on preset comparison rules to obtain the object update log; The CAN database file for development is updated based on the object update log.

2. The method for updating a CAN database file for development according to claim 1, characterized in that, The new CAN database file and the old CAN database file are parsed to obtain the new object list dictionary database and the old object list dictionary database, respectively, including: Text parsing is performed on the new version of the CAN database file and the old version of the CAN database file respectively to construct a global object database. The global object database includes the new version attribute set corresponding to each object in the new version of the CAN database file and the old version attribute set corresponding to each object in the old version of the CAN database file. Based on preset attribute fields, the new attribute set is traversed to determine the new definition line corresponding to each object in the new CAN database file, and the old attribute set is traversed to determine the old definition line corresponding to each object in the old CAN database file. Based on the new version definition line, obtain the new version attribute parameters corresponding to each object in the new version attribute set, and based on the old version definition line, obtain the old version attribute parameters corresponding to each object in the old version attribute set; Based on a preset data structure, the new version attribute parameters are constructed into a new version object list dictionary database, and the old version attribute parameters are constructed into an old version object list dictionary database.

3. The method for updating a CAN database file for development according to claim 2, characterized in that, For each object in the new version of the object list dictionary database and the old version of the object list dictionary database, the attribute parameters are concatenated to obtain the new version object list string and the old version object list string, respectively, including: Traverse the dictionary database of the new object list and concatenate the new attribute parameters corresponding to each object into a new object list string; Iterate through the dictionary database of the old version object list, and concatenate the old version attribute parameters corresponding to each object to form the old version object list string.

4. The method for updating a CAN database file for development according to claim 3, characterized in that, The new version of the object list string and the old version of the object list string are compared based on preset comparison rules to obtain the object update log, including: Obtain the new version unique identifier from each of the new version object list strings, and the old version unique identifier from each of the old version object list strings; Based on the new version unique identifier and the old version unique identifier, the preset comparison rules are used to compare each new version object list string and each old version object list string to determine the objects to be added and the objects to be deleted; The object update log is constructed based on the new attribute parameters corresponding to the object to be added and the old attribute parameters corresponding to the object to be deleted.

5. The method for updating a CAN database file for development according to claim 4, characterized in that, The preset comparison rules include: If the new version unique identifier is the same as the old version unique identifier, compare the new version object list string corresponding to the new version unique identifier with the old version object list string corresponding to the old version unique identifier; If any character in the new object list string is inconsistent with the old object list string, the object corresponding to the old object list string is determined as the object to be deleted, and the object in the new object list string is determined as the object to be added.

6. The method for updating a CAN database file for development according to claim 4, characterized in that, The preset comparison rules also include: If the new version unique identifier is inconsistent with the old version unique identifier of each old version object list string, the object corresponding to the new version unique identifier in the new version object list string is determined as the object to be added; If the old version unique identifier is inconsistent with the new version unique identifier of each of the new version object list strings, the object corresponding to the old version unique identifier in the old version object list string is determined as the object to be deleted.

7. The method for updating a CAN database file for development according to claim 4, characterized in that, Obtain the CAN database file for development, and update the CAN database file for development based on the object update log, including: The CAN database file used for development is parsed to construct a development list database; Based on the object update log, obtain the object dictionary database for the object to be deleted and the object dictionary database for the object to be added; Based on the dictionary database of objects to be deleted, delete the old version attribute parameters corresponding to the objects to be deleted from the development list database; Based on the dictionary database of objects to be added, the new attribute parameters corresponding to the objects to be added are added to the development list database; The development list database is written into the development CAN database file to complete the update of the development CAN database file.

8. The method for updating a CAN database file for development according to claim 7, characterized in that, Based on the dictionary database of objects to be deleted, the old version attribute parameters corresponding to the objects to be deleted are deleted from the development list database, including: Based on the dictionary database of objects to be deleted, determine the old version unique identifier and the old version attribute parameters corresponding to each object to be deleted; Based on the unique identifier of the old version and the attribute parameters of the old version corresponding to the object to be deleted, obtain the features to be matched and deleted; Based on the features to be matched and deleted, the development list database is traversed, and the old version attribute parameters that match the features to be matched and deleted in the development list database are deleted.

9. The method for updating a CAN database file for development according to claim 7, characterized in that, The objects to be added include message objects to be added; the dictionary database of objects to be added includes a message database to be added; the message database to be added includes new message attribute parameters corresponding to the message objects to be added; and Based on the dictionary database of objects to be added, the new attribute parameters corresponding to the objects to be added are added to the development list database, and the process also includes: Traverse the development list database to determine the first insertion position for inserting the new message attribute parameters corresponding to the new message object to be added; Based on the database of messages to be added, the new message attribute parameters corresponding to the message object to be added are inserted at the first insertion position.

10. The method for updating a CAN database file for development according to claim 7, characterized in that, The objects to be added also include signal objects to be added, the dictionary database of objects to be added includes a database of signals to be added, and the database of signals to be added includes a dictionary of new signal attribute parameters corresponding to the signal objects to be added; as well as Based on the dictionary database of objects to be added, the new attribute parameters corresponding to the objects to be added are added to the development list database, and the process also includes: If the object to be added is the signal object to be added, the new CAN database file is parsed to construct the original configuration list database. Based on the new version of the signal attribute parameter dictionary, the original configuration list database is traversed to obtain the original configuration list database to be added, which includes the attribute configuration information to be added corresponding to the new version of the signal attribute parameters. Traverse the development list database to determine the second insertion position for inserting the attribute configuration information corresponding to the signal object to be added; Based on the original configuration list database to be added, the attribute configuration information to be added corresponding to the signal object to be added is inserted at the second insertion position.

11. The method for updating a CAN database file for development according to claim 1, characterized in that, Also includes: Before concatenating the attribute parameters of each object in the new version of the object list dictionary database and the old version of the object list dictionary database, a preset whitelist is obtained. The preset whitelist includes the identifiers of the objects that do not need to be updated. Based on the preset whitelist, the objects corresponding to the identifier are filtered out from the new version of the object list dictionary database and the old version of the object list dictionary database.

12. An update device for a CAN database file for development, characterized in that, include: The acquisition module is used to acquire both the new and old versions of the CAN database file. The parsing module is used to parse the new version of the CAN database file and the old version of the CAN database file to obtain the new version of the object list dictionary database and the old version of the object list dictionary database, respectively, wherein the new version of the object list dictionary database and the old version of the object list dictionary database each include multiple objects; The string concatenation module is used to concatenate the attribute parameters corresponding to each object in the new version object list dictionary database and the old version object list dictionary database to obtain the new version object list string and the old version object list string respectively; The comparison module is used to compare the new version of the object list string and the old version of the object list string based on preset comparison rules to obtain the object update log; The update module is used to obtain the CAN database file for development and update the CAN database file for development based on the object update log.

13. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the method for updating a CAN database file for development as described in any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the method for updating a CAN database file for development as described in any one of claims 1-11.

Images