SYSTEMS AND METHODS FOR TRACKING HISTORIC DRIVER DATA ON THE EDGE
Driver insurance and risk management scores are calculated per driver based on vehicle and driver behavior data collected during driving sessions. Often one vehicle is shared by multiple drivers and one driver can drive multiple vehicles. The present disclosure securely tracks the individual drivers, stores, and retrieves associated driver data for analysis on the edge (vehicle) in near real time. Data collected is analyzed at various time intervals (each trip, daily, monthly) to produce the scores. The goal of the proposed solution minimizes cost associated with data transmission and cloud storage, tracks long term driver driving history on the edge for near real time analysis of driver behavior, minimizes driver distraction due to user device while driving, securely stores and retrieves driver driving data on the edge device associated with the driver, restricts access to the driver driving data, and restricts user device access to servers and telematic units.
1 . One or more non-transitory computer readable media storing computer-executable instructions that upon execution cause one or more processors on a user device to perform acts comprising:
securing the user device to a docking station on a telematic unit for communicating with a server;
transmitting, via the one or more processors, user device identifier data to the server for validating the user device;
receiving, via the one or more processors, a user device authentication identification from the server upon successful validation of the user device identification data by the server;
waking, via the one or more processors, the telematic unit; and
transmitting, via the one or more processors, the user device identification data to the telematic unit.
2 . The one or more non-transitory computer-readable media of claim 1 , wherein the user identification data sent to the server includes a user identification, a user device identification, a password, a user device location, and a timestamp.
3 . The one or more non-transitory computer-readable media of claim 1 , further comprising:
receiving a login failure status message from the server upon successful validation of the user device identification data by the server; and
displaying an error message on a display screen of the user device.
4 . One or more non-transitory computer readable media storing computer-executable instructions that upon execution cause one or more processors on a server to perform acts comprising:
receiving user device identification data from the user device for validating the user device;
generating a user device authentication identification for the user device upon successful validation of the user device;
storing the authentication identification on a database on the server;
transmitting the user device authentication identification to the user device;
receiving a ready message from the telematic unit;
generating a random telematic unit docking station key;
storing the random telematic unit docking station key and the ready message on the database on the server; and
transmitting the random telematic unit docking station key to the telematic unit.
5 . The one or more non-transitory computer-readable media of claim 4 , wherein the ready message includes a telematic unit identification, a GPS location of the user device, and a timestamp.
6 . The one or more non-transitory computer-readable media of claim 4 , further comprising transmitting a login failure status message to the user device upon unsuccessful validation of the user device.
7 . A method for establishing a 3-way system identification between a server, a telematics unit (TU), and a user device, comprising:
generating, by at least one processor of the telematic unit, a random pair key;
requesting, by the at least one processor of the telematic unit, user device information from the user device;
transmitting, by at least one processor of the user device, user device information to the telematic unit via short range communication;
transmitting, by the at least one processor of the telematic unit, the user device information to the server;
retrieving, by at least one processor of the server, a login status associated with the user device from a database on the server;
requesting, by the at least one processor of the telematic unit, a pairing request from the server upon successful login by the user device;
requesting, by the at least one processor of the server, a device pairing with the user device causing the user device to request pairing information from the telematic unit;
transmitting, by the at least one processor of the telematic unit, the pairing information to the user device, the pairing information includes a copy of the random pair key; and
transmitting, by the at least one processor of the user device, the pairing information to the server for validating the device pairing with the user device from telematic unit, the pairing information includes the copy of the random pair key.
8 . The method of claim 7 , wherein the copy of the random pair key is transmitted to the user device via short range communication.
9 . The method of claim 7 , wherein the copy of the random pair key is transmitted to the server via a cloud communication.
10 . The method of claim 9 , wherein the user device information is requested from the user device via short range communication.
11 . The method of claim 7 , wherein the pairing request includes a user identification, a user device identification, a telematic unit identification, the copy of the random pair key, a user device location, and a timestamp.
12 . The method of claim 11 , further comprising:
comparing, by the server, the copy of the random pair key received from the user device to the random pair key sent by the telematic unit.
13 . The method of claim 12 , wherein the random pair key and the copy of the random pair key are transmitted to the server asynchronously.
14 . The method of claim 7 , further comprising:
transmitting, by the at least one processor of the server, device pair success to the telematic unit; and
transmitting, by the at least one processor of the telematic unit, the device pair success to the user device.
15 . The method of claim 7 , wherein the pairing information includes a user identification, a user device identification, a pair timestamp, the copy of the random pair key, and a docking station key.
16 . A method for establishing a 3-way system identification between a server, a telematics unit (TU), and a user device, comprising:
generating, by at least one processor of the server, a random pair key;
requesting, by the at least one processor of the server, user device information from the user device;
transmitting, by at least one processor of the user device, user device information to the server;
retrieving, by at least one processor of the server, a login status associated with the user device from a database on the server;
transmitting, by the at least one processor of the server, a login status to the user device;
transmitting, by the at least one processor of the user device, the login status to the telematic unit;
requesting, by the at least one processor of the telematic unit, a pairing request from the server upon successful login by the user device;
transmitting, by the at least one processor of the telematic unit, a device pairing request with the server;
transmitting, by the at least one processor of the server, a copy of the random pair key to the telematic unit;
transmitting, by the at least one processor of the server, the device pairing request and the copy of the random pair key;
transmitting, by the at least one processor of the user device, a request for pairing information to the telematic unit;
transmitting, by the at least one processor of the telematic unit, a docking station key and a pair timestamp; and
transmitting, by the at least one processor of the user device, a pairing response to the server, the pairing response including a copy of the random pair key.
17 . The method of claim 16 , wherein the pairing request includes a user identification, a user device identification, a telematic unit identification, the copy of the random pair key, a user device location, and a timestamp.
18 . The method of claim 16 , further comprising:
comparing, by the server, the copy of the random pair key received from the user device to the random pair key generated by the server.
19 . The method of claim 16 , further comprising:
transmitting, by the at least one processor of the server, a device pairing success message to the telematic unit; and
transmitting, by the at least one processor of the telematic unit, the device pairing success message to the user device.
20 . The method of claim 16 , wherein the pairing information includes a user identification, the user device identification, a pair timestamp, the copy of the random pair key, and the docking station key.