KR102451096B1 - System and method for multi-layer performance analysis of arbitrary section in network through socket control interface - Google Patents

Abstract

The present invention relates to a multi-layer performance analysis system of an arbitrary section in a network through a socket control interface and a method therefor that perform a multi-layer performance analysis for a network through a socket (TCP, UDP) control interface connected to the network, and enable to perform an analysis for where there is a problem among all the equipment and sections involved in communication from a client to a server. The multi-layer performance analysis system comprises: a socket interface part; a background processing part; a script initialization part; and a script flow processing part.

Description

{System and method for multi-layer performance analysis of arbitrary section in network through socket control interface}

The present invention relates to a performance analysis of an arbitrary section within a network, and in particular, performs multi-layer performance analysis on a network through a socket (TCP, UDP) control interface connected to the network to perform multi-layer performance analysis with all equipment involved in communication from a client to a server and It relates to a multi-layer performance analysis system and method for an arbitrary section in a network through a socket control interface that is suitable for performing analysis on where there is a problem in the section.

In general, all client-server communication is based on the client connecting to the network to which the server is connected through several different networks through the network to which it is connected, and ultimately exchanging data with the server.

1 is a conceptual diagram illustrating the structure of a typical client-server.

Therefore, when performing communication between a specific client-server, it can go through several networks. Also, in some cases, data may be transmitted through different paths even when accessing the same server.

When data is transmitted, which device or network it will go through depends on the routing and communication rules set on each device.

Each network is composed of a number of communication equipment and security equipment. In the case of communication quality degradation or communication abnormality, it is most important to find out which equipment is the cause of the problem.

Conventionally, there is LAYER-3 PERFORMANCE MONITORING SECTIONALIZATION of US Patent Registration No. 9306830 filed by Accedian Network Inc. Accedian supports various media of the network using GBIC (Gigabit Interface Converter, Gigabit Access Converter), which is hardware developed by using these technologies. It is called 'Technology 1'.)

In the prior art 1, the network to be verified is TCP/IP. The starting hardware is a GBIC developed by Accedian. In terms of usage, it is limited to switches that can use GBIC. If the GBIC is not compatible with the switch, it cannot be used. Also, if there is no port to insert GBIC, it cannot be used. Supportable protocols are designated protocol protocols, such as TWAMP (Two-Way Active Measurement Protocol, Bidirectional Active Measurement Protocol)/UDP (User Datagram Protocol, User Datagram Protocol). Looking at the test scenario, in the prior art 1, only a scenario designated based on a round trip time (RTT) can be used. Looking at the applicable environment, the prior art 1 is dependent on the switch.

