# US 2010/0142410 A1 · System and method for providing virtual private networks

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

- Number: US 2010/0142410 A1
- Document ID: US20100142410A1
- Status: Published application
- Kind: A1
- Application number: 12/634,536
- Filed: 2009-12-09
- Published: 2010-06-10
- Earliest claimed: 2008-12-09
- Assignees: Glue Networks, Inc.
- Inventors: Olivier HUYNH VAN; Jeff Gray
- Web page: https://patentgrep.com/patent/US20100142410A1

## CPC

- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- 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 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/14: Network analysis or design
- H04L 45/17: Shortcut routing, e.g. using next hop resolution protocol [NHRP]
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/164: {at the network layer}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A computerized system and method for automatically determining customized configurations for each of a plurality of endpoints of a virtual private network (VPN) and deploying the configurations to the endpoints, comprising: accepting, using an interface, parameters required for building the configurations from a user, the configurations enabling the endpoints to process a mixture of time sensitive and non-time sensitive data, and the parameters comprising: endpoint IP addressing scheme information and network design information; automatically generating, using at least one configuration engine, complete customized endpoint configurations for the parameters, and instantiating the configurations based on endpoint hardware-specific information, with no further input required from the user; and deploying, using a scheduler, the configurations to the endpoints of the at least one VPN, wherein the VPN is an mGRE VPN using NHRP protocol.

## Claims

### Claim 1

A computerized method for automatically determining customized configurations for each of a plurality of endpoints of at least one virtual private network (VPN) and deploying the configurations to the endpoints, comprising:
accepting, using at least one user interface, parameters required for building the configurations from at least one user, the configurations enabling the endpoints to process a mixture of time sensitive and non-time sensitive data, and the parameters comprising: endpoint IP addressing scheme information and network design information;
automatically generating, using at least one configuration engine, complete customized endpoint configurations for the parameters, and instantiating the configurations based on endpoint hardware-specific information, with no further input required from the user; and
deploying, using at least one scheduler, the configurations to the endpoints of the VPN, wherein the VPN is an mGRE VPN using NHRP protocol.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
validating the parameters utilizing the at least one configuration engine.

### Claim 3 (depends on 1)

The method of claim 1, wherein the deploying is distributed into reasonable time slots so that resource starvation and connection bottlenecks are avoided.

### Claim 4 (depends on 1)

The method of claim 1, wherein the computerized method prevents misconfigurations.

### Claim 5 (depends on 4)

The method of claim 4, wherein the computerized method prevents overlapping IP address spaces.

### Claim 6 (depends on 4)

The method of claim 4, wherein the computerized method automatically queries each endpoint to verify that the hardware-specific information is consistent with the customized endpoint specific configuration for the endpoint.

### Claim 7 (depends on 1)

The method of claim 1, wherein a consistent network addressing plan is utilized.

### Claim 8 (depends on 1)

The method of claim 1, wherein the computerized method automatically assigns the endpoint IP addressing.

### Claim 9 (depends on 8)

The method of claim 8, wherein the computerized method automatically selects an unused IP Subnet from the Master IP Subnet,

### Claim 10 (depends on 9)

The method of claim 9, wherein the computerized method automatically determines the unused IP Subnet from the Master IP Subnet using IP Subnetting,

### Claim 11 (depends on 1)

The method of claim 1, wherein all hardware platforms with all possible combinations of field upgradable parts are managed.

### Claim 12 (depends on 1)

The method of claim 1, wherein a contemporaneous inventory is maintained of all VPN hardware to which configurations are automatically deployed,

### Claim 13 (depends on 1)

The method of claim 1, wherein the parameters further comprise network resiliency information.

### Claim 14 (depends on 1)

The method of claim 1, wherein the parameters further comprise endpoint authentication information.

### Claim 15 (depends on 1)

The method of claim 1, wherein the parameters further comprise: security rules, routing policies, or licensing information, or any combination thereof.

### Claim 16 (depends on 1)

The method of claim 1, wherein the parameters can be used to create endpoint specific settings and hardware-specific configuration settings.

### Claim 17 (depends on 1)

The method of claim 1, wherein at least one orchestrator generates a proper endpoint configuration code.

### Claim 18 (depends on 1)

The method of claim 1, wherein the endpoint addressing scheme information comprises at least one mGRE IP subnet prefix.

### Claim 19 (depends on 1)

The method of claim 1, wherein the network design information comprises at least one network ID.

### Claim 20 (depends on 1)

The method of claim 1, wherein the endpoints are capable of belonging to the same network.

### Claim 21 (depends on 1)

The method of claim 1, wherein the endpoints are capable of belonging to the same customer.

### Claim 22 (depends on 1)

The method of claim 1, wherein the endpoints are capable of belonging to many networks.

### Claim 23 (depends on 1)

The method of claim 1, wherein the endpoints are capable of belonging to many customers.

### Claim 24 (depends on 17)

The method of claim 17, wherein customer-level objects are utilized.

### Claim 25 (depends on 18)

The method of claim 18, wherein the customer-level object comprise: networks, Public Key Infrastructure (PKI) Root Certificate Authorities (CAs), endpoint templates, High Availability (HA) groups, or IP address pools, or any combination thereof.

### Claim 26 (depends on 19)

The method of claim 19, wherein the IP address pools comprise: Master IP Subnet (MIS) groups, Master IP Subnets (MIS), and IP Subnets, or any combination thereof.

### Claim 27 (depends on 1)

The method of claim 1, wherein activity logs are created and maintained.

### Claim 28 (depends on 27)

The method of claim 27, wherein the activity logs comprise: output of the configuration engine, scheduler, or delivery engine, or any combination thereof.

### Claim 29 (depends on 1)

The method of claim 1, wherein the mGRE VPN using NHRP protocol is using at least one Master IP Subnet.

### Claim 30 (depends on 1)

The method of claim 1, wherein the mGRE VPN using NHRP protocol is resilient due to the use of high availability (HA) groups, which allows VHEs to fail without affecting the user experience.

### Claim 31 (depends on 29)

The method of claim 29, wherein all VHEs that are part of the same mGRE VPN using NHRP protocol use at least one daisy chaining HA Group.

### Claim 32 (depends on 31)

The method of claim 31, wherein all VPN headends (VHEs) that are part of the same mGRE VPN using NHRP protocol have all their internal interfaces connected on the same local area network (LAN) segment.

### Claim 33 (depends on 32)

The method of claim 32, wherein all VHE internal interfaces are automatically numbered by the at least one configuration engine.

### Claim 34 (depends on 1)

The method of claim 1, wherein a CPE is attached to at least one mGRE VPN using NHRP protocol.

### Claim 35 (depends on 34)

The method of claim 34, wherein a deterministic algorithm is used to select which VHEs a CPE will peer with.

### Claim 36 (depends on 33)

The method of claim 33, wherein all the VHEs are daisy chained together.

### Claim 37 (depends on 34)

The method of claim 34, wherein a CPE that is part of at least two mGRE VPNs using NHRP protocol uses at least one bundling HA Group.

### Claim 38 (depends on 1)

The method of claim 1, wherein endpoints that are part of the same VPN authenticate themselves to each other.

### Claim 39 (depends on 38)

The method of claim 38, wherein there is at least one public key infrastructure (PKI) server.

### Claim 40 (depends on 39)

The method of claim 39, wherein at least one orchestrator creates and manages at least one PKI server.

### Claim 41 (depends on 40)

The method of claim 40, wherein the at least one orchestrator can manage at least one associated Certificate Lifecycle.

### Claim 42 (depends on 1)

The method of claim 1, wherein the parameters further comprise templates used to define profiles of the endpoints.

### Claim 43 (depends on 42)

The method of claim 42, wherein the templates comprise: VHE templates and/or CPE templates.

### Claim 44 (depends on 41)

The method of claim 41, wherein the at least one orchestrator synchronizes all the endpoints according to the templates.

### Claim 45 (depends on 1)

The method of claim 1, wherein the parameters further comprise customer specifications.

### Claim 46 (depends on 1)

The method of claim 1, wherein the parameters further comprise network specifications.

### Claim 47 (depends on 45)

The method of claim 45, wherein at least one orchestrator synchronizes all the endpoints according to customer specifications.

### Claim 48 (depends on 46)

The method of claim 46, wherein at least one orchestrator synchronizes all the endpoints according to network specifications.

### Claim 49 (depends on 1)

The method of claim 1, wherein at least one entity's network can be extended to at least one remote location.

### Claim 50 (depends on 49)

The method of claim 49, wherein at least one user of at least one endpoint can self-provision at least one remote device to the at least one entity's network.

### Claim 51 (depends on 50)

The method of claim 50, wherein the at least one user can self-provision access to the at least one entity's network by: providing personal information, credential information, and entity information; and receiving an endpoint.

### Claim 52 (depends on 51)

The method of claim 51, wherein the received endpoint is configured by a remote device automation engine using the personal information, the credential information, and the entity information.

### Claim 53 (depends on 52)

The method of claim 52, wherein certificates are generated and delivered to at least one legitimate endpoint.

### Claim 54 (depends on 53)

The method of claim 53, wherein at least one fingerprint of the at least one endpoint is taken when the at least one endpoint is enrolled in the entity's network.

### Claim 55 (depends on 54)

The method of claim 54, wherein at least one orchestrator verifies that at least one fingerprint of a certificate request from at least one entity matches the at least one fingerprint of the at least one endpoint taken when the at least one endpoint was enrolled in the entity's network.

### Claim 56 (depends on 1)

The method of claim 1, wherein the at least one endpoint remains in sync with the settings defined in the network.

### Claim 57 (depends on 37)

The method of claim 37, wherein NHRP maps and NHS server entries are configured for each VHE.

### Claim 58 (depends on 57)

The method of claim 57, wherein if there are greater than two VHEs, two NHRP maps are created and two NHS server entries are created for each VHE.

### Claim 59 (depends on 58)

The method of claim 58, wherein one NHRP map is a primary map, and the other NHRP map is a secondary map; and wherein one NHS server entry is a primary entry, and the other NHS server entry is a secondary entry.

### Claim 60

A computerized system for automatically determining customized configurations for each of a plurality of endpoints of at least one virtual private network (VPN) and deploying the configurations to the endpoints, comprising:
at least one processor, wherein the at least one processor is configured for:
accepting, using at least one user interface, parameters required for building the configurations from at least one user, the configurations enabling the endpoints to process a mixture of time sensitive and non-time sensitive data, and the parameters comprising: endpoint IP addressing scheme information and network design information;
automatically generating, using at least one configuration engine, complete customized endpoint configurations for the parameters, and instantiating the configurations based on endpoint hardware-specific information, with no further input required from the user; and
deploying, using at least one scheduler, the configurations to the endpoints of the VPN, wherein the VPN is an mGRE VPN using NHRP protocol.

### Claim 61 (depends on 60)

The system of claim 60, further comprising:
validating the parameters utilizing the at least one configuration engine.

### Claim 62 (depends on 60)

The system of claim 60, wherein the deploying is distributed into reasonable time slots so that resource starvation and connection bottlenecks are avoided.

### Claim 63 (depends on 60)

The system of claim 60, wherein the computerized method prevents misconfigurations.

### Claim 64 (depends on 63)

The system of claim 63, wherein the computerized method prevents overlapping IP address spaces.

### Claim 65 (depends on 63)

The system of claim 63, wherein the computerized method automatically queries each endpoint to verify that the hardware-specific information is consistent with the customized endpoint specific configuration for the endpoint.

### Claim 66 (depends on 60)

The system of claim 60, wherein a consistent network addressing plan is utilized.

### Claim 67 (depends on 60)

The system of claim 60, wherein the computerized method automatically assigns the endpoint IP addressing.

### Claim 68 (depends on 67)

The system of claim 67, wherein the computerized method automatically selects an unused IP Subnet from the Master IP Subnet,

### Claim 69 (depends on 68)

The system of claim 68, wherein the computerized method automatically determines the unused IP Subnet from the Master IP Subnet using IP Subnetting,

### Claim 70 (depends on 60)

The system of claim 60, wherein all hardware platforms with all possible combinations of field upgradable parts are managed.

### Claim 71 (depends on 60)

The system of claim 60, wherein a contemporaneous inventory is maintained of all VPN hardware to which configurations are automatically deployed,

### Claim 72 (depends on 60)

The system of claim 60, wherein the parameters further comprise network resiliency information.

### Claim 73 (depends on 60)

The system of claim 60, wherein the parameters further comprise endpoint authentication information.

### Claim 74 (depends on 60)

The system of claim 60, wherein the parameters further comprise: security rules, routing policies, or licensing information, or any combination thereof.

### Claim 75 (depends on 60)

The system of claim 60, wherein the parameters can be used to create endpoint specific settings and hardware-specific configuration settings.

### Claim 76 (depends on 60)

The system of claim 60, wherein at least one orchestrator generates a proper endpoint configuration code.

### Claim 77 (depends on 60)

The system of claim 60, wherein the endpoint addressing scheme information comprises at least one mGRE IP subnet prefix.

### Claim 78 (depends on 60)

The system of claim 60, wherein the network design information comprises at least one network ID.

### Claim 79 (depends on 60)

The system of claim 60, wherein the endpoints are capable of belonging to the same network.

### Claim 80 (depends on 60)

The system of claim 60, wherein the endpoints are capable of belonging to the same customer.

### Claim 81 (depends on 60)

The system of claim 60, wherein the endpoints are capable of belonging to many networks.

### Claim 82 (depends on 60)

The system of claim 60, wherein the endpoints are capable of belonging to many customers.

### Claim 83 (depends on 76)

The system of claim 76, wherein customer-level objects are utilized.

### Claim 84 (depends on 77)

The system of claim 77, wherein the customer-level object comprise: networks, Public Key Infrastructure (PKI) Root Certificate Authorities (CAs), endpoint templates, High Availability (HA) groups, or IP address pools, or any combination thereof.

### Claim 85 (depends on 78)

The system of claim 78, wherein the IP address pools comprise: Master IP Subnet (MIS) groups, Master IP Subnets (MIS), and IP Subnets, or any combination thereof.

### Claim 86 (depends on 60)

The system of claim 60, wherein activity logs are created and maintained.

### Claim 87 (depends on 86)

The system of claim 86, wherein the activity logs comprise: output of the configuration engine, scheduler, or delivery engine, or any combination thereof.

### Claim 88 (depends on 60)

The system of claim 60, wherein the mGRE VPN using NHRP protocol is using at least one Master IP Subnet.

### Claim 89 (depends on 60)

The system of claim 60, wherein the mGRE VPN using NHRP protocol is resilient due to the use of high availability (HA) groups, which allows VHEs to fail without affecting the user experience.

### Claim 90 (depends on 88)

The system of claim 88, wherein all VHEs that are part of the same mGRE VPN using NHRP protocol use at least one daisy chaining HA Group.

### Claim 91 (depends on 90)

The system of claim 90, wherein all VPN headends (VHEs) that are part of the same mGRE VPN using NHRP protocol have all their internal interfaces connected on the same local area network (LAN) segment.

### Claim 92 (depends on 91)

The system of claim 91, wherein all VHE internal interfaces are automatically numbered by the at least one configuration engine.

### Claim 93 (depends on 60)

The system of claim 60, wherein a CPE is attached to at least one mGRE VPN using NHRP protocol.

### Claim 94 (depends on 93)

The system of claim 93, wherein a deterministic algorithm is used to select which VHEs a CPE will peer with.

### Claim 95 (depends on 92)

The system of claim 92, wherein all the VHEs are daisy chained together.

### Claim 96 (depends on 93)

The system of claim 93, wherein a CPE that is part of at least two mGRE VPNs using NHRP protocol uses at least one bundling HA Group.

### Claim 97 (depends on 60)

The system of claim 60, wherein endpoints that are part of the same VPN authenticate themselves to each other.

### Claim 98 (depends on 97)

The system of claim 97, wherein there is at least one public key infrastructure (PKI) server.

### Claim 99 (depends on 98)

The system of claim 98, wherein at least one orchestrator creates and manages at least one PKI server.

### Claim 100 (depends on 99)

The system of claim 99, wherein the at least one orchestrator can manage at least one associated Certificate Lifecycle.

### Claim 101 (depends on 60)

The system of claim 60, wherein the parameters further comprise templates used to define profiles of the endpoints.

### Claim 102 (depends on 101)

The system of claim 101, wherein the templates comprise: VHE templates and/or CPE templates.

### Claim 103 (depends on 100)

The system of claim 100, wherein the at least one orchestrator synchronizes all the endpoints according to the templates.

### Claim 104 (depends on 60)

The system of claim 60, wherein the parameters further comprise customer specifications.

### Claim 105 (depends on 60)

The system of claim 60, wherein the parameters further comprise network specifications.

### Claim 106 (depends on 104)

The system of claim 104, wherein at least one orchestrator synchronizes all the endpoints according to customer specifications.

### Claim 107 (depends on 105)

The system of claim 105, wherein at least one orchestrator synchronizes all the endpoints according to network specifications.

### Claim 108 (depends on 60)

The system of claim 60, wherein at least one entity's network can be extended to at least one remote location.

### Claim 109 (depends on 108)

The system of claim 108, wherein at least one user of at least one endpoint can self-provision at least one remote device to the at least one entity's network.

### Claim 110 (depends on 109)

The system of claim 109, wherein the at least one user can self-provision access to the at least one entity's network by: providing personal information, credential information, and entity information; and receiving an endpoint.

### Claim 111 (depends on 110)

The system of claim 110, wherein the received endpoint is configured by a remote device automation engine using the personal information, the credential information, and the entity information.

### Claim 112 (depends on 111)

The system of claim 111, wherein certificates are generated and delivered to at least one legitimate endpoint.

### Claim 113 (depends on 112)

The system of claim 112, wherein at least one fingerprint of the at least one endpoint is taken when the at least one endpoint is enrolled in the entity's network.

### Claim 114 (depends on 113)

The system of claim 113, wherein at least one orchestrator verifies that at least one fingerprint of a certificate request from at least one entity matches the at least one fingerprint of the at least one endpoint taken when the at least one endpoint was enrolled in the entity's network.

### Claim 115 (depends on 60)

The system of claim 60, wherein the at least one endpoint remains in sync with the settings defined in the network.

### Claim 116 (depends on 97)

The system of claim 97, wherein NHRP maps and NHS server entries are configured for each VHE.

### Claim 117 (depends on 116)

The system of claim 116, wherein if there are greater than two VHEs, two NHRP maps are created and two NHS server entries are created for each VHE.

### Claim 118 (depends on 117)

The system of claim 117, wherein one NHRP map is a primary map, and the other NHRP map is a secondary map; and wherein one NHS server entry is a primary entry, and the other NHS server entry is a secondary entry.
