🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS ISO/IEC 29341-20-2:2017

BS ISO/IEC 29341-20-2:2017

$167.15

Information technology. UPnP Device Architecture – Audio video device control protocol. Level. Media renderer device

Published By Publication Date Number of Pages
BSI 2017 38
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

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 1MediaRenderer 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.

PDF Catalog

PDF Pages PDF Title
2 National foreword
7 Foreword
14 1 Scope
2 Normative references
17 3 Terms, definitions, symbols and abbreviations
3.1 Provisioning terms
18 3.2 Symbols
4 Notations and Conventions
4.1 Notation
4.1.1 Data Types
19 4.1.2 Strings Embedded in Other Strings
4.1.3 Extended Backus-Naur Form
4.1.3.1 Typographic conventions for EBNF
4.2 Derived Data Types
4.2.1 Summary
20 4.2.2 CSV Lists
21 4.3 Management of XML Namespaces in Standardized DCPs
25 4.3.1 Namespace Prefix Requirements
26 4.3.2 Namespace Names, Namespace Versioning and Schema Versioning
28 4.3.3 Namespace Usage Examples
4.4 Vendor-defined Extensions
4.4.1 Vendor-defined Action Names
4.4.2 Vendor-defined State Variable Names
29 4.4.3 Vendor-defined XML Elements and attributes
4.4.4 Vendor-defined Property Names
5 Device Definitions
5.1 Device Type
5.2 Device Model
30 5.2.1 Description of Device Requirements
5.2.2 Relationships Between Services
6 XML Device Description
32 7 Test
33 A.1 Device Discovery
A.2 Preparing to Transfer the Content
A.3 Controlling the Transfer of the Content
34 A.4 Controlling How the Content is Rendered

Related products

BS ISO/IEC 29341-20-2:2017
$167.15