Communications control system with a serial communications interface and a parallel communications interface

Information

  • Patent Grant
  • 10896145
  • Patent Number
    10,896,145
  • Date Filed
    Monday, April 9, 2018
    6 years ago
  • Date Issued
    Tuesday, January 19, 2021
    3 years ago
Abstract
A communications control system is disclosed that includes a serial communications interface and a parallel communications interface for coupling a plurality of input/output modules with a control module. The serial communications interface is configured for connecting the plurality of input/output modules to the control module in parallel to transmit information between the plurality of input/output modules and the control module, and the parallel communications interface is configured for separately connecting the plurality of input/output modules to the control module to transmit information between the plurality of input/output modules and the control module, and to transmit information between individual ones of the plurality of input/output modules. The serial communications interface may comprise a multidrop bus, and the parallel communications interface may comprise a cross switch.
Description
BACKGROUND

Industrial and process control systems include various types of control equipment used in industrial production, such as Supervisory Control and Data Acquisition (SCADA) systems, Distributed Control Systems (DCS), and other control equipment using, for example, Programmable Logic Controllers (PLC). These control systems are typically used in industries including electrical, water, oil, gas, and data. Using information collected from remote stations in the field, automated and/or operator-driven supervisory commands can be transmitted to field control devices. These field devices control local operations, such as opening and closing valves and breakers, collecting data from sensor systems, and monitoring a local environment for alarm conditions.


For example, SCADA systems typically use open-loop control with sites that may be widely separated geographically, using potentially unreliable or intermittent low-bandwidth/high-latency links. These systems use Remote Terminal Units (RTUs) to send supervisory data to a control center. The RTUs may have a limited capacity for local controls when the master station is not available. DCS systems are generally used for real time data collection and control with high-bandwidth, low-latency data networks. PLCs typically provide Boolean logic operations, timers, continuous control, and so on. However, as industrial control systems evolve, new technologies are combining aspects of these various types of control systems. For instance, Programmable Automation Controllers (PACs) can include aspects of SCADA, DCS, and PLCs.


SCADA systems can be used with industrial processes, including manufacturing, production, power generation, fabrication, and refining. They can also be used with infrastructure processes, including water treatment and distribution, wastewater collection and treatment, oil and gas pipelines, electrical power transmission and distribution, wind farms, large communication systems, and so forth. Further, SCADA systems can be used in facility processes for buildings, airports, ships, space stations, and the like (e.g., to monitor and control Heating, Ventilation, and Air Conditioning (HVAC) equipment and energy consumption). DCS systems are generally used in large campus industrial process plants, such as oil and gas, refining, chemical, pharmaceutical, food and beverage, water and wastewater, pulp and paper, utility power, mining, metals, and so forth. PLCs are typically used in industrial sectors and with critical infrastructures.


SUMMARY

A communications control system is disclosed. In one or more implementations, the communications control system includes a serial communications interface and a parallel communications interface for coupling a plurality of input/output modules with a control module. The serial communications interface is configured for connecting the plurality of input/output modules to the control module in parallel to transmit information between the plurality of input/output modules and the control module, and the parallel communications interface is configured for separately connecting the plurality of input/output modules to the control module to transmit information between the plurality of input/output modules and the control module, and to transmit information between individual ones of the plurality of input/output modules. The serial communications interface may comprise a multidrop bus, and the parallel communications interface may comprise a cross switch.


This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.





DRAWINGS

The Detailed Description is described with reference to the accompanying figures. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.



FIG. 1 is a block diagram illustrating a communications control system in accordance with example implementations of the present disclosure.



FIG. 2 is a circuit diagram illustrating a switch fabric for a communications control system in accordance with example implementations of the present disclosure.



FIG. 3 is an isometric view illustrating a communications control system in accordance with example implementations of the present disclosure.



FIG. 4 is a side elevation view of the communications control system illustrated in FIG. 3.



FIG. 5 is an end view of the communications control system illustrated in FIG. 3.



FIG. 6 is a partial cross-sectional end view of the communications control system illustrated in FIG. 3.



FIG. 7 is a cross-sectional view illustrating an input/output module for the communications control system illustrated in FIG. 3.



FIG. 8 is an isometric view illustrating a support frame for the communications control system illustrated in FIG. 3.



FIG. 9 is a flow diagram illustrating a process for furnishing communication between multiple input/output modules and one or more communications/control modules in accordance with example implementations of the present disclosure.





DETAILED DESCRIPTION

Overview


Process control systems typically use two types of busses: multidrop busses and parallel backplanes. A multidrop serial bus with a master and multiple slave devices may be used for distributed control systems where reliability is critical, such as safety-critical systems, and the like. However, as additional devices are connected to a multidrop serial bus, data transfer speeds between components within the system may slow considerably. A parallel backplane may be used where multiple devices are connected in parallel, such as with programmable logic controllers. Parallel backplanes offer increased data transfer speeds compared to multidrop serial busses. However, parallel backplanes do not offer redundancy for safety-critical systems.


Accordingly, communications control systems are described that include a switch fabric having a serial communications interface (e.g., a serial or Multidrop Bus (MDB) with a master and multiple slaves) and a parallel communications interface (e.g., a parallel or point-to-point bus implemented using a cross switch, or the like). The serial communications interface and the parallel communications interface may be used for connecting multiple Input/Output (I/O) modules to communications/control modules, and to one another.


In some implementations, the serial communications interface and the parallel communications interface may be formed on a single printed circuit board. The serial communications interface may be configured for connecting the plurality of input/output modules to a redundant control module in parallel, and the parallel communications interface may be configured for separately connecting the plurality of input/output modules to the redundant control module. Information transmitted via the serial communications interface and/or the parallel communications interface may be packetized. The control module may comprise a network interface for transmitting information collected from the plurality of input/output modules via a network, and so forth. Additionally, the communications control system may include a power module for supplying electrical power to at least one of the plurality of input/output modules.


A communications control system configured in accordance with the present disclosure may provide deterministic behavior (e.g., with respect to data turnaround time) and reliability for critical systems, while still providing speed and scalability. The communications control system may provide fault isolation, along with data turnaround times that do not increase as additional components are added to a system. Further, the communications control system may allow components connected to the system to communicate directly with one another using the communications control system. Communications control systems configured in this manner may be implemented in various systems that may otherwise use a parallel backplane.


Example Implementations


FIGS. 1 through 8 illustrate an example communications control system 100 in accordance with the present disclosure. In implementations, the communications control system 100 may be configured for use with process control systems technology, and so forth. For example, the communications control system 100 may be used with a distributed control system comprised of controller elements and subsystems, where the subsystems are controlled by one or more controllers distributed throughout the system. The communications control system 100 includes a switch fabric 102 comprising a serial communications interface 104 and a parallel communications interface 106 for furnishing communications with a number of I/O modules 108.


The serial communications interface 104 may be implemented using a group of connectors connected in parallel with one another. For example, the serial communications interface 104 may be implemented using a multidrop bus 110, or the like. In implementations, the multidrop bus 110 may be used for configuration and diagnostic functions of the I/O modules 108. The parallel communications interface 106 allows multiple signals to be transmitted simultaneously over multiple dedicated high speed parallel communication channels. For instance, the parallel communications interface 106 may be implemented using a cross switch 112, or the like.


In a particular implementation, as described in FIG. 2, the parallel communications interface 106 can be implemented using a four (4) wire full duplex cross switch 112 with a dedicated connection to each I/O module 108. For example, the cross switch 112 can be implemented as a programmable cross switch connecting point-to-point busses and allowing traffic between the I/O modules 108. The cross switch 112 may be configured by a master device, such as a communications/control module 114. For example, a communications/control module 114 may configure one or more sets of registers included in the cross switch 112 to control traffic between the I/O modules 108. In implementations, a communications/control module 114 may comprise a rule set dictating how the I/O modules 106 are interconnected. For example, a communications/control module 114 may comprise a set of registers, where each register defines the operation of a particular switch (e.g., with respect to how packets are forwarded, and so forth). Thus, the cross switch 112 may not necessarily auto-configure, instead implementing a configuration provided by a communications/control module 114. However, this configuration is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, in other implementations, the cross switch 112 may auto-configure.


The parallel communications interface 106 may be used for data collection from the I/O modules 108. Further, because each I/O module 108 has its own private bus to the master (e.g., communications/control modules 114), each I/O module 108 can communicate with the master at the same time. Thus, the total response time for the communications control system 100 may be limited to that of the slowest I/O module 108, instead of the sum of all slave devices.


In implementations, the switch fabric 102, the serial communications interface 104, and the parallel communications interface 106 may be implemented in a single, monolithic circuit board 116. However, this configuration is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, the serial communications interface 104 and the parallel communications interface 106 may be implemented using different arrangements of multiple components, such as multiple discrete semiconductor devices for implementing the serial communications interface 104 and the parallel communications interface 106 separately, and so forth.


The switch fabric 102 may be configured for connecting one or more I/O modules 108 and transmitting data to and from the I/O modules 108. The I/O modules 108 may comprise input modules, output modules, and/or input and output modules. For instance, input modules can be used to receive information from input instruments in the process or the field, while output modules can be used to transmit instructions to output instruments in the field. For example, an I/O module 108 can be connected to a process sensor, such as a sensor 118 for measuring pressure in piping for a gas plant, a refinery, and so forth. In implementations, the I/O modules 116 may be used to collect data and control systems in applications including, but not necessarily limited to: industrial processes, such as manufacturing, production, power generation, fabrication, and refining; infrastructure processes, such as water treatment and distribution, wastewater collection and treatment, oil and gas pipelines, electrical power transmission and distribution, wind farms, and large communication systems; facility processes for buildings, airports, ships, and space stations (e.g., to monitor and control Heating, Ventilation, and Air Conditioning (HVAC) equipment and energy consumption); large campus industrial process plants, such as oil and gas, refining, chemical, pharmaceutical, food and beverage, water and wastewater, pulp and paper, utility power, mining, metals; and/or critical infrastructures.


In implementations, the I/O module 108 may be configured to convert analog data received from the sensor 118 to digital data (e.g., using Analog-to-Digital Converter (ADC) circuitry, and so forth). An I/O module 108 may also be connected to a motor 120 and configured to control one or more operating characteristics of the motor 120, such as motor speed, motor torque, and so forth. Further, the I/O module 108 may be configured to convert digital data to analog data for transmission to the motor 120 (e.g., using Digital-to-Analog (DAC) circuitry, and so forth). In implementations, one or more of the I/O modules 108 may comprise a communications module configured for communicating via a communications sub-bus, such as an Ethernet bus, an H1 field bus, a Process Field Bus (PROFIBUS), a Highway Addressable Remote Transducer (HART) bus, a Modbus, and so forth. Further, two or more of the I/O modules 108 can be used to provide fault tolerant and redundant connections for a communications sub-bus.


Each I/O module 108 may be provided with a unique identifier (ID) for distinguishing one I/O module 108 from another I/O module 108. In implementations, an I/O module 108 may be identified by its ID when it is connected to the communications control system 100. Multiple I/O modules 108 can be used with the communications control system 100 to provide redundancy. For example, two or more I/O modules 108 can be connected to the sensor 118 and/or the motor 120, as described in FIG. 1. Each I/O module 108 can include one or more ports 122 furnishing a physical connection to hardware and circuitry included with the I/O module 108, such as a Printed Circuit Board (PCB) 124, and so forth.


One or more of the I/O modules 108 may include an interface for connecting to other networks, including but not necessarily limited to: a wide-area cellular telephone network, such as a 3G cellular network, a 4G cellular network, or a Global System for Mobile communications (GSM) network; a wireless computer communications network, such as a Wi-Fi network (e.g., a Wireless LAN (WLAN) operated using IEEE 802.11 network standards); a Personal Area Network (PAN) (e.g., a Wireless PAN (WPAN) operated using IEEE 802.15 network standards); a Wide Area Network (WAN); an intranet; an extranet; an internet; the Internet; and so on. Further, one or more of the I/O modules 108 may include a connection for connecting an I/O module 108 to a computer bus, and so forth.


The switch fabric 102 may be coupled with one or more communications/control modules 114 for monitoring and controlling the I/O modules 108, and for connecting the I/O modules 108 together. The communications/control module(s) 114 may be used to configure the cross switch 112. For example, a communications/control module 114 may update a routing table when an I/O module 108 is connected to the communications control system 100 based upon a unique ID for the I/O module 108. Further, when multiple redundant I/O modules 108 are used, each communications/control module 114 can implement mirroring of informational databases regarding the I/O modules 108 and update them as data is received from and/or transmitted to the I/O modules 108. In some implementations, two or more communications/control modules 114 may be used to provide redundancy.


Data transmitted using the switch fabric 102 may be packetized, i.e., discrete portions of the data may be converted into data packets comprising the data portions along with network control information, and so forth. The communications control system 100 may use one or more protocols for data transmission, including a bit-oriented synchronous data link layer protocol such as High-Level Data Link Control (HDLC). In a specific instance, the communications control system 100 may implement HDLC according to an International Organization for Standardization (ISO) 13239 standard, or the like. Further, two or more communications/control modules 114 can be used to implement redundant HDLC. However, it should be noted that HDLC is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, the communications control system 100 may use other various communications protocols in accordance with the present disclosure.


One or more of the communications/control modules 114 may be configured for exchanging information with components used for monitoring and/or controlling the instrumentation connected to the switch fabric 102 via the I/O modules 108, such as one or more control loop feedback mechanisms/controllers 126. In implementations, a controller 126 can be configured as a microcontroller/Programmable Logic Controller (PLC), a Proportional-Integral-Derivative (PID) controller, and so forth. One or more of the communications/control modules 114 may include a network interface 128 for connecting the communications control system 100 to a controller 126 via a network 130. In implementations, the network interface 128 may be configured as a Gigabit Ethernet interface for connecting the switch fabric 102 to a Local Area Network (LAN). Further, two or more communications/control modules 114 can be used to implement redundant Gigabit Ethernet. However, it should be noted that Gigabit Ethernet is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, the network interface 128 may be configured for connecting the communications control system 100 to other various networks, including but not necessarily limited to: a wide-area cellular telephone network, such as a 3G cellular network, a 4G cellular network, or a Global System for Mobile communications (GSM) network; a wireless computer communications network, such as a Wi-Fi network (e.g., a Wireless LAN (WLAN) operated using IEEE 802.11 network standards); a Personal Area Network (PAN) (e.g., a Wireless PAN (WPAN) operated using IEEE 802.15 network standards); a Wide Area Network (WAN); an intranet; an extranet; an internet; the Internet; and so on. Additionally, the network interface 128 may be implemented using computer bus. For example, the network interface 128 can include a Peripheral Component Interconnect (PCI) card interface, such as a Mini PCI interface, and so forth. Further, the network 130 may be configured to include a single network or multiple networks across different access points.


