GB2491344A

GB2491344A - Programme list management using assigned priorities

Info

Publication number: GB2491344A
Application number: GB1108620.4A
Authority: GB
Inventors: Christopher Mark Alder
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2011-05-23
Filing date: 2011-05-23
Publication date: 2012-12-05
Anticipated expiration: 2031-05-23
Also published as: GB201108620D0; GB2491344B

Abstract

Record list data (shown on graphical interface (GUI) 100, Figure 1) identifies record list groups (140), for genres such as news, sport and films, including one or more broadcast programs. In a method for record (program, content) list management, based also on programme characteristics, a record list or program group is selected (subscribed to) 210 for speculative recording of programs belonging to the group, e.g. recording a program series. Different priorities are then assigned 280 to different record list groups, and a broadcast recorder is controlled to schedule the recording of broadcast programs according to assigned priorities. Priorities or preferences may be based on event histories for recorded programs, such as measures of numbers of programs recorded 240, watched 260 or deleted (565, Figure 5), or based on a predetermined time period or memory storage capacity (e.g. low disc space; 620, Figure 6). Multiple, hierarchical priority levels may be assigned Figure 9 â with priorities set by content broadcasters, manually, or by using dynamic, automatic priorities. Lists may be identified using metadata. By assigning priorities to broadcast record list groups, conflict between programs belonging to different record list groups may be resolved.

Description

RECORD LIST MANAGEMENT

Field of the Invention

The present invention relates generally to broadcast content, and more specifically, but not exclusively, to a method and apparatus for managing record list data.

Background of the Invention

Digital broadcast systems, such as digital terrestrial television, enable program content to be broadcast to receiving devices. These receiving devices may comprise, amongst others, digital televisions, set-top boxes, digital video recorders (D'VRs), personal computers and mobile devices. A receiving device may be arranged to enable program content to be viewed live, i.e. contemporaneously with the time of broadcast, and/or recorded, for example for later viewing.

To facilitate the acquisition of broadcast program content broadcasters may make use of record list data. Record list data may comprise one or more record list groups of program content. Record list groups enable a method by which broadcasters may signal in a broadcast stream particular content to be acquired by an appropriately enabled receiving device. Once a user has selected a record list group, a receiving device can acquire the program content that belongs to the group without user intervention. This functionality may enable, for example, broadcasters to associate thematically-related content, expose users to niche programming or simplify the recording process for a user. For example, a record list group may identify program content where each program has a consistent theme such as "the best of the last week" or "classic films". When a user selects a particular record list group, events referenced by that list may be automatically booked and then acquired by a receiving device without further user intervention. Signalling that accompanies the broadcast program content may be used to achieve this end.

One problem that arises in the art is how to manage record list data. As a user subscribes to multiple record list groups it becomes more difficult to successfully acquire the appropriate program content.

Aspects of the present invention improve the process of scheduling programs to be recorded using record list data.

Summary of the Invention

In accordance with a first aspect of the present invention, there is provided a method for scheduling programs to be recorded from broadcast content, based on program data identifying characteristics of broadcast programs and using record list data, the record list data identifying record list groups, each of said record list groups including one or more broadcast programs, wherein a record list group may be selected for speculative recording on a broadcast recorder of broadcast programs belonging to the record list group, the method comprising: selecting, from said record list data, a plurality of record list groups for speculative recording on said broadcast recorder; assigning different priorities to different ones of said plurality of record list groups; controlling said broadcast recorder to schedule the recording of broadcast programs within said selected plurality of record list groups in accordance with said assigned priorities.

By assigning priorities to broadcast record list groups, conflict between programs that belong to different record list group may be resolved. This in turn increases the usability of record list groups.

In one embodiment, the method comprises storing event histories for broadcast programs which have been recorded, and assigning a score to a record list group based on event histories for broadcast programs within the record list group, the score being used to assign a priority for the record list group within said assigned priorities.

Using this method enables, for example, the actions of a user can be monitored such that priorities can be assigned with minimal user input. This makes the use of record list groups less onerous for a user and resolves conflict in a manner that is consistent with user preference.

The step of assigning priorities may comprise calculating the score for the record list group as a function of one or more of: a number of broadcast programs within the record list group that have been recorded; a number of broadcast programs within the record list group that have been watched; and a number of broadcast programs within the record list group that have been deleted.

In one embodiment, the step of assigning priorities is performed dynamically in accordance with at least one of: a broadcast program being recorded, watched, or deleted; scheduling of the recording of broadcast programs; and/or a predetermined time period having passed.

In this manner, a priority may be repeatedly updated over time such that any changes in user preference are reflected in the assigned priorities.

In certain embodiments, each priority may be modified by a user and, following modification, the priority is no longer dynamically assigned. This provides a way in which user-assigned and dynamically-assigned priorities can co-exist.

In one embodiment, the step of assigning priorities to different ones of said plurality of record list groups comprises assigning an initial priority to a newly selected record list group, said initial priority being predetermined for newly selected record list groups. For example, the lowest possible priority may initially be assigned and then modified over time in accordance with the dynamic calculations described above.

In one embodiment, when a first transmission time of a first broadcast program within a first record list group coincides partially or wholly with a second transmission time of second broadcast program within a second record list group, the method further comprises: comparing the priority of the first record list group with the priority of the second record list group; if the priority of the first record list group is higher than the priority of the second record list group, scheduling the recording of the first broadcast program; if the priority of the second record list group is higher than the score of the first record list group, scheduling the recording of the second broadcast program.

Hence, the assigned priorities may be used to resolve a conflict for tuner resources and an appropriate program may be selected for recordal. For example, this may be useful if a receiving device comprises a single tuner.

The above method may comprise determining if there are alternative broadcast times for the first and/or second broadcast program before comparing the priority of the first record list group with the priority of the second record list group.

In one embodiment, for a selected broadcast program of a selected record list group to be recorded, the method further comprises: determining one or more program scores of one or more respective recorded broadcast programs belonging to selected record list groups, said recorded broadcast programs being stored upon a storage device coupled to the broadcast recorder; comparing a program score of the selected broadcast program to be recorded with the one or more program scores of the one or more recorded broadcast programs; and deleting one or more of the one or more recorded broadcast programs if said recorded broadcast programs have program scores less than the program score of the selected broadcast program to be recorded, each program score being based on a respective record list group priority.

Hence, the assigned priorities may be used to resolve a conflict for storage device resources and storage space may be automatically freed if required. The program score may be directly based on the assigned record list group priority, e.g. could be the priority value itself, or it may be a function of the record list group priority, e.g. a function that additionally takes as input program-specific characteristics. As record list groups have the potential of comprising a large number of programs, a method for management of storage space when using record list groups is beneficial. For example, a record list group relating to a particular collection of films could comprise multiple programs over an hour in length, which would quickly consume storage space.

In a variation of the above method, the steps of determining, comparing and deleting are performed if it is determined that storage space in the storage device is below a predetermined threshold. The predetermined threshold may comprise the storage space required to record the selected broadcast program. If a broadcast program has been watched, the program score may comprise a function of the respective record list group priority and a number of viewings of the broadcast program. If the broadcast program has not been watched, the program score may comprise a function of the respective record list group priority and an age of the broadcast program.

In one embodiment, the priority for a record list group may be used to arrange the display of said plurality of record list groups on a user interface.

In one embodiment, the step of assigning priorities comprises assigning a priority at one of a plurality of levels, wherein a priority assigned at a first level overrides a priority assigned at a second level, wherein each level may be assigned by one of a user, a broadcaster or the broadcast recorder. This enables broadcasters to recommend programs to take priority without overriding user selections.

The priorities of the selected record list groups may be unique.

In accordance with a second aspect of the present invention, there is provided a broadcast recorder for scheduling programs to be recorded from broadcast content, based on program data identifying characteristics of broadcast programs and using record list data, the record list data identifying record list groups, each of said record list groups including one or more broadcast programs, wherein a record list group may be selected for speculative recording on a broadcast recorder of broadcast programs belonging to the record list group, the broadcast recorder being arranged to: receive a plurality of record list groups indicating selections, the plurality of record list groups being selected from said record list data for speculative recording on said broadcast recorder; assign different priorities to different ones of said plurality of record list groups; and schedule the recording of broadcast programs within said received plurality of record list groups in accordance with said assigned priorities.

The broadcast receiver of the second aspect may be adapted to provide features equivalent to any one of those described above as variations of the method of the first aspect of the invention.

In accordance with a third aspect of the present invention, there is provided a computer program comprising computer program code means arranged to perform the above methods when said code is processed by a computer processor.

Further features and advantages of the invention will become apparent from the following description of preferred embodiments of the invention, given by way of example only, which is made with reference to the accompanying drawings.

Brief Description of the Drawings

Figure 1 shows an exemplary user interface for selection of record list groups; Figure 2 shows a flow diagram for a first exemplary priority assignment process according to an embodiment of the present invention; Figure 3 shows a flow diagram for an exemplary scheduling process according to an embodiment of the present invention; Figure 4 shows a flow diagram for a first exemplary storage management process according to an embodiment of the present invention; Figure 5 shows a flow diagram for a second exemplary priority assignment process according to an embodiment of the present invention; Figure 6 shows a flow diagram for a second exemplary storage management process according to an embodiment of the present invention; Figure 7 shows an exemplary user interface for displaying record list groups that have been assigned a priority; Figure 8 shows an exemplary user interface illustrating how a user may manually assign a new priority; Figure 9 shows a flow diagram illustrating how a number of differently assigned priorities may be managed; and Figure 10 shows a schematic diagram of an exemplary receiving device that may be used to implement an embodiment of the present invention.

Detailed Description of the Invention

Figure 1 shows an exemplary user interface 100 for the management of record list groups. The user interface 100 may be implemented by a receiving device and displayed on a coupled display. The user interface may comprise a "Broadcast Record Lists" configuration screen 110, whereby a user is able to select and de-select record list groups. The user interface displays a plurality of record list groups 140, such as "News", "Sport" etc. The groups may be arranged hierarchically; for example, a user may select record list group "Films" and/or record list sub-groups "Action Films" and "Classic Films". The user may navigate the user interface using an input device such as a remote control to select and de-select record list groups. For example, in Figure 1 the user has highlighted the "Films" record list group. A short description or synopsis 120 of a selected group may be displayed above the list of record list groups. By activating an appropriate input device or user interface control, such as the "Subscribe" option 160, the user may subscribe or unsubscribe to the selected record list group or groups. For example, icon 130 in the form of a tick indicates that a user has selected available record list groups "News" and "Modem Classics: 2000-20 10" for subscription, which may be confirmed by selecting icon 160 or pressing an assigned remote control button. Subscription to a record list group may comprise subscribing to all child sub-groups if the record list groups support a hierarchy of groups. The term "subscribe" is used herein to refer to the selection of a record list group. A selection may be made on the basis of a variety of actions. A selection may be performed explicitly by a user or may be performed automatically, for example on a user's behalf based on event histories. The selection may be in relation to speculative recording, e.g. selecting a record list group such that programs belonging to the group are recorded. In some embodiments, the selection identifies a record list group to a receiving device such that the receiving device can monitor data channels for broadcast content belonging to the selected record list group.

Data identifiying record list groups may form part of broadcast data relating to programs and events, for example electronic program guide data and the like. For example, a record list group may be defined based on metadata carried over broadcast channels. The metadata may comprise a descriptive title and synopsis, along with a unique identifier for each record list group. The metadata may be based on the TV-Anytime XML model set out in published standard TS 102 822-3-1. The metadata may be received and decoded by a receiving device so as to automatically capture, store and expire recorded program content. Electronic program guide data for program content such as individual programs may include program content data that identifies one or more record list groups. For example, a news program "World News" may be associated with an identifier for the record list group "News". Electronic program guide data for program content may further include a start time, duration, program title and synopsis. Program and/or record list data may also be supplied separately from electronic program guide data, for example for programs that are "off-schedule", i.e. are not part of a broadcast schedule. These "off-schedule" programs may comprise on-demand programming. Program and/or record list data may be supplied in different ways: for example, as well as over-the-air using broadcast channels such data could be supplied over a wired or wireless network data connection. A server may be used to supply program and/or record list data, wherein the receiving devices communicates with the server using protocols available in the art to obtain such data. The association between a record list group and program content may be indirect, for example, a data element may be associated with a record list group identifier, the data element enabling a program to be resolved as an event. Once a user has subscribed to a record list group, a receiving device may be adapted to monitor broadcast content for program content belonging to a record list group and, on location of such program content, automatically schedule the recording of the program content using data such as start time, duration etc..

In one embodiment, one or more broadcasters of program content may provide both the record list groups, and the list of programs belonging to each group, via tables or data fragments carried in control data that forms part of the broadcast data stream. For example, the control data may comply with the digital storage media command and control (DSM-CC) standard that is defined as part of the Moving Picture Experts Group (IVIPEG) standards. When using a DSM-CC based system, the broadcast programs that belong to a record list group may be described in a push download program (PDP) fragment and may be identified by a Content Reference Identifier (CRID). A CRID is a globally unique identifier, similar to a Uniform Resource Locator (URL), that identifies a unit of content in a broadcast stream. Programs can be defined as either "On-Schedule", or "Off-Schedule". "On-Schedule" means the CRID referenced in the PDP fragment resolves to an entry in an Event Information Table (EIT). In this case, a receiving device may search EIT cache, i.e. a cache of EIT data stored based on received control data from a broadcast stream, and, when it finds a CRJD for a program that belongs to a subscribed record list group, the receiving device schedules or books the program for recording. The receiving device may retrieve and use metadata for the program, e.g. title, synopsis, start time etc., from the EIT. "Off Schedule" events do not exist in tables making up the EIT, so a receiving device may schedule a program belonging to a subscribed record list group based on the start time and location as described in the PDP fragment. In both cases, program metadata can be taken from an additional program information fragment.

If a DSM-CC based system is used, record list group and/or program information may be supplied as part of a data carousel; for example, in this case, a set of data that is repeated in a continuous cycle in a broadcast data stream, allowing a receiving device to tune into the stream at any time to retrieve the data. The record list group and/or program information may then be kept up to date by monitoring the data carousel periodically, for example every 10 minutes.

This may be used to supply record list data identifying available record list groups for selection by a user, e.g. the list of Figure 1, and/or program data to be used for speculative recording. In the case of "On-Schedule" bookings a receiving device may also monitor the EIT cache automatically.

Record list groups represent an improvement over grouping programs using genre or topic program data. Often program data is set by the publisher of content rather than a broadcaster, or even generated using third party databases, making it difficult to control program grouping. Genre or topic program data is inflexible; for example it limits grouping to thematically similar content, excluding curated groups such as "best TV of the last week". Typically, a program will only have a single genre or topic, which further prevents programs from being included in multiple groups.

Even though record list groups may be beneficial to a user, they may also lead to problems. As record list groups may comprise a large number of broadcast programs, and there may be a large number of record list groups, this may result in competition for limited hardware resources. For example, a receiving device may be limited in its ability to tune broadcast streams or channels. Hence, there may be the problem of collisions or conflicts between events belonging to different record lists groups. For example, the news program "World News" in the record list group "News" may have a broadcast time (an event) that partially or wholly overlaps with a broadcast time of a film "Adaptation" in the record list group "Modem Classics: 2000-20 10". If a receiving device comprises a single tuner resource for receiving broadcast signals then only one broadcast event may be recorded as the receiving device can only be tuned to a single broadcast stream. To compound matters, it is neither practical nor desirable to obtain input from the user to resolve these conflicts. For example, events may appear in a program guide schedule dynamically, and as such indications via a graphical user interface can interrupt viewing or occur at times when a user is not present.

If the receiving device comprises a storage device for recording program content, the use of record list groups may also rapidly consume available storage space. When the storage device is full no more recordings may be made until the user manually makes space by deleting recordings they no longer want.

There is thus a need for a broadcast recorder and a method of operating a receiving device that addresses these problems.

Embodiments of the present invention provide such an apparatus and method. For example, priorities may be assigned to different ones of said plurality of record list groups and these priorities may be used to control a broadcast recorder. If conflict for resources occurs, the priorities can be used to resolve the conflict and select an appropriate broadcast program.

Figure 2 illustrates an exemplary method 200 for managing record list groups. At step 210 a user subscribes to a record list group, i.e. selects a record list group for speculative recording. For example, this may be using the interface described with regard to Figure 1. A recording device acknowledges the subscription and implements procedures to schedule program content belonging to the subscribed record list group. In alternative embodiments, the step of selecting a record list group may be performed automatically on behalf of a user, for example, according to user preference data, instead of requiring a user-initiated subscription. Steps 220 to 290 represent a particular method of assigning a priority to the subscribed record list group. Steps 230 to 290 provide a method that assigns the priority dynamically, i.e. the assigns a priority that may change over time. These steps are for example only and the exemplary method may comprise additional or fewer steps in practice.

At step 220 a priority is assigned and initialised. This may comprise assigning an initial priority to the newly subscribed record list group. The initial priority may be predetermined. For example, it may comprise a priority that has not yet been assigned to other subscribed record list groups or a priority with a lowest value for a group of subscribed record list groups. The initialisation step may also involve generating count values for subsequent steps and initialising these values, e.g. to zero.

Steps 230 to 290 may be performed at any time following the initialisation step 220. They may also be performed repeatedly, either in response to one or more predefined events or at predetermined time intervals.

For example, the events may comprise: a broadcast program being recorded, watched, or deleted; a command to schedule the recording of broadcast programs; and/or a timer event. At step 230 a broadcast program is recorded, the program belonging to the broadcast record list group subscribed to in step 210.

This may give rise to an event that initiates the next step. At step 240 a count value is incremented. This count value comprises the number of programs belonging to the subscribed record list group that have been recorded; hence whenever a program within the group is newly recorded, the count value is updated. Incrementing the count value may occur directly, e.g. as soon as a program is recorded, or indirectly, e.g. based on histories or logs of activity stored by the recording device. At steps 250 and 260, actions similar to those of steps 240 and 250 are performed: at step 250 a program belonging to the subscribed record list group is watched and at step 260 a count value for the number of watched programs belonging to said group is incremented. A program may be considered watched may on a number of criteria; for example, a program may be considered to be watched when a user has viewed a set amount of a program, such as over fifty percent. This amount may be chosen to prevent a program being considered "watched", and thus used to assign a priority, if only a few minutes of the program have been watched. In alternative embodiments, additional or fewer events could give rise to usage metric for a record list group, for example the number of deleted programs as later described with regard to Figure 5.

At step 270 a metric is calculated based on the count values. In the present exemplary method the metric is a representation of the popularity of a particular record list group; for example, how popular a record list group is with a user. The metric is a function of the count values of steps 240 and 260, although other values may also be used to calculate the metric. The metric may be seen as a record list group score and may be calculated as a percentage. The function may equal the count value for the number of recorded programs, divided by 100 and all multiplied by the count value for the number of watched programs. Alternatively, the function may equal the number of recorded programs for a chosen group divided by the total number of recorded programs, e.g. the total number of recorded programs for all groups, multiplied by 100.

Other functions may also be used as required.

At step 280, the calculated metric is used to assign a priority to the record list group subscribed-to in step 210. At step 290 the priorities of other subscribed-to record list groups are also adjusted if required. This may be performed by ranking any subscribed-to record list groups in order of metric value and then applying a different priority to each ranked record list group. For example, if there were ten subscribed record list groups, each group may be assigned a priority from 0 to 9, wherein 9 may indicate the highest priority, e.g. the record list group with the largest metric value. It should be understood that priority values can be assigned in a variety of ways, for example a priority of 0 may indicate the highest priority, and so the examples described herein should not be construed as limiting. If priorities are assigned dynamically, steps 230 to 290 may be repeated, in which case after a metric for a particular record list group has been updated, it may be determined at step 280 whether the ranking of the group has changed. It may be that only a subset of the existing record list group priorities need adjusting at step 290; for example, if only two record list groups switch places based on an updated metric for one of the groups. Steps 280 and 290 may result in all subscribed record list groups having a unique priority value.

Figures 3 and 4 illustrate two examples of the use of assigned record list group priorities to resolve conflicts. In particular, Figure 3 illustrates an exemplary method 300 for scheduling recordings and Figure 4 illustrates an exemplary method 400 for deleting stored programs.

Turning to Figure 3, at step 310 an attempt is made to schedule recording of broadcast programs. For example, at a predetermined time or after a predetermined event, a receiving device may scan electronic program guide data for the presence of broadcast programs belonging to one or more subscribed record list groups or may monitor for over-the-air signalling that indicates a program belonging to a record list group is available for reception by the receiving device. On detection of a first program that belongs to a subscribed record list group, step 320 may be performed. Step 320 considers whether there is a conflict between the detected first program and any other program scheduled to be recorded. If there is no conflict then the program is scheduled to be recorded at step 350. If a conflict is detected, the method proceeds to step 330. A conflict may exist if a first transmission time of the first program, which belongs to a first record list group, coincides partially or wholly with a second transmission time of second program, which belongs to a second record list group. The second program may be indicated in a booking schedule. For example, the second program may have been scheduled for recording by applying steps 310, 320 and 350 in the past when no conflict existed. At step 330, if the receiving device is suitably adapted and the step is supported by the broadcast system, an attempt may be made to locate an altemative instance of the first program to avoid a conflict. For example, the first program may be repeated at a later time and/or date on the same or a different broadcast channel.

If an alternative instance of the first program is located in, for example, the electronic program guide data, the alternative instance of the first program may be scheduled at step 350. In some embodiments, the method 300 may be applied iteratively, such that the alternative instance of the first program is also checked for potential conflicts. If there are no alternative instances of the first program, or if this option is not available, then the method proceeds to step 340, wherein the priority of the first record list group is compared with the priority of the second record list group and one of the first or second programs is selected accordingly. For example, if the priority of the first record list group is higher than the priority of the second record list group, the first broadcast program may be selected; if the priority of the second record list group is higher than the score of the first record list group, the second broadcast program may be selected. At step 350 the selected program may then be scheduled. The unselected program is not scheduled. The exemplary method 300 of Figure 3 may be repeated for each detected program event that belongs to a record list group, or alternatively may be performed with regard to a list of potential program events that have been noted from broadcast data over time. In this manner, a booked event belonging to a higher priority record list group takes priority over a conflicting booked event belonging to a lower priority record list group, and automatically replaces it in a booking list. If alternative instances cannot be found, a higher priority event takes priority.

Figure 4 illustrates a related method 400 for resolving storage space conflicts. One or more of the methods of Figures 3 and 4 may be implemented on a receiving device. At step 410, a receiving device such as a broadcast recorder attempts to start recording a broadcast program. In other embodiments, the same method may be initiated when a recording is scheduled as well as, or instead of, when it is started. At step 420, the receiving device may be configured to determine the amount of storage space available for recording a program. As described previously, the receiving device may comprise one or more separate or integrated storage devices. These storage devices may be digital, such as magnetic disks or flash storage, or analogue, such as tape devices. Step 420 may comprise a check to see whether the storage device is low on storage space, wherein low" may be defined as when a storage space metric, such as time or megabytes remaining, falls below a predetermined threshold. In certain embodiments, the predetermined threshold may comprise at least the storage space required to record the broadcast program in question. If storage space exists, e.g. if a storage space metric is above a predetermined threshold, the program may be recorded at step 480. If, however, storage space is limited, for example the storage space metric is below a predetermined threshold the method proceeds to step 430. In this context, "above" and "below" may include values equal to any threshold.

At step 430, the group priorities for one or more recorded programs are analysed. The group priorities are the priorities assigned to the record list groups to which the recorded programs belong. In some embodiments, all recorded programs residing on the storage device may be analysed; in other embodiments this may only be performed for a filtered subset of recorded programs. At step 440, the record list group priorities of the analysed recorded programs are compared to a group priority for the program to be recorded. If a program with a lower record list group priority is located then that program is deleted from the storage device at step 460. At step 470, a check may be made to determine if the deletion of the program has freed enough storage space to record the proposed program. If there is still not enough space to record the program, step 440 may be repeated. If there is enough space to record the proposed program, the proposed program is recorded at step 480. If, however, no programs with lower record list group priorities are located, or if the deletion of any located programs does not free enough storage space, the recording of the proposed program may be aborted at step 450.

The method of Figure 4 effectively compares the priorities of booked events against the priorities of recorded events. If the booked events belong to a higher priority record list group, a broadcast recorder automatically deletes recorded programs belonging to the lower scoring record list group.

A number of variations of the above methods will now be described.

Figure 5 illustrates a second exemplary priority assignment process. This process is an extension of the process illustrated in Figure 2. Steps 510, 520, 530, 540, 550, 560, 570, 580 and 590 are similar to steps 210 to 290 of Figure 2.

The process of Figure 5 differs from the process of Figure 2 in that it takes account of deleted programs when calculating a metric at step 570. At step 555 a "program deleted" event is detected. This enables the incrementing of a count value for the number of deleted programs belonging to the same record list group as the deleted program. This occurs at step 565. The function to calculate the metric at step 570 can then take into account the number of deleted programs for a particular record list group. For example, the metric may be calculated according to the function: (number of recorded programs / 100) * (number of watched programs -number of deleted programs). By using the number of deleted programs in the calculation of the metric, the second exemplary process can take account of, for example, recorded programs from a particular record list group that were deleted immediately, and therefore not popular, or programs from a particular record list group that have been stored on the storage device for a long time but have not been watched. The record list group priority thus further indicates the popularity of a record list group for a user. For example, a record list group that contains events that are rarely watched, or simply deleted without being watched, would have a lower priority, and thus be indicated as less popular, than a record list group where events are watched many times and are not manually deleted. The methods of Figures 2 and 5 effectively assign a score to a record list group based on event histories for broadcast programs within the record list group, wherein the score is used to then assign a priority for the record list group.

Figure 6 illustrates a second exemplary storage management process.

This process comprises a modification of the storage management process of Figure 4. Steps 610 to 680 of Figure 6 correspond to steps 410 to 480 of Figure 2. However, in the second exemplary storage management process, a program score, rather than a group priority is used in steps 630 and 640. The program score is a function of the record list group priority that effectively weights the priority based on properties of an individual program. The program score may comprise a function of one or more of: the record list group priority for a particular program; the number of times the particular program has been watched; and, if a program has not been watched, the age of the program. The age of the program may comprise the time the program has resided on the storage device or the time since the broadcast of the program. The calculation of the program score may be as follows: If the program has been watched: Program score = group priority * number of viewings; If the program has not been watched: Program score = group priority / age.

The use of a program score that comprises a function of the record list group priority avoids the problem of a lack of storage space when any one group comprises a large number of programs. This is because the individual program score of programs within a record list group may vary from the group priority preventing a high priority record list group monopolising space upon the storage device.

An exemplary implementation of displaying record list groups with assigned priorities will now be described. Figure 7 shows a graphical user interface 700, similar to user interface 110 in Figure 1. User interface 700 displays the subscribed record list groups in the form of a list 710 organised by the record list priority. The list may comprise scroll bars and so include subscribed record list groups that are not visible upon the screen. For example, if there are seven subscribed groups, as shown in Figure 7, the top listed group - "Modem Classics: 2000-2010. Great Movies" -may have a priority of 7 and the bottom listed group -"News" -may have a priority of 1, with a priority of 0 being reserved for the initial priority for newly subscribed record list groups.

Figure 7 is provided as an example only, other user interfaces may be provided to display subscribed record list groups according to assigned priority. In such interfaces, the user may be able to view and/or change an assigned priority as will now be described with regard to Figure 8. The user interface need not be graphical and could be text based. It could also be accessed remotely, via an intermediate server or directly from the receiving device. For example, the user interface could be supplied to a mobile device to enable viewing and possible modification of priorities; any user input being subsequently sent to the receiving device, e.g. via a TCP/IP network.

In the user interface of Figure 7, a user is able to select a record list group, for example using a user input device such as a remote control. In Figure 7, group "News" 720 has been selected. Once a record list group is selected the user may modify the position of said group in the displayed list, for example, by pressing an "up" arrow on a remote control device. Figure 8 shows the result of a user moving group 720 to the top 730 of the list. This may be achieved by repeatedly pressing an "up" arrow on a remote control device. Group "News" is now assigned a priority of 6, replacing group -"Modem Classics: 2000-20 10.

Great Movies", which may now be assigned a priority of S. Priorities may be moved down as well as up.

In certain variations, when a user modifies a priority assigned to a record list group, for example as performed for record list group "News", the newly assigned priority may become exempt from dynamic updates, i.e. retain the newly assigned priority as a static priority. In effect when a user modifies a priority in this way they override the dynamically-assigned priority, i.e. the priority assigned, for example, using the methods of Figure 2 or Figure 5 when program usage count values change. In the example of Figure 8, once record list group "News" is moved to the top of the list of record list groups it may remain there, i.e. have the highest priority, despite dynamic update of the priorities of other record list groups. For example, in the "Adjust Priorities" step 290 or 590 in Figures 2 and 5, user-modified priorities may be assigned reserved priorities that are not available for dynamic assignment, e.g. only "News" can have priority 7.

If a user unsubscribes from a record list group, i.e. no longer wishes to speculative record program content belonging to that group, then a group priority may no longer be applied. Any recorded program belonging to the group that reside on the storage device may be treated as manual recordings, i.e. may not be subject to the algorithms of Figures 4 or 6.

Figure 9 illustrates an exemplary method wherein different types of priority may be assigned to a record list group. In the examples of Figures 2 and 5 the priority may be assigned automatically by a receiving device such as a broadcast recorder. However, in other cases a priority may be assigned by a third party, such as a broadcaster or publisher of program content. The priority could either be carried in the record list metadata, or be available on a server that a receiving device can communicate with, for example over a local, wide-area network or telecommunications network. This third-party priority may be assigned instead of, or as well as, a dynamically assigned priority as described above, and a user-assigned priority, as for example demonstrated with regard to Figure 8. In cases where only a single priority was assigned to each record list group, the methods of Figures 3, 4 and 6 would still apply. In cases where multiple levels of priority are used, for example in a hierarchy, the exemplary method of Figure 9 may be applied.

Figure 9 illustrates an exemplary method that is a variation on the method of Figure 3. Steps 910 and 920 are similar to steps 310 and 320: a program to be scheduled for recording is selected at step 910 and at step 920 it is determined whether a broadcast time for the selected program overlaps wholly or partially with a broadcast time for another scheduled program, i.e. whether a conflict exists. If no conflict exists the program is scheduled to be recorded at step 980. If a conflict does exist the method proceeds to step 930.

Steps 930 and 940 comprise comparing the various levels of priority in hierarchy order. In this example, manually-assigned priorities have precedence over third-party-assigned priorities, which in turn have precedence over dynamically-assigned priorities. In other examples, other priority level orders may be used, e.g. broadcaster priorities may have precedence over manually-assigned priorities. Returning to Figure 9, at step 930 it is determined whether any manually-assigned priorities exist for the record list groups to which the conflicting programs belong. If manually-assigned priorities do exist they are compared at step 950 and the program with the highest priority is scheduled at step 980. This may comprise scheduling a first program in place of a scheduled program or retaining a scheduled program and aborting the scheduling of the first program. If manually-assigned priorities do not exist, then at step 940 it is determined whether any third-party-assigned priorities exist. In this example, such priorities are broadcaster-assigned priorities and if they exist they are compared at step 960 for the conflicting programs. A program with the highest priority is scheduled at step 980. Third-party assigned priorities may be assigned to a particular program or a particular record list group. If no third-party-assigned priorities exist, then dynamically-assigned record list group priorities may be compared for the conflicting programs. These dynamically-assigned record list group priorities may be calculated at step 970 or be based on stored, i.e. pre-ealculated values. The program whose record list group has the highest priority is scheduled at step 980. In some variations, each level of priorities may comprise comparable priority values or priority values may be normalised so that priorities at different level may be compared.

The exemplary methods of Figures 4 and 6 may also be adapted in a similar manner to Figure 9, i.e. an iterative comparison of different priority levels may be performed at steps 440 or 640. For example, when deleting programs on a storage device, any manually set priority may have precedence over broadcaster-assigned priorities, which in turn may have precedence over dynamically calculated priorities. In this manner, as demonstrated by the method of Figure 9, the third-party assigned priorities effectively enable a broadcaster or publisher to suggest, rather than mandate, a priority for a record list group or a program within a group.

Figure 10 shows a schematic diagram of an exemplary receiving device 1000 that may be used to implement embodiments of the present invention. The receiving device is shown for example only and may comprise additional or fewer features than those illustrated in the Figure. The receiving device comprises a receiver 1030 for receiving a broadcast signal. This may be a terrestrial, cable, satellite or network signal, and may be received via aerial or port 1020. The receiver 1030 may comprise a single tuner for tuning into a single television channel. The receiving device further comprises one or more decoders 1040, for example one or more decoders complying with a Moving Picture Experts Group (MPEG) or Multimedia and Hypermedia Experts Group (MHEG) standard. Other signal processing components such as descramblers, demultiplexers etc. may be provided according to the form of the broadcast signal. Once a signal has been processed a graphical user interface 1050 may be provided and/or overlaid to enable display on display 1010. Display 1010 may be separate or integrated into the receiving device. Components 1030, 1040 and 1050 are illustrated in Figure 10 as being under control of a central processing unit (CPU) 1060 coupled to memory 1070; however, they may alternatively be coupled in series or any other known arrangement. CPU 1060 may be configured to process program code stored in memory 1070 to implement the methods described above, or alternatively such functionality may be provided by dedicated hardware. Memory 1070 may comprise a storage device as well as volatile memory. Alternatively, receiving device 1000 may have one or more integrated storage devices or be couple to one or more external storage devices.

Embodiments of the present invention enable the dynamic calculation of record list priorities or scores, based on how popular the groups, and programs within the groups are with the user. Certain examples provide a way in which such record list group priorities may be automatically generated, as well as variations that account for user and/or broadcaster assigned priorities. The embodiments provide a simple yet powerful mechanism to allow a user to make optimum use of available receiving device resources. They provide a method and system that are scalable for multiple broadcasters who each in tum offer multiple record list groups. The dynamic assignment of priorities may take account of a user's viewing preferences for recorded programs that belong to a record list group, resulting in an increasing priority for a group as more programs within the group are watched. The priorities may be set automatically to avoid making demands on a user. The priorities may then be used in algorithms that are applied when resources of a receiving device become limited, for example when tuner or magnetic disk resources are limited. The embodiments also enable a broadcaster to recommend a priority or score for a record list group or program, and these recommendations can be managed together with dynamically and user assigned priorities. A user interface may use assigned priorities to determine a simple ordered list for display of record list groups.

The above embodiments are to be understood as illustrative examples of the invention. Further embodiments of the invention are envisaged. For example, the variations also described above provide modifications of the described embodiments and the assignment of a priority may be performed with more complex probabilistic or statistical algorithms such as neural networks. It is to be understood that any feature described in relation to any one embodiment may be used alone, or in combination with other features described, and may also be used in combination with one or more features of any other of the embodiments, or any combination of any other of the embodiments.

Furthermore, equivalents and modifications not described above may also be employed without departing from the scope of the invention, which is defined in the accompanying claims.

Claims

Claims 1. A method for scheduling programs to be recorded from broadcast content, based on program data identifying characteristics of broadcast programs and using record list data, the record list data identifying record list groups, each of said record list groups including one or more broadcast programs, wherein a record list group may be selected for speculative recording on a broadcast recorder of broadcast programs belonging to the record list group, the method comprising: selecting, from said record list data, a plurality of record list groups for speculative recording on said broadcast recorder; assigning different priorities to different ones of said plurality of record list groups; controlling said broadcast recorder to schedule the recording of broadcast programs within said selected plurality of record list groups in accordance with said assigned priorities.
2. A method according to claim 1, comprising storing event histories for broadcast programs which have been recorded, and assigning a score to a record list group based on event histories for broadcast programs within the record list group, the score being used to assign a priority for the record list group within said assigned priorities.
3. A method according to claim 2, wherein the step of assigning priorities comprises calculating the score for the record list group as a function of one or more of: a number of broadcast programs within the record list group that have been recorded; a number of broadcast programs within the record list group that have been watched; and a number of broadcast programs within the record list group that have been deleted.
4. A method according to any preceding claim, wherein the step of assigning priorities is performed dynamically in accordance with at least one of: a broadcast program being recorded, watched, or deleted; scheduling of the recording of broadcast programs; and/or a predetermined time period having passed.
5. A method according to claim 4, wherein each priority may be modified by a user and, following modification, the priority is no longer dynamically assigned.
6. A method according to any preceding claim, wherein the step of assigning priorities to different ones of said plurality of record list groups comprises: assigning an initial priority to a newly selected record list group, said initial priority being predetermined for newly selected record list groups.
7. A method according to any preceding claim, wherein when a first transmission time of a first broadcast program within a first record list group coincides partially or wholly with a second transmission time of second broadcast program within a second record list group, the method further comprises: comparing the priority of the first record list group with the priority of the second record list group; if the priority of the first record list group is higher than the priority of the second record list group, scheduling the recording of the first broadcast program; if the priority of the second record list group is higher than the score of the first record list group, scheduling the recording of the second broadcast program.
8. A method according to claim 7, further comprising: determining if there are alternative broadcast times for the first and/or second broadcast program before cornparing the priority of the first record list group with the priority of the second record list group.
9. A method according to any preceding claim, wherein, for a selected broadcast program of a selected record list group to be recorded, the method further comprises: determining one or more program scores of one or more respective recorded broadcast programs belonging to selected record list groups, said recorded broadcast programs being stored upon a storage device coupled to the broadcast recorder; comparing a program score of the selected broadcast program to be recorded with the one or more program scores of the one or more recorded broadcast programs; and deleting one or more of the one or more recorded broadcast programs if said recorded broadcast programs have program scores less than the program score of the selected broadcast program to be recorded, each program score being based on a respective record list group priority.
10. A method according to claim 9, wherein the steps of determining, comparing and deleting are performed if it is determined that storage space in the storage device is below a predetermined threshold.
11. A method according to claim 10, wherein the predetermined threshold comprises the storage space required to record the selected broadcast program.
12. A method according to any one of claims 9 to 11, wherein, if a broadcast program has been watched, the program score comprises a function of the respective record list group priority and a number of viewings of the broadcast program, and if the broadcast program has not been watched, the program score comprises a function of the respective record list group priority and an age of the broadcast program.
13. A method according to any preceding claim, wherein said broadcast recorder comprises a single tuner.
14. A method according to any preceding claim, wherein the priority for a record list group is used to arrange the display of said plurality of record list groups on a user interface.
15. A method according to any preceding claim, wherein the step of assigning priorities comprises assigning a priority at one of a plurality of levels, wherein a priority assigned at a first level overrides a priority assigned at a second level.
16. A method according to claim 15, wherein each level is assigned by one of a user, a broadcaster or the broadcast recorder.
17. A method according to any preceding claim, wherein all the priorities of the selected record list groups are unique.
18. A broadcast recorder for scheduling programs to be recorded from broadcast content, based on program data identifying characteristics of broadcast programs and using record list data, the record list data identifying record list groups, each of said record list groups including one or more broadcast programs, wherein a record list group may be selected for speculative recording on a broadcast recorder of broadcast programs belonging to the record list group, the broadcast recorder being arranged to: receive a plurality of record list groups indicating selections, the plurality of record list groups being selected from said record list data for speculative recording on said broadcast recorder; assign different priorities to different ones of said plurality of record list groups; and schedule the recording of broadcast programs within said received plurality of record list groups in accordance with said assigned priorities.
19. A broadcast recorder according to claim 18, wherein the broadcast recorder is further arranged to: store event histories for broadcast programs which have been recorded, and assign a score to a record list group based on event histories of broadcast programs within the record list group, the score being used to assign a priority for the record list group within said assigned priorities.
20. A broadcast recorder according to claim 18, wherein the broadcast recorder is further arranged to calculate the score for the record list group as a function of one or more of: a number of broadcast programs within the record list group that have been recorded; a number of broadcast programs within the record list group that have been watched; and a number of broadcast programs within the record list group that have been deleted.
21. A broadcast recorder according to any one of claims 18 to 20, wherein the broadcast recorder is further arranged to dynamically assign priorities in accordance with at least one of a broadcast program being recorded, watched, or deleted; a command to schedule the recording of broadcast programs; and/or a predetermined time period having passed.
22. A broadcast recorder according to claim 21, further comprising: a user interface arranged to enable a user to modify a priority, wherein following modification, the broadcast recorder is arranged to no longer dynamically assign the modified priority.
23. A broadcast recorder according to any one of claims 18 to 22, wherein the broadcast recorder is further arranged to assign an initial priority to a newly selected record list group, said initial priority being predetermined for newly selected record list groups.
24. A broadcast recorder according to any one of claims 18 to 23, wherein the broadcast recorder is further arranged to: detect an event when a first transmission time of a first broadcast program within a first record list group coincides partially or wholly with a second transmission time of second broadcast program within a second record list group, and, on detection of said event, select one of the first broadcast program or the second broadcast program for recording based on a comparison of a first priority for the first record list group and a second priority for the second record list group.
25. A broadcaster recorder according to claim 24, wherein the broadcast recorder is arranged to determine if there are alternative broadcast times for the first and/or second broadcast program and only select one of the first or second broadcast programs if there are no alternative broadcast times.
26. A broadcast recorder according to any one of claims 18 to 25, wherein the broadcast recorder is couplable to a storage device and further arranged to delete a first broadcast program stored upon the storage device if a second broadcast program to be recorded has a program score higher than a program score of said first broadcast program, wherein the first and second broadcast programs belong to respective first and second record list groups and wherein each program score is based on a priority for a respective record list group.
27. A broadcast recorder according to claim 26, wherein if a broadcast program has been watched, the program score comprises a function of the priority of the respective record list group and a number of viewings of the broadcast program, and if the broadcast program has not been watched, the program score comprises a function of the priority of the respective record list group priority and an age of the broadcast program.
28. A broadcast recorder according to claim 26 or claim 27, wherein the broadcast recorder is further arranged to delete the first broadcast program if it is determined that storage space in the storage device is below a predetermined threshold.
29. A broadcast recorder according to claim 28, wherein the predetermined threshold comprises the storage space required to record the selected broadcast program.
30. A broadcast recorder according to any one of claims 18 to 29, wherein said broadcast recorder comprises a single tuner.
31. A broadcast recorder according to any one of claims 18 to 30, wherein the broadcast recorder is further arranged to use the assigned priorities to arrange the display of said plurality of record list groups on a user interface.
32. A broadcast recorder according to any one of claims 18 to 31, wherein the broadcast recorder is further arranged to receive a priority for a record list group and assign said priority to one or a plurality of priority levels, wherein a priority assigned at a first priority level overrides a priority assigned at a second priority level.
33. A broadcast recorder according to claim 32, wherein the priority is received from one of a user and a broadcast and overrides a priority assigned by the broadcast recorder.
34. A broadcast recorder according to any one of claims 18 to 33, wherein the broadcast recorder is arranged to assign unique priorities to all of the selected record list groups.
35. A computer program comprising computer program code means arranged to perform a method according to any one of claims 1 to 17 when said code is processed by a computer processor.