Systems and methods for write protecting foundation fieldbus linking devices

• US 8,762,528 B2
• Filed: 06/13/2011
• Issued: 06/24/2014
• Est. Priority Date: 05/31/2011
• Status: Active Grant

• Current Assignee: GE Infrastructure Technology, LLC (General Electric Company)
• Original Assignee: General Electric Company
• Inventors: Smith, Steven William, Pettigrew, William Robert
• Primary Examiner(s): Joo, Joshua
• Application Number:
  US13/159,159
• Publication Number:
  US 20120310378A1
• Time in Patent Office: 1,107 Days
• Field of Search: 709/208, 709/211, 709/206, 709223-225
• US Class Current: 709/225
• CPC Class Codes: H04L 2012/4026 Bus for use in automation systems
• CPC Class Codes: H04L 41/0853 by actively collecting configuration information or by backing up configuration information
• CPC Class Codes: H04L 41/0897 by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: Y04S 40/00 Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
• CPC Class Codes: Y04S 40/18 Network protocols supporting networked applications, e.g. including control of end-device applications over a network

Abstract

Systems and methods for write protecting Foundation Fieldbus linking devices are described. A message output by an external system for communication to a Foundation Fieldbus linking device may be received by a gateway device. The linking device may be identified by a virtual address included in the received message. The gateway device may determine whether the message includes a command to write data to the linking device or a Foundation Fieldbus device connected to the linking device. If it is determined that the message does not include a command to write data, then the gateway device may direct communication of the message to the linking device. If, however, it is determined that the message includes a command to write data, the gateway device may generate an exception for preventing the requested write operation.

Claims

1. A method comprising:

receiving, by a gateway device comprising one or more computers, a message output by an external system for communication to a Foundation Fieldbus linking device, wherein the linking device is identified by a virtual address, wherein the virtual address represents a plurality of redundant linking devices;

determining, by the gateway device, whether the message comprises a command for a write operation to write data to the linking device or to a Foundation Fieldbus device connected to the linking device, wherein a header of the message is evaluated to determine whether the message includes the command to write data; and

directing, by the gateway device if the gateway device determined that the message does not include the command to write data, communication of the message to the linking device;

or

generating, by the gateway device if the gateway device determined that the message includes the command to write data, an exception for preventing the write operation.

2. The method of claim 1, wherein determining whether the message comprises a command to write data comprises:

identifying, by the gateway device, a message type associated with the message; and

determining, by the gateway device, whether the identifying message type is associated with the write operation.

3. The method of claim 2, wherein identifying a message type comprises identifying a message type based upon an evaluation of a header associated with the message.

4. The method of claim 1, wherein it is determined that the message comprises a command to write data, and further comprising:

generating, by the gateway device, an error message associated with an unauthorized attempt to write data; and

communicating, by the gateway device to the external system, the generated error message.

5. The method of claim 1, wherein it is determined that the message does not comprise a command to write data, and further comprising:

determining, by the gateway device, a physical address associated with the linking device; and

directing, by the gateway device based at least in part upon the determined physical address, communication of the message to the linking device.

6. The method of claim 5, further comprising:

determining, by the gateway device based at least in part upon an analysis of the received message, an identity of the linking device,

wherein determining the physical address comprises determining the physical address based at least in part upon the determined identity.

7. The method of claim 6, wherein determining an identity of the linking device comprises:

identifying, based at least in part upon the analysis of the received message, a Foundation Fieldbus device that is an intended recipient of the received message; and

identifying the linking device as a linking device to which the Foundation Fieldbus device is connected.

8. The method of claim 5, wherein the message comprises a first message, and further comprising:

receiving, by the gateway device, a second message output by the linking device in response to the first message;

modifying, by the gateway device, the second message in order to associate the virtual address with the second message; and

providing, by the gateway device, the modified second message to the external system.

9. The method of claim 8, wherein receiving a second message comprises receiving one of (i) a message associated with operation of the linking device or (ii) a message associated with the Foundation Fieldbus device connected to the linking device.

10. The method of claim 1, wherein receiving a message output by an external system comprises receiving a message output by an asset management system.

11. A system comprising:

at least one memory operable to store computer-executable instructions;

at least one processor configured to access the at least one memory and execute the computer-executable instructions to;

receive a message output by an external system for communication to a Foundation Fieldbus linking device, wherein the linking device is identified by a virtual address, wherein the virtual address represents a plurality of redundant linking devices;

determine whether the message comprises a command for a write operation to write data to the linking device or to a Foundation Fieldbus device connected to the linking device, wherein a header of the message is evaluated to determine whether the message includes the command to write data; and

direct, if the processor determined that the message does not include the command to write data, communication of the message to the linking device;

or

generate, if the processor determined that the message includes the command to write data, an exception for preventing the write operation.

12. The system of claim 11, wherein the at least one processor is configured to determine whether the message comprises a command to write data by executing the computer-executable instructions to:

identify a message type associated with the message; and

determine whether the identified message type is associated with the write operation.

13. The system of claim 11, wherein the message type is identified based upon an evaluation of a header associated with the message.

14. The system of claim 11, wherein it is determined that the message comprises a command to write data, wherein the at least one processor is configured to determine an identity of the linking device by executing the computer-executable instructions to:

generate an error message associated with an unauthorized attempt to write data; and

direct communication of the generated error message to the external system.

15. The system of claim 11, wherein it is determined that the message does not comprise a command to write data, and wherein the at least one processor is configured to determine an identity of the linking device by executing the computer-executable instructions to:

determine a physical address associated with the linking device; and

direct, based at least in part upon the determined physical address, communication of the message to the linking device.

16. The system of claim 15, wherein the at least one processor is further configured to execute the computer-executable instructions to:

determine, based at least in part upon an analysis of the received message, an identity of the linking device; and

determine the physical address based at least in part upon the determined identity.

17. The system of claim 16, wherein the at least one processor is configured to determine an identity of the linking device by executing the computer-executable instructions to:

identify, based at least in part upon the analysis of the received message, a Foundation Fieldbus device that is an intended recipient of the received message; and

identify the linking device as a linking device to which the Foundation Fieldbus device is connected.

18. The system of claim 15, wherein the message comprises a first message, and wherein the at least one processor is configured to determine an identity of the linking device by executing the computer-executable instructions to:

receive a second message output by the linking device in response to the first message;

modify the second message in order to associate the virtual address with the second message; and

direct communication of the modified second message to the external system.

19. The system of claim 18, wherein the second message comprises one of (i) a message associated with operation of the linking device or (ii) a message associated with the Foundation Fieldbus device connected to the linking device.

20. The system of claim 11, wherein the external system comprises an asset management system.