IP Library Granted Patent US 12,374,225
Granted Patent B1
US 12,374,225 · App. 18/330,533 · Granted Jul 29, 2025

Customized route tracking

Inventors: Sachal Nanda (Alamo, CA); Greg Hogan (Mountain View, CA); Jennifer Julia Zhang (San Francisco, CA); Kathryn Siegel (San Francisco, CA); Kelsey Lam (Fremont, CA); Sean McGee (San Francisco, CA); Alex Wu (San Francisco, CA); Tirso Peguero (San Francisco, CA); Emily White (San Francisco, CA); Eric Shreve (Calistoga, CA); Wei Wu (San Francisco, CA); Chaein Jung (Seoul, KR); Helen Chung (Great Falls, VA); Sachie Weber (San Francisco, CA); Yosub Shin (Seoul, KR); Utkarsh Jaiswal (San Francisco, CA)
Assignee: Samsara Inc.
G08G1/20G01C21/3626G01C21/3691G08G1/123
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,374,225
App. No.
18/330,533
Granted
Jul 29, 2025
Kind
B1
Abstract

Disclosed are systems, methods, and non-transitory computer-readable media for automated fleet tracking. A route management system enables fleet managers to define and assign routes for vehicles in a fleet, as well as set route tracking configurations for customized tracking of the vehicles. For example, the route tracking configuration may include customizations to the scheduled start and/or end time of a route, a threshold for determining that a vehicle has arrived and/or departed from a scheduled stop, and the like.

Claims (64)

1. A method comprising:

receiving an input that defines a route variable;

associating the route variable with a fleet attribute within a database;

receiving, from a sensor device associated with a vehicle from among a fleet of vehicles, sensor data that describes an operation of the vehicle, the fleet of vehicles corresponding with the fleet attribute;

generating a route tracking window based on a scheduled start time associated with the route variable, and a scheduled end time associated with the route variable; and

generating a report based on the route variable associated with the fleet attribute and the sensor data received within the route tracking window.

2. The method of claim 1 , wherein the route variable includes one or more of:

a start location;

a destination location;

a scheduled departure time; and

a scheduled arrival time.

3. The method of claim 1 , further comprising:

causing display of a notification that includes the report at a client device associated with the fleet of vehicles.

4. The method of claim 1 , wherein the route variable comprises a threshold, and the generating the report includes:

determining the sensor data transgresses the threshold that corresponds with the route variable; and

generating the report responsive to the determining that the sensor data transgresses the threshold that corresponds with the route variable.

5. The method of claim 1 , wherein the sensor data comprises location data that indicates a location of the vehicle.

6. The method of claim 1 , wherein the route variable comprising an identification of a location, the sensor data comprises location data, and wherein the generating the report includes:

determining the location data identifies the location identified by the route variable; and

generating the report responsive to the determining the location data identifies the location identified by the route variable.

7. The method of claim 1 , wherein the fleet attribute includes a vehicle type.

8. A system comprising:

one or more computer processors; and

one or more computer-readable mediums storing instructions that, when executed by the one or more computer processors, cause the system to perform operations comprising:

receiving an input that defines a route variable;

associating the route variable with a fleet attribute within a database;

receiving, from a sensor device associated with a vehicle from among a fleet of vehicles, sensor data that describes an operation of the vehicle, the fleet of vehicles corresponding with the fleet attribute;

generating a route tracking window based on a scheduled start time associated with the route variable, and a scheduled end time associated with the route variable; and

generating a report based on the route variable associated with the fleet attribute and the sensor data received within the route tracking window.

9. The system of claim 8 , wherein the route variable includes one or more of:

a start location;

a destination location;

a scheduled departure time; and

a scheduled arrival time.

10. The system of claim 8 , further comprising:

causing display of a notification that includes the report at a client device associated with the fleet of vehicles.

11. The system of claim 8 , wherein the route variable comprises a threshold, and the generating the report includes:

determining the sensor data transgresses the threshold that corresponds with the route variable; and

generating the report responsive to the determining that the sensor data transgresses the threshold that corresponds with the route variable.

12. The system of claim 8 , wherein the sensor data comprises location data that indicates a location of the vehicle.

13. The system of claim 8 , wherein the route variable comprising an identification of a location, the sensor data comprises location data, and wherein the generating the report includes:

determining the location data identifies the location identified by the route variable; and

generating the report responsive to the determining the location data identifies the location identified by the route variable.

14. The system of claim 8 , wherein the fleet attribute includes a vehicle type.

15. A non-transitory computer-readable medium storing instructions that, when executed by one or more computer processors of one or more computing devices, cause the one or more computing devices to perform operations comprising:

receiving an input that defines a route variable;

associating the route variable with a fleet attribute within a database;

receiving, from a sensor device associated with a vehicle from among a fleet of vehicles, sensor data that describes an operation of the vehicle, the fleet of vehicles corresponding with the fleet attribute;

generating a route tracking window based on a scheduled start time associated with the route variable, and a scheduled end time associated with the route variable; and

generating a report based on the route variable associated with the fleet attribute and the sensor data received within the route tracking window.

16. The non-transitory computer-readable medium of claim 15 , wherein the route variable includes one or more of:

a start location;

a destination location;

a scheduled departure time; and

a scheduled arrival time.

17. The non-transitory computer-readable medium of claim 15 , further comprising:

causing display of a notification that includes the report at a client device associated with the fleet of vehicles.

18. The non-transitory computer-readable medium of claim 15 , wherein the route variable comprises a threshold, and the generating the report includes:

determining the sensor data transgresses the threshold that corresponds with the route variable; and

generating the report responsive to the determining that the sensor data transgresses the threshold that corresponds with the route variable.

19. The non-transitory computer-readable medium of claim 15 , wherein the sensor data comprises location data that indicates a location of the vehicle.

20. The non-transitory computer-readable medium of claim 15 , wherein the route variable comprising an identification of a location, the sensor data comprises location data, and wherein the generating the report includes:

determining the location data identifies the location identified by the route variable; and

generating the report responsive to the determining the location data identifies the location identified by the route variable.

Assignments (3)
CORRECTIVE ASSIGNMENT TO CORRECT THE INVENTOR NAME TO SEAN MCGEE THAT WAS INCORRECTLY RECORDED AS SEAN AUSTEN MCGEE PREVIOUSLY RECORDED ON REEL 65329 FRAME 482. ASSIGNOR(S) HEREBY CONFIRMS THE THE ASSIGNMENT. Recorded Jun 24, 2025
From: NANDA, SACHAL; HOGAN, GREG; ZHANG, JENNIFER JULIA; SIEGEL, KATHRYN; LAM, KELSEY; MCGEE, SEAN; WU, ALEX; PEGUERO, TIRSO; WHITE, EMILY; SHREVE, ERIC; WU, WEI; JUNG, CHAEIN; CHUNG, HELEN; WEBER, SACHIE; SHIN, YOSUB; JAISWAL, UTKARSH
To: SAMSARA NETWORKS INC.
Reel/Frame 071712/0944 →
CHANGE OF NAME Recorded Jan 17, 2024
From: SAMSARA NETWORKS INC.
To: SAMSARA INC.
Reel/Frame 066154/0870 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 23, 2023
From: NANDA, SACHAL; HOGAN, GREG; ZHANG, JENNIFER JULIA; SIEGEL, KATHRYN; LAM, KELSEY; MCGEE, SEAN AUSTEN; WU, ALEX; PEGUERO, TIRSO; WHITE, EMILY; SHREVE, ERIC; WU, WEI; JUNG, CHAEIN; CHUNG, HELEN; WEBER, SACHIE; SHIN, YOSUB; JAISWAL, UTKARSH
To: SAMSARA NETWORKS INC.
Reel/Frame 065329/0482 →
Continuity (2)
Continuation 17447385 · Sep 10, 2021
Continuation 17249827 · Mar 15, 2021
References Cited (96)
US 5948040A · DeLorme et al. · 1999 [cited by applicant]
US 9557187B2 · Schuurbiers · 2017 [cited by examiner]
US 10832206B2 · Lafrance · 2020 [cited by applicant]
US 10895463B1 · Cope et al. · 2021 [cited by applicant]
US 10970746B2 · Singhal et al. · 2021 [cited by applicant]
US 11145208B1 · Nanda · 2021 [cited by examiner]
US 11182700B2 · Judge et al. · 2021 [cited by applicant]
US 11674813B1 · Chung · 2023 [cited by examiner]
US 11710409B2 · Nanda et al. · 2023 [cited by applicant]
US 12073725B2 · Woodrow · 2024 [cited by examiner]
US 20120253548A1 · Davidson · 2012 [cited by applicant]
US 20130069803A1 · Mccormick et al. · 2013 [cited by applicant]
US 20130116916A1 · Kickbusch · 2013 [cited by applicant]
US 20130238167A1 · Stanfield · 2013 [cited by examiner]
US 20130253833A1 · Tuukkanen · 2013 [cited by applicant]
US 20150338226A1 · Mason et al. · 2015 [cited by applicant]
US 20160307155A1 · Bell · 2016 [cited by applicant]
US 20160358471A1 · Hajj et al. · 2016 [cited by applicant]
US 20170076609A1 · Hubbard · 2017 [cited by examiner]
US 20170262786A1 · Khasis · 2017 [cited by applicant]
US 20180188042A1 · Chen · 2018 [cited by applicant]
US 20180209789A1 · Bryant et al. · 2018 [cited by applicant]
US 20180275661A1 · Glaser · 2018 [cited by examiner]
US 20180322431A1 · Folck · 2018 [cited by applicant]
US 20180341261A1 · Kislovskiy et al. · 2018 [cited by applicant]
US 20180373268A1 · Antunes Marques Esteves · 2018 [cited by applicant]
US 20180375939A1 · Magalhães De Matos · 2018 [cited by examiner]
US 20190185010A1 · Ganguli et al. · 2019 [cited by applicant]
US 20190187707A1 · Zheng et al. · 2019 [cited by applicant]
US 20190236959A1 · Belapurkar · 2019 [cited by examiner]
US 20190258251A1 · Ditty et al. · 2019 [cited by applicant]
US 20190279440A1 · Ricci · 2019 [cited by examiner]
US 20190285425A1 · Ludwick · 2019 [cited by examiner]
US 20200072626A1 · Kumar · 2020 [cited by examiner]
US 20200080856A1 · Ho · 2020 [cited by examiner]
US 20200167702A1 · Beaurepaire et al. · 2020 [cited by applicant]
US 20200193549A1 · Pedersen et al. · 2020 [cited by applicant]
US 20200200553A1 · Voznesensky et al. · 2020 [cited by applicant]
US 20200269877A1 · Mortazavi et al. · 2020 [cited by applicant]
US 20200309544A1 · Ozturk et al. · 2020 [cited by applicant]
US 20200326194A1 · Wang · 2020 [cited by examiner]
US 20200341490A1 · Silva et al. · 2020 [cited by applicant]
US 20200353917A1 · Leitermann et al. · 2020 [cited by applicant]
US 20200353937A1 · Bennett et al. · 2020 [cited by applicant]
US 20200357198A1 · Bennett et al. · 2020 [cited by applicant]
US 20200378771A1 · Beaurepaire · 2020 [cited by applicant]
US 20200380467A1 · Chen · 2020 [cited by applicant]
US 20210026353A1 · Luo · 2021 [cited by applicant]
US 20210026360A1 · Luo · 2021 [cited by applicant]
US 20210092551A1 · Millington et al. · 2021 [cited by applicant]
US 20210118330A1 · Baer et al. · 2021 [cited by applicant]
US 20210223051A1 · Hochberg · 2021 [cited by examiner]
US 20210293555A1 · Roherty et al. · 2021 [cited by applicant]
US 20210293573A1 · Sofman · 2021 [cited by examiner]
US 20210358308A1 · Li · 2021 [cited by examiner]
US 20220018674A1 · Xu · 2022 [cited by examiner]
US 20220164747A1 · Shah et al. · 2022 [cited by applicant]
US 20220187847A1 · Cella et al. · 2022 [cited by applicant]
US 20220292978A1 · Nanda et al. · 2022 [cited by applicant]
US 20220366336A1 · Khasis · 2022 [cited by examiner]
US 20220366369A1 · Nice · 2022 [cited by examiner]
US 20230106268A1 · Venkatesh · 2023 [cited by examiner]
US 20240077322A1 · Balasubramanian · 2024 [cited by examiner]
US 20240177102A1 · S · 2024 [cited by examiner]
CN 117664163A · 2024 [cited by examiner]
DE 112018005737T5 · 2020 [cited by examiner]
EP 3719449A1 · 2020 [cited by examiner]
GB 2610252A · 2023 [cited by examiner]
WO 2013188843 · 2013 [cited by applicant]
WO 2014172323 · 2014 [cited by applicant]
WO 2015036471 · 2015 [cited by applicant]
WO 2015179532 · 2015 [cited by applicant]
WO 2016077677 · 2016 [cited by applicant]
WO 2016123303 · 2016 [cited by applicant]
WO 2017205961 · 2017 [cited by applicant]
WO WO2018140505A1 · 2018 [cited by examiner]
WO WO2019023324A1 · 2019 [cited by examiner]
WO WO2019136341A1 · 2019 [cited by examiner]
WO WO2020090847A1 · 2020 [cited by examiner]
WO 2020131222 · 2020 [cited by applicant]
WO 2020132141 · 2020 [cited by applicant]
WO WO2023060275A1 · 2023 [cited by examiner]
Skarga-Bandurova, et al., “The Information Service for Delivering Arrival Public Transport Prediction,” 2018 IEEE 4th International Symposium on Wireless Systems, Lviv, Ukraine, 2018, pp. 191-195 (https://ieeexplore.iee… [cited by examiner]
Skarga-Bandurova, et al., “The Information Service for Delivering Arrival Public Transport Prediction,” 2018 IEEE 4th Intl Symposium on Wireless Systems within the Intl Conferences on Intelligent Data Acquisition and Ad… [cited by examiner]
“U.S. Appl. No. 17/249,827, Non Final Office Action mailed May 12, 2021”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/249,827, Response filed Jul. 8, 2021 to Non Final Office Action mailed May 12, 2021”, 20 pgs. [cited by applicant]
“U.S. Appl. No. 17/249,827, Notice of Allowance mailed Aug. 2, 2021”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/447,385, Preliminary Amendment filed Oct. 29, 2021”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/447,385, Non Final Office Action mailed Dec. 22, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/447,385, Response filed Feb. 1, 2023 to Non Final Office Action mailed Dec. 22, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/447,385, Notice of Allowance mailed Mar. 8, 2023”, 8 pgs. [cited by applicant]
“Compliance Product Brief”, Motive Technologies Inc, (2022), 4 pgs. [cited by applicant]
“Dispatch Product Brief”, Motive Technologies, Inc., (2022), 4 pgs. [cited by applicant]
“Driver Safety Product Brief”, Motive Technologies Inc, (2022), 4 pgs. [cited by applicant]
“Product Brief Tracking and Telematics”, Motive Technologies Inc, (2022), 4 pgs. [cited by applicant]
“Smart Event Thresholds Guide”, Motive Technologies Inc, (2022), 11 pgs. [cited by applicant]