KR20230124249A - Apparatus and method for processing of establishment of connection for transmission control protocol - Google Patents

Abstract

A transmission control protocol connection processing apparatus and method, wherein the transmission control protocol connection processing apparatus stores at least one SYNACK packet and at least one request socket corresponding to the at least one SYNACK packet, and a SYN packet from a client device. and a processing unit for browsing the storage, and detecting a SYNACK packet corresponding to the SYN packet and a request socket corresponding to the SYN packet from the storage, the SYN packet is transmitted to the client device, and the request The socket may establish a transmission control protocol connection with the client device by receiving an ACK packet transmitted by the client device in response to the SYN packet.

Description

Transmission control protocol connection processing apparatus and method

Transmission control protocol connection processing device and method.

Transmission Control Protocol (TCP) is a communication protocol for data communication between two or more information processing devices such as computers or server devices, and is usually used together with Internet Protocol (IP). The transmission control protocol is commonly used because it guarantees the order of transmitted and received data and can establish a reliable connection without errors. The transmission control protocol requires a connection establishment process. This connection establishment process is performed through the process of transmitting a SYN packet from a client, transmitting a SYNACK packet from a server device, and transmitting an ACK packet from a client (3-way handshake). do. In this case, a memory allocation process is performed in the server device. Specifically, in the case of the Linux kernel, when a client sends a SYN packet to the server to request a transmission control protocol connection, the server determines a listen socket to receive the packet, and the memory allocator creates two instances for connection persistence. Allocates (instance) (SYNACK packet, which is the packet to be used for connection establishment, and Request socket, which is the socket for receiving the ACK packet for the SYNACK packet). When the states of the two instances are initialized, the server exchanges SYNACK and ACK packets with the client, respectively, and creates a connection with the client if there is nothing wrong with the received ACK packet. At this time, the two instances release their initialized states and return to the memory allocator. Such a connection establishment process is known to be a cause of a server's central processing unit (CPU) load. In particular, the connection establishment process of such a transmission control protocol may be a bigger problem when using a hypertext transfer protocol (HTTP). The hypertext transmission protocol not only has a short-lived connection characteristic, but also has a characteristic of repeatedly generating the above-described transmission control protocol connection establishment process, thereby degrading actual data packet exchange performance. Conventionally, in order to solve these problems, the data structure of the socket interface is lightweight, system calls are processed in batches, and transmission control protocol processing is off-loaded using a specific device to reduce the number of short-term connections that occur during short-term connections. I was trying to solve the load. However, since they use other external elements while maintaining the transmission control protocol, they affect other functions, causing performance degradation, and lack compatibility with existing applications.

An object to be solved is to provide a transmission control protocol connection processing device and method for solving an unnecessary processing bottleneck of a processing device due to repetitive creation of transmission control protocol connections.

In order to solve the above problems, a transmission control protocol connection processing apparatus and method are provided.

The transmission control protocol connection processing device, when a SYN packet is received from a repository storing at least one SYNACK packet and at least one request socket corresponding to the at least one SYNACK packet and a client device, browses the repository, and a processing unit for detecting a SYNACK packet corresponding to the SYN packet and a request socket corresponding to the SYN packet from By receiving the ACK packet transmitted as a response, a transmission control protocol connection with the client device may be established.

The processing unit may store the SYN packet and the request socket used for the transmission control protocol connection with the client device in the storage when the repeated connection with the client device exceeds a predefined threshold.

The processing unit may determine whether the SYN packet and the request socket can be reused, and store the SYN packet and the request socket in the storage according to whether the SYN packet and the request socket can be reused.

The processing unit may maintain the number of SYN packets and request sockets that can be stored in the storage as the maximum number of transmission control protocols that can be simultaneously established.

The processing unit determines whether a connection with at least one client device is absent while the timer runs and expires at least once, and if there is no connection with the at least one client device, the at least one client device is not connected. SYN packets and request sockets used for connection with the client device of may be removed from the storage.

The transmission control protocol connection processing apparatus may further include a connection list storing information on whether the at least one request socket corresponds to the at least one SYNACK packet.

