Rechercher

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…

1 Scope This document defines the device for IOT Management and Control, which identifies Level 1 of the device named IOT Management and Control. This Publicly Available Specification is applicable to Standardized DCPs of the UPnP Forum which include this device. This device definition is compliant with the UPnP Device Architecture version 1.0 [1]. It defines a device type referred to herein…

1 Scope 1.1 Introduction This document defines the service DataStore:1, which identifies Version 1 of the service named DataStore. This Publicly Available Specification is applicable to Standardized DCPs of the UPnP Forum which include this service. This service definition is compliant with the UPnP Device Architecture, version 1.0.

1 Scope This part of Publicly Available Specification ISO/IEC 29341 specifies the characteristics of a networked service that offers sensor and/or actuator data transport capabilities to an independent networked entity known as a control point. This document defines the service SensorTransportGeneric:1 (in short TransportGeneric), which identifies Level 1 of the UPnP IoT Management and…

1 Scope This specification 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.

1 Scope This document defines single-point gestures for common system actions used in information and communication technology (ICT) systems. It specifies movements for clear and classified gestures recognized by the systems and applications. The single-point gestures are performed using an input device (e.g. a mouse, a stylus, etc.) or a body part (e.g. a fingertip, a hand, etc.). These single-…

1 Scope This International Standard describes, and gives guidance on, a smart city concept model (SCCM) that can provide the basis of interoperability between component systems of a smart city, by aligning the ontologies in use across different sectors. It includes: • concepts (e.g. ORGANIZATION, PLACE, COMMUNITY, ITEM, METRIC, SERVICE, RESOURCE); and • relationships between concepts (e.g.…