Difference between revisions of "Intelligence at the Edge"
From AMTech WikiDocs
(Created page with "Edge *Generalized protocols *Smooth protocols chatting **Transmitting only the interesting information that results from local data processing not only mea...") |
|||
(22 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
[[AMTech...#Edge|Edge]] | [[AMTech...#Edge|Edge]] | ||
− | * | + | *Generalize protocols |
+ | *Example [[Example_plugins#LLRPReader|LLRPReader]] and [[Example_plugins#BLEbeaconsScanner|BLEbeaconsScanner]] implement smoothing logic. | ||
*Smooth protocols chatting | *Smooth protocols chatting | ||
**Transmitting only the interesting information that results from local data processing not only means more efficient use of bandwidth but the capability to collect and analyze much higher volumes of data | **Transmitting only the interesting information that results from local data processing not only means more efficient use of bandwidth but the capability to collect and analyze much higher volumes of data | ||
− | *Recover from protocols | + | *Monitoring |
− | *Commands | + | **Recover and send observation about errors from devices, protocols and connection |
+ | *[[Actions#Send command|Commands]] | ||
+ | *Implement placeholders (see [[Sensor%27s network#Observation Enrichment|Observation Enrichment]]) allowing specific protocol data to be integrated with the [[Sensor's network#Observations and observation types|Observations]] | ||
+ | ** <code>#{bridgeId}</code> m2mBox Id set at bridgeConfig.json configuration file bridgeId property, or a unique id create in absence or this value | ||
+ | ** <code>#{typeId}</code> Unique id of the thingType that produces the event | ||
+ | ** <code>#{thingId}</code> Unique id of the instances that produces the event | ||
+ | ** <code>#{tenantId}</code> Tenant id used to authenticate the m2mBridge, defined at bridgeConfig.json tenant property | ||
+ | ** <code>#{userId}</code> User id used to authenticate the m2mBridge, defined at bridgeConfig.json userId property | ||
+ | '''plugins can implement custom placeholders, specifics to their domain.''' (See [[HelloWorld_plugin#What_helloWorld_does|HelloWorld placeholder]]) | ||
+ | *[[Edge_reasoners|Edge reasoners]] |
Latest revision as of 15:49, 19 September 2017
- Generalize protocols
- Example LLRPReader and BLEbeaconsScanner implement smoothing logic.
- Smooth protocols chatting
- Transmitting only the interesting information that results from local data processing not only means more efficient use of bandwidth but the capability to collect and analyze much higher volumes of data
- Monitoring
- Recover and send observation about errors from devices, protocols and connection
- Commands
- Implement placeholders (see Observation Enrichment) allowing specific protocol data to be integrated with the Observations
-
#{bridgeId}
m2mBox Id set at bridgeConfig.json configuration file bridgeId property, or a unique id create in absence or this value -
#{typeId}
Unique id of the thingType that produces the event -
#{thingId}
Unique id of the instances that produces the event -
#{tenantId}
Tenant id used to authenticate the m2mBridge, defined at bridgeConfig.json tenant property -
#{userId}
User id used to authenticate the m2mBridge, defined at bridgeConfig.json userId property
-
plugins can implement custom placeholders, specifics to their domain. (See HelloWorld placeholder)