System and Method for Tracking Messages in a Messaging Service

• US 20140310365A1
• Filed: 04/16/2014
• Published: 10/16/2014
• Est. Priority Date: 01/31/2012
• Status: Abandoned Application

• Current Assignee: Global Relay Communications Incorporated
• Original Assignee: Global Relay Communications Incorporated
• Inventors: Roy, Warren, Quon, Colin Shong Chin, Sample, Michael Edward
• Application Number:
  US14/254,573
• Publication Number:
  US 20140310365A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

Abstract

A system, server and a method for processing messages received at a server device in a network are provided. The method comprises: for a message being transmitted from a first account associated with a client device to a second account in the network, receiving a message event associated with the message at the server; determining whether the message event is associated with an existing conversation involving the first account, and if so setting a sequence number associated with the message event to a value incremented from a current sequence number associated with the existing conversation, otherwise setting the sequence number to a value to track a new conversation; and sending the sequence number to the first user account.

Claims

1. A method for processing messages received at a server device in a network, the method comprising:

receiving a message event associated with a message being transmitted from a first account associated with a first client device to a second account in the network associated with a second client device at the server;

determining whether the message event is associated with an existing conversation involving the first account, and if so setting a sequence number associated with the message event to a value incremented from a current sequence number associated with the existing conversation, otherwise setting the sequence number to a value to track a new conversation; and

sending the sequence number to the first user account.

2. The method of claim 1, further comprising:

after the sequence number has been set, forwarding the message event to the second client device.

3. The method of claim 2, further comprising:

storing the sequence number and the message event in a database.

4. The method of claim 3, further comprising:

after the message event has been sent to the second client device, evaluating sequences numbers associated with the existing conversation to determine if there is a gap in an expected sequence of the sequence numbers; and

when the gap is detected, searching the data store for a message event associated with a sequence number in the gap and when the message event associated with the sequence number in the gap is identified, providing information about the message event associated with the sequence number in the gap to first or second client device which did not receive same.

5. The method of claim 1, further comprising:

when the message event is associated with a new thread for the existing conversation, associating a new thread number with the sequence number.

6. The method of claim 1, further comprising:

receiving a second message event associated with a second message being transmitted from the first account to the second account at the server; and

determining whether the second message event is associated with an existing conversation involving the first account, and if so setting a sequence number associated with the second message event to a value incremented from a current sequence number associated with the existing conversation.

7. The method of claim 1, further comprising:

synchronizing the second client with the message events in the conversation using the sequence numbers associated with the message events in the conversation.

8. The method of claim 1, further comprising:

receiving a second message event associated with a second message being transmitted from the second account to the first account at the server;

determining whether the second message event is associated with an existing conversation involving the first account,

and if so setting a sequence number associated with the second message event to a value incremented from a current sequence number associated with the existing conversation, otherwise

setting the sequence number to a value to track a new conversation and analyzing the sequence number to determine whether the second account sent to the first account a response to the message event, and if so sending the second message event to the first account.

9. The method of claim 8, further comprising:

marking the second message event with an in-reference-to tag using the sequence number of the first message event.

10. A server for processing messages received from devices in a network, the server comprising:

a processor; and

a memory device for storing instructions for execution on the processor, the instructions causing the processor to

receive a message event associated with the message at the server for a message being transmitted from a first account associated with a client device to a second account in the network,

determine whether the message event is associated with an existing conversation involving the first account,

and if so set a sequence number associated with the message event to a value incremented from a current sequence number associated with the existing conversation, otherwise

set the sequence number to a value to track a new conversation; and

send the sequence number to the first user account.

11. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

forward the message event to a second client device associated with the second account in the network after the sequence number has been set.

12. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

store the sequence number and the message event in a database.

13. The server of claim 12, wherein the memory device stores further instructions for execution on the processor causing the processor to:

evaluate sequences numbers associated with the existing conversation to determine if there is a gap in an expected sequence of the sequence numbers after the message event has been sent to the second client device; and

search the data store for a message event associated with a sequence number in the gap when the gap is detected, and when the message event associated with the sequence number in the gap is identified, provide information about the message event associated with the sequence number in the gap to first or second client device which did not receive same.

14. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

associate a new thread number with the sequence number when the message event is associated with a new thread for the existing conversation.

15. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

receive a second message event associated with a second message being transmitted from the first account to the second account at the server; and

determine whether the second message event is associated with an existing conversation involving the first account, and if so set a sequence number associated with the second message event to a value incremented from a current sequence number associated with the existing conversation.

16. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

synchronize the second client with the message events in the conversation using the sequence numbers associated with the message events in the conversation.

17. The server of claim 10, wherein the memory device stores further instructions for execution on the processor causing the processor to:

receive a second message event associated with a second message being transmitted from the second account to the first account at the server;

determine whether the second message event is associated with an existing conversation involving the first account,

and if so set a sequence number associated with the second message event to a value incremented from a current sequence number associated with the existing conversation, otherwise

set the sequence number to a value to track a new conversation and analyze the sequence number to determine whether the second account sent to the first account a response to the message event, and if so send the second message event to the first account.

18. The server of claim 17, wherein the memory device stores further instructions for execution on the processor causing the processor to:

mark the second message event with an in-reference-to tag using the sequence number of the first message event.