Information technology - UPnP Device Architecture - Part 30-1: IoT management and control device control protocol - IoT management and control architecture overview

Designation Number:
CSA ISO/IEC 29341-30-1:19
Standard Type:
National Standard of Canada - Adoption of International Standard
Standard Development Activity:
Reaffirmation
ICS code(s):
25.300
Status:
Proceeding to development
SDO Comment Period Start Date:
SDO Comment Period End Date:
Posted On:

Scope:

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 provides persistent retention and distribution of both sensor data as well as data from mobile devices which may leave the UPnP network at any time. This service can be hosted within the UPnP IoTManagementAndControl device as well as within other UPnP compliant devices.

1.2 Goals

The UPnP IoTManagementAndControl Architecture was explicitly defined to meet the following goals:

- Describe sensors and actuators residing on both UPnP and non-UPnP networks.
- Provide data transport services for sensors and actuators to UPnP network clients.
- Define a service to describe, retain and distribute data received from sensors as well as other non-persistent data sources.
- Define an allowed device protection model for both the sensor and data retention components.

1.3 Non-Goals

The following are not initial goals of the IoTManagementAndControl architecture:

- Low-level control of bridged networks
 

The initial version of UPnP IoTManagementAndControl treats Sensors and Actuators as abstract data sources and sinks and does not expose details or provide direct access to bridging network protocols. Low-level control of selected bridged network protocols will be considered in subsequent versions of the architecture.

Low-latency control of sensors and actuators

The initial version of UPnP IoTManagementAndControl treats sensors and actuators as autonomous objects requiring relatively infrequent supervision from home-network clients. Closed loop control of sensor and actuator pairs is better accomplished directly within the internal vendor-device sensor/actuator architecture with UPnP home-network clients providing overall supervision. However, UPnP IoTManagementAndControl does support sensors which have substantial throughput requirements using transport connections.

Project need:

Project Need
To review the Standard within the required 5 year period.

Note: The information provided above was obtained by the Standards Council of Canada (SCC) and is provided as part of a centralized, transparent notification system for new standards development. The system allows SCC-accredited Standards Development Organizations (SDOs), and members of the public, to be informed of new work in Canadian standards development, and allows SCC-accredited SDOs to identify and resolve potential duplication of standards and effort.

Individual SDOs are responsible for the content and accuracy of the information presented here. The text is presented in the language in which it was provided to SCC.