GB2479164A

GB2479164A - Provisioning of customised media content

Info

Publication number: GB2479164A
Application number: GB1005396A
Authority: GB
Inventors: Morten Eidal; Anthony Rose
Original assignee: British Broadcasting Corp
Current assignee: British Broadcasting Corp
Priority date: 2010-03-30
Filing date: 2010-03-30
Publication date: 2011-10-05
Also published as: GB201005396D0

Abstract

Providing media content to a device (102) comprises: receiving data relating to the device; analysing the data to determine at least one appropriate attribute for the media content; receiving input commands from an input means of the device; actioning the input commands from the input means in dependence on the analysis of the data; and providing media content having said at least one appropriate attribute to the device. In response to a stored data string being communicated to a media content provider media content having at least one attribute in dependence on the digital data string, which contains information relating to the device specification, is received. The data is preferably a user agent string or a URL and preferably relates to at least one of the resolution of the media content, user interface, rendering protocol (e.g. HTML4, HTML5, Flash), playback protocol (e.g. Windows Media Player, HTTP over SSL RTSP) and play back mode.

Description

INTELLECTUAL

. .... PROPERTY OFFICE Application No. GB 1005396.5 RTM Date:28 July 2011 The following terms are registered trademarks and should be read as such wherever they occur in this document: Internet Explorer, Firefox and Windows.

Intellectual Property Office is an operating name of the Patent Office www.ipo.gov.uk Media Content Provision The present invention relates to a system for media content provision, a method for media content provision, and a device for playing media content. In particular, the present invention relates to providing customised media content to devices, without prior knowledge

of the devices' specifications.

According to the present invention there is provided a system for providing media content to a device, comprising: means (preferably in the form of a receiver) for receiving data relating to the device: means (preferably in the form of a processor and associated memory) for analysing the data to determine at least one appropriate attribute for the media content; and means (preferably in the form of a server having a processor and associated memory) for providing media content having at least one said appropriate attribute to the device. By providing media content to a device with attributes in dependence on data received, the most appropriate format of media content may be provided to the device without the system having prior knowledge of the specific type of device, or that device's specifications.

Preferably, the means for providing media content is adapted to select, or adjust, media content to provide media content to the device with the required attributes.

Preferably, the receiving means is adapted to receive the data from the device. More preferably, the data is contained within a digital data string sent from the device to the system communicating data other than said data. Yet more preferably, the digital data string is a standard variable communicated by said device, and may either be the user agent string or the uniform resource locator query string. By utilising a standard variable communicated by the device, the requirement for specific changes to devices to enable compatibility with the system may be reduced.

In the case where both a user agent string and a uniform resource locator query string are provided, preferably the analysing means is adapted to use data obtained from said Uniform Resource Locator query string in priority to the data obtained from the user agent string; thus manufacturers of the devices may test their devices with the system without the requirement of changing the user agent string.

Preferably, the data is appended to the end of the digital data string such that the original data contained with the digital data string is unaffected by the addition of said data.

Preferably, the data relates to media content attributes comprising at least one of: the resolution of the media content, the type of user interface, the user interface rendering protocol, the media playback protocol, and the media playback mode.

Preferably, the resolution includes at least one of; the number of vertical lines of video content, and the maximum bitrate of the media.

Preferably, the type of user interface includes interfaces optimised for television, mobile devices, personal computers, and set-top boxes.

Preferably, the user interface rendering protocol includes HTML4, HTML5, and Flash.

Preferably, the media playback protocol includes the video playback protocol and the audio playback protocol.

Preferably, the video playback protocol includes Flash, Windows Media Player streaming, HTTP over SSL streaming, HTTP progressive download, and RTSP streaming.

Preferably, the audio playback protocol includes Flash, Windows media player streaming, AAC over HTTP streaming, and MP3 over HTTP streaming.

Preferably, the system further comprises means for storing default values for each said attribute. By providing storage for default values the quantum of data being communicated may be reduced. Preferably, the media content is provided in dependence on the default values when an attribute is not specified in said data received from said device.

Preferably, the system further comprises means for providing additional media content in dependence on said data. More preferably, the additional media content is subtitles.

Preferably, the system further comprises means for receiving input commands from the device.

