IP Library Granted Patent US 11,145,208
Granted Patent B1
US 11,145,208 · App. 17/249,827 · Granted Oct 12, 2021

Customized route tracking

Inventors: Sachal Nanda (San Francisco, 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 (Park City, UT); Eric Shreve (San Francisco, CA); Wei Wu (San Francisco, CA); Chaein Jung (Seoul, KR); Helen Chung (Great Falls, VA); Sachie Weber (Aspen, CO); Yosub Shin (Seoul, KR); Utkarsh Jaiswal (San Francisco, CA)
Assignee: Samsara Networks 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 11,145,208
App. No.
17/249,827
Granted
Oct 12, 2021
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 (51)

1. A method comprising:

receiving, by a route management system, first sensor data describing movement of a first vehicle associated with a first account of the route management system, the first vehicle being assigned to travel a first route;

receiving, by the route management system, second sensor data describing movement of a second vehicle associated with a second account of the route management system, the second vehicle being assigned to travel a second route;

generating a first route tracking report based on the first sensor data, the first route and a first route tracking configuration associated with the first account, the first route tracking configuration including a first tracking customization to a set of route variables for tracking vehicles;

generating a second route tracking report based on the second sensor data, the second route and a second route tracking configuration associated with the second account, the second route tracking configuration including a second tracking customization to the set of route variables for tracking vehicles, the second tracking customization being different than the first tracking customization;

causing presentation of the first route tracking report on a first client device associated with the first account; and

causing presentation of the second route tracking report a second client device associated with the second account.

2. The method of claim 1 , wherein the set of route variables for the first route includes a start time and an end time defining a scheduled route window for the first route, and the first route tracking configuration includes a first tracking customization to the start time or the end time for the first route.

3. The method of claim 2 , further comprising:

generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.

4. The method of claim 1 , wherein the first route tracking configuration defines a threshold period of time for determining arrival at a scheduled stop.

5. The method of claim 4 , wherein generating the first route tracking report comprises:

determining, based on the first sensor data, that the first vehicle is within a first geographic region associated with a first scheduled stop of the first route;

determining that a period of time that the first vehicle is within the first geographic region meets the threshold period of time defined by the first route tracking configuration; and

including data in the first route tracking report indicating that the first vehicle arrived at the first scheduled stop of the first route.

6. The method of claim 4 , wherein the first route tracking configuration further defines an expected amount of time to be spent at the scheduled stop.

7. The method of claim 6 , further comprising:

determining, based on the first sensor data, that the first vehicle is within a first geographic region associated with a first scheduled stop of the first route; and

determining a departure time for the first vehicle from the first scheduled stop based on the expected amount of time defined in the first route tracking configuration.

8. A route management 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 route management system to perform operations comprising:

receiving first sensor data describing movement of a first vehicle associated with a first account of the route management system, the first vehicle being assigned to travel a first route;

receiving second sensor data describing movement of a second vehicle associated with a second account of the route management system, the second vehicle being assigned to travel a second route;

generating a first route tracking report based on the first sensor data, the first route and a first route tracking configuration associated with the first account, the first route tracking configuration including a first tracking customization to a set of route variables for tracking vehicles;

generating a second route tracking report based on the second sensor data, the second route and a second route tracking configuration associated with the second account, the second route tracking configuration including a second tracking customization to the set of route variables for tracking vehicles, the second tracking customization being different than the first tracking customization;

causing presentation of the first route tracking report on a first client device associated with the first account; and

causing presentation of the second route tracking report on a second client device associated with the second account.

9. The route management system of claim 8 , wherein the set of route variables for the first route includes a start time and an end time defining a scheduled route window for the first route, and the first route tracking configuration includes a first tracking customization to the start time or the end time for the first route.

10. The route management system of claim 9 , the operations further comprising:

generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.

11. The route management system of claim 8 , wherein the first route tracking configuration defines a threshold period of time for determining arrival at a scheduled stop.

12. The route management system of claim 11 , wherein generating the first route tracking report comprises:

determining, based on the first sensor data, that the first vehicle is within a first geographic region associated with a first scheduled stop of the first route;

determining that a period of time that the first vehicle is within the first geographic region meets the threshold period of time defined by the first route tracking configuration; and

including data in the first route tracking report indicating that the first vehicle arrived at the first scheduled stop of the first route.

13. The route management system of claim 11 , wherein the first route tracking configuration further defines an expected amount of time to be spent at the scheduled stop.

14. The route management system of claim 13 , the operations further comprising:

determining, based on the first sensor data, that the first vehicle is within a first geographic region associated with a first scheduled stop of the first route; and

determining a departure time for the first vehicle from the first scheduled stop based on the expected amount of time defined in the first route tracking configuration.

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

receiving first sensor data describing movement of a first vehicle associated with a first account of the route management system, the first vehicle being assigned to travel a first route;

receiving second sensor data describing movement of a second vehicle associated with a second account of the route management system, the second vehicle being assigned to travel a second route;

generating a first route tracking report based on the first sensor data, the first route and a first route tracking configuration associated with the first account, the first route tracking configuration including a first tracking customization to a set of route variables for tracking vehicles;

generating a second route tracking report based on the second sensor data, the second route and a second route tracking configuration associated with the second account, the second route tracking configuration including a second tracking customization to the set of route variables for tracking vehicles, the second tracking customization being different than the first tracking customization;

causing presentation of the first route tracking report on a first client device associated with the first account; and

causing presentation of the second route tracking report on a second client device associated with the second account.

16. The non-transitory computer-readable medium of claim 15 , wherein the set of route variables for the first route includes a start time and an end time defining a scheduled route window for the first route, and the first route tracking configuration includes a first tracking customization to the start time or the end time for the first route.

17. The non-transitory computer-readable medium of claim 16 , the operations further comprising:

generating a route tracking window based on the scheduled route window for the first route and the first tracking customization, the route tracking window being an expansion of the scheduled route window based on the first tracking customization, wherein the first route tracking report is generated based on sensor data describing movement of the first vehicle during the route tracking window, including sensor data describing movement of the first vehicle that is outside of the scheduled route window.

18. The non-transitory computer-readable medium of claim 15 , wherein the first route tracking configuration defines a threshold period of time for determining arrival at a scheduled stop.

Assignments (4)
CHANGE OF NAME Recorded Jan 17, 2024
From: SAMSARA NETWORKS INC.
To: SAMSARA INC.
Reel/Frame 066154/0870 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE RECEIVING PARYT NAME PREVIOUSLY RECORDED AT REEL: 057301 FRAME: 0662. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 14, 2021
From: WHITE, EMILY
To: SAMSARA NETWORKS INC.
Reel/Frame 057500/0100 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 26, 2021
From: WHITE, EMILY
To: SAMSARA INC.
Reel/Frame 057301/0662 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 15, 2021
From: NANDA, SACHAL; HOGAN, GREG; ZHANG, JENNIFER JULIA; SIEGEL, KATHRYN; LAM, KELSEY; MCGEE, SEAN; WU, ALEX; PEGUERO, TIRSO; SHREVE, ERIC; WU, WEI; JUNG, CHAEIN; CHUNG, HELEN; WEBER, SACHIE; SHIN, YOSUB; JAISWAL, UTKARSH
To: SAMSARA NETWORKS INC.
Reel/Frame 055597/0313 →
Cited By (3)
US 12,333,462 US 12,374,225 US 12,717,650