Method for identifying and mitigating risk related to use of improper security device

Abstract

A safety device monitoring system for a vehicle includes a vehicle processor for storing vehicle data including one or more of vehicle event data, vehicle occupant data, and restraint system data. The security device monitoring system also includes a server communicatively coupled with the vehicle processor and configured to determine a baseline desired location of the constraint based on the vehicle occupant data and the constraint system data. The server is also configured to determine whether any deviation from a desired location of the constraint has occurred based on one or more of the vehicle event data and the constraint system data.

Description

Technical Field

[0001] The present invention generally relates to safety equipment monitoring systems for vehicles. Background Art

[0002] The information provided in this section is for the purpose of generally presenting the background of the present disclosure. To the extent described in this section, the work of the presently named inventors, as well as aspects of the description that may not qualify as prior art at the time of filing, are neither explicitly nor implicitly admitted to be prior art with respect to the present disclosure.

[0003] Restraint systems are important in vehicles because they protect vehicle occupants in the event of a vehicle collision. However, to be effective, the restraint system must be properly worn by the vehicle occupant at all times during vehicle operation.

[0004] While some vehicles include restraint detection systems that can notify vehicle occupants when vehicle restraints are not secured, proper placement of the restraint system is also required to be effective. Therefore, there remains a need for a system that can continuously detect and notify vehicle occupants that restraints are misplaced to ensure the safety of all vehicle occupants. Summary of the invention

[0005] In one configuration, a safety device monitoring system for a vehicle includes a vehicle processor for storing vehicle data, the vehicle data including one or more of vehicle event data, vehicle occupant data, and restraint system data. The safety device monitoring system also includes a server communicatively coupled to the vehicle processor and configured to determine a baseline desired position of a restraint based on the vehicle occupant data and the restraint system data. The server is further configured to determine whether any deviation from the desired position of the restraint has occurred based on one or more of the vehicle event data and the restraint system data. In addition, the server is further configured to notify a user of any determined deviation from the desired position of the restraint.

[0006] The safety equipment monitoring system may also include one or more of the following optional features. For example, the vehicle occupant data may include biometric information of the vehicle occupant, including one or more of the vehicle occupant's height and the vehicle occupant's weight. In addition, the restraint system data may include whether a child safety seat is installed. In addition, the server may be configured to determine whether the vehicle occupant is within the safety limits of the installed child safety seat based on the vehicle occupant data and the restraint system data. In addition, vehicle data may be collected using one or more of an onboard radar, a camera, a locking sensor, and a weight sensor. In addition, a vehicle may include the safety equipment monitoring system.

[0007] In another configuration, a safety device monitoring system for a vehicle includes a vehicle processor for storing vehicle data and a server communicatively coupled to the vehicle processor, the vehicle data including one or more of vehicle event data, vehicle occupant data, and restraint system data. The vehicle server is configured to determine whether a deviation from a desired seat belt position has occurred based on one or more of the vehicle event data, the vehicle occupant data, and the restraint system data. The vehicle server is further configured to determine a necessary response level based on one or more of the vehicle event data, the vehicle occupant data, and the restraint system data. The vehicle server is further configured to determine a required correction method based on one or more of the vehicle occupant data and the restraint system data. In addition, the vehicle server is configured to warn an occupant of a deviation from a desired seat belt position, including the detected location of the deviation and the determined necessary response level, and to recommend a corrective action based on the determined correction method requirement.

[0008] The safety equipment monitoring system may also include one or more of the following optional features. For example, the server may be further configured to limit the speed of the vehicle if it is determined that an emergency corrective action is required. In addition, the vehicle occupant data may include biometric information of the vehicle occupant, including one or more of the vehicle occupant height and the vehicle occupant weight. In addition, the restraint system data may include whether a child safety seat is installed. In addition, the server may be further configured to determine whether the vehicle occupant is within the safety limits of the installed child safety seat based on the vehicle occupant data and the restraint system data. In addition, vehicle data may be collected using one or more of an onboard radar, a camera, a lock sensor, and a weight sensor. In addition, a vehicle may include the safety equipment monitoring system.

[0009] In another configuration, a safety device monitoring system for a vehicle includes a vehicle processor for storing vehicle data including one or more of a vehicle location and restraint system data and a server communicatively coupled to the vehicle processor. The server is configured to determine whether a child safety seat has been properly installed based on the restraint system data. The server is further configured to recommend an installation technique to correct the installation of the child safety seat based on the restraint system data, and if it is determined that the child safety seat is not properly installed, direct the vehicle to the nearest fire station or police station for further assistance based on the vehicle location.

[0010] The safety equipment monitoring system may also include one or more of the following optional features. For example, the vehicle processor may be configured to store data related to the serial number of the installed child safety seat, and the server may be configured to provide specific installation techniques based on the serial number of the installed child safety seat to correct the installation of the child safety seat. In addition, the vehicle processor may store vehicle occupant data including biometric information of the vehicle occupant, including one or more of the vehicle occupant height and the vehicle occupant weight. In addition, the server may be configured to determine whether the occupant is within the safety limits of the installed child safety seat based on the vehicle occupant data and the restraint system data. In addition, vehicle data may be collected using one or more of an onboard radar, a camera, a lock sensor, and a weight sensor. In addition, a vehicle may include the safety equipment monitoring system. 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 front perspective view of a vehicle incorporating a safety device monitoring system according to the present disclosure;

[0013] Figure 2 A security device monitoring system according to the present disclosure is provided. Figure 1 a perspective view of the interior of the vehicle; and

[0014] Figure 3 is an exemplary process flow diagram of a safety device monitoring system according to the present disclosure.

[0015] Corresponding reference characters indicate corresponding parts throughout the several views. DETAILED DESCRIPTION

[0016] 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 exemplary configurations should not be construed as limiting the scope of the present disclosure.

[0017] The terms used herein are only for describing specific exemplary configurations, not for 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 "comprise", "include", "contain" and "have" are inclusive, thus specifying 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.

[0018] 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, engaged, connected, 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 of the associated listed items.

[0019] 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 are only used to distinguish each element, component, region, layer or part. Terms such as "first", "second" and other numerical terms do not imply order or sequence unless the context clearly indicates. Therefore, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part, without departing from the teaching of the example configuration.

[0020] In this application, including the definitions below, the term module may be replaced by the term circuit. The term "module" may refer to or be part of an application specific integrated circuit (ASIC), 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 group) that executes code; a memory (shared, dedicated, or group) that stores code executed by the processor; other suitable hardware components that provide the functionality; or a combination of some or all of the above, such as in a system on a chip.

[0021] The term code 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 includes a single processor that executes some or all of the code from multiple modules. The term group processor includes a processor that executes some or all of the code from one or more modules in combination with an additional processor. The term shared memory includes a single memory that stores some or all of the code from multiple modules. The term group memory includes a memory that stores some or all of the code 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 can therefore be considered to be tangible non-transitory memory. Non-limiting examples of non-transitory memory include tangible computer-readable media, including non-volatile memory, magnetic memory, and optical memory.

[0022] The apparatus 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.

[0023] Software applications (i.e., software resources) may refer to computer software that enables a computing device to perform tasks. In some examples, software applications may be referred to as "applications," "apps," or "programs." 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.

[0024] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., instruction sequences) 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.

[0025] 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, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, 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.

[0026] 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 comprising at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from a storage system, and to send data and instructions to the storage system.

[0027] The processes and logic flows described in this specification can be performed by one or more programmable processors, also known as data processing hardware, executing one or more computer programs to perform functions by operating on input data and generating outputs. These processes and logic flows can also be performed by dedicated logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits). For example, processors suitable for executing computer programs include general-purpose and special-purpose microprocessors, and any one or more processors of any kind 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 storage devices for storing instructions and data. Typically, a computer will also include or be operably connected to one or more large-capacity storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, to receive data from the large-capacity storage device or to 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 non-volatile memory, media and storage 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.

[0028] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device for displaying information to the user, such as a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen, and an optional keyboard and pointing device, such as a mouse or trackball, through which the user can provide input to the computer. Other types 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.

[0029] refer to Figures 1 to 3 , the safety equipment monitoring system 100 includes a vehicle processor 200 and a server 300 communicatively coupled to the vehicle processor 200. Figure 1In the embodiment of the present invention, the safety equipment monitoring system 100 is incorporated into a vehicle 10. The vehicle 10 may be an electric vehicle 10 (EV) and may include autonomous or semi-autonomous capabilities. Alternatively, the vehicle 10 may include an internal combustion engine (ICE). In addition, the vehicle 10 may be a hybrid vehicle 10 that combines EV and ICE components and capabilities.

[0030] Reference now Figure 2 , the vehicle 10 includes a vehicle interior 12, which includes one or more vehicle seats 13. Each vehicle seat 13 may also include one or more restraints 15 configured to secure a vehicle occupant thereto. The restraint 15 may be a three-point restraint including a lumbar portion 17 and an upper torso portion 19, a two-point restraint including only the lumbar portion 17, or may be a five-point restraint including a seat belt 21. Regardless of the type of restraint (i.e., two-point, three-point, five-point, etc.), the restraint 15 is configured to move between a locked state and an unlocked state.

[0031] The child safety seat 40 can be installed on one or more vehicle seats 13. Many child safety seats 40 require two restraints 15 to operate. For example, a first restraint 15 is required to secure the child safety seat 40 to the vehicle seat 13. The first restraint 15 can be a three-point restraint of the vehicle seat 13, or can be a lower buckle and tether (LATCH) coupling mechanism configured to secure the child safety seat 40 to a child in the vehicle seat 13. In addition, a second restraint 15 is required to secure the occupant of the child safety seat 40 to the child safety seat 40. The second restraint 15 can be a three-point restraint coupled to the vehicle seat 13, or can be a five-point restraint included in the child safety seat 40.

[0032] The vehicle interior 12 may include one or more of the onboard radar sensor 11, the camera 12, the LATCH sensor 14, and the weight sensor 16 to collect vehicle data 202. The vehicle data 202 includes one or more of vehicle event data 204, vehicle occupant data 206, restraint system data 208, and vehicle position 210. The vehicle event data 204 generally relates to actions taken by the vehicle 10 during operation. For example, the vehicle event data 204 may include vehicle speed, vehicle steering wheel angle, vehicle collision, or other vehicle operations that may cause the vehicle occupant and / or restraint 15 to move. The vehicle speed may be related to the current speed of the vehicle 10, whether the vehicle 10 has stopped, whether the vehicle 10 has changed speed quickly, and other events related to vehicle speed. In addition, the vehicle steering wheel angle may be related to the current angle of the steering wheel and whether the steering wheel angle changes quickly, indicating that the vehicle is turning or turning sharply. In addition, the vehicle collision data includes whether the vehicle 10 has experienced any kind of collision or impact.

[0033] The vehicle occupant data 206 generally relates to any sensed or collected data related to the load of an occupant to be secured by the restraint 15. The vehicle occupant data 206 may include biometric information of the occupant, including one or more of the vehicle occupant height and the vehicle occupant weight. In addition, the vehicle occupant data 206 may include data for each occupant in the vehicle 10, including occupants of child safety seats 40. In addition, the vehicle occupant data 206 may relate to items that may affect the safety of the occupants. For example, the vehicle occupant data 206 may include data related to bulky clothing worn by the occupant that may affect the restraint 15, or may include data related to loose items in the vehicle 10 that may move during vehicle operation and cause harm to the occupant.

