MESSAGE HISTORY DISPLAY SYSTEM AND METHOD

• US 20200137016A1
• Filed: 12/31/2019
• Published: 04/30/2020
• 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
• Granted Patent: US 10,986,057 B2
• Time in Patent Office: Days
• 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 system comprising:

a server configured to;

identify a plurality of devices in association with a user profile;

receive communications from the plurality of devices bound for a respective plurality of networks;

forward the communications to the respective plurality of networks;

a history aggregation engine implemented at the server and configured to;

create a plurality of message logs from the communications for respective ones of the plurality of devices;

aggregate the plurality of message logs to create an aggregated message log;

a history provisioning engine implemented at the server and configured to;

receive a request for one of the plurality of message logs from a respective one of the plurality of devices;

compile at least a portion of the aggregated message log, including a portion of at least a sub-plurality of the plurality of message logs, into a format suitable for display on a device associated with the requested message log;

provide the at least a portion of the aggregated message log in response to the request.

2. The system of claim 1, wherein the history provisioning engine is further configured to make message log entries when a message is sent to or from one of the plurality of devices.

3. The system of claim 1, wherein the history provisioning engine is further configured to store one of the plurality of message logs on a respective one of the plurality of devices.

4. The system of claim 1, wherein the request is received from a device associated with the request for one of the plurality of message logs.

5. The system of claim 1, wherein the aggregated message log is compiled immediately after the request is received.

6. The system of claim 1, wherein the aggregated message log is compiled, at least in part, before the request is received.

7. The system of claim 1, wherein the history aggregation engine is further configured to store the aggregated message log in a plurality of formats.

8. The system of claim 7, wherein at least one of the plurality of formats is suitable for display on each of the plurality of devices.

9. The system of claim 1, wherein the aggregated message log is displayed on a device associated with the request for one of the plurality of message log.

10. The system of claim 1, wherein the history provisioning engine is configured to provide the at least a portion of the aggregated message log to a device of the plurality of devices different from the respective one of the plurality of devices.

11. The system of claim 1, further comprising:

a message history data store, embodied in a first computer-readable medium and configured to store the plurality of message logs, including a first message log of the plurality of message logs associated with a user and a second message log of the plurality of message logs associated with the user, wherein the first message log and the second message log are associated with different messaging services and wherein the second message log includes a message log of a mobile device associated with the user;

the history aggregation engine further configured to aggregate the plurality of message logs using the messaged history data store.

12. The system of claim 11, wherein the history aggregation engine further includes an http port configured to receive second messages from the mobile device associated with the user bound for a messaging service, wherein the second messages from the mobile device associated with the user are forwarded to the messaging service.

13. The system of claim 1, wherein the history aggregation engine is implemented, at least in part, through an online platform configured to receives messages from and sends messages to a device of the plurality of devices, wherein, of the messages from the device, the online platform forwards at least some messages bound for a first network associated with a first messaging service to the first network and forwards at least some messages bound for a second network associated with a second messaging service to the second network;

14. The system of claim 1, wherein the request for a one of the plurality of message logs is for a message that is a group chat message.

15. The system of claim 1, wherein the history aggregation engine is further configured to timestamp entries into the aggregated message log.

16. The system of claim 1, wherein the history provisioning engine is further configured to make the aggregated message log available online.

17. The system of claim 1, wherein the history aggregation engine is further configured to store the aggregated message log in every format of the plurality of devices in association with the user profile.

18. The system of claim 1, wherein the history aggregation engine is further configured to store the aggregated message log in a generic format, the aggregated message log converted from the generic format into a format that can be displayed on at least on the plurality of devices.

19. The system of claim 1, wherein each of the plurality of devices has an associated message log of the plurality of message logs.

20. A system comprising:

means for identifying a plurality of devices in association with a user profile;

means for receiving communications from the plurality of devices bound for a respective plurality of networks;

means for forwarding the communications from a server to the respective plurality of networks;

means for creating at the server a plurality of message logs from the communications for respective ones of the plurality of devices;

means for aggregating at the server the plurality of message logs to create an aggregated message log;

means for receiving at the server a request for one of the plurality of message logs from a respective one of the plurality of devices;

means for compiling at the server at least a portion of the aggregated message log, including a portion of at least a sub-plurality of the plurality of message logs, into a format suitable for display on a device associated with the requested message log;

means for providing from the server the at least a portion of the aggregated message log in response to the request.