Detecting the status of a mesh node in a wireless mesh network
First Claim
Patent Images
1. A method for detecting the status of a mesh node in a wireless mesh network of one or a plurality of mesh nodes, wherein a gateway is building up a trust vector over time by combining:
- active detection of the status of a mesh node by accumulating responses to transmitted queries, wherein the active detection comprises;
sending a query to a mesh node neighbour according to a communications protocol, andchecking whether the response received is the expected response, wherein if the response received is the expected response, storing a positive value in a table, and if the response received is not the response expected, storing a negative value in a table,passive detection of the status of a mesh node by monitoring and collecting routing metric values and storing the values in a table, wherein the passive detection comprises;
monitoring the behavior of their upstream neighbours, with respect to link quality,collecting the link quality values in a table,storing the link quality values about its neighbours periodically in the table, based on a routing tree, andstoring the time at which the link quality is measured along with the link quality and a neighbor identifier, thereby enable link quality values to be stored over time,wherein a reputation manager at each mesh node sends the trust vector [AEcB, AKcB, ψ
pRcB] at regular intervals to the gateway, wherein the trust vector comprises (1) an experience valuation based on the gateway'"'"'s direct experience with the mesh node, (2) a knowledge valuation based on what the gateway knows about the mesh node, and (3) a recommendation valuation based on collected recommendations from other mesh nodes or other gateways, wherein the status of the mesh node is regarded as misbehaving when the trust vector reaches a certain level.
4 Assignments
0 Petitions
Accused Products
Abstract
A method for detecting the status of a mesh node in a wireless mesh network, wherein a gateway is building up a vector over time by combining active detection, passive detection and binary tests on anomaly metrics and wherein the status of the mesh node is regarded as misbehaving when the vector reaches a certain level.
14 Citations
7 Claims
-
1. A method for detecting the status of a mesh node in a wireless mesh network of one or a plurality of mesh nodes, wherein a gateway is building up a trust vector over time by combining:
-
active detection of the status of a mesh node by accumulating responses to transmitted queries, wherein the active detection comprises; sending a query to a mesh node neighbour according to a communications protocol, and checking whether the response received is the expected response, wherein if the response received is the expected response, storing a positive value in a table, and if the response received is not the response expected, storing a negative value in a table, passive detection of the status of a mesh node by monitoring and collecting routing metric values and storing the values in a table, wherein the passive detection comprises; monitoring the behavior of their upstream neighbours, with respect to link quality, collecting the link quality values in a table, storing the link quality values about its neighbours periodically in the table, based on a routing tree, and storing the time at which the link quality is measured along with the link quality and a neighbor identifier, thereby enable link quality values to be stored over time, wherein a reputation manager at each mesh node sends the trust vector [AEcB, AKcB, ψ
pRcB] at regular intervals to the gateway, wherein the trust vector comprises (1) an experience valuation based on the gateway'"'"'s direct experience with the mesh node, (2) a knowledge valuation based on what the gateway knows about the mesh node, and (3) a recommendation valuation based on collected recommendations from other mesh nodes or other gateways, wherein the status of the mesh node is regarded as misbehaving when the trust vector reaches a certain level. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
Specification