A vehicle model and parts adaptation data maintenance system

Abstract

The application provides a vehicle model and accessory adaptation data maintenance system, comprising: an adaptation center station, used for storing vehicle model data and first adaptation data of a general group and vehicle model data and second adaptation data of OE coding; a store client, used for obtaining a data update request submitted by a store user, a to-be-updated store automobile accessory and OE coding of the to-be-updated store automobile accessory, and determining third adaptation data of the to-be-updated store automobile accessory and the general group according to the OE coding of the to-be-updated store automobile accessory; and a data calculation platform, used for updating, in response to the data update request, adaptation data of vehicle model data and store automobile accessories in a store database for the store user according to the first adaptation data, the second adaptation data and the third adaptation data. The system can flexibly update adaptation data of vehicle models and store automobile accessories for different automobile repair stores according to the needs of the automobile repair stores.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to a vehicle model and parts adaptation data maintenance system. Background Technology

[0002] In the automotive aftermarket, vehicle repair shops need to consult vehicle repair manuals to determine which parts are compatible with different car models when replacing parts. They then recommend parts to customers based on their inventory, a time-consuming and labor-intensive process. Furthermore, when registering their inventory, repair shops often enter parts names that are not the standard names, making it difficult to accurately match compatible parts to specific car models. These factors negatively impact the efficiency of vehicle repair shops. Summary of the Invention

[0003] One or more embodiments of this application describe a vehicle model and parts adaptation data maintenance system that can at least partially overcome the above-mentioned technical problems.

[0004] One or more embodiments of this application provide a vehicle model and parts adaptation data maintenance system, including:

[0005] The adaptation platform is used to store the first adaptation data of vehicle model data and general groups, and the second adaptation data of vehicle model data and OE codes. In the first adaptation data, each general group adapts to a set of vehicle models. The general group is used to record the same type of automotive parts data but different brands that are applicable to the corresponding set of vehicle models, including: general group code, OE code, brand and parts category.

[0006] The store client is used to obtain data update requests submitted by store users, the auto parts to be updated in the store, and the OE code of the auto parts to be updated in the store, and to determine the third adaptation data of the auto parts to be updated in the store and the general group based on the OE code of the auto parts to be updated in the store.

[0007] The data computing platform is used to respond to the data update request submitted by the store client from the store user, and update the vehicle model data and the matching data of the store's auto parts in the store database for the store user according to the first adaptation data, the second adaptation data and the third adaptation data.

[0008] As an optional implementation of the system, the data computing platform is specifically used for:

[0009] Based on the third adaptation data, determine the universal group code corresponding to the auto parts of the store to be updated;

[0010] Based on the general group code, the target general group and the set of target vehicle models corresponding to the target general group are searched from the first adaptation data;

[0011] The vehicle models in the target vehicle model set are matched with the auto parts of the stores to be updated, and the matching results are updated in the store database of the store users.

[0012] As an optional implementation of the system, the store client is also used to: if there is at least one out-of-group car accessory in the car accessories to be updated that does not have a corresponding general group, the store client adds the out-of-group car accessory and its OE code to a whitelist and uploads the whitelist to the data computing platform.

[0013] The data computing platform is also used to find the corresponding car model in the second adaptation data according to the OE code recorded in the whitelist, and to associate and match the found car model with the external car parts recorded in the whitelist, and update the matching result to the store database of the store user.

[0014] As an optional implementation of the system, the store client is also used to: if the store user wants to remove one or more car models from the store database, the store client adds the car models to be removed and the OE codes of the car models to be removed submitted by the store user to a blacklist, and uploads the blacklist to the data computing platform;

[0015] The data computing platform is also used to find the target general group in the store database based on the OE code in the blacklist, and delete the vehicle model to be removed from the vehicle model set corresponding to the target general group.

[0016] As an optional implementation of the system, the store client is also used to obtain the vehicle model data submitted by the store user and the fourth matching data of the store's auto parts, and update the fourth matching data to the store database.

[0017] As an optional implementation of the system, the system further includes a data update module, which is used to periodically acquire vehicle model change data and send the vehicle model change data to the data computing platform; the data computing platform updates the data in the data platform according to the vehicle model change data.

[0018] As an optional implementation of the system, the system further includes a data update module, which is used to periodically acquire OE encoding change data and send the OE encoding change data to the data computing platform; the data computing platform updates the data in the data middleware according to the OE encoding change data.

