Aggregating data from a plurality of data sources
US-9105000-B1 · Aug 11, 2015 · US
US9680761B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9680761-B2 |
| Application number | US-201414459878-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 14, 2014 |
| Priority date | Aug 14, 2014 |
| Publication date | Jun 13, 2017 |
| Grant date | Jun 13, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some implementations, state messages can be queued at a server device for transmission to a disconnected client device when the client device reconnects to the server device. To conserve resources, queued state messages can be consolidated, combined and/or deleted.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, at a chat server within a synchronized content management system, a new state message including state information for a chat state taking place within a chat application associated with the synchronized content management system at a first client device; storing, at the synchronized content management system, the new state message in a message queue within the chat server that stores a plurality of state messages; determining, at the synchronized content management system, a state message type for the new state message; identifying two or more state messages from the plurality of state messages in the message queue having the state message type; consolidating the two or more state messages that have the state message type into a single state message; and storing the single state message in the message queue. 2. The method of claim 1 , wherein the consolidating comprises: determining that at least one of the identified two or more state messages have a replaceable state message type; and deleting at least one of the identified two or more state messages that are replaceable, keeping only the most recently received of the replaceable state message types when the replaceable state message types refer to a particular attribute of a particular object. 3. The method of claim 1 , wherein the consolidating comprises: combining two or more messages in the message queue when the one or two or more messages refer to a particular attribute of different objects. 4. The method of claim 1 , wherein the message queue has a first size before the consolidating and a second size after the consolidating and wherein the second size is smaller than the first size. 5. The method of claim 1 , further comprising transmitting the single message to a second client device. 6. A non-transitory computer-readable medium including one or more sequences of instructions which, when executed by one or more processors, causes: receiving, at a chat server within a synchronized content management system, a new state message including state information for a chat state taking place within a chat application associated with the synchronized content management system at a first client device; storing, at the synchronized content management system, the new state message in a message queue within the chat server that stores a plurality of state messages; determining, at the synchronized content management system, a state message type for the new state message; identifying two or more state messages from the plurality of state messages in the message queue having the state message type; consolidating the two or more state messages that have the state message type into a single state message; and storing the single state message in the message queue. 7. The non-transitory computer-readable medium of claim 6 , wherein the instructions that cause consolidating comprise instructions that cause: determining that at least one of the identified two or more state messages have a replaceable state message type; and deleting at least one of the identified two or more state messages that are replaceable, keeping only the most recently received of the replaceable state message types when the replaceable state message types refer to a particular attribute of a particular object. 8. The non-transitory computer-readable medium of claim 6 , wherein the instructions that cause consolidating comprise instructions that cause: combining two or more messages in the message queue when the one or two or more messages refer to a particular attribute of different objects. 9. The non-transitory computer-readable medium of claim 6 , wherein the message queue has a first size before the consolidating and a second size after the consolidating and wherein the second size is smaller than the first size. 10. The non-transitory computer-readable medium of claim 6 , wherein the instructions cause transmitting the single state message to a second client device. 11. A system comprising: one or more processors; and a non-transitory computer-readable medium including one or more sequences of instructions which, when executed by the one or more processors, causes: receiving, at a chat server within a synchronized content management system, a new state message including state information for a chat state taking place within a chat application at a first client device; storing, at the synchronized content management system, the new state message in a message queue within the chat server that stores a plurality of state messages; determining, at the synchronized content management system, a state message type for the new state message; identifying two or more state messages from the plurality of state messages in the message queue having the state message type; consolidating the two or more state messages that have the state message type into a single state message; and storing the single state message in the message queue. 12. The system of claim 11 , wherein the instructions that cause consolidating comprise instructions that cause: determining that at least one of the identified two or more state messages have a replaceable state message type; and deleting at least one of the identified two or more state messages that are replaceable, keeping only the most recently received of the replaceable state message types when the replaceable state message types refer to a particular attribute of a particular object. 13. The system of claim 11 , wherein the instructions that cause consolidating comprise instructions that cause: combining two or more messages in the message queue when the one or two or more messages refer to a particular attribute of different objects. 14. The system of claim 11 , wherein the message queue has a first size before the consolidating and a second size after the consolidating and wherein the second size is smaller than the first size. 15. The system of claim 11 , wherein the instructions cause transmitting the single state message to a second client device.
Electricity · mapped topic
Real-time or near real-time messaging, e.g. instant messaging [IM] · CPC title
Altering the ordering of packets in an individual queue · CPC title
Dynamic adaptation of the packet size · CPC title
Mailbox-related aspects, e.g. synchronisation of mailboxes · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.