Message history display system and method

• US 10,523,612 B2
• Filed: 11/30/2015
• Issued: 12/31/2019
• Est. Priority Date: 12/09/2005
• Status: Active Grant

• Current Assignee: eBuddy Technologies B.V.
• Original Assignee: eBuddy Technologies B.V.
• Inventors: Taylor, Paulo, Rueb, Jan-Joost, Bakker, Onno
• Primary Examiner(s): Asres, Hermon
• Application Number:
  US14/954,887
• Publication Number:
  US 20160094505A1
• Time in Patent Office: 1,492 Days
• Field of Search: 709206
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes
• CPC Class Codes: H04L 65/00 Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1044 Group management mechanisms management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• CPC Class Codes: H04M 3/493 Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals

Abstract

A technique for message history display includes combining message histories for multiple different messaging services. A system constructed according to the technique may include, for example, a message history database; a history aggregation engine that aggregates message logs for storage in the message history database; and a history provisioning engine that provides an aggregated message log associated with the user from the message history database to a requesting device. A method according to the technique may include, for example, identifying a device in association with a user profile; providing an online platform that receives messages from and sends messages to the device; and creating an aggregated log from messages sent to and from the device.

Claims

1. A server system that is provided separately from and coupled to a server of a first network and a server of a second network, the system comprising:

a message history database, embodied in a non-transitory computer-readable medium;

a database interface for accessing the message history database;

a history aggregation engine, embodied in the non-transitory computer-readable medium and coupled to the database interface, that generates a first message log associated with first messages sent to or from a device associated with a user through the server system and the first network in the message history database, generates a second message log associated with second messages sent to or from a device associated with the user through the server system and the second network in the message history database, and aggregates each of the first message log and the second message log into an aggregated message log associated with the user;

an online history provisioning engine, embodied in the non-transitory computer-readable medium and coupled to the database interface, that provides at least part of the aggregated message log associated with the user from the message history database to a requesting device, said at least part of the aggregated message log including at least part of the first message log and at least part of the second message log;

an event queue that collects new first messages and new second messages;

wherein when new messages are collected in the event queue;

the history aggregation engine generates an updated first message log in the message history database, generates an updated second message log in the message history database, and aggregates each of the updated first message log and the updated second message log into an updated aggregated message log associated with the user;

the online history provisioning engine provides at least part of the updated aggregated message log associated with the user to the requesting device, said at least part of the updated aggregated message log including at least part of the updated first message log and at least part of the updated second message log.

2. The system of claim 1,

wherein, in operation, the history aggregation engine receives the first messages through the first network and forms the first message log thereby, and receives the second messages through the second network and forms the second message log thereby.

3. The system of claim 1, further comprising:

a user profile database, embodied in the non-transitory computer-readable medium, including a user record that stores sufficient user profile data to determine aggregation of the first message log and the second message log into the aggregated message log.

4. The system of claim 1, wherein, in operation, the history aggregation engine forms the aggregated message log on the fly.

6. The system of claim 1, wherein the history aggregation engine aggregates each of the first message log and the second message log into the aggregated message log in response to the request for the aggregated message log.

7. The system of claim 1, wherein the history aggregation engine aggregates each of the first message log and the second message log into the aggregated message log in response to the request for the aggregated message log, wherein the first message log is stored in the message history database in a first format before aggregation into the aggregated message log, and the second message log is stored in the message history database in a second format before aggregation into the aggregated message log.

8. The system of claim 1, wherein the history aggregation engine aggregates the first message log into the aggregated message log responsive to the first messages being sent, and aggregates the second message log into the aggregated message log responsive to the second messages being sent.

9. The system of claim 1, wherein the history aggregation engine aggregates the first message log into the aggregated message log responsive to the first messages being sent, by converting a format of the first message log into an aggregated log format, and aggregates the second message log into the aggregated message log responsive to the second messages being sent, by converting a format of the second message log into the aggregated log format, and

the format of the aggregated message log is caused to be in the first format or the second format, responsive to the request for the aggregated message log from the requesting device.

10. The system of claim 1, wherein the history aggregation engine aggregates the first message log into the aggregated message log responsive to the first messages being sent, and aggregates the second message log into the aggregated message log responsive to the second messages being sent, and

the history aggregation engine compiles the at least part of the aggregated message log selectively from the aggregated message log, responsive to the request for the aggregated message log.

11. The system of claim 1, wherein the requesting device is different from the device to or from which the first messages are sent and different from the device to or from which the second messages are sent.

12. The system of claim 1, wherein the device to or from which the first messages are sent is different from the device to or from which the second messages are sent, and the requesting device is one of the device to or from which the first messages are sent and the device to or from which the second messages are sent.

5. A method of managing a message log at a server system that is provided separately from and coupled to a server of a first network and a server of a second network, the method comprising:

generating a first message log associated with first messages sent to or from a device associated with a user through the server system and the first network in a message history database;

generating a second message log associated with second message messages sent to or from a device associated with the user through the server system and the second network in the message history database;

aggregating each of the first message log and the second message log into an aggregated message log associated with the user;

providing at least part of the aggregated message log associated with the user to a requesting device, said at least part of the aggregated message log including at least part of the first message log and at least part of the second message log;

collecting new first messages and new second messages;

when new messages are collected;

generating an updated first message log in the message history database;

generating an updated second message log in the message history database;

aggregating each of the updated first message log and the updated second message log into an updated aggregated message log associated with the user;

providing at least part of the updated aggregated message log associated with the user to the requesting device, said at least part of the updated aggregated message log including at least part of the updated first message log and at least part of the updated second message log.

13. The method of claim 5, wherein the aggregating each of the first message log and the second message log into the aggregated message log comprises aggregating each of the first message log and the second message log into the aggregated message log in response to the request for the aggregated message log.

14. The method of claim 5, wherein the aggregating each of the first message log and the second message log into the aggregated message log comprises aggregating each of the first message log and the second message log into the aggregated message log in response to the request for the aggregated message log,

wherein the first message log is stored in the message history database in a first format before aggregation into the aggregated message log, and the second message log is stored in the message history database in a second format before aggregation into the aggregated message log.

15. The method of claim 5, wherein the aggregating each of the first message log and the second message log into the aggregated message log comprises:

aggregating the first message log into the aggregated message log responsive to the first messages being sent, by converting a format of the first message log into an aggregated log format;

aggregating the second message log into the aggregated message log responsive to the second messages being sent, by converting a format of the second message log into the aggregated log format,

wherein the format of the aggregated message log is caused to be in the first format or the second format, responsive to the request for the aggregated message log from the requesting device.

16. The method of claim 5, wherein the requesting device is different from the device to or from which the first messages are sent and different from the device to or from which the second messages are sent.