Jump to: navigation, search

Project Proposals:Internet of Things Data Management (IOTDM)

Name

Internet of Things Data Management (IOTDM)

Repo Name

iotdm

Follow this link to the IoTDM Main page.

Description

The oneM2M Global Partnership is developing standards for Machine‐to‐Machine (M2M) communications enabling large‐scale implementation of the Internet‐of‐Things (IoT). It is progressing specifications supporting communications between the oneM2M service entities, and work is underway on oneM2M‐specific bindings for CoAP, HTTP, and MQTT protocol implementations.

The proposal is to develop a data-centric middleware that will act as a oneM2M compliant IoT Data Broker (IOTDM) and enable authorized applications to retrieve IoT data uploaded by any device. The choice of a data-centric paradigm, as opposed to a message-centric one, ensures that the network - as a distributed IoT platform - provides a single version of the global data space to interested applications. It also optimizes network traffic and application processing as applications and/or devices join and leave the IoT domain.

The IOTDM application (plugin) will interact with data producers (IoT devices such as sensors, and IoT management systems) and data consumers (analytics engines). The interaction is through a variety of IoT Protocol plugins, such as CoAP, MQTT, HTTP, etc.

Overall Architecture

Idm.jpg

References:

Scope

IOTDM Core:

  • Definition of a YANG model representing the oneM2M resource tree (TS0001, TS0004)
  • Definition and implementation of RPCs for CRUD and notifications (TS0004)
  • Integration of existing common IoT southbound protocols: CoAP (TS0008), MQTT (TS0010), HTTP (TS0009)
  • Security Manager – User Authentication and Policy Enforcement
    • The entities ( devices, applications, other IOTDMs) need to be authenticated and and authorized to access the data store. We can leverage the AAA module under development
    • Once authenticated, the clients accessing the data store must be limited to certain operations. oneM2M defines some mechanisms to address this need. We may explore other ways as we see fit (AAA authorization)
  • Federation – distributed set of IOTDM instances
    • We expect that other oneM2M data stores will be deployed in the network. Some on ODL, some on different platforms. oneM2M defines some procedures to interconnect various data stores. We could implement them and others as we see fit.

South Bound Protocols:

  • We will implement as many IoT southbound wire-protocols as possible (as contributions permit): HTTP, CoAP, MQTT, XMPP, Thread…

Resources Committed (developers committed to working)

Resources Committed (developers committed to working)

  • Lionel Florit (lflorit@cisco.com)
  • John Burns (johnburn@cisco.com)
  • Reinaldo Penno (repenno@cisco.com)
  • Jan Medved (jmedved@cisco.com)
  • Cangji Wu (canwu@cisco.com)
  • Wenxin Shi (wenxshi@cisco.com)
  • Kevin Blomseth (kblomseth@echelon.com)
  • Peter Chau(ychau@cisco.com)

Initial Committers

Initial Committers:

  • [lflorit@cisco.com Lionel Florit, ODL userID lflorit]
  • [johnburn@cisco.com John Burns, ODL userID jburns]
  • [repenno@gmail.com Reinaldo Penno]
  • [cyc79@etri.re.kr, Yunchul Choi , ETRI)]
  • [kblomseth@echelon.com, Kevin Blomseth, Echelon, ODL userID kblomseth]
  • [jmedved@cisco.com Jan Medved]

Vendor Neutral

  • No vendor package names in code
  • No vendor branding present in code or output of build
  • No vendor branding present in documentation

Meets Board Policy (including IPR)