IP Library Granted Patent US 10,652,335
Granted Patent B2
US 10,652,335 · App. 14/828,581 · Granted May 12, 2020

Dynamically presenting vehicle sensor data via mobile gateway proximity network

Inventor: Mark Philip Botticelli (North Grafton, MA)
Assignee: Trimble Inc.
H04L67/125H04L67/025H04L67/26H04L67/36H04W84/18
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 10,652,335
App. No.
14/828,581
Granted
May 12, 2020
Kind
B2
Abstract

A new sensor is detected being added to a vehicle sensor bus. A publication topic is created based on the new sensor. The publication topic is made available via at least a server component operating via the proximity networking radio. Data from the new sensor is added to the publication topic. In response to a subscription to the publication topic via a user device, the data is dynamically presented to the user device via the server component.

Claims (63)

1. A mobile gateway comprising:

a sensor interface configured to communicate via a vehicle sensor bus;

a proximity networking radio configured to communicate with a user device via a proximity network;

a radio module configured to communicate with an Internet-connected, cloud gateway;

a sensor logging component;

a publish/subscribe interface; and

a processor coupled to the sensor interface, the proximity networking radio, the radio module, the sensor logging component, and the publish/subscribe interface;

wherein the sensor interface, the proximity networking radio, the radio module, the sensor logging component, the publish/subscribe interface, and the processor are integrated in the mobile gateway located on a motor vehicle and are configured to operate on the motor vehicle;

wherein the processor is configured to:

detect a new sensor added to the vehicle sensor bus via the sensor logging component;

determine, via the publish/subscribe interface of the mobile gateway via accessing the cloud gateway, a context in which the sensor is being used;

create a publication topic based on the new sensor and the context, the publication topic made available via the publish/subscribe interface that is further accessible via the proximity networking radio;

add sensor data from the new sensor to the publication topic via the sensor logging component;

in response to creation of the publication topic via the publish/subscribe interface, receive a template from the cloud gateway that defines a view of the sensor data; and

in response to a subscription to the publication topic via the user device, dynamically present the sensor data to a web browser of the user device via a web server using the template to define a web page used to view of the sensor data on the user device.

2. The mobile gateway of claim 1 , wherein the sensor bus comprises a controller area network bus.

3. The mobile gateway of claim 1 , wherein the publish/subscribe interface-comprises an HTTP server.

4. The mobile gateway of claim 1 , wherein the proximity network comprises a wireless network.

5. The mobile gateway of claim 1 , wherein the processor is further configured to:

determine a numerical identifier of the new sensor; and

based on the numerical identifier, determine at least a type of the new sensor.

6. The mobile gateway of claim 5 , wherein the publication topic is based on the type of the new sensor.

7. The mobile gateway of claim 1 , wherein the processor is further configured to:

determine a user selection of multiple topics via the user device and the web server; and

dynamically present sensor data from the multiple topics via the web server.

8. The mobile gateway of claim 1 , wherein the processor is further configured to:

receive a second subscription to the publication topic via the cloud gateway; and

in response to the second subscription, dynamically send the sensor data to the cloud gateway.

9. The mobile gateway of claim 1 , wherein the processor is further configured to:

create another publication topic based on user data created at the user device and present the other publication topic via the publish/subscribe interface;

receive the user data from the user device via the sensor logging component; and

in response to a subscription of the other publication topic via the cloud gateway, provide the user data to the cloud gateway.

10. The mobile gateway of claim 1 , wherein the processor is further configured to:

determine, via the publish/subscribe interface, the context in which the sensor is being used by determining, via the publish/subscribe interface, a vehicle subsystem in which the sensor is configured to operate.

11. The mobile gateway of claim 1 , wherein the processor is further configured to:

determine, via the sensor logging component, a type of the detected new sensor.

12. The mobile gateway of claim 11 , wherein the publication topic is created, via the publish/subscribe interface, based at least on the type of the detected new sensor determined via the sensor logging component.

13. The mobile gateway of claim 1 , wherein the processor is further configured to:

authenticate a user's access to the sensor data using at least one of a hardware key or biometrics information of the user received from the user device.

14. The mobile gateway of claim 1 , wherein the processor is further configured to:

compress, via the sensor logging component, new sensor data for storage; and

discard, via the sensor logging component, prior sensor data.

15. The mobile gateway of claim 9 , wherein the user data received from the user device comprises input by a vehicle operator indicating at least one of rest or operating times.

16. A method comprising:

detecting a new sensor added to a vehicle sensor bus via a sensor logging component of a mobile gateway;

determining, via an Internet-connected, cloud gateway coupled to a publish/subscribe interface of the mobile gateway, a context in which the sensor is being used;

creating a publication topic based on the new sensor and the context, the publication topic made available via at least a the publish/subscribe interface of the mobile gateway operating via a proximity network and the cloud gateway;

adding sensor data from the new sensor to the publication topic;

in response to creation of the publication topic via the publish/subscribe interface, receiving a template from the cloud gateway that defines a view of the sensor data;

publishing the publication topic for subsequent subscription by a user via a user device that is coupled to the mobile gateway via the proximity network;

receiving a subscription to the published publication topic from the user via the user device; and

in response to the subscription to the publication topic via the user device, dynamically presenting the data to a web browser of the user device via a server component using the template to define a web page used to view the sensor data on the user device.

17. The method of claim 16 , further comprising:

determining a numerical identifier of the new sensor; and

based on the numerical identifier, determining at least a type of the new sensor.

18. The method of claim 17 , wherein the publication topic is based on the type of the new sensor.

19. The method of claim 16 , further comprising:

determining user selection of multiple topics via the user device and the server component; and

dynamically presenting data from the multiple topics via the server component.

20. The method of claim 16 , further comprising:

creating another publication topic based on user data created at the user device and present the other publication topic via the publish/subscribe interface;

receiving the user data from the user device via the sensor logging component; and

in response to a subscription of the other publication topic via the cloud gateway, providing the user data to the cloud gateway.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED AT REEL: 70232 FRAME: 268. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Feb 21, 2025
From: TRIMBLE INC.
To: PEOPLENET COMMUNICATIONS CORPORATION
Reel/Frame 071216/0670 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 13, 2025
From: TRIMBLE INC.
To: PEOPLENET COMMUNICATIONS CORPORATION; TRIMBLE N.V.; TOGS USA, INC.; GEOTRAC SYSTEMS INC.; ACUNIA INTERNATIONAL NV; WEVADA NV; SOLID SAS; PUNCH TELEMATIX FRANCE SAS; PUNCH TELEMATIX NEDERLAND B.V.; LOGICWAY B.V.
Reel/Frame 070232/0268 →
MERGER AND CHANGE OF NAME Recorded Aug 9, 2019
From: TRIMBLE NAVIGATION LIMITED; TRIMBLE INC.
To: TRIMBLE INC.
Reel/Frame 050016/0990 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 11, 2015
From: BOTTICELLI, MARK PHILIP
To: TRIMBLE NAVIGATION LIMITED
Reel/Frame 036538/0189 →
Continuity (2)
Provisional Application 62038611 · Aug 18, 2014
Related Publication 20160050265A1 · Feb 18, 2016
Cited By (32)
US 12,197,610 US 12,213,090 US 12,228,944 US 12,253,617 US 12,256,021 US 12,260,616 US 12,269,498 US 12,289,181 US 12,306,010 US 12,327,445 US 12,328,639 US 12,344,168 US 12,346,712 US 12,367,718 US 12,426,007 US 12,445,285 US 12,450,329 US 12,479,446 US 12,501,178 US 12,511,947 US 12,534,097 US 12,561,624 US 12,565,143 US 12,626,200 US 12,630,050 US 12,646,402 US 12,651,529 US 12,662,152 US 12,665,989 US 12,671,464 US 12,675,419 US 12,701,004