IP Library › Granted Patent US 12,296,876
Granted Patent B2
US 12,296,876 · App. 17/703,471 · Granted May 13, 2025

System and method for remote device monitoring

Inventors: Kent Shue (Bonner Springs, KS); Carlos Aguilera (Lenexa, KS); Marcus Parrott (Kansas City, MO); Jerry Wade Specht (Overland Park, KS); Perry Peden, Jr. (Overland Park, KS)
Assignee: BNSF Railway Company
B61L27/70B61K9/08B61L23/04B61L23/042B61L27/40B61L27/53
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,296,876
App. No.
17/703,471
Granted
May 13, 2025
Kind
B2
Abstract

A railroad infrastructure communication network is presented. The network can include a plurality of infrastructure nodes distributed proximate a railroad track, such as near railroad equipment and/or assets. Infrastructure nodes can be configured to receive data from equipment sensor and/or assets and transmit such data via the network. Infrastructure nodes can further generate alert and/or alert packets based on such received data. Infrastructure nodes can self-define in a network infrastructure depending on configured connection types, and can for example, serve as repeater nodes (to promulgate a transmission to additional infrastructure nodes) and/or collector nodes (to collect data for a centralized server node). A server node can be configured to receive data and/or packet from infrastructure nodes and generate requests for additional systems, personnel, etc. to address such requests. The network can limit the data transmission size and leverage distributed processing capabilities to enable transmissions over long ranges, such as by reducing the bandwidth required to transmit packets.

Claims (61)

1. A method for alert generation and handling in a railroad infrastructure, comprising:

receiving, via a second node having a second processor, sensor data related to a railroad asset;

generating an alert if the sensor data satisfies an alert threshold;

determining at least one configured connection type;

defining the second node as a first node type if a first connection type is not configured on the second node;

defining the second node as a second node type if the first connection type is configured on the second node;

transmitting the alert to a third node if a first node is the first node type; and

transmitting the alert to the first node if the second node is the second node type.

2. The method of claim 1 , further comprising the first node:

receiving the alert;

generating an acknowledgment;

transmitting the acknowledgment to at least the second node;

generating a request; and

transmitting the request.

3. The method of claim 2 , further comprising the first node:

determining if the request is acknowledged;

retransmitting the request if the request is not acknowledged; and

terminating the request if the request is acknowledged.

4. The method of claim 1 , wherein the second node is located proximate a railroad track.

5. The method of claim 1 , wherein the second node is located at a crossing house.

6. The method of claim 1 , wherein the railroad asset is a railroad crossing.

7. The method of claim 1 , wherein the second node transmits the alert to the third node via a LoRa protocol.

8. The method of claim 1 , wherein the third node is of the second node type.

9. A method of integrating a node into a railroad monitoring infrastructure, the system comprising:

receiving, via an infrastructure node having a first processor, a first packet having first data;

determining whether on-node processing is required and at least one configured connection type;

defining the infrastructure node as a first node type if a first connection type is not configured on the infrastructure node;

defining the infrastructure node as a second node type if the infrastructure node is configured with the first connection type;

repeating the first packet via a second connection type if the infrastructure node is defined as the first node type; and

processing the first packet to generate a second packet having second data if the infrastructure node is defined as the second node type.

10. The method of claim 9 , further comprising the infrastructure node transmitting the second packet via the first connection type if the infrastructure node is defined as the second node type and the first connection type is available.

11. The method of claim 9 , further comprising the infrastructure node transmitting the second packet via a third connection type if the at least one infrastructure node is of the second node type and the first connection type is not available.

12. The method of claim 9 , further comprising the infrastructure node:

determining, using the first packet, if acknowledgment is required;

requesting acknowledgment if acknowledgment is required; and

terminating transmission of the first or second packet if acknowledgment is received.

13. The method of claim 12 , further comprising the server node generating a first request and transmitting the first request if the second data includes an alert.

14. The method of claim 9 , further comprising:

receiving, via a server node having a second processor, the second packet;

identifying, via a server node, the second data;

generating, via a server node, an acknowledgment if the second data requires acknowledgment; and

transmitting, via a server node, the acknowledgment to the infrastructure node.

15. The method of claim 14 , further comprising the server node:

determining if the second data includes a node status;

generating a second request if the node status indicates that node attention is required; and

transmitting the second request.

16. The method of claim 9 , further comprising the infrastructure node:

determining if the first data has reached a first destination;

if the first destination has been reached, processing the first packet, determining if acknowledgment is required, and, if acknowledgment is required, transmitting an acknowledgment.

17. The method of claim 9 , wherein the infrastructure node includes a first memory having a plurality of data, thresholds, and specifications related to railroad assets.

18. A method of integrating a node into a railroad monitoring infrastructure, the system comprising:

determining, via a first node having a first processor, if a temporal threshold has been satisfied;

determining a node status of the first node after the temporal threshold has been satisfied;

encapsulating processed packet data and retransmitting an encapsulated data packet;

determining one or more connection types for the first node;

defining the first node as a first node type if the first node is not configured with a first connection type;

transmitting the node status to an infrastructure node.

19. The method of claim 9 , wherein the node status includes node connections, health, temperature, and location.

20. The method of claim 9 , further comprising:

defining the first node as a second node type if the first node is configured with a first connection type; and

transmitting the node status to a server node.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 24, 2022
From: SHUE, KENT; AGUILERA, CARLOS; PARROTT, MARCUS; SPECHT, JERRY WADE; PEDEN, PERRY, JR.
To: BNSF RAILWAY COMPANY
Reel/Frame 059392/0718 →
Continuity (2)
Continuation 17506071 · Oct 20, 2021
Related Publication 20230122108A1 · Apr 20, 2023
References Cited (37)
US 7705743B2 · Barone et al. · 2010 [cited by applicant]
US 8605754B2 · Siriwongrairat et al. · 2013 [cited by applicant]
US 10106079B2 · Denny et al. · 2018 [cited by applicant]
US 11305796B1 · Shue · 2022 [cited by examiner]
US 20020027495A1 · Darby, Jr. · 2002 [cited by examiner]
US 20060085103A1 · Smith, Jr. · 2006 [cited by examiner]
US 20070040070A1 · Stevenson et al. · 2007 [cited by applicant]
US 20090219900A1 · Kokkinen et al. · 2009 [cited by applicant]
US 20110026411A1 · Hao · 2011 [cited by examiner]
US 20110075641A1 · Siriwongpairat · 2011 [cited by examiner]
US 20160046308A1 · Chung et al. · 2016 [cited by applicant]
US 20160052531A1 · Boukari · 2016 [cited by applicant]
US 20160144875A1 · Kim, II · 2016 [cited by examiner]
US 20160272228A1 · LeFebvre et al. · 2016 [cited by applicant]
US 20170001653A1 · Ferencz, Jr. · 2017 [cited by examiner]
US 20170088046A1 · Denny · 2017 [cited by examiner]
US 20170279636A1 · Giroud · 2017 [cited by examiner]
US 20170320507A1 · Denny et al. · 2017 [cited by applicant]
US 20170282944A1 · Carlson · 2017 [cited by examiner]
US 20170313331A1 · Hilleary · 2017 [cited by examiner]
US 20180199237A1 · Vare et al. · 2018 [cited by applicant]
US 20190054942A1 · Carlson · 2019 [cited by applicant]
US 20190071106A1 · Carlson · 2019 [cited by applicant]
US 20190251804A1 · Stogel · 2019 [cited by applicant]
US 20190329806A1 · Anderson et al. · 2019 [cited by applicant]
US 20210291881A1 · Morgart et al. · 2021 [cited by applicant]
US 20230122108A1 · Shue et al. · 2023 [cited by applicant]
CN 207965551U · 2018 [cited by applicant]
EP 3199421B1 · 2020 [cited by applicant]
WO 2019185872A1 · 2019 [cited by applicant]
GE, Industrial Communication Solutions for the Rail Industry , Dec. 31, 2016. [cited by applicant]
Aguilera, C. Remote Device Monitoring Abstract., Dec. 11, 2019. [cited by applicant]
Aguilera, C. Remote Device Monitoring Abstract., Jun. 3, 2020. [cited by applicant]
Aguilera, C. Remote Device Monitoring Abstract., May 8, 2020. [cited by applicant]
Aguilers—GNCC Presentation Pooled Fund Draft Jun. 17, 2020. [cited by applicant]
Aguilers—AREMA 2020 Remote Device Monitoring Presentation Jun. 4, 2020. [cited by applicant]
Aguilers—AREMA 2020 Remote Device Monitoring Presentation Aug. 21, 2020. [cited by applicant]