IP Library Granted Patent US 8,019,892
Granted Patent B2
US 8,019,892 · App. 11/415,093 · Granted Sep 13, 2011

Multi-layered enveloped method and system for push content metadata

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,019,892
App. No.
11/415,093
Granted
Sep 13, 2011
Kind
B2
Abstract

A method and system for adding processing intelligence to content payload in a dynamic content delivery architecture having at least a first processing element and a second processing element, the method having the steps of: creating a first envelope, the first envelope including content payload and second processing element metadata, the second processing element metadata adapted to be run on the second processing element; and forming a second envelope, the second envelope containing the first envelope and first processing element metadata adapted to be run on the first processing element.

Claims (45)

1. A method performed at a content provider of a dynamic content delivery architecture, the method comprising:

configuring a content payload, first metadata and second metadata in a content package consisting of nested envelopes, the second metadata being at least one of distinct and different from the first metadata; and

delivering, to a content server, the content package consisting of nested envelopes, wherein the content package consisting of nested envelopes includes:

a client envelope containing the first metadata and the content payload, the first metadata being opaque to the content server for instructing only a content client how to process the content payload upon the first metadata being extracted, at the content client, from the client envelope; and

a server envelope containing the second metadata and the client envelope, the second metadata instructing only the content server how to process at least one of the content payload and the first metadata upon the second metadata being extracted, at the content server, from the server envelope.

2. The method of claim 1 wherein:

the first metadata is configured for at least one of use and extraction by only the content client; and

wherein the second metadata is configured for at least one of use and extraction by only the content server.

3. The method of claim 2 wherein the first metadata includes information related to expiring or replacing the content payload at the content client.

4. The method of claim 2 wherein the second metadata includes information related to expiring or replacing the content payload at the content server.

5. The method of claim 3 wherein the second metadata includes information related to expiring or replacing the content payload at the content server.

6. The method of claim 1 wherein:

configuring further comprises configuring, in the content package consisting of nested envelopes, third metadata with the content payload, the first metadata and the second metadata, the third metadata being at least one of distinct and different from the first metadata, and at least one of distinct and different from the second metadata,

wherein the content package consisting of nested envelopes further includes:

a content envelope contained in the client envelope, the content envelope containing the third metadata and the content payload, wherein the third metadata is opaque to the content server and opaque to the content client for instructing an application which is registered with the content client how to process the content payload upon the third metadata being extracted from the content envelope.

7. A method of processing content at a delivery server of a dynamic content delivery architecture, the method comprising:

receiving, from a content provider, a content package consisting of nested envelopes, the content package including a client envelope contained within a server envelope, wherein the client envelope contains client metadata and a content payload, the client metadata being opaque to the delivery server for instructing only a delivery client how to process the content payload, and wherein the server envelope contains the client envelope and server metadata that 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 content payload and the client metadata;

extracting, from the server envelope, the server metadata;

using the server metadata to process at least one of: a) the client envelope; b) the content payload; and c) the client metadata such that a processed package is provided; and

delivering the processed package to the delivery client.

8. The method of claim 7 wherein the server metadata includes information related to expiring or replacing the content payload at the delivery server before the delivering.

9. The method of claim 7 further comprising receiving, from the content provider, additional metadata related to a channel associated with the content payload.

10. The method of claim 7 wherein the content package consisting of nested envelopes further includes a content envelope, and wherein the content envelope is contained within the client envelope which is contained within the server envelope, the content envelope containing application metadata for facilitating processing of the content payload only by an application that is registered with the content client.

11. A method of processing content at a delivery client of a dynamic content delivery architecture, the method comprising:

receiving, from a delivery server, a content package consisting of nested envelopes, the content package including a content envelope contained within a client envelope, wherein the client envelope contains client metadata that is opaque to the content server for instructing only the delivery client how to process the content envelope or a content payload contained in the content envelope;

extracting, from the client envelope, the client metadata;

using the client metadata to process at least one of: a) the content envelope; b) the content payload contained in the content envelope; and c) application metadata contained in the content envelope such that a processed package is provided; and

delivering the processed package to an application.

12. The method of claim 11 wherein the client metadata includes information related to expiring or replacing the content payload at the delivery client before the delivering.

13. The method of claim 11 further comprising receiving, from a content provider or from the delivery server, additional metadata related to a channel associated with the content payload.

14. A non-transitory storage medium containing instructions which cause a machine to perform a method at a content provider of a dynamic content delivery architecture, the method comprising:

configuring a content payload, first metadata and second metadata in a content package consisting of nested envelopes, the second metadata being at least one of distinct and different from the first metadata; and

delivering, to a content server, the content package consisting of nested envelopes, wherein the content package consisting of nested envelopes includes:

a client envelope containing the first metadata and the content payload, the first metadata being opaque to the content server for instructing only a content client how to process the content payload upon the first metadata being extracted, at the content client, from the client envelope; and

a server envelope containing the second metadata and the client envelope, the second metadata instructing only the content server how to process at least one of the content payload and the first metadata upon the second metadata being extracted, at the content server, from the server envelope.

15. A non-transitory storage medium containing instructions which cause a machine to perform a content processing method at a delivery server of a dynamic content delivery architecture, the method comprising:

receiving, from a content provider, a content package consisting of nested envelopes, the content package including a client envelope contained within a server envelope, wherein the client envelope contains client metadata and a content payload, the client metadata being opaque to the delivery server for instructing only a delivery client how to process the content payload, and wherein the server envelope contains the client envelope and server metadata that 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 content payload and the client metadata;

extracting, from the server envelope, the server metadata;

using the server metadata to process at least one of: a) the client envelope; b) the content payload; and c) the client metadata such that a processed package is provided; and

delivering the processed package to the delivery client.

16. A non-transitory storage medium containing instructions which cause a machine to perform a content processing method at a delivery client of a dynamic content delivery architecture, the method comprising:

receiving, from a delivery server, a content package consisting of nested envelopes, the content package including a content envelope contained within a client envelope, wherein the client envelope contains client metadata that is opaque to the content server for instructing only the delivery client how to process the content envelope or a content payload contained in the content envelope;

extracting, from the client envelope, the client metadata;

using the client metadata to process at least one of: a) the content envelope; b) the content payload contained in the content envelope; and c) application metadata contained in the content envelope such that a processed package is provided; and

delivering the processed package to an application.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
CHANGE OF NAME Recorded Feb 19, 2016
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 037861/0215 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 15, 2006
From: SHENFIELD, MR. MICHAEL
To: RESEARCH IN MOTION LIMITED
Reel/Frame 017796/0129 →