Patent Grant
11375599
The present disclosure relates to illumination, and more particularly to control of illumination devices and systems.
Luminaires enjoy widespread use in a variety of industrial, commercial, and municipal applications. Such applications can include general or area lighting of workspaces, roadways, parking lots, and the like. Multiple luminaires are typically arranged in patterns and positioned at intervals sufficient to provide a minimum overall level of illumination across the area of interest. For example, luminaires may be spaced at intervals along a driveway in a multilevel parking garage to provide an overall level of illumination that permits safe ingress and egress by pedestrians as well as permits safe operation of motor vehicles within the parking garage. In a similar manner, luminaires may be spaced at intervals throughout a commercial center parking lot to promote safe operation of motor vehicles, permit safe ingress and egress by customers, and foster a sense of safety and well-being for business patrons within the commercial center. Similarly, a number of luminaires may be spaced along a roadway to provide a level of illumination permitting safe operation of motor vehicles on the roadway and, where applicable, safe passage of pedestrians on sidewalks adjoining the roadway.
To simplify power distribution and control wiring, such luminaires may be organized into groups or similar hierarchical power and control structures. For example, multiple luminaires along a roadway may be grouped together on a common power circuit that is controlled using a single, centralized controller to collectively adjust the luminous output of all of the luminaires in the group. In another instance, multiple luminaires within a parking garage may be controlled using a single photocell mounted on the exterior of the parking garage. Such installations may however compromise operational flexibility for ease of installation and simplicity of operation.
Energy conservation has become of ever-increasing importance. Efficient use of energy can result in a variety of benefits, including financial benefits such as cost savings and environmental benefits such as preservation of natural resources and reduction in “green house” (e.g., CO2) gas emissions.
Residential, commercial, and street lighting which illuminate interior and exterior spaces consume a significant amount of energy. Conventional lighting devices or luminaires exist in a broad range of designs, suitable for various uses. Lighting devices employ a variety of conventional light sources, for example incandescent lamps, fluorescent lamps such as high-intensity discharge (HID) lamps (e.g., mercury vapor lamps, high-pressure sodium lamps, metal halide lamps).
There appears to be at least two primary approaches to reducing energy consumption associated with lighting systems. One approach employs higher efficiency light sources. The other approach selectively provides light only when needed.
Use of higher efficiency light sources may, for instance, include replacing incandescent lamps with fluorescent lamps or even with solid-state light sources (e.g., light emitting diodes (LEDs), organic LEDs (OLEDs), polymer LEDs (PLEDs)) to increase energy efficiency. In some instances, these higher efficiency light sources may present a number of problems. For example, fluorescent light sources may take a relatively long time after being turned ON to achieve their full rated level of output light or illumination. Such light sources also typically have a high energy consumption during warm-up. Many higher efficiency light sources emit light with a low color rendering index (CRI). For reference, sunlight has a CRI of 100 and represents “ideal light” which contains a continuous spectrum of visible radiation. Low CRI light is less pleasing to the human eye. Surfaces illuminated with low CRI light may not be perceived in their “true” color. Low CRI light makes it more difficult to discern details, often requiring a higher level of output light or illumination to discern details that would otherwise be discernable in high CRI light. Further, higher efficiency light sources may require additional circuitry (e.g., ballasts) and/or thermal management techniques (e.g., passive or active cooling).
Providing illumination only when needed can be achieved manually by a user of the lighting system, or automatically by a control mechanism. Automatic control mechanisms generally fall into two broad categories, timers and environmental sensors. Timer based control mechanisms turn light sources ON and OFF based on time. The times are typically user configurable. Such relies on the user to account for changes or variations in the length of daylight in a 24 hour cycle which may occur throughout a year. Very often, timer based control mechanisms are set once and never updated.
Environmental sensor based control mechanisms sense light or illumination levels and/or motion or proximity. Light or illumination level based control mechanisms are commonly referred to as dusk-to-dawn sensors. Dusk-to-dawn light or illumination level based control mechanisms turn the light sources ON when a level of light or illumination in an environment falls below a turn ON threshold (i.e., dusk threshold), and turn the light sources OFF when the level of light or illumination exceeds a turn OFF threshold (i.e., dawn threshold). Light or illumination level based control subsystems advantageously automatically accommodate changes in length of day light throughout the year.
Example outdoor lighting systems may include a number of individual luminaires mounted on poles and that are each controlled by a photocontrol (or other mechanism) that controls the AC power to the luminaire for daytime and nighttime operation. This is often accomplished through a standard wired 3-pin twist-lock receptacle (e.g., ANSI C136.10 compliant receptacle) on the luminaire that mates with a compatible photocontrol plug interface (e.g., ANSI C136.10 compliant plug). The photocontrol switches the luminaire power ON/OFF based on the dusk/dawn events. There are also scenarios where groups of luminaires are controlled together by an AC contactor that activates power to the group as a whole, and controlled by a photocontrol, timer, etc.
More elaborate lighting networks may cover a large area, such as a city, and may include numerous individual luminaires outfitted with network communication nodes that can each be controlled by a remotely located central management system (CMS). Communication between the luminaires and the CMS may be enabled through mesh or mobile wireless networks, or through powerline communications. The network nodes may additionally offer more capabilities to control the luminaires, such as dimming to specific levels and varying illumination with time, metering of the power being consumed by the luminaire, maintenance alerts regarding luminaire failure or malfunction, and ability to commission and/or decommission the luminaires remotely.
A wireless adapter system may be summarize as including: an adapter system physical luminaire interface that is physically coupleable to a physical luminaire interface of a luminaire to receive alternating current (AC) power from the luminaire; a first adapter system transceiver that in operation wirelessly communicates with a luminaire transceiver of the luminaire; at least one processor communicatively coupled to the first adapter system transceiver; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one processor and storing at least one of data or instructions which, when executed by the at least one processor, cause the at least one processor to: cause the first adapter system transceiver to at least one of: wirelessly send data or instructions to the luminaire; or wirelessly receive data or instructions from the luminaire.
The adapter system physical luminaire interface may include a 3-wire interface comprising an AC line connection, an AC neutral connection, and an AC switched line connection. The adapter system physical luminaire interface may include a twist lock plug. The adapter system physical luminaire interface may be selectively physically coupleable to a control node physical node interface of a control node in an integrated housing.
The wireless adapter system may include an adapter system physical node interface that is selectively physically coupleable to a control node physical node interface of a control node. The adapter system physical node interface may include one of a 5-pin receptacle interface or a 7-pin receptacle interface. In operation, the adapter system physical node interface may provide AC power from the physical luminaire interface of the luminaire to the control node physical node interface of the control node. In operation, the adapter system physical luminaire interface may couple an AC line connection, a neutral connection, and a switched line connection of the luminaire to the control node physical node interface of the control node. In operation, the adapter system physical node interface may enable power switching to and power measurement of the luminaire by the control node.
The at least one processor of the wireless adapter system may: receive, via the adapter system physical node interface, at least one of instructions or data; and cause the first adapter system transceiver to wirelessly send the received at least one of instructions or data to the luminaire in a format that is readable by the luminaire. The at least one processor may: receive, via the adapter system transceiver, at least one of instructions or data from the luminaire; and send, via the adapter system physical node interface, the received at least one of instructions or data to the control node. The at least one processor may include at least one of an analog dimming receiver or a digitally addressable lighting interface (DALI) transceiver. The adapter system physical luminaire interface, adapter system physical node interface, and the first adapter system transceiver may all be disposed in an adapter system housing.
The wireless adapter system may include a second adapter system transceiver that in operation communicates wirelessly with an external device over a wireless network. The at least one processor may: receive, via the second adapter system transceiver, at least one of instructions or data; and cause the first adapter system transceiver to wirelessly send the received at least one of instructions or data to the luminaire in a format that is readable by the luminaire. The at least one processor may: receive, via the first adapter system transceiver, at least one of instructions or data from the luminaire; and send, via the second adapter system transceiver, the received at least one of instructions or data to an external device over at least one communications network.
A method of operating a luminaire may be summarized as including: providing a wireless adapter system comprising an adapter system physical luminaire interface, a first adapter system transceiver, and at least one processor communicatively coupled to the first adapter system transceiver; physically coupling the adapter system physical luminaire interface of the wireless adapter system to a luminaire physical node interface of a luminaire to receive alternating current (AC) power from the luminaire; and causing, by the at least one processor, the first adapter system transceiver to at least one of wirelessly send data or instructions to the luminaire or wirelessly receive data or instructions from the luminaire.
The adapter system physical luminaire interface may include a 3-wire interface comprising an AC line connection, an AC neutral connection, and an AC switched line connection, and physically coupling the adapter system physical luminaire interface of the wireless adapter system to a luminaire physical node interface may include physically coupling the AC line connection, the AC neutral connection, and the AC switched line connection to circuitry of the luminaire. The adapter system physical luminaire interface may include a twist lock plug and physically coupling the adapter system physical luminaire interface of the wireless adapter system to a luminaire physical node interface may include physically coupling the twist lock plug to a receptacle of the luminaire. The adapter system physical luminaire interface may be selectively physically coupleable to a control node physical node interface of a control node in an integrated housing.
The wireless adapter system may include an adapter system physical node interface, and the method may further include physically coupling the adapter system physical node interface to a control node physical node interface of a control node. The adapter system physical node interface may include one of a 5-pin receptacle interface or a 7-pin receptacle interface, and physically coupling the adapter system physical node interface to a control node physical node interface of a control node may include physically coupling the one of a 5-pin receptacle interface or the 7-pin receptacle interface to a plug of the control node. The method may include providing, via the adapter system physical luminaire interface, AC power from the physical luminaire interface of the luminaire to the control node physical node interface of the control node. The method may include receiving, by the at least one processor via the adapter system physical node interface, at least one of instructions or data; and causing, by the at least one processor, the first adapter system transceiver to wirelessly send the received at least one of instructions or data to the luminaire in a format that is readable by the luminaire. The method may include receiving, by the at least one processor via the first adapter system transceiver, at least one of instructions or data from the luminaire; and sending, by the at least one processor via the adapter system physical node interface, the received at least one of instructions or data to the control node.
The wireless adapter system may include a second adapter system transceiver, and the method may further include communicating, via the second adapter system transceiver, wirelessly with an external device over a wireless network. The method may include receiving, by the at least one processor via the second adapter system transceiver, at least one of instructions or data; and causing, by the at least one processor, the first adapter system transceiver to wirelessly send the received at least one of instructions or data to the luminaire in a format that is readable by the luminaire. The method may include receiving, by the at least one processor via the first adapter system transceiver, at least one of instructions or data from the luminaire; and sending, by the at least one processor via the second adapter system transceiver, the received at least one of instructions or data to an external device over at least one communications network.
An illumination system may be summarized as including: a plurality of terminal luminaires, each of the terminal luminaires including: at least one terminal luminaire processor; at least one light source operatively coupled to the at least one terminal luminaire processor; a terminal luminaire transceiver operatively coupled to the at least one terminal luminaire processor, in operation the terminal luminaire transceiver communicates via a first communications protocol; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one terminal luminaire processor and storing at least one of data or instructions; a gateway luminaire including: at least one gateway luminaire processor; at least one light source operatively coupled to the at least one gateway luminaire processor; a first gateway luminaire transceiver operatively coupled to the at least one gateway luminaire processor, in operation the first gateway luminaire transceiver communicates via the first communications protocol; a second gateway luminaire transceiver operatively coupled to the at least one gateway luminaire processor, in operation the second gateway luminaire transceiver communicates via a second communications protocol, the second communications protocol different from the first communications protocol; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one gateway luminaire processor and storing at least one of data or instructions which, when executed by the at least one gateway luminaire processor, cause the at least one gateway luminaire processor to: receive, via the second gateway luminaire transceiver, at least one of instructions or data from at least one mobile system; and send, via the first gateway luminaire transceiver, the received at least one of instructions or data to at least one of the plurality of terminal luminaires.
At least some of the plurality of terminal luminaires may communicate with other of the plurality of terminal luminaires using the first communications protocol via respective terminal luminaire transceivers. Each of the plurality of terminal luminaires may communicate with at least one gateway luminaire using the first communications protocol via respective terminal luminaire transceivers. The first and second communication protocols may be wireless communications protocols, the first and second communications protocols may have first and second ranges, respectively, and the first range may be greater than the second range. The at least one gateway luminaire processor: may receive, via the second gateway luminaire transceiver, at least one of commissioning data, decommissioning data, dimming level data, light schedule data, firmware update data or operational parameter data from the at least one mobile system. The at least one gateway luminaire processor: may receive, via the first gateway luminaire transceiver, at least one of instructions or data from at least one of the plurality of terminal luminaires; and may send, via the second gateway luminaire transceiver, the received at least one of instructions or data to the at least one mobile system. The illumination system may further include: a mobile system including: at least one mobile system processor; a first mobile system transceiver operatively coupled to the at least one mobile system processor, in operation the first mobile system transceiver communicates via the second communications protocol; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one mobile system processor and storing at least one of data or instructions which, when executed by the at least one mobile system processor, may cause the at least one mobile system processor to: send, via the first mobile system transceiver, at least one of instructions or data to the gateway luminaire; or receive, via the first mobile system transceiver, at least one of instructions or data from the gateway luminaire. The mobile system may include: a second mobile system transceiver operatively coupled to the at least one mobile system processor, wherein the at least one mobile system processor: may send, via the second mobile system transceiver, at least one of instructions or data to at least one remote processor-based device; or may receive, via the second mobile system transceiver, at least one of instructions or data from the remote processor-based device. The second mobile system transceiver may communicate via the first communications protocol. The second mobile system transceiver may communicate via a third communications protocol, the third communications protocol different from the first and second communications protocols. The third communications protocol may include a mobile telecommunications protocol. The at least one terminal luminaire processor: may receive, via the terminal luminaire transceiver, sensor data from at least one sensor; and may send, via the terminal luminaire transceiver, the received sensor data to the gateway luminaire. The at least one terminal luminaire processor: may store the sensor data temporarily in the nontransitory processor-readable storage medium of the terminal luminaire. The at least one sensor may include at least one of a motion sensor, a temperature sensor, a humidity sensor, a carbon monoxide sensor, a noise sensor, or a gunshot detection sensor. The illumination system may further include: a data storage device, including: at least one data storage device processor; a data storage device transceiver operatively coupled to the at least one data storage device processor; and at least one data storage device nontransitory processor-readable storage medium operatively coupled to the at least one data storage device processor and storing at least one of data or instructions which, when executed by the at least one data storage device processor, may cause the at least one data storage device processor to: receive, via the data storage device transceiver, sensor; and store the received sensor data in the at least one data storage device nontransitory processor-readable storage medium. The at least one gateway luminaire processor: may receive, via the first gateway luminaire transceiver, sensor data from at least one of the terminal luminaires; and may send, via the second gateway luminaire transceiver, the received sensor data to the at least one mobile system. The at least one sensor may include at least one of a motion sensor, a temperature sensor, a humidity sensor, a carbon monoxide sensor, a noise sensor, or a gunshot detection sensor.
A method of operating an illumination system, the illumination system including a plurality of terminal luminaires each including a terminal luminaire transceiver which communicates via a first communications protocol and a gateway luminaire including first and second gateway transceivers which communicate via first and second communications protocols, respectively, the method may be summarized as including: receiving, via the second gateway luminaire transceiver, at least one of instructions or data from at least one mobile system via the second communications protocol; and sending, via the first gateway luminaire transceiver, the received at least one of instructions or data to at least one of the plurality of terminal luminaires via the first communications protocol.
Receiving at least one of instructions or data from at least one mobile system may include receiving at least one of commissioning data, decommissioning data, dimming level data, light schedule data, firmware update data or operational parameter data from the at least one mobile system. The method may further include: receiving, via the first gateway luminaire transceiver, luminaire information from at least one of the terminal luminaires, the luminaire information including at least one of identifier information, operational information, or maintenance information for at least one of the terminal luminaires; and sending, via the second gateway luminaire transceiver, the received luminaire information to the at least one mobile system. The method may further include: receiving, via the first gateway luminaire transceiver, at least one of instructions or data from at least one of the plurality of terminal luminaires; and sending, via the second gateway luminaire transceiver, the received at least one of instructions or data to the at least one mobile system. The method may further include: sending, via a first mobile system transceiver of a mobile system, at least one of instructions or data to the gateway luminaire via the second communications protocol; or receiving, via the first mobile system transceiver of the mobile system, at least one of instructions or data from the gateway luminaire via the second communications protocol. The method may further include: sending, via a second mobile system transceiver of the mobile system, at least one of instructions or data to at least one remote processor-based device; or receiving, via the second mobile system transceiver of the mobile system, at least one of instructions or data from the gateway luminaire. Sending or receiving via the second mobile system transceiver may include sending or receiving at least one of instructions or data via the first communications protocol. Sending or receiving via the second mobile system transceiver may include sending or receiving at least one of instructions or data via a third communications protocol, the third communications protocol different from the first and second communications protocols. Sending or receiving via the second mobile system may include sending or receiving at least one of instructions or data via the third communications protocol, the third communications protocol including a mobile telecommunications protocol. The method may further include: receiving, via a data storage device transceiver communicatively coupled to a data storage device, sensor data; and storing the received sensor data in at least one data storage device nontransitory processor-readable storage medium of the data storage device. The method may further include: receiving, via a terminal luminaire transceiver of one of the plurality of terminal luminaires, sensor data from at least one sensor; and sending, via the terminal luminaire transceiver, the received sensor data to the gateway luminaire. Receiving sensor data from the at least one sensor may include receiving sensor data from at least one sensor which includes at least one of: a motion sensor, a temperature sensor, a humidity sensor, a carbon monoxide sensor, a noise sensor, or a gunshot detection sensor. The method may further include: receiving, via first gateway luminaire transceiver, sensor data from at least one of the terminal luminaires; and sending, via the second gateway luminaire transceiver, the received sensor data to the at least one mobile system. Receiving sensor data may include receiving sensor data which originates from at least one of: a motion sensor, a temperature sensor, a humidity sensor, a carbon monoxide sensor, a noise sensor, or a gunshot detection sensor.
An illumination system may be summarized as including: a plurality of terminal luminaires, each of the terminal luminaires including: at least one terminal luminaire processor; at least one light source operatively coupled to the at least one terminal luminaire processor; a terminal luminaire transceiver operatively coupled to the at least one terminal luminaire processor, in operation the terminal luminaire transceiver communicates via a first communications protocol; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one terminal luminaire processor and storing at least one of data or instructions; a gateway luminaire including: at least one gateway luminaire processor; at least one light source operatively coupled to the at least one gateway luminaire processor; a first gateway luminaire transceiver operatively coupled to the at least one gateway luminaire processor, in operation the first gateway luminaire transceiver communicates via the first communications protocol; a second gateway luminaire transceiver operatively coupled to the at least one gateway luminaire processor, in operation the second gateway luminaire transceiver communicates via a second communications protocol, the second communications protocol different from the first communications protocol; and at least one nontransitory processor-readable storage medium operatively coupled to the at least one gateway luminaire processor and storing at least one of data or instructions which, when executed by the at least one gateway luminaire processor, cause the at least one gateway luminaire processor to: receive, via the first gateway luminaire transceiver, at least one of instructions or data from at least one of the plurality of terminal luminaires; and send, via the second gateway luminaire transceiver, the received at least one of instructions or data to at least one mobile system.
In the drawings, identical reference numbers identify similar elements or acts. The sizes and relative positions of elements in the drawings are not necessarily drawn to scale. For example, the shapes of various elements and angles are not necessarily drawn to scale, and some of these elements may be arbitrarily enlarged and positioned to improve drawing legibility. Further, the particular shapes of the elements as drawn, are not necessarily intended to convey any information regarding the actual shape of the particular elements, and may have been solely selected for ease of recognition in the drawings.
In the following description, certain specific details are set forth in order to provide a thorough understanding of various disclosed implementations. However, one skilled in the relevant art will recognize that implementations may be practiced without one or more of these specific details, or with other methods, components, materials, etc. In other instances, well-known structures associated with computer systems, server computers, and/or communications networks have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the implementations.
Unless the context requires otherwise, throughout the specification and claims that follow, the word “comprising” is synonymous with “including,” and is inclusive or open-ended (i.e., does not exclude additional, unrecited elements or method acts).
Reference throughout this specification to “one implementation” or “an implementation” means that a particular feature, structure or characteristic described in connection with the implementation is included in at least one implementation. Thus, the appearances of the phrases “in one implementation” or “in an implementation” in various places throughout this specification are not necessarily all referring to the same implementation. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more implementations.
As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. It should also be noted that the term “or” is generally employed in its sense including “and/or” unless the context clearly dictates otherwise.
The headings and Abstract of the Disclosure provided herein are for convenience only and do not interpret the scope or meaning of the implementations.
More elaborate lighting networks may cover a large area, such as a park, highway, or city, and may include numerous individual luminaires outfitted with network communication nodes or “lamp control nodes” that can each be controlled by a remotely located central management system (CMS). Communication between the luminaires and the CMS may be enabled through mesh or mobile wireless networks, or through powerline communications. In addition to photocontrol capability, the lamp control nodes may additionally offer more capabilities to control the luminaires, such as dimming to specific levels and varying illumination with time, metering of the power being consumed by the luminaire, maintenance alerts regarding luminaire failure or malfunction, and ability to commission and/or decommission the luminaires remotely.
These extended capabilities are accomplished through an expanded version of the three wire twist-lock receptacle that includes more interface pins (e.g., 5 or 7 total pins) and wires for dimming control and for reading status signals from the luminaire. This expanded version is described in the ANSI C136.41 standard. The extra pins or pads allow dimming through a standard 0-10 V analog interface or through a digital lighting protocol referred to as Digitally Addressable Lighting Interface (DALI) that typically interfaces to the power control electronics in the luminaire. The extra control lines usually route to specialized lighting drivers of the luminaire that recognize the specific control input appropriately.
A problem arises when an existing street light luminaire is being upgraded in the field to the 5-pin or 7-pin (e.g., ANSI C136.41) network control capabilities from the traditional 3-pin interface (e.g., ANSI C136.10). At a minimum, the 3-pin receptacle on the luminaire needs to be replaced by the 5-pin or 7-pin version and the wires connected appropriately. In most cases, the existing driver electronics for the lighting of the luminaire have no connections available for the extra control lines from the receptacle unless the driver was originally specified to be a more advanced model. The result is that the driver of the luminaire is also replaced and is likely a major percentage of the cost of the entire luminaire, not including the labor involved in the replacement. This would be a normal scenario in upgrading many of the already-deployed LED street and roadway luminaires to date, as the network control rollouts are in their infancy with few deployed.
The problem is compounded for decorative post top street and area lights, most of which have not yet converted to LED lighting. The majority of these post top lights have internal electronics housed at the base of the light fixture or at the base of the pole. They often include the standard 3-pin receptacle and photocontrol either on top of the post top fixture, or tucked away inside with the other electronics with a peep hole for the photocontrol sensor. In this scenario, the only viable solution for upgrading the luminaire to LED lighting and including the ability to support the 5-pin or 7-pin control node is to replace the entire luminaire with a modern unit. This can be very expensive, especially for highly ornate fixtures, and it may be impossible to duplicate the look of older, historical luminaires with modern replacements.
One or more implementations of the present disclosure provide systems, methods and articles which leverage the wireless communication capability present in wireless-enabled luminaires where the lamps include a short-range wireless transceiver (e.g. Bluetooth® transceiver) and can be controlled by a CMS and/or a smart appliance (e.g., smartphone, tablet computer, laptop computer). In at least some implementations, the wireless capability embedded in the luminaire may be paired with a second compatible wireless interface to standard plug-in photocontrols and wireless lamp control nodes, or any wireless-enabled control device (e.g., secondary communications network node, secondary control appliance) of any form factor within proximity of the luminaire.
In at least some implementations, a wireless adapter system may be provided that replaces the standard 3-pin, 5-pin or 7-pin wired receptacle. The wireless adapter system may include a 3-wire interface (e.g., line, neutral, switched line) to the luminaire which provides power to the wireless adapter system. The wireless adapter system may include a receptacle interface (e.g., 5-pin, 7-pin) that receives a plug (e.g., 3-pin, 5-pin, 7-pin) of a control device, such as photocontrol or a networked control node. The wireless adapter system may also include a wireless interface circuit that communicates control, status or other data between the connected control device and the luminaire. The wireless adapter system may accumulate information (e.g., operational status, power draw) from multiple luminaires of a secondary communications network or communications subnetwork and provide the accumulated information or an aggregation of the accumulated information to a central management system via a primary communications network (e.g., mobile or cellular communications network). Additionally or alternatively, the wireless adapter system may accumulate instructions received from a central management system via a primary communications network (e.g., mobile or cellular communications network) and provide the instructions one or more luminaries via a secondary communications network or communications subnetwork. Thus, the wireless adapter system advantageously makes a plurality or group of luminaries appear as a single luminaire to the central management system. In at least some implementations, the wireless interface circuit may replace some or all of the control lines from any control device while offering the same capabilities available to the smart appliance.
The wireless adapter system 102 also includes a short-range wireless interface circuit 120 (e.g., Bluetooth® radio, WiFi® radio) disposed in the housing 104. In operation, the wireless adapter system 102 receives via the wired receptacle interface 106 ON/OFF, dimming, or other commands or data from the control node 112 and autonomously interprets or translates those signals using one or more processors, for example. The received interpreted signals are translated into wireless signals that are transmitted by the wireless interface circuit 120 of the adapter system 102 and received by the wireless-enabled luminaire 118, as well as by other wireless-enabled luminaire within a range of the wireless signals. Similarly, the adapter system 102 may receive via the wireless interface circuit 120 signals encoding data or instructions from the luminaire 118, as well as from other wireless-enabled luminaire within a range of the wireless signals, and may interpret and transmit the signals to the control node 112 via the wired receptacle interface 106. As described herein, the adapter system 102 may accumulate, aggregate and store data or information received from one or a plurality of luminaires 118, and/or provide an accumulated or aggregated representation of the information to a remotely located central management system (CMS) 124. The instructions or commands may be in the form of switch-controlled ON/OFF signals, analog dimming with dim-to-off capability (e.g., 0-10 V), digital control and status commands (e.g., DALI), or any other types of signals.
As noted above, the luminaire 118, as well as other luminaires within the vicinity, may contain one or more short-range wireless network interfaces (e.g., Bluetooth®, WiFi) that allow the luminaire to communicate with wireless adapter system 102 disposed proximate (e.g., within 150 meters, within 100 meters, within 50 meters) the luminaires. Additionally, or alternatively, a mobile system 122 may wireless communicate via the wireless adapter system 102. Although only one luminaire is shown for explanatory purposes, it should be appreciated than in practice some applications may have a plurality of luminaires (e.g., 2 luminaires, 100 luminaires, 1000 luminaires).
The control node 112a may communicate instructions and/or data with the CMS 124 via a network. The control node 112a may be a specific “plug-in” embodiment of a primary network control node or primary network node. As an example, the wireless-enabled adapter system 102 may communicate with the CMS 124 via an access point (e.g., cellular tower, WIFI® access point) communicatively coupled to the CMS via one or more suitable data communications networks (e.g., mobile or cellular telecommunications network(s), Internet).
In the implementation shown in
The luminaire 604 may include one or more light sources 612 (e.g., LEDs), AC connections and filtering circuitry 614, a power supply system 616, a control system 618 (e.g., one or more processors, RAM, ROM, buses, interfaces), a physical luminaire interface 620, a programmable light driver 622, and a wireless short-range radio or transceiver 624 which communicates via a wireless communications protocol (e.g., Bluetooth®).
The wireless adapter system (e.g., “plug-in” embodiment of a secondary communications network node or secondary control appliance) 602 may include a control system 626, a wireless short-range radio or transceiver 628, a power supply system 630, a physical luminaire interface 632, a physical node interface 634, an analog dimming receiver 636, and a DALI transceiver 638.
The networked control node 606 may include a control system 640, a wireless network radio or transceiver 642, a power supply system 644, AC connections and filtering circuity 646, a luminaire power measurement module 648, an ON/OFF controller 650, an analog dimming controller 652, an optional DALI transceiver 654, optional sensors and/or a GPS receiver 656, and a physical node interface 658.
The AC connections and filtering circuitry 614 of the luminaire 604 may be electrically coupled with a power distribution system 660. The AC connections and filtering circuitry 614 may receive an AC power signal from the power distribution system 660, and the power supply system 616 may generate a DC power output from the AC power input to system components of the luminaire 604. The programmable light driver 622 may supply the generated DC power output to the light sources 612 to power the light sources. The light sources 612 may include one or more of a variety of conventional light sources, for example, incandescent lamps or fluorescent lamps such as high-intensity discharge (HID) lamps (e.g., mercury vapor lamps, high-pressure sodium lamps, metal halide lamps). The light sources may also include one or more solid-state light sources (e.g., light emitting diodes (LEDs), organic LEDs (OLEDs), polymer LEDs (PLEDs)).
The control systems 618, 626 and/or 640 may each include one or more logic processing units, such as one or more central processing units (CPUs), microprocessors, digital signal processors (DSPs), graphics processors (GPUs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc. Unless described otherwise, the construction and operation of the various blocks shown in
The physical luminaire interface 632 of the wireless adapter system 602 may be a 3-wire interface (line, neutral, switched line) that connects to the physical luminaire interface 620 (e.g., circuit board) of the luminaire 604. The physical node interface 634 may be a 5-pin or 7-pin receptacle interface (e.g., ANSI C146.41 compliant receptacle) that mates with the physical node interface 658 (e.g., ANSI C146.41 compliant plug) of the networked control node 606.
In operation, the networked control node 606 receives power from the luminaire 604 via the adapter system 602, and sends an ON/OFF signal to the luminaire via the physical luminaire interface 632 (e.g., via the switched line of the 3-wire interface). The wireless adapter system 602 also receives or transmits analog dimming signals and/or DALI signals to and from the networked control node 606 via the physical connection between the physical node interface 634 of the adapter system 602 and the physical node interface 658 of the networked control node 606. The signals received by the analog dimming receiver 636 (or transceiver) or the DALI transceiver 638 may be processed (e.g., translated, interpreted, decoded) into a wireless format that may be sent wirelessly to the luminaire 604. More generally, the wireless adapter system 602 may communicate with the networked control node 606 via the physical node interfaces 634 and 658, and may communicate such information or data with the luminaire 604 via the wireless short-range radios 624 and 628. Thus, the luminaire 604 may utilize the added functionality provided by the networked control node 606.
Advantageously, the wireless adapter systems discussed above may be added to a wireless-enabled luminaire replacing a 3-pin receptacle originally controlled by a basic photocontrol for dusk and dawn transitions. Such allows the photocontrol to be replaced by an enhanced 7-pin lamp control node to provide all of the extended control and status capabilities in the luminaire to be managed by a remote CMS with no other changes to the luminaire. This saves the cost and labor of also replacing an incompatible driver of the luminaire that does not support the enhanced control capabilities of the control node.
Additionally, for decorative post top luminaires (see
In both of the above cases, the luminaire maintains the capability to interface to a smart appliance through the wireless interface. This provides a backup or alternative solution to the wireless network interface should the control node or network fail and the luminaire's settings need to be adjusted.
The functional blocks for the wireless adapter 702a may be similar or identical to the wireless adapter system 602 shown in
The integrated control node 802 includes a control system 914, a short-range wireless radio or transceiver 916 to communicate with one or more luminaires via one communications network and protocol, a wireless network radio or transceiver 918 to communicate with the CMS 806 via another communications network and protocol, a power supply system 920, a physical luminaire interface 922, AC connections and filtering circuity 924, a luminaire power measurement module 926, and optional sensors and/or a GPS receiver 928. As discussed above with reference to
The integrated control node 802 provides several advantages. First, the integrated control node 802 may be added to a wireless luminaire containing only a 3-pin receptacle originally controlled by a basic photocontrol for dusk and dawn transitions. This provides all of the extended control and status capabilities in the luminaires to be managed by a remote CMS without the expense of upgrading the luminaire's physical socket, wiring, and electronics required to support the standard implementation. Second, the integrated control node 802 may be added to a 5-pin socket implementation designed for only remote 0-10 V analog control. This provides all of the control and status capabilities of a full 7-pin (DALI) implementation without added cost in the luminaires. In both of the above cases, the luminaires maintain the capability to interface to a CMS and/or smart appliance via the short range wireless interface (e.g., Bluetooth®). The smart appliance provides a backup or alternative solution to the wireless network interface should the node or network fail and the luminaire's settings need to be adjusted.
One or more implementations of the present disclosure provide systems, methods and articles which utilize luminaires that include wireless communication capabilities that allow a plurality of luminaires to be controlled via a secondary communications network which can be implemented via, for example secondary communications network radio that may be part of a secondary communications node (e.g., wireless adaptor), luminaire control circuitry or a luminaire fixture disposed proximate the other luminaires. One or more implementations discussed herein allow for control of a network (e.g. subnetwork) of wireless-enabled luminaires, for example legacy luminaries where the legacy luminaire fixture was not originally wirelessly-enabled but can or has be retrofitted with, for instance: a wirelessly-enabled light source or a wireless-enabled adapter system (e.g., plug in). Such may advantageously allow communications with a plurality of luminaries without requiring those luminaries to communicate directly with a central management system (CMS). For instance, a secondary communications network node or wireless adaptor may intermediate communications between the CMS and a secondary network comprised of legacy luminaires that were installed without wireless communications capability but later retrofitted with wireless communications capability. This may advantageously eliminate wiring and/or reduce a load on a given communications network. This may also, for example, allow control of historically significant posts and historically significant luminaires by the CMS, and collection of data therefrom, without requiring expensive replacement of the historically significant luminaires which are highly prized in certain historically significant neighborhoods. Information collected from the luminaires via the secondary communications network may be aggregated and uploaded by the secondary communications node (e.g., wireless adaptor) to a central management system (CMS) or data repository. Further, in at least some implementations, the secondary communications nodes (e.g., wireless adaptors) may use their wireless communication ability to obtain data from nearby wireless sensors, which sensor information may be collected via the secondary communications network from one or more luminaires in the secondary network of luminaires. The sensor data and/or other data (e.g., luminaire-related data) may be uploaded to the CMS or data repository in a non-real-time period, for example in aggregated or non-aggregated form.
A primary network node 1006a and a secondary communications network node or secondary control appliance 1006b. The primary network node 1006a and a secondary communications network node or secondary control appliance 1006b are communicatively coupled to one another, for example via a wired interface. As illustrated in
Each of the luminaires 1004 contains at least one wireless interface (e.g., radio, transceiver) capable of creating a network group or subnetwork within a sub-area 1000a of the geographic area 1000, with the ability for all terminal luminaires 1004a-1004d within the sub-area 1000a to communicate directly or indirectly with the secondary communications network node or secondary control appliance 1006b in a secondary communications network. In at least some implementations, there may be more than one secondary communications network node or secondary control appliance 1006b. The terminal luminaires 1004a-1004d and the secondary communications network node or secondary control appliance 1006b each include a wireless transceiver of a first type (“first type transceiver”) that allows the secondary communications network node or secondary control appliance and the luminaires 1004a-1004b to wirelessly communicate with each other via the secondary communications network, for example employing a first communications protocol (e.g., 802.15.4, Zigbee, 6Lowpan, Bluetooth®). Additionally, the secondary communications network node or secondary control appliance 1006b includes a wireless transceiver of a second type (“second type transceiver”) that allows for wireless communication with a central management system 1008 via a primary communications network, for example employing a second communications protocol (e.g., cellular protocols, for instance: GSM, IS-95, UMTS, CDMA2000, LTE). The second communications protocol may be different from the first communications protocol.
The secondary communications network node or secondary control appliance 1006b may communicate instructions and/or data with the central management system (CMS) 1008 via the primary communications network 1013. As an example, the secondary communications network node or secondary control appliance 1006b may wirelessly communicate with an access point 1010 (e.g., cellular tower, WIFI® access point) communicatively coupled to the CMS 1008 via one or more suitable data communications networks 1013 (e.g., mobile or cellular telecommunications network(s), Internet). The secondary communications network node or secondary control appliance 1006b may act as a master coordination point for the terminal luminaires 1004a-1004d, mediating communications between the CMS 1008 and the terminal luminaires 1004a-1004d. The CMS 1008 may be similar, or even identical to the CMS 124 (
Referring back to
Although not required, some portion of the implementations will be described in the general context of computer-executable instructions or logic and/or data, such as program application modules, objects, or macros being executed by a computer. Those skilled in the relevant art will appreciate that the illustrated implementations as well as other implementations can be practiced with other computer system or processor-based device configurations, including handheld devices, for instance Web enabled cellular phones or PDAs, multiprocessor systems, microprocessor-based or programmable consumer electronics, personal computers (“PCs”), network PCs, minicomputers, mainframe computers, and the like. The implementations can be practiced in distributed computing environments where tasks or modules are performed by remote processing devices, which are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
The central management system 1008 may take the form of a PC, server, or other computing system executing logic or other machine executable instructions. The central management system 1008 includes one or more processors 1206, a system memory 1208 and a system bus 1210 that couples various system components including the system memory 1208 to the processor 1206. The central management system 1008 will at times be referred to in the singular herein, but this is not intended to limit the implementations to a single system, since in certain implementations, there will be more than one central management system 1008 or other networked computing device involved. Non-limiting examples of commercially available systems include, but are not limited to, an 80×86 or Pentium series microprocessor from Intel Corporation, U.S.A., a PowerPC microprocessor from IBM, a Sparc microprocessor from Sun Microsystems, Inc., a PA-RISC series microprocessor from Hewlett-Packard Company, or a 68xxx series microprocessor from Motorola Corporation.
The central management system 1008 may be implemented as a SCADA system or as one or more components thereof. Generally, a SCADA system is a system operating with coded signals over communication channels to provide control of remote equipment. The supervisory system may be combined with a data acquisition system by adding the use of coded signals over communication channels to acquire information about the status of the remote equipment for display or for recording functions.
The processor 1206 may be any logic processing unit, such as one or more central processing units (CPUs), microprocessors, digital signal processors (DSPs), graphics processors (GPUs), application-specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), etc. Unless described otherwise, the construction and operation of the various blocks shown in
The system bus 1210 can employ any known bus structures or architectures. The system memory 1208 includes read-only memory (“ROM”) 1212 and random access memory (“RAM”) 1214. A basic input/output system (“BIOS”) 1216, which may be incorporated into at least a portion of the ROM 1212, contains basic routines that help transfer information between elements within the central management system 1008, such as during start-up. Some implementations may employ separate buses for data, instructions and power.
The central management system 1008 also may include one or more drives 1218 for reading from and writing to one or more nontransitory computer- or processor-readable media 1220 (e.g., hard disk, magnetic disk, optical disk). The drive 1218 may communicate with the processor 1206 via the system bus 1210. The drive 1218 may include interfaces or controllers (not shown) coupled between such drives and the system bus 1210, as is known by those skilled in the art. The drives 1218 and their associated nontransitory computer- or processor-readable media 1220 provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the central management system 1008. Those skilled in the relevant art will appreciate that other types of computer-readable media may be employed to store data accessible by a computer.
Program modules can be stored in the system memory 1208, such as an operating system 1230, one or more application programs 1232, other programs or modules 1234, and program data 1238.
The application program(s) 1232 may include logic capable of providing the luminaire management functionality described herein. For example, applications programs 1232 may include programs to analyze and organize luminaire information automatically received from the luminaires 1004. The application programs 1232 may also include programs to present raw or analyzed illumination information in a format suitable for presentation to a user.
The system memory 1208 may include communications programs 1240 that permit the central management system 1008 to access and exchange data with other networked systems or components, such as the luminaires 1004, the mobile systems 1006, and/or other computing devices.
While shown in
Personnel can enter commands (e.g., system maintenance, upgrades) and information (e.g., parameters) into the central management system 1008 using one or more communicably coupled input devices 1246 such as a touch screen or keyboard, a pointing device such as a mouse, and/or a push button. Other input devices can include a microphone, joystick, game pad, tablet, scanner, biometric scanning device, etc. These and other input devices may be connected to the processing unit 1206 through an interface such as a universal serial bus (“USB”) interface that couples to the system bus 1210, although other interfaces such as a parallel port, a game port or a wireless interface or a serial port may be used. One or more output devices 1250, such as a monitor or other display device, may be coupled to the system bus 1210 via a video interface, such as a video adapter. In at least some instances, the input devices 1246 and the output devices 1250 may be located proximate the central management system 1008, for example when the system is installed at the system user's premises. In other instances, the input devices 1246 and the output devices 1250 may be located remote from the central management system 1008, for example when the system is installed on the premises of a service provider.
In some implementations, the central management system 1008 uses one or more of the logical connections to communicate with one or more mobile systems, remote computers, servers and/or other devices via one or more communications channels, for example, the one or more networks 1013. These logical connections may facilitate any known method of permitting computers to communicate, such as through one or more LANs and/or WANs. Such networking environments are known in wired and wireless enterprise-wide computer networks, intranets, extranets, and the Internet.
In some implementations, a network port or interface 1256, communicatively linked to the system bus 1210, may be used for establishing and maintaining communications over the primary communications network 1013.
The central management system 1008 may include an AC/DC power supply 1260. The AC/DC power supply 1260 converts AC power from a power source (e.g., AC mains) into DC power, which may be provided to power the various components of the central management system 1008.
In the illumination system 1002, program modules, application programs, or data, or portions thereof, can be stored in one or more computing systems. Those skilled in the relevant art will recognize that the network connections shown in
For convenience, the processor 1206, system memory 1208, network port 1256 and devices 1246, 1250 are illustrated as communicatively coupled to each other via one or more buses 1210, thereby providing connectivity between the above-described components. In alternative implementations, the above-described components may be communicatively coupled in a different manner than illustrated in
It should be appreciated that the luminaires 1004 may include components similar to those components present in the central management system 1008, including the processor 1206, power supply 1260, buses, nontransitory computer- or processor-readable media, wired or wireless communications interfaces, and one or more input and/or output devices.
The secondary communications network node 1024 can include any device, system or combination of systems and devices having at least wireless communications capabilities and the ability to operate between a primary communications network and a secondary communications network. In most instances, the secondary communications network node 1024 includes additional devices, systems, or combinations of systems and devices capable of providing graphical data display capabilities. In at least some implementations, the secondary communications network node 1024 includes one, more or all of the electrical or electronics structures of the control node 606 and the wireless adapter system 602 (
As shown in
In at least some implementations, the luminaires 1004 include a satellite positioning receiver such as GPS receiver, Glonass, etc., and store their position data in nontransitory computer- or processor-readable media or memory. The position data may only need to be acquired relatively infrequently, thus enabling location data to be acquired in poor reception areas or with relatively low cost receiver hardware.
The secondary communications network node 1024 includes a control system 1045b (e.g., one or more processors) and a nontransitory data store 1048b (e.g., memory, RAM, ROM, FLASH, disk based storage) communicatively coupled to the control system 1045b and which stores at least one of processor-executable instructions and/or data. The nontransitory data store 1048b also stores information or data collected from or about the luminaries 1004a-1004d, either in raw form or amalgamated form. The control system 1045b may convert raw form data to amalgamated form. The secondary communications network node 1024 includes an instance of a first type transceiver 1050b which communicates via the first wireless communications protocol (e.g., Bluetooth®, Wi-Fi®) as part of the secondary communications network 1. The first type of transceiver 1050b allow for communication with the luminaires 1004 that form the secondary communications network 1.
The primary network node 1023 includes a control system 1045c (e.g., one or more processors) and a nontransitory data store 1048c (e.g., memory, RAM, ROM, FLASH, disk based storage) communicatively coupled to the control system 1045c and which stores at least one of processor-executable instructions and/or data. The primary network node 1023 includes an instance of a second type transceiver 1052 which communicates via the second wireless communications protocol (e.g., cellular or mobile protocols, for instance GSM, CDMA) as part of the primary communications network 2. The second type transceiver 1052 provides wireless communications capabilities which allow communications with the CMS 1008 for example via a cellular or mobile communications provider network.
During installation, testing or setup of the luminaires 1004, the secondary communications network node 1024 may transmit information (e.g., geographical coordinates, configuration information or instructions, operational information or instructions) to the luminaires 1004a-1004d over a secondary data communications channel (e.g., Bluetooth®, Wi-Fi®). The secondary communications network node 1024 may additionally or alternatively receive information pertaining to one or more luminaires 1004a-1004d, one or more sensors, etc. The secondary communications network node 1024 may amalgamate information collected from across a plurality of luminaires 1004a-1004d. The primary communications network node 1023 may receive information (e.g., geographical coordinates, configuration information or instructions, operational information or instructions) from the central management system 1008 over a primary data communications channel (e.g., cellular, mobile). The primary communications network node 1023 may additionally or alternatively transmit information pertaining to one or more luminaires 1004a-1004d (e.g., amalgamated information) to the central management system 1008 via primary data communications channel (e.g., cellular, mobile). Communications between the primary and secondary network nodes 1023, 1024 may occur via a physical interface or even a hardwired physical interface.
In at least some implementations, each of the luminaires 1004 is programmed with a unique identifier (e.g., identification number, such as a serial number). The unique identifier uniquely identifies the respective luminaire with respect to all other luminaires in an installation, or installed base, asset collection, or inventory of an entity. The unique identifier may be programmed or otherwise stored in the nontransitory data store 1018 during manufacture, during installation, or at any other time. The unique identifier may be programmed using the secondary network nodes 1024, a factory programming fixture, DIP switches, or using any other suitable method.
Once the luminaires 1004 have received their respective identification information and any other configuration information, the luminaires 1004 may send such information to the CMS 1008 via the primary network node 1023 and secondary communications network node 1024, for storage by the CMS 1008. As discussed in further detail below, the CMS 1008 may utilize the received luminaire information to build an asset management table. The CMS 1008 may also include mapping functions that generate an asset management map which may visually present luminaire information to one or more users. The CMS 1008 may also analyze the collected data and generate one or more electronic reports that are valuable for users associated with the illumination system 1002.
The local ICS 1045a of each of the luminaires 1004 may include a photocontrol, or an interface to a photocontrol, that has a photosensitive transducer (photosensor) associated therewith. The ICS 1045a may be operative to control operation of the light sources 1040 based on ambient light levels detected by the photosensor. The ICS 1045a may provide illumination data signals to control the light sources 1040. The ICS 1045a may also include a switch that provides electrical power to the light sources 1040 only when detected light levels are below a desired level. For example, the local ICS 1045a of each of the luminaires 1004 may include a photosensor that controls an electro-mechanical relay coupled between a source of electrical power and a control device (e.g., a magnetic or electronic transformer) within the luminaires. The electro-mechanical relay may be configured to be in an electrically continuous state unless a signal from the photosensor is present to supply power to the luminaires 1004. If the photosensor is illuminated with a sufficient amount of light, the photosensor outputs the signal that causes the electro-mechanical relay to switch to an electrically discontinuous state such that no power is supplied to the luminaires 1004.
In some implementations, the ICS 1045a may include one or more clocks or timers, and/or one or more look-up tables or other data structures that indicate dawn events and dusk events for one or more geographical locations at various times during a year. The time of occurrence of various solar events may additionally or alternatively be calculated using geolocation, time, or date data either generated by or stored within a nontransitory processor-readable medium of the luminaires 1004 or obtained from one or more external devices via one or more wired or wireless communication interfaces either in or communicably coupled to the luminaire. In some implementations, the ICS 1045a is implemented partially or fully by one or more processors.
The power supply 1044 of the luminaires 1004 may be electrically coupled with a power distribution system. The power supply 1044 may receive an AC power signal from the power distribution system, generate a DC power output, and supply the generated DC power output to the light sources 1040 to power the light sources as controlled by light source control commands from the ICS 1045a.
The light sources 1040 may include one or more of a variety of conventional light sources, for example, incandescent lamps or fluorescent lamps such as high-intensity discharge (HID) lamps (e.g., mercury vapor lamps, high-pressure sodium lamps, metal halide lamps). The light sources 140 may also include one or more solid-state light sources (e.g., light emitting diodes (LEDs), organic LEDs (OLEDs), polymer LEDs (PLEDs)).
The secondary network node 1024 may receive luminaire information from each of the luminaires 1004 in the illumination system 1002. For example, in some implementations the secondary network node 1024 may interrogate the luminaires 1004 and receive signals from each of the luminaires that provide luminaire information. The secondary network node 1024 may send such information (e.g., amalgamated information) to the CMS 1008, as discussed above, via the primary network node 1023 and primary communications network. Similarly, the secondary network node 1024 may send information (e.g., control information, operational parameter information) to the luminaires 1004 via the secondary communications network. Such information may be received by the CMS 1008 via one or more primary communications networks (e.g., primary communications network 1013).
The CMS 1008 may store the luminaire information in one or more nontransitory computer- or processor-readable media (e.g., nontransitory computer- or processor-readable media 1220 of
Logged data from each of the networked luminaires 1004 can be retrieved and passed to the CMS 1008 or other data repository via the gateway 1006 via the primary communications network. This information may contain any available information from the luminaires, including operational and maintenance data, performance data such as power usage, and asset management data such as luminaire model, serial number, and location (if available).
Advantageously, the illumination system 1002 shown in
Further, in at least some of the implementations of the present disclosure network security is increased significantly over traditional luminaire network deployments. Since the network of luminaires 1004 may not be connected directly to the Internet, no attacks can be generated on the infrastructure through Web-based cyber-attacks. An attacker would need to physically access the wireless secondary network with the ability to intercept wireless communications to affect the network of luminaires 1004 in the illumination system 1002. Further, network security is increased since the illumination system 1002 may be connected to the Internet only during brief intervals when the secondary network node 1024 is connected to the Internet when communicating with the CMS 1008 over a primary communications network (e.g., cellular or mobile network).
The data distribution and collection by the secondary network node 1024 allows periodic information to be manually initiated by a data collection user and added to a repository without the need for having a complete end-to-end real-time control and monitoring center in place. The data can be refreshed periodically and can be made available on-demand.
The illumination system 1300 provides a data collection network which includes a plurality of luminaires 1004. One or more of the luminaires 1004 may obtain periodic sensor data from one or more sensors 1302a-1302f (collectively, sensors 1302) and may temporarily store the data locally in the luminaire 1004, and may deliver the sensor data over a short-range wireless communications protocol via a secondary communications network to a secondary communications network node 1006b or a set of luminaire control circuitry 1006b, which in turn may deliver the data to the central management system 1008 over a suitable primary communications network (e.g., cellular or mobile network) 1013 via primary communications network node 1006a. As an example, each of the one or more sensors 1302a-1302f may gather sensor data (e.g., continuously, periodically, from time-to-time) and may send the sensor data to one of the luminaires 1004 for temporary storage in a memory of the luminaire. In some implementations, the one or more of the secondary communications network node 1006b may obtain sensor data from the one or more sensors 1302 and temporarily store the data locally in memory, which data may be sent by the one or more secondary network nodes 1006b, 1024 to be collected, amalgamated, and delivered thereby to the central management system 1008 via the primary network node 1006a, 1023, as discussed above.
In operation, the secondary network nodes 1006b, 1024 may network via the secondary communications network with the communication-enabled sensors 1302 that collect information from areas proximate the illumination system 1300 and from time-to-time send data to the primary network nodes 1006a, 1023, which may from time-to-time send the data to the CMS 1008 or other data repository in offline or online mode. Non-limiting examples of sensors may include a motion sensor (e.g., traffic sensor, a pedestrian sensor, a parking space usage sensor), a temperature sensor, a humidity sensor, a carbon monoxide sensor, a noise sensor, a gunshot detection sensor, etc.
Each of the luminaires 1004 contains wireless network communication capability, either single wireless network capability or dual wireless network and short-range network (e.g., Bluetooth®) capability, as discussed above. Each of the sensors 1302 includes a power system 1304, sensor electronics 1306, a control system 1310, and at least one transceiver 1308 (e.g., wireless network and/or short-range communications protocol, such as Bluetooth®). The sensors 1302 may be battery-powered or may receive power from power lines of a luminaire pole to which the sensor is coupled, or via a photovoltaic array. The sensors 1302 can be any sensors that detect events or periodically record any type of measurement.
In at least some implementations, a wireless data collector 1312 (e.g., network attached storage) may be positioned proximate at least one of the luminaires 1004 and may be coupled to the secondary communications network (formed by: luminaires 1004 and the secondary communications network node 1006b, 1024). The data collector 1312 may include a power system 1314, a control system 1316, data storage 1318, and one or more wireless transceivers 1320. In operation, the data collector 1312 wirelessly receives and stores a large dataset from multiple sensors 1302 for a period of time. The data collector 1312 can be positioned anywhere in coverage of the wireless network where it has access to receiving data from any of the sensors 1302 directly or via one or more of the luminaires 1004. The data collector 1312 may be a separate component or may be integrated into a secondary network nodes 1006b, 1024 (e.g., data storage amalgamated across multiple luminaires).
Upon a trigger to capture data, the sensors 1302 may transfer the data to the data collector 1312 or the secondary network node 1006b, 1024 via the secondary wireless network or a tertiary wireless network. The secondary network node 1006b, 1024 may periodically access the sensor data stored by the data collector 1312 and transfer the set of data to the CMS 1008 or other remote repository via the primary network node 1006a, 1023. In at least some implementations, the data collector 1312 may also be enabled for short-range wireless communication (e.g., Bluetooth®), which allows for direct connection between the data collector 1312 and the secondary network node 1006b, 1024.
The illumination system 1300 of
Various of the described components or devices may include a control system or processor and associated nontransitory computer- or processor-readable media or memory, for instance one or more data stores that may take the form of nonvolatile memories such as read only memory (ROM) or FLASH memory and/or one or more volatile memories such as random access memory (RAM).
While the primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024 are generally described as including two transceivers or radios and associated antennas for implementing the primary communication network and the secondary communications network, in at least some implementations, the primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024 may include one or more additional transceivers or radios, for example to provide communications with one or more mobile communications devices (e.g., tablet computers, cellular or mobile phones). The primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024 may further be communicatively coupled via one or more wired interfaces (not shown) that utilize parallel cables, serial cables, or wireless channels capable of high speed communications, for instance, via one or more of FireWire®, Universal Serial Bus® (USB), Thunderbolt®, or Gigabit Ethernet®, for example.
Some or all of the components within the primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024 may be communicably coupled using at least one bus (not shown) or similar structure adapted to transferring, transporting, or conveying data between the devices, systems, or components used within the primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024. The bus can include one or more serial communications links or a parallel communications link such as an 8-bit, 16-bit, 32-bit, or 64-bit data bus. In some implementations, a redundant bus (not shown) may be present to provide failover capability in the event of a failure or disruption of a primary bus.
The control system or processor(s) 1045 (
The transceivers or radios described herein can include any device capable of transmitting and receiving communications via electromagnetic energy. Non-limiting examples of cellular communications transceivers or radios include a CDMA transceiver, a GSM transceiver, a 3G transceiver, a 4G transceiver, an LTE transceiver, and any similar current or future developed computing device transceiver having at least one of a voice telephony capability or a data exchange capability. In at least some instances, the cellular transceivers or radios can include more than one interface. For example, in some instances, the cellular transceivers or radios can include at least one dedicated, full- or half-duplex, voice call interface and at least one dedicated data interface. In other instances, the cellular transceivers or radios can include at least one integrated interface capable of contemporaneously accommodating both full- or half-duplex voice calls and data transfer.
Non-limiting examples of Wi-Fi® short-range transceivers or radios include various chipsets available from Broadcom, including BCM43142, BCM4313, BCM94312MC, BCM4312, and chipsets available from Atmel, Marvell, or Redpine. Non-limiting examples of Bluetooth® short-range transceivers or radios include various chipsets available from Nordic Semiconductor, Texas Instruments, Cambridge Silicon Radio, Broadcom, and EM Microelectronic.
As noted, nontransitory computer- or processor-readable media can, for example, include non-volatile storage memory and in some implementations may include volatile memory as well. At least a portion of the nontransitory computer- or processor-readable media may be used to store one or more processor executable instruction sets for execution by the processor 1045a-1045c. In some implementations, all or a portion of the memory may be disposed within the processor 1045a-1045c, for example in the form of a cache. In some implementations, the memory may be supplemented with one or more slots configured to accept the insertion of one or more removable memory devices such as a secure digital (SD) card, a compact flash (CF) card, a universal serial bus (USB) memory “stick,” or the like.
In at least some implementations, one or more sets of logic or machine executable instructions providing luminaire control applications or “apps” executable by the processor 1045a-1045c may be stored in whole or in part in at least a portion of the memory. In at least some instances, the applications may be downloaded or otherwise acquired by the end user. In some implementations, such applications may start up in response to selection of a corresponding user selectable icon by the user. The applications can facilitate establishing a data link between the primary network nodes 1006a, 1023 and secondary network nodes 1006b, 1024 and the central management system 1008 or the luminaires 1004 via the transceivers or radios and communication networks.
The secondary communications network node 1602 also includes a short-range wireless interface circuit 1620 (e.g., Bluetooth®, WiFi) disposed in the housing 1604. In operation, the secondary communications network node 1602 receives via the wired receptacle interface 1606 ON/OFF, dimming, or other commands or data from the control node 112 and autonomously interprets or translates those signals using one or more processors, for example. The received interpreted signals are translated into wireless signals that are transmitted by the wireless interface circuit 1620 of the secondary communications network node 1602 and transmitted to the wireless-enabled luminaire 1618. Optionally, the secondary communications network node 1602 may receive via the wireless interface circuit 1620 signals encoding data or instructions from the luminaire 1618, and may interpret and transmit the signals to the primary network control node 1612 via the wired receptacle interface 1606. The instructions or commands may be in the form of switch-controlled ON/OFF signals, analog dimming with dim-to-off capability (e.g., 0-10 V), digital control and status commands (e.g., DALI), or any other types of signals.
As noted above, the luminaire 1618 may contain one or more short-range wireless network interfaces (e.g., Bluetooth®, WiFi) that allow the luminaire to communicate with the secondary communications network node 1602 disposed proximate (e.g., within 150 meters, within 100 meters, within 50 meters) the luminaire 1618. Although only one luminaire is shown for explanatory purposes, it should be appreciated than in practice some applications may have a plurality of luminaires (e.g., 2 luminaires, 100 luminaires, 1000 luminaires).
The primary network control node 1612 may communicate instructions and/or data with a central management system (CMS) 1624 via a primary communications network (e.g., an access point for instance cellular tower, WIFI® access point) communicatively coupled to the CMS via one or more suitable data communications networks (e.g., mobile telecommunications network(s), Internet).
The luminaire system 1700 optionally includes a primary network node 1704. The primary network node 1704 comprises a first primary network node radio (not shown in
The luminaire system 1700 includes a secondary control appliance 1712. The secondary control appliance 1712 includes a primary network node interface 1714, a secondary communications network radio (not shown in
The secondary control appliance 1712 can be separate and distinct from the luminaires 1702. The secondary control appliance 1712 can be mounted directly to a structure (e.g., pole, post, arm, head) of an existing luminaire 1702. The secondary control appliance 1712 can be mounted on a luminaire, for instance via a standard interface socket. For instance, secondary control appliance 1712 can be mounted to a modern street light (e.g., street light with wirelessly-enabled luminaire) which is nearby or proximate (e.g., within wireless range) a group of legacy street lights that have been out retrofitted with wirelessly-enabled light sources. The secondary control appliance 1712 can be mounted on a building or other structure that is which is nearby or proximate (e.g., within wireless range) a group of legacy street lights that have been out retrofitted with wirelessly-enabled light sources. The secondary control appliance 1712 can be powered from AC power available from an existing luminaire, either through a hardwired connection or via a pass-through adapter on a standard interface socket.
In at least some implementations, each of the plurality of luminaries comprises a respective tertiary radio and antenna (not shown in
In operation, the secondary control appliance 1712 can aggregate status from all of the luminaires 1702 in a group. The secondary control appliance 1712 can provide the primary network node 1704 with a single operational status for the group of luminaires. The operational status can include an indication that at least one luminaire 1702 is not operating as expected or that all luminaires 1702 in the group are operating as expected. The operational status can additionally or alternatively include an indication of a total power draw of the luminaires 1702 in the group, for example summed from each individual luminaire 1702 on the tertiary communications network 1718. The secondary control appliance 1712 can additionally translate commands and/or data between the primary network node 1704 and the luminaires 1702, providing bi-directional communications between the luminaire management system (CMS) 1706 and the luminaires 1702 of a group of luminaires.
The primary network node 1704 can communicate with the secondary control appliance 1721 via analog methods for dimming, on/off enable, and power status, in addition to digital control and status methods, such as DALI (digitally addressable lighting interface). The secondary control appliance 1721 and subnetwork luminaires 1702 as a group may look like a single luminaire on the primary network 1708 for control and status or allow access to individual luminaires 1702 on the secondary or tertiary wireless network 1716, 1718.
The approach described herein may advantageously significantly reduced the number of primary lighting network nodes required in areas where there are many luminaires in close proximity, while still enabling control and status to be communicated from the luminaire management system (CMS) 1706. The approach described herein may advantageously enhance the ability to cost-effectively add to a lighting network, decorative and historic luminaires to that do not contain the necessary lighting network node interfaces. The approach described herein may advantageously enhance the ability to scale far beyond the power-handling and control limitations of networked contactor solutions currently available.
In at least some implementations, a smart appliance 1720 (e.g., wirelessly-enabled mobile device, smartphone, tablet computer, laptop computer) may wirelessly communicate with the secondary control appliance 1712. Such communications may, for example, be via the secondary communications network 1716 or via a separate channel or network (e.g., Bluetooth) from the secondary communications network 1716.
The smart appliance 1720 can wirelessly communicate with the secondary control appliance 1712 to allow configuring and/or provisioning the of the luminaires 1702 in the group, and to allow locally controlling the luminaires 1702 in the group in parallel with control by the CMS 1706 via the primary network node 1704. This enables overrides or local control in the event of a network failure to the CMS 1706 or failure of the mobile or cellular network 1710. The smart appliance 1720 can also download information from the secondary control appliance 1712, which characterizes or represents the operational status of the luminaires 1702 of the group of luminaires.
The lighting system 1800 comprises a first set of lights 1802a, 1802b, 1802c, 1802d (four illustrated, collectively 1802) that are communicatively coupled as an intermediate network 1804, a second set of lights 1806a, 1806b, 1806c, 1806d (four illustrated, collectively 1804) that are communicatively coupled as a first secondary network 1808, and a third set of lights 1810a, 1801b, 1810c, 1810d (four illustrated, collectively 1810) that are communicatively coupled as a second secondary network 1812. The intermediate network 1804, the first secondary network 1808, and second secondary network 1812 can each be considered subnetworks of an overall network.
In the illustrated topology, the mobile network communications system forms a primary network 1814 which provides communications between a central management system 1816 and the lights 1802 of the intermediate network 1802, the lights 1806 of the first secondary network 1808, and the lights 1810 of second secondary network 1812. The central management system 1816 will typically be located remotely from one, more or all of the intermediate network 1804, the first secondary network 1808, and second secondary network 1812.
The described topology allows the central management system 1816 to collect operational information about the operation of the lights 1802, 1806, 1810 and/or to control operation of the lights 1802, 1806, 1810. As described elsewhere herein, the topology may in some implementations advantageously simplify operation, where each network or subnetwork 1804, 1808, 1812 of lights 1802, 1806, 1810 appears as a single light from the perspective of the central management system 1816. For instance, the central management system 1816 may be provide with an indication of accumulated power consumption for all of the lights 1802, 1806, 1810 on a given subnetwork 1804, 1808, 1812. Also for instance, the central management system 1816 may be provide with an indication of the existence of an error condition for a network or subnetwork 1804, 1808, 1812 if any one light 1802, 1806, 1810 of the network or subnetwork 1804, 1808, 1812 is experiencing an error. Also for instance, the central management system 1816 may be provide control instructions which would be implemented for all lights 1802, 1806, 1810 on a given network or subnetwork 1804, 1808, 1812. Thus, even if a network or subnetwork 1804, 1808, 1812 includes 1,000 separate lights 1802, 1806, 1810, the network or subnetwork 1804, 1808, 1812 appears as a single light to the central management system 1816 with respect to the collection of data or information or the sending of operational commands. The central management system 1816 may, or may not, form part of the lighting system 1800, and any claimed lighting system should not be interpreted as requiring a central management system 1816 unless explicitly recited in those claims.
The primary network 1814 may take various forms, for example one or more communications networks provided by a mobile communications service provider (e.g., Verizon, T-Mobile, AT&T). The primary network 1814 may include various types of infrastructure, for example one or more base stations with associated antenna 1818 to provide wireless communications via one or more defined wireless communications protocols (e.g., CDMA, GSM, G4, G5). The primary network 1814 is not typically considered a part of the lighting system 1800.
The intermediate network 1804 may include a primary network/intermediate network gateway 1820 which provides communications between the primary network 1814 and the intermediate network 1804, for example to provide communications with the remotely located central management system (CMS) 1816. The primary network/intermediate network gateway 1820 acts as a “gate” between two different networks, which networks may employ respective communications protocols, which communications protocols may be different or incompatible with one another. Thus, the primary network 1814 may employ a first communications protocol (e.g., GSM) while the intermediate network 1804 may employ an intermediate network protocol (e.g., WI-FI). Examples of devices that operate as gateways have been described above.
As noted, the intermediate network 1804 may include a plurality of lights 1802, for example lights mounted on poles. The lights 1802 may take a variety of forms, for example as the wireless-enabled luminaires or luminaries with wireless-enabled adapters such as the luminaires described above, or alternatively wireless-enable light such as the wireless-enabled lights described above. The lights 1802 may have an associated lighting network control node 1822a, 1822b, 1822c, 1822d (four shown, collectively 1822) coupled thereto, for instance physically and communicatively coupled to the respective luminaire via a standard 3, 5, or 7 pin interface (e.g., female receptacle and complimentary male pins). The lighting network control node 1822 provide communications with the primary network/intermediate network gateway 1820 via the intermediate network 1804, employing an intermediate network protocol. For example, the lighting network control node 1822 can relay power switching and dimming commands and/or can collect and relay operational conditions, for example aggregate power measurements and error conditions for any associated lights 1802, including multiple lights 1802 on a same pole. In at least some implementations, one or more lighting network control nodes 1822 may be physically and communicatively coupled with an associated network appliance to implement control and data collection activities. The lighting network control node 1822 and the standard 3, 5, or 7 pin interfaces may take any of the forms described above.
The first secondary network 1808 may include a first secondary network appliance 1824 and an intermediate network/first secondary network control node 1826. The intermediate network/first secondary network control node 1826 provides communications between the intermediate network 1804 and the first secondary network 1808. The intermediate network/first secondary network control node 1826 may act as a “gate” between two different networks, which networks may employ respective communications protocols, which communications protocols may be the same as one another (e.g., WI-FI) or different from one another. The intermediate network/first secondary network control node 1826 and the first secondary network appliance 1824 are communicatively coupled to one another, for example, physically and communicatively coupled to one another via a standard 3, 5, or 7 pin interface physical interface. The first secondary network appliance 1824 provides wireless communications with the lights 1806 of the first secondary network 1808, to receive and collect operational information therefrom and/or to send commands (e.g., power and/or dimming control commands) thereto for execution thereby in order to control lighting and other operations.
As noted, the first secondary network 1808 may include a plurality of lights 1806, for example lights mounted on poles. The lights 1806 may take a variety of forms, for example luminaires such as the wireless-enabled luminaires or luminaries with wireless-enabled adapters (as illustrated) described above, or alternatively as wireless-enabled lights such as the wireless-enabled lights described above. As noted, each luminaire may have a wireless controller control node 1828a, 1828b, 1828c, 1828d (four shown, collectively 1828) coupled thereto, for instance via a standard 3, 5, or 7 pin interface. The wireless controller control nodes 1828 provide communications with the first secondary network appliance 1824 via the first secondary network 1808, employing a first secondary network protocol. The wireless controller control nodes 1828 and the standard 3, 5, or 7 pin interfaces may take any of the forms described above.
The second secondary network 1812 may include a second secondary network appliance 1830 and an intermediate network/second secondary network control node 1832. The intermediate network/second secondary network control node 1832 provides communications between the intermediate network 1804 and the second secondary network 1812. The intermediate network/second secondary network control node 1832 may act as a “gate” between two different networks, which networks may employ respective communications protocols, which communications protocols may be the same as one another (e.g., WI-FI) or different from one another. The intermediate network/second secondary network control node 1832 and the second secondary network appliance 1830 are communicatively coupled to one another, for example, physically and communicatively coupled to one another via a standard 3, 5, or 7 pin interface physical interface. The second secondary network appliance 1830 provides wireless communications with the lights 1810 of the second secondary network 1812, to receive and collect operational information therefrom and/or to send commands (e.g., power and/or dimming control commands) thereto for execution thereby in order to control lighting.
As noted, the second secondary network 1812 may include a plurality of lights 1810, for example lights mounted on poles. The lights 1810 may take a variety of forms, for example wireless-enabled lights (as illustrated) such as the wireless-enabled lights described above, or alternatively luminaires such as the wireless-enabled luminaires or luminaries with wireless-enabled adapters described above. Each light 1810 may implement or have an integral control node that provides communications with the second secondary network appliance 1830 via the second secondary network 1812, employing a second secondary network protocol.
While illustrated in
The wirelessly-enabled lamp 1900 includes a housing 1902, comprising a base portion 1902a, a distal portion 1902b, and an intermediate portion 1902c positioned between the base portion 1902a and the distal portion 1902b. The distal portion 1902b is distal with respect to the base portion 1902a.
The wirelessly-enabled lamp 1900 may include a first interface 1904 to physically and electrically couple the wirelessly-enabled lamp 1900 to a power source, for example an Edison type interface including a threaded cap 1904a and electrical contact 1904b with an electrical insulator positioned therebetween as is conventional for Edison type lamps. One of ordinary skill in the art will note that the first interface 1904 is not limited to Edison type interfaces, and that any of a variety of conventional types of interfaces may be employed including a hardwired connection.
The wirelessly-enabled lamp 1900 may include a second interface, for example a twist-lock receptacle 1906, positioned to be assessable from an exterior of the housing 1902, for instance at or proximate the distal portion 1902b thereof. The twist-lock receptacle 1906 may have one or more slots or other apertures 1906a (only once called out) sized, dimensioned, positioned and/or oriented to receive pins, prongs or blades of one or more types of attachments, for example of photocontrols with 3-pin interface (e.g., ANSI C136.10), the 5-pin or 7-pin (e.g., ANSI C136.41), or other number of pins (e.g., 2-pin, 4-pin) interface. One of ordinary skill in the art will note that the second interface 1906 is not limited to that illustrated in
The base portion 1902a may have an interior that houses circuitry, for example power filtering and power conversion circuitry. As such, the base portion 1902a may include one or more vents and/or fins to enhance heat exchange (e.g., convective or active heat transfer) to enhance cooling of the circuitry.
The distal portion 1902b may have an interior that houses circuitry, for example control circuitry and/or transceivers or radios and associated antenna. As such, the base portion 1902a may include one or more vents and/or fins to enhance heat exchange (e.g., convective or active heat transfer) to enhance cooling of the circuitry.
The intermediate portion 19020c may have an interior that houses one or more light sources, for example a plurality of light emitting diodes (LEDs), for instances LEDs mounted to one or more printed circuit boards, arrayed about a longitudinal axis. The intermediate portion 19020c may be transparent or translucent, for instance forming a lens spaced radially outward from the LEDs.
The wirelessly-enabled lamp 1900 may be similar to the solid-state lighting devices illustrated and described in International Application Number PCT/US2014/055909, published as WO 2015/039120, with the addition of radios and antennas, and/or other components or structures described in this detailed description or incorporated herein by reference.
The sensor(s) 2000 can include a photosensor and associated circuitry acting as a photocontrol that is operable to detect dusk and dawn conditions based on light sensed by the photosensor. Other sensors may include motion detectors, noise detectors or microphones, or remote actuation detectors that provide signals to the wirelessly-enabled lamp 1900 to change its lighting state (e.g., ON/OFF states, dimming states) and/or provide a notification, alert or other indication of a sensed condition (e.g., via a radio, flashing pattern, siren or speaker). The sensor(s) 2000 may include any of a variety of interfaces, for example a pin interface, and thus is physically and communicatively coupleable to the wirelessly-enabled lamp 1900 via the twist-lock receptacle 1906 (
Alternatively or additionally, the wirelessly-enabled lamp 1900 may include one or more integral sensors, integral to the wirelessly-enabled lamp 1900, for example housed by the housing 1902 or otherwise carried thereby. Again, the integral sensor(s) may take a variety of forms, for example photosensors, motion detectors, noise detectors or microphones, or remote actuation detectors that provide signals to circuitry of the wirelessly-enabled lamp 1900 which may cause the wirelessly-enabled lamp 1900 to change its lighting state (e.g., ON/OFF states, dimming states) and/or provide a notification, alert or other indication of a sensed condition (e.g., via a radio, flashing pattern, siren or speaker). For example, the photosensor and associated circuitry act as a photocontrol that is operable to detect dusk and dawn conditions based on light sensed by the photosensor, providing signals to control the lighting state (e.g., ON/OFF states, dimming states) of the wirelessly-enabled lamp 1900. The wirelessly-enabled lamp 1900 may, for example, employ a photosensor that is sensitive or response to specific wavelengths (e.g., infrared wavelengths) rather than a broadband (e.g., white light) sensor. Additionally or alternatively, an optical filter may be employed to limit wavelengths of light that reach the photosensor. Such may advantageously reduce the effect of light emitted by the wirelessly-enabled lamp 1900 on the photosensor, allowing the photosensor to be more responsive to solar insolation. Alternatively or additionally, the wirelessly-enabled lamp 1900 may employ a “real-time” clock to determine dusk and dawn events or other solar events, which may be employed in lieu of photosensor based dusk/dawn sensing (e.g. photocontrols), or may be employed in conjunction therewith which allows confirmation that the photosensor and/or photocontrols are operating correctly.
The operation and features of many of these components are discussed above, and thus in the interest of conciseness only some of the details are described below.
The wirelessly-enabled gateway lamp 2100 is denominated as a “gateway” since such may operate as an intermediary for communications, for instance between two or more different communications networks or communications channels. The wirelessly-enabled terminal lamps 2104a-2104n and the wirelessly-enabled terminal luminaires 2106a-2106n are denominated as “terminal” because they are nodes in the communications networks or communications channels with which the wirelessly-enabled gateway lamp 2100 intermediates communications.
The wirelessly-enabled gateway lamp 2100 includes a housing 2112, which may be similar or even identical to that described with respect to the wirelessly-enabled lamp 1900 (
The wirelessly-enabled gateway lamp 2100 includes one or more light sources, for example solid-state light sources, for instance LEDs 2114a-2114n (two called out). The LEDs 2114a-2114n may be arrayed about a longitudinal axis, for example coupled or mounted to one or more printed circuit boards 2116, each LED 2114a-2114n mounted with a principal axis of emission generally facing radially outward. As previously noted, the LEDs 2114a-2114n may be positioned in an intermediate portion 1902c (
The wirelessly-enabled gateway lamp 2100 includes AC connections and filtering circuitry 2118, which may include or be electrically coupled to the first interface 1904 (e.g., threaded cap 1904a and electrical contact 1904b with an electrical insulator positioned therebetween). The AC connections and filtering circuitry 2118 may include filtering circuitry, voltage converters, and/or fuses or breakers operable to receive and condition AC power received from a power source (e.g., received via an electrical socket of a luminaire). The wirelessly-enabled gateway lamp 2100 includes lamp power system circuitry 2120, which may be electrically coupled to the AC connections and filtering circuitry 2118. The lamp power system circuitry 2120 may include one or more rectifiers operable to rectify the AC power to DC power, one or more voltage converters (e.g., step down or buck converters), and/or filtering or other conditioning circuitry. The lamp power system circuitry 2120 may supply electrical power (e.g., DC power) at appropriate voltages to the various other components of the wirelessly-enabled gateway lamp 2100. The AC connections and filtering circuitry 2118 and/or lamp power system circuitry 2120 may, for example, employ circuitry similar or even identical to that illustrated and/or described in U.S. patent application publication 2020/0029404; U.S. patent application publication 2018/0083438; U.S. patent application publication 2018/0083539; and/or U.S. patent application publication 2020/0045794.
The wirelessly-enabled gateway lamp 2100 includes a driver, for example a programmable light driver 2122, communicatively coupled to drive the light sources (e.g., LEDs 2114a-2114n). The programmable light driver 2122 may, for example, employ circuitry similar or even identical to that illustrated and/or described in U.S. patent application publication U.S. Pat. Nos. 9,924,582, 9,210,751; U.S. patent application publication 2013/0163243; U.S. 2013/0313982; U.S. patent application publication 2014/039180; U.S. patent application publication 2014/0159585; and/or U.S. patent application publication 2013/0649613.
The wirelessly-enabled gateway lamp 2100 includes a control system 2124 operable to control operation of the wirelessly-enabled gateway lamp 2100. The control system 2124 may take a variety of forms with one or more components. The control system 2124 will typically include one or more processors 2126 (e.g., microprocessors, microcontrollers, application specific integrated circuits, field programmable gate array, other logic circuitry). The control system 2124 will typically include one or more nontransitory storage media, for example nonvolatile memory and/or volatile memory, for instance read only memory (ROM) 2128 and random access memory (RAM) 2130. One of ordinary skill in the art will recognize that the control system may employ other forms of nontransitory storage media (e.g., FLASH, solid state drives).
The control system 2124 may, for example, provide control signals to the programmable light driver 2122 to operate one or more of the LEDs 2214a-2114n, for example placing one or more of the LEDs 2214a-2114n in an ON state or an OFF state, or adjusting an intensity of output of one or more of the LEDs 2214a-2114n. The control system 2124 may control operation of the LEDs 2214a-2114n based on one or more input values, for example based on input from the photocontrols 2000 or based on input received from the central management system 2102, sensors 2108a-2108n, and/or smart appliance 2110. Additionally or alternatively, control system 2124 may control operation of the LEDs 2214a-2114n based on other inputs, for example based on a clock or calendar, which may be implemented by the control system 2124, or which may be provided via an external source.
The wirelessly-enabled gateway lamp 2100 may optionally include a twist-lock receptacle 1906, similar or even identical to that described in reference to
Alternatively or additionally, the wirelessly-enabled lamp 1900 may include one or more integral sensors and/or associated circuitry, integral to the wirelessly-enabled lamp 1900, for example housed by the housing 1902 or otherwise carried thereby. The integral sensor(s) may take a variety of forms, for example photosensors 2131a, motion detectors 2131b, noise detectors or microphones 2131c, remote actuation detectors 2131d, temperature sensors (e.g., thermocouples), humidity sensors, carbon monoxide sensors, gunshot sensors or detectors, that provide signals to circuitry of the wirelessly-enabled lamp 1900 which may cause the wirelessly-enabled lamp 1900 to change its lighting state (e.g., ON/OFF states, dimming states) and/or provide a notification, alert or other indication of a sensed condition (e.g., via a radio, flashing pattern, siren or speaker 2131e). For example, the photosensor 2131a and associated circuitry 2133 act as a photocontrol that is operable to detect dusk and dawn conditions based on light sensed by the photosensor, providing signals to control the lighting state (e.g., ON/OFF states, dimming states) of the wirelessly-enabled lamp 1900. While the dusk/dawn sensing is illustrated as separate circuitry 2133, in at least some implementations such can be implemented via the processor(s) 2126. Integral sensors and/or circuitry (e.g., dusk/dawn sensing, motion sensing, gunshot detection) may advantageously reduce the physical size and cost of the solution, as well as simplify setup and maintenance, reduce malfunctions (e.g., from corroded contacts of externally exposed interfaces, electrical arcing of contacts), and streamline overall operation and software integration of the various provided functionalities.
The wirelessly-enabled gateway lamp 2100 includes a number of radios or transceivers operable to provide wireless communications via one or more communications channels or networks. The wirelessly-enabled gateway lamp 2100 may, for example, include a first radio 2132a and associated antenna 2134a, a second radio 2132b and associated antenna 2134b, and optionally a third radio 2132c and associated antenna 2134c.
The second radio 2132b and antenna 2134b may take the form of a cellular network radio and antenna operable to provide cellular communications via a cellular communications compliant network and/or protocol (e.g., GSM). The second radio 2132b and antenna 2134b may, for example, provide communications with the CMS 2102 via the cellular communications network, for example via a cellular antenna on a tower 2136 and associated cellular base station 2138 and/or via any intermediate communications channels or intermediate communications networks. Such may allow the wirelessly-enabled gateway lamp 2100 to receive instructions and data (e.g., commissioning data) from the CMS 2102 and/or provide operational conditions, status, or state information to the CMS 2102.
The first radio 2132a and antenna 2134a may take the form of a short-range wireless radio or transceiver to provide communications with one or more terminal lamps 2104a-2104n or luminaires 2106a-2106n via one or more communications networks and/or protocols (e.g., a WI-FI® communications compliant protocol). Such may allow the wirelessly-enabled gateway lamp 2100 to receive conditions, status, or state information from the terminal lamps 2104a-2104n or luminaires 2106a-2106n and/or to provide instructions and data (e.g., commissioning data) to the terminal lamps 2104a-2104n or luminaires 2106a-2106n. In at least some implementations, the wirelessly-enabled gateway lamp 2100 receives conditions, status, or state information from the terminal lamps 2104a-2104n or luminaires 2106a-2106n may act as an intermediary between the CMS 2102, for example, collecting, accumulating or aggregating conditions, status, or state information from the terminal lamps 2104a-2104n or luminaires 2106a-2106n, and transferring the collected, accumulated or aggregated data to the CMS 2102 from time-to-time. In at least some implementations, the wirelessly-enabled gateway lamp 2100 receives instructions, commands or data from the CMS 2102, and/or provides instructions or commands or data to the terminal lamps 2104a-2104n or luminaires 2106a-2106n for execution by the same. In at least some implementations, the wirelessly-enabled gateway lamp 2100 may control operation of one or more of the terminal lamps 2104a-2104n or luminaires 2106a-2106n via the first radio 2132a and antenna 2134a.
The first radio 2132a and antenna 2134a may additionally or alternatively provide communications with one or more sensors 2108a-2108n via one or more communications networks 2140 and/or protocols (e.g., a WI-FI® communications compliant protocol). Such may allow the wirelessly-enabled gateway lamp 2100 to receive conditions, status, or state information from the sensors 2108a-2108n and/or to provide instructions and data (e.g., commissioning data) to the sensors 2108a-2108n. Such may additionally or alternatively allow the wirelessly-enabled gateway lamp 2100 to receive conditions, status, or state information from the sensors 2108a-2108n and/or to provide instructions, commands, and/or data to the terminal lamps 2104a-2104n or luminaires 2106a-2106n, for example based on an analysis of the conditions, status, or state information. For instance, the wirelessly-enabled gateway lamp 2100 may analyze received sensed information such as a level of light, motion sensing condition and/or detection of sound and/or flash of light (e.g., gunshot detection), and transmit instructions or commands for the terminal lamps 2104a-2104n or luminaires 2106a-2106n to all turn ON to a brightest illumination level on detection of an abnormal or alert condition or state, and to provide a notification or alert of such, for example to authorities. In at least some implementations, the wirelessly-enabled gateway lamp 2100 to receive conditions, status, or state information from the sensors 2108a-2108n may act as an intermediary between the CMS 2102 and the sensors, for instance collecting, accumulating or aggregating sensed conditions, status, or state information from the sensors 2108a-2108n, for example, providing the collected, accumulated or aggregated sensed conditions, status, or state information to the CMS 2102 from time-to-time.
The third radio 2132c and antenna 2134c may take the form of a short-range wireless radio and antenna to provide communications with one or more smart appliances (e.g., mobile devices), via one or more communications channels, networks and/or protocols (e.g., a BLUETOOTH® communications compliant protocol). Such may allow the wirelessly-enabled gateway lamp 2100 to receive instructions and data (e.g., commissioning data) from the smart appliance 2110 and/or provide operational conditions, status, or state information to the smart appliance 2110. Such may allow the wirelessly-enabled gateway lamp 2100 to receive instructions and data (e.g., commissioning data) from the smart appliance 2110 and/or provide operational conditions, status, or state information to smart appliance 2110. Such may additionally or alternatively allow the wirelessly-enabled gateway lamp 2100 to receive instructions and data smart appliance 2110 to be relayed to the terminal lamps 2104a-2104n or luminaires 2106a-2106n. In some implementations, the smart appliance 2110 may act as an intermediary between the wirelessly-enabled gateway lamp 2100 and the CMS 2102.
In some implementations, the first radio 2132b and antenna 2134b may employ a first communications network and/or protocol, the second radio 2132a and antenna 2134a may employ a second communications network and/or protocol, and the third radio 2132c and antenna 2134c may employ a third communications channel, network and/or protocol, where the third communications channel, network and/or protocol is different from the first and the second communications networks and/or protocols, and/or the second communications channel, network and/or protocol is different from first communications network and/or protocol.
The various structures and/or components and operations illustrated and described with respect to
One or more implementations of the present disclosure provide systems, methods and articles which utilize luminaires that include wireless communication capabilities that allow a plurality of luminaires to be controlled via a secondary communications network which can be implemented via, for example secondary communications network radio that may be part of a secondary communications node (e.g., wireless adaptor), luminaire control circuitry or a luminaire fixture disposed proximate the other luminaires. One or more implementations discussed herein allow for control of a network (e.g. subnetwork) of wireless-enabled luminaires, for example legacy luminaries where the legacy luminaire fixture was not originally wirelessly-enabled but can or has be retrofitted with, for instance: a wirelessly-enabled lamp 2100 or a wireless-enabled adapter system (e.g., plug in). Such may advantageously allow communications with a plurality of luminaries without requiring those luminaries to communicate directly with a central management system (CMS). For instance, a secondary communications network node or wireless adaptor may intermediate communications between the CMS and a secondary network comprised of legacy luminaires that were installed without wireless communications capability but later retrofitted with wireless communications capability. This may advantageously eliminate wiring and/or reduce a load on a given communications network. This may also, for example, allow control of historically significant posts and historically significant luminaires by the CMS, and collection of data therefrom, without requiring expensive replacement of the historically significant luminaires which are highly prized in certain historically significant neighborhoods. Information collected from the luminaires via the secondary communications network may be aggregated and uploaded by the secondary communications node (e.g., wireless adaptor) to a central management system (CMS) or data repository. Further, in at least some implementations, the secondary communications nodes (e.g., wireless adaptors) may use their wireless communication ability to obtain data from nearby wireless sensors, which sensor information may be collected via the secondary communications network from one or more luminaires in the secondary network of luminaires. The sensor data and/or other data (e.g., luminaire-related data) may be uploaded to the CMS or data repository in a non-real-time period, for example in aggregated or non-aggregated form.
The foregoing detailed description has set forth various implementations of the devices and/or processes via the use of block diagrams, schematics, and examples. Insofar as such block diagrams, schematics, and examples contain one or more functions and/or operations, it will be understood by those skilled in the art that each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In one implementation, the present subject matter may be implemented via Application Specific Integrated Circuits (ASICs). However, those skilled in the art will recognize that the implementations disclosed herein, in whole or in part, can be equivalently implemented in standard integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more controllers (e.g., microcontrollers) as one or more programs running on one or more processors (e.g., microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of ordinary skill in the art in light of this disclosure.
Those of skill in the art will recognize that many of the methods or algorithms set out herein may employ additional acts, may omit some acts, and/or may execute acts in a different order than specified.
In addition, those skilled in the art will appreciate that the mechanisms taught herein are capable of being distributed as a program product in a variety of forms, and that an illustrative implementation applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of signal bearing media include, but are not limited to, the following: recordable type media such as floppy disks, hard disk drives, CD ROMs, digital tape, and computer memory.
The various implementations described above can be combined to provide further implementations. To the extent that they are not inconsistent with the specific teachings and definitions herein, all of the U.S. patents, U.S. patent application publications, U.S. patent applications, foreign patents, foreign patent applications and non-patent publications referred to in this specification and/or listed in the Application Data Sheet, including but not limited to U.S. Provisional Patent Application No. 61/052,924, filed May 13, 2008; U.S. Pat. No. 8,926,138, issued Jan. 6, 2015; PCT Publication No. WO2009/140141, published Nov. 19, 2009; U.S. Provisional Patent Application No. 61/051,619, filed May 8, 2008; U.S. Pat. No. 8,118,456, issued Feb. 21, 2012; PCT Publication No. WO2009/137696, published Nov. 12, 2009; U.S. Provisional Patent Application No. 61/088,651, filed Aug. 13, 2008; U.S. Pat. No. 8,334,640, issued Dec. 18, 2012; U.S. Provisional Patent Application No. 61/115,438, filed Nov. 17, 2008; U.S. Provisional Patent Application No. 61/154,619, filed Feb. 23, 2009; U.S. Patent Publication No. 2010/0123403, published May 20, 2010; U.S. Patent Publication No. 2016/0021713, published Jan. 21, 2016; PCT Publication No. WO2010/057115, published May 20, 2010; U.S. Provisional Patent Application No. 61/174,913, filed May 1, 2009; U.S. Pat. No. 8,926,139, issued Jan. 6, 2015; PCT Publication No. WO2010/127138, published Nov. 4, 2010; U.S. Provisional Patent Application No. 61/180,017, filed May 20, 2009; U.S. Pat. No. 8,872,964, issued Oct. 28, 2014; U.S. Patent Publication No. 2015/0015716, published Jan. 15, 2015; PCT Publication No. WO2010/135575, published Nov. 25, 2010; U.S. Provisional Patent Application No. 61/229,435, filed Jul. 29, 2009; U.S. Patent Publication No. 2011/0026264, published Feb. 3, 2011; U.S. Provisional Patent Application No. 61/295,519, filed Jan. 15, 2010; U.S. Provisional Patent Application No. 61/406,490, filed Oct. 25, 2010; U.S. Pat. No. 8,378,563, issued Feb. 19, 2013; PCT Publication No. WO2011/088363, published Jul. 21, 2011; U.S. Provisional Patent Application No. 61/333,983, filed May 12, 2010; U.S. Pat. No. 8,541,950, issued Sep. 24, 2013; PCT Publication No. WO2010/135577, published Nov. 25, 2010; U.S. Provisional Patent Application No. 61/346,263, filed May 19, 2010; U.S. Pat. No. 8,508,137, issued Aug. 13, 2013; U.S. Pat. No. 8,810,138, issued Aug. 19, 2014; U.S. Pat. No. 8,987,992, issued Mar. 24, 2015; PCT Publication No. WO2010/135582, published Nov. 25, 2010; U.S. Provisional Patent Application No. 61/357,421, filed Jun. 22, 2010; U.S. Pat. No. 9,241,401, granted Jan. 19, 2016; PCT Publication No. WO2011/163334, published Dec. 29, 2011; U.S. Pat. No. 8,901,825, issued Dec. 2, 2014; U.S. Patent Publication No. 2015/0084520, published Mar. 26, 2015; PCT Publication No. WO2012/142115, published Oct. 18, 2012; U.S. Pat. No. 8,610,358, issued Dec. 17, 2013; U.S. Provisional Patent Application No. 61/527,029, filed Aug. 24, 2011; U.S. Pat. No. 8,629,621, issued Jan. 14, 2014; PCT Publication No. WO2013/028834, published Feb. 28, 2013; U.S. Provisional Patent Application No. 61/534,722, filed Sep. 14, 2011; U.S. Pat. No. 9,312,451, issued Apr. 12, 2016; PCT Publication No. WO2013/040333, published Mar. 21, 2013; U.S. Provisional Patent Application No. 61/567,308, filed Dec. 6, 2011; U.S. Pat. No. 9,360,198, issued Jun. 7, 2016; U.S. Provisional Patent Application No. 61/561,616, filed Nov. 18, 2011; U.S. Patent Publication No. 2013/0141010, published Jun. 6, 2013; PCT Publication No. WO2013/074900, published May 23, 2013; U.S. Provisional Patent Application No. 61/641,781, filed May 2, 2012; U.S. Patent Publication No. 2013/0293112, published Nov. 7, 2013; U.S. Patent Publication No. 2013/0229518, published Sep. 5, 2013; U.S. Provisional Patent Application No. 61/640,963, filed May 1, 2012; U.S. Patent Publication No. 2013/0313982, published Nov. 28, 2013; U.S. Patent Publication No. 2014/0028198, published Jan. 30, 2014; U.S. Patent Publication No. 2016/0037605, published Feb. 4, 2016; PCT Publication No. WO2014/018773, published Jan. 30, 2014; U.S. Provisional Patent Application No. 61/723,675, filed Nov. 7, 2012; U.S. Pat. No. 9,301,365, issued Mar. 29, 2016; U.S. Provisional Patent Application No. 61/692,619, filed Aug. 23, 2012; U.S. Patent Publication No. 2014/0055990, published Feb. 27, 2014; U.S. Provisional Patent Application No. 61/694,159, filed Aug. 28, 2012; U.S. Pat. No. 8,878,440, issued Nov. 4, 2014; U.S. Patent Publication No. 2014/0062341, published Mar. 6, 2014; U.S. Patent Publication No. 2015/0077019, published Mar. 19, 2015; PCT Publication No. WO2014/039683, published Mar. 13, 2014; U.S. Provisional Patent Application No. 61/728,150, filed Nov. 19, 2012; U.S. Patent Publication No. 2014/0139116, published May 22, 2014; U.S. Pat. No. 9,433,062, issued Aug. 30, 2016; PCT Publication No. WO2014/078854, published May 22, 2014; U.S. Provisional Patent Application No. 61/764,395, filed Feb. 13, 2013; U.S. Pat. No. 9,288,873, issued Mar. 15, 2016; U.S. Provisional Patent Application No. 61/849,841, filed Jul. 24, 2013; U.S. Patent Publication No. 2015/0028693, published Jan. 29, 2015; PCT Publication No. WO2015/013437, published Jan. 29, 2015; U.S. Provisional Patent Application No. 61/878,425, filed Sep. 16, 2013; U.S. Patent Publication No. 2015/0078005, published Mar. 19, 2015; PCT Publication No. WO2015/039120, published Mar. 19, 2015; U.S. Provisional Patent Application No. 61/933,733, filed Jan. 30, 2014; U.S. Pat. No. 9,185,777, issued Nov. 10, 2015; PCT Publication No. WO2015/116812, published Aug. 6, 2015; U.S. Provisional Patent Application No. 61/905,699, filed Nov. 18, 2013; U.S. Pat. No. 9,414,449, issued Aug. 9, 2016; U.S. Provisional Patent Application No. 62/068,517, filed Oct. 24, 2014; U.S. Provisional Patent Application No. 62/183,505, filed Jun. 23, 2015; U.S. Pat. No. 9,445,485, issued Sep. 13, 2016; PCT Publication No. WO2016/064542, published Apr. 28, 2016; U.S. Provisional Patent Application No. 62/082,463, filed Nov. 20, 2014; U.S. Publication No. 2016/0150369, published May 26, 2016; PCT Publication No. WO2016/081071, published May 26, 2016; U.S. Provisional Patent Application No. 62/057,419, filed Sep. 30, 2014; U.S. Publication No. 2016/0095186, published Mar. 31, 2016; PCT Publication No. WO2016/054085, published Apr. 7, 2016; U.S. Provisional Patent Application No. 62/114,826, filed Feb. 11, 2015; U.S. Non-provisional patent application Ser. No. 14/939,856, filed Nov. 12, 2015; U.S. Provisional Patent Application No. 62/137,666, filed Mar. 24, 2015; U.S. Non-provisional patent application Ser. No. 14/994,569, filed Jan. 13, 2016; U.S. Non-provisional patent application Ser. No. 14/844,944, filed Sep. 3, 2015; U.S. Provisional Patent Application No. 62/208,403, filed Aug. 21, 2015; U.S. Non-provisional patent application Ser. No. 15/238,129, filed Aug. 16, 2016; U.S. Provisional Patent Application No. 62/264,694, filed Dec. 8, 2015; U.S. Non-provisional patent application Ser. No. 15/369,559, filed Dec. 5, 2016; U.S. Provisional Patent Application No. 62/397,709, filed Sep. 21, 2016; U.S. Provisional Patent Application No. 62/397,713, filed Sep. 21, 2016; U.S. Provisional Patent Application No. 62/327,939, filed Apr. 26, 2016; U.S. Provisional Patent Application No. 62/379,037, filed Aug. 24, 2016; U.S. Provisional Patent Application No. 62/458,970, filed Feb. 14, 2017; U.S. patent application Ser. No. 15/895,439, filed Feb. 13, 2018 (now U.S. Pat. No. 10,098,212); U.S. Provisional Patent Application No. 62/480,833, filed Apr. 3, 2017; U.S. patent application Ser. No. 16/284,869, filed Apr. 2, 2018; U.S. patent application Ser. No. 15/943,183, filed Apr. 2, 2018; U.S. patent application Ser. No. 16/440,612, filed Jun. 13, 2019; and U.S. patent application Ser. No. 17/127,483, filed Dec. 18, 2020, are incorporated herein by reference, in their entirety. Aspects of the implementations can be modified, if necessary, to employ systems, circuits and concepts of the various patents, applications and publications to provide yet further implementations.
These and other changes can be made to the implementations in light of the above-detailed description. In general, in the following claims, the terms used should not be construed to limit the claims to the specific implementations disclosed in the specification and the claims, but should be construed to include all possible implementations along with the full scope of equivalents to which such claims are entitled. Accordingly, the claims are not limited by the disclosure.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2240050 | John | Apr 1941 | A |
| 2745055 | Woerdemann | May 1956 | A |
| 3374396 | Bell et al. | Mar 1968 | A |
| 4153927 | Owens | May 1979 | A |
| 4237377 | Sansum | Dec 1980 | A |
| 4663521 | Maile | May 1987 | A |
| 4811176 | Myhres | Mar 1989 | A |
| 5086379 | Denison et al. | Feb 1992 | A |
| 5150009 | Kling et al. | Sep 1992 | A |
| 5160202 | Légaré | Nov 1992 | A |
| 5161107 | Mayeaux et al. | Nov 1992 | A |
| 5230556 | Canty et al. | Jul 1993 | A |
| 5274350 | Larson | Dec 1993 | A |
| 5276385 | Itoh et al. | Jan 1994 | A |
| 5343121 | Terman et al. | Aug 1994 | A |
| 5349505 | Poppenheimer | Sep 1994 | A |
| 5450302 | Maase et al. | Sep 1995 | A |
| 5508589 | Archdekin | Apr 1996 | A |
| 5561351 | Vrionis et al. | Oct 1996 | A |
| 5589741 | Terman et al. | Dec 1996 | A |
| 5619127 | Warizaya | Apr 1997 | A |
| 5808294 | Neumann | Sep 1998 | A |
| 5838226 | Houggy et al. | Nov 1998 | A |
| 5869960 | Brand | Feb 1999 | A |
| 5892331 | Hollaway | Apr 1999 | A |
| 5892335 | Archer | Apr 1999 | A |
| 5936362 | Alt et al. | Aug 1999 | A |
| 5948829 | Wallajapet et al. | Sep 1999 | A |
| 6094919 | Bhatia | Aug 2000 | A |
| 6111739 | Wu et al. | Aug 2000 | A |
| 6149283 | Conway et al. | Nov 2000 | A |
| 6154015 | Ichiba | Nov 2000 | A |
| 6160353 | Mancuso | Dec 2000 | A |
| 6230497 | Morris et al. | May 2001 | B1 |
| D447266 | Verfuerth | Aug 2001 | S |
| 6377191 | Takubo | Apr 2002 | B1 |
| 6400101 | Biebl et al. | Jun 2002 | B1 |
| D460735 | Verfuerth | Jul 2002 | S |
| D463059 | Verfuerth | Sep 2002 | S |
| 6499860 | Begemann | Dec 2002 | B2 |
| 6585396 | Verfuerth | Jul 2003 | B1 |
| 6601972 | Sei et al. | Aug 2003 | B2 |
| D479826 | Verfuerth et al. | Sep 2003 | S |
| 6612720 | Beadle | Sep 2003 | B1 |
| D483332 | Verfuerth | Dec 2003 | S |
| 6674060 | Antila | Jan 2004 | B2 |
| 6681195 | Poland et al. | Jan 2004 | B1 |
| 6746274 | Verfuerth | Jun 2004 | B1 |
| 6753842 | Williams et al. | Jun 2004 | B1 |
| 6758580 | Verfuerth | Jul 2004 | B1 |
| 6787999 | Stimac et al. | Sep 2004 | B2 |
| 6828911 | Jones et al. | Dec 2004 | B2 |
| 6841947 | Berg-johansen | Jan 2005 | B2 |
| 6847156 | Kim | Jan 2005 | B2 |
| 6880956 | Zhang | Apr 2005 | B2 |
| 6885134 | Kurashima et al. | Apr 2005 | B2 |
| 6902292 | Lai | Jun 2005 | B2 |
| 6948829 | Verdes et al. | Sep 2005 | B2 |
| 6964501 | Ryan | Nov 2005 | B2 |
| 6964502 | Verfuerth | Nov 2005 | B1 |
| 6985827 | Williams et al. | Jan 2006 | B2 |
| 7019276 | Cloutier et al. | Mar 2006 | B2 |
| 7066622 | Alessio | Jun 2006 | B2 |
| 7081722 | Huynh et al. | Jul 2006 | B1 |
| 7084587 | Archdekin et al. | Aug 2006 | B2 |
| 7111961 | Trenchard et al. | Sep 2006 | B2 |
| 7122976 | Null et al. | Oct 2006 | B1 |
| 7144140 | Sun et al. | Dec 2006 | B2 |
| 7145179 | Petroski | Dec 2006 | B2 |
| 7165866 | Li | Jan 2007 | B2 |
| D538462 | Verfuerth et al. | Mar 2007 | S |
| 7188967 | Dalton et al. | Mar 2007 | B2 |
| 7190121 | Rose et al. | Mar 2007 | B2 |
| 7196477 | Richmond | Mar 2007 | B2 |
| 7213940 | Van et al. | May 2007 | B1 |
| 7218056 | Harwood | May 2007 | B1 |
| 7239087 | Ball | Jul 2007 | B2 |
| 7252385 | Engle et al. | Aug 2007 | B2 |
| 7258464 | Morris et al. | Aug 2007 | B2 |
| 7270441 | Fiene | Sep 2007 | B2 |
| 7281820 | Bayat et al. | Oct 2007 | B2 |
| 7294973 | Takahama et al. | Nov 2007 | B2 |
| D557817 | Verfuerth | Dec 2007 | S |
| D560469 | Bartol et al. | Jan 2008 | S |
| 7314261 | Jackson et al. | Jan 2008 | B2 |
| 7314291 | Tain et al. | Jan 2008 | B2 |
| 7317403 | Grootes et al. | Jan 2008 | B2 |
| 7322714 | Barnett et al. | Jan 2008 | B2 |
| 7330002 | Joung | Feb 2008 | B2 |
| 7330568 | Nagaoka et al. | Feb 2008 | B2 |
| 7339323 | Bucur | Mar 2008 | B2 |
| 7339471 | Chan et al. | Mar 2008 | B1 |
| 7341362 | Bjornson et al. | Mar 2008 | B2 |
| 7387403 | Mighetto | Jun 2008 | B2 |
| 7401942 | Verfuerth et al. | Jul 2008 | B1 |
| 7405524 | Null et al. | Jul 2008 | B2 |
| 7438440 | Dorogi | Oct 2008 | B2 |
| 7440280 | Shuy | Oct 2008 | B2 |
| 7458330 | MacDonald et al. | Dec 2008 | B2 |
| 7461964 | Aubrey | Dec 2008 | B1 |
| 7468723 | Collins | Dec 2008 | B1 |
| 7475002 | Mann | Jan 2009 | B1 |
| 7524089 | Park | Apr 2009 | B2 |
| 7538499 | Ashdown | May 2009 | B2 |
| 7547113 | Lee | Jun 2009 | B2 |
| 7549773 | Lim | Jun 2009 | B2 |
| D595894 | Verfuerth et al. | Jul 2009 | S |
| 7556406 | Petroski et al. | Jul 2009 | B2 |
| 7559674 | He et al. | Jul 2009 | B2 |
| 7563006 | Verfuerth et al. | Jul 2009 | B1 |
| 7564198 | Yamamoto et al. | Jul 2009 | B2 |
| 7569802 | Mullins | Aug 2009 | B1 |
| 7575338 | Verfuerth | Aug 2009 | B1 |
| 7578596 | Martin | Aug 2009 | B2 |
| 7578597 | Hoover et al. | Aug 2009 | B2 |
| 7581856 | Kang et al. | Sep 2009 | B2 |
| 7595595 | Mehta | Sep 2009 | B2 |
| 7623042 | Huizenga | Nov 2009 | B2 |
| D606697 | Verfuerth et al. | Dec 2009 | S |
| D606698 | Verfuerth et al. | Dec 2009 | S |
| 7626342 | Sun et al. | Dec 2009 | B2 |
| 7627372 | Vaisnys et al. | Dec 2009 | B2 |
| 7628506 | Verfuerth et al. | Dec 2009 | B2 |
| 7631324 | Buonasera et al. | Dec 2009 | B2 |
| 7633463 | Negru | Dec 2009 | B2 |
| 7635203 | Weaver et al. | Dec 2009 | B2 |
| 7637633 | Wong | Dec 2009 | B2 |
| 7638743 | Bartol et al. | Dec 2009 | B2 |
| 7654699 | Chang et al. | Feb 2010 | B2 |
| 7665862 | Villard | Feb 2010 | B2 |
| 7677753 | Wills | Mar 2010 | B1 |
| 7686461 | Goray et al. | Mar 2010 | B2 |
| 7688002 | Ashdown et al. | Mar 2010 | B2 |
| 7688222 | Peddie et al. | Mar 2010 | B2 |
| 7695160 | Hirata et al. | Apr 2010 | B2 |
| 7697925 | Wilson et al. | Apr 2010 | B1 |
| 7702135 | Hill et al. | Apr 2010 | B2 |
| 7703951 | Piepgras et al. | Apr 2010 | B2 |
| D617028 | Verfuerth et al. | Jun 2010 | S |
| D617029 | Verfuerth et al. | Jun 2010 | S |
| 7746003 | Verfuerth et al. | Jun 2010 | B2 |
| 7748879 | Koike 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 |
| 7766507 | Nakajima | Aug 2010 | B2 |
| 7766508 | Villard et al. | Aug 2010 | B2 |
| 7780310 | Verfuerth et al. | Aug 2010 | B2 |
| 7780314 | Seabrook | Aug 2010 | B2 |
| D623340 | Verfuerth et al. | Sep 2010 | S |
| 7798669 | Trojanowski et al. | Sep 2010 | B2 |
| 7804200 | Flaherty | Sep 2010 | B2 |
| 7828463 | Willis | Nov 2010 | B1 |
| 7834922 | Kurane | Nov 2010 | B2 |
| 7857497 | Koike et al. | Dec 2010 | B2 |
| 7872423 | Biery et al. | Jan 2011 | B2 |
| 7874699 | Liang | Jan 2011 | B2 |
| 7874710 | Tsai et al. | Jan 2011 | B2 |
| D632006 | Verfuerth et al. | Feb 2011 | S |
| 7901107 | Van et al. | Mar 2011 | B2 |
| 7932535 | Mahalingam et al. | Apr 2011 | B2 |
| 7940191 | Hierzer | May 2011 | B2 |
| 7952609 | Simerly et al. | May 2011 | B2 |
| 7960919 | Furukawa | Jun 2011 | B2 |
| 7976182 | Ribarich | Jul 2011 | B2 |
| 7983817 | Breed | Jul 2011 | B2 |
| 7985005 | Alexander et al. | Jul 2011 | B2 |
| 8018135 | Van et al. | Sep 2011 | B2 |
| 8057070 | Negley et al. | Nov 2011 | B2 |
| 8066410 | Booth et al. | Nov 2011 | B2 |
| D650225 | Bartol et al. | Dec 2011 | S |
| 8070312 | Verfuerth et al. | Dec 2011 | B2 |
| 8100552 | Spero | Jan 2012 | B2 |
| 8118450 | Villard | Feb 2012 | B2 |
| 8118456 | Reed et al. | Feb 2012 | B2 |
| 8136958 | Verfuerth et al. | Mar 2012 | B2 |
| 8143769 | Li | Mar 2012 | B2 |
| 8174212 | Tziony et al. | May 2012 | B2 |
| 8183797 | McKinney | May 2012 | B2 |
| 8186855 | Wassel et al. | May 2012 | B2 |
| RE43456 | Verfuerth et al. | Jun 2012 | E |
| 8207830 | Rutjes et al. | Jun 2012 | B2 |
| 8254137 | Wilkolaski et al. | Aug 2012 | B2 |
| 8260575 | Walters et al. | Sep 2012 | B2 |
| 8290710 | Cleland et al. | Oct 2012 | B2 |
| 8324641 | Yan et al. | Dec 2012 | B2 |
| 8324840 | Shteynberg et al. | Dec 2012 | B2 |
| 8334640 | Reed et al. | Dec 2012 | B2 |
| 8337043 | Verfuerth et al. | Dec 2012 | B2 |
| 8344665 | Verfuerth et al. | Jan 2013 | B2 |
| 8362677 | Morejon et al. | Jan 2013 | B1 |
| 8376583 | Wang et al. | Feb 2013 | B2 |
| 8378563 | Reed et al. | Feb 2013 | B2 |
| 8390475 | Feroldi | Mar 2013 | B2 |
| 8395329 | Jutras et al. | Mar 2013 | B2 |
| 8408739 | Villard et al. | Apr 2013 | B2 |
| 8427076 | Bourquin et al. | Apr 2013 | B2 |
| 8436556 | Eisele et al. | May 2013 | B2 |
| 8445826 | Verfuerth | May 2013 | B2 |
| 8450670 | Verfuerth et al. | May 2013 | B2 |
| 8457793 | Golding et al. | Jun 2013 | B2 |
| 8476565 | Verfuerth | Jul 2013 | B2 |
| 8508137 | Reed | Aug 2013 | B2 |
| 8541950 | Reed | Sep 2013 | B2 |
| 8547022 | Summerford et al. | Oct 2013 | B2 |
| 8586902 | Verfuerth | Nov 2013 | B2 |
| 8604701 | Verfuerth et al. | Dec 2013 | B2 |
| 8610358 | Reed | Dec 2013 | B2 |
| 8629621 | Reed | Jan 2014 | B2 |
| 8637877 | Negley | Jan 2014 | B2 |
| 8646944 | Villard | Feb 2014 | B2 |
| 8674608 | Holland et al. | Mar 2014 | B2 |
| 8749403 | King et al. | Jun 2014 | B2 |
| 8749635 | Hogasten et al. | Jun 2014 | B2 |
| 8764237 | Wang et al. | Jul 2014 | B2 |
| 8779340 | Verfuerth et al. | Jul 2014 | B2 |
| 8779686 | Jin | Jul 2014 | B2 |
| 8794804 | Verfuerth et al. | Aug 2014 | B2 |
| 8810138 | Reed | Aug 2014 | B2 |
| 8816576 | Erion et al. | Aug 2014 | B1 |
| 8858019 | Novak et al. | Oct 2014 | B2 |
| 8866392 | Chen | Oct 2014 | B2 |
| 8866582 | Verfuerth et al. | Oct 2014 | B2 |
| 8872430 | Yang | Oct 2014 | B2 |
| 8872964 | Reed et al. | Oct 2014 | B2 |
| 8878440 | Reed | Nov 2014 | B2 |
| 8884203 | Verfuerth et al. | Nov 2014 | B2 |
| 8896215 | Reed et al. | Nov 2014 | B2 |
| 8901825 | Reed | Dec 2014 | B2 |
| 8921751 | Verfuerth | Dec 2014 | B2 |
| 8922124 | Reed et al. | Dec 2014 | B2 |
| 8926138 | Reed et al. | Jan 2015 | B2 |
| 8926139 | Reed et al. | Jan 2015 | B2 |
| 8975827 | Chobot et al. | Mar 2015 | B2 |
| 8987992 | Reed | Mar 2015 | B2 |
| 8988005 | Jungwirth et al. | Mar 2015 | B2 |
| 9002522 | Mohan et al. | Apr 2015 | B2 |
| 9024545 | Bloch et al. | May 2015 | B2 |
| 9084310 | Bedell et al. | Jul 2015 | B2 |
| 9107026 | Viswanadham et al. | Aug 2015 | B1 |
| 9119270 | Chen et al. | Aug 2015 | B2 |
| 9204523 | Reed et al. | Dec 2015 | B2 |
| 9210751 | Reed | Dec 2015 | B2 |
| 9210759 | Reed | Dec 2015 | B2 |
| 9288873 | Reed | Mar 2016 | B2 |
| 9312451 | Reed et al. | Apr 2016 | B2 |
| 9357618 | Pandharipande et al. | May 2016 | B2 |
| 9414449 | Reed | Aug 2016 | B2 |
| 9445485 | Reed | Sep 2016 | B2 |
| 9466443 | Reed | Oct 2016 | B2 |
| 9572230 | Reed | Feb 2017 | B2 |
| 9657922 | Negley et al. | May 2017 | B2 |
| 9693433 | Reed et al. | Jun 2017 | B2 |
| 9713228 | Reed | Jul 2017 | B2 |
| 9801248 | Reed et al. | Oct 2017 | B2 |
| 9930758 | Jayawardena et al. | Mar 2018 | B2 |
| 10009983 | Noesner | Jun 2018 | B2 |
| 10068468 | John et al. | Sep 2018 | B2 |
| 10098212 | Vendetti | Oct 2018 | B2 |
| 10219360 | Vendetti et al. | Feb 2019 | B2 |
| 10390414 | Vendetti et al. | Aug 2019 | B2 |
| 20020084767 | Arai | Jul 2002 | A1 |
| 20020113192 | Antila | Aug 2002 | A1 |
| 20030016143 | Ghazarian | Jan 2003 | A1 |
| 20030123521 | Luoma | Jul 2003 | A1 |
| 20030184672 | Wu et al. | Oct 2003 | A1 |
| 20040095772 | Hoover et al. | May 2004 | A1 |
| 20040105264 | Spero | Jun 2004 | A1 |
| 20040120148 | Morris et al. | Jun 2004 | A1 |
| 20040120156 | Ryan | Jun 2004 | A1 |
| 20040192227 | Beach et al. | Sep 2004 | A1 |
| 20040201992 | Dalton et al. | Oct 2004 | A1 |
| 20050057187 | Catalano | Mar 2005 | A1 |
| 20050099802 | Lai | May 2005 | A1 |
| 20050117344 | Bucher et al. | Jun 2005 | A1 |
| 20050135101 | Richmond | Jun 2005 | A1 |
| 20050146884 | Scheithauer | Jul 2005 | A1 |
| 20050174762 | Fogerlie | Aug 2005 | A1 |
| 20050174780 | Park | Aug 2005 | A1 |
| 20050179404 | Veskovic et al. | Aug 2005 | A1 |
| 20050231133 | Lys | Oct 2005 | A1 |
| 20050243022 | Negru | Nov 2005 | A1 |
| 20050254013 | Engle et al. | Nov 2005 | A1 |
| 20050265019 | Sommers et al. | Dec 2005 | A1 |
| 20060001384 | Tain et al. | Jan 2006 | A1 |
| 20060014118 | Utama | Jan 2006 | A1 |
| 20060034075 | Alessio | Feb 2006 | A1 |
| 20060053459 | Simerly et al. | Mar 2006 | A1 |
| 20060066264 | Ishigaki et al. | Mar 2006 | A1 |
| 20060098440 | Allen | May 2006 | A1 |
| 20060146652 | Huizi et al. | Jul 2006 | A1 |
| 20060158130 | Furukawa | Jul 2006 | A1 |
| 20060202914 | Ashdown | Sep 2006 | A1 |
| 20060208667 | Lys et al. | Sep 2006 | A1 |
| 20060259080 | Vaisnys et al. | Nov 2006 | A1 |
| 20060262544 | Piepgras et al. | Nov 2006 | A1 |
| 20060277823 | Barnett et al. | Dec 2006 | A1 |
| 20070032990 | Williams et al. | Feb 2007 | A1 |
| 20070096118 | Mahalingam et al. | May 2007 | A1 |
| 20070102033 | Petrocy | May 2007 | A1 |
| 20070139961 | Cheah et al. | Jun 2007 | A1 |
| 20070147046 | Arik et al. | Jun 2007 | A1 |
| 20070153550 | Lehman et al. | Jul 2007 | A1 |
| 20070159819 | Bayat et al. | Jul 2007 | A1 |
| 20070164689 | Suzuki | Jul 2007 | A1 |
| 20070183156 | Shan | Aug 2007 | A1 |
| 20070217093 | Xue et al. | Sep 2007 | A1 |
| 20070224461 | Oh | Sep 2007 | A1 |
| 20070225933 | Shimomura | Sep 2007 | A1 |
| 20070247853 | Dorogi | Oct 2007 | A1 |
| 20070279921 | Alexander et al. | Dec 2007 | A1 |
| 20070285000 | Lim et al. | Dec 2007 | A1 |
| 20070297184 | Isely | Dec 2007 | A1 |
| 20080018261 | Kastner | Jan 2008 | A1 |
| 20080025020 | Kolb | Jan 2008 | A1 |
| 20080043106 | Hassapis et al. | Feb 2008 | A1 |
| 20080062687 | Behar et al. | Mar 2008 | A1 |
| 20080106907 | Trott et al. | May 2008 | A1 |
| 20080130304 | Rash et al. | Jun 2008 | A1 |
| 20080205068 | Neeld et al. | Aug 2008 | A1 |
| 20080215279 | Salsbury et al. | Sep 2008 | A1 |
| 20080224623 | Yu | Sep 2008 | A1 |
| 20080232116 | Kim | Sep 2008 | A1 |
| 20080248837 | Kunkel | Oct 2008 | A1 |
| 20080266839 | Claypool et al. | Oct 2008 | A1 |
| 20080271065 | Buonasera et al. | Oct 2008 | A1 |
| 20080291661 | Martin | Nov 2008 | A1 |
| 20080298058 | Kan et al. | Dec 2008 | A1 |
| 20090000217 | Verfuerth et al. | Jan 2009 | A1 |
| 20090001372 | Arik et al. | Jan 2009 | A1 |
| 20090046151 | Nagaoka et al. | Feb 2009 | A1 |
| 20090058320 | Chou et al. | Mar 2009 | A1 |
| 20090129067 | Fan et al. | May 2009 | A1 |
| 20090153062 | Guo et al. | Jun 2009 | A1 |
| 20090160358 | Leiderman | Jun 2009 | A1 |
| 20090161356 | Negley et al. | Jun 2009 | A1 |
| 20090167203 | Dahlman et al. | Jul 2009 | A1 |
| 20090195162 | Maurer et al. | Aug 2009 | A1 |
| 20090195179 | Joseph et al. | Aug 2009 | A1 |
| 20090225540 | Chen | Sep 2009 | A1 |
| 20090230883 | Haug | Sep 2009 | A1 |
| 20090235208 | Nakayama et al. | Sep 2009 | A1 |
| 20090244899 | Chyn | Oct 2009 | A1 |
| 20090261735 | Sibalich et al. | Oct 2009 | A1 |
| 20090268023 | Hsieh | Oct 2009 | A1 |
| 20090273290 | Ziegenfuss | Nov 2009 | A1 |
| 20090278474 | Reed et al. | Nov 2009 | A1 |
| 20090278479 | Planter et al. | Nov 2009 | A1 |
| 20090284155 | Reed et al. | Nov 2009 | A1 |
| 20090315485 | Verfuerth et al. | Dec 2009 | A1 |
| 20100001652 | Damsleth | Jan 2010 | A1 |
| 20100008090 | Li et al. | Jan 2010 | A1 |
| 20100052557 | Van Der Veen et al. | Mar 2010 | A1 |
| 20100053962 | Mo et al. | Mar 2010 | A1 |
| 20100060130 | Li | Mar 2010 | A1 |
| 20100084979 | Balczarek et al. | Apr 2010 | A1 |
| 20100090577 | Reed et al. | Apr 2010 | A1 |
| 20100096460 | Carlson et al. | Apr 2010 | A1 |
| 20100123403 | Reed | May 2010 | A1 |
| 20100149822 | Cogliano et al. | Jun 2010 | A1 |
| 20100164406 | Kost et al. | Jul 2010 | A1 |
| 20100171442 | Draper et al. | Jul 2010 | A1 |
| 20100177519 | Schlitz | Jul 2010 | A1 |
| 20100237711 | Parsons | Sep 2010 | A1 |
| 20100244708 | Cheung et al. | Sep 2010 | A1 |
| 20100246168 | Verfuerth et al. | Sep 2010 | A1 |
| 20100259193 | Umezawa et al. | Oct 2010 | A1 |
| 20100262296 | Davis et al. | Oct 2010 | A1 |
| 20100270945 | Chang et al. | Oct 2010 | A1 |
| 20100271802 | Recker et al. | Oct 2010 | A1 |
| 20100277082 | Reed et al. | Nov 2010 | A1 |
| 20100277914 | Bachl et al. | Nov 2010 | A1 |
| 20100277917 | Shan | Nov 2010 | A1 |
| 20100290236 | Gingrich et al. | Nov 2010 | A1 |
| 20100295454 | Reed | Nov 2010 | A1 |
| 20100295455 | Reed | Nov 2010 | A1 |
| 20100295946 | Reed et al. | Nov 2010 | A1 |
| 20100309310 | Albright | Dec 2010 | A1 |
| 20100328946 | Borkar et al. | Dec 2010 | A1 |
| 20100328947 | Chang et al. | Dec 2010 | A1 |
| 20110001626 | Yip et al. | Jan 2011 | A1 |
| 20110006703 | Wu et al. | Jan 2011 | A1 |
| 20110026264 | Reed et al. | Feb 2011 | A1 |
| 20110090686 | Pickard | Apr 2011 | A1 |
| 20110175518 | Reed et al. | Jul 2011 | A1 |
| 20110176297 | Hsia et al. | Jul 2011 | A1 |
| 20110204845 | Paparo et al. | Aug 2011 | A1 |
| 20110215724 | Chakravarty et al. | Sep 2011 | A1 |
| 20110215731 | Jeong et al. | Sep 2011 | A1 |
| 20110221346 | Lee et al. | Sep 2011 | A1 |
| 20110235317 | Verfuerth et al. | Sep 2011 | A1 |
| 20110248812 | Hu et al. | Oct 2011 | A1 |
| 20110251751 | Knight | Oct 2011 | A1 |
| 20110282468 | Ashdown | Nov 2011 | A1 |
| 20110310605 | Renn et al. | Dec 2011 | A1 |
| 20120001566 | Josefowicz et al. | Jan 2012 | A1 |
| 20120019971 | Flaherty et al. | Jan 2012 | A1 |
| 20120038490 | Verfuerth | Feb 2012 | A1 |
| 20120081906 | Verfuerth et al. | Apr 2012 | A1 |
| 20120086561 | Ilyes | Apr 2012 | A1 |
| 20120098439 | Recker et al. | Apr 2012 | A1 |
| 20120119669 | Melanson et al. | May 2012 | A1 |
| 20120119682 | Warton | May 2012 | A1 |
| 20120139426 | Ilyes et al. | Jun 2012 | A1 |
| 20120143383 | Cooperrider et al. | Jun 2012 | A1 |
| 20120146518 | Setomoto et al. | Jun 2012 | A1 |
| 20120153854 | Setomoto et al. | Jun 2012 | A1 |
| 20120169053 | Tchoryk, Jr. et al. | Jul 2012 | A1 |
| 20120169239 | Chen et al. | Jul 2012 | A1 |
| 20120181935 | Velazquez | Jul 2012 | A1 |
| 20120194054 | Johnston et al. | Aug 2012 | A1 |
| 20120209755 | Verfuerth et al. | Aug 2012 | A1 |
| 20120221154 | Runge | Aug 2012 | A1 |
| 20120224363 | Van | Sep 2012 | A1 |
| 20120230584 | Kubo et al. | Sep 2012 | A1 |
| 20120242254 | Kim et al. | Sep 2012 | A1 |
| 20120262069 | Reed | Oct 2012 | A1 |
| 20120286770 | Schröder et al. | Nov 2012 | A1 |
| 20130033183 | Verfuerth et al. | Feb 2013 | A1 |
| 20130043792 | Reed | Feb 2013 | A1 |
| 20130049613 | Reed | Feb 2013 | A1 |
| 20130057158 | Josefowicz et al. | Mar 2013 | A1 |
| 20130126715 | Flaherty | May 2013 | A1 |
| 20130131882 | Verfuerth et al. | May 2013 | A1 |
| 20130141000 | Wei et al. | Jun 2013 | A1 |
| 20130141010 | Reed et al. | Jun 2013 | A1 |
| 20130154488 | Sadwick et al. | Jun 2013 | A1 |
| 20130163243 | Reed | Jun 2013 | A1 |
| 20130193857 | Tlachac et al. | Aug 2013 | A1 |
| 20130210252 | Ilyes | Aug 2013 | A1 |
| 20130229518 | Reed et al. | Sep 2013 | A1 |
| 20130235202 | Nagaoka et al. | Sep 2013 | A1 |
| 20130249429 | Woytowitz et al. | Sep 2013 | A1 |
| 20130249479 | Partovi | Sep 2013 | A1 |
| 20130293112 | Reed et al. | Nov 2013 | A1 |
| 20130307418 | Reed | Nov 2013 | A1 |
| 20130308325 | Verfuerth et al. | Nov 2013 | A1 |
| 20130313982 | Reed | Nov 2013 | A1 |
| 20130320862 | Campbell et al. | Dec 2013 | A1 |
| 20130340353 | Whiting et al. | Dec 2013 | A1 |
| 20140001961 | Anderson et al. | Jan 2014 | A1 |
| 20140028198 | Reed et al. | Jan 2014 | A1 |
| 20140028200 | Van Wagoner et al. | Jan 2014 | A1 |
| 20140055990 | Reed | Feb 2014 | A1 |
| 20140070964 | Rupprath et al. | Mar 2014 | A1 |
| 20140078308 | Verfuerth | Mar 2014 | A1 |
| 20140097759 | Verfuerth et al. | Apr 2014 | A1 |
| 20140139116 | Reed | May 2014 | A1 |
| 20140140052 | Villard | May 2014 | A1 |
| 20140159585 | Reed | Jun 2014 | A1 |
| 20140166447 | Thea et al. | Jun 2014 | A1 |
| 20140203714 | Zhang et al. | Jul 2014 | A1 |
| 20140225521 | Reed | Aug 2014 | A1 |
| 20140244044 | Davis et al. | Aug 2014 | A1 |
| 20140252961 | Ramer et al. | Sep 2014 | A1 |
| 20140265894 | Weaver | Sep 2014 | A1 |
| 20140265897 | Taipale et al. | Sep 2014 | A1 |
| 20140313719 | Wang et al. | Oct 2014 | A1 |
| 20140320027 | Reed | Oct 2014 | A1 |
| 20140339390 | Verfuerth et al. | Nov 2014 | A1 |
| 20140359078 | Liu | Dec 2014 | A1 |
| 20150015716 | Reed et al. | Jan 2015 | A1 |
| 20150028693 | Reed | Jan 2015 | A1 |
| 20150028770 | Verfuerth et al. | Jan 2015 | A1 |
| 20150069920 | Denteneer et al. | Mar 2015 | A1 |
| 20150077019 | Reed et al. | Mar 2015 | A1 |
| 20150078005 | Renn et al. | Mar 2015 | A1 |
| 20150084520 | Reed | Mar 2015 | A1 |
| 20150123563 | Dahlen | May 2015 | A1 |
| 20150160305 | Ilyes et al. | Jun 2015 | A1 |
| 20150208479 | Radermacher et al. | Jul 2015 | A1 |
| 20150280782 | Airbinger et al. | Oct 2015 | A1 |
| 20150312983 | Hu et al. | Oct 2015 | A1 |
| 20160021713 | Reed | Jan 2016 | A1 |
| 20160037605 | Reed et al. | Feb 2016 | A1 |
| 20160113084 | White et al. | Apr 2016 | A1 |
| 20160150622 | Flinsenberg et al. | May 2016 | A1 |
| 20160234899 | Reed et al. | Aug 2016 | A1 |
| 20160286623 | Reed | Sep 2016 | A1 |
| 20160295656 | Lenk | Oct 2016 | A1 |
| 20160323955 | Reed | Nov 2016 | A1 |
| 20170311424 | Vendetti et al. | Oct 2017 | A1 |
| 20180035518 | Cook | Feb 2018 | A1 |
| 20180083438 | Reed | Mar 2018 | A1 |
| 20180083539 | Reed | Mar 2018 | A1 |
| 20180288860 | Vendetti et al. | Oct 2018 | A1 |
| 20180338367 | Reed | Nov 2018 | A1 |
| 20190394862 | Vendetti et al. | Dec 2019 | A1 |
| 20200029404 | Reed | Jan 2020 | A1 |
| 20200045794 | Reed et al. | Feb 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 103162187 | Jun 2013 | CN |
| 40 01 980 | Aug 1990 | DE |
| 19810827 | Sep 1999 | DE |
| 1 734 795 | Dec 2006 | EP |
| 2 320 713 | May 2011 | EP |
| 2 559 937 | Feb 2013 | EP |
| 2 629 491 | Aug 2013 | EP |
| 1 459 600 | Feb 2014 | EP |
| 2781138 | Sep 2014 | EP |
| 2 883 306 | Sep 2006 | FR |
| 6-335241 | Dec 1994 | JP |
| 2001-333420 | Nov 2001 | JP |
| 2004-279668 | Oct 2004 | JP |
| 2004-320024 | Nov 2004 | JP |
| 2004-349065 | Dec 2004 | JP |
| 2005093171 | Apr 2005 | JP |
| 2005-198238 | Jul 2005 | JP |
| 2005198238 | Jul 2005 | JP |
| 2005-310997 | Nov 2005 | JP |
| 2006031977 | Feb 2006 | JP |
| 2006-179672 | Jul 2006 | JP |
| 2006-244711 | Sep 2006 | JP |
| 2008-59811 | Mar 2008 | JP |
| 2008-509538 | Mar 2008 | JP |
| 200859811 | Mar 2008 | JP |
| 2008-130523 | Jun 2008 | JP |
| 2008-159483 | Jul 2008 | JP |
| 2008-177144 | Jul 2008 | JP |
| 2008529177 | Jul 2008 | JP |
| 2008-535279 | Aug 2008 | JP |
| 2010-504628 | Feb 2010 | JP |
| 10-2005-0078403 | Aug 2005 | KR |
| 20060071869 | Jun 2006 | KR |
| 10-2006-0086254 | Jul 2006 | KR |
| 20080094344 | Oct 2008 | KR |
| 10-2009-0042400 | Apr 2009 | KR |
| 10-0935736 | Jan 2010 | KR |
| 20-2010-0007230 | Jul 2010 | KR |
| 10-1001276 | Dec 2010 | KR |
| 10-1044224 | Jun 2011 | KR |
| 10-1150876 | May 2012 | KR |
| 20120108662 | Oct 2012 | KR |
| 02076068 | Sep 2002 | WO |
| 02076069 | Sep 2002 | WO |
| 03056882 | Jul 2003 | WO |
| 2005003625 | Jan 2005 | WO |
| 2006057866 | Jun 2006 | WO |
| 2007023454 | Mar 2007 | WO |
| 2007036873 | Apr 2007 | WO |
| 2008030450 | Mar 2008 | WO |
| 2008034242 | Mar 2008 | WO |
| 2009040703 | Apr 2009 | WO |
| 2009105168 | Aug 2009 | WO |
| 2010086757 | Aug 2010 | WO |
| 2010085882 | Aug 2010 | WO |
| 2010133719 | Nov 2010 | WO |
| 2011005441 | Jan 2011 | WO |
| 2011019806 | Feb 2011 | WO |
| 2011063302 | May 2011 | WO |
| 2011129309 | Oct 2011 | WO |
| 2012006710 | Jan 2012 | WO |
| 2012033750 | Mar 2012 | WO |
| 2012142115 | Oct 2012 | WO |
| 2013028834 | Feb 2013 | WO |
| 2013074900 | May 2013 | WO |
| 2014018773 | Jan 2014 | WO |
| 2014039683 | Mar 2014 | WO |
| 2014078854 | May 2014 | WO |
| 2015039120 | Mar 2015 | WO |
| Entry |
|---|
| “A Review of the Literature on Light Flicker: Ergonomics, Biological Attributes, Potential Health Effects, and Methods in Which Some LED Lighting May Introduce Flicker,” IEEE Standard P1789, Feb. 26, 2010, 26 pages. |
| Koninklijke Philips N.V., “High Intensity Discharge Lamps: MasterColor Ceramic Metal Halide Lamps,” Lighting Catalog, Lamp Specification Guide, p. 70, 2013. |
| Non-Final Office Action Issued in U.S. Appl. No. 16/842,924, dated Jun. 3, 2021, 13 pages. |
| Notice of Allowance dated Nov. 22, 2021, for Deed, “Photocontroller to Control Operation of a Luminaire Having a Dimming Line” U.S. Appl. No. 16/342,924, 9 pages. |
| “Lcd Backlight I/O Ports and Power Protection Circuit Design,” dated May 2, 2011, retrieved Jun. 10, 2011, from http://www.chipoy.info/gadgets/lcd-backlight-i-o-ports-and-power-pr . . . , 4 pages. |
| Corrected Notice of Allowance, dated Aug. 12, 2015, and Notice of Allowance, dated Jul. 31, 2015 for Reed et al., “Remotely Adjustable Solid-State Lamp,” U.S. Appl. No. 13/875,130, 11 pages. |
| EE Herald, “Devices to protect High brightness LED from ESD,” dated Mar. 16, 2009, retrieved Jun. 10, 2011, from http://www.eeherald.com/section/new-products/npl00779.html, 1 page. |
| European Office Action, dated Aug. 11, 2017, for European Application No. 13 823 055.2-1802, 4 pages. |
| Extended European Search Report dated Aug. 25, 2016, for corresponding EP Application No. 14843796.5-1757, 6 pages. |
| Extended European Search Report dated Jan. 4, 2016, for corresponding EP Application No. 13823055.2-1802, 7 pages. |
| Extended European Search Report dated Oct. 21, 2015, for corresponding EP Application No. 13835001.2-1802, 7 pages. |
| Extended European Search Report, dated Aug. 13, 2014, for corresponding European Application No. 09826926.9, 8 pages. |
| Extended European Search Report, dated May 3, 2016, for corresponding European Application No. 12771286.7, 9 pages. |
| Extended European Search Report, dated Sep. 28, 2015, for corresponding European Application No. 12850159.0-1802, 6 pages. |
| Fairchild Semiconductor, “LED Application Design Guide Using Half-Bridge LLC Resonant Converter for 100W Street Lighting,” AN-9729, Fairchild Semiconductor Corporation, Rev. 1.0.0, Mar. 22, 2011, 17 pages. |
| Huang, “Designing an LLC Resonant Half-Bridge Power Converter,” 2010 Texas Instruments Power Supply Design Seminar, SEM1900, Topic 3, TI Literature No. SLUP263, Copyright 2010, 2011, Texas Instruments Incorporated, 28 pages. |
| International Search Report and Written Opinion, dated Feb. 29, 2016, for PCT/US2015/053000, 20 pages. |
| International Search Report and Written Opinion, dated Feb. 29, 2016, for PCT/US2015/053006, 21 pages. |
| International Search Report and Written Opinion, dated Jan. 13, 2016. for PCT/US2015/053009, 15 pages. |
| International Search Report dated Nov. 11, 2014, for International Application No. PCT/US2014/047867, 3 pages. |
| International Search Report, dated Dec. 13, 2010 for PCT/US2010/035649, 3 pages. |
| International Search Report, dated Dec. 15, 2010 for PCT/US2010/035658, 3 pages. |
| International Search Report, dated Dec. 28, 2010 for PCT/US2010/035651, 3 pages. |
| International Search Report, dated Dec. 30, 2013 for PCT/US2013/058266, 3 pages. |
| International Search Report, dated Feb. 26, 2014, for PCT/US2013/070794, 3 pages. |
| International Search Report, dated Feb. 27, 2013, for PCT/US2012/065476, 3 pages. |
| International Search Report, dated Jan. 14, 2013, for PCT/US2012/052009, 3 pages. |
| International Search Report, dated Jul. 9, 2009 for PCT/US2009/043171, 5 pages. |
| International Search Report, dated Jun. 21, 2010, for PCT/US2009/064625, 3 pages. |
| International Search Report, dated Nov. 19, 2013 for PCT/US2013/052092, 4 pages. |
| International Search Report, dated Oct. 8, 2012 for PCT/US2012/033059, 3 pages. |
| International Search Report, dated Sep. 30, 2011, for PCT/US2011/021359, 3 pages. |
| Japanese Office Action, dated Jan. 6, 2015, for corresponding Japanese Application No. 2011-536564, 6 pages. |
| Kadirvel et al., “Self-Powered, Ambient Light Sensor Using bq25504,” Texas Instruments, Application Report, SLUA629—Jan. 2012, 6 pages. |
| Littelfuse, “Application Note: Protecting LEDs in Product Designs,” 2009, 2 pages. |
| Notice of Allowance dated Apr. 11, 2014, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 13/943,537, 9 pages. |
| Notice of Allowance dated Apr. 12, 2013, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 12/784,093, 9 pages. |
| Notice of Allowance dated Apr. 27, 2015, for Reed et al., “Apparatus and Method of Operating a Luminaire,” U.S. Appl. No. 13/558,191, 8 pages. |
| Notice of Allowance dated Aug. 29, 2014, for Reed et al., “Adjustable Output Solid-State Lamp With Security Features,” U.S. Appl. No. 13/679,687, 9 pages. |
| Notice Of Allowance dated Jul. 1, 2014, for Reed, “Luminaire With Atmospheric Electrical Activity Detection and Visual Alert Capabilities,” U.S. Appl. No. 13/786,114, 9 pages. |
| Notice of Allowance dated Jul. 30, 2014, for Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” U.S. Appl. No. 13/085,301, 5 pages. |
| Notice of Allowance dated Jul. 7, 2014, for Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” U.S. Appl. No. 13/604,327, 8 pages. |
| Notice of Allowance dated Jun. 19, 2015, for Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire” U.S. Appl. No. 14/552,274, 9 pages. |
| Notice Of Allowance dated Jun. 20, 2014, for Reed et al., “Long-Range Motion Detection for Illumination Control,” U.S. Appl. No. 12/784,080, 7 pages. |
| Notice of Allowance dated Mar. 16, 2017, for U.S. Appl. No. 14/552,274, Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” 9 pages. |
| Notice of Allowance dated Mar. 24, 2017, for Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” U.S. Appl. No. 14/557,275, 23 pages. |
| Notice of Allowance dated May 23, 2013, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 12/784,091, 6 pages. |
| Notice of Allowance dated Nov. 5, 2014, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 14/329,508, 10 pages. |
| Notice of Allowance dated Oct. 5, 2016 for U.S. Appl. No. 14/869,511, Reed, “Centralized Control of Area Lighting Hours of Illumination,” 8 pages. |
| Notice of Allowance dated Sep. 12, 2013, for Reed, “Electrostatic Discharge Protection for Luminaire,” U.S. Appl. No. 13/212,074, 6 pages. |
| Notice of Allowance dated Sep. 30, 2013, for Reed, “Resonant Network for Reduction of Flicker Perception in Solid State Lighting Systems,” U.S. Appl. No. 13/592,590, 9 pages. |
| Notice of Allowance, dated Oct. 14, 2011, for Reed et al., “Low-Profile Pathway Illumination System,” U.S. Appl. No. 12/437,472, 9 pages. |
| Notice of Allowance, dated Jun. 14, 2017, for U.S. Appl. No. 14/557,275, Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” 2 pages. |
| Notice of Allowance, dated Jun. 22, 2017, for U.S. Appl. No. 14/816,754, Reed et al., “Apparatus and Method of Operating a Luminaire ,” 11 pages. |
| Office Action dated Apr. 21, 2015, for Reed et al., “Remotely Adjustable Solid-State Lamp,” U.S. Appl. No. 13/875,130, 10 pages. |
| Office Action dated Apr. 23, 2014, for Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” U.S. Appl. No. 13/085,301, 12 pages. |
| Office Action dated Apr. 24, 2013, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 12/784,091, 12 pages. |
| Office Action dated Aug. 23, 2016, for Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” U.S. Appl. No. 14/557,275, 23 pages. |
| Office Action dated Aug. 28, 2014, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 14/329,508, 8 pages. |
| Office Action dated Aug. 31, 2016, for U.S. Appl. No. 14/869,501,Reed, “Asset Management System for Outdoor Luminaires,” 15 pages. |
| Office Action dated Dec. 17, 2014, for Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” U.S. Appl. No. 13/786,332, 20 pages. |
| Office Action dated Dec. 21, 2012, for Reed et al., “Long-Range Motion Detection for Illumination Control,” U.S. Appl. No. 12/784,080, 26 pages. |
| Office Action dated Dec. 22, 2014, for Reed et al., “Apparatus and Method of Operating a Luminaire,” U.S. Appl. No. 13/558,191, 17 pages. |
| Office Action dated Dec. 5, 2012, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 12/784,091, 18 pages. |
| Office Action dated Dec. 5, 2012, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 12/784,093, 13 pages. |
| Office Action dated Feb. 17, 2017, for U.S. Appl. No. 14/939,856, Reed et al., “Luminaire With Adjustable Illumination Pattern,” 13 pages. |
| Office Action dated Feb. 27, 2014, for Reed et al., “Adjustable Output Solid-State Lamp With Security Features,” U.S. Appl. No. 13/679,687, 11 pages. |
| Office Action dated Jan. 30, 2014, for Reed et al., “Long-Range Motion Detection for Illumination Control,” U.S. Appl. No. 12/784,080, 26 pages. |
| Office Action dated Jul. 22, 2013, for Reed et al., “Long-Range Motion Detection for Illumination Control,” U.S. Appl. No. 12/784,080, 29 pages. |
| Office Action dated Mar. 15, 2013 for Reed et al., “Electrostatic Discharge Protection for Luminaire,” U.S. Appl. No. 13/212,074, 11 pages. |
| Office Action dated Mar. 2, 2015, for Reed et al., “Apparatus and Method for Schedule Based Operations of a Luminaire,” U.S. Appl. No. 14/552,274, 7 pages. |
| Office Action dated Mar. 26, 2014, for Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” U.S. Appl. No. 13/604,327, 10 pages. |
| Office Action dated Nov. 27, 2013, for Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 13/943,537, 8 pages. |
| Office Action dated Oct. 1, 2013, for Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” U.S. Appl. No. 13/085,301, 11 pages. |
| Office Action dated Sep. 19, 2016, for U.S. Appl. No. 14/552,274, Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” 9 pages. |
| Office Action, dated May 5, 2011, for Reed et al., “Low-Profile Pathway Illumination System,” U.S. Appl. No. 12/437,472, 24 pages. |
| Panasonic Electronic Components, “LED Lighting Solutions,” 2009, 6 pages. |
| Reed et al., “Adjustable Output Solid-State Lamp With Security Features,” Amendment filed Jun. 24, 2014, for U.S. Appl. No. 13/679,687, 11 pages. |
| Reed et al., “Adjustable Output Solid-State Lamp With Security Features,” U.S. Appl. No. 61/561,616, filed Nov. 18, 2011, 33 pages. |
| Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire” Amendment filed Dec. 7, 2016, for U.S. Appl. No. 14/552,274, 11 pages. |
| Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire” Amendment filed Jun. 1, 2015, for U.S. Appl. No. 14/552,274, 14 pages. |
| Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” Amendment filed Jun. 24, 2014, for U.S. Appl. No. 13/604,327, 14 pages. |
| Reed et al., “Apparatus and Method for Schedule Based Operation of a Luminaire,” Amendment filed Jun. 7, 2016, for U.S. Appl. No. 14/552,274, 14 pages. |
| Reed et al., “Apparatus and Method of Operating a Luminaire,” Amendment filed Mar. 19, 2015, for U.S. Appl. No. 13/558,191, 20 pages. |
| Reed et al., “Apparatus, Method to Change Light Source Color Temperature with Reduced Optical Filtering Losses,” U.S. Appl. No. 61/295,519, filed Jan. 15, 2010, 35 pages. |
| Reed et al., “Apparatus, Method to Change Light Source Color Temperature With Reduced Optical Filtering Losses,” U.S. Appl. No. 61/406,490, filed Oct. 25, 2010, 46 pages. |
| Reed et al., “Apparatus, Method to Enhance Color Contrast in Phosphor-Based Solid State Lights,” U.S. Appl. No. 61/534,722, filed Sep. 14, 2011, 53 pages. |
| Reed et al., “Electrically Isolated Heat Sink for Solid-State Light,” U.S. Appl. No. 61/229,435, filed Jul. 29, 2009, 29 pages. |
| Reed et al., “Gas-Discharge Lamp Replacement With Passive Cooling,” U.S. Appl. No. 61/174,913, filed May 1, 2009, 29 pages. |
| Reed et al., “Gas-Discharge Lamp Replacement,” U.S. Appl. No. 61/052,924, filed May 13, 2008, 32 pages. |
| Reed et al., “Long-Range Motion Detection for Illumination Control,” Amendment filed Apr. 22, 2013, for U.S. Appl. No. 12/784,080, 17 pages. |
| Reed et al., “Long-Range Motion Detection for Illumination Control,” Amendment filed Apr. 28, 2014, for U.S. Appl. No. 12/784,080, 20 pages. |
| Reed et al., “Long-Range Motion Detection for Illumination Control,” Amendment filed Sep. 27, 2013, for U.S. Appl. No. 12/784,080, 20 pages. |
| Reed et al., “Long-Range Motion Detection for Illumination Control,” U.S. Appl. No. 61/180,017, filed May 20, 2009, 32 pages. |
| Reed et al., “Low-Profile Pathway Illumination System,” Amendment filed Jul. 29, 2011, for U.S. Appl. No. 12/437,472, 19 pages. |
| Reed et al., “Low-Profile Pathway Illumination System,” U.S. Appl. No. 61/051,619, filed May 8, 2008, 25 pages. |
| Reed et al., “Remotely Adjustable Solid-State Lamp,” Amendment filed Apr. 1, 2015, for U.S. Appl. No. 13/875,130, 14 pages. |
| Reed et al., “Remotely Adjustable Solid-State Lamp,” Amendment filed Jul. 20, 2015, for U.S. Appl. No. 13/875,130, 15 pages. |
| Reed et al., “Remotely Adjustable Solid-State Lamp,” U.S. Appl. No. 61/641,781, filed May 2, 2012, 65 pages. |
| Reed et al., “Turbulent Flow Cooling for Electronic Ballast,” U.S. Appl. No. 61/088,651, filed Aug. 13, 2008, 23 pages. |
| Reed, “Adjustable Output Solid-State Lighting Device,” U.S. Appl. No. 61/567,308, filed Dec. 6, 2011, 49 pages. |
| Reed, “Ambient Light Control in Solid State Lamps and Luminaires,” U.S. Appl. No. 61/933,733, filed Jan. 30, 2014, 8 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” Amendment filed Jan. 2, 2014, for U.S. Appl. No. 13/085,301, 26 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination Using Received Signals,” Amendment filed Jul. 23, 2014, for U.S. Appl. No. 13/085,301, 12 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” Amendment filed Apr. 2, 2013, for U.S. Appl. No. 12/784,093, 13 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” Amendment filed Apr. 4, 2013, for U.S. Appl. No. 12/784,091, 15 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” Amendment filed May 14, 2013, for U.S. Appl. No. 12/784,091, 9 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” Amendment filed Sep. 30, 2014, for U.S. Appl. No. 14/329,508, 18 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 61/346,263, filed May 19, 2010, 67 pages. |
| Reed, “Apparatus and Method of Energy Efficient Illumination,” U.S. Appl. No. 61/333,983, filed May 12, 2010, 57 pages. |
| Reed, “Asset Management System for Outdoor Luminaires,” U.S. Appl. No. 14/869,501, filed Sep. 29, 2015, 57 pages. |
| Reed, “Asset Management System for Outdoor Luminaires,” U.S. Appl. No. 62/082,463, filed Nov. 20, 2014, 56 pages. |
| Reed, “Centralized Control Area Lighting Hours of Illumination,” U.S. Appl. No. 62/057,419, filed Sep. 30, 2014, 39 pages. |
| Reed, “Centralized Control of Area Lighting Hours of Illumination,” Office Action dated Mar. 24, 2016 for U.S. Appl. No. 14/869,511, 31 pages. |
| Reed, “Detection and Correction of Faulty Photo Controls in Outdoor Luminaires,” Notice of Allowance dated May 19, 2016 for U.S. Appl. No. 14/869,492, 9 pages. |
| Reed, “Detection and Correction of Faulty Photo Controls in Outdoor Luminaires,” U.S. Appl. No. 14/869,492, filed Sep. 29, 2015, 71 pages. |
| Reed, “Detection and Correction of Faulty Photo Controls in Outdoor Luminaires,” U.S. Appl. No. 62/068,517, filed Oct. 24, 2014, 47 pages. |
| Reed, “Detection and Correction of Faulty Photo Controls in Outdoor Luminaires,” U.S. Appl. No. 62/183,505, filed Jun. 23, 2015, 71 pages. |
| Reed, “Electronic Control to Regulate Power for Solid-State Lighting and Methods Thereof,” U.S. Appl. No. 61/115,438, filed Nov. 17, 2008, 51 pages. |
| Reed, “Electronic Control to Regulate Power for Solid-State Lighting and Methods Thereof,” U.S. Appl. No. 61/154,619, filed Feb. 23, 2009, 62 pages. |
| Reed, “Electrostatic Discharge Protection for Luminaire,” Amendment filed Jun. 17, 2013, for U.S. Appl. No. 13/212,074, 11 pages. |
| Reed, “High Efficiency Power Controller for Luminaire,” U.S. Appl. No. 61/905,699, filed Nov. 18, 2013, 5 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” Amendment filed Jul. 23, 2015, for U.S. Appl. No. 13/786,332, 17 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” Amendment filed Mar. 13, 2015, for U.S. Appl. No. 13/786,332, 23 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” Notice of Allowance dated Aug. 6, 2015, for U.S. Appl. No. 13/786,332, 8 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” Notice of Allowance dated May 4, 2016, for U.S. Appl. No. 14/950,823, 10 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” Office Action dated May 29, 2015, for U.S. Appl. No. 13/786,332, 7 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” U.S. Appl. No. 14/950,823, filed Nov. 24, 2015, 72 pages. |
| Reed, “Luminaire With Ambient Sensing and Autonomous Control Capabilities,” U.S. Appl. No. 61/728,150, filed Nov. 19, 2012, 83 pages. |
| Reed, “Luminaire With Atmospheric Electrical Activity Detection and Visual Alert Capabilities,” U.S. Appl. No. 61/649,159, filed Aug. 28, 2012, 52 pages. |
| Reed, “Luminaire With Switch-Mode Converter Power Monitoring,” U.S. Appl. No. 61/723,675, filed Nov. 7, 2012, 73 pages. |
| Reed, “Photocontrol for Luminaire Consumes Very Low Power,” U.S. Appl. No. 61/849,841, filed Jul. 24, 2013, 41 pages. |
| Reed, “Resonant Network for Reduction of Flicker Perception in Solid State Lighting Systems,” U.S. Appl. No. 61/527,029, filed Aug. 24, 2011, 41 pages. |
| Reed, “Solid State Hospitality Lamp,” U.S. Appl. No. 61/692,619, filed Aug. 23, 2012, 32 pages. |
| Reed, “Solid State Lighting, Drive Circuit and Method of Driving Same,” U.S. Appl. No. 61/640,963, filed May 1, 2012, 24 pages. |
| Reed, “Systems, Methods, and Apparatuses for Using a High Current Switching Device as a Logic Level Sensor,” U.S. Appl. No. 61/764,395, filed Feb. 13, 2013, 48 pages. |
| Reed, “Luminaire With Adjustable Illumination Pattern,” U.S. Appl. No. 62/114,826, filed Feb. 11, 2015, 68 pages. |
| Renesas Electronics, “Zener Diodes for Surge Absorption—Applications of high-intensity LED,” Apr. 2010, 1 page. |
| Renn et al., “Solid State Lighting Device and Method Employing Heat Exchanger Thermally Coupled Circuit Board,” U.S. Appl. No. 61/357,421, filed Jun. 22, 2010, 49 pages. |
| Tyco Electronics, “Circuit Protection,” retrieved Jun. 10, 2011, retrieved from http://www.tycoelectronics.com/en/products/circuit-protection.html, 2 pages. |
| Vendetti et al., “Systems and Methods for Controlling Luminaire Wireless Network Using Smart Appliance,” U.S. Appl. No. 62/458,970, filed Feb. 14, 2017, 50 pages. |
| Vendetti et al., “Systems and Methods for Controlling Outdoor Luminaire Wireless Network Using Smart Appliance,” U.S. Appl. No. 15/895,439, filed Feb. 13, 2018, 50 pages. |
| Written Opinion dated Nov. 11, 2014, for International Application No. PCT/US2014/047867, 5 pages. |
| Written Opinion, dated Dec. 13, 2010 for PCT/US2010/035649, 4 pages. |
| Written Opinion, dated Dec. 15, 2010 for PCT/US2010/035658, 3 pages. |
| Written Opinion, dated Dec. 28, 2010 for PCT/US2010/035651, 3 pages. |
| Written Opinion, dated Dec. 30, 2013 for PCT/US2013/058266, 8 pages. |
| Written Opinion, dated Feb. 26, 2014, for PCT/US2013/070794, 10 pages. |
| Written Opinion, dated Feb. 27, 2013, for PCT/US2012/065476, 8 pages. |
| Written Opinion, dated Jan. 14, 2013, for PCT/US2012/052009, 5 pages. |
| Written Opinion, dated Jul. 9, 2009 for PCT/US2009/043171, 8 pages. |
| Written Opinion, dated Jun. 21, 2010 for PCT/US2009/064625, 5 pages. |
| Written Opinion, dated Nov. 19, 2013 for PCT/US2013/052092, 7 pages. |
| Written Opinion, dated Oct. 8, 2012 for PCT/US2012/033059, 3 pages. |
| Written Opinion, dated Sep. 30, 2011, for PCT/US2011/021359, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210160994 A1 | May 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62480833 | Apr 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16791672 | Feb 2020 | US |
| Child | 17127483 | US | |
| Parent | 15943183 | Apr 2018 | US |
| Child | 16284869 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17127483 | Dec 2020 | US |
| Child | 17146011 | US | |
| Parent | 16440612 | Jun 2019 | US |
| Child | 16791672 | US | |
| Parent | 16284869 | Feb 2019 | US |
| Child | 16440612 | US |
