Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
Many industry domains such as smart metering, energy management, inventory control, fleet management, healthcare, and security have an inherent need for technology, products and solutions that interface physical world events from sensors, actuators and other types of devices, with Enterprise and Web applications. M2M technology enables these domains, supporting not only the devices and device networks, but also integration with a wide range of enterprise middleware and Web programming models.
An M2M solution is generally composed of:
Usually, the M2M server infrastructure has to be interfaced with other information systems. Examples are telecom operators (e.g. SIM card subscription management or billing), and enterprise systems (e.g. cargo tracking and vehicle maintenance). An M2M server also needs to expose interfaces allowing third-party applications to access collected data, accept and process control functions, and to perform management and provisioning operations on modules and assets in the field.
The objective of the M2M Working group is to encourage, develop, and promote opens source solutions that can be used to overcome market inhibitors found in most M2M ecosystems, such as:
The Eclipse Foundation is a place where people collaborate to deliver exemplary, extensible tools, frameworks and runtime components. The Machine-to-Machine (M2M) Industry Working Group aims at defining an open development environment and key runtimes for M2M solutions that will enable open solutions. The M2M Industry Working Group will address the following topics:
Because M2M developers currently lack an Integrated Development Environment, the M2M Industry Working Group will initially focus on the definition of such an environment, along with key enabling runtime components for open interfaces.
The M2M Industry Working Group may have interactions with the Polarsys Working Group.
The M2M Industry Working Group will also work in collaboration with other M2M Industry Groups and Standards organizations in order to avoid fragmentation and duplication of effort. The Technical Committee M2M at ETSI is, for example, already working on the definition of an end-to-end overall high level architecture for M2M applications.
The M2M Industry Working Group will work on the following topics:
The M2M Industry Working Group will work on the requirements and specifications to support the integration of M2M tooling, with relevant Eclipse tooling that is used by developers of the Enterprise and Web applications who integrate with M2M embedded and server applications.
The M2M Industry Working Group will identify and specify software components needed to efficiently develop M2M solutions (communication services, industrial protocol implementations).
The M2M working group will identify and maintain common use cases that represent typical M2M environments. The goal is to highlight the capabilities and requirements that need to be standardized to ensure open interoperability, portability, reusability, and ease of integration.
The M2M Industry Working Group will work on the definition of a set of architectural guidelines ("M2M Blueprints") for M2M solutions, derived from the identified use cases.
The M2M Industry Working Group will identify, reference and specify open specifications for lightweight communication protocol supporting two-way communication between devices and servers. The Working Group will be responsible for the creation and the maintenance of the standard, Linux-based, implementation of this protocol; and will also create and maintain a Compatibility Test Suite to enable validation of other implementations.
The M2M Industry Working Group will work on the definition of Application Programming Interfaces both on the embedded and on the server-side in order to help increase the modularity, extensibility and effective decoupling of M2M solutions.
The M2M Industry Working Group will define the technical requirements for allowing the delivery of M2M-oriented software components (industrial protocol drivers, embedded devices models, code generators, etc.) via the Eclipse Marketplace.
Because M2M development requires actual hardware, and likely prepaid airtime, in order to perform end-to-end experiments, the M2M Working Group may work on the definition of a so-called "hacker place", which will take the form of a website easing the ordering of M2M developer kits (development boards, wireless sensors, 3G modems, etc.). The M2M Working Group will work together with the Eclipse Foundation and hardware providers to propose discounts on developer kits, airtime, etc.
Developing and testing M2M integration with Enterprise and Web applications requires access to middleware, monitoring servers, enterprise servers and various Web application interfaces. The M2M Working Group will work to define and promote the availability of a "sandbox" of accessible server environments for the development, testing and integration of M2M systems with Enterprise, Web, and cloud-based software to developers using Eclipse M2M tools and runtimes.
The M2M Industry Working Group will work to communicate and evangelize the solutions developed by the M2M IWG. The activities may include joint press releases, joint trade show participation, publishing white papers and/or preparing other content that communicates the vision and solutions of the IWG.
The M2M Industry Working Group will follow the Eclipse Industry Working Group Process.
Back to the top