WO2023158428A1

WO2023158428A1 - Wireless device for railcar tracking

Info

Publication number: WO2023158428A1
Application number: PCT/US2022/016800
Authority: WO
Inventors: Jimmy Pang; Bharanikumar RAMASUNDARAM
Original assignee: Trinityrail Leasing Management, Inc.
Priority date: 2022-02-17
Filing date: 2022-02-17
Publication date: 2023-08-24

Abstract

In certain embodiments, a system comprises a railcar and a wireless device coupled to the railcar. The railcar is configured to travel a track and is associated with identification information that indicates an identity of the railcar. The wireless device comprises memory and processing circuitry. The memory is configured to store the identification information associated with the railcar. The processing circuitry is configured to provide status information to one or more trackside automatic equipment identification (AEI) readers and to one or more wireless network nodes. The status information that the processing circuitry is configured to provide to the one or more trackside AEI readers comprises the identification information associated with the railcar.

Description

WIRELESS DEVICE FOR RAILCAR TRACKING

TECHNICAL FIELD

Certain embodiments of the disclosure relate, in general, to a wireless device for railcar tracking. BACKGROUND

Automatic equipment identification (AEI) is an electronic recognition system used by the railroad industry. The electronic recognition system includes AEI readers deployed trackside and spaced along the path of a railroad track. For example, an AEI reader may be located at an entrance or exit of a switchyard. Each AEI reader is configured to automatically identify a railcar when the railcar passes the AEI reader. In particular, the electronic recognition system uses AEI tags mounted on each side of the railcar to send the AEI readers radio frequency (RF) signals indicating identification information for the railcar. The AEI readers use this information to identify the railcar when en route. SUMMARY

According to certain embodiments, a system comprises a railcar and a wireless device coupled to the railcar. The railcar is configured to travel a track and is associated with identification information that indicates an identity of the railcar. The wireless device comprises memory and processing circuitry. The memory is configured to store the identification information associated with the railcar. The processing circuitry is configured to provide status information to one or more trackside AEI readers and to one or more wireless network nodes. The status information that the processing circuitry is configured to provide to the one or more trackside AEI readers comprises the identification information associated with the railcar.

Certain embodiments of the system may include one or more additional features, such as any one or more of the following:

Certain embodiments receive a signal from a positioning system and determine location information associated with the railcar based on the signal received from the positioning system. The status information that the processing circuitry is configured to provide to the one or more wireless network nodes comprises the location information. Certain embodiments may include the location information in the status information provided to the one or more trackside AEI readers.

Certain embodiments determine whether the railcar is stationary or in motion. While the railcar is in motion, certain embodiments provide the location information to the one or more wireless network nodes based on a pre-determined periodicity. While the railcar is stationary, certain embodiments abstain from providing the location information to the one or more wireless network nodes.

Certain embodiments determine when to provide the location information to the one or more wireless network nodes based at least in part on a proximity of the railcar to one of the trackside AEI readers. For example, certain embodiments determine the proximity of the railcar to the one of the trackside AEI readers based on a geofence region associated with the one of the trackside AEI readers. In response to exiting the geofence region, certain embodiments determine whether the status information was provided to the one of the trackside AEI readers associated with the geofence region. Alternatively, in response to determining that the status information was not provided to the one of the trackside AEI readers associated with the geofence region, certain embodiments provide the location information to the one or more wireless network nodes.

Certain embodiments provide the identification information to one of the trackside AEI readers at a first time and determine whether to provide the location information to the one or more wireless network nodes at a second time. The determination is based on whether the second time is within a pre-determined time period of the first time. In response to determining that the second time is within the pre-determined time period of the first time, certain embodiments wait to provide the location information to the one or more wireless network nodes. Alternatively, in response to determining that the second time is outside the pre-determined time period of the first time, certain embodiments provide the location information to the one or more wireless network nodes at the second time.

In certain embodiments, the system further comprises one or more sensors coupled to the railcar or to cargo of the railcar. Certain embodiments receive one or more signals from the one or more sensors, determine sensor information based on the one or more signals, and include the sensor information with status information provided to the one or more wireless network nodes and/or with status information provided to the one or more trackside AEI readers.

According to certain embodiments, a method performed by a wireless device comprises storing identification information associated with a railcar in memory of the wireless device. The method comprises receiving a signal from a positioning system and determining location information associated with the railcar based on the signal received from the positioning system. The method comprises providing first status information to one or more trackside AEI readers and providing second status information to one or more wireless network nodes. The first status information comprises the identification information associated with the railcar and the second status information comprises the location information.

According to certain embodiments, one or more computer-readable non- transitory storage media embody instructions that, when executed by processing circuitry of a wireless device, cause the performance of operations comprising storing identification information associated with a railcar in memory of the wireless device. The operations comprise receiving a signal from a positioning system and determining location information associated with the railcar based on the signal received from the positioning system. The operations comprise providing first status information to one or more trackside AEI readers and providing second status information to one or more wireless network nodes. The first status information comprises the identification information associated with the railcar and the second status information comprises the location information.

Certain embodiments determine whether the railcar is stationary or in motion and provide the location information while the railcar is in motion and abstain from providing the location information when the railcar is stationary.

Certain embodiments determine when to provide the location information to the one or more wireless network nodes based at least in part on a proximity of the railcar to one of the trackside AEI readers.

Certain embodiments determine a proximity of the railcar to the one of the trackside AEI readers based on a geofence region associated with the one of the trackside AEI readers. In response to exiting the geofence region, certain embodiments determine whether the first status information was provided to the one of the trackside AEI readers associated with the geofence region. In response to determining that the first status information was not provided to the one of the trackside AEI readers associated with the geofence region, certain embodiments provide the location information to the one or more wireless network nodes.

Certain embodiments provide the identification information to one of the trackside AEI readers at a first time and determine whether to provide the location information to the one or more wireless network nodes at a second time based on whether the second time is within a pre-determined time period of the first time. In response to determining that the second time is within the pre-determined time period of the first time, certain embodiments wait to provide the location information to the one or more wireless network nodes. In response to determining that the second time is outside the pre-determined time period of the first time, certain embodiments provide the location information to the one or more wireless network nodes at the second time.

Certain embodiments receive one or more signals from one or more sensors coupled to the railcar or to cargo of the railcar and determine sensor information based on the one or more signals. Certain embodiments include the sensor information in the second status information. Examples of sensors may include a temperature sensor, a humidity sensor, a cargo volume sensor, a cargo weight sensor, a gate open sensor, or a hatch open sensor.

Optionally, certain embodiments may include the identification information in the second status information provided to the one or more wireless network nodes.

Optionally, certain embodiments may include the location information and/or the sensor information in the first status information provided to the one or more trackside AEI readers.

Certain embodiments may provide one or more technical advantages. Certain embodiments may allow for modernizing railcar communications from passive Radio Frequency Identification (RFID) technology to condition-based, real-time communication. Certain embodiments may allow for simplifying hardware, software, and/or device management by using a single wireless device for communicating status information. For example, instead of requiring a railcar to be equipped with both an AEI tag and a separate GPS device, a single wireless device may provide both AEI tag functionality and GPS device functionality. Certain embodiments facilitate compatibility between the AEI tag functionality and the GPS device functionality included in the same wireless device. Certain embodiments provide compatibility with AEI readers and other components of existing AEI systems. Certain embodiments include digital health self-monitoring of the wireless device. For example, artificial intelligence or machine learning may be used to monitor telemetry information and detect a problem with the wireless device. This may allow for more efficient detection of a malfunctioning device than methods that rely on visual inspection by a person. In addition, certain embodiments provide robust status information associated with the railcar, which may allow for efficient detection if the railcar has a problem. Certain embodiments may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 is a block diagram illustrating an example system according to certain embodiments of the present disclosure.

FIGURE 2 is a block diagram illustrating an example of a wireless device according to certain embodiments of the present disclosure.

FIGURE 3 is a flow chart illustrating a method performed by a wireless device according to certain embodiments of the present disclosure.

FIGURE 4 is a flow chart illustrating a method according to certain embodiments of the present disclosure.

FIGURE 5 is a flow chart illustrating a method performed by a wireless device according to certain embodiments of the present disclosure.

FIGURE 6 is a flow chart illustrating a method performed by a wireless device according to certain embodiments of the present disclosure. FIGURE 7 is a flow chart illustrating a method performed by a wireless device according to certain embodiments of the present disclosure.

FIGURE 8 is a flow chart illustrating a method performed by a wireless device according to certain embodiments of the present disclosure.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Like numerals indicate like and corresponding aspects of the various figures. Other embodiments are contained within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

As described above, the railroad industry uses AEI tags mounted to a railcar in order to identify the railcar to trackside AEI readers. This allows for tracking the location of a railcar. For example, the railcar can be mapped to a location of a particular AEI reader when that AEI reader reads identification information from the railcar’s AEI tag. However, existing AEI tags use passive RFID technology that can only be read with AEI readers. An existing AEI tag includes electronic circuitry, but it has no power of its own. As the railcar approaches an AEI reader, the AEI reader sends an RF signal that the AEI tag receives, modulates, a reflects back to the AEI reader with identification information, such as the car identification number. The AEI reader receives this identification information and processes the identification in order to report the specific railcar location to the railroad. As such, the railcar location can only be determined when the railcar passes an AEI reader. If the railcar is outside of the physical area sensed by AEI readers, the railcar’s precise location cannot be known (e.g., the AEI system would only know the location where the railcar’s AEI tag was most recently read by an AEI reader). Additionally, the AEI tags fail to provide details about the condition of the railcar.

Global Positioning System (GPS) devices provide an independent solution for locating a railcar. GPS devices allow for improved tracking of the railcar location because, unlike AEI tags that are limited to communicating with AEI readers, GPS devices can transmit data practically anywhere. For example, GPS devices may provide location information via one or more wireless networks, such as satellite networks, cellular networks, Wi-Fi networks, and/or other suitable wireless networks. The wireless networks typically provide substantial or even total wireless coverage for the path traversed by a railcar.

A GPS device is separate from the AEI tag. Using both an AEI tag and a separate GPS device may allow for improved tracking of the railcar location, however, this requires managing and coordinating two devices. Additionally, the GPS device does not communicate with the existing AEI network. Certain embodiments of the present disclosure provide a solution to this problem. Certain embodiments combine GPS technology with other low power telecommunication protocols and interoperate with the well-established AEI network, all designed into a wireless device (e.g., a Connected Smartcar Device or “CSD”) as single device hardware that can easily be integrated to existing processes of AEI tag replacement and railcar design going forward.

In certain embodiments, a wireless device attached to a railcar includes functionalities of GPS, communicates to Bluetooth mesh, and is compatible with AEI readers used in the railroad industry. Because the wireless device is compatible with AEI readers, the wireless device may be used as a substitute for existing AEI tags.

Certain embodiments design the wireless device as a Line Replaceable Unit (LRU) to retrofit in the place where AEI tags are placed currently. As an example, when an existing AEI tag is missing or malfunctioning, the AEI tag may be replaced with the wireless device as a new tag for the railcar. Certain embodiments of the wireless device have the capability of transmitting location information (e.g., GPS coordinates) anywhere that there is wireless network coverage, such as satellite, cellular, Wi-Fi, etc. The wireless device may be capable of communicating with Bluetooth, low-power wide area networking (LoRaWan) protocol, Wi-Fi mesh, etc. In certain embodiments, the wireless device may be based on an open source design. In certain embodiments, the wireless device includes AEI RFID technology and uses a communication protocol compatible with existing AEI readers. Like existing AEI tags, the wireless device provides identification information when the railcar passes the AEI readers. In certain embodiments, the AEI tag readers may communicate the identification information received from the wireless device to other components of the AEI system, such as to an operations center configured to manage the identification information received from many AEI readers. In this manner, signals sent by certain embodiments of the wireless device may be formatted to be compatible with existing AEI readers and components upstream of the AEI readers such that information sent by the wireless device may follow the same path as that followed by information sent by AEI tags in existing systems.

In certain embodiments, the wireless device makes real-time data subscriptions available for consumption by the existing AEI architecture. The AEI architecture may subscribe to one or more types of information. Examples of such information include identification information, location information (e.g., GPS latitude/longitude coordinates and timestamp), and sensor information (e.g., temperature inside the railcar, humidity inside the railcar, volume of cargo inside the railcar, weight of cargo inside the railcar, open/closed status of a gate or hatch, equipment status information, etc.).

Certain embodiments of the wireless device provide an interoperable AEI, GPS, sensor hardware, software, and telecommunications system to facilitate automating the on-boarding of railcars and/or providing status updates indicating location, health, and/or condition of the railcar. The status updates may be provided at any time and in any location based on wireless coverage. In addition, certain status updates may be provided to AEI readers, such as providing identification information to the AEI readers passed by the railcar. However, status updates need not be bound to AEI readers. In this manner, certain embodiments leverage all available reporting mechanisms, including reporting via wireless networks and reporting via AEI readers. Certain embodiments may be compatible with Internet of Things (loT) protocols.

FIGURE 1 is a block diagram illustrating an example system 100 according to certain embodiments of the present disclosure. In the example shown in Figure 1, system 100 comprises a railcar 105, at least one wireless device 110, a plurality of AEI readers 120a-n, a plurality of wireless network nodes 130a-n, and a positioning system 140.

In general, railcar 105 may refer to any rail equipment or asset that travels a track. At least one wireless device 110 is mounted on railcar 105. Wireless device 110 is configured to provide status information to a railroad operator via the AEI readers 120 and the wireless network nodes 130. For example, the status information may include identification information that wireless device 110 provides to each AEI reader 120 passed by wireless device 110 as railcar 105 travels the track.

AEI readers 120 may be deployed trackside and spaced along the path of the track, such as at entrances or exits of switchyards. Certain embodiments may deploy one or more AEI readers 120 on a first side of the track (e.g., the left side) and one or more AEI readers 120 on a second side of the track (e.g., the right side). To facilitate communicating with AEI readers 120 deployed on both sides of the track, certain embodiments may mount at least two wireless devices 110 to railcar 105. For example, a first wireless device 110 may be mounted on a first side of railcar 105 to facilitate communication with AEI readers 120 on the first side of the track (e.g., the first wireless device 110 may be mounted on the left side of railcar 105 to facilitate communication with AEI readers 120 on the left side of the track). A second wireless device 110 may be mounted on a second side of railcar 105 to facilitate communication with AEI readers 120 on the second side of the track (e.g., the second wireless device 110 may be mounted on the right side of railcar 105 to facilitate communication with AEI readers 120 on the right side of the track). Note that FIGURE 1 shows one side of railcar 105 such that one wireless device 110 is in view and the other wireless device 110 is out of view (it being understood that the other wireless device 110 may be placed in a similar position on the opposite side of railcar 105). Optionally, some embodiments may mount more than two wireless devices 110 to railcar 105, for example, for redundancy purposes.

Alternatively, other embodiments may mount only one wireless device 110 to railcar 105. As an example, an embodiment may mount wireless device 110 to the first side of railcar 105 and may mount an AEI tag to the second side of the railcar. As another example, an embodiment may rely on communication between wireless device 110 and a wireless network node 130 as a fallback option in the event that wireless device 110 fails to provide status information to an AEI reader 120 (such as when the AEI reader 120 is on the opposite side of the track and out of communication range of wireless device 110). As another example, in certain embodiments, one wireless device 110 may be deployed to communicate with AEI readers 120 on both sides of the track (e.g., by adjusting the position of wireless device 110 on railcar 105, selecting a type of wireless interface for wireless device 110 and AEI readers 120 that facilitates such communication, and/or configuring the wireless interfaces in a manner that facilitates such communication).

The identification information provided to an AEI reader 120 identifies the railcar 105 to which wireless device 110 is mounted. For example, the identification information indicates a car identification number of railcar 105. Wireless devices 110 mounted to the same railcar 105 may be configured with the same identification information for that railcar 105 (e.g., the same car identification number of railcar 105). Certain embodiments of wireless device 110 are compatible with existing AEI readers 120. Thus, wireless device 110 may communicate with AEI readers 120 in accordance with protocols used by existing AEI tags. Wireless device 110 may format the identification information in a manner that enables AEI readers 120 to provide the identification information to other components of the AEI system, such as to an operations center.

In certain embodiments, status information communicated by wireless device 110 further includes location information that wireless device 110 provides to the railroad operator via wireless network nodes 130. Examples of wireless network nodes 130 include satellite nodes, cellular nodes, Wi-Fi nodes, and/or other types of nodes capable of wireless communication with wireless device 110. As further examples, wireless device 110 may be capable of communicating with one or more of the wireless network nodes 130 via Bluetooth, LoRaWan, Wi-Fi mesh, or other suitable protocol. Wireless network nodes 130 are distinct from AEI readers 120. For example, while AEI readers 120 are deployed proximate a railroad track at specific locations, such as switchyards, and have limited range, wireless networks comprising wireless network nodes 130 provide widespread coverage. The wireless networks comprising wireless network nodes 130 may provide substantial or even total wireless coverage for the path traversed by a railcar 105.

Wireless device 110 may obtain or determine the location information based on information received from positioning system 140. As an example, positioning system 140 may comprise a plurality of GPS satellites from which wireless device 110 may obtain GPS coordinates. Wireless device 110 may be configured to communicate the location information to wireless network nodes 130 in any suitable manner. As an example, certain embodiments may communicate the location information periodically (such as every N time units, where N is a number and the time units may be seconds, minutes, or other suitable time unit). A timer may be used to facilitate communicating the location information periodically. For example, expiry of the timer may cause wireless device 110 to communicate the current location information and to reset the timer. As another example, certain embodiments may communicate the location information in response to an event. For example, certain embodiments may communicate the location information in response to the event of receiving a query from wireless network node 130. Certain embodiments may communicate the location information in response to the event of railcar 105 travelling a certain distance (such as every N distance units, where N is a number and the distance units may be meters, yards, kilometers, miles, or other suitable distance). Certain embodiments may communicate the location information in response to the event of railcar 105 entering or exiting a geofence area. As an example, a geofence may provide a virtual geographic boundary (which may be defined by GPS or RFID technology, for example), that enables software to trigger a response when wireless device 110 enters or exits a particular area.

In an embodiment, wireless device 110 detects whether railcar 105 is stationary or in motion. In response to detecting that railcar 105 is in motion, wireless device sends location information based on a pre-determined periodicity. The predetermined periodicity may be static or dynamic. For example, the frequency of reporting may be configured to decrease dynamically if wireless device 110 has low power or poor wireless coverage. In certain embodiments, wireless device 110 accumulates status information over a period of time and uploads the accumulated status information. Certain embodiments report the accumulated status information as a set of separate samples, such as a set of location coordinates and timestamps corresponding to each location. Certain embodiments may configure settings in software, such as middleware, to instruct wireless device 110 when and/or how to report the location information or other status information.

In certain embodiments, status information communicated by wireless device 110 includes sensor information that wireless device 110 provides to the railroad operator via wireless network nodes 130. For example, railcar 105 may be equipped with one or more sensors. Sensors may be configured to sense conditions associated with railcar 105. Examples of conditions may include temperature inside railcar 105, humidity inside railcar 105, volume of cargo inside railcar 105, weight of cargo inside railcar 105, open/closed status of a gate or hatch, equipment status information (such as whether a problem has occurred in a component of railcar 105), and/or other conditions. Certain embodiments may communicate the sensor information to wireless network node 130 periodically. Certain embodiments may communicate the sensor information to wireless network node 130 in response to an event, such as in response to a query from wireless network node 130 or in response to determining that a condition has changed (e.g., gate has gone from closed to open; temperature has increased by N degrees; equipment has changed from a functioning state to a malfunctioning state, etc.). Wireless device 110 may communicate the sensor information to wireless network node 130 together with the location information, or wireless device may communicate the sensor information to wireless network node 130 separately from the location information. For example, certain embodiments use different time periods and/or different events for communicating location information versus sensor information.

One or more wireless devices 110 may be mounted to railcar 105. Certain embodiments mount one or more wireless devices 110 to railcar 105 in place of one or more AEI tags. As an example, two wireless devices 110 may be used in place of two AEI tags. In certain embodiments, wireless device 110 may be an LRU that retrofits in the location of an AEI tag if the AEI tag is missing or malfunctions. Certain embodiments mount two wireless devices 110 on railcar 105, one on each side. The first wireless device 110 communicates with AEI readers 120 positioned on one side of the track (e.g., left side of railcar 105), and the second wireless device 110 communicates with AEI readers 120 on the other side of the track (e.g., right side of railcar 105). In other embodiments, railcar 105 need only include one wireless device 110. To the extent that the single wireless device 110 might be unable to communicate with some of the AEI readers 120 (such as AEI readers 120 on the other side of the track from wireless device 110), wireless device 110 can supplement its location information via communication with wireless network nodes 130. Although the previous examples describe mounting wireless device 110 to railcar 105 in place of an AEI tag, other embodiments may mount wireless device 110 to railcar 105 in addition to an AEI tag.

In certain embodiments, system 100 comprises one or more networks 150. As an example, network 150 may facilitate communication between AEI readers 120 and upstream components of the AEI system, such as an operations center. As another example, network 150 may comprise network infrastructure that supports wireless network nodes 130 (such as any suitable switches, routers, gateways, etc.). In some embodiments, wireless network nodes 130 may report location information and/or status information to an upstream system separate from the AEI system. In other embodiments, network 150 facilitates communicating location information and/or sensor information received by network nodes 130 to upstream components shared by the AEI system. As an example, an operations center may be configured to merge, reconcile, and report the status information received from AEI readers 120 and wireless nodes 13 On. Thus, portions of the AEI network(s) may be separate from portions of the wireless network(s) comprising wireless network nodes 130 and, optionally, certain embodiments may include one or more upstream components to integrate status information received from both the AEI network(s) and the wireless network(s).

Examples of network 150 may comprise all or a portion of one or more of the following: a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network such as the Internet, a wireline or wireless network (including, but not limited to, cellular networks, such as Long Term Evolution (LTE)), an enterprise intranet, other suitable communication link, or any combination of any of the preceding.

Certain embodiments program wireless device 110 with data, such as the railcar identification number. It may receive other information from the airwaves, such as GPS location (e.g., via positioning system 140). This data may be queried when desired via various technologies to extract the information from wireless device 110. When railcar 105 approaches an AEI reader 120, wireless device 110 detects the RF from the AEI reader 120 and transmits the railcar ID and potentially other information back to the AEI reader via RF. FIGURE 2 illustrates an example wireless device 110, according to certain embodiments of the present disclosure. Wireless device 110 may comprise one or more interfaces 112, processing circuitry 114, and memory 116. The one or more interfaces 112, processing circuitry 114, and memory 116 may be housed within the same housing of wireless device 110.

In certain embodiments, the one or more interfaces 112 comprise one or more wireless interfaces configured to send and/or receive wireless signals. Certain embodiments support a protocol for communication with AEI readers 120 (e.g., based on RFID). Certain embodiments support a protocol for communication with wireless network nodes 130, such as a satellite protocol, a cellular protocol, a Wi-Fi protocol, and/or other suitable wireless protocol. Certain embodiments support a protocol for communication with a positioning system 140, such as a protocol for receiving GPS coordinates from a GPS satellite.

Optionally, certain embodiments may further include a port or other interface that facilitates a wired connection, for example, in order to connect with a device that includes a provisioning application that can configure or update the wireless device 110 and/or a diagnostic application that can facilitate detecting a problem if the wireless device 110 malfunctions.

Certain embodiments may comprise one or more interfaces 112 (e.g., wired or wireless) that facilitate communication with one or more other wireless devices 110 (such as another wireless device 110 mounted to the same railcar 105).

Certain embodiments may comprise one or more interfaces 112 (e.g., wired or wireless interfaces) that facilitate communication with a device (such as a gateway) configured to consolidate data from various sources (such as various hardware devices). As examples, a device (such as a gateway) may be configured to provide wireless device 110 with data consolidated from one or more sensors (temperature sensors that indicate temperature inside the railcar, humidity sensors that indicate humidity inside the railcar, cargo volume sensors that indicate a volume of cargo inside the railcar, cargo weight sensors that indicate a weight of cargo inside the railcar, gate open sensors that indicate an open or closed status of a gate, hatch open sensors that indicate an open or closed status of a hatch, equipment sensors that indicate equipment status information, etc.), one or more other wireless devices 110, one or more AEI readers 120, one or more wireless network nodes 130, one or more positioning systems 140 (such as data from GPS), and/or other source(s). In certain embodiments, the device (such as a gateway) may be deployed on or in railcar 105.

Interface 112 receives input, sends output, processes the input and/or output, and/or performs other suitable operation. Interface 112 may comprise hardware and/or software. As an example of an input, interface 112 may be configured to receive identification information associated with railcar 105. The identification information may be received when provisioning wireless device 110 to be mounted to railcar 105. As another example of an input, interface 112 may be configured to receive location information from positioning system 140. As another example of an input, interface 112 may be configured to receive sensor information from one or more sensors associated with railcar 105. As another example of an input, interface 112 may be configured to receive queries from AEI readers 120 and/or wireless network nodes 130 requesting status information (e.g., the identification information, location information, and/or sensor information). Examples of the output may include the status information (e.g., the identification information, location information, and/or sensor information. Wireless device 110 may send the output in response to a query and/or based on logic executed by wireless device 110.

Processing circuitry 114 may include any suitable combination of hardware and software implemented in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of wireless device 110. In some embodiments, processing circuitry 114 may include, for example, one or more processors, one or more microprocessors, one or more applications, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs), and/or other logic. Certain embodiments include both logic configured to perform AEI functionality and logic to perform GPS functionality. Certain embodiments may include further logic to determine and provide sensor information.

In certain embodiments, processing circuitry 114 may comprise a management module, an identification module, a location module, and/or a sensor module. The management module may be configured to manage operations of processing circuitry 114. For example, the management module may manage interoperability among the other modules. The identification module may be configured to determine the identification information (e.g., based on reading from memory 116) and provide the identification information to AEI reader 120. Thus, certain embodiments configure the identification module to use an AEI protocol. In certain embodiments, the identification module may include a passive RFID. The location module may be configured to determine location information (e.g., based on input from positioning system 140) and to provide the location information to wireless network node 130. Certain embodiments configure location module to use a GPS protocol. The sensor module may be configured to determine sensor information (e.g., based on input from one or more sensors associated with railcar 105) and to provide the sensor information to wireless network node 130.

Memory (or memory unit) 116 stores information. As an example, memory 116 may store identification information, location information, and/or sensor information. Wireless device 110 may use the stored information to communicate information about the status of railcar 105 to AEI reader 120 and/or wireless network node 130. As another example, memory 116 may store logic for performing any of the methods described herein as being performed by wireless device 110. Memory 116 may comprise one or more non-transitory, tangible, computer-readable, and/or computer-executable storage media. Examples of memory 116 include computer memory, such as Random Access Memory (RAM) or Read Only Memory (ROM), and/or other computer-readable medium. In certain embodiments, memory 116 may be embodied on an integrated circuit, such as semiconductor memory using metal- oxide-semiconductor (MOS) technology, examples of which include static RAM (SRAM), dynamic RAM (DRAM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), and flash memory.

