[go: up one dir, main page]

WO2016112902A1 - Procédé et système pour la détection d'événements de véhicule - Google Patents

Procédé et système pour la détection d'événements de véhicule Download PDF

Info

Publication number
WO2016112902A1
WO2016112902A1 PCT/DE2016/200004 DE2016200004W WO2016112902A1 WO 2016112902 A1 WO2016112902 A1 WO 2016112902A1 DE 2016200004 W DE2016200004 W DE 2016200004W WO 2016112902 A1 WO2016112902 A1 WO 2016112902A1
Authority
WO
WIPO (PCT)
Prior art keywords
event
data
sensor data
vehicle
determining
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/DE2016/200004
Other languages
German (de)
English (en)
Inventor
Jin Li
Marcel Philipp Mayer
Ralf Stopp
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.)
Schaeffler Technologies AG and Co KG
Original Assignee
Schaeffler Technologies AG and Co KG
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 Schaeffler Technologies AG and Co KG filed Critical Schaeffler Technologies AG and Co KG
Publication of WO2016112902A1 publication Critical patent/WO2016112902A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
    • G06F11/0739—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in automotive or aircraft systems

Definitions

  • the present invention relates to a system for detecting vehicle events. Furthermore, the invention relates to a computer-implemented method for the reporting of vehicle events and to a computer program product for carrying out the computer-implemented method.
  • Modern vehicles have sophisticated electronic systems with complex networking. Further, the systems are connected to off-vehicle infrastructures, such as via wireless data communication devices, to integrate up-to-date and / or new functionality. For example, a navigation convenience function can be supplied with new map material. Or it is possible to update the engine control program, the ABS (Anti-lock Braking System) or the ESP (Electronic Stability Program) program. Such changes are often also possible due to the existing vehicle sensors, such as the ABS or ESP sensors.
  • the networking of the electronic systems leads to a variety of interactions that are so complex that it is hardly possible to test all applications before the market launch of a vehicle. This concerns, for example, comfort functions such as seat heating with heat regulation and sensor technology, but also safety functions such as driver assistance systems for braking, roll stabilization or distance regulation to the front or to the side.
  • a specific event such as a malfunction that occurs due to the complex interactions of different electronic systems, is difficult or impossible to reproduce. It is also not possible to directly process and / or store all sensor data that occurs during operation, since in modern vehicles sensor data of the order of magnitude of up to 1 GB per minute can be incurred. Thus, it is difficult to identify such a specific event and, if necessary, to remedy this, as in the case of a malfunction. This is particularly disadvantageous Such events typically can occur for all vehicles of the same type or electronic system in a particular integration with other systems. In addition, these events usually occur during the operation of a vehicle, that is to say in the field application during which access to the sensor data is restricted.
  • the method of reporting an event to a vehicle includes receiving sensor data from at least one vehicle sensor and storing that sensor data on a rewritable memory element.
  • the sensor data from several vehicle sensors for, for example, brakes, ABS, EPS, speed, speed, air pressure, fluid levels and temperatures, engine conditions, and others, can be stored in a buffer memory. This has the advantage that even large amounts of data of, for example, 1 GB per minute can be stored at least for a specific time window or a certain period of time. If the buffer memory is not free memory space, the oldest buffered data will be overwritten by
  • the inventive method further comprises receiving an event indicator about the event.
  • an event indicator may be initiated by the driver, for example.
  • the switch function can also be implemented via an interactive and touch-sensitive display, such as the so-called touchscreen of a smartphone or a multimedia system of the vehicle.
  • a voice or gesture recognition is also possible for the initiation of the event indicator.
  • the method includes determining a time period based on the event indicator and then copying the sensor data received within the time period from the rewritable storage element to another storage element.
  • all sensor data is copied from the buffer memory to a buffer within a defined period of time.
  • the cache is not overwritten like the cache, at least for as long as the cached sensor data must be kept.
  • all the sensor data stored in the buffer memory can be copied, which was buffered up to the time of the event indicator.
  • the sensor data can also be copied for a shorter period, namely for a period that does not include all the sensor data in the buffer.
  • the method includes receiving and storing event data regarding the event. So it is possible that the driver comments on the abnormalities, such as a stuttering of the engine, and thus provides event data.
  • the event data can therefore be documentation data from the driver.
  • the documentation or generation of the event data can take place in this case independently of the time of the event. It is thus possible for the driver of the vehicle to first arrive at his destination and to document his observations after the end of the journey.
  • the sensor data is saved in the further memory, the buffer, on the basis of the event indicator, the assignment of the event data to the sensor data is possible.
  • the event data can be created, for example, in the form of written text, as a sound recording, as a video log or other.
  • the storage of the event data can also be done in the further memory element, or any other memory. A speedy copying from the buffer into the further memory element / cache, as required by the sensor data due to a continuous sensor data stream with the continuous overwriting of the oldest sensor data in the buffer memory, is not necessary in the storage of the event data.
  • the method further comprises determining relevant sensor data from the sensor data copied to the further memory element and transmitting the relevant sensor data and / or the event data.
  • all sensor data on the further memory element and the event data are transmitted, for example, to the manufacturer or service provider of the vehicle or electronic system. If event data is not present, for example if the driver indicates that he can not or does not want to provide any further data for the event, then only the relevant sensor data can be transmitted. After transmitting the relevant sensor data and / or the event data, the further memory element and / or the memory on which the event data are saved can be released again.
  • the transmission of the relevant sensor data and / or the event data takes place via a data connection.
  • the data connection can be wireless or wired.
  • the data communication info- infrastructure of mobile networks for a wireless data connection.
  • a corresponding communication cable can be connected to an interface of the vehicle.
  • the further memory element and / or the memory on which the event data are saved can also be removed from the vehicle and read out at a corresponding arithmetic unit.
  • the removable memory can store a flash memory such as SD memory. Cards (English for Secure-Digital Memory) or a magnetic memory is.
  • determining the relevant sensor data comprises comparing the sensor data for the time period and the event data. It is thus possible for the event data to include information for the assignment of a specific vehicle sensor. For example, the driver could make a preselection when entering his observations that he has noticed, for example, braking problems. This makes it possible to limit the relevant sensor data to the data of vehicle sensors, which are related to the braking function of the vehicle. This allows for a beneficial reduction in the amount of sensor data, which may be helpful depending on the data transmission bandwidth and / or cost of transmitting data.
  • the method includes transmitting the event data and receiving an instruction to determine the relevant sensor data based on the sent event data.
  • a receiver can be, for example, a solver system, which can have better analysis options than a simple vehicle computer.
  • a solver system can have high computing power with sophisticated algorithms, or also include the ability to access extensive comparative data.
  • the recipient is a human processor.
  • the instruction for determining the relevant sensor data on the basis of the transmitted event data can be advantageously used, for example, only the sensor data of a single vehicle sensors. Another time restriction is possible.
  • the method includes comparing the relevant sensor data and / or the event data to an event database and, if an event such as an error is identified, issuing an instruction.
  • the event database can be carried in the vehicle, which allows, for example, a speedy identification of safety-critical errors. In this case, only the sensor data, that is without any event data, can be used for comparison. For example, certain patterns in the event database and sensor data may already lead to detection of ABS problems.
  • the event database may also be present at a receiver. The latter can analyze the relevant sensor data and / or event data transmitted to him accordingly and compare it with the event database.
  • the instruction can accordingly be received and output at the vehicle.
  • An instruction can be a simple speech or textual display output. But an instruction to a vehicle component is possible, such as limiting the engine speed to prevent damage to the engine.
  • the method for reporting events including the relevant sensor data, in particular for the manufacturer and / or service provider of the vehicles and / or systems advantageous.
  • For an identification of an example difficult to find error can be corrected accordingly in other vehicles and / or systems.
  • Another aspect of the present invention is a computer program product which, when loaded into a memory of a data processing system and executed by at least one processor of the data processing system, performs the steps of the computer-implemented method.
  • the invention further includes a vehicle having a reporter system for reporting a vehicle event as described above and below.
  • Figure 1 shows an embodiment of the system according to the invention for the detection of vehicle events in an application scenario.
  • FIG. 2 shows a flowchart for illustrating a method according to the invention.
  • FIG. 3 shows a simple block diagram of the system of FIG. 1.
  • the application scenario 100 shows a vehicle 101 with a plurality of vehicle sensors 102.
  • the vehicle sensors 102 send sensor data to the reporter system 110 for reporting an event (FIG. Event is not illustrated).
  • the transmission of the sensor data to the reporter system 1 10 is shown by dotted lines.
  • the reporter system 110 is configured and configured for detecting and determining rele- vant sensor data and / or event data which can be transmitted further.
  • the reporter system 110 sends 172 the relevant sensor data and / or event data to a solver system 150.
  • the solver system 150 is configured and configured to assist in the detection of the relevant sensor data or other compute-intensive operations, such as for speech recognition is required.
  • the solver system 150 and reporter system 1 10 can bi-directionally establish a data connection.
  • the reporter system 110 and the solver system 150 form the system for detecting vehicle events.
  • the reporter system 110 and the solver system 150 are shown, for example, in FIG. 3 (FIG. 3, reference numerals 310 and 350). Procedural steps in cooperation Hang with the reporter system 110 and the solver system 150 are shown for example in Figure 2.
  • the vehicle event detection system, reporter system 110 and solver system 150 may bi-directionally exchange 174, 176 data with a service location 180 for the vehicle 101.
  • a service location 180 may be, for example, the vehicle manufacturer or OEM ( Original Equipment Manufacturer).
  • the service point 180 may also be a manufacturer of an electronic device from the vehicle 101.
  • the service station 180 may evaluate the event data and, if necessary, identify errors that are reported back to the vehicle 101 for output. Further, detected vehicle events may be collected in a database at service location 180 and thus used to enhance the vehicle or vehicle type or vehicle system or component. Such improvement data are transmitted to the development and production 182 178.
  • FIG. 2 shows a flow chart for illustrating a method 200 according to the invention for reporting a vehicle event. Dashed steps shown in Figure 2 are optional.
  • the method 200 includes receiving 210 sensor data from at least one vehicle sensor and storing 212 the sensor data on a rewritable storage element, such as a buffer memory or ring buffer.
  • the method 200 further includes receiving 220 an event indicator about the event and then determining 222 a time period based on the event indicator. Thereafter, the sensor data received within the period are copied 225 from the rewritable memory element to another memory element, that is, stored in a memory which is not overwritten without release. Further, simultaneously or temporally offset, event data relating to the event is received 230 and also stored 232.
  • the method 200 then includes determining 240 relevant sensor data from the sensor data copied to the further memory element, the relevant sensor data representing the entire data. quantity on the further memory element or a subset or even more still to be detected sensor data after the time of the event may include. Subsequently, the relevant sensor data and / or the event data transmitted 250. They can be sent, for example via a wireless data communication, or be read out via the contact interface.
  • the method 200 includes sending 242 the event data and receiving 244 an instruction to determine 240 the relevant sensor data based on the sent event data.
  • the method 200 includes sending 242 the event data and receiving 244 an instruction to determine 240 the relevant sensor data based on the sent event data.
  • the relevant sensor data and / or the event data is compared 260 to an event database and, if a match, such as a similar or similar event, is identified, an instruction is issued 262.
  • the comparison with an event database may also be after the transfer 250 of the relevant sensor data and / or the event data takes place, ie outside the vehicle.
  • the method further comprises first receiving 264 the instruction before the corresponding output 262 occurs.
  • FIG. 3 shows a simple block diagram of the vehicle event detection system 300 of FIG. 1.
  • FIG. 3 shows in the upper half a timeline depicting the temporal relationship of various events or periods in relation to the data stored in the reporter system 310 be processed to report an event 301.
  • the reporter system 310 is connected to the solver system 350 via a data link 390 for data communication, thereby forming the system 300 for detecting vehicle events.
  • the data connection can be wireless.
  • the reporter system 310 includes a first interface component 312 that is configured to receive sensor data 302 about the vehicle, such as during vehicle operation.
  • the sensor data 302 is stored on the rewritable data storage component 322.
  • the reporter system 310 includes a second interface component 314 configured to receive an event indicator 304 relating to the event 301, and a third interface component 316 configured to receive event data 306 relating to the event 301.
  • the receipt of the event indicator 304 and the event data 306 may be staggered, but they are clearly attributable. are denbar.
  • the assignability and the time offset are shown in Figure 3 with the dashed lines.
  • reporter system 310 includes at least one processor component 324 configured to determine time period 308 based on event indicator 304 and further receive sensor data 302 received within specified time period 308 from rewritable data storage component 322 copied to another data storage component 326.
  • the processor component 324 is further configured to determine relevant sensor data 338 from the sensor data copied to the further memory element 326.
  • the reporter system 310 further includes a fourth interface component 318 configured to transmit the relevant sensor data 338 and / or the event data 306 to the solver system 350 via the data link 390.
  • the solver system 350 is used to compute a Instruction 358 for determining the relevant sensor data 338 of a vehicle event 301 and comprises an interface component 352 configured to receive event data 306, a data storage component for storing the event data 306, and at least one processor component 356 for calculating the instruction 358 based on Event data 306.
  • the interface component 352 of the solver system 350 is further configured to send the instruction 358 for determining the relevant sensor data 338 to the reporter system 310 via the data link 390.
  • the relevant sensor data 338 and / or event data 306 can also be transmitted to other receivers via the fourth interface component 318 and / or the interface component 352.
  • a service device for detecting vehicle errors Such a service facility may, for example, have access to a database of event data, such as vehicle error data and associated risks in the presence of the errors.
  • the reporter system 310 or the solver system 350 may have access to such a database to match the relevant sensor data and / or event data with the data in the database. This is illustrated in FIG. 3 with database 370. Database 370 is shown on the system boundaries between the reporter system 310 and the solver system 350.
  • database 370 can be part of one and / or the other system, or also on any other which may be the point at which a data connection can be accessed.
  • a so-called cloud or remote storage is possible here.
  • the advantage of cloud or remote storage is that the database can be updated regularly and many systems can access it.
  • Solver system 350 may also belong to the service facility, so solver system 350 may be part of the data processing system of the service facility.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Economics (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Quality & Reliability (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Traffic Control Systems (AREA)

Abstract

La présente invention concerne un procédé de rapport d'un événement dans un véhicule (101) qui comporte la réception de données de capteur d'au moins un capteur de véhicule (102), le stockage des données de capteur sur un élément de stockage réinscriptible, la réception d'un indicateur d'événement au sujet de l'événement et la détermination d'une période de temps sur la base de l'indicateur d'événement. Le procédé comprend en outre la copie des données de capteur, qui sont reçues au cours de la période de temps, de l'élément de stockage réinscriptible sur un autre élément de stockage ainsi que la réception et le stockage de données d'événement concernant l'événement. Le procédé comprend en outre la détermination de données de capteurs pertinentes parmi les données de capteur qui sont copiées sur l'autre élément de stockage et la communication des données de capteur pertinentes et/ou des données d'événement.
PCT/DE2016/200004 2015-01-12 2016-01-11 Procédé et système pour la détection d'événements de véhicule Ceased WO2016112902A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102015200269.1 2015-01-12
DE102015200269.1A DE102015200269A1 (de) 2015-01-12 2015-01-12 Verfahren und System für die Erfassung von Fahrzeugereignissen

Publications (1)

Publication Number Publication Date
WO2016112902A1 true WO2016112902A1 (fr) 2016-07-21

Family

ID=55699280

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/DE2016/200004 Ceased WO2016112902A1 (fr) 2015-01-12 2016-01-11 Procédé et système pour la détection d'événements de véhicule

Country Status (2)

Country Link
DE (1) DE102015200269A1 (fr)
WO (1) WO2016112902A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE102023131365A1 (de) * 2023-11-10 2025-05-15 Lemken Gmbh & Co. Kg Landwirtschaftliche Arbeitsmaschine
DE102024204414A1 (de) * 2024-05-13 2025-11-13 Knick Elektronische Messgeräte GmbH & Co. KG Verfahren zum Übertragen von Ereignisdaten von einem Feldgerät an eine entfernt gelegene Recheneinrichtung, Computerprogrammprodukt, Feldgerät und System

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1298005A2 (fr) * 2001-09-28 2003-04-02 DaimlerChrysler AG Procédé pour fournir un algorithme de maintenance
US20140032079A1 (en) * 2012-07-26 2014-01-30 Anil Varma Diagnostic and control system and method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1298005A2 (fr) * 2001-09-28 2003-04-02 DaimlerChrysler AG Procédé pour fournir un algorithme de maintenance
US20140032079A1 (en) * 2012-07-26 2014-01-30 Anil Varma Diagnostic and control system and method

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Event-Driven Architecture: Softwarearchitektur für ereignisgesteuerte Geschäftsprozesse", 28 May 2010, SPRINGER, ISBN: 978-3-642-02438-2, article RALF BRUNS ET AL: "Event-Driven Architecture: Softwarearchitektur für ereignisgesteuerte Geschäftsprozesse", pages: 0 - 241, XP055229309 *

Also Published As

Publication number Publication date
DE102015200269A1 (de) 2016-07-14

Similar Documents

Publication Publication Date Title
EP2040957B1 (fr) Procédé et dispositif de contrôle de plausibilité de valeurs de mesure dans l'environnement d'un véhicule à moteur
DE102016120511B4 (de) Fahrzeugfernsteuerung
DE112018005352T5 (de) Informationsverarbeitungsvorrichtung, bewegte einrichtung, verfahren und programm
DE112018001894T5 (de) Steuervorrichtung, Übertragungsverfahren und Computerprogramm
WO2014048518A1 (fr) Procédé et système permettant de déterminer la qualité d'un réseau de radiotéléphonie mobile et de charger des données de radiotéléphonie mobile
DE102018221981B4 (de) Verfahren, Steuereinrichtung und System zum Ermitteln von Profiltiefen von Reifen an Fahrzeugen
WO2018188937A1 (fr) Procédé pour la collecte de données
DE102020206755A1 (de) Redundanzinformationen für objektschnittstelle für hoch und vollautomatisiertes fahren
EP3208775A1 (fr) Enregistrement de données de fonctionnement dans un véhicule automobile
WO2016012387A1 (fr) Dispositif et procédé de détection de défaillance et d'intrusion pour un véhicule automobile
WO2018007050A1 (fr) Procédé et dispositif de traitement de signaux à partir de messages sur au moins deux bus de données, en particulier des bus can, de préférence dans un véhicule, ainsi que système
WO2016112902A1 (fr) Procédé et système pour la détection d'événements de véhicule
DE102015214157A1 (de) Verfahren, System und von einem Computer lesbares Aufzeichnungsmedium für das Steuern eines abnormalen Zustands des Fahrzeugs
DE112020005622T5 (de) Informationsverarbeitungsvorrichtung, Informationsverarbeitungsverfahren und Programm
DE102016000555A1 (de) Verfahren zur Kommunikation zwischen zumindest zwei Fahrzeugen
WO2021175568A1 (fr) Procédé de traitement d'ensembles de données contenant au moins une série chronologique, dispositif de mise en œuvre, véhicule et programme informatique
EP3510577B1 (fr) Concept pour détecter un environnement d'un véhicule à moteur
DE102020113193B4 (de) Verfahren und System zum Verarbeiten von Sensordaten zur Übermittlung an eine zentrale Einheit
DE102016014505A1 (de) Verfahren und System zum Auffinden einer freien Abstellfläche für einen Kraftwagen
WO2014060257A1 (fr) Dispositifs électroniques ainsi que procédé de diagnostic dans un réseau local de données
DE102010042199A1 (de) Verfahren zum Betreiben eines Feldbus-Interface sowie Computerprogrammprodukt
DE102019204198A1 (de) Verfahren zum Überwachen einer Antriebseinheit zum Antreiben eines Kraftfahrzeugs, Computerprogrammprodukt und Kraftfahrzeug
EP3169978B1 (fr) Procédé et dispositif pour acquérir des données dépendantes de la localisation au moyen d'un vehicule
DE102014209199A1 (de) Übertragungsanordnung zum Übertragen von Daten zu einer Datenverarbeitungsstation über ein Kommunikationsnetzwerk
DE102022107588A1 (de) Verfahren und System zum Betreiben von auf ein Kraftfahrzeug bezogenen Datendiensten

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: 16715236

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16715236

Country of ref document: EP

Kind code of ref document: A1