Intelligence in distributed lighting control devices

Information

  • Patent Grant
  • 10139787
  • Patent Number
    10,139,787
  • Date Filed
    Monday, December 10, 2012
    12 years ago
  • Date Issued
    Tuesday, November 27, 2018
    6 years ago
Abstract
Exemplary systems, methods, and apparatuses for distributed intelligence in facility lighting control are provided. A facility lighting system may be organized into multiple control areas, each of which may include one or more component devices. Each lighting control area may be associated with a control apparatus, which controls the operation of the lighting devices of the associated control area based on various types of signal information. Signal information may include information concerning local conditions or environments, as well as information from a centralized control server. Some embodiments further include monitoring the operation and predicting fault states of the lighting control area.
Description
BACKGROUND OF THE INVENTION

Field of the Invention


The present invention relates to facilities management. More specifically, the present invention relates to distributed intelligence in lighting control.


Description of Related Art


Various resources are provided to an area by facilities systems. Facilities systems may encompass lighting systems, HVAC systems, security systems, fire/safety systems, irrigation systems, agricultural wind systems, blind/louver systems, and the like. The area receiving the resources from facilities systems may include a building, a floor, a room, a group of buildings, etc. Depending on the area, the resources provided, and specific occupant requirements, such facilities systems may include multiple devices of various types. For example, a lighting system for a large building may include several types of lights in various configurations distributed throughout multiple rooms, on multiple floors, etc.


One possible way to manage a facilities system is to provide centralized control of all the devices in such a system. Centralization may allow an individual, such as a facilities manager, to control all the devices of the facilities system from one or a few control interfaces. For example, the facilities manager can turn on all of the lights and/or turn off all of the lights remotely and without having to physically flick each switch on and off in each room. Some disadvantages to a highly centralized control system may include implementation difficulties and inefficiencies. For example, it may be difficult and/or costly to retrofit a large area with a centralized control system.


Centralized control of a facilities system having multiple devices may also be complicated by various factors. For instance, some devices in the system may be subject to different demands than other devices in the system. Using the above example, the lighting system may need to provide more light in certain rooms that do not receive as much natural sunlight as other rooms. As such, high centralization may be inflexible to local conditions and unable to adapt to changing conditions. Further, high centralization may lead to waste. For example, using a highly centralized system to provide adequate resources to the rooms that require it may result in resources being sent to rooms that do not require the same amount of resources. Energy is wasted where resources are provided to areas that do not require such resources.


In contrast, a highly localized facilities control solution presents different disadvantages, such as in the ability to maintain and operate the facilities system. An example of a highly localized control solution is an individual light switch for a light or a group of lights in a particular location. Separate light switches may be distributed throughout a building, floor, etc., and each switch must be separately switched on for its associated device, or group of devices, to be activated. For some areas, this process may be extremely time-consuming. Additionally, separate switches may lead to energy waste when area occupants forget or neglect to switch off each individual switch.


There is, therefore, a need in the art for improved management and control of facilities systems.


SUMMARY OF THE INVENTION

Exemplary systems, methods, and apparatuses of the present invention provide for distributed intelligence in lighting control. A lighting facilities system may be organized into control areas, each of which may include one or more lighting devices. Each lighting control area is associated with a control apparatus, which controls the operation of the lighting devices within the lighting control area based on various types of signal information. Signal information may include information concerning local conditions or environments, as well as information from a centralized control server. In some embodiments, the control apparatus may reference actuation logic in determining operation instructions.


Various embodiments of the present invention include methods for distributed intelligence in lighting control. A method may include receiving signal information concerning a lighting control area in a lighting facilities system with multiple lighting control areas, determining instructions for operation of the lighting control area, and controlling operation of the lighting control area based on the determined instructions. The signal information may include such factors as switching input, centralized control input, schedules, environmental conditions, and the like. Further, in some embodiments, such signal information may be considered and the instructions may be determined by reference to rule-based actuation logic. The method may also include monitoring operation of the control area, detecting any fault states, and predicting when the control area may fail.


In some embodiments, the present invention may include an apparatus for distributed intelligence in lighting control. Associated with a lighting control area, an exemplary apparatus may include a communication interface for receiving various types of signal information, a processor for determining operation instructions, and a controller for controlling operation of the lighting control area based on the operation instructions. Various embodiments may further include timers, schedules, and various sensors, including light sensors, motion sensors, and the like.


Various embodiments of the present invention include systems for distributed intelligence in lighting control. An exemplary system may include multiple lighting control areas. Each lighting control area may be configured to receive signal information, determine operation instructions based on the signal information, and control operations by reference to the determined instructions. The exemplary system may further include a control server configured to provide certain signal information to the multiple control areas.


Some embodiments of the present invention include computer media and instructions for distributed intelligence in facilities control. Embodiments may further include instructions for monitoring operations and predicting failure of control areas in the facilities system.





BRIEF DESCRIPTION OF THE FIGURES


FIG. 1 illustrates an exemplary implementation of an environment providing distributed intelligence in facilities control.



FIG. 2 illustrates an exemplary actuation control apparatus for providing distributed intelligence in facilities control.



FIG. 3 is a flowchart depicting an exemplary method for providing distributed intelligence in facilities control.





DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Embodiments of the present invention comprise systems, methods, and apparatuses for distributed intelligence in control of lighting systems. A facilities lighting system may be organized into multiple control areas. A control area can include a component device or series of component devices in the facilities system. In a lighting system, for example, a control area can include a single light fixture or a group of light fixtures. Each control area is associated with an actuation control apparatus, which determines instructions for the operation of each control area based on various types of signal information and controls operation of the control area based on the determined instructions.



FIG. 1 illustrates an exemplary implementation of an environment 100 providing distributed intelligence in facilities control. Implemented on a communications network 110, environment 100 may include multiple actuation control apparatuses 130A-130C, and a control server 140. Each of the control apparatuses 130A-C may be associated with a control area (e.g., 120A-120C, respectively). In some embodiments of the present invention, the network 110 may also allow for the control server 140 to send and receive information from various user devices.


The network 110 may be a local, proprietary network (e.g., intranet) and/or may be a part of a larger wide-area network. For example, the network 110 may be a local area network (LAN), which may also be communicatively coupled to a wide area network (WAN) such as the Internet. In some embodiments, the network 110 may be configured to transmit various electromagnetic waves, including, for example, radio signals. Examples of the network 110 may include IEEE 802.11 (Wi-Fi or Wireless LAN) networks, IEEE 802.16 (WiMAX) networks, IEEE 802.16c networks, and the like. Network 110 allows for communication between the various components of environment 100.


The control areas 120A-C may comprise a component device or a series of component devices in a facilities system. For example, as illustrated by FIG. 1, the control area 120A includes three lighting devices; the control area 120B includes one lighting device; and the control area 120C includes two lighting devices. A control area may also be defined as some or all devices in a room, on a floor, in a building, and so forth, based on a desired level of granularity. In various embodiments of the present invention, the component devices in a control area 120 may be in close proximity to each other, share similar environmental conditions, etc. Organizing a facilities system into the control areas 120A-C allows for local, distributed management of local devices. The organization further allows for robustness within the environment 100, because the effects of a hardware, software, or communication failure may be contained locally to one of the control areas 120.


Each control area 120A-C may be associated with their respective actuation control apparatus 130A-C. The actuation control apparatus (e.g., 130A) may be embedded in a device (e.g., a light fixture) of the control area (e.g., control area 120A), housed within a ballast (e.g., a ballast associated with the light fixtures of the control area 120A), in a separate device, or the like. Described in further detail with respect to FIG. 3, the actuation control apparatus 130 controls the operation of the device or devices in the control area 120 based on various types of signal information, including signal information sent over the network 110 from the control server 140. Associating each control area 120 with a separate actuation control apparatus 130 allows for granular and autonomous control, while still allowing for centralized control, for example, from the control server 140. In some embodiments of the present invention, the control area 120 may gather, store, generate, and/or transmit information concerning the operation of the devices in the control area 120. Such information may include power usage, energy consumption, equipment status, fault detection, predictions concerning fault states, and the like.


The control server 140 may comprise any combination of computer hardware and software configured to receive and transmit information to actuation control apparatuses (e.g., actuation control apparatuses 130A-C) concerning operation of their control areas (e.g., control areas 120A-C) in a facilities system. The control server 140 may be, for example, an enterprise server, such as that found in any number of corporate entities and businesses.


In some embodiments, control server 140 may be used to designate default settings and/or customize various settings for each of the actuation control apparatuses 130. For example, control server 140 may receive schedule information from a building manager and transmit the information to one or more of the actuation control apparatuses 130 in the facilities system. Each actuation control apparatus 130 may be sent the same information, different information, or a combination of same and different information. For example, each actuation control apparatus 130 may receive slightly different schedules of operation. Other types of information sent to the actuation control apparatuses may include operation instructions, signal information, updated information, etc. In some embodiments, the control server 140 may also receive information from the various control areas 120 concerning the operation of each respective control area 120. Such information may be reported to a building manager, for example. The information may further be used as input data in other devices.



FIG. 2 illustrates the exemplary actuation control apparatus 130 for providing distributed intelligence in facilities control. The actuation control apparatus 130 may include an input/output module 210, actuation logic 220, processor 230, controller 240, timekeeper 250, and sensors 260. Alternative embodiments may comprise more, less, or functionally equivalent components and still be within the scope of the exemplary embodiments.


A module may be any collection of routines that perform various system-level functions and may be dynamically loaded and unloaded by hardware and device drivers as required. The modular software components described herein may also be incorporated as part of a larger software platform or integrated as part of an application specific component.


The input/output module 210 may comprise any of a variety of hardware and/or software components configured to provide a communications interface capable of receiving various types of information from various sources. For example, the input/output module 210 may include various interfaces, devices, and/or antenna for receiving information wirelessly through network 110, and so forth. The information received may include switching information, schedule information, sensor information, information from the control server 140 (FIG. 1), and the like. Users may communicate signal information to the input/output module 210 through switches, as well as through computer-based or web-based interfaces in communication with control server 140.


The input/output module 210 may be further configured to transmit information, such as operation information, status information, prediction information, etc. For example, a report concerning the operation of the devices within the control area 120 associated with the actuation control apparatus 130 may be sent to a building manager or building maintenance staff. Reports may also be sent to a database (e.g., operation database 270) for storage, to various analysis engines for analysis, and so forth.


The exemplary actuation logic 220 may be configured to store and provide guidelines for responding to various types of signal information. For example, the actuation logic 220 may comprise a guideline concerning tasks to be performed at a particular time of day. Specifically, a guideline may direct that at 7:00 am, the lighting devices associated with control area 120 are switched on and the light from the lighting devices increased to 100% lighting capacity, if not already on and at 100%. Another guideline may direct that at 10:00 am, the light of the lighting devices should be dimmed to 70% of full lighting capacity.


In another example, actuation logic 220 may include a guideline concerning one or more tasks to be performed in response to a certain level of light. Using the above example, if the level of light at 10:00 am falls below a predefined level, the guideline may direct that the lighting devices may not be dimmed to 70% lighting capacity. Yet another guideline may direct that a certain level of light may trigger one task during a weekday and a different task during the weekend. Actuation logic 220 may be rule-based, algorithmic, a combination of the foregoing, etc. Depending on the type of facilities system, area requirements, occupant requirements, etc., the actuation logic 220 may provide default guidelines for responses to the particular signal information received. In some embodiments, actuation logic 220 may be customized and/or updated by information received by input/output module 210 through control server 140 (FIG. 1) from a user, such as a building manager, system administrator, etc., to reflect new area requirements, new user requirements, and so forth.


In exemplary embodiments, the processor 230 uses the signal information received by the input/output module 210 and the guidelines provided by the actuation logic 220 to determine operation instructions for the devices of the control area 120. For example, the input/output module 210 may receive signal information concerning a level of light detected in an area by one or more of the sensors 260 (described below). The processor 230 may then consult the guidelines provided by the actuation logic 220 to determine how to respond to such signal information. For example, the processor 230 may determine, based on the guidelines provided by the actuation logic 220, that the particular level of light is associated with a particular task, such as turning off one or more lighting fixtures of the control area 120A.


Having determined the task or tasks to be performed, then processor 230 can then relay operation instructions associated with the task or tasks to the controller 240. The controller 240 is configured to control the operation of the devices of control area 120. Depending on the type of facilities system, the controller 240 can turn the devices of the control area 120 on and off, adjust operation (e.g., dimming lights), and the like.


In some embodiments of the present invention, the timekeeper 250 may be included in the actuation control apparatus 130, or the timekeeper 250 may be included in a separate device associated with the actuation control apparatus 130. In exemplary embodiments, the timekeeper 250 keeps track of and provides signal information concerning dates, times, schedules, etc. to the other components of the actuation control apparatus 130A. Thus, the timekeeper 250 may trigger an operation based on a schedule. The timekeeper 250 may further be used to keep track of holidays and any special schedules of operations associated with certain holidays. For example, a particular holiday may trigger decreased lighting in unoccupied offices. Alternatively, a holiday may trigger a holiday-specific lighting display, including colored lights and/or lighting control areas configured in various shapes. In some embodiments, the timekeeper 250 may provide information concerning the time elapsed between certain events. For example, the timekeeper 250 can provide information to the operations database 270 (described below) concerning the life of a lighting fixture (i.e., when a light bulb is installed and when the light bulb fails).


The sensors 260 may include any of a variety of sensors with the ability to detect a variety of conditional and/or environmental information, including occupancy, motion, sound, vibration, light, loss of radio communication, power usage, etc. The types of sensors 260 included in the actuation control apparatus 130 may vary depending on requirements of the area, requirements of the facilities system, etc. For example, a particular security system may incorporate motion sensors, but not light sensors.


In some embodiments, the sensors 260 may be embedded in the actuation control apparatus 130A, housed in a separate device, or the like. Upon sensing the conditional or environmental information, the sensors 260 can provide signal information to the input/output module 210. The sensors 260 may further allow for the operation of the control area 120 to be responsive to its local environment. For example, the sensors 260 may detect changing levels of natural sunlight in a room throughout a day. That information may be provided to the processor 230, which can then generate instructions for adjusting the level of lamp light in that room proportionately with the loss of sunlight so that the room may be provided with a consistent level of light. In some embodiments of the present invention, information concerning the operational state of the sensors (e.g., failure in communication) may also be used, in conjunction with actuation logic 220, to determine the operational state of a control area 120, the system, and/or to generate instructions.


The actuation control apparatus 130A optionally may comprise an operations database 270 for storing information concerning the operations of the devices of the control area 120. Such operation information may include measurements of current, voltage, power and energy consumption, equipment status, operating hours, etc. Some of the operation information (e.g., operating hours) may be received from the timekeeper 250 and/or the sensors 260. In some embodiments, the information may be processed to determine a minimum, maximum, averages, etc., which may also be stored in the operations database 270. Such information may be communicated to the network 110 for reporting. The information may also be used as input data for various algorithms, such as an algorithm for determining a fault state in a lighting fixture or ballast based on the characteristics of an electric load. A fault state in a lighting device, for example, may include a failed light bulb, etc. that may result in the device being inoperable. In various embodiments, such information concerning the electric load may be provided to the control server 140 for determination of fault states. Alternatively, the information may be provided to the processor 230 for determining a fault state. The processor 230 may further provide the information concerning the fault state to the operations database 270 for storage. Further, the operations database 270 may provide information concerning the number of actuations and operating hours for a lighting fixture of the control area 120, for example. When the number of actuations or operating hours accumulates to a certain level, the life of the lighting fixture or other device may be close to expiry.



FIG. 3 is a flowchart depicting an exemplary method 300 for providing distributed intelligence in facilities control. In this method, signal information is received at a control area 120, operation instructions for the control area 120 are determined, and the control area 120 is operated according to the instructions. In some embodiments of the present invention, the operation of the control area 120 may be monitored, and a fault state in the control area 120 may be detected. Further, predictions concerning future fault states may be made based on operation information.


In step 310, signal information is received by the input/output module 210. The signal information may come from various sources, including user input through switches, user input through computer-based or web-based interfaces in communication with the control server 140, the timekeeper 250, the sensors 260, a combination of the foregoing, and so forth. For example, the timekeeper 250 may provide signal information concerning a time of day. Alternatively, the sensors 260 may sense motion in a particular area and communicate signal information concerning the sensed motion to the input/output module 210.


In step 320, operation instructions are determined. Consulting the actuation logic 220, the processor 230 may determine what task or tasks are associated with the signal information received by the input/output module 210. For example, signal information concerning motion as detected by one of the motion sensor 260 is received. The processor 230 may access the actuation logic 220 for guidelines in responding to the signal information. The appropriate guidelines, as provided by the actuation logic 220, may indicate that motion at a certain time in a certain area is associated with a particular task or set of tasks, such as sounding a security alarm or set of security alarms. Subsequently, the processor 230 determines the operation instructions for the indicated tasks and relays the instructions to the controller 240.


In step 330, operations of the control area 120 are controlled according to the instructions. In an exemplary embodiment, the controller 240 receives the operation instructions and controls the operation of the devices of the control area 120. For example, the controller 240 may receive instructions for sounding the security alarm associated with the control area 120 and then control operation of the security alarm according to the received instructions.


In an optional step 340, operations of the control area 120 may be monitored. Various information, including current, voltage, power, energy consumption, information from the timekeeper 250, information from the sensors 260, etc., may be stored in the operations database 270. Such information may be processed and reported to various parties, including occupants, building managers, other devices, and so forth.


In an optional step 350, a fault state in the control area 120 may be detected. Variations in power usage, energy usage, electrical load, etc., may indicate a fault state in one or more devices of the control area 120. Such determinations may be based on the information stored in the operations database 270. In some embodiments, the fault state may be reported to occupants, building managers, etc. through the network 110.


In an optional step 360, a prediction is made concerning a possible future fault state. Information from the operations database 270 may be used to estimate or predict a lifespan for the one or more devices of the control area 120. Such information may also be reported to occupants, building managers, etc. through the network 110.


Some of the above-described functions can be composed of instructions that are stored on storage media (e.g., computer-readable medium). The instructions may be retrieved and executed by the processor 230. Some examples of storage media are memory devices, tapes, disks, integrated circuits, and servers. The instructions are operational when executed by the processor 230 to direct the processor 230 to operate in accord with the invention. Those skilled in the art are familiar with instructions, processor(s), and storage media.


It is noteworthy that any hardware platform suitable for performing the processing described herein is suitable for use with the invention. The terms “computer-readable medium” and “computer-readable media” as used herein refer to any medium or media that participate in providing instructions to a CPU for execution. Such media can take many forms, including, but not limited to, non-volatile media, volatile media and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as a fixed disk. Volatile media include dynamic memory, such as system RAM. Transmission media include coaxial cables, copper wire and fiber optics, among others, including the wires that comprise one embodiment of a bus. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, punch cards, paper tape, any other physical medium with patterns of marks or holes, a RAM, a PROM, an EPROM, a FLASHEPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.


Various forms of computer-readable media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU.


The above description is illustrative and not restrictive. Many variations of the invention will become apparent to those of skill in the art upon review of this disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.


While the present invention has been described in connection with a series of preferred embodiment, these descriptions are not intended to limit the scope of the invention to the particular forms set forth herein. It will be further understood that the methods of the invention are not necessarily limited to the discrete steps or the order of the steps described. To the contrary, the present descriptions are intended to cover such alternatives, modifications, and equivalents as may be included within the spirit and scope of the invention as defined by the appended claims and otherwise appreciated by one of ordinary skill in the art.

Claims
  • 1. A method for distributed intelligence in facility lighting control, the method comprising: detecting installation of a component for a lighting device;sensing, using a sensor, presence of occupants in a lighting control area;receiving signal information concerning a lighting control area in a facilities system comprising a plurality of control areas, the control area comprising the lighting device, wherein the signal information includes an indication as to when the component failed, as well as information concerning power usage, number of actuations, fault detection, and predictions concerning fault states of the component, wherein fault detection comprises evaluating characteristics of an electric load of the component;determining instructions for operation of the control area based on at least rule-based actuation logic and the received signal information, wherein the rule-based actuation logic comprises tasks associated with particular light levels;predicting that the component is close to expiry by evaluating the number of actuations or operating hours of the component accumulated relative to a predetermined level or threshold;determining, by a dedicated time keeper based on the signal information, a time period between installation of the component and failure of the component;storing, by the dedicated time keeper, the time period in a database; andproviding alarms or tasks, based on the time period or the prediction that the component is close to expiry.
  • 2. The method of claim 1, wherein the signal information comprises information concerning an environmental condition.
  • 3. The method of claim 1, wherein the signal information comprises information concerning an operation schedule.
  • 4. The method of claim 1, wherein the signal information comprises information from a control server.
  • 5. The method of claim 1, wherein the signal information comprises information designated by a user.
  • 6. The method of claim 1, further comprising monitoring operation of the lighting control area.
  • 7. The method of claim 6, wherein monitoring operation of the lighting control area further comprises detecting a fault state in the lighting control area.
  • 8. The method according to claim 1, further comprising: detecting actuations or operating hours for a plurality of lighting devices, the lighting device being similar to the plurality of lighting devices;detecting a fault state for one or more of the plurality of lighting devices; andpredicting failure of the lighting device based upon actuations or operating hours for the lighting device as compared to the actuations or operating hours for the plurality of lighting devices and the detected fault state.
  • 9. The method according to claim 1, further comprising: detecting actuations or operating hours for a plurality of lighting devices, the lighting device having similar components to the plurality of lighting devices, the components comprising any of a bulb, a ballast, a power supply, a controller, or combinations thereof;detecting a fault state for one or more of the components of the plurality of lighting devices;predicting failure of the lighting device based upon actuations or operating hours for the lighting device as compared to the actuations or operating hours for the plurality of lighting devices and the detected fault state; andtransmitting to a control server a message that is indicative of the predicted failure of the lighting device.
  • 10. An apparatus for distributed intelligence in facility lighting control, the apparatus comprising: a communication interface configured to receive signal information concerning a lighting control area in a facilities system comprising a plurality of lighting control areas, the signal information further comprising power usage, number of actuations, fault detection, and predictions concerning fault states of a component for a lighting device within the lighting control area, wherein fault detection comprises evaluating characteristics of an electric load of the component;a processor configured to determine instructions for operation of the control area based on at least rule-based actuation logic and the received signal information, wherein the rule-based actuation logic comprises tasks associated with particular light levels, the processor further configured to predict that the component is close to expiry by evaluating the number of actuations or operating hours of the component accumulated relative to a level or threshold so as to determine a future fault state for the lighting control area by comparing fault states for similar lighting control areas to the signal information of the lighting control area, as detected and stored by a dedicated time keeper;the dedicated time keeper configured to track and provide signal information concerning date and time to the component and trigger operations; anda controller configured to transmit a predicted future fault state for the lighting control area to a control server and estimate an expiry of a similar component based on a determined time period for the component that comprises a time frame defined by an installation date and a failure date.
  • 11. The apparatus of claim 10, further comprising a timekeeper configured to provide signal information concerning date and time.
  • 12. The apparatus of claim 10, further comprising a light sensor configured to provide signal information concerning a level of light.
  • 13. The apparatus of claim 10, further comprising a motion sensor configured to provide signal information concerning presence of an occupant.
  • 14. The apparatus of claim 10, wherein the communication interface is further configured to receive signal information from the control server.
  • 15. A system for distributed intelligence in facility lighting control, the system comprising: a plurality of lighting control areas, each lighting control area comprising: a plurality of sensors for capturing environmental input;a communication interface for receiving signal information concerning a lighting control area, the signal information further comprising power usage, number of actuations, fault detection, and predictions concerning fault states of a component for a lighting device within one of the plurality of lighting control areas, wherein fault detection comprises evaluating characteristics of an electric load of the component;a processor configured to determine instructions for operation of the control area based on at least rule-based actuation logic and the received signal information, wherein the rule-based actuation logic comprises tasks associated with particular light levels and the signal information includes light levels sensed in the lighting control area, as well as information concerning the presence of occupants in the lighting control area, wherein the tasks further comprise selectively adjusting artificial light in the lighting control areas as natural light level changes in the lighting control areas, and predict that the component is close to expiry by evaluating the number of actuations or operating hours of the component accumulated relative to level or threshold;a controller for controlling operation of the lighting control area by selecting a task that is associated with the particular light level and the presence of occupants in the lighting control area; anda control server configured to provide signal information concerning an operation configuration to each lighting control area in the plurality of lighting control areas in response to the task determined for each of the lighting control areas.
  • 16. The system of claim 15, wherein the control server is further configured to receive user input concerning the operation configuration.
  • 17. The system of claim 15, wherein the control server is further configured to receive operation information from each control area from the plurality of control areas.
  • 18. A method for distributed intelligence in facility lighting control, the method comprising: detecting installation of a component for a lighting device, the component comprising any of a bulb, a ballast, a power supply, a controller, or combinations thereof;receiving signal information concerning a lighting control area in a facilities system comprising a plurality of control areas, the control area comprising the lighting device, wherein the signal information includes an indication as to when the component failed;determining a time period between installation of the component and failure of the component using a dedicated time keeper;determining instructions for operation of the control area based on at least rule-based actuation logic and the received signal information, wherein the rule-based actuation logic comprises tasks associated with particular light levels;predicting that the component is close to expiry by evaluating a number of actuations or operating hours of the component accumulated relative to a predetermined level or threshold;storing the time period in a database by the dedicated time keeper;transmitting the time period to a control server; andproviding alarms or tasks, based on the time period or the prediction that the component is close to expiry.
