Distributed mesh network

• US 8,626,881 B2
• Filed: 12/16/2011
• Issued: 01/07/2014
• Est. Priority Date: 12/15/2009
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Saint-Hilaire, Ylian
• Primary Examiner(s): HIGA, BRENDAN Y
• Application Number:
  US13/328,554
• Publication Number:
  US 20120159581A1
• Time in Patent Office: 753 Days
• Field of Search: 709208-211, 709220-222, 709227-229, 370310-350
• US Class Current: 709/220
• CPC Class Codes: G06F 1/3203 Power management, i.e. event-based initiation of a power-saving mode
• CPC Class Codes: G06F 3/0625 Power saving in storage systems
• CPC Class Codes: H04L 41/04 Network management architectures or arrangements
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04W 40/248 Connectivity information update
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A device, method, and system are disclosed. In one embodiment a computing device resides in a mesh network. The device includes a first storage device that operates when the computing device is awake. The first storage device stores a last known list of peer computing devices in the mesh network. The device also includes a second storage device that operates regardless of whether any central processing unit in the computing device is awake or asleep. The second storage device includes a local block that stores a list of resources provided by the first computing device and a list of computing devices in the mesh network verified by the first computing device. The second storage device also includes a remote block that stores an unverified remote list of computing devices in the mesh network.

Claims

1. A computer system, comprising:

a local node in a mesh network, the local node to;

store a first list of remote nodes in the mesh network verified by the local node;

store a second list of remote nodes in the mesh network not verified by the local node; and

iterate over the second list of remote nodes, wherein for each iteration the local node to;

define a current node from the second list of remote nodes;

determine if the current node is present in the first list of remote nodes;

verify the current node in response to determining the current node is not present in the first list of remote nodes;

store the current node in the first list of remote nodes in response to successfully verifying the current node;

determine if the current node is a last node in the second list of remote nodes; and

define, in response to the current node not being the last node in the second list of remote nodes, a next node from the second list of remote nodes as the current node.

2. The computer system of claim 1, wherein the local node further to allow remote nodes in the mesh network to access (i) the first list of remote nodes and (ii) the second list of remote nodes, while a main processor of the computer system is not fully operational.

3. The computer system of claim 1, wherein to store the current node in the first list of remote nodes comprises to:

store an internet protocol (IP) address of the current node;

store a verification timestamp of a most recent direct contact with the current node, the verification timestamp corresponding to a time of verification; and

update a version number and timestamp corresponding to the first list of remote nodes.

4. The computer system of claim 1, wherein the local node further to:

store a resource information list comprising resource information corresponding to remote nodes in the mesh network; and

wherein for each iteration the local node further to;

store, in the resource information list, resource information for the current node in response to successfully verifying the current node.

5. The computer system of claim 4, wherein the local node further to:

store a local timestamp corresponding to a date the resource information list was last updated by the local node; and

wherein for each iteration the local node further to;

determine, in response to determining the current node is present in the first list of remote nodes, whether the resource information for the current node stored in the resource information list is up-to-date by comparing the local timestamp to a resource timestamp stored in the resource information of the current node, wherein the resource timestamp corresponds to a date the resource information was created by the current node; and

store, in the resource information list, the resource information for the current node in response to determining the resource information for the current node stored in the resource information list is not up-to-date.

6. The computer system of claim 1, wherein to verify the current node comprises to:

contact the current node;

provide to the current node a first mesh certificate to allow the current node to securely verify the authenticity of the local node;

receive from the current node a second mesh certificate to allow the local node to securely verify the authenticity of the current node;

receive from the current node a third list of remote nodes verified by the current node and storing the third list of remote nodes in the second list of remote nodes; and

store the first list of remote nodes on the current node.

7. The computer system of claim 1, wherein the local node further to:

inquire with a remote server external to the mesh network whether a leader position in the mesh network is available;

establish a two-way communication tunnel with the remote server in response to the leader position being available;

wake a target node in the mesh network in response to receiving a wakeup request from the remote server over the two-way communication tunnel, the wakeup request received by the local node in response to the remote server receiving a request communication from a requestor node; and

send a resource request to the target node in response to waking the target node, wherein the resource request comprises a request to the target node to provide a resource to the requestor node.

