Vehicle part trading support apparatus

Abstract

To provide a vehicle part trading support apparatus for supporting quick vehicle part trading without bothering a person having specialized knowledge about vehicles.SOLUTION: In a support system S, a support apparatus 1 comprises: a compatibility database 121 for storing compatibility information including vehicle part information in association with a category of a part, a type of a vehicle, and the compatibility of the part with the vehicle of the type; a type receiving unit 112 for receiving the type of vehicle; a category receiving unit 113 for receiving the category of the part; a compatibility calculation unit 114 for calculating the compatibility of the part with the vehicle based on the compatibility information; an extraction unit 115 for extracting two or more pieces of compatibility information related to compatible parts that belong to the category and are compatible with the vehicle of the type from the compatibility database 121; and a display command unit 117 for commanding display of the part related to the extracted compatibility information arranged based on the compatibility.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a support device for vehicle parts trading. [Background technology]

[0002] While there is a desire to sell vehicle parts (vehicle components) held in stock as recycled parts, there is also a desire to procure vehicle parts necessary for repairs. Therefore, there is a demand for transactions between those who want to sell vehicle parts and those who want to procure them. However, since vehicle parts are diverse and complex, it is not easy for those without specialized knowledge to trade vehicle parts. Therefore, transactions of vehicle parts are usually carried out through the intermediation of a specialist business (parts dealer) who has specialized knowledge about vehicles. Due to these circumstances, there is a demand for a means to support the trading of vehicle parts.

[0003] Regarding a means for supporting vehicle parts transactions, Patent Document 1 discloses a compatibility check system that uses a host computer, a customer terminal, and a stock company terminal that can communicate with each other to determine the compatibility of a product before the product is ordered by a customer, and includes an individual data storage means in the customer terminal that stores individual data related to the product the customer wishes to purchase, a product display means that displays products that can be searched for, a product data display means that receives and displays product data of the searched product from an inventory data storage means in the host computer, a compatibility check selection means that asks whether or not a compatibility check of the searched product is necessary and allows the customer to select it, a compatibility check command means that transmits a compatibility check request and the individual data to the stock company terminal when the compatibility check is selected as necessary, a compatibility display means that displays compatibility or non-compatibility received from the stock company terminal, and an ordering means that transmits order data of the product that is displayed as compatible to the host computer or another computer and places an order. According to the technology in Patent Document 1, before a customer searches for, selects, and orders a product, the stock company that holds the product can check whether the product selected by the customer is a compatible product for the customer. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2007-122458 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, the technology of Patent Document 1 only allows the inventory company to check whether the parts are compatible before placing an order. Therefore, the technology of Patent Document 1 has room for further improvement in terms of supporting the speedy trading of vehicle parts without bothering people with specialized knowledge about vehicles.

[0006] The present invention has been made in consideration of the above circumstances, and its object is to support the rapid trading of vehicle parts without having to involve people with specialized knowledge about vehicles every time. [Means for solving the problem]

[0007] As a result of intensive research into solving the above problems, the inventors have found that the above object can be achieved by searching for vehicle parts using information related to the vehicle type, and displaying search results in a list based on automatically calculated suitability. The inventors have then completed the present invention. Specifically, the present invention provides the following.

[0008] The present invention provides a vehicle parts trading support device comprising: a compatibility database configured to store compatibility information contained in information on vehicle parts associated with the category of the part, the type of vehicle, and the compatibility of the part with a vehicle of the type; a type receiving unit configured to receive the type of vehicle; a category receiving unit configured to receive the category of the part; a compatibility calculation unit configured to calculate the compatibility of the part with the vehicle based on the compatibility information; an extraction unit configured to extract from the compatibility database two or more pieces of compatibility information relating to compatible parts that belong to the category and are compatible with a vehicle of the type of vehicle; and a display command unit configured to command the display of parts related to the extracted compatibility information arranged based on the compatibility.

[0009] The compatibility database of the present invention stores the compatibility of parts with vehicles. As a result, the present invention can sort and display two or more pieces of compatibility information related to compatible parts that belong to the received category and are compatible with the received type of vehicle based on the compatibility. As a result, traders who wish to make a transaction can obtain information on substitute products that can be installed on the vehicle as substitutes for the genuine products, in addition to information on so-called genuine manufacturer products. Therefore, even if a trader does not have specialized knowledge about vehicles, he or she can consider vehicle parts including not only genuine manufacturer products but also substitute products without the mediation of a parts dealer, and can make a transaction that comprehensively considers compatibility, price, and other conditions. Effect of the Invention

[0010] The present invention can assist in quickly conducting transactions of vehicle parts without having to involve people with specialized knowledge about vehicles. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing an example of the hardware and software configurations of a support system S for vehicle parts trading according to this embodiment. [Diagram 2] FIG. 2 is an example of the compatibility information stored in the compatibility database 121. As shown in FIG. [Diagram 3] FIG. 3 is a diagram showing an example of the relationship between the pieces of information stored in the compatibility database 121. As shown in FIG. [Figure 4] FIG. 4 is a flowchart showing an example of the flow of a product trading process in the system S of this embodiment. [Diagram 5] FIG. 5 is a main flowchart showing an example of a preferable flow of the support process executed by the support device 1 of this embodiment. [Figure 6] FIG. 6 is a continuation of FIG. [Figure 7] FIG. 7 is a continuation of FIG. [Figure 8] FIG. 8 is a continuation of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an example of an embodiment of the present invention will be described in detail with reference to the drawings.

[0013] <System S> Fig. 1 is a block diagram showing an example of the hardware configuration and software configuration of the vehicle parts trading support system S of this embodiment. Hereinafter, an example of a preferred embodiment of the hardware configuration and software configuration of the vehicle parts trading support system S (system S) of this embodiment will be described with reference to Fig. 1. The vehicle parts trading support system S includes a support device 1, a purchaser terminal P that can be configured to communicate with the support device 1 via a network N, a settlement server D, and a seller terminal V.

[0014] [Support device 1] The support device 1 includes a control unit 11, a storage unit 12, and a communication unit 13. The type of the support device 1 is not particularly limited. Examples of the type include a server and a cloud server. The support device 1 of this embodiment calculates the compatibility of a part with respect to a vehicle, and issues a command to display the part based on the calculated compatibility.

[0015] [Goodness of fit] In this disclosure, the "suitability" of a part for a vehicle refers generally to an index indicating whether the part can be installed on the vehicle and used. A "high suitability" indicates that there is a high probability that the part can be installed on the vehicle and used, or that the part can actually be installed and used, regardless of the magnitude of the index's numerical value. A "low suitability" indicates that there is a low probability that the part can be installed on the vehicle and used, or that the part could not actually be installed and used, regardless of the magnitude of the index's numerical value.

[0016] [Control unit 11] The control unit 11 includes a central processing unit (CPU), a random access memory (RAM), and a read only memory (ROM).

[0017] The control unit 11 cooperates with the storage unit 12 and / or the communication unit 13 as necessary. The control unit 11 then realizes software components of the program of this embodiment executed by the support device 1, such as a similarity calculation unit 111, a type reception unit 112, a category reception unit 113, a compatibility calculation unit 114, an extraction unit 115, a price calculation unit 116, and a display command unit 117. The functions provided by each of the software components of the program of this embodiment will be described in the description of a preferred flow of the support process, which will be described later.

[0018] [Storage section 12] The storage unit 12 is a device in which data and / or files are stored, and includes a data storage unit such as a hard disk, a semiconductor memory, a recording medium, and a memory card.

[0019] The storage unit 12 may have a mechanism that enables connection via the network N to a storage device or storage system such as a NAS, a SAN, cloud storage, a file server, and / or a distributed file system.

[0020] The memory unit 12 stores a program executed by a microcomputer, a compatibility database 121, a vehicle database 122, a neural network capable of determining the similarity between two or more images (similarity discrimination neural network), a neural network capable of calculating the compatibility of parts with a vehicle (compatibility calculation neural network), a neural network capable of calculating an appropriate trading price for vehicle parts (price calculation neural network), and the like.

[0021] (Compatibility database 121) The compatibility database 121 stores compatibility information. The compatibility information includes identification information capable of identifying a vehicle part, associated with the category of the part, the type of vehicle, and the compatibility of the part with the vehicle type. The compatibility information also preferably includes transaction information related to the transaction of the part associated with the identification information. By including the transaction information in the compatibility information, the support device 1 can calculate the price of the part.

[0022] An example of the identification information is a parts management number, which is a number uniquely assigned to each type of part. An example of the category is a classification number that classifies each type of part. The compatibility information may include, as information related to part identification, a part image, part minor information, part body color, part manufacturer name, part manufacturer part number, manufacturer genuine part number, replacement part number, product name code, part name, etc., in addition to the part management number and classification number.

[0023] The type may be, for example, a model designation number that designates the model of the vehicle. The compatibility information may include, as information related to vehicle identification, in addition to the model designation number, a certified model, which is a model name certified by the manufacturer, a commonly known model, an abbreviated model, and a classification model, which are model names other than the certified model, a manufacturer code, a vehicle name code, a vehicle name, a vehicle type, a year, a grade, an engine model, a transmission model, an engine specification, and a transmission classification.

[0024] The transaction information includes the part classification, whether the part is new or recycled, inventory status, quality, retail price, quantity, information regarding sales and returns, and information regarding shipping charges.

[0025] The compatibility is not particularly limited as long as it indicates the degree to which a part fits a vehicle. For example, the compatibility is expressed as a real number, etc., with a genuine part and a completely equivalent part to the genuine part being 0, and an absolute value of the substitute part corresponding to the difference from the genuine part. By expressing the compatibility as such a real number, database processing and calculation processing related to the compatibility are facilitated.

[0026] FIG. 2 is an example of the compatibility information stored in the compatibility database 121. As shown in FIG. The conformance information shown in FIG. 2 includes the part management number “4215270500”, the part name code (part number) “7050”, and the part name “driver’s seat” as identification information that can identify the vehicle part, and the identification information includes the classification number “6” as the part category, the manufacturer code “7” as the vehicle type, the vehicle name code “8100”, the vehicle name “XXX”, the year “July 2003”, the vehicle type “3HB”, the grade “A 4WD”, the exterior color “silver”, the color number “S28”, the trim number “FAS4”, and the model designation number “11683”, the conformance degree for the vehicle type “YYY” is “0.1”, the part category “recycled product”, the inventory status “commercialized”, the remark 1 “manual”, the remark 2 “overall dirt / wrinkles / wear and tear / hole”, and the update date “2021 / 11 / 24”. 2, the number of images (not shown) of the part associated with the identification information is "5."

