WO2014049352A1 - Système de détection d'un incident sur un véhicule - Google Patents

Système de détection d'un incident sur un véhicule Download PDF

Info

Publication number
WO2014049352A1
WO2014049352A1 PCT/GB2013/052506 GB2013052506W WO2014049352A1 WO 2014049352 A1 WO2014049352 A1 WO 2014049352A1 GB 2013052506 W GB2013052506 W GB 2013052506W WO 2014049352 A1 WO2014049352 A1 WO 2014049352A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
incident
detection system
signal
threshold
Prior art date
Application number
PCT/GB2013/052506
Other languages
English (en)
Inventor
Wayne Gilbert
Jonathan Edward GILBERT
Stephen William COWPER
Original Assignee
Masternaut Risk Solutions Limited
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 Masternaut Risk Solutions Limited filed Critical Masternaut Risk Solutions Limited
Publication of WO2014049352A1 publication Critical patent/WO2014049352A1/fr

Links

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • G07C5/085Registering performance data using electronic data carriers
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Registering or indicating the working of vehicles
    • G07C5/08Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841Registering performance data
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60RVEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R21/00Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
    • B60R21/01Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
    • B60R21/013Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over
    • B60R21/0132Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over responsive to vehicle motion parameters, e.g. to vehicle longitudinal or transversal deceleration or speed value
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B60VEHICLES IN GENERAL
    • B60RVEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R21/00Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
    • B60R21/01Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
    • B60R21/013Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over
    • B60R21/0132Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over responsive to vehicle motion parameters, e.g. to vehicle longitudinal or transversal deceleration or speed value
    • B60R2021/01322Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over responsive to vehicle motion parameters, e.g. to vehicle longitudinal or transversal deceleration or speed value comprising variable thresholds, e.g. depending from other collision parameters
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME 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/00Registering or indicating the working of vehicles
    • G07C5/008Registering or indicating the working of vehicles communicating information to a remotely located station
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/20Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • G08G1/205Indicating the location of the monitored vehicles as destination, e.g. accidents, stolen, rental

