Difference between revisions of "Aggregation"
From AMTech WikiDocs
| Line 2: | Line 2: | ||
*Aggregation can be configured by thing type | *Aggregation can be configured by thing type | ||
*This configuration is done at amtechM2MBridge instance level | *This configuration is done at amtechM2MBridge instance level | ||
| − | **Set | + | **Set aggregation type The list of Thing types that the bridge aggregates |
| − | **Set | + | ***Only one bridge can be aggregating a Thing type on a local area network |
| + | **Set aggregation instances The list of instances that will act as sources. | ||
**Selecting multiples bridge instances and validating the configurations validates aggregation settings. | **Selecting multiples bridge instances and validating the configurations validates aggregation settings. | ||
| − | |||
'''At the moment aggregation works just for BLEPeripheralsScanner and BLEbeaconsScanner''' | '''At the moment aggregation works just for BLEPeripheralsScanner and BLEbeaconsScanner''' | ||
Revision as of 19:42, 5 October 2016
Aggregation allows to consolidate information read from many m2m bridges.Use case, an area has multiple M2Mbridges using beacons to track "things", the intention is to aggregate all the reads done by the deployed M2Mbrigdes in one and executed a centralized smoothing process; if at less one bridge sees the beacons the thing is inside; if no one bridge sees the beacon the things is out.
- Aggregation can be configured by thing type
- This configuration is done at amtechM2MBridge instance level
- Set aggregation type The list of Thing types that the bridge aggregates
- Only one bridge can be aggregating a Thing type on a local area network
- Set aggregation instances The list of instances that will act as sources.
- Selecting multiples bridge instances and validating the configurations validates aggregation settings.
- Set aggregation type The list of Thing types that the bridge aggregates
At the moment aggregation works just for BLEPeripheralsScanner and BLEbeaconsScanner