[0027] This allows the support device 1 to calculate the compatibility of the parts with the vehicle based on the compatibility information, particularly the vehicle name, model designation number, and classification number included in the compatibility information. Also, the support device 1 can calculate the compatibility based on an image of the part associated with the identification information.

[0028] The compatibility database 121 is preferably a relational database. The relational database is preferably a database in which information on parts, information on the type (model) of the vehicle corresponding to the part, information on the manufacturer that manufactured the part, information on the specification (part specification) of the part, the state of the part, and the purchase history of the part are stored in association with each other. The purchase history is an example of the above-mentioned transaction information.

[0029] Fig. 3 is a diagram showing an example of the relationship between each piece of information stored in the compatibility database 121. In the example shown in Fig. 3, the information related to the parts has a one-to-one correspondence with the information related to the vehicle model, the information related to the manufacturer, and the information related to the part specifications. The information related to the part specifications has a one-to-one correspondence with the information related to the part status. And the information related to the purchase history has a many-to-one correspondence with the information related to the parts, the information related to the vehicle model, the information related to the manufacturer, and the information related to the part specifications.

[0030] As a result, the information on the parts, the information on the vehicle model, the information on the manufacturer, the information on the part specifications, and the information on the part status are managed as a consistent set of information in the compatibility database 121. Therefore, the support device 1 can extract this information based on the part category and / or the type of vehicle. Furthermore, the support device 1 can associate multiple purchase histories with the parts indicated by the above-mentioned set of information and manage them in the compatibility database 121. As a result, the support device 1 can calculate the compatibility level using the amount of the purchase histories.

[0031] (Vehicle Database 122) The vehicle database 122 is configured to store vehicle information in which a vehicle type and parts that can be obtained from the vehicle type are associated with each other. The vehicle database 122 may be configured integrally with the compatibility database 121, or may be configured separately.

[0032] In vehicle database 122 configured integrally with compatibility database 121, information on the type of vehicle is used to extract information on parts included in the compatibility information. In this configuration, information on parts is managed in an integrated database, making it easy to manage the consistency of the database.

[0033] Vehicle database 122, which is configured separately from compatibility database 121, stores information related to the type of vehicle and the parts included in the vehicle in association with each other. In this configuration, the process of extracting parts that can be obtained from a vehicle is performed independently of the process related to compatibility database 121. This reduces the processing load on the database.

[0034] [Communications Section 13] The communication unit 13 is not particularly limited as long as it connects the support device 1 to the network N and enables communication with the purchaser terminal P, the payment server D, the seller terminal V, etc. Examples of the communication unit 13 include a wireless device compatible with a mobile phone network, a device connectable to a wireless LAN, and a network card compatible with the Ethernet standard.

[0035] [Network N] The type of the network N is not particularly limited as long as it enables communication between the support device 1, the purchaser terminal P, the payment server D, the seller terminal V, etc. The type of the network N is, for example, the Internet, a mobile phone network, a wireless LAN, etc.

[0036] [Purchaser terminal P] The purchaser terminal P is, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, etc. The purchaser terminal P can execute a process of displaying information provided by the support device 1, a process of providing input of the purchaser via a user interface to the support device 1, etc.

[0037] [Payment Server D] The payment server D may be, for example, a server or a cloud server. There are no particular limitations on the payment server D as long as it is configured to execute processing related to the payment between the purchaser terminal P, the system S, and the seller terminal V. The payment server D may be, for example, a server of a credit card company.

[0038] [Seller terminal V] The seller terminal V is, for example, a personal computer, a laptop computer, a smartphone, a tablet terminal, etc. The seller terminal V can execute a process of displaying information provided by the support device 1, a process of providing the support device 1 with input from the seller via a user interface, and the like.

[0039] [Product transaction processing flow] Fig. 4 is a flow chart showing an example of the flow of a product transaction process in the system S of this embodiment. Prior to step SP1 shown in Fig. 4, the support device 1 displays information on vehicle parts that can be installed in a vehicle of a type specified by a purchaser on the purchaser terminal P. The process of displaying information on the installable vehicle parts on the purchaser terminal P will be described in detail later with reference to Figs. 5 to 8.

[0040] [Step SP1: Order product] Next, in step SP1, the purchaser places an order for a product (vehicle part) based on the displayed information with the support device 1. The support device 1 generates an instance corresponding to the transaction related to the order, and moves the process to step SP2.

[0041] [Step SP2: Request payment processing] In step SP2, the support device 1 requests the payment server D to perform payment processing. The payment server D generates an instance related to the payment and performs the payment processing. The payment processing is not particularly limited and may be the same as the payment processing related to electronic transactions in the prior art. The payment server D moves the processing to step SP3.

[0042] [Step SP3: Return the result of the payment process] In step SP3, the payment server D returns the result of the payment process to the support device 1, and ends the instance related to the payment. The support device 1 moves the process to step SP4.

[0043] [Step SP4: Instruct to ship the product] In step SP4, the support device 1 instructs the seller terminal V to ship the product based on the result that the payment process was successful. The seller terminal V generates an instance related to the shipping and performs a process to ship the product. The process to ship the product is not particularly limited and may be similar to the process to ship a product related to mail order sales in the prior art. The seller terminal V moves the process to step SP4.

