1. Field of the Invention
The present invention relates to load control systems for controlling electrical loads and more particularly to a procedure for addressing remotely-located control devices of a radio frequency (RF) lighting control system.
2. Description of the Related Art
Control systems for controlling electrical loads, such as lights, motorized window treatments, and fans, are known. Such control systems often use radio frequency (RF) transmission to provide wireless communication between the control devices of the system. Examples of RF lighting control systems are disclosed in commonly-assigned U.S. Pat. No. 5,905,442, issued on May 18, 1999, entitled METHOD AND APPARATUS FOR CONTROLLING AND DETERMINING THE STATUS OF ELECTRICAL DEVICES FROM REMOTE LOCATIONS, and commonly-assigned U.S. Pat. No. 6,803,728, issued Oct. 12, 2004, entitled SYSTEM FOR CONTROL OF DEVICES. The entire disclosures of both patents are hereby incorporated by reference.
The RF lighting control system of the '442 patent includes wall-mounted load control devices, table-top and wall-mounted master controls, and signal repeaters. The control devices of the RF lighting control system include RF antennas adapted to transmit and receive the RF signals that provide for communication between the control devices of the lighting control system. The control devices all transmit and receive the RF signals on the same frequency. Each of the load control devices includes a user interface and an integral dimmer circuit for controlling the intensity of an attached lighting load. The user interface has a pushbutton actuator for providing on/off control of the attached lighting load and a raise/lower actuator for adjusting the intensity of the attached lighting load. The table-top and wall-mounted master controls have a plurality of buttons and are operable to transmit RF signals to the load control devices to control the intensities of the lighting loads.
To prevent interference with other nearby RF lighting control systems located in close proximity, the RF lighting control system of the '442 patent preferably uses a house code (i.e., a house address), which each of the control devices stores in memory. It is particularly important in applications such as high-rise condominiums and apartment buildings that neighboring systems each have their own separate house code to avoid a situation where neighboring systems attempt to operate as a single system rather than as separate systems. Accordingly, during installation of the RF lighting control system, a house code selection procedure is employed to ensure that a proper house code is selected. In order to accomplish this procedure, one repeater of each system is selected as a “main” repeater. The house code selection procedure is initialized by pressing and holding a “main” button on the selected one repeater in one of the RF lighting control systems. The repeater randomly selects one of 256 available house codes and then verifies that no other nearby RF lighting control systems are utilizing that house code. The repeater illuminates a light-emitting diode (LED) to display that a house code has been selected. This procedure is repeated for each neighboring RF lighting control system. The house code is transmitted to each of the control devices in the lighting control system during an addressing procedure described below.
Collisions between transmitted RF communication signals may occur in the RF lighting control system when two or more control devices attempt to transmit at the same time. Accordingly, each of the control devices of the lighting control system is assigned a unique device address (typically one byte in length) for use during normal operation. The device addresses are unique identifiers that are used by the devices of the control system to distinguish the control devices from each other during normal operation. The device addresses allow the control devices to transmit the RF signals according to a communication protocol at predetermined times to avoid collisions. Further, the signal repeaters help to ensure error-free communication by repeating the RF communication signals such that every component of the system receives the RF signals intended for that component.
The house code and the device address are typically included in each RF signal transmitted in the lighting control system. After the house code selection procedure is completed during installation of the lighting control system, an addressing procedure, which provides for assignment of the device addresses to each of the control devices, is executed. In the RF lighting control system described in the '442 patent, the addressing procedure is initiated at a repeater of the lighting control system (e.g., by pressing and holding an “addressing mode” button on the repeater), which places all repeaters of the system into an “addressing mode.” The main repeater is responsible for assigning device addresses to the RF control devices (e.g., master controls, wall-mounted load control devices, etc.) of the control system. The main repeater assigns a device address to an RF control device in response to a request for an address sent by the control device.
To initiate a request for the address, a user moves to one of the wall-mounted or table-top control devices and presses a button on the control device (e.g., an on/off actuator of the wall-mounted load control devices). The control device transmits a signal associated with the actuation of the button. This signal is received and interpreted by the main repeater as a request for an address. In response to the request for address signal, the main repeater assigns and transmits a next available device address to the requesting control device. A visual indicator is then activated to signal to the user that the control device has received a system address from the main repeater. For example, lights connected to a wall-mounted load control device, or an LED located on a master control, may flash. The addressing mode is terminated when a user presses and holds the addressing mode button of the repeater, which causes the repeater to issue an exit address mode command to the control system.
The above-described addressing procedure of the control system of the '442 patent requires that the control devices be located in a reasonably accessible fashion to provide for physical contact between a user and an actuator of the RF control device to identify each control device that requires an address. The addressing procedure, therefore, is directed to addressing RF control devices, such as wall-mounted load control devices and master controls, that are adapted for contact by a user during the addressing procedure. The prior addressing procedure, however, is not adapted for addressing RF load control devices that may be mounted in relatively inaccessible locations. For example, load control devices, such as electronic dimming ballasts, motorized window treatments, or remote dimmer modules, may be mounted in remote locations such that contact with the load control device during the addressing procedure is rendered impractical.
Wired control systems (i.e., control systems that utilize wired communication links) for remotely mounted electronic dimming ballasts and motorized window treatments are known in the art. An example of a lighting control system that comprises a plurality of electronic dimming ballasts that are operable to communicate on a wired communication link using the DALI (Digital Addressable Lighting Interface) protocol is described in greater detail in commonly-assigned U.S. patent application Ser. No. 11/011,933, filed Dec. 14, 2004, entitled DISTRIBUTED INTELLIGENCE BALLAST SYSTEM AND EXTENDED LIGHTING CONTROL PROTOCOL, the entire disclosure of which is incorporated herein by reference. An example of a control system comprising a plurality of motorized window treatments is described in greater detail in commonly-assigned U.S. Pat. No. 6,983,783, issued Jan. 10, 2006, entitled MOTORIZED SHADE CONTROL SYSTEM, the entire disclosure of which is incorporated herein by reference.
These control systems utilize a random addressing procedure to assign the device addresses. To facilitate the random addressing procedure, each control device comprises a unique serial number, which is stored in memory when the control device is manufactured. The serial number is typically much larger than a device address (e.g., 3 to 6 bytes in length) and is used to uniquely identify each control device during initialization procedures. Because of the relatively large size of the serial number and the potentially large number of control devices in a system, it is often impractical to use the serial number to communicate between control devices during normal operation. Since the serial number is typically transmitted with each message, the messages tend to be larger and the communication times tend to be longer. Therefore, a shorter device address is typically assigned to each control device during the random addressing procedure.
The random addressing procedure is activated, for example, by a user pressing one or more buttons on a wall-mounted keypad of the control system. The selected keypad transmits a query message on the wired link to all unaddressed control devices. Accordingly, all control devices on the wired communication link respond by sending their serial numbers to the selected keypad. The selected keypad receives the serial numbers from all control devices on the link and randomly assigns a unique device address to each control device.
However, since two or more RF lighting control systems may be located in close proximity to each other, such a random addressing procedure may cause the improper initialization of the RF lighting control systems if both systems have unaddressed control devices. Therefore, there is a need for a method of addressing inaccessible remotely-located control devices of an RF lighting control system in which physical contact with the RF control devices is not required.
According to the present invention, a method for assigning a unique device address to a remotely-located control device in a lighting control system comprises the steps of (1) applying power to the control device; (2) the control device transmitting a signal uniquely identifying the control device within a predetermined amount of time after the step of applying power; and (3) the control device subsequently receiving the unique device address.
The present invention further provides a method for providing an address to a first remote control device in an RF control system. RF control signals are sent from a second device to the first remote control device and each include the address to enable the first remote control device to respond to the RF control signals. The method comprises the steps of cycling power from off to on to the first remote control device to designate the first remote control device as requiring the address; identifying at the second device the remote control device designated as requiring the address; and providing the address to the first remote control device by sending an RF addressing signal from the second device to the first remote control device to enable the first remote control device to respond to RF control signals sent from the second device that include the address.
The present invention further provides a method for selecting a first remotely-located control device from a plurality of control devices in a lighting control system. The method comprises the step of applying power to a subset of the plurality of control devices. The subset contains the first control device. The method further comprises the steps of receiving a signal requesting the serial number at each of the control devices of the subset within a predetermined amount of time after the step of interrupting and restoring power; transmitting the serial number of at least one of the control devices of the subset; generating a list of the serial numbers; and selecting the first control device from the list of serial numbers.
Other features and advantages of the present invention will become apparent from the following description of the invention that refers to the accompanying drawings.
The foregoing summary, as well as the following detailed description of the preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purposes of illustrating the invention, there is shown in the drawings an embodiment that is presently preferred, in which like numerals represent similar parts throughout the several views of the drawings, it being understood, however, that the invention is not limited to the specific methods and instrumentalities disclosed.
The lighting control system 100 comprises a wall-mounted dimmer 112 and a remote dimming module 114, which are operable to control the intensities of the lighting loads 104, 106, respectively. The remote dimming module 114 is preferably located in a ceiling area, i.e., near a lighting fixture, or in another remote location that is inaccessible to a typical user of the lighting control system 100. A motorized window treatment (MWT) control module 116 is coupled to the motorized roller shade 108 for controlling the position of the fabric of the roller shade and the amount of daylight entering the room. Preferably, the MWT control module 116 is located inside the roller tube of the motorized roller shade 108, and is thus inaccessible to the user of the system.
A first wall-mounted master control 118 and a second wall-mounted master control 120 each comprise a plurality of buttons that allow a user to control the intensity of the lighting loads 104, 106 and the position of the motorized roller shade 108. In response to an actuation of one of the buttons, the first and second wall-mounted master controls 118, 120 transmit RF signals 110 to the wall-mounted dimmer 112, the remote dimming module 114, and the MWT control module 116 to control the associated loads.
Preferably, the control devices of the lighting control system 100 are operable to transmit and receive the RF signals 110 on a plurality of channels (i.e., frequencies). A repeater 122 is operable to determine a select one of the plurality of channels for all of the control devices to utilize. The repeater 122 also receives and re-transmits the RF signals 110 to ensure that all of the control devices of the lighting control system 100 receive the RF signals. Each of the control devices in the RF lighting control system comprises a serial number that is preferably six bytes in length and is programmed in a memory during production. As in the prior art control systems, the serial number is used to uniquely identify each control device during initial addressing procedures.
The lighting control system 100 further comprises a first circuit breaker 124 coupled between the HOT connection 102 and a first power wiring 128, and a second circuit breaker 126 coupled between the HOT connection 102 and a second power wiring 130. The wall-mounted dimmer 112, the first wall-mounted master control 118, the remote dimming module 114, and the MWT control module 116 are coupled to the first power wiring 128. The repeater 122 and the second wall-mounted master control 120 are coupled to the second power wiring 130. The repeater 122 is coupled to the second power wiring 130 via a power supply 132 plugged into a wall-mounted electrical outlet 134. The first and second circuit breakers 124, 126 allow power to be disconnected from the control devices and the electrical loads of the RF lighting control system 100.
The first and second circuit breakers 124, 126 preferably include manual switches that allow the circuit breakers to be reset to the closed position from the open position. The manual switches of the first and second circuit breakers 124, 126 also allow the circuit breakers to be selectively switched to the open position from the closed position. The construction and operation of circuit breakers is well known and, therefore, no further discussion is necessary.
The addressing procedure 200 begins when the lighting control system 100 enters an addressing mode at step 210, for example, in response to a user pressing and holding an actuator on the repeater 122 for a predetermined amount of time. At step 212, the user manually actuates the non-remote devices, i.e., the wall-mounted dimmer 112 and the first and second wall-mounted master controls 118, 120, as in the addressing procedure of the prior art lighting control system disclosed in the '442 patent. In response to an actuation of a button, the non-remote devices transmit a signal associated with the actuation of the button to the repeater 122 on the predetermined addressing channel. Accordingly, the repeater 122 receives the signal, which is interpreted as a request for an address, and transmits the next available device address to the actuated non-remote control device.
Next, the remote control devices, i.e., the remote dimming module 114 and the MWT control module 116, are assigned device addresses. In order to prevent the inadvertent assignment of addresses to unaddressed devices in a neighboring RF lighting control system, e.g., an RF lighting control system installed within approximately 60 feet of the system 100, the user cycles power to all of the remote devices at step 214. For example, the user switches the first circuit breaker 124 to the open position in order to disconnect the source from the first power wiring 128, and then immediately switches the first circuit breaker back to the closed position to restore power. Accordingly, the power provided to the remote dimming module 114 and the MWT control module 116 is cycled. Upon power-up, these remotely-located control devices enters a “power-cycled” state. Specifically, the remote devices set the POWER_CYCLED flag in memory to designate that power has recently been applied. Further, the remote devices begin to decrement a “power-cycled” timer. Preferably, the “power-cycled” timer is set to expire after approximately 10 minutes, after which the remote devices clear the POWER_CYCLED flag.
At this time, the remote device discovery procedure 216, which is shown in
Referring to
Next, the repeater 122 transmits a “request serial number” message to each device that was stored in memory (i.e., each device having a random slot number and a random data byte stored in memory at step 316). Specifically, at step 318, the repeater transmits the message to the “next” device, e.g., the first device in memory when the “request serial number” message is transmitted for the first time. Since the repeater 122 has stored only the number of the ACK transmission slot and the associated random data byte for each device that transmitted an ACK message, the “request serial number” message is transmitted using this information. For example, the repeater 122 may transmit a “request serial number” message to the device that transmitted the ACK message in slot number 34 with the random data byte 0xA2 (hexadecimal). The repeater 122 waits to receive a serial number back from the device at step 320. When the repeater 122 receives the serial number, the serial number is stored in memory at step 322. At step 324, the repeater transmits a “set found flag” message to the present control device, i.e., to the control device having the serial number that was received at step 320. Upon receipt of the “set found flag” message, the remote device sets the FOUND flag in memory, such that the device no longer responds to query messages during the remote device discovery procedure 216. At step 326, if all serial numbers have not been collected, the process loops around to request the serial number of the next control device at step 318.
Since collisions might have occurred when the remote devices were transmitting the ACK message (at step 314), the same subset of devices is polled again at step 312. Specifically, if all serial numbers have been collected at step 326, the process loops around to poll the same subset of devices again at step 312. If no ACK messages are received at step 314, the process flows to step 328. If the variable M is less than a constant MMAX at step 328, the variable M is incremented at step 330. To ensure that all of the devices in the first subset have transmitted an ACK message to the query at step 312 without a collision occurring, the constant MMAX is preferably two (2) such that the repeater 122 preferably receives no ACK messages at step 314 in response to transmitting two queries at step 312. If the variable M is not less than the constant MMAX at step 328, then a determination is made at step 332 as to whether there are more devices to poll. If so, the variable M is set to zero at step 334 and the subset of devices (that are polled in step 312) is changed at step 336. For example, if the devices having even serial numbers were previously polled, the subset will be changed to those devices having odd serial numbers. If there are no devices left to poll at step 332, the remote device discovery procedure exits at step 338.
Referring back to
The step of cycling power to the remote devices, i.e., step 214, prevents unaddressed devices in a neighboring system from being addressed. The step of cycling power to the remote devices is very important when many RF lighting control systems are being concurrently installed in close proximity, such as in an apartment building or a condominium, and are being configured at the same time. Since two neighboring apartments or condominiums will each have their own circuit breakers, the remote devices of each system can be separately power cycled. However, this step is optional since the user may be able to determine that the present lighting control system 100 is not located close to any other unaddressed RF lighting control systems. If the step of cycling power is omitted from the procedure 200, the repeater 122 will poll all unaddressed devices at step 312 in the remote device discovery procedure 216 rather than polling only unaddressed devices that have been recently power cycled. Further, the step of cycling power need not occur after step 212, but could occur at any time before the remote device discovery procedure, i.e., step 216, is executed, as long as the remote device discovery procedure is completed before the “power-cycled” timer expires.
The control devices of the lighting control system 100 are operable to transmit and receive the RF signals 110 on a plurality of channels. Accordingly, the repeater 122 is operable to determine the quality of each of the channels, i.e., determine the ambient noise on each of the channels, and to choose a select one of the channels for the system to communicate on. In prior art lighting control systems, an unaddressed control device communicated with the repeater on a predetermined addressing frequency in order to receive a unique device address and the selected channel. However, if there is a substantial amount of noise on the predetermined addressing frequency, the control devices are not able to communicate with the repeater and configuration of the control devices is hindered. Therefore, it is desirable to allow the RF lighting control system to communicate on the selected channel during the configuration procedure.
At step 412, the repeater 122 begins repeatedly transmitting a beacon message to the control devices on the selected channel. Each of the control devices sequentially changes to each of the available channels to listen for the beacon message. Upon receiving the beacon message, the control devices begins to communicate on the selected channel.
Referring to
The second beacon process 550, which is executed by each of the control devices of the RF lighting control system 100 at power up, begins at step 560. If the control device has a unique device address at step 562, the process simply exits at step 564. However, if the control device is unaddressed at step 562, the control device begins to communicate on the first channel (i.e., to listen for the beacon message on the lowest available channel) and a timer is initialized to a constant TMAX and starts decreasing in value at step 566. If the control device hears the beacon message at step 568, the control device maintains the present channel as the communication channel at step 570 and exits the process at step 564.
Preferably, the control device listens for a predetermined amount of time (i.e., corresponding to the constant TMAX of the timer) on each of the available channels and steps through consecutive higher channels until the control device receives the beacon message. Preferably, the predetermined amount of time is substantially equal to the time required to transmit the beacon message twice plus an additional amount of time. For example, if the time required to transmit the beacon message once is approximately 140 msec and the additional amount of time is 20 msec, the predetermined amount of time that the control device listens on each channel is preferably 300 msec. Specifically, if the control device does not hear the beacon message at step 568, a determination is made as to whether the timer has expired at step 572. If the timer has not expired, the process loops until the timer has expired. At step 574, if the present channel is not equal to the maximum channel, i.e., the highest available channel, the control device begins to communicate on the next higher available channel and the timer is reset at step 576. Then, the control device listens for the beacon message once again at step 568. If the present channel is equal to the maximum channel at step 574, the control device begins to communicate again on the first channel and the timer is reset at step 578. Accordingly, the second beacon process 550 continues to loop until the control device receives the beacon message.
While the present invention has been described with reference to an RF lighting control system, the procedures of the present invention could be applied to other types of lighting control system, e.g., a wired lighting control system, in order to assign an address to a remotely-located control device on a wired communication link.
Although the present invention has been described in relation to particular embodiments thereof, many other variations and modifications and other uses will be apparent to those skilled in the art. It is preferred, therefore, that the present invention be limited not by the specific disclosure herein, but only by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4114099 | Hollander | Sep 1978 | A |
4529980 | Liotine et al. | Jul 1985 | A |
4864588 | Simpson et al. | Sep 1989 | A |
4932037 | Simpson et al. | Jun 1990 | A |
4995053 | Simpson et al. | Feb 1991 | A |
5239205 | Hoffman et al. | Aug 1993 | A |
5340954 | Hoffman et al. | Aug 1994 | A |
5365551 | Snodgrass et al. | Nov 1994 | A |
5375254 | Owen | Dec 1994 | A |
5454077 | Cheron | Sep 1995 | A |
5467266 | Jacobs et al. | Nov 1995 | A |
5671387 | Jacobs et al. | Sep 1997 | A |
5736965 | Mosebrook et al. | Apr 1998 | A |
5818128 | Hoffman et al. | Oct 1998 | A |
5838226 | Houggy et al. | Nov 1998 | A |
5848054 | Mosebrook et al. | Dec 1998 | A |
5905442 | Mosebrook | May 1999 | A |
5982103 | Mosebrook et al. | Nov 1999 | A |
6175201 | Sid | Jan 2001 | B1 |
6275476 | Wood, Jr. | Aug 2001 | B1 |
6324089 | Symoen et al. | Nov 2001 | B1 |
6388399 | Eckel et al. | May 2002 | B1 |
6535109 | Mahdavi | Mar 2003 | B1 |
6661336 | Atkins et al. | Dec 2003 | B1 |
6687487 | Mosebrook et al. | Feb 2004 | B1 |
6803728 | Balasubramaniam | Oct 2004 | B2 |
6812843 | Soto et al. | Nov 2004 | B2 |
6819223 | Amtmann | Nov 2004 | B2 |
6831562 | Rodgers et al. | Dec 2004 | B2 |
6831569 | Wang et al. | Dec 2004 | B2 |
6856236 | Christensen et al. | Feb 2005 | B2 |
6876294 | Regan | Apr 2005 | B1 |
6879806 | Shorty | Apr 2005 | B2 |
6901439 | Bonasia | May 2005 | B1 |
6901542 | Bartenstein et al. | May 2005 | B2 |
6927547 | Walko, Jr. et al. | Aug 2005 | B2 |
6975206 | Reining | Dec 2005 | B2 |
6980080 | Christensen et al. | Dec 2005 | B2 |
6983783 | Carmen, Jr. et al. | Jan 2006 | B2 |
7031735 | Koshino | Apr 2006 | B2 |
7054616 | Rickhoff et al. | May 2006 | B2 |
7085627 | Bamberger et al. | Aug 2006 | B2 |
7102502 | Autret | Sep 2006 | B2 |
7106261 | Nagel | Sep 2006 | B2 |
7123140 | Denes | Oct 2006 | B1 |
7126291 | Kruse et al. | Oct 2006 | B2 |
7130584 | Hirvonen | Oct 2006 | B2 |
7155296 | Klasson et al. | Dec 2006 | B2 |
7193504 | Carrender et al. | Mar 2007 | B2 |
7211968 | Adamson et al. | May 2007 | B2 |
7219141 | Bonasia et al. | May 2007 | B2 |
7253717 | Armstrong et al. | Aug 2007 | B2 |
7307542 | Chandler et al. | Dec 2007 | B1 |
7346016 | Nielsen et al. | Mar 2008 | B2 |
7486172 | Martinez et al. | Feb 2009 | B2 |
7498924 | Scherabon | Mar 2009 | B2 |
20020043938 | Lys | Apr 2002 | A1 |
20020046226 | Nakabe et al. | Apr 2002 | A1 |
20020049822 | Burkhardt et al. | Apr 2002 | A1 |
20020126020 | Wang et al. | Sep 2002 | A1 |
20020140379 | Chevalier et al. | Oct 2002 | A1 |
20020154025 | Ling | Oct 2002 | A1 |
20030040813 | Gonzales et al. | Feb 2003 | A1 |
20030109270 | Shorty | Jun 2003 | A1 |
20040051467 | Balasubramaniam et al. | Mar 2004 | A1 |
20040158624 | Bodin et al. | Aug 2004 | A1 |
20040250964 | Carmen et al. | Dec 2004 | A1 |
20050102040 | Kruse et al. | May 2005 | A1 |
20050280598 | Webb et al. | Dec 2005 | A1 |
20060002110 | Dowling et al. | Jan 2006 | A1 |
20060071757 | Burghard et al. | Apr 2006 | A1 |
20060125426 | Veskovic | Jun 2006 | A1 |
20060171332 | Barnum | Aug 2006 | A1 |
20060174102 | Smith et al. | Aug 2006 | A1 |
20060273970 | Mosebrook et al. | Dec 2006 | A1 |
20060284734 | Newman, Jr. | Dec 2006 | A1 |
20070076650 | Manjeshwar et al. | Apr 2007 | A1 |
20070126555 | Bandy | Jun 2007 | A1 |
20070139164 | O'Toole et al. | Jun 2007 | A1 |
20070159305 | Cesar et al. | Jul 2007 | A1 |
20070200677 | Murano | Aug 2007 | A1 |
20080055073 | Raneri | Mar 2008 | A1 |
20080068126 | Johnson | Mar 2008 | A1 |
20080068204 | Carmen | Mar 2008 | A1 |
20080089266 | Orsat | Apr 2008 | A1 |
20080092075 | Jacob et al. | Apr 2008 | A1 |
20080111491 | Spira | May 2008 | A1 |
20080125057 | Nass et al. | May 2008 | A1 |
20080136663 | Courtney | Jun 2008 | A1 |
20090201135 | Kawamura et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
0 767 551 | Apr 1997 | EP |
1513376 | Sep 2003 | EP |
1 513 376 | Mar 2005 | EP |
1 693 991 | Aug 2006 | EP |
2410867 | Aug 2005 | GB |
03 244954 | Oct 1991 | JP |
2003 087403 | Mar 2003 | JP |
WO 9729467 | Aug 1997 | WO |
WO 0152515 | Jul 2001 | WO |
WO 02071689 | Sep 2002 | WO |
WO 03007665 | Jan 2003 | WO |
WO 2006046104 | May 2006 | WO |
WO2006099422 | Sep 2006 | WO |
Number | Date | Country | |
---|---|---|---|
20080068126 A1 | Mar 2008 | US |