Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "IoT"
(→M2M Industry Working Group) |
(→Work in progress) |
||
| (47 intermediate revisions by 6 users not shown) | |||
| Line 3: | Line 3: | ||
There are several initiatives to bring Machine-to-Machine technologies at Eclipse: | There are several initiatives to bring Machine-to-Machine technologies at Eclipse: | ||
| − | = | + | = M2M Industry Working Group = |
| − | [http://www.eclipse.org/ | + | In November 2011, a set of industrial partners decided to create an [http://www.eclipse.org/org/industry-workgroups/industry_wg_process.php Industry Working Group] at Eclipse to address the main obstacle to M2M market growth: many incompatible platforms and protocols are available, and developers are forced to continually reinvent solutions that have already been created. |
| − | + | *[http://www.eclipse.org/org/industry-workgroups/m2miwg_charter.php M2M Industry Working Group Charter] | |
| + | *[http://wiki.eclipse.org/images/5/52/M2M_IWG_Presentation.pdf M2M IWG Presentation] [http://wiki.eclipse.org/images/6/62/M2M_IWG_Presentation.zip [ppt]] | ||
| + | *[[Machine-to-Machine/M2MIWG/Resources | Other resources (presentation, graphic files, ...)]] | ||
| + | *[[Machine-to-Machine/M2MIWG/Weekly call minutes|☎ Weekly status call minutes]] | ||
| + | *[https://dev.eclipse.org/mailman/listinfo/m2m-iwg Mailing List] | ||
| + | *[[Machine-to-Machine/Face-2-Face-Meeting-Jan31|Face-to-Face Meeting on Jan 31]] | ||
| + | *[[Machine-to-Machine/Face-2-Face-Meeting-Mar29|Face-to-Face Meeting on March 29]] (EclipseCon NA 2012 - Reston, VA.) | ||
| − | |||
| − | |||
| − | = M2M | + | == Work in progress == |
| + | |||
| + | *[[Machine-to-Machine/M2MIWG/Terminology|Terminology]] | ||
| + | *[[Machine-to-Machine/M2MIWG/Roadmap|Roadmap draft]] | ||
| + | *[[Machine-to-Machine/M2MIWG/M2M meta-model|M2M meta-model]] | ||
| + | *[[Machine-to-Machine/M2MIWG/M2M Scenarios|M2M Scenarios]] | ||
| + | *[[Machine-to-Machine/M2MIWG/M2M-Problems|M2M Problems]] | ||
| + | *[[Machine-to-Machine/M2MIWG/M2M-Interface|M2M Interface]] | ||
| + | *[[Machine-to-Machine/M2MIWG/Marketing-Programs | Marketing Programs]] | ||
| + | *[[Machine-to-Machine/M2MIWG/M2M EPP Package | M2M EPP Package]] | ||
| + | |||
| + | = M2M Eclipse projects = | ||
| + | |||
| + | == Koneki == | ||
| + | |||
| + | [http://www.eclipse.org/koneki/ Koneki] is a Technology Project that aims at providing Machine-to-Machine solutions developers with tools easing the development, simulation, testing/debugging and deployment of such solutions. | ||
| + | |||
| + | It has been provisioned at the end of May 2011, with an initial contribution actually done during October 2011. Initial focus is put on providing [http://www.eclipse.org/koneki/ldt/ tools for Lua developers]. | ||
| + | |||
| + | *[[Koneki|Koneki project wiki page]] | ||
| + | |||
| + | == Paho == | ||
| + | |||
| + | The Paho project has been created to provide scalable open-source implementations of open and standard messaging protocols aimed at new, existing, and emerging applications for Machine-to-Machine (M2M) and Internet of Things (IoT). The initial contribution of MQTT client code was from IBM during March 2012. | ||
| + | |||
| + | *[[Paho|Paho project wiki page]] | ||
| + | |||
| + | == Mihini == | ||
| − | + | Mihini is a proposed Technology project that aims at providing an open source implementation of an embedded runtime exposing high-level Lua API that can be used to develop portable M2M applications easily. | |
| + | The project is currently in the proposal phase. | ||
| − | *[[ | + | *[[Mihini|Mihini project wiki page]] |
| − | + | ||
| − | + | ||
| − | [[Category: | + | [[Category:Machine-to-Machine]] [[Category:Eclipse_IWG]] |
Revision as of 09:11, 11 September 2012
According to Wikipedia, Machine-to-Machine (M2M), refers to technologies that allow both wireless and wired systems to communicate with other devices of the same ability.
There are several initiatives to bring Machine-to-Machine technologies at Eclipse:
Contents
M2M Industry Working Group
In November 2011, a set of industrial partners decided to create an Industry Working Group at Eclipse to address the main obstacle to M2M market growth: many incompatible platforms and protocols are available, and developers are forced to continually reinvent solutions that have already been created.
- M2M Industry Working Group Charter
- M2M IWG Presentation [ppt]
- Other resources (presentation, graphic files, ...)
- ☎ Weekly status call minutes
- Mailing List
- Face-to-Face Meeting on Jan 31
- Face-to-Face Meeting on March 29 (EclipseCon NA 2012 - Reston, VA.)
Work in progress
- Terminology
- Roadmap draft
- M2M meta-model
- M2M Scenarios
- M2M Problems
- M2M Interface
- Marketing Programs
- M2M EPP Package
M2M Eclipse projects
Koneki
Koneki is a Technology Project that aims at providing Machine-to-Machine solutions developers with tools easing the development, simulation, testing/debugging and deployment of such solutions.
It has been provisioned at the end of May 2011, with an initial contribution actually done during October 2011. Initial focus is put on providing tools for Lua developers.
Paho
The Paho project has been created to provide scalable open-source implementations of open and standard messaging protocols aimed at new, existing, and emerging applications for Machine-to-Machine (M2M) and Internet of Things (IoT). The initial contribution of MQTT client code was from IBM during March 2012.
Mihini
Mihini is a proposed Technology project that aims at providing an open source implementation of an embedded runtime exposing high-level Lua API that can be used to develop portable M2M applications easily. The project is currently in the proposal phase.