Systems and methods for phone call management

Information

  • Patent Grant
  • 7596217
  • Patent Number
    7,596,217
  • Date Filed
    Tuesday, November 25, 2008
    16 years ago
  • Date Issued
    Tuesday, September 29, 2009
    15 years ago
Abstract
A communication system includes client software operating on a PC, or similar platform, and a client telephone that is connected to a call routing server. A user manages telephone communication, including incoming and outgoing calls, conference calls and call forwarding, through the client software. The client software commands the call routing server using instant messenger communication.
Description
BACKGROUND OF THE INVENTION

This application relates to communication and in particular relates to integration of existing communication formats in a manner that provides additional functionality to a user.


Various communication formats are commonly used for electronic communication. In particular, email and instant messenger formats are commonly used for communication through a personal computer (PC) or other device. Telephone communication is generally performed using a dedicated stand-alone telephone device (desktop telephone, cell phone, or other device). In some cases Voice over Internet Protocol (VoIP) may allow telephone communication using a PC or similar device. Generally, some additional hardware is needed to use a PC in this way (e.g. an IP handset). Where a telephone is integrated with a PC in this way (as a softphone) telephone calls are generally made on a peer-to-peer basis. Softphones have certain advantages including the ability to manage telephone communication in ways that are more difficult from a traditional telephone. For example, a call may be made from an address book simply by clicking on the phone number, instead of punching the number into a keypad. A call log may be automatically maintained. Because such features are not generally available with stand-alone telephones, there is a need for better integration of telephone and computer based communication systems to provide additional functions with stand-alone telephones.


SUMMARY OF THE INVENTION

An apparatus for integrated voice and text communication according to an embodiment of the present invention comprises: a call routing server that is connected to a client telephone; an instant messenger server that is in communication with the call routing server and is also in communication via instant messenger with a client device that is associated with the client telephone; and wherein the call routing server manages calls to and from the telephone in response to commands received from the client device via the instant messenger server.


A method of integrating telephone and computer communication according to an embodiment of the present invention comprises: associating a telephone with a client device, the client device having instant messenger communication capability; and managing operation of a call routing server connected to the telephone by instant messenger commands send from the client device.


A method of managing telephone calls to and from a telephone according to an embodiment of the present invention comprises: sending a first instant messenger communication from a client device associated with the telephone to a call routing server that is connected to the telephone, the first instant messenger communication containing information regarding an outgoing telephone call including a destination; the call routing server placing the outgoing telephone call to the destination and connecting the telephone to the destination in response to the first instant messenger communication; and in response to the call routing server receiving an incoming telephone call directed to the telephone, sending a second instant messenger communication to the client device that is associated with the telephone, the second instant messenger communication including information regarding the incoming telephone call.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows a communication system during placement of an outgoing call with client software using IM communication to manage telephone communication through the call routing server.



FIG. 2 shows the communication system as an incoming call is received including the sending of an IM by the call routing server, the IM including call parameters such as start time, error code etc.



FIG. 3 shows the communication system updating presence information for a user when an incoming telephone call is accepted.



FIG. 4 shows the communication system performing a call forwarding operation, the call forwarding operation initiated by client software sending an IM to the call routing server that commands the server to forward the call, and identifying the destination to which the call is to be forwarded.





DETAILED DESCRIPTION OF ILLUSTRATED EMBODIMENTS

According to an embodiment of the present invention, a user has both a client computer and a stand-alone telephone, and manages telephone calls to and from the telephone through the client computer. This provides various features associated with computer management of telephone communication (address book, phone log etc.) while still using legacy telephone technology including stand-alone telephones. Instead of using software on a Personal Computer (PC) as a softphone to replace a traditional telephone, software on a PC may be used to add functionality to a legacy telephone. In this way, if the PC is not used, the telephone may still be used as a telephone in the usual way. Thus, if the PC is not booted up, or if network problems affect communication with the PC, the telephone still functions. When the PC is operating normally, software gives the user many of the advantages of a softphone.


In one example, telephone calls are routed through a Call Routing Server (CRS) and the CRS is managed by Client Software (CS) on a suitable platform such as a PC. One convenient format for communication between the CS and the CRS is Instant Messenger (IM). Several instant messenger formats are currently in widespread use and any of these formats, or similar formats, may be used. Suitable formats include, but are not limited to, ICQ™, AIM™, MSN™, XMPP and Jabber™. A CRS may be configured to receive commands from a CS via IM and to manage telephone communication to and from one or more telephones in response to the IM communication received.



FIG. 1 shows an example of a communication system that uses IM communication to manage telephone calls. A server portion 100 of the communication system includes an Instant Messenger Server (IMS), an Interactive Voice Response Server (IVRS), a Call Routing Server (CRS) a Data Access Server (DAS), a dedicated (or distributed) Data Store (DS) and at least one Phone Gateway (PG). Server portion 100 may also include other components that are not shown here for clarity. For example, more than one of any of the servers listed may be provided.


The IMS comprises computer hardware (CH) and software which includes a data exchange module (DEM), a message handling module (MHM), an authentication and authorization module (AAM) and a presence manager module (PMM). The presence manager module generally maintains presence information regarding users through instant messenger communication.


The IVRS comprises computer hardware (CH) and software which includes an interactive voice response (IVR) module, a call processing module (CPM), a data exchange module (DEM), a messaging module (MM) and a authentication and authorization module (AAM). The IVRS provides the user with information regarding telephone management. The IVRS may inform the user about call status and may obtain user preferences through a phone menu.


The CRS comprises computer hardware (CH) and software which includes a call routing module (CRM), a data exchange module (DEM), an authentication and authorization module (AAM), a phone registration module (PRM) and a messaging module (MM). The CRS is configured so that the CRM may be operated according to commands received by instant messenger.


The DAS comprises computer hardware (CH) and software which includes a data access module (DAM), authentication and authorization module (AAM) and data exchange module (DEM). The DAS acts as a gateway for accessing data stored in the DS.


The DS comprises data storage hardware which could be one or more computer hard drive, flash drive, NAS, SUN or any other data storage device or devices and data management software i.e. data-base management system, file system, etc. The DS is used to store data used by the other servers.


Server portion 100 of the communication system may consist of software on a single hardware platform or may consist of software extending over several hardware platforms. Where several platforms are used, the servers remain in communication with each other using IP protocol. The term “server” is generally used to describe software that performs server functions in relation to a client and is not limited to any particular hardware configuration, though in some cases a server may operate on a dedicated hardware platform (sometimes also referred to as a server). In one example, the server portion consists of several software servers on a single hardware platform, each server performing a different function.


Server portion 100 may be connected to one or more Client Agents (CAs). Only one CA is shown in FIG. 1 for clarity, though in many systems a server portion serves many CAs. The CA includes a CS operating on a PC in the present example, and a Client Phone (CP), which is a stand-alone telephone in the present example. In other examples, the CP may be a softphone operating on the same PC as the CS. In other examples, the CA may be a mobile device having both IM and telephone capability.


The CA has a unique identifier (agent-id), and any other CAs that are connected to server portion 100 also have unique identifiers. The CS has a unique location identifier (s-location-id), and any other CSs that are connected to the server portion also have unique location identifiers. The CP has a unique device identifier (device-id) and a device location identifier (d-location-id), and any other CPs that are connected to the server portion also have unique device and location identifiers. In addition, all telephone calls passing through the CRS have a unique identifier (call-id) and each instant message contains the sender's signature and is uniquely identifiable.


Communication between components of the present system may be secure (encrypted) or not secure (unencrypted). A user may select a security setting according to the level of security desired.


The CA is connected to the IMS for communication by instant messenger. The CP is registered with the CRS, so that the CRS can select the CP as a destination for a telephone call and recognizes the CP as a valid origination point for telephone call. The CS is associated with the CP and information that the two components are linked may be stored in the DS. The CS may be linked to the CP by associating the CP's d-location-id and device-id with the s-location-id of the CS. In some cases, these are associated by a person who configures the system. In some cases, there may be a default scheme that associates a particular CP with a CA.


During startup of the CS, the CS requests information about the CRS and IMS from the DS. This allows the CS to communicate with the CRS via instant messenger. The CRS then recognizes IM communication from the CS as commands and manages telephone calls to and from the CP according to those commands.



FIG. 1 shows the situation where a user makes an outgoing call from the CP using the CS. For example, instead of dialing a number directly on the CP, a user may consult an address book through the CS and dial the number directly from the address book. In response to the user's selection of a particular number to dial, the CS sends an IM 102 “IM-Originate call” that contains information about the call to be placed. In particular, IM 102 contains signal information required by call control protocol, call-id, device-id and d-location-id for the CP and s-location-id for the CS. In other examples, the CS may send device-ids and d-location-ids for multiple devices. For example, the user may wish to initiate a conference call by calling a list of people together.


IM 102 is sent from the CS to the IMS, where it is directed to the CRS. When the CRS receives IM 102 from the CS, it initially establishes a call between the IVRS and the CP (based on the device-id provided in the IM 102). For example, the CP may ring, indicating a call so that the user picks up the handset. The IVRS then plays a prerecorded message to the user. For example, “Your call is being placed, please hold.” While this message is being played, the IVRS initiates a call to the destination 104 (telephone number) indicated by the user via the CRS. In the example of FIG. 1, the outgoing call goes through the PG, though in other cases the call may go to another CA that is connected to server portion 100. When the call from the CRS to destination 104 is connected (e.g. when the person at the other end picks up the phone), the prerecorded message stops and the IVRS connects the two calls so that the user of the CP is in telephone contact with the destination. If the call to destination 104 is not successful, the CRS informs the IVRS and the IVRS may play a prerecorded message to the user indicating that the call was not successful.



FIG. 2 shows the communication system of FIG. 1 during receipt of an incoming call. A call is received by the CRS through the PG. The call contains information regarding the destination. In this case the destination is the CP, identified by device-id or d-location-id. The CRS directs the call to the CP causing the CP to ring, or otherwise indicate an incoming call. In addition, the CRS sends an IM 210, “IM-Call parameters,” to the CS via the IMS. IM-Call parameters contains information about the call including start time, error code information etc. If the call is sent to multiple destinations, IM 210 may be sent to all destinations. Also, if the call is transferred the transfer destination receives the IM 210. Other events such as the call being placed on hold, answered or hung up may also cause the CRS to send an IM to the CA or other CAs.


When IM 210 is received by the CA, the CRS is identified so that the CA can respond with an appropriate command according to the user's preferences. The user may be presented with information about the incoming call on screen and also presented with options such as “transfer the call,” “put call on hold,” or “hang-up the call,” etc. The user can respond by picking up the handset of the CP or can respond through the CS. When the user responds through the CS, the CS sends an IM to the CRS that identifies the call-id and specifies what action the CRS should take with the call.


One feature of instant messenger systems that is useful in efficient communication is presence awareness. Generally, IM systems maintain presence state information for all users. A user may be assigned a presence state from a finite set of presence states. A user's presence state may be used to manage communication. When the user is on the phone (i.e. has placed an outgoing call or accepted an incoming call), the user's presence state may be updated accordingly. FIG. 3 shows such an updating operation that occurs after the user accepts the telephone call of FIG. 2. Because the user has accepted the incoming telephone call, the CRS sends an IM 320 (IM-Change presence) to the CS, via the IMA, requesting the CS to update presence information for the user. In this case, the requested update is to change the user's presence state to “on the phone.” In other cases, a request may be made to change the user's presence state to a different state such as “away,” “available,” or some other state. The CS makes this change in response and the change may be reflected in the status of the user as shown to other people connected to the server portion. For example, if the user was involved in an IM exchange, the user's status would change to “on the phone” and other participants would see the change and would be able to act accordingly. Any time the user accepts a call, transfers away a call, places a call on hold, hangs up a call or otherwise changes the user's condition, the CRS may send an IM to the CS requesting that the CS change the user's presence state.