[0034] The restraint system data 208 generally relates to any sensed or collected data related to the restraint 15 of the vehicle 10. The restraint system data 208 may include the position of the restraint 15, including the position relative to the body part of the vehicle occupant, so that it is possible to determine the correct placement (i.e., whether the upper portion 19 is disposed on the shoulder of the occupant), whether the restraint 15 is locked or unlocked, or whether the restraint 15 has the correct tightness in effect. In addition, the restraint system data 208 may include data corresponding to each restraint 15 of each vehicle seat 13 and / or the restraint 15 associated with the child safety seat 40 (i.e., the restraint that secures the child safety seat 40 to the vehicle seat 13 and the restraint 15 that secures the occupant to the child safety seat 40). In addition, the restraint system data 208 may include data related to the specific child safety seat 40 installed in the vehicle 10, including but not limited to the serial number of the child safety seat 40, the expiration date, the size and / or configuration of the child safety seat 40. In addition, the restraint system data 208 may include historical restraint system data 208, which includes data related to any past placement or configuration of the restraint 15.

[0035] The vehicle location 210 generally relates to the location of the vehicle 10. More specifically, the vehicle location 210 generally relates to the current location of the vehicle 10. The current vehicle location may be obtained from a global positioning system (GPS) or other navigation system, may be obtained from a user device such as a mobile phone or tablet, and / or may be obtained from a third-party processor 500 and transmitted to the vehicle processor 200. In addition, the vehicle location 210 may include route data, such that the route traveled by the vehicle 10 may also be transmitted to the vehicle processor 200. The route information may also include start and end point information. The route information may be obtained from user input, a vehicle navigation system, past driver activity, or a third-party processor 500 and transmitted to the vehicle processor 200.

[0036] Further references Figures 1 to 3, the server 300 is configured as a network and / or cloud-based system in communication with the vehicle processor 200. It is also contemplated that the vehicle processor 200 may transmit any or all of the vehicle data 202 to the server 300 for further processing and / or evaluation. In addition, the vehicle processor 200 and / or the server 300 may be continuously and / or periodically updated so that the vehicle data 202 is updated in real time.

[0037] The server 300 may also be configured to communicate with a third-party processor 500 to collect third-party data. For example, the third-party processor 500 may include, but is not limited to, a third-party database, such as a database including child safety seat information for a particular child safety seat 40 installed in the vehicle 10, such as installation instructions, height and / or weight requirements, expiration dates, troubleshooting suggestions, proper restraint placement, and / or recall information.

[0038] Still refer to Figures 1 to 3 In the example shown, the server 300 is configured to determine a baseline desired position for the restraint 15 based on the vehicle occupant data 206 and the restraint system data 208. The desired baseline position may be the safest position for the vehicle occupant based on the vehicle occupant's biometric information data and / or the safest configuration of the restraint 15. For example, the desired baseline position may include a vehicle seat 13 that is optimal for the occupant based on the occupant's height and weight. More specifically, the desired baseline position may include an indication of placing a certain passenger in the rear vehicle seat 13 based on their height and / or weight. Additionally, the desired baseline position may include an optimal position for each portion of the restraint 15. For example, the desired baseline position may include an upper portion 19 of the restraint that extends beyond the occupant's shoulders.

[0039] In addition, the server 300 is configured to determine whether any deviation from the desired baseline position of the restraint 15 has occurred based on one or more of the vehicle event data 204 and the restraint system data 208. More specifically, the server 300 can use data collected from the vehicle sensors 11, 14, 16 and / or the camera 12 and compare the data with the desired baseline position to determine whether any deviation has occurred. For example, the server 300 can use data collected from the vehicle camera 12 that shows that the upper portion 19 of the restraint no longer extends over the shoulder of the passenger, but is set behind the passenger to determine that a deviation from the desired baseline position has occurred. In addition, the server 300 is also configured to notify the occupant of any determined deviation from the desired position of the restraint 15. The notification can be through text or images displayed on the vehicle dashboard 30, through an audio system, or other notifications.

[0040] In addition, the server 300 is further configured to determine whether the occupant of the child safety seat 40 is within the safety limits of the installed child safety seat 40 based on the vehicle occupant data 206 and the restraint system data 208. More specifically, the server 300 may use the vehicle occupant data 206, data collected from the third-party processor 500 related to the specific child safety seat 40 installed, and the restraint system data 208, which includes the placement or adjustable configuration of the restraints 15 related to determining whether the vehicle occupant is within the safety limits of the child safety seat 40. For example, the server 300 may use the height and weight of the occupant from the vehicle occupant data 206 and the third-party data related to the height and / or weight limits of the child safety seat 40 to determine whether the height and weight of the occupant is within the height and / or weight limits of the child safety seat 40.

[0041] In addition, the server 300 is configured to determine whether the child safety seat 40 has been correctly installed based on the restraint system data 208. In addition, the server 300 can use data from the third-party processor 500 to check the installation of a specific child safety seat 40 based on the serial number. If the server 300 determines that the child safety seat 40 is not installed correctly, the server 300 can be configured to recommend installation techniques based on the restraint system data 208 to correct the installation of the child safety seat 40. The recommendation can be based on the restraint system data 208 and / or the third-party data. For example, the server 300 can recommend a specific installation or troubleshooting video that helps to properly install the child safety seat 40. In addition, if the child safety seat 40 is still not installed correctly after the recommendation, the server 300 can be configured to guide the vehicle 10 to the nearest fire station or police station for further assistance. For example, if the server 300 determines that the child safety seat 40 is not installed level, the server 300 can recommend an installation video from the manufacturer that describes how to level the child safety seat 40. If the child safety seat 40 is still not leveled after the recommendation, the server 300 will use the vehicle location 210 to determine the nearest fire station or police station that can provide further assistance.

[0042] Once it is determined that the child safety seat 40 has been properly installed, the server 300 can be configured to provide periodic and / or ongoing checks to confirm that the child safety seat 40 remains properly installed. In addition, since the child safety seat 40 often becomes loose over time, the server 300 can be configured to provide periodic reminders to the occupant to manually verify the correct installation of the child safety seat 40.

[0043] If it is determined that the position of the restraint 15 has moved from the desired baseline position, the vehicle occupant is not within the safety limits of the installed child safety seat 40, and / or the child safety seat 40 is not installed correctly, the server 300 is configured to determine the necessary response level. The response level may be based on one or more of the vehicle event data 204, the vehicle occupant data 206, and the restraint system data 208. The response level may include low urgency, medium urgency, or high urgency, and may include a corresponding notification level to the occupant. The response level may range from simply notifying the occupant of the problem in a low urgency situation to setting a speed limit on the vehicle 10 so that the vehicle 10 does not travel at a speed above the set speed before taking corrective action in a high urgency situation. For example, if the server 300 determines that one or more restraints 15 of the child safety seat 40 are unlocked, the server 300 may determine that the necessary response level is very urgent, and may subsequently implement a speed limit on the vehicle 10 until the problem is corrected.

[0044] In addition, the server 300 can be configured to determine a required correction method for the restraint system 15 based on one or more of the vehicle occupant data 206 and the restraint system data 208. For example, if the server 300 determines that the restraint 15 has been unlocked from the child safety seat 40, the server 300 can determine that a corrective action of the restraint 15 is required to re-lock the child safety seat 40. In addition, the server 300 can be configured to advise the occupant that the determined corrective action should be taken. For example, if the child safety seat 40 needs to be re-locked, the server 300 can be configured to display an image of the location and the desired corrective action on the vehicle dashboard 30. In addition, the display can be accompanied by an audio or other visual notification of the desired corrective action.

[0045] In addition to the foregoing, the server 300 may be configured to determine whether the child safety seat 40 should be replaced. For example, the server 300 may use the vehicle event data 204 to determine whether a vehicle impact event has occurred, and may use the restraint system data 208 to determine whether the impact force has affected the child safety seat 40. Furthermore, if it is determined that the child safety seat 40 should be replaced, notifications may continue to be issued to the driver until the child safety seat 40 is replaced.

[0046] Reference now Figure 3In the example shown, in operation, the safety equipment monitoring system 100 starts at step 500 and installs the child safety seat 40 at step 502. At step 504, the vehicle processor 200 is then configured to store the serial number or model number of the child safety seat 40 and the date and time of installation and upload it to the server 300. At step 506, the vehicle 10 begins to travel, and at step 508, the server 300 checks whether a predetermined time has passed since the child safety seat 40 has been installed. If the predetermined time has passed, then at step 510, the server 300 will warn the occupant to check the installation of the child safety seat 40 to ensure that it is still safe. Once the warning is completed, the server 300 will start a timer at the predetermined time at step 512 and repeat the process. However, if the predetermined time has not passed, the system 100 monitors the child safety seat 40 using the vehicle camera 14 and / or sensors 11, 13, 16 at step 514 and stores the vehicle data 202 at step 516. The system 100 also stores the movement pattern of the child safety seat 40 for historical reference at step 518. The server 300 then analyzes the data at step 520. At step 522, the analyzed data is used to determine whether a deviation from the desired position of the child safety seat 40 has occurred. If a deviation has occurred, the server 300 warns the occupant using one or more of an audio, visual, and mobile alert (i.e., an alert to a mobile device such as a cell phone or tablet associated with one or more vehicle occupants) at step 524. The server 300 may then provide a reason for the warning at step 526 and provide suggestions for remedying the problem detected at step 528 before concluding at step 530.

[0047] Restraint systems are important in vehicles because they protect vehicle occupants in the event of a vehicle crash. However, to be effective, the vehicle occupants must properly wear the restraints throughout the operation of the vehicle. While some vehicles include restraint detection systems that can notify vehicle occupants when vehicle restraints are not secured, proper placement of the restraints is also required to be effective. Therefore, the safety equipment monitoring system 100 as described herein can continuously detect and notify vehicle occupants of misplaced restraints to ensure the safety of all vehicle occupants.

[0048] 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 also within the scope of the following claims.

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

Claims

1. A safety device monitoring system for a vehicle, the safety device monitoring system comprising: a vehicle processor for storing vehicle data, the vehicle data including one or more of vehicle event data, vehicle occupant data, and restraint system data; as well as A server is communicatively coupled to the vehicle processor and is configured to: determining a baseline desired position of the restraint based on the vehicle occupant data and the restraint system data; and A determination is made based on one or more of the vehicle event data and the restraint system data as to whether any deviation from a desired position of the restraint has occurred.

2. The safety equipment monitoring system according to claim 1, wherein: The server is configured to notify the user of any determined deviations from the desired position of the constraint.

3. The safety equipment monitoring system according to claim 1, wherein: The vehicle occupant data includes biometric information of the vehicle occupant, including one or more of a vehicle occupant height and a vehicle occupant weight.

4. The safety equipment monitoring system according to claim 1, wherein: The restraint system data includes whether a child safety seat is installed.

5. The safety equipment monitoring system according to claim 4, wherein: The server is further configured to determine whether a vehicle occupant is within safety limits of an installed child safety seat based on the vehicle occupant data and the restraint system data.

6. The safety equipment monitoring system according to claim 1, wherein: The vehicle data is collected using one or more of onboard radars, cameras, lock sensors, and weight sensors.

7. The safety equipment monitoring system according to claim 1, wherein: The server is further configured to determine a level of responsiveness to a deviation from a desired seat belt position based on one or more of the vehicle event data, vehicle occupant data, and restraint system data.

8. The safety equipment monitoring system according to claim 7, wherein: The server is further configured to limit the speed of the vehicle if it is determined that an emergency corrective action is required.

9. The safety equipment monitoring system according to claim 1, wherein: The server is further configured to determine a required correction method based on one or more of the vehicle occupant data and the restraint system data.

10. A vehicle comprising the safety equipment monitoring system according to claim 1.

Images