Patent Grant
10306733
Intelligent lighting systems combine solid-state light sources, embedded sensors and controls, and low-cost pervasive networking to create an integrated illumination system which is highly responsive to its environment. Benefits of some or all such systems may include, but are not limited to, a much higher quality of light tailored specifically to user needs and significant energy savings, compared to legacy lighting system technologies.
In many environments illuminated by artificial light, significant amounts of ambient daylight may be present at certain times of the day. When sufficient levels of ambient light are present, intelligent lighting systems may reduce the amount of artificial light delivered in order to maintain consistent environmental lighting conditions and to save energy. The process of changing the amount of light emitted by a fixture in response to changes in ambient lighting conditions is known as “daylight harvesting.”
Conventional lighting fixtures are typically arranged in groups, each of which is on a single circuit. When a detector (or a person) senses that the ambient light level has risen above a predetermined threshold in a given part of the warehouse, the sensor (or person) triggers a switch that turns off an entire circuit. Similarly, if the ambient light level falls below a predetermined threshold, the circuit may be turned on to provide additional light.
Embodiments of the present invention include a lighting fixture to illuminate an environment and a corresponding method of illuminating the environment, such as a warehouse, a cold-storage facility, an office space, a retail space, an educational facility, an entertainment venue, a sports venue, a transportation facility, and a correctional facility. An exemplary lighting fixture includes a memory, an ambient light sensor, a processor communicatively coupled to the memory and the ambient light sensor, and a light source, such as a light-emitting diode (LED), communicatively coupled to the processor. The memory stores a first transfer function mapping first ambient light levels at a first position within the environment to corresponding second ambient light levels at a second position within the environment. The ambient light sensor measures an actual ambient light level at the first position within the environment. The processor determines: an expected ambient light level at the second position, based on the actual ambient light level measured at the first position and the first transfer function stored in the memory; and a change in a light output of the lighting fixture to provide a desired ambient light level at the second position, based at least in part on the expected ambient light level at the second position. And the light source generates the change in the light output of the lighting fixture so as to provide the desired ambient light level at the second position.
In certain embodiments, the first position is at the lighting fixture and the second position is at a task height within the environment (e.g., about 1 ft to about 6 ft from the floor of the environment).
The memory may be configured to store a plurality of transfer functions, including the first transfer function, each of which maps ambient light levels at the first position within the environment to corresponding ambient light levels at the second position within the environment. Each of these transfer functions may correspond to a different state of the environment. In such cases, the lighting fixture may also include a communications interface to accept a user input selecting the first transfer function from among the plurality of transfer functions and/or a state parameter sensor to provide a state parameter measurement used by the processor to select the first transfer function from among the plurality of transfer functions. For instance, the lighting fixture may include a real-time clock, communicatively coupled to the processor, that provides a timing signal used by the processor to select the first transfer function from among the plurality of transfer functions.
The processor may also be configured to determine a portion of the actual ambient light level provided by the lighting fixture (artificial light) and/or a portion of the actual ambient light level provided by one or more light sources (daylight) other than the lighting fixture. For example, the ambient light sensor may sense a wavelength of at least one spectral component of the actual ambient light level, and the processor may determining the amount of artificial light and/or daylight in the actual ambient light based on the wavelength sensed by the ambient light sensor.
The processor may control the light source to generate the change in the light output of the lighting fixture so as to provide the desired ambient light level at the second position. For instance, the processor may adjust the intensity, beam pattern, direction, color, and/or a color temperature of the light output.
An exemplary lighting fixture may also include an occupancy sensor, communicatively coupled to the processor, that senses a presence of at least one occupant within the environment and provides an occupancy signal indicative of the at least one occupant. The processor may select the desired ambient light level at the second position within the environment based at least in part on the occupancy signal. In addition, the occupancy sensor may sense a number of occupants within the environment, a location of the at least one occupant within the environment, and/or a motion of the at least one occupant within the environment.
Additional embodiments include a sensing module and corresponding method of calibrating a sensing module. (Such a sensing module may be integrated into or communicatively coupled to a lighting fixture or ballast interface.) An exemplary sensing module includes an ambient light sensor, a memory, and a processor communicatively coupled to the ambient light sensor and to the memory. The ambient light sensor generates an actual output representative of a change in an actual ambient light level of the environment caused by a change in a light output of at least one light source illuminating the environment. The memory stores a transfer function mapping ambient light levels of an environment to corresponding outputs of the ambient light sensor. And the processor determines (1) an expected output of the ambient light sensor based on the transfer function stored in the memory and the change in the ambient light level and (2) a difference between the actual output and the expected output. The processor also updates the transfer function stored in the memory based on the difference between the actual output and the expected output.
An exemplary sensing module may also include a communications interface, communicatively coupled to the processor, to transmit a signal that causes the at least one light source to generate the change in the light output. In addition, the processor may log, in the memory, the output, the expect output, and the change in the light output of the at least one light source illuminating the environment.
Yet another embodiment includes a ballast interface for a light-emitting diode (LED) lighting fixture and a corresponding method of operating a ballast interface. The ballast interface includes a power input, an LED driver circuit, a power meter operatively coupled to the power input, and a power management unit (PMU) communicatively coupled to the power meter. The power input receives alternating current (AC) power. The LED driver circuit transforms the AC power to power suitable for driving at least one LED in the LED lighting fixture. The power meter senses a waveform of the AC power. And the PMU adjusts the LED driver circuit in response to the waveform of the AC power.
In some cases, the power meter measures a phase angle, a power factor, and/or a noise level of the AC power. The PMU may determine a presence of at least one of a brownout and a lightning strike based on the waveform of the AC power. The PMU may a current drawn by the LED driver circuit to power the at least one LED in response to the waveform of the AC power. The PMU and/or the power meter may also store a representation of the waveform of the AC power in a memory.
For purposes of the present disclosure, the term “ambient light” refers to visible radiation (i.e., radiation whose wavelength is between about 450 nm and about 700 nm) that pervades a given environment or space. In other words, ambient light is the soft, indirect light that fills the volume of the environment and is perceptible to a person within the environment.
Similarly, the term “ambient light level” refers to the illuminance, or luminous flux on a surface per unit area. The illuminance is a measure of how much the incident light illuminates the surface, wavelength-weighted by the luminosity function to correlate with human brightness perception. Luminous flux may be measured in lux (lumens per square meter) or foot-candles.
The following U.S. published applications are hereby incorporated herein by reference:
U.S. Pat. No. 8,232,745, filed Apr. 14, 2009, and entitled “MODULAR LIGHTING SYSTEMS”;
U.S. Pat. No. 8,138,690, filed Jun. 25, 2010, and entitled “LED-BASED LIGHTING METHODS, APPARATUS, AND SYSTEMS EMPLOYING LED LIGHT BARS, OCCUPANCY SENSING, LOCAL STATE MACHINE, AND METER CIRCUIT”;
U.S. Pre-Grant Publication No. 2010-0296285-A1, published Nov. 25, 2010, filed Jun. 17, 2010, and entitled “SENSOR-BASED LIGHTING METHODS, APPARATUS, AND SYSTEMS EMPLOYING ROTATABLE LED LIGHT BARS”;
U.S. Pre-Grant Publication No. 2010-0301773-A1, published Dec. 2, 2010, filed Jun. 24, 2010, and entitled “LED-BASED LIGHTING METHODS, APPARATUS, AND SYSTEMS EMPLOYING LED LIGHT BARS OCCUPANCY SENSING, AND LOCAL STATE MACHINE”;
U.S. Pre-Grant Publication No. 2010-0302779-A1, published Dec. 2, 2010, filed Jun. 24, 2010, and entitled “LED-BASED LIGHTING METHODS, APPARATUS, AND SYSTEMS EMPLOYING LED LIGHT BARS, OCCUPANCY SENSING, LOCAL STATE MACHINE, AND TIME-BASED TRACKING OF OPERATIONAL MODES”;
U.S. Pre-Grant Publication No. 2010-0264846-A1, published Oct. 21, 2010, filed Jun. 28, 2010, and entitled “POWER MANAGEMENT UNIT WITH ADAPTIVE DIMMING”;
U.S. Pre-Grant Publication No. 2010-0295473-A1, published Nov. 25, 2010, filed Jun. 30, 2010, and entitled “LED LIGHTING METHODS, APPARATUS, AND SYSTEMS INCLUDING RULES-BASED SENSOR DATA LOGGING”;
U.S. Pre-Grant Publication No. 2010-0301768-A1, published Dec. 2, 2010, filed Jun. 30, 2010, and entitled “LED LIGHTING METHODS, APPARATUS, AND SYSTEMS INCLUDING HISTORIC SENSOR DATA LOGGING”;
U.S. Pre-Grant Publication No. 2010-0270933-A1, published Oct. 28, 2010, filed Jun. 30, 2010, and entitled “POWER MANAGEMENT UNIT WITH POWER METERING”;
U.S. Pre-Grant Publication No. 2012-0235579, published Sep. 20, 2012, filed Mar. 20, 2012, and entitled “METHODS, APPARATUS AND SYSTEMS FOR PROVIDING OCCUPANCY-BASED VARIABLE LIGHTING”;
U.S. Pre-Grant Publication No. 2012-0143357, published Jun. 7, 2012, filed Nov. 4, 2011, and entitled “METHOD, APPARATUS, AND SYSTEM FOR OCCUPANCY SENSING”;
WO 2012/061709, published May 10, 2012, filed Nov. 4, 2011, and entitled “METHOD, APPARATUS, AND SYSTEM FOR OCCUPANCY SENSING”; and
WO 2012/129243, published Sep. 27, 2012, filed Mar. 20, 2012, and entitled “METHODS, APPARATUS AND SYSTEMS FOR PROVIDING OCCUPANCY-BASED VARIABLE LIGHTING.”
It should be appreciated that all combinations of the foregoing concepts and additional concepts discussed in greater detail below (provided such concepts are not mutually inconsistent) are contemplated as being part of the inventive subject matter disclosed herein. In particular, all combinations of claimed subject matter appearing at the end of this disclosure are contemplated as being part of the inventive subject matter disclosed herein. It should also be appreciated that terminology explicitly employed herein that also may appear in any disclosure incorporated by reference should be accorded a meaning most consistent with the particular concepts disclosed herein.
The skilled artisan will understand that the drawings primarily are for illustrative purposes and are not intended to limit the scope of the inventive subject matter described herein. The drawings are not necessarily to scale; in some instances, various aspects of the inventive subject matter disclosed herein may be shown exaggerated or enlarged in the drawings to facilitate an understanding of different features. In the drawings, like reference characters generally refer to like features (e.g., functionally similar and/or structurally similar elements).
Following below are more detailed descriptions of various concepts related to, and embodiments of, inventive systems, methods and apparatus for intelligent lighting related to daylight harvesting, temperature monitoring, and power analysis. It should be appreciated that various concepts introduced above and discussed in greater detail below may be implemented in any of numerous ways, as the disclosed concepts are not limited to any particular manner of implementation. Examples of specific implementations and applications are provided primarily for illustrative purposes. For instance, although
In many environments illuminated by intelligent lighting systems, real-time collection of ambient temperature data at many points provides valuable insight into the performance of other building systems, such as HVAC systems, machinery of various sorts, and high-volume chiller systems for cold storage environments. Intelligent lighting systems with integrated temperature sensing functionality can provide this real-time data stream to facilitate analysis, monitoring, and adjustment of these other building systems.
Many intelligent lighting systems also feature the ability to measure and analyze the energy used by the various parts of the lighting system. This measurement may occur at the facility level, at the level of an individual electrical circuit within the facility, or at the level of an individual light fixture within an electrical circuit. Measuring characteristics of energy and power used by individual light fixtures provides significant end-user benefits in both accuracy and granularity of analysis.
Embodiments of the present disclosure include sn apparatus for determining a first ambient light level at a first position (e.g., about one foot to about six feet from a floor). In an illustrative embodiment, the apparatus includes a sensor to measure a second ambient light level at a second position (e.g., at a lighting fixture) and a processor, which is operably coupled to the sensor, to determine the first ambient light level based on the second ambient light level. The processor may be further configured to determine a difference between the second ambient light level and a desired light level and, optionally, to determine a change in an illumination level to bring the first ambient light level into coincidence with the desired light level. In at least one example, the processor is further configured to adjust an illumination level to bring the first ambient light level into coincidence with the desired light level and to drive a light source, which is operably coupled to the processor, to provide illumination at the illumination level. An exemplary apparatus may also include a communications interface that is operably coupled to the processor and configured to provide an indication of the second ambient light level to a lighting fixture or another processor.
Other disclosed embodiments include methods of determining a difference between a first ambient light level and a desired ambient light level. Exemplary methods include measuring a second ambient light level at a second position, determining the first ambient light level based on the second ambient light level, and determining a difference between the first ambient light level and the desired light level. Further exemplary methods may also include adjusting an illumination level to bring the first ambient light level into coincidence with the desired light level.
Intelligent Lighting Fixtures
The LED light bars 120 are mounted to a frame 102 that also holds an ambient light sensor 110, a ballast interface or power management unit (PMU) 130, an occupancy sensor 140, and one or more status LEDs 190, which indicate the lighting fixture's current operating mode (e.g., active mode, sleep mode, service mode), whether or not the lighting fixture 100 needs to be serviced, whether the lighting fixture 100 is communicating with another device, etc. As shown in
Each of these components is communicatively coupled to the PMU 130, e.g., via an appropriate bus or electrical connection, and may be a modular component that can be “hot swapped” or replaced in the field or integrated into either the lighting fixture 100 or the PMU 130. Alternatively, one or more of these components may be packaged separately and installed apart from the lighting fixture 100 or the PMU 130 and communicatively coupled to the lighting fixture 100 or PMU 130, e.g., via a wireless interface.
As described in greater detail below, the PMU 130 controls the illumination emitted by the LEDs on the LED light bars 120.
The PMU 130 logs measurement signals (data) in the memory 134 from the ambient light sensor 110, occupancy sensor 140, hardware power meter 150, communications interface 160, and real-time clock 170 and may cause the state machine to transition from one state to another state based on these measurement signals. For instance, the processor 132 may cause the light output of the LED light bars 120 to change in response to inputs from the ambient light sensor 110, occupancy sensor 140, temperature sensor 180, and/or real-time clock 170 according to the instructions stored in the memory 134. These components, their respective functions, and the other components shown in
Ambient Light Sensors
The ambient light sensor 110 may be a photocell (e.g., an Intersil™ ISL29102 Low Power Ambient Light-to-Voltage Non-Linear Converter) that monitors the level of ambient light at the sensor position or sensor height, Ls, emits an ambient light signal whose value (e.g., amplitude or phase), Vs, represents the amount of detected ambient light. The ambient light sensor 110 may include one or more optical elements (e.g., a lens) that direct ambient light onto one or more photosensitive elements, which transduce incident photons into a photocurrent, voltage, change in resistance, or other measureable electrical quantity. The ambient light sensor 110 may also include a circuit that provides automatic gain control—that is, the circuit controls the proportionality of the signal Vs to the measured ambient light level Ls. If desired, the sensor gain can be tuned (either manually, automatically, or via remote control), e.g., to increase or decrease the ambient light sensor's sensitivity to ambient light. Similarly, the sensor circuit may include an offset that can be increased or decreased, e.g., to account for changes in fixed-pattern background illumination or noise.
In one example, an illustrative ambient light sensor 110 may employ processor-based tuning of the light sensor gain, offset, and threshold characteristics for improving the accuracy and precision of ambient light measurement. In some cases, the ambient light sensor 110 may be tuned after installation in a target environment to account for specific ambient light characteristics of that environment, such as the reflectivity of various surfaces, location and brightness of windows, skylights, or other light sources, or desired ambient light levels at various locations in that environment. The tuning process may be automated, or may involve substantial manual interaction. The tuning process may be conducted via a software user interface or via a special-purpose handheld device. The tuning process may be a one-time operation, or may be repeated (manually or automatically) to account for changes in the target environment.
An exemplary ambient light sensor 110 may respond to light in the visible, near infrared, mid-infrared, and far-infrared portions of the electromagnetic spectrum. For instance, the light sensor 110 may include two active regions: a first active region that senses visible light and a second active region that senses infrared light. Light sensors which measure both visible light and infrared light may output the visible and infrared readings separately to allow an intelligent lighting controller to distinguish between the ambient light provided by the sun (which contains a significant infrared component) and the light provided by an artificial light source (which may contain little or no infrared component). These readings may allow a controller (e.g., the state machine implemented in the PMU 130) to maintain target illumination levels and prevent undesired feedback loops in the PMU 130 from driving the daylight harvesting system as explained below.
Occupancy Sensors
The occupancy sensor 140 monitors the illuminated environment for the presence of people, vehicles, etc., and transmits an occupancy signal to the PMU 130 when it detects a person, vehicle, moving object, etc. in the illuminated environment. As understood by those of skill in the art, the occupancy sensor 140 may be a passive infrared (PIR) device that operates by sensing infrared radiation emitted by a person (or animal) in the environment. The occupancy sensor 140 may also emit radio-frequency or ultrasonic pulses and detect echo pulses reflected from objects or people in the environment. The occupancy sensor 140 may be configured to detect a person's location within the environment. It may also sense the number of people within the environment, their respective locations within the environment, and their respective trajectories within or through the environment.
As shown in
When the occupancy sensor 140 detects an occupancy event (e.g., a person entering a previously unoccupied room), it may increase the amplitude of its output (the occupancy signal). The processor 132 receives this occupancy signal and treats it as a state parameter indicative of the environment's occupancy state (e.g., occupied or unoccupied). If the occupancy signal indicates that the environment is occupied, then the processor 132 may send a signal to one or more LED drivers 122, which respond to the signal by changing the amount of light emitted by one or more LED light bars 120. As described below, the processor 132 may determine the desired output of the LED light bars based at least in part on a transfer function selected based on the occupancy signal itself as described in greater detail below.
The processor 132 may continue transmitting a “high” occupancy signal to the LED drivers 122 for as long as the occupancy sensor 110 detects an occupancy event, or it may send a second signal to the LED drivers 122 in response to detection of another change in occupancy (e.g., when the occupancy event ends). Alternatively, the processor 132 may simply send an occupancy signal periodically for as long the occupancy state of the environment does not change. At this point, the lighting fixture 100 enters a delay or timeout period, based on instructions stored in the memory 134 and timing data from the clock 170, during which the LED light bars 120 remain in the active state (or possibly transition to a state of intermediate activity, e.g., 50% illumination). Once the delay period has elapsed, as indicated by the change in state of a signal from the processor 132 and/or the LED driver 122, the LED light bars 120 enter an inactive state (e.g., they turn off or emit light at a very low level). As described below, the processor 132 may adjust the delay period and/or the light levels based on its analysis of logged sensor data.
Additional State Parameter Sensors
The lighting fixture 100 may also include additional state parameter sensors, each of which may be integrated into the PMU 130 or communicatively coupled to the PMU 130 via an appropriate communications interface. For instance, the lighting fixture 100 and/or the PMU 130 may include one or more temperature sensors 180 to sense the temperature of the lighting fixture 100, its components (e.g., the LEDs in the LED light bars 120), and/or the ambient temperature (the temperature of the air surrounding the lighting fixture 100). The lighting fixture 100 and/or the PMU 130 may also include an radio-frequency identification (RFID) sensor (not shown) for tracking RFID tags, a magnetometer, a camera, and any other sensor suitable for sensing a state of the environment. These additional sensors (not shown) may be coupled to the processor 132 via one or more digital input/output ports 164 and/or one or more analog input ports 166 or integrated into the lighting fixture 100 and/or the PMU 130.
The lighting fixture 100 also includes a real-time clock 170 that can also, optionally, be integrated into the PMU 130. The real-time clock 170 provides timing data (e.g., time-stamp information) on an as needed or periodic basis to the processor 132, which may store or tag the sensor data (including the ambient light and occupancy data) in the memory 134 with time stamps to indicate when the data was collected. In addition, the processor 132 may treat the time stamps as state parameters that indicate the time of day, day of the week, or day of the year. If the processor 132 determines from the time stamp that it is a weekend day or a holiday, it may determine that, for a given occupancy condition, the ambient light level should be lower that the ambient light level for a weekday at the same time. It may also determine that an intruder is present or that a security breach has occurred based on occupancy event data detected when the facility is closed. The real-time clock 170 may also be used to time or coordinate the sensor/lighting fixture delay period and to synchronize the PMU 130 to other devices, systems, and components on the same network and/or within the same environment.
Ambient Light, Occupancy Sensor Data, and Daylight Harvesting State Machines
The PMU 130 may use ambient light sensor data and/or occupancy sensor data to advance a software-configurable state machine governing the light fixture's behavior. More specifically, the PMU 130 may employ ambient light and occupancy measurements to “harvest” light from other sources, including the sun, to reduce the lighting fixture's light output and energy consumption. As part of this process, the PMU 130 may determine the light output from the light bars 120 using a “fixture-to-task” transfer function that maps the ambient light levels measured at the ambient light sensor 110 to the ambient light levels at “task position” or “task height,” which correspond to the position or height at which a person working in the environment engages in tasks benefiting from illumination. For instance, task height may be the height at which a person uses his or her hands at a desk, in/on a rack, or holds a clipboard. In a warehouse, cold-storage facility, or office environment, task position or task height may about 1 ft to about 6 ft from the ground, e.g., about 3, 4, or 5 ft. An environment may include multiple task heights or task positions; for example, in a warehouse full of racks, there may be a different task position associated with each rack in the warehouse and/or each rack in a shelf.
In many situations, the ambient light sensor 110 may be located some distance from the task position or task height. For instance, the ambient light sensor 110 may be suspended from the ceiling as part of the fixture 100 in a high-bay or mid-bay installation or mounted to the wall as part of a separate sensor unit or PMU 130. As a result, the ambient light level at the sensor may be different than the ambient light level at the task position/height. To compensate for this, the PMU 130 may use a “fixture-to-task” transfer function, stored in the memory 134 (e.g., as a look-up table), that maps the measured ambient light signal from the ambient light sensor 110 to the estimated ambient light level at task position/height. The PMU 130 uses this transfer function, together with information about the lighting fixture's light output, to determine the amount of daylight illuminating the environment and the change in the lighting fixture's light output necessary to achieve a desired ambient light level at task height.
The PMU 130 may also update or calibrate the fixture-to-task transfer function based on closed-loop feedback from the ambient light sensor 110 and the PMU 130. In some cases, for example, the processor 132 may also log ambient light sensor data and information about the lighting fixture's light output in the memory 134 on a periodic basis to track changes in the environment's reflectivity over days, weeks, months, or years. It may also log ambient light sensor data in the memory 134 immediately before and after a change in the lighting fixture's light output. From these measurements, the PMU 130 may determine that the task-position ambient light level has not increased by the desired amount and may change the lighting fixture's light output and the transfer function's scaling accordingly.
Consider, for example, a lighting fixture 100 that illuminates the warehouse environment shown in
Variations in the amount of light coming through the skylights 14 affects the ambient light level at task height Lf, which may be about three feet above the floor 10. Task height represents the height at which a worker in the warehouse performs day-to-day tasks, including inspecting items (and tags on items), moving items on and off shelves on the racks, turning switches on and off, and working with his or her hands. Obstructions scattered throughout the warehouse may attenuate, scatter, or reflect light from skylights 14, so the ambient light level at task height may not necessarily be the same as the ambient light level at other distances from the floor. The ambient light level at task position/height may also vary with (lateral) position on the floor (distance from a rack 12/skylight 14/window). For instance, a rack 12 may shield one area of the warehouse floor 10 from light coming in through a particular skylight 14, but not another area.
One or more intelligent lighting fixtures 100 illuminate the warehouse environment. The lighting fixtures 100 may be mounted from the ceiling of the warehouse and arrayed in a semi-regular grid (e.g., along aisles between racks) as shown in
In operation, the PMU 130 in each lighting fixture 100 measures the ambient light level on a continuous or periodic basis and senses the presence (or absence) of occupants in the environment. Each PMU 130 also monitors aspects of the light emitted by its fixture 100, such as the intensity, direction, and pattern of the beam(s) projected by the LED light bars 120 into the environment. For instance, the PMU 130 may compute the intensity of the emitted beam based on a measurement of the power drawn by the LED driver circuit 122, the fixture's temperature and age, and information stored in the memory 134 about the operating characteristics of the LED light bars 120. The PMU 130 uses this information, along with ambient light level measurements and calibration data about the ambient light sensor 110, to determine what fraction of the measured ambient light is light emitted by the LED light bars 120 and what fraction comes from other light sources, such as the sun. It may also measure the power spectral density of the ambient light to determine how much sunlight is present, if any.
If the PMU 130 determines that the amount of sunlight is increasing, it may cause the lighting fixture 100 to emit less light so as to maintain a desired ambient illumination level. Similarly, if the PMU 130 determines that the amount of sunlight is decreasing, it may cause the lighting fixture 100 to emit more light so as to maintain the desired ambient illumination level. The PMU 130 may also cause the lighting fixture 100 to change the beam pattern in response to an indication that one portion of the environment is brighter than another portion of the environment, e.g., because the sun is shining through one window or skylight but not another. For instance, the PMU 130 can selectively turn on or off LEDs in the LED light bars 120; cause some LEDs to emit more light than others; modulate the transparency, focus, or pattern of an electro-active optical element (e.g., a spatial light modulator) placed over some or all of the LEDs in a light bar 120; or actuate a motor that rotates one or more of the LED light bars 120.
Occupancy-Based State Machine Employing a Fixture-to Task Transfer Function
In at least one embodiment, an inventive PMU 130 implements an occupancy-based state machine that uses the “fixture-to-task” transfer function described above to provide a desired task-position ambient light level for a given occupancy state. Each occupancy state may have associated with it a desired task-position ambient light level, or target illumination level. In operation, the occupancy sensor 140 detects a change in occupancy state and reports the change to the PMU 130, which advances the state machine from one state to another (e.g., unoccupied to occupied) based on the change. (It may also advance the state machine based on signals from a timer, such as the real-time clock 170.) The PMU 130 determines the target level for the new state and servos the lighting fixture's light output using ambient light sensor data and the “fixture-to-task” transfer function to compensate for changes in daylight levels, environmental reflectivity, etc.
The sensor tuning software module 306 may also adjust the gain, offset, and threshold in response to measurements that map the ambient light level Lf at task height to the instantaneous value Vs of the digitized signal 115. For instance, the sensor tuning software module 306 may change the sensor gain in response to changes in the sensor's performance or changes in the environment. Painting the walls of the environment or moving boxes on the racks 12 may cause the reflectivity to increase or decrease by a known or measureable amount. Tuning the sensor gain, offset, and/or threshold compensates for this change in reflectivity.
The lighting fixture 100 remains in the active occupied state 356 so long as the environment remains occupied. In the active occupied state 356, the control loop 308 may servo the light output setting about a desired (e.g., constant) value of the ambient light level Lf at task height using proportional-integrative-derivative (PID) control with gain coefficients tuned to provide the desired response. Those of skill in the art will readily appreciate that other forms of control (e.g., proportional control or proportional-derivative control) may be employed as well.
In some environments, and with some sensors 110, this can be accomplished when the control loop 408 that implements a “laggy follower,” i.e., PID control where the “proportional” gain coefficient is equal to the reciprocal of the error term. The control loop 308 may also provide an “asymmetric” response to changes in the ambient light levels: it may increase the light output setting quickly in response to a decrease in the ambient light level and decrease the light output gradually in response to an increase in the ambient light level. The type of response may also vary with user commands, the time of day, the time of year, the weather, the presence or absence of people in or near the illuminated environment, etc. Similarly, the desired ambient light level at task height Lf may be constant or may vary in response to user commands, the time of day, the time of year, the weather, the presence or absence of people in or near the illuminated environment, etc.
When occupancy is no longer detected (358), the control loop 308 transitions the lighting fixture 100 from the active occupied state 356 to an active unoccupied state 360, e.g., by starting a sensor delay timer 362 controlled by the real-time clock 170. The lighting fixture 100 remains in the active unoccupied state 360 until the sensor delay timer 362 elapses, in which case the control loop 308 transitions the lighting fixture 100 to the inactive state 352, or the occupancy sensor 140 detects another occupancy event 354, in which case the control loop 308 transitions the lighting fixture 100 to the active occupied state 356.
Transfer Functions Mapping Ambient Light Levels to Light Outputs
As explained above, the PMU 130 uses the fixture-to-task transfer function to map the measured ambient light level to an estimated ambient light level, and a state-to-target transfer function to map the fixture's current operating state to a desired ambient light level for each state of the environment. These transfer functions may be stored in look-up tables as one or more combinations of measured ambient light level(s), current lighting fixture light output(s), and change(s) in lighting fixture light output to achieve a particular ambient light level. In one example, the PMU 130 determines the amount of light provided by other sources (the amount of “daylight”) by subtracting a scaled or calibrated measure of the lighting fixture's light output from the measured ambient light level. It may also determine the amount of daylight by measuring the power spectral density of the ambient light and decomposing the measured power spectral density into the weighted superposition of the power spectral densities of the sun and the lighting fixture.
The PMU 130 also determines the target ambient light level, or desired illumination level, based on an occupancy signal from the occupancy sensor 140 and, optionally, time values from the real-time clock 170 or another time source. For instance, the target illumination level may be highest during daytime hours when the environment is occupied, high during nighttime hours when the environment is occupied, and low when the environment is unoccupied. If the target ambient light level is higher than the measured ambient light level, or if the amount of daylight decreases, the PMU 130 increases the light output of the lighting fixture 100. If the target ambient light level is lower than the measured ambient light level, or if the amount of daylight increases, the PMU 130 decreases the light output of the lighting fixture 100.
The PMU 130 also updates the target ambient light level if the environment's state changes, e.g., according to the state diagram 350 in
In the occupancy-based state machine sub-process 410, the occupancy sensor 140 senses or measures the occupancy state 414 of the environment. The PMU 130 combines this occupancy data with timer data 412 from the real-time clock to advance an operating state machine 416 from one state to another according to operating rules stored in the memory 134. (The PMU 130 may also use information about temperature, time of day, day of the week, operational status of the lighting fixture, etc. to advance the state machine.) For instance, the PMU 130 may receive an occupancy signal from the occupancy sensor 140 indicating that the environment has transitioned from an unoccupied state to an occupied state. The PMU 130 determines the environment's operating state 417 and selects a target illumination level 419 at task height corresponding to the operating state 417 from a look-up table (LUT) 418 stored in the memory 134.
In the ambient light level sub-process 420, which may occur before, during, or after execution of the state machine sub-process 410, the PMU 130 receives a measurement of the ambient light level 422 (possibly in hexadecimal form) from the ambient light sensor 110 and records this measurement in the memory 134. (The PMU 130 may log the state parameters in the memory 134 as well.) It maps this measured ambient light level at one location to the estimated ambient light level at the task location according to the fixture-to-task transfer function 424, possibly by determining the amount of daylight as well. This mapping yields a predicated task-height ambient light level 426, which the PMU compares to the target illumination level 419 at task height (comparison 450).
In the adjustment sub-process 430, which may run continuously or iteratively (e.g., periodically), the PMU 130 calculates the error 432 between the predicted ambient light level 434 at task height and the target illumination level 419 at task height (comparison 450). It uses a control loop 434, such as a proportional-integral-derivative (PID) control loop, to adjust the output of the lighting fixture 100 (step 436) so as to provide the desired amount of illumination. As understood by those of skill in the art, the PID control loop 434 generates a weighted sum of the present error, the accumulation of past errors, and a prediction of future errors to generate an adjustment amount to the lighting fixture's light output so as to keep the measured ambient light level 322 at a level corresponding to the target illumination level 419 at task height.
The “learning” sub-process 440 involves monitoring the inner control loop (sub-processes 420 and 430) (step 442) and updating the fixture-to-task transfer function (step 444), e.g., using logged sensor data and/or the calibration routines described below. In this sub-process 440, the PMU 130 compares the measured ambient light level 422 to the target ambient light level 419, e.g., on a continuous, periodic, or intermittent basis. If the PMU 130 determines that the changed ambient light level matches the target ambient light level, it resumes monitoring the ambient light level and the occupancy. Otherwise, if the PMU 130 determines that the changed ambient light level does not match the target ambient light level, it adjusts the transfer function (step 444) to compensate for the discrepancy between the measured and target values. For example, if the changed ambient light level is lower than the target ambient light level, the PMU 130 may adjust the transfer function so as to increase the lighting fixture's light output for the state of the environment, the amount of daylight, and the measured ambient light level. Likewise, if the changed ambient light level is higher than the target ambient light level, the PMU 130 may adjust the transfer function so as to decrease the lighting fixture's light output for the state of the environment, the amount of daylight, and the measured ambient light level. The PMU 130 may use the sensor measurements logged in the memory 134 to determine how much to change the transfer function and, optionally, to determine whether or not the discrepancy between measured and target light levels is spurious. If the discrepancy is spurious, the PMU 130 may not adjust the transfer function.
The ambient light level measurements 422 and occupancy state measurements 412 may occur continuously or at discrete intervals. For instance, they may occur periodically (e.g., once per second), aperiodically, and/or on demand. They may occur more frequently when the environment is likely to be occupied, e.g., during operational hours. They may be synchronized or may occur asynchronously (e.g., the ambient light level measurements 422 may occur more frequently than the occupancy state measurements 412).
Mapping Sensor Readings to Ambient Light Levels at Task Height
Referring again to
Plotting the ambient light level Ls at the sensor versus the ambient light level Lf at task height yields the curve shown in
Manual Transfer Function/Ambient Light Sensor Calibration
In some cases, the relationship shown in
Automatic Transfer Function/Ambient Light Sensor Calibration
Plotting these measurements (along with many other before-and-after measurements) yields the scatter plot shown in
The relationship between sensor readings Vs and light output settings represented by the curve 702 in
The state machine 300 may continue to measure and record pairs of sensor readings Vs as the lighting fixture operates, e.g., on a periodic basis, an as-needed or as-desired basis, or even every time the lighting output setting changes. The state machine 300 can use these additional measurements to update the sensor reading/light output setting relationship represented by the curve 702 in
The state machine 300 may utilize ambient light sensor data alone or combined with occupancy sensor data; for instance, it may be a software-configurable state machine 300 that governs the behavior of one or more individual light fixtures 100 based on a combination of occupancy and ambient light data. This software-configurable control may, for example, allow a user to specify one daylight harvesting profile to be used when an occupancy sensor indicates the presence of a person or vehicle in an area of interest and another daylight harvesting profile to be used when the occupancy sensor indicates that the area is empty or inactive. In this example, the “inactive” daylight harvesting profile may be configured to save more energy than the “active” profile. If no occupancy sensor data is available, a lighting control system which uses ambient light sensor data may allow a user to specify a target illumination level as well as maximum and minimum fixture dimming levels, among other user-specifiable operating parameters.
Performance with Transfer-Function-Based Daylight Harvesting
Fault Detection and Protection with a Power Management Unit
An exemplary intelligent light fixture 100 may include an integrated power and energy measurement subsystem that provides a detailed record of power and energy usage over time. This power and energy usage may be further broken down by fixture subsystem or individual driver output channels. It may also represent power and energy usage for the fixture 100 as a whole. The power and energy management subsystem may also measure characteristics of the AC power input to the light fixture, including but not limited to: phase angle, noise on the AC line, or power factor. The power and energy management subsystem may log measurements in memory onboard the light fixture, or transmit measurements to a remote monitoring system via wired or wireless network.
Referring again to
Alternatively, the lighting fixture 100 (and occupancy sensing unit 102) may draw power from an external DC power supply, such as a rechargeable battery. Such an embodiment may include one or more DC-DC power converters coupled to a DC power input and configured to step up or step down the DC power as desired or necessary for proper operation of the electronic components in the lighting fixture 100 (and occupancy sensing unit 102). For instance, the DC-DC power converter(s) may supply DC voltages suitable for logic operations (e.g., 5 VDC) and for powering electronic components (e.g., 12 VDC). In such embodiments, the power meter 150 may
The processor 132 may use information derived from the power meter's measurements to identify various fault conditions and to protect the lighting fixture 100 and its components from some or all of these fault conditions. The power meter 150 may provide various power-related measurements to the microcontroller, including but not limited to: the input AC voltage or current waveforms, the current or voltage waveforms associated with energy storage capacitors, the output pulse duration of a buck or boost power conversion circuit, or the voltage across and current through a series-wired string of LEDs. For example, the power meter 150 may sample the AC waveform received from the AC power input 156 at a rate equal to or greater than the Nyquist frequency of the AC waveform (e.g., a sampling rate of 120 Hz or higher for 120 VAC at 60 Hz). The processor 132 may process these measurements to produce a calculated power measurement corresponding to each of several LED driver outputs, to an entire light fixture, or to any or all of several electrical subsystems within a fixture. The processor 132 may also log some or all of these samples in the memory 134 for later analysis, e.g., to determine energy usage, lighting fixture performance, component performance, and/or performance of the corresponding circuit in the AC power grid.
The processor 132 may also detect undesired fluctuations in the input voltage in real-time. The processor 132 may react to these fluctuations in such a way as to prevent permanent damage to the fixture's power controller circuit, LEDs, or other electrical subsystems. The processor 132 may also be configured to detect any of several possible failure modes for the one or more strings of output LEDs and safely react to the failure modes in a way that prevents permanent damage to the fixture's power controller circuit, LEDs, or other electrical subsystems.
For instance, the processor 132 may determine whether the AC waveform's amplitude exceeds or falls below a predetermined threshold or exhibits a predetermined pattern or profile. If the processor 132 senses that the AC waveform's amplitude is drifting towards or has drifted below a predetermined threshold (e.g., 60 Vpp), the processor 132 may determine that a brownout is occurring. In such a case, the processor 132 may reduce power consumption by high-voltage components, such as the LED light bars 120, so to prevent these components from drawing too much current as the input voltage falls. Similarly, if the processor 132 senses a sudden voltage spike, it may determine that a lightning strike has occurred and shunt power and/or turn off one or more components in the PMU 130 or lighting fixture 100. The processor 132 may also detect and respond to indications that one or more components within the PMU 130 or fixture 100 is malfunctioning.
Independent Power Management Units and Communications Interfaces
As shown in
The ambient light sensor 110 and the occupancy sensor 140 can also serve as receivers for modulated infrared data from remote control devices, infrared beacons, or other data transmitters. Light sensors may also serve as receivers for modulated infrared or visible light data. This data may be transmitted from a handheld device used in the sensor tuning process. This data may also be transmitted from an infrared or visible light beacon device attached to persons, vehicles, or other objects in the environment to facilitate tracking of these objects as they move within the environment.
Alternative embodiments of the PMU may physically be detached or separated from the lighting fixture. For instance, the PMU may be packaged and deployed in the environment as an independent unit that includes integrated sensors (e.g., ambient light level sensor and/or occupancy sensor) and a wired or wireless communications interface. Alternatively, or in addition, the PMU may be communicatively coupled to other PMUs, other light fixtures (including “dumb” light fixtures), and/or other independent sensors distributed throughout the environment. Such an independent PMU may detect ambient light levels and state parameter information from integrated sensors and/or from communicatively coupled sensors and process this data as described above. For instance, an independent PMU may be communicatively coupled to and control several lighting fixtures disposed to illuminate an environment. The PMU may also be retrofit to existing light fixtures, such as high-bay lighting fixtures common in many warehouses and cold-storage facilities.
Temperature-Based Intelligent Lighting
Inventive aspects of the temperature monitoring systems include, but are not limited to, light fixtures 100 with integrated sensors (e.g., temperature sensor 180 in
An intelligent light fixture 100 may include one or more integrated temperature sensors 180 coupled to or integrated into its power management unit (PMU 130 in
In some cases, it may be desirable to monitor temperature in an environment at a location physically separated from any light fixture 100 deployed in the environment. In these cases, the temperature sensor may be contained in a remote module capable of communicating via a wireless or wired network with the PMU 130, lighting fixture 100, and/or other devices in an intelligent lighting system. The remote temperature sensor may be battery powered or may operate off of an AC or DC power connection.
The PMU 130 may record temperature data (e.g., from temperature sensor 180) in the memory 134 for real-time analysis and for post-processing and historical data analysis. The temperature data may be recorded in a database (e.g., local memory 134 or remote memory accessible via the communications interface 160), and may be annotated with the location where the reading was taken and the time at which it was taken. The temperature data may be analyzed to remove spurious readings, or to flag excessively high or low readings for further processing or response. The temperature data may be displayed as a time-based graph, or as a two-dimensional representation of the environmental layout with a temperature data overlay. Other building systems, including but not limited to HVAC units, chillers, blowers, and heaters, may be configured to act on real-time temperature data or alerts generated by an intelligent lighting system equipped with temperature sensors. Alternatively, the temperature data collected by the intelligent lighting system (PMU 130) may be exported in raw or processed form to control systems responsible for managing these other building systems for the other building system control systems to analyze. Based on temperature data it may also be possible to analyze and create visual representations of airflow patterns within a facility, allowing for optimized operation of HVAC and other related building systems.
While various inventive embodiments have been described and illustrated herein, those of ordinary skill in the art will readily envision a variety of other means and/or structures for performing the function and/or obtaining the results and/or one or more of the advantages described herein, and each of such variations and/or modifications is deemed to be within the scope of the inventive embodiments described herein. More generally, those skilled in the art will readily appreciate that all parameters, dimensions, materials, and configurations described herein are meant to be exemplary and that the actual parameters, dimensions, materials, and/or configurations will depend upon the specific application or applications for which the inventive teachings is/are used. Those skilled in the art will recognize, or be able to ascertain using no more than routine experimentation, many equivalents to the specific inventive embodiments described herein. It is, therefore, to be understood that the foregoing embodiments are presented by way of example only and that, within the scope of the appended claims and equivalents thereto, inventive embodiments may be practiced otherwise than as specifically described and claimed. Inventive embodiments of the present disclosure are directed to each individual feature, system, article, material, kit, and/or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits, and/or methods, if such features, systems, articles, materials, kits, and/or methods are not mutually inconsistent, is included within the inventive scope of the present disclosure.
The above-described embodiments can be implemented in any of numerous ways. For example, the embodiments may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers.
Further, it should be appreciated that a computer may be embodied in any of a number of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. Additionally, a computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital Assistant (PDA), a smart phone or any other suitable portable or fixed electronic device.
Also, a computer may have one or more input and output devices. These devices can be used, among other things, to present a user interface. Examples of output devices that can be used to provide a user interface include printers or display screens for visual presentation of output and speakers or other sound generating devices for audible presentation of output. Examples of input devices that can be used for a user interface include keyboards, and pointing devices, such as mice, touch pads, and digitizing tablets. As another example, a computer may receive input information through speech recognition or in other audible format.
Such computers may be interconnected by one or more networks in any suitable form, including a local area network or a wide area network, such as an enterprise network, and intelligent network (IN) or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks.
The various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages and/or programming or scripting tools, and also may be compiled as executable machine language code or intermediate code that is executed on a framework or virtual machine.
In this respect, various inventive concepts may be embodied as a computer readable storage medium (or multiple computer readable storage media) (e.g., a computer memory, one or more floppy discs, compact discs, optical discs, magnetic tapes, flash memories, circuit configurations in Field Programmable Gate Arrays or other semiconductor devices, or other non-transitory medium or tangible computer storage medium) encoded with one or more programs that, when executed on one or more computers or other processors, perform methods that implement the various embodiments of the invention discussed above. The computer readable medium or media can be transportable, such that the program or programs stored thereon can be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above.
The terms “program” or “software” are used herein in a generic sense to refer to any type of computer code or set of computer-executable instructions that can be employed to program a computer or other processor to implement various aspects of embodiments as discussed above. Additionally, it should be appreciated that according to one aspect, one or more computer programs that when executed perform methods of the present invention need not reside on a single computer or processor, but may be distributed in a modular fashion amongst a number of different computers or processors to implement various aspects of the present invention.
Computer-executable instructions may be in many forms, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.
Also, data structures may be stored in computer-readable media in any suitable form. For simplicity of illustration, data structures may be shown to have fields that are related through location in the data structure. Such relationships may likewise be achieved by assigning storage for the fields with locations in a computer-readable medium that convey relationship between the fields. However, any suitable mechanism may be used to establish a relationship between information in fields of a data structure, including through the use of pointers, tags or other mechanisms that establish relationship between data elements.
Also, various inventive concepts may be embodied as one or more methods, of which an example has been provided. The acts performed as part of the method may be ordered in any suitable way. Accordingly, embodiments may be constructed in which acts are performed in an order different than illustrated, which may include performing some acts simultaneously, even though shown as sequential acts in illustrative embodiments.
All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and/or ordinary meanings of the defined terms.
The indefinite articles “a” and “an,” as used herein in the specification and in the claims, unless clearly indicated to the contrary, should be understood to mean “at least one.”
The phrase “and/or,” as used herein in the specification and in the claims, should be understood to mean “either or both” of the elements so conjoined, i.e., elements that are conjunctively present in some cases and disjunctively present in other cases. Multiple elements listed with “and/or” should be construed in the same fashion, i.e., “one or more” of the elements so conjoined. Other elements may optionally be present other than the elements specifically identified by the “and/or” clause, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, a reference to “A and/or B”, when used in conjunction with open-ended language such as “comprising” can refer, in one embodiment, to A only (optionally including elements other than B); in another embodiment, to B only (optionally including elements other than A); in yet another embodiment, to both A and B (optionally including other elements); etc.
As used herein in the specification and in the claims, “or” should be understood to have the same meaning as “and/or” as defined above. For example, when separating items in a list, “or” or “and/or” shall be interpreted as being inclusive, i.e., the inclusion of at least one, but also including more than one, of a number or list of elements, and, optionally, additional unlisted items. Only terms clearly indicated to the contrary, such as “only one of” or “exactly one of,” or, when used in the claims, “consisting of,” will refer to the inclusion of exactly one element of a number or list of elements. In general, the term “or” as used herein shall only be interpreted as indicating exclusive alternatives (i.e. “one or the other but not both”) when preceded by terms of exclusivity, such as “either,” “one of,” “only one of,” or “exactly one of.” “Consisting essentially of,” when used in the claims, shall have its ordinary meaning as used in the field of patent law.
As used herein in the specification and in the claims, the phrase “at least one,” in reference to a list of one or more elements, should be understood to mean at least one element selected from any one or more of the elements in the list of elements, but not necessarily including at least one of each and every element specifically listed within the list of elements and not excluding any combinations of elements in the list of elements. This definition also allows that elements may optionally be present other than the elements specifically identified within the list of elements to which the phrase “at least one” refers, whether related or unrelated to those elements specifically identified. Thus, as a non-limiting example, “at least one of A and B” (or, equivalently, “at least one of A or B,” or, equivalently “at least one of A and/or B”) can refer, in one embodiment, to at least one, optionally including more than one, A, with no B present (and optionally including elements other than B); in another embodiment, to at least one, optionally including more than one, B, with no A present (and optionally including elements other than A); in yet another embodiment, to at least one, optionally including more than one, A, and at least one, optionally including more than one, B (and optionally including other elements); etc.
In the claims, as well as in the specification above, all transitional phrases such as “comprising,” “including,” “carrying,” “having,” “containing,” “involving,” “holding,” “composed of,” and the like are to be understood to be open-ended, i.e., to mean including but not limited to. Only the transitional phrases “consisting of” and “consisting essentially of” shall be closed or semi-closed transitional phrases, respectively, as set forth in the United States Patent Office Manual of Patent Examining Procedures, Section 2111.03.
This application is a continuation of and claims the benefit of U.S. patent application Ser. No. 14/267,386, filed May 1, 2014, which claims priority under 35 U.S.C. § 111(a) to International Patent Application PCT/US2012/063372, filed Nov. 2, 2012, which in turns claims the priority benefit of U.S. Provisional Patent Application No. 61/555,075, filed on Nov. 3, 2011, entitled “Methods, Apparatus, and Systems for Intelligent Lighting,” and of U.S. Provisional Patent Application No. 61/577,354, filed on Dec. 19, 2011, entitled “Methods, Systems, and Apparatus for Daylight Harvesting,” both of which applications are hereby incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2899541 | De Mauro | Aug 1957 | A |
| D185410 | Bodian | Jun 1959 | S |
| D191530 | Zurawski | Oct 1961 | S |
| D200548 | Reeves | Mar 1965 | S |
| 4194181 | Brundage | Mar 1980 | A |
| 4217646 | Caltagirone et al. | Aug 1980 | A |
| 4277691 | Lunn | Jul 1981 | A |
| 4298922 | Hardwick | Nov 1981 | A |
| 4558275 | Borowy et al. | Dec 1985 | A |
| 4755920 | Tinley | Jul 1988 | A |
| 4772825 | Tabor et al. | Sep 1988 | A |
| 4780731 | Creutzmann et al. | Oct 1988 | A |
| D300471 | Szymanek | Mar 1989 | S |
| 4873469 | Young et al. | Oct 1989 | A |
| 5055985 | Fabbri | Oct 1991 | A |
| 5144222 | Herbert | Sep 1992 | A |
| 5293097 | Elwell | Mar 1994 | A |
| 5323334 | Meyers et al. | Jun 1994 | A |
| 5430356 | Ference et al. | Jul 1995 | A |
| 5455487 | Mix et al. | Oct 1995 | A |
| 5489827 | Xia | Feb 1996 | A |
| 5521852 | Hibbs et al. | May 1996 | A |
| 5521853 | Hibbs et al. | May 1996 | A |
| D374301 | Kleffman | Oct 1996 | S |
| 5566084 | Cmar | Oct 1996 | A |
| 5572237 | Crooks et al. | Nov 1996 | A |
| 5572239 | Jaeger | Nov 1996 | A |
| 5640792 | Smith et al. | Jun 1997 | A |
| 5655833 | Raczynski | Aug 1997 | A |
| 5668446 | Baker | Sep 1997 | A |
| 5739639 | Johnson | Apr 1998 | A |
| 5753983 | Dickie et al. | May 1998 | A |
| 5764146 | Baldwin et al. | Jun 1998 | A |
| 5895986 | Walters et al. | Apr 1999 | A |
| 5914865 | Barbehenn et al. | Jun 1999 | A |
| 5945993 | Fleischmann | Aug 1999 | A |
| 5971597 | Baldwin et al. | Oct 1999 | A |
| 6016038 | Mueller et al. | Jan 2000 | A |
| 6025679 | Harper et al. | Feb 2000 | A |
| 6028396 | Morrissey, Jr. et al. | Feb 2000 | A |
| 6028597 | Ryan et al. | Feb 2000 | A |
| 6035266 | Williams et al. | Mar 2000 | A |
| 6092913 | Edwards, Jr. | Jul 2000 | A |
| 6097419 | Morris et al. | Aug 2000 | A |
| 6113137 | Mizutani et al. | Sep 2000 | A |
| 6118230 | Fleischmann | Sep 2000 | A |
| 6150774 | Mueller et al. | Nov 2000 | A |
| 6151529 | Batko | Nov 2000 | A |
| 6160359 | Fleischmann | Dec 2000 | A |
| 6166496 | Lys et al. | Dec 2000 | A |
| 6211626 | Lys et al. | Apr 2001 | B1 |
| 6257735 | Baar | Jul 2001 | B1 |
| D447266 | Verfuerth | Aug 2001 | S |
| 6292901 | Lys et al. | Sep 2001 | B1 |
| 6340868 | Lys et al. | Jan 2002 | B1 |
| 6359555 | Williams | Mar 2002 | B1 |
| 6370489 | Williams et al. | Apr 2002 | B1 |
| D457667 | Piepgras et al. | May 2002 | S |
| D457669 | Piepgras et al. | May 2002 | S |
| D457974 | Piepgras et al. | May 2002 | S |
| 6384722 | Williams | May 2002 | B1 |
| 6388399 | Eckel et al. | May 2002 | B1 |
| 6393381 | Williams et al. | May 2002 | B1 |
| D458395 | Piepgras et al. | Jun 2002 | S |
| D460735 | Verfuerth | Jul 2002 | S |
| 6415205 | Myron et al. | Jul 2002 | B1 |
| 6415245 | Williams et al. | Jul 2002 | B2 |
| 6428183 | McAlpin | Aug 2002 | B1 |
| D463059 | Verfuerth | Sep 2002 | S |
| D463610 | Piepgras et al. | Sep 2002 | S |
| 6452339 | Morrissey et al. | Sep 2002 | B1 |
| 6452340 | Morrissey, Jr. et al. | Sep 2002 | B1 |
| 6456960 | Williams et al. | Sep 2002 | B1 |
| 6459919 | Lys et al. | Oct 2002 | B1 |
| 6466190 | Evoy | Oct 2002 | B1 |
| 6467933 | Baar | Oct 2002 | B2 |
| 6486790 | Perlo et al. | Nov 2002 | B1 |
| D468035 | Blanc et al. | Dec 2002 | S |
| 6491412 | Bowman et al. | Dec 2002 | B1 |
| 6517218 | Hochstein | Feb 2003 | B2 |
| 6528954 | Lys et al. | Mar 2003 | B1 |
| 6548967 | Dowling et al. | Apr 2003 | B1 |
| 6577080 | Lys et al. | Jun 2003 | B2 |
| 6585396 | Verfuerth | Jul 2003 | B1 |
| 6604062 | Williams et al. | Aug 2003 | B2 |
| 6608453 | Morgan et al. | Aug 2003 | B2 |
| D479826 | Verfuerth et al. | Sep 2003 | S |
| 6624597 | Dowling et al. | Sep 2003 | B2 |
| 6641284 | Stopa et al. | Nov 2003 | B2 |
| 6652119 | Barton | Nov 2003 | B1 |
| D483332 | Verfuerth | Dec 2003 | S |
| 6710588 | Verfuerth et al. | Mar 2004 | B1 |
| 6714895 | Williams et al. | Mar 2004 | B2 |
| 6717376 | Lys et al. | Apr 2004 | B2 |
| 6720745 | Lys et al. | Apr 2004 | B2 |
| 6724180 | Verfuerth et al. | Apr 2004 | B1 |
| D491678 | Piepgras | Jun 2004 | S |
| D492042 | Piepgras | Jun 2004 | S |
| 6746274 | Verfuerth | Jun 2004 | B1 |
| 6748299 | Motoyama | Jun 2004 | B1 |
| 6758580 | Verfuerth | Jul 2004 | B1 |
| D494700 | Hartman et al. | Aug 2004 | S |
| 6774584 | Lys et al. | Aug 2004 | B2 |
| 6774619 | Verfuerth et al. | Aug 2004 | B1 |
| 6777891 | Lys et al. | Aug 2004 | B2 |
| 6781329 | Mueller et al. | Aug 2004 | B2 |
| 6788011 | Mueller et al. | Sep 2004 | B2 |
| 6791458 | Baldwin | Sep 2004 | B2 |
| 6798341 | Eckel et al. | Sep 2004 | B1 |
| 6801003 | Schanberger et al. | Oct 2004 | B2 |
| 6806659 | Mueller et al. | Oct 2004 | B1 |
| 6807516 | Williams et al. | Oct 2004 | B2 |
| 6841944 | Morrissey et al. | Jan 2005 | B2 |
| 6869204 | Morgan et al. | Mar 2005 | B2 |
| 6883929 | Dowling | Apr 2005 | B2 |
| 6888322 | Dowling et al. | May 2005 | B2 |
| 6888323 | Null et al. | May 2005 | B1 |
| 6892168 | Williams et al. | May 2005 | B2 |
| 6909921 | Bilger | Jun 2005 | B1 |
| 6933627 | Wilhelm | Aug 2005 | B2 |
| 6936978 | Morgan et al. | Aug 2005 | B2 |
| 6964502 | Verfuerth | Nov 2005 | B1 |
| 6965205 | Piepgras et al. | Nov 2005 | B2 |
| 6967448 | Morgan et al. | Nov 2005 | B2 |
| 6969954 | Lys | Nov 2005 | B2 |
| 6975079 | Lys et al. | Dec 2005 | B2 |
| 7002546 | Stuppi et al. | Feb 2006 | B1 |
| D518218 | Roberge et al. | Mar 2006 | S |
| 7014336 | Ducharme et al. | Mar 2006 | B1 |
| 7019276 | Cloutier et al. | Mar 2006 | B2 |
| 7031920 | Dowling et al. | Apr 2006 | B2 |
| 7038398 | Lys et al. | May 2006 | B1 |
| 7038399 | Lys et al. | May 2006 | B2 |
| 7042172 | Dowling et al. | May 2006 | B2 |
| 7062360 | Fairlie et al. | Jun 2006 | B2 |
| 7064498 | Dowling et al. | Jun 2006 | B2 |
| 7093952 | Ono et al. | Aug 2006 | B2 |
| 7113541 | Lys et al. | Sep 2006 | B1 |
| 7132635 | Dowling | Nov 2006 | B2 |
| 7132785 | Ducharme | Nov 2006 | B2 |
| 7132804 | Lys et al. | Nov 2006 | B2 |
| 7135824 | Lys et al. | Nov 2006 | B2 |
| 7139617 | Morgan et al. | Nov 2006 | B1 |
| 7160140 | Mrakovich et al. | Jan 2007 | B1 |
| 7161311 | Mueller et al. | Jan 2007 | B2 |
| 7161313 | Piepgras et al. | Jan 2007 | B2 |
| 7161556 | Morgan et al. | Jan 2007 | B2 |
| 7178941 | Roberge et al. | Feb 2007 | B2 |
| 7180252 | Lys et al. | Feb 2007 | B2 |
| D538462 | Verfuerth et al. | Mar 2007 | S |
| 7186003 | Dowling et al. | Mar 2007 | B2 |
| 7187141 | Mueller et al. | Mar 2007 | B2 |
| 7190121 | Rose et al. | Mar 2007 | B2 |
| 7199531 | Loughrey | Apr 2007 | B2 |
| 7202613 | Morgan et al. | Apr 2007 | B2 |
| 7204622 | Dowling et al. | Apr 2007 | B2 |
| 7220015 | Dowling | May 2007 | B2 |
| 7220018 | Crabb et al. | May 2007 | B2 |
| 7221104 | Lys et al. | May 2007 | B2 |
| 7228190 | Dowling et al. | Jun 2007 | B2 |
| 7231060 | Dowling et al. | Jun 2007 | B2 |
| 7233115 | Lys | Jun 2007 | B2 |
| 7233831 | Blackwell | Jun 2007 | B2 |
| 7236366 | Chen | Jun 2007 | B2 |
| 7242152 | Dowling et al. | Jul 2007 | B2 |
| 7248239 | Dowling et al. | Jul 2007 | B2 |
| D548868 | Roberge et al. | Aug 2007 | S |
| 7253566 | Lys et al. | Aug 2007 | B2 |
| 7255457 | Ducharme et al. | Aug 2007 | B2 |
| 7256554 | Lys | Aug 2007 | B2 |
| 7256556 | Lane et al. | Aug 2007 | B2 |
| 7274160 | Mueller et al. | Sep 2007 | B2 |
| 7274975 | Miller | Sep 2007 | B2 |
| 7300192 | Mueller et al. | Nov 2007 | B2 |
| D557817 | Verfuerth | Dec 2007 | S |
| 7303300 | Dowling et al. | Dec 2007 | B2 |
| 7308296 | Lys et al. | Dec 2007 | B2 |
| 7309965 | Dowling et al. | Dec 2007 | B2 |
| 7311423 | Frecska et al. | Dec 2007 | B2 |
| D560469 | Bartol et al. | Jan 2008 | S |
| D562494 | Piepgras | Feb 2008 | S |
| 7333903 | Walters et al. | Feb 2008 | B2 |
| 7344279 | Mueller et al. | Mar 2008 | B2 |
| 7344296 | Matsui et al. | Mar 2008 | B2 |
| 7348736 | Piepgras et al. | Mar 2008 | B2 |
| D566323 | Piepgras et al. | Apr 2008 | S |
| 7350936 | Ducharme et al. | Apr 2008 | B2 |
| 7352138 | Lys et al. | Apr 2008 | B2 |
| 7352339 | Morgan et al. | Apr 2008 | B2 |
| 7353071 | Blackwell et al. | Apr 2008 | B2 |
| 7354172 | Chemel et al. | Apr 2008 | B2 |
| 7358679 | Lys et al. | Apr 2008 | B2 |
| 7358929 | Mueller et al. | Apr 2008 | B2 |
| 7379981 | Elliott et al. | May 2008 | B2 |
| 7385359 | Dowling et al. | Jun 2008 | B2 |
| 7387405 | Ducharme et al. | Jun 2008 | B2 |
| 7391335 | Mubaslat et al. | Jun 2008 | B2 |
| 7401942 | Verfuerth et al. | Jul 2008 | B1 |
| 7411489 | Elwell et al. | Aug 2008 | B1 |
| 7427840 | Morgan et al. | Sep 2008 | B2 |
| 7445354 | Aoki et al. | Nov 2008 | B2 |
| 7453217 | Lys et al. | Nov 2008 | B2 |
| 7470055 | Hacker et al. | Dec 2008 | B2 |
| 7482565 | Morgan et al. | Jan 2009 | B2 |
| 7482764 | Morgan et al. | Jan 2009 | B2 |
| 7495671 | Chemel et al. | Feb 2009 | B2 |
| 7501768 | Lane et al. | Mar 2009 | B2 |
| 7502034 | Chemel et al. | Mar 2009 | B2 |
| 7506993 | Kain et al. | Mar 2009 | B2 |
| 7507001 | Kit | Mar 2009 | B2 |
| 7518319 | Konno et al. | Apr 2009 | B2 |
| 7520634 | Ducharme et al. | Apr 2009 | B2 |
| D592786 | Bisberg et al. | May 2009 | S |
| 7529594 | Walters et al. | May 2009 | B2 |
| D593697 | Liu et al. | Jun 2009 | S |
| 7543956 | Piepgras et al. | Jun 2009 | B2 |
| 7546167 | Walters et al. | Jun 2009 | B2 |
| 7546168 | Walters et al. | Jun 2009 | B2 |
| 7550931 | Lys et al. | Jun 2009 | B2 |
| 7550935 | Lys et al. | Jun 2009 | B2 |
| D595894 | Verfuerth et al. | Jul 2009 | S |
| 7563006 | Verfuerth et al. | Jul 2009 | B1 |
| 7571063 | Howell et al. | Aug 2009 | B2 |
| 7572028 | Mueller et al. | Aug 2009 | B2 |
| 7575338 | Verfuerth | Aug 2009 | B1 |
| 7598681 | Lys et al. | Oct 2009 | B2 |
| 7598684 | Lys et al. | Oct 2009 | B2 |
| 7598686 | Lys et al. | Oct 2009 | B2 |
| 7603184 | Walters et al. | Oct 2009 | B2 |
| 7619370 | Chemel et al. | Nov 2009 | B2 |
| D606697 | Verfuerth et al. | Dec 2009 | S |
| D606698 | Verfuerth et al. | Dec 2009 | S |
| 7628506 | Verfuerth et al. | Dec 2009 | B2 |
| 7638743 | Bartol et al. | Dec 2009 | B2 |
| 7642730 | Dowling et al. | Jan 2010 | B2 |
| 7646029 | Mueller et al. | Jan 2010 | B2 |
| 7659674 | Mueller et al. | Feb 2010 | B2 |
| 7660892 | Choong et al. | Feb 2010 | B2 |
| 7703951 | Piepgras et al. | Apr 2010 | B2 |
| D617028 | Verfuerth et al. | Jun 2010 | S |
| D617029 | Verfuerth et al. | Jun 2010 | S |
| 7744251 | Liu et al. | Jun 2010 | B2 |
| 7746003 | Verfuerth et al. | Jun 2010 | B2 |
| 7753568 | Hu et al. | Jul 2010 | B2 |
| 7761260 | Walters et al. | Jul 2010 | B2 |
| 7762861 | Verfuerth et al. | Jul 2010 | B2 |
| D621410 | Verfuerth et al. | Aug 2010 | S |
| D621411 | Verfuerth et al. | Aug 2010 | S |
| 7766518 | Piepgras et al. | Aug 2010 | B2 |
| 7777427 | Stalker, III | Aug 2010 | B2 |
| 7780310 | Verfuerth et al. | Aug 2010 | B2 |
| 7783390 | Miller | Aug 2010 | B2 |
| 7784966 | Verfuerth et al. | Aug 2010 | B2 |
| D623340 | Verfuerth et al. | Sep 2010 | S |
| 7792956 | Choong et al. | Sep 2010 | B2 |
| 7809448 | Lys et al. | Oct 2010 | B2 |
| 7824065 | Maxik | Nov 2010 | B2 |
| 7828465 | Roberge et al. | Nov 2010 | B2 |
| 7839017 | Huizenga et al. | Nov 2010 | B2 |
| 7839295 | Ries, II | Nov 2010 | B2 |
| 7845823 | Mueller et al. | Dec 2010 | B2 |
| 7852017 | Melanson | Dec 2010 | B1 |
| 7866847 | Zheng | Jan 2011 | B2 |
| D632006 | Verfuerth et al. | Feb 2011 | S |
| D632418 | Bisberg et al. | Feb 2011 | S |
| 7878683 | Logan et al. | Feb 2011 | B2 |
| 7911359 | Walters et al. | Mar 2011 | B2 |
| 7924155 | Soccoli et al. | Apr 2011 | B2 |
| 7925384 | Huizenga et al. | Apr 2011 | B2 |
| 7926974 | Wung et al. | Apr 2011 | B2 |
| 7936561 | Lin | May 2011 | B1 |
| 7938558 | Wilcox et al. | May 2011 | B2 |
| 7959320 | Mueller et al. | Jun 2011 | B2 |
| 7962606 | Barron et al. | Jun 2011 | B2 |
| 7976188 | Peng | Jul 2011 | B2 |
| 7988335 | Liu et al. | Aug 2011 | B2 |
| 7988341 | Chen | Aug 2011 | B2 |
| 7997762 | Wang et al. | Aug 2011 | B2 |
| 8010319 | Walters et al. | Aug 2011 | B2 |
| 8013281 | Morgan et al. | Sep 2011 | B2 |
| 8025426 | Mundle et al. | Sep 2011 | B2 |
| 8033686 | Recker et al. | Oct 2011 | B2 |
| 8035320 | Sibert | Oct 2011 | B2 |
| 8042968 | Boyer et al. | Oct 2011 | B2 |
| 8052301 | Zhou et al. | Nov 2011 | B2 |
| 8061865 | Piepgras et al. | Nov 2011 | B2 |
| 8066403 | Sanfilippo et al. | Nov 2011 | B2 |
| 8067906 | Null | Nov 2011 | B2 |
| D650225 | Bartol et al. | Dec 2011 | S |
| 8070312 | Verfuerth et al. | Dec 2011 | B2 |
| 8079731 | Lynch et al. | Dec 2011 | B2 |
| 8080819 | Mueller et al. | Dec 2011 | B2 |
| 8096679 | Chen et al. | Jan 2012 | B2 |
| 8101434 | Guillien et al. | Jan 2012 | B2 |
| 8136958 | Verfuerth et al. | Mar 2012 | B2 |
| 8138690 | Chemel et al. | Mar 2012 | B2 |
| 8147267 | Oster | Apr 2012 | B2 |
| RE43456 | Verfuerth et al. | Jun 2012 | E |
| 8214061 | Westrick, Jr. et al. | Jul 2012 | B2 |
| 8232745 | Chemel et al. | Jul 2012 | B2 |
| 8237581 | Ries, II | Aug 2012 | B2 |
| 8237582 | Ries, II | Aug 2012 | B2 |
| 8242927 | Ries, II | Aug 2012 | B2 |
| 8260575 | Walters et al. | Sep 2012 | B2 |
| 8265674 | Choong et al. | Sep 2012 | B2 |
| 8275471 | Huizenga et al. | Sep 2012 | B2 |
| 8337043 | Verfuerth et al. | Dec 2012 | B2 |
| 8339069 | Chemel et al. | Dec 2012 | B2 |
| 8344660 | Mohan et al. | Jan 2013 | B2 |
| 8344665 | Verfuerth et al. | Jan 2013 | B2 |
| 8364325 | Huizenga et al. | Jan 2013 | B2 |
| 8368321 | Chemel et al. | Feb 2013 | B2 |
| 8370483 | Choong et al. | Feb 2013 | B2 |
| 8373362 | Chemel et al. | Feb 2013 | B2 |
| 8376583 | Wang et al. | Feb 2013 | B2 |
| 8376600 | Bartol et al. | Feb 2013 | B2 |
| 8406937 | Verfuerth et al. | Mar 2013 | B2 |
| 8415897 | Choong et al. | Apr 2013 | B2 |
| 8422401 | Choong et al. | Apr 2013 | B1 |
| 8445826 | Verfuerth | May 2013 | B2 |
| 8450670 | Verfuerth et al. | May 2013 | B2 |
| 8466626 | Null et al. | Jun 2013 | B2 |
| 8476565 | Verfuerth | Jul 2013 | B2 |
| 8531134 | Chemel et al. | Sep 2013 | B2 |
| 8536802 | Chemel et al. | Sep 2013 | B2 |
| 8543249 | Chemel et al. | Sep 2013 | B2 |
| 8552664 | Chemel et al. | Oct 2013 | B2 |
| 8586902 | Verfuerth | Nov 2013 | B2 |
| 8593135 | Chemel et al. | Nov 2013 | B2 |
| 8604701 | Verfuerth et al. | Dec 2013 | B2 |
| 8610376 | Chemel et al. | Dec 2013 | B2 |
| 8610377 | Chemel et al. | Dec 2013 | B2 |
| 8700749 | Elliott et al. | Apr 2014 | B2 |
| 8729833 | Chemel et al. | May 2014 | B2 |
| 8754589 | Chemel et al. | Jun 2014 | B2 |
| 8755039 | Ramer et al. | Jun 2014 | B2 |
| 8805550 | Chemel et al. | Aug 2014 | B2 |
| 8823277 | Chemel et al. | Sep 2014 | B2 |
| 8841859 | Chemel et al. | Sep 2014 | B2 |
| 8855019 | Elliott et al. | Oct 2014 | B2 |
| 8866408 | Chemel et al. | Oct 2014 | B2 |
| 8954170 | Chemel et al. | Feb 2015 | B2 |
| 9014829 | Chemel et al. | Apr 2015 | B2 |
| 9072133 | Chemel et al. | Jun 2015 | B2 |
| 9125254 | Chemel et al. | Sep 2015 | B2 |
| 9241392 | Chemel et al. | Jan 2016 | B2 |
| 9519426 | Chemel et al. | Nov 2016 | B2 |
| 20010028227 | Lys et al. | Oct 2001 | A1 |
| 20010055965 | Delp et al. | Dec 2001 | A1 |
| 20020032535 | Alexander et al. | Mar 2002 | A1 |
| 20020036430 | Welches et al. | Mar 2002 | A1 |
| 20020038157 | Dowling et al. | Mar 2002 | A1 |
| 20020047628 | Morgan et al. | Apr 2002 | A1 |
| 20020048169 | Dowling et al. | Apr 2002 | A1 |
| 20020070688 | Dowling et al. | Jun 2002 | A1 |
| 20020074559 | Dowling et al. | Jun 2002 | A1 |
| 20020078221 | Blackwell et al. | Jun 2002 | A1 |
| 20020101197 | Lys et al. | Aug 2002 | A1 |
| 20020113555 | Lys et al. | Aug 2002 | A1 |
| 20020130627 | Morgan et al. | Sep 2002 | A1 |
| 20020133270 | Hung et al. | Sep 2002 | A1 |
| 20020134849 | Disser | Sep 2002 | A1 |
| 20020145394 | Morgan et al. | Oct 2002 | A1 |
| 20020152045 | Dowling et al. | Oct 2002 | A1 |
| 20020153851 | Morgan et al. | Oct 2002 | A1 |
| 20020163316 | Lys et al. | Nov 2002 | A1 |
| 20020171365 | Morgan et al. | Nov 2002 | A1 |
| 20020171377 | Mueller et al. | Nov 2002 | A1 |
| 20020171378 | Morgan et al. | Nov 2002 | A1 |
| 20020175642 | von Kannewurff et al. | Nov 2002 | A1 |
| 20030011538 | Lys et al. | Jan 2003 | A1 |
| 20030057886 | Lys et al. | Mar 2003 | A1 |
| 20030057887 | Dowling et al. | Mar 2003 | A1 |
| 20030057888 | Archenhold et al. | Mar 2003 | A1 |
| 20030057890 | Lys et al. | Mar 2003 | A1 |
| 20030063462 | Shimizu et al. | Apr 2003 | A1 |
| 20030076056 | Schuurmans | Apr 2003 | A1 |
| 20030076281 | Morgan et al. | Apr 2003 | A1 |
| 20030097309 | Gibler et al. | May 2003 | A1 |
| 20030100837 | Lys et al. | May 2003 | A1 |
| 20030100998 | Brunner et al. | May 2003 | A2 |
| 20030102675 | Noethlichs | Jun 2003 | A1 |
| 20030123705 | Stam et al. | Jul 2003 | A1 |
| 20030123706 | Stam et al. | Jul 2003 | A1 |
| 20030133292 | Mueller et al. | Jul 2003 | A1 |
| 20030137258 | Piepgras et al. | Jul 2003 | A1 |
| 20030206411 | Dowling et al. | Nov 2003 | A9 |
| 20030214259 | Dowling et al. | Nov 2003 | A9 |
| 20030216971 | Sick et al. | Nov 2003 | A1 |
| 20030222587 | Dowling et al. | Dec 2003 | A1 |
| 20030222603 | Mogilner et al. | Dec 2003 | A1 |
| 20040002792 | Hoffknecht | Jan 2004 | A1 |
| 20040036006 | Dowling | Feb 2004 | A1 |
| 20040052076 | Mueller et al. | Mar 2004 | A1 |
| 20040090191 | Mueller et al. | May 2004 | A1 |
| 20040090787 | Dowling et al. | May 2004 | A1 |
| 20040105261 | Ducharme et al. | Jun 2004 | A1 |
| 20040105264 | Spero | Jun 2004 | A1 |
| 20040111638 | Yadav et al. | Jun 2004 | A1 |
| 20040113044 | Ishiguchi | Jun 2004 | A1 |
| 20040113568 | Dowling et al. | Jun 2004 | A1 |
| 20040119415 | Lansing et al. | Jun 2004 | A1 |
| 20040130909 | Mueller et al. | Jul 2004 | A1 |
| 20040141321 | Dowling et al. | Jul 2004 | A1 |
| 20040155609 | Lys et al. | Aug 2004 | A1 |
| 20040160199 | Morgan et al. | Aug 2004 | A1 |
| 20040178751 | Mueller et al. | Sep 2004 | A1 |
| 20040212320 | Dowling et al. | Oct 2004 | A1 |
| 20040212321 | Lys et al. | Oct 2004 | A1 |
| 20040212993 | Morgan et al. | Oct 2004 | A1 |
| 20040240890 | Lys et al. | Dec 2004 | A1 |
| 20040252501 | Moriyama et al. | Dec 2004 | A1 |
| 20040257007 | Lys et al. | Dec 2004 | A1 |
| 20050030744 | Ducharme et al. | Feb 2005 | A1 |
| 20050035728 | Schanberger et al. | Feb 2005 | A1 |
| 20050036300 | Dowling et al. | Feb 2005 | A1 |
| 20050040774 | Mueller et al. | Feb 2005 | A1 |
| 20050041161 | Dowling et al. | Feb 2005 | A1 |
| 20050041424 | Ducharme | Feb 2005 | A1 |
| 20050044617 | Mueller et al. | Mar 2005 | A1 |
| 20050047132 | Dowling et al. | Mar 2005 | A1 |
| 20050047134 | Mueller et al. | Mar 2005 | A1 |
| 20050062440 | Lys et al. | Mar 2005 | A1 |
| 20050063194 | Lys et al. | Mar 2005 | A1 |
| 20050099796 | Magee | May 2005 | A1 |
| 20050099824 | Dowling et al. | May 2005 | A1 |
| 20050116667 | Mueller et al. | Jun 2005 | A1 |
| 20050125083 | Kiko | Jun 2005 | A1 |
| 20050128751 | Roberge et al. | Jun 2005 | A1 |
| 20050151489 | Lys et al. | Jul 2005 | A1 |
| 20050162101 | Leong et al. | Jul 2005 | A1 |
| 20050174473 | Morgan et al. | Aug 2005 | A1 |
| 20050213352 | Lys | Sep 2005 | A1 |
| 20050213353 | Lys | Sep 2005 | A1 |
| 20050218838 | Lys | Oct 2005 | A1 |
| 20050218870 | Lys | Oct 2005 | A1 |
| 20050219872 | Lys | Oct 2005 | A1 |
| 20050231133 | Lys | Oct 2005 | A1 |
| 20050236029 | Dowling | Oct 2005 | A1 |
| 20050236998 | Mueller et al. | Oct 2005 | A1 |
| 20050248299 | Chemel et al. | Nov 2005 | A1 |
| 20050253533 | Lys et al. | Nov 2005 | A1 |
| 20050258765 | Rodriguez | Nov 2005 | A1 |
| 20050275626 | Mueller et al. | Dec 2005 | A1 |
| 20050276053 | Nortrup et al. | Dec 2005 | A1 |
| 20050285547 | Piepgras et al. | Dec 2005 | A1 |
| 20060002110 | Dowling et al. | Jan 2006 | A1 |
| 20060012987 | Ducharme et al. | Jan 2006 | A9 |
| 20060022214 | Morgan et al. | Feb 2006 | A1 |
| 20060038511 | Tagawa | Feb 2006 | A1 |
| 20060050509 | Dowling et al. | Mar 2006 | A9 |
| 20060076908 | Morgan et al. | Apr 2006 | A1 |
| 20060087843 | Setomoto et al. | Apr 2006 | A1 |
| 20060098077 | Dowling | May 2006 | A1 |
| 20060104058 | Chemel et al. | May 2006 | A1 |
| 20060106762 | Caracas et al. | May 2006 | A1 |
| 20060108935 | Stevn | May 2006 | A1 |
| 20060109649 | Ducharme et al. | May 2006 | A1 |
| 20060125426 | Veskovic et al. | Jun 2006 | A1 |
| 20060132061 | McCormick et al. | Jun 2006 | A1 |
| 20060146531 | Reo et al. | Jul 2006 | A1 |
| 20060152172 | Mueller et al. | Jul 2006 | A9 |
| 20060158881 | Dowling | Jul 2006 | A1 |
| 20060160199 | DiCosimo et al. | Jul 2006 | A1 |
| 20060170376 | Piepgras et al. | Aug 2006 | A1 |
| 20060181878 | Burkholder | Aug 2006 | A1 |
| 20060198128 | Piepgras et al. | Sep 2006 | A1 |
| 20060208667 | Lys et al. | Sep 2006 | A1 |
| 20060221606 | Dowling | Oct 2006 | A1 |
| 20060245174 | Ashdown et al. | Nov 2006 | A1 |
| 20060262516 | Dowling et al. | Nov 2006 | A9 |
| 20060262521 | Piepgras et al. | Nov 2006 | A1 |
| 20060262544 | Piepgras et al. | Nov 2006 | A1 |
| 20060262545 | Piepgras et al. | Nov 2006 | A1 |
| 20060273741 | Stalker, III | Dec 2006 | A1 |
| 20060276938 | Miller | Dec 2006 | A1 |
| 20060285325 | Ducharme et al. | Dec 2006 | A1 |
| 20070021946 | Williams et al. | Jan 2007 | A1 |
| 20070030716 | Manolescu | Feb 2007 | A1 |
| 20070032990 | Williams et al. | Feb 2007 | A1 |
| 20070040513 | Cleland et al. | Feb 2007 | A1 |
| 20070045407 | Paul | Mar 2007 | A1 |
| 20070047227 | Ducharme | Mar 2007 | A1 |
| 20070064425 | Frecska et al. | Mar 2007 | A1 |
| 20070086754 | Lys et al. | Apr 2007 | A1 |
| 20070086912 | Dowling et al. | Apr 2007 | A1 |
| 20070115658 | Mueller et al. | May 2007 | A1 |
| 20070115665 | Mueller et al. | May 2007 | A1 |
| 20070143046 | Budike, Jr. | Jun 2007 | A1 |
| 20070145915 | Roberge et al. | Jun 2007 | A1 |
| 20070152797 | Chemel et al. | Jul 2007 | A1 |
| 20070153514 | Dowling et al. | Jul 2007 | A1 |
| 20070188114 | Lys et al. | Aug 2007 | A1 |
| 20070188427 | Lys et al. | Aug 2007 | A1 |
| 20070189026 | Chemel et al. | Aug 2007 | A1 |
| 20070195526 | Dowling et al. | Aug 2007 | A1 |
| 20070206375 | Piepgras et al. | Sep 2007 | A1 |
| 20070211463 | Chevalier et al. | Sep 2007 | A1 |
| 20070217196 | Shaner | Sep 2007 | A1 |
| 20070228999 | Kit | Oct 2007 | A1 |
| 20070229250 | Recker et al. | Oct 2007 | A1 |
| 20070236156 | Lys et al. | Oct 2007 | A1 |
| 20070237284 | Lys et al. | Oct 2007 | A1 |
| 20070258231 | Koerner et al. | Nov 2007 | A1 |
| 20070258240 | Ducharme et al. | Nov 2007 | A1 |
| 20070263379 | Dowling | Nov 2007 | A1 |
| 20070267978 | Shteynberg et al. | Nov 2007 | A1 |
| 20070273307 | Westrick et al. | Nov 2007 | A1 |
| 20070291483 | Lys | Dec 2007 | A1 |
| 20080001071 | Lee et al. | Jan 2008 | A1 |
| 20080007943 | Verfuerth et al. | Jan 2008 | A1 |
| 20080007944 | Verfuerth et al. | Jan 2008 | A1 |
| 20080012502 | Lys | Jan 2008 | A1 |
| 20080012506 | Mueller et al. | Jan 2008 | A1 |
| 20080030149 | Callahan | Feb 2008 | A1 |
| 20080074059 | Ahmed | Mar 2008 | A1 |
| 20080079568 | Primous et al. | Apr 2008 | A1 |
| 20080089060 | Kondo et al. | Apr 2008 | A1 |
| 20080111498 | Budike | May 2008 | A1 |
| 20080140231 | Blackwell et al. | Jun 2008 | A1 |
| 20080158878 | Van Laanen et al. | Jul 2008 | A1 |
| 20080164826 | Lys | Jul 2008 | A1 |
| 20080164827 | Lys | Jul 2008 | A1 |
| 20080164854 | Lys | Jul 2008 | A1 |
| 20080170371 | Lai | Jul 2008 | A1 |
| 20080180015 | Wu et al. | Jul 2008 | A1 |
| 20080183081 | Lys et al. | Jul 2008 | A1 |
| 20080183307 | Clayton et al. | Jul 2008 | A1 |
| 20080183316 | Clayton | Jul 2008 | A1 |
| 20080195561 | Herzig | Aug 2008 | A1 |
| 20080204268 | Dowling et al. | Aug 2008 | A1 |
| 20080208651 | Johnston et al. | Aug 2008 | A1 |
| 20080215391 | Dowling et al. | Sep 2008 | A1 |
| 20080246415 | Chitta et al. | Oct 2008 | A1 |
| 20080265799 | Sibert | Oct 2008 | A1 |
| 20080272934 | Wang et al. | Nov 2008 | A1 |
| 20080275802 | Verfuerth et al. | Nov 2008 | A1 |
| 20080278941 | Logan et al. | Nov 2008 | A1 |
| 20080310850 | Pederson et al. | Dec 2008 | A1 |
| 20090000217 | Verfuerth et al. | Jan 2009 | A1 |
| 20090009989 | Verfuerth et al. | Jan 2009 | A1 |
| 20090014625 | Bartol et al. | Jan 2009 | A1 |
| 20090018673 | Dushane et al. | Jan 2009 | A1 |
| 20090021955 | Kuang et al. | Jan 2009 | A1 |
| 20090027932 | Haines et al. | Jan 2009 | A1 |
| 20090034263 | Stenback et al. | Feb 2009 | A1 |
| 20090050908 | Yuan et al. | Feb 2009 | A1 |
| 20090051506 | Hicksted et al. | Feb 2009 | A1 |
| 20090059603 | Recker et al. | Mar 2009 | A1 |
| 20090059915 | Baker | Mar 2009 | A1 |
| 20090066266 | Jungwirth et al. | Mar 2009 | A1 |
| 20090076790 | Fein et al. | Mar 2009 | A1 |
| 20090085494 | Summerland | Apr 2009 | A1 |
| 20090085500 | Zampini et al. | Apr 2009 | A1 |
| 20090122571 | Simmons et al. | May 2009 | A1 |
| 20090147507 | Verfuerth et al. | Jun 2009 | A1 |
| 20090160364 | Ackermann et al. | Jun 2009 | A1 |
| 20090189535 | Verfuerth et al. | Jul 2009 | A1 |
| 20090193217 | Korecki et al. | Jul 2009 | A1 |
| 20090243517 | Verfuerth et al. | Oct 2009 | A1 |
| 20090248217 | Verfuerth et al. | Oct 2009 | A1 |
| 20090267540 | Chemel et al. | Oct 2009 | A1 |
| 20090278472 | Mills et al. | Nov 2009 | A1 |
| 20090278479 | Platner et al. | Nov 2009 | A1 |
| 20090284184 | Valois et al. | Nov 2009 | A1 |
| 20090299527 | Huizenga et al. | Dec 2009 | A1 |
| 20090299811 | Verfuerth et al. | Dec 2009 | A1 |
| 20090303722 | Verfuerth et al. | Dec 2009 | A1 |
| 20090315485 | Verfuerth et al. | Dec 2009 | A1 |
| 20090323347 | Zhang et al. | Dec 2009 | A1 |
| 20100026479 | Tran | Feb 2010 | A1 |
| 20100034386 | Choong et al. | Feb 2010 | A1 |
| 20100052574 | Blakeley | Mar 2010 | A1 |
| 20100061088 | Bartol et al. | Mar 2010 | A1 |
| 20100109536 | Jung et al. | May 2010 | A1 |
| 20100124376 | Thind | May 2010 | A1 |
| 20100127634 | Dowling et al. | May 2010 | A1 |
| 20100134051 | Huizenga et al. | Jun 2010 | A1 |
| 20100135186 | Choong et al. | Jun 2010 | A1 |
| 20100141153 | Recker | Jun 2010 | A1 |
| 20100148689 | Morgan et al. | Jun 2010 | A1 |
| 20100169249 | Jhala et al. | Jul 2010 | A1 |
| 20100171145 | Morgan et al. | Jul 2010 | A1 |
| 20100171442 | Draper | Jul 2010 | A1 |
| 20100185339 | Huizenga et al. | Jul 2010 | A1 |
| 20100201267 | Bourquin et al. | Aug 2010 | A1 |
| 20100204841 | Chemel et al. | Aug 2010 | A1 |
| 20100207534 | Dowling et al. | Aug 2010 | A1 |
| 20100211443 | Carrel et al. | Aug 2010 | A1 |
| 20100235004 | Thind | Sep 2010 | A1 |
| 20100246168 | Verfuerth et al. | Sep 2010 | A1 |
| 20100246172 | Liu | Sep 2010 | A1 |
| 20100253499 | Haab et al. | Oct 2010 | A1 |
| 20100259931 | Chemel et al. | Oct 2010 | A1 |
| 20100262313 | Chambers et al. | Oct 2010 | A1 |
| 20100264834 | Gaines et al. | Oct 2010 | A1 |
| 20100264846 | Chemel et al. | Oct 2010 | A1 |
| 20100270933 | Chemel et al. | Oct 2010 | A1 |
| 20100283605 | Nevins | Nov 2010 | A1 |
| 20100295473 | Chemel et al. | Nov 2010 | A1 |
| 20100295474 | Chemel et al. | Nov 2010 | A1 |
| 20100295475 | Chemel et al. | Nov 2010 | A1 |
| 20100295482 | Chemel et al. | Nov 2010 | A1 |
| 20100296285 | Chemel et al. | Nov 2010 | A1 |
| 20100301768 | Chemel et al. | Dec 2010 | A1 |
| 20100301769 | Chemel et al. | Dec 2010 | A1 |
| 20100301770 | Chemel et al. | Dec 2010 | A1 |
| 20100301771 | Chemel et al. | Dec 2010 | A1 |
| 20100301773 | Chemel et al. | Dec 2010 | A1 |
| 20100301774 | Chemel et al. | Dec 2010 | A1 |
| 20100301834 | Chemel et al. | Dec 2010 | A1 |
| 20100302779 | Chemel et al. | Dec 2010 | A1 |
| 20100307075 | Zampini et al. | Dec 2010 | A1 |
| 20100308736 | Hung et al. | Dec 2010 | A1 |
| 20100327766 | Recker | Dec 2010 | A1 |
| 20110001436 | Chemel et al. | Jan 2011 | A1 |
| 20110001438 | Chemel et al. | Jan 2011 | A1 |
| 20110033632 | Vance et al. | Feb 2011 | A1 |
| 20110035404 | Morgan et al. | Feb 2011 | A1 |
| 20110038148 | Pyle | Feb 2011 | A1 |
| 20110043124 | Johnston et al. | Feb 2011 | A1 |
| 20110057581 | Ashar et al. | Mar 2011 | A1 |
| 20110060701 | Verfuerth et al. | Mar 2011 | A1 |
| 20110068702 | Van De Ven et al. | Mar 2011 | A1 |
| 20110084608 | Lin et al. | Apr 2011 | A1 |
| 20110090684 | Logan et al. | Apr 2011 | A1 |
| 20110102052 | Billingsley et al. | May 2011 | A1 |
| 20110118890 | Parsons | May 2011 | A1 |
| 20110133655 | Recker | Jun 2011 | A1 |
| 20110140611 | Elek et al. | Jun 2011 | A1 |
| 20110140612 | Mohan et al. | Jun 2011 | A1 |
| 20110146669 | Bartol et al. | Jun 2011 | A1 |
| 20110172844 | Choong et al. | Jul 2011 | A1 |
| 20110198977 | VanderSluis | Aug 2011 | A1 |
| 20110204820 | Tikkanen et al. | Aug 2011 | A1 |
| 20110215736 | Horbst et al. | Sep 2011 | A1 |
| 20110216538 | Logan et al. | Sep 2011 | A1 |
| 20110235317 | Verfuerth et al. | Sep 2011 | A1 |
| 20110248171 | Rueger | Oct 2011 | A1 |
| 20110254466 | Jackson et al. | Oct 2011 | A1 |
| 20110279063 | Wang et al. | Nov 2011 | A1 |
| 20110279248 | Ogawa | Nov 2011 | A1 |
| 20120007511 | Choong et al. | Jan 2012 | A1 |
| 20120032599 | Mohan et al. | Feb 2012 | A1 |
| 20120037725 | Verfuerth | Feb 2012 | A1 |
| 20120038281 | Verfuerth | Feb 2012 | A1 |
| 20120038490 | Verfuerth | Feb 2012 | A1 |
| 20120040606 | Verfuerth | Feb 2012 | A1 |
| 20120044350 | Verfuerth | Feb 2012 | A1 |
| 20120044670 | Piepgras et al. | Feb 2012 | A1 |
| 20120058663 | Oster | Mar 2012 | A1 |
| 20120062123 | Jarrell et al. | Mar 2012 | A1 |
| 20120062125 | Mohan et al. | Mar 2012 | A1 |
| 20120080944 | Recker | Apr 2012 | A1 |
| 20120081906 | Verfuerth et al. | Apr 2012 | A1 |
| 20120086363 | Golding et al. | Apr 2012 | A1 |
| 20120098439 | Recker | Apr 2012 | A1 |
| 20120112654 | Choong et al. | May 2012 | A1 |
| 20120112667 | Mohan et al. | May 2012 | A1 |
| 20120130544 | Mohan et al. | May 2012 | A1 |
| 20120143357 | Chemel et al. | Jun 2012 | A1 |
| 20120153844 | Chobot | Jun 2012 | A1 |
| 20120167957 | Verfuerth et al. | Jul 2012 | A1 |
| 20120182729 | Verfuerth et al. | Jul 2012 | A1 |
| 20120203601 | Verfuerth et al. | Aug 2012 | A1 |
| 20120209755 | Verfuerth et al. | Aug 2012 | A1 |
| 20120229049 | Mohan et al. | Sep 2012 | A1 |
| 20120233045 | Verfuerth et al. | Sep 2012 | A1 |
| 20120235579 | Chemel et al. | Sep 2012 | A1 |
| 20120262074 | Wang-Wei-Chang | Oct 2012 | A1 |
| 20120274222 | Verfuerth et al. | Nov 2012 | A1 |
| 20120286673 | Holland et al. | Nov 2012 | A1 |
| 20120299485 | Mohan et al. | Nov 2012 | A1 |
| 20120326608 | Mohan et al. | Dec 2012 | A1 |
| 20130006437 | Verfuerth et al. | Jan 2013 | A1 |
| 20130020949 | Mohan et al. | Jan 2013 | A1 |
| 20130033183 | Verfuerth et al. | Feb 2013 | A1 |
| 20130063042 | Bora et al. | Mar 2013 | A1 |
| 20130069542 | Curasi et al. | Mar 2013 | A1 |
| 20130069543 | Mohan et al. | Mar 2013 | A1 |
| 20130088168 | Mohan et al. | Apr 2013 | A1 |
| 20130093323 | Radermacher | Apr 2013 | A1 |
| 20130094230 | Verfuerth et al. | Apr 2013 | A1 |
| 20130131882 | Verfuerth et al. | May 2013 | A1 |
| 20130141904 | Verfuerth et al. | Jun 2013 | A1 |
| 20130169185 | Dai et al. | Jul 2013 | A1 |
| 20130176401 | Monari | Jul 2013 | A1 |
| 20130193857 | Tlachac et al. | Aug 2013 | A1 |
| 20130229795 | Wang et al. | Sep 2013 | A1 |
| 20130249410 | Thompson | Sep 2013 | A1 |
| 20130257292 | Verfuerth et al. | Oct 2013 | A1 |
| 20130293117 | Verfuerth | Nov 2013 | A1 |
| 20130293877 | Ramer et al. | Nov 2013 | A1 |
| 20130308325 | Verfuerth et al. | Nov 2013 | A1 |
| 20140001977 | Zacharchuk et al. | Jan 2014 | A1 |
| 20140028199 | Chemel et al. | Jan 2014 | A1 |
| 20140117852 | Zhai et al. | May 2014 | A1 |
| 20140239824 | Li | Aug 2014 | A1 |
| 20140252961 | Ramer et al. | Sep 2014 | A1 |
| 20140265920 | Pederson | Sep 2014 | A1 |
| 20140285090 | Chemel et al. | Sep 2014 | A1 |
| 20140285095 | Chemel et al. | Sep 2014 | A1 |
| 20140292208 | Chemel | Oct 2014 | A1 |
| 20140293605 | Chemel et al. | Oct 2014 | A1 |
| 20140333222 | Chemel et al. | Nov 2014 | A1 |
| 20140375206 | Holland et al. | Dec 2014 | A1 |
| 20150008827 | Carrigan et al. | Jan 2015 | A1 |
| 20150008828 | Carrigan et al. | Jan 2015 | A1 |
| 20150061511 | Chemel et al. | Mar 2015 | A1 |
| 20150184842 | Chemel et al. | Jul 2015 | A1 |
| 20160014856 | Wacheux | Jan 2016 | A1 |
| 20160050725 | Johnson et al. | Feb 2016 | A1 |
| 20160360594 | Chemel et al. | Dec 2016 | A1 |
| 20160374166 | Chen et al. | Dec 2016 | A1 |
| 20170019970 | Chemel et al. | Jan 2017 | A1 |
| 20170027045 | Chemel et al. | Jan 2017 | A1 |
| 20170086279 | Chemel et al. | Mar 2017 | A1 |
| 20170094753 | Lunn et al. | Mar 2017 | A1 |
| 20180160509 | Treible et al. | Jun 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2734757 | Mar 2010 | CA |
| 1873908 | Dec 2006 | CN |
| 101351067 | Jan 2009 | CN |
| 101861007 | Oct 2010 | CN |
| 102591277 | Jul 2012 | CN |
| 2005-073133 | Mar 1993 | JP |
| 2006-106762 | Apr 2006 | JP |
| 2007-045407 | Feb 2007 | JP |
| WO 9620369 | Jul 1996 | WO |
| WO 9834206 | Aug 1998 | WO |
| WO 2007003038 | Jan 2007 | WO |
| WO 2007116332 | Oct 2007 | WO |
| WO 2009003279 | Jan 2009 | WO |
| WO 2009129232 | Oct 2009 | WO |
| WO 2010116283 | Oct 2010 | WO |
| 2012005718 | Jan 2012 | WO |
| WO 2012061709 | May 2012 | WO |
| WO 2012129243 | Sep 2012 | WO |
| WO 2013067389 | May 2013 | WO |
| WO 2013142292 | Sep 2013 | WO |
| Entry |
|---|
| Communication pursuant to Article 94(3) EPC, issued by the European Patent Office for Application No. 13763788.0, dated Apr. 4, 2017, 5 pages. |
| European Search Report issued by the European Patent Office for Application No. 14852889.6, dated May 19, 2017, 8 pages. |
| Examination Report No. 1 issued by the Australian Patent Office for Application No. 2014259974, dated Apr. 3, 2017, 3 pages. |
| Examination Report No. 1 issued by the Australian Patent Office for Application No. 2016206250, dated May 1, 2017, 3 pages. |
| Examination Report No. 2 issued by the Australian Patent Office for Application No. 2015203026, dated May 16, 2017, 3 pages. |
| Extended European Search Report issued by the European Patent Office for Application No. 11838876.8, dated Apr. 11, 2017, 8 pages. |
| Non-Final Office Action in U.S. Appl. No. 14/645,548, dated May 4, 2017, 20 pages. |
| Non-Final Office Action in U.S. Appl. No. 14/927,413, dated May 5, 2017, 12 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/175,725, dated Jun. 1, 2017, 14 pages. |
| Non-Final Office Action in U.S. Appl. No. 14/294,081, dated Jun. 15, 2017, 15 pages. |
| Notice of Allowance in U.S. Appl. No. 14/960,105, dated May 10, 2017, 8 pages. |
| Advisory Action in U.S. Appl. No. 12/831,358, dated Feb. 27, 2014, 2 pages. |
| Albeo Technologies, C Series, http://www.albeotech.com/?site_id=1500&item_id=161711, retrieved May 18, 2011, 2 pages. |
| Albeo Technologies, C3 Series, http://www.albeotech.com/?site_id=1500&item_id=173338, retrieved May 18, 2011, 2 pages. |
| Albeo Technologies, S Series, http://www.albeotech.com/?site_id=1500&item_id=161722, retrieved May 18, 2011, 2 pages. |
| Albeo Technologies, Surface Mounts, http://www.albeotech.com/?site_id=1500&item_id=161724, retrieved May 18, 2011, 2 pages. |
| Beta LED, 227 Series LED Canopy, http://www.betaled.com/us-en/TechnicalLibrary/TechnicalDocuments/227-series-canopy.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, 227 Series LED Sofit, http://www.betaled.com/us-en/TechnicalLibrary/TechnicalDocuments/227-series-soffit.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, 304 Series LED Interior, http://www.betaled.com/us-en/TechnicalLibrary/TechnicalDocuments/304-series-canopy.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, 304 Series LED Parking Structure, http://www.betaled.com/us-en/TechnicalLibrary/TechnicalDocuments/304-series-parking.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, 304 Series LED Sofit, http://www.betaled.com/us-en/TechnicalLibrary/TechnicalDocuments/304-series-soffit.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, The Edge Canopy, http://www.betaled.com/us- en/TechnicalLibrary/TechnicalDocuments/TheEdgeCanopy.aspx, retrieved May 18, 2011, 2 pages. |
| Beta LED, The Edge LED Parking Structure, http://www.betaled.com/us- en/TechnicalLibrary/TechnicalDocuments/TheEdgeParking.aspx, retrieved May 18, 2011, 2 pages. |
| Color Kinetics, eW Cove EC Powercore line, http://www.colorkinetics.com/support/datasheets/eW_Cove_EC_Powercore_2700K_12in_SpecSheet.pdf, retrieved May 18, 2011, 2 pages. |
| Color Kinetics, eW Cove MX Powercore line, http://www.colorkinetics.com/support/datasheets/eW_Cove_MX_Powercore_2700K_Wide_Beam_Angle_SpecSheet.pdf, retrieved May 18, 2011, 2 pages. |
| Color Kinetics, eW Cove QLX Powercore line, http://www.colorkinetics.com/support/datasheets/eW_Cove_QLX_Powercore_6in_110degreex110degree.pdf, retrieved May 18, 2011, 2 pages. |
| Color Kinetics, eW Fuse Powercore line, http://www.colorkinetics.com/support/datasheets/eW_Fuse_Powercore_2700K_10degree_x_60degree.pdf, retrieved May 18, 2011, 2 pages. |
| Color Kinetics, eW Graze Powercore line, http://www.colorkinetics.com/support/datasheets/eW_Graze_Powercore_SpecSheet_2700K_10x60.pdf, retrieved May 18, 2011, 2 pages. |
| “Enlightened Energy Management System,” ETCC Open Forum, 13 pp. (Jul. 24, 2012). |
| Examination Report in Australian Patent Application No. 2009236311, dated May 10, 2013, 3 pages. |
| Examination Report in Australian Patent Application No. 2011323165, dated Aug. 22, 2014, 3 pages. |
| Examination Report in Australian Patent Application No. 2012230991, dated Nov. 18, 2014, 3 pages. |
| Examination Report in Australian Patent Application No. 2012332206, dated Feb. 12, 2015, 3 pages. |
| Examination Report in Australian Patent Application No. 2015255250, dated Jun. 1, 2016, 3 pages. |
| Examination Report in European Patent Application No. 09732558.3, dated Apr. 19, 2016, 5 pages. |
| Extended European Report and Opinion for European Appln No. EP 09732558.3, dated Aug. 23, 2012, 8 pages. |
| Extended European Report and Opinion for European Appln No. EP 12844864.4, dated Nov. 3, 2015, 8 pages. |
| Extended European Report and Opinion for European Patent Application No. EP 13763788.0, dated Dec. 17, 2015, 7 pages. |
| Final Office Action in U.S. Appl. No. 12/817,425 dated Sep. 17, 2015, 9 pages. |
| Final Office Action in U.S. Appl. No. 13/425,295, dated Mar. 7, 2016, 18 pages. |
| Office Action in U.S. Appl. No. 14/294,081, dated Mar. 14, 2016, 20 pages. |
| Final Office Action in U.S. Appl. No. 12/817,425, dated Sep. 15, 2014, 17 pages. |
| Final Office Action in U.S. Appl. No. 13/425,295, dated Jan. 2, 2015, 17 pages. |
| Final Office Action in U.S. Appl. No. 14/294,081 dated Oct. 5, 2016, 20 pages. |
| Final Office Action in U.S. Appl. No. 14/245,196, dated May 27, 2015, 6 pages. |
| Final Office Action in U.S. Appl. No. 14/267,368 dated Dec. 31, 2015, x pages. |
| Final Office Action in U.S. Appl. No. 14/294,081 dated Jun. 10, 2015, 13 pages. |
| Garg, Visha et al., “Smart occupancy sensors to reduce energy consumption, Energy and Buildings,” vol. 32, Issue 1, Jun. 2000, pp. 81-87. ISSN 0378-7788, 10.1 016/S0378-7788(99)00040-7. (http://www.sciencedirect.com/science/article/pii/S037877889. |
| International Preliminary Report on Patentability in International Application No. PCT/US2012/029834, dated Sep. 24, 2013, 7 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/US2012/063372, dated Mar. 19, 2013, 14 pages. |
| International Preliminary Report on Patentability in International Application No. PCT/US2013/031790, dated Sep. 23, 2014, 10 pages. |
| International Preliminary Report on Patentability of PCT/US2009/040514, dated Oct. 19, 2010, 4 pages. |
| International Preliminary Report on Patentability of PCT/US2011/059334, dated May 7, 2013, 8 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2011/059334, dated Feb. 2, 2012, 11 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2012/063372, dated Mar. 19, 2013, 18 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2013/031790, dated Jun. 3, 2013, 13 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2014/35990, dated Sep. 18, 2014, 11 pages. |
| International Search Report and Written Opinion in International Application No. PCT/US2014/060095, dated Jan. 29, 2015, 16 pages. |
| International Search Report and Written Report in International Application No. PCT/US12/029834, dated Jul. 12, 2012, 10 pages. |
| International Search Report in International Application No. PCT/US2009/040514 dated Jun. 26, 2009, 4 pages. |
| Notice of Acceptance for Australian Patent Application No. 2012332206, dated Jan. 21, 2016, 2 pages. |
| Notice of Acceptance in Australian Application No. 2009236311, dated May 28, 2014, 2 pages. |
| Notice of Acceptance in Australian Patent Application No. 2011323165, dated Apr. 10, 2015, 2 pages. |
| Notice of Allowance in U.S. Appl. No. 12/423,543, dated Jun. 21, 2012, 4 pages. |
| Notice of Allowance in U.S. Appl. No. 12/423,543, dated Feb. 8, 2012, 12 pages. |
| Notice of Allowance in U.S. Appl. No. 12/423,543, dated Apr. 11, 2012, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 12/822,421, dated Mar. 1, 2013, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 12/822,577, dated Mar. 15, 2013, 10 pages. |
| Notice of Allowance in U.S. Appl. No. 12/823,195, dated Oct. 27, 2011, 7 pages. |
| Notice of Allowance in U.S. Appl. No. 12/823,195, dated Dec. 12, 2011, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 12/824,797 dated Nov. 9, 2012, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 12/827,336, dated Oct. 2, 2013, 12 pages. |
| Notice of Allowance in U.S. Appl. No. 12/827,397, dated Oct. 29, 2012, 5 pages. |
| Notice of Allowance in U.S. Appl. No. 12/828,340, dated Nov. 21, 2012, 5 pages. |
| Notice of Allowance in U.S. Appl. No. 12/828,495, dated Feb. 19, 2014, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 12/830,868, dated Mar. 25, 2013, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 12/830,868, dated Jun. 24, 2013, 6 pages. |
| Notice of Allowance in U.S. Appl. No. 12/831,358, dated Aug. 29, 2014, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 12/831,476, dated Jun. 11, 2014, 5 pages. |
| Notice of Allowance in U.S. Appl. No. 12/832,179, dated Aug. 1, 2014, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 12/832,211, dated Apr. 23, 2014, 10 pages. |
| Notice of Allowance in U.S. Appl. No. 12/833,181, dated May 23, 2013, 18 pages. |
| Notice of Allowance in U.S. Appl. No. 12/833,332, dated Mar. 21, 2013, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 13/289,492, dated Nov. 19, 2014, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 13/289,492, dated Jan. 23, 2015, 10 pages. |
| Notice of Allowance in U.S. Appl. No. 14/045,679, dated Feb. 20, 2014, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 14/245,196, dated Sep. 9, 2015, 8 pages. |
| Notice of Allowance in U.S. Appl. No. 14/245,196, dated Sep. 23, 2015, 2 pages. |
| Notice of Allowance in U.S. Appl. No. 14/289,601, dated Apr. 1, 2015, 9 pages. |
| Notice of Allowance in U.S. Appl. No. 14/289,601, dated Jun. 4, 2015, 2 pages. |
| Notice of Allowance in U.S. Appl. No. 14/294,082, dated May 19, 2015, 8 pages. |
| Office Action in Canadian Application No. 2,721,486 dated Jul. 14, 2015, 4 pages. |
| Office Action in U.S. Appl. No. 14/267,386, dated Apr. 17, 2015, 30 pages. |
| Office Action in U.S. Appl. No. 14/267,386 dated Aug. 10, 2015, 27 pages. |
| Office Action in Chinese Patent Application No. 201380026132.5 dated Sep. 12, 2015, 17 pages. |
| Office Action in U.S. Appl. No. 13/425,295, dated Jun. 10, 2014, 12 pages. |
| Office Action in U.S. Appl. No. 12/423,543, dated Jun. 27, 2011, 14 pages. |
| Office Action in U.S. Appl. No. 14/960,105, dated Aug. 30, 2016, 50 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Apr. 30, 2012, 18 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Feb. 25, 2015, 6 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Mar. 27, 2014, 16 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Mar. 23, 2016, 9 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Nov. 3, 2011, 14 pages. |
| Office Action in U.S. Appl. No. 12/817,425, dated Sep. 10, 2013, 15 pages. |
| Office Action in U.S. Appl. No. 12/822,421, dated Jan. 19, 2012, 20 pages. |
| Office Action in U.S. Appl. No. 12/822,421, dated Sep. 12, 2012, 16 pages. |
| Office Action in U.S. Appl. No. 12/822,577, dated Apr. 2, 2012, 25 pages. |
| Office Action in U.S. Appl. No. 12/822,577, dated Oct. 11, 2012, 21 pages. |
| Office Action in U.S. Appl. No. 12/824,797, dated Jun. 29, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/827,209, dated Jan. 10, 2014, 20 pages. |
| Office Action in U.S. Appl. No. 12/827,336, dated Jun. 13, 2013, 6 pages. |
| Office Action in U.S. Appl. No. 12/827,336, dated Oct. 4, 2012, 26 pages. |
| Office Action in U.S. Appl. No. 12/827,397, dated Jul. 11, 2012, 6 pages. |
| Office Action in U.S. Appl. No. 12/828,340, dated Jul. 2, 2012, 4 pages. |
| Office Action in U.S. Appl. No. 12/828,385, dated Mar. 19, 2013, 12 pages. |
| Office Action in U.S. Appl. No. 12/828,385, dated Sep. 12, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/828,495, dated Dec. 12, 2012, 21 pages. |
| Office Action in U.S. Appl. No. 12/828,495, dated May 17, 2012, 6 pages. |
| Office Action in U.S. Appl. No. 12/828,495, dated Mar. 28, 2013, 22 pages. |
| Office Action in U.S. Appl. No. 12/828,495, dated Oct. 10, 2013, 25 pages. |
| Office Action in U.S. Appl. No. 12/830,868, dated Aug. 13, 2012, 26 pages. |
| Office Action in U.S. Appl. No. 12/830,868, dated Mar. 5, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/831,358, dated Jun. 13, 2013, 7 pages. |
| Office Action in U.S. Appl. No. 12/831,358, dated Nov. 19, 2013, 16 pages. |
| Office Action in U.S. Appl. No. 12/831,476, dated Apr. 11, 2012, 7 pages. |
| Office Action in U.S. Appl. No. 12/831,476, dated Feb. 13, 2013, 42 pages. |
| Office Action in U.S. Appl. No. 12/831,476, dated Jul. 23, 2013, 42 pages. |
| Office Action in U.S. Appl. No. 12/831,476, dated Nov. 21, 2013, 52 pages. |
| Office Action in U.S. Appl. No. 12/831,476, dated Oct. 17, 2012, 36 pages. |
| Office Action in U.S. Appl. No. 12/832,179, dated Feb. 21, 2014, 16 pages. |
| Office Action in U.S. Appl. No. 12/832,179, dated Jul. 17, 2013, 15 pages. |
| Office Action in U.S. Appl. No. 12/832,179, dated Mar. 13, 2013, 13 pages. |
| Office Action in U.S. Appl. No. 12/832,179, dated Sep. 12, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/832,211, dated Jun. 20, 2013, 12 pages. |
| Office Action in U.S. Appl. No. 12/832,211, dated Oct. 2, 2013, 13 pages. |
| Office Action in U.S. Appl. No. 12/832,211, dated Sep. 12, 2012, 4 pages. |
| Office Action in U.S. Appl. No. 12/833,181, dated Sep. 12, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/833,332 dated Nov. 23, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 12/833,332, dated Aug. 20, 2012, 5 pages. |
| Office Action in U.S. Appl. No. 13/289,492, dated Aug. 5, 2014, 29 pages. |
| Office Action in U.S. Appl. No. 13/289,492, dated Feb. 27, 2014, 28 pages. |
| Office Action in U.S. Appl. No. 13/425,295 dated Jun. 29, 2015, 17 pages. |
| Office Action in U.S. Appl. No. 14/245,196, dated Feb. 9, 2015, 13 pages. |
| Office Action in U.S. Appl. No. 14/289,601, dated Jan. 30, 2015, 6 pages. |
| Office Action in U.S. Appl. No. 14/294,081, dated Jan. 22, 2015, 7 pages. |
| Office Action in U.S. Appl. No. 14/294,082, dated Jan. 2, 2015, 10 pages. |
| Patent Examination Report No. 1 for Australian Patent Application No. 2013235436, dated Jan. 18, 2016, 3 pages. |
| Progress Report: Reducing Barriers to Use of High Efficiency Lighting Systems; Oct. 2001, (http://www.lrc.rpi.edu/researchAreas/reducingBarriers/pdf/year1FinalReport.pdf), 108 pages. |
| Restriction Requirement in U.S. Appl. No. 12/817,425, dated Dec. 10, 2014, 6 pages. |
| Restriction Requirement in U.S. Appl. No. 14/294,081, dated Oct. 9, 2014, 6 pages. |
| Second Office Action in Chinese Patent Application No. 201380026132.5, dated Apr. 20, 2016, 6 pages (w/English translation). |
| Vainio, A.-M. et al., Learning and adaptive fuzzy control system for smart home, Mar. 2008, http://www.springerlink.com/content/ll72k32006l4qx81/fulltext.pdf, 10 pages. |
| Written Opinion in International Application No. PCT/US2009/040514, dated Jun. 26, 2009, 3 pages. |
| ZigBee Alliance “Wireless Sensors and Control Networks: Enabling New Opportunities with ZigBee”, Bob Heile, Chairman, ZigBee Alliance, Dec. 2006 Powerpoint Presentation, 53 pages. |
| ZigBee Alliance Document No. 08006r03, Jun. 2008, ZigBee-200y Layer Pics and Stack Profile, Copyright © 1996-2008 by the ZigBee Alliance. 2400 Camino Ramon, Suite 375, San Ramon, CA 94583, USA; http://www.zigbee.org, 119 pages. |
| ZigBee Specification Document 053474r17, Notice of Use and Disclosure; Jan. 17, 2008 11:09 A.M., Sponsored by: ZibEe Alliance; Copyright © 2007 ZigBee Standards Organizat. All rights reserved, 602 pages. |
| Final Office Action in U.S. Appl. No. 12/817,425 dated Dec. 15, 2016. |
| Supplementary European Search Report dated Nov. 28, 2016 in European Application No. EP 14 79 1232, 6 pages. |
| International Search Report and Written Opinion dated Oct. 14, 2016 in International Application No. PCT/US2016/043893, 14 pages. |
| Final Office Action in U.S. Appl. No. 12/817,425 dated Dec. 15, 2016, 10 pages. |
| Office Action in U.S. Appl. No. 14/518,831 dated Dec. 30, 2016, 51 pp. |
| Communication pursuant to Article 94(3) EPC, issued by the European Patent Office for Application No. 12761180.4, dated Jan. 27, 2017, 5 pages. |
| Office Action issued by the Canadian Patent Office for Application No. 2721486, dated Oct. 14, 2016, 4 pages. |
| Notice of Acceptance issued by the Australian Patent Office for Application No. 2014218445, dated Jul. 15, 2016, 2 pages. |
| Notice of Acceptance issued by the Australian Patent Office for Application No. 2015255250, dated Jan. 24, 2017, 3 pages. |
| Notification of Fulfilling of Registration Formality issued by the Patent Office of the People's Republic of China for Application No. 201380026132.5, dated Aug. 3, 2016 (English Translation), 2 pages. |
| Notice of Acceptance issued by the Australian Patent Office for Application No. 2013235436, dated Nov. 16, 2016, 2 pages. |
| Examination Report No. 1 dated Oct. 14, 2016 in Australian Patent Application No. 2015203026, 2 pages. |
| U.S. Appl. No. 10/009,969, filed Jun. 26, 2018, Knode et al. |
| Examination Report in European Application No. 12844864.4, dated May 8, 2018, 6 pages. |
| Examination Report No. 1 in Australian Application No. 2014331746, dated Jun. 27, 2018, 3 pages. |
| Final Office Action in U.S. Appl. No. 12/817,425, dated Jun. 13, 2018, 39 pages. |
| Final Office Action in U.S. Appl. No. 15/728,618, dated Jul. 10, 2018, 10 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/218,851, dated Jul. 24, 2018, 18 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/916,234, dated Apr. 26, 2018, 13 pages. |
| Notice of Allowance in U.S. Appl. No. 15/094,559, dated Jun. 27, 2018, 14 pages. |
| Notice of Allowance in U.S. Appl. No. 14/645,548, dated Oct. 20, 2017, 12 pages. |
| Notice of Allowance in U.S. Appl. No. 14/927,413, dated Nov. 7, 2017, 14 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/094,559, dated Sep. 28, 2017, 29 pages. |
| Office Action issued by the Canadian Patent Office for Application No. 2,721,486, dated Sep. 19, 2017, 3 pages. |
| Office Action issued by the Canadian Patent Office for Application No. 2,816,978, dated Oct. 3, 2017, 4 pages. |
| Examination Report No. 1 issued by the Australian Patent Office for Application No. 2017202824, dated Jan. 15, 2018, 4 pages. |
| Final Office Action in U.S. Appl. No. 15/175,725, dated Jan. 9, 2018, 14 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/218,851, dated Jan. 25, 2018, 16 pages. |
| Examination Report issued by the Canadian Patent Office for Application No. 2,830,991, dated Jul. 13, 2017, 3 pages. |
| Examination Report issued by the European Patent Office for Application No. 12844864.4, dated Aug. 16, 2017, 3 pages. |
| Examination Report No. 1 issued by the Australian Patent Office for Application No. 2016202824, dated Jul. 17, 2017, 6 pages. |
| Examination Report No. 1 issued by the Australian Patent Office for Application No. 2017201414, dated Jun. 6, 2017, 3 pages. |
| Non-Final Office Action in U.S. Appl. No. 12/817,425, dated Aug. 3, 2017, 17 pages. |
| Notice of Allowance in U.S. Appl. No. 14/518,831, dated Aug. 21, 2017, 13 pages. |
| Notice of Allowance in U.S. Appl. No. 14/960,105, dated Jul. 12, 2017, 6 pages. |
| Office Action issued by the European Patent Office for Application No. 12 761 180.4, dated Aug. 24, 2017, 5 pages. |
| Advisory Action in U.S. Appl. No. 15/175,725, dated Apr. 19, 2018, 4 pages. |
| Examination Report in European Patent Application No. 12761180.4, dated Apr. 11, 2018, 5 pages. |
| Examination Report in European Patent Application No. 13763788.0, dated Apr. 10, 2018, 6 pages. |
| Final Office Action in U.S. Appl. No. 14/294,081, dated Mar. 9, 2018, 14 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/367,125, dated Apr. 6, 2018, 14 pages. |
| Non-Final Office Action in U.S. Appl. No. 15/728,618, dated Mar. 1, 2018, 4 pages. |
| Amy Feng, Office Action and Search Report in Chinese Application No. 201610908188.9, dated Jul. 30, 2018, 6 pages, State Intellectual Property Office of People's Republic of China, Beijing China. |
| Number | Date | Country | |
|---|---|---|---|
| 20170042001 A1 | Feb 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61577354 | Dec 2011 | US | |
| 61555075 | Nov 2011 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14267386 | May 2014 | US |
| Child | 15298064 | US | |
| Parent | PCT/US2012/063372 | Nov 2012 | US |
| Child | 14267386 | US |
