Method And System For Managing Access To A Resource In A Decentralized Peer To Peer Network

Elear Solutions Tech Private Limited
Granted App No 202044011976 Patent 383538 Communication

Patent information

IP India · live record
Application number
202044011976
Filing date
19 March 2020
Status
Granted
Legal status
Inforce
Publication number
41/2020
Publication type
INA
Invention field
Communication
Patent number
383538
Grant date
02 December 2021
Next renewal due
19 March 2026Overdue

Abstract

Embodiments of the present disclosure relate to method and a system for managing a decentralized access to a resource. A user of a client device having a third-party application installed therein request to join the mesh network based on invite received from the owner of the IoT gateway. The mesh network comprises one or more IoT gateway. One gateway is identified based on the topology of the client device, and an optimal connection between the client device and the identified gateway is determined. The third-party application may send a resource access request for accessing a resource of the mesh network and access the requested resource through the optimal connection route thus determined. Thus, the disclosure enables a peer-to-peer mesh network infrastructure that allows secure access to the resource by a third-party application without using a cloud server to route the resource access request from the client device to the gateway.

Applicants

1
India
ELEAR SOLUTIONS TECH PRIVATE LIMITED 8-2-573, Road no. 7, Banjara Hills, Hyderabad, Telangana, India

Inventors

3
India
Manav Kumar MehtaApartment #101, Romanesque Apartments, Lane #1, Chikoti Gardens, Begumpet, Hyderabad, Telangana, 500016 India
India
Narendra Kumar AgarwalFlat # 210, 99 Parc, Neknampur, Manikonda Hyderabad, Telangana, 500089, India
India
Ashish BajajHouse #99, Cheers, Road #7, Banjara Hills, Hyderabad, Telangana, 500034, India

Specification

Show full textCollapse

A method of managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, method comprising: receiving, by a relay node, a request, for accessing one or more resources in the mesh overlay network, from a cliënt application of a cliënt device associated with user, wherein the mesh overlay network that comprises one or more gateway nodes, and the one or more resources connected to each of the one or more gateway nodes; determining, by the relay node, at least one optimal connection route between the cliënt device and each of the one or more gateway nodes of the mesh overlay network based on network topoiogy of the cliënt device; identifying, by the relay node, at least one preferred gateway node based on the at least one optimal connection route thus determined; and establishing, by the relay node, a connection, between the cliënt device and the at least one identified gateway node, to enable the cliënt application to access the one or more resources connected with the at least one identified gateway node. The method as claimed in claim 1, wherein determining the at least one optimal connection route comprising steps of: retrieving, by the relay node, a topology graph that comprises a list of connection routes between the cliënt device and the each of the one or more gateway nodes; and determining, by the relay node, the at least one optimal route in the topology graph for the cliënt device to connect with the one or more gateway nodes based on one or more parameters including proximity and cost between the cliënt device and the one or more gateway nodes; and. providing a list of preferred gateway nodes associated with the at least one optimal route thus determined. The method as claimed in claim 1, wherein the at least one gateway node is a routing node configured to connect the third-party app of the cliënt device with the

one or more resources of the mesh overlay network, wherein the gateway node is at least one of a physical gateway node, and a virtual gateway node. 4. The method as claimed in claim 1, wherein the relay node is provided with a static Internet Protocol (IP) address and is configured to exchange dynamic IP addresses of the cliënt device and the at least one identified gateway node therebetween to establish a peer-to-peer connection between the cliënt device and the at least one gateway node in the mesh overlay network. 5. The method as claimed in claim 1, wherein the relay node is configured to establish a connection between the cliënt device and the at least one identified gateway node in the mesh overlay network through the relay node if the peer-to-peer connection is not established. 6. The method as claimed in claim 1, wherein enabling accessing of the one or more resources in the mesh overlay network by: mapping a plurality of application access permissions allocated to the cliënt application with a list of functions provided by the one or more resources; and allowing the cliënt application to avail the list of functions mapping with the application access permissions. 7. A method of managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, comprising: receiving, by a mesh network management server (MNMS), a request for a list of users in the mesh overlay network, firom a cliënt application of a cliënt device of owner of at least one gateway node in the mesh overlay network, wherein the request comprises at least network ID and app access token associated with the cliënt application; providing, by the MNMS, the list of users to the cliënt application upon verifying the network ID and the app access token received in the request; receiving, by the MNMS, a request from the cliënt application, for adding a new user to the mesh overlay network, wherein the request for adding comprises user data of the new user including at least the network ID, user ID, user role and a

resource access list, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the new user; and adding, by the MNMS, the new user to the mesh overlay network upon successful verification of the new user based on the user data received in the request. 8. The method as claimed in claim 7, further comprising receiving a request for cliënt application to join the mesh overlay network, by: receiving, by the MNMS, a request from the cliënt application for joining the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application; transmitting, by the MNMS, a request to the relay server, for connecting with the relay node and with the one or more gateway nodes, upon verifying the network ID and the app access token received in the request; receiving, by the MNMS, a cliënt app node invite from the relay server upon creation of the relay node and connecting the relay node with the one or more gateway nodes using a cliënt app proxy node created at the one or more gateway nodes; and transmitting, by the MNMS, the cliënt app node invite to the cliënt application for creation of a cliënt app node for the cliënt application and enabling the cliënt application to connect with the relay node and the one or more gateway nodes using the cliënt app node invite for joining the mesh overlay network. 9. The method as claimed in claim 7, further comprising editing resource authorizations for the at least one user, by: receiving, by the MNMS, a request for list of users in the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application; providing, by the MNMS, the list of users to the cliënt application upon verifying the network ID and the app access token received in the request;

receiving, by the MNMS, a request from the cliënt application, for updating the resource authorizations of the user, wherein the request for updating comprises user data including at least the app access token, network ID, user ID, user role and a resource access list that is obtained by the cliënt application connected to the mesh overlay network, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the cliënt application; and transmitting, by the MNMS, the request for updating the resource authorizations to the relay server, wherein the request for updating comprises user data including at least the app access token, network ID, user ID, user role and a resource access list that is obtained by the cliënt application connected to the mesh overlay network, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the cliënt application; and updating, by the MNMS, the resource access list for the user and Access Control List (ACL) information of the at least one gateway node of the mesh overlay network on receiving a confirmation message from the relay server based on the user data, wherein the ACL information comprises a list of resources of the mesh overlay network and one or more application access permissions assigned to manage functions of the one or more resources. 10. The method as claimed in claim 7, further comprising removing at least one user from the mesh overlay network, by: receiving, by the MNMS, a request for list of mesh overlay networks of the cliënt device application, wherein the request comprises at least app access token associated with the cliënt application; providing, by the MNMS, the list of mesh overlay networks to the cliënt application upon verifying the app access token received in the request; receiving, by the MNMS, a request for list of users in the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application;

providing, by the MNMS, the list of users to the cliënt application upon verifying the network ID and the app access token received in the request; receiving, by the MNMS, a request for removing at least one user from the mesh overlay network, wherein the request comprises at least the user ID, the network ID and the app access token associated with the cliënt application; transmitting, by the MNMS, the request for removing the at least one user from the mesh overlay network to the relay server, upon validating the app access token received in the request; deleting, by the MNMS, the user from the mesh overlay network on receiving a confirmation message from the relay server; and transmitting a further confirmation message to the cliënt application upon successful deletion of the user by the MNMS. 11. A method of managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, comprising: receiving, by a relay server, a request for connecting a relay node with the one or more gateway nodes, wherein the request comprises at least network ID, user ID, user role, cliënt application ID, an application access list and a resource access list; generating, by the relay server, the relay node for the cliënt application for the network ID and user ID, and a gateway node invite for connecting the one or more gateway nodes with the relay node; receiving, by the relay server, a confirmation message indicative of successful creation of a cliënt app proxy node at the one or more gateway nodes created upon receiving the gateway node invite; and generating, by the relay server, a cliënt app node invite for enabling the cliënt application to join the mesh overlay network on receiving the confirmation message. 12. The method as claimed in claim 11, further comprising removing at least one user from the mesh overlay network, by:

receiving, by the relay server, a request to remove at least one user from the mesh overlay network, wherein the request comprises at least network ID and the user ID associated with the user to be removed; deleting, by the relay server, one or more cliënt app nodes on the relay server corresponding to the user having user ID and for the mesh overlay network having network ID; transmitting, by the relay server, a request to remove all cliënt app nodes and cliënt app proxy nodes for the user having the user ID and for the mesh overlay network having network ID; and transmitting, by the relay server, a confirmation message to the MNMS to delete the user from the mesh overlay network. 13. The method as claimed in claim 11, further comprising uninstalling the cliënt application from the mesh overlay network, by receiving, by the relay server, a request for uninstalling one or more cliënt applications from the mesh overlay network, wherein the request comprises at least the user ID and the cliënt application ID; verifying, by the relay server, the request based on determination of inactive time period of the one or more cliënt applications in the mesh overlay network; and removing, by the relay server, the relay node corresponding to the one or more cliënt applications based on determination. 14. A system for managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, system comprising: a relay 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: receive a request, for accessing one or more resources in the mesh overlay network, from a cliënt application of a cliënt device associated with user, wherein the mesh overlay network that comprises one or more gateway nodes, and the one or more resources connected to each of the one or more gateway nodes;

determine at least one optimal connection route between the cliënt device and each of the one or more gateway nodes of the mesh overlay network based on network topoiogy of the cliënt device; identify at least one preferred gateway node based on the at least one optimal connection route thus determined; and establish a connection, between the cliënt device and the at least one identified gateway node, to enable the cliënt application to access the one or more resources connected with the at least one identified gateway node. 15. The system as claimed in claim 14, wherein relay node determines the at least one optimal connection route by steps of: retrieving a topology graph that comprises a list of connection routes between the cliënt device and the each of the one or more gateway nodes; and determining the at least one optimal route in the topology graph for the cliënt device to connect with the one or more gateway nodes based on one or more parameters including proximity and cost between the cliënt device and the one or more gateway nodes; and. providing a list of preferred gateway nodes associated with the at least one optimal route thus determined. 16. The system as claimed in claim 14, wherein the at least one gateway node is a routing node configured to connect the third-party app of the cliënt device with the one or more resources of the mesh overlay network, wherein the gateway node is at least one of a physical gateway node, and a virtual gateway node. 17. The system as claimed in claim 14, wherein the relay node is provided with a static Internet Protocol (IP) address and is configured to exchange dynamic IP addresses of the cliënt device and the at least one identified gateway node therebetween to establish a peer-to-peer connection between the cliënt device and the at least one gateway node in the mesh overlay network. 18. The system as claimed in claim 14, wherein the relay node is configured to establish a connection between the cliënt device and the at least one identified gateway node

in the mesh overlay network through the relay node if the peer-to-peer connection is not established. 19. The system as claimed in claim 14, wherein the relay node enables accessing of the one or more resources in the mesh overlay network by: mapping a plurality of application access permissions allocated to the cliënt application with a list of functions provided by the one or more resources; and allowing the cliënt application to avail the list of functions mapping with the application access permissions. 20. A system for managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, comprising: a mesh network management server (MNMS) 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 list of users in the mesh overlay network, firom a cliënt application of a cliënt device of owner of at least one gateway node in the mesh overlay network, wherein the request comprises at least network ID and app access token associated with the cliënt application; provide the list of users to the cliënt application upon verifying the network ID and the app access token received in the request; receive a request from the cliënt application, for adding a new user to the mesh overlay network, wherein the request for adding comprises user data of the new user including at least the network ID, user ID, user role and a resource access list, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the new user; and add the new user to the mesh overlay network upon successful verification of the new user based on the user data received in the request. 21. The system as claimed in claim 20, wherein the MNMS is further configured to receive a request for cliënt application to join the mesh overlay network, by:

receiving a request from the cliënt application for joining the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application; transmitting a request to the relay server, for connecting with the relay node and with the one or more gateway nodes, upon verifying the network ID and the app access token received in the request; receiving a cliënt app node invite from the relay server upon creation of the relay node and connecting the relay node with the one or more gateway nodes using a cliënt app proxy node created at the one or more gateway nodes; and transmitting the cliënt app node invite to the cliënt application for creation of a cliënt app node for the cliënt application and enabling the cliënt application to connect with the relay node and the one or more gateway nodes using the cliënt app node invite for joining the mesh overlay network. 22. The system as claimed in claim 20, wherein the MNMS is further configured to edit resource authorizations for the at least one user, by: receiving a request for list of users in the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application; providing the list of users to the cliënt application upon verifying the network ID and the app access token received in the request; receiving a request from the cliënt application, for updating the resource authorizations of the user, wherein the request for updating comprises user data including at least the app access token, network ID, user ID, user role and a resource access list that is obtained by the cliënt application connected to the mesh overlay network, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the cliënt application; and transmitting the request for updating the resource authorizations to the relay server, wherein the request for updating comprises user data including at least the app access token, network ID, user ID, user role and a resource access list that is

obtained by the cliënt application connected to the mesh overlay network, wherein the resource access list comprises a list of the one or more resources of the mesh overlay network that can be accessed by the cliënt application; and updating the resource access list for the user and Access Control List (ACL) information of the at least one gateway node of the mesh overlay network on receiving a confirmation message from the relay server based on the user data, wherein the ACL information comprises a list of resources of the mesh overlay network and one or more application access permissions assigned to manage functions of the one or more resources. 23. The system as claimed in claim 20, wherein the MNMS is further configured to remove at least one user from the mesh overlay network, by: receiving a request for list of mesh overlay networks of the cliënt device application, wherein the request comprises at least app access token associated with the cliënt application; providing the list of mesh overlay networks to the cliënt application upon verifying the app access token received in the request; receiving a request for list of users in the mesh overlay network from the cliënt device application, wherein the request comprises at least network ID and app access token associated with the cliënt application; providing the list of users to the cliënt application upon verifying the network ID and the app access token received in the request; receiving a request for removing at least one user from the mesh overlay network, wherein the request comprises at least the user ID, the network ID and the app access token associated with the cliënt application; transmitting the request for removing the at least one user from the mesh overlay network to the relay server, upon validating the app access token received in the request; deleting the user from the mesh overlay network on receiving a confirmation message from the relay server; and

transmitting a further confirmation message to the cliënt application upon successful deletion of the user by the MNMS. 24. A system for managing a decentralized access to a resource in an IP-based mesh overlay network of one or more nodes, 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 connecting a relay node with the one or more gateway nodes, wherein the request comprises at least network ID, user ID, user role, cliënt application ID, an application access list and a resource access list; generate the relay node for the cliënt application for the network ID and user ID, and a gateway node invite for connecting the one or more gateway nodes with the relay node; receive a confirmation message indicative of successful creation of a cliënt app proxy node at the one or more gateway nodes created upon receiving the gateway node invite; and generate a cliënt app node invite for enabling the cliënt application to join the mesh overlay network on receiving the confirmation message. 25. The system as claimed in claim 24, wherein the relay server is further configured to remove at least one user firom the mesh overlay network, by: receiving a request to remove at least one user from the mesh overlay network, wherein the request comprises at least network ID and the user ID associated with the user to be removed; deleting one or more cliënt app nodes on the relay server corresponding to the user having user ID and for the mesh overlay network having network ID; transmitting a request to remove all cliënt app nodes and cliënt app proxy nodes for the user having the user ID and for the mesh overlay network having network ID; and transmitting a confirmation message to the MNMS to delete the user from the mesh overlay network.

26. The system as claimed in claim 24, wherein the relay server is further configured to uninstall the cliënt application from the mesh overlay network, by receiving a request for uninstalling one or more cliënt applications from the mesh overlay network, wherein the request comprises at least the user ID and the cliënt application ID; verifying the request based on determination of inactive time period of the one or more cliënt applications in the mesh overlay network; and removing the relay node corresponding to the one or more cliënt applications based on determination.

Documents

Sign in to open
Orders
Section 15Controller: SRINIVASARAO REESU 27 Oct 2021
Section 15Controller: SRINIVASARAO REESU 02 Dec 2021
Application documents
1 202044011976-US 62828003-DASCODE-3886 [19-03-2020].pdf 19 Mar 2020
2 202044011976-STATEMENT OF UNDERTAKING (FORM 3) [19-03-2020(online)].pdf 19 Mar 2020
3 202044011976-FORM FOR STARTUP [19-03-2020(online)].pdf 19 Mar 2020
4 202044011976-FORM FOR SMALL ENTITY(FORM-28) [19-03-2020(online)].pdf 19 Mar 2020
5 202044011976-FORM 1 [19-03-2020(online)].pdf 19 Mar 2020
6 202044011976-FIGURE OF ABSTRACT [19-03-2020(online)].pdf 19 Mar 2020
7 202044011976-EVIDENCE FOR REGISTRATION UNDER SSI(FORM-28) [19-03-2020(online)].pdf 19 Mar 2020
8 202044011976-EVIDENCE FOR REGISTRATION UNDER SSI [19-03-2020(online)].pdf 19 Mar 2020
9 202044011976-DRAWINGS [19-03-2020(online)].pdf 19 Mar 2020
10 202044011976-DECLARATION OF INVENTORSHIP (FORM 5) [19-03-2020(online)].pdf 19 Mar 2020
11 202044011976-COMPLETE SPECIFICATION [19-03-2020(online)].pdf 19 Mar 2020
12 202044011976-Proof of Right [19-06-2020(online)].pdf 19 Jun 2020
13 202044011976-FORM-26 [19-06-2020(online)].pdf 19 Jun 2020
14 202044011976-STARTUP [05-11-2020(online)].pdf 05 Nov 2020
15 202044011976-FORM28 [05-11-2020(online)].pdf 05 Nov 2020
16 202044011976-FORM 18A [05-11-2020(online)].pdf 05 Nov 2020
17 202044011976-FORM 3 [23-06-2021(online)].pdf 23 Jun 2021
18 202044011976-FER_SER_REPLY [23-06-2021(online)].pdf 23 Jun 2021
19 202044011976-CLAIMS [23-06-2021(online)].pdf 23 Jun 2021
20 202044011976-Correspondence to notify the Controller [02-09-2021(online)].pdf 02 Sep 2021
21 202044011976-Written submissions and relevant documents [22-09-2021(online)].pdf 22 Sep 2021
22 202044011976-PETITION UNDER RULE 137 [22-09-2021(online)].pdf 22 Sep 2021
23 202044011976-FORM 3 [22-09-2021(online)].pdf 22 Sep 2021
24 202044011976-US(14)-HearingNotice-(HearingDate-08-09-2021).pdf 18 Oct 2021
25 202044011976-FER.pdf 18 Oct 2021
26 202044011976-US(14)-HearingNotice-(HearingDate-08-11-2021).pdf 27 Oct 2021
27 202044011976-Correspondence to notify the Controller [03-11-2021(online)].pdf 03 Nov 2021
28 202044011976-Written submissions and relevant documents [19-11-2021(online)].pdf 19 Nov 2021
29 202044011976-Correspondence-Letter [19-11-2021(online)].pdf 19 Nov 2021
30 202044011976-PatentCertificate02-12-2021.pdf 02 Dec 2021
31 202044011976-IntimationOfGrant02-12-2021.pdf 02 Dec 2021
Search strategy
1search1976E_04-12-2020.pdf

ERegister / renewals

Inforce
3rd Renewed 04 Jan 2022 Period 19 Mar 2022 – 19 Mar 2023 · CBR 243 · Certificate 339 ₹800
4th Renewed 03 Jan 2023 Period 19 Mar 2023 – 19 Mar 2024 · CBR 271 · Certificate 591 ₹800
5th Renewed 11 Mar 2024 Period 19 Mar 2024 – 19 Mar 2025 · CBR 16238 · Certificate 48628 ₹800
6th Renewed 17 Mar 2025 Period 19 Mar 2025 – 19 Mar 2026 · CBR 15361 · Certificate 20121 ₹800