Industrial control systems (ICS), which may include process control systems (PCS), distributed control systems (DCS), programmable logic controller (PLC)-based systems supervisory control and data acquisition (SCADA) systems, and the like are instrumental in the production of goods and provision of essential services. Using information collected from remote stations in an industrial or infrastructure environment, automated and/or operator-driven supervisory commands can be transmitted to remote station control devices. These control devices can control various local operations, such as opening and/or closing valves and circuit breakers, operating solenoids, collecting data from sensor systems, and monitoring a local environment for alarm conditions.
A secure industrial control system is disclosed. In one or more implementations, the secure industrial control system includes a security credential source, a security credential implementer, and at least two industrial elements. The security credential source is configured to generate unique security credentials. The security credential implementer is configured to provision respective ones of the at least two industrial elements with a unique security credential generated by the security credential source.
In one or more implementations, the secure industrial control system includes at least one control module provisioned with a first unique security credential. The system further includes at least one input/output module provisioned with a second unique security credential. The at least one control module and the at least one input/output module are operable to bi-directionally communicate with one another based on the first and second unique security credentials.
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.
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.
Securing cyber-to-physical systems requires the integration of design and planning, as well as the efforts of operating engineers having cyber security and support skills. Industrial control systems (ICS) were initially envisioned to operate in isolated and trusted domains. However, expanded connectivity technology has boosted productivity, allowed for leveraging of information from both a plant floor and from around the world, thereby leaving ICS potentially exposed to a larger number of people. Unfortunately, this expanded connectivity technology has outpaced corresponding cyber security solutions and has taxed people with the engineering understanding and security skills to keep critical systems safe from advanced cyber threats.
A secure industrial control system is disclosed herein. In one or more implementations, the secure industrial control system includes a security credential source, a security credential implementer, and industrial elements of the industrial control system. In embodiments, the industrial elements may include a control module (e.g., communications control module) and an input/output module. The security credential source is configured to generate unique security credentials (e.g., keys, certificates, etc.). The security credential implementer is configured to provision the industrial elements with the unique security credential generated by the security credential source. For instance, the communications control module and the input/output module may each be provisioned with unique security credentials. An authentication process for authenticating the industrial elements implemented in the industrial control system may be performed based upon the security credentials. For example, in embodiments, the communications control module and the input/output module may be operable to bi-directionally communicate with one another based on the security credentials (e.g., based upon the authentication process). Further, in the secure industrial control system disclosed herein, multiple (e.g., every) industrial elements (e.g., module, power supply, physical interconnect device, etc.) of the system may be provisioned with security credentials for providing security at multiple (e.g., all) levels of the system. Still further, the industrial elements may be provisioned with the security credentials (e.g., keys, certificates, etc.) during manufacture (e.g., at birth), and may be managed from birth by a key management entity of the industrial control system for promoting security of the industrial control system.
Referring generally to
SCADA systems can be used with industrial processes, including manufacturing, production, power generation, fabrication, and refining. SCADA system 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.
In embodiments, the industrial control system 100 includes a control and input/output (I/O) sub-system 102, as shown in
As shown, the communications control modules 106 are communicatively coupled via communication links 114 to the power modules 110, for allowing communications and/or power signal transmission. In embodiments, each communications control module 106 is connected to each power module 110 and to each input/output module 108.
One or more input/output modules 108 are connected to (e.g., communicatively coupled with) the one or more field devices 112. The one or more input/output modules 108 may comprise input modules and/or output modules (e.g., may be configured for receiving inputs and/or providing outputs). The one or more field devices 112 may include an input instrument, such as a sensor, which may be used for functions such as measuring pressure in piping for a gas plant, a refinery, and so forth. In such instances, the input modules of the input/output modules 108 can be used to receive information from input instruments, such as the sensor, in the process or the field. The input/output modules 108 may be configured to convert analog data received from the sensor of the field device 112 to digital data (e.g., using Analog-to-Digital Converter (ADC) circuitry, and so forth). The power modules 110 are configured for supplying electrical power to the field devices 112 via the input/output modules 108.
The input/output modules 108, when configured as output modules, can be used to transmit instructions to output instruments of the field devices 112. For example, the field devices 112 may include an output instrument, such as a motor. In such implementations, the input/output modules 108 may be connected to the motor and configured to control one or more operating characteristics of the motor, such as motor speed, motor torque, and so forth. Further, the input/output modules 108 may be configured to convert digital data to analog data for transmission to the motor (e.g., using Digital-to-Analog (DAC) circuitry, and so forth). In embodiments, one or more of the input/output modules 108 may include 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 input/output modules 108 can be used to provide fault tolerant and redundant connections for the communications sub-bus.
The input/output modules 108 may be configured 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.
The input/output modules 108 can be connected to the control and input/output sub-system 102 using one or more connectors. In embodiments, the communications link(s) 114 may be configured for use with any systems technology, such as a telecommunications network technology, computer network technology, process control systems technology, and so forth. The communications link(s) 114 may be implemented in a single, monolithic circuit board. However, this configuration is provided by way of example only and is not meant to be restrictive of the present disclosure.
Respective ones of the input/output module 108 can include one or more ports furnishing a physical connection to hardware and circuitry included with the input/output module 108, such as a printed circuit board (PCB), and so forth. The input/output modules 108 may also 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. The input/output modules 108 may further include a connection for connecting an input/output module 108 to a computer bus, and so forth.
The communications links 114 may be coupled with one or more communications control modules 106, which can be used as master devices for monitoring and controlling the input/output modules 108, and for connecting the input/output modules 108 together. For example, a communications control module 106 may update a routing table when an input/output module 108 is connected to the control and input/output sub-system 102 based upon a unique ID for the input/output module 108. Further, when multiple redundant input/output modules 108 are used, each communications control module 106 can implement mirroring of informational databases regarding the input/output modules 108 and update them as data is received from and/or transmitted to the input/output modules 108. In some implementations, two or more communications control modules 106 may be used to provide redundancy.
Data transmitted using communications links 114 may be packetized (e.g., discrete portions of the data may be converted into data packets comprising the data portions along with network control information, and so forth). The control and input/output sub-system 102 and/or communications links 114 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 embodiments, the control and input/output sub-system 102 and/or communications links 114 may implement HDLC according to an International Organization for Standardization (ISO) 13239 standard, or the like. Further, two or more communications control modules 106 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 control and input/output sub-system 102 may use other various communications protocols in accordance with the present disclosure.
The communications control modules 106 may be configured for exchanging information with components used for monitoring and/or controlling instrumentation connected to the communications links 114 via the input/output modules 108, such as one or more control loop feedback mechanisms/controllers. For example, a controller 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 106 may include a network interface for connecting the control and input/output sub-system 102 to a controller via a network. In embodiments, the network interface may be configured as a Gigabit Ethernet interface for connecting the control and input/output sub-system 102 to a Local Area Network (LAN). Further, two or more communications control modules 106 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 may be configured for connecting the control and input/output sub-system 102 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 may be implemented using computer bus. For example, the network interface can include a Peripheral Component Interconnect (PCC) card interface, such as a Mini PCI interface, and so forth. Further, the network may be configured to include a single network or multiple networks across different access points.
One or more of the power modules 110 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 112, such as a motor (e.g., in an implementation where the motor comprises a DC motor). Two or more power modules 110 can be used to provide redundancy. For example, two power modules 110 can be connected to each of the input/output modules 108 using a separate (e.g., redundant) power backplane for each power module 110. In embodiments, the power backplane(s) may be connected to one or more of the input/output modules using connectors/connector assemblies.
In embodiments, the control and input/output sub-system 102 may be implemented using a support frame. The support frame may be used to support and/or interconnect the communications control modules 106, the power modules 110, the communications links 114, the power backplane(s), and/or the input/output modules 108. For example, the communications links 114 may be comprised of a circuit board. The circuit board may be mounted to the support frame. Additionally, the connectors may be mounted to the support frame.
The secure industrial control system 100 further includes a control network 116. The control network 116 is communicatively coupled with the control and input/output sub-system 102 via communications links 118. The control network 116 may include one or more switches 120. In embodiments, the switches 120 are telecommunications devices that receive data (e.g., messages) from devices to which they are connected and selectively transmit the data to only a device for which the data is meant. The switches 120 are configured for connecting the communications control modules 106 to one or more workstations 122 of the control network 116 via communications links (118,124). In implementations, the workstations 122 may comprise microcomputers configured for technical or scientific applications. The workstations 122 may be connected to a local area network and may run multi-user operating systems. In embodiments, the workstations 122 may be mainframe computer terminals or personal computers (PCs) connected to a network. In implementations, the workstations 122 are connected to the control and input/output sub-system 102 via the switches 120.
As shown, the industrial control system 100 may include a first network 126. In embodiments, the first network 126 may be a corporate network. The corporate network may comprise a computer network made up of an interconnection of local area networks (LANs) within a limited geographical area. In examples, the switches 120 include network interfaces for connecting the switches 120 to the first network 126 via communications links 128. In implementations, the workstations 122 may be connected to (e.g., communicatively coupled with) the first network (e.g., corporate network) 126 via the switches 120. The workstations 122 collect information which can be used to generate/provide commands to field control devices, such as the input/output modules 108.
One or more components of the industrial control system 100, including the communications control modules 106; the input/output modules 108; the power modules 110; the field devices 112; the switches 120; and/or the workstations 122 may include and/or may be connected to a controller (e.g., a microcontroller). In implementations, one or more of the communications links (114, 118, 124, 128) may include and/or may be connected to a controller. For example, physical interconnect devices, such as cable assemblies, of the communications links (114, 118, 124, 128) may include and/or may be connected to a controller. In some implementations, all of the components and all physical interconnect devices (e.g., cable assemblies) connecting the components of the industrial control system 100 may each include controllers. In embodiments, the controller(s) connected to or included in the physical interconnect devices may be one-wire encryption chips, which allow for implementation of authentication between a component (e.g., an input/output module 108) and the physical interconnect device (e.g., cable assembly) connected to that component as discussed in more detail below. For example, microprocessor secure encrypted technology may be built into the cable assembly and keyed to a specific component of the industrial control system 100. This configuration provides security for the system 100 when a user installs (e.g., plugs) the cable assembly into a component which is not configured to be connected with that cable assembly. In embodiments, a one-wire serial key (e.g., one-wire embedded key) is implemented in one or more (e.g., each of) the physical interconnect devices. In further embodiments, actuators or valves that interconnect to the industrial control system 100 may include security credentials (e.g., keys, certificates).
The secure industrial control system 100 includes a security credential source 101, a security credential implementer 103, and the industrial elements of the industrial control system 100 (e.g., of the control and I/O subsystem 102). As noted, the industrial elements may include a control module (e.g., communications control module 106), an input/output module 108, and a power module (e.g., smart power module 110). The security credential source 101 is configured to generate unique security credentials (e.g., keys, certificates, etc.). The security credential implementer 103 is configured to provision the industrial elements with the unique security credential generated by the security credential source 101. For instance, the communications control module 106, the input/output module 108, and/or the smart power module 110 may each be provisioned with unique security credentials (e.g., keys and certificates). An authentication process for authenticating the industrial elements implemented in the industrial control system may be performed based upon the security credentials
Communication between one or more of the components and/or physical interconnect devices (e.g., cable assemblies) of the industrial control system 100 may include an authentication process. The authentication process may be performed for authenticating a component and/or physical interconnect device implemented in the industrial control system 100. In implementations, the authentication process may utilize security credentials associated with the component and/or physical interconnect device for authenticating that component and/or physical interconnect device. For example, the security credentials may include encryption keys, certificates (e.g., public key certificates, digital certificates, identity certificates, security certificates, asymmetric certificates, standard certificates, non-standard certificates) and/or identification numbers. In embodiments, controllers (e.g., secure microcontrollers) which are included in/connected to the components and/or physical interconnect devices of the industrial control system 100 may be configured for performing the authentication process for promoting secure communication between the components and/or physical interconnect devices.
In implementations, one or more of the industrial elements (e.g., components and/or physical interconnect devices) of the industrial control system 100 are provisioned with their own unique security credentials. For example, one or more of the industrial elements of the industrial control system 100 are provisioned with their own unique sets of certificates, encryption keys and/or identification numbers when the industrial elements are manufactured (e.g., the individual sets of keys and certificates are defined at the birth of the industrial element). The sets of certificates, encryption keys and/or identification numbers are configured for providing/supporting strong encryption. The encryption keys may be implemented with standard (e.g., commercial off-the-shelf (COTS)) encryption algorithms, such as National Security Agency (NSA) algorithms, National Institute of Standards and Technology (NIST) algorithms, or the like.
Based upon the results of the authentication process, the industrial element being authenticated may be activated, partial functionality of the industrial element may be enabled or disabled within the industrial control system 100, complete functionality of the industrial element may be enabled within the industrial control system 100, and/or functionality of the industrial element within the industrial control system 100 may be completely disabled (e.g., no communication between that industrial element and other industrial elements of the industrial control system 100.
In embodiments, the keys, certificates and/or identification numbers associated with an industrial element of the industrial control system 100 may specify the original equipment manufacturer (OEM) of that industrial element. As used herein, the term “original equipment manufacturer” or “OEM” may be defined as an entity that physically manufactures the device (e.g., industrial element) and/or a supplier of the device such as an entity that purchases the device from a physical manufacturer and sells the device. Thus, in embodiments, a device may be manufactured and distributed (sold) by an OEM that is both the physical manufacturer and the supplier of the device. However, in other embodiments, a device may be distributed by an OEM that is a supplier, but is not the physical manufacturer. In such embodiments, the OEM may cause the device to be manufactured by a physical manufacturer (e.g., the OEM may purchase, contract, order, etc. the device from the physical manufacturer). Additionally, where the OEM comprises a supplier that is not the physical manufacturer of the device, the device may bear the brand of the supplier instead of brand of the physical manufacturer. For example, in instances where industrial elements (e.g., module) are associated with a particular OEM that is a supplier but not the physical manufacturer, the industrial element's keys, certificates and/or identification numbers may specify that origin. During authentication of an industrial element of the industrial control system 100, when a determination is made that an industrial element being authenticated was manufactured or supplied by an entity that is different than the OEM of one or more other industrial elements of the industrial control system 100, then the functionality of that industrial element may be at least partially disabled within the industrial control system 100. For example, limitations may be placed upon communication (e.g., data transfer) between that industrial element and other industrial elements of the industrial control system 100, such that the industrial element may not worklfunction within the industrial control system 100. When one of the industrial elements of the industrial control system 100 requires replacement, this feature may prevent a user of the industrial control system 100 from unknowingly replacing the industrial element with a non-homogenous industrial element (e.g., an industrial element having a different origin (a different OEM) than the remaining industrial elements of the industrial control system 100) and implementing the industrial element in the industrial control system 100. In this manner, the techniques described herein may prevent the substitution of industrial elements (which may furnish similar functionality) of other OEM's into a secure industrial control system 100 manufactured and/or supplied by the originating OEM (the OEM that originally supplied the industrial control system 100 to the user) in place of industrial elements manufactured and/or supplied by the originating OEM without the approval of the originating OEM.
In another instance, a user may attempt to implement an incorrectly designated (e.g., miss-marked) industrial element within the industrial control system 100. For example, the miss-marked industrial element may have a physical indicia marked upon it which falsely indicates that the industrial element is associated with a same OEM as the OEM of the other industrial elements of the industrial control system 100. In such instances, the authentication process implemented by the industrial control system 100 may cause the user to be alerted that the industrial element is counterfeit. This process may also promote improved security for the industrial control system 100 since counterfeit industrial elements are often a vehicle by which malicious software can be introduced into the industrial control system 100. In embodiments, the authentication process provides a secure air gap for the industrial control system 100, ensuring that the secure industrial control system is physically isolated from insecure networks.
In implementations, the secure industrial control system 100 includes a key management entity (e.g., key management system 130). As shown in
In embodiments, the key management system 130 comprises a secure entity such as an entity located in a secure facility). The key management system 130 may be remotely located from the control and input/output sub-system 102, the control network 116 and/or the corporate network 126. For example, a firewall 132 may separate the key management system 130 from the control and input/output sub-system 102, the control network 116 and/or the corporate network 126. In implementations, the firewall 132 may be a software or hardware-based network security system that controls ingoing and outgoing network traffic by analyzing data packets and determining whether the data packets should be allowed through or not, based on a rule set. The firewall 132 thus establishes a barrier between a trusted, secure internal network (e.g., corporate network 114, control network 106) and another network that is not assumed to be secure and trusted (e.g., cloud, Internet). In embodiments, the firewall 132 allows for selective (e.g., secure) communication between the key management system 130 and one or more of the control and input/output sub-system 102, the control network 116 and/or the corporate network 126. In examples, one or more firewalls 132 may be implemented at various locations within the industrial control system 100. For example, firewall(s) 132 may be integrated into switches 120 and/or workstations 122 of the control network 116.
The secure industrial control system 100 may further include one or more manufacturing entities (e.g., factories) 136. The manufacturing entities 136 may be associated with original equipment manufacturers (OEMs) for the industrial elements of the industrial control system 100. As shown, the key management system 130 may be communicatively coupled with the manufacturing entity (or entities) 136 via network 134 (e.g., a cloud. In implementations, when the industrial elements of the industrial control system 100 are being manufactured at the one or more manufacturing entities 136, the key management entity 130 may be communicatively coupled with (e.g., may have an encrypted communications pipeline to) the industrial elements. The key management entity 130 can utilize the communications pipeline for provisioning the industrial elements with security credentials (e.g., inserting keys, certificates and/or identification numbers into the industrial elements) at the point of manufacture. Further, when the industrial elements are placed into use (e.g., activated), the key management entity 130 may be communicatively coupled (e.g., via an encrypted communications pipeline) to each individual industrial element worldwide and may confirm and sign the use of specific code, revoke (e.g., remove) the use of any particular code, and/or enable the use of any particular code. Thus, the key management entity 130 may communicate with each industrial element at the factory 136 where the industrial element is originally manufactured (e.g., born), such that the industrial element is born with managed keys. A master database and/or table including all encryption keys, certificates and/or identification numbers for each industrial element of the industrial control system 100 may be maintained by the key management system 130. The key management entity 130 through its communication with the industrial elements is configured for revoking keys, thereby promoting the ability of the authentication mechanism to counter theft and re-use of components.
In implementations, the key management system 130 may be communicatively coupled with one or more of the control and input/output sub-system 102, the control network 116 and/or the corporate network 126 via network (e.g., cloud, Internet) 134 and firewall 132. For example, in embodiments, the key management system 130 may be a centralized system or a distributed system. Moreover, in embodiments, the key management system 130 may be managed locally or remotely. In some implementations, the key management system 130 may be located within (e.g., integrated into) the control network 116, the corporate network 126 and/or the control and input/output subsystem 102. The key management system 130 may provide management and/or may be managed in a variety of ways. For example, the key management system 130 may be implemented/managed: by a customer at a central location, by the customer at individual factory locations 136, by an external third party management company and/or by the customer at different layers of the industrial control system 100, and at different locations, depending on the layer.
Varying levels of security (e.g., scalable, user-configured amounts of security) may be provided by the authentication process. For example, a base level of security may be provided which authenticates the industrial elements and protects code within the industrial elements. Other layers of security can be added as well. For example, security may be implemented to such a degree that a component, such as a power module 110, may not power up without proper authentication occurring. In implementations, encryption in the code is implemented in the industrial elements, security credentials (e.g., keys and certificates) are implemented on the industrial elements. Security may be distributed (e.g., flows) through the industrial control system 100. For example, security may flow through the system 100 all the way to an end user, who knows what that module is designed to control in that instance. In embodiments, the authentication process provides encryption, identification of devices for secure communication and authentication of system hardware or software components (e.g., via digital signature).
the industrial elements of the industrial secure control system 100 are provisioned with unique security credentials and include controllers (e.g., microcontrollers) for implementing the above-referenced authentication process so that security is provided at multiple (e.g., all) communication levels within the secure industrial control system 100.
In implementations, the authentication process may be implemented to provide for/enable interoperability within the secure industrial control system 100 of industrial elements manufactured and/or supplied by different manufacturers/vendors/suppliers (e.g., OEMs). For example, selective (e.g., some) interoperability between industrial elements manufactured and/or supplied by different manufacturers/vendors/suppliers may be enabled. In embodiments, security credentials (e.g., keys) implemented during authentication may form a hierarchy, thereby allowing for different functions to be performed by different industrial elements of the industrial control system 100.
The communication links connecting the components of the industrial control system 100 may further employ data packets, such as runt packets (e.g., packets smaller than 64 bytes), placed (e.g., injected/stuffed) therein for providing an added level of security. The use of runt packets increases the level of difficulty with which outside information (e.g., malicious content such as false messages, malware (viruses), data mining applications, etc.) can be injected onto the communications links. For example, runt packets may be injected onto a communication link within gaps between data packets transmitted between a communications control module 106 and an input/output module 108 to hinder an external entity's ability to inject malicious content onto the communication link.
The secure industrial control system 100, including some or all of its components and physical interconnect devices, can operate under computer control. For example, a processor can be included with or in each controller to control components and physical interconnect devices and functions of the industrial control system 100 by using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or a combination thereof. The terms “controller,” “functionality,” “service,” and “logic” as used herein generally represent software, firmware, hardware, or a combination of software, firmware, or hardware in conjunction with controlling the industrial control system 100. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., central processing unit (CPU) or CPUs). The program code can be stored in one or more computer-readable memory devices (e.g., internal memory and/or one or more tangible media), and so on. The structures, functions, approaches, and techniques described herein can be implemented on a variety of commercial computing platforms having a variety of processors.
The processors provide processing functionality for the components and physical interconnect devices of the industrial control system 100 and can include any number of processors, micro-controllers, or other processing systems, and resident or external memory for storing data and other information accessed or generated by the secure industrial control system 100. Each processor can execute one or more software programs that implement techniques described herein. The processors are not limited by the materials from which they are formed or the processing mechanisms employed therein and, as such, can be implemented via semiconductor(s) and/or transistors (e.g., using electronic integrated circuit (IC) components), and so forth.
Memory can be included with or in each controller. The memory is an example of a tangible, computer-readable storage medium that provides storage functionality to store various data associated with operation of the industrial control system 100, such as software programs and/or code segments, or other data to instruct the processor(s), components, and physical interconnect devices of the industrial control system 100, to perform the functionality described herein. Thus, the memory can store data, such as a program of instructions for operating the industrial control system 100 (including its components and physical interconnect devices), and so forth. It should be noted that a wide variety of types and combinations of memory (e.g., tangible, non-transitory memory) can be employed. The memory can be integral with the processor, can comprise stand-alone memory, or can be a combination of both. The memory can include, but is not necessarily limited to: removable and non-removable memory components, such as random-access memory (RAM), read-only memory (ROM), flash memory (e.g., a secure digital (SD) memory card, a mini-SD memory card, and/or a micro-SD memory card), magnetic memory, optical memory, universal serial bus (USB) memory devices, hard disk memory, external memory, and so forth. In implementations, the system 100 and/or the memory can include removable integrated circuit card (ICC) memory, such as memory provided by a subscriber identity module (SIM) card, a universal subscriber identity module (USIM) card, a universal integrated circuit card (UICC), and so on.
A communications interface can be included with or in each controller. The communications interface is operatively configured to communicate with components and physical interconnect devices of the industrial control system 100. For example, the communications interface can be configured to transmit data for storage in the industrial control system 100, retrieve data from storage in the industrial control system 100, and so forth. The communications interface is also communicatively coupled with the processor to facilitate data transfer between components and physical interconnect devices of the industrial control system 100. It should be noted that while the communications interface is described as being included with or connected to a component and/or physical interconnect device of the industrial control system 100, one or more elements of the communications interface can be implemented as external elements communicatively coupled to component(s) and/or physical interconnect devices of the industrial control system 100 via a wired and/or wireless connection. Component(s) and/or physical interconnect devices of the industrial control system 100 can also comprise and/or connect to one or more input/output (I/O) devices (e.g., via the communications interface) including, but not necessarily limited to: a display, a mouse, a touchpad, a keyboard, and so on.
The communications interface and/or the processor can be configured to communicate with a variety of different 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 local area network (WLAN) operated using IEEE 802.11 network standards); an internet; the Internet; a wide area network (WAN); a local area network (LAN); a personal area network (PAN) (e.g., a wireless personal area network (WPAN) operated using IEEE 802.15 network standards); a public telephone network; an extranet; an intranet; and so on. However, this list is provided by way of example only and is not meant to be restrictive of the present disclosure. Further, the communications interface can be configured to communicate with a single network or multiple networks across different access points.
Referring now to
Referring now to
Generally, any of the functions described herein can be implemented using hardware (e.g., fixed logic circuitry such as integrated circuits), software, firmware, manual processing, or a combination thereof. Thus, the blocks discussed in the above disclosure generally represent hardware (e.g., fixed logic circuitry such as integrated circuits), software, firmware, or a combination thereof. In the instance of a hardware configuration, the various blocks discussed in the above disclosure may be implemented as integrated circuits along with other functionality. Such integrated circuits may include all of the functions of a given block, system, or circuit, or a portion of the functions of the block, system or circuit. Further, elements of the blocks, systems, or circuits may be implemented across multiple integrated circuits. Such integrated circuits may comprise various integrated circuits including, but not necessarily limited to: a monolithic integrated circuit, a flip chip integrated circuit, a multichip module integrated circuit, and/or a mixed signal integrated circuit. In the instance of a software implementation, the various blocks discussed in the above disclosure represent executable instructions (e.g., program code) that perform specified tasks when executed on a processor. These executable instructions can be stored in one or more tangible computer readable media. In some such instances, the entire system, block or circuit may be implemented using its software or firmware equivalent. In other instances, one part of a given system, block or circuit may be implemented in software or firmware, while other parts are implemented in hardware.
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.
The present application is a continuation of U.S. patent application Ser. No. 15/717,452, titled “SECURE INDUSTRIAL CONTROL SYSTEM” filed Sep. 27, 2017, which is a continuation of U.S. patent application Ser. No. 14/942,305, titled “SECURE INDUSTRIAL CONTROL SYSTEM” filed Nov. 16, 2015, which is a continuation of U.S. patent application Ser. No. 14/469,931, titled “SECURE INDUSTRIAL CONTROL SYSTEM” filed Aug. 27, 2014, which is a continuation of International Patent Application No. PCT/US2013/053721, titled “SECURE INDUSTRIAL CONTROL SYSTEM” filed Aug. 6, 2013. U.S. patent application Ser. Nos. 15/717,452, 14/942,305, and 14/469,931, and International Patent Application No. PCT/US2013/053721 are incorporated herein by reference, in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
1778549 | Conner | Oct 1930 | A |
1961013 | Battista et al. | May 1934 | A |
2540575 | Tomun et al. | 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 et al. | 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 |
4789792 | Ruedi | Dec 1988 | A |
4882702 | Struger et al. | Nov 1989 | A |
4929939 | Varma et al. | May 1990 | A |
4932892 | Hatch | Jun 1990 | A |
5013247 | Watson | May 1991 | A |
5128664 | Bishop | Jul 1992 | 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 |
5572511 | Ouyang | Nov 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 | Ogroske et al. | Apr 1998 | A |
5757795 | Schnell | May 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 |
6218740 | Mildice | Apr 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 et al. | 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 |
7788431 | Deshpande 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 | Buehler 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 |
10613567 | Rooyakkers et al. | Apr 2020 | B2 |
11093427 | Calvin et al. | Aug 2021 | B2 |
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 |
20020124198 | Bormann et al. | Sep 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 |
20030013727 | Maw 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 |
20030236998 | Gilstrap et al. | Dec 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 |
20050151720 | Cruz-Hernandez et al. | Jul 2005 | A1 |
20050162019 | Masciarelli et al. | Jul 2005 | A1 |
20050182876 | Kim et al. | Aug 2005 | A1 |
20050189910 | Hui | Sep 2005 | A1 |
20050198522 | Shaw et al. | 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 et al. | Jul 2007 | A1 |
20070177298 | Jaatinen et al. | Aug 2007 | A1 |
20070192134 | Littenberg 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 et al. | Nov 2007 | A1 |
20080067874 | Tseng | Mar 2008 | A1 |
20080077976 | Schulz | Mar 2008 | A1 |
20080080395 | Law et al. | Apr 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 | 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 |
20110038114 | Pance et al. | Feb 2011 | A1 |
20110066309 | Matsuoka et al. | Mar 2011 | A1 |
20110074349 | Ghovanloo | Mar 2011 | A1 |
20110080056 | Low et al. | 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 | Neupaertl 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 | Audéon et al. | Sep 2014 | A1 |
20140312913 | Kikuchi et al. | Oct 2014 | A1 |
20140327318 | Calvin et al. | Nov 2014 | A1 |
20140335703 | Calvin et al. | Nov 2014 | A1 |
20140341220 | Lessmann | Nov 2014 | A1 |
20150019790 | Calvin et al. | Jan 2015 | A1 |
20150046701 | Rooyakkers et al. | Feb 2015 | A1 |
20150048684 | Rooyakkers et al. | Feb 2015 | A1 |
20150115711 | Kouroussis et al. | Apr 2015 | A1 |
20150303729 | Kasai et al. | Oct 2015 | A1 |
20150365240 | Callaghan | Dec 2015 | A1 |
20160065656 | Patin et al. | Mar 2016 | A1 |
20160069174 | Cannan et al. | Mar 2016 | A1 |
20160141894 | Beaston | May 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 |
Number | Date | Country |
---|---|---|
2162746 | Apr 1994 | CN |
1408129 | Apr 2003 | CN |
1440254 | Sep 2003 | CN |
2596617 | Dec 2003 | CN |
1571335 | Jan 2005 | CN |
1702582 | Nov 2005 | CN |
1839581 | Sep 2006 | CN |
1864305 | Nov 2006 | CN |
2899151 | May 2007 | CN |
101005359 | Jul 2007 | CN |
101069407 | Nov 2007 | CN |
101262401 | Sep 2008 | CN |
101322089 | Dec 2008 | CN |
101349916 | Jan 2009 | CN |
101447861 | Jun 2009 | CN |
101533380 | Sep 2009 | CN |
101576041 | Nov 2009 | CN |
201515041 | Jun 2010 | CN |
101809557 | Aug 2010 | CN |
201590580 | Sep 2010 | CN |
101919139 | Dec 2010 | CN |
101977104 | Feb 2011 | CN |
102035220 | Apr 2011 | CN |
102123031 | Jul 2011 | CN |
102236329 | Nov 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 |
103064032 | Apr 2013 | CN |
203180248 | Sep 2013 | CN |
103376766 | Oct 2013 | CN |
103682883 | Mar 2014 | CN |
103701919 | Apr 2014 | CN |
203645015 | Jun 2014 | CN |
104025387 | Sep 2014 | CN |
203932181 | Nov 2014 | CN |
104185969 | Dec 2014 | CN |
104297691 | Jan 2015 | CN |
104505894 | Apr 2015 | CN |
204243110 | Apr 2015 | CN |
105278327 | Jan 2016 | CN |
105556762 | May 2016 | CN |
104025387 | Jul 2018 | CN |
102013213550 | Jan 2015 | DE |
0473336 | Mar 1992 | EP |
0507360 | Oct 1992 | EP |
1176616 | Jan 2002 | EP |
1241800 | Sep 2002 | EP |
1246563 | Oct 2002 | EP |
1571559 | Sep 2005 | EP |
1877915 | Jan 2008 | EP |
1885085 | Feb 2008 | EP |
2179364 | Apr 2010 | EP |
2317743 | May 2011 | EP |
2450921 | May 2012 | EP |
2557657 | Feb 2013 | EP |
2557670 | Feb 2013 | EP |
1885085 | Mar 2013 | EP |
2613421 | Jul 2013 | EP |
2777796 | Sep 2014 | EP |
2806319 | Nov 2014 | EP |
S5974413 | May 1984 | JP |
S59177226 | Nov 1984 | JP |
H0163190 | Apr 1989 | JP |
H04245411 | Sep 1992 | JP |
H05346809 | Dec 1993 | JP |
07075143 | Mar 1995 | JP |
H07105328 | Apr 1995 | JP |
H07320963 | Dec 1995 | JP |
H0837121 | Feb 1996 | JP |
H0898274 | Apr 1996 | JP |
H08241824 | Sep 1996 | JP |
H08322252 | Dec 1996 | JP |
H09182324 | Jul 1997 | JP |
H1189103 | Mar 1999 | JP |
H1198707 | Apr 1999 | JP |
H11230504 | Aug 1999 | JP |
H11235044 | Aug 1999 | JP |
H11312013 | Nov 1999 | JP |
2000041068 | Feb 2000 | JP |
2000124890 | Apr 2000 | JP |
2000252143 | Sep 2000 | JP |
2001242971 | Sep 2001 | 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 |
2004532596 | Oct 2004 | JP |
2005020759 | Jan 2005 | 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 |
2006254650 | Sep 2006 | JP |
2007034711 | Feb 2007 | JP |
2007096817 | Apr 2007 | JP |
2007519150 | Jul 2007 | JP |
2007238696 | Sep 2007 | JP |
2007252081 | Sep 2007 | JP |
2007535235 | Nov 2007 | JP |
2008008861 | Jan 2008 | 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 |
2009538112 | Oct 2009 | JP |
2010011351 | Jan 2010 | JP |
2010503134 | Jan 2010 | JP |
4439340 | Mar 2010 | JP |
2010515407 | May 2010 | JP |
2010135903 | Jun 2010 | JP |
2010233167 | Oct 2010 | JP |
2011078249 | Apr 2011 | JP |
2011217037 | Oct 2011 | JP |
2011223544 | Nov 2011 | JP |
2012033491 | Feb 2012 | JP |
5013019 | Aug 2012 | JP |
2012190583 | Oct 2012 | JP |
2012195259 | Oct 2012 | JP |
2013021798 | Jan 2013 | JP |
2013031358 | Feb 2013 | JP |
2013153596 | Aug 2013 | JP |
2013170258 | Sep 2013 | JP |
2013192389 | Sep 2013 | JP |
5362930 | Dec 2013 | JP |
2014507721 | Mar 2014 | JP |
2014080952 | May 2014 | JP |
2015023375 | Feb 2015 | JP |
2016512039 | Apr 2016 | JP |
2016149128 | Aug 2016 | JP |
2016527844 | Sep 2016 | JP |
6189479 | Aug 2017 | JP |
2020115457 | Jul 2020 | JP |
20020088540 | Nov 2002 | KR |
20050014790 | Feb 2005 | KR |
20060034244 | Apr 2006 | KR |
100705380 | Apr 2007 | KR |
100807377 | Feb 2008 | KR |
20130039174 | Apr 2013 | KR |
201310344 | Mar 2013 | TW |
2005070733 | Aug 2005 | WO |
2005081659 | Sep 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 |
2014061307 | Apr 2014 | WO |
2014179556 | Nov 2014 | WO |
2014179566 | Nov 2014 | WO |
2015020633 | Feb 2015 | WO |
Entry |
---|
Emerson Process Management, “DeltaV Digital Automation System—System Overview,” XP055402326, Jan. 1, 2009, pp. 1-40. |
Extended European Search Report for 21187809.5, dated Nov. 29, 2021. |
Office Action for Chinese Application No. 201910660260.4, dated Nov. 18, 2021. |
Office Action for Japanese Application No. 2017-237592, dated Dec. 27, 2021. |
Seimens AG, “ERTEC400—Enhanced Real-Time Ethernet Controller—Handbuch,” XP002637652, Version 1.2.2, Jul. 31, 2010, pp. 1-98. |
Office Action for Japanese Application No. 2015-136186, dated Oct. 10, 2019. |
Partial European Search Report in European Application No. 17208183.8, dated Mar. 28, 2018. |
Partial Supplementary European Search Report in Application No. 12862174.5, dated Nov. 3, 2015. |
Partial European Search Report for European Patent Application No. EP 15175744 dated Jan. 4, 2016, 7 pages. |
Partial Search Report for European Application No. 15175744.0, dated Dec. 14, 2015. |
Partial Supplementary European Search Report dated Nov. 10, 2015 in Application# EP12862174.5. |
Reason for Rejection in Japanese Patent Application No. 2016-533279, dated Aug. 13, 2018. |
Reason for Rejection for Japanese Application No. 2015-136186, dated May 7, 2020. |
Rodrigues A., “SCADA Security Device: Design and Implementation”, Master of Science Thesis, Wichita State University, Dec. 2011. |
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, p. 1, XP055230335, New York, New York, USA. |
Roman Kleinerman, Daniel Feldman (May 2011), Power over Ethernet (PoE): An Energy-Efficient Alternative (PDF), Marvell, retrieved Sep. 25, 2018 @ http://www.marvell.com/switching/assets/Marveii-PoE-An-Energy-Efficient-Aiternative.pdf (Year: 2011). |
Search Report for European Application No. 14196406.4, dated Nov. 4, 2015. |
Search Report for European Application No. 16154943.1 dated Jun. 17, 2016. |
Search Report for European Application No. 14196409.8, dated May 19, 2016. |
Search Report for European Application No. 15175744.0, dated Apr. 26, 2016. |
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]. |
Siemens, “Uninterruptible 24 V DC Power Supply High-Performance, communicative and integrated in TIA,” Mar. 31, 2015,XP055290324. |
Summons to attend oral proceedings for European Application No. 14196409.8, dated Nov. 13, 2019. |
Supplementary European Search Report for European Patent Application No. EP 14791210 dated Dec. 16, 2016, 11 pages. |
Supplementary Search Report for European Application No. 13890953.6 dated Jan. 26, 2017. |
Supplementary Search Report for European Application No. 13891327.2, dated Jan. 10, 2017. |
Supplementary Search Report for European Application No. 14791210.9, dated Dec. 6, 2016. |
Supplementary European Search Report for European Patent Application No. EP 13890953 dated Feb. 6, 2017, 9 pages. |
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. |
Chinese Office Action for Application No. 202010105899.9, dated Dec. 3, 2020. |
European Examination Report for Application No. 14196406.4, dated May 12, 2020. |
European Search Report for Application No. 20173319.3, dated Nov. 24, 2020. |
Extended European Search Report for European Application No. 20150993.2, dated Apr. 29, 2020. |
Final Decision for Rejection for Patent Application No. 2016-021763, dated Jul. 31, 2020. |
Hosseinabady, Mohammad, et al., “Using the inter- and intra-switch regularity in NoC switch testing,” Design, Automation & Test in Europe Conference & Exhibition: Nice, France, Apr. 16-20, 2007, IEEE Service Center, Apr. 16, 2007 (XP058290046). |
Notice of Reason for Rejection for Japanese Application No. 2016-080207, dated Feb. 4, 2021. |
Notice of Reason for Rejection for Japanese Application No. 2014-243827, dated Feb. 1, 2021. |
Office Action for Chinese Patent Application No. 201610236358.3, dated Jan. 25, 2021. |
Office Action of Chinese Application No. 201711349441.2 dated May 27, 2021. |
Office Action for Japanese Application No. 2014-243830, dated Jun. 29, 2021. |
Office Action for Japanese Application No. 2016-021763, dated Jun. 11, 2021. |
Notice of Reason for Rejection for Japanese Patent Application No. 2014-243830, dated Jul. 10, 2019. |
Notice of Reason for Rejection for Japanese Patent Application No. 2014-243830, dated Sep. 21, 2018. |
Notice of Reason for Rejection for JP Patent Application No. 2018-109151, dated Jun. 25, 2019. |
Notice of Reason for Rejection for Patent Application No. 2016-021763, dated Nov. 27, 2019. |
Notice of Reasons for Rejection dated Jul. 13, 2017 for Japanese Application No. JP2016-533279. |
Notice of Reasons for Rejection dated Mar. 1, 2018 for Japanese Application No. JP2016-533279. |
Notification of the Second Office Action for Chinese Application No. 201380079514.4, dated Nov. 5, 2018. |
Office Action for Canadian Application No. 2,875,515, dated Feb. 17, 2016. |
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. |
Office Action for Chinese Application No. 2015103905202.2, dated Jun. 20, 2018. |
Office Action for Chinese Application No. 2015103905202.2, dated Mar. 6, 2019. |
Office Action for Chinese Application No. 2015103905202.2, dated Aug. 6, 2019. |
Office Action dated Dec. 2, 2016 for JP Application No. 2014-550508. |
Office Action dated Feb. 5, 2018 for Chinese Application No. CN201380079514.4. |
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 Canadian Application No. 2,875,518, dated Apr. 22, 2016. |
Office Action for Canadian Application No. 2,875,518, dated Jun. 3, 2015. |
Office Action for Chinese Application No. 201280065564.2 dated Oct. 19, 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. |
Office Action for Chinese Appln No. 201380079515.9, dated Feb. 25, 2019. |
Office Action for Chinese Patent Application 201410802889.5, dated May 7, 2019. |
Office Action for Japanese Application No. 2014-080952, dated Jan. 7, 2019. |
Office Action for Japanese Application No. 2014-080952, dated May 2, 2018. |
Office Action for Japanese Application No. 2014-159475, dated Feb. 15, 2019. |
Office Action for Japanese Application No. 2014-159475, dated Jun. 11, 2018. |
Office Action for Japanese Application No. 2016-512039, dated Feb. 5, 2019. |
Office Action for Japanese Application No. 2016-512039, dated Jun. 5, 2018. |
Office Action for Japanese Application No. 2016-533280, dated Apr. 11, 2018. |
Office Action for Japanese Application No. 2016-533280, dated Jan. 7, 2019. |
Office Action for Japanese Application No. 2016-533280, dated Jun. 29, 2020. |
Office Action for Canadian Application No. 2,920,133, dated Apr. 14, 2016. |
Office Action for Canadian Application No. 2,875,515 dated Feb. 10, 2017. |
Office Action for Canadian Application No. 2,875,515 dated Jul. 5, 2017. |
Office Action for Candian Application No. 2,875,517 dated May 4, 2015. |
Office Action for Chinese Application No. 201280065564.2, dated Aug. 3, 2016. |
Office Action for Chinese Application No. 20141079995.2, dated Jul. 3, 2019. |
Office Action for Chinese Application No. 201410802889.5 dated Jul. 26, 2018. |
Office Action for Chinese Patent Application No. 201610236358.3, dated Jun. 24, 2020. |
Office Action for Chinese Patent Application No. 201610236358.3, dated Sep. 4, 2019. |
Office Action for EP Application No. 14196409.8 dated Jan. 22, 2018. |
Office Action for Japanese Application No. 2016-533280, dated Jun. 28, 2017. |
Office Action forChinese Patent Application 201410802889.5, dated Dec. 4, 2019. |
Office Action from Chinese Patent Application No. 201610229230.4, dated Jul. 15, 2020. |
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. |
Office Action for Chinese Application No. 201280065564.2, dated Feb. 28, 2017. |
Baran, M. et al., “Overcurrent Protection on Voltage-Source-Converter-Based Multiterminal DC Distribution Systems,” IEEE Transactions on Power Delivery, vol. 22, No. 1, Jan. 2007, pp. 406-412. |
Canadian Office Action for Application No. 2920133 dated Jan. 30, 2017. |
Canadian Office Action for Application No. 2920133 dated Oct. 19, 2016. |
CGI, White Paper on “Public Key Encryption and Digital Signature: How do they work?”, 2004 (refer to pp. 3-4). |
Chinese Office Action for Application No. 201380079515.9 dated Aug. 7, 2018. |
Chinese Office Action for Application No. 201380079515.9 dated Nov. 16, 2017. |
Chinese Office Action for Application No. CN201610239130.X dated Aug. 2, 2017. |
Chinese Office Action for Application No. CN201610239130.X dated Feb. 14, 2018. |
Chinese Office Action for Application No. 201410383686.7 dated May 31, 2017. |
Chinese Office Action for Application No. 201410799473.2, dated Oct. 12, 2018. |
Chinese Office Action for Application No. CN201410182071.8 dated Mar. 1, 2017. |
Decision of Rejection for Japanese Application No. 2014-243830, dated Mar. 18, 2020. |
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. |
European Search Report for European Application No. 14196406.4, dated Sep. 23, 2015. |
European Search Report for EP Application No. 14196408.0, dated Nov. 24, 2015. |
European Search Report in Application No. 12862174.5, dated Feb. 15, 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 in European Application No. 17208183.8, dated Feb. 27, 2019. |
Examination Report for European Application No. 14180106.8, dated Jun. 28, 2017. |
Examination Report for European Application No. 17178867.2, dated Mar. 13, 2019. |
Examination Report for European Application No. 13891327.2, dated Sep. 26, 2018. |
Examination Report for European Application No. 16165112.0, dated Apr. 17, 2019. |
Examination Report for European Application No. 16165112.0, dated Feb. 16, 2018 . |
Examination Report for European Patent Application No. 16154943.1, dated May 16, 2019. |
Examination Report for European Patent Application No. 1720883.8, dated Oct. 29, 2019. |
Extended European Search Report for European Patent Application No. EP 14166908 dated Jan. 7, 2015, 10 pages. |
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 17178867 dated Nov. 2, 2017, 13pages. |
Extended European Search Report for European Patent Application No. EP 18176358 dated Sep. 11, 2018, 11 pages. |
Extended Search Report for European Application No. 14180106.8, dated Jul. 13, 2015. |
Extented European search report for European Patent Application No. EP16165112 dated Sep. 6, 2016, 12 pages. |
Fabien F., “Raspberry Pi + Mihini, Controlling an off-the-grid Electrical Installation, Part I,” Apr. 11, 2014, XP055290314. |
Generex Systems GMBH, “SACS—Battery Analysis & Care System,” Aug. 17, 2014, XP055290320. |
International Search Report and Written Opinion for PCT/US2014/036368, dated Sep. 12, 2014. |
International Search Report and Written Opinion dated May 12, 2014 in International Application# PCT/US2013/053721. |
International Search Report and Written Opinion of the International Searching Authority dated Apr. 29, 2013, International Application No. PCT/US2012/072056. |
International Search Report for Application No. PCT/US2013/053721 dated May 12, 2014. |
“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). |
Japanese Office Action for Application No. JP2014-550508 dated Sep. 15, 2017. |
Keith S., et al. “Guide to Industrial Control Systems (ICS) Security,” NIST, Special Publication 800-882, Jun. 2011, (refer to pp. 2-1 to 2-10). |
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. |
Extended European Search Report in European Application No. 17208183.8, dated Jun. 22, 2018. |
Notice of Reason for Rejection for Japanese Application No. 2016-080207, dated Jun. 4, 2020. |
Notice of Reason for Rejection for Japanese Application No. 2014-243827, dated Jan. 24, 2019. |
Final Decision of Rejection and Decision of Dismissal of Amendment for Japanese Application No. 2016-080207, dated Sep. 10, 2021. |
Office Action for Chinese Application No. 2020101058999, dated Sep. 3, 2021. |
Office Action for Japanese Application No. 2020-135564, dated Jul. 20, 2021. |
Chen, et al., “Active Diagnosability of Discrete Event Systems and its Application to Battery Fault Diagnosis,” IEEE Transactions on Control Systems Technology, vol. 22, No. 5, Sep. 2014. |
Examination Report for European Application No. 14196406.4, dated Mar. 31, 2021. |
Extended European Search Report for European Application No. 20201408.0, dated Apr. 7, 2021. |
Extended European Search Reported for European Application No. 20201403.1, dated Apr. 29, 2021. |
Fang et al., “Application of expert diagnosis system in rechargeable battery,” Department of Computer Science, Qinghua University, Beijing, China, vol. 26, No. 3, Jun. 2002. |
Generex System GMBH, “BACS—Battery Analysis & Care System,” Aug. 17, 2014 , XP055290320, Retrieved from the Internet: URL :HTTP://web.archive.org/we/2040929060116/http://www.generex.de/generex/download/datasheets/datasheet_BACS_C20_de.pdf. |
Notice of Reasons for Rejection for Japanese Patent Application No. 2020-035778, dated Apr. 15, 2021. |
Office Action for Chinese Application No. 201610229230.4, dated Mar. 18, 2021. |
Reason for Rejection for Japanese Application No. 2020-061935, dated Mar. 31, 2021. |
Office Action for Japanese Application No. 2020-135564, dated Mar. 8, 2022. |
D. Dzung, M. Naedele, T. P. Von Hoff and M. Crevatin, “Security for Industrial Communication Systems,” in Proceedings of the IEEE, vol. 93, No. 6, pp. 1152-1177, Jun. 2005, doi: 10.11 09/JPROC.2005.849714. (Year: 2005). |
Number | Date | Country | |
---|---|---|---|
20210110025 A1 | Apr 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15717452 | Sep 2017 | US |
Child | 17069323 | US | |
Parent | 14942305 | Nov 2015 | US |
Child | 15717452 | US | |
Parent | 14469931 | Aug 2014 | US |
Child | 14942305 | US | |
Parent | PCT/US2013/053721 | Aug 2013 | US |
Child | 14469931 | US |