SYSTEMS AND METHODS FOR REMOTE ACTIVATION OF RAILROAD CROSSING SIGNALS

Abstract

A method for the remote activation of railroad crossing signals includes determining a physical location of a client system. The method further includes determining, from a plurality of records of railroad crossing signals, an eligible railroad crossing signal that is within a predetermined distance of the physical location of the client system. The method further includes sending identification information about the eligible railroad crossing signal to the client system. The method further includes receiving, from the client system, an indication of a user selection to activate the eligible railroad crossing signal. The method further includes sending an activation signal to the eligible railroad crossing signal in response to receiving the indication of the user selection to activate the eligible railroad crossing signal.

Claims

1. A railroad crossing signal activation system comprising: one or more memory units configured to store a plurality of records of railroad crossing signals; and one or more computer processors communicatively coupled to the one or more memory units and configured to: determine a physical location of a client system; determine, from the plurality of records of railroad crossing signals, an eligible railroad crossing signal that is within a predetermined distance of the physical location of the client system; send identification information about the eligible railroad crossing signal to the client system; receive, from the client system, an indication of a user selection to activate the eligible railroad crossing signal; and send an activation signal to the eligible railroad crossing signal in response to receiving the indication of the user selection to activate the eligible railroad crossing signal.

2. The system of claim 1, wherein the one or more computer processors are further configured to: continuously monitor a current physical location of the client system after sending the activation signal to the eligible railroad crossing signal; and send a deactivation signal to the eligible railroad crossing signal when a distance between the eligible railroad crossing signal and the current physical location of the client system exceeds the predetermined distance.

3. The system of claim 1, wherein the one or more computer processors are further configured to: start a first timer upon sending the activation signal to the eligible railroad crossing signal; upon expiration of the first timer: start a second timer; send one or more instructions to display a deactivation user interface on the client system, the deactivation user interface comprising: a first user-selectable element configured to continue activation of the eligible railroad crossing signal; a second user-selectable element configured to deactivate the eligible railroad crossing signal; and a visual indication of the second timer; send a deactivation signal to the eligible railroad crossing signal upon expiration of the second timer; send the deactivation signal to the eligible railroad crossing signal upon receiving an indication of selection of the second user-selectable element; and restart the first timer upon receiving an indication of selection of the first user-selectable element.

4. The system of claim 1, wherein the one or more computer processors are further configured to: determine, from the plurality of records of railroad crossing signals, that no railroad crossing signals are within the predetermined distance of the physical location of the client system; and in response to determining that no railroad crossing signals are within the predetermined distance of the physical location of the client system, send one or more instructions to display a message on the client system, the message indicating that no eligible railroad crossing signals are within range of the client system.

5. The system of claim 1, wherein the physical location of the client system comprises latitude and longitude coordinates from a Global Positioning System (GPS) unit in the client system.

6. The system of claim 5, wherein determining the eligible railroad crossing signal that is within the predetermined distance of the physical location of the client system comprises comparing latitude and longitude coordinates stored in each of the plurality of records of railroad crossing signals to the latitude and longitude coordinates of the client system.

7. The system of claim 1, wherein the identification information about the eligible railroad crossing signal comprises one or more of: a street name associated with the eligible railroad crossing signal; a Department of Transportation (DOT) identification number of the eligible railroad crossing signal; and a unique asset identification number of the eligible railroad crossing signal.

8. A method by a computing system for the remote activation of railroad crossing signals, the method comprising: determining a physical location of a client system; determining, from a plurality of records of railroad crossing signals, an eligible railroad crossing signal that is within a predetermined distance of the physical location of the client system; sending identification information about the eligible railroad crossing signal to the client system; receiving, from the client system, an indication of a user selection to activate the eligible railroad crossing signal; and sending an activation signal to the eligible railroad crossing signal in response to receiving the indication of the user selection to activate the eligible railroad crossing signal.

9. The method of claim 8, further comprising: continuously monitoring a current physical location of the client system after sending the activation signal to the eligible railroad crossing signal; and sending a deactivation signal to the eligible railroad crossing signal when a distance between the eligible railroad crossing signal and the current physical location of the client system exceeds the predetermined distance.

10. The method of claim 8, further comprising: starting a first timer upon sending the activation signal to the eligible railroad crossing signal; upon expiration of the first timer: starting a second timer; sending one or more instructions to display a deactivation user interface on the client system, the deactivation user interface comprising: a first user-selectable element configured to continue activation of the eligible railroad crossing signal; a second user-selectable element configured to deactivate the eligible railroad crossing signal; and a visual indication of the second timer; sending a deactivation signal to the eligible railroad crossing signal upon expiration of the second timer; sending the deactivation signal to the eligible railroad crossing signal upon receiving an indication of selection of the second user-selectable element; and restarting the first timer upon receiving an indication of selection of the first user-selectable element.

11. The method of claim 8, further comprising: determining, from the plurality of records of railroad crossing signals, that no railroad crossing signals are within the predetermined distance of the physical location of the client system; and in response to determining that no railroad crossing signals are within the predetermined distance of the physical location of the client system, sending one or more instructions to display a message on the client system, the message indicating that no eligible railroad crossing signals are within range of the client system.

12. The method of claim 8, wherein the physical location of the client system comprises latitude and longitude coordinates from a Global Positioning System (GPS) unit in the client system.

13. The method of claim 12, wherein determining the eligible railroad crossing signal that is within the predetermined distance of the physical location of the client system comprises comparing latitude and longitude coordinates stored in each of the plurality of records of railroad crossing signals to the latitude and longitude coordinates of the client system.

14. The method of claim 8, wherein the identification information about the eligible railroad crossing signal comprises one or more of: a street name associated with the eligible railroad crossing signal; a Department of Transportation (DOT) identification number of the eligible railroad crossing signal; and a unique asset identification number of the eligible railroad crossing signal.

15. One or more computer-readable non-transitory storage media embodying instructions that, when executed by a processor, cause the processor to perform operations comprising: determining a physical location of a client system; determining, from a plurality of records of railroad crossing signals, an eligible railroad crossing signal that is within a predetermined distance of the physical location of the client system; sending identification information about the eligible railroad crossing signal to the client system; receiving, from the client system, an indication of a user selection to activate the eligible railroad crossing signal; and sending an activation signal to the eligible railroad crossing signal in response to receiving the indication of the user selection to activate the eligible railroad crossing signal.

16. The one or more computer-readable non-transitory storage media of claim 15, the operations further comprising: continuously monitoring a current physical location of the client system after sending the activation signal to the eligible railroad crossing signal; and sending a deactivation signal to the eligible railroad crossing signal when a distance between the eligible railroad crossing signal and the current physical location of the client system exceeds the predetermined distance.

17. The one or more computer-readable non-transitory storage media of claim 15, the operations further comprising: starting a first timer upon sending the activation signal to the eligible railroad crossing signal; upon expiration of the first timer: starting a second timer; sending one or more instructions to display a deactivation user interface on the client system, the deactivation user interface comprising: a first user-selectable element configured to continue activation of the eligible railroad crossing signal; a second user-selectable element configured to deactivate the eligible railroad crossing signal; and a visual indication of the second timer; sending a deactivation signal to the eligible railroad crossing signal upon expiration of the second timer; sending the deactivation signal to the eligible railroad crossing signal upon receiving an indication of selection of the second user-selectable element; and restarting the first timer upon receiving an indication of selection of the first user-selectable element.

18. The one or more computer-readable non-transitory storage media of claim 15, the operations further comprising: determining, from the plurality of records of railroad crossing signals, that no railroad crossing signals are within the predetermined distance of the physical location of the client system; and in response to determining that no railroad crossing signals are within the predetermined distance of the physical location of the client system, sending one or more instructions to display a message on the client system, the message indicating that no eligible railroad crossing signals are within range of the client system.

19. The one or more computer-readable non-transitory storage media of claim 15, wherein the physical location of the client system comprises latitude and longitude coordinates from a Global Positioning System (GPS) unit in the client system.

20. The one or more computer-readable non-transitory storage media of claim 19, wherein determining the eligible railroad crossing signal that is within the predetermined distance of the physical location of the client system comprises comparing latitude and longitude coordinates stored in each of the plurality of records of railroad crossing signals to the latitude and longitude coordinates of the client system.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0008] FIG. 1 illustrates a system for the remote activation of railroad crossing signals, according to certain embodiments;

[0009] FIGS. 2A-2B are example graphical user interfaces that may be provided by the system of FIG. 1 to select one or more railroad crossing signals for activation, according to particular embodiments;

[0010] FIG. 3 is an example confirmation graphical user interface that may be provided by the system of FIG. 1 to confirm the selection of one or more railroad crossing signals for activation, according to particular embodiments;

[0011] FIG. 4 is an example graphical user interface that may be provided by the system of FIG. 1 to indicate an out-of-range condition, according to particular embodiments;

[0012] FIG. 5 is an example deactivation graphical user interface that may be provided by the system of FIG. 1 to confirm deactivation of one or more railroad crossing signals, according to particular embodiments;

[0013] FIG. 6 is a flow diagram illustrating an example method for remotely activating railroad crossing signals, according to particular embodiments;

[0014] FIG. 7 illustrates an example personal computing device that may be used as the client system of FIG. 1, according to particular embodiments;

[0015] FIG. 8 illustrates an example software architecture for information and applications on a personal computing device, according to particular embodiments;

[0016] FIG. 9 is an example computer system that can be utilized to implement aspects of the various technologies presented herein, according to particular embodiments.

[0017] It should be understood that the drawings are not necessarily to scale and that the disclosed embodiments are sometimes illustrated diagrammatically and in partial views. In certain instances, details which are not necessary for an understanding of the disclosed methods and apparatuses or which render other details difficult to perceive may have been omitted. It should be understood, of course, that this disclosure is not limited to the particular embodiments illustrated herein.

DETAILED DESCRIPTION

[0018] The disclosure presented in the following written description and the various features and advantageous details thereof, are explained more fully with reference to the non-limiting examples included in the accompanying drawings and as detailed in the description. Descriptions of well-known components have been omitted to not unnecessarily obscure the principal features described herein. The examples used in the following description are intended to facilitate an understanding of the ways in which the disclosure can be implemented and practiced. A person of ordinary skill in the art would read this disclosure to mean that any suitable combination of the functionality or exemplary embodiments below could be combined to achieve the subject matter claimed. The disclosure includes either a representative number of species falling within the scope of the genus or structural features common to the members of the genus so that one of ordinary skill in the art can recognize the members of the genus. Accordingly, these examples should not be construed as limiting the scope of the claims.

[0019] A person of ordinary skill in the art would understand that any system claims presented herein encompass all of the elements and limitations disclosed therein, and as such, require that each system claim be viewed as a whole. Any reasonably foreseeable items functionally related to the claims are also relevant. The Examiner, after having obtained a thorough understanding of the disclosure and claims of the present application has searched the prior art as disclosed in patents and other published documents, i.e., nonpatent literature. Therefore, as evidenced by issuance of this patent, the prior art fails to disclose or teach the elements and limitations presented in the claims as enabled by the specification and drawings, such that the presented claims are patentable under the applicable laws and rules of this jurisdiction.

[0020] Railroad crossing signals play an important role in railroad safety. In addition to alerting and protecting vehicles from oncoming trains, railroad crossing signals protect railroad maintenance crews from traffic during repairs or inspections of the railroad track. To test or otherwise activate railroad crossing signals outside of normal train operations, a user is typically required to physically approach a railroad crossing signal and manually operate controls (e.g., with a key) that are physically located on the railroad crossing signal. Such manual activation of railroad crossing signals is unsafe and inconvenient, especially during times of inclement weather or in locations with heavy traffic.

[0021] To address these and other problems associated with railroad crossing signals, the enclosed embodiments provide systems and methods for the remote activation of railroad crossing signals. In general, the disclosed embodiments utilize a client system (e.g., a smartphone) and one or more back-end computer systems to remotely activate railroad crossing signals based on geofencing. For example, the back-end computer system(s) may determine a physical location of a client system by analyzing Global Positioning System (GPS) coordinates provided by the client system. The back-end computer system(s) may then determine one or more eligible railroad crossing signals that are within a predetermined distance of the physical location of the client system and then send identification information about the one or more eligible railroad crossing signals to the client system. The client system may display the identification information about the one or more eligible railroad crossing signals in a graphical user interface and allow a user to select one or more of the eligible railroad crossing signals for remote activation. The back-end computer system(s) may receive, from the client system, an indication of a user selection to activate one or more of the eligible railroad crossing signals, and in response, send an activation signal to the one or more selected railroad crossing signals. The activation signal activates the one or more selected railroad crossing signals (e.g., activates lights, activates bells, lowers arms, etc.). As a result, railroad crossing signals may be remotely activated without requiring personnel to physically approach a crossing, thereby increasing safety, saving time, and decreasing physical demands on personnel. Furthermore, the use of geofencing limits activation of railroad crossing signals to those that are nearby the user, thereby preventing the accidental activation of incorrect crossing signals.

