System and Method for Content Messaging

• US 20170118262A1
• Filed: 10/21/2016
• Published: 04/27/2017
• Est. Priority Date: 10/23/2015
• Status: Active Grant

• Current Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Original Assignee: Kodiak Networks (Motorola Solutions, Inc.)
• Inventors: Patel, Krishnakant M., Ayyasamy, Ravi, Chandana, Pratap, Dash, Debabrata, Setti, Bharat Ram, Gaffar, Sayyad
• Granted Patent: US 10,630,742 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/285 Clustering or classification
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/06 Message adaptation to terminal or network requirements
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 65/4061 Push-to services, e.g. push-to-talk or push-to-video
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 84/042 Public Land Mobile systems, e.g. cellular systems

Abstract

A system and method for content messaging includes observing, by the server, synchronization of a database cluster accessible to the server with a first local database at a first client, the database cluster including a message after the synchronization, the message including content and instructions for processing the content, and processing, by the server, the content of the message according to the instructions for processing the content, in response to observing the synchronization.

Claims

1. A method, by a server, for content delivery, the method comprising:

observing, by the server, synchronization of a database cluster accessible to the server with a first local database at a first client, the database cluster including a message after the synchronization, the message including content and instructions for processing the content; and

processing, by the server, the content of the message according to the instructions for processing the content, in response to observing the synchronization.

2. The method of claim 1, further comprising:

detecting, by the server, availability of the message in the database cluster after the synchronization of the message.

3. The method of claim 1, wherein the synchronization of the message is triggered by an event at the first client causing the first client to create or update the content of the message.

4. The method of claim 1, wherein processing the content of the message comprises:

invoking, by the server, one or more services at the server according to the instructions for processing the content.

5. The method of claim 4, wherein processing the content of the message further comprises:

sending, by the server, one or more notifications to one or more second clients according to an expected result of the one or more services, the one or more notifications not including the message.

6. The method of claim 5, further comprising:

observing, by the one or more second clients, synchronization of the message from the database cluster into second local databases at the one or more second clients.

7. The method of claim 6, further comprising:

observing, by the server, synchronization of a delivery receipt for the message from the second local database into the database cluster; and

notifying, by the server, the first client that the delivery receipt for the message is available for synchronization from the database cluster into the first local database, in response to observing the synchronization of the delivery receipt.

8. The method of claim 1, wherein the content of the message comprises a metadata document and an attachment content document, and wherein the observing the synchronization of the database cluster comprises:

observing, by the server, the synchronization of the metadata document from the first local database into the database cluster;

after the observing the synchronization of the metadata document, processing the metadata document; and

observing, by the server, synchronization of the attachment content document from the first local database into the database cluster.

9. The method of claim 8, further comprising:

observing, by a second client, synchronization of the metadata document from the database cluster into a second local database at a second client;

receiving, by the server, a request for the attachment content document from the second client; and

observing, by the second client, synchronization of the attachment content document from the database cluster into the second local database, in response to receiving the request for the attachment content document.

10. The method of claim 8, wherein the metadata document is synchronized over a first connection, and the attachment content document is synchronized over a second connection.

11. The method of claim 10, wherein the first connection and the second connection are different connections.

12. The method of claim 10, wherein the first connection and the second connection are the same connection.

13. The method of claim 1, wherein the content includes text, an image, a video, location information, a file or a combination thereof.

14. A server for content delivery, the server comprising:

a processor; and

a computer readable storage medium storing programming for execution by the processor, the programming including instructions for;

observing synchronization of a database cluster accessible to the server with a first local database at a first client, the database cluster including a message after the synchronization, the message including content and instructions for processing the content; and

processing the content of the message according to the instructions for processing the content, in response to observing the synchronization.

15. The server of claim 14, wherein the programming further includes instructions for:

detecting availability of the message in the database cluster after the synchronization of the message.

16. The server of claim 14, wherein the synchronization of the message is triggered by an event at the first client causing the first client to create or update the content of the message.

17. The server of claim 14, wherein the instructions for processing the content of the message includes instructions for:

invoking one or more services at the server according to the instructions for processing the content.

18. The server of claim 17, wherein the instructions for processing the content of the message further includes instructions for:

sending, by the server, one or more notifications to one or more second clients according to an expected result of the one or more services, the one or more notifications not including the message.

19. The server of claim 18, wherein the instructions for processing the content of the message further includes instructions for:

observing synchronization of the message from the database cluster into second local databases at the one or more second clients.

20. The server of claim 19, wherein the programming further includes instructions for:

observing synchronization of a delivery receipt for the message from the second local database into the database cluster; and

notifying the first client that the delivery receipt for the message is available for synchronization from the database cluster into the first local database, in response to observing the synchronization of the delivery receipt.

21. The server of claim 14, wherein the content of the message comprises a metadata document and an attachment content document, and wherein the instructions for observing synchronization of the database cluster includes instructions for:

observing synchronization of the metadata document from the first local database into the database cluster;

after the observing the synchronization of the metadata document, processing the metadata document; and

observing synchronization of the attachment content document from the first local database into the database cluster.

22. The server of claim 21, wherein the programming further includes instructions for:

observing synchronization of the metadata document from the database cluster into a second local database at a second client;

receiving, by the server, a request for the attachment content document from the second client; and

observing synchronization of the attachment content document from the database cluster into the second local database, in response to receiving the request for the attachment content document.

23. The server of claim 21, wherein the metadata document is synchronized over a first connection, and the attachment content document is synchronized over a second connection.

24. The server of claim 23, wherein the first connection and the second connection are different connections.

25. The server of claim 23, wherein the first connection and the second connection are the same connection.

26. The server of claim 14, wherein the content includes text, an image, a video, location information, a file or a combination thereof.

27. A method, by a client, for content delivery, the method comprising:

creating, by the client, a message, the message including content and instructions for processing the content;

storing, by the client, the message in a first local database at the client; and

synchronizing, by the client, the first local database at the client with a database cluster at a server, the database cluster including the message after the synchronizing.

28. The method of claim 27, wherein the synchronizing the message is triggered by an event at the client causing first client to create or update the content of the message.

29. The method of claim 27, wherein the creating the message comprises:

splitting the message into a metadata document and an attachment content document.