Impact monitoring system

Abstract

An impact monitoring system for a vehicle includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations performed by the data processing hardware include receiving sensor data from a plurality of sensors disposed along the vehicle and identifying an impact event based on the sensor data. The sensor data and the identified impact event are compared to a series of impact thresholds, and an impact score is determined based on the comparison of the sensor data and the identified impact event to the series of impact thresholds. The impact score is compared to an impact score hierarchy, the impact score hierarchy corresponding to a series of impact thresholds, and an impact event is monitored using updated sensor data.

Description

[0001] introduction

[0002] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent described in this section and in aspects of the description that may not otherwise be identified as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art against the present disclosure. Technical Field

[0003] The present disclosure generally relates to an impact monitoring system for a vehicle. Background Art

[0004] Vehicles travel along a road system and encounter many external factors during travel. As a result, engagement with the vehicle may cause components of the vehicle to change, which may affect the functionality of the vehicle. While some vehicles are equipped with sensors that can provide an indication that an event has occurred, most vehicles utilize a blanket system that does not necessarily differentiate between severity levels or event types. Summary of the invention

[0005] In some aspects, a computer-implemented method, when executed by data processing hardware, causes data processing hardware to perform operations, including receiving sensor data from a plurality of sensors disposed along a vehicle. Identifying an impact event based on the sensor data, and comparing the sensor data and the identified impact event to a series of impact thresholds. Determining an impact score based on the comparison of the sensor data and the identified impact event to the series of impact thresholds. Comparing the impact score to a hierarchy of impact scores. The impact score hierarchy corresponds to a series of impact thresholds and includes a first layer of impact scores, a second layer of impact scores, and a third layer of impact scores. Notifying an operator of the vehicle of the impact event based on the impact score and the hierarchy of impact scores. Monitoring the impact event using updated sensor data, and determining an estimated distance traveled based on the impact event and the updated sensor data.

[0006] In some examples, the impact event can be determined as having an intermediate impact score that can correspond to the second layer of the impact score hierarchy. In response to the determined intermediate impact score, the data processing hardware can recommend the operator to check the impact of the vehicle. In other examples, the impact event can be determined as having a high impact score that can correspond to the third layer of the impact score hierarchy. In response to the determined high impact score, the data processing hardware can receive communications from a communication server to facilitate the operation of the vehicle. Optionally, if the impact event has a high impact score, a pull-over location can be identified. In some examples, the component operation duration can be determined, and the component operation duration can be notified to the operator of the vehicle. The service date of the component corresponding to the component operation duration can be determined, and a notification including the service date can be issued. In some cases, the impact event can be notified to a third-party device.

[0007] In other aspects, a crash monitoring system for a vehicle includes data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations performed by the data processing hardware include receiving sensor data from a plurality of sensors disposed along the vehicle and identifying a crash event based on the sensor data. The sensor data and the identified crash event are compared to a series of crash thresholds, and a crash score is determined based on the comparison of the sensor data and the identified crash event to the series of crash thresholds. The crash score is compared to a crash score hierarchy, the crash score hierarchy corresponding to a series of crash thresholds, and the crash event is monitored using the updated sensor data.

[0008] In some examples, an estimated driving duration is determined based on the impact event and the updated sensor data. A component operation duration may be determined, and the component operation duration may be notified to an operator of the vehicle. Optionally, a notification may be issued identifying the impact event based on a crash score and a crash score hierarchy. The impact event may be determined to have a low impact score that may correspond to a first-tier impact score of the crash score hierarchy. In response to the determined low impact score, a notification may be issued including a recommended service date. In some cases, the impact event and the impact score may be notified to a third-party device. Optionally, the impact monitoring system may recommend an inspection of the vehicle in response to the impact event and the determined impact score.

[0009] In other aspects, the impact monitoring system may include data processing hardware and memory hardware in communication with the data processing hardware. The memory hardware stores instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations. The operations performed by the data processing hardware include receiving sensor data from a plurality of sensors disposed along the vehicle and identifying impact events based on the sensor data. Comparing the sensor data and the identified impact events with a series of impact thresholds, and determining an impact score based on the comparison of the sensor data and the identified impact events with a series of impact thresholds. Comparing the impact score with a hierarchy of impact scores. The hierarchy of impact scores corresponds to a series of impact thresholds. Using updated sensor data to monitor impact events.

