IMPACT MONITORING SYSTEM

Abstract

An impact monitoring system for a vehicle comprises data processing hardware and storage hardware that communicates with the data processing hardware. The storage hardware holds 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 variety of sensors positioned along the vehicle and identifying an impact event based on that sensor data. The sensor data and the identified impact event are compared against a set of impact thresholds, and an impact score is determined based on this comparison.The impact score is compared to an impact score hierarchy, where the impact score hierarchy corresponds to the series of impact thresholds, and the impact event is monitored using updated sensor data.

Description

introduction

[0001] The information provided in this section is intended to generally present the context of the disclosure. The work of the inventors identified herein, to the extent described in this section, as well as aspects of the description that do not otherwise describe the prior art at the time of the application, are neither expressly nor impliedly acknowledged as prior art to the present disclosure.

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

[0003] Vehicles travel on the road network and encounter many external factors while driving. As a result, an encounter with a vehicle can cause parts of the vehicle to change, which can affect or impair its functionality. While some vehicles are equipped with sensors that can provide an indication that an event has occurred, most vehicles use a blanket system that doesn't necessarily differentiate between severity levels or the type of event. Summary

[0004] In some aspects, a computer-implemented method that, when executed by computing hardware, causes the computing hardware to perform operations includes receiving sensor data from a plurality of sensors disposed along a vehicle. An impact event is identified based on the sensor data, and the sensor data and the identified impact event are compared to a series of impact thresholds. Based on the comparison of the sensor data and the identified impact event to the series of impact thresholds, an impact score is determined. The impact score is compared to an impact score hierarchy.The impact score hierarchy corresponds to the series of impact thresholds and includes a first-level impact score, a second-level impact score, and a third-level impact score. An operator or driver of the vehicle is notified of the impact event based on the impact score and the impact score hierarchy. The impact event is monitored using updated sensor data, and an estimated travel distance is determined based on the impact event and the updated sensor data.

[0005] In some examples, the impact event may be determined to have a medium impact score, which may correspond to the impact score of a second level of the impact score hierarchy. In response to the determined medium impact score, the computing hardware may recommend that the operator inspect the vehicle for impact effects. In other examples, the impact event may be determined to have a high impact score, which may correspond to the impact score of a third level of the impact score hierarchy. In response to the determined high impact score, the computing hardware may receive a notification from a communications server to enable operation of the vehicle. If the impact event has a high impact score, then optionally a pull-over or stop location may be identified.In some examples, a component's service life may be determined, and the vehicle operator may be notified of the component's service life. A service date for a component corresponding to the component's service life may be determined, and a notification with the service date may be issued. In some cases, third-party devices may be notified of the impact event.

[0006] In other aspects, an impact monitoring system for a vehicle includes computing hardware and memory hardware in communication with the computing hardware. The memory hardware stores instructions that, when executed on the computing hardware, cause the computing hardware to perform operations. The operations performed by the computing 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 against a set of impact thresholds, and an impact score is determined based on the comparison of the sensor data and the identified impact event against the set of impact thresholds.The impact score is compared to an impact score hierarchy, where the impact score hierarchy corresponds to the series of impact thresholds, and the impact event is monitored using updated sensor data.

[0007] In some examples, an estimated drive time is determined based on the impact event and the updated sensor data. A component service life may be determined, and the vehicle operator may be notified of the component service life. Optionally, a notification may be issued that identifies the impact event based on the impact score and the impact score hierarchy. The impact event may be determined to have a low impact score, which may correspond to a first-level impact score of the impact score hierarchy. In response to the determined low impact score, a notification may be issued that includes a recommended maintenance date. In some cases, third-party devices may be notified of the impact event and the impact score.Optionally, the impact monitoring system may recommend an inspection of the vehicle in response to the impact event and the determined impact score.

