IoT Standards and Protocols

Facebook Twitter
WebHooks
Service

Process

Sensor Modelling

MPEG-21

Microformats

Last week the microformats.org community celebrated its 7th birthday at a gathering hosted by Mozilla in San Francisco and recognized accomplishments, challenges, and opportunities. Humans First: Admin Emeriti & New Admins The microformats tagline “humans first, machines second” forms the basis of many of our principles, and in that regard, we’d like to recognize a few people and thank them for their years of volunteer service as community admins: They’ve each been essential positive community contributors and guides over the years, and as admin emeriti are always welcome back should they decided to become admins again. We’re also pleased to announce two new community admins: Both have similarly been consistent positive contributors to microformats for years, and we’re very happy they’ve stepped up as community admins. Microformats
HTML Microdata
This site provides information about Extended Environments Markup Language (EEML), a protocol for sharing sensor data between remote responsive environments, both physical and virtual. It can be used to facilitate direct connections between any two environments; it can also be used to facilitate many-to-many connections as implemented by the web service Pachube, which enables people to tag and share real time sensor data from objects, devices and spaces around the world. Possible end-users range from construction managers, large-building occupants and architects, to electronics manufacturers and interactive artists and designers. EEML supports installations, buildings, devices and events that collect environmental data and enables people to share this resource in realtime either within their own organisations or with the world as a whole via an internet connection or mobile network access. EEML EEML

IETF

IETF The Internet Engineering Task Force (IETF) The goal of the IETF is to make the Internet work better. The mission of the IETF is to make the Internet work better by producing high quality, relevant technical documents that influence the way people design, use, and manage the Internet. Newcomers to the IETF should start here.
Constrained Application Protocol (CoAP) Constrained Application Protocol (CoAP) CoRE Working Group Z. 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
object {} { members } members JSON

JSON

Web Service Architecture

Web Service Architecture A Web service is a method of communications between two electronic devices over a network. It is a software function provided at a network address over the web with the service always on as in the concept of utility computing. The W3C defines a Web service as: a software system designed to support interoperable machine-to-machine interaction over a network.

REST

REST Representational state transfer (REST) is an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors, and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.[1][2] The term representational state transfer was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation at UC Irvine.[1][3]
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. 6LoWPAN 6LoWPAN
6LowApp 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 ¶ The first result of the 6lowapp activity has been the CoRE working group, which met for the first time at IETF77.
Object Naming Service 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). 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. ONS points the middleware to a server where a file about that product is stored. The middleware retrieves the file (after proper authentication), and the information about the product in the file can be forwarded to a company's inventory or supply chain applications. [1]
EDIFACT United Nations/Electronic Data Interchange For Administration, Commerce and Transport (UN/EDIFACT) is the international EDI standard developed under the United Nations. In 1987, following the convergence of the UN and US/ANSI syntax proposals, the UN/EDIFACT Syntax Rules were approved as the ISO standard ISO 9735 by the International Organization for Standardization. The EDIFACT standard provides:

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. All these methods rely on features included by default in browsers, such as JavaScript, rather than on non-default plugins. The Comet approach differs from the original model of the web, in which a browser requests a complete web page at a time.[3]
WebSocket is a protocol providing full-duplex communications channels over a single TCP connection. 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

HTML WebSockets

Project Atmosphere
IPv6
Ubiquitous ID
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. OGC
1) Overview 2) Downloads3) Official Schemas 4) Related News 1) Overview The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and postmeasurement. The main objective is to enable interoperability, first at the syntactic level and later at the semantic level (by using ontologies and semantic mediation), so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes. This standard is one of several implementation standards produced under OGC’s Sensor Web Enablement (SWE) activity. SensorML
EPCglobal
AWISSENET
The OPC Foundation - The Interoperability Standard for a Connected World™
ASAM Connects - Home