Preferably, the system further comprises means for analysing said input commands in dependence on said analysis of said data, and wherein said input commands are actioned in dependence on said analysis of said commands. By analysing the commands received from the device in dependence on the data, the system may be customised to accept commands from a device without having prior knowledge of the specific type of device, and can then action the commands by playing the media content, pausing the media content etc. Preferably, the commands are received via a device input means, such as a television remote control, a computer keyboard, or the like, in connection with the device.

According to a further aspect of the present invention there is provided a system for providing media content to a device, comprising: means for providing media content to the device; means for receiving data relating to the device input means; means for analysing the data; and means for receiving input commands from the input means via the device, wherein the input commands are actioned (for example, the media content is played, paused, fast-forwarded, rewound, etc) in dependence on the analysis of the data.

Preferably, the data includes key-mapping attributes to map the commands from said input device to actions relating to the provision of said media content. Such actions may be initiating playback of the media content, volume control of the media content, selecting different media content etc. Preferably, the key-mapping data relates to at least one command. More preferably, the key-mapping data relates to a group of commands.

Preferably, the system further comprises means for storing default key-mapping information. More preferably, the default key-mapping information is utilised when no key- mapping information is provided within said data, or when only a limited number of key-mapping information is provided.

Preferably, the system further comprises means for uploading said media content to said device.

Preferably, the system further comprises means for streaming said media content to said device.

Preferably, the streaming and/or uploading is initiated by said command.

According to a yet further aspect of the present invention there is provided a device for playing media content, comprising: means for storing a digital data string; means for communicating the digital data string to a media content provider; and means for receiving media content having attributes in dependence on the digital data string, wherein the digital data string contains information relating to the device specifications.

According to a still further aspect of the present invention there is provided a method of providing media content to a device, comprising: receiving data relating to the device; analysing the data; acquiring media content having at least one attribute; and providing the acquired media content having at least one attribute to the device, wherein the at least one attribute of the media content is in dependence on the analysis of the data.

According to a still further aspect of the present invention there is provided a method of providing media content to a device, comprising: providing media content to the device; receiving data relating to the device input means; analysing the data; receiving input commands from the input means via the device; and actioning the input commands in dependence on the analysis of the data.

According to a still further aspect of the present invention there is provided a method of playing media content, comprising: storing a digital data string; communicating the digital data string to a media content provider; and receiving media content having at least one attribute in dependence on the digital data string, wherein the digital data string contains

information relating to the device specifications.

The invention extends to methods and/or apparatus substantially as herein described with reference to the accompanying drawings.

The invention also provides a computer program and a computer program product for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, and a computer readable medium having stored thereon a program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.

The invention also provides a signal embodying a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, a method of transmitting such a signal, and a computer product having an operating system which supports a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.

Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.

Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, method aspects may be applied to apparatus aspects, and vice versa.

Furthermore, features implemented in hardware may generally be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly.

These and other aspects of the present invention will become apparent from the following exemplary embodiments that are described with reference to the following figures in which: Figure 1 shows a schematic representation of the media content provision system; Figure 2 shows a schematic representation of the data string provided by the device; Figure 3 shows a schematic representation of the content provision system, including the key-mapping feature.

Figure 1 shows a schematic representation of the media content provision system 100. The system is connected to multiple user devices 102, via the network 104 (such as the internet). Each user device has a user agent 106 that is utilised to playback the media content provided by the system over the network, and each user agent has a user agent string (UAS) 108. The system 100 comprises a server 110 with a user agent string identifier 112 adapted to cross-reference with the user agent string look-up table 114 in order to ascertain required attributes of the media content to be provided to the user device 102. The information contained within the UAS is processed by processor 116 using the data analysis engine 117, and in dependence on that processing the content provider 118 provides content from the content database 120 to the device over the network.

Figure 2 shows a schematic representation of the user agent string (data string) 108 provided by the device to the system over the network. The section 200 of the user agent string 108 is standard and is used by all devices when requesting data over a network, such as the internet. In addition to the standard data 200, further information including the device name 202, and specification tokens 204 to 206 are included to supply information to the

system about the specifications of the device.

The user agent string 108 may contain one or more of the attributes that can be specified, and where an attribute is not specified in the UAS a default value is utilised; this enables a reduction in the amount of data transmitted over the network.

In use, the system is in communication with the user device and receives, among other information and requests, the user agent string. The system then extracts the specification tokens from the user agent string using the user agent string identifier 112, and looks up the resulting data in the look-up table 114. The processor then analyses the data and requests the content provider 118 to serve up the required media content to the user device from the media content database 120.

Figure 3 shows a schematic representation of the content provision system, including a key-mapping feature. The system is similar to that shown in Figure 2, and like reference numerals refer to like features. In this example, the user agent 106 includes an input processor 300 that is adapted to receive commands from an input device such as a keyboard 302 or a remote control 304. Those commands are provided, via the network, in order to control the media content playback. In order to allow customisation of the actions taken upon receipt of a command from the input device, further specification tokens may be inserted into the user agent string that map keys on the input device to actions within the media content player. The key-mapper 306 is then utilised to store the customised key-map for that device. Examples of such key-mapping are provided below.

Specific aspects of the system architecture The media content provider may provide content in a wide range of user interface and playback options, including: o user interface styles (mobile devices, desktop computers, TV (i.e. bigscreen), set-top boxes, DVD players, Blu-ray players) a rendering technologies (Flash, HTML) o playback technologies (Flash, Windows Media Player, Real Player, H.264, MPEG2) o transport protocols (RTMP, SSL, HTTP) o audio and video formats (H.264, WMV, AAC, MP3, WMA) o video bitrates (200Kbps to 3.2Mbps) o video resolutions (176x140 to 1280x720 HD) o configurable key maps These various options and combinations of options are suitable for multiple platforms, and hence a wide range of platforms may be supported.

To enable multiple devices, such as next-generation mobile phones, set-top boxes, games consoles and portable computing devices, televisions, desktop personal computers etc, to access the media content via the system, manufacturers of the devices are provided with means to specify, via the user agent string passed to the system server on web page requests, the optimal display and media formats to deliver for the device. The various attributes available are stored within the user agent string look-up table 114.

In the preferred embodiment, the devices access the system using a web browser.When a web browser makes a request to a web server, along with the URL that the web browser is requesting, it passes a user agent string. The user agent string is a text field in an HTTP request header that contains the name and version of the browser. The server uses the UAS to identify the browser (e.g. Internet Explorer, Firefox, etc.), and allows the server to generate a web page that may display optimally on that browser.

An example of a UAS generated by Internet Explorer 8 is provided below: MoziIIa/4.O (compatib'e; MSIE 8.0; Windows NT 6.2; Trident/4.O; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0) The UAS informs the server that the user device is a PC running Windows, with.NET and Windows Media Centre installed, allowing the server to make decisions based on the device configuration.

The present system defines a custom UAS, including extensions, which, if passed with page requests from the device, may allow the system server to serve up web pages and media content best suited for the device's needs and capabilities.

This is accomplished by modifying the UAS (which is usually stored in a config file or registry entry on the device) to append the parameters listed below, to set the optimal media content player appearance and functionality on the device. It should be noted that the same UAS is modified both when specifying attributes of the media content, and when mapping keys.

For example, the device manufacturer could make use of the UAS in the following manner to specify a custom media content player display for the manufacturer's device. In this example, the device is a Linux-based that runs the Opera browser, and so it would have a UAS that looked something like this: Operal9.64 (Linux i686; U; sv) If a user visited the media content player web site from the device, they would get the default media content player web page (i.e. designed for a PC with a 1024x768 or greater screen, with Flash installed, and able to play 1500Kbps SD-quality video).

However, if the device has a much smaller screen (e.g. 800x600), and its limited CPU power is only able to support our 640x360, 800Kbps video stream. This would mean that the normal media content player web site would be too large for the device's screen resolution, and the device's CPU may not have enough power to render the higher bitrate video formats.

Therefore, with the present system, a few parameters may be added to the UAS used by the device's browser, like this: Opera/9.64 (Linux i686; U; sv) (avuiltv; avvl/400; avvp/flash) * avsf ("media content player User Interface") followed by Itv means that the device is requesting the iPlayer's landscape format user interface, which is designed for TV5 and devices with lower screen resolutions, rather than the default user.

* avvl ("media content player Video Lines") followed by /400 means that the device is specifying that the largest video window size that it can handle is 400 pixels. For example, when the media content is video in 16:9 format, this means the device is requesting to display the largest available video format that is less than 710x400, which could mean that the media content provision system would select the 640x360 video window size for the device.

* avvp ("media content player Video Player") followed by /flash means that the device is specifying that the video may play back using its in-built Flash player.

Providing the manufacturer with these customisation options means that they can tune the media content player to each device's unique requirements. If the device falls within the class of device types that are supported by the system then specifying an optimal experience for the device can be accomplished with minimal configuration.

Note: The extended UAS is also made available to the media content players client-side JavaScript, through the standard navigator user agent property.

Provided below are tables of the various attributes that can be specified by the specification tokens, as described above, in order to customise the media content, and to specify the media content provision to the user's device: User Interface style The default value for the user interface style is Desktop. User

Attribute Parameter interface Description type

Specifies the TV-style user interface. Best suited for devices with lower screen resolutions and/or devices designed to be Avui ttv TV operated at a distance, such as gaming consoles, set top boxes and IPTV-connected TV sets.

Specifies the mobile-phone style interface.

Best suited for devices with lower-resolution /mob Mobile portrait-style displayed such as mobile phones.

Specifies the browser style user interface.

Best suited for devices with 1024x768 or Idtp Desktop greater screen sizes, such as a regular personal computer.

Specifies that the device is requesting the /cvs Canvas Canvas user interface.

In addition to specifying the User Interface type, this attribute may be used to dictate the server that the media content is served from; for example, content for a television could be served from a different server to that of a desktop personal computer due to the varying requirements for resolution etc. User Interface Rendering Technology The default value for the user interface rendering technology is HTML4.

User interface

Attribute Parameter rendering Description

technology Specifies that the server should return an HTML4-compatible web page. This option IhtmI4 HTML4 is applicable to most standard browsers today.

Specifies that the server should return an HTML5-.compatible web page. For devices avrt that support HTML5, this provides a next- /html5 HTML5 gen browsing experience with integrated video playback, better integration with remote control keys, etc. Specifies that the device does not have a /flash Flash browser, and that the request is being made by a custom Flash application.

Video Playback method The default value for the video playback method is Flash. Video

Attribute Parameter playback Description

method Specifies that video will play back in the Flash player, typically streamed over RTMP. The /flash Flash video will typically be H.264 at our preferred size and bitrate, unless overridden by the Video Lines and/or Max Bitrate options below.

Specifies that, instead of embedded a Flash Windows player in the page, clicking the Play button will Media launch a (DRM protected) WMV or WMA file, /wm p Player served as an HTTP progressive download.

streaming That file will then launch and play back in the avvp device's native video player.

Specifies that an H.264 file will be served over HTTP over SSL, launched and played back in the /ssl SSL device's native video player or, if using streaming HTML5, optionally embedded in the media content player web page.

HTTP

As above, but the file will be served as an /http progressive HTTP progressive download.

down load RTSP As above, but the file will be served as an /rts p streaming RTSP stream.

Note that the /ssl, /http and /rtsp options require that the system implement a robust token or certification authentication system to detect and authenticate the device.

Examples of the use of query strings: http://www.XYZ.co. uklmediacontentplayer/biqscreen?avvp=flash http://www.XYZ.co. uk/mediacontentplayer/biqscreen?avvp=wmp Audio Playback method The default value for the audio playback method is Flash. Audio

Attribute Parameter playback Description

method Specifies that audio will play back in the Flash player, typically streamed over RTMP. The /flash Flash audio will typically be AAC at the preferred size.

Specifies that, instead of embedded a Flash player in the page, clicking the Play button will Windows launch a WMA, served as an HTTP /wmp Media Player progressive download. That file will then avrp streaming launch and play back in the native audio player.

AAC over Specifies that an AAC file will be served over /aac HTTP HTTP, launched and played back in the streaming device's native player.

MP3 over Specifies that an Mp3 file will be served over /mp3 HTTP HTTP, launched and played back in the streaming device's native player.

Examples of the use of query strings: http://www.XYZ.co. uk/med iacontentplayer/biqscreen?avrp=flash http://www.XYZ.co. uk/med iacontentplayer/biciscreen?avrp=aac Maximum number of Video Lines In general the media content system will try to serve up the highest possible video size to provide the best possible video quality. However, if the device is unable to render large video playback sizes, or is unable to dynamically resize video streams that are larger than the available screen size, then the device can request that the media content player cap the size of the video, as follows: No. of Video

Attribute Parameter Description lines

The media content player will display the largest video size available that is smaller cap the than the number of vertical lines that are /<N> video to no specified. avvl

e.g. /400 more than N vertical lines The media content player, for example, is able to provide the following video sizes: 640x360, 832x468, 1280x720 (HD).

If the awl option is not specified then the system can serve up the largest video size that it thinks may fit on the detected screen size, as reported (where applicable) by the browser.

Examples of the use of query strings: http://www.XYZ.co. uk/mediacontentplayer/biqscreen?avvp=wmp&avvl=720 http://www.XYZ.co. uk/med iacontentplayer/bigscreen?avvp=wmp&avvl=360 Max Bitrate In general the media content system may try to serve up the highest possible video bitrate to provide the best possible video quality. However, if the device is unable to render high bitrate video, then the device can request that the bitrate of the video is capped, as follows:

Attribute Parameter Max bitrate Description

The media content system makes use of Adaptive Bitrate techniques, where possible, to serve the best possible video stream that the user's internet connection can support.

However, if the device is unable to support cap the video the decode complexity of high bitrate /<N> to no more avmb. streams then the bitrate can be capped to e.g. /1000 than N kilobits match the device's CPU and GPU per second capabilities.

The media content system, for example, is able to provide the following video sizes: H.264: 480Kbps, 800Kbps, 1 500Kbs, 3200Kbps (HD); WMV: 1000Kbps If the avmb option is not specified then the system may serve up the highest video bitrate that it detects is supportable by any given device's Internet connection.

Examples of the use of query strings: http://www.XYZ.co. uk/med iacontentplayer/biqscreen?avvp=flash&avvl=3200 http://www.XYZ.co. uk/flied iacontentplayer/biqscreen?avvp=flash&avvl= 1500 http://www.XYZ.co. uk/mediacontentplayer/biclscreen?avvD=flash&avvl=800 http://www.XYZ.co. uk/mediacontentplayer/biqscreen?avvp=flash&avvl=500 Playback Video Mode If using a Flash based player (EMP), the media content system may typically provide the user the option of playing the video embedded within the web page, or playing the video in fuliscreen mode. If the device supports only embedded playback, or supports only fullscreen playback, then default behaviour can be overridden as follows: Playback

Attribute Parameter Description

Video mode embedded Only displays the video embedded in the /e only web page.

Always jumps immediately to fuliscreen If fuliscreen only avvm when playback starts.

Use to simulate fullscreen mode on devices Is Scaled mode that do not support fuliscreen flash. Embeds the media player to fill the entire screen.

If the avvm option is not specified then the system can allow the user to choose whether they want to view the video embedded within the web page or in fullscreen mode.

Note that this option is only applicable to Flash or HTML5 playback; for all other playback methods (e.g. Windows Media Player), playback may take place in the device's native video player, which may likely be a fullscreen-only experience.

Examples of the use of query strings: http://www.XYZ.co. uk/med iacontentplayer/bigscreen?avvp=flash&avvm=e http://www.XYZ.co. uk/mediacontentplayer/bigscreen?avvp=flash&avvm=f http://www.XYZ.co.uk/mediacontentplayer/biqscreen?avvp=flash&avvm=s Subtitles Many programmes on the media content system contain optional subtitles. On a PC a user has the choice of showing subtitles via the S' button within the flash player, however this UI may not be appropriate for the device. If the device has user-configurable subtitles, the current setting can be passed to the system using:

Attribute Parameter Subtitles Description

Default behaviour. No subtitles are /off No subtitles displayed unless explicitly enabled via the media content player UI.

avst __________ _____________ _______________________________________ Show subtitles Forces the media content player to show Ion where subtitles (availability depends on both media available and playback type.) If the avst option is not specified then the media content player will not display subtitles.

Key-maps To allow easy navigation using a remote control or keyboard, the media content player interface can respond to various key presses. As different devices may map different remote control keys to different virtual key codes, the user-agent configuration may specify a base key-map and overrides for individual keys: This configuration option takes the form of: avkbl<base>,<key> :<code>,<key> <code>,...

Where:

Attribute Parameter Key-mapping Description

The base key-map defines a default mapping for a number of keys. The following base key-maps are defined: The base key-I<base> Ipc -standard PC cursor keys, and map return/enter.

/mc (deprecated) /mcr -Media Center remote arrow buttons, ok, back and volume/mute.

Specifies which key the following code remaps to. Can be at least one of: L -Left cursor/arrow R -Right cursor/arrow U -Up cursor/arrow avkb D -Down cursor/arrow E -Enter/Select/OK A key to <key> B -Back/Cancel remap P -Play PU-Pause S -Stop VU-Volume Up VD -Volume Down M-Mute SF -Seek Forward/FFWD SB -Seek Back/RWND Specifies the decimal virtual key code which is provided by the <code> Key code event.which/event.keyCode property of keyboard event handlers when this key is pressed.

If the avkb option is not specified then the media content system will not provide any special event handling for key presses.

An example of a valid user-agent header containing a custom key-map (overriding the standard PC key-map by mapping Page Up and Page Down to control volume) is: Operal9.64 (Linux i686; U; sv) (avui/tv; avvp/f lash; avkb/pc,VU:33,VD:34) The system interface requires the user-agent/browser to move focus between navigable active user-interface elements (i.e. anchors and embedded flash objects) when the appropriate key is pressed. The system interface provides hover states for all such elements to inform the user which currently has focus. The browser may also handle the user activating a link (e.g. by pressing OK) in the same manner as a standard browser, i.e.: * If the anchor has no onclick handler, navigate to the URL specified in the HREF attribute.

* If the anchor does have an onclick handler, execute the hander.

* If the handler returns TRUE, navigate to the URL specified in the HREF attribute.

* If the handler returns FALSE, do nothing.

Examples of the use of query strings: http://www.XYZ.co.uk/mediacontentplayer/bigscreen?avkb=pc (enable keymapping) http://www.XYZ.co.uk/mediacontentplayer/bigscreen?avkb=pc,E:32 (remap OK/Select to space key) User Agent string format The user agent string formatting provides for various allowable syntax. The UAS analyser scans the whole string and the values can appear anywhere in the string, in any order, as long as it is in the following format: * SPACE "(" or ";" * Followed by av??/value * Followed by SPACE ")" or Multiple sets of parenthesis may also supported, including the following examples: (avu i/tv avkb/pc) (avui/tv;avkb/pc) (avu i/tv; avkb/pc) (avu i/tv avkb/pc) (avu i/tv) (avkb/pc) Using the Query String Any of the above attributes can also be specified using the query string (for example during testing of a device quickly, thus eliminating the need to alter the UAS).

Specify attributes as key=value pairs, using the normal query string format e.g. http://www.XYZ.co. uklmediacontentplayer/bigscreen?avuitv&avvl400 The system may store these values in a cookie so they are available during all future media content player page requests. All persisted attributes within this cookie may be overwritten if a further request containing one or more attributes in the query string is provided.

Attributes provided by the query string take precendence over those specified in the user-agent string. This allows the manufacturer of the device to test different options/values without altering the user-agent string.

In addition to the above attributes and parameters a unique device name may be included in the UAS -e.g. Operal9.64 (Linux i686; iGizmo) (avuiltv; avvl/400; avvp/flash) where iGizmo is the name of the device.

There are three reasons for including your device name in the UAS: a) it enables tracking of the system traffic by device, b) the system can share traffic statistics with the manufacturer for their device, c) specific rendering tweaks can be provided as needed for the device.

