Personalized broadcast system

Information

  • Patent Grant
  • 8990850
  • Patent Number
    8,990,850
  • Date Filed
    Friday, December 20, 2013
    11 years ago
  • Date Issued
    Tuesday, March 24, 2015
    9 years ago
Abstract
A system and method for providing personal broadcast channels are provided. In one embodiment, one or more users interact with a local broadcast agent hosted by a local server to define profiles for a number of personal broadcast channels. The profiles include information identifying types of content to be broadcast on the personal broadcast channels and optionally formats for the personal broadcast channels. Based on the profiles for the personal broadcast channels, the local broadcast agent generates a request for content types desired for the personal broadcast channels and provides the request to a content distribution agent hosted by a master server. Based on content provided to the local server in response to the request and the profiles of the personal broadcast channels, the local broadcast agent generates the local broadcast channels.
Description
FIELD OF THE INVENTION

The present invention relates to a system and method for providing personalized broadcast channels.


BACKGROUND OF THE INVENTION

Traditionally, viewers watch a very small percentage of content broadcast by television service providers. Thus, there is a need for a system and method of providing broadcast channels that are personalized to user preferences.


SUMMARY OF THE INVENTION

The present invention relates to a system and method for providing personal broadcast channels. In one embodiment, the system includes a master server including a content distribution agent, a local or in-home server including a local broadcast agent, and one or more display devices connected to the local server. In operation, one or more users interact with the local broadcast agent either via the local server or a display device associated with the local server to define profiles for a number of personal broadcast channels. The profiles include information identifying types of content to be broadcast on the personal broadcast channels and optionally formats for the personal broadcast channels. Based on the profiles for the personal broadcast channels, the local broadcast agent generates a request for content types desired for the personal broadcast channels and provides the request to the content distribution agent at the master server. Based on content provided to the local server in response to the request and the profiles for the personal broadcast channels, the local broadcast agent generates the local broadcast channels.


In one embodiment, in order to generate the personal broadcast channels, the local broadcast agent receives a content list from the content distribution agent identifying content to be distributed to the local server. Based on the content list and the profiles of the personal broadcast channels, the local broadcast agent generates schedules for the personal broadcast channels. At some point after receiving the content list, the local broadcast agent receives the content identified in the content list. Thereafter, when a user desires to view a personal broadcast channel, the local broadcast agent provides or broadcasts the content identified for the personal broadcast channel according to the schedule for the personal broadcast channel.


Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.





BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the invention, and together with the description serve to explain the principles of the invention.



FIG. 1 illustrates a Personal Video Broadcast System (PVBS) according to one embodiment of the present invention;



FIG. 2 illustrates the operation of the PVBS according to one embodiment of the present invention;



FIG. 3 illustrates the operation of the PVBS according to another embodiment of the present invention;



FIG. 4 is a block diagram of the local server of FIGS. 1-3 according to one embodiment of the present invention;



FIG. 5 illustrates the PVBS according to another embodiment of the present invention;



FIG. 6 is a block diagram of the PVBS master server of FIGS. 1-5 according to one embodiment of the present invention;



FIG. 7 is a block diagram of the display device of FIG. 5 according to one embodiment of the present invention;



FIG. 8 illustrates a content review and distribution system according to one embodiment of the present invention;



FIG. 9 illustrates the operation of the content review and distribution system of FIG. 8 according to one embodiment of the present invention;



FIG. 10 is a more detailed illustration of a review process implemented by the content review and distribution system of FIG. 8 according to one embodiment of the present invention;



FIG. 11 is a block diagram of the content review and distribution server of FIG. 8 according to one embodiment of the present invention; and



FIG. 12 is a block diagram of the user device of FIG. 8 according to one embodiment of the present invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.



FIG. 1 illustrates a Personal Video Broadcast System (PVBS) 10 according to one embodiment of the present invention. Note that while the discussion herein focuses on video content, the personal broadcast channels are not limited thereto. In general, the PVBS 10 includes a Personal Video Broadcast System (PVBS) master server 12 and a number of consumer premises (CPs) 14-18 communicatively coupled by a network 20. Preferably, the network 20 is a Wide Area Network (WAN). However, the present invention is not limited thereto. As an example, the network 20 may be a distributed public access network such as the Internet. In addition, the customer premises 14-18 preferably have high speed connections to the network 20 such as, for example, Fiber-To-The-Home (FTTH) connections to the network 20 via one or more FTTH distribution networks.


The PVBS master server 12 includes a content distribution agent 22, which may be implemented in software, hardware, or a combination of software and hardware. The PVBS master server 12 may also maintain or be associated with a content database 24 and an advertisements database 26. The content database 24 may include commercial video content such as movies and television programs provided by commercial television content providers. In addition or alternatively, the content database 24 may include content authored and distributed by peer users. An exemplary system for providing content authored and distributed by peer users is discussed below with respect to FIGS. 8-12. The advertisements database 26 operates to store advertisements and optionally distribution criteria or distribution lists for the advertisements. As discussed below, the content distribution agent 22 operates to distribute video content and optionally advertisements from the databases 24 and 26 to the CPs 14-18.


It should be noted that while the content distribution agent 22 is illustrated as being hosted by the PVBS master server 12, the present invention is not limited thereto. For example, both the content distribution agent 22 and the content corresponding to the content database 24 may be hosted by one or more peers in a peer-to-peer (P2P) network. Thus, the content distribution agent 22 may operate to effect distribution of content from peers in the P2P network to the CPs 14-18 in a manner similar to that described below for the PVBS master server 12.


The CP 14 includes a local server 28 communicatively coupled to a number of display devices 30-1 through 30-N. Note that the following discussion is equally applicable to the other CPs 16 and 18. The local server 28 may also be referred to herein as an in-home server. The local server 28 includes a local broadcast agent 32, a personal channel profiles database 34, a content database 36, and an advertisements database 38. The local broadcast agent 32 may be implemented in software, hardware, or a combination of software and hardware. The personal channel profiles database 34, the content database 36, and the advertisements database 38 may be implemented in one or more digital storage devices such as one or more hard disk drives, one or more optical storage devices, memory, or the like. Further, the content database 36, for example, may be distributed among multiple devices within the CP 14.


The personal channel profiles database 34 operates to store a channel profile for each of a number of personal broadcast channels defined by users 40-1 through 40-N. Each of the channel profiles includes information identifying types of content to be broadcast on the associated personal broadcast channel and a format for the personal broadcast channel. Note that unlike Video-on-Demand (VoD) systems, the personal broadcast channels define types of content to be broadcast rather than selecting a particular video for viewing on demand. The types of content to be broadcast via the personal broadcast channel may be defined using various metadata. The metadata may include, for example, media type such as movie or television program; genre such as sports, news, history, drama, comedy, mystery, action, or science fiction; time period such as 1950s, 1960s, 1970s, 1980s, 1990s, or 2000s; television program series title such as Star Trek, Seinfeld, or Survivor, actors or actresses in the movie or television program; director of the movie or television program; or the like or any combination thereof. The exemplary metadata mentioned above for defining types of content is not intended to limit the scope of the present invention. Other types of metadata for defining types of content will be apparent to one of ordinary skill in the art upon reading this specification.


In addition, each of the channel profiles may include information identifying a desired format for the associated personal broadcast channel. The format may define a time at which the personal broadcast channel is to be active. For example, the format may be 24 hours a day, 7 days a week; from the hours of 5 p.m. to 9 p.m. on Monday through Friday; or the like. Still further, the format may be defined such that different types of content are broadcast at different times of the day. For example, the format may be defined such that educational content for children is broadcast from 8 a.m. until noon, television programs from the comedy genre are broadcast from noon until 5 p.m., news content is broadcast from 5 p.m. until 6 p.m., and episodes of Star Trek are broadcast from 6 p.m. until 10 p.m. The exemplary formats given above are not intended to limit the scope of the present invention.


The content database 36 operates to store content for the personal broadcast channels distributed to the local server 28 from the content distribution agent 22 of the PVBS master server 12. Likewise, the advertisements database 38 operates to store advertisements for the personal broadcast channels distributed to the local server 28 from the content distribution agent 22 of the PVBS master server 12.


Each of the display devices 30-1 through 30-N may be a television, a set-top box, a set-top box with digital video recorder functionality, a personal computer, a portable device such as a Personal Digital Assistant (PDA) or mobile telephone, or the like enabling users 40-1 through 40-N to view the personal broadcast channels provided by the local broadcast agent 32.



FIG. 2 illustrates the operation of the PVBS 10 of FIG. 1 according to one embodiment of the present invention. In general, the users 40-1 through 40-N interact with the local broadcast agent 32 via the display devices 30-1 through 30-N to define one or more personal broadcast channels (step 200). For each personal broadcast channel, a personal channel profile is defined. Alternatively, the users 40-1 through 40-N may interact directly with the local server 28 to define the personal channel profiles for the personal broadcast channels. As discussed above, the personal channel profiles include information identifying types of content desired for the personal broadcast channels and optionally formats for the personal broadcast channels.


The local broadcast agent 32 then generates a request for content to be provided to the content distribution agent 22 (step 202). More specifically, the local broadcast agent 32 aggregates the personal channel profiles to identify the types of content desired for the associated personal broadcast channels and optionally the relative amounts of content desired for each of the types of content. For example, if there is a 24 hour personal broadcast channel for sports content and a 1 hour a day or a 1 hour segment of a broadcast channel for news, then the local broadcast agent 32 may determine that the personal broadcast channels desire a greater amount of sports content than news content. As such, the generated request may provide information indicating that more sports content is desired than news content. Note that the request generated by the local broadcast agent 32 is a request for types of content in general. The request preferably does not include information regarding the specific users 40-1 through 40-N. As such, privacy is maintained between the PVBS master server 12 and the users 40-1 through 40-N.


The local broadcast agent 32 then sends the request to the content distribution agent 22 at the PVBS master server 12 (step 204). In a similar fashion, the content distribution agent 22 may receive requests from the local broadcast agents of the other CPs 16 and 18 in the PVBS 10. The content distribution agent 22 then generates a distribution plan for distributing content to the local broadcast agent 32 as well as the local broadcast agents of the other CPs 16 and 18 (step 206). The distribution plan may be generated, for example, daily or weekly. More specifically, the content distribution agent 22 identifies content from the content database 24 and optionally advertisements from the advertisements database 26 to distribute to the local broadcast agent 32 of the CP 14. Likewise, the content distribution agent 22 may identify content and advertisements for the other CPs 16 and 18. In order to efficiently distribute content to the CP 14 as well as to the other CPs 16 and 18, the content distribution agent 22 aggregates the request from the local broadcast agent 32 with requests from the local broadcast agents of the other CPs 16 and 18 and generates the distribution plan such that content and optionally advertisements are multicast to the CPs 14-18. For example, if a particular video is to be distributed to the CPs 14 and 16, the content distribution agent 22 may generate the distribution plan such that the video is multicast to the local broadcast agents of the CPs 14 and 16, thereby providing the video to both of the CPs 14 and 16 using a single transfer of the video.


From this point on, the local broadcast agent 32 generally operates to generate the personal broadcast channels based on content and optionally advertisements received from the content distribution agent 22 in response to the request and broadcast the personal broadcast channels to one or more of the display devices 30-1 through 30-N.


In this embodiment, content distribution agent 22 provides a content list to the local broadcast agent 32 identifying content and optionally advertisements that are to be distributed to the local broadcast agent 32 (step 208). Note that the content list may be redistributed or updated periodically such as daily or weekly in light of changes in content availability. For each video, or more generally digital asset, to be distributed to the local broadcast agent 32, the content list may include a title; estimated time at which the video will be distributed; a brief description of the video content; a length of the video content; information identifying a quality of the video; Digital Rights Management (DRM) rights such as one time play, multiple plays, and/or whether rewind and pausing are allowed; and advertisement insertion information such as types of advertisements that may be inserted into the video content, a total advertisement time required for the video content, and an overall video value to advertisement value. The overall video value to advertisement value provides an indication as to the relative value of commercials in the content. In a similar fashion, the content list may include information regarding advertisements to be distributed to the local broadcast agent 32 such as the advertisement type, run time, and the desired program to advertisement value.


Based on the content list and the personal channel profiles, the local broadcast agent 32 generates schedules for the personal broadcast channels (step 210). More specifically, based on the personal channel profiles, the local broadcast agent 32 analyzes the information provided in the content list to associate each video identified by the content list to one or more of the personal broadcast channels. Then, for each personal broadcast channel, a schedule is generated that provides the broadcast time and sequence of broadcast for the videos associated with the personal broadcast channel.


In addition, the local broadcast agent 32 may insert advertisement slots into the schedules for the personal broadcast channels. As stated above, the content list may include advertisement information identifying the types of advertisements to be inserted into each video, the total advertisement time for each video, and the overall program value to advertisement value for each video. In addition, the content list may include information regarding advertisements that are to be delivered to the local broadcast agent 32. Based on this information, the local broadcast agent 32 may insert advertisement slots into the schedules for the personal broadcast channels. The advertisement slots may be inserted during videos in the schedule and/or between successive videos in the schedule. In addition, advertisements may be placed in an Electronic Program Guide (EPG) or the like used to access the personal broadcast channels.


When selecting advertisements to be inserted into the schedules, the local broadcast agent 32 may consider the viewing habits of the user 40-1. For example, the local broadcast agent 32 may identify a prime viewing time for the user 40-1 based on the viewing habits of the user 40-1. As such, the content scheduled for this prime viewing time may be given a higher program to advertisement value. As such, advertisements that are desired to be inserted during content having high program to advertisement value may be inserted during the prime viewing time for the user 40-1.


Alternatively, rather than the local broadcast agent 32 inserting advertisement slots in the schedules, the content provided by the content distribution agent 22 may already include advertisements or advertisement slots.


Thereafter, the content and optionally advertisements for the personal broadcast channels are distributed to the local broadcast agent 32 according to the distribution plan of the content distribution agent 22 (step 212). In one embodiment, the content distribution agent 22 pushes the content and advertisements to the local broadcast agent 32 as well as the local broadcast agents of the CPs 16 and 18 using a multicasting scheme. More specifically, the distribution plan may identify each of the CPs 14-18 that are to receive a particular video. Thus, when the video is to be distributed, the content distribution agent 22 multicasts the video to the local broadcast agents of the CPs 14-18 that are to receive the video. In another embodiment, the content distribution agent 22 implements a hybrid push/pull scheme wherein the content distribution agent 22 multicasts content and advertisements to each of a number of the CPs 14-18, all of which may or may not desire the content and advertisements. As such, the local broadcast agents of the CPs 14-18 may obtain desired content and advertisements from the multicast and ignore content and advertisements that are not desired. The content and advertisements distributed to the local broadcast agent 32 are stored in the content database 36 and the advertisements database 38 of the local server 28.


Note that the content and advertisements may be assigned an aging out period by either the content distribution agent 22 or the local broadcast agent 32. The aging out period defines a period of time after which the associated content or advertisement is removed from storage at the local server 28. The user 40-1 may be given the ability to override the aging out period.


The distribution scheme described herein provides substantial benefits. For example, the content distribution agent 22 may provide content to the CPs 14-18 during off-peak hours, such as during the hours of 10 pm to 6 am, when the PVBS master server 12, the local server 28, and the network 20 are likely not to be experiencing heavy loads. Further, by pre-pushing the content to the local server 28 before broadcasting, quality of service issues associated with streaming content over the network 20 are avoided.


In this embodiment, at the request of the user 40-1, the display device 30-1 sends a selection message to the local broadcast agent 32 selecting a personal broadcast channel to view at the display device 30-1 (step 214). The local broadcast agent 32 then broadcasts the content and advertisements for the selected personal broadcast channel to the display device 30-1 according to the schedule generated for the selected personal broadcast channel, thereby providing the personal broadcast channel (step 216). The selected personal broadcast channel may be provided over an unused cable television channel or over a Local Area Network (LAN) connection. In an alternative embodiment, the personal broadcast channels may be continuously broadcast to the display devices 30-1 through 30-N over different channels where the display devices 30-1 through 30-N are tuned to the channel for the selected personal broadcast channel. It should be noted that not all content for the personal broadcast channel needs to be distributed to the local server 28 before broadcasting can begin. As long as content that is to be distributed at the current time is stored or at least partially stored at the local server 28, the broadcast can take place.


