Rechercher

ISO/IEC 29341-26-13:2017 specifies the PhoneManagement profile of the ConfigurationManagement Service defined in [7]. The PhoneManagement profile can be used for managing the configuration of the UPnP TelephonyServer device (i.e. a telephone), with tasks such as managing an address book, configuring the settings of the phone, configuring the ringing modes, checking the battery level of the phone…

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

ISO/IEC 29341-20-4:2017 defines the layout of the AV Datastructure Template (AVDT) XML document. An AVDT document describes the format requirements and restrictions of various data structures used within the UPnP AV specifications. Although these data structures are defined very precisely in the appropriate service specification, in most cases, each data structure definition allows for a certain…

ISO/IEC 29341-24-1:2017 specifies the characteristics of a device that manages connectivity to the Internet as an "edge" device between a residential Local Area Network and a Wide Area Network. The gateway can be physically implemented as a standalone device, or logically as a set of UPnP devices and services on a PC. This specified device is intended to be controlled from inside the…

ISO/IEC 29341-26-15:2017 is compliant with [1]. It defines a service type referred to herein as Calendar. This service provides the following functionalities: - Manage the family calendar events and share calendar events between the family members. - Calendar events includes Reminders/Alarms/Free-BusyTime. - Synchronizing the local calendar events with family…

ISO/IEC 29341-26-16:2017 is compliant with the [1]. It defines a service type referred to herein as Presence service. The Presence service is a UPnP service that allows control points, or better known as Telephony Control Points (TelCP), to manage presence information through a Telephony Server (TS) device or a Telephony Client (TC) device (in the role of UPnP server device for Presence service…

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-24-10:2017 specifies the characteristics of the UPnP networked service named WANIPConnection, version 2. This service definition is compliant with UPnP Device Architecture 1.0 [1] . It is one component of the Device Control Protocol for the UPnP Internet Gateway Device (see [3]). This service enables a UPnP control point to: - configure and control an IP connection…

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-24-11:2017 specifies the characteristics of the UPnP networked service named WANIPv6FirewallControl, version 1. This service definition is compliant with UPnP Service Architecture 1.0 [1]. This service supports the management IPv6 firewall pinholes in Internet gateway devices independent of the WAN access type (PPP, DHCP, ?). It also supports access control to restrict operations…