WO2017160285A1 - Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés - Google Patents

Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés Download PDF

Info

Publication number
WO2017160285A1
WO2017160285A1 PCT/US2016/022582 US2016022582W WO2017160285A1 WO 2017160285 A1 WO2017160285 A1 WO 2017160285A1 US 2016022582 W US2016022582 W US 2016022582W WO 2017160285 A1 WO2017160285 A1 WO 2017160285A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
wearable device
data
computer system
device data
Prior art date
Application number
PCT/US2016/022582
Other languages
English (en)
Inventor
Hussein F. Nasrallah
David Anthony Hatton
Johannes Geir Kristinsson
Thomas Nelson
Krishnaswamy Venkatesh Prasad
Original Assignee
Ford Global Technologies, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ford Global Technologies, Llc filed Critical Ford Global Technologies, Llc
Priority to PCT/US2016/022582 priority Critical patent/WO2017160285A1/fr
Publication of WO2017160285A1 publication Critical patent/WO2017160285A1/fr

Links

Classifications

    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60K—ARRANGEMENT OR MOUNTING OF PROPULSION UNITS OR OF TRANSMISSIONS IN VEHICLES; ARRANGEMENT OR MOUNTING OF PLURAL DIVERSE PRIME-MOVERS IN VEHICLES; AUXILIARY DRIVES FOR VEHICLES; INSTRUMENTATION OR DASHBOARDS FOR VEHICLES; ARRANGEMENTS IN CONNECTION WITH COOLING, AIR INTAKE, GAS EXHAUST OR FUEL SUPPLY OF PROPULSION UNITS IN VEHICLES
    • B60K28/00—Safety devices for propulsion-unit control, specially adapted for, or arranged in, vehicles, e.g. preventing fuel supply or ignition in the event of potentially dangerous conditions
    • B60K28/10—Safety devices for propulsion-unit control, specially adapted for, or arranged in, vehicles, e.g. preventing fuel supply or ignition in the event of potentially dangerous conditions responsive to conditions relating to the vehicle 
    • B60K28/14—Safety devices for propulsion-unit control, specially adapted for, or arranged in, vehicles, e.g. preventing fuel supply or ignition in the event of potentially dangerous conditions responsive to conditions relating to the vehicle  responsive to accident or emergency, e.g. deceleration, tilt of vehicle
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W40/00—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models
    • B60W40/08—Estimation or calculation of non-directly measurable driving parameters for road vehicle drive control systems not related to the control of a particular sub unit, e.g. by using mathematical models related to drivers or passengers
    • B60W2040/0872—Driver physiology
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2540/00—Input parameters relating to occupants
    • B60W2540/221—Physiology, e.g. weight, heartbeat, health or special needs
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60W—CONJOINT CONTROL OF VEHICLE SUB-UNITS OF DIFFERENT TYPE OR DIFFERENT FUNCTION; CONTROL SYSTEMS SPECIALLY ADAPTED FOR HYBRID VEHICLES; ROAD VEHICLE DRIVE CONTROL SYSTEMS FOR PURPOSES NOT RELATED TO THE CONTROL OF A PARTICULAR SUB-UNIT
    • B60W2556/00—Input parameters relating to data
    • B60W2556/45—External transmission of data to or from the vehicle

