The subject matter disclosed herein relates to the synchronization of control logic between various portions of a network-based system.
Automated 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.
An 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.
Synchronization 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.
Approaches 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.
When 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.
Settings 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.
In 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.
The 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.
For a more complete understanding of the disclosure, reference should be made to the following detailed description and accompanying drawings wherein:
Skilled 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.
Approaches 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.
Referring now to
The 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.
The 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.
The 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.
The 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.
The 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.
As 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).
Automation 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.
The 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.
The 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.
Multiple 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.
In one example of the operation of the system of
When 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.
Settings 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.
Referring now to
At 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.
At 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.
At 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.
At 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.
Referring now to
The 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).
The 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.
The 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.
The 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.
Referring now to
The 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.
The 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.
The 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.
Local 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.
In one example of the operation of the system of
Preferred 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.
As 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.
This 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.
Although 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.
This application claims priority to U.S. Provisional Application Ser. No. 61/583,956, filed on Jan. 6, 2012, the contents of which are incorporated herein by reference in its entirety. PCT International application No. PCT/US2012/044766, entitled “Method and Apparatus for Network Based Testing” and published as WO/2013/103381; PCT International application No. PCT/US2012/044767, entitled “Apparatus and Method for Creating and Presenting Control Logic” and published as WO/2013/103382; and PCT International application No. PCT/US2012/044770, entitled “Apparatus and Method for Third Party Creation of Control Logic” and published as WO/2013/103383; are being filed on the same date as the present application, the contents of which are incorporated herein by reference in their entireties.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US2012/044759 | 6/29/2012 | WO | 00 | 12/3/2014 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2013/103380 | 7/11/2013 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
5530643 | Hodorowski | Jun 1996 | A |
5870537 | Kern et al. | Feb 1999 | A |
6353926 | Parthesarathy et al. | Mar 2002 | B1 |
6445963 | Blevins et al. | Sep 2002 | B1 |
6449624 | Hammack | Sep 2002 | B1 |
6567937 | Flores et al. | May 2003 | B1 |
6704735 | Salo et al. | Mar 2004 | B1 |
6799080 | Hylden et al. | Sep 2004 | B1 |
6882890 | Horn et al. | Apr 2005 | B2 |
6904449 | Quinones | Jun 2005 | B1 |
7103647 | Aziz | Sep 2006 | B2 |
7127330 | Spool et al. | Oct 2006 | B2 |
7143186 | Stewart et al. | Nov 2006 | B2 |
7246078 | Vincent | Jul 2007 | B2 |
7257620 | Lo | Aug 2007 | B2 |
7290244 | Peck et al. | Oct 2007 | B2 |
7318044 | Matsuoka et al. | Jan 2008 | B2 |
7330473 | Baier et al. | Feb 2008 | B1 |
7392421 | Bloomstein et al. | Jun 2008 | B1 |
7401059 | Owen et al. | Jul 2008 | B1 |
7523045 | Walker et al. | Apr 2009 | B1 |
7634757 | De et al. | Dec 2009 | B2 |
7738975 | Denison et al. | Jun 2010 | B2 |
7747404 | Meckelburg et al. | Jun 2010 | B2 |
7778883 | Albazz et al. | Aug 2010 | B2 |
7860609 | Yanagita et al. | Dec 2010 | B2 |
7861223 | Schmidt et al. | Dec 2010 | B1 |
7870223 | Grgic et al. | Jan 2011 | B2 |
7908194 | Hollas | Mar 2011 | B2 |
7912560 | Hood et al. | Mar 2011 | B2 |
7958013 | Porat et al. | Jun 2011 | B2 |
7970830 | Staggs et al. | Jun 2011 | B2 |
8015373 | Ballard et al. | Sep 2011 | B2 |
8015546 | Jones et al. | Sep 2011 | B2 |
8024732 | Sheehan et al. | Sep 2011 | B2 |
8121707 | Karaffa et al. | Feb 2012 | B2 |
8468335 | Lin et al. | Jun 2013 | B2 |
8584114 | Rabinovich et al. | Nov 2013 | B2 |
20020004709 | Peter et al. | Jan 2002 | A1 |
20020029377 | Pavela | Mar 2002 | A1 |
20020049625 | Kilambi et al. | Apr 2002 | A1 |
20030063013 | Jin et al. | Apr 2003 | A1 |
20030076353 | Blackstock et al. | Apr 2003 | A1 |
20030163212 | Smith et al. | Aug 2003 | A1 |
20030204784 | Jorapur | Oct 2003 | A1 |
20030216986 | Hassan | Nov 2003 | A1 |
20050011967 | Skelton-Becker et al. | Jan 2005 | A1 |
20050132055 | Neogi | Jun 2005 | A1 |
20050132064 | Lo | Jun 2005 | A1 |
20050138111 | Aton et al. | Jun 2005 | A1 |
20050278577 | Doong et al. | Dec 2005 | A1 |
20060036876 | Kitada | Feb 2006 | A1 |
20060036907 | Inscoe et al. | Feb 2006 | A1 |
20060064183 | Chandhoke | Mar 2006 | A1 |
20060089886 | Wong | Apr 2006 | A1 |
20060095855 | Britt et al. | May 2006 | A1 |
20060235594 | Knoefler et al. | Oct 2006 | A1 |
20060245564 | Li et al. | Nov 2006 | A1 |
20070005266 | Blevins et al. | Jan 2007 | A1 |
20070074280 | Callaghan et al. | Mar 2007 | A1 |
20070094541 | Kang | Apr 2007 | A1 |
20070118345 | Olesen et al. | May 2007 | A1 |
20070208435 | Schott | Sep 2007 | A1 |
20080141238 | Balassanian | Jun 2008 | A1 |
20080154909 | Dam et al. | Jun 2008 | A1 |
20080208380 | Taylor | Aug 2008 | A1 |
20080222604 | Murphy | Sep 2008 | A1 |
20080243311 | Dahmer et al. | Oct 2008 | A1 |
20080244449 | Morrison et al. | Oct 2008 | A1 |
20080250045 | Balassanian et al. | Oct 2008 | A1 |
20090012631 | Fuller | Jan 2009 | A1 |
20090037008 | Moorer et al. | Feb 2009 | A1 |
20090063650 | Anslow et al. | Mar 2009 | A1 |
20090144108 | Cloud | Jun 2009 | A1 |
20090204458 | Wiese et al. | Aug 2009 | A1 |
20090217163 | Jaroker | Aug 2009 | A1 |
20090265694 | Bakowski | Oct 2009 | A1 |
20090300149 | Ferris et al. | Dec 2009 | A1 |
20090300423 | Ferris | Dec 2009 | A1 |
20100023600 | Hill et al. | Jan 2010 | A1 |
20100023918 | Bernardini et al. | Jan 2010 | A1 |
20100082844 | Stoupis et al. | Apr 2010 | A1 |
20100088150 | Mazhar et al. | Apr 2010 | A1 |
20100131624 | Ferris | May 2010 | A1 |
20100138017 | Vrba et al. | Jun 2010 | A1 |
20100223157 | Kalsi | Sep 2010 | A1 |
20100278336 | Tahan et al. | Nov 2010 | A1 |
20100306379 | Ferris | Dec 2010 | A1 |
20100318665 | Demmer et al. | Dec 2010 | A1 |
20110004685 | De Groot | Jan 2011 | A1 |
20110022626 | Plache et al. | Jan 2011 | A1 |
20110022827 | Plache et al. | Jan 2011 | A1 |
20110117845 | Kirsch et al. | May 2011 | A1 |
20110126168 | Ilyayev | May 2011 | A1 |
20110145439 | Chaturvedi et al. | Jun 2011 | A1 |
20110154092 | Dash et al. | Jun 2011 | A1 |
20110154451 | Thomas | Jun 2011 | A1 |
20110179154 | Ravichandran et al. | Jul 2011 | A1 |
20110191181 | Blackhurst et al. | Aug 2011 | A1 |
20110191500 | Odayappan et al. | Aug 2011 | A1 |
20110197097 | Beaty et al. | Aug 2011 | A1 |
20110202901 | Givoni et al. | Aug 2011 | A1 |
20110208606 | Hadar et al. | Aug 2011 | A1 |
20110208695 | Anand et al. | Aug 2011 | A1 |
20110231670 | Shevchenko et al. | Sep 2011 | A1 |
20110231818 | Steden | Sep 2011 | A1 |
20110238458 | Purcell et al. | Sep 2011 | A1 |
20110246721 | Crisan | Oct 2011 | A1 |
20110264550 | Fair | Oct 2011 | A1 |
20110271278 | Dittrich | Nov 2011 | A1 |
20110282476 | Hegemier et al. | Nov 2011 | A1 |
20110282940 | Zhang et al. | Nov 2011 | A1 |
20110314168 | Bathiche et al. | Dec 2011 | A1 |
20120010488 | Henry et al. | Jan 2012 | A1 |
20120109384 | Stepanian | May 2012 | A1 |
20120131176 | Ferris et al. | May 2012 | A1 |
20120143767 | Abadir et al. | Jun 2012 | A1 |
20120158972 | Gammill et al. | Jun 2012 | A1 |
20120185821 | Yaseen et al. | Jul 2012 | A1 |
20130024542 | Keller et al. | Jan 2013 | A1 |
20130024572 | Chen | Jan 2013 | A1 |
20130096727 | Brandt et al. | Apr 2013 | A1 |
20130124465 | Pingel et al. | May 2013 | A1 |
20130211546 | Lawson et al. | Aug 2013 | A1 |
20130211555 | Lawson et al. | Aug 2013 | A1 |
20130211559 | Lawson et al. | Aug 2013 | A1 |
20130212129 | Lawson et al. | Aug 2013 | A1 |
20130212420 | Lawson et al. | Aug 2013 | A1 |
20130282180 | Layton et al. | Oct 2013 | A1 |
20140047064 | Maturana et al. | Feb 2014 | A1 |
20140047107 | Maturana et al. | Feb 2014 | A1 |
20140058535 | Dickie | Feb 2014 | A1 |
20150066979 | Zhang et al. | Mar 2015 | A1 |
Number | Date | Country |
---|---|---|
1363072 | Aug 2002 | CN |
1857877 | Nov 2006 | CN |
1862477 | Nov 2006 | CN |
101083657 | Dec 2007 | CN |
101196740 | Jun 2008 | CN |
101208674 | Jun 2008 | CN |
101782893 | Jul 2010 | CN |
101958805 | Jan 2011 | CN |
102105861 | Jun 2011 | CN |
1296232 | Mar 2003 | EP |
1742125 | Jan 2007 | EP |
1814036 | Aug 2007 | EP |
2040135 | Mar 2009 | EP |
2237120 | Oct 2010 | EP |
2592812 | May 2013 | EP |
0075826 | Dec 2000 | WO |
0159642 | Aug 2001 | WO |
0228125 | Apr 2002 | WO |
2013103381 | Jul 2013 | WO |
Entry |
---|
Cunning et al., “Automatic Test Case Generation from Requirements Specifications for Real-time Embedded Systems”, vol. No. 5, pp. 784-789, 1999. |
Husain et al., “Remote device management of WiMAX devices in multi-mode multi-access environment”, pp. 1-13, Mar. 31-Apr. 2, 2008. |
“Knowledge as a Service (KaaS) Enables the Right Action, Right Now”, Cumulus IQ: Knowledge as a Service, 2009. |
Altmann et al., “A Marketplace and its Market Mechanism for Trading Commoditized Computing Resources”, TEMEP Discussion Paper, Mar. 2010. |
Ranchal et al., “Protection of Identity Information in Cloud Computing without Trusted Third Party”, 2010 29th IEEE Symposium on Reliable Distributed Systems, pp. 368-372, 2010. |
“Top ten advantages of Google's cloud”, Google Apps for Business, 2011. |
Salves, “Timeline Cloud Family Edition Reviewed”, Pudai LLC, Jul. 18, 2011. |
Arefin et al., “CloudInsight: Shedding Light on the Cloud”, 30th IEEE International Symposium on Reliable Distributed Systems, pp. 219-228, Oct. 4-7, 2011. |
International Search Report and Written Opinion issued in connection with related PCT Application No. PCT/US2012/044767 dated Sep. 19, 2012. |
International Search Report and Written Opinion issued in connection with related PCT Application No. PCT/US2012/044770 dated Sep. 19, 2012. |
International Search Report and Written Opinion issued in connection with related PCT Application No. PCT/US2012/044766 dated Oct. 17, 2012. |
European Office Action issued in connection with related EP Application No. 12735996.6 dated May 28, 2015. |
European Office Action issued in connection with related EP Application No. 12737949.3 dated May 28, 2015. |
European Office Action issued in connection with related EP Application No. 12738292.7 dated May 28, 2015. |
Unofficial English Translation of Chinese Office Action issued in connection with corresponding CN Application No. 201280071226.X dated Nov. 24, 2015. |
Unofficial English Translation of Chinese Office Action issued in connection with related CN Application No. 201280071178.4 dated Dec. 21, 2015. |
Unofficial English Translation of Chinese Office Action issued in connection with related CN Application No. 201280071182.0 dated Dec. 31, 2015. |
Xianjin, et al., “File Synchronization of Multi-Machine System Design and Implementation Based Cloud Storage”, Computer Science and Service System (CSSS), 2011 International Conference, On page(s): 1275-1278, Issue Date: Jun. 27-29, 2011. |
Search Report issued in connection with corresponding PCT Application PCT/US2012/044759 dated Sep. 19, 2012. |
Soon et al., Test Strategy and Automation for Complex Systems,dated Mar. 1, 2007, IP.com Prior Art Database Technical Disclosure,IP.com No. IPCOM000147528D, Mar. 1, 2007. |
IBM,“Method of Creating a Componentized Architecture for Unifying Resource Sharing Scenarios in Cloud Computing Environment”, Prior Art Database Disclosure, pp. 1-13, Feb. 11, 2010. |
Zexi et al., “An Optimal Hysteretic Control Policy for Energy Saving in Cloud Computing”, Global Telecommunications Conference, pp. 1-5, 2011. |
International Search Report and Written Opinion issued in connection with related Application No. PCT/US2013/048529 dated Oct. 4, 2013. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,748 dated Feb. 11, 2014. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,748 dated Oct. 28, 2014. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,672 dated Apr. 28, 2015. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,748 dated May 6, 2015. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,748 dated Sep. 1, 2015. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,204 dated Oct. 15, 2015. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,748 dated Jan. 12, 2016. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,204 dated Feb. 20, 2016. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,672 dated Mar. 1, 2016. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,672 dated Jun. 14, 2016. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,204 dated Jul. 21, 2016. |
U.S. Notice of Allowance issued in connection with related U.S. Appl. No. 13/760,748 dated Aug. 4, 2016. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 13/760,672 dated Sep. 26, 2016. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,204 dated Dec. 20, 2016. |
U.S. Final Office Action issued in connection with related U.S. Appl. No. 13/760,672 dated Jan. 27, 2017. |
U.S. Non-Final Office Action issued in connection with related U.S. Appl. No. 14/376,958 dated Jun. 2, 2017. |
Number | Date | Country | |
---|---|---|---|
20150120012 A1 | Apr 2015 | US |
Number | Date | Country | |
---|---|---|---|
61583956 | Jan 2012 | US |