Voice mail notification using instant messaging

- AT&T

A system and method that notifies a voice mailbox subscriber of the receipt of a message at a voicemail server using instant messaging. A preferred embodiment of the invention includes an enhanced notification server that receives a notification of the message from the voicemail server, queries the availability of an instant messaging client via an instant messaging presence server, and forwards the notification to the instant messaging client via the instant messaging presence server if the instant messaging client is available. In preferred embodiments, provisions are made to forward the message to the subscriber via instant messaging.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description

This is a continuation application of U.S. application Ser. No. 10/232,749 filed Sep. 3, 2002, now U.S. Pat. No. 6,707,809 which is herein incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

Most, if not all, telephone users have at least one voice mailbox in which callers can leave voice messages when the users are unavailable to answer calls. Voicemails are typically retrieved by the users in a number of ways. For example, using a telephone set in her office, a voicemail user who returns from a lunch break can hear voicemails that were left at her voice mailbox while she was at lunch. Alternatively, the voicemail user could remotely dial in (e.g., from her home or while she is out of town) to her voice mailbox to retrieve the voicemail messages. Regardless of the method used, the voicemail user must first access her voicemail server to determine whether or not a new message has been stored in her voice mailbox since the last time she checked the mailbox. This can be inconvenient to the user.

Accordingly, there is a need for a system and method that would notify the user instantaneously when a voicemail has arrived at her voice mailbox.

SUMMARY OF THE INVENTION

The present invention is a system and method that provides enhanced notification of messages received by a voicemail server using instant messaging. In a preferred embodiment, the invention provides an enhanced notification server that works with a voicemail server and an instant messaging presence server to notify an instant messaging client of messages received at the voicemail server. When a new message, e.g., a voicemail, a fax message, or the like, intended for a subscriber of a voice mailbox is received, the voicemail server sends a notification to the enhanced notification server. The enhanced notification server then queries the instant messaging presence server to determine whether the voice mailbox subscriber (who is also the instant messaging client) is available. “Available” means the instant messaging client is online, engaged in an instant messaging session, or otherwise logged on to the instant messaging presence server. If the instant messaging client is available, the enhanced notification server forwards the notification to the instant messaging client. Preferably, forwarding of the notification to the instant messaging client (the voice mailbox subscriber) is accomplished via the instant messaging presence server. The enhanced notification server queues the notification for a later delivery if the instant messaging client is not available.

In another preferred embodiment, the invention provides a method for notifying an instant messaging client of messages received by a voicemail server of which the instant messaging client is a voice mailbox subscriber. The methods include the following steps. First, when the voicemail server receives a message, e.g., a voicemail, a fax message, and the like, which is intended for the instant messaging client, the voicemail server sends a notification to an enhanced notification server. The notification indicates that a new message is available on the voicemail server for retrieval. The enhanced notification server then queries an instant messaging presence server whether the instant messaging client is available. If the voice mailbox subscriber (who is also the instant messaging client) is available, the enhanced notification server forwards the notification to the instant messaging presence server, which in turns forwards the notification to the instant messaging client using known instant messaging technologies.

In other embodiments, the invention can be adapted to forward the incoming message to the voice mailbox subscriber via instant messaging.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing the system architecture used in a preferred embodiment of the invention.

FIG. 2 is a schematic diagram summarizing the sequence of activities of a preferred embodiment that involves a voicemail server, an enhanced notification server, an instant messaging presence server, and an instant messaging client.

FIG. 3 is a flowchart showing exemplary steps involved in implementing a preferred embodiment of the invention.

FIG. 4 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention.

FIG. 5 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention.

FIG. 6 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention.

 DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic diagram showing the system architecture used in a preferred embodiment of the invention. PSTN 110, voicemail (VM) server 120, IP network 140, and instant messaging (IM) presence server 150 are known elements in the art. As shown in FIG. 1, PSTN 110 is accessible to users via one or more of wireless telephone 102, fax machine 104, and wireline telephone 106. Although not indicated in FIG. 1, PSTN 100 can be accessible to other telecommunications devices including, for example, a computer with a modem, an interactive pager, a personal digital assistant, and the like.

As known in the art, voicemail server 120 can receive voicemail, fax messages, and the like from various sources including, for example, PSTN 110, through link 112. Voicemail server 120 is in communication with IP network 140 via link 122. Voicemail server 120 and IP network 140 can communicate with each other using known protocols, including, for example, TCP/IP.

Preferably, voicemail server 120 is adapted to provide traditional voicemail features as well as new features. Voicemail server 120 preferably includes a profile for each of its voice mailbox subscribers regarding how notification of incoming messages should be performed. Preferably, voicemail server 120 is adapted to initiate the notification by communicating with enhanced notification server 130. Communications between voicemail server 120 and enhanced notification server 130 can be accomplished via IP network 140 and links 122 and 142.

As known in the art, there are a number of different protocols used by different instant messaging service providers. For example, each of AOL, Yahoo!, and MSN uses its own protocol for its instant messaging service. Accordingly, communication sessions between enhanced notification server 130 and instant messaging presence server 150 is facilitated by the appropriate protocol associated with instant messaging presence 150.

Preferably, enhanced notification server 130 includes microprocessor 134. Microprocessor 134 is preferably adapted to provide a number of functionalities. For example, in a preferred embodiment of the invention, enhanced notification server 130 can query instant messaging presence server 150 whether instant messaging client 160 is available. For example, enhanced notification server 130 can query instant messaging presence server 150 whether instant messaging client 160 (voicemail subscriber) has an active instant messaging session. If instant messaging client 160 is available, enhanced notification server 130 forwards the notification to instant messaging client 160. The notification is preferably forwarded via IP network 140 and instant messaging presence server 150 through links 142, 152, and 132.

FIG. 2 is a schematic diagram summarizing the sequence of activities involving voicemail server 120, enhanced notification server 130, instant messaging presence server 150, and instant messaging client 160. As shown in FIG. 2, communications between enhanced notification server 130 and instant messaging presence server 150 include multiple queries and responses regarding the presence or availability of instant messaging client 160. Additional details regarding FIG. 2 are explained in conjunction with the description of FIG. 3 below.

FIG. 3 is a flowchart showing exemplary steps involved in implementing a preferred embodiment of the invention.

In step 302, an incoming message (e.g., voice, fax, or the like) intended for a voice mailbox subscriber is received at voicemail server 120.

In step 304, voicemail server 120 sends a notification to enhanced notification server 130. The notification may include a number of attributes associated with the incoming message including, for example, the date and time on which the incoming message was received, the identity of the sender of the incoming message, the length (or size) of the incoming message, and so on. The notification preferably includes a voice mailbox identification of the voice mailbox subscriber. The voice mailbox identification can be, for example, a telephone number associated with the voice mailbox subscriber.

In step 306, enhanced notification server 130 maps the voice mailbox identification (VM ID) to an instant messaging identification (IM ID). Note that both the VM ID and the IM ID belong to a common entity. The common entity is instant messaging client 160 that is also the voice mailbox subscriber for which the incoming message is intended. The IM ID can be, for example, an alphanumeric character string associated with instant messaging client 160.

In step 308, enhanced notification server 130 checks the presence status or availability of instant messaging client 160. Preferably, the IM ID is utilized in this step.

In step 310, if it is determined that instant messaging client 160 is present or available, the process goes to step 312; otherwise, the process goes to step 314.

In step 312, the notification is forwarded by enhanced notification server 130 to instant messaging client 160. Preferably, the notification is forwarded via instant messaging presence server 150.

In step 314, the notification is queued at enhanced notification server 130 for a later delivery until instant messaging client 160 is available.

FIG. 4 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention. In this embodiment, the invention enables a user of the invention, e.g., the voice mailbox subscriber or instant messaging client 160 discussed above, to receive the incoming message along with the notification. In this embodiment, voicemail server 120 is adapted to attach the incoming message to the notification.

In step 402, preferences are set. The preferences may include, for example, the user's desire to receive the incoming message in addition to the notification via instant messaging. Preferences are stored in a location that is accessible to voicemail server 120.

In step 404, voicemail server 120 receives an incoming message.

In step 406, voicemail server 120 reviews the preferences set in step 402.

In step 408, if the preferences have been set such a way that the user does not wish to have the incoming message attached to a notification, the process goes to step 412; otherwise, the process goes to step 410.

In step 410, voicemail server 120 prepares a notification with the incoming message attached to the notification.

In step 412, voicemail server 120 prepares a notification without the incoming message attached to the notification.

Following one of steps 410 and 412, steps generally similar to steps 304 through 314 shown in FIG. 3 and discussed above may be used to implement this embodiment.

FIG. 5 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention. In this embodiment, the invention enables a user of the invention to receive the incoming message along with the notification. In this embodiment, enhanced notification server 130 is adapted to retrieve the incoming message from voicemail server 120 and attach the incoming message to the notification.

In step 502, preferences are set. The preferences may include, for example, the user's desire to receive the incoming message in addition to the notification via instant messaging. Preferences are stored in a location that is accessible to enhanced notification server 130.

After step 502 but before step 506, steps generally similar to steps 302 through 304 shown in FIG. 3 and discussed above may be used to implement this invention.

In step 506, enhanced notification server 130 receives a notification from voicemail server 120 that an incoming message has been received by voicemail server 120.

In step 508, enhanced notification server 130 reviews the preferences set in step 502.

In step 510, if the preferences have been set such a way that the user does not wish to have the incoming message attached to the notification via instant messaging, the process goes to steps that are generally similar to steps 306 through 314 shown in FIG. 3 and described above. Otherwise, the process goes to step 512.

In step 512, enhanced notification server 130 communicates with voicemail server 120 to retrieve the incoming message.

In step 514, enhanced notification server 130 attaches the incoming message to the notification.

Following step 514, steps generally similar to steps 306 through 314 shown in FIG. 3 and discussed above may be used to implement this embodiment.

FIG. 6 is a flowchart showing exemplary steps involved in implementing another preferred embodiment of the invention. In this embodiment, the invention enables a user of the invention to receive the incoming message via instant messaging after reviewing the notification. In this embodiment, enhanced notification server 130 is adapted to retrieve the incoming message from voicemail server 120 after receiving a respond from the user that the user wishes to receive the incoming message via instant messaging.

Steps similar to steps 302 through 310 shown in FIG. 3 and discussed above may be used to implement this embodiment.

Following step 310, in step 612, enhanced notification server 130 forwards the notification to the user. Here, the notification includes a query whether the user wishes to receive the incoming message via instant messaging.

If in step 614 the user responds with an affirmative answer, the process goes to step 616. Otherwise, the process ends.

In step 616, enhanced notification server 130 communicates with voicemail server 120 to retrieve the incoming message.

In step 618, after the incoming message is received from voicemail server 120, enhanced notification server 130 forwards the incoming message to the user via instant messaging.

The foregoing disclosure of the preferred embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be obvious to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.

Further, in describing representative embodiments of the present invention, the specification may have presented the method and/or process of the present invention as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process of the present invention should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the present invention.

Claims

1. A method, at an enhanced notification server, for notification of messages comprising:

receiving a notification from a first message server, wherein the notification includes information related to an incoming message that is intended for a subscriber, wherein the notification further includes a first identification associating the subscriber with the first message server;
determining at least one user preference setting, wherein the at least one user preference setting indicates whether the subscriber desires to receive the incoming message with the notification;
mapping the first identification to a second identification, wherein the second identification associates the subscriber with a second message server;
querying the second message server using the second identification, to determine current availability of the subscriber on a communications device associated with the second message server;
in response to a determination that the subscriber is currently available on the communications device, forwarding the notification to the communications device; and
in response to a determination that the subscriber is currently not available on the communications device, queuing the notification at the enhanced notification server for later delivery.

2. The method of claim 1, wherein the first message server is a voicemail server.

3. The method of claim 1, wherein the information related to an incoming messages includes one or more of the following: an identity of a sender of the incoming message, a date of the incoming message, a time of the incoming message, a size of the incoming message.

4. The method of claim 1, wherein the second message server is an instant messaging presence server.

5. The method of claim 1, wherein the communications device is an instant messaging client.

6. The method of claim 1, further comprising, in response to a determination that the at least one user preference setting indicates that the subscriber prefers to receive the incoming message with the notification, attaching the incoming message to the notification.

7. An enhanced notification server configured to:

receive a notification from a first message server, wherein the notification includes information related to an incoming message that is intended for a subscriber, wherein the notification further includes a first identification associating the subscriber with the first message server;
determine at least one user preference setting, wherein the at least one user preference setting indicates whether the subscriber desires to receive the incoming message with the notification;
map the first identification to a second identification, wherein the second identification associates the subscriber with a second message server;
query the second message server using the second identification, to determine current availability of the subscriber on a communications device associated with the second message server;
in response to a determination that the subscriber is currently available on the communications device, forward the notification to the communications device; and
in response to a determination that the subscriber is currently not available on the communications device, queue the notification at the enhanced notification server for later delivery.

8. The server of claim 7, wherein the first message server is a voicemail server.

9. The server of claim 7, wherein the information related to an incoming messages includes at least one of the following: an identity of a sender of the incoming message, a date of the incoming message, a time of the incoming message, a size of the incoming message.

10. The server of claim 7, wherein the second message server is an instant messaging presence server.

11. The server of claim 7, wherein the communications device is an instant messaging client.

12. The server of claim 7, further configured to, in response to a determination that the at least one user preference setting indicates that the subscriber prefers to receive the incoming message with the notification, attach the incoming message to the notification.

13. A method, at an enhanced notification server, for notification of messages comprising:

receiving a notification from a first message server, wherein the notification includes information related to an incoming message that is intended for a subscriber, wherein the notification further includes a first identification associating the subscriber with the first message server;
mapping the first identification to a second identification, wherein the second identification associates the subscriber with a second message server;
querying the second message server, using the second identification, to de current availability of the subscriber on a communications device associated with the second message server;
in response to a determination that the subscriber is currently available on the communications device, forwarding the notification to the communications device, wherein the notification includes a query of whether the subscriber desires to receive the incoming message via the second message server;
in response to a determination that the subscriber is not currently available on the communications device, queuing the notification at the enhanced notification server for later delivery; and
in response to receiving a response to the query, indicating that the subscriber desires to receive the incoming message via the second messaging server, retrieving the incoming message from the first messaging server.

14. The method of claim 13, wherein the first message server is a voicemail server.

15. The method of claim 13, further comprising forwarding the retrieved incoming message to the second messaging server.

16. The method of claim 13, wherein the second message server is an instant messaging presence server.

17. The method of claim 13, wherein the communications device is an instant messaging client.

Referenced Cited
U.S. Patent Documents
4930152 May 29, 1990 Miller
4933967 June 12, 1990 Lo et al.
4951044 August 21, 1990 Nelson et al.
5058152 October 15, 1991 Solomon et al.
5313515 May 17, 1994 Allen et al.
5353331 October 4, 1994 Emery et al.
5361295 November 1, 1994 Solomon et al.
5425091 June 13, 1995 Josephs
5493607 February 20, 1996 Arumainayagam et al.
5521969 May 28, 1996 Paulus et al.
5559800 September 24, 1996 Mousseau et al.
5572578 November 5, 1996 Lin et al.
5572583 November 5, 1996 Wheeler, Jr. et al.
5631948 May 20, 1997 Bartholomew et al.
5680442 October 21, 1997 Bartholomew et al.
5684862 November 4, 1997 Finnigan
5687220 November 11, 1997 Finnigan
5692033 November 25, 1997 Farris
5712903 January 27, 1998 Bartholomew et al.
5717742 February 10, 1998 Hyde-Thomson
5740230 April 14, 1998 Vaudreuil
5740231 April 14, 1998 Cohn et al.
5742668 April 21, 1998 Pepe et al.
5742763 April 21, 1998 Jones
5742769 April 21, 1998 Lee et al.
5742905 April 21, 1998 Pepe et al.
5764747 June 9, 1998 Yue et al.
5768348 June 16, 1998 Solomon et al.
5790637 August 4, 1998 Johnson et al.
5802466 September 1, 1998 Gallant et al.
5812639 September 22, 1998 Bartholomew et al.
5812670 September 22, 1998 Micali
5832072 November 3, 1998 Rozenblit
5832221 November 3, 1998 Jones
5838768 November 17, 1998 Sumar et al.
5848132 December 8, 1998 Morley et al.
5884160 March 16, 1999 Kanazaki
5905774 May 18, 1999 Tatchell et al.
5930479 July 27, 1999 Hall
5940478 August 17, 1999 Vaudreuil et al.
5940740 August 17, 1999 Aas et al.
5987317 November 16, 1999 Venturini
5999595 December 7, 1999 Shaffer et al.
6002751 December 14, 1999 Shaffer
6005845 December 21, 1999 Svennesson et al.
6005922 December 21, 1999 Longster et al.
6006087 December 21, 1999 Amin
6061432 May 9, 2000 Wallace et al.
6064876 May 16, 2000 Ishida et al.
6069890 May 30, 2000 White et al.
6122348 September 19, 2000 French-St. George et al.
6219694 April 17, 2001 Lazaridis et al.
6233430 May 15, 2001 Helferich
6259892 July 10, 2001 Helferich
6389276 May 14, 2002 Brilla et al.
6393908 May 28, 2002 Swain et al.
6408176 June 18, 2002 Urs
6507643 January 14, 2003 Groner
6654601 November 25, 2003 Picoult et al.
6707890 March 16, 2004 Gao et al.
6782081 August 24, 2004 Malik
6865384 March 8, 2005 Sagi et al.
6882708 April 19, 2005 Bedingfield et al.
6981223 December 27, 2005 Becker et al.
6999565 February 14, 2006 Delaney et al.
7142646 November 28, 2006 Zafar et al.
7167546 January 23, 2007 Moore
20010033639 October 25, 2001 Martin
20010044297 November 22, 2001 Myer et al.
20020067806 June 6, 2002 Rodriguez et al.
20020077082 June 20, 2002 Cruickshank
20020087643 July 4, 2002 Parsons et al.
20020090963 July 11, 2002 Avalos et al.
20020110226 August 15, 2002 Kovales et al.
20020173306 November 21, 2002 Adamany et al.
20020173308 November 21, 2002 Dorenbosch et al.
20020181673 December 5, 2002 Henry et al.
20030002632 January 2, 2003 Bhogal et al.
20030027560 February 6, 2003 Jammal
20030095643 May 22, 2003 Fortman et al.
20030131143 July 10, 2003 Myers
20030147512 August 7, 2003 Abburi
20030194990 October 16, 2003 Helferich
20030229670 December 11, 2003 Beyda
20040076272 April 22, 2004 Zafar et al.
20040161089 August 19, 2004 Hanson et al.
20050020288 January 27, 2005 Davis et al.
20050055411 March 10, 2005 Bouchard et al.
20050136896 June 23, 2005 Ward et al.
20050286689 December 29, 2005 Vuori
Foreign Patent Documents
0255325 February 1988 EP
0412799 February 1991 EP
0507125 October 1992 EP
0543235 May 1993 EP
0624967 November 1994 EP
0662762 July 1995 EP
0782304 July 1997 EP
0782315 July 1997 EP
0782316 July 1997 EP
0813162 December 1997 EP
0825752 February 1998 EP
0841796 May 1998 EP
0843453 May 1998 EP
0886228 December 1998 EP
0841796 September 1999 EP
0255325 June 2007 EP
9708901 March 1997 WO
Other references
  • M., Day, et al.; Instant Messaging/Presence Protcol Requirements; Feb. 2000; pp. 1-25.
  • M. Day et al.; A Model for Presence and Instant Messaging; Feb. 2000; pp. 1-17.
  • M. Day, et al., A Model for Presence and Instant Messaging, Feb. 2000, pp. 1-17.
  • M. Day, et al., Instant Messaging/Presence Protocol Requirements, Feb. 2000, pp. 1-26.
  • An Enhanced Message Networking Topology: Multimedia Messaging with the Intuity (TM) Interchange Server, Bell Labs Technical Journal, Apr.-Jun. 1998, pp. 124-135.
  • Die T-Net-Box-der Anrufbeantworter in Netz, XP-000861610, 1998.
  • General Recommendations on Telephone Switching and Signalling-Introduction to Intelligent Network Capability Set 1, International Telecommunication Union, XP-002141945, Mar. 1993.
  • The Belcore and ITU-T Call Model Operations, XP-002141946, 1998.
  • Transactions in Intelligent Networks, XP-002141947, 1998.
  • Voice Services on the Intelligent Network: Intelligent Peripherals and Service Nodes, F. Bosco, XP-000607359, Aug. 1992.
  • James Carlton Bedingfield, Non Final Office Action, mailed Apr. 1, 2003, filing date Feb. 25, 2000 U.S. Appl. No. 09/513,005 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Final Office Action, mailed Jan. 28, 2004, filing date Feb. 25, 2000 U.S. Appl. No. 09/513,005 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Non Final Office Action, mailed Jul. 1, 2004, filing date Feb. 25, 2000 U.S. Appl. No. 09/513,005 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Notice of Allowance Fees, mailed Aug. 25, 2004, filing date Feb. 25, 2000 U.S. Appl. No. 09/513,005 (Note: copy not provided as it is part of PTO records).
  • Gao et al., Non Final Office Action, mailed Mar. 24, 2003, filing date Sep. 3, 2002 U.S. Appl. No. 10/232,749 (Note: copy not provided as it is part of PTO records).
  • Gao et al., Final Office Action, mailed Jul. 11, 2003, filing date Sep. 3, 2002 U.S. Appl. No. 10/232,749 (Note: copy not provided as it is part of PTO records).
  • Gao et al., Notice of Allowance and Fees, mailed Oct. 17, 2003, filing date Sep. 3, 2002 U.S. Appl. No. 10/232,749 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Requirement for Restriction/Election, mailed Sep. 9, 2004, filing date Mar. 14, 2003 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Non Final Office Action, mailed Jan. 14,2005, filing date Mar. 14, 2003 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Final Office Action, mailed Jul. 14,2005, filing date Mar. 14, 2002 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Non final Office Action, mailed Dec. 5,2005, filing date Mar. 14, 2002 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Examiners interview, mailed Jan. 4,2005, filing date Mar. 14, 2002 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Final Office Action, mailed May 18, 2006, filing date Mar. 14, 2002 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Notice of Allowance and Fees, mailed Aug. 22, 2006, filing date Mar. 14, 2002 U.S. Appl. No. 10/097,278 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Examiner Interview Summary, mailed Oct. 20,2005, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Final Office Action, mailed Jan 10,2005, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Non Final Office Action, mailed Jun. 28,2006, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Non Final Office Action, mailed Jul. 14,2005, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Final Office Action, mailed Dec. 13, 2006, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Examiner Interview Summary, mailed Feb. 22,2007, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • Royce D. Jordan Jr., Non Final Office Action, mailed Mar. 30,2007, filing date Jan. 4, 2005 U.S. Appl. No. 11/028,973 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Non Final Office Action, mailed Feb. 10,2006, filing date Feb. 13, 2003 U.S. Appl. No. 10/369,445 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Final Office Action, mailed Jul. 24,2006, filing date Feb. 13, 2003 U.S. Appl. No. 10/369,445 (Note: copy not provided as it is part of PTO records).
  • James Carlton Bedingfield, Notice of Allowance and Fees, mailed Jun. 1,2007, filing date Feb. 13, 2003 U.S. Appl. No. 10/369,445 (Note: copy not provided as it is part of PTO records).
  • Maria Adamczyk, Non Final Office Action, mailed Apr. 22,2005, filing date Jan. 31, 2003 U.S. Appl. No. 10/355,931 (Note: copy not provided as it is part of PTO records).
  • Maria Adamczyk, Final Office Action, mailed Nov. 22,2005, filing date Jan. 31, 2003 U.S. Appl. No. 10/355,931 (Note: copy not provided as it is part of PTO records).
  • Maria Adamczyk, Non Final Office Action, mailed Aug. 10,2006, filing date Jan. 31, 2003 U.S. Appl. No. 10/355,931 (Note: copy not provided as it is part of PTO records).
  • Maria Adamczyk, Notice of Allowance and Fees, mailed Feb. 7,2007, filing date Jan. 31, 2003 U.S. Appl. No. 10/355,931 (Note: copy not provided as it is part of PTO records).
  • Mary Arnoff, Non Final Office Action, mailed Mar. 24,2006, filing date May 5, 2004 U.S. Appl. No. 10/839,535 (Note: copy not provided as it is part of PTO records).
  • Mary Arnoff, Final Office Action, mailed Apr. 23,2007, filing date May 5, 2004 U.S. Appl. No. 10/839,535 (Note: copy not provided as it is part of PTO records).
  • Arnoff; Non-Final Office Action, mailed Oct. 31, 2007; U.S. Appl. No. 10/839,535; filed May 5, 2004 (Note: copy not provided as it is part of PTO records).
Patent History
Patent number: 7369647
Type: Grant
Filed: Jan 20, 2004
Date of Patent: May 6, 2008
Patent Publication Number: 20040146144
Assignee: AT&T Delaware Intellectual Property, Inc. (Wilmington, DE)
Inventors: Xiaofeng Gao (Alpharetta, GA), Maria Adamczyk (Alpharetta, GA), Karen Mullis (Loganville, GA)
Primary Examiner: Gerald Gauthier
Attorney: Thomas, Kayden, Horstemeyer & Risley, LLP
Application Number: 10/759,165