[0019] As an optional implementation of the system, the adaptation platform is also used to periodically collect historical whitelists, set new general groups based on the historical whitelists, and then update the first adaptation data based on the new general groups.

[0020] As an optional implementation of the system, the store client is also used to obtain the auto parts query request of the store user, and query the target auto parts from the store database and / or the data platform according to the car model in the auto parts query request.

[0021] Beneficial effects: One or more embodiments of this application provide a vehicle model and parts compatibility data maintenance system. This system can flexibly update the vehicle model and parts compatibility data of different auto repair shops according to their needs, making it convenient for shops to query the corresponding auto parts for different vehicle models and improving the work efficiency of the shops.

[0022] The entire data maintenance work is completed by the vehicle model and parts matching data maintenance system. Store users only need to submit the vehicle parts to be updated and their OE codes, which reduces the workload of store users and saves auto repair shops the cost of maintaining the store database. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of the structure of a vehicle model and parts adaptation data maintenance system according to one embodiment of this application.

[0025] Figure 2 This is a schematic diagram of the format of a first adaptation data involved in one embodiment of this application.

[0026] Figure 3 This is a schematic diagram of the format of a second adaptation data involved in one embodiment of this application.

[0027] Figure 4 This is a schematic diagram of a third-adaptive data format involved in one embodiment of this application. Detailed Implementation

[0028] First, it should be noted that the terminology used in the embodiments of this invention is for the purpose of describing specific embodiments only and is not intended to limit the invention. The singular forms “a,” “the,” and “the” used in the embodiments of this invention and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0029] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Therefore, those skilled in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and conciseness, descriptions of well-known functions and structures are omitted in the following description.

[0030] It should be noted that the steps of the corresponding methods in other embodiments are not necessarily performed in the order shown and described in this application. In some other embodiments, the methods may include more or fewer steps than those described in this application. Furthermore, a single step described in this application may be broken down into multiple steps in other embodiments; and multiple steps described in this application may be combined into a single step in other embodiments.

[0031] The vehicle model and accessory adaptation data maintenance system described in this application will be further described in detail below with reference to the accompanying drawings and specific embodiments. However, this detailed description does not constitute a limitation on the embodiments of this application.

[0032] Please refer to Figure 1 , Figure 1 A schematic diagram of a vehicle model and parts compatibility data maintenance system is shown. The system mainly includes a platform and a user terminal. The platform includes an adaptation middleware and a data computing platform, while the user terminal includes store clients and a store database.

[0033] First, let's introduce the adaptation platform. The adaptation platform is used to store the first adaptation data of vehicle model data and general group, as well as the second adaptation data of vehicle model data and OE code.

[0034] In the aforementioned adaptation platform, the first adaptation data describes the adaptation relationship between vehicle model data and universal groups. Within this first adaptation data, each universal group adapts to a set of vehicle models. Universal groups record automotive parts data of the same type but from different brands that are applicable to the corresponding set of vehicle models. This includes: universal group code, OE code, brand, and parts category. Vehicle model data primarily includes vehicle brand, manufacturer, model series, vehicle group, engine displacement, and engine model.

[0035] Please refer to Figure 2 , Figure 2 A schematic diagram of a first-adaptation data format is shown. Figure 2 The diagram shows the universal oil filter groups, including universal groups FED1557 to FED1562. Universal group FED1560 contains four different OE codes for oil filters. These four oil filters come from different brands (i.e., manufacturers), but they are universal for the corresponding vehicle models. Universal group FED1557 contains two different OE codes for oil filters. These two oil filters come from different brands (i.e., manufacturers), but they are universal for the corresponding vehicle models.

[0036] The second set of adaptation data describes the compatibility between vehicle model data and OE encoding. Please refer to [link / reference]. Figure 3 , Figure 3 A schematic diagram of a second-adaptive data format is shown. Figure 3 The diagram shows the compatibility between vehicle models and oil filter OE codes. The vehicle model data includes the car brand, manufacturer, model series, vehicle group, engine displacement, and engine model.

[0037] Next, we will introduce the store client. The store client is used to obtain the data update request submitted by the store user, the auto parts to be updated, and the OE code of the auto parts to be updated. Based on the OE code of the auto parts to be updated, the third adaptation data of the auto parts to be updated and the general group is determined.

[0038] Specifically, the store client can query the corresponding universal group in the adaptation platform based on the OE code of the auto parts to be updated, and associate the queried universal group code with the auto parts to be updated and their OE codes to obtain third-party adaptation data. Please refer to [link / reference]. Figure 4 , Figure 4 A schematic diagram of a third-adapter data format is shown.

[0039] The aforementioned store client also features blacklist and whitelist functionality. Specifically, if at least one non-grouped auto parts in the store's auto parts inventory lacks a corresponding universal group, the store client can add the non-grouped auto parts and their OE codes to the whitelist and then send the whitelist to the data computing platform. If a store user wants to remove one or more vehicle models from the store database, the store client will add the models to be removed and their OE codes to the blacklist and then upload the blacklist to the data computing platform.

[0040] The aforementioned store client also provides a user customization function, which allows users to directly enter vehicle model data and the fourth matching data of the store's auto parts, and then update the fourth matching data to the store database.

[0041] The data computing platform is used to respond to data update requests submitted by store users from store clients, and update the vehicle models and store auto parts matching data in the store database for store users based on the first matching data, the second matching data, and the third matching data.

[0042] Specifically, the data computing platform can determine the universal group code corresponding to the auto parts of the store to be updated based on the third adaptation data; then, based on the universal group code, it can find the target universal group and the target vehicle set corresponding to the target universal group from the first adaptation data; then, it can associate and match the vehicle models in the target vehicle set with the auto parts of the store to be updated, and update the matching results to the store user's store database.

[0043] Corresponding to the whitelist function of the store client, the data computing platform is also used to find the corresponding car model in the second matching data based on the OE code recorded in the whitelist, and to match the found car model with the external car parts recorded in the whitelist, and update the matching results to the store user's store database.

[0044] Corresponding to the blacklist function of the store client, the data computing platform is also used to find the target general group in the store database based on the OE code in the blacklist, and delete the model to be removed from the model set corresponding to the target general group.

[0045] Optionally, the system may also include a data update module, which periodically acquires vehicle model change data and sends it to the data computing platform; the data computing platform updates the data in the data middleware based on the vehicle model change data.

[0046] The data update module can collect recently updated model change data from publicly available product data from car manufacturers, and then send this data to the data computing platform. Model change data typically includes the car brand, manufacturer, model series, vehicle group, engine displacement, and engine model. The data update module can then query the corresponding model's maintenance manual published by the manufacturer to obtain the car parts and OE codes for that model.

[0047] For the first set of adaptation data in the data platform, the data computing platform can search for the existence of a corresponding universal group based on the OE code. If it exists, the updated vehicle model is directly added to the corresponding universal group's set of compatible vehicles. If no universal group exists for the OE code, the data computing platform can create a new universal group in the first set of adaptation data and then add the auto parts, OE code, and vehicle model. For the second set of adaptation data in the data platform, the data computing platform can search for the OE code in the second set of adaptation data. If the OE code exists in the second set of adaptation data, the vehicle model corresponding to the OE code is directly updated based on the vehicle model change data. If the OE code does not exist in the second set of adaptation data, the data computing platform enters the OE code and its corresponding vehicle model into the second set of adaptation data.

[0048] The data computing platform can also update data in the store database. Specifically, the platform can query the store database to see if a corresponding data record exists based on the OE code of the vehicle model change data. If it exists, the vehicle model in that record (i.e., store auto parts - vehicle model) is updated to match the model in the change data. If it doesn't exist, it means the store doesn't have that type of auto part in its inventory. In this case, the platform can either leave it as is or push the change data to the store user, allowing them to choose whether to update the store database. Store users can submit fourth-party matching data for vehicle model data and store auto parts based on the change data, and update the store database with this fourth-party matching data. Alternatively, they can send a data update request to the platform, along with the auto parts to be updated and their OE codes, and the platform will automatically update the store database.

[0049] Optionally, the data update module can also be used to periodically obtain OE encoding change data and send it to the data computing platform. The data computing platform updates the first and second adaptation data of the adaptation platform based on the OE encoding change data.

[0050] OE code change data typically refers to new automotive parts information released by manufacturers. This data primarily includes the type, brand, specifications, OE code, and compatible vehicle models of the new parts. The data update module can collect recently updated OE code change data from publicly available product data from automotive parts manufacturers and then send it to the data processing platform. The data processing platform can then update the first and second compatibility datasets with the OE code change data.