In addition, conventionally, Cisco (Cisco Technology, Inc.) assigned a special function to a switch or router, and performed network performance analysis. (Hereinafter, Cisco's network performance analysis technology using a switch is referred to as 'Prior Art 2'.)

In the prior art 2, the network to be verified is TCP/IP. Startup hardware is hardware that Cisco gives special functions to a switch or router. In terms of usage, the network performance analysis function is activated in the switch. If the switch does not have a network performance analysis function, network performance analysis cannot be used. In addition, it is difficult to provide a flexible test environment because the CPU embedded in the switch is specialized for switching. Supportable protocols are designated protocol conventions, such as TWAMP/UDP. Looking at the test scenario, in the prior art 2, only the scenario designated as RTT center can be used. Looking at the applicable environment, the prior art 2 is dependent on the switch.

As such, the prior art is dependent on a specific hardware or interface based on hardware when analyzing network performance, and has a limitation in network performance analysis function.

US 9,306,830 B2

Accordingly, the present invention has been proposed in order to solve the problems of the related art as described above, and an object of the present invention is to perform multi-layer performance analysis on a network through a socket (TCP, UDP) control interface connected to the network to perform multi-layer performance analysis from the client to the server. An object of the present invention is to provide a multi-layered performance analysis system and method for an arbitrary section in a network through a socket control interface that can analyze where there is a problem among all equipment and sections involved in communication with the network.

2 is a block diagram of a multi-layer performance analysis system of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.

As shown here, the multi-layer performance analysis system 100 and a socket interface unit 110 to perform an interface with the TCP or UDP socket of the network; a background processing unit 120 communicating with the network through the socket interface unit 110, determining whether communication is successful according to data communication with the network by a script, and performing multi-layer performance analysis on the network; a script initialization unit 130 that initializes a script for performing network performance analysis through the socket interface unit 110; Flow processing through the background processing unit 120 is performed on the script initialized by the script initialization unit 130, and a TCP handshake is performed if the script includes TCP, and the TCP or UDP data is processed. It is characterized in that it comprises a; script flow processing unit 140 for performing transmission and reception processing to the network.

The background processing unit 120 measures the time required for the TCP handshake when the script flow processing unit 140 performs the TCP handshake, and measures the time between data transmission and reception during TCP or UDP data transmission and reception to RTT ( Round Trip Time) is calculated, and the total amount of data is analyzed as sending and receiving time to extract BPS (Bits Per Second) to determine whether the cause of failure is a timeout or a socket error, It is characterized in that it analyzes the layer and network section where the problem occurs among each of the L2 header, L3 header, L4 header, and payload, which are multi-layers of the network, and analyzes the cause of the problem using RTT and BPS and timeout information. .

The multi-layer performance analysis system 100 includes a function of generating large-scale dummy data, a function of converting between binary data and hexadecimal text, and accessing resources that are difficult to access in a script or having a relatively low speed. It is characterized in that it further includes a; utility processing unit 150 that provides a utility function so that it can be called and used by the script flow processing unit 140 by providing functions that require fast processing for a reason of being slow.

7 is a flowchart illustrating a multi-layer performance analysis method of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.

As shown in this figure, the socket interface unit 110 of the multi-layer performance analysis system 100 performs an interface with a TCP or UDP socket of the network to start communication with the network, a socket interface step (ST1); a script initialization step (ST2) of performing initialization on a script for performing network performance analysis after the socket interface step; The script flow processing unit 140 performs flow processing on the script initialized in the script initialization step, and when the script includes TCP, a TCP handshake is performed, and TCP or UDP data is transmitted to the network and reception processing, and the background processing unit 120 determines whether communication is successful according to data communication with the network by the script, performs multi-layer performance analysis on the network, and outputs the test result of the performance analysis on the network Script and background processing steps (ST3, ST4); characterized in that it is performed including.

8 is a detailed flowchart of FIG. 7 .

In the script and background processing step, if the socket accessed by the socket interface unit 110 is a TCP socket, the script flow processing unit 140 performs a TCP handshake, and the background processing unit 120 performs the TCP handshake. a TCP handshake step (ST11 to ST17) of diagnosing whether the TCP handshake succeeds or fails by measuring the required time; If the socket is not a TCP socket or after the TCP handshake step, the script flow processing unit 140 processes a script for data transmission of TCP or UDP, and the background processing unit 120 performs an operation between transmission and reception of data. Time is measured to calculate RTT, and BPS is extracted by analyzing the total amount of data as transmission/reception time to determine whether the cause of failure is a timeout or socket error. The data transmission/reception processing step (ST18 ~ ST26) that analyzes the layer and network section in which the problem occurs in each payload, and analyzes the cause of the problem using RTT and BPS and timeout information (ST18 ~ ST26); characterized in that it is performed do.

FIG. 9 is a flowchart showing processing when the script in FIG. 7 is a TCP fast reconnection script.

As shown in this figure, in the script and background processing step, if the script is TCP fast reconnection, a TCP handshake is performed to a designated server to generate a TCP handshake event, and the operation of disconnecting the connection when connected to the server is repeated a plurality of times. TCP fast reconnection execution step (ST31 ~ ST35); In the TCP fast reconnection performing step, when the number of repetitions of a plurality of times is terminated, a determination step of determining a failure if a connection cannot be made in the middle of the number of repetitions, and determining success if all connections are made in the number of repetitions of the plurality of repetitions (ST36) It is characterized in that it is performed including ;.

FIG. 10 is a flowchart showing processing when the script in FIG. 7 is an HTTP HEAD script.

As shown in this figure, the script and background processing step is, if the script is an HTTP HEAD script, performs a TCP handshake to generate a TCP handshake event, and sends an HTTP HEAD request when connected to the server (ST41) ~ ST44) and; When the server sends data in the HTTP HEAD execution step, a sub response event is generated, data transmission and reception status and RTT are checked, and when the server does not respond for a certain period of time in the HTTP HEAD execution step, a timeout event is generated. Steps (ST45 ~ ST48); characterized in that it is performed including.

FIG. 11 is a flowchart showing processing when the script in FIG. 7 is a UDP RTT script.

As shown in this figure, the script and background processing steps include: if the script is a UDP RTT script, UDP RTT processing steps (ST51, ST52) of sending data to a designated server; After the UDP RTT processing step, if a server response event occurs, success processing is performed, and when a server response event does not occur, a determination step (ST53, ST54) of failure processing is performed.

FIG. 12 is a flowchart showing processing in the case where the script in FIG. 7 is an SMTP EHLO script.

As shown in this figure, the script and the background processing step, if the script is an SMTP (Simple Mail Transfer Protocol) EHLO (extended Hello, Extended HELLO) script, performs a TCP handshake to perform a TCP handshake SMTP EHLO processing step (ST61 ~ ST64) of generating an event and sending an EHLO message when connected to the server; In the SMTP EHLO processing step, when a message indicating that the server is ready for domain service is received, complete processing, and the SMTP EHLO processing step When the connection is forcibly disconnected from the server in the processing step, a connection disconnection event is generated, and a determination step (ST65 to ST69) of processing a socket error and failure is performed.

A multi-layer performance analysis system and method of an arbitrary section in a network through a socket control interface according to the present invention perform multi-layer performance analysis on a network through a socket (TCP, UDP) control interface connected to the network, and transfer from a client to a server. It has the effect of being able to analyze where there is a problem among all equipment and sections involved in the communication of

1 is a conceptual diagram illustrating the structure of a typical client-server.
2 is a block diagram of a multi-layer performance analysis system of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.
3 is an exemplary diagram of a network to which the present invention of FIG. 2 is applied.
4 is a conceptual diagram illustrating an example of performing multi-layer performance analysis of an arbitrary section in a network according to FIG. 2 .
5 is a structural diagram of a general network packet for performance analysis of the present invention.
6 is a conceptual diagram illustrating a test scenario application of the present invention.
7 is a flowchart illustrating a multi-layer performance analysis method of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.
8 is a detailed flowchart of FIG. 7 .
FIG. 9 is a flowchart showing processing when the script in FIG. 7 is a TCP fast reconnection script.
FIG. 10 is a flowchart showing processing when the script in FIG. 7 is an HTTP HEAD script.
FIG. 11 is a flowchart showing processing when the script in FIG. 7 is a UDP RTT script.
FIG. 12 is a flowchart showing processing in the case where the script in FIG. 7 is an SMTP EHLO script.

A preferred embodiment of a multi-layer performance analysis system and method of an arbitrary section in a network through a socket control interface according to the present invention configured as described above will be described in detail with reference to the accompanying drawings. In the following description of the present invention, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And the terms to be described later are terms defined in consideration of functions in the present invention, which may vary depending on the intention or precedent of the user or operator, and accordingly, the meaning of each term should be interpreted based on the contents throughout this specification. will be.

First, the present invention is to perform multi-layer performance analysis of the network through a socket (TCP, UDP) control interface connected to the network to analyze where there is a problem among all equipment and sections involved in communication from the client to the server. will be.

2 is a block diagram of a multi-layer performance analysis system of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.

The multi-layer performance analysis system 100 of the present invention can be configured to include a socket interface unit 110 , a background processing unit 120 , a script initialization unit 130 , a script flow processing unit 140 , and a utility processing unit 150 . have.

The socket interface unit 110 allows the multi-layer performance analysis system 100 to interface with a TCP or UDP socket of a network. The socket interface unit 110 processes including a raw Internet Protocol (IP), Stream Control Transmission Protocol (SCTP) socket, etc. in addition to TCP and UDP.

The background processing unit 120 communicates with the network through the socket interface unit 110 , and determines whether communication is successful according to data communication with the network using a script, and performs multi-layer performance analysis on the network. Therefore, the background processing unit 120 measures the time required for the TCP handshake when the script flow processing unit 140 performs the TCP handshake, and calculates the RTT by measuring the time between data transmission and reception during TCP or UDP data transmission and reception. , analyzes the total amount of data by transmission/reception time to extract BPS to determine whether the cause of failure is a timeout or socket error and network section, and provide the cause of the problem by using RTT and BPS and timeout information.

Here, the RTT (Round Trip Time) analyzed by the background processing unit 120 measures the time from requesting data from the client to receiving a response from the server. Also, bits per second (BPS) measures the maximum amount of data that can be uploaded or downloaded. Also, a timeout is a kind of error, but is also included in the measurement target. So, in the case of timeout, there is no response when a connection is attempted, or one party abruptly stops transmission during data exchange.

