IoT

To define an ISO/OSI application layer for communication systems for and remote reading of all meters within the scope of TC 294 to fullfill the user requirements as defined by WG 1 (as one part of the standards). To define and maintain a glossary of terms (as one part of the standards).

Prepare a standard for the lower layers for uni and bi-directional meters data exchange by radio frequency communication. (see resolutions 2& 3/1999).

Produce and maintain standards for meter data exchange protocols, for use over short range wireless networks with meshing functionality. Note: Work will be based on existing ZigBee specifications.

IoT devices represent a wide variety of non-traditional devices that are increasingly implemented in organizations due to the numerous benefits. These unique devices often pose a security challenge due to the limited size and lack of innate security making them difficult to secure with traditional security controls and methodologies. It is a combination of these factors that has rendered many devices vulnerable to attacks like the Mirai botnet. The IoT Working Group's mission is dedicated to understanding relevant use cases for IoT deployments and defining actionable guidance for security practitioners to secure their IoT ecosystem. This includes outlining best practices for securing IoT implementations, identifying gaps in standards coverage for IoT security, and identifying threats to IoT devices and implementations.

Cloud Customer Architecture for IoT is a reference architecture for supporting the Internet of Things (IoT) using cloud computing.
 
IoT is one of the most exciting and most dynamic areas of IT at the present time. IoT involves the linking of physical entities (“things”) with IT systems that derive information about or from those things which can be used to drive a wide variety of applications and services.
 
The cloud components of the IoT reference architecture are positioned within a three-tier architecture pattern comprising edge, platform, and enterprise tiers. The cloud components, subcomponents, and relationships are discussed in detail. Considerations are discussed for meeting scale, safety, reliability, and privacy requirements.

This CWA addresses a broad set of Principles and Guidance to form a solid foundation for future practice with regard to SEP licensing for ICT standards such as mobile communication standards and other wireless communication standards. The CWA also includes information about licensing to those who are new to the implementation and use of standardised technology and the licensing of patents that cover those technologies.

The present document defines security solutions applicable within the M2M system.

The present document specifies the binding of Mca and Mcc primitives onto the WebSocket binding. It specifies:

• Procedures and message formats for operating and closing of WebSocket connections.

• How request and response primitives are mapped into the payload of the WebSocket protocol.

The purpose of oBIX (open Building Information Exchange) is to enable the mechanical and electrical control systems in buildings to communicate with enterprise applications, and to provide a platform for developing new classes of applications that integrate control systems with other enterprise functions. Enterprise functions include processes such as Human Resources, Finance, Customer Relationship Management (CRM), and Manufacturing.

The OASIS MQTT TC is producing a standard for the Message Queuing Telemetry Transport Protocol compatible with MQTT V3.1, together with requirements for enhancements, documented usage examples, best practices, and guidance for use of MQTT topics with commonly available registry and discovery mechanisms. The standard supports bi-directional messaging to uniformly handle both signals and commands, deterministic message delivery, basic QoS levels, always/sometimes-connected scenarios, loose coupling, and scalability to support large numbers of devices. Candidates for enhancements include message priority and expiry, message payload typing, request/reply, and subscription expiry.

As an M2M/Internet of Things (IoT) connectivity protocol, MQTT is designed to support messaging transport from remote locations/devices involving small code footprints (e.g., 8-bit, 256KB ram controllers), low power, low bandwidth, high-cost connections, high latency, variable availability, and negotiated delivery guarantees. For example, MQTT is being used in sensors communicating to a broker via satellite links, SCADA, over occasional dial-up connections with healthcare providers (medical devices), and in a range of home automation and small device scenarios. MQTT is also ideal for mobile applications because of its small size, minimized data packets, and efficient distribution of information to one or many receivers (subscribers).