[0051] For data in the store database, the data computing platform can push OE code change data to store users, who can then choose whether to update the store database. Store users can submit vehicle model data and fourth-party compatibility data for their auto parts based on the OE code change data, and update the store database with this fourth-party compatibility data. Alternatively, they can send a data update request, along with the auto parts to be updated and their OE codes, to the data computing platform, which will then automatically update the store database.

[0052] Optionally, the aforementioned adaptation platform can also be used to periodically compile historical whitelists, such as compiling the historical whitelists acquired each month, setting new general groups based on the historical whitelists, and then updating the first adaptation data based on the new general groups.

[0053] Optionally, the store client can also provide a car parts search function for store users. Specifically, the store client receives car parts search requests from store users, which typically include the car model. The store client can then search the store's database based on the car model to obtain the corresponding car parts. If the car model is not found in the store's database, the store client can search for the car parts based on the car model in the data platform to determine the car parts needed, thus facilitating the store's procurement of out-of-stock parts. Store users can also directly search for specific car parts in their car parts search requests and then determine whether the car parts are compatible with the vehicle currently needing repair based on the car model information in the search results.

[0054] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the system of the embodiments of this application. In other embodiments of the specification, the above system may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0055] The various embodiments in this application 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 device 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.

[0056] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0057] It should be noted that the above examples are merely specific embodiments of the present invention, and the present invention is obviously not limited to the above embodiments, with many similar variations. All modifications that can be directly derived or conceived by those skilled in the art from the content disclosed in this invention should fall within the protection scope of this invention.

Claims

1. A vehicle model and accessory adaptation data maintenance system characterized by, The system comprises: an adaptation platform for storing vehicle model data and first adaptation data of general groups and second adaptation data of vehicle model data and OE codes; in the first adaptation data, each general group adapts a vehicle model set, and the general group is used to record different brand automobile accessory data of the same type which is common to the corresponding vehicle model set, and comprises a general group code, an OE code, a brand, and an accessory category; a store client for obtaining a data update request submitted by a store user, a to-be-updated store automobile accessory, and an OE code of the to-be-updated store automobile accessory, determining third adaptation data of the to-be-updated store automobile accessory and the general group according to the OE code of the to-be-updated store automobile accessory; a data calculation platform for determining a general group code corresponding to the to-be-updated store automobile accessory according to the third adaptation data, searching for a target general group and a target vehicle model set corresponding to the target general group from the first adaptation data according to the general group code, and associating and matching vehicle model data in the target vehicle model set with the to-be-updated store automobile accessory, and updating a matching result to a store database of the store user.

2. The system of claim 1, wherein, The store client is further configured to add the out-of-group automobile accessory and the OE code of the out-of-group automobile accessory to a white list if there is at least one out-of-group automobile accessory without a corresponding general group in the to-be-updated store automobile accessory, and upload the white list to the data calculation platform. The data calculation platform is further configured to search for a corresponding vehicle model in the second adaptation data according to the OE code recorded in the white list, and associate and match the searched vehicle model with the out-of-group automobile accessory recorded in the white list, and update a matching result to the store database of the store user.

3. The system of claim 1, wherein, The store client is further configured to add a to-be-removed vehicle model submitted by the store user and an OE code of the to-be-removed vehicle model to a black list if the store user wants to remove one or more vehicle models from the store database, and upload the black list to the data calculation platform. The data calculation platform is further configured to find a target general group in the store database according to the OE code in the black list, and delete the to-be-removed vehicle model from a vehicle model set corresponding to the target general group.

4. The system of claim 1, wherein, The store client is further configured to obtain fourth adaptation data of vehicle model data and store automobile accessories submitted by the store user, and update the fourth adaptation data to the store database.

5. The system of claim 1, wherein, The system further comprises a data update module configured to periodically obtain vehicle model change data, and send the vehicle model change data to the data calculation platform; and the data calculation platform is configured to update data in the adaptation platform according to the vehicle model change data.

6. The system of claim 1, wherein, The system further comprises a data update module configured to periodically obtain OE code change data, and send the OE code change data to the data calculation platform; and the data calculation platform is configured to update data in the adaptation platform according to the OE code change data.

7. The system of claim 1, wherein, The adaptation platform is further configured to periodically count the obtained historical white list, set a new universal group according to the historical white list, and then update the first adaptation data according to the new universal group.

8. The system of claim 1, wherein, The store client is further configured to obtain an automobile accessory query request of the store user, query target automobile accessories from the store database and / or the adaptation platform according to a vehicle type in the automobile accessory query request.

Images