Dynamic syndicated content delivery system and method

• US 8,024,452 B2
• Filed: 05/02/2006
• Issued: 09/20/2011
• Est. Priority Date: 05/02/2006
• Status: Expired due to Fees

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: Smith, Christopher, Shenfield, Michael
• Primary Examiner(s): Etienne; Ario
• Assistant Examiner(s): KIM, HEE SOO
• Application Number:
  US11/415,288
• Publication Number:
  US 20070260673A1
• Time in Patent Office: 1,967 Days
• Field of Search: 709/224, 709/246
• US Class Current: 709/224
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/2876 Pairs of inter-processing entities at each side of the network, e.g. split proxies
• 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/5681 Pre-fetching or pre-delivering data based on network characteristics
• 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
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

A dynamic syndicated content delivery system and method, the system having: a push proxy, the push proxy having: a deferred retrieval message store, the deferred retrieval message store adapted to storing deferred content for future delivery; a push agent, the push agent adapted to push content; and a push scheduler, the push schedule adapted to communicate with the push agent to schedule the pushing of content and further adapted to monitor a wireless network for network conditions; a push client, the push client having: a client push agent, the client push agent adapted to communicate with the push agent of the push proxy; a content pull broker, the content pull broker adapted to communicate with the deferred retrieval message store of the push proxy; a deferred retrieval manager, the deferred retrieval manager adapted to communicate with the content pull broker and the client push agent to pull content, the deferred retrieval manager further adapted to monitor a network and instruct the content pull broker to pull the content if the network conditions are favorable for receiving the deferred content; and a network status monitor adapted to monitor the status of the network; and the wireless network.

Claims

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

receiving, from a content provider, a package consisting of nested envelopes, the nested envelopes being;

a client envelope including a payload and client metadata; and

a server envelope containing the client envelope and server metadata, wherein the client metadata is opaque to the delivery server for instructing only a delivery client how to process the payload, and wherein the server metadata is distinct or different from the client metadata, the server metadata instructing only the delivery server how to process at least one of the client envelope, the payload and the client metadata;

extracting the server metadata from the package consisting of nested envelopes, the server metadata specifying network preferences for delivery of the client envelope to the delivery client; and

delivering, to the delivery client, the client envelope containing the payload and the client metadata if network conditions correspond to the network preferences from the server metadata.

2. The method of claim 1, wherein said network preferences are based on a price of delivery for various network types.

3. The method of claim 1, wherein said network preferences are based on bandwidth restrictions for various network types.

4. The method of claim 1, wherein said server metadata specifies a rule regarding whether delivery is acceptable during roaming.

5. The method of claim 1, wherein said server metadata specifies acceptable network types.

6. The method of claim 1 wherein the client metadata contained in the client envelope is configured for extraction and use by only the delivery client.

7. The method of claim 6 wherein the client envelope further includes metadata for extraction and use by only an application which is registered with the delivery client.

8. A method performed by a delivery client, the method comprising:

receiving, from a delivery server, a package consisting of nested envelopes, the nested envelopes being;

a content envelope including a payload; and

a client envelope containing the content envelope and client metadata, wherein the client metadata is opaque to the delivery server for instructing only the delivery client how to process the content envelope or the payload;

extracting the client metadata from the package consisting of nested envelopes, the client metadata specifying network preferences for the delivery client to obtain content; and

using the client metadata to request content from the delivery server according to the network preferences.

9. The method of claim 8, wherein said network preferences are based on a price of delivery for various network types.

10. The method of claim 8, wherein said network preferences are based on bandwidth restrictions for various network types.

11. The method of claim 8, wherein said client metadata specifies a rule regarding whether delivery is acceptable during roaming.

12. The method of claim 8, wherein said client metadata specifies acceptable network types.

13. The method of claim 8 wherein the content envelope further includes metadata for extraction and use by only an application which is registered with the delivery client.

14. A method performed by a content provider, the method comprising:

packaging, at the content provider, first metadata with a content envelope that includes a payload such that a delivery client envelope is formed containing the first metadata and the content envelope, the first metadata being opaque to a delivery server for extraction from the delivery client envelope only by a delivery client and for use by only the delivery client; and

nesting, at the content provider, the delivery client envelope in second metadata such that a delivery server envelope containing the second metadata and the delivery client envelope is formed, the second metadata being opaque to the delivery client for extraction from the delivery server envelope only by the delivery server and for use by only the delivery server,

wherein the delivery server envelope contains the delivery client envelope, and the delivery client envelope contains the content envelope, and

wherein at least one of the first metadata and the second metadata specifies preferences which facilitate selection of a network for delivery of content.

15. The method of claim 14 wherein the first metadata is configured for use by only the delivery client to facilitate processing of the content envelope, and wherein the second metadata is configured for use by only the delivery server to facilitate processing of the delivery client envelope.

16. The method of claim 14 wherein at least one of the first metadata or the second metadata includes information related to expiring or replacing the payload before the payload is consumed by an application registered with the delivery client.

17. The method of claim 14 wherein the content envelope further includes third metadata with the payload, the third metadata being configured to provide instructions regarding processing of the payload to an application that is registered with the delivery client.

18. A non-transitory storage medium containing instructions which cause a machine to perform a delivery server method comprising:

receiving, from a content provider, a package consisting of nested envelopes, the nested envelopes being;

a client envelope including a payload and client metadata; and

a server envelope containing the client envelope and server metadata, wherein the client metadata is opaque to the delivery server for instructing only a delivery client how to process the payload, and wherein the server metadata is distinct or different from the client metadata, the server metadata instructing only the delivery server how to process at least one of the client envelope, the payload and the client metadata;

extracting the server metadata from the package consisting of nested envelopes, the server metadata specifying network preferences for delivery of the client envelope to the delivery client; and

delivering, to the delivery client, the client envelope containing the payload and the client metadata if network conditions correspond to the network preferences from the server metadata.

19. A non-transitory storage medium containing instructions which cause a machine to perform a delivery client method comprising:

receiving, from a delivery server, a package consisting of nested envelopes, the nested envelopes being;

a content envelope including a payload; and

a client envelope containing the content envelope and client metadata, wherein the client metadata is opaque to the delivery server for instructing only the delivery client how to process the content envelope or the payload;

extracting the client metadata from the package consisting of nested envelopes, the client metadata specifying network preferences for the delivery client to obtain content; and

using the client metadata to request content from the delivery server according to the network preferences.

20. A non-transitory storage medium containing instructions which cause a machine to perform a content provider method comprising:

packaging, at the content provider, first metadata with a content envelope that includes a payload such that a delivery client envelope is formed containing the first metadata and the content envelope, the first metadata being opaque to a delivery server for extraction from the delivery client envelope only by a delivery client and for use by only the delivery client; and

nesting, at the content provider, the delivery client envelope in second metadata such that a delivery server envelope containing the second metadata and the delivery client envelope is formed, the second metadata being opaque to the delivery client for extraction from the delivery server envelope only by the delivery server and for use by only the delivery server,

wherein the delivery server envelope contains the delivery client envelope, and the delivery client envelope contains the content envelope, and

wherein at least one of the first metadata and the second metadata specifies preferences which facilitate selection of a network for delivery of content.