JP2006182319A - Information providing method for vehicle associated parts, information providing server, and information providing system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To specify a failure section of a vehicle loaded with an electronic control part (an ECU) and provide information about parts by utilizing a network. <P>SOLUTION: A terminal unit 10a of a user 10 and a server computer 30 of a service company 100 are connected with the Internet 20 to transmit and receive information mutually. When the server computer 30 obtains the information for specifying a vehicle from the terminal unit 10a, it refers to data base 42 for vehicle information (product number) to specify the vehicle. Next, it refers to data base 48 for searching failure depending on failure phenomenon and sends a question-asking screen corresponding to the contents of the failure phenomenon of the specified vehicle to the terminal unit 10a to specify a failure section including the ECU from the reply. When the failure section is specified, the server computer 30 refers to commodity information data base 52 and failure information data base 56 and extracts information related to the corresponding parts by taking the degree of failure occurrence frequency into account to provide the terminal unit 10a with the information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information providing method, an information providing server, and an information providing system for vehicle-related parts using a network. More specifically, the present invention relates to an information providing method suitable for specifying (or searching for) a defective part of a vehicle, a server, It is about the system.

  In recent years, with the spread of networks represented by the Internet, display of product catalogs and transaction of products have been activated in various industries. The auto industry is no exception, and it improves the repeat rate and purchase frequency by providing personalized products, advertisements, and services to Internet users (users) to improve customer satisfaction with products and websites. And trying to increase sales.

  On the other hand, whether or not an electronic control unit (ECU: Electronic Control Unit) such as an automobile is good or bad has a self-judgment system in the vehicle itself in the state of being mounted on the vehicle based on the maintenance manual for each vehicle type and model year issued by the manufacturer. In some cases, inspections are carried out, and inspections of defective parts on the vehicle side or replacement of equipment are performed for each abnormality / normality / code. If the abnormal code is not resolved even after inspection or part replacement, the ECU is replaced and compared with the state before the replacement to determine whether the ECU is good or bad.

  However, in the background art as described above, if there is a non-defective product for the replacement ECU, it is possible to make a comparison before and after the replacement. There is an inconvenience that it is difficult to specify whether there is a cause on the side or a problem on the ECU side. Even if it is confirmed that there is a problem on the ECU side, the repair or regeneration of the ECU is not performed at a repair shop or the like, and the ECU is merely replaced as a part. For this reason, even if a person has specialized knowledge about the ECU, even if it can be reused by repair, it is difficult to make the determination, so that most ECUs are discarded.

  On the other hand, technical solutions and parts information, such as information on breakdowns and malfunctions, which are the needs of automobile maintenance personnel, and troubleshooting related to electronic control equipment (ECU) of automobiles, are sold on the above-mentioned Internet. It is not provided as a service. Therefore, if it is possible to identify a malfunctioning part of an automobile equipped with an ECU or obtain information about the malfunctioning part using a network such as the Internet, it is very convenient for a person engaged in automobile maintenance. It is.

  The present invention focuses on the above points. The purpose of the present invention is to identify (or search for) a defective part of a vehicle equipped with an electronically controlled component (ECU) using a network and to obtain component information relating to the defective part. Is to provide.

  In order to achieve the above object, the vehicle-related component information providing method of the present invention is a vehicle for providing a requesting terminal via a network with a method for searching for a defective portion of a vehicle equipped with an electronically controlled component and information regarding the defective portion. An information providing method for related parts, the step of identifying a vehicle based on information for identifying a vehicle acquired from the requesting terminal, performing an inquiry regarding the malfunction phenomenon of the identified vehicle to the requesting terminal, The method includes a step of identifying the defective part based on an answer from the requesting terminal to the inquiry, and a step of transmitting information on a part of the identified defective part to the requesting terminal.

  One of the main forms is that the response history information based on the response information from the requesting terminal for the inquiry and the sales performance information based on the purchase information of the vehicle parts are totaled, and the frequency of trouble occurrence is high from the total result Alternatively, the information on the parts is transmitted to the requesting terminal in the order in which the sales results are large.

  The vehicle-related component information providing server according to the present invention is a vehicle-related component information providing server that provides a method for searching for a defective portion of a vehicle equipped with an electronic control component and information on the defective portion to a requesting terminal through a network. Vehicle information database in which vehicle information is collected, failure search database by failure phenomenon in which information for narrowing down inspection items by vehicle is accumulated, failure information database in which vehicle inspection items and inspection points are accumulated, and vehicle-related A component information database in which component information is integrated is obtained, vehicle identifying information is acquired from the requesting terminal, and a vehicle corresponding to the acquired vehicle identifying information is identified with reference to the vehicle information database. Refer to the vehicle identification means, the failure search database by failure phenomenon, and narrow down the inspection items of the identified vehicle. For the requesting terminal, refer to the fault location specifying means for specifying the fault location, the failure information database or the component information database, and extract information on the part of the specified fault location, And a component information providing means for transmitting to the requesting terminal.

  One of the main forms is that the response history information based on the response information from the requesting terminal for the inquiry and the sales performance information based on the purchase information of the vehicle-related parts are totaled, and the response by failure phenomenon for each vehicle information A totaling unit for generating a result master, wherein the component information providing unit is configured to request the terminal in the order in which the trouble occurrence frequency is high or the sales record is high from the answer phenomenon-specific master record. It is characterized by providing parts information. In another aspect, the electronic control component simulation apparatus and a terminal connectable to the simulation apparatus are provided.

  An information providing system for a vehicle-related part according to the present invention includes an information providing server for a vehicle-related part according to any one of claims 3 to 5, and a large number of requesters capable of exchanging information with the information providing server via a network. Terminal. The above and other objects, features and advantages of the present invention will become apparent from the following detailed description and the accompanying drawings.

  The present invention uses a network to identify a vehicle based on vehicle identification information received from a requesting terminal, conducts an inquiry according to the failure or malfunction phenomenon of the vehicle, identifies a malfunction location, and identifies Since it is decided to provide the requesting terminal with the part information related to the troubled part, it is possible to provide appropriate information regarding the maintenance and repair of the vehicle and to improve the work efficiency. In addition, since it can be determined whether or not the defective part is in the electronic control component (ECU), the electronic control component that does not need to be discarded can be reused by repair, and resources can be effectively utilized. Furthermore, when repairing or inspecting electronic control parts, it is possible to utilize the response information acquired from the requesting terminal to improve the efficiency of the work, verify the repair location, and the like.

  Hereinafter, the best mode for carrying out the present invention will be described in detail based on examples.

  First, Embodiment 1 of the present invention will be described with reference to FIGS. First, the system configuration of the present invention will be described with reference to FIGS. FIG. 1 is a block diagram showing the system configuration of this embodiment. The vehicle referred to in the present invention is a vehicle equipped with an electronic control component (or electronic control device / electronic control unit) (ECU: Electronic Control Unit). As shown in FIG. 1, the vehicle-related component information providing system of this embodiment includes a large number of users 10 having terminals 10 a, 10 b, 10 c,. The service company 100 provides the user 10 with information related to vehicle-related parts. The service company 100 has a server computer 30 and a storage device 40 and a simulator 72 (see FIG. 4) for checking the ECU as necessary. In the present embodiment, the user 10 is not a vehicle owner but a maintenance factory that performs vehicle maintenance or repair. The terminals 10a, 10b, 10c,... Include information input units 12a, 12b, 12c,... Such as a keyboard, display units 14a, 14b, 14c,. A personal computer (PC) provided with a browser connected to the computer 20 to exchange and display various information. The terminals 10a, 10b, 10c,... (Hereinafter referred to as “10a”) and the server computer 30 are connected to the Internet 20 via a communication unit, a communication line, a provider, etc. (not shown).

  The server computer 30 of the service company 100 is mainly composed of an information processing unit 32 that performs various arithmetic processes and the like, and includes a vehicle information setting program 34, a defect content setting program 36, a parts information display program 38, and a totaling program 39. In addition, a mail program (not shown) for sending and receiving E-mail with the terminal 10a on the user 10 side is provided as necessary. The storage device 40 includes a vehicle information (product number) database 42, a failure search database 48 for each failure phenomenon, a product information database 52, a failure information database 56, a failure information file 60, a customer information file 62, and a sales record file 64. .

  FIG. 2 shows record structures of various databases in the storage device 40. First, the vehicle information (product number) database 42 is a collection of the vehicle information table 44 shown in FIG. 2A and the product number information table 46 shown in FIG. 2B, and is used for specifying the vehicle. Is done. The vehicle information table 44 includes, for example, items such as a vehicle type code 44A, an engine type code 44B, a year type code 44C, a mission 44D, and a vehicle name 44E. The product number information table 46 is a collection of product number codes 46A. The failure phenomenon-specific failure search database 48 is an accumulation of the phenomenon-specific failure information table 50 shown in FIG. 2C, and is used to identify a failure location. The phenomenon-specific defect information table 50 includes, for example, a phenomenon-specific defect code 50A and an inspection item 50B.

  The product information database 52 is a collection of product information tables 54 shown in FIG. 2D, and is component information provided to the terminal 10a as necessary. The product information table 54 includes items such as a product code 54A, image information 54B, and product description 54C. The failure information database 56 is an accumulation of the failure information table 58 shown in FIG. 2E. Based on the repair procedure for each vehicle, the failure location and inspection location are determined from the failure code 58A for the terminal 10a. Used to display The failure information table 58 includes, for example, a failure code 58A, a failure location 58B, image information 58C, an inspection location 58D, and the like.

  FIG. 3 shows record structures of various files in the storage device 40. First, the failure information file 60 is used to identify a failure occurrence frequency that is a cause of failure from the failure search database 48 by failure phenomenon. As shown in FIG. The vehicle type code 60A, the failure code 60B, and the count number 60C are included. Also, the response history information based on the response information from the terminal 10a is reflected in the failure information file 60, and the failure occurrence classes are set in descending order of the cause of failure (for example, A, B, C, D). In ascending order) and reflected in the failure information database 56. The customer information file 62 is a collection of information of customers (users 10 such as maintenance shops in this embodiment). For example, as shown in FIG. 3B, for example, a customer code 62A, a company name 62B, It consists of an affiliation 62C, a name 62D, an address 62E,. The sales record file 64 stores sales record information based on purchase information. For example, as shown in FIG. 3C, for example, a product code 64A, an inquiry number 64B, an order number 64C,.・ It is composed of.

The various programs in the server computer 30 described above refer to various databases and files in the storage device 40 and perform the following processing according to instructions from the information processing unit 32.
(1) Vehicle information setting program 34... Vehicle identification information (vehicle type, engine type, year, product number, etc.) is acquired from the terminal 10a, and a vehicle information table in the vehicle information (product number) database 42 is obtained. 44 or the product number table 46, the vehicle corresponding to the acquired vehicle specifying information is specified.
(2) Failure content setting program 36... Refers to the failure search database 48 for each failure phenomenon, narrows down inspection items in accordance with the specified vehicle failure phenomenon, and displays an inquiry screen for identifying the failure location. Is transmitted to the terminal 10a.
(3) Parts information display program 38... Processing of failure location information display 38A, product information display 38B, etc. regarding the specified failure location with respect to the terminal 10a with reference to the product information database 52 and failure information database 56 I do.
(4) Aggregation program 39... Aggregate answer history information based on the answer information acquired from the terminal 10a and sales performance information based on the purchase information, and store the information for each vehicle information in the failure information file 60. Generate an answer record master by defect phenomenon.

  Next, the operation of the present embodiment will be described with reference to FIGS. FIG. 5 is a flowchart showing an outline of information providing processing on the server computer 30 side. Note that the processing described below is realized by the server computer 30 described above referring to various databases and files in the storage device 40 and performing desired processing. On the terminal 10a side, the operator of the terminal 10a inputs and selects information by operating the input unit 12a according to the guidance on the screen displayed on the display unit 14a. The same applies to the other terminals 10b, 10c,. First, the user 10 requested for maintenance or inspection by a vehicle owner or the like accesses the server computer 30 of the service company 100 via the Internet 20 using the terminal 10a or the like. On the server computer 30 side accessed from the terminal 10a, by executing the vehicle information setting program 34, a screen for prompting the terminal 10a to input vehicle information or a product number (vehicle specifying information) is transmitted. And if the information for vehicle specification is acquired from the terminal 10a, the vehicle corresponding to the acquired information will be specified with reference to the vehicle information (article number) database 42 (step S10). When the vehicle is specified, the failure content setting program 36 is executed to refer to the failure search database 48 for each failure phenomenon, and an inquiry for specifying the failure location for each specified vehicle is started (step S12). It is assumed that the inquiry is performed on the basis of an answer inputted or selected in response to an inquiry screen transmitted from the server computer 30 to the terminal 10a.

  When an inquiry process regarding startability is selected by the terminal 10a on the selection screen for inquiry contents (Yes in step S14), the process proceeds to an inquiry process regarding startability described later (step S30), and if the problem is solved (step S22). If yes, the process returns to step S14 to select a desired inquiry process. Alternatively, when the inquiry regarding startability is not selected (No in step S14) and the inquiry process regarding instability of idle is selected (Yes in step S16), the process proceeds to the interview process regarding idol (step S130) described later. If the problem is solved, the process is terminated, and when an inquiry process related to another item is performed, the process returns to step S14 to select another inquiry process. Alternatively, when an inquiry regarding drivability is not selected (No at Steps S14 and S16) and an inquiry regarding drivability is selected (Yes at Step S18), an inquiry process regarding drivability described later ( The process proceeds to step S150), and if the problem is solved, the process ends. If an inquiry regarding other items is performed, the process returns to step S14. Alternatively, if an inquiry regarding stoppage is selected (No in Steps S14, S16, and S18) without selecting an inquiry regarding the startability, idle instability, and drivability (No in Steps S14, S16, and S18), it will be described later. The process proceeds to the inquiry process (step S180) relating to the stopping property, and if the problem is solved, the process is terminated. If an inquiry relating to other items is to be performed, the process returns to step S14. Hereinafter, the flow of each inquiry process described above will be described in order.

  (1) Interrogation process regarding startability (step S30)... When the interrogation regarding startability is selected in step S14, the interrogation process regarding startability shown in FIG. 6 is started. FIG. 6 is a flowchart illustrating an example of an inquiry process regarding startability. First, when the start itself is impossible (Yes in step S32), the process proceeds to a start impossible / interrogation process (step S40) described later. On the other hand, if the engine can be started but is defective (Yes in step S34), the process proceeds to a starting defect / inquiry process (step S90) described later. If there is no problem in startability and the inquiry process related to startability is to be ended (Yes in step S36), the other inquiry processes shown in FIG. 5 are performed as necessary, and then all the inquiry processes are ended. . When the inquiry process regarding the startability is performed again (No in step S36), the process returns to step S32.

  <Unable to start / interview process (step S40)>... If the start is impossible (Yes in step S32), the unstartable / interrogation process is performed. FIG. 7 is a flowchart illustrating an example of the start failure / interrogation process. As shown in FIG. 7, first, when there is an abnormality in the inspection of the power source and the ignition switch (step S42) (No in step S44), information on the parts is displayed (step S46). In addition, in the present embodiment, for example, the part name (for example, ISC servo, airflow sensor, water temperature sensor, etc.) and the corresponding part may be displayed. The model number is displayed. When there are a large number of component names, the component names are displayed, and the model number of the component selected by the terminal 10a is displayed. Such display processing is realized by the component information display program 38 extracting relevant information from the product information database 52 and the failure information database 56 and transmitting the data in a format that can be viewed on the display unit 14a of the terminal 10a. The At this time, information is displayed in the order of the frequency of occurrence of failures, in the order of the repair record, and hence in the sales record. It should be noted that the display of information regarding parts is the same as that exemplified here even during various types of inquiry processing described later.

  Next, when it is answered that there is no abnormality in the power supply and ignition switch inspection (Yes in step S44), the process proceeds to ECU ground inspection (step S48), and when abnormality is recognized (No in step S50), A ground correction is instructed (step S52). On the other hand, if no abnormality is recognized in the ECU ground (Yes in step S50), the process proceeds to the fuel pump inspection (step S54), and if an answer indicating an abnormality is obtained (No in step S56), the corresponding part. The information regarding is displayed (step S58). If the fuel pump check indicates that there is no abnormality (Yes in step S56), the process proceeds to the cam angle / crank angle sensor check (step S60), and if there is a response indicating abnormality (No in step S62). ) Displays information related to the relevant part (step S64). On the other hand, if there is a reply that there is no abnormality when checking the cam angle and crank angle sensors (Yes in step S62), the process proceeds to an ECU inquiry process (step S70) described later.

  <ECU Interview Processing (Step S70)> ... Interrogation processing related to the ECU is performed according to the procedure shown in the flowchart of FIG. First, a question about the diag code check (step S72) is made, and if there is an answer that there is an abnormality (No in step S74), the part information display program 38 refers to the product information database 52 and relates to the relevant ECU. The component information is searched, and the obtained information is embedded in the information providing page (step S78) and transmitted to the terminal 10a (step S80). On the other hand, when it is answered that there is no abnormality in the diag code check (Yes in step S74), a question about the inspection of the sensor power supply voltage is made. If there is a reply that there is an abnormality (No in step S82), the step S78 is performed. And it progresses to S80 and provides ECU-related product information to the terminal 10a. Further, when it is answered that there is no abnormality even in the inspection of the sensor power supply voltage (Yes in step S82), it is considered that the quality of the ECU is unknown. 10a (step S84), and the process ends.

  Here, in the case where the ECU trouble part cannot be identified by the ECU inquiry process described above (Yes in step S82) or when the ECU needs to be repaired, the user 10 sends the ECU to the service company 100. The service company checks and repairs the ECU. FIG. 4 shows a simulator connection configuration and an input / output signal block configuration used when the service company 100 requires inspection and repair of the ECU. As shown in FIG. 4A, the service company 100 includes a terminal 70 and a simulator 72, and an ECU 74 provided from the user 10 is connected to the simulator 72 by an appropriate means such as a cable 78. . The terminal 70 and the simulator 72 are also connected by a cable 76 such as a LAN or an optical fiber. The simulator 72 performs voltage application, simulation waveform application, and the like via the control bus 73 according to a command from the terminal 70, and measures the output of the voltage, waveform, and the like from the ECU 74 in real time. The input / output signals between the simulator 72 and the ECU 74 are, for example, a crank angle signal 80A, a cam angle signal 80B, a knock sensor signal 80C, a water temperature sensor signal 80D, an intake pressure sensor signal 80E, a throttle signal 80F,. .., ignition signal 80L, injection signal 80M, sensor supply voltage 80N,..., Backup power supply 80S, ignition power supply 80T, starter signal 80U,. When the trouble of the ECU 74 is identified by the inspection by the simulator 72 and repair / regeneration is possible, the ECU 74 is returned to the user 10 after correction / regeneration and repair / regeneration is impossible. Then, services such as checking the presence or absence of inventory in the ECU and selling related products are performed for the user 10.

  <Starting failure / interrogation process (step S90)> ... On the other hand, if the starting failure occurs such as when an engine stall occurs only at the first explosion or the starting time is long (Yes in step S34), the starting failure / interrogation process is performed. . FIG. 9 is a flowchart illustrating an example of the startup failure inquiry process. First, a question about fuel pump check is made (step S92), and if there is an answer that there is an abnormality (No in step S94), information about the part is displayed (step S96). If there is an answer that there is no abnormality in the fuel pump check (Yes in step S94), a question about the injector check is made (step S98). Here, if there is an answer that abnormality is recognized (No in step S100), information on the corresponding part is displayed (step S102). If it is answered that there is no abnormality in the injector inspection (Yes in step S100), the process proceeds to the question for the ignition switch (starter) inspection (step S104). If there is an answer that there is an abnormality (No in step S106), the relevant parts are related. Information is displayed (step S108). On the contrary, if there is an answer that there is no abnormality (Yes in step S106), the process proceeds to a question regarding ISC servo check. Here, if there is an answer in the ISC servo check that there is an abnormality (No in step S112), information on the corresponding part is displayed (step S114), and if there is no abnormality (Yes in step S112), the fuel pressure check is related. Proceed to the question (step S116). If there is an answer at the fuel pressure check that there is an abnormality (No in step S118), information on the part is displayed (step S120), and if there is no abnormality (Yes in step S118), the cam angle and crank angle sensor check (Step S122). If there is an answer that there is an abnormality (No in step S124), information on the component is displayed (step S126), and if there is an answer that there is no abnormality, the process proceeds to the ECU inquiry process (step S70) described above.

  (2) Interview process regarding idol (step S130)... When the interrogation regarding idol is selected in step S16, the interrogation process regarding idol is started as shown in FIG. First, an inquiry is made as to whether or not it is unstable (step S132), and if it is answered that it is unstable (Yes in step S132), an inquiry process regarding idle instability (step S134) is performed. On the other hand, if there is an answer that is not unstable (No in step S132), the process proceeds to a question regarding inappropriate rotation, and if there is an answer that the rotation is inappropriate (Yes in step S136), idle It progresses to the inquiry process (step S138) regarding rotation improperness. If there is an answer that the rotation is not inappropriate (No in step S136), the process proceeds to the question regarding the persistence failure. Here, if there is an answer that the sustainability is poor (Yes in Step S140), an inquiry process (Step S142) related to the idle sustainability is performed, but if an answer of good sustainability is obtained (No in Step S140). ), If necessary, the process returns to S132 and repeats the inquiry (No in Step S144) or proceeds to the end as it is (Yes in Step S144). In addition, after the inquiry process regarding such an idle, after performing the other inquiry process shown in FIG. 5 as needed, all the inquiry processes are complete | finished.

  (3) Interrogation process regarding drivability (step S150)... When the interrogation regarding drivability is selected in step S18, the interrogation process regarding drivability as shown in FIG. 11 is started. First, a question about the presence or absence of breathing is performed. If there is a reply that there is a breath (Yes in step S152), an inquiry process regarding breathing is performed (step S154). (No in step S152), the process proceeds to a question regarding acceleration failure (step S156). Here, if there is a response that acceleration failure is recognized (Yes in step S156), an inquiry process regarding acceleration failure is performed (step S158), and if there is a response that acceleration failure is not recognized (No in step S156), A question regarding tackiness is made (step S160). Here, if there is an answer that there is tackiness (Yes in step S160), an inquiry process relating to rattling is performed (step S162), and if there is no answer (No in step S160), a question regarding the presence or absence of shock is given. Proceed (step S164). If there is a shock (Yes in step S164), an inquiry process regarding shock (step S166) is performed, and if there is no response (No in step S164), the process proceeds to a question regarding surge (step S168). If there is a response with a surge (Yes in step S168), an inquiry process regarding surge is performed (step S170), and if there is no response (No in step S168), a question regarding the presence or absence of knocking is performed. (Step S172). When it is answered that knocking is present (Yes in step S172), an inquiry process regarding knocking is performed (step S174), and it is answered that there is no knocking (No in step S172), and the inquiry process regarding drivability is terminated (step S176). (Yes), the other inquiry processes shown in FIG. 5 are performed as necessary, and all the inquiry processes are terminated. When the inquiry process regarding drivability is performed again (No in step S176), the process returns to step S152.

  (4) Interrogation process related to stoppage (step S180)... When an inquiry about stoppage is selected in step S20, an inquiry process related to stoppage is started as shown in FIG. First, a question is asked about the presence or absence of a run-on, and if it is answered that there is a run-on (Yes in step S182), the process proceeds to a question relating to injector inspection (step S184), and if it is answered that there is an abnormality (in step S186) No) displays information about the component (step S190). On the other hand, when there is no abnormality in the injector inspection (Yes in step S186), or when it is answered that there is no run-on (No in step S182), an inquiry is made as to whether or not to execute the ECU inquiry process. If execution is selected (Yes in step S192), the process proceeds to the ECU inquiry process (step S70) described above. In addition, when the ECU inquiry process is not selected (No in step S192) and the inquiry process regarding stoppage is terminated (Yes in step S194), the other inquiry processes shown in FIG. 5 are performed as necessary. After that, all the inquiry processes are terminated. When the inquiry process regarding the stoppage is performed again (No in step S194), the process returns to step S182.

Thus, according to the first embodiment, there are the following effects.
(1) The user 10 accesses the server computer 30 using the terminal 10a, inputs vehicle specifying information, and answers the inquiry displayed by the server computer 30. It is possible to easily identify the defective part and to obtain appropriate part information and repair information regarding the defective part. For this reason, it becomes possible to greatly improve the efficiency of vehicle repair and maintenance. In particular, information can be provided with high reliability by providing information in descending order of occurrence frequency of defective portions.
(2) When it is impossible to judge whether or not the ECU 74 is good or repair is required, the ECU 74 is sent to the service company 100, and the service company 100 side uses the simulator 72 to check the defective part of the ECU 74. If possible, repair and recycle and use the ECU 74 again. For this reason, it is possible to reuse the ECU 74 that has been discarded in the past, which can contribute to the reuse and effective utilization of resources.
(3) The server computer 30 stores the reply information obtained from the terminal 10a in the storage device 40, so that when the ECU 74 needs to be inspected or repaired, the reply information is used to make the ECU 74 In addition to improving the efficiency of work related to inspections and repairs, it is also possible to apply it to verification of repair points.
(4) Since it is decided to use the Internet 20 to identify faulty parts and provide information on parts related to the faulty parts to the terminal 10a on the user side, it is highly convenient for an unspecified number of users and provides customer service. Is also greatly improved.

