Patent Grant
8984533
- -
- -
The present invention relates to the integration of industrial automation systems having multiple domains such as control and enterprise domains and, and more particularly, to systems and methods for conducting or facilitating the conducting of communications among various components of such multidomain industrial automation systems.
Industrial automation systems include various enterprise software applications (which are also known as information technology (IT) or manufacturing software applications) for monitoring and/or managing different aspects of production, as well as various manufacturing (or automation) controllers which control the actual manufacturing processes. The enterprise software applications and manufacturing controllers can be considered to operate in two different domains of an industrial automation system, namely, an enterprise domain and a control domain, respectively.
Conventionally, communication between an enterprise software application and a controller (between the different domains) is problematic, due to different programming languages, different messaging protocols, and different execution environments that can exist. Current communication systems between these two domains rely on the use of customized code to enable communication in various forms. However, such systems for facilitating messaging or message exchange between these domains are often unpredictable, fault intolerant, and not performance scalable. Additionally, such systems struggle with trade-offs between overhead burden (such as memory footprint, CPU cycles, etc.) and application coupling. The message processing load is typically not optimally distributed across the system in accordance with system capabilities and, if one part of the system is shut down, alternative messaging routes are not always in place to allow production to continue.
Further, the design and installation of controllers in control systems of such industrial automation systems often require incremental changes to be applied to the controllers over time, and new controllers or interface screens to be added to a human machine interface (HMI). Such control systems can become unstable, screens can lock up, and data can be lost. Also, limited diagnostic functions of the communication system can make problems difficult to uncover. Solutions are then typically based on estimates established through limited system metrics. Additionally, communication system management during configuration and runtime is typically complex and difficult. The multiple messaging protocols in many systems complicate configuration and management of such systems. This can be aggravated when many different applications and controllers are involved. This complexity often hinders the system's capacity to provide reports on higher level system information and reduces the ability to easily configure such systems.
For at least these reasons, therefore, it would be advantageous if one or more improved systems or methods for conducting or facilitating the conducting of communications among various components of such multidomain industrial automation systems could be developed.
The present inventors have recognized that an improved communication system for an industrial automation system can overcome one or more of the disadvantages described above. The improved communication system in at least some embodiments allows communication in the form of messages between modules in different control or enterprise domains. Further, in at least some embodiments, such communications are achieved by providing a communication system including a manufacturing service bus having two internal service busses with a bridge between the internal busses. In at least some such embodiments, the manufacturing service bus is operable to define virtual channels between these modules. Also, in at least some embodiments, a predefined messaging framework is employed in which at least some of the modules have a common defined interface and/or employ standard instructions such as send (SEND) and receive (RECV) instructions. Further, in at least some embodiments, the communication system employs service oriented architecture (SOA) which relies on a common service description language employed by the modules, and/or an event driven architecture (EDA), wherein events and alarms in real time can be noted and acted upon.
In at least one embodiment, the present invention relates to a method of communicating between modules. The method includes sending a first message from a first module, where the first module includes a first data transport layer and a first application object layer, the first message originating at the first application object layer and being sent out of the first module via the first data transport layer. The method also includes receiving the first message at a second module, where the second module includes a second data transport layer and one or both of a transaction layer and a second application object layer, the first message being received via the second data transport layer. The sending and receiving are governed by ladder logic and are performed in a synchronous manner, and the first message is at least temporarily stored in a buffer after being received, prior to being acted upon by the ladder logic.
Embodiments of the invention are disclosed with reference to the accompanying drawings. The drawings are for illustrative purposes only. Thus, the invention is not limited in its application to the details of construction or the arrangement of the components illustrated in the drawings, but rather the invention is capable of other embodiments or of being practiced or carried out in other various manners. Like reference numerals are used to indicate like components. In the drawings:
More particularly with respect to the enterprise modules 18A-18E, these modules can include various applications, for example, manufacturing execution system (MES) applications and enterprise resource planning (ERP) applications. Specific examples of enterprise modules include a recipe procedure on an application server, an instance of an HMI screen (or other HMI module), an MES application such as RSScheduler, a data aggregation module at the area level running on an application server, or any of a variety of other applications or software modules. As for the control modules 20A-20D, these modules can include a variety of applications providing specific capabilities, for example, periodic or event-based execution models, access to controlled process input and output data, and pre-allocated resources. Although none of the control modules 20A-20D is shown to be, a human-machine interface (HMI) module, in at least some embodiments one or more control modules can be present that are HMI modules. Such HMI modules can run on an operator panel and can utilize an HMI development graphic language to provide graphical output.
The various modules 18A-18E and 20A-20D operate upon and are supported by operating system(s) running on various hardware device(s), as a result of which each module is able to execute and to provide desired functionality and behavior. The supporting operating system and hardware device corresponding to each of the modules 18A-18E and 20A-20D can be termed an execution framework for that module. Each respective execution framework for each respective one of the modules 18A-18E and 20A-20D can have standard capabilities, such as messaging and module lifecycle management, as well as specific capabilities unique to the execution framework type. Also, each execution framework type typically supports one or more different programming languages.
More particularly with respect to the enterprise modules 18A-18E, each of these can be run on a corresponding execution framework that includes a personal computer (PC) 22, as shown with respect to the enterprise modules 18A-18B, or another hosting device such as an enterprise server 24, as shown with respect to the enterprise modules 18C-18E. These execution frameworks can operate using various programming languages such as C, C++, Java, etc. As for the control modules 20A-20D (including other types of control modules such as HMI modules, which are not shown in
The particular numbers and arrangements of enterprise and control modules, their respective execution frameworks, and other components of the industrial automation system 10 can vary depending upon the embodiment. For example, while in the embodiment of
Physically, the various components of an industrial automation system such as the system 10 can be located at a variety of locations depending upon the embodiment. For example, the enterprise modules 18A-18E and control modules 20A-20D of the industrial automation system 10 and their respective execution frameworks can be located in various physical locations (and need not necessarily be located at the same location or plant). The communication system 12 and any of its component parts (e.g., the directory 14 or the MSB 16 or its component parts) can also be can be located in a variety of places, for example, in the chassis of an industrial controller such as one of the controllers 26A or 26B, on a PC such as PC 22, on an enterprise server such as the server 24, etc. Indeed, different parts of the communication system 12 can be found at different locations.
The communication system 12 enables communications between and among the various modules 18A-18E and 20A-20D. The communications can take a variety of forms and in the present embodiment include message exchanges of a variety of types. More particularly, the message exchanges can involve one or more of the sharing of data in one or more databases, the delivery of messages/information, and service invocations by which one or more of the modules invoke services of other(s) of the modules. Service invocations and responses in some embodiments can involve messages that are built from system libraries and that are sent and received via the communication system 12. The communication system 12 facilitates message exchange among the various modules 18A-18E and 20A-20D, regardless of their type, execution framework, or standalone messaging capabilities. The communication system 12 makes available to the modules 18A-18E and 20A-20D a set of messaging application programming interfaces (APIs) and a set of common design, configuration, deployment, runtime, and diagnostic tools, as described below. The communication system 12 (and particularly channels established thereby, as discussed in further detail below) also provides for both real-time messaging and scalability (important features for automation control modules), as well as service discovery, quality of service, security, message persistence, and message traceability functionality/features.
Further as shown in
More particularly, the ESB 30 provides a common integration platform that combines different communication standards/protocols and intelligent routing by which the MSB 16 can be reliably connected with the various enterprise modules 18A-18E. The ESB 30 operates to route messages to and from the enterprise modules 18A-18E, provide module and service discovery, provide a common service description language, provide bindings for different communication technologies, and provide security support, including authentication and authorization. With respect to the bindings that are provided, as shown in
By comparison, the ICB 28 in the present embodiment utilizes (e.g., is built on top of) the Common Industrial Protocol (CIP), which is a standard application level protocol for the manufacturing environment, and is used in a variety of networking technologies such as Ethernet/IP, DeviceNet, ControlNet, and others. While based upon the CIP, the ICB 28 also includes additional features in addition to those provided by the CIP, including supporting a common service description language in an open and reusable format, supporting event driven architecture, and providing dynamic service binding, as described in more detail below. Although not necessarily always in communications with the ESB 30, in the present embodiment the ICB 28 is capable of communicating with the ESB at least at some times by way of the bridge 32. As discussed in further detail below, the bridge 32 is capable of facilitating the establishment of one or more channels between one or more of the enterprise modules 18A-18E and one or more of the control modules 20A-20D via the ESB 30 and the ICB 28. The establishment of such channels is further made possible by the directory 14, which is in communication with one or more of the bridge 32, the ICB 28 and the ESB 30 and operates to publish service description documents respectively relating to the respective modules 18A-18E and 20A-20D. The bridge 32 in particular in some embodiments can be implemented in an industrial controller such as the controllers 26A, 26B supporting the control modules 20A-20D (or another chassis based module associated with one or more of the control modules) or an IT server such as the enterprise server 24.
Referring to
By comparison, as schematically illustrated in
Bridged messaging between modules in the enterprise and control domains is facilitated by several factors. Some of these, such as the use of a common interface (or interfaces) for the modules, and/or the use of common instructions by the control modules (e.g., the use of send (SEND) and receive (RECV) instructions), are described in further detail below. In at least some embodiments, the communication system 12 employs a service oriented architecture (SOA) which relies on a common service description language employed by the modules, and/or an event driven architecture (EDA), where events and alarms in real time can be noted and acted upon. With respect to the use of common service description documents (that is, documents using a common service description language such as a version of WSDL, e.g., WSDL 2.0), such documents describe available services of the modules. With respect to the system 10 of
More particularly, each service description document pertaining to a given module can include a listing of available services of that module, a module interface type including identification of interface elements of that module, a protocol used to communicate with that module and its interface, and a module address at which where services of that module can be accessed by other modules. Such service description documents can be generated or developed in various manners, including by users through the use of a set of development and configuration tools available for creating such documents. Upon receiving service description documents pertaining to the modules 18A-18E and 20A-20D of the system 10, the directory 14 renders those documents discoverable by all of the modules that are part of the system 10 and in contact with the MSB 16. In this manner, the services of each given one of the modules 18A-18E and 20A-20D become known (or can become known) and are available for use by others of those modules. More particularly, the directory 14 publishes the service description documents and thereby allows for the accessing of those documents via the MSB 16.
Although in some embodiments publication of the service description documents by the directory 14 can be automatic or periodic, in the present embodiment the publication of such documents by the directory occurs in response to search requests or inquiries made by the modules 18A-18E and 20A-20D to the directory. For example, the directory 14 can be or include a hierarchical structure of data descriptors and references that the modules can search and read. Assuming such a structure, the directory 14 allows the modules 18A-18E and 20A-20D to discover registered modules (e.g., to discover one another). In this regard, the directory receives search inquiries from inquiring modules in which various types of searching criteria are specified, such as a type of module interface or a location in an organizational hierarchy, and in response provides relevant service description documents pertaining to (and identifying) ones of the modules that satisfy the searching criteria, and/or related data descriptors or references or other information. In addition to such publishing and related search services, it should further be noted that the directory 14 is also able to provide other directory services such as advertising or location services.
As noted above, the bridge 32 between the ESB 30 and the ICB 28 operates to automatically provide channels between modules connected to different ones of the ESB and ICB as illustrated in
In at least some embodiments, the MSB 16 uses queues and topics to support message exchange among modules and can include a queuing mechanism to buffer requests and responses from multiple modules. More particularly, in such embodiments the MSB 16 defines a message (or event) producer as a module sending a message and a message (or event) consumer as a module receiving a message. Any given module can be a message producer, a message consumer, or both. Producers and consumers are not directly tied to each other, instead, they are connected to each other through channels (e.g., the channels 36A, 36B of
Referring to
Turning to
As for
As mentioned above, successful bridged messaging between modules in the enterprise and control domains is facilitated by the use of modules that share in common one or more defined interfaces. The use of shared, defined interfaces makes it possible to develop modules or applications that are able to access or be accessed by one another via the defined interface configuration. Referring now to
As further shown in
By comparison, a method provides functionality or a service that is implemented by module logic and accessible externally by other modules. Typically a method can be called by other modules, requires one or more input parameters to be provided for such calls to be successful and, assuming the calls are successful, in response generates one or more output parameters. A method call can be represented in the messaging infrastructure as a request message from a module carrying all the method input parameters. The called (or source) module sends back to the method calling (or requesting) module the method output parameters or error information if the method call was not successful. A queuing mechanism enabling the buffering of multiple requests and responses can also be provided. Additionally, for security purposes, users can configure method access rules or policies for each module similar to the attribute access policies described above. The MSB 16 is programmed to check the policies before allowing for the calling of a particular method and it allows access to the method only when the request complies with all policy settings.
As for events and alarms, these are occurrences that can be sent and received. More particularly, an event is an asynchronous occurrence that is detected by one module and can be distributed to one or more other modules. An alarm is a special version of an event typically representing some urgent or problematic situation that is detected and requires special attention, and has an associated state machine and can take on various states, such as being active or inactive or acknowledged or unacknowledged. Event and alarm types, which are predetermined sets of events and alarms, can be defined to allow specific modules to interact in a predefined manner. For example, if a manufacturing module publishes a standard “Material Consume” event, the material tracking software application module can consume and process the event without additional configuration. Custom event and alarm types can also be defined. Specific execution frameworks can also define system level events and alarms that are related to their functionality. For example, a Logix execution framework (that is, an execution framework involving/suitable for implementation on a Logix controller as available from Rockwell Automation of Milwaukee, Wis.) can define event and alarm types such as major faults, minor faults, mode changes, and new module deployed. In a similar manner, an application server execution framework can define event and alarm types such as new module deployed, and unhandled exception captured. Additionally, events and alarms can be grouped into categories. Typically, an event or alarm category can include multiple event types or alarm types. For example, a diagnostic event category can be defined that includes all the diagnostic events that a system generates. Each event and alarm can be associated with one or multiple categories. A system can include a predefined set of standard categories, or custom categories can also be defined.
Module developers can program modules to subscribe to one or more selected categories, one or more selected types, and/or one or more specifically selected events or alarms. Also, in some embodiments the MSB 16 is able to provide APIs to one or more of the modules (such as API 46 of
In general, the characteristics of the interface elements of a given module will vary depending upon the embodiment. Indeed, a module developer can take into account a variety of considerations in designing an interface for a given module including, for example, the expected functionality of a given module and/or the type of other (external) modules with which the given module is expected to interact. Based upon such considerations, the given module can be designed to include one or more of the aforementioned interface elements (or possibly others), and/or can be designed to include specific policies for interface access. Also, modules can be developed and deployed for different execution frameworks, such as a Logix controller framework, a .Net framework, or a Java framework. Although a module for any given execution framework will often entail methods, attributes, and events and alarms, each execution framework can use different terms and patterns for these interface elements, such as those in the following table:
In at least some embodiments, a given module (or modules) is developed and deployed for an execution framework in a manner that particularly allows other (remote) modules to read and write attribute values from and to that given module, and/or that allows for the given module to achieve periodic updating of attributes. In some such embodiments, the communication system 12 can periodically send values of all periodically-updated attributes to other corresponding modules consuming those attributes. The refresh frequency for periodically-updated attributes can be set by a module developer implementing the given module with an interface that supports periodically-updated attributes, or by a system integrator deploying the given module. To the extent that a given module uses (or consumes) periodically-updated attributes of another module, the given module does not need to access the other module, but rather is able to simply use the last value provided by the communication system 12, which amounts to synchronous communication from the point of view of the given (consuming) module. Periodically-updated attributes can have a data quality parameter, so a consuming module can appropriately handle a situation in which a consumed attribute has poor quality (e.g., when an attribute value has not been refreshed as expected).
Given a system in which each enterprise module and control module (such as the enterprise modules 18A-18E and control modules 20A-20D of
As shown in
More particularly with respect to
Numerous other types of message exchanges in addition to the exemplary scenarios shown in
As mentioned above, bridged messaging between modules in the enterprise and control domains is also facilitated by the use of common instructions by the control modules. In at least some embodiments, these common instructions can take the form of SEND (send) instructions that cause the sending of data to one or more target(s) (e.g., one or more other modules) and RECV (receive) instructions that cause the receiving of data from one or more source(s) (again, e.g., one or more other modules). The SEND instructions and RECV instructions typically are in the form of messages, including service invocations and responses, and can in some circumstances be generated by method calls as described above (which, as described above, involve input parameters and output parameters). Referring particularly to
To support messaging, particularly messaging involving SEND and RECV instructions, in the present embodiment at least some of the modules 20A-20D and 18A-18E (particularly the control modules 20A-20D) and at least some portions of the communication system 12 (particularly the bridge 32) have particular transaction or messaging architectures. Referring to
Typically, message exchanges involve a series of actions in which a message is sent by a source module, the message is received and processed by a target module, a response to the message is sent back to the source by the target, and the response is received by the source. In this manner, message exchanges typically are two-direction transactions rather than merely single-direction transactions in which data is merely provided from one module to another module.
Further as shown, the application object layers 81 are where, in each of the modules 90 and 91 respectively, there exists ladder logic programming for initiating SEND and RECV instructions. In the present example, although the same application object layer 81 is shown to be present in each of the modules 90, 91, this is meant to signify that the same type of application object layer is present in each module, but should not be interpreted as indicating that the exact ladder logic programming in each module is identical. Indeed, the ladder logic programming 92 of the source module 90 is shown to have SEND and RECV rungs that are opposite in order relative to those of the ladder logic programming 98 of the target module 91 and, depending upon the embodiment, the ladder logic programming of modules such as the modules 90, 91 can take a variety of other forms as well. As for the data transport layers 82 for each of the modules 90, 91, each of the data transport layers includes a respective transmit manager 93 and a respective receive manager 94. The transmit managers 93 and receive managers 94 establish and maintain connections between the modules 90, 91 via the communication system 12 and, more particularly (since in the present example both of the modules 90, 91 are control modules), via the ICB 28. The data transport layers 82 in particular are capable of addressing data fragmentation and performing reassembly of data if the data is longer than one CIP packet size. The connections established via the ICB 28 can take a variety of forms including, for example, Class 3 connections as shown.
The two-dimensional transactions occurring during the message exchange are illustrated in
The ladder logic programming 92, 98 in the source and target modules 90, 91 control the precise timing when the data should be captured for sending and when the data should be accepted by the receiver side. In the present embodiment, data being sent is captured when the SEND instruction is executed and received on the other side when the RECV instruction is executed, which makes the data transfer synchronous. Although the above description presumes that the signal returned via the second Class 3 connection 96 is a confirmation signal, this need not always be the case. Rather, in circumstances where the data transmitted from the source module 90 to the target module 91 is not properly communicated or received by the target module, the signal returned via the second Class 3 connection 96 can instead be indicative of a failure of the data communication, or of an abnormal operational state. The absence of the sending of a signal via the second Class 3 connection 96 following the sending of data via the first Class 3 connection 95 can also be interpreted by the source module 90 as indicative of a failure.
Although
Additionally, it will be understood that, as shown in
The above description with respect to
Turning to
As already noted, the MSB 16 includes the ICB 28, the bridge 32, and the ESB 30. The particular embodiment shown in
By virtue of the data transport layer 87 and the transaction layer 85 and also the CIP stack 116, the bridge 32 functions as a translator between the CIP network provided by the ICB 28 and the ESB 30 and thus facilitates messaging transactions between the control module 110 and the enterprise modules 111-113. The data transport layer 87 of the bridge 32, similar to the data transport layer 82 of the control module 110, has a receive manager 117 and a transmit manager 118. The receive manager 117 can be identical or similar in operation to the receive manager 94 of the data transport layer 82, while the transmit manager 118 can be identical or similar in operation to the transmit manager 93 of the data transport layer. Together with the transmit and receive managers 93, 94, the receive and transmit managers 117, 118 establish and maintain connections between the module 110 and the bridge 32 via the ICB 28 and the CIP stack 116. Further in the present embodiment, the bridge 32 uses one or both of XML based configuration files 99 and JAR files 119 to configure messages/message transactions (also, in some cases, WSDL-based files can be used for this purpose).
Notwithstanding the particular embodiment shown in
Turning to
Next at a step 134, the receive manager 117 of the data transport layer 87 on the bridge 32 receives the data associated with the message, reassembles the data to the extent it is arriving in multiple packets, and stores the data in a receive buffer (not shown) that is part of (or associated with) the receive manager (in an alternate embodiment, the received data is stored in packet form and is only reassembled after being stored). Upon receiving the data, the transmit manager 118 of the bridge 32 sends back an indication of the successful receipt of the data at a step 135. More particularly, a “success” response can be sent back from the transmit manager 118 on the bridge 32 to the receive manager 94 on the data transport layer 82 of the control module 110 for every valid received packet, so as to inform the control module about the successful packet delivery. Alternatively (or in addition), another “success” response can be sent back from the transmit manager 118 to the receive manager 94 when all packets are successfully received by the receive manager 117 on the bridge 32. The message(s) sent back from the bridge 32 to the control module 110 in this regard can be considered receive messages (reflective of RECV instructions being executed at the bridge) not unlike those already discussed above in relation to
Upon receiving these one or more “success” responses, the receive manager 94 of the data transport layer 82 sets the data delivery (.DD) status bit on the SEND backing tag indicating that the data has been successfully sent. Further, at a step 136, when all data from the control module 110 has been received by the bridge 32, the transaction layer 85 of the bridge 32 takes the data from the receive buffer and unpacks it. Further, at a step 137, the transaction is extracted and one of the adapters 120 is identified as being appropriate for allowing the transaction to proceed toward an intended one of the enterprise modules 111-113. In the present example, the intended recipient of the message is the ESB enterprise module 111, and consequently it is the WebService adapter 121 that is identified at the step 107. Next, at a step 138, the WebService adapter 121 identified at the step 107 is invoked such that the message is communicated via the ESB 30 to the intended recipient, which in this example is the ESB enterprise module 111 (the message communicated at this point can be considered to be the same as, or at least based upon, the original message received by the bridge 32 from the control module 110). Finally, at a step 139, when the ESB enterprise module 111 has finished the transaction, the transaction layer 85 notified. Although not shown, depending upon the embodiment, the above process can be modified or include additional aspects as well. For example, in one alternate embodiment, upon receiving a message at the bridge 32, the bridge performs each of a message queue (MQ) operation, a dispatch, and a method invocation, and then completes its operation in response to that message.
Further, at a step 145, the receive manager 82 on the control module 110 receives the data packets and stores them into a receive buffer (not shown). Additionally, at a step 146, the transmit manager 93 of the control module 110 sends one or more confirmation signals back to the bridge 32 confirming receipt of each packet. These signals can be sent upon receipt of each packet and/or when all data packets have been received. The bridge 32 then sets the data delivery (.DD) status bit for the transaction. Next, at a step 147, the ladder logic programming 92 of the application object layer 81 of the control module 110 invokes the RECV instruction. The RECV instruction takes the binary data from the send buffer, unpacks it, and places the data into corresponding receive tags. Finally, at a step 148, the control module 110 at this time additionally sends back (by way of the transmit manager 93) an additional signal to the bridge 32 at this moment indicating that the RECV instruction was executed. The bridge 32, upon receiving such information, in turn sets a data processed (.DP) status bit for the transaction, at which point the messaging transaction is complete.
In at least some embodiments, messaging transactions involving control module 110, MSB 16/bridge 32 and an enterprise module such as the module 111 can particularly make use of headers and/or queues, and/or can be described in other terms. For example, in some such embodiments, the receive manager 117 at the step 134 also decodes a message header associated with the message data that is received. If a reply queue name is included in the message header, the bridge device 32 then creates a consumer to be able to receive a service response. Also, in some such embodiments, if the receive manager 117/bridge device 32 detects a destination queue name at the step 134 from the message header, it then encodes the message header and sends a service message to a destination queue within the bridge. Ultimately, the service message can further then be received by a service framework (e.g., one of the enterprise modules 111-113) and, upon the receiving of the service message, the service framework causes an appropriate service to be invoked and further causes a response message to be sent to a response queue of the bridge. The bridge 32, upon receiving the response message from the response queue decodes a further message header of the response message to find an industrial protocol message path. The bridge 32 then ultimately encodes an additional message header to be sent back to the control-level module 110.
It should be understood from the discussion above that any arbitrary number of messaging transactions can be conducted in the above-described manner involving the control module 110, MSB 16/bridge 32, and enterprise modules 111-113, and that the transmit and receive managers 93, 94, 117, 118 of the data transport layers 82, 87 are particularly suited for processing numerous messages. Further, notwithstanding the exemplary messaging transactions shown in
Depending upon the embodiment, the industrial automation system 10 can be configured to operate in a variety of advantageous manners, particularly in view of the communication system 12 described above. Although it is the case that various enterprise modules such as the enterprise modules 18A-18E and 111-113 can generate messages at varying rates and generally require that the communication system 12 be able to carry messages at their rate of operation, various steps can be taken to guarantee or enhance quality of service. In particular, quality of service can be addressed by defining and tracking various quality of service parameters. These parameters can include bandwidth, the rate at which an application's traffic must be carried by the network; latency, the delay that an application can tolerate in delivering a packet of data; jitter, the variation in latency; and loss, the percentage of lost data. Indeed, the MSB 16 and execution frameworks can provide different delivery mechanisms with different quality of service parameters. Some execution frameworks can be limited to a preconfigured set of bindings having a preset quality of service, while other execution frameworks can choose configurable bindings with configurable quality of service parameters. The MSB 16 can be operated so as to guarantee that a requested quality of service parameter is provided for a channel between communicating modules even if the modules are deployed to different execution frameworks. User configurability of bindings is permitted as part of module configuration.
The MSB 16 also in at least some embodiments provides traceability and diagnostic tools so users can track and diagnose issues in the industrial control system. For example, to support traceability, the communication system 12 can include a logging mechanism with coordinated system time-stamping. A maintenance engineer can use various diagnostic tools to collect, correlate and combine message logs, such that a unified view of transferred messages can be displayed. Such diagnostic tools can provide a graphic display sequence of messages sent between sets of modules with precise time-stamping. The common service description allows users to decode message content and identify message exchange patterns in the entire system or a selected subsystem. Status information, such as number of messages sent, consumed, and/or forwarded can be collected. Because the integration of automation control and manufacturing software (enterprise) environments increases security concerns, the communication system 12 can include security features so that a module's access and/or a user's access to other modules or services can be restricted according to policies defined in the service description documents. Further, the MSB 16 includes the ability to check that messages come from an authenticated and authorized module. Data encryption of sensitive data can also be employed as required.
As already discussed above, the exact hardware implementations of the components of the industrial automation system 10 can vary considerably depending upon the embodiment. By comparison with the arrangement discussed above and shown in
Notwithstanding the embodiments discussed above, the present invention can encompass a variety of other configurations of industrial automation systems as well. Referring to
By virtue of the respective bindings 27A, 27B, 27D, and 27E, the alternative bridge 162 allows for communications to occur between the ICB 28 and the respective control modules 18A, 18B-18C, 18D, and 18E as represented by arrows 168A, 16B, 168D, and 168E (the binding 27F would allow for further communications between one or more other enterprise module(s) if the they were present as hosted by the enterprise server 24, as indicated by a further arrow 168F). The directory 14 further facilitates the communications between the ICB 28 and the alternative bridge 162. Because the alternative bridge 162 does not require all of the same components as the bridge 16, and in particular does not employ the ESB 30, the alternative bridge 162 is simpler than the bridge 16 and yet still can provide functionality that is similar to or even the same as that provided using the bridge 16 with the ESB 30, particularly in terms of allowing for communications to occur between the control modules and enterprise modules (and especially between each of the enterprise modules and any one or more of the control modules). Thus, the alternative bridge 162 ties together the control system and the enterprise system directly, without the need for the ESB 30.
The industrial automation system 10 described above including the communication system 12 and associated modules can be advantageous on numerous counts depending upon the embodiment. In particular, in at least some embodiments, the communication system 12 offers a controlled manner of interaction among various software applications, and allows for reliable, secure communications between software applications (provided in modules) to be achieved, regardless of system (or module) age, platform type, operating system, or implementation language. The use of the communication system 12 also allows for a reduction in the complexity of messaging within an industrial manufacturing system, and allows for the addition of new modules or modification of modules. The use of modules itself provides a consistent method for integrating legacy applications and control systems through the use of standard libraries of messaging definitions. The modular approach also provides an efficient system that is simple, reliable, and secure, has built in diagnostics, and comes with selectable levels of service in reusable “packages”. Although discussed in the context of industrial automation, the present invention is also intended to encompass and apply to other types automation/computer systems that are outside of the industrial automation field as well.
It is specifically intended that the present invention not be limited to the embodiments and illustrations contained herein, but include modified forms of those embodiments including portions of the embodiments and combinations of elements of different embodiments as come within the scope of the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4268901 | Subrizi et al. | May 1981 | A |
| 4347564 | Sugano et al. | Aug 1982 | A |
| 4623964 | Getz et al. | Nov 1986 | A |
| 4990838 | Kawato et al. | Feb 1991 | A |
| 5072374 | Sexton et al. | Dec 1991 | A |
| 5185708 | Hall et al. | Feb 1993 | A |
| 5253184 | Kleinschnitz | Oct 1993 | A |
| 5282244 | Fuller et al. | Jan 1994 | A |
| 5301320 | McAtee et al. | Apr 1994 | A |
| 5446868 | Gardea, II et al. | Aug 1995 | A |
| 5455775 | Huber et al. | Oct 1995 | A |
| 5485620 | Sadre et al. | Jan 1996 | A |
| 5504891 | Motoyama et al. | Apr 1996 | A |
| 5524253 | Pham et al. | Jun 1996 | A |
| 5537585 | Blickenstaff et al. | Jul 1996 | A |
| 5572731 | Morel et al. | Nov 1996 | A |
| 5611059 | Benton et al. | Mar 1997 | A |
| 5619724 | Moore | Apr 1997 | A |
| 5634048 | Ryu et al. | May 1997 | A |
| 5644740 | Kiuchi | Jul 1997 | A |
| 5675748 | Ross | Oct 1997 | A |
| 5699520 | Hodgson et al. | Dec 1997 | A |
| 5715413 | Ishai et al. | Feb 1998 | A |
| 5721905 | Elixmann et al. | Feb 1998 | A |
| 5761499 | Sonderegger | Jun 1998 | A |
| 5790935 | Payton | Aug 1998 | A |
| 5797137 | Golshani et al. | Aug 1998 | A |
| 5812394 | Lewis et al. | Sep 1998 | A |
| 5812773 | Norin | Sep 1998 | A |
| 5828851 | Nixon et al. | Oct 1998 | A |
| 5832486 | Itoh et al. | Nov 1998 | A |
| 5838563 | Dove et al. | Nov 1998 | A |
| 5848273 | Fontana et al. | Dec 1998 | A |
| 5862052 | Nixon et al. | Jan 1999 | A |
| 5884025 | Baehr et al. | Mar 1999 | A |
| 5884033 | Duvall et al. | Mar 1999 | A |
| 5913029 | Shostak | Jun 1999 | A |
| 5924094 | Sutter | Jul 1999 | A |
| 5936539 | Fuchs | Aug 1999 | A |
| 5940294 | Dove | Aug 1999 | A |
| 5940854 | Green, Jr. et al. | Aug 1999 | A |
| 5951440 | Reichlinger | Sep 1999 | A |
| 5960420 | Leymann et al. | Sep 1999 | A |
| 5966705 | Koneru et al. | Oct 1999 | A |
| 5970494 | Velissaropoulos et al. | Oct 1999 | A |
| 5978577 | Rierden et al. | Nov 1999 | A |
| 5980078 | Krivoshein et al. | Nov 1999 | A |
| 5983016 | Brodsky et al. | Nov 1999 | A |
| 6011899 | Ohishi et al. | Jan 2000 | A |
| 6032208 | Nixon et al. | Feb 2000 | A |
| 6044217 | Brealey et al. | Mar 2000 | A |
| 6061740 | Ferguson et al. | May 2000 | A |
| 6063129 | Dadd et al. | May 2000 | A |
| 6081899 | Byrd | Jun 2000 | A |
| 6098116 | Nixon et al. | Aug 2000 | A |
| 6101531 | Eggleston et al. | Aug 2000 | A |
| 6195591 | Nixon et al. | Feb 2001 | B1 |
| 6208987 | Nihei | Mar 2001 | B1 |
| 6234899 | Nulph | May 2001 | B1 |
| 6266726 | Nixon et al. | Jul 2001 | B1 |
| 6275977 | Nagai et al. | Aug 2001 | B1 |
| 6308168 | Dovich et al. | Oct 2001 | B1 |
| 6308224 | Leymann et al. | Oct 2001 | B1 |
| 6311187 | Jeyaraman | Oct 2001 | B1 |
| 6321337 | Reshef et al. | Nov 2001 | B1 |
| 6327511 | Naismith et al. | Dec 2001 | B1 |
| 6336152 | Richman et al. | Jan 2002 | B1 |
| 6356920 | Vandersluis | Mar 2002 | B1 |
| 6377957 | Jeyaraman | Apr 2002 | B1 |
| 6393566 | Levine | May 2002 | B1 |
| 6398106 | Ulvr et al. | Jun 2002 | B1 |
| 6409082 | Davis et al. | Jun 2002 | B1 |
| 6411987 | Steger et al. | Jun 2002 | B1 |
| 6415983 | Ulvr et al. | Jul 2002 | B1 |
| 6421743 | Byron et al. | Jul 2002 | B1 |
| 6425051 | Burton et al. | Jul 2002 | B1 |
| 6438744 | Toutonghi et al. | Aug 2002 | B2 |
| 6445963 | Blevins et al. | Sep 2002 | B1 |
| 6446202 | Krivoshein et al. | Sep 2002 | B1 |
| 6457053 | Satagopan et al. | Sep 2002 | B1 |
| 6469986 | Lecheler et al. | Oct 2002 | B1 |
| 6473656 | Langels et al. | Oct 2002 | B1 |
| 6477435 | Ryan et al. | Nov 2002 | B1 |
| 6484061 | Papadopoulos et al. | Nov 2002 | B2 |
| 6501996 | Bieber | Dec 2002 | B1 |
| 6505247 | Steger et al. | Jan 2003 | B1 |
| 6510352 | Badavas et al. | Jan 2003 | B1 |
| 6539271 | Lech et al. | Mar 2003 | B2 |
| 6539430 | Humes | Mar 2003 | B1 |
| 6539458 | Holmberg | Mar 2003 | B2 |
| 6615091 | Birchenough et al. | Sep 2003 | B1 |
| 6631519 | Nicholson et al. | Oct 2003 | B1 |
| 6643555 | Eller et al. | Nov 2003 | B1 |
| 6661426 | Jetha et al. | Dec 2003 | B1 |
| 6664981 | Ashe et al. | Dec 2003 | B2 |
| 6681227 | Kojima et al. | Jan 2004 | B1 |
| 6687817 | Paul | Feb 2004 | B1 |
| 6697797 | Hoggatt et al. | Feb 2004 | B1 |
| 6704746 | Sokolov et al. | Mar 2004 | B2 |
| 6714949 | Frey, Jr. | Mar 2004 | B1 |
| 6714981 | Skaggs et al. | Mar 2004 | B1 |
| 6738821 | Wilson et al. | May 2004 | B1 |
| 6745089 | Rasmussen et al. | Jun 2004 | B2 |
| 6748486 | Burton et al. | Jun 2004 | B2 |
| 6751634 | Judd | Jun 2004 | B1 |
| 6758403 | Keys et al. | Jul 2004 | B1 |
| 6760721 | Chasen et al. | Jul 2004 | B1 |
| 6760732 | Busshart et al. | Jul 2004 | B2 |
| 6763395 | Austin | Jul 2004 | B1 |
| 6766312 | Landt | Jul 2004 | B2 |
| 6768987 | Couch et al. | Jul 2004 | B1 |
| 6769095 | Brassard et al. | Jul 2004 | B1 |
| 6778537 | Ishibashi | Aug 2004 | B1 |
| 6801822 | Fujiwara et al. | Oct 2004 | B1 |
| 6807632 | Carpentier et al. | Oct 2004 | B1 |
| 6809732 | Zatz et al. | Oct 2004 | B2 |
| 6832120 | Frank et al. | Dec 2004 | B1 |
| 6836892 | Ikoma et al. | Dec 2004 | B2 |
| 6839790 | Barros De Almeida et al. | Jan 2005 | B2 |
| 6842769 | Kim et al. | Jan 2005 | B1 |
| 6853920 | Hsiung et al. | Feb 2005 | B2 |
| 6865509 | Hsiung et al. | Mar 2005 | B1 |
| 6868413 | Grindrod et al. | Mar 2005 | B1 |
| 6868538 | Nixon et al. | Mar 2005 | B1 |
| 6874145 | Ye et al. | Mar 2005 | B1 |
| 6874146 | Iyengar | Mar 2005 | B1 |
| 6880060 | Talagala et al. | Apr 2005 | B2 |
| 6889282 | Schollenberger | May 2005 | B2 |
| 6901578 | Beaven et al. | May 2005 | B1 |
| 6904473 | Bloxham et al. | Jun 2005 | B1 |
| 6920474 | Walsh et al. | Jul 2005 | B2 |
| 6928521 | Burton et al. | Aug 2005 | B1 |
| 6930985 | Rathi et al. | Aug 2005 | B1 |
| 6934749 | Black et al. | Aug 2005 | B1 |
| 6938079 | Anderson et al. | Aug 2005 | B1 |
| 6944626 | Cameron et al. | Sep 2005 | B2 |
| 6947947 | Block et al. | Sep 2005 | B2 |
| 6950900 | McKean et al. | Sep 2005 | B1 |
| 6952727 | Lindner et al. | Oct 2005 | B1 |
| 6954770 | Carlson et al. | Oct 2005 | B1 |
| 6961728 | Wynblatt et al. | Nov 2005 | B2 |
| 6973556 | Milligan et al. | Dec 2005 | B2 |
| 6975913 | Kreidler et al. | Dec 2005 | B2 |
| 7043311 | Nixon et al. | May 2006 | B2 |
| 7089530 | Dardinski et al. | Aug 2006 | B1 |
| 7096465 | Dardinski et al. | Aug 2006 | B1 |
| 7146355 | Chu-Carroll | Dec 2006 | B2 |
| 7162312 | Gross et al. | Jan 2007 | B2 |
| 7171476 | Maeda et al. | Jan 2007 | B2 |
| 7225193 | Mets et al. | May 2007 | B2 |
| 7251222 | Chen et al. | Jul 2007 | B2 |
| 7308454 | Abineri et al. | Dec 2007 | B2 |
| 7483994 | Stephens et al. | Jan 2009 | B1 |
| 7664869 | Baker et al. | Feb 2010 | B2 |
| 7672737 | Hood et al. | Mar 2010 | B2 |
| 7835894 | Kwon | Nov 2010 | B2 |
| 7912945 | Little | Mar 2011 | B2 |
| 8086758 | Allan et al. | Dec 2011 | B1 |
| 8180402 | Dewey et al. | May 2012 | B2 |
| 8266308 | Rydberg et al. | Sep 2012 | B2 |
| 20020007286 | Okamoto | Jan 2002 | A1 |
| 20020012401 | Karolys et al. | Jan 2002 | A1 |
| 20020013748 | Edmison et al. | Jan 2002 | A1 |
| 20020069167 | Conlow | Jun 2002 | A1 |
| 20020073236 | Helgeson et al. | Jun 2002 | A1 |
| 20020087786 | Burton et al. | Jul 2002 | A1 |
| 20020091838 | Rupp et al. | Jul 2002 | A1 |
| 20020103785 | Harvey | Aug 2002 | A1 |
| 20020116453 | Todorov et al. | Aug 2002 | A1 |
| 20020131404 | Mehta et al. | Sep 2002 | A1 |
| 20020161827 | Brault | Oct 2002 | A1 |
| 20020173984 | Robertson et al. | Nov 2002 | A1 |
| 20020188366 | Pepper et al. | Dec 2002 | A1 |
| 20020194577 | Connor et al. | Dec 2002 | A1 |
| 20030014387 | Kreidler et al. | Jan 2003 | A1 |
| 20030036876 | Fuller, III et al. | Feb 2003 | A1 |
| 20030065673 | Grobler et al. | Apr 2003 | A1 |
| 20030090514 | Cole et al. | May 2003 | A1 |
| 20030093471 | Upton | May 2003 | A1 |
| 20030120710 | Pulsipher et al. | Jun 2003 | A1 |
| 20030123467 | Du et al. | Jul 2003 | A1 |
| 20030126308 | Kim | Jul 2003 | A1 |
| 20030172145 | Nguyen | Sep 2003 | A1 |
| 20030177114 | Lin et al. | Sep 2003 | A1 |
| 20030212828 | Miyazaki et al. | Nov 2003 | A1 |
| 20030218641 | Longobardi | Nov 2003 | A1 |
| 20040006401 | Yamada et al. | Jan 2004 | A1 |
| 20040024995 | Swaine | Feb 2004 | A1 |
| 20040044421 | Brune et al. | Mar 2004 | A1 |
| 20040073565 | Kaufman et al. | Apr 2004 | A1 |
| 20040098153 | Neudeck | May 2004 | A1 |
| 20040098269 | Wise et al. | May 2004 | A1 |
| 20040117624 | Brandt et al. | Jun 2004 | A1 |
| 20040153171 | Brandt et al. | Aug 2004 | A1 |
| 20040158842 | Gilfix et al. | Aug 2004 | A1 |
| 20040167790 | Grasse | Aug 2004 | A1 |
| 20040193449 | Wildman et al. | Sep 2004 | A1 |
| 20040196855 | Davies et al. | Oct 2004 | A1 |
| 20040199655 | Davies et al. | Oct 2004 | A1 |
| 20040203620 | Thome et al. | Oct 2004 | A1 |
| 20040210629 | Klindt et al. | Oct 2004 | A1 |
| 20040249771 | Berg et al. | Dec 2004 | A1 |
| 20040260591 | King | Dec 2004 | A1 |
| 20040268186 | Maturana et al. | Dec 2004 | A1 |
| 20050005289 | Adolph et al. | Jan 2005 | A1 |
| 20050015397 | Abineri et al. | Jan 2005 | A1 |
| 20050044112 | Yamamoto et al. | Feb 2005 | A1 |
| 20050065626 | Kappelhoff et al. | Mar 2005 | A1 |
| 20050065829 | Birkhoelzer | Mar 2005 | A1 |
| 20050065971 | Honda | Mar 2005 | A1 |
| 20050069853 | Tyson et al. | Mar 2005 | A1 |
| 20050091349 | Scheibli | Apr 2005 | A1 |
| 20050102672 | Brothers | May 2005 | A1 |
| 20050107897 | Callaghan | May 2005 | A1 |
| 20050108247 | Heinla et al. | May 2005 | A1 |
| 20050120021 | Tang et al. | Jun 2005 | A1 |
| 20050129247 | Gammel et al. | Jun 2005 | A1 |
| 20050135782 | Ando et al. | Jun 2005 | A1 |
| 20050154741 | Hebert et al. | Jul 2005 | A1 |
| 20050166215 | Holloway et al. | Jul 2005 | A1 |
| 20050177687 | Rao | Aug 2005 | A1 |
| 20050187925 | Schechinger et al. | Aug 2005 | A1 |
| 20050193118 | Le et al. | Sep 2005 | A1 |
| 20050198248 | Morimoto et al. | Sep 2005 | A1 |
| 20050216460 | Yoon et al. | Sep 2005 | A1 |
| 20050223010 | Murray | Oct 2005 | A1 |
| 20050251527 | Phillips et al. | Nov 2005 | A1 |
| 20050256788 | Mukai | Nov 2005 | A1 |
| 20050267952 | Ricciardi et al. | Dec 2005 | A1 |
| 20050268253 | Johnson et al. | Dec 2005 | A1 |
| 20050278373 | Corbett et al. | Dec 2005 | A1 |
| 20060004475 | Brackett et al. | Jan 2006 | A1 |
| 20060004847 | Claudatos et al. | Jan 2006 | A1 |
| 20060064428 | Colaco et al. | Mar 2006 | A1 |
| 20060067209 | Sheehan et al. | Mar 2006 | A1 |
| 20060074498 | Kalan et al. | Apr 2006 | A1 |
| 20060173895 | Engquist et al. | Aug 2006 | A1 |
| 20060195817 | Moon | Aug 2006 | A1 |
| 20060212855 | Bournas et al. | Sep 2006 | A1 |
| 20060230130 | Cho et al. | Oct 2006 | A1 |
| 20060259160 | Hood et al. | Nov 2006 | A1 |
| 20070067497 | Craft et al. | Mar 2007 | A1 |
| 20070079028 | Hall | Apr 2007 | A1 |
| 20070186011 | Batke et al. | Aug 2007 | A1 |
| 20070226318 | Rydberg et al. | Sep 2007 | A1 |
| 20070268922 | Dougan et al. | Nov 2007 | A1 |
| 20080028068 | Nochta et al. | Jan 2008 | A1 |
| 20080140759 | Conner et al. | Jun 2008 | A1 |
| 20080189636 | Hood et al. | Aug 2008 | A1 |
| 20100172372 | Sichner et al. | Jul 2010 | A1 |
| 20110258262 | Bezdicek et al. | Oct 2011 | A1 |
| 20110258359 | Bezdicek et al. | Oct 2011 | A1 |
| 20120041572 | Halsall | Feb 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 200 16 625 | Dec 2000 | DE |
| 1 696 376 | Aug 2006 | EP |
| 1746799 | Jan 2007 | EP |
| 1906623 | Apr 2008 | EP |
| 2006021052 | Mar 2006 | WO |
| Entry |
|---|
| Michael Young et al “The Duality of Memory and Communication in the Implementation of a Multiprocessor Operating System”; 1987. |
| European Search Report; EP Application No. 11162627.1; Sep. 1, 2011; 8 pages. |
| European Search Report; EP Application No. 11162628.9; Aug. 31, 2011; 9 pages. |
| European Extended Search Report; EP Application No. 11162623.0; Oct. 19, 2011; 5 pages. |
| Machado, G.B. et al; “Integration of Embedded Devices Through Web Services: Requirements, Challenges and Early Results”; Computers and Communications; 11th IEEE Symposium on Cagliari Italy; Jun. 2006; pp. 353-358. |
| European Search Report relating to Application No. EP 07 11 7361, date of completion of the search Jan. 30, 2008 (1 pg.). |
| Extended European Search Report relating to Application No. EP 07 117409, date of completion of the search Jan. 24, 2008 (8 pgs.). |
| Extended European Search Report relating to Application No. EP 05 01 6793, date of completion of the search Nov. 28, 2005 (3 pgs.). |
| PCT International Search Report and Written Opinion of the International Search Authority, relating to International Application No. PCT/US06/18180, date of mailing of the International Search Report Jul. 7, 2008 (1 pg.), date of completion of Opinion Jun. 10, 2008 (4 pgs.), (5 pgs.). |
| WO 2006/124471 A3, International Search Report and PCT Written Opinion of the International Searching Authority, relating to International Application No. PCT/US06/18122, date of mailing of the International Search Report May 6, 2008 (1 pg.), date of completion of Opinion Apr. 15, 2008 (8 pgs.), (10 total pgs.). |
| WO 2006/124488 A3, International Search Report and PCT Written Opinion of the International Searching Authority, relating to International Application No. PCT/US06/18181, date of mailing of the International Search Report Mar. 4, 2008 (2 pgs.), date of completion of Opinion Feb. 12, 2008 (9 pgs.), (13 total pgs.). |
| WO 2006/124513 A3, International Search Report and PCT Written Opinion of the International Searching Authority, relating to International Application No. PCT/US06/18238, date of mailing of the International Search Report Jan. 24, 2008 (1 pg.), date of completion of Opinion Jan. 11, 2008 (5 pgs.), (7 total pgs.). |
| WO 2006/124547 A3, International Search Report and PCT Written Opinion of the International Searching Authority, relating to International Application No. PCT/US06/18350, date of mailing of the International Search Report Jun. 19, 2008 (2 pgs.), date of completion of Opinion May 14, 2008 (5 pgs.), (9 total pgs.). |
| U.S. Appl. No. 11/238,537, Non-final Office Action, dated Apr. 22, 2008 (48 pgs.). |
| U.S. Appl. No. 11/238,537, Non-final Office Action, dated Oct. 20, 2008 (44 pgs.). |
| U.S. Appl. No. 11/238,537, Non-final Office Action, dated Apr. 15, 2009 (22 pgs.). |
| U.S. Appl. No. 11/238,606, Non-final Office Action, dated Jan. 18, 2008 (23 pgs.). |
| U.S. Appl. No. 11/238,606, Final Office Action, dated Jul. 2, 2008 (17 pgs.). |
| U.S. Appl. No. 11/238,606, Non-final Office Action, dated Nov. 20, 2008 (19 pgs.). |
| U.S. Appl. No. 11/238,606, Final Office Action, dated Jun. 3, 2009 (24 pgs.). |
| U.S. Appl. No. 11/238,607, Non-final Office Action, dated Apr. 2, 2008 (37 pgs.). |
| U.S. Appl. No. 11/238,607, Final Office Action, dated Oct. 8, 2008 (32 pgs.). |
| U.S. Appl. No. 11/238,607, Non-final Office Action, dated Mar. 6, 2009 (61 pgs.). |
| U.S. Appl. No. 11/239,567, Non-final Office Action, dated Nov. 2, 2007 (39 pgs.). |
| U.S. Appl. No. 11/239,567, Final Office Action, dated May 30, 2008 (29 pgs.). |
| U.S. Appl. No. 11/239,567, Non-final Office Action, dated Nov. 14, 2008 (34 pgs.). |
| U.S. Appl. No. 11/239,567, Final Office Action, dated May 1, 2009 (35 pgs.). |
| U.S. Appl. No. 11/240,335, Non-final Office Action, dated May 15, 2008 (31 pgs.). |
| U.S. Appl. No. 11/536,338, entitled “Distributed Message Engines and Systems”, filed Sep. 28, 2006 (49 pgs.). |
| U.S. Appl. No. 11/536,395, entitled “Message Engine”, filed Sep. 28, 2006 (48 pgs.). |
| U.S. Appl. No. 11/536,269, entitled “Messaging Configuration System”, filed Sep. 28, 2006 (48 pgs.). |
| U.S. Appl. No. 11/536,411, entitled “Message Engine Searching and Classification”, filed Sep. 28, 2006 (51 pgs.). |
| Cheah R. S-S et al., “Implementing Manufacturing Message Specification Services and Protocol Using ISO Development Environment”, IEEE Tencon, Bejing, China, 1993 (pp. 553-556). |
| Goldman R. et al., “From Semistructured Data to XML: Migrating the Lore Data Model and Querly Language”, In: ACM SIGMOD Workshop on The Web and Databases (WebDB 1999), Philadelphia, PA, Jun. 3-4 (pp. 1-7). |
| Kubiatowicz J. et al., “OceanStore: An Architecture for Global-Scale Persistent Storage”, ASPLOS 2000, Cambridge, Massachusetts, USA, Nov. 2000 (pp. 1-12). |
| Ozsoyoglu et al., “Database Systems for Programmable Logic Controllers”, Statistical and Scientific Database Management, Lecture Notes in Computer Science, vol. 420, 1990 (pp. 183-199). |
| Pitzek, S. et al., “Configuration and Management of a Real-Time Smart Transducer Network”, IEEE, 2003 (pp. 1-10). |
| Tanenbaum A.S., “Computer Networks”, Pearson Education, US, XP-002466380, 2003 (pp. VII-XVII and pp. 869-901). |
| Tanenbaum A.S., “Structured Computer Organization”, Prentice-Hall, U.S., XP-002466381, 1999 (pp. VII-XV and pp. 653-669). |
| U.S. Appl. No. 12/761,243; Non-Final Office Action; Mar. 21, 2012; 7 pages. |
| U.S. Appl. No. 12/761,237; Non-Final Office Action; Jun. 26, 2012; 8 pages. |
| European Patent Application No. 11 162 627.1; Response to Office Communication; Mar. 13, 2013; 10 pages. |
| European Patent Application No. 11162627.1; Office Communication; Oct. 5, 2012; 5 pages. |
| U.S. Appl. No. 12/761,237; Final Office Action; Jan. 10, 2013; 10 pages. |
| U.S. offcice action for U.S. Appl. No. 12/761,237, dated Sep. 18, 2014, 10 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20110258637 A1 | Oct 2011 | US |
