Difference between revisions of "Intelligence at the Edge"
From AMTech WikiDocs
| Line 8: | Line 8: | ||
*[[Actions#Send command|Commands]] | *[[Actions#Send command|Commands]] | ||
*Implement [[Observation enrichment#Placeholders substitution|Placeholders]] allowing specific protocol data be integrated with the [[Sensor's network#Observations and observation types|Observations]] | *Implement [[Observation enrichment#Placeholders substitution|Placeholders]] allowing specific protocol data be integrated with the [[Sensor's network#Observations and observation types|Observations]] | ||
| − | ** #{deviceId} m2mBox Id set at bridgeConfig.json configuration file bridgeId property, or a unique id create in absence or this value | + | ** <code>#{deviceId}</code> 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 | + | ** <code>#{typeId}</code> Unique id of the thingType that produces the event |
| − | ** #{thingId} Unique id of the instances that produces the event | + | ** <code>#{thingId}</code> Unique id of the instances that produces the event |
| − | ** #{tenantId} Tenant id used to authenticate the m2mBridge, defined at bridgeConfig.json tenant property | + | ** <code>#{tenantId}</code> 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 | + | ** <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]]) | '''plugins can implement custom placeholders, specifics to their domain.''' (See [[HelloWorld_plugin#What_helloWorld_does|HelloWorld placeholder]]) | ||
Revision as of 08:55, 16 May 2016
- 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 allowing specific protocol data be integrated with the Observations
-
#{deviceId}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)
