# US 2021/0176091 A1 · Intelligent multi-channel vpn orchestration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0176091 A1
- Document ID: US20210176091A1
- Status: Published application
- Kind: A1
- Application number: 17/178,095
- Filed: 2021-02-17
- Published: 2021-06-10
- Earliest claimed: 2015-10-01
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Subil M. Abraham
- Web page: https://patentgrep.com/patent/US20210176091A1

## CPC

- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 43/08: Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L 45/54: {Organization of routing tables}
- H04L 65/102: Gateways (arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66)
- H04L 65/80: Responding to QoS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A respective VPN routing table for each of a plurality of VPNs can be stored on a client device. The client device can access a first VPN routing table and, using the first VPN routing table, establish a first VPN tunnel to a first VPN. The first VPN can be a first subnetwork assigned a particular network prefix. While the first VPN tunnel is currently active, the client device can access a second VPN routing table and, using the second VPN routing table, establish a second VPN tunnel to the second VPN. The second VPN can be a second subnetwork assigned the same particular network prefix as the first subnetwork. While the first VPN tunnel and the second VPN tunnel are simultaneously active, the client device can communicate data to remote devices in the first VPN and the second VPN using the particular network prefix for both.

## Claims

### Claim at position 1

1-25. (canceled)

### Claim 26

A method, comprising:
storing on a client device a respective virtual private network (VPN) routing table for each of a plurality of VPNs;
responsive to receiving a request to connect to a first VPN of the plurality of VPNs, accessing by the client device a first VPN routing table and, using the first VPN routing table, establishing by the client device a first VPN tunnel from the client device to the first VPN, wherein the first VPN is a first subnetwork that is assigned a particular network prefix, the particular network prefix being a portion of an internet protocol address of the first subnetwork;
while the first VPN tunnel is currently active, responsive to receiving a request to connect to a second VPN of the plurality of VPNs, accessing by the client device a second VPN routing table and, using the second VPN routing table, establishing by the client device a second VPN tunnel from the client device to the second VPN, wherein the second VPN is a second subnetwork that is assigned the same particular network prefix as the first subnetwork; and
while the first VPN tunnel and the second VPN tunnel are simultaneously active, communicating first data from the client device to a first remote device in the first VPN using the particular network prefix, and communicating second data from the client device to a second remote device in the second VPN using the particular network prefix.

### Claim 27 (depends on 26)

The method of claim 26, wherein:
the first VPN routing table comprises first association data associating a name of the first remote device in the first VPN to the first VPN;
receiving the request to connect to the first VPN comprises receiving from an application executing on the client device a request to connect to the first remote device in the first VPN; and
establishing by the client device the first VPN tunnel from the client device to the first VPN comprises identifying in the first VPN routing table the first association data associating the name of the first remote device in the first VPN to the first VPN.

### Claim 28 (depends on 27)

The method of claim 27, wherein the first VPN is defined within a third VPN, the method further comprising:
establishing by the client device a third VPN tunnel from the client device to the third VPN, wherein the client device automatically establishes the third VPN tunnel and the first VPN tunnel in a sequence in which the third VPN tunnel is established prior to establishment of the first VPN tunnel being initiated.

### Claim 29 (depends on 26)

The method of claim 26, further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN;
responsive to the QoS falling below a threshold level, automatically establishing a third VPN tunnel to the first VPN; and
dynamically splitting data communicated from the client device to the first remote device among the first VPN tunnel and the third VPN tunnel.

### Claim 30 (depends on 29)

The method of claim 29, further comprising:
dynamically aggregating, by the client device, data communicated from the first remote device to the client device via the first VPN tunnel and the third VPN tunnel.

### Claim 31 (depends on 26)

The method of claim 26, further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN and, based on the QoS, determining changes to be made to VPN routing parameters in the first VPN routing table to improve the QoS; and
automatically applying, by the client device, the changes to the VPN routing parameters in the first VPN routing table.

### Claim 32 (depends on 26)

The method of claim 26, further comprising:
via the first VPN tunnel, the client device accessing, through the first VPN, a service provided by a third remote device in a public communication network outside of the first VPN;
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the third remote device; and
responsive to the QoS falling below a threshold level, automatically establishing a new connection from the client device to the third remote device that does not route through the first VPN.

### Claim 33

A client device, comprising:
a processor programmed to initiate executable operations comprising:
storing on the client device a respective virtual private network (VPN) routing table for each of a plurality of VPNs;
responsive to receiving a request to connect to a first VPN of the plurality of VPNs, accessing by the client device a first VPN routing table and, using the first VPN routing table, establishing by the client device a first VPN tunnel from the client device to the first VPN, wherein the first VPN is a first subnetwork that is assigned a particular network prefix, the particular network prefix being a portion of an internet protocol address of the first subnetwork;
while the first VPN tunnel is currently active, responsive to receiving a request to connect to a second VPN of the plurality of VPNs, accessing by the client device a second VPN routing table and, using the second VPN routing table, establishing by the client device a second VPN tunnel from the client device to the second VPN, wherein the second VPN is a second subnetwork that is assigned the same particular network prefix as the first subnetwork; and
while the first VPN tunnel and the second VPN tunnel are simultaneously active, communicating first data from the client device to a first remote device in the first VPN using the particular network prefix, and communicating second data from the client device to a second remote device in the second VPN using the particular network prefix.