[0044] [Step SP5: Report that the product has been shipped] In step SP5, the seller terminal V reports the completion of the shipment of the product to the support device 1, and ends the instance related to the shipment. The support device 1 moves the process to step SP6.

[0045] [Step SP6: Request confirmation of provisional sales] In step SP6, the support device 1 requests the settlement server D to confirm the provisional sales. The settlement server D generates an instance related to the confirmation of the provisional sales, and performs a process to confirm the provisional sales. The process to confirm the provisional sales is not particularly limited, and may be the same as the process to confirm the provisional sales related to electronic transactions in the prior art. The settlement server D moves the process to step SP7.

[0046] [Step SP7: Return the result of the payment process] In step SP7, the settlement server D returns the result of the provisional sales confirmation process to the support device 1, and ends the instance related to the confirmation of the provisional sales.

[0047] [Step SP8: Ship the product] Step SP8 is a step carried out between steps SP4 and SP5. In step SP8, the seller using the seller terminal V ships the product to the purchaser using the purchaser terminal P. The process of shipping the product is not particularly limited. This process includes a procedure of sending information instructing shipping to the sender of the product via the network N, a procedure of instructing or executing shipping of the product using various methods not involving the seller terminal V, and the like.

[0048] [Main Flowchart of Support Processing] Fig. 5 is a main flow chart showing an example of a preferred flow of the support processing executed by the support device 1 of this embodiment. Fig. 6 is a diagram continuing from Fig. 5. Fig. 7 is a diagram continuing from Fig. 6. Fig. 8 is a diagram continuing from Fig. 7. The following is an example of a preferred flow of the support processing executed by the support device 1 of this embodiment using Figs. 5 to 8.

[0049] The support device 1 preferably executes a process of calculating a similarity between an image of a part for which a compatibility is to be calculated and an image of an optimum part, and calculating a compatibility of the part with respect to the vehicle based on the calculated similarity and compatibility information. Steps S1 to S4 shown below are an example of a preferred flow of the process.

[0050] [Step S1: Determine whether to calculate similarity] The control unit 11 executes the similarity calculation unit 111 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of determining whether to calculate the similarity between an optimum part exemplified by a genuine part or the like for a specific type of vehicle and a specific part by the similarity calculation unit 111 (step S1, similarity calculation necessity determination step). If it is determined that the similarity should be calculated, the control unit 11 shifts the process to step S2. If it is determined that the similarity should not be calculated, the control unit 11 shifts the process to step S5.

[0051] The step of determining whether or not the similarity should be calculated is not particularly limited. This step includes, for example, a procedure of determining that the similarity should be calculated when a terminal such as the purchaser terminal P asks whether a specific part (a part for which the compatibility is calculated) can be installed in a specific type of vehicle. This step also includes a procedure of determining that the similarity should be calculated using a part as a part for which the compatibility with a specific type of vehicle has not been calculated when there is a part. This allows the support device 1 to automatically register compatibility for combinations of parts and vehicle types for which compatibility has not been manually registered, and combinations of parts and vehicle types for which machine learning related to compatibility has not been performed, which will be described later.

[0052] [Step S2: Acquire images] The control unit 11 executes a process of acquiring images of the predetermined parts that can be installed on the type of vehicle determined to be the calculation target in step S1 and images of the parts to be calculated from the compatibility database 121, etc., by the similarity calculation unit 111 (step S2, image acquisition step). The control unit 11 shifts the process to step S3.

[0053] [Step S3: Calculate similarity] The control unit 11 executes a process of calculating the similarity between the image of the predetermined part and the image of the calculation target part acquired in step S2 by the similarity calculation unit 111 (step S3, similarity calculation step). The control unit 11 moves the process to step S4.

[0054] The similarity calculation step is not particularly limited. The similarity calculation step preferably includes a procedure of calculating the similarity using the above-mentioned similarity discrimination neural network. The image of the part may have non-constant shooting parameters, such as the shooting environment, shooting angle, angle of view, zoom, etc. On the other hand, the similarity discrimination neural network is constructed so as to be able to calculate the similarity between images whose shooting parameters are non-constant. Therefore, by using the similarity discrimination neural network, it is possible to calculate the similarity between images whose shooting parameters are non-constant.

[0055] [Step S4: Update the compatibility information] Control unit 11 executes a process of updating the compatibility information related to the calculation target part whose similarity was calculated in step S3, using similarity calculation unit 111 (step S4, compatibility information update step). Control unit 11 moves the process to step S5. The compatibility information update step updates the compatibility information related to the calculation target part so as to include the compatibility calculated based on the similarity calculated in step S3. Note that the "calculated compatibility" here refers to the compatibility when the "calculation target part" is installed in the "specific type of vehicle" that was the subject of discrimination in step S1.

[0056] The assistance device 1 preferably executes a process for estimating the value of the vehicle and displaying the estimated value. Steps S5 to S9 shown below are an example of a preferred flow of the process.

[0057] [Step S5: Determine whether to estimate the value of the vehicle] The control unit 11, in cooperation with the memory unit 12 and the communication unit 13, executes a process of determining whether to estimate the value of the vehicle (step S5, value estimation presence / absence determination step). If it is determined that an estimate is to be made, the control unit 11 transfers the process to step S6. If it is determined that an estimate is not to be made, the control unit 11 transfers the process to step S10. The value estimation presence / absence determination step includes, for example, a procedure of determining that the value of the vehicle is to be estimated when a request for an estimate of the value of the vehicle is received from the seller terminal V.