8. A method for updating mesh network information of a local node, the method comprising:

storing, on the local node, a first list of remote nodes in a mesh network verified by the local node;

storing, on the local node, a second list of remote nodes in the mesh network not verified by the local node; and

iterating, by the local node, over the second list of remote nodes, wherein each iteration comprises;

defining a current node from the second list of remote nodes;

determining if the current node is present in the first list of remote nodes;

verifying the current node in response to determining the current node is not present in the first list of remote nodes;

storing the current node in the first list of remote nodes in response to successfully verifying the current node;

determining if the current node is a last node in the second list of remote nodes; and

defining, in response to the current node not being the last node in the second list of remote nodes, a next node from the second list of remote nodes as the current node.

9. The method of claim 8, further comprising allowing remote nodes in the mesh network to access (i) the first list of remote nodes and (ii) the second list of remote nodes, while a main processor of the local node is not fully operational.

10. The method of claim 8, wherein storing the current node in the first list of remote nodes comprises:

storing an internet protocol (IP) address of the current node;

storing a verification timestamp of a most recent direct contact with the current node, the verification timestamp corresponding to a time of verification; and

updating a version number and timestamp corresponding to the first list of remote nodes.

11. The method of claim 8, further comprising:

storing, on the local node, a resource information list comprising resource information corresponding to remote nodes in the mesh network; and

wherein each iteration further comprises;

storing, in the resource information list, resource information for the current node in response to successfully verifying the current node.

12. The method of claim 11, further comprising:

storing, on the local node, a local timestamp corresponding to a date the resource information list was last updated by the local node; and

wherein each iteration further comprises;

determining, on the local node, in response to determining the current node is present in the first list of remote nodes, whether the resource information for the current node stored in the resource information list is up-to-date by comparing the local timestamp to a resource timestamp stored in the resource information of the current node, wherein the resource timestamp corresponds to a date the resource information was created by the current node; and

storing, in the resource information list, replacement resource information for the current node in response to determining the resource information for the current node stored in the resource information list is not up-to-date.

13. The method of claim 8, wherein verifying the current node comprises:

contacting the current node;

providing to the current node a first mesh certificate to allow the current node to securely verify the authenticity of the local node;

receiving from the current node a second mesh certificate to allow the local node to securely verify the authenticity of the current node;

receiving from the current node a third list of remote nodes verified by the current node and storing the third list of remote nodes in the second list of remote nodes; and

storing the first list of remote nodes on the current node.

14. The method of claim 8, further comprising:

inquiring, by the local node, with a remote server external to the mesh network whether a leader position in the mesh network is available;

establishing, by the local node, a two-way communication tunnel with the remote server in response to the leader position being available;

waking, by the local node, a target node in the mesh network in response to receiving a wakeup request from the remote server over the two-way communication tunnel, the wakeup request received by the local node in response to the remote server receiving a request communication from a requestor node; and

sending, by the local node, a resource request to the target node in response to waking the target node, the resource request comprising a request to the target node to provide a resource to the requestor node.

15. One or more machine readable storage devices comprising a plurality of instructions that in response to being executed result in a computing device:

storing a first list of remote nodes in a mesh network verified by the computing device;

storing a second list of remote nodes in the mesh network not verified by the computing device; and

iterating over the second list of remote nodes, wherein each iteration comprises;

defining a current node from the second list of remote nodes;

determining if the current node is present in the first list of remote nodes;

verifying the current node in response to determining the current node is not present in the first list of remote nodes;

storing the current node in the first list of remote nodes in response to successfully verifying the current node;

determining if the current node is a last node in the second list of remote nodes; and

defining, in response to the current node not being the last node in the second list of remote nodes, a next node from the second list of remote nodes as the current node.

16. The one or more machine readable storage devices of claim 15, further comprising a plurality of instructions that in response to being executed result in the computing device allowing remote nodes in the mesh network to access (i) the first list of remote nodes and (ii) the second list of remote nodes, while a main processor of the computing device is not fully operational.

17. The one or more machine readable storage devices of claim 15, further comprising a plurality of instructions that in response to being executed result in the computing device:

storing a resource information list comprising resource information corresponding to remote nodes in the mesh network; and

wherein each iteration further comprises;

storing, in the resource information list, resource information for the current node in response to successfully verifying the current node.

