US20100106417A1 - System and method for identifying a trajectory for each vehicle involved in an accident - Google Patents
System and method for identifying a trajectory for each vehicle involved in an accident Download PDFInfo
- Publication number
- US20100106417A1 US20100106417A1 US12/266,598 US26659808A US2010106417A1 US 20100106417 A1 US20100106417 A1 US 20100106417A1 US 26659808 A US26659808 A US 26659808A US 2010106417 A1 US2010106417 A1 US 2010106417A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- accident
- gnss location
- gnss
- location
- 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.)
- Granted
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
- 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/0841—Registering performance data
- G07C5/085—Registering performance data using electronic data carriers
-
- 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
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F25—REFRIGERATION OR COOLING; COMBINED HEATING AND REFRIGERATION SYSTEMS; HEAT PUMP SYSTEMS; MANUFACTURE OR STORAGE OF ICE; LIQUEFACTION SOLIDIFICATION OF GASES
- F25J—LIQUEFACTION, SOLIDIFICATION OR SEPARATION OF GASES OR GASEOUS OR LIQUEFIED GASEOUS MIXTURES BY PRESSURE AND COLD TREATMENT OR BY BRINGING THEM INTO THE SUPERCRITICAL STATE
- F25J2290/00—Other details not covered by groups F25J2200/00 - F25J2280/00
- F25J2290/10—Mathematical formulae, modeling, plot or curves; Design methods
Definitions
- the present invention relates generally to accident reconstruction, and more particularly to identifying a trajectory for each vehicle involved in an accident.
- the shock of the situation may impair one party's ability to remember and/or articulate the events immediately preceding the accident or subsequent thereto.
- the present invention provides a method for identifying a trajectory for each vehicle involved in an accident, said method comprising:
- GNSS Global Navigation Satellite System
- FIG. 1 illustrates a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention.
- FIG. 2 illustrates an accident reconstruction comprising an initial trajectory of a vehicle involved in an accident, in accordance with embodiments of the present invention.
- FIG. 3 illustrates an accident reconstruction comprising a trajectory of a vehicle involved in an accident utilizing Bezier curves to approximate the complete path of the vehicle, in accordance with embodiments of the present invention.
- FIG. 4 illustrates an accident reconstruction comprising a trajectory of a vehicle involved in an accident and further identifying locations within the trajectory where the vehicle lost traction, in accordance with embodiments of the present invention.
- FIG. 5 illustrates a computer system which may facilitate a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention.
- GNSS Global Navigation Satellite System
- GPS Global Positioning System
- Galileo Galileo
- GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya
- IRNSS Indian Regional Navigational Satellite System
- DORIS Doppler Orbitography
- DORIS Quasi-Zenith Satellite System
- Beidou Navigation System Beidou Navigation System.
- FIG. 1 illustrates a method 100 for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention.
- the present invention utilizes an accident report created by at least one vehicle involved in an accident.
- Vehicles involved in the accident not only include those vehicles which physically participated in the accident, but also include vehicles within a predetermined distance which may be witnesses to the accident/incident.
- the accident report comprises information taken from each vehicle involved in the accident.
- the accident report comprises for each vehicle involved in the accident: a list of indices indeed (i), a list of timestamps (T i ), a list of Global Navigation Satellite System (GNSS) locations (x i , y i ), as well as a list of the specific vehicle's orientation (Dx i , Dy i ).
- Each orientation pair (Dx i , Dy i ) not only identify the direction in which the vehicle is pointing, but also represent a measurement of the vehicle's speed along the x-axis and along the y-axis.
- Each timestamp corresponds to both a unique GNSS location and a unique orientation.
- An example of data residing in an accident report for a single vehicle may be as follows:
- Method 100 begins with step 102 , which comprises building a trajectory for a vehicle involved in the accident.
- Step 102 comprises building a trajectory for a vehicle involved in the accident. Utilizing the accident report, step 102 overlays onto a Cartesian Coordinate Plane all GNSS locations (x i , y i ) for a vehicle involved in an accident.
- the GNSS locations correspond to a path a vehicle took prior to, during, and subsequent to an accident.
- the GNSS locations are overlaid on the Cartesian Coordinate Plane so a path may be drawn through the GNSS locations in the order of the timestamps (T i ).
- I represents the total number of timestamps corresponding to a specific vehicle which reside in the accident report.
- step 106 comprises calculating X 0 , X 1 , X 2 , X 3 , Y 0 , Y 1 , Y 2 , and Y 3 .
- Step 106 comprises calculating X 0 , X 1 , X 2 , X 3 , Y 0 , Y 1 , Y 2 , and Y 3 .
- the values X 0 , X 1 , X 2 , X 3 , Y 0 , Y 1 , Y 2 , and Y 3 are coordinate characteristics of a cubic Bezier curve used to approximate the intermediate GNSS locations between timestamps for the vehicle involved in the accident.
- the coordinate characteristics of the cubic Bezier curve are calculated as follows:
- step 108 prepares the method 100 for calculating all intermediate GNSS locations between timestamps T i and T i+1 .
- j does not begin at T i , mainly because the GNSS location of the vehicle at time T i was already overlaid on the Cartesian Coordinate Plane pursuant to step 102 , supra.
- step 110 which calculates Lambda ( ⁇ ).
- Step 110 calculates Lambda ( ⁇ ) as a relative time offset for the interval between GNSS locations.
- Step 110 utilizes index z to calculate Lambda ( ⁇ ) according to
- step 110 ends and the method 100 continues with step 112 which comprises plotting XX and YY on the Cartesian Coordinate Plane.
- Step 112 comprises plotting XX and YY on the Cartesian Coordinate Plane. Before plotting XX and YY on the Cartesian Coordinate Plane, step 112 must first calculate both XX and YY. Coordinate XX,YY is calculated according to the following functions:
- XX X 0 *(1 ⁇ ) 3 +3 +X 1 * ⁇ *(1 ⁇ ) 2 +3* X 2 * ⁇ 2 *(1 ⁇ )+ X 3 * ⁇ 3
- YY Y 0 *(1 ⁇ ) 3 +3 +Y 1 * ⁇ *(1 ⁇ ) 2 +3* Y 2 * ⁇ 2 *(1 ⁇ )+ Y 3 * ⁇ 3
- the goal of steps 108 through 114 is to approximate the intermediate GNSS locations between timestamps for the vehicle involved in the accident. It is assumed that the i timestamps are spaced uniformly apart in time. For example, using the accident report data provide supra, the timestamps are spaced apart every ten (10) seconds.
- step 118 comprises identifying instances of speeding and/or skidding.
- Step 118 comprises identifying instances of speeding and/or skidding. Step 118 identifies whether the vehicle was speeding by calculating the average speed of the vehicle between timestamps T i and T i+1 . Since the timestamps are uniformly spaced apart and coupled with the fact that the GNSS locations identify location, the calculation of
- Average ⁇ ⁇ Speed Distance ⁇ ⁇ Traveled Time ⁇ ⁇ of ⁇ ⁇ Travel
- step 118 marks the approximate GNSS locations between T i and T i+1 on the Cartesian Coordinate Plane in such a way that it is understood to an end user that the vehicle was speeding. For an example of the identifying marks, see 414 in FIG. 4 , infra.
- the speed threshold is equal to the speed limit on the road the vehicles was traveling and is provided in the accident report. In an alternative embodiment of the present invention, the speed threshold value is provided by an end user.
- Step 118 also identifies whether the vehicle was skidding between timestamps T i and T i+1 .
- Skidding refers to an unexpected or uncontrollable sliding on a surface by something not rotating (i.e. the vehicle tires).
- Step 118 identifies instances of skidding by reviewing the intermediate GNSS locations between timestamps T i and T i+1 and comparing that information with the vehicle's orientation (Dx i , Dy i ) at time T i . If the vehicle orientation when compared to the path produced by the intermediate GNSS locations exceeds a skid threshold, step 118 marks the Cartesian Coordinate Plane in such a way that it is understood to an end user that the vehicle was skidding. For an example of the identifying marks, see 402 in FIG. 4 , infra. In one embodiment of the present invention the skid threshold is provided by an end user.
- Step 124 comprises determining whether vehicle information pertaining to another vehicle resides in the accident report.
- the method 100 overlays the trajectories for all vehicles involved in the accident onto the Cartesian Coordinate Plane. Therefore, step 124 determines whether the method 100 has overlaid all vehicle information residing in the accident report to the Cartesian Coordinate Plane. If all vehicles have been processed pursuant to steps 102 through 124 , then step 124 returns a value that no additional vehicle information resides in the accident report; and the method 100 continues with step 126 which comprises storing the trajectories to an output device 910 (see FIG. 5 , infra).
- step 124 returns a value that yes additional vehicle information resides in the accident report; and the method loops back to step 102 to perform steps 102 through 124 for a different vehicle.
- Step 126 comprises storing the trajectories to an output device 910 (see FIG. 5 , infra). After completion of step 126 , the method 100 ends.
- FIG. 2 illustrates a Cartesian Coordinate Plane 200 comprising an initial trajectory of a vehicle involved in an accident, in accordance with embodiments of the present invention.
- the Cartesian Coordinate Plane 200 comprises GNSS locations 0 through 10 for one of the vehicles involved in the accident.
- the Cartesian Coordinate Plane 200 illustrated herein was produced pursuant to step 102 , see FIG. 1 , supra.
- FIG. 3 illustrates a Cartesian Coordinate Plane 300 comprising a trajectory of a vehicle involved in an accident utilizing Bezier curves to approximate the complete path of the vehicle, in accordance with embodiments of the present invention.
- the Cartesian Coordinate Plane 300 comprises GNSS locations 0 through 10 for one of the vehicles involved in the accident.
- FIG. 3 further includes the intermediate GNSS locations 302 between timestamps for the vehicle involved in the accident.
- the intermediate GNSS locations 302 (as well as all intermediate locations between successive timestamps) were calculated between two timestamps pursuant to step 104 through 114 , see FIG. 1 , supra.
- the entire Cartesian Coordinate Plane 300 illustrated herein was produced pursuant to steps 102 through 114 , see FIG. 1 , supra.
- FIG. 4 illustrates a Cartesian Coordinate Plane 400 comprising a trajectory of a vehicle involved in an accident and further identifying locations within the trajectory where the vehicle was speeding or lost traction, in accordance with embodiments of the present invention.
- the Cartesian Coordinate Plane 400 comprises GNSS locations 0 through 10 for one of the vehicles involved in the accident.
- the Plane 400 further includes the intermediate GNSS locations between known GNSS locations 0 through 10 for the vehicle involved in the accident.
- 414 represents the marks made pursuant to step 118 (see FIG. 1 , supra) that identify when the vehicle involved in the accident was speeding.
- the intermediate GNSS locations identified as stars 414 are different enough to signify to an end user that the vehicle's speed was exceeding the speed threshold between GNSS locations 0 and 1 .
- the Plane 400 includes marks that convey to an end user the vehicle was skidding. These marks are represented by the rectangles 402 through 412 .
- the marks 402 through 412 signify to an end user that the vehicle's orientation was exceeding the skid threshold throughout the trajectory from GNSS locations 4 through 9 .
- the entire Cartesian Coordinate Plane 400 illustrated herein was produced pursuant to steps 102 through 120 , see FIG. 1 , supra.
- FIG. 5 illustrates a computer system 900 which may facilitate a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention.
- the computer system 900 comprises a processor 908 , an input device 906 coupled to the processor 908 , an output device 910 coupled to the processor 908 , and memory devices 902 and 912 each coupled to the processor 908 .
- the input device 906 may be, inter alia, a keyboard, a mouse, a keypad, a touchscreen, a voice recognition device, a sensor, a network interface card (NIC), a Voice/video over Internet Protocol (VoIP) adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, etc.
- NIC network interface card
- VoIP Voice/video over Internet Protocol
- the output device 910 may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, a NIC, a VoIP adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, an audio and/or visual signal generator, a light emitting diode (LED), etc.
- the memory devices 902 and 912 may be, inter alia, a cache, a dynamic random access memory (DRAM), a read-only memory (ROM), a hard disk, a floppy disk, a magnetic tape, an optical storage such as a compact disc (CD) or a digital video disc (DVD), etc.
- the memory device 912 includes a computer code 914 which is a computer program that comprises computer-executable instructions.
- the computer code 914 includes, inter alia, an algorithm used for identifying a trajectory for each vehicle involved in an accident according to the present invention.
- the processor 908 executes the computer code 914 .
- the memory device 902 includes input data 904 .
- the input data 904 includes input required by the computer code 914 .
- the output device 910 displays output from the computer code 914 .
- Either or both memory devices 902 and 912 may be used as a computer usable medium (or a computer readable medium or a program storage device) having a computer readable program embodied therein and/or having other data stored therein, wherein the computer readable program comprises the computer code 914 .
- a computer program product (or, alternatively, an article of manufacture) of the computer system 900 may comprise said computer usable medium (or said program storage device).
- any of the components of the present invention can be deployed, managed, serviced, etc. by a service provider that offers to deploy or integrate computing infrastructure with respect to a process for identifying a trajectory for each vehicle involved in an accident.
- the present invention discloses a process for supporting computer infrastructure, comprising integrating, hosting, maintaining and deploying computer-readable code into a computing system (e.g., computing system 900 ), wherein the code in combination with the computing system is capable of performing a method for identifying a trajectory for each vehicle involved in an accident.
- the invention provides a business method that performs the process steps of the invention on a subscription, advertising and/or fee basis. That is, a service provider, such as a Solution Integrator, can offer to create, maintain, support, etc. a process for authenticating an end user. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- a service provider such as a Solution Integrator
- the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- FIG. 5 shows the computer system 900 as a particular configuration of hardware and software
- any configuration of hardware and software as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with the particular computer system 900 of FIG. 5 .
- the memory devices 902 and 912 may be portions of a single memory device rather than separate memory devices.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Traffic Control Systems (AREA)
Abstract
Description
- The present invention relates generally to accident reconstruction, and more particularly to identifying a trajectory for each vehicle involved in an accident.
- It is common for an automobile accident to occur in which the only witness is the offending party. When the offending party fails to provide contact information, the innocent victim is left without a means of identifying the responsible party or determining who was at fault.
- Similarly, when two parties are involved in an automobile accident, the shock of the situation may impair one party's ability to remember and/or articulate the events immediately preceding the accident or subsequent thereto.
- The present invention provides a method for identifying a trajectory for each vehicle involved in an accident, said method comprising:
- plotting at least one Global Navigation Satellite System (GNSS) location on a Cartesian Coordinate Plane, each GNSS location of said at least one GNSS location corresponding to a unique vehicle having been involved in said accident;
- identifying a GNSS location of said at least one GNSS location on said Cartesian Coordinate Plane if it was determined that said vehicle was speeding at said identified GNSS location;
- marking a GNSS location of said at least one GNSS location on said Cartesian Coordinate Plane if it was determined that said vehicle was skidding at said marked GNSS location;
- repeating said plotting and said identifying and said marking for at least one other vehicle having been involved in said accident; and
- sending said Cartesian Coordinate Plane to an output device.
-
FIG. 1 illustrates a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention. -
FIG. 2 illustrates an accident reconstruction comprising an initial trajectory of a vehicle involved in an accident, in accordance with embodiments of the present invention. -
FIG. 3 illustrates an accident reconstruction comprising a trajectory of a vehicle involved in an accident utilizing Bezier curves to approximate the complete path of the vehicle, in accordance with embodiments of the present invention. -
FIG. 4 illustrates an accident reconstruction comprising a trajectory of a vehicle involved in an accident and further identifying locations within the trajectory where the vehicle lost traction, in accordance with embodiments of the present invention. -
FIG. 5 illustrates a computer system which may facilitate a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention. - Definitions The term ‘Global Navigation Satellite System (GNSS)’ as used herein is defined as a satellite navigation system providing autonomous geo-spatial positioning with global coverage. Examples of GNSS include, inter alia, Global Positioning System (GPS), Galileo, GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (GLONASS), Indian Regional Navigational Satellite System (IRNSS), Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), Quasi-Zenith Satellite System (QZSS), and Beidou Navigation System.
- Although certain embodiments of the present invention are described herein, it is understood modifications may be made to the present invention without departing from its course and scope. Scope of the present invention is not limited to the number of constituting components, the materials thereof, the shapes thereof, the relative arrangement thereof, etc. Furthermore, while the accompanying drawings illustrate certain embodiments of the present invention, such drawings are not necessarily depicted to scale.
-
FIG. 1 illustrates amethod 100 for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention. - The present invention utilizes an accident report created by at least one vehicle involved in an accident. Vehicles involved in the accident not only include those vehicles which physically participated in the accident, but also include vehicles within a predetermined distance which may be witnesses to the accident/incident.
- The accident report comprises information taken from each vehicle involved in the accident. The accident report comprises for each vehicle involved in the accident: a list of indices indeed (i), a list of timestamps (Ti), a list of Global Navigation Satellite System (GNSS) locations (xi, yi), as well as a list of the specific vehicle's orientation (Dxi, Dyi). Each orientation pair (Dxi, Dyi) not only identify the direction in which the vehicle is pointing, but also represent a measurement of the vehicle's speed along the x-axis and along the y-axis. Each timestamp corresponds to both a unique GNSS location and a unique orientation. An example of data residing in an accident report for a single vehicle may be as follows:
-
Index (i) Time (Ti) xi yi Dxi Dyi 1 0 2 8 0.5 −2.5 2 10 3 4 0.5 −1.5 3 20 4 3 1 1 4 30 6 6 0.75 1.5 5 40 7 8 1 1 6 50 8 8 0 −1 7 60 7 4 0 −2 8 70 8 3 1 −1 9 80 8 2 −1 −1 10 90 6 2 −2 0 11 100 1 2 −4 0 -
Method 100 begins withstep 102, which comprises building a trajectory for a vehicle involved in the accident. -
Step 102 comprises building a trajectory for a vehicle involved in the accident. Utilizing the accident report,step 102 overlays onto a Cartesian Coordinate Plane all GNSS locations (xi, yi) for a vehicle involved in an accident. The GNSS locations correspond to a path a vehicle took prior to, during, and subsequent to an accident. The GNSS locations are overlaid on the Cartesian Coordinate Plane so a path may be drawn through the GNSS locations in the order of the timestamps (Ti). After completion ofstep 102, themethod 100 continues withstep 104 which comprises setting index i=1. -
Step 104 comprises setting index i=1. By setting index i=1,step 104 prepares themethod 100 for calculating all intermediate GNSS locations between timestamps Ti for i=1, 2, . . . , I. I represents the total number of timestamps corresponding to a specific vehicle which reside in the accident report. After completion ofstep 104, themethod 100 continues withstep 106 which comprises calculating X0, X1, X2, X3, Y0, Y1, Y2, and Y3. -
Step 106 comprises calculating X0, X1, X2, X3, Y0, Y1, Y2, and Y3. The values X0, X1, X2, X3, Y0, Y1, Y2, and Y3 are coordinate characteristics of a cubic Bezier curve used to approximate the intermediate GNSS locations between timestamps for the vehicle involved in the accident. The coordinate characteristics of the cubic Bezier curve are calculated as follows: -
- After calculating X0, X1, X2, X3, Y0, Y1, Y2, and Y3,
step 106 is complete and themethod 100 continues withstep 108 which comprises setting index j=Ti+1. -
Step 108 comprises setting indeed j=Ti+1. By setting index j=Ti30 1,step 108 prepares themethod 100 for calculating all intermediate GNSS locations between timestamps Ti and Ti+1. Note that j does not begin at Ti, mainly because the GNSS location of the vehicle at time Ti was already overlaid on the Cartesian Coordinate Plane pursuant tostep 102, supra. After completion ofstep 108, themethod 100 continues withstep 110 which calculates Lambda (λ). -
Step 110 calculates Lambda (λ) as a relative time offset for the interval between GNSS locations. Before calculating Lambda (λ),step 110 first determines index z so that z satisfies the condition where Tz≦j<Tz+1. For example, if i=3, Ti=20, and j=24, then index z must satisfy the condition Tz≦j<Tz+1. Since j=24, the condition index z must satisfy is Tz≦24<Tz+1. Since T3=20 and 20<24, T3 can equal Tz. Thus 20≦24<30 and index z satisfies the condition where z=3. -
Step 110 utilizes index z to calculate Lambda (λ) according to -
- Thus, if i=3, Ti=20, j=24, and z=3, then
-
- After calculating Lambda (λ),
step 110 ends and themethod 100 continues withstep 112 which comprises plotting XX and YY on the Cartesian Coordinate Plane. -
Step 112 comprises plotting XX and YY on the Cartesian Coordinate Plane. Before plotting XX and YY on the Cartesian Coordinate Plane,step 112 must first calculate both XX and YY. Coordinate XX,YY is calculated according to the following functions: -
XX=X 0*(1−λ)3+3+X 1*λ*(1−λ)2+3*X 2*λ2*(1−λ)+X 3*λ3 -
YY=Y 0*(1−λ)3+3+Y 1*λ*(1−λ)2+3*Y 2*λ2*(1−λ)+Y 3*λ3 - After calculating XX and YY, step 112 plots XX,YY on the Cartesian Coordinate Plane. After completion of
step 112, themethod 100 continues withstep 114 which comprises determining if j=Ti+1−1. - Step 114 which comprises determining if j=Ti+1−1. The goal of
steps 108 through 114 is to approximate the intermediate GNSS locations between timestamps for the vehicle involved in the accident. It is assumed that the i timestamps are spaced uniformly apart in time. For example, using the accident report data provide supra, the timestamps are spaced apart every ten (10) seconds. - Plotting XX,YY utilizing index j is performed every one second from Ti to Ti+1−1. Thus using the provided accident report data, steps 108 through 114 would approximate the GNSS location of the vehicle involved in the accident every one second between Ti+1 and Ti+1−1. If j does equal Ti+1−1,
method 100 continues withstep 118 which comprises identifying instances of speeding and/or skidding. - However, if j does not equal Ti+1−1, then the
method 100 continues by increases index j by one (i.e. j=j+1) instep 116 and looping back to step 110 to performsteps 110 through 114 for the updated j. - Step 118 comprises identifying instances of speeding and/or skidding. Step 118 identifies whether the vehicle was speeding by calculating the average speed of the vehicle between timestamps Ti and Ti+1. Since the timestamps are uniformly spaced apart and coupled with the fact that the GNSS locations identify location, the calculation of
-
- is relatively simple for
step 118 to perform. If the average speed of the vehicle exceeds a speed threshold, step 118 marks the approximate GNSS locations between Ti and Ti+1 on the Cartesian Coordinate Plane in such a way that it is understood to an end user that the vehicle was speeding. For an example of the identifying marks, see 414 inFIG. 4 , infra. - In one embodiment of the present invention, the speed threshold is equal to the speed limit on the road the vehicles was traveling and is provided in the accident report. In an alternative embodiment of the present invention, the speed threshold value is provided by an end user.
- Step 118 also identifies whether the vehicle was skidding between timestamps Ti and Ti+1. Skidding refers to an unexpected or uncontrollable sliding on a surface by something not rotating (i.e. the vehicle tires). Step 118 identifies instances of skidding by reviewing the intermediate GNSS locations between timestamps Ti and Ti+1 and comparing that information with the vehicle's orientation (Dxi, Dyi) at time Ti. If the vehicle orientation when compared to the path produced by the intermediate GNSS locations exceeds a skid threshold, step 118 marks the Cartesian Coordinate Plane in such a way that it is understood to an end user that the vehicle was skidding. For an example of the identifying marks, see 402 in
FIG. 4 , infra. In one embodiment of the present invention the skid threshold is provided by an end user. After completion ofstep 118, themethod 100 continues withstep 120 which comprises determining whether i=I. - Step 120 comprises determining whether i=I. Value I represents the total number of timestamps (Ti) corresponding to a single vehicle that was involved in the accident. If i=I,
method 100 completed approximating the intermediate GNSS locations between timestamps for the vehicle involved in the accident; and themethod 100 continues withstep 124 which comprises determining whether vehicle information pertaining to another vehicle resides in the accident report. - However, if i does not equal I, then the
method 100 continues by increases index i by one (i.e. i=i+1) in step 122 and looping back to step 104 to performsteps 104 through 120 for the updated i. - Step 124 comprises determining whether vehicle information pertaining to another vehicle resides in the accident report. The
method 100 overlays the trajectories for all vehicles involved in the accident onto the Cartesian Coordinate Plane. Therefore,step 124 determines whether themethod 100 has overlaid all vehicle information residing in the accident report to the Cartesian Coordinate Plane. If all vehicles have been processed pursuant tosteps 102 through 124, then step 124 returns a value that no additional vehicle information resides in the accident report; and themethod 100 continues withstep 126 which comprises storing the trajectories to an output device 910 (seeFIG. 5 , infra). - However, if all vehicles have not been processed pursuant to
steps 102 through 124, then step 124 returns a value that yes additional vehicle information resides in the accident report; and the method loops back to step 102 to performsteps 102 through 124 for a different vehicle. - Step 126 comprises storing the trajectories to an output device 910 (see
FIG. 5 , infra). After completion ofstep 126, themethod 100 ends. -
FIG. 2 illustrates a Cartesian CoordinatePlane 200 comprising an initial trajectory of a vehicle involved in an accident, in accordance with embodiments of the present invention. - The Cartesian Coordinate
Plane 200 comprisesGNSS locations 0 through 10 for one of the vehicles involved in the accident. The Cartesian CoordinatePlane 200 illustrated herein was produced pursuant to step 102, seeFIG. 1 , supra. -
FIG. 3 illustrates a Cartesian CoordinatePlane 300 comprising a trajectory of a vehicle involved in an accident utilizing Bezier curves to approximate the complete path of the vehicle, in accordance with embodiments of the present invention. - The Cartesian Coordinate
Plane 300 comprisesGNSS locations 0 through 10 for one of the vehicles involved in the accident.FIG. 3 further includes theintermediate GNSS locations 302 between timestamps for the vehicle involved in the accident. Specifically, the intermediate GNSS locations 302 (as well as all intermediate locations between successive timestamps) were calculated between two timestamps pursuant to step 104 through 114, seeFIG. 1 , supra. The entire Cartesian CoordinatePlane 300 illustrated herein was produced pursuant tosteps 102 through 114, seeFIG. 1 , supra. -
FIG. 4 illustrates a Cartesian CoordinatePlane 400 comprising a trajectory of a vehicle involved in an accident and further identifying locations within the trajectory where the vehicle was speeding or lost traction, in accordance with embodiments of the present invention. - The Cartesian Coordinate
Plane 400 comprisesGNSS locations 0 through 10 for one of the vehicles involved in the accident. ThePlane 400 further includes the intermediate GNSS locations betweenknown GNSS locations 0 through 10 for the vehicle involved in the accident. 414 represents the marks made pursuant to step 118 (seeFIG. 1 , supra) that identify when the vehicle involved in the accident was speeding. The intermediate GNSS locations identified asstars 414 are different enough to signify to an end user that the vehicle's speed was exceeding the speed threshold between 0 and 1.GNSS locations - Additionally, the
Plane 400 includes marks that convey to an end user the vehicle was skidding. These marks are represented by therectangles 402 through 412. Themarks 402 through 412 signify to an end user that the vehicle's orientation was exceeding the skid threshold throughout the trajectory fromGNSS locations 4 through 9. The entire Cartesian CoordinatePlane 400 illustrated herein was produced pursuant tosteps 102 through 120, seeFIG. 1 , supra. -
FIG. 5 illustrates acomputer system 900 which may facilitate a method for identifying a trajectory for each vehicle involved in an accident, in accordance with embodiments of the present invention. - The
computer system 900 comprises aprocessor 908, aninput device 906 coupled to theprocessor 908, anoutput device 910 coupled to theprocessor 908, and 902 and 912 each coupled to thememory devices processor 908. - The
input device 906 may be, inter alia, a keyboard, a mouse, a keypad, a touchscreen, a voice recognition device, a sensor, a network interface card (NIC), a Voice/video over Internet Protocol (VoIP) adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, etc. - The
output device 910 may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, a NIC, a VoIP adapter, a wireless adapter, a telephone adapter, a dedicated circuit adapter, an audio and/or visual signal generator, a light emitting diode (LED), etc. - The
902 and 912 may be, inter alia, a cache, a dynamic random access memory (DRAM), a read-only memory (ROM), a hard disk, a floppy disk, a magnetic tape, an optical storage such as a compact disc (CD) or a digital video disc (DVD), etc. Thememory devices memory device 912 includes acomputer code 914 which is a computer program that comprises computer-executable instructions. - The
computer code 914 includes, inter alia, an algorithm used for identifying a trajectory for each vehicle involved in an accident according to the present invention. Theprocessor 908 executes thecomputer code 914. Thememory device 902 includesinput data 904. Theinput data 904 includes input required by thecomputer code 914. Theoutput device 910 displays output from thecomputer code 914. Either or bothmemory devices 902 and 912 (or one or more additional memory devices not shown inFIG. 5 ) may be used as a computer usable medium (or a computer readable medium or a program storage device) having a computer readable program embodied therein and/or having other data stored therein, wherein the computer readable program comprises thecomputer code 914. Generally, a computer program product (or, alternatively, an article of manufacture) of thecomputer system 900 may comprise said computer usable medium (or said program storage device). - Any of the components of the present invention can be deployed, managed, serviced, etc. by a service provider that offers to deploy or integrate computing infrastructure with respect to a process for identifying a trajectory for each vehicle involved in an accident. Thus, the present invention discloses a process for supporting computer infrastructure, comprising integrating, hosting, maintaining and deploying computer-readable code into a computing system (e.g., computing system 900), wherein the code in combination with the computing system is capable of performing a method for identifying a trajectory for each vehicle involved in an accident.
- In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising and/or fee basis. That is, a service provider, such as a Solution Integrator, can offer to create, maintain, support, etc. a process for authenticating an end user. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement, and/or the service provider can receive payment from the sale of advertising content to one or more third parties.
- While
FIG. 5 shows thecomputer system 900 as a particular configuration of hardware and software, any configuration of hardware and software, as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with theparticular computer system 900 of FIG. 5. For example, the 902 and 912 may be portions of a single memory device rather than separate memory devices.memory devices - While particular embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.
Claims (25)
XX=X 0*(1−λ)3+3+X 1*λ*(1−λ)2+3*X 2*λ2*(1−λ)+X 3*λ3; and YY=Y 0*(1−λ)3+3+Y 1*λ*(1−λ)2+3*Y 2*λ2*(1−λ)+Y 3*λ3.
XX=X 0*(1−λ)3+3+X 1*λ*(1−λ)2+3*X 2*λ2*(1−λ)+X 3*λ3; and YY=Y 0*(1−λ)3+3+Y 1*λ*(1−λ)2+3*Y 2*λ2*(1−λ)+Y 3*λ3.
XX=X 0*(1−λ)3+3+X 1*λ*(1−λ)2+3*X 2*λ2*(1−λ)+X 3*λ3; and YY=Y 0*(1−λ)3+3+Y 1*λ*(1−λ)2+3*Y 2*λ2*(1−λ)+Y 3*λ3.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EPEP08305732.3 | 2008-10-27 | ||
| EP08305732 | 2008-10-27 | ||
| EP08305732 | 2008-10-27 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20100106417A1 true US20100106417A1 (en) | 2010-04-29 |
| US10657738B2 US10657738B2 (en) | 2020-05-19 |
Family
ID=42118312
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/266,598 Active 2034-06-20 US10657738B2 (en) | 2008-10-27 | 2008-11-07 | Reconstructing an accident for a vehicle involved in the accident |
Country Status (1)
| Country | Link |
|---|---|
| US (1) | US10657738B2 (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102607553A (en) * | 2012-03-06 | 2012-07-25 | 北京建筑工程学院 | Travel track data-based stroke identification method |
| CN107980109A (en) * | 2017-01-04 | 2018-05-01 | 深圳配天智能技术研究院有限公司 | Robot motion's method for planning track and relevant apparatus |
| US20240056299A1 (en) * | 2022-08-03 | 2024-02-15 | Hangzhou Normal University | Traffic accident forensics method based on blockchain |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10467783B2 (en) * | 2018-02-23 | 2019-11-05 | ExoAnalytic Solutions, Inc. | Visualization interfaces for real-time identification, tracking, and prediction of space objects |
| AU2020319085C1 (en) | 2019-07-25 | 2024-12-05 | ExoAnalytic Solutions, Inc. | Systems and visualization interfaces for orbital paths and path parameters of space objects |
| WO2024050163A2 (en) | 2022-07-29 | 2024-03-07 | ExoAnalytic Solutions, Inc. | Space object alert management and user interfaces |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5296852A (en) * | 1991-02-27 | 1994-03-22 | Rathi Rajendra P | Method and apparatus for monitoring traffic flow |
| US5446659A (en) * | 1993-04-20 | 1995-08-29 | Awaji Ferryboat Kabushiki Kaisha | Traffic accident data recorder and traffic accident reproduction system |
| US5628033A (en) * | 1995-09-28 | 1997-05-06 | Triodyne, Inc. | Accident investigation and reconstruction mapping with aerial photography |
| US20020059086A1 (en) * | 2000-10-02 | 2002-05-16 | Steven Wahlbin | Computerized method and system of displaying a roadway configuration relating to an accident |
| US20030046003A1 (en) * | 2001-09-06 | 2003-03-06 | Wdt Technologies, Inc. | Accident evidence recording method |
| US6675074B2 (en) * | 2001-08-21 | 2004-01-06 | Robert Bosch Gmbh | Method and system for vehicle trajectory estimation |
| US20040102984A1 (en) * | 2002-11-27 | 2004-05-27 | Stefan Wahlbin | Computerized method and system for estimating liability using recorded vehicle data |
| US20050137757A1 (en) * | 2003-05-06 | 2005-06-23 | Joseph Phelan | Motor vehicle operating data collection and analysis |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6141611A (en) | 1998-12-01 | 2000-10-31 | John J. Mackey | Mobile vehicle accident data system |
| WO2000028410A1 (en) | 1998-11-06 | 2000-05-18 | Phoenix Group, Inc. | Mobile vehicle accident data system |
| US6246933B1 (en) | 1999-11-04 | 2001-06-12 | BAGUé ADOLFO VAEZA | Traffic accident data recorder and traffic accident reproduction system and method |
| US6741168B2 (en) | 2001-12-13 | 2004-05-25 | Samsung Electronics Co., Ltd. | Method and apparatus for automated collection and transfer of collision information |
| EP1324274A3 (en) | 2001-12-28 | 2005-11-02 | Matsushita Electric Industrial Co., Ltd. | Vehicle information recording system |
| JP4001529B2 (en) | 2002-09-03 | 2007-10-31 | 三井住友海上火災保険株式会社 | Accident situation recording device, negligence diagnosis system, accident information recording method, negligence diagnosis method, and program |
| JP2005100107A (en) | 2003-09-25 | 2005-04-14 | Nec Corp | Property-damage-only accident detection system for preventing hit-and-run |
| US7317397B2 (en) | 2004-05-29 | 2008-01-08 | Rodney Melvin Gunsauley | Method and apparatus for using RFID's in the investigation of motor vehicle accidents |
| WO2006053676A1 (en) | 2004-11-18 | 2006-05-26 | Wacker Chemie Ag | Process for preparing element halides |
| US7327238B2 (en) | 2005-06-06 | 2008-02-05 | International Business Machines Corporation | Method, system, and computer program product for determining and reporting tailgating incidents |
| JP2006168717A (en) | 2005-07-01 | 2006-06-29 | Maruhama:Kk | Vehicle drive recorder |
| US20070150140A1 (en) | 2005-12-28 | 2007-06-28 | Seymour Shafer B | Incident alert and information gathering method and system |
| WO2008007878A1 (en) | 2006-07-10 | 2008-01-17 | Ubtechnology Co., Ltd | Black box system for vehicle |
-
2008
- 2008-11-07 US US12/266,598 patent/US10657738B2/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5296852A (en) * | 1991-02-27 | 1994-03-22 | Rathi Rajendra P | Method and apparatus for monitoring traffic flow |
| US5446659A (en) * | 1993-04-20 | 1995-08-29 | Awaji Ferryboat Kabushiki Kaisha | Traffic accident data recorder and traffic accident reproduction system |
| US5628033A (en) * | 1995-09-28 | 1997-05-06 | Triodyne, Inc. | Accident investigation and reconstruction mapping with aerial photography |
| US20020059086A1 (en) * | 2000-10-02 | 2002-05-16 | Steven Wahlbin | Computerized method and system of displaying a roadway configuration relating to an accident |
| US6675074B2 (en) * | 2001-08-21 | 2004-01-06 | Robert Bosch Gmbh | Method and system for vehicle trajectory estimation |
| US20030046003A1 (en) * | 2001-09-06 | 2003-03-06 | Wdt Technologies, Inc. | Accident evidence recording method |
| US20040102984A1 (en) * | 2002-11-27 | 2004-05-27 | Stefan Wahlbin | Computerized method and system for estimating liability using recorded vehicle data |
| US20050137757A1 (en) * | 2003-05-06 | 2005-06-23 | Joseph Phelan | Motor vehicle operating data collection and analysis |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102607553A (en) * | 2012-03-06 | 2012-07-25 | 北京建筑工程学院 | Travel track data-based stroke identification method |
| CN107980109A (en) * | 2017-01-04 | 2018-05-01 | 深圳配天智能技术研究院有限公司 | Robot motion's method for planning track and relevant apparatus |
| US20240056299A1 (en) * | 2022-08-03 | 2024-02-15 | Hangzhou Normal University | Traffic accident forensics method based on blockchain |
| US12407508B2 (en) * | 2022-08-03 | 2025-09-02 | Hangzhou Normal University | Traffic accident forensics method based on blockchain |
Also Published As
| Publication number | Publication date |
|---|---|
| US10657738B2 (en) | 2020-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6904637B2 (en) | Systems and methods for determining transport stop locations | |
| CN102122400B (en) | Smart road-toll-system | |
| US11085778B2 (en) | Method and apparatus for providing opportunistic intermodal routes with shared vehicles | |
| US10657738B2 (en) | Reconstructing an accident for a vehicle involved in the accident | |
| US20140257969A1 (en) | Methods and apparatus to measure exposure to mobile advertisements | |
| US20180245934A1 (en) | Identifying a map matched trip from received geographic position information | |
| CN102177750A (en) | System and method for preventing cell phone use while driving | |
| AU2014244449A1 (en) | Determining an amount for a toll based on location data points provided by a computing device | |
| CN111951554A (en) | Illegal parking road information acquisition method and system | |
| US11531116B2 (en) | Methods and systems for detecting potential interference with a tracking device associated with a vehicle | |
| US20110223939A1 (en) | System For Tracking Text Messaging While Driving | |
| JP2018530835A (en) | System for providing city planning tools | |
| EP4300336A1 (en) | Method, apparatus, and computer program product for estimating the privacy risk of anonymized trajectory data | |
| US10497256B1 (en) | Method, apparatus, and system for automatic evaluation of road closure reports | |
| Jensen et al. | The INFATI data | |
| CN111024116A (en) | Prompting method and device for prohibiting parking, storage medium and electronic equipment | |
| US20220229868A1 (en) | Method and apparatus for automated map object conflict resolution via map event normalization and augmentation | |
| US10163339B2 (en) | Monitoring traffic congestion | |
| JP2004240688A (en) | Traffic condition monitoring system for vehicle, its configuring device, traffic condition monitoring method, and computer program | |
| US20230331239A1 (en) | Method, apparatus and vehicle for adaptively evaluating a driver's performance in safe driving | |
| Lopez et al. | Assessment of smartphone positioning data quality in the scope of citizen science contributions | |
| Ou et al. | Big data processing and analysis on the impact of COVID-19 on public transport delay | |
| Walcott-Bryant et al. | Harsh brakes at potholes in Nairobi: Context-based driver behavior in developing cities | |
| AU2018262456B2 (en) | Dynamic support information based on contextual information | |
| Bagheri et al. | A Computational Framework for Revealing Competitive Travel Times with Low‐Carbon Modes Based on Smartphone Data Collection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAUCHOT, FREDERIC;CLEMENT, JEAN-YVES;MARMIGERE, GERARD;AND OTHERS;SIGNING DATES FROM 20081104 TO 20081106;REEL/FRAME:021800/0746 Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION,NEW YO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAUCHOT, FREDERIC;CLEMENT, JEAN-YVES;MARMIGERE, GERARD;AND OTHERS;SIGNING DATES FROM 20081104 TO 20081106;REEL/FRAME:021800/0746 |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED |
|
| STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
| AS | Assignment |
Owner name: KYNDRYL, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:057885/0644 Effective date: 20210930 Owner name: KYNDRYL, INC., NEW YORK Free format text: ASSIGNMENT OF ASSIGNOR'S INTEREST;ASSIGNOR:INTERNATIONAL BUSINESS MACHINES CORPORATION;REEL/FRAME:057885/0644 Effective date: 20210930 |
|
| MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |