IP Library › Granted Patent US 12,300,045
Granted Patent B2
US 12,300,045 · App. 17/651,886 · Granted May 13, 2025

Systems and methods for sending vehicle information and health data over a wireless network

Inventors: Peyton Riley (Atlanta, GA); Matt Shorts (Atlanta, GA); Spencer Fowler (Atlanta, GA); Oluwafemi Adeyemi (Atlanta, GA); Mark Barton (Atlanta, GA); Barak Weinisman (Atlanta, GA); Altan Stalker (Atlanta, GA)
Assignee: Cox Communications, Inc.
G07C5/0808G07C5/008G07C5/0816G07C5/0841H04W4/38H04W4/40
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,300,045
App. No.
17/651,886
Granted
May 13, 2025
Kind
B2
Abstract

Systems and methods are disclosed for sending vehicle information and health data over a wireless network. An example method may include receiving, from an on-board diagnostic (OBD) device associated with a vehicle and over a LoRaWAN network, a first message including first data, wherein the first data is a first category of data received by the OBD device from the vehicle. The example method may also include receiving, from the OBD device and over the LoRaWAN network, a second message including second data, wherein the second data is a second category of data received by the OBD device from the vehicle.

Claims (39)

1. A system comprising:

one or more processors; and

memory storing computer-executable instructions, that when executed by the processor, cause the processor to:

receive, by an on-board diagnostic (OBD) device and from a vehicle, first data and second data, wherein the first data is a first category of data and the second data is a second category of data;

create a first packet including a first portion of the first data;

determine a maximum amount of the first data that fits within the first packet, wherein the maximum amount of the first data is less than a size of the first data;

create, based on the maximum amount being less than the size of the first data, a second packet including a second portion of the first data, wherein the first packet includes a field indicating that the second portion of the first data is included in the second packet, wherein the first packet and the second packet include an indication of a category of data, a hash of a vehicle identification number (VIN) associated with the vehicle, a total number of DTCs associated with the first category of data, a number of DTCs included within the first packet, and an index of a first DTC within the first packet;

send, by the OBD device and over a LoRaWAN network, the first packet and the second packet; and

send, by the OBD device and over the LoRaWAN network, a third packet including the second data.

2. The system of claim 1 , wherein the first category of data and the second category of data include at least one of: a pending diagnostic trouble code (DTC), a stored DTC, and/or a permanent DTC.

3. The system of claim 1 , wherein the computer-executable instructions further cause the one or more processors to:

receive, from a remote system, an indication of a location within a memory of the vehicle where the first category of data and the second category of data are located, wherein the location is based on a type of the vehicle, and wherein receiving the first data and second data is based on the indication.

4. A method comprising:

receiving, from an on-board diagnostic (OBD) device associated with a vehicle and over a LoRaWAN network, a first message including a first portion of first data, wherein the first data is a first category of data received by the OBD device from the vehicle;

receiving, from the OBD device and over the LoRaWAN network, a second message including a second portion of the first data, wherein the second portion of the first data is included in the second message based on a determination that a maximum amount of the first data that fits within the first message is less than a size of the first data, and wherein the first message includes a field indicating that the second portion of the first data is included in the second message, wherein the first message and the second message include an indication of a category of data, a hash of a vehicle identification number (VIN) associated with the vehicle, a total number of DTCs associated with the first category of data, a number of DTCs included within the first message, and an index of a first DTC within the first message; and

receiving, from the OBD device and over the LoRaWAN network, a third message including second data, wherein the second data is a second category of data received by the OBD device from the vehicle.

5. The method of claim 4 , wherein the first category of data and the second category of data include at least one of: a pending diagnostic trouble code (DTC), a stored DTC, and/or a permanent DTC.

6. The method of claim 5 , further comprising:

determining that the first message and the third message are associated with the vehicle and with the first category of data;

extracting the first portion of the first data from the first message and the second portion of the first data from the third message; and

combining the first portion of the first data and the second portion of the first data.

7. The method of claim 4 , further comprising:

sending, to the OBD device, an indication of a location within a memory of the vehicle where the first category of data and the second category of data are located, wherein the location is based on a type of the vehicle.

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

receiving, from an on-board diagnostic (OBD) device associated with a vehicle and over a LoRaWAN network, a first message including a first portion of first data, wherein the first data is a first category of data received by the OBD device from the vehicle;

receiving, from the OBD device and over the LoRaWAN network, a second message including a second portion of the first data, wherein the second portion of the first data is included in the second message based on a determination that a maximum amount of the first data that fits within the first message is less than a size of the first data, and wherein the first message includes a field indicating that the second portion of the first data is included in the second message, wherein the first message and the second message include an indication of a category of data, a hash of a vehicle identification number (VIN) associated with the vehicle, a total number of DTCs associated with the first category of data, a number of DTCs included within the first message, and an index of a first DTC within the first message; and

receiving, from the OBD device and over the LoRaWAN network, a third message including second data, wherein the second data is a second category of data received by the OBD device from the vehicle.

9. The non-transitory computer-readable medium of claim 8 , wherein the first category of data and the second category of data include at least one of: a pending diagnostic trouble code (DTC), a stored DTC, and/or a permanent DTC.

10. The non-transitory computer-readable medium of claim 9 , wherein the computer-executable instructions further cause the one or more processors to perform operations of:

determining that the first message and the third message are associated with the vehicle and with the first category of data;

extracting the first portion of the first data from the first message and the second portion of the first data from the third message; and

combining the second portion of the first data and the second portion of the first data.

11. The non-transitory computer-readable medium of claim 8 , wherein the computer-executable instructions further cause the one or more processors to perform operations of:

sending, to the OBD device, an indication of a location within a memory of the vehicle where the first category of data and the second category of data are located, wherein the location is based on a type of the vehicle.

12. The system of claim 1 , wherein the computer-executable instructions further cause the one or more processors to:

receive, by a receiving device, the first packet and the second packet;

determine that a first VIN hash included in the second packet is a same VIN hash as a second VIN hash included in the first packet; and

determine, based on determining that the first VIN hash is a same VIN hash as the second VIN hash, that the first packet and second packet include related data.

13. The system of claim 1 , wherein a frequency of data transmission by the OBD device over the LoRaWAN network is based on a battery level of vehicle.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2025
From: COX COMMUNICATIONS, INC.
To: COGNOSOS, INC.
Reel/Frame 072432/0238 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2023
From: RILEY, PEYTON; SHORTS, MATT; FOWLER, SPENCER; ADEYEMI, OLUWAFEMI; BARTON, MARK; WEINISMAN, BARAK; STALKER, ALTAN
To: COX COMMUNICATIONS, INC.
Reel/Frame 062450/0416 →
Continuity (1)
Related Publication 20230267774A1 · Aug 24, 2023
References Cited (55)
US 6553292B2 · Kokes et al. · 2003 [cited by applicant]
US 6677854B2 · Dix · 2004 [cited by applicant]
US 6678591B2 · Ohmura et al. · 2004 [cited by applicant]
US 6735503B2 · Ames · 2004 [cited by applicant]
US 6933842B2 · Oesterling et al. · 2005 [cited by applicant]
US 7096101B2 · Sonnenrein et al. · 2006 [cited by applicant]
US 7155321B2 · Bromley et al. · 2006 [cited by applicant]
US 7359774B2 · Grenn · 2008 [cited by applicant]
US 7979178B2 · Bertosa et al. · 2011 [cited by applicant]
US 8744668B2 · Selkirk et al. · 2014 [cited by applicant]
US 8996230B2 · Lorenz et al. · 2015 [cited by applicant]
US 9047719B2 · Yagi et al. · 2015 [cited by applicant]
US 9224253B2 · Kakinuma · 2015 [cited by applicant]
US 9245393B2 · Yagi et al. · 2016 [cited by applicant]
US 9317840B2 · Kleinschmidt et al. · 2016 [cited by applicant]
US 9401054B2 · Fountain et al. · 2016 [cited by applicant]
US 9513789B2 · Marshall et al. · 2016 [cited by applicant]
US 9607448B2 · Ukai et al. · 2017 [cited by applicant]
US 9619946B2 · Huang et al. · 2017 [cited by applicant]
US 10156960B2 · Marshall et al. · 2018 [cited by applicant]
US 10606445B2 · Marshall et al. · 2020 [cited by applicant]
US 10666767B1 · Floyd · 2020 [cited by examiner]
US 10706645B1 · Herron et al. · 2020 [cited by applicant]
US 10748354B2 · Liu et al. · 2020 [cited by applicant]
US 10852910B2 · Marshall et al. · 2020 [cited by applicant]
US 10964134B2 · Frisch et al. · 2021 [cited by applicant]
US 11513814B1 · Luban · 2022 [cited by examiner]
US 20020103583A1 · Ohmura et al. · 2002 [cited by applicant]
US 20050234616A1 · Oliver et al. · 2005 [cited by applicant]
US 20050251304A1 · Cancellara et al. · 2005 [cited by applicant]
US 20060101311A1 · Lipscomb · 2006 [cited by applicant]
US 20060106508A1 · Liebl et al. · 2006 [cited by applicant]
US 20060122748A1 · Nou · 2006 [cited by applicant]
US 20060136104A1 · Brozovich et al. · 2006 [cited by applicant]
US 20080109130A1 · Huang · 2008 [cited by applicant]
US 20090265055A1 · Gillies · 2009 [cited by applicant]
US 20100042287A1 · Zhang et al. · 2010 [cited by applicant]
US 20120116609A1 · Jung et al. · 2012 [cited by applicant]
US 20140121888A1 · Guo et al. · 2014 [cited by applicant]
US 20150134192A1 · Kakinuma · 2015 [cited by applicant]
US 20150170435A1 · Ko · 2015 [cited by applicant]
US 20180293811A1 · Liu et al. · 2018 [cited by applicant]
US 20180342115A1 · Chen · 2018 [cited by examiner]
US 20190188925A1 · Calvert · 2019 [cited by examiner]
US 20200145342A1 · Olesen · 2020 [cited by examiner]
US 20200145978A1 · Gulati · 2020 [cited by examiner]
US 20200219335A1 · Gintz · 2020 [cited by examiner]
US 20200226852A1 · Lian et al. · 2020 [cited by applicant]
US 20210042014A1 · Marshall et al. · 2021 [cited by applicant]
US 20210065474A1 · Liu et al. · 2021 [cited by applicant]
US 20210065480A1 · Liu et al. · 2021 [cited by applicant]
US 20230252824A1 · Merg · 2023 [cited by examiner]
WO 2019057188 · 2019 [cited by applicant]
WO 2021035634 · 2021 [cited by applicant]
WO 2021042241 · 2021 [cited by applicant]