1. Field of the Invention
The present invention relates to the field of telecommunications. More particularly, the present invention relates to an interactive voice response (IVR) system for managing customer calls.
2. Acronyms
The written description provided herein contains acronyms which refer to various telecommunications services, components and techniques, as well as features relating to the present invention. Although some of these acronyms are known, use of these acronyms is not strictly standardized in the art. For purposes of the written description herein, acronyms will be defined as follows:
Dual Tone Multi Frequency (DTMF)
Interactive Voice Response (IVR)
3. Description of Background Information
Many companies utilize IVR call management systems in order to handle and route incoming telephone calls. This is especially true for calls not requiring a live operator to assist the caller. UVR systems have been phenomenally successful and enjoy widespread use because they generate enormous cost savings at customer call centers, due to a reduction in required staff.
Conventional IVR systems are well-suited to providing small amounts of information to a user in real-time. However, conventional UVR systems have shortcomings, particularly with respect to larger amounts of information or instruction sets longer than one or two sentences. The primary reason for this shortcoming is the short-term memory and cognitive limitations inherent in the average caller. That is, most callers are not well adapted to remembering long strings of information (e.g., a long sequential recitation of tasks) presented in a short period of time, especially when sequence-specific procedures are presented. Further, conventional IVR systems require the caller to remember various navigational control keys, i.e., forward, backward, repeat, continue, etc. Moreover, conventional IVR systems lack the ability and flexibility to present long, detailed sequential instructions sets to a caller in a manner suitable to the average caller's cognitive capabilities. Further, conventional IVR systems also assume that the caller has performed a particular step correctly. Successive steps may be impossible to perform when a previous step has been performed incorrectly. This approach may lead to customer frustration and dissatisfaction.
As a result, it would be desirable to have a IWR system that would allow a caller to perform a series of sequential tasks, based on an instruction set, at the caller's own pace.
The present invention overcomes the problems associated with the prior art.
The present invention is further described in the detailed description that follows, by reference to the noted plurality of drawings by way of non-limiting examples of embodiments of the present invention, in which like reference numerals represent similar parts throughout several views of the drawings, and in which:
In view of the foregoing, the present invention, through one or more of its various aspects and/or embodiments is thus presented to provide an interactive voice response (VR) system for managing customer calls.
Accordingly, one aspect of the present invention is to provide a method for sequentially presenting instructions in a telephone call placed to an IVR system of a customer service center. The method includes receiving a call from a caller, presenting a main menu to the caller that includes multiple messages in which each message represents a procedure, and prompting the caller to select from one of the main menu messages. The method further includes presenting a sequence of instructions to the caller according to the caller's main menu selection, in which each instruction identifies a task to be performed by the caller that is distinct from interaction with the IVR system and wherein the tasks collectively constitute the procedure, The sequence of instructions are automatically paused after each instruction for a predetermined amount of time so as to permit the caller to perform the task identified in an instruction. Then, the caller is queried after each instruction as to whether the caller has performed the task identified in the instruction.
The method may further include periodically re-presenting the instruction to the caller until the caller indicates that the caller has performed the task identified in the instruction. Also, the method may include transferring the caller to a service representative after the instruction has been re-presented to the caller for a predetermined number of times. The sequence of instructions may be paused at the caller's request.
A summary of the sequence of the instructions may be presented to the caller immediately after the caller's selection, after the sequence of instructions has been presented to the caller, or immediately after the caller's selection and after the sequence of instructions has been presented to the caller.
The method may include presenting a previously presented instruction to the caller in response to a caller's indication that the caller has not performed the task identified in the previously presented instruction. Further, additional information associated with the instruction may be presented to the caller upon the caller's request, which is followed by a recommencement of the sequence of instructions.
The method may include querying the caller after the caller indicates that the caller has performed a task identified in the instruction as to whether the task identified in the instruction was performed correctly. The instruction may be re-presented to the caller in response to the caller's indication that the task identified in the instruction was not performed correctly. Further the caller may be queried as to whether the procedure was performed correctly. The sequence of instructions may be re-presented to the caller in response to the caller's indication that the procedure was not performed correctly.
The method may also include transferring the call from a position in the sequence of instructions to a service representative and transferring the call back to the position in the sequence of instructions. Alternatively, the method may include transferring the call from a position in the sequence of instructions to a service representative and transferring the call back to a location in the sequence of instructions other than the position.
Further, the method may include re-presenting apreviously presented instruction to the caller in response to the caller's request receive a previously presented instruction. Also, the method may include re-presenting a previously presented instruction to the caller, as requested by the caller during a recitation of previously presented instructions. The method may further include presenting the caller with troubleshooting information in response to the caller's request for troubleshooting information.
Accordingly, another aspect of the present invention is to provide a system for receiving telephone calls at a customer service center. The system includes an IVR unit that presents a main menu of messages to a caller, presents a sequence of instructions to the caller and automatically pauses the sequence of instructions after each instruction by a predetermined amount of time so as to permit the caller to perform a task identified in an instruction that is distinct from interaction with the IVR. The IVR unit queries the caller after each instruction as to whether the caller has performed the task identified in the instruction. Each main menu message represents a procedure and each instruction identifies a task to be performed by the caller.
The system may include a component that transfers a call from a position in the sequence of instructions to a service representative and transfers the call back to the position in the sequence of instructions. Further, the system may include a component that transfers a call from a position in the sequence of instructions to a service representative and transfers the call back to a location in the sequence of instructions other than the position.
Accordingly, another aspect of the present invention is to provide a computer readable medium for storing a computer program that processes a telephone call in an IVR system. A presenting source code segment is provided that presents a main menu of messages to a caller and presents a sequence of instructions to the caller in which each instruction identifies a task distinct from interaction with the IVR system. A pausing source code segment is provided that pauses the sequence of instructions after each instruction for a predetermined amount of time so as to permit the caller to perform a task identified in an instruction A querying source code segment is also provided that queries the caller after each instruction as to whether the caller performed the task identified in the instruction.
The presenting source code segment may periodically re-present the instruction to the caller until the caller indicates that the caller has performed the task identified in the instruction. Also, a transferring source code segment may be provided that transfers the call to a service representative after the instruction has been re-presented to the caller for a predetermined number of times. Further, the pausing source code segment may pause the sequence of instructions in response to the caller's command to do so.
The presenting source code segment may present a summary of the sequence of the instructions to the caller immediately after the caller's selection, after the sequence of instructions has been presented to the caller, or immediately after the caller's selection and after the sequence of instructions has been presented to the caller.
Further, the presenting source code segment may present a previously presented instruction to a caller in response to a caller's indication that the caller has not performed the task identified in the previously presented instruction. Also, the presenting source code segment may present additional information associated with the instruction in response to the caller's request for additional information, followed by a recommencement of the sequence of instructions.
The querying source code segment may query the caller, after the caller indicates that the caller has performed the task identified in the instruction, as to whether the task identified in the instruction was performed correctly. Further, the presenting source code segment may re-present the instruction to the caller in response to the caller's indication that the task identified in the instruction was not performed correctly.
Also, the querying source code segment may query the caller as to whether the procedure was performed correctly. Further, the presenting source code segment may represent the sequence of instructions to the caller in response to the caller's indication that the procedure was not performed correctly.
Further, a transferring source code segment may be provided that transfers the call from a position in the sequence of instructions to a service representative and transfers the call back to the position in the sequence of instructions. Alternatively, a transferring source code segment may be provided that transfers the call from a position in the sequence of instructions to a service representative and transfers the call back to a location in the sequence of instructions other than the position.
Still further, the presenting source code segment may re-present an instruction to the caller in response to the caller's command to receive a previously presented instruction. Also, the presenting source code segment may re-present a previously presented instruction to the caller, as requested by the caller during a recitation of previously presented instructions.
The present invention relates to an IVR system that allows a caller to receive a sequence of instructions and perform the instructed steps at the callers own pace. Customers often have difficulties when performing complex tasks, e.g., installing computer hardware and/or software. Some of the difficulties arise from inexperience on the part of the customer. Other times, the problems are associated with the customer's equipment. In any event, customers may require detailed, sequential instructions in order to performing various procedures. This is especially true with respect to computer and telecommunications applications. Unfortunately, instructions in these disciplines tend to be long. Moreover, customers will undoubtedly have questions and make mistakes. As a result, a certain amount of hand-holding is necessary, while not frustrating experienced customers or creating excessively long IVR calls.
In one embodiment, the IVR system employs, as a non-limiting example, the Nortel Networks Periphonics Voice Processing Series Information Server VPS/is 2 model. The IVR call management system may use Periphonics Operating System 5.3-1 (or higher version) running on a Sparc workstation available from Sun Microsystems, Inc. The Sparc workstation may be equipped, for example, with Sun Operating System 5.6 (or higher version). Other systems can also be equipped without deviating from the scope and spirit of the present invention.
Next, the caller is presented with an instruction set comprising a series of sub-instructions (i.e., tasks), e.g., represented by a, b, c, d, e, . . . . If procedure x is chosen by the caller, main menu variable “MM” is set to x (i.e., MM=x) and sub-instruction Identification “SI ID” is set to “a” (i.e., SI ID=a), at step s8. The variables MM and SI ID are used by the IVR system to determine which messages to present to the caller. At step s10, sub-instruction “a” is played to the caller. At step s12, MM=x and SI ID=b. Thus, at step s14 sub-instruction “b” is played to the caller. At step s16, MM=x and SI ID=c. As a result, at step s18 sub-instruction “c” is played to the caller. At step s20, MM=x and SI ID=d. Accordingly, at step s22 sub-instruction “d” is played to the caller. Recitation of the sub-instructions proceeds in this fashion until all of the sub-instructions have been presented.
After all of the sub-instructions have been presented and successfully performed, the caller can elect to receive a summary of all of the steps, in order to ensure that all of the steps have been completed. If the user is uncertain about successful completion of any or all of the steps recited in the summary, they would be provided an opportunity to return to any point in the instruction set. Thus, the caller may receive a summary of the instructions before and/or after performing the steps. In
After the sub-instruction is presented to the caller, the caller may input a dual tone multi frequency (DTMF) command, by pressing a key, at step s30 for various options, based upon prompting by the system. The prompting may be provided prior to any sub-instructions are presented, especially if the sub-instructions are relatively short. Alternatively, the prompting may be included at the end of each sub-instruction. In any event, exemplary prompting may advise the caller to select “0” to pause, select “1” to unpause, select “2” to repeat the instruction, select “3” to return to the main menu, and select “4” to receive detailed instructions. If the caller selects “0”, the instruction set is paused (step s32) as will be discussed below. If the caller selects “1”, the pause command is canceled (step s34). If the caller selects “2”, the previous instruction is repeated (step s36). If the caller selects “3”, the caller is returned to the main menu at step s4 (step s38). If the caller selects “4”, detailed instructions are presented to the caller as will be discussed below (step s40). If no command is entered by the caller, processing continues at step s42.
At step s42, the caller is queried as to whether the task was completed (e.g., “Done yet?”). The prompt will be repeatedly presented to the caller at predetermined intervals (e.g., every 5 seconds) in a looping fashion, giving the caller sufficient time to perform the task. The repeated prompting serves to keep the caller focused on the particular task. It has been observed that persons performing tasks previously foreign to them are often times overwhelmed and may understandably exhibit anxiety, tentativeness, and confusion. Hence, keeping the caller focused is a key objective. Also, the repeated prompting serves as a reminder of what task to perform in a series of tasks, making certain that a step is not inadvertently omitted. The repeated prompting also includes and serves as a checklist, should the user become distracted during completion of a particular task.
If the “Done yet?” query is presented to the caller for a predetermined number of times (e.g., five times), it may be indication that the caller has encountered a problem. Therefore, in an alternative embodiment, the caller may be redirected to a service representative, for example, if the predetermined number of times condition is satisfied.
If the caller selects “1” at step s44 indicating the task was completed, call processing continues at a correct completion branch (i.e., task correct) as will be discussed below (step s46). If the caller selects “2” at step s44, the sub-instruction is repeated to the caller and the caller remains in a sub-instruction loop (step s48). If the caller selects “3” at step s44, the caller is transferred to the main menu at step s4 (step s50). If the caller selects “4” at step s44, the instruction set is backed up to the previous instruction (step s52). If the caller selects “5” at step s44, the call completion prompt loop continues and the “Done yet?” prompt is repeated (step s54). If the caller selects “6” at step s44, the call is transferred to a service representative, as will be discussed below (step s56).
Referring to an earlier point in
If the caller selects “3” at step s60, the pause branch processing continues (step s32) and the caller is prompted at a predetermined intervals (e.g., every 5 seconds) as to whether they would like to unpause the system. As explained, the pause branch processing continues until the caller exits the loop by selecting “1” or “2”.
Referring to
Referring to
Rather than, or in addition to, querying the caller after each sub-instruction as to whether the task was performed correctly, the caller may be queried after the entire procedure is completed (e.g., “Was the procedure a success?”). In this case, if the caller selects “1”, the system begins the exiting procedure and the call is disconnected. If the caller selects “2”, call processing is sent to a troubleshooting branch. If the caller selects “3”, the entire set of sub-instructions is re-started, so that the caller may trace all of the steps.
If the caller selects “4” at step s44, the call is backed up.
If the caller selects “6” at step s44, the call is transferred to a service representative.
At step s5, the caller selects “1” from the main menu in order to receive instructions on installing a network card. At step s7, sub-instruction “a” is presented to the caller instructing the caller, i.e., “Turn off the computer”. At step s9, sub-instruction “b” is presented to the caller, i.e., “Open the computer case”. At step s11, sub-instruction “c” is presented to the caller, i.e., “Take the PCI slot cover out using a screwdriver”. At step s13, sub-instruction “d” is presented to the caller, i.e., “Insert the card. Push firmly to ensure that it is seated”. At step s15, sub-instruction “d” is presented to the caller, i.e., “Put the cover back on and re-start the computer”. A step (not shown) may be provided giving the caller the option of receiving a recap of the instruction set. In
The IVR system recognizes that caller may take some time to complete the sub-instruction. As a result, the call flow continues in a loop until the caller indicates completion of the sub-instruction. Referring to
As shown, the present IVR system allows a caller to perform a series of sequential tasks based on an instruction set. The caller is queried after each instruction to ensure that the caller has successfully completed all of the steps for that instruction. Additionally, provision is made to automatically pause the instruction set and present reminders to the caller. Further the caller may elect to repeat instructions, back up the instruction set, receive additional details, transfer to a service representative, or receive summary information.
Although the invention has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the invention in its aspects. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed; rather, the invention extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims. For instance, it should be understood that callers may select menu messages via any means including DTMF input or spoken word. Further, it is to be understood that the specific menu selections discussed herein (e.g., “press 1”) are representational in nature and that any suitable selections may be employed.
In accordance with various embodiments of the present invention, the methods described herein are intended for operation as software programs running on a computer processor. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.
It should also be noted that the software implementations of the present invention as described herein are optionally stored on a tangible storage medium, such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories. Accordingly, the invention is considered to include a tangible storage medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.
Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. Each of the standards, including standards for the IVR system, represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents.
This application is a continuation application of pending U.S. patent application Ser. No. 11/876,525, which was filed on Oct. 22, 2007, which is a continuation application of U.S. patent application Ser. No. 10/058,785, which was filed on Jan. 30, 2002, now U.S. Pat. No. 7,305,070, the contents of which are expressly incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4310727 | Lawser | Jan 1982 | A |
4694483 | Cheung | Sep 1987 | A |
4761542 | Kubo et al. | Aug 1988 | A |
4922519 | Daudelin | May 1990 | A |
4930077 | Fan | May 1990 | A |
4964077 | Eisen et al. | Oct 1990 | A |
5115501 | Kerr | May 1992 | A |
5147205 | Gross et al. | Sep 1992 | A |
5181259 | Rorvig | Jan 1993 | A |
5204968 | Parthasarathi | Apr 1993 | A |
5206903 | Kohler et al. | Apr 1993 | A |
5263167 | Conner, Jr. et al. | Nov 1993 | A |
5299260 | Shaio | Mar 1994 | A |
5311422 | Loftin et al. | May 1994 | A |
5323452 | Dickman et al. | Jun 1994 | A |
5327529 | Fults et al. | Jul 1994 | A |
5329578 | Brennan et al. | Jul 1994 | A |
5335268 | Kelly, Jr. et al. | Aug 1994 | A |
5335269 | Steinlicht | Aug 1994 | A |
5371673 | Fan | Dec 1994 | A |
5384831 | Creswell et al. | Jan 1995 | A |
5388198 | Layman et al. | Feb 1995 | A |
5420975 | Blades et al. | May 1995 | A |
5479488 | Lennig et al. | Dec 1995 | A |
5493608 | O'Sullivan | Feb 1996 | A |
5495567 | Iizawa et al. | Feb 1996 | A |
5500795 | Powers et al. | Mar 1996 | A |
5519772 | Akman et al. | May 1996 | A |
5530744 | Charalambous et al. | Jun 1996 | A |
5533107 | Irwin et al. | Jul 1996 | A |
5535321 | Massaro et al. | Jul 1996 | A |
5537470 | Lee | Jul 1996 | A |
5553119 | McAllister et al. | Sep 1996 | A |
5561711 | Muller | Oct 1996 | A |
5566291 | Boulton et al. | Oct 1996 | A |
5586060 | Kuno et al. | Dec 1996 | A |
5586171 | McAllister et al. | Dec 1996 | A |
5586219 | Yufik | Dec 1996 | A |
5594791 | Szlam et al. | Jan 1997 | A |
5600781 | Root et al. | Feb 1997 | A |
5615323 | Engel et al. | Mar 1997 | A |
5633909 | Fitch | May 1997 | A |
5657383 | Gerber et al. | Aug 1997 | A |
5659724 | Borgida et al. | Aug 1997 | A |
5666400 | McAllister et al. | Sep 1997 | A |
5668856 | Nishimatsu et al. | Sep 1997 | A |
5671351 | Wild et al. | Sep 1997 | A |
5675707 | Gorin et al. | Oct 1997 | A |
5684870 | Maloney et al. | Nov 1997 | A |
5684872 | Flockhart et al. | Nov 1997 | A |
5706334 | Balk et al. | Jan 1998 | A |
5710884 | Dedrick | Jan 1998 | A |
5727950 | Cook et al. | Mar 1998 | A |
5729600 | Blaha et al. | Mar 1998 | A |
5734709 | DeWitt et al. | Mar 1998 | A |
5740549 | Reilly et al. | Apr 1998 | A |
5757644 | Jorgensen et al. | May 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5771276 | Wolf | Jun 1998 | A |
5790117 | Halviatti et al. | Aug 1998 | A |
5793368 | Beer | Aug 1998 | A |
5802526 | Fawcett et al. | Sep 1998 | A |
5806060 | Borgida et al. | Sep 1998 | A |
5808908 | Ghahramani | Sep 1998 | A |
5809282 | Cooper et al. | Sep 1998 | A |
5812975 | Komori et al. | Sep 1998 | A |
5819221 | Kondo et al. | Oct 1998 | A |
5821936 | Shaffer et al. | Oct 1998 | A |
5822397 | Newman | Oct 1998 | A |
5822744 | Kesel | Oct 1998 | A |
5825856 | Porter et al. | Oct 1998 | A |
5825869 | Brooks et al. | Oct 1998 | A |
5832428 | Chow et al. | Nov 1998 | A |
5832430 | Lleida et al. | Nov 1998 | A |
5835565 | Smith et al. | Nov 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5864605 | Keshav | Jan 1999 | A |
5864844 | James et al. | Jan 1999 | A |
5870308 | Dangelo et al. | Feb 1999 | A |
5872865 | Normile et al. | Feb 1999 | A |
5873068 | Beaumont et al. | Feb 1999 | A |
5875108 | Hoffberg et al. | Feb 1999 | A |
5884029 | Brush, II et al. | Mar 1999 | A |
5884262 | Wise et al. | Mar 1999 | A |
5899992 | Iyer et al. | May 1999 | A |
5903641 | Tonisson | May 1999 | A |
5905774 | Tatchell et al. | May 1999 | A |
5920477 | Hoffberg et al. | Jul 1999 | A |
5923745 | Hurd | Jul 1999 | A |
5943416 | Gisby | Aug 1999 | A |
5953406 | LaRue et al. | Sep 1999 | A |
5963965 | Vogel | Oct 1999 | A |
5974253 | Nahaboo et al. | Oct 1999 | A |
5991735 | Gerace | Nov 1999 | A |
5999611 | Tatchell et al. | Dec 1999 | A |
5999908 | Abelow | Dec 1999 | A |
6014638 | Burge et al. | Jan 2000 | A |
6016336 | Hanson | Jan 2000 | A |
6026381 | Barton, III et al. | Feb 2000 | A |
6032129 | Greef et al. | Feb 2000 | A |
6035283 | Rofrano | Mar 2000 | A |
6035336 | Lu et al. | Mar 2000 | A |
6038560 | Wical | Mar 2000 | A |
6044355 | Crockett et al. | Mar 2000 | A |
6052693 | Smith et al. | Apr 2000 | A |
6055542 | Nielsen et al. | Apr 2000 | A |
6058163 | Pattison et al. | May 2000 | A |
6058179 | Shaffer et al. | May 2000 | A |
6058435 | Sassin et al. | May 2000 | A |
6061433 | Polcyn et al. | May 2000 | A |
6067538 | Zorba et al. | May 2000 | A |
6088429 | Garcia | Jul 2000 | A |
6099320 | Papadopoulos | Aug 2000 | A |
6104790 | Narayanaswami | Aug 2000 | A |
6128380 | Shaffer et al. | Oct 2000 | A |
6128624 | Papierniak et al. | Oct 2000 | A |
6134315 | Galvin | Oct 2000 | A |
6134530 | Bunting et al. | Oct 2000 | A |
6148063 | Brennan et al. | Nov 2000 | A |
6157808 | Hollingsworth | Dec 2000 | A |
6160877 | Tatchell et al. | Dec 2000 | A |
6161130 | Horvitz et al. | Dec 2000 | A |
6163607 | Bogart et al. | Dec 2000 | A |
6166732 | Mitchell et al. | Dec 2000 | A |
6170011 | Macleod Beck et al. | Jan 2001 | B1 |
6173053 | Bogart et al. | Jan 2001 | B1 |
6173279 | Levin et al. | Jan 2001 | B1 |
6201948 | Cook et al. | Mar 2001 | B1 |
6208970 | Ramanan | Mar 2001 | B1 |
6212502 | Ball et al. | Apr 2001 | B1 |
6219665 | Shiomi | Apr 2001 | B1 |
6230197 | Beck et al. | May 2001 | B1 |
6236395 | Sezan et al. | May 2001 | B1 |
6236955 | Summers | May 2001 | B1 |
6236990 | Geller et al. | May 2001 | B1 |
6243375 | Speicher | Jun 2001 | B1 |
6249579 | Bushnell | Jun 2001 | B1 |
6263051 | Saylor et al. | Jul 2001 | B1 |
6263052 | Cruze | Jul 2001 | B1 |
6269153 | Carpenter et al. | Jul 2001 | B1 |
6278976 | Kochian | Aug 2001 | B1 |
6282404 | Linton | Aug 2001 | B1 |
6289084 | Bushnell | Sep 2001 | B1 |
6292909 | Hare | Sep 2001 | B1 |
6295551 | Roberts et al. | Sep 2001 | B1 |
6296376 | Kondo et al. | Oct 2001 | B1 |
6308172 | Agrawal et al. | Oct 2001 | B1 |
6330326 | Whitt | Dec 2001 | B1 |
6332154 | Beck et al. | Dec 2001 | B2 |
6336109 | Howard | Jan 2002 | B2 |
6338050 | Conklin et al. | Jan 2002 | B1 |
6349290 | Horowitz et al. | Feb 2002 | B1 |
6349410 | Lortz | Feb 2002 | B1 |
6353661 | Bailey, III | Mar 2002 | B1 |
6353825 | Ponte | Mar 2002 | B1 |
6357017 | Bereiter et al. | Mar 2002 | B1 |
6366879 | Coxhead et al. | Apr 2002 | B1 |
6373817 | Kung et al. | Apr 2002 | B1 |
6374260 | Hoffert et al. | Apr 2002 | B1 |
6381640 | Beck et al. | Apr 2002 | B1 |
6389400 | Bushey et al. | May 2002 | B1 |
6389403 | Dorak, Jr. | May 2002 | B1 |
6389538 | Gruse et al. | May 2002 | B1 |
6400807 | Hewitt et al. | Jun 2002 | B1 |
6405149 | Tsai et al. | Jun 2002 | B1 |
6405159 | Bushey et al. | Jun 2002 | B2 |
6405170 | Phillips et al. | Jun 2002 | B1 |
6411687 | Bohacek et al. | Jun 2002 | B1 |
6418216 | Harrison et al. | Jul 2002 | B1 |
6434714 | Lewis et al. | Aug 2002 | B1 |
6448980 | Kumar et al. | Sep 2002 | B1 |
6456619 | Sassin et al. | Sep 2002 | B1 |
6456699 | Burg et al. | Sep 2002 | B1 |
6459912 | Moeller et al. | Oct 2002 | B1 |
6483523 | Feng | Nov 2002 | B1 |
6487277 | Beyda et al. | Nov 2002 | B2 |
6510411 | Norton et al. | Jan 2003 | B1 |
6516051 | Sanders | Feb 2003 | B2 |
6539080 | Bruce et al. | Mar 2003 | B1 |
6564197 | Sahami et al. | May 2003 | B2 |
6587127 | Leeke et al. | Jul 2003 | B1 |
6598022 | Yuschik | Jul 2003 | B2 |
6600821 | Chan et al. | Jul 2003 | B1 |
6618715 | Johnson et al. | Sep 2003 | B1 |
6624803 | Vanderheiden et al. | Sep 2003 | B1 |
6651755 | Kelpe | Nov 2003 | B1 |
6654447 | Dewan | Nov 2003 | B1 |
6658389 | Alpdemir | Dec 2003 | B1 |
6728685 | Ahluwalia | Apr 2004 | B1 |
6741967 | Wu et al. | May 2004 | B1 |
6778643 | Bushey et al. | Aug 2004 | B1 |
6778651 | Jost et al. | Aug 2004 | B1 |
RE38649 | Setlur et al. | Nov 2004 | E |
6826173 | Kung et al. | Nov 2004 | B1 |
6970551 | Costrell et al. | Nov 2005 | B2 |
6980963 | Hanzek | Dec 2005 | B1 |
7006487 | Ma et al. | Feb 2006 | B1 |
7085257 | Karves et al. | Aug 2006 | B1 |
7305070 | Kortum et al. | Dec 2007 | B2 |
7453994 | Kortum et al. | Nov 2008 | B2 |
20010014863 | Williams, III | Aug 2001 | A1 |
20010014868 | Herz et al. | Aug 2001 | A1 |
20010041562 | Elsey et al. | Nov 2001 | A1 |
20020055868 | Dusevic et al. | May 2002 | A1 |
20020133394 | Bushey et al. | Sep 2002 | A1 |
20020196277 | Bushey et al. | Dec 2002 | A1 |
20030026409 | Bushey et al. | Feb 2003 | A1 |
20030033294 | Walker et al. | Feb 2003 | A1 |
20030055974 | Brophy et al. | Mar 2003 | A1 |
20030143981 | Kortum et al. | Jul 2003 | A1 |
20030156133 | Martin et al. | Aug 2003 | A1 |
20030156706 | Koehler et al. | Aug 2003 | A1 |
20030158655 | Obradovich et al. | Aug 2003 | A1 |
20030161464 | Rodriguez et al. | Aug 2003 | A1 |
20040006473 | Mills et al. | Jan 2004 | A1 |
20040032935 | Mills et al. | Feb 2004 | A1 |
20040042592 | Knott et al. | Mar 2004 | A1 |
20040062371 | Maropis et al. | Apr 2004 | A1 |
20040077347 | Lauber et al. | Apr 2004 | A1 |
20040090950 | Lauber et al. | May 2004 | A1 |
20040179659 | Byrne et al. | Sep 2004 | A1 |
20040240635 | Bushey et al. | Dec 2004 | A1 |
20050163304 | Judkins et al. | Jul 2005 | A1 |
20050232250 | Craig et al. | Oct 2005 | A1 |
20080089491 | Kortum et al. | Apr 2008 | A1 |
20090034697 | Kortum et al. | Feb 2009 | A1 |
Number | Date | Country |
---|---|---|
01283969 | May 2000 | GB |
9906929 | Feb 1999 | WO |
0033548 | Jun 2000 | WO |
0073968 | Feb 2003 | WO |
03013111 | Feb 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20090034697 A1 | Feb 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11876525 | Oct 2007 | US |
Child | 12251153 | US | |
Parent | 10058785 | Jan 2002 | US |
Child | 11876525 | US |