[0022] FIG. 1 is a network diagram illustrating a railroad crossing signal activation system 100 for the remote activation of one or more railroad crossing signals 120, according to certain embodiments. Railroad crossing signal activation system 100 includes one or more computing systems 110 (collectively herein, computing system 110), one or more client systems 130, and a network 140. Client system 130 and railroad crossing signals 120 are communicatively coupled with computing system 110 using any appropriate wired or wireless communication system or network (e.g., network 140). Client system 130 includes an electronic display that displays a graphical user interface 132. Graphical user interface 132 displays various information and user-selectable elements that permit a user to view and select eligible railroad crossing signals 120 for remote activation, as described in more detail herein.

[0023] In general, railroad crossing signal activation system 100 utilizes client system 130 (e.g., a smartphone) and computing system 110 to remotely activate one or more railroad crossing signals 120 based on geofencing. To do so, client system 130 may first send physical location information 135 (e.g., latitude and longitude coordinates of the current physical location of client system 130) to computing system 110. Computing system 110 may then determine one or more eligible railroad crossing signals 120 to present to the user via user interface 132 on client system 130. To determine eligible railroad crossing signals 120, computing system 110 may determine, by analyzing railroad crossing signal records 150, which railroad crossing signals 120 have remote activation capabilities and are located within a predetermined distance of the current physical location of client system 130. Once one or more eligible railroad crossing signals 120 are determined from railroad crossing signal records 150, computing system 110 sends identification information 125 (e.g., a street name, a Department of Transportation (DOT) number, etc.) about each of the one or more eligible railroad crossing signals to client system 130. Client system 130 may display the identification information 125 about the one or more eligible railroad crossing signals in user interface 132 along with user-selectable elements that allow a user to select one or more of the eligible railroad crossing signals 120 for remote activation. After a user selects one or more of the eligible railroad crossing signals 120 for remote activation, client system 130 sends an indication of the user's selection to computing system 110 via user activation selection 137. Computing system 110 receives user activation selection 137 from client system 130 and in response sends an activation signal 127 to each of the one or more selected railroad crossing signals 120 (e.g., via a controller computer system located in a crossing signal house) in order to activate the crossing signals. After a certain amount of time or after certain conditions are met (as discussed below), computing system 110 may send a deactivation signal 128 to each of the one or more selected railroad crossing signals 120 (e.g., via a controller computer system located in a crossing signal house) in order to deactivate the crossing signals. As a result, railroad crossing signals 120 may be remotely activated without requiring personnel to physically approach the crossing, thereby increasing safety, saving time, and decreasing physical demands on personnel.

[0024] Computing system 110 may be any appropriate computing system in any suitable physical form. As example and not by way of limitation, computing system 110 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, an augmented/virtual reality device, or a combination of two or more of these. Where appropriate, computing system 110 may include one or more computer systems; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, computing system 110 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example, and not by way of limitation, computing system 110 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. Computing system 110 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate. A particular example of a computing system 110 is described in reference to FIG. 9.

[0025] Computing system 110 includes one or more memory units/devices 115 (collectively herein, memory 115) that may store railroad crossing signal records 150 and a railroad crossing signal activation module 160. Railroad crossing signal activation module 160 is utilized by computing system 110 to remotely activate one or more railroad crossing signals 120, as described herein. Railroad crossing signal activation module 160 represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, railroad crossing signal activation module 160 may be embodied in memory 115, a disk, a CD, or a flash drive. In particular embodiments, railroad crossing signal activation module 160 may include instructions (e.g., a software application) executable by a computer processor to perform one or more of the functions described herein.

[0026] Railroad crossing signal 120 is a device that is located at an intersection of a railroad track and a road. Railroad crossing signal 120 may include a bell and multiple lights in order to visually and audibly warn the public of the presence of a train at the crossing. In some embodiments, railroad crossing signal 120 includes one or more arms that may be lowered in order to physically prevent/impede traffic from crossing the railroad track. Railroad crossing signal 120 may include a transceiver for receiving commands/instructions from computing system 110 via network 140. For example, railroad crossing signal 120 may include a wireless transceiver for wirelessly receiving activation signal 127 and deactivation signal 128 from computing system 110 via network 140. In some embodiments, railroad crossing signal 120 receives activation signals 127 and deactivation signals 128 from computing system 110 via a controller computer system located in a crossing signal house. Upon receiving activation signal 127, railroad crossing signal 120 may activate one or more lights or bells and may lower an arm to prevent traffic from crossing the adjacent railroad track. Upon receiving deactivation signal 128, railroad crossing signal 120 may deactivate its lights and bells and raise its arm to allow traffic to cross the adjacent railroad track.

[0027] Client system 130 is any appropriate user device for communicating with components of computing system 110 over network 140 (e.g., the internet). In particular embodiments, client system 130 may be an electronic device including hardware, software, or embedded logic components or a combination of two or more such components and capable of carrying out the appropriate functionalities implemented or supported by client system 130. As an example, and not by way of limitation, a client system 130 may include a computer system (e.g., computer system 900) such as a desktop computer, notebook or laptop computer, netbook, a tablet computer, e-book reader, GPS device, camera, personal digital assistant (PDA), handheld electronic device, cellular telephone, smartphone, smartwatch, augmented/virtual reality device such as wearable computer glasses, other suitable electronic device, or any suitable combination thereof. This disclosure contemplates any suitable client system 130. A client system 130 may enable a network user at client system 130 to access network 110. A client system 130 may enable a user to communicate with other users at other client systems 130. Client system 130 may include an electronic display that displays graphical user interface 132, a processor such processor 902, and memory such as memory 904.

