System and method for speech-enabled call routing

Information

  • Patent Grant
  • 8503662
  • Patent Number
    8,503,662
  • Date Filed
    Wednesday, May 26, 2010
    14 years ago
  • Date Issued
    Tuesday, August 6, 2013
    11 years ago
Abstract
A method includes receiving speech of a call from a caller at a processor of a call routing system. The method includes using the processor to determine a first call destination for the call based on the speech. The method includes using the processor to determine whether the caller is in compliance with at least one business rule related to an account of the caller. The method includes routing the call to the first call destination when the caller is in compliance with the at least one business rule and routing the call to a second call destination when the caller is not in compliance with the at least one business rule.
Description
FIELD OF THE DISCLOSURE

The present disclosure relates generally to speech recognition systems and more particularly to speech recognition-enabled automatic call routing systems and methods.


BACKGROUND

Speech recognition systems are specialized computers that are configured to process and recognize human speech and may also take action or carry out further processes. Developments in speech recognition technologies support “natural language” type interactions between automated systems and users. A natural language interaction allows a person to speak naturally. Speech recognition systems can react responsively to a spoken request. An application of natural language processing is speech recognition with automatic call routing (ACR). A goal of an ACR application is to determine why a person is calling a service center and to route the caller to an appropriate agent or destination for servicing a request. Speech recognition technology generally allows an ACR application to recognize natural language statements so that the caller does not have to rely on a menu system. Natural language systems allow the caller to state the purpose of their call “in their own words.”


Natural language ACR systems attempt to interpret the intent of the caller based on the spoken language and then selects a routing destination. When a speech recognition system misinterprets the caller's intent, significant problems can result. A caller who is misrouted is generally unhappy. Misrouted callers realize that there has been a mistake with the automated phone service and often terminate the call by hanging up. If a caller does not hang up they will typically be routed to an operator who will attempt to manually route the call. Routing a caller to an undesired location and to human operators leads to considerable inefficiencies for a business. Most call routing systems handle a large volume of calls and, even if a small percentage of calls are abandoned, the costs associated with abandoned calls are significant.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a simplified configuration of a telecommunication system;



FIG. 2 is a general diagram that illustrates a method of routing calls;



FIG. 3 is a flow diagram that illustrates a method of processing and routing calls;



FIG. 4 is a table that depicts speech input and mapped synonym terms; and



FIG. 5 is a table illustrating action-object pairs and call destinations relating to the action-object pairs.





DETAILED DESCRIPTION

In a particular embodiment, a method includes receiving speech of a call from a caller at a processor of a call routing system. The method includes using the processor to determine a first call destination for the call based on the speech. The method includes using the processor to determine whether the caller is in compliance with at least one business rule related to an account of the caller. The method includes routing the call to the first call destination with the processor when the caller is in compliance with the at least one business rule. The method also includes routing the call to a second call destination with the processor when the caller is not in compliance with the at least one business rule.


In a particular embodiment, a method includes transforming speech of a call received from a caller into text using a processor. The method includes converting the text into an object and an action with the processor. The method includes determining, with the processor, a first call destination based on the object and the action. The method includes determining, with the processor, whether the caller is in compliance with a first business rule related to an account of the caller. The method also includes routing the call to a second call destination with the processor when the caller is not in compliance with the first business rule.


In a particular embodiment, a system including a processor and a network interface to receive speech input of a call from a caller. The system includes an action-object routing module executable by the processor to determine a first call destination based on the speech input. The system also includes a business rule module executable by the processor to determine whether the caller is in compliance with a business rule related to payment of an account of the caller. The system routes the call to a second call destination when the caller is not in compliance with the business rule and the system routes the call to the first call destination when the caller is in compliance with the business rule.


A method of processing a call is disclosed. The method can transform speech input from a caller of a call into text and convert the text into an object and an action. The method determines a call destination based on the object and the action. The method can route the call to a destination when a caller is not in compliance with at least one business rule. The method can further route the call to the call destination when the caller is in compliance.


In a particular embodiment, the system includes a call routing system that has a processor configured to convert speech input from a caller into an object and an action. The system has an action-object routing module configured to determine a first destination for the call based on the object and the action. The call routing system can route the call to a second destination when the caller is not in compliance with a business rule.


In another embodiment the communication system includes an acoustic model configured to accept speech input and to produce text and a semantic model coupled to the acoustic model for producing an action and an object responsive to the text. The system further includes a routing module table responsive to the semantic model to provide a routing destination based on the action and the object.


Referring now to FIG. 1, an illustrated communications system 100 that includes a call routing support system is shown. The communications system 100 includes a speech-enabled call routing system (SECRS) 118, such as an interactive voice response system having a speech recognition module. The communications system 100 includes a plurality of potential call destinations. Illustrative call destinations shown include service departments, such as billing department 120, balance information 122, technical support 124, employee directory 126, and new customer service departments 128. The system 100 includes a communication network 116 that receives calls from a variety of callers, such as the illustrated callers 110, 112, and 114. In a particular embodiment, the communication network 116 may be a public telephone network or may be provided by a voice over Internet protocol (VoIP) type network. The SECRS 118 may include components, such as a processor 142, a synonym table 144, and an action-object routing module 140. The SECRS 118 is coupled to and may route calls to any of the destinations, as shown. In addition, the SECRS 118 may route calls to an agent, such as the illustrated live operator 130. An illustrative embodiment of the SECRS 118 may be a call center having a plurality of agent terminals attached. Thus, while only a single operator 130 is shown, it should be understood that a plurality of different agent terminals or types of terminals may be coupled to the SECRS 118, such that a variety of agents may service incoming calls. In addition, the SECRS 118 may be an automated call routing system. In a particular embodiment, the action-object routing module 140 includes an action-object lookup table for matching action-object pairs to desired call routing destinations.


Referring to FIG. 2, an illustrative block diagram of the SECRS 118 is depicted. In this particular embodiment, the processor 142 in the SECR 118 includes an acoustic model 210, a semantic model 220, and an action-object routing table 230. The acoustic model 210 receives speech input 202 and provides text as its output 204, and the semantic model 220 receives text 204 from the acoustic model 210 and produces an action-object pair. The actions and objects in the action-object table are ordered or ranked according to a confidence level. A confidence level indicates how likely a particular action or object reflects a correct and useable caller instruction. A call can be routed based on the overall highest confidence level action and object in an action-object list in the routing table 230. An exemplary routing table is depicted in FIG. 5. Objects are listed on the left side of the chart and actions are listed across the top of the chart. If the action of “acquire” has the highest confidence level for an action and “DSL” has the highest confidence level for an object, then the call would be routed to extension “001” according to the intersection in the table of the action-object pair “acquire-DSL.” As a further example, when the action-object pair of “cancel-DSL” is selected, then the call would be routed to extension “002” according to the routing table. In the event that a confidence level for an action-object pair is below a predetermined level, the call may be routed to a human operator or agent terminal.


The routing table 230 can receive a selected action-object pair 206 from the semantic model 220 and produces a desired call routing destination 208. Based on the call routing destination 208, a call received at the SECRS 118 may be routed to a destination, such as billing department 120 or technical support service destination 124, as shown in FIG. 1. In a particular embodiment, the action-object routing table 230 may be a look-up table or a spreadsheet, such as Microsoft Excel™.


Referring to FIG. 3, an illustrative embodiment of a method of processing a call using an automated call routing system, such as the system of FIG. 1, is illustrated. The method starts at 300 and proceeds to step 302 where a speech input signal, referred to as an utterance, is received or detected. Information about the caller is also received, such as information that can identify the caller or the caller's account number. This information can be automatically provided or it can be requested using a voice prompt and received as part of the utterance or as touchtone input. Using phonemes, the received speech input is converted into a plurality of word strings or text in accordance with an acoustic model, as shown at steps 304 and 306. In a particular embodiment, confidence levels are assigned to word strings based on established rules and the content and coherency of the word string. Next, at step 308, the word strings are parsed into actions and objects. Objects generally represent nouns and adjective-noun combinations while actions generally represent verbs and adverb-verb combinations. The actions and objects are assigned confidence values based on how likely they are to reflect the intent of the caller.


Many possible actions and objects may be detected or created from the word strings. To aid in the selection of a particular action and object, a table such as a synonym table can be utilized, as shown in FIG. 4. The synonym table can store natural language phrases and map the phrases to a predetermined list of actions and objects. Textual conversion of the natural language spoken by the caller in the acoustic model can be compared to natural language phrases in the table based on the phonetic-to-text conversion. Using the synonym table, the system and method maps portions of the natural phrases to at least one action or at least one object.


Additionally, the synonym table can provide rules for distinguishing recognized actions and recognized objects from specific actions and specific objects. Generally, there may be numerous actions that map to the same destination and numerous objects that map to the same destination. For example, in FIG. 4, the recognized object “Named Services” can include specific objects, such as “Caller ID,” “Call Notes,” “Call Forward” and other features or services that a single call service department may process. Thus, when a call request creates a recognized action or recognized object from a class of possible actions or objects, the call can be routed based on the recognized and selected action or the recognized and selected object. The specific action or specific object can be stored and transmitted with the call such that a destination system can utilize the action or object to assist the caller and meet the caller's objectives.


Recognized actions and objects can be assigned a confidence level based on textual similarities between predetermined or known actions and objects and results of the phonetic conversion. Additionally, rules that are based on consistency between a recognized action or an object and known phonemes can also be utilized to determine the confidence level. The method selects a most probable action and object from a list of recognized objects and actions utilizing the confidence levels, as is illustrated in steps 310 and 312. The selected action and selected object are paired and a current routing destination is determined at step 314. The method can track the treatment of the call utilizing three variables known as prior routing destination, current routing destination, and future routing destination. The prior routing destination variable refers to a previous location having processed the call, the current routing destination refers to a present location that is processing the call, and the future routing destination variable refers to where the call may be routed for processing. The variables can be set and reset throughout the process, as the call is routed, possibly among call centers. Thus, after an initial action object selection, the variables may be as follows: future routing destination equals null; prior routing destination equals null; current routing destination equals action-object table selection results.


Using the caller information received, the method determines if the caller is violating or has violated any business rules at decision step 316. For example, if a caller is late on their payment, or has a voice message box that has been full for over two months, the method may determine that the caller has violated a business rule. When a business rule has been violated, the call can be routed to a destination or a call service department determined by the business rules, as shown in step 320. When the call is transferred to a call service department that can overcome the rule violation, the variable can be reset as follows: (future routing destination equals table results; current routing destination equals business rules table; prior routing destination equals null). The call is routed to the current routing destination at step 322 and the caller is encouraged to take action to comply with the business rule that has been violated. After an attempt has been made to comply with the violation, the variables are reset (prior routing destination equals current routing destination; current routing destination equals future routing destination; future routing destination equals null), at step 324. The method proceeds back to decision step 316 to determine if the caller remains in violation of at least one business rule. If the caller is not in violation of a business rule, then the call is routed to the caller's desired destination, at step 318, the call routing destination variables are reset, and the method ends at step 326.


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 that fall within the scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure 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 method comprising: receiving speech of a call from a caller at a processor;using the processor to determine a first call destination for the call based on the speech;using the processor to determine whether the caller is in compliance with a first business rule based on a comparison of a time period, to a threshold time period, wherein the time period is associated with a voice message box of the caller being full;routing the call to the first call destination in response to the caller being in compliance with the first business rule; androuting the call to a second call destination in response to the caller not being in compliance with the first business rule.
  • 2. The method of claim 1, wherein the second call destination allows the caller to come into compliance with the first business rule.
  • 3. The method of claim 1, wherein the call is a voice over internet protocol call.
  • 4. The method of claim 1, wherein the first call destination comprises a technical support department.
  • 5. The method of claim 1, wherein the first call destination comprises support for new services.
  • 6. The method of claim 1, wherein the caller is not in compliance with the first business rule conditioned on the time period being at least as great as the threshold time period.
  • 7. The method of claim 6, wherein the threshold time period is two months.
  • 8. The method of claim 1, further comprising after the call is routed to the second call destination, routing the call from the second call destination to the first call destination in response to the caller being in compliance with a second business rule.
  • 9. The method of claim 8, wherein the second business rule is related to an account status of the caller.
  • 10. The method of claim 8, further comprising routing the call from the second call destination to a third call destination in response to the caller not being in compliance with the second business rule.
  • 11. A method comprising: transforming speech of a call received from a caller into text using a processor;converting the text into an object and an action using the processor;determining a first call destination based on the object and the action;determining whether the caller is in compliance with a first business rule based on a comparison of a time period to a threshold time period, wherein the time period is associated with a voice message box of the caller being full; androuting the call to a second call destination in response to the caller not being in compliance with the first business rule.
  • 12. The method of claim 11, further comprising routing the call to the first call destination in response to the caller being in compliance with the first business rule.
  • 13. The method of claim 11, further comprising: determining whether the caller is in compliance with a second business rule after the caller comes into compliance with the first business rule and after routing the call to the second call destination; androuting the call to the first call destination conditioned upon the caller being in compliance with the second business rule.
  • 14. The method of claim 11, further comprising setting a future routing to the first destination in response to the call being routed to the second destination.
  • 15. A system, comprising: a processor;a network interface to receive speech input of a call from a caller;an action-object routing module executable by the processor to determine a first call destination based on the speech input; anda business rule module executable by the processor, the business rule module operative to: route the call to the first call destination in response to the caller being in compliance with a first business rule; androute the call to a second call destination in response to the caller not being in compliance with the first business rule;wherein a determination of whether the caller is in compliance with the first business rule is based on a comparison of a time period to a threshold time period, wherein the time period is associated with a voice message box of the caller being full.
  • 16. The system of claim 15, wherein the second call destination is a call service department that facilitates compliance with the first business rule.
  • 17. The system of claim 15, wherein conditioned on the call being routed to the second call destination, the business rule module is further executable by the processor to determine whether the caller is in compliance with a second business rule, and wherein the system routes the call from the second call destination to a third call destination in response to the caller not being in compliance with the second business rule.
  • 18. The system of claim 17, wherein the system routes the call from the second call destination to the first call destination in response to the caller being in compliance with the second business rule.
  • 19. The system of claim 15, wherein the call is received via a public telephone network.
  • 20. The system of claim 15, wherein the action-object routing module is configured to use a synonym table and a routing table.
CLAIM OF PRIORITY

This application is a Continuation patent application of, and claims priority from, U.S. patent application Ser. No. 11/032,495, filed on Jan. 10, 2005, and entitled “SYSTEM AND METHOD FOR SPEECH-ENABLED CALL ROUTING,” which is hereby incorporated by reference in its entirety.

