The present invention relates generally to the field of programmable controllers for homes and/or buildings are their related grounds. More specifically, the present invention relates to simplified interfaces for such controllers having interview programming capabilities.
Controllers are used on a wide variety of devices and systems for controlling various functions in homes and/or buildings and their related grounds. Some controllers have schedule programming that modifies device parameter set points as a function of date and/or time. Some such device or system controllers that utilize schedule programming for controlling various functions in homes and/or buildings and their related grounds include, for example, HVAC controllers, water heater controllers, water softener controllers, security system controllers, lawn sprinkler controllers, and lighting system controllers.
HVAC controllers, for example, are employed to monitor and, if necessary, control various environmental conditions within a home, office, or other enclosed space. Such devices are useful, for example, in regulating any number of environmental conditions with a particular space including for example, temperature, humidity, venting, air quality, etc. The controller may include a microprocessor that interacts with other components in the system. For example, in many modem thermostats for use in the home, a controller unit equipped with temperature and humidity sensing capabilities may be provided to interact with a heater, blower, flue vent, air compressor, humidifier and/or other components, to control the temperature and humidity levels at various locations within the home. A sensor located within the controller unit and/or one or more remote sensors may be employed to sense when the temperature or humidity reaches a certain threshold level, causing the controller unit to send a signal to activate or deactivate one or more component in the system.
The controller may be equipped with an interface that allows the user to monitor and adjust the environmental conditions at one or more locations within the building. With more modem designs, the interface typically includes a liquid crystal display (LCD) panel inset within a housing that contains the microprocessor as well as other components of the controller. In some designs, the interface may permit the user to program the controller to activate on a certain schedule determined by the user. For example, the interface may include a separate menu routine that permits the user to change the temperature at one or more times during a particular day. Once the settings for that day have been programmed, the user can then repeat the process to change the settings for the other remaining days.
With more modem designs, the programmable controller may include a feature that allows the user to set a separate schedule for weekday and weekend use, or to copy the settings for a particular day and then apply them towards other selected days of the week. While these designs allow the user to copy settings from one day to another, a number of steps are often required to establish a program, adding to the complexity of the interface. In some cases, the interface may not permit the user to select multiple days outside of the normal weekday/weekend scheme. In other cases, the interface is simply too complex to be conveniently used to program a temperature scheme and is simply by-passed or not programmed by the user. Accordingly, there is an ongoing need in the art to decrease the time and complexity associated with programming a multi-day schedule in a programmable controller.
Generally, the present invention pertains to simplified interfaces for controllers having interview programming capabilities.
In one illustrative embodiment, a method of programming a schedule of a controller having a user interface is described. The illustrative method includes the steps of providing one or more interview questions to a user via the user interface; accepting one or more user responses to the one or more interview questions from the user via the user interface; and creating and/or modifying or building a schedule based on the user responses.
The above summary of the present invention is not intended to describe each disclosed embodiment or every implementation of the present invention. The Figures, Detailed Description and Examples which follow more particularly exemplify these embodiments.
The invention may be more completely understood in consideration of the following detailed description of various embodiments of the invention in connection with the accompanying drawings, in which:
While the invention is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the invention to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.
The following description should be read with reference to the drawings, in which like elements in different drawings are numbered in like fashion. The drawings, which are not necessarily to scale, depict selected embodiments and are not intended to limit the scope of the invention. Although examples of construction, dimensions, and materials are illustrated for the various elements, those skilled in the art will recognize that many of the examples provided have suitable alternatives that may be utilized.
Generally, the present invention pertains to simplified interfaces for controllers having interview programming capabilities. These controllers can be used in a variety of systems such as, for example, HVAC systems, water heater systems, water softener systems, sprinkler systems, security systems, lighting systems, and the like. The Figures depict HVAC controllers. While the present invention is not so limited, an appreciation of various aspects of the invention will be gained through a discussion of the examples provided below.
In some embodiments, the interview scheduling blocks 120 and 130 can provide interview questions that elicit an affirmative (e.g., “yes”) or negative (e.g., “no”) user response. Alternatively, or in addition, the interview scheduling blocks 120, and 130 can provide include interview questions that allow a user to select one (or more) answers from a predetermined list of answers.
In some embodiments, these interview questions can solicit information from the user regarding the grouping of the controller set points entered or the temporal relationship of the controller set points such as, for example, the interview question may ask “Do you want the schedule to apply to every day of the week?”, requiring the user to respond with a “YES” or “NO” answer. The interview scheduling block 120 preferably includes questions that are natural language questions, which may be phrases that have one, two, three, four, five, six, or seven or more words, although this is not required in all embodiments.
Alternatively, or in addition, interview scheduling block 130 can provide interview questions that require a numerical user response. For example, these interview questions can solicit information from the user regarding the specific time and temperature set points for each grouping of controller set points solicited by the interview block 120 described above. Interview block 130 can provide a question such as, for example, “What is a comfortable sleeping temperature in the winter?”, requiring the user to respond with a numerical temperature answer. Like interview schedule block 120 above, interview scheduling block 130 can include questions that are natural language questions, which may be phrases that have one, two, three, four, five, six, or seven or more words, although this is not required in all embodiments.
The interview scheduling blocks 120 and 130 can provide one or more interview questions about, for example, which weekdays will have the same schedule?, when a first person wakes up?, when a last person goes to sleep?, when a last person leaves during the day?, when a first person arrives home?, what a comfortable temperature is when heat is on?, what a comfortable temperature is when air conditioning is on?, what a comfortable sleeping temperature is in summer?, and/or what a comfortable sleeping temperature is in winter?
Alternatively, or in addition, the interview scheduling blocks 120 and 130 may provide one or more interview questions that provide a plurality of predetermined answers or responses (e.g., multiple choice format) where the user selects an answer or response. For example, the interview question may provide a question such as, “What type of schedule do you desire?” In this illustrative embodiment, a series of predetermined responses or answers can be provided such as, “Every day of the week is the same,” “Weekdays are the same and Saturday/Sunday is the same,” “Weekday are the same and Saturday/Sunday is different,” “Each Weekday is different and Saturday/Sunday is the same,” and “Each day of the week is different.”
Alternatively, or in addition, once an initial schedule has been built, the interview scheduling blocks 120, and 130 can display a previous answer that was accepted by the user interface based on the prior built schedule. This illustrative feature can provide the user with a convenient option to select and alter only the schedule parameters 140, 150 that the user desires to modify. This feature can be utilized in all illustrative embodiments described herein, however it is not required.
In an illustrative embodiment, the interview question generator 225 provides interview questions, such as those described above, to the user interface 220. The user interface 220 can be any form of user interface such as, for example, a physical interface including a touchscreen, an LCD with buttons, and/or an aural interface including a speaker and microphone, or any other suitable user interface. A user can activate the interview question generator 225 by any suitable mechanism, such as by pressing a schedule button on a touchscreen of the user interface 220. Alternatively, or in addition, the controller 210 may activate the interview question generator 225 on its own, such as when it believes additional scheduling information is needed or might otherwise be desired. In response to questions posed by the interview question generator 225, the user can enter one or more user responses into the user interface 220. The response acceptor 240 accepts the user responses and provides the response to the programmable schedule 250. In some embodiments, the programmable schedule 250 has a number of time and temperature set points that can be entered or modified by the response acceptor 240. Once the schedule is built and/or modified, a control signal 260 is generated by the control module 210 based on the programmable schedule 250.
In some embodiments, the interview scheduling block 325 includes interview questions that require an affirmative (e.g, “yes”) or negative (e.g., “no”) user response. In addition, the interview questions can solicit information from the user regarding the grouping of the controller set points entered or the temporal relationship of the controller set points. For example, the interview question may ask “Do you want the schedule to apply to every day of the week?”, requiring the user to respond with a “YES” or “NO” answer. The interview scheduling block 325 can include questions that are natural language questions such as, for example, phrases that can have one, two, three, four, five, six, or seven or more words.
In an illustrative embodiment, interview scheduling block 325 may also provide interview questions that require a numerical user response. These interview questions can solicit information from the user regarding the specific time and temperature set points for each grouping of controller set points solicited by the interview block 325 described above. The interview block 325 can provide a question such as, for example, “What is a comfortable sleeping temperature in the winter?”, requiring the user to respond with a numerical temperature answer. The interview scheduling block 325 can include questions that are natural language questions such as, for example, phrases that can have one, two, three, four, five, six, or seven or more words.
In the illustrative embodiment, the interview scheduling block 325 can also provide one or more interview questions related to, for example, which weekdays will have the same schedule?, when a first person wakes up?, when a last person goes to sleep?, when a last person leaves during the day?, when a first person arrives home?, what a comfortable temperature is when heat is on?, what a comfortable temperature is when air conditioning is on?, what a comfortable sleeping temperature is in the summer?, or what a comfortable sleeping temperature is in the winter?
The response translator 360 can translate the user responses to create appropriate schedule parameters 370 that help define the schedule of the controller. That is, the response translator 360 applies the user responses to one or more interview questions to establish the controller schedule. For example, the response translator 360 can take an affirmative user response to the interview question, “Do you want the same schedule for Saturday and Sunday?” and correlate with the interview question, “What temperature do you like when the heat is on?” to establish the schedule parameters for the heating temperature during at least selected periods on Saturday and Sunday.
Alternatively, or in addition, the interview scheduling block 325 may provide one or more interview questions that provide a plurality of predetermined answers or responses (e.g., multiple choice format) where the user selects an answer or response. For example, the interview question may provide a question such as, “What type of schedule do you desire?” In this illustrative embodiment, a series of predetermined responses or answers can be provided such as, “Every day of the week is the same,” “Weekdays are the same and Saturday/Sunday is the same,” “Weekday are the same and Saturday/Sunday is different,” “Each Weekday is different and Saturday/Sunday is the same,” and “Each day of the week is different.”
In the illustrative embodiment, the interview question generator 435 provides interview questions, such as those described above, to the user interface 420. The user interface 420 can be any form of user interface such as, for example, a physical interface including a touchscreen, an LCD with buttons, and/or an aural interface including a speaker and microphone, or any other suitable user interface. A user can activate the interview question generator 435 by any suitable mechanism, such as by pressing a mechanical schedule button on the controller, touching an appropriate region of a touchscreen, voice activation, etc. Alternatively, or in addition, the controller 410 may activate the interview question generator 425 on its own, such as when it believes additional scheduling information is needed or might otherwise be desired. In response to questions posed by the interview question generator 425, the user can enter one or more user responses into the user interface 420. The response acceptor 440 accepts the user responses and provides the response to the response translator 460. The response translator 460 provides a translated response to a programmable schedule 470. In some embodiments, the programmable schedule 470 has a number of time and temperature set points that can be entered or modified by the response translator 470. Once the schedule is built and/or modified a control signal 465 is generated by the control module 410 based on the programmable schedule 470.
Interview questions 425 are posed to the user. As shown in the illustrative example: an interview question 425 of “Same schedule for Saturday and Sunday?” elicits an user response 440 of “YES”; an interview question 425 of “For the weekend, is someone home all day?” elicits an user response 440 of “YES”; an interview question 425 of “What time does the first person wake up?” elicits an user response 440 of “7:00 a.m.”; an interview question 425 of “What time does the last person go to sleep?” elicits an user response 440 of “10:00 p.m.”; an interview question 425 of “What temperature is comfortable when the heat is on?” elicits an user response 440 of “72° F.”; an interview question 425 of “What temperature is comfortable when the air conditioning is on?” elicits an user response 440 of “68° F.”; an interview question 425 of “What is a comfortable sleeping temperature in summer?” elicits an user response 440 of “67° F.”; and an interview question 425 of “What is a comfortable sleeping temperature in winter?” elicits an user response 440 of “65° F.”.
In the illustrative embodiment, the response translator 460 accepts the user responses provided in block 440. The response translator 460 then builds and/or modifies the programmable schedule 470. In the illustrative embodiment, each cell 471, 472, 473, 474 includes a start time, a heat temperature and a cool temperature. The Saturday wake cell 471 and the Sunday wake cell 472 has a start time of 7:00 a.m., a heat temperature of 72° F., and a cool temperature of 68° F., all of the times and temperatures are provided by the response translator. The Saturday sleep cell 473 and the Sunday sleep cell 474 has a start time of 10:00 p.m., a heat temperature of 65° F., and a cool temperature of 67° F., all of the times and temperatures are provided by the response translator.
In this illustrative embodiment, the response translator 460 takes a plurality of user responses 440 to the interview questions 425 and builds and/or modifies a plurality of schedule parameters. The Saturday and Sunday Leave and Return cells 475, 476, 477, and 478 are ignored and/or zeroed out by the response translator 460 since they are not required based on the user responses 425 for this example.
The sufficient information block 560 can, for example, help ensure that a sufficient number of schedule parameters are defined, such as, for example, a start time, a heating temperature and a cooling temperature for a particular time period such as, for example, a specific day or group of days wake period, leave period, return period and/or sleep period, as shown in
In some embodiments, the interview scheduling block 525 provides a number of predetermined interview questions in a predetermined sequential order. The number of questions or queries may be adapted to collect information from the user responses to generate at least a portion of the schedule parameters.
Like above, the interview scheduling block 525 can include interview questions that require an affirmative (e.g., “yes”) or negative (e.g., “no”) user response. For example, interview scheduling block 525 can provide interview questions solicit information from the user regarding the grouping of the controller set points entered or the temporal relationship of the controller set points such as, for example, “Do you want the schedule to apply to every day of the week?”, requiring the user to respond with a “YES” or “NO” answer. The interview scheduling block 525 can include questions that are natural language questions which can be phrases that have one, two, three, four, five, six, or seven or more words in length.
Alternatively or in addition, interview scheduling block 525 can provide interview questions that require a numerical user response. For example, these interview questions can solicit information from the user regarding the specific time and temperature set points for each grouping of controller set points solicited by the interview block 525 described above. The interview block 525 can provide a question such as, for example, “What is a comfortable sleeping temperature in the winter?”, requiring the user to respond with a numerical temperature answer. Again, the interview scheduling block 525 can include questions that are natural language questions that can be phrases which can be one, two, three, four, five, six, seven or more words, although this is not required in all embodiments.
The interview scheduling block 525 may also provide one or more interview questions about, which weekdays will have a same schedule?, when a first person wakes up?, when a last person goes to sleep?, when a last person leaves during the day?, when a first person arrives home?, what a comfortable temperature is when heat is on?, what a comfortable temperature is when air conditioning is on?, what a comfortable sleeping temperature is in the summer?, or what a comfortable sleeping temperature is in the winter?
Alternatively, or in addition, the interview scheduling block 525 may provide one or more interview questions that provide a plurality of predetermined answers or responses (e.g., multiple choice format) where the user selects an answer or response. For example, the interview question may provide a question such as, “What type of schedule do you desire?” In this illustrative embodiment, a series of predetermined responses or answers can be provided such as, “Every day of the week is the same,” “Weekdays are the same and Saturday/Sunday is the same,” “Weekday are the same and Saturday/Sunday is different,” “Each Weekday is different and Saturday/Sunday is the same,” and “Each day of the week is different.”
In the illustrative embodiment, the interview question generator 625 provides interview questions, such as those described above, to the user interface 620. The user interface 620 can be any form of user interface such as, for example, a physical interface including a touchscreen, an LCD with buttons, an aural interface including a speaker and microphone, or any other suitable user interface. A user can activate the interview question generator 625 by any suitable mechanism, such as by pressing a schedule button on a touchscreen of the user interface 620. Alternatively, or in addition, the controller 610 may activate the interview question generator 625 on its own, such as when it believes additional scheduling information is needed or might otherwise be desired. In response to the questions posed by the interview question generator 625, the user can enter one or more user responses into the user interface 620. The response acceptor 640 accepts the user responses and provides the responses to the programmable schedule 650 if it determines that sufficient information has been provided by the user responses to establish a program schedule. If not, the response acceptor 640 instructs the interview question generator 625 to provide another interview question to the user via the user interface 620. Once the response acceptor 640 determines that sufficient information has been provided by the user to establish a program schedule 650 the program schedule 650 is built and/or modified. In some embodiments, the programmable schedule 650 has a number of time and temperature set points that can be entered or modified by the response acceptor 640. Once the programmable schedule 650 is built and/or modified, a control signal 660 is generated by the control module 610 based on the programmable schedule 650.
The program can begin by asking whether the user wants the same schedule to be used for every day of the week, as shown at block 720. If the user responds with a “YES” response, then the program can move to ask context questions for that group of days, as shown at block 725, which may set the schedule for the week assuming the same schedule for every 24 hour period or day. If the user responds with a “NO” response, the program may ask the user if the same schedule applies to both weekend days, Saturday and Sunday, as shown at block 730. If the user responds with a “YES” response, then the program can ask if the user wants two schedules, one for weekdays and one for weekends, as shown at block 735. A “YES response to block 735 can move the program to asking context questions for a weekend group of days and a weekdays group of days, as shown at block 725, to set the schedule for the week assuming a first schedule for weekend days and a second schedule for weekdays. A “NO” response to block 730 can cause the program to ask whether the user wants three schedules including a weekday schedule, a Saturday schedule, and a Sunday schedule, as shown at block 740. A “YES” response to block 740 moves the program to asking context questions for a week day group of days schedule, a Saturday schedule and a Sunday schedule, as shown at block 725, to set the schedule for the week assuming a first schedule for weekdays, and a second schedule for Saturday and a third schedule for Sundays. A “NO” response to either block 740 or block 735 moves the program to asking the user to group each day of the seven days of the week into similar schedule groupings until all days are assigned to one group, as shown at block 750. The program can ask if all days are assigned at block 755, with a “NO” response returning the user to block 750 to assign a non-assigned day or days until all days have been assigned. Once all days have been assigned to a group, the program moves to asking context questions for each group of days schedule, as shown at block 725, to set the schedule for the each grouping of days assuming a first schedule for a first group, a second schedule for a second group, a third schedule for a third group and so on until all groupings of days are scheduled.
The program 700 can ask a variety of context sensitive question to determine the desired schedule for each grouping of days identified by the program 700 above. For example, and as shown in
The program 700 can then request information from the user regarding comfortable awake, sleeping and away temperatures. For example, and referring to
In some embodiments, the program 700 can allow the user to request a schedule review at block 795, which can allow the user to review the built or modified schedule, as shown at block 796. If the user does not wish to review the schedule or when the user is done reviewing the schedule, the program returns to normal thermostat operation block 710 operation under the newly built or modified schedule.
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
At
The present invention should not be considered limited to the particular examples described above, but rather should be understood to cover all aspects of the invention as fairly set out in the attached claims. Various modifications, equivalent processes, as well as numerous structures to which the present invention can be applicable will be readily apparent to those of skill in the art to which the present invention is directed upon review of the instant specification.
Number | Name | Date | Kind |
---|---|---|---|
4079366 | Wong | Mar 1978 | A |
4174807 | Smith et al. | Nov 1979 | A |
4206872 | Levine | Jun 1980 | A |
4224615 | Penz | Sep 1980 | A |
4264034 | Hyltin et al. | Apr 1981 | A |
4298946 | Hartsell et al. | Nov 1981 | A |
4308991 | Peinetti et al. | Jan 1982 | A |
4337822 | Hyltin et al. | Jul 1982 | A |
4382544 | Stewart | May 1983 | A |
4386649 | Hines et al. | Jun 1983 | A |
4388692 | Jones et al. | Jun 1983 | A |
4431134 | Hendricks et al. | Feb 1984 | A |
4442972 | Sahay et al. | Apr 1984 | A |
4446913 | Krocker | May 1984 | A |
4479604 | Didner | Oct 1984 | A |
4506827 | Jamieson et al. | Mar 1985 | A |
4606401 | Levine et al. | Aug 1986 | A |
4621336 | Brown | Nov 1986 | A |
4622544 | Bially et al. | Nov 1986 | A |
4717333 | Carignan | Jan 1988 | A |
4725001 | Carney et al. | Feb 1988 | A |
4819714 | Otsuka et al. | Apr 1989 | A |
4837731 | Levine et al. | Jun 1989 | A |
4881686 | Mehta | Nov 1989 | A |
4918439 | Wozniak et al. | Apr 1990 | A |
4948040 | Kobayashi et al. | Aug 1990 | A |
4992779 | Sugino et al. | Feb 1991 | A |
4997029 | Otsuka et al. | Mar 1991 | A |
5012973 | Dick et al. | May 1991 | A |
5038851 | Metha | Aug 1991 | A |
5053752 | Epstein et al. | Oct 1991 | A |
5065813 | Berkeley et al. | Nov 1991 | A |
5086385 | Launey et al. | Feb 1992 | A |
5088645 | Bell | Feb 1992 | A |
5140310 | DeLuca et al. | Aug 1992 | A |
5161606 | Berkeley et al. | Nov 1992 | A |
5170935 | Federspiel et al. | Dec 1992 | A |
5181653 | Foster et al. | Jan 1993 | A |
5230482 | Ratz et al. | Jul 1993 | A |
5238184 | Adams | Aug 1993 | A |
5251813 | Kniepkamp | Oct 1993 | A |
5259445 | Pratt et al. | Nov 1993 | A |
5329991 | Metha et al. | Jul 1994 | A |
5348078 | Dushane et al. | Sep 1994 | A |
5386577 | Zenda | Jan 1995 | A |
5482209 | Cochran et al. | Jan 1996 | A |
5526422 | Keen | Jun 1996 | A |
5537106 | Mitcuhashi | Jul 1996 | A |
5566879 | Longtin | Oct 1996 | A |
5570837 | Brown et al. | Nov 1996 | A |
5673850 | Uptegraph | Oct 1997 | A |
5761083 | Brown et al. | Jun 1998 | A |
5782296 | Metha | Jul 1998 | A |
5818428 | Eisenbrandt et al. | Oct 1998 | A |
5873519 | Beilfuss | Feb 1999 | A |
5877957 | Bennett | Mar 1999 | A |
5886697 | Naughton et al. | Mar 1999 | A |
5902183 | D'Souza | May 1999 | A |
5937942 | Bias et al. | Aug 1999 | A |
5947372 | Tiernan | Sep 1999 | A |
6020881 | Naughton et al. | Feb 2000 | A |
6032867 | Dushane et al. | Mar 2000 | A |
6059195 | Adams et al. | May 2000 | A |
6081197 | Garrick et al. | Jun 2000 | A |
6121875 | Hamm et al. | Sep 2000 | A |
6140987 | Stein et al. | Oct 2000 | A |
6192282 | Smith et al. | Feb 2001 | B1 |
6196467 | Dushane et al. | Mar 2001 | B1 |
6208331 | Singh et al. | Mar 2001 | B1 |
6236326 | Murphy | May 2001 | B1 |
6285912 | Ellison et al. | Sep 2001 | B1 |
6290140 | Pesko et al. | Sep 2001 | B1 |
6315211 | Sartain et al. | Nov 2001 | B1 |
6318639 | Toth | Nov 2001 | B1 |
6330806 | Beaverson et al. | Dec 2001 | B1 |
6351693 | Monie et al. | Feb 2002 | B1 |
6344861 | Naughton et al. | Mar 2002 | B1 |
6398118 | Rosen et al. | Jun 2002 | B1 |
6478233 | Shah | Nov 2002 | B1 |
6502758 | Cottrell | Jan 2003 | B2 |
6518957 | Lehtinen et al. | Feb 2003 | B1 |
6578770 | Rosen | Jun 2003 | B1 |
6580950 | Johnson et al. | Jun 2003 | B1 |
6581846 | Rosen | Jun 2003 | B1 |
6595430 | Shah | Jul 2003 | B1 |
6619555 | Rosen | Sep 2003 | B2 |
6621507 | Shah | Sep 2003 | B1 |
6786421 | Rosen | Sep 2004 | B2 |
6824069 | Rosen | Nov 2004 | B2 |
6967565 | Lingemann | Nov 2005 | B2 |
20010029585 | Simon et al. | Oct 2001 | A1 |
20010042684 | Essalik et al. | Nov 2001 | A1 |
20010052459 | Essalik et al. | Dec 2001 | A1 |
20020005435 | Cottrell | Jan 2002 | A1 |
20020022991 | Sharood et al. | Feb 2002 | A1 |
20020060701 | Naughton et al. | May 2002 | A1 |
20020092779 | Essalik et al. | Jul 2002 | A1 |
20030034897 | Shamoon et al. | Feb 2003 | A1 |
20030034898 | Shamoon et al. | Feb 2003 | A1 |
20030121652 | Carey et al. | Jul 2003 | A1 |
20030123224 | LaCroix et al. | Jul 2003 | A1 |
20030142121 | Rosen | Jul 2003 | A1 |
20030150926 | Rosen | Aug 2003 | A1 |
20030150927 | Rosen | Aug 2003 | A1 |
20040074978 | Rosen | Apr 2004 | A1 |
20040193324 | Hoog et al. | Sep 2004 | A1 |
20040245352 | Smith | Dec 2004 | A1 |
Number | Date | Country |
---|---|---|
3334117.6 | Apr 1985 | DE |
0678204 | Mar 2000 | EP |
0985994 | Mar 2000 | EP |
1074009 | Jul 2001 | EP |
WO 9711448 | Mar 1997 | WO |
WO 9739392 | Oct 1997 | WO |
WO 0043870 | Jul 2000 | WO |
WO 0152515 | Jul 2001 | WO |
WO 0179952 | Oct 2001 | WO |
WO 0193779 | Dec 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20050119771 A1 | Jun 2005 | US |