US 12,261,749 B2
Automatically managing a mesh network based on dynamically self-configuring node devices
Ameya Pethe, Lake Saint Louis, MO (US); and Sindoora Koneru, O'Fallon, MO (US)
Assigned to MASTERCARD INTERNATIONAL INC., Purchase, NY (US)
Filed by MASTERCARD INTERNATIONAL INCORPORATED, Purchase, NY (US)
Filed on Nov. 10, 2021, as Appl. No. 17/523,056.
Claims priority of provisional application 63/111,783, filed on Nov. 10, 2020.
Prior Publication US 2022/0150154 A1, May 12, 2022
Int. Cl. H04L 41/0895 (2022.01); H04L 9/40 (2022.01); H04L 41/08 (2022.01); H04L 41/0803 (2022.01); H04L 41/0823 (2022.01); H04L 41/084 (2022.01); H04L 41/0853 (2022.01); H04L 41/0894 (2022.01); H04L 45/02 (2022.01); H04L 45/44 (2022.01); H04L 45/586 (2022.01); H04L 67/12 (2022.01); H04W 84/18 (2009.01)
CPC H04L 41/0895 (2022.05) [H04L 41/0803 (2013.01); H04L 41/0823 (2013.01); H04L 41/0846 (2013.01); H04L 41/0853 (2013.01); H04L 41/0886 (2013.01); H04L 41/0894 (2022.05); H04L 45/02 (2013.01); H04L 45/44 (2013.01); H04L 45/586 (2013.01); H04L 63/0209 (2013.01); H04W 84/18 (2013.01); H04L 67/12 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A system for configuring a mesh network of node devices for routing data, the system comprising:
at least one processor of a first node device; and
at least one memory comprising computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the at least one processor to:
based on the first node device detecting a connection to a second device, send, by the first node device, a mesh node signature of the first node device to the second device, the first node device and the second device comprising a plurality of role-based operating system (OS) configurations, each OS configuration configured to cause a device to perform a corresponding role by activating a virtualized role-based OS in a virtual computing instance (VCI) on the device, the corresponding role comprising a mesh node role, an egress node role, or a firewall node role, the mesh node signature of the first node device including an identifier of the first node device, a port to which the first node device is connected, and an indication that the first node device is configured to operate in a mesh network;
in response to receiving the mesh node signature of the first node device by the second device, send, by the second device, a mesh node signature of the second device to the first node device, the mesh node signature of the second device including an identifier of the second device, a port to which the second device is connected, and an indication that the second device is configured to operate in the mesh network;
based on receiving a mesh node signature of the second device, update, by the first node device, a mesh node signature list of the first node device to include the mesh node signature of the second device;
determine, by the first node device, that one or more mesh network requirements are satisfied based on the updated mesh node signature list, wherein the one or more mesh network requirements include data defining requirements to be satisfied by the first node device and the second device to form a mesh network;
generate, by the first node device, a mesh network configuration that includes the updated mesh node signature list, and one or more routing functions, the one or more routing functions indicating routes between node devices on which network traffic data is to be routed and a destination node device for the network traffic data;
share, by the first node device, the generated mesh network configuration with the second device, the second device being configured to forward the generated mesh network configuration to devices to which the first node device is not directly connected that are also configured to operate in a mesh network;
activate, by the second device, an inactive role-based virtualized OS on the second device to perform the corresponding role, the first node device and the second device configured to host a plurality of separate role-based virtualized OS's simultaneously, thereby causing the device to perform the corresponding plurality of roles; and
route the network traffic data to at least the second device in accordance with the generated mesh network configuration including the one or more routing functions,
wherein each node device in the mesh network is configured to synchronize any changes to the generated mesh network configuration with each other node device in the mesh network in response to a change in the configuration of a node device in the mesh network.