When providing personal broadcast channels to the display devices 30-1 through 30-N over a LAN connection or digital cable television channel, DRM restrictions may be used to control access to the personal broadcast channels. For example, DRM restrictions may be applied to a personal broadcast channel defined by the user 40-1 such that the personal broadcast channel is only accessible to the user 40-1 at the display device 30-1. The manner in which DRM restrictions may be applied to the personal broadcast channels will be apparent to one of ordinary skill in the art upon reading this disclosure.


While not illustrated, the local broadcast agent 32 may monitor the viewing habits of the user 40-1. Based on the viewing habits of the user 40-1, the local broadcasting agent 32 may adjust the amounts of the desired types of content requested from the content distribution agent 22. Alternatively, the local broadcasting agent 32 may provide information describing the viewing habits of the user 40-1 to the content distribution agent 22, where the content distribution agent 22 may consider the viewing habits of the user 40-1 when identifying content and the amounts of content to distribute to the local broadcast agent 32.



FIG. 3 illustrates the operation of the PVBS 10 of FIG. 1 according to a second embodiment of the present invention. In this embodiment, the content distribution agent 22 does not provide the content list to the local broadcast agent 32, and the local broadcast agent 32 generates the personal broadcast channels as content is delivered to the local server 28. More specifically, the users 40-1 through 40-N interact with the local broadcast agent 32 via the display devices 30-1 through 30-N to define one or more personal broadcast channels (step 300). For each personal broadcast channel, a personal channel profile is defined. Alternatively, the users 40-1 through 40-N may interact directly with the local server 28 to define the personal channel profiles for the personal broadcast channels. The local broadcast agent 32 then generates a request for content to be provided to the content distribution agent 22 (step 302).


The local broadcast agent 32 then sends the request to the content distribution agent 22 at the PVBS master server 12 (step 304). In a similar fashion, the content distribution agent 22 may receive requests from the local broadcast agents of the other CPs 16 and 18 in the PVBS 10. The content distribution agent 22 then generates a distribution plan for distributing content to the local broadcast agent 32 as well as the local broadcast agents of the other CPs 16 and 18 (step 306). The content distribution agent 22 then provides content and optionally advertisements to the local broadcast agent 32 according to the distribution plan (step 308).


As content and advertisements are delivered to the local broadcast agent 32 or at some point thereafter, the local broadcast agent 32 generates schedules for the personal broadcast channels based on the corresponding personal channel profiles (step 310). As discussed above, the schedules for the personal broadcast channels may be generated by analyzing the videos and optionally advertisements delivered to the local broadcast agent 32 or metadata associated therewith to associate each video and advertisement with one or more of the personal broadcast channels based on the personal channel profiles. The schedule for each of the personal video channels may then be generated to provide a broadcast sequence and broadcast times for the associated videos and advertisements.


In this embodiment, at the request of the user 40-1, the display device 30-1 sends a selection message selecting a personal broadcast channel to view at the display device 30-1 (step 312). The local broadcast agent 32 then broadcasts the videos and advertisements for the selected personal broadcast channel to the display device 30-1 according to the schedule generated for the selected personal broadcast channel, thereby providing the personal broadcast channel, as described above (step 314).



FIG. 4 is a block diagram of the local server 28 according to one embodiment of the present invention. In general, the local server 28 is communicatively coupled to the network 20 via a FTTH interface 42. Note that the FTTH interface 42 is exemplary. Other types of high speed interfaces may be used to connect the local server 28 to the network 20. The FTTH interface 42 provides a high speed connection to the network 20 for delivery of content and optionally advertisements for personal broadcast channels according to the present invention. The local server 28 may also be communicatively coupled to a Local Area Network (LAN) via a LAN gateway 44. This may be particularly beneficial where the display devices 30-1 through 30-N are personal computers or like device having a LAN interface rather than a traditional analog or digital cable television interface.


As illustrated, the local server 28 includes an Ethernet switch 46, the local broadcast agent 32, a content storage device 48, and a radio frequency (RF) output 50. The Ethernet switch 46 operates in one of three modes. In a first mode, the Ethernet switch 46 connects the FTTH interface 42 to the local broadcast agent 32 for communication between the local broadcast agent 32 and the content distribution agent 22 according to the present invention. In a second mode, the Ethernet switch 46 connects the FTTH interface 42 to the LAN gateway 44 for direct communication between LAN devices and the network 20. In a third mode, the Ethernet switch 46 connects the local broadcast agent 32 to the LAN gateway 44 for communication between the local broadcast agent 32 and ones of the display devices 30-1 through 30-N connected to the local server 28 via the LAN.


As illustrated in this embodiment, the local broadcast agent 32 includes a DRM encoder function 52, a DRM decoder function 54, a streaming server function 56, and a file manager function 58. The functions 52-58 may be implemented in software, hardware, or a combination thereof. The DRM encoder and decoder functions 52 and 54 may be used where content provided to the local broadcast agent 32 or the personal broadcast channels provided by the local broadcast agent 32 have or are to have DRM restrictions. The streaming server function 56 operates to stream or broadcast the personal broadcast channels to the display devices 30-1 through 30-N either over the LAN via the LAN gateway 44 or a traditional cable television connection via the RF output 50. The file manager function 58 operates to receive content and advertisements from the content distribution agent 22 via the FTTH interface 42 and store the content and advertisements in the content storage device 48. Due to the high speed connection provided by the FTTH interface 42, the file manager function 58 may buffer incoming files using high speed memory and transfer the buffered files to the content storage device 48. Note that the content storage device 48 may include one or more storage units such as one or more hard disk drives. As such, in order to efficiently transfer the buffered file to storage, the file manager function 58 may simultaneously transfer segments of the buffered file to different storage units and thereafter manage the segments of the file as a single file.


The RF output 50 enables the local broadcast agent 32 to broadcast the personal broadcast channels to the display devices 30-1 through 30-N using a traditional cable television connection. More specifically, each user 40-1 through 40-N, or alternatively each display device 30-1 through 30-N, may be assigned an unused cable television channel. As such, the streaming server function 56 may provide a different personal broadcast channel for each of the users 40-1 through 40-N, where the personal broadcast channels are combined into a single data stream. A video playback function 60 of the RF output 50 processes the output of the streaming server function 56 to provide a separate analog output for each of the personal broadcast channels. An RF modulator function 62 operates to upconvert the analog outputs to desired RF frequencies, which preferably correspond to unused cable television channels. An RF combiner function 64 then combines the upconverted analog outputs into a combined RF signal. An RF splitter/combiner function 66 then combines the combined RF signal with an input signal from an associated land-based or satellite-based television service provider. The display devices 30-1 through 30-N may then tune to channels corresponding to the personal broadcast channels in order to view the personal broadcast channels.



FIG. 5 illustrates a PVBS 10′ according to another embodiment of the present invention. This embodiment is substantially the same as that described above. However, in this embodiment, local broadcast agents are implemented on each of a number of display devices 68-1 through 68-3 rather than on a local or in-home server. Note that while the embodiments of FIGS. 1 and 5 are discussed separately, the PVBS 10′ may include both the CPs 14-18 of FIG. 1 and the display devices 68-1 through 68-1 of FIG. 5.


As illustrated, the system 10′ includes the PVBS master server 12 and the display devices 68-1 through 68-3 interconnected by the network 20. The display devices 68-1 through 68-3 may be personal computers, portable devices such as PDAs or mobile telephones, set-top boxes, televisions, or the like and are associated with users 70-1 through 70-3. Regarding the display device 68-1, the user 70-1 interacts with the local broadcast agent 32′ to create one or more personal channel profiles defining desired personal broadcast channels. The local broadcast agent 32′ aggregates the personal channel profiles and identifies the types of content desired for the personal broadcast channels and optionally relative amounts of content desired for each type of content. The local broadcast agent 32′ then sends a request for the desired types of content and optionally the relative amounts of content for each type of content to the content distribution agent 22. In a similar fashion, local broadcast agents of the other display devices 68-2 and 68-3 send requests to the content distribution agent 22.


At some time thereafter, the content distribution agent 22 identifies content from the content database 24 and optionally advertisements from the advertisements database 26 to provide to each of the display devices 68-1 through 68-3. The content distribution agent 22 then aggregates the requests from the display devices 68-1 through 68-3 and generates a content distribution plan for distributing the identified content to the display devices 68-1 through 68-3.


Then, as discussed above, in one embodiment, the content distribution agent 22 provides a content list to the local broadcast agent 32′ identifying the content that is to be distributed to the display device 68-1. In response, the local broadcast agent 32′ generates a schedule for each of the personal broadcast channels based on the corresponding personal channel profiles and the content list. Likewise, the content distribution agent 22 may provide content lists to the other display devices 68-2 and 68-3. In response, the local broadcast agents of the display devices 68-2 and 68-3 generate schedules for personal broadcast channels of the users 70-2 and 70-3. The content distribution agent 22 then distributes the content to the display devices 68-1 through 68-3 according to the distribution plan. Again, the distribution plan preferably uses multicasting to efficiently transfer the content to the display devices 68-1 through 68-3. For example, if a particular video is to be distributed to the display devices 68-1 and 68-2, the distribution plan may be generated such that the content distribution agent 22 multicasts the video to the display devices 68-1 and 68-2. Once the content is distributed to the display device 68-1, the local broadcast agent 32′ may provide the personal broadcast channels for viewing by the user 70-1 based on the schedules for the personal broadcast channels.


In another embodiment, the content distribution agent 22 does not provide a content list to the local broadcast agent 32′. Rather, the content distribution agent 22 distributes content to the display devices 68-1 through 68-3 according to the distribution plan. As content is received by the display device 68-1 or at some point after the content is received, the local broadcast agent 32′ generates the schedule for the personal broadcast channels based on the corresponding personal channel profiles. Thereafter, the local broadcast agent 32′ may provide the personal broadcast channels for viewing by the user 70-1 based on the schedules for the personal broadcast channels.



FIG. 6 is a block diagram of the PVBS master server 12 according to one embodiment of the present invention. In general, the PVBS master server 12 includes a control system 72 having associated memory 74. In this embodiment, the content distribution agent 22 is implemented in software and stored in the memory 74. The PVBS master server 12 also includes one or more digital storage devices 76, which may operate to store the content database 24 and the advertisements database 26. The digital storage devices 76 may be, for example, hard disk drives, optical storage devices, memory, or the like. The PVBS master server 12 also includes a communication interface 78 communicatively coupling the PVBS master server 12 to the network 20. The PVBS master server 12 may also include a user interface 80, which may include components such as a display, one or more user input devices, and the like.



FIG. 7 is a block diagram of the display device 68-1 of FIG. 5 according to one embodiment of the present invention. However, this discussion is equally applicable to the other display devices 68-2 and 68-3. In general, the display device 68-1 includes a control system 82 including the local broadcast agent 32′. As will be apparent to one of ordinary skill in the art, the control system 82 may include hardware and/or software components in addition to the local broadcast agent 32′ depending on the particular implementation. The local broadcast agent 32′ may be implemented in software, hardware, or a combination of software and hardware. The display device 68-1 also includes one or more digital storage devices 84 operating to store the personal channel profiles database 34′, the content database 36′, and the advertisements database 38′. The digital storage devices 84 may be, for example, hard disk drives, optical storage devices, memory, or the like. The display device 68-1 also includes a communication interface 86 communicatively coupling the display device 68-1 to the network 20. In addition, the communication interface 86 may communicatively couple the display device 68-1 to a land-based or satellite-based television service provider. The display device 68-1 may also include a user interface 88, which may include components such as one or more user input devices, a display, speakers, and the like.


As mentioned above, FIGS. 8-12 discuss an exemplary system for providing content to the PVBS master server 12 of FIG. 1. However, the content review and distribution system 90 discussed below is not limited to distributing content via the PVBS 10 and may distribute reviewed content using any type of public or commercial distribution entity or system.



FIG. 8 illustrates the content review and distribution system 90 according to one embodiment of the present invention. As discussed below, in an exemplary embodiment, the system 90 may provide all or a portion of the content distributed by the PVBS master server 12 described above. In general, the system 90 includes a central review and distribution server 92, a number of user devices 94-1 through 94-N, and a distribution entity 96 communicatively coupled by a network 98. The network 98 may be any type of Wide Area Network (WAN), Local Area Network (LAN), Personal Area Network (PAN), or the like. As an example, the network 98 may be a public distributed network such as the Internet. Authors/reviewers 100-1 through 100-N are associated with the user devices 94-1 through 94-N. The authors/reviewers 100-1 through 100-N are persons that both submit content to the central review and distribution server 92 for review and potentially distribution and agree to review content submitted by other persons. Depending on the particular role that the authors/reviewers 100-1 through 100-N are performing at a particular point in the following discussion, the authors/reviewers 100-1 through 100-N may alternatively be referred to as either authors 100-1 through 100-N or reviewers 100-1 through 100-N.


The central review and distribution server 92 includes a review and distribution agent 102, which may be implemented in software. As discussed below, the review and distribution agent 102 operates to effect review and potentially distribution of content authored by the authors 100-1 through 100-N. The central review and distribution server 92 also includes or is associated with an author/reviewer profiles database 104 and a content database 106. The author/reviewer profiles database 104 operates to store profiles of the authors/reviewers 100-1 through 100-N. The profiles include credentials of the authors/reviewers 100-1 through 100-N, where the credentials of the authors/reviewers 100-1 through 100-N are used to select reviewers for submitted content, as discussed below. The content database 106 operates to store content submitted to the central review and distribution server 92 for review and potentially distribution to a distribution entity such as the distribution entity 96. The content submitted for review may be any type of digital content such as, for example, videos, images, audio files, literature, or the like. Individual content, such as individual video files, may be referred to herein as digital assets.


The user devices 94-1 through 94-N may be, for example, personal computers; portable devices such as PDAs, mobile telephones, or mobile media players; or a like device capable of accessing the network 98. In operation, the authors/reviewers 100-1 through 100-N are enabled to submit content to the central review and distribution server 92 and review content submitted to the central review and distribution server 92 by others of the authors/reviewers 100-1 through 100-N via the user devices 94-1 through 94-N.


The distribution entity 96 may be a public or commercial content distribution entity. For example, the distribution entity 96 may be a commercial content provider such as the PVBS master server 12 discussed above, a television service provider, or the like. Alternatively, the distribution entity 96 may be a public content provider such as, for example, http://www.youtube.com, http://www.video.google.com, or the like.


Note that while FIG. 8 illustrates the review and distribution agent 102 as being implemented on the central review and distribution server 92, the present invention is not limited thereto. For example, the review and distribution agent 102 may alternatively be implemented as a distributed agent hosted by one or more of the user devices 94-1 through 94-N where the user devices 94-1 through 94-N are configured as a P2P network.



FIG. 9 illustrates the operation of the system 90 of FIG. 8 according to one embodiment of the present invention. First, the authors 100-1 through 100-N register with the review and distribution agent 102 via the user devices 94-1 through 94-N (step 400). During registration, the authors 100-1 through 100-N agree to review content submitted by others of the authors 100-1 through 100-N in exchange for review and potentially distribution of their own content. For example, the author 100-1 may agree to review two digital assets submitted by others of the authors 100-2 through 100-N for each digital asset submitted by the author 100-1 for review and potentially distribution. The agreements may be enforced by refusing to distribute content submitted by the authors 100-1 through 100-N until the authors have met the requirements of the agreement.


At some point in time, one of the authors 100-1 through 100-N submits content to the review and distribution agent 102 for review and potentially distribution (step 402). For this discussion, the author 100-1 is the author that submits the content. When submitting the content, the content and metadata for the content are provided to the review and distribution agent 102. Alternatively, only the metadata for the content may be provided to the review and distribution agent 102. The metadata may be defined by the author 100-1, automatically populated, or both. The metadata preferably includes a target quality level for the content selected by the author 100-1. In addition or alternatively, the metadata may include a content type such as video, image, or audio; file format; file size; resolution; title; brief description; keywords; genre or content category such as comedy, history, drama, mystery, action, science fiction, or the like; sub-genre or sub-category such as standup, sitcom, movie, or the like; requested distribution scheme such as free, copyrighted, ad-based, payment-on-demand, or the like; usage polices such as DRM restrictions for the content when distributed; recommended reviewers; non-recommended reviewers; or the like.


