Internet of Things (IoT) — Requirements of IoT data exchange platform for various IoT services
This document specifies requirements for an Internet of Things (IoT) data exchange platform
This document specifies requirements for an Internet of Things (IoT) data exchange platform
The objective of this Recommendation is to analyse identifiers in existing technologies and networks for IoT service, and describe the requirements of IoT identifier, common characteristics of IoT identifier, and the general architecture of IoT identifier.
This part of standard specifies the IoT interoperability from a syntactic point of view. In ISO/IEC 21823-1: Framework [2], five facets are described for IoT interoperability, i.e. transport, semantic, syntactic, behavioural and policy. In this document, the following specifications for IoT interoperability from a syntactic viewpoint are included;
This document provides the basic concepts for IoT systems semantic interoperability, as
This document presents a conceptual model for network connection interoperability and requirements for interoperable IoT systems to enable information exchange, peer-to-peer connectivity and seamless communication both between different IoT systems and also between entities within an IoT system.
This part of standards presents an overview of interoperable IoT systems and framework for
This document specifies the system framework, IoT application model and overall technical requirements for ELS.
The present document addresses the requirements for communications between the authorized representatives who can be involved in the responses and actions when handling an emergency. It describes the functional requirements for communications between the authorized representatives involved in the responses and actions when handling an emergency. The level of precision has been chosen to avoid interaction with the specific local, regional or national organizations and diagrams of relations between authorized representatives. It follows from this that adaptations will have to be done when implementing the present document at a local level. Furthermore, the scope of the present document also encompasses various types of services that can bring an added value to this basic scenario or add new scenarios, such as the services brought by other technologies e.g. IoT devices that support communications between authorities during emergencies.
The Pan-European Mobile Emergency Application (PEMEA) architecture provides the requirements and architecture for a solution to provide emergency application interconnection. It specifies the protocols and procedures enabling interoperable implementations of the architecture and provides extension points to enable new communication mechanisms as they evolve.
A common framework for sensor performance specification terminology, units, conditions, and limits is provided. Specifically, the accelerometer, magnetometer, gyrometer/ gyroscope, accelerometer/magnetometer/gyroscope combination sensors, barometer/pressure sensors, hygrometer/humidity sensors, temperature sensors, light sensors (ambient and RGB), and proximity sensors are discussed.
The document describes the frame format for transmission of IPv6 packets and the method of forming IPv6 link-local addresses and statelessly autoconfigured addresses on IEEE 802.15.4 networks. Additional specifications include a simple header compression scheme using shared context and provisions for packet delivery in IEEE 802.15.4 meshes.
The document defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular it defines objects for managing IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) [RFC4944].