WO2009030130A1

WO2009030130A1 - A method and system for transmitting data

Info

Publication number: WO2009030130A1
Application number: PCT/CN2008/071577
Authority: WO
Inventors: Zhigang Ye
Original assignee: Shenzhen Coship Electronics Co., Ltd.
Priority date: 2007-09-07
Filing date: 2008-07-08
Publication date: 2009-03-12
Also published as: CN101202704B; CN101202704A

Abstract

A method and system for transmitting data are disclosed. The method includes the following steps of: sending a network connection request to a data receiving terminal; after the connection is successful and a notice slot of the pre-established socket is registered, judging whether it is successful to write data into the data receiving terminal through the socket or not, when it is successful reading the response package of the data receiving terminal, and when it is unsuccessful adding the socket into a work queue, and notifying the socket to write the data into the data receiving terminal when it is inquired that the socket is writable. In the embodiments of the invention, the state machine is built for the socket through general inquiring mechanism, and the socket performs the data circulation according to the state machine, and a notice mechanism is built for the socket to notice the state of data circulation of the socket in time and exactly, so the network protocol and the network connection are disposed effectively in the case of the large network subsequent quantity.

Description

Data transmission method and system

The present application claims priority to Chinese Patent Application No. 200710076929.2, entitled "A Data Transmission Method and System", filed on September 7, 2007, the entire contents of which is incorporated herein by reference. in.

Technical field

The invention belongs to the field of network communication, and in particular relates to a data transmission method and system.

Background technique

In the network server system, there are two models for the client's connection request: one is that the receiver uses the iterative server model to process the client's request in turn; the other is that the receiver uses the concurrent server model for each The client requests a process to process. The receiving end adopts the concurrent server model, and some sub-processes are pre-derived to process client requests; the receiving end adopts a concurrent server model, and one thread is generated for each client to process; the receiving end adopts a concurrent server model, and some threads are pre-derived for processing.

In the prior art, the receiving end generally adopts a concurrent server model, and some threads are pre-derived to process client requests. Whenever a client requests, the request is submitted to a thread pool until the request is processed.

The prior art does not divide or divide the execution of the intermediate state of the socket, the execution state of the protocol, and the execution state of the data, or introduces such a mechanism, and the socket does not adopt a notification mechanism or is imperfect, when a network event occurs. When the application layer is not notified in a timely and accurate manner.

Summary of the invention

The purpose of the embodiments of the present invention is to provide a data transmission method and system, which aims to solve the problem that the network data transmission in the prior art is large and the application layer cannot be accurately and timely notified when a network event occurs.

The embodiment of the present invention is implemented by the method for sending data, and the method includes the following steps:

Sending a network connection request to the data receiving end;

After the connection is successful and the notification slot is registered for the pre-established socket, it is judged whether the data is successfully written to the data receiving end by the socket, and when the data is successfully written, the response packet of the data receiving end is read; When the write data is unsuccessful, the socket is added to the work queue, and when the socket is queried, When writing, the socket is notified to write data to the data receiving end.

Another object of the embodiments of the present invention is to provide a method for receiving data, the method comprising the following steps:

When the connection request of the data sender is monitored through a pre-established listening socket, the listening socket reselects a new socket;

Determining whether the data is successfully read by the new socket, processing the data when the data is successful, and writing a response packet to the data sending end; when the reading data is unsuccessful, the new socket is Joining the work queue, and continuously detecting the status of the new socket, and notifying the new socket to read data when the new socket is readable.

Another object of the present invention is to provide a data sending system, where the system includes: a socket establishing module, configured to establish a socket;

a connection request sending module, configured to send a network connection request to the data receiving end;

Notifying a slot registration module, for registering a notification slot of the socket when the connection is successful; and

