switch

A switch with integrated ASIC or FPGA handles VPN encryption and decryption, addressing CPU resource usage issues in VPNs by bypassing server CPUs, ensuring efficient application execution and communication speed.

JP7948315B2Active Publication Date: 2026-11-11NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2024526152
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-06-09
Publication Date
2026-11-11
Estimated Expiration
2042-06-09

AI Technical Summary

Technical Problem

The use of a server's CPU for encryption and decryption in VPNs can affect the execution of other applications, leading to reduced efficiency.

Method used

A switch configured to relay VPN data using an ASIC or FPGA for encryption and decryption, bypassing the server's CPU resources.

Benefits of technology

Enables VPN encryption and decryption without utilizing server CPU resources, maintaining application efficiency and reducing communication speed reductions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007948315000001
    Figure 0007948315000001
  • Figure 0007948315000002
    Figure 0007948315000002
  • Figure 0007948315000003
    Figure 0007948315000003
Patent Text Reader

Abstract

A switch (10) is configured to relay data that is transmitted and received between virtual private network (VPN) peers. The switch (10) comprises a first circuit (20 and 11A) that transmits a packet via a VPN by encrypting a packet from any one of first VPN peer computers (41-43) and transmitting the encrypted packet to any one of other VPN peer computers (141-143) via a network. This configuration achieves encryption in a VPN without using CPU resources of a server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a switch used in a network.

Background Art

[0002] A technique is known in which the operation and management of a VPN (Virtual Private Network) is performed by utilizing the centralized control plane of an SDN (Software Defined Network) (Non-Patent Document 1). In such a technique, transmission data transmitted and received via the VPN is encrypted or decrypted by an application server.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] When the CPU (Central Processing Unit) of a server such as an application server is used for encryption and decryption for a VPN, this encryption and decryption may affect the execution of other applications by the CPU.

[0005] The present invention has been made in view of the above points, and an object thereof is to implement encryption in a VPN without using the CPU resources of a server.

Means for Solving the Problems

[0006] To solve the above problems, the switch according to the present invention is a switch configured to relay data transmitted and received between a first combination of VPN (Virtual Private Network) peers, and includes a first circuit that encrypts the first data from one of the first combination of VPN peers, or encrypts it using an ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array) on a network interface connected to the switch, and transmits the encrypted first data to the other first device of the first combination of VPN peers via the network, thereby transmitting the first data via VPN. [Effects of the Invention]

[0007] According to the present invention, encryption in a VPN can be achieved without using the server's CPU resources. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a diagram illustrating the configuration of a VPN communication system including a switch according to the first embodiment of the present invention. [Figure 2] Figure 2 is a diagram showing the configuration of the switch in Figure 1. [Figure 3] Figure 3 is a configuration diagram showing the details of the first packet processing circuit in Figure 2. [Figure 4] Figure 4 is a configuration diagram showing the details of the second packet processing circuit in Figure 2. [Figure 5] Figure 5 is a configuration diagram of a switch according to a second embodiment of the present invention. [Figure 6] Figure 6 is a configuration diagram showing the details of the first packet processing circuit in Figure 5. [Figure 7] Figure 7 is a configuration diagram showing the details of the second packet processing circuit in Figure 5. [Modes for carrying out the invention]

[0009] Embodiments of the present invention will be described below with reference to the drawings.

[0010] (First Embodiment) As shown in Figure 1, a switch 10 according to the first embodiment of the present invention is connected to a plurality of computers 41-43, and a router 50 connected to a network NW such as the Internet. The switch 10, the plurality of computers 41-43, and the router 50 are installed at Site A.

[0011] Site B, which is different from Site A, has a switch 110, multiple computers 141-143, and a router 150. Switch 110 has the same configuration as switch 10, is connected to multiple computers 141-143, and is also connected to router 150, which is connected to the network NW.

[0012] Computers 41-43 are, for example, host or client computers and can communicate with each other via switch 10. Furthermore, computers 41-43 can communicate with computers 141-143 via router 50, network NW, router 150, and switch 110. In particular, in this embodiment, communication using IPsec (Security Architecture for Internet Protocol)-VPN (Virtual Private Network) is possible. Hereinafter, IPsec-VPN will also be simply referred to as VPN. A pair of any one of computers 41-43 and any one of computers 141-143 that communicate via VPN constitutes a VPN peer. Switches 10 and 110 are configured to relay data transmitted and received between multiple combinations of VPN peers.

[0013] At site C, an SDN (Software Defined Network) controller C1 that integrally manages communication devices of sites A and B, such as switches 10 and 110, and routers 50 and 150, is disposed. The SDN controller C1 is connected to a network NW via a router (not illustrated) or the like.

[0014] In this embodiment, encryption and decryption required for VPN communication are performed by switches 10 and 110. This enables VPN communication that does not utilize the CPU resources of various servers. Switch 10 and switch 110 have the same configuration. Hereinafter, switch 10 will be described.

[0015] As shown in Figure 2, the switch 10 includes a plurality of ports P1 to Pn (where n is the total number of ports), a controller 11, a table memory 12, an interface circuit 15, a first packet processing circuit 20, and a second packet processing circuit 30. The numeric part of the reference signs of ports P1 to Pn is defined as the port number of each port. For example, the port number of port P3 is "3". Ports P1 to Pn are also collectively referred to as port P.

[0016] Computers 41 to 43 are connected to ports P1 to P3 respectively. A router 50 is connected to port P4. It is assumed that computers are also connected to the other ports P.

[0017] The controller 11 includes a CPU (Central Processing Unit) 11A, a main memory 11B for the CPU 11A, and a non-volatile memory 11C that stores programs and data for causing the CPU 11A to operate as will be described later. The controller 11 (the CPU 11A executing the programs) controls the entire switch 10 and performs operations to be described later.

[0018] The table memory 12 is composed of a RAM (Random Access Memory), and stores various tables such as a MAC (Media Access Control address) table, an SPD (Security Policy Database), an encryption rule table, and a decryption rule table. Each table is managed by the controller 11 and the SDN controller C1. For example, the SDN controller C1 communicates with the controller 11 via the network NW, the router 50, the port P4, the interface circuit 15 and the like, and manages the content of the SPD via the controller 11. The controller 11 and the SDN controller C1 preferably perform encrypted communication via a VPN or the like. The controller 11 and the SDN controller C1 may be connected via a dedicated line for security purposes.

[0019] When packets are input from the computers 41 to 43 to the ports P1 to P3, the interface circuit 15 transfers the packets to the first packet processing circuit 20. When a packet is input from the router 50 to the port P4, the interface circuit 15 transfers the packet to the second packet processing circuit 30.

[0020] The first packet processing circuit 20 performs processing of transferring a packet from the interface circuit 15 to the port P corresponding to its destination. This destination includes the computers 141 to 143. Details of the first packet processing circuit 20 will be described later.

[0021] The second packet processing circuit 30 performs processing of transferring a packet from the interface circuit 15 to the port P corresponding to its destination. The destination ports P are mainly the ports P1 to P3. Details of the second packet processing circuit 30 will be described later.

[0022] The table memory 12, the first packet processing circuit 20, and the second packet processing circuit 30 may be provided, for example, in an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array). In this case, the table memory 12 is configured as BRAM (Block Random Access Memory) or SRAM (Static Random Access Memory) on the ASIC or FPGA.

[0023] As shown in Figure 3, the first packet processing circuit 20 includes a parser module 21, an SPD matching module 22, an encryption module 23, a forwarder module 24, and a deparser module 25.

[0024] The parser module 21 analyzes the packet from the interface circuit 15 and generates header identification information that specifies the range of the header within the entire packet. The parser module sends the packet along with the header identification information to the SPD matching module 22. From this point onward, the packet header is identified by the header identification information sent along with the header.

[0025] The SPD matching module 22 references the SPD using the source and destination IP address pairs and the type of communication protocol included in the packet header as keys. The SPD shows the correspondence between the source and destination IP address pairs, the type of communication protocol, and the action. The aforementioned actions include "encryption" and "bypass".

[0026] In SPD, the "Encrypt" action is set for each combination of source and destination IP address pairs configured as targets for VPN communication, and the type of communication protocol used for communication between these sources and destinations. In SPD, the "Bypass" action is set for each combination of source and destination IP address pairs configured as not targets for VPN communication, and the type of communication protocol used for communication between these sources and destinations. Note that the type of communication protocol may be omitted as appropriate for SPD and the key used when referencing SPD.

[0027] The SPD matching module 22 obtains from the SPD the action corresponding to the combination that matches the key. If the obtained action is "encrypt," the SPD matching module 22 sends the packet and header identification information to the encryption module 23. If the obtained action is "bypass," the SPD matching module 22 sends the packet and header identification information to the forwarder module 24. If there is no combination that matches the key, the SPD matching module 22 discards the packet to be processed.

[0028] The encryption module 23 sends packets from the SPD matching module 22 to the controller 11 (CPU 11A) along with encryption instructions. At this time, the encryption module 23 refers to the encryption rule table. The encryption rule table shows the correspondence between each pair of source and destination IP addresses and an encryption rule. An encryption rule is information that includes the type of encryption algorithm and the encryption key. The encryption module 23 retrieves the encryption rule corresponding to each pair of source and destination IP addresses contained in the packet header from the encryption rule table and supplies the rule to the controller 11. The encryption module 23 stores predetermined information such as the IP address and MAC address in the packet header in memory or elsewhere.

[0029] The controller 11 encrypts packets from the encryption module 23 based on the encryption rules provided by the encryption module 23. The controller 11 then returns the encrypted packets to the encryption module 23 as encrypted packets.

[0030] The encryption module 23 generates a new header based on the predetermined information described above and encapsulates the encrypted packet from the controller 11 by adding the generated new header. The encryption module 23 sends the encapsulated encrypted packet to the forwarder module 24 along with header identification information that specifies the range of the new header. The new header contains encrypted information indicating that subsequent packets are encrypted.

[0031] The forwarder module 24 forwards the packet and its header identification information received from module 22 or 23 to port P, which corresponds to the destination MAC address contained in the header, via the deparser module 25 and interface circuit 15. The port number corresponding to the MAC address is identified by referring to a MAC table that shows the correspondence between MAC addresses and port numbers (the same applies to the identification of port numbers hereafter).

[0032] The deparser module 25 removes the header identification information from the packets and header identification information forwarded from the forwarder module 24 to port P. In other words, the header identification information is not forwarded to port P. The deparser module 25 may generate a new header depending on the type of communication protocol included in the header. When the deparser module 25 generates a new header, it adds this header to the packet and sends it to port P.

[0033] Packets forwarded to port P by forwarder module 24 are then sent to the destination with the destination MAC address, and finally to the destination with the destination IP address. This transmission enables VPN communication if the packet is an encapsulated encrypted packet, and normal communication if the packet is not encrypted. Thus, both normal and VPN communication occur depending on whether the packet is encrypted or not.

[0034] The encryption and forwarding processes for the packets described above to port P are also performed on switch 110.

[0035] As shown in Figure 4, the second packet processing circuit 30 includes a parser module 31, a decoding module 32, a forwarder module 33, and a deparser module 34.

[0036] The parser module 31 analyzes the packet from the interface circuit 15 and generates header identification information that identifies the range of the header within the entire packet. If the header contains encrypted information, the parser module 31 sends this packet, along with the header identification information, to the decryption module 32. In this case, the packet becomes an encapsulated encrypted packet from computers 141-143 that was transmitted via the VPN by being encrypted at switch 110 in the same manner as described above. If the header does not contain encrypted information, the parser module 31 determines that this packet was not transmitted via VPN communication. In this case, the parser module 31 bypasses this packet, along with the header identification information, to the forwarder module 33.

[0037] The decryption module 32 sends the encrypted packet, with the header removed, from the packet sent from the parser module 31 to the controller 11. At this time, the decryption module 32 refers to the decryption rule table. The decryption rule table shows the correspondence between each pair of source and destination IP addresses and a decryption rule. A decryption rule is information that includes the type of decryption algorithm and the decryption key. The decryption module 32 retrieves the decryption rule corresponding to each pair of source and destination IP addresses included in the packet header from the decryption rule table and supplies the decryption rule to the controller 11.

[0038] Controller 11 decrypts encrypted packets from decryption module 32 based on decryption rules from decryption module 32. Controller 11 returns the decrypted packets to decryption module 32 as decrypted packets. Decryption module 32 sends the returned decrypted packets and the header attached to the beginning of the packets (hereinafter also referred to as the leading header) as a single packet to forwarder module 33 along with header identification information from parser module 31.

[0039] The forwarder module 33 forwards packets from the parser module 31 or the decryption module 32 to port P, which has a port number corresponding to the MAC address included in the header, via the deparser module 34 and the interface circuit 15.

[0040] The deparser module 34 removes the header (or the leading header if the packet contains a decrypted packet) and header identification information if the header contains encrypted information. As a result, only the decrypted packet is forwarded to port P. If the header does not contain encrypted information, the deparser module 34 removes the header identification information. The decrypted or unencrypted packet forwarded to port P is sent to one of the destination computers 41-43. As a result, in the former case, the decryption and reception of the packet sent via VPN are achieved, and in the latter case, normal communication without encryption takes place.

[0041] As described above, the switch 10 according to this embodiment includes a first circuit (first packet processing circuit 20 and CPU 11A) that encrypts packets from one of the computers 41 to 43 of the VPN peer and transmits the encrypted packets to one of the other computers 141 to 143 of the VPN peer via the network NW, thereby transmitting packets via VPN. The devices constituting the VPN peer are not limited to computers, but may also be other communication devices such as switches or routers. With this configuration, packet encryption is performed by the switch 10, so VPN encryption is achieved without using CPU resources such as those of an application server. This suppresses disadvantages such as a decrease in the execution efficiency of other applications due to CPU resources.

[0042] Switch 10 further includes a second circuit (second packet processing circuit 30 and CPU 11A) that decrypts packets transmitted via VPN from the other VPN peer computer 141-143 over the network NW, and transmits the decrypted packets to the other VPN peer computer 41-43. With this configuration, packet decryption is performed by switch 10, enabling VPN decryption without using CPU resources from application servers or other devices. The devices constituting the VPN peer are not limited to computers; they may also be other communication devices such as switches or routers.

[0043] Furthermore, the first circuit receives a packet from a first port P connected to one of the computers 41-43 of the VPN peer, and determines whether the received packet is subject to VPN communication by referring to the SPD. When the first circuit determines that the packet is subject to VPN communication, it encrypts the packet and forwards the encrypted packet to a second port P connected to the network NW to which the other computers 141-143 of the VPN peer are connected. When the first circuit determines that the packet is not subject to VPN communication, it forwards the packet to the second port P without encrypting it. With this configuration, the switch 10 can also have a non-VPN packet forwarding function, which is a conventional packet forwarding function.

[0044] Furthermore, in this embodiment, multiple types of VPNs are provided with different combinations of VPN peers and / or different encryption or decryption methods, and these multiple types of VPNs are aggregated at switch 10. As a result, the computing resources for encryption and decryption within the site are aggregated at switch 10, thereby consolidating and improving the efficiency of encryption and decryption computing resources. In this embodiment, multiple types of VPNs are realized by providing multiple pairs of destination and source IP addresses corresponding to the "encryption" of the SPD, and / or by setting different rules in the encryption and decryption rule table according to different pairs of destination and source IP addresses, but the method for realizing multiple types of VPNs is arbitrary.

[0045] In the above embodiment, the second circuit decrypts a packet received from the second port P if it is encrypted, and forwards the decrypted packet to the first port P. If the packet received from the second port P is not encrypted, it forwards the packet to the first port P without decrypting it. As a result, the switch 10 can also have a non-VPN forwarding function, which is a conventional packet forwarding function.

[0046] In the above embodiment, encryption and decryption are performed by the CPU 11A that controls the operation of the switch 10, thus simplifying the configuration for the encryption and decryption processes. Encryption may be performed by the encryption module 23 of the first packet processing circuit 20 instead of the CPU 11A. Decryption may be performed by the decryption module 32 of the second packet processing circuit 30 instead of the CPU 11A.

[0047] Switch 10 is originally used as a communication device that relays packets sent and received between any of computers 41-43 and any of computers 141-143, that is, between VPN peers. Therefore, encryption and decryption are performed without increasing the number of relay points for packets sent and received between VPN peers, thus suppressing the reduction in communication speed that would occur if new relay points such as application servers were established. In this way, according to this embodiment, the reduction in communication speed of VPN communication is suppressed.

[0048] Regarding VPN communication, it is conceivable to have a server called a middlebox between the switch and the router, with the middlebox's CPU performing VPN encryption and decryption. However, in this embodiment, such a middlebox is unnecessary. This improves site operability and power efficiency. Furthermore, it prevents the overall communication performance of the system from degrading due to poor performance of the middlebox.

[0049] (Second Embodiment) As shown in Figure 5, the switch 60 according to this embodiment includes a first packet processing circuit 70 and a second packet processing circuit 80 instead of the first packet processing circuit 20 and the second packet processing circuit 30 of the switch 10 according to the first embodiment. Furthermore, encryption and decryption of packets in the VPN are performed by encryption devices 41A and decryption devices 42A, respectively, provided in computers 41 and 42. Encryption devices 41A and decryption devices 42A are configured as ASICs or FPGAs mounted on smart NICs, etc., and are connected to the switch 60. Encryption devices 41A and decryption devices 42A may be configured as ASICs or FPGAs of network interfaces, for example, or they may be provided on the ASICs or FPGAs of the smart NIC of the router 50. The following description will focus on the differences between the first and second embodiments.

[0050] As shown in Figure 6, the first packet processing circuit 70 includes a parser module 71, an SPD matching module 22, forwarder modules 73 and 75, and deparser modules 74 and 76.

[0051] The parser module 71 receives packets from ports P1 to P3. If the encryption device 41A is configured with network interfaces of devices other than the computer 41, such as the router 50's NIC, the parser module 71 also receives packets from port P connected to that network interface (details will be described later). With this configuration, the parser module 71 is supplied with both unencrypted and encrypted packets.

[0052] The parser module 71 analyzes packets from the interface circuit 15, similar to the first embodiment, and generates header identification information that identifies the range of the header within the entire packet. The parser module 71 also determines whether the header contains encrypted information.

[0053] If the header does not contain encrypted information, the parser module 71 sends the packet and header identification information to the SPD matching module 22. The SPD matching module 22 has the same configuration as in the first embodiment and obtains an action from the SPD corresponding to the combination that matches the key. If the obtained action is "encrypt", the SPD matching module 22 sends the packet along with the header identification information to the forwarder module 73. If the obtained action is "bypass", the SPD matching module 22 sends the packet and header identification information to the forwarder module 75. If there is no combination that matches the key, the SPD matching module 22 discards the packet to be processed.

[0054] The forwarder module 73 sends the packet and header identification information to port P (in this case, port P1) on the port number to which the encryption device 41A is connected, via the deparser module 74 and interface circuit 15. The deparser module 74 removes the header identification information and sends the packet to port P along with the encryption instruction. The packet and encryption instruction sent to port P are then transmitted to the encryption device 41A.

[0055] When the encryption device 41A receives a packet and an encryption instruction, it encrypts the packet by referring to its stored encryption rule table. The encryption device 41A retrieves encryption rules from the encryption rule table corresponding to each source and destination IP address pair included in the packet header, and encrypts the packet based on the retrieved encryption rules. The encryption device 41A generates a new header based on predetermined information such as the IP address and MAC address in the packet header before encryption, and encapsulates the encrypted packet by adding this header to the encrypted packet. The new header also includes the encrypted information. The encryption device 41A sends the encapsulated encrypted packet and the new header as a single packet and a reply to the encryption instruction to port P1 connected to the encryption device 41A, i.e., computer 41. The packet sent to port P1 as a reply to the encryption instruction is sent to the parser module 71 via the interface circuit 15. The encryption rule table is managed by the SDN controller C1 via the network NW, port P, etc., as in the first embodiment.

[0056] If the header contains encrypted information, the parser module 71 sends the encapsulated encrypted packet and the header identification information obtained by analyzing this packet to the forwarder module 75.

[0057] The forwarder module 75 forwards packets and header identification information from the parser module 71 or the SPD matching module 22 to port P, which has a port number corresponding to the destination MAC address included in the header, via the deparser module 76 and the interface circuit 15.

[0058] The deparser module 76 removes the header identification information from the packet and header identification information forwarded from the forwarder module 75 to port P. The deparser module 76 may generate a new header depending on the type of communication protocol included in the header. When the deparser module 76 generates a new header, it adds this header to the packet and sends it to port P.

[0059] Packets forwarded to port P by forwarder module 75 are sent to the destination with the destination MAC address, and finally to the destination with the destination IP address. This transmission enables VPN communication if the packet is an encapsulated encrypted packet, and normal communication if the packet is not encrypted. Thus, both normal and VPN communication occur depending on whether the packet is encrypted or not.

[0060] As shown in Figure 7, the second packet processing circuit 80 includes a parser module 81, forwarder modules 83 and 85, and deparser modules 84 and 86.

[0061] The parser module 81 receives packets from port P4 via the interface circuit 15. The parser module 81 also receives packets from port P2 to which the decryption device 42A, i.e., computer 42, is connected (the decrypted packets described later) via the interface circuit 15. If the decryption device 42A is configured with a network interface of a device other than computer 41, such as the NIC of router 50, the parser module 71 receives packets from port P connected to that network interface via the interface circuit 15 (details will be described later). With this configuration, the parser module 71 is supplied with both undecrypted and decrypted packets.

[0062] The parser module 81 analyzes the packet from the interface circuit 15 and generates header identification information that identifies the range of the header within the entire packet. The parser module 71 also determines whether the header contains encrypted information.

[0063] If the header contains encrypted information, the parser module 81 sends the packet (encapsulated encrypted packet) and header identification information to the forwarder module 73.

[0064] The forwarder module 83 sends the packet and header identification information to port P2, which is port P corresponding to the MAC address of the decryption device 42A, via the deparser module 84. The deparser module 84 removes the header identification information and sends the packet along with the decryption instruction to port P2. The packet (encapsulated encrypted packet) and the decryption instruction sent to port P2 are then transmitted to the decryption device 42A.

[0065] When the decryption device 42A receives a packet and a decryption instruction, it refers to its stored decryption rule table and decrypts the encrypted packet within the packet. The decryption device 42A retrieves a decryption rule from the decryption rule table corresponding to each source and destination IP address pair included in the packet header, and decrypts the encrypted packet based on the retrieved decryption rule. The decryption device 42A sends the decrypted encrypted packet as a reply to the decryption instruction to port P2 connected to the decryption device 42A, i.e., computer 42. The packet sent to port P1 as a reply to the decryption instruction is sent to the parser module 81 via the interface circuit 15. The decryption rule table is managed by the SDN controller C1 via the network NW, port P, etc., as in the first embodiment.

[0066] If the header does not contain encrypted information, the parser module 81 sends header identification information to the forwarder module 85.

[0067] The forwarder module 85 forwards the packet and header identification information from the parser module 81 to port P, which corresponds to the destination MAC address included in the header, via the deparser module 86.

[0068] The deparser module 86 removes the header identification information from the packet and header identification information forwarded from the forwarder module 85 to port P. The deparser module 86 may generate a new header depending on the type of communication protocol included in the header. When the deparser module 86 generates a new header, it adds this header to the packet and sends it to port P.

[0069] Packets forwarded to port P by forwarder module 85 are sent to the destination with the destination MAC address, and finally to the destination with the destination IP address. This transmission enables VPN communication if the packet is a decrypted packet, and normal communication if the packet was not originally encrypted. Thus, both normal and VPN communication occur depending on whether the packet is encrypted or not.

[0070] According to this embodiment, the switch 60 in this embodiment includes a first circuit (first packet processing circuit 70) that encrypts packets from one of the computers 41 to 43 of the VPN peer using an encryption device 41A connected to the switch 60, i.e., an ASIC or FPGA of the network interface, and transmits the encrypted packets to one of the other computers 141 to 143 of the VPN peer via the network NW, thereby transmitting packets via VPN.

[0071] Switch 60 further includes a second circuit (second packet processing circuit 80) that decodes packets sent via VPN from the other VPN peer computer 141-143 over the network NW using a decoder 42A connected to switch 60, i.e., an ASIC or FPGA on the network interface, and transmits the decoded packets to one of the VPN peer computers 41-43.

[0072] With the above configuration, the same effects as in the first embodiment can be obtained, and since the CPU 11A of the switch 60 is not used for encryption and decryption in VPN communication, the throughput and power consumption of the switch 60 are reduced accordingly.

[0073] (modified version) Various modifications are possible to the above embodiment. For example, port P on the switch may be a port connected to another network, such as a corporate LAN (Local Area Network). Port P may be a port dedicated to VPN or a port dedicated to non-VPN. A VPN other than IPsec-VPN may be used as the VPN. The switch can be a switching hub, a network switch, or the like.

[0074] (Scope of the present invention) The present invention is not limited to the embodiments and modifications described above. For example, the present invention includes various modifications to the embodiments and modifications described above that can be understood by those skilled in the art within the scope of the technical concept of the present invention. The configurations listed in the embodiments and modifications described above can be combined as appropriate to the extent that they do not contradict each other. It is also possible to delete any of the above configurations.

[0075] (Note) Examples of configurations disclosed herein, including the embodiments and modifications described above, are illustrated below. (Note 1) A switch configured to relay data transmitted and received between a first combination of VPN (Virtual Private Network) peers, comprising a first circuit that encrypts the first data from one of the first combination of VPN peers, or encrypts it using an ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array) on a network interface connected to the switch, and transmits the encrypted first data to the other first device of the first combination of VPN peers via the network, thereby transmitting the first data via VPN. (Note 2) The switch according to Appendix 1, further comprising a second circuit for decoding the first-second data transmitted from the first-second devices via VPN over the network, or for decoding it using an ASIC or FPGA of a network interface connected to the switch, and transmitting the decoded first-second data to the first-first device. (Note 3) The switch described in Appendix 1 or 2, wherein the first circuit receives the first data from a first port connected to the first device, determines whether the received first data is subject to VPN communication, encrypts the first data or has it encrypted by the ASIC or FPGA when it is determined to be subject to VPN communication, and transfers the encrypted first data to a second port connected to the network, and when it is determined not to be subject to VPN communication, transfers the first data to the second port without encryption. (Note 4) The switch described in any of Appendix 1 to 3, wherein the first circuit encrypts the second data from one of the second combination VPN peers, the second data, using a second rule different from the rule used to encrypt the first data, or has the ASIC or FPGA of the network interface connected to the switch encrypt the second data using the second rule, and transmits the encrypted second data to the other of the second combination VPN peers, the second data, via the network, thereby transmitting the second data via VPN. (Note 5) The switch according to any one of the appendices 2 to 4, wherein the second circuit, when the first-second data received from the second port connected to the network is encrypted, decrypts the first-second data, or has the ASIC or FPGA of the network interface connected to the switch decrypt it, and transfers the decrypted first-second data to the first port connected to the first-first device, and when the first-second data received from the second port is not encrypted, transfers the first-second data to the first port without decrypting it. (Note 6) The switch according to any one of the appendices 1 to 5, wherein the first circuit is configured to encrypt the 1-1 data, and includes a CPU that controls the operation of the switch and encrypts the 1-1 data. [Explanation of Symbols]

[0076] 10, 60, 110…Switch, 11…Controller, 11A…CPU, 12…Table memory, 15…Interface circuit, 20…First packet processing circuit, 21…Parser module, 22…SPD matching module, 23…Encryption module, 24…Forwarder module, 25…Deparser module, 30…Second packet processing circuit, 31…Parser module, 32…Decryption module, 33…Forwarder module, 34…Deparser module, 41~43…Computer, 41A…Encryption device, 42A…Decryption device, 50…Router, 60...Switch, 70...First packet processing circuit, 71...Parser module, 73...Forwarder module, 74...Departer module, 75...Forwarder module, 76...Departer module, 80...Second packet processing circuit, 81...Parser module, 83...Forwarder module, 84...Departer module, 85...Forwarder module, 86...Departer module, 110...Switch, 141~143...Computer, 150...Router, A...Site, B...Site, C...Site, C1...SDN controller, P,P1~Pn...Port.

Claims

1. A switch configured to relay data transmitted and received between first combinations of VPN (Virtual Private Network) peers, The first circuit transmits the data via VPN by encrypting the data from the first-first device of one of the first combination of VPN peers using an ASIC (Application Specific Integrated Circuit) or FPGA (Field-Programmable Gate Array) on the network interface of a device different from the switch that is connected to the switch, and then transmitting the encrypted data to the other first-second device of the first combination of VPN peers via the network. switch.

2. The system further includes a second circuit that decodes the first-second data transmitted from the first-second devices via VPN over the network using an ASIC or FPGA on the network interface of a device different from the switch that is connected to the switch, and transmits the decoded first-second data to the first-first device. The switch according to claim 1.

3. The first circuit is, The first port connected to the first device receives the first data, Determine whether the received data 1-1 is subject to communication via VPN. When it is determined that the data is subject to communication via the VPN, the 1-1 data is encrypted by the ASIC or FPGA, and the encrypted 1-1 data is transferred to the second port connected to the network. When it is determined that the communication is not subject to the VPN, the 1-1 data is transferred to the 2 port without encryption. The switch according to claim 1.

4. The first circuit transmits the second data via VPN by having the second-1 device of one of the second combination VPN peers encrypt the second data using a rule different from the rule used to encrypt the first-1 data, by having the ASIC or FPGA of the network interface of a device different from the switch that is connected to the switch, and then transmitting the encrypted second data to the other second-2 device of the second combination VPN peer via the network. The switch according to claim 1.

5. The second circuit is, If the 1-2 data received from the second port connected to the network is encrypted, the 1-2 data is decrypted by the ASIC or FPGA, and the decrypted 1-2 data is transferred to the first port connected to the 1-1 device. If the first-second data received from the second port is not encrypted, the first-second data is forwarded to the first port without decryption. The switch according to claim 2.

6. The first circuit includes a CPU that controls the operation of the switch. The switch according to claim 1.

Citation Information

Patent Citations

  • Network nodes using network-attached stateless security offload devices

    JP2015511434A

  • System and method for a secure I / O interface

    US20050076228A1

  • Policy-based configuration of internet protocol security for a virtual private network

    US20130298182A1

  • Method to save computational resources by detecting encrypted payload

    US20200186507A1

  • Automatic virtual private network internet snoop avoider

    US6473863B1