Communication threads over different communication mediums

• US 20060168315A1
• Filed: 12/15/2005
• Published: 07/27/2006
• Est. Priority Date: 09/17/2002
• Status: Active Grant

• Current Assignee: Uber Technologies, Inc.
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Malik, Dale W., Daniell, W. Todd
• Granted Patent: US 7,853,668 B2
• Time in Patent Office: Days
• US Class Current: 709/237
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 12/1831 Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

Abstract

Included herein are systems and methods for associating information related to a first communication and information related to a second communication. At least one embodiment of a method includes receiving a first communication, the first communication being associated with a first communications protocol; and associating the received first communication with a communication thread. Additionally embodiments of the method include receiving a second communication, the second communication associated with a second communications protocol, wherein the first communications protocol is different than the second communications protocol; and associating the second communication with the communication thread. Other methods and devices are also provided.

Claims

1. A method for associating information related to a first communication and information related to a second communication, the method comprising:

receiving a first communication, the first communication being associated with a first communications protocol;

associating the received first communication with a communication thread;

receiving a second communication, the second communication associated with a second communications protocol, wherein the first communications protocol is different than the second communications protocol; and

associating the second communication with the communication thread.

2. The method of claim 1, wherein at least one of the first communication and the second communication includes at least one of the following:

a Voice over Internet Protocol (VoIP) communication and a web conference communication.

3. The method of claim 1, further comprising receiving user input related to associating the second communication with the communication thread.

4. The method of claim 1, further comprising storing at least one of the following:

at least a portion of the first communication and at least a portion of the second communication.

5. The method of claim 1, wherein the first communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VOIP) session, and a web conference.

6. The method of claim 1, wherein the second communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VOIP) session, and a web conference.

7. The method of claim 1, further comprising receiving at least one file associated with the second communication and associating the received at least one file associated with the second communication with the communication thread.

8. The method of claim 1, further comprising determining that the first communication is associated with the first protocol.

9. The method of claim 1, further comprising determining that the second communication is associated with the second protocol.

10. The method of claim 1, further comprising receiving at least one user-defined name for the communication thread.

11. A computer readable medium for associating information related to a first communication and information related to a second communication, the computer readable medium comprising:

logic configured to receive a first communication, the first communication being associated with a first communications protocol;

logic configured to associate the received first communication with a communication thread;

logic configured to receive a second communication, the second communication associated with a second communications protocol, wherein the first communications protocol is different than the second communications protocol; and

logic configured to associate the second communication with the communication thread.

12. The computer readable medium of claim 11, wherein at least one of the first communication and the second communication includes at least one of the following:

a Voice over Internet Protocol (VOIP) communication and a web conference communication.

13. The computer readable medium of claim 11, further comprising logic configured to receive user input related to associating the second communication with the communication thread.

14. The computer readable medium of claim 11, further comprising logic configured to store at least one of the following:

at least a portion of the first communication and at least a portion of the second communication.

15. The computer readable medium of claim 11, wherein the first communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VoIP) session, and a web conference.

16. The computer readable medium of claim 11, wherein the second communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VoIP) session, and a web conference.

17. The computer readable medium of claim 11, further comprising logic configured to receive at least one file associated with the second communication and associating the received at least one file associated with the second communication with the communication thread.

18. The method of claim 11, further comprising receiving at least one user-defined name for the communication thread.

19. A client device configured to associate a first communication with a second communication in a common thread, the client device comprising:

an input configured to receive a first communication, the first communication being associated with a first communications protocol, the input further configured to receive a second communication, the second communication being associated with a second communications protocol, wherein the first communications protocol is different than the second communications protocol;

logic configured to associate the received first communication with a communication thread; and

logic configured to associate the second communication with the communication thread.

20. The client device of claim 19, wherein at least one of the first communication and the second communication includes at least one of the following:

a Voice over Internet Protocol (VoIP) communication and a web conference communication.

21. The client device of claim 19, the input further configured to receive user input related to associating the second communication with the communication thread.

22. The client device of claim 19, further comprising logic configured to store at least one of the following:

at least a portion of the first communication and at least a portion of the second communication.

23. The client device of claim 19, wherein the first communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VOIP) session, and a web conference.

24. The client device of claim 19, wherein the second communication includes at least one of the following:

an email, an instant messaging chat session, a Voice over Internet Protocol (VOIP) session, and a web conference.

25. The method of claim 19, further comprising receiving at least one user-defined name for the communication thread.

26. The client device of claim 19, further comprising logic configured to associate at least one received file associated with the second communication with the communication thread.