An alternative outcome to that shown in FIGS. 2 and 3 (where the user accepts the incoming call) is shown in FIG. 4. In the example of FIG. 4, the user of the CA does not accept the call. Instead the user forwards the call to an alternate device 430 with a different device identifier “Alt device-id.” As in the example, the CRS sends an IM 432, “IM-Call parameters” to the CS, via the IMS. This may cause the CS to display various options to the user including forwarding the call. Alternatively, the user may have selected an option to automatically forward the call to alternate device 430. In either case, the CS sends an IM 434 “IM-reply” to the CRS, via the IMS. IM 434 includes the command to forward the call and the destination to which the call is to forwarded (Alt device-id). The CRS may then send the call to alternate device 430 in the same manner as previously described (sending an IM) or otherwise. If the call is accepted by the user of alternate device 430, the CRS connects the incoming call to alternate device 430. A call may also be transferred away after a user has initially accepted the call in a manner similar to that described above.


In addition to the operations shown, the CS may send an IM command to the CRS to add more callers to an ongoing telephone call. Thus, multiple callers may be conferenced into a conference call using a PC interface instead of using a telephone interface, which is often not as user friendly. The CS may send an IM command to the CRS to place an ongoing call on hold or to hang up the call.


While the examples discussed above show a single CP controlled through a CRS by a CP, in other examples one CS may control more than one CP and such CPs may not be close to the CS. For example, a single PC in a call-center may control the distribution of calls to various employees, with instant messenger used as the communication format to command the CRS (or CRSs).


While the examples discussed above include a PC and a stand-alone telephone, the methods described may be used with other hardware also. Telephone calls to and from a softphone may also be managed as described.


All patents, patent applications, articles, books, specifications, other publications, documents and things referenced herein are hereby incorporated herein by this reference in their entirety for all purposes. To the extent of any inconsistency or conflict in the definition or use of a term between any of the incorporated publications, documents or things and the text of the present document, the definition or use of the term in the present document shall prevail.


Although the various aspects of the present invention have been described with respect to certain preferred embodiments, it is understood that the invention is entitled to protection within the full scope of the appended claims.

Claims
  • 1. A method of managing telephone calls to and from a user's telephone comprising: sending a first instant messenger communication from a client device associated with the telephone to a call routing server that is connected to the telephone, the first instant messenger communication containing information regarding an outgoing telephone call including a destination;the call routing server placing the outgoing telephone call to the destination and connecting the telephone to the destination in response to the first instant messenger communication; andin response to the call routing server receiving an incoming telephone call directed to the telephone, sending a second instant messenger communication to the client device that is associated with the telephone, the second instant messenger communication including information regarding the incoming telephone call;wherein the incoming telephone call is transferred in response to an instant messenger command sent from the client device to the call routing server, the instant messenger command being dependent on presence information regarding the user.
  • 2. The method of claim 1 further comprising connecting the telephone to an interactive voice response server while the call routing server places the outgoing telephone call, prior to connecting the telephone to the destination, the interactive voice response server providing voice information to the telephone.
  • 3. The method of claim 1 wherein another incoming telephone call is placed on hold in response to another instant messenger command sent from the client device to the call routing server, the another instant messenger command being dependent on presence information regarding the user.
  • 4. The method of claim 1 wherein another incoming telephone call is hung-up in response to another instant messenger command sent from the client device to the call routing server, the another instant messenger command being dependent on presence information regarding the user.
  • 5. A system for managing telephone calls to and from a user's telephone comprising: a client device associated with the telephone configured to send a first instant messenger communication to a call routing server that is connected to the telephone, the first instant messenger communication containing information regarding an outgoing telephone call including a destination;the call routing server configured to place the outgoing telephone call to the destination and connecting the telephone to the destination in response to the first instant messenger communication; andthe call routing server sending a second instant messenger communication to the client device associated with the telephone in response to the call routing server receiving an incoming telephone call directed to the telephone, the second instant messenger communication including information regarding the incoming telephone call;wherein the incoming telephone call is transferred in response to an instant messenger command sent from the client device to the call routing server, the instant messenger command being dependent on presence information regarding the user.
  • 6. The system of claim 5 wherein the call routing server connects the telephone to an interactive voice response server while the call routing server places the outgoing telephone call prior to connecting the telephone to the destination, the interactive voice response server providing voice information to the telephone.
  • 7. The system of claim 5 wherein the call routing server places another incoming telephone call on hold in response to another instant messenger command sent from the client device to the call routing server, the another instant messenger command being dependent on presence information regarding the user.
  • 8. The system of claim 5 wherein the call routing server hangs up another incoming telephone call in response to another instant messenger command sent from the client device to the call routing server, the another instant messenger command being dependent on presence information regarding the user.
CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation of U.S. patent application Ser. No. 11/743,059 filed on May 1, 2007, entitled “Systems And Methods For Phone Call Management,” which is hereby incorporated by reference in its entirety.

US Referenced Citations (187)
Number Name Date Kind
1479442 Adendorff Jan 1924 A
3221107 Seemann et al. Nov 1965 A
3479465 Masucci Nov 1969 A
4953159 Hayden et al. Aug 1990 A
5012511 Hanle et al. Apr 1991 A
5060255 Brown Oct 1991 A
5309513 Rose May 1994 A
5327486 Wolff et al. Jul 1994 A
5335269 Steinlicht Aug 1994 A
5515428 Sestak et al. May 1996 A
5557667 Bruno et al. Sep 1996 A
5647002 Brunson et al. Jul 1997 A
5654961 Araujo et al. Aug 1997 A
5696809 Voit Dec 1997 A
5740237 Malik et al. Apr 1998 A
5796394 Wicks et al. Aug 1998 A
5875302 Obhan Feb 1999 A
6069949 Schuenhoff et al. May 2000 A
6192048 Nelson et al. Feb 2001 B1
6208658 Pickett Mar 2001 B1
6212268 Nielsen Apr 2001 B1
6285752 Rice Sep 2001 B1
6324264 Wiener et al. Nov 2001 B1
6404747 Berry et al. Jun 2002 B1
6438222 Burg Aug 2002 B1
6442268 Klaghofer et al. Aug 2002 B1
6529502 Sarkissian et al. Mar 2003 B2
6560222 Pounds et al. May 2003 B1
6580787 Akhteruzzaman et al. Jun 2003 B1
6587556 Judkins et al. Jul 2003 B1
6625141 Glitho et al. Sep 2003 B1
6633848 Johnson et al. Oct 2003 B1
6640230 Alexander et al. Oct 2003 B1
6658095 Yoakum et al. Dec 2003 B1
6747970 Lamb et al. Jun 2004 B1
6766012 Crossley Jul 2004 B1
6792085 Rigaldies et al. Sep 2004 B1
6807254 Guedalia et al. Oct 2004 B1
6810116 Sorensen et al. Oct 2004 B1
6816578 Kredo et al. Nov 2004 B1
6816589 Pinard Nov 2004 B2
6832245 Isaacs et al. Dec 2004 B1
6836480 Basso et al. Dec 2004 B2
6836893 Pinard Dec 2004 B2
6839736 Kajita et al. Jan 2005 B1
6895558 Loveland May 2005 B1
6904140 Trossen Jun 2005 B2
6917610 Kung et al. Jul 2005 B1
6920208 Rosen et al. Jul 2005 B1
6985576 Huck Jan 2006 B1
7003091 Burns et al. Feb 2006 B1
7007085 Malik Feb 2006 B1
7023980 Lenard Apr 2006 B2
7027463 Mathew Apr 2006 B2
7039411 Purdy et al. May 2006 B2
7047030 Forysyth May 2006 B2
7062021 Starbuck et al. Jun 2006 B2
7076043 Curbow et al. Jul 2006 B2
7103167 Brahm et al. Sep 2006 B2
7117445 Berger Oct 2006 B2
7136475 Rogers et al. Nov 2006 B1
7180888 Crouch et al. Feb 2007 B1
7184525 Arnoff et al. Feb 2007 B2
7185054 Ludwig et al. Feb 2007 B1
7187761 Bookstaff Mar 2007 B2
7194523 Nelson et al. Mar 2007 B2
7212617 Owens et al. May 2007 B2
7222156 Gupta et al. May 2007 B2
7224774 Brown et al. May 2007 B1
7245711 Margolis Jul 2007 B2
7254641 Broughton et al. Aug 2007 B2
7269163 Koch et al. Sep 2007 B1
7274778 Hanson et al. Sep 2007 B2
7286661 Balk et al. Oct 2007 B1
7313617 Malik et al. Dec 2007 B2
7334021 Fletcher Feb 2008 B1
7382868 Moore et al. Jun 2008 B2
7412657 Forlenza et al. Aug 2008 B2
7424537 Bennett et al. Sep 2008 B2
20020075304 Thompson et al. Jun 2002 A1
20020076025 Liversidge et al. Jun 2002 A1
20020085701 Parsons et al. Jul 2002 A1
20020098831 Castell et al. Jul 2002 A1
20020099777 Gupta et al. Jul 2002 A1
20020116461 Diacakis et al. Aug 2002 A1
20030023691 Knauerhase Jan 2003 A1
20030035528 Baker Feb 2003 A1
20030037113 Petrovykh Feb 2003 A1
20030041048 Balasuriya Feb 2003 A1
20030123431 Geck et al. Jul 2003 A1
20030129967 Verona Jul 2003 A1
20030135569 Khakoo et al. Jul 2003 A1
20030152203 Berger et al. Aug 2003 A1
20030163819 Lee et al. Aug 2003 A1
20030174815 Didcock et al. Sep 2003 A1
20030229722 Beyda Dec 2003 A1
20040002359 Deas et al. Jan 2004 A1
20040054646 Daniell et al. Mar 2004 A1
20040064514 Daniell et al. Apr 2004 A1
20040086100 Moore et al. May 2004 A1
20040141594 Brunson et al. Jul 2004 A1
20040170263 Michael et al. Sep 2004 A1
20040213400 Golitsin et al. Oct 2004 A1
20040215723 Chadha Oct 2004 A1
20040240642 Crandell et al. Dec 2004 A1
20040252679 Williams et al. Dec 2004 A1
20040267871 Pratley et al. Dec 2004 A1
20050013421 Chavez et al. Jan 2005 A1
20050020288 Davis et al. Jan 2005 A1
20050027867 Mueller et al. Feb 2005 A1
20050041793 Fulton et al. Feb 2005 A1
20050071241 Flockhart et al. Mar 2005 A1
20050074113 Mathew et al. Apr 2005 A1
20050080852 Kelley et al. Apr 2005 A1
20050084079 Lang Apr 2005 A1
20050100145 Spencer et al. May 2005 A1
20050144291 Frank et al. Jun 2005 A1
20050190744 Sun et al. Sep 2005 A1
20050201362 Klein et al. Sep 2005 A1
20050213724 O'Brien et al. Sep 2005 A1
20050220286 Valdez et al. Oct 2005 A1
20050238157 Shaffer et al. Oct 2005 A1
20050251555 Little, II Nov 2005 A1
20050257142 Lai et al. Nov 2005 A1
20050259808 Andrews et al. Nov 2005 A1
20050275878 Hiatt et al. Dec 2005 A1
20060002536 Ambrose Jan 2006 A1
20060023695 Yarlagadda et al. Feb 2006 A1
20060025164 Wang et al. Feb 2006 A1
20060026232 Malik Feb 2006 A1
20060031510 Beck et al. Feb 2006 A1
20060039545 Rahman et al. Feb 2006 A1
20060053208 Laurila et al. Mar 2006 A1
20060053225 Poikselka et al. Mar 2006 A1
20060085242 Mark Apr 2006 A1
20060092970 Song et al. May 2006 A1
20060095575 Sureka et al. May 2006 A1
20060117098 Dezonno et al. Jun 2006 A1
20060140176 Farris et al. Jun 2006 A1
20060142012 Kirchhoff et al. Jun 2006 A1
20060161632 Wu et al. Jul 2006 A1
20060161872 Rytivaara et al. Jul 2006 A1
20060177030 Rajagopalan et al. Aug 2006 A1
20060195585 Samayamantry Aug 2006 A1
20060210047 Neyman et al. Sep 2006 A1
20060252444 Ozugur Nov 2006 A1
20060256816 Yarlagadda et al. Nov 2006 A1
20060265347 Caballero-McCann et al. Nov 2006 A1
20060276179 Ghaffari et al. Dec 2006 A1
20070016647 Gupta et al. Jan 2007 A1
20070042792 Perfetto et al. Feb 2007 A1
20070058637 Lo Mar 2007 A1
20070101144 Owen et al. May 2007 A1
20070124371 Desai et al. May 2007 A1
20070130260 Weintraub et al. Jun 2007 A1
20070130340 Alperin et al. Jun 2007 A1
20070143433 Daigle Jun 2007 A1
20070203977 Wu et al. Aug 2007 A1
20070206738 Patel et al. Sep 2007 A1
20070271376 Yach Nov 2007 A1
20070276937 Chavda et al. Nov 2007 A1
20080002820 Shtiegman et al. Jan 2008 A1
20080005239 Podl Jan 2008 A1
20080037583 Dawes et al. Feb 2008 A1
20080043986 Darby Feb 2008 A1
20080056454 Lahtiranta et al. Mar 2008 A1
20080059579 Maes Mar 2008 A1
20080062970 Picard et al. Mar 2008 A1
20080065974 Campbell Mar 2008 A1
20080075241 Kent et al. Mar 2008 A1
20080101224 Khasnabish May 2008 A1
20080104169 Combel et al. May 2008 A1
20080148154 Burrell et al. Jun 2008 A1
20080155080 Marlow et al. Jun 2008 A1
20080212762 Gray et al. Sep 2008 A1
20080247530 Barton et al. Oct 2008 A1
20080249778 Barton et al. Oct 2008 A1
20080261630 Wormald et al. Oct 2008 A1
20080263459 Altberg et al. Oct 2008 A1
20080298566 Scott et al. Dec 2008 A1
20080299948 Rosener Dec 2008 A1
20080313329 Wang et al. Dec 2008 A1
20080317223 Koch Dec 2008 A1
20080320148 Capuozzo et al. Dec 2008 A1
20090009343 Boyer et al. Jan 2009 A1
20090029690 Levien et al. Jan 2009 A1
20090060155 Chingon et al. Mar 2009 A1
Foreign Referenced Citations (27)
Number Date Country
0 510 411 Oct 1992 EP
0 641 112 Mar 1995 EP
0881802 Dec 1998 EP
1499097 Jan 2005 EP
1551 164 Jul 2005 EP
921659 Aug 2005 EP
1589733 Oct 2005 EP
1657871 May 2006 EP
1720330 Nov 2006 EP
5290060 Nov 1993 JP
8032618 Feb 1996 JP
2000049851 Feb 2000 JP
2004070752 Mar 2004 JP
2005159439 Jun 2005 JP
2006127142 May 2006 JP
WO 9718661 May 1997 WO
WO 9918697 Apr 1999 WO
WO 0016207 Mar 2000 WO
WO 0250722 Jun 2002 WO
WO03039128 May 2003 WO
WO 2004063854 Jul 2004 WO
WO 2005006165 Jan 2005 WO
WO 2005048121 May 2005 WO
WO 2005083995 Sep 2005 WO
WO 2005109844 Nov 2005 WO
WO 2006082506 Aug 2006 WO
WO 2006118651 Nov 2006 WO
Related Publications (1)
Number Date Country
20090067595 A1 Mar 2009 US
Continuations (1)
Number Date Country
Parent 11743059 May 2007 US
Child 12277999 US