Difference between revisions of "Aggregation"

From AMTech WikiDocs
Jump to: navigation, search
(English, typos and grammar)
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
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.  
+
Aggregates observations read from multiple m2m bridges. As a 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 into one and execute a centralized smoothing process; if at least one bridge sees the beacons the thing is inside; if no one bridge sees the beacon the things is out.  
*The aggregatio works by thing type
+
*Aggregation can be configured by thing type
*This configuration is done at amtechM2MBridge level
+
*This configuration is done at amtechM2MBridge instance level
**Set aggregators The list of Thing types that the bridge aggregates
+
**Set aggregation type: the list of Thing types that the bridge aggregates
**Set source instances The list of instances that will act as aggregators, only one aggregator by Thing type is allowed on a local area network.
+
***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.
 
+
***Only one instance by Thing Type can be set.
 +
**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'''

Latest revision as of 00:09, 12 October 2016

Aggregates observations read from multiple m2m bridges. As a 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 into one and execute a centralized smoothing process; if at least 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.
      • Only one instance by Thing Type can be set.
    • Selecting multiples bridge instances and validating the configurations validates aggregation settings.

At the moment aggregation works just for BLEPeripheralsScanner and BLEbeaconsScanner