Patent Description:
Movement of vehicles is controlled by control systems that receive user input and communicate control signals to components of the vehicles to implement actions dictated by the user input. For example, a vehicle operator may depress a pedal, move a lever, or take other action to change a throttle setting of a vehicle or activate a brake of the vehicle. Responsive to this operator input, a control system of the vehicle may communicate signals (e.g., changes in voltages, currents, etc.) to engines, motors, brakes, etc., of the vehicle in order to implement the operator input (and change the throttle or activate the brake, as appropriate).

The control systems of some vehicles may be complex in that many components communicate with each other. Not all of these components, however, may communicate signals of the same or similar importance or criticality to operation of the vehicle. For example, components that measure operations of the vehicle (e.g., location, speed, etc.), components that record events occurring during movement of the vehicle, components that measure fuel onboard the vehicle, etc., may communicate signals that are less important to ensuring the safe operation of the vehicle compared to other communications, such as signals communicated with motors of the vehicle, signals communicated with input/output devices, etc..

The control systems may use different communication networks within a vehicle to ensure that the more important or critical communications and the less important or less critical communications are all successfully communicated. But, using many different communication networks within a vehicle can present unnecessarily complexity. For example, some components may not be able to communicate with each other without the communications being relayed and/or converted by another component. As the number of networks and components needed to communicate within a vehicle control system increases, the potential points of failure and complexity of ensuring that communications successful occur increase.

<CIT> discloses a wireless communication device of a vehicle system using different kind of modems for communication.

<CIT> discloses a "smart" transit signal priority and control system.

In one embodiment, a control system includes the features of claim <NUM>.

The subject matter described herein will be better understood from reading the following description of non-limiting embodiments, with reference to the attached drawings, wherein below:.

<FIG> illustrates one example of a vehicle control system <NUM>. The vehicle control system <NUM> may be disposed onboard one or more vehicles of a vehicle system. For example, the control system <NUM> may be disposed onboard a locomotive of a rail vehicle system formed from the locomotive and one or more other locomotives <NUM>, <NUM>. The locomotives in the vehicle system are communicatively coupled by a wired connection <NUM>, such as a <NUM>-pin trainline cable. Other control systems identical or similar to the control system <NUM> shown in <FIG> may be disposed onboard the other locomotives <NUM>, <NUM>, with the various control systems <NUM> communicatively coupled (e.g., able to communicate with each other via) the wired connection <NUM>. While the control system <NUM> is shown as being disposed onboard a locomotive of a rail vehicle system, alternatively, the control system <NUM> may be disposed onboard another type of vehicle. For example, the control system <NUM> may be disposed onboard an automobile, a marine vessel, a mining vessel, another off-highway vehicle (e.g., a vehicle that is not legally permitted or that is not designed for travel along public roadways), airplanes, etc..

The control system <NUM> communicates via the wired connection <NUM> via a vehicle system interface device <NUM> ("EMU" in <FIG>), such as an Ethernet over a multiple unit (MU) cable interface. The interface device <NUM> represents communication circuitry, such as modems, routing circuitry, etc. A front end controller <NUM><NUM> ("Customer ACC" in <FIG>) is coupled with the interface device <NUM> by one or more wired connections. The controller <NUM><NUM> represents hardware circuitry that couples with (e.g., receives) one or more other circuits (e.g., compute cards) that control operation of the control system <NUM>. As shown in <FIG>, the controller <NUM> also may be connected with the second communication network <NUM>.

Several control devices <NUM>, such as a radio, display units, and/or vehicle system management controllers, are connected with the interface device <NUM> and the controller <NUM> via a first communication network <NUM> ("PTC Ethernet Network" in <FIG>). The communication network <NUM> may be an Ethernet network that communicates data packets between components connected to the network <NUM>. One or more other devices <NUM> may be connected with the network <NUM> to provide other functions or control over the vehicle.

The networks described herein can be formed from a structure of communication devices and hardware, such as cables interconnecting devices, wireless devices interconnecting other devices, routers interconnecting devices, switches interconnecting devices, transceivers, antennas, and the like. One or more networks described herein can be entirely off-board all vehicles. Optionally, at least part of a network can be disposed onboard one or more vehicles, such as by having one or more hardware components that form the network being onboard a vehicle and communicating in the network as the vehicle is moving. Additionally or alternatively, a network can be disposed entirely onboard a vehicle or vehicle system, such as when the components communicating with each other to form the network are all disposed onboard the same vehicle or onboard multiple vehicles that travel together along routes as a vehicle system.

An interface gateway <NUM> also is connected the first communication network <NUM>. The interface gateway <NUM> is referred to as a locomotive interface gateway ("LIG" shown in <FIG> ), but optionally may be referred to by another name depending on the type of vehicle that the interface gateway <NUM> is disposed upon. The interface gateway <NUM> represents hardware circuitry that communicatively couples the first network <NUM> with at least a second communication network <NUM>. hi the illustrated embodiment, the second communication network <NUM> is referred to as a data Ethernet network, and can represent an Ethernet network similar to the first network <NUM>.

The interface gateway <NUM> can provide a communication bridge between the two networks <NUM>, <NUM>. For example, the interface gateway <NUM> can change protocols of communications between the two networks <NUM>, <NUM>, can determine which communications to allow to be communicated from a device on one network <NUM> or <NUM> to a device on the other network <NUM> or <NUM> (for example, by applying one or more rules to determine which communications may be allowed to pass between the networks <NUM>, <NUM>), or otherwise control communications between the two networks <NUM>, <NUM>.

A dynamic brake modem <NUM> ("DBM" in <FIG>) also is connected with the second network <NUM>. This brake modem <NUM> also can be referred to as a dynamic brake modem. The dynamic brake modem <NUM> also may be connected with the wired connection <NUM>. The dynamic brake modem <NUM> represents hardware circuitry that receives control signals from one or more other vehicles <NUM>, <NUM> via the wired connection <NUM> and/or via the second network <NUM> in order to control one or more brakes of the vehicle. For example, the dynamic brake modem <NUM> may receive a control signal from the vehicle <NUM>, <NUM> or from an input/output device <NUM> ("SCIO" shown in <FIG> and described below) that reports the dynamic braking capability of the vehicle so that the braking capacity of the entire consist can be computed. The dynamic brakes can represent traction motors that operate in a regenerative braking mode in order to slow or stop movement of the vehicle. The dynamic brake modem is a FRA (Federal Rail Administration) required item for modern control systems.

The input/output device <NUM> represents one or more devices that receive input from an operator onboard the vehicle and or that present information to the operator. The input/output device <NUM> may be referred to as a super centralized input/output device (one device), and can represent one or more touchscreens, keyboards, styluses, display screens, lights, speakers, or the like. The input/output device <NUM> is connected with the second communication network <NUM> and also is connected with a third communication network <NUM>. The third communication network <NUM> also can be an Ethernet network, and may be referred to as a control Ethernet network, as shown in <FIG>. This network can also be either single path or can be implemented in a redundant network.

Several display devices <NUM> may be connected with the input/output device <NUM> via the third network <NUM> and optionally may be connected with the input/output devices <NUM> and other components via the second communication network <NUM>. An engine control unit <NUM> ("ECU" in <FIG>) represents hardware circuitry that includes and/or is connected with one or more processors (for example, one or more microprocessors, field programmable gate arrays, and/or integrated circuits) that generate control signals communicated to an engine of the vehicle (for example, based on input provided by the input/output device <NUM>) in order to control operation of the engine of the vehicle.

An auxiliary load controller <NUM> ("ALC" in <FIG>) represents hardware circuitry that includes and/or is connected with one or more processors (for example, one or more microprocessors, field programmable gate arrays, and/or integrated circuits) that control operation of one or more auxiliary loads of the vehicle. The auxiliary loads may be loads that consume electric current without propelling movement of the vehicle. These auxiliary loads can include, for example, fans or blowers, battery chargers, or the like.

One or more traction motor controllers <NUM> ("TMC" in <FIG>) control operation of traction motors of the vehicle. The traction motor controllers <NUM> represent hardware circuitry that includes and/or is connected with one or more processors (for example, one or more microprocessors, field programmable gate arrays, and/or integrated circuits) that generate control signals to control operation of the traction motors. For example, based on or responsive to a throttle setting selected by an operator input via the input/output devices <NUM> and communicated to the traction motor controllers <NUM> via a fourth communication network <NUM>, the traction motor controllers <NUM> may change a speed at which one or more of the traction motors operate to implement the selected throttle setting.

In the illustrated example, the communication network <NUM> differs from the communication networks <NUM>, <NUM>, <NUM> in that the fourth communication network <NUM> may be a deterministic communication network. The fourth communication network <NUM> is an ARCnet control network, which is a deterministic communication network. A deterministic communication network may be a communication network that ensures successful communication between devices communicating with each other through the network by only allowing certain devices to communicate with each other at different times. In one example, a deterministic communication network <NUM> may only allow a device to communicate with another device during a time period that the device sending the communication has or is associated with a communication token. For example, if the input/output device <NUM> has the token during a first time period, then the input/output device <NUM> can send control signals or other signals to the display devices <NUM>, the traction motor controllers <NUM>, and/or a protocol translator <NUM> during the first time period, but none of the display devices <NUM>, traction motor controllers <NUM>, or protocol translator <NUM> may be allowed to send communications to any other device on the fourth location network <NUM> during this first time period.

During a subsequent, non-overlapping second time period, the protocol translator <NUM> may have the token and is allowed to communicate with other devices. No other components connected with the fourth communication network <NUM> other than the protocol translator <NUM> may be allowed to send communications during the second time period. In contrast, the Ethernet communication networks <NUM>, <NUM>, <NUM> may allow multiple, or all, devices connected to the respective network <NUM>, <NUM>, <NUM> to communicate with each other at the same time. For example, two or more of the components connected to the network <NUM>, <NUM>, and/or <NUM> can communicate with each other at the same time by concurrently or simultaneously sending data packets in the network <NUM>, <NUM>, and/or <NUM>.

The protocol translator <NUM> ("PTP" shown in <FIG>) represents hardware circuitry that converts a protocol of signals communicated by one or more additional devices <NUM> of the vehicle. These devices <NUM> may communicate using signals having a different protocol (e.g., a different syntax, a different format, or the like) than signals communicated by the devices communicating on the deterministic communication network <NUM>. For example, the devices <NUM> may communicate with the protocol translator <NUM> over serial connections <NUM>. The devices <NUM> may include sensors that monitor operation of the vehicle. Examples of these devices <NUM> include a location determining device (for example, a global positioning system receiver), an audio alarm panel ("AAP" in <FIG>), an event recorder or log ("ER" in <FIG>), a distributed power device ("DP" in <FIG>, such as a device that coordinates operations of the vehicle with the operations of other vehicles <NUM>, <NUM> in the same vehicle system), a head of train/end of train communication device ("HOT/EOT" in <FIG>), an airbrake controller ("Air brake" in <FIG>), a signaling controller ("Cab signal" in <FIG>), a fuel gauge or fuel tank sensor ("FTM" in <FIG>), or the like.

As shown in <FIG> , the control system <NUM> includes many communication networks <NUM>, <NUM>, <NUM>, <NUM>, and the serial connections <NUM> of the devices <NUM>. These many communication networks add increased cost and complexity to control system <NUM>, and may provide for additional points of failure in a control system <NUM>. Simply reducing the number of networks in the control system <NUM>, however, may present additional problems. For example, merely connecting the devices that control movement of the vehicle (e.g., the input/output device <NUM>, the display devices <NUM>, the engine control unit <NUM>, the auxiliary load controller <NUM>, and/or the traction motor controllers <NUM>) with an Ethernet network (that may or may not be connected with one or more of the devices <NUM>) could result in so much information or data being communicated in the network that communications with the devices that control movement of the vehicle being prevented, interrupted, or otherwise interfered with.

<FIG> illustrates a vehicle control system <NUM> according to one embodiment of the inventive subject matter described herein. Similar to the control system <NUM> shown in <FIG> , the control system <NUM> is described in connection with a rail vehicle system, but optionally maybe used in connection with another type of vehicle, such as automobile, marine vessel, a mining vehicle, or the like. The control system <NUM> may be disposed onboard a vehicle in a vehicle system that includes the one or more other vehicles <NUM>, <NUM>. The wired connection <NUM> may communicatively coupled with the vehicle on which the control system <NUM> is disposed, as well as the vehicles <NUM>, <NUM>, as described above. The control system <NUM> includes many of the same components described above in connection with the control system <NUM>.

