System and method for providing computer assisted user support

Information

  • Patent Grant
  • 7602898
  • Patent Number
    7,602,898
  • Date Filed
    Wednesday, August 18, 2004
    20 years ago
  • Date Issued
    Tuesday, October 13, 2009
    15 years ago
Abstract
The disclosure is directed to a customer support call system including an interactive voice response system configured to receive a customer support call and configured to determine a caller identification. The interactive voice response system is configured to determine whether the customer support call is associated with a computer system having an installed self-support tool. The customer support call system further includes a call center management system responsive to the interactive voice response system. The call center management system is configured to direct the customer support call in response to determining whether the customer support call is associated with the computer system having the installed self-support tool.
Description
FIELD OF THE DISCLOSURE

This disclosure, in general relates to systems and methods for providing computer assisted user support.


BACKGROUND

Traditionally, customer support for technical issues has been performed using technical support call centers. When a customer has a technical issue or trouble with a technology related product, such as high-speed Internet access or a software product, the customer calls the call center to discuss the trouble with a call center agent. However, operation of technical support call centers is expensive.


Technical support call center agents are generally experienced and competent in technology related fields. As such, technical support agents demand higher wages than the average call center agent. In addition, technical support agents undergo expensive training relating to the technology products they support, increasing agent costs.


To reduce costs associated with technical support call centers, some companies have attempted to move technical support call centers to countries with lower labor costs. However, foreign call centers incur increased expenses relating to communication traffic. In addition, companies typically find a shortage in competent and trained agents in the foreign location.


For both regional and foreign call centers, increased usage by customers leads to further increased costs. High call volume leads to high labor costs for regional call centers and high communications traffic and logistics problems for foreign call centers.


For some products, such as high-speed Internet connections and software products, companies have developed automated self-support tools in an effort to reduce call volume. However, these support tools typically do not provide metrics or measurements as to their effectiveness. Therefore, there is a need for improved systems and methods for providing automated self-support tools and for measuring the effectiveness of using such tools.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1 and 2 are block diagrams illustrating exemplary embodiments of customer support systems.



FIGS. 3, 4, 5 and 6 are flow diagrams illustrating exemplary methods of operation of customer support systems such as those illustrated in FIGS. 1 and 2.





DESCRIPTION OF THE DRAWING(S)

In a particular embodiment, the disclosure is directed to a customer support call system including an interactive voice response system configured to receive a customer support call and configured to determine a caller identification. The interactive voice response system is configured to determine whether the customer support call is associated with a computer system having an installed self-support tool. The customer support call system further includes a call center management system responsive to the interactive voice response system. The call center management system is configured to direct the customer support call in response to determining whether the customer support call is associated with the computer system having the installed self-support tool.


In another exemplary embodiment, the disclosure is directed to a method of providing computer assisted user support to a computer user. The method includes receiving a customer support call and a caller identification associated with the customer support call, determining whether the customer support call is associated with a computer system having an installed self-support tool based on the caller identification, and managing the customer support call in response to determining whether the customer support call is associated with the computer system having the installed self-support tool.


In a further exemplary embodiment, the disclosure is directed to a computer implement system having computer readable memory including computer implemented software instructions operable to perform the method described above.


An illustrative system is depicted in FIG. 1. A customer located at a customer location 102 may have on premise equipment, such as a telephone 104 and a computer 108 coupled to a modem 106. The customer may, for example, install a computer software self-support and diagnostics tool on the computer 108. Once installed, the self-support and diagnostics tool communicates an SST identifier 130, such as a DSL telephone number of the customer, via a broadband transport, such as through the modem 106, such as a DSL modem, to a self-support tool (SST) server 118. The SST server 118 stores the customer's DSL telephone number in a SST database 120. Broadband transports may include digital subscriber lines (DSL), fiber optic data lines, cable data networks, long range wireless data networks and satellite communications systems. In alternative embodiments, the SST identifier 130 can be a unique customer identifier, such as an account number, member identifier or telephone number.


The SST identifier stored in the SST database 120 is transferred to an interactive voice response (IVR) system 110 and stored in an IVR database 112. For example, DSL telephone numbers may be transferred as received, periodically (i.e. hourly or nightly), or during off-peak times (i.e. at night).


When the customer experiences a problem, the customer may use the self-support tool (SST) installed on the computer 108. For example, the computer software SST may launch automatically in response to detecting a problem. Alternatively, the computer software SST may be initiated by a user of the computer 108. If the problem is resolved by the computer software SST, information about the problem and resolution of the problem 132 is sent to the SST server 118 and stored on the SST database 120. Information about failure to solve a problem 132 may also be transferred and stored on the SST database 120. Data associated with resolution of customer problems, such as SST problem resolution metrics, are reported to a data warehouse 122. When a problem has been resolved by the SST and the customer does not call a call center, the call has been deflected, reducing the number of calls the call center receives.


If a customer calls a call center for support, the customer may first interact with an interactive voice response (IVR) system 110. The IVR system 110 receives customer identification information, such as DSL telephone number information, and compares the information to SST identifiers, such as the DSL telephone numbers previously stored in the IVR database 112. The IVR directs the call based on whether the customer has an installed and operational SST. For example, if the IVR determines, based on finding the customer's DSL telephone number in a list of stored DSL telephone numbers, that the customer has an installed and operational SST, the system may direct the call to an SST supporting agent or may direct the troubleshooting flow to be followed by the agent. For example, the call may be sent to a call center queue management server 114 with an indication that an SST is installed on the customer's computer.


Based on the customer's identification and response to menu options and queries, the customer may be transferred to a call center queue management server 114 to await interaction with a call center agent. Information associated with the customer's call, such as the DSL telephone number, reason for the call, and resolution data, may be stored in a call center metrics database 116.


The call center metrics database 116 transfers data 134, such as the DSL telephone numbers, to the data warehouse 122 for storage. Reporting teams may access the data warehouse 122 via a reporting team interface 124. The data warehouse 122, which includes data received from the SST database 120 and data received from the call center metrics database 116, may be used to analyze and report effectiveness of the computer software SST. For example, the reporting team interface 124 may determine efficiency of the SST, a return on investment (ROI) based on a number of measured deflected calls, and future problem resolutions that may be implemented in subsequent versions of the computer software SST. In one exemplary embodiment, the reporting team interface 124 may compare DSL telephone numbers of customers calling into the call center with the DSL telephone numbers of customers running the computer software SST to determine an efficiency of the SST or the ROI of the SST.


Referring to FIG. 2, an illustrative system is shown. The system includes a representative end user computer 202 coupled via a data connection 218 to network equipment 204. The system further includes a call center 220 coupled to the network equipment 204 via an intermediate computer network 206. The call center 220 is coupled to a customer call center support data log 222, a call deflection determination module 224, and a call deflection measurement and reporting module 226. The end computer 202 includes a customer self-help support and diagnostic software tool 212.


During operation, a user of the computer 202 executes the customer self-help support and diagnostic software tool 212 and generates trouble resolution data 216. In addition, the computer 202 retrieves information as to the user identity and creates a data item referred to as a customer ID 214. After use of the self-help support tool, the customer ID 214 and the trouble resolution data 216 are communicated over the data connection 218, such as a digital subscriber line (DSL) connection, to the network equipment 204. The network equipment 204 retrieves the customer ID 214 and trouble resolution data 216 from the computer 202 as well as other data that may be received at the network equipment and all data provided by the self-help support tool is stored at the self-help support tool data collection module 230. The network equipment 204 communicates the customer ID 214 and the trouble resolution data 216 over a distributive network 206, such as the Internet or a private distributive computer network, to the remotely located call center 220.


The call center 220 stores the customer ID 214 and trouble resolution data 216. A call deflection determination module 224 receives the stored customer ID 214 and trouble resolution data 216 and compares such data with call records stored within the customer call center support data log 222. The call deflection determination module 224, based on the comparison, generates a determination as to the number and identity of potential call center calls that have been deflected through use of the self-help support and diagnostic tool. For example, based on a particular type of trouble item and based on a customer ID, the call deflection determination module checks the call center 220 to determine whether a customer having the caller ID places a call with a specified time frame to the call center. If no call is detected, the resolution actions taken by the SST are tracked as a successful call deflection. The call deflection determination module 224 generates call deflection data and provides such call deflection information to the call deflection measurement and reporting unit 226. The call deflection measurement and reporting module 226 performs cost measurements and other data measurements to create and display call deflection reports for operations personnel to evaluate call deflection metrics and performance.


Referring to FIG. 3, a method of operation with respect to the illustrative customer support center and related systems of FIGS. 1 and 2 is shown. A customer call is received, as shown at step 302. For example, a customer may call an 800 number and interact with an interactive voice response (IVR) system. The IVR system may determine a caller identification, such as a telephone number using an automated number identification (ANI) system, as shown at step 304. If the caller identification is not recognized, as shown at step 306, the system may prompt the customer for a caller identification, such as a telephone number associated with a digital subscriber line (DSL) account, as shown at step 310. Similarly, when a call is transferred from another call center system, as shown at step 308, the system may prompt the customer for the caller identification.


Once the customer has entered a caller identification or the system recognizes the caller identification, the customer interacts with an IVR-based menu. For example, the caller may be prompted to determine whether the caller is calling for technical support, as shown at step 312. If the caller is not calling for technical support, the caller is transferred to a call center system or agent not associated with technical support, as shown at step 314.


If the customer is calling for technical support, the caller may be prompted to determine if the self-support tool has been installed, as shown at step 316. If the call has been made prior to installation of the self-support tool, the call may be transferred to a support queue associated with installation assistance and pre-installation troubleshooting, as shown at step 318.


If the self-support tool has been installed, the system may compare the customer identification with a list identifying customers having the self-support tool installed. For example, when the self-support tool is operating, the tool may send a message to notify a self-support tool server of its presence. In addition, the self-support tool may provide data identifying the customer and data identifying trouble issues and resolution actions. The data identifying the customer may be stored in a list and used for comparison with the customer identification received in conjunction with the call.


If the customer identification is not found in the list, the call is transferred to an agent, as shown at step 312. The agent may follow a troubleshooting flow that is based on the determination that the self-support tool is not installed.


If the customer identification is found in the list, a support agent is notified that the self-support tool is installed and operational, as shown at step 324. The call is transferred to the support agent who follows a troubleshooting flow based on the installation and operability of the self-support tool. In one exemplary embodiment, the support agent may also receive information associated with trouble issue and resolution steps identified and taken by the self-support tool.


Referring to FIG. 4, a method of operation with respect to the illustrative call centers and related systems of FIGS. 1 and 2 is shown. The method includes collecting customer identification information for a user of a computer-assisted user support tool, as shown at step 402. The method further includes collecting trouble report resolution information in response to use of the computer assisted user support tool, as shown at step 404. The trouble report resolution information may be associated with a particular class of reportable trouble items. As shown at step 406, the customer identification information and the trouble report resolution information are compared to a data log of call records retrieved from a customer support call center. A report of a number of deflected customer support calls through successful use of the computer assisted user support tool is provided, as shown at step 408. Cost savings based on the number of deflected calls is measured as shown at step 410, and a report including the deflected call count and measured call center cost savings information is reported, as shown at step 412. The report may be generated locally or may be distributed over a network for remote access and display.


Referring to FIG. 5, a method of evaluating performance of a computer self-support tool is shown. The method includes collecting data that includes a customer identifier, a reported trouble issue, and resolution action for the reported trouble issue, as shown at 502. The method further includes comparing the data from computer support tool to a call center data log to determine whether the customer called the call center for support with respect to a reported trouble issue corresponding to the issue handled using the self-help tool, or whether the call was successfully deflected by the customer's use of the self-support tool, as shown at step 504. The method further includes recording measurement data with respect to the result of comparing the call center data log and the data from the self-help support tool, as shown at step 506. After the measurement data from the comparison has been recorded, a first cost savings estimate is determined based on the average cost of call center support for the first type of reported trouble issue multiplied by the number of deflected calls having the first type of trouble issue, as shown at step 508. The method further includes determining a second cost savings estimate by multiplying the average cost of call center support for a second type of reported trouble issue with a number of recorded deflected calls having the second type of reported trouble issue, as shown at step 510. An example of the first trouble issue would be an email problem and an example of the second trouble issue class would be a broadband network connectivity failure. The method further includes determining a total cost savings estimate by adding the first cost savings estimate and the second cost savings estimate, as shown at 512. Additional types of reported trouble items and the associated cost savings for calls deflected with those trouble items may also be added to the total cost savings estimate. A report then may be generated to display the total cost savings estimate, as shown at step 514.


Referring to FIG. 6, a method of identifying and tracking call deflection from use of a computer software self-support tool is shown. The method starts, as shown at step 602, and proceeds to step 604 where a customer has a problem while using a particular software program. The customer uses a computer software self-support tool to attempt resolution of the problem, as shown at step 606, and the computer software self-support tool takes an action to resolve the problem, as shown at step 608. The computer software self-support tool reports the trouble issue, a customer identification, and the steps taken for resolution of the reported problem, as shown at step 610.


At decision step 612, it is determined whether the computer software self-support tool acted to resolve the particular reported trouble issue. If the self-support tool acted to resolve the trouble issue then processing proceeds to decision step 614. Where the self-support tool did not act to support the problem, the method proceeds to step 616, where data is collected to indicate that the support tool was unable to resolve the trouble issue, and the problem is recorded for a future tool update. Processing ends at 622.


Referring back to decision step 614, the customer ID is compared against call log data from a call center to determine if the customer called for agent support. If the customer called for support, the support call was not deflected and the lack of call deflection is recorded for return on investment measurement information, as shown at step 614, and processing ends, as shown at step 622. In the case where the customer did not call for support, then the customer call was successfully deflected and the call deflection is recorded for measurement purposes, as shown at step 620. The method ends, as shown at step 622.


In one exemplary embodiment, software, including self-support tools and other software applications, can report, through a network connection, such as a dial-up connection or a broadband transport connection, information about the software, such as version information, capabilities, and configuration information. This information may be associated with a customer identifier, such as a customer number, a software license code, or an account number. The information and the customer identifier may be accessible to an IVR system. Upon determining the customer identifier associated with a support call, the IVR may use the information to direct the flow of customer support, such as selection of a customer support agent or steps suggested to mitigate a technical problem.


The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims
  • 1. A customer support calls system comprising: an interactive voice response system to receive a customer support call, to determine a caller identification associated with the customer support call, and to determine whether the a computer system associated with the customer support call˜includes an installed self-support tool;a self-support tool server to receive a self-support tool identifier from the computer system associated with the customer support call and to provide the self-support tool identifier to the interactive voice response system;wherein the interactive voice response system compares the caller identification associated with the customer support call to the self-support tool identifier provided by the self-support tool server to determine whether the computer system associated with the customer support call includes the installed self-support tool;a call center management system responsive to the interactive voice response system, the call center management system configured to direct the customer support call to a destination in response to determining whether the computer system associated with the customer support call includes the installed self-support tool;a call center metrics database responsive to the call center management system, the call center metrics database to store metrics data associated with the customer support call;a data warehouse responsive to the call center metrics database and responsive to the self-support tool server, the data warehouse to store the metrics data associated with the customer support call and to store the self-support tool identifier from the computer system associated with the customer support call; andan interface system to access the data warehouse and to display measurement data associated with effectiveness of the installed self-support tool.
  • 2. The customer support call system of claim 1, wherein the self-support tool server receives trouble issue data from the installed self-support tool.
  • 3. The customer support call system of claim 1, wherein the self-support tool server receives trouble issue data and resolution data from the installed self-support tool, and wherein the data warehouse stores the trouble issue data and the resolution data.
  • 4. The customer support call system of claim 1, wherein the measurement data includes a measurement of deflected calls.
  • 5. The customer support call system of claim 1, wherein the measurement data includes a return on investment associated with the installed self-support tool.
  • 6. A method of providing computer assisted user support to a user, the method comprising: receiving, at an interactive voice response system, a customer support call;determining, at the interactive voice response system, a caller identification associated with the customer support call;receiving, at a self-support tool server, a self-support tool identifier from a computer system associated with the customer support callcomparing, at the interactive voice response system, the caller identification information associated with the customer support call to the self-support tool identifier received at the self-support tool server to determine whether the computer system associated with the customer support call includes an installed self-support tool;directing the customer support call using a call center management system to a destination when the computer system includes the installed self-support tool;storing, at a call center metrics database, metrics data associated with the customer support call;storing, at a data warehouse, the self-support tool identifier from the computer system associated with the customer support call; andsending measurement data accessed from the data warehouse to an interface system for display, wherein the measurement data is associated with effectiveness of the installed self-support tool.
  • 7. The method of claim 6, further comprising notifying a support agent that the computer system associated with the customer support call includes the installed self-support tool.
  • 8. The method of claim 7, further comprising transferring the customer support call to the support agent.
  • 9. The method of claim 8, wherein the support agent follows a troubleshooting flow when the computer system associated with the customer support call includes the installed self-support tool.
  • 10. The method of claim 6, further comprising receiving, at the self-support tool server, notification of a trouble issue from the installed self-support tool.
  • 11. The method of claim 10, further comprising providing information associated with the notification of the trouble issue to a call center agent in conjunction with transferring the customer support call to the call center agent.
  • 12. The method of claim 6, wherein the caller identification is determined using automated number identification.
  • 13. The method of claim 6, further comprising determining whether the customer support call relates to installation activities associated with the installed self-support tool.
  • 14. A tangible computer readable storage memory storing computer executable instructions that, when executed by a computer, cause the computer to: receive a customer support call;determine a caller identification associated with the customer support call;receive a self-support tool identifier from a computer system associated with the customer support call;compare the caller identification information associated with the customer support call to the self-support tool identifier to determine whether the computer system associated with the customer support call includes an installed self-support tool;direct the customer support call to a destination when the computer system includes the installed self-support tool;store metrics data associated with the customer support call at a call center metrics database;store the self-support tool identifier from the computer system associated with the customer support call at a data warehouse in response to the call center metrics database and the self-support tool server; andsend measurement data associated with effectiveness of the installed self-support tool to an interface system for display.
  • 15. The computer readable storage medium of claim 14, wherein the measurement data includes a measurement of deflected calls.
  • 16. The computer readable storage medium of claim 14, wherein the measurement data includes return on investment information associated with the installed self-support tool.
  • 17. The computer readable storage medium of claim 14, wherein the caller identification is determined using automated number identification.
US Referenced Citations (186)
Number Name Date Kind
4953204 Cuschleg, Jr. et al. Aug 1990 A
4967405 Upp et al. Oct 1990 A
5335269 Steinlicht Aug 1994 A
5455903 Jolissaint et al. Oct 1995 A
5497373 Hulen et al. Mar 1996 A
5522046 McMillen et al. May 1996 A
5530744 Charalambous et al. Jun 1996 A
5555299 Maloney et al. Sep 1996 A
5590186 Liao et al. Dec 1996 A
5652789 Miner et al. Jul 1997 A
5754639 Flockhart et al. May 1998 A
5754978 Perez-Mendez et al. May 1998 A
5923745 Hurd Jul 1999 A
5940476 Morganstein et al. Aug 1999 A
5946388 Walker et al. Aug 1999 A
5953704 McIlroy et al. Sep 1999 A
5999965 Kelly Dec 1999 A
6002689 Christie et al. Dec 1999 A
6002760 Gisby Dec 1999 A
6003011 Sarin et al. Dec 1999 A
6049594 Furman et al. Apr 2000 A
6118866 Shtivelmann Sep 2000 A
6119101 Peckover Sep 2000 A
6173266 Marx et al. Jan 2001 B1
6173289 Sonderegger et al. Jan 2001 B1
6173399 Gilbrech Jan 2001 B1
6175621 Begeja Jan 2001 B1
6259786 Gisby Jul 2001 B1
6269153 Carpenter et al. Jul 2001 B1
6317439 Cardona et al. Nov 2001 B1
6333980 Hollatz et al. Dec 2001 B1
6353608 Cullers et al. Mar 2002 B1
6366658 Bjornberg et al. Apr 2002 B1
6366668 Borst et al. Apr 2002 B1
6381329 Uppaluru et al. Apr 2002 B1
6385584 McAllister et al. May 2002 B1
6389400 Bushey et al. May 2002 B1
6400804 Bilder Jun 2002 B1
6400996 Hoffberg et al. Jun 2002 B1
6405159 Bushey et al. Jun 2002 B2
6414966 Kulkarni et al. Jul 2002 B1
6418424 Hoffberg et al. Jul 2002 B1
6442247 Garcia Aug 2002 B1
6496567 Bjornberg et al. Dec 2002 B1
6510414 Chaves Jan 2003 B1
6519562 Phillips et al. Feb 2003 B1
6529871 Kanevsky et al. Mar 2003 B1
6553113 Dhir et al. Apr 2003 B1
6570967 Katz May 2003 B2
6584180 Nemoto Jun 2003 B2
6587556 Judkins et al. Jul 2003 B1
6598136 Norrod et al. Jul 2003 B1
6600736 Ball et al. Jul 2003 B1
6603854 Judkins et al. Aug 2003 B1
6614781 Elliott et al. Sep 2003 B1
6631186 Adams et al. Oct 2003 B1
6678360 Katz Jan 2004 B1
6678718 Khouri et al. Jan 2004 B1
6690788 Bauer et al. Feb 2004 B1
6694012 Posthuma Feb 2004 B1
6697460 Knott et al. Feb 2004 B2
6700972 McHugh et al. Mar 2004 B1
6704404 Burnett Mar 2004 B1
6707789 Arslan et al. Mar 2004 B1
6714631 Martin et al. Mar 2004 B1
6721416 Farrell Apr 2004 B1
6731722 Coffey May 2004 B2
6738473 Burg et al. May 2004 B1
6744861 Pershan et al. Jun 2004 B1
6744877 Edwards Jun 2004 B1
6751306 Himmel et al. Jun 2004 B2
6757306 Klish, II et al. Jun 2004 B1
6766320 Wang et al. Jul 2004 B1
6775359 Ron et al. Aug 2004 B1
6778643 Bushey et al. Aug 2004 B1
6792096 Martin et al. Sep 2004 B2
6807274 Joseph et al. Oct 2004 B2
6823307 Steinbiss et al. Nov 2004 B1
6831932 Boyle et al. Dec 2004 B1
6832224 Gilmour Dec 2004 B2
6842504 Mills et al. Jan 2005 B2
6847711 Knott et al. Jan 2005 B2
6853722 Joseph et al. Feb 2005 B2
6853966 Bushey et al. Feb 2005 B2
6859529 Duncan et al. Feb 2005 B2
6871212 Khouri et al. Mar 2005 B2
6879683 Fain et al. Apr 2005 B1
6885734 Eberle et al. Apr 2005 B1
6891932 Bhargava et al. May 2005 B2
6895083 Bers et al. May 2005 B1
6895532 Raynham May 2005 B2
6901366 Kuhn et al. May 2005 B1
6907119 Case et al. Jun 2005 B2
6915246 Gusler et al. Jul 2005 B2
6963983 Munson et al. Nov 2005 B2
7006605 Morganstein et al. Feb 2006 B1
7379886 Zaring et al. May 2008 B1
7430554 Heisinger, Jr. Sep 2008 B1
20010011211 Bushey et al. Aug 2001 A1
20010018672 Petters et al. Aug 2001 A1
20010021948 Khouri et al. Sep 2001 A1
20010032229 Hulls et al. Oct 2001 A1
20010034662 Morris Oct 2001 A1
20020046030 Haritsa et al. Apr 2002 A1
20020057678 Jiang et al. May 2002 A1
20020059164 Shtivelman May 2002 A1
20020059169 Quarterman et al. May 2002 A1
20020067714 Crain et al. Jun 2002 A1
20020087385 Vincent Jul 2002 A1
20020114432 Shaffer et al. Aug 2002 A1
20020133394 Bushey et al. Sep 2002 A1
20020133413 Chang et al. Sep 2002 A1
20020135618 Maes et al. Sep 2002 A1
20020156699 Gray et al. Oct 2002 A1
20020165732 Ezzeddine et al. Nov 2002 A1
20020196277 Bushey et al. Dec 2002 A1
20030026409 Bushey et al. Feb 2003 A1
20030035381 Chen et al. Feb 2003 A1
20030035516 Guedalia Feb 2003 A1
20030069937 Khouri et al. Apr 2003 A1
20030097428 Afkhami et al. May 2003 A1
20030103619 Brown et al. Jun 2003 A1
20030114105 Haller et al. Jun 2003 A1
20030118159 Shen et al. Jun 2003 A1
20030130864 Ho et al. Jul 2003 A1
20030143981 Kortum et al. Jul 2003 A1
20030144846 Denenberg et al. Jul 2003 A1
20030144919 Trompette et al. Jul 2003 A1
20030156133 Martin et al. Aug 2003 A1
20030165223 Timmins et al. Sep 2003 A1
20030187732 Seta Oct 2003 A1
20030187773 Santos et al. Oct 2003 A1
20030194063 Martin et al. Oct 2003 A1
20030195753 Homuth Oct 2003 A1
20030202640 Knott et al. Oct 2003 A1
20030202643 Joseph et al. Oct 2003 A1
20030202649 Haug, Jr. et al. Oct 2003 A1
20030204435 McQuilkin et al. Oct 2003 A1
20030228007 Kurosaki Dec 2003 A1
20030235287 Margolis Dec 2003 A1
20040005047 Joseph et al. Jan 2004 A1
20040006473 Mills et al. Jan 2004 A1
20040032862 Schoeneberger et al. Feb 2004 A1
20040032935 Mills et al. Feb 2004 A1
20040042592 Knott et al. Mar 2004 A1
20040044950 Mills et al. Mar 2004 A1
20040066401 Bushey et al. Apr 2004 A1
20040066416 Knott et al. Apr 2004 A1
20040073569 Knott et al. Apr 2004 A1
20040083206 Wu et al. Apr 2004 A1
20040083479 Bondarenko et al. Apr 2004 A1
20040088285 Martin et al. May 2004 A1
20040103017 Reed et al. May 2004 A1
20040109555 Williams Jun 2004 A1
20040120473 Birch et al. Jun 2004 A1
20040125937 Turcan et al. Jul 2004 A1
20040125938 Turcan et al. Jul 2004 A1
20040125940 Turcan et al. Jul 2004 A1
20040161078 Knott et al. Aug 2004 A1
20040161094 Martin et al. Aug 2004 A1
20040161096 Knott et al. Aug 2004 A1
20040174980 Knott et al. Sep 2004 A1
20040230438 Pasquale et al. Nov 2004 A1
20040240635 Bushey et al. Dec 2004 A1
20040243568 Wang et al. Dec 2004 A1
20050008141 Kortum et al. Jan 2005 A1
20050015744 Bushey et al. Jan 2005 A1
20050027535 Martin et al. Feb 2005 A1
20050041796 Joseph et al. Feb 2005 A1
20050047578 Knott et al. Mar 2005 A1
20050055216 Bushey et al. Mar 2005 A1
20050058264 Joseph et al. Mar 2005 A1
20050075894 Bushey et al. Apr 2005 A1
20050078805 Mills et al. Apr 2005 A1
20050080630 Mills et al. Apr 2005 A1
20050080667 Knott et al. Apr 2005 A1
20050086630 Chefalas et al. Apr 2005 A1
20050131892 Knott et al. Jun 2005 A1
20050132262 Bushey et al. Jun 2005 A1
20050135595 Bushey et al. Jun 2005 A1
20050141692 Scherer et al. Jun 2005 A1
20050169441 Yacoub et al. Aug 2005 A1
20050169453 Knott et al. Aug 2005 A1
20050201547 Burg et al. Sep 2005 A1
20050240411 Yacoub Oct 2005 A1
20060002540 Kreiner et al. Jan 2006 A1
Foreign Referenced Citations (9)
Number Date Country
0 424 015 Apr 1991 EP
0 424 015 Apr 1991 EP
0 424 015 Apr 1991 EP
0 876 652 Sep 1996 EP
WO 9726612 Jul 1997 WO
WO 0137539 May 2001 WO
WO 0137539 May 2001 WO
WO 2004017584 Feb 2004 WO
WO 2004049222 Jun 2004 WO
Related Publications (1)
Number Date Country
20060039547 A1 Feb 2006 US