The present invention relates generally to data communication and, more particularly, to a system and method for enabling distribution and brokering of content information.
Today's broadband access to networks, such as the Internet and its subset, the World Wide Web, enables fast download and storage of content files to personal computer systems.
Typically, customers access a server, for example a content provider, select a set of content files residing on the server, possibly provide payment for the download of content files, and download the content files for local consumption. However, in this embodiment, since the content provider stores all the content files, access to the content may be slow due to network congestion or other reasons.
Alternatively, customers may download a number of content files from the server and may select from the previously downloaded content files, which are encrypted or locked using one of a number of available encryption techniques. After providing payment to the content provider, customers receive a decryption tool, for example a key for decrypting the content within the content files. This embodiment provides faster access to content, because the content is already downloaded at the customers' end. However, capacity issues, such as storage and bandwidth, may prevent content providers from using the pre-download technique, even if customers would make storage capacity available for download.
An alternate solution to the pre-download approach involves the distribution of content over a wide variety of private servers. Customers can access any one of the private servers and download the respective content files stored on the private server. However, this model cannot guarantee a revenue stream for the original content provider and cannot properly protect the copyright of the downloaded content files.
A system and method for enabling distribution and brokering of content information are described. A request to download data is transmitted to a server. Information on multiple content providers storing data obtained from the server is received. Finally, identification information for one content provider, which allowed the download of data, is transmitted to the server along with payment for the download of data.
Other features and advantages of the present invention will be apparent from the accompanying drawings and from the detailed description that follows.
The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
According to embodiments described herein, a system and method for enabling distribution and brokering of content information are described.
In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, functional, and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
Using one of a variety of network connection devices, in one embodiment, server 104 can also communicate directly with clients 102. In a particular implementation of this network configuration, a server computer 104 may operate as a web server if the World Wide Web (Web) portion of the Internet is used as wide-area network 100. Using the Hyper Text Transfer Protocol (HTTP) and the Hyper text Markup Language (HTML) across a network, web server 104 may communicate across the Web with a client 102. In this configuration, client 102 uses a client application program known as a web browser, such as the Netscape Navigator™ browser, published by America Online™, the Internet Explorer™ browser, published by Microsoft Corporation of Redmond, Wash., the user interface of America Online™, or the web browser or HTML translator of any other conventional supplier. Using such conventional browsers and the Web, client 102 may access graphical and textual data or video, audio, or tactile data provided by server 104. Conventional means exist by which client 102 may supply information to web server 104 through the network 100 and the web server 104 may return processed data to client 102.
In one embodiment, software application programs for implementing the present invention run on web server 104 and at least one web client 102. As illustrated in
Referring again to
In one embodiment, server database 124 within server 104, for example a server operated by a content provider, stores encrypted data, for example a plurality of encrypted content files, such as audio/video content files, which can be accessed and downloaded by multiple clients 102 via network 100. In one embodiment, the content files are encrypted using one of a number of available encryption techniques.
In one embodiment, a user activates client application 112 within client 102 to transmit a request to server 104 to download encrypted data through network 100. If server 104 can accommodate the request, server application 114 accesses server database 124 and retrieves the encrypted data. Server 104 then transmits the encrypted data to client 102. Client application 102 receives and stores the encrypted data in the client database 122.
Subsequently, client application 102 transmits a request to server 104 to download a decryption tool, for example a decryption key, configured to allow access to the encrypted data. In one embodiment, client application 112 uses browser 132 to communicate with the user and to prompt the user to provide payment information for the use of the decryption tool. After it receives the payment information, client application 112 sends an electronic payment to server 104 for the use of the decryption tool. In return, server application 114 within server 104 transmits the decryption tool to client 102.
In one embodiment, if client 102 decides to become a content provider and to allow retrieval of the encrypted data from its site, client application 112 within client 102 transmits a request to server 104 to download a distribution tool, for example a distribution key, from server 104. In one embodiment, the distribution tool identifies client 102 as a content provider, which stores encrypted data obtained from server 104 and makes encrypted data available to other clients 102. Server application 114 within server 104 accesses the server database 124 to retrieve the distribution tool and transmits the distribution tool to client 102.
In one embodiment, after the distribution tool is received from server 104, client application 112 applies the distribution tool to the encrypted data stored in client database 122 and embeds the identification information into the encrypted data. In one embodiment, the distribution tool is embedded in the encrypted data as a watermark, for example a digital watermark, using one of many known types of watermarking methods. The watermark contains identification information about server 104 and the client 102 which allows retrieval of the encrypted data from its site.
In an alternate embodiment, if client 102 decides to become a content provider and subsequently downloads the distribution tool, server 104 may also store the distribution tool and its relationship with client 102 in a list of additional content providers stored within server database 124 and may provide the distribution tool to other clients 102 requesting the same encrypted data, as described in further detail below.
In one embodiment, client 102 becomes a content provider for a predetermined period of time. After the predetermined period of time, the distribution tool expires and client application 112 within client 102 needs to send a new request to server 104 to update the distribution tool and to reinstate its status as content provider.
Alternatively, client 102 may become a content provider until it transmits a request to server 104 to be removed from the list of additional content providers stored in server database 124. In this embodiment, client application 112 transmits the request and server application 114 within server 104 accesses the server database 124 and removes the client 102 from the list of additional content providers.
In another alternate embodiment, server 104 may periodically poll each client 102, which is an additional content provider, using one of many available polling methods. Server 104 may then determine the status of each polled client 102 and may remove any client 102 that requests to be removed.
In one embodiment, if server 104 is overloaded and cannot accommodate the request received from client application 112, server application 114 accesses the server database 114 and retrieves the list of additional content providers. Server application 114 transmits information on additional content providers to client 102, for example links to the additional providers which store the encrypted data obtained from server 104 and which allow retrieval of the requested encrypted data from their sites. In one embodiment, the additional content providers are also clients 102 connected to server 104 via network 100.
In one embodiment, client 102 requesting the download of encrypted data communicates with one of the additional content providers using one of the provided links. If the accessed content provider can accommodate the request, the client application 112 of client 102 downloads the encrypted data and the embedded distribution tool, which identifies the particular content provider, and stores the encrypted data in client database 122. Client application 112 then transmits a request to server 104 to download the decryption tool for decrypting the retrieved data and provides payment for the use of the decryption tool, as described in detail above.
At the same time, in one embodiment, client application 112 communicates to server 104 identification information related to the accessed content provider, for example the distribution tool identifying the content provider. After the decryption tool is transmitted to client 102, server application 114 sends a fee to the content provider, which accommodated the request and allowed the download of encrypted data. In one embodiment, the fee is predetermined and represents a percentage of the payment for the use of the decryption tool provided by client 102.
In an alternate embodiment, if server 104 cannot accommodate the request, it may provide information on additional content providers to client 102, which may include the links to the additional providers, as well as the distribution tool associated with each additional content provider. Client 102 may use the links to connect and download encrypted data from one content provider. Once the encrypted data is downloaded, client 102 may communicate the distribution tool associated with the content provider back to server 104 for proper credit of the fee.
Having briefly described one embodiment of the network environment in which the present invention operates,
In one embodiment, computer system 200 includes a system bus 201, or other communications module similar to the system bus, for communicating information, and a processing module, such as processor 202, coupled to bus 201 for processing information. Computer system 200 further includes a main memory 204, such as a random access memory (RAM) or other dynamic storage device, coupled to bus 201, for storing information and instructions to be executed by processor 202. Main memory 204 may also be used for storing temporary variables or other intermediate information during execution of instructions by processor 202.
In one embodiment, computer system 200 also comprises a read only memory (ROM) 206, and/or other similar static storage device, coupled to bus 201, for storing static information and instructions for processor 202.
In one embodiment, an optional data storage device 207, such as a magnetic disk or optical disk, and its corresponding drive, may also be coupled to computer system 200 for storing information and instructions. System bus 201 is coupled to an external bus 210, which connects computer system 200 to other devices. In one embodiment, computer system 200 can be coupled via bus 210 to a display device 221, such as a cathode ray tube (CRT) or a liquid crystal display (LCD), for displaying information to a computer user. For example, graphical or textual information may be presented to the user on display device 221. Typically, an alphanumeric input device 222, such as a keyboard including alphanumeric and other keys, is coupled to bus 210 for communicating information and/or command selections to processor 202. Another type of user input device is cursor control device 223, such as a conventional mouse, touch mouse, trackball, or other type of cursor direction keys, for communicating direction information and command selection to processor 202 and for controlling cursor movement on display 221. In one embodiment, computer system 200 may optionally include video, camera, speakers, sound card, and many other similar conventional options.
A communication device 224 is also coupled to bus 210 for accessing remote computers or servers, such as server 104, or other servers via the Internet, for example. The communication device 224 may include a modem, a network interface card, or other well-known interface devices, such as those used for interfacing with Ethernet, Token-ring, or other types of networks. In any event, in this manner, the computer system 200 may be coupled to a number of servers 104 via a conventional network infrastructure such as the infrastructure illustrated in
At processing block 320, a decision is made whether server 104 is unable to accommodate the request. If server 104 is able to accommodate the request and to allow download of the encrypted data, then at processing block 340, encrypted data is transmitted to client 102.
Otherwise, if server 104 is unable to accommodate the request, at processing block 330, server 104 transmits information on additional content providers storing the encrypted data obtained from server 104, for example links to the content providers. In one embodiment, the additional content providers are clients 102, which have decided to become content providers and to allow other clients 102 to download encrypted data residing on their sites. In one embodiment, the information on additional content providers includes links to the content providers and a distribution tool associated with each content provider, which identifies the content provider and its relationship to server 104.
At processing block 350, server 104 receives a request from client 102 to download a decryption tool for decrypting the downloaded data. In one embodiment, server 104 also receives payment for the use of the decryption tool. Alternatively, server 104 receives the payment and identification information for the content provider, for example the distribution tool identifying the content provider, which accommodated the request and allowed the download of encrypted data.
At processing block 360, server 104 transmits the decryption tool to client 102. At processing block 370, if client 102 downloaded the encrypted data from one of the additional content providers able to accommodate the request, server 104 sends a fee to the respective content provider. In one embodiment, the fee is predetermined and represents a percentage of the payment received from client 102.
At processing block 380, if client 102 decides to become a content provider and to allow retrieval of the encrypted data residing on its site, server 104 receives a request to download a distribution tool, which identifies client 102 in future transactions. After it receives the request for the distribution tool, at processing block 390, server 104 transmits the distribution tool to client 102. Finally, in one embodiment, at processing block 395, server 104 stores the distribution tool associated with client 102.
At processing block 420, a decision is made whether content provider server 104 is unable to accommodate the request. If server 104 is able to accommodate the request, at processing block 440, client 102 receives the encrypted data.
Otherwise, if server 104 is unable to accommodate the request, at processing block 430, client 102 receives information on additional content providers storing encrypted data obtained from server 104 on their sites. In one embodiment, client 102 receives links to the additional content providers. Alternatively, client 102 may receive the links to the content providers and a distribution tool for each content provider.
At processing block 450, client 102 transmits a request to download encrypted data to one of the additional content providers able to accommodate the request. At processing block 460, client 102 receives the encrypted data and identification information from the content provider. In one embodiment, the identification information is the distribution tool identifying the content provider.
At processing block 470, client 102 transmits a request to download the decryption tool to server provider 104. In one embodiment, if server 104 provided the encrypted data, client 102 also sends payment for the use of the decryption tool. Alternatively, if one of the additional content providers provided the encrypted data, client 102 sends the payment and the identification information for the content provider, for example the distribution tool identifying the content provider, to server 104. At processing block 480, client 102 receives the decryption tool from server provider 104.
At processing block 490, if client 102 decides to become a content provider and to allow downloads of the encrypted data residing on its site, client 102 transmits a request to download a distribution tool, identifying client 102 in future transactions. Finally, at processing block 495, client 102 receives the distribution tool from server provider 104.
It is to be understood that embodiments of this invention may be used as or to support software programs executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine or computer readable medium. A machine readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine readable medium includes read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); or any other type of media suitable for storing or transmitting information.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
4745549 | Hashimoto | May 1988 | A |
4965825 | Harvey et al. | Oct 1990 | A |
5134499 | Sata et al. | Jul 1992 | A |
5223924 | Strubbe | Jun 1993 | A |
5231494 | Wachob | Jul 1993 | A |
5371551 | Logan | Dec 1994 | A |
5406626 | Ryan | Apr 1995 | A |
5457746 | Dolphin | Oct 1995 | A |
5481296 | Cragun et al. | Jan 1996 | A |
5483277 | Granger | Jan 1996 | A |
5483278 | Strubbe et al. | Jan 1996 | A |
5524051 | Ryan | Jun 1996 | A |
5534911 | Levitan | Jul 1996 | A |
5553281 | Brown et al. | Sep 1996 | A |
5563946 | Cooper et al. | Oct 1996 | A |
5590195 | Ryan | Dec 1996 | A |
5614940 | Cobbley et al. | Mar 1997 | A |
5619249 | Billock et al. | Apr 1997 | A |
5625464 | Compoint | Apr 1997 | A |
5635979 | Kostreski | Jun 1997 | A |
5638443 | Stefik et al. | Jun 1997 | A |
5699107 | Lawler et al. | Dec 1997 | A |
5740549 | Reilly et al. | Apr 1998 | A |
5748890 | Goldberg | May 1998 | A |
5751806 | Ryan | May 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5758259 | Lawler | May 1998 | A |
5786845 | Tsuria | Jul 1998 | A |
5790177 | Kallatly | Aug 1998 | A |
5790935 | Payton | Aug 1998 | A |
5797010 | Brown | Aug 1998 | A |
5798785 | Hendricks et al. | Aug 1998 | A |
5805763 | Lawler et al. | Sep 1998 | A |
5826102 | Escobar et al. | Oct 1998 | A |
5852435 | Vigneaux et al. | Dec 1998 | A |
5861881 | Freeman et al. | Jan 1999 | A |
5861906 | Dunn et al. | Jan 1999 | A |
5884056 | Steele | Mar 1999 | A |
5892900 | Ginter et al. | Apr 1999 | A |
5900905 | Shoff et al. | May 1999 | A |
5907321 | Grossman et al. | May 1999 | A |
5931908 | Gerba et al. | Aug 1999 | A |
5949954 | Young et al. | Sep 1999 | A |
5982363 | Naiff | Nov 1999 | A |
5995155 | Schindler et al. | Nov 1999 | A |
6029045 | Picco et al. | Feb 2000 | A |
6029046 | Khan et al. | Feb 2000 | A |
6064380 | Swenson et al. | May 2000 | A |
6078360 | Doornhein et al. | Jun 2000 | A |
6081533 | Laubach et al. | Jun 2000 | A |
6084581 | Hunt | Jul 2000 | A |
6144375 | Jain et al. | Nov 2000 | A |
6160570 | Sitnik | Dec 2000 | A |
6173406 | Wang et al. | Jan 2001 | B1 |
6175925 | Nardone et al. | Jan 2001 | B1 |
6177931 | Alexander et al. | Jan 2001 | B1 |
6178509 | Nardone et al. | Jan 2001 | B1 |
6182050 | Ballard | Jan 2001 | B1 |
6205550 | Nardone et al. | Mar 2001 | B1 |
6215526 | Barton et al. | Apr 2001 | B1 |
6226444 | Goldschmidt et al. | May 2001 | B1 |
6233389 | Barton et al. | May 2001 | B1 |
6236395 | Sezan et al. | May 2001 | B1 |
6237786 | Ginter et al. | May 2001 | B1 |
6253193 | Ginter et al. | Jun 2001 | B1 |
6264560 | Goldberg | Jul 2001 | B1 |
6269369 | Robertson | Jul 2001 | B1 |
6289346 | Milewski et al. | Sep 2001 | B1 |
6304714 | Krause et al. | Oct 2001 | B1 |
6310886 | Barton | Oct 2001 | B1 |
6327418 | Barton | Dec 2001 | B1 |
6338139 | Ando et al. | Jan 2002 | B1 |
6359636 | Schindler et al. | Mar 2002 | B1 |
6366296 | Boreczky et al. | Apr 2002 | B1 |
6377861 | York | Apr 2002 | B1 |
6385739 | Barton et al. | May 2002 | B1 |
6416714 | Nova et al. | Jul 2002 | B1 |
6434535 | Kupka et al. | Aug 2002 | B1 |
6434747 | Khoo | Aug 2002 | B1 |
6460036 | Herz | Oct 2002 | B1 |
6463444 | Jain et al. | Oct 2002 | B1 |
6468160 | Eliott | Oct 2002 | B2 |
6476825 | Croy et al. | Nov 2002 | B1 |
6483986 | Krapf | Nov 2002 | B1 |
6487646 | Adams et al. | Nov 2002 | B1 |
6490722 | Barton et al. | Dec 2002 | B1 |
6493878 | Kassalty | Dec 2002 | B1 |
6498895 | Young et al. | Dec 2002 | B2 |
6512837 | Ahmed | Jan 2003 | B1 |
6516467 | Schindler et al. | Feb 2003 | B1 |
6519571 | Guheen et al. | Feb 2003 | B1 |
6526577 | Knudson et al. | Feb 2003 | B1 |
6535253 | Barton et al. | Mar 2003 | B2 |
6574378 | Lim | Jun 2003 | B1 |
6584552 | Kuno et al. | Jun 2003 | B1 |
6611607 | Davis et al. | Aug 2003 | B1 |
6614987 | Ismail et al. | Sep 2003 | B1 |
6625295 | Wolfgang et al. | Sep 2003 | B1 |
6628344 | Weber | Sep 2003 | B1 |
6636273 | Weber | Oct 2003 | B1 |
6640145 | Holfberg et al. | Oct 2003 | B2 |
6642939 | Vallone et al. | Nov 2003 | B1 |
6643798 | Barton et al. | Nov 2003 | B2 |
6678389 | Sun et al. | Jan 2004 | B1 |
6697948 | Rabin et al. | Feb 2004 | B1 |
6714683 | Tian et al. | Mar 2004 | B1 |
6728713 | Beach et al. | Apr 2004 | B1 |
6748080 | Russ et al. | Jun 2004 | B2 |
6757837 | Platt et al. | Jun 2004 | B1 |
6757906 | Look et al. | Jun 2004 | B1 |
6848002 | Detlef | Jan 2005 | B1 |
6865550 | Cok | Mar 2005 | B1 |
6868403 | Wiser et al. | Mar 2005 | B1 |
7058414 | Rofheart et al. | Jun 2006 | B1 |
7123813 | Inoue | Oct 2006 | B2 |
7231669 | Leung et al. | Jun 2007 | B2 |
7359883 | Namba et al. | Apr 2008 | B2 |
7546627 | Kawai | Jun 2009 | B2 |
20010018742 | Hiraiq | Aug 2001 | A1 |
20020023230 | Bolnick et al. | Feb 2002 | A1 |
20020040439 | Kellum | Apr 2002 | A1 |
20020040475 | Yap et al. | Apr 2002 | A1 |
20020059614 | Lipsanen et al. | May 2002 | A1 |
20020083157 | Sekiguschi et al. | Jun 2002 | A1 |
20020106197 | Boyle | Aug 2002 | A1 |
20020138761 | Kanemaki et al. | Sep 2002 | A1 |
20020170068 | Rafey et al. | Nov 2002 | A1 |
20030088872 | Maissel et al. | May 2003 | A1 |
20030126432 | Tonnisson | Jul 2003 | A1 |
20030149988 | Ellis et al. | Aug 2003 | A1 |
20030154390 | Yamauchi et al. | Aug 2003 | A1 |
20030174861 | Levy et al. | Sep 2003 | A1 |
20030219127 | Russ et al. | Nov 2003 | A1 |
20030221100 | Russ et al. | Nov 2003 | A1 |
20040083377 | Wu et al. | Apr 2004 | A1 |
20040107368 | Colvin | Jun 2004 | A1 |
20040117320 | Morioka et al. | Jun 2004 | A1 |
20040117663 | Colvin | Jun 2004 | A1 |
20040177369 | Akins | Sep 2004 | A1 |
20050144641 | Lewis | Jun 2005 | A1 |
20050204392 | Na | Sep 2005 | A1 |
20050289617 | Safadi et al. | Dec 2005 | A1 |
20060212900 | Ismail et al. | Sep 2006 | A1 |
Number | Date | Country |
---|---|---|
0676756 | Oct 1995 | EP |
0726574 | Aug 1996 | EP |
0862328 | Sep 1998 | EP |
WO 8002093 | Oct 1980 | WO |
WO 9413107 | Jun 1994 | WO |
WO 9741690 | Nov 1997 | WO |
Entry |
---|
Electronic House Com, EchoStart Communications Corporation and Geocast Network Systems Align to Deliver New Personalized Interactive Broadband Services to PC Users Via Satellite, Jun. 4, 2002, http://209.6.10.99/news101600echostar.html, 3 pages. |
Lost Remote, The TV Revolution is Coming, Lost Remote TV New Media & Television Convergence News, TV News Gets (too?) Personal by Cory Bergman, Sep. 25, 2000, http://www.lostremote.com/producer/personal.html, 2 pages. |
“Automatic Constructions of Personalized TV News Programs”, Association of Computing Machinery (ACM) Multimedia Conf., 323-331 (Presented Nov. 3, 1999). |
“Metabyte Announces Personalized TV Software”, Jan. 12, 1999, 2 pages, http://www.findwealth.com/metabyte-announces-personalized-tv-software-3252. |
“TiVo brings home HBO through agreement benefiting personal television service users” Press Release, “Online!” Jan. 28, 1999, XP002154115, Retrieved from the Internet: <URL:www.tivo.com?, retrieved on Nov. 29, 2000. |
“The Wave Report”, Feb. 12, 1999, 2 pages, http://www.wave-report.com/1999—Wave—Issues/wave9016.html. |
Number | Date | Country | |
---|---|---|---|
20030028391 A1 | Feb 2003 | US |