Caller initiated undivert from voicemail

Information

  • Patent Grant
  • 8150003
  • Patent Number
    8,150,003
  • Date Filed
    Tuesday, January 23, 2007
    17 years ago
  • Date Issued
    Tuesday, April 3, 2012
    12 years ago
Abstract
Once a voicemail is received, it is the onus of the recipient of the voicemail message to call the caller back when a “missed call” message is received on the phone or after the voicemail message is retrieved. While some of the more advanced voicemail systems provide the capability of automatically placing a call from the callee back to the caller upon completion of the callee listening to the voicemail message, an exemplary embodiment of the present invention allows the caller to be connected to the callee should the callee become available while the caller is leaving a voicemail message for the callee.
Description
FIELD OF THE INVENTION

An exemplary embodiment of the present invention is directed toward telephony devices, services and methods, and more specifically, to allow a caller that has been diverted to voicemail the option of being put through to the callee, should the callee become available while the caller is leaving a message.


BACKGROUND

Voicemail systems have been around for a number of years. Traditional voicemail systems have generally been centered around an answering machine that may or may not be collocated with a caller. The voicemail systems can be analog or digital, and may also be a service offered by a carrier. Some of these answering machines allow a callee to intercept the caller while the caller is leaving a message on the machine.


More advanced voicemail systems allow enhanced functionality above and beyond simple “play” and “delete” functions. For example, this enhanced functionality can include fast forward, fast forward to end of message, faster playback, slower playback, repeat, envelope information, message skipping, replying to the message, calling back the caller who left the message, saving the message, forwarding the message, receive notification services, downloading of message(s), personal greeting and options menus, etc.


Callwave® provides an Internet based answering machine that is capable of receiving calls while online. The Caller ID and Caller Name features of Callwave® enable the user to view the name of the person calling while the callee is online. Before a callee hears a caller's message, the callee will see the caller's name and telephone number displayed in a window in the Callwave® interface. Thus, the callee is aware of who called even if the caller does not leave a message.


SUMMARY

Call Waiting allows a callee to switch between calls. Should the callee choose, and upon notification that there is a call waiting, the callee can interrupt a current call and flash over to speak with the incoming call that is in a “call waiting” state. This toggling between an active call and a call waiting call can occur at the callee's discretion.


In existing voicemail systems, once a voicemail is received, it is the onus of the recipient of the voicemail message to call the caller back when a “missed call” message is received on the phone or after the voicemail message is retrieved. While some of the more advanced voicemail systems provide the capability of automatically placing a call back to the caller upon completion of the voicemail message, an exemplary embodiment of the present invention allows the caller, automatically or at the caller's election, to be connected to the callee should the callee become available while the caller is leaving a voicemail message.


For example, and from the perspective of the involved parties, the flow between a caller and a callee would be as follows. The caller calls the callee but the callee is unavailable as, for example, they are on another call. Thus, the caller is diverted to voicemail. While the caller is leaving a message, the callee becomes available, i.e., they end their call. The caller is informed, e.g., by an armouncement being played, that the callee is now available and is given the option of connecting to the callee or continuing to leave the message.


In accordance with an exemplary embodiment, there could also be communication between a PBX and a voicemail system to send notification messages regarding the callee's state to the caller and to handle the re-termination of the call to the callee. For example, a PBX could receive a call from the caller and, upon finding the callee to be unavailable, connect the caller to voicemail. The PBX continues to monitor the availability of the callee until the PBX receives a message from the voicemail system indicating that the caller has completed their message and terminated the call.


If the PBX detects that the callee has become available and the caller is still connected to the voicemail system, the PBX can signal the voicemail system with this information. The voicemail system could then audibly or through some other indication or message notify the caller that the callee is available. If the caller signals to the voicemail system that they would like to be put through to the callee, then the appropriate network components would transfer the call back to the PBX which would in turn the ring the callee's phone.


A Session Initiation Protocol (SIP) is a signaling protocol that can be used for establishing sessions in an IP network. The session can be a simple two-way telephone call or, for example, could be a multi-party, multi-media conference session. SIP protocols are well known and allow the ability to establish sessions in a host of different service options such as voice-enriched e-commerce, web page click-to-dial, instant messaging, IP Centrex services and the like. An exemplary embodiment of the systems and methods of this invention could use SIP protocols to implement the functionality and messaging described herein. Additionally, the determination as to whether a callee is available need not be limited to the identification of a busy signal, but could also be based on presence information or “do not disturb” status information available to, for example, a PBX.


An exemplary aspect of the invention is related to call redirection.


More specifically, an exemplary aspect of the invention relates to reconnecting a previously terminated call once a callee becomes available.


Aspects of the invention further relate to allowing a caller that has been diverted to voicemail an option of being put through to the callee when the callee becomes available.


Still further aspects of the invention relate to redirecting a caller to a callee upon a determination being made that the callee is available.


These and other features and advantages of this invention are described in, or are apparent from, the following detailed description of the exemplary embodiments. The embodiments and configurations herein are neither complete nor exhaustive. As will be appreciated, other embodiments of the invention are possible utilizing, alone or in combination, one or more of the features set forth above or described in detail below.