[0058] [Step S6: Receive type] The control unit 11 executes the type receiving unit 112 in cooperation with the memory unit 12 and the communication unit 13. Then, the control unit 11 executes a process of receiving the vehicle type from the seller terminal V or the like by the type receiving unit 112 (step S6, type receiving step). The control unit 11 moves the process to step S7. The "type" received in the type receiving step is not particularly limited, and may include, for example, one or more of the "model designation number," "vehicle name," "grade," "year," etc., related to the vehicle type.

[0059] [Step S7: Extraction of obtainable parts] The control unit 11 executes the extraction unit 115 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of extracting, by the extraction unit 115, one or more parts that can be obtained from the vehicle of the type received in step S6 from the vehicle database 122 (step S7, part extraction step). The control unit 11 shifts the process to step S8.

[0060] [Step S8: Calculate the price] The control unit 11 executes the price calculation unit 116 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of calculating a fair price as a transaction price for each of the one or more parts extracted in step S7 by the price calculation unit 116 (step S8, vehicle price calculation step). The control unit 11 shifts the process to step S9.

[0061] [Step S9: Command display] The control unit 11 executes the display command unit 117 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of commanding the seller terminal V, etc. to display the fair price calculated in step S8 by the display command unit 117 (step S9, price display command step). The control unit 11 moves the process to step S10.

[0062] The price display command step preferably enables the display of the total transaction price of the parts, thereby enabling a seller or the like to estimate the value of a vehicle held in inventory, including the value of parts that can be obtained from the vehicle.

[0063] The assistance device 1 preferably executes a process for issuing a command to display a list of parts that are compatible with a specified type of vehicle. Steps S10 to S16 shown below are an example of a preferred flow of the process.

[0064] [Step S10: Determine whether the purchase of vehicle parts is desired] The control unit 11, in cooperation with the memory unit 12 and the communication unit 13, executes a process of determining whether or not the purchase of a vehicle part is desired (step S10, purchase desire determination step). If it is determined that a purchase is desired, the control unit 11 transfers the process to step S11. If it is not determined that a purchase is desired, the control unit 11 transfers the process to step S17. The purchase desire determination step includes, for example, a procedure of determining that the purchase of a vehicle part is desired when a request for searching for a vehicle part is received from the purchaser terminal P.

[0065] [Step S11: Receive type] The control unit 11 executes the type receiving unit 112 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of receiving the vehicle type from the purchaser terminal P or the like by the type receiving unit 112 (step S11, type receiving step). The control unit 11 moves the process to step S12. The "type" received in the type receiving step is not particularly limited, and includes, for example, one or more of the "model designation number," "vehicle name," "grade," "year," etc., related to the vehicle type.

[0066] [Step S12: Receive category] The control unit 11 executes the category receiving unit 113 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of receiving a category to which the part desired to be purchased belongs from the purchaser terminal P or the like by the category receiving unit 113 (step S12, category receiving step). The control unit 11 shifts the process to step S13.

[0067] The "category" received in the category receiving step is not particularly limited. The category may be a category selected from a category list displayed on the purchaser terminal P in response to a command from the support device 1, or a category selected from a list of candidate categories related to the part name provided from the support device 1 based on the part name, part ID, etc. provided from the purchaser terminal P. The category receiving step may also include a procedure of receiving the part name, part ID, etc. provided from the purchaser terminal P and determining the category based on the received part name.

[0068] [Step S13: Calculate the compatibility] The control unit 11 executes the compatibility calculation unit 114 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of calculating the compatibility of each part belonging to the category received in step S12 with the type of vehicle received in step S11 by the compatibility calculation unit 114 (step S13, compatibility calculation step). The control unit 11 shifts the process to step S14.

[0069] The compatibility calculation step is not particularly limited. For example, the compatibility calculation step includes a procedure of searching the compatibility database 121 using information on the type received in step S11 (such as "model designation number", "vehicle name", "grade", "year", etc.) and information on the category received in step S12 (such as "classification number", "parts ID", etc.) as search keys, and calculating the compatibility based on the search information of a user who is searching for a specific vehicle name. This allows the support device 1 to calculate the compatibility of the part with a vehicle type searched for by a larger number of users.

[0070] The compatibility calculation step preferably includes a procedure of calculating the similarity of each of the car name, the model number, and the classification number in the compatibility information between the genuine product and the part to be calculated, weighting the calculated similarities, and adding them up to calculate the compatibility m. For example, the procedure includes a procedure of calculating the similarity of the car name (s1), the similarity of the model number (s2), and the similarity of the classification number (s3) in the range of 0 (similarity of perfect compatibility) to 1 (similarity of no compatibility at all), and calculating the compatibility m by the formula m=w1×s1+w2×s2+w3×s3. Here, w1 is a given weight for the car name, w2 is a given weight for the model number, and w3 is a given weight for the classification number, and w1+w2+w3=1. The compatibility m is an index in which a value of 0 corresponds to a high compatibility with no problem, and a value of 1 corresponds to a low compatibility with no compatibility at all.

