Search

Refine Results
International Classification for Standards (ICS) code
Source
Standards Development Organization (SDO) code
Language
Status
National Standards of Canada (NSC) code
Period range

From

To

Displaying 5191 - 5200 of 16934
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…
Publisher :
IEC
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology - UPnP Device Architecture - Part 28-1: Multiscreen device control protocol -...
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…
Publisher :
IEC
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology — UPnP Device Architecture — Part 31-1: Energy management device control prot...
ISO/IEC 29341-31-1:2017 is compliant with the UPnP Device Architecture version 1.0. It defines a service type named EnergyManagement service. It is scoped to any UPnP Device that needs to convey energy management functionality available for the UPnP Device and its services.
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology — UPnP Device Architecture — Part 20-1: Audio video device control protocol —...
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/…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology — UPnP Device Architecture — Part 20-4: Audio video device control protocol —...
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…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology — UPnP Device Architecture — Part 20-13: Audio video device control protocol ...
ISO/IEC 29341-20-13:2017 is compliant with the UPnP Device Architecture version 1.0 [14]. It defines a service type referred to herein as RenderingControl.
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
Information technology — UPnP Device Architecture — Part 20-2: Audio video device control protocol —...
ISO/IEC 29341-20-2:2017 is compliant with the Universal Plug and Play Device Architecture version 1.0 [14]. It defines a device type referred to herein as MediaRenderer. The MediaRenderer specification defines a general-purpose device template that can be used to instantiate any Consumer Electronics (CE) device that is capable of rendering AV content from the home network. It exposes a set of…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
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…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
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…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200
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…
Publisher :
ISO
Status :
Published
Published Date :
2017-09-12
ICS Code(s) :
35.200