US20230116116A1 - Roadside and emergency assistance system - Google Patents
Roadside and emergency assistance system Download PDFInfo
- Publication number
- US20230116116A1 US20230116116A1 US17/845,023 US202217845023A US2023116116A1 US 20230116116 A1 US20230116116 A1 US 20230116116A1 US 202217845023 A US202217845023 A US 202217845023A US 2023116116 A1 US2023116116 A1 US 2023116116A1
- Authority
- US
- United States
- Prior art keywords
- vehicle
- roadside assistance
- vehicle unit
- server
- assistance request
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000004891 communication Methods 0.000 claims abstract description 21
- 238000000034 method Methods 0.000 description 9
- 230000001133 acceleration Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000012790 confirmation Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000004807 localization Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 101001093748 Homo sapiens Phosphatidylinositol N-acetylglucosaminyltransferase subunit P Proteins 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
- H04M11/04—Telephonic communication systems specially adapted for combination with other electrical systems with alarm systems, e.g. fire, police or burglar alarm systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/303—Terminal profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/5116—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing for emergency applications
-
- 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/48—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for in-vehicle communication
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/50—Connection management for emergency connections
Definitions
- This invention relates to a system and method for providing roadside and emergency assistance to a vehicle.
- Some current systems provide emergency and roadside assistance through in-vehicle systems.
- these systems have several weaknesses. For one, they utilize cell phone network connectivity only, which means that assistance will be unavailable where cell coverage is not available.
- the present invention provides a method and system for providing roadside and emergency assistance to a vehicle.
- the system includes a vehicle unit with several connectivity options.
- a user interface unit permits a user to request assistance and communicate with an emergency dispatcher and/or service provider.
- a server receives requests for assistance from the vehicle unit and relays information between the vehicle unit and a dispatcher or service provider to provide communication between the driver of the vehicle and the dispatcher or service provider. Alternatively, such as in an emergency (e.g. crash) situation, the server directly requests assistance to be sent to the vehicle.
- FIG. 1 is a schematic view of the roadside and emergency assistance system of the present invention.
- FIG. 1 a schematic representation of the system 10 is shown and includes a vehicle unit 14 installed in a vehicle 12 .
- vehicle 12 A would similarly contain vehicle units similar to vehicle unit 14 .
- the vehicle unit 14 is attached and connected to receive power from a vehicle power source. Power from the vehicle 12 can originate from a non-switched fuse box, OBD-II port 55 , or other powered connection within the vehicle 12 as known.
- the vehicle unit 14 includes a computer processor 15 and computer storage 18 (such as memory, hard drive, RAM, ROM, or any kind of electronic, optical, magnetic or other computer readable medium) and is suitably programmed to perform the functions described herein.
- Each vehicle unit 14 includes at least one wireless communication circuit 17 , such as a Bluetooth communication circuit, GSM, GPRS, CDMA, WiFi, WiMax, cell phone, satellite phone or other wireless communication protocol, and more preferably, more than one protocol. If the wireless communication circuit 17 includes Bluetooth (or equivalent), it can communicate with a wireless device 19 , which is preferably a cell phone, smart phone, smart PDA or other portable wireless communication device 19 in order to communicate with cell towers 21 . In this manner, the vehicle units 14 are able to exchange information with a Service Request Classification and Vehicle Localization (SRCVL) server 22 and with other vehicles 12 A.
- the SRCVL server 22 includes at least one computer processor and computer storage.
- An in-vehicle camera 26 may be provided in the system and connected to the vehicle unit 14 .
- the camera 26 may be mounted to the headliner of the vehicle 12 so that it captures images (still and or video images) of the interior and exterior of the vehicle 12 (such as by using a fish-eye lens).
- the system 10 further includes a user interface device 30 , which may be portable (wireless) or may be connected to the vehicle unit 14 .
- the user interface device 30 may include a display 32 and user input devices such as buttons 34 (such as on a keyboard), or alternatively, the display 32 could be a touch-screen.
- the user interface device 30 includes a processor 36 , storage 38 (both as previously described), and a communication interface 39 , such as a wireless communication interface (e.g. Bluetooth, RF, 802.11, wi-fi, or any other protocol).
- the user interface device 30 may also include a microphone 33 and speaker 35 .
- the SRCVL server 22 is in communication (via a wide area network, such as the Internet) with a Telematics Service Processing (“TSP”) server 50 (again, with at least one processor and storage and suitably programmed to perform the functions described herein).
- TSP Telematics Service Processing
- the TSP server 50 is in communication with many dispatcher/service providers 52 (assistance providers) via a WAN and telephone.
- the dispatcher/service providers 52 include local emergency assistance providers, such as service dispatchers, 911 operators, fire and police dispatchers, etc.
- the dispatcher/service providers 52 also include roadside assistance providers, such as tow-truck operators.
- the TSP server 50 includes a database 54 of the dispatcher/service providers 52 , including their locations, contact information and types of services provided.
- the vehicle unit 14 includes a configurable database 28 to store mission critical contacts book of telephone numbers and IP addresses of critical dispatch/service providers 52 . This information and more is also stored on the SRCVL 22 .
- the system 10 has the ability to determine the location of the vehicle unit 14 using any of numerous existing techniques (or several).
- the vehicle unit 14 may include a GPS receiver 16 . Location could also be determined from a global navigation satellite system, GSM localization, DSRC, WiMAX, etc.
- the server 22 can determine the positions of the devices 19 using triangulation from cell towers 21 . Using cell tower triangulation, the location of the device 19 is determined at the servers 22 and can remain at the server 22 or can also be transmitted to the vehicle unit 14 .
- the vehicle unit 14 can include a three-axis accelerometer 46 for determining an acceleration or deceleration of the vehicle 12 , from which some speed and position information can be determined.
- the accelerometer 46 can also determine that a collision has occurred and can determine driving habits of the driver (e.g. hard accelerations or decelerations).
- the vehicle unit 14 also receives speed and heading information from the On Board Diagnostics port OBD 55 . Speed and heading can be used to determine location of the vehicle unit 14 .
- the location of the vehicle unit 14 (and vehicle 12 ) is determined, the location and the time spent (or distance driven) in certain geographic areas (e.g. zip codes) may be used to determine insurance rates in several ways. Some insurance premiums are based upon miles driven and based upon geographic areas in which the miles are driven. The premiums may also be based upon the driver's driving habits, such as hard accelerations, speed, time of day, day of the week, type of roads, etc.
- the system 10 also provides emergency and/or roadside assistance to the vehicle 12 .
- a service call is initiated by the vehicle 12 (due to crash as determined by the accelerometer 46 , etc) or its operator via the user interface device 30 , or on behalf of another vehicle 12 A (or its operator) in its vicinity, a connection to the SRCVL 22 is attempted using one or more of the connection options provided by communication device 17 .
- the vehicle unit 14 provides automatic detection and failover between the various available connectivity options. If the service request is time critical and a connection was not realized or an acknowledgment is not received within a prescribed time threshold from the SRCVL server 22 , the vehicle unit 14 will attempt to connect directly to the appropriate dispatch/service provider 52 using the information stored in its mission critical contact book in database 28 .
- the vehicle unit 14 determines (or already knows) the current location of the vehicle 12 , vehicle speed, heading, the level of precision of position fix, and current time/date.
- the vehicle unit 14 acquires (or has already acquired) vehicle data and diagnostics information from the vehicle's OBD system 55 .
- the vehicle unit 14 attempts a connection to the SRCVL server 22 as above.
- a roadside assistance message is created (containing the timestamp, various diagnostic data and parameters such as location (and precision of location), speed, heading) and is forwarded to SRCVL server 22 .
- the SRCVL server 22 validates the request and processes it to look up a 10-digit telephone number associated with the vehicle unit 14 .
- the SRCVL server 22 also validates and processes the vehicle geographical location (e.g. convert to street address or location with respect to a landmark) and vehicle travel direction (e.g., on street xy moving east to west).
- the SRCVL server 22 also processes information from the vehicle unit 14 to determine vehicle 12 health condition.
- the SRCVL server 22 creates a Telematic Service request including of a summary of the request, level of urgency, and a classification of the service requested and forwards it to the TSP server 50 .
- the TSP server 50 sends a location response message containing a unique confirmation identifier if it successfully receives the service request.
- the SRCVL server 22 receives and stores the confirmation identifier.
- the TSP server 50 determines the best dispatch/service provider 50 to respond to the request.
- the TSP server 50 connects to the appropriate dispatch/service provider 50 .
- the TSP server 50 provides the dispatch/service provider 50 information such as vehicle location, vehicle IP or Phone Number, requested service type, a summary of requested service including vehicle information, and time when service was requested.
- the dispatch/service provider 50 delivers the requested service to the requesting vehicle 12 by either attending to the vehicle 12 physically, or by contacting the vehicle 12 using phone or internet.
- This communication can be proactive i.e., the dispatch/service provider 50 initiates the call to the vehicle 12 (more specifically to the vehicle unit 14 or to the mobile device 19 ), or reactive, i.e., dispatch/service provider 50 anticipates a call from the vehicle 12 (i.e. the vehicle unit 14 or to the mobile device 19 ).
- the SRCVL server 22 will forward the dispatch/service provider 50 telephone number to the vehicle 12 that initiated the request.
- the vehicle 12 that initiated the request will use the received telephone number to initiate two-way voice communication with the dispatch/service provider 50 .
- the vehicle unit 14 may initiate automatic dialing of the received dispatch/service provider 50 telephone number. If the dialed number is busy the vehicle unit 14 will retry at least one additional time.
- the dispatch/service provider 50 is reached and the roadside assistance request is handled directly between the vehicle 12 operator and the dispatch/service provider 50 .
- the user can speak to a dispatcher via the microphone 33 and speaker 35 on the user interface device 30 . If the vehicle unit 14 is unable to communicate via phone (such as, lack of cell coverage), the dispatch/service provider 50 may dispatch assistance to the vehicle 12 directly based upon the location of the vehicle 12 , to the extent it is known.
- the same connection process is attempted to SRCVL server 22 ; however, in addition to the information transmitted as described above, the urgency of the request is flagged as critical to ensure timely response.
- the vehicle unit 14 also transmits a video capture of ten seconds before the crash, ten seconds after the crash (and including the crash), other crash intensity and type and other crash parameters (such as vehicle speed during the video capture times, accelerometer 46 measurements), number of occupants in the vehicle, and continuous feed of temperature in the vehicle 12 .
- the SRCVL server 22 in this case will contact an emergency response provider (of the dispatch/service providers 52 ) and provide them with all of the information received from the vehicle unit 14 .
- the vehicle unit 14 initiates a connection only if it can do so using its communication circuit 17 .
- the SRCVL server 22 forwards information to maintenance service providers (of the dispatch service providers 52 ), e.g., a car dealership, or SRCVL server 22 will email a maintenance reminder with report summary to vehicle owner/operator. A copy of the report is stored on SRCVL server 22 .
- failures There are a number of points of failure that must be handled. These failures include, lack of GPS connectivity, no GSM network coverage (or the relevant protocol), SRCVL server 22 unavailable, and TSP server 50 unavailable. These failures and how they are to be handled are described below.
- the vehicle unit 14 will initiate a roadside assistance request to SRCVL server 22 with the last known position of the vehicle 12 collected through the GPS receiver 16 . This position will be aged (5 minutes) and if it is detected that the position is reasonably accurate it will be passed to the SRCVL server 22 for processing. If the position has aged passed the state of usability, then the ‘ERS Access Number’ shall be used.
- the vehicle unit 14 will indicate to the user (such as by displaying through an LED display that GSM/CDMA network coverage cannot be obtained via the message “No GSM/CDMA Network Coverage”). In this case an attempt will be made to connect through wifi or wimax if detected in the surrounding. If wifi or wimax is not available an attempt will be made to establish a connection via other cars in the area via Bluetooth or another wireless connection.
- the vehicle unit 14 will dial a HELP number for instances when either the SRCVL server 22 and/or the TSP server 50 are unavailable.
- the vehicle unit 14 may also provide timely, voice-driven notification of upcoming roadside emergencies (as received from the SRCVL server 22 or another server) that are tailored to the location of the vehicle 12 .
- This feature proactively delivers valuable information through the existing infrastructure, and can be used for severe weather conditions, traffic incidents, and other dangers to assist in the avoidance of roadside emergencies.
- server is used broadly, as it is understood that a “server” may include many hardware-independent computers that may even be in different geographic locations. Further, it should be recognized that the SRCVL server 22 and TSP server 50 could be implemented in a single server.
Abstract
A system for providing roadside and emergency assistance to a vehicle includes a vehicle unit with several connectivity options. A user interface unit permits a user to request assistance and communicate with an emergency dispatcher and/or service provider. A server receives requests for assistance from the vehicle unit and relays information between the vehicle unit and a dispatcher or service provider to provide communication between the driver of the vehicle and the dispatcher or service provider. Alternatively, such as in an emergency (e.g. crash) situation, the server directly requests assistance to be sent to the vehicle.
Description
- This application is a continuation of U.S. Non-Provisional patent application Ser. No. 14/991,976 filed on Jan. 10, 2016. U.S. Non-Provisional application Ser. No. 14/991,976 is a continuation of U.S. Pat. No. 9,237,242 issued on Jan. 12, 2016. U.S. Pat. No. 9,237,242 claims priority to U.S. Provisional Application No. 61/037,301, filed Mar. 17, 2008.
- This invention relates to a system and method for providing roadside and emergency assistance to a vehicle.
- Drivers often need roadside assistance with their vehicle, such as when they have a flat tire, the vehicle is stuck in the snow, or is otherwise not functioning. For most drivers, this currently requires the user to call for help with their cell phone. If cell service is unavailable, the driver must walk to get assistance or wait for another passing car to call for assistance.
- Frequently, drivers need emergency assistance, such as in the event of a crash. Often, the drivers and passengers in the vehicle are unable to call for emergency assistance themselves.
- Some current systems provide emergency and roadside assistance through in-vehicle systems. However, these systems have several weaknesses. For one, they utilize cell phone network connectivity only, which means that assistance will be unavailable where cell coverage is not available.
- The present invention provides a method and system for providing roadside and emergency assistance to a vehicle. The system includes a vehicle unit with several connectivity options. A user interface unit permits a user to request assistance and communicate with an emergency dispatcher and/or service provider. A server receives requests for assistance from the vehicle unit and relays information between the vehicle unit and a dispatcher or service provider to provide communication between the driver of the vehicle and the dispatcher or service provider. Alternatively, such as in an emergency (e.g. crash) situation, the server directly requests assistance to be sent to the vehicle.
-
FIG. 1 is a schematic view of the roadside and emergency assistance system of the present invention. - Referring to
FIG. 1 , a schematic representation of thesystem 10 is shown and includes avehicle unit 14 installed in avehicle 12. Other vehicles, such asvehicle 12A, would similarly contain vehicle units similar tovehicle unit 14. Thevehicle unit 14 is attached and connected to receive power from a vehicle power source. Power from thevehicle 12 can originate from a non-switched fuse box, OBD-IIport 55, or other powered connection within thevehicle 12 as known. Thevehicle unit 14 includes acomputer processor 15 and computer storage 18 (such as memory, hard drive, RAM, ROM, or any kind of electronic, optical, magnetic or other computer readable medium) and is suitably programmed to perform the functions described herein. - Each
vehicle unit 14 includes at least onewireless communication circuit 17, such as a Bluetooth communication circuit, GSM, GPRS, CDMA, WiFi, WiMax, cell phone, satellite phone or other wireless communication protocol, and more preferably, more than one protocol. If thewireless communication circuit 17 includes Bluetooth (or equivalent), it can communicate with awireless device 19, which is preferably a cell phone, smart phone, smart PDA or other portablewireless communication device 19 in order to communicate with cell towers 21. In this manner, thevehicle units 14 are able to exchange information with a Service Request Classification and Vehicle Localization (SRCVL)server 22 and withother vehicles 12A. The SRCVLserver 22 includes at least one computer processor and computer storage. - An in-
vehicle camera 26 may be provided in the system and connected to thevehicle unit 14. Thecamera 26 may be mounted to the headliner of thevehicle 12 so that it captures images (still and or video images) of the interior and exterior of the vehicle 12 (such as by using a fish-eye lens). - The
system 10 further includes auser interface device 30, which may be portable (wireless) or may be connected to thevehicle unit 14. Theuser interface device 30 may include adisplay 32 and user input devices such as buttons 34 (such as on a keyboard), or alternatively, thedisplay 32 could be a touch-screen. Theuser interface device 30 includes aprocessor 36, storage 38 (both as previously described), and acommunication interface 39, such as a wireless communication interface (e.g. Bluetooth, RF, 802.11, wi-fi, or any other protocol). Theuser interface device 30 may also include amicrophone 33 andspeaker 35. - The SRCVL
server 22 is in communication (via a wide area network, such as the Internet) with a Telematics Service Processing (“TSP”) server 50 (again, with at least one processor and storage and suitably programmed to perform the functions described herein). TheTSP server 50 is in communication with many dispatcher/service providers 52 (assistance providers) via a WAN and telephone. The dispatcher/service providers 52 include local emergency assistance providers, such as service dispatchers, 911 operators, fire and police dispatchers, etc. The dispatcher/service providers 52 also include roadside assistance providers, such as tow-truck operators. TheTSP server 50 includes adatabase 54 of the dispatcher/service providers 52, including their locations, contact information and types of services provided. - The
vehicle unit 14 includes aconfigurable database 28 to store mission critical contacts book of telephone numbers and IP addresses of critical dispatch/service providers 52. This information and more is also stored on the SRCVL 22. - The
system 10 has the ability to determine the location of thevehicle unit 14 using any of numerous existing techniques (or several). First, thevehicle unit 14 may include aGPS receiver 16. Location could also be determined from a global navigation satellite system, GSM localization, DSRC, WiMAX, etc. Alternatively, or additionally, theserver 22 can determine the positions of thedevices 19 using triangulation from cell towers 21. Using cell tower triangulation, the location of thedevice 19 is determined at theservers 22 and can remain at theserver 22 or can also be transmitted to thevehicle unit 14. Optionally, thevehicle unit 14 can include a three-axis accelerometer 46 for determining an acceleration or deceleration of thevehicle 12, from which some speed and position information can be determined. Theaccelerometer 46 can also determine that a collision has occurred and can determine driving habits of the driver (e.g. hard accelerations or decelerations). Thevehicle unit 14 also receives speed and heading information from the On Board Diagnostics port OBD 55. Speed and heading can be used to determine location of thevehicle unit 14. - However the location of the vehicle unit 14 (and vehicle 12) is determined, the location and the time spent (or distance driven) in certain geographic areas (e.g. zip codes) may be used to determine insurance rates in several ways. Some insurance premiums are based upon miles driven and based upon geographic areas in which the miles are driven. The premiums may also be based upon the driver's driving habits, such as hard accelerations, speed, time of day, day of the week, type of roads, etc.
- The
system 10 also provides emergency and/or roadside assistance to thevehicle 12. When a service call is initiated by the vehicle 12 (due to crash as determined by theaccelerometer 46, etc) or its operator via theuser interface device 30, or on behalf of anothervehicle 12A (or its operator) in its vicinity, a connection to the SRCVL 22 is attempted using one or more of the connection options provided bycommunication device 17. Thevehicle unit 14 provides automatic detection and failover between the various available connectivity options. If the service request is time critical and a connection was not realized or an acknowledgment is not received within a prescribed time threshold from theSRCVL server 22, thevehicle unit 14 will attempt to connect directly to the appropriate dispatch/service provider 52 using the information stored in its mission critical contact book indatabase 28. If a direct connection is not realized, an attempt will be made to establish a connection via anothervehicle 12A in the vicinity, who in turn tries to contact theSVCL 22, the dispatch/service provide 52 or yet another vehicle, and so on, and so on. The process is repeated until a connection is established. - If a roadside assistance request is made by the vehicle operator, the user presses the roadside assistance button on the
user interface device 30. Theuser interface device 30 forwards the request to thevehicle unit 14. Thevehicle unit 14 determines (or already knows) the current location of thevehicle 12, vehicle speed, heading, the level of precision of position fix, and current time/date. Thevehicle unit 14 acquires (or has already acquired) vehicle data and diagnostics information from the vehicle'sOBD system 55. - The
vehicle unit 14 attempts a connection to theSRCVL server 22 as above. A roadside assistance message is created (containing the timestamp, various diagnostic data and parameters such as location (and precision of location), speed, heading) and is forwarded toSRCVL server 22. - The
SRCVL server 22 validates the request and processes it to look up a 10-digit telephone number associated with thevehicle unit 14. TheSRCVL server 22 also validates and processes the vehicle geographical location (e.g. convert to street address or location with respect to a landmark) and vehicle travel direction (e.g., on street xy moving east to west). - The
SRCVL server 22 also processes information from thevehicle unit 14 to determinevehicle 12 health condition. TheSRCVL server 22 creates a Telematic Service request including of a summary of the request, level of urgency, and a classification of the service requested and forwards it to theTSP server 50. TheTSP server 50 sends a location response message containing a unique confirmation identifier if it successfully receives the service request. TheSRCVL server 22 receives and stores the confirmation identifier. - Based on the Telematic Service request, the vehicle location, class and the summary, the
TSP server 50 determines the best dispatch/service provider 50 to respond to the request. TheTSP server 50 connects to the appropriate dispatch/service provider 50. TheTSP server 50 provides the dispatch/service provider 50 information such as vehicle location, vehicle IP or Phone Number, requested service type, a summary of requested service including vehicle information, and time when service was requested. - The dispatch/
service provider 50 delivers the requested service to the requestingvehicle 12 by either attending to thevehicle 12 physically, or by contacting thevehicle 12 using phone or internet. This communication can be proactive i.e., the dispatch/service provider 50 initiates the call to the vehicle 12 (more specifically to thevehicle unit 14 or to the mobile device 19), or reactive, i.e., dispatch/service provider 50 anticipates a call from the vehicle 12 (i.e. thevehicle unit 14 or to the mobile device 19). - If
TSP server 50 manages to determine the dispatch information successfully, theSRCVL server 22 will forward the dispatch/service provider 50 telephone number to thevehicle 12 that initiated the request. Thevehicle 12 that initiated the request will use the received telephone number to initiate two-way voice communication with the dispatch/service provider 50. Thevehicle unit 14 may initiate automatic dialing of the received dispatch/service provider 50 telephone number. If the dialed number is busy thevehicle unit 14 will retry at least one additional time. The dispatch/service provider 50 is reached and the roadside assistance request is handled directly between thevehicle 12 operator and the dispatch/service provider 50. The user can speak to a dispatcher via themicrophone 33 andspeaker 35 on theuser interface device 30. If thevehicle unit 14 is unable to communicate via phone (such as, lack of cell coverage), the dispatch/service provider 50 may dispatch assistance to thevehicle 12 directly based upon the location of thevehicle 12, to the extent it is known. - In the event that the
vehicle unit 14 detects a crash, the same connection process is attempted toSRCVL server 22; however, in addition to the information transmitted as described above, the urgency of the request is flagged as critical to ensure timely response. Thevehicle unit 14 also transmits a video capture of ten seconds before the crash, ten seconds after the crash (and including the crash), other crash intensity and type and other crash parameters (such as vehicle speed during the video capture times,accelerometer 46 measurements), number of occupants in the vehicle, and continuous feed of temperature in thevehicle 12. TheSRCVL server 22 in this case will contact an emergency response provider (of the dispatch/service providers 52) and provide them with all of the information received from thevehicle unit 14. - For a more routine maintenance request, the
vehicle unit 14 initiates a connection only if it can do so using itscommunication circuit 17. TheSRCVL server 22 forwards information to maintenance service providers (of the dispatch service providers 52), e.g., a car dealership, orSRCVL server 22 will email a maintenance reminder with report summary to vehicle owner/operator. A copy of the report is stored onSRCVL server 22. - Failure Handling
- There are a number of points of failure that must be handled. These failures include, lack of GPS connectivity, no GSM network coverage (or the relevant protocol),
SRCVL server 22 unavailable, andTSP server 50 unavailable. These failures and how they are to be handled are described below. - Lack of GPS Connectivity
- If the
vehicle unit 14 is experiencing a lack of GPS connectivity withGPS receiver 16, thevehicle unit 14 will initiate a roadside assistance request toSRCVL server 22 with the last known position of thevehicle 12 collected through theGPS receiver 16. This position will be aged (5 minutes) and if it is detected that the position is reasonably accurate it will be passed to theSRCVL server 22 for processing. If the position has aged passed the state of usability, then the ‘ERS Access Number’ shall be used. - No GSM/CDMA Network Coverage
- The
vehicle unit 14 will indicate to the user (such as by displaying through an LED display that GSM/CDMA network coverage cannot be obtained via the message “No GSM/CDMA Network Coverage”). In this case an attempt will be made to connect through wifi or wimax if detected in the surrounding. If wifi or wimax is not available an attempt will be made to establish a connection via other cars in the area via Bluetooth or another wireless connection. - Servers Unavailable
- The
vehicle unit 14 will dial a HELP number for instances when either theSRCVL server 22 and/or theTSP server 50 are unavailable. - The
vehicle unit 14 may also provide timely, voice-driven notification of upcoming roadside emergencies (as received from theSRCVL server 22 or another server) that are tailored to the location of thevehicle 12. This feature proactively delivers valuable information through the existing infrastructure, and can be used for severe weather conditions, traffic incidents, and other dangers to assist in the avoidance of roadside emergencies. - In this document, the term “server” is used broadly, as it is understood that a “server” may include many hardware-independent computers that may even be in different geographic locations. Further, it should be recognized that the
SRCVL server 22 andTSP server 50 could be implemented in a single server. - In accordance with the provisions of the patent statutes and jurisprudence, exemplary configurations described above are considered to represent a preferred embodiment of the invention. However, it should be noted that the invention can be practiced otherwise than as specifically illustrated and described without departing from its spirit or scope. Alphanumeric identifiers on method steps are for convenient reference in dependent claims and do not signify a required sequence of performance unless otherwise indicated in the claims.
Claims (9)
1. A roadside assistance system comprising:
a vehicle unit installed in a vehicle, the vehicle unit including a processor and at least one wireless communication circuit;
a user interface device including a touch-screen display, a processor, and a communication interface for communicating with the vehicle unit, the user interface device being in communication with the vehicle unit and permitting a user to initiate a roadside assistance request in which the roadside assistance request includes a location of the vehicle, a timestamp, a speed of the vehicle, and a heading of the vehicle, and the roadside assistance request is transmitted to a first remote server, the roadside assistance system being further configured to directly communicate the roadside assistance request to a roadside assistance provider.
2. The system of claim 1 wherein the at least one wireless communication circuit of the vehicle unit communicates the roadside assistance request wirelessly to the first remote server.
3. The system of claim 2 wherein the vehicle unit transmits vehicle diagnostic information from an on-board diagnostics system with the roadside assistance request.
4. The system of claim 3 wherein the at least one communication circuit of the vehicle unit is capable of transmitting the roadside assistance request via a plurality of wireless protocols.
5. The system of claim 4 wherein the vehicle unit automatically transmits the roadside assistance request via a second one of the plurality of protocols if a first one of the plurality of protocols is unavailable.
6. The system of claim 3 wherein the at least one communication circuit of the vehicle unit is capable of transmitting the roadside assistance request via a mobile device.
7. The system of claim 2 wherein the vehicle unit is programmed to automatically communicate with a roadside assistance provider directly if the first remote server is unavailable.
8. The system of claim 7 wherein the roadside assistance provider is a tow truck operator.
9. The system of claim 1 , wherein the location of the vehicle includes a precision of the location.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/845,023 US20230116116A1 (en) | 2008-03-17 | 2022-06-21 | Roadside and emergency assistance system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US3730108P | 2008-03-17 | 2008-03-17 | |
US12/405,723 US9237242B2 (en) | 2008-03-17 | 2009-03-17 | Roadside and emergency assistance system |
US14/991,976 US11399101B2 (en) | 2008-03-17 | 2016-01-10 | Roadside and emergency assistance system |
US17/845,023 US20230116116A1 (en) | 2008-03-17 | 2022-06-21 | Roadside and emergency assistance system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/991,976 Continuation US11399101B2 (en) | 2008-03-17 | 2016-01-10 | Roadside and emergency assistance system |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230116116A1 true US20230116116A1 (en) | 2023-04-13 |
Family
ID=41063569
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/405,723 Active 2033-07-15 US9237242B2 (en) | 2008-03-17 | 2009-03-17 | Roadside and emergency assistance system |
US14/991,976 Active US11399101B2 (en) | 2008-03-17 | 2016-01-10 | Roadside and emergency assistance system |
US17/845,023 Pending US20230116116A1 (en) | 2008-03-17 | 2022-06-21 | Roadside and emergency assistance system |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/405,723 Active 2033-07-15 US9237242B2 (en) | 2008-03-17 | 2009-03-17 | Roadside and emergency assistance system |
US14/991,976 Active US11399101B2 (en) | 2008-03-17 | 2016-01-10 | Roadside and emergency assistance system |
Country Status (4)
Country | Link |
---|---|
US (3) | US9237242B2 (en) |
EP (1) | EP2266091A4 (en) |
CA (1) | CA2718591A1 (en) |
WO (1) | WO2009114940A1 (en) |
Families Citing this family (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8583320B2 (en) * | 2009-06-26 | 2013-11-12 | Esurance Insurance Services, Inc. | Apparatus and method for automated vehicle roadside assistance |
US9070243B1 (en) | 2009-08-19 | 2015-06-30 | Allstate Insurance Company | Assistance on the go |
US9384491B1 (en) | 2009-08-19 | 2016-07-05 | Allstate Insurance Company | Roadside assistance |
US10453011B1 (en) | 2009-08-19 | 2019-10-22 | Allstate Insurance Company | Roadside assistance |
US9412130B2 (en) | 2009-08-19 | 2016-08-09 | Allstate Insurance Company | Assistance on the go |
US9659301B1 (en) | 2009-08-19 | 2017-05-23 | Allstate Insurance Company | Roadside assistance |
US8805707B2 (en) | 2009-12-31 | 2014-08-12 | Hartford Fire Insurance Company | Systems and methods for providing a safety score associated with a user location |
US9558520B2 (en) * | 2009-12-31 | 2017-01-31 | Hartford Fire Insurance Company | System and method for geocoded insurance processing using mobile devices |
US20150197154A1 (en) * | 2010-12-24 | 2015-07-16 | Martin Kelly Jones | Selection of battery remediation type and/or battery remediation station based upon available time period at location |
US20150191095A1 (en) * | 2010-12-24 | 2015-07-09 | Martin Kelly Jones | Authentication Methods for Battery Remediation in Connection with Electric Powered Mobile Thing (EPMT) |
CA2760342C (en) | 2011-01-26 | 2018-07-24 | The Goodyear Tire & Rubber Company | Management of roadside service requests |
US10284652B2 (en) * | 2011-07-14 | 2019-05-07 | Visteon Globaltechnologies, Inc. | Systems and methods for providing network-based content to an in-vehicle telematics system |
US8756641B2 (en) | 2011-07-28 | 2014-06-17 | At&T Intellectual Property I, L.P. | Method and apparatus for generating media content |
US8634597B2 (en) | 2011-08-01 | 2014-01-21 | At&T Intellectual Property I, Lp | Method and apparatus for managing personal content |
US9799061B2 (en) | 2011-08-11 | 2017-10-24 | At&T Intellectual Property I, L.P. | Method and apparatus for managing advertisement content and personal content |
WO2013097195A1 (en) * | 2011-12-30 | 2013-07-04 | 华为技术有限公司 | Method, device and system for help-seeking based on location service |
US9055409B2 (en) | 2012-02-27 | 2015-06-09 | Ford Global Technologies, Llc | Method and apparatus for roadside assistance facilitation |
US10083548B2 (en) * | 2012-09-07 | 2018-09-25 | Cellco Partnership | Appliance diagnostic information via a wireless communication link |
US9344869B2 (en) * | 2013-02-12 | 2016-05-17 | Motorola Solutions, Inc. | Method and apparatus for enhanced navigation in a dispatch communication system |
US9392100B2 (en) | 2013-06-26 | 2016-07-12 | Raed H. AlHazme | Emergency assistance requesting device |
US9633561B2 (en) | 2013-07-12 | 2017-04-25 | Ford Global Technologies, Llc | On-vehicle system providing roadside assistance |
DE102013224279A1 (en) | 2013-11-27 | 2015-05-28 | Bayerische Motoren Werke Aktiengesellschaft | Method and system for providing an assistance suggestion to a user of a motor vehicle |
JP5828882B2 (en) * | 2013-12-27 | 2015-12-09 | 株式会社プレステージインターナショナル | Business request system, business request server, and business request program |
US10235884B2 (en) * | 2014-01-28 | 2019-03-19 | The Curators Of The University Of Missouri | Wireless beacon collision warning system |
US9277385B2 (en) * | 2014-03-13 | 2016-03-01 | Denso International America, Inc. | 911 assist by wireless charger with NFC in the vehicle |
US10832327B1 (en) * | 2014-07-21 | 2020-11-10 | State Farm Mutual Automobile Insurance Company | Methods of providing insurance savings based upon telematics and driving behavior identification |
US9282430B1 (en) | 2014-07-30 | 2016-03-08 | Allstate Insurance Company | Roadside assistance service provider assignment system |
US11132629B2 (en) | 2014-07-30 | 2021-09-28 | Allstate Insurance Company | Crowdsourced roadside assistance service provider assignment system |
US11216824B1 (en) | 2015-02-26 | 2022-01-04 | Allstate Insurance Company | Role assignment for enhanced roadside assistance |
US10142420B2 (en) * | 2015-08-25 | 2018-11-27 | Ford Global Technologies, Llc | On-board web server telematics systems and methods |
US9615209B2 (en) * | 2015-08-26 | 2017-04-04 | Aman Navani | Systems and methods for facilitating integrated services for providing road-side assistance |
US10194484B2 (en) * | 2015-09-17 | 2019-01-29 | Ford Global Technologies, Llc | Apparatus and method for initiating an emergency call using a personal communication device |
US10101018B2 (en) * | 2015-09-22 | 2018-10-16 | Ford Global Technologies, Llc | Dome light assembly with integral removable lamp unit for use in emergencies |
RU2718414C2 (en) | 2015-10-01 | 2020-04-02 | Шлюмбергер Текнолоджи Б.В. | System and method for controlling access to potentially hazardous equipment |
US20170140580A1 (en) | 2015-11-17 | 2017-05-18 | The Goodyear Tire & Rubber Company | System and method for servicing a damaged vehicle |
US11023833B2 (en) | 2015-12-30 | 2021-06-01 | International Business Machines Corporation | Pro-active fuel and battery refilling for vehicles |
US10556532B2 (en) | 2017-05-15 | 2020-02-11 | Lear Corporation | Seating system having seat with individually controllable thermal units |
US10034631B1 (en) | 2017-05-19 | 2018-07-31 | Lear Corporation | Vehicle seating system with seat occupant vital sign monitoring |
US10363846B2 (en) | 2017-05-30 | 2019-07-30 | Lear Corporation | Vehicle seating system having seat with individually controllable electromagnetic coils |
US10445817B2 (en) | 2017-10-16 | 2019-10-15 | Allstate Insurance Company | Geotagging location data |
US11052223B2 (en) | 2017-12-21 | 2021-07-06 | Lear Corporation | Seat assembly and method |
US10535206B2 (en) | 2018-01-12 | 2020-01-14 | Ford Global Technologies, Llc | Method and apparatus for remotely assisted vehicle assistance |
US11748817B2 (en) | 2018-03-27 | 2023-09-05 | Allstate Insurance Company | Systems and methods for generating an assessment of safety parameters using sensors and sensor data |
US11348170B2 (en) | 2018-03-27 | 2022-05-31 | Allstate Insurance Company | Systems and methods for identifying and transferring digital assets |
JP7128096B2 (en) * | 2018-11-26 | 2022-08-30 | 本田技研工業株式会社 | Video display device |
JP7200645B2 (en) * | 2018-12-11 | 2023-01-10 | トヨタ自動車株式会社 | In-vehicle device, program, and vehicle |
US11059490B1 (en) | 2020-03-17 | 2021-07-13 | Lear Corporation | Seat system |
US11590873B2 (en) | 2020-05-13 | 2023-02-28 | Lear Corporation | Seat assembly |
US11634055B2 (en) | 2020-05-13 | 2023-04-25 | Lear Corporation | Seat assembly |
US11292371B2 (en) | 2020-05-13 | 2022-04-05 | Lear Corporation | Seat assembly |
US11173818B1 (en) | 2020-05-13 | 2021-11-16 | Lear Corporation | Seat assembly |
US11679706B2 (en) | 2020-12-02 | 2023-06-20 | Lear Corporation | Seat assembly |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5797091A (en) * | 1995-03-07 | 1998-08-18 | Xypoint Corporation | Personal communication system and method of use |
US6028537A (en) | 1996-06-14 | 2000-02-22 | Prince Corporation | Vehicle communication and remote control system |
US6707421B1 (en) | 1997-08-19 | 2004-03-16 | Siemens Vdo Automotive Corporation | Driver information system |
DE19921533C1 (en) * | 1999-05-11 | 2001-01-04 | Mannesmann Vdo Ag | Communication system of a motor vehicle |
WO2002000316A1 (en) * | 1999-09-24 | 2002-01-03 | Goldberg Sheldon F | Geographically constrained network services |
WO2001037240A1 (en) * | 1999-11-12 | 2001-05-25 | Matsushita Electric Industrial Co., Ltd. | On-board communication terminal and information service center communicating with on-board communication terminal |
US20040192336A1 (en) * | 2002-11-26 | 2004-09-30 | Walby James Allen | Device and method for establishing a wireless communication link by a wireless communication device having more than one transceiver |
US7962119B2 (en) * | 2003-06-30 | 2011-06-14 | Harman Becker Automotive Systems Gmbh | System for transmitting an emergency call |
US20080090546A1 (en) * | 2006-10-17 | 2008-04-17 | Richard Dickinson | Enhanced E911 network access for a call center using session initiation protocol (SIP) messaging |
WO2005085021A1 (en) | 2004-03-08 | 2005-09-15 | Sekhar Padmanabhan | Vehicle security system using short messaging services / internet |
KR20060014765A (en) * | 2004-08-12 | 2006-02-16 | 주식회사 현대오토넷 | Emergency safety service system and method using telematics system |
WO2006085379A1 (en) * | 2005-02-10 | 2006-08-17 | Fujitsu Limited | Service providing system for providing various kinds of service including mobile body diagnosis, and car a/v used for the system |
JP2006287705A (en) | 2005-04-01 | 2006-10-19 | Matsushita Electric Ind Co Ltd | Communication system, information communication device for vehicle and indoor information processing device |
US7957744B2 (en) * | 2005-05-13 | 2011-06-07 | General Motors Llc | Method and system for delivering telematics services via a handheld communication device |
US20070155360A1 (en) * | 2005-12-30 | 2007-07-05 | Yafan An | Methods, Apparatuses and Systems for the Reporting of Roadway Speed and Incident Data and the Constructing of Speed Map Database |
US20070159354A1 (en) | 2006-01-09 | 2007-07-12 | Outland Research, Llc | Intelligent emergency vehicle alert system and user interface |
US20090214000A1 (en) * | 2006-01-17 | 2009-08-27 | Medical Envelope L.L.C. | System and method for providing medical and contact information during an emergency call |
WO2008033305A2 (en) * | 2006-09-11 | 2008-03-20 | Telecommunication Systems, Inc. | Automatic emergency call notification to pre-designated personal emergency contacts |
US7991381B1 (en) * | 2007-04-18 | 2011-08-02 | Cellco Partnership | Hierarchical telematics emergency call direction |
US8060085B2 (en) * | 2007-06-04 | 2011-11-15 | Pine Valley Investments, Inc. | System and method for communicating location information |
US20090190735A1 (en) * | 2008-01-24 | 2009-07-30 | General Motors Corporation | Method and system for enhancing telematics services |
-
2009
- 2009-03-17 EP EP09721398A patent/EP2266091A4/en not_active Ceased
- 2009-03-17 WO PCT/CA2009/000339 patent/WO2009114940A1/en active Application Filing
- 2009-03-17 US US12/405,723 patent/US9237242B2/en active Active
- 2009-03-17 CA CA2718591A patent/CA2718591A1/en not_active Abandoned
-
2016
- 2016-01-10 US US14/991,976 patent/US11399101B2/en active Active
-
2022
- 2022-06-21 US US17/845,023 patent/US20230116116A1/en active Pending
Also Published As
Publication number | Publication date |
---|---|
CA2718591A1 (en) | 2009-09-24 |
US20090233572A1 (en) | 2009-09-17 |
US9237242B2 (en) | 2016-01-12 |
US20160205526A1 (en) | 2016-07-14 |
EP2266091A1 (en) | 2010-12-29 |
WO2009114940A1 (en) | 2009-09-24 |
US11399101B2 (en) | 2022-07-26 |
EP2266091A4 (en) | 2012-11-21 |
WO2009114940A8 (en) | 2009-12-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230116116A1 (en) | Roadside and emergency assistance system | |
US11708050B2 (en) | Methods of pre-generating insurance claims | |
CN1312004C (en) | Bus, stop and center system with information exchange | |
US20070061155A1 (en) | Universal Vehicle Communication & Management System | |
US9478134B2 (en) | Method of determining an attribute of a parking structure | |
US10854087B2 (en) | Assistance system and method for transferring data regarding an accident or a breakdown of a vehicle | |
CN102568056A (en) | Method of processing vehicle crash data | |
CN102369562B (en) | Voice connection to an infrastructure facility after an event | |
CN102906798A (en) | Methods for providing emergency services to a mobile vehicle | |
CN110276974A (en) | Remote endpoint is got off navigation guide | |
CN103685345A (en) | Vehicular networking system and method based on relay signal transmission | |
Rustamov et al. | Evaluation Safety of Vehicle Motion in The Condition of Visual Impairment | |
CN107871403A (en) | For detecting method and apparatus that are dangerous and sending warning | |
JP2002032897A (en) | Taxi arrangement service method and system therefor | |
US20230125597A1 (en) | Information collection system | |
DE102017221901A1 (en) | System and method for automatic control of emergency vehicles | |
JP2000207685A (en) | Machine on vehicle and vehicle communication system provided with this machine | |
JP2002334397A (en) | System for managing bus arrival | |
JPH1042072A (en) | Emergency notice system | |
WO2005052884A1 (en) | Driver and vehicle status communication system | |
KR101196383B1 (en) | Apparatus and method for recognizing vehicle information in portable terminal | |
JP2009043074A (en) | Communication system | |
JP2014232391A (en) | Distribution server and information distribution system | |
JP2002288078A (en) | Using method of electronic mail | |
FR2899368A1 (en) | Motor vehicle`s information e.g. timestamping information, exchanging system for e.g. driver, has movable radiotelephone transmitter/receiver transferring information from post to vehicle`s memories, where post triggers warning process |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |