WO2015159104A1

WO2015159104A1 - System and method for managing stored media content

Info

Publication number: WO2015159104A1
Application number: PCT/GB2015/051173
Authority: WO
Inventors: Royston WALKER; Herve Murret-Labarthe; Cammy CRONIN
Original assignee: Sky Uk Limited
Priority date: 2014-04-17
Filing date: 2015-04-17
Publication date: 2015-10-22
Also published as: GB2525247B; GB201406980D0; GB2525247A

Abstract

A method and system for managing stored media content is described. A media receiver displays media library information corresponding to a set of media items, the media items comprising at least one local media item downloaded from a remote media server and stored at the media receiver. The media receiver stores data defining a respective key file associated with each of said at least one local media items, each data file including metadata defining a persistence state of the associated media item. A user command to archive a selected one of the media items in the media library is processed, whereby the selected media item is deleted from the media receiver and the metadata of the associated data file is updated with the archived persistence state.

Description

System and Method for Managing Stored Media Content

Field of the Invention

[0001] This invention relates to management of digital media content, particularly in broadcast receiver set top boxes (STBs) that download and store digital media content.

Background of the Invention

[0002] On-demand media content systems are generally known, in which a satellite receiver STB provides an interface for customers to browse, purchase and download media items from a remote server. Examples of satellite receiver STB's provided by the applicant, British Sky Broadcasting Ltd., are the Sky+® and Sky+® High Definition (HD) set top boxes. Both of these devices are configured with personal video recorder (PVR) functionality and have integrated storage devices for storing recorded programmes.

[0003] However, conventional media content systems typically provide rudimentary management of locally stored media content through an electronic programme guide (EPG). For example, the EPG commonly provides a user interface that lists locally stored media content and facilitates playback and deletion of the locally stored media content. As the size and prevalence of remote media content catalogues increases, the size of local media content libraries will increase as well, giving rise to unwieldy lists of locally stored media content.

[0004] US2009/0254966 (Josephs, et al) discusses upgrading STBs which have customer selected content stored thereon, allowing content stored on a STB to be uploaded to a network storage device, WO2013/026023 (Apple) discusses a system for managing local and remote media content in synchronized playlists across a user's multiple devices.

[0005] There is a need for a system that enables improved management of local and remote media content, particularly within a broadcast receiver environment. Statements of the Invention

[0006] Aspects of the present invention are set out in the accompanying claims.

[0007] According to one aspect of the present invention, a method of managing stored media items comprises displaying, by a media receiver, media library information corresponding to a set of media items, the media items comprising at least one local media item downloaded from a remote media server and stored at the media receiver; storing, by the media receiver, data defining a respective key file associated with each of said at least one local media items, each data file including metadata defining a persistence state of the associated media item; and processing a user command to archive a selected one of the media items in the media library, whereby the selected media item is deleted from the media receiver and the metadata of the associated data file is updated with the archived persistence state.

[0008] A user command to restore an archived media item in the media library can also be processed, whereby the media item is downloaded from the media server and the metadata of the associated data file is updated with a downloaded persistence state.

[0009] A user command to delete a selected one of the media items in the media library can be processed, whereby the selected media item and the associated data file are deleted from the media receiver.

[0010] A user command to restore a deleted media item to the media library can be processed, whereby the associated data file is transmitted by the media server to the media receiver. The restored media item can be downloaded from the media server to the media receiver after the associated data file is stored in the media library.

[0011] The media receiver is associated with a registered user of a media system. The media server can store a copy of the key files of the media library for a registered user in a user database. The key files stored by the media receiver can be synchronized with the key files stored by the media server.

[0012] The media library can be restored to a different media receiver by transmitting a plurality of key files of the media library to that media receiver.

[0013] The user command to restore a deleted media item can be received from a computing device associated with the registered user. [0014] In another aspect, the present invention provides a system comprising means for performing the above method. In yet another aspect, there is provided a computer program arranged to carry out the above method when executed by a programmable device.

Brief Description of the Drawings

[0015] There now follows, by way of example only, a detailed description of embodiments of the present invention, with references to the figures identified below.

