Information technology - UPnP Device Architecture - Part 27-1: Friendly device control protocol - Fr...
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…
Information technology — UPnP Device Architecture — Part 26-12: Telephony device control protocol — ...
ISO/IEC 29341-26-12:2017 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 phone, VoIP…
Information technology — UPnP Device Architecture — Part 26-15: Telephony device control protocol — ...
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…
Information technology — UPnP Device Architecture — Part 26-16: Telephony device control protocol — ...
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…
Information technology — UPnP Device Architecture — Part 27-1: Friendly device control protocol — Fr...
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…
Information technology — UPnP Device Architecture — Part 28-2: Multiscreen device control protocol —...
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-…
Information technology — UPnP Device Architecture — Part 26-3: Telephony device control protocol — L...
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…
Information technology — UPnP Device Architecture — Part 26-11: Telephony device control protocol — ...
ISO/IEC 29341-26-11:2017 is compliant with [1]. It defines a service type referred to herein as the MediaManagement service.
The MediaManagement service enables the feature to set-up a media session on a Telephony Client (TC), under the control of a Telephony Control Point (TelCP). This service provides the following functions:
- Set up a media session to send and/or receive media…
Information technology — UPnP Device Architecture — Part 26-13: Telephony device control protocol — ...
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…
Information technology — UPnP Device Architecture — Part 26-14: Telephony device control protocol — ...
ISO/IEC 29341-26-14:2017 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…