Search

ISO/IEC 29341-27-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type referred to herein as FriendlyInfoUpdate service . It is scoped to the Device Description Document (DDD) and is a service allowing control points to create orderly updates to the <friendlyName> and <iconList> elements. Once a change has taken place the status of the DDD might…

ISO/IEC 29341-28-2:2017 defines a device type referred to as ScreenDevice version 1. This device specification is compliant with UPnP Device Architecture 1.0 [1]. The ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-…

ISO/IEC 29341-26-1:2017 describes an architecture that allows UPnP Telephony devices, services and control points defined in the propoded DCP to be deployed in the home network environment and to enable management of incoming and outgoing telephony calls, messaging, presence information and phone features configuration through UPnP means from devices within the home. In order to accommodate the…

ISO/IEC 29341-26-2:2017 defines a device type named TelephonyClient, that complies with [1]. The TelephonyClient device is a UPnP device that allows control points to exploit a set of telephony features such as management of media session with a telephony server, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the…

ISO/IEC 29341-28-2:2017 defines a device type referred to as ScreenDevice version 1. This device specification is compliant with UPnP Device Architecture 1.0 [1]. The ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-…

ISO/IEC 29341-20-1:2017 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/…

ISO/IEC 29341-26-3:2017 defines a device type named TelephonyServer that complies with [1]. The TelephonyServer device is a UPnP device that allows control points to exploit a set of telephony features such as managing telephony calls, messaging, presence etc via UPnP though other UPnP enabled home network devices. This device provides control points with the following functionality…

ISO/IEC 29341-29-2:2017 defines a device type referred to as ScreenDevice version 2. This device specification is compliant with UPnP Device Architecture 1.0 [1]. ScreenDevice provides various interactive services with other display device(s) which is (are) implemented with Screen Control Point(s). It is designed to be controlled by and interact with Screen Control Point(s). See the Multi-Screen…

Today multi-screen/second-screen solutions are proliferating. However, each is a proprietary vertical for particular vendor(s). Therefore users expectations aren't being met: - Seamless interoperability across vendors. - Ability for second screen integrated usages rather than 100s of different apps. The UPnP Multi-Screen Device Control Protocols (DCPs) provide an open…

ISO/IEC 29341-26-10:2017 is compliant with [1]. It defines a service type referred to herein as the CallManagement service. The CallManagement service is a UPnP service that allows control points to use the telephony features(e.g., voice call, video call, and data transfer etc.) provided by a Telephony Server (TS). The CallManagement service enables the following features to a Telephony Control…