WARNING SYSTEM AND PROCEDURES

Abstract

A warning system for a vehicle includes 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 include receiving location data from a user device, determining a location of the user device relative to the vehicle based on the location data, and configuring an electronic control unit (ECU) with a range. The operations also include issuing a vibration request based on the location of the user device and the range and executing a user warning application of the ECU based on the issued vibration request.

Description

INTRODUCTION

[0001] The information contained in this section is intended to provide a general context for the disclosure. Work by the presently named inventors, to the extent described in this introduction, as well as aspects of the description that may not otherwise be considered prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against this disclosure.

[0002] The present disclosure generally relates to a warning system for a vehicle that assists hearing aid wearers or distracted users using vibrations on a user device.

[0003] Vehicles are typically equipped with audible alerts designed to notify a user of a vehicle-related event. For example, if a user is not wearing a seatbelt, the vehicle may emit a beep or other audible warning until the seatbelt is fastened. While an audible alert is effective in reminding users of various vehicle features or related events, people with hearing impairments may benefit from additional forms of alert. Vehicles may also trigger a text notification on the vehicle's user interface in combination with the audible alert. While a text notification may be beneficial to a person with a hearing impairment, the person may occasionally miss the text notification during the period the text notification is displayed.Therefore, there is a need for improved alerts and notifications regarding vehicle alerts. SUMMARY

[0004] In some aspects, a computer-implemented method, when executed by the computing hardware, causes the computing hardware to perform operations. The operations include determining a location of a user device relative to a vehicle using location data, identifying a trigger event based on position data and a vehicle status, and issuing a vibration request to the user device via a user alert application. The operations also include receiving a vibration log from the user device, determining an alert level based on the trigger event and the vibration log, and executing an alert on the user device based on the alert level.

[0005] In some examples, the warning level may include a low level, a medium level, and a high level, and the vibration protocol may include a single vibration, a multiple vibration, and an extended vibration. The single vibration may correspond to the low level, the multiple vibration may correspond to the medium level, and the extended vibration may correspond to the high level. The operations may include executing a calibration protocol and determining the distance between a vehicle and the user device based on the calibration protocol. In some cases, determining the location of the user device may include detecting a digital key and matching the detected digital key to a stored digital key profile.In other examples, determining the location of the user device may include determining distance data and identifying a change in the distance data corresponding to the user device. Optionally, the operations may include determining a range corresponding to the user device's distance data. In some cases, determining the alert level may include comparing the change in the distance data to the determined range.

[0006] In other aspects, a system includes 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 include determining a location of a user device relative to a vehicle using location data, identifying a trigger event based on position data and a vehicle status, and issuing a vibration request to the user device via a user alert application. The operations also include receiving a vibration log from the user device, determining an alert level based on the trigger event and the vibration log, and executing an alert on the user device based on the alert level.

[0007] In some examples, the warning level may include a low level, a medium level, and a high level, and the vibration protocol may include a single vibration, a multiple vibration, and an extended vibration. The single vibration may correspond to the low level, the multiple vibration may correspond to the medium level, and the extended vibration may correspond to the high level. The operations may include executing a calibration protocol that includes detecting a digital key. In some cases, determining the location of the user device includes matching the detected digital key to a stored digital key profile. In other examples, determining the location of the user device includes determining distance data and identifying a change in the distance data corresponding to the user device.Optionally, the operations may include determining a range corresponding to the user device's distance data. In further examples, determining the alert level includes comparing the change in the distance data to the determined range.

[0008] In further aspects, a warning system for a vehicle includes 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 include receiving location data from a user device, determining a location of the user device relative to the vehicle based on the location data, and configuring an electronic control unit (ECU) with a range. The operations also include issuing a vibration request based on the location of the user device and the range, and executing a user warning application of the ECU based on the issued vibration request.

[0009] In some examples, the operations may include identifying a trigger event via the user alert application and issuing an alert via the user alert application in response to the trigger event. Optionally, the operations may include comparing the position of the user device to the configured range, and executing the user alert application includes issuing an alert in response to comparing the position of the user device to the configured range. In some cases, the operations may include executing a vibration protocol in response to the issued vibration request, wherein the vibration protocol corresponds to the alert. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The drawings described herein are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Fig. 1 is an example schematic of a vehicle with a user walking away from the vehicle with a user device equipped with an alert application according to the present disclosure; Fig. 2 is an example diagram of a user walking away from a vehicle at different distances, the user wearing a user device equipped with an alert application in accordance with the present disclosure; Fig. 3 is an exemplary block diagram of a warning system according to the present disclosure; Fig. 4 is a partial perspective view of the interior of a vehicle equipped with a warning system according to the present disclosure; Fig. 5 is an exemplary flowchart for a warning system according to the present disclosure; and Fig. Figure 6 is another example flowchart for the warning system of Fig. 5.

[0011] In the drawings, corresponding reference symbols designate corresponding parts. DETAILED DESCRIPTION

[0012] Example configurations will now be described in more detail with reference to the accompanying drawings. Because example configurations are provided, this is a thorough disclosure designed to convey the full scope of the disclosure to those skilled in the art. Specific details are set forth, such as examples of specific 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 used, 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 specific example configurations only and is not intended to be limiting. As used herein, the singular articles “a,” “an,” and “the” can also include the plural forms, unless the context clearly indicates otherwise. The terms “comprise,” “comprising,” “containing,” 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, or groups thereof. The steps, processes, and operations described herein should not be construed as necessarily being performed in the particular order explained or illustrated unless they are expressly identified as being in that order of performance.Additional or alternative steps may be applied.

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

[0015] The terms "first," "second," "third," etc., may be used herein to describe various steps, elements, components, regions, layers, and / or sections. These elements, components, regions, layers, and / or sections should not 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 the context clearly indicates otherwise.Thus, a first element, component, region, layer, or section discussed below could be referred to as a second element, component, region, layer, or section without departing from the teachings of the example configurations.

[0016] For the purposes of this application, which includes 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 (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 described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0017] The term "code" as used above can include software, firmware and / or microcode and can refer to programs, routines, functions, classes and / or objects. The term "shared processor" includes a single processor that executes code from multiple modules in part or in whole. The term "group processor" includes a processor that, in combination with additional processors, executes code from one or more modules in part or in whole. The term "shared memory" includes a single memory that stores code from multiple modules in part or in whole. The term "group memory" includes memory that, in combination with additional memory, stores code from one or more modules in part or in whole. The term "memory" is a subset of the term "computer-readable medium".The term "computer-readable medium" does not encompass transitory electrical or electromagnetic signals propagating through a medium and can therefore be considered tangible and non-transitory. 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 entirely by one or more computer programs executed by one or more processors. The computer programs include processor-executable instructions stored on at least one non-transitory, tangible, computer-readable medium. The computer programs may also include and / or be based on 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 store programs (e.g., sequences of instructions) or data (e.g., information about program state) on a temporary or permanent basis 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, among others, 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, among others, 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) comprise machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented language and / or 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 deliver 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 used to provide machine instructions and / or data to a programmable processor.

[0022] Various implementations of the systems and techniques described herein may be embodied in digital electronic and / or optical circuits, integrated circuits, purpose-built 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 a special-purpose or general-purpose processor, coupled to receive data and instructions from and communicate 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 patent may be performed 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 performed by special-purpose logic circuits, 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 and one or more processors of any type of digital computer. Generally, a processor receives instructions 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 memory devices for storing instructions and data. Generally, a computer will also include, or be 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 to or from them, or both. However, a computer need not include these 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 as internal 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 logic circuits.

[0024] To enable interaction with a 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 touch screen for displaying information to the user, and optionally a keyboard and a 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 interact with a 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 the user's input may be received in any form, including auditory, voice, 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 documents requested by the web browser.

[0025] With reference to Fig. 1-3, a warning system 10 for a vehicle 100 includes an electronic control unit (ECU) 12 of the vehicle and a user device 200 in communication with the ECU 12. The ECU 12 is configured with a user warning application 14 executed by computing hardware 16 of the ECU 12. The ECU 12 also includes memory hardware 18 in communication with the computing hardware 16. The memory hardware 18 stores instructions that, when executed on the computing hardware 16, cause the computing hardware 16 to perform operations described herein. For example, the computing hardware 16 is configured to execute the user warning application 14 to output alerts 20 from the user warning application 14 to the user device 200. The warning system 10 is designed to advantageously provide tactile feedback to a user, whether using hearing aids or not, based on the user's hearing status.Thus, the warning system 10 advantageously provides tactile feedback to the user regardless of his hearing status.

[0026] The user alert application 14 is configured to issue the alert 20 or alerts 20 with varying degrees of alert levels 22 such that the user device 200 receives the alert level 22 to assist, for example, a hearing amplification device (not shown). The alert levels 22 may include, but are not limited to, a low level 22a, a medium level 22b, and a high level 22c. The alert levels 22 may also have a variable range that can detect levels between each of the low, medium, and high levels 22a-22c. For example, the alert levels 22 may increase incrementally between the various alert levels 22. Each of the 22 alert levels is described in more detail below with respect to the vehicle 100 and the user device 200 and the operation of the alert system 10.The ECU 12 is equipped with various short-range wireless communication protocols, including Bluetooth® Low Energy (BLE) and Ultra-Wide Band (UWB). For example, the ECU 12 can detect when a user 210 is inside the vehicle 100 via UWB, and when the user 210 exits the vehicle 100, BLE can be used to determine position data 24 based on the BLE communication with the user device 200.

[0027] Furthermore, the ECU 12 may use BLE channel probing (BLE / CS) to determine a distance D1-D n between the user device 200 and the vehicle 100. Channel sounding (CS) is a subset of Bluetooth® technology that measures a distance between a user device 200 and the equipped CS device (e.g., the ECU 12) by calculating a series of frequencies to determine a distance D1-D nbetween the user device 200 and the ECU 12. Thus, the ECU 12 may use CS to estimate location data 202 and, in particular, distance data 202a of the user device 200. For example, the ECU 12 may use UWB and BLE / CS as a complement depending on the range of UWB and BLE / CS. The distance data 202a is used by the user alerting application 14 to determine whether to issue an alert 20 and the alert level 22, as described herein. The user alerting application 14 uses BLE / CS to determine the position of the user 210 and subsequently establish an order for issuing the alerts 20. For example, the user alerting application 14 may establish a hierarchy of alert levels 22 based on the distance data 202a, such that the alert 20 with the highest priority alert level 22 at a previous distance D1-D n can be issued.

[0028] In other examples, the ECU 12 may use a BLE received signal strength indicator (RSSI) that evaluates the performance of the transmission between the user device 200 and the ECU 12. For example, the ECU 12 may use a combination of UWB and BLE RSSI to determine the signal strength of the user device 200 and thus estimate the distance data 202a by using a complement depending on a range of each of the UWB and BLE RSSI. In another example, the ECU 12 may use a combination of UWB and Wi-Fi® orbital wave time to estimate the distance data 202a. In other examples, the ECU 12 may use a combination of UWB, BLE RSSI, and CS and / or a combination of UWB, BLE RSSI, CS, and Wi-Fi® orbital wave time to estimate the distance data 202a.In these examples, UWB provides a high-accuracy estimate at short range, while BLE / CS, BLE RSSI, and / or Wi-Fi® orbital wave time each provide a medium-accuracy estimate at long range. Furthermore, any of the above combinations of UWB, BLE / CS, BLE RSSI, and / or Wi-Fi® orbital wave time can be calibrated as part of the warning system 10.

[0029] With continued reference to Fig. 1-3, the memory hardware 18 may store a digital key profile 30 corresponding to a digital key 204 of the user device 200. For example, a user 210 pairs the user device 200 to the vehicle 100 via the ECU 12 by setting the digital key profile 30. In some examples, the user 210 may execute a digital key application on the user device 200 to pair the user device 200 with the digital key 204 to the ECU 12. The user device 200 may include, among other things, a mobile phone, a tablet, and / or a smartwatch. As illustrated, the user device 200 is a smartwatch worn by the user 210. However, the user device 200 may be any device capable of receiving information or data from the ECU 12.

