Patent Grant
10586288
Various aspects of the disclosure relate to risk unit based insurance systems for determining and implementing risk unit based insurance policies. More specifically, aspects of the disclosure relate to determining a risk unit, providing a plurality of risk units to a user, receiving and analyzing various driver data, vehicle data, and/or driving trip data, determining a consumption rate of risk units (or other units within an account) and reducing a balance in a risk unit account based on the consumption rate in accordance with risk unit based insurance policies.
Vehicle insurance policies are generally purchased by insurance customers from various insurance providers. Conventional policies generally provide coverage to the user for a term of the policy based on payment of a premium associated with the policy. Such term based policies might not account for driving behaviors, environmental conditions, or the like. Rather, coverage may be provided for the term, regardless of how, where, when, etc. the driver operates the vehicle.
Many vehicles include sensors and internal computer systems designed to store and monitor driving data, vehicle operation data, driving conditions, and driving functions. Many vehicles also include one or more communication systems designed to send and receive information from inside or outside the vehicle. Such information can include, for example, vehicle operational data, driving conditions, and communications from other vehicles or systems.
The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosure. The summary is not an extensive overview of the disclosure. It is neither intended to identify key or critical elements of the disclosure nor to delineate the scope of the disclosure. The following summary merely presents some concepts of the disclosure in a simplified form as a prelude to the description below.
Aspects of the disclosure relate to methods, computer-readable media, and apparatuses for determining and implementing risk unit based insurance policies. In some arrangements, a user may receive a plurality of risk units associated with an insurance policy, such as an auto insurance policy. The risk units may be stored in a risk unit account associated with the user, the vehicle, etc. During operation of the vehicle, sensor data may be received. The sensor data may provide information associated with driving behaviors of the user, environmental conditions in which the vehicle is being operated, and the like. A consumption rate of the risk units may be determined based, at least in part, on the received sensor data. Consumption rate may also be based on additional factors, such as driving experience, policy coverage, vehicle features, and the like. In some examples, the consumption rate may be based on a combination of factors or on only sensor data factors or only other factors not determined based on sensor data. Accordingly, as the vehicle is operated, a number or balance of risk units in the risk unit account may be reduced based on the determined consumption rate.
In some examples, a determination may be made as to whether a number or balance of risk units in the risk unit account is below a predetermined threshold. If so, a notification may be transmitted to the user. In some arrangements, the notification may include a request for user input to purchase additional risk units (e.g., a request for user input identifying a number of additional risk units to purchase, payment information, etc.). In some examples, upon determining that the balance of risk units in the risk unit account is below the predetermined threshold, a predetermined number of risk units may be added to the risk unit account and a cost associated with purchase of the additional risk units may be paid automatically using predetermined or prestored payment information.
Other features and advantages of the disclosure will be apparent from the additional description provided herein.
A more complete understanding of the present invention and the advantages thereof may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features, and wherein:
In the following description of the various embodiments, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration, various embodiments of the disclosure that may be practiced. It is to be understood that other embodiments may be utilized.
As will be appreciated by one of skill in the art upon reading the following disclosure, various aspects described herein may be embodied as a method, a computer system, or a computer program product. Accordingly, those aspects may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, such aspects may take the form of a computer program product stored by one or more computer-readable storage media having computer-readable program code, or instructions, embodied in or on the storage media. Any suitable computer-readable storage media may be utilized, including hard disks, CD-ROMs, optical storage devices, magnetic storage devices, and/or any combination thereof. In addition, various signals representing data or events as described herein may be transferred between a source and a destination in the form of electromagnetic waves traveling through signal-conducting media such as metal wires, optical fibers, and/or wireless transmission media (e.g., air and/or space).
Input/Output (I/O) 109 may include a microphone, keypad, touch screen, and/or stylus through which a user of the computing device 101 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, audiovisual and/or graphical output. Software may be stored within memory 115 and/or storage to provide instructions to processor 103 for enabling device 101 to perform various actions. For example, memory 115 may store software used by the device 101, such as an operating system 117, application programs 119, and an associated internal database 121. The various hardware memory units in memory 115 may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Certain devices and systems within risk unit based insurance systems may have minimum hardware requirements in order to support sufficient storage capacity, processing capacity, analysis capacity, network communication, etc. For instance, in some embodiments, one or more nonvolatile hardware memory units having a minimum size (e.g., at least 1 gigabyte (GB), 2 GB, 5 GB, etc.), and/or one or more volatile hardware memory units having a minimum size (e.g., 256 megabytes (MB), 512 MB, 1 GB, etc.) may be used in a device 101 (e.g., a personal mobile device 101, vehicle-based device 101, insurance system server 101, etc.), in order to collect and analyze driver data, vehicle data, and/or driving trip data, determine risk unit based insurance policy parameters, determine rate at which risk units are consumed during operation of a vehicle, etc., using the various devices of the risk unit based insurance systems. Memory 115 also may include one or more physical persistent memory devices and/or one or more non-persistent memory devices. Memory 115 may include, but is not limited to, random access memory (RAM) 105, read only memory (ROM) 107, 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 processor 103.
Processor 103 may include a single central processing unit (CPU), which may be a single-core or multi-core processor (e.g., dual-core, quad-core, etc.), or may include multiple CPUs. Processor(s) 103 may have various bit sizes (e.g., 16-bit, 32-bit, 64-bit, 96-bit, 128-bit, etc.) and various processor speeds (ranging from 100 MHz to 5 Ghz or faster). Processor(s) 103 and its associated components may allow the system 101 to execute a series of computer-readable instructions, for example, determine a risk unit balance in a risk unit account, to receive and analyze driver data, vehicle data, and/or driving trip data, determine a rate at which risk units are consumed (e.g., based on analyzed driver data, vehicle data, external data, or the like), and/or automatically refill a risk unit account balance upon determining that the balance has reached a predetermined threshold.
The computing device (e.g., a personal mobile device, vehicle-based system, insurance system server, etc.) may operate in a networked environment 100 supporting connections to one or more remote computers, such as terminals 141, 151, and 161. Such terminals may be personal computers or servers 141 (e.g., home computers, laptops, web servers, database servers), mobile communication devices 151 (e.g., mobile phones, tablet computers, etc.), vehicle-based computing systems 161 (e.g., on-board vehicle systems, telematics devices, mobile phones or other personal mobile devices within vehicles), and the like, each of which may include some or all of the elements described above with respect to the computing device 101. The network connections depicted in
Also illustrated in
As discussed below, the data transferred to and from various devices in a risk unit based insurance system 100 may include secure and sensitive data, such as confidential vehicle operation data, insurance policy data, and confidential user data from drivers and passengers in vehicles. Therefore, it may be desirable to protect transmissions of such data by using secure network protocols and encryption, and also to protect the integrity of the data when stored on the various devices within a personalized insurance system, such as personal mobile devices, vehicle-based devices, insurance servers, external data source servers, or other computing devices in the system 100, by using the security and integration layer 160 to authenticate users and restrict access to unknown or unauthorized users. In various implementations, security and integration layer 160 may provide, for example, a file-based integration scheme or a service-based integration scheme for transmitting data between the various devices in an electronic display system 100. Data may be transmitted through the security and integration layer 160, using various network communication protocols. Secure data transmission protocols and/or encryption may be used in file transfers to protect to integrity of the data, for example, File Transfer Protocol (FTP), Secure File Transfer Protocol (SFTP), and/or Pretty Good Privacy (PGP) encryption. In other examples, one or more web services may be implemented within the various devices 101 in the system 100 and/or the security and integration layer 160. The web services may be accessed by authorized external devices and users to support input, extraction, and manipulation of the data (e.g., vehicle data, driver data, driving trip data, etc.) between the various devices 101 in the system 100. Web services built to support a personalized display system may be cross-domain and/or cross-platform, and may be built for enterprise use. Such web services may be developed in accordance with various web service standards, such as the Web Service Interoperability (WS-I) guidelines. In some examples, a driver data, vehicle data, and/or driving trip data analysis web service, a risk unit based insurance policy determination or offer web service, or the like, may be implemented in the security and integration layer 160 using the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocol to provide secure connections between servers 101 and various clients 141, 151, and 161. SSL or TLS may use HTTP or HTTPS to provide authentication and confidentiality. In other examples, such web services may be implemented using the WS-Security standard, which provides for secure SOAP messages using XML encryption. In still other examples, the security and integration layer 160 may include specialized hardware for providing secure web services. For example, secure network appliances in the security and integration layer 160 may include built-in features such as hardware-accelerated SSL and HTTPS, WS-Security, and firewalls. Such specialized hardware may be installed and configured in the security and integration layer 160 in front of the web servers, so that any external devices may communicate directly with the specialized hardware.
Although not shown in
It will be appreciated that the network connections shown are illustrative and other means of establishing a communications link between the computers may be used. The existence of any of various network protocols such as TCP/IP, Ethernet, FTP, HTTP and the like, and of various wireless communication technologies such as GSM, CDMA, WiFi, and WiMAX, is presumed, and the various computing devices in risk unit based insurance system components described herein may be configured to communicate using any of these network protocols or technologies.
Additionally, one or more application programs 119 may be used by the various computing devices 101 within a risk unit based insurance system 100 (e.g., vehicle data, driver data, and/or driving trip data analysis software applications, insurance parameter determination software applications, risk unit account applications, etc.), including computer executable instructions for receiving and analyzing various driver data, vehicle data, and/or driving trip data, determining parameters for risk unit insurance policies, presenting risk unit based insurance policies via the devices in the risk unit based insurance system, determining a rate at which risk units are consumed during operation of a vehicle, and evaluating and/or automatically refilling a balance of a risk unit account using the devices of the risk unit based insurance systems.
The risk unit based insurance system 200 may include one or more modules that may include hardware and/or software configured to perform various functions within the system 200. The one or more modules may be separate, physical devices or, in other examples, one or more modules may be part of the same physical device.
The risk unit based insurance system may include a risk unit module 202. The risk unit module 202 may be configured to determine a cost to insure an average user for a predetermined period of time. For instance, the risk unit module 202 may receive data, such as insurance data from insurance data store 204, locality data from locality data store 206, as well as other data (from data stores not shown that may be internal to the entity 201 or external to the entity 201), and determine, based on the received data, the cost to insure an average user over a predetermined period of time (e.g., one month, one week, one day, one year, or the like). This cost may be considered equivalent to one risk unit. Further, a cost to the user or insurance policy holder to purchase a risk unit may be determined by the system. This cost may be different from the cost forming the risk unit and may be determined on a fixed date. The cost to the user may then be revised at a second date (e.g., monthly, annually, etc.). Accordingly, insurance may be provided to one or more users based on risk units, as will be discussed more fully herein.
The risk unit based insurance system 200 may further include a policy module 208. The policy module 208 may generate and/or store insurance policies using risk units, as well as insurance policy information or factors, such as vehicle information, driving record/experience, policy limits, deductibles, etc. That is, a user may be insured through a policy that provides a number of risk units for a particular cost (e.g., insurance premium). The risk units may then be consumed by the user as, for example, the user drives or operates his or her vehicle. The risk units may be consumed based on sensor data-focused factors, such as time elapsed, driving habits of the user, environmental conditions in which the user operates the vehicle, vehicle parameters (such as year, make, model, features, specifications, etc.), condition or performance of the vehicle (e.g., based on sensor data), and the like, as well as traditional policy factors, such as driving experience, driving record, credit variables, policy coverage, deductible, policy limits, familiarity of the driver with the vehicle or surroundings, and the like. In some examples, one policy parameter may include a level of coverage. For instance, risk units may be purchased at various levels with each level providing a different level of coverage, as will be discussed more fully herein. Additionally or alternatively, the consumption rate may reflect different levels of coverage.
The insurance policies based on risk units may further include a risk unit account stored in risk unit account module 210. The risk unit account module 210 may include one or more accounts associated with one or more users (e.g., users having risk unit based insurance policies), vehicles (e.g., vehicles associated with a risk unit based insurance policy), or the like. The accounts may include information associated with a user such as name, address, contact information, and the like, as well as information associated with the vehicle, such as vehicle identification number, make, model, year, etc. Further, the accounts may include a number of risk units associated with or available to the user or account holder, associated with the vehicle, etc. Accordingly, if a user has a risk unit based insurance policy that includes the purchase of 100 risk units, the user account will show, at the purchase, 100 risk units. As the risk units are consumed (e.g., by the user operating the vehicle, or the like) a balance of risk units in the account may be reduced. In some examples, the balance of risk units in an account may be displayed to the user via a computing device, such as one or more of computing devices 212a-212f. For instance, the risk unit account balance may be displayed via an application (e.g., online or mobile application) on a smartphone 212a, personal digital assistant (PDA) 212b, tablet 212c, cell phone 212d, or other computing device 212e. In some examples, the risk unit account balance may be displayed to a user on a vehicle display 212f. In addition to display of the account balance, various other account details may be displayed as desired.
In some arrangements, the risk unit account may include units of another type (e.g., other than risk units). For instance, the risk unit account may include an amount or balance of funds or money. The balance of funds may be reduced based on operation of the vehicle, as discussed above. In some examples, the risk units may be converted to funds in order to facilitate this reduction of balance (e.g., the consumption rate of units based on operation of the vehicle may be determined in risk units and then converted to funds in order to reduce the balance in the account appropriately). In other examples, the consumption rate may be determined in monetary units and the balance reduced as appropriate. Although various arrangements discussed herein will be described in terms of consumption rate being determined in risk units and a balance of an account including a number of risk units reduced accordingly, various other units may be used (e.g., monetary units) without departing from the invention.
The risk unit based insurance system 200 may further include a risk unit consumption rate module 214. The risk unit consumption rate module 214 may include hardware and/or software configured to determine and/or implement a consumption rate of risk units due to operation of the vehicle (e.g., as the user operates the vehicle, the number or balance of risk units in the risk unit account is reduced based on a determined consumption rate, thereby depleting the balance associated with the policy. Once the balance of risk units reaches a predetermined threshold, the number of risk units may be replenished, akin to renewal of a conventional insurance policy). As discussed above, the consumption rate may be determined in risk units, monetary units or other units, as desired.
As discussed above, the rate at which risk units are consumed by a user (e.g., by a user's operation of a vehicle) may be based on a variety of factors, such as personal information of the user, driving habits or behaviors of the user, environmental conditions, locality or geographic conditions, types of road being travelled, traditional policy factors, coverage, vehicle features or operation, and the like. Various algorithms may be used to determine the consumption rate. For example, Equation 1 is one example that may be used to determine consumption rate based on sensor data-focused factors may include:
RC1=L1×R1×T1×B1×E1, where Equation 1:
Equation 2 is another example that may be used to determine consumption rate based on sensor data-focused factors, as well as traditional policy factors, may include:
RC2=O2×P2×V2×C2×L2×R2×T2×B2×E2, where Equation 2:
In addition, either Equation 1 or Equation 2 may further include an expenses factor. In some examples, an expenses value may be added to the result of Equation 1 or Equation 2 in order to determine the consumption rate.
Further, although Equation 1 and Equation 2 are provided as examples for determining consumption rate, various other equations and/or algorithms may be used without departing for the invention. For instance, one or more factors may be removed from the equation to determine consumption rate. Additionally or alternatively, other factors may be included in the equations, without departing from the invention.
Accordingly, one or more sensors 216 may be used to obtain data that may be used to determine the consumption rate for the user. For instance, the one or more sensors may include sensors to detect driving behaviors of the user, such as hard braking, speeding, and the like. In another example, one or more sensors may be used to detect environmental conditions such as precipitation, humidity, cloud cover, or the like. In still another example, one or more sensors may be used to determine road conditions or to obtain information from outside sources (e.g., external databases, or the like) regarding traffic conditions, types of road (e.g., two-lane road, four-lane road), speed limit of the road, or the like. The data from one or more sensors 216, which may include data from combinations of different types of sensors, may be used by the risk unit consumption rate module 214 to determine a risk unit consumption rate for the user.
In examples in which the consumption rate is determined based on traditional policy factors (either in combination with sensor data-focused factors or alone) the traditional policy factors, such as driving record, credit information, driving experience, vehicle features and/or specifications, coverages, deductibles, policy limits, etc. may be obtained from, for example, policy module 208. In some examples, the risk unit consumption rate may be determined or calculated for a particular trip. Additionally or alternatively, the consumption rate may be calculated or determined in real-time or near real-time, such that the rate may change as the user's driving behavior changes, as the type of road changes, as the environmental conditions change, or the like. Thus, for example, if a user is driving at speed higher than the speed limit and it is raining, the consumption rate may be higher than if the user is driving at the speed limit and/or there is no precipitation. This is merely one example of how consumption rate may change based on received sensor data and should not be viewed as limiting the disclosure to only this example. Rather, various other changes in received sensor data may be used to modify or alter the risk unit consumption rate for the user.
Similar to the risk unit account information, the risk unit consumption rate may be displayed to a user, such as via one or more computing devices 212a-212f. In some examples, the risk unit consumption rate module 214 may generate and/or display to a user suggestions for improving the consumption rate. For instance, the system may generate an alternate route that has been determined to be safer than the user's current route and, thus, by taking the alternate route, the consumption rate may be reduced. In another example, a user may be driving faster than a posted speed limit. The system may generate a notice to display to the user (e.g., via a computing device 212a-212f) indicating that, by slowing down, the user's consumption rate may be reduced. These are merely some examples of messages that may be displayed in order to aid the user in reducing the consumption rate of the risk units. However, various other suggestions or driving behavior modifications may be generated and provided to the user without departing from the invention.
The risk unit based insurance system 200 may further include a risk unit marketplace 218. The risk unit marketplace 218 may be connected to or in communication with various other modules within the system 200. In some examples, the risk unit marketplace may be used to refill a user's risk unit account. For instance, upon the user reaching a predetermined threshold within the risk unit account of the user (e.g., the balance of risk units within the account reaches a certain threshold) the user may be notified that the balance of risk units in the account is low and may offer one or more options for purchasing additional risk units or otherwise increasing the balance of risk units in the account.
For example, in some instances, upon reaching the threshold number of risk units within the account, a notification may be displayed to the user (e.g., via one or more of computing devices 212a-212f) indicating that the balance is low and offering additional risk units for sale. In some examples, the user may store credit card or other payment information (e.g., account information, debit card information, electronic funds transfer information, and the like) in the system (e.g., within the risk unit marketplace 218) such that, upon receiving the notification, the user may select a “purchase” option and a predetermined number of risk units may be purchased by the user and charged to the stored payment information. In another example, the user may select an automatic refill option. In such arrangements, a user may input payment information (e.g., credit card information, debit card information, checking or other account information, electronic funds transfer information, and the like) and may identify a predetermined threshold below which the system may automatically purchase additional risk units. These and various other arrangements will be discussed more fully below.
The risk unit marketplace 218 may also provide risk units for sale to other users or insurance providers. For instance, a user may obtain insurance through a different insurance provider but the risk units may be common units among a plurality of insurance providers. Accordingly, users having insurance policies with other providers may purchase risk units from the risk unit marketplace 218 and may have the risk units placed in an account associated with the policy provided by or associated with the other insurance provider. In some examples, entity 201 may charge a service fee or surcharge for purchase of risk units for use with a policy provided by another insurance carrier.
Vehicle 310 in the system 300 may be, for example, an automobile, a motorcycle, a scooter, a bus, a recreational vehicle, a boat, or other vehicle for which vehicle data, location data, driver data (or operator data), operational data and/or other driving data (e.g., location data, time data, weather data, etc.) may be collected and analyzed. The vehicle 310 includes vehicle operation sensor 311 (similar to one or more of sensors 216a-216c of
Additional sensors 311 may detect and store the external driving conditions, for example, external temperature, rain, snow, light levels, and sun position for driver visibility. For example, external cameras and proximity sensors 311 may detect other nearby vehicles, vehicle spacing, traffic levels, road conditions, traffic obstructions, animals, cyclists, pedestrians, and other conditions that may factor into a driving data/behavior analysis. Sensor 311 also may detect and store data relating to moving violations and the observance of traffic signals and signs by the vehicle 310. Additional sensors 311 may detect and store data relating to the maintenance of the vehicle 310, such as the engine status, oil level, engine coolant temperature, odometer reading, the level of fuel in the fuel tank, engine revolutions per minute (RPMs), software upgrades, and/or tire pressure.
Vehicles sensor 311 also may include cameras and/or proximity sensors capable of recording additional conditions inside or outside of the vehicle 310. For example, internal cameras may detect conditions such as the number of the passengers and the types of passengers (e.g. adults, children, teenagers, pets, etc.) in the vehicles, and potential sources of driver distraction within the vehicle (e.g., pets, phone usage, and unsecured objects in the vehicle). Sensor 311 also may be configured to collect data identifying a current driver from among a number of different possible drivers, for example, based on driver's seat and mirror positioning, driving times and routes, radio usage, etc. Voice/sound data along with directional data also may be used to determine a seating position within a vehicle 310. Sensor 311 also may be configured to collect data relating to a driver's movements or the condition of a driver. For example, vehicle 310 may include sensors that monitor a driver's movements, such as the driver's eye position and/or head position, etc. Additional sensors 311 may collect data regarding the physical or mental state of the driver, such as fatigue or intoxication. The condition of the driver may be determined through the movements of the driver or through other sensors, for example, sensors that detect the content of alcohol in the air or blood alcohol content of the driver, such as a breathalyzer, along with other biometric sensors.
Certain vehicle sensors 311 also may collect information regarding the driver's route choice, whether the driver follows a given route, and to classify the type of trip (e.g. commute, errand, new route, etc.) and type of driving (e.g., continuous driving, parking, stop-and-go traffic, etc.). In certain embodiments, sensors and/or cameras 311 may determine when and how often the vehicle 310 stays in a single lane or strays into other lane. A Global Positioning System (GPS), locational sensors positioned inside the vehicle 310, and/or locational sensors or devices external to the vehicle 310 may be used to determine the route, speed, lane position, road-type (e.g. highway, entrance/exit ramp, residential area, etc.) and other vehicle position/location data.
The data collected by vehicle sensor 311 may be stored and/or analyzed within the vehicle 310, such as for example a driving analysis computer 314 integrated into the vehicle, and/or may be transmitted to one or more external devices. For example, as shown in
As shown in
In the example shown in
The system 300 in
Mobile device 330 may include a network interface 321, which may include various network interface hardware (e.g., adapters, modems, wireless transceivers, etc.) and software components to enable mobile device 330 to communicate with insurance system server 350, vehicle 310, and various other external computing devices. One or more specialized software applications, such as a driving analysis application 334 and/or a risk unit based insurance application 335 may be stored in the memory of the mobile device 330. The driving analysis application 334 and risk unit based insurance application 335 may be received via network interface 321 from the insurance server 350, vehicle 310, or other application providers (e.g., application stores). As discussed below, the driving analysis application 334 and risk unit based insurance application 335 may or may not include various user interface screens, and may be configured to run as user-initiated applications or as background applications. The memory of the mobile device 330 also may include databases configured to receive and store vehicle data, driving data, driving trip data, and the like, associated with one or more drivers and/or vehicles.
Like the vehicle-based computing devices in vehicle 310, mobile device 330 also may include various components configured to generate and/or receive vehicle data, driver data, and driving data or other operational data. For example, using data from the GPS receiver 333, a driving analysis software application 334 may be able to identify starting and stopping points of driving trips, determine driving speeds, times, routes, and the like. Additional components of mobile device 330 may be used to generate or receive driving data for the driving data analysis application 334 and/or risk unit based insurance application 335, such as an accelerometer, compass, and various cameras and proximity sensors. As discussed below, these and other mobile device components may be used to receive, store, and output various user/driver data, to identify starting and stopping points and other characteristics of driving trips, to determine various driving data such as speeds, driving routes and times, acceleration, braking, and turning data, and other driving conditions and behaviors. In some implementations, the driving analysis software application 334 may store and analyze the data from various mobile device components, and the risk unit based insurance application 335 may use this data, alone or in any combination with other components or devices (e.g., insurance server 350), to determine and present insurance offers, insurance costs, and the like.
When mobile computing devices within vehicles are used to detect vehicle driving data and/or to receive vehicle driving data from vehicle sensors, such mobile computing devices 330 may store, analyze, and/or transmit the vehicle driver data (e.g., data identifying a current driver), driving data (e.g., speed data, acceleration, braking, and turning data, and any other vehicle sensor or operational data), and driving trip data (e.g., driving route, driving times, driving destinations, etc.), to one or more other devices. For example, mobile computing device 330 may transmit driver data, driving data and driving behaviors, and driving trip data directly to one or more insurance servers 350, and thus may be used in conjunction with or instead of telematics devices 313. Moreover, the processing components of the mobile computing device 330 may be used to identify vehicle drivers and passengers, analyze vehicle driving data, analyze driving trips, determine parameters related to aspects of risk unit based insurance policies, and perform other related functions. Therefore, in certain embodiments, mobile computing device 330 may be used in conjunction with, or in place of, the insurance system server 350.
Vehicle 310 may include driving analysis computer 314, which may be separate computing devices or may be integrated into one or more other components within the vehicle 310, such as the telematics device 313, autonomous driving systems, or the internal computing systems of vehicle 310. As discussed above, driving analysis computers 314 also may be implemented by computing devices independent from the vehicle 310, such as mobile computing device 330 of the drivers or passengers, or one or more separate computer systems (e.g., a user's home or office computer). In any of these examples, the driving analysis computer 314 may contain some or all of the hardware/software components as the computing device 101 depicted in
The system 300 also may include one or more insurance system servers 350, containing some or all of the hardware/software components as the computing device 101 depicted in
The insurance system server 350 may initiate communication with and/or retrieve driver data, vehicle data, and driving data from vehicle 310 wirelessly via telematics device 313, mobile device 330, or by way of separate computing systems over one or more computer networks (e.g., the Internet). Additionally, the insurance system server 350 may receive additional data from other third-party data sources, such as external traffic databases containing traffic data (e.g., amounts of traffic, average driving speed, traffic speed distribution, and numbers and types of accidents, etc.) at various times and locations, external weather databases containing weather data (e.g., rain, snow, sleet, and hail amounts, temperatures, wind, road conditions, visibility, etc.) at various times and locations, and other external data sources containing driving hazard data (e.g., road hazards, traffic accidents, downed trees, power outages, road construction zones, school zones, and natural disasters, etc.), route and navigation information, and insurance company databases containing insurance data (e.g., driver score, coverage amount, deductible amount, premium amount, insured status) for the vehicle, driver, and/or other nearby vehicles and drivers.
Data stored in the insurance database 352 may be organized in any of several different manners. For example, a driver table in database 352 may contain all of the driver data for drivers associated with the insurance provider (e.g., driver personal information, insurance account information, demographic information, accident histories, risk factors, driving scores and driving logs, etc.), a vehicle table may contain all of the vehicle data for vehicles associated with the insurance provider (e.g., vehicle identifiers, makes, models, years, accident histories, maintenance histories, travel logs, estimated repair costs and overall values, etc.), and a driving trip table may store all of the driving trip data for drivers and vehicles associated with the insurance provider (e.g., driving trip driver, vehicle driven, trip time, starting and ending points, route driven, etc.). Other tables in the database 352 may store additional data, including data types discussed above (e.g. traffic information, road-type and road condition information, weather data, insurance policy data, etc.). Additionally, one or more other databases of other insurance providers containing additional driver data and vehicle data may be accessed to retrieve such additional data.
The risk unit based insurance system 351 within the insurance system server 350 may be configured to retrieve data from the database 352, or may receive driver data, vehicle data, and driving trip directly from vehicle 310, mobile device 330, or other data sources, and may perform driving data analyses, determine insurance parameters for risk unit based insurance policies, and other related functions. The functions performed by the risk unit based insurance analysis system 351 may be performed by specialized hardware and/or software separate from the additional functionality of the insurance system server 350. Such functions may be similar to those of driving analysis module 314 of vehicle 310, and the driving analysis and risk unit based insurance applications 334 and 335 of mobile device 330, and further descriptions and examples of the algorithms, functions, and analyses that may be executed by the risk unit based insurance system 351 are described below, including in reference to
In various examples, the driving data and driving trip analyses and/or risk unit based insurance determinations may be performed entirely in the insurance system server 350, may be performed entirely in the vehicle-based driving analysis computing module 314, or may be performed entirely in the driving analysis and risk unit based insurance applications 334 and 335 of mobile device 330. In other examples, certain analyses of driver data, vehicle data, and driving trip data, and certain risk unit based insurance determinations may be performed by vehicle-based devices (e.g., within driving analysis module 314) or mobile device 330 (e.g., within applications 334 and 335), while other data analyses and risk unit based insurance determinations are performed by the risk unit based insurance system 351 at the insurance system server 350. For example, a vehicle-based driving analysis computer 314, or the hardware and software components of mobile device 330 may continuously receive and analyze driver data, vehicle data, driving trip data, and the like to determine certain events and characteristics (e.g., commencement of a driving trip, identification of a driver, determination of a driving route or intended destination, driving data and behaviors during driving trips, etc.), so that large amounts of data need not be transmitted to the insurance system server 350. However, for example, after driver, vehicle, and/or driving trip is determined by a vehicle-based device and/or mobile device, corresponding information may be transmitted to the insurance server 350 to perform insurance offer and cost determinations, determine consumption rate of risk units, generate one or more recommendations for reducing consumption rate, etc. which may be transmitted back to the vehicle-based device and/or personal mobile devices.
In step 402, a request is received to obtain a risk unit based insurance policy. The request may be received from a user and may be received, in some examples, via a computing device (e.g., mobile device, or the like). The request may include information associated with the user, such as name, contact information, vehicle information including make, model, year, vehicle identification number, and the like. In some examples, the request to obtain the risk unit based insurance policy may include a level of coverage. For instance, similar to conventional insurance policies, a user may select from different levels of protection (e.g., whether to include collision coverage, amount of coverage for personal property, and the like). Similarly, a user may select a level of risk unit on which the policy is based. In one example, three levels may be used with the highest level of risk unit providing the most coverage and, in some instances, having the highest cost (e.g., cost per risk unit) to the user. A second level would provide lower coverage at a lower cost and the third level may provide a lowest level of coverage at a lowest cost. In another example, different levels of coverage selected may be reflected in the consumption rate of the units. For instance, the consumption rate may vary based on a level of coverage selected. Although different levels of coverage may be available to a user, the levels offered may meet minimum standards for insurance coverage, such as those required by the state in which the user lives, or the like.
Further, although three levels of risk units are described in the above example, more or fewer levels of risk unit, and, accordingly, insurance coverage, may be provided without departing from the invention.
In step 404, a risk unit based insurance policy is generated for the user and a risk unit account is created for the user. The risk unit account may be associated with the user or the vehicle. That is, the risk unit based insurance policy may provide coverage for the vehicle, regardless of which user is operating the vehicle, or may provide coverage to any vehicle being operated by a particular user. Thus, in some examples, the user or operator of a vehicle may be identified (e.g., upon initiation of vehicle operation) in order to determine whether or what type of coverage to provide.
In step 406, a predetermined number of risk units is deposited into the account created. The predetermined number or risk units may be based on one or more policy parameters (e.g., term or length of policy), and/or one or more user preferences.
In step 408, data associated with the driving behaviors of the user and/or environmental conditions in which the vehicle is operating are received. As discussed above, the data may be received from one or more sensors associated with the vehicle, as well as various other sources, such as traffic, weather, road condition, etc. sources. As discussed herein, received data may include speed, braking habits of the user or operator, type of road(s) being travelled, time of day, level of traffic, precipitation, and the like.
Based on the data received, a consumption rate of risk units in the risk unit account may be determined in step 410. As discussed herein, the consumption rate may be higher based on various behaviors and/or conditions that are determined to include more risk to the user, vehicle, etc. For instance, if a user is driving at a rate of speed above the speed limit, the consumption rate may be higher than if the user was operating at a speed closer to the speed limit. In another example, the consumption rate may be determined to be lower if the user travels outside of rush hour, rather than during peak travel times. In still another example, the consumption rate may increase if data is received that it is raining or snowing on the route which the vehicle is travelling. As discussed above, consumption rate may also be based, at least in part, on traditional policy factors, such as driving experience, driving record, credit factors, coverages, deductibles, and the like. Data related to various behaviors and conditions and/or traditional policy data, may be combined to determine the consumption level in real-time or near real-time, as the user is operating the vehicle. Accordingly, the system may provide information associated with the consumption rate to the user. For instance, the vehicle display or mobile device of the user may display the current consumption rate. In another example, the display may include historical information associated with consumption rate for previous trips and/or a graphical display of previous and/or current consumption rates.
Field 508 indicates that data is being received. As discussed herein, data associated with one or more sensors detecting driving behaviors of the user, environmental conditions, and the like, may be received by the system and used to determine a current consumption rate. Field 508 provides an indication that data is currently being received. In the event of a communication disruption, field 508 may indicate that data is not being received or that an error has occurred. In some example situations of that nature, the system may apply the most recently determined consumption rate until data communication is restored and more current data is received by the system.
Field 510 provides the current calculated or determined consumption rate. As described herein, the consumption rate may be based on a variety of factors that may include driving behaviors, environmental conditions, and the like, as determined based on data received by the system. Field 512 provides a listing of historical consumption rate information that may be useful to the user in tracking consumption rate.
With further reference to
If, in step 414, the balance in the risk unit account is at or above the predetermined threshold, the process may return to step 408 to continue receiving data and determining consumption rate. If, in step 414, the balance is below the predetermined threshold, one or more refill options may be provided to the user in step 416. Refill options may include providing a notification to the user of the current balance and/or providing options for automatic refill, user requested refill, cancellation of policy, purchase of a new policy and associated risk units, and the like. Once the refill options are presented, the system may return to step 408 to continue receiving data, etc.
In step 604, a determination is made as to whether the account is set up for automatic refill. That is, the system may determine whether the user has preselected an option to automatically refill a balance in the account (e.g., by automatically purchasing additional risk units using pre-stored payment information). If so, the system may automatically purchase the predetermined number of units, charge any cost to the pre-stored payment information (e.g. credit card information, account information, debit card information, etc.), and deposit the risk units purchased in the account in step 606.
If, in step 604, it is determined that the account is not set for automatic refill, in step 608, the user may respond to the notification transmitted in step 602 with a request to refill the account balance. The request may include a number of units to purchase, payment information, risk unit account information, policy information, and the like. In step 610, the designated number of risk units may be purchased and deposited in the risk unit account.
Upon selection of yes option in 700a, interface 700b shown in
Upon selection of continue option, interface 700d in
User interface 700d further includes an option to select automatic refill. Indication of “yes” to automatic refill prompts the system to store the payment information provided in interface 700c and, upon the system determining that the balance of risk units is below the predetermined threshold (e.g., step 414 in
In step 804, one or more driving behavior or environmental condition modifications may be identified that may aid in reducing the risk unit consumption rate. For instance, if a user is driving on a road that is known as being in poor condition (e.g., potholes, poor lane markings, etc.), the system may indicate that, by changing the route to the destination, the user may reduce his or her consumption rate. In some examples, a recommended modification identified to aid in reducing risk unit consumption rate may include modifications to more traditional policy factors, such as policy coverage, deductibles and/or limits, vehicle operation and/or maintenance, vehicle features, and the like.
In some examples, the modifications to reduce consumption rate may be identified by comparing received data with a database storing known conditions, behaviors, roads, environmental factors, and the like, that are associated with a reduced consumption rate. The database may store information such as historical travel information, accident history information, accident probability information, etc. that may be collected based on insurance data received by the insurance provider. For instance, the data associated with current speed may be compared to a posted speed limit for the current road (as stored in the database or received from an outside source) and, if the current speed is higher than the posted speed limit, a modification to slow the speed of the vehicle in order to reduce consumption rate may be identified.
In another example, the received data may indicate that the current road is congested or is experiencing heavy traffic. The system may compare the current traffic information to levels of traffic that would result in a reduced consumption rate and may recommend modifying the route being travelled. In some examples, the suggested modification may include a suggested alternate route.
Various other driving behavior and/or environmental condition modifications may be identified based on the received data and/or historical data, stored data, and the like. The examples described herein are merely some examples and are not intended to limit the modifications or types of modifications identified by the system. Rather, various other modifications may be identified without departing from the invention.
In step 806, the identified modifications may be display to the user. For instance, one or more of the recommended modifications to reduce consumption rate may be displayed to the user via a computing device, such as a mobile device, vehicle display, or the like.
While the aspects described herein have been discussed with respect to specific examples including various modes of carrying out aspects of the disclosure, those skilled in the art will appreciate that there are numerous variations and permutations of the above described systems and techniques that fall within the spirit and scope of the invention.
This application is a continuation of and claims priority to co-pending U.S. application Ser. No. 15/170,084, filed Jun. 1, 2016, and entitled “Risk Unit Based Policies,” which is a divisional of and claims priority to U.S. application Ser. No. 14/607,662 (now U.S. Pat. No. 9,390,452), filed Jan. 28, 2015, and entitled “Risk Unit Based Policies,” which are incorporated herein by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5510765 | Madau | Apr 1996 | A |
| 5797134 | McMillan | Aug 1998 | A |
| 6556905 | Mittelsteadt et al. | Apr 2003 | B1 |
| 6868386 | Henderson et al. | Mar 2005 | B1 |
| 7117173 | Ambani | Oct 2006 | B1 |
| 7323970 | Murray et al. | Jan 2008 | B1 |
| 7865378 | Gay | Jan 2011 | B2 |
| 7890355 | Gay et al. | Feb 2011 | B2 |
| 7937278 | Cripe et al. | May 2011 | B1 |
| 7941258 | Mittelsteadt et al. | May 2011 | B1 |
| 7987103 | Gay et al. | Jul 2011 | B2 |
| 7991629 | Gay et al. | Aug 2011 | B2 |
| 8090598 | Bauer et al. | Jan 2012 | B2 |
| 8140358 | Ling et al. | Mar 2012 | B1 |
| 8180655 | Hopkins, III | May 2012 | B1 |
| 8280752 | Cripe et al. | Oct 2012 | B1 |
| 8407139 | Palmer | Mar 2013 | B1 |
| 8566126 | Hopkins, III | Oct 2013 | B1 |
| 8577703 | McClellan et al. | Nov 2013 | B2 |
| 8595034 | Bauer | Nov 2013 | B2 |
| 8606512 | Bogovich et al. | Dec 2013 | B1 |
| 8630768 | McClellan et al. | Jan 2014 | B2 |
| 8736483 | Takeuchi | May 2014 | B2 |
| 8799036 | Christensen et al. | Aug 2014 | B1 |
| 8892451 | Everett et al. | Nov 2014 | B2 |
| 8935036 | Christensen et al. | Jan 2015 | B1 |
| 9037394 | Fernandes et al. | May 2015 | B2 |
| 9053469 | Bohanek et al. | Jun 2015 | B1 |
| 9082072 | Wedding, Jr. et al. | Jul 2015 | B1 |
| 9141582 | Brinkmann et al. | Sep 2015 | B1 |
| 9141995 | Brinkmann et al. | Sep 2015 | B1 |
| 9361599 | Biemer et al. | Jun 2016 | B1 |
| 9390452 | Biemer et al. | Jul 2016 | B1 |
| 9454786 | Srey et al. | Sep 2016 | B1 |
| 9524269 | Brinkmann et al. | Dec 2016 | B1 |
| 9535878 | Brinkmann et al. | Jan 2017 | B1 |
| 9569799 | Biemer et al. | Feb 2017 | B2 |
| 9619203 | Tamir et al. | Apr 2017 | B2 |
| 9628958 | McBurney | Apr 2017 | B1 |
| 9984420 | Manzella et al. | May 2018 | B1 |
| 20020002475 | Freedman et al. | Jan 2002 | A1 |
| 20020089660 | Weiss | Jul 2002 | A1 |
| 20020111725 | Burge | Aug 2002 | A1 |
| 20030236686 | Matsumoto et al. | Dec 2003 | A1 |
| 20040064247 | Davis | Apr 2004 | A1 |
| 20040153352 | Bems et al. | Aug 2004 | A1 |
| 20040153362 | Bauer et al. | Aug 2004 | A1 |
| 20050171663 | Mittelsteadt et al. | Aug 2005 | A1 |
| 20060052929 | Bastian et al. | Mar 2006 | A1 |
| 20060053038 | Warren et al. | Mar 2006 | A1 |
| 20060182661 | Aquila | Aug 2006 | A1 |
| 20070200663 | White et al. | Aug 2007 | A1 |
| 20070239992 | White et al. | Oct 2007 | A1 |
| 20070250382 | Beck | Oct 2007 | A1 |
| 20070282638 | Surovy | Dec 2007 | A1 |
| 20070299700 | Gay et al. | Dec 2007 | A1 |
| 20080065427 | Helitzer et al. | Mar 2008 | A1 |
| 20080164769 | Eck | Jul 2008 | A1 |
| 20080252412 | Larsson et al. | Oct 2008 | A1 |
| 20080255888 | Berkobin et al. | Oct 2008 | A1 |
| 20090024419 | McClellan et al. | Jan 2009 | A1 |
| 20100030586 | Taylor et al. | Feb 2010 | A1 |
| 20100131304 | Collopy | May 2010 | A1 |
| 20100294583 | Biondo et al. | Nov 2010 | A1 |
| 20110009107 | Guba et al. | Jan 2011 | A1 |
| 20110106370 | Duddle et al. | May 2011 | A1 |
| 20110112969 | Zaid et al. | May 2011 | A1 |
| 20110125363 | Blumer et al. | May 2011 | A1 |
| 20110153367 | Amigo et al. | Jun 2011 | A1 |
| 20110173084 | Cheng | Jul 2011 | A1 |
| 20110304465 | Boult et al. | Dec 2011 | A1 |
| 20120004933 | Foladare et al. | Jan 2012 | A1 |
| 20120010906 | Foladare et al. | Jan 2012 | A1 |
| 20120066007 | Ferrick et al. | Mar 2012 | A1 |
| 20120072243 | Collins et al. | Mar 2012 | A1 |
| 20120073892 | Hunter | Mar 2012 | A1 |
| 20120123806 | Schumann, Jr. et al. | May 2012 | A1 |
| 20120179493 | Giordano | Jul 2012 | A1 |
| 20120197669 | Kote et al. | Aug 2012 | A1 |
| 20120262283 | Biondo et al. | Oct 2012 | A1 |
| 20130006674 | Bowne et al. | Jan 2013 | A1 |
| 20130013347 | Ling | Jan 2013 | A1 |
| 20130046559 | Coleman | Feb 2013 | A1 |
| 20130046562 | Taylor et al. | Feb 2013 | A1 |
| 20130110867 | Grabau et al. | May 2013 | A1 |
| 20130169410 | Amselem | Jul 2013 | A1 |
| 20130169442 | Ruocco et al. | Jul 2013 | A1 |
| 20130217990 | Saettel et al. | Aug 2013 | A1 |
| 20130226622 | Adamson et al. | Aug 2013 | A1 |
| 20130274955 | Rosenbaum | Oct 2013 | A1 |
| 20140006164 | Bellegante et al. | Jan 2014 | A1 |
| 20140019167 | Cheng et al. | Jan 2014 | A1 |
| 20140019170 | Coleman et al. | Jan 2014 | A1 |
| 20140046701 | Steinberg et al. | Feb 2014 | A1 |
| 20140051041 | Stefan et al. | Feb 2014 | A1 |
| 20140058761 | Freiberger et al. | Feb 2014 | A1 |
| 20140067434 | Bourne et al. | Mar 2014 | A1 |
| 20140095214 | Mathe et al. | Apr 2014 | A1 |
| 20140108058 | Bourne et al. | Apr 2014 | A1 |
| 20140114674 | Krughoff et al. | Apr 2014 | A1 |
| 20140148972 | Basir et al. | May 2014 | A1 |
| 20140164027 | Cheung et al. | Jun 2014 | A1 |
| 20140172467 | He et al. | Jun 2014 | A1 |
| 20140180727 | Freiberger et al. | Jun 2014 | A1 |
| 20140257862 | Billman et al. | Sep 2014 | A1 |
| 20140257863 | Maastricht et al. | Sep 2014 | A1 |
| 20140257866 | Gay et al. | Sep 2014 | A1 |
| 20140257867 | Gay et al. | Sep 2014 | A1 |
| 20140257871 | Christensen et al. | Sep 2014 | A1 |
| 20140257873 | Hayward et al. | Sep 2014 | A1 |
| 20140257874 | Hayward et al. | Sep 2014 | A1 |
| 20140278574 | Barber | Sep 2014 | A1 |
| 20140278837 | Blumer et al. | Sep 2014 | A1 |
| 20140297348 | Ellis | Oct 2014 | A1 |
| 20140335902 | Guba et al. | Nov 2014 | A1 |
| 20150019268 | Handel et al. | Jan 2015 | A1 |
| 20150025917 | Stempora | Jan 2015 | A1 |
| 20150032481 | Norling-Christensen et al. | Jan 2015 | A1 |
| 20150045983 | Fraser et al. | Feb 2015 | A1 |
| 20150081404 | Basir | Mar 2015 | A1 |
| 20150106289 | Basir et al. | Apr 2015 | A1 |
| 20150134368 | Lee | May 2015 | A1 |
| 20150141043 | Abramson et al. | May 2015 | A1 |
| 20150161738 | Stempora | Jun 2015 | A1 |
| 20150168174 | Abramson et al. | Jun 2015 | A1 |
| 20150253144 | Rau et al. | Sep 2015 | A1 |
| 20160086285 | Jordan Peters | Mar 2016 | A1 |
| 20160086397 | Phillips | Mar 2016 | A1 |
| 20160171620 | Bogovich et al. | Jun 2016 | A1 |
| 20160189304 | Todasco et al. | Jun 2016 | A1 |
| 20160205238 | Abramson et al. | Jul 2016 | A1 |
| 20160379310 | Madigan | Dec 2016 | A1 |
| 20170021764 | Adams et al. | Jan 2017 | A1 |
| 20180060970 | Oduor et al. | Mar 2018 | A1 |
| 20180374113 | Ramirez | Dec 2018 | A1 |
| 20190066223 | Bogovich et al. | Feb 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 1921580 | May 2008 | EP |
| 2002007718 | Jan 2002 | JP |
| 2002297910 | Oct 2002 | JP |
| 2007257326 | Oct 2007 | JP |
| 2010529562 | Aug 2010 | JP |
| 2010034909 | Apr 2010 | WO |
| 2014151155 | Sep 2014 | WO |
| 2014181303 | Nov 2014 | WO |
| Entry |
|---|
| 2008, Tomer Toledo, Oren Musicant and Tsippy Lotan In-vehicle data recorders for monitoring and feedback on drivers' behavior, Transportation Research Part C: Emerging Technologies, vol. 16, Issue 3, 2008, pp. 320-331, ISSN 0968-090X, https://doi.org/10.1016/j.trc.2008.01.001. |
| May 22, 2018—(CA) Office Action—App 2,975,084. |
| Nov. 28, 2017—(WO) International Search Report & Written Opinion—PCT/US17/050231. |
| Nov. 28, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/170,000. |
| Oct. 29, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 15/138,516. |
| Jul. 3, 2018—(EP) Supplementary Search Report—EP16743838.1. |
| Feb. 16, 2018—U.S. Non-Final Office Action—U.S. Appl. No. 14/988,977. |
| Jun. 15, 2015—U.S. Non-Final Office Action—U.S. Appl. No. 14/607,636. |
| Sep. 16, 2015—U.S. Final Office Action—U.S. Appl. No. 14/607,636. |
| Feb. 11, 2016—U.S. Notice of Allowance—U.S. Appl. No. 14/607,636. |
| Mar. 29, 2016—(WO) Search Report and Written Opinion—App PCT/US2016/013201. |
| Mar. 29, 2016—(WO) Search Report and Written Opinion—App PCT/US16/013192. |
| Oct. 4, 2016—U.S. Notice of Allowance—U.S. Appl. No. 15/170,084. |
| Oct. 6, 2016—U.S. Notice of Allowance—U.S. Appl. No. 15/170,203. |
| Jan. 25, 2019—U.S. Non-Final Office Action—U.S. Appl. No. 15/262,541. |
| Aug. 10, 2018—U.S. Final Office Action—U.S. Appl. No. 14/988,977. |
| Jun. 1, 2018—(CA) Office Action—App 2,975,085. |
| Jul. 23, 2018—(EP) Extended search report—App 16743837.3. |
| Mar. 28, 2019—U.S. Notice of Allowance—U.S. Appl. No. 15/397,199. |
| Mar. 12, 2019—U.S. Final Office Action—U.S. Appl. No. 15/138,516. |
| Mar. 14, 2019—U.S. Non-Final Office Action—U.S. Appl. No. 15/138,576. |
| Mar. 26, 2019—(CA) Office Action—App 2,975,085. |
| Feb. 5, 2019—(CA) Notice of Allowance—App 2,975,084. |
| May 23, 2019—U.S. Notice of Allowance—U.S. Appl. No. 14/988,977. |
| “Usage-Based Auto Insurance (UBI) a revolution is underway . . . Is your Company Ready?” by Robin Harbage, FCAS, MAAA. Pub. Dec. 2011. (Year: 2011). |
| “Profiting From Business Model Innovation: Evidence from Pay-As-You-Drive Auto Insurance” by Panos Desyllas and Mari Sako. Research Policy 42 (2013) 101-116. Available Online: Jun. 25, 2012. (Year: 2012). |
| Jun. 10, 2019 U.S. Final Office Action—U.S. Appl. No. 15/262,541. |
| Jun. 18, 2019 U.S. Corrected Notice of Allowance and Fees Due—U.S. Appl. No. 14/988,977. |
| Jul. 10, 2019—U.S. Notice of Allowance—U.S. Appl. No. 15/170,000. |
| Jul. 10, 2019—U.S. Notice of Allowance—U.S. Appl. No. 15/397,199. |
| Nov. 7, 2019—(JP) Office Action—U.S. Appl. No. 2017540654. |
| Jan. 22, 2020—U.S. Non-Final Office Action—U.S. Appl. No. 15/262,541. |
| Number | Date | Country | |
|---|---|---|---|
| 20170103467 A1 | Apr 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14607662 | Jan 2015 | US |
| Child | 15170084 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15170084 | Jun 2016 | US |
| Child | 15379019 | US |
