Managing record events

Abstract

Systems, methods, and computer program products for managing and prioritizing record events. A priority manager includes an event list that lists scheduled record events. Each event in the event list has a priority that is different from the other events in the event list. If some of the events conflict, such as when a tuning resource is lost and unavailable, then those events with the highest priority in the event list are recorded. A user can assign priority to events when they are scheduled or at a later time. This enables event conflicts to be resolved by the user when the events are initially scheduled. When an event conflict arises later, the conflict is resolved by the priority manager according to the relative priority of the events in the event list.

1 . In a system that includes tuner resources, wherein tuner resources are required to perform record events in the system and wherein one or more record events are scheduled to record by using the tuner resources, a method for managing the record events such that the events are recorded according to their priority at least when a tuning resource is unavailable, the method comprising:
 maintaining a record event list with a priority manager, wherein the record event list includes one or more record events that have different priorities;   scheduling a new event, wherein scheduling the new event creates a conflict when a tuning resource is unavailable, the conflict being created with at least one other event that is already included in the record event list;   assigning a priority to the new event;   determining the record events to record when a tuning resource is unavailable, based on priorities of the record events in the record event list; and   performing the record events in the record event list that have the highest priority.   
   
   
       2 . A method as defined in  claim 1 , wherein determining the record events to record comprises determining that at least one tuning resource has become unavailable during a record event and wherein performing the record event comprises continuing recording of record events based on priorities of the record events in the record event list. 
   
   
       3 . A method as defined in  claim 1 , wherein assigning a priority to the new event comprises assigning the new event a higher priority than at least one conflicting event in the record event list. 
   
   
       4 . A method as defined in  claim 1 , wherein assigning a priority to the new event comprises assigning the new event a lower priority than at least one conflicting event in the record event list. 
   
   
       5 . A method as defined in  claim 1 , further comprising recording events with the highest priorities even when a conflict with another event is unresolved, wherein the conflicting events that have the lowest priority are not recorded. 
   
   
       6 . A method as defined in  claim 1 , further comprising assigning a default priority to the new event when the new event does not conflict with an event that is already scheduled. 
   
   
       7 . A method as defined in  claim 1 , wherein determining the record events to record when a tuning resource is unavailable further comprises:
 determining that there is insufficient storage to perform the record events in the record event list; and   deleting at least one program from the storage such that there is sufficient storage to perform a pending event in the record event list.   
   
   
       8 . A method as defined in  claim 7 , wherein deleting at least one program from the storage such that there is sufficient storage to perform a pending event in the record event list further comprises:
 identifying each program stored in the storage;   searching guide data to determine a program stored in the storage that is broadcast in the future;   deleting only programs scheduled for broadcast in the future; and   re-recording each deleted program at a later time.   
   
   
       9 . A method as defined in  claim 7 , wherein deleting at least one program from the storage such that there is sufficient storage to perform the events in the record event list further comprises at least one of:
 using the priority manager to identify programs for deletion based on a priority of the recorded programs; and   using criteria to determine which programs are deleted, wherein the criteria includes each of whether a recorded program is watched or unwatched, when a program was recorded, and a priority of the recorded program.   
   
   
       10 . A method as defined in  claim 7 , wherein deleting at least one program from the storage such that there is sufficient storage to perform a pending event in the record event list further comprises deleting at least one program using a priority manager for recorded programs, wherein the priority manager for recorded shows prioritizes the recorded programs such that recorded programs with the lowest priority are deleted in order to perform the events in the record list. 
   
   
       11 . In a system that records video streams received from a source, a method for prioritizing record events to determine which video streams are recorded when a tuning resource of the system is unavailable such that the system does not have sufficient tuning resources to record all of the record events, the method comprising:
 scheduling one or more record events in an event list, wherein each of the record events in the event list has an associated priority;   establishing a priority for new record events in the event list, the priority for each new record event being established by a a priority manager;   determining whether sufficient tuning resources are available to record each of the record events in the event list;   when one or more tuning resources are unavailable, such that more record events are currently scheduled than there are available tuning resources, determining which record events to record when a tuning resource is unavailable based on priorities of the record events in the event list, and thereby recording the record events in the event list that have the highest priority.   
   
   
       12 . A method as defined in  claim 11 , wherein scheduling one or more record events in an event list further comprises:
 scheduling a single record event;   scheduling a series record event;   scheduling a single manual record event;   scheduling a repeated manual record event; and   scheduling a smart record event.   
   
   
       13 . A method as defined in  claim 11 , wherein establishing a priority for new record events in the event list further comprises one of:
 for a new event, assigning the new event a priority that is higher than the lowest priority of those record events in the event list that conflict with the new event; or   for the new event, assigning the new event a priority that is lower than those record events in the event list that conflict with the new event.   
   
   
       14 . A method as defined in  claim 11 , wherein establishing a priority for new record events in the event list further comprises receiving an assignment of priority for at least one of the events in the event list from a user. 
   
   
       15 . A method as defined in claim I  1 , further comprising altering the priorities of the record events in the event list from another application. 
   
   
       16 . A method as defined in  claim 11 , wherein determining which record events to record when a tuning resource is unavailable comprises determining which record events to keep recording when a tuning resource becomes unavailable during recording of a record event in the event list, wherein unavailability of the tuning resource creates a conflict between record events. 
   
   
       17 . A computer-program product for use in a system that includes tuner resources, wherein tuner resources are required to perform record events in the system and wherein one or more record events are scheduled to record, the computer program product storing computer-executable instructions for managing the record events when one or more tuning resources are unavailable and such that the events are recorded according to their priority, the computer-executable instructions, when executed, causing the system to:
 maintain a record event list with a priority manager, wherein the record event list includes one or more record events that have different priorities;   schedule a new event based on user input, wherein scheduling the new event creates a conflict when a tuning resource is unavailable, the conflict being created with at least one other event that is already included in the record event list;   assign a priority to the new event;   determine the record events to record when a tuning resource is unavailable, based on priorities of the record events in the record event list; and   perform the record events in the record event list that have the highest priority.   
   
   
       18 . A computer-program product as defined in  claim 17 , wherein the computer program product is a set-top box. 
   
   
       19 . A computer-program product as defined in  claim 17 , wherein the priority assigned to the new event is received from the user. 
   
   
       20 . A computer-program product as defined in  claim 17 , wherein the computer-executable instructions, when executed, further cause the system to record events with the highest priorities even when a conflict with another event is unresolved or a tuning resource is unavailable, wherein conflicting events that have the lowest priority are not recorded.