a socket write data judging processing module, configured to determine, after the notification slot registration module registers the notification slot of the socket, whether the data is successfully written to the data receiving end by the socket, when writing data If successful, the response packet of the data receiving end is read; when the writing data is unsuccessful, the socket is added to the working queue, and when the socket is readable, the socket is notified to the The data receiving end writes data.

Another object of the present invention is to provide a data receiving system, where the system includes: a listening socket establishment determining module, configured to establish a listening socket, and determine whether the socket monitoring is successful;

a connection request judging module, configured to determine, after the monitoring socket is successfully monitored, whether the listening socket listens to a connection request of the data receiving end;

a new socket selection module, configured to: when the connection request judging module listens to the connection request of the data sending end, the listening socket reselects a new socket;

a socket read data judging processing module, configured to judge whether the data is successfully read by the new socket, when the read data is successful, process the data, and write a response packet to the data sending end; When the data is unsuccessful, the new socket is added to the work queue, and the shape of the new socket is continuously detected. And, when the query to the new socket is readable, notifying the new socket to read data.

The embodiment of the present invention establishes a state machine for a socket through a general query mechanism, and the socket performs data flow according to the state machine, and establishes a notification mechanism for the socket, so as to timely and accurately notify the state of the socket data flow. In this way, network protocols and network connections are effectively handled in the case of a large amount of network concurrency.

DRAWINGS

1 is a flowchart of an implementation of a method for sending network data according to an embodiment of the present invention;

2 is a flowchart of implementing a response packet of a socket reading and receiving end according to an embodiment of the present invention; FIG. 3 is a flowchart for implementing detection of read network transmission traffic of a file according to an embodiment of the present invention; Flow chart for implementing the method for receiving network data;

FIG. 5 is a flowchart of implementing a socket write response packet according to an embodiment of the present invention;

FIG. 6 is a flowchart of a method for detecting write network traffic of a file according to an embodiment of the present invention; FIG. 7 is a structural diagram of a data transmission system according to an embodiment of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

In the embodiment of the present invention, the state of the socket is defined as follows:

Input and output interface io open: After a socket is established, its state becomes io open state; io listener: After a socket is successfully monitored, its state becomes io listener;

Io wait for the connection: the socket requests the state before the connection;

Io idle: input / output interface i / o is idle;

Io idle waiting: When the i/o read/write speed is too high, in order to limit the speed and not read and write data, the read/write speed can be read and written after the read/write speed is reduced;

Io waits for reading: i/o does not read the data temporarily or waits to read the other party after sending the data Data, or a state in which data is not read because of the speed at which data is restricted;

Io waiting to write: i/o failed to write data or to control the sending speed without writing data; io test: used to test the status of i/o;

Io waits for the shutdown: i/o is about to be closed;

Io error: the status of the error occurred in i/o;

Io is shutting down: i/o is performing the shutdown state;

Io closed: i/o has been closed;

Io is put into the release queue: In order to recycle the i/o, after it ends the operation, put it into the queue and wait for the state to be taken again.

The flow status of the protocol data is defined as follows:

Initialization: protocol initialization phase;

Read: The socket has read the network data;

Reading: The socket is reading network data;

Read data user waits: After reading data from the network, it is necessary to save the data to the buffer or write the file. This state is generally used to limit the speed. When the speed is greater than a certain threshold, the write file is waiting. State, until the speed drops and then write the file;

Socket read wait: socket does not read data temporarily, the socket in this state will join the work queue, when another thread queries the readable event of the socket, send a notification message to the socket, notify the socket to read Data

Write: socket has finished writing network data;

Writing: socket is writing network data;

Write data user wait: This state is to limit the speed. When writing data, firstly, the data should be fetched from the file or buffer. When the sending speed is too fast, in order to limit the speed, the user will not be able to temporarily obtain the data. Until the speed drops, take the data;

Socket write wait: This is generally caused by the socket write i / o blockage, the socket in this state should be added to the work area, another thread will query the socket, send a writable notification message when the socket can be written. Then the socket goes to write data again;

Processing: The protocol data analysis is completed;

Processing: Processing of protocol data is being analyzed; Processing wait: When a request data is submitted to a new thread for processing, the main thread returns to the processing wait state;

Error: Processing status when socket error occurs;

Ready to close: When the protocol data is completely processed, the state is set to be ready to be closed; Close: The state of the socket is ready to be closed after the protocol is closed. The steps are as follows:

In step S101, a socket is established, wherein the state of the socket is an open state, and the state of the data protocol is an initialization state.

In step S102, the sender sends a connection request to the receiver, and the state of the socket is waiting for the connection.

In step S103, it is judged whether the connection of step S102 is successful, if yes, step S105 is performed, otherwise step S104 is performed.

In step S104, the above socket is closed, and the program directly returns.

In step S105, the notification slot slot of the socket is registered.

In the embodiment of the present invention, there are two classes in the program, Isocket and IsocketSlot. The Isocket specifically encapsulates the socket operation, the IsocketSlot is specifically used to provide the notified function, the Isocket retains the IsocketSlot, and the IsocketSlot also retains the Isocket, in sending the request. At the time, if the socket connection is successful, then the corresponding IsocketSlot is associated with the Isocket, which is the registration process.

In step S106, protocol data is generated, and the protocol data is stored in a buffer, and the protocol data is prepared. At this time, the state of the protocol data is in a write state, wherein the protocol data includes a status line, a header, and a packet body.

In step S107, data is written to the receiving end through the socket.

In step S108, it is judged whether the socket write data is successful, if yes, step S109 is performed; otherwise, step S110 is performed. Among them, writing data on the network is written in blocks, for example, every 4K data is sent in one piece.

In step S109, the socket write data is completed, that is, the data file is sent, the protocol data state is the write data state, and then the socket reads the response of the receiver, and the state of the socket is Read.

In the embodiment of the present invention, after the socket reads the response of the protocol data, it indicates that the protocol data is sent, that is, the connection ends; if the read response is unsuccessful, the socket is added to the queue, and the queue is continuously queried for readability. Read the response when it is readable, then close the socket and the entire protocol interaction ends.

In step S110, the socket write data fails. At this time, the socket state is a socket error state, and the protocol data state is a socket write wait state, and the socket is added to a work queue.

In step S111, the new thread continuously queries the state of the socket in the work queue to determine whether the state of the socket becomes writable. If yes, step S112 is performed; otherwise, step S113 is performed.

In step S112, the sender sends a writable message to the socket, and returns to the execution step.

S108, in the embodiment of the present invention, the loop process is always present until the data file is sent.

In step S113, it waits until the socket is writable, and step S11 is executed again. In the embodiment of the present invention, the data transmission process is based on a Transmission Control Protocol (TCP) protocol, which is mainly a Hyper Text Transfer Protocol (HTTP), a real-time streaming protocol (Real Time). Streaming Protocol, RTSP) and custom protocols.

In the embodiment of the present invention, the socket is allocated to the work area, wherein the processing for the I/O is divided into a plurality of work areas, and each work area has a certain limit on the I/O processed, for example, each work area Only 1024 sockets can be processed at a time. Currently, the first workspace handles the listener and the rest of the I/O. If the number of sockets to be processed is large, the work area is increased, and the added work area is processed. Exit when finished; if the number of sockets is small, reduce the workspace. Each workspace is handled by one thread. Generally, the default number of queries per window system is 64. The default number of linux is 1024. Under Windows, each socket handles 130 sockets. The work area handles 1024 sockets, and the thread that handles each work area is always running, and each socket of the work area is processed cyclically. This adjustment makes the network concurrent processing capability strong, ensuring speed and efficiency. Among them, the socket is always set in the non-blocking mode.

As an embodiment of the present invention, there are two situations in which the socket reads the response of the receiving end, that is, the protocol interaction and the file transmission. In the embodiment of the present invention, the protocol interaction includes the request, the processing, and the response. These three steps can indicate the end of the protocol interaction process, and the file transfer process is a cyclic process. File transfer is done by blocking. The transfer of each file is a complete protocol interaction process. The detailed process description is given below:

In step S201, it is determined whether the response packet of the read receiving end is successful, if yes, step S202 is performed; otherwise, step S203 is performed.

In step S202, the response packet of the receiving end is read, and the protocol data state is the read state, and the response of the receiving end is processed at the same time.

In the embodiment of the present invention, the program is divided into an application layer and an underlying layer. After the bottom layer reads the response, the response is submitted to the application layer for processing, for example, registering a transmission mode, and the client sends a request to the server and the server gives the request. After the response, the client reads the response packet of the server, and then submits the response packet to the component that just registered the transmission mode. If the registration is successful, it does not need to be registered again. If the registration is unsuccessful, it will be continuously registered until it succeeds. So far, different response processing methods are different, business requirements are different, and some responses do not need to be processed, but as a protocol interaction process, the entire process is over.

After processing, the socket state is off, and the protocol data state is also off, and the entire protocol interaction process ends.

In step S203, the response packet of the receiving end is not read, the socket state changes to a socket error, and the protocol data state changes to a socket read wait. At this time, the socket is added to the work queue.

In step S204, the new thread continuously queries the status of the socket, that is, determines whether the socket is readable. If yes, step S205 is performed; otherwise, step S206 is performed.

In step S205, the socket is notified to read the response packet, and the process returns to step S201.

In step S206, the query continues until the socket is readable.

If the above network connection is a normal protocol interaction, then the socket only reads the response packet of the receiver once.

If the above connection is a file transfer, the response packet is read multiple times between the sender and the receiver, that is, cyclically read.

In the embodiment of the present invention, in the case that the network connection is a file transmission, as shown in FIG. 3, whether the traffic of the read network exceeds a set value is detected, and the detailed steps are as follows:

In step S301, it is determined whether the read network transmission traffic exceeds a set value, and if yes, the execution step S302. Otherwise, in the embodiment of the present invention, the determining is to determine whether the file traffic transmitted in the current network exceeds a preset value, because the file transmission is transmitted by using a block, when the block size exceeds a preset value. , that is, the traffic exceeds the predetermined network transmission.

In step S302, a write interrupt is returned during the file writing process. At this time, the protocol data state changes to read data, the user waits, and the socket state temporarily changes to the idle wait state.

In step S303, the socket is added to the work queue.

In step S304, the new thread continuously queries the state of the socket in the work queue, that is, determines whether the socket is readable. If yes, step S305 is performed, otherwise the query is continued.

In step S305, the socket is notified to read the file data.

In step S306, in the process of continuously reading the file data by the socket, it is judged whether the read data is successful, and if yes, the reading is continued, otherwise step S308 is performed.

In step S307, the socket state becomes an error state, and the protocol data state changes to a socket read wait, and the socket is added to the work queue.

In step S308, another new thread continuously queries the status of the socket, that is, whether the socket is readable. If yes, step S309 is performed, otherwise the query is continued.

In step S309, the socket is notified to read the data, and so on until the file is read. Through the above implementation process, network traffic is effectively controlled, and file data transmission is realized. FIG. 4 is a flowchart showing an implementation process of a method for receiving network data according to an embodiment of the present invention, and the detailed steps are as follows:

In step S401, a listening socket is established.

In step S402, it is determined whether the socket monitoring is successful, that is, whether there is a connection request of an IP address and a port, if yes, step S404 is performed; otherwise, step S403 is performed.

In step S403, the socket is closed and returned.

In step S404, the listening socket is added to the working queue, and the state of the socket is the listening state.

In step S405, the new thread continuously queries the listening socket in the work area.

In step S406, according to the new thread continuously querying, it is determined whether to listen to the connection request of the sender, if yes, step S407 is performed, otherwise, the monitor socket is closed.

In step S407, the listening socket re-accepts a new socket. In the embodiment of the present invention, the intercepted connection is submitted to the linear queue, and the receiving end specifically opens up a thread to process the connected monitored connection.

In step S408, it is judged whether the new socket read data of the re-acceptance is successful, and the protocol data state is in the read state, if yes, step S413 is performed, otherwise step S409 is performed.

In step S409, the new socket reads the data unsuccessfully. At this time, the socket state changes to a socket error, and the protocol data state changes to a socket read error, indicating that the data cannot be read temporarily, and the socket force is injected into the work queue. .

In step S410, the new thread continuously queries the status of the new socket.

In step S411, it is judged whether the state of the new socket becomes readable, if yes, step S412 is performed, otherwise the query is continued, and the step is returned.

In step S412, the receiving end sends a readable notification message to the new socket, and returns to step S408.

In step S413, after the data is read, the protocol data state changes to the read state, and the analysis processing protocol data is started. At this time, the protocol data state changes to the processing state.

In step S414, the receiving end writes the response data, and the socket status side is writing.

As another embodiment of the present invention, the receiving end write response data includes two cases, that is, normal protocol interaction and file transmission. In the embodiment of the present invention, the protocol interaction includes request, processing, and response, and the three steps can be represented. The protocol interaction process ends, and the file transfer process is a cyclic process. File transfer is done by blocking. The transfer of each file is a complete protocol interaction process. A detailed description is given below:

In step S501, it is determined whether the write response packet is successful, if yes, step S502 is performed, otherwise step S503 is performed.

In step S502, the response packet is successfully written, and the protocol data state is in the write state, and the socket is closed. After processing, the socket status is off, and the protocol data status is also off. The protocol interaction process ends. If it is a file transfer, the socket can only be closed after all the block file transfers are completed.

In step S503, if the response to the packet write fails, the socket state changes to a socket error, and the protocol data state changes to a socket write wait. At this time, the socket is added to the work queue.

In step S504, the new thread continuously queries the state of the socket. In step S505, it is determined whether the socket is writable, if yes, step S506 is performed, otherwise step S507 is performed.

In step S506, the socket is notified to write the response packet, and the process returns to step S501.

In step S507, the query continues until the socket is writable.

If the above network connection is a normal protocol interaction, then the response packet is written once.

If the above connection is a file transmission, the receiving end writes a response packet to the data sending end multiple times, and each time the file is sent, the file is written in response, wherein the detailed flow of detecting whether the network traffic exceeds the set value is as follows: Said:

In step S601, it is judged whether the flow rate of the network of the file data exceeds the set value, if yes, step S602 is performed, otherwise, it ends.

In step S602, a read interrupt is returned during the process of reading the file. At this time, the protocol data state changes to the write data user waits, and the socket state temporarily becomes the idle wait state.

In step S603, the socket is added to the work queue.

In step S604, the new thread continuously queries the status of the socket in the work queue, that is, determines whether the socket is writable, and if yes, step S605 is performed, otherwise the query is continued.

In step S605, the socket is notified to write the file data.

In step S606, in the process of continuously writing the file data by the socket, it is judged whether the write data is successful, and if yes, the reading is continued, otherwise step S607 is performed.

In step S607, the socket state becomes an error state, and the protocol data state changes to a socket write wait, and the socket is added to the work queue.

In step S608, another new thread continuously queries the status of the socket, that is, whether the socket is writable, and if yes, step S609 is performed, otherwise the query is continued.

In step S609, the socket is notified to write data, and so on until the file is read. FIG. 7 is a structural diagram of a data transmission system according to an embodiment of the present invention. For convenience of description, only parts related to the embodiment of the present invention are shown, wherein the data transmission system 1 and the data receiving system 2 are placed in a software unit of the terminal. , hardware unit or hardware and software unit.

