Patent ID: 12190390

DETAILED DESCRIPTION

The following description is merely illustrative in nature and is not intended to limit the present disclosure, application, or uses. It will be noted that the first digit of three-digit reference numbers and the first digit of four-digit reference numbers correspond to the figure number in which the element first appears.

The following description explains, by way of illustration only and not of limitation, various embodiments of enabling verification and/or securing of vehicle insurance to cover temporary use of a vehicle.

By way of a non-limiting introduction and overview, in various embodiments a system associated with a vehicle is configured to determine an identity of a user seeking to operate the vehicle and whether an insurance policy associated with the vehicle covers the user's operation of the vehicle. If it is determined that the user is not associated with the insurance policy covering the use of the vehicle, operation of the vehicle may be permitted when the user is covered by an additional insurance policy. The additional insurance policy may be an existing insurance policy associated with the user that provides coverage for the operation of the vehicle by the user or an on-demand insurance policy secured by the user to provide coverage for the user's operation of the vehicle. Thus, an owner (or other individual that controls use of the vehicle can), for example, restrict use of the vehicle to persons intended to be covered by the owner's policy or a person whose use is covered by his own policy or is able to arrange a supplemental or on-demand policy to cover the user; the system may facilitate the user's procurement of the on-demand policy.

Now that a general overview has been given, details of various embodiments will be explained by way of non-limiting examples given by way of illustration only and not of limitation.

Referring toFIG.1, in various embodiments a vehicle100has a body102that incorporates a cabin104that accommodates a payload that includes occupants and/or cargo. In various embodiments, the body102also includes a cargo area106separate from the cabin104, such as a truck bed or trunk, where additional cargo may be carried. The vehicle100also includes a drive system108that is operably coupled with wheels109to accelerate, decelerate, steer, brake, or otherwise motivate the vehicle100. In various embodiments, the drive system108includes at least one electric motor, an internal combustion engine, or a hybrid motor/engine to provide motive force to the wheels109, and may also include drive train and/or transmission systems to convey rotational force from the motor and/or engine to the wheels109. The drive system108also may include steering systems to guide the wheels109, as well as a braking system to slow the wheels109and/or to recapture energy from the rotating wheels109to provide electrical energy to one or more batteries or other power cells (not expressly shown) included in the drive system108. In various embodiments, the vehicle100also includes a vehicle control system110that controls operation of the vehicle100including, but not limited to, controlling access to operate the vehicle100.

In various embodiments, presenting an authorized key122for verification by the vehicle control system110is a requirement to be able to operate the vehicle100. The authorized key122, as further described below, may include a key or key fob, or another device that provides an authorization that may be verified by the vehicle control system110. An authorized key122may be possessed and/or allocated by an owner112of the vehicle100. In various embodiments, for purposes of this description, one or more owners112has legal control of the vehicle100. The owner112may be an actual legal owner of the vehicle100(owning the vehicle outright or subject to a lien of an entity financing purchase of the vehicle100), a lessee of the vehicle100, or another person in whom control of the vehicle100is vested, such as an employee given control of a company car, a renter of a car, etc. It will be appreciated that the owner112may be one of multiple owners of the vehicle100, such as a domestic couple or a business entity (for which one or more persons may be tasked with control of the vehicle100). According to various embodiments, in addition to the owner112of the vehicle100, there may be regular, preauthorized users of the vehicle102, such as a spouse, domestic partner, employee, and/or child of the owner112. These other users (not shown inFIG.1) may be authorized to operate the vehicle100, but, according to various embodiments, only the owner112can actually authorize these other users to operate the vehicle.

For purposes of this example, it is assumed that spouses, children, employees, etc., as regular users of the vehicle100, are included in insurance policies that cover the ordinary use of the vehicle100. However, on occasion, the owner112of the vehicle100may wish to authorize another user to operate the vehicle100but only on the condition that the user has his or her own insurance coverage that will cover their use of the vehicle100or is willing to secure such coverage. The owner112may not require such coverage for limited uses, such as by a valet or a mechanic. Thus, the stipulation that insurance coverage be provided by the user may be limited to select users of the vehicle100.

When the owner112wishes to permit an authorized user114to operate the vehicle100subject to demonstrating or securing insurance coverage, the owner may access an authorization control system120, as further described below. Using the authorization control system120, the owner112may provide the authorized key122to an authorized user114to enable the authorized user122to be able to operate the vehicle100. The authorized key122, as described further below, may be a physical device, such as a key fob, or a code providable to a smartphone or other device that may be carried and presented to the vehicle control system110the authorized user114. The authorized key122may be presented to the vehicle control system110by being brought within proximity of the vehicle control system110by, for example, inserting the authorized key122in a key receptacle (not shown inFIG.1), by bringing the authorized key122into the cabin104of the vehicle100or otherwise bringing the authorized key122into proximity of the vehicle control system110where the vehicle control system110can verify the authentication of the authorized key122.

As previously described, however, a condition of permitting the authorized user122to use the vehicle100may be that the authorized user114verify insurance coverage or secure insurance coverage to cover his or her operation of the vehicle100. If the authorized user114has insurance coverage that will cover his or her use of the vehicle100, the authorized user114will provide policy information to the authorization control system120. The authorization control system120will then verify the coverage through an insurance carrier system130. Alternatively, if the authorized user114does not have coverage that will cover his or her use of the vehicle100, via the authorization control system120, the authorized user114may obtain coverage from the insurance carrier systems130.

In various embodiments, an interface is included in the vehicle control system110that may enable the owner112to grant authorization to use the vehicle100to the authorized user114. Similarly, the authorized user114may use an interface (not shown inFIG.1) of vehicle control system110to present policy information to permit verification of coverage. Additionally or alternatively, the owner112and/or the authorized user114may access the authorization control system120via computing devices such as smartphones or other computing devices with communications capabilities (not shown inFIG.1).

In various embodiments, the authorization control system120may configure the authorized key122for acceptance by the vehicle control system110when the insurance coverage of the authorized user114(pre-existing or presently-secured) is verified. The authorized key122may become activated upon such verification and/or the vehicle control system110may accept the authorized key122only after it receives verification from the authorization control system120. In various embodiments, the verification of insurance coverage (pre-existing or presently-secured) is desirably received via the authorization control system120to be able to directly verify the existence of the coverage rather than relying, for example, on a statement or assurance from the authorized user114that could prove to be inaccurate.

Referring additionally toFIG.2, in various embodiments the cabin104of the vehicle100(FIG.1) includes a vehicle control system interface210that enables interaction with the vehicle control system110(FIG.1). The vehicle control system interface210may include a display212and a number of inputs213-216that enable a user to interact with the vehicle control system interface210. It will be appreciated that the display212may include a touchscreen or receive voice commands to enable user interaction with the vehicle control system interface210instead of or in addition to by using the inputs213-216. The owner112or the authorized user114(FIG.1) may use the vehicle control system interface210to interact with the authorization control system120to facilitate authorization of the authorized user114and/or to verify or arrange insurance coverage for the authorized user114. Additionally or alternatively, a smartphone or other computing device250may be used with the vehicle control system110via a device interface252to enable the owner112and/or the authorized user114to interact with the vehicle control system110to facilitate authorization of the authorized user114and/or to verify or arrange insurance coverage for the authorized user114. The smartphone or other computing device250also may be able to communicate directly with the authorization control system120to facilitate authorization of the authorized user114and/or to verify or arrange insurance coverage for the authorized user114.

Once the authorization of the authorized user114and the verification of pre-existing or presently-secured coverage are completed, the authorized key122may become active and/or recognized by the vehicle control system110to permit the authorized user114to operate the vehicle100. As previously stated, the authorized key122may include a key fob220that is recognizable by a key fob sensor222. The key fob sensor222may be configured to recognize the key fob220when the key fob220is inserted into a receptacle224or brought within proximity of the key fob sensor222, such as by being carried into the cabin104of the vehicle100. It will be appreciated that the key fob220may or may not include or be integrated with an actual mechanical key; the nature of the key fob220is not limited to any particular form.

As also previously stated, the authorized key122may include a portable computing device250, such as a smartphone, smartwatch, fitness tracker, or other computing device that may include a code presentable to and/or readable by the vehicle control system110to enable operation of the vehicle100. Thus, in response to being detected and/or successfully interrogated via a device interface252, the portable computing device250may provide verification that the authenticated user114is authorized to operate the vehicle100. The portable computing device250may include any device capable of receiving and/or presenting a code that may be used to identify the authorized user114to the vehicle control system110.

In various embodiments, the cabin104may also include additional instrumentation usable to record or verify the identity of a person seeking to operate the vehicle100. The vehicle control system110may be configured to verify that a would-be operator includes the owner112, the authorized user114, or another person authorized to operate the vehicle100. The instrumentation may be used to record or compare characteristics of a person seeking to operate the vehicle100with available or previously-captured data regarding the operator. For example, a camera or other imaging device230may be positioned to image the operator (not shown). Capturing image data of the operator may be part of the process of the owner112enabling the authorized user114to use the vehicle100. An image of the authorized user114may be captured by the camera230as part of the authorization process, or an image may be collected using the owner's smartphone or another device. The image may then be compared to image data collected by the camera230when the authorized user114seeks to operate the vehicle100. Similarly, when a person operates the vehicle100, selected positions of an operator's seat240, a repositionable steering wheel245, or other positionable apparatuses may be compared to positions of these apparatuses used by permitted users to verify or further verify the identity of the person seeking to operate the vehicle100. Thus, for example, when a person possessing the key fob220or the smartphone encoded to be that of the owner112or the authorized user114seeks to operate the vehicle100, the vehicle control system110may first capture data from the camera230or one of the other apparatuses. The captured data may then be compared to previously-captured or recorded data to ensure that the individual presenting the key fob220or the smartphone250is the person to whom authorization to use the vehicle100has been granted.

Referring additionally toFIG.3, and given by way of example only and not of limitation, some form of a generalized computing system300may be used for the vehicle control system110of the vehicle100, the authorization control system120, the insurance carrier system(s)130(FIG.1), the portable computing device250(FIG.2), other computer systems. In various embodiments, the computing system300typically includes at least one processing unit320and a system memory330. Depending on the exact configuration and type of computing system, the system memory330may be volatile memory, such as random-access memory (“RAM”), non-volatile memory, such as read-only memory (“ROM”), flash memory, and the like, or some combination of volatile memory and non-volatile memory. The system memory330typically maintains an operating system332, one or more applications334, and program data338. The operating system332may include any number of operating systems executable on desktop or portable devices including, but not limited to, Linux, Microsoft Windows®, Apple OS®, or Android®, or a proprietary operating system.

The computing system300may also have additional features or functionality. For example, the computing system300may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, tape, or flash memory. Such additional storage is illustrated inFIG.3by removable storage340and non-removable storage350. Computer storage media may include volatile and non-volatile, 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. The system memory330, the removable storage340, and the non-removable storage350are all examples of computer storage media. Available types of computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory (in both removable and non-removable forms) or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computing system300. Any such computer storage media may be part of the computing system300.

The computing system300may also have input device(s)360such as a keyboard, mouse, stylus, voice input device, touchscreen input device, etc. Output device(s)370such as a display, speakers, printer, short-range transceivers such as a Bluetooth transceiver, etc., may also be included. The computing system300also may include one or more communication systems380that allow the computing system300to communicate with other computing systems390, as further described below. Available forms of communication media typically carry computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” may include a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of illustrative example only and not of limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared and other wireless media. The term computer-readable media as used herein includes both storage media and communication media.

In further reference toFIG.3, the computing system300may include global positioning system (“GPS”) circuitry385that can automatically discern its location based on relative positions to multiple GPS satellites. As described further below, GPS circuitry385may be used to determine a location and generate data about acceleration, speed, braking, turning, and other movement of the vehicle100(FIG.1).

Referring additionally toFIG.4, an operating environment400of the vehicle control system110may include one or more multiple remote computing systems420and421. For example, a first remote computing system420may support the authorization control system120and a second remote computing system421may support an insurance carrier system130. Although one computing system is shown for each, it will be appreciated that the authorization control system120may operate across multiple separate computing systems at one or more locations and each insurance carrier system130may operate multiple separate computing systems at one or more locations. Alternatively, if the operator of the authorization control system120provides insurance, the authorization control system120and the insurance carrier system130may be hosted on the same computing system.

In various embodiments, the remote computing systems420and421may be configured to communicate with the vehicle control system110of the vehicle100and/or a portable computing system250(FIG.2) to control authorization of use of the vehicle100and/or to verify or secure insurance coverage to use the vehicle100. The vehicle control system110, the portable computing system250, and the remote computing systems420and421may communicate over a network410via communications links411,412,413, and414, respectively. Because the vehicle100and the portable computing system250are movable devices, the communications links411and412generally may be wireless communications links, such as cellular, satellite, or Wi-Fi communications links. However, it will be appreciated that any or all of the systems may communicate over wireless or wired communications links. For example, when the vehicle100is connected to a power system to charge its battery system, a wired connection also may be made to permit wired communication between the vehicle control system110with the network410. The remote computing systems420and421may include servers or server farms422and423, respectively. The remote computing systems420and421may access programming and data from data storage devices424and425, respectively, over high-speed channels426and427, respectively.

For the authorization control system120, data stored in the data storage devices424may include authorization data430identifying persons able to authorize use of the vehicle100, authorized users114(not shown), and the conditions by which authorization has been permitted. For the insurance carrier system130, data stored in the data storage devices425may include policy data431, including data on existing policies that authorized users may invoke to support their use of the vehicle, or new policy data such as coverage and terms available for a policy that be secured to support use of the vehicle100. In addition, the data storage devices424and425may include operating systems, applications, and other executable instructions used by the remote computing systems420and421, respectively, as well as other data.

With the operational context and supporting environments thus described, operation of various embodiments is described to depict the function of apparatuses, systems, vehicles, and methods herein described. Referring additionally toFIG.5, as previously described, the owner112of the vehicle100(not shown in this or the subsequent figures) may choose to permit the authorized user114to use the vehicle100. By using an interface510, which may be an interface of the vehicle control system110or another computing device, the owner112may authorize another user to use the vehicle. The interface510may allow the owner to verify the identity of himself or herself as one of the owners512to provide authorization to use the vehicle. The interface510may identify other drivers514authorized to use the vehicle and who may be covered by insurance associated with the vehicle. The interface510also may list authorized users516who have been authorized to use the vehicle, and provide an add option518to enable the creation of one or more additional authorized users. The interface510may include a touchscreen interface or other visual interface that the owner112may engage with a hand519and/or the interface510may be operated by voice commands.

Using the interface510to interact with the authorization control system120, the owner112may activate or generate the authorized key122usable by the authorized user114to operate the vehicle. The authorized key122may be a key or fob220. The authorized key122may be a wearable or portable object, such as a band560, that includes a readable identification device565, such as a transponder or a radio frequency identification (RFID) tag that may be read by the vehicle control system110(not shown inFIG.5) to determine if the authorized user114presents a valid, authorized key. The authorized key122also may be presented as an electronic credential via the portable computing device250that is carried by the authorized user114. Embodiments of the present disclosure are not restricted to an authorized key122of any particular type or form. It will also be appreciated that the embodiments of the present disclosure are not limited to any particular interface being used by the owner112and/or authorized user114to interact with the systems herein described.

