WO2019064813A1 - 車両診断装置、車両診断システム及び車両診断プログラム - Google Patents

車両診断装置、車両診断システム及び車両診断プログラム Download PDF

Info

Publication number
WO2019064813A1
WO2019064813A1 PCT/JP2018/026027 JP2018026027W WO2019064813A1 WO 2019064813 A1 WO2019064813 A1 WO 2019064813A1 JP 2018026027 W JP2018026027 W JP 2018026027W WO 2019064813 A1 WO2019064813 A1 WO 2019064813A1
Authority
WO
WIPO (PCT)
Prior art keywords
diagnosis
diagnostic
application
scenario
unit
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2018/026027
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
卓也 河▲崎▼
雄三 原田
和明 早川
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Denso Corp
Original Assignee
Denso Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Denso Corp filed Critical Denso Corp
Priority to DE112018004312.6T priority Critical patent/DE112018004312B4/de
Priority to CN201880062027.XA priority patent/CN111133289B/zh
Publication of WO2019064813A1 publication Critical patent/WO2019064813A1/ja
Priority to US16/821,844 priority patent/US11541899B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
    • B60W50/0205—Diagnosing or detecting failures; Failure detection models
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01M—TESTING STATIC OR DYNAMIC BALANCE OF MACHINES OR STRUCTURES; TESTING OF STRUCTURES OR APPARATUS, NOT OTHERWISE PROVIDED FOR
    • G01M17/00—Testing of vehicles
    • G01M17/007—Wheeled or endless-tracked vehicles
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
    • B60W50/0225—Failure correction strategy
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W20/00—Control systems specially adapted for hybrid vehicles
    • B60W20/50—Control strategies for responding to system failures, e.g. for fault diagnosis, failsafe operation or limp mode
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W50/00—Details of control systems for road vehicle drive control not related to the control of a particular sub-unit, e.g. process diagnostic or vehicle driver interfaces
    • B60W50/02—Ensuring safety in case of control system failures, e.g. by diagnosing, circumventing or fixing failures
    • B60W50/029—Adapting to failures or work around with other constraints, e.g. circumvention by avoiding use of failed parts
    • B60W2050/0292—Fail-safe or redundant systems, e.g. limp-home or backup systems

Definitions

  • the present disclosure relates to a vehicle diagnostic device, a vehicle diagnostic system, and a vehicle diagnostic program.
  • a diagnosis application is executed, diagnosis is performed according to a diagnosis scenario defined by the diagnosis application, and a defect is detected or detected. Treat (see, for example, Patent Document 1).
  • the present disclosure relates to a vehicle diagnostic device, a vehicle diagnostic system, and a vehicle diagnostic system capable of appropriately performing diagnosis by repeatedly performing diagnosis according to a new diagnostic scenario when the diagnostic scenario used for diagnosis is not appropriate.
  • the purpose is to provide a program.
  • the diagnosis unit carries out diagnosis of the diagnosis target according to the diagnosis scenario defined in the diagnosis application.
  • the diagnosis scenario determination unit determines whether the diagnosis scenario used for diagnosis by the diagnosis unit is appropriate. When the diagnostic scenario determination unit determines that the diagnostic scenario used in the current diagnosis is not appropriate, the diagnostic unit performs diagnosis in accordance with the diagnostic scenario defined by the new diagnostic application different from the current diagnostic application. Do. When the diagnosis scenario used for diagnosis is not appropriate, diagnosis can be appropriately performed by repeatedly performing diagnosis according to a new diagnosis scenario.
  • FIG. 1 is a functional block diagram illustrating one embodiment
  • FIG. 2 is a diagram showing a diagnostic result database
  • FIG. 3 is a flowchart (part 1) showing a diagnosis process
  • FIG. 4 is a flowchart (part 2) showing the diagnosis process.
  • the vehicle diagnostic system 1 includes an electronic control unit (ECU: Electronic Control Unit) 2 (hereinafter referred to as a vehicle management ECU, corresponding to a vehicle diagnostic device) for vehicle management mounted in the vehicle, and a communication network side.
  • the server 3 is included.
  • the vehicle management ECU 2 is connected to the communication bus 4 in the vehicle, and the communication buses 4 are connected to the ECUs 5 and 6 (corresponding to diagnosis targets) and the in-vehicle communication device 7.
  • the vehicle management ECU 2 has a function of managing the ECUs 5 and 6, and has a function of diagnosing the ECUs 5 and 6 as one of them.
  • the communication bus 4 is, for example, a multimedia communication bus, a power train communication bus, a body communication bus, etc., and can be controller area network (CAN) (registered trademark), LIN (local interconnect network), CXPI (Clock Extension) Peripheral Interface (registered trademark), FlexRay (registered trademark), Media Oriented Systems Transport (MOST) (registered trademark), and the like.
  • CAN controller area network
  • LIN local interconnect network
  • CXPI Chip Extension
  • Peripheral Interface registered trademark
  • FlexRay registered trademark
  • MOST Media Oriented Systems Transport
  • the ECUs 5 and 6 are, for example, an engine ECU that controls an engine, a transmission ECU that controls an automatic transmission, a brake ECU that controls a brake, a steering ECU that controls steering, a navigation ECU that controls navigation, and an electronic ETC ECU that performs communication control with toll collection system, door ECU that controls lock / unlock of door, meter ECU that controls display of meter, air conditioner ECU that controls air conditioner, window ECU that controls opening / closing of window It is.
  • the number of communication buses and the number of ECUs to be managed by the vehicle management ECU 2 are not limited to the illustrated configuration.
  • the on-vehicle communication device 7 transmits / receives data to / from the server 3 or the user terminal 8 when wirelessly connected to the server 3 or the user terminal 8 portable by the user via the wide area communication network.
  • the user terminal 8 is, for example, a smartphone or a tablet terminal.
  • the vehicle management ECU 2 has a microcomputer 9 (hereinafter referred to as a microcomputer).
  • the microcomputer 9 has a CPU, a RAM, a ROM, an I / O port, etc., and supports a computer program by executing a computer program (including a vehicle diagnostic program) stored in a non-transitional tangible recording medium. Processing to control the overall operation of the vehicle management ECU 2.
  • the microcomputer 9 has a diagnosis application storage unit 9a, a diagnosis unit 9b, a diagnosis scenario determination unit 9c, a diagnosis application request unit 9d, and a diagnosis application acquisition unit 9e as functions related to diagnosis realized by software or the like. And a diagnosis result data notification unit 9f.
  • the diagnosis includes determining and detecting whether or not a failure has occurred, analyzing the detected failure, and implementing measures for the analyzed failure.
  • the diagnosis application storage unit 9a stores, as a diagnosis application, a periodic diagnosis application, a probe information collection application, a specific pattern collection application, a follow-up observation application, a detailed diagnosis application, and a cause identification diagnosis application.
  • the periodic diagnosis application is an application that periodically acquires a diagnostic code from the ECUs 5 and 6 and analyzes and diagnoses the acquired diagnostic code.
  • the probe information collection application is an application for collecting probe information to be utilized when the periodic diagnosis is not appropriate.
  • the unique pattern collection application is an application that collects unique patterns, such as a sudden change in numerical value. In this case, the numerical value is, for example, a numerical value specified by a signal acquired from the vehicle side, and is an engine rotational speed, temperature, pressure or the like.
  • the follow-up observation application is an application for observing the progress after the diagnosis unit 9b performs periodic diagnosis, detailed diagnosis, and cause-specific diagnosis as described later.
  • the detailed diagnosis application is an application that diagnoses the details of the defect when the diagnosis unit 9b performs periodic diagnosis as described later, but the treatment for the detected defect is not appropriate.
  • the cause identifying diagnostic application is an application that diagnoses the undetected cause of the defect when the diagnosing unit 9b performs the periodic diagnosis as described later, but the defect is not detected.
  • the configuration in which the diagnostic application storage unit 9a is provided inside the vehicle management ECU 2 is exemplified, but the configuration in which the diagnostic application storage unit 9a is provided outside the vehicle management ECU 2 may be used. . That is, for example, another ECU connected to the vehicle management ECU 2 via the communication bus 4 or a dedicated storage device is provided with a storage unit corresponding to the diagnostic application storage unit 9a, and the other ECU or the dedicated storage device is provided.
  • the microcomputer 9 may be configured to acquire the stored diagnostic applications one by one. Further, a plurality of storage units corresponding to the diagnostic application storage unit 9a may be provided, and the diagnostic applications may be dispersed and stored in the vehicle.
  • the diagnosis unit 9b executes a diagnosis application stored in the diagnosis application storage unit 9a, and diagnoses the ECUs 5 and 6 to be diagnosed according to a diagnosis scenario defined by the diagnosis application. That is, when the diagnosis unit 9 b executes the diagnosis application, the diagnosis unit 9 b diagnoses the ECUs 5 and 6 by transmitting and receiving data related to the diagnosis with the ECUs 5 and 6 as the diagnosis target via the communication bus 4.
  • the diagnosis scenario determination unit 9c determines whether the diagnosis scenario used for diagnosis by the diagnosis unit 9b is appropriate. In this case, the diagnostic scenario determination unit 9c compares the operation log of the ECUs 5 and 6 after the diagnosis unit 9b performs the diagnosis with the normal operation log defined in advance, when the diagnosis unit 9b performs the diagnosis. It is determined whether the diagnostic scenario is appropriate by comparing the generated diagnostic execution data with the normal diagnostic execution data defined in advance, determining the predetermined operation by the user after the diagnostic unit 9b performs the diagnosis, etc. Do. With the predetermined operation by the user, for example, the user judges that the diagnostic scenario in the user terminal 8 was appropriate and operates the "appropriate key” or operates the "inappropriate key” judging that the diagnostic scenario is inappropriate. It is.
  • the diagnosis scenario determination unit 9c digitizes the coincidence between the operation log of the ECUs 5 and 6 after the diagnosis by the diagnosis unit 9b and the normal operation log, and if the numerical value indicating the coincidence is within the predetermined range, Identify the diagnostic scenario as appropriate, and if the numerical value indicating the degree of coincidence is out of the predetermined range, identify the diagnostic scenario as inappropriate. Further, the diagnosis scenario determination unit 9c, for example, digitizes the degree of coincidence between the diagnosis execution data generated when the diagnosis unit 9b carries out the diagnosis and the normal diagnosis execution data, and the numerical value indicating the degree of coincidence falls within a predetermined range.
  • the diagnostic scenario is identified as appropriate and the numerical value indicating the degree of coincidence is out of the predetermined range, the diagnostic scenario is identified as not appropriate.
  • the diagnosis scenario determination unit 9c determines that the diagnosis scenario is appropriate and the user determines that the user terminal is a user terminal.
  • the diagnostic scenario is specified as being appropriate.
  • the diagnostic scenario is not appropriate Identify.
  • the user judges whether the diagnosis result is normal for example, the user judges that the diagnosis result is normal if the diagnosis result is not uncomfortable, and the diagnosis result is not normal if some discomfort is felt It is assumed that the user makes a decision.
  • the diagnostic application request unit 9d transmits a diagnostic application request command to the in-vehicle communication device 7 via the communication bus 4 when an event of a diagnostic application request occurs due to, for example, a vehicle diagnostic program execution instruction, user operation, or self judgment.
  • the in-vehicle communication device 7 transmits a diagnostic application request signal to the server 3, and the diagnostic application is requested to the server 3.
  • the diagnostic application acquisition unit 9 e receives the diagnostic application transmitted from the server 3 by the in-vehicle communication device 7, and receives the diagnostic application from the in-vehicle communication device 7 via the communication bus 4, whereby the diagnostic application is received by the server 3.
  • the diagnosis result data notification unit 9 f transmits a diagnosis result data notification command to the in-vehicle communication device 7 via the communication bus 4 to transmit diagnosis result data including the diagnosis result from the in-vehicle communication device 7 to the server 3 or the user terminal 8. It is transmitted, and the diagnosis result data is notified to the server 3 and the user terminal 8.
  • the server 3 has a microcomputer 10 and a diagnosis result database 11.
  • the microcomputer 10 has a CPU, a RAM, a ROM, an I / O port, and the like, and executes a computer program stored in a non-transitional tangible recording medium to execute processing corresponding to the computer program. Control the overall operation of 3.
  • the microcomputer 10 has a diagnostic application storage unit 10 a and a data management unit 10 b as functions related to diagnosis realized by software or the like.
  • the diagnosis application storage unit 10a stores a follow-up observation application, a detailed diagnosis application, and a cause identification diagnosis application.
  • the microcomputer 10 receives the diagnostic application request signal transmitted from the in-vehicle communication device 7, the microcomputer 10 transmits the diagnostic application specified by the diagnostic application request signal to the in-vehicle communication device 7. That is, among the diagnosis applications stored in the diagnosis application storage unit 9a shown in FIG. 1, the follow-up observation application, the detail diagnosis application, and the cause identification diagnosis application are not incorporated at the manufacturing stage of the vehicle management ECU 2 and are shipped as products.
  • the diagnostic application may be transmitted from the server 3 to the vehicle management ECU 2 later, or may be a diagnostic application incorporated at the manufacturing stage of the vehicle management ECU 2.
  • the server 3 is configured to store a periodic diagnostic application, a probe information collection application, and a specific pattern collection application, periodicity of the diagnostic applications stored in the diagnostic application storage unit 9a shown in FIG.
  • the diagnostic application, the probe information collection application, and the specific pattern collection application may not be incorporated at the manufacturing stage of the vehicle management ECU 2 and may be a diagnostic application transmitted from the server 3 to the vehicle management ECU 2 after product shipment. It may be a diagnostic application incorporated at the manufacturing stage of the management ECU 2. Which diagnostic application is to be incorporated at the manufacturing stage of the vehicle management ECU 2 and whether or not to be managed by the server 3 may be designed in any way.
  • a diagnostic application that has been useful for the diagnosis target based on past results may be incorporated at the manufacturing stage of the vehicle management ECU 2 or the like.
  • priority is given to diagnostic applications that have been useful for the diagnosis target based on past results, and vehicle management is given priority for high priority diagnostic applications. It may be incorporated at the manufacturing stage of the ECU 2 or the like.
  • the data management unit 10 b When the data management unit 10 b receives the diagnosis result data transmitted from the in-vehicle communication device 7, the data management unit 10 b stores the diagnosis result specified by the diagnosis result data in the diagnosis result database 11 as a history.
  • the diagnosis result data transmitted from the in-vehicle communication device 7 to the server 3 is a vehicle ID capable of specifying the vehicle type, grade, manufacturing time etc. of the vehicle, and diagnosis capable of specifying the time when the diagnosis was performed.
  • the timing, the diagnostic application used for diagnosis, and the information of the diagnostic result performed according to the diagnostic scenario prescribed in the diagnostic application are included.
  • the user terminal 8 When the user terminal 8 receives the diagnosis result data transmitted from the in-vehicle communication device 7, the user terminal 8 displays and outputs the diagnosis result specified by the diagnosis result data. As the user terminal 8 displays and outputs the diagnostic result, the user can determine whether the diagnostic scenario is appropriate as described above.
  • the user terminal 8 may display and output the status before diagnosis, during diagnosis, after diagnosis, etc. by receiving status information from the in-vehicle communication device 7 before diagnosis, during diagnosis, after diagnosis, etc.
  • a periodic diagnosis application is used as a primary diagnosis application to be executed first, and a secondary diagnosis is executed when the primary diagnosis scenario defined in the primary diagnosis application is not appropriate.
  • the case of using the detailed diagnosis application and the cause identification diagnosis application as an application will be described.
  • the microcomputer 9 executes the periodic diagnosis application and performs periodic diagnosis according to the periodic diagnosis scenario defined by the periodic diagnosis application (S1, corresponding to the present diagnosis procedure) ).
  • the microcomputer 9 carries out a periodic diagnosis, it causes the in-vehicle communication device 7 to transmit diagnosis result data including the periodic diagnosis result to the server 3 or the user terminal 8, and the diagnosis result data of the periodic diagnosis is sent to the server 3 or the user The terminal 8 is notified.
  • the microcomputer 9 determines whether or not a defect is detected in the periodic diagnosis result by the periodic diagnosis (S2).
  • the microcomputer 9 determines that a defect is detected in the periodic diagnosis result (S2: YES), the detected defect is analyzed (S3), and it is determined whether or not a treatment method for the defect is specified (S4).
  • the microcomputer 9 may analyze the detected defect alone or in cooperation with the server 3. Further, the microcomputer 9 may cause the server 3 to analyze the defect alone by transmitting the content of the defect to the server 3.
  • the microcomputer 9 determines that the treatment method for the defect is specified by analyzing the defect (S4: YES), the microcomputer 9 performs the treatment for the defect according to the specified treatment method (S5).
  • the microcomputer 9 observes the progress after the treatment for the defect is performed (S6), and determines whether the periodic diagnosis scenario is appropriate (S7, corresponding to the diagnosis scenario determination procedure).
  • the microcomputer 9 compares the operation log of the ECUs 5 and 6 after the periodic diagnosis with the normal operation log defined in advance, and predefines the diagnostic execution data generated when the periodic diagnosis is performed. It is determined whether the periodic diagnosis scenario is appropriate by comparing it with the normal diagnosis execution data and determining the predetermined operation by the user after the periodic diagnosis.
  • the microcomputer 9 has a numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the periodic diagnosis is within a predetermined range, the diagnosis execution data generated when the periodic diagnosis is performed and the normal diagnosis
  • the user determines that the numerical value indicating the degree of coincidence with the implementation data is within a predetermined range or that the periodic diagnosis scenario is appropriate, operates the user terminal 8, and the appropriate confirmation signal transmitted from the user terminal 8 is in-vehicle communication If it is determined that the periodic diagnosis scenario is appropriate (S7: YES), the diagnosis process is terminated.
  • the microcomputer 9 performs the diagnosis execution data generated when the periodic diagnosis is performed, in which the numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the periodic diagnosis is outside the predetermined range.
  • the user determines that the numerical value indicating the degree of coincidence with the data for performing normal diagnosis is outside the predetermined range and that the periodic diagnosis scenario is not appropriate, operates the user terminal 8, and the inappropriate confirmation signal transmitted from the user terminal 8 If it is determined that the periodic diagnostic scenario is not appropriate because it is received by the in-vehicle communication device 7 (S7: NO), it is determined whether the problem can be re-analyzed (S8).
  • the microcomputer 9 determines that the problem can be reanalyzed (S8: YES)
  • the microcomputer 9 reanalyzes the problem (S9), and determines again whether or not the treatment method for the problem is specified (S10).
  • the microcomputer 9 determines that the defect can not be reanalyzed (S8: NO)
  • the microcomputer 9 specifies that the detected defect is dealt with by dealer repair (S11), and ends the diagnosis processing.
  • the microcomputer 9 determines that the treatment method for the defect is not specified (S4: NO), in this case as well, the defect is reanalyzed (S9) and it is determined again whether the treatment method for the defect is specified (S9) S10).
  • the microcomputer 9 determines that the treatment method for the defect is specified by re-analyzing the defect (S10: YES), the detailed diagnosis application is executed, and the detailed diagnosis is performed according to the detailed diagnosis scenario defined in the detailed diagnosis application. Conduct (S12, corresponding to a new diagnostic procedure). In this case, if the microcomputer 9 stores the detailed diagnostic application, the microcomputer 9 executes the stored detailed diagnostic application. If the microcomputer 9 stores a plurality of detailed diagnostic applications, the microcomputer 9 selects an optimal detailed diagnostic application from the plurality of detailed diagnostic applications according to the specified treatment method, and executes the selected detailed diagnostic application. On the other hand, when the microcomputer 9 does not store the detailed diagnostic application, the microcomputer 9 transmits a diagnostic application request signal from the in-vehicle communication device 7 to the server 3 to request the detailed diagnostic application from the server 3.
  • the server 3 When the server 3 receives the diagnostic application request signal, it uses the diagnostic result data received from the transmission source of the diagnostic application request signal to search the diagnostic result database 11 and select from among a plurality of detailed diagnostic applications. Select the detailed diagnosis app. That is, if the detailed diagnostic application differs depending on, for example, the vehicle type, grade, manufacturing time, etc., the server 3 specifies the vehicle type, grade, manufacturing time, etc. of the transmission source of the diagnostic application request signal by the vehicle ID. The detailed diagnosis application transmitted to the vehicle similar to the transmission source vehicle and whose diagnosis result is normal is identified, and the identified detailed diagnosis application is transmitted. The server 3 acquires probe information from, for example, the vehicle management ECU 2, analyzes the acquired probe information, creates a detailed diagnostic application, and selects the created detailed diagnostic application as an optimal detailed diagnostic application. good.
  • the microcomputer 9 receives the detailed diagnostic application transmitted from the server 3 by the in-vehicle communication device 7, and the diagnostic application is received from the in-vehicle communication device 7 via the communication bus 4 to obtain the detailed diagnostic application from the server 3. Acquire and execute the acquired detailed diagnostic app.
  • the microcomputer 9 executes the periodic diagnosis application as the primary diagnosis application and executes the periodic diagnosis, it determines that the periodic diagnosis scenario is not appropriate due to the incompatibility of the treatment for the detected defect, and the treatment for the defect
  • the detailed diagnosis application is executed as a secondary diagnosis application to carry out the detailed diagnosis.
  • the microcomputer 9 executes the detailed diagnosis application and carries out the detailed diagnosis
  • the microcomputer 9 observes the progress after the detailed diagnosis is carried out (S13), and determines whether or not the detailed diagnosis scenario is appropriate (S14).
  • the microcomputer 9 compares the operation log of the ECUs 5 and 6 after the detailed diagnosis with the normal operation log defined in advance, and predefines the diagnostic execution data generated when the detailed diagnosis is performed. Whether or not the detailed diagnosis scenario is appropriate is determined by comparing with the normal diagnosis execution data, and determining the predetermined operation by the user after the detailed diagnosis has been performed.
  • the microcomputer 9 has a numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the detailed diagnosis is within a predetermined range, and the diagnostic execution data generated when the detailed diagnosis is performed and the normal diagnosis
  • the user determines that the numerical value indicating the degree of coincidence with the implementation data is within a predetermined range or that the detailed diagnostic scenario is appropriate, and operates the user terminal 8, and the appropriate confirmation signal transmitted from the user terminal 8 indicates in-vehicle communication If it is determined that the detailed diagnosis scenario is appropriate (S14: YES), the diagnosis process is terminated.
  • the microcomputer 9 is a diagnostic execution data generated when the detailed diagnosis is performed, wherein the numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the detailed diagnosis is out of the predetermined range
  • An inappropriate confirmation signal transmitted from the user terminal 8 by operating the user terminal 8 by the user judging that the numerical value indicating the degree of coincidence with the normal diagnosis execution data is outside the predetermined range or the detailed diagnostic scenario is not appropriate If it is determined that the detailed diagnosis scenario is not appropriate because the in-vehicle communication device 7 or the like has received (S14: NO), it is determined according to the result of the follow-up observation whether the problem can be reanalyzed (S15) ).
  • the microcomputer 9 determines that the problem can be reanalyzed (S15: YES)
  • the microcomputer 9 returns to the above-described step S9, and repeatedly executes step S9 and subsequent steps. In this case, the microcomputer 9 executes a new detailed diagnostic application different from the previous detailed diagnostic application to diagnose the detailed diagnosis.
  • the microcomputer 9 determines that the defect can not be reanalyzed (S15: NO)
  • the microcomputer 9 specifies that the detected defect is dealt with by dealer repair (S11), and ends the diagnosis processing.
  • the microcomputer 9 determines whether or not a diagnosis instruction operation of cause specific diagnosis has been performed by the user (S16).
  • the microcomputer 9 determines that the diagnostic instruction operation of the cause identification diagnosis has been performed by the user (S16: YES)
  • the in-vehicle communication device 7 transmits a diagnostic application request signal to the server 3 according to the contents of the diagnostic instruction operation.
  • the specific diagnostic application is requested to the server 3 (S17).
  • the server 3 When receiving the diagnostic application request signal, the server 3 searches the diagnostic result database 11 using the diagnostic result data received from the transmission source of the diagnostic application request signal, and is optimum among the plurality of cause identification diagnostic applications. Select the cause specific diagnosis app. That is, when the cause identifying diagnostic application differs depending on, for example, vehicle type, grade, manufacturing time, etc., the server 3 specifies the vehicle type, grade, manufacturing time, etc. of the transmission source of the diagnostic application request signal by vehicle ID. A cause identifying diagnostic application transmitted to a vehicle similar to the vehicle from which the signal was sent and whose diagnosis result was normal is identified, and the identified cause identifying diagnostic application is transmitted.
  • the server 3 may select the optimum cause identification diagnosis application using the diagnosis instruction operation specified by the diagnosis application request signal, and the optimum cause identification diagnosis application according to a procedure other than searching the diagnosis result database 11 You may choose That is, the server 3 may search the diagnostic result database 11 as one method for selecting the optimum cause identification diagnostic application.
  • the microcomputer 9 receives the cause identification diagnostic application transmitted from the server 3 by the in-vehicle communication device 7 and receives the diagnosis application from the in-vehicle communication device 7 via the communication bus 4, thereby providing a server for the cause identification diagnosis application. 3.
  • the acquired cause identifying diagnosis application is executed, and the cause identifying diagnosis is performed according to the cause identifying diagnosis scenario defined in the cause identifying diagnostic application (S18, corresponding to a new diagnostic procedure).
  • the microcomputer 9 executes the periodic diagnosis application as the primary diagnosis application and executes the periodic diagnosis, it determines that the periodic diagnosis scenario was not appropriate due to the non-detection of the defect, and the user instructs diagnosis by the user.
  • the cause identifying diagnosis application is executed as a secondary diagnosing application to execute the cause identifying diagnosis.
  • the microcomputer 9 observes the process after the cause identification diagnosis is performed (S19), and determines whether the cause identification diagnosis scenario is appropriate (S20). In this case, the microcomputer 9 compares the operation log of the ECUs 5 and 6 after the cause identifying diagnosis with the normal operation log defined in advance, and carries out in advance the diagnostic execution data generated when the cause identifying diagnosis is executed. Whether or not the cause-specific diagnosis scenario is appropriate is determined by comparing with prescribed normal diagnosis execution data, determining a predetermined operation by the user after performing the cause-specific diagnosis, or the like.
  • the microcomputer 9 generates diagnosis execution data generated when the cause identification diagnosis is performed, in which the numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the cause identification diagnosis is within a predetermined range
  • the appropriate confirmation signal transmitted from the user terminal 8 by operating the user terminal 8 by the user judging that the numerical value indicating the degree of coincidence with the normal diagnosis execution data is within the predetermined range or the cause specific diagnosis scenario is appropriate.
  • the microcomputer 9 performs the diagnosis generated when the cause identifying diagnosis is performed, in which the numerical value indicating the degree of coincidence between the operation log of the ECUs 5 and 6 and the normal operation log after the cause identifying diagnosis is out of the predetermined range.
  • the user determines that the numerical value indicating the degree of coincidence between the data and the normal diagnosis execution data is outside the predetermined range or that the cause-specific diagnosis scenario is not appropriate, and operates the user terminal 8,
  • the cause identification diagnostic scenario is not appropriate because the appropriate confirmation signal is received by the in-vehicle communication device 7 (S20: NO), in this case as well, it is identified that the failure is not detected by dealer repair. (S11), the diagnostic process ends.
  • the microcomputer 9 determines whether a unique pattern is detected (S21). If the microcomputer 9 determines that a specific pattern is detected (S21: YES), it executes a specific pattern collection application and performs specific pattern collection according to a specific pattern collection scenario defined by the specific pattern collection application (S22) . The microcomputer 9 analyzes the collected specific pattern (S23), and determines whether or not the treatment method for the specific pattern is specified (S24). The microcomputer 9 may analyze the collected unique pattern alone or in cooperation with the server 3.
  • microcomputer 9 determines that the treatment method for the specific pattern is specified (S24: YES)
  • the microcomputer 9 executes the above-described steps S18 and later according to the treatment method for the specified specific pattern. If the microcomputer 9 determines that the treatment method for the specific pattern is not specified (S24: NO), it determines that the failure is not detected by dealer repair (S11), and ends the diagnosis processing.
  • the microcomputer 9 executes the periodic diagnosis application as the primary diagnosis application and executes the periodic diagnosis, it determines that the periodic diagnosis scenario is not appropriate due to the non-detection of the defect, detects the unique pattern, and detects the singularity.
  • the cause specific diagnosis application is executed as a secondary diagnosis application to execute the cause specific diagnosis.
  • the microcomputer 9 determines whether the time elapsed from the start of the periodic diagnosis has reached a predetermined time defined in advance (S25). If the microcomputer 9 determines that the elapsed time from the start of the periodic diagnosis has not reached the predetermined time (S25: NO), it selects the specific pattern collection application again (S26), and returns to step S2 described above, step S2 Repeat and execute. If the microcomputer 9 determines that the elapsed time from the start of the periodical diagnosis has reached the predetermined time (S25: YES), the periodical diagnostic application is selected again (S27), and the process returns to step S1 described above, Repeatedly execute.
  • the vehicle management ECU 2 executes the periodic diagnostic application as the primary diagnostic application and performs periodical diagnosis, but if it is determined that the periodical diagnostic scenario is not appropriate, the detailed diagnostic application is executed as the secondary diagnostic application and detailed diagnosis is performed. It was implemented or the cause specific diagnosis app was executed to execute the cause specific diagnosis.
  • the diagnosis can be appropriately performed by repeatedly performing the diagnosis according to the new detailed diagnosis scenario and the cause-specific diagnosis scenario when the regular diagnosis scenario used for the periodic diagnosis is not appropriate.
  • diagnosis is performed according to the diagnosis scenario defined by the diagnosis application stored in the diagnosis application storage unit 9a.
  • a diagnostic application with a relatively high frequency of use may be stored in advance in the diagnostic application storage unit 9a, whereby the procedure for acquiring a diagnostic application with a relatively high frequency of use from the server 3 can be omitted. Further, even if a failure occurs in the data communication with the server 3, it can be coped with.
  • the diagnosis application is requested to the server 3, and the diagnosis is performed in accordance with the diagnosis scenario defined by the diagnosis application acquired from the server 3.
  • the storage area of the diagnostic application storage unit 9a can be effectively used by acquiring from the server 3 without storing the diagnostic application with a relatively low use frequency in the diagnostic application storage unit 9a in advance.
  • the diagnosis may be performed according to a diagnosis scenario defined by the diagnosis application stored in the server 3 by performing data communication with the server 3 without acquiring the diagnosis application from the server 3.
  • the operation logs of the ECUs 5 and 6 after the execution of the diagnosis are compared with the normal operation log to determine whether the diagnosis scenario used for the diagnosis is appropriate. For example, by determining the degree of coincidence between the operation log of the ECUs 5 and 6 after execution of diagnosis and the normal operation log, it is easily determined without causing the user to determine whether the diagnostic scenario used for the diagnosis was appropriate. can do.
  • the diagnostic execution data generated when the diagnosis was performed is compared with the normal diagnostic execution data to determine whether the diagnostic scenario used for the diagnosis was appropriate. For example, it is easily determined without causing the user to determine whether the diagnostic scenario used for diagnosis is appropriate by determining the degree of coincidence between the diagnostic execution data generated when the diagnosis is performed and the normal diagnostic execution data. can do.
  • the predetermined operation by the user after the diagnosis is performed is determined, and it is determined whether the diagnosis scenario used for the diagnosis is appropriate.
  • the user can be made to determine whether the diagnostic scenario used for diagnosis is appropriate.
  • the diagnosis result database may store data including other information in addition to the vehicle ID, the diagnosis time, the diagnosis application, and the diagnosis result.
  • the evaluation by review may be used for the diagnostic application managed by the server 3. Evaluation by review can be used as a selection criterion when selecting a diagnostic app.
  • the user Before using the diagnostic application or acquiring from the server 3, the user may confirm that the diagnostic application is used or acquired from the server 3 by the user terminal 8 or the like.
  • the diagnosis result in one vehicle may be expanded to other vehicles of the same type. That is, you may expand the information regarding the correctness of the diagnosis in one vehicle, the diagnostic application used, etc. to another same vehicle type vehicle.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Human Computer Interaction (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)
