Patent Grant
7911359
The present invention generally relates to light system management. More particularly, it relates to controlling and managing outdoor lighting units using a light management system having networked intelligent luminaire managers, and applications thereof.
It is estimated that there are more than 60 million outdoor lights in the United States autonomously controlled by conventional photo-controls. These outdoor lights, when properly working, simply react to ambient light conditions, for example, to turn-on at dusk and turn-off at dawn. This method of operating outdoor lights results in many lights being on when they are not needed, and it significantly increases outdoor lighting system operating costs.
The use of conventional photo-controls to control outdoor lights (luminaires) also leads to maintenance and repair issues. There are significant costs associated with hiring qualified maintenance personnel and buying equipment such as, for example, special maintenance vehicles required to access light fixtures for replacing lamps and servicing electrical components. To discover faulty fixture operations, light system owners and operators must resort to sending maintenance personnel to do “drive-by” visual examination of all units, which often number in the thousands or wait for a customer to report a malfunction. This drive-by must be done at night to detect non-functioning fixtures. These high costs limit how many lights can be repaired or serviced on any given day and force many light system operators to maintain their outdoor lights on an as needed basis (i.e., only when they are notified of an inoperable light). Understandably, this maintenance methodology is highly inefficient because it ties up resources as crews and equipment randomly travel to failed, geographically dispersed outdoor lights.
Lighting system operators (e.g., electric utilities) have tried to limit the time, equipment, and personnel spent on any given outdoor light by conducting group maintenance programs, where lights within a given geographical area are maintained on a scheduled basis. This approach reduces travel time between lights. In order to implement this maintenance methodology, light system operators must estimate lighting equipment life expectancy and schedule maintenance in each geographical area when lighting outages in the area are expected to reach a predetermined level. While this methodology has certain benefits, maintenance crews often replace good equipment that has significant additional life remaining. Consequently, this maintenance methodology results in maintenance crews throwing away good equipment and visiting outdoor lights that do not require maintenance. Locating light fixtures with failed lamps is a problem since roadway fixtures are only on at night and most maintenance crews work during the day.
What is needed is a new light management system that overcomes the deficiencies noted above.
The present invention provides a light management system having networked intelligent luminaire managers, and applications thereof. In an embodiment, a plurality of networked luminaire managers, each collocated with a respective luminaire, monitor the status of their respective luminaires. Each luminaire manager includes a transmitter for transmitting status information about its respective luminaire, such as for example a lamp out condition upon occurrence of such a lamp out condition, and third-party devices to a network server. The network server forwards the received status information from the networked luminaire managers to a computer of a light system owner/operator and/or a third-party user computer. The luminaire managers communicate with each other, whereby they form a network.
Features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with reference to the accompanying drawings.
The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable persons skilled in the pertinent arts to make and use the invention.
In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left-most digit of the reference number indicates a drawing in which the reference number first appears.
The present invention provides a light management system having networked, intelligent luminaire managers, and applications thereof. In the detailed description of the invention that follows, references to “one embodiment”, “an embodiment”, “an example embodiment”, etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Each of the networks 102a and 102b includes several intelligent luminaire managers (ILMs) 112 and a master control 114. The intelligent luminaire managers 112 communicate with each other and with master controller 114 using, for example, short-range radio frequency (RF) communication links. In an embodiment, these RF communication links operate in the 900 MHz unlicensed band and have a range of about 1000 feet. As described further below with reference to
Networks 102a and 102b in
In preferred embodiments of the present invention, networks 102 are peer-to-peer networks and/or mesh networks. These networks support three levels of devices: master controllers 114; network routing devices, for example, intelligent luminaire manager 112; and other nodes such as RF device 202 (see
Each of the network links between intelligent luminaire managers 112 includes a two-way communication channel. These two-way communication channels between intelligent luminaire managers 112 support, for example, over the air or power-line carrier re-keying and re-programming of these intelligent control device. This allows for on-demand, turn-on and turn-off, for example, of selected street lights coupled to intelligent luminaire managers 112.
In an embodiment, each intelligent luminaire manager 112 maintains an internal clock which is synchronized throughout the entire network. The clock may be local to the device or maintained at a selected location and transmitted to each luminaire manager 112. This permits accurate date/time stamps to be added to data sent to network operations center 106 and for time-based control of intelligent luminaire managers 112.
In embodiments of the present invention, intelligent luminaire managers 112 support commands sent from master controller 114 to alternate routing paths. Additionally, intelligent luminaire managers 112 will automatically attempt to reconnect to network 102 if a signal is lost for more than a selected period of time (e.g., after 15 minutes, after 30 minutes, after 60 minutes, etc.). Each intelligent luminaire manager 112 is capable of rerouting data through an alternative path, should one or more of the intelligent luminaire managers 112 fail. When a failed or new intelligent network controller 112 reenters network 102, other devices within the network pass on the activation or installation of the new intelligent luminaire manager to other network routing devices.
Additional details about the operation of intelligent luminaire managers 112 are described below.
Master controllers 114a and 114b serve as gateways between their associated intelligent luminaire managers 112 and network operation center 106. Each master controller 114 is coupled to network operation center 106 through a communication backbone channel 104. In embodiments, communication backbone channels 104 can be, for example, electrical and/or optical land line communication channels, satellite communication channels, paging network channels, power line carrier channels, RF links and/or cellular communication channels. These communication channels can include public and/or private communication means (e.g., utility owned lines and/or the Internet).
In one embodiment, network operation center 106 couples to master controllers 114 via an internet protocol infrastructure provided by third party carrier network services. Master controllers 114 preferably provide data concentration and compression, and thereby reduce the overall service fees for third party leasing arrangements of communication services. Master controllers 114 also preferably include a data storage capability so that data to and from intelligent luminaire managers 112 can be stored during network communication disruptions and transmitted after communications are restored.
In an embodiment, each master controller 114 connects with network operation center 106 at predetermined times and uploads the current status of all intelligent luminaire managers 112 within its area of responsibility and any devices that have entered network 102 since its last update to network operations center 106. For high-priority communications, such as, for example, detection of a failed lamp, master controller 114 may make unscheduled communications to network operation center 106.
Preferably, each master controller 114 is responsible for linking several intelligent luminaire managers 112 to network operation center 106. For example, in one embodiment, more than 500 intelligent luminaire managers may be linked by a single master controller 114 to network operation center 106. It is a feature of each master controller 114 that it can be programmed from network operation center 106.
In certain embodiments, master controller 114 is capable of inheriting the features of network 102 routing devices, such as intelligent luminaire manager 112, for communications within network 102. Master controller 114 also can implement, for example, a TCP/IP stack for communications over communication backbone channel 104 with network operation center 106. Master controller 114 preferably includes memory such as card slot non-volatile storage or compact flash memory and caches data representing the status of all intelligent luminaire managers 112 for which it is responsible.
As described in more detail below, in embodiments, master controller 114 provides authentication and authorization to radio frequency devices wanting to enter network 102. Master controller 114 communications with intelligent luminaire managers 112 and optimizes routing within its network cluster. Master controller 114 also preferably includes a backup energy source sufficient to power master controller 114, for example, for up to 24 hours of operation.
Network operation center 106 provides a variety of services for light system owner/operators 108. These services include, for example, 24-hour-a-day, seven-day-a-week data storage and forwarding services for data flowing between light system owner/operators 108 and their respective intelligent luminaire managers 112. Network operation center 106 is preferably responsible for configuring, monitoring, and operating the router switches and other communication equipment that comprise the data network illustrated by
As illustrated in
In operation, system 100 performs as illustrated by the following example cycle of events. An owner/operator 108 of an outdoor light system wishes to reduce operation and maintenance costs associated with his or her light system. The owner/operator 108 therefore has maintenance personnel 120 install and activate intelligent luminaire managers 112 according to the present invention on each of the lights of the light system, for example, as the conventional photo-controls are replaced due to failures. A master controller 114 is also installed in the vicinity of one of the intelligent luminaire managers (e.g., on a nearby pole or building rooftop).
During the installation and activation of each intelligent luminaire manager, selected information such as the intelligent luminaire manager's identification number, GPS grid coordinates for the location of the installation, the type of light equipment being controlled, a digital photo of the installation, and/or initial equipment parameters is collected by maintenance personnel 120 with the aid of the PDA hosted field unit 122. This information is then stored in the owner/operator's maintenance system records. In embodiments, the PDA hosted field unit 122 can communicate with intelligent luminaire managers 112 as well as master controllers 114 to receive information and/or upload information.
Using the services of network operation center 106 and a computer connected to network operation system 106 (e.g., via a secure Internet link), owner/operator 108 is able to monitor and control his or her lights. For example, if a light fails or is determined to be degraded, the intelligent luminaire manager 112 coupled to the light sends an alarm to owner/operator 108, indicating that a failure has occurred or is likely to occur, via the network and network operation center 106. This alarm notifies light system owner/operator 108 of the changed light system status and allows owner/operator 108 to take appropriate action.
In one embodiment, the alarm interacts automatically with the owner/operator's maintenance program and generates a work order that tells maintenance personnel 120 what actions are needed. The work order might include, for example, the time of the alarm, the location of the degraded or failed equipment, and what equipment or parts are needed to correct the problem that caused the alarm. This work order is down-loaded into the PDA-hosted intelligent luminaire manager field unit and used to guide maintenance personnel 120 to the site of the degraded or failed equipment. Once the repairs to the light are made, intelligent luminaire manager 112 updates the status for the light and the alarm is cleared. In an alternative embodiment, the alarm is cleared only when owner/operator 108 updates his or her maintenance records, for example, using data collected by the intelligent luminaire manager field unit 122 while the repair was being performed. In another embodiment, failure is only reported to owner/operator 108 when the failure has occurred a specified number of days in a row.
Once owner/operator 108 has installed intelligent luminaire managers on his or her lights, owner operator 108 can control when the lights are turned-on and turned-off. This is achieved by sending commands over the data network to individual or assignable groups of intelligent luminaire managers 112 and/or reprogramming a control program stored in a memory of each intelligent luminaire manager or group of assignable intelligent luminaire managers. More details regarding the functionality of intelligent luminaire managers 112 is provided below.
Also shown in
As shown in
In one embodiment, RF device 202 may become a part of a network by transmitting a signal that is received by a communications unit inside intelligent luminaire manager 112. Intelligent luminaire manager 112 then reports the presence of RF device 202 to network operation center 106, via the network and a master control 114. RF device 202 may be allowed to simply transmit data over the network, or it may be allowed to transmit and receive data. This communication can be either open or encrypted. Intelligent luminaire manager 112 is able to block communications from RF device 202 if RF device 202 is assessed to be functioning improperly or if the RF device's access is denied based on a blacklist maintained by the network operations center or if the RF device is interfering with the routing of higher priority traffic.
In embodiments of the present invention, RF device 202 is referred to as a blind slave. A blind slave is a device controlled by intelligent luminaire manager 112. One example use of a blind slave is to control the operation of an outdoor light (e.g., a house porch light or a driveway light). The blind slave coupled to the light receives commands from a nearby intelligent luminaire manager 112 to turn-on and turn-off the light, for example, in conjunction with the luminaire controlled by the intelligent luminaire manager 112. In one embodiment, blind slaves may be controlled by a utility in order to limit power usage during periods of high power demand and thereby prevent brown-outs or black-outs from occurring. The use of blind slaves is not limited to just photo control.
In embodiments of the present invention, the communication links between intelligent luminaire managers 112 can include, for example, power line carrier communication links or optical communication links. Thus, the present invention is not limited to using only RF communication links.
As described further below with reference to
As will be understood by persons skilled in the relevant arts, the potential for communicating with radio frequency (RF) or radio frequency identification (RFID) type devices using the network formed by intelligent luminaire managers 112 is nearly boundless and limited only by the bandwidth available. For example, an RF device 202 might be included in a car and used to monitor and locate stolen cars as they pass by or park near streetlights 200. An auto insurance company can pay a light system owner/operator to monitor for and report the location of stolen cars using his or her network. In this example, an RF device 202 might be configured to start transmitting a stolen car signal, for example, whenever the car's engine was started without using the car's ignition key. This stolen car signal would be detected by an intelligent luminaire manager 112 and reported via the network to an appropriate individual (e.g., a third party user 110 such as an insurance company representative and/or a local law enforcement official).
A similar use to that described above of the network capabilities of intelligent luminaire managers 112 would be to identify and locate an individual under house arrest, wearing an ankle bracelet, who has left his or her house. Other possible uses include, but are not limited to: providing security monitoring to determine if a nearby gate is open or closed or whether a particular system is on or off; to provide an interface to General Motor's ON-STAR system; to provide gun shot detection; to provide auto traffic and pedestrian monitoring; to provide public address audio communications and broadcast warning information (e.g., radiation alerts, bio alerts, chemical alerts, smog alerts, etc.); to provide high crime area surveillance; to locate lost individuals, children and pets; to relay weather monitoring data, power monitoring data, etc.; to repeat cellular communications, WiFi communications, or Internet communications; and to read and/or relay electric meter data, gas meter data, and/or water meter data for public utilities. Still other uses will become apparent to those skilled in the relevant arts given the description herein.
In an embodiment, intelligent luminaire manager 112 includes at least one LED (not shown) internal or external to enclosure 301 for communicating with maintenance crews. In one embodiment, the LED transmits infrared signals that are received by PDA hosted field unit 122. In another embodiment, the LED flashes a visual code that can be seen and interpreted by the maintenance crew. For example, when an intelligent luminaire manager is initially installed, it sends a message to a nearby intelligent luminaire manager 112 and receives back an acknowledgement signal. When this acknowledgment signal is received by the newly installed intelligent luminaire manager 112, its LED sends or flashes a code to let the maintenance crew know that the signal has been sent and an acknowledgement signal received. This lets the maintenance crew know that the intelligent luminaire manager 112 is working properly. In an embodiment, an LED signal may be different colors to indicate different status.
As noted above, enclosure 301 preferably conforms to appropriate NEMA and ANSI standards so that is can be installed on an intended light fixture without requiring a new mount and without requiring any rewiring or physical modification of the fixture. In embodiments, enclosure 301 is formed from a highly durable material, such as plastic, that is appropriate for outdoor use and that will withstand the expected weather and temperatures variations at the intended location of installation. Enclosure 301 also can be coated with a weather-resistant material.
In an embodiment, each luminaire manager 112 or enclosure 301 has a scannable barcode securely attached for purposes of identification. An identification code can also be stored in a memory of each luminaire manager 112. In an embodiment, PDA hosted field unit 122 is used to read and/or write the identification code to the memory of each luminaire manager 112.
In an embodiment, luminaire 200 is a conventional luminaire such as, for example, a street light. The purpose and function of ballast 302, starter 306, and lamp 308 are well-known to persons skilled in the relevant art.
Controller 310 includes a processor 318, memory 320, and an interface subsystem 322. Memory 320 stores a variety of programs that are executed and/or implemented using processor 318. These programs include, for example, a luminaire control program 324, luminaire and intelligent luminaire manager configuration program 326, status reporting program 328, and other optional programs 330.
As will become apparent to persons skilled in the relevant arts given the description herein, intelligent luminaire manager 112 is a novel and enhanced networking device that includes and improves upon the functionality and capabilities of the luminaire diagnostic system(s) described in U.S. Pat. Nos. 6,028,396, 6,452,339, and 6,841,944, each of which is incorporated herein by reference in its entirety. These improvements are described below.
One notable improvement is added functionality that allows intelligent luminaire manager 112 to be used to turn-on and turn-off lamp 308 on demand. Commands to turn-on and turn-off lamp 308 can be delivered to intelligent luminaire manager 112 via the data network illustrated in
The above described programmable commands to turn-on and turn-off lamp 308 are illustrative only and not intended to limit the present invention. Other programmable commands that can be used will become apparent to persons skilled in the relevant arts given the description herein. For example, commands can be programmed to turn lamp 308 on only during certain days of the week, to turn-on and turn-off lamp 308 at different times during different days in a given week, or all lamps in a group can be turned-on at a specified time and turned-off, for example, at dawn. In one embodiment, selected lamps can be sent a command to turned-off during periods of high power demand. Likewise, turn-on and turn-off times can be programmed to meet state or local light trespass codes, and these can be re-programmed remotely if the light trespass codes change.
In one embodiment, in the event an intelligent luminaire manager 112 loses contact with network operations center 106 or master controller 114, due for example to a network failure, intelligent luminaire manager 112 will revert to a pre-stored program for controlling luminaire 200. For example, this could be to turn on lamp 308 at dusk and to turn it off at dawn. Intelligent luminaire manager 112 can tolerate and continue operating through expected energy surges and sags without disruption of operation.
In an embodiment, an intelligent luminaire manager 112 uses luminaire condition sensing and diagnostic subsystem 312 to monitor A/C power provided to luminaire 200. For example, luminaire condition sensing and diagnostic subsystem 312 monitors voltage sags and over voltage and records the time, severity, and duration of these events, and reports these events to owner/operator 108. Additionally, in an embodiment, luminaire condition sensing and diagnostic subsystem 312 records the current provided to start lamp 308 and the current drawn by lamp 308 at some period after it is lit. Such data is useful, for example, for monitoring the proper operation of luminaire 200, and in particular ballast 302.
In one example embodiment, intelligent luminaire manager 112 monitors cycling of luminaire 200. It records, for example, fixture current after lamp 308 starts. If the fixture current increases or decreases more than a specified amount in a given time interval, this denotes one cycle. Cycle detections are reported to the master controller 114, via network messages, and forwarded to owner/operator 108. In one embodiment, an occurrence of multiple cycles such as, for example, about five in a given night may be reported as a defective lamp.
In an embodiment, intelligent network luminaire manager 112 generates a faulty lamp signal/alarm in the following manner. First, it measures lamp 308 power or volt amperes at two seconds after start, 15 seconds after start, one minute after start, and 8.5 minutes after start. If all four measurements are the same within, for example, about 10%, lamp 308 is flagged as faulty. Accordingly, a faulty lamp detection signal/alarm is stored and relayed to network operation center 106 and owner/operator 108.
As noted herein, values such as the 10% tolerance for current comparisons are reprogrammable. However, loss of network connectivity, for example, for more than a selected period of time causes intelligent luminaire manager 112 to revert programmable time measurement intervals and tolerances to default values stored within intelligent luminaire manager 112 memory.
Intelligent luminaire manager 112 is preferably capable of measuring true AC currents and voltages in addition to average currents and voltages. In embodiments, intelligent luminaire manager 112 determines and records the power consumption of an attached device as well as power factor and load.
As described above, status data collected by intelligent luminaire managers 112 is communicated via network 102 to master controller 114 and then to network operation center 106. At network operation center 106, the status data is analyzed for alarms and alerts, sorted, stored, and routed to an appropriate owner/operator 108.
Additional features and functionality of intelligent luminaire manager 112 are described below.
As shown in
In step 361, the input AC voltage (VAC) provided to a luminaire is measured. In an embodiment, the input AC voltage is preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The frequency (ω) of the input AC voltage can be determined, for example, by identifying how many voltage waveform zero-crossings occur in a selected time interval.
In step 362, the input AC current (IAC) provided to the luminaire is measured. In an embodiment, the input AC current is also preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The phase angle (θ) between the measured AC current and the AC voltage measured in step 361 can be determined, for example, by determining a time difference between the current waveform zero-crossing and the voltage waveform zero-crossing.
In step 363, a ratio between real power and apparent power is calculated (e.g., real power divided by apparent power). Both real power and apparent power are determined based on the AC voltage measurements from step 361 and the AC current measurements from step 362. Example ratios of real power divided by apparent power range from about 1 to about less than 0.1. For example, a properly working, non-power-factor-corrected luminaire having a reactor ballast and a 100 watt high pressure sodium lamp has a real power of about 120 watts and an apparent power of about 200 VA. This results in a ratio of 120/200 or 0.6. A power-factor-corrected luminaire having a reactor ballast and a 100 watt high pressure sodium lamp has a real power of about 120 watts and an apparent power of about 120 VA. This results in a ratio of 120/120 or 1.
In step 364, a determination is made whether the AC current is greater than or equal to a first threshold value. This check is performed, for example, to make sure the lamp is lit. In an embodiment, the first threshold value is about one amp. Other values can also be used. If the AC current is greater than or equal to a first threshold value, control passes to step 365. Otherwise, control passes to step 366.
In step 365, a determination is made whether the ratio of real power to apparent power calculated in step 363 is less than or equal to a second threshold value. The second threshold value can be selected, for example, based on the particular luminaire (e.g., fixture type and lamp type) to be monitored, or it can be a more general value that is selected to work with multiple luminaires (e.g., various combinations of fixture types and lamp types). For example, a value of 0.4 could be selected to monitor both a non-power-factor-corrected luminaire having a reactor ballast and a 100 watt high pressure sodium lamp and a power-factor-corrected luminaire having a reactor ballast and a 100 watt high pressure sodium lamp. If the ratio calculated in step 363 is less than the second threshold value, control passes to step 367 (Lamp Cycling). Otherwise, control passes to step 366.
Persons skilled in the relevant arts will know how to select a second threshold value given the description herein. It is a feature of method 360 that in step 365 cycling can be detected for a wide variation of luminaires (e.g., luminaires having lamps with an operating power of about 70 watts to about 1000 watts).
In step 366, a determination is made whether there has been a change in the AC current that is greater than or equal to a third threshold value. For example, in one embodiment, a determination is made after lamp startup whether the current measured in step 362 has increased or decreased more than about 25% in a one second interval. If there has been a 25% change in current, the lamp is identified as cycling unless, for example, there was an interruption in AC power. Other threshold values can be used, and persons skilled in the relevant arts will know how to select a third threshold value given the description herein. This test works well, for example, with luminaires having lamps with an operating power of about 70 watts to about 400 watts. If the change in AC current is greater than or equal to the third threshold value, control passes to step 367 (Lamp Cycling). Otherwise, control passes to step 361.
In step 367, a signal is generated to indicate that the lamp has cycled. In certain applications, a counter may be used to keep track of how many times a lamp has cycled, for example, during a single night. Once a predetermined number of cycles have occurred, power to the lamp may be switched off to prevent damage of the luminaire.
As will be understood by persons skilled in the relevant art, method 360 can be modified, for example, to delete one of the two depicted cycling tests or to add additional cycling tests.
In step 371, the input AC voltage (VAC) provided to a luminaire is measured. In an embodiment, the input AC voltage is preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The frequency (ω) of the input AC voltage can be determined, for example, by identifying how many voltage waveform zero-crossings occur in a selected time interval.
In step 372, the input AC current (IAC) provided to the luminaire is measured. In an embodiment, the input AC current is also preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The phase angle (θ) between the measured AC current and the AC voltage measured in step 371 can be determined, for example, by determining a time difference between the current waveform zero-crossing and the voltage waveform zero-crossing.
In step 373, real power being consumed is calculated. Real power is determined based on the AC voltage measurements from step 371 and the AC current measurements from step 372. In an embodiment, real power is calculated, for example, at times 0 seconds, 10 seconds, 60 seconds, and 600 seconds after an attempt to start the lamp. Other times can also be used.
In step 374, a determination is made whether real power is changing during an expected startup time of the lamp. If no change in real power is detected, control passes to step 375 (Bad Lamp). Otherwise, control passes to step 371.
In step 375, a signal is generated to indicate that the lamp is bad.
In step 381, the input AC voltage (VAC) provided to a luminaire is measured. In an embodiment, the input AC voltage is preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The frequency (ω) of the input AC voltage can be determined, for example, by identifying how many voltage waveform zero-crossings occur in a selected time interval.
In step 382, the input AC current (IAC) provided to the luminaire is measured. In an embodiment, the input AC current is also preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The phase angle (θ) between the measured AC current and the AC voltage measured in step 381 can be determined, for example, by determining a time difference between the current waveform zero-crossing and the voltage waveform zero-crossing.
In step 383, real power being consumed is calculated. Real power is determined based on the AC voltage measurements from step 381 and the AC current measurements from step 382.
In step 384, a determination is made whether the AC current is less than or equal to a first threshold value. In one embodiment, a threshold value of about 0.2 amps is used. Other values can also be used. If the AC current is less than or equal to the first threshold value, control passes to step 386. Otherwise, control passes to step 385. In an embodiment, a current of less than about 0.2 amps indicates, for example, either a bad fixture, ballast or a bad starter.
In step 385, a determination is made whether the real power is less than or equal to a second threshold value. In one embodiment, a threshold value of about 40 watts is used. Other values can also be used. If the real power is less than or equal to the second threshold value, control passes to step 386. Otherwise, control passes to step 381. In an embodiment, a power of less than 40 watts is an indication, for example, of an open ballast, a bad starter, an open lamp, or a broken wire.
In step 386, a signal is generated to indicate that the fixture is bad.
In step 391, the input AC voltage (VAC) provided to a luminaire is measured. In an embodiment, the input AC voltage is preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The frequency (ω) of the input AC voltage can be determined, for example, by identifying how many voltage waveform zero-crossings occur in a selected time interval.
In step 392, the input AC current (IAC) provided to the luminaire is measured. In an embodiment, the input AC current is also preferably measured at a plurality of times (Ti). The time intervals between measurements can be constant or variable. The phase angle (θ) between the measured AC current and the AC voltage measured in step 391 can be determined, for example, by determining a time difference between the current waveform zero-crossing and the voltage waveform zero-crossing.
In step 393, real power being consumed is calculated. Real power is determined based on the AC voltage measurements from step 391 and the AC current measurements from step 392.
In step 394, a determination is made whether real power is changing after time T1. In an embodiment, T1 is about 2 minutes. This value is based on curve A1 in
In step 395, a determination is made whether real power is changing after time T2. In an embodiment, T2 is about 6 minutes. This value is based on curve C1 in
In step 396, a determination is made whether real power is less than or equal to a threshold value after time T3. In an embodiment, the threshold value is about 50 watts and T3 is about 6 minutes. These value are based on curve B1 in
In step 397, a determination is made whether a DC component of voltage/current is greater than or equal to a selected percentage of the AC component of voltage/current. A relatively large DC component of voltage/current is an indication of rectification. Lamps usually cycle, however, before rectification problems occur. If the DC component of voltage/current is greater than or equal to a selected percentage of the AC component of voltage/current, control passes to step 398. Otherwise, control passes to step 391.
In step 398, a signal is generated to indicate the lamp is about to fail. This signal may also indicate that the wrong type lamp has been installed, if it occurs soon after lamp replacement. If the lamp has been installed and operating properly for a period of time, one can deduce that the correct lamp was initially installed and thus the installed lamp is one that is about to fail.
As will be understood by persons skilled in the relevant art, method 390 can be modified, for example, to delete one of the depicted predictive tests, such as the DC component test, or to add additional predictive tests.
Based on the description of the present invention contained herein, it will become apparent to persons skilled in the relevant arts that some or all of the functions and/or functionality described with regards to intelligent luminaire manager 112 herein can be implemented, for example, as an integral part of luminaire 200. Similarly, functions and/or functionality described with respect to luminaire 200 (e.g., starter 306) can be implemented as a part of intelligent luminaire manager 112. Thus, the illustration and description of specific functions and functionality residing in luminaire 200 and/or intelligent luminaire manager 112 is illustrative and not intended to limit the present invention.
As will become apparent from the description herein, network operation center 106 provides many services, such as, for example, main data network system operation and maintenance 408, subscriber/customer services 410, network security services 412, and subscriber/customer data interface services 414. As used herein, the term subscriber/customer refers to a light system owner/operator 108 and/or a third party user 110.
In one embodiment, network operation services provided by network operation center 106 personnel include six major components: subscriber provisioning, network provisioning, traffic engineering, billing, service assurance, and security management. Subscriber provisioning refers to subscriber management, subscriber selection, and subscriber activation. Network provisioning refers to capacity planning, network design, and device provisioning. Traffic engineering refers to network traffic analysis and policy management. Billing refers to, for example, both settlement of accounts between and amongst subscriber/customers, and usage data collection, rating, invoicing, and collection of bills. In an embodiment, network operations center 106 records customer information for each intelligent luminaire manager 112 that can be used by owner/operators 108 to support customer service queries and reports and billing of their respective customers. Service assurance refers to asset management, performance management, service-level management, fault management, trouble management, and work-force management. Security management refers to access fraud, service fraud, management access control, and denial of service. The goal of these network services is to provide a framework that provides scalability for a unified wide-area network platform that can be easily managed and controlled in real time, for example, over the internet using either standard web browsers or customer-specific applications developed within a software framework. Like the physical hardware of the network, the software is scalable.
Scalability of the system can be ensured by distributing the necessary software over multiple servers. In addition, this increases both redundancy and reliability. A communications software program maintained by network operation center 106 provides a virtual private network for each gateway to the network operation center (e.g., master controllers 114). Network operation center 106 is capable of supporting many thousands of concurrent subscribers. Notable features of network operation center 106 include its store and forward data management technology; its management environment that supports and controls a massive subscriber base of mobile computers, integrated servers and web service users; its security and data independence that facilitates supporting large numbers of separate customers and their sensitive business data; and its ability to provide fast, secure, and highly-available synchronization between servers and the subscriber/customer populations they support.
In an embodiment, network operation center 106 is capable, for example, of being scaled to support up to about 120,000 master controllers or more and up to about 60 million intelligent luminaire manager nodes or more, which could handle traffic of about 1 megabyte of data per day per gateway or master controller 114.
In an embodiment, network operation center 106 records GPS coordinates for each node location (e.g., the locations of intelligent luminaire managers 112). This data is used to generate user display maps of node locations and to support workforce management reports that include node locations.
Network operation center 106, based on data collected, also is able to provide detailed information to its subscribers/customer regarding the type of fixture, lamp type, ballast type, and starter type operated by each intelligent luminaire manager 112. Additionally, network operation center 106 software is able to generate summary failure analysis reports, broken down by lighting system attributes such as, for example, fixture type, lamp type, ballast type, starter type, and hours of operation. This analysis is provided to specific customers and/or all customers, based on how often a component fails or requires a service call. The analysis preferably includes failure conditions identified by the network as well as information provided to call centers about the failures.
In an embodiment, a time stamp is provided with data packet transported via a network such that resolution about events on the network can be identified, for example, within one minute. If a luminaire 200 controlled by an intelligent luminaire manager 112 fails, it preferably takes about one minute in this embodiment before an alarm is generated at an associated owner/operator's site. This alarm preferably displays both the location of the failed luminaire and the time of failure.
As shown in
In an embodiment, when the alarm data is received at network operation center 106, it is compared to predetermined action stored in a program, and the actions are carried out as described. For example, the network operation center may send an email to certain individuals, a map showing the location of the failed device, and/or generate a work order by interfacing with a subscriber/customer's work-order program. The type of data sent from network operations center 106 to a subscriber/customer is not limited, but in practical terms may be limited in its usefulness to a subscriber/customer based on ability to receive and use the data.
In an embodiment, the message traffic passed between network operation center 106 and intelligent luminaire managers 112 includes applications data packages, query command packages, device status packages, event and alarm packages, and network status packages. Subscriber/customer access to this data stored at the network operation center is controlled by password. Subscriber/customer notification of events is transmitted to the subscriber/customer, and no password is required to obtain this data.
In an embodiment, network operation center 106 is able to identify when there is a power failure effecting a subscriber/customer's light system and when backup power is being used at master controls 114. For a system-wide power outage, network operation center 106 can consolidate alarm reports and generate a generalized message that is forwarded to an effected subscriber/customer (e.g., a light-system owner/operator 108).
As noted above, in the event of a power failure or a network failure such that a master controller 114 cannot provide data to network operation center 106 on a scheduled interval, the data is maintained at the master controller 114 until power and communications are restored. The stored data is then forwarded at the next scheduled reporting interval, unless specifically requested earlier by a subscriber/customer In an embodiment, master controller 114 includes battery back-up power. In another embodiment, master controller 114 is capable of transmitting an “I've Lost Power” signal when power is lost.
Network operation center 106 is responsible for IP protocol traffic analysis. Traffic is routed such that it is able to support peak loading of the data network and still pass data. In order to manage data, subscriber/customer commands may be limited during certain unexpected peak loads and held until bandwidth becomes available to forward this traffic. When a bandwidth limitation is being reached in a network 102, an alarm is sent to network operation center 106 so that traffic can be managed accordingly to control the peak load. Network operation center 106 personnel can monitor traffic loading on the network and install additional capacity as required.
In an embodiment, as noted above, network operation center personnel perform asset management functions, which include tracking the life cycle of node equipment, and replacing end-of-life equipment or degraded equipment before failure. For light system owner/operators 108, network operation center 106 data analysis programs can track the complete life of a device (e.g., the time it was installed, the number of hours it was operated, and a cause of failure).
Network security services 412 control access to the information stored by network operation center 106 using firewalls and prevent unauthorized access/network usage to prevent compromise of the data and/or network. In an embodiment, network security services 412 require both authentication and authorization. Security techniques are implemented to prevent denial-of-service attacks and virus attacks that would cause the networks to fail or breakdown. Network security services 412 also preferably include intrusion tracking and the ability to trace and combat malicious acts by unauthorized users. In an embodiment, a “call home” feature is used such that when a request for information or service is sent from a subscriber/customer to network operation center 106, the request is repeated and sent back to the subscriber/customer's known address by network operation center 106 to verify that the request actually came from that subscriber/customer. Network security services 412 also employ and support data encryption.
In an embodiment, network operation center 106 as a part of its subscriber/customer service provides monthly reports summarizing asset status of monitored devices to subscribers/customers. Additionally, in an embodiment, network operation center 106 sends messages to light system managers when a light is turned on and when it is turned off so that the light system manager can keep track of the present status of the light system assets.
Computer display 504 presents, in both a text and a graphical manner, information about the owner/operator's light system. The text and graphical information includes, for example, the status of any alarms, power usage, network status, and device status. The status is also shown graphically on a visual map display. In one embodiment, a graphical user interface presents a visual photometric mapping to a user, for example, of selected lights of the light system. This photometric mapping can provide the user with a visual representation of the illumination, for example, of a parking lot, a sports field, or other area of interest. The bottom portion of computer screen 504 shows commands being entered and responses being received from network operation center 106.
The light system manager preferably has the ability to run several programs at his or her site. These programs include alarm and maintenance (e.g., repair dispatch) program(s) 506, light system management program(s) 508, billing program(s) 510, data analysis program(s) 512, a data storage and retrieval program 514, a network operation center interface program 516, and a data routing program 518. Each of these programs is further described below.
Alarm and maintenance program(s) 506 displays an alarm such that maintenance personnel 120 can take corrective action. In an embodiment, the program uses data that has been analyzed, for example, by network operation center 106 and schedules maintenance so that equipment in the field close to the end of its useful operating life can be replaced prior to failure. For better predictability, this end of life analysis can be based on a larger population of equipment than only that owned and operated by a particular light system manager.
Light management program(s) 508 are used by the light system manager to reprogram devices in the field. Examples of this include, for example, turning lights on and lights off using a schedule rather than having them simply turn on at dusk and off at dawn.
Billing program(s) 510 keep track of when specific lights are used and generates customer bills accordingly. In one embodiment, the rate charged for turning on and using a particular light can be based on the time it is turned on (e.g., during peak hours of operation or off-peak hours of operation).
Data analysis program(s) 512 maintain the state of components in use in a light system and compare, for example, each component's total time in use to an estimated life expectancy to predict a remaining time to failure for the component. When a component is at its expected end of life, the data generated by program(s) 512 can be used to create a work order to have maintenance personnel 120 replace the component before it fails, for example, by interacting with a maintenance/work order program 520.
Data storage and retrieval program(s) 514 facilitate the storage and retrieval of data at the light manager's site in database 502.
Network operating system interface program 516 is used to interface with network operation center 106. This interface program is useful, for example, for transmitting data to and receiving data from intelligent luminaire managers 112 installed on the light system manager's equipment.
Data routing program 518 parses and routes data received from network operation center 106.
On the maintenance unit side, there is included a maintenance work order program 520, an intelligent luminaire manager field unit interface device 522, and an intelligent luminaire manager field unit 524. Also included are an inventory purchasing program 526 and an asset management program 528.
In an embodiment, when an alarm or maintenance requirement is sent to the light system manager by network operation center 106, it is automatically routed to maintenance/work order program 520. This program then automatically generates a work order that can be acted upon by a maintenance worker. An electronic copy of the work order can be downloaded to intelligent luminaire manager field unit 524 via intelligent luminaire manager field unit interface 522.
In an embodiment, intelligent luminaire manager field unit 524 is a hand-carried portable device that can be taken on-site while installing and/or servicing a luminaire 200. Information about the installation and/or service is captured by intelligent luminaire manager field unit 524 for subsequent entry into the records of the light system owner/operator 108. Upon return of the maintenance worker to the maintenance unit, the collected information is uploaded from the field unit into maintenance records. In an embodiment, this uploaded information is forwarded to network operation center 106 where it is stored and analyzed along with information gather by maintenance units of other light system owner/operators.
In an embodiment, alarms generated by an intelligent luminaire manager 112 are not cleared until replacement/service information is received at network operation center 106.
In an embodiment, inventory purchasing program 526 keeps track, for example, of stock on hand and causes equipment to be ordered and stocked based on information collected from intelligent luminaire managers 112.
The asset management program 528 is a program that modifies asset management data received, for example, from network operation center 106 to satisfy particular light system owner/operator data requirements.
Based on the description of the present invention contained herein, it will become apparent to persons skilled in the relevant arts that any or all of the functions and/or functionality described with regards to network operation center 106 can be implemented, for example, by a light system owner/operator 108. Similarly, any or all of the functions and/or functionality described with respect to a light system owner/operator can be implemented by network operation center 106. Thus, the illustration and description of specific functions and functionality residing at a particular location or with a particular entity is illustrative and not intended to limit the present invention.
In an embodiment, field unit 524 includes an on-board GPS system 534 and a communications interface 536. The communications interface can communicate, for example, with an intelligent luminaire manager or other device using RF and/or optical communications. Using the GPS 534, the field unit identifies the location where an intelligent luminaire manager 112 is installed. This information is stored, for example, in memory 320 of intelligent luminaire manager 112. It is also taken back to the maintenance unit and stored in the maintenance unit's records. Additionally, it is forwarded to network operation center 106 via the light manager's subscriber/customer interface to network operation center 106. Other information collected and forwarded to network operation center 106 includes, for example, all the particulars about the equipment monitored and controlled by the intelligent luminaire manager 112 (e.g., lamp type, ballast type, digital photo, etc.).
In embodiments of the present invention, for example where more than one intelligent luminaire manager 112 may be installed at the same geographical location (e.g., in a situation where two luminaires are attached to a single pole and each luminaire has its own intelligent luminaire manager 112), field unit 524 can be used to assign a unique identification value to each of the luminaire managers.
Once an intelligent luminaire manager 112 is installed, it self-configures by running a configuration program. Once alive, network 102 notifies network operation center 106, via master controller 114, that a new device has entered the network.
In an embodiment, field unit 524 is hosted by a PDA 530, running application program(s) 532. The present invention is not limited, however, to requiring the use of a PDA. Map base reports downloaded to field unit 524 show the location of each luminaire in a light system and display efficient driving routes for maintenance crews to get to a luminaire requiring repair. Fault types are communicated to crews via network operation center 106 and field unit 524 for pre-diagnostics of a failed luminaire so that time on-site is minimized and the need for return trips to a failed luminaire are eliminated. In an embodiment, the type of faults and corrective actions that can be provided to maintenance crew workers include anticipated lamp cycling, lamp cycling, no starting pulse, starting pulse but failed to start, non-reporting unit, replace lamp when traveling to area, replace lamp, replace starter, check power at fixture, if no power repair power, and if power replace intelligent luminaire manager unit. As will be understood by persons skilled in the relevant arts, this list is illustrative and not intended to limit the present invention.
It is a feature of the present invention that during activation of a new intelligent luminaire manager 112, each unit is identified both in terms of its type of luminaire and its GPS location. This data, coupled with the failure mode reporting, allows for a much greater maintenance crew efficiency. Additionally, dedicated, less-costly maintenance crews are able to conduct all maintenance during daylight hours, rather than nighttime, at significantly lower cost.
In an embodiment, when an intelligent luminaire manager 112 is removed from service, its identification number is captured by field unit 524. If the GPS coordinates of the removed intelligent luminaire manager 112 differ from what is expected (e.g., by more than a couple of meters) an alert/alarm is generated or initiated by field unit 524 and preferably provided to network operation center 106. The alarm is an indication, for example, that (1) the removed intelligent luminaire manager 112 was originally installed improperly (e.g., at the wrong location or with the wrong GPS coordinates); (2) the removed intelligent luminaire manager 112 has been moved since its activation without proper authority; or (3) the data stored by the removed intelligent luminaire manager 112 has been corrupted.
While the foregoing is a complete description of exemplary embodiments of the invention, it should be evident that various modifications, alternatives and equivalents may be made and used. For example, although the intelligent luminaire manager of the present invention is described as controlling luminaires having conventional lamps, it will be apparent to individuals skilled in the relevant arts given the description herein that the intelligent luminaire manager can be adapted to manage other types of lighting such as, for example, light emitting diodes. In addition, the intelligent luminaire manager of the present invention can also be adapted to manage other electromechanical devices. Thus, it is not limited to managing only luminaires. Accordingly, the above description should not be taken as limiting the scope of the invention.
This application claims the benefit of U.S. Provisional Patent Application No. 60/715,584, filed on Sep. 12, 2005, which is incorporated herein by reference in its entirety; and this application is related to the following commonly owned patent applications: (1) U.S. patent application Ser. No. 11/518,497, filed Sep. 11, 2006, entitled “Light Management System Having Networked Intelligent Luminaire Managers”, which issued as U.S. Pat. No. 7,603,184; (2) U.S. patent application Ser. No. 11/518,488, filed Sep. 11, 2006, entitled “Network Operation Center For A Light Management System Having Networked Intelligent Luminaire Managers”, which issued as U.S. Pat. No. 7,546,167; (3) U.S. patent application Ser. No. 11/518,494, filed Sep. 11, 2006, entitled “Owner/Operator Control Of A Light Management System Using Networked Intelligent Luminaire Managers”, which issued as U.S. Pat. No. 7,546,168; (4) U.S. patent application Ser. No. 12/028,597, filed Sep. 11, 2006, entitled “Light Management System Having Networked Intelligent Luminaire Managers With Enhanced Diagnostics Capabilities”, which issued as U.S. Pat. No. 7,761,260; and (5) U.S. patent application Ser. No. 11/518,511, filed Sep. 11, 2006, entitled “Activation Device For An Intelligent Luminaire Manager”, which issued as U.S. Pat. No. 7,529,594; each of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3149317 | Brugliera et al. | Sep 1964 | A |
| 3747104 | Pansini | Jul 1973 | A |
| 3873882 | Gershen | Mar 1975 | A |
| 4338562 | Terwilliger | Jul 1982 | A |
| 4575660 | Zaharchuk et al. | Mar 1986 | A |
| 4691341 | Knoble et al. | Sep 1987 | A |
| 4694223 | Campolo | Sep 1987 | A |
| 4727296 | Zaharchuk et al. | Feb 1988 | A |
| 4924151 | D'Aleo et al. | May 1990 | A |
| 4980806 | Taylor et al. | Dec 1990 | A |
| 4988920 | Hoeksma | Jan 1991 | A |
| 5019955 | Hoeksma | May 1991 | A |
| 5051727 | Fockens | Sep 1991 | A |
| 5095502 | Finzel | Mar 1992 | A |
| 5187655 | Post et al. | Feb 1993 | A |
| 5191265 | D'Aleo et al. | Mar 1993 | A |
| 5209560 | Taylor et al. | May 1993 | A |
| 5248919 | Hanna et al. | Sep 1993 | A |
| 5329431 | Taylor et al. | Jul 1994 | A |
| 5357170 | Luchaco et al. | Oct 1994 | A |
| 5383187 | Vardakas et al. | Jan 1995 | A |
| 5399940 | Hanna et al. | Mar 1995 | A |
| 5430356 | Ference et al. | Jul 1995 | A |
| 5452294 | Natarajan | Sep 1995 | A |
| 5463286 | D'Aleo et al. | Oct 1995 | A |
| 5473202 | Mudge et al. | Dec 1995 | A |
| 5479159 | Kelly et al. | Dec 1995 | A |
| 5487088 | Weltz et al. | Jan 1996 | A |
| 5498931 | Bedocs | Mar 1996 | A |
| 5506715 | Zhu | Apr 1996 | A |
| 5530322 | Ference et al. | Jun 1996 | A |
| 5565855 | Knibbe | Oct 1996 | A |
| 5623256 | Marcoux | Apr 1997 | A |
| 5637964 | Hakkarainen et al. | Jun 1997 | A |
| 5648656 | Begemann et al. | Jul 1997 | A |
| 5652751 | Sharony | Jul 1997 | A |
| 5654968 | Smiroldo | Aug 1997 | A |
| 5668446 | Baker | Sep 1997 | A |
| 5668537 | Chansky et al. | Sep 1997 | A |
| 5699243 | Eckel et al. | Dec 1997 | A |
| 5701117 | Platner et al. | Dec 1997 | A |
| 5721471 | Begemann et al. | Feb 1998 | A |
| 5726644 | Jednacz et al. | Mar 1998 | A |
| 5769527 | Taylor et al. | Jun 1998 | A |
| 5770928 | Chansky et al. | Jun 1998 | A |
| 5798581 | Keagy et al. | Aug 1998 | A |
| 5805593 | Busche | Sep 1998 | A |
| 5808417 | Ference et al. | Sep 1998 | A |
| 5811785 | Heiman et al. | Sep 1998 | A |
| 5811942 | Pedretti | Sep 1998 | A |
| 5812422 | Lyons | Sep 1998 | A |
| 5861717 | Begemann et al. | Jan 1999 | A |
| 5864184 | Platner et al. | Jan 1999 | A |
| 5874903 | Shuey et al. | Feb 1999 | A |
| 5884181 | Arnold et al. | Mar 1999 | A |
| 5886423 | Gershen et al. | Mar 1999 | A |
| 5898384 | Alt et al. | Apr 1999 | A |
| 5905442 | Mosebrook et al. | May 1999 | A |
| 5909087 | Bryde et al. | Jun 1999 | A |
| 5919239 | Fraker et al. | Jul 1999 | A |
| 5959275 | Hughes et al. | Sep 1999 | A |
| 5959549 | Synesiou et al. | Sep 1999 | A |
| 5962989 | Baker | Oct 1999 | A |
| 5962991 | Levy | Oct 1999 | A |
| 5962992 | Huang et al. | Oct 1999 | A |
| 5963546 | Shoji | Oct 1999 | A |
| 5971597 | Baldwin et al. | Oct 1999 | A |
| 5978364 | Melnik | Nov 1999 | A |
| 5986574 | Colton | Nov 1999 | A |
| 5990635 | Ference et al. | Nov 1999 | A |
| 6016038 | Mueller et al. | Jan 2000 | A |
| 6028396 | Morrissey, Jr. et al. | Feb 2000 | A |
| 6028853 | Haartsen | Feb 2000 | A |
| 6035266 | Williams et al. | Mar 2000 | A |
| 6037721 | Lansing et al. | Mar 2000 | A |
| 6044062 | Brownrigg et al. | Mar 2000 | A |
| 6046550 | Ference et al. | Apr 2000 | A |
| 6046992 | Meier et al. | Apr 2000 | A |
| 6078251 | Landt et al. | Jun 2000 | A |
| 6119076 | Williams et al. | Sep 2000 | A |
| 6124806 | Cunningham et al. | Sep 2000 | A |
| 6130881 | Stiller et al. | Oct 2000 | A |
| 6157943 | Meyer | Dec 2000 | A |
| 6160359 | Fleischmann | Dec 2000 | A |
| 6169377 | Bryde et al. | Jan 2001 | B1 |
| 6172468 | Holländer | Jan 2001 | B1 |
| 6174073 | Regan et al. | Jan 2001 | B1 |
| 6181086 | Katyl et al. | Jan 2001 | B1 |
| 6188181 | Sinha et al. | Feb 2001 | B1 |
| 6192053 | Angelico et al. | Feb 2001 | B1 |
| 6195018 | Ragle et al. | Feb 2001 | B1 |
| 6215398 | Platner et al. | Apr 2001 | B1 |
| 6239722 | Colton et al. | May 2001 | B1 |
| 6249516 | Brownrigg et al. | Jun 2001 | B1 |
| 6275707 | Reed et al. | Aug 2001 | B1 |
| 6285912 | Ellison et al. | Sep 2001 | B1 |
| 6300727 | Bryde et al. | Oct 2001 | B1 |
| 6301257 | Johnson et al. | Oct 2001 | B1 |
| 6304180 | Platner et al. | Oct 2001 | B1 |
| 6304556 | Haas | Oct 2001 | B1 |
| 6310440 | Lansing et al. | Oct 2001 | B1 |
| 6316889 | Chansky et al. | Nov 2001 | B1 |
| 6333605 | Grouev et al. | Dec 2001 | B1 |
| 6340864 | Wacyk | Jan 2002 | B1 |
| 6349091 | Li | Feb 2002 | B1 |
| 6369704 | Hilleary | Apr 2002 | B2 |
| 6370489 | Williams et al. | Apr 2002 | B1 |
| 6373399 | Johnson et al. | Apr 2002 | B1 |
| 6377001 | Levy | Apr 2002 | B2 |
| 6380696 | Sembhi et al. | Apr 2002 | B1 |
| 6388396 | Katyl et al. | May 2002 | B1 |
| 6388399 | Eckel et al. | May 2002 | B1 |
| 6392368 | Deller et al. | May 2002 | B1 |
| 6393381 | Williams et al. | May 2002 | B1 |
| 6396216 | Noone et al. | May 2002 | B1 |
| 6415245 | Williams et al. | Jul 2002 | B2 |
| 6424270 | Ali | Jul 2002 | B1 |
| 6437692 | Petite et al. | Aug 2002 | B1 |
| 6441565 | Levy | Aug 2002 | B1 |
| 6452339 | Morrissey et al. | Sep 2002 | B1 |
| 6453687 | Sharood et al. | Sep 2002 | B2 |
| 6456960 | Williams et al. | Sep 2002 | B1 |
| 6462654 | Sandelman et al. | Oct 2002 | B1 |
| 6496012 | Weng et al. | Dec 2002 | B1 |
| 6499114 | Almstead et al. | Dec 2002 | B1 |
| 6507158 | Wang | Jan 2003 | B1 |
| 6509828 | Bolavage et al. | Jan 2003 | B2 |
| 6509841 | Colton et al. | Jan 2003 | B1 |
| 6512455 | Finn et al. | Jan 2003 | B2 |
| 6528954 | Lys et al. | Mar 2003 | B1 |
| 6535498 | Larsson et al. | Mar 2003 | B1 |
| 6545434 | Sembhi et al. | Apr 2003 | B2 |
| 6548967 | Dowling et al. | Apr 2003 | B1 |
| 6552525 | Bessler | Apr 2003 | B2 |
| 6553020 | Hughes et al. | Apr 2003 | B1 |
| 6574227 | Rosenberg et al. | Jun 2003 | B1 |
| 6581837 | Hattersley | Jun 2003 | B1 |
| 6587046 | Joao | Jul 2003 | B2 |
| 6603276 | Chansky et al. | Aug 2003 | B2 |
| 6604062 | Williams et al. | Aug 2003 | B2 |
| 6608453 | Morgan et al. | Aug 2003 | B2 |
| 6614013 | Pitigoi-Aron et al. | Sep 2003 | B2 |
| 6617560 | Forke | Sep 2003 | B2 |
| 6633823 | Bartone et al. | Oct 2003 | B2 |
| 6636005 | Wacyk et al. | Oct 2003 | B2 |
| 6640087 | Reed et al. | Oct 2003 | B2 |
| 6640253 | Schaefer | Oct 2003 | B2 |
| 6667578 | Lansing et al. | Dec 2003 | B2 |
| 6704283 | Stiller et al. | Mar 2004 | B1 |
| 6714895 | Williams et al. | Mar 2004 | B2 |
| 6717376 | Lys et al. | Apr 2004 | B2 |
| 6717660 | Bernardo | Apr 2004 | B1 |
| 6724159 | Gutta et al. | Apr 2004 | B2 |
| 6731079 | Andersen | May 2004 | B2 |
| 6734642 | Reverberi | May 2004 | B1 |
| 6744740 | Chen | Jun 2004 | B2 |
| 6744766 | Alapuranen | Jun 2004 | B2 |
| 6744771 | Barber et al. | Jun 2004 | B1 |
| 6751455 | Acampora | Jun 2004 | B1 |
| 6754192 | Kennedy | Jun 2004 | B2 |
| 6757268 | Zendle | Jun 2004 | B1 |
| 6771666 | Barker, Jr. | Aug 2004 | B2 |
| 6774584 | Lys et al. | Aug 2004 | B2 |
| 6777891 | Lys et al. | Aug 2004 | B2 |
| 6781329 | Mueller et al. | Aug 2004 | B2 |
| 6794830 | Lansing et al. | Sep 2004 | B2 |
| 6803728 | Balasubramaniam et al. | Oct 2004 | B2 |
| 6806813 | Cheng et al. | Oct 2004 | B1 |
| 6807165 | Belcea | Oct 2004 | B2 |
| 6807516 | Williams et al. | Oct 2004 | B2 |
| 6808279 | Greiner | Oct 2004 | B2 |
| 6836737 | Petite et al. | Dec 2004 | B2 |
| 6841944 | Morrissey et al. | Jan 2005 | B2 |
| 6842668 | Carson et al. | Jan 2005 | B2 |
| 6845274 | Wang | Jan 2005 | B2 |
| 6850502 | Kagan et al. | Feb 2005 | B1 |
| 6859644 | Wang | Feb 2005 | B2 |
| 6867707 | Kelley et al. | Mar 2005 | B1 |
| 6869204 | Morgan et al. | Mar 2005 | B2 |
| 6870846 | Cain | Mar 2005 | B2 |
| 6879574 | Naghian et al. | Apr 2005 | B2 |
| 6888322 | Dowling et al. | May 2005 | B2 |
| 6888323 | Null et al. | May 2005 | B1 |
| 6892168 | Williams et al. | May 2005 | B2 |
| 6897624 | Lys et al. | May 2005 | B2 |
| 6917985 | Madruga et al. | Jul 2005 | B2 |
| 6927547 | Walko, Jr. et al. | Aug 2005 | B2 |
| 6930455 | Chansky et al. | Aug 2005 | B2 |
| 6933486 | Pitigoi-Aron et al. | Aug 2005 | B2 |
| 6933685 | Gutta et al. | Aug 2005 | B2 |
| 6936978 | Morgan et al. | Aug 2005 | B2 |
| 6937985 | Kuma | Aug 2005 | B2 |
| 6944131 | Beshai et al. | Sep 2005 | B2 |
| 6963285 | Fischer et al. | Nov 2005 | B2 |
| 6965205 | Piepgras et al. | Nov 2005 | B2 |
| 6965568 | Larsen | Nov 2005 | B1 |
| 6965575 | Srikrishna et al. | Nov 2005 | B2 |
| 6967448 | Morgan et al. | Nov 2005 | B2 |
| 6969954 | Lys | Nov 2005 | B2 |
| 6970444 | Chwieseni et al. | Nov 2005 | B2 |
| 6975079 | Lys et al. | Dec 2005 | B2 |
| 6977937 | Weinstein et al. | Dec 2005 | B1 |
| 6980537 | Liu | Dec 2005 | B1 |
| 6982982 | Barker, Jr. et al. | Jan 2006 | B1 |
| 6993325 | Waesterlid | Jan 2006 | B1 |
| 7012520 | Webb, Sr. | Mar 2006 | B2 |
| 7012546 | Zigdon et al. | Mar 2006 | B1 |
| 7027808 | Wesby | Apr 2006 | B2 |
| 7031920 | Dowling et al. | Apr 2006 | B2 |
| 7046149 | Badenhop et al. | May 2006 | B1 |
| 7050808 | Janusz et al. | May 2006 | B2 |
| 7064498 | Dowling et al. | Jun 2006 | B2 |
| 7071634 | Johnson et al. | Jul 2006 | B2 |
| 7075254 | Chitta et al. | Jul 2006 | B2 |
| 7084581 | Honma et al. | Aug 2006 | B2 |
| 7109668 | Pogodayev et al. | Sep 2006 | B2 |
| 7113541 | Lys et al. | Sep 2006 | B1 |
| 7119676 | Silverstrim et al. | Oct 2006 | B1 |
| 7122976 | Null et al. | Oct 2006 | B1 |
| 7123140 | Denes | Oct 2006 | B1 |
| 7135824 | Lys et al. | Nov 2006 | B2 |
| 7135956 | Bartone et al. | Nov 2006 | B2 |
| 7148800 | Cunningham et al. | Dec 2006 | B2 |
| 7126291 | Johnson et al. | Jan 2007 | B2 |
| 7161213 | Ito et al. | Jan 2007 | B2 |
| 7164110 | Pitigoi-Aron et al. | Jan 2007 | B2 |
| 7166970 | Johnson et al. | Jan 2007 | B2 |
| 7167777 | Budike, Jr. | Jan 2007 | B2 |
| 7170238 | Adamson et al. | Jan 2007 | B2 |
| 7172328 | Hoelen et al. | Feb 2007 | B2 |
| 7180251 | Van Eerden | Feb 2007 | B2 |
| 7184905 | Stefan | Feb 2007 | B2 |
| 7186003 | Dowling et al. | Mar 2007 | B2 |
| 7187141 | Mueller et al. | Mar 2007 | B2 |
| 7190124 | Kumar et al. | Mar 2007 | B2 |
| 7190125 | McDonough et al. | Mar 2007 | B2 |
| 7209958 | Crookham et al. | Apr 2007 | B2 |
| 7211968 | Adamson et al. | May 2007 | B2 |
| 7231060 | Dowling et al. | Jun 2007 | B2 |
| 7242152 | Dowling et al. | Jul 2007 | B2 |
| 7248239 | Dowling et al. | Jul 2007 | B2 |
| 7253566 | Lys et al. | Aug 2007 | B2 |
| 7333903 | Walters et al. | Feb 2008 | B2 |
| 7529594 | Walters et al. | May 2009 | B2 |
| 7546167 | Walters et al. | Jun 2009 | B2 |
| 7546168 | Walters et al. | Jun 2009 | B2 |
| 7603184 | Walters et al. | Oct 2009 | B2 |
| 20010005368 | Rune | Jun 2001 | A1 |
| 20010034793 | Madruga et al. | Oct 2001 | A1 |
| 20010038343 | Meyer et al. | Nov 2001 | A1 |
| 20010040805 | Lansing et al. | Nov 2001 | A1 |
| 20020002444 | Williams et al. | Jan 2002 | A1 |
| 20020008621 | Barritz et al. | Jan 2002 | A1 |
| 20020009975 | Janusz et al. | Jan 2002 | A1 |
| 20020013679 | Petite | Jan 2002 | A1 |
| 20020013856 | Garcia-Luna-Aceves et al. | Jan 2002 | A1 |
| 20020016767 | Johnston | Feb 2002 | A1 |
| 20020044549 | Johansson et al. | Apr 2002 | A1 |
| 20020060530 | Sembhi et al. | May 2002 | A1 |
| 20020067284 | Chamberlain et al. | Jun 2002 | A1 |
| 20020074559 | Downling et al. | Jun 2002 | A1 |
| 20020091653 | Peevey | Jul 2002 | A1 |
| 20020101184 | Chansky et al. | Aug 2002 | A1 |
| 20020130627 | Morgan et al. | Sep 2002 | A1 |
| 20020143482 | Karanam et al. | Oct 2002 | A1 |
| 20020152045 | Dowling et al. | Oct 2002 | A1 |
| 20020154025 | Ling | Oct 2002 | A1 |
| 20020161556 | Williams et al. | Oct 2002 | A1 |
| 20020176396 | Hammel et al. | Nov 2002 | A1 |
| 20020178047 | Or et al. | Nov 2002 | A1 |
| 20020181427 | Sparr et al. | Dec 2002 | A1 |
| 20020193969 | Frantz et al. | Dec 2002 | A1 |
| 20030020595 | Wacyk | Jan 2003 | A1 |
| 20030057884 | Dowling et al. | Mar 2003 | A1 |
| 20030061159 | Adams et al. | Mar 2003 | A1 |
| 20030076281 | Morgan et al. | Apr 2003 | A1 |
| 20030076417 | Thomas et al. | Apr 2003 | A1 |
| 20030085749 | Xu et al. | May 2003 | A1 |
| 20030101108 | Botham et al. | May 2003 | A1 |
| 20030128134 | Fierro et al. | Jul 2003 | A1 |
| 20030137968 | Lareau et al. | Jul 2003 | A1 |
| 20030198188 | Castlebury et al. | Oct 2003 | A1 |
| 20030222587 | Dowling, Jr. et al. | Dec 2003 | A1 |
| 20040001442 | Rayment et al. | Jan 2004 | A1 |
| 20040032226 | Lys | Feb 2004 | A1 |
| 20040051467 | Balasubramaniam et al. | Mar 2004 | A1 |
| 20040051485 | Chansky et al. | Mar 2004 | A1 |
| 20040052076 | Mueller et al. | Mar 2004 | A1 |
| 20040062224 | Brownrigg et al. | Apr 2004 | A1 |
| 20040068549 | Motoyama | Apr 2004 | A1 |
| 20040099736 | Neumark | May 2004 | A1 |
| 20040119415 | Lansing et al. | Jun 2004 | A1 |
| 20040136194 | Disalvo | Jul 2004 | A1 |
| 20040138786 | Blackett et al. | Jul 2004 | A1 |
| 20040151129 | Kun-Szabo et al. | Aug 2004 | A1 |
| 20040162902 | Davis | Aug 2004 | A1 |
| 20040177032 | Bradley et al. | Sep 2004 | A1 |
| 20040178257 | Jeffery | Sep 2004 | A1 |
| 20040181496 | Odinotski et al. | Sep 2004 | A1 |
| 20040212993 | Morgan et al. | Oct 2004 | A1 |
| 20040232856 | Huber | Nov 2004 | A1 |
| 20040248578 | Korpela et al. | Dec 2004 | A1 |
| 20040252643 | Joshi | Dec 2004 | A1 |
| 20050029955 | Blake | Feb 2005 | A1 |
| 20050035717 | Adamson et al. | Feb 2005 | A1 |
| 20050035720 | Blake | Feb 2005 | A1 |
| 20050041161 | Dowling et al. | Feb 2005 | A1 |
| 20050047134 | Mueller et al. | Mar 2005 | A1 |
| 20050054292 | Janusz et al. | Mar 2005 | A1 |
| 20050067982 | Pilz | Mar 2005 | A1 |
| 20050075104 | Jain et al. | Apr 2005 | A1 |
| 20050076034 | Addonisio et al. | Apr 2005 | A1 |
| 20050094493 | Walko, Jr. | May 2005 | A1 |
| 20050102040 | Kruse et al. | May 2005 | A1 |
| 20050124346 | Corbett et al. | Jun 2005 | A1 |
| 20050128666 | Pogodayev et al. | Jun 2005 | A1 |
| 20050136834 | Bonta et al. | Jun 2005 | A1 |
| 20050145688 | Milenkovic et al. | Jul 2005 | A1 |
| 20050146284 | Honma et al. | Jul 2005 | A1 |
| 20050146288 | Johnson et al. | Jul 2005 | A1 |
| 20050149345 | Daily | Jul 2005 | A1 |
| 20050161511 | Parker et al. | Jul 2005 | A1 |
| 20050163101 | Ashwood Smith et al. | Jul 2005 | A1 |
| 20050163144 | Srikrishna et al. | Jul 2005 | A1 |
| 20050164630 | Kates | Jul 2005 | A1 |
| 20050184671 | Williams et al. | Aug 2005 | A1 |
| 20050207159 | Maxik | Sep 2005 | A1 |
| 20050213350 | Tsuda et al. | Sep 2005 | A1 |
| 20050225441 | Kernan | Oct 2005 | A1 |
| 20050232289 | Walko, Jr. et al. | Oct 2005 | A1 |
| 20050236998 | Mueller et al. | Oct 2005 | A1 |
| 20050242181 | Cunningham et al. | Nov 2005 | A1 |
| 20050248300 | Walko, Jr. et al. | Nov 2005 | A1 |
| 20050249215 | Kelsey et al. | Nov 2005 | A1 |
| 20050259647 | Wakumoto et al. | Nov 2005 | A1 |
| 20050271006 | Chari et al. | Dec 2005 | A1 |
| 20050275532 | Ferri et al. | Dec 2005 | A1 |
| 20050276233 | Shepard et al. | Dec 2005 | A1 |
| 20050277443 | Ozluturk | Dec 2005 | A1 |
| 20050280555 | Warner, IV | Dec 2005 | A1 |
| 20050282494 | Kossi et al. | Dec 2005 | A1 |
| 20050286426 | Padhye et al. | Dec 2005 | A1 |
| 20060002368 | Budampati et al. | Jan 2006 | A1 |
| 20060004679 | Cahill-O'Brien et al. | Jan 2006 | A1 |
| 20060020498 | Aitipamula et al. | Jan 2006 | A1 |
| 20060038672 | Schoettle | Feb 2006 | A1 |
| 20060044152 | Wang | Mar 2006 | A1 |
| 20060049935 | Giannopoulos et al. | Mar 2006 | A1 |
| 20060058925 | Diederiks et al. | Mar 2006 | A1 |
| 20060064205 | Ying | Mar 2006 | A1 |
| 20060071605 | Diederuks | Apr 2006 | A1 |
| 20060108950 | Chansky et al. | May 2006 | A1 |
| 20060125426 | Veskovic et al. | Jun 2006 | A1 |
| 20060144920 | Fang et al. | Jul 2006 | A1 |
| 20060202851 | Cash et al. | Sep 2006 | A1 |
| 20060235611 | Deaton et al. | Oct 2006 | A1 |
| 20060242200 | Horowitz et al. | Oct 2006 | A1 |
| 20060244395 | Taipale et al. | Nov 2006 | A1 |
| 20060244631 | Zigdon et al. | Nov 2006 | A1 |
| 20060273970 | Mosebrook et al. | Dec 2006 | A1 |
| 20060279236 | Johnson et al. | Dec 2006 | A1 |
| 20060284734 | Newman, Jr. | Dec 2006 | A1 |
| 20070013489 | Bechtle et al. | Jan 2007 | A1 |
| 20070018783 | Erhardt | Jan 2007 | A1 |
| 20070029949 | Null et al. | Feb 2007 | A1 |
| 20070032990 | Williams et al. | Feb 2007 | A1 |
| 20070043540 | Cleland et al. | Feb 2007 | A1 |
| 20070046489 | Fair et al. | Mar 2007 | A1 |
| 20070049242 | Fair et al. | Mar 2007 | A1 |
| 20070057807 | Walters et al. | Mar 2007 | A1 |
| 20070061020 | Bovee et al. | Mar 2007 | A1 |
| 20070063866 | Webb | Mar 2007 | A1 |
| 20070085699 | Walters et al. | Apr 2007 | A1 |
| 20070085700 | Walters et al. | Apr 2007 | A1 |
| 20070085702 | Walters et al. | Apr 2007 | A1 |
| 20070086912 | Dowling et al. | Apr 2007 | A1 |
| 20070091623 | Walters et al. | Apr 2007 | A1 |
| 20070103324 | Kosuge et al. | May 2007 | A1 |
| 20070109142 | McCollough, Jr. | May 2007 | A1 |
| 20070121323 | Pawlik et al. | May 2007 | A1 |
| 20070124074 | Katoh et al. | May 2007 | A1 |
| 20070124077 | Hedlund, Jr. | May 2007 | A1 |
| 20070126368 | McDonough et al. | Jun 2007 | A1 |
| 20070146126 | Wang | Jun 2007 | A1 |
| 20070194722 | Bruekers et al. | Aug 2007 | A1 |
| 20070195526 | Dowling et al. | Aug 2007 | A1 |
| 20070222581 | Hawkins et al. | Sep 2007 | A1 |
| 20070230159 | Cortenraad et al. | Oct 2007 | A1 |
| 20080191897 | McCollough | Aug 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 2419118 | Aug 2003 | CA |
| 1571618 | Jan 2005 | CN |
| 1596053 | Mar 2005 | CN |
| 0586322 | Mar 1994 | EP |
| 0880308 | Nov 1998 | EP |
| 1239704 | Sep 2002 | EP |
| 1241924 | Sep 2002 | EP |
| 1339155 | Aug 2003 | EP |
| 0880308 | Sep 2003 | EP |
| 1742321 | Jan 2007 | EP |
| 2116211 | Jul 1998 | ES |
| 2601485 | Jan 1988 | FR |
| 2710205 | Mar 1995 | FR |
| 2815744 | Apr 2002 | FR |
| 2368905 | May 2002 | GB |
| 2372160 | Aug 2002 | GB |
| 2403357 | Dec 2004 | GB |
| 11-283760 | Oct 1999 | JP |
| 10-2005-0003165 | Jan 2005 | KR |
| WO 9620369 | Jul 1996 | WO |
| 9636202 | Nov 1996 | WO |
| 9802859 | Jan 1998 | WO |
| WO 0076034 | Dec 2000 | WO |
| WO 0211098 | Feb 2002 | WO |
| WO 03034570 | Apr 2003 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070085701 A1 | Apr 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60715584 | Sep 2005 | US |
