Menu
0
Total price
0 €
PRICES include / exclude VAT
Homepage>BS ISO/IEC 29341-20-3:2017 Information technology. UPnP Device Architecture Audio video device control protocol. Level 4. Media server device
Sponsored link
sklademVydáno: 2017-09-22
BS ISO/IEC 29341-20-3:2017 Information technology. UPnP Device Architecture Audio video device control protocol. Level 4. Media server device

BS ISO/IEC 29341-20-3:2017

Information technology. UPnP Device Architecture Audio video device control protocol. Level 4. Media server device

Format
Availability
Price and currency
Anglicky Secure PDF
Immediate download
309.84 €
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
30.98 €
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
92.95 €
Anglicky Hardcopy
In stock
309.84 €
Označení normy:BS ISO/IEC 29341-20-3:2017
Počet stran:38
Vydáno:2017-09-22
ISBN:978 0 580 90850 7
Status:Standard
DESCRIPTION

BS ISO/IEC 29341-20-3:2017


This standard BS ISO/IEC 29341-20-3:2017 Information technology. UPnP Device Architecture is classified in these ICS categories:
  • 35.200 Interface and interconnection equipment

This device specification is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaServer.

The MediaServer specification defines a general-purpose device that can be used to instantiate any Consumer Electronics (CE) device that provides AV content (for example, media) to other UPnP devices on the home network. It is based on the UPnP AV Architecture Framework (described in another document). It exposes its content via the ContentDirectory service (refer to the ContentDirectory service specification for details). The MediaServer may also provide functionality to record content using the ScheduledRecording service (refer to the ScheduledRecording service specification). As such, the MediaServer can handle any specific type of media, any data format, and transfer protocol.

Example instances of a MediaServer include traditional devices such as VCRs, CD Players, DVD Players, audio-tape players, still-image cameras, camcorders, radios, TV Tuners, and set-top boxes. Additional examples of a MediaServer also include new digital devices such as MP3 servers, PVRs, smartphones and Home MediaServers such as the PC. Although these devices contain diverse (AV) content in one form or another, the MediaServer (via the ContentDirectory service) is able to expose this content to the home network in a uniform and consistent manner. This ability allows the MediaServer to instantiate traditional single-function devices as well as more recent multi-function devices such as VCR-DVD players and the general purpose Home MediaServer, which contains a wide variety of content such as MPEG2 video, CD audio, MP3 and/or WMA audio, JPEG images, etc.

The MediaServer specification is very lightweight and can easily be implemented on low-resource devices such as still-image cameras or MP3 players that want to expose their local content to the home network. The MediaServer can also be used for high-end Home MediaServers that contain dozens of Gigabytes of heterogeneous content. Refer to the Theory Of Operation subclause for some specific examples of the MediaServer.

A full-featured MediaServer device provides clients with the following capabilities:

  • Enumerate and query any of the content that the MediaServer can provide to the home network.

  • Negotiate a common transfer protocol and data format between the MediaServer and target device.

  • Control the flow of the content (for example, FF, REW, etc).

  • Copy (import) content to the MediaServer from another device.

  • Record content using the ScheduledRecording service [25].

This device specification does not provide:

  • The ability to render AV content.

Figure 1 MediaServer Functional Diagram

image

The un-shaded blocks represent the UPnP services that are contained by a MediaServer device. The shaded blocks represent various device-specific modules that the UPnP services might interact with. However, the internal architec tur e of a MediaServer devic e is vendor specific.