One difference between the control system <NUM> and the control system <NUM> shown in <FIG> is that the devices <NUM> that do not control movement of the vehicle and the devices that control movement of the vehicle (e.g., the engine control unit <NUM>, the auxiliary load controller <NUM>, the traction motor controllers <NUM>, the display devices <NUM>, and input/output devices <NUM>) are all connected with a common (e.g., the same) communication network <NUM>. This communication network <NUM> may be an Ethernet network, such as a control Ethernet network. The network <NUM> described above in connection with <FIG> may also be present in the control system <NUM> and also may be connected with the display devices <NUM> and the input/output devices <NUM>, as described above and shown in <FIG>.

Another difference between the control systems <NUM>, <NUM> is that the devices <NUM> are directly connected with the network <NUM> without having to be connected with the other devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM> by the protocol translator <NUM> shown in <FIG>. This allows for the devices <NUM> to directly communicate with each other and/or with the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM> without having to communicate via the translator <NUM>.

One additional difference between the control systems <NUM>, <NUM> is that the interface gateway <NUM> is not present between the communication networks <NUM>, <NUM>. Instead, one or more linking gateways <NUM> are connected with the communication network <NUM> and or the networks <NUM>, <NUM>, as shown in <FIG>. The linking gateways <NUM> represent hardware circuitry that can control which signals are communicated between the different networks <NUM>, <NUM>, <NUM>. For example, the linking gateways <NUM> can determine whether or not a communication is permitted to pass from one device connected with the network <NUM> to one or more devices connected to the network <NUM>. The linking gateways <NUM> may receive one or more computing cards <NUM> that provide customizable functionality, such as one or more operations or functions desired by a customer or user of the control system <NUM>. In contrast, the interface gateway <NUM> shown in <FIG>, may not be customizable by an end-user, but instead may be instead the operations of the interface gateway <NUM> may be dictated by the manufacturer of the control system <NUM>.

The devices <NUM> can provide data or other information that is useful for the monitoring and control of the vehicle system, but this information and data may be less important to the safe operation of the vehicle and vehicle system relative to communications and information communicated between other devices connected to the same network <NUM> (e.g., the input/output device is <NUM>, the display devices <NUM>, the traction motor controllers <NUM>, auxiliary load controllers <NUM>, and/or the engine control unit <NUM>). For example, while determining the location of the vehicle may be useful from one of the devices <NUM>, it may be more critical are important to the safe operation of the vehicle to be able to ensure communication between the traction motor controller and the input/output devices <NUM>.

Connecting these more critical devices with less critical devices <NUM> on the same Ethernet network <NUM> could present problems with increased risk of communications to and/or from the more critical components not being received or sent to or from these components due to the increased traffic on the network caused by data indicated by the less critical devices <NUM>. While communications to or from the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be assigned with higher priorities than communications with the devices <NUM>, the amount of data being communicated on the Ethernet network <NUM> may, at times, be too large to ensure the communications to or from the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM> are received.

In order to ensure these communications with the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>,<NUM> are sent and/or received in time (for example, that a change to a throttle setting received by the input/output devices <NUM> is received by the traction motor controllers <NUM> within a designated period of time, such as within a few milliseconds), the communication network <NUM> may operate as a data distribution service (DDS) running on a time sensitive network (TSN).

In one embodiment, the data distribution service is an object management group middleware communication standard for communication between and/or among the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> using the network <NUM>. The devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> that communicate using the data distribution service may be referred to as publishers and/or subscribers. A publisher is a dev ice <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> that provides data or information for one or more other devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> to obtain. A subscriber is a device <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> that receives or obtains this data or information (and performs some function using that data or information). The same device <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be both a publisher of some data and a subscriber to other data. For example, the input/output device <NUM> may be a publisher of some data (e.g., instructions received from an operator to change a throttle setting) and a subscriber of other data (e.g., sensor data provided by one or more of the devices <NUM> for display to the operator).

In one embodiment, the data distribution service is used by the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> to communicate data through the network <NUM> that is established according to at least some of the standards developed by the Time-Sensitive Networking Task Group, which may include one or more of the IEEE <NUM> standards. In contrast to an Ethernet network operating without TSN that communicates data frames or packets in a random manner, the TSN network <NUM> may communicate data frames or packets according to a type or category of the data or information being communication. This can ensure that the data is communicated within designated time periods or at designated times. In other Ethernet networks, some data may not reach devices in sufficient time for the devices to operate using the data. With respect to some vehicle control systems, the late arrival of data can have significantly negative consequences, such as an inability to slow or stop movement of a vehicle in time to avoid a collision.

The TSN-based Ethernet network <NUM>, however, can dictate when certain data communications occur to ensure that certain data frames or packets are communicated within designated time periods or at designated times. Data transmissions within the TSN-based Ethernet network <NUM> can be based on times or time slots in which the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> communicate being scheduled for at least some of the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. The communications between or among some of the devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> may be time sensitive communications or include time sensitive data. Time sensitive communications involve the communication of time sensitive data within designated periods of time. For example, data indicative of a change in a brake setting may need to be communicated from the input/output device <NUM> to the traction motor controllers <NUM> within several milliseconds of being sent by the input/output device <NUM> into the network <NUM>. The failure to complete this communication within the designated time limit or period of time may prevent the vehicle from braking in time. Other non-time sensitive communications may be communications that do not necessarily need to be communicated within a designated period of time, such as communication of a location of the vehicle from the GPS receiver, a measurement of the amount of fuel from the fuel sensor, etc. These non-time sensitive communications may be best effort communications or rate constrained communications.

Best effort communications may be communicated within the network <NUM> when there is sufficient bandwidth in the network <NUM> to allow for the communications to be successfully completed without decreasing the available bandwidth in the network <NUM> below a bandwidth threshold needed for the communication of time sensitive communications between publishers and subscribers. For example, if <NUM>% of the available bandwidth in the network <NUM> is needed at a particular time to ensure that communications with the engine control unit <NUM> and traction motor controllers <NUM> successfully occur, then the remaining <NUM>% of the available bandwidth in the network <NUM> may be used for other communications, such as best effort communications with the auxiliary load controller <NUM>. The bandwidth threshold may be a user-selected or default amount of bandwidth. The communication of these best effort communications may be delayed to ensure that the time sensitive communications are not delayed.

Rate constrained communications are communications that are communicated using the remaining amount of bandwidth, if any, in the network <NUM>. For example, a rate constrained communication may be sent between devices using the bandwidth in the network <NUM> that is not used by the time sensitive communications and the best effort communications. If no bandwidth is available (e.g., the time sensitive and best effort communications consume all the available bandwidth), then the rate constrained communication may not occur until more bandwidth is available.

The type of communication with a device may be set by the controller <NUM> and/or the operator of the system <NUM>. For example, the controller <NUM> may designate that all communications to and/or from the engine control unit <NUM>, the traction motor controllers <NUM>, and the input/output devices <NUM> are time sensitive communications, communications to and/or from the display devices <NUM> and auxiliary load controller <NUM> are best effort communications, and the communications to and/or from the devices <NUM> are rate constrained communications. Optionally, the type of information being communicated by these devices may determine the type of communications. For example, the controller <NUM> may establish that control signals (e.g., signals that change operation of a device, such as by increasing or decreasing a throttle of a vehicle, applying brakes of a vehicle, etc.) communicated to the engine control unit <NUM> and/or traction motor controllers <NUM> may be time sensitive communications while status signals (e.g., signals that indicate a current state of a device, such as a location of the vehicle) communicated from the engine control unit <NUM> and/or traction motor controllers <NUM> are best effort or rate constrained communications. In one embodiment, different types of communication can be used to send command signals that control movement or other operation of a vehicle. For example, a command signal can be communicated to a vehicle in order to change a throttle of the vehicle, apply brakes of the vehicle, release brakes of the vehicle, or the like, as a time sensitive communication, a rate constrained communication, and/or a best effort communication.

<FIG> illustrates one embodiment of a method <NUM> for establishing a communication network between devices of a vehicle control system. The method <NUM> may be used to create the network <NUM> shown in <FIG>. At <NUM>, several different vehicle-controlling devices <NUM>, <NUM>, <NUM> are communicatively coupled with each other by an Ethernet network. These devices <NUM>, <NUM>, <NUM> are components that operate to control a vehicle, such as by changing throttle settings, applying or disengaging brakes, or the like, to control movement of the vehicle.

