# US 2015/0150073 A1 · Smart Virtual Private Network

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

- Number: US 2015/0150073 A1
- Document ID: US20150150073A1
- Status: Published application
- Kind: A1
- Application number: 14/090,378
- Filed: 2013-11-26
- Published: 2015-05-28
- Earliest claimed: 2013-11-26
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Pranav Bhalerao; Sunil Nr; Chandra Balaji
- Web page: https://patentgrep.com/patent/US20150150073A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 63/0272: {Virtual private networks}
- H04L 63/105: {Multiple levels of security}
- H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one implementation, a policy server establishes a smart virtual private network between two client devices. The smart virtual private network includes a secure communication session using a security level or security algorithm that is variable and defined as a function of the two client devices. A first client device may generate a registration request including a first security configuration including the security level. Based on the registration request, the policy server generates a routing message that defines routing for communication from the first client device to a second client device. The routing message may update a routing table to associate the policy server with the second client device.

## Claims

### Claim 1

A method comprising:
establishing a security protocol channel between a policy server and a first client device;
receiving a registration request including a first security configuration for the first client device, wherein the first security configuration includes a security level;
updating a client database according to the security configuration; and
generating a routing message for the first client device, wherein the routing message defines routing for communication from the first client device to a second client device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the routing message is configured to update a routing table of the first client device with an address of the policy server as a next hop for communication to the second client device.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
receiving a policy request from the first client device, wherein the policy request specifies the second client device; and
accessing the client database based on the policy request.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
generating a security policy based on the first security configuration and the second security configuration.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
in response to the policy request from the first client device, pushing the security polity to the first client device and the second client device.

### Claim 6 (depends on 4)

The method of claim 4, wherein the security policy includes a highest common security level of the security level of the first client device and a security level of the second client device.

### Claim 7 (depends on 4)

The method of claim 4, wherein the security policy includes data indicative of an encryption algorithm or a hash algorithm.

### Claim 8

A method comprising:
establishing a security protocol channel with a policy server;
generating a registration request including a first security configuration for the first client device, wherein the first security configuration includes a security level;
sending the registration request to the policy server;
receiving a routing message from the policy server, wherein the routing message defines routing for communication from the first client device to a second client device; and
updating a routing table in response to the routing message.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
receiving a packet for protection under the first security configuration; and
querying the routing table for the destination address.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
when the routing table specifies a next hop as the policy server for the packet for protection, sending a policy request to the policy server.

### Claim 11 (depends on 9)

The method of claim 9, further comprising:
receiving an acknowledgement message from the policy server.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
cloning a virtual access interface for secure communication under the policy.

### Claim 13 (depends on 9)

The method of claim 9, further comprising:
when the routing table specifies a next hop as the policy server for the packet for protection, dropping the packet for protection.

### Claim 14

An apparatus comprising:
a client database configured to store protected network addresses and security configurations;
a communication interface configured to receive a registration request including a security configuration for a first client device, wherein the security configuration includes a security level or a security algorithm; and
a processor configured to update the client database according to the security configuration and generate a routing message for the first client device, wherein the routing message defines routing for communication from the first client device to a second client device.

### Claim 15 (depends on 14)

The apparatus of claim 14, wherein the routing message is configured to update a routing table of the first client device with an address of the communication interface as a next hop for communication to the second client device.

### Claim 16 (depends on 14)

The apparatus of claim 14, wherein the communication interface receives a policy request from the first client device, wherein the policy request specifies the second client device and the processor queries the client database based on the policy request.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein the processor is configured to generate a security policy based on the security configuration of the first client device and a second security configuration of the second client device, and send the security policy to the first client device and the second client device.

### Claim 18

An apparatus comprising:
a routing database configured to store destination addresses and next hop addresses; and
a processor configured to generate a registration request including a security level for a local device and configured to update the routing database based on a routing message received from a policy server in response to the registration request, wherein the routing message defines the next hop address for a remote client device as the policy server.

### Claim 19 (depends on 18)

The apparatus of claim 18, wherein the processor is configured to query the routing database based on a received packet listing the remote client device as a destination and forward the received packet to the policy server.

### Claim 20 (depends on 19)

The apparatus of claim 19, wherein the processor is configured to drop the received packet in response to the destination being associated with the policy server in the routing database.
