USRE50665E1 - Apparatus and method for automated vehicle roadside assistance - Google Patents
Apparatus and method for automated vehicle roadside assistanceInfo
- Publication number
- USRE50665E1 USRE50665E1 US17/121,195 US202017121195A USRE50665E US RE50665 E1 USRE50665 E1 US RE50665E1 US 202017121195 A US202017121195 A US 202017121195A US RE50665 E USRE50665 E US RE50665E
- Authority
- US
- United States
- Prior art keywords
- vehicle
- location
- request
- stranded
- mobile device
- 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.)
- Active, expires
Links
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
-
- 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/50—Network services
- H04L67/52—Network services specially adapted for the location of the user terminal
Definitions
- This invention relates generally to vehicle roadside assistance. More particularly, this invention relates to a vehicle roadside assistance apparatus and method for automatically provisioning a dispatched vehicle to a stranded vehicle.
- Vehicle roadside assistance is typically used to provide emergency services to vehicle owners experiencing problems that have rendered their vehicles inoperable.
- a vehicle owner is typically required to call a roadside assistance coverage center such as the vehicle owner's insurance company to request roadside assistance.
- the vehicle owner is subsequently directed to a service representative at a vehicle dispatch center to process the request.
- the vehicle dispatch center selects a vehicle to dispatch to the vehicle owner by identifying the nearest vehicles with respect to a given address associated with the vehicle requiring roadside assistance. Thereafter, a dispatched vehicle is directed to the stranded vehicle.
- a computer readable storage medium includes executable instructions to receive from a mobile device a request regarding a stranded vehicle. The request is processed to determine the location of the stranded vehicle. Additional information regarding the stranded vehicle may be retrieved. The location of the stranded vehicle and the additional information may be communicated as a dispatch request. The location of the stranded vehicle relative to a dispatched vehicle is delivered to the mobile device.
- FIG. 1 is an exemplary illustration of the components of an automatic roadside assistance system, in accordance with one embodiment of the present invention.
- FIG. 2 illustrates an exemplary graphical user interface (GUI) for receiving on a mobile device a request regarding a stranded vehicle, in accordance with one embodiment of the present invention.
- GUI graphical user interface
- FIG. 3 illustrates an exemplary graphical user interface (GUI) for making a request on a mobile device to receive location updates regarding a dispatched vehicle, in accordance with one embodiment of the present invention.
- GUI graphical user interface
- FIG. 4 illustrates an exemplary graphical user interface (GUI) for displaying details of a dispatch request on the mobile device, in accordance with one embodiment of the present invention.
- GUI graphical user interface
- FIG. 5 illustrates an exemplary sequence of operations performed by the components of the automatic roadside assistance system shown in FIG. 1 , in accordance with one embodiment of the present invention.
- FIG. 1 is an exemplary illustration of the components of an automatic roadside assistance system 100 configured in accordance with one embodiment of the present invention.
- the system 100 includes a mobile device 102 connected to a server computer 104 and a remote computer 106 via a communication channel 118 , which may be any wired or wireless communication channel.
- the mobile device 102 includes standard components, such as a central processing unit 108 , input/output devices 109 and a network connection circuit 110 , which are linked by a bus 112 .
- the network connection circuit 110 provides connectivity to the communication channel 118 , thereby allowing the mobile device 102 to operate in a networked environment.
- the mobile device 102 may include, but is not limited to, a cellular phone, a handheld computer, a personal digital assistant or a smart phone.
- the input/output devices 109 may include a keyboard and/or display screen that displays one or more graphical user interfaces for providing a user with access to various system objects and for conveying information to the user.
- a mobile web application 116 is stored in a memory 114 , which is connected to the bus 112 .
- the mobile web application 116 includes executable instructions to receive a request regarding a stranded vehicle from the mobile device 102 .
- the server computer 104 includes standard components, such as a network connection circuit 120 , input/output devices 121 and a central processing unit 122 , which are linked by a bus 124 .
- the server computer 104 is configured to provide roadside assistance services.
- the server computer 104 includes a web service module 126 stored in a memory 125 , which is connected to the bus 124 .
- the web service module 126 includes executable instructions to process the request from the mobile web application 116 and determine the location of the stranded vehicle.
- the server computer 104 also includes a dispatch request delivery module 128 and a dispatch request display module 130 .
- the dispatch request delivery module 128 includes executable instructions to deliver a dispatch request to the remote computer 106 .
- the dispatch request display module 130 includes executable instructions to route a graphical map of the location of the stranded vehicle relative to a dispatched vehicle for display on the mobile device 102 .
- the remote computer 106 also includes standard components, such as a network connection circuit 132 , input/output devices 134 and a central processing unit 136 , which are linked via a bus 138 .
- the remote computer 106 includes a dispatch request processing module 142 stored in a memory 140 , which is connected to the bus 138 .
- the dispatch request processing module 142 includes executable instructions to process the dispatch request from the dispatch request delivery module 128 .
- a graphical map of the location of the stranded vehicle relative to the dispatched vehicle is delivered to the server computer 104 .
- executable modules stored in memory units 114 , 125 and 140 are exemplary. Additional modules, such as an operating system module or GUI module may also be included. It should be appreciated that the functions of the modules may be combined. In addition, the functions of the modules may be distributed across the network 100 in any number of ways. The operations performed by the executable modules in memory units 114 , 125 and 140 are discussed in greater detail below.
- a request regarding a stranded vehicle is received on the mobile device 102 .
- the mobile web application 116 in the mobile device 102 includes executable instructions to receive the request.
- the mobile web application 116 may include, for example, a Rich Internet Application (RIA) utilizing Silverlight or Active X configured to receive the request via a graphical user interface provided by the mobile device 102 .
- RIA Rich Internet Application
- the web service module 126 includes executable instructions to receive the request from the mobile web application 116 .
- the web service module 126 includes executable instructions to communicate the request to a mobile device location service 150 , such as AT&T or Sprint, associated with the mobile device 102 to determine the location of the stranded vehicle.
- the web service module 126 includes executable instructions to display the location as a set of GPS coordinates on the display screen of the mobile device 102 .
- the web service module 126 also includes executable instructions to pass the set of GPS coordinates as input parameters to a mobile location mapping service 152 .
- the mobile location mapping service 152 may include, for example, a mapping service such as Microsoft's Virtual EarthTM.
- the web service module 126 further includes executable instructions to receive a graphical map of the location of the stranded vehicle from the mobile location mapping service 152 and route the graphical map for display on the display screen of the mobile device 102 .
- FIG. 2 illustrates an exemplary graphical user interface (GUI) for receiving a request regarding a stranded vehicle on the mobile device 102 , in accordance with one embodiment of the present invention.
- GUI graphical user interface
- a user requests roadside assistance by activating a URL, http://109.168.8.42/esurancemobile.com and selecting an option, “Request a Tow” 160 on the display screen of the mobile device 102 .
- the location of the stranded vehicle is displayed as a set of Global Positioning System (GPS) coordinates on the mobile device 102 .
- GPS Global Positioning System
- the user may acknowledge the accuracy of the location displayed on the mobile device 102 by selecting a radio button choice 162 on the display screen of the mobile device 102 .
- GPS Global Positioning System
- the web service module 126 includes executable instructions to receive additional information regarding the stranded vehicle from the mobile web application 116 .
- the additional information may be displayed as a plurality of questions related to the stranded vehicle on the display screen of the mobile device 102 .
- the additional information may include, for example, the current status of the stranded vehicle, the current coverage limits on the vehicle and details regarding the user's vehicle insurance policy.
- the web service module 126 may include executable instructions to obtain the additional information regarding the current coverage limits on the vehicle and the user's vehicle insurance policy directly from an Insurance Policy Database 156 connected to the server computer 104 .
- the dispatch request delivery module 128 includes executable instructions to receive the location of the stranded vehicle and the additional information from the web service module 126 and deliver the location and the additional information as a dispatch request to the remote computer 106 .
- the dispatch request delivery module 128 includes executable instructions to deliver the dispatch request via a dispatch request application programming interface (API) call to the remote computer 106 .
- API application programming interface
- the dispatch request processing module 142 in the remote computer 106 includes executable instructions to receive the dispatch request from the server computer 104 and communicate the dispatch request to a vehicle dispatch center 158 via the dispatch request API.
- the dispatch request is received by an appropriate vehicle provider in the vehicle dispatch center 158 .
- the dispatch request processing module 142 further includes executable instructions to receive a dispatch request result from the vehicle dispatch center 158 , via the dispatch request API.
- the dispatch request result may include information regarding a dispatched vehicle provisioned for the user, such as the location of the dispatched vehicle, the estimated time of arrival (ETA) of the dispatched vehicle, etc.
- the dispatch request processing module 142 further includes executable instructions to generate a graphical map of the location of the stranded vehicle relative to the dispatched vehicle. The graphical map may be delivered to the dispatch request display module 130 in the server computer 104 .
- the dispatch request display module 130 includes executable instructions to route the graphical map of the location of the stranded vehicle relative to the dispatched vehicle for display on the mobile device 102 .
- the mobile web application 116 in the mobile device 102 includes executable instructions to periodically poll the server computer 104 to get real-time location information updates associated with the dispatched vehicle relative to the stranded vehicle. Alternately, the server computer 104 can periodically push this information to the mobile device 102 .
- the dispatch request display module 130 further includes executable instructions to display an updated graphical map of the location updates on the mobile device 102 .
- the dispatch request display module 130 includes executable instructions to display real-time location updates associated with the dispatched vehicle relative to the stranded vehicle via short message service (SMS) or email messages on the mobile device 102 .
- SMS short message service
- FIG. 3 illustrates an exemplary graphical user interface (GUI) for making a request to receive location updates regarding a dispatched vehicle on the mobile device 102 , in accordance with one embodiment of the present invention.
- GUI graphical user interface
- the user selects a type of contact method, “Text message”, 164 and enters a contact number in a data field 166 .
- submit button 168 Upon selecting the submit button 168 , a graphical user interface as illustrated in FIG. 4 is displayed to the user.
- a dispatch request confirmation 170 including details of the dispatch request may be displayed on the display screen of the mobile device 102 .
- FIG. 5 illustrates an exemplary sequence of operations performed by the components of the automatic roadside assistance system shown in FIG. 1 .
- a request regarding a stranded vehicle is received.
- the request is processed to determine the location of the stranded vehicle.
- a check is performed to determine if the location of the stranded vehicle can be resolved.
- the web service module 126 includes executable instructions to determine if the location of the stranded vehicle can be resolved. If the location cannot be resolved, then a check 186 is performed to determine if the location of the stranded vehicle can be directly obtained from the user.
- the web service module 126 includes executable instructions to determine if the location can be obtained from the user via the mobile web application 116 .
- a GUI may be presented to the user to enter a physical address.
- a user may be presented with a map of the general vicinity and be provided with controls that allows the user to specify a particular location on the map. If the location of the stranded vehicle has been resolved and/or the location of the stranded vehicle has been directly obtained from the user, execution passes to operation 188 to display a graphical map of the location of the stranded vehicle.
- the information may be provided via the mobile web application 116 to the user by executable instructions in the web service module 126 .
- the web service module 126 may also include executable instructions to determine if the graphical map of the location displayed to the user (in operation 188 ) is accurate. If the graphical map of the location is not accurate, executable instructions in the web service module 126 determine if the accurate location of the stranded vehicle can be directly obtained from the user. If the accurate location cannot be directly obtained from the user, then executable instructions in the web service module 126 provide the user with information to directly contact a service representative for provisioning a vehicle to the user.
- the dispatch request processing module 142 includes executable instructions to determine if a vehicle can be successfully provisioned. For example, following the dispatch request API call, it may be determined that the customer's coverage level is insufficient to cover the cost of dispatching a vehicle or that a dispatched vehicle cannot be provisioned within an acceptable time period.
- the disclosed embodiments enable the provisioning of a vehicle programmatically via software modules that integrate the functionality provided by a vehicle dispatch center with the services provided by a vehicle roadside assistance center.
- the communication and processing of dispatch requests programmatically via the dispatch request API enables the automatic provisioning of a vehicle to the user. Accordingly, information regarding a provisioned vehicle is automatically displayed on the user's mobile device, without the user having to contact a service representative at a vehicle dispatch center to obtain the information. This results in increased cost savings to the user.
- the programmatic display of location updates of a dispatched vehicle relative to a stranded vehicle on the mobile device via the software modules enables the user to view the status of a request in real-time on the mobile device, thereby creating enhanced user experience and satisfaction.
- An embodiment of the present invention relates to a computer storage product with a computer-readable medium having computer code thereon for performing various computer-implemented operations.
- the media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts.
- Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs, DVDs and holographic devices; magneto-optical media; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAM devices.
- ASICs application-specific integrated circuits
- PLDs programmable logic devices
- Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter.
- machine code such as produced by a compiler
- files containing higher-level code that are executed by a computer using an interpreter.
- an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools.
- Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions.
Landscapes
- Engineering & Computer Science (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Traffic Control Systems (AREA)
Abstract
A computer readable storage medium includes executable instructions to receive from a mobile device a request regarding a stranded vehicle. The request is processed to determine the location of the stranded vehicle. Additional information regarding the stranded vehicle may be retrieved. The location of the stranded vehicle and the additional information may be communicated as a dispatch request. The location of the stranded vehicle relative to a dispatched vehicle is delivered to the mobile device.
Description
This application is a continuation reissue of Reissue application Ser. No. 14/940,002 filed on Nov. 12, 2015, which is an application for reissue of U.S. Pat. No. 8,583,320 issued on Nov. 12, 2013 from U.S. patent application Ser. No. 12/493,103 filed on Jun. 26, 2009. This application is also an application for reissue of U.S. Pat. No. 8,583,320 issued on Nov. 12, 2013 from U.S. patent application Ser. No. 12/493,103 filed on Jun. 26, 2009. The entire contents of these applications are incorporated by reference herein in their entirety.
This invention relates generally to vehicle roadside assistance. More particularly, this invention relates to a vehicle roadside assistance apparatus and method for automatically provisioning a dispatched vehicle to a stranded vehicle.
Vehicle roadside assistance is typically used to provide emergency services to vehicle owners experiencing problems that have rendered their vehicles inoperable. In the case of a vehicle breakdown or an emergency, a vehicle owner is typically required to call a roadside assistance coverage center such as the vehicle owner's insurance company to request roadside assistance. The vehicle owner is subsequently directed to a service representative at a vehicle dispatch center to process the request. Upon receiving the request, the vehicle dispatch center selects a vehicle to dispatch to the vehicle owner by identifying the nearest vehicles with respect to a given address associated with the vehicle requiring roadside assistance. Thereafter, a dispatched vehicle is directed to the stranded vehicle.
With the widespread use of mobile devices, vehicle owners are able to conveniently place requests for roadside assistance from their vehicle. It would be desirable to develop a technique by which roadside assistance can be automatically procured by the vehicle owner via the mobile device. It would also be desirable to develop a technique by which a vehicle can be automatically provisioned to the vehicle owner using key inputs at a mobile device.
A computer readable storage medium includes executable instructions to receive from a mobile device a request regarding a stranded vehicle. The request is processed to determine the location of the stranded vehicle. Additional information regarding the stranded vehicle may be retrieved. The location of the stranded vehicle and the additional information may be communicated as a dispatch request. The location of the stranded vehicle relative to a dispatched vehicle is delivered to the mobile device.
The invention is more fully appreciated in connection with the following detailed description taken in conjunction with the accompanying drawings, in which:
Like reference numerals refer to corresponding parts throughout the several views of the drawings.
The server computer 104 includes standard components, such as a network connection circuit 120, input/output devices 121 and a central processing unit 122, which are linked by a bus 124. In one embodiment, the server computer 104 is configured to provide roadside assistance services. The server computer 104 includes a web service module 126 stored in a memory 125, which is connected to the bus 124. The web service module 126 includes executable instructions to process the request from the mobile web application 116 and determine the location of the stranded vehicle. The server computer 104 also includes a dispatch request delivery module 128 and a dispatch request display module 130. The dispatch request delivery module 128 includes executable instructions to deliver a dispatch request to the remote computer 106. The dispatch request display module 130 includes executable instructions to route a graphical map of the location of the stranded vehicle relative to a dispatched vehicle for display on the mobile device 102.
The remote computer 106 also includes standard components, such as a network connection circuit 132, input/output devices 134 and a central processing unit 136, which are linked via a bus 138. The remote computer 106 includes a dispatch request processing module 142 stored in a memory 140, which is connected to the bus 138. The dispatch request processing module 142 includes executable instructions to process the dispatch request from the dispatch request delivery module 128. In one embodiment, a graphical map of the location of the stranded vehicle relative to the dispatched vehicle is delivered to the server computer 104.
It should also be noted that the executable modules stored in memory units 114, 125 and 140 are exemplary. Additional modules, such as an operating system module or GUI module may also be included. It should be appreciated that the functions of the modules may be combined. In addition, the functions of the modules may be distributed across the network 100 in any number of ways. The operations performed by the executable modules in memory units 114, 125 and 140 are discussed in greater detail below.
Initially, a request regarding a stranded vehicle is received on the mobile device 102. A variety of techniques may be used to receive the request. In one embodiment, the mobile web application 116 in the mobile device 102 includes executable instructions to receive the request. The mobile web application 116 may include, for example, a Rich Internet Application (RIA) utilizing Silverlight or Active X configured to receive the request via a graphical user interface provided by the mobile device 102.
The web service module 126 includes executable instructions to receive the request from the mobile web application 116. In one embodiment, the web service module 126 includes executable instructions to communicate the request to a mobile device location service 150, such as AT&T or Sprint, associated with the mobile device 102 to determine the location of the stranded vehicle. In a particular embodiment, the web service module 126 includes executable instructions to display the location as a set of GPS coordinates on the display screen of the mobile device 102. In certain embodiments, the web service module 126 also includes executable instructions to pass the set of GPS coordinates as input parameters to a mobile location mapping service 152. The mobile location mapping service 152 may include, for example, a mapping service such as Microsoft's Virtual Earth™. The web service module 126 further includes executable instructions to receive a graphical map of the location of the stranded vehicle from the mobile location mapping service 152 and route the graphical map for display on the display screen of the mobile device 102.
Returning to FIG. 1 , in another embodiment, the web service module 126 includes executable instructions to receive additional information regarding the stranded vehicle from the mobile web application 116. In one embodiment, the additional information may be displayed as a plurality of questions related to the stranded vehicle on the display screen of the mobile device 102. The additional information may include, for example, the current status of the stranded vehicle, the current coverage limits on the vehicle and details regarding the user's vehicle insurance policy. In an alternate embodiment, the web service module 126 may include executable instructions to obtain the additional information regarding the current coverage limits on the vehicle and the user's vehicle insurance policy directly from an Insurance Policy Database 156 connected to the server computer 104.
The dispatch request delivery module 128 includes executable instructions to receive the location of the stranded vehicle and the additional information from the web service module 126 and deliver the location and the additional information as a dispatch request to the remote computer 106. In one embodiment, the dispatch request delivery module 128 includes executable instructions to deliver the dispatch request via a dispatch request application programming interface (API) call to the remote computer 106.
The dispatch request processing module 142 in the remote computer 106 includes executable instructions to receive the dispatch request from the server computer 104 and communicate the dispatch request to a vehicle dispatch center 158 via the dispatch request API. The dispatch request is received by an appropriate vehicle provider in the vehicle dispatch center 158. The dispatch request processing module 142 further includes executable instructions to receive a dispatch request result from the vehicle dispatch center 158, via the dispatch request API. The dispatch request result may include information regarding a dispatched vehicle provisioned for the user, such as the location of the dispatched vehicle, the estimated time of arrival (ETA) of the dispatched vehicle, etc. In one embodiment, the dispatch request processing module 142 further includes executable instructions to generate a graphical map of the location of the stranded vehicle relative to the dispatched vehicle. The graphical map may be delivered to the dispatch request display module 130 in the server computer 104.
The dispatch request display module 130 includes executable instructions to route the graphical map of the location of the stranded vehicle relative to the dispatched vehicle for display on the mobile device 102. In certain embodiments, the mobile web application 116 in the mobile device 102 includes executable instructions to periodically poll the server computer 104 to get real-time location information updates associated with the dispatched vehicle relative to the stranded vehicle. Alternately, the server computer 104 can periodically push this information to the mobile device 102. The dispatch request display module 130 further includes executable instructions to display an updated graphical map of the location updates on the mobile device 102. In another embodiment, the dispatch request display module 130 includes executable instructions to display real-time location updates associated with the dispatched vehicle relative to the stranded vehicle via short message service (SMS) or email messages on the mobile device 102.
In certain embodiments, the web service module 126 may also include executable instructions to determine if the graphical map of the location displayed to the user (in operation 188) is accurate. If the graphical map of the location is not accurate, executable instructions in the web service module 126 determine if the accurate location of the stranded vehicle can be directly obtained from the user. If the accurate location cannot be directly obtained from the user, then executable instructions in the web service module 126 provide the user with information to directly contact a service representative for provisioning a vehicle to the user.
Returning to FIG. 5 , in operation 192, additional information regarding the stranded vehicle is obtained from the user. In operation 194, the location of the stranded vehicle and the additional information is sent as a dispatch request to provision a vehicle for the user. In operation 196, a check is performed to determine if a vehicle can be successfully provisioned for the user. In one embodiment, the dispatch request processing module 142 includes executable instructions to determine if a vehicle can be successfully provisioned. For example, following the dispatch request API call, it may be determined that the customer's coverage level is insufficient to cover the cost of dispatching a vehicle or that a dispatched vehicle cannot be provisioned within an acceptable time period. If a vehicle cannot be successfully provisioned, then execution passes to operation 198 wherein executable instructions in the dispatch request processing module 142 provide the vehicle dispatch center 158 with information to directly call the user to discuss alternative arrangements to dispatch a vehicle to the user. If a vehicle can be successfully provisioned, then execution passes to operation 200 to display a map of the location of the GPS-enabled dispatched vehicle relative to the stranded vehicle. It may be noted that in the sequence of operations (180-200) discussed above, a user may elect to call a service representative in the vehicle dispatch center 158 to provision a vehicle for the user, at any point in time.
Those skilled in the art will recognize a number of advantages associated with the disclosed embodiments. The disclosed embodiments enable the provisioning of a vehicle programmatically via software modules that integrate the functionality provided by a vehicle dispatch center with the services provided by a vehicle roadside assistance center. The communication and processing of dispatch requests programmatically via the dispatch request API enables the automatic provisioning of a vehicle to the user. Accordingly, information regarding a provisioned vehicle is automatically displayed on the user's mobile device, without the user having to contact a service representative at a vehicle dispatch center to obtain the information. This results in increased cost savings to the user. In addition, the programmatic display of location updates of a dispatched vehicle relative to a stranded vehicle on the mobile device via the software modules enables the user to view the status of a request in real-time on the mobile device, thereby creating enhanced user experience and satisfaction.
An embodiment of the present invention relates to a computer storage product with a computer-readable medium having computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs, DVDs and holographic devices; magneto-optical media; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (“ASICs”), programmable logic devices (“PLDs”) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter. For example, an embodiment of the invention may be implemented using Java, C++, or other object-oriented programming language and development tools. Another embodiment of the invention may be implemented in hardwired circuitry in place of, or in combination with, machine-executable software instructions.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that specific details are not required in order to practice the invention. Thus, the foregoing descriptions of specific embodiments of the invention are presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed; obviously, many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, they thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the following claims and their equivalents define the scope of the invention.
Claims (28)
1. A non-transient computer readable storage medium comprising executable instructions to:
receive from a mobile device a request regarding a stranded vehicle;
process the request to determine the location of the stranded vehicle; and
deliver to the mobile device the location of the stranded vehicle relative to a dispatched vehicle, wherein the executable instructions to deliver include executable instructions to automatically deliver a graphical map of location updates associated with the dispatched vehicle relative to the stranded vehicle.
2. The non-transient computer readable storage medium of claim 1 , wherein the request is received via a mobile web application in the mobile device.
3. The non-transient computer readable storage medium of claim 1 , wherein the executable instructions to process the request comprise executable instructions to retrieve additional information regarding the stranded vehicle.
4. The non-transient computer readable storage medium of claim 3 , wherein the additional information comprises vehicle status information, vehicle coverage information and vehicle insurance policy information.
5. The non-transient computer readable storage medium of claim 3 , wherein the executable instructions to process the request further comprise executable instructions to automatically provision the dispatched vehicle to a user based on the additional information and the location of the stranded vehicle.
6. The non-transient computer readable storage medium of claim 1 , wherein the executable instructions to deliver include executable instructions to automatically deliver at least one of information from a short message service (SMS) and an email message comprising location updates associated with the dispatched vehicle relative to the stranded vehicle.
7. A non-transient computer readable storage medium comprising executable instructions to:
receive from a mobile device a request regarding a stranded vehicle;
process the request to determine the location of the stranded vehicle;
obtain vehicle insurance policy information for the user of the mobile device;
perform an evaluation of the vehicle insurance policy information to confirm a coverage level to cover the cost of dispatching a vehicle to the stranded vehicle; and
selectively dispatch a vehicle to the stranded vehicle based upon the evaluation.
8. The non-transient computer readable storage medium of claim 7 further comprising executable instructions to access a map service.
9. The non-transient computer readable storage medium of claim 8 further comprising executable instructions to deliver to the mobile device the location of the stranded vehicle relative to a dispatched vehicle.
10. The non-transient computer readable storage medium of claim 9 further comprising executable instructions to automatically deliver a graphical map of location updates associated with the dispatched vehicle relative to the stranded vehicle.
11. An apparatus comprising:
at least one processor; and
memory storing computer-readable instructions that, when executed by the at least one processor, cause the apparatus to:
receive, from a mobile device, a request for assistance with a stranded vehicle and additional information for a policy associated with the stranded vehicle;
based on receiving the request and the additional information:
determine a first location of the stranded vehicle at least by communicating the request to a mobile device location service;
transmit, to a remote computer, a dispatch request comprising the first location and the additional information, wherein the remote computer triggers dispatch of a rescue vehicle by delivering the dispatch request to a vehicle dispatch center, wherein the dispatch request is delivered in response to the remote computer determining that the additional information indicates the policy associated with the stranded vehicle includes dispatch of the rescue vehicle;
transmit, to the mobile device, a map generated by the remote computer and based on a dispatch request result received from the vehicle dispatch center, wherein the map includes the first location of the stranded vehicle relative to a second location of the rescue vehicle; and
present, on a graphical user interface presented on a graphical display of the mobile device, the map including the first location and the second location.
12. The apparatus of claim 11 , wherein the apparatus receives the request through a mobile web application.
13. The apparatus of claim 11 , wherein the apparatus receives the request and the additional information over a wireless communications channel.
14. The apparatus of claim 11 , wherein the dispatch request further comprises the additional information for the policy associated with the stranded vehicle.
15. The apparatus of claim 14 , wherein the additional information comprises vehicle status information of the stranded vehicle.
16. The apparatus of claim 15 , wherein the additional information includes coverage information for the stranded vehicle.
17. The apparatus of claim 11 , wherein the instructions, when executed, further cause the apparatus to transmit, to the mobile device, an update to the second location of the rescue vehicle.
18. The apparatus of claim 17 , wherein the apparatus transmits the update to the second location using a short message service (SMS) or using an email message.
19. The apparatus of claim 11 , wherein the mobile device comprises a smart phone.
20. A method comprising:
receiving, by a server and from a mobile device, a request for assistance with a stranded vehicle and additional information for a policy associated with the stranded vehicle;
based on receiving the request and the additional information:
determining a first location of the stranded vehicle at least by communicating the request to a mobile device location service;
transmitting, to a remote computer, a dispatch request comprising the first location and the additional information, wherein the remote computer triggers dispatch of a rescue vehicle by delivering the dispatch request to a vehicle dispatch center, wherein the dispatch request is delivered in response to the remote computer determining that the additional information indicates the policy associated with the stranded vehicle includes dispatch of the rescue vehicle;
transmitting, to the mobile device, a map generated by the remote computer and based on a dispatch request result received from the vehicle dispatch center, wherein the map includes the first location of the stranded vehicle relative to a second location of the rescue vehicle; and
presenting, on a graphical user interface presented on a graphical display of the mobile device, the map including the first location and the second location.
21. The method of claim 20 , wherein the request is received through a mobile web application.
22. The method of claim 20 , wherein the request and the additional information are received over a wireless communications channel.
23. The method of claim 20 , wherein the dispatch request further comprises the additional information for the policy associated with the stranded vehicle.
24. The method of claim 23 , wherein the additional information comprises vehicle status information of the stranded vehicle.
25. The method of claim 24 , wherein the additional information includes coverage information for the stranded vehicle.
26. The method of claim 20 , further comprising transmitting, to the mobile device, an update to the second location of the rescue vehicle.
27. The method of claim 26 , wherein the update to the second location is transmitted using a short message service (SMS) or is transmitted using an email message.
28. The method of claim 20 , wherein the mobile device comprises a smart phone.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US17/121,195 USRE50665E1 (en) | 2009-06-26 | 2020-12-14 | Apparatus and method for automated vehicle roadside assistance |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US12/493,103 US8583320B2 (en) | 2009-06-26 | 2009-06-26 | Apparatus and method for automated vehicle roadside assistance |
| US14/940,002 USRE48359E1 (en) | 2009-06-26 | 2015-11-12 | Apparatus and method for automated vehicle roadside assistance |
| US17/121,195 USRE50665E1 (en) | 2009-06-26 | 2020-12-14 | Apparatus and method for automated vehicle roadside assistance |
Related Parent Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/493,103 Reissue US8583320B2 (en) | 2009-06-26 | 2009-06-26 | Apparatus and method for automated vehicle roadside assistance |
| US14/940,002 Continuation USRE48359E1 (en) | 2009-06-26 | 2015-11-12 | Apparatus and method for automated vehicle roadside assistance |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| USRE50665E1 true USRE50665E1 (en) | 2025-11-18 |
Family
ID=43381659
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/493,103 Ceased US8583320B2 (en) | 2009-06-26 | 2009-06-26 | Apparatus and method for automated vehicle roadside assistance |
| US14/940,002 Active 2032-02-14 USRE48359E1 (en) | 2009-06-26 | 2015-11-12 | Apparatus and method for automated vehicle roadside assistance |
| US17/121,195 Active 2032-02-14 USRE50665E1 (en) | 2009-06-26 | 2020-12-14 | Apparatus and method for automated vehicle roadside assistance |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/493,103 Ceased US8583320B2 (en) | 2009-06-26 | 2009-06-26 | Apparatus and method for automated vehicle roadside assistance |
| US14/940,002 Active 2032-02-14 USRE48359E1 (en) | 2009-06-26 | 2015-11-12 | Apparatus and method for automated vehicle roadside assistance |
Country Status (3)
| Country | Link |
|---|---|
| US (3) | US8583320B2 (en) |
| CA (1) | CA2765950C (en) |
| WO (1) | WO2010151442A1 (en) |
Families Citing this family (32)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| US9070243B1 (en) | 2009-08-19 | 2015-06-30 | Allstate Insurance Company | Assistance on the go |
| US9659301B1 (en) | 2009-08-19 | 2017-05-23 | Allstate Insurance Company | Roadside assistance |
| CA2760342C (en) * | 2011-01-26 | 2018-07-24 | The Goodyear Tire & Rubber Company | Management of roadside service requests |
| CN105701361B (en) * | 2011-09-22 | 2018-11-13 | 阿索恩公司 | Monitoring, diagnosis and trace tool for autonomous mobile robot |
| US9965783B2 (en) | 2014-02-07 | 2018-05-08 | Uber Technologies, Inc. | User controlled media for use with on-demand transport services |
| AU2014386266A1 (en) | 2014-03-13 | 2016-09-29 | Uber Technologies, Inc. | Configurable push notifications for a transport service |
| US9494938B1 (en) | 2014-04-03 | 2016-11-15 | Google Inc. | Unique signaling for autonomous vehicles to preserve user privacy |
| US10477159B1 (en) * | 2014-04-03 | 2019-11-12 | Waymo Llc | Augmented reality display for identifying vehicles to preserve user privacy |
| US9536271B2 (en) | 2014-05-16 | 2017-01-03 | Uber Technologies, Inc. | User-configurable indication device for use with an on-demand transport service |
| US9892637B2 (en) | 2014-05-29 | 2018-02-13 | Rideshare Displays, Inc. | Vehicle identification system |
| US10467896B2 (en) | 2014-05-29 | 2019-11-05 | Rideshare Displays, Inc. | Vehicle identification system and method |
| US10559038B1 (en) | 2014-07-30 | 2020-02-11 | Allstate Insurance Company | Mobile service provider and insurance systems |
| US11216824B1 (en) | 2015-02-26 | 2022-01-04 | Allstate Insurance Company | Role assignment for enhanced roadside assistance |
| US10212536B2 (en) | 2015-07-10 | 2019-02-19 | Uber Technologies, Inc. | Selecting a messaging protocol for transmitting data in connection with a location-based service |
| WO2017053046A1 (en) * | 2015-09-21 | 2017-03-30 | Continental Intelligent Transportation Systems, LLC | On-demand and on-site vehicle maintenance service |
| US20170140580A1 (en) | 2015-11-17 | 2017-05-18 | The Goodyear Tire & Rubber Company | System and method for servicing a damaged vehicle |
| US10325442B2 (en) | 2016-10-12 | 2019-06-18 | Uber Technologies, Inc. | Facilitating direct rider driver pairing for mass egress areas |
| US10355788B2 (en) | 2017-01-06 | 2019-07-16 | Uber Technologies, Inc. | Method and system for ultrasonic proximity service |
| US10440536B2 (en) | 2017-05-19 | 2019-10-08 | Waymo Llc | Early boarding of passengers in autonomous vehicles |
| US10579788B2 (en) | 2017-08-17 | 2020-03-03 | Waymo Llc | Recognizing assigned passengers for autonomous vehicles |
| US11348170B2 (en) | 2018-03-27 | 2022-05-31 | Allstate Insurance Company | Systems and methods for identifying and transferring digital assets |
| 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 |
| US20190320043A1 (en) * | 2018-04-13 | 2019-10-17 | Uber Technologies, Inc. | Network computer system to generate synthetic messages based on service-specific information |
| US11012809B2 (en) | 2019-02-08 | 2021-05-18 | Uber Technologies, Inc. | Proximity alert system |
| JP2020134980A (en) * | 2019-02-12 | 2020-08-31 | トヨタ自動車株式会社 | User support system and vehicle control system |
| US12243091B2 (en) | 2019-05-31 | 2025-03-04 | Allstate Insurance Company | Synchronized interactive voice response system and graphical user interface for automated roadside service |
| US12300043B1 (en) * | 2019-07-12 | 2025-05-13 | Allstate Insurance Company | Roadside assistance detection |
| US20210293551A1 (en) | 2020-03-23 | 2021-09-23 | Toyota Motor North America, Inc. | Automatic alternate transportation |
| US11285968B2 (en) * | 2020-06-30 | 2022-03-29 | Waymo Llc | Roadside assistance for autonomous vehicles |
Citations (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5334974A (en) | 1992-02-06 | 1994-08-02 | Simms James R | Personal security system |
| US5808564A (en) | 1992-02-06 | 1998-09-15 | Simms Security Corp. | Personal security system with remote activation |
| US5890061A (en) | 1996-02-09 | 1999-03-30 | Ford Motor Company | Vehicular emergency message system with call restriction defeating |
| US5904727A (en) | 1995-05-17 | 1999-05-18 | Mobile Information Systems, Inc. | Graphical fleet management methods |
| US20010005217A1 (en) | 1998-06-01 | 2001-06-28 | Hamilton Jeffrey Allen | Incident recording information transfer device |
| US20020145666A1 (en) | 1998-06-01 | 2002-10-10 | Scaman Robert Jeffery | Incident recording secure database |
| US6539301B1 (en) * | 1996-08-02 | 2003-03-25 | Magellan Dis, Inc. | System and method for controlling a vehicle emergency response network |
| US20030109244A1 (en) * | 1996-02-28 | 2003-06-12 | Tendler Robert K. | Location based service request system |
| US6694234B2 (en) | 2000-10-06 | 2004-02-17 | Gmac Insurance Company | Customer service automation systems and methods |
| US20040198441A1 (en) | 2002-07-29 | 2004-10-07 | George Cooper | Wireless communication device and method |
| US20040225582A1 (en) | 2003-05-02 | 2004-11-11 | Gil Spitzer | System and method for prepaid roadside assistance |
| US20050075767A1 (en) * | 2001-10-31 | 2005-04-07 | Giovanni Dasti | Method and system for providing assistance to vehicles with damaged wheel components |
| US20060223518A1 (en) * | 2005-04-04 | 2006-10-05 | Haney Richard D | Location sharing and tracking using mobile phones or other wireless devices |
| US20060258379A1 (en) | 2005-05-13 | 2006-11-16 | General Motors Corporation | Method and system for delivering telematics services via a handheld communication device |
| US7174243B1 (en) | 2001-12-06 | 2007-02-06 | Hti Ip, Llc | Wireless, internet-based system for transmitting and analyzing GPS data |
| US20080027761A1 (en) | 2006-07-25 | 2008-01-31 | Avraham Bracha | System and method for verifying driver's insurance coverage |
| US20080052151A1 (en) | 2006-08-28 | 2008-02-28 | Microsoft Corporation | Selecting advertisements based on serving area and map area |
| US20090143079A1 (en) | 2007-12-04 | 2009-06-04 | Research In Motion Limited | Mobile tracking |
| US20090177385A1 (en) | 2008-01-06 | 2009-07-09 | Apple Inc. | Graphical user interface for presenting location information |
| US20090216600A1 (en) | 2008-02-27 | 2009-08-27 | Montiss Llc | Systems and methods for arranging a transport transaction |
| US20090233572A1 (en) * | 2008-03-17 | 2009-09-17 | Basir Otman A | Roadside and emergency assistance system |
| US7633387B2 (en) * | 2005-11-29 | 2009-12-15 | Ert Systems, Llc | Method for tracking personnel and equipment in chaotic environments |
| US20100151838A1 (en) | 2008-12-12 | 2010-06-17 | Research In Motion Limited | System and method for providing traffic notifications to mobile devices |
| US20110143670A1 (en) * | 2008-01-31 | 2011-06-16 | Tod Farrell | Flexible Telematics System and Method for Providing Telematics to a Vehicle |
| US8036160B1 (en) | 2008-04-02 | 2011-10-11 | United Services Automobile Association (Usaa) | Systems and methods for location based call routing |
| US8755779B1 (en) * | 2008-07-25 | 2014-06-17 | United Services Automobile Association | Systems and methods for claims processing via mobile device |
| US8781958B2 (en) | 2011-06-15 | 2014-07-15 | Joseph Michael | Systems and methods for monitoring, managing, and facilitating transactions involving vehicles |
| US9109904B2 (en) | 2007-06-28 | 2015-08-18 | Apple Inc. | Integration of map services and user applications in a mobile device |
| US9426293B1 (en) | 2008-04-02 | 2016-08-23 | United Services Automobile Association (Usaa) | Systems and methods for location based call routing |
-
2009
- 2009-06-26 US US12/493,103 patent/US8583320B2/en not_active Ceased
-
2010
- 2010-06-11 CA CA2765950A patent/CA2765950C/en not_active Expired - Fee Related
- 2010-06-11 WO PCT/US2010/038292 patent/WO2010151442A1/en not_active Ceased
-
2015
- 2015-11-12 US US14/940,002 patent/USRE48359E1/en active Active
-
2020
- 2020-12-14 US US17/121,195 patent/USRE50665E1/en active Active
Patent Citations (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5808564A (en) | 1992-02-06 | 1998-09-15 | Simms Security Corp. | Personal security system with remote activation |
| US5334974A (en) | 1992-02-06 | 1994-08-02 | Simms James R | Personal security system |
| US5904727A (en) | 1995-05-17 | 1999-05-18 | Mobile Information Systems, Inc. | Graphical fleet management methods |
| US5890061A (en) | 1996-02-09 | 1999-03-30 | Ford Motor Company | Vehicular emergency message system with call restriction defeating |
| US20030109244A1 (en) * | 1996-02-28 | 2003-06-12 | Tendler Robert K. | Location based service request system |
| US6539301B1 (en) * | 1996-08-02 | 2003-03-25 | Magellan Dis, Inc. | System and method for controlling a vehicle emergency response network |
| US20010005217A1 (en) | 1998-06-01 | 2001-06-28 | Hamilton Jeffrey Allen | Incident recording information transfer device |
| US20020145666A1 (en) | 1998-06-01 | 2002-10-10 | Scaman Robert Jeffery | Incident recording secure database |
| US6694234B2 (en) | 2000-10-06 | 2004-02-17 | Gmac Insurance Company | Customer service automation systems and methods |
| US20050075767A1 (en) * | 2001-10-31 | 2005-04-07 | Giovanni Dasti | Method and system for providing assistance to vehicles with damaged wheel components |
| US7174243B1 (en) | 2001-12-06 | 2007-02-06 | Hti Ip, Llc | Wireless, internet-based system for transmitting and analyzing GPS data |
| US20040198441A1 (en) | 2002-07-29 | 2004-10-07 | George Cooper | Wireless communication device and method |
| US20040225582A1 (en) | 2003-05-02 | 2004-11-11 | Gil Spitzer | System and method for prepaid roadside assistance |
| US20060223518A1 (en) * | 2005-04-04 | 2006-10-05 | Haney Richard D | Location sharing and tracking using mobile phones or other wireless devices |
| US20060258379A1 (en) | 2005-05-13 | 2006-11-16 | General Motors Corporation | Method and system for delivering telematics services via a handheld communication device |
| US7633387B2 (en) * | 2005-11-29 | 2009-12-15 | Ert Systems, Llc | Method for tracking personnel and equipment in chaotic environments |
| US20080027761A1 (en) | 2006-07-25 | 2008-01-31 | Avraham Bracha | System and method for verifying driver's insurance coverage |
| US20080052151A1 (en) | 2006-08-28 | 2008-02-28 | Microsoft Corporation | Selecting advertisements based on serving area and map area |
| US9109904B2 (en) | 2007-06-28 | 2015-08-18 | Apple Inc. | Integration of map services and user applications in a mobile device |
| US20090143079A1 (en) | 2007-12-04 | 2009-06-04 | Research In Motion Limited | Mobile tracking |
| US20090177385A1 (en) | 2008-01-06 | 2009-07-09 | Apple Inc. | Graphical user interface for presenting location information |
| US20110143670A1 (en) * | 2008-01-31 | 2011-06-16 | Tod Farrell | Flexible Telematics System and Method for Providing Telematics to a Vehicle |
| US20090216600A1 (en) | 2008-02-27 | 2009-08-27 | Montiss Llc | Systems and methods for arranging a transport transaction |
| US20090233572A1 (en) * | 2008-03-17 | 2009-09-17 | Basir Otman A | Roadside and emergency assistance system |
| US8036160B1 (en) | 2008-04-02 | 2011-10-11 | United Services Automobile Association (Usaa) | Systems and methods for location based call routing |
| US9426293B1 (en) | 2008-04-02 | 2016-08-23 | United Services Automobile Association (Usaa) | Systems and methods for location based call routing |
| US8755779B1 (en) * | 2008-07-25 | 2014-06-17 | United Services Automobile Association | Systems and methods for claims processing via mobile device |
| US20100151838A1 (en) | 2008-12-12 | 2010-06-17 | Research In Motion Limited | System and method for providing traffic notifications to mobile devices |
| US8781958B2 (en) | 2011-06-15 | 2014-07-15 | Joseph Michael | Systems and methods for monitoring, managing, and facilitating transactions involving vehicles |
Non-Patent Citations (4)
| Title |
|---|
| PCT/US10/38292, Esurance, Inc. International Search Report (Aug. 5, 2010). |
| Sep. 1, 2020—(US) Notice of Allowance—U.S. Appl. No. 14/940,002. |
| PCT/US10/38292, Esurance, Inc. International Search Report (Aug. 5, 2010). |
| Sep. 1, 2020—(US) Notice of Allowance—U.S. Appl. No. 14/940,002. |
Also Published As
| Publication number | Publication date |
|---|---|
| CA2765950C (en) | 2015-11-24 |
| WO2010151442A1 (en) | 2010-12-29 |
| US8583320B2 (en) | 2013-11-12 |
| US20100332133A1 (en) | 2010-12-30 |
| USRE48359E1 (en) | 2020-12-15 |
| CA2765950A1 (en) | 2010-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| USRE50665E1 (en) | Apparatus and method for automated vehicle roadside assistance | |
| CN107492063B (en) | Boarding point recommendation processing method and system | |
| CN107491825B (en) | Taxi booking processing method and system | |
| US8805419B2 (en) | Management of roadside service requests | |
| US20030087648A1 (en) | End user to mobile service provider message exchange system based on proximity | |
| US20170163748A1 (en) | Systems and Methods for Providing Beacon-Based Notifications | |
| US20150294266A1 (en) | Delivery of physical objects to non-fixed end points | |
| US20140026094A1 (en) | Service notification and alert system and method | |
| US10674321B2 (en) | Lost device detection using geospatial location data | |
| CN101395449A (en) | Mobile station, server and operating method of navigation system | |
| US20210182757A1 (en) | Server device, information processing system, non-transitory storage medium, and method for operating information processing system | |
| US20180295471A1 (en) | Systems and Methods for Beacon Location Verification | |
| JP2019144986A (en) | Lending management device, lending management method, lending management program and lending management system | |
| US20180330318A1 (en) | Systems and Methods for Dynamically Updating Stored Lists Based on Contemporaneous Location Data Associated with Client Devices | |
| CA2628464A1 (en) | Methods and apparatus for delivering regional parameters | |
| JP2019096171A (en) | Vehicle allocation management system and vehicle allocation management method | |
| JP2006268229A (en) | Taxi dispatch system and program | |
| EP3401871A1 (en) | Entry detection system, entry detection device, and program | |
| US20200025580A1 (en) | Information processing apparatus and information processing method | |
| CN105448127A (en) | Bus arrival prompting method, apparatus and system | |
| JP6666510B1 (en) | Vehicle allocation management system, management device, and vehicle presentation method | |
| US8788422B2 (en) | Identifying partial user-entered data | |
| US20200065742A1 (en) | Information processing apparatus, information processing method, and non-transitory storage medium | |
| CN111985987A (en) | Multi-trip travel service implementation method, terminal and system | |
| JP2004318764A (en) | Inducement system using personal digital assistant |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |