Vehicle type and accessory adaptation data maintenance system

Abstract

The invention provides a vehicle type and accessory adaptation data maintenance system, and the system comprises an adaptation middle platform which is used for storing vehicle type data and first adaptation data of a general group, and the vehicle type data and second adaptation data of an OE code; the store client is used for acquiring a data updating request submitted by a store user, a to-be-updated store automobile part and an OE code of the to-be-updated store automobile part, and determining third adaptive data of the to-be-updated store automobile part and the universal group according to the OE code of the to-be-updated store automobile part; and the data computing platform is used for responding to the data updating request and updating the vehicle model data in the store database and the adaptive data of the store automobile parts for the store user according to the first adaptive data, the second adaptive data and the third adaptive data. The system can flexibly update the adaptive data of the vehicle types and the store automobile parts for different automobile maintenance stores according to the requirements of the automobile maintenance stores.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a vehicle model and accessory adaptation data maintenance system. BACKGROUND

[0002] In the automobile aftermarket, vehicle repair stores need to query vehicle repair manuals to determine which automobile accessories are adapted to different vehicle models when replacing automobile accessories for vehicles, and then recommend automobile accessories in their own inventory to customers. This process is time-consuming and labor-intensive. In addition, when vehicle repair stores register inventory automobile accessories, the entered automobile accessory names are often not the standard names of the accessories, so it is difficult to accurately match the inventory accessories when searching for vehicle model adaptation. These situations affect the work efficiency of vehicle repair stores. SUMMARY

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

[0004] One or more embodiments of the present application provide a vehicle model and accessory adaptation data maintenance system, comprising: An adaptation middle platform is configured to store vehicle model data and first adaptation data of a general group, and vehicle model data and second adaptation data of OE codes; in the first adaptation data, each general group adapts a vehicle model set, and the general group is configured to record automobile accessory data of the same type but different brands that are common to the corresponding vehicle model set, including: general group code, OE code, brand, and accessory category; A store client is configured to obtain 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, and determine 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 is configured to update, in response to the data update request of the store user submitted by the store client, 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.

[0005] As an optional implementation of the system, the data calculation platform is specifically configured to: According to the third adaptation data, determine the general group code corresponding to the to-be-updated store automobile accessory; According to the general group code, find a target general group and a target vehicle model set corresponding to the target general group from the first adaptation data; Correlate and match the vehicle models in the target vehicle model set with the to-be-updated store automobile accessories, and update the matching result to the store database of the store user.

[0006] As an optional implementation of the system, the store client is further configured to: if there is at least one out-of-group automobile accessory without a corresponding general group in the to-be-updated store automobile accessories, the store client adds the out-of-group automobile accessory and the OE code of the out-of-group automobile accessory to a whitelist, and uploads the whitelist to the data computing platform. The data computing platform is further configured to: according to the OE code recorded in the whitelist, find the corresponding vehicle model in the second adaptation data, and correlate and match the found vehicle model with the out-of-group automobile accessory recorded in the whitelist, and update the matching result to the store database of the store user.

[0007] As an optional implementation of the system, the store client is further configured to: if the store user wants to remove one or more vehicle models from the store database, the store client adds the to-be-removed vehicle models submitted by the store user and the OE codes of the to-be-removed vehicle models to a blacklist, and uploads the blacklist to the data computing platform. The data computing platform is further configured to: according to the OE codes in the blacklist, find the target general group in the store database, and delete the to-be-removed vehicle models from the vehicle model set corresponding to the target general group.

[0008] As an optional implementation of the system, the store client is further configured to obtain fourth adaptation data of the vehicle model data submitted by the store user and the store automobile accessories, and update the fourth adaptation data to the store database.

[0009] As an optional implementation of the system, the system further comprises a data updating module, the data updating module is configured to periodically obtain 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 hub according to the vehicle model change data.

[0010] As an optional implementation of the system, the system further comprises a data updating module, the data updating module is configured to periodically obtain OE code change data, and send the OE code change data to the data computing platform; the data computing platform updates the data in the data hub according to the OE code change data.

[0011] As an optional implementation of the system, the adaptation hub is further configured to periodically count the obtained historical whitelist, set a new general group according to the historical whitelist, and then update the first adaptation data according to the new general group.

