US 8,645,014 B1Grant
Assistance on the go
Issue Date:2014-02-04
•13 Claims
•7 Drawing Sheets
Abstract
A mobile computerized apparatus for use with a roadside assistance program to assist in identifying a service provider, such as a tow truck, is disclosed. The apparatus transmits relevant information to a remote server. The server in turn provides information about a plurality of service providers available to service the vehicle.
Metadata
Assignee
- Allstate Insurance Company
Inventors
- Tara Cavallaro Kozlowski
- Ryan Mark Briggs
- Imran Iqbal
Application Information
Application Number:US 12/859,634
Filing Date:2010-08-19
Priority Date:2009-08-19
Art Unit:3667
Classifications
IPC:
G01C22/00G01M17/00H04M11/04
Patent Drawings (7 sheets)
Description
[0001] This application claims priority from both U.S. Provisional Application Ser. No. 61/235,217, entitled “Assistance on the Go,” filed Aug. 19, 2009, and U.S. Provisional Application Ser. No. 61/255,349, entitled “Assistance on the Go,” filed Oct. 27, 2009, which are both herein incorporated by reference in their entireties.
Technical Field
[0002] Aspects of the disclosure relate to roadside service and other enhanced services using a mobile device. More specifically, aspects of the disclosure relate to wireless-enabled devices that communicate with a remote server computer to facilitate and enhance roadside services and other services.
Brief Description of the Drawings
[0003] Aspects of the invention may take physical form in certain parts and steps, embodiments of which will be described in detail in the following description and illustrated in the accompanying drawings that form a part hereof, wherein:
[0004] FIG. 1 depicts an illustrative operating environment in accordance with aspects of the invention;
[0005] FIG. 2 illustrates an exemplary operating environment in accordance with aspects of the invention;
[0006] FIG. 3 is a flowchart illustrating the pre-registration process in accordance with aspects of the invention; and
[0007] FIGS. 4-6 illustrate exemplary screenshots of an application for roadside assistance in accordance with various aspects of the invention.
[0008] It will be apparent to one skilled in the art after review of the entirety disclosed that the steps illustrated in the figures listed above may be performed in other than the recited order, and that one or more steps illustrated in these figures may be optional.
Summary of Invention
[0009] In one embodiment in accordance with aspects of the disclosure, a mobile computerized apparatus configured to provide membership status in a roadside assistance program after occurrence of a roadside event is disclosed. The apparatus executes instructions that cause/allow the apparatus to receive input related to an electronic membership card, retrieve from a data store membership information associated with the vehicle, and dynamically update the electronic membership card for display on the apparatus.
[0010] In one embodiment in accordance with aspects of the disclosure, a mobile computerized apparatus for use with a roadside assistance program to assist in identifying a service provider, such as a tow truck, is disclosed. The apparatus transmits relevant information to a remote server. The server in turn provides information about a plurality of service providers available to service the vehicle.
Detailed Description
[0011] FIG. 1 depicts an illustrative operating environment in accordance with aspects of the invention. A user of wireless-enabled devices 102, 104 may communicate with a wireless access point 106. The wireless-enabled device 102 may be a mobile telephone with applications and other functionality (e.g., APPLE® iPhone, RESEARCH IN MOTION® Blackberry, HTC® Android-based G1, or other mobile telephone), a handheld device with Wi-Fi connectivity (e.g., APPLE® iTouch), a mobile telephone with an enhanced roadside assistance application installed, or other portable electronic device. The wireless-enabled devices 102, 104 may be configured to communicate with a wireless access point 106 such as a cellular tower operated by a cellular service provider. Alternatively, the wireless access point 106 may be a Wi-Fi (e.g., compatible with IEEE 802.11a/b/g/etc. wireless communication standards) hotspot where the wireless-enabled device 102, 104 may obtain access to the Internet (e.g., to communicate using online chat applications or voice-over-IP applications). One skilled in the art will appreciate that other techniques may be used to allow devices 102, 104 access over a wide area network (WAN).
[0012] The data communicated from the user devices 102, 104 may be transmitted to a server 108. The server 108 (e.g., a high-performance Intel® computer) may include a memory 112 storing computer-readable instructions and a processor 114 for executing the computer-readable instructions. The data communicated to the server 108 from the user device 102, 104 may be transmitted over the WAN through wireless access point 106. Meanwhile, another server 110 may be comprised of a memory 120 storing computer-readable instructions and a processor 116 for executing the computer-readable instructions in accordance with aspects of the invention. The memories 112, 120 may also store computer data files that hold information that may be useful to applications running on the user's mobile device 102, 104 or the servers 108, 110. For example, the computer data files may include user login/profile information, insurance policy (or motor club) information, service provider list and related information, and/or other information. The data collected and stored in the data files may be used to support one or more of the numerous features disclosed throughout this disclosure.
[0013] One skilled in the art will appreciate that the server (e.g., servers 110 and 108) is not limited to a single machine or device. The server may be embodied as a web server or Internet-accessible server. Furthermore, the term server refers to any system of computers and/or devices (e.g., firewalls, routers, caching systems, proxy servers, etc. or combination thereof) that may be used to provide access to services and features available for use. As such, different reference to the server performing particular steps does not require that the same machine/device perform all the steps.
[0014] Servers (108 and 110), data store 122, and wireless access point 106 may communicate over a wired and/or wireless connection. In some instances, a private, secure connection may be established between one or more of these components. For example, server 108 and server 110 may communicate over a network cloud representing the Internet. Alternatively, server 108 and data store 122 may communicate over a secure WAN or a dedicated T1 (or other telecommunications) line. Furthermore, wireless devices 102, 104 may include a processor, memory, display screen (e.g., touchscreen), keypad, sensors (e.g., motion, light, etc.), camera, global positioning system (GPS) chip, audio output/input devices, and other electronic components configured for use in mobile phones, PDAs, and mini-laptops.
[0015] In another example, one or more servers 108, 110 may include a processor, RAM, ROM, communications module, and/or memory storing an operating system, applications, and/or data. The server may have a processor for controlling overall operation of the server and its associated components, including random access memory, read-only memory, communications module, and memory. Such a server may include a variety of computer readable media. Computer readable media may be any available media, both tangible and intangible, that may be accessed by the server and include both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer readable media may comprise a combination of computer storage media and communication media. Computer storage media include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, object code, data structures, program modules or other data. Computer storage media include, but are not limited to, random access memory (RAM), read only memory (ROM), electronically erasable programmable read only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the server.
[0016] The aforementioned server may include one or more applications representing the application data stored in RAM memory while the server is on and corresponding software applications (e.g., software tasks) are running on the server. The aforementioned communications module may include a microphone, keypad, touch screen, and/or stylus through which an (optional) user of the server may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audio/visual and/or graphical output. Software may be stored within the memory and/or storage to provide instructions to the processor for enabling the server to perform various functions. For example, memory may store software used by the server, such as an operating system, application programs, and/or an associated database. Alternatively, some or all of the computer executable instructions for the server may be embodied in hardware or firmware. Moreover, a database (or data store) 122 may provide centralized storage of data.
[0017] Such a server may operate in a networked environment supporting connections to one or more remote computing devices. The remote computing devices may be personal computing devices or servers that include many or all of the elements described above relative to the server. Remote computing devices may be a mobile device communicating over wireless carrier channel. The network connections depicted in the figures may include a local area network (LAN) and/or a wide area network (WAN), but may also include other networks. When used in a LAN networking environment, the server may be connected to the LAN through a network interface or adapter in the communications module. When used in a WAN networking environment, the server may include a modem in the communications module or other means for establishing communications over the WAN, such as the Internet. It will be appreciated that the network connections shown and described are illustrative and other means of establishing a communications link between the computing devices may be used. The existence of any of various well-known protocols such as TCP/IP, Ethernet, FTP, HTTP and the like is presumed, and the system can be operated in a client-server configuration to permit a user to retrieve web pages from a web-based server. Any of various commonly known web browsers can be used to display and manipulate data on web pages.
[0018] Referring to FIG. 2 , numerous mobile wireless-enabled devices are illustrated connecting to mobile architecture 200 over a wireless network. The mobile architecture includes wired and/or wireless connections with servers, data store/database, and a wireless access point. An interactive voice response (IVR) system may also be included to facilitate services not using a cellular data plan. Numerous different application servers and data stores may be included in the mobile architecture, including, but not limited to, a database, application server, map server, software application for use at a call center or for a customer service platform), CTI (i.e., computer telephony integration—which presents voice and data within a customer service platform), data store in which customer and supporting data tables may be housed), IVR (interactive voice response) server, web services application server, interceptor, and firewall. The mobile wireless-enabled devices in FIG. 2 may have application software installed in accordance with various aspects of the invention. The application software may permit the mobile device to communicate with a remote web services application server through the firewall. In an alternative embodiment, the mobile device may have a thin-client installed that provides an interface for the mobile device to execute application software on a remote server. One skilled in the art will appreciate the numerous advantages and disadvantages related to the thin-client and thick-client design choices contemplated by the various embodiments of the invention. Moreover, in some embodiments, the mobile device may receive notifications of software updates (e.g., new versions) of the application and can receive automatic (or manually authorized) download and installation of the updates.
[0019] Flat Tire.
[0020] In one example in accordance with aspects of the invention, John Doe's (i.e., a user) vehicle has a flat tire. John has previously installed a roadside assistance application in accordance with various aspects of the invention on his APPLE® iPhone, and he has registered his vehicle with the application. After launching the roadside assistance application, the registered application attempts to assess whether John is in a safe location. If John presses the “911” icon, the application will automatically dial the emergency line to locate emergency assistance for John. However, in this case, John is at the parking garage near his office building, and he presses the “Yes” icon.
[0021] Next the application, in this example, requests information about John's service needs (see FIG. 5 ). The application provides a list of services 500 to John in a “Service Type” selection box. Some examples of service types include, but are not limited to, locked out (i.e., locked out of one's vehicle), flat tire/tire needs air/tire change, dead battery/battery service/battery replacement, jump start, out of gas/incorrect fuel/fluids, towing, vehicular accident/vehicle fire, mechanical failure/brakes/transmission/engine, lock out/locked out/lost keys/damage keys/keys locked in car, locksmith, winch/stuck, won't start, stalled while driving, reunite, dealer service, transfer, recovery, wrecker, and other (i.e., the service type when none of the listed services are appropriate). In addition, in those cases where the mobile device 102, 104 provides functionality to retrieve and display a user's phone number, the application may retrieve and display that information. John, in some embodiments, may be permitted to edit the callback number displayed by the application if he desires.
[0022] In an alternative example, the mobile device 102, 104 may automatically receive information about the vehicle directly through communications with the vehicle's onboard diagnostics system (e.g., ODB II interface or other comparable interface with the vehicle's diagnostics system). The mobile device 102 may be equipped with appropriate circuitry and/or firmware/software to communicate via the requisite communication protocols for the ODB II interface. Alternatively, an external accessory (e.g., peripheral device) may be attached to the ODB II interface to translate the ODB II codes/data into a format compatible with the communication protocol of the application on the mobile device 102, 104. For example, the external accessory may be a device compliant with BLUETOOTH® that receives the ODB II data and transmits it via a communication channel compliant with BLUETOOTH® to the mobile device 102. Alternatively, the external accessory may attach to the pins on a mobile device 102 and receive the data wirelessly transmitted from the ODB II interface. The information received from the vehicle (e.g., through the ODB II interface) may be used to select the appropriate service type without requiring additional user intervention. Moreover, the ODB II codes may be useful to a service provider (e.g., towing company or mechanic) in contemplating the needs of the user in preparation for addressing the user's calamity.
[0023] In yet another alternative example, John's vehicle may be equipped with a wireless transmission module (e.g., transceiver circuitry) to transmit diagnostic information to a car dealership that services his vehicle. The car dealership may then transmit the information to John (e.g., via an onboard display on the vehicle's dashboard). In accordance with various aspects of the invention, assume John Doe is driving a BMW® brand vehicle equipped with BMWAssist®. John may register on a server 108 to have updates from a third party (e.g., BMW) computer server routed through a server 108 to his mobile device 102 whenever a defect in his vehicle is detected. John Doe can designate computer server 108 to receive notifications on his behalf from the third-party server. As such, the computer server 108, in accordance with various aspects of the invention, can process and transmit the notification to John's mobile device 102. For example, the third-party server may receive notification that a flat-tire has occurred on John Doe's vehicle, and may send a notification to John Doe's mobile device 102 indicating the service type required. Consequently, the “Service Type” information may be pre-filled in the application selection screen. Moreover, in such an example, John may or may not need to be physically present at his vehicle. For example, John may have parked his vehicle in an outdoor lot on a cold winter day while at his office, and he may receive a notification (e.g., a push notification available on APPLE® iPhone OS 3.0 and later, SMS message, e-mail, etc.) on his mobile device 102 in the afternoon stating that his battery has gone dead. John may use his mobile device 102, in accordance with the various aspects of the invention disclosed herein, to contact a preferred service provider and repair his vehicle, all while within the comfort of his warm office and not physically present at his vehicle.
[0024] Furthermore, the ODB II codes (or other types of diagnostic codes) transmitted from the vehicle to the mobile device 102 may be translated to map against the numerous “Service Type” selections available. ODB II codes (and other types of diagnostic codes) may be different for different make and model of cars; therefore, when a user registers with the application and provides information about his/her vehicle, the appropriate mapping for the type of car can be identified and used for translating diagnostic codes. The mapping table may be stored in computer memory at the mobile device 102 or may be maintained in memory 112 at a remote server 108. Likewise, the translation may occur at a processor at the mobile device 102 or at the remote server 108. One skilled in the art will appreciate that there are numerous benefits and drawbacks to each approach.
[0025] Next, mobile device 102 transmits data, either directly or indirectly, to the remote server 108. The transmission may occur in response to a user keypress (e.g., the user selecting a phone icon on the mobile device 102 display). Alternatively, the transmission may occur automatically (e.g., in the embodiments where the ODB II codes are automatically retrieved and transmitted). The data transmitted from the mobile device 102 may include, but is not limited to, the “service type” selected, user identification information (e.g., the mobile device 102 phone number, user's login/username, etc.), location information (e.g., retrieved from the mobile device 102, manually entered by the user, triangulated from cellular towers by the cellular service provider, etc.), vehicle diagnostic data (e.g., OBD II data/codes), and other useful information.
[0026] Next, the server 108 receives the data transmitted from the mobile device 102. The server 108 may use the data to identify one or more service providers (e.g., towing company, taxi company, mechanic, etc.) in the area. In one embodiment, the identification may occur in real-time using an algorithmic selection process that maintains ratings and other metrics about the service providers, and selects one or more provider based on these ratings and metrics. In another embodiment, the provider identified may be based on a company's preferred high-quality relationship with particular service providers.
[0027] In one embodiment in accordance with aspects of the invention, the server 108 may transmit information about one or more service providers to the mobile device 102 for the user's review and final selection. As such, information such as a service provider's name, contact information, rating, and other metrics (e.g., distance from mobile device's location, cost, etc.) may be displayed on the user's mobile device 102. In an alternative embodiment, the server 108 may communicate directly with a service provider and hire a service provider to service the user. For example, the server 108 may communicate over a network (e.g., the Internet, WAN, etc.) with a service provider's server 110. The server 110 may receive a request for a particular service. The request may include pertinent information about the service required, including the location of the vehicle requiring servicing, the type of service required, the make/model/color of the vehicle requiring servicing, the maximum charge allowed for the service (e.g., pre-contracted towing rates), and other information.
[0028] The service provider's server 110 may communicate the information to mobile devices carried by (or installed in the vehicles of) its employees in the field. As such, the employee can accept or reject the new service request. Alternatively, the server 110 may communicate the information to employees located at an office and that are responsible for facilitating new service requests and dispatching service vehicles (e.g., using the Beacon system). Once the service provider accepts the new service request, their server 110 transmits an acceptance message to the server 108. In order to facilitate simultaneous communication to multiple service providers, the server 108 may be required to send a confirmation message to the service provider once acceptance has been received and accepted. At least one benefit of such a system is that multiple service providers may be contacted with a request for a particular service, and then only the “best” service provider willing to accept the service request may be confirmed for the job. In one embodiment in accordance with various aspects of the invention, the service providers may include a price or quote (or other information, such as estimated time of arrival at the user's vehicle) in its acceptance message. As such, service providers may compete (e.g., in an auction-like system) for new servicing jobs. Alternatively, the “best” service provider may simply be the first to reply with an acceptance message. In some embodiments, the server 108 may also transmit a cancellation message to the other service providers (i.e., everyone except the one receiving a confirmation message) once a new service request has been filled so that the other service providers are updated about the current status of filled new service requests. Alternatively, new service requests may automatically expire after a predetermined time period. As such, a cancellation message may not be necessary.
[0029] The server 108 may transmit to the mobile device 102 information about the service provider that will be servicing the user's vehicle. The information may include, but is not limited to the name of the service provider, the estimated time of arrival (ETA), the phone number for the service provider (or the mobile phone number of the particular service vehicle servicing the user's vehicle), and/or other useful information. For example, FIG. 6 illustrates an exemplary “service details” screen 600. In some embodiments, the user is conveniently provided with the option of providing feedback while he/she waits for a service provider to arrive. In some embodiments, the mobile device 102 may receive regular (e.g., every 5 minutes, real-time, or on another regular or periodic basis) updates from the server 108 with the approximate location of the service vehicle that will be servicing the user's vehicle. The approximate location may be displayed on a map or may be provided as an approximate distance from the user's vehicle. Moreover, the approximate time until arrival may be displayed and updated on a regular or periodic basis.
[0030] In an alternative embodiment, server 108 may provide the mobile device 102 with information about service providers. The user may contact the service providers directly (e.g., by calling their office) to arrange for a service provider. At least one advantage of such a system over simply looking up service providers in a telephone directory is that the server 108 may be able to provide an enhanced list of service providers to the mobile device 102. For example, the list may include one or more service providers that are competent in the particular type of service required of the user's vehicle. As such, the user need not be concerned with whether a particular service provider offers the particular service required of the user's vehicle.
[0031] In addition, the server 108 may transmit relevant information to the user's insurance company, emergency contacts, police, fire department, taxi company, and/or others. For example, information necessary for starting a claim may be submitted to the insurance company so the user's process for submitting the claim is already partially completed. In some embodiments, the user may retain full control over whether the insurance company is notified of the user's vehicle situation.
[0032] Moreover, a user's parents, spouse, coworkers, etc. may be contacted to alert them about the user's vehicle situation. For example, in one embodiment, the server 108 may receive notification from the user's mobile device 102, and then reference the user's preferences. A copy of the user's preferences may be saved in memory, e.g., as a data file, at the server 108. The preferences may indicate which additional people or organizations to contact and what information to provide to those people. In another embodiment, the application may enable the user to save his/her emergency contact's information on the mobile device 102. For example, the user may enter his insurance agent's information, personal contact information, and emergency contact information. Alternatively, the screen may permit entry of other relevant information about each contact (e.g., email address, SMS number, alternate phone numbers, etc.) As such, the user may conveniently access his contacts through the application's menu.
[0033] In one embodiment, the server 108 may automatically send a text message (e.g., SMS, etc.) to the user's parent's phone number (or other people's phone numbers) with a predetermined message. The server 108 may alternatively send an e-mail message to the desired person/organization's email address. In some embodiments, the desired person may have an application installed on his/her mobile device 102 that receives a push notification initiated by server 108. The push notification may include a textual message and/or other appropriate information (e.g., the location of the vehicle/user, the condition of the vehicle, whether anyone is injured, etc.) Alternatively, a customer service representative may be alerted by server 108 to manually call the desired person/organization and provide an appropriate message.
[0034] In another embodiment in accordance with aspects of the disclosure, the user may be provided with a guided experience when requesting roadside assistance. The guided experience may be implemented using a series of icons along the top of the screen on the user's mobile device 102. One skilled in the art will appreciate that the guided experience may be provided through different configurations of the icons; for example, the icons may be placed vertically along a side of the screen, or they may be configured in a circular or other pattern around the screen. The series of icons may tell the user where he/she in the process of obtaining roadside assistance.
[0035] In some embodiments in accordance with aspects of the invention, the application may verify that the user is in a safe location. An option for calling “911” may be provided should the user require immediate emergency assistance. Next, as depicted in FIG. 3 , the application may request information about the type of service the user requires. As discussed in detail above, there are numerous service types 300 that may be available for the user to select. Moreover, as already discussed herein, in some embodiments, the user's vehicle may be equipped with appropriate technology to communicate directly with the mobile device to provide/recommend the service type information. Next, the application may direct the user to call a roadside assistance customer service representative to identify and secure the appropriate roadside service provider for the user. The application on the mobile device 102 may transmit the appropriate information (e.g., member number, member's zip code, service type requested, and/or user's current location) to the customer service center. As such, the representative may already have information about the user and/or user's vehicle on-screen when the conversation begins. Additional information about aspects of this feature are disclosed below, including the use of a caller ID feature to automatically match the user with his/her information.
[0036] Once the service provider arrives to provide the user's vehicle with roadside assistance, the user may use his/her mobile device 102 to authorize payment to the service provider. For example, the mobile device 102 may display an icon to permit the user to indicate that service has been satisfactorily provided and completed. Upon receipt of a corresponding message at the server 108 from the mobile device 102, the server 108 may authorize release of funds to the service provider. For example, the server 108 may authorize a bank to perform an ACH transaction of funds directly into the service provider's bank account. In one example, the funds are sourced from the user's bank account; while in another example, the funds are sourced directly from the account of the company providing the roadside assistance program. Meanwhile, in another example a first person (e.g., a parent) may arrange for a second person (e.g., their child) to authorize release of the parent's funds to the service provider. The server 108 may also notify the service provider's server 110 that payment has been authorized. As such, service provider may receive more prompt payment for its services, while also reducing the need to process claims at the insurance company.
[0037] Vehicle Incident.
[0038] In yet another example in accordance with various aspects of the invention, two user vehicles may be involved in a vehicular crash. In such a scenario, the two users may exchange insurance information and other information (e.g., pictures of the crash site taken with a camera on the mobile device 102) wirelessly using their mobile device 102. For example, an application in accordance with various aspects of the invention may enable the users to wirelessly transmit (e.g., using Bluetooth, SMS messaging, e-mail, or other wireless transmission techniques) their information to the other user's mobile device. At least one benefit is that the exchange of information between the parties is much more convenient given the stressful situation of a vehicular crash.
[0039] In addition, the user may contact a customer service representative to report the vehicular incident. In accordance with various aspects of the invention, the representative may already have information about the user and/or user's vehicle on-screen when initiating conversation. For example, the application on the mobile device 102 may transmit the device's phone number and other information (e.g., accident information, user's location, pictures, or other information) to server 108. As such, the representative's system may use the caller ID feature to appropriately identify the transmitted data as corresponding to the phone number identified on the caller ID. Therefore, information about the user and/or user vehicle may already be displayed on the representative's screen when the call commences. Thus, an enhanced roadside assistance program may be offered to users.
[0040] Preventive Measures.
[0041] As explained earlier, vehicles with onboard diagnostic equipment (e.g., ODB II port) may be able to retrieve information about operating parameters of the user's vehicle. As such, the diagnostic equipment may be able to assist the user in the maintenance and upkeep of the vehicle; thus, resulting in a safer vehicle and hopefully fewer incidents. The mobile device 102 may receive alert notifications when parameters of the vehicle are outside of normal operating limits or limits set by the user or other entity. For example, if the user's battery is dead or low, the user may receive a notification on the mobile device 102 (or elsewhere designated by the user) about the dead or failing car battery. Likewise, if the vehicle's tire pressure runs low, the mobile device 102 may receive a notification. Along with the notification, the mobile device 102 may be provided with one or more service providers (e.g., towing companies, mechanics shops, or other providers) that can repair the problem.
[0042] Referring to FIG. 3 , the flowchart illustrates various features of the one or more embodiments of the invention. The user may register using the mobile device 102, or may, in some embodiments, register online with a personal computer. Once the user is registered, information about the user (e.g., user profile information) may be stored on the mobile device 102 (or on a remote server 108). That information may be useful in storing and displaying information about the user, including a picture of the user's vehicle, make/model/year of the vehicle, vehicle's insurance policy (or motor club) number (e.g., virtual membership card), and other pertinent information. In some embodiments, the user may only be “pre-registered” 302 (i.e., registered with the application with some basic information (e.g., name, vehicle, phone number, etc.), but may not have a membership in a roadside assistance program); thus, features such as the virtual membership card may be grayed out (i.e., deactivated) on the user's screen. However, in one example, the pre-registered user may provide the application with some basic authentication information (e.g., last four digits of social security number, date of birth, and/or membership number) to authenticate herself, and then need only provide 304 some minimal additional authorization information (e.g., credit card information, vehicle information, driver information, etc.) to activate/register 306 for membership in the roadside assistance program. At least one benefit of pre-registration is that a user can go through the lengthy registration process in advance, and then at the time of a roadside event (e.g., car crash), the user can activate the pre-registration for membership privileges with minimal hassle.
[0043] One of ordinary skill in the art will understand that the flowcharts illustrate just some examples of functions/features available in accordance with various aspects of the invention, and that other examples of features are available as described throughout the specification and figures. For example, various aspects of the invention include a feature for obtaining customer feedback. The feature enables prompt and accurate feedback about the user's experience because, inter alia, the feedback is collected almost immediately after the event of interest, and the questions can be tailored to the specifics of the particular event/user/details.
[0044] Regarding user vehicle registration, the user may enter various information to register for enhanced roadside assistance. In some embodiments, the user may enter just the vehicle VIN (vehicle identification number). The server 108 and/or mobile device 102 may store the VIN and retrieve information about the vehicle (e.g., made, model, year, etc.) based off the VIN. In an alternative embodiment, the user may also be required to enter membership information, such as name, zip code, or a member identification number. The membership information may be linked to the user's insurance or motor club profile and mapped as such on server 108. As a result, future communications between the mobile device 102 and the server 108 may be recognized as related to a particular member. Membership may refer to membership in a roadside assistance program, motor club, or other group/organization.
[0045] Electronic Membership Card.
[0046] Membership information may be illustrated in an exemplary virtual membership card screen, as depicted in FIG. 4 . The member card screen 400 may illustrate the date through which the user's membership is valid and/or the date since the user has been a member. The user's membership number, membership level (e.g., Platinum), and other information may also be displayed on the membership card screen. At least some of the information displayed on the membership card screen may be locally stored on the mobile device 102. As such, the user need not be connected to a carrier or WiFi in order to retrieve his/her membership information. Alternatively, membership information may be stored on a server 108 and retrieved for display on the screen. At least one benefit of an electronic membership card is that changes to the user's policy and/or other updates may be dynamically pushed to the user's mobile device 102. As such, the user may have instant access to updated policy information and need not necessarily wait for an insurance company to mail him/her an updated membership card. In addition, the membership card screen may include information about services and promotions offered to members. For example, a roadside assistance icon may appear to indicate that roadside assistance on the go is available to the user. In addition, promotions and discounts, for example on travel (e.g., flights, rental cars, hotels, etc.) may be available to members and a corresponding icon or information may appear on the membership card screen accordingly.
[0047] Meanwhile, a service provider may also be provided with a registration screen in some embodiments in accordance with aspects of the invention. Service provider vehicles may be equipped with wireless-enabled devices (e.g., navigation systems with Internet connectivity) that permit the vehicle operator to react in realtime to service requests. For example, the exact location of the service vehicle can be tracked using this onboard device.
[0048] Enhanced Interactive Voice Response (IVR). In an alternative embodiment, information from the application on the mobile device 102 may be transmitted to a remote server related to an IVR system. For wireless devices 102 with a mobile data plan, the information may be transmitted over a wireless Internet connection. However, in those instances where the mobile device does not have data connectivity, the device may transmit the data to the IVR system using other available means. For example, in one embodiment, the information may be transmitted as a SMS (or comparable text message format) message to the IVR system. As a result, when a user calls into the IVR system, the user may receive an enhanced experience because the user's location and other relevant information may already be available at the IVR system. The IVR may, in some embodiments, still confirm for security reasons the name of the member, zip code of the member, and service requested before transferring the user to a service provider. The disclosed enhanced IVR is beneficial because it alleviates the requirement to have the user listen to endless prompts and respond with touchtone key presses. In some examples, if the user wishes to speak with a customer service representative, he/she may press “0” (or other designated key) to immediately speak with a representative.
[0049] Other features in accordance with various aspects of the invention are listed below. For example, server 108 may generate a user driving score based on the user's reactions to communications and recommendations from an insurance company or a motor club. The driving score may be used to adjust the user's insurance premiums or membership dues and/or other aspects of the user's insurance policy or motor club membership. In another example, the mobile device 102 may provide the user with information regarding the relative safety of proposed navigation routes as, for example, is described in the provisional applications, which were previously incorporated by reference in their entireties. In yet another example, the mobile device 102 may provide different color-coded zones on a map to indicate the relative safety of various areas. For example, the mobile device 102 may alert the user that a particular intersection is particularly hazardous and has a statistically higher frequency of vehicle incidents. One or more of these features may be provided in accordance with various aspects of the invention. In yet another example, the mobile device may provide the user with information regarding the relative safety of drivers or vehicles in the vicinity of the user. This information may be provided through transmission of scores or other data regarding the drivers or vehicles in the vicinity of the user.
[0050] In one embodiment in accordance with aspects of the invention, a system is described where two servers and a mobile device assist in providing roadside assistance. The mobile device may communicate with a first server and provide various information about the status of a vehicle, the user, and/or other information. The first server may communicate with a second server to electronically request, approve, and monitor a service provider hired to service the vehicle. The first server may provide information and/or regular updates to the mobile device regarding the service provider. The first server may also authorize payment to the service provider once the job is completed. One or more aspects of the aforementioned embodiment are described in greater detail throughout the disclosure.
[0051] The foregoing presents a simplified summary of the disclosure in order to provide a basic understanding of some aspects. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. Although not required, one of ordinary skill in the art will appreciate that various aspects described herein may be embodied as a method, a data processing system, or as a computer-readable medium storing computer-executable instructions. Accordingly, those aspects may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. For example, a tangible computer-readable medium (e.g., a CD-ROM, RAM, hard drive, flash memory, etc.) storing instructions to cause a processor to perform methods in accordance with aspects of the disclosure is contemplated.
[0052] Numerous trademarks and/or service marks have been used throughout this disclosure. These trademarks and/or service marks are owned by their respective companies.
[0053] Aspects of the invention have been described in terms of illustrative embodiments thereof. Numerous other embodiments, modifications and variations within the scope and spirit of the disclosed invention will occur to persons of ordinary skill in the art from a review of this entire disclosure. For example, one of ordinary skill in the art will appreciate that the steps illustrated in the illustrative figures may be performed in other than the recited order, and that one or more steps illustrated may be optional in accordance with aspects of the disclosure.
Claims
We claim:
1. A mobile computerized apparatus for use with a roadside assistance program to assist in identifying a service provider, comprising:
a processor for executing computer-executable instructions;
a memory storing computer-executable instructions that when executed by the processor cause the apparatus to perform steps comprising:
obtaining, by the apparatus, event information indicative of a selected service type required to service a vehicle resulting from a roadside event;
after occurrence of the roadside event to the vehicle, transmitting, by a wireless component in the apparatus, relevant information to a remote server, the relevant information comprising the selected service type, user identification information, and vehicle location information;
receiving at the apparatus a plurality of service providers competent in the selected service type and in proximity to the vehicle's location, where at least some of the plurality of service providers are identified based on a preferred relationship with the roadside assistance program;
displaying, at the apparatus, a list of the plurality of service providers that are competent in the selected service type;
receiving, at the apparatus, an input selecting a selected service provider from the displayed list of the plurality of service providers that are competent in the selected service type;
transmitting a new service request to the remote server from the apparatus, where the new service request is configured to cause the remote server to:
transmit the new service request to a service provider server associated with the selected service provider; and
in response to receiving an acceptance message from the service provider server, transmitting a confirmation message to the service provider server, where the new service request includes at least part of the relevant information, and where the acceptance message comprises at least one of a price quote and an estimated time of arrival by the selected service provider at the vehicle;
receiving, at the apparatus, a name of the selected service provider, the estimated time of arrival by the selected service provider at the vehicle, and a phone number of the service provider; and
receiving, at the apparatus, updates from the remote server about the estimated time of arrival by the selected service provider at the vehicle.
2. The apparatus of claim 1, where the roadside event comprises at least one of: a lock out of the vehicle, a flat tire of the vehicle, a dead battery of the vehicle, an out of gas condition of the vehicle, and a mechanical failure of the vehicle.
3. The apparatus of claim 1, where the updates from the remote server about the estimated time of arrival include displaying an updated map, at the apparatus, indicating an approximate location of the selected service provider's truck that will be servicing the vehicle.
4. The apparatus of claim 1, where the updates about the estimated time of arrival are received at the apparatus on a periodic basis.
5. The apparatus of claim 1, where the selected service type is determined based on diagnostic codes received from the vehicle and translated, using a mapping table.
6. The apparatus of claim 1, where the phone number of the service provider is represented on a display of the apparatus by a selectable icon, which when selected, causes the apparatus to call the service provider.
7. The apparatus of claim 1, further comprising global positioning system circuitry, where the vehicle location information is retrieved by the global positioning system circuitry.
8. The apparatus of claim 1, where the vehicle location information is manually entered into the apparatus by a user.
9. The apparatus of claim 1, the memory storing computer-executable instructions that when executed by the processor cause the apparatus to perform steps further comprising:
determining, by the processor, that the vehicle is not registered with the roadside assistance program;
determining, by the processor, that the vehicle is pre-registered with the roadside assistance program; and
receiving, at the apparatus, additional authorization information to cause activation of the roadside assistance program for the vehicle.
10. The apparatus of claim 9, where the additional authorization information comprises a credit card number manually entered by a user through the apparatus.
11. The apparatus of claim 9, where the activation of the roadside assistance program occurs at a location of the occurrence of the roadside event.
12. The apparatus of claim 1, the memory storing computer-executable instructions that when executed by the processor cause the apparatus to perform steps further comprising:
receiving, at the apparatus, input indicating successful completion of services provided by the selected service provider; and
causing the remote server to authorize payment to the selected service provider.
13. The apparatus of claim 12, where the authorized payment to the selected service provider is funded by a company providing the roadside assistance program.
Patent Citations (128)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| USD426206(S) | 2000-06-01 | Richter | Applicant |
| USD434419(S) | 2000-11-01 | Bomze et al. | Applicant |
| US6233563(B1) | 2001-05-01 | Jefferson et al. | Applicant |
| US6298229(B1) | 2001-10-01 | Tomlinson, Jr. et al. | Applicant |
| USD453767(S) | 2002-02-01 | Istvan et al. | Applicant |
| USD464660(S) | 2002-10-01 | Weng et al. | Applicant |
| US6493629(B1) | 2002-12-01 | Van Bosch | Applicant |
| US6522265(B1) | 2003-02-01 | Hillman et al. | Applicant |
| USD474479(S) | 2003-05-01 | Tambata | Applicant |
| USD474780(S) | 2003-05-01 | Tambata | Applicant |
| USD475719(S) | 2003-06-01 | Horie | Applicant |
| US6677854(B2) | 2004-01-01 | Dix | Applicant |
| US6745153(B2) | 2004-06-01 | White et al. | Applicant |
| USD495338(S) | 2004-08-01 | Peter et al. | Applicant |
| US6771742(B2) | 2004-08-01 | McCalmont et al. | Applicant |
| US6847825(B1) | 2005-01-01 | Duvall et al. | Applicant |
| USD517087(S) | 2006-03-01 | Sands | Applicant |
| US7012993(B2) | 2006-03-01 | Alton | Applicant |
| US7027808(B2) | 2006-04-01 | Wesby | Applicant |
| USD522015(S) | 2006-05-01 | Cummins et al. | Applicant |
| USD523442(S) | 2006-06-01 | Hiramatsu | Applicant |
| US7068994(B2) | 2006-06-01 | Van Camp | Applicant |
| US7091903(B2) | 2006-08-01 | Kim | Applicant |
| US7092695(B1) | 2006-08-01 | Boling et al. | Applicant |
| US7099835(B2) | 2006-08-01 | Williams, III | Applicant |
| USD529507(S) | 2006-10-01 | Cummings | Applicant |
| USD529510(S) | 2006-10-01 | Cummins et al. | Applicant |
| US7119669(B2) | 2006-10-01 | Lundsgaard et al. | Applicant |
| US7130406(B2) | 2006-10-01 | Pines et al. | Applicant |
| US7142959(B2) | 2006-11-01 | Oesterling et al. | Applicant |
| US7155335(B2) | 2006-12-01 | Rennels | Applicant |
| US7167796(B2) | 2007-01-01 | Taylor et al. | Applicant |
| US7215965(B2) | 2007-05-01 | Fournier et al. | Applicant |
| USD544871(S) | 2007-06-01 | Lim et al. | Applicant |
| US7236576(B2) | 2007-06-01 | Schnarel et al. | Applicant |
| US7242966(B1) | 2007-07-01 | Averkamp | Applicant |
| USD550689(S) | 2007-09-01 | Vigesaa | Applicant |
| US7266435(B2) | 2007-09-01 | Wang et al. | Applicant |
| USD553146(S) | 2007-10-01 | Byeon et al. | Applicant |
| US7289786(B2) | 2007-10-01 | Krasner | Applicant |
| USD556770(S) | 2007-12-01 | O'Donnell et al. | Applicant |
| USD560226(S) | 2008-01-01 | Jung et al. | Applicant |
| US7323973(B1) | 2008-01-01 | Ceglia et al. | Applicant |
| USD561191(S) | 2008-02-01 | Haning et al. | Applicant |
| US7336172(B2) | 2008-02-01 | Govindaraj | Applicant |
| USD563975(S) | 2008-03-01 | Vigesaa | Applicant |
| USD564541(S) | 2008-03-01 | Lettau | Applicant |
| US7343565(B2) | 2008-03-01 | Ying et al. | Applicant |
| USD565581(S) | 2008-04-01 | Gunn et al. | Applicant |
| US7405537(B2) | 2008-07-01 | Hoffman et al. | Applicant |
| USD574842(S) | 2008-08-01 | Kwag et al. | Applicant |
| USD575302(S) | 2008-08-01 | Millar et al. | Applicant |
| US7421321(B2) | 2008-09-01 | Breed et al. | Applicant |
| USD578134(S) | 2008-10-01 | Jasinski | Applicant |
| USD579946(S) | 2008-11-01 | Lee et al. | Applicant |
| US7457693(B2) | 2008-11-01 | Olsen et al. | Applicant |
| US7460019(B2) | 2008-12-01 | Henderson | Applicant |
| US7463951(B2) | 2008-12-01 | Ampunan et al. | Applicant |
| US7480546(B2) | 2009-01-01 | Kamdar et al. | Applicant |
| USD586355(S) | 2009-02-01 | Mori et al. | Applicant |
| US7499714(B2) | 2009-03-01 | Ki | Applicant |
| USD592223(S) | 2009-05-01 | Neuhaus | Applicant |
| USD593110(S) | 2009-05-01 | Danton | Applicant |
| USD593111(S) | 2009-05-01 | Danton | Applicant |
| USD594465(S) | 2009-06-01 | Hong et al. | Applicant |
| USD594468(S) | 2009-06-01 | Bamford et al. | Applicant |
| US7602388(B2) | 2009-10-01 | Plut | Applicant |
| USD605657(S) | 2009-12-01 | Danton | Applicant |
| USD607464(S) | 2010-01-01 | Tang et al. | Applicant |
| USD608366(S) | 2010-01-01 | Matas | Applicant |
| USD611056(S) | 2010-03-01 | Langlois et al. | Applicant |
| USD618249(S) | 2010-06-01 | Ahn et al. | Applicant |
| USD618696(S) | 2010-06-01 | Woods et al. | Applicant |
| USD618700(S) | 2010-06-01 | Song | Applicant |
| USD618702(S) | 2010-06-01 | Lee | Applicant |
| USD621849(S) | 2010-08-01 | Anzures et al. | Applicant |
| USD623555(S) | 2010-09-01 | Reithlingshoefer et al. | Applicant |
| USD624556(S) | 2010-09-01 | Chaudhri | Applicant |
| US7802722(B1) | 2010-09-01 | Papierniak et al. | Applicant |
| USD625312(S) | 2010-10-01 | Jewitt et al. | Applicant |
| USD631889(S) | 2011-02-01 | Vance et al. | Applicant |
| USD642194(S) | 2011-07-01 | Kozlowski et al. | Applicant |
| USD642589(S) | 2011-08-01 | Kozlowski et al. | Applicant |
| USD645051(S) | 2011-09-01 | Kozlowski et al. | Applicant |
| US2002/0055861(A1) | 2002-05-01 | King et al. | Applicant |
| US2002/0096561(A1) | 2002-07-01 | Sullivan | Examiner |
| US2002/0184653(A1) | 2002-12-01 | Pierce et al. | Examiner |
| US2003/0088347(A1) | 2003-05-01 | Ames | Examiner |
| US2004/0100479(A1) | 2004-05-01 | Nakano et al. | Applicant |
| US2004/0111195(A1) | 2004-06-01 | Vries et al. | Applicant |
| US2004/0192336(A1) | 2004-09-01 | Walby | Applicant |
| US2004/0203850(A1) | 2004-10-01 | Oesterling | Applicant |
| US2004/0221239(A1) | 2004-11-01 | Hachigian et al. | Applicant |
| US2005/0027438(A1) | 2005-02-01 | Rockett et al. | Applicant |
| US2005/0091272(A1) | 2005-04-01 | Smith et al. | Applicant |
| US2005/0197771(A1) | 2005-09-01 | Seick et al. | Applicant |
| US2006/0022846(A1) | 2006-02-01 | Tummala | Applicant |
| US2006/0123360(A1) | 2006-06-01 | Anwar et al. | Applicant |
| US2006/0245570(A1) | 2006-11-01 | Pfleging et al. | Applicant |
| US2006/0291633(A1) | 2006-12-01 | Glaza et al. | Applicant |
| US2007/0011278(A1) | 2007-01-01 | Nou | Applicant |
| US2007/0033540(A1) | 2007-02-01 | Bridges et al. | Applicant |
| US2007/0066276(A1) | 2007-03-01 | Kuz et al. | Applicant |
| US2007/0072625(A1) | 2007-03-01 | Fournier et al. | Applicant |
| US2007/0088473(A1) | 2007-04-01 | Moon et al. | Applicant |
| US2007/0122026(A1) | 2007-05-01 | Ersue et al. | Applicant |
| US2007/0139182(A1) | 2007-06-01 | O'Connor et al. | Applicant |
| US2007/0142026(A1) | 2007-06-01 | Kuz et al. | Applicant |
| US2007/0167147(A1) | 2007-07-01 | Krasner et al. | Applicant |
| US2007/0185728(A1) | 2007-08-01 | Schwarz et al. | Applicant |
| US2007/0240079(A1) | 2007-10-01 | Flynt et al. | Applicant |
| US2007/0244628(A1) | 2007-10-01 | Rockett et al. | Applicant |
| US2007/0252689(A1) | 2007-11-01 | Rothschild | Applicant |
| US2007/0298765(A1) | 2007-12-01 | Dickinson et al. | Applicant |
| US2008/0004790(A1) | 2008-01-01 | Ames | Applicant |
| US2008/0014908(A1) | 2008-01-01 | Vasant | Applicant |
| US2008/0119203(A1) | 2008-05-01 | Shalmon et al. | Applicant |
| US2008/0140287(A1) | 2008-06-01 | Yang et al. | Applicant |
| US2008/0215240(A1) | 2008-09-01 | Howard et al. | Applicant |
| US2008/0261554(A1) | 2008-10-01 | Keller et al. | Applicant |
| US2008/0319665(A1) | 2008-12-01 | Berkobin et al. | Applicant |
| US2009/0002145(A1) | 2009-01-01 | Berry et al. | Applicant |
| US2009/0072995(A1) | 2009-03-01 | Thomas et al. | Applicant |
| US2009/0093236(A1) | 2009-04-01 | Balan et al. | Applicant |
| US2009/0125178(A1) | 2009-05-01 | Wilson | Applicant |
| US2009/0233572(A1) | 2009-09-01 | Basir | Applicant |
| US2010/0332133(A1) | 2010-12-01 | Harris et al. | Examiner |
| EP1320004(A1) | 2003-06-01 | Applicant |
Non-Patent Literature (35)
- BMW Assist™ Safety & Convenience Services © 2008 BMW of North America, LLC., 16 pages.Applicant
- Allstate Motor Club Launches Roadside Assistance Mobile App for iPhone and BlackBerry Users, Oct. 27, 2009; http://money.cnn.com/news/newsfeeds/articles/prnewswire/2009102711, 2 pages.Applicant
- TMC News, ATX Launches Enhanced Automatic Collision Notification for BMW, Jan. 11, 2009, http://tmcnet.com/usubmit/2009/01/11/3905139.htm, 4 pages.Applicant
- Automotive Fleet, Aug. 2009, vol. 48, No. 9, Charging for Preventable Accidents: What's the Payoff?, Grace Lauron, 4 pages.Applicant
- Automotive Fleet, May 2009, Bright Ideas Energize Fleet Management, Cindy Brauer and Thi Dao, 5 pages.Applicant
- Automotive Fleet, Sep. 2009 vol. 48 No. 10, DWT Proven to Increase Accidents, Grace Lauron, 5 pages.Applicant
- Motorola Demonstrates New Communications System Available in BMW's Global 2005 Model Year Vehicle Line, http://www.virtualizationconference.com/49572/print, 2 pages, retrieved on Feb. 6, 2009.Applicant
- BMW Assist, Safety & Convenience Services © 2006 BMW of North America, LLC, 16 pages.Applicant
- Automotive Fleet, Emkay Partners With Networkcar to Launch New Networkfleet Telematics Solution, Apr. 29, 2008, © 2009 Automotive Fleet, 1 page.Applicant
- Geotab Management by Measurement, Geotab for Insurance Companies © 2008, 1 page.Applicant
- CIO, High-tech Cars: The Coolest Automotive Technologies, Denise Dubie, Network World, Oct. 5, 2008, http://www.cio.com/article/print/452913, retrieved on Feb. 6, 2009, 2 pages.Applicant
- Inrix News, Inrix Real-Time Traffic Now Available on Over 75 Navigation and Mobile Devices, Jul. 30, 2007, http://www.inrix.com/news—75Devices—30July2007.asp, retrieved Feb. 6, 2009, 1 page.Applicant
- ABIresearch, Wireless Connectivity to the Automobile Is Hindered by Lack of Standards and Interoperability, Jul. 31, 2007, http://www.abiresearch.com/abiprdisplay.jsp?pressid=894, retrieved on Feb. 6, 2009, 1 page.Applicant
- When Accidents Happen, Nationwide Mobile App for IPhone is on Your Side, Melanie Broemsen, May 10, 2009, http://www.articlesbase.com/print/909297, retrieved on Jun. 23, 2009, 1 page.Applicant
- Diagnostic Trouble Codes (DTCs) Powertrain Codes for OBD II (OBD-2) equipped GM vehicles, compiled by Anthony W. Haukap; http://myweb.accessus.net/˜090/dtocbd2p.html; retrieved on Jul. 20, 2009, 20 pages.Applicant
- Automotive Fleet, OnStar Receives Honors at Telematics Update Awards © 2009 Automotive Fleet, http://www.automotive-fleet.com/News/Print/Story/2008/051/OnStar Receives, retrieved on Feb. 6, 2009, 1 page.Applicant
- Real time traffic broadcast to debut in Australia, http://www.gpsbusinessnews.com, retrieved Feb. 6, 2009 1 page.Applicant
- ABIresearch, In-Vehicle Infotainment Storage and Networking, Hard Disks, Flash Memory, USB, SD, Bluetooth, UWB, iPod Kits and Other Technologies, http://www.abiresearch.com/producs/market—research/In-Vehicle—Infotainment, retrieved on Feb. 6, 2009, 2 pages.Applicant
- TechWorld, Pimp your ride: Cool car technology, Denise Dubie (Network World) Jul. 10, 2008; http://www.techworld.com/article/262977/pimp—your—ride—cool—car, retrieved on Feb. 6, 2009, 3 pages.Applicant
- Maya Software Technologies, White Paper, Automotive Telematics—Market Overview and Security Considerations © 2001, 12 pages.Applicant
- Intomobile, Volkswagen Launches iPhone Optimized Website Featuring Access to Emergency Roadside Assistance, http://www.intomobile.com/2009/03/30/volkswagen-launches-iPhone-optimized-website-featuring-access, retrieved on Jun. 23, 2009, 3 pages.Applicant
- RepairPal for iPhone, http://repairpal.com/mobile, retrieved Feb. 2, 2009, 13 pages.Applicant
- TradeVibes, The RepairPal iPhone App is Available! © 2007-2008 Mill River Labs, www.tradevibes.com/news/view/repairpal?article=86228, retrieved on Feb. 2, 2009, 1 page.Applicant
- übergizmo™, RepairPal: Roadside Assistance from the iPhone, posted Jan. 22, 2009, http://www.ubergizmo.com/15/archives/2009/01/repairpal—roadside—assistance, retrieved on Feb. 2, 2009, 1 page.Applicant
- Automotive Fleet, Sep. 2009 vol. 48 No. 10, 10 Recommendations: What Drivers Should Do After a Fleet Accident, Mike Antich, 4 pages.Applicant
- Non-Final Office Action in related case U.S. Appl. No. 12/859,627 mailed Jul. 25, 2012.Applicant
- U.S. Appl. No. 29/396,366, filed Jun. 29, 2011.Applicant
- U.S. Copyright Registration No. TX 7-150-082, “Mini Road Assist”, registered on Mar. 19, 2010.Applicant
- U.S. Copyright Registration No. TX 7-329-434, “Mini Road Assist”, registered on Mar. 19, 2010.Applicant
- U.S. Copyright Registration No. TX 7-150-080, “Mini Road Assist”, registered Mar. 29, 2010.Applicant
- U.S. Copyright Registration No. TX 7-195-526, “Allstate Motor Club Roadside Assistance”, registered Mar. 30, 2010.Applicant
- U.S. Copyright Registration No. TX 7-229-997, “Allstate Motor Club Roadside Assistance”, registered Mar. 19, 2010.Applicant
- U.S. Copyright Registration No. TX 7-150-076, “Allstate Motor Club Roadside Assistance”, registered Mar. 26, 2010.Applicant
- Automotive Fleet/2009 NAFA Planning Guide, NAFA 2009 Institute & Expo Advanced Planning Guide, 2 pages.Applicant
- Final Office Action in related case U.S. Appl. No. 12/859,627 mailed Jan. 15, 2013.Applicant