User device agent for asynchronous advertising in time and space shifted media network

• US 20070118425A1
• Filed: 10/25/2006
• Published: 05/24/2007
• Est. Priority Date: 10/25/2005
• Status: Abandoned Application

• Current Assignee: Sony Interactive Entertainment America LLC (Sony Group Corp.)
• Original Assignee: Podbridge, Inc.
• Inventors: Yruski, Andrey, Markovetski, Roman, Navar, Murgesh
• Application Number:
  US11/588,236
• Publication Number:
  US 20070118425A1
• Time in Patent Office: Days
• US Class Current: 705/14.610
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0264 based upon schedule
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/53 using third party service providers

Abstract

A podcast system and method are provided to select and deliver media ads over a network to a user device and to insert the media ads in media content subscribed to and delivered over the network to the user device.

Claims

1. A method of associating media content with media ads comprising:

obtaining a request for a media content file directed to a network subscription feed source of the media content file;

sending the request over the network to the network subscription feed source;

receiving over the network, a media content file responsive to the request;

receiving over the network, one or more ads;

receiving over the network, first metadata indicating one or more locations in the received content file where the one or more ads may be inserted; and

inserting at least one of the one or more received ads within the received media content file consistent with the first metadata.

2. The method of claim 1,

wherein obtaining includes intercepting a request originating in a content subscription manager application and producing a revised request that directs the network subscription feed source to send the requested media content file to a prescribed network location;

and

wherein sending includes sending the revised request.

3. The method of claim 1 further including:

causing the one or more received ads to be stored by a user device before receipt of the requested media content file and before inserting of the one or more received ads therein.

4. The method of claim 1,

wherein receiving the media content file and receiving the one or more ads take place asynchronously.

5. The method of claim 1 further including:

receiving over the network, second metadata indicating ad placement rules;

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

6. The method of claim 1 further including:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify frequency with which an ad is to be inserted into the one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

7. The method of claim 1 further including:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify sequencing of ad insertion into one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

8. The method of claim 1 further including:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify criteria for expiration of one or more ads; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

9. An article of manufacture including computer readable medium encoded with program code causing a computing device to perform a process comprising:

obtaining a request for a media content file directed to a network subscription feed source of the media content file;

sending the request over the network to the network subscription feed source;

receiving over the network, a media content file responsive to the request;

receiving over the network, one or more ads;

receiving over the network, first metadata indicating one or more locations in the received content file where the one or more ads may be inserted; and

inserting at least one of the one or more received ads within the received media content file consistent with the first metadata.

10. The article of claim 9,

wherein obtaining includes intercepting a request originating in a content subscription manager application and producing a revised request that directs the network subscription feed source to send the requested media content file to a prescribed network location;

and

wherein sending includes sending the revised request.

11. The article of claim 9 wherein the process further includes:

causing the one or more received ads to be stored by a user device before receipt of the requested media content file and before inserting of the one or more received ads therein.

12. The article of claim 9,

wherein receiving the media content file and receiving the one or more ads take place asynchronously.

13. The article of claim 9 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

14. The article of claim 9 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify frequency with which an ad is to be inserted into the one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

15. The article of claim 9 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify sequencing of ad insertion into one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

16. The article of claim 9 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify criteria for expiration of one or more ads; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

17. A system to associate media content with media ads comprising:

a CPU;

data storage;

a bus interconnecting the CPU and the data storage;

wherein the data storage is encoded with program code to cause the CPU to perform a process including;

obtaining a request for a media content file directed to a network subscription feed source of the media content file;

sending the request over the network to the network subscription feed source;

receiving over the network, a media content file responsive to the request;

receiving over the network, one or more ads;

receiving over the network, first metadata indicating one or more locations in the received content file where the one or more ads may be inserted; and

inserting at least one of the one or more received ads within the received media content file consistent with the first metadata.

18. The system of claim 17,

wherein obtaining includes intercepting a request originating in a content subscription manager application and producing a revised request that directs the network subscription feed source to send the requested media content file to a prescribed network location;

and

wherein sending includes sending the revised request.

19. The system of claim 17 wherein the process further includes:

causing the one or more received ads to be stored by a user device before receipt of the requested media content file and before inserting of the one or more received ads therein.

20. The system of claim 17,

wherein receiving the media content file and receiving the one or more ads take place asynchronously.

21. The system of claim 17 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

22. The system of claim 17 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify frequency with which an ad is to be inserted into the one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

23. The system of claim 17 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify sequencing of ad insertion into one or more content files; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.

24. The system of claim 17 wherein the process further includes:

receiving over the network, second metadata indicating ad placement rules;

wherein the ad placement rules specify criteria for expiration of one or more ads; and

wherein inserting one of the one or more received ads within the received media content file includes inserting consistent with both the first metadata and the second metadata.