PCT/JP2018/026027 2017-09-28 2018-07-10 車両診断装置、車両診断システム及び車両診断プログラム Ceased WO2019064813A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
DE112018004312.6T DE112018004312B4 (de) 2017-09-28 2018-07-10 Fahrzeugdiagnoseapparat, Fahrzeugdiagnosesystem und Fahrzeugdiagnoseprogramm
CN201880062027.XA CN111133289B (zh) 2017-09-28 2018-07-10 车辆诊断装置、车辆诊断系统以及车辆诊断程序
US16/821,844 US11541899B2 (en) 2017-09-28 2020-03-17 Vehicle diagnosis apparatus, vehicle diagnosis system, and vehicle diagnosis program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017188092A JP6848791B2 (ja) 2017-09-28 2017-09-28 車両診断装置、車両診断システム及び車両診断プログラム
JP2017-188092 2017-09-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/821,844 Continuation US11541899B2 (en) 2017-09-28 2020-03-17 Vehicle diagnosis apparatus, vehicle diagnosis system, and vehicle diagnosis program

Publications (1)

Publication Number Publication Date
WO2019064813A1 true WO2019064813A1 (ja) 2019-04-04

Family

ID=65902857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/026027 Ceased WO2019064813A1 (ja) 2017-09-28 2018-07-10 車両診断装置、車両診断システム及び車両診断プログラム