[0016] Figure 1 is a block diagram showing the main components of a media system according to an embodiment of the invention.

[0017] Figure 2 is a block diagram of the functional components of an exemplary receiver in the system of Figure 1.

[0018] Figure 3, which comprises Figures 3 A and 3B, is a flow diagram of a media library management method according to an exemplary embodiment.

[0019] Figure 4, which comprises Figures 4A to 4K, is an example of an interactive user interface of the media receiver in Figure 1, according to embodiments of the invention.

[0020] Figure 5, which comprises Figures 5A to 5C is an example of a user interface of the computing device in Figure 1, according to an embodiment of the invention.

[0021] Figure 6 is a block diagram of the components of an exemplary media server in the system of Figure 1.

Detailed Description of Embodiments of the Invention

Media System Overview

[0022] Figure 1 shows schematically the main components of a media system 1 in an embodiment of the present invention. A media server 4 provides media content over a data network 5, such as a satellite, cable link and/or the Internet, to a plurality of receivers 3 associated with respective registered users. Only one receiver is shown in Figure 1 for clarity. The media server 4 includes a content database 6 storing remote media items 7a, such as audio and/or video programmes, movies, trailers, promotional videos, etc. The media server 4 also maintains a user database 8 storing data 9 for each registered user of the system 1, including details of each registered user's media library 31a, as well as other user details 32, such as account login, device and account settings, user preferences, etc.

[0023] The media server 4 can also maintain a listing of some or all of the content stored in the content database 6 and the content listing can be transmitted to the receiver 3 for display by a user interface 35. The content listing may be stored in the content database 6 and updated as new content is added to the media server. The user interface 35 provides an interactive interface to a plurality of services for the registered user, such as browsing listings of the remote media content 7a available from the media server 4, searching for local and/or remote media items 7, acquiring media items 7a (e.g., for free or in exchange for money, depending on the specific item) for addition into the registered user's media library 31, managing their accounts, etc. The user interface 35 also provides an interface for the user to manage his or her local media library 31b including media items 7b that the user has previously purchased and/or downloaded from the media server 4. It will be appreciated that the planner interface 35 can include one or more display modules, sections, tabs and/or screens for the respective user services.

[0024] The receiver 3 stores the received content listings and media items 7b of the user's local media library 31b in a memory 36, such as an integrated hard disk and/or an external storage device. The receiver 3 can subsequently playback the received media content in response to a user request, for example via the user interface 35. Each media item in the user's media library 31 is associated with a key file 37 containing metadata for the respective media item. The metadata includes data identifying the associated media item 7, along with a flag defining a persistence state of the associated media item within the media library 37 of the particular registered user. As will be described in more detail below, the key file 37 can be updated in response to user actions via the user interface 35 to manage the associate media item in the media library 31.

[0025] For example, the user interface 35 can provide a user-selectable option to archive the purchased media item 7b. The archive function of the receiver 3 causes the local, downloaded copy of the media item 7b to be deleted to free up space in the storage device 36, but retains the associated key file 37 in the user's local media library

3 lb with a further updated "archived" persistence state. Subsequently, the media item 7 is listed as "archived" by the user interface 35, providing the user with an option to "restore" the archived media item 7, causing the receiver 1 to download the media item 7a from the media server 4 again. It is appreciated that the registered user would not be required to purchase the media item 7 again when restoring an archived media item 7 to the local library 31b.

[0026] As another example, the user interface 35 can be configured to provide a user- selectable option to "delete" a media item 7b from the local media library 31b. The "delete" function causes the receiver 3 to remove both the purchased media item 7b and the associated key file 37b from the user's local library 31b, and consequently from the content listing displayed by the user interface 35. In this embodiment, the media server

4 can include an application module interface 38 that provides an interface for the registered user to login to his or her account and to restore the deleted media item. For example, the application module interface 38 may be a web server configured with a hosted web site. The application module interface 38 can provide a listing of all purchased media items 7b in the registered user's remote library 31a, for example based on the key files 37a stored therein, and give an option to restore each media item, which causes the media server 4 to transmit the associated key file 37a to the registered user's receiver 3. The application module interface 38 can be accessed via a corresponding application module 39 installed on the registered user's computing device 40, such as a web browser or a mobile app.

[0027] In the above embodiments, the user interface 35 can generate a graphical user interface (GUI) display screen using GUI templates which can be stored in the memory 36, together with other information stored in the memory 36, such as the remote content listings received from the media server 4 and local content listings of the media items 7b stored in the memory 36 of the receiver 3. The content listings may be stored in any form, such as an XML data file. As will be described below, a processor 23 can output a generated GUI to an audio visual display 2 via a suitable output interface 20. The receiver 3 also includes a suitable input interface 29 for receiving input commands by a user via a remote controller 28. [0028] Advantageously, the media system 1 provides improved management of local and remote media items by facilitating deletion of selected local media items from the receiver 3 and content listing by the user interface 35, and subsequent restoration of selected individual media items to the device and listing. Further advantageously, if the stored media items of a registered user's local library are wiped after a system reset, the user' s purchased and archived media content can be restored from the media server via the web server module. Furthermore, in the case of installation of a replacement or additional receiver for the registered user, the key files for the registered user can be downloaded onto the new receiver to efficiently rebuild the user's local library. Media Receiver Components

[0029] Figure 2 of the accompanying drawings shows one example of a receiver 3 in greater detail. Television signals from a satellite television broadcast network are input to a tuner 10. In this embodiment, only one tuner is illustrated but any plural number of tuners may be used in the receiver 3. The tuner 10 is tuneable to a particular channel of the satellite television broadcast network for reception of media content such as television programmes and movies. Signals from the tuner 10 are passed to a Quadrature Phase Shift Key (QPSK) demodulator 11. Demodulated signals are error- corrected by way of a forward error corrector circuit 12. The STB 3 has a hard disk 13 which receives from the forward error corrector circuit 12 compressed video and audio data representing received television programmes for recording and subsequent playback.

[0030] The received signals comprise digitally encoded data. In this example, the data is compressed using the Digital Video Broadcast/Moving Pictures Expert Group 2 (DVB/MPEG 2) standard which permits both programme data and additional data (for example interactive service data) to be transmitted in a single channel. DVB/MPEG 2 enables high compression ratios to be achieved. The hard disk 13 receives and stores compressed data. The data is decompressed only after retrieval from the hard disk 13.

[0031] Satellite (and indeed cable) programmes are usually scrambled to prevent unauthorised access by non-authorised subscribers. The STB 3 therefore has a conditional access control circuit 14 which co-operates with a smart card 14a to determine whether the viewer has subscribed to a particular channel and is therefore authorised to access the channel. Parental control over channel access is also provided, at least in part, by the access control circuit 14. The STB 3 further comprises a descrambling circuit 15 which is controlled by the access control circuit 14 to enable the descrambling of the signal by authorised subscribers. In an embodiment, the received data is stored in the hard disk 13 in the compressed and encrypted form. The data is decompressed as mentioned above and descrambled only after retrieval from the hard disk 13. In an embodiment, data received from a remote STB is also in compressed and encrypted form, and decompressed and descrambled in a similar manner on condition that access to the received data by the receiving STB 3 is allowed.

[0032] Descrambled data is supplied to a transport/demultiplexer 16 which separates the data into video data, audio data, user services data, programme scheduling data, etc. for distribution to various locations within the STB 3. The STB 3 also comprises a video decoder circuit 18 for video decompression and processing utilizing a dedicated video Random Access Memory (RAM) 17, and an audio decoder circuit 19 for audio decompression and processing, operating according to the MPEG 2 standard, for example. The video and audio decoder circuits 18 and 19 receive demultiplexed signals directly from the transport/demultiplexer 16, or from the hard disk 13. Decompressed video data is supplied to display circuitry 20, which may be a standard definition and/or a high definition display circuitry, for encoding and converting the video data into an appropriate format. The display circuitry 20 may for example provides the video data to a standard definition digital encoder and Digital to Analogue Converters (not shown) where the data is encoded and converted into an appropriate format for direct input to a television set. Alternatively, or in addition, the display circuitry 20 may supply the video data to a high definition digital encoder (not shown) where the data is encoded into an appropriate high definition format for output to a high definition TV via a High Definition Multimedia Interface (HDMI) interface (not shown). In this case, the HDMI interface may also receive decompressed audio data from the audio decoder circuit 19 via audio post-processing circuitry 21, for output to an HDMI input of a high definition TV if so desired. Decompressed and processed audio data may also be supplied to an audio DAC (not shown) for direct input to an analogue audio device or speakers. [0033] The STB 3 is controlled by a processor 23 which communicates with the various units of the STB via a bus 24. The processor 23 has associated with it Read Only Memory (ROM) 25 (optionally including a Compact Disc - Read Only Memory (CD- ROM) drive 25a), Random Access Memory (RAM 26) and a flash (non-volatile and writable) memory 36.

[0034] The processor 23 controls operation of the STB 3 by tuning the tuner 10 to receive signals for the desired channels by controlling the demultiplexing, descrambling and decompression so that the desired programme and/or interactive service data is displayed on the screen of the TV 2, and by controlling the hard disk 13 to record desired television programmes or movies, or to play back previously recorded media content. The processor 23 also controls operation of the STB 3 to play back previously recorded media content received from a remote STB, as will be discussed below. Viewer selection of desired programmes and customer services is controlled by viewer manipulation of a remote control unit 28, which in response to such viewer manipulation transmits control signals to a STB 29 for input to the processor 23. The remote control unit 28 also allows the viewer to control of the operation of the hard disk 13 to record television programmes, to play back recorded television programmes and to program the recording of television programmes, etc.

[0035] The STB 3 further comprises a wired network interface 30, such as an Ethernet network interface, and optionally a wireless network interface 31 providing a wireless network data link. The wired network interface 30 and the wireless network interface 31 may be connected to other devices of the LAN 1 such as a Personal Computer (PC), a games console and/or other digital equipment (not shown) via for example a router or switch (not shown). The network interfaces 30 and 31 enable the STB 3 to be connected to other devices, for example to enable reception of services transmitted via other media such as broadband cable, external storage media or digital terrestrial broadcast. The STB 3 may further comprise a modem interface 32 for connecting a telephone network.

[0036] The STB 3 may also comprise a media streaming server 22 to process and deliver media items stored in the hard disk 13 to remote media play back devices over the LAN 1 via the network interfaces 30 and 31. For example, the media streaming server 22 may provide a media stream to a remote STB connected to the LAN 1 for play back by the remote STB.

[0037] Operation of the STB 3 is controlled by software that makes the processor 23 responsive to control signals from the remote control unit 28, additional data in the received signals and/or data stored in the memory units 25 to 27. Interaction between hardware and software in the STB 3 is described in detail in our international patent application published as WO 01/11865. Operation of the STB 3 in receiving and decoding data representing television programmes and data defining scheduling and other information related to the programmes is described in detail in our international patent application published as WO 96/37996. Operation of the STB 3 in providing interactive services is described in our international patent application published as WO 97/23997.

[0038] Within the Digital Video Broadcasting (DVB) standards for digital TV transmission there exists a standard for the transmission of schedule information such that it can be decoded and presented correctly to subscribers in the form of an Electronic Programme Guide (EPG).

[0039] This DVB standard is known generally as the SI standard and can be found in the specification: ETS 300 468, ETSI Digital Broadcasting Systems for Television, Sound and Data Services; Specification for Service Information (SI) in Digital Video Broadcasting (DVB) Systems 2nd edition. Guidelines for using the specification are given in ETSI ETR 211 - DVB SI Guidelines.

[0040] In order to allow broadcasters to utilise any proprietary features of their EPGs the SI standard includes methodology for extending the format of the service information (SI) stream by the inclusion of private data tables and descriptors. The STB 3 is, of course, designed to support the mandatory parts of the SI specification.

Media Library Management

[0041] Figure 3 is a flow diagram illustrating a method of facilitating management of local and/or remote media items in the user's media library 31 according to one exemplary embodiment. Reference is also made to Figures 4A to 4K, illustrating an exemplary sequence of display screens of the planner interface 35, and to Figures 5A to 5C, illustrating an exemplary sequence of display screens of the application module 39. As illustrated, at step S3-1, the receiver 3 displays a listing of remote media content that is available from the media server via the user interface 35, for example in response to a user-input command to display the user interface 35 of the EPG. Figure 4A shows an example display screen 101 of the user interface 35, displaying remote media items 7a available via a virtual store front of the media server 4. At step S3-3, the receiver 3 receives user input selection of a remote media item 7a to be purchased. At step S3-5, the receiver 3 transmits a purchase request data message to the media server 4 identifying the selected media item 7a to be purchased. At step S3-7, the media server 4 identifies the selected media item from the received purchase request data message and if necessary, processes a payment transaction for the media item 7a, for example based on the registered user's account details 32. It is appreciated that there are various mechanisms for handling payment or billing of the purchased media item. A confirmation display screen 103 can be displayed by the planner interface, as shown in Figure 4B.

[0042] At step S3-9, the media server 4 generates a key file 37 for the purchased media item 7a, the key file 37 including metadata defining a "purchased" persistence state. At step S3-11, the media server 4 adds the generated key file 37a to the registered user's media library 31a stored in the user database 8. At step S3- 13, the media server 4 transmits the generated key file 37a to the registered user's receiver 3, as a response to the purchase request. The received key file 37b is stored in the user's local media library 31b. At step S3-15, the virtual store front of the user interface 35 is updated to reflect the purchased status 105 of the associated media item 7, as shown in the example display screen 107 of Figure 4C. The user interface 35 can also create a respective entry in the content listing of a planner interface for display to the user to reflect the purchased media item 7b.

[0043] At step S3- 17, the media item 7 is progressively downloaded from the media server 4 to the receiver 3, and stored in the user's media library 31b at step S3-19. The virtual store front of the user interface 35 can be updated to reflect the downloading status 111 of the purchased media item 7, as shown in the example display screen 113 of Figure 4D. The media server 4 may be configured to update the key file 37 for the purchased media item 7 to change the metadata to define a "downloading" persistence state. The updated key file is transmitted to the media server 4 to synchronise the user's local and remote media libraries. Alternatively, synchronization of the key files in the registered user's media library can be performed on an ad hoc and/or batch instruction basis.

[0044] Once the media item 7b has been downloaded and stored in the user's local media library 31b, the receiver 3 updates the persistence state in the key file 37b to a "downloaded" state, at step S3-21. The updated key file 7b is again transmitted to the media server 4 to re- synchronise the user's local and remote media libraries 31. The virtual store front of the user interface 35 is updated to reflect the downloaded and available status 115, as shown in the example display screens 117 of Figures 4E and 4F, together with a prompt 119 for the user to initiate play back of the local media item 7b. At step S3-23, the user interface 35 updates the content listing to reflect that the media item has been downloaded to the receiver 3 and provides a user-selectable option to archive the purchased media item 7b. As shown in Figure 4G, an example display screen 121 includes the planner interface listing local 7a and remote 7b media items purchased by the registered user, together with a prompt 123 for the user to select an archive function to be applied to the highlighted local media item 7a.

[0045] At step S3-25, in response to user input selection of the archive function, the receiver 3 deletes the media item 7b from local media library 31b in the memory 36. A confirmation display screen 125 may be displayed to the user prior to the receiver 2 executing the archive function, as shown in Figure 4H. At step S3-27, the key file 37b associated with the deleted media item 7 is updated with an "archived" persistence state. Subsequently, at step S3-29, the user interface 35 displays the deleted media item 7 as "archived", as shown in the exemplary display screen 127 of Figure 41, and provides the user with an option 129 to "restore" the archived media item 7.

[0046] At step S3-31, in response to user input selection of the restore function, the receiver 3 transmits a request to the media server 4 to re-download the media item. It is appreciated that the registered user would not be required to purchase the media item again when restoring an archived media item 7 to the local library 31b. Processing then returns to step S3- 17 as described above. [0047] The user interface 35 may be configured to provide a further user-selectable option to pause a progressive download that is in progress. Preferably in such a case, a media item 7 with a "paused" persistence state cannot be archived, although the user interface 35 may be further configured to provide this option.

[0048] Additionally or alternatively, the user interface 35 can be configured to provide a user-selectable option 133 to "delete" a media item 7b from the local library 31b, as shown in the exemplary display screen 131 of Figure 4J. At step S3-33, in response to user input selection of the "delete" function, the receiver 3 removes both the purchased media item 7b and the associated key file 37b from the user's local media library 31b. Consequently, the deleted media item 7 is removed from the content listing displayed by the user interface 35.

[0049] Subsequently, the registered user can decide to restore the deleted media item 7 to the local media library 31. At step S3 -35, the application module interface 38 of the media server 4 receives a user request to restore the deleted media item 7 from a listing of the user's media library 31, for example via a web page interface as shown in Figure 5. In response to the received request, the media server 4 transmits the key file 37a associated with the previously deleted media item 7 to the registered user's receiver 3, at step S3-37. A confirmation display screen may be generated and output to the user, as shown for example in Figure 5C. Consequently at step S3-39, the user interface 35 can display an updated content listing on the planner interface, which now includes the restored media item 7b with an associated purchased status, as shown in the exemplary display screen 135 of Figure 4K. The media receiver 3 may be configured to automatically initiate re-download of the restored media item 7b from the media server 4, or in response to a user input command, at step S3-41. Media Server

[0050] The media server 4 described herein may be implemented by any form of computer system, such as computer system 1000 as shown in Figure 6. Embodiments of the present invention may be implemented as programmable code for execution by such computer systems 1000. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures. [0051] Computer system 1000 includes one or more processors, such as processor 1004. Processor 1004 may be any type of processor, including but not limited to a special purpose or a general-purpose digital signal processor. Processor 1004 is connected to a communication infrastructure 1006 (for example, a bus or network). Various software implementations are described in terms of this exemplary computer system. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures.

[0052] Computer system 1000 may include a user input interface 1003 connected to one or more input device(s) 1005 and a display interface 1007 connected to one or more display(s) 1009. Input devices 1005 may include, for example, a pointing device such as a mouse or touchpad, a keyboard, a touchscreen such as a resistive or capacitive touchscreen, etc. After reading this description, it will become apparent to a person skilled in the art how to implement the invention using other computer systems and/or computer architectures, for example using mobile electronic devices with integrated input and display components.

[0053] Computer system 1000 also includes a main memory 1008, preferably random access memory (RAM), and may also include a secondary memory 610. Secondary memory 1010 may include, for example, a hard disk drive 1012 and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. Removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well-known manner. Removable storage unit 1018 represents a floppy disk, magnetic tape, optical disk, etc., which is read by and written to by removable storage drive 1014. As will be appreciated, removable storage unit 1018 includes a computer usable storage medium having stored therein computer software and/or data.

[0054] In alternative implementations, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 1000. Such means may include, for example, a removable storage unit 1022 and an interface 1020. Examples of such means may include a program cartridge and cartridge interface (such as that previously found in video game devices), a removable memory chip (such as an EPROM, or PROM, or flash memory) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from removable storage unit 1022 to computer system 1000. Alternatively, the program may be executed and/or the data accessed from the removable storage unit 1022, using the processor 1004 of the computer system 1000.

[0055] Computer system 1000 may also include a communication interface 1024. Communication interface 1024 allows software and data to be transferred between computer system 1000 and external devices. Examples of communication interface 1024 may include a modem, a network interface (such as an Ethernet card), a communication port, a Personal Computer Memory Card International Association (PCMCIA) slot and card, etc. Software and data transferred via communication interface 1024 are in the form of signals 1028, which may be electronic, electromagnetic, optical, or other signals capable of being received by communication interface 1024. These signals 1028 are provided to communication interface 1024 via a communication path 1026. Communication path 1026 carries signals 1028 and may be implemented using wire or cable, fibre optics, a phone line, a wireless link, a cellular phone link, a radio frequency link, or any other suitable communication channel. For instance, communication path 1026 may be implemented using a combination of channels.

[0056] The terms "computer program medium" and "computer usable medium" are used generally to refer to media such as removable storage drive 1014, a hard disk installed in hard disk drive 1012, and signals 1028. These computer program products are means for providing software to computer system 1000. However, these terms may also include signals (such as electrical, optical or electromagnetic signals) that embody the computer program disclosed herein.

[0057] Computer programs (also called computer control logic) are stored in main memory 1008 and/or secondary memory 1010. Computer programs may also be received via communication interface 1024. Such computer programs, when executed, enable computer system 1000 to implement embodiments of the present invention as discussed herein. Accordingly, such computer programs represent controllers of computer system 1000. Where the embodiment is implemented using software, the software may be stored in a computer program product 1030 and loaded into computer system 1000 using removable storage drive 1014, hard disk drive 1012, or communication interface 1024, to provide some examples.

[0058] Alternative embodiments may be implemented as control logic in hardware, firmware, or software or any combination thereof.

Alternative Embodiments

[0059] It will be understood that embodiments of the present invention are described herein by way of example only, and that various changes and modifications may be made without departing from the scope of the invention.

[0060] For example, the embodiments above are described with reference to a broadcast system, such as a satellite, cable or Internet broadcast system. Aspects of the invention are also applicable to a video on demand (VOD) or push video on demand (PVOD) system, in which a programme is received and/or displayed on demand.

[0061] Those skilled in the art will appreciate that there are various ways to reorder the operations described herein and that the particular order of operations illustrated in Figure 3 is merely exemplary.

[0062] In the embodiment described above, the receiver and media server store a plurality of application or software modules in memory, which when executed, enable the system to implement embodiments of the present invention as discussed herein. As those skilled in the art will appreciate, the software may be stored in a computer program product and loaded into the receiver and media server using any known instrument, such as removable storage disk or drive, hard disk drive, or communication interface, to provide some examples.

[0063] Alternative embodiments may be envisaged, which nevertheless fall within the scope of the following claims.

Claims

1. A method comprising:

displaying, by a media receiver, media library information corresponding to a set of media items, the media items comprising at least one local media item downloaded from a remote media server and stored at the media receiver; storing, by the media receiver, data defining a respective key file associated with each of said at least one local media items, each data file including metadata defining a persistence state of the associated media item; and processing a user command to archive a selected one of the media items in the media library whereby the selected media item is deleted from the media receiver and the metadata of the associated data file is updated with the archived persistence state.

2. The method claim 1, further comprising processing a user command to restore an archived media item in the media library whereby the media item is downloaded from the media server and the metadata of the associated data file is updated with a downloaded persistence state.

3. The method of claim 1 or 2, further comprising processing a user command to delete a selected one of the media items in the media library, whereby the selected media item and the associated data file are deleted from the media receiver.

4. The method of claim 3, further comprising processing a user command to restore a deleted media item to the media library whereby the associated data file is transmitted by the media server to the media receiver.

5. The method claim 4, further comprising downloading the restored media item from the media server to the media receiver after the associated data file is stored in the media library.

6. The method of any preceding claim, wherein the media receiver is associated with a registered user of a media system.

7. The method of claim 6, wherein the media server stores a copy of the key files of the media library for a registered user in a user database.

8. The method of claim 7, further comprising synchronising the key files stored by the media receiver and the key files stored by the media server.

9. The method of claim 7, further comprising restoring the media library to a second media receiver by transmitting a plurality of key files of the media library to the second media receiver.

10. The method of claim 6 when dependent on claim 4, wherein the user command to restore a deleted media item is received from a computing device associated with the registered user.

11. A system comprising means for performing the method of any one of claims 1 to 10.

12. A storage medium comprising machine readable instructions stored thereon for causing a computer system to perform a method in accordance with any one of claims 1 to 10.