Technology for implementing a reverse communication session for automotive devices
Abstract
Systems and methods relate to, inter alia, receiving a set of sensor data from a set of sensors communicatively coupled to the electronic mobile device. The systems and methods may further include determining automatically from the set of sensor data that the collision event occurred during the operation of the automotive device. The systems and methods may further include initiating, in response to determining that the collision event occurred, a reverse communication session between the electronic mobile device and a collision management server. The electronic mobile device, via the initiated reverse communication session, may be configured to receive a first offer from a first service provider and a second offer from a second service provider. The first offer and the second offer are for servicing the automotive device by the first service provider and the second service provider, respectively.
Claims
exact text as granted — not AI-modified1 .- 20 . (canceled)
21 . A computer-implemented method for managing vehicle emergencies, the method comprising:
collecting, at a computing device, sensor data from one or more sensors communicatively coupled to the computing device, the sensor data being indicative of an operation of a vehicle; analyzing, by the computing device, the sensor data to determine that a collision event occurred during the operation of the vehicle; determining, by the computing device, that an emergency service provider is needed to address the collision event; and initiating, by the computing device, a communication session between the computing device and the emergency service provider.
22 . The computer-implemented method of claim 21 , wherein the sensor data include one or more of location data associated with the vehicle, activity data associated with the vehicle, and audio data associated with the vehicle.
23 . The computer-implemented method of claim 22 , further comprising:
transmitting, by the computing device, the location data associated with the vehicle to the emergence service provider.
24 . The computer-implemented method of claim 21 , further comprising:
analyzing, by the computing device, the sensor data to determine that a high impact activity occurred during the operation of the vehicle; and initiating, by the computing device, the communication session between the computing device and the emergency service provider in response to determining that the high impact activity occurred during the operation of the vehicle.
25 . The computer-implemented method of claim 21 , wherein initiating, by the computing device, the communication session between the computing device and the emergency service provider includes prompting for a response from an operator of the vehicle to initiate contact with the emergency service provider.
26 . The computer-implemented method of claim 25 , further comprising initiating contact with the emergency service provider when the response from the operator of the vehicle is received.
27 . The computer-implemented method of claim 21 , further comprising automatically initiating contact with the emergency service provider.
28 . A computing device for managing vehicle emergencies, the computing device comprising:
one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:
collect sensor data from one or more sensors communicatively coupled to the computing device, the sensor data being indicative of an operation of a vehicle;
analyze the sensor data to determine that a collision event occurred during the operation of the vehicle;
determine that an emergency service provider is needed to address the collision event; and
initiate a communication session between the computing device and the emergency service provider.
29 . The computing device of claim 28 , wherein the sensor data include one or more of location data associated with the vehicle, activity data associated with the vehicle, and audio data associated with the vehicle.
30 . The computing device of claim 29 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to: transmit the location data associated with the vehicle to the emergence service provider.
31 . The computing device of claim 28 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to:
analyze the sensor data to determine that a high impact activity occurred during the operation of the vehicle; and initiate the communication session between the computing device and the emergency service provider in response to determining that the high impact activity occurred during the operation of the vehicle.
32 . The computing device of claim 28 , wherein the instructions that cause the one or more processors to initiate the communication session between the computing device and the emergency service provider further comprise instructions that cause the one or more processors to prompt for a response from an operator of the vehicle to initiate contact with the emergency service provider.
33 . The computing device claim 32 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to initiate contact with the emergency service provider when the response from the operator of the vehicle is received.
34 . The computing device of claim 28 , wherein the instructions, when executed by the one or more processors, further cause the one or more processors to automatically initiate contact with the emergency service provider.
35 . A non-transitory computer-readable medium storing instructions for managing vehicle emergencies, the instructions when executed by one or more processors of a computing device, cause the computing device to:
collect sensor data from one or more sensors communicatively coupled to the computing device, the sensor data being indicative of an operation of a vehicle; analyze the sensor data to determine that a collision event occurred during the operation of the vehicle; determine that an emergency service provider is needed to address the collision event; and initiate a communication session between the computing device and the emergency service provider.
36 . The non-transitory computer-readable medium of claim 35 , wherein the sensor data include one or more of location data associated with the vehicle, activity data associated with the vehicle, and audio data associated with the vehicle.
37 . The non-transitory computer-readable medium of claim 36 , wherein the instructions when executed by the one or more processors further cause the computing device to:
transmit the location data associated with the vehicle to the emergence service provider.
38 . The non-transitory computer-readable medium of claim 35 , wherein the instructions when executed by the one or more processors further cause the computing device to:
analyze the sensor data to determine that a high impact activity occurred during the operation of the vehicle; and initiate the communication session between the computing device and the emergency service provider in response to determining that the high impact activity occurred during the operation of the vehicle.
39 . The non-transitory computer-readable medium of claim 35 , wherein the instructions when executed by the one or more processor that cause the computing device to initiate the communication session between the computing device and the emergency service provider further cause the computing device to prompt for a response from an operator of the vehicle to initiate contact with the emergency service provider.
40 . The non-transitory computer-readable medium of claim 39 , wherein the instructions when executed by the one or more processors further cause the computing device to automatically initiate contact with the emergency service provider when the response from the operator of the vehicle is received.Join the waitlist — get patent alerts
Track US2022068043A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.