🔥🔥 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-1:2017

BS ISO/IEC 29341-20-1:2017

$167.15

Information technology. UPnP Device Architecture – Audio video device control protocol. Level 4. Audio video architecture

Published By Publication Date Number of Pages
BSI 2017 42
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]

1.1 Introductioin

This document describes the overall UPnP AV Architecture, which forms the foundation for the UPnP AV Device and Service templates. The AV Architecture defines the general interaction between UPnP control points and UPnP AV devices. It is independent of any particular device type, content format, and transfer protocol. It supports a variety of devices such as TVs, VCRs, CD/DVD players/jukeboxes, settop boxes, stereos systems, MP3 players, still-image cameras, camcorders, electronic picture frames (EPFs), and the PC. The AV Architecture allows devices to support different types of formats for the entertainment content (such as MPEG2, MPEG4, JPEG, MP3, Windows Media Architecture (WMA), bitmaps (BMP), NTSC, PAL, ATSC, etc.) and multiple types of transfer protocols (such as IEC‑61883/IEEE‑1394, HTTP GET, RTP, HTTP PUT/POST, TCP/IP, etc.). The following clauses describe the AV Architecture and how the various UPnP AV devices and services work together to enable various end-user scenarios.

1.2 Goals

The UPnP AV Architecture was explicitly defined to meet the following goals:

  • To support arbitrary transfer protocols and content formats.

  • To enable the AV content to flow directly between devices without any intervention from the control point.

  • To enable control points to remain independent of any particular transfer protocol and content format. This allows control points to transparently support new protocols and formats.

  • Scalability, i.e. support of devices with very low resources, especially memory and processing power as well as full-featured devices.

  • Synchronized playback to multiple rendering devices.

  • Access Control, Content Protection, and Digital Rights Management.

1.3 Non-Goals

The UPnP AV Architecture does not enable any of the following:

  • Two-way Interactive Communication, such as audio and video conferencing, Internet gaming, etc.

PDF Catalog

PDF Pages PDF Title
2 National foreword
14 1 Scope
1.1 Introductioin
1.2 Goals
1.3 Non-Goals
2 Normative references
15 3 Terms, definitions, symbols and abbreviations
16 4 Architectural Overview
18 5 Playback Architecture
19 5.1 MediaServer
20 5.1.1 ContentDirectory Service
5.1.2 ConnectionManager Service
5.1.1 AVTransport Service
5.2 MediaRenderer
21 5.2.1 RenderingControl Service
5.2.2 ConnectionManager Service
5.2.3 AVTransport Service
5.3 Control point
24 5.3.1 2-Box model: Control point with Decoder
25 5.3.2 2-Box model: Control point with Content
5.4 Tracking streams in the network
6 Example Playback Scenarios
26 6.1 3-Box model: Isochronous-Push (IEC61883/IEEE1394)
27 6.2 3-Box model: Asynchronous-Pull (e.g. HTTP GET)
28 6.3 2-Box model: Control point with Decoder using Isochronous-Push (e.g. IEEE-1394)
30 6.4 2-Box model: Control point with Decoder using Asynchronous-Pull (e.g. HTTP GET)
6.4.1 Minimal Implementation
32 6.5 2-Box model: Control point with Content using Isochronous-Push (e.g. IEEE-1394)
33 6.6 2-Box Model: Control point with Content using Asynchronous-Pull (e.g. HTTP GET)
6.7 No ConnectionManager::PrepareForConnection() Action
34 7 Advanced Playback Scenarios
35 7.1 Synchronized playback
37 7.2 Multi-streaming
39 8 Recording Architecture
8.1 Legacy recording mechanism
8.2 Scheduled Recording

Related products

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