EP2458564B1 - Diagnostic de véhicules à distance - Google Patents

Diagnostic de véhicules à distance Download PDF

Info

Publication number
EP2458564B1
EP2458564B1 EP11190359.7A EP11190359A EP2458564B1 EP 2458564 B1 EP2458564 B1 EP 2458564B1 EP 11190359 A EP11190359 A EP 11190359A EP 2458564 B1 EP2458564 B1 EP 2458564B1
Authority
EP
European Patent Office
Prior art keywords
vehicle
checksum
configuration file
data storage
storage space
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.)
Active
Application number
EP11190359.7A
Other languages
German (de)
English (en)
Other versions
EP2458564A2 (fr
EP2458564A3 (fr
Inventor
Joakim Drott
Ulla Salonen
Erik BRÅKENHIELM
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.)
Scania CV AB
Original Assignee
Scania CV AB
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 Scania CV AB filed Critical Scania CV AB
Publication of EP2458564A2 publication Critical patent/EP2458564A2/fr
Publication of EP2458564A3 publication Critical patent/EP2458564A3/fr
Application granted granted Critical
Publication of EP2458564B1 publication Critical patent/EP2458564B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0808—Diagnosing performance data

Definitions

  • the present invention relates generally to solutions for fault diagnosis of vehicles.
  • GB 2 366 407 describes a system for remote diagnosis of faults in a vehicle, whereby a two-way connection is set up between the vehicle and a central server.
  • the vehicle uses said connection to convey details of its type and its current fault state, whereupon the server returns a description of possible causes and/or guidance information relating to continued fault identification.
  • the server has access to a database of historical fault data for the specific vehicle, enabling it to "learn" to diagnose the vehicle increasingly effectively.
  • US 2007/100519 describes a telediagnostic system for performing vehicle diagnosis.
  • the server needs to be provided with full details of the vehicle's current configuration, i.e. what components are incorporated in the vehicle and what functions they are programmed to be able to perform. What is also normally necessary is a relatively comprehensive step-by-step exchange of questions and answers between server and vehicle until all the particulars relevant for the diagnosis have been conveyed to the server.
  • the object of the present invention is to propose a solution which alleviates the above problem and thereby makes more effective remote diagnosis of a motor vehicle possible.
  • the invention includes embodiments relating to the system of claim 1 and to the method of claim 6.
  • the object is achieved by the system described in the introduction whereby the central processor resource is connected to a data storage space which contains for example a database.
  • the central processor resource is also configured to check whether a current configuration file specific to the vehicle, or corresponding data describing a prevailing configuration of the vehicle, is stored in the data storage space. If the data storage space is found to contain a current configuration file, the central processor resource is configured to read it out from the data storage space to serve as a basis for the diagnosis engine to determine the fault diagnosis.
  • the central processor resource is configured to send to the vehicle a request for a configuration file specific to it.
  • the central processor resource is configured to read it in, to serve as a basis for the diagnosis engine to determine the fault diagnosis.
  • This system is advantageous in avoiding unnecessary provision of data describing the vehicle's configuration.
  • a relatively large amount of data is needed to properly describe the configuration of a particular vehicle.
  • providing said data may involve a comprehensive dialogue procedure between a central processor resource and the respective vehicle. Minimising the provision of configuration data thus saves both data traffic costs and time.
  • the vehicle-specific configuration file is regarded as describing a current configuration of the vehicle if it is associated with a timestamp indicating a file age which is less than a first predetermined value.
  • the vehicle-specific configuration file is regarded as describing a current configuration of the vehicle if a history stored for said file in conjunction with the central processor resource indicates that the vehicle's configuration has changed less frequently than a second predetermined value. If this condition is fulfilled, further investigation of the configuration file may be avoided, saving a considerable amount of time and resources. This investigation may of course be combined dynamically with the aforesaid age check so that the configuration file is regarded as current if the time since the latest recorded change to the configuration file is shorter than a historical average interval between two consecutive updates of the file.
  • the vehicle-specific configuration file is associated with a checksum.
  • the diagnosis request transmitted from the vehicle to the central processor resource further includes the checksum associated with the vehicle-specific configuration file.
  • the central processor resource comprises a comparator configured to compare the checksum received via diagnosis requests with a checksum calculated in the central processor resource for a configuration file for the vehicle stored in the data storage space. If the checksum received corresponds to the calculated checksum, the data storage space is regarded as containing a current configuration file for the vehicle, so no further provision of data is required.
  • the checksum is based on the content of the configuration file in such a way that a match between two checksums very probably indicates that the respective configuration files are also identical. The conclusion from this comparison may therefore be drawn with a high degree of safety.
  • the central processor resource be configured to calculate a checksum for a configuration file received for storage in the data storage space, and then to store the calculated checksum in the data storage space in association with the configuration file received.
  • the stored checksum is subsequently read out from the data storage space for comparison with a checksum received via a diagnosis request. The amount of time spent receiving a diagnosis request from a vehicle is thus appreciably minimised.
  • the vehicle-specific configuration file is associated with a checksum.
  • the vehicle is here supposed to have a local processing unit configured to receive an order message from the central processor resource.
  • the order message is in response to a diagnosis request from the vehicle and includes a checksum associated with a vehicle-specific configuration file which is stored in the data storage space connected to the central processor resource.
  • the local processing unit is also supposed to be configured to compare the checksum received from the central processor resource with a checksum calculated locally in the vehicle for a current configuration file for the vehicle.
  • the data storage space is found to contain a current configuration file if the checksum received by the vehicle corresponds to the checksum calculated locally in the vehicle.
  • the vehicle-specific configuration file is associated with a checksum.
  • the vehicle is further supposed to have a local processing unit configured to calculate a new local checksum for said file.
  • the vehicle is assumed to be adapted to transmitting said new local checksum and a diagnosis request to the central processor resource.
  • the central processor resource comprises a comparator configured to compare said new locally calculated checksum with a stored previously received locally calculated checksum for a configuration file stored in the data storage space.
  • the data storage space is here found to contain a current configuration file if said new locally calculated checksum corresponds to said previously received said locally calculated checksum.
  • the aforesaid comparator may be situated in the vehicle so that the comparison is instead done in the vehicle and the calculation of the checksums takes place in the central processor resource. This reduces the vehicle's computing burden.
  • the object is achieved by the method described in the introduction which comprises checking whether a current vehicle-specific configuration file describing a prevailing configuration of the vehicle is stored in a data storage space connected to the central processor resource. If the data storage space is found to contain a current configuration file, the method comprises reading it out from the data storage space to serve as a basis for the diagnosis engine to determine the fault diagnosis. If on the contrary the data storage space is found not to contain a current vehicle-specific configuration file, the central processor resource sends to the vehicle a request for such a file. In response to receiving a vehicle-specific configuration file from the vehicle, the diagnosis engine reads it in, to serve as a basis for determining the fault diagnosis.
  • the object is achieved by a computer programme which can be directly downloaded to the internal memory of a computer and comprises software for controlling the steps according to the method proposed above when said programme is run on a computer.
  • the object is achieved by a computer-readable medium which has stored on it a programme adapted to enabling a computer to control the steps according to the method proposed above.
  • FIG. 1 depicting an embodiment of a system according to the invention.
  • the system comprises a central processor resource 100 and a data storage space 120 and is adapted to remote-diagnosing a vehicle 180.
  • the central processor resource 100 is configured to communicate wirelessly with at least one vehicle 180 via a communication means 182 located in the vehicle.
  • the communication means 182 is itself adapted to receiving information about a functional status of the vehicle 180 from a data gathering means 184 located in the vehicle.
  • the communication means 182 handles inter alia fault signals and fault reports from ECUs (electronic control units) located in the vehicle.
  • the vehicle 180 is configured to generate, and by means of the communication means 182 send to the central processor resource 100, a diagnosis request DR.
  • the diagnosis request DR will include a fault report describing a functional status of the vehicle 180 and may for example be transmitted to the central processor resource 100 via a base station 160 and one or more communication networks 150, e.g. Internet.
  • the central processor resource 100 is configured to use a diagnosis engine to determine a fault diagnosis for the vehicle 180.
  • the central processor resource 100 is connected to a data storage space 120 which for example contains a database.
  • the central processor resource 100 is further configured to check whether a current vehicle-specific configuration file CF describing a prevailing configuration of the vehicle 180 is stored in the data storage space 120.
  • the central processor resource 100 is adapted to reading it out from the data storage space 120 to the diagnosis engine 110 to serve as a basis for determining the fault diagnosis for the vehicle 180. If the data storage space 120 is found not to contain a current vehicle-specific configuration file CF, the central processor resource 100 is adapted instead to sending to the vehicle 180 a request CFR for such a file. In response to receiving a vehicle-specific configuration file CF from the vehicle 180, the central processor resource 100 is further adapted to reading it into the diagnosis engine 110 to serve as a basis for determining the fault diagnosis.
  • the vehicle-specific configuration file CF is regarded as describing a current configuration of the vehicle 180 if it is associated with a timestamp which indicates its age at less than a first predetermined value, e.g. a week, a month, a half-year or a year, depending on vehicle type and/or model, equipment and, where applicable, a dynamic parameter such as a configuration history.
  • the vehicle-specific configuration file CF is regarded as describing a current configuration of the vehicle 180 if a history H stored in conjunction with the central processor resource 100 for the file indicates that the configuration of the vehicle 180 has changed less frequently than a second predetermined value.
  • the history H is stored with advantage in a database 130 which may either be accommodated in the same storage space as, or be stored separately from, the data storage space 120.
  • the file is associated with a checksum calculated, for example, by so-called hashing.
  • the checksum may be calculated locally in the vehicle 180 and be designated # v , or be calculated centrally in the central processor resource 100 and be designated # c .
  • diagnosis requests DR transmitted from the vehicle 180 to the central processor resource 100 may include the checksum # v associated with the vehicle-specific configuration file CF.
  • the central processor resource 100 comprises a comparator 140 configured to compare the checksum # v received via diagnosis requests DR with a checksum # c calculated in the central processor resource for a configuration file CF for the vehicle 180 which is stored in the data storage space 120.
  • the data storage space 120 is here found to contain a current configuration file CF if the checksum # v received corresponds to the centrally calculated checksum # c .
  • the central processor resource 100 may be configured to calculate for a configuration file CF received a checksum # c with a view to the file being stored in the data storage space 120.
  • the central processor resource 100 stores the calculated checksum # c in the data storage space 120 in association with the configuration file CF received, either at a shared location or with suitable linking.
  • the central processor resource 100 is further adapted to reading the checksum # c out from the data storage space 120 for comparison with a checksum # v received via a diagnosis request DR. Valuable computing time is thus saved at the time of the comparison.
  • the comparison between the checksums may instead be performed in the vehicle 180.
  • the vehicle 180 is supposed to have a local processing unit 186 configured to receive an order message OM from the central processor resource 100.
  • the order message OM is sent to the vehicle 180 in response to a diagnosis request DR from it.
  • the order message OM includes a checksum # c associated with a vehicle-specific configuration file CF for the vehicle 180 which is stored in the data storage space 120.
  • the local processing unit 186 is adapted to comparing the checksum # c received from the central processor resource 100 with a checksum # v calculated locally in the vehicle 180 for a current configuration file CF for the vehicle.
  • the data storage space 120 is found to contain a current configuration file CF if the checksum # c received in the vehicle 180 corresponds to the checksum # v calculated locally in the vehicle.
  • the local processing unit 186 of the vehicle 180 may for example be configured to calculate a new local checksum # v for a current configuration file CF for the vehicle 180.
  • the vehicle 180 is further configured to be able to transmit the new local checksum # v to the central processor resource 100, e.g. via the communication means 182, advantageously at the same time as transmitting a diagnosis request DR.
  • the new locally calculated checksum # v is compared with a stored previously received locally calculated checksum # v for a configuration file CF stored in the data storage space 120.
  • the data storage space 120 is found to contain a current configuration file CF if the new locally calculated checksum # v corresponds to the previously received said locally calculated checksum # v .
  • the allocation of work between the vehicle 180 and the central processor resource 100 may be reversed so that a similar comparator is located in the vehicle 180 and the calculation of checksums # c is performed in the central processor resource 100.
  • the central processor resource 100 be configured to function in accordance with the instructions contained in software which is executed in the processor resource 100. It is therefore advantageous if the central processor resource 100 includes, or is in some other way linked to, a memory module M containing software which, when executed in the central processor resource 100, causes the procedure described above to be performed.
  • a first step 210 checks whether a diagnosis request DR from a vehicle has been received.
  • the diagnosis request DR will include a fault report describing a functional status of the vehicle concerned. If such a diagnosis request DR has been received, a step 220 follows, otherwise the procedure loops back and comes to a halt at step 210.
  • Step 220 checks whether a current vehicle-specific configuration file describing a prevailing configuration of the vehicle is stored in an accessible data storage space. If such is the case, a step 230 reads said configuration file CF out from the data storage space to serve as a basis for a diagnosis engine.
  • a subsequent step 240 determines a fault diagnosis for the vehicle on the basis of the configuration file CF and the fault report received.
  • a step 250 follows whereby the vehicle is sent a request for a vehicle-specific configuration file CF.
  • a step 260 checks whether such a file has been received. The procedure loops to step 250 until such a configuration file CF is received. Receipt of the configuration file CF is followed by a step 270 which reads the configuration file CF received into the diagnosis engine to serve in conjunction with the fault report as a basis for determining the fault diagnosis, which takes place at step 240.
  • step 240 When the fault diagnosis has been established at step 240, the procedure loops back to step 210.
  • the method steps described with reference to Figure 2 may be controlled by means of programmed computer apparatus.
  • the embodiments of the invention described above with reference to the diagrams comprise a computer and processes conducted in a computer
  • the invention extends to computer programmes, especially computer programmes on or in a carrier suited to practically implementing the invention.
  • the programme may be in the form of source code, object code, a code intermediate between source and object code, e.g. in partly compiled form, or in any other form suitable for use in implementing the process according to the invention.
  • the carrier may be any entity or device capable of carrying a programme.
  • the carrier may comprise a storage medium such as a flash memory, an ROM (read only memory), e.g.
  • the carrier may also be a transmitting carrier such as an electrical or optical signal which can be conveyed by an electrical or optical cable or via radio or in some other way.
  • the carrier may take the form of such a cable, device or means.
  • the carrier may be an integrated circuit in which the programme is embedded and which is adapted to conducting, or to being used in conducting, the relevant processes.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Small-Scale Networks (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)

Claims (11)

  1. Système de diagnostic de véhicules (180), comprenant
    une ressource de processeur central (100) configurée pour communiquer sans fil avec au moins un véhicule (180) via des moyens de communication (182) situés dans le véhicule et adaptés pour recevoir des informations sur un état fonctionnel du véhicule (180) à partir de moyens de collecte de données (184) situés dans le véhicule (180), ledit au moins un véhicule (180) étant configuré pour générer et envoyer à la ressource de processeur central (100) par l'intermédiaire desdits moyens de communication (182) une demande de diagnostic (DR) qui comprend un rapport de panne décrivant un état fonctionnel du véhicule (180), et
    la ressource de processeur central (100) étant configurée pour déterminer sur la base du rapport de panne un diagnostic de panne pour le véhicule (180) en utilisant un moteur de diagnostic (110),
    caractérisé en ce que la ressource de processeur central (100) est connectée à un espace de stockage de données (120) et est en outre configurée
    pour vérifier si un fichier de configuration (CF) courant spécifique au véhicule décrivant une configuration du véhicule (180) qui prévaut est stocké dans l'espace de stockage de données (120),
    s'il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant spécifique au véhicule, pour le lire à partir de l'espace de stockage de données (120) afin de servir de base au moteur de diagnostic (110) pour déterminer le diagnostic de panne,
    s'il est constaté que l'espace de stockage de données (120) ne contient pas un fichier de configuration (CF) courant spécifique au véhicule,
    pour envoyer au véhicule (180) une demande (CFR) d'un fichier de configuration (CF) spécifique au véhicule, et
    pour répondre à la réception d'un fichier de configuration (CF) spécifique au véhicule provenant du véhicule (180) en le lisant, pour servir de base au moteur de diagnostic (110) pour déterminer le diagnostic de panne,
    dans lequel le fichier de configuration(CF) spécifique au véhicule est considéré comme décrivant une configuration courante du véhicule (180) s'il est associé à un horodatage qui indique que son âge est inférieur à une première valeur prédéterminée et si un historique (H) stocké pour ledit fichier en association avec la ressource de processeur central (100) indique que le fichier de configuration spécifique au véhicule du véhicule (180) a changé moins fréquemment qu'une seconde valeur prédéterminée, de sorte que le fichier de configuration spécifique au véhicule est considéré comme étant courant si le temps écoulé depuis le dernier changement enregistré du fichier de configuration spécifique au véhicule est plus court qu'un intervalle moyen d'historique entre deux mises à jour consécutives du fichier.
  2. Système selon la revendication 1, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c), ladite demande de diagnostic (DR) transmise du véhicule (180) à la ressource processeur central (100) inclut la somme de contrôle (#v) associée au fichier de configuration (CF) spécifique au véhicule, et la ressource de processeur central (100) comprend
    un comparateur (140) configuré pour comparer la somme de contrôle (#v) reçue via des demandes de diagnostic (DR) à une somme de contrôle (#c) calculée dans la ressource de processeur central (100) pour un fichier de configuration (CF) pour le véhicule (180) qui est stocké dans l'espace de stockage de données (120), et
    dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si la somme de contrôle (#v) reçue correspond à la somme de contrôle (#c) calculée.
  3. Système selon la revendication 2, dans lequel la ressource de processeur central (100) est configurée
    pour calculer une somme de contrôle (#c) pour un fichier de configuration (CF) reçu en vue de le stocker dans l'espace de stockage de données (120),
    pour stocker la somme de contrôle (#c) calculée dans l'espace de stockage de données (120) en association avec le fichier de configuration (CF) reçu, et
    pour lire la somme de contrôle (#c) stockée à partir de l'espace de stockage de données (120) afin de la comparer à une somme de contrôle (#v) reçue via une demande de diagnostic (DR).
  4. Système selon la revendication 1, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c) et le véhicule (180) est supposé avoir une unité de traitement locale (186) configurée pour
    recevoir de la ressource de processeur central (100) un message de commande (OM) qui est envoyé en réponse à une demande de diagnostic (DR) provenant du véhicule (180) et inclut une somme de contrôle (#c) associée à un fichier de configuration (CF) spécifique au véhicule (180), qui est stocké dans l'espace de stockage de données (120) connecté à la ressource de processeur central (100), et
    comparer la somme de contrôle (#c) reçue de la ressource de processeur central (100) à une somme de contrôle (#v) calculée localement dans le véhicule (180) pour un fichier de configuration (CF) courant pour le véhicule (180), et
    dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si ladite somme de contrôle (#c) reçue dans le véhicule (180) correspond à ladite somme de contrôle (#v) calculée localement.
  5. Système selon la revendication 1, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c),
    le véhicule (180) étant supposé avoir une unité de traitement locale (186) configurée pour calculer une nouvelle somme de contrôle (#v) locale pour ledit fichier (CF), et étant adaptée pour transmettre à la ressource de processeur central (100) ladite nouvelle somme de contrôle (#v) locale et une demande de diagnostic (DR),
    la ressource de processeur central (100) comprenant un comparateur (140) configuré pour comparer ladite nouvelle somme de contrôle (#v) locale à une somme de contrôle (#v) locale stockée reçue précédemment pour un fichier de configuration (CF) stocké dans l'espace de stockage de données (120), et
    dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si ladite nouvelle somme de contrôle (#v) locale correspond à ladite somme de contrôle (#v) locale précédemment reçue.
  6. Procédé de diagnostic de véhicules (180), comprenant les étapes consistant à
    acheminer vers une ressource de processeur central (100) à partir d'un véhicule (180) une demande de diagnostic (DR) qui comprend un rapport de panne décrivant un état fonctionnel du véhicule (180),
    sur la base du rapport de panne, déterminer un diagnostic de panne pour le véhicule (180) par l'intermédiaire d'un moteur de diagnostic (110) dans la ressource de processeur central (100),
    caractérisé en ce que le procédé comprend les étapes consistant à
    vérifier si un fichier de configuration (CF) courant spécifique au véhicule décrivant une configuration du véhicule (180) qui prévaut est stocké dans un espace de stockage de données (120) connecté à la ressource de processeur central (100),
    s'il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant spécifique au véhicule, le lire à partir de l'espace de stockage de données (120) afin de servir de base au moteur de diagnostic (110) pour déterminer le diagnostic de panne,
    s'il est constaté que l'espace de stockage de données (120) ne contient pas un fichier de configuration (CF) courant spécifique au véhicule,
    envoyer à partir de la ressource de processeur central (100) au véhicule (180) une demande (CFR) d'un fichier de configuration (CF) spécifique au véhicule, et
    répondre à la réception d'un fichier de configuration (CF) spécifique au véhicule provenant du véhicule (180) en le lisant, pour qu'il serve de base au moteur de diagnostic (110) pour déterminer le diagnostic de panne,
    dans lequel le fichier de configuration (CF) spécifique au véhicule est considéré comme décrivant une configuration courante du véhicule (180) s'il est associé à un horodatage qui indique que son âge est inférieur à une première valeur prédéterminée et si un historique (H) stocké pour ledit fichier en association avec la ressource de processeur central (100) indique que la configuration spécifique au véhicule du véhicule (180) a changé moins fréquemment qu'une seconde valeur prédéterminée, de sorte que le fichier de configuration spécifique au véhicule est considéré comme étant courant si le temps écoulé depuis le dernier changement enregistré du fichier de configuration spécifique au véhicule est plus court qu'un intervalle moyen d'historique entre deux mises à jour consécutives du fichier.
  7. Procédé selon la revendication 6, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c), ladite demande de diagnostic (DR) transmise du véhicule (180) à la ressource de processeur central (100) inclut la somme de contrôle (#v) associée au fichier de configuration (CF) spécifique au véhicule, et le procédé comprend l'étape consistant à
    comparer la somme de contrôle (#v) reçue via des demandes de diagnostic (DR) à une somme de contrôle (#c) calculée dans la ressource de processeur central (100) pour un fichier de configuration (CF) pour le véhicule (180) qui est stocké dans l'espace de stockage de données (120),
    et dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si la somme de contrôle (#v) reçue du véhicule (180) correspond à la somme de contrôle (#c) calculée.
  8. Procédé selon la revendication 7, comprenant les étapes de
    calculer dans la ressource de processeur central (100) une somme de contrôle (#c) pour un fichier de configuration (CF) reçu, en vue de le stocker dans l'espace de stockage de données (120),
    stocker la somme de contrôle (#c) calculée dans l'espace de stockage de données (120) en association avec le fichier de configuration (CF) reçu, et
    lire la somme de contrôle (#c) stockée à partir de l'espace de stockage de données (120) pour la comparer à une somme de contrôle (#v) reçue via une demande de diagnostic (DR).
  9. Procédé selon la revendication 6, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c) et dans lequel le procédé comprend les étapes de
    en réponse à une demande de diagnostic (DR) reçue, transmettre de la ressource de processeur central (100) au véhicule (180) une somme de contrôle (#c) associée à un fichier de configuration (CF) spécifique au véhicule pour le véhicule (180) qui est stocké dans l'espace de stockage de données (120),
    comparer dans le véhicule (180) la somme de contrôle (#c) reçue à partir de la ressource de processeur central (100) à une somme de contrôle (#v) calculée localement pour un fichier de configuration (CF) courant pour le véhicule (180),
    et dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si la somme de contrôle (#c) reçue dans le véhicule (180) correspond à la somme de contrôle (#v) calculée localement.
  10. Procédé selon la revendication 6, dans lequel le fichier de configuration (CF) spécifique au véhicule est associé à une somme de contrôle (#v #c) et dans lequel le procédé comprend les étapes de
    transmettre une demande de diagnostic (DR) du véhicule (180) à la ressource de processeur central (100),
    calculer dans le véhicule (180) une nouvelle somme de contrôle (#v) locale pour ledit fichier (CF), et
    transmettre ladite nouvelle somme de contrôle (#v) locale du véhicule (180) à la ressource de processeur central (100), et
    comparer dans la ressource de processeur central (100) ladite nouvelle somme de contrôle (#v) locale à une somme de contrôle (#v) locale précédemment stockée pour un fichier de configuration (CF) stocké dans l'espace de stockage de données (120), et
    dans lequel il est constaté que l'espace de stockage de données (120) contient un fichier de configuration (CF) courant si ladite nouvelle somme de contrôle (#v) locale correspond à ladite somme de contrôle (#v) locale précédemment reçue.
  11. Support (M) lisible par ordinateur sur lequel est stocké un programme adapté pour permettre à un ordinateur de commander les étapes selon l'une quelconque des revendications 6 à 10.
EP11190359.7A 2010-11-29 2011-11-23 Diagnostic de véhicules à distance Active EP2458564B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
SE1051246A SE1051246A1 (sv) 2010-11-29 2010-11-29 Fjärrdiagnostisering av fordon

Publications (3)

Publication Number Publication Date
EP2458564A2 EP2458564A2 (fr) 2012-05-30
EP2458564A3 EP2458564A3 (fr) 2014-08-27
EP2458564B1 true EP2458564B1 (fr) 2018-04-04

Family

ID=45217263

Family Applications (1)

Application Number Title Priority Date Filing Date
EP11190359.7A Active EP2458564B1 (fr) 2010-11-29 2011-11-23 Diagnostic de véhicules à distance

Country Status (3)

Country Link
EP (1) EP2458564B1 (fr)
BR (1) BRPI1105021A2 (fr)
SE (1) SE1051246A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103061910B (zh) * 2012-12-27 2015-07-08 潍柴动力股份有限公司 一种区分发动机当前故障和历史故障的系统及方法
EP2940660A1 (fr) * 2014-04-30 2015-11-04 Continental Automotive GmbH Synchronisation d'enregistrements d'état de service entre un véhicule et une unité fixe
DE102018201130A1 (de) * 2018-01-25 2019-07-25 Robert Bosch Gmbh Vorrichtung und Verfahren zum Registrieren und Überwachen autonomer Fahrzeuge
CN114911652A (zh) * 2021-02-07 2022-08-16 广汽埃安新能源汽车有限公司 车辆配置校验方法、系统及计算机可读存储介质
CN115129026A (zh) * 2022-06-17 2022-09-30 东风汽车集团股份有限公司 一种车辆故障诊断方法和相关模块配置方法及相关设备
DE102023124803A1 (de) 2023-09-14 2025-03-20 AUDI HUNGARIA Zrt. Kraftfahrzeug, Verfahren zum Bauen eines solchen und System sowie Verfahren mit Nutzung einer Mehrzahl von solchen Kraftfahrzeugen

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NL9301301A (nl) * 1993-07-23 1995-02-16 Nederland Ptt Stelsel en inrichting voor het overdragen van voertuiggegevens.
GB2366407A (en) 2000-08-31 2002-03-06 Trw Ltd Remote diagnosis of faults in vehicles
US7155321B2 (en) * 2001-08-06 2006-12-26 Idsc Holdings Llc System, method and computer program product for remote vehicle diagnostics, monitoring, configuring and reprogramming
GB2383854B (en) * 2001-09-06 2005-06-22 Sun Microsystems Inc Method for checking a computer system configuration
DE10323384A1 (de) * 2003-05-23 2004-12-16 Daimlerchrysler Ag Diagnosesystem
DE102006009098A1 (de) * 2006-02-28 2007-08-30 Daimlerchrysler Ag Kraftfahrzeugdiagnose und Fahrzeugannahme
US20100082702A1 (en) * 2008-09-29 2010-04-01 Honeywell International Inc. Dynamic vehicle information management
CN101860531B (zh) * 2010-04-21 2013-04-17 北京星网锐捷网络技术有限公司 数据包过滤规则匹配方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP2458564A2 (fr) 2012-05-30
EP2458564A3 (fr) 2014-08-27
SE1051246A1 (sv) 2012-05-30
BRPI1105021A2 (pt) 2013-03-19

Similar Documents

Publication Publication Date Title
EP3722901B1 (fr) Procédé de diagnostic de panne de véhicule et appareil de diagnostic de panne de véhicule
EP2458564B1 (fr) Diagnostic de véhicules à distance
CN110069053B (zh) 一种基于tsp云台的远程车辆检测系统及其方法
US7589624B2 (en) Component unit monitoring system and component unit monitoring method
US20120041637A1 (en) Engine diagnostic system and method for capturing diagnostic data in real-time
US12175809B2 (en) Remote automobile diagnostic method and apparatus, and computer device
US20090306849A1 (en) System for diagnosis of motor vehicles, and for reception of vehicles at a repair facility
US20150277891A1 (en) Electronic controller software coding system and method for vehicle control
JP2007099145A (ja) 車載ネットワークの診断システム及び車載制御装置
TW200836957A (en) Method and system for processing and transmitting automotive emission data
CN105511448A (zh) 一种集成式车用诊断仪及其诊断方法
CN110995823B (zh) 车载终端离线处理方法、设备、存储介质及装置
CN113505056A (zh) 车辆诊断方法、系统、装置及存储介质
CN115619370A (zh) 一种车辆故障诊断方法及装置
CN114378862B (zh) 基于云平台的机器人异常自动修复方法、装置和机器人
CN110045720A (zh) 车载TBox异常数据上传监控系统及监控方法
KR101412289B1 (ko) 이씨유 관리 시스템 및 방법
CN113625690A (zh) 一种汽车智能诊断方法、系统及移动终端
CN113780963A (zh) 商品车的运输管理方法、系统、存储介质及设备
CN114371683B (zh) 诊断仪的诊断功能验证方法、系统、存储介质及设备
CN111447231B (zh) 一种车辆协议识别的方法及装置
CN104199438A (zh) 车辆远程诊断方法及设备
CN117873020A (zh) 一种车辆的远程诊断方法及装置
CN118897698A (zh) 驱动程序自适配方法、装置、存储介质、车辆控制器及车辆
CN106882162B (zh) 车辆维护装置及系统

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIC1 Information provided on ipc code assigned before grant

Ipc: G07C 5/00 20060101AFI20140723BHEP

Ipc: G07C 5/08 20060101ALI20140723BHEP

17P Request for examination filed

Effective date: 20150227

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

17Q First examination report despatched

Effective date: 20151211

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20171130

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 986369

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180415

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602011047083

Country of ref document: DE

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180404

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180704

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180704

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180705

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 986369

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180806

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602011047083

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

26N No opposition filed

Effective date: 20190107

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20181123

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181123

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181130

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181123

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181123

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181123

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180404

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20111123

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180404

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180804

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230518

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20250930

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20251001

Year of fee payment: 15