Information technology - UPnP Device Architecture Part 20-3: Audio video device control protocol - Level 4 - Media server 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 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 c
Contents: