US 10,007,263 B1Grant
Autonomous vehicle accident and emergency response
Issue Date:2018-06-26
•17 Claims
•15 Drawing Sheets
Abstract
Methods and systems for monitoring use, determining risk, and pricing insurance policies for a vehicle having one or more autonomous or semi-autonomous operation features are provided. According to certain aspects, with the customer's permission, it may be detected by sensors that an occupant of the autonomous or semi-autonomous vehicle is experiencing a medical emergency. A nearby medical facility may be determined based upon the vehicle location and the detected medical emergency. A route from the current vehicle location to the medical facility may be determined, and the autonomous or semi-autonomous vehicle may be automatically directed or routed to the medical facility. A message may also be generated and transmitted to the medical facility to alert them that a person in need of timely medical assistance is on the way. Life and auto insurance discounts may be generated for risk averse customers based upon their vehicles having the emergency response functionality.
Metadata
Assignee
- STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY
Inventors
- Brian Mark Fields
- Chien Che Huang
- Mohamed A. Wazeer
- Shawn C. Bennett
- Steven C. Cielocha
- Ronny S. Bryant
- Stephen Kohaus
- Terry Quakenbush
- Richard A. Novak
- Aaron Scott Chan
- Craig M. Main
- Weixin Wu
- Torri Wollenschlager
- Carol Marie Csanda
- Stacey Gorsuch
- Todd Binion
Application Information
Application Number:US 14/934,371
Filing Date:2015-11-06
Priority Date:2014-11-13
Art Unit:3661
Classifications
IPC:
G08B25/00G05D1/00G05D1/02G01C21/34G08B25/10A61B5/00A61B5/02B60W40/08
Field of Search:
G05D 1/0061G05D 1/0088G05D 1/0278G01C 21/3407B60W 2040/0818A61B 5/6893A61B 5/7282A61B 5/4064A61B 5/4094
Patent Drawings (15 sheets)
Description
Cross-Reference to Related Applications
[0001] This application claims the benefit of U.S. Provisional Application No. 62/079,533 (filed Nov. 13, 2014); U.S. Provisional Application No. 62/103,831 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,836 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,838 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,840 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,855 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,856 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,891 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,893 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,895 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,907 (filed Jan. 15, 2015); U.S. Provisional Application No. 62/103,911 (filed Jan. 15, 2015); and U.S. Provisional Application No. 62/103,914 (filed Jan. 15, 2015). The entirety of each of the foregoing provisional applications is incorporated by reference herein.
[0002] Additionally, the present application is related to co-pending U.S. patent application Ser. No. 14/934,326 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,333 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/931,339 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,343 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,345 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,347 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,352 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,355 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,357 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,361 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,381 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,385 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,388 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,393 (filed Nov. 6, 2015); co-pending U.S. patent application Ser. No. 14/934,400 (filed Nov. 6, 2015); and co-pending U.S. patent application Ser. No. 14/934,405 (filed Nov. 6, 2015).
Field
[0003] The present disclosure generally relates to systems and methods for operating, monitoring, assessing, or insuring autonomous or semi-autonomous vehicles.
Background
[0004] Vehicles are typically operated by a human vehicle operator who controls both steering and motive controls. Operator error, inattention, inexperience, misuse, or distraction leads to many vehicle accidents each year, resulting in injury and damage. Autonomous or semi-autonomous vehicles augment vehicle operators' information or replace vehicle operators' control commands to operate the vehicle in whole or part with computer systems based upon information from sensors within the vehicle.
[0005] Vehicle or automobile insurance exists to provide financial protection against physical damage and/or bodily injury resulting from traffic accidents and against liability that could arise therefrom. Typically, a customer purchases a vehicle insurance policy for a policy rate having a specified term. In exchange for payments from the insured customer, the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy. The payments from the insured are generally referred to as “premiums,” and typically are paid on behalf of the insured over time at periodic intervals. An insurance policy may remain “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy. An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when premium payments are not being paid or if the insured or the insurer cancels the policy.
[0006] Premiums may be typically determined based upon a selected level of insurance coverage, location of vehicle operation, vehicle model, and characteristics or demographics of the vehicle operator. The characteristics of a vehicle operator that affect premiums may include age, years operating vehicles of the same class, prior incidents involving vehicle operation, and losses reported by the vehicle operator to the insurer or a previous insurer. Past and current premium determination methods do not, however, account for use of autonomous vehicle operating features. The present embodiments may, inter alia, alleviate this and/or other drawbacks associated with conventional techniques.
Brief Summary
[0007] The present embodiments may be related to autonomous or semi-autonomous vehicle functionality, including driverless operation, accident avoidance, or collision warning systems. These autonomous vehicle operation features may either assist the vehicle operator to more safely or efficiently operate a vehicle or may take full control of vehicle operation under some or all circumstances. The present embodiments may also facilitate risk assessment and premium determination for vehicle insurance policies covering vehicles with autonomous operation features. For instance, a consumer may opt-in to a rewards program that rewards them, such as in the form of insurance discounts, for affirmatively sharing data related to their vehicles and/or autonomous features with an insurance provider.
[0008] In accordance with the described embodiments, the disclosure herein generally addresses systems and methods for directing a route of an autonomous or semi-autonomous vehicle during an emergency. A computer associated with the vehicle (such as an on-board computer, mobile device, or server communicatively connected to the vehicle) may (1) detect that an occupant of the vehicle is experiencing a medical emergency; (2) generate an indication of the detected medical emergency; (3) determine a vehicle location of the vehicle; (4) identify a medical facility based upon the vehicle location and the indication of the detected medical emergency; (5) determine one or more routes from the vehicle location to the medical facility; and/or (6) cause the vehicle to automatically travel to a medical facility along the determined one or more routes. The vehicle may be controlled by one or more autonomous operation features during travel along the determined one or more routes. Causing the vehicle to automatically travel to the medical facility may include causing the one or more autonomous operation features to engage, causing the one or more autonomous operation features to control the operation of the vehicle along the determined one or more routes to the medical facility, and/or causing the vehicle to park at an appropriate location upon arrival at the medical facility. The autonomous operation features controlling the vehicle during travel may include the following: steering, accelerating, braking, parking, pedestrian detection, artificial intelligence, vehicle navigation, vehicle positioning, and/or remote vehicle location determination.
[0009] Some embodiment may further include communicating a message to one or more of the medical facility, a police department, a fire department, and/or a family member of the occupant. Such message may include a current location of the autonomous or semi-autonomous vehicle, the determined one or more routes to the medical facility, an estimated time of arrival of the autonomous or semi-autonomous vehicle at the medical facility, and/or information regarding the detected medical emergency.
[0010] In further embodiments, the medical emergency may be detected by a biometric device within the vehicle. The detected medical emergency may include one or more of a heart attack, a stroke, and/or a seizure. The vehicle location may be determined using a Global Positioning System (GPS) receiver.
[0011] In each of the embodiments or aspects described above, the methods may be provided in corresponding computer systems including at least one or more processors and a non-transitory program memory coupled to the one or more processors and storing executable instructions. The computer systems may further include or be communicatively connected to one or more sensors, communication components or devices, or other equipment as described herein. In yet another aspect, a tangible, non-transitory computer-readable medium storing instructions corresponding to each of the embodiments or aspects described above may be provided. Each of the methods or executable instructions of the computer systems or computer-readable media may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Brief Description of the Drawings
[0012] Advantages will become more apparent to those skilled in the art from the following description of the preferred embodiments which have been shown and described by way of illustration. As will be realized, the present embodiments may be capable of other and different embodiments, and their details are capable of modification in various respects. Accordingly, the drawings and description are to be regarded as illustrative in nature and not as restrictive.
[0013] The figures described below depict various aspects of the applications, methods, and systems disclosed herein. It should be understood that each figure depicts an embodiment of a particular aspect of the disclosed applications, systems and methods, and that each of the figures is intended to accord with a possible embodiment thereof. Furthermore, wherever possible, the following description refers to the reference numerals included in the following figures, in which features depicted in multiple figures are designated with consistent reference numerals.
[0014] FIG. 1 illustrates a block diagram of an exemplary computer network, a computer server, a mobile device, and an on-board computer for implementing autonomous vehicle operation, monitoring, evaluation, and insurance processes in accordance with the described embodiments;
[0015] FIG. 2 illustrates a block diagram of an exemplary on-board computer or mobile device;
[0016] FIG. 3 illustrates a flow diagram of an exemplary autonomous vehicle operation method in accordance with the presently described embodiments;
[0017] FIG. 4 illustrates a flow diagram of an exemplary monitoring method during vehicle operation in accordance with the presently described embodiments;
[0018] FIG. 5 illustrates a flow diagram of an exemplary operating status assessment method in accordance with the presently described embodiments;
[0019] FIG. 6 illustrates a flow diagram of an exemplary operating status monitoring method in accordance with the presently described embodiments;
[0020] FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-off methods in accordance with the presently described embodiments;
[0021] FIG. 8 illustrates a flow diagram depicting an exemplary vehicle operator identification method in accordance with the presently described embodiments;
[0022] FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring and evaluation method in accordance with the presently described embodiments;
[0023] FIG. 10 illustrates a flow diagram depicting an exemplary cost comparison method in accordance with the presently described embodiments; and
[0024] FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operation feature update method in accordance with the presently described embodiments;
[0025] FIG. 12 illustrates a flow diagram depicting an exemplary autonomous vehicle repair method in accordance with the presently described embodiments; and
[0026] FIG. 13 illustrates a flow diagram depicting an exemplary infrastructure communication method in accordance with the presently described embodiments.
Detailed Description
[0027] The systems and methods disclosed herein generally relate to evaluating, monitoring, and managing risks related to the operation of autonomous or semi-autonomous vehicles having autonomous (or semi-autonomous) operation features. The systems and methods further relate to pricing and processing vehicle insurance policies for autonomous or semi-autonomous vehicles. The autonomous operation features may take full control of the vehicle under certain conditions, viz. fully autonomous operation, or the autonomous operation features may assist the vehicle operator in operating the vehicle, viz. partially autonomous operation. Fully autonomous operation features may include systems within the vehicle that pilot the vehicle to a destination with or without a vehicle operator present (e.g., an operating system for a driverless car). Partially autonomous operation features may assist the vehicle operator in limited ways (e.g., automatic braking or collision avoidance systems).
[0028] The type and quality of the autonomous operation features may affect the risks related to operating a vehicle, both individually and/or in combination. In addition, configurations and settings of the autonomous operation features may further impact the risks. To account for the effects on such risks, some embodiments evaluate the quality of each autonomous operation feature and/or combination of features. Additional embodiments evaluate the risks associated with the vehicle operator interacting with the autonomous operation features. Further embodiments address the relative risks associated with control of some aspects of vehicle control by the autonomous operation features or by the vehicle operator. Still further embodiments address use of information received or generated by the autonomous operation features to manage risk and/or damage.
[0029] Some autonomous operation features may be adapted for use under particular conditions, such as city driving or highway driving. Additionally, the vehicle operator may be able to configure settings relating to the features or may enable or disable the features individually or in groups. For example, the vehicle operator may select a mode of operation for the autonomous or semi-autonomous vehicle, which may adjust settings for one or more autonomous operation features. Therefore, some embodiments monitor use of the autonomous operation features, which may include the settings or levels of feature use during vehicle operation, as well as the selection of features or settings of the autonomous operation features chosen by the vehicle operator.
[0030] Information obtained by monitoring feature usage may be used to determine risk levels associated with vehicle operation, either generally or in relation to a vehicle operator. In such situations, total risk may be determined by a weighted combination of the risk levels associated with operation while autonomous operation features are enabled (with relevant settings) and the risk levels associated with operation while autonomous operation features are disabled. For fully autonomous vehicles, settings or configurations relating to vehicle operation may be monitored and used in determining vehicle operating risk.
[0031] In addition to use in controlling the vehicle, information regarding the risks associated with vehicle operation with and without the autonomous operation features may then be used to determine risk categories or premiums for a vehicle insurance policy covering a vehicle with autonomous operation features. Risk category or price may be determined based upon factors relating to the evaluated effectiveness of the autonomous vehicle features. The risk or price determination may also include traditional factors, such as location, vehicle type, and level of vehicle use. For fully autonomous vehicles, factors relating to vehicle operators may be excluded entirely. For partially autonomous vehicles, factors relating to vehicle operators may be reduced in proportion to the evaluated effectiveness and monitored usage levels of the autonomous operation features. For vehicles with autonomous communication features that obtain information from external sources (e.g., other vehicles or infrastructure), the risk level and/or price determination may also include an assessment of the availability of external sources of information. Location and/or timing of vehicle use may thus be monitored and/or weighted to determine the risk associated with operation of the vehicle.
Autonomous Automobile Insurance
[0032] The present embodiments may relate to assessing and pricing insurance based upon autonomous (or semi-autonomous) functionality of a vehicle, utilization of the autonomous (or semi-autonomous) functionality of the vehicle, and/or operation of the vehicle by a human operator. In some embodiments, the vehicle operator may not control the operations of the vehicle directly, in which case the assessment, rating, and pricing of insurance may exclude consideration of the vehicle operator. A smart vehicle may maneuver itself without human intervention and/or include sensors, processors, computer instructions, and/or other components that may perform or direct certain actions conventionally performed by a human operator.
[0033] An analysis of how artificial intelligence facilitates avoiding accidents and/or mitigates the severity of accidents may be used to build a database and/or model of risk assessment. After which, automobile insurance risk and/or premiums (as well as insurance discounts, rewards, and/or points) may be adjusted based upon autonomous or semi-autonomous vehicle functionality, such as by groups of autonomous or semi-autonomous functionality or individual features. In one aspect, an evaluation may be performed on how artificial intelligence, and the usage thereof, impacts automobile accidents and/or automobile insurance claims.
[0034] The types of autonomous or semi-autonomous vehicle-related functionality or technology that may be used with the present embodiments to replace human driver actions may include and/or be related to the following types of functionality: (a) fully autonomous (driverless); (b) limited driver control; (c) vehicle-to-vehicle (V2V) wireless communication; (d) vehicle-to-infrastructure (and/or vice versa) wireless communication; (e) automatic or semi-automatic steering; (f) automatic or semi-automatic acceleration; (g) automatic or semi-automatic braking; (h) automatic or semi-automatic blind spot monitoring; (i) automatic or semi-automatic collision warning; (j) adaptive cruise control; (k) automatic or semi-automatic parking/parking assistance; (l) automatic or semi-automatic collision preparation (windows roll up, seat adjusts upright, brakes pre-charge, etc.); (m) driver acuity/alertness monitoring; (n) pedestrian detection; (o) autonomous or semi-autonomous backup systems; (p) road mapping systems; (q) software security and anti-hacking measures; (r) theft prevention/automatic return; (s) automatic or semi-automatic driving without occupants; and/or other functionality. Additionally or alternatively, the autonomous or semi-autonomous functionality or technology may include and/or may be related to: (t) driver alertness or responsive monitoring; (u) pedestrian detection; (v) artificial intelligence and/or back-up systems; (w) navigation or GPS-related systems; (x) security and/or anti-hacking measures; and/or (y) theft prevention systems.
[0035] The adjustments to automobile insurance rates or premiums based upon the autonomous or semi-autonomous vehicle-related functionality or technology may take into account the impact of such functionality or technology on the likelihood of a vehicle accident or collision occurring. For instance, a processor may analyze historical accident information and/or test data involving vehicles having autonomous or semi-autonomous functionality. Factors that may be analyzed and/or accounted for that are related to insurance risk, accident information, or test data may include (1) point of impact; (2) type of road; (3) time of day; (4) weather conditions; (5) road construction; (6) type/length of trip; (7) vehicle style; (8) level of pedestrian traffic; (9) level of vehicle congestion; (10) atypical situations (such as manual traffic signaling); (11) availability of internet connection for the vehicle; and/or other factors. These types of factors may also be weighted according to historical accident information, predicted accidents, vehicle trends, test data, and/or other considerations.
[0036] In one aspect, the benefit of one or more autonomous or semi-autonomous functionalities or capabilities may be determined, weighted, and/or otherwise characterized. For instance, the benefit of certain autonomous or semi-autonomous functionality may be substantially greater in city or congested traffic, as compared to open road or country driving traffic. Additionally or alternatively, certain autonomous or semi-autonomous functionality may only work effectively below a certain speed, e.g., during city driving or driving in congestion. Other autonomous or semi-autonomous functionality may operate more effectively on the highway and away from city traffic, such as cruise control. Further individual autonomous or semi-autonomous functionality may be impacted by weather, such as rain or snow, and/or time of day (day light versus night). As an example, fully automatic or semi-automatic lane detection warnings may be impacted by rain, snow, ice, and/or the amount of sunlight (all of which may impact the imaging or visibility of lane markings painted onto a road surface, and/or road markers or street signs).
[0037] Automobile insurance premiums, rates, discounts, rewards, refunds, points, or other costs may be adjusted based upon the percentage of time or vehicle usage that the vehicle is the driver, i.e., the amount of time a specific driver uses each type of autonomous (or even semi-autonomous) vehicle functionality. Such premiums, rates, discounts, rewards, refunds, points, or other costs may further be adjusted based upon the extent of use of the autonomous operation features, including settings or modes impacting the operation of the autonomous operation features. Moreover, information regarding the vehicle environment during use (e.g., weather, traffic, time of day, etc.) may be included in insurance adjustment determinations, as may traditional information regarding one or more vehicle operators (and the extent to which each vehicle operator uses the vehicle).
[0038] Such usage information for a particular vehicle may be gathered over time and/or via remote wireless communication with the vehicle. One embodiment may involve a processor on the vehicle, such as within a vehicle control system or dashboard, monitoring in real-time the vehicle operator and/or the use of autonomous operation features while the vehicle is operating. Other types of monitoring may be remotely performed, such as via wireless communication between the vehicle and a remote server, or wireless communication between a vehicle-mounted dedicated device (that is configured to gather autonomous or semi-autonomous functionality usage information) and a remote server.
[0039] Additionally, in some embodiments, the vehicle may transmit and/or receive communications to or from external sources, such as other vehicles (V2V), infrastructure (e.g., a bridge, traffic light, railroad crossing, toll both, marker, sign, or other equipment along the side of a road or highway), pedestrians, databases, or other information sources external to the vehicle. Such communication may allow the vehicle to obtain information regarding other vehicles, obstacles, road conditions, or environmental conditions that could not be detected by sensors disposed within the vehicle. For example, V2V communication may allow a vehicle to identify other vehicles approaching an intersection even when the direct line between the vehicle and the other vehicles is obscured by buildings. As another example, the V2V wireless communication from a first vehicle to a second vehicle (following the first vehicle) may indicate that the first vehicle is braking, which may include the degree to which the vehicle is braking. In response, the second vehicle may automatically or autonomously brake in advance of detecting the deceleration of the first vehicle based upon sensor data.
[0040] Insurance premiums, rates, ratings, discounts, rewards, special offers, points, programs, refunds, claims, claim amounts, or other costs associated with an insurance policy may be adjusted for, or may otherwise take into account, the foregoing functionality and/or the other functionality described herein. For instance, insurance policies may be updated based upon installed autonomous operation features, the extent of use of the autonomous operation features, V2V wireless communication, and/or vehicle-to-infrastructure or infrastructure-to-vehicle wireless communication. The present embodiments may assess and price insurance risks at least in part based upon autonomous operation features that replace some actions of the vehicle operator in controlling the vehicle, including settings and operating status of the autonomous operation features.
Exemplary Autonomous Vehicle Operation System
[0041] FIG. 1 illustrates a block diagram of an exemplary autonomous vehicle insurance system 100 on which the exemplary methods described herein may be implemented. The high-level architecture includes both hardware and software applications, as well as various data communications channels for communicating data between the various hardware and software components. The autonomous vehicle insurance system 100 may be roughly divided into front-end components 102 and back-end components 104. The front-end components 102 may obtain information regarding a vehicle 108 (e.g., a car, truck, motorcycle, etc.) and the surrounding environment. An on-board computer 114 may utilize this information to operate the vehicle 108 according to an autonomous operation feature or to assist the vehicle operator in operating the vehicle 108. To monitor the vehicle 108, the front-end components 102 may include one or more sensors 120 installed within the vehicle 108 that may communicate with the on-board computer 114. The front-end components 102 may further process the sensor data using the on-board computer 114 or a mobile device 110 (e.g., a smart phone, a tablet computer, a special purpose computing device, etc.) to determine when the vehicle is in operation and information regarding the vehicle. In some embodiments of the system 100, the front-end components 102 may communicate with the back-end components 104 via a network 130. Either the on-board computer 114 or the mobile device 110 may communicate with the back-end components 104 via the network 130 to allow the back-end components 104 to record information regarding vehicle usage. The back-end components 104 may use one or more servers 140 to receive data from the front-end components 102, determine use and effectiveness of autonomous operation features, determine risk levels or premium price, and/or facilitate purchase or renewal of an autonomous vehicle insurance policy.
[0042] The front-end components 102 may be disposed within or communicatively connected to one or more on-board computers 114, which may be permanently or removably installed in the vehicle 108. The on-board computer 114 may interface with the one or more sensors 120 within the vehicle 108 (e.g., an ignition sensor, an odometer, a system clock, a speedometer, a tachometer, an accelerometer, a gyroscope, a compass, a geolocation unit, a camera, a distance sensor, etc.), which sensors may also be incorporated within or connected to the on-board computer 114. The front-end components 102 may further include a communication component 122 to transmit information to and receive information from external sources, including other vehicles, infrastructure, or the back-end components 104. In some embodiments, the mobile device 110 may supplement the functions performed by the on-board computer 114 described herein by, for example, sending or receiving information to and from the mobile server 140 via the network 130. In other embodiments, the on-board computer 114 may perform all of the functions of the mobile device 110 described herein, in which case no mobile device 110 may be present in the system 100. Either or both of the mobile device 110 or on-board computer 114 may communicate with the network 130 over links 112 and 118, respectively. Additionally, the mobile device 110 and on-board computer 114 may communicate with one another directly over link 116.
[0043] The mobile device 110 may be either a general-use personal computer, cellular phone, smart phone, tablet computer, phablet, wearable electronics, PDA (personal digital assistant), smart glasses, smart watches, smart bracelet, pager, computing device configured for wired or wireless RF (radio frequency) communication, a dedicated vehicle use monitoring device, and/or other mobile computing device. Although only one mobile device 110 is illustrated, it should be understood that a plurality of mobile devices 110 may be used in some embodiments. The on-board computer 114 may be a general-use on-board computer capable of performing many functions relating to vehicle operation or a dedicated computer for autonomous vehicle operation. Further, the on-board computer 114 may be installed by the manufacturer of the vehicle 108 or as an aftermarket modification or addition to the vehicle 108. In some embodiments or under certain conditions, the mobile device 110 or on-board computer 114 may function as thin-client devices that outsource some or most of the processing to the server 140.
[0044] The sensors 120 may be removably or fixedly installed within the vehicle 108 and may be disposed in various arrangements to provide information to the autonomous operation features. Among the sensors 120 may be included one or more of a GPS (Global Positioning System) unit, other satellite-based navigation unit, a radar unit, a LIDAR (Light Detection and Ranging) unit, an ultrasonic sensor, an infrared sensor, a camera, an accelerometer, a tachometer, and/or a speedometer. Some of the sensors 120 (e.g., radar, LIDAR, or camera units) may actively or passively scan the vehicle environment for obstacles (e.g., other vehicles, buildings, pedestrians, etc.), lane markings, or signs or signals. Other sensors 120 (e.g., GPS, accelerometer, or tachometer units) may provide data for determining the location or movement of the vehicle 108. Other sensors 120 may be directed to the interior or passenger compartment of the vehicle 108, such as cameras, microphones, pressure sensors, thermometers, or similar sensors to monitor the vehicle operator and/or passengers within the vehicle 108. Information generated or received by the sensors 120 may be communicated to the on-board computer 114 or the mobile device 110 for use in autonomous vehicle operation.
[0045] In some embodiments, the communication component 122 may receive information from external sources, such as other vehicles or infrastructure. The communication component 122 may also send information regarding the vehicle 108 to external sources. To send and receive information, the communication component 122 may include a transmitter and a receiver designed to operate according to predetermined specifications, such as the dedicated short-range communication (DSRC) channel, wireless telephony, Wi-Fi, or other existing or later-developed communications protocols. The received information may supplement the data received from the sensors 120 to implement the autonomous operation features. For example, the communication component 122 may receive information that an autonomous vehicle ahead of the vehicle 108 is reducing speed, allowing the adjustments in the autonomous operation of the vehicle 108.
[0046] In further embodiments, the front-end components may include an infrastructure communication device 124 for monitoring the status of one or more infrastructure components 126. The infrastructure communication device 124 may include or be communicatively connected to one or more sensors (not shown) for detecting information relating to the condition of the infrastructure component 126. The sensors (not shown) may generate data relating to weather conditions, traffic conditions, or operating status of the infrastructure component 126. The infrastructure communication device 124 may be configured to receive the sensor data generated and determine a condition of the infrastructure component 126, such as weather conditions, road integrity, construction, traffic, available parking spaces, etc. The infrastructure communication device 124 may further be configured to communicate information to vehicles 108 via the communication component 122. In some embodiments, the infrastructure communication device 124 may receive information from the vehicles 108, while, in other embodiments, the infrastructure communication device 124 may only transmit information to the vehicles 108.
[0047] In addition to receiving information from the sensors 120, the on-board computer 114 may directly or indirectly control the operation of the vehicle 108 according to various autonomous operation features. The autonomous operation features may include software applications or routines implemented by the on-board computer 114 to control the steering, braking, or throttle of the vehicle 108. To facilitate such control, the on-board computer 114 may be communicatively connected to the controls or components of the vehicle 108 by various electrical or electromechanical control components (not shown). In embodiments involving fully autonomous vehicles, the vehicle 108 may be operable only through such control components (not shown). In other embodiments, the control components may be disposed within or supplement other vehicle operator control components (not shown), such as steering wheels, accelerator or brake pedals, or ignition switches.
[0048] In some embodiments, the front-end components 102 may communicate with the back-end components 104 via the network 130. The network 130 may be a proprietary network, a secure public Internet, a virtual private network or some other type of network, such as dedicated access lines, plain ordinary telephone lines, satellite links, cellular data networks, combinations of these. Where the network 130 comprises the Internet, data communications may take place over the network 130 via an Internet communication protocol.
[0049] The back-end components 104 may include one or more servers 140. Each server 140 may include one or more computer processors adapted and configured to execute various software applications and components of the autonomous vehicle insurance system 100, in addition to other software applications. The server 140 may further include a database 146, which may be adapted to store data related to the operation of the vehicle 108 and its autonomous operation features. Such data might include, for example, dates and times of vehicle use, duration of vehicle use, use and settings of autonomous operation features, speed of the vehicle 108, RPM or other tachometer readings of the vehicle 108, lateral and longitudinal acceleration of the vehicle 108, incidents or near collisions of the vehicle 108, communication between the autonomous operation features and external sources, environmental conditions of vehicle operation (e.g., weather, traffic, road condition, etc.), errors or failures of autonomous operation features, or other data relating to use of the vehicle 108 and the autonomous operation features, which may be uploaded to the server 140 via the network 130. The server 140 may access data stored in the database 146 when executing various functions and tasks associated with the evaluating feature effectiveness or assessing risk relating to an autonomous vehicle.
[0050] Although the autonomous vehicle insurance system 100 is shown to include one vehicle 108, one mobile device 110, one on-board computer 114, and one server 140, it should be understood that different numbers of vehicles 108, mobile devices 110, on-board computers 114, and/or servers 140 may be utilized. For example, the system 100 may include a plurality of servers 140 and hundreds of mobile devices 110 or on-board computers 114, all of which may be interconnected via the network 130. Furthermore, the database storage or processing performed by the one or more servers 140 may be distributed among a plurality of servers 140 in an arrangement known as “cloud computing.” This configuration may provide various advantages, such as enabling near real-time uploads and downloads of information as well as periodic uploads and downloads of information. This may in turn support a thin-client embodiment of the mobile device 110 or on-board computer 114 discussed herein.
[0051] The server 140 may have a controller 155 that is operatively connected to the database 146 via a link 156. It should be noted that, while not shown, additional databases may be linked to the controller 155 in a known manner. For example, separate databases may be used for autonomous operation feature information, vehicle insurance policy information, and vehicle use information. The controller 155 may include a program memory 160, a processor 162 (which may be called a microcontroller or a microprocessor), a random-access memory (RAM) 164, and an input/output (I/O) circuit 166, all of which may be interconnected via an address/data bus 165. It should be appreciated that although only one microprocessor 162 is shown, the controller 155 may include multiple microprocessors 162. Similarly, the memory of the controller 155 may include multiple RAMs 164 and multiple program memories 160. Although the I/O circuit 166 is shown as a single block, it should be appreciated that the I/O circuit 166 may include a number of different types of I/O circuits. The RAM 164 and program memories 160 may be implemented as semiconductor memories, magnetically readable memories, or optically readable memories, for example. The controller 155 may also be operatively connected to the network 130 via a link 135.
[0052] The server 140 may further include a number of software applications stored in a program memory 160. The various software applications on the server 140 may include an autonomous operation information monitoring application 141 for receiving information regarding the vehicle 108 and its autonomous operation features, a feature evaluation application 142 for determining the effectiveness of autonomous operation features under various conditions, a compatibility evaluation application 143 for determining the effectiveness of combinations of autonomous operation features, a risk assessment application 144 for determining a risk category associated with an insurance policy covering an autonomous vehicle, and an autonomous vehicle insurance policy purchase application 145 for offering and facilitating purchase or renewal of an insurance policy covering an autonomous vehicle. The various software applications may be executed on the same computer processor or on different computer processors.
[0053] The various software applications may include various software routines stored in the program memory 160 to implement various modules using the process 162. Additionally, or alternatively, the software applications or routines may interact with various hardware modules that may be installed within or connected to the server 140. Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments. Such modules may include a vehicle control module for determining and implementing control decisions to operate the vehicle 108, a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of the vehicle 108, a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of the vehicle 108, an alert module for generating and presenting alerts regarding the vehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of the vehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator or vehicle 108, a use cost module for determining costs associated with operation of the vehicle 108, a comparison module for comparing one or more costs associated with owning or operating the vehicle 108, an update module for updating an autonomous operation feature of the vehicle 108, or other modules.
Exemplary Mobile Device or On-Board Computer
[0054] FIG. 2 illustrates a block diagram of an exemplary mobile device 110 and/or an exemplary on-board computer 114 consistent with the system 100. The mobile device 110 and/or on-board computer 114 may include a display 202, a GPS unit 206, a communication unit 220, an accelerometer 224, one or more additional sensors (not shown), a user-input device (not shown), and/or, like the server 140, a controller 204. In some embodiments, the mobile device 110 and on-board computer 114 may be integrated into a single device, or either may perform the functions of both. The on-board computer 114 (or mobile device 110) may interface with the sensors 120 to receive information regarding the vehicle 108 and its environment, which information may be used by the autonomous operation features to operate the vehicle 108.
[0055] Similar to the controller 155, the controller 204 may include a program memory 208, one or more microcontrollers or microprocessors (MP) 210, a RAM 212, and an I/O circuit 216, all of which are interconnected via an address/data bus 214. The program memory 208 may include an operating system 226, a data storage 228, a plurality of software applications 230, and/or a plurality of software routines 240. The operating system 226, for example, may include one of a plurality of general purpose or mobile platforms, such as the Android™, iOS®, or Windows® systems, developed by Google Inc., Apple Inc., and Microsoft Corporation, respectively. Alternatively, the operating system 226 may be a custom operating system designed for autonomous vehicle operation using the on-board computer 114. The data storage 228 may include data such as user profiles and preferences, application data for the plurality of applications 230, routine data for the plurality of routines 240, and other data related to the autonomous operation features. In some embodiments, the controller 204 may also include, or otherwise be communicatively connected to, other data storage mechanisms (e.g., one or more hard disk drives, optical storage drives, solid state storage devices, etc.) that reside within the vehicle 108.
[0056] As discussed with reference to the controller 155, it should be appreciated that although FIG. 2 depicts only one microprocessor 210, the controller 204 may include multiple microprocessors 210. Similarly, the memory of the controller 204 may include multiple RAMs 212 and multiple program memories 208. Although FIG. 2 depicts the I/O circuit 216 as a single block, the I/O circuit 216 may include a number of different types of I/O circuits. The controller 204 may implement the RAMs 212 and the program memories 208 as semiconductor memories, magnetically readable memories, or optically readable memories, for example.
[0057] The one or more processors 210 may be adapted and configured to execute any of one or more of the plurality of software applications 230 or any one or more of the plurality of software routines 240 residing in the program memory 204, in addition to other software applications. One of the plurality of applications 230 may be an autonomous vehicle operation application 232 that may be implemented as a series of machine-readable instructions for performing the various tasks associated with implementing one or more of the autonomous operation features according to the autonomous vehicle operation method 300. Another of the plurality of applications 230 may be an autonomous communication application 234 that may be implemented as a series of machine-readable instructions for transmitting and receiving autonomous operation information to or from external sources via the communication unit 220. Still another application of the plurality of applications 230 may include an autonomous operation monitoring application 236 that may be implemented as a series of machine-readable instructions for sending information regarding autonomous operation of the vehicle to the server 140 via the network 130.
[0058] The plurality of software applications 230 may call various of the plurality of software routines 240 to perform functions relating to autonomous vehicle operation, monitoring, or communication. In some embodiments, the plurality of software routines may further assess risk levels or determine insurance policy costs and adjustments. One of the plurality of software routines 240 may be a configuration routine 242 to receive settings from the vehicle operator to configure the operating parameters of an autonomous operation feature. Another of the plurality of software routines 240 may be a sensor control routine 244 to transmit instructions to a sensor 120 and receive data from the sensor 120. Still another of the plurality of software routines 240 may be an autonomous control routine 246 that performs a type of autonomous control, such as collision avoidance, lane centering, and/or speed control. In some embodiments, the autonomous vehicle operation application 232 may cause a plurality of autonomous control routines 246 to determine control actions required for autonomous vehicle operation. Similarly, one of the plurality of software routines 240 may be a monitoring and reporting routine 248 that monitors and transmits information regarding autonomous vehicle operation to the server 140 via the network 130. Yet another of the plurality of software routines 240 may be an autonomous communication routine 250 for receiving and transmitting information between the vehicle 108 and external sources to improve the effectiveness of the autonomous operation features.
[0059] Any of the plurality of software routines 240 may be designed to operate independently of the software applications 230 or in conjunction with the software applications 230 to implement modules associated with the methods discussed herein using the microprocessor 210 of the controller 204. Additionally, or alternatively, the software applications 230 or software routines 240 may interact with various hardware modules that may be installed within or connected to the mobile device 110 or the on-board computer 114. Such modules may implement part of all of the various exemplary methods discussed herein or other related embodiments.
[0060] For instance, such modules may include a vehicle control module for determining and implementing control decisions to operate the vehicle 108, a system status module for determining the operating status of autonomous operation features, a monitoring module for monitoring the operation of the vehicle 108, a remediation module for correcting abnormal operating states of autonomous operation features, an insurance module for determining risks and costs associated with operation of the vehicle 108, an alert module for generating and presenting alerts regarding the vehicle 108 or the vehicle operator, a risk assessment module for determining risks associated with operation of the vehicle 108 by the autonomous operation features or by the vehicle operator, an identification module for identifying or verifying the identity of the vehicle operator, an information module for obtaining information regarding a vehicle operator or vehicle 108, a use cost module for determining costs associated with operation of the vehicle 108, a comparison module for comparing one or more costs associated with owning or operating the vehicle 108, an update module for updating an autonomous operation feature of the vehicle 108, and/or other modules.
[0061] When implementing the exemplary autonomous vehicle operation method 300, the controller 204 of the on-board computer 114 may implement a vehicle control module by the autonomous vehicle operation application 232 to communicate with the sensors 120 to receive information regarding the vehicle 108 and its environment and process that information for autonomous operation of the vehicle 108. In some embodiments, including external source communication via the communication component 122 or the communication unit 220, the controller 204 may further implement a communication module based upon the autonomous communication application 234 to receive information for external sources, such as other autonomous vehicles, smart infrastructure (e.g., electronically communicating roadways, traffic signals, or parking structures), or other sources of relevant information (e.g., weather, traffic, local amenities). Some external sources of information may be connected to the controller 204 via the network 130, such as the server 140 or internet-connected third-party databases (not shown). Although the autonomous vehicle operation application 232 and the autonomous communication application 234 are shown as two separate applications, it should be understood that the functions of the autonomous operation features may be combined or separated into any number of the software applications 230 or the software routines 240.
[0062] In some embodiments, the controller 204 may further implement a monitoring module by the autonomous operation monitoring application 236 to communicate with the server 140 to provide information regarding autonomous vehicle operation. This may include information regarding settings or configurations of autonomous operation features, data from the sensors 120 regarding the vehicle environment, data from the sensors 120 regarding the response of the vehicle 108 to its environment, communications sent or received using the communication component 122 or the communication unit 220, operating status of the autonomous vehicle operation application 232 and the autonomous communication application 234, and/or commands sent from the on-board computer 114 to the control components (not shown) to operate the vehicle 108. The information may be received and stored by the server 140 implementing the autonomous operation information monitoring application 141, and the server 140 may then determine the effectiveness of autonomous operation under various conditions by implementing the feature evaluation application 142 and the compatibility evaluation application 143. The effectiveness of autonomous operation features and the extent of their use may be further used to determine risk associated with operation of the autonomous vehicle by the server 140 implementing a risk assessment module or insurance module associated with the risk assessment application 144.
[0063] In addition to connections to the sensors 120, the mobile device 110 or the on-board computer 114 may include additional sensors, such as the GPS unit 206 or the accelerometer 224, which may provide information regarding the vehicle 108 for autonomous operation and other purposes. Furthermore, the communication unit 220 may communicate with other autonomous vehicles, infrastructure, or other external sources of information to transmit and receive information relating to autonomous vehicle operation. The communication unit 220 may communicate with the external sources via the network 130 or via any suitable wireless communication protocol network, such as wireless telephony (e.g., GSM, CDMA, LTE, etc.), Wi-Fi (802.11 standards), WiMAX, Bluetooth, infrared or radio frequency communication, etc. Furthermore, the communication unit 220 may provide input signals to the controller 204 via the I/O circuit 216. The communication unit 220 may also transmit sensor data, device status information, control signals, and/or other output from the controller 204 to one or more external sensors within the vehicle 108, mobile devices 110, on-board computers 114, and/or servers 140.
[0064] The mobile device 110 and/or the on-board computer 114 may include a user-input device (not shown) for receiving instructions or information from the vehicle operator, such as settings relating to an autonomous operation feature. The user-input device (not shown) may include a “soft” keyboard that is displayed on the display 202, an external hardware keyboard communicating via a wired or a wireless connection (e.g., a Bluetooth keyboard), an external mouse, a microphone, or any other suitable user-input device. The user-input device (not shown) may also include a microphone capable of receiving user voice input.
Exemplary Autonomous Vehicle Operation Method
[0065] FIG. 3 illustrates a flow diagram of an exemplary autonomous vehicle operation method 300, which may be implemented by the autonomous vehicle insurance system 100. The method 300 may begin at block 302 when the controller 204 receives a start signal. The start signal may be a command from the vehicle operator through the user-input device to enable or engage one or more autonomous operation features of the vehicle 108. In some embodiments, the vehicle operator 108 may further specify settings or configuration details for the autonomous operation features. For fully autonomous vehicles, the settings may relate to one or more destinations, route preferences, fuel efficiency preferences, speed preferences, and/or other configurable settings relating to the operation of the vehicle 108. In some embodiments, fully autonomous vehicles may include additional features or settings permitting them to operate without passengers or vehicle operators within the vehicle. For example, a fully autonomous vehicle may receive an instruction to find a parking space within the general vicinity, which the vehicle may do without the vehicle operator. The vehicle may then be returned to a selected location by a request from the vehicle operator via a mobile device 110 or otherwise. This feature may further be adapted to return a fully autonomous vehicle if lost or stolen.
[0066] For other autonomous vehicles, the settings may include enabling or disabling particular autonomous operation features, specifying thresholds for autonomous operation, specifying warnings or other information to be presented to the vehicle operator, specifying autonomous communication types to send or receive, specifying conditions under which to enable or disable autonomous operation features, and/or specifying other constraints on feature operation. For example, a vehicle operator may set the maximum speed for an adaptive cruise control feature with automatic lane centering. In some embodiments, the settings may further include a specification of whether the vehicle 108 should be operating as a fully or partially autonomous vehicle. In embodiments where only one autonomous operation feature is enabled, the start signal may consist of a request to perform a particular task (e.g., autonomous parking) and/or to enable a particular feature (e.g., autonomous braking for collision avoidance). In other embodiments, the start signal may be generated automatically by the controller 204 based upon predetermined settings (e.g., when the vehicle 108 exceeds a certain speed and/or is operating in low-light conditions). In some embodiments, the controller 204 may generate a start signal when communication from an external source is received (e.g., when the vehicle 108 is on a smart highway or near another autonomous vehicle).
[0067] After receiving the start signal at block 302, the controller 204 may receive sensor data from the sensors 120 during vehicle operation at block 304. In some embodiments, the controller 204 may also receive information from external sources through the communication component 122 and/or the communication unit 220. The sensor data may be stored in the RAM 212 for use by the autonomous vehicle operation application 232. In some embodiments, the sensor data may be recorded in the data storage 228 and/or transmitted to the server 140 via the network 130. The sensor data may alternately either be received by the controller 204 as raw data measurements from one of the sensors 120 and/or may be preprocessed by the sensor 120 prior to being received by the controller 204. For example, a tachometer reading may be received as raw data and/or may be preprocessed to indicate vehicle movement or position. As another example, a sensor 120 comprising a radar and/or LIDAR unit may include a processor to preprocess the measured signals and send data representing detected objects in 3-dimensional space to the controller 204.
[0068] The autonomous vehicle operation application 232, other applications 230, and/or routines 240 may cause the controller 204 to process the received sensor data at block 306 in accordance with the autonomous operation features. The controller 204 may process the sensor data to determine whether an autonomous control action is required and/or to determine adjustments to the controls of the vehicle 108. For example, the controller 204 may receive sensor data indicating a decreasing distance to a nearby object in the vehicle's path and process the received sensor data to determine whether to begin braking (and, if so, how abruptly to slow the vehicle 108). As another example, the controller 204 may process the sensor data to determine whether the vehicle 108 is remaining with its intended path (e.g., within lanes on a roadway). If the vehicle 108 is beginning to drift or slide (e.g., as on ice or water), the controller 204 may determine appropriate adjustments to the controls of the vehicle to maintain the desired bearing. If the vehicle 108 is moving within the desired path, the controller 204 may nonetheless determine whether adjustments are required to continue following the desired route (e.g., following a winding road). Under some conditions, the controller 204 may determine to maintain the controls based upon the sensor data (e.g., when holding a steady speed on a straight road).
[0069] When the controller 204 determines an autonomous control action is required at block 308, the controller 204 may cause the control components of the vehicle 108 to adjust the operating controls of the vehicle to achieve desired operation at block 310. For example, the controller 204 may send a signal to open or close the throttle of the vehicle 108 to achieve a desired speed. Alternatively, the controller 204 may control the steering of the vehicle 108 to adjust the direction of movement. In some embodiments, the vehicle 108 may transmit a message or indication of a change in velocity or position using the communication component 122 and/or the communication unit 220, which signal may be used by other autonomous vehicles to adjust their controls. As discussed further below, the controller 204 may also log or transmit the autonomous control actions to the server 140 via the network 130 for analysis.
[0070] The controller 204 may continue to receive and process sensor data at blocks 304 and 306 until an end signal is received by the controller 204 at block 312. The end signal may be automatically generated by the controller 204 upon the occurrence of certain criteria (e.g., the destination is reached or environmental conditions require manual operation of the vehicle 108 by the vehicle operator). Additionally, or alternatively, the vehicle operator may pause, terminate, and/or disable the autonomous operation feature or features using the user-input device or by manually operating the vehicle's controls, such as by depressing a pedal or turning a steering instrument. When the autonomous operation features are disabled or terminated, the controller 204 may either continue vehicle operation without the autonomous features or may shut off the vehicle 108, depending upon the circumstances.
[0071] Where control of the vehicle 108 must be returned to the vehicle operator, the controller 204 may alert the vehicle operator in advance of returning to manual operation. The alert may include a visual, audio, and/or other indication to obtain the attention of the vehicle operator. In some embodiments, the controller 204 may further determine whether the vehicle operator is capable of resuming manual operation before terminating autonomous operation. If the vehicle operator is determined not be capable of resuming operation, the controller 204 may cause the vehicle to stop and/or take other appropriate action.
Exemplary Monitoring Method During Operation
[0072] FIG. 4 illustrates a flow diagram depicting an exemplary monitoring method 400 during vehicle operation, which may be implemented by the autonomous vehicle insurance system 100. The method 400 may monitor the operation of the vehicle 108 and adjust risk levels and rates based upon vehicle use. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the method 400 may be implemented by the mobile device 110, the on-board computer 114, the server 140, or a combination thereof. Upon receiving an indication of vehicle operation at block 402, the on-board computer 114 may determine the configuration and operating status of the autonomous operation features (including the sensors 120 and the communication component 122) at block 404. The identity of the vehicle operator may be determined and/or verified at block 406, which identity may be used to determine or receive a vehicle operator profile at block 408. The vehicle operator profile may contain information regarding the vehicle operator's ability to manually operate the vehicle and/or past use of autonomous operation features by the vehicle operator. Information from the sensors 120 and/or external data from the communication component 122 may be used at block 410 to determine environmental conditions in which the vehicle 108 is operating. Together, this information determined at blocks 404-410 may be used at block 412 to determine one or more risk levels associated with operation of the vehicle, from which may be determined a costs associated with an insurance policy at block 414. In some embodiments, information regarding the determined cost may be presented to the vehicle operator or other insurance customer associated with the vehicle 108 at block 416. In still further embodiments, the vehicle operator and/or insurance customer may be presented with recommendations or options regarding the cost associated with the insurance policy at block 418. Presentation of options may assist the vehicle operator and/or insurance customer in reducing the cost by allowing the vehicle operator and/or insurance customer to select a lower-cost option (e.g., by adjusting the settings associated with the autonomous operation features). In some embodiments, the vehicle operator and/or insurance customer may be able to select one or more of the options to effect an adjustment in the risk levels and/or insurance cost.
[0073] The method 400 may continue monitoring operation of the vehicle 108 at block 420, and adjustments may be made to the risk levels and insurance costs. If the settings associated with the autonomous operation features are determined to have changed at block 422 (e.g., as a result of the vehicle operator taking manual operation of additional controls), the one or more risk levels may be determined based upon the new settings at block 412, in which case the blocks 414-422 may be repeated. When no changes have been made to the settings, the method 400 may further check for changes to the environmental conditions and/or operating status of the autonomous operation features at block 424. If changes are determined to have occurred at block 424, the one or more risk levels may be determined based upon the new settings at block 412, as at block 422. When no changes have occurred, the method 400 may determine whether vehicle operations are ongoing or whether operation is complete at block 426. When vehicle operation is ongoing, the method 400 may continue to monitor vehicle operation at block 420. When vehicle operation is complete, information regarding operation of the vehicle may be recorded at block 428, at which point the method 400 may terminate.
[0074] At block 402, the on-board computer 114 may receive an indication of vehicle operation. This indication may be received from the vehicle operator (either directly or through the mobile device 110), and/or it may be generated automatically. For example, the on-board computer 114 or the mobile device 110 may automatically generate an indication of vehicle operation when the vehicle starts operation (e.g., upon engine ignition, system power-up, movement of the vehicle 108, etc.). Upon receiving the indication of vehicle operation, the on-board computer 114 may initiate a system check and/or begin recording information regarding operation of the vehicle 108.
[0075] At block 404, the on-board computer 114 may determine the configuration and operating status of one or more autonomous operation features of the vehicle 108. This may include determining the configuration, settings, and/or operating status of one or more hardware or software modules for controlling part or all of the vehicle operation, aftermarket components disposed within the vehicle to provide information regarding vehicle operation, and/or sensors 120 disposed within the vehicle. In some embodiments, a software version, model version, and/or other identification of the feature or sensor may be determined. In further embodiments, the autonomous operation feature may be tested to assess proper functioning, which may be accomplished using a test routine or other means. Additionally, the sensors 120 or the communication component 122 may be assessed to determine their operating status (e.g., quality of communication connections, signal quality, noise, responsiveness, accuracy, etc.). In some embodiments, test signals may be sent to one or more of the sensors 120, responses to which may be received and/or assessed by the on-board computer to determine operating status. In further embodiments, signals received from a plurality of sensors may be compared to determine whether any of the sensors are malfunctioning. Additionally, signals received from the sensors may be used, in some embodiments, to calibrate the sensors.
[0076] At block 406, the on-board computer 114 may determine the identity of the vehicle operator. To determine the identity of the vehicle operator, the on-board computer 114 may receive and process information regarding the vehicle operator. In some embodiments, the received information may include sensor data from one or more sensors 120 configured to monitor the interior of the vehicle. For example, a camera or other photographic sensor may provide photographic information regarding the vehicle operator, which may be processed and compared with other photographic data for a plurality of persons to determine the identity of the vehicle operator. In further embodiments, the on-board computer may receive information from a mobile computing device associated with the vehicle operator, such as a mobile phone or wearable computing device. For example, a mobile phone may connect to the on-board computer 114, which may identify the vehicle operator. Additional steps may be taken to verify the identity of the vehicle operator, such as comparing a weight sensed on a seat or use of voice recognition algorithms.
[0077] At block 408, the on-board computer 114 may determine and/or access a vehicle operator profile based upon the identity of the vehicle operator determined at block 406. The vehicle operator profile may include information regarding the vehicle operator's style of operating the vehicle, including information regarding past operation of one or more vehicles by the vehicle operator. This information may further contain past vehicle operator selections of settings for one or more autonomous operation features. In some embodiments, the on-board computer 114 may request or access the vehicle operator profiled based upon the determined identity. In other embodiments, the on-board computer 114 may generate the vehicle operator profile from information associated with the identified vehicle operator. The vehicle operator profile may include information relating to one or more risks associated with operation of the vehicle by the vehicle operator. For example, the vehicle operator profile for a driver may include information relating to risk levels based upon past driving patters or habits in a variety of relevant environments, which may include risk levels associated with manual operation of the vehicle by the driver. In some embodiments, the vehicle operator profile may include information regarding default settings used by the vehicle operator for the autonomous operation features.
[0078] At block 410, the on-board computer 114 may determine environmental conditions within which the vehicle 108 is or is likely to be operating. Such environmental conditions may include weather, traffic, road conditions, time of day, location of operation, type of road, and/or other information relevant to operation of the vehicle. The environmental conditions may be determined based upon signals received from the sensors 120, from external data received through the communication component 122, and/or from a combination of sources. The environmental conditions may then be used in determining risk levels associated with operation of the vehicle 108.
[0079] At block 412, the on-board computer may determine one or more risk levels associated with operation of the vehicle 108. The risk levels may be determined based upon a combination of risk factors relating to the autonomous operation features and/or risk factors relating to the vehicle operation. Risks associated with the autonomous operation features may be determined based upon the configuration and/or operating status of the autonomous operation features, the settings of the autonomous operation features, and the vehicle environment. Risks associated with the vehicle operation may be determined based upon the autonomous operation features settings (i.e., the extent to which the vehicle operator will be controlling vehicle operations) and/or the vehicle operator profile. The combined risk may account for the likelihood of the autonomous operation features and/or the vehicle operator controlling vehicle operations with respect to relevant functions of the vehicle 108.
[0080] At block 414, the on-board computer 114 may determine a cost associated with an insurance policy based upon the one or more risks. In some embodiments, the server 140 may receive information regarding the vehicle operator and the autonomous operation features and/or may determine the cost associated with the insurance policy based upon the risks. The cost may be based upon risk levels associated with separate autonomous operation features, interaction between autonomous operation features, the design and capabilities of the vehicle 108, the past operating history of the vehicle operator as included in the vehicle operator profile, and/or other information regarding the probability of an accident, collision, and/or other loss event involving the vehicle 108. Each of the separate risks may depend upon the environmental conditions, and the risks may be weighted based upon the likelihood of each situation. In some embodiments, a total risk may be determined relating to operation of the vehicle under foreseeable conditions with specific settings and configurations of autonomous operation features by a specific vehicle operator. The total risk may be used to determine one or more costs associated with the insurance policy, such as a premium and/or discount.
[0081] In some embodiments, information regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at block 416. The information may be presented by a display, such as the display 202 of the on-board computer 114 or the mobile device 110. The information may be presented either for informational purposes or to receive acceptance of the vehicle operator or insurance customer. The insurance cost information may include an indication of one or more of a premium, rate, rating, discount, reward, special offer, points level, program, refund, and/or other costs associated with one or more insurance policies. Additionally, or alternatively, summary information may be presented regarding insurance costs, including a risk level (e.g., high risk, low risk, a risk/cost level on a spectrum, etc.). In some embodiments, presentation of insurance cost information may be suppressed or delayed (e.g., cost information may be presented in summary form on a periodic billing statement).
[0082] In further embodiments, options or recommendations regarding the cost associated with the insurance policy may be presented to the vehicle operator or insurance customer at block 418. The options or recommendations may likewise be presented by a display, such as the display 202 of the on-board computer 114 and/or the mobile device 110. The options or recommendations may include information regarding costs associated with other settings or configurations of the autonomous operation features (e.g., enabling additional features, selecting an operating mode with lower risks under the determined environmental conditions, etc.). In some embodiments, the recommendations or options may be presented for informational purposes only, requiring the vehicle operator or insurance customer to make any adjustments separately (e.g., through a settings module or other means of adjusting settings for the autonomous operation features). In other embodiments, the vehicle operator or insurance customer may select one or more of the options, whereby adjustments to the configuration or settings of the autonomous operation features may be caused to be implemented by the on-board computer 114 or other controlling device. In some embodiments, the options or recommendations may include options or recommendations to update the software version of one or more autonomous operation features, in which case information regarding a cost associated with updating the features (if applicable) may be presented. Once the information and/or options or recommendations regarding insurance costs have been presented at blocks 416-418 (including, in some embodiments, while such presentation is occurring), the on-board computer 114 may monitor operation of the vehicle 108.
[0083] At block 420, the on-board computer 114 may monitor operation of the vehicle 108, including autonomous operation feature control decisions, signals from the sensors 120, external data from the communication component 122, and/or control decisions of the vehicle operator. Monitoring vehicle operation may include monitoring data received directly from the features, sensors, and/or other components, as well as summary information regarding the condition, movement, and/or environment of the vehicle 108. The on-board computer 114 and/or mobile device 110 may cause the operating data to be stored or recorded, either locally in the data storage 228 and/or via server 140 in the program memory 160 and/or the database 146. Monitoring may continue until vehicle operation is complete (e.g., the vehicle has reached its destination and shut down), including during any updates or adjustments.
[0084] At block 422, the on-board computer 114 may determine whether any changes have been made to the settings or configuration of the autonomous operation features. If such changes or adjustments have been made, the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412-414 and/or present the information to the vehicle operator or insurance customer at blocks 416-418, as discussed above. In some embodiments, minor changes below a minimum change threshold may be ignored when determining whether any changes have been made. In further embodiments, the cumulate effect of a plurality of such minor changes below the minimum change threshold may be considered as a change at block 422 when the cumulative effect of the minor changes reaches and/or exceeds the minimum change threshold. When no changes to the settings or configuration of the autonomous operation features are determined to have been made at block 422, the on-board computer 114 may further determine whether any changes in the environmental conditions and/or operating status of the autonomous operation features or sensors have occurred. Although these steps are illustrated separately for clarity, it should be understood that they may be further divided or combined in various embodiments.
[0085] At block 424, the on-board computer 114 may determine whether any changes have occurred to the environmental conditions of the vehicle 108 and/or the operating status of the autonomous operation features, sensors 120, or communication component 122. Such changes may occur when weather or traffic conditions change, when sensors 120 malfunction or become blocked by debris, and/or when the vehicle 108 leaves an area where external data is available via the communication component 122. When such changes occur, the risk levels associated with control of the vehicle 108 by the vehicle operator and the autonomous operation features may likewise change. Therefore, it may be advantageous to adjust the use of the autonomous operation features to account for such changes. Thus, the on-board computer 114 may proceed to determine new risk levels and insurance costs at blocks 412-414 and/or present the information to the vehicle operator or insurance customer at blocks 416-418, as discussed above, when such changes are determined to have occurred at block 424. Similar to the determination at block 422, minor changes below a minimum change threshold may be ignored at block 424, unless the cumulative effect of the changes reaches or exceeds the minimum change threshold. When no changes are determined to have occurred at block 424, the method 400 may continue to monitor the operation of the vehicle 108 until vehicle operation is determined to have ended.
[0086] At block 426, the on-board computer 114 may determine whether vehicle operations are complete. This may include determining whether a command to shut down the vehicle 108 has been received, whether the vehicle 108 has remained idle at a destination for a predetermined period of time, and/or whether the vehicle operator has exited the vehicle 108. Until operation is determined at block 426 to be complete (i.e., when the vehicle trip has concluded), the on-board computer 114 may continue to monitor vehicle operation at block 420, as discussed above. When operation is determined to be complete at block 426, the on-board computer 114 may further cause a record of the operation of the vehicle 108 to be made or stored. Such records may include operating data (in full or summary form) and may be used for assessing risks associated with one or more autonomous operation features or the vehicle operator. As noted above, in some embodiments, records of operating data may be generated and stored continually during operation. In some embodiments, the partial or completed records may be transmitted to the server 140 to be stored in the database 146. After completion and recordation of the vehicle operation, the method 400 may terminate.
Exemplary Methods for Determining Operating Status
[0087] FIG. 5 illustrates a flow diagram depicting an exemplary operating status assessment method 500 that may be used to determine operation status of the autonomous operation features, sensors 120, and/or communication component 122, as indicated in blocks 404 and 424 above. The method 500 may evaluate the autonomous operation features of the vehicle 108 (including sensors 120) and determine whether they are operating correctly, are malfunctioning, and/or are operating with impaired or degraded quality. Such determinations may be particularly important as the vehicle 108 ages or in environments that may block or damage sensors 120. In such cases, the original effectiveness of the autonomous operation features may be reduced as sensors become less accurate or processing of the sensor data is slowed (such as by software version updates that improve accuracy but require greater computational resources). The exemplary method 500 may be implemented regularly to ensure appropriate risk assessment, as well as periodically to certify the operating status level of the vehicle for roadworthiness or insurance rate adjustment. In some embodiments, periodic evaluation may be performed using special purpose computing devices and/or by licensed or authorized third parties. Periodic evaluation may further include more thorough testing and analysis of the vehicle 108, which may include testing at a test environment. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the method 500 may be implemented by the mobile device 110, the on-board computer 114, the server 140, or a combination thereof.
[0088] Upon receiving a request to determine the operating status of the autonomous operation features of the vehicle 108 at block 502, the configuration of the sensors 120 may be determined at block 504. The functioning of autonomous operation feature software routines may further be determined at block 506. A test signal may be transmitted to the sensors 120 at block 508, and/or sensor data may be received at block 510. The sensor data may include a response to the test signal, as well as other signals from the sensors based upon the vehicle environment or operation of the vehicle 108. Based upon the received information, the operating status of the autonomous operation features and components may be determined at block 512. If any impairments are detected at block 514, the method 500 may attempt to remediate the impairments at block 516. If impairments are detected to remain at block 518 after the remediation attempt, an alert may be generated and presented to the vehicle operator or an insurance customer at block 520. When no impairments are detected or after presentation of the alert, a report indicating the operational status of the autonomous operation features may be generated at block 522. In some embodiments, the report may be transmitted to an insurer at block 524, and/or a cost associated with an insurance policy associated with the vehicle 108 may be determined at block 526. The determined cost may be presented with the report at block 528 to the vehicle operator or insurance customer. Once the report has been presented, the exemplary method may end.
[0089] FIG. 6 illustrates a flow diagram of an exemplary operating status monitoring method 600 that may be used to determine operation status of the autonomous operation features, sensors 120, and/or communication component 122, in addition to or alternatively to the exemplary method 500 above. The method 600 may be implemented while the vehicle 108 is in operation to monitor the operating status of the autonomous operation features and components. The method 600 may monitor the vehicle operating data at block 602 to determine operating status of the autonomous operation features and components at block 604. When a change in operating status is detected at block 606, one or more corresponding changes in risk levels may be determined at block 608. If the changes in risk levels are determined to cause the risk levels to exceed an alert threshold but not a critical threshold at blocks 610 and 612, respectively, an alert is generated and presented to the vehicle operator at block 614. If the risk levels are determined to exceed the critical threshold at block 612, the method 600 may determine whether control of the vehicle 108 can be safely transferred to the vehicle operator at block 616. If the vehicle operator is prepared and able to assume control of the vehicle 108, then vehicle operation may be transferred to the vehicle operator at block 620. If control cannot be safely transferred, the vehicle 108 may cease operations and shut down at block 618. Once the vehicle 108 is no longer operating, the method 600 may terminate. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the method 600 may be implemented by the mobile device 110, the on-board computer 114, the server 140, or a combination thereof.
Exemplary Methods for Control Hand-Off
[0090] FIGS. 7A-B illustrate flow diagrams depicting exemplary vehicle operation hand-off methods 700 that may be used to transfer operation of the vehicle 108 from one or more autonomous operation features to the vehicle operator. FIG. 7A illustrates hand-off of control when determined necessary based upon heightened risk levels associated with operation by the one or more autonomous operation features under the environmental conditions. FIG. 7B illustrates hand-off of control when requested by the vehicle operator while one or more autonomous operation features are performing vehicle control tasks. The methods 700 illustrated in FIGS. 7A and 7B may be combined or separately implemented in various embodiments. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the exemplary method 700 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
[0091] Exemplary vehicle operation hand-off method 700 may be implemented at any time when one or more autonomous operation features are controlling part or all of the operation of the vehicle 108. The method 700 may begin by identifying the vehicle operator at block 702 and receiving a vehicle operator profile for the vehicle operator at block 704. At block 706, the operating data (including, in some embodiments, sensor data and external data) may be received and used to monitor operation of the vehicle 108. In some embodiments, a request to disable one or more autonomous operation features may be received from the vehicle operator at block 732. Autonomous risk levels associated with operation of the vehicle 108 by the autonomous operation features and operator risk levels associated with operation of the vehicle 108 by the vehicle operator may be determined at block 708 and 710, respectively. The determined risk levels may be used at block 712 to determine whether to disable one or more autonomous operation features. In some embodiments, the determination of whether to disable one or more autonomous operation features may further be based upon the preparedness level of the vehicle operator determined at block 716.
[0092] When it is determined to disable one or more autonomous operation features at block 714, the method 700 may transfer control to the vehicle operator. In some embodiments, this may include determining whether the vehicle operator is able to safely assume control by determining whether the vehicle operator's preparedness level is above a transfer threshold level at block 718. If so, an alert may be presented to the vehicle operator at block 720 to notify the vehicle operator of the transfer of control from the one or more autonomous operation features before transferring operation at block 722. If the vehicle operator's preparedness level is determined to be below the transfer threshold but above a minimum threshold at block 724, an alert may be presented at block 730 to attempt to prepare the vehicle operator to assume control if the risk levels associated with continued operation by the autonomous operation features do not exceed a critical risk threshold at block 726. Once the alert is presented to the vehicle operator at block 730, the vehicle operator's preparedness level may be determined again at block 716 and evaluated at block 718. If the risk levels exceed the critical threshold at block 726 or the vehicle operator's preparedness level is below the minimum threshold at block 724, the vehicle 108 may discontinue operation at block 728 and the method 700 may end.
[0093] When it is determined not to disable the one or more autonomous operation features at block 714, the method 700 may continue to monitor the operating data at block 706. If the vehicle operator requested that one or more autonomous operation features be disabled, the method 700 may present an alert at block 734 to notify the vehicle operator that disabling the autonomous operation features is not recommended. In some embodiments, options to override the determination not to disable the autonomous operation features may be presented to the vehicle operator at block 736, which the vehicle operator may select at block 738. If the vehicle operator is determined at block 740 to have not selected an option to override the determination, the method 700 may continue to monitor operation data at block 706. If the vehicle operator is determined at block 740 to have selected an option to override the determination, control of operation may be transferred from the one or more autonomous operation features to the vehicle operator. In some embodiments, one or more risk levels associated with disabling the autonomous operation features may be determined at block 742. If the risk levels are determined to be below a critical threshold at block 744, control may be transferred to the vehicle operator. If the risk levels meet or exceed the critical threshold at block 744, the vehicle 108 may instead discontinue operation at block 728 and the method 700 may end.
Exemplary Methods for Vehicle Operator Identification
[0094] FIG. 8 illustrates a flow diagram depicting an exemplary vehicle operator identification method 800 that may be used to adjust an insurance policy associated with the vehicle operator or vehicle 108. The exemplary method 800 may begin with receipt of a request to identify the vehicle operator of the vehicle at block 802. At blocks 804-810, the vehicle operator may be identified by sensor data or received indications of identity, such as from a mobile device 110. Once the identity of the vehicle operator has been determined (or cannot be determined), the method 800 may further determine whether the vehicle operator is authorized to operate the vehicle 108 at block 812. If the vehicle operator is not authorized, an alert may be generated and vehicle operations may be limited at blocks 814-816. If the vehicle operator is authorized, a vehicle operator profile associated with the vehicle operator may be obtained at block 818, and/or an insurance policy associated with the vehicle 108 or the vehicle operator may be identified at block 820. During vehicle operation, operating data of the vehicle 108 may be received and used to adjust the vehicle operator profile and the insurance policy at blocks 822-826. When vehicle operation has been determined to be complete at block 828, the method 800 may terminate. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the method 800 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
Exemplary Methods for Monitoring Use by Vehicle Operators
[0095] FIG. 9 illustrates a flow diagram depicting an exemplary vehicle operator use monitoring and evaluation method 900 that may be used to determine skill or risk levels associated with a vehicle operator or adjust an insurance policy. The exemplary method 900 may begin with determining the identity of the vehicle operator at block 902. If a vehicle operator profile can be found for the vehicle operator at block 904, the vehicle operator profile may be accessed at block 912. If no vehicle operator profile can be found for the vehicle operator at block 904, a vehicle operator profile may be created based upon vehicle operations and stored for future use at blocks 906-910. The newly created vehicle operator profile may be generated at block 908 with vehicle operating data from only a short time period or may include only information regarding configuration and/or settings of the autonomous operation features, in which case operation of the vehicle may continue after the vehicle operator profile is generated. If operation is determined to be ongoing at block 914, vehicle operation may be monitored and the vehicle operator profile may be updated at blocks 916-924. In some embodiments, the vehicle operator may be able to select an option of a mode for vehicle operation. If such a mode selection is detected at block 916, the settings of the autonomous operation features may be adjusted at block 918. Vehicle operation may be monitored at block 920 based upon received operating data, which may be used to determine adjustments to the vehicle operator profile at block 922. The adjustments may then be used to update the vehicle operator profile at block 924. When operation is complete, the method 900 may determine risk or skill levels associated with the vehicle operator at blocks 926-928. These determined levels may be used at blocks 930-934 to generate a report or adjust an insurance policy. Although the exemplary embodiment is described as primarily performed by the on-board computer 114, the method 900 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
[0096] The vehicle operator profile may include information regarding the vehicle operator, including an operating style of the vehicle operation. The operating style may include information regarding frequency with which the vehicle operator operates the vehicle manually, uses one or more autonomous operation features, selects one or more settings for the autonomous operation features, and/or takes control from the autonomous operation features under various conditions. The operating style may further include information regarding observed control decisions made by the vehicle operator, such as rate of acceleration, frequency of lane changes, use of vehicle signaling devices, distances maintained from other vehicles or pedestrians, and/or other aspects of vehicle operation. For example, vehicle operator decisions regarding how long to stop at a stop sign or when to begin accelerating from such a stop in the presence of other vehicles or pedestrians may be included in the operating style. The vehicle operator profile may further include information regarding vehicle operator skill levels, as described below. In some embodiments, the vehicle operator profile may include a risk profile or information regarding one or more risk levels associated with operation of the vehicle by the vehicle operator. Such risk levels may be associated with particular configurations or settings of autonomous operation features and/or particular conditions of the vehicle environment (e.g., time of day, traffic levels, weather, etc.).
[0097] In further embodiments, the vehicle operator profile may include information regarding attentiveness of the vehicle operator while the vehicle is being autonomously operated. For example, some vehicle operators may typically pay attention to road conditions while a vehicle is operating in a fully autonomous mode, while other vehicle operators may typically engage in other activities. In some embodiments, the vehicle operator profile may include information regarding decisions made by the vehicle operator regarding actions that would result in adjustments to costs associated with an insurance policy (e.g., accepting or rejecting recommendations to optimize autonomous operation feature use to lower insurance costs).
[0098] The vehicle operator profile or vehicle operator behavior data may indicate how well the specific vehicle operator drives in rain, snow, sleet, ice, heavy traffic, road construction, stop-and-go traffic, bumper-to-bumper traffic, country or rural traffic, and/or city or downtown street traffic. The current environment (or condition) may include or be rain, ice, snow, fog, heavy traffic, bumper-to-bumper traffic, road construction, city traffic, country or rural traffic, and/or may be associated with a type of road, such as a two-lane or four-lane highway, and/or downtown city street or other street having several traffic lights.
[0099] The operating mode may include one or more settings or configurations of autonomous operation features. For example, operating modes may include adjustments to settings that cause the autonomous operation features to control the vehicle 108 in a more or less aggressive manner with respect to speed, distance from other vehicles, distance from pedestrians, etc. As an example, the settings may cause the vehicle 108 to remain at least a minimum distance from other vehicles (which may depend upon vehicle speed or road conditions), and/or modes may set different minimum distances. Examples of modes may include a city driving mode, a highway driving mode, a rush operation mode, a smooth operation mode, a cautious mode, and/or a user-defined mode.
[0100] In some embodiments, an operating mode may be based upon the vehicle operator profile. For example, the vehicle profile may include information indicating an operating style of the vehicle operator based upon observations of control commands by the vehicle operator, which profile information may be used to generate an operation mode that mimics the style of the vehicle operator. Thus, if the vehicle operator typically stops at stop signs for a particular length of time, the operating style may mimic this length of time to provide an experience that seems normal or customary to the vehicle operator.
Exemplary Methods for Comparing Costs
[0101] FIG. 10 illustrates a flow diagram depicting an exemplary cost comparison method 1000 that may be used to compare costs associated with vehicles, some of which may include autonomous operation features. The exemplary method 1000 may begin by receiving a command to generate a comparison report between two or more alternative transportation options for an insurance customer or other user. The method 1000 may further receive information regarding one or more vehicle operators may be received at block 1004 and/or information regarding a first vehicle and a second vehicle at block 1006. The first and second vehicles may differ in autonomous operation features or other characteristics. Cost levels associated with obtaining, operating, and insuring the first vehicle and the second vehicle may be determined at block 1008, and/or a recommendation based upon the costs may be determined at block 1010. A report including the costs levels, recommendation, and/or related information may be generated at block 1012 and presented to the insurance customer or other user at block 1014. Additionally, one or more options may be presented along with the report at block 1016, such as options to perform another comparison or present additional information. If an option is selected at block 1018, the corresponding action may be performed at block 1020. Although the exemplary embodiment is described as primarily performed by the server 140, the method 1000 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
Exemplary Methods for Updating Autonomous Operation Features
[0102] FIG. 11 illustrates a flow diagram depicting an exemplary autonomous operation feature update method 1100 that may be used to identify, recommend, and/or install updates to autonomous operation features in appropriate autonomous or semi-autonomous vehicles. In some embodiments, the updates may include software version updates. The exemplary method 1100 may begin with the receipt of an indication of an available update to an autonomous operation feature at block 1102, which may include an update to a version of autonomous operation feature software. A plurality of vehicles having the autonomous operation feature may be identified at block 1104 based upon recorded features or communication with the plurality of vehicles. A change in one or more risk levels associated with the update may be determined for some or all of the identified vehicles at block 1106, and/or a change in a cost associated with one or more of the plurality of vehicles may be determined at block 1108. If the determined changes in risk levels or insurance costs meet certain criteria for installing the update at block 1110, a notification regarding the update may be presented to an insurance customer at block 1112. The notification may further include information regarding costs associated with the update. If an indication of acceptance of the update is received at block 1114, the update may be installed at block 1116. Although the exemplary embodiment is described as primarily performed by the server 140, the method 1100 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
Exemplary Methods for Repair of an Autonomous Vehicle
[0103] FIG. 12 illustrates a flow diagram depicting an exemplary autonomous vehicle repair method 1200 that may be used to determine repairs needed as a result of damage to an autonomous or semi-autonomous vehicle. The exemplary method 1200 may begin by receiving an indication of damage to the vehicle 108 at block 1202 and/or receiving operating data associated with the vehicle 108 at block 1204. Based upon the operating data, the type and extent of damage to the vehicle 108 may be determined at block 1206, and/or repairs needed to fix the damage may be determined at block 1208. Additionally, one or more expected costs (or ranges of costs) for the repairs may be estimated at block 1210. An insurance policy associated with the vehicle 108 may be identified, and/or a maximum payment for the repairs may be determined at block 1212 based upon the estimated costs and the insurance policy. Information regarding the estimated cost or costs and the maximum payment under the insurance policy may be presented to an insurance customer at block 1214. Additionally, options associated with the repairs may be presented to the insurance customer at block 1216, and/or a selection of one or more options may be received at block 1218. An insurer or other party may cause a payment to be made at block 1220 to the insurance customer, beneficiary, or other relevant party based upon the estimated costs of repairing the damage and the selected option. Although the exemplary embodiment is described as primarily performed by the server 140, the method 1200 may be implemented by the mobile device 110, the on-board computer 114, the server 140, and/or a combination thereof.
[0104] At block 1202, the on-board computer 114 or server 140 may receive an indication of damage to the vehicle 108. The indication may be received from a vehicle operator and/or insurance customer, and/or the indication may be automatically generated upon a determination of damage. For example, the sensors 120 may provide sensor data to the on-board computer 114 that indicates a collision with another vehicle or other object. Alternatively, the substantially simultaneous disconnection and/or malfunction of a plurality of sensors 120 located in close proximity within the vehicle 108 may cause the on-board computer 114 to generate an indication of damage to the vehicle 108.
[0105] At block 1204, the on-board computer 114 and/or server 140 may receive operating data regarding operation of the vehicle. The operating data may cover operation of the vehicle both before and after the damage occurred, covering a period of time without the damage and a period of time with the damage. The operating data may include information received from the sensors 120 and/or the communication component 122. The operating data may further include information regarding autonomous operation features, such as configurations or settings, and/or information regarding command controls issued by the autonomous operation features and/or vehicle operator. The operating data may further include information derived or determined from the sensor or other data, such as vehicle speed and/or direction. Where the vehicle is inoperable following the damage, the operating data for the time period with damage may include sensor data and/or other data regarding the vehicle and/or the vehicle environment. Such data may be useful in determining the likely extent of the damage by determining damaged areas and/or systems of the vehicle 108.
[0106] At block 1206, the server 140 may determine damage to the vehicle 108 based upon the received operating data. In some embodiments, the operating data may be compared against operating data for a plurality of previous instances of known vehicle damage stored within the database 146 to determine likely damage. Such assessment may be based information from similar vehicles (e.g., vehicles of the same make and model, body type, size, or production year). In some embodiments, the operating data may be processed to generate a model of the vehicle in its environment at the time of the damage. For example, the operating data may indicate relative speeds and/or trajectories of vehicles involved in a collision with the vehicle 108. This model may then be further used to determine likely damage based upon information regarding the vehicle 108 and/or previous loss reports for other vehicles. In some embodiments, the determined damage may be reviewed by a verification routine of the server 140 and/or by a reviewer to verify that the determined level of damage appears to match the actual level of damage. Verification may include assessing the operating status of the sensors 120 and/or communication component 122. In some embodiments, the damage may be determined based upon input from a special-purpose computing device or a human assessor.
[0107] At block 1208, the server 140 may determine one or more repairs associated with the determined damage to the vehicle 108. In some embodiments, the repairs may be determined based upon comparisons of information regarding previously repaired vehicles' damage and repairs. In further embodiments, the repairs may be determined based upon models and/or relationships between types of damage and types of repairs. The repairs may include replacing and/or fixing damage to one or more vehicle components, including the vehicle frame and body. In some embodiments, the repairs may include alternative likely repairs, such that performance of one repair may foreclose the necessity of another repair. For example, the operating data may indicate two or more probably types of damage, but only one type of damage may be present. Thus, repair of one type of likely damage would obviate the need to repair the other types of likely damage. In some embodiments, the repairs may include one or more general repair services and/or one or more specialty repair services. General repair services may be performed by most vehicle repair facilities, whereas specialty repair services may require specialized equipment, materials, and/or expertise to perform the repairs.
[0108] At block 1210, the server 140 may determine expected costs associated with the one or more repairs determined at block 1208. The costs may include both direct costs of repair, as well as indirect costs, such as vehicle rental while the vehicle 108 is being repaired. The costs may be determined based upon information regarding actual costs of repairs performed on a plurality of other vehicles. In some embodiments, the repair costs for other vehicles may be used to determine a range of expected costs and/or an average cost for each repair. The range of expected costs may further be used to determine one or more expected cost levels associated with the repairs, such as a median cost, a mean cost, a high cost or low cost (e.g., levels based upon percentages such as the 80th percentile or the 20th percentile of costs), costs associated with different likely damage levels, and/or indirect costs based upon the extent of the repairs. The costs may also be based upon comparisons of costs in one or more relevant geographic areas. For example, minor damage occurring during a long-distance trip may not preclude operation of the vehicle 108 through the remainder of the trip, in which case costs associated with repair in multiple geographic areas may be determined (e.g., an area where the damage occurred, an area corresponding to a destination of the trip, or an area corresponding to the home location of the vehicle operator or insurance customer). In some embodiments, the costs may be determined based upon quotes received from one or more repair facilities based upon the determined repairs and/or operating data.
[0109] At block 1212, the server 140 may determine one or more maximum payments for the repairs to the vehicle 108. The maximum payments may be based upon the determined costs of the repairs. In some embodiments, the maximum payment may be based upon the range of repair costs. For example, the maximum payment may be set to a level based upon the distribution of repair costs within the range, such that the maximum payment is equal to an actual cost of repairs for a vehicle at a certain percentile of vehicles within the actual repair cost range (e.g., 70th percentile). In further embodiments, the maximum payment may be based in whole or part upon the insurance policy under which payment may be made. For example, a maximum payment amount may be set by the insurance policy, which may, in some embodiments, be further limited based upon the expected costs and/or range of expected costs determined at block 1210.
[0110] At block 1214, the server 140 may cause the one or more expected costs to be presented to the insurance customer, using the display 202 and/or other means. In some embodiments, the maximum payment may be presented to the insurance customer together with the expected costs. For example, where a plurality of alternatives are presented regarding the repairs, each expected cost may include an indication of whether it is below the maximum payment.
[0111] At block 1216, the server 140 may cause one or more options regarding the repairs to be presented to the insurance customer. The options may indicate timing, extent, and/or location of the repairs and may be associated with different costs for the repairs. In some embodiments, the options may include options of one or more repair facilities at which the vehicle 108 may be repaired. Each facility may further be associated with a cost estimate and/or an estimate of a length of time required to complete the repairs. In some embodiments, the estimates of costs and/or time for each facility may be based upon the operating data and/or determined damage. In further embodiments, the estimates of costs and/or time for one or more of the repair facilities may be based upon quoted estimates solicited from the repair facilities received by the server 140. The options may be presented together with an indication of whether each exceeds the maximum payment, such as by a warning presented in connection with any options that exceed the maximum payment.
[0112] At block 1218, the server 140 may receive a selection of one or more of the options from the insurance customer or other authorized user. Upon receiving the selection, the server 140 may cause a payment to be made at block 1220 based upon the one or more selections. The payment may be made to the insurance customer and/or beneficiary of the insurance policy, or the payment may be made to a repair facility and/or other party associated with the repairs. In some embodiments, the server 140 may further facility the repairs by scheduling the repairs at a repair facility, arranging towing of the vehicle to the repair facility, and/or arranging a temporary replacement vehicle for the vehicle operator and/or insurance customer. Once all actions relating to the repair and/or payment have been implemented, the method 1200 may terminate.
Exemplary Methods for Infrastructure Communications
[0113] FIG. 13 illustrates a flow diagram depicting an exemplary infrastructure communication method 1300 that may be used to detect and communicate information regarding infrastructure components to vehicles. The exemplary method 1300 may begin with the infrastructure communication device 124 receiving information regarding the infrastructure component 126 from one or more sensors at block 1302. The information may be used at block 1304 to determine a message regarding the infrastructure component 126. In some embodiments, the message may be augmented at block 1306 by information associated with a sponsor or other party affiliated with the infrastructure communication device 124. The message may then be encoded at block 1308 and transmitted at block 1310, which may cause the message to be presented to the vehicle operator of the vehicle 108 at block 1312. Although the exemplary embodiment describes one infrastructure communication device 124 communicating with one vehicle 108, it should be understood than any number of infrastructure communication devices 124 may communicate with any number of vehicles 108.
Accident Reconstruction
[0114] In one aspect, a computer-implemented method of accident reconstruction or fault determination may be provided. The method may include (1) gathering or collecting data from one or more vehicle-mounted sensors and/or one or more autonomous or semi-autonomous functionality or technology systems of a vehicle, via one or more processors (such as a smart vehicle controller and/or insurance provider remote processor or server) in wired or wireless communication with the one or more vehicle-mounted sensors and/or the one or more autonomous or semi-autonomous functionality or technology systems, the data showing operation of the vehicle and/or how the one or more autonomous or semi-autonomous functionality or technology systems performed before, during, and/or after a vehicle accident involving the vehicle, the vehicle being insured by an insurance provider; (2) reconstructing the scene of the vehicle accident and/or a series of events leading up to the vehicle accident, via the one or more processors; (3) determining, via the one or more processors, one or more causes of the vehicle accident (whether human driver error or faulty autonomous or semi-autonomous functionality or technology) based upon the reconstruction of the vehicle accident; (4) generating, updating, or adjusting, via the one or more processors, (i) an insurance claim associated with the vehicle accident, and/or (ii) an insurance policy, premium, rate, discount, or reward based upon the one or more causes of the vehicle accident determined from the reconstruction of the vehicle accident; and/or (5) communicating or transmitting, from the one or more processors, the insurance claim or insurance policy generated, updated, or adjusted to a mobile device of an insured or owner of the vehicle insured by the insurance provider. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Emergency Services
[0115] In one aspect, a computer-implemented method of directing a route of an autonomous or semi-autonomous vehicle may be provided. The method may include (1) detecting, via a biometric device, that a driver or passenger of an autonomous or semi-autonomous vehicle is having a medical emergency, the autonomous or semi-autonomous vehicle being equipped with an autonomous or semi-autonomous vehicle functionality or technology; (2) sending or transmitting, from the biometric device, to one or more processors (such as vehicle-mounted processors, a smart vehicle controller, and/or an insurance provider remote processor or server), an indication that the driver or passenger is having the medical emergency; (3) in response to receiving the indication that the driver or passenger is having the medical emergency, (a) retrieving or receiving a GPS (Global Positioning System) position, at the one or more processors, from a vehicle-mounted GPS unit or a mobile device GPS unit, and/or (b) determining, via the one or more processors, a route from a current location of the autonomous or semi-autonomous vehicle to a hospital (or emergency room or other medical facility); (4) directing, via the one or more processors, one or more autonomous or semi-autonomous vehicle functionalities or technologies to drive the autonomous or semi-autonomous vehicle from the current location to the hospital; and/or (5) directing or controlling, via the one or more processors, a transmission or communication to the hospital, such as via wireless communication from a remote transmitter associated with an insurance provider and/or a vehicle-mounted transmitter, to indicate the current location of the autonomous or semi-autonomous vehicle, the medical emergency of the driver or passenger, and/or the estimated arrival time of the autonomous or semi-autonomous vehicle at the hospital to facilitate medical response to the medical emergency. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0116] The medical emergency detected by the biometric device may be a heart attack, stroke, and/or seizure. The method may further include directing or controlling, via the one or more processors, a transmission from the autonomous or semi-autonomous vehicle to a police department and/or fire department indicating the medical emergency and/or requesting assistance to the current, an approximate, and/or expected (based upon current route) location of the autonomous or semi-autonomous vehicle.
[0117] The method may further include directing or controlling, via the one or more processors, a transmission from the autonomous or semi-autonomous vehicle to a mobile device of a family member of the driver or passenger indicating the medical emergency, current location, current route, and/or current destination of the autonomous or semi-autonomous vehicle.
Directing an Emergency Route
[0118] In one aspect, a computer-implemented method of directing an emergency route of an autonomous or semi-autonomous vehicle may be provided. The method may include (a) detecting, via a biometric device, that a driver or passenger of an autonomous or semi-autonomous vehicle is having a medical emergency, the autonomous or semi-autonomous vehicle being equipped with an autonomous or semi-autonomous vehicle functionality or technology; (b) sending or transmitting, from the biometric device, to one or more processors (such as vehicle-mounted processors, a smart vehicle controller, and/or an insurance provider remote processor or server), an indication that the driver or passenger is having the medical emergency; (c) in response to receiving the indication that the driver or passenger is having the medical emergency, via the one or more processors: (1) directing one or more autonomous or semi-autonomous vehicle functionalities or technologies to automatically engage (such that the autonomous or semi-autonomous vehicle is self-driving without human interaction); (2) retrieving or receiving a current GPS (Global Position System) position of the autonomous or semi-autonomous vehicle (such as from a vehicle-mounted GPS unit or a GPS unit of a mobile device or wearable device associated with the driver or passenger); (3) determining a route from a current GPS location of the autonomous or semi-autonomous vehicle to a hospital (or emergency room or other medical facility); and/or (4) directing one or more autonomous or semi-autonomous vehicle functionalities or technologies to drive the autonomous or semi-autonomous vehicle from the current GPS location to the hospital to facilitate the driver or passenger receiving medical assistance in a prompt and safe manner. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0119] For instance, the method may include directing or controlling, via the one or more processors, a transmission (such from a remote transmitter and/or from the autonomous or semi-autonomous vehicle itself) to the hospital, such as via wireless communication from a remote transmitter and/or a vehicle-mounted transmitter, to indicate the current location of the autonomous or semi-autonomous vehicle, the medical emergency of the driver or passenger, and/or the estimated arrival time of the autonomous or semi-autonomous vehicle at the hospital to facilitate medical response to the medical emergency. The medical emergency detected by the biometric device may be a heart attack, stroke, and/or seizure.
[0120] The method may include directing or controlling, via the one or more processors, a transmission from the autonomous or semi-autonomous vehicle to a police department and/or fire department indicating the medical emergency and/or requesting assistance to the current, an approximate, and/or expected (based upon current route) location of the autonomous or semi-autonomous vehicle. The method may include directing or controlling, via the one or more processors, a transmission from the autonomous or semi-autonomous vehicle to a mobile device of a family member of the driver or passenger indicating the medical emergency, current location, current route, and/or current destination of the autonomous or semi-autonomous vehicle.
[0121] According to certain aspects, with the customer's permission, it may be detected by sensors (such as vehicle-mounted sensors or mobile device sensors) that an occupant of the autonomous or semi-autonomous vehicle is experiencing a medical emergency. A nearby medical facility may be determined based upon the vehicle location and the detected medical emergency, such as via navigation unit or application running on the vehicle controller or mobile device. A route from the current vehicle location to the medical facility may be determined (such as by the vehicle controller or mobile device), and the autonomous or semi-autonomous vehicle may be automatically directed or routed to the medical facility. A message may also be generated by the vehicle controller or mobile device, and transmitted to the medical facility to alert them that a person in need of timely medical assistance is on the way and/or their current location. Life and auto insurance discounts may be generated for risk averse customers based upon their vehicles having the emergency response functionality.
[0122] Also with the foregoing, a customer may opt into a rewards or other type of program, and willingly share their vehicle data with an insurance provider. In return, risk averse drivers and vehicle owners may receive discounts or insurance cost savings related to auto, life, and other types of insurance from the insurance provider.
Updating Insurance Policies
[0123] In one aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of (1) vehicle usage, and/or (2) vehicle drivers for an insured vehicle; (b) analyzing the data, via the one or more processors, to determine (i) an amount and/or (ii) type of vehicle usage for each vehicle driver; (c) based upon the amount of vehicle usage for each vehicle driver and/or the type of vehicle usage for each vehicle driver, via the one or more processors, updating or adjusting an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle; (d) transmitting, under the direction or control of the one or more processors, the updated or adjusted insurance policy (or otherwise causing the updated or adjusted insurance policy to be presented or displayed to the insured) to a mobile device of the insured for their review, modification, and/or approval; and/or (e) receiving, at or via the one or more processors, from the mobile device of the insured (such as via wireless communication) an approval of the updated or adjusted insurance policy of the insured to facilitate more accurate insurance pricing and/or insurance cost savings. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0124] For instance, the amount of vehicle usage may include an amount of time and/or miles that each individual vehicle driver drives the vehicle. The type of vehicle usage may include characterizing various periods of driving and/or trips as city driving; country driving; freeway or highway driving city street driving; heavy traffic or congested traffic driving; driving in good weather; driving in hazardous weather; rush hour driving; and/or time-of-day driving.
[0125] The vehicle drivers may be identified from mobile device signature; seat pressure sensors and weight; image recognition techniques performed upon images of the driver; and/or biometric devices (such as heart beat or rate characteristics; voice print; and/or thumb or finger prints).
Biometric Device Data
[0126] In one aspect, a computer-implemented method of updating an insurance policy using biometric device data may be provided. The method may include (a) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device indicative of whom is driving an insured vehicle; (b) gathering or receiving, at or via the one or more processors, data indicative of vehicle usage for a single trip and/or driving or driver behavior during the single trip; (c) updating or adjusting, at or via the one or more processors, an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle based upon (1) whom is driving the insured vehicle (and/or his or her driving profile or score), and/or (2) the data indicative of vehicle usage for the single trip and/or the driving or driver behavior exhibited during the single trip to facilitate more accurate risk assessment and/or cost savings to the insured. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein. For instance, the biometric device may verify an identity of the driver based upon heartbeat, facial recognition techniques, and/or mood.
[0127] In another aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data from a biometric device identifying a driver of an insured vehicle; (2) gathering or receiving, at or via the one or more processors, data indicative of driving or driver behavior for the driver identified from the biometric device data; (3) generating, at or via the one or more processors, a usage-based insurance policy for the insured vehicle based upon (i) the identity of the driver determined from the biometric device data, and/or (ii) the data indicative of driving or driver behavior exhibited by the driver to facilitate more accurate risk assessment and/or provide cost savings to the insured. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Usage-Based Insurance for Multiple Drivers
[0128] In one aspect, a computer-implemented method of generating or updating an usage-based insurance policy for an autonomous or semi-autonomous vehicle having multiple drivers may be provided. The method may include (1) identifying, via one or more processors (such as a vehicle-mounted local processor or remote insurance provider processor or server), multiple drivers that drive a vehicle, the vehicle having one or more autonomous or semi-autonomous technologies or functionalities; (2) determining, via the one or more processors, a driving behavior for each of the multiple drivers; (3) determining, via the one or more processors, (i) an amount that each autonomous or semi-autonomous technology or functionality is used, and/or (ii) a type of autonomous or semi-autonomous technology or functionality that is employed by each of the multiple drivers; (4) generating or updating, via the one or more processors, an insurance policy (such as a premium, rate, discount, rewards or points program, etc.) for the vehicle based upon (a) the driving behavior for each of the multiple drivers determined, (b) the amount that each autonomous or semi-autonomous technology or functionality is used by each of the multiple drivers, and/or (c) the type of autonomous or semi-autonomous technology or functionality that is employed by each of the multiple drivers to facilitate providing insurance-related cost savings to the insured and/or to provide an enticement to an insured family to implement safety enhancing technology or functionality. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Software Versions
[0129] In one aspect, a computer-implemented method of updating an insurance policy may be provided. The method may include (1) gathering or receiving, at or via one or more processors (such as either a local processor associated with a smart vehicle and/or a remote processor or server associated with an insurance provider), data indicative of a software version installed on or in an insured vehicle that is associated with an autonomous or semi-autonomous functionality; (2) determining, at or via the one or more processors, that the software version is out of date or a (safer or less risky) new software version exists and/or is available for download; (3) generating, at or via the one or more processors, a recommendation to an insured to update or upgrade to the new software version, and transmitting that recommendation under the direction or control of the one or more processors to a mobile device or insured vehicle controller (such as via wireless communication or data transmission); (4) determining, at or via the one or more processors, (or receiving an indication) that the insured has updated or upgraded to the new software version associated with the autonomous or semi-autonomous functionality; and/or (5) updating or adjusting, at or via the one or more processors, an insurance policy (such as a premium, rate, rewards or points program, discount, etc.) for the insured vehicle based upon the insured updating or upgrading to the new software version associated with an autonomous or semi-autonomous functionality to facilitate providing cost savings to the insured and/or enticing drivers to update vehicle software to most recent versions and/or versions that perform better. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Personal Insurance Policies
[0130] In one aspect, a computer-implemented method of generating or adjusting a personal insurance policy may be provided. The method may include (1) collecting, gathering, generating, and/or receiving data, via one or more processors (such as a local smart home or smart vehicle controller, and/or a remote insurance provider processor or server), related to home maintenance or upgrades for an insured home of an insured; (2) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to past vehicle maintenance for a vehicle previously or currently owned by the insured; (3) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to driving behavior of the insured; (4) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to autonomous or semi-autonomous vehicle functionality or technology usage by the insured; and/or (5) generating, updating, and/or adjusting, via the one or more processors, an insurance policy (such as a premium, rate, discount, rewards or points program, etc.) based upon (a) the home maintenance or upgrades for the insured home performed by the insured; (b) past vehicle maintenance for the vehicle previously or currently owned by the insured; (c) the driving behavior of the insured; and/or (d) autonomous or semi-autonomous vehicle functionality or technology usage by the insured to facilitate providing insurance-related cost savings to the insured. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0131] In another aspect, a computer-implemented method of generating or adjusting a personal insurance policy may be provided. The method may include (1) collecting, gathering, generating, and/or receiving data, via one or more processors (such as a local smart home or smart vehicle controller, and/or a remote insurance provider processor or server), related to home maintenance or upgrades for an insured home of an insured; (2) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to past vehicle maintenance for one or more vehicles previously or currently owned by the insured; (3) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to driving behavior of the insured; (4) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to autonomous or semi-autonomous vehicle functionality or technology usage by the insured; (5) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to one or more lifestyle characteristics and/or risky, or risk averse adverse, behaviors of the insured; and/or (6) generating, updating, and/or adjusting, via the one or more processors, an insurance policy (such as a premium, rate, discount, rewards or points program, etc.) based upon (a) the home maintenance or upgrades for the insured home performed by the insured; (b) past vehicle maintenance for the vehicle previously or currently owned by the insured; (c) the driving behavior of the insured; (d) autonomous or semi-autonomous vehicle functionality or technology usage by the insured; and/or (e) one or more lifestyle characteristics and/or risky, or risk averse, behaviors of the insured to facilitate providing insurance-related cost savings to the insured and/or to customers that are generally risk averse. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0132] The insurance policy generated, updated or adjusted, via the one or more processors, may be a life, auto, home, renters, health, or other type of insurance policy; a personal or holistic insurance policy; and/or a personal insurance policy.
Life Insurance
[0133] In one aspect, a computer-implemented method of generating or adjusting a life insurance policy may be provided. The method may include (1) collecting, gathering, generating, and/or receiving data, via one or more processors (such as a local smart home or smart vehicle controller, or mobile device, and/or a remote insurance provider processor or server), related to driving behavior of the insured; (2) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to autonomous or semi-autonomous vehicle functionality or technology usage by the insured; (3) collecting, gathering, generating, and/or receiving data, via the one or more processors, related to one or more lifestyle characteristics and/or risky, or risk averse adverse, behaviors of the insured; and/or (4) generating, updating, and/or adjusting, via the one or more processors, a life insurance policy (such as a premium, rate, discount, rewards or points program, etc.) based upon (i) the driving behavior of the insured; (ii) autonomous or semi-autonomous vehicle functionality or technology usage by the insured; and/or (iii) one or more lifestyle characteristics and/or risky, or risk averse, behaviors of the insured to facilitate providing insurance-related cost savings to the insured and/or to customers that are generally risk averse, and/or to reflect longer life expectancy due to driver usage of autonomous or semi-autonomous vehicle functionality or technology proven to impact driver safety. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
Subscription Insurance Plans for Autonomous Vehicles
[0134] In one aspect, a computer-implemented method of providing insurance as a subscription service may be provided. The method may include (1) generating, via one or more processors (such as a local smart home or smart vehicle controller, and/or a remote insurance provider processor or server), one or more insurance subscription plans and/or periodic insurance rates based upon frequency of autonomous vehicle usage and/or frequency of renting autonomous vehicles (such as with persons living in large cities or communities that would rather use an autonomous vehicle taxi service); (2) causing the one or more subscription plans and/or periodic insurance rates, via the one or more processors, to presented on a computing device of an insurance customer or potential customer (and/or otherwise transmitting, such as via wired or wireless communication, the one or more subscription plans and/or periodic insurance rates to the computing device) for review and selection by the insurance customer or potential customer; (3) receiving, via the one or more processors, a selection or approval of a subscription plan and/or periodic insurance rate from the computing device of the insurance customer or potential customer; and/or (4) in response, issuing, via the one or more processors, a subscription insurance plan to the insurance customer or potential customer covering, and/or providing insurance coverage(s) for, the usage and/or rental of the autonomous vehicle(s). For instance, the one or more processors may transmit a copy of the subscription insurance plan to the computing device of the customer for their review and/or records. The method may include additional, fewer, or alternate actions, including those discussed elsewhere herein.
[0135] The subscription insurance plan may include, and/or may have a rate based upon, an amount of autonomous vehicle usage, such as by amount of miles or time (such as by minutes, hours, or days). The subscription insurance plan may provide, include, and/or may be associated with, automatic routing or directions telling or directing the autonomous vehicle to a pickup point and/or a destination for each trip.
[0136] The subscription insurance plan charges may be based upon (i) a route taken or directed by the insured or customer; (ii) a time of day that the autonomous vehicle service is provided (e.g., peak hours versus off-peak hours); (iii) an amount of time that the trip takes; and/or (iv) a mileage that autonomous vehicle drives to complete delivering the insured or customer to the destination.
[0137] The subscription insurance plan charges may be based upon features and/or capabilities of the autonomous rental vehicles, such as insured or customer selected autonomous and/or rental vehicles, and/or the software versions installed in those vehicles. The subscription insurance plan may include, and/or may be associated with, functionality that verifies the identity of the insured as the insured enters the autonomous vehicle and/or at the pick-up point to prevent fraudulent charges (such as via a biometric device, communication with a mobile device of the insured or customer, facial or voice recognition software, etc.).
Exemplary Autonomous Vehicle Insurance Risk and Price Determination Methods
[0138] Risk profiles or risk levels associated with one or more autonomous operation features determined above may be further used to determine risk categories or premiums for vehicle insurance policies covering autonomous vehicles. In some embodiments or under some conditions, the vehicle 108 may be a fully autonomous vehicle operating without a vehicle operator's input or presence. In other embodiments or under other conditions, the vehicle operator may control the vehicle 108 with or without the assistance of the vehicle's autonomous operation features. For example, the vehicle may be fully autonomous only above a minimum speed threshold or may require the vehicle operator to control the vehicle during periods of heavy precipitation. Alternatively, the autonomous vehicle may perform all relevant control functions using the autonomous operation features under all ordinary operating conditions. In still further embodiments, the vehicle 108 may operate in either a fully or a partially autonomous state, while receiving or transmitting autonomous communications.
[0139] Where the vehicle 108 operates only under fully autonomous control by the autonomous operation features under ordinary operating conditions or where control by a vehicle operator may be disregarded for insurance risk and price determination, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based upon the risks associated with the autonomous operation features, without reference to risks associated with the vehicle operator. Where the vehicle 108 may be operated manually under some conditions, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be based upon risks associated with both the autonomous operation features and the vehicle operator performing manual vehicle operation. Where the vehicle 108 may be operated with the assistance of autonomous communications features, the risk level or premium associated with an insurance policy covering the autonomous vehicle may be determined based in part upon a determination of the expected use of autonomous communication features by external sources in the relevant environment of the vehicle 108 during operation of the vehicle 108.
Data Acquisition
[0140] In one aspect, the present embodiments may relate to data acquisition. Data may be gathered via devices employing wireless communication technology, such as Bluetooth or other IEEE communication standards. In one embodiment, a Bluetooth enabled smartphone or mobile device, and/or an in-dash smart and/or communications device may collect data. The data associated with the vehicle, and/or vehicle or driver performance, that is gathered or collected at, or on, the vehicle may be wirelessly transmitted to a remote processor or server, such as a remote processor or server associated with an insurance provider. The mobile device 110 may receive the data from the on-board computer 114 or the sensors 120, and may transmit the received data to the server 140 via the network 130, and the data may be stored in the database 146. In some embodiments, the transmitted data may include real-time sensor data, a summary of the sensor data, processed sensor data, operating data, environmental data, communication data, or a log such data.
[0141] Data may be generated by autonomous or semi-autonomous vehicles and/or vehicle mounted sensors (or smart sensors), and then collected by vehicle mounted equipment or processors, including Bluetooth devices, and/or an insurance provider remote processor or server. The data gathered may be used to analyze vehicle decision making. A processor may be configured to generate data on what an autonomous or semi-autonomous vehicle would have done in a given situation had the driver not taken over manual control/driving of the vehicle or alternative control actions not taken by the autonomous or semi-autonomous operation features. This type of control decision data (related to vehicle decision making) may be useful with respect to analyzing hypothetical situations.
[0142] In one embodiment, an application, or other computer or processor instructions, may interact with a vehicle to receive and/or retrieve data from autonomous or semi-autonomous processors and sensors. The data retrieved may be related to radar, cameras, sensor output, computer instructions or application output. Other data related to a smart vehicle controller, car navigation unit information (including route history information and typical routes taken), GPS unit information, odometer and/or speedometer information, and smart equipment data may also be gathered or collected. The application and/or other computer instructions may be associated with an insurance provider remote processor or server.
[0143] The control decision data may further include information regarding control decisions generated by one or more autonomous operation features within the vehicle. The operating data and control decision data gathered, collected, and/or acquired may facilitate remote evaluation and/or analysis of what the autonomous or semi-autonomous vehicle was “trying to do” (brake, slow, turn, accelerate, etc.) during operation, as well as what the vehicle actually did do. The data may reveal decisions, and the appropriateness thereof, made by the artificial intelligence or computer instructions associated with one or more autonomous or semi-autonomous vehicle technologies, functionalities, systems, and/or pieces of equipment. The data may include information related to what the vehicle would have done in a situation if the driver had not taken over (beginning manual vehicle control). Such data may include both the control actions taken by the vehicle and control actions the autonomous or semi-autonomous operation features would have caused the vehicle to take. Thus, in some embodiments, the control decisions data may include information regarding control decisions not implemented by the autonomous operation features to control the vehicle. This may occur when an autonomous operation feature generates a control decision or associated control signal, but the control decision or signal is prevented from controlling the vehicle because the autonomous feature or function is disabled, the control decision is overridden by the vehicle operator, the control signal would conflict with another control signal generated by another autonomous operation feature, a more preferred control decision is generated, and/or an error occurs in the on-board computer 114 or the control system of the vehicle.
[0144] For example, a vehicle operator may disable or constrain the operation of some or all autonomous operation features, such as where the vehicle is operated manually or semi-autonomously. The disabled or constrained autonomous operation features may, however, continue to receive sensor data and generate control decision data that is not implemented. Similarly, one or more autonomous operation features may generate more than one control decision in a relevant period of time as alternative control decisions. Some of these alternative control decisions may not be selected by the autonomous operation feature or an autonomous operation control system to control the vehicle. For example, such alternative control decisions may be generated based upon different sets of sensor or communication data from different sensors 120 or include or excluding autonomous communication data. As another example, the alternative control decisions may be generated faster than they can be implemented by the control system of the vehicle, thus preventing all control decisions from being implemented.
[0145] In addition to control decision data, other information regarding the vehicle, the vehicle environment, or vehicle operation may be collected, generated, transmitted, received, requested, stored, and/or recorded in connection with the control decision data. Additional operating data including sensor data from the sensors 120, autonomous communication data from the communication component 122 or the communication unit 220, location data, environmental data, time data, settings data, configuration data, and/or other relevant data may be associated with the control decision data. In some embodiments, a database or log may store the control decision data and associated information. In further embodiments, the entries in such log or database may include a timestamp indicating the date, time, location, vehicle environment, vehicle condition, autonomous operation feature settings, and/or autonomous operation feature configuration information associated with each entry. Such data may facilitate evaluating the autonomous or semi-autonomous technology, functionality, system, and/or equipment in hypothetical situations and/or may be used to calculate risk, and in turn adjust insurance policies, premiums, discounts, etc.
Autonomous Vehicle Insurance Policies
[0146] The disclosure herein relates to insurance policies for vehicles with autonomous operation features. Accordingly, as used herein, the term “vehicle” may refer to any of a number of motorized transportation devices. A vehicle may be a car, truck, bus, train, boat, plane, motorcycle, snowmobile, other personal transport devices, etc. Also as used herein, an “autonomous operation feature” of a vehicle means a hardware or software component or system operating within the vehicle to control an aspect of vehicle operation without direct input from a vehicle operator once the autonomous operation feature is enabled or engaged. The term “autonomous vehicle” means a vehicle including at least one autonomous operation feature. A “fully autonomous vehicle” means a vehicle with one or more autonomous operation features capable of operating the vehicle in the absence of or without operating input from a vehicle operator.
[0147] Additionally, the term “insurance policy” or “vehicle insurance policy,” as used herein, generally refers to a contract between an insurer and an insured. In exchange for payments from the insured, the insurer pays for damages to the insured which are caused by covered perils, acts, or events as specified by the language of the insurance policy. The payments from the insured are generally referred to as “premiums,” and typically are paid by or on behalf of the insured upon purchase of the insurance policy or over time at periodic intervals. Although insurance policy premiums are typically associated with an insurance policy covering a specified period of time, they may likewise be associated with other measures of a duration of an insurance policy, such as a specified distance traveled or a specified number of trips. The amount of the damages payment is generally referred to as a “coverage amount” or a “face amount” of the insurance policy. An insurance policy may remain (or have a status or state of) “in-force” while premium payments are made during the term or length of coverage of the policy as indicated in the policy. An insurance policy may “lapse” (or have a status or state of “lapsed”), for example, when the parameters of the insurance policy have expired, when premium payments are not being paid, when a cash value of a policy falls below an amount specified in the policy, or if the insured or the insurer cancels the policy.
[0148] The terms “insurer,” “insuring party,” and “insurance provider” are used interchangeably herein to generally refer to a party or entity (e.g., a business or other organizational entity) that provides insurance products, e.g., by offering and issuing insurance policies. Typically, but not necessarily, an insurance provider may be an insurance company. The terms “insured,” “insured party,” “policyholder,” and “customer” are used interchangeably herein to refer to a person, party, or entity (e.g., a business or other organizational entity) that is covered by the insurance policy, e.g., whose insured article or entity is covered by the policy. Typically, a person or customer (or an agent of the person or customer) of an insurance provider fills out an application for an insurance policy. In some cases, the data for an application may be automatically determined or already associated with a potential customer. The application may undergo underwriting to assess the eligibility of the party and/or desired insured article or entity to be covered by the insurance policy, and, in some cases, to determine any specific terms or conditions that are to be associated with the insurance policy, e.g., amount of the premium, riders or exclusions, waivers, and the like. Upon approval by underwriting, acceptance of the applicant to the terms or conditions, and payment of the initial premium, the insurance policy may be in-force, (i.e., the policyholder is enrolled).
[0149] Although the exemplary embodiments discussed herein relate to automobile insurance policies, it should be appreciated that an insurance provider may offer or provide one or more different types of insurance policies. Other types of insurance policies may include, for example, commercial automobile insurance, inland marine and mobile property insurance, ocean marine insurance, boat insurance, motorcycle insurance, farm vehicle insurance, aircraft or aviation insurance, and other types of insurance products.
Other Matters
[0150] Although the text herein sets forth a detailed description of numerous different embodiments, it should be understood that the legal scope of the invention is defined by the words of the claims set forth at the end of this patent. The detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this patent, which would still fall within the scope of the claims.
[0151] In one aspect, autonomous or semi-autonomous vehicle; telematics; interconnected home; mobile device; and/or other data, including that discussed elsewhere herein, may be collected or received by an insurance provider remote server, such as via direct or indirect wireless communication or data transmission, after a customer affirmatively consents or otherwise opts into an insurance discount, reward, or other program. The insurance provider may then analyze the data received with the customer's permission to provide benefits to the customer. As a result, risk averse customers may receive insurance discounts or other insurance cost savings based upon data that reflects low risk behavior and/or technology that mitigates or prevents risk to (i) insured assets, such as autonomous or semi-autonomous vehicles, and/or (ii) autonomous or semi-autonomous vehicle operators or passengers.
[0152] It should also be understood that, unless a term is expressly defined in this patent using the sentence “As used herein, the term ‘——————’ is hereby defined to mean . . . ” or a similar sentence, there is no intent to limit the meaning of that term, either expressly or by implication, beyond its plain or ordinary meaning, and such term should not be interpreted to be limited in scope based upon any statement made in any section of this patent (other than the language of the claims). To the extent that any term recited in the claims at the end of this disclosure is referred to in this disclosure in a manner consistent with a single meaning, that is done for sake of clarity only so as to not confuse the reader, and it is not intended that such claim term be limited, by implication or otherwise, to that single meaning. Finally, unless a claim element is defined by reciting the word “means” and a function without the recital of any structure, it is not intended that the scope of any claim element be interpreted based upon the application of 35 U.S.C. § 112(f).
[0153] Throughout this specification, plural instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods are illustrated and described as separate operations, one or more of the individual operations may be performed concurrently, and nothing requires that the operations be performed in the order illustrated. Structures and functionality presented as separate components in example configurations may be implemented as a combined structure or component. Similarly, structures and functionality presented as a single component may be implemented as separate components. These and other variations, modifications, additions, and improvements fall within the scope of the subject matter herein.
[0154] Additionally, certain embodiments are described herein as including logic or a number of routines, subroutines, applications, or instructions. These may constitute either software (code embodied on a non-transitory, tangible machine-readable medium) or hardware. In hardware, the routines, etc., are tangible units capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware module that operates to perform certain operations as described herein.
[0155] In various embodiments, a hardware module may be implemented mechanically or electronically. For example, a hardware module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
[0156] Accordingly, the term “hardware” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware is temporarily configured (e.g., programmed), the hardware need not be configured or instantiated at any one instance in time. Software may accordingly configure a processor, for example, to constitute a particular hardware module at one instance of time and to constitute a different hardware module at a different instance of time. Hardware elements can provide information to, and receive information from, other hardware elements. Accordingly, the described hardware may be regarded as being communicatively coupled.
[0157] The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules. Similarly, the methods or routines described herein may be at least partially processor-implemented. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
[0158] Unless specifically stated otherwise, discussions herein using words such as “processing,” “computing,” “calculating,” “determining,” “presenting,” “displaying,” or the like may refer to actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electronic, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information. As used herein any reference to “one embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. Some embodiments may be described using the expression “coupled” and “connected” along with their derivatives. For example, some embodiments may be described using the term “coupled” to indicate that two or more elements are in direct physical or electrical contact. The term “coupled,” however, may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. The embodiments are not limited in this context.
[0159] As used herein, the terms “comprises,” “comprising,” “includes,” “including,” “has,” “having” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, unless expressly stated to the contrary, “or” refers to an inclusive or and not to an exclusive or. In addition, use of the “a” or “an” are employed to describe elements and components of the embodiments herein. This is done merely for convenience and to give a general sense of the description. In this description, and the claims that follow, the singular also includes the plural unless it is obvious that it is meant otherwise. This detailed description is to be construed as exemplary only and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible. One could implement numerous alternate embodiments, using either current technology or technology developed after the filing date of this application.
[0160] Upon reading this disclosure, those of skill in the art will appreciate still additional alternative structural and functional designs for system and a method for assigning mobile device data to a vehicle through the disclosed principles herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those skilled in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.
[0161] The particular features, structures, or characteristics of any specific embodiment may be combined in any suitable manner and in any suitable combination with one or more other embodiments, including the use of selected features without corresponding use of other features. In addition, many modifications may be made to adapt a particular application, situation or material to the essential scope and spirit of the present invention. It is to be understood that other variations and modifications of the embodiments of the present invention described and illustrated herein are possible in light of the teachings herein and are to be considered part of the spirit and scope of the present invention.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
What is claimed is:
1. A computer-implemented method for directing a route of an autonomous or semi-autonomous vehicle during an emergency, the method comprising:
detecting, by one or more sensors disposed within the autonomous or semi-autonomous vehicle, that an occupant of the autonomous or semi-autonomous vehicle is experiencing a medical emergency;
identifying, by the one or more processors, a medical facility based upon a vehicle location of the autonomous or semi-autonomous vehicle;
determining, by the one or more processors, one or more routes from the vehicle location to the medical facility;
causing, by the one or more processors, the autonomous or semi-autonomous vehicle to automatically travel to the medical facility along the determined one or more routes, wherein the autonomous or semi-autonomous vehicle is controlled by one or more autonomous operation features during travel along the route; and
transmitting, by the one or more processors, a message to at least one of the following: the medical facility, a police department, a fire department, or a family member of the occupant, wherein the message indicates the determined one or more routes to the medical facility.
2. The computer-implemented method of claim 1, wherein the medical emergency is detected by a biometric device within the autonomous or semi-autonomous vehicle.
3. The computer-implemented method of claim 1, wherein the vehicle location is determined using a Global Positioning System (GPS) receiver.
4. The computer-implemented method of claim 1, wherein the detected medical emergency includes one or more of the following: a heart attack, a stroke, or a seizure.
5. The computer-implemented method of claim 1, wherein causing the autonomous or semi-autonomous vehicle to automatically travel to a medical facility further comprises:
causing, by the one or more processors, the one or more autonomous operation features to engage;
causing, by the one or more processors, the one or more autonomous operation features to control the operation of the autonomous or semi-autonomous vehicle along the determined one or more routes to the medical facility; and
causing, by the one or more processors, the autonomous or semi-autonomous vehicle to park at an appropriate location upon arrival at the medical facility.
6. The computer-implemented method of claim 1, wherein the one or more autonomous operation features of the autonomous or semi-autonomous vehicle perform at least one of the following functions:
steering;
accelerating;
braking;
parking;
pedestrian detection;
artificial intelligence;
vehicle navigation;
vehicle positioning; or
remote vehicle location determination.
7. A computer system for directing a route of an autonomous or semi-autonomous vehicle during an emergency, comprising:
one or more processors disposed within the autonomous or semi-autonomous vehicle;
one or more sensors disposed within the autonomous or semi-autonomous vehicle and communicatively connected to the one or more processors;
a communication component communicatively coupled to the one or more processors and
a program memory coupled to the one or more processors and storing executable instructions that when executed by the one or more processors cause the computer system to:
detect that an occupant of the autonomous or semi-autonomous vehicle is experiencing a medical emergency based upon data from the one or more sensors;
identify a medical facility based upon a vehicle location of the autonomous or semi-autonomous vehicle;
determine one or more routes from the vehicle location to the medical facility;
cause the autonomous or semi-autonomous vehicle to automatically travel to the medical facility along the determined one or more routes, wherein the autonomous or semi-autonomous vehicle is controlled by one or more autonomous operation features during travel along the determined one or more routes; and
transmit, by the communication component, a message to at least one of the following: the medical facility, a police department, a fire department, or a family member of the occupant, wherein the message indicates the determined one or more routes to the medical facility.
8. The computer system of claim 7, wherein the one or more sensors that detect the medical emergency include a biometric device within the autonomous or semi-autonomous vehicle.
9. The computer system of claim 7, further comprising a Global Positioning System (GPS) receiver communicatively connected to the one or more processors, wherein the wherein the vehicle location is determined using the GPS receiver.
10. The computer system of claim 7, wherein the detected medical emergency includes one or more of the following: a heart attack, a stroke, or a seizure.
11. The computer system of claim 7, wherein the executable instructions that cause the autonomous or semi-autonomous vehicle to automatically travel to a medical facility further comprise executable instructions that cause the computer system to:
cause the one or more autonomous operation features to engage;
cause the one or more autonomous operation features to control the operation of the autonomous or semi-autonomous vehicle along the determined one or more routes to the medical facility; and
cause the autonomous or semi-autonomous vehicle to park at an appropriate location upon arrival at the medical facility.
12. A tangible, non-transitory computer-readable medium storing instructions for directing a route of an autonomous or semi-autonomous vehicle during an emergency that, when executed by at least one processor of a computer system disposed within the autonomous or semi-autonomous vehicle, cause the computer system to:
detect that an occupant of the autonomous or semi-autonomous vehicle is experiencing a medical emergency;
identify a medical facility based upon a vehicle location of the autonomous or semi-autonomous vehicle;
determine one or more routes from the vehicle location to the medical facility;
cause the autonomous or semi-autonomous vehicle to automatically travel to the medical facility along the determined one or more routes, wherein the autonomous or semi-autonomous vehicle is controlled by one or more autonomous operation features during travel along the determined one or more routes; and
transmit a message to at least one of the following: the medical facility, a police department, a fire department, or a family member of the occupant, wherein the message indicates the determined one or more routes to the medical facility.
13. The tangible, non-transitory computer-readable medium of claim 12, wherein the medical emergency is detected using a biometric device within the autonomous or semi-autonomous vehicle.
14. The tangible, non-transitory computer-readable medium of claim 12, wherein the vehicle location is determined using a Global Positioning System (GPS) receiver.
15. The tangible, non-transitory computer-readable medium of claim 12, wherein the detected medical emergency includes one or more of the following: a heart attack, a stroke, or a seizure.
16. The tangible, non-transitory computer-readable medium of claim 12, wherein the executable instructions that cause the autonomous or semi-autonomous vehicle to automatically travel to a medical facility further comprise executable instructions that cause the computer system to:
cause the one or more autonomous operation features to engage;
cause the one or more autonomous operation features to control the operation of the autonomous or semi-autonomous vehicle along the determined one or more routes to the medical facility; and
cause the autonomous or semi-autonomous vehicle to park at an appropriate location upon arrival at the medical facility.
17. The tangible, non-transitory computer-readable medium of claim 12, wherein the one or more autonomous operation features of the autonomous or semi-autonomous vehicle perform at least one of the following functions:
steering;
accelerating;
braking;
parking;
pedestrian detection;
artificial intelligence;
vehicle navigation;
vehicle positioning; or
remote vehicle location determination.
Patent Citations (324)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4218763(A) | 1980-08-01 | Kelley et al. | Applicant |
| US4565997(A) | 1986-01-01 | Seko et al. | Applicant |
| US5367456(A) | 1994-11-01 | Summerville et al. | Applicant |
| US5368484(A) | 1994-11-01 | Copperman et al. | Applicant |
| US5436839(A) | 1995-07-01 | Dausch et al. | Applicant |
| US5499182(A) | 1996-03-01 | Ousborne | Applicant |
| US5515026(A) | 1996-05-01 | Ewert | Applicant |
| US5626362(A) | 1997-05-01 | Mottola | Applicant |
| US5797134(A) | 1998-08-01 | McMillan et al. | Applicant |
| US5835008(A) | 1998-11-01 | Colemere, Jr. | Applicant |
| US5983161(A) | 1999-11-01 | Lemelson et al. | Applicant |
| US6031354(A) | 2000-02-01 | Wiley et al. | Applicant |
| US6064970(A) | 2000-05-01 | McMillan et al. | Applicant |
| US6067488(A) | 2000-05-01 | Tano | Applicant |
| US6141611(A) | 2000-10-01 | MacKey et al. | Applicant |
| US6246933(B1) | 2001-06-01 | Bague | Applicant |
| US6253129(B1) | 2001-06-01 | Jenkins et al. | Applicant |
| US6298290(B1) | 2001-10-01 | Abe et al. | Applicant |
| US6313749(B1) | 2001-11-01 | Horne et al. | Applicant |
| US6473000(B1) | 2002-10-01 | Secreet et al. | Applicant |
| US6477117(B1) | 2002-11-01 | Narayanaswami et al. | Applicant |
| US6556905(B1) | 2003-04-01 | Mittelsteadt et al. | Applicant |
| US6570609(B1) | 2003-05-01 | Heien | Applicant |
| US6661345(B1) | 2003-12-01 | Bevan et al. | Applicant |
| US6704434(B1) | 2004-03-01 | Sakoh et al. | Applicant |
| US6795759(B2) | 2004-09-01 | Doyle | Applicant |
| US6832141(B2) | 2004-12-01 | Skeen et al. | Applicant |
| US6889137(B1) | 2005-05-01 | Rychlak | Examiner |
| US6909947(B2) | 2005-06-01 | Douros et al. | Applicant |
| US6944536(B2) | 2005-09-01 | Singleton | Examiner |
| US7027621(B1) | 2006-04-01 | Prokoski | Applicant |
| US7054723(B2) | 2006-05-01 | Seto et al. | Applicant |
| US7138922(B2) | 2006-11-01 | Strumolo et al. | Applicant |
| US7149533(B2) | 2006-12-01 | Laird et al. | Applicant |
| US7253724(B2) | 2007-08-01 | Prakah-Asante et al. | Applicant |
| US7254482(B2) | 2007-08-01 | Kawasaki et al. | Applicant |
| US7302344(B2) | 2007-11-01 | Olney et al. | Applicant |
| US7356392(B2) | 2008-04-01 | Hubbard et al. | Applicant |
| US7386376(B2) | 2008-06-01 | Basir et al. | Applicant |
| US7424414(B2) | 2008-09-01 | Craft | Applicant |
| US7565230(B2) | 2009-07-01 | Gardner et al. | Applicant |
| US7609150(B2) | 2009-10-01 | Wheatley et al. | Applicant |
| US7639148(B2) | 2009-12-01 | Victor | Applicant |
| US7692552(B2) | 2010-04-01 | Harrington et al. | Applicant |
| US7719431(B2) | 2010-05-01 | Bolourchi | Applicant |
| US7783505(B2) | 2010-08-01 | Roschelle et al. | Applicant |
| US7792328(B2) | 2010-09-01 | Albertson et al. | Applicant |
| US7812712(B2) | 2010-10-01 | White et al. | Applicant |
| US7835834(B2) | 2010-11-01 | Smith et al. | Applicant |
| US7865378(B2) | 2011-01-01 | Gay | Applicant |
| US7870010(B2) | 2011-01-01 | Joao | Applicant |
| US7877275(B2) | 2011-01-01 | Ball | Examiner |
| US7881951(B2) | 2011-02-01 | Roschelle et al. | Applicant |
| US7890355(B2) | 2011-02-01 | Gay et al. | Applicant |
| US7987103(B2) | 2011-07-01 | Gay et al. | Applicant |
| US7991629(B2) | 2011-08-01 | Gay et al. | Applicant |
| US8009051(B2) | 2011-08-01 | Omi | Applicant |
| US8010283(B2) | 2011-08-01 | Yoshida et al. | Applicant |
| US8016595(B2) | 2011-09-01 | Aoki et al. | Applicant |
| US8027853(B1) | 2011-09-01 | Kazenas | Applicant |
| US8035508(B2) | 2011-10-01 | Breed | Applicant |
| US8040247(B2) | 2011-10-01 | Gunaratne | Applicant |
| US8090598(B2) | 2012-01-01 | Bauer et al. | Applicant |
| US8095394(B2) | 2012-01-01 | Nowak et al. | Applicant |
| US8117049(B2) | 2012-02-01 | Berkobin et al. | Applicant |
| US8140358(B1) | 2012-03-01 | Ling et al. | Applicant |
| US8140359(B2) | 2012-03-01 | Daniel | Applicant |
| US8180522(B2) | 2012-05-01 | Tuff | Applicant |
| US8180655(B1) | 2012-05-01 | Hopkins, III | Applicant |
| US8185380(B2) | 2012-05-01 | Kameyama | Applicant |
| US8188887(B2) | 2012-05-01 | Catten et al. | Applicant |
| US8190323(B2) | 2012-05-01 | Maeda et al. | Applicant |
| US8255243(B2) | 2012-08-01 | Raines et al. | Applicant |
| US8255244(B2) | 2012-08-01 | Raines et al. | Applicant |
| US8260489(B2) | 2012-09-01 | Nielsen et al. | Applicant |
| US8260639(B1) | 2012-09-01 | Medina, III et al. | Applicant |
| US8265861(B2) | 2012-09-01 | Ikeda et al. | Applicant |
| US8280752(B1) | 2012-10-01 | Cripe et al. | Applicant |
| US8311858(B2) | 2012-11-01 | Everett et al. | Applicant |
| US8314708(B2) | 2012-11-01 | Gunderson et al. | Applicant |
| US8340893(B2) | 2012-12-01 | Yamaguchi et al. | Applicant |
| US8352118(B1) | 2013-01-01 | Mittelsteadt et al. | Applicant |
| US8355837(B2) | 2013-01-01 | Avery et al. | Applicant |
| US8364391(B2) | 2013-01-01 | Nagase et al. | Applicant |
| US8384534(B2) | 2013-02-01 | James et al. | Applicant |
| US8386168(B2) | 2013-02-01 | Hao | Applicant |
| US8423239(B2) | 2013-04-01 | Blumer et al. | Applicant |
| US8447231(B2) | 2013-05-01 | Bai et al. | Applicant |
| US8487775(B2) | 2013-07-01 | Victor et al. | Applicant |
| US8554468(B1) | 2013-10-01 | Bullock | Applicant |
| US8554587(B1) | 2013-10-01 | Nowak et al. | Applicant |
| US8566126(B1) | 2013-10-01 | Hopkins, III | Applicant |
| US8595034(B2) | 2013-11-01 | Bauer et al. | Applicant |
| US8595037(B1) | 2013-11-01 | Hyde et al. | Applicant |
| US8698639(B2) | 2014-04-01 | Fung et al. | Applicant |
| US8700251(B1) | 2014-04-01 | Zhu et al. | Applicant |
| US8742936(B2) | 2014-06-01 | Galley et al. | Applicant |
| US8781669(B1) | 2014-07-01 | Teller et al. | Applicant |
| US8816836(B2) | 2014-08-01 | Lee et al. | Applicant |
| US8849558(B2) | 2014-09-01 | Morotomi et al. | Applicant |
| US8874301(B1) | 2014-10-01 | Rao | Examiner |
| US8876535(B2) | 2014-11-01 | Fields et al. | Applicant |
| US8954226(B1) | 2015-02-01 | Binion et al. | Applicant |
| US8965677(B2) | 2015-02-01 | Breed et al. | Applicant |
| US9135803(B1) | 2015-09-01 | Fields et al. | Applicant |
| US9144389(B2) | 2015-09-01 | Srinivasan | Examiner |
| US9147219(B2) | 2015-09-01 | Binion et al. | Applicant |
| US9157752(B1) | 2015-10-01 | Fernandez Garcia | Examiner |
| US2001/0005217(A1) | 2001-06-01 | Hamilton et al. | Applicant |
| US2002/0016655(A1) | 2002-02-01 | Joao | Applicant |
| US2002/0111725(A1) | 2002-08-01 | Burge | Applicant |
| US2002/0116228(A1) | 2002-08-01 | Bauer et al. | Applicant |
| US2002/0128882(A1) | 2002-09-01 | Nakagawa et al. | Applicant |
| US2002/0146667(A1) | 2002-10-01 | Dowdell et al. | Applicant |
| US2003/0028298(A1) | 2003-02-01 | Macky et al. | Applicant |
| US2003/0061160(A1) | 2003-03-01 | Asahina | Applicant |
| US2003/0200123(A1) | 2003-10-01 | Burge et al. | Applicant |
| US2004/0005927(A1) | 2004-01-01 | Bonilla et al. | Applicant |
| US2004/0017106(A1) | 2004-01-01 | Aizawa et al. | Applicant |
| US2004/0039503(A1) | 2004-02-01 | Doyle | Applicant |
| US2004/0054452(A1) | 2004-03-01 | Bjorkman | Applicant |
| US2004/0077285(A1) | 2004-04-01 | Bonilla et al. | Applicant |
| US2004/0085198(A1) | 2004-05-01 | Saito et al. | Applicant |
| US2004/0090334(A1) | 2004-05-01 | Zhang et al. | Applicant |
| US2004/0111301(A1) | 2004-06-01 | Wahlbin et al. | Applicant |
| US2004/0122639(A1) | 2004-06-01 | Qiu | Applicant |
| US2004/0139034(A1) | 2004-07-01 | Farmer | Applicant |
| US2004/0153362(A1) | 2004-08-01 | Bauer et al. | Applicant |
| US2004/0158476(A1) | 2004-08-01 | Blessinger et al. | Applicant |
| US2004/0204837(A1) | 2004-10-01 | Singleton | Examiner |
| US2004/0226043(A1) | 2004-11-01 | Mettu et al. | Applicant |
| US2004/0260579(A1) | 2004-12-01 | Tremiti | Applicant |
| US2005/0073438(A1) | 2005-04-01 | Rodgers et al. | Applicant |
| US2005/0107673(A1) | 2005-05-01 | Ball | Examiner |
| US2005/0108910(A1) | 2005-05-01 | Esparza et al. | Applicant |
| US2005/0131597(A1) | 2005-06-01 | Raz et al. | Applicant |
| US2005/0259151(A1) | 2005-11-01 | Hamilton et al. | Applicant |
| US2005/0267784(A1) | 2005-12-01 | Slen et al. | Applicant |
| US2006/0031103(A1) | 2006-02-01 | Henry | Applicant |
| US2006/0052909(A1) | 2006-03-01 | Cherouny | Applicant |
| US2006/0053038(A1) | 2006-03-01 | Warren et al. | Applicant |
| US2006/0079280(A1) | 2006-04-01 | LaPerch | Applicant |
| US2006/0092043(A1) | 2006-05-01 | Lagassey | Applicant |
| US2006/0136291(A1) | 2006-06-01 | Morita et al. | Applicant |
| US2006/0184295(A1) | 2006-08-01 | Hawkins et al. | Applicant |
| US2006/0212195(A1) | 2006-09-01 | Veith et al. | Applicant |
| US2006/0232430(A1) | 2006-10-01 | Takaoka et al. | Applicant |
| US2007/0001831(A1) | 2007-01-01 | Raz et al. | Applicant |
| US2007/0055422(A1) | 2007-03-01 | Anzai et al. | Applicant |
| US2007/0080816(A1) | 2007-04-01 | Haque et al. | Applicant |
| US2007/0122771(A1) | 2007-05-01 | Maeda et al. | Applicant |
| US2007/0132773(A1) | 2007-06-01 | Plante | Applicant |
| US2007/0149208(A1) | 2007-06-01 | Syrbe et al. | Applicant |
| US2007/0159344(A1) | 2007-07-01 | Kisacanin | Applicant |
| US2007/0219720(A1) | 2007-09-01 | Trepagnier et al. | Applicant |
| US2007/0265540(A1) | 2007-11-01 | Fuwamoto | Examiner |
| US2007/0282638(A1) | 2007-12-01 | Surovy | Applicant |
| US2007/0299700(A1) | 2007-12-01 | Gay et al. | Applicant |
| US2008/0027761(A1) | 2008-01-01 | Bracha | Applicant |
| US2008/0052134(A1) | 2008-02-01 | Nowak et al. | Applicant |
| US2008/0061953(A1) | 2008-03-01 | Bhogal et al. | Applicant |
| US2008/0064014(A1) | 2008-03-01 | Wojtczak et al. | Applicant |
| US2008/0065427(A1) | 2008-03-01 | Helitzer et al. | Applicant |
| US2008/0082372(A1) | 2008-04-01 | Burch | Applicant |
| US2008/0084473(A1) | 2008-04-01 | Romanowich | Applicant |
| US2008/0111666(A1) | 2008-05-01 | Plante et al. | Applicant |
| US2008/0114502(A1) | 2008-05-01 | Breed et al. | Applicant |
| US2008/0126137(A1) | 2008-05-01 | Kidd et al. | Applicant |
| US2008/0147266(A1) | 2008-06-01 | Plante et al. | Applicant |
| US2008/0147267(A1) | 2008-06-01 | Plante et al. | Applicant |
| US2008/0189142(A1) | 2008-08-01 | Brown et al. | Applicant |
| US2008/0255887(A1) | 2008-10-01 | Gruter | Applicant |
| US2008/0255888(A1) | 2008-10-01 | Berkobin et al. | Applicant |
| US2008/0258890(A1) | 2008-10-01 | Follmer et al. | Applicant |
| US2008/0291008(A1) | 2008-11-01 | Jeon | Applicant |
| US2008/0297488(A1) | 2008-12-01 | Operowsky et al. | Applicant |
| US2008/0319665(A1) | 2008-12-01 | Berkobin et al. | Applicant |
| US2009/0015684(A1) | 2009-01-01 | Ooga et al. | Applicant |
| US2009/0063030(A1) | 2009-03-01 | Howarter et al. | Applicant |
| US2009/0132294(A1) | 2009-05-01 | Haines | Applicant |
| US2009/0207005(A1) | 2009-08-01 | Habetha et al. | Applicant |
| US2009/0267801(A1) | 2009-10-01 | Kawai et al. | Applicant |
| US2010/0030540(A1) | 2010-02-01 | Choi et al. | Applicant |
| US2010/0030586(A1) | 2010-02-01 | Taylor et al. | Applicant |
| US2010/0055649(A1) | 2010-03-01 | Takahashi et al. | Applicant |
| US2010/0076646(A1) | 2010-03-01 | Basir et al. | Applicant |
| US2010/0106356(A1) | 2010-04-01 | Trepagnier et al. | Applicant |
| US2010/0128127(A1) | 2010-05-01 | Ciolli | Applicant |
| US2010/0131300(A1) | 2010-05-01 | Collopy et al. | Applicant |
| US2010/0131302(A1) | 2010-05-01 | Collopy et al. | Applicant |
| US2010/0131304(A1) | 2010-05-01 | Collopy et al. | Applicant |
| US2010/0131307(A1) | 2010-05-01 | Collopy et al. | Applicant |
| US2010/0214087(A1) | 2010-08-01 | Nakagoshi et al. | Applicant |
| US2010/0293033(A1) | 2010-11-01 | Hall et al. | Applicant |
| US2010/0299021(A1) | 2010-11-01 | Jalili | Applicant |
| US2011/0054767(A1) | 2011-03-01 | Schafer et al. | Applicant |
| US2011/0066310(A1) | 2011-03-01 | Sakai et al. | Applicant |
| US2011/0087505(A1) | 2011-04-01 | Terlep | Applicant |
| US2011/0090075(A1) | 2011-04-01 | Armitage et al. | Applicant |
| US2011/0090093(A1) | 2011-04-01 | Grimm et al. | Applicant |
| US2011/0106370(A1) | 2011-05-01 | Duddle et al. | Applicant |
| US2011/0133954(A1) | 2011-06-01 | Ooshima et al. | Applicant |
| US2011/0137684(A1) | 2011-06-01 | Peak et al. | Applicant |
| US2011/0140968(A1) | 2011-06-01 | Bai et al. | Applicant |
| US2011/0153367(A1) | 2011-06-01 | Amigo et al. | Applicant |
| US2011/0196571(A1) | 2011-08-01 | Foladare et al. | Applicant |
| US2011/0202305(A1) | 2011-08-01 | Willis et al. | Applicant |
| US2011/0295446(A1) | 2011-12-01 | Basir et al. | Applicant |
| US2011/0301839(A1) | 2011-12-01 | Pudar et al. | Applicant |
| US2011/0304465(A1) | 2011-12-01 | Boult et al. | Applicant |
| US2011/0307188(A1) | 2011-12-01 | Peng et al. | Applicant |
| US2012/0004933(A1) | 2012-01-01 | Foladare et al. | Applicant |
| US2012/0010906(A1) | 2012-01-01 | Foladare et al. | Applicant |
| US2012/0025969(A1) | 2012-02-01 | Dozza | Applicant |
| US2012/0028680(A1) | 2012-02-01 | Breed | Applicant |
| US2012/0059227(A1) | 2012-03-01 | Friedlander | Examiner |
| US2012/0066007(A1) | 2012-03-01 | Ferrick et al. | Applicant |
| US2012/0071151(A1) | 2012-03-01 | Abramson et al. | Applicant |
| US2012/0072243(A1) | 2012-03-01 | Collins et al. | Applicant |
| US2012/0072244(A1) | 2012-03-01 | Collins et al. | Applicant |
| US2012/0083668(A1) | 2012-04-01 | Pradeep et al. | Applicant |
| US2012/0083960(A1) | 2012-04-01 | Zhu et al. | Applicant |
| US2012/0083974(A1) | 2012-04-01 | Sandblom | Applicant |
| US2012/0101855(A1) | 2012-04-01 | Collins et al. | Applicant |
| US2012/0108909(A1) | 2012-05-01 | Slobounov et al. | Applicant |
| US2012/0109692(A1) | 2012-05-01 | Collins et al. | Applicant |
| US2012/0123806(A1) | 2012-05-01 | Schumann, Jr. et al. | Applicant |
| US2012/0135382(A1) | 2012-05-01 | Winston et al. | Applicant |
| US2012/0143630(A1) | 2012-06-01 | Hertenstein | Applicant |
| US2012/0172055(A1) | 2012-07-01 | Edge | Applicant |
| US2012/0185204(A1) | 2012-07-01 | Jallon et al. | Applicant |
| US2012/0190001(A1) | 2012-07-01 | Knight et al. | Applicant |
| US2012/0191343(A1) | 2012-07-01 | Haleem | Applicant |
| US2012/0197669(A1) | 2012-08-01 | Kote et al. | Applicant |
| US2012/0209634(A1) | 2012-08-01 | Ling et al. | Applicant |
| US2012/0215375(A1) | 2012-08-01 | Chang | Applicant |
| US2012/0235865(A1) | 2012-09-01 | Nath et al. | Applicant |
| US2012/0239471(A1) | 2012-09-01 | Grimm et al. | Applicant |
| US2012/0246733(A1) | 2012-09-01 | Schafer et al. | Applicant |
| US2012/0256769(A1) | 2012-10-01 | Satpathy | Examiner |
| US2012/0258702(A1) | 2012-10-01 | Matsuyama | Applicant |
| US2012/0277950(A1) | 2012-11-01 | Plante et al. | Applicant |
| US2012/0316406(A1) | 2012-12-01 | Rahman et al. | Applicant |
| US2013/0006674(A1) | 2013-01-01 | Bowne et al. | Applicant |
| US2013/0006675(A1) | 2013-01-01 | Bowne et al. | Applicant |
| US2013/0018677(A1) | 2013-01-01 | Chevrette | Applicant |
| US2013/0038437(A1) | 2013-02-01 | Talati et al. | Applicant |
| US2013/0046562(A1) | 2013-02-01 | Taylor et al. | Applicant |
| US2013/0073115(A1) | 2013-03-01 | Levin et al. | Applicant |
| US2013/0116855(A1) | 2013-05-01 | Nielsen et al. | Applicant |
| US2013/0144459(A1) | 2013-06-01 | Ricci | Applicant |
| US2013/0151202(A1) | 2013-06-01 | Denny et al. | Applicant |
| US2013/0164715(A1) | 2013-06-01 | Hunt et al. | Applicant |
| US2013/0179198(A1) | 2013-07-01 | Bowne et al. | Applicant |
| US2013/0189649(A1) | 2013-07-01 | Mannino | Applicant |
| US2013/0209968(A1) | 2013-08-01 | Miller et al. | Applicant |
| US2013/0218603(A1) | 2013-08-01 | Hagelstein et al. | Applicant |
| US2013/0218604(A1) | 2013-08-01 | Hagelstein et al. | Applicant |
| US2013/0227409(A1) | 2013-08-01 | Das et al. | Applicant |
| US2013/0245881(A1) | 2013-09-01 | Scarbrough | Applicant |
| US2013/0267194(A1) | 2013-10-01 | Breed | Applicant |
| US2013/0289819(A1) | 2013-10-01 | Hassib et al. | Applicant |
| US2013/0302758(A1) | 2013-11-01 | Wright | Applicant |
| US2013/0304513(A1) | 2013-11-01 | Hyde et al. | Applicant |
| US2013/0304514(A1) | 2013-11-01 | Hyde et al. | Applicant |
| US2013/0307786(A1) | 2013-11-01 | Heubel | Applicant |
| US2013/0317693(A1) | 2013-11-01 | Jefferies et al. | Applicant |
| US2013/0317711(A1) | 2013-11-01 | Plante | Applicant |
| US2013/0317865(A1) | 2013-11-01 | Tofte et al. | Applicant |
| US2014/0002651(A1) | 2014-01-01 | Plante | Applicant |
| US2014/0009307(A1) | 2014-01-01 | Bowers et al. | Applicant |
| US2014/0012492(A1) | 2014-01-01 | Bowers et al. | Applicant |
| US2014/0039934(A1) | 2014-02-01 | Rivera | Applicant |
| US2014/0047347(A1) | 2014-02-01 | Mohn et al. | Applicant |
| US2014/0047371(A1) | 2014-02-01 | Palmer et al. | Applicant |
| US2014/0052323(A1) | 2014-02-01 | Reichel et al. | Applicant |
| US2014/0059066(A1) | 2014-02-01 | Koloskov | Applicant |
| US2014/0070980(A1) | 2014-03-01 | Park | Applicant |
| US2014/0099607(A1) | 2014-04-01 | Armitage et al. | Applicant |
| US2014/0100892(A1) | 2014-04-01 | Collopy et al. | Applicant |
| US2014/0104405(A1) | 2014-04-01 | Weidl | Examiner |
| US2014/0108198(A1) | 2014-04-01 | Jariyasunant et al. | Applicant |
| US2014/0125474(A1) | 2014-05-01 | Gunaratne | Applicant |
| US2014/0135598(A1) | 2014-05-01 | Weidl | Examiner |
| US2014/0167967(A1) | 2014-06-01 | He et al. | Applicant |
| US2014/0168399(A1) | 2014-06-01 | Plummer et al. | Applicant |
| US2014/0172467(A1) | 2014-06-01 | He et al. | Applicant |
| US2014/0172727(A1) | 2014-06-01 | Abhyanker et al. | Applicant |
| US2014/0218187(A1) | 2014-08-01 | Chun et al. | Applicant |
| US2014/0221781(A1) | 2014-08-01 | Schrauf | Examiner |
| US2014/0240132(A1) | 2014-08-01 | Bychkov | Applicant |
| US2014/0257866(A1) | 2014-09-01 | Gay et al. | Applicant |
| US2014/0278840(A1) | 2014-09-01 | Scofield et al. | Applicant |
| US2014/0309864(A1) | 2014-10-01 | Ricci | Applicant |
| US2014/0310186(A1) | 2014-10-01 | Ricci | Applicant |
| US2015/0024705(A1) | 2015-01-01 | Rashidi | Applicant |
| US2015/0051752(A1) | 2015-02-01 | Paszkowicz | Applicant |
| US2015/0066284(A1) | 2015-03-01 | Yopp | Examiner |
| US2015/0070265(A1) | 2015-03-01 | Cruz-Hernandez et al. | Applicant |
| US2015/0088334(A1) | 2015-03-01 | Bowers et al. | Applicant |
| US2015/0088550(A1) | 2015-03-01 | Bowers et al. | Applicant |
| US2015/0112504(A1) | 2015-04-01 | Binion et al. | Applicant |
| US2015/0112545(A1) | 2015-04-01 | Binion et al. | Applicant |
| US2015/0112730(A1) | 2015-04-01 | Binion et al. | Applicant |
| US2015/0112731(A1) | 2015-04-01 | Binion et al. | Applicant |
| US2015/0112800(A1) | 2015-04-01 | Binion et al. | Applicant |
| US2015/0120331(A1) | 2015-04-01 | Russo et al. | Applicant |
| US2015/0158469(A1) | 2015-06-01 | Cheatham, III et al. | Applicant |
| US2015/0160653(A1) | 2015-06-01 | Cheatham, III et al. | Applicant |
| US2015/0170287(A1) | 2015-06-01 | Tirone et al. | Applicant |
| US2015/0178998(A1) | 2015-06-01 | Attard et al. | Applicant |
| US2015/0185034(A1) | 2015-07-01 | Abhyanker | Applicant |
| US2015/0187013(A1) | 2015-07-01 | Adams et al. | Applicant |
| US2015/0233719(A1) | 2015-08-01 | Cudak | Examiner |
| US2015/0242953(A1) | 2015-08-01 | Suiter | Applicant |
| US2015/0254955(A1) | 2015-09-01 | Fields et al. | Applicant |
| US2016/0071418(A1) | 2016-03-01 | Oshida | Examiner |
| EP700009(A2) | 1996-03-01 | Applicant | |
| GB2268608(A) | 1994-01-01 | Applicant | |
| GB2494727(A) | 2013-03-01 | Applicant | |
| JP2002-259708(A) | 2002-09-01 | Applicant | |
| WO-2005/083605(A1) | 2005-09-01 | Applicant | |
| WO-2010/034909(A1) | 2010-04-01 | Applicant | |
| WO-2014/139821(A1) | 2014-09-01 | Applicant |
Non-Patent Literature (128)
- “Driverless Cars . . . The Future is Already Here”, Autolnsurance Center, downloaded from the Internet at: <http://www.autoinsurancecenter.com/driverless-cars . . . the-future-is-already-here.htm> (2010; downloaded on Mar. 27, 2014).Applicant
- “Integrated Vehicle-Based Safety Systems (IVBSS)”, Research and Innovative Technology Administration (RITA), http://www.its.dot.gov/ivbss/, retrieved from the internet on Nov. 4, 2013, 3 pages.Applicant
- Advisory Action dated Apr. 1, 2015 for U.S. Appl. No. 14/269,490, 4 pgs.Applicant
- Carroll et al. “Where Innovation is Sorely Needed”, http://www.technologyreview.com/news/422568/where-innovation-is-sorely-needed/?nlid, retrieved from the internet on Nov. 4, 2013, 3 pages.Applicant
- Davies, Avoiding Squirrels and Other Things Google's Robot Car Can't Do, downloaded from the Internet at: <http://www.wired.com/2014/05/google-self-driving-car-can-cant/ (downloaded on May 28, 2014).Applicant
- Final Office Action, U.S. Appl. No. 14/255,934, dated Sep. 23, 2014.Applicant
- Final Office Action, U.S. Appl. No. 14/269,490, dated Jan. 23, 2015.Applicant
- Hancock et al., “The Impact of Emotions and Predominant Emotion Regulation Technique on Driving Performance,” pp. 5882-5885 (2012).Applicant
- Levendusky, Advancements in automotive technology and their effect on personal auto insurance, downloaded from the Internet at: <http://www.verisk.com/visualize/advancements-in-automotive-technology-and-their-effect> (2013).Applicant
- McCraty et al., “The Effects of Different Types of Music on Mood, Tension, and Mental Clarity.” Alternative Therapies in Health and Medicine 4.1 (1998): 75-84. NCBI PubMed. Web. Jul. 11, 2013.Applicant
- Mui, Will auto insurers survive their collision with driverless cars? (Part 6), downloaded from the Internet at: <http://www.forbes.com/sites/chunkamui/2013/03/28/will-auto-insurers-survive-their-collision> (Mar. 28, 2013).Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/255,934, dated Jan. 15, 2015.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/255,934, dated Jun. 18, 2014.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/269,490, dated Sep. 12, 2014.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,184, dated Feb. 1, 2016.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,188, dated Dec. 3, 2015.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,206, dated Nov. 20, 2015.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,226, dated Jan. 13, 2016.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,249, dated Jan. 20, 2016.Applicant
- Nonfinal Office Action, U.S. Appl. No. 14/713,271, dated Nov. 6, 2015.Applicant
- Notice of Allowance in U.S. Appl. No. 14/057,408 dated Sep. 25, 2014.Applicant
- Notice of Allowance in U.S. Appl. No. 14/057,419 dated Oct. 5, 2015.Applicant
- Notice of Allowance in U.S. Appl. No. 14/208,626 dated May 11, 2015.Applicant
- Notice of Allowance in U.S. Appl. No. 14/208,626 dated Sep. 1, 2015.Applicant
- Notice of Allowance in U.S. Appl. No. 14/255,934 dated May 27, 2015.Applicant
- Notice of Allowance in U.S. Appl. No. 14/729,290 dated Aug. 5, 2015.Applicant
- Office Action dated for U.S. Appl. No. 14/511,712 dated Dec. 26, 2014.Applicant
- Office Action in U.S. Appl. No. 13/844,090 dated Dec. 4, 2013.Applicant
- Office Action in U.S. Appl. No. 14/057,419 dated Mar. 31, 2015.Applicant
- Office Action in U.S. Appl. No. 14/057,419 dated Oct. 9, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,456 dated Mar. 17, 2015.Applicant
- Office Action in U.S. Appl. No. 14/201,491 dated Apr. 29, 2015.Applicant
- Office Action in U.S. Appl. No. 14/201,491 dated Jan. 16, 2015.Applicant
- Office Action in U.S. Appl. No. 14/201,491 dated Sep. 11, 2015.Applicant
- Office Action in U.S. Appl. No. 14/201,491 dated Sep. 26, 2014.Applicant
- Office Action in U.S. Appl. No. 14/215,789 dated Sep. 17, 2015.Applicant
- Office Action in U.S. Appl. No. 14/255,934 dated Jan. 15, 2015.Applicant
- Office Action in U.S. Appl. No. 14/255,934 dated Jun. 18, 2014.Applicant
- Office Action in U.S. Appl. No. 14/255,934 dated Sep. 23, 2014.Applicant
- Office Action in U.S. Appl. No. 14/269,490 dated Jan. 23, 2015.Applicant
- Office Action in U.S. Appl. No. 14/269,490 dated Jun. 11, 2015.Applicant
- Office Action in U.S. Appl. No. 14/269,490 dated Sep. 12, 2014.Applicant
- Office Action in U.S. Appl. No. 14/511,712 dated Jun. 25, 2015.Applicant
- Office Action in U.S. Appl. No. 14/511,712 dated Oct. 10, 2014.Applicant
- Office Action in U.S. Appl. No. 14/511,750 dated Dec. 19, 2014.Applicant
- Office Action in U.S. Appl. No. 14/511,750 dated Jun. 30, 2015.Applicant
- Office Action in U.S. Appl. No. 14/057,408 dated Jan. 28, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,408 dated May 22, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,419 dated Jan. 28, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,419 dated Jun. 18, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,435 dated Jul. 23, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,435 dated Mar. 20, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,435 dated May 29, 2015.Applicant
- Office Action in U.S. Appl. No. 14/057,435 dated Nov. 18, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,447 dated Aug. 28, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,447 dated Dec. 18, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,447 dated Feb. 24, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,447 dated Jul. 6, 2015.Applicant
- Office Action in U.S. Appl. No. 14/057,456 dated Mar. 14, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,456 dated Oct. 28, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,467 dated Feb. 23, 2015.Applicant
- Office Action in U.S. Appl. No. 14/057,467 dated Jan. 27, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,467 dated Jun. 11, 2014.Applicant
- Office Action in U.S. Appl. No. 14/057,467 dated Oct. 17, 2014.Applicant
- Office Action in U.S. Appl. No. 14/208,626 dated Apr. 29, 2014.Applicant
- Office Action in U.S. Appl. No. 14/208,626 dated Aug. 13, 2014.Applicant
- Office Action in U.S. Appl. No. 14/208,626 dated Dec. 23, 2014.Applicant
- Office Action in U.S. Appl. No. 14/339,652 dated May 15, 2015.Applicant
- Office Action in U.S. Appl. No. 14/339,652 dated Oct. 23, 2014.Applicant
- Office Action in U.S. Appl. No. 14/339,652 dated Sep. 24, 2015.Applicant
- Office Action in U.S. Appl. No. 14/528,424 dated Feb. 27, 2015.Applicant
- Office Action in U.S. Appl. No. 14/528,424 dated Jul. 30, 2015.Applicant
- Office Action in U.S. Appl. No. 14/528,642 dated Jan. 13, 2015.Applicant
- Office Action in U.S. Appl. No. 14/713,230 dated Oct. 9, 2015.Applicant
- Office Action in U.S. Appl. No. 14/713,254 dated Oct. 9, 2015.Applicant
- Office Action in U.S. Appl. No. 14/718,338 dated Jul. 7, 2015.Applicant
- Office Action, U.S. Appl. No. 14/713,261, dated Oct. 21, 2015.Applicant
- Read, Autonomous cars & the death of auto insurance, downloaded from the Internet at: <http://www.thecarconnection.com/news/1083266_autonomous-cars-the-death-of-auto-insurance> (Apr. 1, 2013).Applicant
- Riley et al., U.S. Appl. No. 14/269,490, filed May 5, 2014.Applicant
- Ryan, Can having safety features reduce your insurance premiums? (Dec. 15, 2010).Applicant
- Search Report in EP Application No. 13167206.5 dated Aug. 13, 2013, 6 pages.Applicant
- Sharma, Driving the future: the legal implications of autonomous vehicles conference recap, downloaded from the Internet at: <http://law.scu.edu/hightech/autonomousvehicleconfrecap2012> (2012).Applicant
- Stienstra, Autonomous Vehicles & the Insurance Industry, 2013 CAS Annual Meeting—Minneapolis, MN (2013).Applicant
- U.S. Appl. No. 14/215,789, filed Mar. 17, 2014, Baker et al., “Split Sensing Method”.Applicant
- U.S. Appl. No. 14/339,652, filed Jul. 24, 2014, Freeck et al., “System and Methods for Monitoring a Vehicle Operator and Monitoring an Operating Environment Within the Vehicle”.Applicant
- U.S. Appl. No. 14/511,712, filed Oct. 10, 2014, Fields et al., “Real-Time Driver Observation and Scoring for Driver's Education”.Applicant
- U.S. Appl. No. 14/511,750, filed Oct. 10, 2014, Fields et al., “Real-Time Driver Observation and Scoring for Driver's Education”.Applicant
- U.S. Appl. No. 14/528,424, filed Oct. 30, 2014, Christensen et al., “Systems and Methods for Processing Trip-Based Insurance Policies”.Applicant
- U.S. Appl. No. 14/528,642, filed Oct. 30, 2014, Christensen et al., “Systems and Methods for Managing Units Associated with Time-Based Insurance Policies”.Applicant
- U.S. Appl. No. 14/713,184, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Insurance Pricing”.Applicant
- U.S. Appl. No. 14/713,188, filed May 15, 2015, Konrardy et al., “Autonomous Feature Use Monitoring and Insurance Pricing”.Applicant
- U.S. Appl. No. 14/713,194, filed May 15, 2015, Konrardy et al., “Autonomous Communication Feature Use and Insurance Pricing”.Applicant
- U.S. Appl. No. 14/713,201, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Insurance Pricing and Offering Based Upon Accident Risk Factors”.Applicant
- U.S. Appl. No. 14/713,206, filed May 15, 2015, Konrardy et al., “Determining Autonomous Vehicle Technology Performance for Insurance Pricing and Offering”.Applicant
- U.S. Appl. No. 14/713,214, filed May 15, 2015, Konrardy et al., “Accident Risk Model Determination Using Autonomous Vehicle Operating Data”.Applicant
- U.S. Appl. No. 14/713,217, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Operation Feature Usage Recommendations”.Applicant
- U.S. Appl. No. 14/713,223, filed May 15, 2015, Konrardy et al., “Driver Feedback Alerts Based Upon Monitoring Use of Autonomous Vehicle Operation Features”.Applicant
- U.S. Appl. No. 14/713,226, filed May 15, 2015, Konrardy et al., “Accident Response Using Autonomous Vehicle Monitoring”.Applicant
- U.S. Appl. No. 14/713,230, filed May 15, 2015, Konrardy et al., “Accident Fault Determination for Autonomous Vehicles”.Applicant
- U.S. Appl. No. 14/713,237, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Technology Effectiveness Determination for Insurance Pricing”.Applicant
- U.S. Appl. No. 14/713,240, filed May 15, 2015, Konrardy et al., “Fault Determination with Autonomous Feature Use Monitoring”.Applicant
- U.S. Appl. No. 14/713,244, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Operation Feature Evaulation”.Applicant
- U.S. Appl. No. 14/713,249, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness”.Applicant
- U.S. Appl. No. 14/713,254, filed May 15, 2015, Konrardy et al., “Accident Fault Determination for Autonomous Vehicles”.Applicant
- U.S. Appl. No. 14/713,261, filed May 15, 2015, Konrardy et al., “Accident Fault Determination for Autonomous Vehicles”.Applicant
- U.S. Appl. No. 14/713,266, filed May 15, 2015, Konrardy et al., “Autonomous Vehicle Operation Feature Monitoring and Evaluation of Effectiveness”.Applicant
- U.S. Appl. No. 14/713,271, filed May 15, 2015, Konrardy et al. “Fully Autonomous Vehicle Insurance Pricing”.Applicant
- U.S. Appl. No. 14/729,290, filed Jun. 3, 2015, Fields et al., “Advanced Vehicle Operator Intelligence System”.Applicant
- U.S. Appl. No. 14/857,242, filed Sep. 17, 2015, Fields et al., “Advanced Vehicle Operator Intelligence System”.Applicant
- U.S. Appl. No. 14/934,326, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Operating Status Assessment”.Applicant
- U.S. Appl. No. 14/934,333, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Control Assessment and Selection”.Applicant
- U.S. Appl. No. 14/934,339, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Operator Identification”.Applicant
- U.S. Appl. No. 14/934,343, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Operating Style and Mode Monitoring”.Applicant
- U.S. Appl. No. 14/934,345, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Feature Recommendations”.Applicant
- U.S. Appl. No. 14/934,347, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Software Version Assessment”.Applicant
- U.S. Appl. No. 14/934,352, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Automatic Parking”.Applicant
- U.S. Appl. No. 14/934,355, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Insurance Based Upon Usage”.Applicant
- U.S. Appl. No. 14/934,357, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Salvage and Repair”.Applicant
- U.S. Appl. No. 14/934,361, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Infrastructure Communication Device”.Applicant
- U.S. Appl. No. 14/934,371, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Accident and Emergency Response”.Applicant
- U.S. Appl. No. 14/934,381, filed Nov. 6, 2015, Fields et al., “Personal Insurance Policies”.Applicant
- U.S. Appl. No. 14/934,385, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Operating Status Assessment”.Applicant
- U.S. Appl. No. 14/934,388, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Control Assessment and Selection”.Applicant
- U.S. Appl. No. 14/934,393, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Control Assessment and Selection”.Applicant
- U.S. Appl. No. 14/934,400, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Control Assessment and Selection”.Applicant
- U.S. Appl. No. 14/934,405, filed Nov. 6, 2015, Fields et al., “Autonomous Vehicle Automatic Parking”.Applicant
- Wiesenthal et al., “The Influence of Music on Driver Stress,” Journal of Applied Social Psychology 30(8)1 709-19 (2000).Applicant
- Young et al., “Cooperative Collision Warning Based Highway Vehicle Accident Reconstruction”, Eighth International Conference on Intelligent Systems Design and Applications, Nov. 26-28, 2008, pp. 561-565.Applicant