[0012] As an optional implementation of the system, the store client is further configured to obtain a query request for automobile accessories of the store user, and query target automobile accessories from the store database and / or the data platform according to a vehicle model in the query request for automobile accessories.

[0013] Beneficial effects: one or more embodiments of the present application provide a vehicle model and accessory adaptation data maintenance system, which can flexibly update the adaptation data of vehicle models and store automobile accessories for different automobile repair stores according to the needs of the automobile repair stores, facilitate the store to query the automobile accessories corresponding to the automobile models, and improve the work efficiency of the store.

[0014] The entire data maintenance work is completed by the vehicle model and accessory adaptation data maintenance system, and the store user only needs to submit the store automobile accessories to be updated and the OE code of the store automobile accessories to be updated, thereby reducing the workload of the store user and saving the cost of the automobile repair store in maintaining the store database. BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creative labor.

[0016] Figure 1 is a structural schematic diagram of a vehicle model and accessory adaptation data maintenance system involved in an embodiment of the present application.

[0017] Figure 2 is a format schematic diagram of first adaptation data involved in an embodiment of the present application.

[0018] Figure 3 is a format schematic diagram of second adaptation data involved in an embodiment of the present application.

[0019] Figure 4 is a format schematic diagram of third adaptation data involved in an embodiment of the present application. DETAILED DESCRIPTION

[0020] First of all, it should be noted that the terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.

[0021] In order to make the person skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all. Therefore, those skilled in the art should realize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, in order to be clear and concise, the description of well-known functions and structures is omitted in the following description.

[0022] It should be noted that the steps of the corresponding method are not necessarily performed in the order shown and described in the present application in other embodiments. In some other embodiments, the steps included in the method can be more or less than described in the present application. In addition, a single step described in the present application can be divided into multiple steps for description in other embodiments; and multiple steps described in the present application can be combined into a single step for description in other embodiments.

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

[0024] Please refer to Figure 1 , Figure 1 A structural schematic diagram of a vehicle model and accessory adaptation data maintenance system is shown, which mainly includes a platform end and a user end. The platform end includes an adaptation middle station and a data calculation platform, and the user end includes a store client and a store database.

[0025] First, the adaptation middle station is introduced, which 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.

[0026] In the above adaptation middle station, the first adaptation data describes the adaptation relationship between the vehicle model data and the general group. In the first adaptation data, each general group adapts a vehicle model set, and the general group is used to record the same type but different brand of automobile accessory data common to the corresponding vehicle model set, including: general group code, OE code, brand and accessory category. The vehicle model data mainly includes automobile brand, manufacturer, vehicle series, vehicle group, displacement and transmitter model number, etc.

[0027] Please refer to Figure 2 , Figure 2 A format schematic diagram of a first adaptation data is schematically shown. Figure 2The figure shows a universal group of oil filters, including universal groups FED1557 through FED1562. Universal group FED1560 includes four oil filters with different OE codes. These four oil filters come from different brands (i.e., manufacturers), but are universal for all models in the corresponding model set. Universal group FED1557 includes two oil filters with different OE codes. These two oil filters come from different brands (i.e., manufacturers), but are universal for all models in the corresponding model set.

[0028] The second adaptation data describes the adaptation relationship between the vehicle model data and the OE code. Please refer to Figure 3 , Figure 3 A schematic diagram of the format of the second adaptation data is shown schematically. Figure 3 The figure shows the matching relationship between the vehicle model and the OE code of the oil filter, wherein the vehicle model data includes the car brand, manufacturer, car series, car group, displacement and engine model.

[0029] Next, the store client is introduced. The store client is used to obtain data update requests submitted by store users, the store auto parts to be updated, and the OE codes of the store auto parts to be updated, and determine the third adaptation data of the store auto parts to be updated and the universal group based on the OE codes of the store auto parts to be updated.

[0030] Specifically, the store client can query the corresponding universal group in the adaptation center based on the OE code of the store auto parts to be updated, and associate the queried universal group code with the store auto parts to be updated and the OE code of the store auto parts to be updated to obtain the third adaptation data. Figure 4 , Figure 4 A schematic diagram of the format of the third adaptation data is shown schematically.

[0031] The aforementioned store client also features a blacklist and whitelist function. Specifically, if the store's auto parts list contains at least one out-of-group auto part that doesn't have a corresponding universal group, the store client can add the out-of-group auto part and its OE code to a whitelist and then send the whitelist to the data computing platform. If a store user wishes to remove one or more models from the store database, the store client will add the models and their OE codes submitted by the store user to a blacklist and upload the blacklist to the data computing platform.

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

[0033] The data computing platform is configured to update, in response to a data update request submitted by the store client on behalf of a store user, the adaptation data of vehicle models and store automobile parts in a store database of the store user based on the first adaptation data, the second adaptation data, and the third adaptation data.

[0034] Specifically, the data computing platform can determine a general group code corresponding to the store automobile part to be updated based on the third adaptation data, find a target general group and a target vehicle model set corresponding to the target general group from the first adaptation data based on the general group code, and associate and match the vehicle models in the target vehicle model set with the store automobile part to be updated, and update the matching result to the store database of the store user.

[0035] Corresponding to the whitelist function of the store client, the data computing platform is further configured to find corresponding vehicle models in the second adaptation data based on the OE codes recorded in the whitelist, and associate and match the found vehicle models with the out-of-group automobile parts recorded in the whitelist, and update the matching result to the store database of the store user.

[0036] Corresponding to the blacklist function of the store client, the data computing platform is further configured to find a target general group in the store database based on the OE codes in the blacklist, and delete the vehicle models to be removed from the vehicle model set corresponding to the target general group.

[0037] Optionally, the system can further include a data update module configured to periodically obtain vehicle model change data and send the vehicle model change data to the data computing platform, and the data computing platform is configured to update the data in the data center based on the vehicle model change data.

[0038] The data update module can obtain the recently updated vehicle model change data by collecting the product data publicly released by automobile manufacturers, and then send the vehicle model change data to the data computing platform. The vehicle model change data usually includes automobile brands, manufacturers, vehicle series, vehicle groups, displacement, engine model numbers, etc. The data update module can query the maintenance manual of the corresponding vehicle model published by the manufacturer based on the vehicle model change data, and obtain the automobile parts and OE codes of the vehicle model from the maintenance manual.

[0039] For the first adaptation data in the data platform, the data computing platform can search in the first adaptation data according to the OE code to determine whether a corresponding general group exists. If the general group exists, the updated vehicle model is directly added to the adaptation vehicle model set of the corresponding general group. If the general group does not exist, the data computing platform can create a new general group in the first adaptation data, and then add the automobile accessory, the OE code and the vehicle model. For the second adaptation data in the data platform, the data computing platform can search in the second adaptation data according to the OE code. If the OE code exists in the second adaptation data, the vehicle model corresponding to the OE code is directly updated according to the vehicle model change data. If the OE code does not exist in the second adaptation data, the data computing platform records the OE code and the corresponding vehicle model in the second adaptation data.

[0040] The data computing platform can also update the data in the store database. Specifically, the data computing platform can query whether the data record corresponding to the OE code exists in the store database according to the OE code of the vehicle model change data. If the data record exists, the vehicle model in the data record (i.e., the store automobile accessory-vehicle model) is updated to the vehicle model in the vehicle model change data. If the data record does not exist, it means that the store does not have the automobile accessory, and the data computing platform can not process it, or can push the vehicle model change data to the store user to let the store user decide whether to update the store database. The store user can submit the fourth adaptation data of the vehicle model data and the store automobile accessory according to the vehicle model change data, and update the fourth adaptation data to the store database. The data computing platform can also receive a data update request, the automobile accessory to be updated and the OE code of the automobile accessory to be updated, and then automatically update the store database.

[0041] Optionally, the data updating module can also be used to periodically obtain OE code change data and send the OE code change data to the data computing platform. The data computing platform updates the first adaptation data and the second adaptation data of the adaptation platform according to the OE code change data.

[0042] The OE code change data is usually new automobile accessory information published by an automobile accessory manufacturer. The OE code change data mainly includes the type, brand, parameter, OE code and adaptation vehicle model of the new automobile accessory. The data updating module can collect the commodity data publicly disclosed by the automobile accessory manufacturer to obtain the recently updated OE code change data, and then send the OE code change data to the data computing platform. The data computing platform can update the OE code change data to the first adaptation data and the second adaptation data.

[0043] For the data in the store database, the data computing platform can push the OE code change data to the store user, and the store user can select whether to update the store database. The store user can submit the vehicle data and the fourth adaptation data of the store automobile parts according to the OE code change data, and update the fourth adaptation data to the store database. The data computing platform can also be initiated to update the data, the store automobile parts to be updated and the OE code of the store automobile parts to be updated, and then the store database is automatically updated by the data computing platform.

[0044] Optionally, the above-mentioned adaptation platform can also be used to periodically count the obtained historical white list, such as counting the obtained historical white list once a month, and then setting a new universal group according to the historical white list, and updating the first adaptation data according to the new universal group.

[0045] Optionally, the store client can also provide an automobile part query function for the store user. Specifically, the store client obtains an automobile part query request of the store user, and the automobile part query request usually includes a vehicle type. Then the store client can query the store database according to the vehicle type to obtain the automobile parts corresponding to the vehicle type. If there is no automobile part in the store database, the store client can query the data platform based on the vehicle type to determine the automobile part, so as to facilitate the store to purchase the out-of-stock automobile part. The store user can also directly query a specific automobile part in the automobile part query request, and then determine whether the automobile part is adapted to the current vehicle to be repaired according to the vehicle type in the query result.

[0046] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the system of the embodiments of the present application. In other embodiments of the specification, the above-mentioned system can include more or fewer components than the illustration, or combine certain components, or split certain components, or different component arrangements. The illustrated components can be implemented in hardware, software or a combination of software and hardware.

[0047] Each embodiment in the present application adopts a progressive manner for description, and the same and similar parts between each embodiment can be referred to each other. Each embodiment focuses on the difference from other embodiments. Especially for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the related parts can be referred to the part of the method embodiment.

[0048] The above describes specific embodiments of the application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order and still achieve desirable results. Additionally, the processes depicted in the figures do not necessarily require the particular order shown or sequential order in order to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or necessary.

[0049] It should be noted that the above-mentioned embodiments illustrate rather than limit the application, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the application. Accordingly, the legal scope of the application is defined only by the following claims.

Claims

1. A vehicle model and accessory adaptation data maintenance system characterized by, The system comprises: an adaptation middle station 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 automobile accessory data of the same type but different brands which are 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, and 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 updating, in response to the data update request of the store user submitted by the store client, adaptation data of vehicle model data and store automobile accessories in a store database of the store user according to the first adaptation data, the second adaptation data and the third adaptation data.

2. The system of claim 1, wherein, The data calculation platform is specifically configured to: determine a general group code corresponding to the to-be-updated store automobile accessory according to the third adaptation data; find 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; associate and match vehicle model data in the target vehicle model set with the to-be-updated store automobile accessory, 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: if there is at least one out-of-group automobile accessory without a corresponding general group in the to-be-updated store automobile accessory, the store client adds the out-of-group automobile accessory and an OE code of the out-of-group automobile accessory to a white list, and uploads the white list to the data calculation platform; the data calculation platform is further configured to find a corresponding vehicle model in the second adaptation data according to the OE code recorded in the white list, and associate and match the found 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.

4. The system of claim 1, wherein, The store client is further configured to: if the store user wants to remove one or more vehicle models from the store database, the store client adds to-be-removed vehicle models submitted by the store user and OE codes of the to-be-removed vehicle models to a black list, and uploads 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 codes in the black list, and delete the to-be-removed vehicle models from a vehicle model set corresponding to the target general group.

5. 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.

6. The system of claim 1, wherein, The system further comprises a data update module, which is 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 updates data in the data middle station according to the vehicle model change data.

7. The system of claim 1, wherein, The system further comprises a data updating module configured to periodically acquire OE code change data and send the OE code change data to the data computing platform; and the data computing platform is configured to update data in the data middle platform according to the OE code change data.

8. The system of claim 1, wherein, The adaptation middle platform is further configured to periodically count the acquired 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.

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

Images