Search

1 Scope This service definition is compliant with [1]. It defines a service type referred to herein as Messaging service. The Messaging service is a UPnP service that allows control points to use the messaging features provided by a Telephony Server (TS) or a Telephony Client (TC). It provides in the UPnP network the overall set of messaging capabilities of a phone (e.g., smartphone, IP…

1 Scope This document 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…

1 Scope This service definition is compliant [1]. It defines a service type referred to herein as AddressBook. This service provides the following functionalities: ? Managing the network address book: accessing the network address book, adding new contact information in the network address book, synchronizing the local address book of Telephony Server with the network address book etc. ?…

1 Scope This service definition 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 calendar. ?…

1 Scope This service definition 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…

1 Scope This service definition 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…

1 Scope 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 interface to…

1 Scope This document 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-…

1 Scope This document 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-…

1 Scope 1.1 Introduction This document describes the overall UPnP IoTManagementAndControl Architecture, which forms the foundation for the UPnP IoTManagementAndControl device [11] and UPnP DataStore service [13] specifications. The IoTManagementAndControl device hosts services to bridge sensor devices connected to both UPnP networks as well as non-UPnP based networks. The DataStore service…