At <NUM>, several non-vehicle-controlling devices <NUM>, <NUM>, <NUM> are communicatively coupled with each other and with the vehicle-controlling devices <NUM>, <NUM>, <NUM> by the same Ethernet network as the vehicle-controlling devices <NUM>, <NUM>, <NUM>. For example, the devices <NUM>, <NUM>, <NUM> may send and/or receive data that is used to monitor and/or diagnose operation of the vehicle, but that is not used to control movement of the vehicle during movement of the vehicle. These devices <NUM>, <NUM>, <NUM> may be connected with the same network as the vehicle-controlling devices <NUM>, <NUM>, <NUM> without a protocol translator being used to change protocols or other aspects of the communications from and/or to the non-vehicle-controlling devices <NUM>, <NUM>, <NUM>.

At <NUM>, the devices and/or communications connected to the same Ethernet network are designated as time sensitive communications, best effort communications, or rate constrained communications. As described above, the time sensitive communications may be communications with devices that need to be completed in a short period of time (e.g., within a designated period of time, such as thirty milliseconds) in order to ensure that the vehicle is safely controlled, while best effort and/or rate constrained communications may not need to be completed within such short periods of time.

At <NUM>, the network is controlled as a data distribution service operating on a time sensitive network. The controller <NUM> can control communications within the network in this manner to provide a flexible Ethernet network that can have additional devices added to and/or devices removed from the network, without sacrificing or risking the time sensitive communications of some devices on the network. For example, the addition of a device <NUM> to the network <NUM> can be completed without the network <NUM> changing the communications to and/or from the devices <NUM>, <NUM>, <NUM> from time sensitive communications to another type of communication. The devices <NUM>, <NUM>, <NUM> may continue communicating with each other and/or other devices using the time sensitive communications of the network <NUM>, while the new and/or other devices can continue communicating as best effort and/or rate constrained communications.

In one embodiment, a data distribution service as described herein can operate on a network that is operating as a time sensitive network implementation of the IEEE <NUM> Ethernet standards.

In one embodiment, a control system includes a controller configured to control communication between or among plural vehicle devices that control operation of at least one vehicle via a network that communicatively couples the vehicle devices. The controller also is configured to control the communication using a data distribution service (DDS) and with the network operating as a time sensitive network (TSN). The controller is configured to direct a first vehicle device of the plural vehicle device to communicate using time sensitive communications; and at least one of: a different, second vehicle device of the plural vehicle devices to communicate using best effort communications; and/or a different, third vehicle device of the plural vehicle devices to communicate using rate constrained communications.

In one embodiment, a control system includes a controller configured to control communication between or among plural vehicle devices that control operation of a vehicle via a network that communicatively couples the vehicle devices. The controller also is configured to control the communication using a data distribution service (DDS) and with the network operating as a time sensitive network (TSN). The controller is configured to direct a first set of the vehicle devices to communicate using time sensitive communications, a different, second set of the vehicle devices to communicate using best effort communications, and a different, third set of the vehicle devices to communicate using rate constrained communications.

In one example, the network is an Ethernet network at least partially disposed onboard the vehicle.

In one example, the vehicle devices include two or more of an input/output device, an engine control unit, a traction motor controller, a display device, an auxiliary load controller, and/or one or more sensors.

In one example, one or more of the engine control unit or the traction motor controller is included in the first set of vehicle devices using the time sensitive communications.

In one example, the controller is configured to direct the first set of the vehicle devices to communicate using the time sensitive communications such that the time sensitive communications are completed using bandwidth of the network while the second and third set of the vehicle devices communicate the best effort communications and the rate constrained communications using a remaining amount of bandwidth of the network that is not used by the time sensitive communications.

In one example, the vehicle is a rail vehicle.

In one example, the vehicle is an automobile.

In one embodiment, a control system includes a controller configured to control communication between plural vehicle devices that control one or more operations of at least one vehicle. The controller also is configured to control the communication between or among the vehicle devices through an Ethernet network while the Ethernet network operates as a time sensitive network (TSN). The controller is configured to direct a first device of the plural vehicle devices to communicate using time sensitive communications, and at least one of: a different, second vehicle device of the plural vehicle devices to communicate using best effort communications; and/or a different, third vehicle device of the plural vehicle devices to communicate using rate constrained communications.

