Skip to main content
Jump to: navigation, search

Difference between revisions of "OM2M/Roadmap"

Line 1: Line 1:
This page describes the current plan for the upcoming features of the OM2M project. Please note that this plan is a moving target - depending on priorities and community contribution and commitments, the plan can change any time, so do not take it for granted, but see it as a guidance of direction.
+
This page describes the current plan for the upcoming features of the OM2M project.  
 +
Please note that this plan is a moving target. Depending on priorities and community contribution, the roadmap can change any time, so do not take it for granted, but see it as a guidance of direction.
  
 
== Release 1.0.0 ==
 
== Release 1.0.0 ==

Revision as of 15:27, 1 March 2015

This page describes the current plan for the upcoming features of the OM2M project. Please note that this plan is a moving target. Depending on priorities and community contribution, the roadmap can change any time, so do not take it for granted, but see it as a guidance of direction.

Release 1.0.0

The first release of OM2M is planned for 31 March 2015. It will include the following features:

  • Implement the SmartM2M standard. For more information see SmartM2M standard
  • Provide a modular architecture running on top of an OSGi layer based on Eclipse Equinox.
  • Integrate Maven and Tycho to automate build process and RCP development.
  • Provide a protocol-independent CORE plugin to handle generic REST request.
  • Provide the following features: machine registration, application deployment, container management, resource discovery, access right authorization, subscription / notification, group management, and resource announcement.
  • Provide a HTTP binding plugin based on Jetty and Apache HTTP client libraries.
  • Provide a CoAP binding plugin based on the Californium library.
  • Provide a simple retargeting mechanism to connect HTTP and CoAP enabled devices.
  • Provide an interworking sample plugin with simulated devices to show how to connect legacy devices.
  • Provide a web interface plugin for browsing and debugging each machine resource structure.
  • Provide a persistence solution layer based on EclipseLink JPA library to support various database solutions.
  • Replace the DB4O database with the H2 database which provide better performance.
  • Introduce persistence parameters to the "config.ini" file to simplify the JPA configuration.
  • Replace the XSD resource validation with a native validation mechanism that offers more flexibility.
  • Replace the OASIS OBIX library with a native encoder/decoder based on the JAXB library.
  • Improve the OM2M performance by optimizing the resource structure and database access.
  • Enable NAT traversing.

Release 2.0.0

The second release of OM2M is planned for September 2015. It will include the following features:

Back to the top