US Referenced Citations (330)
Number Name Date Kind
4696028 Morganstein et al. Sep 1987 A
4788715 Lee Nov 1988 A
4953204 Cuschleg, Jr. et al. Aug 1990 A
4964077 Eisen et al. Oct 1990 A
4967405 Upp et al. Oct 1990 A
4975841 Kehnemuyi et al. Dec 1990 A
5042006 Flohrer Aug 1991 A
5432845 Burd et al. Jul 1992 A
5235679 Yoshizawa et al. Aug 1993 A
5297183 Bareis et al. Mar 1994 A
5299260 Shaio Mar 1994 A
5335269 Steinlicht Aug 1994 A
5416830 MacMillan, Jr. et al. May 1995 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
5621789 McCalmont et al. Apr 1997 A
5632002 Hashimoto et al. May 1997 A
5652789 Miner Jul 1997 A
5659599 Arumainayagam et al. Aug 1997 A
5729600 Blaha et al. Mar 1998 A
5732133 Mark Mar 1998 A
5754639 Flockhart et al. May 1998 A
5754978 Perez-Mendez et al. May 1998 A
5867817 Catallo et al. Feb 1999 A
5923745 Hurd Jul 1999 A
5930337 Mohler Jul 1999 A
5937051 Hurd et al. Aug 1999 A
5940476 Morganstein et al. Aug 1999 A
5946377 Wolf Aug 1999 A
5946388 Walker et al. Aug 1999 A
5953704 McIlroy et al. Sep 1999 A
5987116 Petrunka et al. Nov 1999 A
5991756 Wu Nov 1999 A
5995979 Cochran Nov 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
6028601 Sarin et al. Dec 1999 A
6173289 Sonderegger et al. Jan 2000 B1
6038293 McNerney et al. Mar 2000 A
6038305 McAllister Mar 2000 A
6044146 Gisby et al. Mar 2000 A
6049594 Furman et al. Apr 2000 A
6061433 Polcyn et al. May 2000 A
6064731 Flockhart et al. May 2000 A
6118866 Shtivelman Sep 2000 A
6119101 Peckover Sep 2000 A
6144938 Surace et al. Nov 2000 A
RE37001 Morganstein et al. Dec 2000 E
6173266 Marx 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
6269336 Ladd et al. Jul 2001 B1
6317439 Cardona et al. Nov 2001 B1
6320951 Shtivelman 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
6377662 Hunt 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
6411687 Bohacek et al. Jun 2002 B1
6414966 Kulkami et al. Jul 2002 B1
6418424 Hoffberg et al. Jul 2002 B1
6421433 Arsenault Jul 2002 B1
6434546 Williamowski et al. Aug 2002 B1
6438520 Curt Aug 2002 B1
6442247 Garcia Aug 2002 B1
6483899 Agraharam et al. Nov 2002 B2
6496836 Ronchi et al. Dec 2002 B1
6510414 Chaves Jan 2003 B1
6519562 Phillips et al. Feb 2003 B1
6526126 Morganstein Feb 2003 B1
6529871 Kanevsky et al. Mar 2003 B1
6546087 Shaffer et al. Apr 2003 B2
6553112 Ishikawa Apr 2003 B2
6553113 Dhir et al. Apr 2003 B1
6570967 Katz May 2003 B2
6571240 Ho et al. May 2003 B1
6574599 Lim et al. Jun 2003 B1
6577718 Kalmanek et al. Jun 2003 B1
6584180 Nemoto Jun 2003 B2
6584191 McPartian et al. Jun 2003 B1
6587556 Judkins et al. Jul 2003 B1
6587558 Lo Jul 2003 B2
6598021 Shambaugh 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
6615209 Gomes et al. Sep 2003 B1
6615248 Smith Sep 2003 B1
6631186 Adams et al. Oct 2003 B1
6662163 Albayrak et al. Dec 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
6697458 Kunjibettu 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
6714643 Gargeya et al. Mar 2004 B1
6721416 Farrell Apr 2004 B1
6731722 Coffey May 2004 B2
6732151 Tobias et al. May 2004 B1
6738082 Dong et al. May 2004 B1
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
6751591 Gorin et al. Jun 2004 B1
6757306 Klish, II et al. Jun 2004 B1
6763095 Cermak et al. Jul 2004 B1
6766320 Wang et al. Jul 2004 B1
6775359 Ron et al. Aug 2004 B1
6778643 Bushey et al. Aug 2004 B1
6782412 Brophy et al. Aug 2004 B2
6792096 Martin et al. Sep 2004 B2
6798876 Bala Sep 2004 B1
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
6847715 Swartz Jan 2005 B1
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
6901366 Kuhn et al. May 2005 B1
6907119 Case et al. Jun 2005 B2
6915246 Gusler et al. Jul 2005 B2
6922689 Shtivelman Jul 2005 B2
6925155 Reynolds et al. Aug 2005 B2
6944592 Pickering Sep 2005 B1
6963983 Munson et al. Nov 2005 B2
6964023 Maes et al. Nov 2005 B2
6970554 Peterson et al. Nov 2005 B1
6999755 Park Feb 2006 B2
7003079 McCarthy et al. Feb 2006 B1
7006605 Morganstein et al. Feb 2006 B1
7013112 Haller et al. Mar 2006 B2
7027975 Pazandak et al. Apr 2006 B1
7031444 Shen et al. Apr 2006 B2
7035388 Kurosaki Apr 2006 B2
7039166 Peterson et al. May 2006 B1
7062505 Lane et al. Jun 2006 B2
7065201 Bushey et al. Jun 2006 B2
7072457 Brown et al. Jul 2006 B2
2095842 Brown et al. Aug 2006 A1
7092370 Jiang et al. Aug 2006 B2
7095827 Guedalia Aug 2006 B2
7095842 Brown et al. Aug 2006 B2
7106850 Campbell et al. Sep 2006 B2
7110949 Bushey et al. Sep 2006 B2
7124059 Wetzer et al. Oct 2006 B2
7130411 Brown et al. Oct 2006 B2
7133504 Fostick Nov 2006 B2
7142652 Ho Nov 2006 B2
7184534 Birch et al. Feb 2007 B2
7200614 Reid et al. Apr 2007 B2
7206400 Dezonno et al. Apr 2007 B2
7242751 Bushey et al. Jul 2007 B2
7245711 Margolis Jul 2007 B2
7245716 Brown et al. Jul 2007 B2
7349843 Beck Mar 2008 B1
7415101 Bushey et al. Aug 2008 B2
7450698 Bushey et al. Nov 2008 B2
7460650 Bushey et al. Dec 2008 B2
7580837 Bushey et al. Aug 2009 B2
7620159 Pasquale et al. Nov 2009 B2
7623632 Bushey et al. Nov 2009 B2
7627096 Bushey et al. Dec 2009 B2
7657020 Bushey et al. Feb 2010 B2
7668889 Edwards et al. Feb 2010 B2
7724889 Bushey et al. May 2010 B2
7864942 Knott et al. Jan 2011 B2
20010011211 Bushey et al. Aug 2001 A1
20010018672 Petters et al. Aug 2001 A1
20010019604 Joyce et al. Sep 2001 A1
20010021948 Khouri et al. Sep 2001 A1
20010026608 Beyda et al. Oct 2001 A1
20010032075 Yamamoto Oct 2001 A1
20010032211 Kuzumaki Oct 2001 A1
20010032229 Hulls et al. Oct 2001 A1
20010034662 Morris Oct 2001 A1
20020046030 Haritsa Apr 2002 A1
20020049874 Kimura Apr 2002 A1
20020055975 Petrovykh May 2002 A1
20020057678 Jiang et al. May 2002 A1
20020059164 Shtivelman May 2002 A1
20020059169 Quarterman et al. May 2002 A1
20020064149 Elliott et al. May 2002 A1
20020067714 Crain et al. Jun 2002 A1
20020067820 Benson et al. Jun 2002 A1
20020087316 Lee et al. Jul 2002 A1
20020087385 Vincent Jul 2002 A1
20020087558 Bailey et al. Jul 2002 A1
20020114432 Shaffer et al. Aug 2002 A1
20020122544 Williams et al. Sep 2002 A1
20020133394 Bushey et al. Sep 2002 A1
20020133413 Chang et al. Sep 2002 A1
20020135618 Maes Sep 2002 A1
20020156699 Gray et al. Oct 2002 A1
20020165732 Ezzeddine et al. Nov 2002 A1
20020169606 Bantz et al. Nov 2002 A1
20020188438 Knight et al. Dec 2002 A1
20020196277 Bushey et al. Dec 2002 A1
20030018659 Fuks et al. Jan 2003 A1
20030026409 Bushey et al. Feb 2003 A1
20030028498 Hayes-Roth 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
20030112956 Brown et al. Jun 2003 A1
20030114105 Haller et al. Jun 2003 A1
20030118159 Shen et al. Jun 2003 A1
20030125945 Doyle Jul 2003 A1
20030130841 Bangalore et al. Jul 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
20030179876 Fox 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
20030212558 Matula Nov 2003 A1
20030228007 Kurosaki Dec 2003 A1
20030235282 Sichelman Dec 2003 A1
20030235287 Margolis et al. 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
20040083479 Bondarenko et al. Apr 2004 A1
20040088285 Martin et al. May 2004 A1
20040101127 Dezonno 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
20050015197 Ohtsuji et al. Jan 2005 A1
20050015744 Bushey et al. Jan 2005 A1
20050018825 Ho Jan 2005 A1
20050027535 Martin et al. Feb 2005 A1
20050041647 Stinnie 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
20050060200 Kobylevsky 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
20050125232 Gadd Jun 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
20050147218 Novack et al. Jul 2005 A1
20050169441 Yacoub Aug 2005 A1
20050169453 Knott et al. Aug 2005 A1
20050171877 Weiss Aug 2005 A1
20050172033 Matthew et al. Aug 2005 A1
20050201547 Burg et al. Sep 2005 A1
20050240411 Yacoub Oct 2005 A1
20060018443 Knott et al. Jan 2006 A1
20060023863 Joseph et al. Feb 2006 A1
20060026049 Joseph et al. Feb 2006 A1
20060036437 Bushey et al. Feb 2006 A1
20060039547 Klein et al. Feb 2006 A1
20060050865 Kortum Mar 2006 A1
20060056406 Bouchard et al. Mar 2006 A1
20060072737 Paden et al. Apr 2006 A1
20060109976 Sundaram et al. May 2006 A1
20060115070 Bushey et al. Jun 2006 A1
20060126811 Bushey et al. Jun 2006 A1
20060165066 Campbell et al. Jul 2006 A1
20060177040 Mitra Aug 2006 A1
20060190424 Beale et al. Aug 2006 A1
20060195312 Knight et al. Aug 2006 A1
20060256956 Lee et al. Nov 2006 A1
20060291642 Bushey et al. Dec 2006 A1
20080008308 Knott et al. Jan 2008 A1
Foreign Referenced Citations (9)
Number Date Country
0424015 Apr 1991 EP
0424015 Apr 1991 EP
0424015 Apr 1991 EP
0876652 Sep 1996 EP
9726612 Jul 1997 WO
0137539 May 2001 WO
0137539 May 2001 WO
2004017584 Feb 2004 WO
2004049222 Jun 2004 WO
Non-Patent Literature Citations (23)
Entry
U.S. Appl. No. 11/036,204, filed Jan. 14, 2005.
U.S. Appl. No. 11/036,201, filed Jan. 14, 2005.
U.S. Appl. No. 11/062,100, filed Feb. 18, 2005.
U.S. Appl. No. 11/071,068, filed Mar. 3, 2005.
U.S. Appl. No. 11/086,796, filed Mar. 23, 2005.
U.S. Appl. No. 11/129,051, filed May 13, 2005.
U.S. Appl. No. 11/145,513, filed Jun. 3, 2005.
U.S. Appl. No. 11/173,227, filed Jul. 1, 2005.
U.S. Appl. No. 11/176,972, filed Jul. 7, 2005.
U.S. Appl. No. 11/086,794, filed Mar. 22, 2005.
U.S. Appl. No. 10/996,127, filed Nov. 23, 2004.
U.S. Appl. No. 10/920,719, filed Dec. 13, 2004.
U.S. Appl. No. 10/920,720, filed Aug. 18, 2004.
U.S. Appl. No. 10/948,089, filed Sep. 23, 2004.
U.S. Appl. No. 10/979,784, filed Nov. 2, 2004.
U.S. Appl. No. 11/212,939, filed Aug. 25, 2005.
Ogino, Tsukasa, et al., “Technologies for Internet Infrastructure: Eliminating the World Wide Wait,” iNet Japan, Jul. 18-21, 2000, www.isoc.org/edproceedings/1g/index.
www.yahoo.com (as in Dec. 12, 1998) as archived in the Internet archive (www.archive.org).
Non-Final Office Action for U.S. Appl. No. 11/032,495 received from the United States Patent and Trademark Office (USPTO) mailed Sep. 17, 2008, 23 pages.
Final Office Action for U.S. Appl. No. 11/032,495 received from the United States Patent and Trademark Office (USPTO) mailed Mar. 19, 2009, 20 pages.
Final Office Action for U.S. Appl. No. 11/032,495 received from the United States Patent and Trademark Office (USPTO) mailed Aug. 31, 2009, 27 pages.
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/032,495 received from the United States Patent and Trademark Office (USPTO) mailed Mar. 19, 2010, 15 pages.
Non-Final Office Action for U.S. Appl. No. 11/032,495 received from the United States Patent and Trademark Office (USPTO) mailed Aug. 31, 2009, 27 pages.
Related Publications (1)
Number Date Country
20100232595 A1 Sep 2010 US
Continuations (1)
Number Date Country
Parent 11032495 Jan 2005 US
Child 12787468 US