It will be understood that the present invention has been described above purely by way of example, and modifications of detail can be made within the scope of the invention.

Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.

Claims

CLAIMS1. A system for providing media content to a device, comprising: means for receiving data relating to the device; means for analysing the data to determine at least one appropriate attribute for the media content; and means for providing media content having said at least one appropriate attribute to the device.
2. A system according to Claim 1, wherein the means for providing media content is adapted to select, or adjust, media content to provide media content to the device with the required attributes.
3. A system according to Claim 1 or 2, wherein said receiving means is adapted to receive said data from said device.
4. A system according to Claim 3, wherein said data is contained within a digital data string for communicating data other than said data.
5. A system according to Claim 4, wherein said data is appended to the end of the digital data string such that the original data contained with the digital data string is unaffected by the addition of said data.
6. A system according to Claim 4 or 5, wherein the digital data string is a standard variable communicated by said device.
7. A system according to Claim 6, wherein said standard variable is the user agent string relating to said device.
8. A system according to Claim 6 or 7, wherein said standard variable is the Uniform Resource Locator query string.
9. A system according to Claim 8 when dependent on Claim 7, wherein said analysing means is adapted to use data obtained from said query string in priority to the data obtained from said user agent string.
10. A system according to any of the preceding claims, wherein said data relates to media content attributes comprising at least one of; the resolution of the media content, the type of user interface, the user interface rendering protocol, the media playback protocol, and the media playback mode.
11. A system according to Claim 10, wherein said resolution includes at least one of; the number of vertical lines of video content, and the maximum bitrate of the media.
12. A system according to Claim 10 or 11, wherein said type of user interface includes interfaces optimised for television, mobile devices, personal computers, and set-top boxes.
13. A system according to Claim 10, 11 or 12, wherein said user interface rendering protocol includes HTML4, HTML5, and Flash.
14. A system according to any of Claims 10 to 13, wherein said media playback protocol includes the video playback protocol and the audio playback protocol.
15. A system according to Claim 14, wherein said video playback protocol includes Flash, Windows Media Player streaming, HTTP over SSL streaming, HTTP progressive download, and RTSP streaming.
16. A system according to Claim 14 or 15, wherein said audio playback protocol includes Flash, Windows media player streaming, AAC over HTTP streaming, and MP3 over HTTP streaming.
17. A system according to any of the preceding claims, further comprising means for storing default values for each said attribute.
18. A system according to Claim 17, wherein said media content is provided in dependence on said default values when an attribute is not specified in said data received from said device.
19. A system according to any of the preceding claims, further comprising means for providing additional media content in dependence on said data.
20. A system according to Claim 19, wherein said additional media content is subtitles.
21. A system according to any of the preceding claims, further comprising means for receiving input commands from said device.
22. A system according to Claim 21, further comprising means for analysing said input commands in dependence on said analysis of said data, and means for actioning said input commands in dependence on said analysis of said commands.
23. A system according to Claim 22, wherein said commands are received via an input device in connection with said device.
24. A system for providing media content to a device, comprising: means for providing media content to the device; means for receiving data relating to the device input means; means for analysing the data; means for receiving input commands from the input means via the device; and means for actioning the input commands in dependence on the analysis of the data.
25. A system according to any of Claims 21 to 24, wherein said data includes key-mapping information to map the commands from said input device to actions relating to the provision of said media content.
26. A system according to Claim 25, wherein said key-mapping data relates to at least one command.
27. A system according to Claim 25 or 26, wherein said key-mapping data relates to a group of commands.
28. A system according to Claim 25, 26 or 27, further comprising means for storing default key-mapping information.
29. A system according to Claim 28, wherein said default key-mapping information is utilised when no key-mapping information is provided within said data.
30. A system according to any of the preceding claims, further comprising means for uploading said media content to said device.
31. A system according to any of the preceding claims, further comprising means for streaming said media content to said device.
32. A system according to Claim 30 or 31, when dependent upon any of Claims 21 to 29 wherein said streaming and/or uploading is initiated by said command.
33. A device for playing media content, comprising: means for storing a digital data string; means for communicating the digital data string to a media content provider; and means for receiving media content having attributes in dependence on the digital data string, wherein the digital data string contains information relating to thedevice specifications.
34. A method of providing media content to a device, comprising: receiving data relating to the device; analysing the data to determine at least one appropriate attribute for the media content; and providing media content having said at least one appropriate attribute to the device.
35. A method of providing media content to a device, comprising: providing media content to the device; receiving data relating to the device input means; analysing the data; receiving input commands from the input means via the device; and actioning the input commands in dependence on the analysis of the data.
36. A method of playing media content, comprising: storing a digital data string; communicating the digital data string to a media content provider; and receiving media content having at least one attribute in dependence on the digital data string, wherein the digital data string contains information relating to thedevice specifications.
37. A system for providing media content as substantiafly herein described with reference to Figures 1 and 2 or Figure 3.
38. A method for providing media content as substantially herein described with reference to Figures 1 and 2 or Figure 3.