The communications control system 100 may include one or more power modules 132 for supplying electrical power to field devices via the I/O modules 108. One or more of the power modules 132 may include an AC-to-DC (AC/DC) converter for converting Alternating Current (AC) (e.g., as supplied by AC mains, and so forth) to Direct Current (DC) for transmission to a field device, such as the motor 120 (e.g., in an implementation where the motor 120 comprises a DC motor). Two or more power modules 132 can be used to provide redundancy. For example, as shown in FIG. 1, two power modules 132 can be connected to each of the I/O modules 108 using a separate power backplane 134 for each power module 132.


The communications control system 100 may be implemented using a support frame 136. The support frame 136 may be used to support and/or interconnect the communications/control module(s) 114, the power module(s) 132, the switch fabric 102, the power backplane(s) 134, and/or the I/O modules 108. The circuit board 116 may be mounted to the support frame 136 using a fastener such as, for example, double sided tape, adhesive, or mechanical fasteners (e.g., screws, bolts, etc.). The support frame 136 may include slots 138 to provide registration for the I/O modules 108, such as for aligning connectors of the I/O modules 108 with connectors included with the circuit board 116 and/or connectors of a power backplane 134. For example, an I/O module 108 may include connectors 140 having tabs/posts 142 for inserting into slots 138 and providing alignment of the I/O module 108 with respect to the circuit board 116. In implementations, one or more of the connectors 140 may be constructed from a thermally conductive material (e.g., metal) connected to a thermal plane of PCB 124 to conduct heat generated by components of the PCB 124 away from the PCB 124 and to the support frame 136, which itself may be constructed of a thermally conductive material (e.g., metal). Further, the communications control system 100 may associate a unique physical ID with each physical slot 138 to uniquely identify each I/O module 108 coupled with a particular slot 138. For example, the ID of a particular slot 138 can be associated with an I/O module 108 coupled with the slot 138 and/or a second ID uniquely associated with the I/O module 108. Further, the ID of a particular I/O module 108 can be used as the ID for a slot 138 when the I/O module 108 is coupled with the slot 138. The support frame 136 can be constructed for cabinet mounting, rack mounting, wall mounting, and so forth.


It should be noted that while the communications control system 100 is described in the accompanying figures as including one switch fabric 102, more than one switch fabric 102 may be provided with communications control system 100. For example, two or more switch fabrics 102 may be used with the communications control system 100 (e.g., to provide physical separation between redundant switch fabrics 102, and so forth). Each one of the switch fabrics 102 may be provided with its own support frame 136. Further, while both the serial communications interface 104 and the parallel communications interface 106 are described as included in a single switch fabric 102, it will be appreciated that physically separate switch fabrics may be provided, where one switch fabric includes the serial communications interface 104, and another switch fabric includes the parallel communications interface 106.


Example Process

Referring now to FIG. 9, example techniques for furnishing communication between multiple input/output devices and one or more communications/control modules using a communications control system that includes a serial communications interface and a parallel communications interface for coupling a plurality of input/output modules with a control module are described.



FIG. 9 depicts a process 900, in an example implementation, for furnishing a communications control system, such as the communications control system 100 illustrated in FIGS. 1 through 8 and described above. In the process 900 illustrated, input/output modules are coupled with a control module (Block 910). For example, with reference to FIGS. 1 through 8, the switch fabric 102 may be configured for connecting the I/O modules 108 to the communications/control modules 114, and transmitting data to and from the I/O modules 108. The input/output modules are connected to the control module in parallel for transmitting information between the input/output modules and the control module (Block 920). In one or more implementations, the input/output modules can be connected to the control module using a multidrop bus (Block 922). For instance, with continuing reference to FIGS. 1 through 8, the serial communications interface 104 of the switch fabric 102 may be implemented using a multidrop bus 110. The input/output modules are separately connected to the control module for transmitting information between the input/output modules and the control module, and for transmitting information between individual ones of the input/output modules (Block 930). In one or more implementations, the input/output modules can be separately connected to the control module using a cross switch (Block 932). For example, with continuing reference to FIGS. 1 through 8, the parallel communications interface 106 of the switch fabric 102 may be implemented using a cross switch 112 comprising a four (4) wire full duplex system with a dedicated connection to each I/O module 108.


In some implementations, the input/output modules are coupled with a redundant control module (Block 940). The input/output modules can be connected to the redundant control module in parallel (Block 950). The input/output devices can also be separately connected to the redundant control module (Block 960). For instance, with continuing reference to FIGS. 1 through 8, two or more communications/control modules 114 can be used to implement a redundant HDLC data link layer protocol. It should be noted that connecting the input/output modules to one redundant control module is provided by way of example only and is not meant to be restrictive of the present disclosure. Thus, the input/output modules may be connected to more than one redundant control module in parallel and/or separately.


In some implementations, the control module can be coupled with a network for transmitting information collected from the input/output modules via the network (Block 970). For example, with continuing reference to FIGS. 1 through 8, one or more of the communications/control modules 114 may include a network interface 128 for connecting the communications control system 100 to a controller 126 via a network 130. The input/output modules can also be coupled with a power module for supplying electrical power to the input/output modules (Block 980). For instance, with continuing reference to FIGS. 1 through 8, one or more power modules 132 may be included with the communications control system 100 for supplying electrical power to field devices via the I/O modules 108.


CONCLUSION