In addition, this invention is not limited to the Example mentioned above, A various change can be added in the range which does not deviate from the summary of this invention. For example, the following are also included.
(1) The system configuration shown in the above embodiment is an example, and may be appropriately changed so as to achieve the same effect. For example, the terminal 10a used on the user 10 side is any type of personal computer, such as a PDA, as long as it has a function capable of transmitting and receiving information and displaying via the Internet 20. Also good.
(2) The record structure of the database and file shown in the above embodiment is also an example, and may be changed as necessary.
(3) In the above-described embodiment, the user 10 has the terminal 10a, and the service company 100 has the server computer 30, the storage device 40, and the simulator 72. However, this is also an example. It may be held by an institution or organization.
(4) The inquiry process shown in the above embodiment is an example, and may be appropriately changed as necessary.
(5) The present invention can be applied to all networks other than the Internet 20.

  According to the present invention, using a network, a vehicle is identified based on vehicle identification information received from a requesting terminal, an inquiry is performed according to a failure or malfunction phenomenon of the vehicle, and a malfunction location is identified. Since the part information relating to the specified failure location is provided to the requesting terminal, it is possible to improve the efficiency of work related to vehicle maintenance and repair. In particular, in a vehicle equipped with an electronic control component (ECU), since it can be determined whether or not the defective portion is in the electronic control component, it is possible to promote the reuse of the ECU by repair or regeneration.

It is a block diagram which shows the system configuration | structure of Example 1 of this invention. It is a figure which shows the record structure of the database in the memory | storage device by the side of the server computer of the said Example 1. FIG. It is a figure which shows the record structure of the file in the memory | storage device by the side of the server computer of the said Example 1. FIG. It is a figure which shows the simulator used by the server computer side of the said Example 1, (A) is a schematic diagram which shows the mode of connection of a simulator, (B) is a block diagram which shows the main input / output signals of the said simulator . It is a flowchart which shows the outline | summary of the information provision process by the side of the server computer in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the startability in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the start impossible in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding EUC in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the starting failure in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the idol in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the drivability in the said Example 1. FIG. It is a flowchart which shows an example of the inquiry process regarding the stop property in the said Example 1. FIG.

Explanation of symbols

10: Users 10a, 10b, 10c: Terminals 12a, 12b, 12c: Input units 14a, 14b, 14c: Display unit 20: Internet 30: Server computer 32: Information processing unit 34: Vehicle information setting program 36: Problem content setting program Program 38: Parts information display program 38A: Fault location information display 38B: Product information display 39: Total program 40: Storage device 42: Vehicle information (product number) database 44: Vehicle information table 44A: Vehicle model code 44B: Engine model code 44C : Model code 44D: Mission 44E: Vehicle name 46: Product number information table 46A: Product number code 48: Failure search database by failure phenomenon 50: Failure information table by phenomenon 50A: Failure code by phenomenon 50B: Inspection item 52: Product information database 54: Product information table 54A: Product code 54B: Image information 54C: Product description 56: Failure information database 58: Failure information table 58A: Failure code 58B: Failure location 58C: Image information 58D: Inspection location 60: Failure information file 60A : Vehicle model code 60B: Failure code 60C: Count number 62: Customer information file 62A: Customer code 62B: Company name 62C: Affiliation 62D: Name 62E: Address 64: Sales result file 64A: Product code 64B: Number of inquiries 64C: Order received Number 70: Terminal 72: Simulator 73: Control bus 74: ECU
76, 78: Cable 80A: Crank angle signal 80B: Cam angle signal 80C: Knock sensor signal 80D: Water temperature sensor signal 80E: Intake pressure sensor signal 80F: Throttle signal 80L: Ignition signal 80M: Injection signal 80N: Sensor supply voltage 80S: Backup power supply 80T: Ignition power supply 80U: Starter signal 100: Service company

Claims (6)

A method for searching for a faulty part of a vehicle equipped with an electronically controlled component and a method for providing information on a vehicle-related part that provides information on the faulty part to a requesting terminal through a network,
Identifying a vehicle based on the vehicle identifying information acquired from the requesting terminal;
Performing an inquiry regarding the specified vehicle failure phenomenon to the requesting terminal, and identifying the failure location based on an answer from the requesting terminal to the inquiry;
Transmitting information related to the identified defective part to the requesting terminal;
The information provision method of the vehicle related components characterized by including these. The response history information based on the response information from the requesting terminal for the inquiry and the sales performance information based on the purchase information of the vehicle parts are tabulated.
2. The method for providing information on vehicle-related parts according to claim 1, wherein the information on the parts is transmitted to the requesting terminal in the order in which the occurrence frequency of defects or the sales record is high from the counting result. . An information providing server for vehicle-related parts that provides a method for searching for a defective part of a vehicle equipped with electronically controlled parts and information on the defective part to a requesting terminal through a network,
Vehicle information database in which vehicle information is accumulated, failure search database by failure phenomenon in which information for narrowing down inspection items for each vehicle is accumulated, failure information database in which vehicle inspection items and inspection points are accumulated, and information on vehicle-related parts With a parts information database
Vehicle specifying means for acquiring vehicle specifying information from the requesting terminal, referring to the vehicle information database, and specifying a vehicle corresponding to the acquired vehicle specifying information;
A failure location specifying means for referring to the failure search database for each failure phenomenon, performing an inquiry to the requesting terminal for narrowing down inspection items of the specified vehicle, and specifying the failure location;
Component information providing means for referring to the failure information database or the component information database, extracting information related to the component of the identified defective part, and transmitting the information to the requesting terminal;
An information providing server for vehicle-related parts, comprising: Aggregating means for totaling response history information based on response information from the requesting terminal for the inquiry and sales performance information based on purchase information of the vehicle-related parts, and generating a response history master by defect phenomenon for each vehicle information,
With
The component information providing means provides the component information to the requesting terminal in the order in which the failure occurrence frequency is high or the sales record is high from the failure event-specific response record master. 3. An information providing server for vehicle-related parts according to 3.   5. The vehicle-related component information providing server according to claim 3, further comprising: a simulation device for the electronic control component; and a terminal connectable to the simulation device. An information providing server for vehicle-related parts according to any one of claims 3 to 5,
A number of requesting terminals capable of exchanging information with the information providing server via a network;
A system for providing information on vehicle-related parts, comprising:

Images