Difference between revisions of "Mesh Network"
From AMTech WikiDocs
(→Mesh Validations) |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
− | |||
A Mesh network is composed of a root and multiple nodes, all thing instances of the type stpg (Smart Tracker Proximity Gateway) | A Mesh network is composed of a root and multiple nodes, all thing instances of the type stpg (Smart Tracker Proximity Gateway) | ||
+ | |||
+ | == Mesh Validations == | ||
+ | |||
A set of stpg instances form a valid mesh if the following conditions are met: | A set of stpg instances form a valid mesh if the following conditions are met: | ||
− | * | + | * All instances must be valid for its metadata |
− | * there must be a single root node (mode=1 or mode=3 in the sc | + | * Mesh id unique for templates in tenant (networkId property in the sc json) |
− | * all instances must have the same mesh id (meshId property in the sc | + | * there must be a single root node (mode=1 or mode=3 in the sc json) |
+ | * all instances must have the same mesh id (meshId property in the sc json) | ||
* all instances must have the same channel | * all instances must have the same channel | ||
* if using encryption, all instances must have the same seed | * if using encryption, all instances must have the same seed |
Latest revision as of 14:09, 19 November 2020
A Mesh network is composed of a root and multiple nodes, all thing instances of the type stpg (Smart Tracker Proximity Gateway)
Mesh Validations
A set of stpg instances form a valid mesh if the following conditions are met:
- All instances must be valid for its metadata
- Mesh id unique for templates in tenant (networkId property in the sc json)
- there must be a single root node (mode=1 or mode=3 in the sc json)
- all instances must have the same mesh id (meshId property in the sc json)
- all instances must have the same channel
- if using encryption, all instances must have the same seed