Abstract:
An apparatus and method for communicating DNP protocol messages across networks that maybe slower, less reliable, and/or bandwidth-cost-constrained are provided. A DNP Bridge server capable of sending/receiving messages to/from a DNP Master System, a DNP Bridge Slave Interface unit capable of sending/receiving DNP message to/from a DNP Slave Device are used. The DNP Bridge server and DNP Bridge Slave Interface act together to transparently link the DNP Master System to the DNP Slave Device over slow, unreliable networks. The DNP Bridge server and DNP Bridge Slave Interface use a combination of techniques to minimize message transmissions and DNP protocol errors over slow, unreliable networks.

Description:
PRIORITY  
       [0001]    This application claims the priority of the U.S. Provisional Patent Application Serial No. 60/330,439 filed on Oct. 22, 2001 entitled “System for bridging DNP network messages over, slow, unreliable, bandwidth-cost-constrained networks.” 
     
    
     
       BACKGROUND OF THE INVENTION  
         [0002]    1. Field of the Invention  
           [0003]    The present invention generally relates to wireless bridging of messages within remote monitoring and control systems. More specifically, the invention relates to wireless network systems used to bridge supervisory control and distribution automation systems used by electrical and other utility companies to monitor and control remote equipment.  
           [0004]    2. Background Information  
           [0005]    Many industries utilize remote mechanical and electrical equipment in their operations. For example, electric power utilities utilize transformers, capacitor banks, voltage regulators, remote generators, and other electronic equipment distributed over a large geographical area. It is desirable for electric power companies to remotely monitor and control their power distribution equipment. Using telemetry to monitor and control power distribution equipment allows the power companies to check the status of, and enable or disable equipment like power transformers that may be miles away from the utility&#39;s headquarters.  
           [0006]    Presently, the Distributed Network Protocol language, also known as the DNP network protocol standard, allows many different vendors of electrical power distribution and other equipment to communicate with a central monitoring and control system. The DNP network protocol specifies a DNP Master System, also known as a Supervisory Control and Distribution Automation System, or SCADA system, and a limited number of DNP Slave Devices. The DNP Master is typically a console system that allows an operator to view the status of and control equipment in the company&#39;s DNP network. The company&#39;s DNP network is made up of DNP Slave Devices, typically embedded into or adapted directly to power distribution or other equipment, communicating to the DNP Master System through a network interface.  
           [0007]    The DNP Master System and DNP Slave Devices typically use dedicated leased line or dial-up modem line to communicate. Although these communication lines are typically reliable and provide adequate communication bandwidth for this purpose, they are costly to install and operate, especially for equipment that is far from existing telephone lines.  
           [0008]    Newer communications technologies are now available that allow data communications using wireless public carrier networks. For example, two national companies currently offer cellular control channel wireless data service that has broad coverage throughout the United States. Typically, the fixed monthly cost for this service is far less than a dedicated leased line from the phone company. However, cellular control channel wireless data service communication bandwidth is significantly lower than that of dedicated leased lines. Cellular control channel data bandwidth is typically tens of bits per minute, while leased line communication bandwidth is typically tens of thousands of bits per second. Additionally, leased line data communications typically allow for very large or even unlimited amounts of data to be transmitted per billing cycle. Cellular control channel data communications becomes cost prohibitive when even modest amounts of data are transmitted in a billing cycle.  
           [0009]    In many DNP applications, the majority of DNP network traffic is generated by the DNP Master System frequently polling the DNP Slave Devices for status information that rarely changes. A system is needed to minimize the amount of DNP network traffic generated by these status messages in order to keep the cost of the service low.  
           [0010]    Most DNP applications were developed assuming the characteristics of a leased line communications link between the DNP Master System and the DNP Slave Device. That is, a communications link that supports thousands or even tens of thousands of bits per second and that sending a great deal of data over the communications link would not have a significant effect on the cost of the communication link. In fact, the Distributed Network Protocol, as well as most other protocols used with distributed networks, is quite verbose. Therefore, several problems arise when simply replacing a leased line communication link with a slower communication link such as cellular control channel. Many DNP commands sent from the DNP Master System may time-out waiting for a response from the DNP Slave Device because of the slow speed of the underlying data transport mechanism. The DNP protocol allows for packet sizes exceeding 2048 bytes. Many of the slower, less reliable network technologies support maximum packet sizes significantly smaller than 2048 bytes.  
           [0011]    A system is needed that can bridge DNP messages using a slower, and perhaps unreliable network, such as a cellular phone system, that would otherwise cause time-out errors to occur in equipment originally designed for use with leased telephone lines.  
           [0012]    In a DNP network, a control message is sometimes sent to a group of DNP Slave Devices simultaneously. A system is needed to “broadcast” the control message to the DNP Slave Device group with minimum network traffic.  
           [0013]    [0013]FIG. 1 shows how the prior art typically communicates messages in a DNP network. The DNP Master System  1  communicates a DNP message over Local Area Network  2  to a modem multiplexer  3 . Modem multiplexer  3  sends the message via one or more dedicated or dial-up modem lines  4  to the ‘dumb’ modem  5 . Typically, a serial interface  6  is used to send the message from ‘dumb’ modem  5  to the DNP Slave Device  7 . Return messages are sent in a reciprocal manner from the DNP Slave Device  7  back to the DNP Master System  1 .  
           [0014]    The existing leased line based data communications afford a certain amount of security in a DNP network system. That is, a potential attacker would typically need to physically tap into a physical phone company line to covertly monitor or control a DNP slave device. Monitoring or controlling many DNP devices simultaneously becomes even more difficult. Transmitting DNP network messages over the Internet or wireless networks opens the doorway to attackers that are not physically near the DNP network. The Internet or wireless networks potentially allow the attacker to target many DNP devices simultaneously. A system is needed to ensure that the DNP Master System can be sure it is communicating with authorized DNP Slave Devices and DNP Slave Devices are communicating with authorized DNP Masters Systems. The prior art does not provide a mechanism for encrypting or authenticating messages sent in a DNP network.  
           [0015]    Additionally, DNP Master Systems are very expensive to install and maintain. Some smaller companies have not been able to justify the expense of a full DNP Master System. Yet many companies have already invested in equipment that supports the DNP. Adding an Internet web-based user interface to the invented DNP Bridge server could provide smaller companies with many of the benefits of a full DNP Master System, at a much lower cost.  
           [0016]    The prior art is limited in scope because it does not provide for a means to address the limitations of using wireless networks that may be slower, less reliable or otherwise incompatible with existing DNP networks. The prior art does not include mechanisms to ensure that, among other problems, the DNP master does not generate an excessive amount of traffic over the DNP network and that the DNP master, or DNP slave devices do not generate excessive DNP message timeouts, potentially “thrashing” the DNP network.  
           [0017]    Additional objects, advantages and novel features of the invention will be set forth in part in the description which follows and in part will become apparent to those skilled in the art upon examination of the following or may be learned by practice of the invention. The objects and advantages of the invention may be realized and attained by means of the instrumentalities and combinations particularly pointed out in the appended claims.  
         SUMMARY OF THE INVENTION  
         [0018]    Accordingly, it is an object of the present invention to provide a system for reliably communicating DNP messages between a DNP Master System and a DNP Slave Device over networks that may be slower, less reliable, data transfer rate or bandwidth-constrained, or cost constrained. It is another object of the invention to provide a system for communicating DNP messages sent to or from a DNP Master System via an invented DNP Bridge server, to or from DNP Slave Devices via an invented DNP Slave Interface unit. It is another object of the invention to minimize the changes to the DNP Master System and DNP Slave Devices to work with the inventive system.  
           [0019]    It is a further object of the present invention to provide a web-based or other user interface to the DNP Bridge server for directly monitoring and controlling the DNP Slave Devices.  
           [0020]    It is another object of the invention to provide a system for minimizing the amount of traffic transmitted over the portion of the network that may be slow, unreliable, and bandwidth-cost-constrained between a DNP Master Device and a DNP Slave Device.  
           [0021]    It is another object of the invention to provide a system for securing and authenticating communications between DNP devices.  
           [0022]    It is another object of the invention to provide a system for grouping DNP Slave Devices and providing a system for sending messages to all devices in the group with a minimum amount of network traffic.  
           [0023]    These objects are achieved by use of a first bridging device which is interconnected to the distributed network master system and is capable of wireless communication, typically through the control channels of a commercial cellular phone network with a number of second bridging devices. The second bridging devices are, in turn, interconnected to the various slave devices of the distributed network. The bridging devices use the original preexisting distributed language protocol to communicate with the various distributed network devices, and a second language protocol, which is far more compact, condensed or compressed to communicate over the control channels of the cellular phone network between the various bridging devices.  
           [0024]    The second bridging devices are programmed to only pass on certain information from the slave devices to the first bridging device. Such things as routine reports of unchanged status or condition of the equipment being monitored by the slave devices are not routinely passed on by the second bridging devices. Instead, by using combinational logic, the second bridging devices will only transmit those conditions or signals that are necessary to properly monitoring the condition of the various pieces of equipment being monitored. For example, reports will be sent to the first bridging device in the event of a change in equipment status or a change in a monitored parameter value for which a report is required. The information transmitted to the first bridging device is cached therein and used as the data for communication with the distributed network master system when it is responding to the network master system, for example, responding to routine, timed, status inquiries.  
           [0025]    The first bridging device is designed to emulate the various distributed network slave devices in its communications with the distributed network master system, and responding with the cached information that it receives from the second bridging devices. The first bridging device only sends a communication to the second bridging devices when, in accordance with its preprogrammed logic that establishes the criteria for when to communicate, it is necessary. In this manner, the amount of data transferred between the various bridging devices over the cellular phone network is minimized. This, in turn, allows for the use of a wireless network, which has a slower, lower capacity, data transmission rate, as a communication medium in a distributed network that uses a language protocol designed for use with a communication medium having much higher data transmission rates and capacity, typically that of a dedicated phone line.  
           [0026]    The information and commands that are passed from the first bridging device to the various secondary bridging devices, when received by the second bridging devices, is decoded and translated back into the original distributed network protocol language and sent to the appropriate network slave device. In this manner, the secondary bridging devices emulate and appear as the original network master system to the slave devices.  
           [0027]    Various encryption systems may be employed to protect and authenticate the various communications being sent over the airwaves on the public cellular network.  
           [0028]    Still other objects and advantages of the present invention will become readily apparent to those skilled in this art from the following detailed description wherein I have shown and described only the preferred embodiment of the invention, simply by way of illustration of the best mode contemplated by carrying out my invention. As will be realized, the invention is capable of modification in various obvious respects all without departing from the invention. Accordingly, the drawings and description of the preferred embodiment are to be regarded as illustrative in nature, and not as restrictive. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0029]    [0029]FIG. 1 shows how the prior art typically communicates messages in a DNP network.  
         [0030]    [0030]FIG. 2 shows how the present invention system typically communicates messages in a DNP network.  
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0031]    While the invention is susceptible of various modifications and alternative constructions, certain illustrated embodiments thereof have been shown in the drawings and will be described below in detail. It should be understood, however, that there is no intention to limit the invention to the specific form disclosed, but, on the contrary, the invention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention as defined in the claims.  
         [0032]    The invention is presented here in the context of usage with a typical Supervisory Control and Distribution Automation System, or SCADA system, which uses Distributed Network Protocol language, or DNP, which is typical of those used by electric utility companies in conjunction with power distribution systems. However, it should be distinctly understood that the invented system can be used in virtually any distributed control network, for example, natural gas distribution systems, water and other utility systems, and many other types of systems, such as heating and ventilation systems for large building complexes, and the like. The invented system will generally work well with any distributed network system wherein there is a centralized control system and a number of dispersed networks of slave systems for either reporting status and/or parameters, or functioning as remote control units.  
         [0033]    The present invention, in the context of a SCADA system utilizing DNP network devices, employs a first bridging device, herein called the DNP Bridge Server, a second bridging device, hereinafter call the DNP Bridge Slave Interface, a highly condensed or compressed transmission format message system, and a collection of software algorithms to achieve the objects of the invention.  
         [0034]    [0034]FIG. 2 shows, in general terms, how the invented system typically communicates messages within a DNP network. The first or primary DNP network device is the DNP Master System  12 . It communicates DNP messages over Local Area Network  14  to router  16 . Router  16  sends the DNP messages via the Internet  18 , or a dedicated line, to the DNP Bridge Server  20 . DNP Bridge Server  20  forms a transmission formatted message and sends the new message via a cellular transmission to the Cellular Bridge Server  22  of the publicly available cellular transmission service being used. Cellular Bridge Server  22  then transmits the transmission formatted message over the cellular network to the invented DNP Bridge Slave Interface  22 . DNP Bridge Slave Interface  22  then translates the transmission formatted message back into its original DNP message and sends it via a serial interface to the other network devices which are typically DNP′ Slave Devices  24 .  
         [0035]    In the inventive system, to the appearance of the DNP Master System, the DNP Bridge Server emulates as the DNP Slave Device. To the appearance of the DNP Slave Device, the DNP′ Slave Interface unit emulates as the DNP Master System. In the prior art, the DNP Master System sends DNP messages through a series of “dumb” communications links (i.e. LAN, Modem Multiplexer, leased line, modem) directly to the DNP Slave Device. In the present invention system, the DNP Bridge Server is capable of acting as the DNP Slave Device. Conversely, the DNP Slave Interface unit is capable of acting as the DNP Master System. Through this means, many additional benefits can be realized, not the least of which is that the amount of information being sent back and forth between the DNP Master System and the DNP Slave Device is minimized, thus reducing costs and bandwidth capacity requirements.  
         [0036]    Typically, the DNP Master System will poll the DNP Slave Devices regularly with DNP Status request messages. It is either looking for information concerning the status of the monitored equipment, such as which switches are closed and which are open, or parameter values, such as what is the voltage or current load, at a certain location. The DNP Master System is looking for changes in the status of the DNP Slave Devices that may be indicative of an alarm condition. Often, the data sent back by the DNP Slave Devices does not change. In the inventive system, the DNP Master System will poll the DNP Bridge Server for DNP Slave Device input status. Instead of relaying the DNP Status Message across the bandwidth-cost-constrained portion of the network, the DNP Bridge Server will return status values cached from the last time the DNP Slave Interface unit sent status information. Since, as will be later explained, the DNP Slave Interface unit only sends a wireless message upon the occurrence of a change in either status or parameter values that it is programmed with combination logic to recognize, the last cached status and parameter values will be accurate.  
         [0037]    More specifically, in the inventive system, the DNP Bridge Server and the DNP Bridge Slave Interface use a combination of transmission format messages, caching of data, and combinational logic to minimize the amount of data transferred over the bandwidth-cost-constrained portion of the network. At initialization, the DNP Slave Interface unit retrieves all of the DNP Slave Device&#39;s input values via a DNP status request message. The DNP Slave Interface saves these values and sends a copy of the values to the DNP Bridge Server. Additionally, at initialization, the DNP Slave Interface unit is programmed with combinational logic, similar to the logic used in the DNP Master System to trigger an alarm on the console. Examples of typical combination logic sequences are as follows: for a binary change event—if a given input value changes from one to zero, or zero to one, for a configurable period of time, the event is triggered; for an analog change event—if the analog input value moves from one configured range, either fixed, stair stepped or computer moving average, to another for a configurable period of time, the event is triggered; and for time scheduled events—the current value for one or more inputs is transmitted on a configurable time schedule.  
         [0038]    For example, assume the DNP Master System is programmed to trigger an alarm condition on the console when a DNP Slave Device&#39;s input exceeds twenty-five percent (25%) of its normal value. In this case, the DNP Slave Interface unit might be programmed to poll the DNP Slave Device once per minute. If the DNP Slave Interface unit detected that any of the DNP Slave Device&#39;s inputs had exceeded twenty-five percent (25%) of their normal value, the DNP Bridge Slave Interface unit will send a transmission format asynchronous status update message to the DNP Bridge Server. The next time the DNP Master System polls the DNP Bridge Server, it will receive the updated status condition and signal an alarm on the console.  
         [0039]    Some DNP messages will need to be passed from the DNP Master System down to the DNP Slave Device for a synchronous response. In this case, problems may arise due to the significant reduction in bandwidth in the slower wireless network. DNP Master Systems are typically programmed to “time-out” a message if a response is not received after a short period of time. Typically, the DNP Master System will retry sending the message. Additionally, DNP messages contain a significant amount of extraneous information that consumes extra space in the network message.  
         [0040]    In the inventive system, the DNP Bridge Server and the DNP Bridge Slave Interface work together to minimize the effects of the limited bandwidth availability and minimize the amount of data transferred over the slow portion of the network. Considering first the case where no time-outs are encountered: when a DNP message to be sent to the DNP Slave Device arrives at the DNP Bridge Server, the following steps are taken: the message is encoded into a smaller transmission format message; if necessary, the message is broken up into smaller network messages that match the underlying transport mechanism packet size; the message type being sent, its source and destination addresses and the state of the message sending process is saved; a timer is started to watch for the response to the transmission format message; and finally the message transmission process is started.  
         [0041]    When the DNP Bridge Slave Interface unit receives the entire message, the transmission format message is decoded into the original DNP message and sent to the DNP Slave device. The DNP Slave device then sends the DNP response message back to the DNP Slave Interface unit. When the DNP response is received, the DNP Bridge Slave Interface Unit builds a transmission format response message, and, if necessary, breaks the message up into smaller network messages that match the underlying transport mechanism size, and sends it back to the DNP Bridge Server. When the DNP Bridge Server receives the transmission format response message, it decodes the message into a DNP response message, sends the message back to the DNP Master System and clears its state and timer information of the message.  
         [0042]    If the DNP Master System times-out waiting for the response from the DNP Bridge Server, the DNP Master System will typically resend the DNP message. When the DNP Bridge Server receives the retransmission of the DNP message, it searches its saved DNP message state information, and when the match is found, it sends the retransmitted DNP message. This mechanism prevents “thrashing” of the low bandwidth portion of the network.  
         [0043]    If the DNP Bridge Server&#39;s timer expires for the transmission format message, the DNP Bridge Server deletes the message state information. This mechanism allows the DNP Master System&#39;s subsequent retries of the DNP message to pass through in the event that the transmission message transfer times-out.  
         [0044]    It is often desirable to be able to send a group of DNP Slave Devices a DNP control message simultaneously. Additionally, it would be desirable to minimize the amount of data sent over the bandwidth-cost-constrained portion of the DNP network. In the inventive system, when the bandwidth-cost-constrained portion of the DNP network uses technology in which all nodes “hear” all network traffic, a specially formatted “group broadcast command message” is employed. At initialization, a group address is programmed into the DNP Bridge Slave Interface unit. When the DNP Bridge Slave Interface unit “hears” a group or specially formatted message addressed to the group address, the DNP Bridge Slave Interface unit will respond to this message.  
         [0045]    By moving part or all of the DNP messages across public networks, the DNP network system becomes more vulnerable to attack. DNP Slave Devices often control equipment that is part of the public power grid. Unauthorized access to DNP Slave Devices could cripple the power network, affecting thousands of businesses and residences. Strong authentication between the DNP Master System and the DNP Slave Device is necessary to prevent such attacks. Encrypting messages between the DNP Master System and the DNP Slave Device may also be desirable in applications where knowledge of the DNP message contents may be helpful to an attacker or even a competitor.  
         [0046]    The inventive DNP network system consists of potentially several different network mediums with different bandwidth, reliability, and cost characteristics. Many different authentication and encryption technologies exist, each placing unique demands on the underlying network infrastructure. In the inventive system, authentication and encryption technologies are deployed to match the characteristics of the network transport and the associated risk of the transport. For example, in one embodiment, messages sent between systems in the DNP Network that are connected via high bandwidth, non-cost constrained networks may use an IPSEC VPN tunnel to communicate messages. IPSEC VPN tunnels can provide a very high level of authentication and encryption, but require a significant amount of bandwidth overhead. For messages sent over the slow, unreliable, bandwidth-cost-constrained portion of the DNP network, other authentication and encryption technologies may be needed. For example, in one embodiment, messages sent over the slow portion of the network use a time-synchronous sequence generator to authenticate the message sender.  
         [0047]    To minimize the time and costs associated with installation of the inventive network transport mechanisms in an existing DNP network, one embodiment of the present invention system provides interfaces to the DNP Master System and DNP Slave Device that are compatible with their existing network interfaces. DNP Master Systems are sometimes configured to communicate through a network terminal server to send messages through modems to the DNP Slave Devices. In one embodiment of the DNP Bridge Server, the present invention system emulates the network terminal server. The present invention system works with the existing DNP Master System by simply changing the address of the DNP Master System&#39;s network terminal server to the address of the DNP Bridge Server. Also, it should be noted that if the DNP Master System is connected to the DNP Bridge Server via the Internet, a single high capacity DNP Bridge Server may serve as the first bridging device for multiple separate networks at the same time and only be limited by its hardware capacity.  
         [0048]    DNP Slave Devices may be configured to communicate DNP network protocol directly over an RS-232 serial interface to an AT-compatible modem. In one embodiment of the DNP Bridge Slave Interface unit, the inventive system emulates an AT-compatible modem. The inventive system works with the existing DNP Slave Device directly.  
         [0049]    The present invention is not limited in scope to the DNP protocol, rather any data acquisition protocol, including but not limited to Modbus, GPIB, IEC 60870-5 and others. Modifications to the above description that include that which is known in the art are well within the scope of the contemplated invention. For example, multiple formats of incoming and outgoing messages are contemplated as included within the scope of the invention.  
         [0050]    While there is shown and described the present preferred embodiment of the invention, it is to be distinctly understood that this invention is not limited thereto but may be variously embodied to practice within the scope of the following claims. From the foregoing description, it will be apparent that various changes may be made without departing from the spirit and scope of the invention as defined by the following claims.