[0010] In some examples, the impact score hierarchy includes a first layer impact score, a second layer impact score, and a third layer impact score, and a series of impact thresholds include a low impact threshold, an intermediate impact threshold, and a high impact threshold. It can be determined that the impact event has a high impact score based on the high impact threshold. The high impact score can correspond to the third layer impact score of the impact score hierarchy. In response to the determined high impact score, a notification indicating the determined high impact score and including a pullover recommendation can be issued. In some cases, a communication can be received from a communication server to facilitate the operation of the vehicle and recommend a pullover location for the pullover event. Optionally, a notification of the impact event and the determined high impact score can be issued to a third-party device. An estimated travel distance can be determined based on the impact event and updated sensor data. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure.

[0012] Figure 1 is a perspective view of a vehicle according to the present disclosure on a road;

[0013] Figure 2 is a partial perspective view of an interior cabin of a vehicle according to the present disclosure;

[0014] Figure 3 is a perspective view of an impact event according to the present disclosure;

[0015] Figure 4 According to the present disclosure Figure 3 A perspective view of an impact event, wherein the vehicle is in a pull-over position;

[0016] Figure 5 is a functional block diagram of an impact monitoring system according to the present disclosure;

[0017] Figure 6 is an example flow chart of an impact monitoring system according to the present disclosure;

[0018] Figure 7 yes Figure 6 An example flow chart of an impact monitoring system; and

[0019] Figure 8 yes Figure 7 An example flow chart of an impact monitoring system.

[0020] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0021] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those of ordinary skill in the art that specific details need not be employed, that example configurations may be implemented in many different forms, and that the specific details and example configurations should not be construed as limiting the scope of the present disclosure.

[0022] The terms used herein are only used for the purpose of describing specific exemplary configurations and are not intended to be limiting. As used herein, the singular articles "a", "an" and "the" may also be intended to include plural forms unless the context clearly indicates otherwise. The terms "comprises", "comprising", "including" and "having" are inclusive and therefore specify the presence of features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts and / or groups thereof. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or shown, unless specifically identified as an execution order. Additional or alternative steps may be adopted.

[0023] When an element or layer is referred to as being "on another element or layer," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, directly engaged with, connected to, attached to, or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on another element or layer," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there may be no intermediate elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more associated listed items.

[0024] The terms "first", "second", "third", etc. can be used here to describe various elements, components, regions, layers and / or parts. These elements, components, regions, layers and / or parts should not be limited by these terms. These terms can only be used to distinguish an element, component, region, layer or part from another region, layer or part. Unless the context clearly indicates, terms such as "first", "second" and other numerical terms do not imply order or sequence. Therefore, without departing from the teaching of the example configuration, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part.

[0025] In this application, including the definitions below, the term "module" may be replaced with the term "circuit". The term "module" may refer to, be part of, or include: an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or grouped) that executes code; a processor (shared, dedicated, or grouped) that stores code executed by a memory; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0026] The term "code" as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class and / or an object. The term "shared processor" covers a single processor that executes some or all codes from multiple modules. The term "group processor" covers a processor that executes some or all codes from one or more modules in combination with an additional processor. The term "shared memory" covers a single memory that stores some or all codes from multiple modules. The term "group memory" includes a memory that stores some or all codes from one or more modules in combination with an additional memory. The term "memory" may be a subset of the term "computer-readable medium". The term "computer-readable medium" does not include transient electrical signals and electromagnetic signals propagated through the medium, and therefore can be considered to be tangible and non-transient memory. Non-limiting examples of non-temporary memory include tangible computer-readable media, which include non-volatile memory, magnetic memory, and optical memory.

[0027] The devices and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include and / or rely on stored data.

[0028] A software application (i.e., software resource) may refer to computer software that enables a computing device to perform tasks. In some examples, a software application may be referred to as an "application," "app," or "program." Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0029] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.

[0030] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, apparatus, and / or device (e.g., disk, optical disk, processor, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable device, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0031] Various implementations of the systems and techniques described herein can be realized in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system that includes at least one programmable processor, which may be special-purpose or general-purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and to send data and instructions to the storage system, at least one input device, and at least one output device.

[0032] The process and logic flow described in this specification can be performed by one or more programmable processors (also referred to as data processing hardware), which execute one or more computer programs to perform functions by operating on input data and generating outputs. The process and logic flow can also be performed by a dedicated logic circuit (e.g., FPGA (field programmable gate array) or ASIC (application-specific integrated circuit)). As an example, a processor suitable for executing a computer program includes both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more large-capacity storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably connected to receive data from it or transmit data to it or both. However, a computer does not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0033] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0034] Reference Figures 1 to 8, the vehicle 10 includes a body 12 equipped with a crash monitoring system 100. In some aspects of the present disclosure, the vehicle 10 is an electric vehicle (EV) with autonomous or semi-autonomous capabilities. Additionally or alternatively, the vehicle 10 can be configured with an internal combustion engine (ICE). In other aspects, the vehicle 10 can be a hybrid vehicle that combines EV and ICE components and capabilities.

[0035] The vehicle body 12 can be generally divided into a vehicle front portion 14 proximate a front bumper 16 of the vehicle body 12 and a vehicle rear portion 18 proximate a rear bumper 20. Figure 1 As shown, the vehicle 10 includes a plurality of sensors 22 that may be incorporated into various elements of the vehicle body 12, including, but not limited to, rearview mirrors 24, front bumper 16, and rear bumper 20. For example, a tire pressure sensor 22a may be configured to detect pressure changes within one or more tires 26 of the vehicle 10. The sensors 22 may also include other vehicle sensors 22, including, but not limited to, proximity sensors, light detection and ranging (LIDAR) sensors, and imaging sensors that may be incorporated as part of the vehicle body 12.

[0036] Reference now Figures 2 to 5 , the interior 28 of the vehicle 10 is defined by the body 12 and includes an interior rearview mirror 24a and a display device 30. The interior rearview mirror 24a can be equipped with one or more of the plurality of sensors 22, including but not limited to an imager 22b. It is also contemplated that the imager 22b can be positioned on the exterior rearview mirror 24b. The imager 22b is configured to capture the surrounding vehicle environment, as further described below.

[0037] The display device 30 may be located at an instrument panel 32 of the vehicle 10 and configured to display information related to the vehicle 10 to an occupant of the vehicle 10, including a driver or operator. In some aspects, the display device 30 may be a head-up display (HUD) integrated with a windshield 34 of the vehicle 10. In other examples, the display device 30 may be a tablet device integrated with the instrument panel 32 and configured with a capacitive sensor for operating functions of the display device 30. As described in more detail below, the display device 30 may display information related to the vehicle 10 to the operator before, during, and after operation of the vehicle 10.

[0038] Further references Figure 2-5, the crash monitoring system 100 is communicatively coupled to the display device 30 and the sensor 22. The crash monitoring system 100 is integrated with the vehicle 10 and includes data processing hardware 102 and memory hardware 104, which can each be configured as part of a vehicle controller 106. The data processing hardware 102 is configured to perform operations of the crash monitoring system 100, and the memory hardware communicates with the data processing hardware 102 and stores instructions that, when executed on the data processing hardware 102, cause the data processing hardware 102 to perform operations. The operations performed by the data processing hardware 102 can include launching a crash monitoring application 108 that can be stored in the memory hardware 104.

[0039] The crash monitoring application 108 may be configured as a user-facing interface for the crash monitoring system 100. The crash monitoring application 108 receives and merges sensor data 40 from the plurality of sensors 22 and vehicle data 110 stored in the memory hardware 104. The vehicle controller 106 may display the crash monitoring application 108 on the display device 30. As described herein, the crash monitoring application 108 may present a notification 112 on the display device 30 in response to a crash event 114. The crash event 114 may be categorized as an event that affects an operational function of the vehicle 10. Examples of crash events 114 may include, but are not limited to, one or more engagements of a pothole or other road object in the tires 26, punctures of one or more of the tires 26, cracks in the suspension of the vehicle 10, engagement between an external object and the vehicle 10, changes in alignment, repetitive clicking or rattling noises, exhaust effects, and other examples. For example, Figure 3 and Figure 4 The impact event 114 shown in FIG. 4 corresponds to one of the tires 26 being in a flattened state after engaging a pothole 400 along a road 402 .

[0040] Further references Figure 2-5 , the crash monitoring system 100 can interconnect the vehicle controller 106 with the GPS processor 200 and the network 300. The vehicle controller 106 can also include a transmission device 50 of the vehicle 10 that is communicatively coupled to the network 300 to transmit the audio message from the communication server 302 to the operator of the vehicle 10. The transmission device 50 can also utilize the communication server 302 to transmit the vehicle data 110 and the crash event 114 stored on the vehicle controller 106. The transmission device 50 can at least partially communicatively couple the vehicle controller 106 to the network 300 for wireless communication capabilities, including wireless calling and emergency communications in some aspects. In some examples, the transmission device 50 is a transmission device that includes operating functions. The system's operating functions include, but are not limited to, in-vehicle safety, emergency services, turn-by-turn navigation, and remote diagnostics that may be performed at least in part between the vehicle controller 106 and the network 300 .

[0041] The vehicle controller 106 is also communicatively coupled to the GPS processor 200 via the network 300 to provide GPS data 202, such as a GPS location 204 of the vehicle 10, to the impact monitoring system 100. For example, the GPS data 202 may include surrounding geographic locations 206 corresponding to the route of the vehicle 10 and environmental information 208 relative to the vehicle 10 monitored during transportation and at a stationary position. The environmental information 208 includes information including, but not limited to, road conditions, road curvature, road grade, building locations, and terrain information. The environmental information 208 may include additional environmental information 208 related to the surrounding environment of the vehicle 10, which may be facilitated for transmission to the vehicle controller 106. The impact monitoring system 100 may query the GPS processor 200 for the GPS data 202 in response to the impact event 114, as described below.

[0042] The GPS processor 200 transmits the geographic location 206 and the environmental information 208 to the vehicle controller 106 via the network 300. As described above, the network 300 may include a communication server 302 that is communicatively coupled to the transmission device 50 to send and receive signals. For example, the communication server 302 may obtain the GPS data 202 from the GPS processor 200 and communicate the GPS data 202 directly to the operator or driver of the vehicle 10 via the transmission device 50. In some examples, the communication server 302 may also transmit the GPS data 202 to the vehicle controller 106 for analysis as part of the impact monitoring system 100. In other examples, the communication server 302 is configured to provide roadside assistance to the operator of the vehicle 10 in response to the impact event 114. Although the transmitted GPS data 202 may be included as part of the roadside assistance, it is also contemplated that the communication server 302 may provide step-by-step instructions for responding to the impact event 114 where appropriate.

[0043] Still reference Figure 2-5 In some aspects, the vehicle data 110 stored in the memory hardware 104 includes information related to the speed of the vehicle 10, the mechanical condition of the vehicle 10, and the electrical condition of the vehicle 10. The vehicle data 110 may also include other information about the vehicle 10, such as range information and / or, in the EV example, the battery life of the vehicle 10. The vehicle controller 106 may utilize the vehicle data 110 in conjunction with the sensor data 40 to monitor the vehicle environment during operation of the vehicle 10 and during various vehicle processes.

[0044] For example, the crash monitoring system 100 may detect a change in speed that may be inconsistent with the operator's execution, which may at least partially inform the crash event 114. In some cases, a rapid decrease in speed after the crash event 114 may indicate potential damage to the vehicle 10. When evaluating the vehicle data 110 in view of the crash event 114, the crash monitoring system 100 may identify the decrease in speed. In other examples, the crash event 114 may be the result of an electrical crash event 114 (such as a thermal runaway event). It is contemplated that the crash event 114 generally corresponds to any event that may impact or otherwise affect the operation of the vehicle 10.

[0045] The vehicle controller 106 is configured to continuously receive sensor data 40 from each of the plurality of sensors 22. The data processing hardware 102 processes the sensor data 40 and monitors for potential impact events 114. In some examples, multiple impact events 114 may be detected from the sensor data 40. For example, if the vehicle 10 engages a pothole, the sensor data 40 may include data corresponding to tire pressure loss and suspension impact from the tire pressure sensor 22a. In other examples, a single impact event 114 may be detected. The sensor data 40 may also include image data from the imager 22b, which may inform the impact event 114 and subsequent evaluation by the impact monitoring system 100. The data processing hardware 102 may identify one or more impact events 114 and compare to a series of impact thresholds 116 stored in the memory hardware 104.

[0046] A series of impact thresholds 116 include a low impact threshold 116a, an intermediate impact threshold 116b, and a high impact threshold 116c. Each impact threshold 116 includes a range of impact events 114. In some examples, the impact events 114 may cumulatively exceed one or more of the impact thresholds 116, such that isolated impact events 114 may be classified based on the lower impact thresholds 116, but cumulative impact events 114 may alternatively be classified based on the higher impact thresholds 116. The data processing hardware 102 is configured to assign impact scores 118 to the impact events 114. The impact scores 118 are determined based on the sensor data 40 and a comparison of the identified impact events 114 with the impact thresholds 116.

[0047] Thus, the crash score 118 is classified by one of the low crash threshold 116a, the intermediate crash threshold 116b, and the high crash threshold 116c. The crash score 118 can then be compared to the crash score hierarchy 120 stored in the memory hardware 104. The crash score hierarchy 120 includes a first layer of crash scores 120a, a second layer of crash scores 120b, and a third layer of crash scores 120c. The crash score hierarchy 120 is generally aligned with the crash thresholds 116, because the first layer of crash scores 120a corresponds to the low crash threshold 116a, the second layer of crash scores 120b corresponds to the intermediate crash threshold 116b, and the third layer of crash scores 120c corresponds to the high crash threshold 116c. The vehicle controller 106 uses the crash score hierarchy 120 to determine the response of the crash monitoring application 108.

[0048] Thus, the data processing hardware 102 first determines a crash score 118 based on the sensor data 40 and the detected crash event 114, and then determines a response of the crash monitoring system 100 based on a comparison of the crash score 118 to the crash score hierarchy 120. Example action responses of the crash monitoring system 100 are described herein with respect to each crash score hierarchy 120. The described example action responses are presented as examples, and the action responses of the crash monitoring system 100 are not limited to the examples presented.

[0049] Further references Figure 2-5 , after being compared to the impact score threshold 116, the impact score 118 can be classified by one of a low impact score 118a, an intermediate impact score 118b, and a high impact score 118c. Each of the impact scores 118 corresponds to the impact score threshold 116 and the impact score hierarchy 120, respectively. If the data processing hardware 102 determines that the impact event 114 has a low impact score 118a, the impact monitoring system 100 takes minimal action. For example, the impact monitoring system 100 continues to monitor updated sensor data 40 throughout the operation of the vehicle 10. The impact monitoring system 100 stores the sensor data 40 associated with the impact event 114 in the memory hardware 104. If the data processing hardware 102 determines a change in the sensor data 40 that can change the determined impact score 118, the impact monitoring system 100 can update the impact score 118. Therefore, the impact score 118 can be continuously monitored and updated based on the updated sensor data 40 received during the operation of the vehicle 10.

[0050] The intermediate impact score 118b corresponds to the second layer impact score 120b, which can trigger the impact monitoring application 108 to issue a notification 112 indicating the impact event 114 to the operator of the vehicle 10. For example, the notification 112 can recommend to the operator to check the potential impact effects of the vehicle 10 due to the impact event 114. Additionally or alternatively, the notification 112 can recommend the operator to monitor any resulting impact effects from the impact event 114 of the vehicle 10. Although the intermediate impact score 118b is greater than the low impact score 118a, the intermediate impact score 118b can lead to monitoring, similar to the execution as a result of the low impact score 118a. The intermediate impact score 118b covers a range of impact events 114 and is the most likely to result in the impact score 118 accumulated over time. For example, the impact event 114 can be classified as having an intermediate impact score 118b based on the initial sensor data 40 received after the impact event 114. However, the impact score 118 can be modified based on the updated sensor data 40 received during the continued operation of the vehicle 10.

[0051] Still reference Figures 2 to 5 , the high crash score 118c corresponds to a third tier crash score 120c, which triggers the crash monitoring application 108 to issue a notification 112 and causes the crash monitoring system 100 to activate the transmission device 50 to communicate with the communication server 302. The communication server 302 may send an audio transmission via the transmission device 50 for reception by an operator of the vehicle 10. For example, the transmission device 50 may transmit instructions from the communication server 302 in response to the crash event 114. The instructions may include, but are not limited to, a pullover recommendation 130 and guidance for evaluating the outcome of the crash event 114. The operator may indicate that the impact of the crash may be remedied or at least partially resolved, and the communication server 302 may provide step-by-step guidance to perform a corrective process.

[0052] In some examples, the transmission device 50 is configured to contact a live advisor and / or can automate a call to a live advisor via the communication server 302. In addition, the transmission device 50 can cooperate with the vehicle controller 106 to crowdsource data from third-party devices 304 over the network 300 that can inform of a crash event 114. The vehicle controller 106 can store the crowdsourced data to identify locations along the road 402 that may be high risk. The high risk location can correspond to a likelihood of a crash event 114 with a high crash score 118c and / or to a third tier crash score 120c. In some examples, the transmission device 50 can also communicate with the communication server 302 if the crash event 114 has a low crash score 118a and / or an intermediate crash score 118b.

