The present invention relates generally to communications systems and, more particularly, to methods and systems for remote establishment of calls.
Telephone systems have become an important aspect of modern day life. Presently various mechanisms exist for customers to make calls when away from their home telephone such that these calls are billed to either their account, the called party, or to a third party.
For example, if the user is away from their home phone and has a calling card, the user may use a payphone to place the call and have it billed to their calling card. For example, the user may place a call to a specific number associated with the calling card that is then transferred to a calling card center. In certain cases, a calling card company may have multiple such centers throughout the United States, in which case the call is typically transferred to a regional calling card center in the same region as the calling party. Alternatively, the call may be transferred to a computer connected to the switch that provides calling card type services. The calling card center or switch then prompts the user to enter the number they are calling and then their calling card number. Typically, the calling number is the user's home phone number plus a four-digit personal identification number (PIN). The call is then forwarded from the calling card center to the number they entered and the caller is appropriately billed.
In another example, a user may purchase a prepaid calling card. Use of this card is essentially the same as described above, with the exception that rather than billing the user after the call, the costs of the call are deducted from the prepaid amount of the calling card until the amount remaining on the card becomes zero. Although billing procedures are simplified, this system requires a separate retail transaction prior to placing the call.
In another example, a user away from their home can make a collect call such that the call is billed to the called party. For example, the user can dial a specific number for obtaining collect call services. This call is then transferred to an appropriate data center or computer device that prompts the user to enter the number they are calling. A call is then placed to the number they are calling. If answered, the answering party is asked whether they will accept charges for the call. If so, the center connects the calling and called parties and the called party is later billed for the call. This system, however, requires action by the called party before the call can proceed.
In yet another example, the user may place a call to an operator. The user is then connected to the operator, and the user provides the operator with the number they are calling plus information regarding whom to bill (e.g., the called party, the user's account, or a third party). The operator then verifies the billing information (e.g. verifies that the party to be billed will accept the charges). The operator then connects the calling and called party. This, however, imposes personnel costs associated with employing live operators.
Accordingly, it would be desirable for improved methods and systems for remote establishment of calls.
In accordance with the purposes of the invention, as embodied and broadly described herein, methods and systems are provided for establishing of a call from a first device to a second device. In one embodiment, the methods and systems include receiving a call placed by a user from the first device, receiving from the first device information regarding the second device to which the call is to be placed, receiving from the first device information regarding a third device, wherein the third device is associated with the user, transferring the call to a first switch associated with the third device, transferring the call from the first switch to a second switch using the information received from the first device, the second switch associated with the second device, and transferring the call from the second switch to the second device.
In another aspect, the invention comprises methods and systems for a system for establishment of a call from a first device to a second device via a communication network, including a first switch for receiving a call placed by a user from a first device, a set of one or more processors for receiving from the first device information regarding a second device to which the call is to be placed and receiving from the first device information regarding a third device, wherein the third device is associated with the user, a second switch associated with the second device for receiving the call and transferring the call to the second device, and a third switch for receiving the call from the first switch and transferring the call to the second switch using the information received from the first device.
Additional objects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one (several) embodiment(s) of the invention and together with the description, serve to explain the principles of the invention.
Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
The following will provide a description of methods and systems consistent with the invention of an embodiment for enabling a user to place a call from any telephone, and have the call billed to the user's primary telephone number (e.g., their home phone). In such an embodiment, the call may be routed to the service switching point (SSP) servicing the user's home phone (phone to be billed). The SSP may then forward the call to the called number.
Voice network 100 may be implemented using PSTN and SS7 as a signaling protocol. SS7 protocol allows voice network 100 to provide features, such as call forwarding, caller-ID, three-way calling, wireless services such as roaming and mobile subscriber authentication, local number portability, and toll-free/toll services. The SS7 protocol provides various types of messages to support the features of voice network 100. For example, these SS7 messages may include Transaction Capabilities Applications Part (“TCAP”) messages to support event “triggers,” and queries and responses between ISCP 102 and SSPs 108 and 110.
ISCP 302 may also be, for example, a standard service control point (SCP), an Advanced Intelligent Network (AIN) SCP, a soft switch, or any other network call controller. As used herein, the term service control point (SCP) is a generic term that covers standard SCPs, ISCPs and AIN SCPs. ISCP 102 provides translation and routing services of SS7 messages to support the features of voice network 100, such as call forwarding. In addition, ISCP 102 may exchange information with the service center 106 using TCP/IP or SS7. ISCP 102 may be implemented using a combination of known hardware and software. ISCP 102 is shown with both a direct connection to service center 106 and a connection through ISCP SPACE 114, however, any number of network elements including routers, switches, hubs, etc., may be used to connect ISCP 102, ISCP SPACE 114, and service center 106. Further, information exchanged between the ISCP 102 and service center 106 may use, for example, the SR-3389 General Data Interface (GDI) for TCP/IP.
STPs 104 and 106 relay SS7 messages within voice network 100. For example, STP 104 may route SS7 messages between SSPs 108 and 110. STP 102 may be implemented using known hardware and software from manufacturers such as NORTEL™ and LUCENT Technologies™.
SSPs 108 and 110 provide an interface between voice network 100 and phones 114 and 120, respectively, to setup, manage, and release telephone calls within voice network 100. SSPs 108 and 110 may be implemented as a voice switch, an SS7 switch, or a computer connected to a switch. SSPs are also often referred to as Central Office (CO) switches, and the terms are used herein interchangeably. SSPs 108 and 110 exchange SS7 signal units to support a telephone call between calling party 120 and user 110. For example, SSPs 108 and 110 may exchange SS7 messages, such as TCAP messages, within message signal units (“MSU”) to control calls, perform database queries to configuration database 112, and provide maintenance information.
Further illustrated is an Intelligent Peripheral (IP) 216 connected, via SSP 208, to SSP 214. IP 216 may be, for example, any type of commercially available IP, such as those available from Cognitronics and IBM. Also illustrated is a voice portal 218 that may include a voice recognition function that can receive and interpret dictation or recognize spoken commands. Voice portal 218 may interface with a data center in a voice data network 220, which may be used for billing purposes.
A user may initiate a call from remote phone 202 by first placing a call to a voice portal number (S302). As used herein the term “place a call” means the user initiating a communications session between the user's device and one or more other devices. This number may be, for example, a specific number advertised for providing this service, and may be, for example, a 1-800 type number.
Network 204-A (
The call is then received at SSP 208 which recognizes the dialed number as one for remote call establishment. SSP 208 then provides signaling information to IP 216 using a protocol, such as, for example, Primary Rate Interface (PRI) signaling (S306).
IP 216 may also, in response to the dialed number, invoke an appropriate software application. This application may, for example, assign a 10-digit session_id for this call and log Calling Party information received in a setup message as part of PRI protocal. This Calling Party information may include the Called Party's Number (CPN), Nature of Number, and Presentation Restriction Indicator. In this example, the CPN is the number dialed out by the user to obtain this service (i.e., the 1-800 number), the Nature of Number is an indication of whether the dialed number is a domestic or international number and the Presentation Restriction Indicator is an indication of whether the number from which the call was placed is unlisted or specifies that caller-ID information is not to be displayed.
The session_id may be used for identification/tracking purposes and include a unique IP id number for identifying IP 216, and a session number for identifying the session between IP 216 and voice portal 218. For example, in an embodiment, the session_id may be a ten digit number that includes a six digit IP id number (NPA-XXX) and a four digit session number (YYYY) for identifying the session within IP 216. Additionally, in this embodiment, each IP may have up to 1,000 simultaneous sessions active with Voice Portal 218.
The application of IP 216 may then send a setup message to the Voice Portal 218. (S308). This setup message may be sent, for example, over a TCP/IP connection. This message may contain, for example, the 10-digit session_id number.
The application of IP 216 may also extend the voice path of the call to the Voice Portal 218. (S310). That is, the IP 216 may direct the SSP 208 to transfer the call back through the network 204-B to the Voice Portal 218. The application of IP 216 may populate the CPN for this call with the session_id sent to it in the TCP/IP Setup Message.
Next, the call arrives at the Voice Portal 218. Voice Portal 218, a software application then matches the CPN to a pending session_id. This indicates that special handling is required for this call. (S312).
The Voice Portal 218 then may play a voice recording indicating to the user that the call has been received and prompting the user to enter the number they wish to call. (S314). Additionally, the user may be prompted to enter a primary number (i.e., the number associated with their home phone 210) along with a Personal Identification Number (PIN). The user may provide the requested information by, for example, speech or by entering it using a keypad on their phone. The Voice Portal 218 may then send the user's primary number and PIN to the voice network's data center 220 to verify that the user is authorized to bill the call to the primary number. If the PIN entered by the user is not recognized, the Voice Portal 218 may ask that the user reenter this information, or play a message that they should try again later.
After the user provides the number they wish to call, the Voice Portal 218 may send a TCP/IP Release Message instructing the IP 216 to drop the call to the Voice Portal 218 and forward the call to the user's primary number (e.g., the number associated with the user's home phone 210). (S318). This Release Message may contain, for example, a Forward-To Number (the 10-digit Number the user wishes to call), the user's Primary Number (the 10-digit Number associated with the user's home phone 210), and the session_id. The IP 216 may then use the session_id in the Release Message to map the release message to appropriate voice channels. (S318).
In one example, the IP 216 may send a PRI setup message to the SSP 208 to cause the call to the Voice Portal 218 to be dropped and a new call established to the SSP 214 associated with user's Primary Number (i.e., home phone 210). This PRI setup message may contain the following: a unique CPN, which may be used by the service logic of the ISCP 206 to invoke the Voice Portal's 218 service logic; a Redirection Parameter containing the Forward To Number; an Originating Calling Number (OCN) (i.e., the remote phone number received on the original call from the user), and the user's Primary Number.
Next, the call is routed to the SSP 214 that serves the user's Primary Number. (S320) This may be accomplished by, for example, the IP's 216 application instructing the SSP 208 to perform a Two B Channel Transfer (TBCT).
A Termination Attempt Trigger (TAT trigger) on the user's Primary Number may then be used to cause the SSP 214 to issue a query to the ISCP 206. (S322). This query may include the Transaction Capability Application Part (TCAP) CPN value received in the received call, and may, for example, cause the ISCP 206 to invoke its service logic. As discussed above, this CPN value may be a unique CPN used by the service logic of ISCP 206 to invoke the Voice Portal's 218 service logic. The service logic employed by the ISCP 206 may be, for example, AIN service logic.
Based on the input Transaction Capability Application Part (TCAP) CPN value, the service logic of ISCP 206 determines that this is a Voice Portal 218 call. The service logic then retrieves the input TCAP OCN and the Redirection Parameters from the received call. The ISCP 206 may then retrieve the Forward to Number from the Redirection Parameters and send the OCN and Forward to Number to SSP 214 by populating this information via output TCAP calling party and called party parameters, respectively. (S324)
Based on the receipt of this information, the SSP 214 then forwards the call to the number the user wishes to call (i.e. the Forward to Number). (S326)
Next, the call is routed over the network 204 to the Forward to Number using the line class of service assigned to the user's Primary Number. The SSP associated with the Forward to Number determines if the associated phone 212 is available. If so, the phone 212 associated with this number begins ringing. If the call is answered, the call is completed, and the user primary number is appropriately billed. (S328)
In another example, voice portal 218 may be connected to various other servers for performing other services as described below with respect to
If the contact has multiple numbers in the address book (e.g., a work and a home number) the user may be provided with this information and permitted to select the desired number via speech or key entries on remote phone 202. The user may also search the address book to select a desired contact, modify the information for a contact or add a new contact using spoken commands or key entries on remote phone 202.
As illustrated, one or more user terminals, such as 212_A and 212_B, are connected to service center 402. This connection may be a direct connection or via a network such as, for example, the Internet. The user terminals 212 may be any appropriate type of device a user may use for communicating with a Service Center 106. For example, the user terminal 212_A may be a PDA running a program for communicating with the Service Center 106, while user terminal 212_B may be a desktop type computer running a web browser for communicating with the Service Center 106 via the Internet. Additionally, the user may call the voice portal 218 using a phone such as remote phone 202.
As illustrated, service center 106 may include one or more digital companion server(s) 406, one or more communication portal server(s) 408, and the voice portal 218. Servers 406, 408 and voice portal 218 may communicate between one another using, for example, web services or any other suitable protocols. Web services are a standardized way of integrating Web-based applications using the Extensible Markup Language (XML), Simple Object Access Protocol (SOAP), Web Services Description Language (WSDL) and Universal Description, Discovery and Integration (UDDI) open standards over an Internet protocol (IP) backbone.
As illustrated, digital companion server(s) 406 may provide the following functions: a client proxy 512, a web server 514, an application server function 516, and a database function 522. Each of these functions may be performed in hardware, software, and/or firmware. Further, these functions may each be executed by a separate server, split across multiple servers, included on the same server functions, or any other manner.
The client proxy function 512 provides a proxy function for the digital companion that may be used for security purposes. This client proxy function 512 may be included in a separate server such that all communications sent from the other digital companion functions/servers to a user terminal 212 go through the client proxy 512. Also, if the client proxy 512 is included on a separate server, for example, an additional firewall may be provided between the client proxy 512 and the other digital companion servers to provide additional security.
Web server 514 provides functionality for receiving traffic over the data network 102 from a customer. For example, web server 514 may be a standard web server that a customer may access using a web browser program, such as Internet Explorer or Netscape Communicator.
Application server function 516 encompasses the general functions performed by the digital companion server(s) 406. For example, these functions may include interfacing with the various other digital companion functions to perform specific applications provided by the service center. These services may include, for example, interfacing with other function(s), software, and/or hardware to provide a customer with the capability of managing their calls online. For example, permitting a customer to add contacts to their address book from a history of calls made or received by the customer, and permitting a customer to modify, add or delete contacts in their address book, e.g., for example, using user terminals 212_A or 212_B.
Additionally, the application server function 516 may interface with one or more external devices, such as an external web server, for retrieving or sending information. For example, the application server function 516 may interface with a voice network's data center 220 (e.g., verizon.com) to determine the services to which the customer subscribes (e.g., call waiting, call forwarding, voice mail, etc.).
Database function 522 provides the storage of information useable by the various applications executed by the digital companion server(s) 406. These databases may be included in, for example, one or more external storage devices connected to the digital companion server(s) 406. Alternatively, the databases may be included in storage devices within the digital companion server(s) 406 themselves. The storage devices providing the database function 522 may be any type of storage device, such as for example, CD-ROMs, DVD's, disk drives, magnetic tape, etc.
The communication portal server(s) 408 may provide the hardware and software for managing a customer's account and interfacing with customer account information stored by the provider of the customer's voice network. As illustrated in
Web server function 526, as with web server function 522 of the digital companion servers, provides functionality for receiving traffic over a network from a customer. For example, the web server may be a standard web server that a customer may access using a web browser, such as Internet Explorer or Netscape Communicator.
The application server function 528 encompasses the general functions performed by the communication portal servers 406. For example, these functions may include interfacing with the voice network to retrieve and/or modify customer profile information, and creating and editing the address book for the user. Additionally, the application server function 528 may include the functionality of sending and/or receiving information to/from external servers and/or devices. For example, the communication portal servers 408 may be connected to a network, such as, the Internet. The application server function 528 may then provide connectivity over the Internet to external servers 552 that provide web services, such as the Superpages webpage. The application function 528 may then contact these external services 552 to retrieve information, such as an address and or number for a person in the user's address book.
In another example, the application server function 528 of the communication portal 408 may interface a single sign on (SSO) server 554. SSO 554 may be used to allow users to access all services to which the user subscribes, on the basis of a single authentication that is performed when they initially access the network.
The contacts database 530 includes storage devices for storing an address book for the user. This address book may be any type of address book. For example, the user's address book may include the names, phone numbers, and addresses of people and/or organizations. These storage devices may be internal or external to the communication portal servers 406 or some combination in between. In addition, these storage devices may be any type of storage device, such as magnetic storage, memory storage, etc.
The customer profile database 532 includes storage devices for storing customer profile information for the user. These storage devices may be the same or separate storage devices used for the contacts database. The customer profile may include information regarding the user's account for their voice network. For example, this information may include the user's name, billing address, and other account information. Additionally, the customer profile may include information regarding voice services to which the user subscribes, such as, for example, call waiting, voice mail, etc.
For example, the voice portal 218 may inquire by synthesized or reworded voice prompt whether the user wishes to access their address book or whether the user wishes to simply enter a number. The user may then select to access their address book by speaking an appropriate command or by entering a particular digit(s) on the keypad of the phone 202. If the user elects to access their address book, the voice portal 218 may, for example, ask for the user to spell the name of the user. The voice portal 218 may then contact the digital companion server(s) 406 to look up this name in the user's address book and retrieve the contact's number. The call may then be forwarded to this number by, for example, the methods discussed above, e.g., steps S316-S328.
Additionally, if the user is unsure of the contacts name, the user may be presented with an option by the voice portal 218 to just speak the first few letters of the contacts name. The voice portal 218 may then retrieve all contacts from the user's address book including these first few letters. The user may then select from these retrieved names the desired contact by speaking an appropriate command or entering a digit on the keypad of their phone. The voice portal 218 may then retrieve the phone number for this contact from the address book and the call may be forwarded as discussed above.
Additionally, if the selected contact has multiple numbers (e.g., home, work, and cell), the voice portal 218 may inform the user of these multiple numbers and ask for the user to select the desired number.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Applicants claim the right to priority under 35 U.S.C. § 119(e) based on Provisional Patent Application No. 60/428,704, entitled “DIGITAL COMPANION,” filed Nov. 25, 2002; and Provisional Patent Application No. 60/436,018, entitled “DIGITAL COMPANION,” filed Dec. 26, 2002, both of which are expressly incorporated herein by reference in their entirety. The present application also relates to U.S. patent application Ser. No. 10/083,792, entitled “VOICE MAIL INTEGRATION WITH INSTANT MESSENGER,” filed Feb. 27, 2002; U.S. patent application Ser. No. 10/083,884, entitled “DEVICE INDEPENDENT CALLER ID,” filed Feb. 27, 2002; and U.S. patent application Ser. No. 10/083,822, entitled “METHOD AND APPARATUS FOR A UNIFIED COMMUNICATION MANAGEMENT VIA INSTANT MESSAGING,” filed Feb. 27, 2002; U.S. patent application Ser. No. 10/083,793, entitled “METHOD AND APPARATUS FOR CALENDARED COMMUNICATIONS FLOW CONTROL,” filed Feb. 27, 2002; U.S. patent application Ser. No. 10/084,121, entitled “CALENDAR-BASED CALLING AGENTS,” filed Feb. 27, 2002; U.S. patent application Ser. No. 10/720,661, entitled “METHODS AND SYSTEMS FOR DRAG AND DROP CONFERENCE CALLING,” U.S. patent application Ser. No. 10/720,859, entitled “METHODS AND SYSTEMS FOR CONFERENCE CALL BUFFERING,” U.S. patent application Ser. No. 10/721,009, entitled “METHODS AND SYSTEMS FOR COMPUTER ENHANCED CONFERENCE CALLING,” U.S. patent application Ser. No. 10/721,005, entitled “METHODS AND SYSTEMS FOR CALL MANAGEMENT WITH USER INTERVENTION,” U.S. patent application Ser. No. 10/720,868, entitled “METHODS AND SYSTEMS FOR DIRECTORY INFORMATION LOOKUP,” U.S. patent application Ser. No. 10/720,970, entitled “METHODS AND SYSTEMS FOR AUTOMATIC COMMUNICATION LINE MANAGEMENT BASED ON DEVICE LOCATION,” U.S. patent application Ser. No. 10/720,952, entitled “METHODS AND SYSTEMS FOR ADAPTIVE MESSAGE AND CALL NOTIFICATION,” U.S. patent application Ser. No. 10/720,870, entitled “METHODS AND SYSTEMS FOR A CALL LOG,” U.S. patent application Ser. No. 10/720,633, entitled “METHODS AND SYSTEMS FOR AUTOMATIC FORWARDING OF CALLS TO A PREFERRED DEVICE,” U.S. patent application Ser. No. 10/720,971, entitled “METHODS AND SYSTEMS FOR LINE MANAGEMENT,” U.S. patent application Ser. No. 10/720,784, entitled “METHODS AND SYSTEMS FOR CONTACT MANAGEMENT,” U.S. patent application Ser. No. 10/720,920, entitled “METHODS AND SYSTEMS FOR NOTIFICATION OF CALL TO PHONE DEVICE,” U.S. patent application Ser. No. 10/720,825, entitled “METHODS AND SYSTEMS FOR SINGLE NUMBER TEXT MESSAGING,” U.S. patent application Ser. No. 10/720,944, entitled “METHODS AND SYSTEMS FOR MULTI-USER SELECTIVE NOTIFICATION,” U.S. patent application Ser. No. 10/720,933, entitled “METHODS AND SYSTEMS FOR CPN TRIGGERED COLLABORATION,” and U.S. patent application Ser. No. 10/720,938, entitled “METHODS AND SYSTEMS FOR PREEMPTIVE REJECTION OF CALLS,” all of which are expressly incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4013839 | Bell | Mar 1977 | A |
4540850 | Herr et al. | Sep 1985 | A |
4600814 | Cunniff et al. | Jul 1986 | A |
4734931 | Bourg et al. | Mar 1988 | A |
4924496 | Figa et al. | May 1990 | A |
5014303 | Velius | May 1991 | A |
5168515 | Gechter et al. | Dec 1992 | A |
5222125 | Creswell et al. | Jun 1993 | A |
5274700 | Gechter et al. | Dec 1993 | A |
5327486 | Wolff et al. | Jul 1994 | A |
5329578 | Brennan et al. | Jul 1994 | A |
5428663 | Grimes et al. | Jun 1995 | A |
5440624 | Schoof | Aug 1995 | A |
5483586 | Sussman | Jan 1996 | A |
5533096 | Bales | Jul 1996 | A |
5535265 | Suwandhaputra | Jul 1996 | A |
5550907 | Carlsen | Aug 1996 | A |
5583564 | Rao et al. | Dec 1996 | A |
5586173 | Misholi et al. | Dec 1996 | A |
5588037 | Fuller et al. | Dec 1996 | A |
5608788 | Demlow et al. | Mar 1997 | A |
5619555 | Fenton et al. | Apr 1997 | A |
5621787 | McKoy et al. | Apr 1997 | A |
5623541 | Boyle et al. | Apr 1997 | A |
5631904 | Fitser et al. | May 1997 | A |
5638434 | Gottlieb et al. | Jun 1997 | A |
5652789 | Miner et al. | Jul 1997 | A |
5661788 | Chin | Aug 1997 | A |
5668863 | Bieselin et al. | Sep 1997 | A |
5673080 | Biggs et al. | Sep 1997 | A |
5692213 | Goldberg et al. | Nov 1997 | A |
5710591 | Bruno et al. | Jan 1998 | A |
5715444 | Danish et al. | Feb 1998 | A |
5717863 | Adamson et al. | Feb 1998 | A |
5719925 | Peoples | Feb 1998 | A |
5724412 | Srinivasan | Mar 1998 | A |
5742095 | Bryant et al. | Apr 1998 | A |
5742668 | Pepe et al. | Apr 1998 | A |
5742905 | Pepe et al. | Apr 1998 | A |
5745561 | Baker et al. | Apr 1998 | A |
5751800 | Ardon | May 1998 | A |
5752191 | Fuller et al. | May 1998 | A |
5764901 | Skarbo et al. | Jun 1998 | A |
5805670 | Pons et al. | Sep 1998 | A |
5841837 | Fuller et al. | Nov 1998 | A |
5864603 | Haavisto et al. | Jan 1999 | A |
5872841 | King et al. | Feb 1999 | A |
5875242 | Glaser et al. | Feb 1999 | A |
5875437 | Atkins | Feb 1999 | A |
5903845 | Buhrmann et al. | May 1999 | A |
5907324 | Larson et al. | May 1999 | A |
5907547 | Foladare et al. | May 1999 | A |
5917817 | Dunn et al. | Jun 1999 | A |
5917912 | Ginter et al. | Jun 1999 | A |
5920826 | Metso et al. | Jul 1999 | A |
5920847 | Kolling et al. | Jul 1999 | A |
5926535 | Reynolds | Jul 1999 | A |
5944769 | Musk et al. | Aug 1999 | A |
5945989 | Freishtat et al. | Aug 1999 | A |
5963925 | Kolling et al. | Oct 1999 | A |
5982870 | Pershan et al. | Nov 1999 | A |
6005870 | Leung et al. | Dec 1999 | A |
6018571 | Langlois et al. | Jan 2000 | A |
6018737 | Shah et al. | Jan 2000 | A |
6021428 | Miloslavsky | Feb 2000 | A |
6029151 | Nikander | Feb 2000 | A |
6031896 | Gardell et al. | Feb 2000 | A |
6041103 | La Porta et al. | Mar 2000 | A |
6052372 | Gittins et al. | Apr 2000 | A |
6058163 | Pattison et al. | May 2000 | A |
6061432 | Wallace et al. | May 2000 | A |
6092102 | Lefeber et al. | Jul 2000 | A |
6100882 | Sharman et al. | Aug 2000 | A |
6122348 | French-St. George et al. | Sep 2000 | A |
6134318 | O'Neil | Oct 2000 | A |
6134548 | Gottsman et al. | Oct 2000 | A |
6144671 | Perinpanathan et al. | Nov 2000 | A |
6154646 | Tran et al. | Nov 2000 | A |
6161008 | Lee et al. | Dec 2000 | A |
6163692 | Chakrabarti et al. | Dec 2000 | A |
6167119 | Bartholomew et al. | Dec 2000 | A |
6188756 | Mashinsky | Feb 2001 | B1 |
6189026 | Birrell et al. | Feb 2001 | B1 |
6192123 | Grunsted et al. | Feb 2001 | B1 |
6195660 | Polnerow et al. | Feb 2001 | B1 |
6215863 | Bennett et al. | Apr 2001 | B1 |
6219413 | Burg | Apr 2001 | B1 |
6226374 | Howell et al. | May 2001 | B1 |
6240449 | Nadeau | May 2001 | B1 |
6260050 | Yost et al. | Jul 2001 | B1 |
6275575 | Wu | Aug 2001 | B1 |
6282522 | Davis et al. | Aug 2001 | B1 |
6296062 | Sundholm | Oct 2001 | B1 |
6298129 | Culver et al. | Oct 2001 | B1 |
6301338 | Makela et al. | Oct 2001 | B1 |
6301609 | Aravamudan et al. | Oct 2001 | B1 |
6310947 | Polcyn | Oct 2001 | B1 |
6324269 | Malik | Nov 2001 | B1 |
6333973 | Smith et al. | Dec 2001 | B1 |
6349299 | Spencer et al. | Feb 2002 | B1 |
6351279 | Sawyer | Feb 2002 | B1 |
6363143 | Fox | Mar 2002 | B1 |
6371484 | Yuan | Apr 2002 | B1 |
6373930 | McConnell et al. | Apr 2002 | B1 |
6385754 | Mizumoto et al. | May 2002 | B1 |
6389113 | Silverman | May 2002 | B1 |
6408191 | Blanchard et al. | Jun 2002 | B1 |
6408327 | McClennon et al. | Jun 2002 | B1 |
6411605 | Vance et al. | Jun 2002 | B1 |
6418214 | Smythe et al. | Jul 2002 | B1 |
6430176 | Christie | Aug 2002 | B1 |
6430289 | Liffick | Aug 2002 | B1 |
6434226 | Takahashi | Aug 2002 | B1 |
6442245 | Castagna et al. | Aug 2002 | B1 |
6442251 | Maes et al. | Aug 2002 | B1 |
6442748 | Bowman-Amuah | Aug 2002 | B1 |
6453031 | Malik | Sep 2002 | B2 |
6453167 | Michaels et al. | Sep 2002 | B1 |
6459780 | Wurster et al. | Oct 2002 | B1 |
6459913 | Cloutier | Oct 2002 | B2 |
6463145 | O'Neal et al. | Oct 2002 | B1 |
6463464 | Lazaridis et al. | Oct 2002 | B1 |
6466910 | Desmond et al. | Oct 2002 | B1 |
6470079 | Benson | Oct 2002 | B1 |
6473615 | Theppasandra et al. | Oct 2002 | B1 |
6477374 | Shaffer et al. | Nov 2002 | B1 |
6480830 | Ford et al. | Nov 2002 | B1 |
6480890 | Lee, Jr. et al. | Nov 2002 | B1 |
6507644 | Henderson et al. | Jan 2003 | B1 |
6519326 | Milewski et al. | Feb 2003 | B1 |
6522734 | Allen et al. | Feb 2003 | B1 |
6526134 | Wallenius | Feb 2003 | B1 |
6532285 | Tucker et al. | Mar 2003 | B1 |
6535596 | Frey et al. | Mar 2003 | B1 |
6539082 | Lowe et al. | Mar 2003 | B1 |
6542596 | Hill et al. | Apr 2003 | B1 |
6546005 | Berkley et al. | Apr 2003 | B1 |
6547830 | Mercer | Apr 2003 | B1 |
6560329 | Draginich et al. | May 2003 | B1 |
6563914 | Sammon et al. | May 2003 | B2 |
6564261 | Gudjonsson et al. | May 2003 | B1 |
6574324 | Malik | Jun 2003 | B1 |
6574470 | Chow et al. | Jun 2003 | B1 |
6577622 | Schuster et al. | Jun 2003 | B1 |
6577720 | Sutter | Jun 2003 | B1 |
6584122 | Matthews et al. | Jun 2003 | B1 |
6590603 | Sheldon et al. | Jul 2003 | B2 |
6590969 | Peters et al. | Jul 2003 | B1 |
6593352 | Weichert et al. | Jul 2003 | B2 |
6594470 | Barnes et al. | Jul 2003 | B1 |
6600736 | Ball et al. | Jul 2003 | B1 |
6609113 | O'Leary | Aug 2003 | B1 |
6611590 | Lu et al. | Aug 2003 | B1 |
6614786 | Byers | Sep 2003 | B1 |
6618710 | Zondervan et al. | Sep 2003 | B1 |
6625258 | Ram et al. | Sep 2003 | B1 |
6628194 | Hellebust et al. | Sep 2003 | B1 |
6628770 | Jain et al. | Sep 2003 | B1 |
6636587 | Nagai et al. | Oct 2003 | B1 |
6643356 | Hickey et al. | Nov 2003 | B1 |
6654768 | Celik | Nov 2003 | B2 |
6661340 | Saylor et al. | Dec 2003 | B1 |
6665388 | Bedingfield | Dec 2003 | B2 |
6668046 | Albal | Dec 2003 | B1 |
6668049 | Koch et al. | Dec 2003 | B1 |
6681119 | Verdonk | Jan 2004 | B1 |
6683939 | Chiloyan et al. | Jan 2004 | B1 |
6687362 | Lindquist et al. | Feb 2004 | B1 |
6690672 | Klein | Feb 2004 | B1 |
6693897 | Huang | Feb 2004 | B1 |
6697461 | Middleswarth et al. | Feb 2004 | B1 |
6697796 | Kermani | Feb 2004 | B2 |
6704294 | Cruickshank | Mar 2004 | B1 |
6711158 | Kahane et al. | Mar 2004 | B1 |
6717938 | D'Angelo | Apr 2004 | B1 |
6718026 | Pershan et al. | Apr 2004 | B1 |
6718178 | Miner et al. | Apr 2004 | B1 |
6724887 | Eilbacher et al. | Apr 2004 | B1 |
6731238 | Johnson | May 2004 | B2 |
6735292 | Johnson | May 2004 | B1 |
6738458 | Cline et al. | May 2004 | B1 |
6747970 | Lamb et al. | Jun 2004 | B1 |
6748054 | Gross et al. | Jun 2004 | B1 |
6757365 | Bogard | Jun 2004 | B1 |
6768788 | Langseth et al. | Jul 2004 | B1 |
6768790 | Manduley et al. | Jul 2004 | B1 |
6771949 | Corliss | Aug 2004 | B1 |
6775546 | Fuller | Aug 2004 | B1 |
6788772 | Barak et al. | Sep 2004 | B2 |
6788775 | Simpson | Sep 2004 | B1 |
6792092 | Michalewicz | Sep 2004 | B1 |
6798753 | Doganata et al. | Sep 2004 | B1 |
6801610 | Malik | Oct 2004 | B1 |
6807258 | Malik | Oct 2004 | B1 |
6807259 | Patel et al. | Oct 2004 | B1 |
6816468 | Cruickshank | Nov 2004 | B1 |
6816469 | Kung et al. | Nov 2004 | B1 |
6820055 | Saindon et al. | Nov 2004 | B2 |
6842460 | Olkkonen et al. | Jan 2005 | B1 |
6847823 | Lehikoinen et al. | Jan 2005 | B2 |
6853634 | Davies et al. | Feb 2005 | B1 |
6853713 | Fobert et al. | Feb 2005 | B1 |
6856974 | Ganesan et al. | Feb 2005 | B1 |
6876736 | Lamy et al. | Apr 2005 | B2 |
6882714 | Mansfield | Apr 2005 | B2 |
6882838 | Lee et al. | Apr 2005 | B1 |
6885742 | Smith | Apr 2005 | B1 |
6907111 | Zhang et al. | Jun 2005 | B1 |
6917610 | Kung et al. | Jul 2005 | B1 |
6944279 | Elsey et al. | Sep 2005 | B2 |
6947538 | Shen et al. | Sep 2005 | B2 |
6954521 | Bull et al. | Oct 2005 | B2 |
6956942 | McKinzie et al. | Oct 2005 | B2 |
6958984 | Kotzin | Oct 2005 | B2 |
6961409 | Kato | Nov 2005 | B2 |
6963857 | Johnson | Nov 2005 | B1 |
6970705 | Yoshimoto et al. | Nov 2005 | B2 |
6996227 | Albal et al. | Feb 2006 | B2 |
6996370 | DeLoye et al. | Feb 2006 | B2 |
6999563 | Thorpe et al. | Feb 2006 | B1 |
7024209 | Gress et al. | Apr 2006 | B1 |
7027435 | Bardehle | Apr 2006 | B2 |
7031437 | Parsons et al. | Apr 2006 | B1 |
7043521 | Eitel | May 2006 | B2 |
7065198 | Brown et al. | Jun 2006 | B2 |
7068768 | Barnes | Jun 2006 | B2 |
7076528 | Premutico | Jul 2006 | B2 |
7107312 | Hackbarth et al. | Sep 2006 | B2 |
7116972 | Zhang et al. | Oct 2006 | B1 |
7130390 | Abburi | Oct 2006 | B2 |
7139728 | Rigole | Nov 2006 | B2 |
7139782 | Osaki | Nov 2006 | B2 |
7142646 | Zafar et al. | Nov 2006 | B2 |
7149773 | Haller et al. | Dec 2006 | B2 |
7174306 | Haseltine | Feb 2007 | B1 |
7181417 | Langseth et al. | Feb 2007 | B1 |
7187932 | Barchi | Mar 2007 | B1 |
7190773 | D'Silva et al. | Mar 2007 | B1 |
7209955 | Major et al. | Apr 2007 | B1 |
7212808 | Engstrom et al | May 2007 | B2 |
7245929 | Henderson et al. | Jul 2007 | B2 |
7254220 | Reding et al. | Aug 2007 | B1 |
7283808 | Castell et al. | Oct 2007 | B2 |
7308087 | Joyce et al. | Dec 2007 | B2 |
7315614 | Bedingfield, Sr. et al. | Jan 2008 | B2 |
7379538 | Ali et al. | May 2008 | B1 |
7418090 | Reding et al. | Aug 2008 | B2 |
7428580 | Hullfish et al. | Sep 2008 | B2 |
20010003202 | Mache et al. | Jun 2001 | A1 |
20010012286 | Huna et al. | Aug 2001 | A1 |
20010014863 | Williams, III | Aug 2001 | A1 |
20010017777 | Maruyama et al. | Aug 2001 | A1 |
20010025262 | Ahmed | Sep 2001 | A1 |
20010025280 | Mandato et al. | Sep 2001 | A1 |
20010032181 | Jakstadt et al. | Oct 2001 | A1 |
20010039191 | Maierhofer | Nov 2001 | A1 |
20010040954 | Brachman et al. | Nov 2001 | A1 |
20010043689 | Malik | Nov 2001 | A1 |
20010043690 | Bakshi et al. | Nov 2001 | A1 |
20010051534 | Amin | Dec 2001 | A1 |
20010054066 | Spitzer | Dec 2001 | A1 |
20010056466 | Thompson et al. | Dec 2001 | A1 |
20020012425 | Brisebois et al. | Jan 2002 | A1 |
20020018550 | Hafez | Feb 2002 | A1 |
20020022453 | Balog et al. | Feb 2002 | A1 |
20020026575 | Wheeler et al. | Feb 2002 | A1 |
20020035617 | Lynch et al. | Mar 2002 | A1 |
20020040355 | Weiner | Apr 2002 | A1 |
20020046299 | Lefeber et al. | Apr 2002 | A1 |
20020055351 | Elsey et al. | May 2002 | A1 |
20020057678 | Jiang et al. | May 2002 | A1 |
20020069060 | Cannavo et al. | Jun 2002 | A1 |
20020069096 | Lindoerfer et al. | Jun 2002 | A1 |
20020071539 | Diament et al. | Jun 2002 | A1 |
20020073163 | Churchill et al. | Jun 2002 | A1 |
20020075303 | Thompson et al. | Jun 2002 | A1 |
20020075306 | Thompson et al. | Jun 2002 | A1 |
20020076026 | Batten | Jun 2002 | A1 |
20020076027 | Bernnan et al. | Jun 2002 | A1 |
20020077082 | Cruickshank | Jun 2002 | A1 |
20020078153 | Chung et al. | Jun 2002 | A1 |
20020080942 | Clapper | Jun 2002 | A1 |
20020082028 | Wittenkamp | Jun 2002 | A1 |
20020082030 | Berndt et al. | Jun 2002 | A1 |
20020083462 | Arnott | Jun 2002 | A1 |
20020085515 | Jaynes et al. | Jul 2002 | A1 |
20020085687 | Contractor et al. | Jul 2002 | A1 |
20020085701 | Parsons et al. | Jul 2002 | A1 |
20020100798 | Farrugia et al. | Aug 2002 | A1 |
20020103864 | Rodman et al. | Aug 2002 | A1 |
20020103898 | Moyer et al. | Aug 2002 | A1 |
20020110121 | Mishra | Aug 2002 | A1 |
20020115471 | DeLoye et al. | Aug 2002 | A1 |
20020137507 | Winkler | Sep 2002 | A1 |
20020137530 | Karve | Sep 2002 | A1 |
20020138468 | Kermani | Sep 2002 | A1 |
20020146105 | McIntyre | Oct 2002 | A1 |
20020147777 | Hackbarth et al. | Oct 2002 | A1 |
20020147811 | Schwartz et al. | Oct 2002 | A1 |
20020152165 | Dutta et al. | Oct 2002 | A1 |
20020168055 | Crockett et al. | Nov 2002 | A1 |
20020177410 | Klein et al. | Nov 2002 | A1 |
20020178117 | Maguire et al. | Nov 2002 | A1 |
20030014488 | Dalal et al. | Jan 2003 | A1 |
20030035381 | Chen et al. | Feb 2003 | A1 |
20030036380 | Skidmore | Feb 2003 | A1 |
20030045309 | Knotts | Mar 2003 | A1 |
20030046071 | Wyman et al. | Mar 2003 | A1 |
20030053612 | Henrikson et al. | Mar 2003 | A1 |
20030055735 | Cameron et al. | Mar 2003 | A1 |
20030055906 | Packham et al. | Mar 2003 | A1 |
20030058838 | Wengrovitz | Mar 2003 | A1 |
20030069874 | Hertzog et al. | Apr 2003 | A1 |
20030083040 | Ruth et al. | May 2003 | A1 |
20030092451 | Holloway et al. | May 2003 | A1 |
20030093700 | Yoshimoto et al. | May 2003 | A1 |
20030096626 | Sabo et al. | May 2003 | A1 |
20030097635 | Giannetti | May 2003 | A1 |
20030104827 | Moran et al. | Jun 2003 | A1 |
20030108172 | Petty et al. | Jun 2003 | A1 |
20030112928 | Brown et al. | Jun 2003 | A1 |
20030119532 | Hatch | Jun 2003 | A1 |
20030140004 | O'Leary et al. | Jul 2003 | A1 |
20030142798 | Gavette et al. | Jul 2003 | A1 |
20030147518 | Albal et al. | Aug 2003 | A1 |
20030149662 | Shore | Aug 2003 | A1 |
20030158860 | Caughey | Aug 2003 | A1 |
20030165223 | Timmins et al. | Sep 2003 | A1 |
20030167229 | Ludwig et al. | Sep 2003 | A1 |
20030169330 | Ben-Shachar et al. | Sep 2003 | A1 |
20030179743 | Bosik et al. | Sep 2003 | A1 |
20030179864 | Stillman et al. | Sep 2003 | A1 |
20030187992 | Steenfeldt et al. | Oct 2003 | A1 |
20030208541 | Musa | Nov 2003 | A1 |
20030217097 | Eitel | Nov 2003 | A1 |
20030228863 | Vander Veen et al. | Dec 2003 | A1 |
20040002350 | Gopinath et al. | Jan 2004 | A1 |
20040019638 | Makagon et al. | Jan 2004 | A1 |
20040034700 | Polcyn | Feb 2004 | A1 |
20040044658 | Crabtree et al. | Mar 2004 | A1 |
20040052356 | McKinzie et al. | Mar 2004 | A1 |
20040081292 | Brown et al. | Apr 2004 | A1 |
20040103152 | Ludwig et al. | May 2004 | A1 |
20040119814 | Clisham et al. | Jun 2004 | A1 |
20040127256 | Goldthwaite et al. | Jul 2004 | A1 |
20040156491 | Reding et al. | Aug 2004 | A1 |
20040184593 | Elsey et al. | Sep 2004 | A1 |
20040203942 | Dehlin | Oct 2004 | A1 |
20040208305 | Gross et al. | Oct 2004 | A1 |
20040236792 | Celik | Nov 2004 | A1 |
20040247088 | Lee | Dec 2004 | A1 |
20040249884 | Caspi et al. | Dec 2004 | A1 |
20040264654 | Reding et al. | Dec 2004 | A1 |
20050053221 | Reding et al. | Mar 2005 | A1 |
20050102382 | MacGregor et al. | May 2005 | A1 |
20050129208 | McGrath et al. | Jun 2005 | A1 |
20050149487 | Celik | Jul 2005 | A1 |
20050191994 | May et al. | Sep 2005 | A1 |
20050216421 | Barry et al. | Sep 2005 | A1 |
20050220286 | Valdez et al. | Oct 2005 | A1 |
20050243993 | McKinzie et al. | Nov 2005 | A1 |
20060093120 | Thorpe et al. | May 2006 | A1 |
20060095575 | Sureka et al. | May 2006 | A1 |
20060168140 | Inoue et al. | Jul 2006 | A1 |
20060276179 | Ghaffari et al. | Dec 2006 | A1 |
20060277213 | Robertson et al. | Dec 2006 | A1 |
20070021111 | Celik | Jan 2007 | A1 |
Number | Date | Country |
---|---|---|
2240878 | Dec 1998 | CA |
10110942 | Sep 2002 | DE |
10255489 | Jun 2004 | DE |
0818908 | Jan 1998 | EP |
0818908 | Jan 1998 | EP |
1028578 | Aug 2000 | EP |
1161063 | Dec 2001 | EP |
1193617 | Mar 2002 | EP |
1235387 | Aug 2002 | EP |
59-169264 | Sep 1984 | JP |
02260750 | Oct 1990 | JP |
04-336742 | Nov 1992 | JP |
05-316233 | Nov 1993 | JP |
07-030664 | Jan 1995 | JP |
07-058856 | Mar 1995 | JP |
07-107171 | Apr 1995 | JP |
07-107549 | Apr 1995 | JP |
07-123098 | May 1995 | JP |
08-149226 | Jun 1996 | JP |
08-181763 | Jul 1996 | JP |
08-298546 | Nov 1996 | JP |
09-064869 | Mar 1997 | JP |
09-064977 | Mar 1997 | JP |
09-083651 | Mar 1997 | JP |
09-200350 | Jul 1997 | JP |
09-223087 | Aug 1997 | JP |
09-294158 | Nov 1997 | JP |
09-294163 | Nov 1997 | JP |
10-013546 | Jan 1998 | JP |
10-051555 | Feb 1998 | JP |
10-155038 | Jun 1998 | JP |
10-173769 | Jun 1998 | JP |
10-336319 | Dec 1998 | JP |
11-055407 | Feb 1999 | JP |
11-127222 | May 1999 | JP |
11-136316 | May 1999 | JP |
11-187156 | Jul 1999 | JP |
11-191800 | Jul 1999 | JP |
11-266309 | Sep 1999 | JP |
2000-032116 | Jan 2000 | JP |
2000-134309 | May 2000 | JP |
2000-165433 | Jun 2000 | JP |
2000-196756 | Jul 2000 | JP |
2000-224301 | Aug 2000 | JP |
2000-270307 | Sep 2000 | JP |
2001-144859 | May 2001 | JP |
2001-156921 | Jun 2001 | JP |
2001-197210 | Jul 2001 | JP |
2001-197562 | Jul 2001 | JP |
2001-298545 | Oct 2001 | JP |
2002-016673 | Jan 2002 | JP |
2002-044257 | Feb 2002 | JP |
2002-157807 | Feb 2002 | JP |
2002-232575 | Aug 2002 | JP |
2002-237893 | Aug 2002 | JP |
2002-247148 | Aug 2002 | JP |
2002-261834 | Sep 2002 | JP |
2002-300290 | Oct 2002 | JP |
2002-300306 | Oct 2002 | JP |
9614704 | May 1996 | WO |
9938309 | Jul 1999 | WO |
0045557 | Aug 2000 | WO |
001064133 | Oct 2000 | WO |
WO0111586 | Feb 2001 | WO |
WO 0111586 | Feb 2001 | WO |
WO 0135621 | May 2001 | WO |
011052513 | Jul 2001 | WO |
WO 0189212 | Nov 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20050053217 A1 | Mar 2005 | US |
Number | Date | Country | |
---|---|---|---|
60428704 | Nov 2002 | US | |
60436018 | Dec 2002 | US |