In one embodiment, a control system includes a controller configured to control communication between plural vehicle devices that control one or more operations of a vehicle. The controller also is configured to control the communication between or among the vehicle devices through an Ethernet network while the Ethernet network operates as a time sensitive network (TSN). The controller is configured to direct a first set of the vehicle devices to communicate using time sensitive communications, a different, second set of the vehicle devices to communicate using best effort communications, and a different, third set of the vehicle devices to communicate using rate constrained communications.

In one example, the Ethernet network is at least partially disposed onboard the vehicle.

In one example, the vehicle devices include two or more of an input/output device, an engine control unit, a traction motor controller, a display device, an auxiliary load controller, or one or more sensors.

In one example, the controller is configured to direct the first set of the vehicle devices to communicate using the time sensitive communications such that the time sensitive communications are completed using bandwidth of the Ethernet network while the second and third set of the vehicle devices communicate the best effort communications and the rate constrained communications using a remaining amount of bandwidth of the Ethernet network that is not used by the time sensitive communications.

In one embodiment, a control system includes a controller configured to control communications between plural vehicle devices onboard a vehicle through a time sensitive network (TSN). The controller is configured to direct a first set of the vehicle devices to communicate using time sensitive communications, a different, second set of the vehicle devices to communicate using best effort communications, and a different, third set of the vehicle devices to communicate using rate constrained communications.

In one example, the TSN network is an Ethernet network that is at least partially disposed onboard the vehicle.

In one example, the controller is configured to direct the first set of the vehicle devices to communicate using the time sensitive communications such that the time sensitive communications are completed using bandwidth of the TSN network while the second and third set of the vehicle devices communicate the best effort communications and the rate constrained communications using a remaining amount of bandwidth of the TSN network that is not used by the time sensitive communications.

It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described embodiments (and/or examples thereof) may be used in combination with each other. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the inventive subject matter without departing from its scope. While the dimensions and types of materials described herein are intended to define the parameters of the inventive subject matter, they are by no means limiting and are exemplary embodiments. Many other embodiments will be apparent to one of ordinary skill in the art upon reviewing the above description. The scope of the inventive subject matter should, therefore, be determined with reference to the appended claims. In the appended claims, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein. " Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. Further, the limitations of the following claims are not written in means-plus-function format and are not intended to be interpreted based on <NUM> U. § <NUM>(f), unless and until such claim limitations expressly use the phrase "means for" followed by a statement of function void of further structure.

This written description uses examples to disclose several embodiments of the inventive subject matter and also to enable a person of ordinary skill in the art to practice the embodiments of the inventive subject matter, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the inventive subject matter is defined by the claims.

The foregoing description of certain embodiments of the inventive subject matter will be better understood when read in conjunction with the appended drawings. To the extent that the figures illustrate diagrams of the functional blocks of various embodiments, the functional blocks are not necessarily indicative of the division between hardware circuitry. Thus, for example, one or more of the functional blocks (for example, processors or memories) may be implemented in a single piece of hardware (for example, a general purpose signal processor, microcontroller, random access memory, hard disk, and the like). Similarly, the programs may be stand-alone programs, may be incorporated as subroutines in an operating system, may be functions in an installed software package, and the like. The various embodiments are not limited to the arrangements and instrumentality shown in the drawings.

Claim 1:
A control system (<NUM>) comprising:
a controller (<NUM>) configured to control communication between or among plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) that control operation of at least one vehicle (<NUM>, <NUM>), characterized in that:
the controller (<NUM>) is configured to control the communication via a time sensitive network, TSN, (<NUM>) that communicatively couples the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>),
the controller (<NUM>) configured to control the communication using an object management group middleware communication standard of a data distribution service, DDS, operating in the TSN (<NUM>), the controller (<NUM>) configured to control the communication for the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) to communicate as publishers and subscribers in the DDS, the TSN (<NUM>) configured to communicate different types of information between or among the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) based on whether the communication of the different types of information need to be completed within designated periods of time for safe operation of the at least one vehicle (<NUM>, <NUM>), and
the controller (<NUM>) configured to direct one or more of an engine control unit or a traction motor controller (<NUM>) of the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) to communicate using time sensitive communications, the controller (<NUM>) configured to direct at least one of: (a) a different, second vehicle device of the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) to communicate using best effort communications, or (b) a different, third vehicle device of the plural vehicle devices (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) to communicate using rate constrained communications.