System and method for automating customer relations in a communications environment

Information

  • Patent Grant
  • 8223954
  • Patent Number
    8,223,954
  • Date Filed
    Tuesday, March 22, 2005
    19 years ago
  • Date Issued
    Tuesday, July 17, 2012
    12 years ago
Abstract
A system and method are disclosed for automating network performance to a customer support department that includes a passive listening device configured to monitor portions of a communication network. A performance database may be coupled to the passive listening device and configured to store network performance data. A customer relations module may be included and configured to receive a subscriber inquiry and to identify at least one monitored component of a communication network that affects the subscriber. The module may retrieve performance data on one or more components of the communication network to provide customer-specific communication performance data to the subscriber and/or the agent assisting the subscriber.
Description
FIELD OF THE DISCLOSURE

The present disclosure relates generally to automating customer support.


BACKGROUND

In today's competitive communications market, service providers strive to improve system performance. Although near perfect reliability and extraordinary speeds are goals of service providers, often unplanned and unexpected phenomena degrade system performance. When a customer feels that performance of their communications system is less than average, they often call a service center to request information, determine if there is an outage, or see if there is work in process to solve their problem. Often customer equipment fails, yet the customer will blame the service provider and inquire whether the service provider is having problems.


Communication service providers seek to efficiently address these concerned subscribers. However, service providers often lack the available resources to identify problems that are specific to subscribers. In fact, a single subscriber may be provided with physical connections and signal processing from many different providers within a network. The vast network of communication systems not only lacks detection equipment but the ability to communicate detected system problems. Accordingly, there is a need for an improved customer service system.





BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that, for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented herein, in which:



FIG. 1 presents a block diagram of a communication system that incorporates teachings of the present disclosure; and



FIG. 2 shows a flow diagram of a method for providing customer service for a communication service provider in accordance with the teachings disclosed herein.





DETAILED DESCRIPTION OF THE DRAWINGS

A system and method are disclosed for automating network performance reporting. In some cases, the reporting may be provided to a customer and/or to a customer support department. Depending upon implementation detail, a system incorporating the present teachings may include a passive listening device configured to monitor portions of a communication network. A performance database may be coupled directly and/or indirectly to the passive listening device and configured to store network performance data.


A customer relations module may be set up to receive a subscriber inquiry and to identify at least one component of a communication network that affects the subscriber. The module may retrieve relevant performance data on identified components of the communication network to provide customer-specific communication performance data to the subscriber and/or an agent assisting the subscriber. In one configuration, the passive listening device can be configured to monitor at least one performance characteristic of a communications network component and to output a plurality of signals representing the performance characteristic. A customer relations management module may be configured to manage customer connection data, to create a list of components used by a given subscriber, and to identify and provide a status of components that have or continue to affect the service provided to the given subscriber.


Referring to FIG. 1 an illustrated system 100 for detecting network performance and providing customer specific performance data to a customer via a customer relationship management module 124 is provided. As depicted, system 100 may help support subscribers and include client interaction interfaces such as e-mail interface 104, telephone interface 106, mobile/wireless interface 102, utilizing antennae 103, and/or Internet interface 108.


System 100 may be implemented by and/or in connection with a communications network-like wide area network (WAN) 110 that facilitates the coupling together of a plurality of service providers such as Internet Service Provider (ISP) 114, power company 116, local Telco provider 118, wireless service provider 112, and messaging service provider 122. System 100 may also include a service bureau offering that assists in near real time tracking of network performance for individual subscribers. As depicted, this service bureau may include a local area network (LAN) 128 interconnecting several components such as customer relationship management module 124, passive listening device interrogator 120, activity database 126, and agent 130.


In an illustrated embodiment, passive listening device interrogator 120 may include a specialized server for locating, addressing, and receiving information from various passive listening devices (PLDs) such as stand-alone PLD 150 located within WAN 110. As depicted, WAN 110 could take several forms including the Public Internet. Depending upon how a designer elects to implement system 100, various components of WAN 110 may have PLDs installed within them. For example, each of the depicted service providers and each of the subscriber interface mechanisms could contain at least one PLD. Stand-alone PLDs may also be installed at pre-defined critical locations. These PLDs may be configured to periodically transmit status information over WAN 110, and/or the PLDs may be responsive to interrogation by PLD interrogator 120.


When a subscriber experiences perceived problems in communicating via WAN 110 and/or some other network, the subscriber may call a customer service department and be placed in contact with customer relationship management module (CRMM) 124. CRMM 124 may be designed to include an auto-response system and a database maintaining customer information such as customer account information. In operation, CRMM 124 may receive a call and based on “call data” received with the call such as CallerID, a CRMM 124 database may be accessed to determine additional information about the subscriber. The additional information can include, for example, subscriber location, the services provided to the subscriber, the communication path servicing the subscriber, and/or a list of PLD monitored components providing service to the subscriber.


Utilizing the customer/subscriber specific information, activity database 126 may be accessed over LAN 128. In some implementations, CRMM 124 may request activity data specific to one or more of the monitored components, which may be components of WAN 110 that supply/support the subject subscriber. Activity database 126 may respond to the request by providing information reflecting the performance of monitored components. The information may be updateable. For example, passive listening device interrogator 120 may send queries to distributed PLDs, receive data from component-based PLDs throughout WAN 110, and write some portion of the received data to activity database 126.


In one instance, PLD interrogator 120 may send periodic queries to PLDs throughout WAN 110. PLD interrogator 120 may also send near-real-time queries to implicated PLDs throughout WAN 110 in response to a particular subscriber inquiry. PLD interrogator 120 can operate on the received data and communicate the network status and/or component status to CRMM 124. Thus, when CRMM 124 requests information specific to a customer/subscriber, activity database 126 may provide historical customer-specific performance data to CRMM 124. In addition, CRMM 124 may also gather additional real-time data. This may not be the only way information is input into activity database 126. For example, outside plant personnel, network status organizations, and/or others may also provide or key-in information to activity database 126.


If CRMM 124 can identify a component in WAN 110 that is under-performing and/or has a significant degradation, the news of this network problem may be sent to the subscriber making the inquiry utilizing an auto-response system. System or component degradation may be hierarchically ordered by CRMM 124 in order of occurrence (date and time), probability of causing a problem, and/or severity. Subject matter in a subscriber query may be linked to an occurrence utilizing a failure analysis, and CRMM 124 may automatically reply to the subscriber request via a communication interface linked to or with WAN 110.


In some cases, the reply to a subscriber may be customer-specific system performance status even when the system is operating within its specified limits. An auto response that provides system performance may be provided to the subscriber based on real-time actual performance, a derived performance characteristic, or a high probability that a component within a communication system has caused unacceptable performance, and/or some other metric or data. In the event that a subscriber inquiry is relatively complicated, the inquiry may be sent from CRMM 124 to agent 130. As such, agent 130 may have access to activity database 126 via LAN 128, and CRMM 124 may automatically provide agent 130 with a list of system performance characteristics that come from distributed PLDs and are subscriber-specific. Although only one agent is illustrated, CRMM 124 may be configured to supply hundreds of agents.


In practice, CRMM 124 may store historic communication responses to subscriber inquiries. As such, in some cases CRMM 124 may determine with a high probability what the problem is for a given subscriber circumstance and provide an inquiring subscriber with a “canned” response. In practice, responses may be assigned confidence levels based on how likely the response is to cover the subscriber inquiry. When the confidence level is low, the inquiry can be routed to agent 130 for manual processing; when the confidence level is high the auto response system can automatically respond.


The system disclosed may utilize many different methods to monitor the communication network 110. A stand-alone PLD 150 or any PLD may use monitoring technologies based on, for example, anomaly detection, heuristics, traffic pattern analysis, application analysis, payload analysis, code violations, as well as passive listening and/or active listening. In some embodiments, an appliance or stand-alone PLD 150 may provide for near-real-time analysis of usage, availability, and performance for applications and services running across public and private networks. For example, stand-alone PLD 150 may measure response times for Internet Protocol applications, network applications, and/or other Web applications. Depending upon implementation detail, stand-alone PLD 150 may be coupled to a port on a data center switch. In some applications, stand-alone PLD 150 may be located behind a corporate firewall, it may track and analyze network activity and usage, and generated information may be stored in a repository or database.


Utilizing stand-alone PLD 150 in combination with activity database 126 may allow agents 130 and technicians to more quickly identify and resolve network problems. In operation, localizing a problem may be accomplished by considering, for example, the interdependencies of a larger network. In effect, such a solution may narrow down the search for customer-specific performance data to a particular component or platform. When a subscriber calls for service, they may be asked questions about their problem. Utilizing an interactive-voice-response system (IVR) the system may be able to learn more about the subscriber's problem and pinpoint a malfunctioning device. Moreover, call-center support personnel may be informed of the problem and made aware of customers who could be impacted by the problem—allowing call center personnel to proactively notify potentially affected customers.


Referring now to FIG. 2 a method of operation that may be used in connection with system 100 of FIG. 1 is illustrated. The method starts at 202 and proceeds to 204 where a subscriber submits an inquiry to a service provider. Data can be gathered regarding the inquiry such as a CallerID telephone number, an e-mail address, and account number, or a MAC address of the subscriber. Additional data may be gathered from prompting the caller and storing caller responses. Additional data can include details about the phenomena surrounding the caller's problem such as slow speed, inoperability, intermittency or whether the problem is reoccurring. This information can be utilized to help diagnose and isolate the cause of the problem.


The subscriber information may be stored at step 206; at decision step 208 it may be determined whether the subscriber can be accurately identified. If the subscriber cannot be accurately identified, then a failure may be recorded at step 212 and additional information may be requested at 210. The method may then proceed back to step 206. If the subscriber can be identified, the monitored components that supply the subscriber with communication services may be identified at step 214. At step 216, the monitored network components that are linked to the subscriber may be queried for past performance and possibly current performance problems. A reply to the subscriber may be created from a library of replies based on component performance at step 218. A confidence level may be assigned to each reply at step 220 based on the likelihood that a reply provides useful information. If the confidence level for a given reply is above a predetermined value, the method may proceed to reply at step 226 where the reply is sent. If the confidence level of the reply is less than a predetermined level, the inquiry may be routed to an agent at step 224 and the process ends at step 228.


The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims
  • 1. A system for providing automated customer support comprising: a customer relations management module configured to: receive a signal from each of a plurality of passive listening devices coupled to a data center switch, each of the passive listening devices configured to monitor a performance characteristic of at least a portion of a communication network and to output the signal in response to the monitored performance characteristic, each of the passive listening devices responsive to interrogation by an interrogation device and configured to receive queries from the interrogation device in response to a subscriber inquiry;identify at least one monitored component of the communication network that provides service to a particular subscriber making the subscriber inquiry;receive historical subscriber-specific performance data related to the particular subscriber and associated with the at least one monitored component from a performance database accessible to the customer relations management module and to each of the passive listening devices;generate a list of responses to the subscriber inquiry based on an analysis of data located in the performance database;assign a confidence level to each particular response in the list of responses based on a likelihood of the particular response addressing the subscriber inquiry;automatically transmit at least one of the responses to the particular subscriber when the confidence level assigned to the at least one response satisfies a threshold level; andautomatically route the subscriber inquiry to an agent station when the confidence level assigned to each of the responses fails to satisfy the threshold level.
  • 2. The system of claim 1, wherein the at least one monitored component has at least one operating parameter and the at least one operating parameter can deviate from an average perfoiniance to a minimal performance, wherein the customer relations management module is further configured to retrieve minimal performance data.
  • 3. The system of claim 2, wherein the customer relations management module is further configured to retrieve the minimal performance data from a plurality of network components.
  • 4. The system of claim 1, wherein at least one of the plurality of passive listening devices is coupled to one of a subscriber computer, a subscriber modem, a service platform, a power monitor, a network traffic monitor, a status-reporting organization, a server monitor, a memory monitor, a router, a switch, a hub, a voice over interne protocol system, a messaging system, a wireless communication cell, a maintenance records department, a code violation monitor, and a quality-of-service monitor.
  • 5. The system of claim 1, wherein data in the performance database is linked to the particular subscriber by one of a geographic location, subscriber connection data, and a list of services provided to the particular subscriber.
  • 6. The system of claim 1, wherein each of the plurality of passive listening devices is coupled to the customer relations management module and wherein the plurality of passive listening devices are distributed throughout multiple communication networks.
  • 7. The system of claim 1, wherein at least one of the plurality of passive listening devices is located behind a firewall.
  • 8. The system of claim 1, wherein at least one of the plurality of passive listening devices is within a network appliance.
  • 9. The system of claim 1, wherein each of the plurality of passive listening devices is configured to monitor the performance characteristic based on at least one of anomaly detection, heuristics, traffic pattern analysis, application analysis, payload analysis, and code violations.
  • 10. The system of claim 1, wherein the interrogation device includes a server configured to locate, address, and receive data from at least one of the plurality of passive listening devices, the interrogation device configured to write a portion of the received data to the performance database.
  • 11. The system of claim 1, wherein at least one of the plurality of passive listening devices is a stand alone device that is not disposed within another network component.
  • 12. A method of providing customer service comprising: receiving a signal from each of a plurality of passive listening devices coupled to a data center switch, each of the passive listening devices configured to monitor a performance characteristic of at least a portion of a communication network and to output the signal in response to the monitored performance characteristic, each of the passive listening devices responsive to interrogation by an interrogation device and configured to receive queries from the interrogation device in response to a subscriber inquiry;identifying at least one monitored component of the communication network that provides service to a particular subscriber making the subscriber inquiry;receiving historical subscriber-specific performance data related to the particular subscriber and associated with the at least one monitored component from a performance database accessible to the data center switch and to the plurality of passive listening devices;generating a list of responses to the subscriber inquiry based on an analysis of data located in the performance database;assigning a confidence level to each particular response in the list of responses based on a likelihood of the particular response addressing the subscriber inquiry;automatically transmitting at least one of the responses to the particular subscriber when the confidence level assigned to the at least one response satisfies a threshold level; andautomatically routing the subscriber inquiry to an agent station when the confidence level assigned to each of the responses fails to satisfy the threshold level.
  • 13. The method of claim 12, further comprising communicating the at least one response in real time.
  • 14. The method of claim 12, further comprising: classifying the subscriber inquiry as a subscriber network performance issue; andidentifying a network component that could cause the subscriber network performance issue.
  • 15. The method of claim 12, wherein stored information indicates that more than one network components provide unacceptable performance.
  • 16. The method of claim 15, further comprising initiating display of a list identifying the more than one network components.
  • 17. The method of claim 12, wherein each of the plurality of passive listening devices is configured to monitor at least one of a subscriber computer, a subscriber modem, a service platform, a power monitor, a network traffic monitor, a status reporting organization, a server monitor, a memory monitor, a router, a switch, a hub, a voice over internet protocol system, a messaging system, a wireless communication cell, a maintenance records department, service records, call records, weather data, a code violation monitor and a quality-of-service monitor.
  • 18. The method of claim 12, further comprising linking the particular subscriber to a network status by one of geographic location, connection data, and subscriber services utilized.
  • 19. The method of claim 12, further comprising receiving an identifier associated with the subscriber inquiry, wherein the identifier comprises caller identification information.
  • 20. The method of claim 12, further comprising receiving the subscriber inquiry via an interactive voice response system.
  • 21. The method of claim 12, further comprising receiving the subscriber inquiry via a website.
  • 22. The method of claim 12, further comprising receiving the subscriber inquiry via a telephony service call.
  • 23. The method of claim 12, further comprising receiving the subscriber inquiry via a voice over internet protocol call.
  • 24. The method of claim 12, wherein each of the plurality of passive listening devices is configured to monitor the performance characteristic based on at least one of anomaly detection, heuristics, traffic pattern analysis, application analysis, payload analysis, and code violations.
  • 25. The method of claim 12, wherein the interrogation device includes a server configured to locate, address, and receive data from at least one of the plurality of passive listening devices, the interrogation device configured to write a portion of the received data to the performance database.