The data transmission system 1 includes a socket establishment module 11, a connection request transmission module 12, a notification slot registration module 13, and a socket write data judgment processing module 14, wherein:

The socket establishing module 11 establishes a socket; the connection request sending module 12 sends a network connection request; When it is determined that the connection is successful, the slot registration module 13 is notified to register the notification slot of the socket; the socket write data judgment processing module 14 determines whether the data is successfully written by the socket, and when the data is successfully written, Reading the response packet of the data receiving end; when the writing data is unsuccessful, the socket is added to the working queue, and the state of the socket is continuously detected, and when the socket is writable, the socket is notified to be writable data.

As an embodiment of the present invention, the socket write data processing judging module 14 further includes a read response packet judging module 141, a read response packet processing module 142, and a read response packet judging processing module 143, wherein:

The read response packet judgment module 141 determines whether the response packet of the read receiving end is successful; when the read response packet of the receiving end succeeds, the read response packet processing module 142 processes the response packet; when the response packet of the receiving end is unsuccessful, The read response packet judgment processing module 143 adds the socket to the work queue, and continuously detects the state of the socket. When the socket is readable, the response packet of the data receiving end is read.

In the embodiment of the present invention, the socket write data judgment processing module 14 further includes a read network traffic judgment module 144 and a read traffic processing module 145. The read network traffic judgment module 144 determines whether the network transmission traffic of the file data exceeds a preset. Value; when the network transmission traffic of the file data exceeds a preset value, the read traffic processing module 145 returns a write interrupt, adds the socket to the work queue, and determines the state of the query socket. When the socket is readable, the socket is notified. Read file data.

The data receiving system 2 includes a listening socket establishment determining module 21, a connection request judging module 22, a new socket selecting module 23, and a socket reading data judging processing module 24, wherein:

The listening socket establishment determining module 21 establishes a listening socket and determines whether the socket monitoring is successful; the connection request determining module 22 determines whether the listening socket listens to the network connection request; when the connection is successful, the new socket selecting module 23 monitors The socket will re-accept - a new socket; the socket read data judgment processing module 24 determines whether the data is successfully read by the new socket, and when the data is successfully read, the request packet of the data sender is read; When the data is unsuccessful, the new socket is added to the work queue, and the state of the new socket is continuously detected. When the new socket is readable, the new socket readable data is notified.

As still another embodiment of the present invention, the socket read data judgment processing module 24 includes a write response packet judgment module 241, a write response packet processing module 242, and a write response packet judgment processing module 243, wherein:

The write response packet judgment module 241 determines whether the write response packet is successful; when the write response packet succeeds, the write back The packet processing module 242 closes the socket; the write response packet judgment processing module 243 adds the new socket to the work queue when the write response packet is unsuccessful, and continuously detects the state of the new socket, when the new set When the word is writable, write the response packet.

In the embodiment of the present invention, the socket read data judging processing module 24 further includes a write network traffic judging module 244 and a write traffic processing module 245, where:

The write network traffic judgment module 244 determines whether the network transmission traffic of the file data exceeds a preset value; when the network transmission traffic of the file data exceeds a preset value, the write traffic processing module returns a read interrupt, and adds the socket to the work. In the queue, and determine the state of the socket, when the socket is writable, the socket is notified to send the file data.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection of the present invention. Within the scope.

Claims

Rights request

A method for transmitting data, characterized in that the method comprises the steps of: transmitting a network connection request to a data receiving end;

After the connection is successful and the notification slot is registered for the pre-established socket, it is judged whether the data is successfully written to the data receiving end by the socket, and when the data is successfully written, the response packet of the data receiving end is read; When the write data is unsuccessful, the socket is added to the work queue, and when the socket is queried, the socket is notified to write data to the data receiving end.

2. The method of transmitting data according to claim 1, wherein the reading the response packet of the data receiving end further comprises the following steps:

Determining whether the response packet of the read data receiving end is successful;

Processing the response packet when reading the response packet of the data receiving end is successful;

When the response packet of the data receiving end is unsuccessful, the socket is added to the working queue, and when the socket is readable, the response packet of the data receiving end is read.

The method for transmitting data according to claim 1 or 2, wherein, when the network connection request is a file transfer request, the response packet is specifically file data, and the response packet of the data receiving end is read. It also includes the following steps:

Determining whether the network transmission traffic of the file data exceeds a preset value;

When the network transmission traffic of the file data exceeds a preset value, returning a write interrupt, and adding the socket to the work queue;

Determining the status of the socket, and notifying the socket to read the file data when the socket is readable.

A method for receiving data, characterized in that the method comprises the following steps: when the connection request of the data transmitting end is monitored through a pre-established listening socket, the listening socket reselects a new set. Socket

The data receiving method according to claim 4, wherein the transmitting to the data The write-response package further includes the following steps:

Determining whether the response packet is successfully written to the data sender;

When the response packet is successfully written to the data transmitting end, the new socket is closed;

When the response packet is unsuccessful to the data sending end, the new socket is added to the working queue, and when the new socket is queried, the response packet is written to the data sending end.

The method for receiving data according to claim 4 or 5, wherein, when the network connection is file transmission, the response packet is specifically file data, and the writing of the response packet to the data receiving end further includes The following steps:

Returning a read interrupt when the network transmission traffic of the file data exceeds a preset value, and adding the new socket to the work queue;

Determining the status of the new socket, and notifying the new socket to read the file data when the new socket is readable.

7. A data transmission system, wherein the system comprises:

a socket building module for establishing a socket;

The data transmission system according to claim 7, wherein the socket write data judgment processing module further comprises:

a read response packet determining module, configured to determine whether the response packet of the read data receiving end is successful; and a read response packet processing module, configured to process the response packet when the response packet of the data receiving end is successful;

The read response packet judgment processing module is configured to: when the response packet of the data receiving end is read, the response packet is unsuccessful The socket is added to the work queue, and when the socket is readable, the response packet of the data receiving end is read.

The data transmission system according to claim 7 or 8, wherein the socket write data judgment processing module further comprises:

The network transmission traffic judging module is configured to: when the response packet is specifically file data, determine whether the network transmission traffic of the file data exceeds a preset value;

The read traffic processing module is configured to: when the network transmission traffic of the file data exceeds a preset value, return a write interrupt, add the socket to the work queue, and determine the state of the socket, When the socket is readable, the socket is notified to read the file data.

10. A data receiving system, the system comprising:

a monitoring socket establishment determining module, configured to establish a listening socket, and determine whether the socket monitoring is successful;

a socket read data judging processing module, configured to judge whether the data is successfully read by the new socket, when the read data is successful, process the data, and write a response packet to the data sending end; When the data is unsuccessful, the new socket is added to the work queue, and the state of the new socket is continuously detected. When the new socket is queried, the new socket read data is notified. .

The data receiving system according to claim 10, wherein the socket read data judgment processing module further comprises:

a response packet judgment module, configured to determine whether the response packet is successfully written to the data sending end; and a write response packet processing module, configured to close the new socket when the response packet is successfully written to the data sending end;

a write response packet judgment processing module, configured to add the new socket to the work queue when the write response packet to the data sender is unsuccessful, and when the query is that the new socket is writable, The data sender writes a response packet.

The data receiving system according to claim 10 or 11, wherein said socket The read data judgment processing module further includes:

Writing a network transmission traffic judging module, configured to determine whether the network transmission traffic of the file data exceeds a preset value when the response packet is specifically file data;

a write traffic processing module, configured to: when the network transmission traffic of the file data exceeds a preset value, return a read interrupt, add the new socket to the work queue, and determine the new socket a state, when the new socket is readable, notifying the new socket to read the file data.