As described above, certain embodiments combine AEI reporting and other status reporting (location information and/or sensor information) housed together in the same hardware. Software interoperability is provided, which may be managed by the management module in certain embodiments. As an example of interoperability, certain embodiments determine whether to provide location information to a wireless network node 130 based on whether railcar 105 has recently passed an AEI reader 120. If the railcar 105 has recently passed an AEI reader 120, wireless device 110 may determine that the operator has up-to-date location information (based on mapping the railcar to the location of the AEI reader 120) and may wait to send location information to wireless network node 130 until some time period has elapsed or other event has occurred to cause wireless device 110 to report to wireless network node 130. In some cases a railcar 105 may pass an AEI reader 120 without the AEI reader 120 being able to successfully read the identification information from wireless device 110. For example, if railcar 105 takes a middle track in a track location with multiple tracks, such as a triple track location or quad-track location, the AEI reader 120 may be unable to read wireless device 110. Certain embodiments map the location of the AEI reader 120 to a geofence location. If wireless device 110 determines that it has exited the geofence location without providing identification information to AEI reader 120, wireless device 110 may determine to push location information to wireless network node 130. Otherwise, if wireless device 110 determines that the identification information was provided to AEI reader 120, wireless 110 need not push the location information to wireless network node 130 when wireless device 110 exits the geofence location associated with AEI reader 120.

FIGURE 3 is a flow chart illustrating a method 300 according to certain embodiments of the present disclosure. Method 300 may be performed by a wireless device 110 coupled to a railcar 105. The railcar 105 is associated with identification information that indicates an identity of the railcar 105, such as a car identification number. In certain embodiments, wireless device 110 comprises processing circuitry 114 and memory 116. An example of memory 116 includes one or more computer- readable non-transitory storage media. Memory 116 comprises instructions that, when executed by the processing circuitry 114, causes one or more components of wireless device 110 to perform method 300.

Method 300 begins at step 302 with storing identification information associated with a railcar 105 in memory 116 of the wireless device 110. Method 300 proceeds to step 304 with receiving a signal from a positioning system 140 and then to step 306 with determining location information associated with the railcar 105 based on the signal received from the positioning system 140.

Method 300 continues with providing first status information to one or more trackside AEI readers 120, as shown in step 308. The first status information comprises identification information associated with the railcar 105. For example, wireless device 110 obtains the identification information that was stored in memory 116 in step 302 and provides the identification information to the one or more AEI readers 120. Optionally, in certain embodiments, the first status information may further include the location information, such as when AEI readers 120 support reading the location information. Alternatively, the first status information need not include the location information when communicating with legacy AEI readers 120 that do not support reading the location information.

Method 300 further comprises providing second status information to one or more wireless network nodes 130, as shown in step 310. The second status information comprises the location information determined in step 306. In certain embodiments, providing the second status information in step 310 may be performed according to method 500 of FIGURE 5, method 600 of FIGURE 6, or method 700 of FIGURE 7. Optionally, in certain embodiments, the second status information may further include the identification information.

Certain embodiments of method 300 may further comprise including sensor information with the first status information and/or the second status information provided by the wireless device 110, for example, as described with respect to method 800 of FIGURE 8. Certain embodiments may format the first status information for compatibility with legacy AEI readers 120. For example, the first status information may be formatted so that legacy AEI readers 120 can read the identification information and ignore information not supported by the legacy AEI readers 120, such as location information or sensor information. The first status information may be formatted so that an upgraded AEI reader 120 can read the identification information and the additional information (e.g., location information and/or sensor information).

Method 300 may be modified to support any of the features of wireless device 110 described with respect to any of the other figures.

FIGURE 4 is a flow chart illustrating a method 400 according to certain embodiments of the present disclosure. Method 400 begins at step 402 with installing wireless device 110 onto railcar 105. Method 400 proceeds to step 404 with programming wireless device 110. For example, wireless device 110 may be programmed with identification information (e.g., railcar ID) for railcar 105. Other data may be programmed onto wireless device 110. Method 400 proceeds to step 406 with wireless device 110 receiving GPS data and other data (e.g., sensor information). Certain embodiments confirm that provisioning of wireless device 110 has completed successfully based at least in part on wireless device 110 receiving the GPS data and other data. Once provisioning of wireless device 110 has completed successfully, railcar 105 may be put into service. With railcar 105 in service, method 400 may proceed to step 408 where wireless device 110 may be queried for data and may transmit data in response to the query. For example, when wireless device 110 detects a query from AEI reader 120, wireless device 110 may respond with at least the identification information. Optionally, certain embodiments may configure AEI reader 120 to support receiving other types of information from wireless device 110, such as location information, location history, sensor information, or sensor history. In such embodiments, wireless device 110 may also provide this information in response to the query from AEI reader 120. As another example, when wireless device 110 detects a query from wireless network node 130, wireless device 110 may respond with status information (e.g., identification information, location information, and/or sensor information). In addition, or in the alternative, wireless device 110 may be configured to communicate status information to wireless network node 130 based on a time period or based on the occurrence of an event (such as a change in location information or a change in sensor information).

In certain embodiments, a computer application may be configured to perform one or more of the steps for provisioning/onboarding wireless device 110. The computer application may manage the workflow of registering wireless device 110 and associating wireless device 110 with a railcar 105 so that an operator does not have to manually update the railroad database, which can be time-consuming and error prone. The computer application may read a pairing between wireless device 110 and railcar 105 and register the pairing in the railroad database.

FIGURE 5 is a flow chart illustrating a method 500 according to certain embodiments of the present disclosure. Method 500 may be performed by a wireless device 110. Method 500 beings at step 502 with determining whether the railcar 105 to which wireless device 110 is mounted is stationary or in motion. In response to determining at step 502 that railcar 105 is in motion, method 500 proceeds to step 504 with providing the location information to the one or more wireless network nodes 130 based on a pre-determined periodicity. For example, while in motion, wireless device 110 may provide the location information to the one or more wireless network nodes 130 every N time units. The value of N may be static or may be determined dynamically. For example, the value of N may be adjusted based on power conditions (e.g., report less frequently when wireless device 110 has low power) and/or wireless coverage conditions (e.g., report less frequently when wireless device 110 has poor wireless coverage). In certain embodiments, wireless device 110 may skip a reporting to the one or more wireless nodes 130 if wireless device 110 has an upcoming opportunity to provide or has recently provided status information via an AEI reader 120, such as described with respect to method 600 of FIGURE 6 or method 700 of FIGURE 7. For example, system 100 may already know a recent location of the railcar 105 based on a recent reporting to AEI reader 120 such that it may be unnecessary to report the location to a wireless network node 130 until a certain amount of time has elapsed/until the railcar 105 has moved to a different location. Or, wireless device 110 may be within close enough proximity to an upcoming AEI reader 120 (e.g., based on distance from the AEI reader 120 or based on estimated time to arrive at the AEI reader 120 given the speed of railcar 105) that certain embodiments may skip a reporting to the one or more wireless nodes 130 and may instead report to the AEI reader 120.

The location information provided to the one or more wireless network nodes 130 in step 504 may include current location information and/or location information that has accumulated since the last reporting time. For example, the accumulated location information may include a plurality of GPS latitude/longitude coordinates and corresponding timestamps indicating when railcar 105 was in a particular location.

In response to determining at step 502 that railcar 105 is stationary, method 500 abstains from providing the location information to the one or more wireless network nodes 130, as shown in step 506.

Certain embodiments may return to step 502 in order to continue/resume sending location information to the one or more wireless network nodes 130 while railcar 105 is in motion and to avoid/stop sending location information to the one or more wireless network nodes 130 while railcar 105 is stationary.

FIGURE 6 is a flow chart illustrating a method 600 according to certain embodiments of the present disclosure. Method 600 may be performed by a wireless device 110. For example, wireless device 110 may perform method 600 in order to determine when to provide the location information to the one or more wireless network nodes 130 based at least in part on a proximity of the railcar 105 to one of the AEI readers 120.

Method 600 beings at step 602 with determining the proximity of the railcar 105 to one of the AEI readers 120. The proximity is determined based on a geofence region associated with the AEI reader 120. For example, the AEI reader 120 may be located in a switchyard, and the geofence region may be configured to indicate when the railcar 105 exits the switchyard.

In response to exiting the geofence region, method 600 continues to step 604 with determining whether the status information was provided to the AEI reader 120 associated with the geofence region. Continuing with the example, method 600 determines whether the AEI reader 120 located in the switchyard read the identification information from the wireless device 110. If the AEI reader 120 has read the identification information, system 100 may have already received an up-to- date location for the railcar 105 based on mapping the location of the railcar 105 to the location of the AEI reader 120. If the AEI reader 120 was unable to read the identification information (for example, if signals between the AEI reader 120 and the wireless device 110 were blocked by another railcar 105), system 100 might not have received an up-to-date location for the railcar 105.

In response to determining at step 604 that the status information was not provided to the AEI reader 120 associated with the geofence region, method 600 proceeds to step 606 with providing the location information to the one or more wireless network nodes 130. In this manner, system 100 can obtain the location of the railcar 105 via a wireless network in scenarios where the AEI reader 120 is unable to read wireless device 110.

In response to determining at step 604 that the status information was provided to the AEI reader 120, method 600 proceeds to step 608 with waiting to provide the location information to the one or more wireless network nodes 130. For example, wireless device 110 may wait for a pre-determined time period, such as N time units (e.g., seconds, minutes, or other time unit) before providing the location information to a wireless network node 130. As another example, wireless device 110 may wait until railcar 105 has moved at least N distance units (e.g., meters, yards, kilometers, miles, or other distance unit) away from the geofence region associated with AEI reader 120 before providing the location information to a wireless network node 130.

Similarly, certain embodiments may determine whether to send the location information to a wireless network node 130 based on whether the railcar 105 is entering a geofence region. As an example, a geofence region may be established proximate the AEI reader 120. If wireless device 110 detects that it is entering the geofence region, the wireless device 110 may recognize that it will soon have an opportunity to send status information to the AEI reader 120. Thus, wireless device 110 may hold off on sending the location information to the wireless network node 130 while it attempts to send the status information to the AEI reader 120. Wireless device 110 may then proceed with the steps of method 600 to determine whether to send the location information to the wireless network node 130 based on whether it was able to send the status information to the AEI reader 120.

Thus, method 600 allows for using the AEI reader 120 to determine a location of the railcar 105 when the railcar 105 is within a pre-determined proximity of the AEI reader 120 and for using a wireless network node 130 to determine a location of the railcar 105 when the railcar 105 is outside the pre-determined proximity of the AEI reader 120. The proximity of the railcar 105 to the AEI reader 120 may be based on distance or based on time. As an example, the railcar 105 may be within proximity of the AEI reader 120 if the railcar 105 is scheduled to reach the AEI reader 120 within a certain distance or if it recently passed the AEI reader 120 within a certain distance. As another example, the railcar 105 may be within proximity of the AEI reader 120 if the railcar 105 is scheduled to reach the AEI reader 120 within a certain amount of time or if less than a certain amount of time has elapsed since the most recent reporting to the AEI reader 120.

FIGURE 7 is a flow chart illustrating a method 700 according to certain embodiments of the present disclosure. Method 700 may be performed by a wireless device 110. Method 700 begins at step 702 with providing identification information to an AEI reader 120 at a first time. Method 700 proceeds to step 704 with determining whether to provide location information to a wireless network node 130 at a second time. The determination is based on whether the second time is within a pre-determined time period of the first time.

In response to determining at step 704 that the second time is within the predetermined time period of the first time, the wireless device 110 is configured to proceed to step 706 where the wireless device 110 waits to provide the location information to the wireless network node 130.

In response to determining at step 704 that the second time is outside the predetermined time period of the first time, the wireless device 110 is configured to proceed to step 708 where the wireless device 110 provides the location information to the wireless network node 130 at the second time.

In this manner, wireless device 110 may avoid consuming power and/or network bandwidth associated with reporting location information to the wireless network node 130 in scenarios where system 100 already knows a recent location of the railcar 105 based on reporting to the AEI reader 120. However, wireless device 110 may ensure that system 100 receives location information in scenarios where wireless device 110 has not recently reported status information to any AEI reader 120 (or to any wireless network node 130).

FIGURE 8 is a flow chart illustrating a method 800 according to certain embodiments of the present disclosure. Method 800 may be performed by a wireless device 110. Method 800 begins at step 802 with receiving one or more signals from one or more sensors coupled to railcar 105 or to cargo of railcar 105. Examples of sensors may include one or more of temperature sensors that indicate temperature inside the railcar, humidity sensors that indicate humidity inside the railcar, cargo volume sensors that indicate a volume of cargo inside the railcar, cargo weight sensors that indicate a weight of cargo inside the railcar, gate open sensors that indicate an open or closed status of a gate, hatch open sensors that indicate an open or closed status of a hatch, equipment sensors that indicate equipment status information, etc. Method 800 proceeds to step 804 with determining sensor information based on the one or more signals. Determining sensor information may include any suitable steps, such as extracting the sensor information from the signals, calculating sensor information based on data received in the signals, formatting the data received in the signals according to a format for providing the sensor information to a wireless network node 130 or to an AEI reader 120, and/or other suitable steps. The method proceeds to step 806 with including the sensor information in the status information provided to the wireless network node 130 or to the AEI reader 120.

As described above, for example, with respect to FIGURE 1, certain embodiments may mount two or more wireless devices 110 on railcar 105. As an example, a first wireless device 110 may be mounted on the left side of the railcar to facilitate communication with AEI readers 120 on the left side of the track, and a second wireless device 110 may be mounted on the right side of the railcar to facilitate communication with AEI readers 120 on the right side of the track. Optionally, each wireless device 110 may be configured with a unique wireless device identifier, for example, to facilitate communication with a particular wireless device 110, to distinguish status information provided by the first wireless device 110 from status information provided by the second wireless device 110, and/or for other suitable purposes. As described above, two or more wireless devices 110 mounted to the same railcar 105 may be configured with the same identification information for the railcar 105 (e.g., the same car identification number).