18. The one or more machine readable storage devices of claim 17, further comprising a plurality of instructions that in response to being executed result in the computing device:

storing a local timestamp corresponding to a date the resource information list was last updated by the computing device; and

wherein each iteration further comprises;

determining, in response to determining the current node is present in the first list of remote nodes, whether the resource information for the current node stored in the resource information list is up-to date by comparing the local timestamp to a resource timestamp stored in the resource information of the current node, wherein the resource timestamp corresponds to a date the resource information was created by the current node; and

storing, in the resource information list, replacement resource information for the current node in response to determining the resource information for the current node stored in the resource information list is not up-to-date.

19. The one or more machine readable storage devices of claim 15, wherein verifying the current node comprises:

contacting the current node;

providing to the current node a first mesh certificate to allow the current node to securely verify the authenticity of the computing device;

receiving from the current node a second mesh certificate to allow the computing device to securely verify the authenticity of the current node;

receiving from the current node a third list of remote nodes verified by the current node and storing the third list of remote nodes in the second list of remote nodes; and

storing the first list of remote nodes on the current node.

20. The one or more machine readable storage devices of claim 15, further comprising a plurality of instructions that in response to being executed result in the computing device:

inquiring with a remote server external to the mesh network whether a leader position in the mesh network is available;

establishing a two-way communication tunnel with the remote server in response to the leader position being available;

waking a target node in the mesh network in response to receiving a wakeup request from the remote server over the two-way communication tunnel, the wakeup request received by the computing device in response to the remote server receiving a request communication from a requestor node; and

sending a resource request to the target node in response to waking the target node, the resource request comprises a request to the target node to provide a resource to the requestor node.

21. A computer system, comprising a local node in a mesh network, the local node comprising:

a local flash block;

a remote flash block; and

an operating system (OS) mesh agent to;

store a first list in the local flash block of remote nodes in the mesh network verified by the mesh agent;

store a second list in the remote flash block of remote nodes in the mesh network not verified by the mesh agent; and

iterate over the second list of remote nodes, wherein for each iteration the OS mesh agent to;

define a current node from the second list of remote nodes;

determine if the current node is present in the first list of remote nodes;

verify the current node in response to determining the current node is not present in the first list of remote nodes;

store the current node in the first list of remote nodes in response to successfully verifying the current node;

determine if the current node is a last node in the second list of remote nodes; and

define, in response to the current node not being the last node in the second list of remote nodes, a next node from the second list of remote nodes as the current node.

22. The computer system of claim 21, wherein the local node further comprises out-of-band management logic to allow remote nodes in the mesh network to access (i) the first list of remote nodes and (ii) the second list of remote nodes, while a main processor of the computer system is not fully operational.

23. The computer system of claim 21, wherein to verify the current node comprises to:

contact the current node;

provide to the current node a first mesh certificate to allow the current node to securely verify the authenticity of the local node;

receive from the current node a second mesh certificate to allow the local node to securely verify the authenticity of the current node;

receive from the current node a third list of remote nodes verified by the current node and storing the third list of remote nodes in the second list of remote nodes; and

store the first list of remote nodes on the current node.

24. The computer system of claim 21, wherein the OS mesh agent further to:

inquire with a remote server external to the mesh network whether a leader position in the mesh network is available;

establish a two-way communication tunnel with the remote server in response to the leader position being available;

wake a target node in the mesh network in response to receiving a wakeup request from the remote server over the two-way communication tunnel, the wakeup request received by the OS mesh agent in response to the remote server receiving a request communication from a requestor node; and

send a resource request to the target node in response to waking the target node, wherein the resource request comprises a request to the target node to provide a resource to the requestor node.

25. The computer system of claim 21, further comprising out-of-band management logic to, while a main processor of the computer system is not fully operational:

inquire with a remote server external to the mesh network whether a leader position in the mesh network is available;

establish a two-way communication tunnel with the remote server in response to the leader position being available;

wake a target node in the mesh network in response to receiving a wakeup request from the remote server over the two-way communication tunnel, the wakeup request received by the out-of-band management logic in response to the remote server receiving a request communication from a requestor node; and

send a resource request to the target node in response to waking the target node, wherein the resource request comprises a request to the target node to provide a resource to the requestor node.