Next, the review and distribution agent 102 effects review of the submitted content according to the present invention (step 404). The details of the review process are discussed below in detail with respect to FIG. 10. In the preferred embodiment, the review and distribution agent 102 effects an iterative review process based on quality level. More specifically, the author 100-1 selects a target quality level for the submitted content. The target quality level may be between and including a minimum quality level, which may be quality level 1, and a maximum quality level, which may be quality level 3. The submitted content is iteratively reviewed by groups of the reviewers 100-2 through 100-N selected for each quality level up to the target quality level or until the submitted content fails to satisfy the requirements of a quality level. Based on the review, the content is assigned a rated quality level. The rated quality level may be used to define, for example, a value of the content to a commercial distribution entity. The review may also check for copyright infringement and the correctness or accuracy of the metadata associated with the submitted content. In addition, the review may allow reviewers, which are select ones of the other authors/reviewers 100-2 through 100-N, to provide comments or other feedback to the author 100-1 regarding the submitted content.


After review of the submitted content, the review and distribution agent 102 provides feedback including the rated quality level to the author 100-1 via the user device 94-1 (step 406). Note that in an alternative embodiment, feedback may be provided to the author 100-1 after each iteration of the review process. Further note that the feedback may include identifiers (IDs) identifying feedback from each of the group of reviewers. Note that if the author 100-1 feels a review by one of the group of reviewers is inaccurate, the author 100-1 can request that the reviewer be excluded from reviewing content from the author 100-1 in the future. If a reviewer is excluded by a threshold number or percentage of the authors 100-1 through 100-N, the reviewer may be prevented from making future content submissions.


After receiving the feedback, the author 100-1 then decides either to revise the content based on the feedback and resubmit the content for review or to distribute the content at the rated quality level (step 408). Once the author 100-1 decides to distribute the content, the review and distribution agent 102 effects transfer of the content to one or more distribution entities, such as the distribution entity 96, according to the desired distribution scheme and usage polices for the content. In one embodiment, the content is submitted to the review and distribution agent 102 in step 402. As such, the review and distribution agent 102 may transfer the content to the distribution entity 96 from the content database 106. In another embodiment, the review and distribution agent 102 may effect a transfer of the content from the user device 94-1 to the distribution entity 96.



FIG. 10 illustrates the review process according to one embodiment of the present invention. In this embodiment, the review process is an iterative review process based on quality level where submitted content is rated at one of a number of quality levels. Each of the quality levels may have associated criteria to be used by reviewers to determine if submitted content satisfies the requirements of the quality level. First, once content is submitted for review by, for example, the author 100-1, the review and distribution agent 102 selects a group of reviewers from the reviewers 100-2 through 100-N for a first or minimum quality level based on credentials of the reviewers 100-2 through 100-N (step 500). For each of the reviewers 100-1 through 100-N, the review and distribution agent 102 generates the credentials of the reviewer based on, for example, a total number of digital assets submitted by the author/reviewer for review, a number or percentage of the total number of digital assets reviewed for each quality level, a total number of digital assets submitted by other authors and reviewed by the reviewer at each of the quality levels, and a percent deviation from the other reviewers at each quality level for the digital assets reviewed by the reviewer. In addition, the review and distribution agent 102 may maintain these statistics for a number of sub-categories within the quality levels such as content type, genre, sub-genre, requested distribution scheme, run time if applicable, and the like. This may be beneficial if specialized reviewers within each quality level are desired.


When selecting the group of reviewers based on the credentials of the reviewers 100-2 through 100-N, the review and distribution agent 102 may first consider the credentials for the reviewers 100-2 through 100-N with respect to the current quality level, which for the first iteration of the review process may be, for example, a minimum quality level. More specifically, the review and distribution agent 102 may first identify ones of the reviewers 100-2 through 100-N having credentials indicating that they have accurately reviewed content at or above the current quality level and/or have submitted content that has been reviewed at or above the current quality level. If the number of identified reviewers is greater than a desired number of reviewers for the submitted content, the review and distribution agent 102 may select a portion of the identified reviewers as the group of reviewers for the submitted content using, for example, a random selection process, based on relative credentials, or based on credentials of the identified reviewers 100-2 through 100-N with respect to other metadata for the submitted content such as content type, genre, sub-genre, requested distribution scheme, run time, or the like.


Before finalizing the selected group of reviewers from the reviewers 100-2 through 100-N, the review and distribution agent 102 may query the selected group of reviewers for their willingness to review the submitted content within a specified amount of time. The specified amount of time may be defined by the review and distribution agent 102 or by the author 100-1 of the submitted content. If all of the selected reviewers indicate willingness to review the submitted content within the specified amount of time, then the selected group of reviewers is finalized. Otherwise, ones of the selected group of reviewers that are not willing to review the submitted content within the specified amount of time may be removed from the selected group of reviewers and optionally replaced.


Once the group of reviewers is selected, the review and distribution agent 102 provides the submitted content to the selected group of reviewers, or more specifically to the ones of the user devices 94-2 through 94-N associated with the selected group of reviewers (step 502). When providing the submitted content to the selected group of reviewers, DRM policies may be applied to the submitted content such that, for example, only the selected group of reviewers may view or otherwise consume the submitted content. In addition, DRM policies may be applied to limit playback to enable or disable multiple viewings of the submitted content, to enable or disable pausing, rewinding, or fast-forwarding of the submitted content, or the like. Alternatively, rather than uploading the submitted content to the content database 106 and then providing the submitted content to the selected group of reviewers, the review and distribution agent 102 may effect a peer-to-peer (P2P) connection between the user device 94-1 of the author 100-1 and the ones of the user devices 94-2 through 94-N associated with the selected group of reviewers where the submitted content is transferred or multicast to the ones of the user devices 94-2 through 94-N associated with the selected group of reviewers.


At this point, the selected group of reviewers review the submitted content to either approve or disapprove of the submitted content being rated at the current quality level or assign the content a rated quality level, to check for copyright infringement, and to check for the accuracy of other metadata associated with the submitted content such as content type, file format, file size, resolution, run time, genre, sub-genre, and the like. In addition, the group of reviewers may comment on the title of the content, the description of the content, the keywords for the content, the requested distribution scheme for the content, the usage policies for the content, or the like. Still further, the group of reviewers may provide additional comments or feedback regarding the content.


Once reviewed, the review and distribution agent 102 receives feedback from the selected group of reviewers (step 504). Based on the feedback, the review and distribution agent 102 may decide whether to continue the review by proceeding to a review at the next quality level (step 506). If, for example, a predefined number or percentage of the select group of users has disapproved of the submitted content being rated at the current quality level, which is also referred to herein as not being reviewed to the current quality level, the review and distribution agent 102 may decide not to proceed to the review at the next quality level. In addition, if there are one or more errors with respect to the other metadata for the submitted content, the review and distribution agent 102 may decide not to proceed to the review at the next quality level. The review and distribution agent 102 may also decide not to proceed to the review at the next quality level if the current quality level is the target quality level for the content or the maximum quality level.


If the review and distribution agent 102 decides to proceed to the review at the next quality level, the review process returns to step 500 where reviewers are selected for the next quality level, and the process is repeated. If the review and distribution agent 102 decides not to proceed to the next quality level or if the submitted content has been reviewed to the target or maximum quality level, then the review and distribution agent 102 provides feedback to the author 100-1 via the user device 94-1 (step 508). The feedback includes the rated quality level, corrections to or information identifying errors in other metadata of the submitted content, and any additional comments or feedback provided by the group of reviewers during the review process. Note that the review and distribution agent 102 may require the author 100-1 to correct some or all of the errors in the metadata before distribution of the content.


Once the review process is complete, the author 100-1 may either distribute the content at the rated quality level or revise the content based on the feedback and re-submit the content for review.


In an alternative embodiment, the review and distribution agent 102 may return feedback to the author 100-1 after each iteration of the review process. In response, the author 100-1 may either revise the content based on the feedback and re-submit the revised content for the next iteration of the review process or instruct the review and distribution agent 102 to distribute the content at current rated quality level.


While the discussion above focuses on an iterative review process, the present invention is not limited thereto. For example, rather than iteratively reviewing submitted content at each successive quality level, the review and distribution agent 102 may effect review of the submitted content only at the target quality level. Further, while the discussion above focuses on the quality level as being the primary consideration for selecting reviewers, the present invention is not limited thereto. Reviewers may be selected based on credentials associated with any of the metadata for the submitted content or any combination thereof. For example, if a video of the comedy genre, the sitcom sub-genre, and a target quality level of 3 is submitted for review, the review and distribution agent 102 may select reviewers for the submitted content based on credentials of the reviewers 100-1 through 100-N with respect to videos, with respect to the comedy genre, with respect to the sitcom sub-genre, with respect to quality level 3, or any combination thereof.



FIG. 11 is a block diagram of the central review and distribution server 92 of FIG. 8 according to one embodiment of the present invention. In general, the central review and distribution server 92 includes a control system 108 having associated memory 110. In this example, the review and distribution agent 102 is implemented in software and stored in the memory 110. The central review and distribution server 92 may also include one or more digital storage devices 112, which may be used to store the author/reviewer profiles database 104 and the content database 106. The central review and distribution server 92 also includes a communication interface 114 communicatively coupling the central review and distribution server 92 to the network 98. The central review and distribution server 92 may also include a user interface 116, which may include components such as a display, one or more user input devices, and the like.



FIG. 12 is a block diagram of the user device 94-1 of FIG. 8 according to one embodiment of the present invention. However, this discussion is equally applicable to the other user devices 94-2 through 94-N. In general, the user device 94-1 includes a control system 118 having associated memory 120. The user device 94-1 may also include one or more digital storage devices 122.


The user device 94-1 also includes a communication interface 124 communicatively coupling the user device 94-1 to the network 98. The user device 94-1 may also include a user interface 126, which may include components such as a display, speakers, one or more user input devices, and the like.


Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.

Claims
  • 1. A method for implementing a media server comprising: receiving a plurality of profiles associated with users of the media server, wherein the plurality of profiles are defined by input received from the users;storing the plurality of profiles in a first database residing on the media server;identifying types of desired content based on the plurality of profiles;sending a request to a first entity for identified types of the desired content, the request indicating relative amounts of the identified types of the desired content;receiving from the first entity, content and content metadata based on the plurality of profiles from a remote content database;receiving from the first entity, advertisements and advertisement metadata based on the plurality of profiles from a remote advertisement database;storing the content and content metadata in a second database residing on the media server;storing the advertisement and advertisement metadata in a third database residing on the media server;selecting a first content item based on a first user profile of the plurality of profiles and the content metadata;determining a first advertisement slot in the first content item;selecting a first advertisement based on the first user profile and the advertisement metadata;inserting the first advertisement into the first advertisement slot; andstreaming the first content item with the inserted first advertisement to a user device associated with the first user profile.
  • 2. The method of claim 1, wherein the first entity is a master server that distributes the content and the advertisements.
  • 3. The method of claim 2, wherein the media server communicates with the first entity via a wide area network (WAN).
  • 4. The method of claim 1, wherein the media server communicates with the user device second entity via a local area network (LAN).
  • 5. The method of claim 1, wherein the content is defined based on at least one type of metadata selected from a group consisting of: content type, genre, sub-genre, time period of release, series title, actors or actresses appearing in the content, and director of the content.
  • 6. The method of claim 1, wherein the content is video content.
  • 7. A hardware media server comprising: a first database;a second database;a third database; anda hardware local agent communicatively coupled with the first database, the second database, and the third database, the hardware local agent configured to:receive a plurality of profiles associated with users of the hardware media server, wherein the plurality of profiles are defined by input received from the users;store the plurality of profiles in the first database;identify types of desired content based on the plurality of profiles;send a request to a first entity for identified types of the desired content, the request indicating relative amounts of the identified types of the desired content;receive from the first entity, content and content metadata based on the plurality of profiles from a remote content database;receive from the first entity, advertisements and advertisement metadata based on the plurality of profiles from a remote advertisement database;store the content and content metadata in the second database;store the advertisement and advertisement metadata in the third database;select a first content item based on a first user profile of the plurality of profiles and the content metadata;determine a first advertisement slot in the first content item;select a first advertisement based on the first user profile and the advertisement metadata;insert the first advertisement into the first advertisement slot; andstream the first content item with the inserted first advertisement to a user device associated with the first user profile.
  • 8. The hardware media server of claim 7, wherein the first entity is a master server that distributes the content and the advertisements.
  • 9. The hardware media server of claim 8, wherein the media server communicates with the first entity via a wide area network (WAN).
  • 10. The hardware media server of claim 7, wherein the media server communicates with the user device via a local area network (LAN).
  • 11. The hardware media server of claim 7, wherein the content is defined based on at least one type of metadata selected from a group consisting of: content type, genre, sub-genre, time period of release, series title, actors or actresses appearing in the content, and director of the content.
  • 12. The hardware media server of claim 7, wherein the content is video content.
PRIORITY CLAIM

The present application is a continuation of U.S. patent application Ser. No. 11/536,135, entitled PERSONALIZED BROADCAST SYSTEM, which was filed on Sep. 28, 2006, which is incorporated by reference herein in its entirety for all purposes.