Referring additionally toFIG.6, using the interface, the owner112may identify a new authorized user and specify terms of by which the authorized user114may operate the vehicle. By using the interface510, the owner112may identify the authorized user by completing an identification field610. The owner112may also provide a verifiable identifier for the authorized user114, such as by entering information in an identification verification field612. The identification verification field612may include a telephone number or email address associated with the authorized user114that the vehicle control system110(not shown inFIG.6) may use to send a message by which the authorized user114can confirm his or her identity. The identification provided also may include a password or other sequence that the authorized user114may be required to present to the vehicle control system110to be able to initiate possible use of the vehicle.

In various embodiments, the owner512also may be able to specify insurance terms620for the authorized use. The owner112may choose to permit the authorized user114to use the vehicle as a permissive use that will be covered by the owner's own policy (subject to whatever coverage may be automatically applied by the policy of the authorized user114). On the other hand, the owner112may choose to permit the use only if the authorized user114provides insurance coverage to cover his or her use of the vehicle. In the example ofFIG.6, the owner112specifies that the authorized user114will provide insurance to cover use of the vehicle. Subject to these terms, the authorized user112chooses to grant use of the vehicle to the authorized user114. The authorized key122(FIGS.1and5) is then operable for the authorized user114to use, provided the authorized user114fulfills the insurance requirement specified in the example ofFIG.6.

Referring additionally toFIG.7, in various embodiments, because the authorized user114is required by the owner to provide authorized driver insurance through interface710for the use of the vehicle100, the authorized user114may choose to satisfy the requirement by identifying an existing policy712or by specifying that the authorized user is requesting coverage714.

Referring additionally toFIG.8, the authorized user114elects to satisfy the insurance requirement by providing proof of insurance coverage that will cover the use of the vehicle. Upon selecting the existing policy712option, in various embodiments, the authorized user114is prompted for policy information810about the existing policy. By providing policy information810, such as the carrier, policy number, and information used for verifying the identity of the authorized user114, and other information, the authorization control system120(not shown inFIG.8) can query the insurance carrier system130of the specified carrier to verify whether the policy exists and if it will cover the authorized use. If the authorized user114is covered by a qualifying policy, the authorization control system120may enable the vehicle control system110to recognize the authorized key122(neither of which is shown inFIG.8) to permit the authorized user114to operate the vehicle. Alternatively, it is possible that the insurance carrier system130may report to the authorization control system120that the identified policy does not cover the authorized user114for the use communicated by the authorization control system120. In this case, use of the vehicle by the authorized user114will not be permitted by the authorization control system120.

Referring additionally toFIG.9, it is possible that the insurance carrier system130may inform the authorized user114that a rider or other supplemental coverage must be added to the specified policy to cover the intended use of the vehicle by the authorized user114. In such a case, the authorized user114may be prompted to select a supplemental insurance option912whereby the authorized user114is willing to secure the supplemental coverage. In such case, the authorized user114will be able to arrange the supplemental coverage in a manner as described below in which the authorized user114seeks to arrange a separate policy to cover the authorized user114in using the vehicle.

Referring additionally toFIG.10, when the authorized114user does not have a policy that will cover the authorized use and/or does not wish to apply an existing policy, the authorized user114may choose the request coverage option714to arrange to secure an on-demand policy. In either of the examples referenced with regard toFIGS.9and10, via the interface710, the authorization control system120will enable the user to engage with the authorized user's insurance carrier system130or potentially secure offers from multiple insurance carrier systems130to arrange an on-demand insurance policy to cover the use of the vehicle.

Referring additionally toFIG.11, in various embodiments, as part of determining the terms of a supplemental or on-demand policy, the authorized user114also may be prompted to provide user driving information1110, including accident data, infraction data, incident data, driving safety or risk avoidance scores, and identified driving behavior style, or the user driving information1110may be provided by a third-party source when the authorized user114provides consent to access the user driving information1110. Driving safety or risk avoidance scores may be assigned by a third party based on driving history, including past incidents, moving violations, or previously asserted insurance claims. Risk avoidance scores also may be assigned based on driving information captured about the authorized user114and his or her driving by vehicle sensors and collected by an insurance carrier or another entity. Based on the information provided, the authorized user114may be presented with terms1112for at least one available policy and/or with the terms for multiple alternative policies. The terms may include the coverage limits, coverage types, deductible amount(s), cost, and other details. The policy may be time-based, for example, to cover use of the vehicle for a duration of hours, days, etc., or the policy may be usage-based, for example, to cover usage per unit time or unit of distance traveled per unit cost.

Referring additionally toFIG.12, once the authorized user114elects to purchase the policy (or a particular policy, if more than one is available), the authorized user114may secure the policy by providing payment information1210, such as payment type, account number, and payment verification information. As previously described, the information may be routed from the interface710via the authorization control system120to the insurance carrier system(s)130to complete the acquisition of the policy. Once the policy is secured, the vehicle authorization system120may enable the vehicle control system110to recognize the authorized key122(neither of which is shown inFIG.8) to permit the authorized user114to operate the vehicle.

In various embodiments, in addition to the types of details and terms previously discussed, as part of allowing the authorized use or securing a supplemental or on-demand insurance policy, the owner112and/or the authorized user114may specify or provide other details. Referring additionally toFIG.13, in various embodiments the owner112may specify additional limitations on the authorized user. The limitations may include specifying particular usage location/route information1310. The usage location may include specifying whether the vehicle is to be used in a city, suburb, off-road, etc. The route information may specify whether the vehicle will be driven on highways, freeways, surface streets, etc. The limitations also may specify a type of driving1320(e.g., work, recreational), a usage time permitted1330, a usage distance permitted1340, or other limitations or conditions. In securing supplemental or on-demand insurance coverage, the authorized user114may similarly identify the usage location1310, the type of driving1320, the usage time1330and/or usage distance1340. Similarly, mode limitations1350may be specified to prevent the authorized user114from activating or using some modes or features of the vehicle100. For example, mode limitations1350may include preventing the authorized user114from activating off-road driving features, from deactivating automated driver assistance systems, such as automatic emergency braking or lane-keeping assistance features. In addition, where the vehicle100is a type of vehicle with which the authorized user114may or may not have familiarity that could affect the terms of the coverage, a vehicle familiarity1360may be specified. For example, if the vehicle100includes an electrically-powered vehicle that, it may have operating characteristics that may present a challenge to a user not familiar with these characteristics, such as rapid deceleration resulting from regenerative braking. Similarly, the vehicle familiarity1360may be applicable if the vehicle100is a truck and authorized user114is used to driving passenger vehicles.

In various embodiments, usage of the vehicle may be restricted to monitored use1370so that the owner112may be assured that the authorized user114does not use the vehicle in a way not contemplated by the owner112in permitting the authorized user114to use the vehicle. The monitored use1370of the vehicle also may be for the sake of the insurance carrier to ensure that the authorized user114uses the vehicle in accordance with the terms on which a supplemental or on-demand policy was issued. Thus, for example, if the owner112agrees to allow the authorized user114to use the vehicle for commuting, the authorized user114may be restricted from using the vehicle for off-road driving or for traveling more than a stated distance. Similarly, if a supplemental or on-demand insurance policy was issued for use in a particular location, such as suburban use, the policy terms could be voided or modified if the user operated the vehicle in an urban area. For example, if the authorized user114uses the vehicle in a manner inconsistent with the policy issued, the insurance carrier could increase the cost of the policy.

Further, the driving behavior of the authorized user114may be monitored to report to the owner112and/or to the insurance carrier for providing decision support to the owner112as whether to allow future use of the vehicle by the authorized user114and/or to inform future insurance coverage determinations. For example, if monitoring operation of the vehicle by the authorized user114indicates that the authorized user114includes high risk behaviors, such as driving at excessive speeds, hard braking, or other behaviors, these monitored behaviors may be reported to the owner112and/or evaluated by an insurance carrier that provides supplemental or on-demand insurance. As a result, the owner112can consider this behavior in determining whether to allow the authorized user114to subsequently be an authorized user. Correspondingly, an insurance carrier that issues supplemental or on-demand insurance coverage to the authorized user114may use the monitored driving behavior to determine a rate for the current or a future policy or policies for the authorized user114based on the monitored driving behavior. Thus, for example, if the authorized user114is charged one rate for a particular authorized use, but the monitored driving behavior includes high-risk behaviors, the insurance carrier may decline to offer subsequent supplemental or on-demand coverage to the authorized user or may adjust the rate charged for the coverage. On the other hand, if the monitored use1370shows that the authorized user114employs careful or low-risk driving behaviors, then the insurance carrier may offer supplemental or on-demand insurance at a reduced charge. Thus, a cost of a supplemental or usage-based policy is adjustable for current and/or subsequent usage based on driving behaviors of the authorized user114detected during at least one preceding instance of operation of the vehicle by the authorized user114.

Referring additionally toFIG.14, in various embodiments the vehicle may include many sensing systems usable to monitor how and where the vehicle is operated. The vehicle control system110includes a number of subsystems that may provide data. For example, in various embodiments, the vehicle control system110may include a forward collision warning system1402to alert an operator, such as the authorized user114, proceeding at a normal travel speed, of a stopped vehicle or other object in the road. The engagement of the forward collision warning system1402, or repeated use of the engagement of the forward collision warning system1402, may be indicative of operator inattention by the authorized user114. Similarly, the vehicle control system110may include an automatic emergency braking system1404. While the forward collision warning system1402alerts the operator to apply the brakes to avoid a stoppage or other object in the road, the automatic emergency braking system1404actually automatically engages the brakes to stop the vehicle100(FIG.1) of its own accord when a stoppage or other object is detected in the road. The engagement of the emergency braking system1404also may be indicative of operator inattention by the authorized user114.

The vehicle control system110also may include an adaptive cruise control system1406. The adaptive cruise control system1406automatically adjusts a cruising speed, set by the operator or the cruise control system, to reflect the speed of traffic ahead. For example, if an operator sets the adaptive cruise control system1406to a posted highway speed of 65 miles per hour but, because of traffic, the speed of vehicles in the road ahead travel varies between 55 and 65 miles per hour, the adaptive cruise control system1406will repeatedly adjust the cruising speed to maintain a desired distance between the vehicle and other vehicles in the road ahead. Whether the authorized user114uses the adaptive cruise control system1406may be considered in evaluating the authorized user114for future use of the vehicle or the insurance terms available to the authorized user114.

