Patent Grant
7224366
The present invention relates to methods for displaying user control information on a touch panel and more particularly, the present invention relates to methods for building interactive control and non-interactive, non-control informational displays onto a touch panel screen.
Touch panels are electronic devices that use liquid crystal displays (LCDs) to display functional information to a user. A touch panel is used to operate various pieces of equipment. For example, touch panels can be used to control the lighting system of a room, electronics equipment such as VCRs, DVDs, stereos, and the like, and video surveillance equipment, such as video cameras, and other similar types of equipment.
A touch panel operates by allowing the user to press a region of the LCD panel to operate an associated piece of equipment. The user knows the region of the LCD to touch because an informational display (sometimes referred to by those in the industry as “buttons”) is presented to the user that allows the user to understand the appropriate location or region at which the panel should be touched. These informational displays are usually in the form of icons for the user to press. The icons are typically icons associated with the operation of the device. For example, a VCR may have a button for the play function and a button for the recording function of the VCR. These buttons would be displayed to the touch panel user in manner that would mimic their appearance on the remote control device for the VCR.
A problem arises, however, when multiple buttons are displayed on the touch panel in close proximity to each other. When this occurs, a single touch by a user can activate more than one button. This causes either an error to occur with the touch panel, or the touch panel itself prioritizes the buttons and selects the button with the higher priority to operate, often resulting in misoperation of the touch panel system. Therefore, it is desired to be able to build a touch panel display that allows for informational displays to be placed in close proximity to one another without resultant interference in the operations of the informational displays.
It has also been found advantageous to allow informational displays to be animated. Animation of an informational display enables certain control features to be displayed directly to the user to inform the user that the component associated with the informational display is in continuous operation. For example, an alarm system for a home may have an associated informational display that is a siren with a police light. By allowing animation, the police light can be continuously illuminated in a rotational manner to mimic a police car's lights. It is therefore desirable to have a touch panel capable of building animated informational displays.
The invention is directed to a method and system for building and displaying information on a touch panel, wherein the information may be control or non-control information, active or non-interactive information or some combination thereof. One embodiment of the invention, providing a method for building and displaying interactive, control, non-interactive and non-control information, selectively, on a touch panel comprises the steps of constructing the page for display on a touch panel, configuring a plurality of graphical display units in association with the page for display on the touch panel, and displaying the page and one or more of the graphical display unit, selectively, on the touch panel. The method further comprises the step of determining whether any of the graphical display units is activated by a touch message comprising an amount of pressure applied to a location on the touch panel.
In a preferred embodiment of the above method, each of the graphical display units is configured to have a total touch area comprising an active touch area and a non-active area, the active touch area of one graphical display unit overlapping a non-active area of another graphical display unit when both of the graphical display units are displayed. The determining step comprises determining whether the touch message location is within the active touch area of any graphical display unit on the touch panel, and if so, activating such graphical display unit.
In a further embodiment, each of the graphical display units is selectively provided with one or more colors, and is further provided with one or more features selected from a group of features that includes a bitmap, an icon, text and a border. Preferably, one or more sub-pages are configured in association with the page, at least one of the sub-pages comprising a video feed. Preferably also, at least one of the graphical display units comprises a bar graph having two or more states.
Another embodiment of the invention comprises a computer system provided with a processor and a computer readable medium operable to build and display interactive, control, non-interactive and non-control information, selectively, on a touch panel, in accordance with the invention.
A user utilizes the computer 15 to create touch panel displays such as 24 and 26 for display by the touch panel. These touch panel displays can be configured to control components 22a–e of the type referred to above. More particularly, a touch panel display comprises or contains a graphical display unit (GDU) 27, which is a symbol or other viewable indication located at a specific region upon screen 28 of touch panel 25. Control is implemented by touching the screen 28 at the specific region. Once a user creates a touch panel display, a file containing the information relating to the touch panel display is transferred from the user computer 15 to the touch panel 25 via the master controller 20. After touch panel 25 receives the file, the touch panel executes the file and builds a touch panel display.
Panels consist of one or more pages. A page is a single informational window displayed by the touch screen. Contained within the pages are one or more GDUs and one or more sub-pages. A GDU is an informational display created to allow the user of a touch panel to control the various components communicatively connected to the master controller 20. Each GDU has two or more states. A state is the operational position of the GDU. In other words and by way of example, a GDU may have two states—on and off. In the on state, the GDU may appear to be one color, while in the off state, the GDU appears as a different color. Each state of a GDU is a different image that is built by the graphics engine 30. Thus, if a GDU has 100 states, then the GDU has 100 associated images. Sub-pages may comprise, for example, video feeds from a camera in communication with the master controller 20 and the touch panel 25. These sub-pages are displayed to the user as windows within the page itself. Sub-pages may also have an associated state.
Communicating with the graphics engine 30 is a systems directory 35 and a panel directory 40. The systems directory 35 and the panel directory also are in communication with each other. The systems directory 35 includes a pages subdirectory 45 and a graphics subdirectory 50. The pages subdirectory 45 can be used to store information concerning the various resolution LCD screens used to build touch panels. It will be appreciated that one of ordinary skill in the art would recognize the various resolutions associated with commercially available LCD screens. The graphics subdirectory 50 contains information concerning known images, fonts, and other similar graphics information.
The panel directory 40 includes a fonts subdirectory 55, an images subdirectory 60, and a sounds subdirectory 65. The fonts subdirectory 55 contains standard fonts recognized and stored by the graphics engine 30. The images subdirectory 60 contains various images, such as bitmaps, icons, and other similar types of images recognized and stored by the graphics engine 30. The sounds subdirectory 65 contains all sounds recognized and stored by the graphics engine 30. The panel directory 40 also includes a pages file 70. The pages file 70 is created when the user uploads panel files from the user computer 15. After the upload, the pages file 70 will contain all information necessary for the graphics engine 30 to make the pages, GDUs, and sub-pages respectively available to the touch panel screen.
After a GDU is selected, the graphics engine determines the state of the GDU and builds that state, as shown by blocks 224 and 226. Once the state of the GDU is built, the graphics engines stores the state of the GDU in a GDU cache, as shown by block 228. The GDU cache is maintained within touch panel memory. After the state of the GDU is saved to the GDU cache, the graphics engine sets the overall opacity of the GDU, as shown by block 230. The opacity of the GDU determines the transparency of the GDU. In other words, some GDUs may be solid and some GDUs may allow objects underneath the GDU to be seen.
After setting the GDU opacity, block 232 shows that the graphics engine delivers the GDU data to RAM of the touch panel. After delivering the GDU data to RAM, the graphics engine determines whether other GDUs need building, as shown by block 234. If other GDUs require building, then the steps of the process are repeated beginning with block 222. If no other GDUs require building, then the graphics engine proceeds to supply sub-pages associated with pages as shown by block 206 of
In supplying sub-pages, the graphics engine first determines if the page has associated sub-pages, as in block 236 of
After the display level is determined, block 610 shows that the graphics engine generates a composite that is a percentage of each state associated with the bargraph GDU. Next, the graphics engine determines if the bargraph GDU has a slider, as shown by block 615. A slider is a graphical representation used to depict the display level position of the bargraph GDU. If a slider exists, a representation thereof is generated, as shown in block 617. Once blocks 605 through 615 are completed, the bargraph GDU is built, as shown by block 620. For the above example, the slider would be shown at a horizontal position along the bargraph so that 75% of the area of the bargraph, on one side of the slider, would be blue, and 25% of the area, on the other side, would be red.
Next, the graphics engine determines whether the GDU has an associated bitmap, as shown by block 820. If the GDU has an associated bitmap, the bitmap is retrieved from a bitmap database stored in RAM and furnished to the GDU, as shown by block 825. Once the graphics engine begins operating the page file in the panel directory, the graphics engine creates the bitmap database. If the GDU does not contain a bitmap or once the bitmap has been retrieved and furnished, then the graphics engine determines whether the GDU has an associated icon, as shown by block 830. If the GDU contains an icon, then the icon is retrieved and furnished to the GDU, as shown by block 835. If the GDU does not contain an icon or once the icon has been retrieved and furnished, then the graphics engine determines whether the GDU has any associated text, as shown by block 840. If the GDU has an associated line of text, then the line of text is built and furnished to the GDU, as shown by block 845. If the GDU does have text or once the text has been built and furnished, then the graphics engine determines whether the GDU has an associated border, as shown by block 850. If the GDU has a border, then the border is built and furnished to the GDU, as shown by block 855. If the GDU does have a border or once the border has been built and furnished, then the built GDU is saved to the GDU cache, as shown by block 860.
If it is determined that the bitmap is dynamic, then the graphics engine retrieves the bitmap from the remote location where it is stored using the master controller 20 as shown in block 905. Once the bitmap is retrieved from the remote location, the graphics engine determines the location of the bitmap on the GDU, as shown by block 915. After the location of the bitmap is determined, the bitmap is provided or delivered to the GDU, as shown by block 920. If the bitmap is not dynamic, then block 910 shows that the graphics engine retrieves the bitmap from the images subdirectory 60. Once the bitmap is retrieved from the images subdirectory, then block 915 shows that the graphics engine determines the location of the bitmap on the GDU. After determining the location of the bitmap, the bitmap is delivered to the GDU, as shown by block 920.
Once it is determined that an icon is associated with the GDU, the graphics engine retrieves the icon from an icon database contained in RAM, as shown by block 1000 of
Once a determination is made that the GDU contains a line of text, block 1100 of
After determining the location of the text on the GDU, the line of text is created and positioned on the GDU, as shown by block 1130. Once a line of text is positioned on the GDU, the graphics engine determines whether another line of text is associated with the GDU, as shown by block 1135. If another line of text is associated with the GDU, then blocks 1100 through 1130 are repeated. These steps are repeated until all lines of text have been created and positioned onto the GDU, as shown by block 1140.
If the character is not an end of line character, then the graphics engine determines whether the character with the appropriate effect is stored in the effect cache, as shown in block 1220. The effect cache is a database containing all characters with effects that have been previously built. If the character with the appropriate effect is stored in the effect cache, then the character and effect are delivered to the GDU, as shown by block 1225 and the next character is determined, as shown by block 1205.
If the character with appropriate effect is not stored in the effect cache, then the graphics engine creates a description of the character and effect, as shown by block 1230. Block 1235 then shows that the description of the character and the effect are saved to the effect cache after which the character effect is delivered to the GDU, as shown by block 1225. The graphics engine then determines the next character, as shown by block 1205.
If the character is an end of line character, then the effects for the line of text have all been provided, and the line of text is reset to the first character to generate actual text characters, as shown by block 1240. Block 1245 shows that the graphics engine again determines the character. After the character is determined, the graphics engine again determines whether the character is an end of line character, as shown by block 1250. If the character is an end of line character, the line of text is complete, as shown by block 1255. If the character is not an end of line character, then the character cache is checked to determine if the character exists, as shown in block 1260. Like the effect cache, the character cache is created once the graphics engine has built characters. If the character is not stored in the character cache, then block 1265 shows that the graphics engine creates a character description for the character after which the character is stored in the character cache, as shown in block 1270. After the character is stored in the character cache, the character is retrieved and delivered to the GDU, as shown by block 1275 and the next character in the line of text is determined, as shown by block 1245. If the character is stored in the character cache, then the character is retrieved and delivered to the GDU, as shown by block 1275. The next character in the line of text is determined, as shown by block 1245.
Once it is determined that the GDU has an associated border, the border description is retrieved from the border database in RAM, as shown by block 1300 of
After the GDU has been masked, the graphics engine determines whether the border is stored in the border cache, as shown by block 1310. The border cache is created once the graphics engine begins building the borders for GDUs. If the border is stored in the border cache, then the border is retrieved and delivered to the GDU, as shown by block 1315. If the border is not stored in the border cache, then the border pieces are created, as shown by block 1320. Each border is a series of eight or more border pieces. Each piece will cover a particular region of the GDU. Once the border pieces are created block 1325 shows that the border pieces are colorized. Next, the colorized border pieces are stored to the border cache, as shown by block 1330. After storing the border pieces in the border cache, the border pieces are delivered to the GDU, as shown by block 1315.
In the operation of touch panels, it has become important to be able to furnish GDUs to the touch panel, such that the GDUs emulate the operational controls for a device associated with and represented by the GDU. For example, a Digital Video Device (DVD) may have a remote control that includes a play button, a reverse button, a fast forward button and a pause button, all within the same general region. A touch panel, to achieve user-friendly operation, should emulate the configuration of the DVD remote control device.
Because all GDUs begin as a square configuration and are then masked or cropped to their display shape, GDUs within close proximity may cause interference with the operations of one another. More particularly, a touch message is the application of pressure to a region of a touch panel screen on which a GDU is displayed. The application of pressure generates a control signal for a purpose associated with the GDU. However, because a GDU remains square even after masking, the areas of adjacent GDUs may overlap, if the GDUs are in close proximity. Thus, a touch message intended for a particular GDU could also apply pressure to a closely spaced adjacent GDU. Accordingly, to prevent this interference, it has been found that an active touch area can be defined for each GDU, for use in discerning between GDUs in close proximity. The active touch area of a GDU will generally be the unmasked area of its corresponding square.
Once a touch message is received by the touch panel, the touch panel determines if the touch message actively touches a GDU. Thus, in
Once the touch panel has mathematically plotted the lines XB and XC, each line is analyzed in the manner described in
If the touch determines the sub-page was not hit, then the touch panel determines if that was the last sub-page, as in block 1555. If other sub-pages exist, then the touch panel begins over the process described above beginning with block 1510. If no other sub-pages exist, then it is determined if the page has GDUs as in block 1560. If GDUs exist, then all GDUs active on the page are ordered and determined if hit, as shown by blocks 1565and 1570. If it is determined that a GDU is hit, the touch panel then determines if the GDU was actively touched, as shown by block 1575. If the GDU was actively touched, then the GDU is operated, as shown by block 1580. If the GDU was not actively touched or the GDU was not hit, the touch panel then determines whether the GDU was the last GDU on the page, as shown by block 1585. If the GDU was not the last GDU on the page, then the next GDU in the order is determined, as shown by block 1565. If the GDU was the last GDU on the page, the touch panel then determines if the touch operates the page, as shown by block 1590. A page may have operational features separate and apart from the GDUs.
If the requested state does not equal min, then it is determined whether the current state equals max, as shown by block 1830. If the current state equals max, then the operation ends, as shown by block 1820. If the current state does not equal max, then the multi-state general would change display from its current state to max, sequentially displaying each state between its current state and its max state, as shown by block 1835. It should be appreciated that if any state between the current state and max does not exist, then that state would be built in accordance with the processes and figures described above.
If it is determined that the multi-state general GDU is a repeating GDU, then it is determined whether the requested state equals min, as shown by block 1840. If the requested state does not equal min, it is determined whether the current state equals max, as shown by block 1845. If the current state equals max, then the state of the multi-state general GDU is set to min and the multi-state general GDU continues to change display from its min state to its max state, sequentially displaying all states in-between, as shown by block 1850. It should be appreciated that this operation allows for the multi-state general GDU to be continuously animated. For example, the multi-state general GDU may be built to resemble a stopwatch such that the min state equals 0 and the max state equals 60. Each state in-between the min state and the max state would account for a one second time interval. Thus, the second hand on the stopwatch would be continuously moving from 0 to 60 under the process described above.
If the current state does not equal max, then the multi-state general would change display from its current state to max, sequentially displaying each state between its current state and its max state, as shown by block 1855. Once the max state has been achieved, then the state is set to min and the multi-state general GDU continues to change display from its min state to its max state, sequentially displaying all states in-between, as shown by block 1850. It should be appreciated that if any state necessary for the operations described in reference to blocks 1850 or 1855 does not exist in the GDU cache, then that state would be built in accordance with the processes and figures described above.
If the requested state equals min, then it is determined whether the current state equals min, as shown by block 1860. If the current state equals min, then the operation of the multi-state general GDU ends, as shown by block 1865. If the current state does not equal min, then the multi-state general GDU would change display from its current state to min, sequentially displaying each state between its current state and its min state, as shown by block 1870. Again, it should be appreciated that if any state between the current state and min does not exist, then that state would be built in accordance with the processes and figures described above.
Obviously, many other modifications and variations of the present invention are possible in light of the above teachings. The specific embodiments discussed here are merely illustrative and are not meant to limit the scope of the present invention in any manner. It should be appreciated that the present invention provides many applicable inventive concepts that may be embodied in a wide variety of specific contexts. It is therefore to be understood that within the scope of the disclosed concept, the invention may be practiced otherwise than as specifically described.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3597743 | Murphy et al. | Aug 1971 | A |
| 3778542 | Hanseman | Dec 1973 | A |
| 4024505 | Sperling | May 1977 | A |
| 4251858 | Cambigue et al. | Feb 1981 | A |
| 4503497 | Krygowski et al. | Mar 1985 | A |
| 4530069 | Desrochers | Jul 1985 | A |
| 4700230 | Pshtissky et al. | Oct 1987 | A |
| 4790003 | Kepley et al. | Dec 1988 | A |
| 4876651 | Dawson et al. | Oct 1989 | A |
| 4882747 | Williams | Nov 1989 | A |
| 4904993 | Sato | Feb 1990 | A |
| 4914527 | Asai et al. | Apr 1990 | A |
| 4953194 | Hansen et al. | Aug 1990 | A |
| 4989081 | Miyagawa et al. | Jan 1991 | A |
| 5014193 | Garner et al. | May 1991 | A |
| 5039980 | Aggers et al. | Aug 1991 | A |
| 5051720 | Kittirutsunetorn | Sep 1991 | A |
| 5056001 | Sexton | Oct 1991 | A |
| 5072374 | Sexton et al. | Dec 1991 | A |
| 5086385 | Launey et al. | Feb 1992 | A |
| 5095480 | Fenner | Mar 1992 | A |
| 5103391 | Barrett | Apr 1992 | A |
| 5109222 | Welty | Apr 1992 | A |
| 5119479 | Arai et al. | Jun 1992 | A |
| 5144548 | Salandro | Sep 1992 | A |
| 5233510 | Brueckner et al. | Aug 1993 | A |
| 5276630 | Baldwin et al. | Jan 1994 | A |
| 5276793 | Borgendale et al. | Jan 1994 | A |
| 5311451 | Barrett | May 1994 | A |
| 5317562 | Nardin et al. | May 1994 | A |
| 5347632 | Filepp et al. | Sep 1994 | A |
| 5371859 | Lennartsson | Dec 1994 | A |
| 5375248 | Lemay et al. | Dec 1994 | A |
| 5388213 | Oppenheimer et al. | Feb 1995 | A |
| 5410326 | Goldstein | Apr 1995 | A |
| 5428470 | Labriola, II | Jun 1995 | A |
| 5434982 | Calzi | Jul 1995 | A |
| 5444851 | Woest | Aug 1995 | A |
| 5446740 | Yien et al. | Aug 1995 | A |
| 5450359 | Sharma et al. | Sep 1995 | A |
| 5452291 | Eisenhandler et al. | Sep 1995 | A |
| 5455959 | Simmering | Oct 1995 | A |
| 5463735 | Pascucci et al. | Oct 1995 | A |
| 5467264 | Rauch et al. | Nov 1995 | A |
| 5481750 | Parise et al. | Jan 1996 | A |
| 5491797 | Thompson et al. | Feb 1996 | A |
| 5491802 | Thompson et al. | Feb 1996 | A |
| 5500794 | Fujita et al. | Mar 1996 | A |
| 5510975 | Ziegler, Jr. | Apr 1996 | A |
| 5519707 | Subramanian et al. | May 1996 | A |
| 5519875 | Yokoyama et al. | May 1996 | A |
| 5528215 | Siu et al. | Jun 1996 | A |
| 5528739 | Lucas et al. | Jun 1996 | A |
| 5537142 | Fenouil | Jul 1996 | A |
| 5537663 | Belmont et al. | Jul 1996 | A |
| 5557723 | Holt et al. | Sep 1996 | A |
| 5565855 | Knibbe | Oct 1996 | A |
| 5565908 | Ahmad | Oct 1996 | A |
| 5568367 | Park | Oct 1996 | A |
| 5568489 | Yien et al. | Oct 1996 | A |
| 5570085 | Bertsch | Oct 1996 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5583994 | Rangan | Dec 1996 | A |
| 5586267 | Chatwani et al. | Dec 1996 | A |
| 5592626 | Papadimitriou et al. | Jan 1997 | A |
| 5594366 | Khong et al. | Jan 1997 | A |
| 5600635 | Hamaki et al. | Feb 1997 | A |
| 5630079 | McLaughlin | May 1997 | A |
| 5634011 | Auerbach | May 1997 | A |
| 5648813 | Tanigawa et al. | Jul 1997 | A |
| 5657221 | Warman et al. | Aug 1997 | A |
| 5675756 | Benton et al. | Oct 1997 | A |
| 5687393 | Brown et al. | Nov 1997 | A |
| 5689353 | Darbee et al. | Nov 1997 | A |
| 5699532 | Barrett et al. | Dec 1997 | A |
| 5706455 | Benton et al. | Jan 1998 | A |
| 5710755 | Chen | Jan 1998 | A |
| 5720032 | Picazo, Jr. et al. | Feb 1998 | A |
| 5721878 | Ottesen et al. | Feb 1998 | A |
| 5724574 | Stratigos et al. | Mar 1998 | A |
| 5732257 | Atkinson et al. | Mar 1998 | A |
| 5737529 | Dolin, Jr. et al. | Apr 1998 | A |
| 5737553 | Bartok | Apr 1998 | A |
| 5739760 | Hatakeyama | Apr 1998 | A |
| 5740231 | Cohn et al. | Apr 1998 | A |
| 5742762 | Scholl et al. | Apr 1998 | A |
| 5754255 | Takamori | May 1998 | A |
| 5764155 | Kertesz et al. | Jun 1998 | A |
| 5805812 | Fish et al. | Sep 1998 | A |
| 5812085 | Barraza et al. | Sep 1998 | A |
| 5812122 | Ng | Sep 1998 | A |
| 5812214 | Miller | Sep 1998 | A |
| 5812750 | Dev et al. | Sep 1998 | A |
| 5815516 | Aaker et al. | Sep 1998 | A |
| 5815703 | Copeland et al. | Sep 1998 | A |
| 5835126 | Lewis | Nov 1998 | A |
| 5844572 | Schott | Dec 1998 | A |
| 5848054 | Mosebrook et al. | Dec 1998 | A |
| 5857199 | Tamano et al. | Jan 1999 | A |
| 5867484 | Shaunfield | Feb 1999 | A |
| 5886894 | Rakoff | Mar 1999 | A |
| 5892924 | Lyon et al. | Apr 1999 | A |
| 5896382 | Davis et al. | Apr 1999 | A |
| 5907837 | Ferrel et al. | May 1999 | A |
| 5909570 | Webber | Jun 1999 | A |
| 5910954 | Bronstein et al. | Jun 1999 | A |
| 5918022 | Batz et al. | Jun 1999 | A |
| 5920694 | Carleton et al. | Jul 1999 | A |
| 5922050 | Madany | Jul 1999 | A |
| 5926187 | Kim | Jul 1999 | A |
| 5935003 | Stephens et al. | Aug 1999 | A |
| 5940387 | Humpleman | Aug 1999 | A |
| 5943064 | Hong | Aug 1999 | A |
| 5956487 | Venkatraman et al. | Sep 1999 | A |
| 5957985 | Wong et al. | Sep 1999 | A |
| 5959536 | Chambers et al. | Sep 1999 | A |
| 5968116 | Day, II et al. | Oct 1999 | A |
| 5977989 | Lee et al. | Nov 1999 | A |
| 5982445 | Eyer et al. | Nov 1999 | A |
| 5995753 | Walker | Nov 1999 | A |
| 5996022 | Krueger et al. | Nov 1999 | A |
| 6005861 | Humpleman | Dec 1999 | A |
| 6008735 | Chiloyan et al. | Dec 1999 | A |
| 6012113 | Tuckner | Jan 2000 | A |
| 6021433 | Payne et al. | Feb 2000 | A |
| 6023762 | Dean et al. | Feb 2000 | A |
| 6029092 | Stein | Feb 2000 | A |
| 6038668 | Chipman et al. | Mar 2000 | A |
| 6049821 | Theriault et al. | Apr 2000 | A |
| 6049828 | Dev et al. | Apr 2000 | A |
| 6052683 | Irwin | Apr 2000 | A |
| 6055236 | Nessett et al. | Apr 2000 | A |
| 6055368 | Kunioka | Apr 2000 | A |
| 6061602 | Meyer | May 2000 | A |
| 6061717 | Carleton et al. | May 2000 | A |
| 6075776 | Tanimoto et al. | Jun 2000 | A |
| 6078747 | Jewitt | Jun 2000 | A |
| 6078952 | Fielding et al. | Jun 2000 | A |
| 6085238 | Yuasa et al. | Jul 2000 | A |
| 6085243 | Fletcher et al. | Jul 2000 | A |
| 6088717 | Reed et al. | Jul 2000 | A |
| 6101189 | Tsuruoka | Aug 2000 | A |
| 6105055 | Pizano et al. | Aug 2000 | A |
| 6108696 | Mendhekar et al. | Aug 2000 | A |
| 6115713 | Pascucci et al. | Sep 2000 | A |
| 6121593 | Mansbery et al. | Sep 2000 | A |
| 6133847 | Yang | Oct 2000 | A |
| 6144993 | Fukunaga et al. | Nov 2000 | A |
| 6160796 | Zou | Dec 2000 | A |
| 6161133 | Kikinis | Dec 2000 | A |
| 6161145 | Bainbridge et al. | Dec 2000 | A |
| 6167567 | Chiles et al. | Dec 2000 | A |
| 6175920 | Schanze | Jan 2001 | B1 |
| 6192282 | Smith et al. | Feb 2001 | B1 |
| 6195688 | Caldwell et al. | Feb 2001 | B1 |
| 6198479 | Humpleman et al. | Mar 2001 | B1 |
| 6199133 | Schnell | Mar 2001 | B1 |
| 6240554 | Fenouil | May 2001 | B1 |
| 6241156 | Kline et al. | Jun 2001 | B1 |
| 6259707 | Dara-Abrams | Jul 2001 | B1 |
| 6260069 | Anglin | Jul 2001 | B1 |
| 6266339 | Donahue et al. | Jul 2001 | B1 |
| 6272134 | Bass et al. | Aug 2001 | B1 |
| 6288716 | Humpleman et al. | Sep 2001 | B1 |
| 6292901 | Lys et al. | Sep 2001 | B1 |
| 6310879 | Zhou et al. | Oct 2001 | B2 |
| 6330238 | Ooe | Dec 2001 | B1 |
| 6338152 | Fera et al. | Jan 2002 | B1 |
| 6342906 | Kumar et al. | Jan 2002 | B1 |
| 6360270 | Cherkasova et al. | Mar 2002 | B1 |
| 6363422 | Hunter et al. | Mar 2002 | B1 |
| 6415328 | Korst | Jul 2002 | B1 |
| 6434157 | Dube et al. | Aug 2002 | B1 |
| 6434680 | Belknap et al. | Aug 2002 | B2 |
| 6437691 | Sandelman et al. | Aug 2002 | B1 |
| 6446130 | Grapes | Sep 2002 | B1 |
| 6456699 | Burg et al. | Sep 2002 | B1 |
| 6469695 | White | Oct 2002 | B1 |
| 6469987 | Rijhsinghani | Oct 2002 | B1 |
| 6477569 | Sayan et al. | Nov 2002 | B1 |
| 6484061 | Papadopoulos et al. | Nov 2002 | B2 |
| 6484149 | Jammes et al. | Nov 2002 | B1 |
| 6496927 | McGrane et al. | Dec 2002 | B1 |
| 6505146 | Blackmer | Jan 2003 | B1 |
| 6523696 | Saito et al. | Feb 2003 | B1 |
| 6542165 | Ohkado | Apr 2003 | B1 |
| 6546405 | Gupta et al. | Apr 2003 | B2 |
| 6553418 | Collins et al. | Apr 2003 | B1 |
| 6574234 | Myer et al. | Jun 2003 | B1 |
| 6609127 | Lee et al. | Aug 2003 | B1 |
| 6615088 | Myer et al. | Sep 2003 | B1 |
| 6657646 | Partridge et al. | Dec 2003 | B2 |
| 6680934 | Cain | Jan 2004 | B1 |
| 6697376 | Son et al. | Feb 2004 | B1 |
| 6744771 | Barber et al. | Jun 2004 | B1 |
| 6760760 | McGrane | Jul 2004 | B1 |
| 6763040 | Hite et al. | Jul 2004 | B1 |
| 6775654 | Yokoyama et al. | Aug 2004 | B1 |
| 6791554 | Mergard et al. | Sep 2004 | B1 |
| 6801529 | McGrane et al. | Oct 2004 | B1 |
| 6829368 | Meyer et al. | Dec 2004 | B2 |
| 6865596 | Barber et al. | Mar 2005 | B1 |
| 6868403 | Wiser et al. | Mar 2005 | B1 |
| 6934414 | Kondo et al. | Aug 2005 | B2 |
| 6937766 | Wilf et al. | Aug 2005 | B1 |
| 7076153 | Ando et al. | Jul 2006 | B2 |
| 20020013948 | Aguayo et al. | Jan 2002 | A1 |
| 20020176601 | Rhoads | Nov 2002 | A1 |
| 20030035556 | Curtis et al. | Feb 2003 | A1 |
| 20030149574 | Rudman | Aug 2003 | A1 |
| 20040034864 | Barrett et al. | Feb 2004 | A1 |
| 20040044742 | Evron et al. | Mar 2004 | A1 |
| 20040075694 | Partridge et al. | Apr 2004 | A1 |
| 20040196255 | Cheng | Oct 2004 | A1 |
| 20050273700 | Champion et al. | Dec 2005 | A1 |
| 20060067341 | Barber et al. | Mar 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 0449632 | Oct 1991 | EP |
| 0626635 | Nov 1994 | EP |
| 0658899 | Jun 1995 | EP |
| 0743595 | May 1996 | EP |
| 0798894 | Oct 1997 | EP |
| 0812086 | Dec 1997 | EP |
| 0841615 | May 1998 | EP |
| 0841616 | May 1998 | EP |
| 0915469 | May 1999 | EP |
| 0939517 | Sep 1999 | EP |
| 0530973 | Oct 2003 | EP |
| 10276478 | Oct 1998 | JP |
| WO 9521415 | Aug 1995 | WO |
| WO 9624231 | Aug 1996 | WO |
| WO 9718636 | May 1997 | WO |
| WO 9726587 | Jul 1997 | WO |
| WO 9744747 | Nov 1997 | WO |
| WO 9800788 | Jan 1998 | WO |
| WO 9811510 | Mar 1998 | WO |
| WO 9835335 | Aug 1998 | WO |
| WO 9836336 | Aug 1998 | WO |
| WO 9853581 | Nov 1998 | WO |
| WO 9903255 | Jan 1999 | WO |
| WO 9905584 | Feb 1999 | WO |
| WO 9924905 | May 1999 | WO |
| WO 0028403 | May 2000 | WO |
| WO 0067135 | Nov 2000 | WO |
| WO 0075738 | Dec 2000 | WO |
| WO 0075903 | Dec 2000 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20040085361 A1 | May 2004 | US |
