The present invention is generally related to recording media communications and, more particularly, is related to systems and methods for recording the media communications through a customer center.
A traditional passive tap recording technique includes recorders that are deployed along routes of communications. In this technique, each recorder operates similar to a “sniffer” by analyzing pass-by communication packets. The recorder records the packets corresponding to certain communication sessions based on its configuration.
With the growing usage of Voice over Internet Protocol (VoIP) technology, many telephony-based businesses, such as customer centers, are adopting distributed telephony systems with local access to PSTN, which are still controlled by centralized soft switches. Many customer centers are using at-home agents with soft-phones on their personal computers (PCs). Hence, some of the communications in the distributed telephony system may not be “along the communication route” that is needed for passive tap recording. Secondly, network security has now become a concern. The deployment of encryption technology has made passive tap recording become even more problematic.
In addition, many customer centers deploy recorders for quality monitoring purposes, instead of compliance. In this regard, only a small percentage of the communications are recorded, monitored, and sampled. However, to assure the accuracy of the sampling, communications are randomly selected for recording across all branch offices. With passive tap recording, a large number of recorders are potentially required and each recorder may have low usage.
A typical IP-based customer center using the passive tapping “sniffing” recording method is shown in
After several rounds of communication signals exchange, media communications between the agent's phone and customer's phone can proceed via media processing device and distribution devices. The distribution devices are network routers and switches. In order to record the media communications using passive tapping, recorders are deployed at the media processing device or distribution devices using the network traffic monitoring or duplicating features, such as the Cisco's Switch Port Analyzer (SPAN) feature, on these devices. These tapping features are often available to the recorders that are directly connected to the media processing device or distribution devices, namely to recorders deployed at each branch office. Hence, a large customer center having multiple branches, such as a branch in New York, a branch in Los Angeles, and a branch in Chicago, may need multiple recorders in each branch to record the voice communications.
Embodiments of the present invention provide systems and methods for recording media communications. An exemplary method is comprised of the following steps: configuring an endpoint recording device for relaying an incoming call to an endpoint component; receiving the incoming call from a communication system; determining whether to relay the incoming call to the endpoint component based on the configurations of the endpoint recording device; responsive to determining that the incoming call is to be relayed, relaying media communications associated with the incoming call to the endpoint component via the endpoint recording device; and recording the relayed media communications at the endpoint component.
Customer center includes, but is not limited to, outsourced contact centers, outsourced customer relationship management, customer relationship management, voice of the customer, customer interaction, contact center, multi-media contact center, remote office, distributed enterprise, work-at-home agents, remote agents, branch office, back office, performance optimization, workforce optimization, hosted contact centers, and speech analytics, for example.
Other systems, methods, features, and advantages of the present invention will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
Many aspects of the invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
Disclosed herein are systems and methods for recording communication signals. In particular, the recording of the communication signals can be achieved using a soft switch, a conference bridge, a soft phone, a media communication device, a media application server and/or a gateway. In some embodiments, this can be accomplished without having a recorder directly connected to a switch or voice gateway for passive tape recording.
Exemplary systems are first discussed with reference to the figures. Although these systems are described in detail, they are provided for purposes of illustration only and various modifications are feasible. After the exemplary systems are described, examples of flow diagrams and sequence diagrams of the systems are provided to explain the manner in which the communication signals can be recorded.
Referring now in more detail to the figures,
Recording device(s) 226 can be deployed anywhere on the IP network 219 connected to the branch offices 203, 206. Alternatively or additionally, the recording devices 226 can communicate with media controlling/processing/distributing devices 213, 231 in a secure fashion in encrypted environments, for getting communication events and for sending instructions. With the capability of the recording devices 226 to communicate with the media controlling/processing/distributing devices 213, 231, the recording device 226 can selectively record communications in the customer center using business rule policy. Alternatively or additionally, if a recording device is a cluster of recording devices, the recording device can communicate with the media controlling/processing/distributing devices 213, 231 to select which recording device from the cluster of recording devices to record the communications for load balancing purposes.
The media controlling/processing devices control the communication between customers and agents and between agents. The media controlling/processing devices can include, but are not limited to, voice gateways, soft switches, conference bridges, and multi-media application servers. The distributing devices can include, but are not limited to, routers and switches. Based on static configuration or instructions from the recording devices, the media controlling/processing devices can duplicate and transmit on-going communication between communication devices 209, 229, 223, 236 to the recording devices via the IP network 219 using its media processing features, such as conferencing. Alternatively or additionally, the media controlling/processing devices can also instruct the communication devices 209, 229 at the company premises 203, 231, respectively, to duplicate and transmit any on-going communications to the recording devices 226 using media processing features on the communication devices 209, 229. The operation of the system 200 is further described in relation to
In this embodiment, the soft switch 306 is operative to send a command to the agent phones 319, 323, 326 and voice gateway 306 via the company network 316, instructing the agent phones 319, 323, 326 and voice gateway 306 to transmit voice communications associated with the incoming calls through the conference bridge 309 via the company network 316. The soft switch 306 also sends a command to the conference bridge 309 via the company network 316 to duplicate and transmit the voice communications to the voice endpoint recorder 339 using the IP network 333. The operation of the system 300 is further described in relation to
Alternatively or additionally, the soft switch 306 can receive instructions for recording the voice communications from the voice endpoint recorder 339 via the IP network 333. In turn, the soft switch 306 sends a command based on the received instructions to the conference bridge 309. Alternatively or additionally, the soft switch 306 can have capabilities of a conference bridge. That is, the soft switch 306 can duplicate and transmit the voice communications without using the conference bridge 309 to the voice endpoint recorder 339. The soft switch 306 with conferencing capabilities is added value to companies with a small number of agent phones.
As shown in
Agent phones 449, 453 within the branches 443, 446 can receive voice communications from within the customer center premises 403 or from customer phone 429. The soft switch 406 can send a command to the agent phones 449, 453, instructing the agent phones 449, 453 to transmit the voice communications through the conference bridge 409 via the IP network 433. The soft switch 406 also can send a command to the conference bridge 409 via the company network 416 to duplicate and transmit the voice communications to the voice endpoint recorder 439 using the IP network 433. The operation of the system 400 will also be described in greater detail in relation to
As in
In this embodiment, the media application server 609 includes a media controller 606 and a media processor 607. The media controller 606 receives incoming media communications, identifies the type of media communications, and routes the media communications to the media communication devices 619, 623 via the company network 616. The media controller 606 can send a command to the media communication devices 619, 623 via the company network 616, instructing the media communication devices 619, 623 to transmit the media communications through the media application server 609 via the company network 616. Once the media application server 609 receives the media communications, the media processor 607 duplicates and transmits the media communications to the media endpoint recorder 639 using the IP network 633. Alternatively or additionally, the media controller 606 can receive instructions for recording the media communications from the media endpoint recorder 639 via the IP network 633. In turn, the media controller 606 sends a command based-on the received instructions to the media processor 607. The operation of the system 600 is further described in relation to
Alternatively or additionally, the media communication devices 619, 623 can have the capabilities of duplicating and transmitting the media communications to a media endpoint recorder 639. For example, the media controller 606 manages the media communications and routes the media communications to the media communication devices 619, 623 via the company network 616. The media controller 606 communicates with the media communication devices 619, 623 to determine whether the communication devices 619, 623 can duplicate and transmit the media communications to the media endpoint recorder 639. If the communication devices 619, 623 have the capability, the media controller 606 instructs the media communication devices 619, 623 via the company network 616 to duplicate and transmit media communications to the media endpoint recorder 639 using the IP network 633. Alternatively or additionally, the media controller 606 can receive instructions for recording the media communications from the media endpoint recorder 639 via the IP network 633. In turn, the media controller 606 sends a command based on the received instructions to the communication devices 619, 623.
In one scenario, for example, calls from a customer phone can be routed to the voice gateway 713, which can route the calls to the soft switch 706. The soft switch 706 receives incoming calls and routes the calls to the agent phones 719, 723, 726. The soft switch 706 communicates with the conference bridge 709 via the company network 716. The IP telephony system 703 communicates with a voice endpoint recorder 739 via an IP network 733. In this example, the soft switch 706 is operative to send a command to the agent phones 719, 723, 726 and voice gateway 706 via the company network 716, instructing the agent phones 719, 723, 726 and voice gateway 713 to transmit voice communications associated with the incoming calls through the conference bridge 709 via the company network 716. The soft switch 706 also sends a command to the conference bridge 709 via the company network 716 to duplicate and transmit the voice communication to the voice endpoint recorder 739 using the IP network 733. In another scenario, for example, the soft switch 706 can have capabilities of a conference bridge, as mentioned above. The soft switch 706 can duplicate and transmit the voice communications without the conference bridge 709 to the voice endpoint recorder 739 using the IP network 733.
In yet another scenario, for example, the soft switch 706 communicates with the agent phones 719, 723, 726 to determine whether the phones can duplicate and transmit the voice communications to an endpoint recorder 739. If the agent phones have the capability, the soft switch 706 instructs the agent phones 719, 723, 726 via the company network 716 to duplicate and transmit the voice communications associated with the incoming calls to the voice endpoint recorder 739 using the IP network 733.
In yet another scenario, for example, the media application server 749 receives incoming media communications, identifies the type of media communications, and routes the media communications to media communication devices 759, 763 via the company network 716. The media application server 749 can send a command to the media communication devices 759, 763 via the company network 716, instructing the media communication devices 759, 763 to transmit the media communications through the media application server 749 via the company network 716. The media application server 749 duplicates and transmits the media communications to the media endpoint recorder 743 using the IP network 733.
In yet another scenario, for example, the media communication devices 759, 763 can have the capabilities of duplicating and transmitting the media communications to a media endpoint recorder 743. For example, the media application server 749 manages the media communications and routes the media communications to the media communication devices 759, 763 via the company network 716. The media application server 749 communicates with the media communication devices 759, 763 to determine whether the communication devices 759, 763 can duplicate and transmit the media communications to the media endpoint recorder 743. If the communication devices 759, 763 have the capability, the media application server 749 instructs the media communication devices 759, 763 via the company network 716 to duplicate and transmit the media communications to the media endpoint recorder 743 using the IP network 733.
In yet another scenario, for example, the voice gateway 713 can perform the functions of duplicating and transmitting the voice communications to the voice endpoint recorder 739. For example, the voice gateway 713 receives instructions to record voice communications from the soft switch 706. It should be noted that the soft switch can receive the recording instructions from the media endpoint recorder 743. The voice gateway 713 receives, manages, and routes the voice communications to the agent phones 719, 723, 726 via the company network 716. The voice gateway 713 determines whether to record the received voice communications at the agent phones 719, 723, 726 according to the received instructions. If the voice gateway 713 determines that the voice communications are to be recorded, the voice gateway 713 duplicates and transmits the voice communications to the voice endpoint recorder 739 using the IP network 733.
In yet another scenario, for example, the voice gateway 713 is operative to be configured to duplicate the voice communications and transmit the duplicated voice communications to a second voice gateway (not shown). The second voice gateway transmits the duplicated voice communications to the desired endpoint component, such as the media endpoint recorder 743, another endpoint
In yet another scenario, for example, the voice gateway 713 is operative to pass the voice communications to the second gateway. The second gateway is operative to be configured to duplicate the voice communications and transmit the duplicated voice communications to the desired endpoint component.
Alternatively or additionally, the voice endpoint recorder 739 is operative to be configured to duplicate and transmit voice communications. The voice endpoint recorder 739 is operative to duplicate and transmit the voice communications to the desired endpoint component using one of an endpoint component name, an IP address, a SIP address, and a domain name system (DNS) name of the desired endpoint component across the company and/or IP networks 716, 733. Some reasons, among others, to transfer recorded media communications from one recorder to another include load balancing the recorders, archive, and replay. The operation of an endpoint recording device is further described in relation to
It should be noted that the systems 200, 300, 400, 500, 600, 700 can perform a service observation or a silent conference. Service observation is an extension-based monitoring functionality where an agent's communication is monitored when there is activity using a service observe access code entered along with the agent's IP address/port. The service observation enables supervisors to listen or view the media communication while the media communications take place. Silent conference is the ability to conference a monitored media communication into a conversation without “conference announcements” or indications.
It should be noted that the proxy server 835 is shown in
In general, incoming calls arrive at the gateway 823, which serves the incoming and outgoing traffic. The soft switch 830 instructs the gateway 823 to route the incoming calls based on customer center policy. Many incoming calls are routed to the IVR 827 before transitioning the call to an available agent in one of potentially many customer centers. It should be noted that the gateway 823, proxy server 835, PBX communication (not shown) and other switching device or network devices (not shown) can also route the incoming calls according to the customer center policy.
The soft switch 830 is operative to monitor incoming calls and invoke duplicate media streaming from the gateways. For example, the soft switch 830 can monitor a route point and identify an agent who potentially will receive the call or a dialed number identification service (DNIS) that had been dialed, among others. The recording system 833 receives an event corresponding to the incoming call and determines if the media streams associated with the incoming call should be recorded based on defined business rules. If the media streams are to be recorded, the recording system 833 issues a command to the soft switch 830, such as a computer-telephone integration (CTI) server. In turn, the soft switch 830 instructs the gateway 823 to duplicate the media streams associated with the incoming call and deliver the duplicated media streams to a specific recorder.
Once instructed to record the incoming call, the gateway 823 delivers the media streams to the recorder by issuing a session initiation protocol (SIP) invite to the recorder, which in turn responds with an “OK.” Alternatively or additionally, the proxy server 835 may be used to distribute the incoming call to a plurality of recorders configured, for example, as a high availability system. The gateway 823 continues to transmit the media streams associated with the incoming calls to the recorder regardless of how the call is routed within the switch or between call centres. In turn, the recorder continues to receive event streams about the incoming calls as the calls transition within the customer center and potentially are transferred between customer centers.
If the media streams are to be recorded while in an IVR platform, the soft switch 830 can be used to instruct the gateway 823 to duplicate the media streams, which provides cradle to grave recording from the point of first contact with the customer and also enables the validation of the IVR handling.
Alternatively or additionally, the gateway 823 can receive instructions from a call manager (not shown) to duplicate the media stream from an agent handset. Alternatively or additionally, the gateway 823 can receive instructions from a call manager JTAPI interface or other CTI event interfaces (not shown) such that this mechanism might be used in topologies where phone DMS (duplicate media streaming) is not practical or where the customer has made a large purchase in handsets which do not support DMS.
Alternatively or additionally, the soft switch 830 can facilitate recording media streams associated with the incoming calls without the recording system constantly monitoring the event stream of the soft switch 830. The soft switch 830 can be configured to record or not record on an extension based on some pre-existing configuration. For example, as soon as the soft switch 830 detects an incoming call for a particular extension, the soft switch 830 can route the duplicate media streams to the appropriately configured recorder of the recording system 833. The gateway 823 receives instructions from the soft switch 830 and transmits SIP (Session Initiation Protocol) messaging for the duplicated media stream associated with the incoming call to the recorder. The SIP messaging is verbose enough such that the origin and reason for the call being recorded can be tagged without the soft switch events. The SIP messaging, includes, for example, the extension number and agent identification of the agent receiving the incoming call.
Alternatively or additionally, internal calls within the customer center can be recorded in certain scenarios. For example, incoming calls can be routed through a back-to-back gateway configuration such that the gateways can be instructed via the soft switch 830 to duplicate media streams associated with the incoming calls.
At event 1008, the soft switch instructs the conference bridge to duplicate and transmit the voice communication to a voice endpoint recorder. The instruction to the conference bridge can include an IP address/port of the voice endpoint recorder. At event 1009, the second soft phone transmits the voice communication to the conference bridge such as by using the IP address/port of the conference bridge. At event 1013, the conference bridge duplicates the voice communication from the second soft phone and transmits the duplicated voice communication such as by using the IP address/port of the voice endpoint recorder. Notably, the voice endpoint recorder can be located virtually anywhere in the customer center premises as long as the recorder is connected to a network.
At event 1016, the conference bridge routes the voice communication from the second soft phone to the first soft phone or the voice gateway. At event 1019, the first soft phone or the voice gateway transmits the voice communication to the conference bridge such as by using the IP address/port of the conference bridge. At event 1023, the conference bridge duplicates the voice communication from the first soft phone or the voice gateway and transmits the duplicated voice communication to the recorder such as by using the IP address/port of the recorder. At event 1026, the conference bridge routes the voice communication from the first soft phone or the voice gateway to the second soft phone of the customer center premises. Thereafter, the sequence is returned to event 1009 so that the second soft phone can transmit the voice communication to the conference bridge as instructed by the soft switch, as shown at event 1029.
At event 1109, the second soft phone receives the voice communication from the first soft phone or the voice gateway, duplicates the voice communication and transmits the duplicated voice communication to the recorder such as by using the IP address/port of the recorder. At event 1113, the second soft phone transmits the voice communication to the first soft phone or the voice gateway. At event 1116, the first soft phone or the voice gateway transmits its voice communication to the second soft phone using the IP address of the second soft phone. At event 1119, the sequence is returned to event 1109 during which the second soft phone receives the voice communication from the first soft phone or the voice gateway, duplicates the voice communication and transmits the duplicated voice communication to the recorder.
At event 1219, the communication devices transmit the media communications to the media application server such as by using the IP address/port of the media application server. In turn, the media application server receives and transmits the media communications to the communication devices. At event 1223, the media application server duplicates the media communication from the communication devices and transmits the duplicated media communications such as by using an IP address/port of a media endpoint recorder. At event 1226, the sequence is returned to event 1219 during which the media application server duplicates the media communications between the calling and called communication devices and transmits the duplicated media communications to the recorder.
At event 1309, the gateway routes the voice communications to a phone of the customer center premises and instructs the phone to transmit the voice communications through the gateway. The instructions to the phone can include an IP address/port of the gateway. The gateway further determines whether to record the voice communications of the call based on the received instructions from, for example, the soft switch.
At event 1319, the phones transmit and receive the voice communications to the gateway such as by using the IP address/port of the gateway. At event 1323, if the gateway determines that the voice communications are to be recorded, the gateway duplicates the voice communications from the phones and transmits the duplicated voice communications such as by using the IP address/port of the voice endpoint recorder. At event 1326, the sequence is returned to event 1319 during which the gateway duplicates the voice communications between the calling and called phones and transmits the duplicated voice communications to the recorder.
It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiments without departing substantially from the spirit and principles of the invention. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present invention and protected by the following claims.
This application is a continuation-in-part of copending U.S. utility application entitled, “Systems and Methods For Endpoint Recording Using Phones,” having Ser. No. 11/394,410, filed Mar. 31, 2006, which is entirely incorporated herein by reference, a continuation-in-part of copending U.S. utility application entitled, “Systems and Methods For Endpoint Recording Using a Conference Bridge,” having Ser. No. 11/395,350, filed Mar. 31, 2006, which is entirely incorporated herein by reference, and a continuation-in-part of copending U.S. utility application entitled, “Systems and Methods For Endpoint Recording Using a Media Application Server,” having Ser. No. 11/395,759 filed Mar. 31, 2006, which is entirely incorporated herein by reference. This application also claims the benefit to U.S. Provisional Application entitled “Systems and Methods for Enterprise Recording Via Software Switch”, filed on Aug. 15, 2006, with 60/837,816, which is entirely incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3594919 | De Bell et al. | Jul 1971 | A |
3705271 | De Bell et al. | Dec 1972 | A |
4510351 | Costello et al. | Apr 1985 | A |
4684349 | Ferguson et al. | Aug 1987 | A |
4694483 | Cheung | Sep 1987 | A |
4763353 | Canale et al. | Aug 1988 | A |
4815120 | Kosich | Mar 1989 | A |
4924488 | Kosich | May 1990 | A |
4953159 | Hayden et al. | Aug 1990 | A |
5016272 | Stubbs et al. | May 1991 | A |
5101402 | Chiu et al. | Mar 1992 | A |
5117225 | Wang | May 1992 | A |
5210789 | Jeffus et al. | May 1993 | A |
5239460 | LaRoche | Aug 1993 | A |
5241625 | Epard et al. | Aug 1993 | A |
5267865 | Lee et al. | Dec 1993 | A |
5299260 | Shaio | Mar 1994 | A |
5311422 | Loftin et al. | May 1994 | A |
5315711 | Barone et al. | May 1994 | A |
5317628 | Misholi et al. | May 1994 | A |
5347306 | Nitta | Sep 1994 | A |
5388252 | Dreste et al. | Feb 1995 | A |
5396371 | Henits et al. | Mar 1995 | A |
5432715 | Shigematsu et al. | Jul 1995 | A |
5465286 | Clare et al. | Nov 1995 | A |
5475625 | Glaschick | Dec 1995 | A |
5485569 | Goldman et al. | Jan 1996 | A |
5491780 | Fyles et al. | Feb 1996 | A |
5499291 | Kepley | Mar 1996 | A |
5535256 | Maloney et al. | Jul 1996 | A |
5572652 | Robusto et al. | Nov 1996 | A |
5577112 | Cambray et al. | Nov 1996 | A |
5590171 | Howe et al. | Dec 1996 | A |
5597312 | Bloom et al. | Jan 1997 | A |
5619183 | Ziegra et al. | Apr 1997 | A |
5696906 | Peters et al. | Dec 1997 | A |
5717879 | Moran et al. | Feb 1998 | A |
5721842 | Beasley et al. | Feb 1998 | A |
5742670 | Bennett | Apr 1998 | A |
5748499 | Trueblood | May 1998 | A |
5778182 | Cathey et al. | Jul 1998 | A |
5784452 | Carney | Jul 1998 | A |
5790798 | Beckett, II et al. | Aug 1998 | A |
5796952 | Davis et al. | Aug 1998 | A |
5809247 | Richardson et al. | Sep 1998 | A |
5809250 | Kisor | Sep 1998 | A |
5825869 | Brooks et al. | Oct 1998 | A |
5835572 | Richardson, Jr. et al. | Nov 1998 | A |
5862330 | Anupam et al. | Jan 1999 | A |
5864772 | Alvarado et al. | Jan 1999 | A |
5884032 | Bateman et al. | Mar 1999 | A |
5907680 | Nielsen | May 1999 | A |
5918214 | Perkowski | Jun 1999 | A |
5923746 | Baker et al. | Jul 1999 | A |
5933811 | Angles et al. | Aug 1999 | A |
5944791 | Scherpbier | Aug 1999 | A |
5948061 | Merriman et al. | Sep 1999 | A |
5958016 | Chang et al. | Sep 1999 | A |
5964836 | Rowe et al. | Oct 1999 | A |
5978648 | George et al. | Nov 1999 | A |
5982857 | Brady | Nov 1999 | A |
5987466 | Greer et al. | Nov 1999 | A |
5990852 | Szamrej | Nov 1999 | A |
5991373 | Pattison et al. | Nov 1999 | A |
5991796 | Anupam et al. | Nov 1999 | A |
6005932 | Bloom | Dec 1999 | A |
6009429 | Greer et al. | Dec 1999 | A |
6014134 | Bell et al. | Jan 2000 | A |
6014647 | Nizzari et al. | Jan 2000 | A |
6018619 | Allard et al. | Jan 2000 | A |
6035332 | Ingrassia et al. | Mar 2000 | A |
6038544 | Machin et al. | Mar 2000 | A |
6039575 | L'Allier et al. | Mar 2000 | A |
6057841 | Thurlow et al. | May 2000 | A |
6058163 | Pattison et al. | May 2000 | A |
6061798 | Coley et al. | May 2000 | A |
6072860 | Kek et al. | Jun 2000 | A |
6076099 | Chen et al. | Jun 2000 | A |
6078894 | Clawson et al. | Jun 2000 | A |
6084581 | Hunt | Jul 2000 | A |
6091712 | Pope et al. | Jul 2000 | A |
6108711 | Beck et al. | Aug 2000 | A |
6122665 | Bar et al. | Sep 2000 | A |
6122668 | Teng et al. | Sep 2000 | A |
6130668 | Stein | Oct 2000 | A |
6138139 | Beck et al. | Oct 2000 | A |
6144991 | England | Nov 2000 | A |
6146148 | Stuppy | Nov 2000 | A |
6151622 | Fraenkel et al. | Nov 2000 | A |
6154771 | Rangan et al. | Nov 2000 | A |
6157808 | Hollingsworth | Dec 2000 | A |
6171109 | Ohsuga | Jan 2001 | B1 |
6182094 | Humpleman et al. | Jan 2001 | B1 |
6195679 | Bauersfeld et al. | Feb 2001 | B1 |
6201948 | Cook et al. | Mar 2001 | B1 |
6211451 | Tohgi et al. | Apr 2001 | B1 |
6225993 | Lindblad et al. | May 2001 | B1 |
6230197 | Beck et al. | May 2001 | B1 |
6236977 | Verba et al. | May 2001 | B1 |
6244758 | Solymar et al. | Jun 2001 | B1 |
6282548 | Burner et al. | Aug 2001 | B1 |
6286030 | Wenig et al. | Sep 2001 | B1 |
6286046 | Bryant | Sep 2001 | B1 |
6288753 | DeNicola et al. | Sep 2001 | B1 |
6289340 | Puram et al. | Sep 2001 | B1 |
6301462 | Freeman et al. | Oct 2001 | B1 |
6301573 | McIlwaine et al. | Oct 2001 | B1 |
6324282 | McIlwaine et al. | Nov 2001 | B1 |
6347374 | Drake et al. | Feb 2002 | B1 |
6351467 | Dillon | Feb 2002 | B1 |
6353851 | Anupam et al. | Mar 2002 | B1 |
6360250 | Anupam et al. | Mar 2002 | B1 |
6370574 | House et al. | Apr 2002 | B1 |
6404857 | Blair et al. | Jun 2002 | B1 |
6411989 | Anupam et al. | Jun 2002 | B1 |
6418471 | Shelton et al. | Jul 2002 | B1 |
6459787 | McIlwaine et al. | Oct 2002 | B2 |
6487195 | Choung et al. | Nov 2002 | B1 |
6493758 | McLain | Dec 2002 | B1 |
6502131 | Vaid et al. | Dec 2002 | B1 |
6510220 | Beckett, II et al. | Jan 2003 | B1 |
6535909 | Rust | Mar 2003 | B1 |
6542602 | Elazar | Apr 2003 | B1 |
6546405 | Gupta et al. | Apr 2003 | B2 |
6560328 | Bondarenko et al. | May 2003 | B1 |
6583806 | Ludwig et al. | Jun 2003 | B2 |
6606657 | Zilberstein et al. | Aug 2003 | B1 |
6665644 | Kanevsky et al. | Dec 2003 | B1 |
6674447 | Chiang et al. | Jan 2004 | B1 |
6683633 | Holtzblatt et al. | Jan 2004 | B2 |
6697858 | Ezerzer et al. | Feb 2004 | B1 |
6724887 | Eilbacher et al. | Apr 2004 | B1 |
6738456 | Wrona et al. | May 2004 | B2 |
6757361 | Blair et al. | Jun 2004 | B2 |
6772396 | Cronin et al. | Aug 2004 | B1 |
6775377 | McIlwaine et al. | Aug 2004 | B2 |
6792575 | Samaniego et al. | Sep 2004 | B1 |
6810414 | Brittain | Oct 2004 | B1 |
6820083 | Nagy et al. | Nov 2004 | B1 |
6823384 | Wilson et al. | Nov 2004 | B1 |
6870916 | Henrikson et al. | Mar 2005 | B2 |
6901438 | Davis et al. | May 2005 | B1 |
6959078 | Eilbacher et al. | Oct 2005 | B1 |
6965886 | Govrin et al. | Nov 2005 | B2 |
7043008 | Dewan | May 2006 | B1 |
7613290 | Williams et al. | Nov 2009 | B2 |
20010000962 | Rajan | May 2001 | A1 |
20010032335 | Jones | Oct 2001 | A1 |
20010043697 | Cox et al. | Nov 2001 | A1 |
20020038363 | MacLean | Mar 2002 | A1 |
20020052948 | Baudu et al. | May 2002 | A1 |
20020064149 | Elliott et al. | May 2002 | A1 |
20020065911 | Von Klopp et al. | May 2002 | A1 |
20020065912 | Catchpole et al. | May 2002 | A1 |
20020128925 | Angeles | Sep 2002 | A1 |
20020143925 | Pricer et al. | Oct 2002 | A1 |
20020165954 | Eshghi et al. | Nov 2002 | A1 |
20030055883 | Wiles et al. | Mar 2003 | A1 |
20030079020 | Gourraud et al. | Apr 2003 | A1 |
20030144900 | Whitmer | Jul 2003 | A1 |
20030154240 | Nygren et al. | Aug 2003 | A1 |
20030190032 | Ravishankar | Oct 2003 | A1 |
20040034672 | Inagaki | Feb 2004 | A1 |
20040100507 | Hayner et al. | May 2004 | A1 |
20040165717 | McIlwaine et al. | Aug 2004 | A1 |
20040247205 | Nagaya et al. | Dec 2004 | A1 |
20050018622 | Halbraich et al. | Jan 2005 | A1 |
20050138560 | Lee et al. | Jun 2005 | A1 |
20060133595 | Ravishankar | Jun 2006 | A1 |
20080082669 | Williams et al. | Apr 2008 | A1 |
20090016522 | Torres et al. | Jan 2009 | A1 |
Number | Date | Country |
---|---|---|
0453128 | Oct 1991 | EP |
0773687 | May 1997 | EP |
0989720 | Mar 2000 | EP |
2369263 | May 2002 | GB |
WO 9843380 | Nov 1998 | WO |
WO 0016207 | Mar 2000 | WO |
WO0217036 | Feb 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20070230446 A1 | Oct 2007 | US |
Number | Date | Country | |
---|---|---|---|
60837816 | Aug 2006 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11394410 | Mar 2006 | US |
Child | 11540902 | US | |
Parent | 11395350 | Mar 2006 | US |
Child | 11394410 | US | |
Parent | 11395759 | Mar 2006 | US |
Child | 11395350 | US |