Although the subject matter has been described in language specific to structural features and/or process operations, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims
  • 1. A communications control system comprising: a control module;a plurality of input/output modules coupled with the control module;a serial communications interface configured for connecting the plurality of input/output modules to the control module in parallel, the serial communications interface configured for transmitting information between the plurality of input/output modules and the control module;a parallel communications interface configured for separately connecting the plurality of input/output modules to the control module, the parallel communications interface configured for transmitting information between the plurality of input/output modules and the control module, and transmitting information between individual ones of the plurality of input/output modules; anda support frame to facilitate interconnection of the plurality of input/output modules and the control module, the support frame comprising a plurality of slots, each slot of the plurality of slots for receiving a respective one of the plurality of input/output modules, wherein the control module is configured to assign each input/output module a unique identifier associated with a physical location where the input/output module is physically connected to the control module.
  • 2. The communications control system as recited in claim 1, wherein the serial communications interface comprises a multidrop bus.
  • 3. The communications control system as recited in claim 1, wherein the parallel communications interface comprises a cross switch.
  • 4. The communications control system as recited in claim 1, wherein the serial communications interface is configured for connecting the plurality of input/output modules to a redundant control module in parallel, and the parallel communications interface is configured for separately connecting the plurality of input/output modules to the redundant control module.
  • 5. The communications control system as recited in claim 1, wherein information transmitted via at least one of the serial communications interface or the parallel communications interface is packetized.
  • 6. The communications control system as recited in claim 1, wherein the control module comprises a network interface for transmitting information collected from the plurality of input/output modules via a network.
  • 7. The communications control system as recited in claim 1, further comprising a power module for supplying electrical power to at least one of the plurality of input/output modules.
  • 8. A process comprising: coupling a plurality of input/output modules with a control module using a support frame to facilitate interconnection of the plurality of input/output modules and the control module, the support frame comprising a plurality of slots, each slot of the plurality of slots for receiving a respective one of the plurality of input/output modules;connecting the plurality of input/output modules to the control module in parallel for transmitting information between the plurality of input/output modules and the control module;separately connecting the plurality of input/output modules to the control module for transmitting information between the plurality of input/output modules and the control module, and transmitting information between individual ones of the plurality of input/output modules; andassigning each input/output module a unique identifier associated with a physical location where the input/output module is physically connected to the control module.
  • 9. The process as recited in claim 8, wherein connecting the plurality of input/output modules to the control module in parallel comprises connecting the plurality of input/output modules to the control module using a multidrop bus.
  • 10. The process as recited in claim 8, wherein separately connecting the plurality of input/output modules to the control module comprises separately connecting the plurality of input/output modules to the control module using a cross switch.
  • 11. The process as recited in claim 8, further comprising: coupling the plurality of input/output modules with a redundant control module;connecting the plurality of input/output modules to the redundant control module in parallel; andseparately connecting the plurality of input/output modules to the redundant control module.
  • 12. The process as recited in claim 8, wherein at least one of transmitting information between the plurality of input/output modules and the control module or transmitting information between individual ones of the plurality of input/output modules comprises packetizing the transmitted information.
  • 13. The process as recited in claim 8, further comprising coupling the control module with a network for transmitting information collected from the plurality of input/output modules via the network.
  • 14. The process as recited in claim 8, further comprising coupling at least one of the plurality of input/output modules with a power module for supplying electrical power to the at least one of the plurality of input/output modules.
  • 15. A communications control system comprising: a control module;a plurality of input/output modules coupled with the control module;a multidrop bus configured for connecting the plurality of input/output modules to the control module in parallel, the multidrop bus configured for transmitting information between the plurality of input/output modules and the control module;a cross switch configured for separately connecting the plurality of input/output modules to the control module, the cross switch configured for transmitting information between the plurality of input/output modules and the control module, and transmitting information between individual ones of the plurality of input/output modules; anda support frame to facilitate interconnection of the plurality of input/output modules and the control module, the support frame comprising a plurality of slots, each slot of the plurality of slots for receiving a respective one of the plurality of input/output modules, wherein the control module is configured to assign each input/output module a unique identifier associated with a physical location where the input/output module is physically connected to the control module.
  • 16. The communications control system as recited in claim 15, wherein the multidrop bus is configured for connecting the plurality of input/output modules to a redundant control module in parallel, and the cross switch is configured for separately connecting the plurality of input/output modules to the redundant control module.
  • 17. The communications control system as recited in claim 15, wherein information transmitted via at least one of the multidrop bus or the cross switch is packetized.