The script initialization unit 130 initializes a script for performing network performance analysis through the socket interface unit 110 . The script initialization unit 130 may or may not be used as needed. The script initialization unit 130 initializes the contents to be prepared before communication, such as declaring global variables (eg, a counter for the number of connection attempts) and creating a necessary data dictionary (eg, a dummy payload of 1 GB or more for a network overload test). use it to

The script flow processing unit 140 performs flow processing through the background processing unit 120 for the script initialized by the script initialization unit 130, and when the script includes TCP, a TCP handshake is performed, and TCP Alternatively, transmission and reception of UDP data to and from the network are performed. Therefore, the script flow processing unit 140 is used to control the socket, control communication in response to a major event of the socket, and proceed with a test scenario. The script flow processing unit 140 may be configured as an event handler according to communication start, communication execution, success declaration, and data reception.

The utility processing unit 150 includes a function of generating a large-scale dummy data, a function of converting between binary data and hexadecimal text, accessing a resource that is difficult to access in a script, or fast processing due to a relatively slow speed. By providing necessary functions, a utility function is provided so that the script flow processing unit 140 can call and use it.

3 is an exemplary diagram of a network to which the present invention of FIG. 2 is applied.

As shown in Figure 3, the multi-layer performance analysis system 100 is a network such as system A (100A) ~ system E (100E), various locations of clients, servers, and intermediate network devices (routers, switches, security devices, etc.) can connect to Therefore, the multi-layer performance analysis system 100 can perform both the server and client roles according to the contents (test scenario) of the mounted test script. If the server communication of the system B 100B is normal but there is a problem in the communication of the system A 100A, it may be determined that there is a problem in the office switch to which the system A 100A is connected.

Similarly, when system C (100C) is acting as a client, communication to system D (100D) or server farm server (100E) is fine, but when system C (100C) is acting as a server, system A (100A) If both and the system B (100B) cause a problem, it can be determined that there is a problem in the server farm switch (100D).

4 is a conceptual diagram illustrating an example of performing multi-layer performance analysis of an arbitrary section in a network according to FIG. 2 .

Each network is composed of a number of communication equipment and security equipment. At this time, when communication quality deterioration or communication abnormality occurs, it is most important to find out which equipment is the cause of the problem.

Therefore, the section analysis according to the present invention makes it possible to find out which section has a problem among all equipment and sections involved in communication from the client to the server.

In the case of the structure shown in FIG. 4, if the sections are analyzed while moving in the order of A→B→C, it is possible to quickly find the equipment (IMPACT) causing the problem.

5 is a structural diagram of a general network packet for performance analysis of the present invention.

Therefore, the present invention can analyze multiple layers of network packets such as Ethernet as an L2 header, IP as an L3 header, TCP or UDP as an L4 header, and payload as actual data. So, when a problem occurs in the network, it is possible to identify in which network layer the problem occurred.

If you are only interested in L3 when performing network performance analysis, configurations below L4 are ignored. If you are interested in a particular L7 protocol, all headers and payloads are meaningful. When creating a test script, the structure and content of the test script can be configured differently depending on which layer you are interested in. For example, if only L4 communication is involved, the payload can be filled with arbitrary data, or the payload can be sent empty. If you mimic HTTP communication, you can make the script generate HTTP request and response related content in the payload. The contents of the script can be configured differently depending on which layer the user is interested in.

Even when the same amount of data is transmitted, depending on the network configuration and security settings, the operation may be slowed or transmission may be rejected under certain conditions (e.g., blocking due to security settings, delay due to load balancing characteristics) , QoS settings, etc.). For various situations of such a network, the present invention can measure the performance of different layers in the same network at the same time by using a scripting engine.

For example, if a script for L4 test and a script for HTTP test exist at the same time, it can be considered that the script for L4 test operates normally but the script for HTTP test fails. In this case, the operation at the L4 level and the operation at the L7 level can be measured together under the same conditions in the same network.

Therefore, which layer to measure can be applied differently depending on the contents of the developed script, and by applying the corresponding script for each layer, it is possible to measure the performance and abnormal behavior of various layers ranging from L3 to L7 layers.

6 is a conceptual diagram illustrating a test scenario application of the present invention.

