# US 2023/0412567 A1 · Globally available vpn as a service

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

- Number: US 2023/0412567 A1
- Document ID: US20230412567A1
- Status: Published application
- Kind: A1
- Application number: 17/842,663
- Filed: 2022-06-16
- Published: 2023-12-21
- Earliest claimed: 2022-06-16
- Assignees: Microsot Technology Licensing, LLC
- Applicants: Microsot Technology Licensing, LLC
- Inventors: Shyamshankar DHARMARAJAN; Sumit GUPTA
- Web page: https://patentgrep.com/patent/US20230412567A1

## CPC

- H04L 63/0272: {Virtual private networks}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/1008: based on parameters of servers, e.g. available memory or workload (monitoring of computer activity G06F11/30)
- H04L 67/1021: based on client or server locations
- H04L 67/1036: Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
- H04L 63/107: {wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Generally discussed herein are devices, systems, and methods for globally accessible virtual private network (VPN) as a service. A method can include receiving a domain name request at a domain name system (DNS), the domain name request being received from a tenant premise equipment and including a domain name of a plurality of domain names associated with a VPN service, identifying, by the DNS and based on the domain name, an Internet Protocol (IP) address of a node of nodes dedicated to servicing traffic of the domain name, and establishing, by the DNS, a VPN tunnel between the tenant premise equipment and the identified node.

## Claims

### Claim 1

A method for virtual private network (VPN) as a service, the method comprising:
receiving a domain name request at a domain name system (DNS), the domain name request being received from a tenant premise equipment and including a domain name of a plurality of domain names associated with a VPN service;
identifying, by the DNS and based on the domain name, an Internet Protocol (IP) address of a node of nodes dedicated to servicing traffic of the domain name; and
establishing, by the DNS, a VPN tunnel between the tenant premise equipment and the identified node.

### Claim 2 (depends on 1)

The method of claim 1, wherein the nodes are a subset of a plurality of nodes, the plurality of nodes organized into groups of nodes dedicated to servicing traffic of a respective domain name of the plurality of domain names, the method further comprising scheduling maintenance of the plurality of nodes such that groups of nodes are sequentially scheduled for maintenance.

### Claim 3 (depends on 2)

The method of claim 2, wherein scheduling maintenance includes scheduling such that only a single group undergoes maintenance at a given time.

### Claim 4 (depends on 2)

The method of claim 2, wherein the groups include nodes in multiple geographically separated regions and the method further comprises:
determining which of the geographically separated regions is closest to the tenant premise equipment; and
wherein identifying the node includes selecting a node of the plurality of nodes assigned to the group and in the region geographically closest to the tenant premise equipment.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
before establishing the VPN tunnel with the identified node, determining whether the identified node has sufficient health to service the traffic; and
establishing the VPN tunnel responsive to determining the identified node has sufficient health.

### Claim 6 (depends on 5)

The method of claim 5, wherein:
determining whether the identified node has sufficient health includes issuing a monitor packet to the node and receiving an acknowledgment packet, a negative acknowledgment, or no response to the monitor packet; and
determining the node has sufficient health responsive to the acknowledgement packet and determining the node has insufficient health otherwise.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
before establishing the VPN tunnel with the identified node, determining whether the identified node has sufficient capacity to service the traffic; and
establishing the VPN tunnel responsive to determining the identified node has sufficient capacity.

### Claim 8 (depends on 7)

The method of claim 7, wherein:
determining whether the identified node has sufficient capacity includes issuing a monitor packet to the node and receiving an acknowledgment packet, a negative acknowledgment, or no response to the monitor packet; and
determining the node has sufficient capacity responsive to the acknowledgement packet and determining the node has insufficient capacity otherwise.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
receiving a request to subscribe to more tunnels than are required to satisfy a bandwidth requirement of a tenant;
subscribing a tenant to the tunnels based on the request; and
satisfying the bandwidth requirement even when a group of nodes dedicated to servicing a tunnel of the tunnels is down for maintenance.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
detecting the established VPN tunnel has failed; and
responsive to detecting the established VPN tunnel has failed, establishing a second VPN tunnel between the tenant premise equipment and a second node of the plurality of nodes with a different IP address.

### Claim 11

A machine-readable medium including instructions that, when executed by a machine, cause a domain name system (DNS) to perform operations for virtual private network (VPN) as a service, the operations comprising:
receiving a domain name request, the domain name request being received from a tenant premise equipment and including a domain name of a plurality of domain names associated with a VPN service;
identifying, based on the domain name, an Internet Protocol (IP) address of a node of nodes dedicated to servicing traffic of the domain name; and
establishing a VPN tunnel between the tenant premise equipment and the identified node.

### Claim 12 (depends on 11)

The machine-readable medium of claim 11, wherein the nodes are a subset of a plurality of nodes, the plurality of nodes organized into groups of nodes dedicated to servicing traffic of a respective domain name of the plurality of domain names, the operations further comprise scheduling maintenance of the plurality of nodes such that groups of nodes are sequentially scheduled for maintenance.

### Claim 13 (depends on 12)

The machine-readable medium of claim 12, wherein scheduling maintenance includes scheduling such that only a single group undergoes maintenance at a given time.

### Claim 14 (depends on 12)

The machine-readable medium of claim 12, wherein the groups include nodes in multiple geographically separated regions and the operations further comprise:
determining which of the geographically separated regions is closest to the tenant premise equipment; and
wherein identifying the node includes selecting a node of the plurality of nodes assigned to the group and in the region geographically closest to the tenant premise equipment.

### Claim 15 (depends on 11)

The machine-readable medium of claim 11, wherein the operations further comprise:
before establishing the VPN tunnel with the identified node, determining whether the identified node has sufficient health to service the traffic; and
establishing the VPN tunnel responsive to determining the identified node has sufficient health.

### Claim 16 (depends on 15)

The machine-readable medium of claim 15, wherein:
determining whether the identified node has sufficient health includes issuing a monitor packet to the node and receiving an acknowledgment packet, a negative acknowledgment, or no response to the monitor packet; and
determining the node has sufficient health responsive to the acknowledgement packet and determining the node has insufficient health otherwise.

### Claim 17

A domain name system (DNS) comprising:
processing circuitry;
a memory coupled to the processing circuitry, the memory including instructions that, when executed by the processing circuitry, cause the processing circuitry to perform operations for virtual private network (VPN) as a service, the operations comprising:
receiving a domain name request, the domain name request being received from a tenant premise equipment and including a domain name of a plurality of domain names associated with a VPN service;
identifying, based on the domain name, an Internet Protocol (IP) address of a node of nodes dedicated to servicing traffic of the domain name; and
establishing a VPN tunnel between the tenant premise equipment and the identified node.

### Claim 18 (depends on 17)

The DNS of claim 17, wherein the operations further comprise:
before establishing the VPN tunnel with the identified node, determining whether the identified node has sufficient capacity to service the traffic; and
establishing the VPN tunnel responsive to determining the identified node has sufficient capacity.

### Claim 19 (depends on 18)

The DNS of claim 18, wherein:
determining whether the identified node has sufficient capacity includes issuing a monitor packet to the node and receiving an acknowledgment packet, a negative acknowledgment, or no response to the monitor packet; and
determining the node has sufficient capacity responsive to the acknowledgement packet and determining the node has insufficient capacity otherwise.

### Claim 20 (depends on 17)

The DNS of claim 17, wherein the operations further comprise:
receiving a request to subscribe to more tunnels than are required to satisfy a bandwidth requirement of a tenant;
subscribing a tenant to the tunnels based on the request; and
satisfying the bandwidth requirement even when a group of nodes dedicated to servicing a tunnel of the tunnels is down for maintenance.