CROSS REFERENCE TO RELATED APPLICATIONS

This nonprovisional patent application is a continuation application of U.S. patent application Ser. No. 12/156,621, filed on Jun. 2, 2008, now U.S. Pat. No. 8,364,325, issued Jan. 29, 2013, entitled “Intelligence in Distributed Lighting Control Devices,” which is hereby incorporated by reference in its entirety.

US Referenced Citations (300)
Number Name Date Kind
3598994 Markle et al. Aug 1971 A
3733528 Gilbreath May 1973 A
3735141 Beling May 1973 A
4242614 Vatis et al. Dec 1980 A
4323820 Teich Apr 1982 A
4347461 Carlson Aug 1982 A
4355309 Hughey et al. Oct 1982 A
4358717 Elliott Nov 1982 A
4388567 Yamazaki et al. Jun 1983 A
4454509 Buennagel et al. Jun 1984 A
4686380 Angott Aug 1987 A
4797599 Ference et al. Jan 1989 A
4889999 Rowen Dec 1989 A
5005211 Yuhasz Apr 1991 A
5025248 Bergeron Jun 1991 A
5061997 Rea Oct 1991 A
5146153 Luchaco et al. Sep 1992 A
5154504 Helal Oct 1992 A
5237264 Moseley et al. Aug 1993 A
5248919 Hanna et al. Sep 1993 A
5268631 Gorman et al. Dec 1993 A
5357170 Luchaco et al. Oct 1994 A
5373453 Bae Dec 1994 A
5471063 Hayes et al. Nov 1995 A
5561351 Vrionis et al. Oct 1996 A
5572438 Ehlers et al. Nov 1996 A
5637930 Rowen et al. Jun 1997 A
5659289 Zonkoski Aug 1997 A
5770926 Choi et al. Jun 1998 A
5774052 Hamm Jun 1998 A
5818128 Hoffman et al. Oct 1998 A
5822012 Jeon et al. Oct 1998 A
5872429 Xia et al. Feb 1999 A
5904621 Small et al. May 1999 A
5905442 Mosebrook et al. May 1999 A
5909087 Bryde et al. Jun 1999 A
5927603 McNabb Jul 1999 A
5962989 Baker Oct 1999 A
5982103 Mosebrook et al. Nov 1999 A
6025783 Steffens, Jr. Feb 2000 A
6044062 Brownrigg et al. Mar 2000 A
6100653 Lovell et al. Aug 2000 A
6108614 Lincoln et al. Aug 2000 A
6148306 Seidl et al. Nov 2000 A
6169377 Bryde et al. Jan 2001 B1
6175860 Gaucher Jan 2001 B1
6184622 Lovell et al. Feb 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6252358 Xydis et al. Jun 2001 B1
6297724 Bryans et al. Oct 2001 B1
6300727 Bryde et al. Oct 2001 B1
6301674 Saito et al. Oct 2001 B1
6311105 Budike, Jr. Oct 2001 B1
6323781 Hutchison Nov 2001 B1
6388399 Eckel et al. May 2002 B1
6400280 Osakabe Jun 2002 B1
6439743 Hutchison Aug 2002 B1
6441750 Hutchison Aug 2002 B1
6450662 Hutchison Sep 2002 B1
6473002 Hutchison Oct 2002 B1
6474839 Hutchison Nov 2002 B1
6504266 Ervin Jan 2003 B1
6510369 Lacy Jan 2003 B1
6527422 Hutchison Mar 2003 B1
6535859 Yablonowski et al. Mar 2003 B1
6548967 Dowling et al. Apr 2003 B1
6614358 Hutchison et al. Sep 2003 B1
6633823 Bartone et al. Oct 2003 B2
6640142 Wong et al. Oct 2003 B1
6676831 Wolfe Jan 2004 B2
6689050 Beutter et al. Feb 2004 B1
6700334 Weng Mar 2004 B2
6775588 Peck Aug 2004 B1
6791606 Miyano Sep 2004 B1
6803728 Balasubramaniam et al. Oct 2004 B2
6891838 Petite et al. May 2005 B1
6904385 Budike, Jr. Jun 2005 B1
6914395 Yamauchi et al. Jul 2005 B2
6914893 Petite Jul 2005 B2
6927546 Adamson et al. Aug 2005 B2
6990394 Pasternak Jan 2006 B2
7006768 Franklin Feb 2006 B1
7039532 Hunter May 2006 B2
7042170 Vakil et al. May 2006 B2
7045968 Bierman et al. May 2006 B1
7054271 Brownrigg et al. May 2006 B2
7079808 Striemer Jul 2006 B2
7103511 Petite Sep 2006 B2
7167777 Budike, Jr. Jan 2007 B2
7199530 Vakil et al. Apr 2007 B2
7202613 Morgan et al. Apr 2007 B2
7221110 Sears et al. May 2007 B2
7233080 Garnault et al. Jun 2007 B2
7263073 Petite et al. Aug 2007 B2
7274975 Miller Sep 2007 B2
7307389 Vakil et al. Dec 2007 B2
7307542 Chandler et al. Dec 2007 B1
7333880 Brewster et al. Feb 2008 B2
7339466 Mansfield et al. Mar 2008 B2
7346433 Budike, Jr. Mar 2008 B2
7349766 Rodgers Mar 2008 B2
7352972 Franklin Apr 2008 B2
7354175 Culbert et al. Apr 2008 B2
7356308 Hamada et al. Apr 2008 B2
7369060 Veskovic et al. May 2008 B2
7400226 Barrieau et al. Jul 2008 B2
7417556 Ling Aug 2008 B2
7432803 Fails et al. Oct 2008 B2
7446671 Giannopoulos et al. Nov 2008 B2
7490957 Leong et al. Feb 2009 B2
7491111 Ghaly Feb 2009 B2
7528503 Rognli et al. May 2009 B2
7550931 Lys et al. Jun 2009 B2
7561977 Horst et al. Jul 2009 B2
7565227 Richard et al. Jul 2009 B2
7571063 Howell et al. Aug 2009 B2
7599764 Matsuura et al. Oct 2009 B2
7606639 Miyaji Oct 2009 B2
7623042 Huizenga Nov 2009 B2
7650425 Davis et al. Jan 2010 B2
7659674 Mueller et al. Feb 2010 B2
7677753 Wills Mar 2010 B1
7697927 Owens Apr 2010 B1
7706928 Howell et al. Apr 2010 B1
7719440 Delp et al. May 2010 B2
7755505 Johnson et al. Jul 2010 B2
7760068 Hatemata et al. Jul 2010 B2
7783188 Clark Aug 2010 B2
7812543 Budike, Jr. Oct 2010 B2
7839017 Huizenga et al. Nov 2010 B2
7843353 Pan et al. Nov 2010 B2
7860495 McFarland Dec 2010 B2
7880394 Sibalich et al. Feb 2011 B2
7884732 Huizenga Feb 2011 B2
7889051 Billig et al. Feb 2011 B1
7902759 Newman, Jr. Mar 2011 B2
7925384 Huizenga et al. Apr 2011 B2
7962054 Nakazato et al. Jun 2011 B2
8033686 Recker et al. Oct 2011 B2
8214061 Westrick et al. Jul 2012 B2
8275471 Huizenga et al. Sep 2012 B2
8344665 Verfuerth et al. Jan 2013 B2
8364325 Huizenga et al. Jan 2013 B2
8571904 Guru et al. Oct 2013 B2
8575861 Gordin Nov 2013 B1
8588830 Myer et al. Nov 2013 B2
8755915 Huizenga et al. Jun 2014 B2
8854208 Huizenga et al. Oct 2014 B2
9192019 Huizenga et al. Nov 2015 B2
9664814 Huizenga et al. May 2017 B2
9888548 Huizenga et al. Feb 2018 B2
20010015409 Mahler et al. Aug 2001 A1
20010025349 Sharood et al. Sep 2001 A1
20020009978 Dukach et al. Jan 2002 A1
20020043938 Lys Apr 2002 A1
20020080027 Conley, III Jun 2002 A1
20020143421 Wetzer Oct 2002 A1
20020175815 Baldwin Nov 2002 A1
20030015973 Ovens et al. Jan 2003 A1
20030020595 Wacyk Jan 2003 A1
20030034284 Wolfe Feb 2003 A1
20030058350 Ishimaru et al. Mar 2003 A1
20030109938 Daum Jun 2003 A1
20030154044 Lundstedt Aug 2003 A1
20030209999 Hui et al. Nov 2003 A1
20040002792 Hoffknecht Jan 2004 A1
20040051467 Balasubramaniam et al. Mar 2004 A1
20040090787 Dowling May 2004 A1
20040100394 Hitt May 2004 A1
20040130909 Mueller et al. Jul 2004 A1
20040153207 Peck Aug 2004 A1
20050017922 Devos et al. Jan 2005 A1
20050030203 Sharp et al. Feb 2005 A1
20050043862 Brickfield et al. Feb 2005 A1
20050090915 Geiwitz Apr 2005 A1
20050099319 Hutchison et al. May 2005 A1
20050234600 Boucher et al. Oct 2005 A1
20060001950 Fujimura et al. Jan 2006 A1
20060044152 Wang Mar 2006 A1
20060125426 Veskovic Jun 2006 A1
20060142900 Rothman et al. Jun 2006 A1
20060159336 Uezono Jul 2006 A1
20060161270 Luskin et al. Jul 2006 A1
20060215345 Huizenga Sep 2006 A1
20060244624 Wang et al. Nov 2006 A1
20060245360 Ensor Nov 2006 A1
20060291136 Okishima Dec 2006 A1
20070005195 Pasquale et al. Jan 2007 A1
20070013489 Bechtle Jan 2007 A1
20070024708 Lin Feb 2007 A1
20070057807 Walters et al. Mar 2007 A1
20070085700 Walters et al. Apr 2007 A1
20070090960 Miki Apr 2007 A1
20070229250 Recker et al. Oct 2007 A1
20070237195 Sekigawa Oct 2007 A1
20070271006 Golden et al. Nov 2007 A1
20070273290 Ashdown Nov 2007 A1
20070273307 Westrick et al. Nov 2007 A1
20070276547 Miller Nov 2007 A1
20070291483 Lys Dec 2007 A1
20080071391 Busby et al. Mar 2008 A1
20080075476 Nakazato et al. Mar 2008 A1
20080133065 Cannon et al. Jun 2008 A1
20080167756 Golden et al. Jul 2008 A1
20080183307 Clayton et al. Jul 2008 A1
20080231464 Lewis et al. Sep 2008 A1
20080242314 McFarland Oct 2008 A1
20080258633 Voysey Oct 2008 A1
20080265799 Sibert Oct 2008 A1
20080281473 Pitt Nov 2008 A1
20090018706 Wittner Jan 2009 A1
20090026966 Budde et al. Jan 2009 A1
20090045941 Cooper Feb 2009 A1
20090048691 Donaldson Feb 2009 A1
20090055032 Rodgers Feb 2009 A1
20090058193 Reid et al. Mar 2009 A1
20090063257 Zak et al. Mar 2009 A1
20090066473 Simons Mar 2009 A1
20090072945 Pan et al. Mar 2009 A1
20090132070 Ebrom et al. May 2009 A1
20090174866 Okada Jul 2009 A1
20090198384 Ahn Aug 2009 A1
20090204232 Guru et al. Aug 2009 A1
20090218951 Weaver Sep 2009 A1
20090222223 Walters et al. Sep 2009 A1
20090236910 Yamada et al. Sep 2009 A1
20090240381 Lane Sep 2009 A1
20090243517 Verfuerth et al. Oct 2009 A1
20090248217 Verfuerth et al. Oct 2009 A1
20090261735 Sibalich et al. Oct 2009 A1
20090262189 Marman Oct 2009 A1
20090267540 Chemel et al. Oct 2009 A1
20090278472 Mills et al. Nov 2009 A1
20090278934 Ecker et al. Nov 2009 A1
20090292402 Cruickshank, III Nov 2009 A1
20090292403 Howell et al. Nov 2009 A1
20090299527 Huizenga et al. Dec 2009 A1
20090315485 Verfuerth et al. Dec 2009 A1
20100008676 Kojima Jan 2010 A1
20100039240 Rodriguez et al. Feb 2010 A1
20100052939 Liang Mar 2010 A1
20100066267 Meyer Mar 2010 A1
20100114340 Huizenga et al. May 2010 A1
20100134019 Berhorst Jun 2010 A1
20100134051 Huizenga et al. Jun 2010 A1
20100141153 Recker et al. Jun 2010 A1
20100164386 You Jul 2010 A1
20100179670 Forbes, Jr. et al. Jul 2010 A1
20100185339 Huizenga et al. Jul 2010 A1
20100191388 Huizenga Jul 2010 A1
20100201203 Schatz et al. Aug 2010 A1
20100204847 Leete, III et al. Aug 2010 A1
20100207548 Iott Aug 2010 A1
20100237783 Dupre et al. Sep 2010 A1
20100262296 Davis et al. Oct 2010 A1
20100265100 Jalbout et al. Oct 2010 A1
20100327766 Recker et al. Dec 2010 A1
20110006877 Franklin Jan 2011 A1
20110012541 Finch Jan 2011 A1
20110029136 Altonen et al. Feb 2011 A1
20110043035 Yamada et al. Feb 2011 A1
20110043052 Huizenga et al. Feb 2011 A1
20110101871 Schenk et al. May 2011 A1
20110109424 Huizenga et al. May 2011 A1
20110112702 Huizenga et al. May 2011 A1
20110121654 Recker et al. May 2011 A1
20110133655 Recker et al. Jun 2011 A1
20110175533 Holman et al. Jul 2011 A1
20110175553 Sampsell Jul 2011 A1
20110206393 Nakazato et al. Aug 2011 A1
20120001548 Recker et al. Jan 2012 A1
20120004739 Sato Jan 2012 A1
20120020060 Myer et al. Jan 2012 A1
20120025717 Klusmann et al. Feb 2012 A1
20120026726 Recker et al. Feb 2012 A1
20120043889 Recker et al. Feb 2012 A1
20120074843 Recker et al. Mar 2012 A1
20120080944 Recker et al. Apr 2012 A1
20120098432 Recker et al. Apr 2012 A1
20120098436 Talstra et al. Apr 2012 A1
20120098439 Recker et al. Apr 2012 A1
20120098655 Preta Apr 2012 A1
20120143383 Cooperrider et al. Jun 2012 A1
20120330476 Huizenga et al. Dec 2012 A1
20130002424 Haynes Jan 2013 A1
20130009036 Yianni et al. Jan 2013 A1
20130033183 Verfuerth et al. Feb 2013 A1
20130103201 Huizenga et al. Apr 2013 A1
20130113291 Recker et al. May 2013 A1
20130131882 Verfuerth et al. May 2013 A1
20130147366 Huizenga et al. Jun 2013 A1
20130193847 Recker et al. Aug 2013 A1
20130221858 Silberstein Aug 2013 A1
20130285558 Recker et al. Oct 2013 A1
20140265878 Gritti Sep 2014 A1
20140354995 Huizenga et al. Dec 2014 A1
20160021723 Huizenga et al. Jan 2016 A1
20170079124 Flinsenberg Mar 2017 A1
20170231071 Elinsenberg Aug 2017 A1
20180084628 Huizenga et al. Mar 2018 A1
Non-Patent Literature Citations (58)
Entry
Zhang, X. and Gockenbach, E., “Component Reliability Modeling of Distribution Systems Based on the Evaluation of Failure Statistics”, Oct. 2007, IEEE Transactions on Dielectrics and Electrical Insulation, vol. 14, No. 5. (Year: 2007).
Singhvi, V.; Krause, A.; Guestrin, C.; Garrett Jr., J.H. and Matthews, H.S., “Intelligent Light Control using Sensor Networks”, Nov. 2-4, 2005, SenSys 2005, San Diego, California, USA., ACM 1-59593-054-X/05/0011. (Year: 2005).
Adams, J.T., “Wireless Sensors and Controls Make the Organic Building,” May 2006, Proceedings of the 2006 IEEE Intl. Symposium on Electronics and the Environment, pp. 109-113.
Canovas, S. R., Chermont, M.G., and Cugnasaca, C.E., “Remote Monitoring and Actuation Based on LonWorks Technology,” Jul. 2005, 2005 EFITA/WCCA Joint Congress on IT in Agriculture.
Gislason, D. and Gillman, T. “ZigBee Wireless Sensor Networks,” Nov. 2004, Dr. Dobbs online journal, www.ddj.com/184405887.
Gutierrez, J.A., “On the Use of IEEE Std. 802, 15.4 to enable Wireless Sensor Networks in Building Automation,” Dec. 2007, Int'l. Journal of Wireless Information Network, vol. 14, No. 4.
Kintner-Meyer, M. “Opportunities of Wireless Sensors and Controls for Building Operations,” Aug.-Sep. 2005, Energy Engineering, vol. 102, No. 5, pp. 27-48.
Motegi, N., Piette, M., Kinney, S., and Herter, K., “Web-Based Energy Information Systems for Energy Management and Demand Response in Commercial Buildings,” Apr. 2003, Lawrence Berkeley National Laboratory.
Park, H., Burke, J., and Srivastava, M., “Design and Implementation of a Wireless Sensor Network for Intelligent Light Control,” Apr. 2007, IPSN 07.
Sandhu, J.S.S., Agogino, A.M., “Wireless Sensor Networks for Commercial Lighting Control: Decision Making with Multi-Agent Systems,” Jul. 2004, Workshop on Sensor Networks.
Sandhu, J.S., Agogino, A.M., and Agogino, A.K., “Wireless Sensor Networks for Commercial Lighting Control: Decision Making with Multi-Agent Systems,” 2004, American Association for Artificial Intelligence.
Singhvi, V., Krause, A., Guestrin, C., Garrett, J.H., Matthews, H.S. “Intelligent Light Control Usine Sensor Networks,” Nov. 2005, SenSys 2005.
Teasdale, D., Rubinstein, F., Watson, D., and Purdy, S., “Annual Technical Progress Report: Adapting Wireless Technology to Lighting Control and Environmental Sensing,” Oct. 2005, Dust Networks, Annual Technical Progress Report.
Wang, D., Arens, E., and Federspiel, C., “Opportunities to Same Energy and Improve Comfort by Using Wireless Sensor Networks in Buildings,” Oct. 2003, Proceedings of the third intl Conference for Enhanced Building Operations.
Sekinger, J., “Wireless Lighting Control Technology,” Oct. 2005, Phillips NAESCO Midwest Regional Mtgs.
Non-Final Office Action, dated May 7, 2008, U.S. Appl. No. 11/376,620, filed Mar. 14, 2006.
Final Office Action, dated Oct. 17, 2008, U.S. Appl. No. 11/376,620, filed Mar. 14, 2006.
Non-Final Office Action, dated Mar. 5, 2009, U.S. Appl. No. 11/376,620, filed Mar. 14, 2006.
Notice of Allowance, dated Oct. 5, 2009, U.S. Appl. No. 11/376,620, filed Mar. 14, 2006.
Notice of Allowance, dated Oct. 20, 2009, U.S. Appl. No. 11/376,620, filed Mar. 14, 2006.
Non-Final Office, dated Apr. 16, 2010, U.S. Appl. No. 12/156,621, filed Jun. 2, 2008.
Final Office Action, dated Sep. 10, 2010, U.S. Appl. No. 12/156,621, filed Jun. 2, 2008.
Non-Final Office Action, dated Apr. 13, 2011, U.S. Appl. No. 12/156,621, filed Jun. 2, 2008.
Final Office Action, dated Dec. 7, 2011, U.S. Appl. No. 12/156,621, filed Jun. 2, 2008.
Notice of Allowance, dated Aug. 20, 2012, U.S. Appl. No. 12/156,621, filed Jun. 2, 2008.
Non-Final Office Action, dated Oct. 14, 2011, U.S. Appl. No. 12/912,717, filed Oct. 26, 2010.
Notice of Allowance, dated May 21, 2012, U.S. Appl. No. 12/912,717, filed Oct. 26, 2010.
Non-Final Office Action, dated May 26, 2011, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Final Office Action, dated Feb. 23, 2012, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Non-Final Office Action, dated Oct. 10, 2012, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Final Office Action, dated Apr. 26, 2013, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Advisory Action, dated Jul. 9, 2013, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Non-Final Office Action, dated Apr. 19, 2010, U.S. Appl. No. 12/613,970, filed Nov. 6, 2009.
Final Office Action, dated Jul. 23, 2010, U.S. Appl. No. 12/613,970, filed Nov. 6, 2009.
Non-Final Office Action, dated Oct. 5, 2011, U.S. Appl. No. 12/613,970, filed Nov. 6, 2009.
Final Office Action, dated Jun. 28, 2012, U.S. Appl. No. 12/613,970, filed Nov. 6, 2009.
Non-Final Office Action, dated Jul. 6, 2010, U.S. Appl. No. 12/380,727, filed Mar. 2, 2009.
Notice of Allowance, dated Sep. 8, 2010, U.S. Appl. No. 12/380,727, filed Mar. 2, 2009.
Non-Final Office Action, dated Jul. 8, 2010, U.S. Appl. No. 12/579,353, filed Oct. 14, 2009.
Notice of Allowance, dated Oct. 28, 2010, U.S. Appl. No. 12/579,353, filed Oct. 14, 2009.
Notice of Allowance, dated Dec. 20, 2010, U.S. Appl. No. 12/579,353, filed Oct. 14, 2009.
Non-Final Office Action, dated Jun. 9, 2010, U.S. Appl. No. 12/690,875, filed Jan. 20, 2010.
Notice of Allowance, dated Dec. 10, 2010, U.S. Appl. No. 12/690,875, filed Jan. 20, 2010.
Notice of Allowance, dated Mar. 4, 2011, U.S. Appl. No. 12/690,875, filed Jan. 20, 2010.
Non-Final Office Action, dated Feb. 2, 2012, U.S. Appl. No. 12/913,725, filed Oct. 27, 2010.
Office Action, dated Oct. 24, 2013, U.S. Appl. No. 13/590,981, filed Aug. 21, 2012.
Non-Final Office Action, dated Jan. 24, 2014, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Notice of Allowance, dated Jun. 27, 2014, U.S. Appl. No. 12/940,902, filed Nov. 5, 2010.
Notice of Allowance, dated Jan. 30, 2014, U.S. Appl. No. 13/590,981, filed Aug. 21, 2012.
Non-Final Office Action, dated May 26, 2015, U.S. Appl. No. 13/694,455, filed Dec. 4, 2012.
Non-Final Office Action, dated Apr. 25, 2016, U.S. Appl. No. 14/459,322, filed Aug. 14, 2014.
Final Office Action, dated Oct. 11, 2016, U.S. Appl. No. 14/459,322, filed Aug. 14, 2014.
Advisory Action, dated Dec. 19, 2016, U.S. Appl. No. 14/459,322, filed Aug. 14, 2014.
Advisory Action, dated Mar. 1, 2017, U.S. Appl. No. 14/459,322, filed Aug. 14, 2014.
Notice of Allowance, dated Mar. 8, 2017, U.S. Appl. No. 14/459,322, filed Aug. 14, 2014.
Non-Final Office Action, dated Jul. 13, 2017, U.S. Appl. No. 14/869,909, filed Sep. 29, 2015.
Final Office Action, dated Aug. 25, 2017, U.S. Appl. No. 14/869,909, filed Sep. 29, 2015.
Notice of Allowance, dated Sep. 28, 2017, U.S. Appl. No. 14/869,909, filed Sep. 29, 2015.
Related Publications (1)
Number Date Country
20130103201 A1 Apr 2013 US
Continuations (1)
Number Date Country
Parent 12156621 Jun 2008 US
Child 13710325 US