The present invention generally relates to calendar, scheduling and time management systems. More particularly, the present invention relates to a method and system for improved electronic task management.
With the advent of the computer age, computer and software users have grown accustomed to user-friendly software applications that help them write, calculate, organize, prepare presentations, send and receive electronic mail, make music, and the like. For example, electronic mail systems allow users to send, receive, respond to and store a variety of mail messages and related information. Electronic calendar systems allow users to store, organize and view meeting dates, appointments and tasks. Electronic task management applications allow users to store, organize and view a variety of tasks that a use must complete or that a user desires to complete according to various time schedules.
However, even with the available functionality of such systems, many users of modern electronic calendar and task management applications still resort to paper task or “to-do” lists on which they write tasks they need to perform or upcoming events, such as appointments or meetings. One reason users resort to such manual systems is because of a real or perceived difficulty associated with inputting tasks and related information into an electronic task management application. For example, typical electronic task management applications require users to launch a task input user interface followed by input of information associated with a task or upcoming event.
Accordingly, there is a need for an improved task input and management method and system that allows users to easily create tasks and input information associated with created tasks. It is with respect to these and other considerations that the present invention has been made.
Embodiments of the present invention solve the above and other problems by providing an improved method and system for identifying data items as task items and for inputting information associated such task items according to an electronic task management application or system. Generally described, according to aspects of the invention, any data item may be annotated (flagged) with information that causes the data item to be recognized as a task item by applications that aggregate, display or otherwise use task and task-like items. Upon flagging an individual data item, the flagged data item is then populated into and exposed by one or more applications used for displaying tasks such as a tasks application, calendar application, or electronic to-do list application.
According to aspects of the invention, a quick flag box is displayed adjacent to every electronic correspondence item that may be flagged as a task. Upon selection of the quick flag box for any electronic correspondence item, a property is set for the item that causes the item to be populated into and displayed by applications that display tasks, such as calendar applications, tasks applications, or electronic to-do lists applications. According to other aspects, additional properties may be applied to a flagged item including start dates and task categories. Additional properties may be applied to a flagged item from a launched menu of task properties that is contextually related to the selected flagged item. In addition, properties may be applied to individual task items from top-level actions menus and mail inspector applications.
These and other features and advantages, which characterize the present invention, will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
As briefly described above, embodiments of the present invention are directed to an improved task input and management method and system that allows users to easily mark data items as tasks and input information associated with marked data items. In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of the present invention and the exemplary operating environment will be described.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Turning now to
The mass storage device 14 is connected to the CPU 4 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media, provide non-volatile storage for the personal computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the personal computer 2.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
According to various embodiments of the invention, the personal computer 2 may operate in a networked environment using logical connections to remote computers through a TCP/IP network 18, such as the Internet. The personal computer 2 may connect to the TCP/IP network 18 through a network interface unit 20 connected to the bus 12. It should be appreciated that the network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The personal computer 2 may also include an input/output controller 22 for receiving and processing input from a number of devices, including a keyboard or mouse (not shown). Similarly, an input/output controller 22 may provide output to a display screen, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 8 of the personal computer 2, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as the WINDOWS operating systems from Microsoft Corporation of Redmond, Wash. The mass storage device 14 and RAM 8 may also store one or more application programs. In particular, the mass storage device 14 and RAM 8 may store an application 105 for providing a variety of functionalities to a user. For instance, the application 105 may comprise many types of programs such as a word processing application program, a spreadsheet application, a desktop publishing, and the like. According to an embodiment of the present invention, the application 105 comprises a multiple functionality software application for providing a user calendar functionality, electronic tasks functionality, electronic mail functionality, contacts information functionality, electronic notes functionality, electronic journal functionality and the like. Some of the individual program modules comprising the multiple functionality application 105 include a calendar application 125, an electronic mail application 130, a contacts application 135, a tasks application 140, a notes application 145 and a journal application (not shown). An example of such a multiple functionality application 105 is OUTLOOK® manufactured by Microsoft Corporation.
The user interface 200 illustrated in
Along the lower left-hand corner of the user interface 200 is an application selection pane 225 containing selectable functionality controls for selecting other types of functionality provided by the multiple functionality software application 105 (described above) through which the user's electronic mail application is provided. For example, the display of the electronic mail user interface 200 is in response to selection of the “Mail” control. If the user wishes to launch a user interface associated with a tasks application 140, the user may select the “Tasks” control to launch the functionality of the tasks application 140 including presentation of a user interface 200 associated with the tasks application. Likewise, the user may select the “Contacts” control to launch the functionality of a contacts application 135 and an associated user interface 200 for displaying information and functionality for a contacts application 135.
Referring still to
Referring still to
A pop-up context menu 265 is illustrated for applying one or more properties, for example, task start dates and task categories, to a selected data item so that the flagged data item becomes a task item bearing the applied properties. Once a data item is flagged as a task, according to embodiments of the present invention, the properties applied to the data item, for example, start date and task category, will dictate the position of the corresponding task item in a task list provided by a tasks application 140 or provided by a task list contained in a To-Do bar 240. For example, if a given data item is flagged with a start date property of “today” and a category of “work project,” a corresponding task may be displayed in a user's task list along with other tasks having a start date of “today,” and the task will bear a category icon indicating that the task is associated with the “work project” category. Thus, the user is able to automatically mark a data item as a task without the need for launching a user interface, completing a task entry form, and submitting the form to a tasks application 140 for creation and storage of the desired task item.
Individual data items are flagged as tasks using a task flagging control (hereinafter referred to as a “quick flag box”) that is displayed to the right of every data item that may be flagged according to embodiments of the present invention. Referring still to
A second property that may be applied to a created task is a category for the created task. A number of task categories that are system-defined or user-defined may be applied to individual tasks. For example, a user may define a first task category associated with a given work project. A second task category may be assigned to a second given work project. A third task category may be assigned to a personal project. A fourth task category may be assigned to a vacation project, and so on. As should be appreciated, the example task categories described herein are not limiting of the great variety of task categories that may be designed by a user or that may be system designed. According to embodiments of the present invention, a task color is assigned to each task category to distinguish one category from another. Accordingly, in addition to applying a timing property to a selected data item, a category property may also be applied to the selected data item to categorize the corresponding task item.
As illustrated in
According to an embodiment of the present invention, a tool-tip box may be provided that may deploy when a user hovers a mouse cursor over a given quick flag box 250, 270, 275. The tool-tip box may provide information to a user as to how to utilize the quick flag box. For example, a tool tip may instruct a user to right-click on a given quick flag box to launch a context menu 265 for applying one or more task flagging properties to a task created from the associated data item. According to an embodiment of the present invention, if a given data item bears other informational icons, for example reminder icons, a corresponding task item will also bear the additional informational icons.
As briefly described above, according to embodiments of the present invention, any items that appear in a mail folder of an electronic mail application 130 may be flagged for creation of a task. Such data items include electronic mail messages, meeting requests, meeting responses, task requests, and task responses. Flagging a data item for creation of a task causes the multiple functionality application 105 or the individual electronic mail application 130 to set special properties on the flagged data item. Setting properties on the flagged data item will cause a data item to appear in a tasks application 140 user interface for showing task items or in the To-Do bar 240 illustrated in
Having described the task flagging functionality according to embodiments of the present invention with respect to
Referring back to
Referring to
With the context menu 265, a user may customize start date or due date properties and category properties for the created task. For example, if a user desires a start date of this week, the user may select the “This Week” control 330 from the context menu 265 to apply the associated start date property to the new task. Selection of the “This Week” control 330 also populates the quick flag box with an associated single flag icon 320 as illustrated for the quick flag box 275.
If the user desires to assign a particular task category to the created task item, the user may select one of the category controls, for example, the “Smith Project” control 340, the “London Trip” control 345, or the “IT Upgrade” category. The bottom portion of the context menu 265 shows the top five most frequently used category names in order of frequency of use with the associated color controls 340, 345. In addition, a user may assign multiple categories to a selected item. For example, the category “Carson project” illustrated in the context menu 265 is associated with multiple categories, and accordingly, the color applied to the quick flag box upon application of the “Carson project” category is comprised of multiple colors associated with the multiple categories assigned to the associated data item and new task item. As should be understood, the example task categories illustrated in the context menu 265 are for purposes of example only and are not restrictive of the many different task categories that may be system-defined or that may be defined by an individual user. In order to review additional task categories, the “All Categories” control 350 may be selected to cause a fly-out menu to be displayed showing all additional task categories that may be applied to a given task item.
Additional properties that may be applied to a task item include the “Show Reminder” property 335 and a “Flag Complete” property. Additionally, as set forth above, a “Set Defaults” control 360 is provided in the context menu 265 to set certain default properties that will be applied to a task item automatically upon selection of the quick flag box associated with a given data item. For example, a default task category may be set which will then be automatically applied upon initial selection of a quick flag box for creation of a task item. However, a user may always change the default task category to a different task category by selection of a desired task category from the context menu 265. Similarly, a default start date or due date property may be selected for all created task items, but may be modified if desired. A “Clear Flag” property may also be set on a data item to clear the data item of previously set task properties such that the data item will no longer be recognized as a task item.
For application of two properties to a selected data item and corresponding task item with a single user action (e.g., mouse click), a radial context menu may be provided to allow the user to select a desired start date or due date and task category simultaneously by selecting a given location in the radial context menu. For a detailed description of a radial context menu for use in accordance with embodiments of the present invention, see U.S. patent application, entitled “Two-dimensional Radial User Interface For Computer Software Applications,” which is incorporated herein by reference as if fully set out herein.
In addition to the foregoing, properties may also be applied to a selected data item and corresponding new task item by selecting a top-level actions menu associated with the software application user interface in use by the user. For example, the user interface 200 illustrated in
Referring to
Referring still to
According to an embodiment of the invention, a given data item may also be flagged as a new task item by dragging the data item to the task list or date picker control contained in the To-Do bar 240, illustrated in
According to embodiments of the present invention, a user may re-flag an item previously flagged as a task item. If the user applies a flag to an item and then flags the item again, all relevant properties, for example, start date and task category, are reset according to the second flagging of the item unless the user has selected a “Specific Date And Time” option. If the user has selected a “Specific Date And Time” option, then re-flagging a previously flagged item only changes the start date of the flagged item according to the date on which the item is re-flagged.
Referring to
As described above, with reference to
As described herein, methods and systems provide for automatically marking data items as for recognition as task items by selection of a quick flag box associated with individual data items. By applying one or more task properties to individual data items according to embodiments of the present invention, a user is able to create a task item by “touching” on a selected data item. Thus, the user avoids the potentially cumbersome and time-consuming process of launching a task item creation user interface to complete information associated with a desired task item. Through the use of quickly and efficiently deployed context menus associated with selected data items, a user may apply important information such as start times and task categories to selected data items and corresponding task item. It will be apparent to those skilled in the art that various modifications or variations may be made in the present invention without departing from the scope or spirit of the invention. Other embodiments of the present invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
5202828 | Vertelney et al. | Apr 1993 | A |
5493692 | Theimer et al. | Feb 1996 | A |
5530794 | Luebbert | Jun 1996 | A |
5537628 | Luebbert | Jul 1996 | A |
5544321 | Theimer et al. | Aug 1996 | A |
5555376 | Theimer et al. | Sep 1996 | A |
5563996 | Tchao | Oct 1996 | A |
5596656 | Goldberg | Jan 1997 | A |
5603054 | Theimer et al. | Feb 1997 | A |
5611050 | Theimer et al. | Mar 1997 | A |
5625783 | Ezekiel et al. | Apr 1997 | A |
5625810 | Kurosu et al. | Apr 1997 | A |
5701424 | Atkinson | Dec 1997 | A |
5724595 | Gentner | Mar 1998 | A |
5734915 | Roewer | Mar 1998 | A |
5752254 | Sakairi | May 1998 | A |
5760768 | Gram | Jun 1998 | A |
5761683 | Logan et al. | Jun 1998 | A |
5765156 | Guzak et al. | Jun 1998 | A |
5778346 | Frid-Nielsen et al. | Jul 1998 | A |
5781192 | Kodimer | Jul 1998 | A |
5798760 | Vayda et al. | Aug 1998 | A |
5801693 | Bailey | Sep 1998 | A |
5812865 | Theimer et al. | Sep 1998 | A |
5838321 | Wolf | Nov 1998 | A |
5855006 | Huemoeller et al. | Dec 1998 | A |
5870552 | Dozier et al. | Feb 1999 | A |
5884306 | Bliss et al. | Mar 1999 | A |
5898434 | Small et al. | Apr 1999 | A |
5924099 | Guzak et al. | Jul 1999 | A |
5940078 | Nagarajayya et al. | Aug 1999 | A |
5958008 | Pogrebisky et al. | Sep 1999 | A |
5970455 | Wilcox et al. | Oct 1999 | A |
5970466 | Detjen et al. | Oct 1999 | A |
5999938 | Bliss et al. | Dec 1999 | A |
6002402 | Schacher | Dec 1999 | A |
6025837 | Matthews, III et al. | Feb 2000 | A |
6034686 | Lamb et al. | Mar 2000 | A |
6057845 | Dupouy | May 2000 | A |
6065012 | Balsara et al. | May 2000 | A |
6177939 | Blish et al. | Jan 2001 | B1 |
6233591 | Sherman et al. | May 2001 | B1 |
6249283 | Ur | Jun 2001 | B1 |
6262724 | Crow et al. | Jul 2001 | B1 |
6269389 | Ashe | Jul 2001 | B1 |
6275940 | Edwards et al. | Aug 2001 | B1 |
6278450 | Arcuri et al. | Aug 2001 | B1 |
6282548 | Burner et al. | Aug 2001 | B1 |
6308201 | Pivowar et al. | Oct 2001 | B1 |
6309305 | Kraft | Oct 2001 | B1 |
6310622 | Asente | Oct 2001 | B1 |
6310634 | Bodnar et al. | Oct 2001 | B1 |
6321242 | Fogg et al. | Nov 2001 | B1 |
6389434 | Rivette et al. | May 2002 | B1 |
6411311 | Rich et al. | Jun 2002 | B1 |
6429882 | Abdelnur et al. | Aug 2002 | B1 |
6433801 | Moon et al. | Aug 2002 | B1 |
6448987 | Easty et al. | Sep 2002 | B1 |
6459441 | Perroux et al. | Oct 2002 | B1 |
6466232 | Newell et al. | Oct 2002 | B1 |
6490634 | Coiner | Dec 2002 | B2 |
6499041 | Breslau et al. | Dec 2002 | B1 |
6513046 | Abbott, III et al. | Jan 2003 | B1 |
6549219 | Selker | Apr 2003 | B2 |
6549915 | Abbott, III et al. | Apr 2003 | B2 |
6572660 | Okamoto | Jun 2003 | B1 |
6606653 | Ackermann et al. | Aug 2003 | B1 |
6618732 | White | Sep 2003 | B1 |
6651059 | Sundaresan et al. | Nov 2003 | B1 |
6686938 | Jobs et al. | Feb 2004 | B1 |
6694087 | Weaver | Feb 2004 | B1 |
6704770 | Ramakesavan | Mar 2004 | B1 |
6708202 | Shuman et al. | Mar 2004 | B1 |
6735247 | Lundby | May 2004 | B2 |
6747675 | Abbott et al. | Jun 2004 | B1 |
6751777 | Bates et al. | Jun 2004 | B2 |
6763496 | Hennings et al. | Jul 2004 | B1 |
6789228 | Merril et al. | Sep 2004 | B1 |
6791580 | Abbott et al. | Sep 2004 | B1 |
6801223 | Abbott et al. | Oct 2004 | B1 |
6802041 | Rehm | Oct 2004 | B1 |
6810405 | LaRue et al. | Oct 2004 | B1 |
6812937 | Abbott et al. | Nov 2004 | B1 |
6826729 | Giesen et al. | Nov 2004 | B1 |
6836270 | Du | Dec 2004 | B2 |
6842877 | Robarts et al. | Jan 2005 | B2 |
6848075 | Becker et al. | Jan 2005 | B1 |
6918091 | Leavitt et al. | Jul 2005 | B2 |
6924797 | MacPhail | Aug 2005 | B1 |
6925496 | Ingram et al. | Aug 2005 | B1 |
6944821 | Bates et al. | Sep 2005 | B1 |
6970867 | Hsu et al. | Nov 2005 | B1 |
7032210 | Alloing et al. | Apr 2006 | B2 |
7039234 | Geidl et al. | May 2006 | B2 |
7114128 | Koppolu et al. | Sep 2006 | B2 |
7143338 | Bauchot et al. | Nov 2006 | B2 |
7165098 | Boyer et al. | Jan 2007 | B1 |
7184955 | Obrador et al. | Feb 2007 | B2 |
7185050 | Eld et al. | Feb 2007 | B2 |
7188073 | Tam et al. | Mar 2007 | B1 |
7210107 | Wecker et al. | Apr 2007 | B2 |
7254785 | Reed | Aug 2007 | B2 |
7406501 | Szeto et al. | Jul 2008 | B2 |
7454763 | Veselova et al. | Nov 2008 | B2 |
7460713 | Lapstun et al. | Dec 2008 | B2 |
7555707 | Labarge et al. | Jun 2009 | B1 |
7707518 | Veselova | Apr 2010 | B2 |
7712049 | Williams et al. | May 2010 | B2 |
20010032214 | Bauchot et al. | Oct 2001 | A1 |
20010040590 | Abbott et al. | Nov 2001 | A1 |
20010040591 | Abbott et al. | Nov 2001 | A1 |
20010043231 | Abbott et al. | Nov 2001 | A1 |
20010043232 | Abbott et al. | Nov 2001 | A1 |
20020026478 | Rodgers et al. | Feb 2002 | A1 |
20020032689 | Abbott, III et al. | Mar 2002 | A1 |
20020044152 | Abbott, III et al. | Apr 2002 | A1 |
20020049785 | Bauchot | Apr 2002 | A1 |
20020052930 | Abbott et al. | May 2002 | A1 |
20020052963 | Abbott et al. | May 2002 | A1 |
20020054130 | Abbott, III et al. | May 2002 | A1 |
20020054174 | Abbott et al. | May 2002 | A1 |
20020078180 | Miyazawa | Jun 2002 | A1 |
20020078204 | Newell et al. | Jun 2002 | A1 |
20020080155 | Abbott et al. | Jun 2002 | A1 |
20020080156 | Abbott et al. | Jun 2002 | A1 |
20020083025 | Robarts et al. | Jun 2002 | A1 |
20020083158 | Abbott et al. | Jun 2002 | A1 |
20020087525 | Abbott et al. | Jul 2002 | A1 |
20020087534 | Blackman et al. | Jul 2002 | A1 |
20020087642 | Wei et al. | Jul 2002 | A1 |
20020088008 | Markel | Jul 2002 | A1 |
20020089540 | Geier et al. | Jul 2002 | A1 |
20020091739 | Ferlitsch et al. | Jul 2002 | A1 |
20020099777 | Gupta et al. | Jul 2002 | A1 |
20020099817 | Abbott et al. | Jul 2002 | A1 |
20020120697 | Generous et al. | Aug 2002 | A1 |
20020133520 | Tanner | Sep 2002 | A1 |
20020138582 | Chandra et al. | Sep 2002 | A1 |
20020140731 | Subramaniam et al. | Oct 2002 | A1 |
20020161800 | Eld et al. | Oct 2002 | A1 |
20020161804 | Chiu et al. | Oct 2002 | A1 |
20020184264 | Berg et al. | Dec 2002 | A1 |
20020196293 | Suppan et al. | Dec 2002 | A1 |
20030013483 | Ausems et al. | Jan 2003 | A1 |
20030014395 | Ruvolo et al. | Jan 2003 | A1 |
20030014490 | Bates et al. | Jan 2003 | A1 |
20030020749 | Abu-Hakima et al. | Jan 2003 | A1 |
20030023755 | Harris et al. | Jan 2003 | A1 |
20030046401 | Abbott et al. | Mar 2003 | A1 |
20030050927 | Hussam | Mar 2003 | A1 |
20030069877 | Grefenstette et al. | Apr 2003 | A1 |
20030070143 | Maslov | Apr 2003 | A1 |
20030076352 | Uhlig et al. | Apr 2003 | A1 |
20030084104 | Salem et al. | May 2003 | A1 |
20030088534 | Kalantar et al. | May 2003 | A1 |
20030097361 | Huang et al. | May 2003 | A1 |
20030100999 | Markowitz | May 2003 | A1 |
20030135565 | Estrada | Jul 2003 | A1 |
20030154254 | Awasthi | Aug 2003 | A1 |
20030154476 | Abbott, III et al. | Aug 2003 | A1 |
20030172168 | Mak et al. | Sep 2003 | A1 |
20030172384 | Comps | Sep 2003 | A1 |
20030182450 | Ong et al. | Sep 2003 | A1 |
20030187930 | Ghaffar et al. | Oct 2003 | A1 |
20030196196 | Nylander et al. | Oct 2003 | A1 |
20030212680 | Bates et al. | Nov 2003 | A1 |
20030222899 | Alvesalo | Dec 2003 | A1 |
20040001093 | Sellers et al. | Jan 2004 | A1 |
20040039779 | Amstrong et al. | Feb 2004 | A1 |
20040054736 | Daniell et al. | Mar 2004 | A1 |
20040063400 | Kim | Apr 2004 | A1 |
20040073679 | Martens et al. | Apr 2004 | A1 |
20040098398 | Ahn et al. | May 2004 | A1 |
20040109033 | Vienneau et al. | Jun 2004 | A1 |
20040128613 | Sinisi | Jul 2004 | A1 |
20040153445 | Horvitz et al. | Aug 2004 | A1 |
20040158611 | Daniell et al. | Aug 2004 | A1 |
20040168119 | Liu et al. | Aug 2004 | A1 |
20040172455 | Green et al. | Sep 2004 | A1 |
20040174392 | Bjoernsen et al. | Sep 2004 | A1 |
20040177122 | Appleman et al. | Sep 2004 | A1 |
20040177319 | Horn | Sep 2004 | A1 |
20040189694 | Kurtz et al. | Sep 2004 | A1 |
20040194025 | Hubert et al. | Sep 2004 | A1 |
20040221243 | Twerdahl et al. | Nov 2004 | A1 |
20040230599 | Moore et al. | Nov 2004 | A1 |
20040243677 | Curbow et al. | Dec 2004 | A1 |
20040243941 | Fish | Dec 2004 | A1 |
20040267625 | Feng et al. | Dec 2004 | A1 |
20040267706 | Springer et al. | Dec 2004 | A1 |
20040268231 | Tunning | Dec 2004 | A1 |
20040268263 | Van Dok et al. | Dec 2004 | A1 |
20050004989 | Satterfield et al. | Jan 2005 | A1 |
20050004990 | Durazo et al. | Jan 2005 | A1 |
20050005235 | Satterfield et al. | Jan 2005 | A1 |
20050005249 | Hill et al. | Jan 2005 | A1 |
20050010871 | Ruthfield et al. | Jan 2005 | A1 |
20050034078 | Abbott et al. | Feb 2005 | A1 |
20050055424 | Smith | Mar 2005 | A1 |
20050064852 | Baldursson | Mar 2005 | A1 |
20050097465 | Giesen et al. | May 2005 | A1 |
20050102365 | Moore et al. | May 2005 | A1 |
20050102607 | Rousselle et al. | May 2005 | A1 |
20050102639 | Dove | May 2005 | A1 |
20050108619 | Theall et al. | May 2005 | A1 |
20050114521 | Lee | May 2005 | A1 |
20050119018 | Kim | Jun 2005 | A1 |
20050125717 | Segal et al. | Jun 2005 | A1 |
20050149851 | Mittal | Jul 2005 | A1 |
20050154761 | Lee et al. | Jul 2005 | A1 |
20050165795 | Myka et al. | Jul 2005 | A1 |
20050166154 | Wilson et al. | Jul 2005 | A1 |
20050175089 | Jung | Aug 2005 | A1 |
20050183008 | Crider et al. | Aug 2005 | A1 |
20050208962 | Kim | Sep 2005 | A1 |
20050233744 | Karaoguz | Oct 2005 | A1 |
20050240590 | Shimizu et al. | Oct 2005 | A1 |
20050245241 | Durand | Nov 2005 | A1 |
20050286414 | Young et al. | Dec 2005 | A1 |
20050289109 | Arrouye et al. | Dec 2005 | A1 |
20060036945 | Radtke et al. | Feb 2006 | A1 |
20060036950 | Himberger et al. | Feb 2006 | A1 |
20060036965 | Harris et al. | Feb 2006 | A1 |
20060047704 | Gopalakrishnan | Mar 2006 | A1 |
20060053379 | Henderson et al. | Mar 2006 | A1 |
20060069603 | Williams et al. | Mar 2006 | A1 |
20060069604 | Leukart et al. | Mar 2006 | A1 |
20060069617 | Milener et al. | Mar 2006 | A1 |
20060075347 | Rehm | Apr 2006 | A1 |
20060075360 | Bixler | Apr 2006 | A1 |
20060095452 | Jansson et al. | May 2006 | A1 |
20060139709 | Bifano et al. | Jun 2006 | A1 |
20060150109 | Schultz et al. | Jul 2006 | A1 |
20060195461 | Lo et al. | Aug 2006 | A1 |
20070022372 | Liu et al. | Jan 2007 | A1 |
20070124325 | Moore et al. | May 2007 | A1 |
20070156627 | D'Alicandro | Jul 2007 | A1 |
20070156643 | Sareen et al. | Jul 2007 | A1 |
20070168278 | Peterson et al. | Jul 2007 | A1 |
20070168378 | Dev Sareen et al. | Jul 2007 | A1 |
20070245223 | Siedzik et al. | Oct 2007 | A1 |
20070245229 | Siedzik et al. | Oct 2007 | A1 |
20080115048 | Veselova et al. | May 2008 | A1 |
20080115069 | Veselova et al. | May 2008 | A1 |
Number | Date | Country |
---|---|---|
0569133 | Nov 1993 | EP |
0 986 011 | Mar 2000 | EP |
1 223 503 | Jul 2002 | EP |
1 376 337 | Feb 2004 | EP |
1 630 694 | Mar 2006 | EP |
2 391 148 | Jan 2004 | GB |
2001-265753 | Sep 2001 | JP |
WO 9800787 | Aug 1998 | WO |
WO 2004038548 | May 2004 | WO |
WO 2004086254 | Oct 2004 | WO |
WO 2005001709 | Jan 2005 | WO |
WO 2004038548 A3RA | Apr 2005 | WO |
WO 2005067328 | Jul 2005 | WO |
WO 2005110010 | Nov 2005 | WO |
WO 2007081783 | Jul 2007 | WO |
WO 2007081783 | Jul 2007 | WO |
WO 2007081786 | Jul 2007 | WO |
WO 2007081786 | Jul 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20060074844 A1 | Apr 2006 | US |