US Referenced Citations (261)
Number Name Date Kind
4953204 Cuschelg, Jr. et al. Aug 1990 A
4967405 Upp et al. Oct 1990 A
4975841 Kehnemuyi et al. Dec 1990 A
5297183 Bareis et al. Mar 1994 A
5299260 Shaio Mar 1994 A
5309513 Rose May 1994 A
5335269 Steinlicht Aug 1994 A
5432845 Burd et al. Jul 1995 A
5455903 Jolissaint et al. Oct 1995 A
5497373 Hulen et al. Mar 1996 A
5522046 McMillen et al. May 1996 A
5530744 Charalambous et al. Jun 1996 A
5555299 Maloney et al. Sep 1996 A
5590186 Liao et al. Dec 1996 A
5621789 McCalmont et al. Apr 1997 A
5652789 Miner Jul 1997 A
5732133 Mark Mar 1998 A
5754639 Flockhart et al. May 1998 A
5754978 Perez-Mendez et al. May 1998 A
5794001 Malone et al. Aug 1998 A
5845062 Branton et al. Dec 1998 A
5867817 Catallo et al. Feb 1999 A
5923745 Hurd Jul 1999 A
5937051 Hurd et al. Aug 1999 A
5940476 Morganstein Aug 1999 A
5946388 Walker et al. Aug 1999 A
5953704 McIlroy et al. Sep 1999 A
5999965 Kelly Dec 1999 A
6002689 Christie et al. Dec 1999 A
6002760 Gisby Dec 1999 A
6003011 Sarin et al. Dec 1999 A
6016336 Hanson Jan 2000 A
6038293 McNerney et al. Mar 2000 A
6049594 Furman et al. Apr 2000 A
6061433 Polcyn et al. May 2000 A
6118866 Shtivelman Sep 2000 A
6119101 Peckover Sep 2000 A
6173266 Marx et al. Jan 2001 B1
6173289 Sonderegger et al. Jan 2001 B1
6173399 Gilbrech Jan 2001 B1
6175621 Begeja Jan 2001 B1
6181776 Crossley et al. Jan 2001 B1
6259786 Gisby Jul 2001 B1
6269153 Carpenter et al. Jul 2001 B1
6317439 Cardona et al. Nov 2001 B1
6320951 Shtivelman et al. Nov 2001 B1
6333980 Hollatz et al. Dec 2001 B1
6353608 Cullers et al. Mar 2002 B1
6366658 Bjornberg et al. Apr 2002 B1
6366668 Borst et al. Apr 2002 B1
6381329 Uppaluru et al. Apr 2002 B1
6385584 McAllister et al. May 2002 B1
6389400 Bushey et al. May 2002 B1
6400804 Bilder Jun 2002 B1
6400996 Hoffberg et al. Jun 2002 B1
6405159 Bushey et al. Jun 2002 B2
6411687 Bohacek et al. Jun 2002 B1
6414966 Kulkarni et al. Jul 2002 B1
6418424 Hoffberg et al. Jul 2002 B1
6442247 Garcia Aug 2002 B1
6496567 Bjornberg et al. Dec 2002 B1
6496836 Ronchi et al. Dec 2002 B1
6510414 Chaves Jan 2003 B1
6519562 Phillips et al. Feb 2003 B1
6529871 Kanevsky et al. Mar 2003 B1
6553112 Ishikawa Apr 2003 B2
6553113 Dhir et al. Apr 2003 B1
6570967 Katz May 2003 B2
6574599 Lim et al. Jun 2003 B1
6577718 Kalmanek et al. Jun 2003 B1
6584180 Nemoto Jun 2003 B2
6584191 McPartlan et al. Jun 2003 B1
6587556 Judkins et al. Jul 2003 B1
6587558 Lo Jul 2003 B2
6594470 Barnes et al. Jul 2003 B1
6598136 Norrod et al. Jul 2003 B1
6600736 Ball et al. Jul 2003 B1
6603854 Judkins et al. Aug 2003 B1
6614781 Elliott et al. Sep 2003 B1
6631186 Adams et al. Oct 2003 B1
6678360 Katz Jan 2004 B1
6678718 Khouri et al. Jan 2004 B1
6690788 Bauer et al. Feb 2004 B1
6694012 Posthuma Feb 2004 B1
6697458 Kunjibettu Feb 2004 B1
6697460 Knott et al. Feb 2004 B2
6697806 Cook Feb 2004 B1
6700972 McHugh et al. Mar 2004 B1
6704404 Burnett Mar 2004 B1
6707789 Arslan et al. Mar 2004 B1
6714631 Martin et al. Mar 2004 B1
6721416 Farrell Apr 2004 B1
6731722 Coffey May 2004 B2
6738473 Burg et al. May 2004 B1
6744861 Pershan et al. Jun 2004 B1
6744877 Edwards Jun 2004 B1
6751306 Himmel et al. Jun 2004 B2
6751591 Gorin et al. Jun 2004 B1
6757306 Klish, II et al. Jun 2004 B1
6766320 Wang et al. Jul 2004 B1
6775359 Ron et al. Aug 2004 B1
6778643 Bushey et al. Aug 2004 B1
6792096 Martin et al. Sep 2004 B2
6807274 Joseph et al. Oct 2004 B2
6823307 Steinbiss et al. Nov 2004 B1
6831932 Boyle et al. Dec 2004 B1
6832224 Gilmour Dec 2004 B2
6842504 Mills et al. Jan 2005 B2
6847711 Knott et al. Jan 2005 B2
6847715 Swartz Jan 2005 B1
6853722 Joseph et al. Feb 2005 B2
6853966 Bushey et al. Feb 2005 B2
6859529 Duncan et al. Feb 2005 B2
6871212 Khouri et al. Mar 2005 B2
6879683 Fain et al. Apr 2005 B1
6885734 Eberle et al. Apr 2005 B1
6891932 Bhargava et al. May 2005 B2
6895083 Bers et al. May 2005 B1
6895532 Raynham May 2005 B2
6901366 Kuhn et al. May 2005 B1
6907119 Case et al. Jun 2005 B2
6915246 Gusler et al. Jul 2005 B2
6963983 Munson et al. Nov 2005 B2
7006605 Morganstein Feb 2006 B1
7031444 Shen et al. Apr 2006 B2
7035388 Kurosaki Apr 2006 B2
7050936 Levy et al. May 2006 B2
7065201 Bushey et al. Jun 2006 B2
7124059 Wetzer et al. Oct 2006 B2
7206400 Dezonno et al. Apr 2007 B2
7231384 Wu et al. Jun 2007 B2
7242751 Bushey et al. Jul 2007 B2
7245716 Brown et al. Jul 2007 B2
7346152 Paden et al. Mar 2008 B2
7379886 Zaring et al. May 2008 B1
7430554 Heisinger Sep 2008 B1
7506241 Chefalas et al. Mar 2009 B2
7512545 Knott et al. Mar 2009 B2
7660233 Paden et al. Feb 2010 B2
20010011211 Bushey et al. Aug 2001 A1
20010018672 Petters et al. Aug 2001 A1
20010021948 Khouri et al. Sep 2001 A1
20010032075 Yamamoto Oct 2001 A1
20010032229 Hulls et al. Oct 2001 A1
20010034662 Morris Oct 2001 A1
20020046030 Harista Apr 2002 A1
20020055975 Petrovykh May 2002 A1
20020057678 Jiang et al. May 2002 A1
20020059164 Shtivelman May 2002 A1
20020059169 Quaterman et al. May 2002 A1
20020067714 Crain et al. Jun 2002 A1
20020087316 Lee et al. Jul 2002 A1
20020087385 Vincent Jul 2002 A1
20020087558 Bailey et al. Jul 2002 A1
20020114432 Shaffer et al. Aug 2002 A1
20020122544 Williams et al. Sep 2002 A1
20020133394 Bushey et al. Sep 2002 A1
20020133413 Chang et al. Sep 2002 A1
20020135618 Maes Sep 2002 A1
20020156699 Gray et al. Oct 2002 A1
20020165732 Ezzeddine et al. Nov 2002 A1
20020169606 Bantz et al. Nov 2002 A1
20020196277 Bushey et al. Dec 2002 A1
20030026409 Bushey et al. Feb 2003 A1
20030035381 Chen et al. Feb 2003 A1
20030035516 Guedalia Feb 2003 A1
20030069937 Khouri et al. Apr 2003 A1
20030097428 Afkhami et al. May 2003 A1
20030103619 Brown et al. Jun 2003 A1
20030114105 Haller et al. Jun 2003 A1
20030118159 Shen et al. Jun 2003 A1
20030130841 Bangalore et al. Jul 2003 A1
20030130864 Ho et al. Jul 2003 A1
20030143981 Kortum et al. Jul 2003 A1
20030144846 Denenberg et al. Jul 2003 A1
20030144919 Trompette et al. Jul 2003 A1
20030154184 Chee et al. Aug 2003 A1
20030156133 Martin et al. Aug 2003 A1
20030165223 Timmins et al. Sep 2003 A1
20030179876 Fox et al. Sep 2003 A1
20030187732 Seta Oct 2003 A1
20030187773 Santos et al. Oct 2003 A1
20030194063 Martin et al. Oct 2003 A1
20030195753 Homuth Oct 2003 A1
20030202640 Knott et al. Oct 2003 A1
20030202643 Joseph et al. Oct 2003 A1
20030202649 Haug, Jr. et al. Oct 2003 A1
20030204435 McQuilkin et al. Oct 2003 A1
20030228007 Kurosaki Dec 2003 A1
20030235287 Margolis et al. Dec 2003 A1
20040005047 Joseph et al. Jan 2004 A1
20040006473 Mills et al. Jan 2004 A1
20040030649 Nelson et al. Feb 2004 A1
20040032862 Schoeneberger et al. Feb 2004 A1
20040032935 Mills et al. Feb 2004 A1
20040042592 Knott et al. Mar 2004 A1
20040044950 Mills et al. Mar 2004 A1
20040066401 Bushey et al. Apr 2004 A1
20040066416 Knott et al. Apr 2004 A1
20040073569 Knott et al. Apr 2004 A1
20040083479 Bondarenko et al. Apr 2004 A1
20040088285 Martin et al. May 2004 A1
20040103017 Reed et al. May 2004 A1
20040109555 Williams Jun 2004 A1
20040120473 Birch et al. Jun 2004 A1
20040125937 Turcan et al. Jul 2004 A1
20040125938 Turcan et al. Jul 2004 A1
20040125940 Turcan et al. Jul 2004 A1
20040161078 Knott et al. Aug 2004 A1
20040161094 Martin et al. Aug 2004 A1
20040161096 Knott et al. Aug 2004 A1
20040174980 Knott et al. Sep 2004 A1
20040230438 Pasquale et al. Nov 2004 A1
20040240635 Bushey et al. Dec 2004 A1
20040243568 Wang et al. Dec 2004 A1
20050008141 Kortum et al. Jan 2005 A1
20050015744 Bushey et al. Jan 2005 A1
20050018825 Ho Jan 2005 A1
20050027535 Martin et al. Feb 2005 A1
20050041796 Joseph et al. Feb 2005 A1
20050047578 Knott et al. Mar 2005 A1
20050055216 Bushey et al. Mar 2005 A1
20050058264 Joseph et al. Mar 2005 A1
20050060200 Kobylevsky et al. Mar 2005 A1
20050075894 Bushey et al. Apr 2005 A1
20050078805 Mills et al. Apr 2005 A1
20050080630 Mills et al. Apr 2005 A1
20050080667 Knott et al. Apr 2005 A1
20050131892 Knott et al. Jun 2005 A1
20050132262 Bushey et al. Jun 2005 A1
20050135595 Bushey et al. Jun 2005 A1
20050141692 Scherer et al. Jun 2005 A1
20050147218 Novack et al. Jul 2005 A1
20050152530 Pence Jul 2005 A1
20050169441 Yacoub Aug 2005 A1
20050169453 Knott et al. Aug 2005 A1
20050195961 Pasquale et al. Sep 2005 A1
20050201547 Burg et al. Sep 2005 A1
20050240411 Yacoub Oct 2005 A1
20050254632 Pasquale et al. Nov 2005 A1
20050278655 Sims Dec 2005 A1
20060002540 Kreiner et al. Jan 2006 A1
20060023863 Joseph Feb 2006 A1
20060039547 Klein Feb 2006 A1
20060056287 Paden et al. Mar 2006 A1
20060072737 Paden et al. Apr 2006 A1
20060085538 Newman et al. Apr 2006 A1
20060109974 Paden et al. May 2006 A1
20060109976 Sundaram et al. May 2006 A1
20060115070 Bushey et al. Jun 2006 A1
20060146806 Khuc et al. Jul 2006 A1
20060165057 Paden et al. Jul 2006 A1
20060177040 Mitra Aug 2006 A1
20060256956 Lee et al. Nov 2006 A1
20060291642 Bushey et al. Dec 2006 A1
20060291644 Ellinwood Dec 2006 A1
20070025542 Bushey et al. Feb 2007 A1
20070041551 Whitecotten et al. Feb 2007 A1
20070047720 Brandt et al. Mar 2007 A1
20070116230 Brandt et al. May 2007 A1
20070206772 Sato et al. Sep 2007 A1
Foreign Referenced Citations (15)
Number Date Country
0 424 015 Apr 1991 EP
0 424 015 Apr 1991 EP
0 424 015 Apr 1991 EP
0 876 652 Sep 1996 EP
0 876 652 Nov 1998 EP
9726612 Jul 1997 WO
WO 9726612 Jul 1997 WO
0137539 May 2001 WO
0137539 May 2001 WO
WO 0137539 May 2001 WO
WO 0137539 May 2001 WO
WO 2004017584 Feb 2004 WO
2004017584 Apr 2004 WO
WO 2004049222 Jun 2004 WO
2004049222 Oct 2004 WO
Related Publications (1)
Number Date Country
20060215833 A1 Sep 2006 US