In the case of SBC (single-board computer, single board computer) hardware such as Raspberry Pi, if the operating system layer, the network socket layer of TCP or UDP, and the scripting engine for flow control are loaded, the script is tested It is implemented in various test scenarios such as Scenario 1, Test Scenario 2, and Test Scenario 3 to perform performance analysis on multiple layers of the network.

7 is a flowchart illustrating a multi-layer performance analysis method of an arbitrary section in a network through a socket control interface according to an embodiment of the present invention.

First, in the socket interface step ST1 , the socket interface unit 110 of the multi-layer performance analysis system 100 interfaces with a TCP or UDP socket of the network to start communication with the network.

Also, in the script initialization step ST2, initialization is performed on a script for performing network performance analysis after the socket interface step.

In the script and background processing steps (ST3, ST4), the script flow processing unit 140 performs flow processing on the script initialized in the script initialization step, and when the script includes TCP, a TCP handshake is performed, Transmission and reception processing for TCP or UDP data to the network is performed, and the background processing unit 120 determines whether communication is successful according to data communication with the network by a script, and performs multi-layer performance analysis on the network, Output the test result of the performance analysis for the network.

8 is a detailed flowchart of FIG. 7 .

So, in the TCP handshake step, if the socket connected by the socket interface unit 110 is a TCP socket (ST11), the script flow processing unit 140 selects a TCP socket (ST12) and processes to perform a TCP handshake (ST13). ). Then, the background processing unit 120 attempts a TCP handshake (ST14). Therefore, the background processing unit 120 determines whether the TCP handshake succeeds (ST15) or fails (ST16). At this time, the background processing unit 120 measures the time required for the TCP handshake. Then, when the background processing unit 120 determines the TCP handshake success, the script flow processing unit 140 confirms the TCP handshake success (ST17).

After the socket is not a TCP socket or the TCP handshake step is completed, the script flow processing unit 140 transmits TCP or UDP data to the network (ST18). Then, the background processing unit 120 attempts to transmit data to the network (ST19). Then, the transmission success (ST20) or transmission failure (ST21) determination is performed according to the data transmission attempt. Also, if transmission is successful, data is received from the network (ST22). If data is not received from the network, it is determined as reception failure (ST23). At this time, the background processing unit 120 measures the time between transmission and reception of data to calculate the RTT, extracts the BPS by analyzing the total amount of data as the transmission/reception time, and determines whether the failure cause is a timeout or a socket error, It analyzes the layer and network section where the problem occurs among each of the L2 header, L3 header, L4 header, and payload, which are multi-layers of the network, and analyzes the cause of the problem using RTT and BPS and timeout information and provides it.

Then, when the background processing unit 120 receives data from the network, the script flow processing unit 140 performs processing (eg: data transmission, connection type, etc.) on the received data (ST24). When the data transmission and reception to the network are completed and the connection to the network is terminated (ST25), the script flow processing unit 140 performs a test success declaration (ST26).

Here, the cause of the failure due to a network failure can be analyzed as either a timeout or a socket error.

Also, when the socket is UDP or raw IP, the TCP handshake step (ST11 to ST17) is omitted.

FIG. 9 is a flowchart showing processing when the script in FIG. 7 is a TCP fast reconnection script.

In the step of performing TCP fast reconnection (ST31 ~ ST35), if the script is TCP fast reconnection, it performs a TCP handshake to the specified server to generate a TCP handshake event, and disconnects the connection when connected to the server multiple times (ex: 10 times) is repeated.

And in the determination step ST36, when the number of repetitions of multiple times is terminated in the step of performing TCP fast reconnection, if a case in which a connection cannot be established occurs in the middle of the number of repetitions, it is determined as a failure, and when all connections are made in the number of repetitions of multiple times, it is determined as success do.

FIG. 10 is a flowchart showing processing when the script in FIG. 7 is an HTTP HEAD script.

In the HTTP HEAD execution steps (ST41 to ST44), if the script is an HTTP HEAD script, a TCP handshake is performed to generate a TCP handshake event, and an HTTP HEAD request is sent when connected to the server.

In the determination step (ST45 ~ ST48), when the server sends data in the HTTP HEAD execution phase, a sub-response event is generated and the data transmission and reception status and RTT are checked. If there is no response for a while, a timeout event is generated.

FIG. 11 is a flowchart showing processing when the script in FIG. 7 is a UDP RTT script.

In the UDP RTT processing steps ST51 and ST52, if the script is a UDP RTT script, data is sent to the designated server.