[0008] In still other aspects, an impact monitoring system may include computing hardware and storage hardware in communication with the computing hardware. The storage hardware stores instructions that, when executed on the computing hardware, cause the computing hardware to perform operations. The operations performed by the computing hardware include receiving sensor data from a plurality of sensors disposed along a vehicle and identifying an impact event based on the sensor data. The sensor data and the identified impact event are compared against a series of impact thresholds, and an impact score is determined based on the comparison of the sensor data and the identified impact event against the series of impact thresholds.The impact score is compared to an impact score hierarchy. The impact score hierarchy corresponds to the series of impact thresholds. The impact event is monitored using updated sensor data.

[0009] In some examples, the impact score hierarchy includes a first-level impact score, a second-level impact score, and a third-level impact score, and the series of impact thresholds includes a low impact threshold, a medium impact threshold, and a high impact threshold. Based on the high impact threshold, the impact event may be determined to have a high impact score. The high impact score may correspond to the third-level 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 pull-over / stopping recommendation may be issued.In some cases, a message may be received from a communications server to enable vehicle operation and recommend a stopping location for the stopping event. Optionally, a notification of the impact event and the determined high impact score may be issued to third-party devices. Based on the impact event and the updated sensor data, an estimated travel route may be determined. Brief description of the drawings

[0010] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure. Fig. 1 is a perspective view of a vehicle according to the present disclosure on a road; Fig. 2 is a partial perspective view of an interior cabin of a vehicle according to the present disclosure; Fig. 3 is a perspective view of an event with impact according to the present disclosure; Fig. 4 is a perspective view of the event with effect from Fig. 3 with a vehicle at a stopping location according to the present disclosure; Fig. 5 is a functional block diagram for an impact monitoring system according to the present disclosure; Fig. 6 is an exemplary flow diagram of an impact monitoring system according to the present disclosure; Fig. Figure 7 is an example flowchart of the impact monitoring system of Fig. 6; and Fig. Figure 8 is an example flowchart of the impact monitoring system of Fig. 7.

[0011] Corresponding reference numerals designate corresponding parts throughout the drawings. Detailed description

[0012] Example configurations will now be described in more detail with reference to the accompanying drawings. The example configurations are provided so that this disclosure will be complete and will fully convey the scope of the disclosure to those skilled in the art. Specific details are set forth, such as examples of particular components, devices, and methods, in order to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed to limit the scope of the disclosure.

[0013] The terminology used herein is for the purpose of describing particular example configurations only and is not intended to be limiting. As used herein, the singular articles "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprise," "comprising," "including," and "having" are inclusive and therefore specify the presence of features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. The method steps, processes, and operations described herein should not be construed as necessarily being performed in the order discussed or illustrated unless they are expressly identified as being in order of implementation.Additional or alternative steps may be used.

[0014] When an element or layer is referred to as being located "on," "engaging with," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, engaging with, connected to, attached to, or coupled with the other element or layer, or there may be intervening elements or layers. In contrast, when an element is referred to as being located "directly on," "directly engaging with," "directly connected to," "directly attached to," or "directly coupled with" another element or layer, there may be no intervening elements or layers. Other words used to describe the relationship between elements should be interpreted similarly (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.).As used herein, the term “and / or” includes all combinations of one or more of the associated listed elements.

[0015] The terms "first", "second", "third", etc. may be used herein to describe various elements, components, regions, layers, and / or sections. These elements, components, regions, layers, and / or sections are not intended to be limited by these terms. These terms may only be used to distinguish one element, component, region, layer, or section from another region, layer, or section. Terms such as "first", "second", and other numerical terms do not imply a sequence or order unless clearly indicated by the context. For example, a first element, component, region, layer, or section could be...a first section, referred to below, may also be referred to as a second element, second component, second region, second layer, or second portion, or second section, without departing from the teachings of the exemplary configurations.

[0016] In this application, including the definitions below, the term "module" may be replaced by 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 (common, dedicated, or group) executing code, a memory (common, dedicated, or group) storing code executed by a processor, 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-chip.

[0017] The term "code" as used above may include software, firmware, and / or microcode and may refer to programs, routines, functions, classes, and / or objects. The term "shared processor" includes a single processor that executes some or all of the code from multiple modules. The term "group processor" includes a processor that, in combination with additional processors, executes some or all of the code from one or more modules. The term "shared memory" includes a single memory that stores some or all of the code from multiple modules. The term "group memory" includes memory that, in combination with additional memory, stores some or all of the code from one or more modules. The term "memory" may be a subset of the term "computer-readable medium."The term "computer-readable medium" does not encompass the transitory electrical and electromagnetic signals that propagate through a medium and can therefore be considered tangible, or non-transitory, storage. Non-limiting examples of non-transitory storage include tangible computer-readable medium, including non-volatile memory, magnetic storage, and optical storage.

[0018] The devices and methods described in this application may be implemented partially or completely using one or more computer programs executed by one or more processors. The computer programs contain processor-executable instructions stored on at least one non-transitory, tangible, computer-readable medium. The computer programs may also contain and / or access stored data.

[0019] A software application (i.e., a software resource) may refer to computer software that causes a computing device to perform a task. 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.

[0020] Non-transitory memory may be physical devices 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 may 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) / electronically erasable programmable read-only memory (EEPROM) (e.g., typically used for firmware such as boot programs). Examples of volatile memory include, but are not limited to, random access memory (RAID).Random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and floppy disks or tapes.

[0021] These computer programs (also referred to as programs, software, software applications, or code) contain machine instructions or instructions for a programmable processor and may be implemented in a procedural high-level and / or object-oriented programming language and / or in assembly / machine language. 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., magnetic disks, optical disks, memories, programmable logic devices (PLDs)) used to provide machine instructions and / or data to a programmable processor containing a machine-readable medium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0022] Various implementations of the systems and techniques described herein may be realized in digital electronic and / or optical circuitry, integrated circuitry, specially designed or configured ASICs (Application Specific Integrated Circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementation in one or more computer programs executable and / or interpretable on a programmable system including at least one programmable processor, which may be special-purpose or general-purpose, and coupled to receive data and instructions from and transmit data and instructions to a memory system, at least one input device, and at least one output device.

[0023] The processes and logic flows described in this specification may be carried out by one or more programmable processors, also referred to as data processing hardware, that execute one or more computer programs to perform functions by processing input data and generating output. The processes and logic flows may also be carried out by special-purpose logic circuitry, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit). Processors suitable for executing a computer program include, for example, both general-purpose and special-purpose microprocessors, as well as any one or more processors of any type of digital computer. In general, a processor receives instructions orInstructions and data from read-only memory or random access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more storage devices for storing instructions and data. Generally, a computer also includes, or is operatively coupled to, one or more mass storage devices for storing data, such as magnetic, magneto-optical, or optical disks, or to receive or transfer data from or to them, or both. However, a computer is not required to include such devices. Computer-readable media suitable for storing computer program instructions and data includes all forms of non-volatile memory, media, and storage devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices, magnetic disks, such asInternal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory can be supplemented by or integrated into special-purpose logic circuitry.

[0024] To enable interaction with the user, one or more aspects of the disclosure may be implemented on a computer having a display device, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or a touchscreen for displaying information to the user, and optionally a keyboard and a pointing device, a mouse, or a trackball, for the user to provide input to the computer. Other types of devices may also be used to enable interaction with the user; for example, 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 auditory, verbal, or tactile input.In addition, a computer may interact with a user by sending and receiving documents to and from a device used by the user, for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

[0025] Referring to Fig. 1-8, a vehicle 10 includes a vehicle body 12 equipped with an impact monitoring system 100. In some aspects of the disclosure, the vehicle 10 is an electric vehicle (EV) with autonomous or semi-autonomous capabilities. Additionally or alternatively, the vehicle 10 may also be equipped with an internal combustion engine (ICE). In other aspects, the vehicle 10 may be a hybrid vehicle including both EV and ICE components and capabilities.

[0026] The vehicle body 12 can generally be divided into a front portion 14 near a front bumper 16 of the vehicle body 12 and a rear portion 18 of the vehicle near a rear bumper 20. As in Fig. 1, the vehicle 10 includes a plurality of sensors 22 that may be integrated into various elements of the vehicle body, including, but not limited to, rearview mirrors 24, front bumper 16, and rear bumper 20, 12. For example, a tire pressure sensor 22a may be configured to detect a pressure change in 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 (LI-DAR) sensors, and image sensors, which may be incorporated as part of the vehicle body 12.

[0027] Referring to Fig. 2-5, an interior 28 of the vehicle 10 is defined by the vehicle body 12 and includes an interior rearview mirror 24a and a display device 30. The interior rearview mirror 24a may be equipped with one or more of the plurality of sensors 22, including, but not limited to, an image sensor 22b. It is also contemplated that the image sensor 22b may be positioned on exterior rearview mirrors 24b. The image sensor 22b is configured to sense the surroundings of the vehicle, as further described below.

[0028] The display device 30 may be located on an instrument panel 32 of the vehicle 10 and is configured to display information related to the vehicle 10 to an occupant, including a driver or operator, of the vehicle 10. In some aspects, the display device 30 may be a head-up display (HUD) integrated into a windshield 34 of the vehicle 10. In other examples, the display device 30 may be a tablet device integrated into the instrument panel 32 and configured with capacitive sensors for the operational 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.

[0029] Further referring to Fig. 2-5, the impact monitoring system 100 is communicatively coupled to the display device 30 and the sensors 22. The impact monitoring system 100 is integrated into the vehicle 10 and includes computing hardware 102 and memory hardware 104, each of which may be configured as part of a vehicle controller 106. The computing hardware 102 is configured to perform operations of the impact monitoring system 100, and the memory hardware communicates with the computing hardware 102 and stores instructions that, when executed on the computing hardware 102, cause the computing hardware 102 to perform the operations. The operations performed by the computing hardware 102 may include initiating an impact monitoring application 108, which may be stored in the storage hardware 104.

[0030] The impact monitoring application 108 may be configured as the user-facing interface of the impact monitoring system 100. The impact monitoring application 108 receives and integrates sensor data 40 from the plurality of sensors 22 and vehicle data 110 stored in the storage hardware 104. The vehicle controller 106 may display the impact monitoring application 108 on the display device 30. As described herein, in response to an impact event 114, the impact monitoring application 108 may present notifications 112 on the display device 30. The impact event 114 may be categorized as an event affecting the operational function of the vehicle 10.Examples of impact event 114 may include, among other examples, one or more tires 26 hitting a pothole or coming into contact with another object on the road, one or more tires 26 being punctured or blown out, a crack occurring in a suspension of vehicle 10, an external object and vehicle 10 coming into contact, a change in alignment, repeated clunking or clicking noises, and exhaust effects. For example, the example shown in . Fig. 3 and Fig. 4 illustrated event 114 affecting one of the tires 26 after hitting a pothole 400 along a road 402 in a flattened state.

[0031] With further reference to Fig. 2-5, the impact monitoring system 100 may couple the vehicle controller 106 to a GPS processor 200 and a network 300. The vehicle controller 106 may also include a transmission device 50 of the vehicle 10 communicatively connected to the network 300 to send or transmit audio messages from a communication server 302 to the driver of the vehicle 10. The transmission device 50 may also transmit the vehicle data 110 and the impact event 114 stored in the vehicle controller 106 to the communication server 302. The transmission device 50 may at least partially communicatively couple the vehicle controller 106 to the network 300 to provide wireless communication capabilities, including, in some aspects, wireless calling and emergency communications. In some examples, the transmission device 50 is an OnStar ®System including operational functions including, but not limited to, vehicle security, 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.

[0032] 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. The GPS data 202 may include, for example, a geographic environmental location 206 corresponding to a route of the vehicle 10 and environmental information 208 related to the vehicle 10, which is monitored both while moving and in a stationary position. The environmental information 208 includes, but is not limited to, information about road conditions, road curves, road gradient, building locations, and topographical information. The environmental information 208 may include additional environmental information 208 related to the environment of the vehicle 10, the transmission of which to the vehicle controller 106 may be beneficial.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.

[0033] The GPS processor 200 transmits the geographical location 206 and the environmental information 208 over the network 300 to the vehicle controller 106. As mentioned above, the network 300 may include the communications server 302 communicatively coupled to the transmission device 50 to send and receive signals. For example, the communications server 302 may receive the GPS data 202 from the GPS processor 200 and communicate the GPS data 202 directly with the operator or driver of the vehicle 10 via the transmission device 50. In some examples, the communications 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 communications server 302 is configured to provide roadside assistance to the operator of the vehicle 10 in response to the impact event 114.While the transmitted GPS data 202 may be included as part of the roadside assistance, it is also contemplated that the communication server 302 may, where appropriate, provide step-by-step instructions for responding to the impact event 114.

[0034] Still on Fig. 2-5, in some aspects, the vehicle data 110 stored in the memory hardware 104 includes information regarding 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 trip information and / or, in an EV example, the battery life of the vehicle 10. The vehicle controller 106 may use the vehicle data 110 in combination with the sensor data 40 to monitor a vehicle environment during operation of the vehicle 10 and during various vehicle procedures.

[0035] For example, the impact monitoring system 100 may detect a change in speed that is inconsistent with the driver's input, which may at least partially indicate the impact event 114. In some cases, a rapid decrease in speed following an impact event 114 may indicate potential damage to the vehicle 10. The impact monitoring system 100 may identify the reduction in speed when evaluating the vehicle data 110 with respect to the impact event 114. In other examples, the impact event 114 may be the result of an electrical impact event 114, such as a thermal runaway event. It is contemplated that the impact event 114 generally corresponds to any event that may impact or otherwise affect the operation of the vehicle 10.

[0036] 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.

[0037] For example, if the vehicle 10 hits a pothole, the sensor data 40 may include data from the tire pressure sensor 22a corresponding to a loss of tire pressure and suspension impacts. In other examples, a single impact event 114 may be detected. The sensor data 40 may also include image data from the image sensor 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 them to a series of impact thresholds 116 stored in the memory hardware 104.

[0038] The series of impact thresholds 116 includes a low impact threshold 116a, a medium impact threshold 116b, and a high impact threshold 116c. Each of the impact thresholds 116 encompasses 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 an isolated impact event 114 may be categorized based on a lower impact threshold 116, but the cumulative impact events 114 may instead be categorized based on a higher impact threshold 116. The computing hardware 102 is configured to assign an impact score 118 to the impact event 114.The impact score 118 is determined based on the comparison of the sensor data 40 and the identified event 114 with impact with the impact thresholds 116.

[0039] The impact score 118 is thus categorized using one of the low impact threshold 116a, the medium impact threshold 116b, and the high impact threshold 116c. The impact score 118 can then be compared to a hierarchy 120 of impact scores stored within the storage hardware 104. The impact score hierarchy 120 includes a first-level impact score 120a, a second-level impact score 120b, and a third-level impact score 120c.The impact score hierarchy 120 generally corresponds to the impact thresholds 116 in that the first-level impact score 120a corresponds to the low impact threshold 116a, the second-level impact score 120b corresponds to the medium impact threshold 116b, and the third-level impact score 120c corresponds to the high impact threshold 116c. The impact score hierarchy 120 is used by the vehicle controller 106 to determine a response from the impact monitoring application 108.

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

