We Claim:
1. A method of creating and managing a decentralized IP-based mesh overlay network
of one or more nodes, method comprising:
receiving, by a mesh network management server, a provisioning request from at least one gateway node;
provisioning, by the mesh network management server, of license and firmware of the at least one gateway node upon authentication of the mesh network management server and the at least one gateway node;
receiving, by the mesh network management server, a request for ownership of the at least one gateway node from the at least one gateway node, wherein the ownership request includes a gateway access token of the at least one gateway node and a user access token associated with the client application;
providing, by the mesh network management server, ownership rights of the at least one gateway node to the user upon validation of the gateway access token and the user access token; and
creating, by the mesh network management server, the mesh overlay network with the at least one gateway node added to the mesh overlay network upon successful verification of the ownership rights of the at least one gateway node.
2. The method as claimed in claim 1, wherein provisioning of the license and firmware
of the at least one gateway node comprises steps of:
receiving, by the mesh network management server, a request for authentication information of the mesh network management server from the at least one gateway node;
providing, by the mesh network management server, the authentication information of the mesh network management server to the at least one gateway node;
receiving, by the mesh network management server, upon successful authentication of the mesh network management server, credential information of the at least one gateway node for authentication of the at least one gateway node,

wherein the credential information includes unique identification information of the at least one gateway node;
authenticating, by the mesh network management server, the at least one gateway node based on validation of the credential information of the at least one gateway node;
granting the license to the at least one gateway node upon successful validation;
generating, by the mesh network management server, the gateway access token in response to granting of the license;
receiving, by the mesh network management server, a request for provisioning of firmware of the at least one gateway node; and
provisioning, by the mesh network management server, of the firmware of the at least one gateway node upon verifying the firmware provisioning request.
3. The method as claimed in claim 1, wherein providing ownership rights of the at
least one gateway node comprises step of:
verifying the gateway access token and the user access token received in the ownership request, wherein the user access token is a unique identification assigned to the client application; and
assigning, upon successful verification, the at least one gateway node to the user of the client application associated with the user access token, providing ownership rights of the at least one gateway node to the user.
4. The method as claimed in claim 1, wherein creating the mesh overlay network
comprises:
receiving, by the mesh network management server, a request for adding the at least one new gateway node to the mesh overlay network, from at least one gateway node, wherein the request for adding comprises at least name of a new mesh overlay network;
verifying the ownership rights of the at least one gateway node upon receiving the request;

determining non-existence of the new mesh overlay network with corresponding name;
generating a network id corresponding to the new mesh overlay network upon successful verification of the ownership rights and determination;
requesting, a relay server coupled with the mesh network management server, to create a network management (NM) node and to generate a gateway node invite for allowing the at least one gateway node to join the new mesh overlay network;
transmitting the gateway node invite, received from the relay server, to the at least one gateway node for enabling the at least one gateway node to connect to the relay server using the gateway node invite;
creating the new mesh overlay network with the at least one gateway node added to the new mesh overlay network; and
updating network information of the new mesh overlay network including information of at least one gateway node added to the new mesh overlay network.
5. The method as claimed in claim 1, wherein creating the mesh overlay network comprises:
receiving, by the mesh network management server, a request for adding the at least one gateway node to the mesh overlay network, from the at least one gateway node, wherein the request comprises network id of an existing mesh overlay network;
verifying the ownership rights of the at least one gateway node and the mesh overlay network;
requesting the relay server for an additional gateway node invite for allowing the at least one gateway node to join the existing mesh overlay network, upon successful verification of the ownership rights;
receiving the additional gateway node invite from the relay server, via a network management (NM) node of the relay server, for enabling the at least one gateway node to join the existing mesh overlay network using the additional gateway node invite;

transmitting the additional gateway node invite to the at least one gateway node for allowing the at least one gateway node to join the existing mesh overlay network and
updating network information of the existing mesh overlay network including list of gateway nodes added to the existing mesh overlay network.
6. The method as claimed in claim 1, wherein creating the mesh overlay network
further comprises:
receiving, by the mesh network management server, a request for an invite to connect to the mesh overlay network from the client application of the at least one gateway node, wherein the request comprises at least the network id of the mesh overlay network, app access token and the user access token associated with the client application;
verifying the ownership rights to the mesh overlay network based on the user access token received in the request;
requesting the relay server for creation of a relay node and a client app proxy node invite used for connecting the at least one gateway node with a relay node, wherein the relay node is generated by the relay server in response to receiving the request for client app proxy node invite; and
transmitting the client app proxy node invite, received from the relay server, to the at least one gateway node for creation of a client app proxy node for the at least one gateway node.
7. The method as claimed in claim 6, wherein the client app node connects the client
application of the user with the client app proxy node, wherein the client app proxy
node connects a client app node with the at least one gateway node in the mesh
overlay network, wherein the relay server generates a client app node invite upon
receiving a confirmation from the at least one gateway node of successful
provisioning of the client app proxy node by the at least one gateway node using
the client app proxy node invite, wherein the relay node facilitates tunneling of
connection between the client app node and the client app proxy node.

8. The method as claimed in claim 1, further comprising:
receiving a request, for removal of the at least one new gateway node, from the at least one gateway node, wherein the request comprises name of the at least one gateway node to be removed and network id of the mesh overlay network;
verifying the ownership rights of the at least one gateway node and the mesh overlay network;
determining that the at least one gateway node exists as part of the mesh overlay network;
requesting, the relay server coupled with the mesh network management server, for removal of the at least one gateway node from the mesh overlay network based on determination; and
updating network information of the mesh overlay network including information of at least one gateway node removed from the mesh overlay network, upon successful removal of the at least one gateway node,
wherein the removal comprises deleting information of the at least one gateway node from all the gateway nodes, deleting all client app proxy nodes from the at least one gateway node removed, and disconnecting the removed gateway node from the mesh overlay network.
9. A method of creating and managing a decentralized IP-based mesh overlay network
of one or more nodes, method comprising:
transmitting, by at least one gateway node, a provisioning request to a mesh network management server;
receiving, by the at least one gateway node, a gateway access token and firmware provisioned by the mesh network management server in response to authentication of the mesh network management server and the at least one gateway node;
transmitting, by the at least one gateway node, a request for ownership from a client application of the user of the at least one gateway node to the mesh network management server, wherein the request for ownership includes a gateway access

token received from the mesh network management server, and a user access token associated with the client application;
receiving, by the at least one gateway node, confirmation of ownership rights of the at least one gateway node upon verification of the gateway access token and the user access token by the mesh network management server; and
adding, by the at least one gateway node, to one of a new and existing mesh overlay network to create the mesh overlay network based on successful verification of the ownership rights of the at least one gateway node.
10. The method as claimed in claim 9, further comprising:
requesting for a new gateway access token to the mesh network management server, wherein the request comprises at least a gateway refresh token of the at least one gateway node received along with the gateway access token from the mesh network management server; and
receiving the new gateway access token based on validation of the gateway refresh token by the mesh network management server.
11. The method as claimed in claim 9, further comprising:
receiving, by at least one gateway node, a request for addition of one or more resources from the client application, wherein the mesh overlay network is a collection of at least one gateway node and one or more resources coupled with each gateway node, wherein each resource is a capable of providing one or more functions associated with the resource;
adding, by the at least one gateway node, one or more resources to at least one gateway node with each added resource assigned with a unique identifier;
transmitting, by the at least one gateway node, resource information of the at least one resource added to the at least one gateway node to all other gateway nodes of the mesh overlay network, wherein the resource information includes the unique identifier of the at least one added resource; and
updating, by at the least one gateway node, Access Control List (ACL) information of the at least one gateway node of the mesh overlay network, wherein the ACL information comprises a list of resources of the mesh overlay network and

one or more permissions assigned to manage functions of the one or more resources.
12. The method as claimed in claim 9, further comprising:
receiving, by the at least one gateway node, a request for removal of one or more resources from the client application associated with user of at least one gateway node of the mesh overlay network, wherein the request comprises unique identifier of the one or more resources that are to be removed;
removing, by the at least one gateway node, the one or more resources from the at least one gateway node by disconnecting the one or more resources from the at least one gateway node and deleting the unique identifier, assigned to the one or more removed resources, from the ACL information of the at least one gateway node; and
transmitting, by the at least one gateway node, a request for deletion of resource information of the one or more removed resources, to all other gateway nodes of the mesh overlay network, wherein the resource information includes the unique identifier of the one or more removed resources..
13. The method as claimed in claim 9, wherein adding the at least one gateway node to
a new mesh overlay network comprises steps of:
sending a request for adding the at least one gateway node to a new mesh overlay network from the client application of user of the at least one gateway node, wherein the request for adding comprises at least name of the mesh overlay network;
receiving a gateway node invite for connecting with a relay server, upon creation of a network management (NM) node by the relay server;
connecting to the relay server using the gateway node invite;
receiving a client app proxy node invite from the relay server for creation of a client app proxy node at the at least one gateway node, wherein the relay server creates a relay node and the client app proxy node invite to enable the owner of the at least one gateway node to use a client application to connect to the mesh overlay; and

creating and connecting to the relay server, the client app proxy node using the client app proxy node invite, wherein the client app proxy node connects the client application of the user and the at least one gateway node; and
creating an access control list (ACL) for the client app proxy node, wherein the ACL comprises a list of resources of the mesh overlay network and one or more permissions assigned to manage functions of the one or more resources.
14. The method as claimed in claim 9, wherein adding the at least one gateway node to
an existing mesh overlay network comprises steps of:
sending a request for adding the at least one gateway node to the existing mesh overlay network from the client application of user of the at least one gateway node, wherein the request for adding comprises at least network id of an existing mesh overlay network;
receiving an additional gateway node invite from the relay server, via a network management (NM) node of the relay server; and
connecting to the existing mesh overlay network using the additional gateway node invite received from the relay server.
15. A system for creating and managing a decentralized IP-based mesh overlay network
of one or more nodes, system comprising:
a mesh network management server, comprising:
at least a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
receive a provisioning request from at least one gateway node;
provision license and firmware of the at least one gateway node upon authentication of the mesh network management server and the at least one gateway node;
receive a request for ownership of the at least one gateway node from the at least one gateway node, wherein the ownership request includes a gateway access token of the at least one gateway node and a user access token associated with the client application;

provide ownership rights of the at least one gateway node to the user upon validation of the gateway access token and the user access token; and
create the mesh overlay network with the at least one gateway node added to the mesh overlay network upon successful verification of the ownership rights of the at least one gateway node.
16. The system as claimed in claim 15, wherein the processor is configured to provision
the license and firmware of the at least one gateway node by performing steps of:
receiving a request for authentication information of the mesh network management server from the at least one gateway node;
providing the authentication information of the mesh network management server to the at least one gateway node;
receiving, upon successful authentication of the mesh network management server, credential information of the at least one gateway node for authentication of the at least one gateway node, wherein the credential information includes unique identification information of the at least one gateway node;
authenticating, the at least one gateway node based on validation of the credential information of the at least one gateway node;
granting the license to the at least one gateway node upon successful validation;
generating the gateway access token in response to granting of the license;
receiving a request for provisioning of firmware of the at least one gateway node; and
provisioning the firmware of the at least one gateway node upon verifying the firmware provisioning request.
17. The system as claimed in claim 16, wherein the processor is further configured to:
receive a request for a new gateway access token from the at least one gateway node provisioned by the mesh network management server; and
grant the new gateway access token in response to receiving the request.

18. The system as claimed in claim 15, wherein the processor provides ownership rights
to the at least one gateway node by performing steps comprising:
verifying the gateway access token and the user access token received in the ownership request, wherein the user access token is a unique identification assigned to the client application; and
assigning, upon successful verification, the ownership rights of the at least one gateway node to the user.
19. The system as claimed in claim 15, wherein the processor creates the mesh overlay
network by:
receiving a request for adding the at least one new gateway node to the mesh overlay network, from the at least one gateway node, wherein the request for adding comprises at least name of a new mesh overlay network;
verifying the ownership rights of the at least one gateway node upon receiving the request;
determining non-existence of the new mesh overlay network with corresponding name;
generating a network id corresponding to the new mesh overlay network upon successful verification of the ownership rights and determination;
requesting, a relay server coupled with the mesh network management server, to create a network management (NM) node and to generate a gateway node invite for allowing the at least one gateway node to join the new mesh overlay network;
transmitting the first gateway node invite, received from the relay server, to the at least one gateway node for enabling the at least one gateway node to connect to the relay server using the gateway node invite;
creating the new mesh overlay network with the at least one gateway node added to the new mesh overlay network upon successful connection of the at least one gateway node to the relay server; and
updating network information of the new mesh overlay network including information of at least one gateway node added to the new mesh overlay network.

20. The system as claimed in claim 19, wherein the processor creates the mesh overlay
network by steps further comprising of:
receiving a request for an invite to connect to the mesh overlay network from the client application of the at least one gateway node, wherein the request comprises at least the network id of the mesh overlay network, the app access token and the user access token associated with the client application;
verifying the ownership rights to the at least one gateway node based on the user access token received in the request;
requesting the relay server for creation of a relay node and a client app proxy node invite used for connecting the at least one gateway node with a relay node, wherein the relay node is generated by the relay server in response to receiving the request for client app proxy node invite; and
transmitting the client app proxy node invite, received from the relay server, to the at least one gateway node for creation of a client app proxy node for the at least one gateway node.
21. The system as claimed in claim 20, wherein the client app node connects the client application of the user with the client app proxy node, wherein the client app proxy node connects a client app node with the at least one gateway node in the mesh overlay network, wherein the relay server generates a client app node invite upon creation of the client app proxy node by the at least one gateway node using the client app proxy node invite, wherein the relay node facilitates tunneling of connection between the client app node and the client app proxy node.
22. The system as claimed in claim 15, wherein the processor creates the mesh overlay network by steps further comprising of:
receiving a request for adding the at least one gateway node to the mesh overlay network, from the at least one gateway node, wherein the request comprises network id of an existing mesh overlay network;
verifying the ownership rights of the at least one gateway node and the mesh overlay network;

requesting the relay server for an additional gateway node invite for allowing the at least one gateway node to join the existing mesh overlay network, upon successful verification of the ownership rights;
receiving the additional gateway node invite from the relay server, via a network management (NM) node of the relay server, for enabling the at least one gateway node to join the existing mesh overlay network using the additional gateway node invite;
transmitting the additional gateway node invite to the at least one gateway node for allowing the at least one gateway node to join the existing mesh overlay network and
updating network information of the existing mesh overlay network including list of gateway nodes added to the existing mesh overlay network.
23. The system as claimed in claim 15, wherein the processor is further configured to:
receive a request, for removal of the at least one new gateway node, from the at least one gateway node, wherein the request comprises name of the at least one gateway node to be removed and network id of the mesh overlay network;
verify the ownership rights of the at least one gateway node and the mesh overlay network;
determine that the at least one gateway node exists as part of the mesh overlay network;
request, the relay server coupled with the mesh network management server, for removal of the at least one gateway node from the mesh overlay network based on determination; and
update network information of the mesh overlay network including information of at least one gateway node removed from the mesh overlay network, upon successful removal of the at least one gateway node,
wherein the removal comprises deleting information of the at least one gateway node from all gateway nodes, deleting all client app proxy nodes from the at least one gateway node removed, and disconnecting the removed gateway node from the mesh overlay network.

24. A system for creating and managing a decentralized IP-based mesh overlay network
of one or more nodes, system comprising:
at least one gateway node, comprising at least a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
transmit a provisioning request to a mesh network management server;
receive a gateway access token and firmware provisioned by the mesh network management server in response to authentication of the mesh network management server and the at least one gateway node;
transmit a request for ownership from a client application of the user of the at least one gateway node to the mesh network management server, wherein the request for ownership includes a gateway access token received from the mesh network management server, and a user access token associated with the client application;
receive confirmation of ownership rights of the at least one gateway node upon verification of the gateway access token and the user access token by the mesh network management server; and
add to one of a new and existing mesh overlay network to create the mesh overlay network based on successful verification of the ownership rights of the at least one gateway node.
25. The system as claimed in claim 24, wherein the processor is further configured to:
request for a new gateway access token to the mesh network management server, wherein the request comprises at least a gateway refresh token of the at least one gateway node received along with the gateway access token from the mesh network management server; and
receive the new gateway access token based on validation of the gateway refresh token by the mesh network management server.
26. The system as claimed in claim 24, wherein the processor is further configured to:

receive a request for addition of one or more resources from the client application, wherein the mesh overlay network is a collection of at least one gateway node and one or more resources coupled with each gateway node, wherein each resource is a capable of providing one or more functions associated with the resource;
add one or more resources to at least one gateway node with each added resource assigned with a unique identifier;
transmit resource information of the at least one resource added to the at least one gateway node to all other gateway nodes of the mesh overlay network, wherein the resource information includes the unique identifier of the at least one added resource; and
update Access Control List (ACL) information of the at least one gateway node of the mesh overlay network, wherein the ACL information comprises a list of resources of the mesh overlay network and one or more permissions assigned to manage functions of the one or more resources.
27. The system as claimed in claim 24, wherein the processor is further configured to:
receive a request for removal of one or more resources from the client application associated with user of at least one gateway node of the mesh overlay network, wherein the request comprises unique identifier of the one or more resources that are to be removed;
remove the one or more resources from the at least one gateway node by disconnecting the one or more resources from the at least one gateway node and deleting the unique identifier, assigned to the one or more removed resources, from the ACL information of the at least one gateway node; and
transmit a request for deletion of resource information of the one or more removed resources, to all other gateway nodes of the mesh overlay network, wherein the resource information includes the unique identifier of the one or more removed resources.
28. The system as claimed in claim 24, wherein the processor enables addition of the
at least one gateway node to a new mesh overlay network by steps comprising of:

sending a request for adding the at least one gateway node to the new mesh overlay network from the client application of user of the at least one gateway node, wherein the request for adding comprises at least name of the mesh overlay network;
receiving a gateway node invite for connecting with a relay server, upon creation of a network management (NM) node by the relay server;
connecting to the relay server using the first gateway node invite;
receiving a client app proxy node invite from the relay server for creation of a client app proxy node at the at least one gateway node, wherein the relay server creates a relay node and the client app proxy node invite to enable the at least one gateway node to get added to the mesh overlay network; and
creating the client app proxy node using the client app proxy node invite, wherein the client app proxy node connects the client application of the user and the at least one gateway node.
. The system as claimed in claim 24, wherein the processor enables addition of the at least one gateway node to the existing mesh overlay network by steps comprising of:
sending a request for adding the at least one gateway node to the mesh overlay network from the client application of user of the at least one gateway node, wherein the request for adding comprises at least network id of an existing mesh overlay network;
receiving an additional gateway node invite from the relay server, via a network management (NM) node of the relay server; and
connecting to the existing mesh overlay network using the additional gateway node invite received from the relay server.
. A method of creating and managing a decentralized IP-based mesh overlay network of one or more nodes, method comprising:

receiving, by a relay server, a request for a network management (NM) node for the mesh overlay network from the management server, wherein the request comprises at least network name and network ID of the mesh overlay network;
creating, by the relay server, the NM node and a gateway node invite for the one of the gateway nodes joining the mesh overlay network; and
transmitting, by the relay server, the gateway node invite to the management server for creating the mesh network and adding the one of gateway nodes to the mesh network.
31. The method as claimed in claim 30, wherein the NM node manages the functions of the gateway nodes associated with the mesh overlay network, wherein the gateway node invite is an invite used by the one of the gateway nodes to join the mesh overlay network.
32. The method as claimed in claim 30, further comprising:
receiving a request from a client device, connected to the one of the gateway nodes of the mesh network, to access the resources;
determining if the client device require remote connectivity access permission to connect to the resources;
creating a relay node and a client app proxy node invite upon determination that the client device require remote connectivity access permission;
transmitting the client app proxy node invite to one of the gateway nodes for creation of a client app proxy node, wherein the client app proxy node enables the client application to connect with the one of the gateway nodes;
receiving a confirmation message indicating creation of client app proxy node from the one of the gateway nodes;
creating a client app node invite for creation of a client app node, wherein the client app node is an instance of the client application created to act as connecting node between the client application and the client app proxy node; and
transmitting the client app proxy node invite to the client device via the management server for creation of client app node that enables access to the resources by the client device.

33. A system for creating and managing a decentralized IP-based mesh overlay network
of one or more nodes, system comprising:
a relay server, comprising:
at least a processor, and a memory communicatively coupled to the processor, wherein the memory stores processor-executable instructions, which, on execution, cause the processor to:
receive a request for a network management (NM) node for the mesh overlay network from the management server, wherein the request comprises at least network name and network ID of the mesh overlay network;
create the NM node and a gateway node invite for the one of the gateway nodes joining the mesh overlay network; and
transmit the gateway node invite to the management server for creating the mesh network and adding the one of gateway nodes to the mesh network.
34. The system as claimed in claim 33, wherein the processor enables the NM node to manage the functions of the gateway nodes associated with the mesh overlay network, wherein the gateway node invite is an invite used by the one of the gateway nodes to join the mesh overlay network.
35. The system as claimed in claim 33, wherein the processor is further configured to performs steps comprising of:
receiving a request from a client device, connected to the one of the gateway nodes of the mesh network, to access the resources;
determining if the client device require remote connectivity access permission to connect to the resources;
creating a relay node and a client app proxy node invite upon determination that the client device require remote connectivity access permission;

transmitting the client app proxy node invite to one of the gateway nodes for creation of a client app proxy node, wherein the client app proxy node enables the client application to connect with the one of the gateway nodes;
receiving a confirmation message indicating creation of client app proxy node from the one of the gateway nodes;
creating a client app node invite for creation of a client app node, wherein the client app node is an instance of the client application created to act as connecting node between the client application and the client app proxy node; and
transmitting the client app proxy node invite to the client device via the management server for creation of client app node that enables access to the resources by the client device.
36. A method of enabling synchronization of one or more gateway nodes in a mesh
overlay network, method comprising:
detecting, by the mesh overlay network, at least one of events including addition/connection/reconnection of a new gateway node to the mesh overlay network, removal of one of the gateway nodes from the mesh overlay network and addition/removal of one or more resources connected to one of the gateway nodes in the mesh overlay network; and
updating, by the mesh overlay network, one or more of network data and resource data based on at least one event detected, wherein the network data is associated with the one or more gateway nodes of the mesh overlay network, and the resource data is associated with the one or more resources connected to the one or more gateway nodes in the mesh overlay network.
37. The method as claimed in claim 36, wherein the network data comprises network
name, network ID, gateway ID assigned to the gateway nodes and Access Control
List (ACL) information, wherein the ACL comprises a list of resources of the mesh
overlay network and one or more permissions assigned to manage functions of the
one or more resources.

38. The method as claimed in claim 36, wherein the resource data comprises list of resources, user access list and capabilities of each of the resources as per the user access list.
39. The method as claimed in claim 36, wherein step of updating one or more of network data and resource data if the at least one detected event is addition/connection/reconnection of the new gateway node to the mesh overlay network, comprising steps of:
receiving and storing the network data of the new gateway node and resource data of the one or more resources connected to the new gateway node;
updating the ACL of the one or more gateway nodes of the mesh overlay network; and
transmitting the network data and the resource data of all the gateway nodes of the mesh overlay network to the new gateway node for updation of network data, resource data and ACL of the new gateway node.
40. The method as claimed in claim 36, wherein step of updating one or more of
network data and resource data if the at least one detected event is removal of one
of the gateway nodes from the mesh overlay network, comprising steps of:
transmitting a request for gateway cleanup to one of the gateway nodes to be removed from the mesh overlay network;
receiving a cleanup acknowledgement from the one of the gateway nodes to be removed upon deletion of network data, resource data, ACL, all client app proxy nodes stored at the one of the gateway nodes to be removed; and
deleting the network data, resource data and one or more resources connected to the removed gateway node from the ACL of each gateway node in the mesh network.
41. The method as claimed in claim 36, wherein step of updating one or more of
network data and resource data if the at least one detected event is addition/removal
of one or more resources connected to one of the gateway nodes in the mesh overlay
network, comprising steps of:

receiving updated resource data from one of the gateway nodes;
enabling update of resource data and ACL at the one of the gateway nodes; and
updating resource data and ACL of each of the gateway nodes in the mesh overlay network.