[0053] The transmission device 50 may relay data related to the impact event 114 to the communication server 302. In addition to relaying data to the communication server 302, the impact monitoring system 100 may also predict a component operation duration 132. The component operation duration 132 may be communicated to the operator via the above-mentioned notification 112 on the impact monitoring application 108. The component operation duration 132 may correspond to an estimated travel distance that the vehicle 10 may travel before encountering potential long-term impacts.

[0054] It is also contemplated that the crash monitoring system 100 may determine a recommended service date for a corresponding component based on the component operation duration 132. The recommended service date may be presented to the operator via a notification 112 on the display device 30. In response to the crash monitoring system 100 identifying the crash event 114 and determining the crash score 118, the notification 112 may be displayed on the display device 30. In addition, the crash monitoring system 100 may record the date and time associated with the crash event 114 in the memory hardware 104 for future analysis and reference in determining the component operation duration 132 and the recommended service date.

[0055] Continue to refer Figures 2 to 5 , the notification 112 displayed on the display device 30 can prompt the operator to take action in response to the impact event 114, or to temporarily ignore the impact event 114. It is expected that the option to ignore the impact event 114 can be associated with the low impact score 118a and / or the intermediate impact score 118b. As described above, the impact monitoring system 100 can present a pullover recommendation 130, where the operator of the vehicle 10 can safely reposition the vehicle 10 off the road 402. In some examples, the communication server 302 can communicate the pullover recommendation 130 with the operator. The pullover recommendation 130 can be identified by the impact monitoring system 100 through communication with the GPS processor 200.

[0056] In the event of a crash event 114 having a high crash score 118c, the crash monitoring system 100 will notify the operator of immediate attention and recommend an accelerated stopping procedure. In response, the vehicle controller 106 will identify a pullover location 134 and notify the operator of a pullover recommendation 130 including the pullover location 134 to check for impact impacts on the vehicle 10. As described above, the crash monitoring system 100 is communicatively coupled to the GPS processor 200 to identify the pullover location 134 once the pullover recommendation 130 is issued. The GPS processor 200 utilizes the GPS location 204 of the vehicle 10 in addition to the geographic location 206 and environmental information 208 of the area surrounding the vehicle 10. Each of the GPS location 204, the geographic location 206, and the environmental information 208 is communicated to the crash monitoring system 100 as GPS data 202. The crash monitoring system 100 utilizes the GPS data 202 to determine the pullover location 134.

[0057] The impact monitoring system 100 may also utilize the GPS data 202 in conjunction with the network 300 to communicate with a third-party device 304 to warn nearby vehicles of the impact event 114. In some examples, the impact monitoring system 100 may utilize the GPS data 202 to transmit the location of the impact event 114, including environmental information 208 that may be related to the impact event 114. Thus, the third-party device 304 may be warned of potential external factors that may have caused the impact event 114. It is also contemplated that the impact monitoring system 100 may warn the third-party device 304 of the presence of the vehicle 10 in the pull-over position 134 to help provide space around the vehicle 10. For example, a third-party driver may otherwise be unaware that the vehicle 10 is in the pull-over position 134, so the impact monitoring system 100 may issue an alert via the network 300 that the vehicle 10 is in the pull-over position 134.

[0058] Reference now Figures 6 to 8, the crash monitoring system 100 is outlined with respect to the various steps leading up to and responding to the crash event 114. At 600, the crash monitoring system 100 monitors the vehicle 10 during operation. The crash monitoring system 100 identifies various events during operation to determine whether the crash event 114 is detected at 602. If the crash event 114 is not detected, the crash monitoring system 100 continues to monitor the vehicle 10. If the crash event 114 is detected, the crash monitoring system 100 determines the crash score 118 at 604. At 606, the crash monitoring system 100 determines whether the crash score 118 is greater than the low crash threshold 116a. If the crash score 118 is less than the low crash threshold 116a, the crash monitoring system 100 stores data associated with the crash event 114 at 608 and returns to the monitoring vehicle 10. If the crash score 118 is greater than the low crash threshold 116a, then at 610, the crash monitoring system 100 determines whether the crash score is less than the intermediate crash threshold 116b. If the crash score 118 is less than the intermediate crash threshold 116 b, the crash monitoring system 100 alerts the operator of the crash event 114 and possible need for future service at 612 . The crash monitoring system 100 then continues to store data associated with the crash event 114 at 608 and monitor the vehicle 10 at 600 .

