# US 2006/0070115 A1 · Server, VPN client, VPN system, and software

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

- Number: US 2006/0070115 A1
- Document ID: US20060070115A1
- Status: Published application
- Kind: A1
- Application number: 11/047,772
- Filed: 2005-02-02
- Published: 2006-03-30
- Earliest claimed: 2004-09-29
- Assignees: Hitachi Communication Technologies, Ltd.
- Inventors: Mariko Yamada; Masashi Yano; Makoto Arai
- Web page: https://patentgrep.com/patent/US20060070115A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- 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

When forming an L2VPN, each VPN server is required to decrypt data received from a VPN client using the source VPN client key and encrypt the data using the destination VPN client key. The loads of the encrypting and decrypting processings are high, thereby the VPN server through-put is lowered. In order to solve the above problem, according to the present invention, the destination address of an IP packet sent from the VPN client is used as a multicast address, then data is encrypted according to the security association of the multicast address distributed from the VPN server. The encrypted IP packet is encapsulated with the IP address of the VPN server and sent to the VPN server. Receiving this IP packet, the VPN server determines the destination VPN client according to the multicast address of the encapsulated IP packet, then encapsulated with the IP address of the destination VPN client and sent to the VPN client.

## Claims

### Claim 1

A server connected to a plurality of VPN client devices through a network, having a memory and a sending/receiving part,
wherein said memory stores an address common to said plurality of VPN client devices and encrypting information common to said plurality of VPN client devices, said common address and said common encrypting information being paired,
wherein said sending/receiving part sends said common address and said common encrypting information that are paired to said plurality of VPN client devices, and
wherein one of said plurality of VPN client devices, when receiving an IP packet that is encrypted according to said encrypting information and has said common address from said sending/receiving part, transfers said encrypted IP packet to a VPN client device other than said one of said plurality of VPN client devices as is.

### Claim 2 (depends on 1)

The server according to claim 1,
wherein said server changes said encrypting information for notifying a VPN client device belonging to a new VPN group if the configuration of a VPN group formed in said plurality of VPN client devices is changed.

### Claim 3 (depends on 1)

The server according to claim 1,
wherein said common address of said plurality of VPN client devices is a multicast address.

### Claim 4 (depends on 1)

The server according to claim 1,
wherein said encrypting information is security association generated for each common address of said plurality of VPN client devices.

### Claim 5 (depends on 1)

The server according to claim 1,
said encrypting information is at least any one of an encrypting algorithm, a key, and a security parameter index generated for each common address of said plurality of VPN client devices.

### Claim 6

A VPN client device connected at least to a different VPN client through a network, including:
a memory for storing an address and encrypting information common to said different VPN client device respectively, said common address and said common encrypting information being paired; and
a sending/receiving part for sending an IP packet that is encrypted according to said encrypting information, addressed to said common address, and encapsulated.

### Claim 7 (depends on 6)

The VPN client device according to claim 6,
wherein said sending/receiving part can receive both of said common address and said common encrypting information from any VPN server connected through said network.

### Claim 8 (depends on 6)

The VPN client device according to claim 6,
wherein said common address is a multicast address.

### Claim 9 (depends on 6)

The VPN client device according to claim 6,
wherein said common address is a multicast address.

### Claim 10

A VPN system having a server and a plurality of VPN client devices connected to itself through a network,
wherein said server includes:
a memory for storing both of said common address and said common encrypting information of said plurality of VPN client devices, said common address and said common encrypting information being paired; and
an interface for notifying said plurality of VPN client devices of both of said common address and said common encrypting information of said plurality of VPN client devices,
wherein each of said plurality of VPN client devices includes:
a memory for storing both of said common address and said common encrypting information of said plurality of VPN client devices, said common address and said common encrypting information being paired; and
an interface for sending an IP packet that is encrypted according to said common encrypting information, addressed to said common address, and encapsulated again with another IP packet to said server.

### Claim 11

A software program that enables a controller of a server to execute a VPN generating method, said server being connected to a plurality of VPN client devices and including said controller, a memory, and a sending/receiving part, said method including:
a step of storing said common address and said common encrypting information of said plurality of VPN client devices in said memory; and
a step of sending both of said common address and said common encrypting information received from said sending part to said plurality of VPN client devices.