[0028] Network 140 allows communication between and amongst the various components of railroad crossing signal activation system 100. This disclosure contemplates network 140 being any suitable network operable to facilitate communication between the components of railroad crossing signal activation system 100. Network 140 may include any interconnecting system capable of transmitting audio, video, signals, data, messages, or any combination of the preceding. Network 140 may include all or a portion of a local area network (LAN), a wide area network (WAN), an overlay network, a software-defined network (SDN), a virtual private network (VPN), a packet data network (e.g., the Internet), a mobile telephone network (e.g., cellular networks, such as 4G or 5G), a Plain Old Telephone (POT) network, a wireless data network (e.g., WiFi, WiGig, WiMax, etc.), a Long Term Evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS) network, a peer-to-peer (P2P) network, a Bluetooth network, a Near Field Communication network, a Zigbee network, and/or any other suitable network.

[0029] Each railroad crossing signal record 150 stores vital information about a respective railroad crossing signal 120. For example, railroad crossing signal record 150A may be associated with railroad crossing signal 120A and store vital information about railroad crossing signal 120A. For example, the railroad crossing signal record 150A for railroad crossing signal 120A may store unique identification information for railroad crossing signal 120A (e.g., a street name (e.g., Street A) associated with railroad crossing signal 120A, a DOT identification number of railroad crossing signal 120A (e.g., DOT #145), a unique asset identification number of railroad crossing signal 120A, and the like). In some embodiments, railroad crossing signal record 150 may store location information for the associated railroad crossing signal 120 (e.g., latitude and longitude coordinates). In some embodiments, railroad crossing signal record 150 may store remote activation capabilities for the associated railroad crossing signal 120. For example, railroad crossing signal record 150A that is associated with railroad crossing signal 120A may store information regarding whether or not railroad crossing signal 120A may be remotely activated (e.g., has the required hardware installed to remotely receive commands such as activation signal 127 and deactivation signal 128).

[0030] FIGS. 2A-2B illustrate example graphical user interfaces 132A and 132B that may be provided by railroad crossing signal activation system 100 to allow a user to select one or more railroad crossing signals 120 for remote activation, according to particular embodiments. In these example embodiments, graphical user interfaces 132A and 132B each display two eligible railroad crossing signals: 220A and 220B. As discussed herein, each eligible railroad crossing signal 220 has remote activation capabilities and is located within a predetermined distance 230 (e.g., a geofence) of the current physical location 240 of client system 130. In some embodiments, eligible railroad crossing signals 220 are displayed on a map along with current physical location 240 of client system 130, as illustrated in FIG. 2A. In other embodiments, eligible railroad crossing signals 220 are displayed in a list format, as illustrated in FIG. 2B.

[0031] In both illustrated embodiments of FIGS. 2A-2B, each eligible railroad crossing signal 220 includes identification information 125. For example, eligible railroad crossing signal 220A includes identification information 125A of DOT #145 as illustrated in FIG. 2A or DOT #145, STREET A as illustrated in FIG. 2B. Similarly, eligible railroad crossing signal 220B includes identification information 125B of DOT #146 as illustrated in FIG. 2A or DOT #146, STREET B as illustrated in FIG. 2B. In addition, each eligible railroad crossing signal 220 includes an associated user-selectable element 250 (e.g., a checkbox, radial button, etc.) that allows a user to select the eligible railroad crossing signal 220 for activation. For example, eligible railroad crossing signal 220A includes a user-selectable element 250A, and eligible railroad crossing signal 220B includes a user-selectable element 250B. Once a user selects one or more eligible railroad crossing signals 220 for activation using user-selectable elements 250, the user may select a graphical element 260 to advance to confirmation graphical user interface 132C as illustrated in FIG. 3 and discussed below.

[0032] In some embodiments, graphical user interfaces 132A and 132B are displayed on client system 130 only after a user is authenticated as an approved user. In some embodiments, a user may be authenticated using a username and password. In some embodiments, a user may be authenticated using biometrics such as fingerprint or facial recognition. In some embodiments, two-factor authentication may be used to authenticate a user prior to the display of graphical user interfaces 132A and 132B.

[0033] FIG. 3 is an example confirmation graphical user interface 132C that may be provided by railroad crossing signal activation system 100 to confirm the selection of one or more eligible railroad crossing signals 220 for activation, according to particular embodiments. In some embodiments, confirmation graphical user interface 132C may be displayed on client system 130 after a user selects graphical element 260 in user interface 132A or 132B. In general, confirmation graphical user interface 132C displays the eligible railroad crossing signals 220 that were selected in user interface 132A or 132B and asks the user to confirm the selection. In the illustrated embodiment, eligible railroad crossing signal 220B and its associated identification information 125B is displayed in confirmation graphical user interface 132C since eligible railroad crossing signal 220B was selected via user-selectable element 250B in user interface 132A and 132B. To confirm the selection, the user may select confirmation graphical element 310. To reject the selection, the user may select confirmation graphical element 320. Upon selection of confirmation graphical element 310, client system 130 may send user activation selection 137 to computing system 110 as an indication of the user selection of which eligible railroad crossing signals 220 to activate. In turn, computing system 110 may send activation signals 127 to the selected eligible railroad crossing signals 220 (e.g., via a controller computer system located in a crossing signal house).

[0034] FIG. 4 is an example graphical user interface 132D that may be provided by railroad crossing signal activation system 100 to indicate an out-of-range condition, according to particular embodiments. In general, embodiments of the disclosure enable a user to remotely activate one or more railroad crossing signals 120 based on geofencing. That is, railroad crossing signal activation system 100 determines a current physical location of client system 130 using physical location information 135 (e.g., GPS coordinates) and then determines, by analyzing railroad crossing signal records 150, which railroad crossing signals 120 have remote activation capabilities and are located within a predetermined distance of the current physical location of client system 130. If railroad crossing signal activation system 100 determines that no railroad crossing signals 120 with remote activation capabilities are located within a predetermined distance of the current physical location of client system 130, user interface 132D may be displayed on client system 130 to instruct the user that there are no eligible railroad crossing signals 120 to activate and to move closer to the desired crossing signal. In some embodiments, user interface 132D may include a map as illustrated in FIG. 4 to visually indicate to the user their current physical location 240 as well as geofence 230. The user may select graphical element 410 to return to previous user interfaces 132 (e.g., 132A-132B).

[0035] FIG. 5 is an example deactivation graphical user interface 132E that may be provided by railroad crossing signal activation system 100 to confirm deactivation of one or more railroad crossing signals 120, according to particular embodiments. In some embodiments, deactivation graphical user interface 132E may be presented to the user on client system 130 after certain conditions are met. For a first example, railroad crossing signal activation system 100 may display deactivation graphical user interface 132E a certain amount of time after activation of one or more railroad crossing signals 120. In these embodiments, railroad crossing signal activation system 100 may start a first timer upon sending activation signal 127 to the one or more selected eligible railroad crossing signals 220. The first timer may be any appropriate amount of time (e.g., one minute, two minutes, three minutes, etc.). Upon expiration of the first timer, railroad crossing signal activation system 100 may send one or more instructions to display deactivation graphical user interface 132E on client system 130.

[0036] As a second example, railroad crossing signal activation system 100 may display deactivation graphical user interface 132E if client system 130 travels away from an activated railroad crossing signal 120 such that the activated railroad crossing signal 120 is no longer within geofence 230. In these embodiments, railroad crossing signal activation system 100 may continuously monitor a current physical location of client system 130 after sending activation signal 127 (e.g., via physical location information 135 provided by client system 130 at certain time intervals). If client system 130 travels to where one or more activated railroad crossing signals 120 are no longer within geofence 230, railroad crossing signal activation system 100 may send one or more instructions to display deactivation graphical user interface 132E on client system 130.

[0037] In general, deactivation graphical user interface 132E displays the eligible railroad crossing signals 220 that were selected in user interfaces 132A-B and asks the user to confirm continued activation of the selected crossing signals. In the illustrated embodiment, eligible railroad crossing signal 220B and its associated identification information 125B is displayed in deactivation graphical user interface 132E since eligible railroad crossing signal 220B was selected via user-selectable element 250B in user interface 132A and 132B. To continue activation of the selected crossing signals, the user may select graphical element 510. To discontinue with activation (i.e., to deactivate the activated railroad crossing signals 120), the user may select graphical element 510. Upon selection of graphical element 510, client system 130 may restart the first timer. Upon selection of graphical element 520, computing system 110 may send deactivation signal 128 to the activated railroad crossing signals 120 (e.g., via a controller computer system located in a crossing signal house).

[0038] In some embodiments, deactivation graphical user interface 132E may display a visual indication 530 of a second timer. In general, the second timer may be started immediately after deactivation graphical user interface 132E is displayed and may be used to automatically deactivate the activated railroad crossing signals 120. For example, the second timer may be a one-minute countdown timer (or any other appropriate amount of time). Upon expiration of the second timer, computing system 110 may send deactivation signal 128 to the activated railroad crossing signals 120 regardless of whether or not graphical elements 510-520 are selected by the user. The automatic deactivation of activated railroad crossing signals 120 based on the second timer protects against situations that may keep railroad crossing signals 120 activated for extended periods of time (e.g., where the user is preoccupied, where client system 130 loses communications capabilities, and the like).

[0039] In operation, and in reference to FIGS. 1-5, railroad crossing signal activation system 100 provides for the remote activation of railroad crossing signals 120 based on geofencing. As a first step, a user may utilize a client system 130 (e.g., a smartphone) to execute an application on client system 130 that communicates with computing system 110. In some embodiments, opening the application on client system 130 may first require the user to be authenticated (e.g., using a username/password or biometrics such as a fingerprint). Once the user is authenticated, client system 130 may send physical location information 135 (e.g., latitude and longitude coordinates of the current physical location of client system 130) to computing system 110. Computing system 110 may then determine one or more eligible railroad crossing signals 120 to present to the user via user interfaces 132A-B on client system 130. To determine eligible railroad crossing signals 120, computing system 110 may determine, by analyzing railroad crossing signal records 150, which railroad crossing signals 120 have remote activation capabilities (e.g., a wireless transceiver) and are located less than or equal to a predetermined distance (e.g., within a geofence) of the current physical location of client system 130. The predetermined distance for the geofence may be, for example, any distance such as 100 feet, 200 feet, 500 feet, 1000 feet, one mile, two miles, and the like. In some embodiments, determining whether a particular railroad crossing signal 120 is within the predetermined distance of the physical location of client system 130 includes comparing latitude and longitude coordinates stored in the railroad crossing signal record 150 for the particular railroad crossing signal 120 to latitude and longitude coordinates of client system 130 provided via physical location information 135.

[0040] Once one or more eligible railroad crossing signals 120 are determined from railroad crossing signal records 150, computing system 110 sends identification information 125 about each of the one or more eligible railroad crossing signals 120 to client system 130. The identification information 125 may include a street name, a DOT identification number of railroad crossing signal 120A, a unique asset identification number of railroad crossing signal 120A, and the like. Once received, client system 130 displays eligible railroad crossing signals 220 in user interfaces 132A-132B that each include the associated identification information 125, as illustrated in FIGS. 2A-2B. If railroad crossing signal activation system 100 determines that there are no railroad crossing signals 120 with remote activation capabilities located within a predetermined distance of the current physical location of client system 130, user interface 132D may be displayed on client system 130 to instruct the user that there are no eligible railroad crossing signals 120 to activate and to move closer to the desired crossing signal, as illustrated in FIG. 4.

[0041] Next, a user selects one or more of the eligible railroad crossing signals 220 for remote activation in user interfaces 132A-132B using user-selectable elements 250. After the user selects one or more of the eligible railroad crossing signals 220 for remote activation in user interfaces 132A-132B, confirmation graphical user interface 132C may be displayed on client system 130, as illustrated in FIG. 3. Confirmation graphical user interface 132C allows the user to confirm activation of the selected eligible railroad crossing signals 220. In response to the user's confirmation in confirmation graphical user interface 132C, client system 130 sends an indication of the user's selection to computing system 110 via user activation selection 137.

[0042] Next, computing system 110 receives user activation selection 137 from client system 130, which may include indications of which eligible railroad crossing signals 220 were selected by the user in user interfaces 132A-132B. In response to receiving activation selection 137, computing system 110 sends an activation signal 127 to each of the one or more selected eligible railroad crossing signals 220 in order to activate the crossing signals (e.g., to enable lights, bells, and arms).

[0043] After a certain amount of time or after certain conditions are met (as discussed above in reference to FIG. 5), computing system 110 may display deactivation graphical user interface 132E to allow a user to confirm deactivation of one or more railroad crossing signals 120 (e.g., to disable lights, bells, and arms). If the user chooses to discontinue activation of one or more railroad crossing signals 120 in deactivation graphical user interface 132E, computing system 110 sends a deactivation signal 128 to each of the one or more selected railroad crossing signals 120 (e.g., via a controller computer system located in a crossing signal house) in order to deactivate the crossing signals. As a result, railroad crossing signals 120 may be remotely activated without requiring personnel to physically approach the crossing, thereby increasing safety, saving time, and decreasing physical demands on personnel.

[0044] FIG. 6 is a flow diagram illustrating an example method 600 for remotely activating railroad crossing signals, according to certain embodiments. In some embodiments, method 600 may be performed by computing system 110. Method 600 may begin in step 610 where method 600 determines a physical location of a client system. In some embodiments, the client system is client system 130 such as a smartphone. In some embodiments, the physical location of the client system includes latitude and longitude coordinates from a GPS unit in the client system. In some embodiments, step 610 includes analyzing physical location information such as physical location information 135 provided by the client system. The physical location information may include the latitude and longitude coordinates of the client system and may be provided at periodic intervals by the client system (e.g., every minute, etc.).

[0045] In step 620, method 600 determines an eligible railroad crossing signal that is within a predetermined distance of the physical location of the client system determined in step 610 (e.g., via a controller computer system located in a crossing signal house). In some embodiments, step 620 includes analyzing one or more railroad crossing signal records such as railroad crossing signal records 150. In some embodiments, step 620 includes first filtering railroad crossing signal records 150 to discover the railroad crossing signals that include remote activation capabilities (e.g., wireless transceivers) and then comparing latitude and longitude coordinates of the railroad crossing signals with remote activation capabilities to latitude and longitude coordinates of the client system.

[0046] In step 630, method 600 sends identification information about the eligible railroad crossing signal determined in step 620 to the client system. In some embodiments, the identification information is identification information 125. In some embodiments, the identification information is determined from railroad crossing signal records such as railroad crossing signal record 150. In some embodiments, the identification information includes one or more of a street name associated with the eligible railroad crossing signal, a DOT identification number of the eligible railroad crossing signal, and a unique asset identification number of the eligible railroad crossing signal.

[0047] In step 640, method 600 receives, from the client system, an indication of a user selection to activate the eligible railroad crossing signal. In some embodiments, the indication received in step 640 is user activation selection 137. In some embodiments, the indication of a user selection to activate the eligible railroad crossing signal is sent by the client system in response to a user selecting an eligible railroad crossing signal 220 in graphical user interfaces 132A-132B.

[0048] In step 650, method 600 sends an activation signal to the eligible railroad crossing signal in response to receiving the indication of the user selection to activate the eligible railroad crossing signal in step 640. In some embodiments, the activation signal is activation signal 127. In some embodiments, the activation signal enables one or more bells, lights, and arms of the eligible railroad crossing signal. In some embodiments, the activation signal is sent to the eligible railroad crossing signal via a controller computer system located in a crossing signal house. After step 650, method 600 may end.

[0049] Particular embodiments may repeat one or more steps of the method of FIG. 6, where appropriate. Although this disclosure describes and illustrates particular steps of the method of FIG. 6 as occurring in a particular order, this disclosure contemplates any suitable steps of the method of FIG. 6 occurring in any suitable order. Moreover, although this disclosure describes and illustrates an example method for remotely activating railroad crossing signals including the particular steps of the method of FIG. 6, this disclosure contemplates any suitable method for remotely activating railroad crossing signals including any suitable steps, which may include all, some, or none of the steps of the method of FIG. 6, where appropriate. Furthermore, although this disclosure describes and illustrates particular components, devices, or systems carrying out particular steps of the method of FIG. 6, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable steps of the method of FIG. 6.

[0050] FIG. 7 illustrates an example personal computing device 700, which may be used as client system 130. In particular embodiments, personal computing device 700 includes a processor 710, a memory 720, a communication component 730 (e.g., antenna and communication interface for wireless communications), one or more input and/or output (I/O) components and/or interfaces 740, and one or more sensors 750. In particular embodiments, one or more I/O components and/or interfaces 740 may incorporate one or more sensors 750. In particular embodiments, personal computing device 700 may comprise a computer system or an element thereof as described in FIG. 9 and its associated description.

[0051] In particular embodiments, personal computing device 700, such as a mobile device, may include various types of sensors 750, such as, for example and without limitation: touch sensors (disposed, for example, on a display of the device, the back of the device and/or one or more lateral edges of the device) for detecting a user touching the surface of the mobile electronic device (e.g., using one or more fingers); an accelerometer for detecting whether the personal computing device 700 is moving and the speed of the movement; a thermometer for measuring the temperature change near the personal computing device 700; a proximity sensor for detecting the proximity of the personal computing device 700 to another object (e.g., a hand, desk, or other object); a light sensor for measuring the ambient light around the personal computing device 700; an imaging sensor (e.g., camera) for capturing digital still images and/or video of objects near the personal computing device 700 (e.g., scenes, people, bar codes, QR codes, etc.); location sensors (e.g., GPS) for determining the location (e.g., in terms of coordinates such as latitude and longitude) of the mobile electronic device; sensors for detecting communication networks within close proximity (e.g., near field communication (NFC), Bluetooth, RFID, infrared); chemical sensors; biometric sensors for biometrics-based (e.g., fingerprint, palm vein pattern, hand geometry, iris/retina, DNA, face, voice, olfactory, sweat) authentication of user of personal computing device 700; etc. This disclosure contemplates that personal computing device 700 may include any applicable type of sensor.

[0052] In particular embodiments, a sensors hub 760 may optionally be included in personal computing device 700. Sensors 750 may be connected to sensors hub 760, which may be a low power-consuming processor that controls sensors 750, manages power for sensors 750, processes sensor inputs, aggregates sensor data, and performs certain sensor functions. In addition, in particular embodiments, some types of sensors 750 may be connected to a controller 770. In this case, sensors hub 760 may be connected to controller 770, which in turn is connected to sensor 750. Alternatively, in particular embodiments, personal computing device 700 may include a sensor monitor in place of sensors hub 760 for managing sensors 750.

[0053] In particular embodiments, personal computing device 700 may have one or more sensors for performing authentication/authorization using biometric identification. Such sensors may be positioned on any surface of personal computing device 700. In example embodiments, as a user's hand touches personal computing device 700 to grab hold of it, the touch sensors may capture the user's fingerprints or palm vein pattern. In example embodiments, while a user is viewing the screen of personal computing device 700, a camera may capture an image of the user's face to perform facial recognition. In example embodiments, while a user is viewing the screen of personal computing device 700, an infrared scanner may scan the user's iris and/or retina. In example embodiments, while a user is in contact or close proximity with personal computing device 700, chemical and/or olfactory sensors may capture relevant data about a user.

[0054] FIG. 8 illustrates an example software architecture 800 for information and applications on personal computing device 700. In particular embodiments, software architecture 800 includes software 810 and data store(s) 820. In particular embodiments, personal information may be stored in an application data cache 820 and/or a profile data store 820 and/or another data store 820. In particular embodiments, one or more software applications (i.e., apps) may be executed on personal computing device 700. In particular embodiments, the applications may be typical mobile computing apps or web-based applications hosted on servers. For example, a web-based application may be associated with a URI (Uniform Resource Identifier) or URL (Uniform Resource Locator). From personal computing device 700, a user may access the web-based application through its associated URI or URL (e.g., by using a web browser). Alternatively, in other embodiments, the applications may be native apps installed and residing on personal computing device 700. Thus, software 810 may also include any number of application user interfaces 830 and application functions 840. For example, one application (e.g., Google Maps) may enable a device user to view a map, search for addresses and businesses, and get directions; a second application may enable the device user to read, send, and receive emails; a third application (e.g., a web browser) may enable the device user to browse and search the Internet; a fourth application may enable the device user to take photos or record videos using personal computing device 700; a fifth application may allow the device user to receive and initiate VoIP and/or cellular network calls, and so on. Each application has one or more specific functionalities, and the software (e.g., one or more software modules) implementing these functionalities may be included in application functions 840. Each application may also have a user interface that enables the device user to interact with the application, and the software implementing the application user interface may be included in application user interfaces 830. In particular embodiments, the functionalities of an application may be implemented using JavaScript, Java, C, or any other suitable programming language. In particular embodiments, the user interface of an application may be implemented using HyperText Markup Language (HTML), JavaScript, Java, or other suitable programming languages.

[0055] In particular embodiments, the user interface of an application may include any number of screens or displays. In particular embodiments, each screen or display of the user interface may be implemented as a web page. Thus, the device user may interact with the application through a series of screens or displays (i.e., a series of web pages).

[0056] During the execution of an application, the device user may interact with the application through its user interface. For example, the user may provide inputs to the application in various displays (e.g., web pages). Outputs of the application may be presented to the user in various displays (e.g., web pages) as well. In particular embodiments, when the user provides an input to the application through a specific display (e.g., a specific web page), an event (e.g., an input event) may be generated by, for example, a web view 860 or application user interfaces 830. Each input event may be forwarded to application functions 840, or application functions 840 may listen for input events thus generated. When application functions 840 receive an input event, the appropriate software module in application functions 840 may be invoked to process the event. In addition, specific functionalities provided by operating system 850 and/or hardware may also be invoked. For example, if the event is generated as a result of the user pushing a button to take a photo with personal computing device 700, a corresponding image processing module may be invoked to convert the raw image data into an image file (e.g., JPG or GIF) and store the image file in the storage 820 of personal computing device 700. As anther example, if the event is generated as a result of the user selecting an icon to compose an instant message, the corresponding short message service (SMS) module may be invoked to enable the user to compose and send the message.

[0057] In particular embodiments, when an output of the application is ready to be presented to the user, an event (e.g., an output event) may be generated by, for example, a software module in application functions 840 or operating system 850. Each output event may be forwarded to application user interfaces 830, or application user interfaces 830 may listen for output events thus generated. When application user interfaces 830 receive an output event, it may construct a web view 860 to display a web page representing or containing the output. For example, in response to the user selecting an icon to compose an instant message, an output may be constructed that includes a text field that allows the user to input the message. This output may be presented to the user as a web page and displayed to the user in a web view 860 so that the user may type into the text field the message to be sent.

[0058] The user interface of an application may be implemented using a suitable programming language (e.g., HTML, JavaScript, or Java). More specifically, in particular embodiments, each web page that implements a screen or display of the user interface may be implemented using a suitable programming language. In particular embodiments, when a web view 860 is constructed to display a web page (e.g., by application user interfaces 830 in response to an output event), the code implementing the web page is loaded into web view 860.

[0059] FIG. 9 illustrates an example computer system 900. In particular embodiments, one or more computer systems 900 perform one or more steps of one or more methods described or illustrated herein. In particular embodiments, one or more computer systems 900 provide functionality described or illustrated herein. In particular embodiments, software running on one or more computer systems 900 performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein. Particular embodiments include one or more portions of one or more computer systems 900. Herein, reference to a computer system may encompass a computing device, and vice versa, where appropriate. Moreover, reference to a computer system may encompass one or more computer systems, where appropriate.

[0060] This disclosure contemplates any suitable number of computer systems 900. This disclosure contemplates computer system 900 taking any suitable physical form. As example and not by way of limitation, computer system 900 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, an augmented/virtual reality device, or a combination of two or more of these. Where appropriate, computer system 900 may include one or more computer systems 900; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks. Where appropriate, one or more computer systems 900 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein. As an example, and not by way of limitation, one or more computer systems 900 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein. One or more computer systems 900 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.

[0061] In particular embodiments, computer system 900 includes a processor 902, memory 904, storage 906, an input/output (I/O) interface 908, a communication interface 910, and a bus 912. Although this disclosure describes and illustrates a particular computer system having a particular number of particular components in a particular arrangement, this disclosure contemplates any suitable computer system having any suitable number of any suitable components in any suitable arrangement.

[0062] In particular embodiments, processor 902 includes hardware for executing instructions, such as those making up a computer program. As an example, and not by way of limitation, to execute instructions, processor 902 may retrieve (or fetch) the instructions from an internal register, an internal cache, memory 904, or storage 906; decode and execute them; and then write one or more results to an internal register, an internal cache, memory 904, or storage 906. In particular embodiments, processor 902 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor 902 including any suitable number of any suitable internal caches, where appropriate. As an example, and not by way of limitation, processor 902 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs). Instructions in the instruction caches may be copies of instructions in memory 904 or storage 906, and the instruction caches may speed up retrieval of those instructions by processor 902. Data in the data caches may be copies of data in memory 904 or storage 906 for instructions executing at processor 902 to operate on; the results of previous instructions executed at processor 902 for access by subsequent instructions executing at processor 902 or for writing to memory 904 or storage 906; or other suitable data. The data caches may speed up read or write operations by processor 902. The TLBs may speed up virtual-address translation for processor 902. In particular embodiments, processor 902 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor 902 including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor 902 may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors 902. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.

[0063] In particular embodiments, memory 904 includes main memory for storing instructions for processor 902 to execute or data for processor 902 to operate on. As an example, and not by way of limitation, computer system 900 may load instructions from storage 906 or another source (such as, for example, another computer system 900) to memory 904. Processor 902 may then load the instructions from memory 904 to an internal register or internal cache. To execute the instructions, processor 902 may retrieve the instructions from the internal register or internal cache and decode them. During or after execution of the instructions, processor 902 may write one or more results (which may be intermediate or final results) to the internal register or internal cache. Processor 902 may then write one or more of those results to memory 904. In particular embodiments, processor 902 executes only instructions in one or more internal registers or internal caches or in memory 904 (as opposed to storage 906 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 904 (as opposed to storage 906 or elsewhere). One or more memory buses (which may each include an address bus and a data bus) may couple processor 902 to memory 904. Bus 912 may include one or more memory buses, as described below. In particular embodiments, one or more memory management units (MMUs) reside between processor 902 and memory 904 and facilitate accesses to memory 904 requested by processor 902. In particular embodiments, memory 904 includes random access memory (RAM). This RAM may be volatile memory, where appropriate. Where appropriate, this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be single-ported or multi-ported RAM. This disclosure contemplates any suitable RAM. Memory 904 may include one or more memories 904, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.

[0064] In particular embodiments, storage 906 includes mass storage for data or instructions. As an example, and not by way of limitation, storage 906 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or a Universal Serial Bus (USB) drive or a combination of two or more of these. Storage 906 may include removable or non-removable (or fixed) media, where appropriate. Storage 906 may be internal or external to computer system 900, where appropriate. In particular embodiments, storage 906 is non-volatile, solid-state memory. In particular embodiments, storage 906 includes read-only memory (ROM). Where appropriate, this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these. This disclosure contemplates mass storage 906 taking any suitable physical form. Storage 906 may include one or more storage control units facilitating communication between processor 902 and storage 906, where appropriate. Where appropriate, storage 906 may include one or more storages 906. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.

[0065] In particular embodiments, I/O interface 908 includes hardware, software, or both, providing one or more interfaces for communication between computer system 900 and one or more I/O devices. Computer system 900 may include one or more of these I/O devices, where appropriate. One or more of these I/O devices may enable communication between a person and computer system 900. As an example, and not by way of limitation, an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touch screen, trackball, video camera, another suitable I/O device or a combination of two or more of these. An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 908 for them. Where appropriate, I/O interface 908 may include one or more device or software drivers enabling processor 902 to drive one or more of these I/O devices. I/O interface 908 may include one or more I/O interfaces 908, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.

[0066] In particular embodiments, communication interface 910 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computer system 900 and one or more other computer systems 900 or one or more networks. As an example, and not by way of limitation, communication interface 910 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network. This disclosure contemplates any suitable network and any suitable communication interface 910 for it. As an example, and not by way of limitation, computer system 900 may communicate with an ad hoc network, a personal area network (PAN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), or one or more portions of the Internet or a combination of two or more of these. One or more portions of one or more of these networks may be wired or wireless. As an example, computer system 900 may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network, a Long-Term Evolution (LTE) network, or a 5G network), or other suitable wireless network or a combination of two or more of these. Computer system 900 may include any suitable communication interface 910 for any of these networks, where appropriate. Communication interface 910 may include one or more communication interfaces 910, where appropriate. Although this disclosure describes and illustrates a particular communication interface, this disclosure contemplates any suitable communication interface.

[0067] In particular embodiments, bus 912 includes hardware, software, or both coupling components of computer system 900 to each other. As an example and not by way of limitation, bus 912 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these. Bus 912 may include one or more buses 912, where appropriate. Although this disclosure describes and illustrates a particular bus, this disclosure contemplates any suitable bus or interconnect.

[0068] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the disclosure as defined by the appended claims. Moreover, the scope of the present application is not intended to be limited to the particular embodiments of the process, machine, manufacture, composition of matter, means, methods and steps described in the specification. As one of ordinary skill in the art will readily appreciate from the disclosure of the present disclosure, processes, machines, manufacture, compositions of matter, means, methods, or steps, presently existing or later to be developed that perform substantially the same function or achieve substantially the same result as the corresponding embodiments described herein may be utilized according to the present disclosure. Accordingly, the appended claims are intended to include within their scope such processes, machines, manufacture, compositions of matter, means, methods, or steps.

[0069] Moreover, the description in this patent document should not be read as implying that any particular element, step, or function can be an essential or critical element that must be included in the claim scope. Also, none of the claims can be intended to invoke 35 U.S.C. 112(f) with respect to any of the appended claims or claim elements unless the exact words means for or step for are explicitly used in the particular claim, followed by a participle phrase identifying a function. Use of terms such as (but not limited to) member, module, device, unit, component, element, mechanism, apparatus, machine, system, processor, processing device, or controller within a claim can be understood and intended to refer to structures known to those skilled in the relevant art, as further modified or enhanced by the features of the claims themselves, and can be not intended to invoke 35 U.S.C. 112(f). Even under the broadest reasonable interpretation, in light of this paragraph of this specification, the claims are not intended to invoke 35 U.S.C. 112(f) absent the specific language described above.

[0070] The disclosure may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. For example, each of the new structures described herein, may be modified to suit particular local variations or requirements while retaining their basic configurations or structural relationships with each other or while performing the same or similar functions described herein. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive. Accordingly, the scope of the disclosures can be established by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Further, the individual elements of the claims are not well-understood, routine, or conventional. Instead, the claims are directed to the unconventional inventive concept described in the specification.