The vehicle control system110may include a lane departure warning system1408that alerts an operator when the vehicle veers close to or across a lane marker and thereby presents an obvious hazard. The vehicle control system110may include a lane keeping assist system1410that steers the vehicle to prevent the vehicle from veering close to or across a lane marker. The extent to which the authorized user114uses the system—or must rely on the system—may be used in evaluating the level of care employed by the authorized user114.

The vehicle control system110may include a blind spot detection system1412that alerts an operator of vehicles traveling in blind spots off the rear quarters of the vehicle to warn the operator not to change lanes in such cases. The vehicle control system110may include a steering wheel engagement system1414that detects when the operator has released the wheel. Release of the wheel may be logged as an indication of operator inattention. The vehicle control system110may include a pedal engagement system1416that detects when the operator's foot is in contact with the accelerator pedal or the brake pedal. The timing of the operator in engaging one of the pedals also may be logged as an indication of overly-aggressive driving, such as if the operator continually accelerates and decelerates sharply. The vehicle control system110also may include a traffic sign recognition system1418that, for example, recognizes stop signs or speed limit signs. Again, all of these systems may provide data indicative of the level of care employed by the authorized user114.

The vehicle control system110also may include a rear cross-traffic alert system1420to apprise an operator of the approach of other vehicles when the vehicle is moving out of a space. Similarly, the vehicle control system110may include a backup warning system1422that warns the operator when the vehicle is approaching an object behind the vehicle. The vehicle control system110may include an automatic high-beam control system1424to de-activate and re-activate high beams as other cars approach and then pass by. Availability of such a system may reduce the likelihood of incidents during travel on highways or surface streets with insufficient or no lighting. The vehicle control system110also may include an automated driving system1450that provides for partially-autonomous or fully autonomous control of the vehicle. Permitting the authorized user114to use the vehicle100only subject to partially-autonomous or fully-autonomous control could affect the coverage available or the cost of that coverage based on the reduced risk afforded by using such systems. The willingness of the authorized user114to activate these features may also provide an indication of the level of care used by the authorized user114in operating the vehicle.

Referring additionally toFIG.15, in addition to the devices included in the vehicle control system110, the vehicle data system111may receive inputs from other sensors. The sensors1500may include a GPS device1530to monitor position and movement of the vehicle to, for example, determine where the vehicle is being used and/or if the use is consistent with the agreed use and the supplemental or on-demand insurance policy in place. The sensors1500also may include an accelerometer1532to detect rapid acceleration or deceleration that potentially may indicate overly-aggressive driving or hard braking as a result of operator inattention or dangerous traffic patterns. The sensors1500may include a gyroscope1534to detect abrupt changes of direction indicative of a treacherous road, sharp lane changes, or abrupt turns. The sensors1500may include at least one following distance/lateral distance sensor1536to determine how closely the vehicle follows other vehicles or how closely the vehicle passes next to other vehicles. The following distance/lateral distance sensor1536may use any technology that can determine following distance from another vehicle, such as radar, LIDAR, optical measurement made using cameras or other optical sensors, ultrasonic measurement, laser measurement, or any other technology that can be used to determine following distance from another vehicle.

The sensors1500may also include device sensors, such as tire pressure sensors1538to monitor whether the tires are inflated to a recommended level. The sensors1500also may include miscellaneous device sensors1540to determine whether other systems, such as the lights, horn, and wipers have been used on particular routes. The sensors1500may also include a seatbelt sensor1542to indicate whether the occupants wore seatbelts on particular routes. The sensors1500may also include a phone usage sensor1544(which may take the form of an app executing on the phone) to report whether the operator was handling or operating the operator's phone on particular routes. The sensors1500may include an airbag deployment sensor1546or a collision sensor1548to report a catastrophic event that resulted in a collision and/or a serious collision that warranted deployment of the airbag. Finally, the sensors1500may include one or more cameras1550to detect and evaluate conditions in and around the vehicle100. The cameras1550outside of the vehicle may be able to monitor position of the vehicle relative to other vehicles and position of the vehicle on the road, to monitor travel conditions such as traffic, weather, and roadway conditions, and to collect other data. The cameras1550inside of the vehicle may be used to identify the operator, determine whether occupants are wearing seatbelts, whether an operator is distracted, and gather other information.

The data collected from the sensors1500may be received by the vehicle control system110and used to evaluate the care used by the authorized user114for the sake of the owner112and/or for an insurance carrier who may have provided or may be providing the supplemental or on-demand insurance coverage. Table 1 presents a list of data that may be included in the vehicle driving data101. Table 1 includes a data field that may be logged and, for those quantities that are regularly sampled and/or stored, a frequency with which the data is sampled and/or stored.

