WO2009045560A2

WO2009045560A2 - System and method for dispatching flexible content podcast files

Info

Publication number: WO2009045560A2
Application number: PCT/US2008/059588
Authority: WO
Inventors: Jay Rifkin; Matthew Stuart
Original assignee: Digicorp, Inc.
Priority date: 2007-04-06
Filing date: 2008-04-07
Publication date: 2009-04-09
Also published as: WO2009045560A3

Abstract

Enables users to dispatch flexible content based on contextual information that may dynamically change after podcast creation time. Allows creation of a podcast or any other type of executable media package and monetization of the podcast thru advertising or other media where compensation is based on the viewing of or actions taken with respect to that media. The podcast is generated via a content creation interface configured to flexibly interchange portions of the content based on contextual or requested requirements. This allows for advertisements based on date, geographic location, weather, etc., to be dynamically included in the podcast after time of podcast creation. Utilizes dynamically filled placeholders in tracks added to a podcast to obtain flexible content. Video, audio, image, text or any other form of ad may be dynamically interleaved into the podcast during playback.

Description

PCT PATENT APPLICATION

SYSTEM AND METHOD FOR DISPATCHING FLEXIBLE CONTENT

PODCAST FILES

INVENTORS:

Jay RIFKIN

Matthew STUART

RC.

LOS ANGELES - 530 S. Lake Ave., Ste 422 Pasadena, Ca 91101 SAN DIEGO - 7910 Ivanhoe Ave., Ste. 325 La Jolla, Ca 92037 BACKGROUND OF THE INVENTION

FIELD OF THE INVENTION

M I Embodiments of the invention relate to the field of computer software and hardware systems. More particularly but not by way of limitation, embodiments of the invention are directed to a system and method dispatching flexible content podcast files wherein the flexible content may be dynamically selected based on contextual information that may not be available at podcast creation time.

DESCRIPTION OF THE RELATED ART

[0002] Modern communication systems provide an efficient mechanism for rapidly communicating data to a universe of multiple recipients. Giving users such capabilities has dramatically changed existing distribution systems for digital media. Radio and television for instance are becoming replaced by other technologies. In a prior era music was distributed in the form of Compact Discs (CDs) and made available to consumers via physical storefronts or simply played to customers on radio stations. The digital data stored on these CDs remained largely undistributed across computer networks because doing so was overly complex and largely impractical due to low bandwidth network connections and large file sizes required to maintain a relatively good level of audio quality. The advent of compressed file formats for audio data such as the MPEG Audio Layer 3 format (commonly referred to as MP3) resulted in smaller file sizes and thereby eased the constraints that previously prevented the distribution of music across computer networks. The smaller files sizes are a result of the way data is stored in the MP3 file (as pulse-code modulation-encoded (PCM) audio data where portions that are considered less important to human hearing are discarded). Other audio data formats such as Advanced Audio Coding (AAC) which is also known as MPEG-2 Part 7 also provide a compressed format for distributing music files.

|CKHO] Existing applications allow consumers to encode audio data into the forementioned formats and other compressed file formats. As such, music sharing has become significantly more commonplace as users may now email or share music data across a computer network. Systems such as Napster, Kazza and Grokster which in essence provide users with a way to share music stored on one computer with users on another computer. Such systems are referred to as peer-to-peer systems (P2P). A pure P2P network is a network that relies on the computer power and bandwidth of each computer / peer that is connected to the network. A P2P network does not have the notion of clients or servers but has each peer function as both a client and a server. This model of network arrangement differs from the client-server model where communication is usually to and from a central server. Peer-to-peer architecture embodies one of the key technical concepts of the Internet, described in the first internet Request for Comments, "RFC 1, Host Software." More recently, the peer-to-peer concept achieved wide spread recognition in the general public in the context of the absence of central indexing servers in architectures used for exchanging multimedia files such as audio data

The popularity of peer-to-peer systems, which in the past offered the lure of free music notwithstanding had legal issues about the legality of such distribution, led to more commercially acceptable alternatives such as Apple Computer's ITUNES®. Music distribution systems such as Apple Computer's ITUNES® system brought legitimacy to a form of distribution that was once viewed negatively by the entertainment industry. Using data distribution systems such as ITUNES® users can now purchase and download music and videos of their liking with a few simple mouse clicks. Another option that users have for obtaining music is to receive a subscription feed of automatically delivered audio or video content. These subscription feeds are accomplished using either Really Simply Syndication (RSS) or Atom syndication for listening on mobile devices and personal computers and are called podcasts usually featuring audio or video versions of a show, lesson or any other type of periodic broadcast. Subscribers to a podcast typically receive updates at sporadic or planned intervals such as daily, weekly, etc. There are also podcast networks that feature multiple shows on the same feed. Podcasting is about giving users customization and control over the audio and video data the user desires. In essence the goal in podcasting is to create audio or video content for an audience that wants to listen to the content when they want, where they want and how they want.

[0005] As devices such as the IPOD® and other MP3 type players become increasingly popular distribution mechanisms such as podcasting must be become more sophisticated to overcome current limitations. Current tools for monetizing podcasts or other RSS feeds are inefficient in that once the podcast is generated the file is inflexible with respect to inserting or otherwise modifying or updating the podcast to contain media that differs from the time of original authorship. Another problem that arises with current podcast solutions is that there is no easily usable way to alter or "flex" the content based on contextual feedback such as the geographic location where playback is occurring or other audience characteristics such a demographic or using any other dynamic variable available after podcast creation time. To overcome at least the problems stated above, there is a need for a system and method for dispatching flexible content podcast files, wherein the content is based on contextual playback information.

BRIEF SUMMARY OF THE INVENTION

[0006] Embodiments of the invention enable a system and method for dispatching flexible content podcast files. Additionally, the system enables the creation of the podcast from user specified media such as video and/or audio files, or any other type of media. The system further enables the monetization of podcasts thru tracking of interaction with flexible content such as advertising, for example wherein compensation is based on the viewing of or actions taken with respect to that media. The flexible content may be dynamically selected based on contextual information such as for example the IP address of a end user's media playback device, the geographic location of a end user, the date and/or time, the weather or any other parameter that may or may not be known at the podcast creation time. Distribution of a podcast created with one or more embodiments of the invention is achieved using any network system that allows client playback devices to obtain and view the contents of the podcast including flexible content.

[0007] The term podcast is used herein for purposes of example but readers should note that the invention is applicable to any assemblage of media that is capable of playback and that as such the term podcast should be given is broadest construction in the sense that it defines any set of media files capable of playback. Hence, although the term podcast is used extensively in the remaining sections, the term applies to any playable media files or file formats whatsoever. 181 One or more embodiments of the invention are implemented by enabling approval of a publisher, creating a user account and presenting a content creation interface. The content creation interface allows for the creation of a podcast file configured to dynamically play flexible content based on contextual or requested requirements. Context information may be based on dynamic information not necessarily available at the time of podcast creation. Embodiments of the invention also provide functionality that allows for a publisher to edit the media to include name, artist, comments, or any other type of information that is to be encoded with the media. The system may utilize media in any desired format for example a format with defined size, codec, bit rate and/or file format and adds tags or placeholders and add media elements, i.e., tracks to the media. Once such format that embodiments of the invention may utilize is QUICKTIME® media format.

[0009] The podcast may, for instance, be associated with a pre-tagged inventory of advertisements accessed from an ad pool. The podcast may also be associated with other information that is related to a specific set of context display parameters that are context specific. An advertisement whether in video, image, text or any other form is an example of the type of flexible content that may be added or interleaved into the podcast during playback.

S 00101 One or more embodiments of the invention do not transcode an incoming media file. Embodiments may also reject non-supported media file types, (or optionally transcode them to a standard format in other embodiments). Hence if a publisher uploads a file of a given type with particular characteristics, e.g., 64kHz audio, then the resulting media file configured for flexible content is generally retains the 64kHz audio format. In one or more embodiments of the invention a media element is added to the media to allow for publisher specific ads to be presented with the media. A media element may for example be a "track" in a QUICKTIME® file. The process of combining media and media elements is also known as "muxing". Muxing rules for combining media and media elements or tracks for example may include how often the media element refreshes, the size and length and/or location on the screen of the dynamically selected media with respect to the publisher generated media size and length and/or location.

10011 ] By adding a media element, e.g., a track, to uploaded media, the media is prepared for redirection of URLs that once the flexible content track links are filled in, for example on a client playback device. The URLs in the added tracks may utilize placeholders that allow for a client playback device to replace with a session identifier, or other unique identifier that allows for a server to determine the flexible content to be directed at the client playback device. For example, adding a track with a link to a PHP page on the server that has a placeholder value for the session identifier that is later replaced on the client device is one embodiment that allows for flexible content to stream to a client playback device via an ad pool. The track, when clicked on may send an http request to a PHP page that in this example may redirect to another image for the particular advertisement from the ad pool, based on the inserted session identifier. The server is free to decide which ad to forward based on any contextual information obtained via the client playback device link or any contextual information derived or in any other way obtained on the server.

[0012] Embodiments of the invention further provide access for the publisher to obtain statistics regarding the advertisements that have been served, and allow the publisher to track the amount of money earned as a result of the advertisements. The publisher can also modify the advertisements available via the media element without regenerating the publisher content again using embodiments of the method enabled herein. The system also enables advertisers to log into the system to track their advertisement campaigns and obtain the impressions, clicks and conversions that have occurred. The system also allows the advertisers to select which publishers or groups of publishers to make certain advertisement campaigns available to as well.

[0013] Server side scripts and/or client side scripts may be used to dynamically modify the placeholders for flexible content URLs. Regardless of the location of the modification of the placeholder, the flexible content is delivered to the client playback device. The flexible content may include advertisements that are generated specifically for a user based on a context category such as the client playback device IP address, geographic location, or based on the weather or temperature or time/day or any other variable available to the client or server. Randomization or playback in any desired order of any combination of ads specific to one of these context categories is thus achieved. Any other order for playing a group of advertisements to a end users is also possible. The view information related to the end user and advertisement views is logged for monetization and further analysis in one or more embodiments of the invention.

[0014] When a media element is asserted, i.e., clicked-on, then the media element accesses the server database to check the user against the database and send browser headers for the appropriate web address related to the advertisement media. One or more embodiments of the invention utilize a session number that is implemented as a 9 to 20 digit number for example that is generated by the end user's system and transmitted back to the server. In another embodiment, the session number is generated as a multiple of the value of the available system resources in bits and the current time value of seconds, i.e., between 0 and 60. The session number is a generally unique number on a per machine/session basis and any other method of generating a unique number per machine is in keeping with the spirit of the invention. The session number and the IP address of the client playback device for example may be utilized to query the server database to obtain end user specific information, for example URL information related to the advertisement currently being displayed, etc. In other embodiments of the invention, the available memory, IP address and number of seconds count are utilized to provide a unique combination that is capable of providing a unique identifier for filling a link placeholder.

I DESCRIPTION OF THE DRAWINGS

I CKI 16] The figures referred to throughout and setting forth one or more example embodiments of an innovative system and method dispatching flexible content based on contextual information are as follows:

[0017] Figure 1 is an architectural block level diagram that illustrates the components of the system as implemented in accordance with one embodiment of the invention.

[0018] Figure 2 is an embodiment of the content creation interface for creating a podcast utilizing embodiments of the system and method enabled herein.

[0019] Figure 3 is a flow chart illustrating the process as it is executed to dispatch flexible content based on one or more embodiments of the invention.

Figure 4 is a flow chart illustrating the builder or content creation interface portion of the method.

[0021 ] Figure 5 is a flow chart illustrating the dispatcher portion of the method.

[0022] Figure 6 is a flow chart illustrating interaction with various advertisement networks.

[0023] Figure 7 is a flow chart illustrating the advertisement tracker interaction.

[0024] Figure 8 is a podcast diagram showing a placeholder for requesting flexible content based on contextual information. DETAILED DESCRIPTION OF THE INVENTION

[0025] An innovative system and method for system and method for dispatching flexible content based on contextual information will now be described. In one or more embodiments of the invention the content contained in the podcasts is customizable based on context specific attributes that may not be known at the podcast creation time. In the following description numerous specific details are set forth in order to provide a more thorough understanding of embodiments of the invention. It will be apparent, however, to an artisan of ordinary skill that the description given is an example and that the present invention may be practiced without incorporating all aspects of the specific details described herein. For instance systems embodying one or more aspects of the invention can be implemented using a number of different technologies and hence the invention is not to be limited to the specific examples given herein but can also include other implementations used to accomplish the functions described herein. In some cases specific features well known to those of ordinary skill in the art have not been described in detail so as not to obscure the invention. Readers should note that although examples of the invention are set forth herein, the claims, and the full scope of any equivalents, are what define the invention.

Figure 1 is an architectural block level diagram that illustrates the components of the system as implemented in accordance with one embodiment of the invention. The basic components of the system include server 110, client playback device 112 configured to play media 114. When playing media 114, advertisements based on contextual information detected at client playback device 112 and/or at server 110 are utilized to control which advertisement, i.e., ad 102, 104, 106 or 108n is selected from ad pool 100 for playback on client playback device 112.

[0027] Embodiments of the invention provide users with an innovative way to create and distribute executable media packages such as podcasts. For instance, systems designed to implement one or more attributes of the invention are coupled to an interconnection fabric such as a computer network, represented by the lines in Figure 1 that connect server system 110, client playback device 112 and ad pool 110 for example. The computer network enables transfer of media and from a publisher for example using client playback device 112 or any other media generator to server 110. Client playback device, any other media generator and/or server 110 may each be configured to assist with the creation of an executable media package that has the flexibility described herein. In one or more embodiments a standalone client, or web interface may be utilized in creating the executable media package. In at least one case the flexible media package comprises data such as podcast data or other data obtainable via a subscription feed such as Really Simple Syndication (RSS) protocol. Client playback device 112 may utilize a software component that allows for custom playback of media 114 to allow for the local introduction of information that informs server 110 which client playback device 112 it is communicating with. Introduction of information may for example include the filling in of a placeholder in a media track with the session identifier associated with client playback device 112. Dynamically specifying a link at podcast playback time allows for the transfer of contextual information that enables flexible content targeted specifically at the end user utilizing client playback device 112.

[002§] To assemble a podcast the content provider utilizes a content creation interface such as the one depicted at Figure 2. Using the content creation interface 200 the user identifies the content that is to make-up one or more aspects of the podcast and requests that a podcast be assembled. In this figure, publisher information, payment information, site information and category information areas enable the system to accept input for generation and monetization of a podcast that is to have flexible content associated with it. Backend systems generate the podcast using a process that when finalized presents the podcast to the user who may then post it at a location of the users choosing. In the example shown at Figure 2 media for the podcast may be provided using any type of interface component and the podcast is created when the user initiates the creation process via any user interface component. Those of ordinary skill will recognize that various types of computer interfaces would suffice for purposes of accomplishing the stated functionality and that the invention is by no means limited to such interface specifics. The finished podcast may be presented to the user via any type of user interface component, for example such as a media player. The publisher or an end user may download the podcast and make it available to others as desired. Users such as content providers, publishers and other users wishing to monetize their podcast (s) may utilize one or more embodiments of the invention to assemble a podcast and then manage the revenue driving aspects of the podcast. £91 Figure 3 is a flow chart illustrating the process as it is executed to dispatch flexible content based on one or more embodiments of the invention. The content owner, for example a publisher, creates an audio/video media file at 301. Text based media are also publishable utilizing embodiments of the invention. The media is uploaded to a host service, e.g., a server at 302, for example utilizing a computer network or any other type of connection fabric. A feed is created at 303 that includes the original media and any placeholder URL substrings in any added flexible content tracks. The podcast is posted at 304, for example on a website or any other location where a client playback device may access it. An end user, e.g., consumer downloads a software component configured to play the custom podcast at 305 and plays the podcast at 306.

