Relay device, relay method, and program
The relay device improves resource and network efficiency in communication systems by managing addresses and converting packet destinations, addressing inefficiencies in current systems and enabling stable, low-latency communication for autonomous driving applications.
Patent Information
- Application Number
- PCT/JP2023/020280
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2024-12-05
AI Technical Summary
Current communication systems using multiple transport protocols, such as HTTP/3, QUIC, and MPTCP, face inefficiencies in resource utilization and network management, particularly in autonomous driving applications where multiple terminals require stable and low-latency communication, leading to increased load on terminals and inefficient resource usage.
A relay device configuration that manages addresses and converts packet destinations within a communication system, allowing for efficient data transfer between terminals through address translation and multiplexing, reducing the load on terminals and improving resource utilization by centralizing encryption and congestion control.
This solution enhances resource and network usage efficiency by enabling stable and low-latency communication between terminals, reducing the computational burden on terminals and avoiding conflicts in traffic control, while allowing data transfer without relying on upper protocols like HTTP.
Smart Images

Figure JP2023020280_05122024_PF_FP_ABST
Abstract
Description
Relay device, relay method, and program
[0001] The present invention relates to a communication system in which a plurality of terminals (applications) communicate with one or more transport protocols via a plurality of networks.
[0002] As autonomous driving technology for automobiles continues to develop, limited level 4 driving, in which the system takes over the primary driving operations, is beginning to be approved in Japan.
[0003] With regard to autonomous driving technology, remote vehicle monitoring and control support are required from the perspective of accident prevention. Vehicle monitoring requires that monitors can receive images from multiple cameras inside and outside the vehicle in real time. Control support must also be possible without delay or loss. It is also anticipated that various communications will be required for infotainment systems such as navigation and entertainment.
[0004] On the other hand, with current mobile communications such as LTE and 5G, it is difficult to stably meet these communication requirements with a single line due to congestion and radio wave conditions.
[0005] In response to this, conventional technologies have proposed mechanisms to achieve low latency and stability, such as MPTCP and QUIC's Multipath extension, which combine multiple lines at the transport layer, and mechanisms that utilize these.
[0006] "The MASQUE Protocol," draft-schinazi-masque-00 https: / / datatracker.ietf.org / doc / html / draft-schinazi-masque-00"Tunneling Internet protocols inside QUIC," draft-piraux-quic-tunnel-03 https: / / datatracker.ietf.org / doc / html / draft-piraux-quic-tunnel-03"Enabling application policy-awareness in Multipath QUIC," draft-an-multipath-quic-application-policy-00 https: / / datatracker.ietf.org / doc / html / draft-an-multipath-quic-application-policy-00#ref-MPQUIC-Scheduler
[0007] In conventional technologies, terminals are equipped with communication functions using HTTP / 3, QUIC, MPTCP, etc., which allows for the use of multiple lines and communication multiplexing. This increases the load on the terminals and also leads to inefficient use of resources (computing resources, network resources, etc.).
[0008] The present invention has been made in consideration of the above points, and aims to provide a technology that enables improving the efficiency of resource utilization in a communication system in which communication is carried out between terminals using one or more transport protocols.
[0009] According to the disclosed technology, there is provided a relay device constituting a communication system having a plurality of relay devices connected by one or more networks, the relay device comprising at least an address management unit that registers sending and receiving addresses for communication between terminals, an address conversion unit that converts the destination address of a packet received from a terminal, and a transport unit that receives the packet after the destination address conversion from the address conversion unit and transfers the data of the packet using a transport connection between the relay devices by referring to the address management unit.
[0010] According to the disclosed technology, it is possible to improve the efficiency of resource utilization in a communication system in which communication is performed between terminals using one or more transport protocols.
[0011] FIG. 1 is a diagram illustrating an example of the configuration of a communication system. FIG. 1 is a diagram illustrating an example of the configuration of a relay device 10. FIG. 2 is a sequence diagram illustrating a transfer start method for TCP communication. FIG. 3 is a sequence diagram illustrating a transfer method 1 for UDP communication. FIG. 4 is a sequence diagram illustrating a transfer method 2 for UDP communication. FIG. 5 is a sequence diagram illustrating a transfer method for IP communication. FIG. 6 is a flowchart illustrating a transfer switching method for UDP and IP communication. FIG. 7 is a sequence diagram illustrating UDP transfer using a logical path. FIG. 8 is a diagram illustrating an example of the configuration of a communication system in Example 2. FIG. 9 is a sequence diagram in Example 2. FIG. 10 is a diagram illustrating an example of the hardware configuration of the device.
[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.
[0013] Below, we will explain technology related to a relay device that terminates communication flows, multiplexes them into a single connection, and forwards them in an environment where multiple communication terminals (applications) communicate using various transport protocols via multiple networks, thereby improving the computing resources of the terminals and the efficiency of network utilization.
[0014] In the following, first, the conventional technology and its problems will be described, and then the technology according to the present embodiment will be described in detail. Note that, regarding the conventional technology, the technology itself disclosed in the non-patent document is publicly known, but the explanation of the conventional technology and the explanation of the problems below are not publicly known.
[0015] (Regarding the Prior Art) As mentioned above, in the prior art, mechanisms for achieving low latency and stability have been proposed, such as MPTCP and QUIC Multipath extensions that combine multiple lines at the transport layer, and mechanisms that utilize these. Specifically, the prior art includes the following:
[0016] <Prior Art 1: Multiplexed Application Substrate over QUIC Encryption (MASQUE), 2020> Prior Art 1 is a technology disclosed in Non-Patent Document 1. Prior Art 1, MASQUE, is a mechanism for proxying streams and datagram communications encrypted using HTTP, and is being discussed in the IETF standardization working group.
[0017] MASQUE uses the HTTP CONNECT method, which includes destination information, and an HTTP / 3 proxy that receives a forwarding request from a client forwards QUIC stream frames or datagram frames to the original destination (TCP or UDP is used in HTTP / 2 and earlier).
[0018] <Prior Art 2: Tunneling Internet protocols inside QUIC, 2019> Prior Art 2 is a technique disclosed in Non-Patent Document 2. Prior Art 2 specifies the following Method 1 and Method 2 as tunneling methods using QUIC.
[0019] Method 1: The source packet is stored directly in the payload of the datagram frame. There is no specific specification for the signaling method.
[0020] Method 2: The protocol type and a 2-byte tag are added to the beginning of the datagram frame to store the source packet. Examples of tag usage include timestamps and packet numbers.
[0021] Prior art 2 also defines a method for joining a multi-path session.
[0022] <Prior Art 3: (enhanced) Access Traffic Steering, Switching, and Splitting ((e)ATSSS)> Prior Art 3 is a technology disclosed in Non-Patent Document 3. Prior Art 3 ATSSS is a standard that provides an MPTCP proxy function in the UE and 5G UPF, and uses MPTCP between the UE and UPF to simultaneously use 3GPP and non-3GPP access. eATSSS utilizes the Multipath extension of QUIC, and consideration is being given to supporting communications other than TCP and adding transfer modes.
[0023] (Issues) Conventional technologies use multiple lines and multiplex communications by equipping terminals with communication functions using HTTP / 3, QUIC, MPTCP, etc. This creates the following issues, especially when multiple terminals exist within the same vehicle.
[0024] - Applications that use conventional TCP or UDP cannot be used as is.
[0025] - High-load processing such as encryption must be performed on devices that do not have sufficient hardware resources such as CPU and memory, such as in-vehicle systems.
[0026] - Because each terminal manages connections using QUIC, MPTCP, etc., quality management and congestion control for multiple lines must be performed separately, resulting in inefficient use of computing resources and networks.
[0027] The configuration and operation of a system / apparatus according to this embodiment for solving the above problems will be described below.
[0028] (System Configuration Example) FIG. 1 shows a configuration example of a communication system according to this embodiment.
[0029] As shown in Fig. 1, this communication system includes a relay device 10-1 and a relay device 10-2. The relay device 10-1 and the relay device 10-2 are connected via a plurality of networks 20-1 to 20-m. In the example of Fig. 1, the networks 20-1 to 20-2 connected to the relay device 10-1 are connected to a wide area network 30-1, and the wide area network 30-1 is connected to the relay device 10-2.
[0030] Terminals 1 to n are connected to the relay device 10-1, and terminals 1' to n' are connected to the relay device 10-2.
[0031] That is, terminals 1 to n communicate with terminals 1' to n' via relay device 10-1, one or more networks, and relay device 10-2. Note that the terminals and relay devices may be virtualized and installed in the same physical terminal. Hereinafter, each embodiment will be described using an example in which communication is performed from terminal 1 to terminal 1'. Embodiments 1 and 2 can be implemented in combination. Furthermore, transfer methods 1 and 2, the IP transfer method, and the transfer method using additional path connections in embodiment 1 can be implemented in any combination.
[0032] (Example 1) In Example 1, a transfer method using address translation will be described. Fig. 2 shows an example of the configuration of relay device 10-1 and relay device 10-2 in Example 1. Since relay device 10-1 and relay device 10-2 basically have the same configuration, "-1" and "-2" will be omitted here for explanation.
[0033] As shown in FIG. 2, the relay device 10 includes a communication I / F for connecting to a terminal, an address conversion unit 11, an address management unit 13, a transport unit 12, and a communication I / F for connecting to one or more networks.
[0034] The address conversion unit 11 performs address conversion. The address management unit 13 manages sending and receiving addresses (source address and destination address) between terminals. The transport unit 12 terminates communication with terminals at L4, multiplexes communication from one or more terminals, and transfers the communication via multiple networks.
[0035] Hereinafter, the operation will be described using an example in which a single QUIC connection using multiple paths is used to connect the transport unit 12-1 of the relay device 10-1 and the transport unit 12-2 of the relay device 10-2.
[0036] (First embodiment: transfer start method for TCP communication) First, a transfer start method for TCP communication will be described.
[0037] TCP communication between terminals is transparently terminated by performing address conversion at the relay device 10, and the TCP communication between terminals is forwarded by mapping it to a stream frame of a QUIC connection connecting between the relay devices 10. When using TCP, SCTP, or other protocols, the forwarding function can be realized by assigning an ID and offset information equivalent to that of the stream frame.
[0038] 3 is a sequence diagram showing the procedure for starting transfer of TCP communication. In the example shown in FIG. 3, the reception of a TCP SYN packet is used as a trigger, but a TCP connection may be established between the terminal 1 and the relay device 10-1 first.
[0039] 3, any TCP communication can be forwarded, but it is also possible to register in advance in the address management unit 13 only the addresses to be forwarded, and forward other communications as IP packets without terminating L4. Hereinafter, when simply written as "address," it means a combination of an IP address and a TCP / UDP port number.
[0040] A TCP connection that starts transfer from terminal 1' to terminal 1 can be realized by performing the procedure of FIG. 3 in the reverse direction.
[0041] Regarding the end of transfer of TCP communication, the disconnection of the TCP connection of either terminal 1 or terminal 1' is used as a trigger to delete the address registration information between relay devices 10 in the same procedure, and the other TCP connection is disconnected.
[0042] The processing procedure will be described below with reference to the sequence diagram of Fig. 3. Note that in the following sequence diagrams, for convenience of description, the relay device 10-1 will be referred to as relay device 1, and the relay device 10-2 will be referred to as relay device 2.
[0043] A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0044] In S1, the terminal 1 transmits a SYN packet requesting connection establishment to the terminal 1'. The address translation unit 11-1 of the relay device 10-1 receives the SYN packet.
[0045] In steps S2 and S3, the address management unit 13-1 checks whether the sender / receiver address information of the SYN packet has been registered, and if not, assigns an unused QUIC stream ID and registers it together with the sender / receiver address information. This stream ID may also be called a flow identifier.
[0046] When a new registration is performed in the address management unit 13-1, in S4, the address management unit 13-1 notifies the address management unit 13-2 of the relay device 10-2 of the assigned stream ID and sending and receiving addresses by storing them in a stream frame using the QUIC connection between the relay devices 10. The stream ID and sending and receiving addresses are registered in the address management unit 13-2.
[0047] When the relay device 10-1 notifies the address of the stream communication, in steps S5 to S7, the transport unit 12-2 of the relay device 10-2 establishes a TCP connection with the notified destination address (terminal 1').
[0048] If the relay device 10-2 has successfully established a TCP connection with the terminal 1', in S8 it notifies the relay device 10-1 that the connection has been established. Thereafter, the address conversion unit 11-1 of the relay device 10-1 converts the destination address of the TCP communication from the terminal 1 to a destination address for the transport unit 12-1 of the relay device 10-1. Note that, for the sake of convenience, S4 and S8 are illustrated as communication between address management units, but in reality, communication is carried out over the QUIC connection established between the transport units.
[0049] In S9, the initially received SYN packet is transferred to transport unit 12-1, and in S10 to S11, a TCP connection is established between terminal 1 and transport unit 12-1 of relay device 10-1.
[0050] If the relay device 10-2 fails to establish a TCP connection with the terminal 1', it notifies the relay device 10-1 of the connection failure, and the relay device 10-1 transmits a TCP RST packet to the terminal 1, thereby terminating the process.
[0051] Thereafter, the TCP packet transmitted from terminal 1 in S12 is address-converted in relay device 10-1 and transferred to transport section 12-1.
[0052] In steps S13 and S14, the transport unit 12-1 refers to (obtains) the stream ID from the source address information from the address management unit 13-1, and in step S15, using the QUIC connection between the relay devices 10, stores the referred stream ID and TCP payload data in the stream frame and transfers the stream frame to the relay device 10-2.
[0053] The transport unit 12-2 of the relay device 10-2 that receives the QUIC stream frame acquires the destination address from the stream ID from the address management unit 13-2 (S16 to S17), and transfers the TCP payload data again using the established TCP connection (S18).
[0054] TCP ACK and other data in the direction from terminal 1' to terminal 1 can be transferred by carrying out a similar procedure from relay device 10-2 to relay device 10-1.
[0055] (Example 1: Transfer Method 1 for UDP Communication) Next, transfer method 1 for UDP communication will be described. In transfer method 1 for UDP communication, similar to the transfer method for TCP communication, flows are identified by mapping unique datagram IDs with sender and receiver addresses. In real-time video distribution applications, stream communication is performed using RTP or the like as a higher-level protocol above UDP. The datagram ID may also be called a flow identifier.
[0056] 4 is a sequence diagram showing the procedure of UDP communication transfer method 1. In the sequence diagram, "par" and the dotted frame mean that the processing in the dotted frame is performed in parallel for multiple terminals.
[0057] At the end of transfer in UDP communication, there is no connection management like in TCP communication, so the address information is deleted by using a timeout process or the like.
[0058] The processing procedure will be described below with reference to the sequence diagram of FIG.
[0059] A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0060] In S1, terminal 1 transmits a UDP packet addressed to terminal 1'. Address management unit 13-1 of relay device 10-1 checks whether the sender / receiver address information of the UDP packet has been registered, and if not, issues a unique datagram ID and registers it together with the sender / receiver address information (S2-S3).
[0061] When a new registration is made in the address registration unit 13-1, in S4, the QUIC connection between the relay devices 10 is used to store the assigned datagram ID and sending and receiving addresses in a datagram frame, thereby notifying the address management unit 13-2 of the relay device 10-2 of these. The datagram ID and sending and receiving addresses are registered in the address management unit 13-2.
[0062] Relay device 10-1 can start forwarding UDP packets in parallel without waiting for the completion of address registration to relay device 10-2. However, if the forwarded UDP packet arrives at relay device 10-2 before the address registration, relay device 10-2 will not know the forwarding destination address. Therefore, it is preferable to perform processing such as buffering for a certain period of time in either relay device 10-1 or 10-2.
[0063] The address conversion unit 11-1 of the relay device 10-1 converts the destination address of the UDP communication from the terminal 1 to a destination address of the transport unit 12-1 of the relay device 10-1, and in S5, the UDP packet is transferred to the transport unit 12-1.
[0064] In steps S6 to S8, the transport unit 12-1 references the datagram ID from the source address information, and using the QUIC connection between the relay devices 10, stores the referenced datagram ID and UDP payload data in the datagram frame, and forwards the datagram frame to the relay device 10-2.
[0065] In steps S9 to S11, the transport unit 12-2 of the relay device 10-2 that received the datagram frame acquires the destination address from the datagram ID for the address management unit 13-2, and transfers the payload data again to the destination address (terminal 1') using UDP communication.
[0066] Note that UDP communication from terminal 1' to terminal 1 can be performed in the same way from relay device 10-2 to relay device 10-1 by reversing the sender and receiver addresses.
[0067] (Example 1: Transfer Method 2 for UDP Communication) Next, transfer method 2 for UDP communication will be described. In transfer method 2 for UDP communication, sender and receiver address information and UDP payload data are directly stored in the QUIC datagram frame and transferred. Compared to transfer method 1, there is no state management, so the delay time until the start of transfer can be reduced and the processing of the relay device 10 can be simplified, but the packet overhead increases by at least 12 bytes for sender and receiver IP addresses and port numbers in the case of IPv4, and 36 bytes in the case of IPv6.
[0068] 5 is a sequence diagram showing the procedure of UDP communication transfer method 2. When transfer of UDP communication is completed, since there is no connection management like in TCP communication, the address information registration is deleted using a timeout process or the like.
[0069] The processing procedure will be described below with reference to the sequence diagram of FIG.
[0070] A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0071] In S1, terminal 1 transmits a UDP packet addressed to terminal 1'. The address management unit 13-1 of relay device 10-1 checks whether the sending and receiving address information of the UDP packet has been registered, and if not, registers the sending and receiving address information (S2 to S3).
[0072] The address conversion unit 11-1 of the relay device 10-1 converts the destination address of the UDP communication from the terminal 1 to a destination address of the transport unit 12-1 of the relay device 10-1, and in S4, the UDP packet is transferred to the transport unit 12-1.
[0073] In steps S5 to S7, the transport unit 12-1 obtains the destination address information from the source address information, and stores the sending and receiving address information and UDP payload data in the datagram frame using the QUIC connection between the relay devices 10, and transfers the datagram frame to the relay device 10-2.
[0074] In the relay device 10-2 that receives the datagram frame, if the sending and receiving address information in the datagram frame is not registered in the address management unit 13-2, it is registered (S8).
[0075] In S9, the transport unit 12-2 of the relay device 10-2 transfers the payload data again to the destination address (terminal 1') in the datagram frame using UDP communication.
[0076] UDP communication from terminal 1' to terminal 1 can be performed in the same way from relay device 10-2 to relay device 10-1 by reversing the sender and receiver addresses.
[0077] (Example 1: Transfer Method of IP Communication) Next, a transfer method of IP communication will be described. Some applications satisfy MTU (Maximum Transmission Unit) restrictions by performing IP fragmentation. If L4 termination is performed at the relay device 10 for such applications, additional fragment reconstruction and division processing will be required. Therefore, in this example, IP fragmented communication is transferred as IP packets.
[0078] Although IP communication transfer does not require state management or address management, it is necessary to transfer transport layer headers such as IP header, TCP, and UDP as they are, which increases header overhead and reduces transfer efficiency.
[0079] The processing procedure will be described below with reference to the sequence diagram of FIG.
[0080] A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0081] In S1, terminal 1 transmits an IP packet addressed to terminal 1'. Address conversion unit 11-1 of relay device 10-1 refers to the fragment bit in the header of the IP packet received from terminal 1, and if fragmentation is enabled, in S2, it transfers the IP packet as is to transport unit 12-1.
[0082] In S3, the transport unit 12-1 uses the QUIC connection between the relay devices 10 to store the IP packet as is in the payload of the QUIC datagram frame and transfers it to the relay device 10-2.
[0083] In S4, the transport unit 12-2 of the relay device 10-2 extracts the IP packet from the datagram frame and transfers it to the terminal 1' based on the destination address information.
[0084] (First embodiment: Transfer switching between UDP and IP communications) Next, transfer switching between UDP and IP communications will be described.
[0085] Regarding transfer methods 1 and 2 for UDP communication and transfer method for IP communication, which method is more suitable varies depending on the application.
[0086] For example, UDP transfer method 2 is effective for applications such as DNS, which involve short packets and in which the number of communications between the server and client is small and response speed is important.
[0087] On the other hand, for applications that use long packets and transmit large amounts of data, such as real-time video streaming, UDP transfer method 1 is effective from the perspective of transfer efficiency.
[0088] The transfer method suited to the flow (application) as described above may be set in the address management unit 13 on the relay device 10 side for each flow.
[0089] It is also possible to dynamically allocate transfer methods based on the packet payload length or the number of transfers.
[0090] For example, if the UDP payload length before transfer is sufficiently small, the header overhead can be ignored and UDP transfer method 2 is used, but if the sum of the UDP payload length and the sending and receiving address lengths exceeds the maximum payload length of a QUIC packet, UDP transfer method 1 is used.
[0091] If neither of these conditions apply, the number of packet transfers per fixed period is measured, and if it is above a threshold, meaning that data transfers are occurring frequently, UDP transfer method 1 is used; otherwise, UDP transfer method 2 is used.
[0092] Furthermore, by adding an identifier indicating which transfer method is used to the beginning of the QUIC datagram frame, decoding is possible on the reception relay device 10-2 side regardless of which transfer method is used.
[0093] The processing procedure for the dynamic allocation will be described with reference to the flowchart of Fig. 7. Note that the subject of judgment in the following flowchart is, for example, the address conversion unit 11.
[0094] In S101, the relay device 10-1 receives an IP packet. If there is an IP fragment, the process proceeds to S103 (Yes in S102), and if there is no IP fragment, the process proceeds to S104 (No in S102).
[0095] In S103, the relay device 10-1 determines to forward the IP packet as it is. In S104, the relay device 10-1 determines whether "(UDP payload length + sending / receiving address length) > QUIC maximum payload length", and if Yes, proceeds to S105, and if No, proceeds to S106.
[0096] In S105, the relay device 10-1 determines to use UDP transfer method 1 for transfer.
[0097] In S106, the relay device 10-1 determines whether the UDP payload length is equal to or less than the threshold, and if Yes, proceeds to S107, and if No, proceeds to S108. In S107, the relay device 10-1 determines to perform transfer using UDP transfer method 2.
[0098] In S108, the relay device 10-1 determines whether the number of transfers within a certain period is equal to or greater than a threshold value, and if Yes, proceeds to S109, and if No, proceeds to S110.
[0099] In S109, the relay device 10-1 determines to perform transfer using UDP transfer method 1. In S110, the relay device 10-1 determines to perform transfer using UDP transfer method 2.
[0100] (Example 1: Communication transfer method by adding a path / connection) In the transfer method described above, even when using a datagram ID, it is necessary to assign ID information to packets. Here, we will explain a method of transferring packets without packet overhead by assigning a new logical path or connection to communications using TCP, UDP, or other protocols to be transferred.
[0101] 8 shows the sequence for UDP transfer using a logical path. In this case, the relay device 10-1 assigns a port number to be used for the QUIC connection instead of a datagram ID, and adds a new path using the assigned port number. The source port number is then associated with the sender / receiver address to be transferred, and the UDP payload is transferred over the new path.
[0102] When using a connection, a QUIC connection is added to the TCP, UDP, or IP flow to be transferred, and the connection ID is associated with the sender and receiver addresses to be transferred.
[0103] A specific processing procedure when a logical path is used will be described with reference to FIG.
[0104] A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0105] In S1, terminal 1 transmits a UDP packet addressed to terminal 1'. Address management unit 13-1 of relay device 10-1 checks whether the sending and receiving address information of the UDP packet has been registered, and if not, assigns a new sending port number to be used between relay devices 10 and registers the port number together with the sending and receiving addresses (S2 to S3).
[0106] In S4, the address management unit 13-1 issues a path addition instruction to the transport unit 12-1. In S5 and S6, a new logical path is added between the relay devices 10 using the assigned port number.
[0107] In S7, the address management unit 13-1 notifies the address management unit 13-2 of the pair of sender and receiver addresses from terminal 1 to terminal 1' using the added logical path. The address management unit 13-2 registers the pair of the sender port number and the sender and receiver addresses. In S8, the address management unit 13-2 sends a registration completion notification to the address management unit 13-1.
[0108] Thereafter, address conversion section 11-1 of relay device 10-1 converts the destination address of the UDP communication from terminal 1 to a destination address of transport section 12-1 of relay device 10-1, and in S9, the UDP packet is transferred to transport section 12-1.
[0109] In steps S10 to S12, the transport unit 12-1 references the path to be used from the source address, and transfers the UDP payload from the terminal 1 to the relay device 10-2 using the referenced path.
[0110] In steps S13 to S15, the transport unit 12-2 obtains the destination address from the source port number and transfers the UDP payload data to the terminal 1'.
[0111] (Embodiment 2: Transfer setting method using DNS) Next, a transfer setting method using DNS will be described as embodiment 2. Fig. 9 shows an example of the configuration of a communication system in embodiment 2.
[0112] 9, a DNS server 40 is provided, and relay devices 10-1 and 10-2 are connected to a wide area network 30. The DNS server 40 can communicate with each terminal and each relay device. Compared to the first embodiment, the relay device 10 of the second embodiment does not have an address conversion unit 11.
[0113] An example of the operation of the communication system of the second embodiment will be described with reference to Fig. 10. A QUIC connection is established in advance between the relay devices 10 via one or more networks using a protocol such as MPTCP or MPQUIC.
[0114] In S1, terminal 1 queries the SRV record of terminal 1' to the DNS server 40. The DNS server 40 assigns a stream ID or datagram ID to be used within the QUIC connection between relay device 10-1 and relay device 10-2 through which communication from terminal 1 to terminal 1' passes.
[0115] In steps S2 to S5, the DNS server 40 notifies each relay device 10 along the way of the source address, destination address, and ID to be used in the QUIC connection, and each relay device 10 registers the address and ID information in the address registration unit 13 and sends a registration completion notification to the DNS server 40.
[0116] In S6, the DNS server 40 responds to the terminal 1 with the address of the relay device 10-1 instead of the address of the terminal 1', and in S7, the terminal 1 transfers the data addressed to the terminal 1' to the relay device 10-1. The data is transferred in S8 and S9. At this time, the transfer method is one of TCP, UDP, and IP, as in the first embodiment.
[0117] When forwarding IP packets as they are, no port number is required, so DNS can simply use an A record, and no ID for the QUIC connection is required.
[0118] 10, the DNS server 40 returns the address of the relay device 10-1, but it may return the address of the terminal 1' and perform address conversion on the relay device 10-1 side. In this method, it is possible to go through two or more relay devices 10, and any relay device 10 can be used.
[0119] (Hardware Configuration Example) Any of the devices described in this embodiment (relay device 10, DNS server 40) can be realized, for example, by running a program on a computer. This computer may be a physical computer or a virtual machine on a cloud.
[0120] That is, the device can be realized by executing a program corresponding to the processing performed by the device using hardware resources such as a CPU and memory built into a computer. The program can be recorded on a computer-readable recording medium (such as a portable memory) and stored or distributed. The program can also be provided via a network such as the Internet or email.
[0121] Fig. 11 is a diagram showing an example of the hardware configuration of the computer. The computer in Fig. 11 includes a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, and the like, all of which are interconnected by a bus BS. The computer may further include a GPU. The auxiliary storage device 1002 and the memory device 1003 may be collectively referred to as a storage device. The address management unit 13 is implemented using a storage device.
[0122] The program that realizes the processing on the computer is provided by a recording medium 1001, such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via a network. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.
[0123] The memory device 1003 reads and stores a program from the auxiliary storage device 1002 when an instruction to start the program is received. The CPU 1004 realizes functions related to the device in accordance with the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network, etc. The display device 1006 displays a GUI (Graphical User Interface) or the like according to the program. The input device 1007 is composed of a keyboard, mouse, buttons, a touch panel, etc., and is used to input various operation instructions. The output device 1008 outputs the results of calculations.
[0124] (Summary of the embodiment) In the communication system of this embodiment, data is transmitted between terminals via multiple relay devices 10 connected by one or more networks. Each relay device 10 terminates communication at the transport layer (L4), and multiple stream communications or datagram communications between the relay devices 10 are multiplexed into one transport connection and transferred via one or more networks.
[0125] The relay device 10 converts the destination address of a packet sent from a terminal. The relay device 10 also associates the original sending and receiving addresses of the packet with a flow identifier used in the transport connection between the relay devices 10, and notifies the opposing relay device 10 of the flow identifier and sending and receiving addresses.
[0126] In addition, the relay device 10 checks the fragment identifier of the source packet, and if the fragment identifier is present, the relay device 10 can forward the source packet using the transport connection between the relay devices 10 without making any changes to the source packet.
[0127] Furthermore, the relay device 10 can switch the transfer method in the transport connection between the relay devices 10 based on the payload length or transmission frequency of the source packet. The transfer method may be a method of assigning a flow identifier or a method of assigning a sending and receiving address.
[0128] Furthermore, when a terminal makes a DNS inquiry to the DNS server 40, the DNS server 40 determines the transfer settings of one or more relay devices 10 through which the terminal's communication will pass, and the transfer method of the transport connection between the relay devices 10, and notifies each relay device 10 of information such as the transfer source address, transfer destination address, and usage ID. Each relay device 10 registers the notified information and uses the registered information when transferring data.
[0129] (Effects) The technology according to the present embodiment described above makes it possible to transfer data using multiple lines even for applications that use TCP, UDP, or IP, which are not compatible with conventional proxies such as MASQUE, or tunneling protocols.
[0130] Furthermore, since encryption, quality control of multiple lines, and congestion control can be centrally processed in the relay device, the utilization efficiency of computational resources and the utilization efficiency of the network can be improved. Furthermore, the technology according to the present embodiment enables data transfer without using a higher-level protocol such as HTTP.
[0131] As shown in Figures 3 and 4 of the first embodiment, the relay device 10 terminates the transport protocol (TCP / UDP) of the transfer source and transfers only the payload using a transfer method (QUIC stream / datagram, respectively) that matches the original transport protocol.
[0132] This reduces the packet header size compared to simply tunneling IP / UDP / TCP packets. Furthermore, in the case of TCP, traffic control (such as congestion control) is performed twice: by TCP between terminals and by QUIC between relay devices, which helps avoid conflicts between the controls.
[0133] The following additional notes are provided regarding the above-described embodiments.
[0134] <Additional Notes> (Additional Item 1) A relay device constituting a communication system having a plurality of relay devices connected by one or more networks, comprising: a memory; and at least one processor connected to the memory, wherein the processor at least registers in the memory sending and receiving addresses of communications between terminals, converts the destination address of a packet received from the terminal, receives the packet after the destination address conversion, and forwards the packet data using a transport connection between the relay devices by referring to the memory. (Additional Item 2) The processor registers the sending and receiving addresses and a flow identifier used in the transport connection in association with each other, and notifies the sending and receiving addresses and the flow identifier to a remote relay device, and the processor terminates a transport protocol of a source of the packet and forwards only the payload of the packet using a transfer method matching the original transport protocol. The relay device according to Additional Item 1. (Supplementary Item 3) The relay device according to Supplementary Item 1 or 2, wherein the processor checks whether a fragment of an IP packet received from a terminal is valid, and if valid, forwards the IP packet without performing address translation of the IP packet. (Supplementary Item 4) The relay device according to any one of Supplementary Items 1 to 3, wherein the processor determines a packet forwarding method based on the payload length or forwarding frequency of the packet received from the terminal. (Supplementary Item 5) The relay device according to any one of Supplementary Items 1 to 4, wherein the processor associates the sending and receiving addresses with a port number used in a transport connection between the relay devices, registers the address and the port number, adds a path using the port number, and notifies the opposing relay device of the sending and receiving addresses using the added path. (Supplementary Item 6) The relay device according to any one of Supplementary Items 1 to 5, wherein, in response to a query from the terminal to a DNS server, the processor receives address information and a flow identifier used in the transport connection from the DNS server and registers them.(Supplementary Item 7) A relay method executed by a relay device constituting a communication system having a plurality of relay devices connected by one or more networks, the relay method comprising at least the steps of: registering sending and receiving addresses for communication between terminals in a storage device; converting the destination address of a packet received from the terminal; and receiving the packet after the destination address conversion and forwarding the data of the packet using a transport connection between the relay devices by referring to the storage device. (Supplementary Item 8) A non-transitory storage medium storing a program for causing a computer to function as each unit in the relay device described in any one of Supplementary Item 1 to 6.
[0135] Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and changes are possible within the scope of the gist of the present invention described in the claims.
[0136] 1 to n terminals 1' to n' terminals 10 relay device 11 address conversion unit 12 transport unit 13 address management unit 20 network 30 wide area network 1000 drive device 1001 recording medium 1002 auxiliary storage device 1003 memory device 1004 CPU 1005 interface device 1006 display device 1007 input device 1008 output device
Claims
1. A relay device constituting a communication system having a plurality of relay devices connected by one or more networks, comprising at least an address management unit which registers sending and receiving addresses for communication between terminals, an address conversion unit which converts the destination address of a packet received from the terminal, and a transport unit which receives a packet after the destination address conversion from the address conversion unit and transfers the data of the packet using a transport connection between the relay devices by referring to the address management unit.
2. The relay device according to claim 1, wherein the address management unit registers the sending and receiving addresses and the flow identifier used in the transport connection in association with each other, and notifies the opposing relay device of the sending and receiving addresses and the flow identifier, and the transport unit terminates the transport protocol of the source of the packet and transfers only the payload of the packet using a transfer method that matches the original transport protocol.
3. The relay device according to claim 1, wherein the address conversion unit checks whether a fragment of an IP packet received from a terminal is valid, and if valid, transfers the IP packet to the transport unit without performing address conversion on the IP packet.
4. The relay device according to claim 1, wherein the address conversion unit determines a packet forwarding method based on a payload length or a forwarding frequency of the packet received from the terminal.
5. The relay device according to claim 1, wherein the address management unit registers the sending and receiving addresses in correspondence with a port number used in a transport connection between relay devices, instructs the transport unit to add a path using the port number, and notifies the opposing relay device of the sending and receiving addresses using the added path.
6. The relay device according to claim 1, wherein, in response to an inquiry from a terminal to a DNS server, said address management unit receives and registers address information and a flow identifier used in said transport connection from said DNS server.
7. A relay method executed by a relay device constituting a communication system having a plurality of relay devices connected by one or more networks, comprising at least the steps of: registering in a storage device sender / receiver addresses for communication between terminals; converting the destination address of a packet received from a terminal; and receiving the packet after the destination address conversion and forwarding the packet data using a transport connection between the relay devices by referring to the storage device.
8. A program for causing a computer to function as each unit in the relay device according to any one of claims 1 to 6.
Citation Information
Patent Citations
Method, system and device for communicating packet between networks
JP2001345854A
Method and apparatus for achieving seamless handoff between IP connections
JP2005535230A
Gateway device and radio terminal
JP2006222993A
Communication system
JP2015070583A
Communication relay device and data relay method
JP2022079634A
