Vehicle model data management, device, electronic equipment and storage medium
By using tag comparison and feature value setting in vehicle model data management, vehicle model data from different export modes can be automatically merged, solving the problems of large data volume and high maintenance difficulty, and achieving efficient and accurate data management.
Patent Information
- Application Number
- CN202610969666.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-01
- Publication Date
- 2026-11-03
AI Technical Summary
In vehicle model data management, because model data under different export modes are stored in separate rooms, the amount of data to be managed is large, the data maintenance is difficult and inefficient.
By obtaining the first and second data sets based on N tags of vehicle model data, performing a comparison operation, merging identical entries into the third data set, and setting feature values for further merging under different results, automated data merging management is achieved.
This significantly improves the efficiency and accuracy of vehicle model data merging, and reduces the difficulty and cost of data maintenance.
Smart Images
Figure CN123030593A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the fields of data management and information technology, and more specifically, to a vehicle model data management device, electronic device, and storage medium. Background Technology
[0002] In the vehicle model data management system, model data is stored and managed using a hierarchical management strategy based on the vehicle's development platform and the specific model. According to the vehicle's export model, data for the same model is divided into at least two categories: complete vehicle export and kit export, with data for each export model stored separately. One model room stores all data for a single model under one export model. However, these different model rooms are independent and manually maintained separately, resulting in a large volume of data and difficulties in data maintenance. Summary of the Invention
[0003] In view of this, embodiments of this application propose a vehicle model data management device, electronic device, and storage medium, which can automatically merge vehicle model data stored in multiple vehicle model rooms in different modes into one vehicle model room for management, thereby reducing the amount of data to be managed and reducing the difficulty of data maintenance.
[0004] The following technical solution is adopted in this application.
[0005] In a first aspect, embodiments of this application provide a method for managing vehicle model data, the method comprising: Based on N tags of vehicle model data, a first data set and a second data set are obtained; the first data set includes vehicle model data of the target vehicle determined from the first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room; a first comparison operation is performed between the first entry in the first data set and the second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags; when the comparison result of the first comparison operation is the same, the first entry or the second entry is stored in the third data set.
[0006] In some embodiments, after storing the first entry or the second entry into the third data set, the process includes: When the first entry in the first data set is deleted, and the second entry in the second data set is deleted.
[0007] In some embodiments, after performing the first comparison operation between the first entry in the first data set and the second entry in the second data set, the following steps are included: When the comparison result of the first comparison operation is different, a first feature value is set under the target label of the first entry, and a second feature value is set under the target label of the second entry. Then, a second comparison operation is performed between the first sub-entry in the first data set and the second sub-entry in the second data set. The first sub-entry is the data of N-1 tags other than the target label in the first entry. The second sub-entry is the data of N-1 tags other than the target label in the second entry. When the comparison result of the second comparison operation is the same, the first sub-entry or the second sub-entry is stored in the third data set. The data under the target labels of the first entry and the second entry, as well as the first feature value and the second feature value, are all stored under the target label of the first sub-entry or the second sub-entry.
[0008] In some embodiments, after storing the first sub-entry or the second sub-entry into the third data set, the method further includes: When the comparison result of the second comparison operation is different, the first sub-entry is stored in the third data set, and the data under the target label of the first entry and the first feature value are stored under the target label of the first sub-entry; and the second sub-entry is stored in the third data set, and the data under the target label of the second entry and the second feature value are stored under the target label of the second sub-entry.
[0009] In some embodiments, the method for obtaining a first data set and a second data set based on N tags of vehicle model data includes: The system retrieves vehicle data of the target vehicle from the first vehicle model room and the second vehicle model room; it then categorizes and stores the vehicle data in the first vehicle model room according to multiple tags to obtain the first data set; similarly, it categorizes and stores the vehicle data in the second vehicle model room according to the multiple tags to obtain the second data set; the multiple tags include the N tags, and the multiple tags include one or more combinations of the following: part number, part name, quantity, part group, part function name, configuration usage, and part type.
[0010] In some embodiments, the N tags include part number, quantity, part grouping, part function name and configuration usage from the plurality of tags; and / or, the target tag includes the configuration usage.
[0011] Secondly, embodiments of this application provide a management device, the device comprising: The acquisition module acquires a first data set and a second data set based on N tags of vehicle model data; the first data set includes vehicle model data of the target vehicle determined from a first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from a second vehicle model room; the comparison module performs a first comparison operation between a first entry in the first data set and a second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags; the merging module stores the first entry or the second entry into a third data set when the comparison result of the first comparison operation is the same.
[0012] Thirdly, embodiments of this application provide an electronic device, which includes: a processor; and a memory storing computer-readable instructions. When the computer-readable instructions are executed by the processor, the management of the vehicle model data as described above is realized.
[0013] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-readable instructions thereon, which, when executed by a processor or electronic device, enables the management of the vehicle model data as described above.
[0014] Fifthly, embodiments of this application provide a computer program product, the computer program product including computer instructions, the computer instructions being stored in a computer-readable storage medium; the computer instructions being read and executed by a processor of a computer device to achieve the management of the vehicle model data as described above.
[0015] In this application's solution, vehicle model data of the target vehicle is obtained from the first vehicle model room and classified and stored in the first data set according to N tags. Vehicle model data of the same target vehicle is obtained from the second vehicle model room and classified and stored in the second data set according to N tags. By comparing the data under N tags in the first and second data sets, entries with the same comparison results are automatically merged and stored in the third data set. Compared with the manual operation of analyzing, comparing and merging vehicle model data one by one, this solution realizes the automatic merging of vehicle model data from multiple vehicle model rooms into the same vehicle model room for management, which greatly improves the efficiency and accuracy of vehicle model data merging and reduces the difficulty of maintaining vehicle model data.
[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description
[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0018] Figure 1 This is a schematic diagram of a vehicle model data management system provided in an embodiment of this application.
[0019] Figure 2 This is a schematic diagram illustrating a process for managing vehicle model data, provided as an embodiment of this application.
[0020] Figure 3 This is a schematic diagram illustrating another process for managing vehicle model data, provided as an embodiment of this application.
[0021] Figure 4 This is a flowchart illustrating a method for obtaining vehicle model data provided in an embodiment of this application.
[0022] Figure 5 This is a schematic diagram of a first table based on whole vehicle room data provided in an embodiment of this application.
[0023] Figure 6 A schematic diagram of a second table based on KD room data provided in an embodiment of this application.
[0024] Figure 7 This is a schematic diagram of the first data merging provided in an embodiment of this application.
[0025] Figure 8 This is a schematic diagram of the first table after the first comparison provided in the embodiments of this application.
[0026] Figure 9 This is a schematic diagram of the second table after the first comparison provided in an embodiment of this application.
[0027] Figure 10 This is a schematic diagram of the second data merging provided in an embodiment of this application.
[0028] Figure 11 This is a schematic diagram of the third table after data merging, provided in an embodiment of this application.
[0029] Figure 12 This is a schematic diagram of data storage before and after merging, provided as an embodiment of this application.
[0030] Figure 13 This is a schematic diagram of the structure of a management device provided in an embodiment of this application.
[0031] Figure 14This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0032] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through specific embodiments. Detailed Implementation
[0033] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0034] In related technologies, the same vehicle model is typically divided into a complete vehicle room and a kit (knock-down kit) room for data management based on different export formats. To reduce data redundancy and avoid missing maintenance issues for engineered parts, data from multiple vehicle room rooms under the same vehicle model is integrated and managed uniformly. However, there are numerous vehicle room rooms, with approximately 5,000 rows of data per vehicle room, and a total of 300,000 rows of data for all vehicle categories, including both common and specialized parts. Manually comparing, analyzing, and merging data line by line is extremely difficult, labor-intensive, and results in low data processing efficiency and accuracy.
[0035] The vehicle data management provided in this application aims to solve the above-mentioned technical problems in the prior art.
[0036] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.
[0037] Figure 1 This is a schematic diagram of a vehicle parts data management system provided in an embodiment of this application. Figure 1 As shown, the vehicle parts data management system 100 provided in this application embodiment includes a data acquisition module 110 and a data merging module 120. The data merging module includes a data comparison module 121 and a data storage module 122.
[0038] In one optional implementation, the data acquisition module 110 and the data merging module 120 refer to software units or modules. Specifically, the data acquisition module 110 acquires vehicle model data from different data sources and stores it in different tables, while the data merging module 120 compares and / or processes the vehicle model data from different tables, then merges and stores it in a new table.
[0039] In another alternative implementation, the data acquisition module 110 and the data merging module 120 refer to hardware devices; these may include, but are not limited to, electronic devices with data processing capabilities such as computers, host machines, servers, or data centers.
[0040] The following is combined Figure 1 The vehicle parts data management system 100 shown is an example of the vehicle model data management provided in this application embodiment: the data acquisition module 110 acquires data from the first vehicle model room, classifies it according to N tags and stores it in the first table, and acquires data from the second vehicle model room, classifies it according to N tags and stores it in the second table; the first table and the second table are sent to the data merging module 120.
[0041] In addition, the data merging module 120 receives the first table and the second table, and its data comparison module 121 compares the first entry (data corresponding to N labels) in the first table with the second entry (data corresponding to N labels) in the second table; wherein, when the comparison results are the same, the data storage module 122 stores the first entry or the second entry into the third table, and deletes the first entry and the second entry from the first table and the second table respectively.
[0042] When the comparison results are different, the data comparison module 121 compares the first sub-entry (the data of N-1 tags other than configuration usage in the first entry) with the second sub-entry (the data of N-1 tags other than configuration usage in the second entry). When the comparison results are the same, the data storage module 122 sets a feature value under the configuration usage tag and stores the first or second sub-entry, the data under the configuration usage tag, and the feature value into one entry of the third table. When the comparison results are different, the data storage module 122 sets a feature value under the configuration usage tag and stores the first entry and feature value, and the second entry and feature value into two entries of the third table, respectively.
[0043] Below Figure 1 Based on the vehicle parts data management system 100 shown, the management of vehicle model data provided in the embodiments of this application will be further explained, such as... Figure 2The diagram illustrates a process for managing vehicle model data. In a specific embodiment, this vehicle model data management can be applied to, for example... Figure 13 The management device 600 and the electronic device 700 configured with the management device 600 are shown. Figure 14 The specific process of the embodiments of this application will be described below. Of course, it is understood that this method can be executed by a cloud server with computing power. The following will focus on... Figure 2 The process shown is explained in detail. The management of vehicle model data may include the following steps 210 to 230.
[0044] Step 210: Based on the N tags of the vehicle model data, obtain a first data set and a second data set; the first data set includes vehicle model data of the target vehicle determined from the first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room.
[0045] In one example, a data set integrating configuration rules and constraint information, using vehicle type, engine type, and chassis type as basic units, is typically defined as a "vehicle type room," serving as the fundamental organizational unit for unified access to and maintenance of vehicle type data. The vehicle type room acts as the data source for vehicle type data, and by defining a first vehicle type room and a second vehicle type room, vehicle type data obtained from different data sources can be represented.
[0046] In this embodiment of the application, the first data set includes vehicle model data of target vehicle models determined from the first vehicle model room, and the vehicle model data is stored in the form of a first table categorized by tags, such as... Figure 7 The model room shown is a table for the entire vehicle.
[0047] In this embodiment of the application, the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room, and stores the vehicle model data in the form of a second table according to the classification of tags, such as... Figure 7 The model room shown is a table for KD.
[0048] In one optional implementation, tags are used to distinguish attributes of vehicle model data for categorized storage. The N tags include part number, quantity, part grouping, part function name, and configuration usage from the plurality of tags.
[0049] In addition to the aforementioned N labels, the first and second tables also include labels such as FND (Chinese), Engineer, Part Type, Combination, and Value.
[0050] For example, such as Figure 5 As shown, the first vehicle model room can be represented as a vehicle model room stored in the form of data from the complete vehicle export; such as Figure 6As shown, the second vehicle model room can be represented as a vehicle model room stored in the form of KD (knock-down) export data. That is, the exporter disassembles the whole vehicle and exports it as a semi-finished product or parts, and then the importer completes the vehicle manufacturing by assembling it itself.
[0051] Optionally, KD includes CKD and SKD. CKD (Complete Knocked Down) refers to the complete disassembly of a vehicle into parts for export. It means that the vehicle is imported or introduced in a completely disassembled state, and then all the parts are assembled into a complete vehicle. SKD (Semi Knocked Down) refers to the export of semi-finished vehicle assemblies, which are only simply assembled. It means that vehicle assemblies such as engines, cabs, and chassis are imported from abroad and then assembled into a complete vehicle in China.
[0052] For example, the labels include, but are not limited to, part number, GPC (General Part Classification), FND (Function Name Description), usage, and configuration usage. Among them, the part number serves as a unique code for the component, used to distinguish and identify various types of parts; GPC is used to classify and manage components, such as chassis system, engine system, braking system, etc.; FND is used to quickly locate the corresponding component data and obtain the naming and functional description of the component's application in the whole vehicle, such as right front brake caliper assembly, left front brake caliper assembly; usage refers to the number of the component assembled in the corresponding configuration of a single vehicle; configuration usage is used to record the vehicle configuration, usage rules, and application scenarios to which the component is adapted.
[0053] Furthermore, such as Figure 5 As shown, the data in the vehicle assembly room is categorized using five tag attributes: part number, GPC, FND, quantity, and configuration usage. The data pointed to by these five tags are then combined into a new set of data using the "&" connector and stored in the system. Figure 5 Under the "Combinations" tag, and recorded as Key1, Key2...KeyM ( Figure 5 The "value" label in the table is stored in the first table.
[0054] Furthermore, such as Figure 6 As shown, the data in the KD room is categorized using five tag attributes: part number, GPC, FND, quantity, and configuration usage. The data pointed to by these five tags is then combined into a new set of data using the "&" connector and stored in the KD room. Figure 6 Under the "Combination" tag, and recorded as KD-Key1, KD-Key2...KD-KeyN ( Figure 6The "value" label in the table is stored in the second table.
[0055] Step 220: Perform a first comparison operation between the first entry in the first data set and the second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags.
[0056] In this embodiment of the application, the first entry is used to indicate the data corresponding to the five tag attributes of part number, GPC, FND, quantity, and configuration usage in the first table; the second entry is used to indicate the data corresponding to the five tag attributes of part number, GPC, FND, quantity, and configuration usage in the second table.
[0057] For example, in order to perform the comparison task more efficiently, based on the combination of the data pointed to by the 5 tags into a new data according to the connector, the comparison result is obtained by comparing the Key value data in the first table and the second table, that is, by comparing the data under the "combination" tag.
[0058] Specifically, if the data under the "Combination" tag is found to be completely identical, the comparison results of the first comparison operation are determined to be the same; otherwise, the comparison results of the first comparison operation are determined to be different.
[0059] Step 230: When the comparison results of the first comparison operation are the same, the first entry or the second entry is stored in the third data set.
[0060] In one example, when the comparison results of the first comparison operation are the same, the first and second entries are directly merged and stored in a new model room, i.e., the third data set.
[0061] The third dataset stores vehicle model data in a third table format, categorized by tags, such as... Figure 7 The car model rooms shown are from the merged table.
[0062] For example, such as Figure 7 As shown, based on the part number 112000177AA, by comparing the data under the combination label of this part in the first table and the second table, it can be determined that the data under the combination label in the first table is 112000177AA1112A01VFR39, and the data under the combination label in the second table is also 112000177AA1112A01VFR39. They are identified as completely identical data, and the data corresponding to this part is placed in the new vehicle model room, that is, the merged third table.
[0063] In particular, after step 230, after storing the first entry or the second entry into the third data set, how to process the first entry in the first data set and the second entry in the second data set, this application embodiment also provides an optional implementation method, which may specifically include the following step 231.
[0064] Step 231: Delete the first entry in the first data set and delete the second entry in the second data set.
[0065] For example, when the first data set and the second data set store data in the form of a first table and a second table, after storing the same entry in the third data set, the entry is deleted from the first data set and the second data set to facilitate subsequent data merging.
[0066] For example, such as Figure 8 and Figure 9 As shown, delete the single row of data containing part number 112000177AA in the first and second tables.
[0067] Please refer to step 220, where after performing the first comparison operation between the first entry in the first data set and the second entry in the second data set, how to merge entries with different comparison results, such as... Figure 3 The diagram shows another data merging process. This application embodiment also provides an optional implementation method, which may include the following steps 221 to 222.
[0068] Step 221: When the comparison result of the first comparison operation is different, a first feature value is set under the target label of the first entry and a second feature value is set under the target label of the second entry. Then, a second comparison operation is performed between the first sub-entry in the first data set and the second sub-entry in the second data set. The first sub-entry is the data of N-1 tags other than the target label in the first entry. The second sub-entry is the data of N-1 tags other than the target label in the second entry.
[0069] In the embodiments of this application, the feature values are used to indicate the special features of components in different vehicle model compartments. For example, the whole vehicle compartment includes the features CHN (domestic sales) and CBU (Completely Built Unit, complete vehicle export sales) for whole vehicle-specific parts, and the KD compartment includes the features CKD (Completely Knocked Down, fully knocked-down assembly) and SKD (Semi-Knocked Down, semi-knocked-down assembly) for KD-specific parts.
[0070] The feature value includes at least a first feature value and a second feature value. The first feature value is the feature value of the whole vehicle-specific part, such as CHN|CBU; the second feature value is the feature value of the KD-specific part, such as CKD|SKD.
[0071] For example, according to Figure 8 The data in the first table shown and Figure 9 The data in the second table shown are different, as... Figure 10 As shown, based on the data corresponding to a certain component in the first table, if there is no component with completely identical data in the second table, the component is determined to be a vehicle-specific part. For example, for the component with part number 112000142AA in the first table, the characteristic value (CHN|CBU) of the vehicle-specific part is added to the data unit corresponding to the configuration usage.
[0072] For further information, please refer to [link / reference]. Figure 10 Based on the data corresponding to a certain component in the second table, if there is no component with completely identical data in the first table, the component is determined to be a KD dedicated part. For example, for the component with part number 112000143AA in the second table, the feature value (CKD|SKD) of the KD dedicated part is added to the data unit corresponding to the configuration usage.
[0073] In this embodiment, the first sub-entry indicates the data corresponding to any four of the five tag attributes (part number, GPC, FND, quantity, and configuration usage) in the first table; the second sub-entry indicates the data corresponding to any four of the five tag attributes (part number, GPC, FND, quantity, and configuration usage) in the second table. For example, the first or second sub-entry may be the data corresponding to the part number, GPC, FND, and quantity.
[0074] In one example, when the first alignment operation results in a difference, such as... Figure 8 In the vehicle room shown, based on deleting the entries that have been identified as the same in step 230, the four tag attributes of part number, GPC, FND, and quantity are recombined to form a new data unit, which is recorded as Key1, Key2...KeyM and stored again in the first table.
[0075] Similarly, the first comparison operation showed that they were different, such as... Figure 9 In the KD room shown, based on deleting the entries that have been identified as the same in step 230, similarly, the four tag attributes of part number, GPC, FND, and quantity are recombined to form a new data unit, which is recorded as KD-Key1, KD-Key2...KD-KeyN, and then stored in the second table.
[0076] Optionally, the above-mentioned re-storage to the first table (vehicle room) or the second table (KD room) can be performed in the original table or in a new table, without any limitation.
[0077] Furthermore, based on the re-storage of the first and second tables, the data under the "Combination" label is compared again to obtain the comparison result of the second comparison operation. When the data under the "Combination" label is found to be completely identical, the comparison result of the second comparison operation is determined to be identical; otherwise, the comparison result of the second comparison operation is determined to be different.
[0078] Step 222: When the comparison result of the second comparison operation is the same, the first sub-entry or the second sub-entry is stored in the third data set, and the data under the target label of the first entry and the second entry, as well as the first feature value and the second feature value, are all stored under the target label of the first sub-entry or the second sub-entry.
[0079] For example, according to Figure 8 The data in the first table shown and Figure 9 The data in the second table shown are compared and found to be the same. The configuration usage of the corresponding data is found in the first table (vehicle room) and the second table (KD room) by using the Key value and KD-Key value of the data. Then, the feature value of the vehicle-specific part (CHN|CBU) is added to the data suffix under the configuration usage in the vehicle room, and the feature value of the KD-specific part (CKD|SKD) is added to the data suffix under the configuration usage in the KD room. The two sets of data are then combined into one set of data and stored in the new vehicle room (merged vehicle room).
[0080] For example, such as Figure 8 The component with part number 401001086AA in the first table shown is... Figure 9 The comparison results for part number 401001086AA in the second table shown are the same. Using Key2, the configuration usage of part 401001086AA is found, and the suffix FR39 is added to the data under this configuration usage (CHN|CBU). Similarly, using KD-Key2, the configuration usage of part 401001086AA is found, and the suffix FR42 is added to the data under this configuration usage (CKD|SKD). Using the logical operators "&" and "|", the two sets of data are combined into one set of data and stored in a new vehicle model room, as shown below. Figure 11 As shown.
[0081] Among them, feature values and data, or feature values themselves, can be combined using the logical operators "&" and "|", or can be represented by other forms, without any restrictions here.
[0082] Alternatively, the method of integrating data from the vehicle assembly room and the KD room can also be extended to merging data from two or more workshop rooms on the same platform.
[0083] In particular, after step 222, after storing the first sub-entry or the second sub-entry into the third data set, how to process the first sub-entry in the first data set and the second sub-entry in the second data set is also provided in this embodiment of the application as an optional implementation method, which may specifically include the following steps.
[0084] Step 223: Delete the first sub-entry in the first data set and delete the second sub-entry in the second data set.
[0085] For example, such as Figure 8 , Figure 9 As shown, delete the single row of data containing the component with part number 401001086AA in the first and second tables.
[0086] Step 224: When the comparison result of the second comparison operation is different, the first sub-entry is stored in the third data set, and the data under the target label of the first entry and the first feature value are stored under the target label of the first sub-entry; and the second sub-entry is stored in the third data set, and the data under the target label of the second entry and the second feature value are stored under the target label of the second sub-entry.
[0087] In this embodiment of the application, the third table represents the merged vehicle model room.
[0088] For example, for the component with part number 112000142AA in the first table, the feature value (CHN|CBU) is added to the data suffix corresponding to the configuration usage using the logical operator "&", such as... Figure 10 The FR02&(CHN|CBU) shown is used to store all data corresponding to this component in the new vehicle room (the merged vehicle room).
[0089] For example, for the part number 112000143AA in the second table, the feature value (CKD|SKD) is added to the data suffix corresponding to the configuration usage using the logical operator "&", such as... Figure 10 The FR02&(CKD|SKD) shown is used, and all data corresponding to this part is stored in the new model room (the merged model room).
[0090] In this embodiment, data is obtained from the first vehicle model room and classified and stored in the first data set according to N tags. Data is also obtained from the second vehicle model room and classified and stored in the second data set according to N tags. The first and second entries containing N tags are compared to obtain the comparison results. Entries with the same comparison results are automatically merged and stored in the third data set. Entries with different comparison results are added with feature values and then stored in the third data set using different merging measures. The first and second sub-entries containing N-1 tags are then compared to obtain the comparison results. The same merging measures as the first comparison are used. This achieves automatic merging of data from multiple vehicle model rooms into one vehicle model room for management, significantly reducing the cost of subsequent vehicle model data management, reducing manual workload and difficulty, and improving data accuracy and efficiency.
[0091] Based on the above, this application provides an optional implementation method for obtaining the first data set and the second data set, such as... Figure 4 The flowchart shown is a method for obtaining vehicle model data, which may specifically include the following steps 310 to 360.
[0092] Step 310: Obtain the target vehicle model data from the first vehicle model room and the second vehicle model room.
[0093] In this embodiment, the first vehicle model room is a complete vehicle room, and the second vehicle model room is a KD (knock-down) room; the first data is data stored for the target vehicle model in the form of a complete vehicle export, such as... Figure 12 The data shown is from the whole vehicle room. The second data is the data stored for the target vehicle model in the form of bulk export, such as... Figure 12 The data shown is from the KD room.
[0094] Step 320: Classify and store the vehicle data in the first vehicle room according to multiple labels to obtain the first data set.
[0095] For example, in conjunction with the steps shown in step 210 Figure 5 and Figure 6 The first dataset is a first table built on the N labels of the first car model room. The first table is further enhanced with two labels, “combination” and “key value”, to facilitate data comparison between the two tables later.
[0096] Optionally, the data corresponding to part number, quantity, part group, part function name, and configuration usage can be combined into a new cell to further facilitate the comparison between the two tables.
[0097] Step 330: Classify and store the vehicle data in the second vehicle room according to the multiple tags to obtain the second data set; the multiple tags include the N tags, and the multiple tags include one or more combinations of the following: part number, part name, quantity, part group, part function name, configuration usage, and part type.
[0098] For example, in conjunction with the steps shown in step 210 Figure 5 and Figure 6 The second dataset is a second table built upon the N labels in the second vehicle model room, with additional "Combination" and "Key Value" labels added to the second table. The N labels include part number, quantity, part grouping, part function name, and configuration usage determined from multiple labels.
[0099] Step 340: Based on the N tags of the vehicle model data, obtain a first data set and a second data set; the first data set includes vehicle model data of the target vehicle determined from the first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room.
[0100] Step 350: Perform a first comparison operation between the first entry in the first data set and the second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags.
[0101] Step 360: When the comparison results of the first comparison operation are the same, the first entry or the second entry is stored in the third data set.
[0102] The specific steps of steps 340 to 360 can be found in steps 210 to 230, and will not be repeated here.
[0103] In this embodiment of the application, by combining the five tags of part number, GPC, FND, quantity, and configuration usage with logical connectors to form a new data unit and recording the corresponding key value, the efficiency of horizontal comparison between the two tables and data storage in the new table is greatly improved.
[0104] To achieve the functions described in the above embodiments, the management of vehicle model data includes hardware structures and / or software modules that execute each function. Those skilled in the art should readily recognize that, based on the units and method steps of the examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed through hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.
[0105] exist Figures 2 to 12 Based on the management of vehicle model data shown, the embodiments of this application further provide a management device, such as... Figure 13 The diagram shows the structure of the management device 600, which includes: an acquisition module 610, a comparison module 620, and a merging module 630.
[0106] The acquisition module 610 is used to acquire a first data set and a second data set based on N tags of vehicle model data; the first data set includes vehicle model data of a target vehicle determined from a first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from a second vehicle model room; wherein, the acquisition module 610 may include, for example, Figure 1 The data acquisition module 110 shown.
[0107] The comparison module 620 is used to perform a first comparison operation between a first entry in the first data set and a second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags; the merging module is used to store the first entry or the second entry into a third data set when the comparison result of the first comparison operation is the same; wherein, the comparison module 620 may include, for example, Figure 1 The data merging module 120 shown.
[0108] The merging module 630 is configured to store either the first entry or the second entry into a third data set when the comparison results of the first comparison operation are the same; wherein, the merging module 630 may include, for example, Figure 1 The data merging module 120 shown.
[0109] In some embodiments, the acquisition module 610 includes: a data acquisition module, configured to acquire vehicle data of a target vehicle from the first vehicle model room and the second vehicle model room; a first data storage module, configured to classify and store the vehicle data in the first vehicle model room according to multiple tags to obtain the first data set; and a second data storage module, configured to classify and store the vehicle data in the second vehicle model room according to the multiple tags to obtain the second data set; wherein the multiple tags include the N tags, and the multiple tags include one or more combinations of the following: part number, part name, quantity, part group, part function name, configuration usage, and part type.
[0110] In some embodiments, the acquisition module 610 further includes: for the N tags to include part number, quantity, part grouping, part function name and configuration usage from the plurality of tags; and / or, the target tag includes the configuration usage.
[0111] In some embodiments, the merging module 630 includes: deleting the first entry in the first data set and deleting the second entry in the second data set.
[0112] In some embodiments, the merging module 630 further includes: deleting the first sub-entry in the first data set and deleting the second sub-entry in the second data set.
[0113] In other embodiments, the comparison module 620 includes: when the comparison result of the first comparison operation is different, setting a first feature value under the target label of the first entry and setting a second feature value under the target label of the second entry, and performing a second comparison operation on the first sub-entry in the first data set and the second sub-entry in the second data set; the first sub-entry is the data of N-1 tags in the first entry excluding the target label; the second sub-entry is the data of N-1 tags in the second entry excluding the target label; when the comparison result of the second comparison operation is the same, storing the first sub-entry or the second sub-entry in the third data set, and storing the data under the target labels of the first entry and the second entry, as well as the first feature value and the second feature value, under the target labels of the first sub-entry or the second sub-entry.
[0114] In some embodiments, the comparison module 620 further includes: storing the first sub-entry into a third data set when the comparison result of the second comparison operation is different, and storing the data under the target label of the first entry and the first feature value under the target label of the first sub-entry; and storing the second sub-entry into the third data set, and storing the data under the target label of the second entry and the second feature value under the target label of the second sub-entry.
[0115] According to one aspect of the embodiments of this application, Figure 14 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 14 As shown, the electronic device 700 includes a processor 710 and one or more memories 720. The one or more memories 720 are used to store program instructions executed by the processor 710. When the processor 710 executes the program instructions, it manages the vehicle model data as described above.
[0116] Furthermore, the processor 710 may include one or more processing cores. The processor 710 runs or executes instructions, programs, code sets, or instruction sets stored in the memory 720, and retrieves data stored in the memory 720. Optionally, the processor 710 may be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 710 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor and may be implemented using a separate communication chip.
[0117] According to one aspect of this application, a computer-readable storage medium is also provided, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer-readable storage medium carries computer-readable instructions that, when executed by a processor, implement the methods in any of the above embodiments.
[0118] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. Computer-readable storage media can be, for example, but not limited to: electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such transmitted data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.
[0119] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.
[0120] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.
[0121] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein.
[0122] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A method for managing vehicle model data, characterized in that, include: Based on N tags of vehicle model data, obtain the first data set and the second data set; The first data set includes vehicle model data of the target vehicle determined from the first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room; Perform a first comparison operation between the first entry in the first data set and the second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags; If the comparison results of the first comparison operation are the same, then the first entry or the second entry is stored in the third data set.
2. The method according to claim 1, characterized in that, After storing the first entry or the second entry into the third data set, the method further includes: Delete the first entry from the first data set and delete the second entry from the second data set.
3. The method according to claim 1, characterized in that, After performing the first comparison operation between the first entry in the first data set and the second entry in the second data set, the method further includes: When the comparison results of the first comparison operation are different, a first feature value is set under the target label of the first entry, a second feature value is set under the target label of the second entry, and a second comparison operation is performed between the first sub-entry in the first data set and the second sub-entry in the second data set; the first sub-entry is the data of N-1 tags other than the target label in the first entry; the second sub-entry is the data of N-1 tags other than the target label in the second entry; When the comparison results of the second comparison operation are the same, the first sub-entry or the second sub-entry is stored in the third data set, and the data under the target label of the first entry and the second entry, as well as the first feature value and the second feature value, are all stored under the target label of the first sub-entry or the second sub-entry.
4. The method according to claim 3, characterized in that, After storing the first sub-entry or the second sub-entry into the third data set, the method further includes: Delete the first sub-entry in the first data set and delete the second sub-entry in the second data set.
5. The method according to claim 3, characterized in that, After performing a second comparison operation between the first sub-entry in the first data set and the second sub-entry in the second data set, the method further includes: When the comparison result of the second comparison operation is different, the first sub-entry is stored in the third data set, and the data under the target label of the first entry and the first feature value are stored under the target label of the first sub-entry; and the second sub-entry is stored in the third data set, and the data under the target label of the second entry and the second feature value are stored under the target label of the second sub-entry.
6. The method according to any one of claims 1-5, characterized in that, The method for obtaining a first data set and a second data set based on N tags of vehicle model data includes: Obtain the target vehicle model data from the first vehicle model room and the target vehicle model data from the second vehicle model room; The vehicle data in the first vehicle model room is classified and stored according to multiple labels to obtain the first data set; The vehicle data in the second vehicle room is classified and stored according to the multiple tags to obtain the second data set; the multiple tags include the N tags, and the multiple tags include one or more combinations of the following: part number, part name, quantity, part group, part function name, configuration usage, and part type.
7. The method according to claim 6, characterized in that, The N tags include part number, quantity, part group, part function name and configuration usage from the plurality of tags; and / or, the target tag includes the configuration usage.
8. A management device, characterized in that, include: The acquisition module is used to acquire a first data set and a second data set based on N tags of vehicle model data; the first data set includes vehicle model data of the target vehicle determined from the first vehicle model room, and the second data set includes vehicle model data of the target vehicle determined from the second vehicle model room; The comparison module is used to perform a first comparison operation between the first entry in the first data set and the second entry in the second data set; the first entry or the second entry includes vehicle model data corresponding to the N tags; the merging module is used to store the first entry or the second entry into the third data set when the comparison result of the first comparison operation is the same.
9. An electronic device, characterized in that, The electronic device includes: processor; A memory storing computer-readable instructions that, when executed by the processor, implement the method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium contains program code that can be invoked by a processor or electronic device to execute the method as described in any one of claims 1 to 7.