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 List) |
(→M2M Problem Descriptions) |
||
| Line 21: | Line 21: | ||
== M2M Problem Descriptions == | == M2M Problem Descriptions == | ||
| + | |||
| + | ==='''M2M-Problem-001 : Sharing of information for properly interpreting data values'''=== | ||
| + | |||
| + | Consider a sensor that provides the refrigerator temperature as a floating point number. In an M2M system there will be many potential consumers of this sensor reading. Some consumers may be on the embedded platform itself, others may execute in the enterprise or cloud. There is also a producer for transforming this number into a logical format(3.7 degrees C) instead of its protocol wire format. There is additional information that is required in order to properly make use of this floating point number that represents Refrigerator Temperature. Examples of this additional information from the producer include the data type(floating point), the units of the number(degrees Celsius), data range minimum and maximum values, and values used to represent sensor errors or missing sensors. Consumers may have their own additional information about this particular sensor reading, such as warning and error thresholds for alarm notification and text to display the units and sensor name in various human readable languages. | ||
| + | |||
| + | In order for producers and consumers to collaborate effectively, this additional information about sensors and actuators needs to be shared between the interested systems. | ||
| + | |||
| + | Related Scenarios : M2M-Scenario-001 | ||
| + | |||
| + | Referenced Problems : | ||
Revision as of 15:31, 7 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.
M2M Problem List
M2M Problem 001 : Sharing of information for properly interpreting data values
M2M Problem Descriptions
M2M-Problem-001 : Sharing of information for properly interpreting data values
Consider a sensor that provides the refrigerator temperature as a floating point number. In an M2M system there will be many potential consumers of this sensor reading. Some consumers may be on the embedded platform itself, others may execute in the enterprise or cloud. There is also a producer for transforming this number into a logical format(3.7 degrees C) instead of its protocol wire format. There is additional information that is required in order to properly make use of this floating point number that represents Refrigerator Temperature. Examples of this additional information from the producer include the data type(floating point), the units of the number(degrees Celsius), data range minimum and maximum values, and values used to represent sensor errors or missing sensors. Consumers may have their own additional information about this particular sensor reading, such as warning and error thresholds for alarm notification and text to display the units and sensor name in various human readable languages.
In order for producers and consumers to collaborate effectively, this additional information about sensors and actuators needs to be shared between the interested systems.
Related Scenarios : M2M-Scenario-001
Referenced Problems :