[0071] The compatibility calculation step may include a procedure for calculating the compatibility based on the compatibility calculation neural network. This allows the support device 1 to calculate the compatibility reflecting machine learning using the transaction information described later.

[0072] In addition, the compatibility calculation step may include a procedure for calculating the compatibility using the compatibility calculated based on the similarity between images exemplified in steps S1 to S4. This allows the support device 1 to calculate the compatibility even when the search information and the transaction information are not available. Note that, in order to indicate the compatibility of a part for which it is difficult to calculate the compatibility, the compatibility calculation step may include a procedure for displaying a form for inquiring about the compatibility of the part to the seller of the part.

[0073] [Step S14: Extract compatibility information] The control unit 11 executes the extraction unit 115 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of extracting compatibility information in which the compatibility calculated in step S13 satisfies a predetermined criterion by the extraction unit 115 (step S14, extraction step). The control unit 11 moves the process to step S15. The predetermined criterion may be, for example, a criterion set by an administrator of the system S, a criterion determined by a compatibility calculation neural network, or the like.

[0074] The support process preferably includes a price calculation step in step S15. It may be difficult for a person without specialized knowledge to trade vehicle parts, including recycled products, at an appropriate price. By including the price calculation step in the support process, the support device 1 can support the vehicle parts to be traded at an appropriate price.

[0075] [Step S15: Calculate the price] The control unit 11 executes the price calculation unit 116 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of calculating a fair price as a transaction price of the vehicle part corresponding to the compatibility information extracted in step S14 by the price calculation unit 116 (step S15, price calculation step). The control unit 11 shifts the process to step S16.

[0076] The price calculation step is not particularly limited. For example, the price calculation step includes a procedure of calculating a fair price based on a past transaction price included in the transaction information stored in the matching database 121. The price calculation step may also include a procedure of calculating a fair price using a price calculation neural network that has been subjected to machine learning of calculating a fair transaction price based on the transaction information stored in the matching database 121.

[0077] [Step S16: Command display] The control unit 11 executes the display command unit 117 in cooperation with the storage unit 12 and the communication unit 13. Then, the control unit 11 executes a process of commanding the purchaser terminal P or the like to display a list in which the parts related to the compatibility information extracted in step S14 are arranged based on the compatibility calculated in step S13, by the display command unit 117 (step S16, display command step). The control unit 11 moves the process to step S17.

[0078] The arrangement based on the degree of compatibility is not particularly limited. For example, the arrangement may be from parts that are highly compatible with the vehicle to parts that are less compatible with the vehicle. This allows the purchaser or the like to proceed with considering a transaction starting with parts that are more compatible with the vehicle. It is preferable that the display of the list is accompanied by information on whether each part is compatible with the vehicle. The information on whether a part is compatible with the vehicle is, for example, information indicating that the part is compatible with the vehicle when the degree of compatibility satisfies a given standard. This allows the purchaser to select and purchase compatible parts even if he or she does not have specialized knowledge about vehicles.

[0079] The display command step preferably includes a procedure for commanding the display of a list of parts accompanied by the fair prices calculated in step S15. This allows a purchaser to trade for a part he or she wishes to purchase at a fair price even if he or she does not have specialized knowledge about vehicles.

[0080] [Sales of vehicle parts] When a request to purchase one or more of the vehicle parts displayed in step S16 is received from the purchaser terminal P or the like, the support device 1 executes a process related to the sale of the vehicle parts. In this process, the purchaser selects a shipping method, a payment method, etc. for the vehicle parts. When the purchaser makes a selection, the control unit 11 of the support device 1 moves the process to step S17.

[0081] The support device 1 preferably accumulates information related to vehicle part transactions and executes a process of performing machine learning related to suitability, etc., based on the accumulated information. Steps S17 to S22 shown below are an example of a preferred flow of the process.

[0082] [Step S17: Determine whether the transaction has been concluded] The control unit 11, in cooperation with the storage unit 12 and the communication unit 13, executes a process of determining whether a transaction for the vehicle part has been concluded (step S17, transaction conclusion determination step). If it is determined that the transaction has been concluded, the control unit 11 shifts the process to step S18. If it is not determined that the transaction has been concluded, the control unit 11 shifts the process to step S19.

[0083] [Step S18: Update transaction information] The control unit 11, in cooperation with the storage unit 12 and the communication unit 13, executes a process of updating the transaction information so that the transaction information includes information related to the transaction determined to have been concluded in step S17 (step S18, transaction conclusion update step). The control unit 11 shifts the process to step S19.

[0084] When the transaction is concluded, the control unit 11 cooperates with the storage unit 12 and the communication unit 13 to send a command to prepare for shipment to the seller terminal V. When the seller completes the preparation for shipment, the support device 1 notifies the purchaser terminal P of the completion of shipment.

[0085] [Step S19: Determine whether a return has been made] The control unit 11, in cooperation with the storage unit 12 and the communication unit 13, executes a process of determining whether or not the vehicle part has been returned (step S19, return determination step). If it is determined that the vehicle part has been returned, the control unit 11 shifts the process to step S20. If it is not determined that the vehicle part has been returned, the control unit 11 shifts the process to step S21.

[0086] [Step S20: Update transaction information] The control unit 11, in cooperation with the storage unit 12 and the communication unit 13, executes a process of updating the transaction information so that the information related to the return determined to have been made in step S19 is included (step S20, return update step). The control unit 11 moves the process to step S21.

