Information technology - UPnP Device Architecture - Part 20-2: Audio video device control protocol - Level 4 - Media renderer device
Introduction: ISO and IEC draw attention to the fact that it is claimed that compliance with this document may involve the use of patents as indicated below. ISO and IEC take no position concerning the evidence, validity and scope of these patent rights. The holders of -these patent rights have assured ISO and IEC that they are willing to negotiate licenses under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statements of the holders of these patent rights are registered with ISO and IEC. Intel Corporation has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Intel Corporation Standards Licensing Department 5200 NE Elam Young Parkway MS: JFS-98 USA – Hillsboro, Oregon 97124 Microsoft Corporation has informed IEC and ISO that it has patent applications or granted patents as listed below: 6101499 / US; 6687755 / US; 6910068 / US; 7130895 / US; 6725281 / US; 7089307 / US; 7069312 / US; 10/783 524 /US Information may be obtained from: Microsoft Corporation One Microsoft Way USA – Redmond WA 98052 Philips International B.V. has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: Philips International B.V. – IP&S High Tech campus, building 44 3A21 NL – 5656 Eindhoven NXP B.V. (NL) has informed IEC and ISO that it has patent applications or granted patents. Information may be obtained from: NXP B.V. (NL) High Tech campu
Scope: This device specification is compliant with the Universal Plug and Play Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaRenderer. The MediaRenderer specification defines a general-purpose device template that can be used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. It exposes a set of rendering controls in which a control point can control how the specified AV content is rendered. This includes controlling various rendering features such as brightness, contrast, volume, etc. Example instances of a MediaRenderer include traditional devices such as TVs and stereo systems. Some more contemporary examples include digital devices such as MP3 players and Electronic Picture Frames (EPFs). Although most of these examples typically render one specific type of content (for example, a TV typically renders video content), a MediaRenderer is able to support a number of different data formats and transfer protocols. For example, a sophisticated implementation of a TV MediaRenderer could also support MP3 data so that its speakers could be used to play MP3 audio content. The MediaRenderer device specification is very lightweight and is easy to implement on low- resource devices such as an MP3 player. However, it can also be used to expose the high- end capabilities of devices such as a PC. A full-featured MediaRenderer exposes the following capabilities: Control various rendering characteristics Expose the supported transfer protocols and data formats Control the flow of the content (for example, FF, REW, etc), if appropriate depending on the transfer protocol. The MediaRenderer DOES not enable control points to: Send AV content to another device Figure 1 — MediaRenderer Functional Diagram The un-shaded blocks represent the UPnP services that are contained by a MediaRenderer. The shaded blocks represent various device-specific modules that the UPnP services might interact with. However, the internal architecture of a MediaRenderer device is vendor specific.
Contents: