US20230134558A1 - Transmitting driving data to an insurance platform - Google Patents
Transmitting driving data to an insurance platform Download PDFInfo
- Publication number
- US20230134558A1 US20230134558A1 US17/840,046 US202217840046A US2023134558A1 US 20230134558 A1 US20230134558 A1 US 20230134558A1 US 202217840046 A US202217840046 A US 202217840046A US 2023134558 A1 US2023134558 A1 US 2023134558A1
- Authority
- US
- United States
- Prior art keywords
- user
- driving
- mobile device
- data
- insurance
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 claims description 13
- 238000005516 engineering process Methods 0.000 abstract description 44
- 230000006399 behavior Effects 0.000 description 12
- 230000015654 memory Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 7
- 230000001133 acceleration Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013459 approach Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 239000004984 smart glass Substances 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000003213 activating effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000011982 device technology Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007274 generation of a signal involved in cell-cell signaling Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0283—Price estimation or determination
Definitions
- the present disclosure generally relates to determining user driving behavior and, in particular, to determining user driving behavior using a mobile device.
- Insurance companies calculate rates for car insurance for customers based on various factors. For example, factors such as where a customer lives, the make, model, and year of the car they drive, and their age may all be taken into consideration when calculating an insurance rate. These factors are used to generate a driver profile that attempts to determine what type of driver the customer is (e.g., whether the customer is a risky driver or a safe driver). Riskier drivers may receive more costly insurance quotes than safer drivers. However, the use of these factors may not be as accurate as actual driving data in determining what type of driver a customer is.
- UBI Usage-Based Insurance
- UBI strategies typically involve the installation of a tracking device in a vehicle.
- some UBI strategies involve plugging the tracking device to the On-Board Diagnostic (OBD) device in the vehicle.
- OBD On-Board Diagnostic
- Such approaches involve at least a step where the user receives the tracking device from the insurance vendor or a third party, and a step where the user plugs the tracking device to the vehicle's OBD. Accordingly, users are discouraged from purchasing such UBI strategies due to the extra steps and the technical know-how involved.
- addition of a tracking device to the vehicle creates the issue of handling the hardware upon termination of the policy, or upgrading the policy to a new or different vehicle.
- the system includes one or more processors, one or more sensors configured to receive sensor data, and a machine-readable medium comprising instructions stored therein, which when executed by the one or more processors, cause the one or more processors to perform operations.
- the operations include generating driving data for the user based on the sensor data and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- Some aspects of the subject technology relate to a method for transmitting driving data for a user to an insurance platform.
- the method includes receiving sensor data from a mobile device associated with a user, determining whether the user is in a driving state based on the sensor data, generating driving data for the user when the user is in the driving state, and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- Some aspects of the subject technology relate to a non-transitory machine-readable medium comprising instructions stored therein, which when executed by a machine, cause the machine to perform operations.
- the operations include generating driving data for the user based on the sensor data from sensors on a smartphone device associated with a user and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- FIG. 1 is a block diagram illustrating an example environment in which a system for transmitting driving data for a user to an insurance platform may exist in accordance with various aspects of the subject technology.
- FIG. 2 is a block diagram illustrating an example ‘mobile device in accordance with various aspects of the subject technology.
- FIG. 3 is a flow chart illustrating an example process for providing driving data for a user to an insurance platform in accordance with various aspects of the subject technology.
- FIG. 4 is a block diagram illustrating an example computer system with which any of the computing machines, devices, or systems discussed herein may be implemented, in accordance with some aspects of the subject technology.
- a system may include one or more sensors configured to receive sensor data.
- Driving data for the user may be generated based on the sensor data and transmitted to an insurance platform for modification of an insurance product. For example, rates or fees associated with a vehicle insurance policy provided by the insurance platform may be adjusted by the insurance platform based on the received driving data.
- the insurance platform may more accurately assess what type of driver a user is, more accurately assess risks for the user, and provide the user with insurance products that are more personalized to the user and possibly lowering insurance costs for safe drivers.
- embodiments consistent with the present disclosure use the ability of mobile device technology to include detailed characteristics of a driver behavior in a personalized insurance policy. Some characteristics of a driver behavior include turning speed, braking speed, and acceleration patterns. Some embodiments include erratic behavior characteristics, such as continued lane shifting, speed irregularity, and directional features including sudden turns, drifting, and the like.
- FIG. 1 is a block diagram illustrating an example environment 100 in which a system for transmitting driving data for a user to an insurance platform may exist in accordance with various aspects of the subject technology.
- the environment 100 may include mobile device 105 and an insurance platform 130 in communication with one another via the network 150 , although in other implementations, additional entities or alternative entities may be used.
- the mobile device 105 may include, for example, a smart phone, a tablet, smart watch, a set of smart glasses, a camera device, or any other device capable of communicating with other devices via a network 150 .
- the mobile device 105 may be a computing device that is typically carried by or taken with the user. However, in other aspects of the subject technology, other computing devices may also be used.
- the system may be implemented as an application 115 installed on a mobile device 105 , such as a smart phone.
- a user may download an application 115 provided by the insurance platform 130 and install the application 115 on the user's smart phone.
- the application 115 may be previously installed on the user's smart phone.
- the application 115 may access data from the various hardware and software sensors of the user's mobile device 105 in order to generate driver data and transmit the driver data to the insurance platform.
- mobile device 105 may gather driver data provided wirelessly from the vehicle's OBD device.
- mobile device 105 is configured to communicate with the OBD device using a Bluetooth enabled transmitter included in the vehicle.
- the system may function without any specialized devices that may he costly to provide and confusing for a user to install on the user's vehicle.
- the system may be implemented on the user's smartphone, which is often carried by the user, the driving data may be personalized to the user and get a more complete picture of the driving habits of the user.
- the system implemented on the user's smartphone may be able to obtain driving data for the user when the user is driving other vehicles (as many families have two or more vehicles).
- the system may also prevent driving data for another person driving the user's vehicle from being used as the user's driving data because the user's smartphone is usually with the user and is not tied to the vehicle.
- the driving data generated by the system on the mobile device 105 may be transmitted to the insurance platform 130 over the network 150 .
- the network 150 may include, for example, any one or more of a cellular network, a satellite network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like. Further, the network 150 can include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, tree or hierarchical network, and the like.
- the insurance platform 130 may be implemented on one or more computing machines (e.g., servers) in communication with the network 150 .
- the insurance platform 130 May be associated with a single entity (e.g., a company) or multiple entities that work together to provide insurance services to customers.
- the insurance platform 130 is configured to receive the driving data for a user from the mobile device 105 and adjust one or more insurance products associated with the user based on the driving data.
- the insurance platform 130 may calculate a driving score based on the driving data for the user and adjust an existing insurance policy for the user, provide discounts or other products to the user based on the driving data, increase or decrease fees associated with an insurance product, or generate alerts to an owner of an insurance product. Advertisements or other content may also be provided to the owner of the insurance product based on the driving data for the user received from the mobile device 105 .
- FIG. 2 is a block diagram illustrating an example mobile device 200 in accordance with various aspects of the subject technology.
- Examples of a mobile device 200 may include a smartphone, a smart watch, or smart glasses.
- the mobile device 200 may include one or more sensors 230 , one or more memories 240 , one or more processors 250 , a network interface 260 , a display 270 , a speaker 280 , and/or a haptic-feedback interface 290 .
- the mobile device 200 may include additional components, fewer components, or alternative components.
- the sensors 230 may be configured to generate various sensor data that may be used to determine when a user is in a driving state (e.g., when the user is driving) and used to generate driving data about the user's driving behavior.
- the data can indicate turning speed, braking speed, acceleration patterns, continued lane shifting, speed irregularity, sudden turns, drifting, and the like.
- the sensors 230 may include, for example, a gyroscope 205 configured to generate orientation data, an accelerometer 210 configured to generate acceleration data, and/or a global positioning system (GPS) device 215 or other location sensing device configured to generate location data.
- GPS global positioning system
- the sensors 230 may also include application sensors 220 or software sensors configured to detect and generate mobile device usage data, For example, the application sensors 220 may determine whether a user is using the mobile device 200 , what the user is doing with the mobile device 200 , and other information about the user's interaction with the mobile device 200 . The mobile device usage data may be indicative of whether the user is focused on driving or instead interacting with the mobile device 200 while driving.
- the information may include, for example, what application is currently open and running (e.g., a text messaging application, an email application, a web browser, etc.), what application is being displayed, whether the user is providing input to the mobile device 200 (e.g., keyboard input, scrolling, accessing buttons or other interface items, etc.), or how active applications are (e.g., whether a web browser is actively requesting and loading content).
- the information may further include whether the mobile device 200 is receiving calls, an average number of calls per time period, whether the user picks up calls while driving, the average length of calls while driving, and any other information associated with the user's usage of the mobile device 200 .
- the information may also include user information such as account logins for certain applications.
- an application e.g., the application 115 in FIG. 1
- the sensors 230 may also include other sensors 225 not specifically shown in FIG. 2 .
- the system may include a camera configured to capture images, video, or video feeds, a microphone configured to record sounds, or one or more biometric scanners (e.g., a fingerprint scanner) configured to identify specific users that may be driving.
- the mobile device 200 may also include one or more memories 240 configured to store data such as sensor data or driving data to be transmitted to the insurance platform 130 .
- the memory 240 may also include a machine-readable medium (also referred to as a computer-readable medium) storing one or more sets of instructions, such as the application 115 in FIG. 1 , which may be executed by the processor 250 in order to perform the processes described herein.
- the network interface 260 is configured to transmit and receive data from the insurance platform 130 or other devices over the network 150 .
- the network interface 260 may transmit driving data to the insurance platform 130 and receive notifications, advertisements, or other content from the insurance platform 130 .
- the mobile device 200 may also include a display 270 , a speaker 280 , and/or a haptic feedback device 290 configured to provide information (e.g., visual content, audible content, or haptic feedback) to a user.
- the mobile device 200 may also include a power supply (not shown in FIG. 2 ) configured to provide the mobile device 200 with power.
- the power supply may be configured to interface with an external power source such as a wall outlet, vehicle power outlet, or an external battery.
- FIG. 3 is a flow chart illustrating an example process 300 for providing driving data for a user to an insurance platform in accordance with various aspects of the subject technology.
- FIG. 3 is shown in a particular order, other orderings are also possible. For example, some blocks may be performed in different orders or in parallel with other blocks.
- the process may be performed by a mobile device 105 and, in particular, an application 115 running on the mobile device 105 .
- a user of a mobile device 105 may download and install the application 115 on the mobile device 105 .
- the application 115 may open the application 115 on the mobile device 105 .
- the application 115 may authenticate the user so that the user may be associated with an account that is recognized by the insurance platform 130 . For example, authentication may occur based on the user providing a user name and password or through biometric input (e.g., scanning a fingerprint).
- the application 115 may run in the background on the mobile device 105 and, at block 305 , receive sensor data from the sensors of the mobile device 105 associated with the user.
- the application 115 may determine whether the user is driving (e.g., whether the user is in a driving state). The application may determine whether the user is driving based on any number of different factors or combinations of factors. For example, in some embodiments the user provides a manual indication of a driving condition simply by pressing a button, activating a touch screen tab provided by application 115 , or providing a voice input indicating the driving condition.
- the application 115 may determine whether the user is driving by determining, based on the sensor data from the mobile device, a speed at which the user is traveling and comparing that speed with a threshold speed (e.g., 15 miles per hour). If the user's speed is over the threshold speed, the application 115 may determine that the user is driving. According to some aspects of the subject technology, the application 115 may determine whether the user is driving by determining, based on the sensor data from the mobile device, a distance that the user has traveled and comparing that distance with a threshold distance (e.g., 3 miles). If the user has traveled more than the threshold distance, the application 115 may determine that the user is driving.
- a threshold speed e.g. 15 miles per hour
- the application 115 may determine whether the user is in the driving state by identifying, based on the sensor data from the mobile device, a route traveled by the user and determining whether that route is traveling a route associated with a particular transit type.
- the particular transit type may be a bus route, a train route, a public transportation route, a biking route, a boat route, a waterway, or an aerial route.
- the application 115 may determine that the user is driving if the route traveled by the user is associated with the particular transit type. in some embodiments, at least one of application 115 and insurance platform 130 discard driving data when the user is in a bus route, a train route, a public transportation route, a boat route, a waterway or an aerial route.
- the application 115 may determine whether the user is driving by prompting the user to provide an indication that the user is driving or not driving.
- the indication may include the user selecting a button on the display.
- the indication may include the user linking the mobile device 105 to the vehicle (e.g., a Bluetooth link).
- the user indicates a driving condition via a voice control feature included in application 115 .
- the application 115 may determine whether the user is driving by identifying wireless signals detected by the mobile device 105 .
- the wireless signals may include, for example, Bluetooth signals or Wi-Fi signals.
- the mobile device 105 detects a Wi-Fi network that is known to be a public transportation network, then the user may be on a form of public transportation and not driving. If the mobile device 105 detects 8 or more Bluetooth signals for a period of time (e.g., 2 minutes), then the mobile device 105 may be on a form of public transportation with other people using Bluetooth enabled devices. Accordingly, the user is deemed to not be driving.
- a Wi-Fi network that is known to be a public transportation network
- 8 or more Bluetooth signals for a period of time e.g., 2 minutes
- some embodiments include detailed data processing to indicate that the user of mobile device 105 is a driver and not a passenger of the vehicle.
- the data processing may include determining that the user is not manipulating mobile device 105 while driving data is collected.
- Other indicators of the user being actually at the wheel may include detecting that mobile device 105 is approximately in a fixed orientation relative to the vehicle orientation, or based on a connection (e.g., via Bluetooth) between the mobile device 105 and an onboard computer of the vehicle (e.g., indicating, for example, that the user is the driver because the user's smartphone is connected to the vehicle's telephone functionality).
- rules that combine multiple factors may be used in determining whether the user is driving.
- one example rule may state that a user is driving if the user has traveled over 40 miles per hour for one minute and/or 5 consecutive miles.
- Another example rule may state that a user is driving if the average speed for a user for the last hour is over 10 miles per hour.
- Driving data may include, for example, various speed measurements for the user, whether there are sudden braking actions, and/or sudden accelerations.
- the driving data may also include speed for certain situations such as entering school zones, on turns, and/or on on-ramps and off-ramps.
- the driving data may further include locations (e.g., general areas, cities, counties, etc.) in which the user typically drives, the amount of time the user drives in particular locations, and/or the when the user typically drives. The user's speed measurements can then be compared to known speed limits for the locations.
- the driving data may further include sensor data from the sensors on the mobile device 105 such as, for example, mobile device usage data.
- the application may transmit the driving data for the user to an insurance platform 130 where it may be used by the insurance platform 130 to assess one or more insurance products associated with the user or provide content to the user based on the driving data.
- the insurance platform may calculate a driving score for the user based on the user's driving data and adjust an existing insurance policy for the user, provide discounts or other products to the user based on the driving data, or increase or decrease fees associated with an insurance product.
- the insurance platform 130 may also generate communications. (e.g., alerts, messages, or notifications) for a user based on the user's driving data and transmit the alerts or notifications to the user.
- the insurance platform may email the user at an email address provided by the user or transmit communications to the mobile device 105 (e.g., a text message) and/or the application 115 (e.g., an application message or alert).
- the communications may include, for example, an assessment of recent driving activity of the user, notifications for safe or risky driving, tips on how to improve driving behavior, and/or information about how driving behavior (the user's or in general) may affect adjustments to insurance products.
- the application 115 on the mobile device 105 may be configured to analyze the generated driving data and determine driving behaviors of the user.
- the application 115 may also provide one or more real-time notifications about the driving behaviors to the user via the mobile device while the user is driving. For example, if the application 115 determines that a hard acceleration event was detected, the application 115 may send a notification to the user.
- the notification may include an audible sound or haptic feedback (e.g., two quick vibrations or buzzes) that may inform the user that a hard acceleration event was detected without the user having to take the user's eyes off the road.
- visual notifications may also be used. Notifications may also be generated for hard braking events, speeding, using the mobile device while driving, or any other driving behavior for the user.
- a driving score may be calculated and provided to the user along with driving details or characteristics about how the user was driving during a recent driving event. Tips on how to improve the score may also be delivered to the user.
- the information provided to the user may be provided in real-time as the information is calculated while the user is driving or after a driving event. Furthermore, the information may also be delivered to the user via an email.
- the feedback provided to the user may help the user modify the user's driving behavior (e.g., to help the user drive more safely) and, as a result, help the user adjust an insurance product associated with the user.
- FIG. 4 is a block diagram illustrating an example computer system 400 with which any of the computing machines, devices, or systems discussed herein may be implemented, in accordance with some aspects of the subject technology.
- the computer system 400 may be implemented using hardware or a combination of software and hardware, either in a dedicated server, or integrated into another entity, or distributed across multiple entities.
- the example computer system 400 includes a processor 402 , a main memory 404 , a static memory 406 , a disk drive unit 416 , and a network interface device 420 which communicate with each other via a bus 408 .
- the computer system 400 may further include an input/output interface 412 that may be configured to communicate - with various input/output devices such as video display units (e.g., liquid crystal (LCD) displays, cathode ray tubes (CRTs), or touch screens), an alphanumeric input device (e.g., a keyboard), a cursor control device (e.g., a mouse), or a signal generation device (e.g., a speaker).
- video display units e.g., liquid crystal (LCD) displays, cathode ray tubes (CRTs), or touch screens
- an alphanumeric input device e.g., a keyboard
- a cursor control device e.g., a mouse
- a signal generation device e.
- Processor 402 may be a general-purpose microprocessor (e.g., a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other manipulations of information.
- CPU central processing unit
- GPU graphics processing unit
- DSP Digital Signal Processor
- ASIC Application Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- PLD Programmable Logic Device
- a machine-readable medium may store one or more sets of instructions 424 embodying any one or more of the methodologies or functions described herein.
- the instructions 424 may also reside, completely or at least partially, within the main memory 404 and/or within the processor 402 during execution thereof by the computer system 400 , with the main memory 404 and the processor 402 also constituting machine-readable media.
- the instructions 424 may further be transmitted or received over a network 426 via the network interface device 420 .
- the machine-readable medium may be a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions.
- the machine-readable medium may include the drive unit 416 , the static memory 406 , the main memory 404 , the processor 402 , an external memory connected to the input/output interface 412 , or some other memory.
- the term “machine-readable medium” shall also be taken to include any non-transitory medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the embodiments discussed herein.
- the term “machine-readable medium” shall accordingly be taken to include, but not be limited to, storage mediums such as solid-state memories, optical media, and magnetic media.
- a phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology.
- a disclosure relating to an aspect may apply to all configurations, or one or more configurations.
- An aspect may provide one or more examples.
- a phrase such as an aspect may refer to one or more aspects and vice versa.
- a phrase such as an “embodiment” does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology.
- a disclosure relating to an embodiment may apply to all embodiments, or one or more embodiments.
- An embodiment may provide one or more examples.
- a phrase such an embodiment may refer to one or more embodiments and vice versa.
- a phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology.
- a disclosure relating to a configuration may apply to all configurations, or one or more configurations.
- a configuration may provide one or more examples.
- a phrase such a configuration may refer to one or more configurations and vice versa.
Landscapes
- Business, Economics & Management (AREA)
- Development Economics (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Various aspects of the subject technology relate to transmitting driving data for a user to an insurance platform. A system may include one or more sensors configured to receive sensor data. Driving data for the user may be generated based on the sensor data and transmitted to an insurance platform for assessment of an insurance product.
Description
- The present application claims priority to U.S. patent application Ser. No. 14/275,821 filed on May 12, 2014, which is incorporated by reference in its entirety herein.
- The present disclosure generally relates to determining user driving behavior and, in particular, to determining user driving behavior using a mobile device.
- Insurance companies calculate rates for car insurance for customers based on various factors. For example, factors such as where a customer lives, the make, model, and year of the car they drive, and their age may all be taken into consideration when calculating an insurance rate. These factors are used to generate a driver profile that attempts to determine what type of driver the customer is (e.g., whether the customer is a risky driver or a safe driver). Riskier drivers may receive more costly insurance quotes than safer drivers. However, the use of these factors may not be as accurate as actual driving data in determining what type of driver a customer is.
- Some attempts to achieve more accurate driver profiles and to broaden potential client base include Usage-Based Insurance (UBI) strategies. UBI strategies typically involve the installation of a tracking device in a vehicle. For example, some UBI strategies involve plugging the tracking device to the On-Board Diagnostic (OBD) device in the vehicle. Such approaches involve at least a step where the user receives the tracking device from the insurance vendor or a third party, and a step where the user plugs the tracking device to the vehicle's OBD. Accordingly, users are discouraged from purchasing such UBI strategies due to the extra steps and the technical know-how involved. Furthermore, addition of a tracking device to the vehicle creates the issue of handling the hardware upon termination of the policy, or upgrading the policy to a new or different vehicle.
- Various aspects of the subject technology relate to system-for transmitting driving data for a user to an insurance platform. The system includes one or more processors, one or more sensors configured to receive sensor data, and a machine-readable medium comprising instructions stored therein, which when executed by the one or more processors, cause the one or more processors to perform operations. The operations include generating driving data for the user based on the sensor data and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- Some aspects of the subject technology relate to a method for transmitting driving data for a user to an insurance platform. The method includes receiving sensor data from a mobile device associated with a user, determining whether the user is in a driving state based on the sensor data, generating driving data for the user when the user is in the driving state, and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- Some aspects of the subject technology relate to a non-transitory machine-readable medium comprising instructions stored therein, which when executed by a machine, cause the machine to perform operations. The operations include generating driving data for the user based on the sensor data from sensors on a smartphone device associated with a user and transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
- It is understood that other configurations of the subject technology will become readily apparent to those skilled in the art from the following detailed description, wherein various configurations of the subject technology are shown and described by way of illustration. As will be realized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
- The accompanying drawings, which are included to provide further understanding of the subject technology and are incorporated in, and constitute a part of this specification, illustrate disclosed aspects of the subject technology and together with the description serve to explain the principles of the subject technology.
-
FIG. 1 is a block diagram illustrating an example environment in which a system for transmitting driving data for a user to an insurance platform may exist in accordance with various aspects of the subject technology. -
FIG. 2 is a block diagram illustrating an example ‘mobile device in accordance with various aspects of the subject technology. -
FIG. 3 is a flow chart illustrating an example process for providing driving data for a user to an insurance platform in accordance with various aspects of the subject technology. -
FIG. 4 is a block diagram illustrating an example computer system with which any of the computing machines, devices, or systems discussed herein may be implemented, in accordance with some aspects of the subject technology. - The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, it will be apparent to those skilled in the art that the subject technology may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring the concepts of the subject technology.
- Various aspects of the subject technology relate to transmitting driving data for a user to an insurance platform. A system may include one or more sensors configured to receive sensor data. Driving data for the user may be generated based on the sensor data and transmitted to an insurance platform for modification of an insurance product. For example, rates or fees associated with a vehicle insurance policy provided by the insurance platform may be adjusted by the insurance platform based on the received driving data. By using driving data for a user, the insurance platform may more accurately assess what type of driver a user is, more accurately assess risks for the user, and provide the user with insurance products that are more personalized to the user and possibly lowering insurance costs for safe drivers. Accordingly, embodiments consistent with the present disclosure use the ability of mobile device technology to include detailed characteristics of a driver behavior in a personalized insurance policy. Some characteristics of a driver behavior include turning speed, braking speed, and acceleration patterns. Some embodiments include erratic behavior characteristics, such as continued lane shifting, speed irregularity, and directional features including sudden turns, drifting, and the like.
-
FIG. 1 is a block diagram illustrating anexample environment 100 in which a system for transmitting driving data for a user to an insurance platform may exist in accordance with various aspects of the subject technology. Theenvironment 100 may includemobile device 105 and aninsurance platform 130 in communication with one another via thenetwork 150, although in other implementations, additional entities or alternative entities may be used. - The
mobile device 105 may include, for example, a smart phone, a tablet, smart watch, a set of smart glasses, a camera device, or any other device capable of communicating with other devices via anetwork 150. Themobile device 105 may be a computing device that is typically carried by or taken with the user. However, in other aspects of the subject technology, other computing devices may also be used. According to some aspects of the subject technology, the system may be implemented as anapplication 115 installed on amobile device 105, such as a smart phone. For example, a user may download anapplication 115 provided by theinsurance platform 130 and install theapplication 115 on the user's smart phone. Alternatively, theapplication 115 may be previously installed on the user's smart phone. Theapplication 115 may access data from the various hardware and software sensors of the user'smobile device 105 in order to generate driver data and transmit the driver data to the insurance platform. In some embodimentsmobile device 105 may gather driver data provided wirelessly from the vehicle's OBD device. For example, in some embodimentsmobile device 105 is configured to communicate with the OBD device using a Bluetooth enabled transmitter included in the vehicle. - Accordingly, the system may function without any specialized devices that may he costly to provide and confusing for a user to install on the user's vehicle. Furthermore, because the system may be implemented on the user's smartphone, which is often carried by the user, the driving data may be personalized to the user and get a more complete picture of the driving habits of the user. For example, compared to a device that may be installed on or plugged into a vehicle, the system implemented on the user's smartphone may be able to obtain driving data for the user when the user is driving other vehicles (as many families have two or more vehicles). The system may also prevent driving data for another person driving the user's vehicle from being used as the user's driving data because the user's smartphone is usually with the user and is not tied to the vehicle.
- The driving data generated by the system on the
mobile device 105 may be transmitted to theinsurance platform 130 over thenetwork 150. Thenetwork 150 may include, for example, any one or more of a cellular network, a satellite network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a broadband network (BBN), the Internet, and the like. Further, thenetwork 150 can include, but is not limited to, any one or more of the following network topologies, including a bus network, a star network, a ring network, a mesh network, a star-bus network, tree or hierarchical network, and the like. - The
insurance platform 130 may be implemented on one or more computing machines (e.g., servers) in communication with thenetwork 150. Theinsurance platform 130 May be associated with a single entity (e.g., a company) or multiple entities that work together to provide insurance services to customers. Theinsurance platform 130 is configured to receive the driving data for a user from themobile device 105 and adjust one or more insurance products associated with the user based on the driving data. For example, theinsurance platform 130 may calculate a driving score based on the driving data for the user and adjust an existing insurance policy for the user, provide discounts or other products to the user based on the driving data, increase or decrease fees associated with an insurance product, or generate alerts to an owner of an insurance product. Advertisements or other content may also be provided to the owner of the insurance product based on the driving data for the user received from themobile device 105. -
FIG. 2 is a block diagram illustrating an examplemobile device 200 in accordance with various aspects of the subject technology. Examples of amobile device 200 may include a smartphone, a smart watch, or smart glasses. Themobile device 200 may include one ormore sensors 230, one ormore memories 240, one ormore processors 250, anetwork interface 260, adisplay 270, aspeaker 280, and/or a haptic-feedback interface 290. According to other aspects however, themobile device 200 may include additional components, fewer components, or alternative components. - The
sensors 230 may be configured to generate various sensor data that may be used to determine when a user is in a driving state (e.g., when the user is driving) and used to generate driving data about the user's driving behavior. For example, the data can indicate turning speed, braking speed, acceleration patterns, continued lane shifting, speed irregularity, sudden turns, drifting, and the like. Thesensors 230 may include, for example, agyroscope 205 configured to generate orientation data, anaccelerometer 210 configured to generate acceleration data, and/or a global positioning system (GPS)device 215 or other location sensing device configured to generate location data. - The
sensors 230 may also includeapplication sensors 220 or software sensors configured to detect and generate mobile device usage data, For example, theapplication sensors 220 may determine whether a user is using themobile device 200, what the user is doing with themobile device 200, and other information about the user's interaction with themobile device 200. The mobile device usage data may be indicative of whether the user is focused on driving or instead interacting with themobile device 200 while driving. - The information may include, for example, what application is currently open and running (e.g., a text messaging application, an email application, a web browser, etc.), what application is being displayed, whether the user is providing input to the mobile device 200 (e.g., keyboard input, scrolling, accessing buttons or other interface items, etc.), or how active applications are (e.g., whether a web browser is actively requesting and loading content). The information may further include whether the
mobile device 200 is receiving calls, an average number of calls per time period, whether the user picks up calls while driving, the average length of calls while driving, and any other information associated with the user's usage of themobile device 200. - The information may also include user information such as account logins for certain applications. According to some aspects, an application (e.g., the
application 115 inFIG. 1 ) configured to generate and transmit driving data for a user may associate the driving data with the user logged into the application. Thesensors 230 may also includeother sensors 225 not specifically shown inFIG. 2 . For example, the system may include a camera configured to capture images, video, or video feeds, a microphone configured to record sounds, or one or more biometric scanners (e.g., a fingerprint scanner) configured to identify specific users that may be driving. - According to some aspects, the
mobile device 200 may also include one ormore memories 240 configured to store data such as sensor data or driving data to be transmitted to theinsurance platform 130. Thememory 240 may also include a machine-readable medium (also referred to as a computer-readable medium) storing one or more sets of instructions, such as theapplication 115 inFIG. 1 , which may be executed by theprocessor 250 in order to perform the processes described herein. - The
network interface 260 is configured to transmit and receive data from theinsurance platform 130 or other devices over thenetwork 150. For example, thenetwork interface 260 may transmit driving data to theinsurance platform 130 and receive notifications, advertisements, or other content from theinsurance platform 130. Themobile device 200 may also include adisplay 270, aspeaker 280, and/or ahaptic feedback device 290 configured to provide information (e.g., visual content, audible content, or haptic feedback) to a user. Themobile device 200 may also include a power supply (not shown inFIG. 2 ) configured to provide themobile device 200 with power. The power supply may be configured to interface with an external power source such as a wall outlet, vehicle power outlet, or an external battery. -
FIG. 3 is a flow chart illustrating anexample process 300 for providing driving data for a user to an insurance platform in accordance with various aspects of the subject technology. Although the blocks inFIG. 3 are shown in a particular order, other orderings are also possible. For example, some blocks may be performed in different orders or in parallel with other blocks. - According to some aspects the subject technology, the process may be performed by a
mobile device 105 and, in particular, anapplication 115 running on themobile device 105. For example, a user of amobile device 105 may download and install theapplication 115 on themobile device 105. Once theapplication 115 is installed, the user may open theapplication 115 on themobile device 105. Theapplication 115 may authenticate the user so that the user may be associated with an account that is recognized by theinsurance platform 130. For example, authentication may occur based on the user providing a user name and password or through biometric input (e.g., scanning a fingerprint). - The
application 115 may run in the background on themobile device 105 and, atblock 305, receive sensor data from the sensors of themobile device 105 associated with the user. Atblock 310, theapplication 115 may determine whether the user is driving (e.g., whether the user is in a driving state). The application may determine whether the user is driving based on any number of different factors or combinations of factors. For example, in some embodiments the user provides a manual indication of a driving condition simply by pressing a button, activating a touch screen tab provided byapplication 115, or providing a voice input indicating the driving condition. - According to some aspects of the subject technology, the
application 115 may determine whether the user is driving by determining, based on the sensor data from the mobile device, a speed at which the user is traveling and comparing that speed with a threshold speed (e.g., 15 miles per hour). If the user's speed is over the threshold speed, theapplication 115 may determine that the user is driving. According to some aspects of the subject technology, theapplication 115 may determine whether the user is driving by determining, based on the sensor data from the mobile device, a distance that the user has traveled and comparing that distance with a threshold distance (e.g., 3 miles). If the user has traveled more than the threshold distance, theapplication 115 may determine that the user is driving. - According to other aspects of the subject technology, the
application 115 may determine whether the user is in the driving state by identifying, based on the sensor data from the mobile device, a route traveled by the user and determining whether that route is traveling a route associated with a particular transit type. For example, the particular transit type may be a bus route, a train route, a public transportation route, a biking route, a boat route, a waterway, or an aerial route. Theapplication 115 may determine that the user is driving if the route traveled by the user is associated with the particular transit type. in some embodiments, at least one ofapplication 115 andinsurance platform 130 discard driving data when the user is in a bus route, a train route, a public transportation route, a boat route, a waterway or an aerial route. - In other implementations, the
application 115 may determine whether the user is driving by prompting the user to provide an indication that the user is driving or not driving. The indication may include the user selecting a button on the display. According to other aspects, the indication may include the user linking themobile device 105 to the vehicle (e.g., a Bluetooth link). In some embodiments, the user indicates a driving condition via a voice control feature included inapplication 115. In still other aspects, theapplication 115 may determine whether the user is driving by identifying wireless signals detected by themobile device 105. The wireless signals may include, for example, Bluetooth signals or Wi-Fi signals. For example, if themobile device 105 detects a Wi-Fi network that is known to be a public transportation network, then the user may be on a form of public transportation and not driving. If themobile device 105 detects 8 or more Bluetooth signals for a period of time (e.g., 2 minutes), then themobile device 105 may be on a form of public transportation with other people using Bluetooth enabled devices. Accordingly, the user is deemed to not be driving. - Further, some embodiments include detailed data processing to indicate that the user of
mobile device 105 is a driver and not a passenger of the vehicle. For example, the data processing may include determining that the user is not manipulatingmobile device 105 while driving data is collected. Other indicators of the user being actually at the wheel may include detecting thatmobile device 105 is approximately in a fixed orientation relative to the vehicle orientation, or based on a connection (e.g., via Bluetooth) between themobile device 105 and an onboard computer of the vehicle (e.g., indicating, for example, that the user is the driver because the user's smartphone is connected to the vehicle's telephone functionality). - According to other aspects of the subject technology, rules that combine multiple factors may be used in determining whether the user is driving. For illustrative purposes, one example rule may state that a user is driving if the user has traveled over 40 miles per hour for one minute and/or 5 consecutive miles. Another example rule may state that a user is driving if the average speed for a user for the last hour is over 10 miles per hour.
- Returning to
FIG. 3 , if the user is not driving, the application may continue to receive the sensor data atblock 305. If, on the other hand, the user is driving, atblock 315, theapplication 115 may generate driving data for the user based on the sensor data. Driving data may include, for example, various speed measurements for the user, whether there are sudden braking actions, and/or sudden accelerations. The driving data may also include speed for certain situations such as entering school zones, on turns, and/or on on-ramps and off-ramps. The driving data may further include locations (e.g., general areas, cities, counties, etc.) in which the user typically drives, the amount of time the user drives in particular locations, and/or the when the user typically drives. The user's speed measurements can then be compared to known speed limits for the locations. The driving data may further include sensor data from the sensors on themobile device 105 such as, for example, mobile device usage data. - At block 320, the application may transmit the driving data for the user to an
insurance platform 130 where it may be used by theinsurance platform 130 to assess one or more insurance products associated with the user or provide content to the user based on the driving data. According to some aspects of the subject technology, the insurance platform may calculate a driving score for the user based on the user's driving data and adjust an existing insurance policy for the user, provide discounts or other products to the user based on the driving data, or increase or decrease fees associated with an insurance product. - The
insurance platform 130 may also generate communications. (e.g., alerts, messages, or notifications) for a user based on the user's driving data and transmit the alerts or notifications to the user. For example, the insurance platform may email the user at an email address provided by the user or transmit communications to the mobile device 105 (e.g., a text message) and/or the application 115 (e.g., an application message or alert). The communications may include, for example, an assessment of recent driving activity of the user, notifications for safe or risky driving, tips on how to improve driving behavior, and/or information about how driving behavior (the user's or in general) may affect adjustments to insurance products. - According to some aspects of the subject technology, the
application 115 on themobile device 105 may be configured to analyze the generated driving data and determine driving behaviors of the user. Theapplication 115 may also provide one or more real-time notifications about the driving behaviors to the user via the mobile device while the user is driving. For example, if theapplication 115 determines that a hard acceleration event was detected, theapplication 115 may send a notification to the user. The notification may include an audible sound or haptic feedback (e.g., two quick vibrations or buzzes) that may inform the user that a hard acceleration event was detected without the user having to take the user's eyes off the road. However, in other aspects, visual notifications may also be used. Notifications may also be generated for hard braking events, speeding, using the mobile device while driving, or any other driving behavior for the user. - According to other aspects of the subject technology, a driving score may be calculated and provided to the user along with driving details or characteristics about how the user was driving during a recent driving event. Tips on how to improve the score may also be delivered to the user. The information provided to the user may be provided in real-time as the information is calculated while the user is driving or after a driving event. Furthermore, the information may also be delivered to the user via an email. The feedback provided to the user may help the user modify the user's driving behavior (e.g., to help the user drive more safely) and, as a result, help the user adjust an insurance product associated with the user.
-
FIG. 4 is a block diagram illustrating anexample computer system 400 with which any of the computing machines, devices, or systems discussed herein may be implemented, in accordance with some aspects of the subject technology. In certain aspects, thecomputer system 400 may be implemented using hardware or a combination of software and hardware, either in a dedicated server, or integrated into another entity, or distributed across multiple entities. - The
example computer system 400 includes aprocessor 402, amain memory 404, astatic memory 406, adisk drive unit 416, and anetwork interface device 420 which communicate with each other via abus 408. Thecomputer system 400 may further include an input/output interface 412 that may be configured to communicate- with various input/output devices such as video display units (e.g., liquid crystal (LCD) displays, cathode ray tubes (CRTs), or touch screens), an alphanumeric input device (e.g., a keyboard), a cursor control device (e.g., a mouse), or a signal generation device (e.g., a speaker). -
Processor 402 may be a general-purpose microprocessor (e.g., a central processing unit (CPU)), a graphics processing unit (GPU), a microcontroller, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Programmable Logic Device (PLD), a controller, a state machine, gated logic, discrete hardware components, or any other suitable entity that can perform calculations or other manipulations of information. - A machine-readable medium (also referred to as a computer-readable medium) may store one or more sets of
instructions 424 embodying any one or more of the methodologies or functions described herein. Theinstructions 424 may also reside, completely or at least partially, within themain memory 404 and/or within theprocessor 402 during execution thereof by thecomputer system 400, with themain memory 404 and theprocessor 402 also constituting machine-readable media. Theinstructions 424 may further be transmitted or received over anetwork 426 via thenetwork interface device 420. - The machine-readable medium may be a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The machine-readable medium may include the
drive unit 416, thestatic memory 406, themain memory 404, theprocessor 402, an external memory connected to the input/output interface 412, or some other memory. The term “machine-readable medium” shall also be taken to include any non-transitory medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the embodiments discussed herein. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, storage mediums such as solid-state memories, optical media, and magnetic media. - The various illustrative blocks, modules, elements, components, methods; and algorithms described herein may be implemented as electronic hardware, computer software, or combinations of both. To illustrate this interchangeability of hardware and software, various illustrative blocks, modules, elements, components, methods, and algorithms have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application. Various components and blocks may be arranged differently (e.g., arranged in a different order, or partitioned in a different way) all without departing from the scope of the subject technology.
- It is understood that the specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged. Some of the steps may be performed simultaneously.
- The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. The previous description provides various examples of the subject technology, and the subject technology ‘is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects.
- A phrase such as an “aspect” does not imply that such aspect is essential to the subject technology or that such aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. A phrase such as an aspect may refer to one or more aspects and vice versa. A phrase such as an “embodiment” does not imply that such embodiment is essential to the subject technology or that such embodiment applies to all configurations of the subject technology. A disclosure relating to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. A phrase such an embodiment may refer to one or more embodiments and vice versa. A phrase such as a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. A phrase such a configuration may refer to one or more configurations and vice versa.
- Furthermore, to the extent that the term “include,” “have,” or the like is used in the description or the claims, such term is intended to be inclusive in a manner similar to the term “comprise” as “comprise” is interpreted when employed as a transitional word in a claim.
Claims (1)
1. A method comprising:
receiving sensor data from a mobile device associated with a user;
determining, based on the sensor data, whether the user is in a driving state;
generating, when the user is in the driving state, driving data for the user; and
transmitting, via a network, the driving data for the user to an insurance platform for rate assessment by the insurance platform.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/840,046 US20230134558A1 (en) | 2014-05-12 | 2022-06-14 | Transmitting driving data to an insurance platform |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/275,821 US11361379B1 (en) | 2014-05-12 | 2014-05-12 | Transmitting driving data to an insurance platform |
US17/840,046 US20230134558A1 (en) | 2014-05-12 | 2022-06-14 | Transmitting driving data to an insurance platform |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/275,821 Continuation US11361379B1 (en) | 2014-05-12 | 2014-05-12 | Transmitting driving data to an insurance platform |
Publications (1)
Publication Number | Publication Date |
---|---|
US20230134558A1 true US20230134558A1 (en) | 2023-05-04 |
Family
ID=81944034
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/275,821 Active 2036-01-04 US11361379B1 (en) | 2014-05-12 | 2014-05-12 | Transmitting driving data to an insurance platform |
US17/840,046 Pending US20230134558A1 (en) | 2014-05-12 | 2022-06-14 | Transmitting driving data to an insurance platform |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/275,821 Active 2036-01-04 US11361379B1 (en) | 2014-05-12 | 2014-05-12 | Transmitting driving data to an insurance platform |
Country Status (1)
Country | Link |
---|---|
US (2) | US11361379B1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11820386B1 (en) * | 2020-04-28 | 2023-11-21 | United Services Automobile Association (Usaa) | Distracted driving detection and mitigation |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220116743A1 (en) * | 2020-10-14 | 2022-04-14 | Lyft, Inc. | Detecting handheld device movements utilizing a handheld-movement-detection model |
JP2022098912A (en) * | 2020-12-22 | 2022-07-04 | 日本電気株式会社 | Passage information providing device, passage information providing method and computer program |
US11769211B2 (en) * | 2021-03-22 | 2023-09-26 | Toyota Jidosha Kabushiki Kaisha | Vehicle insurance system, vehicle dealer terminal, and vehicle sales method |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110213628A1 (en) * | 2009-12-31 | 2011-09-01 | Peak David F | Systems and methods for providing a safety score associated with a user location |
US20120209632A1 (en) * | 2011-01-24 | 2012-08-16 | Lexisnexis Risk Solutions Inc. | Telematics smart pinging systems and methods |
US20150039348A1 (en) * | 2013-08-05 | 2015-02-05 | Ford Global Technologies, Llc | Vehicle operations monitoring |
Family Cites Families (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8090598B2 (en) | 1996-01-29 | 2012-01-03 | Progressive Casualty Insurance Company | Monitoring system for determining and communicating a cost of insurance |
US5797134A (en) | 1996-01-29 | 1998-08-18 | Progressive Casualty Insurance Company | Motor vehicle monitoring system for determining a cost of insurance |
US8140358B1 (en) | 1996-01-29 | 2012-03-20 | Progressive Casualty Insurance Company | Vehicle monitoring system |
JP2001076012A (en) | 1999-08-31 | 2001-03-23 | Hitachi Ltd | Method and device for gathering vehicle information |
US7339483B1 (en) | 2000-08-11 | 2008-03-04 | Telanon, Inc. | Automated consumer to business electronic marketplace system |
JP2004522237A (en) | 2001-08-10 | 2004-07-22 | テルシン・カンパニー・リミテッド | Vehicle data collection and vehicle diagnosis system and method using smart card, and automatic setting method of vehicle convenience device |
KR20040017465A (en) | 2002-08-21 | 2004-02-27 | 주식회사 텔사인 | Method and system of calculating a car insurance value using a smartcard |
US6931309B2 (en) | 2003-05-06 | 2005-08-16 | Innosurance, Inc. | Motor vehicle operating data collection and analysis |
US20040260579A1 (en) | 2003-06-19 | 2004-12-23 | Tremiti Kimberly Irene | Technique for providing automobile insurance |
US9311676B2 (en) | 2003-09-04 | 2016-04-12 | Hartford Fire Insurance Company | Systems and methods for analyzing sensor data |
US7542915B2 (en) | 2003-09-30 | 2009-06-02 | The Boeing Company | System of charging for automobile insurance |
US8606603B2 (en) * | 2003-12-05 | 2013-12-10 | Scorelogix Llc | Unemployment risk score and private insurance for employees |
US20050174217A1 (en) | 2004-01-29 | 2005-08-11 | Basir Otman A. | Recording and reporting of driving characteristics |
EP1607892A1 (en) | 2004-06-18 | 2005-12-21 | John Hannon | A method and system adapted to enable an electronic payment of mobile device insurance. |
US20060053038A1 (en) | 2004-09-08 | 2006-03-09 | Warren Gregory S | Calculation of driver score based on vehicle operation |
US20070299700A1 (en) | 2004-10-29 | 2007-12-27 | Milemeter, Inc. | System and Method for Assessing Earned Premium for Distance-Based Vehicle Insurance |
US7991629B2 (en) | 2004-10-29 | 2011-08-02 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7865378B2 (en) | 2004-10-29 | 2011-01-04 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7890355B2 (en) | 2004-10-29 | 2011-02-15 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US7987103B2 (en) | 2004-10-29 | 2011-07-26 | Milemeter, Inc. | System and method for the assessment, pricing, and provisioning of distance-based vehicle insurance |
US20070033076A1 (en) | 2005-04-07 | 2007-02-08 | Sadeghi Darius A | Vehicle value insurance system and method |
US20090002147A1 (en) * | 2006-08-30 | 2009-01-01 | Sony Ericsson Mobile Communications Ab | Method for safe operation of mobile phone in a car environment |
US20080312969A1 (en) | 2007-04-20 | 2008-12-18 | Richard Raines | System and method for insurance underwriting and rating |
US8027853B1 (en) | 2008-10-23 | 2011-09-27 | United States Automobile Associates (USAA) | Systems and methods for self-service vehicle risk adjustment |
US20100131300A1 (en) | 2008-11-26 | 2010-05-27 | Fred Collopy | Visible insurance |
US20120046974A1 (en) * | 2010-08-23 | 2012-02-23 | Bank Of America Corporation | Unemployment Insurance Underwriting System |
US9311271B2 (en) * | 2010-12-15 | 2016-04-12 | Andrew William Wright | Method and system for logging vehicle behavior |
CA2823152C (en) * | 2010-12-26 | 2019-08-06 | The Travelers Indemnity Company | Systems and methods for utilization of risk zones |
US9164957B2 (en) * | 2011-01-24 | 2015-10-20 | Lexisnexis Risk Solutions Inc. | Systems and methods for telematics monitoring and communications |
US8666786B1 (en) | 2011-01-24 | 2014-03-04 | Derek Wirz | Automated system to update insurance carrier with exposure data in real-time |
US20130006674A1 (en) | 2011-06-29 | 2013-01-03 | State Farm Insurance | Systems and Methods Using a Mobile Device to Collect Data for Insurance Premiums |
US10977601B2 (en) | 2011-06-29 | 2021-04-13 | State Farm Mutual Automobile Insurance Company | Systems and methods for controlling the collection of vehicle use data using a mobile device |
JP2015513830A (en) * | 2012-02-17 | 2015-05-14 | インタートラスト テクノロジーズ コーポレイション | System and method for vehicle policy enforcement |
US20140108058A1 (en) | 2012-10-11 | 2014-04-17 | Agero, Inc. | Method and System to Determine Auto Insurance Risk |
US20140149145A1 (en) * | 2012-11-29 | 2014-05-29 | State Farm Insurance | System and Method for Auto-Calibration and Auto-Correction of Primary and Secondary Motion for Telematics Applications via Wireless Mobile Devices |
US9253603B1 (en) * | 2013-03-05 | 2016-02-02 | Trend Micro Incorporated | Accelerometer-based calibration of vehicle and smartphone coordinate systems |
US8666789B1 (en) | 2013-08-02 | 2014-03-04 | State Farm Mutual Automobile Insurance Company | Bluetooth device to enable data collection for insurance rating purposes |
-
2014
- 2014-05-12 US US14/275,821 patent/US11361379B1/en active Active
-
2022
- 2022-06-14 US US17/840,046 patent/US20230134558A1/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110213628A1 (en) * | 2009-12-31 | 2011-09-01 | Peak David F | Systems and methods for providing a safety score associated with a user location |
US20120209632A1 (en) * | 2011-01-24 | 2012-08-16 | Lexisnexis Risk Solutions Inc. | Telematics smart pinging systems and methods |
US20150039348A1 (en) * | 2013-08-05 | 2015-02-05 | Ford Global Technologies, Llc | Vehicle operations monitoring |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11820386B1 (en) * | 2020-04-28 | 2023-11-21 | United Services Automobile Association (Usaa) | Distracted driving detection and mitigation |
Also Published As
Publication number | Publication date |
---|---|
US11361379B1 (en) | 2022-06-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230134558A1 (en) | Transmitting driving data to an insurance platform | |
US12008841B2 (en) | Vehicle telematics and account management | |
US10911909B1 (en) | Text message control system | |
US11798089B1 (en) | Vehicle telematics and account management | |
EP3561780A1 (en) | Driving behavior determination method, device, equipment and storage medium | |
US9477639B2 (en) | Safe driving monitoring system | |
US10127737B1 (en) | Communication system and method for using human telematic data to provide a hazard alarm/notification message to a user in a dynamic environment such as during operation of a vehicle | |
US8907772B1 (en) | System and method for automatic unsafe driving determination and notification | |
US8947263B2 (en) | Assessing traffic status with sensors | |
US9619945B2 (en) | Recommending an alternative route to a service location to service a vehicle issue that was detected by a change in status in a sensor of the automobile's diagnostic system | |
US20150181414A1 (en) | Discouraging text messaging while driving | |
US10885724B1 (en) | Communication system and method for using human telematic data to provide a hazard alarm/notification message to a user in a dynamic environment such as during operation of a vehicle | |
US11669756B2 (en) | Partitioning sensor based data to generate driving pattern map | |
US20170019503A1 (en) | Method and apparatus for seamless application portability over multiple environments | |
US20200094851A1 (en) | Realtime driver assistance system | |
US10511936B1 (en) | Mobile device notification generation | |
US20170328732A1 (en) | Navigation system with notification mechanism and method of operation thereof | |
EP3125169A1 (en) | Computing system with geofence mechanism and method of operation thereof | |
US12008842B2 (en) | Systems and methods for detecting full-stops to reduce vehicle accidents | |
US20230316411A1 (en) | Deductible Determination System | |
US20220207477A1 (en) | Methods and systems for detecting delivery trip events and improving delivery driver safety | |
CN111695956A (en) | Intelligent service management method and system for automobile leasing platform and electronic equipment | |
US20220383256A1 (en) | Post-vehicular incident reconstruction report | |
US11348181B1 (en) | Method and system for assessing driving risks by detecting driving routines | |
JP2020091699A (en) | Information processor and program |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
AS | Assignment |
Owner name: ESURANCE INSURANCE SERVICES, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RODONI, PHILIP;REEL/FRAME:064339/0286 Effective date: 20140509 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |