IoT Internet of Things

The scope of the present document is to provide an overview of the IoT standards landscape: requirements, architecture, protocols, tests, etc. to provide the roadmaps of the IoT standards, when they are available

Recommendation ITU-T X.1364 analyses potential deployment schemes and typical application scenarios for narrowband Internet of things (NB-IoT). It specifies security threats and requirements specific to the NB-IoT deployments and establishes a security framework for the operator to safeguard new NB-IoT technology applications. Current developments in telecommunication technology in the mobile communication domain, are leading to changes in communication patterns from person-to-person to person-to-thing and thing-to-thing, making inevitable the evolution to the Internet of things. Compared to short distance communication technologies such as Bluetooth, ZigBee and others, cellular mobile networks characterized by wide coverage, mobility and extensive connections that bring richer application scenarios will become the main interconnection technology of IoT. NB-IoT is based on cellular mobile network technology, using a bandwidth of approximately only 180 KHz. It may be deployed on global system for mobile communication (GSM) networks, universal mobile telecommunications system (UMTS) networks or long-term evolution (LTE) networks directly to reduce costs and achieve a smooth upgrade. Based on its low power dissipation, wide coverage, low cost and high capacity, NB-IoT is expected to be massively adopted by operators with wide application in multiple vertical industries. As a new technology, NB-IoT has its own characteristics that may bring new security issues. In order to ensure security of NB-IoT deployments and applications, security threats and relevant security requirements specific to NB-IoT need to be analysed and an overall security framework for NB-IoT needs to be established.

This recommendation provides an overview of the Internet of things (IoT). It clarifies the concept and scope of the IoT, identifies the fundamental characteristics and high-level requirements of the IoT and describes the IoT reference model. The ecosystem and business models are also provided in an informative appendix.

This European Standard gives general guidelines and recommendations to ensure interworking between HBES devices made by different manufacturers. It also contains design guidelines for the design of Functional Blocks and new datapoint types, the building blocks of HBES interworking. In this way, the standard can be used as a basis to design application specifications relative to an Application Domain. If designed and supported by a large group of manufacturers, such application specifications will ensure to end customers a high degree of interoperability between products based on the HBES Communication System of different manufacturers. This European Standard is used as a product family standard. It is not intended to be used as a stand alone standard.

This international standard establishes general principles for network- and device-management shared by and independent of the installation mode. The goal is to standardize the interaction, between a management client and a management server, that shall lead to the successful configuration of the devices. In this way, these management procedures thus specify the highest level communication requirements between a management client and a management server. These requirements specify: a) the sequence of messages that shall be exchanged between a management client and a management server, and b) the contents and interpretation of the transported data, and c) the action to take based on these data (setting internal resources, state machines, physical actions, …), and d) the error and exception handling. The management procedures base on the application layer services. Some management procedures solely base on the use of one or a sequence of dedicated application layer services to achieve the required goal. For these, the documents EN 50090-4-1 and EN 50090-4-2 provide sufficient information for the underlying mechanisms. Other management procedures additionally use the application layer services to access internal data in the management server to achieve the required goal. These data are laid down as objects as specified in EN 50090 3 2.

This European Standard concentrates on control applications for Home and Building HBES Open Communication System and covers any combination of electronic devices linked via a digital transmission network. Home and Building Electronic System as provided by the HBES Open Communication System is a specialized form of automated, decentralised and distributed process control, dedicated to the needs of home and building applications. The EN 50090 series concentrates on HBES Open Communication System Class 1 and includes a specification for a communication network for Home and Building for example for the control of lighting, heating, food preparation, washing, energy management, water control, fire alarms, blinds control, different forms of security control, etc. This European Standard gives an overview of the features of the HBES Open Communication System and provides the reader with references to the different parts of EN 50090 series. This European Standard is used as a product family standard. It is not intended to be used as a stand-alone standard.

The present document would undertake compilation and review of activities taking place in the area of Smart City. It will analyse the relevance of Smart City applications, and possible underlying network architecture. The present document will describe use case descriptions for Smart City applications in context of but not limited to IoT communications.

The Computational Storage TWG was created for the purpose of establishing architectures and software for storage, disk, and solid state device based functionalities that allow them to be integrated with Computation in its many forms. This TWG creates software and standards that enable specific features for these devices that meet the requirements of stakeholders with these computational needs.