System, Server, and Mobile Device for Content Provider Website Interaction and Method Therefore

• US 20110231478A1
• Filed: 09/09/2010
• Published: 09/22/2011
• Est. Priority Date: 09/10/2009
• Status: Abandoned Application

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: CAMP, William N. II, WEI, Kai, HU, Xin, SHAH, Anish M., MASTER, Cyrus P., PUTTERMAN, Scott I., WHEELER, Maxon R., ROBINSON, Tony, HANGAS, Paul W., MAMITSUKA, Lien T., LEROY, Heather M., RYPINSKI, Christopher, MITRA, Christopher A., BRAHMBHATT, Milan S., SEWERYNEK, Stephen J., SAWHNEY, Sapna
• Application Number:
  US12/878,705
• Publication Number:
  US 20110231478A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

An aggregate service server, configured to communicate with a user device and a plurality of different content providers. A processor configured to obtain content from the plurality of different content providers and further configured to push the obtained content to the user device.

Claims

1. An aggregate service server, configured to communicate with a user device and a plurality of different content providers, comprising:

a processor configured to obtain content from the plurality of different content providers and further configured to push the obtained content to the user device.

2. The aggregate service server of claim 1, wherein the processor is further configured to receive a status update from the user device and to transmit the status update to a corresponding one of the plurality of content providers.

3. The aggregate service server of claim 1, further comprising:

a plurality of plug-ins, each corresponding to a respective one of the plurality of content providers and configured to transmit and receive communications from the corresponding content provider.

4. The aggregate service server of claim 3, further comprising:

a memory,

wherein the processor is further configured to receive an update from one of the plug-ins, to assign a priority to the update and to store the update and the assigned priority in the memory.

5. The aggregate service server of claim 4, wherein the processor is further configured to schedule a push to the user device based upon the assigned priority to the received update.

6. The aggregate service server of claim 5, wherein the processor is further configured to receive a request for data from the user device and is further configured to push any updates stored in the memory to the user device.

7. The aggregate service server of claim 6, wherein the request for data is a single request for updates from all of the content providers.

8. The aggregate service server of claim 4, wherein each plug-in is configured to reformat the received update into a format compatible with the user device.

9. The aggregate service server of claim 7, wherein the processor is further configured to push the received content to a plurality of user devices associated with a single account by:

monitoring the content pushed to each of the user devices; and

pushing content to each of the user devices based upon the monitoring.

10. A method of controlling communications between a client device and a plurality of content providers using an intermediate server, comprising:

receiving, by the intermediate server, an update from one of the plurality of content providers;

assigning, by the intermediate server, a priority to the received update; and

scheduling, by the intermediate server, a push of the received update to the client device based upon the assigned priority.

11. The method of claim 10, further comprising:

receiving, by the intermediate server, a single request from the client device for an update; and

pushing updates, by the intermediate server, to the client device from all of the content providers in response to the single request.

12. The method of claim 10, further comprising:

monitoring the updates that have been pushed to the client device; and

pushing updates to the user devices based upon the monitoring.

13. The method of claim 10, further comprising:

reformatting the received update into a format compatible with the client device.

14. The method of claim 10, further comprising:

periodically pushing updates to the client device.

15. The method of claim 10, further comprising:

pushing an update to the client device when the update is assigned a high priority.

16. An intermediate server, configured to communicate with a user device and a plurality of different content providers, comprising:

a memory;

a content provider processor configured to obtain updates from the plurality of different content providers and to store the updates in the memory; and

a core services processor configured to push the updates stored in memory to the user device.

17. The intermediate server of claim 16, wherein the content provider processor is further configured to reformat the obtained updates from the plurality of different content providers into a format compatible with the user device.

18. The intermediate server of claim 16, wherein the core services processor assigns a priority to the obtained updates stored in the memory.

19. The intermediate server of claim 18, wherein the core services processor schedules a push of the obtained updates stored in memory to the user device based upon the assigned priority.

20. The intermediate server of claim 16, wherein the core services processor deletes the obtained updates from the memory after the obtained updates have been pushed to the user device.