Push framework for delivery of dynamic mobile content

• US 20070260674A1
• Filed: 05/02/2006
• Published: 11/08/2007
• Est. Priority Date: 05/02/2006
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Research In Motion Limited (Blackberry Limited)
• Inventors: Shenfield, Michael
• Application Number:
  US11/415,289
• Publication Number:
  US 20070260674A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A push proxy and push client for use in a generic dynamic content delivery system the push proxy having: a content provider registration service provider interface, said service provider interface adapted to register said push proxy with content providers and to further receive channel metadata for the content providers; a channel metadata repository adapted to store said channel metadata received from the content providers; a content metadata extractor and cache module adapted to extract metadata for said push proxy from a content and metadata envelope received from the content providers, said content metadata extracting cache further adapted to cache said metadata on said push proxy; a content fragmentation module adapted to break a content and metadata envelope into segments; a deferred retrieval message store module adapted to store a content envelope or one or more segments from said content fragmentation module; a content expiry and replacement module adapted to expire content stored in the deferred retrieval message store or to replace content stored in the deferred retrieval message store; a content dependencies module adapted to provide selection of push clients to advertise a service to; a push scheduler, said push scheduler adapted to schedule the pushing of a content envelope stored in the deferred retrieval message store; and a subscription and rules module adapted to maintain a subscription between an application and the content provider and maintain a list of rules for the subscription.

Claims

1. A push proxy for use in a generic dynamic content delivery system comprising:

a content provider registration service provider interface, said service provider interface adapted to register said push proxy with content providers and to further receive channel metadata for the content providers;

a channel metadata repository, said channel metadata repository adapted to store said channel metadata received from the content providers;

a content metadata extractor and cache module, said content metadata extractor and cache module being adapted to extract metadata for said push proxy from a content and metadata envelope received from the content providers, said content metadata extracting cache further adapted to cache said metadata on said push proxy;

a content fragmentation module, said content fragmentation module adapted to break a content and metadata envelope into segments;

a deferred retrieval message store module, said deferred retrieval message store module adapted to store a content envelope or one or more segments from said content fragmentation module;

a content expiry and replacement module, said content expiry and replacement module adapted to expire content stored in the deferred retrieval message store or to replace content stored in the deferred retrieval message store;

a content dependencies module, said content dependencies module adapted to provide selection of push clients to advertise a service to;

a push scheduler, said push scheduler adapted to schedule the pushing of a content envelope stored in the deferred retrieval message store; and

a subscription and rules module, said subscription and rules module adapted to maintain a subscription between an application and the content provider and maintain a list of rules for the subscription.

2. The push proxy of claim 1, further comprising push agents to push content and metadata envelopes to a push client.

3. The push proxy of claim 1, further comprising a flow control management module, the flow control management module adapted to receive flow control messages from the push client and start or stop pushing content and metadata envelopes.

4. The push proxy of claim 1, further comprising message brokers and delivery queues to store and manage content and metadata envelopes.

5. The push proxy of claim 1, wherein the push proxy is adapted to register only one content provider.

6. The push proxy of claim 1, wherein the push proxy is adapted to register multiple content providers.

7. The push proxy of claim 1, further comprising a content storage module for storing content.

8. The push proxy of claim 1, further comprising a service administration module for administering said push proxy.

9. A push client for use in a dynamic content delivery architecture, the push client comprising:

an application registration application provider interface adapted to register applications to said push client and further adapted to receive an application manifest for said applications, said application manifest containing channel metadata;

a channel metadata repository adapted to store channel metadata received from said application;

communication means, such communication means adapted to receive a content and metadata envelope from a push proxy;

content metadata extractor and cache module, said content metadata extractor and cache module being adapted to extract metadata for said push client from said content and metadata envelope and further being adapted to cache said metadata on said push client;

a deferred retrieval manager adapted to schedule retrieval of content from the push proxy not yet received by the push client;

a content dependencies module adapted to reconstitute content previously broken into segments;

a content expiry and replacement module, said content expiry and replacement module adapted to expire content stored at said push client or to replace content stored at the push client;

an update notification block, said update notification block adapted to work with said applications to notify the applications that new content is waiting for them;

a subscription management block, said subscription management block adapted to manage subscriptions between the application and a content provider;

a pull broker adapted to pull content when required by the push client, said pull broker being driven by aid deferred retrieval manager,

wherein said push client is adapted to register generic applications and receive generic content type from the content provider.

10. The push client of claim 9, further comprising push agents to receive content and metadata envelopes from the push proxy.

11. The push client of claim 9, further comprising a flow control management module, the flow control management module adapted to send flow control messages to the push proxy to start or stop pushing content and metadata envelopes.

12. The push client of claim 9, further comprising message brokers and delivery queues to store and manage content and metadata envelopes.

13. The push client of claim 9, wherein the push client is adapted to register with only one application.

14. The push client of claim 9, wherein the push client is adapted to register with multiple applications.

15. The push client of any of claim 9, further comprising a content storage module for storing content.

16. The push client of claim 9, further comprising a service administration module for administering said push client.

17. The push client of claim 9, wherein said push client further includes a background update processing module adapted to perform background updates for applications not connected with said push client.

18. The push client of claim 9, wherein the update notification module is adapted to store content for said applications in predetermined locations.

20. The push client of any of claim 9, wherein the update notification sends the content and metadata envelope to the applications.

19. The push client of claim 19, wherein the update notification sends a message to the client application that data has been stored in the predetermined locations.