BACKGROUND INFORMATION

Digital video recording (â€œDVRâ€ ) devices allow users to record media content programs (e.g., television programs, etc.) and then view or otherwise experience the recorded media content programs. For example, a user may create a DVR schedule that includes instructions for a DVR device to record certain media content programs as they are broadcast or otherwise provided for presentation by a media content provider. The user may then view the recorded media content programs at his or her convenience.

Unfortunately, it is often difficult and/or time-consuming for a user to populate a DVR schedule with media content programs that he or she would most enjoy viewing. For example, a user may have access to hundreds or even thousands of channels by way of a set-top box device, but be interested in recording only a small fraction of the media content programs offered by way of these channels. Locating and including these media content programs in a DVR schedule can be cumbersome and time-consuming for the user, and can often lead to missed viewing opportunities.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various embodiments and are a part of the specification. The illustrated embodiments are merely examples and do not limit the scope of the disclosure. Throughout the drawings, identical or similar reference numbers designate identical or similar elements.

FIG. 1 illustrates an exemplary DVR schedule collaboration system according to principles described herein.

FIG. 2 shows an exemplary configuration wherein a master DVR schedule may be created based on a plurality of DVR schedules associated with a plurality of users according to principles described herein.

FIG. 3 shows an exemplary table that lists various media content programs that may be included in one or more DVR schedules upon which a master DVR schedule is based according to principles described herein.

FIGS. 4-7 illustrate various interfaces that may be presented to a user according to principles described herein.

FIG. 8 shows an exemplary implementation of the DVR schedule collaboration system of FIG. 1 according to principles described herein.

FIG. 9 illustrates an exemplary DVR schedule collaboration method according to principles described herein.

FIG. 10 illustrates another exemplary DVR schedule collaboration method according to principles described herein.

FIG. 11 illustrates an exemplary computing device according to principles described herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

DVR schedule collaboration methods and systems are described herein. As will be described below, a DVR schedule collaboration system may 1) maintain data representative of a plurality of DVR schedules associated with (e.g., created by) a plurality of users, 2) create a master DVR schedule based on the plurality of DVR schedules, and 3) facilitate creation of a personal DVR schedule by a user in accordance with the master DVR schedule and/or one or more of the DVR schedules associated with the plurality of users. As will be described below, the personal DVR schedule may include instructions for a DVR device associated with the user to record one or more media content programs during one or more time slots (e.g., during one or more broadcast time slots).

The methods and systems described herein may allow a user to effectively and efficiently populate a DVR schedule with media content programs that are of interest to the user. To illustrate, a particular user may subscribe to a media content distribution service (e.g., a subscriber television network service) and acquire (e.g., lease or buy) a DVR device (e.g., a set-top box device with DVR capabilities) to access media content provided by the media content distribution service. Upon acquiring the DVR device, the user may desire to create a personal DVR schedule that governs a recording operation of the DVR device (e.g., by specifying a plurality of media content programs available by way of the media content distribution service that are to be recorded by the DVR device). However, it may be difficult and/or time-consuming for the user to manually locate media content programs of interest to the user and/or manually schedule media content programs for recording by the DVR device.

Hence, in accordance with the methods and systems described herein, the user may select an option to access (e.g., view) a master DVR schedule that, for example, includes a set of â€œmost popularâ€ media content programs as selected by a community of users (e.g., a group of subscribers to the media content distribution service). The user may additionally or alternatively access one or more DVR schedules created by one or more other users (e.g., one or more other subscribers to the media content distribution service). By accessing the master DVR schedule and/or the one or more DVR schedules created by the one or more other users, the user may readily identify and select media content programs that are potentially of interest to the user for inclusion in the user's personal DVR schedule. For example, the user may select an option to use the master DVR schedule or a DVR schedule associated with another user as the user's personal DVR schedule. Other manners in which the user may create a personal DVR schedule based on the master DVR schedule and/or one or more DVR schedules associated with other users will be described in more detail below.

As used herein, the term â€œmedia content programâ€ may refer to any television program, on-demand media program, pay-per-view media program, broadcast media program (e.g., broadcast television program), multicast media program (e.g., multicast television program), narrowcast media program (e.g., narrowcast video-on-demand program), IPTV media content, advertisement, video, movie, audio program, radio program, or any segment, component, or combination of these or other forms of media content that a user may access by way of a DVR device. A â€œDVR deviceâ€ may include any device or combination of devices configured to provide DVR functionality. For example, a DVR device may include a set-top box device, a receiver, a personal computer, a mobile device (e.g., a mobile phone and/or tablet computer), a personal-digital assistant device, a gaming device, a television device, a server, etc. A DVR device may be local (i.e., located within a premises of a user) or remote (e.g., located remote from a premises of a user).

FIG. 1 illustrates an exemplary DVR schedule collaboration system 100 (â€œsystem 100â€ ). As shown, system 100 may include, without limitation, a DVR schedule management facility 102, a personalization facility 104, and a storage facility 106 selectively and communicatively coupled to one another. Storage facility 106 may be configured to maintain DVR schedule data 108 generated and/or used by DVR schedule management facility 102, and personalization data 110 generated and/or used by personalization facility 104. Storage facility 106 may maintain additional or alternative data as may serve a particular implementation. It will be recognized that although facilities 102-106 are shown to be separate facilities in FIG. 1, any of facilities 102-106 may be combined into fewer facilities, such as into a single facility, or divided into more facilities as may serve a particular implementation.

DVR schedule management facility 102 may be configured to perform various DVR schedule management operations. For example, DVR schedule management facility 102 may maintain data representative of a plurality of DVR schedules associated with (e.g., created by) a plurality of users. This may be performed in any suitable manner. For example, DVR schedule management facility 102 may receive data representative of the plurality of DVR schedules from the plurality of users and store the received data (e.g., as DVR schedule data 108).

To illustrate, FIG. 2 shows an exemplary configuration 200 in which DVR schedule management facility 102 receives data representative of a plurality of DVR schedules 202 (e.g., DVR schedules 202-1 through 202-N) from a plurality of users 204 (e.g., users 204-1 through 204-N). As shown, each user 204 may be associated with (e.g., use) a DVR device 206 (e.g., DVR devices 206-1 through 206-N). In some examples, each user 204 may use a DVR device 206 to create a DVR schedule 202. For example, user 204-1 may use DVR device 206-1 to create DVR schedule 202-1.

In some examples, each user 204 may publish his or her DVR schedule 202. As used herein, â€œpublishing a DVR scheduleâ€ refers to any action taken by a user to share the DVR schedule with DVR schedule management facility 102 (e.g., by uploading data representative of the DVR schedule to DVR schedule management facility 102). In response to users 204 publishing DVR schedules 202, data representative of each DVR schedule 202 may be transmitted to DVR schedule management facility 102 (e.g., by DVR devices 206), as illustrated by arrows 208-1 through 208-N. DVR schedule management facility 102 may receive the data representative of DVR schedules 202 from the plurality of users and store the received data (e.g., as DVR schedule data 108). It will be recognized that DVR schedule management facility 102 may alternatively receive data representative of DVR schedules 202 in any other manner (e.g., from a device or system other than DVR devices 206).

In some examples, DVR schedule management facility 102 may maintain data representative of a DVR schedule associated with a particular user only if the user elects to publish the DVR schedule. Hence, by choosing not to publish a DVR schedule, a user may keep his or her DVR schedule private.

Once a user has published a DVR schedule, he or she may modify the DVR schedule (e.g., by adding or removing media content programs from the DVR schedule). In some examples, DVR schedule management facility 102 may detect the modification and, based on the modification, update data representative of the DVR schedule as maintained by DVR schedule management facility 102. The detecting and updating may be performed automatically in response to the modification of the DVR schedule by the user. Alternatively, the detecting and updating may only be performed in response to a re-publishing of the DVR schedule by the user.

For example, user 204-1 may remove a certain media content program scheduled for recording from DVR schedule 202-1 (e.g., by accessing DVR device 206-1 and selecting an option to remove the media content program from DVR schedule 202-1). DVR schedule management facility 102 may detect the modification and update data representative of DVR schedule 202-1 as maintained by DVR schedule management facility 102 to reflect the modification made by user 204-1 to DVR schedule 202-1.

DVR schedule management facility 102 may be further configured to create a master DVR schedule based on the plurality of DVR schedules maintained by DVR schedule management facility 102. For example, with reference to FIG. 2, DVR schedule management facility 102 may create a master DVR schedule 210 based on DVR schedules 202.

