Lattice mesh
A system comprises an interface and a processor. The interface is configured to provide a request to join a publish group from a client or a point to point communication link of a lattice mesh; and receive a group key or a host public key. The processor is configured to determine whether a message has been received; in response to the message having been received, determine whether the message is to be sent on; in response to the message being determined not to be sent on, decode the message using the group key or the host public key; determine whether to store the message in a backfill database; in response to determining to store the message in the backfill database, store the message in the backfill database.
1. A system for a lattice mesh, comprising:
an interface configured to:
provide a request to join a publish group from a client or a point to point communication link of a lattice mesh; and
receive a group key or a host public key; and
a processor configured to:
determine whether a message has been received;
in response to a determination that the message has been received, determine whether the message is to be sent on;
in response to a determination that the message is to be sent on, send the message on;
determine whether the message is for a host, wherein the host includes a host service;
in response to a determination that the message is for the host, decode the message using the group key or the host public key;
determine whether the message is to be stored in a backfill database; and
in response to a determination that the message is to be stored in the backfill database, store the message in the backfill database.
2. The system as in claim 1 , wherein the message is encoded using the group key or the host public key in an asset database, wherein encoding the message comprises encrypting the message using the group key or signing the message using the host public key.
3. The system as in claim 2 , wherein the message is sent to another node or published to multiple nodes after encoding.
4. The system as in claim 1 , wherein the message was sent specifically to one node or published to multiple nodes.
5. The system as in claim 1 , wherein the interface and the processor belong to a hub.
6. The system as in claim 5 , wherein the hub includes a resource authority.
7. The system as in claim 6 , wherein the resource authority includes a certificate authority.
8. The system as in claim 6 , wherein the resource authority includes a key store.
9. The system as in claim 8 , wherein the key store stores keys in a hardware security module.
10. The system as in claim 6 , wherein the resource authority includes an asset database.
11. The system as in claim 6 , wherein the resource authority includes a host to claim map.
12. The system as in claim 6 , wherein the resource authority includes an asset database sharer.
13. The system as in claim 1 , wherein the host service includes a registration requestor.
14. The system as in claim 1 , wherein the host service includes a key store.
15. The system as in claim 14 , wherein the key store stores keys in a hardware security module.
16. The system as in claim 1 , wherein the host service includes an asset database.
17. The system as in claim 1 , wherein the host service includes an asset database sharer.
18. A method for a lattice mesh, comprising:
providing a request to join a publish group from a client or a point to point communication link of a lattice mesh;
receiving a group key or a host public key;
determining whether a message has been received;
in response to a determination that the message has been received, determining whether the message is to be sent on;
in response to a determination that the message is to be sent on, sending the message on;
determining whether the message is for a host, wherein the host includes a host service;
in response to a determination that the message is for the host, decoding the message using the group key or the host public key;
determining whether the message is to be stored in a backfill database; and
in response to a determination that the message is to be stored in the backfill database, storing the message in the backfill database.
19. A computer program product for a lattice mesh, the computer program product being embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:
providing a request to join a publish group from a client or a point to point communication link of a lattice mesh;
receiving a group key or a host public key;
determining whether a message has been received;
in response to a determination that the message has been received, determining whether the message is to be sent on;
in response to a determination that the message is to be sent on, sending the message on;
determining whether the message is for a host, wherein the host includes a host service;
in response to a determination that the message is for the host, decoding the message using the group key or the host public key;
determining whether the message is to be stored in a backfill database; and
in response to a determination that the message is to be stored in the backfill database, storing the message in the backfill database.