background preloader

IoT Standards and Protocols

Facebook Twitter



Process. Sensor Modelling. MPEG-21. Microformats. HTML Microdata. EEML. IETF. Constrained Application Protocol (CoAP) CoRE Working Group Z.

Constrained Application Protocol (CoAP)

Shelby Internet-Draft Sensinode Intended status: Standards Track K. Hartke Expires: December 30, 2013 C. Routing Over Low power and Lossy networks (roll) Roll-3. ITU-T USN. ETSI M2M. JSON. Web Service Architecture. REST. Representational State Transfer (REST) is a software architecture style consisting of guidelines and best practices for creating scalable web services.[1][2] REST is a coordinated set of constraints applied to the design of components in a distributed hypermedia system that can lead to a more performant and maintainable architecture.[3] REST has gained widespread acceptance across the Web[citation needed] as a simpler alternative to SOAP and WSDL-based Web services.


RESTful systems typically, but not always, communicate over the Hypertext Transfer Protocol with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) used by web browsers to retrieve web pages and send data to remote servers.[3] 6LoWPAN. 6LoWPAN is an acronym of IPv6 over Low power Wireless Personal Area Networks.[1] 6LoWPAN is the name of a concluded working group in the Internet area of the IETF.[2] The 6LoWPAN concept originated from the idea that "the Internet Protocol could and should be applied even to the smallest devices,"[3] and that low-power devices with limited processing capabilities should be able to participate in the Internet of Things.[4] The 6LoWPAN group has defined encapsulation and header compression mechanisms that allow IPv6 packets to be sent to and received from over IEEE 802.15.4 based networks.


IPv4 and IPv6 are the work horses for data delivery for local-area networks, metropolitan area networks, and wide-area networks such as the Internet. Likewise, IEEE 802.15.4 devices provide sensing communication-ability in the wireless domain. The inherent natures of the two networks though, are different. 6LowApp. The 6LowApp activity of the IETF coordinates work in the IETF to specify application (as well as possibly transport, security and operations) protocols for constrained nodes and networks, the Wireless Embedded Internet. 6LowApp is not itself an IETF Working Group, but is intended to result in the creation of IETF Working Groups.


In the 6LowApp activity, definition of work will be carried out as well as initial work leading up to specifications. CoRE Working Group ¶ Object Naming Service. Object Name Service (ONS) is a mechanism that leverages Domain Name System (DNS) to discover information about a product and related services from the Electronic Product Code (EPC).

Object Naming Service

It is a component of the EPCglobal Network. The Object Name Service (ONS) is an automated networking service similar to the Domain Name Service (DNS) that points computers to sites on the World Wide Web. When an interrogator reads an RFID tag, the Electronic Product Code is passed to middleware, which, in turn, goes to an ONS on a local network or the Internet to find where information on the product is stored. EDIFACT. United Nations/Electronic Data Interchange For Administration, Commerce and Transport (UN/EDIFACT) is the international EDI standard developed under the United Nations.


Comet (programming) Comet is a web application model in which a long-held HTTP request allows a web server to push data to a browser, without the browser explicitly requesting it.[1][2] Comet is an umbrella term, encompassing multiple techniques for achieving this interaction.

Comet (programming)

All these methods rely on features included by default in browsers, such as JavaScript, rather than on non-default plugins. HTML WebSockets. WebSocket is a protocol providing full-duplex communications channels over a single TCP connection.

HTML WebSockets

The WebSocket protocol was standardized by the IETF as RFC 6455 in 2011, and the WebSocket API in Web IDL is being standardized by the W3C. Technical overview[edit] Browser implementation[edit] WebSocket protocol handshake[edit] To establish a WebSocket connection, the client sends a WebSocket handshake request, for which the server returns a WebSocket handshake response, as shown in the following example:[9]:section 1.2 Client request: GET /chat HTTP/1.1 Host: Upgrade: websocket Connection: Upgrade Sec-WebSocket-Key: x3JJHMbDL1EzLkh9GBhXDw== Sec-WebSocket-Protocol: chat, superchat Sec-WebSocket-Version: 13 Origin: Server response: Project Atmosphere. IPv6. Ubiquitous ID. OGC. Introduction OGC members are specifying interoperability interfaces and metadata encodings that enable real time integration of heterogeneous sensor webs into the information infrastructure.


Developers will use these specifications in creating applications, platforms, and products involving Web-connected devices such as flood gauges, air pollution monitors, stress gauges on bridges, mobile heart monitors, Webcams, and robots as well as space and airborne earth imaging devices. OGC members have developed and tested the following candidate specifications. Others are planned. Observations & Measurements (O&M) - Standard models and XML Schema for encoding observations and measurements from a sensor, both archived and real-time. Please visit our OpenGIS® Specification page to view and comment on publicly available OGC Sensor Web Enablement Specifications. General Documentation. SensorML. EPCglobal. AWISSENET. The OPC Foundation - The Interoperability Standard for a Connected World™ ASAM Connects - Home.