A transmission control protocol connection processing method includes: receiving a SYN packet from a client device, browsing a storage according to the reception of the SYN packet, wherein the storage includes at least one SYNACK packet and at least one SYNACK packet corresponding to the at least one SYNACK packet. Storing a request socket; detecting a SYNACK packet corresponding to the SYN packet and a request socket corresponding to the SYN packet from the storage; transmitting the SYN packet to the client device; Transmitting an ACK packet as a response to the packet, receiving the ACK packet through the request socket, and establishing a transmission control protocol connection with the client device.

The transmission control protocol connection processing method includes storing the SYN packet and the request socket used for the transmission control protocol connection with the client device in the storage when the repeated connection with the client device exceeds a predefined threshold. It may include more steps.

Storing the SYN packet and the request socket in the storage includes determining whether the SYN packet and the request socket can be reused, and storing the SYN packet and the request socket in the storage according to whether the SYN packet and the request socket can be reused. may also include

The transmission control protocol connection processing method may further include maintaining the number of SYN packets and request sockets that can be stored in the storage as the maximum number of transmission control protocols that can be simultaneously established.

The transmission control protocol connection processing method includes determining whether a connection with at least one client device is absent while a timer is started and expired at least once, and if the connection with the at least one client device is absent. If so, the method may further include removing SYN packets and request sockets used for connection with the at least one client device from the storage.

According to the transmission control protocol connection processing apparatus and method described above, it is possible to solve the unnecessary processing bottleneck of the processor due to the repetitive creation of transmission control protocol connections, and thus to process more transmission control protocol connections and packets. Therefore, it is possible to obtain an advantage of being able to further improve the performance of a device such as a server device.

According to the transmission control protocol connection processing apparatus and method described above, by reusing data structures used to establish a transmission control protocol connection, overhead due to memory allocation and initialization is reduced, and processor performance is improved by maximizing a caching effect. be able to improve

According to the above-described transmission control protocol connection processing apparatus and method, even when transmission control protocol traffic is large due to a large number of repetitions of transmission control protocol connections such as hypertext transmission protocol, the server device provides services requested by clients without performance degradation. You can also get the effect of being able to provide it stably.

A detailed description of each drawing is provided in order to more fully understand the drawings cited in the detailed description of the present invention.
1 is a schematic diagram of one embodiment of a transmission control protocol connection processing system.
2 is a block diagram of an embodiment of a transmission control protocol connection processing device.
3 is a diagram showing an example of allocating instance storage for each core.
4 is a flow chart of an embodiment of a transmission control protocol connection processing method.
5 is a flowchart illustrating an embodiment of a process for determining whether to store an instance that is repeatedly used.
6 is a flowchart illustrating an embodiment of a process for removing unused instances.

In the entire specification below, the same reference numerals refer to the same components unless otherwise specified. A term with an added 'unit' used below may be implemented in software and/or hardware, and depending on an embodiment, one 'unit' may be implemented as one physical or logical component, or a plurality of 'units' may be implemented as one physical or logical component. It is possible to implement one physical or logical component, or one 'unit' to implement a plurality of physical or logical components. When a part is said to be connected to another part throughout the specification, this may mean that a part and another part are physically connected to each other and/or electrically connected. In addition, when a part includes another part, this means that it does not exclude another part other than the other part unless otherwise stated, and may further include another part according to the designer's choice. do. Expressions such as the first to Nth (N is a natural number of 1 or more) are for distinguishing at least one part (s) from other part (s), and do not necessarily mean that they are sequential unless otherwise specified. In addition, singular expressions may include plural expressions, unless there is a clear exception from the context.

An embodiment of a transmission control protocol connection processing system and a transmission control protocol connection processing apparatus will be described with reference to FIGS. 1 to 3 .

1 is a schematic diagram of one embodiment of a transmission control protocol connection processing system.

As shown in FIG. 1, the transmission control protocol connection processing system 1 (hereinafter referred to as processing system) includes, in one embodiment, a client device 10 and a server device communicatively connected to the client device 10. It may include a control protocol connection establishment control device (100, hereinafter referred to as a TCP connection processing device) that The client device 10 and the TCP connection processing device 100 may perform communication based on at least one of a mutual wired communication network and a wireless communication network. Here, the wireless communication network is a short-distance communication network (eg, Wi-Fi, Wi-Fi Direct, Bluetooth, Bluetooth Low Energy, zigbee communication, seconds Ultra-WideBand (UWB) communications, Radio-Frequency IDentification (RFID), CAN communications, and/or Near Field Communication (NFC), etc.) or telecommunication networks (e.g., 3GPP) , 3GPP2, a mobile communication network implemented based on a mobile communication standard such as WiBro or WiMAX series, etc.).