In certain embodiments, the first wireless device 110 and the second wireless device 110 may function independently of each other. For example, each wireless device 110 may be configured to perform the methods described herein. In this manner, an operations center (or other destination for the status information) may receive some duplicate information, for example, due to the first wireless device 110 and the second wireless device 110 both providing status information via wireless network nodes 130. System 100 may be configured to combine, consolidate, filter, de-duplicate, and/or otherwise process the status information in any suitable manner. Embodiments where the first wireless device 110 and the second wireless device 110 provide duplicate status information may provide redundancy for the status information in case one of the wireless devices 110 malfunctions or misses a reporting opportunity. Additionally, embodiments where the first wireless device 110 and the second wireless device 110 provide duplicate status information may facilitate detecting a malfunctioning wireless device 110, for example, if the status information provided by the wireless device 110 is inconsistent with the status information provided by another wireless device 110 mounted to the same railcar 105. Examples of inconsistent status information may include unexpected gaps in status information or differences in status information (e.g., beyond an acceptable tolerance).

Alternatively, in certain embodiments, the first wireless device 110 and the second wireless device 110 mounted to the same railcar 105 may be configured to avoid sending duplicate information. This approach may reduce overhead and conserve system resources (such as processing resources and network bandwidth that would otherwise be required to handle duplicate information). As an example, one wireless device 110 may be configured as a primary device and the other wireless device 110 may be configured as a secondary device. The primary device may be configured to have primary responsibility for providing status information, and the secondary device may be configured to only provide the status information that the primary device does not provide (e.g., based on configuration or capabilities of the primary device and/or the secondary device, based on current conditions, such as wireless signal interference levels, etc.). As an example, the secondary device may be configured to communicate with AEI readers 120 on the side of the track that is beyond the communication range of the primary device and/or to perform other functionality that the primary device is unable to perform.

Optionally, certain embodiments may configure the primary/secondary designation based on the type of status information (e.g., the first wireless device 110 may be the primary device with respect to sending location information to wireless network node 130, and the second wireless device 110 may be the primary device with respect to sending sensor information to the wireless network node 130). Certain embodiments may switchover the primary/secondary designation, for example, in response to an event (e.g., if the primary device malfunctions, the secondary device may takeover the primary designation).

In certain embodiments, the first wireless device 110 and the second wireless device 110 mounted to the same railcar 105 may be configured to communicate with each other in order to determine which wireless device 110 provides certain status information or to otherwise operate in a coordinated manner. Communication between wireless devices 110 may be direct (e.g., via a wired or wireless connection) or indirect. In certain embodiments, railcar 105 may be configured with a device (such as a gateway) that facilitates coordinating which wireless device 110 provides certain status information. As one example, the device (such as a gateway )_may be configured to consolidate data from various sources (e.g., one or more sensors, one or more wireless devices 110, one or more AEI readers 120, one or more wireless network nodes 130, one or more positioning systems 140 (such as data from GPS), and/or other source(s)). In certain embodiments, the device (such as a gateway) may select one of multiple wireless devices 110 mounted to railcar 105 to provide certain consolidated data to AEI readers 120 and/or to wireless network nodes 130. The device may select the wireless device 110 based on any suitable criteria, such as availability, capabilities, and/or configuration settings (such as primary/secondary designation) of the wireless device 110, one or more rules (such as load-balancing rules), and/or other suitable criteria.

The methods described herein may be performed by two wireless devices 110 mounted to the same railcar 105 and operating in a coordinated manner. As examples:

• In FIGURE 3, step 308, the first wireless device 110 may provide the first status information (e.g., identification information associated with the railcar) to AEI readers 120 on one side of the track, and the second wireless device 110 may provide the first status information (e.g., identification information associated with the railcar) to AEI readers 120 on the other side of the track. In an embodiment of step 310, the first wireless device 110 has primary responsibility for providing the second status information (e.g., location information or sensor information) to one or more wireless network nodes 130. The second wireless device 110 may be configured to provide the second status information to the one or more wireless network nodes 130 in the event that the first wireless device 110 cannot do so. As an example, the second wireless device 110 may receive a message from the first wireless device 110 or the wireless network node 130 indicating that the first wireless device 110 cannot provide/has failed to provide the second status information. As another example, the second wireless device 110 may determine to provide the second status information if a pre-determined time period has elapsed or a predetermined number of reporting opportunities or events have passed without the first wireless device 110 providing the second status information.

• In FIGURE 5, method 500 may be configured such the wireless device 110 further abstains from providing the location information, for example, in response to determining that another wireless device 110 mounted to the same railcar 105 has primary responsibility to provide the location information and/or that the other wireless device 110 has already provided the location information for the current reporting period.

• In FIGURE 6, certain embodiments of step 604 determine that the status information has been provided to the AEI reader 120 prior to exiting the geofence region if either the wireless device 110 itself or another wireless device 110 mounted to the same railcar 105 provided the status information to the AEI reader 120. In this manner, even if the wireless device 110 did not itself provide the status information to the AEI reader 120 at step 604, the method would still proceed to step 608 (wait to provide location information to the wireless network node 130) based on the other wireless device 110 mounted to the same railcar 105 having provided the status information to the AEI reader 120.

• In FIGURE 7, certain embodiments of step 702 determine that the identification information has been provided to the AEI reader 120 at the first time if either the wireless device 110 itself or another wireless device 110 mounted to the same railcar 105 provided the identification information to the AEI reader 120 at the first time. In certain embodiments, step 704 may be performed by the wireless device 110 currently designated as the primary device (e.g., the primary device may determine whether to provide location information to a wireless network node 130 at a second time based on whether the second time is within a pre-determined time period of the first time). The wireless device 110 currently designated as the secondary device may abstain from providing location information at the second time based on the primary device being responsible for performing step 704 and the applicable next step (step 706 or step 708, depending on the result of step 704).

• In FIGURE 8, in certain embodiments, a wireless device 110 may determine whether to provide the sensor information to the wireless network node(s) 130 based at least in part on determining whether another wireless device 110 mounted to the same railcar 105 has primary responsibility to provide the sensor information and/or whether the other wireless device 110 has already provided the wireless network node(s) 130 with the sensor information for a particular event (such as an event indicating a timer expiry for a current reporting period, an event indicating a status change for a sensor, etc.).

Other embodiments may coordinate operations of two wireless devices 110 mounted to the same railcar 105 in any suitable manner.

Certain embodiments allow for the automatic update of equipment management and reporting tools (such as Umler tools). Certain embodiments use a single reporting stream for status information received via both the AEI readers 120 and the wireless network nodes 130. Certain embodiments use the existing AEI system to facilitate updating the equipment management and reporting tools. Certain embodiments may allow for the reuse of existing AEI systems (without requiring changes or additions to capabilities). For example, the existing AEI system can read the wireless device 110 as it would an existing AEI tag. The wireless device 110 may combine AEI tag circuitry to provide the identification information to AEI readers 120 with additional circuitry that reports to a separate system (via wireless network nodes 130) to provide the location information and/or sensor information. Combining the AEI circuitry and the additional circuitry permits enhanced capabilities and efficiency, enabling future developments to the existing AEI system not possible with separate but connected systems, while allowing a way of maintaining compatibility with the existing AEI system, if needed. Certain embodiments move from a one-way communication system (traditional AEI system) to a two-way communication system capable of exchanging much more information through the AEI system. Further, this information is more easily customizable as electronics and railcar sensor technology evolves. This is more efficient than existing systems that necessarily must use a separate path for other railcar information instead of using and building upon the existing AEI infrastructure.

Modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.

Claims

1. A system (100), the system comprising: a railcar (105), the railcar configured to travel a track, the railcar associated with identification information that indicates an identity of the railcar; and a wireless device (110) coupled to the railcar, the wireless device comprising: memory (116) configured to store the identification information associated with the railcar; and processing circuitry (114), the processing circuitry configured to provide status information to one or more trackside automatic equipment identification (AEI) readers (120) and to one or more wireless network nodes (130), wherein the status information that the processing circuitry is configured to provide to the one or more trackside AEI readers comprises the identification information associated with the railcar.

2. The system of Claim 1, the wireless device further configured to: receive a signal from a positioning system (140); and determine location information associated with the railcar based on the signal received from the positioning system; wherein the status information that the processing circuitry is configured to provide to the one or more wireless network nodes comprises the location information.

3. The system of Claim 2, the wireless device further configured to: determine whether the railcar is stationary or in motion; while the railcar is in motion, provide the location information to the one or more wireless network nodes based at least in part on a pre-determined periodicity; and while the railcar is stationary, abstain from providing the location information to the one or more wireless network nodes.

4. The system of any of Claims 2-3, wherein the wireless device is further configured to determine when to provide the location information to the one or more wireless network nodes based at least in part on a proximity of the railcar to one of the trackside AEI readers.

5. The system of Claim 4, wherein the wireless device is configured to: determine the proximity of the railcar to the one of the trackside AEI readers based on a geofence region associated with the one of the trackside AEI readers; in response to exiting the geofence region, determine whether the status information was provided to the one of the trackside AEI readers associated with the geofence region; and in response to determining that the status information was not provided to the one of the trackside AEI readers associated with the geofence region, provide the location information to the one or more wireless network nodes.

6. The system of any of Claims 2-5, wherein the wireless device is configured to: provide the identification information to one of the trackside AEI readers at a first time; and determine whether to provide the location information to the one or more wireless network nodes at a second time based on whether the second time is within a pre-determined time period of the first time; wherein, in response to determining that the second time is within the predetermined time period of the first time, the wireless device is configured to wait to provide the location information to the one or more wireless network nodes, and in response to determining that the second time is outside the pre-determined time period of the first time, the wireless device is configured to provide the location information to the one or more wireless network nodes at the second time.

7. The system of any of Claims 1-6, wherein the system further comprises one or more sensors coupled to the railcar or to cargo of the railcar, and wherein the wireless device is further configured to: receive one or more signals from the one or more sensors; and determine sensor information based on the one or more signals; wherein the status information that the processing circuitry is configured to provide to the one or more wireless network nodes comprises the sensor information.

8. The system of any of Claims 1-7, wherein the status information that the processing circuitry is configured to provide to the one or more trackside AEI readers further comprises location information and/or sensor information.

9. The system of any of Claims 1-8, wherein the system comprises a second wireless device coupled to the railcar.

10. The system of Claim 9, wherein the processing circuitry is configured to determine the status information to provide to the one or more trackside AEI readers or to the one or more wireless network nodes based at least in part on information that facilitates coordination with the second wireless device coupled to the railcar.

11. A method performed by a wireless device, the method comprising: storing (302) identification information associated with a railcar in memory of the wireless device; receiving (304) a signal from a positioning system; determining (306) location information associated with the railcar based on the signal received from the positioning system; providing (308) first status information to one or more trackside automatic equipment identification (AEI) readers, the first status information comprising the identification information associated with the railcar; and providing (310) second status information to one or more wireless network nodes, the second status information comprising the location information associated with the railcar.

12. The method of Claim 11, further comprising: determining (502) whether the railcar is stationary or in motion; while the railcar is in motion, providing (504) the location information to the one or more wireless network nodes based at least in part on a pre-determined periodicity; and while the railcar is stationary, abstaining (506) from providing the location information to the one or more wireless network nodes.

13. The method of any of Claims 11-12, wherein the method further comprises determining when to provide the location information to the one or more wireless network nodes based at least in part on a proximity of the railcar to one of the trackside AEI readers.

14. The method of any of Claims 11-13, further comprising: providing (702) the identification information to one of the trackside AEI readers at a first time; and determining (704) whether to provide the location information to the one or more wireless network nodes at a second time based on whether the second time is within a pre-determined time period of the first time; wherein, in response to determining that the second time is within the predetermined time period of the first time, the method comprises waiting (706) to provide the location information to the one or more wireless network nodes, and in response to determining that the second time is outside the pre-determined time period of the first time, the method comprises providing (708) the location information to the one or more wireless network nodes at the second time.

15. The method of any of Claims 11-14, further comprising: receiving (802) one or more signals from one or more sensors coupled to the railcar or to cargo of the railcar; determining (804) sensor information based on the one or more signals; and including (806) the sensor information in the second status information.

16. One or more computer-readable non-transitory storage media embodying instructions that, when executed by processing circuitry of a wireless device, cause the performance of operations comprising: storing identification information associated with a railcar in memory of the wireless device; receiving a signal from a positioning system; determining location information associated with the railcar based on the signal received from the positioning system; providing first status information to one or more trackside automatic equipment identification (AEI) readers, the first status information comprising the identification information associated with the railcar; and providing second status information to one or more wireless network nodes, the second status information comprising the location information associated with the railcar.

17. The one or more computer-readable non-transitory storage media of Claim 16, the operations further comprising: determining whether the railcar is stationary or in motion; while the railcar is in motion, providing the location information to the one or more wireless network nodes based at least in part on a pre-determined periodicity; and while the railcar is stationary, abstaining from providing the location information to the one or more wireless network nodes.

18. The one or more computer-readable non-transitory storage media of any of Claims 16-17, wherein the operations further comprise determining when to provide the location information to the one or more wireless network nodes based at least in part on a proximity of the railcar to one of the trackside AEI readers.

19. The one or more computer-readable non-transitory storage media of any of Claims 16-8, the operations further comprising: providing the identification information to one of the trackside AEI readers at a first time; and determining whether to provide the location information to the one or more wireless network nodes at a second time based on whether the second time is within a pre-determined time period of the first time; wherein, in response to determining that the second time is within the predetermined time period of the first time, the operations comprise waiting to provide the location information to the one or more wireless network nodes, and in response to determining that the second time is outside the pre-determined time period of the first time, the operations comprise providing the location information to the one or more wireless network nodes at the second time.

20. The one or more computer-readable non-transitory storage media of any of Claims 16-19, the operations further comprising: receiving one or more signals from one or more sensors coupled to the railcar or to cargo of the railcar; determining sensor information based on the one or more signals; and including the sensor information in the second status information; wherein at least one of the one or more sensors comprises a temperature sensor, a humidity sensor, a cargo volume sensor, a cargo weight sensor, a gate open sensor, or a hatch open sensor.