IPSO Working Group Resources
This area of the community provides information to people interested in specifying, building, testing, or just trying out Smart Object systems. Check back often, as we will be continually adding resources that are relevant to Smart Objects, such as work integrating Identity and Privacy aspects, and new reference architecture guidelines.
The IPSO Woking Group offers this technical archive of white papers and other materials developed by the IPSO Working Group members companies that offer valuable information in support of our mission.
IPSO Smart Object Guidelines provide a common design pattern, an object model, that can effectively use the IETF CoAP protocol to provide high-level interoperability between Smart Object devices and connected software applications on other devices and services.
Public IPSO Repository
The IPSO Smart Object Registry registry is intended for developers that are building products based on IPSO Objects, it is not intended to be used at runtime by applications. Some of the objects are generic in nature, such as voltage, altitude or percentage, while others are more specialized like the colour object or the gyrometer object. Actuators and controllers are also defined such as timer or buzzer and joystick and Level. All of these objects were found to be necessary on a variety of use case domains.
Internet of Things Protocol Comparison White Paper
Many standards-developing organizations have contributed various technological building blocks to make IoT deployments more robust and secure. A popular debate among technologists working on IoT deployments is about the best choice of protocols for getting data from and to IoT devices. In this article, members of the IPSO Working Group considered six standardized protocols (HTTP, HTTP/2, WebSockets, XMPP, MQTT, CoAP), and refer to them as “transfer protocols.” This is not a comprehensive list of protocols in use in IoT, but it represents an example of each of the different constructs, reliable, unreliable, REST, publish/subscribe, chat, point to point, client/server, extended services etc.
This whitepaper compares the differences between these six transfer protocols as used with IoT devices. The purpose is to provide technical and product personnel, in a way to assess the impact of each protocol and what they provide with regard to their IoT products. IoT products will likely require a suite of standard protocols to support the many different configurations and requirements of the systems/services that they are deployed in.