Depending on the embodiment, at least one of the client device 10 and the TCP connection processing device 100 may be implemented using one or more information processing devices, or separately for performing operations and functions described later. It may also include specially designed devices. Here, the information processing device is, for example, a hardware device for a server, a desktop computer, a laptop computer, a smart phone, a tablet PC, a smart watch, a smart tag, a smart band, a head mounted display (HMD) device, and a handheld game machine. , navigation device, personal digital assistant (PDA), voice recorder, video recording device (camcorder or action cam, etc.), scanner device, printer device, 3D printer device, smart key, remote control device (remote control), digital Televisions, set-top boxes, digital media player devices, media streaming devices, DVD playback devices, compact disc playback devices, sound playback devices (artificial intelligence speakers, etc.), home appliances, manned/unmanned mobile vehicles (vehicles, mobile robots or wireless model vehicles) etc.), manned/unmanned aerial vehicles (aircraft, drones or model airplanes, etc.), medical devices, household/industrial/military robots, or industrial/military machines, etc., but are not limited thereto.

As shown in FIG. 1 , the client device 10 and the TCP connection processing device 100 first establish a transmission control protocol-based connection (hereinafter referred to as TCP connection) for mutual communication. In this case, the client device 10 first transfers the SYN packet for the TCP connection to the TCP connection processing device 100 (p1), and the TCP connection processing device 100 performs a series of operations to be described later in response thereto , In order to confirm that the SYN packet has been received, as a response to the SYN packet, a SYNACK packet (191 in FIG. 2) corresponding to the SYN packet is transmitted to the client device 10 (p2). In response to the SYNACK packet 191, the client device 10 transmits an ACK packet for confirming that the SYNACK packet 191 has been received to the TCP connection processing device 100 (p3), and accordingly the client device ( 10) and a TCP connection between the TCP connection processing device 100 is established. Thereafter, the client device 10 and the TCP connection processing device 100 can transmit data, commands/instructions, or programs in one or both directions based on the TCP connection.

2 is a block diagram of an embodiment of a transmission control protocol connection processing device, and FIG. 3 is a diagram showing an example of allocating instance storage for each core.

As shown in FIG. 2 , in one embodiment, the TCP connection processing device 100 may use the two instances 191 and 192 at least once before transmitting the SYNACK packet 191 (p2). The two instances may include a SYNACK packet 191 corresponding to the SYN packet and a request socket 192, which is a socket for receiving an ACK packet corresponding to the SYNACK packet 191. Normally, the states of the SYNACK packet 191 and the request socket 192 in the connection between the same client device 10 and the TCP connection processing device 100 are maintained without significant change. According to one embodiment, the SYNACK packet 191 is selected from at least one SYNACK packet 191-1 to 191-k stored in the storage 120, and the request socket 192 is also stored in the storage 120. may be one selected from at least one request socket 192-1 to 192-k. Here, the SYNACK packets 191-1 to 191-k stored in the storage 120 and at least one request socket 192-1 to 192-k stored in the storage 120 are each of the above-described client devices ( 10) Alternatively, it may be a SYNACK packet and a request socket previously used in the communication process with other client devices. In other words, the SYNACK packet 191 and the request socket 192 for establishing a connection with the client device 10 may be reused. By reusing the SYNACK packet 191 and the request socket 192, the initialization process performed in the conventional TCP connection process becomes unnecessary.

Referring to FIG. 2 , the TCP connection processing device 100 may include a communication unit 101 , a storage 120 , and a processing unit 130 in one embodiment.

The communication unit 101 connects to a wired or wireless communication network, receives packets (eg, SYN packets) from the client device 10 and transfers them to the listen socket 102, or packets to the client device 10. (eg, SYNACK packet 191) may be transmitted. The communication unit 101 receives an electrical signal or radio wave signal transmitted from the outside, converts the received signal into an electrical signal and outputs it, converts the received analog signal into a digital signal, or amplifies the electrical signal. can also be performed. The communication unit 101 may be implemented using, for example, a LAN card or a wireless communication module.

A listen socket (102, listen socket) is a socket for receiving incoming connections. For example, when at least one packet (for example, a SYN packet or an ACK packet) transmitted by the client device 10 is transmitted, the listen socket 102 transfers information corresponding thereto to the processing unit 130, thereby processing the processing unit ( 130) makes it possible to know that a TCP connection request has come from the client device 10.

The storage 120 may temporarily or non-temporarily store instances such as at least one SYNACK packet 191-1 to 191-k and one request socket 192-1 to 192-k. In this case, the storage 120 may store SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k in pairs according to their correspondence. According to one embodiment, the SYNACK packets 191-1 to 191-k and the request sockets 192-1 to 192-k are previously generated in the process of establishing a TCP connection with the client device 10 or another client device. SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k. In other words, the SYNACK packets 191-1 to 191-k are packets transmitted to the client device 10 or other client devices in the past, and the request sockets 192-1 to 192-k are packets transmitted to the client device 10 in the past. ) or a socket that receives an ACK packet sent by another client device. Depending on circumstances, new SYNACK packets and/or request sockets may be further stored in the archive 120, and existing SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k At least one of them may be deleted. Storage or deletion of these SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k may be performed by the processing unit 130. Depending on the embodiment, the storage may be optimized by applying a lock-less method to maintain scalability in a multi-core system. According to embodiments, the storage 120 may be implemented using at least one main memory device (RAM, etc.) or auxiliary memory device (flash memory device, hard disk device, etc.).

The processing unit 130 may perform various operations or control operations necessary for the operation of the TCP connection processing device 100, for example, generation of the listen socket 102, SYNACK packet 191, and request socket 192. ) Search and determination, management of the storage 120 and/or control of the communication unit 101 may be performed. The processing unit 130 may also perform the above-described operation by driving a program (which may be referred to as an app, application, or software) stored in a storage medium (not shown). The processing unit 130 may include a central processing unit (CPU), a graphic processing unit (GPU), a micro controller unit (MCU), an application processor (AP), according to an embodiment. Processor), electronic control unit (ECU), and/or at least one electronic device capable of performing other various calculation and control processes. In addition, the processing unit 130 includes at least one core 140-1 to 140-n among a plurality of cores 140-1 to 140-n in FIG. 3 (ie, multi-core) of the central processing unit (CPU). At least one of) may be implemented using.

According to an embodiment, the processing unit 130 may include a storage processing unit 131 , a storage processing unit 132 , an instance removal unit 133 , and a reuse determination unit 134 .

The storage processing unit 131 may perform an operation of detecting instances in the storage 120 . Specifically, the storage processing unit 131 obtains information about the client device 10 from the information of the first received SYN packet, and the instance matching the pair information of the client device 10 and the TCP connection processing device 100 (ie, , SYNACK packet 191 and request socket 192) can be checked whether they exist in the archive. If SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k of the repository 120 match the pair information of the client device 10 and the TCP connection processing device 100, If the packet 191 and the request socket 192 exist, they are detected from the storage 120 as the SYNACK packet 191 and the request socket 192 to be used, and reused for TCP connection establishment. Thereafter, the TCP connection processing device 100 exchanges SYNACK packets and ACK packets with the client device 10 as shown in FIG. 1 (p2, p3). If the TCP connection is normally created, the corresponding instance (that is, the SYNACK packet 191 and the request socket 192) is stored in the storage again. In other words, during the TCP connection process, the memory allocator allocates the SYNACK packet 191 and the request socket 192, and according to the establishment of the TCP connection, the SYNACK packet 191 and the request socket 192 are released and returned to the memory allocator. Repeated execution of the operation becomes unnecessary. In this way, omission of repetitive allocation, release, and initialization processes can improve TCP connection establishment performance. According to an embodiment, the storage processing unit 131 may use a predetermined hash table to detect the SYNACK packet 191 and the request socket 192. According to the use of the hash table, the storage processing unit 131 can find the SYNACK packet 191 and the request socket 192 within a constant time on average. In addition, the storage processing unit 131 may detect the SYNACK packet 191 and the request socket 192 corresponding to each other by referring to the connection list 199 . The connection list 199 may sequentially or non-sequentially store information on correspondence between the SYNACK packets 191-1 to 191-k and the request sockets 192-1 to 192-k recorded in the storage 120. , and the storage processing unit 131 can more quickly detect SYNACK packets 191-1 to 191-k and request sockets 192-1 to 192-k that correspond to each other by referring to this.

The storage processing unit 132 performs storage processing of used instances (ie, SYNACK packets (eg, 191) and request sockets (eg, 192) used in the previous or current TCP connection establishment process). More specifically, the storage processing unit 132 determines a pair of the TCP connection processing device 100 and the client device 10 to store the instances 191 and 192, and stores the instances 191 and 192 in the storage 120. 192) can be stored. According to an embodiment, the storage processing unit 132 may use a threshold value to determine a pair of the TCP connection processing device 100 and the client device 10 to store the instances 191 and 192 . In this case, the storage processing unit 132, if there is a pair of the TCP connection processing device 100 and the client device 10 repeatedly connected beyond a predefined threshold for a certain period of time, the corresponding TCP connection processing device 100 and the client It is determined that the pair of devices 10 are repeatedly connected, and instances 191 and 192 used to establish a connection between the corresponding TCP connection processing device 100 and the client device 10 may be stored. In addition, the archive processing unit 132 sets the number of instances to be stored in the archive 120, that is, the number of SYNACK packets 191-1 to 191-k and/or the number of request sockets 192-1 to 192-k. To determine, you can also manage the number of TCP connections that can be created simultaneously. In this case, the storage processing unit 132 can simultaneously establish the number of instances 191-1 to 191-k and 192-1 to 192-k to be stored in the storage 120 for a certain period of time (for example, a time window). It can also be maintained with the maximum number of TCP connections. This is because the state of each of the plurality of instance(s) (191-1 to 191-k, 192-1 to 192-k) can be reused, but the state that distinguishes each connection is not shared, so that multiple instances are almost simultaneously This is because, if TCP connection establishment is being performed, the number of instances 191 and 192 corresponding to the number of TCP connections is requested for their processing.

The instance removal unit 133 may determine an unnecessary instance (that is, an instance that is no longer used) as a removal target, and may remove the corresponding instance from the storage 120 as needed. The instance removal unit 133 includes the TCP connection processing device 100 and the client device (at least one of 191-1 to 191-k and at least one of 192-1 to 192-k) corresponding to a specific pair of instances. If the pair of 10) is not repeatedly connected, instances of the pair (at least one of 191-1 to 191-k and at least one of 192-1 to 192-k) may be determined as a target for removal. For this purpose, the instance removal unit 133 may use a timer. Specifically, the timer repeatedly expires at regular intervals, and the instance removal unit 133 browses the storage 120 whenever the timer expires, so that a pair of TCP connection processing device 100 and client device 10 has repeated connection characteristics. is lost, and based on the check result, whether to remove the pair of the corresponding TCP connection processing device 100 and the client device 10 may be determined. For example, if the TCP connection processing device 100 and the client device 10 are not connected to each other at all while the timer expires, the instance removal unit 133 may determine that the repeated connection characteristic is lost, Alternatively, if the corresponding TCP connection processing device 100 and the client device 10 are not connected to each other at all while the timer expires twice, it may be determined that the repeated connection characteristic is lost. The timer may be provided separately for each of the plurality of cores 140-1 to 140-n described later, or one or more timers may be globally used by the plurality of cores 140-1 to 140-n. there is.

The reuse determination unit 134 may determine whether the instance to be stored, for example, the SYNACK packet 191 and/or the request socket 192 is reusable. Being reusable means a state in which the instances 191 and 192 can be used as they are without changing values, and specifically, the connection between the client device 10 and the TCP connection processing device 100 must be repeatedly performed, Each instance used for this, for example, the SYNACK packet 191 and the request socket 192 should be able to be stored in the storage 120. However, specific data may be reused in another TCP connection, but other data may not be reused. For example, since the protocol family, Internet Protocol (IP) address, port number, or routing information has the same value in the connection between the same client device 10 and the TCP connection processing device 100, reuse is possible, but packet Sequence numbers or timestamps cannot be reused because they must be newly initialized each time a connection is made. The reuse determination unit 134 may determine whether or not the instance 191 or 192 can be reused or not, and determine whether the corresponding instance 191 or 192 is stored in the storage 120 . The determination result may be transmitted to the storage processing unit 132, and in this case, the storage processing unit 132 may store the corresponding instances 191 and 192 based on the determination result.

In one embodiment, the processing unit 130 may use a soft interrupt request (Soft IRQ) along with the TCP stack to perform the above-described operation. Specifically, in order for the processing unit 130 to perform the above-described processing, synchronization of the structure of the SYNACK packet 191 and the request socket 192 is requested. In the case of newly adding or deleting , local IRQ disabling may be used for synchronization. In general, a soft interrupt request can be divided into a case where it is directly performed by a hardware interrupt and a case where it is processed by a ksoftirqd process. Since the ksoftirqd process is a user process, it may be preempted from a hardware interrupt. Therefore, a minimum lock can be generated within the same processing unit (core, 130: 130-1 to 130-k). When the new instances 191 and 192 are allocated, the processing unit 130 may prevent such a lock from occurring by inactivating the regional interrupt requests occupied by the cores 130-1 to 130-k for a short period of time.

According to one embodiment, the processing unit 130, for example, the cores 130-1 to 130-k, detect instances such as SYNACK packets 191 and request sockets 192 from the storage 120 or send them back. In this case, synchronization may be performed. If two pairs of instances (eg, (191, 192) and (191-1, 192-1)) are required at the same time, this means that two TCP connection establishments are being performed, so different instances must be used. To this end, the processing unit 130 may use a general atomic operation technique, and accordingly, busy waiting becomes unnecessary and synchronization costs can be reduced.

According to one embodiment, as shown in FIG. 3 , the TCP connection processing device 100 may include a plurality of storages 120-1 to 120-n. At least one of these storages 120-1 to 120-n, as described above, includes at least one SYNACK packet 191-1 to 191-k and at least one request socket 192-1 to 192-k corresponding thereto. k) can be stored. Meanwhile, the TCP connection control device may include a plurality of processing units 130, and each of the plurality of processing units 130 stores or deletes an instance of the storage 120 corresponding to each of the plurality of processing units 130. etc. can be controlled. Each processing unit 130 may be implemented using each of the cores 140-1 to 140-n as described above. In this case, according to an embodiment, each storage 120-1 to 120-n may be provided to correspond to each of the plurality of cores 140-1 to 140-n. As described above, as the storage 120 is used, it is possible to omit allocation, deallocation, and/or initialization, but overall performance is affected by performance degradation due to the use of the storage 120. In order to prevent performance degradation due to storage 120-based operations, processing of the same connection is performed by the same cores 140-1 to 140-n, and in this case, each core 140-1 to 140-n corresponds to The corresponding connection is processed using the repositories 120-1 to 120-n. That is, the storages 120-1 to 120-n are separated for each core 140-1 to 140-n and then fixed to the cores 140-1 to 140-n. According to an embodiment, a Receive-Side Scaling (RSS) technology of a Network Interface Controller (NIC) may be used for this purpose. In this case, the core (at least one of 140-1 to 140-n) that has received the SYN packet performs all of the corresponding TCP connection processing, and transfers the used instance to another core (at least one of 140-1 to 140-n). or does not receive an instance used by the other core (at least one of 140-1 to 140-n) from the other core (at least one of 140-1 to 140-n). When the storage 120 is used globally, the locality of the instances 191-1 to 191-k and 192-1 to 192-k is reduced and a lock is generated. In particular, occurrence of lock causes delay due to busy weighting between cores. However, as described above, when different cores 140-1 to 140-n process different storages 120-1 to 120-n, not only cache coherency is maintained, but locks are not used, so Unnecessary performance degradation can be avoided.

Referring to FIGS. 4 to 6, an embodiment of a transmission control protocol connection processing method will be described.

4 is a flow chart of an embodiment of a transmission control protocol connection processing method.

As shown in FIG. 4, a listen socket is determined for a transmission control protocol connection process (TCP connection process), and a SYN packet is received from a client device through the listen socket (400).

If the SYN packet is received, the archive may be browsed in response (404). One or more pairs of instances (SYNACK packet and request socket) may be stored in advance in the archive.

Through browsing of the storage, it may be determined whether an instance (SYNACK packet and request socket) corresponding to the SYN packet exists in the storage (406). If the corresponding SYNACK packet and request socket exist in the archive (YES in 406), the corresponding SYNACK packet and request socket are used for connection between the client device that transmitted the received SYN packet and the TCP connection processing device (408). Conversely, if the corresponding SYNACK packet and request socket do not exist in the storage (No in 406), a new instance (SYNACK packet and request socket) may be created by a memory allocator or the like.

The archived or newly generated SYNACK packets may be delivered to the client device (410).

The client device generates and sends an ACK packet in response to reception of the SYNACK packet, and the TCP connection processing device receives the ACK packet sent through the request socket (412).

Accordingly, a connection between the client device and the TCP connection processing device is established (414).

5 is a flowchart illustrating an embodiment of a process for determining whether to store an instance that is repeatedly used.

Meanwhile, the TCP connection processing device may determine whether to store an instance used for repeated connections between a specific client device and a TCP connection processing device, as shown in FIG. 5 .

Specifically, for example, when a TCP connection is first established between a specific client device and a TCP connection processing device, the number of connection establishments is counted (412).

The count result and the predefined threshold value are compared (422), and if the count result is greater than the threshold value (Yes in 422), the TCP connection between the specific client device and the TCP connection processing device is considered to have a repetitive characteristic. It is judged (423).

In this case, the instances used for the connection between the specific client device and the TCP connection processing device (ie, SYNACK packet and request socket) are stored in the storage (424).

Conversely, if the comparison result coefficient is smaller than the threshold value (No in 422), the above-described processes 423 and 424 are not performed.

The above-described processes 421 to 425 may be repeated until a predetermined time (time window) elapses. If it is determined that the connection between the specific client device and the TCP connection processing device is repetitive (ie, when the count result is greater than the threshold value (Yes in 422)), the repetition may be stopped (425). In other words, if the connection between the specific client device and the TCP connection processing device is smaller than the threshold value (No in 422), the process of creating and counting the connection or storing the instance according to the comparison result of the threshold value (421 to 424) continues. can be repeated.

6 is a flowchart illustrating an embodiment of a process for removing unused instances.

Also, as shown in FIG. 6 , the TCP connection processing device may determine whether or not to remove an instance previously stored in a storage and used for a connection between a specific client device and a TCP connection processing device.

Specifically, for example, the timer starts driving and expires after a predetermined time (which may be determined by a user or a designer) has elapsed (431) according to a predefined bar.

When the timer expires (every time the timer expires according to an embodiment), it may be determined whether an additional or repeated connection exists between at least one specific client device and the TCP connection processing device (432).

If, by the time the timer expires, no additional or repetitive connections exist between the at least one specific client device and the TCP connection processing device (NO in 432), the absence of additional or repetitive connections is counted, and the count result (i.e. , The number of times of operation of the timer in which there was no connection between the two devices during the operation period) may be determined (433) whether the number of times of operation of the timer previously defined by the user or designer (eg, twice) is exceeded.

If the number of additional or repetitive connection absences exceeds the predefined number of times (Yes in 433), instances used for TCP connection establishment (i.e., SYNACK packets and request sockets) of a specific client device and TCP connection processing device are deleted. Remove from storage (434). As a result, it is possible to optimally manage the storage by removing unnecessary instances.

Conversely, if the number of additional or repetitive connection absences does not exceed the predefined reference number (No in 433), instances used for TCP connection establishment of a specific client device and TCP connection processing device are continuously maintained in the storage.

On the other hand, if at least one specific client device and the TCP connection processing device have been connected to each other while the timer is running (Yes in 432), the above-described reference number exceeding determination 433 or instance removal operation 434 is not performed. .

The above process may be continuously repeated (435). Therefore, the timer continuously, periodically or arbitrarily starts and expires (431), and accordingly, whether or not a repeated connection between a specific client device and a TCP connection processing device is determined (432), and the instance is removed accordingly. Whether or not it can be determined (433, 434).

The transmission control protocol connection processing method according to the above-described embodiment may be implemented in the form of a program that can be driven by a computer device. The program may include commands, libraries, data files, and/or data structures alone or in combination, and may be designed and manufactured using machine language codes or high-level language codes. The program may be specially designed to implement the above-described method, or may be implemented using various functions or definitions known and usable to those skilled in the art in the field of computer software. Also, here, the computer device may be implemented by including a processor or a memory capable of realizing program functions, and may further include a communication device as needed. A program for implementing the transmission control protocol connection processing method described above may be recorded on a recording medium readable by a device such as a computer. A computer-readable recording medium is, for example, a semiconductor storage medium such as ROM, RAM, SD card or flash memory (for example, a solid state drive (SSD), etc.), or a magnetic disk storage such as a hard disk or a floppy disk. At least one program capable of temporarily or non-temporarily storing one or more programs executed by a device such as a computer, such as a medium, an optical recording medium such as a compact disk or DVD, or a magneto-optical recording medium such as a floptical disk, etc. type of physical storage medium.

Although various embodiments of the transmission control protocol connection processing device and transmission control protocol connection processing method have been described above, the transmission control protocol connection processing device or transmission control protocol connection processing method is not limited to the above-described embodiment. Various other devices or methods that can be implemented by modifying and transforming based on the above-described embodiments by those skilled in the art may also be an embodiment of the above-described transmission control protocol connection processing device or transmission control protocol connection processing method. can For example, the described method(s) may be performed in an order different from that described, and/or component(s) of a described system, structure, device, circuit, etc. may be coupled, connected, or otherwise used in a manner other than described. Even if they are combined or substituted or substituted by other components or equivalents, it may be an embodiment of the above-described transmission control protocol connection processing device and/or transmission control protocol connection processing method.

10: client device 100: transmission control protocol connection device
102: listen socket 120: storage
130: processing unit 191: SYNACK packet
192: request socket

Claims (11)

a repository for storing at least one SYNACK packet and at least one request socket corresponding to the at least one SYNACK packet; and
When a SYN packet is received from a client device, a processing unit that browses the repository and detects a SYNACK packet corresponding to the SYN packet and a request socket corresponding to the SYN packet from the repository;
The SYN packet is transmitted to the client device, and the request socket receives an ACK packet transmitted by the client device in response to the SYN packet, thereby establishing a transmission control protocol connection with the client device Transmission control protocol connection processing Device. According to claim 1,
The processing unit stores the SYN packet and the request socket used for the transmission control protocol connection with the client device in the storage when the repeated connection with the client device exceeds a predefined threshold. processing unit. According to claim 2,
The processing unit determines whether the SYN packet and the request socket can be reused, and stores the SYN packet and the request socket in the storage according to whether the SYN packet and the request socket can be reused. According to claim 1,
The processing unit maintains the number of SYN packets and request sockets that can be stored in the storage as the maximum number of transmission control protocols that can be established simultaneously. According to claim 1,
The processing unit determines whether a connection with at least one client device is absent while the timer runs and expires at least once, and if there is no connection with the at least one client device, the at least one client device is not connected. A transmission control protocol connection processing device that removes SYN packets and request sockets used for connection with a client device of the storage from the storage. According to claim 1,
and a connection list storing information on whether the at least one request socket corresponds to the at least one SYNACK packet. receiving a SYN packet from a client device;
browsing a repository according to reception of a SYN packet, wherein the repository stores at least one SYNACK packet and at least one request socket corresponding to the at least one SYNACK packet;
detecting a SYNACK packet corresponding to the SYN packet and a request socket corresponding to the SYN packet from the storage;
sending the SYN packet to the client device;
transmitting, by the client device, an ACK packet in response to the SYN packet;
receiving the ACK packet through the request socket; and
A transmission control protocol connection processing method comprising the step of establishing a transmission control protocol connection with the client device. According to claim 7,
If the repeated connection with the client device exceeds a predefined threshold, storing the SYN packet and the request socket used for the transmission control protocol connection with the client device in the storage; transmission control further comprising How protocol connections are handled. According to claim 8,
The step of storing the SYN packet and the request socket in the storage,
determining whether SYN packets and request sockets can be reused; and
and storing the SYN packet and the request socket in the repository according to whether they can be reused. According to claim 7,
and maintaining the number of SYN packets and request sockets that can be stored in the storage as the maximum number of transmission control protocols that can be simultaneously established. According to claim 7,
determining whether a connection with at least one client device is absent while the timer is driven and expired at least once; and
If there is no connection with the at least one client device, removing the SYN packet and the request socket used for the connection with the at least one client device from the repository.