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/M2MIWG/M2M-Problems"
(→M2M Problem Description Links) |
(→M2M Problem Description Template) |
||
| Line 5: | Line 5: | ||
== M2M Problem Description Template == | == M2M Problem Description Template == | ||
| − | The following is | + | The following is the template for an M2M Problem Description. |
#M2M Problem Number - Incremental id number from Problem list page for easy reference in other pages/docs | #M2M Problem Number - Incremental id number from Problem list page for easy reference in other pages/docs | ||
Revision as of 10:58, 6 March 2012
Contents
M2M Problems
The Machine to Machine(M2M) space combines system from the embedded space and the enterprise/cloud space. This combination introduces problems that must be addressed by an M2M system provider that do not traditionally exist in either the embedded space or the enterprise/cloud space. This page is meant to catalog these M2M specific issues. This catalog is meant to serve as an educational tool for developers and architects who are new to M2M and as a reference during development of M2M technologies at Eclipse.
M2M Problem Description Template
The following is the template for an M2M Problem Description.
- M2M Problem Number - Incremental id number from Problem list page for easy reference in other pages/docs
- M2M Problem Name - Descriptive name of the problem
- M2M Problem Description - Description of the problem.
- Fielded Solution Patterns - Description of known approaches to dealing with the problem.
- Related M2M Problem Numbers - Numbers of other problems that are closely related to this one
- Referenced M2M Scenarios - Numbers of M2M Scenarios that depend on the solution patterns for this problem
When creating a new M2M problem description, please add it to the list of links below, claiming the next number in the sequence. Then add your problem description to the descriptions section below.