METHODS AND SYSTEMS FOR GENERATING NOTIFICATIONS BASED ON THE INTERESTS OF GUESTS

Methods and systems are provided herein for generating notifications based on the interests of guests. Guests may request notifications on their host's television, and the system will generate notifications based on the guest's interests and preferences as stored in the guest's user profile. In doing so, the guest will be notified of events of interest, such as when a favorite sports team scores a point or when an important scene in a favorite movie is playing. The system monitors the network of the apartment or house and detects when a guest device is accessing the network. The system then accesses the guest's interests and identifies a set of programs based on these interests. The system then monitors these programs and generates notifications on the display device when an event of interest has occurred in one of the identified programs.

BACKGROUND

In our connected world, it is common for a user to set settings for controlling notifications on his own television or display device. In these situations, the user is affecting the settings on his user account and can control the other devices associated with that account. However, when guests use the user's television or display device, the guests have no ability to set any of these functions while they are using those same devices. For example, a group of friends gather in an apartment for dinner and the news is on the television. In this example, the user who's hosting this dinner can set any number of notifications, but any of his friends, who may be missing his sports games or shows, cannot connect to his device temporarily to see his notifications while they are at this dinner. Guests, upon visiting another user, are unable to request notifications on the main display device for shows of interest to be displayed while visiting the other user.

SUMMARY

Methods and systems are provided herein for generating notifications based on the interests of guests. Guests may request notifications on their host's television, and the system will generate notifications based on the guest's interests and preferences as stored in the guest's user profile. In doing so, the guest will be notified of events of interest, such as when a favorite sports team scores a point or when an important scene in a favorite movie is playing. The system monitors the network of the apartment or house and detects when a guest device is accessing the network. The system then accesses the guest's interests and identifies a set of programs based on these interests. The system then monitors these programs and generates notifications on the display device when an event of interest to the guest has occurred in one of the identified programs.

In some aspects, the media guidance application detects a device accessing a network. For example, the media guidance application may detect a cell phone connecting to the local area network (LAN). The media guidance application transmits, to the server, a request for a set of device identifiers associated with the network. For example, the media guidance application may request from the server a list of cell phones, mobile devices, and laptops that are identified as having previously accessed the network on a regular basis (e.g., devices that have previously accessed the network within a predetermined time interval) or at a rate exceeding a specified frequency. The media guidance application receives, from the server, the set of device identifiers, where one of the device identifiers of the set of device identifiers represents a display device. The display device may be a device that displays content to multiple users (e.g., a shared display device). For example, the media guidance application may receive, for a network associated with a house, a list of device identifiers that includes each resident's cell phone and laptop, as well as the smart televisions.

In some embodiments, the network is a local area network and the set of device identifiers associated with the network represents a set of devices identified as accessing the network frequently or regularly. The media guidance application may monitor the network. For example, the media guidance application may monitor the local area network for the various cell phones, mobile devices, and laptops that may access it. The media guidance application may measure a frequency of access for each device that accesses the network. For example, the media guidance application may record each time a specific cell phone connects to the LAN and calculate a regular frequency for that cell phone over a time period, such as a weekly or monthly frequency. As a specific example, the media guidance application records whether the cell phone connects to the LAN every day for five hours, in which case the frequency is once a day, or connects to the LAN once a week for only two hours. The media guidance application may compare the frequency of access for each device that accesses the network to a threshold. The media guidance application may then, based on the comparing, determine that the frequency of access for a new device is above a threshold. For example, the threshold may be any device which connects to the LAN at least once every other day. The identified cell phone may access the LAN daily and so may exceed the threshold. In another example, the identified cell phone may access the LAN only once a week and so fail to exceed the threshold. The media guidance application may add a new device identifier associated with the new device to the set of device identifiers. For example, the identified cell phone that has been determined to connect to the LAN at a frequency above the threshold may be added to a list of device identifiers that regularly accesses the network.

The media guidance application retrieves a device identifier for the device accessing the network. For example, the media guidance application may detect a cell phone connecting with the LAN and retrieve the cellphone's device ID. A device ID may be a mac address, IP address, phone number, or other unique identifier. The media guidance application compares each of the set of device identifiers to the retrieved device identifier. For example, the media guidance application may compare the cellphone's device ID to the list of devices associated with the house. The media guidance application, in response to comparing, determines that the retrieved device identifier does not match any of the device identifiers in the set of device identifiers. For example, the media guidance application may determine that the cell phone is not on the list of devices associated with the house because this is the first time the cell phone has connected to the LAN.

The media guidance application identifies the device associated with the device identifier as a guest device. For example, the media guidance application tags the cell phone's device ID as a guest device. In some embodiments, the media guidance application may identify the device associated with the device identifier as a guest device by retrieving, from the server, contact information associated with the set of device identifiers, searching for the detected device identifier in the retrieved contact information and, based on the searching, determining that the detected device identifier represents the guest device. For example, the media guidance application may access the contact list from the cell phone for each resident of the house and check the contact lists for an entry associated with the detected cell phone and, based on determining that this cell phone is associated with one of the entries in one of the contact lists, then tag the cell phone's device ID as a guest device.

In some embodiments, the media guidance application may verify whether the device associated with the device identifier is a guest device or a new device associated with the user by detecting a user account associated with the device. For example, the user may bring home a new device that has not yet accessed the network, and be prompted to login with a username that connects the device to the user's account. In this specific example, the new device would not be identified as a guest device, even though the device is new, because it is associated with a user account that has other devices which are already identified as accessing the network regularly. In some embodiments, the media guidance application may determine a list of user accounts associated with each device identifier in the set of device identifiers, search the list of user accounts for the detected user account, and, based on the search, add the device ID for the identified device to the set of device identifiers. For example, the media guidance application may determine a list of user accounts based on the user accounts associated with each laptop that regularly accesses the network, so that when a user buys a new laptop associated with one of the listed user accounts, the media guidance application automatically identifies the laptop and adds the laptop to the list of devices associated with the network.

The media guidance application accesses, via a database of user profiles, a guest user profile associated with the guest device. For example, the media guidance application may search the database of user profiles for a profile associated with the cell phone's device ID. The media guidance application registers the guest user profile as a profile with limited control of the display device. For example, the media guidance application may tag the guest user profile as a profile that has limited permissions to control the smart television in the house. The media guidance application, in response to registering the guest user profile as the profile with limited control, receives a request for notifications from a guest user profile. For example, once the guest profile has been marked as a profile with limited access, the guest may be able to use his cell phone to request notifications on the smart television. The media guidance application retrieves, from the guest user profile, a set of interests. For example, the media guidance application may access the guest's user profile to find the guest's interests such as favorite sports teams, genres, or channels.

The media guidance application determines a set of media assets currently available that match the set of interests from the guest user profile. For example, the media guidance application may, based on the guest's user profile, identify a sports game currently playing based on the guest's favorite team or may identify a movie about to start based on the guest's favorite actor. In another example, the guest's user profile may include account information for other social networks, such as Twitter, and determine the programs and interests of the user based on who the guest follows on these social networks, such as Twitter. In some embodiments, the media guidance application may determine a set of media assets currently available by retrieving a list of favorite media assets associated with the guest user profile, retrieving a schedule of recordings associated with the guest user profile, and searching a program guide schedule for a media asset that matches at least one of 1) a media asset on the list of favorites, 2) a media asset on the schedule of recordings, or 3) a media asset in the set of interests of the user. For example, the media guidance application may search the program guide for programs currently playing or about to start for programs that match items on the guest's favorites list such as a favorite movie. In another example, the media guidance application may search the program guide for programs that the guest has scheduled to record on his home DVR. In yet another example, the media guidance application may search for a television show in the program guide because the guest follows the official account for the show on a social network such as Twitter.

The media guidance application monitors the set of media assets for an event of interest to the guest. For example, the media guidance application may monitor the programs identified as programs of interest to determine what is happening in each program. The media guidance application determines whether the event of interest to a user associated with the guest user profile has occurred in one of the media assets in the set of media assets. For example, the media guidance application may receive from a server a set of timestamps for a movie, where each timestamp is a favorite scene for that movie. If the program has reached one of these timestamps or is about to reach one of these timestamps, the media guidance application may determine that an event of interest to the guest is occurring. In some embodiments, the media guidance application may monitor social media posts associated with the media assets, and determine whether the event of interest to the guest has occurred comprises determining that one of the set of media assets is referenced in a number of the social media posts that exceeds a threshold. For example, the media guidance application may monitor a social network such as Twitter and determine if a certain event is trending. If an event is trending on the social network, the media guidance application may determine that it is an event of interest to the guest as well.

The media guidance application generates for display, on the display device, a notification indicating the event of interest to the guest and the media asset. The display device may be a device displaying content to multiple users and may be a device associated with another user's profile. For example, the media guidance application may generate a notification on the television that the guest's favorite team has just scored in the on-going sports game. In some embodiments, the media guidance application may receive a user selection of the generated notification from the guest device and then may generate for display, on the display device, the media asset associated with the selected notification. For example, the media guidance application may allow the guest to select the notification indicating that the guest's favorite team has just scored a point and then have the television tune to the sports game. In some embodiments, the media guidance application may receive a user selection, from the guest device, to rewind the media asset to the event of interest to the guest. The media guidance application may generate for display, on the display device, the media asset from the event of interest to the guest. For example, the media guidance application may, upon tuning to the sports game, play the game from a timestamp before the point was scored instead of tuning to the live program.

In some embodiments, the media guidance application may detect that the guest device is no longer connected to the network. For example, the media guidance application may determine that the guest's cell phone is no longer accessing the LAN. The media guidance application may delete the guest user profile as the profile with limited control of the display device. The media guidance application may terminate the monitoring of the set of media assets for the event of interest to the guest. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application may receive a user selection, from the guest device, to terminate notifications. For example, the media guidance application may receive an instruction from guest's cell phone to discontinue the notifications. The media guidance application may delete the guest user profile as the profile with limited control of the display device. The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for the event of interest to the guest. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application receives a user selection, from a device associated with a device identifier from the set of device identifiers, to mute notifications from the profile with limited control of the display device. For example, a user with a laptop that regularly accesses the LAN for this house may select the controls to stop notifications requested from guests. The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for the event of interest to the guest. For example, the media guidance application may discontinue any notifications relating to that guest's interests.

DETAILED DESCRIPTION

Methods and systems are provided herein for generating notifications based on the interests of guests. Guests may request notifications on their host's television, and the system will generate notifications based on the guest's interests and preferences as stored in the guest's user profile. In doing so, the guest will be notified of events of interest, such as when a favorite sports team scores a point or when an important scene in a favorite movie is playing. The system monitors the network of the apartment or house and detects when a guest device is accessing the network. The system then accesses the guest's interests and identifies a set of programs based on these interests. The system then monitors these programs and generates notifications on the display device when an event of interest to the guest has occurred in one of the identified programs.

As referred to herein, a “guest” is a person with a user account and user profile on the server and/or on his guest device who is temporarily visiting a location associated with a network of another user with a different user account and user profile and which does not have a record of the guest user account and/or profile. For example, a guest is a person who is visiting a friend's home at which the device of the friend does not have an account or profile set up for the guest. A “guest device” is a device associated with the guest, the guest's account and/or profile.

FIG. 1 shows an illustrative embodiment of user devices connecting to the network to access control of the display device, in accordance with some embodiments of the disclosure. User devices 102, 104, and 106 are associated with users 108, 110, and 112 respectively. User devices 102, 104, and 106, as well as display device 114 connect to network 116.

In some embodiments, the media guidance application detects a user device 102 accessing a network 116. For example, the media guidance application may detect a cell phone (e.g., user device 102) connecting to the local area network (LAN) (e.g., network 116). The media guidance application transmits, to the server, a request for a set of device identifiers associated with the network 116. For example, the media guidance application may request from the server a list of cell phones, mobile devices, and laptops that are identified as having previously accessed the network 116 on a regular basis (e.g., devices that have previously accessed the network within a predetermined time interval) or at a rate exceeding a specified frequency. The media guidance application receives, from the server, the set of device identifiers, where one of the device identifiers of the set of device identifiers represents display device 114. The display device 114 may be a device that displays content to multiple users (e.g., a shared display device). For example, the media guidance application may receive, for a network associated with a house (e.g., network 116), a list of device identifiers that includes each resident's cell phone (e.g., user devices 102 and 106) and laptop, as well as the smart televisions (e.g., display device 114).

In some embodiments, the network 116 is a local area network and the set of device identifiers associated with the network represents a set of devices identified as accessing the network frequently or regularly. The media guidance application may monitor the network 116. For example, the media guidance application may monitor the local area network for the various cell phones, mobile devices, and laptops that may access it. The media guidance application may measure a frequency of access for each device (e.g., user devices 102 and 106) that accesses the network 116. For example, the media guidance application may record each time a specific cell phone connects to the LAN and calculate a regular frequency for that cell phone over a time period, such as a weekly or monthly frequency. As a specific example, the media guidance application records whether the cell phone connects to the LAN every day for five hours, in which case the frequency is once a day, or connects to the LAN once a week for only two hours. The media guidance application may compare the frequency of access for each device (e.g., user devices 102 and 106) that accesses the network 116 to a threshold. The media guidance application may then, based on the comparing, determine that the frequency of access for a new device (e.g., user devices 102 and 106) is above a threshold. For example, the threshold may be any device which connects to the LAN (e.g., network 116) at least once every other day. The identified cell phone (e.g., user device 102) may access the LAN (e.g., network 116) daily and so exceed the threshold. In another example, the identified cell phone (e.g., user device 106) may access the LAN (e.g., network 116) only once a week and so fail to exceed the threshold. The media guidance application may add a new device identifier associated with the new device (e.g., user device 102) to the set of device identifiers. For example, the identified cell phone that has been determined to connect to the LAN at a frequency above the threshold may be added to a list of device identifiers that regularly accesses the network 116.

The media guidance application retrieves a device identifier for the device (e.g., user device 104) accessing the network 116. For example, the media guidance application may detect a cell phone connecting with the LAN and retrieve the cellphone's device ID. A device ID may be a mac address, IP address, phone number, or other unique identifier. The media guidance application compares each of the set of device identifiers to the retrieved device identifier. For example, the media guidance application may compare the cellphone's device ID to the list of devices associated with the house. The media guidance application, in response to comparing, determines that the retrieved device identifier does not match any of the device identifiers in the set of device identifiers. For example, the media guidance application may determine that the cell phone is not on the list of devices associated with the house because this is the first time the cell phone has connected to the LAN.

The media guidance application identifies the device 104 associated with the device identifier as a guest device. For example, the media guidance application tags the cell phone's device ID as a guest device. In some embodiments, the media guidance application may identify the device 104 associated with the device identifier as a guest device by retrieving, from the server, contact information associated with the set of device identifiers, searching for the detected device identifier in the retrieved contact information and, based on the searching, determining that the detected device identifier represents the guest device. For example, the media guidance application may access the contact list from the cell phone (e.g., user devices 102 and 106) for each resident of the house (e.g., users 108 and 112) and check the contact lists for an entry associated with the detected cell phone and, based on determining that this cell phone (e.g., user device 104) is associated with one of the entries in one of the contact lists (e.g., user 110), then tag the cell phone's device ID as a guest device.

In some embodiments, the media guidance application may verify whether the device 104 associated with the device identifier is a guest device or a new device associated with user 112 of the network by detecting a user account associated with the device. For example, user 112 may bring home a new device (e.g., user device 106) that has not yet accessed network 116, and be prompted to login with a username that connects the device to the user's account. In this specific example, the new device (e.g., user device 106) would not be identified as a guest device, even though the device is new, because it is associated with a user account that has other devices which are already identified as accessing the network regularly. In some embodiments, the media guidance application may determine a list of user accounts associated with each device identifier in the set of device identifiers, search the list of user accounts for the detected user account, and, based on the search, add the device ID for the identified device to the set of device identifiers. For example, the media guidance application may determine a list of user accounts based on the user accounts associated with each laptop that regularly accesses the network, so that when a user buys a new laptop associated with one of the listed user accounts, the media guidance application automatically identifies the laptop and adds the laptop to the list of devices associated with the network 116.

The media guidance application accesses, via a database of user profiles, a guest user profile associated with the guest device (e.g., user device 104). For example, the media guidance application may search the database of user profiles for a profile associated with the cell phone's device ID. The media guidance application registers the guest user profile as a profile with limited control of the display device 114. For example, the media guidance application may tag the guest user profile as a profile that has limited permissions to control the smart television (e.g., display device 114) in the house. The media guidance application, in response to registering the guest user profile as the profile with limited control, receives a request for notifications from a guest user profile. For example, once the guest profile has been marked as a profile with limited access, the guest (e.g., user 110) may be able to use his cell phone (e.g., user device 104) to request notifications on the smart television (e.g., display device 114) or perform a limited set of guest functions (e.g., control volume and change channels but not purchase content). The media guidance application retrieves, from the guest user profile, a set of interests. For example, the media guidance application may access the guest's user profile to find the guest's interests such as favorite sports teams, genres, or channels.

The media guidance application determines a set of media assets currently available that match the set of interests of the user (e.g., user 110) from the guest user profile. For example, the media guidance application may, based on the guest's user profile, identify a sports game currently playing based on the guest's favorite team or may identify a movie about to start based on the guest's favorite actor. In another example, the guest's user profile may include account information for other social networks, such as Twitter, and determine the programs and interests of the user (e.g., user 110) based on who the guest follows on these social networks, such as Twitter. In some embodiments, the media guidance application may determine a set of media assets currently available by retrieving a list of favorite media assets associated with the guest user profile, retrieving a schedule of recordings associated with the guest user profile, and searching a program guide schedule for a media asset that matches at least one of 1) a media asset on the list of favorites, 2) a media asset on the schedule of recordings, or 3) a media asset in the set of interests of the user (e.g., user 110). For example, the media guidance application may search the program guide for programs currently playing or about to start for programs that match items on the guest's favorites list such as a favorite movie. In another example, the media guidance application may search the program guide for programs that the guest has scheduled to record on his home DVR. In yet another example, the media guidance application may search for a television show in the program guide because the guest follows the official account for the show on a social network such as Twitter.

The media guidance application monitors the set of media assets for an event of interest to the user (e.g., user 110). For example, the media guidance application may monitor the programs identified as programs of interest to determine what is happening in each program. The media guidance application determines whether the event of interest to a user (e.g., user 110) associated with the guest user profile has occurred in one of the media assets in the set of media assets. For example, the media guidance application may receive from a server a set of timestamps for a movie, where each timestamp is a favorite scene for that movie. If the program has reached one of these timestamps or is about to reach one of these timestamps, the media guidance application may determine that an event of interest is occurring. In some embodiments, the media guidance application may monitor social media posts associated with the media assets, and determine whether the event of interest has occurred by determining that one of the set of media assets is referenced in a number of the social media posts that exceeds a threshold. For example, the media guidance application may monitor a social network such as Twitter and determine if a certain event is trending. If an event is trending on the social network, the media guidance application may determine that it is an event of interest to the guest (e.g., user 110) as well.

The media guidance application generates for display, on the display device 114, a notification indicating the event of interest and the media asset. The display device 114 may be a device displaying content to multiple users and may be a device associated with another user's profile. For example, the media guidance application may generate a notification on the television (e.g., display device 114) that the guest's favorite team has just scored in the on-going sports game. In some embodiments, the media guidance application may receive a user selection of the generated notification from the guest device (e.g., user device 104) and then may generate for display, on the display device 114, the media asset associated with the selected notification. For example, the media guidance application may allow the guest (e.g., user 110) to select the notification indicating that the guest's favorite team has just scored a point and then have the television (e.g., display 114) tune to the sports game. In some embodiments, the media guidance application may receive a user selection, from the guest device (e.g., user device 104), to rewind the media asset to the event of interest. The media guidance application may generate for display, on the display device 114, the media asset from the event of interest. For example, the media guidance application may, upon tuning to the sports game, play the game from a timestamp before the point was scored instead of tuning to the live program.

In some embodiments, the media guidance application may detect that the guest device (e.g., user device 104) is no longer connected to the network 116. For example, the media guidance application may determine that the guest's cell phone (e.g., user device 104) is no longer accessing the LAN (e.g., network 116). The media guidance application may delete the guest user profile as the profile with limited control of the display device 114. The media guidance application may terminate the monitoring of the set of media assets for the event of interest. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application may receive a user selection, from the guest device (e.g., user device 104), to terminate notifications.

For example, the media guidance application may receive an instruction from guest's cell phone (e.g., user device 104) to discontinue the notifications. The media guidance application may delete the guest user profile as the profile with limited control of the display device 114. The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for an event of interest to user 110. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application receives a user selection, from a device associated with a device identifier from the set of device identifiers (e.g., user device 102), to mute notifications from the profile with limited control of the display device 114. For example, a user with a laptop that regularly accesses the LAN for this house may select the controls to stop notifications requested from guests (e.g., user 110). The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for the event of interest. For example, the media guidance application may discontinue any notifications relating to that guest's interests.

FIG. 2 shows another illustrative embodiment of display screens that may be used to generate notifications based on the interests of guests, in accordance with some embodiments of the disclosure. User device 202 is connected to network 204 and displays, to the user, selectable options 206 and 208. Display device 210 shows notifications 212, 214, and 216. User device 218 displays notification 220. Notification 220 may match notification 214.

The media guidance application generates for display, on the display device 210, a notification (e.g., notifications 212, 214, and 216) indicating the event of interest and the media asset. The display device 210 may be a device displaying content to multiple users and may be a device associated with another user's profile. For example, the media guidance application may generate a notification (e.g., notifications 212, 214, and 216) on the television (e.g., display device 210) that the guest's favorite team has just scored in the on-going sports game (e.g., notification 214). In some embodiments, notifications that are provided based on the guest profile (e.g., the guest's team just scored) may be visually distinguished (e.g., the notification may include a textual or visual representation of the guest) from notifications provided based on a profile or device that regularly accesses the network. In some embodiments, the media guidance application may receive a user selection of the generated notification (e.g., notification 220) from the guest device (e.g., user device 218) and then may generate for display, on the display device 210, the media asset associated with the selected notification (e.g., notification 220). For example, the media guidance application may allow the guest to select the notification (e.g., notification 220) indicating that the guest's favorite team has just scored a point and then have the television (e.g., display device 210) tune to the sports game. In some embodiments, the media guidance application may receive a user selection, from the guest device (e.g., user devices 202 or 218), to rewind the media asset to the event of interest. The media guidance application may generate for display, on the display device 210, the media asset from the event of interest. For example, the media guidance application may, upon tuning to the sports game, play the game from a timestamp before the point was scored instead of tuning to the live program.

In some embodiments, the media guidance application may detect that the guest device (e.g., user device 202) is no longer connected to the network 204. For example, the media guidance application may determine that the guest's cell phone is no longer accessing the LAN. The media guidance application may delete the guest user profile as the profile with limited control of the display device 210. The media guidance application may terminate the monitoring of the set of media assets for the event of interest. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television (e.g., display device 210) and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application may receive a user selection, from the guest device (e.g., user device 202), to terminate notifications.

For example, the media guidance application may receive an instruction from guest's cell phone (e.g., user device 202) to discontinue the notifications. The media guidance application may delete the guest user profile as the profile with limited control of the display device 210. The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for an event of interest. For example, the media guidance application may remove the guest's user profile permissions to request notifications for the television (e.g., display device 210) and may discontinue any notifications relating to that guest's interests.

In some embodiments, the media guidance application receives a user selection, from a device associated with a device identifier from the set of device identifiers, to mute notifications from the profile with limited control of the display device 210. For example, a user with a laptop that regularly accesses the LAN for this house may select the controls to stop notifications requested from guests. The media guidance application, in response to receiving the user selection, may terminate the monitoring of the set of media assets for the event of interest. For example, the media guidance application may discontinue any notifications relating to that guest's interests.

FIG. 3 shows illustrative grid of a program listings display 300 arranged by time and channel that also enables access to different types of content in a single display. Display 300 may include grid 302 with: (1) a column of channel/content type identifiers 304, where each channel/content type identifier (which is a cell in the column) identifies a different channel or content type available; and (2) a row of time identifiers 306, where each time identifier (which is a cell in the row) identifies a time block of programming. Grid 302 also includes cells of program listings, such as program listing 308, where each listing provides the title of the program provided on the listing's associated channel and time. With a user input device, a user can select program listings by moving highlight region 310. Information relating to the program listing selected by highlight region 310 may be provided in program information region 312. Region 312 may include, for example, the program title, the program description, the time the program is provided (if applicable), the channel the program is on (if applicable), the program's rating, and other desired information.

Internet content may include web events, such as a chat session or Webcast, or content available on-demand as streaming content or downloadable content through an Internet web site or other Internet access (e.g., FTP).

Grid 302 may provide media guidance data for non-linear programming including on-demand listing 314, recorded content listing 316, and Internet content listing 318. A display combining media guidance data for content from different types of content sources is sometimes referred to as a “mixed-media” display. Various permutations of the types of media guidance data that may be displayed that are different than display 300 may be based on user selection or guidance application definition (e.g., a display of only recorded and broadcast listings, only on-demand and broadcast listings, etc.). As illustrated, listings 314, 316, and 318 are shown as spanning the entire time block displayed in grid 302 to indicate that selection of these listings may provide access to a display dedicated to on-demand listings, recorded listings, or Internet listings, respectively. In some embodiments, listings for these content types may be included directly in grid 302. Additional media guidance data may be displayed in response to the user selecting one of the navigational icons 320. (Pressing an arrow key on a user input device may affect the display in a similar manner as selecting navigational icons 320.)

Another display arrangement for providing media guidance is shown in FIG. 4. Video mosaic display 400 includes selectable options 402 for content information organized based on content type, genre, and/or other organization criteria. In display 400, television listings option 404 is selected, thus providing listings 406, 408, 410, and 412 as broadcast program listings. In display 400 the listings may provide graphical images including cover art, still images from the content, video clip previews, live video from the content, or other types of content that indicate to a user the content being described by the media guidance data in the listing. Each of the graphical listings may also be accompanied by text to provide further information about the content associated with the listing. For example, listing 408 may include more than one portion, including media portion 414 and text portion 416. Media portion 414 and/or text portion 416 may be selectable to view content in full-screen or to view information related to the content displayed in media portion 414 (e.g., to view listings for the channel that the video is displayed on).

The listings in display 400 are of different sizes (e.g., listing 406 is larger than listings 408, 410, and 412), but if desired, all the listings may be the same size. Listings may be of different sizes or graphically accentuated to indicate degrees of interest to the user or to emphasize certain content, as desired by the content provider or based on user preferences. Various systems and methods for graphically accentuating content listings are discussed in, for example, Yates, U.S. Patent Application Publication No. 2010/0153885, filed Nov. 12, 2009, which is hereby incorporated by reference herein in its entirety.

Users may access content and the media guidance application (and its display screens described above and below) from one or more of their user equipment devices. FIG. 5 shows a generalized embodiment of illustrative user equipment device 500. More specific implementations of user equipment devices are discussed below in connection with FIG. 6. User equipment device 500 may receive content and data via input/output (hereinafter “I/O”) path 502. I/O path 502 may provide content (e.g., broadcast programming, on-demand programming, Internet content, content available over a local area network (LAN) or wide area network (WAN), and/or other content) and data to control circuitry 504, which includes processing circuitry 506 and storage 508. Control circuitry 504 may be used to send and receive commands, requests, and other suitable data using I/O path 502. I/O path 502 may connect control circuitry 504 (and specifically processing circuitry 506) to one or more communications paths (described below). I/O functions may be provided by one or more of these communications paths, but are shown as a single path in FIG. 5 to avoid overcomplicating the drawing.

Memory may be an electronic storage device provided as storage 508 that is part of control circuitry 504. As referred to herein, the phrase “electronic storage device” or “storage device” should be understood to mean any device for storing electronic data, computer software, or firmware, such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Storage 508 may be used to store various types of content described herein as well as media guidance data described above.

Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage, described in relation to FIG. 6, may be used to supplement storage 508 or instead of storage 508.

A user may send instructions to control circuitry 504 using user input interface 510. User input interface 510 may be any suitable user interface, such as a remote control, mouse, trackball, keypad, keyboard, touch screen, touchpad, stylus input, joystick, voice recognition interface, or other user input interfaces. Display 512 may be provided as a stand-alone device or integrated with other elements of user equipment device 500. For example, display 512 may be a touchscreen or touch-sensitive display. In such circumstances, user input interface 510 may be integrated with or combined with display 512. Display 512 may be one or more of a monitor, a television, a liquid crystal display (LCD) for a mobile device, amorphous silicon display, low temperature poly silicon display, electronic ink display, electrophoretic display, active matrix display, electro-wetting display, electrofluidic display, cathode ray tube display, light-emitting diode display, electroluminescent display, plasma display panel, high-performance addressing display, thin-film transistor display, organic light-emitting diode display, surface-conduction electron-emitter display (SED), laser television, carbon nanotubes, quantum dot display, interferometric modulator display, or any other suitable equipment for displaying visual images. In some embodiments, display 512 may be HDTV-capable. In some embodiments, display 512 may be a 3D display, and the interactive media guidance application and any suitable content may be displayed in 3D. A video card or graphics card may generate the output to the display 512. The video card may offer various functions such as accelerated rendering of 3D scenes and 2D graphics, MPEG-2/MPEG-4 decoding, TV output, or the ability to connect multiple monitors. The video card may be any processing circuitry described above in relation to control circuitry 504. The video card may be integrated with the control circuitry 504. Speakers 514 may be provided as integrated with other elements of user equipment device 500 or may be stand-alone units. The audio component of videos and other content displayed on display 512 may be played through speakers 514. In some embodiments, the audio may be distributed to a receiver (not shown), which processes and outputs the audio via speakers 514.

The guidance application may be implemented using any suitable architecture. For example, it may be a stand-alone application wholly-implemented on user equipment device 500. In such an approach, instructions of the application are stored locally (e.g., in storage 508), and data for use by the application is downloaded on a periodic basis (e.g., from an out-of-band feed, from an Internet resource, or using another suitable approach). Control circuitry 504 may retrieve instructions of the application from storage 508 and process the instructions to generate any of the displays discussed herein. Based on the processed instructions, control circuitry 504 may determine what action to perform when input is received from input interface 510. For example, movement of a cursor on a display up/down may be indicated by the processed instructions when input interface 510 indicates that an up/down button was selected.

User equipment device 500 of FIG. 5 can be implemented in system 600 of FIG. 6 as user television equipment 602, user computer equipment 604, wireless user communications device 606, or any other type of user equipment suitable for accessing content, such as a non-portable gaming machine. For simplicity, these devices may be referred to herein collectively as user equipment or user equipment devices, and may be substantially similar to user equipment devices described above. User equipment devices, on which a media guidance application may be implemented, may function as a standalone device or may be part of a network of devices. Various network configurations of devices may be implemented and are discussed in more detail below.

A user equipment device utilizing at least some of the system features described above in connection with FIG. 5 may not be classified solely as user television equipment 602, user computer equipment 604, or a wireless user communications device 606. For example, user television equipment 602 may, like some user computer equipment 604, be Internet-enabled allowing for access to Internet content, while user computer equipment 604 may, like some television equipment 602, include a tuner allowing for access to television programming. The media guidance application may have the same layout on various different types of user equipment or may be tailored to the display capabilities of the user equipment. For example, on user computer equipment 604, the guidance application may be provided as a web site accessed by a web browser. In another example, the guidance application may be scaled down for wireless user communications devices 606.

In system 600, there is typically more than one of each type of user equipment device but only one of each is shown in FIG. 6 to avoid overcomplicating the drawing. In addition, each user may utilize more than one type of user equipment device and also more than one of each type of user equipment device.

The user equipment devices may be coupled to communications network 614. Namely, user television equipment 602, user computer equipment 604, and wireless user communications device 606 are coupled to communications network 614 via communications paths 608, 610, and 612, respectively.

Communications network 614 may be one or more networks including the Internet, a mobile phone network, mobile voice or data network (e.g., a 4G or LTE network), cable network, public switched telephone network, or other types of communications network or combinations of communications networks. Paths 608, 610, and 612 may separately or together include one or more communications paths, such as, a satellite path, a fiber-optic path, a cable path, a path that supports Internet communications (e.g., IPTV), free-space connections (e.g., for broadcast or other wireless signals), or any other suitable wired or wireless communications path or combination of such paths. Path 612 is drawn with dotted lines to indicate that in the exemplary embodiment shown in FIG. 6 it is a wireless path and paths 608 and 610 are drawn as solid lines to indicate they are wired paths (although these paths may be wireless paths, if desired). Communications with the user equipment devices may be provided by one or more of these communications paths, but are shown as a single path in FIG. 6 to avoid overcomplicating the drawing.

System 600 includes content source 616 and media guidance data source 618 coupled to communications network 614 via communication paths 620 and 622, respectively. Paths 620 and 622 may include any of the communication paths described above in connection with paths 608, 610, and 612. Communications with the content source 616 and media guidance data source 618 may be exchanged over one or more communications paths, but are shown as a single path in FIG. 6 to avoid overcomplicating the drawing. In addition, there may be more than one of each of content source 616 and media guidance data source 618, but only one of each is shown in FIG. 6 to avoid overcomplicating the drawing. (The different types of each of these sources are discussed below.) If desired, content source 616 and media guidance data source 618 may be integrated as one source device. Although communications between sources 616 and 618 with user equipment devices 602, 604, and 606 are shown as through communications network 614, in some embodiments, sources 616 and 618 may communicate directly with user equipment devices 602, 604, and 606 via communication paths (not shown) such as those described above in connection with paths 608, 610, and 612.

In a third approach, users of user equipment devices inside and outside a home can use their media guidance application to communicate directly with content source 616 to access content. Specifically, within a home, users of user television equipment 602 and user computer equipment 604 may access the media guidance application to navigate among and locate desirable content. Users may also access the media guidance application outside of the home using wireless user communications devices 606 to navigate among and locate desirable content.

A user may use various content capture devices, such as camcorders, digital cameras with video mode, audio recorders, mobile phones, and handheld computing devices, to record content. The user can upload content to a content storage service on the cloud either directly, for example, from user computer equipment 604 or wireless user communications device 606 having content capture feature. Alternatively, the user can first transfer the content to a user equipment device, such as user computer equipment 604. The user equipment device storing the content uploads the content to the cloud using a data transmission service on communications network 614. In some embodiments, the user equipment device itself is a cloud resource, and other user equipment devices can access the content directly from the user equipment device on which the user stored the content.

Cloud resources may be accessed by a user equipment device using, for example, a web browser, a media guidance application, a desktop application, a mobile application, and/or any combination of access applications of the same. The user equipment device may be a cloud client that relies on cloud computing for application delivery, or the user equipment device may have some functionality without access to cloud resources. For example, some applications running on the user equipment device may be cloud applications, e.g., applications delivered as a service over the Internet, while other applications may be stored and run on the user equipment device. In some embodiments, a user device may receive content from multiple cloud resources simultaneously. For example, a user device can stream audio from one cloud resource while downloading content from a second cloud resource. Or a user device can download content from multiple cloud resources for more efficient downloading. In some embodiments, user equipment devices can use cloud resources for processing operations such as the processing operations performed by processing circuitry described in relation to FIG. 5. As referred herein, the term “in response to” refers to initiated as a result of. For example, a first action being performed in response to a second action may include interstitial steps between the first action and the second action. As referred herein, the term “directly in response to” refers to caused by. For example, a first action being performed directly in response to a second action may not include interstitial steps between the first action and the second action.

FIG. 7 is a flowchart of illustrative steps involved in generating for display notifications based on the interests of guests, in accordance with some embodiments of the disclosure.

At 702, control circuitry 504 monitors a set of device identifiers associated with a household, where the household is associated with a plurality of user profiles and where the set of devices includes display device 114. The display device 114 may be a device that displays content to multiple users (e.g., a shared display device). For example, control circuitry 504 may detect a cell phone (e.g., user device 102) connecting to the local area network (LAN) (e.g., network 116) and identify the device identifier. In another example, control circuitry 504 may identify a set of device identifiers that includes each resident's cell phone (e.g., user devices 102 and 106) and laptop, as well as the smart televisions (e.g., display device 114). Process 700 proceeds to 704.

At 704, control circuitry 504 detects a guest device that is associated with a guest user profile, where the guest user profile is not one of the plurality of user profiles associated with the household. For example, control circuitry 504 may determine that the detected cell phone is not on the list of devices associated with the house because this is the first time the cell phone has connected to the LAN. Process 700 proceeds to 706.

At 706, control circuitry 504 registers the guest user profile as a profile with limited control of the display device 114. For example, control circuitry 504 may tag the guest user profile as a profile that has limited permissions to control the smart television (e.g., display device 114) in the house. For example, the guest device may have permission to change the volume of display device 114 or change the channels but may not have permission to purchase content. Process 700 proceeds to 708.

At 708, control circuitry 504, in response to registering the guest user profile as the profile with limited control, receives a request for notifications from a guest user profile. For example, once the guest profile has been marked as a profile with limited access, the guest (e.g., user 110) may be able to use his cell phone (e.g., user device 104) to request notifications on the smart television (e.g., display device 114). Process 700 proceeds to 710.

At 710, control circuitry 504 retrieves, from the guest user profile, a set of interests. For example, control circuitry 504 may access the guest's user profile to find the guest's interests such as favorite sports teams, genres, or channels. Process 700 proceeds to 712.

At 712, control circuitry 504 determines a set of media assets currently available that match the set of interests of the user (e.g., user 110) from the guest user profile. For example, control circuitry 504 may, based on the guest's user profile, identify a sports game currently playing based on the guest's favorite team or may identify a movie about to start based on the guest's favorite actor. In another example, the guest's user profile may include account information for other social networks, such as Twitter, and determine the programs and interests of the user (e.g., user 110) based on who the guest follows on these social networks, such as Twitter. Process 700 proceeds to 714.

At 714, control circuitry 504 determines whether the event of interest to a user (e.g., user 110) associated with the guest user profile has occurred in one of the media assets in the set of media assets. For example, control circuitry 504 may receive from a server a set of timestamps for a movie, where each timestamp is a favorite scene of the guest for that movie. If the program has reached one of these timestamps or is about to reach one of these timestamps, control circuitry 504 may determine that an event of interest to the guest is occurring. Process 700 proceeds to 716.

At 716, control circuitry 504 generates for display, on the display device 114, a notification indicating the event of interest and the media asset. The display device 114 may be a device displaying content to multiple users and may be a device associated with another user's profile. For example, control circuitry 504 may generate a notification on the television (e.g., display device 114) that the guest's favorite team has just scored in the on-going sports game.

FIG. 8 is another flowchart of illustrative steps involved in generating for display notifications based on the interests of guests, in accordance with some embodiments of the disclosure.

At 802, control circuitry 504 detects a user device 102 accessing a network 116. For example, control circuitry 504 may detect a cell phone (e.g., user device 102) connecting to the local area network (LAN) (e.g., network 116). Process 800 proceeds to 804.

At 804, control circuitry 504 transmits, to the server, a request for a set of device identifiers associated with the network 116. For example, control circuitry 504 may request from the server a list of cell phones, mobile devices, and laptops that are identified as having previously accessing the network 116 on a regular basis (e.g., devices that have previously accessed the network within a predetermined time interval) or at a rate exceeding a specified frequency. Process 800 proceeds to 806.

At 806, control circuitry 504 receives, from the server, the set of device identifiers, where one of the device identifiers of the set of device identifiers represents display device 114. The display device 114 may be a device that displays content to multiple users (e.g., a shared display device). For example, control circuitry 504 may receive, for a network associated with a house (e.g., network 116), a list of device identifiers that includes each resident's cell phone (e.g., user devices 102 and 106) and laptop, as well as the smart televisions (e.g., display device 114). Process 800 proceeds to 808.

At 808, control circuitry 504 retrieves a device identifier for the device (e.g., user device 104) accessing the network 116. For example, control circuitry 504 may detect a cell phone connecting with the LAN and retrieve the cellphone's device ID. A device ID may be a mac address, IP address, phone number, or other unique identifier. Process 800 proceeds to 810.

At 810, control circuitry 504 compares each of the set of device identifiers to the retrieved device identifier. For example, control circuitry 504 may compare the cellphone's device ID to the list of devices associated with the house. Process 800 proceeds to 812.

At 812, control circuitry 504, in response to comparing, determines that the retrieved device identifier does not match any of the device identifiers in the set of device identifiers. For example, control circuitry 504 may determine that the cell phone is not on the list of devices associated with the house because this is the first time the cell phone has connected to the LAN. Process 800 proceeds to 814.

At 814, control circuitry 504 identifies the device 104 associated with the device identifier as a guest device. For example, control circuitry 504 tags the cell phone's device ID as a guest device. Process 800 proceeds to 816.

At 816, control circuitry 504 accesses, via a database of user profiles, a guest user profile associated with the guest device (e.g., user device 104). For example, control circuitry 504 may search the database of user profiles for a profile associated with the cell phone's device ID. Process 800 proceeds to 818.

At 818, control circuitry 504 registers the guest user profile as a profile with limited control of the display device 114. For example, control circuitry 504 may tag the guest user profile as a profile that has limited permissions to control the smart television (e.g., display device 114) in the house. Process 800 proceeds to 820.

At 820, control circuitry 504, in response to registering the guest user profile as the profile with limited control, receives a request for notifications from a guest user profile. For example, once the guest profile has been marked as a profile with limited access, the guest (e.g., user 110) may be able to use his cell phone (e.g., user device 104) to request notifications on the smart television (e.g., display device 114). Process 800 proceeds to 822.

At 822, control circuitry 504 retrieves, from the guest user profile, a set of interests. For example, control circuitry 504 may access the guest's user profile to find the guest's interests such as favorite sports teams, programs, movies, genres, or channels. Process 800 proceeds to 824.

At 824, control circuitry 504 determines a set of media assets currently available that match the set of interests of the user (e.g., user 110) from the guest user profile. For example, control circuitry 504 may, based on the guest's user profile, identify a sports game currently playing based on the guest's favorite team or may identify a movie about to start based on the guest's favorite actor. In another example, the guest's user profile may include account information for other social networks, such as Twitter, and determine the programs and interests of the user (e.g., user 110) based on who the guest follows on these social networks, such as Twitter. Process 800 proceeds to 826.

At 826, control circuitry 504 monitors the set of media assets for an event of interest to the user (e.g., user 110). For example, control circuitry 504 may monitor the programs identified as programs of interest to determine what is happening in each program. Process 800 proceeds to 828.

At 828, control circuitry 504 determines whether the event of interest to a user (e.g., user 110) associated with the guest user profile has occurred in one of the media assets in the set of media assets. For example, control circuitry 504 may receive from a server a set of timestamps for a movie, where each timestamp is a favorite scene of the guest for that movie. If the program has reached one of these timestamps or is about to reach one of these timestamps, control circuitry 504 may determine that an event of interest to the guest is occurring. Process 800 proceeds to 830.

At 830, control circuitry 504 generates for display, on the display device 114, a notification indicating the event of interest and the media asset. The display device 114 may be a device displaying content to multiple users and may be a device associated with another user's profile. For example, control circuitry 504 may generate a notification on the television (e.g., display device 114) that the guest's favorite team has just scored in the on-going sports game.

FIG. 9 is a flowchart of illustrative steps involved in registering that the first device identifier has limited control, in accordance with some embodiments of the disclosure.

At 902, control circuitry 504 receives, from the server, the set of device identifiers associated with the network 116. For example, control circuitry 504 may receive, for a network associated with a house (e.g., network 116), a list of device identifiers that includes each resident's cell phone (e.g., user devices 102 and 106) and laptop, as well as the smart televisions (e.g., display device 114). Process 900 proceeds to 904.

At 904, control circuitry 504 receives a device identifier for the device (e.g., user device 104) accessing the network 116. For example, control circuitry 504 may detect a cell phone connecting with the LAN and receive the cellphone's device ID. A device ID may be a mac address, IP address, phone number, or other unique identifier. Process 900 proceeds to 906.

At 906, control circuitry 504 determines whether there is another device identifier in the set of device identifier. If there is another device identifier in the set of device identifier, process 900 proceeds to 908. Otherwise, process 900 proceeds to 904.

At 908, control circuitry 504 retrieves a new device identifier from the set of device identifiers. Process 900 proceeds to 910.

At 910, control circuitry 504 determines whether the first device identifier matches the new device identifier. If the first device identifier matches the new device identifier, process 900 proceeds to 912. Otherwise, process 900 proceeds to 906.

At 912, control circuitry 504 searches the database of user profiles for a profile associated with the first device identifier (e.g., a guest user profile associated with the guest device (e.g., user device 104)). For example, control circuitry 504 may search the database of user profiles for a profile associated with the cell phone's device ID. Process 900 proceeds to 914.

At 914, control circuitry 504 registers the profile associated with the first device identifier as a profile with limited control of the display device 114. For example, control circuitry 504 may tag the guest user profile as a profile that has limited permissions to control the smart television (e.g., display device 114) in the house. Process 900 proceeds to 904.

FIG. 10 is a flowchart of illustrative steps involved in detecting a device accessing a network, in accordance with some embodiments of the disclosure.

At 1002, control circuitry 504 receives a request from a user device to access the network (e.g., network 116). For example, a user may submit through his mobile device a request to connect to a LAN. Process 1000 proceeds to 1004. At 1004, control circuitry 504 receives from device the device credentials.

For example, control circuitry 504 may receive a password or other security information from the mobile device to access the LAN. Process 1000 proceeds to 1006.

At 1006, control circuitry 504 compares the credentials to the network requirements. For example, control circuitry 504 may compare the password provided to a password on record. Process 1000 proceeds to 1008.

At 1008, control circuitry 504 determines whether the devices are allowed to access the network (e.g., network 116). If control circuitry 504 determines that, based on the received credentials, the device is not allowed to access the network, process 1000 proceeds to 1010. Otherwise, process 1000 proceeds to 1012.

At 1010, control circuitry 504 refrains from granting the device access to the network. For example, control circuitry 504 may provide the user an error message indicating that the credentials were rejected.

At 1012, control circuitry 504 provides the device access to the network. For example, control circuitry 504 may connect the user device to the LAN. Process 1000 proceeds to 1014.

At 1014, control circuitry 504 registers the Device ID associated with the user device as accessing the network (e.g., network 116). For example, the device ID may be included in set of device ID stored in memory as accessing the network.

FIG. 11 is a flowchart of illustrative steps involved in determining a set of device identifiers associated with the network, in accordance with some embodiments of the disclosure.

At 1102, control circuitry 504 determines the network ID. For example, the network may have an assigned name or other identifier. Process 1100 proceeds to 1104.

At 1104, control circuitry 504 requests, from the database of user profiles, the set of users associated with the network ID. For example, each resident of a house may have in his user profile the network ID associated with his house. Process 1100 proceeds to 1106.

At 1106, control circuitry 504 determines, for each user in the set of users, a device identifier for a device associated with the user. For example, control circuitry 504 may determine the IP address for the laptop of each resident of the house. Process 1100 proceeds to 1108.

At 1108, control circuitry 504 compiles a set of device identifiers based on the devices associated with each user. For example, the set of device identifiers may include a device identifier for each resident's cell phone and laptop.

FIG. 12 is a flowchart of illustrative steps involved in determining that a device from the set of device identifiers is a display device, in accordance with some embodiments of the disclosure.

At 1202, control circuitry 504 receives a set of device identifiers. Control circuitry 504 may store, in memory, the set of device identifiers for each device associated with the network. Process 1200 proceeds to 1204.

At 1204, control circuitry 504 retrieves one of the device identifiers from the set of device identifiers. Process 1200 proceeds to 1206.

At 1206, control circuitry 504 searches the database of user profiles for users associated with the device identifier. For example, control circuitry 504 may find the user associated with a cell phone. Process 1200 proceeds to 1208.

At 1208, control circuitry 504 determines whether there are multiple users associated with the device identifier. For example, a cell phone may only have one associated user, but multiple users may be associated with the same laptop or television. If control circuitry 504 determines that there are multiple users associated with the device identifier, process 1200 proceeds to 1210. Otherwise, process 1200 proceeds to 1212.

At 1210, control circuitry 504 tags the device as a display device. For example, control circuitry 504 may store a tag in association with the device identifier an indication that the device is a display device.

At 1212, control circuitry 504 tags the device as a personal device. For example, control circuitry 504 may store a tag in association with the device identifier an indication that the device is a personal device.

FIG. 13 is a flowchart of illustrative steps involved in accessing, via a database of user profiles, a guest user profile associated with the guest device, in accordance with some embodiments of the disclosure.

At 1302, control circuitry 504 requests a guest user ID associated with the guest device from the guest device. For example, control circuitry 504 may request the name of the user associated with a cell phone. Process 1300 proceeds to 1304.

At 1304, control circuitry 504 receives, from the guest device, a guest user ID. For example, control circuitry 504 may receive the name of a guest from the guest's cell phone. Process 1300 proceeds to 1306.

At 1306, control circuitry 504 generates a request for user profile information associated with guest user ID. For example, control circuitry 504 generates a request for user profile information based on the name of the guest. Process 1300 proceeds to 1308.

At 1308, control circuitry 504 transmits the request, to the server, for the user profile information. For example, control circuitry 504 may transmit the request for the user profile information, including the name of the guest. Process 1300 proceeds to 1310.

At 1310, control circuitry 504 receives, from the server, the user profile information. For example, control circuitry 504 may receive from the server, the user profile information associated with the name of the guest.

FIG. 14 is a flowchart of illustrative steps involved in identifying the device associated with the device identifier as a guest device, in accordance with some embodiments of the disclosure.

At 1402, control circuitry 504 receives, from the server, the guest user profile information. For example, control circuitry 504 may receive the guest user's preferences including a list of favorite shows. Process 1400 proceeds to 1404.

At 1404, control circuitry 504 identifies a user associated with the display device. For example, control circuitry 504 may identify a default user that is one of the users associated with the display device and is a resident of the household. Process 1400 proceeds to 1406.

At 1406, control circuitry 504 retrieves user preferences for conditional control of the display device. For example, the default user of the display device may have specific settings controlling the conditions for a guest to request notifications. Process 1400 proceeds to 1408.

At 1408, control circuitry 504 generates a tag based on the conditional control preferences. For example, the default user may have a preference that all guests can only request notifications for an hour at a time and so control circuitry 504 may generate a tag indicating this specific time frame. Process 1400 proceeds to 1410.

At 1410, control circuitry 504 stores the tag in the guest user profile information in memory. Process 1400 proceeds to 1412.

At 1412, control circuitry 504 accesses the tag in the guest user profile information. Process 1400 proceeds to 1414.

At 1414, control circuitry 504 determines whether the tag's conditions are met. If control circuitry 504 determines that the tag's conditions are met, process 1400 proceeds to 1412. Otherwise, process 1400 proceeds to 1416.

At 1416, control circuitry 504 deletes guest user profile information from memory. For example, if the time frame specified by the default user, and so the conditions of the tag are no longer met, the guest user is removed from the system by deleting the user profile information from memory.

FIG. 15 is a flowchart of illustrative steps involved in determining whether an event of interest to the guest has occurred, in accordance with some embodiments of the disclosure.

At 1502, control circuitry 504 retrieves a media asset from the determined set of media assets. For example, control circuitry 504 may retrieve a media asset from the guest's list of favorite television shows. Process 1500 proceeds to 1504. At 1504, control circuitry 504 generates a request for metadata associated with the media data. For example, control circuitry 504 may generate a request for the genre or actors associated with the favorite television show. Process 1500 proceeds to 1506.

At 1506, control circuitry 504 transmits the request for metadata to the server. Process 1500 proceeds to 1508.

At 1508, control circuitry 504 receives the metadata associated with the media asset from the server. Process 1500 proceeds to 1510.

At 1510, control circuitry 504 retrieves, from the guest user profile information, guest user requirements for events of interest. For example, the guest may indicate to be notified of every score made by a favorite team. Process 1500 proceeds to 1512.

At 1512, control circuitry 504 generates a likelihood that the guest will be interested in the media asset based on the metadata and the guest user requirements for events of interest. For example, control circuitry 504 may determine that a sports game has a high likelihood of interest because the metadata associated with the game shows that the guest's favorite team is playing and the guest's requirements indicate to be notified of all sports games. Process 1500 proceeds to 1514.

At 1514, control circuitry 504 determines whether the likelihood exceeds the threshold for likelihood of interest. If the likelihood does exceed the threshold, process 1500 proceeds to 1516. Otherwise, process 1500 proceeds to 1502.

At 1516, control circuitry 504 generates a notification for the event of interest. For example, control circuitry 504 may generate a display indicating the sports game and the two teams playing. Process 1500 proceeds to 1502.

FIG. 16 is a flowchart of illustrative steps involved in generating for display, on the display device, a notification indicating the event of interest and the media asset, in accordance with some embodiments of the disclosure.

At 1602, control circuitry 504 retrieves the media asset information from the server. For example, control circuitry 504 may receive the metadata associated with the media asset as well as an indication of an event of interest to a particular guest. Process 1600 proceeds to 1604.

At 1604, control circuitry 504 identifies the device identifier tagged as a display device. For example, control circuitry 504 may identify which device identifier of the device identifiers in memory is a display device. Process 1600 proceeds to 1606.

At 1606, control circuitry 504 identifies a user associated with the display device. For example, control circuitry 504 may identify a default user associated with the display device. Process 1600 proceeds to 1608.

At 1608, control circuitry 504 retrieves user profile information. For example, user profile information may include the favorites and preferences of the default user for the display device. Process 1600 proceeds to 1610.

At 1610, control circuitry 504 determines whether the user has muted the guest user notifications. If the user has muted guest notifications, process 1600 proceeds to 1612. Otherwise, process 1600 proceeds to 1616.

At 1612, control circuitry 504 determines whether the media asset matches the preferences of the user. If the media asset does not match the preferences of the user for the display device, process 1600 proceeds to 1614. Otherwise, process 1600 proceeds to 1616.

At 1614, control circuitry 504 generates notifications for the media asset on the guest device. For example, the guest may receive a notification on his personal cell phone indicating an event of interest.

At 1616, control circuitry 504 generates notifications for the media asset on the display device. For example, a notification of the event of interest may appear on the display device.