Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "OM2M/Roadmap"
< OM2M
(→Release 1.0.0) |
(→Release 1.0.0) |
||
| Line 7: | Line 7: | ||
* Implement the SmartM2M standard. For more information see [http://www.etsi.org/technologies-clusters/technologies/m2m SmartM2M standard] | * Implement the SmartM2M standard. For more information see [http://www.etsi.org/technologies-clusters/technologies/m2m SmartM2M standard] | ||
* Provide a protocol-independent CORE plugin to handle generic REST request. | * Provide a protocol-independent CORE plugin to handle generic REST request. | ||
| − | * Provide machine authentication, application registration, container management, resource discovery, access right authorization, subscription / notification, group management, resource discovery, and resource announcement. | + | * Provide the following features: machine authentication, application registration, container management, resource discovery, access right authorization, subscription / notification, group management, resource discovery, and resource announcement. |
* Provide a HTTP binding plugin based on Jetty and Apache HTTP client libraries. | * 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 CoAP binding plugin based on the Californium library. | ||
Revision as of 08:22, 1 March 2015
This page describes the current plan for the upcoming features of the Eclipse 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.
Release 1.0.0
The first release of OM2M is planned for 31 March 2015. It includes the following features:
- Implement the SmartM2M standard. For more information see SmartM2M standard
- Provide a protocol-independent CORE plugin to handle generic REST request.
- Provide the following features: machine authentication, application registration, container management, resource discovery, access right authorization, subscription / notification, group management, resource discovery, 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 retargeting mechanism based the APOC resource to connect HTTP and CoAP enabled devices.
- Provide an interworking proxy sample plugin with simulated devices to show how to connect legacy devices.
- Provide a web interface plugin for browsing and debugging the SCL 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 code to provide flexibility.
- Replace the OASIS OBIX library with a native code based on the JAXB library.
- Improve the OM2M performance by optimizing the resource structure and database access.
- Provide a long-polling mechanism for NAT traversing based on the resource "CommunicationChannel".
Release 2.0.0
The second release of OM2M is planned for 30 September 2015. It includes the following features:
- Implementation of oneM2M standard. For more information see oneM2M standard.