Definitions

  • the illustrative embodiments generally relate to utilizing features of wearable devices that interact with a vehicle computer system.
  • Wearable devices may be worn by users to monitor their daily activity. Wearable devices worn by users may also be utilized while in a vehicle. A vehicle may communicate data with a wearable device to be utilized in various vehicle settings.
  • a first illustrative embodiment discloses a vehicle computer system comprising a wireless transceiver configured to receive wearable device data from one or more wearable devices each corresponding to an occupant.
  • the vehicle computer system further comprises a processor configured to output to an off-board server a parameter indicative of a severity of a vehicle accident in response to the wearable device data indicating pre-accident to post-accident changes in relative occupant location.
  • a second illustrative embodiment discloses a vehicle comprising a vehicle processor in communication with a wireless transceiver that is configured to receive wearable device data from wearable devices worn by occupants of the vehicle and configured to output to an emergency service provider, in response to vehicle impact, a parameter indicative of a degree of the vehicle impact based on the wearable device data indicating pre-impact to post-impact changes in relative occupant location.
  • a third illustrative embodiment discloses a vehicle computer system comprising a wireless transceiver configured to communicate with a plurality of wearable devices that each correspond to one of a plurality of occupants.
  • the vehicle computer system further includes a processor configured to receive wearable device data from the wearable devices via the transceiver and, in response to a detected accident condition, to output to the transceiver age-range data of the occupants derived from the wearable device data.
  • Figure 1 illustrates an example block topology for a vehicle based computing system for a vehicle.
  • Figure 2 illustrates an example block topology of a vehicle based computing system utilizing various wearable devices during an emergency situation.
  • Figure 3 illustrates an illustrative sequence diagram identifying data communication between a vehicle and a wearable device during a vehicle emergency.
  • Figure 4 illustrates an exemplary flow chart for utilizing wearable device data in the event of a vehicle emergency.
  • Figure 1 illustrates an example block topology for a vehicle based computing system
  • VCS vehicle-based computing system 1
  • SYNC system manufactured by THE FORD MOTOR COMPANY
  • a vehicle enabled with a vehicle-based computing system may contain a visual front end interface 4 located in the vehicle.
  • the user may also be able to interact with the interface if it is provided, for example, with a touch sensitive screen.
  • the interaction occurs through, button presses, spoken dialog system with automatic speech recognition and speech synthesis.
  • a processor 3 controls at least some portion of the operation of the vehicle-based computing system.
  • the processor allows onboard processing of commands and routines.
  • the processor is connected to both non-persistent 5 and persistent storage 7.
  • the non- persistent storage is random access memory (RAM) and the persistent storage is a hard disk drive (HDD) or flash memory.
  • the processor is also provided with a number of different inputs allowing the user to interface with the processor.
  • a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24 and a BLUETOOTH input 15 are all provided.
  • An input selector 51 is also provided, to allow a user to select between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor.
  • these and other components may be in communication with the VCS over a vehicle multiplex network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).
  • Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output.
  • the speaker is connected to an amplifier 1 1 and receives its signal from the processor 3 through a digital-to-analog converter 9.
  • Output can also be made to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.
  • the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., wearable device, cell phone, smart phone, PDA, tablet, a device having wireless remote network connectivity, etc.).
  • the nomadic device can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57.
  • tower 57 may be a WiFi access point.
  • Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.
  • Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with nomadic device 53.
  • a data-plan data over voice
  • DTMF tones associated with nomadic device 53.
  • the nomadic device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57.
  • the modem 63 may establish communication 20 with the tower 57 for communicating with network 61.
  • modem 63 may be a USB cellular modem and communication 20 may be cellular communication.
  • the processor is provided with an operating system including an API to communicate with modem application software.
  • the modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device).
  • Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols.
  • IEEE 802 LAN (local area network) protocols include WiFi and have considerable cross- functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle.
  • Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.
  • nomadic device 53 includes a modem for voice band or broadband data communication.
  • a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domain Multiple Access (SDMA) for digital cellular communication.
  • CDMA Code Domain Multiple Access
  • TDMA Time Domain Multiple Access
  • SDMA Space-Domain Multiple Access
  • ITU IMT-2000 (3G) compliant standards offer data rates up to 2 mbs for stationary or walking users and 385 kbs for users in a moving vehicle.
  • 3G standards are now being replaced by IMT-Advanced (4G) which offers 100 mbs for users in a vehicle and 1 gbs for stationary users.
  • 4G IMT-Advanced
  • nomadic device 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31.
  • the ND 53 may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802. l lg network (i.e., WiFi) or a WiMax network.
  • LAN wireless local area network
  • incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3.
  • the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.
  • Additional sources that may interface with the vehicle include a personal navigation device 54, having, for example, a USB connection 56 and/or an antenna 58, a vehicle navigation device 60 having a USB 62 or other connection, an onboard GPS device 24, or remote navigation system (not shown) having connectivity to network 61.
  • USB is one of a class of serial networking protocols.
  • IEEE 1394 FireWireTM (Apple), i.LI KTM (Sony), and LynxTM (Texas Instruments)
  • EIA Electros Industry Association
  • IEEE 1284 Chip Port
  • S/PDIF Synchronization/Philips Digital Interconnect Format
  • USB-IF USB Implementers Forum
  • the CPU could be in communication with a variety of other auxiliary devices
  • auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, nomadic device, key fob and the like.
  • the CPU could be connected to a vehicle based wireless router
  • WiFi IEEE 83.11
  • the exemplary processes may be executed by a computing system in communication with a vehicle computing system.
  • a computing system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device.
  • a wireless device e.g., and without limitation, a mobile phone
  • a remote computing system e.g., and without limitation, a server
  • VACS vehicle associated computing systems
  • particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system.
  • VACS vehicle computing system
  • FIG. 2 illustrates an example block topology of a vehicle based computing system that may be utilized for assistance during a vehicle emergency.
  • the vehicle 201 may include vehicle modules to detect an emergency situation 203, including various sensors, processor, or controllers. Such vehicle modules may be utilized to detect a crash, sudden acceleration/deceleration, impacts, air bag deployment, etc. The modules may be in communication with one another or other remote services in order to recognize an emergency situation.
  • the vehicle may include multiple occupants, including a driver and passengers.
  • the occupants may wear wearable devices that they own or utilize that interact with the vehicle computer system (VCS).
  • VCS vehicle computer system
  • Such wearable devices may include smart glasses, smart watch, pedometer, activity tracker or health monitor (e.g. FITBIT), clothing that includes sensors (e.g. E-textiles, smart shirt, etc), GPS watch, or other type of devices.
  • the devices may interact with the vehicle computer system via wireless or wired communication.
  • the vehicle computer system may be configured to interact with multiple devices 205, 207, 209.
  • the vehicle 201 may include a first occupant wearing a wearable device 205, a second occupant wearing a second wearable device 207, and a third occupant wearing a third wearable device (FITBIT) 209.
  • the VCS may also be in communication with nomadic devices, such as phones.
  • the vehicle computer system may exchange data with the wearable devices and nomadic devices for various applications.
  • the vehicle 201 may send the transmission of all connected wearables data, which could include the number of passengers and additional info 21 1 to the cloud 213.
  • the cloud 213 may utilize the data for enhancing emergency services, if necessary.
  • the cloud may also have additional data to extract related to the user or vehicle based on the wearable devices and information/data from the vehicle computer system. For instance, the cloud may recognize attributes of a particular vehicle involved in the accident based on the vehicle identification number (VEST), which can tailor emergency services to the vehicle.
  • VEST vehicle identification number
  • the cloud 213 may have access to additional databases or off-board servers to communicate vehicle information, such as make, model, year, engine-type, etc. Additionally, the cloud 213 may receive data from the wearable devices to recognize an occupant.
  • the cloud may have additional access to other databases or servers to retrieve additional data, such as emergency contact information, preferred physician, or other data.
  • the cloud may send part or all of the data 221 to an emergency operator 215.
  • the emergency operator 215 may be able to utilize the data to enhance services provided to the vehicle 201 and occupants.
  • a wearable device may be able to send movement data to an emergency service provider that is related to the user.
  • the movement data may be relevant to a specific body part of the user.
  • the movement data may be analyzed pre-crash and post-crash to detect any serious conditions, injuries, or other data.
  • the data utilized by the wearable device may be sent to the cloud 213 to be input to create a determination of various vehicle conditions (impact of the crash, number of occupants, ages of the occupants, situation of the occupant, severity of the accident, determines type of hospital to send users based on the emergency, etc.).
  • the vehicle may monitor the wearable device data before a crash, and compare it to the data after a crash. After analyzing such data, the severity of the accident may be determined (e.g. ranked low severity to high severity) and provided to an emergency responder or other third party.
  • the emergency operator 215 may also be able to send some or all of the data 223 to the emergency responder 217.
  • the emergency responder may utilize the data for prompt responses.
  • the emergency responder may be able to utilize the analytics from the wearable device data that identifies the number of occupants, ages of the occupants, situation of the occupant, severity of accident, recommended type of hospital, etc.
  • the analytics may also be able to be sent to a hospital, doctors, helicopter response, and fire-department.
  • the wearable device data indicates that a roll-over accident occurred
  • the vehicle may send data indicating a roll-over occurred to an emergency responder.
  • the vehicle or emergency responder may notify the fire department that the "Jaws of Life" may be needed to assist in the incident.
  • FIG 3 shows an illustrative sequence diagram of a vehicle based computing system in communication with wearable devices that illustrate the transfer of various communication and data.
  • the VCS may utilize a Bluetooth transceiver to pair with a wear device 301.
  • the pairing process may utilize different Bluetooth profiles to facilitate communication between the VCS and the wearable device. Some of these profiles may include HFP, A2DP, AVRCP, PBAP, HID, BVRA (part of the HFP profile), etc.
  • the pairing process may be accomplished from either the wearable device or the VCS.
  • the vehicle may be in communication with a first wearable device 301, a second wearable device 302, or other wearable devices 303.
  • a first wearable device 301 a wearable device 301
  • a second wearable device 302 a wearable device 303
  • other wearable devices 303 Given m vehicle occupants, each with up to n possible wearables 303, one can represent an occupant-wearable (O-W) matrix in the form of the following matrix:
  • An represents the j wearable of the i occupant.
  • the vectorial Aj 2 ... A in ] represents the n possible wearables associated with the t th occupant.
  • the system may detect a number of wearables detected within the vehicle. For purposes of this embodiment, the system may assume P wearables are detected on the interior. In subsequent steps, these P wearables will need to be associated with the Q possible individual occupants with wearables.
  • the process of detecting the Q possible vehicle occupants with wearables itself may utilize four-dimensional (three spatial dimensions and one temporal dimension) spatial clustering to identify Q possible clusters and label the occupants from 1 to Q based on the locations of the detected wearables.
  • a single occupant may include multiple wearables that could be detected to be correlated to a specific occupant.
  • a single occupant may include a mobile device and a smart watch.
  • an O-W matrix may be mapped into a state matrix
  • the matrix S is expected to be a sparse matrix (i.e., containing a number of zeroes) but the key novelty is in using this matrix to infer a number of properties, including: (1) the minimum number of occupants; (2) the possible range of ages of occupants; (3) the locations of occupants; (4) measure of any gradual or sudden occupant movement.
  • the wearable device data may be utilized to determine all of these estimate either onboard at the vehicle or at an off-board server. Each of these estimates may be utilized to be output to a server of emergency service provider during a vehicle emergency.
  • the wearable device may be able to track and monitor fine tune movement for a specific body part of a user, which a mobile phone or another device may not be able to do. Furthermore, a user may be wearing multiple wearable devices for more accurate fine movement precision.
  • N_occupant N_occupant + 1 ;
  • N_occupant N_occupant;
  • a number of other estimates could be made, including: (1) the current and immediate past heart-rates; (2) the current and immediate past pulse-rates; (3) blood glucose rates, where applicable; (4) other conditions including but not limited to whether or not there are occupants with special needs.
  • the wearable device data may be utilized to determine all of these estimate either onboard at the vehicle or at an off-board server. Each of these estimates may be utilized to be output to a server of emergency service provider during a vehicle emergency.
  • the vehicle crash detection modules 305 may include various sensors and modules utilized to determine an emergency situation. Such modules may include impact sensors, cameras, restraint control modules, gyroscopes, accelerometers, air bag sensors, etc.
  • the vehicle crash detection modules may communicate data or information to a wireless connectivity medium 307.
  • the vehicle crash detection modules 305 may trigger various events to occur (e.g. airbag deployment, seatbelt restraint, etc.).
  • the vehicle crash detection modules may communicate information and data to a wireless connectivity medium 307, which may include a vehicle computer system connected or paired with various nomadic devices to connect with the cloud, to identify that an emergency event has occurred.
  • the VCS may communicate information to nomadic devices (e.g. wearable device) that an emergency event has occurred.
  • the VCS may also send data indicative of the emergency to the wearable devices or request the wearable device to send data related to the occupant or user of the wearable device.
  • the wearable device may send information to the VCS or to off-board servers.
  • the wireless connectivity medium 307 may be the wearable device itself, a mobile phone, an embedded telematics module, etc.
  • the wireless connectivity medium 307 may then utilize its communication capability to communicate with the emergency response infrastructure 309.
  • the emergency response infrastructure may include a public-safety answering point (PSAP), emergency medical service (EMS), hospital, fire department, etc.
  • PSAP public-safety answering point
  • EMS emergency medical service
  • Each of the various servers or establishments within an emergency response infrastructure may utilize data communicated from the vehicle, including those from the wearable devices, to assist occupants during a vehicle emergency.
  • Figure 4 illustrates an exemplary flow chart for utilizing wearable device data in the event of a vehicle emergency.
  • a vehicle computer system may be in communication with one or more devices inside of the vehicle, including a mobile phone, tablet, or wearable device.
  • the vehicle computer system may pair with wearable devices of one or more occupants 401.
  • the vehicle may allow one or more occupants of the vehicle to connect their wearable device with the vehicle computer system (VCS).
  • VCS vehicle computer system
  • the VCS may have the ability to pair with multiple wearable devices in order to
  • the system may be able to use some form of a wireless (e.g., radio-frequency, ultrasonic, infrared) sensing system to passively (i.e., without requiring any "pairing" action on the part of the occupant) detect the presence of wearable devices.
  • a wireless sensing system e.g., radio-frequency, ultrasonic, infrared sensing system to passively (i.e., without requiring any "pairing" action on the part of the occupant) detect the presence of wearable devices.
  • the sensing system could scan the vehicle interior to detect wearables.
  • the system could also be programmed to scan the exterior to detect wearables.
  • the VCS may monitor wearable device data constantly while in communication with the wearable devices 403. For example, the VCS may send requests to receive wearable device data constantly or at specific intervals.
  • the wearable device may send various data to the VCS, including location of the user, movement data of the user, body information (e.g. blood pressure, heart rate, blood glucose, etc.), and other data related to the user or wearable device.
  • the constant communication between the VCS and the wearable devices may allow the VCS to associate the wearable device data with a specific time and identify of the vehicle environment at that time. For example, during sudden braking or acceleration of the vehicle, the VCS may retrieve the wearable device data to analyze a change in various data, such as movement of a user or relative location. Such monitoring may be utilized during emergency situations.
  • the VCS may then monitor for an emergency situation at the vehicle 405.
  • the VCS itself may monitor for an emergency, or it may receive a signal or other incoming data to identify an emergency.
  • the VCS may be in communication with a restraint control module (RCM) that monitors crash detection, air-bag deployment, or other emergency situations.
  • RCM restraint control module
  • the VCS may then be in communication with the RCM, or similar vehicle module to receive data indicating an emergency situation. If no emergency situation occurs, the VCS may continue to monitor data and operate as normal.
  • the VCS may react appropriately to activate emergency services, such as FORD SYNC's 911 ASSIST, or other type of services.
  • the wearable device data may be monitored and aggregated to determine changes with respect to the wearable device data before and after an emergency. While a typical vehicle emergency may be a vehicle crash or accident, other situations may arise to be an emergency, such as sudden acceleration or deceleration, or sudden swerving or braking.
  • the VCS may receive the wearable device data from the various wearable devices in the vehicle 407.
  • the VCS may also be in communication with other modules in the vehicle to retrieve their data.
  • the VCS may also communicate with nomadic devices, such as mobile phones or tablets, to retrieve data or utilize functionality during a vehicle emergency.
  • the nomadic devices may communicate solely with the VCS or through the wearable device, which may be paired with the nomadic device.
  • the VCS may retrieve different types of wearable device data, such as occupant-data, location data, movement data, gait data, health data (blood sugar, pulse, hear rate, etc.), user data (e.g. identify or other information about the user), and other data.
  • Different types of wearable devices may send or utilize different types of data to the VCS.
  • the VCS may then aggregate data from each individual wearable device 409.
  • a number of wearable devices that collect and send different data to the VCS may be able to utilize each of its own data collectively in a unique, novel fashion.
  • the VCS may then utilize the aggregated data from each of the wearable devices 409.
  • the aggregated data may include all the various data collected by the VCS, including wearable device data and occupant data, vehicle data from other vehicle controllers, vehicle environment data (e.g. data to determine the vehicle' s surrounding environment) from various sensors, and dynamic data from off-board servers (e.g. weather data, traffic data, local event data, etc.).
  • the aggregated data may be utilized in conjunction with data collected from the wearable device data to assist during various vehicle events or conditions.
  • the aggregated data may then be utilized by the VCS 411 for various conditions.
  • the VCS 411 may then be utilized by the VCS 411 for various conditions.
  • VCS may utilize wearable device data in a number of different fashions.
  • the occupant-wearable matrix may be utilized to assign a value to the vehicle, as a whole. Based on the value assigned to the vehicle by the occupant-wearable matrix, various conditions or estimates may be determined by the vehicle or an off -board server. The value may be utilized to determine the minimum number of occupants; the possible age-range of occupants; the locations of occupants; and any measure of any gradual or sudden occupant movement. Coordinating the occupant to wearable devices may be utilized for these estimates. Of course, additional data may be utilized to improve accuracy or identify further attributes of the vehicle.
  • the VCS may also be utilized to output the data collected from the wearable device
  • the VCS may output the data to an off -board server for further processing. Additionally, and as explained above, the VCS may output the data to an emergency service provider to facilitate a driver or occupant in a vehicle emergency.
  • the VCS may also continuously send data to the emergency service provider in real-time. For example, the VCS may collect real-time wearable device data and determine if movement is occurring at the vehicle with a user.
  • the VCS or off- board server may categorize the movement as normal or severe. Additionally, if there is a lack of movement, the vehicle may categorize lack of movement to identify that a user may be unconscious.
  • the vehicle or cloud may send such categorization of the movement to the emergency responder for the appropriate response.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Chemical & Material Sciences (AREA)
  • Combustion & Propulsion (AREA)
  • Transportation (AREA)
  • Mechanical Engineering (AREA)
  • Alarm Systems (AREA)

Abstract

L'invention concerne un système informatique de véhicule comprenant un émetteur-récepteur sans fil configuré pour recevoir des données d'un dispositif pouvant être porté à partir d'un ou de plusieurs dispositifs pouvant être portés correspondant chacun à un occupant. Le système informatique de véhicule comprend en outre un processeur configuré pour délivrer à un serveur externe un paramètre indiquant la gravité d'un accident de véhicule en réponse aux données du dispositif pouvant être porté indiquant des changements entre avant l'accident et après l'accident en ce qui concerne les emplacements relatifs des occupants.
PCT/US2016/022582 2016-03-16 2016-03-16 Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés WO2017160285A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2016/022582 WO2017160285A1 (fr) 2016-03-16 2016-03-16 Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/022582 WO2017160285A1 (fr) 2016-03-16 2016-03-16 Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés

Publications (1)

Publication Number Publication Date
WO2017160285A1 true WO2017160285A1 (fr) 2017-09-21

Family

ID=59850415

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/022582 WO2017160285A1 (fr) 2016-03-16 2016-03-16 Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés

Country Status (1)

Country Link
WO (1) WO2017160285A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2619739A (en) * 2022-06-15 2023-12-20 Continental Automotive Tech Gmbh Method and system for determining and providing information about occupants of a vehicle
WO2024158491A1 (fr) * 2023-01-24 2024-08-02 Apple Inc. Communications avec services externes

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140024334A1 (en) * 2007-06-27 2014-01-23 Ford Global Technologies, Llc Method and System for Emergency Notification
US20150116078A1 (en) * 2013-10-24 2015-04-30 GM Global Technology Operations LLC Enhanced vehicle key fob
US20150124944A1 (en) * 2013-11-01 2015-05-07 Plantronics, Inc. Interactive Device Registration, Setup and Use
US20150342542A1 (en) * 2014-06-03 2015-12-03 Lg Electronics Inc. Handling Vehicle Accidents Using A Mobile Terminal

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140024334A1 (en) * 2007-06-27 2014-01-23 Ford Global Technologies, Llc Method and System for Emergency Notification
US20150116078A1 (en) * 2013-10-24 2015-04-30 GM Global Technology Operations LLC Enhanced vehicle key fob
US20150124944A1 (en) * 2013-11-01 2015-05-07 Plantronics, Inc. Interactive Device Registration, Setup and Use
US20150342542A1 (en) * 2014-06-03 2015-12-03 Lg Electronics Inc. Handling Vehicle Accidents Using A Mobile Terminal

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2619739A (en) * 2022-06-15 2023-12-20 Continental Automotive Tech Gmbh Method and system for determining and providing information about occupants of a vehicle
WO2024158491A1 (fr) * 2023-01-24 2024-08-02 Apple Inc. Communications avec services externes

Similar Documents

Publication Publication Date Title
US10343682B2 (en) Vehicle operation based on activity tracking
US11993269B2 (en) Smart ring system for measuring driver impairment levels and using machine learning techniques to predict high risk driving behavior
CN105635244B (zh) 用于生物特征数据收集和分发的方法和设备
US10040423B2 (en) Vehicle with wearable for identifying one or more vehicle occupants
US20150365979A1 (en) Methods And Apparatus For Intelligent Connection Control And Emergency Assisting With mobile devices
US9767373B2 (en) Head-mounted display head pose and activity estimation
CN105100192B (zh) 用于启动应用的方法和系统
US20160063773A1 (en) Apparatus and System for Generating Emergency Vehicle Record Data
US9096234B2 (en) Method and system for in-vehicle function control
CN105101115B (zh) 用于启动应用的方法和系统
US20150279125A1 (en) Variable reporting rate telematics
US10121291B2 (en) Method and apparatus for visual accident detail reporting
US20180026669A1 (en) Phone docking station for enhanced driving safety
US20170365106A1 (en) Method and apparatus for automatic transmission of medical data
JP6530562B2 (ja) 車載携帯機器による注意散漫の制限
US20140207309A1 (en) Vehicle driver determination and behavior monitoring
US10632949B2 (en) Method of assistance to at least one occupant of an accident affected vehicle and dedicated assistance system
US20170339529A1 (en) Method and apparatus for vehicle occupant location detection
AU2016200015A1 (en) Methods and Systems for Configuration of a Vehicle Feature
US20240278790A1 (en) Method of assisting a driver if a passenger encounters a health issue
WO2017160285A1 (fr) Détection d'occupants dans un véhicule après une situation d'urgence en utilisant des dispositifs pouvant être portés
US10547730B2 (en) Method and apparatus for vehicular emergency call
KR101825134B1 (ko) 감정측정 디바이스를 활용한 드론 방범 시스템
US12077193B1 (en) Smart ring system for monitoring sleep patterns and using machine learning techniques to predict high risk driving behavior
EP4142317A1 (fr) Système d'urgence pour véhicule et procédé de fourniture d'informations d'urgence

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16894744

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16894744

Country of ref document: EP

Kind code of ref document: A1