BRIEF DESCRIPTION OF THE DRAWINGS

The exemplary embodiments of the invention will be described in detail, with reference to the following figures wherein:



FIG. 1 is a block diagram illustrating an exemplary embodiment of a voicemail redirect system according this invention;



FIG. 2 illustrates exemplary call flow according to an embodiment of this invention; and



FIG. 3 is a flowchart illustrating an exemplary method of voicemail redirect according to this invention.





DETAILED DESCRIPTION

The exemplary embodiments of this invention will be described in relation to caller initiated undivert from voicemail. However, it should be appreciated, that in general, the systems and methods of this invention will work equally well for any type of communication system in any environment.


The exemplary systems and methods of this invention will also be described in relation to telecommunications systems and associated communication hardware, software and communication channels. However, to avoid unnecessarily obscuring the present invention, the following description omits well-known structures, network components and devices that may be shown in block diagram form, are well known or are otherwise summarized.


For purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the present invention. It should be appreciated however that the present invention may be practiced in a variety of ways beyond the specific details set forth herein.


Furthermore, while the exemplary embodiments illustrated herein show the various components of the system collocated, it is to be appreciated that the various components of the system can be located at distant portions of a distributed network, such as a telecommunications network and/or the Internet, or within a dedicated secure, unsecured and/or encrypted system. Thus, it should be appreciated that the components of the system can be combined into one or more devices, such as a PBX or voicemail system, or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a circuit switched network and/or a packet switched network. As will be appreciated from the following description, and for reasons of computational efficiency, the components of the system can be arranged at any location within a distributed network without affecting the operation of the system. For example, the various components can be located in a PBX, at one or more users' premises, or some combination thereof. Similarly, one or more functional portions of the system could be distributed between a telecommunications device(s) and an associated computing device.


Furthermore, Session Initiation Protocol or SIP (which is a simple signaling/application layer protocol for data network multimedia conferencing and telephony) can at least be used with the present invention to provide a degree of presence awareness in the communication network. Although other protocols are equally supportive of presence concepts, SIP provides an illustrative basis for the present invention.


In SIP, end systems and proxy servers can provide services such as call forwarding, callee and caller number delivery (where numbers can be any naming scheme such as a conventional URL format), personal mobility (the ability to reach a callee under a single, location-independent address even when the callee changes terminals), terminal-type negotiation and selection (e.g., a caller can be given a choice on how to reach the callee), mobile phone answering service, terminal capability negotiation, caller and callee authentication, blind and supervised call transfer, and invitations to multicast conferences.


To provide these varied services, SIP uses a relatively simple message system, namely an “INVITE” message (with the caller's codec preferences) and an “OK” message (with the callee's codec preferences), and various software entities, namely registrars which maintain a map of the addresses of a given user at the current time, proxies which perform call routing, session management, user authentication, redirect functions, and routing to media gateways, redirect servers which perform a subset of forwarding functions, and SIP location servers which maintain user profiles and provide subscriber registration. “Registration” is a mechanism whereby a user's communication device registers with the network each time he or she comes online and individual profiles are accessed that specify information for routing based on a number of different criteria.


It should also be appreciated that the various links, including communications channel and the various links 5, connecting the elements can be wired or wireless links, or any combination thereof, or any other known or later developed element(s) that is capable of supplying and/or communicating data to and from the connected elements. The term module as used herein can refer to any known or later developed hardware, software, firmware, or combination thereof that is capable of performing the functionality associated with that element. The terms determine, calculate and compute, and variations thereof, as used herein are used interchangeably and include any type of methodology, process, mathematical operation or technique. Further, it is to be noted that the term “a” or “an” entity refers to one or more of that entity. As such, the terms “a” (or “an”), “one or more” and “at least one” can be used interchangeably herein. It is also to be noted that the terms “comprising”, “including” and “having” can be used interchangeably.


Also, while the flowcharts have been discussed in relation to a particular sequence of events, it should be appreciated that changes, additions and omissions to this sequence can occur without materially effecting the operation of the invention.



FIG. 1 illustrates an exemplary embodiment of the voicemail redirect system 1. The voicemail redirect system 1 comprises a portion of a telecommunications system 100 connected via links 5 and networks 10 to a communications device 105 at a caller and a communications device 115 at a callee. The portion of the telecommunications system 100 comprises a call status monitoring module 110, a call management module 120, a messaging module 130, a voicemail management module 140, voicemail 150, controller 160 and memory 170, all interconnected via link 5.


As will be appreciated, the portion of the telecommunications system 100 comprises other well known components which will not be discussed herein in detail. For example, the portion of the telecommunications system 100 can further include one or more telephony switch/media servers that can be any architecture for directing communications to one or more communication devices. The network 10 can and typically includes proxies, registrars, switches and routers that are well known. The communication devices 105 and 115 can be any communication device suitable for the network to which they are connected. For example, the communications devices can be any wired or wireless phone such as IP hardphones, such as the Cisco 7960™ phone, IP softphones, Personal Digital Assistants or PDAs, Personal Computers or PCs, laptops, mobile phones, traditional PSTN type phones, cellular phones or any combination thereof.


A typical communications device comprises a handset, or headset, and a cradle assembly. The cradle assembly typically comprises a display, a nonprogrammable or hard keypad and programmable or soft keypad.


In operation, a call is originated in communications device 105 by the caller and routed, with the cooperation of network 10 and various portions of the telecommunications system 100 such as controller 160 and memory 170, to the communications device 115 possessed by the callee. The call management module 120 monitors the status of the incoming call's connection to communications device 115. Upon determining that the communications device 115 is busy, or otherwise not available, the call management module 120 in cooperation with the voicemail management module 140, forwards the incoming call from the caller for the callee to voicemail 150.


The voicemail management module 140 and voicemail 150 provide standard, well-known features that allow the caller/callee to navigate the voicemail system. Features such as review message, save message, send message, delete message, skip message, forward message, faster, slower, repeat and the like can be provided as are well known.


While the caller is leaving a voicemail in voicemail 150, which may or may not also be broadcast to the callee, the call status monitoring module 110, in cooperation with the controller 160 and memory 170, monitors the status of the communications device 115. Upon the call status monitoring module 110 determining that the communications device 115 is available, and in cooperation with the messaging module 130 and the voicemail management module 140, the caller is notified that the callee is available. In conjunction with this notification, the voicemail management module 140 and instructs voicemail 150 go into a pause mode until a determination is made by the caller as to whether they would like to connect to the callee.


More specifically, and in cooperation with the messaging module 130, a message is determined and forwarded via network 10 and link 5 to the communications device 105. The caller is prompted, for example, via an audio or other prompt, to select to either connect to the callee, continue the voicemail, or terminate the call.


If the caller elects to connect to the callee, the caller can be prompted as to whether the partially completed voicemail should be deleted. If desired, the caller can select to have the partially completed voicemail deleted and the caller terminated to the callee. Alternatively, the caller can leave the partially completed voicemail in voicemail 150 which will, in due course, be forwarded to the callee at communication device 115. Alternatively still, the partially completed voicemail can be automatically deleted.


If the caller elects to not be connected to the callee, the caller can be returned to voicemail when the caller can complete the voicemail or, alternatively, the call terminated.



FIG. 2 illustrates an exemplary call flow associated with an embodiment of this invention. Specifically, the caller places a call to the callee. If the callee is not busy, the caller is connected to the callee. However, if the callee is busy, the caller is diverted to the callee's voicemail. While the caller is in the callee's voicemail, the status of the callee is monitored to detect availability. Should the callee become available during the time when the caller is leaving a voicemail, the caller is given the opportunity to connect with the callee and exit the voicemail system. For example, the caller can be prompted with “Press 1 to connect to callee, Press 2 to continue with voicemail.” For example, one or more of the caller and the callee can subscribe to a service that provides the above functionality and, for example, the service can store a profile that defines how, for example, notification, billing, or the like is to occur.


Additionally, or alternatively, the present invention can use presence information to determine the status of the callee and the appropriate termination or diversion of a call. “Presence” relates to the person having multiple devices with multiple communication paths and the user's preference/preferred devices and availability. “Presence information” typically refers to any information associated with a network node and/or endpoint device, such as a communication device, that is in turn associated with a person. Examples of presence information include registration information under the Session Initiation Protocol, information regarding the accessibility of the endpoint device, the endpoint's telephone number or address, the recency of use of the endpoint device by the person, recency of authentication by the person to a network component, and the preferences of the person (e.g., contact mode preferences or profiles such as the communication device to be contacted for specified types of contacts or under specified factual scenarios or presence contexts, contact time preferences, impermissible contact types and/or subjects such as subjects about which the person does not wish to be contacted, permissible contact types and/or subjects such as subjects about which the person does wish to be contacted, parties who must not contact (i.e., do not call if you are calling on behalf of XYZ company), and parties who can contact at any time (e.g., I will accept a call from the head of Company “x” regardless of what I am doing). Presence information can be user configurable, i.e., the user can configure the number and type of communication and message devices with which he or she can be contacted and to define different profiles that define the communication and messaging options presented to the incoming contactor in specified factual situations or sets of facts. By identifying a predefined set of facts, the pertinent profile can be followed to direct the contact to the user preferred device. “Contact” means a connection or request for connection between two or more communication devices. As will be appreciated, the contacts can be of various types and forms, such as voice contacts, e-mail, faxes, instant messages, paging signals, VoIP sessions, chat sessions, video conferences, multimedia multi-part messages, and cross-media messages. Moreover, “Availability intelligence” can be combined with the presence information, wherein “Availability intelligence” refers to processed (e.g., compiled, cross-referenced, and/or filtered) presence information or meta-information. Policy rules associated with the callee's name space can then be mapped against the one or more of the presence information and intelligence information to determine what availability intelligence, if any, is to be provided to a callee.



FIG. 3 is a flowchart illustrating an exemplary method of the invention. In particular, control begins in step S100 and continues to step S110. In step S110, a caller places a call to the callee. Next, in step S120, the caller is routed to, for example, the callee's voicemail since the callee is busy or otherwise unavailable. For example, the determination that the callee is unavailable can be based on one or more of presence information, a do not disturb status, line conditions, a busy signal, or the like. Alternatively, the caller could be routed to, for example, an interactive voice response system, where the redirecting of the caller to a callee when the callee becomes available would work in the same manner. In general, the caller could be directed to any service while the callee is busy with the systems and methods described herein having the ability to redirect the caller from that service to a callee upon the callee becoming available.


Then, in step S130, and during the caller's communication with the callee, the status of the callee is monitored. Control then continues to step S140.


In step S140, a determination is made whether the callee has become available. If the callee has become available, control continues to step S150. Otherwise, control jumps to step S145.


In step S145, a determination is made whether the caller has completed their voicemail. If the voicemail has not been completed, control jumps back to step S130. Otherwise, control continues to step S190 where the control sequence ends.


In step S150, the caller leaving the voicemail is interrupted and voicemail is paused. Next, in step S160, the caller is notified that the callee is available. For example, the caller can be notified through one or more of an audio message, a visual indicator, vibrating, or an interactive voice response (IVR) type of message. Another example of notifying the caller would be to alter a display on a phone, such as a LCD display, to provide a message to the caller that, for example, the callee's line is no longer busy. The display could also be populated with the appropriate messages and corresponding buttons activated to, for example, allow the caller to “Return to Voicemail,” “Connect to Callee,” and “Hang-up.”


Then, in step as 170, a determination is made whether the caller has elected to connect to the now available callee.


If the caller desires to connect to the callee, control continues to step S172. In step S172, the caller is given the option of deleting the partially completed voicemail. If the caller elects to delete the voicemail, the voicemail is deleted in step S173 with control continuing to S176. Otherwise, the caller can save the voicemail which will be forwarded to the callee in step S174. Control then continues to step S176 where the caller and callee are connected.


If the caller decides not to connect to the now-available callee, control continues to step S180. In step S180, the caller is queried whether they would like to return to voicemail or to terminate the call. If the call is to be terminated, control continues to step S190 were the control sequence ends.


However, if the caller elects to return voicemail, control continues to step S185 where the caller is returned to voicemail until the voicemail is completed. Control then continues to step S190 were the control sequence ends.


While the above-described flowcharts have been discussed in relation to a particular sequence of events, it should be appreciated that changes to this sequence can occur without materially effecting the operation of the invention. Additionally, the exact sequence of events need not occur as set forth in the exemplary embodiments. The exemplary techniques illustrated herein are not limited to the specifically illustrated embodiments but can also be utilized with the other exemplary embodiments and each described feature is individually and separately claimable.


The above-described system can be implemented on wired and/or wireless telecommunications devices, such a telephone, mobile phone, PDA, a wired and/or wireless wide/local area network system, a satellite communication system, or the like, or on a separate programmed general purpose computer having a communications device(s) or in conjunction with any compatible communications protocol(s).


Additionally, the systems, methods and protocols of this invention can be implemented on a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device such as PLD, PLA, FPGA, PAL, a communications device, such as a phone, any comparable means, or the like. In general, any device capable of implementing a state machine that is in turn capable of implementing the methodology illustrated herein can be used to implement the various communication methods, protocols and techniques according to this invention.


Furthermore, the disclosed methods may be readily implemented in software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms. Alternatively, the disclosed system may be implemented partially or fully in hardware using standard logic circuits or VLSI design. Whether software or hardware is used to implement the systems in accordance with this invention is dependent on the speed and/or efficiency requirements of the system, the particular function, and the particular software or hardware systems or microprocessor or microcomputer systems being utilized. The communication systems, methods and protocols illustrated herein can be readily implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the functional description provided herein and with a general basic knowledge of the computer and telecommunications arts.


Moreover, the disclosed methods may be readily implemented in software that can be stored on a storage medium, executed on a programmed general-purpose computer with the cooperation of a controller and memory, a special purpose computer, a microprocessor, or the like. In these instances, the systems and methods of this invention can be implemented as program embedded on personal computer such as an applet, JAVA® or CGI script, as a resource residing on a server or computer workstation, as a routine embedded in a dedicated communication system or system component, or the like. The system can also be implemented by physically incorporating the system and/or method into a software and/or hardware system, such as the hardware and software systems of a communications device or system.


It is therefore apparent that there has been provided, in accordance with the present invention, systems and methods for caller redirect. While this invention has been described in conjunction with a number of embodiments, it is evident that many alternatives, modifications and variations would be or are apparent to those of ordinary skill in the applicable arts. Accordingly, it is intended to embrace all such alternatives, modifications, equivalents and variations that are within the spirit and scope of this invention.

Claims
  • 1. A call diversion method comprising: monitoring a status of a communications device while a caller is connected to voicemail;while the caller is connected to voicemail, determining that the communications device which was previously unavailable is now available;providing an indicator to the caller upon determining that the communications device which was previously unavailable is available;prompting the caller, via an audio or other prompt, to select to either connect to the communications device, continue in voicemail, or terminate the call; andbased on a response to the prompting: redirecting the call from voicemail to the now available communications device,continuing in voicemail, orterminating the call.
  • 2. The method of claim 1, further comprising one or more of: forwarding the call to voicemail when the communications device is unavailable,determining presence information associated with a person associated with the communications device, andcombining availability intelligence with the presence.
  • 3. The method of claim 1, further comprising prompting the caller to connect to the communications device when the communications device becomes available.
  • 4. The method of claim 3, further comprising returning the call to voicemail when the caller elects to not be connected to the available communications device.
  • 5. The method of claim 1, further comprising prompting a caller to delete a partially completed voicemail.
  • 6. The method of claim 1, further comprising: forwarding an indication to a caller when the communications device becomes available; andperforming an action based on a response received from the caller.
  • 7. The method of claim 1, further comprising pausing voicemail during a time period when the caller is being queried to connect to the available communications device.
  • 8. The method of claim 1, further comprising providing one or more of an audio, interactive voice response (IVR) or visual indicator to a caller upon determining that the communications device which was previously unavailable is available.
  • 9. A call diversion system comprising: a call status monitoring module configured to monitor a status of a communications device while a caller is connected to voicemail, determine that the communications device which was previously unavailable is now available, provide an indicator to the caller upon determining that the communications device which was previously unavailable is available, prompt the caller, via an audio or other prompt, to select to either connect to the communications device, continue in voicemail, or terminate the call; and based on a response to the prompting:a call management module is configured to: redirect the call from voicemail to the now available communications devicecontinue the voicemail, orterminate the call.
  • 10. The system of claim 9, further comprising a voicemail management module configured to: cooperate with the call management module to forward the call to voicemail when the communications device is unavailable,determine presence information associated with a person associated with the communications device, orcombine availability intelligence with the presence.
  • 11. The system of claim 9, further comprising a messaging module configured to prompt the caller to connect to the communications device when the communications device becomes available.
  • 12. The system of claim 11, wherein the call management module returns the call to voicemail when the caller elects to not be connected to the available communications device.
  • 13. The system of claim 9, further comprising a messaging module configured to cooperate with a voicemail management module to prompt the caller to delete a partially completed voicemail.
  • 14. The system of claim 9, further comprising: a messaging module configured to forward an indication to the caller when the communications device becomes available and to cooperate with the call management module to perform an action based on a response received from the caller.
  • 15. The system of claim 9, wherein the voicemail management module pauses voicemail during a time period when the caller is being queried to connect to the available communications device.
  • 16. The system of claim 9, further comprising providing one or more of an audio or visual indicator to the caller upon determining that the communications device which was previously unavailable is available.
  • 17. A call diversion architecture comprising: means for monitoring a status of a communications device while a call is in voicemail;means for determining that the communications device which was previously unavailable is available;means for providing an indicator to a caller upon determining that the communications device which was previously unavailable is available;means for prompting the caller, via an audio or other prompt, to select to either connect to the communications device, continue in voicemail, or terminate the call; andbased on a response to the prompting: means for redirecting the call from voicemail to the now available communications device,means for continuing in voicemail, ormeans for terminating the call.
  • 18. The architecture of claim 17, further comprising one or more of: means for forwarding the call to voicemail when the communications device is unavailable,means for determining presence information associated with a person associated with the communications device, andmeans for combining availability intelligence with the presence.
  • 19. The architecture of claim 17, further comprising means for prompting the caller to connect to the communications device when the communications device becomes available.
  • 20. The architecture of claim 19, further comprising means for returning the call to voicemail when the caller elects to not be connected to the available communications device.
  • 21. The architecture of claim 17, further comprising means for prompting the caller to delete a partially completed voicemail.
  • 22. The architecture of claim 17, further comprising: means for forwarding an indication to the caller when the communications device becomes available; andmeans for performing an action based on a response received from the caller.
  • 23. The architecture of claim 17, further comprising means for pausing voicemail during a time period when the caller is being queried to connect to the available communications device.
  • 24. The architecture of claim 17, further comprising means for providing one or more of an audio or visual indicator to a caller upon determining that the communications device which was previously unavailable is available.
  • 25. A call routing protocol comprising: determining a status of a callee communications device;routing a call to voicemail when the communications device is not available;monitoring the status of the communications device while the call is in voicemail;providing an indicator to a caller upon determining that the communications device which was previously unavailable is available;prompting the caller, via an audio or other prompt, to select to either connect to the communications device, continue in voicemail, or terminate the call; andbased on a response to the prompting: terminating the call to the communications device when the communications device becomes available,continuing in voicemail, orterminating the call.
  • 26. The protocol of claim 25, further comprising one or more of: providing the caller with one or more options for voicemail management,determining presence information associated with a person associated with the communications device, andcombining availability intelligence with the presence.
US Referenced Citations (270)
Number Name Date Kind
4809272 Torgrim et al. Feb 1989 A
4817130 Frimmel, Jr. Mar 1989 A
4941168 Kelly, Jr. Jul 1990 A
5001710 Gawrys et al. Mar 1991 A
5003577 Ertz et al. Mar 1991 A
5007076 Blakley Apr 1991 A
5153905 Bergeron et al. Oct 1992 A
5185782 Srinivasan Feb 1993 A
5206903 Kohler et al. Apr 1993 A
5311588 Polcyn et al. May 1994 A
5313515 Allen et al. May 1994 A
5329578 Brennan et al. Jul 1994 A
5341414 Popke Aug 1994 A
5371534 Dagdeviren et al. Dec 1994 A
5371787 Hamilton Dec 1994 A
5396542 Alger et al. Mar 1995 A
5410343 Coddington et al. Apr 1995 A
5430792 Jesurum et al. Jul 1995 A
5434908 Klein Jul 1995 A
5493692 Theimer et al. Feb 1996 A
5511112 Szlam Apr 1996 A
5533103 Peavey et al. Jul 1996 A
5555376 Theimer et al. Sep 1996 A
5590178 Murakami et al. Dec 1996 A
5675639 Itani Oct 1997 A
5706329 Foladare et al. Jan 1998 A
5712902 Florence et al. Jan 1998 A
5724420 Torgrim Mar 1998 A
5742763 Jones Apr 1998 A
5802510 Jones Sep 1998 A
5805587 Norris et al. Sep 1998 A
5819084 Shapiro et al. Oct 1998 A
5826039 Jones Oct 1998 A
5828731 Szlam et al. Oct 1998 A
5828747 Fisher et al. Oct 1998 A
5864874 Shapiro Jan 1999 A
5894504 Alfred et al. Apr 1999 A
5903726 Donovan et al. May 1999 A
5905793 Flockhart et al. May 1999 A
5982873 Flockhart et al. Nov 1999 A
5999611 Tatchell et al. Dec 1999 A
6018655 Bartle et al. Jan 2000 A
6031896 Gardell et al. Feb 2000 A
6038296 Brunson et al. Mar 2000 A
6046762 Sonesh et al. Apr 2000 A
6068188 Knowles May 2000 A
6088441 Flockhart et al. Jul 2000 A
6094681 Shaffer et al. Jul 2000 A
6128304 Gardell et al. Oct 2000 A
6130937 Fotta Oct 2000 A
6144644 Bajzath et al. Nov 2000 A
6154738 Call Nov 2000 A
6163607 Bogart et al. Dec 2000 A
6167266 Havinis et al. Dec 2000 A
6169795 Dunn et al. Jan 2001 B1
6173053 Bogart et al. Jan 2001 B1
6185603 Henderson et al. Feb 2001 B1
6188756 Mashinsky Feb 2001 B1
6192122 Flockhart et al. Feb 2001 B1
6199048 Hudetz et al. Mar 2001 B1
6208870 Lorello et al. Mar 2001 B1
6208970 Ramanan Mar 2001 B1
6212265 Duphorne Apr 2001 B1
6215784 Petras et al. Apr 2001 B1
6226360 Goldberg et al. May 2001 B1
6272319 Narusawa Aug 2001 B1
6282284 Dezonno et al. Aug 2001 B1
6298062 Gardell et al. Oct 2001 B1
6301609 Aravamudan et al. Oct 2001 B1
6307931 Vaudreuil Oct 2001 B1
6310947 Polcyn Oct 2001 B1
6311231 Bateman et al. Oct 2001 B1
6317593 Vossler Nov 2001 B1
6330243 Strandberg Dec 2001 B1
6330317 Garfinkel Dec 2001 B1
6332081 Do Dec 2001 B1
6332154 Beck et al. Dec 2001 B2
6360222 Quinn Mar 2002 B1
6408177 Parikh et al. Jun 2002 B1
6411682 Fuller et al. Jun 2002 B1
6430271 DeJesus et al. Aug 2002 B1
6430602 Kay et al. Aug 2002 B1
6430604 Ogle et al. Aug 2002 B1
6449260 Sassin et al. Sep 2002 B1
6456711 Cheung et al. Sep 2002 B1
6463299 Macor Oct 2002 B1
6463471 Dreke et al. Oct 2002 B1
6477270 Wu Nov 2002 B1
6477373 Rappaport et al. Nov 2002 B1
6477374 Shaffer et al. Nov 2002 B1
6480484 Morton Nov 2002 B2
6535600 Fisher et al. Mar 2003 B1
6546097 Peltz Apr 2003 B1
6549612 Gifford et al. Apr 2003 B2
6560318 Spielman et al. May 2003 B1
6561805 Kumar May 2003 B2
6587681 Sawai Jul 2003 B1
6614783 Sonesh et al. Sep 2003 B1
6636587 Nagai et al. Oct 2003 B1
6643360 Reine Nov 2003 B1
6658095 Yoakum et al. Dec 2003 B1
6665534 Conklin et al. Dec 2003 B1
6668167 McDowell et al. Dec 2003 B2
6675168 Shapiro et al. Jan 2004 B2
6700967 Kleinoder et al. Mar 2004 B2
6707890 Gao et al. Mar 2004 B1
6738462 Brunson May 2004 B1
6741586 Schuster et al. May 2004 B1
6750897 Moshrefi et al. Jun 2004 B1
6751453 Schemers et al. Jun 2004 B2
6751459 Lee et al. Jun 2004 B1
6788773 Fotta Sep 2004 B1
6789120 Lee et al. Sep 2004 B1
6795429 Schuster et al. Sep 2004 B1
6807423 Armstrong et al. Oct 2004 B1
6839735 Wong et al. Jan 2005 B2
6865384 Sagi et al. Mar 2005 B2
6868140 Myers et al. Mar 2005 B2
6868395 Szlam et al. Mar 2005 B1
6871062 Trop et al. Mar 2005 B2
6879677 Trandal et al. Apr 2005 B2
6879828 Virtanen et al. Apr 2005 B2
6888927 Cruickshank et al. May 2005 B1
6891933 Kumamoto May 2005 B2
6891934 Gao et al. May 2005 B1
6925166 Chan Aug 2005 B1
6937597 Rosenberg et al. Aug 2005 B1
6968052 Wullert, II Nov 2005 B2
6968179 De Vries Nov 2005 B1
6987765 March et al. Jan 2006 B2
6988126 Wilcock et al. Jan 2006 B2
6999731 Cronin Feb 2006 B2
7003087 Spencer et al. Feb 2006 B2
7020480 Coskun et al. Mar 2006 B2
7023971 Huart et al. Apr 2006 B1
7023980 Lenard Apr 2006 B2
7027586 Bushey et al. Apr 2006 B2
7035385 Levine et al. Apr 2006 B2
7039040 Burg May 2006 B1
7054939 Koch et al. May 2006 B2
7058036 Yu et al. Jun 2006 B1
7068762 Skladman et al. Jun 2006 B2
7074853 Smith et al. Jul 2006 B2
7080321 Aleksander et al. Jul 2006 B2
7092370 Jiang et al. Aug 2006 B2
7099867 Okada et al. Aug 2006 B2
7103155 Caharel et al. Sep 2006 B2
7123697 Amir et al. Oct 2006 B2
7130390 Abburi Oct 2006 B2
7158630 Fotta et al. Jan 2007 B2
7171473 Eftis et al. Jan 2007 B1
7192235 Blight et al. Mar 2007 B2
7218626 Shaheen et al. May 2007 B2
7245713 Simpson et al. Jul 2007 B1
7248677 Randall et al. Jul 2007 B2
7269162 Turner Sep 2007 B1
7269247 Mashinsky Sep 2007 B2
7283808 Castell et al. Oct 2007 B2
7287056 Loveland et al. Oct 2007 B2
7313617 Malik et al. Dec 2007 B2
7340246 Kanerva et al. Mar 2008 B1
7356137 Burg et al. Apr 2008 B1
7359496 Qian et al. Apr 2008 B2
7398061 Mousseau Jul 2008 B2
7436939 Packingham et al. Oct 2008 B1
7436945 Agrawal et al. Oct 2008 B2
7437162 Zhang et al. Oct 2008 B1
7487095 Hill et al. Feb 2009 B2
7492872 Di Carlo et al. Feb 2009 B1
7542558 Klein et al. Jun 2009 B2
7602895 Terry et al. Oct 2009 B2
7609663 Neuhaus et al. Oct 2009 B2
20010006893 Yoshioka Jul 2001 A1
20010012286 Huna et al. Aug 2001 A1
20010029176 Taniguchi Oct 2001 A1
20020019829 Shapiro Feb 2002 A1
20020021307 Glenn et al. Feb 2002 A1
20020024958 Iveland et al. Feb 2002 A1
20020032040 Tsukamoto Mar 2002 A1
20020035605 McDowell et al. Mar 2002 A1
20020052225 Davis et al. May 2002 A1
20020055350 Gupte et al. May 2002 A1
20020055975 Petroyikh May 2002 A1
20020065894 Dalai et al. May 2002 A1
20020069081 Ingram et al. Jun 2002 A1
20020076010 Sahal Jun 2002 A1
20020076025 Liversidge et al. Jun 2002 A1
20020082931 Siegel et al. Jun 2002 A1
20020083127 Agrawal Jun 2002 A1
20020085701 Parsons et al. Jul 2002 A1
20020087630 Wu Jul 2002 A1
20020098831 Castell et al. Jul 2002 A1
20020116336 Diacakis et al. Aug 2002 A1
20020116461 Diacakis et al. Aug 2002 A1
20020120687 Diacakis et al. Aug 2002 A1
20020126701 Requena Sep 2002 A1
20020131395 Wang Sep 2002 A1
20020160757 Shavit et al. Oct 2002 A1
20020176558 Tate et al. Nov 2002 A1
20030014491 Horvitz et al. Jan 2003 A1
20030018720 Chang et al. Jan 2003 A1
20030026289 Mukherjee et al. Feb 2003 A1
20030028597 Salmi et al. Feb 2003 A1
20030028621 Furlong et al. Feb 2003 A1
20030037103 Salmi et al. Feb 2003 A1
20030041101 Hansche et al. Feb 2003 A1
20030065788 Salomaki Apr 2003 A1
20030073440 Mukhegee et al. Apr 2003 A1
20030086390 Eschbach et al. May 2003 A1
20030110228 Xu et al. Jun 2003 A1
20030110292 Takeda et al. Jun 2003 A1
20030112952 Brown et al. Jun 2003 A1
20030115332 Honeisen Jun 2003 A1
20030130864 Ho et al. Jul 2003 A1
20030135569 Khakoo et al. Jul 2003 A1
20030148756 Onishi et al. Aug 2003 A1
20030154251 Manabe et al. Aug 2003 A1
20030154293 Zmolek Aug 2003 A1
20030191762 Kalliokulju et al. Oct 2003 A1
20030195811 Hayes et al. Oct 2003 A1
20030217142 Bobde et al. Nov 2003 A1
20030233415 Beyda Dec 2003 A1
20040010431 Thomas et al. Jan 2004 A1
20040062383 Sylvain Apr 2004 A1
20040078445 Malik Apr 2004 A1
20040086094 Bosik et al. May 2004 A1
20040120498 Sylvain Jun 2004 A1
20040133641 McKinnon et al. Jul 2004 A1
20040136505 Garg et al. Jul 2004 A1
20040141594 Brunson Jul 2004 A1
20040156493 Cohen Aug 2004 A1
20040189698 Bokish Sep 2004 A1
20040198427 Kimbell et al. Oct 2004 A1
20050025295 Christie, IV Feb 2005 A1
20050031107 Fotta Feb 2005 A1
20050054361 Turcanu et al. Mar 2005 A1
20050071642 Moghe et al. Mar 2005 A1
20050114159 Ozugur et al. May 2005 A1
20050147086 Rosenberg et al. Jul 2005 A1
20050163104 Christensen et al. Jul 2005 A1
20050165894 Rosenberg et al. Jul 2005 A1
20050165934 Rosenberg et al. Jul 2005 A1
20050187781 Christensen et al. Aug 2005 A1
20050198299 Beck et al. Sep 2005 A1
20050207361 Rosenberg et al. Sep 2005 A1
20050210104 Torvinen Sep 2005 A1
20050216565 Ito et al. Sep 2005 A1
20050216848 Thompson et al. Sep 2005 A1
20050221807 Karlsson et al. Oct 2005 A1
20050226403 Lenard Oct 2005 A1
20050233776 Allen et al. Oct 2005 A1
20050267895 Yoshiuchi et al. Dec 2005 A1
20050276407 Mohler Dec 2005 A1
20060013233 Trossen et al. Jan 2006 A1
20060167998 Yoshiuchi et al. Jul 2006 A1
20060248184 Wu et al. Nov 2006 A1
20060252444 Ozugur Nov 2006 A1
20070067443 Seligmann et al. Mar 2007 A1
20070087731 Karlsson et al. Apr 2007 A1
20070106756 Eftis et al. May 2007 A1
20070112965 Eftis et al. May 2007 A1
20070112966 Eftis et al. May 2007 A1
20070237130 Milstein et al. Oct 2007 A1
20070274466 Tidwell et al. Nov 2007 A1
20080019300 Perzy et al. Jan 2008 A1
20080040441 Maes Feb 2008 A1
20080049911 Hanson et al. Feb 2008 A1
20080089488 Brunson et al. Apr 2008 A1
20080152109 Bartfeld et al. Jun 2008 A1
20090225972 Kahn Sep 2009 A1
Foreign Referenced Citations (46)
Number Date Country
0 886 416 Dec 1998 EP
0930592 Jul 1999 EP
1259053 Nov 2002 EP
1261179 Nov 2002 EP
05-260188 Oct 1993 JP
H8-23577 Jan 1996 JP
9-200813 Jul 1997 JP
H11-046377 Feb 1999 JP
11-088495 Mar 1999 JP
H11-187454 Jul 1999 JP
H11-205837 Jul 1999 JP
2000-102059 Apr 2000 JP
2000-312258 Nov 2000 JP
2001-189774 Jul 2001 JP
2001-224075 Aug 2001 JP
2001-251395 Sep 2001 JP
2001-251682 Sep 2001 JP
2001-350782 Dec 2001 JP
2002-094614 Mar 2002 JP
2002-101155 Apr 2002 JP
2002-108794 Apr 2002 JP
2002-152335 May 2002 JP
2002-176449 Jun 2002 JP
2003-8655 Jan 2003 JP
2003-116175 Apr 2003 JP
2003-517781 May 2003 JP
2003-169147 Jun 2003 JP
2003-196469 Jul 2003 JP
2003-296556 Oct 2003 JP
2004-013303 Jan 2004 JP
2004-30371 Jan 2004 JP
WO 9724010 Jul 1997 WO
WO 9803923 Jan 1998 WO
WO 9812644 Mar 1998 WO
WO 0039964 Jul 2000 WO
WO 0069140 Nov 2000 WO
WO 0145368 Jun 2001 WO
WO 0155915 Aug 2001 WO
WO 0169387 Sep 2001 WO
WO 0171925 Sep 2001 WO
WO 0230105 Apr 2002 WO
WO 02093959 Nov 2002 WO
WO 03025776 Mar 2003 WO
WO 03054717 Jul 2003 WO
WO 03096559 Nov 2003 WO
WO 03085539 Oct 2006 WO