[0087] [Step S21: Determine whether to perform machine learning] The control unit 11, in cooperation with the storage unit 12 and the communication unit 13, executes a process of determining whether or not to perform machine learning (step S21, machine learning determination step). If it is determined that machine learning is to be performed, the control unit 11 moves the process to step S22. If it is not determined that machine learning is to be performed, the control unit 11 returns the process to step S1, and repeats the processes from step S1 to step S22.

[0088] The machine learning determination step may include various procedures, such as a procedure of determining that machine learning will be performed if it is a predetermined timing, such as a timing specified by an administrator of system S, and a procedure of determining that machine learning will be performed if the amount of updates to the transaction information reaches a predetermined amount, such as an amount specified by the administrator of system S.

[0089] [Step S22: Run machine learning] The control unit 11 executes the compatibility calculation unit 114 in cooperation with the storage unit 12. Then, the control unit 11 executes a process of executing machine learning related to the neural network stored in the storage unit 12 by the compatibility calculation unit 114 (step S22, machine learning step). The control unit 11 returns the process to step S1 and repeats the processes from step S1 to step S22.

[0090] The machine learning in the machine learning step is not particularly limited. For example, the machine learning is machine learning that treats transaction information related to a transaction in which there was no return within a predetermined period after the transaction as training data supporting a higher degree of suitability, and treats transaction information related to a transaction in which there was a return within a predetermined period after the transaction as training data supporting a lower degree of suitability. The machine learning is not limited to machine learning using a neural network, and may be machine learning that calculates or corrects the suitability m by a formula using the number of transactions in which there was no return c and the number of transactions in which there was a return r as variables. An example of the formula is m=max(0,rc). However, the suitability m calculated by the formula is set to 0 for the suitability of a genuine product, and the higher the degree of incompatibility with the vehicle, the larger the value.

[0091] [Register the vehicle parts you wish to sell] The support process preferably includes a process of registering information on the vehicle parts desired to be sold in the compatibility database 121. This allows sellers and the like using the seller terminal V to trade the vehicle parts via the support device 1. In order to provide the buyer with the appearance of the part, the registration process preferably includes a procedure of registering an image of the vehicle part. In addition, the registration process preferably includes a procedure of registering a desired selling price for the vehicle part. In the procedure of registering the desired selling price for the vehicle part, the support device 1 preferably commands the display of the price calculated in the price calculation unit 116. This allows the seller to put up the vehicle part at an appropriate desired selling price that reflects the trading information.

[0092] The registration process preferably includes a procedure for registering data in a batch in various formats such as CSV format in order to reduce the seller's workload. The registration process also preferably includes a procedure for importing data from a vehicle management system other than the assistance device 1 or the system S in order to utilize existing data, prevent inconsistencies with existing data entered manually, and reduce the seller's workload.

[0093] [Determining compatible vehicles] The support process preferably includes a process for determining a suitable vehicle on which the specified vehicle part can be installed. The process includes, for example, a process for calculating the suitability for each combination of the specified vehicle part and the type of vehicle related to the vehicle part in the compatibility database 121 in the same procedure as the suitability calculation step, and extracting suitability information in which the suitability calculated in the same procedure as the extraction step satisfies a predetermined standard. This allows a trader to consider vehicles of the type and year of the vehicle to be installed, including not only vehicles of the type and year of the vehicle that can be used as a genuine manufacturer part, but also vehicles that can be used as a substitute for the vehicle part, even if he does not have specialized knowledge about vehicles, and to conduct a transaction that takes into consideration the suitability, price, and other conditions comprehensively. In addition, the process can also contribute to reflecting the value of the vehicle part installed in a suitable vehicle in the price calculated in the above-mentioned "process for registering information related to the vehicle part to be sold".

[0094] [Register compatibility information] The support process preferably includes a process of registering compatibility information. This allows more accurate compatibility, such as compatibility determined after actually attempting to install the device on a vehicle, to be stored in the compatibility database 121. In addition, the support process preferably includes a process of manually updating the compatibility information stored in the compatibility database 121. This allows the similarity between images, compatibility calculated erroneously by machine learning, etc., transaction prices, etc. to be corrected to more appropriate ones.

[0095] [Effects of Support Processing] The support process of this embodiment issues a command to sort and display two or more pieces of compatibility information related to compatible parts that belong to the received category and are compatible with the received type of vehicle based on the compatibility. This allows a trader who wishes to make a transaction, such as a purchaser using the purchaser terminal P, to obtain information on substitute products that can be installed on the vehicle as substitutes for the genuine products, in addition to information on so-called genuine products from the manufacturer. Therefore, even if the trader does not have specialized knowledge about vehicles, he or she can consider vehicle parts including not only genuine products from the manufacturer but also substitute products without being mediated by a parts dealer, and can make a transaction that comprehensively considers compatibility, price, and other conditions.

[0096] <Usage example> The following is a description of an example of how the support device 1 can be used.

[0097] [Registering conformity information] An administrator of the support device 1, a user of the seller terminal V, or the like registers compatibility information related to vehicle parts that can be installed on a specific type of vehicle or vehicle parts that cannot be installed on the vehicle in the compatibility database 121. In addition, an administrator of the support device 1, a user of the seller terminal V, or the like registers images of the vehicle parts in the compatibility database 121.

[0098] [Image-based compatibility calculation] The support device 1 calculates the similarity of the images registered in the matching database 121, and calculates the matching degree based on the calculated similarity. Then, the support device 1 registers the calculated matching degree in the matching database 121.

[0099] [Verifying the value of vehicle parts] A seller who wishes to sell vehicle parts transmits information related to the type of vehicle from which the vehicle parts to be sold will be acquired to the support device 1 via the seller terminal V. The support device 1 calculates the transaction price of each part that can be acquired from the vehicle of that type, using the information stored in the vehicle database 122 and the information stored in the compatibility database 121. The support device 1 displays the calculated prices on the seller terminal V. The seller uses the displayed prices to comprehensively consider whether or not to sell the vehicle parts, and then sells the vehicle parts.

[0100] [Search for vehicle parts] A purchaser who wishes to purchase a vehicle part transmits information related to the type of vehicle on which the vehicle part is to be installed and information related to the category of the vehicle part to the support device 1 via the purchaser terminal P. The support device 1 receives the information transmitted via the purchaser terminal P. Then, the support device 1 calculates the compatibility between the vehicle of that type and the vehicle part using the information stored in the compatibility database 121. The support device 1 causes the purchaser terminal P to display a list of vehicle parts that can be installed on the vehicle of that type, arranged using the calculated compatibility.

[0101] [Purchase of vehicle parts] The purchaser uses the list of vehicle parts displayed on the purchaser terminal P to comprehensively consider the price, suitability, etc., and purchases the vehicle part. The support device 1 communicates with the settlement server D and the seller terminal V to mediate the transaction of the vehicle part between the purchaser and the seller. The support device 1 stores transaction information indicating that the transaction of the vehicle part has been concluded in the compatibility database 121.

[0102] [Return of vehicle parts] The purchaser attempts to install the purchased vehicle part. Then, the purchaser returns the vehicle part that could not be installed on the vehicle via the support device 1. The support device 1 stores transaction information indicating that the vehicle part has been returned in the compatibility database 121.

[0103] [Machine learning for relevance] The support device 1 performs machine learning to treat transaction information relating to a transaction in which there was no return within a predetermined period after the transaction as training data that supports a higher degree of suitability, and to treat transaction information relating to a transaction in which there was a return within a predetermined period after the transaction as training data that supports a lower degree of suitability. This allows the support device 1 to calculate a high degree of suitability for a combination of vehicle models and parts that was traded in large numbers without being returned, and to calculate a high degree of suitability for a combination of vehicle models and parts that was returned frequently.

[0104] It should be noted that within the scope of the concept of the present invention, a person skilled in the art may come up with various modifications and alterations. It is understood that such modifications and alterations fall within the scope of the present invention. For example, even if a person skilled in the art appropriately adds, deletes, or modifies the design of the above-described embodiment, or adds, omits, or modifies the conditions of a process, these modifications and alterations are included in the scope of the present invention as long as they include the gist of the present invention. [Explanation of symbols]

[0105] S System 1 Support equipment 11 Control section 111 Similarity calculation unit 112 Type Reception Unit 113 Category Reception Department 114 Compatibility Calculation Unit 115 Extraction part 116 Price Calculation Department 117 Display command section 12 Storage section 121 Conformity Database 122 vehicle database 13. Communications Department N Network P Purchaser terminal D Payment server V Seller terminal

Claims

1. a compatibility database configured to store compatibility information including information on a vehicle part associated with a category of the part, a type of vehicle, and a compatibility of the part with the type of vehicle; A type receiving unit configured to receive a type of vehicle; a category receiver configured to receive a category of the part; a compatibility calculation unit configured to calculate a compatibility of the part with the vehicle based on the compatibility information; an extracting unit configured to extract from the compatibility database two or more pieces of compatibility information related to compatible parts that belong to the category and are compatible with the vehicle type; a display command unit configured to command display of the parts related to the extracted fitness information arranged based on the fitness; Equipped with Support device for vehicle parts trading.

2. The compatibility database is configured to store the compatibility information, the compatibility information being further associated with transaction information related to a transaction of the part, The display command unit is configured to command the display of the transaction information. The support device according to claim 1 .

3. a price calculator configured to calculate a price of the part based on the goodness of fit associated with the part and the transaction information associated with the part. The support device according to claim 2 .

4. A vehicle database configured to store vehicle information in which a type of vehicle and a part that can be obtained from the vehicle of the type are associated with each other, The display command unit is configured to command a display of prices of parts that can be obtained from the vehicle type received by the type receiving unit based on the vehicle database. The support device according to claim 3.

5. the compatibility calculation unit is configured to calculate the compatibility by machine learning based on the transaction information; The machine learning is machine learning that treats transaction information related to a transaction in which there was no return within a predetermined period after the transaction as training data that supports a higher degree of conformance, and treats transaction information related to a transaction in which there was a return within a predetermined period after the transaction as training data that supports a lower degree of conformance. The support device according to claim 2 .

6. a similarity calculation unit configured to calculate a similarity between an image of one part and an image of another part; the fit database is configured to store the fit information including an image of the part; the compatibility calculation unit is configured to calculate a compatibility of the part with the vehicle based on similarity and compatibility information between an image of a part for which compatibility with the vehicle is to be calculated and an image of a predetermined part that can be attached to the vehicle. The support device according to claim 1 .

Images