[003Oj Figure 4 is a flow chart illustrating the builder or content creation interface portion of the method. In this figure, the content creation interface, e.g., builder software component is utilized to obtain media via upload and insert tags into the media that are playable by the client playback device hosted software component. The builder enables the user to download the modified file for use in step 301.

[0031] Figure 5 is a flow chart illustrating the dispatcher portion of the method. The dispatcher is utilized at 501 to obtain an advertisement from an ad network which may be part of an ad pool for example. The ad requested may utilize contextual information to dynamically select the proper ad to utilize. Figure 6 is a flow chart illustrating interaction with various advertisement networks. Specifically, when the consumer plays the media via the software component on the client playback device at 306 and the dispatcher requests an ad from ad network 601, the proper ad as determined by any combination of contextual information provided is then returned to the software component at 306.

[0032] Figure 7 is a flow chart illustrating the advertisement tracker interaction. The dispatcher at 501 saves information related to the ads viewed, clicked on, etc., via ad tracker 701 which is also utilized to collect and distribute metadata associated with the ads that have been utilized.

133] In one scenario, a user requests to view a podcast via an embodiment of the invention. The IP address and a unique session identifier are transferred to the server. The server presents a banner in a media element, e.g., track associated with the podcast and associated with the publisher, IP address and unique session identifier. When the client clicks on the banner associated with a podcast, the link from the track is filled with the session identifier of the playback device and the http request associated with the link is transmitted to the server. In one or more embodiments, the link points to a PHP page for dynamic http generation. The server returns a redirection link and/or http header that points to the image associated with the banner and logs the view information for later use. Any modification of the podcast by adding a track with a dynamically filled placeholder for ad redirection and tracking of ad viewing is in keeping with the spirit of the invention.

[0034] While the invention herein disclosed has been described by means of specific embodiments and applications thereof, numerous modifications and variations could be made thereto by those skilled in the art without departing from the scope of the invention set forth in the claims.

Claims

CLAIMSWhat is claimed is:

1. A system for dispatching flexible content podcast files comprising: a server configured to add a track to a podcast wherein said track comprises a placeholder for a session identifier;

a client software component having client software computer readable program code embodied in a computer usable memory medium on an end user playback device where said computer readable program code is configured to play said podcast obtained from said server, insert said session identifier into said placeholder;

said server further configured to instruct an ad pool to provide an advertisement based on session identifier and contextual information and transmit a redirection link to said advertisement;

said client software component further configured to receive said redirection link and play flexible content obtained from said ad pool on said end user playback device; and,

said server further configured to collect advertisement viewing information based on said session identifier inserted into said placeholder.

2. The system of claim 1 wherein said server is further configured to calculate a payment for a publisher who created said podcast based on said advertisement viewing information.

3. The system of claim 1 wherein an owner of said server is paid for said advertisement based on said advertisement viewing information.

4. The system of claim 1 wherein said track further comprises a link which comprises said placeholder.

5. The system of claim 1 wherein said track further comprises a link which comprises said placeholder and wherein said client playback device alters a portion of said placeholder.

6. The system of claim 1 wherein said track further comprises a link which comprises said placeholder and wherein said server alters a portion of said placeholder.

7. The system of claim 1 wherein said client software component is configured to playback a standard media file format.

8. The system of claim 1 wherein said session identifier comprises a time value.

9. The system of claim 1 wherein said session identifier comprises a value specific to said client playback device.

10. The system of claim 1 wherein said placeholder further comprises said contextual information.

11. The system of claim 1 wherein said server comprises said contextual information.

12. The system of claim 1 wherein said server allows a publisher to add a comment to said podcast.

13. The system of claim 1 wherein said server allows a publisher to add a artist name to said podcast.

14. The system of claim 1 wherein said context information includes geographic location.

15. The system of claim 1 wherein said context information includes time related information.

16. The system of claim 1 wherein said context information includes weather related information.

17. The system of claim 1 wherein advertisement from said ad pool is delivered in a randomized order.

18. A system for dispatching flexible content podcast files comprising: a server configured to add a track to a podcast wherein said track comprises a placeholder for a session identifier;

said server further configured to instruct an ad pool to provide an advertisement based on session identifier and contextual information and transmit a redirection link to said advertisement; said client software component further configured to receive said redirection link and play flexible content obtained from said ad pool on said end user playback device;

said server further configured to collect advertisement viewing information based on said session identifier inserted into said placeholder; and,

said server configured to calculate a payment for a publisher who created said podcast based on said advertisement viewing information.

19. In a computer system, a method for dispatching flexible content podcast files comprising: inserting a track in a podcast wherein said track comprises a placeholder for a session identifier;

playing said podcast on a client playback device and inserting said session identifier into said placeholder;

instructing an ad pool to provide flexible content comprising an advertisement based on said session identifier and contextual information and transmitting a redirection link to said advertisement; and,

receiving said redirection link and playing said flexible content from said ad pool; and,

collecting advertisement viewing information based on said session identifier.

20. The method of claim 19 further comprising: calculating a payment for a publisher who created said podcast based on said advertisement viewing information.