GB2504274A

GB2504274A - Distributing encrypted multimedia data via a closed box

Info

Publication number: GB2504274A
Application number: GB1213058.9A
Authority: GB
Inventors: Jerome Anthony Santherasakaram
Original assignee: Individual
Current assignee: Individual
Priority date: 2012-07-23
Filing date: 2012-07-23
Publication date: 2014-01-29
Anticipated expiration: 2032-07-23
Also published as: GB2504274B; GB201213058D0

Abstract

A method of distributing multimedia data across a network comprising a server terminal 101 storing multimedia data, a server-dependent (or server-controlled) data processing device 105 and a user terminal 109 remote from the server, comprises the steps of; associating with the server-dependent device a user identifier of a user operating the user terminal; the server receiving a request 110 for multimedia data from the user terminal; encrypting or scrambling this data and communicating 104 the encrypted data to the server-dependent device; and storing the encrypted data at the server-dependent device. The server-dependent device may then decrypt the data and reproduce 108 the media for the user. The server-dependent device may be a closed, proprietary device configured for minimal user interaction and for preventing user access to its components, device file system and the encrypted media data. This method may be a form of digital rights management (DRM). The encryption and decryption step may use a unique registration key associated with the user identifier.

Description

METHOD AND SYSTEM FOR DISTRIBUTING MEDIA DATA

Field of the Invention

[0001] The present invention relates to a method and a system for distributing multimedia data in a network. More particularly, the present invention relates to an improved method and system for controlling the distribution and, through same, any subsequent use of multimedia data by a user.

io Background of the Invention

[0002] Many multimedia data distributions systems are known, with which users access remote media files, typically audio tracks and audio-video sequences, across a network for local reproduction at a user terminal or media playing device. In the context of the present disclosure, at its simplest such a system consists of a server storing a digital audio file and a user terminal, both remote from one another and connected to a common network, typically the Internet. The user terminal accesses the digital audio file at the server and downloads it therefrom over the network, and reproduces it locally, either after the entire file is downloaded, or as the file data is fed to the terminal by the network connection, a technique known as stream playing.

[0003] The ever more complex architecture and, correspondingly, ever-increasing cross-functionality of personal electronic devices, such as computers, portable computing devices, televisions, mobile telephones, high fidelity audio equipment, optical and/or storage-based media players and more, has resulted in a nearly limitless array of technical architectures with which to access, store and reproduce digital media data. The adoption of digital interconnecting and networking standards by most manufacturers of such devices, for the purpose of ensuring compatibility and inter-operability of these devices when connected to one another, is compounding this diversity with every new device or model iteration.

[0004] In parallel with the above, multimedia file formats and containers have likewise increased in diversity, to exploit the increasing functionality of media playing devices, and to reduce their bandwidth and storage requirements whilst maintaining and even improving the resolution of the media they encode.

For instance, in the early years of the Internet, distributed media files were commonly encoded in high-fidelity, substantially uncompressed formats such as the windows audio file format (way') and audio video interleaved format (avi'), both having substantial bandwidth and storage requirements. Comparatively, recent media file formats particularly suited for network distribution, such as the MPEG (1 or 2) audio layer Ill (mp3') format for digital audio and the Matroska multimedia container (mkv') for digital audio-video, provide higher-resolution media with substantially smaller storage requirements and, correspondingly, lower bandwidth requirements.

[0005] Several disadvantages have arisen from the above over time. A first important problem is that most distribution methods do not allow any control by the source provider over any subsequent redistribution of the digital media files by their users, after the files have been first distributed.

[0006] The advent and now widespread use of highly-contentious file-swapping networked applications is a symptomatic example of this issue, greatly facilitated when the source media files are not encrypted. Attempts to restrict users' access to and use of the media files, through Digital Rights Management (DRM') techniques, have repeatedly showed severe limitations, either through their defeat as a result of users' reverse-engineering efforts with a view to decrypt and still redistribute the files, or because of inherently defective implementations, to the extent that DRM was eventually abandoned in respect of audio compact discs by notable proponents such as EMITM and sonyTM. The root of the problem is thus the users' access to the media files once they are obtained from a first source, irrespective of whether these media files are encrypted or not, for any ulterior data processing tasks other than their straightforward reproduction for consumption. Such user access for ulterior purposes and motives is greatly facilitated by obtaining the files though multi-purpose, user-configurable data processing devices, typically personal computers, still the preferred platform of legitimate distribution.

[0007] A second important problem lies with legacy media playing devices that lack relevant data processing functionality and/or wide area network connectivity, and which still represent a vast majority of the global, installed user base.

[0008] Considering for instance television sets, very few liquid crystal display-based (LCD') models, and still fewer older cathode ray tube (CR1') models if any, include both networking means apt to interface the set with a remote multimedia data source across a wide area network and data processing means and/or instructions for same apt to access and download digital multimedia files from that source and to reproduce them. Many modern sets do is include data processing means and instructions for same apt to reproduce digital multimedia files, typically image files to the jpeg format, digital audio files to the mp3 format and audio-video files to the avi format, for instance compressed with the well-known DivXTM codec.

[0009] The same problem pervades high -fidelity audio equipment and many other types of conventional media playing platforms, both analogue and digital, still very few of which combine hardware and/or instructions relevant to both network connectivity, whether wide or local, and digital media file storage and processing.

