IP Library › Granted Patent US 12,735,048
Granted Patent B2
US 12,735,048 · App. 18/783,185 · Granted Sep 15, 2026

Systems and methods for tracking historic driver data on the edge

Inventors: Sivashankar Yoganathan (Moorpark, CA); Patrick Heffernan (Moorpark, CA); Pranam Kalla (Simi Valley, CA); James Makishima (Palos Verdes, CA); Kenji Fujii (Torrance, CA); Craig Lozofsky (Torrance, CA); Erika Shimojo (Torrance, CA); Taku Yamane (Torrance, CA)
Assignee: MOTER TECHNOLOGIES, INC.
B60W40/09G06Q40/08G06V20/59G06V20/597G06V40/172H04L9/0643H04L67/12H04W4/40B60W2520/10B60W2556/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,735,048
App. No.
18/783,185
Granted
Sep 15, 2026
Kind
B2
Abstract

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.

Claims (42)

1 . 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 a communication from a telematic unit, the communication including a first request for a first symmetrical key, a first hashed encrypted historic data generated by the telematic unit by hashing a first encrypted historic data received from a user device, and a user device identification corresponding to a user device;

retrieving a second encrypted historic data and the first symmetrical key corresponding to the user device identification from a database;

hashing the second encrypted historic data and generating a second hashed encrypted data;

comparing the first hashed encrypted historic data received from the telematic unit to the second hashed encrypted historic data;

generating a second symmetrical key; and

storing the second symmetrical key in the database; and

transmitting the first and second symmetrical keys to the telematic unit when the first hashed encrypted data matches the second hashed encrypted historic data.

2 . The one or more non-transitory computer-readable media of claim 1 , wherein the telematic unit hashed the first encrypted historic data from the user device prior to transmission to the server.

3 . The one or more non-transitory computer-readable media of claim 1 , further comprising transmitting the first and second symmetrical keys to the telematic unit when the first hashed encrypted historic data matches the second hashed encrypted historic data.

4 . The one or more non-transitory computer-readable media of claim 1 , further comprising transmitting the first and second symmetrical keys, and the second encrypted historic data to the telematic unit when the first hashed encrypted historic data and the second hashed encrypted historic data do not match.

5 . The one or more non-transitory computer-readable media of claim 1 , further comprising:

receiving a second request from the telematic unit for the first and second symmetrical keys and historic data when the user device does not contain user device historic data;

transmitting the historic data and the first and second symmetrical keys to the telematic unit when the server contains the historic data; and

transmitting a no historic data message to the telematic unit when the server does not contain the historic data.

6 . The one or more non-transitory computer-readable media of claim 1 , further comprising:

receiving, from the telematic unit, encrypted trip data for a new user device, a new user identification, a new user device identification, a telematic unit identification, and a timestamp.

7 . One or more non-transitory computer readable media storing computer-executable instructions that upon execution cause one or more processors on a telematic unit to perform acts comprising:

transmitting a first request to a user device, the first request for a first encrypted historic data and a user device identification;

receiving the first encrypted historic data from the user device;

hashing the first encrypted historic data and generating a first hashed encrypted historic data;

transmitting a second request to a server, the second request including the first hashed encrypted historic data, a request for a first symmetrical key, and the user device identification;

receiving a first symmetrical key and the second symmetrical key from the server when the first hashed encrypted historic data matches a second hashed encrypted historic data stored on the server wherein the server generates the second hashed encrypted historic data by hashing a second encrypted historic data retrieved from a database corresponding to the user device identification, and the server transmits the first and second symmetrical keys upon determining that the first hashed encrypted historic data matches the second hashed encrypted historic data.

8 . The one or more non-transitory computer-readable media of claim 7 , further comprising:

receiving a second encrypted historic data from the server when the first hashed encrypted data does not match the second hashed encrypted historic data;

decrypting the second encrypted historic data using the second symmetrical key; and

storing the second encrypted historic data in a memory device on the telematic unit.

9 . The one or more non-transitory computer-readable media of claim 7 , further comprising transmitting a third request to the server, the third request for a third encrypted historic data and the first and second symmetrical keys when the user device does not contain any encrypted historic data.

10 . The one or more non-transitory computer-readable media of claim 9 , further comprising:

receiving a second encrypted historic data from the server when the first hashed encrypted data does not match the second hashed encrypted historic data;

decrypting the second encrypted historic data using the second symmetrical key; and

storing the second encrypted historic data in a memory device on the telematic unit.

11 . The one or more non-transitory computer-readable media of claim 7 , further comprising:

receiving a no historic data message from the server upon a determination that the server does not contain the first encrypted historic data; and

creating a record on the telematic unit for the user device.

12 . The one or more non-transitory computer-readable media of claim 7 , further comprising:

determining an end to a trip in a vehicle, the trip generating a trip historic data;

updating the first encrypted historic data from the user device with the trip historic data;

encrypting the first updated encrypted historic data; and

transmitting the first updated encrypted updated historic data to the user device.

13 . The one or more non-transitory computer-readable media of claim 12 , further comprising:

sending the first updated encrypted historic data to the server along with the user identification, a user device identification, a telematic unit identifier, and a timestamp.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 26, 2024
From: YOGANATHAN, SIVASHANKAR; HEFFERNAN, PATRICK; KALLA, PRANAM; MAKISHIMA, JAMES; FUJII, KENJI; LOZOFSKY, CRAIG; SHIMOJO, ERIKA; YAMANE, TAKU
To: MOTER TECHNOLOGIES, INC.
Reel/Frame 068099/0509 →
Continuity (2)
Provisional Application 63515272 · Jul 24, 2023
Related Publication 20250033648A1 · Jan 30, 2025
References Cited (29)
US 8140358B1 · Ling et al. · 2012 [cited by applicant]
US 9180887B2 · Nemat-Nasser et al. · 2015 [cited by applicant]
US 9221428B2 · Kote et al. · 2015 [cited by applicant]
US 10127810B2 · Durie, Jr. et al. · 2018 [cited by applicant]
US 11273838B2 · Du et al. · 2022 [cited by applicant]
US 11299127B2 · Tucker et al. · 2022 [cited by applicant]
US 11321970B2 · Wright · 2022 [cited by applicant]
US 11578990B1 · Chintakindi et al. · 2023 [cited by applicant]
US 11580756B2 · Gleeson-May et al. · 2023 [cited by applicant]
US 20120101855A1 · Collins et al. · 2012 [cited by applicant]
US 20150133108A1 · Ahmed · 2015 [cited by examiner]
US 20160105539A1 · Maddox et al. · 2016 [cited by applicant]
US 20160360557A1 · Lavi · 2016 [cited by applicant]
US 20180091596A1 · Alvarez · 2018 [cited by examiner]
US 20190080540A1 · Sim · 2019 [cited by examiner]
US 20190109834A1 · Lyons · 2019 [cited by examiner]
US 20200050774A1 · Unagami · 2020 [cited by examiner]
US 20210064778A1 · Vladimerou · 2021 [cited by examiner]
US 20220032920A1 · Varughese et al. · 2022 [cited by applicant]
US 20220048432A1 · Switalski et al. · 2022 [cited by applicant]
US 20220237277A1 · Rahman et al. · 2022 [cited by applicant]
US 20220412759A1 · Neubecker · 2022 [cited by applicant]
CN 111091474A · 2020 [cited by applicant]
CN 112776738A · 2021 [cited by applicant]
CN 113705333A · 2021 [cited by applicant]
KR 20200141402A1 · 2020 [cited by applicant]
Related PCT Application No. PCT/US2024/039379. International Search Report & Written Opinion (Oct. 29, 2024). [cited by applicant]
Corresponding PCT Application No. PCT/US2024/039393. International Search Report & Written Opinion (Oct. 31, 2024). [cited by applicant]
Lundbaek. The Porsche-XAIN Vehicle Blockchain Network: A Technical Overview (Mar. 23, 2018). [cited by applicant]