KR102641949B1 - Proxyless multi-path transmission system, and signalling method for session connection - Google Patents

Abstract

It is a multi-path gateway connected to the core network, and receives the first packet transmitted by the terminal for initial connection from the multi-path transmission supporter and the core network, and traffic related to the first packet is multi-path (multi-path) When it is a transmission target, it includes a packet forwarder that delivers the first packet to the multi-path transmission supporter. The multi-path transmission supporter creates a first subflow with the terminal based on the first packet, creates a session with a destination server of the first packet, and binds the first subflow and the session, Traffic is transmitted and received between the terminal and the destination server through the bound first subflow and the session. The first subflow passes through the core network and is connected to the terminal.

Description

Non-proxy based multipath transport system, and signaling method for session connection thereof {PROXYLESS MULTI-PATH TRANSMISSION SYSTEM, AND SIGNALLING METHOD FOR SESSION CONNECTION}

The present invention relates to multipath transmission.

Aggregation transmission is a technology that transmits data using multiple communication networks simultaneously, and processes data transmitted through each path as one session. Through merged transmission technology, a terminal can be connected to multiple communication networks at one time, and one service/application communicates by merging multiple networks as one network, regardless of network type or number of networks. Therefore, the merged transmission system can quickly transmit and receive large amounts of data using a plurality of available network resources. In the sense of merging multiple networks, it can be called MultiNet Aggregation.

Among merged transmission technologies, there is multi-path TCP (Multi-Path TCP, MPTCP) technology that uses multiple TCP flows bundled together. MPTCP is an L4 technology for using multiple IP interfaces simultaneously. A terminal equipped with multiple physical interfaces can be connected to multiple communication networks at one time through MPTCP technology, and creates sessions on a subflow basis to communicate end-to-end.

The terminal and the gateway go through a signaling procedure to establish a session connection for merged transmission, and can exchange signaling information according to the SOCKS (Socket Secure) protocol defined in RFC1928 and RFC1929. The SOCKS protocol is a protocol used by content servers and clients to communicate TCP/UDP via a proxy server. However, the SOCKS protocol defined in RFC1928 and RFC1929 has the disadvantage of increasing the session connection time and increasing the load on the client and proxy server due to the large number of transactions exchanged between the client and proxy server.

As such, the MPTCP technology so far has merged the LTE network and WiFi network through a proxy-based gateway, but has the disadvantage of not being able to charge from the LTE core network (Evolved Packet Core, EPC) due to the proxy structure and the SOCKS protocol generated for each TPC session. There is a problem that the initial connection time is very delayed due to the initial connection procedure. As the new 5G network is introduced, a new multi-path transmission technology that solves the shortcomings of the current MPTCP technology is required.

The problem to be solved by the present invention is to provide a multi-path gateway in which an MPTCP enabler converts MPTCP packets transmitted from the core network into TCP packets and transmits them to the Internet network, and a multi-path transmission system including the same.

The problem to be solved by the present invention is to provide a non-proxy based signaling method in which a multi-path gateway creates a subflow with a terminal.

According to one embodiment, it is a multi-path gateway connected to a core network for multi-path transmission, receiving a multi-path transmission supporter and the first packet transmitted by the terminal for initial connection from the core network, When traffic related to the first packet is subject to multi-path transmission, it includes a packet forwarder that delivers the first packet to the multi-path transmission supporter. The multi-path transmission supporter creates a first subflow with the terminal based on the first packet, creates a session with a destination server of the first packet, and binds the first subflow and the session, Traffic is transmitted and received between the terminal and the destination server through the bound first subflow and the session. The first subflow passes through the core network and is connected to the terminal.

The multi-path transmission supporter may set the source address of the second packet to the address of the multi-path gateway and then transmit the second packet to the destination server to create the session.

When the multi-path transmission supporter receives a third packet requesting addition of a second subflow from the terminal, it generates the second subflow based on the third packet, and generates the first subflow and the second subflow. Traffic can be transmitted to the terminal by merging flows.

The core network may be a network that integrates the cores of a 5G network and a 3G/LTE network. The first subflow may be a session connecting the terminal and the multi-path transmission supporter through one of the 5G network and the 3G/LTE network. The second subflow may be a session connected to the terminal through a network different from the first subflow among the 5G network and the 3G/LTE network.

When the multi-path transmission supporter receives a message indicating that the WiFi network is available from the terminal, it transmits the IP address assigned for accessing the WiFi network to the terminal and requests additional subflows from the terminal connected to the IP address. Upon receiving the message, a WiFi subflow connected to the terminal through the WiFi network can be added to the first subflow.

The multi-path transmission supporter includes a first socket manager that creates at least one subflow connected to the terminal, a second socket manager that creates a session with the destination server, and the at least one created in the first socket manager. It may include a socket binder that binds a subflow and the session created in the second socket manager.

The first packet may be an MPTCP SYN message transmitted when an application is executed in the terminal.

According to another embodiment, a method of signaling for a session connection with a terminal by a multi-path gateway connected to a core network for multi-path transmission, comprising: receiving an MPTCP SYN message transmitted from the terminal from the core network; After exchanging responses to the MPTCP SYN message, creating a first subflow with the terminal, creating a TCP session with a destination server of the MPTCP SYN message, and connecting the first subflow and the TCP session. Binding, and transmitting and receiving traffic between the terminal and the destination server through the bound first subflow and the TCP session. The first subflow passes through the core network and is connected to the terminal.

In the step of creating the TCP session, the TCP session may be created by transmitting a TCP SYN message whose source address is the address of the multi-path gateway to the destination server.

The signaling method includes receiving a subflow addition request message from the terminal, generating a second subflow connected to the terminal, and merging the first subflow and the second subflow to send traffic to the terminal. It may further include the step of transmitting. The second subflow may be connected to the terminal through the core network.

The first subflow is a session connected to the terminal through one of the 5G network and the 3G/LTE network, and the second subflow is a network different from the first subflow among the 5G network and the 3G/LTE network. It may be a session connected to the terminal through .

The signaling method includes receiving a message indicating the availability of a WiFi network from the terminal, transmitting an IP address assigned for accessing the WiFi network to the terminal, and requesting additional subflow from the terminal connected to the IP address. It may further include receiving a message, creating a WiFi subflow connected to the terminal through the WiFi network, and merging the first subflow and the WiFi subflow to transmit traffic to the terminal. You can.

In the step of generating the first subflow, user authentication is performed based on authentication information included in the MPTCP SYN message, and if the user authentication is successful, a response to the MPTCP SYN message can be exchanged with the terminal.

The signaling method may further include periodically transmitting the authentication information to the terminal.

According to an embodiment of the present invention, it is possible to efficiently use multi-wireless networks by merging 5G networks and 3G networks/LTE networks, and by merging WiFi networks, communication quality can be improved by merging multiple networks using the communication interfaces of the terminal. .

According to an embodiment of the present invention, proxy-based merged transmission, which delays the initial connection time, is not performed, so the terminal can quickly initial connect for merged transmission, thereby improving connection quality.

According to an embodiment of the present invention, the terminal does not need to additionally include a proxy client for merged transmission, and a multi-path gateway does not need to be developed as a proxy server, thereby reducing the difficulty of developing a system for multi-path transmission.

1 is a diagram illustrating the configuration of a multi-path system according to an embodiment.
Figure 2 is a configuration diagram of a multi-path gateway according to an embodiment.
Figure 3 is a flowchart explaining a conventional SOCKS protocol-based initial connection method.
Figure 4 is a flowchart of a signaling method for session connection between a terminal and a multi-path gateway according to an embodiment.
FIG. 5 is a diagram illustrating the configuration of a multi-path system combined with a WiFi network according to an embodiment.
Figure 6 is a flowchart of a subflow generation method in a multi-path system combined with a WiFi network according to an embodiment.
Figure 7 is a flowchart of a session authentication method according to one embodiment.

Below, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily implement the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. In order to clearly explain the present invention in the drawings, parts that are not related to the description are omitted, and similar parts are given similar reference numerals throughout the specification.

Throughout the specification, when a part is said to “include” a certain element, this means that it may further include other elements rather than excluding other elements, unless specifically stated to the contrary. In addition, terms such as "... unit", "... unit", and "module" used in the specification refer to a unit that processes at least one function or operation, which may be implemented as hardware or software or a combination of hardware and software. there is.

In this specification, the terminal refers to a client, a mobile station (MS), a mobile terminal (MT), a subscriber station (SS), a portable subscriber station (PSS), and a user device ( It may refer to User Equipment (UE), Access Terminal (AT), etc., and may include all or part of the functions of mobile stations, mobile terminals, subscriber stations, portable subscriber stations, user devices, and access terminals. .

The terminal in this specification is a gateway, a base station (BS), an access point (AP), a radio access station (RAS), a Node B, and an evolved Node B. You can connect to a remote server by accessing network devices such as NodeB, eNodeB, Base Transceiver Station (BTS), Mobile Multihop Relay (MMR)-BS, 5G NB (gNB), etc.

The terminal of this specification is a variety of communication terminals such as mobile terminals such as smartphones, tablet terminals such as smart pads and tablet PCs, computers, and televisions, and may be equipped with a plurality of communication interfaces.

Communication interfaces may vary. For example, communication interfaces include short-range wireless network interfaces such as WiFi/WLAN/Bluetooth, and mobile devices such as 3G/LTE (Long Term Evolution)/LTE-A (Long Term Evolution-Advanced)/5G. It can include a communication network interface, and terminal manufacturers can add various communication interfaces. In this specification, the 3G/LTE interface, 5G interface, and WiFi interface are used as examples, but the communication interface is not limited thereto.

Multi-network merging technologies can be classified as follows depending on the merging point.

L2/link layer merging creates a dedicated tunnel from the border point (i.e., eNB) of the LTE core network and access network to the WiFi AP.

L3/network layer merging creates a virtual IP tunnel to integrate IP addresses used independently in the LTE network and WiFi network.

L4/transport layer merging can create a session through a single access network and then participate in data transmission regardless of the IP address system if an additional access network is available. At this time, the communication subject at the application level supports a structure that allows single session-based data communication using one or more access networks.

In L7/application layer merging, a dedicated application/network agent recombines data received through the LTE network and WiFi network or separates and transmits application protocol data.

In this way, various merged transmissions are possible depending on the merged transmission layer, and in the future, merge technology through L4-based multi-path TCP (Multi-Path TCP, MPTCP) will be explained as an example.

MultiNet Aggregation transmission is a technology that transmits data by merging multiple communication networks. Transmission data is divided and transmitted into paths of multiple homogeneous networks or multiple heterogeneous networks, or data transmitted through multiple paths is transmitted. It can be bundled and transmitted through one route. Multi-network merge transmission can be called multi-path transmission in the sense that data is transmitted simultaneously through multiple paths.

In the present invention, 5G network and 3G network/LTE network merging are mainly explained, and WiFi network merging is additionally explained.

1 is a diagram illustrating the configuration of a multi-path transmission system according to an embodiment.

Referring to FIG. 1, the multi-path transmission system includes a terminal 100, a plurality of base stations 200 and 220 to which the terminal 100 is connected, and a core network 300 that transmits and receives traffic to and from the base stations 200 and 220. , and a multi-path gateway (MP-GW) 400 that creates and binds an MPTCP-TCP session between the core network 300 and the Internet network. The explanation will be made using eNB 200, a 3G/LTE base station, and gNB 220, a 5G base station, as an example. The MP-GW 400 is composed of hardware including at least one processor, memory device, communication device, etc., and includes a program including instructions implementing the operating method of the present invention. The program executes the present invention in combination with hardware such as a processor and memory device.

It is assumed that the terminal 100 includes a 3G/LTE interface, a 5G interface, and a WiFi interface, and is equipped with an MPTCP function to perform merge transmission. The terminal 100 is connected to the core network 300 by accessing at least one of the eNB 200 and the gNB 220. The communication interface of the terminal 100 may have a predetermined priority. For example, the terminal 100 creates a first subflow through the 3G/LTE interface and a second subflow through the 5G interface. (Secondary subflow) can be added. A third subflow can be added to the WiFi interface. At this time, the terminal 100 can make initial connection for multi-path transmission by simply transmitting the MPTCP SYN generated for initial connection without the need to install a proxy agent for multi-path transmission.

The core network 300 is explained using a non-standalone mode (NSA) that integrates a 5G core and a 3G/LTE core (Evolved Packet Core, EPC) as an example, but can also be applied to standalone mode (Standalone).

MP-GW (400) is connected to the core network (300), converts MPTCP traffic output from the core network (300) to TCP, and transmits it to the Internet network. To this end, when the application is run on the terminal 100 and a packet (MPTCP SYN) is generated, the MP-GW 400 creates an MPTCP session with the terminal 100 according to the MPTCP protocol, and sends the content server 500 of the packet. and create a TCP session. The MP-GW 400 may create a first subflow connected to the first interface of the terminal 100 and then add a second subflow connected to the second interface. The first interface may be a 3G/LTE interface or a 5G interface, but in the description, it is assumed that the first subflow is created through the 3G/LTE interface and the second subflow is created through the 5G interface. MP-GW 400 can add a WiFi subflow connected to the WiFi interface of the terminal 100. Specifically, the packet generated in the application of the terminal 100 is generated as an MPTCT packet (MPTCP SYN) through the MPTCP kernel and transmitted to the MP-GW (400). The terminal 100 creates an MPTCP session with the MP-GW 400 and makes initial connection. Therefore, without the need for user authentication for each MPTCP session through a SOCKS-based proxy agent for initial connection, the terminal 100 can transmit MPTCT with the MP-GW 400 by simply transmitting the MPTCP packet generated through the MPTCP kernel. You can make initial connection for. That is, the MPTCP packet is transmitted with the IP address of the content server 500 listed in the destination address.

For this purpose, the MP-GW 400 includes a packet redirector 410 that receives packets from the core network 300, and a multi-path transmission enabler 430. Since the multi-path transmission supporter performs merge transmission based on MPTCP, it will simply be called the MPTCP supporter from now on.

The MPTCP supporter 430 creates an MPTCP session with the terminal 100 based on the MPTCP packet delivered from the packet forwarder 410, and creates a TCP session with the content server 500 of the MPTCP packet. The MPTCP supporter 430 may be called an On-Path MPTCP Enabler. Meanwhile, when the packet transmitter 410 receives a TCP packet from the core network 300, it can directly transmit the TCP packet to the Internet network without transmitting it to the MPTCP supporter 430.

The packet transmitter 410 receives an MPTCP packet (MPTCP SYN) from the core network 300. The packet forwarder 410 delivers the MPTCP packet to the MPTCP supporter 430.

The MPTCP supporter 430 delivers a response (MPTCP Ack) to the MPTCP packet to the terminal 100 and transmits a TCP packet (TCP SYN) to the destination address of the MPTCP packet. Through this, the MPTCP supporter 430 creates an MPTCP session with the terminal 100 and a TCP session with the content server 500. That is, the MPTCP supporter 430 converts MPTCP packets into TCP packets or converts TCP packets into MPTCP packets and transmits them. At this time, the MPTCP supporter 430 describes the source address of the TCP packet as the IP address of the MP-GW 400 and transmits it. In this way, the MPTCP supporter 430 connects an MPTCP session and a TCP session between the terminal 100 and the content server 500 to support the terminal 100 to communicate using multiple networks.

Figure 2 is a configuration diagram of a multi-path gateway according to an embodiment.

Referring to FIG. 2, the MP-GW 400 includes a packet forwarder 410 that receives packets from the core network 300 and an MPTCP supporter 430.

The packet forwarder 410 includes a traffic receiver 411, a traffic controller 413, an MPTCP traffic redirector 415 that delivers MPTCP packets to the MPTCP supporter 430, and an address conversion unit. (Network Address Translator, NAT) (417) and Blacklist Table (419).

The traffic receiving unit 411 receives traffic packets from the core network 300.

The traffic control unit 413 checks (Traffic Checker, ACL) whether traffic (multi-path transmission target) requires multi-path based on the source address, destination address, and destination port (e.g., 80) of the received packet. Table).

If the traffic requires multi-path transmission, the traffic control unit 413 transfers the packet to the MPTCP delivery unit 415 and controls the packet to be delivered to the MPTCP supporter 430. The MPTCP transmission unit 415 redirects the packet to the MPTCP port (eg, 25486) of the MPTCP supporter 430. When the MPTCP supporter 430 is first executed, a specific TCP port (for example, 25486) for receiving MPTCP packets is opened as an MPTCP port through the MPTCP socket manager 432.

If multi-path transmission is unnecessary traffic, the traffic control unit 413 transfers the received packet to the NAT 417 and controls the packet to be transmitted to the content server 500. The traffic control unit 413 may determine whether information related to the received packet is included in the blacklist table 419 and discard the packet included in the blacklist table 419.

The MPTCP supporter 430 includes a Multi-Path Control Manager (431), an MPTCP Socket Manager (432), a TCP Socket Manager (433), and an MPTCP-TCP Socket Binder ( Includes MPTCP-TCP Socket Binder (434), Packet Buffer/Queue (435), and Multi-Path QoS Manager (436).

When the MPTCP socket manager 432 opens an MPTCP port (for example, 25486) for transmitting and receiving MPTCP packets, it receives the MPTCP packet (MPTCP SYN) transmitted from the packet forwarder 410.

The TCP socket manager 433 opens a specific TCP port for sending and receiving TCP packets.

When an MPTCP packet (MPTCP SYN) is delivered to the MPTCP socket manager 432, the multipath control manager 431 controls the MPTCP socket manager 432 to create an MPTCP session with the terminal 100. And, the multi-path control manager 431 controls the TCP socket manager 433 to create a TCP session with the content server 500. At this time, the TCP socket manager 433 transmits a TCP packet (TCP SYN) for the TCP session to the original destination server address, and sets the source address to the IP address of the MP-GW (400).

The MPTCP-TCP socket binder 434 connects and manages MPTCP sessions and TCP sessions.

The packet buffer/queue 435 stores packets received from the packet forwarder 410. Packets stored in the packet buffer/queue 435 are transmitted to the content server 500 through a connected TCP session. Likewise, the packet buffer/queue 435 stores packets received from the content server 500, and the stored packets are transmitted to the terminal 100 through a connected MPTCP session.

The multi-path QoS manager 436 manages the QoS set in the created MPTCP session and TCP session, and controls traffic to be transmitted to the MPTCP session/TCP session according to the set QoS.

Additionally, the multi-path control manager 431 can control whether or not to transmit multi-path. For example, after the terminal 100 creates a main subflow, a secondary subflow can be created by transmitting an MP_JOIN SYN message (subflow addition message), but merge transmission through the secondary subflow is not necessary depending on the traffic. can do. Accordingly, the multi-path control manager 431 can set multi-path transmission conditions and control the creation of additional sub-subflows only for traffic that meets the multi-path transmission conditions. Multi-path transmission conditions may include, for example, TCP session maintenance time, data transmission speed, and transmission data amount. The multipath control manager 431 can save resources of the MP-GW 400 by controlling the additional subflows to be created only for traffic that meets the multipath transmission conditions. Meanwhile, in order to smoothly inspect the upload data (eg, HTTP request) of the terminal in the 5G core network, the multi-path control manager 431 can control the upload data to be transmitted in a single subflow.

The multi-path control manager 431 can request the terminal to use a single subflow and control the terminal not to transmit the MP_JOIN SYN message. Alternatively, the multipath control manager 431 may transmit a response message disallowing the connection when the terminal transmits an MP_JOIN SYN message.

In this way, the MP-GW (400) creates an MPTCP session and a TCP session with MPTCP packets that passed through the core network (300), and then uses the two connected sessions to convert the MPTCP traffic that passed through the core network (300) into TCP traffic. It is converted and delivered, and TCP traffic is converted into MPTCP traffic and delivered to the core network 300. Therefore, according to the present invention, the terminal 100 and the MP-GW 400 do not need to be implemented as a proxy agent and proxy server that include a complicated user authentication procedure for initial connection, but can provide multiplexing by simply forwarding the MPTCP packet. You can make an initial connection for route transmission. Additionally, according to the present invention, the MP-GW (400) receives packets that have passed through the core network (300) or transmits packets to the core network (300). Therefore, when using the MP-GW (400), there is no need to add a separate charging device for multi-path transmission, and the core network (300) can charge for transmission and reception traffic in the same way as general traffic.

Figure 3 is a flowchart explaining a conventional SOCKS protocol-based initial connection method.

Referring to FIG. 3, when the application 11 is run on the terminal and an initial connection packet (TCP SYN) is generated, the proxy client 12 communicates with the application 11 and performs TCP SYN and SYN/ACK according to the TCP connection procedure. , exchange ACKs.

The proxy client 12 attempts a proxy connection by exchanging MPTCP SYN, SYN/ACK, and ACK with the proxy server 20, which is a multi-path gateway. Afterwards, the proxy client 12 and the proxy server 20 exchange messages according to the SOCKS protocol as follows.

The proxy client 12 transmits a SOCKS version identifier message to the proxy server 20. The proxy client 12 transmits a SOCKS Method selection message to the proxy server 20. The proxy client 12 transmits a SOCKS Authentication Request message to the proxy server 20. The proxy client 12 receives a SOCKS Authentication Response message from the proxy server 20.

The user-authenticated proxy client 12 transmits a SOCKS Connection Request message to the proxy server 20 to request a server connection. The proxy server 20 performs a TCP connection procedure with the server of the destination address included in the SOCKS Connection Request message. The proxy server 20 sends a SOCKS Connection Reply message to the proxy client 12 to respond with the server connection result.

Since the conventional signaling method for initial connection following the SOCKS protocol merges MPTCP through the proxy client 12 in the terminal, a connection procedure with the proxy client 12 is required every time. A SOCKS connection procedure between the proxy client 12 and the proxy server 20 is required each time. Therefore, the conventional signaling method following the SOCKS protocol has problems such as signaling overhead, connection latency, processing load, and resource waste due to messages exchanged between the proxy client 12 and the proxy server 20. . Ultimately, there is a problem that the initial connection time becomes longer when a user connects to the Internet.

In the following, a signaling method that improves the conventional initial access procedure will be described.

Figure 4 is a flowchart of a signaling method for session connection between a terminal and a multi-path gateway according to an embodiment.

Referring to FIG. 4, the terminal 100 transmits an MPTCP SYN message to the MP-GW 400 for initial access to the application (S110). Since the terminal 100 does not include a proxy client, the application does not need a TCP connection with the proxy client within the terminal, and the TCP SYN generated in the application is generated as an MPTCP SYN and transmitted to the MP-GW 400.

MP-GW 400 transmits an MPTCP SYN/ACK message to terminal 100 (S120).

The terminal 100 transmits an ACK message to the MP-GW 400 (S130).

When the MPTCP connection procedure is completed, the terminal 100 and the MP-GW 400 create an MPTCP session (i.e., main subflow) (S140).

MP-GW (400) transmits a TCP SYN message for creating a TCP session to the content server (500) (S150). At this time, the MP-GW (400) transmits the TCP SYN to the destination server address of the MPTCP SYN, but transmits the source address as the IP address of the MP-GW (400).

MP-GW (400) receives a TCP SYN/ACK message from the content server (500) (S160).

MP-GW (400) transmits an ACK message to the content server (500) (S170).

When the TCP connection procedure is completed, the MP-GW (400) and the content server (500) create a TCP session (S180).

MP-GW (400) binds the MPTCP session and the TCP session (S190).

The terminal 100 and the content server 500 transmit and receive data through the MP-GW (400).

Afterwards, the terminal 100 can add a secondary subflow through exchanging MP_JOIN SYN, SYN/ACK, and ACK messages with the MP-GW 400. At this time, the main subflow may be an LTE subflow created through the LTE interface of the terminal, and the secondary subflow may be a 5G subflow created through the 5G interface of the terminal.

FIG. 5 is a diagram illustrating the configuration of a multi-path transmission system combined with a WiFi network according to an embodiment, and FIG. 6 is a flowchart of a subflow generation method of a multi-path transmission system combined with a WiFi network according to an embodiment. am.

Referring to Figures 5 and 6, the MP-GW (400) can transmit traffic by merging a 3G/LTE network, a 5G network, and a WiFi network. The WiFi network is not connected to the core network (300) of the 3G/LTE network and 5G network, but is connected to the MP-GW (400). The terminal 100 can connect to the access point (AP) 240 through a WiFi interface and create a WiFi subflow connected to the MP-GW (400).

In addition to the first public IP address (Pub_IP1) for communication with the Internet, that is, the IP address for NAT, the MP-GW (400) provides a second public IP address (Pub_IP2) to which the terminal 100 connects through the WiFi interface. I have extra.

The terminal 100 creates an LTE subflow by exchanging MPTCP SYN, SYN/ACK, and ACK messages with the MP-GW 400 through the LTE interface (S210).

The MP-GW 400 creates a TCP session by exchanging TCP SYN, SYN/ACK, and ACK messages with the content server 500 (S220).

The terminal 100 and the content server 500 can transmit and receive data through the MP-GW 400 that binds the LTE subflow and TCP session (S230).

Afterwards, the terminal 100 adds a 5G subflow by exchanging MP_JOIN SYN, SYN/ACK, and ACK messages with the MP-GW 400 through the 5G interface (S240).

The terminal 100 is capable of multi-path transmission through the LTE subflow and 5G subflow (S250).

If the terminal 100 can use the WiFi interface for merge transmission, the terminal 100 transmits a message (WiFi Enable) indicating WiFi availability to the MP-GW 400. WiFi Enable can be transmitted by including it in the MP_JOIN ACK message.

The MP-GW 400, which has received the WiFi Enable message, transmits a WIFI_ADD_ADDR message including the second public IP address (Pub_IP2) to the terminal 100 (S260).

The terminal 100 transmits the MP_JOIN SYN message to the MP-GW 400 through the WiFi interface (S270). At this time, the terminal 100 transmits an MP_JOIN SYN message with the second public IP address (Pub_IP2) set as the destination address and the IP address of the WiFi interface set as the source address. The MP-GW 400 transmits a SYN/ACK to the terminal 100 (S272), and the terminal 100 transmits an ACK message to the MP-GW 400 (S274).

The terminal 100 and MP-GW 400 add a WiFi subflow (S280).

The terminal 100 is capable of multi-path transmission through LTE subflow, 5G subflow, and WiFi subflow (S290).

Figure 7 is a flowchart of a session authentication method according to one embodiment.

As shown in FIG. 3, a conventional session created based on a proxy performs user authentication according to the SOCKS protocol upon initial connection, but the MP-GW 400 can perform user authentication for an MPTCP session as follows.

Referring to FIG. 7, the MP-GW (400) transmits authentication information to terminals that can use MPTCP at the current time (S310). Authentication information may be transmitted periodically. Authentication information may be a hash value generated based on various information such as the number of currently connected TCP sessions, time, and traffic volume. Authentication information may be stored in the terminal 100 as a cookie. Even if a terminal has a history of being connected to the MP-GW (400) before the time of transmitting authentication information, authentication information is not transmitted to a subscriber terminal that has canceled its MPTCP subscription. Authentication information can be generated and transmitted by the multi-path control manager 431 of the MP-GW (400). Meanwhile, a policy server or authentication server separate from the MP-GW (400) may generate and transmit authentication information and share it with the MP-GW (400).

MP-GW 400 receives an MPTCP SYN message including authentication information from terminal 100 (S320).

The MP-GW (400) authenticates the user based on the authentication information included in the MPTCP SYN message (S330).

The MP-GW (400) transmits an MPTCP SYN/ACK message to the terminal (100) where user authentication is successful (S340).

As such, according to an embodiment of the present invention, it is possible to efficiently use multi-wireless networks by merging 5G networks and 3G networks/LTE networks, and by merging WiFi networks, it is possible to improve communication quality by using multiple paths using the communication interfaces of the terminal. You can. According to an embodiment of the present invention, proxy-based merged transmission, which delays the initial connection time, is not performed, so the terminal can quickly initial connect for merged transmission, thereby improving connection quality. According to an embodiment of the present invention, there is no need for the terminal to additionally include a proxy client for merged transmission, and there is no need to develop a multi-path transmission gateway as a proxy server, thereby reducing the difficulty of developing a system for multi-path transmission.

The embodiments of the present invention described above are not only implemented through devices and methods, but can also be implemented through programs that implement functions corresponding to the configurations of the embodiments of the present invention or recording media on which the programs are recorded.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements made by those skilled in the art using the basic concept of the present invention defined in the following claims are also possible. It falls within the scope of rights.

Claims (14)

As a multi-path gateway connected to the core network for multi-path transmission,
multipath transmission support, and
When a terminal that is a non-proxy client receives the first packet transmitted for initial connection from the core network, and the traffic related to the first packet that has passed through the core network is subject to multi-path transmission, the first packet A packet forwarder that transmits 1 packet to the multi-path transmission supporter and, when the first packet is a TCP packet, transmits TCP traffic of the terminal to an Internet network,
The multi-path transmission supporter
Create a first subflow based on the terminal and MPTCP based on the first packet, create a TCP session with the destination server of the first packet, bind the first subflow and the TCP session, and bind. Transmitting and receiving traffic between the terminal and the destination server through the first subflow and the TCP session,
The first subflow is connected to the terminal through the core network,
Charging for traffic transmitted through the first subflow proceeds in the same manner as charging for the TCP traffic in the core network,
A multi-path gateway in which the terminal and the multi-path gateway signal on a non-proxy basis. In paragraph 1:
The multi-path transmission supporter
A multi-path gateway that sets the source address of the second packet to the address of the multi-path gateway and then transmits the second packet to the destination server to create the session. In paragraph 1:
The multi-path transmission supporter
When receiving a third packet requesting addition of a second subflow from the terminal, the second subflow is generated based on the third packet, and the first subflow and the second subflow are merged to the terminal. A multi-path gateway that forwards traffic to. In paragraph 3,
The core network is a network that integrates the cores of the 5G network and 3G/LTE network,
The first subflow is a session connecting the terminal and the multi-path transmission supporter through one of the 5G network and the 3G/LTE network,
The second subflow is a session connected to the terminal through a network different from the first subflow among the 5G network and the 3G/LTE network. In paragraph 1:
The multi-path transmission supporter
When receiving a message indicating that the WiFi network is available from the terminal, the IP address allocated for accessing the WiFi network is transmitted to the terminal, and when a subflow addition request message is received from the terminal connected to the IP address, the A multi-path gateway that adds a WiFi subflow connected to the terminal through a WiFi network to the first subflow. In paragraph 1:
The multi-path transmission supporter
A first socket manager that creates at least one subflow connected to the terminal,
a second socket manager that creates a session with the destination server, and
A socket binder that binds the at least one subflow created in the first socket manager and the session created in the second socket manager.
A multi-path gateway, including. In paragraph 1:
The first packet is a multi-path gateway that is an MPTCP SYN message transmitted when an application is executed in the terminal. A method of signaling for a session connection with a terminal by a multi-path gateway connected to the core network for multi-path transmission,
Receiving an MPTCP SYN message transmitted from the terminal, which is a non-proxy client, from the core network, if:
After exchanging responses to the MPTCP SYN message with the terminal, generating an MPTCT-based first subflow with the terminal,
Creating a TCP session with the destination server of the MPTCP SYN message, and
Binding the first subflow and the TCP session, and transmitting and receiving traffic between the terminal and the destination server through the bound first subflow and the TCP session,
When receiving a TCP packet transmitted from the terminal through the core network, further comprising transmitting TCP traffic of the terminal to an Internet network,
The first subflow is connected to the terminal through the core network,
Charging for traffic transmitted through the first subflow proceeds in the same manner as charging for the TCP traffic in the core network,
A signaling method in which the terminal and the multi-path gateway signal on a non-proxy basis. In paragraph 8:
The step of creating the TCP session is
A signaling method for creating the TCP session by transmitting a TCP SYN message whose source address is the address of the multi-path gateway to the destination server. In paragraph 8:
Receiving a subflow addition request message from the terminal,
Creating a second subflow connected to the terminal, and
Further comprising merging the first subflow and the second subflow and transmitting traffic to the terminal,
The second subflow is connected to the terminal through the core network. In paragraph 10:
The first subflow is a session connected to the terminal through either a 5G network or a 3G/LTE network,
The second subflow is a session connected to the terminal through a network different from the first subflow among the 5G network and the 3G/LTE network. In paragraph 8:
Receiving a message indicating that a WiFi network is available from the terminal,
Transmitting the IP address assigned for accessing the WiFi network to the terminal,
Receiving a subflow addition request message from the terminal connected to the IP address,
Creating a WiFi subflow connected to the terminal through the WiFi network, and
Merging the first subflow and the WiFi subflow and transmitting traffic to the terminal
A signaling method further comprising: In paragraph 12:
The step of generating the first subflow is
A signaling method that authenticates a user based on authentication information included in the MPTCP SYN message and, if the user authentication is successful, exchanges a response to the MPTCP SYN message with the terminal. In paragraph 13:
Periodically transmitting the authentication information to the terminal
A signaling method further comprising:

Images