CSA Preface
Standards development within the Information Technology sector is harmonized with international standards development. Through the CSA Technical Committee on Information Technology (TCIT), Canadians serve as the SCC Mirror Committee (SMC) on ISO/IEC Joint Technical Committee 1 on Information Technology (ISO/IEC JTC1) for the Standards Council of Canada (SCC), the ISO member body for Canada and sponsor of the Canadian National Committee of the IEC. Also, as a member of the International Telecommunication Union (ITU), Canada participates in the International Telegraph and Telephone Consultative Committee (ITU-T).
For brevity, this Standard will be referred to as “CSA ISO/IEC 29341-30-1” throughout.
At the time of publication, ISO/IEC 29341-30-1:2017 is available from ISO and IEC in English only. CSA Group will publish the French version when it becomes available from ISO and IEC.
The International Standard was reviewed by the CSA TCIT under the jurisdiction of the CSA Strategic Steering Committee on Information and Communications Technology and deemed acceptable for use in Canada. From time to time, ISO/IEC may publish addenda, corrigenda, etc. The TCIT will review these documents for approval and publication. For a listing, refer to the Current Standards Activities page at standardsactivities.csagroup.org. This Standard has been formally approved, without modification, by the Technical Committee and has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group.
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.