Definitions

  • the invention relates to detection of vehicle incidents. Background
  • PHYD pay how you drive
  • PAYD pay as you drive
  • the insurance premium may be determined according to how often, when and where the vehicle is driven. The driver may, for example, pay a premium that allows for a certain amount of usage, and will be billed more if the vehicle is driven more than this amount.
  • Various other options are also available in both types of insurance models, many variants of which are already on the market.
  • Vehicle monitoring systems for use in PHYD models may be more or less sophisticated depending on the level of monitoring required by the insurance provider.
  • vehicle speed and location which may be considered to be basic minimum requirements, other parameters may be monitored such as levels of acceleration or deceleration, which can provide further indications of how safely the vehicle is being driven.
  • Such monitoring systems may also have the ability to provide feedback when the vehicle is involved in an incident such as a collision.
  • One sign of a vehicle being involved in a collision is if an airbag system is tripped as a result of the vehicle decelerating above a certain rate. Linking such an indication with a remote monitoring system can enable an accident notification service that can potentially deliver numerous safety benefits as well as economic benefits to the driver, passengers and other parties such as the insurance providers and emergency services.
  • These benefits may include: the emergency services being able to respond faster to a potentially serious incident with knowledge of the location and severity of the incident; the insurance provided being notified, enabling more efficient claim settlement based on clear evidence of an incident having occurred; and a clearer establishment of liability based on the monitored behaviour of the driver before the incident.
  • a vehicle incident detection system comprising:
  • an accelerometer assembly mounted on the vehicle for measuring acceleration along an axis
  • a vibration sensor rigidly connected to a structural component of the vehicle; a signal processing module connected to the vibration sensor and accelerometer assembly for receiving first and second respective signals therefrom and configured to detect an incident if a magnitude of the first signal exceeds a first threshold; and an event management module configured to store data from the accelerometer assembly and vibration sensor and data relating to the status of the vehicle on detection of the incident by the signal processing module.
  • the invention addresses the above mentioned problem of false triggering by using a combination of sensors configured to detect different parameters relating to the vehicle. While an accelerometer can detect how quickly the vehicle is decelerating, which by itself might suggest a collision, a vibration sensor connected to a structural component of the vehicle can provide confirmation an incident has in fact occurred.
  • the vibration signals can also be used alone to determine whether an incident has occurred, with signals from the accelerometer used to confirm the type of incident.
  • a further advantage is that the vibration sensor can provide further useful information on the type of incident. Experimental work has shown that this significantly improves accident discrimination for low g-force events, in particular for events involving accelerations having a magnitude of less than 2.5g, where the vibration sensor signal can be used to discriminate between a reportable incident and normal use.
  • the signal processing module may be configured to detect an incident if magnitudes of the first and second signals both exceed respective first and second thresholds.
  • the signal processing module may also or alternatively be configured to detect an incident if the magnitude of the first signal exceeds the first threshold and a magnitude of the second signal is below a second threshold.
  • the signal processing module may also be configured to detect an incident if the magnitude of the first signal exceeds a third threshold greater than the first threshold and the magnitude of the second signal is below the second threshold.
  • the second threshold may for example be 2.5g.
  • the event management module is preferably configured to wirelessly transmit a notification of the detected incident to a remote server on or after detection of the incident, the notification optionally including data from the accelerometer assembly and/or vibration sensor and/or data relating to the status of the vehicle.
  • the incident detection system is able to transmit a notification only when an incident is detected, which can be done by the system on the vehicle rather than having to be assessed remotely. This reduces the amount of data needed to be transmitted wirelessly to the remote serve.
  • the data, or a selected portion thereof, may be transmitted along with the notification, but this is not necessary for the notification to be effective.
  • the notification may for example be transmitted over a cellular telephone network.
  • the notification may include an indication of the severity or type of the detected incident, for example as determined using the combination of accelerometer and vibration readings, or from the vibration readings alone.
  • the vibration sensor in the vehicle incident detection system is preferably a piezoelectric sensor.
  • Such sensors are well known in the fields of sensing and actuation covering a wide range of applications, existing applications in vehicles being engine knock sensors, fuel injection systems and ultrasonic parking sensors.
  • the piezoelectric sensor may be configured according to the range of frequencies of vibrations to be detected and the degree of sensitivity required.
  • a typical piezoelectric sensor may for example be in the form of a block or ring, and configured to detect vibrations with a reasonably uniform sensitivity over a wide range of frequencies below the resonant frequency of the sensor itself.
  • the sensor may alternatively be configured such that a resonant frequency of the sensor lies within a range of frequencies of interest, so as to increase the sensitivity of response within this range.
  • Piezoelectric sensors are particularly advantageous because they can be configured to detect a wide range of vibration frequencies directly from the component to which the sensor is attached.
  • the signal processing module of the vehicle incident detection system may be configured to continuously obtain components of the first and/or second signals enabling an incident to be detected quickly and accurately.
  • the accelerometer assembly of the vehicle incident detection system may be configured to sense acceleration along a plurality of axes, the plurality of axes optionally including three mutually orthogonal axes, one of which may be aligned with a direction of travel of the vehicle. Detecting along more than one axis has an advantage of being able, if necessary, to discriminate acceleration/deceleration in a direction of travel or transverse to the direction of travel, thereby providing a further indication of the type of incident.
  • the signal processing system of the vehicle incident detection system may be configured to obtain a magnitude of a force vector derived from sensed acceleration along the plurality of axes, for example from a modulus of a sum of squares of acceleration signals along the plurality of axes.
  • the event management module may be configured to determine and store a measure of severity of the detected incident based on the magnitude, such as the modulus of sum of squares, of the acceleration signals.
  • the measure of severity can be in a straitforward relationship with the magnitude of the modulus, i.e. the higher the modulus the greater the severity.
  • the relationship may for example be linear or logarithmic.
  • the accelerometer assembly may also be configured to sense rotation about a plurality of axes. Sensing rotation as well as direction of acceleration can be useful in, for example, determining whether the incident involves the vehicle rotating, whether this is due to a roll or a spin.
  • the first and/or second thresholds may be dependent on a measure of the current status of the vehicle.
  • the first (or vibration) threshold may be varied up and down depending on the speed of the vehicle, as vibration will tend to increase as the vehicle is driven faster.
  • the current status may be one or more of vehicle speed, engine speed and systemic background noise. Systemic background noise may for example be measured by taking an average of an output of the vibration sensor over time.
  • the detected incident is typically a collision, although other incidents may also be detected.
  • a vehicle incident detection unit configured to be mounted to a vehicle, the unit comprising: a signal processing module having a first input configured to receive a first signal from avibration sensor, a second input configured to receive a second signal from an accelerometer assembly and a third input configured to receive vehicle status signals, the signal processing module configured to detect an incident if a magnitude of the first signal exceeds a first threshold; and
  • an event management module configured to store data from the accelerometer assembly and vibration sensor and data relating to the status of the vehicle on detection of the incident by the signal processing module.
  • the vehicle incident detection unit may further comprise the accelerometer assembly and/or the vibration sensor, for example as part of a kit of parts configured for mounting to a vehicle.
  • the unit may be configured to be connected to an engine management system of the vehicle, from which the unit may receive the vehicle status signals.
  • the various optional and preferable features of the first aspect may also be applied to the second or third aspects of the invention.
  • figure 1 is a schematic block diagram of an exemplary incident detection system
  • figure 2 is a flow chart illustrating an exemplary method according to an aspect of the invention
  • figure 3 is a schematic representation of acceleration and vibration amplitudes as a function of time during an incident
  • figure 4 is a flow chart illustrating an exemplary method of processing a reported incident based on event data
  • figure 5 is a schematic diagram illustrating a system for handling reported incidents
  • figure 6 are exemplary plots of measured acceleration and vibration for a test incident
  • figure 7 is a schematic circuit diagram configured for detection and reporting of an incident.
  • FIGS 7a-7d illustrate detailed partial views of the circuit diagram of figure 7.
  • an in-vehicle system includes a vibration sensor and an accelerometer/gyroscope array, which functions to provide event discrimination at a local level.
  • the devices making up the in-vehicle system may be co-located or alternatively fixed at separate locations to enable ease of installation.
  • the function of the in-vehicle system is detailed in figure 2, as described below.
  • the in-vehicle system connects to a remote server, which can function to provide an average or aggregated input used by the in-vehicle system to further improve event discrimination.
  • FIG. 1 illustrates an exemplary vehicle incident detection system 100, in which a microprocessor 101 functions as a signal processing and event management module.
  • the microprocessor 101 receives signals from an accelerometer 102 and optionally a magnetometer 103, either or both of which may sense in up to 3 axes.
  • the microprocessor 101 also receives a signal from a vibration sensor 104, for example a piezoelectric sensor, optionally via a filter 105 that may be configured to filter out any unwanted frequency ranges. In alternative arrangements the vibration sensor may be sampled directly by the microprocessor 101 and digitally filtered as required.
  • the microprocessor 101 is connected to a memory module 106, such as an erasable electronically programmable read only memory (EEPROM), within which program data for the microprocessor 101 may be stored.
  • the memory 106 may also or alternatively be used for storage of data from the sensors 102, 103, 104.
  • the microprocessor 101 is powered by a battery 107, preferably a rechargeable battery, which is in turn powered by a power supply unit 108, such as a power supply available in the vehicle.
  • the rechargeable battery 107 enables the system 100 to continue functioning in the event power is cut, for example when the vehicle to which the system is connected is involved in an incident that disconnects or otherwise disables the power supply 108.
  • the microprocessor 101 provides one or more input/output interfaces, for example in the form of a USB (universal serial bus) interface 109 and/or an RS232 interface 1 10, either or both of which may be used to extract from or input data or programs to the system 100.
  • An interface such as the USB interface 109, may be used to connect the microprocessor 101 to a wireless transceiver 1 1 1 to allow the system 100 to wirelessly transmit notifications to a remote server, via an aerial 1 12.
  • the transceiver 1 1 1 may also be able to receive data, for example in order to remotely reconfigure or reprogram the microprocessor 101 or to provide notifications to the driver of the vehicle.
  • Figure 2 illustrates a flow diagram of an exemplary method of operation 200, in which data relating to an event is stored and sent, for example to a remote server, in response to a threshold being triggered by one or both of a piezoelectric vibration sensing device or an accelerometer/gyroscope. Outputs from the vibration sensing device and the accelerometer/gyroscope are continually sampled and compared to predetermined limits or thresholds. In the event that a trigger is initiated by either or both signals, a pre-defined event storage algorithm captures the relevant data and prepares it for transmission to the remote server. Events detected without a sufficiently high signal from the vibration sensor may be ignored or can be stored for later evaluation.
  • Event data that is continually being monitored 201 for an accident or other type of event is compared 202 to a threshold 203 relating to a G event, or acceleration. If the acceleration threshold 203 is not exceeded, monitoring continues 201. Once an event is triggered by the threshold 203 being exceeded, a check 204 is made to determine whether an event is also triggered by a signal from the piezoelectric vibration sensor. If not, monitoring continues 201. If an event is triggered by a signal from the piezoelectric sensor exceeding a vibration threshold, the event is stored 205 and a notification of the event is sent 206, optionally along with the event data, to a remote server.
  • the acceleration threshold may for example be around 2.5g.
  • This threshold can be set lower than would otherwise be the case for a system having only acceleration detection, since the vibration sensor can be used to provide improved discrimination between normal events and reportable incidents.
  • the acceleration threshold may be set to be higher and the vibration sensor used to provide increased certainty of the type of event once the acceleration threshold is exceeded.
  • the method of operation may also include continual monitoring, or sampling, 207 of the signal from the piezoelectric vibration sensor, and comparing 208 the signal to a further threshold value 209.
  • the further threshold value 209 may be the same as, or higher than, the vibration threshold value mentioned above in relation to the check to determine whether an event is triggered, or may be different. If this further threshold value 209 alone is exceeded, an event may be triggered, at which point the event data is stored 205 and a notification sent 206.
  • This further optional feature may be used, for example, to detect events where accelerations are too low to trigger an event according to the acceleration threshold, but where the vibrations detected by the vibration sensor indicate that significant damage is likely to have occurred.
  • FIG. 3 illustrates schematic plots of acceleration (figure 3a) and vibration (figure 3b) amplitudes as a function of time, illustrating the types of signals that may indicate an event having occurred that is worth reporting.
  • the acceleration signal 301 which may be a modulus of a measured acceleration in one or more directions, rises above an acceleration threshold 302.
  • a measured vibration amplitude 303 also rises to above a vibration threshold 304.
  • Data relating to the event which includes the acceleration and vibration signals as well as other information such as the time and location of the vehicle, are then recorded.
  • Te The time period between the start and end of the event, defined by Te and Ts, may for example be less than one second.
  • the event information over this time period is stored and a notification is sent to a remote server, in this case indicating that a significant collision is likely to have occurred.
  • Figure 4 illustrates a flow diagram illustrating a mode of operation 400 when an event is triggered.
  • the event data 401 is first assessed to determine whether the risk associated with the event is high 402.
  • the risk may for example relate to a risk of injury of occupants of the vehicle. If the risk is assessed to be high, a first notice of loss (FNOL) process is initiated 403, since it is practically certain that one or more claims will need to be made.
  • a high risk incident may be defined as one where the incident requires immediate action for loss mitigation, and involves a high risk of personal injury.
  • FNOL first notice of loss
  • a medium risk incident may be defined as an incident requiring prompt action for loss mitigation, with a risk of personal injury and damage to the vehicle.
  • an incident process is initiated 407.
  • a low risk incident may be defined as an incident requiring no immediate action, but the incident is added to a driver record and the insurance provided awaits further input such as a claim.
  • the thresholds are updated 408. This process takes incoming event data and compares it to standard data models (thresholds) currently in use. If variances exist, the new values are then shared with similar instances in remote devices, thus continually improving result accuracy.
  • the assessments of risk is preferably undertaken by a server remote from the vehicle for which the event is triggered, but may alternatively be undertaken at least in part by a system onboard the vehicle.
  • Figure 5 illustrates schematically a system 500 incorporating various features relating to the invention.
  • a vehicle 501 incorporating an incident detection system communicates wirelessly with a server 502 on detection of an incident or event that meets the required threshold(s).
  • the server 502 assesses information pertinent to the risk profiles of users, obtained from third parties, and uses this information to configure the sensitivity of algorithms both on the remote target (i.e. the vehicle) and on the server 502. This may be used to compute a current risk status or be used for analysis after an event.
  • This information may for example relate to the weather or traffic conditions at the time and location the incident is detected, and may be obtained by the server by automatic connection to respective databases 505, 506 over the internet 504.
  • the information may be stored along with the event data by the server for future reference.
  • Figures 6a and 6b illustrate exemplary plots of acceleration (figure 6a) and vibration (figure 6b) as measured on a vehicle over a time period within which an incident occurred.
  • Acceleration is measured in g, i.e. in multiples of a nominal gravitational force (i.e. 9.81 Nkg “1 or ms "2 ), while vibration is measured in arbitrary units indicating a relative signal amplitude from the vibration sensor.
  • acceleration is measured in three orthogonal axes: x, y and z.
  • the acceleration readings all indicate a peak. Acceleration in the z axis has the largest peak 604, indicating that the direction of acceleration/deceleration is closest to the z axis. Subsequent smaller peaks occur before the acceleration signals fall away as the energy in the collision is dissipated.
  • the vibration signal 605 also registers a peak value 606, indicating that the collision has resulted in a significant vibrations being set up in the structural component to which the vibration sensor is attached.
  • the peak 605 registers a level of between 1500 and 2000 units, i.e. over three times the maximum level established for systemic background noise.
  • the magnitude of the vibration signal indicates that the event detected by the levels of acceleration indicated in figure 6a was caused by a collision.
  • the vibration signal can be used to evaluate an impact profile, which will be indicative of the type of event recorded.
  • Other signals such as the vehicle speed at the time of the event (or shortly before) can be used to make an assessment of the type of event. If, for example, the vehicle is not moving when the event is recorded this will enable the event to be classified differently to one where the vehicle is moving.
  • Other information such as that relating to the type of road the vehicle is on and the weather, can also be useful in classifying the event.
  • FIG 7 is a schematic circuit diagram showing in more detail the various components of an impact sensing device (ISD) 700 for a vehicle incident detection system of the type described above and illustrated in figure 1 , in which the various components are identifiable as collections of circuit elements.
  • Figures 7a to 7d show the same circuit diagram in more detailed partial views.
  • a central microprocessor 701 is connected to various other circuits, including RS232 and USB interface circuits 710, 709 and a power supply circuit 708 incorporating a battery 707.
  • the microprocessor 701 in this case is a Renesas RX62N, which provides a complete digital subsystem with internal FLASH memory, RAM and data FLASH memory. Extension of the memory system may be provided by an external 64Mb serial FLASH memory device 706 (S25FL064K).
  • the microprocessor 701 also includes analogue to digital conversion devices and is designed to meet automotive environmental requirements. Power generation and management are provided by a switching regulator 71 1 (LM22675), inverting boost regulator 712 (SP5205) and battery management chip 703 (MAX 1555). Internal and external communications are provided by a USB slave port 714 (FT230X) and RS232 transceiver 715 (SP3232E). A magnetometer chip 716 (MAG3 1 10) is provided to assist in orienting the ISD 700.
  • a switching regulator 71 1 LM22675
  • SP5205 inverting boost regulator
  • MAX 1555 battery management chip
  • Internal and external communications are provided by a USB slave port 714 (FT230X) and RS232 transceiver 715 (SP3232E).
  • a magnetometer chip 716 (MAG3 1 10) is provided to assist in orienting the ISD 700.
  • a three-axis linear accelerometer 720 (LIS33 1HH) provides acceleration signals to the microprocessor 701.
  • the microprocessor 701 is programmed to analyse the signals received from the piezoelectric transducer and accelerometer 720 according to the algorithms described above. Data relating to an individual vehicle's behaviour can be gathered on a remote server, allowing typical vehicle profiles to be developed.
  • the vibration sensor is physically attached to a structural member of the vehicle, for example the chassis or frame of the vehicle. This requires no special orientation with respect to the vehicle axes, since vibrations will travel in all directions within the structural component. Best performance is provided with a solid physical connection to a metal component, although connection to any load bearing member should be adequate.
  • the sensor may be attached in various ways such as by using a fast-setting adhesive such as a cyanoacrylate adhesive or epoxy resin, a magnetic attachment, a screw fixing, clamping or any other appropriate method that provides a secure fixing.
  • the accelerometer and/or gyroscope array is preferably aligned to the axes of the vehicle, or alternatively be accommodated by the use of software supporting automatic orientation and calibration of the accelerometer.
  • the calibration system preferably continuously monitors the sensor to ensure that the calibration accommodates the vehicle being parked on inclines in any combination of variation to pitch, roll and yaw.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Mechanical Engineering (AREA)
  • Traffic Control Systems (AREA)

Abstract

La présente invention a trait à la détection d'incidents sur des véhicules. Un mode de réalisation concerne un système de détection d'un incident sur un véhicule (100) comprenant : un véhicule ; un ensemble accéléromètre (102) monté sur le véhicule et destiné à mesurer une accélération le long d'un axe ; un capteur de vibration (104) solidarisé avec un composant structural du véhicule ; un module de traitement de signaux (101) connecté au capteur de vibration (104) et à l'ensemble accéléromètre (102) et conçu pour recevoir des premier et second signaux respectifs provenant de ceux-ci et pour détecter un incident si une amplitude du premier signal est supérieure au premier seuil ; et un module de gestion d'événement conçu pour mémoriser des données provenant de l'ensemble accéléromètre (102) et du capteur de vibration (104), ainsi que des données relatives à l'état du véhicule lors de la détection de l'incident par le module de traitement de signaux (101).
PCT/GB2013/052506 2012-09-26 2013-09-26 Système de détection d'un incident sur un véhicule WO2014049352A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB1217189.8A GB2506365B (en) 2012-09-26 2012-09-26 Vehicle incident detection
GB1217189.8 2012-09-26

Publications (1)

Publication Number Publication Date
WO2014049352A1 true WO2014049352A1 (fr) 2014-04-03

Family

ID=47190651

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2013/052506 WO2014049352A1 (fr) 2012-09-26 2013-09-26 Système de détection d'un incident sur un véhicule

Country Status (2)

Country Link
GB (1) GB2506365B (fr)
WO (1) WO2014049352A1 (fr)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10055909B2 (en) 2016-07-08 2018-08-21 Calamp Corp. Systems and methods for crash determination
CN109102587A (zh) * 2018-07-24 2018-12-28 中国华能集团清洁能源技术研究院有限公司 设备行驶数据的监测器和监测方法
US10214166B2 (en) 2015-06-11 2019-02-26 Calamp Corp. Systems and methods for impact detection with noise attenuation of a sensor signal
US10395438B2 (en) 2016-08-19 2019-08-27 Calamp Corp. Systems and methods for crash determination with noise filtering
US10466269B2 (en) 2013-02-19 2019-11-05 Calamp Corp. Systems and methods for low latency 3-axis accelerometer calibration
US10473750B2 (en) 2016-12-08 2019-11-12 Calamp Corp. Systems and methods for tracking multiple collocated assets
US10599421B2 (en) 2017-07-14 2020-03-24 Calamp Corp. Systems and methods for failsafe firmware upgrades
US10645551B2 (en) 2016-10-12 2020-05-05 Calamp Corp. Systems and methods for radio access interfaces
US11924303B2 (en) 2017-11-06 2024-03-05 Calamp Corp. Systems and methods for dynamic telematics messaging

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8977426B2 (en) 2012-06-04 2015-03-10 Geotab Inc. VIN based accelerometer threshold
GB2522728A (en) * 2014-01-31 2015-08-05 Cambridge Consultants Monitoring device
US9754325B1 (en) 2014-05-20 2017-09-05 State Farm Mutual Automobile Insurance Company Autonomous vehicle operation feature monitoring and evaluation of effectiveness
US10373259B1 (en) * 2014-05-20 2019-08-06 State Farm Mutual Automobile Insurance Company Fully autonomous vehicle insurance pricing
US9972054B1 (en) 2014-05-20 2018-05-15 State Farm Mutual Automobile Insurance Company Accident fault determination for autonomous vehicles
NO342828B1 (en) * 2016-02-03 2018-08-13 Abax As Device for detection of external damage to chassis of a vehicle
JP2019531560A (ja) 2016-07-05 2019-10-31 ナウト, インコーポレイテッドNauto, Inc. 自動運転者識別システムおよび方法
WO2018031678A1 (fr) 2016-08-09 2018-02-15 Nauto Global Limited Système et procédé de localisation de précision et de cartographie
JP6940612B2 (ja) 2016-09-14 2021-09-29 ナウト, インコーポレイテッドNauto, Inc. ニアクラッシュ判定システムおよび方法
US10733460B2 (en) 2016-09-14 2020-08-04 Nauto, Inc. Systems and methods for safe route determination
WO2018085804A1 (fr) 2016-11-07 2018-05-11 Nauto Global Limited Système et procédé de détermination de distraction d'un conducteur
US10417816B2 (en) 2017-06-16 2019-09-17 Nauto, Inc. System and method for digital environment reconstruction
EP3638542B1 (fr) 2017-06-16 2022-01-26 Nauto, Inc. Système et procédé de détermination de fonctionnement contextualisé d'un véhicule
WO2018229550A1 (fr) 2017-06-16 2018-12-20 Nauto Global Limited Système et procédé de détermination d'événement de véhicule dommageable
GB2568053A (en) * 2017-11-01 2019-05-08 Charles Handsaker Joseph Vehicle monitoring system for capturing vehicle incidents
NO344614B1 (en) * 2017-11-03 2020-02-10 Dtecto As System for detection of vehicle body damage
EP3759700B1 (fr) 2018-02-27 2023-03-15 Nauto, Inc. Procédé de détermination de directives de conduite
ES2736901A1 (es) 2018-06-29 2020-01-08 Geotab Inc Caracterización de una colisión de vehículo
DE102018211421A1 (de) * 2018-07-10 2020-01-16 Zf Friedrichshafen Ag Aufzeichnungssystem mit unabhängiger Versorgung
GB2595516A (en) * 2020-05-29 2021-12-01 Appy Risk Tech Limited Device for vehicle monitoring and system including same
US11862022B2 (en) 2021-02-03 2024-01-02 Geotab Inc. Methods for characterizing a vehicle collision
US11884285B2 (en) 2021-02-03 2024-01-30 Geotab Inc. Systems for characterizing a vehicle collision
US11941986B2 (en) 2021-02-03 2024-03-26 Geotab Inc. Methods for characterizing a low-impact vehicle collision using high-rate acceleration data

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5825286A (en) * 1995-05-08 1998-10-20 Semisystems, Inc. Vehicular data collection and transmission system and method
US6735506B2 (en) * 1992-05-05 2004-05-11 Automotive Technologies International, Inc. Telematics system
US20080147280A1 (en) * 1995-06-07 2008-06-19 Automotive Technologies International, Inc. Method and apparatus for sensing a rollover
US20110202305A1 (en) * 2010-02-12 2011-08-18 Webtech Wireless Inc. Monitoring Aggressive Driving Operation of a Mobile Asset
US20120224827A1 (en) * 2011-03-03 2012-09-06 Data Tec Co., Ltd. Operation management device to be mounted to a moving object, portable information terminal, operation management server, and computer program

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH03296661A (ja) * 1990-04-16 1991-12-27 Casio Comput Co Ltd 車載用データ処理装置
WO1999040545A1 (fr) * 1998-02-09 1999-08-12 I-Witness, Inc. Systeme de stockage d'images sequentielles conservant l'historique d'un evenement
JP2000233707A (ja) * 1999-02-15 2000-08-29 Asuko Kk 乗員保護装置用制御システム
US20030081942A1 (en) * 2001-10-29 2003-05-01 Visteon Global Technologies, Inc. Video recorder for an automobile
US20120146809A1 (en) * 2010-12-13 2012-06-14 Samsung Electronics Co. Ltd. Information providing apparatus and method for vehicles
CN102303608B (zh) * 2011-06-16 2013-11-06 大连理工大学 嵌入式移动互联智能助驾系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735506B2 (en) * 1992-05-05 2004-05-11 Automotive Technologies International, Inc. Telematics system
US5825286A (en) * 1995-05-08 1998-10-20 Semisystems, Inc. Vehicular data collection and transmission system and method
US20080147280A1 (en) * 1995-06-07 2008-06-19 Automotive Technologies International, Inc. Method and apparatus for sensing a rollover
US20110202305A1 (en) * 2010-02-12 2011-08-18 Webtech Wireless Inc. Monitoring Aggressive Driving Operation of a Mobile Asset
US20120224827A1 (en) * 2011-03-03 2012-09-06 Data Tec Co., Ltd. Operation management device to be mounted to a moving object, portable information terminal, operation management server, and computer program

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11480587B2 (en) 2013-02-19 2022-10-25 CalAmpCorp. Systems and methods for low latency 3-axis accelerometer calibration
US10466269B2 (en) 2013-02-19 2019-11-05 Calamp Corp. Systems and methods for low latency 3-axis accelerometer calibration
US10214166B2 (en) 2015-06-11 2019-02-26 Calamp Corp. Systems and methods for impact detection with noise attenuation of a sensor signal
US11570529B2 (en) 2016-07-08 2023-01-31 CalAmpCorp. Systems and methods for crash determination
US10055909B2 (en) 2016-07-08 2018-08-21 Calamp Corp. Systems and methods for crash determination
US10395438B2 (en) 2016-08-19 2019-08-27 Calamp Corp. Systems and methods for crash determination with noise filtering
US10645551B2 (en) 2016-10-12 2020-05-05 Calamp Corp. Systems and methods for radio access interfaces
US10473750B2 (en) 2016-12-08 2019-11-12 Calamp Corp. Systems and methods for tracking multiple collocated assets
US11022671B2 (en) 2016-12-08 2021-06-01 Calamp Corp Systems and methods for tracking multiple collocated assets
US10599421B2 (en) 2017-07-14 2020-03-24 Calamp Corp. Systems and methods for failsafe firmware upgrades
US11436002B2 (en) 2017-07-14 2022-09-06 CalAmpCorp. Systems and methods for failsafe firmware upgrades
US11924303B2 (en) 2017-11-06 2024-03-05 Calamp Corp. Systems and methods for dynamic telematics messaging
CN109102587A (zh) * 2018-07-24 2018-12-28 中国华能集团清洁能源技术研究院有限公司 设备行驶数据的监测器和监测方法

Also Published As

Publication number Publication date
GB2506365B (en) 2017-12-20
GB201217189D0 (en) 2012-11-07
GB2506365A (en) 2014-04-02

Similar Documents

Publication Publication Date Title
WO2014049352A1 (fr) Système de détection d'un incident sur un véhicule
EP2481037B1 (fr) Dispositif d'aide à la conduite, système de détection d'un accident de véhicule et procédé de détection d'un accident de véhicule
JP5659939B2 (ja) 車両検出システム、車載機およびセンター
US20170200331A1 (en) Telematics devices and methods for vehicle speeding detection
CN108025719A (zh) 用于分析和管理由车辆的配备有传感器的制动系统生成的数据的设备
US11015311B2 (en) System for detecting an impact of a vehicle against a road safety device
CN105383416A (zh) 用于事件数据记录的激活与记录的方法和设备
EP2412588A1 (fr) Motocyclette et dispositif de signalement de vol installé sur la motocyclette
US20130253760A1 (en) Vehicle Text-Cell Sensor
US10861260B2 (en) Driving behaviour monitoring systems
JP2018531337A6 (ja) 道路安全装置及び道路安全装置群に対する車両の衝突を検出するための、道路安全装置のモニタリングのシステム及び方法
CN112750337A (zh) 一种限高架碰撞无线报警系统及其报警方法
KR101469708B1 (ko) 자동차 급발진 및 주행 상태 통합 관리 블랙박스 시스템
US11455847B2 (en) Method and apparatus for obtaining event related data
CN113727211B (zh) 数据处理方法、装置、服务器、系统
CN214067977U (zh) 一种限高架碰撞无线报警系统
CN212569136U (zh) 充电桩防撞报警电路
CN112977339A (zh) 一种车辆油箱防盗报警方法和系统
US20170349127A1 (en) Safety system for a vehicle of a vehicle fleet
KR20050014907A (ko) 차량의 운행상태 검출을 위한 블랙박스 및 이를 이용한차량용 운행 안전 관리 시스템
CN102917921A (zh) 用于对车辆用行人探测装置进行监控的方法
CN106564441B (zh) 一种车载无线智能控制系统
KR20170100246A (ko) 급발진 감지를 위한 페달 움직임 측정 센서 모듈
CN107707587B (zh) 控制方法、服务器、车辆检测器及车辆检测系统
AU2021105007A4 (en) AN IoT ENABLED HEAVY VEHICLE DETECTION SYSTEM FOR RESTRICTED AREA

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13785577

Country of ref document: EP

Kind code of ref document: A1