Country Status (5)

Country Link
US (1) US11541899B2 (enExample)
JP (1) JP6848791B2 (enExample)
CN (1) CN111133289B (enExample)
DE (1) DE112018004312B4 (enExample)
WO (1) WO2019064813A1 (enExample)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115214701A (zh) * 2022-07-14 2022-10-21 潍柴动力股份有限公司 一种车辆就绪状态的控制方法、装置、设备及介质

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7131475B2 (ja) 2018-05-15 2022-09-06 株式会社デンソー 電子制御装置、セッション確立プログラム及び制御プログラム
JP7379892B2 (ja) 2018-07-25 2023-11-15 株式会社デンソー 車両用電子制御システム、車両側システム及び携帯端末
WO2020022265A1 (ja) 2018-07-25 2020-01-30 株式会社デンソー 車両用電子制御システム、プログラム更新の承諾判定方法及びプログラム更新の承諾判定プログラム
JP6973449B2 (ja) 2018-08-10 2021-12-01 株式会社デンソー 車両用電子制御システム、配信パッケージのダウンロード判定方法及び配信パッケージのダウンロード判定プログラム
JP6973450B2 (ja) 2018-08-10 2021-12-01 株式会社デンソー 車両用マスタ装置、インストールの指示判定方法及びインストールの指示判定プログラム
JP7367359B2 (ja) 2018-08-10 2023-10-24 株式会社デンソー 車両用電子制御システム、ファイルの転送制御方法、ファイルの転送制御プログラム及び装置
JP7115429B2 (ja) 2018-08-10 2022-08-09 株式会社デンソー 車両用マスタ装置、ロールバックの実行制御方法及びロールバックの実行制御プログラム
JP7419689B2 (ja) 2018-08-10 2024-01-23 株式会社デンソー 車両用電子制御システム、センター装置、車両用マスタ装置、表示制御情報の送信制御方法、表示制御情報の受信制御方法、表示制御情報の送信制御プログラム及び表示制御情報の受信制御プログラム
JP7484096B2 (ja) 2018-08-10 2024-05-16 株式会社デンソー 電子制御装置、書換えの実行制御方法及び書換えの実行制御プログラム
JP7338280B2 (ja) 2018-08-10 2023-09-05 株式会社デンソー 車両用電子制御システム、車両用マスタ装置、メータ装置、プログラム更新の報知制御方法、インジケータの表示指示プログラム及びインジケータの表示プログラム
JP7111074B2 (ja) 2018-08-10 2022-08-02 株式会社デンソー 車両用マスタ装置、セキュリティアクセス鍵の管理方法、セキュリティアクセス鍵の管理プログラム及び車両用電子制御システム
JP7156192B2 (ja) 2018-08-10 2022-10-19 株式会社デンソー 車両用マスタ装置、非書換え対象の電源管理方法及び非書換え対象の電源管理プログラム
JP7047819B2 (ja) 2018-08-10 2022-04-05 株式会社デンソー 電子制御装置、車両用電子制御システム、アクティベートの実行制御方法及びアクティベートの実行制御プログラム
JP7427879B2 (ja) 2018-08-10 2024-02-06 株式会社デンソー 車両用マスタ装置、書換え対象のグループ管理方法及び書換え対象のグループ管理プログラム
JP7003976B2 (ja) 2018-08-10 2022-01-21 株式会社デンソー 車両用マスタ装置、更新データの検証方法及び更新データの検証プログラム
WO2020032121A1 (ja) 2018-08-10 2020-02-13 株式会社デンソー 車両用マスタ装置、更新データの検証方法及び更新データの検証プログラム
JP7159989B2 (ja) 2018-08-10 2022-10-25 株式会社デンソー 車両用マスタ装置、車両用電子制御システム、アクティベート要求の指示方法及びアクティベート要求の指示プログラム
JP7024765B2 (ja) 2018-08-10 2022-02-24 株式会社デンソー 車両用マスタ装置、更新データの配信制御方法及び更新データの配信制御プログラム
JP7354631B2 (ja) 2018-08-10 2023-10-03 株式会社デンソー 電子制御装置、車両用電子制御システム、差分データの整合性判定方法及び差分データの整合性判定プログラム
JP7400232B2 (ja) 2018-08-10 2023-12-19 株式会社デンソー 電子制御装置、リトライポイントの特定方法、リトライポイントの特定プログラム及び車両用電子制御システム
JP7354658B2 (ja) 2018-08-10 2023-10-03 株式会社デンソー 車両用電子制御システム、進捗表示の画面表示制御方法及び進捗表示の画面表示制御プログラム
JP7439402B2 (ja) 2018-08-10 2024-02-28 株式会社デンソー 表示制御装置、書換え進捗状況の表示制御方法及び書換え進捗状況の表示制御プログラム
JP7151634B2 (ja) * 2019-06-13 2022-10-12 いすゞ自動車株式会社 点検支援プログラム及び点検支援システム
KR102851313B1 (ko) * 2020-03-31 2025-08-27 현대자동차주식회사 차량 및 그 제어 방법
CN115461711A (zh) 2020-04-21 2022-12-09 株式会社电装 车辆用电子控制系统、数据的初始化方法、中心装置、车辆用主装置、初始化数据包的分发程序以及数据的初始化程序
CN112863006B (zh) * 2021-02-24 2023-01-06 联合汽车电子有限公司 车辆的检测方法、装置、设备、车辆和存储介质
JP7447855B2 (ja) * 2021-03-23 2024-03-12 トヨタ自動車株式会社 異常診断装置
DE102021115385A1 (de) 2021-06-14 2022-12-15 Hans Kallich KfZ-Diagnosegerät zur Anzeige eines Schaltbildes mit Mess- und Steuersignalen
DE102021128916A1 (de) 2021-11-05 2023-05-11 Hans Kallich Kfz–Diagnosegerät mit einem Diagnoseprozessrechner
US20230419743A1 (en) * 2022-06-23 2023-12-28 Innova Electronics Corporation Method and system of vehicle diagnostics based on known communication architecture of the vehicle
JP2024134891A (ja) * 2023-03-22 2024-10-04 日立グローバルライフソリューションズ株式会社 家電機器管理システムおよびプログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH06102148A (ja) * 1992-09-22 1994-04-15 Zanabui Infuomateikusu:Kk 車両故障診断システム
JP2003019931A (ja) * 2001-07-06 2003-01-21 Denso Corp 故障診断システム、車両管理装置、サーバ装置、及び検査診断プログラム
US20070010922A1 (en) * 2005-07-08 2007-01-11 Snap-On Incorporated Vehicle diagnostics
JP2007028037A (ja) * 2005-07-14 2007-02-01 Nec Electronics Corp 故障検知診断対処装置、故障検知診断対処システムおよび故障検知診断対処方法

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3674239B2 (ja) * 1997-04-23 2005-07-20 トヨタ自動車株式会社 情報提供システム及び情報提供センタ
JP2002073153A (ja) 2000-08-30 2002-03-12 Hitachi Ltd 車載故障診断通信システム
US6694235B2 (en) * 2001-07-06 2004-02-17 Denso Corporation Vehicular relay device, in-vehicle communication system, failure diagnostic system, vehicle management device, server device and detection and diagnostic program
US6745151B2 (en) 2002-05-16 2004-06-01 Ford Global Technologies, Llc Remote diagnostics and prognostics methods for complex systems
JP3963181B2 (ja) * 2003-12-03 2007-08-22 トヨタ自動車株式会社 車両の故障診断システム
JP4661381B2 (ja) 2005-06-14 2011-03-30 トヨタ自動車株式会社 故障診断装置、故障診断システム、故障診断方法、及び車載装置
JP5445146B2 (ja) 2010-01-06 2014-03-19 トヨタ自動車株式会社 不具合診断装置、不具合診断方法及びプログラム
JP5633262B2 (ja) * 2010-01-07 2014-12-03 株式会社デンソー 車両用情報記憶装置、車両診断システム、プログラム
US9818088B2 (en) * 2011-04-22 2017-11-14 Emerging Automotive, Llc Vehicles and cloud systems for providing recommendations to vehicle users to handle alerts associated with the vehicle
US8543280B2 (en) 2011-04-29 2013-09-24 Toyota Motor Engineering & Manufacturing North America, Inc. Collaborative multi-agent vehicle fault diagnostic system and associated methodology
CN103604612B (zh) * 2013-10-30 2016-08-17 奇瑞汽车股份有限公司 一种车辆远程诊断系统和诊断方法
US11279357B2 (en) * 2013-12-25 2022-03-22 Denso Corporation Vehicle diagnosis system and method
JP6398739B2 (ja) * 2015-01-19 2018-10-03 株式会社デンソー 車載機、車載機診断システム
US20170200325A1 (en) * 2016-01-13 2017-07-13 Ford Global Technologies, Llc Diagnostic test performance control system and method
KR101642436B1 (ko) 2016-04-01 2016-07-26 에이치제이산전(주) 화재 경보 기능을 갖춘 비상전원 자동공급 및 제어장치
CN106406296B (zh) * 2016-12-14 2019-04-23 东北大学 一种基于车载和云端的列车故障诊断系统及方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH06102148A (ja) * 1992-09-22 1994-04-15 Zanabui Infuomateikusu:Kk 車両故障診断システム
JP2003019931A (ja) * 2001-07-06 2003-01-21 Denso Corp 故障診断システム、車両管理装置、サーバ装置、及び検査診断プログラム
US20070010922A1 (en) * 2005-07-08 2007-01-11 Snap-On Incorporated Vehicle diagnostics
JP2007028037A (ja) * 2005-07-14 2007-02-01 Nec Electronics Corp 故障検知診断対処装置、故障検知診断対処システムおよび故障検知診断対処方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115214701A (zh) * 2022-07-14 2022-10-21 潍柴动力股份有限公司 一种车辆就绪状态的控制方法、装置、设备及介质

Also Published As

Publication number Publication date
JP6848791B2 (ja) 2021-03-24
DE112018004312B4 (de) 2025-03-20
DE112018004312T5 (de) 2020-05-07
CN111133289A (zh) 2020-05-08
JP2019066181A (ja) 2019-04-25
CN111133289B (zh) 2022-07-05
US11541899B2 (en) 2023-01-03
US20200216083A1 (en) 2020-07-09

Similar Documents

Publication Publication Date Title
WO2019064813A1 (ja) 車両診断装置、車両診断システム及び車両診断プログラム
US20180315260A1 (en) Automotive diagnostics using supervised learning models
JP4453764B2 (ja) 車両診断装置、車両診断システム、診断方法
US10723361B2 (en) Monitoring apparatus, communication system, vehicle, monitoring method, and non-transitory storage medium
US20170206718A1 (en) Methods and systems for diagnosing a vehicle using sound
EP3913453A1 (en) Fault detection system and method for a vehicle
JP7612711B2 (ja) 攻撃解析装置、攻撃解析方法、および、プログラム
CN108919776B (zh) 一种故障评估方法及终端
US12347241B2 (en) Vehicle diagnosis method and information presentation method
CN106919163B (zh) 通信系统和在通信系统中执行的信息收集方法
US11962605B2 (en) Information processing apparatus, data analysis method and program
US11126730B2 (en) Inspection system
JP2009294004A (ja) 異常解析装置及び異常解析方法
JP7631529B2 (ja) 車両コンポーネントの状態を捕捉するためのシステム
US20220163942A1 (en) Distributed System and Data Transmission Method
CN113759866A (zh) 一种存储信息的系统和装置
CN114911982A (zh) 一种车辆故障预警方法、装置、终端设备及存储介质
CN114379570A (zh) 车辆数据操纵和机械故障的自动检测
JP2017144852A (ja) 車両制御装置
CN115134109A (zh) 攻击分析器、攻击分析方法和存储介质
WO2021111726A1 (ja) 故障診断装置、故障診断システム、故障診断方法および故障診断プログラム
US12166781B2 (en) Attack analyzer for accurate estimation of attack route
US12051288B2 (en) Fault sign detection device, fault sign detection system, fault sign method, and fault sign detection program
JP2018119866A (ja) 車載故障診断システム
WO2024013879A1 (ja) 診断制御装置及び診断制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18860581

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 18860581

Country of ref document: EP

Kind code of ref document: A1

WWG Wipo information: grant in national office

Ref document number: 112018004312

Country of ref document: DE