DVR schedule management facility 102 may create a master DVR schedule based on a plurality of DVR schedules maintained by DVR schedule management facility 102 in any suitable manner. For example, DVR schedule management facility 102 may use the DVR schedules to identify a set of â€œmost popularâ€ media content programs and select the set of most popular media content programs for inclusion in the master DVR schedule. As used herein, a â€œmost popularâ€ media content program refers to a media content program that is included or specified in a relatively high number of DVR schedules upon which the master DVR schedule is based. In other words, a â€œmost popularâ€ media content program has been selected by a relatively high number of users for inclusion in the users' individual DVR schedules. For example, the most commonly specified media content program in DVR schedules 202 may be referred to as the most popular media content program out of all of the media content programs specified in DVR schedules 202. Likewise, the second most commonly specified media content program in DVR schedules 202 may be referred to as the next most popular media content program out of all of the media content programs specified in DVR schedules 202.

DVR schedule management facility 102 may use DVR schedules 202 to identify a set of most popular media content programs (e.g., a predetermined total number of media content programs, a predetermined number of media content programs per time slot, etc.) and select the set of most popular media content programs for inclusion in master DVR schedule 210 in any suitable manner. To illustrate, each DVR schedule 202 may include data specifying a plurality of media content programs selected by a particular user (e.g., a user included in users 204) for recording during a plurality of time slots. As used herein, the term â€œtime slotâ€ refers to a period of time during which a media content program is broadcast or otherwise provided for presentation by a media content distribution service (e.g., in accordance with a predefined broadcast or presentation schedule). DVR schedule management facility 102 may identify a media content program that is most commonly specified in DVR schedules 202 and designate the identified media content program as the most popular media content program. DVR schedule management facility 102 may then select the identified media content program for inclusion in master DVR schedule 210 at a time slot associated with the identified media content program (e.g., at a time slot at which the identified media content program is to be broadcast or otherwise provided for presentation). A next most popular media content program may be identified and selected for inclusion in master DVR schedule 210 in a similar manner. This process may be repeated until each available time slot included in master DVR schedule 210 (e.g., each available time slot during a particular period of time, such as a day or week) is filled with a media content program.

To illustrate, FIG. 3 shows an exemplary table 300 that lists various media content programs (e.g., media content programs labeled â€œprogram Aâ€ through â€œprogram Dâ€ ) that may be included in one or more of DVR schedules 202. It will be recognized that additional or alternative media content programs may be included in one or more of DVR schedules 202 as may serve a particular implementation.

FIG. 3 also shows time slots corresponding to each media content program. For example, table 300 indicates that the media content program labeled â€œprogram Aâ€ is scheduled to be presented each Monday between 3:00 and 4:00 pm, the media content program labeled â€œprogram Bâ€ is scheduled to be presented each Monday between 3:30 and 4:30 pm, the media content program labeled â€œprogram Câ€ is scheduled to be presented each Monday between 4:30 and 5:00 pm, and the media content program labeled â€œprogram Dâ€ is scheduled to be presented each Monday between 5:00 and 6:00 pm.

As mentioned, DVR schedule management facility 102 may determine a frequency of occurrence of each media content program in DVR schedules 202. In other words, DVR schedule management facility 102 may determine how many DVR schedules 202 include each media content program. This information is labeled in FIG. 3 as â€œNumber of Occurrences.â€ For example, table 300 indicates that the media content program labeled â€œprogram Aâ€ is included in ninety-five DVR schedules 202, the media content program labeled â€œprogram Bâ€ is included in ninety-three DVR schedules 202, the media content program labeled â€œprogram Câ€ is included in ninety DVR schedules 202, and the media content program labeled â€œprogram Dâ€ is included in eighty-eight DVR schedules 202. For purposes of this example, it will be assumed that the media content program labeled â€œprogram Aâ€ is the most popular media content program included in DVR schedules 202, the media content program labeled â€œprogram Bâ€ is the second most popular media content program included in DVR schedules 202, the media content program labeled â€œprogram Câ€ is the third most popular media content program included in DVR schedules 202, and the media content program labeled â€œprogram Dâ€ is the fourth most popular media content program included in DVR schedules 202.

Based on the data presented in table 300, DVR schedule management facility 102 may select one or more of the media content programs listed in table 300 for inclusion in master DVR schedule 310. In some examples, DVR schedule management facility 102 may select media content programs for inclusion in master DVR schedule 210 based solely on the number of occurrences of each media content program in DVR schedules 202. In these examples, media content programs may be selected for inclusion in master DVR schedule 210 even if their corresponding time slots overlap. For example, the media content programs labeled â€œprogram Aâ€ and â€œprogram Bâ€ may both be selected for inclusion in master DVR schedule 310 even though their corresponding time slots overlap by thirty minutes. A master DVR schedule that includes overlapping media content programs may be desirable for DVR devices that have a relatively high number of tuners (e.g., more than two tuners).

In some alternative examples, DVR schedule management facility 102 may select media content programs for inclusion in master DVR schedule 210 in a manner such that time slots corresponding to the media content programs do not overlap. For example, with reference to FIG. 3, the media content program labeled â€œprogram Bâ€ may be excluded from being included in master DVR schedule 210 because its corresponding time slot overlaps with that of the media content program labeled â€œprogram Aâ€ . A master DVR schedule that includes non-overlapping media content programs (e.g., a master DVR schedule that is limited to include only non-overlapping media content programs) may be desirable for DVR devices that have a limited number of tuners (e.g., one or two tuners).

In some examples, DVR schedule management facility 102 may personalize a master DVR schedule to a particular user. For example, a user may provide input representative of the recording capabilities of his or her DVR device (e.g., how many tuners the DVR device has). In response, DVR schedule management facility 102 may determine how many media content programs with overlapping time slots may be included in the master DVR schedule.

Additionally or alternatively, DVR schedule management facility 102 may personalize a master DVR schedule to a particular user by identifying and selecting one or more media content programs for inclusion in the master DVR schedule that have a media content attribute specified by the user. As used herein, the term â€œmedia content attributeâ€ may refer to any characteristic of a media content program such as, but not limited to, genre (e.g., soap operas, sporting events, etc.), resolution (e.g., high definition), personnel (e.g., actors, directors, and/or other users associated with the media content program), etc.

To illustrate, a user may desire to access a master DVR schedule that includes media content programs associated with the actor â€œTom Hanksâ€ . Accordingly, the user may provide â€œTom Hanksâ€ as input. In response, DVR collaboration facility 102 may identify media content programs that are associated with â€œTom Hanksâ€ (e.g., by analyzing metadata associated with the media content programs). DVR schedule management facility 102 may then select one or more of the identified media content programs for inclusion in the master DVR schedule.

In another example, a user may wish to access a master DVR schedule that includes media content programs that are categorized as game shows (e.g., â€œThe Price is Rightâ€ , â€œFamily Feudâ€ , â€œJeopardyâ€ , etc.). To do so, the user may provide input representative of the â€œgame showsâ€ category. In response, DVR collaboration facility 102 may identify media content programs that are categorized as being â€œgame showsâ€ and select one or more of the identified media content programs for inclusion in the master DVR schedule.

Additionally or alternatively, DVR schedule management facility 102 may personalize a master DVR schedule to a particular user by allowing the user to select which users' DVR schedules are used to create the master DVR schedule. For example, the user may specify that only those DVR schedules associated with a group of social media contacts of the user are to be used to create the master DVR schedule.

Returning to FIG. 1, personalization facility 104 may be configured to facilitate creation of a personal DVR schedule by a user in accordance with any of the DVR schedules maintained by DVR schedule management facility 102 (e.g., the master DVR schedule and/or one or more of the DVR schedules associated with the plurality of users). This may be performed in any suitable manner. For example, personalization facility 104 may be configured to present the user with an interface (e.g., a graphical user interface (â€œGUIâ€ )) that allows the user to selectively access the master DVR schedule and the one or more DVR schedules associated with the plurality of users.

To illustrate, FIG. 4 shows an exemplary interface 400 that may be presented to the user and that may allow the user to selectively access the master DVR schedule and the one or more DVR schedules associated with the plurality of users. Interface 400, as well as the other interfaces described herein, may be presented to the user in any suitable way. For example, interface 400 may be presented by way of a display (e.g., a television, display screen, etc.) associated with a DVR device.

As shown in FIG. 4, interface 400 may facilitate creation of a personal DVR schedule by a user. For example, interface 400 shows that the user has selected four media content programs (i.e., the media content programs labeled â€œprogram Aâ€ through â€œprogram Dâ€ ) for inclusion in the personal DVR schedule. To manually add one or more other media content programs to the DVR schedule, the user may select an option 402. Alternatively, the user may select option 404 to access the master DVR schedule or option 406 to access one or more DVR schedules associated with one or more individual users.

FIG. 5 shows an exemplary interface 500 that may be presented in response to the user selecting option 404 to access the master DVR schedule. As shown, interface 500 may include a list of media content programs (e.g., the media content programs labeled â€œprogram Eâ€ through â€œprogram Hâ€ ) that have been selected for inclusion in the master DVR schedule. Additional information associated with each media content program (e.g., whether each media content program is part of a series or a single event and a time slot at which each media content program is to be broadcast or otherwise made available for presentation) may also be displayed within interface 500.

In some examples, the user may use interface 500 to select one or more media content programs included in the master DVR schedule for inclusion in the user's personal DVR schedule. For example, to select the media content program labeled â€œprogram Eâ€ for inclusion in the user's personal DVR schedule, the user may select option 502-1. Likewise, the user may select the media content program labeled â€œprogram Fâ€ for inclusion in the user's personal DVR schedule by selecting option 502-2, the media content program labeled â€œprogram Gâ€ for inclusion in the user's personal DVR schedule by selecting option 502-3, and/or the media content program labeled â€œprogram Hâ€ for inclusion in the user's personal DVR schedule by selecting option 502-4. In response to a user selection of one of options 502-1 through 502-4, personalization facility 104 may automatically include the corresponding media content program in the user's personal DVR schedule. For example, in response to a user selection of option 502-1, personalization facility 104 may automatically include the media content program labeled â€œprogram Eâ€ in the user's personal DVR schedule.

In some examples, personalization facility 104 may allow the user to use (i.e., designate) the master DVR schedule as the user's personal DVR schedule. For example, option 504 may be presented within interface 500. In response to a user selection of option 504, personalization facility 104 may designate the master DVR schedule as the user's personal DVR schedule (e.g., by overwriting what was originally included in the personal DVR schedule with the contents of the master DVR schedule).

Returning to FIG. 4, the user may access DVR schedules (e.g., individual DVR schedules upon which the master DVR schedule is based) associated with other users by selecting option 406. FIG. 6 illustrates an exemplary interface 600 that may be presented in response to a selection by the user of option 406.

As shown, interface 600 may include a search box 602 into which the user may input one or more search terms in order to access DVR schedules associated with one or more users. For example, FIG. 6 shows that the user has input a search term of â€œSmith.â€ In response, personalization facility 104 may present a list 604 of users included in the plurality of users that each have the name of â€œSmithâ€ . The user may then select an option (e.g., option 606) to access a DVR schedule associated with a particular user included in list 604 and/or an option (e.g., option 608) to follow a particular user included in list 604. It will be recognized that interface 600 may include additional or alternative options configured to facilitate access by the user to one or more DVR schedules associated with one or more other users.

FIG. 7 illustrates an exemplary interface 700 that may be presented in response to a user selection of option 606 shown in FIG. 6 (i.e., the option to access the DVR schedule associated with a user named â€œAbe Smithâ€ ). As shown, the DVR schedule associated with the user named â€œAbe Smithâ€ is displayed in interface 700. The user may browse through the DVR schedule and select various media content programs included in the DVR schedule for inclusion in the user's personal DVR schedule. For example, the user may select a media content program labeled â€œprogram Iâ€ for inclusion in the user's personal DVR schedule by selecting option 702-1, a media content program labeled â€œprogram Jâ€ for inclusion in the user's personal DVR schedule by selecting option 702-2, a media content program labeled â€œprogram Kâ€ for inclusion in the user's personal DVR schedule by selecting option 702-3, and/or a media content program labeled â€œprogram Lâ€ for inclusion in the user's personal DVR schedule by selecting option 702-4.

In some examples, personalization facility 104 may allow the user to use (i.e., designate) a DVR schedule associated with an individual user as the user's personal DVR schedule. For example, the user may use the DVR schedule associated with the user named â€œAbe Smithâ€ as the user's personal DVR schedule by selecting an option 704 presented within interface 700.

Returning to FIG. 6, the user may select option 608 to provide a request to follow the user named â€œAbe Smith.â€ As used herein, a request to â€œfollowâ€ a particular user refers to a request to have access to the user's DVR schedule. For example, a first user may follow a second user by receiving notifications of changes made to the second user's DVR schedule, having quick access (e.g., by way of a link) to the second user's DVR schedule, and/or in any other manner.

In response to the user selecting option 608, a request to follow the user named â€œAbe Smithâ€ may be transmitted to personalization facility 104. Personalization facility 104 may receive the request and, in response, allow the user to follow the user named â€œAbe Smithâ€ by providing the user with access to the DVR schedule associated with the user named â€œAbe Smith.â€

As mentioned, a user may browse through a master DVR schedule (e.g., by accessing interface 500) and/or through one or more individual DVR schedules associated with one or more other users (e.g., by accessing interfaces 600 and 700) in order to locate media content programs that may be of interest to the user. In some examples, the user may filter the master DVR schedule and/or one or more individual DVR schedules to present one or more media content programs that include or are related to one or more search terms. To this end, the user may provide input representative of one or more search terms (e.g., by way of interface 500 and/or interface 700). Personalization facility 104 may receive the input, and, in response, identify one or more media content programs included in the master DVR schedule and/or in the one or more individual DVR schedules. Personalization facility 104 may then present, within an interface accessible by the user, information representative of the identified one or more media content programs.

For example, the user may wish to include media content programs related to the search term â€œsoccerâ€ in his or her personal DVR schedule. By providing input to personalization facility 104 representative of the search term â€œsoccerâ€ , the user may be presented, by way of an interface (e.g., an interface similar to interface 600), with information representative of media content programs associated with soccer (e.g., scheduled soccer matches, movies related to soccer, talk shows featuring soccer players, etc.).

In some examples, once the user has created his or her personal DVR schedule, he or she may publish the personal DVR schedule. In response, DVR schedule management facility 102 may include data representative of the DVR schedule in the data representative of the plurality of DVR schedules that is maintained by DVR schedule management facility 102. In this manner, the personal DVR schedule may be included in the plurality of DVR schedules upon which the master DVR schedule is based.

In some examples, personalization facility 104 may automatically update a user's personal DVR schedule once it has been created based on a change in the master DVR schedule and/or one or more individual DVR schedules upon which the personal DVR schedule is based. This may be performed in any suitable manner. For example, the personal DVR schedule may include media content programs selected from the master DVR schedule. Over time, as the popularity of media content programs included in the master DVR schedule changes, DVR schedule management facility 102 may update the master DVR schedule to include additional or alternative media content programs. In response, personalization facility 104 may update the personal DVR schedule to remove one or more media content programs from the personal DVR schedule that are no longer included in the master DVR schedule and/or add one or more media content programs to the personal DVR schedule that are now in the master DVR schedule.

FIG. 8 illustrates an exemplary implementation 800 of system 100 wherein a DVR device 802 is communicatively coupled to a collaboration server subsystem 804 by way of a network 806. As shown, DVR device 802 may be associated with (e.g., accessed by) a user 808. As will be described below, DVR schedule management facility 102, personalization facility 104, and storage facility 106 may each be implemented by DVR device 802 and/or collaboration server subsystem 804.

DVR device 802 may be configured to facilitate access by a user (e.g., user 808) to content (e.g., media content programs) provided by a media content provider and/or content stored locally by DVR device 802. DVR device 802 may be implemented by any suitable access device, such as a set-box device, a personal computer, a mobile device (e.g., a mobile phone, tablet device, etc.), a television device, and/or any other suitable computing device configured to access media content.

Collaboration server subsystem 804 may be associated with (e.g., managed by) a media content provider, a DVR service provider, and/or any other entity as may serve a particular implementation. Collaboration server subsystem 804 may be implemented by one or more computing devices as may serve a particular implementation.

DVR device 802 and collaboration server subsystem 804 may communicate with one another using any suitable communication technologies, devices, media, and protocols supportive of data communications, including, but not limited to, socket connections, Ethernet, data bus technologies, data transmission media, communications devices, Transmission Control Protocol (â€œTCPâ€ ), Internet Protocol (â€œIPâ€ ), File Transfer Protocol (â€œFTPâ€ ), Telnet, Hypertext Transfer Protocol (â€œHTTPâ€ ), Hypertext Transfer Protocol Secure (â€œHTTPSâ€ ), Session Initiation Protocol (â€œSIPâ€ ), Simple Object Access Protocol (â€œSOAPâ€ ), Extensible Mark-up Language (â€œXMLâ€ ) and variations thereof, Simple Mail Transfer Protocol (â€œSMTPâ€ ), Real-Time Transport Protocol (â€œRTPâ€ ), User Datagram Protocol (â€œUDPâ€ ), Global System for Mobile Communications (â€œGSMâ€ ) technologies, Code Division Multiple Access (â€œCDMAâ€ ) technologies, Evolution Data Optimized Protocol (â€œEVDOâ€ ), Time Division Multiple Access (â€œTDMAâ€ ) technologies, Short Message Service (â€œSMSâ€ ), Multimedia Message Service (â€œMMSâ€ ), radio frequency (â€œRFâ€ ) signaling technologies, wireless communication technologies (e.g., Bluetooth, Wi-Fi, etc.), in-band and out-of-band signaling technologies, and other suitable communications technologies.

DVR device 802 and collaboration server subsystem 804 may communicate using any suitable network. For example, as shown in FIG. 8, DVR device 802 and collaboration server subsystem 804 may be configured to communicate with each other by way of network 806. Network 806 may include one or more networks or types of networks capable of carrying communications and/or data signals between DVR device 802 and collaboration server subsystem 804. For example, network 806 may include, but is not limited to, a cable network, an optical fiber network, a hybrid fiber coax network, a wireless network (e.g., a Wi-Fi and/or mobile telephone network), a satellite network, a wireless broadcast network (e.g., a satellite media broadcasting network or terrestrial broadcasting network), a subscriber television network, a provider-specific network, the Internet, an intranet, a local area network, any other suitable network, and/or any combination or sub-combination of these networks.

In certain embodiments, system 100 may be implemented entirely by or within DVR device 802 or entirely by or within collaboration server subsystem 804. In other embodiments, components of system 100 may be distributed across DVR device 802 and collaboration server subsystem 804.

FIG. 9 illustrates an exemplary DVR schedule collaboration method 900. While FIG. 9 illustrates exemplary steps according to one embodiment, other embodiments may omit, add to, reorder, and/or modify any of the steps shown in FIG. 9. One or more of the steps shown in FIG. 9 may be performed by system 100 and/or any implementation thereof.

In step 902, a DVR schedule collaboration system maintains data representative of a plurality of DVR schedules associated with a plurality of users. Step 902 may be performed in any of the ways described herein.

In step 904, the DVR schedule collaboration system creates a master DVR schedule based on the plurality of DVR schedules. Step 904 may be performed in any of the ways described herein.

In step 906, the DVR schedule collaboration system facilitates creation of a personal DVR schedule by a user in accordance with at least one of the master DVR schedule and one or more of the DVR schedules associated with the plurality of users. Step 906 may be performed in any of the ways described herein.

FIG. 10 illustrates another exemplary DVR schedule collaboration method 1000. While FIG. 10 illustrates exemplary steps according to one embodiment, other embodiments may omit, add to, reorder, and/or modify any of the steps shown in FIG. 10. One or more of the steps shown in FIG. 10 may be performed by system 100 and/or any implementation thereof.

In step 1002, a DVR schedule collaboration system maintains data representative of a plurality of DVR schedules associated with a plurality of users. The plurality of DVR schedules specify a plurality of media content programs selected by the users for recording. Step 1002 may be performed in any of the ways described herein.

In step 1004, the DVR schedule collaboration system identifies, based on a frequency of occurrence of each of the plurality of media content programs in the plurality of DVR schedules, a set of most popular media content programs included in the plurality of media content programs. Step 1004 may be performed in any of the ways described herein.

In step 1006, the DVR schedule collaboration system includes the set of most popular media content programs in a master DVR schedule. Step 1006 may be performed in any of the ways described herein.

In certain embodiments, one or more of the processes described herein may be implemented at least in part as instructions embodied in a non-transitory computer-readable medium and executable by one or more computing devices. In general, a processor (e.g., a microprocessor) receives instructions, from a non-transitory computer-readable medium, (e.g., a memory), and executes those instructions, thereby performing one or more processes, including one or more of the processes described herein. Such instructions may be stored and/or transmitted using any of a variety of known computer-readable media.

A computer-readable medium (also referred to as a processor-readable medium) includes any non-transitory medium that participates in providing data (e.g., instructions) that may be read by a computer (e.g., by a processor of a computer). Such a medium may take many forms, including, but not limited to, non-volatile media and/or volatile media. Non-volatile media may include, for example, optical or magnetic disks and other persistent memory. Volatile media may include, for example, dynamic random access memory (â€œDRAMâ€ ), which typically constitutes a main memory. Common forms of computer-readable media include, for example, a disk, hard disk, magnetic tape, any other magnetic medium, a Compact Disc Read-Only Memory (â€œCD-ROMâ€ ), a Digital Versatile Disc (â€œDVDâ€ ), any other optical medium, a Random-Access Memory (â€œRAMâ€ ), a Programmable ROM (â€œPROMâ€ ), an Erasable PROM (â€œEPROMâ€ ), a Flash Electrically EPROM (â€œFLASH-EEPROMâ€ ), any other memory chip or cartridge, or any other tangible medium from which a computer can read.

FIG. 11 illustrates an exemplary computing device 1100 that may be configured to perform one or more of the processes described herein. As shown in FIG. 11, computing device 1100 may include a communication interface 1102, a processor 1104, a storage device 1106, and an input/output (â€œI/Oâ€ ) module 1108 communicatively connected by way of a communication infrastructure 1110. While an exemplary computing device 1100 is shown in FIG. 11, the components illustrated in FIG. 11 are not intended to be limiting. Additional, fewer, or alternative components may be used in other embodiments. Components of computing device 1100 shown in FIG. 11 will now be described in additional detail.

Communication interface 1102 may be configured to communicate with one or more computing devices. Examples of communication interface 1102 include, without limitation, a wired network interface (such as a network interface card), a wireless network interface (such as a wireless network interface card), a modem, an audio/video connection, and any other suitable interface.

Processor 1104 generally represents any type or form of processing unit capable of processing data or interpreting, executing, and/or directing execution of one or more of the instructions, processes, and/or operations described herein. Processor 1104 may execute and/or direct execution of operations as directed by one or more applications 1112 or other computer-executable instructions such as may be stored in storage device 1106 or another computer-readable medium.

Storage device 1106 may include one or more data storage media, devices, or configurations and may employ any type, form, and combination of data storage media and/or device. For example, storage device 1106 may include, but is not limited to, a hard drive, network drive, flash drive, magnetic disc, optical disc, RAM, DRAM, other non-volatile and/or volatile data storage units, or a combination or sub-combination thereof. Electronic data, including data described herein, may be temporarily and/or permanently stored in storage device 1106. For example, data representative of one or more applications 1112 configured to direct processor 1104 to perform any of the operations described herein may be stored within storage device 1106. In some examples, data may be arranged in one or more databases residing within storage device 1106.

I/O module 1108 may be configured to receive user input and provide user output and may include any hardware, firmware, software, or combination thereof supportive of input and output capabilities. For example, I/O module 1108 may include hardware and/or software for capturing user input, including, but not limited to, a keyboard or keypad, a touch screen component (e.g., touch screen display), a receiver (e.g., an RF or infrared receiver), and/or one or more input buttons.

I/O module 1108 may include one or more devices for presenting output to a user, including, but not limited to, a graphics engine, a display (e.g., a display screen), one or more output drivers (e.g., display drivers), one or more audio speakers, and one or more audio drivers. In certain embodiments, I/O module 1108 is configured to provide graphical data to a display for presentation to a user. The graphical data may be representative of one or more GUI views and/or any other graphical content as may serve a particular implementation.

In some examples, any of the facilities described herein may be implemented by or within one or more components of computing device 1100. For example, one or more applications 1112 residing within storage device 1106 may be configured to direct processor 1104 to perform one or more processes or functions associated with DVR schedule management facility 102 and/or personalization facility 104. Likewise, storage facility 106 may be implemented by or within storage device 1106. Such an implementation may be referred to as a computer-implemented system, such as a computer-implemented DVR schedule collaboration system 100 or a computing system 100.

To the extent the aforementioned embodiments collect, store, and/or employ personal information provided by individuals, it should be understood that such information shall be used in accordance with all applicable laws concerning protection of personal information. Additionally, the collection, storage, and use of such information may be subject to consent of the individual to such activity, for example, through well known â€œopt-inâ€ or â€œopt-outâ€ processes as may be appropriate for the situation and type of information. Storage and use of personal information may be in an appropriately secure manner reflective of the type of information, for example, through various encryption and anonymization techniques for particularly sensitive information.

In the preceding description, various exemplary embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the scope of the invention as set forth in the claims that follow. For example, certain features of one embodiment described herein may be combined with or substituted for features of another embodiment described herein. The description and drawings are accordingly to be regarded in an illustrative rather than a restrictive sense.