In the determination steps ST53 and ST54, if a server response event occurs after the UDP RTT processing step, success processing is performed, and if a server response event does not occur, failure processing is performed.

FIG. 12 is a flowchart showing processing in the case where the script in FIG. 7 is an SMTP EHLO script.

In the SMTP EHLO processing steps (ST61 to ST64), if the script is an SMTP EHLO script, a TCP handshake is performed to generate a TCP handshake event, and when connected to the server, an EHLO message is transmitted.

In the judgment step (ST65 ~ ST69), if a message indicating that the domain service is ready from the server is received in the SMTP EHLO processing phase, the processing is completed. Handle errors and failures.

Table 1 below compares the present invention with the prior art 1 and the prior art 2.

division the present invention prior art 1 prior art 2 network to be verified TCP/IP TCP/IP TCP/IP startup hardware Commercial hardware based on Windows or Linux Self-developed GBIC Switch/Router Special Features mode of use It can be installed on PC, server, SBC (small computer such as Raspberry Pi), smartphone, tablet, etc.
Depending on the installed hardware, various connections to Ethernet, WiFi, and mobile communication networks (LTE, 5G, etc.) are possible. Limited to switches that can use GBIC.
Not available if GBIC is not compatible with the switch. Enable feature on switch (unavailable if switch doesn't have feature) Supported protocols ICMP, TCP, UDP and any L7 protocol operating as TCP or UDP Specified protocol or convention (TWAMP/UDP centric) Specified protocol or convention (TWAMP/UDP centric) test scenario Various types of scenarios can be applied, such as repeating TCP handshake, sending a specific style of payload, and trying to overload the line Only RTT-centric specified scenarios are available Only RTT-centric specified scenarios are available Applicable environment Freely configurable server-network specific section, partial network section, client-network section, etc. dependent on switch dependent on switch

As shown in Table 1, in the present invention, the verification target network is TCP/IP, which is the same as in the prior art.

On the other hand, the startup hardware of the present invention is commercial hardware based on Windows or Linux, and the range of startup hardware is wider than that of the prior art.

In terms of use, the present invention can be installed in a PC, a server, an SBC (small computer such as a Raspberry Pi), a smartphone, a tablet, and the like. Also, depending on the installed hardware, it can be connected to Ethernet, WiFi, mobile communication network (LTE, 5G, etc.) in various ways. Therefore, the present invention is capable of various connections, compared to the prior art being limited to a network switch.

As for supportable protocols, the present invention is applicable to ICMP (Internet Control Message Protocol), TCP, UDP and any L7 protocol operating as TCP or UDP. In contrast, in the present invention, supportable protocols are more diverse.

Looking at the test scenario, the present invention can be applied to various types of scenarios such as repeating TCP handshake, transmitting a specific style of payload, and attempting to overload a line. Therefore, while the prior art can use only RTT-centered designated scenarios, the present invention can apply various test scenarios for diagnosing the state of a network.

Looking at the applicable environment, the present invention can be freely configured such as a specific server-network section, a partial section of the entire network, and a client-network section. Therefore, compared to the prior art depending on the switch, the present invention has the advantage of being freely configurable in various sections for diagnosing the network state.

As such, the present invention performs multi-layer performance analysis on the network through a socket (TCP, UDP) control interface connected to the network to analyze where there is a problem among all equipment and sections involved in communication from the client to the server. .

Although the present invention has been described in more detail with reference to examples above, the present invention is not necessarily limited to these examples, and various modifications may be made within the scope without departing from the technical spirit of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical spirit of the present invention, but to explain, and the scope of the technical spirit of the present invention is not limited by these embodiments. The protection scope of the present invention should be construed by the claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

100: multi-layer performance analysis system
110: socket interface unit
120: background processing unit
130: script initialization unit
140: script flow processing unit
150: utility processing unit

Claims (8)

a socket interface unit 110 for allowing the multi-layer performance analysis system 100 to interface with a TCP or UDP socket of a network;
a background processing unit 120 communicating with the network through the socket interface unit 110, determining whether communication is successful according to data communication with the network by a script, and performing multi-layer performance analysis on the network;
a script initialization unit 130 that initializes a script for performing network performance analysis through the socket interface unit 110;
Flow processing through the background processing unit 120 is performed on the script initialized by the script initialization unit 130, and a TCP handshake is performed if the script includes TCP, and the TCP or UDP data is processed. Script flow processing unit 140 for performing transmission and reception processing to the network; is configured to include,
The background processing unit 120 measures the time required for the TCP handshake when the script flow processing unit 140 performs the TCP handshake, and measures the time between data transmission and reception when transmitting and receiving TCP or UDP data to perform RTT. It calculates and analyzes the total amount of data by transmission/reception time to extract BPS to determine whether the cause of failure is a timeout or socket error, A multi-layer performance analysis system of an arbitrary section in the network through a socket control interface, characterized in that it analyzes the generated layer and network section, and analyzes the cause of the problem using RTT and BPS and timeout information.
delete a socket interface step (ST1) of starting communication with a network by performing an interface with a TCP or UDP socket of the network in the socket interface unit 110 of the multi-layer performance analysis system 100;
a script initialization step (ST2) of performing initialization on a script for performing network performance analysis after the socket interface step;
The script flow processing unit 140 performs flow processing on the script initialized in the script initialization step, and when the script includes TCP, a TCP handshake is performed, and TCP or UDP data is transmitted to the network and reception processing, and the background processing unit 120 determines whether communication is successful according to data communication with the network by the script, performs multi-layer performance analysis on the network, and outputs the test result of the performance analysis on the network Script and background processing steps (ST3, ST4);
The script and background processing step,
If the socket accessed by the socket interface unit 110 is a TCP socket, the script flow processing unit 140 processes to perform the TCP handshake, and the background processing unit 120 measures the required time of the TCP handshake to perform the TCP handshake. a TCP handshake step (ST11 to ST17) for diagnosing success or failure;
If the socket is not a TCP socket or after the TCP handshake step, the script flow processing unit 140 processes a script for data transmission of TCP or UDP, and the background processing unit 120 performs an operation between transmission and reception of data. Time is measured to calculate RTT, and BPS is extracted by analyzing the total amount of data as transmission/reception time to determine whether the cause of failure is a timeout or socket error. a data transmission/reception processing step (ST18 to ST26) of analyzing a layer and a network section in which a problem occurs in each payload, and analyzing the cause of the problem using RTT and BPS and timeout information;
A multi-layer performance analysis method of an arbitrary section within a network through a socket control interface, characterized in that it is performed, including:
delete 4. The method according to claim 3,
The script and background processing step,
If the script is TCP fast reconnection, a TCP fast reconnection performing step (ST31 ~ ST35) of performing a TCP handshake to a designated server to generate a TCP handshake event, and repeating the operation of disconnecting when connected to the server multiple times;
In the TCP fast reconnection performing step, when the number of repetitions of a plurality of times is terminated, a determination step of determining a failure if a connection cannot be made in the middle of the number of repetitions, and determining success if all connections are made in the number of repetitions of the plurality of repetitions (ST36) ;
A multi-layer performance analysis method of an arbitrary section within a network through a socket control interface, characterized in that it is performed, including:
4. The method according to claim 3,
The script and background processing step,
If the script is an HTTP HEAD script, performing a TCP handshake to generate a TCP handshake event, and sending an HTTP HEAD request when connected to a server (ST41 to ST44);
When the server sends data in the HTTP HEAD execution step, a sub response event is generated, data transmission and reception status and RTT are checked, and when the server does not respond for a certain period of time in the HTTP HEAD execution step, a timeout event is generated. step (ST45 to ST48);
A multi-layer performance analysis method of an arbitrary section within a network through a socket control interface, characterized in that it is performed, including:
4. The method according to claim 3,
The script and background processing step,
If the script is a UDP RTT script, the UDP RTT processing step (ST51, ST52) of sending data to a designated server;
a determination step (ST53, ST54) of success processing if a server response event occurs after the UDP RTT processing step, and failure processing if no server response event occurs;
A multi-layer performance analysis method of an arbitrary section within a network through a socket control interface, characterized in that it is performed, including:
4. The method according to claim 3,
The script and background processing step,
If the script is an SMTP EHLO script, the SMTP EHLO processing step (ST61 ~ ST64) of performing a TCP handshake to generate a TCP handshake event, and transmitting an EHLO message when connected to the server;
In the SMTP EHLO processing step, if a message indicating that the domain service is ready from the server is received, the processing is completed. step (ST65 to ST69);
A multi-layer performance analysis method of an arbitrary section in a network through a socket control interface, characterized in that it is performed including a.

Images