[0041] Continue on Fig. Referring to Figures 2-5, the impact score 118 may be classified or categorized, after comparison with the impact score threshold 116, using a low impact score 118a, a medium impact score 118b, and a high impact score 118c. Each of the impact scores 118 corresponds to the impact score thresholds 116 and the impact score hierarchy 120, respectively. If the computing hardware 102 determines that the impact event 114 has a low impact score 118a, only minimal action is taken by the impact monitoring system 100. For example, during operation of the vehicle 10, the impact monitoring system 100 continues to monitor the updated sensor data 40. The impact monitoring system 100 stores the sensor data 40 associated with the impact event 114 in the storage hardware 104.If the data processing hardware 102 determines a change in the sensor data 40 that may change the determined impact score 118, then the impact monitoring system 100 may update the impact score 118. Consequently, the impact scores 118 may be continuously monitored and updated based on the updated sensor data 40 received during operation of the vehicle 10.

[0042] The medium impact score 118b corresponds to a second-level impact score 120b, which may cause the impact monitoring application 108 to deliver a notification 112 to the operator of the vehicle 10 indicating the impact event 114. For example, the notification 112 may recommend the operator to inspect the vehicle 10 for possible impact effects resulting from the impact event 114. Additionally or alternatively, the notification 112 may recommend the operator to monitor the vehicle 10 for any resulting impact effects of the impact event 114. Although the medium impact score 118b is higher than the low impact score 118a, the medium impact score 118b may result in monitoring similar to that performed as a result of the low impact score 118a.The mean impact score 118b encompasses a range of impact events 114 and is the impact score 118 most likely to accumulate over time. For example, the impact event 114 may be categorized as having a mean impact score 118b based on the initial sensor data 40 received after the impact event 114. However, the impact score 118 may be revised based on the updated sensor data 40 received during continued operation of the vehicle 10.

[0043] Still on Fig. Referring to FIGS. 2-5, the high impact score 118c corresponds to a third-level impact score 120c, which causes the impact monitoring application 108 to issue a notification 112 and, for the impact monitoring system 100, 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 receipt by the operator of the vehicle 10. For example, in response to the impact event 114, the transmission device 50 may transmit instructions from the communication server 302. The instructions may include a pull-over recommendation 130 and guidance for evaluating the consequence of the impact event 114.The operator may indicate that the impact effects can be corrected or at least partially corrected, and the communication server 302 may provide step-by-step instructions to perform a corrective procedure.

[0044] In some examples, the transmission device 50 is configured to contact a live advisor and / or may automate a call to the live advisor via the communication server 302. Further, the transmission device 50 may cooperate with the vehicle controller 106 to receive, via the network 300, crowdsourced data from third-party devices 304 that may inform about the impact event 114. The vehicle controller 106 may store the crowdsourced data to identify locations along the road 402 that may pose a high risk. A high-risk location may correspond to a potential impact event 114 with a high impact score 118c and / or a third-level impact score 120c.In some examples, the transmission device 50 may also communicate with the communication server 302 if the impact event 114 has a low impact score 118a and / or a medium impact score 118b.

[0045] The transmission device 50 may forward data related to the impact event 114 to the communications server 302. In addition to forwarding data to the communications server 302, the impact monitoring system 100 may predict a component operating time 132. The component operating time 132 may be communicated to the operator via the aforementioned notification 112 of the impact monitoring application 108. The component operating time 132 may correspond to an estimated distance that the vehicle 10 can travel before experiencing potential long-term effects.

[0046] It is also conceivable that the impact monitoring system 100 may determine a recommended maintenance date for the respective component based on the component operating life 132. The recommended maintenance date may be presented to the operator via the notification 112 on the display device 30. The notification 112 may be presented on the display device 30 in response to the impact monitoring system 100 identifying the impact event 114 and determining the impact score 118. Furthermore, the impact monitoring system 100 may record the date and time associated with the impact event 114 in the storage hardware 104 for future analysis and reference in determining the component operating life 132 and the recommended maintenance date.

[0047] Continue on Fig. 2-5, the notification 112 displayed on the display device 30 may prompt the operator to either take action in response to the impact event 114 or to temporarily ignore the impact event 114. It is contemplated that the option to ignore the impact event 114 may be associated with the low impact score 118a and / or the medium impact score 118b. As mentioned above, the impact monitoring system 100 may issue the stop recommendation 130, at which the operator of the vehicle 10 may safely reposition the vehicle 10 off the roadway 402. In some examples, the communication server 302 may communicate the stop recommendation 130 to the operator or driver. The stop recommendation 130 may be identified by the impact monitoring system 100 via communication with the GPS processor 200.

[0048] If the impact event 114 has a high impact score 118c, the impact monitoring system 100 notifies the operator of immediate attention and recommends an expedited stopping procedure. In response, the vehicle controller 106 identifies a pullover or stop location 134 and notifies the operator of the stop recommendation 130, which includes the stop location 134, to inspect the vehicle 10 for impact effects. As mentioned above, the impact monitoring system 100 is communicatively coupled to the GPS processor 200 to identify the stop location 134 once the stop 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 the environmental information 208 about the environment surrounding the vehicle 10.The GPS location 204, the geographic location 206, and the environmental information 208 are all transmitted to or exchanged with the impact monitoring system 100 as GPS data 202. The impact monitoring system 100 uses the GPS data 202 to determine the stopping location 134.

[0049] The impact monitoring system 100 may also use the GPS data 202 in combination with the network 300 to communicate with third-party devices 304 to inform nearby vehicles of the impact event 114. In some examples, the impact monitoring system 100 may use the GPS data 202 to communicate the location of the impact event 114, including environmental information 208 that may be associated with the impact event 114. Thus, third-party devices 304 may be informed of possible external factors that may have led to the impact event 114. It is also conceivable that the impact monitoring system 100 may inform the third-party devices 304 of the presence of the vehicle 10 at the stopping location 134 to assist in clearing space around the vehicle 10.For example, other drivers may otherwise be unaware that vehicle 10 is at stop location 134, so impact monitoring system 100 may issue a warning via network 300 that vehicle 10 is at stop location 134.

[0050] Now on Fig.Referring to FIGS. 6-8, the impact monitoring system 100 is described with respect to the various steps leading up to and in response to the impact event 114. At 600, the impact monitoring system 100 monitors the vehicle 10 during operation. The impact monitoring system 100 identifies various events during operation to determine at 602 whether an impact event 114 has been detected. If no impact event 114 is detected, the impact monitoring system 100 continues to monitor the vehicle 10. If an impact event 114 is detected, then at 604, the impact monitoring system 100 determines the impact score 118. At 606, the impact monitoring system 100 determines whether the impact score 118 is greater than the low impact threshold 116a.If the impact score 118 is less than the low impact threshold 116a, the impact monitoring system 100 then stores the data associated with the impact event 114 at 608 and returns to monitoring the vehicle 10. If the impact score 118 is greater than the low impact threshold 116a, the impact monitoring system 100 then determines at 610 whether the impact score is less than the medium impact threshold 116b. If the impact score 118 is less than the medium impact threshold 116b, the impact monitoring system 100 then reports the impact event 114 and the possible need for future maintenance to the operator at 612. The impact monitoring system 100 then proceeds to store the data associated with the impact event 114 at 608 and to monitor the vehicle 10 at 600.

[0051] If the impact score 118 is greater than the average impact threshold 116b, the impact monitoring system then reports the impact event 114 to the operator at 614. The impact monitoring system 100 may also report the impact event 114 to third-party devices 304 that may be in close proximity to the vehicle 10 at 616. The impact monitoring system 100 may then initiate communication with the communication server 302 via the transmission device 50 and the network 300 at 618. Next, the impact monitoring system 100 determines a maximum travel distance after the impact event 114 at 620. For example, the impact monitoring system 100 may evaluate the GPS data 202 and the impact score 118 to determine a severity level 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.The impact monitoring system 100 determines at 624, based on the GPS data 202, whether there is a safe stopping location 134. If there is a safe stopping location 134, the impact monitoring system 100 then issues the stopping recommendation 130 at 626.

[0052] If there is no safe stopping location 134 near the GPS location 204 of the vehicle 10, the impact monitoring system 100 then determines at 628 whether there is a stopping location within the maximum travel distance of the vehicle 10. If there is a stopping location 134 within the maximum travel distance, the impact monitoring system 100 then issues the stopping recommendation for the future stopping location 134 at 630. If there is no alternative stopping location within the maximum travel distance, the impact monitoring system 100 then issues the stopping recommendation 130 for the current location of the vehicle 10 at 626. The impact monitoring system 100 may also issue an alert to the nearby third-party devices 304 to inform the other operators 506 of the presence of the vehicle 10 at the stopping location 134.The steps described above may be performed by the impact monitoring system 100 in different orders and sequences or 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, alternatively, perform some steps before others. It is also conceivable that some steps may be omitted depending on the impact event 114.

[0053] A number of implementations have been described. Nevertheless, it should be understood that various modifications may be made without departing from the spirit and scope of the disclosure. Accordingly, other implementations are within the scope of the following claims.

[0054] The foregoing description is for purposes of illustration and description. It is not intended to be exhaustive or limiting of the disclosure. Individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable and may be used in a selected configuration, even if not specifically shown or described. The same may also be varied in many respects. Such variations are not to be considered a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.

Claims

[1] An impact monitoring system for a vehicle, the impact monitoring system comprising: a data processing hardware; and Storage hardware in communication with the computing hardware, the storage hardware storing instructions that, when executed on the computing hardware, cause the computing hardware to perform operations that include: Receiving sensor data from a plurality of sensors arranged along the vehicle; Identifying an impact event based on the sensor data; Comparing the sensor data and the identified impact event with a set of impact thresholds; Determining an impact score based on comparing the sensor data and the identified impact event with the set of impact thresholds; Comparing the impact score with an impact score hierarchy, where the impact score hierarchy corresponds to the series of impact thresholds; and Monitor the impact event using updated sensor data. [2] The impact monitoring system of claim 1, wherein the operations include determining an estimated travel distance based on the impact event and the updated sensor data. [3] The impact monitoring system of claim 2, wherein determining the estimated travel distance includes determining a component operating time and notifying the operator of the vehicle of the component operating time. [4] The impact monitoring system of claim 1, wherein the operations include issuing a notification identifying the impact event based on the impact score and the impact score hierarchy. [5] The impact monitoring system of claim 1, wherein monitoring the impact event comprises notifying third party devices of the impact event and the impact score. [6] The impact monitoring system of claim 1, wherein the operations include recommending that the vehicle be inspected in response to the impact event and the determined impact score. [7] The impact monitoring system of claim 1, wherein determining the impact score comprises determining that the impact event has a low impact score corresponding to an impact score of a first level of the impact score hierarchy, and, in response to the determined low impact score, issuing a notification including a recommended maintenance date. [8] The impact monitoring system of claim 7, wherein determining the impact score comprises determining that the impact event has a mean impact score corresponding to an impact score of a second level of the impact score hierarchy, and, in response to the determined mean impact score, recommending to the operator that the vehicle be inspected for impact effects. [9] The impact monitoring system of claim 8, wherein determining the impact score comprises determining that the impact event has a high impact score corresponding to an impact score of a third level of the impact score hierarchy, and, in response to the determined high impact score, receiving a notification from a communications server to enable operation of the vehicle. [10] The impact monitoring system of claim 9, wherein determining that the impact event has a high impact score comprises identifying a stopping location.

Images