### Claim 34 (depends on 33)

The client device of claim 33, wherein:
the first VPN routing table comprises first association data associating a name of the first remote device in the first VPN to the first VPN;
receiving the request to connect to the first VPN comprises receiving from an application executing on the client device a request to connect to the first remote device in the first VPN; and
establishing by the client device the first VPN tunnel from the client device to the first VPN comprises identifying in the first VPN routing table the first association data associating the name of the first remote device in the first VPN to the first VPN.

### Claim 35 (depends on 34)

The client device of claim 34, wherein the first VPN is defined within a third VPN, the executable operations further comprising:
establishing by the client device a third VPN tunnel from the client device to the third VPN, wherein the client device automatically establishes the third VPN tunnel and the first VPN tunnel in a sequence in which the third VPN tunnel is established prior to establishment of the first VPN tunnel being initiated.

### Claim 36 (depends on 33)

The client device of claim 33, the executable operations further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN;
responsive to the QoS falling below a threshold level, automatically establishing a third VPN tunnel to the first VPN; and
dynamically splitting data communicated from the client device to the first remote device among the first VPN tunnel and the third VPN tunnel.

### Claim 37 (depends on 36)

The client device of claim 36, the executable operations further comprising:
dynamically aggregating, by the client device, data communicated from the first remote device to the client device via the first VPN tunnel and the third VPN tunnel.

### Claim 38 (depends on 33)

The client device of claim 33, the executable operations further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN and, based on the QoS, determining changes to be made to VPN routing parameters in the first VPN routing table to improve the QoS; and
automatically applying, by the client device, the changes to the VPN routing parameters in the first VPN routing table.

### Claim 39 (depends on 33)

The client device of claim 33, the executable operations further comprising:
via the first VPN tunnel, the client device accessing, through the first VPN, a service provided by a third remote device in a public communication network outside of the first VPN;
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the third remote device; and
responsive to the QoS falling below a threshold level, automatically establishing a new connection from the client device to the third remote device that does not route through the first VPN.

### Claim 40

A computer program product comprising a computer readable storage medium having program code stored thereon, the program code executable by a processor of a client device to perform operations comprising:
storing, by the processor, on the client device a respective virtual private network (VPN) routing table for each of a plurality of VPNs;
responsive to receiving a request to connect to a first VPN of the plurality of VPNs, accessing by the client device a first VPN routing table and, using the first VPN routing table, establishing by the client device a first VPN tunnel from the client device to the first VPN, wherein the first VPN is a first subnetwork that is assigned a particular network prefix, the particular network prefix being a portion of an internet protocol address of the first subnetwork;
while the first VPN tunnel is currently active, responsive to receiving a request to connect to a second VPN of the plurality of VPNs, accessing by the client device a second VPN routing table and, using the second VPN routing table, establishing by the client device a second VPN tunnel from the client device to the second VPN, wherein the second VPN is a second subnetwork that is assigned the same particular network prefix as the first subnetwork; and
while the first VPN tunnel and the second VPN tunnel are simultaneously active, communicating first data from the client device to a first remote device in the first VPN using the particular network prefix, and communicating second data from the client device to a second remote device in the second VPN using the particular network prefix.

### Claim 41 (depends on 40)

The computer program product of claim 40, wherein:
the first VPN routing table comprises first association data associating a name of the first remote device in the first VPN to the first VPN;
receiving the request to connect to the first VPN comprises receiving from an application executing on the client device a request to connect to the first remote device in the first VPN; and
establishing by the client device the first VPN tunnel from the client device to the first VPN comprises identifying in the first VPN routing table the first association data associating the name of the first remote device in the first VPN to the first VPN.

### Claim 42 (depends on 41)

The computer program product of claim 41, wherein the first VPN is defined within a third VPN, the operations further comprising:
establishing by the client device a third VPN tunnel from the client device to the third VPN, wherein the client device automatically establishes the third VPN tunnel and the first VPN tunnel in a sequence in which the third VPN tunnel is established prior to establishment of the first VPN tunnel being initiated.

### Claim 43 (depends on 40)

The computer program product of claim 40, the operations further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN;
responsive to the QoS falling below a threshold level, automatically establishing a third VPN tunnel to the first VPN; and
dynamically splitting data communicated from the client device to the first remote device among the first VPN tunnel and the third VPN tunnel.

### Claim 44 (depends on 43)

The computer program product of claim 43, the operations further comprising:
dynamically aggregating, by the client device, data communicated from the first remote device to the client device via the first VPN tunnel and the third VPN tunnel.

### Claim 45 (depends on 40)

The computer program product of claim 40, the operations further comprising:
monitoring, by the client device, a quality of service (QoS) measured for communications exchanged between the client device and the first remote device within the first VPN and, based on the QoS, determining changes to be made to VPN routing parameters in the first VPN routing table to improve the QoS; and
automatically applying, by the client device, the changes to the VPN routing parameters in the first VPN routing table.
