Apparatus and method for synchronization of control logic

Cross References to Related Application

0001This application claims priority to <patcit id="pcit0001" dnum="US61583956" dnum-type="L"><text>U.S. Provisional Application Serial Number 61/583,956, filed on January 6, 2012</text></patcit>. <ul id="ul0001" list-style="none" compact="compact"><li>PCT International application entitled "Method and Apparatus for Network Based Testing" naming as inventor Kenneth Dickie and having attorney docket number 256210;</li><li>PCT International application entitled "Apparatus and Method for Creating and Presenting Control Logic" naming as inventor Bernardo Anger and having attorney docket number 256211; and</li><li>PCT International application entitled "Apparatus and Method for Third Party Creation of Control Logic" naming as inventor Kenneth Dickie and having attorney docket number 256213;</li><li>are being filed on the same date as the present application.</li></ul>

Background of the Invention

Field of the Invention

0002The subject matter disclosed herein relates to the synchronization of control logic between various portions of a network-based system.

Brief Description of the Related Art

0003Automated devices perform various functions and these devices typically include a controller or control device that controls or manages the execution of these functions. For example, robotic controllers (e.g., those that utilize microprocessors) often control the functions of a robot and the robot can perform various manufacturing tasks. Assembly line controllers are used to control the various functions performed on or at an assembly line. A consumer device controller may be used to control the operation and functioning of any type of consumer device (e.g., a washer, dryer, dishwasher, building security system, building lighting system, building heating system, conveyer, boiler, extruder, pump, valve, control arm, or microwave oven). Together, these types of controllers provide automated functions and are generally referred to as automation controllers.

0004An automation controller typically includes and utilizes control logic to perform its functions. Control logic may include computer software and/or computer hardware that performs various predetermined functions. For example, an assembly line controller (e.g., for a bottling plant) may include a microprocessor that operates programmed computer software to regulate the speed and other functions associated with operating an assembly line that fills and caps the bottles. In another example, a controller may also include a microprocessor running programmed computer software that regulates various device parameters (e.g., temperature, pressure, or operating speed). In yet another example, a water system controller may include control logic that controls pumps and sprinklers.

0005Synchronization typically ensures that instances of the same parameters or code that are maintained at different system locations are identical. Conventional control logic systems do not maintain multiple versions of these items, so there is no need for synchronization between multiple versions of these items. <patcit id="pcit0002" dnum="US6449624B"><text>US6449624</text></patcit> teaches that is important to have good control of versions of updated software and the like. This is achieved using a version control routine which stores details of modifications. <patcit id="pcit0003" dnum="EP1742125A"><text>EP 1742125</text></patcit> teaches a method and apparatus for communicating transactions between an industrial controller and a programming interface. The industrial controller is able to pre-process a plurality of operations, designate the plurality of operations with a pending status, and then carry out the operations and clear the pending status responsive to receiving a commit transaction command.

Brief description of the Invention

0006Approaches are provided whereby synchronization is achieved between the control logic at an automation controller and a representation of this logic at a communication network. Control logic is initially deployed to an automation controller and a representation or model of this control logic is stored at the communication network. The automation controller is located remotely (i.e., is physically distinct and separated from) the network. A method of synchronizing control logic is according to annexed independent claim 1. A system of synchronizing control logic is according to annexed independent claim 10. Other advantageous features are defined in the method and system dependent claims.

0007When a change is made to the representation of the control logic at the network, the control logic is re-deployed to the automation controller so that the operation of the control logic at the automation controller is synchronized to the representation at the communication network. One technical effect is that the synchronization is effective to allow a service center to remotely service the control logic at the automation controller without the need to travel to the automation controller. The control logic may be any combination of hardware and/or software, and in some embodiments may utilize software library routines.

0008Settings at the automation controller can also be synchronized to their representations at the network. A technical effect of the synchronization of the settings, for example, allows for reliable testing of the control logic to be performed at the communication network since the settings at both locations are the same. In systems where settings are not used or are not critical, setting synchronization need not be performed.

0009In some aspects, the customer order is received via a graphical user interface. In other aspects, the customer order describes a plurality of control elements and interaction of selected ones of the plurality of control elements.

0010The automation controller may be a wide variety of devices. For instance, the automation controller may be a robot controller, an assembly line controller, or a consumer device controller. In other aspects, the automation controller may be an emulated controller or a physical controller. Other applications of controllers and implementations of controllers are possible.

Brief description of the Drawings

0011For a more complete understanding of the disclosure, reference should be made to the following detailed description and accompanying drawings wherein: <ul id="ul0002" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> comprises a block diagram of a communication network that synchronizes control logic according to various embodiments of the present invention;</li><li><figref idref="f0002">FIG. 2</figref> comprises a flow chart showing an approach for the synchronization of control logic according to various embodiments of the present invention;</li><li><figref idref="f0003">FIG. 3</figref> comprises a block diagram of a network controller according to various embodiments of the present invention; and</li><li><figref idref="f0004">FIG. 4</figref> comprises a block diagram of an automation controller according to various embodiments of the present invention.</li></ul>

0012Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required. It will also be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein.

Detailed Description of the Invention

0013Approaches are provided whereby the control logic at an automation controller is synchronized to a control logic representation stored at a communication network that is separate from and remotely located from the automation controller. The settings of the automation controller may also be synchronized to copies of the settings maintained at the communication network. By synchronizing these elements, reliable testing can be performed at the communication network since the multiple versions of these elements are identical. One of the benefits of the present approaches is that changes to the control logic can be reliably made since the multiple versions of these elements are identical. Other advantages will become apparent in view of the following discussion.

0014Referring now to <figref idref="f0001">FIG. 1</figref>, one example of a system for synchronizing multiple instances of control logic is described. A communication network 102 includes a memory unit 104, and a make changes module 106. The network 102 is coupled to a site 108 that includes an automation controller 110 (with settings 112) and interface 114. The site 108 may be any site where an automation controller can be deployed such as at a consumer device, at a factory, in an office, or at a communication device (e.g., base station) to mention a few examples.

0015The communication network 102 may be any type of communication network or combination of networks. For example, the communication network 102 may be the Internet, a cloud network, a telecommunication (e.g., cellular) network or any combination of these or other networks.

0016The memory unit 104 is any type of memory device or combination of memory devices. The memory unit 104 as well as the other elements of the communication network 102 may physically reside on any type of device or devices such as servers, access points, computers, interfaces of any type, or any other type of network element.

0017The memory unit 104 includes a library 116 with library elements or modules 118 and 120, a control logic representation 122, and copy of settings 124.

0018The control logic representation 122 is a description (in one example, implemented as programmed computer software or code) that represents the control logic at the automation controller 110. The control logic representation 122 describes the functions, workings, operation, inputs, outputs, and other characters of the operation of the associated automation controller 110.

0019The control logic representation 122 uses modules 118 and 120 from the library 116. In this respect, the modules 118 and 120 may be programmed software modules that perform specified functions. Although only two modules 118 and 120 are shown, it will be appreciated that any number of modules may be used. Further, it will be understood that different control logic representations may share modules.

0020As mentioned, the library 116 includes modules 118 and 120. Alternatively, a third party can create the entire control logic 122 (without the modules 118 and 120). In other aspects, a third party can create pieces of different types of logic (e.g., the same type of control logic for different automation controllers or different types of control logic for the same automation controller).

0021Automation controller 110 may be any device, combination of devices, or network of devices that are implemented in any combination of hardware or software. In one example, the automation controller 110 is an assembly line controller. In other examples, the automation controller is a controller for a pumping network (e.g., pumps, valves, pipes, sprinklers, and their associated controllers). Other examples of automation controllers and systems that utilize automation controllers are possible.

0022The interface 114 is any type of interface device that interacts with a human such as a personal computer, a laptop, a cellular telephone, or a personal digital assistant. Other examples of interfaces are possible. The interface 114 provides input and output functions as shown in the figure.

0023The make changes module 106 accepts a change request 132 to be made to the control logic representation 122. A service control center 134 may request a change to the control logic representation 122 or provide other service 130 to the control logic representation 122. In other aspects, the change request 132 may originate with other third parties or from the customer (e.g., entering the change via the interface 114). The change request 132 generally describes (via any appropriate software command or structure) the change requested to be made the control logic representation 122 (and hence to the control logic at the automation controller). The service 130 may, for example, involve monitoring the control logic representation 122.

0024Multiple versions of the control logic representation 122 may be maintained at the communication network 102. This may be advantageous in many situations where similar automation controller use different versions of the control logic. For example, a first pump of a first customer may use a first and original version of the control logic. For cost reasons, the owner of the first pump does not wish to utilize a second (and revised or improved) version of the control logic that includes new features. However, a second customer does desire to utilize the second version of the control logic in a second pump that the second customer owns. Representations of the first version of the control logic and the second version of the control logic are both maintained at the communication network 102. Thus, one technical effect is that both customers have access to the control logic they desire or require.

0025In one example of the operation of the system of <figref idref="f0001">FIG. 1</figref>, synchronization is achieved between control logic at an automation controller 110 and control logic representation 122 at a communication network. Control logic is initially deployed to the automation controller 110 and this control logic representation 122 is stored at the communication network 102. The automation controller 110 is located remotely (i.e., is not part of and/or is physically separated by a substantial distance from) the network 102.

0026When a change request 132 is sent to make a change to the control logic representation 122 at the network 102, the change is made and the control logic is re-deployed via update 127 to the automation controller 110 so that the operation of the control logic is synchronized to the control logic representation 122. The synchronization is effective to allow a service center 134 to engage in remote service 130 of the control logic without the need for traveling to the automation controller 110 in order to service the automation controller 110.

0027Settings 112 at the automation controller can also be synchronized to their representations at the network by sending a settings update 125 to the network 102. Settings may include various parameter values (e.g., pressures, temperatures, operating speeds) associated with the automation controller 110.

0028Referring now to <figref idref="f0002">FIG. 2</figref>, one example of an approach for achieving synchronized control logic is illustrated according to the present approaches. At step 202, control logic is initially deployed from the network controller to an automation controller. The deployment may be accomplished by a communication medium such as the Internet. At step 204 the control logic change is stored at the automation controller. The change may occur at any time after the control logic is initially deployed. At step 206, a representation (copy) of the control logic is sent to a memory at the communication network, and at step 208, the control logic representation is stored in memory at the communication network.

0029At step 210, a change request (requesting a change be made to the control logic) is transmitted by a third party and this change request 212 results in the creation of a changed version 214 of the control logic in the memory at the communication network. It will be appreciated that the original control logic representation may be overwritten or multiple versions of the control logic may be stored at the communication network. The later approach is particularly advantageous when similar automation controllers utilize different versions of the control logic so that all controllers have the control logic they require. In another approach, the original representation is always preserved and changes will be versioned.

0030At step 216, the control logic is re-deployed to the automation controller. At step 218, some control action is performed to the control logic representation stored at the communication network by a remote service center without the service center personnel having to travel to the actual site of the automation controller.

0031At step 222, a setting update reflecting settings 220 is sent from the automation controller to the network controller. At step 224, this is stored in memory at the communication network as settings 226.

0032At step 228, a test can be performed using updated settings and control logic. Since the instances of these elements at the automation controller and the communication network are identical, the test is reliable in that it will accurately reflect the operation of the control logic at the automation controller.

0033Referring now to <figref idref="f0003">FIG. 3</figref>, one example of a communication network controller 300 is described. The controller 300 includes a processor 302 and an interface 304. The processor 302 includes a receiver logic module 306, a receive changes module 308, a change module 310, a receive settings module 312, and a store settings module 314. The interface 304 is coupled to communication medium 307. Communication medium 307 is coupled to automation controller 320, third party 322 (e.g., a third party control logic provider), a memory 323, and a service center 324 (e.g., a service provider that services control logic).

0034The receive logic module 306 receives a representation of control logic for storage in the network at the memory 323. The receive changes module 306 receives changes from a third party 322 (via communication medium 307) and utilizes change module 310 to make changes to the control logic. The change module 310 performs all actions to implement the changes to the control logic (including creating a new version of the control logic).

0035The receive settings module 320 receives settings from automation controller 320 (via the communication medium 307) and the store settings module 314 stores these settings at the network (e.g., at a memory). Consequently, the same values for the settings are maintained at the automation controller 320 and the communication network. In systems where settings are not used or are not critical, setting synchronization need not be performed.

0036The service center 324, in one example, sends change requests to the controller 300. The changes are made to the control logic and the modified control logic is transmitted to the automation controller 320. Thus, synchronization of multiple instances of the control logic is maintained. In one aspect, a new (changed) version of the control logic is maintained and stored at the communication network while in others only a single version of the control logic is maintained.

0037The medium 307 may be any type of communication medium (hard wires, over the air, the Internet to mention a few examples). The interface 304 provides formatting and control functions between the processor 302 and the communication medium 307. The processor 302 is any processing device such as a microprocessor or the like. The controller 300 may be incorporated into or a part of any device such as an access point, server, base station, to mention a few examples.

0038Referring now to <figref idref="f0004">FIG. 4</figref>, one example of an automation controller 400 is described. The automation controller 400 includes an interface 402, one or more actuators 404, a processor 406, and a memory 408 (that includes control logic 410 and settings 412).

0039The interface 402 facilitates communications between the automation controller 400 and a communication network 414, and between the automation controller 400 and a local user interface 416. In this respect, the interface 402 includes hardware and/or software that interprets or translates commands and/or other information between the communication network 414 and the automation controller 400, and between the automation controller 400 and the local user interface 416.

0040The actuators 404 actuate physical or logical devices (e.g., the mechanical components of a valve or a sprinkler motor, to mention two examples). The function of the actuators 404 is to physically implement one or more of the functions associated with or provided by the controller 400.

0041The processor 406 is any programmed logic device such as a microprocessor or the like. Control logic 410 implements control functions that control actuators 404. Settings 412 are settings or other parameters (e.g., valve levels, pressures, temperatures, speeds) for the actuators 404.

0042Local user interface 416 may be a personal computer, cellular phone, or any other device that communicates with network 414 and/or controller 400. The communication network 414 is the location where the control logic 410 is built.

0043In one example of the operation of the system of <figref idref="f0004">FIG. 4</figref>, the control logic 410 at the automation controller 400 is synchronized with a representation of the control logic that is maintained at the communication network 414. The settings 412 at the automation controller 400 are also synchronized with a copy of the settings maintained at the communication network 414. In systems where settings are not used or are not critical, setting synchronization need not be performed.

0044Preferred embodiments of this invention are described herein, including the best mode known to the inventors for carrying out the invention. It should be understood that the illustrated embodiments are exemplary only, and should not be taken as limiting the scope of the invention.

0045As used herein, an element or function recited in the singular and proceeded with the word "a" or "an" should be understood as not excluding plural said elements or functions, unless such exclusion is explicitly recited. Furthermore, references to "one embodiment" of the claimed invention should not be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.

0046This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.

0047Although specific features of the invention are shown in some drawings and not in others, this is for convenience only as each feature may be combined with any or all of the other features in accordance with the invention. The words "including", "comprising", "having", and "with" as used herein are to be interpreted broadly and comprehensively and are not limited to any physical interconnection. Moreover, any embodiments disclosed in the subject application are not to be taken as the only possible embodiments. Other embodiments will occur to those skilled in the art and are within the scope of the following claims.