TABLE 1MinimumSampling/StoringFieldDescriptionFrequencyVehicle IDUnique identifier for each vehicle thatNAcan be tied back to the VINVINVehicle Identification NumberNADriver IDUnique identifier for each driverNAwhen availableTrip IDUnique identifier for a specific tripNATrip StartStart date and time of tripNATrip EndEnd date and time of tripNATime StampTimestamp taken from every variable1 Hzreporting at one-second granularityTime Zone Offset1 HzOdometerNAVehicle SpeedCalculated using multiple sensors1 Hzincluding speed of each motorAccelerometerMeasuring 3-axis movement10 Hzthroughout the vehicleHard Braking1 HzRapid Acceleration1 HzAggressive cornering1 HzAutonomous ModeEnabled and Disabled1 HzOn/OffAutonomous ModeWarnings, driver actions, feature1 HzIndicatorsstatus, feature sub-state, etc.Adaptive CruiseEnabled and Disabled1 HzControl On/OffAdaptive CruiseWarnings, driver actions, feature1 HzControl Statusstatus (set, cancel, resume, etc.),feature sub-state, distance/gapsettings, speed settings, etc.Lane Keeping AssistEnabled and Disabled1 HzOn/OffLane Keeping AssistWarnings (LH, RH), driver actions,1 Hzfeature status, feature sub-state, etc.Lane DepartureEnabled and Disabled1 HzWarning On/OffLane DepartureWarnings (LH, RH), driver actions,1 HzWarningfeature status, feature sub-state, etc.Manual Park AssistEnabled and Disabled1 HzOn/OffManual Park AssistWarnings, driver actions, feature1 Hzstatus, feature sub-state, etc.Auto EmergencyEnabled and Disabled1 HzBraking EngagedOn/OffAuto EmergencyWarnings, Proximity, driver actions,1 HzBraking Engagedvehicle actions, feature status, featuresub-state, etc.Hands off the wheelWarnings, driver actions, feature1 Hzstatus, feature sub-state, etc.Forward CollisionEnabled and Disabled1 HzWarning On/OffForward CollisionWarnings, Proximity, driver actions,1 HzWarningvehicle actions, feature status, featuresub-state, etc.Rear Cross TrafficEnabled and Disabled1 HzAlert On/OffRear Cross TrafficWarnings, Proximity, driver actions,1 HzAlertvehicle actions, feature status, featuresub-state, etc.Blindspot MonitoringEnabled and Disabled1 HzOn/OffBlindspot MonitoringWarnings, Proximity, driver actions,1 Hzvehicle actions, feature status, featuresub-state, etc.Backup WarningEnabled and Disabled1 HzSystem On/OffBackup WarningWarnings, Proximity, driver actions,1 HzSystemvehicle actions, feature status, featuresub-state, etc.GPS (Latitude,Altitude, bearing, error, mode,1 HzLongitude, andposition (latitude/longitude), speedAccuracy)Vehicle NighttimeNAParkingVehicle DaytimeNAParkingDistraction/InattentionEnabled and Disabled Status for each1 HzOn/Offmonitoring device, driver monitoringsystem and any additional sensorsbeing usedDistraction/InattentionEyes on road, head and/or eye1 Hzpositions, pupil dilation, warnings,driver actions, feature status, featuresubstate, etc.Proximity SensorsObject distance from the vehicle -1 Hzvehicles, pedestrians, etc. - multiplesensors including radar, LiDAR,video, ultrasonic, etc.Impact Sensor Event1 HzCrash DetectionIncident detection, location of impact,1 Hzseverity of impact, sensors damaged,etc.Airbag Deployment1 HzVehicle Roll-over1 HzVehicle Spin-out1 HzDriver Seatbelt EventSeat occupied, seatbelt status1 HzPassenger SeatbeltSeat occupied, seatbelt status1 HzEventDriver DetectionDriver ID detection, age, gender, key1 Hztype, user role, known insured,vehicle settings and connections, etc.Headlights On/OffOn/Off, high or low beam, status,1 Hzfault, warnings, animations, etc.Fog-lights On/OffOn/Off, high or low beam, status,1 Hzfault, warnings, animations, etc.Windshield WipersStatus1 HzManual On/OffRain sensorEnabled, disabled, status, failure1 HzwarningsWarning LightsStatus1 HzOn/OffSmartphone PairedEnabled, name, usage, warnings,1 Hzfeatures status, subfeature status, etc.Phone CallsConnection, connection type,1 Hzduration, volume, etc.Alexa UsageConnection, connection type,1 Hzduration, volume, etc.Music VolumeConnection, connection type,1 Hzduration, volume, etc.Traffic SignEnabled or disabled, feature status,1 HzRecognitionfailures, type, translation, etc.Traffic Light InfoEnabled or disabled, feature status,1 Hzfailures, type, translation, etc.High Beam AssistFeature Status1 HzTire PressureStatus, position, pressure, warnings,1 HzactionsOutside Temperature1 HzVehicle Interior1 HzTemperatureDoor LocksLocked, unlocked, door ajar, failures,1 Hzdoor location, signals, warnings,feature status, etc.Video recordingEnabled or disabled, frame rate,1 Hzduring tripstorage location, storage type, storagespace, retrieval, recording ID,recording flags, etc.Video recording whenEnabled or disabled, frame rate,1 Hzparkedstorage location, storage type, storagespace, retrieval, recording ID,recording flags, etc.

Referring additionally toFIG.16, in various embodiments an illustrative method1600can determine whether a user's use of a vehicle is covered by an insurance policy associated with the user. The method1600begins at a block1605. At a block1610, an identity is determined of a user seeking to operate a vehicle. At a block1620, it is determined whether an insurance policy associated with the vehicle covers operation of the vehicle by the user. At a block1630, operation of the vehicle by the user who is not associated with the insurance policy covering the use of the vehicle is enabled in response to a determination that the user is covered by an additional insurance policy including either an existing insurance policy associated with the user that provides coverage for the operation of the vehicle by the user or an on-demand insurance policy that provides coverage for the operation of the vehicle by the user. The method1600ends at a block1635.

Those skilled in the art will recognize that at least a portion of the devices and/or processes described herein can be integrated into a data processing system. Those having skill in the art will recognize that a data processing system generally includes one or more of a system unit housing, a video display device, memory such as volatile or non-volatile memory, processors such as microprocessors or digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices (e.g., a touch pad, a touch screen, an antenna, etc.), and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity; control motors for moving and/or adjusting components and/or quantities). A data processing system may be implemented utilizing suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

The term module, as used in the foregoing/following disclosure, may refer to a collection of one or more components that are arranged in a particular manner, or a collection of one or more general-purpose components that may be configured to operate in a particular manner at one or more particular points in time, and/or also configured to operate in one or more further manners at one or more further times. For example, the same hardware, or same portions of hardware, may be configured/reconfigured in sequential/parallel time(s) as a first type of module (e.g., at a first time), as a second type of module (e.g., at a second time, which may in some instances coincide with, overlap, or follow a first time), and/or as a third type of module (e.g., at a third time which may, in some instances, coincide with, overlap, or follow a first time and/or a second time), etc. Reconfigurable and/or controllable components (e.g., general purpose processors, digital signal processors, field programmable gate arrays, etc.) are capable of being configured as a first module that has a first purpose, then a second module that has a second purpose and then, a third module that has a third purpose, and so on. The transition of a reconfigurable and/or controllable component may occur in as little as a few nanoseconds, or may occur over a period of minutes, hours, or days.

In some such examples, at the time the component is configured to carry out the second purpose, the component may no longer be capable of carrying out that first purpose until it is reconfigured. A component may switch between configurations as different modules in as little as a few nanoseconds. A component may reconfigure on-the-fly, e.g., the reconfiguration of a component from a first module into a second module may occur just as the second module is needed. A component may reconfigure in stages, e.g., portions of a first module that are no longer needed may reconfigure into the second module even before the first module has finished its operation. Such reconfigurations may occur automatically, or may occur through prompting by an external source, whether that source is another component, an instruction, a signal, a condition, an external stimulus, or similar.

For example, a central processing unit of a personal computer may, at various times, operate as a module for displaying graphics on a screen, a module for writing data to a storage medium, a module for receiving user input, and a module for multiplying two large prime numbers, by configuring its logical gates in accordance with its instructions. Such reconfiguration may be invisible to the naked eye, and in some embodiments may include activation, deactivation, and/or re-routing of various portions of the component, e.g., switches, logic gates, inputs, and/or outputs. Thus, in the examples found in the foregoing/following disclosure, if an example includes or recites multiple modules, the example includes the possibility that the same hardware may implement more than one of the recited modules, either contemporaneously or at discrete times or timings. The implementation of multiple modules, whether using more components, fewer components, or the same number of components as the number of modules, is merely an implementation choice and does not generally affect the operation of the modules themselves. Accordingly, it should be understood that any recitation of multiple discrete modules in this disclosure includes implementations of those modules as any number of underlying components, including, but not limited to, a single component that reconfigures itself over time to carry out the functions of multiple modules, and/or multiple components that similarly reconfigure, and/or special purpose reconfigurable components.

In some instances, one or more components may be referred to herein as “configured to,” “configured by,” “configurable to,” “operable/operative to,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Those skilled in the art will recognize that such terms (for example “configured to”) generally encompass active-state components and/or inactive-state components and/or standby-state components, unless context requires otherwise.

While particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of the subject matter described herein. It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (for example, bodies of the appended claims) are generally intended as “open” terms (for example, the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to claims containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (for example, “a” and/or “an” should typically be interpreted to mean “at least one” or “one or more”); the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should typically be interpreted to mean at least the recited number (for example, the bare recitation of “two recitations,” without other modifiers, typically means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (for example, “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that typically a disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms unless context dictates otherwise. For example, the phrase “A or B” will be typically understood to include the possibilities of “A” or “B” or “A and B.”

The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples contain one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software (e.g., a high-level computer program serving as a hardware specification), firmware, or virtually any combination thereof, limited to patentable subject matter under 35 U.S.C. 101. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, can be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, limited to patentable subject matter under 35 U.S.C. 101, and that designing the circuitry and/or writing the code for the software (e.g., a high-level computer program serving as a hardware specification) and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subject matter described herein are capable of being distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link (e.g., transmitter, receiver, transmission logic, reception logic, etc.), etc.).

With respect to the appended claims, those skilled in the art will appreciate that recited operations therein may generally be performed in any order. Also, although various operational flows are presented in a sequence(s), it should be understood that the various operations may be performed in other orders than those which are illustrated or may be performed concurrently. Examples of such alternate orderings may include overlapping, interleaved, interrupted, reordered, incremental, preparatory, supplemental, simultaneous, reverse, or other variant orderings, unless context dictates otherwise. Furthermore, terms like “responsive to,” “related to,” or other past-tense adjectives are generally not intended to exclude such variants, unless context dictates otherwise.

While the disclosed subject matter has been described in terms of illustrative embodiments, it will be understood by those skilled in the art that various modifications can be made thereto without departing from the scope of the claimed subject matter as set forth in the claims.