Method and system for preloading suggested content onto digital video recorder based on social recommendations
Systems and methods provide users with suggested content that is preloaded on a media player. The suggested content is selected based on playback data from individuals and groups in a social network or playback data from anonymous users, or explicit suggestions from peers of the user in the social network, such as friends or family. The user may set aside space on their media player, such as a DVR or PC hard drive. A service then populates this space with suggested content. In addition, systems and methods allow users to track and create recommendations of content and to automatically schedule recording of showings of this content. The user may automatically record everything suggested, or require the user make selections. Systems and methods also provide for automatic selections, based on content type, time of day, or a random pattern.
Latest Red Hat, Inc. Patents:
1. Field of the Invention
The present invention relates to online services and communications tools and, more particularly, to social networks.
2. Background of the Invention
In its short history, Internet usage has been mainly driven by portals and search engines, such as Yahoo! and Google. Recently, the rapid growth of social networking sites, such as MySpace and Facebook, has revealed a new trend of Internet usage. Social networking generally relates to services and tools that help users maintain and expand their circles of friends usually by exploiting existing relationships. Social networking sites have shown potential to become the places on the Internet where many people spend most of their time, thus making these sites the main entry point for online activity Often times, these social networking sites can become the focal point of sharing information, such as links, multimedia, music, and the like.
In general, social networking sites and other online services of the Internet offer a mix of features and tools, such as message boards, games, journals or web logs (“blogs”). Many of these sites try to build communities around multi-media or popular culture, such as television, film, music, etc. These sites and their features are designed to keep users clicking on advertising-supported pages of the site. Thus, the known social networking sites employ a closed platform of services that attempt to keep their user-base captive to the site.
The Internet is now crowded with a large number of social networking sites and sharing tools. For example, the recent supremacy of iTunes has triggered a plethora of music service offerings. As another example, the recent success of YouTube and Google Video has sparked an explosion of video-sharing sites. Therefore, most users typically utilize multiple social networking sites and maintain separate accounts on these services.
Unfortunately, it has become difficult for users to share and highlight content across their multiple social networking services. Accordingly, it would be desirable to provide methods and systems that allow users to suggest content that is of high or low value with their social network.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. In the figures:
Embodiments of the present invention provide users with suggested content that is preloaded on a media player. The suggested content is selected based on playback data from individuals and groups in a social network or playback data from anonymous users, or explicit suggestions from peers of the user in the social network (such as friends or family). The user may set aside space on their media player, such as a DVR or PC hard drive. A service then populates this space with suggested content. For example, the user may elect to populate this space with shows that their friends are watching, automatically. In addition, embodiments of the present invention allow users to track and create recommendations of content and to automatically schedule recording of showings of this content. The user may automatically record everything suggested, or require the user make selections. The present invention also provides for automatic selections, based on content type, time of day, or a random pattern. Finally, a user may acknowledge that they have watched a show suggested by their friends and automatically or manually send feedback about that show.
Reference will now be made in detail to the exemplary embodiments of the invention, which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
Client 102 provides a user interface for system 100. Client 102 may be implemented using a variety of devices and software. For example client 102 may be implemented on a personal computer, workstation, or terminal. In addition, client 102 may run under an operating system, such as the LINUX operating system, the Microsoft™ Windows operating system, and the like. Client 102 may also operate through an Internet browser application, such as Firefox by Mozilla, Internet Explorer by Microsoft Corporation, or Netscape Navigator by Netscape Communications Corporation.
One skilled in the art will also recognize that client 102 may be implemented with various peripheral devices, such as a display, one or more speakers, and other suitable devices. Client 102 may also be implemented with various peripherals for accepting input from a user, such as a keyboard, a mouse, and the like. Although
Services 104 are the applications and services that users of system 100 already use. Services 104 may be implemented on one or more servers that are well known to those skilled in the art. Rather than recreating functionality, open overlay service 106 merely interfaces services 104 and allows users to seamlessly continue using the services, such as social networking services, instant messaging, etc., that they currently use. Examples of services 104 include iTunes, Yahoo Music Engine, MySpace, Friendster, AOL Instant Messenger, Yahoo! Messenger, etc. Any sort of online service may be incorporated into the context provided by open overlay service 106.
Open overlay service 106 serves as a social network service and stores, manages, and provides access control to the various services and social networks of clients 102. In general, open overlay service 106 is essentially a web site and application service that stores and forwards information shared by users, as well as user profiles and social network information. Open overlay service 106 may be hosted as a public instance, similar in fashion to a service, such as Wikipedia. In addition, open overlay service 106 may provide various application programming interfaces that have an open specification so that anyone can create an interface.
For example, open overlay service 106 may process requests to retrieve an object, document, image file, web page, and the like. Open overlay service 106 may be implemented using a variety of devices and software. For example, open overlay service 106 may be implemented as a web site running on one or more servers that support various application programs and stored procedures.
The components of system 100 may be coupled together via network 108. Network 108 may comprise one or more networks, such as a local area network, the Internet, or other type of wide area network. In addition, network 108 may support a wide variety of known protocols, such as the transport control protocol and Internet protocol (“TCP/IP”) and hypertext transport protocol (“HTTP”).
Operating system (OS) 200 is an integrated collection of routines that service the sequencing and processing of programs and applications running in open overlay service 106. OS 200 may provide many services, such as resource allocation, scheduling, input/output control, and data management. OS 200 may be predominantly software, but may also comprise partial or complete hardware implementations and firmware. Well known examples of operating systems that are consistent with the principles of the present invention include the Linux operating system, the UNIX operating system. In addition, OS 200 may operate in conjunction with other software, such as an application server, such as JBoss, to implement various features of open overlay service 106.
Application server 202 provides the logic for analyzing and managing the operations of open overlay service 106. As previously noted, application server 202 may be written in a variety of programming languages, such as C, C++, Java, etc.
For example, one responsibility of application server 202 may be managing the various identifies of the users of open overlay service 106. As noted previously, a single person may have multiple identities that they use for various online services and social networks. For example, a person named, John Smith, may use jsmith@ domain.com as an identity one service, but use smithj@domain2.com as his identity on another service.
In one embodiment, in order to track the various users of open overlay service 106, application server 202 may assign each user a unique identifier, such as a numeric identifier. Application server 202 may then utilize this unique identifier with the identity resources (i.e., email address, account names, screen names, etc.) used by services 104 to identify a person. In some embodiments, application server 202 generates a graph of each social network within open overlay service 106 in terms of person's names and the identity resources from the point of view of a particular user based on what is trusted by that user.
For example, given information about a person's name, their unique identifier assigned by application server 202, and associations to identity resources trusted by other users, application server 202 can generate a list of person names and identity resources (i.e., email address, account names, etc.) that should be visible to a particular user. Hence, the particular user will only be allowed to see identity resources they happen to (or only) know about that user and identity resources that have been verified by application server 202. For example, a user A may have a unique identifier of 2345, and email address #1 and email address #2 as identity resources. A user B may only know about email address #1 for user A. Meanwhile, a user C may similarly only know about email address #2 for user A. Thus, for user B, application server 202 will only allow user B to view and use email address #1 as an identity resource for user A. Likewise, application server 202 will only allow user C to view and use email address #2 as an identity resource for user A. However, if user A subsequently explicitly indicates to application server 202 that both users B and C can be trusted, then users B and C will then be also allowed to view both email addresses #1 and 2, as well. The primary uses of this information by open overlay service 106 may be for sharing a link with person by addressing that person either by an email address or by a short nickname, or for viewing a list of persons in open overlay service 106 that they think they know.
Application server 202 may also determine what information of a user should be public or private. In some embodiments, application server 202 may default to making information public, but provide an option, such as a checkbox, that allows the user to designate information as private. Application server 202 may also employ per page settings, such as all private or all public. Other privacy policies may be implemented by application server 202.
Application server 202 may further provide various search features. For example, application server 202 may allow users to search for other users based on various criteria, such as age, gender, school, etc. Application server 202 may also allow searches for various resources, such as email addresses, topics, links, etc.
Messaging server 204 manages communications between open overlay service 106 and clients 102 via network 108. For example, messaging server 204 may be configured to periodically poll clients 102 on a regular basis and have them request information from services 104. Messaging server 204 may be implemented based on well-known hardware and software and utilize well-known protocols, such as TCP/IP, hypertext transport protocol, etc.
Messaging server 204 may be configured to handle a wide variety of data and may handle data that is in any format. For example, information from clients 102 may be in the form of an extensible markup language (XML) file or a network location, such as a uniform resource locator (URL) on the Internet. Alternatively, messaging server 204 may be configured to obtain information from services 104 directly in a peer-to-peer fashion.
Messaging agent 206 serves as an interface between open overlay service 106 and online services 104 and may operate to monitor the activity of clients 102 at these services. In particular, messaging agent 206 may be a relatively small and focused computer application (or “bot”) that runs continuously, in the background simultaneously for each of clients 102, as other programs are being run, and responds automatically to activity on services 104 that may be of interest to clients 102, such as new messages, postings, and the like.
Messaging agent 206 may be created by open overlay service 106 (i.e., by application server 202) for the benefit of the users at clients 102. Alternatively, for example, messaging server 204 may send information to clients 102 upon request, perform automated searches, or monitor messages or events at services 104.
In one embodiment, messaging server 204 and/or messaging agent 206 may work in conjunction to perform client-side data scraping on services 104. Client-side data scraping may be desirable in some instances where services 104 refuse or block a direct interface with open overlay service 106. For example, MySpace and AOL's instant messaging service may be implemented as one of services 104, but is known to block proxy requests for a client.
Client-side data scraping may be initiated by messaging server 204 or using information provided by messaging server. Messaging server 204 may poll client overlay client 302 to trigger a request to one of services 104. Accordingly, overlay client 302 may cause one of service applications 306 to interface with service 104 and request data from that service, such as web page refresh. Since the request originated from client 102, service 104 will provide a response. Overlay client 302 may detect this response and forward it to messaging server 204. Messaging server 204 may then pass this response. Of course, the polling may be configured at overlay client 302 based on information provided to messaging server 204.
Messaging server 204 evaluates the response and determines if a notification event is needed. If notification is needed, messaging server 204 send a message to overlay client 302. The notification may then be displayed to the user using, for example, browser 304 or service application 306.
One application of client-side data scraping may be used to detect when messages or postings have been entered on one of services 104. For example, on MySpace, users often repeatedly refresh their pages in anticipation of receiving a post or message from a friend. With client-side data scraping, open overlay service 106 may automatically perform this function, and more conveniently, indicate when the user has received activity on their MySpace page. This notification may appear in the form of a pop-up bubble or may be displayed as a link on the user's page in open overlay service 106. Of course, other applications of client-side data scraping are consistent with the principles of the present invention.
Web server 208 provides a communications interface between open overlay service 106, clients 102, and services 104. For example, web server 208 may be configured to provide information that indicates the status of client 102. Such communications may be based on well known protocols and programming languages, such as HTTP, TCP/IP and Java. Interfaces provided by web server 208 may be implemented using well known Internet technologies, such as web pages, which are well known to those skilled in the art.
User database 210 maintains information identifying users and clients 102. User database 210 may be implemented using well known database technology, such as relational databases, or object oriented databases.
For example, user database 210 may include information indicating one or more operating systems and applications installed on clients 102 as well as services subscribed to by users. User database 210 may also comprise information related to authenticating a user determining the respective rights of a user relative to other users. For example, a user may select various groups or channels of content in which they are interested in receiving information. User database 210 may further include information that indicates the permissions and delivery of the information to clients 102. Other information that may be included in user database 210 may comprise information, such as system and individual permissions of clients 102 on services 104, activation keys, registration information, and payment information (such as credit card information).
Furthermore, user database 210 may include other information related to the manner in which open overlay service 106 communicates with clients 102. For example, this information may relate to periodicity of notifications, email addresses, format of the information, and the like. User database 210 may include data structures to log the activities and transactions of its users. Activities, such as recent links, history of operations, etc., that may be logged in user database 210 are well known to those skilled in the art.
Operating system (OS) 300 is an integrated collection of routines that service the sequencing and processing of programs and applications running in open overlay service 106. OS 300 may provide many services, such as resource allocation, scheduling, input/output control, and data management. OS 300 may be predominantly software, but may also comprise partial or complete hardware implementations and firmware. Well known examples of operating systems that are consistent with the principles of the present invention include Mac OS by Apple Computer, the Windows family of operating systems by Microsoft Corporation, and the Linux operating system.
Overlay client 302 maintains an inventory of the software and service applications 306 installed on client 102 and archives one or more states of activity on client 102. In some embodiments, overlay client 302 may be configured to periodically connect to open overlay service 106 and perform various operations requested by open overlay service 106.
Browser 304 is an application that runs on client 102 and provides an interface to access information on network 108, such as information on services 104. Browser 304 may be implemented as well known programs, such as Mozilla Firefox, Microsoft Internet Explorer, Netscape Navigator, and the like.
Service applications 306 run on client 102 to support the services provided by services 104. For example, service applications 306 may be applications, such as a browser, an instant messaging client, a music player (such as iTunes), and the like that are provided from services 104. Other examples for applications 306 are well known to those skilled in the art.
User data cache 308 provides a cache that indicates the activity of a user at client 102. For example, user data cache 308 may include information that indicates documents, such as HTML pages, images, URL links, web site access times, and the like.
In order to illustrate some of the features of open overlay service 106 that provide a live social context, several examples of features will now be described.
Initially, users may reserve some space on their DVRs 400 or on clients 102. Open overlay service 106 then populates this space with content based on suggestions and other users (such as friends of the user) are watching, automatically. In contrast to known recommendation techniques, like TiVo's existing “Tivo Recommends”, open overlay service 106 populates its suggestions based on feedback from the social network, not a global recommender engine. This feature allows the suggestions to be more accurate and more relevant to a user.
Over time, open overlay service 106 may keep track in database 210 of what the users watch and create recommendations of content based on that history. Open overlay service 106 also lets users explicitly suggest content and enables automatic scheduling to record showings of this content. Clients 102 may be configured to have DVRs 400 autorecord all suggested content, such as content suggested by a group of friends watch, or some subset of the suggestions, such as a random selection or filtering. For example, clients 102 may record based on current scheduled recordings, a history of spontaneous watches by the user, querying through a social recommendation engine provided by open overlay service 106, and explicit sharing of a show by one user to another.
In general, open overlay service 106 collects suggestions from its users and may preload the suggested content. Open overlay service 106 may publish suggestions publicly to all or most of the users or only to the group that contributed the suggestions. Open overlay service 106 may publish this information on a small scale (“most popular among my friends”) or a larger scale (“most popular among cable viewers this week”).
For purposes of illustration,
Initially, Alice, Bob, and Charlie may watch content independently on their respective DVRs 400. During this viewing, their playback data may be monitored and collected. For example, overlay clients 302 may be configured to periodically poll DVRs 400 to collect this playback data. Alternatively, DVRs 400 may have their own application, such as one of service applications 306. For example, one of service applications 306 may be configured to retrieve program schedule information from service 104 over network 108. Accordingly, overlay client 302 may operate in conjunction with service application 306 to obtain playback data of the users.
Of note, the playback data may be collected actively or passively. For example, the users may be interactively prompted to tag a show as either high value or low value. Users may also actively tag various segments of a show. One skilled in the art will recognize that any type of segment, such as commercials, highlights, scenes, etc., may be tagged by the users.
Alternatively, playback data may be passively collected from the user. That is, the users'playback behavior is merely observed without requesting or prompting. For example, the playback data may simply indicate which shows the user played or skipped and where the user paused, rewound, skipped forward, etc.
Clients 102 then send this playback data to open overlay service 106. Open overlay service 106 may, for example, periodically poll for this playback data from clients 102. Alternatively, clients 102 may be configured to provide their playback data at defined intervals or in real-time as it's collected.
In addition, open overlay service 106 may collect program information 404 from the various providers via service 104. This information allows open overlay service 106 to correlate and aggregate the various playback data for the same content. For example, the same show or movie may be played at different times by different providers. Thus, open overlay service 106 may operate across different providers and allow users to share suggested content across different providers.
Open overlay service 106 may aggregate the playback data, either at a central location in database 210 or by broadcasting results to multiple locations, such as service application 104. The aggregation could be done at a small scale (“most popular among my friends”) or a larger scale (“most popular among all viewers this week”) within open overlay service 106.
Application server 202 may then process the playback data collected from clients 102 and program information 404 to determine suggested content that are of high or low interest to the users. Application server 202 may determine different suggestions for different social networks. For example, application server 202 may determine suggestions for different families or groups of friends. This allows open overlay service 106 to provide distinct sharing among its social networks. Alternatively, application server 202 may aggregate playback data from all of its users. Such information may be useful for certain types of content, such as sports, family programming, etc.
Application server 202 then queries database 210 to retrieve a list of users and groups that may be interested in the suggested content. Clients 102 may selectively choose suggestions. This feature allows various social networks to selectively choose which suggestions they receive. For example, sports shows may be of interest to one group of users or social network. In contrast, content with a particular actor or musical group may be of interest to another group of users or social network.
For example, in the scenario shown in
Application server 202 may then preload the suggested content to Alice, Bob, and Charlie on their respective DVRs 400. The suggested content may be sent to overlay client 302, or as directly to service application 306 for DVRs 400. The segment information may be sent periodically, on-demand, etc. based on the preferences of the clients 102. One skilled in the art will recognize that there is wide variety of ways that the segment information can be distributed. DVRs 400 may then present the suggested content using well known techniques and menus.
Application server 202 may also filter the suggested content preloaded to DVRs 400 at clients 102 based on that client's profile or other criteria. For example, application server 202 may filter suggestions sent to Alice based on various criteria, such as Alice's age, Alice's location, Alice's other activities in open overlay service 106 as indicated in cache 308, etc. For example, segment information that contains adult material may be filtered from being sent to Alice.
Furthermore, application server 202 may send various accompanying information with the suggestions. For example, this accompanying information may be information that indicates comments by users about the suggestions, the number of users that made the suggestion, descriptive phrases, timing information, duration of the suggested content, and the like.
Finally, a user may acknowledge that they have watched a show suggested by their friends and automatically or manually send feedback about that show. This acknowledgement may be sent via a variety of ways, such as instant message, email, etc., through open overlay service 106 as described above.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Claims
1. A method of recommending content to a user, said method comprising:
- executing an open overlay service on a device of the user, wherein the open overlay service executes: determining suggested content for the user based on playback data collected from a social network service of the user and a programming schedule of the content, wherein determining suggested content for the user comprises: receiving information that indicates scheduled recordings of other users in the social network of the user; and determining suggested content based on the scheduled recordings of the other users; automatically selecting a subset of the suggested content for the user; receiving, from the user, a request to reserve storage space on the device of the user for the subset of the suggested content; reserving the storage space on the device of the user in response to receiving the request; and scheduling a recording of the subset of the suggested content on the storage space on the device of the user, wherein the content is media content.
2. The method of claim 1, wherein determining suggested content for the user further comprises:
- receiving playback data from users of the social network service; and
- determining suggested content from the received playback data.
3. The method of claim 1, wherein determining suggested content for the user further comprises:
- receiving playback data passively collected from users of the social network service; and
- determining suggested content from the received playback data.
4. The method of claim 1, wherein determining suggested content for the user further comprises:
- receiving suggestions from other users in a social network of the user; and
- determining suggested content from the suggestions.
5. The method of claim 1, wherein determining suggested content for the user further comprises:
- determining a history of content requested by the user and a social network of the user; and determining suggested content based on the history of content requested by the user and the user's social network.
6. The method of claim 1, wherein the subset of the suggested content comprises content suggested by other users of a social network of the user.
7. The method of claim 1, wherein the subset of the suggested content comprises content that matches criteria specified by the user.
8. The method of claim 1, further comprising:
- determining if the user has viewed the selected subset of suggested content.
9. A computer readable storage device comprising executable program code to configure a computer to perform the method of claim 1.
10. An apparatus for providing content to a user, said apparatus, comprising:
- a memory adapted to store a user database comprising information about users; and
- a processor adapted to execute an open overlay service, wherein the open overlay service is configured to determine suggested media content for the user based on playback data collected from a social network service of the user and a programming schedule of the media content, automatically select a subset of the suggested media content for the user, receive, from the user, a request to reserve storage space on a device of the user for the subset of the suggested media content, reserve the storage space on the device of the user in response to receiving the request; and schedule a recording of the subset of the suggested media content on the storage space on the device of the user,
- wherein determining suggested media content for the user comprises: receiving information that indicates scheduled recordings of other users in the social network of the user; and determining suggested media content based on the scheduled recordings of the other users.
| 6018768 | January 25, 2000 | Ullman et al. |
| 6317784 | November 13, 2001 | Mackintosh et al. |
| 6519648 | February 11, 2003 | Eyal |
| 6526411 | February 25, 2003 | Ward |
| 6553180 | April 22, 2003 | Kikuchi et al. |
| 6714722 | March 30, 2004 | Tsukidate |
| 6763345 | July 13, 2004 | Hempleman et al. |
| 6957398 | October 18, 2005 | Nayeri |
| 7069308 | June 27, 2006 | Abrams |
| 7345232 | March 18, 2008 | Toivonen et al. |
| 7426537 | September 16, 2008 | Lee et al. |
| 7684815 | March 23, 2010 | Counts et al. |
| 7698301 | April 13, 2010 | Lourdeaux |
| 7730216 | June 1, 2010 | Issa et al. |
| 7886010 | February 8, 2011 | Shankar |
| 20020016960 | February 7, 2002 | Yamato et al. |
| 20020042915 | April 11, 2002 | Kubischta et al. |
| 20020120925 | August 29, 2002 | Logan |
| 20020156852 | October 24, 2002 | Hughes et al. |
| 20020188947 | December 12, 2002 | Wang et al. |
| 20020194598 | December 19, 2002 | Connelly |
| 20030014419 | January 16, 2003 | Clapper |
| 20030028595 | February 6, 2003 | Vogt et al. |
| 20030028892 | February 6, 2003 | Gewickey et al. |
| 20030050976 | March 13, 2003 | Block et al. |
| 20030093790 | May 15, 2003 | Logan et al. |
| 20030115274 | June 19, 2003 | Weber |
| 20030115585 | June 19, 2003 | Barsness et al. |
| 20030135513 | July 17, 2003 | Quinn et al. |
| 20040078825 | April 22, 2004 | Murphy |
| 20040083273 | April 29, 2004 | Madison et al. |
| 20040128624 | July 1, 2004 | Arellano et al. |
| 20050004985 | January 6, 2005 | Stochosky |
| 20050022251 | January 27, 2005 | Ohnuma et al. |
| 20050038819 | February 17, 2005 | Hicken et al. |
| 20050097173 | May 5, 2005 | Johns et al. |
| 20050114340 | May 26, 2005 | Huslak et al. |
| 20050132401 | June 16, 2005 | Boccon-Gibod et al. |
| 20050138659 | June 23, 2005 | Boccon-Gibod et al. |
| 20050210285 | September 22, 2005 | Williams |
| 20050251411 | November 10, 2005 | Ishii et al. |
| 20050267766 | December 1, 2005 | Galbreath et al. |
| 20050278377 | December 15, 2005 | Mirrashidi et al. |
| 20060013566 | January 19, 2006 | Nakamura |
| 20060020614 | January 26, 2006 | Kolawa et al. |
| 20060041902 | February 23, 2006 | Zigmond |
| 20060143236 | June 29, 2006 | Wu |
| 20060190824 | August 24, 2006 | Montulli et al. |
| 20060195462 | August 31, 2006 | Rogers |
| 20060195479 | August 31, 2006 | Spiegelman et al. |
| 20060195516 | August 31, 2006 | Beaupre |
| 20060195525 | August 31, 2006 | Page et al. |
| 20060195532 | August 31, 2006 | Zlateff et al. |
| 20060212906 | September 21, 2006 | Cantalini |
| 20060239131 | October 26, 2006 | Nathan et al. |
| 20060242234 | October 26, 2006 | Counts et al. |
| 20060242554 | October 26, 2006 | Gerace et al. |
| 20060253584 | November 9, 2006 | Dixon et al. |
| 20060277455 | December 7, 2006 | Yamada et al. |
| 20060288041 | December 21, 2006 | Plastina et al. |
| 20070078993 | April 5, 2007 | Issa |
| 20070106627 | May 10, 2007 | Srivastava et al. |
| 20070106672 | May 10, 2007 | Sighart et al. |
| 20070146820 | June 28, 2007 | Asazu et al. |
| 20070157105 | July 5, 2007 | Owens et al. |
| 20070161382 | July 12, 2007 | Melinger et al. |
| 20070162432 | July 12, 2007 | Armstrong et al. |
| 20070168543 | July 19, 2007 | Krikorian et al. |
| 20070169165 | July 19, 2007 | Crull et al. |
| 20070174389 | July 26, 2007 | Armstrong et al. |
| 20070192299 | August 16, 2007 | Zuckerberg et al. |
| 20070220092 | September 20, 2007 | Heitzeberg et al. |
| 20070220554 | September 20, 2007 | Barton et al. |
| 20070255785 | November 1, 2007 | Hayashi et al. |
| 20070266401 | November 15, 2007 | Hallberg |
| 20070277110 | November 29, 2007 | Rogers et al. |
| 20070282949 | December 6, 2007 | Fischer et al. |
| 20070282950 | December 6, 2007 | Fischer et al. |
| 20080010372 | January 10, 2008 | Khedouri et al. |
| 20080040474 | February 14, 2008 | Zuckerberg et al. |
| 20080052371 | February 28, 2008 | Partovi et al. |
| 20080065604 | March 13, 2008 | Tiu et al. |
| 20080092054 | April 17, 2008 | Bhumkar et al. |
| 20080092168 | April 17, 2008 | Logan et al. |
| 20080092182 | April 17, 2008 | Conant |
| 20080104521 | May 1, 2008 | Dubinko et al. |
| 20080133475 | June 5, 2008 | Fischer |
| 20080133593 | June 5, 2008 | Clark |
| 20080133638 | June 5, 2008 | Fischer et al. |
| 20080133649 | June 5, 2008 | Pennington et al. |
| 20080133658 | June 5, 2008 | Pennington |
| 20080133696 | June 5, 2008 | Hanebeck |
| 20080133737 | June 5, 2008 | Fischer et al. |
| 20080133763 | June 5, 2008 | Clark et al. |
| 20080134053 | June 5, 2008 | Fischer |
| 20080134054 | June 5, 2008 | Clark et al. |
| 20080201376 | August 21, 2008 | Khedouri et al. |
| 20080320139 | December 25, 2008 | Fukuda et al. |
| 20090019374 | January 15, 2009 | Logan et al. |
| 20100162324 | June 24, 2010 | Mehta et al. |
Type: Grant
Filed: Nov 30, 2006
Date of Patent: Nov 15, 2011
Patent Publication Number: 20080134039
Assignee: Red Hat, Inc. (Raleigh, NC)
Inventors: Donald Fischer (Westford, MA), Havoc Pennington (Westford, MA), Bryan Clark (Westford, MA)
Primary Examiner: Ting Lee
Attorney: Lowenstein Sandler PC
Application Number: 11/565,005
International Classification: G06F 3/00 (20060101); H04N 7/173 (20060101); H04N 5/76 (20060101);
