Source: https://patents.google.com/patent/US8280057B2/en
Timestamp: 2019-04-25 05:03:14+00:00

Document:
2008-01-25 Assigned to HONEYWELL INTERNATIONAL INC. reassignment HONEYWELL INTERNATIONAL INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KOLAVENNU, SOUMITRI N., KUNE, DENIS FOO, BUDAMPATI, RAMAKRISHNA S.
A method includes receiving data at a first wireless node in a wireless network, where the data is associated with an industrial control and automation system. The method also includes decrypting the received data using a first encryption key to produce decrypted data and encrypting the decrypted data using a second encryption key to produce encrypted data. The method further includes communicating the encrypted data to at least a second wireless node in the wireless network. Another method includes generating first data at a first wireless node in a wireless network, where the data is associated with an industrial control and automation system. The other method also includes encrypting the first data using an encryption key and transmitting the first data to multiple second wireless nodes in the wireless network, where the second wireless nodes are capable of using the same encryption key to decrypt the first data.
This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 60/967,342 filed on Sep. 4, 2007, which is hereby incorporated by reference.
This disclosure relates generally to communication networks and more specifically to a method and apparatus for providing security in wireless communication networks.
Many buildings, facilities, and other structures include secure communication networks, which are used for wireless and other types of communications. For example, chemical plants and other industrial facilities often include wireless networks, which can be used for a wide variety of purposes. As particular examples, the wireless networks in industrial facilities could be used to transport data to and from process controllers, process sensors, and process actuators. The wireless networks could also facilitate wireless communications between personnel working in the industrial facilities.
In order to prevent malicious or other unauthorized intrusions into a wireless network, various forms of security are typically employed in the wireless network. A common security mechanism includes the use of encryption keys to encrypt and decrypt data that is transmitted wirelessly.
This disclosure provides a method and apparatus for providing security in wireless communication networks.
In a first embodiment, a method includes receiving data at a first wireless node in a wireless network, where the data is associated with an industrial control and automation system. The method also includes decrypting the received data using a first encryption key to produce decrypted data. The method further includes encrypting the decrypted data using a second encryption key to produce encrypted data. In addition, the method includes communicating the encrypted data to at least a second wireless node in the wireless network.
In particular embodiments, receiving the data includes receiving the data from a third wireless node in the wireless network. The first encryption key is uniquely associated with the first wireless node-third wireless node pair, and the second encryption key is uniquely associated with the first wireless node-second wireless node pair.
In other particular embodiments, the method also includes verifying a digital signature at the first wireless node, where the digital signature is associated with a trust authority and provided by the second wireless node. The method further includes exchanging encryption keys with the second wireless node, where the exchanged encryption keys include the second encryption key. The first wireless node could exchange encryption keys with any wireless node having (i) an active link with the first wireless node and (ii) a certificate signed by the trust authority.
In yet other particular embodiments, decrypting the received data and encrypting the decrypted data are performed at a Medium Access Control (MAC) layer and/or a network layer in the first wireless node.
In still other particular embodiments, receiving the data includes receiving the data from a leaf node in the wireless network, the leaf node communicates the data to the first wireless node and at least one other wireless node, and the first wireless node and the at least one other wireless node use the same first encryption key to produce the decrypted data. In other particular embodiments, the second wireless node includes a leaf node, the leaf node receives the encrypted data from the first wireless node and at least one other wireless node, and the first wireless node and the at least one other wireless node use the same second encryption key to produce the encrypted data.
In additional particular embodiments, the data is associated with a sensor and/or an actuator in the industrial control and automation system.
In a second embodiment, a wireless node in a wireless network includes at least one transceiver configured to receive data over the wireless network, where the data is associated with an industrial control and automation system. The wireless node also includes at least one controller configured to decrypt the received data using a first encryption key to produce decrypted data, encrypt the decrypted data using a second encryption key to produce encrypted data, and provide the encrypted data to the at least one transceiver for communication to at least a second wireless node in the wireless network.
In a third embodiment, a method includes generating first data at a first wireless node in a wireless network, where the data is associated with an industrial control and automation system. The method also includes encrypting the first data using an encryption key. In addition, the method includes transmitting the first data to multiple second wireless nodes in the wireless network, where the second wireless nodes are capable of using the same encryption key to decrypt the first data.
FIGS. 7 and 8 illustrate example methods for providing security in a wireless network according to this disclosure.
FIGS. 1 through 8, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the invention. Those skilled in the art will understand that the principles of the invention may be implemented in any type of suitably arranged device or system.
FIG. 1 illustrates an example industrial control and automation system 100 according to this disclosure. The embodiment of the industrial control and automation system 100 shown in FIG. 1 is for illustration only. Other embodiments of the industrial control and automation system 100 could be used without departing from the scope of this disclosure.
In this example embodiment, the industrial control and automation system 100 includes one or more process elements 102. The process elements 102 represent components in a process or production system that may perform any of a wide variety of functions. For example, the process elements 102 could represent sensors, actuators, or any other or additional industrial equipment in a processing environment. Each of the process elements 102 includes any suitable structure for performing one or more functions in a processing or production system. Also, the phrase “industrial control and automation system” generally refers to a system that automates and controls at least one process.
A controller 104 is coupled to the process elements 102. The controller 104 controls the operation of one or more of the process elements 102. For example, the controller 104 could receive information associated with the system 100, such as by receiving sensor measurements from some of the process elements 102. The controller 104 could use this information to provide control signals to others of the process elements 102, thereby adjusting the operation of those process elements 102. The controller 104 includes any hardware, software, firmware, or combination thereof for controlling one or more process elements 102. The controller 104 could, for example, represent a computing device executing a MICROSOFT WINDOWS operating system.
A network 106 facilitates communication between various components in the system 100. For example, the network 106 may communicate Internet Protocol (IP) packets, frame relay frames, Asynchronous Transfer Mode (ATM) cells, or other suitable information between network addresses. The network 106 may include one or more local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of a global network such as the Internet, or any other communication system or systems at one or more locations.
As shown in FIG. 1, the industrial control and automation system 100 also includes one or more wireless networks for communicating with wireless sensors or other wireless devices. In this example, a wireless network (such as a mesh network) is formed using infrastructure nodes (“I nodes”) 108 a-108 e, leaf nodes 110 a-110 e, and a gateway infrastructure node 112.
The infrastructure nodes 108 a-108 e and the leaf nodes 110 a-110 e engage in wireless communications with each other. For example, the infrastructure nodes 108 a-108 e may receive data transmitted over the network 106 (via the gateway infrastructure node 112) and wirelessly communicate the data to the leaf nodes 110 a-110 e. Similarly, the leaf nodes 110 a-110 e may wirelessly communicate data to the infrastructure nodes 108 a-108 e for forwarding to the network 106 (via the gateway infrastructure node 112). In addition, the infrastructure nodes 108 a-108 e may wirelessly exchange data with one another. In this way, the nodes 108 a-108 e and 110 a-110 e form a wireless network capable of providing wireless coverage to a specified area, such as in a large industrial complex.
In this example, the nodes 108 a-108 e and 110 a-110 e are divided into infrastructure nodes and leaf nodes. The infrastructure nodes 108 a-108 e typically represent line-powered devices, meaning these nodes receive operating power from an external source. As a result, these nodes 108 a-108 e are typically not limited in their operations since they need not minimize power consumption to increase the operational life of their internal power supplies. On the other hand, the leaf nodes 110 a-110 e typically represent battery-powered devices, meaning these nodes receive operating power from internal batteries or other power supplies. Because of this, these nodes 110 a-110 e are often more limited in their operations in order to help preserve the operational life of their internal power supplies.
Each of the nodes 108 a-108 e and 110 a-110 e includes any suitable structure facilitating wireless communications, such as an RF transceiver. Each of the nodes 108 a-108 e and 110 a-110 e could also include other functionality, such as functionality for generating or using data communicated over the wireless network. For example, the leaf nodes 110 a-110 e could represent wireless sensors in an industrial facility, where the sensors are used to measure various characteristics within the facility. These sensors could collect sensor readings and communicate the sensor readings to the controller 104 via the gateway infrastructure node 112. The leaf nodes 110 a-110 e could also represent actuators that can receive control signals from the controller 104 and adjust the operation of the industrial facility. In this way, the leaf nodes 110 a-110 e may include or operate in a similar manner as the process elements 102 that are physically connected to the controller 104. The leaf nodes 110 a-110 e could further represent handheld user devices (such as INTELATRAC devices from HONEYWELL INTERNATIONAL INC.), mobile stations, programmable logic controllers (PLCs), or any other or additional devices.
In particular embodiments, the leaf nodes 110 a-110 e can include 802.15.4-based low data-rate sensors and 802.11-based high data-rate devices, and the various nodes in FIG. 1 form a mesh network communicating at 2.4 GHz or 5.8 GHz. Also, in particular embodiments, data can be injected into the wireless mesh network through the infrastructure nodes, thus providing versatile, multifunctional, plant-wide coverage for wireless sensing, asset location tracking, personnel tracking, wireless communications, and any other or additional functionality as desired.
The gateway infrastructure node 112 communicates wirelessly with, transmits data to, and receives data from one or more infrastructure nodes 108 a-108 e and possibly one or more leaf nodes 110 a-110 e. The gateway infrastructure node 112 also converts data between the protocol(s) used by the network 106 and the protocol(s) used by the nodes 108 a-108 e and 110 a-110 e. For example, the gateway infrastructure node 112 could convert Ethernet-formatted data (transported over the network 106) into a wireless protocol format (such as an IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.15.3, 802.15.4, or 802.16 protocol format) used by the nodes 108 a-108 e and 110 a-110 e. The gateway infrastructure node 112 could also convert data received from one or more of the nodes 108 a-108 e and 110 a-110 e into Ethernet-formatted data for transmission over the network 106. In addition, the gateway infrastructure node 112 could support various functions, such as network creation and security, used to create and maintain a wireless network. The gateway infrastructure node 112 includes any suitable structure for facilitating communication between components or networks using different protocols.
In this example, a wireless configuration and OLE for Process Control (OPC) server 114 can be used to configure and control various aspects of the process control system 100. For example, the server 114 could be used to configure the operation of the infrastructure nodes 108 a-108 e and the gateway node 112. The server 114 could also be used to support security in the industrial control and automation system 100. For instance, the server 114 could distribute cryptographic keys or other security data to various components in the industrial control and automation system 100, such as to the nodes 108 a-108 e, 110 a-110 e, and 112. The server 114 includes any hardware, software, firmware, or combination thereof for configuring wireless networks and providing security information.
In one aspect of operation, the nodes 108 a-108 e, 110 a-110 e, 112 in the wireless network transmit data that is protected using encryption keys, which are used to encrypt and decrypt the data. The encryption used in the wireless network or in the system 100 in general may represent an “end-to-end” security mechanism, meaning the data is transmitted in encrypted form from a source and arrives in encrypted form at one or more destinations (whether the data traverses one or multiple paths to the destinations). The actual security mechanism used in the system 100 could vary according to particular needs. For example, in some embodiments, the end-to-end security could be used only within the wireless network, meaning data can be encrypted during all wireless transmissions (but the data need not be encrypted when transmitted over a wired network). The end-to-end security could also be used throughout the system 100 or in larger portions of the system 100, where data can be encrypted during wired or wireless transmissions.
Conventional wireless networks, such as those used for industrial wireless applications, use a single encryption key for the entire wireless network. This approach has inherent security problems since, for example, a compromised node in the network can compromise communications throughout the entire network.
In accordance with this disclosure, different encryption keys can be used for communications between nodes in the system 100. For example, the infrastructure nodes 108 a-108 e, 112 could communicate using different encryption keys. In some embodiments, for instance, each pair of infrastructure nodes may communicate using an encryption key unique to that pair. In these embodiments, each infrastructure node in the pair can transmit data to and receive data from the other infrastructure node in the pair using that encryption key. In other embodiments, each infrastructure node may transmit data to and receive data from one or multiple neighboring nodes using its own encryption key. “Neighboring nodes” of a particular infrastructure node could represent other nodes that are in direct contact with the particular infrastructure node or other nodes that maintain an active link with the particular infrastructure node. As a particular example, the infrastructure node 108 e in FIG. 1 is in direct communication with infrastructure node 108 d and gateway infrastructure node 112, and any communications to or from the infrastructure node 108 e can be made using the encryption key supported by the infrastructure node 108 e.
When data is received by a particular infrastructure node, the data is typically encrypted using that infrastructure node's encryption key. If the data is ultimately intended for that particular infrastructure node, the data can be decrypted using the infrastructure node's encryption key and then processed and used in any suitable manner. If the data is intended for a different destination, the infrastructure node can decrypt the data using its encryption key and then re-encrypt the data using the encryption key of the next node to receive the data (referred to as the next “hop” in the data's path to a destination). As a result, each data message flowing through an infrastructure node can be protected using the appropriate encryption key for the next hop along the data message's path.
In some embodiments, the encryption key used by an infrastructure node is unique to that infrastructure node or to a subset of the infrastructure nodes. In other words, the same encryption key is not used by all nodes in the wireless network. In particular embodiments, the encryption keys are used by the infrastructure nodes 108 a-108 e, 112 at the link layer level or at the network layer level.
The leaf nodes 110 a-110 e can also operate using encryption keys for encrypting and decrypting data sent over the wireless network. For example, in some embodiments, each leaf node operates using a single encryption key and sends encrypted data to multiple infrastructure nodes (such as to two infrastructure nodes). In these embodiments, the encryption key used by the leaf node can be shared between the multiple infrastructure nodes, which act as redundant nodes for the leaf node. Because of this, a transmitted data message from the leaf node may be received by multiple infrastructure nodes. These infrastructure nodes can then forward the data message to their respective next hops, where the data message is protected under the respective keys used by the infrastructure nodes (as described above). The infrastructure nodes may also use the same shared cryptographic key to send data messages to the leaf node. The use of the encryption key in a leaf node could occur at any suitable level, such as at the link layer level in the leaf node.
Among other things, this allows the leaf node to use a single encryption key to communicate with multiple infrastructure nodes, so one encryption key can be used to support redundant communications. Using a single key at the leaf node may help to offset some of the burden of managing multiple encryption keys and associated state data to the infrastructure nodes. This approach may also reduce key storage requirements at the leaf nodes and reduce the amount of processing needed at the leaf nodes (since a leaf node can perform a single cryptographic operation on a data message sent to multiple infrastructure nodes).
Cryptographic keys can be distributed to devices or exchanged between devices in the system 100 in any suitable manner. In particular embodiments, cryptographic keys are distributed and exchanged using data from the server 114 or other component(s) (referred to generally as a “trust authority”). For example, a signed Medium Access Control (MAC) address/public key pair can be used for each node receiving a key. In these embodiments, prior to deployment, each node can register its MAC address and its public key with a trust authority. This could be done over an isolated wired connection to help avoid “man in the middle” or other types of security attacks. The trust authority may sign the MAC address/public key pair and upload the signature (as well as the trust authority's public key) into the node being deployed. After installation, the node being deployed can detect and communicate with at least one other node, such as its neighboring nodes. For each neighboring node, the node being deployed can use the trust authority's digital signature to determine whether the neighboring node has been seen and verified by the trust authority (such as by determining whether the neighboring node has a certificate signed by the trust authority). If so, a pair-wise key exchange can follow between the nodes, allowing the nodes to learn each other's encryption key.
Multicast and broadcast communications can still take place in the system 100 using, for example, a network-wide key distributed by the trust authority over a unique link to each routing node in the network. Also, upon revocation of a node, a new network key can be deployed to the remaining nodes using the unique link as outlined above.
In particular embodiments, data routing in the system 100 can occur by predefining at least two best non-overlapping routes from each source to each destination in the system or wireless network, and data can be sent on these multiple routes at the same time. The destination may receive two or more copies of the same data messages, and useful information can be extracted from the copies. While sending multiple copies of the messages increases the communication bandwidth requirement, it may significantly increase system reliability by making it robust to any single point failure. Unlike homogeneous mesh networks, this approach can operate at a high data-rate (such as up to 54 Mbps) at the infrastructure level and a low data-rate (such as 250 Kbps) at the sensor level, so providing increased bandwidth at the infrastructure level is not a problem. As noted above, redundancy can also be achieved on the sensor level by transmitting data messages from leaf nodes that are received by two or more infrastructure nodes.
Using the cryptographic keys in this manner, significantly improved security can be obtained in a wireless network. Moreover, the processing requirements and other burdens can be removed partially from the leaf nodes and placed on the infrastructure nodes. Further, this approach provides a simple technique for isolating pair-wise communications since communications between a pair of devices can be stopped by revoking the key of at least one of the components (which might not affect a large portion of the wireless network). In addition, using these techniques, a hybrid (wireless and wired) mesh network can be provided for cost-effective, secure, and reliable communications in industrial control systems, where the network has a robust network architecture built on fundamentally strong principles for robust and reliable communications.
Although FIG. 1 illustrates one example of an industrial control and automation system 100, various changes may be made to FIG. 1. For example, the industrial control and automation system 100 could include any number of process elements, controllers, networks (wired or wireless), infrastructure nodes (gateway or other), leaf nodes, and servers. Also, the functional division shown in FIG. 1 is for illustration only. Various components in FIG. 1 could be combined, subdivided, or omitted and additional components could be added according to particular needs. In addition, while described as supporting a wired network and a wireless network, the industrial control and automation system 100 could support any number of wireless or wired networks, at least one of which can use the security mechanisms described above.
FIGS. 2 through 4 illustrate example techniques for data encryption in an industrial control and automation system according to this disclosure. The data encryption techniques shown in FIGS. 2 through 4 are for illustration only. Other data encryption techniques could be used without departing from the scope of this disclosure.
As shown here, each infrastructure node (gateway or other) may include a MAC layer 202, a network layer 204, and an application layer 206. The MAC layer 202 represents the data link layer of the infrastructure node, which is used to transfer data between network nodes. The MAC layer 202 may also provide techniques for detecting and correcting errors in an underlying physical layer (such as an underlying Ethernet physical layer). The network layer 204 supports the transport of data over a network, such as by routing data to appropriate destinations. The network layer 204 may also perform other functions, such as enforcing quality of service parameters. The application layer 206 generally supports upper level applications executed for users, such as applications for controlling an infrastructure node or providing other higher-level functions. Each of the layers 202-206 can be implemented in any suitable manner, such as by using hardware, software, firmware, or combination thereof.
In FIGS. 2 and 3, data transfers between infrastructure nodes are encrypted using different encryption keys. For example, data transfers between infrastructure nodes “A” and “B” are encrypted using a key known to both nodes “A” and “B” (denoted EK(A, B)). Similarly, data transfers between infrastructure nodes “B” and “C” are encrypted using a key known to both nodes “B” and “C” (denoted EK(B,C)). Data transfers involving infrastructure node “A” and another node are encrypted using a key known to node “A” (denoted EK( . . . ,A)), and data transfers involving infrastructure node “C” and another node are encrypted using a key known to node “C” (denoted EK(C, . . . )). In these figures, an encryption key is denoted as EK(x,y), where x and y represent the infrastructure nodes using that key.
Data encryption and decryption occur at the MAC layer level in FIG. 2 and at the network layer level in FIG. 3. In FIG. 2, data messages being transferred to the next “hop” in a communication path are decrypted and re-encrypted at the MAC layer 202. The data messages may not need to be provided to the network layer 204 in FIG. 2. In FIG. 3, data messages being transferred to the next “hop” in a communication path may not stop at the MAC layer 202 and instead move up to the network layer 204, where the decryption and re-encryption may occur. The exact layer used to perform the encryption and decryption could vary depending on the circumstances. For example, encryption and decryption at the MAC layer 202 could be used as a general rule, and encryption and decryption at the network layer 204 could be used when changes to the underlying MAC protocol cannot be made. Whatever the case, encryption and decryption of data may occur as noted above, where different keys are used to transport data between different infrastructure nodes.
As shown in FIG. 4, the leaf nodes may similarly include a MAC layer 402, a network layer 404, and an application layer 406. These layers may represent the same or similar layers as in the infrastructure nodes. As noted above, a leaf node can communicate with multiple infrastructure nodes using the same encryption key. This shared encryption key is denoted EK(S) and is known and used by two infrastructure nodes in FIG. 4. The infrastructure nodes may continue to communicate amongst themselves using the same technique(s) shown in FIGS. 2 and 3. In particular embodiments, when multiple infrastructure nodes are transmitting the same message to a leaf node, nonce values used for each of the infrastructure nodes may contain the source address of the message originator (in order to avoid leaking information through nonce collision).
Any suitable data could be transferred between leaf and/or infrastructure nodes in this manner. For example, the leaf nodes could include sensors that generate sensor data (such as measurement data). The sensor data, as well as other general data, could be transferred from the leaf nodes to the infrastructure nodes as shown in FIG. 4. The sensor and general data could then be transferred between infrastructure nodes as shown in FIGS. 2 or 3. In particular embodiments, sensor data and general data could be transferred between infrastructure nodes as shown in FIG. 2, and only general data could be transferred between infrastructure nodes as shown in FIG. 3 (although other embodiments could be used).
Although FIGS. 2 through 4 illustrate examples of techniques for data encryption in an industrial control and automation system, various changes may be made to FIGS. 2 through 4. For example, each of the nodes may include any suitable layers in their respective implementations. Also, other types of communications could occur between nodes in the wireless network, and different or common encryption keys could be used for these various communications.
FIG. 5 illustrates an example encrypted data flow 500 between components in an industrial control and automation system according to this disclosure. The embodiment of the encrypted data flow 500 shown in FIG. 5 is for illustration only. Other embodiments of the encrypted data flow 500 could be used without departing from the scope of this disclosure.
As shown in FIG. 5, the leaf nodes may include a frequency-hopping spread-spectrum (FHSS) MAC layer (FH MAC) and an FHSS physical layer (FH PHY). These layers support wireless communications between leaf nodes and infrastructure nodes using FHSS techniques. The leaf nodes may also include a network layer (NET), which provides various functions for supporting the creation and use of a wireless network (such as routing, forwarding, and error handling functions). The leaf nodes may further include a security layer (SEC), which supports various security-related functions associated with the wireless network (such as authentication). In addition, the leaf nodes may include an application interface layer (AIL) that provides an interface for applications executed on the leaf nodes at an application and mobile object layer (APP/MO).
The infrastructure nodes may include FHSS MAC and physical layers, which are used to communicate with the leaf nodes. A network layer (NET), security layer (SEC), application interface layer (AIL), and mobile object layer (MO) are also used in the infrastructure nodes. An address resolution protocol layer (ARP) can be used to identify a particular node's hardware address, and an address allocation protocol layer (AAP) can support multicasting of information to multiple nodes. A first 802.11 MAC and physical layer pair can be used for wireless fidelity (WiFi) communications with various wireless devices in the system 100, such as wireless controllers or hand-held user devices. A second 802.11 MAC and physical layer pair can be used for wireless mesh communications with other infrastructure nodes (gateway or other). These communications can be supported by a mesh layer (MESH) in the infrastructure nodes. TCP/UDP and IP layers represent the transport and network layers supporting the wireless mesh network.
The gateway infrastructure nodes may include the same layers as the infrastructure nodes. In this example, the gateway infrastructure nodes also include an 802.3 MAC layer and an 802.3 physical layer, which support communications over a wired network (such as the network 106). The gateway infrastructure nodes also include a Modbus/OPC layer, which supports communications over the wired network with the appropriate protocols.
A control system (such as the controller 104) can use an 802.3 MAC layer and an 802.3 physical layer to communicate with one or more gateway infrastructure nodes. Also, TCP/UDP, IP, and Modbus/OPC layers in the control system support communications with the gateway infrastructure node(s). In addition, a control application layer (CONTROL APP) provides an interface for the control applications executed by the controller 104, such as applications that use data from one or more sensors to generate control signals for one or more actuators.
The dashed lines in FIG. 5 illustrate how data can flow between a leaf node and a control system through one or more infrastructure nodes (gateway or other). As noted above, the leaf node could transmit data to and receive data from multiple infrastructure nodes, each of which can use the same cryptographic key to communicate with the leaf node. Also, communications between different pairs of infrastructure nodes can occur using different cryptographic keys. Decryption of data and subsequent re-encryption of data could occur at any suitable locations, such as in the MAC layers and/or the network layers of the infrastructure nodes.
Although FIG. 5 illustrates one example of an encrypted data flow 500 between components in an industrial control and automation system, various changes may be made to FIG. 5. For example, each device in FIG. 5 could include any other or additional layers depending on its particular implementation. Also, while particular protocols or technologies (such as FHSS, WiFi, 802.11, and 802.3) are noted here, these are for illustration only.
FIG. 6 illustrates an example wireless node 600 in an industrial control and automation system according to this disclosure. The wireless node 600 could, for example, represent a leaf node, infrastructure node, or gateway infrastructure node in the system 100 of FIG. 1 or other system. The embodiment of the wireless node 600 shown in FIG. 6 is for illustration only. Other embodiments of the wireless node 600 could be used without departing from the scope of this disclosure.
As shown in FIG. 6, the device 600 includes a controller 602. The controller 602 controls the overall operation of the device 600. For example, the controller 602 may receive or generate data to be transmitted externally, and the controller 602 could provide the data to one or more other components in the device 600 for transmission over a wired or wireless network. The controller 602 could also receive data over a wired or wireless network and use or pass on the data. As a particular example, the controller 602 in a sensor leaf node could provide sensor data for transmission, and the controller 602 in an actuator leaf node could receive and implement control signals (note that a leaf node could represent a combined sensor-actuator device). As another example, the controller 602 in an infrastructure node could receive data transmitted wirelessly, determine a next hop for the data (if any), and provide the data for transmission to the next hop (if any). As a third example, the controller 602 in a gateway infrastructure node 112 could receive data from a wired network and provide the data for wireless transmission (or vice versa). The controller 602 could perform any other or additional functions to support the operation of the device 600, such as the decryption of received data and the encryption of transmitted data. The controller 602 includes any suitable hardware, software, firmware, or combination thereof for controlling the operation of the device 600. As particular examples, the controller 602 could represent a processor, microprocessor, microcontroller, field programmable gate array (FPGA), or other processing or control device.
A memory 604 is coupled to the controller 602. The memory 604 stores any of a wide variety of information used, collected, or generated by the device 600. For example, the memory 604 could store information received over one network that is to be transmitted over another network. The memory 604 includes any suitable volatile and/or non-volatile storage and retrieval device or devices.
The device 600 also includes a wireless transceiver 606 coupled to an antenna 608. The transceiver 606 and antenna 608 can be used by the device 600 to communicate wirelessly with other devices. For example, in a leaf node, the transceiver 606 and antenna 608 can be used to communicate with infrastructure nodes. In an infrastructure node or gateway infrastructure node, the transceiver 606 and antenna 608 can be used to communicate with leaf nodes. One or more additional transceivers 610 could also be used in the device 600. For instance, in an infrastructure node or gateway infrastructure node, the additional transceiver(s) 610 could be used to communicate with WiFi devices and with other infrastructure nodes or gateway infrastructure nodes. The additional transceivers 610 may be coupled to their own antennas 612 or share one or more common antennas (such as antenna 608). Each transceiver includes any suitable structure for transmitting and/or receiving wireless signals. In some embodiments, each transceiver represents a radio frequency (RF) transceiver, and each antenna represents an RF antenna (although any other suitable wireless signals could be used to communicate). Also, each transceiver could include a transmitter and a separate receiver.
If the device 600 represents a gateway infrastructure node, the device 600 may further include one or more wired network interfaces 614. The wired network interfaces 614 allow the device 600 to communicate over one or more wired networks, such as the network 106. Each wired network interface 614 includes any suitable structure for transmitting and/or receiving signals over a wired network, such as an Ethernet interface.
Although FIG. 6 illustrates one example of a wireless node 600 in an industrial control and automation system, various changes may be made to FIG. 6. For example, various components in FIG. 6 could be combined, subdivided, or omitted and additional components could be added according to particular needs. Also, in general, a “wireless node” may represent any device that can transmit and/or receive data wirelessly (even if the “wireless node” has the ability to transmit and/or receive data over a wired connection, as well).
FIGS. 7 and 8 illustrate example methods for providing security in a wireless network according to this disclosure. The embodiments of the methods shown in FIGS. 7 and 8 are for illustration only. Other embodiments of the methods could be used without departing from the scope of this disclosure.
As shown in FIG. 7, a method 700 includes receiving a data message over a network at step 702. This may include, for example, an infrastructure node 108 a-108 e receiving the data message over a wireless connection. This may also include a gateway infrastructure node 112 receiving the data message over a wired or wireless connection. The message could come from any suitable source, such as another infrastructure node or gateway infrastructure node or from a leaf node. The data message may be encrypted using an encryption key known to the receiving device.
A determination is made as to whether the data message is to be passed along to a next hop in a communication route at step 704. This may include, for example, the infrastructure node or gateway infrastructure node examining the data message to determine if the message is destined for that node and/or for any other destinations.
If the data message is to be passed along, the data message is decrypted at step 706 and encrypted at step 708. This may include, for example, decrypting the data message using a first encryption key known to the infrastructure node or gateway infrastructure node. The first encryption key could, for instance, be used only by that infrastructure node or gateway infrastructure node and a neighboring node. This may also include encrypting the data message using a second encryption key known to the infrastructure node or gateway infrastructure node. The second encryption key could, for instance, be used only by that infrastructure node or gateway infrastructure node and by the next node along the communication route. The re-encrypted message is then communicated at step 710.
If the data message is not to be passed along, the data message is decrypted at step 712 and then processed and used at step 714. This may include, for example, decrypting the data message using an encryption key known to the infrastructure node or gateway infrastructure node. Also, the message could be processed and used in any suitable manner, such as by examining the message contents, taking any specified actions, or providing any requested data.
It may be noted that while the method 700 includes “yes” and “no” branches from step 704, both branches could apply in certain situations. For example, a broadcast or multicast message could be intended for the infrastructure node or gateway infrastructure node and for other nodes. In these cases, the functions in both branches could occur (although only a single decryption operation may be necessary).
As shown in FIG. 8, a method 800 includes generating a first data message at a leaf node at step 802. This may include, for example, the leaf node generating a data message containing sensor or actuator data. The data message is encrypted at step 804 and transmitted to multiple wireless nodes at step 806. This may include, for example, encrypting the data message using an encryption key known to the leaf node and to two or more infrastructure nodes (gateway or other). The data message can be encrypted once, and the encrypted data message can then be broadcast or otherwise communicated to multiple infrastructure nodes.
A second data message is received at the leaf node at step 808. This may include, for example, the leaf node receiving the data message from one or multiple infrastructure nodes. The data message is decrypted at step 810 and processed and used at step 812. This may include, for example, decrypting the data message using the encryption key known to the leaf node and the two or more infrastructure nodes. Also, the second data message could be processed and used in any suitable manner, such as by examining the message contents, taking any specified actions, or providing any requested data.
Although FIGS. 7 and 8 illustrate examples of methods for providing security in a wireless network, various changes may be made to FIGS. 7 and 8. For example, while shown as a series of steps in each figure, various steps in FIGS. 7 and 8 could overlap, occur in parallel, occur multiple times, or occur in a different order.
communicating the first encrypted data to the third wireless routing node.
exchanging encryption keys at the first wireless routing node with any wireless node having (i) an active link with the first wireless routing node and (ii) a certificate signed by the trust authority.
3. The method of claim 1, wherein decrypting the received first data and encrypting the first decrypted data are performed at one or more of: a MAC layer and a network layer in the first wireless routing node.
4. The method of claim 1, wherein the first wireless routing node and the third wireless routing node use a same encryption key to communicate with one or more leaf nodes in the wireless network.
5. The method of claim 1, further comprising receiving second data at the first wireless routing node, wherein the second data is associated with at least one of: a sensor and an actuator in the industrial control and automation system.
provide the first encrypted data to the at least one transceiver for communication to the third wireless routing node.
7. The wireless routing node of claim 6, wherein the at least one controller is configured to exchange encryption keys at the wireless routing node with any other wireless node having (i) an active link with the wireless routing node and (ii) a certificate signed by the trust authority.
8. The wireless routing node of claim 6, wherein the at least one controller is configured to decrypt the received first data and encrypt the first decrypted data at one or more of: a MAC layer and a network layer in the wireless routing node.
9. The wireless routing node of claim 6, wherein the wireless routing node and the third wireless routing node are configured to use a same encryption key to communicate with one or more leaf nodes in the wireless network.
10. The wireless routing node of claim 6, wherein the at least one controller is further configured to receive second data via the at least one transceiver, the second data associated with at least one of: a sensor and an actuator in the industrial control and automation system.
transmitting the first data to multiple second wireless nodes in the wireless network, wherein the second wireless nodes are infrastructure nodes and are capable of using the same first encryption key to decrypt the first data.
communicating the encrypted data at each of the second wireless nodes.
decrypting the second data using the encryption key.
14. The method of claim 11, wherein encrypting the first data using the first encryption key comprises performing a single cryptographic operation to encrypt the first data for communication to the multiple second wireless nodes.
exchanging encryption keys with one of the second wireless nodes based on the verification, the exchanged encryption keys including the first encryption key.
exchanging encryption keys at the first wireless node with any wireless node having (i) an active link with the first wireless node and (ii) a certificate signed by the trust authority.
17. The method of claim 11, wherein encrypting the first data is performed at one or more of: a Medium Access Control (MAC) layer and a network layer in the first wireless node.
18. The method of claim 11, wherein the first wireless node is at least one of: a sensor and an actuator in the industrial control and automation system.
19. The method of claim 1, wherein a MAC address of the first wireless routing node and a MAC address of the third wireless routing node are registered with the trust authority.
exchanging encryption keys between the first and third wireless routing nodes, the encryption keys including the second encryption key uniquely associated with communications between the first and third wireless routing nodes.
wherein a MAC address of the third wireless routing node is also registered with the trust authority.
"IP/MPLS-Based VPNS, Layer-3 vs. Layer-2", Foundry Networks, 2002, 16 pages.
"XYR 5000 Wireless Transmitters-Honeywell Solutions for Wireless Data Acquisition and Monitoring", Honeywell, Feb. 2006, 6 pages.
Arvinderpal S. Wandert, et al., "Energy Analysis of Public-Key Cryptography for Wireless Sensor Networks", Proceedings of the 3rd IEEE Int'l. Conf. on Pervasive Computing and Communications (PerCom 2005), 2005 IEEE, 5 pages.
Communication pursuant to Article 94(3) EPC dated Oct. 28, 2009 in connection with European Patent Application No. 08163537.7.
Dr. Soumitri Kolavennu, Presentation, "WNSIA MAC Layer", ISA SP100 meeting, Feb. 14, 2007, 24 pages, see esp. p.17.
European Search Report dated Aug. 24, 2009 in connection with European Patent Application No. 08163537.7.
Frederick Hidle, "System and Method for Providing Secure Network Communications", U.S. Appl. No. 11/981,213, filed Oct. 30, 2007.
Office Action dated Dec. 17, 2010 in connection with European Patent Application No. 08163537.7.
Partial European Search Report dated Apr. 28, 2009 in connection with European Patent Application No. 08163537.7.
Ramakrishna S. Budampati, et al., "System and Method for Providing Simultaneous Connectivity Between Devices in an Industrial Control and Automation or Other System", U.S. Appl. No. 11/981,212, filed Oct. 30, 2007.

References: §119
 Application No. 60
 Application No. 08163537
 Application No. 08163537
 Application No. 08163537
 Application No. 08163537