[0059] If the impact score 118 is greater than the intermediate impact threshold 116b, then at 614, the impact monitoring system alerts the operator to the impact event 114. At 616, the impact monitoring system 100 may also alert a third-party device 304 that may be in close proximity to the vehicle 10 of the impact event 114. Then, at 618, the impact monitoring system 100 may initiate communication with the communication server 302 via the transmission device 50 and the network 300. Next, at 620, the impact monitoring system 100 determines the maximum travel distance after the impact event 114. For example, the impact monitoring system 100 may evaluate the GPS data 202 and the impact score 118 to determine the severity of the impact event 114. In some examples, the impact monitoring system 100 may query the GPS location 204 from the GPS processor 200 at 622. At 624, the impact monitoring system 100 determines whether a safe pull-over location 134 exists based on the GPS data 202. If a safe pullover location 134 exists, then at 626 , the impact monitoring system 100 issues a pullover recommendation 130 .

[0060] If there is no safe pullover location 134 near the GPS location 204 of the vehicle 10, then at 628, the impact monitoring system 100 determines whether there is a pullover location within the maximum travel distance of the vehicle 10. If there is a pullover location 134 within the maximum travel distance, then at 630, the impact monitoring system 100 issues a pullover recommendation 130 for a future pullover location 134. If there is no alternative pullover location within the maximum travel distance, then at 626, the impact monitoring system 100 issues a pullover recommendation 130 at the current location of the vehicle 10. The impact monitoring system 100 may also issue an alert to a nearby third-party device 304 to notify the third-party operator 506 that the vehicle 10 is present in the pullover location 134. The above steps may be performed by the impact monitoring system 100 in various orders and operations depending on the severity of the impact event 114. The impact monitoring system 100 may perform the steps in the order outlined herein, or may alternatively perform some steps before performing other steps. It is also contemplated that, depending on the impact event 114 , some steps may be omitted.

[0061] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0062] The foregoing description is provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in a selected configuration, even if not specifically shown or described. It can also be varied in many ways. Such variations should not be considered as departing from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A collision monitoring system for a vehicle, the collision monitoring system comprising: Data processing hardware; as well as Memory hardware in communication with the data processing hardware, the memory hardware storing instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations comprising: receiving sensor data from a plurality of sensors disposed along the vehicle; identifying an impact event based on the sensor data; comparing the sensor data and the identified impact event to a series of impact thresholds; determining a crash score based on a comparison of the sensor data and the identified crash event to the series of crash thresholds; comparing the impact score to a hierarchy of impact scores corresponding to the series of impact thresholds; and The impact event is monitored using the updated sensor data. 2 . The crash monitoring system of claim 1 , wherein the operations include determining an estimated distance traveled based on the crash event and updated sensor data. 3 . The crash monitoring system of claim 2 , wherein determining the estimated distance traveled includes determining a component operation duration and notifying an operator of the vehicle of the component operation duration. 4 . The crash monitoring system of claim 1 , wherein the operations include issuing a notification identifying the crash event based on the crash score and the crash score hierarchy. 5 . The crash monitoring system of claim 1 , wherein monitoring the crash event comprises notifying a third party device of the crash event and the crash score. 6 . The crash monitoring system of claim 1 , wherein the operation comprises recommending an inspection of the vehicle in response to the crash event and the determined crash score.

7. The crash monitoring system of claim 1 , wherein determining the crash score comprises determining that the crash event has a low crash score corresponding to a first tier crash score of the crash score hierarchy, and in response to the determined low crash score, issuing a notification including a recommended service date.

8. The crash monitoring system of claim 7, wherein determining the crash score comprises determining that the crash event has an intermediate crash score corresponding to a second tier crash score of the crash score hierarchy, and in response to the determined intermediate crash score, recommending that the operator inspect the vehicle for a crash impact.

9. The crash monitoring system of claim 8, wherein determining the crash score comprises determining that the crash event has a high crash score corresponding to a third tier crash score of the crash score hierarchy, and receiving a communication from a communication server to facilitate operation of the vehicle in response to the determined high crash score. 10 . The crash monitoring system of claim 9 , wherein determining that the crash event has a high crash score includes identifying a pullover location.

Images