US Referenced Citations (294)
Number Name Date Kind
1778549 Conner Oct 1930 A
1961013 Saraceno May 1934 A
2540575 Finizie Feb 1951 A
3702983 Chace et al. Nov 1972 A
4079440 Ohnuma et al. Mar 1978 A
4082984 Iwata Apr 1978 A
4337499 Cronin et al. Jun 1982 A
4403286 Fry Sep 1983 A
4508414 Kusui et al. Apr 1985 A
4628308 Robert Dec 1986 A
4656622 Lea Apr 1987 A
4672529 Kupersmit Jun 1987 A
4691384 Jobe Sep 1987 A
4882702 Stuger et al. Nov 1989 A
4929939 Varma et al. May 1990 A
4932892 Hatch Jun 1990 A
5013247 Watson May 1991 A
5229652 Hough Jul 1993 A
5325046 Young et al. Jun 1994 A
5378166 Gallagher, Sr. Jan 1995 A
5385487 Beitman Jan 1995 A
5385490 Demeter et al. Jan 1995 A
5388099 Poole Feb 1995 A
5422558 Stewart Jun 1995 A
5469334 Balakrishnan Nov 1995 A
5519583 Kolling et al. May 1996 A
5546463 Caputo et al. Aug 1996 A
5590284 Crosetto Dec 1996 A
5602754 Beatty et al. Feb 1997 A
5603044 Annapareddy et al. Feb 1997 A
5719483 Abbott et al. Feb 1998 A
5724349 Cloonan et al. Mar 1998 A
5735707 O'Groske et al. Apr 1998 A
5773962 Nor Jun 1998 A
5860824 Fan Jan 1999 A
5896473 Kaspari Apr 1999 A
5909368 Nixon et al. Jun 1999 A
5951666 Ilting et al. Sep 1999 A
5958030 Kwa Sep 1999 A
5963448 Flood et al. Oct 1999 A
5980312 Chapman et al. Nov 1999 A
6009410 LeMole et al. Dec 1999 A
6046513 Jouper et al. Apr 2000 A
6124778 Rowley et al. Sep 2000 A
6178474 Hamano et al. Jan 2001 B1
6219789 Little et al. Apr 2001 B1
6220889 Ely et al. Apr 2001 B1
6347963 Falkenberg et al. Feb 2002 B1
6393565 Lockhart et al. May 2002 B1
6435409 Hu Aug 2002 B1
6453416 Epstein Sep 2002 B1
6480963 Tachibana et al. Nov 2002 B1
6490176 Holzer et al. Dec 2002 B2
6574681 White et al. Jun 2003 B1
6597683 Gehring et al. Jul 2003 B1
6643777 Chu Nov 2003 B1
6680904 Kaplan et al. Jan 2004 B1
6695620 Huang Feb 2004 B1
6799234 Moon et al. Sep 2004 B1
6812803 Goergen Nov 2004 B2
6814580 Li et al. Nov 2004 B2
6828894 Sorger et al. Dec 2004 B1
6840795 Takeda et al. Jan 2005 B1
6988162 Goergen Jan 2006 B2
7164255 Hui Jan 2007 B2
7172428 Huang Feb 2007 B2
7200692 Singla et al. Apr 2007 B2
7234963 Huang Jun 2007 B1
7254452 Davlin et al. Aug 2007 B2
7402074 LeBlanc et al. Jul 2008 B2
7415368 Gilbert et al. Aug 2008 B2
7426585 Rourke Sep 2008 B1
7460482 Pike Dec 2008 B2
7510420 Mori Mar 2009 B2
7526676 Chou et al. Apr 2009 B2
7529862 Isani May 2009 B2
7536548 Batke et al. May 2009 B1
7554288 Gangstoe et al. Jun 2009 B2
7587481 Osburn, III Sep 2009 B1
7614909 Lin Nov 2009 B2
7619386 Sasaki et al. Nov 2009 B2
7622994 Galal Nov 2009 B2
7660998 Walmsley Feb 2010 B2
7670190 Shi et al. Mar 2010 B2
7685349 Allen et al. Mar 2010 B2
7730304 Katsube et al. Jun 2010 B2
7746846 Boora et al. Jun 2010 B2
7761640 Hikabe Jul 2010 B2
7774074 Davlin et al. Aug 2010 B2
7790304 Hendricks et al. Sep 2010 B2
7811136 Hsieh et al. Oct 2010 B1
7815471 Wu Oct 2010 B2
7822994 Hamaguchi Oct 2010 B2
7839025 Besser et al. Nov 2010 B2
7872561 Matumoto Jan 2011 B2
7948758 Buhler et al. May 2011 B2
7960870 Besser et al. Jun 2011 B2
7971052 Lucas et al. Jun 2011 B2
8013474 Besser et al. Sep 2011 B2
8019194 Morrison et al. Sep 2011 B2
8032745 Bandholz et al. Oct 2011 B2
8062070 Jeon et al. Nov 2011 B2
8125208 Gyland Feb 2012 B2
8132231 Amies et al. Mar 2012 B2
8143858 Tsugawa et al. Mar 2012 B2
8149587 Baran et al. Apr 2012 B2
8157569 Liu Apr 2012 B1
8181262 Cooper et al. May 2012 B2
8189101 Cummings et al. May 2012 B2
8212399 Besser et al. Jul 2012 B2
8266360 Agrawal Sep 2012 B2
8281386 Milligan et al. Oct 2012 B2
8287306 Daugherty et al. Oct 2012 B2
8295770 Seil et al. Oct 2012 B2
8310380 Aria et al. Nov 2012 B2
8380905 Djabbari et al. Feb 2013 B2
8390441 Covaro et al. Mar 2013 B2
8465762 Lee et al. Jun 2013 B2
8480438 Mattson Jul 2013 B2
8560147 Taylor et al. Oct 2013 B2
8587318 Chandler et al. Nov 2013 B2
8651874 Ku et al. Feb 2014 B2
8677145 Maletsky et al. Mar 2014 B2
8694770 Osburn, III Apr 2014 B1
8777671 Huang Jul 2014 B2
8862802 Calvin et al. Oct 2014 B2
8868813 Calvin et al. Oct 2014 B2
8971072 Calvin et al. Mar 2015 B2
9071082 Nishibayashi et al. Jun 2015 B2
9318917 Kubota et al. Apr 2016 B2
9436641 Calvin et al. Sep 2016 B2
9465762 Calvin et al. Oct 2016 B2
9467297 Clish et al. Oct 2016 B2
9812803 Toyoda et al. Nov 2017 B2
10103875 Roth et al. Oct 2018 B1
20020070835 Dadafshar Jun 2002 A1
20020080828 Ofek et al. Jun 2002 A1
20020080829 Ofek et al. Jun 2002 A1
20020084698 Kelly et al. Jul 2002 A1
20020086678 Salokannel et al. Jul 2002 A1
20020095573 O'Brien Jul 2002 A1
20020097031 Cook et al. Jul 2002 A1
20020116619 Maruyama et al. Aug 2002 A1
20020171525 Kobayashi et al. Nov 2002 A1
20020182898 Takahashi et al. Dec 2002 A1
20020189910 Yano et al. Dec 2002 A1
20030005289 Gougeon et al. Jan 2003 A1
20030040897 Murphy et al. Feb 2003 A1
20030074489 Steger et al. Apr 2003 A1
20030094855 Lohr et al. May 2003 A1
20030105601 Kobayashi et al. Jun 2003 A1
20030137277 Mori et al. Jul 2003 A1
20030166397 Aura Sep 2003 A1
20030202330 Lopata et al. Oct 2003 A1
20030204756 Ransom et al. Oct 2003 A1
20050001589 Edington et al. Jan 2005 A1
20050019143 Bishman Jan 2005 A1
20050091432 Adams et al. Apr 2005 A1
20050102535 Patrick et al. May 2005 A1
20050144437 Ransom et al. Jun 2005 A1
20050144440 Catherman et al. Jun 2005 A1
20050162019 Masciarelli et al. Jul 2005 A1
20050182876 Kim et al. Aug 2005 A1
20050189910 Hui Sep 2005 A1
20050229004 Callaghan Oct 2005 A1
20060015590 Patil et al. Jan 2006 A1
20060020782 Kakii Jan 2006 A1
20060108972 Araya May 2006 A1
20060119315 Sasaki et al. Jun 2006 A1
20060155990 Katsube et al. Jul 2006 A1
20060156415 Rubinstein et al. Jul 2006 A1
20070072442 DiFonzo et al. Mar 2007 A1
20070076768 Chiesa et al. Apr 2007 A1
20070123304 Pattenden et al. May 2007 A1
20070123316 Little May 2007 A1
20070143838 Milligan et al. Jun 2007 A1
20070174524 Kato Jul 2007 A1
20070177298 Jaatinen et al. Aug 2007 A1
20070194944 Galera et al. Aug 2007 A1
20070214296 Takamatsu et al. Sep 2007 A1
20070229302 Penick et al. Oct 2007 A1
20070260897 Cochran Nov 2007 A1
20080067874 Tseng Mar 2008 A1
20080077976 Schulz Mar 2008 A1
20080123669 Oliveti et al. May 2008 A1
20080140888 Blair et al. Jun 2008 A1
20080181316 Crawley et al. Jul 2008 A1
20080189441 Jundt et al. Aug 2008 A1
20080194124 Di Stefano Aug 2008 A1
20080303351 Jansen et al. Dec 2008 A1
20090036164 Rowley Feb 2009 A1
20090061678 Minoo et al. Mar 2009 A1
20090066291 Tien et al. Mar 2009 A1
20090083843 Wilkinson, Jr. et al. Mar 2009 A1
20090091513 Kuhn Apr 2009 A1
20090092248 Rawson Apr 2009 A1
20090121704 Shibahara May 2009 A1
20090204458 Wiese et al. Aug 2009 A1
20090217043 Metke et al. Aug 2009 A1
20090222885 Batke et al. Sep 2009 A1
20090234998 Kuo Sep 2009 A1
20090239468 He et al. Sep 2009 A1
20090245245 Malwankar et al. Oct 2009 A1
20090254655 Kidwell et al. Oct 2009 A1
20090256717 Iwai Oct 2009 A1
20090278509 Boyles et al. Nov 2009 A1
20090287321 Lucas et al. Nov 2009 A1
20090288732 Gielen Nov 2009 A1
20100052428 Imamura et al. Mar 2010 A1
20100066340 Delforge Mar 2010 A1
20100082869 Lloyd et al. Apr 2010 A1
20100122081 Sato et al. May 2010 A1
20100148721 Little Jun 2010 A1
20100149997 Law et al. Jun 2010 A1
20100151816 Besehanic et al. Jun 2010 A1
20100153751 Tseng et al. Jun 2010 A1
20100197366 Pattenden et al. Aug 2010 A1
20100197367 Pattenden et al. Aug 2010 A1
20100233889 Kiani et al. Sep 2010 A1
20100262312 Kubota et al. Oct 2010 A1
20110010016 Giroti Jan 2011 A1
20110066309 Matsuoka et al. Mar 2011 A1
20110074349 Ghovanloo Mar 2011 A1
20110080056 Low Apr 2011 A1
20110082621 Berkobin et al. Apr 2011 A1
20110089900 Hogari Apr 2011 A1
20110140538 Jung et al. Jun 2011 A1
20110150431 Klappert Jun 2011 A1
20110185196 Asano et al. Jul 2011 A1
20110196997 Ruberg et al. Aug 2011 A1
20110197009 Agrawal Aug 2011 A1
20110202992 Xiao et al. Aug 2011 A1
20110285847 Riedel et al. Nov 2011 A1
20110291491 Lemmens et al. Dec 2011 A1
20110296066 Xia Dec 2011 A1
20110313547 Hernandez et al. Dec 2011 A1
20120028498 Na et al. Feb 2012 A1
20120046015 Little Feb 2012 A1
20120053742 Tsuda Mar 2012 A1
20120102334 O'Loughlin et al. Apr 2012 A1
20120124373 Dangoor et al. May 2012 A1
20120143586 Vetter et al. Jun 2012 A1
20120159210 Hosaka Jun 2012 A1
20120236769 Powell et al. Sep 2012 A1
20120242459 Lambert Sep 2012 A1
20120265361 Billingsley et al. Oct 2012 A1
20120271576 Kamel et al. Oct 2012 A1
20120274273 Jacobs et al. Nov 2012 A1
20120282805 Ku et al. Nov 2012 A1
20120284354 Mukundan et al. Nov 2012 A1
20120284514 Lambert Nov 2012 A1
20120295451 Hyun-Jun et al. Nov 2012 A1
20120297101 Neupartl et al. Nov 2012 A1
20120311071 Karaffa et al. Dec 2012 A1
20120322513 Pattenden et al. Dec 2012 A1
20120328094 Pattenden et al. Dec 2012 A1
20130011719 Yasui et al. Jan 2013 A1
20130026973 Luke et al. Jan 2013 A1
20130031382 Jau et al. Jan 2013 A1
20130070788 Deiretsbacher et al. Mar 2013 A1
20130170258 Calvin et al. Jul 2013 A1
20130173832 Calvin et al. Jul 2013 A1
20130211547 Buchdunger et al. Aug 2013 A1
20130212390 Du et al. Aug 2013 A1
20130224048 Gillingwater et al. Aug 2013 A1
20130233924 Burns Sep 2013 A1
20130244062 Teramoto et al. Sep 2013 A1
20130290706 Socky et al. Oct 2013 A1
20130291085 Chong et al. Oct 2013 A1
20140015488 Despesse Jan 2014 A1
20140068712 Frenkel et al. Mar 2014 A1
20140075186 Austen Mar 2014 A1
20140091623 Shippy et al. Apr 2014 A1
20140095867 Smith et al. Apr 2014 A1
20140097672 Takemura et al. Apr 2014 A1
20140129162 Hallman et al. May 2014 A1
20140131450 Gordon et al. May 2014 A1
20140142725 Boyd May 2014 A1
20140280520 Baier et al. Sep 2014 A1
20140285318 Audeon et al. Sep 2014 A1
20140312913 Kikuchi et al. Oct 2014 A1
20140327318 Calvin Nov 2014 A1
20140335703 Calvin et al. Nov 2014 A1
20140341220 Lessmann Nov 2014 A1
20150046701 Rooyakkers et al. Feb 2015 A1
20150048684 Rooyakkers et al. Feb 2015 A1
20150115711 Kouroussis et al. Apr 2015 A1
20150365240 Callaghan Dec 2015 A1
20160065656 Patin et al. Mar 2016 A1
20160069174 Cannan et al. Mar 2016 A1
20160172635 Stimm et al. Jun 2016 A1
20160224048 Rooyakkers et al. Aug 2016 A1
20160301695 Trivelpiece et al. Oct 2016 A1
20180190427 Rooyakkers et al. Jul 2018 A1
Foreign Referenced Citations (142)
Number Date Country
2162746 Apr 1994 CN
1408129 Apr 2003 CN
1440254 Sep 2003 CN
1571335 Jan 2005 CN
1702582 Nov 2005 CN
1839581 Sep 2006 CN
101005359 Jul 2007 CN
101069407 Nov 2007 CN
101262401 Sep 2008 CN
101322089 Dec 2008 CN
101447861 Jun 2009 CN
10153380 Sep 2009 CN
101576041 Nov 2009 CN
201515041 Jun 2010 CN
101809557 Aug 2010 CN
101919139 Dec 2010 CN
101977104 Feb 2011 CN
102035220 Apr 2011 CN
102237680 Nov 2011 CN
202205977 Apr 2012 CN
102480352 May 2012 CN
1934766 Jun 2012 CN
102546707 Jul 2012 CN
102809950 Dec 2012 CN
102812578 Dec 2012 CN
103376766 Oct 2013 CN
103682883 Mar 2014 CN
103701919 Apr 2014 CN
104025387 Sep 2014 CN
203932181 Nov 2014 CN
104185969 Dec 2014 CN
204243110 Apr 2015 CN
105556762 May 2016 CN
102013213550 Jan 2015 DE
473336 Apr 1992 EP
507360 Oct 1992 EP
1176616 Jan 2002 EP
1241800 Sep 2002 EP
1246563 Oct 2002 EP
1571559 Jul 2005 EP
1877915 Jan 2008 EP
1885085 Feb 2008 EP
1885085 Jun 2008 EP
2179364 Apr 2010 EP
2317743 May 2011 EP
2450921 May 2012 EP
2557657 Feb 2013 EP
2557670 Feb 2013 EP
2613421 Oct 2013 EP
2777796 Sep 2014 EP
2806319 Nov 2014 EP
S59-074413 May 1984 JP
S59-177226 Nov 1984 JP
H0163190 Apr 1989 JP
04245411 Sep 1992 JP
H05346809 Dec 1993 JP
07105328 Apr 1995 JP
07-320963 Aug 1995 JP
08-037121 Feb 1996 JP
08098274 Apr 1996 JP
08241824 Sep 1996 JP
08322252 Dec 1996 JP
09182324 Jul 1997 JP
1189103 Mar 1999 JP
11235044 Aug 1999 JP
H11230504 Aug 1999 JP
11-098707 Sep 1999 JP
11-312013 Sep 1999 JP
2000252143 Sep 2000 JP
2001292176 Oct 2001 JP
2001307055 Nov 2001 JP
2002134071 May 2002 JP
2002280238 Sep 2002 JP
2002343655 Nov 2002 JP
2002359131 Dec 2002 JP
3370931 Jan 2003 JP
2003047912 Feb 2003 JP
2003068543 Mar 2003 JP
2003142327 May 2003 JP
2003152703 May 2003 JP
2003152708 May 2003 JP
2003216237 Jul 2003 JP
2004501540 Jan 2004 JP
2004303701 Oct 2004 JP
2005038411 Feb 2005 JP
2005513956 May 2005 JP
2005151720 Jun 2005 JP
2005250833 Sep 2005 JP
2005275777 Oct 2005 JP
2005531235 Oct 2005 JP
2005327231 Nov 2005 JP
2005332406 Dec 2005 JP
2006060779 Mar 2006 JP
2006180460 Jul 2006 JP
2006223950 Aug 2006 JP
2006238274 Sep 2006 JP
2007034711 Feb 2007 JP
2007096817 Apr 2007 JP
2007519150 Jul 2007 JP
2007238696 Sep 2007 JP
2007252081 Sep 2007 JP
2008215028 Sep 2008 JP
2008257707 Oct 2008 JP
2008538668 Oct 2008 JP
4245411 Mar 2009 JP
2009157913 Jul 2009 JP
2009163909 Jul 2009 JP
2010503134 Jan 2010 JP
4439340 Mar 2010 JP
2010515407 May 2010 JP
2010135903 Jun 2010 JP
2011078249 Apr 2011 JP
2011217037 Oct 2011 JP
2011223544 Nov 2011 JP
5013019 Aug 2012 JP
2012190583 Oct 2012 JP
2012195259 Oct 2012 JP
2013021798 Jan 2013 JP
2013170258 Sep 2013 JP
2014507721 Mar 2014 JP
2014080952 May 2014 JP
2015023375 Feb 2015 JP
2016512039 Apr 2016 JP
6189479 Aug 2017 JP
10-20020088540 Nov 2002 KR
20050014790 Feb 2005 KR
20060034244 Apr 2006 KR
100705380 Apr 2007 KR
100807377 Feb 2008 KR
201310344 Mar 2013 TW
2005070733 Aug 2005 WO
2006059195 Jun 2006 WO
2007041866 Apr 2007 WO
2007148462 Dec 2007 WO
2008083387 Jul 2008 WO
2009032797 Mar 2009 WO
2011104935 Sep 2011 WO
2013033247 Mar 2013 WO
2013102069 Jul 2013 WO
2014179556 Nov 2014 WO
2014179566 Nov 2014 WO
2015020633 Feb 2015 WO
Non-Patent Literature Citations (123)
Entry
International Search Report dated Apr. 29, 2013 for Appln. No. PCT/US2012/072056.
Office Action for Japanese Application No. 2014-159475, dated Jul. 18, 2018.
Office Action for Japanese Application No. 2014-159475, dated Feb. 15, 2019.
Office Action for Japanese Application No. 2016-512039, dated Jun. 5, 2018.
Office Action for Japanese Application No. 2016-512039, dated Feb. 5, 2019.
International Search Report and Written Opinion for PCT/US2014/036368, dated Sep. 12, 2014.
Office Action for Chinese Appln No. 201380079515.9, dated Nov. 16, 2017.
Office Action for Chinese Appin No. 2013800795 dated Aug. 7, 2018.
Office Action for Chinese Appin No. 201380079515.9, dated Feb. 25, 2019.
Supplementary Search Report in European Application No. 13890953.6, dated Jan. 26, 2017.
Office Action for Japanese Application No. 2016-533280, dated Jun. 28, 2017.
Office Action for Japanese Application No. 2016-533280, dated Apr. 11, 2018.
Office Action for Japanese Application No. 2016-533280, dated Jan. 7, 2019.
International Search Report and Written Opinion for PCT/US2013/053721, dated May 12, 2014.
Office Action for Chinese Appln No. 201380079514.4, dated Feb. 5, 2018.
Office Action for Chinese Appln No. 201380079514.4, dated Nov. 5, 2018.
Examination Report for European Application No. 13891327.2, dated Sep. 26, 2018.
Supplementary Search Report for European Application No. 13891327.2, dated Jan. 10, 2017.
Reason for Rejection in Japanese Patent Application No. 2016-533279, dated Aug. 13, 2018.
Notice of Reasons for Rejection in Japanese Patent Application No. 2016-533279, dated Jul. 13, 2017.
Notice of Reason for Rejection in Japanese Patent Application No. 2016-533279, dated Mar. 1, 2018.
Fabien Fleuot, “Raspberry Pi + Mihini, Controlling an off-the-grid Electrical Installation, Part I,” Apr. 11, 2014, XP055290314.
Generex Systems Gmbh, “BACS—Battery Analysis & Care System,” Aug. 17, 2014, XP055290320.
Siemens, “Uninterruptible 24 V DC Power Supply High-Performance, communicative and integrated in TIA,” Mar. 31, 2015, XP055290324.
“Introduction to Cryptography,” Network Associates, Inc., PGP 6.5.1, 1990-1999, Retrieved @ (ftp://ftp.pgpi.org/pub/pgp/6.5/docs/english/IntroToCrypto.pdf) on Mar. 17, 2016, (refer to pp. 16-20).
Stouffer, et al. “Guide to Industrial Control Systems (ICS) Security,” NIST, Special Pub. 800-82, Jun. 2011, (refer to pp. 2-1 to 2-10).
Rodrigues, A. et al., “Scada Security Device,” Proceedings of the Seventh Annual Workshop on Cyber Security and Information Intelligence Research, CSIIRW '11, Jan. 1, 2011, XP055230335.
Zafirovic-Vukotic, M. et al., “Secure SCADA network supporting NERC CIP”, Power & Energy Society General Meeting, 2009, PES '09, IEEE, Piscataway, NJ, USA, Jul. 26, 2009, pp. 1-8, XP031538542.
Roman Kieinerman; Daniel Feldman (May2011), Power over Ethernet (PoE): An Energy-Efficient Alternative (PDF), Marvell, retrieved Aug. 25, 2018 @ http://www.marvell.com/switching/assets/Marvell-PoE-An-Energy-Efficient-Alternative. pdf (Year: 2011).
Molva, R. Ed et al., “Internet security architecture”, Computer Networks, Elsevier Science Publishers B. V., Amsterdam, NL, vol. 31, No. 8, Apr. 23, 1999, pp. 787-804, XP004304518.
Rodrigues, A., “SCADA Security Device: Design and Implementation”, Master of Science Thesis, Wichita State University, Dec. 2011.
CGI, White Paper on “Public Key Encryption and Digital Signature: How do they work?”, 2004 (refer to pp. 3-4).
Baran, M.E. et al., “Overcurrent Protection on Voltage-Source-Converter-Based Multiterminal DC Distribution Systems,” IEEE Transactions on Power Delivery, Jan. 2007.
Office Action for Canadian Application No. 2,875,517, dated May 4, 2015.
Office Action for Chinese Application No. 201410802889.5, dated Jul. 26, 2018.
Search Report for European Application No. 14196406.4, dated Nov. 4, 2015.
European Search Report for European Application No. 14196406.4, dated Sep. 23, 2015.
Extended Search Report for European Application No. 16165112.0, dated Sep. 6, 2016.
Examination Report for European Application No. 16165112.0, dated Feb. 16, 2018.
Notice of Reason for Rejection for Japanese Application No. 2014-243827, dated Jan. 24, 2019.
Office Action for Chinese Application No. 2015103905202.2, dated Jun. 20, 2018.
Office Action for Chinese Application No. 2015103905202.2, dated Mar. 6, 2019.
Search Report for European Application No. 15175744.0, dated Apr. 26, 2016.
Partial Search Report for European Application No. 15175744.0, dated Dec. 14, 2015.
Office Action for Canadian Application No. 2,875,518, dated Jun. 3, 2015.
Office Action for Canadian Application No. 2,875,518, dated Apr. 22, 2016.
European Search Report for EP Application No. 14196408.0, dated Nov. 24, 2015.
Office Action for Canadian Application No. 2,875,515, dated Jul. 5, 2017.
Office Action for Canadian Application No. 2,875,515, dated Feb. 10, 2017.
Office Action for Canadian Application No. 2,875,515, dated Jun. 1, 2016.
Office Action for Canadian Application No. 2,875,515, dated Oct. 6, 2016.
Office Action for Chinese Application No. 201410799473.2, dated Oct. 12, 2018.
Examination Report for European Application No. 14196409.8, dated Jan. 22, 2018.
Search Report for European Application No. 14196409.8, dated May 19, 2016.
Notice of Reason for Rejection for Japanese Application No. 2014-243830, dated Sep. 21, 2018.
Office Action for Canadian Application No. 2,920,133, dated Jan. 30, 2017.
Office Action for Canadian Application No. 2,920,133, dated Oct. 19, 2016.
Search Report for European Application No. 16154943.1, dated Jun. 17, 2016.
Partial European Search Report in European Application No. 17208183.8, dated Mar. 28, 2018.
Examination Report in European Application No. 17208183.8, dated Jun. 22, 2018.
Examination Report in European Application No. 17208183.8, dated Feb. 27, 2019.
Office Action for Chinese Appln. No. 201610239130.X, dated Feb. 14, 2018.
Office Action for Chinese Appln. No. 201610239130.X, dated Aug. 2, 2017.
Office Action for Chinese Application No. 201280065564.2, dated Aug. 3, 2016.
Office Action for Chinese Application No. 201280065564.2, dated Feb. 28, 2017.
Office Action for Chinese Application No. 201280065564.2, dated Oct. 19, 2017.
Partial Supplementary European Search Report in Application No. 12862174.5, dated Nov. 3, 2015.
European Search Report in Application No. 12862174.5, dated Feb. 15, 2016.
European Search Report in Application No. 17178867.2, dated Nov. 2, 2017.
Office Action for Japanese Application No. 2014-550508, dated Dec. 2, 2016.
Office Action for Japanese Application No. 2014-550508, dated Sep. 15, 2017.
Office Action for CN Appln. No. 201410182071.8, dated Mar. 1, 2017.
Office Action for Chinese Application No. 201410383686.7, dated May 31, 2017.
Office Action for Chinese Application No. 201410383686.7, dated Feb. 23, 2018.
Office Action for Chinese Application No. 201480034066.0, dated May 3, 2017.
Search Report and Opinion for European Application No. 14166908.8, dated Jan. 7, 2015.
Extended Search Report for European Application No. 14180106.8, dated Jul. 13, 2015.
Examination Report for European Application No. 14180106.8, dated Jun. 28, 2017.
Supplementary Search Report for European Application No. 14791210.9, dated Dec. 6, 2016.
Office Action for Japanese Application No. 2014-080952, dated May 2, 2018.
Office Action for apanese Application No. 2014-080952, dated Jan. 7, 2019.
Canadian Office Action for Application No. 2920133 dated Jan. 30, 2017.
Canadian Office Action for Application No. 2920133 dated Oct. 19, 2016.
European Search Report dated Dec. 2, 2015 for EP Application No. 14196408.0.
European search report for European Patent Application No. EP14196406 dated Oct. 2, 2015, 6 pages.
European Search Report published Nov. 4, 2015 in Application No. EP14196406.4.
Examination Report for European Application No. 17178867.2, dated Mar. 13, 2019.
Examination Report for European Application No. 16165112.0, dated Apr. 17, 2019.
Supplementary European Search Report for European Patent Application No. EP 14791210 dated Dec. 16, 2016, 11 pages.
Examination Report for European Patent Application No. 16154943.1, dated May 16, 2019.
Extended European Search Report for Application No. EP14180106.8, dated Aug. 12, 2015.
Extended European Search Report for European Patent Application No. EP 14196409 dated May 31, 2016, 10pages.
Extended European Search Report for European Patent Application No. EP 16154943 dated Jun. 29, 2016, 9pages.
Extended European Search Report for European Patent Application No. EP 18176358 dated Sep. 11, 2018, 11 pages.
International Search Report and Written Opinion dated May 12, 2014 in International Application# PCT/US2013/053721.
Notice of Reason for Rejection for Japanese Patent Application No. 2014-243830, dated Jul. 10, 2019.
Notice of Reason for Rejection for JP Patent Application No. 2018-109151, dated Jun. 25, 2019.
Office Action for Chinese Application No. 2015103905202.2, dated Aug. 6, 2019.
Siemens AG: “ERTEC 400 I Enhanced Real-Time Ethernet Controller I Handbuch”, No. Version 1.2.2 pp. 1-98, XP002637652, Retrieved from the Internet: URL:http:llcache.automation.siemens.comldniiDUIDUxNDgzNwAA_21631481_HBIERTEC400_Handbuch_V122.pdf [retrieved on May 2, 2011].
Office Action for Canadian Application No. 2,875,515 dated Feb. 17, 2016.
Office Action for Chinese Patent Application 201410802889.5, dated May 7, 2019.
Office Action for Canadian Application No. 2,920,133, dated Apr. 14, 2016.
Office Action for Chinese Application No. 20141079995.2, dated Jul. 3, 2019.
Partial European Search Report for European Patent Application No. EP 15175744 dated Jan. 4, 2016, 7 pages.
Partial Supplementary European Search Report dated Nov. 10, 2015 in Application# EP12862174.5.
Supplementary European Search Report for European Patent Application No. EP 13890953 dated Feb. 6, 2017, 9 pages.
Office Action for Japanese Application No. 2015-136186, dated Oct. 10, 2019.
Office Action for Japanese Application No. 2014-159475, dated Jun. 11, 2018.
Decision of Rejection for Patent Application No. 2014-243827, dated Nov. 28, 2019.
Decision of Rejection for Chinese Application No. 2015103905202.2, dated Nov. 5, 2019.
Examination Report for European Patent Application No. 1720883.8, dated Oct. 29, 2019.
Notice of Reason for Rejection for Patent Application No. 2016-021763, dated Nov. 27, 2019.
Office Action for Chinese Patent Application No. 201610236358.3, dated Sep. 4, 2019.
Office Action forChinese Patent Application 201410802689.5, dated Dec. 4, 2019.
Office Action from Chinese Patent Application No. 201610229230.4, dated Oct. 24, 2019.
Office Action from EP Application No. 14196406.4, dated Jul. 29, 2019.
Notice of Reason for Rejection for Japanese Application No. 2016-080207, dated Jun. 4, 2020.
Decision of Rejection for Japanese Application No. 2014-243830, dated Mar. 18, 2020.
Reason for Rejection for Japanese Application No. 2015-136186, dated May 7, 2020.
Summons to attend oral proceedings for European Application No. 14196409.8, dated Nov. 13, 2019.
Office Action for Japanese Application No. 2016-533280, dated Jun. 29, 2020.
Office Action for Chinese Patent Application No. 201610236358.3; dated Jun. 24, 2020.
Office Action from Chinese Patent Application No. 201610229230.4, dated Jul. 15, 2020.
Related Publications (1)
Number Date Country
20180300284 A1 Oct 2018 US
Continuations (4)
Number Date Country
Parent 15491562 Apr 2017 US
Child 15948418 US
Parent 15289613 Oct 2016 US
Child 15491562 US
Parent 14502006 Sep 2014 US
Child 15289613 US
Parent 13341176 Dec 2011 US
Child 14502006 US