IP Library › Granted Patent US 8,914,446
Granted Patent B2
US 8,914,446 · App. 13/080,540 · Granted Dec 16, 2014

IM continuation across SIP sessions and across clients for point-to-point and multi-user chat

Inventor: Robert E. Braudes (Dracut, MA)
Assignee: Avaya Inc.
H04L51/16H04L51/04
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,914,446
App. No.
13/080,540
Filed
Apr 5, 2011
Granted
Dec 16, 2014
Kind
B2
Art Unit
2457
USPC
709/206
Abstract

A communication system can create a conversation identifier (ID) for a logical IM conversation. The conversation ID can identify messages that are associated with the same IM conversation. The associated IM messages can be stored in an archive for later use. When a SIP session ends but an IM conversation continues, a SIP server can rebuild the IM conversation with messages retrieved with the conversation ID. Further, an IM conversation can be restarted on a different IM client by retrieving messages from the archive associated with the previously established conversation ID. Thus, the conversation ID ensures that an IM conversation does not end due to system changes or reconfigurations in IM clients.

Claims (68)

1. A computer program product including computer executable instructions stored onto a non-transitory computer readable medium which, when executed by a processor of a computer, causes the computer to perform a method for conducting an Instant Messaging (IM) session, the instructions comprising:

instructions to receive a first IM message from a first IM client at a Session Initiation Protocol (SIP) instant messaging server, wherein the received first IM message is destined for a second IM client;

instructions to establish, via the SIP instant messaging server, a Session Initiation Protocol (SIP) session between the first IM client and the second IM client;

instructions to generate automatically, at the SIP instant messaging server, a conversation identifier (ID) in response to determining that the conversation ID was not included in the received first IM message;

if the conversation ID was not included in the received first IM message:

instructions to create a new data structure in an archive for the received first IM message; and

instructions to store the received first IM message with the conversation ID in the new data structure;

instructions to send, by the SIP instant messaging server, the received first IM message with the conversation ID to the second IM client;

instructions to receive a third IM message from a third IM client, wherein the third IM client is associated with a first user, wherein the first user is associated with the first IM client, and wherein the third IM message includes the conversation ID;

instructions to retrieve at least a second IM message from the archive, wherein the second IM message is associated with the conversation ID;

instructions to provide at least the second IM message to the second IM client; and

instructions to provide at least the second IM message to the third IM client.

2. The computer program product as defined in claim 1 , wherein the first IM client can also automatically generate the conversation ID, the conversation ID is new, and the conversation ID is not found in the archive.

3. The computer program product as defined in claim 1 , wherein the received first IM message is also sent to the third IM client in a multiuser chat session.

4. The computer program product as defined in claim 1 , wherein the conversation ID indicates that the received first IM message and a least one other IM message, with the conversation ID, are related to a same logical conversation.

5. The computer program product as defined in claim 1 , wherein the conversation ID in the second IM message is based on a user selection of the conversation ID from a user interface.

6. The computer program product as defined in claim 1 , further comprising instructions to provide a privacy setting that dictates which of the IM messages will be provided to an added recipient.

7. The computer program product as defined in claim 1 , further comprising instructions to provide a web service that receives a privacy or security setting for the received first IM message.

8. A method for conducting an instant messaging (IM) session across two or more Session Initiation Protocol (SIP) sessions, comprising:

receiving, by a SIP instant messaging server, a first IM message from a first IM client, wherein the received first IM message is destined for a second IM client;

the SIP instant messaging server establishing a first SIP session between the first IM client and the second IM client;

the SIP instant messaging server automatically generating a conversation identifier (ID) in response to the SIP instant messaging server determining that the received first IM message did not include the conversation ID;

the SIP instant messaging server associating the conversation ID with the IM session;

the SIP instant messaging server sending the received first IM message and the conversation ID to the second IM client;

the SIP instant messaging server storing the received first IM message with the conversation ID in an archive;

the SIP instant messaging server ending the first SIP session;

after the first SIP session is ended, the SIP instant messaging server receiving a second IM message from either the first IM client or the second IM client, wherein the second IM message includes the conversation ID and wherein the conversation ID in the second IM message is retrieved from a previous message containing the conversation ID or based on a user selection of the conversation ID;

the SIP instant messaging server retrieving the conversation ID from the second IM message;

based on information stored in the archive associated with the conversation ID, the SIP instant messaging server establishing a second SIP session between the first IM client and the second IM client;

the SIP instant messaging server sending the second IM message;

defining a new topic for the SIP session between the first IM client and the second IM client;

in response to defining the new topic for the SIP session between the first IM client and the second IM client, creating a second conversation ID based on the new topic for the SIP session between the first IM client and the second IM client; and

associating any new IM messages in the SIP session between the first IM client and the second IM client with the second conversation ID.

9. The method as defined in claim 8 , further comprising:

after receiving the second IM message, the SIP instant messaging server retrieving at least the received first IM message from the archive based on the conversation ID; and

the SIP instant messaging server providing at least the received first IM message to at least one of the first IM client or the second IM client as a previous messages thread.

10. The method as defined in claim 9 , wherein the previous message thread is displayed with the second IM message to appear as an uninterrupted IM conversation.

11. The method as defined in claim 10 , further comprising the SIP instant messaging server sending the received first IM message to a third IM client in a multiuser chat.

12. The method as defined in claim 11 , further comprising:

the SIP instant messaging server receiving a third IM message addressed to a fourth IM client and having the conversation ID, wherein the fourth IM client was not addressed in the first or second IM message and wherein the conversation ID in the third message is retrieved from a previous message containing the conversation ID or based on a user selection of the conversation ID;

after receiving the third IM message, the SIP instant messaging server retrieving at least the received first IM message and the second IM message from the archive based on the conversation ID; and

the SIP instant messaging server providing at least the received first IM message and the second IM message to the fourth IM client as a previous messages thread.

13. The method as defined in claim 8 , wherein the conversation ID in the second IM message is based on a user selection of the conversation ID from a user interface.

14. The method as defined in claim 8 , further comprising a privacy setting that dictates which of the IM messages will be provided to an added recipient.

15. A Session Initiation Protocol (SIP) instant messaging server comprising:

an archive that stores one or more instant messages;

a memory that stores computer-executable instructions;

a processor in communication with the memory, the processor executes the computer-executable instructions to execute:

a message relay that:

receives a first IM message from a first IM client, wherein the received first IM message is destined for a second IM client;

generates a conversation identifier (ID) in response to determining that the received first IM message did not include the conversation ID;

establishes a SIP session between the first IM client and the second IM client;

sends the received first IM message with the conversation ID; and

receives a second IM message from a third IM client, wherein the third IM client is associated with a first user, wherein the first user is also associated with the first IM client, and wherein the second IM message includes the conversation ID;

an archiving engine that:

obtains the conversation ID;

associates the conversation ID with the IM session; and

stores the received first IM message with the conversation ID in the archive; and an archive interface that:

retrieves at least the received first IM message from the archive, wherein the received first IM message is associated with the conversation ID; and

provides at least the received first IM message to the second IM client.

16. The SIP instant messaging server as defined in claim 15 , wherein the archiving engine further:

creates a new data structure in the archive for the received first IM message;

generates automatically a new conversation ID; and

stores the new conversation ID with the received first IM message in the new data structure.

17. The SIP instant messaging server as defined in claim 16 , wherein the data structure includes at least one of the conversation ID, a sender ID, a receiver ID, a time stamp, privacy and security settings, and a message text, wherein the privacy and security settings limit how the instant message is shared with a user.

18. The SIP instant messaging server as defined in claim 17 , wherein the archive includes two or more data structures, and wherein at least two of the data structures share a same conversation ID.

19. The SIP instant messaging server as defined in claim 15 , further comprising a web service that receives a privacy or security setting for the received first IM message.

20. The SIP instant messaging server as defined in claim 15 , wherein the received first IM message is also sent to the third IM client in a multiuser chat session.

Assignments (21)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 4, 2024
From: AVAYA LLC
To: ARLINGTON TECHNOLOGIES, LLC
Reel/Frame 067022/0780 →
INTELLECTUAL PROPERTY RELEASE AND REASSIGNMENT Recorded Mar 25, 2024
From: CITIBANK, N.A.
To: AVAYA LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 066894/0117 →
INTELLECTUAL PROPERTY RELEASE AND REASSIGNMENT Recorded Mar 25, 2024
From: WILMINGTON SAVINGS FUND SOCIETY, FSB
To: AVAYA LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 066894/0227 →
(SECURITY INTEREST) GRANTOR'S NAME CHANGE Recorded Sep 21, 2023
From: AVAYA INC.
To: AVAYA LLC
Reel/Frame 065019/0231 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 045034/0001) Recorded May 18, 2023
From: GOLDMAN SACHS BANK USA., AS COLLATERAL AGENT
To: AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC. (FORMER NAME OF AVAYA CLOUD INC.); HYPERQUALITY, INC.; HYPERQUALITY II, LLC; CAAS TECHNOLOGIES, LLC; AVAYA MANAGEMENT L.P.
Reel/Frame 063779/0622 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 53955/0436) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063705/0023 →
RELEASE OF SECURITY INTEREST IN PATENTS (REEL/FRAME 61087/0386) Recorded May 18, 2023
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS NOTES COLLATERAL AGENT
To: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063690/0359 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 4, 2023
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 063542/0662 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 3, 2023
From: AVAYA MANAGEMENT L.P.; AVAYA INC.; INTELLISIST, INC.; KNOAHSOFT INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB [COLLATERAL AGENT]
Reel/Frame 063742/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS AT REEL 45124/FRAME 0026 Recorded Apr 26, 2023
From: CITIBANK, N.A., AS COLLATERAL AGENT
To: AVAYA HOLDINGS CORP.; AVAYA INC.; AVAYA MANAGEMENT L.P.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
Reel/Frame 063457/0001 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Aug 5, 2022
From: AVAYA INC.; INTELLISIST, INC.; AVAYA MANAGEMENT L.P.; AVAYA CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 061087/0386 →
SECURITY INTEREST Recorded Sep 25, 2020
From: AVAYA INC.; AVAYA MANAGEMENT L.P.; INTELLISIST, INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 053955/0436 →
SECURITY INTEREST Recorded Jan 23, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 045124/0026 →
SECURITY INTEREST Recorded Jan 10, 2018
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS LLC; OCTEL COMMUNICATIONS LLC; VPNET TECHNOLOGIES, INC.; ZANG, INC.
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 045034/0001 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 029608/0256 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 044891/0801 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639 Recorded Dec 15, 2017
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
To: AVAYA INC.
Reel/Frame 045012/0666 →
BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 041576/0001 Recorded Dec 15, 2017
From: CITIBANK, N.A.
To: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS LLC (FORMERLY KNOWN AS OCTEL COMMUNICATIONS CORPORATION); VPNET TECHNOLOGIES, INC.
Reel/Frame 044893/0531 →
SECURITY INTEREST Recorded Jan 27, 2017
From: AVAYA INC.; AVAYA INTEGRATED CABINET SOLUTIONS INC.; OCTEL COMMUNICATIONS CORPORATION; VPNET TECHNOLOGIES, INC.
To: CITIBANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 041576/0001 →
SECURITY AGREEMENT Recorded Mar 13, 2013
From: AVAYA, INC.
To: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE
Reel/Frame 030083/0639 →
SECURITY AGREEMENT Recorded Jan 10, 2013
From: AVAYA, INC.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 029608/0256 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 6, 2011
From: BRAUDES, ROBERT E.
To: AVAYA INC.
Reel/Frame 026080/0583 →
Continuity (1)
Related Publication 20120259925A1 · Oct 11, 2012