IP Library Granted Patent US 11,765,232
Granted Patent B1
US 11,765,232 · App. 17/888,176 · Granted Sep 19, 2023

Communication functions in a mesh network

Inventors: Benas Orlovas (Jonavos r., LT); Kristupas Antanavi{hacek over (c)}ius (Vilnius, LT)
Assignee: UAB 360 IT
H04L67/12H04L41/08H04L69/321
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,765,232
App. No.
17/888,176
Granted
Sep 19, 2023
Kind
B1
Abstract

A method including configuring an intermediate layer included in a network stack associated with an infrastructure device to: receive a request from a first device in a mesh network, the request requesting the infrastructure device to determine a communication parameter associated with communicating meshnet data with the first device; determine the communication parameter based at least in part on information included in the request; and transmit identification information identifying the communication parameter to an application layer included in the network stack; configuring the application layer to determine a response including an encrypted meshnet packet including the identification information; and transmitting, by the infrastructure device, the response to a second device in the mesh network is disclosed. Various other aspects are contemplated.

Claims (45)

1. A method, comprising:

configuring an intermediate layer included in a network stack associated with an infrastructure device to:

receive a request from a first device in a mesh network, the request requesting the infrastructure device to determine a communication parameter associated with communicating meshnet data with the first device;

determine the communication parameter based at least in part on information included in the request; and

transmit identification information identifying the communication parameter to an application layer included in the network stack;

configuring the application layer to determine a response including an encrypted meshnet packet including the identification information; and

transmitting, by the infrastructure device, the response to a second device in the mesh network.

2. The method of claim 1 , wherein the intermediate layer includes a transport layer included in the network stack.

3. The method of claim 1 , wherein the intermediate layer includes a session layer included between a transport layer and the application layer in the network stack.

4. The method of claim 1 , wherein the intermediate layer includes a presentation layer included between a transport layer and the application layer in the network stack.

5. The method of claim 1 , wherein the communication parameter includes a public port to be utilized by the infrastructure device or the second device for communicating the meshnet data with the first device.

6. The method of claim 1 , further comprising:

configuring the application layer to determine the response includes configuring the application layer to encrypt a meshnet packet utilizing an encryption key negotiated between the infrastructure device and the first device.

7. The method of claim 1 , wherein

configuring the intermediate layer to receive the request includes configuring the intermediate layer to receive the request in encrypted form via a meshnet connection between the first device and the infrastructure device; and

transmitting the response includes transmitting the response in the encrypted form via the meshnet connection.

8. An infrastructure device, comprising:

a memory; and

a processor communicatively coupled to the memory, the memory and the processor being configured to:

configure an intermediate layer included in a network stack associated with an infrastructure device to:

receive a request from a first device in a mesh network, the request requesting the infrastructure device to determine a communication parameter associated with communicating meshnet data with the first device;

determine the communication parameter based at least in part on information included in the request; and

transmit identification information identifying the communication parameter to an application layer included in the network stack;

configure the application layer to determine a response including an encrypted meshnet packet including the identification information; and

transmit the response to a second device in the mesh network.

9. The infrastructure device of claim 8 , wherein the intermediate layer includes a transport layer included in the network stack.

10. The infrastructure device of claim 8 , wherein the intermediate layer includes a session layer included between a transport layer and the application layer in the network stack.

11. The infrastructure device of claim 8 , wherein the intermediate layer includes a presentation layer included between a transport layer and the application layer in the network stack.

12. The infrastructure device of claim 8 , wherein the communication parameter includes a public port to be utilized by the infrastructure device or the second device for communicating the meshnet data with the first device.

13. The infrastructure device of claim 8 , wherein, to configure the application layer to determine the response, the memory and the processor are configured to configure the application layer to encrypt a meshnet packet utilizing an encryption key negotiated between the infrastructure device and the first device.

14. The infrastructure device of claim 8 , wherein

to configure the intermediate layer to receive the request, the memory and the processor are configured to configure the intermediate layer to receive the request in encrypted form via a meshnet connection between the first device and the infrastructure device; and

to transmit the response, the memory and the processor are configured to transmit the response in the encrypted form via the meshnet connection.

15. A non-transitory computer-readable medium configured to store instructions, which when executed by a processor associated with an infrastructure device, cause the processor to:

configure an intermediate layer included in a network stack associated with an infrastructure device to:

receive a request from a first device in a mesh network, the request requesting the infrastructure device to determine a communication parameter associated with communicating meshnet data with the first device;

determine the communication parameter based at least in part on information included in the request; and

transmit identification information identifying the communication parameter to an application layer included in the network stack;

configure the application layer to determine a response including an encrypted meshnet packet including the identification information; and

transmit the response to a second device in the mesh network.

16. The non-transitory computer-readable medium of claim 15 , wherein the intermediate layer includes a transport layer included in the network stack.

17. The non-transitory computer-readable medium of claim 15 , wherein the intermediate layer includes a session layer included between a transport layer and the application layer in the network stack.

18. The non-transitory computer-readable medium of claim 15 , wherein the intermediate layer includes a presentation layer included between a transport layer and the application layer in the network stack.

19. The non-transitory computer-readable medium of claim 15 , wherein the communication parameter includes a public port to be utilized by the infrastructure device or the second device for communicating the meshnet data with the first device.

20. The non-transitory computer-readable medium of claim 15 , wherein, to configure the application layer to determine the response, the processor is configured to configure the application layer to encrypt a meshnet packet utilizing an encryption key negotiated between the infrastructure device and the first device.

Continuity (1)
Continuation 17887443 · Aug 13, 2022