[0030] After pairing, the user device 200 may send and receive information to and from the ECU 12, including the alerts 20. During the pairing process, the ECU 12 may execute a calibration protocol 26 to calibrate a range 32 corresponding to the distances D1-D n of the user device 200 relative to the ECU 12 and thus to the vehicle 100. For example, the user alert application 14 may use the calibration protocol 26 to set alerts 20 within one or more predetermined ranges 32. In some examples, the vehicle application 208 may notify the user alert application 14 that the user device 200 has moved a first distance D1 from the vehicle 100, and the user alert application 14 may issue an alert 20 in response.

[0031] The distances D1-D nmay include the first distance D1, a second distance D2 and a third distance D3. Similar to warning levels 22, the distances D1-D3 may extend over a varying degree of distances D1-D n within the predetermined range 32 stored in the memory hardware 18. Thus, each distance D1-D3 may have a respective range 32 that may at least partially overlap with or extend from a previous distance D1-D3. With respect to the first distance D1, the range 32 is determined based on the ECU 12 losing UWB contact with the user device 200 and instead using BLE / CS to monitor the distance data 202a of the user device 200. The first distance D1 may overlap with the range 32 in which the ECU 12 may utilize UWB and BLE / CS to minimize connection losses and maintain tracking of the distance data 202a.

[0032] With reference to Fig. 2-4, the distances D1-D3 generally correspond to different trigger events 40 that may occur relative to the vehicle 100. However, it is also contemplated that the trigger events 40 may occur within the vehicle if the ECU 12 uses UWB to monitor the position data 24 and / or the location data 202 of the user device 200. The Fig. 2-4 generally illustrate examples of trigger events 40. For example, user 210 may enter vehicle 100 and partially close a door 102 of vehicle 100. Consequently, the partially closed door 102 may be a trigger event 40 of user alert application 14, and user alert application 14 may issue an alert 20 in response. User alert application 14 may increase alert level 22 based on the duration of alert 20. For example, if user 210 does not respond to alert 20, user alert application 14 may increase a low level alert 22a to a medium level alert 22b.

[0033] In other examples, the lights of vehicle 100 may be on and the user 210 may exit the vehicle 100. The user alert application 14, in response to receiving the distance data 202a, may issue a low-level alert 22a to remind the user 210 that the lights are still on. The user may disable the alert 20 and / or may use the digital key 204 to stop the lights from operating. In some cases, the user 210 may leave the digital key 204 or a key fob in the vehicle 100. The user alert application 14 may determine the location data 202 of the user 210 based on the user device 200 and may issue an alert 20 in response. For example, the user may leave a mobile device in the vehicle 100, and the user alert application 14 may send the alert to a smartwatch 200 worn by the user 210.The ECU 12 can track when the user 210 leaves the vehicle 100 via the location data 24 by determining that the user device 200 is outside of the UWB range. If the user 210 leaves a device equipped with the digital key 204 in the vehicle 100, the user alert application 14 can alert the worn user device 200 (e.g., a smartwatch) based on the distance data 202a.

[0034] When the user alert application 14 executes the calibration protocol 26, the user alert application 14 calibrates the alert level 22 in addition to the range 32. The user device 200 may also be configured with a vibration protocol 206, which may be stored on the user device 200 as part of a vehicle application 208. The vehicle application 208 may store and execute the digital key 204 and provide the connection to the ECU 12 to receive the position and distance data 202, 202a. The vibration protocol 206 may include, among other things, a single vibration 206a, a multiple vibration 206b, and / or an extended vibration 206c. The vibration protocol 206 may be shared with the user alert application 14 in response to a vibration request 28 issued by the user alert application 14 as part of the alert 20.The vibration protocol 206 provides beneficial support for users who use hearing aids or other hearing amplification devices. Furthermore, the vibration protocol 206 can assist users who otherwise intentionally or inadvertently ignore audible or text alerts by alerting the user regardless of their hearing status.

[0035] After receiving the vibration protocol 206, the user alert application 14 may determine which vibration 206a-206c of the vibration protocol 206 to execute based on the alert level 22. In some examples, the user 210 may configure the vibration protocol 206 to correspond to specific alert levels 22. For example, the single vibration 206a may correspond to the low level 22a, the multiple vibration 206b may correspond to the medium level 22b, and the extended vibration 206c may correspond to the high level 22c. However, various applications of the vibration protocol 206 may be used, so each vibration 206a-206c of the vibration protocol 206 may be used interchangeably with the various alert levels 22. In other examples, in response to receiving the vibration protocol 206, the user alert application 14 may adjust the vibration 206a-206c for each of the alert levels 22.

[0036] The user alert application 14 cooperates with the vibration protocol 206 of the user device 200 to vibrate the user device 200 when the user alert application 14 issues an alert 20. The user alert application 14 can determine which vibration 206a-206c should be associated with a respective alert level 22 and can communicate the determined vibration 206a-206c to the user device 200. The user device 200 can then execute the corresponding vibration protocol 206 to vibrate the user device 200 according to the alert level 22.

[0037] As mentioned above, the user alert application 14 issues the alert 20 in response to one or more trigger events 40. The trigger event 40 may include, but is not limited to, a seatbelt fastening reminder, a door open, lighting operation, vehicle status, window status, roof status, and / or any other event that may trigger or result in an audible alert or alarm. The user alert application 14 utilizes the combination of the detection of the trigger event 40 and the distance data 202a to determine the alert 20. In some cases, the ECU 12 may determine a change in the distance data 202a according to the user device 200. For example, the first distance D1 may correspond to approximately ten (10) meters, the second distance D2 may correspond to approximately twenty (20) meters, and a third distance D3 may correspond to approximately thirty (30) meters.Each distance D1-D3 can be linked to a warning level 22 and a specific trigger event 40 determined by the user warning application 14.

[0038] In some examples, the first distance D1 may correspond to trigger events 40 with a high level 22c. For example, if the user 210 is running the engine, the user alert application 14 may issue an alert 20 with a high alert level 22c corresponding to the enhanced vibration 206c. Thus, in response to determining the trigger event 40 and the corresponding alert level 22, the user alert application 14 issues the vibration request 28 to the user device 200. In this example, the vibration request 28 requests the user device 200 to execute the enhanced vibration 206c of the vibration protocol 206.

[0039] In other examples, the second distance D2 may correspond to the fact that the door 102 is left open or a window 104 remains partially or fully open, such that the user alert application 14 identifies the trigger event 40 when the user approaches the second distance D2. In response, the user alert application 14 may issue the vibration request 28 to the user device 200, which includes the alert 20 with the medium level 22b. In further examples, the third distance D3 may correspond to the remaining operability of the lighting, as mentioned above. In this example, the user alert application 14 may issue the vibration request 28, which includes an alert 20 with a low alert level 22a. The user alert application 14 may adjust the vibration 206a-206c based on the alert level 22 by communicating the alert level 22 to the user device 200.Thus, the user alert application 14 may determine the alert level 22 by comparing a change in the distance data 202a with the range 32.

[0040] As mentioned above, the user alert application 14 uses BLE to transmit the vibration request 28 to the user device 200. For example, the user alert application 14 sends the vibration request 28 to the vehicle application 208 on the user device 200 using BLE, requesting the execution of the vibration protocol 206. When the user 210 is inside the vehicle 100, the ECU 12 may use UWB to identify the user's location data 202, and when the user 210 exits the vehicle 100, it may switch to BLE to monitor the distance data 202a in addition to the location data 202.

[0041] To determine that the user 210 is within the vehicle 100, the ECU 12 may use a positioning method based on a signal arrival time to estimate the location data 202 of the user 210. For example, the ECU 12 may utilize trilateral ranging using UWB. Once identified, the ECU 12 shares the location data 202 with the user alert application 14 and may issue an alert 20 depending on the position of the user 210 within the vehicle 100. When determining whether the user has exited the vehicle 100, the ECU 12 may first determine whether the user device 200 is outside of UWB range.When the user device 200 is out of UWB range, the ECU 12 may switch to using BLE / CS by using a phase shift analysis of different tones between a received radio signal and a transmitted radio signal between the ECU 12 and the user device 200.

[0042] Depending on the location data 202 and / or distance data 202a determined by the ECU 12, the user may receive a distinguishable vibration 206a-206c corresponding to the alert 20. Thus, the alert system 10 utilizes a hybrid UWB and BLE / CS technology to identify the trigger event(s) 40 and subsequently notify the user via the user alert application 14.

[0043] With reference now to Fig. 5 and Fig. 6, an exemplary flowchart for the warning system 10 is set forth. In step 400, the user device 200 is coupled to the ECU 12 of the vehicle 100, and in step 402, the vehicle 100 is connected to the user device 200. The ECU 12 determines at 404 whether the user 210 is inside the vehicle 100 using a matrix of UWB devices distributed around the vehicle 100. If the user 210 is not inside the vehicle 100, the ECU 12 proceeds as described below with respect to steps 412-424. If the user 210 is inside the vehicle 100, the ECU 12 determines at 406 whether a door 102 is open. If the door 102 is not open, the ECU 12 determines at 408 whether a seatbelt alert is active. If the door 102 is not open and the seatbelt alert is not active, the ECU 12 returns to monitoring whether the user 210 is inside the vehicle 100.When the door 102 is open and / or the seatbelt alert tone is active, the ECU 12 executes the user alert application 14 to send the vibration request 28 to the user device 200. Although the steps described with respect to the flowchart in FIG. Fig. 5 is an open door 102 and / or a seatbelt beep, the trigger event 40 may be any of the trigger events described herein, and the flowchart for the alarm system 10 may proceed accordingly.

[0044] If the user 210 is outside the vehicle 100, the ECU 12 monitors a distance D1-D3 of the user 210 using BLE channel probing at 412, as mentioned above. The ECU 12 determines at 414 whether the user 210 is approaching the first distance D1. If so, the ECU 12 may execute the user alert application 14 at 416 to issue an alert 20 with a low level 22a. If the user 210 has exceeded the first distance D1, the ECU 12 determines at 418 whether the user 210 is approaching the second distance D2. If so, the ECU 12 may execute an alert 20 with the medium level 22b at 420. If the user 210 has exceeded the second distance D2, the ECU 12 may determine at 422 whether the user 210 is approaching the third distance D3. If the user 210 is approaching the third distance D3, the ECU 12 may execute the user alert application 14 at 424 to issue an alert 20 with a high level 22c.If the user 210 is not approaching the third distance D3 or has already exceeded it, the ECU 12 continues to monitor the distance data 202a.

[0045] While a number of implementations have been described, it should be understood that various changes may be made without departing from the spirit and scope of the disclosure. Accordingly, other embodiments are also within the scope of the following claims.

[0046] The foregoing description is for purposes of illustration and description only. It is not intended to be exhaustive or limiting of the disclosure. Individual elements or features of a particular arrangement are generally not limited to that particular arrangement, but are interchangeable and may be used in a selected arrangement even if not specifically shown or described. They may also be modified in many ways. Such modifications are not to be regarded as a departure from the disclosure, and all such changes are intended to be included within the scope of the disclosure. legend

[0047] In the drawings, N stands for No and Y stands for Yes.

Claims

[1] System that includes: 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, comprising: Determining, via location data, a location of a user device relative to a vehicle; Identifying a trigger event based on position data and vehicle status; issuing a vibration request to the user device via a user alert application; Receiving a vibration log from the user device; Determining a warning level based on the trigger event and the vibration log; and Execute an alert on the user device based on the alert level. [2] The system of claim 1, wherein the warning level comprises a low level, a medium level, and a high level, and the vibration protocol comprises a single vibration, a multiple vibration, and an extended vibration. [3] The system of claim 2, wherein the single vibration corresponds to the low level, the multiple vibration corresponds to the medium level, and the extended vibration corresponds to the high level. [4] The system of claim 1, further comprising executing a calibration protocol that includes detecting a digital key. [5] The system of claim 4, wherein determining the location of the user device comprises matching the detected digital key with a stored digital key profile. [6] The system of claim 4, further comprising determining, based on the calibration protocol, a distance between a vehicle and the user device. [7] The system of claim 1, wherein determining the location of the user device comprises determining distance data and identifying a change in the distance data corresponding to the user device. [8] The system of claim 7, further comprising determining a range corresponding to the user device distance data. [9] The system of claim 8, wherein determining the warning level comprises comparing the change in the distance data with the determined range. [10] A vehicle comprising the system of claim 1.

Images