US Referenced Citations (188)
Number Name Date Kind
5278834 Mazzola Jan 1994 A
5613004 Cooperman et al. Mar 1997 A
5633678 Parulski et al. May 1997 A
5687236 Moskowitz et al. Nov 1997 A
5758257 Herz et al. May 1998 A
5768640 Takahashi et al. Jun 1998 A
5790935 Payton Aug 1998 A
5818838 Backes et al. Oct 1998 A
5905800 Moskowitz et al. May 1999 A
6128736 Miller Oct 2000 A
6141753 Zhao et al. Oct 2000 A
6247009 Shiiyama et al. Jun 2001 B1
6282299 Tewfik et al. Aug 2001 B1
6304729 Honda et al. Oct 2001 B2
6389541 Patterson May 2002 B1
6438579 Hosken Aug 2002 B1
6507371 Hashimoto et al. Jan 2003 B1
6510234 Cox et al. Jan 2003 B1
6629104 Parulski et al. Sep 2003 B1
6657661 Cazier Dec 2003 B1
6721282 Motley Apr 2004 B2
6735699 Sasaki et al. May 2004 B1
6738493 Cox et al. May 2004 B1
6751670 Patterson Jun 2004 B1
6774926 Ellis et al. Aug 2004 B1
6804779 Carroni et al. Oct 2004 B1
6914625 Anderson et al. Jul 2005 B1
6914626 Squibbs Jul 2005 B2
6943825 Silvester Sep 2005 B2
6975743 Venkatesan et al. Dec 2005 B2
6987985 Purkayastha et al. Jan 2006 B2
7003131 Watson et al. Feb 2006 B2
7016668 Vaidyanathan et al. Mar 2006 B2
7020304 Alattar et al. Mar 2006 B2
7036024 Watson Apr 2006 B2
7039932 Eldering May 2006 B2
7065607 England et al. Jun 2006 B2
7079176 Freeman et al. Jul 2006 B1
7106360 Frederick Sep 2006 B1
7149549 Ortiz et al. Dec 2006 B1
7219301 Barrie et al. May 2007 B2
7382879 Miller Jun 2008 B1
7409556 Wu et al. Aug 2008 B2
7430302 Thorwirth Sep 2008 B2
7565450 Garcia-Luna-Aceves et al. Jul 2009 B2
7600037 Tucker Oct 2009 B2
7650617 Hoshino et al. Jan 2010 B2
7652594 Lamont et al. Jan 2010 B2
7983440 Roberts et al. Jul 2011 B1
8102863 Evans Jan 2012 B1
8320610 Evans et al. Nov 2012 B2
20010051996 Cooper et al. Dec 2001 A1
20020010759 Hitson et al. Jan 2002 A1
20020013812 Krueger et al. Jan 2002 A1
20020045987 Ohata et al. Apr 2002 A1
20020049580 Kutaragi et al. Apr 2002 A1
20020054578 Zhang et al. May 2002 A1
20020061029 Dillon May 2002 A1
20020071677 Sumanaweera Jun 2002 A1
20020095454 Reed et al. Jul 2002 A1
20020104003 Iwamura Aug 2002 A1
20020104015 Barzilai et al. Aug 2002 A1
20020104099 Novak Aug 2002 A1
20020110123 Shitama Aug 2002 A1
20020114336 Chow Aug 2002 A1
20020129367 Devara Sep 2002 A1
20020138291 Vaidyanathan et al. Sep 2002 A1
20020138440 Vaidyanathan et al. Sep 2002 A1
20020144267 Gutta et al. Oct 2002 A1
20020156842 Signes et al. Oct 2002 A1
20020168082 Razdan Nov 2002 A1
20020184403 Dahlin et al. Dec 2002 A1
20020191087 Hashimoto et al. Dec 2002 A1
20020199203 Duffy et al. Dec 2002 A1
20030004793 Feuer et al. Jan 2003 A1
20030009769 Hensgen et al. Jan 2003 A1
20030012403 Rhoads et al. Jan 2003 A1
20030050055 Ting et al. Mar 2003 A1
20030058836 Even Mar 2003 A1
20030081580 Vaidyanathan et al. May 2003 A1
20030093665 Cooper et al. May 2003 A1
20030145325 Finster et al. Jul 2003 A1
20030152096 Chapman Aug 2003 A1
20030156208 Obradovich Aug 2003 A1
20030161268 Larsson et al. Aug 2003 A1
20040008864 Watson et al. Jan 2004 A1
20040010692 Watson Jan 2004 A1
20040010694 Collens et al. Jan 2004 A1
20040021780 Kogan Feb 2004 A1
20040030798 Andersson et al. Feb 2004 A1
20040032495 Ortiz Feb 2004 A1
20040042421 Mahany Mar 2004 A1
20040049787 Maissel et al. Mar 2004 A1
20040070593 Neely et al. Apr 2004 A1
20040083487 Collens et al. Apr 2004 A1
20040086122 Watson May 2004 A1
20040088557 Malcolm et al. May 2004 A1
20040117824 Karaoguz et al. Jun 2004 A1
20040139047 Rechsteiner et al. Jul 2004 A1
20040156528 Joo et al. Aug 2004 A1
20040174434 Walker et al. Sep 2004 A1
20040174443 Simske Sep 2004 A1
20040187005 Molaro Sep 2004 A1
20040248615 Purkayastha et al. Dec 2004 A1
20040252651 Karlsen et al. Dec 2004 A1
20040263941 Chen et al. Dec 2004 A1
20040264372 Huang Dec 2004 A1
20050008017 Datta et al. Jan 2005 A1
20050034001 Pontarelli Feb 2005 A1
20050050103 Kesteloot et al. Mar 2005 A1
20050065891 Lee et al. Mar 2005 A1
20050081042 Venkatesan et al. Apr 2005 A1
20050086069 Watson et al. Apr 2005 A1
20050091160 Kitze et al. Apr 2005 A1
20050091232 Eschbach et al. Apr 2005 A1
20050097183 Westrelin May 2005 A1
20050097331 Majidimehr et al. May 2005 A1
20050108769 Arnold et al. May 2005 A1
20050120120 Suzuki Jun 2005 A1
20050120127 Bradley et al. Jun 2005 A1
20050125405 Watson et al. Jun 2005 A1
20050169632 Song et al. Aug 2005 A1
20050182989 Zarnke et al. Aug 2005 A1
20050183120 Jain et al. Aug 2005 A1
20050192987 Marsh Sep 2005 A1
20050193421 Cragun Sep 2005 A1
20050198068 Mukherjee et al. Sep 2005 A1
20050201340 Wang et al. Sep 2005 A1
20050201726 Malcolm et al. Sep 2005 A1
20050216942 Barton Sep 2005 A1
20050220321 Langelaar Oct 2005 A1
20050239497 Bahl et al. Oct 2005 A1
20050251491 Medina et al. Nov 2005 A1
20050278379 Nakazawa Dec 2005 A1
20050286438 Rajkotia Dec 2005 A1
20060010274 Olson Jan 2006 A1
20060015193 Kato Jan 2006 A1
20060015735 Kudo et al. Jan 2006 A1
20060036490 Sagalyn Feb 2006 A1
20060048185 Alterman Mar 2006 A1
20060048186 Alterman Mar 2006 A1
20060050880 Taylor et al. Mar 2006 A1
20060053452 Lee et al. Mar 2006 A1
20060056349 Nakatugawa et al. Mar 2006 A1
20060059560 Montulli Mar 2006 A1
20060072786 Watson et al. Apr 2006 A1
20060075057 Gildea et al. Apr 2006 A1
20060075243 Lakamp et al. Apr 2006 A1
20060080707 Laksono Apr 2006 A1
20060085830 Bruck et al. Apr 2006 A1
20060095401 Krikorian et al. May 2006 A1
20060095471 Krikorian et al. May 2006 A1
20060095472 Krikorian et al. May 2006 A1
20060095507 Watson May 2006 A1
20060095792 Hurtado et al. May 2006 A1
20060110552 Ishida et al. May 2006 A1
20060123235 Vanstone Jun 2006 A1
20060127037 Van Hoff et al. Jun 2006 A1
20060129672 Mayer Jun 2006 A1
20060133644 Wells et al. Jun 2006 A1
20060156003 Zhang et al. Jul 2006 A1
20060161776 Van Der Veen et al. Jul 2006 A1
20060173794 Sellars et al. Aug 2006 A1
20060174128 Yuval Aug 2006 A1
20060195325 Tateson et al. Aug 2006 A1
20060200416 White et al. Sep 2006 A1
20060206933 Molen et al. Sep 2006 A1
20060212900 Ismail et al. Sep 2006 A1
20060221190 Limberis et al. Oct 2006 A1
20060271691 Jacobs et al. Nov 2006 A1
20060271960 Jacoby et al. Nov 2006 A1
20060271997 Jacoby et al. Nov 2006 A1
20060294555 Xie Dec 2006 A1
20070002742 Krishnaswamy et al. Jan 2007 A1
20070061488 Alagappan et al. Mar 2007 A1
20070061580 Venkatesan et al. Mar 2007 A1
20070064121 Issa et al. Mar 2007 A1
20070078833 Chea et al. Apr 2007 A1
20070101368 Jacoby et al. May 2007 A1
20070133673 Imaizumi Jun 2007 A1
20070143778 Covell et al. Jun 2007 A1
20070169165 Crull et al. Jul 2007 A1
20080044087 Levy et al. Feb 2008 A1
20090037388 Cooper et al. Feb 2009 A1
20090067328 Morris et al. Mar 2009 A1
20090133116 Waisbard et al. May 2009 A1
20090287837 Felsher Nov 2009 A1
20130117621 Saraiya et al. May 2013 A1
Foreign Referenced Citations (10)
Number Date Country
1162840 Dec 2001 EP
1524602 Apr 2005 EP
1528478 May 2005 EP
2306869 May 1997 GB
9905584 Feb 1999 WO
0040021 Jul 2000 WO
0069163 Nov 2000 WO
0171524 Sep 2001 WO
0245430 Jun 2002 WO
2006046099 May 2006 WO
Non-Patent Literature Citations (45)
Entry
Bailey, S., et al., “The Architecture of Direct Data Placement (DDP) and Remote Direct Memory Access (RDMA) on Internet Protocols”, Request for Comments (RFC) 4296, Network Working Group, Internet Engineering Task Force, Dec. 2005, http://www.ietf.org/rfc/rfc4296.txt, 21 pages.
Cain, B., et al., “Internet Group Management Protocol, Version 3”, Request for Comments (RFC) 3376, Network Working Group, Internet Engineering Task Force, Oct. 2002, http://www.ietf.org/rfc/rfc3376.txt, 50 pages.
Deering, S., et al., “Internet Protocol, Version 6 (IPv6) Specification”, Request for Comments (RFC) 2460, Network Working Group, Internet Engineering Task Force, Dec. 1998, http://www.ietf.org/rfc/rfc2460.txt, 37 pages.
Fridrich, J., “Methods for data hiding,” Center for Intelligent Systems & Department of Systems Science and Industrial Engineering, SUNY Binghamton, http://www.ws.binghamton.edu/fridrich/research/meth—ps.ps, accessed Feb. 20, 2009, 33 pages.
Hilland, Jeff et al., “RDMA Protocol Verbs Specification (Version 1.0)”, Apr. 2003, http://www.rdmaconsortium.org/home/draft-hilland-iwarp-verbs-v1.0-RDMAC.pdf, 242 pages.
Postel, J. (ed), “Internet Protocol: DARPA Internet Program Protocol Specification”, Request for Comments (RFC) 791, Information Sciences Institute, Sep. 1981, http://www.ietf.org/rfc/rfc791.txt, 49 pages.
Postel, J., “User Datagram Protocol”, Request for Comments (RFC) 768, Aug. 28, 1980, http://www.ietf.org/rfc/rfc768.txt, 3 pages.
Recio, R., et al., “An RDMA Protocol Specification (Version 1.0)”, Oct. 2002, http://www.rdmaconsortium.org/home/draft-recio-iwarp-rdmap-v1.0.pdf, 60 pages.
Romanow, A., et al., “Remote Direct Memory Access (RDMA) over IP Problem Statement”, Request for Comments (RFC) 4297, Network Working Group, Internet Engineering Task Force, Dec. 2005, http://www.ietf.org/rfc/rfc4297.txt, 19 pages.
Schulzrinne, H., et al., “Real Time Streaming Protocol (RTSP)”, Request for Comments (RFC) 2326, Network Working Group, Internet Engineering Task Force, Apr. 1998, http://www.ietf.org/rfc/rfc2326.txt, 86 pages.
Schulzrinne, H., et al., “RTP: A Transport Protocol for Real-Time Applications”, Request for Comments (RFC) 3550, Network Working Group, Internet Engineering Task Force, Jul. 2003, http://www.ietf.org/rfc/rfc3550.txt, 98 pages.
Shah, Hemal et al., “Direct Data Placement over Reliable Transports (Version 1.0)”, Oct. 2002, http://www.rdmaconsortium.org/home/draft-shah-iwarp-ddp-v1.0.pdf, 35 pages.
Wenger S., et al., “RTP Payload Format for H.264 Video”, Request for Comments (RFC) 3984, Network Working Group, Internet Engineering Task Force, Feb. 2005, http://www.ietf.org/rfc/rfc3984.txt, 65 pages.
Author Unknown, “ITU Publications: Welcome,” International Telecommunications Union, http://www.itu.int/publications/, accessed on Jun. 26, 2008, 1 page.
Author Unknown, “PacketCable TM 2.0: Codec and Media Specification, PKT-AP-CODEC-MEDIA-I02-061013”, CableLabs, Oct. 13, 2006, http://www.packetcable.com/downloads/specs/PKT-AP-CODEC-MEDIA-I02-061013.pdf, 89 pages.
Author Unknown, “Advertisement Bidding System and Method,” ip.com: Prior Art Database, Copyright: 2004, Retrieved: Jun. 15, 2007, 2 pages, http://www.priorartdatabase.com/IPCOM/000138556.
Author Unknown, “Double 108Mbps Wireless PC Card (WG511U),” PC Connection, Copyright: 2006, 2 pages http://www.pcconnection.com/ProductDetail?sku=5373172&SourceID=k40132, 2006.
Author Unknown, “Extendex Series: ST-C5DVI-150 150 Foot DVI Video Extender Installation and Operation Manual Software Version 1.2 ,” Network Technologies Incorporated, Oct. 4, 2006, 11 pages.
Author Unknown, “Global-Link Product Manual,” Logical Solutions, Inc., Rev. C., Jan. 2005, 68 pages.
Author Unknown, “Global-Link: KVM Over IP Overview,” Thinklogical, Retrieved Jul. 13, 2007, 1 page, http://www.thinklogical.com/products/globalLink.php.
Author Unknown, “HDMI CAT-5 Extreme User Manual,” Gefen,Inc., Copyright: 2006, 16 pages.
Author Unknown, “HDTC Extender,” XtendexTM, Copyright: 2005, 2 pages.
Author Unknown, “Internet Cache Protocol,” Wikipedia—The Free Encyclopedia, Modified: Sep. 21, 2006, Retrieved: Jun. 15, 2007, 2 pages, http://en.wikipedia.org/wiki/internet—cache—protocol.
Author Unknown, “Introducing the World's First ‘Legal’ HDMI Distribution Amp with HDCP on Every Port!,” PureLink Digital Extender, Retrieved, Jul. 13, 2007, 2 pages, http://www.dtrovision.com.
Author Unknown, “Kaleidescape—Home,” Kaleidescape, Inc., Copyright 2007, 1 page, www.kaleidescape.com.
Author Unknown, “Overview: Life is Good . . . with Media Max,” MediaMax Axonix Corporation, Copyright: 2007, 2 pages, www.axionix.com/mediamax/.
Author Unknown, “SnapStream: PC DVR and TV turner,” SnapStream Media, Copyright: 2007, 1 page, http://www.snapatream.com.
Author Unknown, “Squid Cache,” Wikipedia—The Free Encyclopedia, May 18, 2007, 3 pages, http://en.wikipedia.org/wiki/squid—cache.
Degermark, Mikael, et al., “Low-loss TCP/IP Header Compression for Wireless Networks,” MOBICOM '96, Proceedings of the Second Annual International Conference on Mobile Computing and Networking, Rye, New York, USA, Nov. 10-12, 1996, ACM 1996, 14 pages.
Dittman, Jana et al., “Robust MPEG Video Watermarking Technologies,” 1998 Proceedings of the Sixth ACM Conference on Multimedia, Copyright: 1998, 10 pages.
Fridrich, Jiri, “Applications of Data Hiding in Digital Images,” Tutorial for the ISPACS '98 Conference in Melbourne, Australia, Nov. 4-6, 1998, 33 pages.
Gwertzman, James et al., “Analysis of Geographical Push-Caching,” Proceedings of the 5th IEEE Workshop on Hot Topics in Operating Systems, Copyright: 1997, 20 pages.
Judge, Paul et al., “WHIM: Watermarking Multicast Video with a Hierarchy of Intermediaries,” 10th International Workshop on Network and Operation System Support for Digital Audio and Video (NOSSDAV), May 12-14, 2002, 9 pages.
Koch, E. et al., “Towards Robust and Hidden Image Copyright Labeling,” In Proceedings of 1995 Workshop on Nonlinear Signal and Image Processing, Jun. 20-22, 1995, pp. 1-4.
Raisinghani, Vijay T. et al., “ECLAIR: An Efficient Cross Layer Architecture for Wireless Protocol Stacks,” 5th World Wireless Congress, May 25-28, 2004, 6 pages, San Francisco, CA.
Recio, R. et al., “A Remote Direct Memory Access Protocol Specification,” Remote Direct Data Placement Work Group, Sep. 8, 2006, 82 pages.
Setton, Eric et al., “Cross-Layer Design of Ad Hoc Networks for Real-Time Video Streaming,” IEEE Wireless Communications, vol. 12, issue 4, Aug. 2005, 7 pages.
Srivastava, Vineet et al., “Cross-Layer Design: A Survey and the Road Ahead,” IEEE Communications Magazine, Dec. 2005, pp. 112-119.
Non-Final Office Action for U.S. Appl. No. 11/536,135, mailed Dec. 19, 2008, 19 pages.
Final Office Action for U.S. Appl. No. 11/536,135, mailed Apr. 29, 2009, 20 pages.
Non-Final Office Action for U.S. Appl. No. 11/536,135, mailed Aug. 10, 2009, 18 pages.
Final Office Action for U.S. Appl. No. 11/536,135, mailed Jan. 29, 2010, 20 pages.
Non-Final Office Action for U.S. Appl. No. 11/536,135, mailed Jul. 12, 2011, 21 pages.
Final Office Action for U.S. Appl. No. 11/536,135, mailed Jan. 25, 2012, 17 pages.
Notice of Allowance for U.S. Appl. No. 11/536,135, mailed Aug. 22, 2013, 13 pages.
Related Publications (1)
Number Date Country
20140109136 A1 Apr 2014 US
Continuations (1)
Number Date Country
Parent 11536135 Sep 2006 US
Child 14136553 US