[0010] Some modern devices within the above subset are known to include Universal Plug and Play (UPnP) -compliant networking means for connection to a networked computing device configured as a Digital Living Network Alliance (DLNA') server. Nevertheless, all such solutions still rely upon first obtaining multimedia files through a personal computer as explained above, and then somehow communicating the files to the set for reproduction.

[0011] Some further modern devices within the above subset are known to include Wide Area Network (WAN) connectivity, to obviate the requirement to first obtain multimedia files through a personal computer. Recent multimedia distribution services, which stream multimedia data on demand, such as NetflixTh and LovefilmlM have been developed to exploit this additional functionality. Nevertheless, all such solutions necessarily rely upon a stable network connection at the time of and throughout the requirement, with a bandwidth substantial enough to match the data processing throughput of the device and avoid intempestive buffering.

[0012] A simpler and improved method of distributing multimedia data, and a system embodying this method, are therefore required, which mitigate at least the above shortcomings of the prior art. In particular, the method and system should at least obviate a software-only approach, in order to prevent is user access to digital multimedia files, and be compatible with legacy media playing devices, for facilitating its integration with a user's existing equipment.

Summary of the Invention

[0013] The present invention provides a distributed method and system, which relies upon at least one server terminal remotely controlling proprietary server-dependent data processing devices located with respective users. The server stores multimedia data, which users can select for retrieval and eventual consumption, for instance in the form of one or more themed playlists in a user interface distributed by the server to a user terminal. Upon receiving a multimedia data request from a user, the server encrypts the requested multimedia data and communicates it to the server-dependent data processing device of the requesting user. The server-dependent data processing device has a limited operating interface, which does not permit user access to the device file system or stored encrypted media data, but permits a user to instruct a media selection and reproduction. The server-dependent data processing device decrypts and reproduces selected media, for instance as an audio or video sequence output to an external consumer device, as and when instructed to do so by the user.

[0014] According to an aspect of the present invention, there is therefore provided a method of distributing multimedia data across a network comprising at least one server terminal storing multimedia data, at least one server-dependent data processing device and one or more remote user terminals, comprising the steps of, at the at least one server terminal, associating the at least one server-dependent data processing device with a user identifier of the user operating the one or more remote user terminals; receiving at least one multimedia data request from at least one remote user terminal; and encrypting the requested multimedia data and communicating the encrypted data to the server-dependent data processing device; and, at the server-dependent data processing device, receiving and storing the encrypted multimedia data.

[0015] In an embodiment of the method according to the invention, the is method preferably comprises the further steps of assigning the at least one server-dependent data processing device with a unique registration key at the at least one server terminal and storing the unique registration key.

[0016] In a variant of this embodiment, the associating step preferably comprises the further step of associating the unique registration key with the user identifier.

[0017] In a variant of these embodiments, the encrypting step preferably comprises the further step of encrypting the requested multimedia data with the unique registration key.

[0018] In an embodiment of the method according to the invention, the method preferably comprises the further step of selecting multimedia data stored by the server terminal with the at least one remote user terminal across the network.

[0019] In an embodiment of the method according to the invention, the method preferably comprises the further step of decrypting the stored encrypted multimedia data at the server-dependent data processing device at a user -selected time of multimedia data reproduction.

[0020] In a variant of this embodiment, the decrypting step preferably comprises the further step of decrypting the stored encrypted multimedia data with the unique registration key.

[0021] In an embodiment of the method according to the invention, the method preferably comprises the further step of updating the encrypted multimedia data stored in the server-dependent data processing device with a next request.

[0022] According to another aspect of the present invention, there is also provided a system for distributing multimedia data across a network, comprising is one or more remote user terminals, connected to the network at least one server terminal, connected to the network and configured to store multimedia data, associate at least one server-dependent data processing device with a user identifier of a user operating the one or more remote user terminals, receive multimedia data requests from at least one remote user terminal, encrypt requested multimedia data and communicate the encrypted data to the at least one server-dependent data processing device; and the at least one server-dependent data processing device, connected to the network and configured to receive and store the encrypted multimedia data.

[0023] In an embodiment of the system according to the invention, the at least one server terminal is preferably further configured to assign a unique registration key to the or each server-dependent data processing device and to store assigned unique registrations.

[0024] In a variant of this embodiment, each unique registration key is preferably associated with a respective user identifier.

[0025] In a variant of these embodiments, the multimedia data is preferably encrypted with the unique registration key. The unique registration key may advantageously have a length of 256 bits.

[0026] In an embodiment of the system according to the invention, the at least one server-dependent data processing device is preferably further configured to decrypt the stored encrypted multimedia data at a user -selected time of multimedia data reproduction.

[0027] In a variant of this embodiment, the at least one server-dependent data processing device is preferably further configured to decrypt the stored encrypted multimedia data with the unique registration key.

[0028] According to yet another aspect of the present invention, there is is also provided a data processing device comprising data storage means, data processing means, networking means and at least one multimedia data output interface, configured as a server-dependent device for use with any of the above embodiments of the method and/or system according to the invention.

[0029] An embodiment of the server-dependent device according to the invention may preferably include a plurality of multimedia data output interfaces.

The or each multimedia data output interface may advantageously be selected from the group comprising analogue and digital interfaces, including composite audio and/or video sockets, RGB or Separate Video or component video sockets, SR/DIE sockets, optical TOSLINK' audio sockets, High-Definition Multimedia Interface ("HDMI") video or audio-video sockets, Digital Video Interface ("DVI") video sockets and Universal Serial Bus ("USB") data sockets.

[0030] According to still another aspect of the present invention, there is also provided a set of instructions recorded on a data carrying medium which, when processed by a data processing terminal connected to a network, configures the terminal as a server terminal apt to store multimedia data; associate a user identifier of a user operating one or more remote user terminals with at least one remote server-dependent data processing device; receive at least one multimedia data request from at least one remote user terminal operated by the user; and encrypt the requested multimedia data and communicate the encrypted data to the server-dependent data processing device associated with the user identifier.

[0031] An embodiment of the set of instructions according to the invention may preferably further configure the terminal as a server terminal apt to update the encrypted multimedia data stored in the server-dependent data processing device with a next request.

[0032] For any of the above embodiments and further variants, the multimedia data may be any data structure embodying one or a combination selected from the group comprising audio data, video data, audio-video data, Is interactive data.

[0033] For any of the above embodiments and further variants, the at least one multimedia data request may be for one or more data structures embodying an audio data sequence, a video data sequence and/or an audio-video sequence.

[0034] For any of the above embodiments and further variants, the or each user terminal may be any selected from the group comprising desktop computers, portable computers, tablet computers, personal digital assistants, portable media players, mobile telephone handsets, network -enabled television sets, set top media devices, network -enabled media players, home game consoles, portable game consoles.

[0035] For any of the above embodiments and further variants, multimedia data selected for retrieval and eventual consumption may be retrieved at user scheduled times. Changes or updates at the server-dependent data processing device may be scheduled for periods of time wherein bandwidth usage is minimal, thereby speeding up the communication process and minimising its impact on networking performance, this being a particular issue in areas with legacy or sparse communication infrastructure and shared or [0036] Moreover, changes or updates to the multimedia data, content and schedules at the server-dependent data processing device may be implemented as a background process, so that the server-dependent data processing device continues to deploy current content until the change or update is complete and playback is not interrupted.

[0037] Furthermore, for any of the above embodiments and further variants, multimedia data stored in the server -dependent device may be processed by the server -dependent device for reproduction at user -scheduled times. With this embodiment, a user may usefully schedule is multimedia data reproduction, i.e. specify start and end chronological points for the deployment of themed playlists, at the server.

[0038] For any of the above embodiments and further variants, the server-dependant data processing device may be supplied to the user, pre-loaded with one or more encrypted multimedia files, playlists and/or unique identifiers, associated with user data held on the server terminal. This embodiment advantageously further minimises communication requirements between the server-dependant data processing device and the server terminal.

[0039] Other aspects are as set out in the claims herein.

Brief Description of the Drawings

[0040] For a better understanding of the invention and to show how the same may be carried into effect, there will now be described by way of example only, specific embodiments, methods and processes according to the present invention with reference to the accompanying drawings in which: Figure 1 shows a network environment comprising a plurality of communication networks and a plurality of data processing terminals, including a variety of user terminal types, a server terminal and a server-dependent device, and a variety of multimedia reproducing consumer devices.

Figure 2 is a logical diagram of a typical hardware architecture of a mobile user terminal shown in Figure 1, in the example a mobile data communication device.

Figure 3 is a logical diagram of a typical hardware architecture of a data processing terminal configured as a server shown in Figure 1, the terminal including memory means.

Figure 4 is a logical diagram of a first hardware architecture of a server -dependent device shown in Figure 1, the device including memory means and a multimedia data output interface.

Figure 5 is a logical diagram of a second hardware architecture of a server -dependent device shown in Figure 1, the device including memory means and several multimedia data output interfaces.

Figure 6 details data processing steps of an embodiment of the method performed by the plurality of data processing terminals of Figure 1.

Figure 7 details certain data processing steps of the method of Figure 6 performed by the user terminal of Figure 1 and 2.

Figure 8 is a logical diagram of the contents of the memory means of the user terminal of Figures 1 and 1, when performing the method steps of Figures 6 and 7.

Figure 9 details certain data processing steps of the method of Figure 6 performed by the server of Figures 1 and 3.

Figure 10 is a logical diagram of the contents of the memory means of the server of Figures 1 and 3, when performing the method steps of Figures 6 and 8, including a database.

Figure 11 details certain data processing steps of the method of Figure 6 performed by the server-dependent device of Figures 1 and 4 or 5.

Figure 12 is a logical diagram of the contents of the memory means of the server-dependent device of Figures 1 and 4 or 5, when performing the method steps of Figures 6 and 9, including encrypted multimedia data and a registration key.

Detailed Description of the Embodiments

[0041] There will now be described by way of example a specific mode Is contemplated by the inventors. In the following description numerous specific details are set forth in order to provide a thorough understanding. It will be apparent however, to one skilled in the art, that the present invention may be practiced without limitation to these specific details. In other instances, well known methods and structures have not been described in detail so as not to

unnecessarily obscure the description.

[0042] With reference to Figure 1, an example embodiment of a system according to the invention is shown within a networked environment, which includes several communication networks interfaced with one another and a plurality of data processing terminals.

[0043] At least a first data processing terminal 101 is configured as a server 101 according to the invention, which stores and distributes multimedia files as will be described hereafter. The server 101 is connected to a Wide Area Network (WAN) communication network 102, in the example the Internet.

Generally, the at least one data processing terminal 101 may be any portable or desktop data processing device having networking means apt to establish a data communication with the other terminals described hereafter, across the WAN 102 and optionally further networks via one or more relevant gateways as required.

[0044] The server 101 sends and receives network data, which is any of voice, alphanumeric and/or audio-video data encoded using the Internet Protocol (IP), Voice data over IP (V0IP') protocol, Hypertext Transfer Protocol (HTTP') or Secure Hypertext Transfer Protocol (HTTPS'). The network data takes the form of digital signals embodying data packets, which a router 103 processes, operationally interfacing the server 101 with the wired WAN 102.

The router 103 forwards data packets originating from remote terminals and received across the WAN 102 to the server 101 and, reciprocally, data packets originating from the server 101 and addressed to remote terminals across the WAN 102. Incoming and outgoing data packets are carried locally over a wired Local Area Network (LAN') connection 104 conforming to the IEEE 802.3 is (Gigabit Ethernet') standard and/or over a wireless local area network (WLAN') connection 104 conforming to the 802.11 standard (Wi-Fi'), depending on the respective configurations of the router 103 and the server 101.

[0045] At least a second data processing terminal 105, located remotely from server 101, is configured as a server-dependent device 105 according to the invention, which receives, stores and reproduces multimedia files as will be described hereafter. The server-dependent device 105 reproduces multimedia files as a standalone unit and, depending on the embodiment, may or may not deploy with multimedia files stored therein, but in any case must be connected to the Wide Area Network (WAN) communication network 102 to receiveany updates to its stored content.

[0046] The server-dependent device 105 receives network data, which in one embodiment is one or more multimedia files stored by the server 101, encrypted by the server 101 and encoded using the Internet Protocol (IP), Hypertext Transfer Protocol (HTTP') or Secure Hypertext Transfer Protocol (HTTPS'). The network data again takes the form of digital signals embodying data packets, which another router 103 processes, operationally interfacing the server-dependent device 105 with the wired WAN 102 at the remote location, substantially as described above in relation to the server 101. The router 103 forwards data packets originating from the server 101 and received across the WAN 102 to the server-dependent device 105. Incoming data packets are carried locally over a wired Local Area Network (LAN') connection 104 conforming to the IEEE 802.3 (Gigabit Ethernet') standard and/or over a wireless local area network (WLAN') connection 104 conforming to the 802.11 standard (Wi-Fi'), depending on the configuration of the router 103 and the embodiment of the server-dependent device 105.

[0047] The server-dependent device 105 is a purpose-specific data processing device configured both for minimal user interaction and for preventing user access to its components and the data stored therein. In a basic embodiment, the server-dependent device 105 is a closed, proprietary device is having a network interface for establishing the connection 104 to the router 103, a minimal user interface for instance limited to an on/off switch and a play button, and at least one multimedia data output interface for communicating multimedia data, decrypted and reproduced as an analogue ordigital stream, to a local media amplifying and/or playing device, such as high fidelity audio equipment 106 or a television set 107, over a suitable interconnect 108.

[0048] At least a third data processing terminal 109 is a conventional user terminal. A suitable terminal is a mobile data communication device, in the example a mobile telephone handset 109 having wireless telecommunication emitting and receiving functionality over a cellular telephone network configured according to the Global System for Mobile Communication (GSM'), General Packet Radio Service (GPRS'), International Mobile Telecommunications-2000 (IMT -2000, W-CDMA' or 3G') network industry standards, and wherein telecommunication is performed as voice, alphanumeric or audio-video data using the Short Message Service (SMS') protocol, the Wireless Application protocol (WAF') the Hypertext Transfer Protocol (HTTP') or the Secure Hypertext Transfer Protocol (HTTPS').

[0049] The mobile telephone handset 109 receives or emits data encoded as a digital signal over a wireless data transmission 110, wherein the signal is relayed respectively to or from the handset by the geographically-closest communication link relay 111 of a plurality thereof. The plurality of communication link relays 111 allows digital signals to be routed between the handset 109 and their destination by means of a remote gateway 112 via a MSC or base station 113. The gateway 112 is for instance a communication network switch, which couples digital signal traffic between wireless telecommunication networks, such as the cellular network within which wireless data transmissions 110 take place, and the WAN 102. The gateway 112 further provides protocol conversion if required, for instance whether the handset 109 uses the WAP or HTTPS protocol to communicate data. The mobile data communication device 109 may additionally have wired wireless telecommunication emitting and receiving functionality over a wireless local area is network (WLAN') conforming to the 802.11 standard (Wi-Fi') as previously described, in addition to GSM, GPRS, W-CDMA and/or 3G.

[0050] A typical handset 109 for use with the system according to the invention is preferably that commonly referred to as a smartphone' and may for instance be an iPhonelM handset manufactured by the Apple Corporation or a Galaxy S TM series handset manufactured by Samsung Electronics Co. Generally, the mobile terminal 109 may be any portable data processing device having at least wireless communication means over one or more networks apt to communicate data with the server 101. It will therefore be readily understood by the skilled person from the present disclosure, that one or more of the mobile data communication devices 109 may instead be a portable computer commonly referred to as a laptop' or netbook' 114, a tablet computer 115 such as an AppleTM iPadTM or a MotorolaTM XOOMTM, and many other functionally comparable devices such as a personal digital assistant such as an Hewlett-PackardTM iPaqTM, a portable media player such as an ArchosTM 43 PMP, or even a portable entertainment device such as a SonyTM PlaystationTTM VitaTM.

[0051] A typical hardware architecture of a mobile telephone handset 109 is shown in Figure 2 in further detail, by way of non-limitative example.

[0052] The handset 109 firstly includes a data processing unit 201, for instance a general-purpose microprocessor (CPU'), acting as the main controller of the handset 109 and which is coupled with memory means 202, comprising non-volatile random-access memory (NVRAM').

[0053] The mobile telephone handset 109 further includes a modem 203 to implement the wireless communication functionality, as the modem provides the hardware interface to external communication systems, such as the GSM or GPRS cellular telephone network 111, 112, 113 shown in Figure 1. An aerial 204 coupled with the modem 203 facilitates the reception of wireless signals trom nearby communication link relays 111. The modem 203 is interfaced with is or includes an analogue-to-digital converter 205 (ADC') for demodulating wavelength wireless signals, for instance network data received via the antenna 204 into digital data, and reciprocally for outgoing data.

[0054] The handset 109 further includes self-locating means in the form of a GPS receiver 206, wherein the ADC 205 receives analogue positional and time data from orbiting satellites (not shown), which the data processing unit 201 or a dedicated data processing unit processes into digital positional and time data.

[0055] The handset 109 further includes a sound transducer 207, for converting ambient sound waves, such as the user's voice into an analogue signal, which the ADC 205 receives for the data processing unit 201 or a dedicated data processing unit to process into digital first audio data.

[0056] The handset 109 further includes imaging means 208 in the form of an electronic image sensor, typically a Charge-Coupled Device (CCD) objective for capturing image data which the data processing unit 201 or a dedicated data processing unit processes into digital image data.

[0057] The CPU 201, NVRAM 202, modem 203, GPS receiver 206, microphone 207 and digital camera 208 are connected by a data input/output bus 209, over which they communicate and to which further components of the handset 109 are similarly connected, in order to provide wireless communication functionality and receive user interrupts, inputs and configuration data.

[0058] Alphanumerical and/or image data processed by CPU 201 is output to a video display unit 210 (VDU'), from which user interrupts may also be received if it is a touch screen display. Further user interrupts may also be received from a keypad 211 of the handset, or from an external human interface device (HiD') connected to the handset via a Universal Serial Bus (USB') interface 212. The USB interface advantageously also allows the CPU 201 to is read data from and/or write data to an external or removable storage device.

Audio data processed by CPU 201 is output to a speaker unit 213.

[0059] Power is provided to the handset 109 by an internal module battery 214, which an electrical converter 215 charges from a mains power supply as and when required.

[0060] A typical hardware architecture of the data processing terminal 101 configured as a server is next shown in Figure 3 in further detail, by way of non-limitative example.

[0061] The data processing terminal 101 is a computer configured with a data processing unit 301, data outputting means such as video display unit (VDU) 302, data inputting means such as HiD devices, commonly a keyboard 303 and a pointing device (mouse) 304, as well as the VDU 302 itself if it is a touch screen display, and data inputting/outputting means such as the wired network connection 104, a magnetic data-carrying medium reader/writer 306 and an optical data-carrying medium reader/writer 307.

[0062] Within data processing unit 301, a central processing unit (CPU) 308 provides task co-ordination and data processing functionality. Sets of instructions and data for the CPU 308 are stored in memory means 309 and a hard disk storage unit 310 facilitates non-volatile storage of the instructions and the data. A wired or wireless network interface card (NIC) 311 provides the physical interface to the network connection 104. A universal serial bus (USB) input/output interface 312 facilitates connection to the keyboard and pointing devices 303, 304.

[0063] All of the above components are connected to a data input/output bus 313, to which the magnetic data-carrying medium reader/writer 306 and optical data-carrying medium reader/writer 307 are also connected. A video adapter 314 receives CPU instructions over the bus 313 for outputting processed data to VDU 302. All the components of data processing unit 301 are is powered by a power supply unit 315, which receives electrical power from a local mains power source and transforms same according to component ratings and requirements.

[0064] A hardware architecture of a first embodiment of the server-dependent device 105 for use with the system and method of the present invention is next shown in Figure 4 in further detail, by way of non-limitative

example.

[0065] As previously described, the server-dependent device 105 is a closed, purpose -specific data processing device configured both for minimal user interaction and for preventing user access to its components and the data stored therein. The core functionalities of the device include receiving encrypted multimedia data from the server 101 across the WAN 102 and storing same, and decrypting the stored multimedia data and reproducing it upon user request at the time of media consumption.

[0066] Accordingly, the server-dependent device 105 includes a central processing unit (CPU) 401, which provides task co-ordination and data processing functionality. Sets of instructions and runtime data for the CPU 401 are stored in a rewritable non-volatile memory 402, for instance NVRAM, NAND Flash or an EEPROM. A hard disk drive or solid state drive 403 facilitates non-volatile storage of encrypted multimedia data received from the server 101. A wired or wireless network interface card (NIC) 404 provides the physical interface to the network connection 104.

[0067] The first embodiment shown in Figure 4 is a basic architecture as introduced with reference to Figure 1, with a user interface 405 limited to a device on/off switch 406 and a play button 407, and one multimedia data output interface 408 for communicating multimedia data, decrypted and reproduced as an analogue audio signal to an external audio playing device, for instance the local high fidelity audio amplifier 106 over a relevant audio interconnect 108. An alternative embodiment of the server -dependent device 105, for use with an Is embodiment of the system permitting user -scheduled reproduction of stored multimedia data, even considers as minimal a user interface 405 as the device on/off switch 406 itself, since, in this embodiment, the play command is according to a schedule stored at the server 101 and distributed to the server -dependent device 105 as will be described hereafter.

[0068] A digital to analogue converter (DAC') 409 receives decrypted and processed digital data from the CPU 401 and outputs a corresponding analogue audio signal to the interface 408 which, in this simple embodiment, is a stereo socket for a 3.5mm TRS connector. Accordingly, the interconnect 108 in the example is an audio lead including, at one extremity, a 3.5mm TRS connector for the socket 408 and, at the other extremity, two stereo audio RCA connectors for complementary RCA sockets of the high fidelity audio amplifier 106.

[0069] All of the above components are connected to a data input/output bus 410. All the components of the server-dependent device 105 are powered by a power supply unit 411, which receives electrical power from a local mains power source and transforms same according to component ratings and requirements.

[0070] It will be readily understood by the skilled reader that the example architecture shown in Figure 4 is provided by way of example only, and that many variations in components and complexity can exist, without departing from the core characteristics and functionality described herein. For instance, with reference to Figure 5 now, a hardware architecture of a second embodiment of the server-dependent device 105 is shown in further detail, again by way of non-

limitative example.

[0071] The second embodiment shown in Figure 5 reprises the core components of the embodiment shown in Figure 4, but is a more complex architecture offering additional functions and connectivity, with a user interface is 405 having a device on/off switch 406 and media play button 407 as before, but expanded in this embodiment with additional media playing skip and pause buttons 501, 502, a media type switch 503 for operating a play selection between audio-only data and audio-video data, and a display for a Graphic User Interface (GUI) 506 providing operational information about the device such as current file being processed, current playlist being processed, device and/or media update status and media selection options.

[0072] The second embodiment includes two multimedia data output interfaces 408, 504 for communicating multimedia data, decrypted and reproduced as, respectively, an analogue audio signal to an external audio playing device, for instance the local high fidelity audio amplifier 106 over the TRS and RCA interconnect 108, or a digital audio-video signal to an external audio-video playing device, for instance the local television set 107 over another HDMI interconnect 108. In this embodiment therefore, an additional module 505 receives CPU instructions and/or output for outputting decrypted and processed digital audio-video data to the audio-video HDMI output interface 504.

[0073] It will be readily understood by the skilled reader that embodiments intended to minimise the number of multimedia data output interfaces may advantageously rely upon those types of interfaces which combine video and audio signals in a same connector, and the use of a Universal Serial Bus ("USB") socket is considered suitable for this purpose, in addition to any suitable amongst the above interface formats. By way of example, a particularly cost-effective embodiment may rely upon a single socket substantially as described with the reference 408 above, yet apt to output a combination of an analogue stereo audio signal and a composite video signal, for an interconnect 108 combining a 3.5mm IRS connector for the socket 408 and three RCA connectors, two audio and one video, for complementary RCA sockets of the television set 107.

[0074] Further alternative embodiments consider a battery-powered is solution rather than a PSU 411 and, preferably still, a hybrid mains-and-battery powered solution using one or more rechargeable high-capacity batteries, to permit portability of the device on an ad hoc basis, according to user requirements.

[0075] Details of data processing steps corresponding to an embodiment of the method performed in the environment of Figure 1 with the data processing devices 101, 105 and 109 or 114 or 115 are now provided with reference to Figure 6.

[0076] A user shall firstly obtain at least one server-dependent device from a relevant supplier, either the operator of the server 101 or another.

Upon taking possession of the or each device 105, the user must perform a one -time only registration procedure at the server 101 at step 601, in order to pair the device 105 with a respective user at the server 101. Ihe registration procedure is performed between a user terminal 109, 115 of the user and the server 101 across the WAN 102, wherein the server 101 distributes a relevant user interface, preferably a HIIP-secure web form in which the user inputs relevant alphanumerical data, for instance a unique server-dependent device identifier such as the device serial number and a unique user identifier such as a PIN or password. The unique server-dependent device identifier and unique user identifier data is communicated to the server 101, which stores them in a relevant data structure and generates a unique registration key for the device 105, whereby the server-dependent device is then uniquely associated with the user. The procedure may be repeated with any number of devices 105 for a same user. The server communicates the unique registration key to the device across the WAN 102 in order to validate connectivity to the device 105 and to complete the registration procedure.

[0077] In use, the user terminal 109, 115 logs in at the server 101 at step 602, for instance by inputting the username, PIN or password from step 601 in a relevant HTTP-secure form, then selects multimedia media stored at the server 101 for eventual reproduction. The selection procedure is again performed is between the user terminal 109, 115 of the user and the server 101 across the WAN 102, wherein the server 101 distributes a relevant user interface, preferably a HTTP-secure web page encoding a multimedia catalogue, in which the user may select multimedia data entry or entries, for instance groups of songs thematically or logically linked by any or more of musical genre, artist, dates, etc. presented to the user as themed playlists. In an alternative embodiment, the user may further schedule the multimedia data to be deployed between chronological parameters such as repetitive days or finite periods. The multimedia selection data and optionally the schedule data is communicated to the server 101, which stores same in a relevant data structure whereby the selection is uniquely associated with the user and, by comparison against the data structure uniquely associating the server-dependent device 105 with the user, the selection is likewise uniquely associated with the user's server-dependent device 105 and its unique registration key.

[0078] At step 603, the server 101 encrypts the selected multimedia data with the unique registration key. The encryption algorithm may conform to the AES standard and in a preferred embodiment has a block size of 256 bits, to impede any attempts to access and decode the multimedia data without permission, however improbable access to the encrypted multimedia files is due to the closed architecture of the end user device 105.

[0079] At step 604, the server 101 communicates the encrypted multimedia data to the user's server-dependent device 105 across the WAN 102, at which it is stored, still in encrypted form, in the permanent storage unit 403 at step 605. Any number of bandwidth and/or energy -saving techniques may be used as part of the data pushing step 604.

[0080] Upon completing the communication and storing of steps 604, 605 or, if the server-dependent device 105 is so configured, as a sufficient amount of encrypted multimedia data incoming from the server 101 becomes buffered by the server-dependent device 105, at step 606 the user commands local reproduction of the multimedia data selected at step 602 by the server-Is dependent device 105, for instance by pressing the play button 407 of the device user interface 405, wherein the device is commanded to decrypt the stored and/or buffered multimedia data and to output the decoded multimedia data to the output interface 408.

[0081] A question is subsequently asked at step 607, as to whether the user wishes to perform a new or further multimedia data selection at the remote server 101. If the question is answered positively, then control returns to step 602, at which the user may select further, different multimedia data, for its encryption, communication, storing and reproduction by the server-dependent device 105 according to step 603 to 606 as before. Alternatively, if the question is answered negatively, when the user eventually wishes to interrupt multimedia reproduction by the device 105, control proceeds to step 608 at which the device 105 is switched off or, preferably still, placed in a low-power standby mode providing sufficient power to the architecture of Figures 4 or 5 to maintain connectivity with the server 101, for instance to permit scheduled rather than real-time multimedia communication.

[0082] With reference to steps 601 and 602, Figure 7 further details certain data processing steps performed by the user terminal 109, 115 of Figures 1 and 2. The one -time only registration procedure of step 601 comprises a first step 701 of accessing the server 101 across the WAN 102, for instance with a network address of the server 101, typically the server's respective Uniform Resource Locator (URL'). At step 702, the user terminal 109, 115 receives the HTTP-secure web form. At step 703, the user inputs the server-dependent device's respective serial number and a personal identification number (PIN) in the form and communicates this data to the server, for instance with a relevant, user -selectable send' button on the form.

At step 704, the user terminal eventually receives a confirmation of registration from the server 101, after successful association of the device 105 with the user. This confirmation may take the form of a subsequent HTTP-secure web page, or an electronic mail message if the data inputting of step 703 requires an is electronic mail address of the user.

[0083] The multimedia selection procedure of step 602 601 comprises a first step 705 of accessing the server 101 across the WAN 102, for instance with the same network address of the server 101. At step 706, the user terminal 109, 115 receives a HTTP-secure form for authenticating access to the page displaying the multimedia data stored at the server 101. At step 707, the user inputs the personal identification number (PIN) in the form and communicates this data to the server, for instance with a relevant, user -selectable send' button on the form. At step 708, the user terminal eventually receives the HTTP-secure web page encoding a multimedia catalogue representative of the multimedia data stored at the server 101 and available for communication to the server-dependent device 105. At step 709, the user inputs a selection of multimedia data, typically one or more playlists as previously described, for instance with playlist-respective user -selectable select' tick boxes on the page, and communicates this selection to the server, for instance with a user -selectable send' button on the page. At step 710, the user terminal eventually receives a confirmation of selection from the server 101. This confirmation may again take the form of a subsequent HTTP-secure web page, or an electronic mail message if the data inputting of step 703 requires an electronic mail address of the user.

[0084] Further embodiments of the above method consider additional steps, for instance to administer the encrypted multimedia data stored by a server-dependent device 105, for instance commanding its partial or total deletion from the device 105 via corresponding commands to be sent from the server 101, updating stored multimedia data, scheduling multimedia data updating and scheduling stored multimedia data reproduction (playback). Such further steps may be provided through substantially the same user interface distributed by the server 101 to a logged-in user terminal 109, 115. Such user interface may preferably be rendered by the browser application of a user terminal 109, 115 in order to facilitate the cross-portability of the present solution to most user terminals apt to connect to the WAN 102, irrespective of is their operating system, architecture and multimedia capacities.

[0085] Thus, in an alternative embodiment of the method shown in Figures 6 and 7, a user firstly provides the operator of the server 101 with their registration details in order to create a user account. The registration procedure is again performed between a user terminal 109, 115 of the user and the server 101 across the WAN 102, wherein the server distributes a relevant user interface, preferably a HTTP secure web form in which the user inputs specified personal data such as name, address, and payment method. The server 101 stores the data as a unique user account with a unique identifier such a username and PIN or password.

[0086] In this embodiment, in use, the user terminal 109, 115 again logs in at the server 101, for instance by inputting the username, PIN or password from step 601 in a relevant HTTP-secure form. The user is then given the option either to select a server-dependent device 105 which they already have in their possession, for which a method as described with reference to Figures 6 and 7 is subsequently performed, or to configure a new server-dependent device 105 for eventual dispatch.

[0087] For any new server-dependent device 105 requested by the user, the server 101 selects the next available server-dependent device 105 serial number and generates a unique registration key for the device 105, then stores the unique registration key in a relevant data structure, whereby the server-dependent device 105 is then uniquely associated with the user. The user then selects multimedia media stored at the server 101 for storing on the new device prior to dispatch. The selection procedure is again performed between the user terminal 109, 115 of the user and the server 101 across the WAN 102, io wherein the server 101 distributes a relevant user interface, preferably a HTTP-secure web page encoding a multimedia catalogue, in which the user may select multimedia data entry or entries, for instance groups of songs thematically or logically linked by any or more of musical genre, artist, dates, etc. presented to the user as themed playlists. In addition, the user may is schedule the multimedia data to be deployed between chronological parameters such as repetitive days or finite periods. The multimedia selection data and optional schedule data is communicated to the server 101, which stores same in a relevant data structure described hereafter, whereby the selection is uniquely associated with the user and, by comparison against the data structure uniquely associating the server-dependent device 105 with the user, the selection is likewise uniquely associated with the user's server-dependent device 105 and its unique registration key.

[0088] The server 101 again encrypts the selected multimedia data with the unique registration key, per step 603. The encryption algorithm may conform to the AES standard and in a preferred embodiment has a block size of 256 bits, to impede any attempts to access and decode the multimedia data without permission, however improbable access to the encrypted multimedia files is due to the closed architecture of the end user device 105.

[0089] The server 101 again communicates the encrypted multimedia data to the respective server-dependent device 105 uniquely associated with the user per step 604, however wherein the device 105 is local to the server before its dispatch to the configuring user, and connected thereto for instance across the LAN 104 via the router 105. Thus the server 101 selects the relevant device 105 by serial number and communication takes place across the LAN, after which it is stored, still in encrypted form, in the permanent storage unit 403 per step 605. Upon completing the communication and storing of steps 604, 605 the server-dependent device 105 is fully configured according to the user selections and subsequently dispatched to the user.

[0090] After the user takes delivery of the pre-configured server- io dependent device 105, the user may command local reproduction of the pre-loaded multimedia data by the server-dependent device 105 per step 605, for instance by pressing the play button 407 of the device user interface 405, wherein the device is commanded to decrypt the stored and/or buffered multimedia data and to output the decoded multimedia data to the output is interface 408.

[0091] Figure 8 is a logical diagram of the contents of the memory means 202 of the mobile data communication device 109, when performing steps 701 to 710 at runtime. An operating system (OS') is shown at 801 which, depending on the handset manufacturer, may be OS 5TM developed and distributed by Apple, Inc. or AndroidTM developed and distributed by Google, Inc. [0092] A browser application is shown at 802, with which the mobile handset 109 may perform processing steps 701 to 710 as described hereinbefore, and which is interfaced with the OS 801 via one or more suitable Application Programming Interfaces (API'). Network data 803 associated with the method and system of the invention comprises web pages and/or forms as described in relation to steps 702, 704, 706, 708 and 710. Local data 804 associated with the method and system of the invention comprises alphanumerical input, e.g. device serial number and/or PIN, as well as interface inputs such as user multimedia or selections, as described in relation to steps 703, 707 and 709.

[0093] The memory 202 may further comprise local and/or network data that is unrelated to the method and system of the invention, respectively shown at 805 and 806, for instance used by or generated for another application being processed in parallel.

[0094] With reference to steps 601 to 604, Figure 9 details certain data processing steps of the method of Figure 6 performed by the server 101 of Figures 1 and 3. The server is configured by a main set of instructions described hereafter to perform the following step iteratively. At step 901, a network request is received from a user terminal 109, 115 and the server 101 determines whether the request is for a registration procedure according to step 601 or for logging in for a multimedia selection and optional scheduling according to step 602. If the request is for a registration, then at step 902 the server 101 communicates a HTTP-secure web form to the requesting user terminal and generates a new entry in a database for a new server-dependent device 105 with a new unique registration key. At step 903, the server receives the server-dependent device's respective serial number and PIN from the user terminal 109, 115 and populates the database entry with same, which associates the device 105 with the user. At step 904, the server communicates a confirmation of registration to the user terminal 109, 115 and communicates the registration key to the corresponding server-dependent device 105 in order to validate connectivity to the device 105 and to complete the registration procedure. Alternatively (Method 2) At step 903 the server selects from a list of available server-dependant devices 105 and serial numbers and populates the database entry with same, which associates the device 105 with the user.

[0095] Alternatively, the request is a login request and, at step 905, the server 101 communicates a HTTP-secure form to the requesting user terminal 109, 115 and eventually authenticates access at step 906 upon receiving the PIN data. At step 907, the server 101 communicates a HTTP-secure web page encoding a multimedia catalogue and optional schedule representative of the multimedia data stored at the server 101 and available for communication and optional scheduling to the server-dependent device 105 associated with the user of the requesting user terminal 109, 115. The user selection data of step 709 is eventually received at step 908, and the server 101 queues the selected multimedia data in a First-In First-Out (FIFO) buffer for encrypting with the registration key of the database entry associated with the logged-in user. At step 909, the server communicates a confirmation of selection to the user terminal 109, 115.

[0096] If no network request is received during an iteration of the above process, control defaults to step 603, at which the server encrypts the next multimedia data selection buffered in the FIFO with the registration key respectively associated with its target server-dependent device 105. At the next step 604, the server 101 communicates the next encrypted multimedia data output by the FIFO to its target server-dependent device 105. Control subsequently returns to step 901.

[0097] In a preferred embodiment, the CPU 308 of the server 101 is a multi-core CPU adapted to process multiple instructions concurrently, and the set of instructions is likewise configured to exploit this functionality by dedicating a processing thread to the remote terminal requests of steps 901 to 909, a processing thread to the encrypting of step 603 and a processing thread to the communicating of step 603, thus substantially increasing data processing throughput and the capacity of the server 101 to perform all of the above steps substantially in real-time.

[0098] Figure 10 is a logical diagram of the contents of the memory means 309 of the server 101 of Figures 1 and 3, when performing steps 603, 604 and 901 to 909 at runtime. An operating system (OS') is shown at 1001 which, if the server 101 is a desktop computer, is for instance Windows 7TM distributed by the Microsoft Corporation. The OS 1001 includes communication subroutines 1002 to configure the terminal for bilateral network communication via the NIC 311.

[0099] An application is shown at 1003, which configures the server 101 to perform at least processing steps 603, 604 and 901 to 909 as described hereinbefore, and which is interfaced with the OS 1001 and network communication subroutines 1002 thereof via one or more suitable Application Programming Interfaces (API).

[0100] Application data comprises local and network data. Network data 1005 comprises network requests 1006 from remote user terminals 109, 115 received via the NIC 311 and processed according to steps 901 to 909, network replies 1007 to the requests and including web pages and forms data, and encrypted multimedia data 1008 packeted for communication to remote server-dependent devices 105 according to step 604.

[0101] Local data comprises registration data and multimedia data user is selections 1009 extracted from network messages 1006, the FIFO buffer 1010 described with reference to steps 908, 603 and 604 including queued and encrypted multimedia data 1011, and a database 1012.

[0102] The database 1012 is relational and comprises a plurality of data structures, in the example data tables, wherein data is organized logically. Thus, a first table 1013 contains entries created at each iteration of step 902, wherein each such entry contains at least a unique server-dependent identifier 1014, a user identifier 1015 and a unique registration key 1016.

[0103] A same user may acquire several server-dependent devices 105, each such server-dependent device 105 having a respective entry, all such entries having a common user identifier 1015. In such a case, the user selection of step 709 may include a further selection of which device 105 to communicate the new multimedia data selection to.

[0104] A second table 1017 may contain entries, wherein each such entry contains at least one from the unique server-dependent identifier 1014, user identifier 1015 or unique registration key 1016, and playlist selection identifiers 1018. Further to the completion of step 604, this table usefully references multimedia tiles stored at each user's server-dependent device 105.

[0105] A third table 1019 may contain entries, wherein each such entry contains a playlist selection identifier 1018 and one or more multimedia data files identifiers 1020 representative of multimedia data file or files constituting a selectable playlist. Such multimedia data files are stored in the permanent storage 310, and are retrieved therefrom by the application 1003 for encrypting and communicating according to steps 603, 604 whenever an entry of table 1017 is updated with a next user selection.

[0106] A fourth table 1023 may contain entries, wherein each entry contains at least one from the unique server-dependent identifier 1014, user identifier 1015 or unique registration key 1016, and at least one set of is chronological parameters 1024 constituting a schedule. The schedule in table 1023 is for communications between the server and remote device 105 and, in the example, chronological parameters 1024 are shown respectively for a once-daily network communication starting at 23:00 and ending at 04:00 for a first device 105 and for a once-weekly communication starting at 22:00 for a second device 105. In an alternative embodiment, either the same table 1023 or a further, fifth table (not shown) may contain scheduling data for reproduction of the multimedia data stored in one or more remote devices 105. For instance, a user may schedule a breakfast' audio playlist to be reproduced between 08:00 and 10:00 Monday to Friday only, and/or may schedule a Christmas' playlist to be reproduced only between Pt and 3Pt December.

[0107] The memory 309 may further comprise local and/or network data that is unrelated to application 1003, respectively shown at 1021 and 1022, for instance used by or generated for another application being processed in parallel with application 1003.

[0108] With reference to steps 605 and 606, Figure 11 details certain data processing steps of the method of Figure 6 performed by the server-dependent device 105 of Figures 1 and 4 or 5. The device is initially switched on at step 1101, either by the user interacting with button 406, or by a Wake-On-WAN network message sent by the server 101 at the onset of step 604. An operating system (OS) and an application are loaded from the non-volatile memory 402 or the permanent storage 403 at step 1102, both of which configure the device 105 for standard operation as described hereafter.

[0109] At step 1103, a question is asked, as to whether a user input or interrupt has been received from the user interface 405, for instance a user activation of the play button 407. If the question is answered positively, then a second question is asked at step 1104, as to whether the user input corresponds to a device powering down command. If the second question is answered positively, the device powers down at step 1105 and, in a preferred embodiment, enters a low-power standby mode suitable for interruption by a Is Wake-On-WAN network message.

[0110] However, if the second question of step 1104 is answered negatively, then at step 1106 the device 105 accesses the encrypted multimedia data stored in the permanent storage means 403 at step 605 and the device-respective registration key 1016 received from step 904, and decrypts the encrypted multimedia data with the registration key. At step 1107, the decrypted multimedia data is output to the device media interface 408, 504 and therefrom to a media playing device 106, 107 via a relevant interconnect 108 and at which it is reproduced. Control subsequently returns to step 1103.

[0111] Alternatively, if the question of step 1103 is answered negatively, then at step 1108 the device 105 processes any network data packets incoming from the server 101 which, besides the limited user interface 405, constitutes the sole means of inputting any data into the device 105. For instance, in the alternative embodiment using the optional network communication scheduling stored in the fourth database table 1023, the server 101 sends a Wake-On-WAN network message according to the scheduling information 1024 to the device 105 which, upon receipt, performs steps 1101 and 1102, and pursuant to which the question of step 1103 is answered negatively.

[0112] The incoming data packets may comprise encrypted multimedia data communicated according to step 604, or server instructions to modify or delete part or all of the data respectively stored in the non-volatile memory 402 and in the permanent storage means 403. For instance, the server may relay user instructions to delete part or all of the multimedia data stored in the permanent storage means 403, to free storage for still newer multimedia data.

Likewise, the server may communicate an updated OS and/or application for improving the data processing functionality and efficiency of the device 105.

Accordingly, the processed data is stored at step 1109 in the non-volatile memory 402 or in the permanent storage means 403, according to the data type. Control subsequently returns to step 1103.

[0113] Figure 12 is a logical diagram of the contents of the memory means 402 of the server-dependent device of Figures 1 and 4 or 5, when performing steps 1101 to 1109 at runtime. An operating system is shown at 1201, which may be an embedded version of an Open Source or Windows OS.

The OS 1201 includes communication subroutines 1202 to configure the device for network communication via the NIC 404 and is integrated with an application shown at 1203. The application 1203 configures the device 105 to perform at least processing steps 1101 to 1109 as described hereinbefore, and is interfaced with the network communication subroutines 1202 for performing steps 1108 and 1109.

[0114] Application data comprises local and network data. Network data 1204 only comprises incoming data, and typically includes encrypted multimedia data received from the server 101 and being processed according to step 1108.

Pursuant to the above description, network data 1204 may at times also include a Wake-On-WAN network message and/or updates for, or an updated version of, the OS and application 1201, 1202, 1203.

[0115] Local data typically includes the device-respective registration key 1016, encrypted multimedia data 1205 fetched from the permanent storage means 403 when performing step 1106, and decrypted multimedia data 1206 output to the multimedia interface 408 when performing step 1107, typically a digital audio signal communicated to the DAC 409 over the bus 410 and/or a digital audio-video signal communicated to the GPU 505 over the bus 410.

Local data also includes user input 1207 read from the user interface 405 by the OS 1201.

[0116] The present invention thus provides a method and a system, wherein a server-dependent device 105 effectively replaces the traditional platform 109, 115 relied upon by a user to access, download and store multimedia data over a network, typically a personal computer. The closed architecture of the device 105 prevents access by the user to the multimedia data stored therein, and the encrypted character of the stored multimedia data further hinders any attempts to redistribute the multimedia data illegitimately.

The remote configuration of the device 105, performed via a platform-independent interface distributed by the server 101 by a user with any device apt to connect to the server 101 and process web pages and forms, advantageously allows a user to request multimedia files from the server 101 at any point in time and from any location. The central storing of all original multimedia data files by the server 101 allows standardisation of the data files formats and removes all concerns of equipment and codec compatibility with the multimedia files for the user. In a further benefit of the invention, rights inherent to the content of the multimedia files, typically copyrights, are administered from a central location by the operator of the server 101.

[0117] The embodiments in the invention described with reference to the drawings comprise a computer apparatus and/or processes performed in a computer apparatus. However, the invention also extends to computer programs, particularly computer programs stored on or in a carrier adapted to bring the invention into practice. The program may be in the form of source code, object code, or a code intermediate source and abject code, such as in partially compiled form or in any other form suitable for use in the implementation of the method according to the invention. The carrier may comprise a storage medium such as ROM, e.g. CD ROM, or magnetic recording medium, e.g. a floppy disk or hard disk. The carrier may be an electrical or optical signal which may be transmitted via an electrical or an optical cable or by radio or other means.

[0118] In the specification the terms "comprise, comprises, comprised and comprising" or any variation thereof and the terms include, includes, included and including" or any variation thereof are considered to be totally interchangeable and they should all be afforded the widest possible interpretation and vice versa.

[0119] The invention is not limited to the embodiments hereinbefore is described but may be varied in both construction and detail.

Claims

Claims 1. A method of distributing multimedia data across a network comprising at least one server terminal storing multimedia data, at least one server-dependent data processing device and one or more remote user terminals, comprising the steps of at the at least one server terminal, associating the at least one server-dependent data processing device with a user identifier of the user operating the one or more remote user terminals; receiving at least one multimedia data request from at least one remote user terminal; and encrypting the requested multimedia data and communicating the encrypted data to the server-dependent data processing device; and at the server-dependent data processing device, receiving and storing the encrypted multimedia data.
2. A method according to claim 1, comprising the further steps of assigning the at least one server-dependent data processing device with a unique registration key at the at least one server terminal and storing the unique registration key.
3. A method according to claim 2, wherein the associating step comprises the further step of associating the unique registration key with the user identifier.
4. A method according to claim 2 or 3, wherein the encrypting step comprises the further step of encrypting the requested multimedia data with the unique registration key.
5. A method according to any of claims 1 to 4, wherein the receiving step comprises the further step of selecting multimedia data stored by the server terminal with the at least one remote user terminal across the network.
6. A method according to any of claims 1 to 5, comprising the further step of decrypting the stored encrypted multimedia data at the server-dependent data processing device at a user -selected time of multimedia data reproduction.
7. A method according to claim 6 when depending on claim 4, is wherein the decrypting step comprises the further step of decrypting the stored encrypted multimedia data with the unique registration key.
8. A method according to any of claims 1 to 7, comprising the further step of updating the encrypted multimedia data stored in the server-dependent data processing device with a next request.
9. A method according to any of claims 1 to 8, wherein the multimedia data is any data structure embodying one or a combination selected from the group comprising audio data, video data, audio-video data, interactive data.
10. A method according to any of claims 1 to 9, wherein the at least one multimedia data request is for one or more data structures embodying an audio data sequence, a video data sequence and/or an audio-video sequence.
11. A method according to any of claims 1 to 10, wherein the or each user terminal is any selected from the group comprising desktop computers, portable computers, tablet computers, personal digital assistants, portable media players, mobile telephone handsets, network -enabled television sets, set top media devices, network -enabled media players, home game consoles, portable game consoles.
12. A method according to any of claims 1 to 11, comprising the further step of storing multimedia data file in the server-dependent data processing device before the steps of associating the at least one server-dependent data processing device with a user identifier and receiving at least one multimedia data request from the at least one remote user terminal.
13. A system for distributing multimedia data across a network, comprising one or more remote user terminals, connected to the network at least one server terminal, connected to the network and configured to store multimedia data, associate at least one server-dependent data processing device with a user identifier of a user operating the one or more remote user terminals, receive multimedia data requests from at least one remote user terminal, encrypt requested multimedia data and communicate the encrypted data to the at least one server-dependent data processing device; and the at least one server-dependent data processing device, connected to the network and configured to receive and store the encrypted multimedia data.
14. A system according to claim 13, wherein the at least one server terminal is further configured to assign a unique registration key to the or each server-dependent data processing device and to store assigned unique registrations.
15. A system according to claim 14, wherein each unique registration key is associated with a respective user identifier.
16. A system according to claim 1401 15, wherein the multimedia data is encrypted with the unique registration key.
17. A system according to any of claims 14 to 16, wherein the unique registration key has a length of 256 bits.
18. A system according to any of claims 13 to 17, wherein the at least one server-dependent data processing device is further configured to decrypt the stored encrypted multimedia data at a user -selected time of multimedia data reproduction.
19. A system according to claim 18 when depending on claim 16 or 17, wherein the at least one server-dependent data processing device is further configured to decrypt the stored encrypted multimedia data with the unique Is registration key.
20. A system according any of claims 13 to 19, wherein the multimedia data is any data structure embodying one or a combination selected from the group comprising audio data, video data, audio-video data, interactive data.
21. A system according to any of claims 13 to 20, wherein the at least one multimedia data request is for one or more data structures embodying an audio data sequence, a video data sequence and/or an audio-video sequence.
22. A system according to any of claims 13 to 21, wherein the or each user terminal is any selected from the group comprising desktop computers, portable computers, tablet computers, personal digital assistants, portable media players, mobile telephone handsets, network -enabled television sets, set top media devices, network -enabled media players, home game consoles, portable game consoles.
23. A data processing device comprising data storage means, data processing means, networking means and at least one multimedia data output interface, configured as a server-dependent device for use with the method of any of claims ito 12.
24. A data processing device comprising data storage means, data processing means, networking means and at least one multimedia data output interface, configured as a server-dependent device for use with the system of any of claims 13 to 22.
25. A device according to claim 23 or 24, comprising a plurality of multimedia data output interfaces.
26. A device according to any of claims 23 to 25, wherein the or each multimedia data output interface is selected from the group comprising analogue and digital interfaces, including composite audio and/or video sockets, RGB or Separate Video or component video sockets, SR/DIE sockets, optical TOSLINK' audio sockets, High-Definition Multimedia Interface ("HDMI") video or audio-video sockets, Digital Video Interface ("DVI") video sockets and Universal Serial Bus ("USB") data sockets.
27. A set of instructions recorded on a data carrying medium which, when processed by a data processing terminal connected to a network, configures the terminal as a server terminal apt to perform the steps of storing multimedia data; associating a user identifier of a user operating one or more remote user terminals with at least one remote server-dependent data processing device; receiving at least one multimedia data request from at least one remote user terminal operated by the user; and encrypting the requested multimedia data and communicating the encrypted data to the server-dependent data processing device associated with the user identifier.
28. A set of instructions according to claim 27, further configuring the terminal as a server terminal apt to perform the step of updating the encrypted multimedia data stored in the server-dependent data processing device with a next request.
29. A method substantially as described herein, in association with and as shown in the accompanying drawings.
30. A system substantially as described herein, in association with and as shown in the accompanying drawings.
31. A server-dependent data processing device substantially as described herein, in association with and as shown in the accompanying drawings.