TCP (Transmission Control Protocol) communication connection management method, TCP communication connection management device and server

Abstract

The invention relates to the field of new energy vehicles, and provides a TCP communication connection management method and device and a server. The method is applied to a server socket monitoring thread, and comprises the following steps: collecting and recording first TCP communication connection information when a server establishes TCP communication connection with a plurality of clients; acquiring second TCP communication connection information according to a preset monitoring period; comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of which the TCP communication connection is to be closed; and executing the connection closing instruction, and closing the TCP communication connection between the server and the target client. According to the method and the device, resource waste caused by a large number of CLOSEWAIT states of the server in a short time or downtime and even system crash caused by too heavy load can be effectively prevented.

Description

Technical Field

[0001] The present application relates to the field of new energy vehicles, and in particular to a TCP communication connection management method, device and server. Background Art

[0002] In the scenario of OTA (Over the Air Technology) parallel upgrading and flashing multiple ECUs (Electronic Control Units), multiple clients need to be created for the multiple ECUs to be upgraded (one client is created for each ECU), and each client communicates with a server and transmits the corresponding data of the upgraded ECU to the server. The more clients there are, the more data the client transmits to the server, and the more data the server needs to forward, which easily leads to the server being too busy due to too much data to be forwarded, and thus unable to timely process the connection shutdown request (connection release request) of the client that has completed the data transmission task and actively closed the communication connection. When the connection shutdown requests that are not processed in time continue to accumulate, the server will appear in a large number of "CLOSE_WAIT" states in a very short time. Excessive "CLOSE_WAIT" will cause the occupation of file descriptors, memory resources, CPU resources and thread resources, etc. When the CPU resources and memory are exhausted, it will cause downtime or restart, or even cause system crash, resulting in the failure of ECU upgrade and flashing, greatly reducing the performance of upgrade and flashing.

[0003] Therefore, it is urgent to provide a method to solve the problem of how to promptly handle the client's connection shutdown request, prevent the server from appearing in a large number of "CLOSE_WAIT" states in a short period of time, save CPU resources and memory resources, and ensure the success rate and performance of ECU upgrade flashing. Summary of the invention

[0004] In view of this, the embodiments of the present application provide a TCP communication connection management method, device and server to solve the problem of how to promptly process the client's connection shutdown request, prevent the server from appearing in a large number of "CLOSE_WAIT" states in a short period of time, save CPU resources and memory resources, and ensure the success rate and performance of ECU upgrade flashing.

[0005] In a first aspect of an embodiment of the present application, a TCP communication connection management method is provided, which is applied to a server socket monitoring thread, where the server socket monitoring thread is deployed on the server; the method comprises the following steps:

[0006] Collect and record first TCP communication connection information when the server establishes a TCP communication connection with multiple clients, the first TCP communication connection information including a client connection identifier corresponding to each client and a first TCP communication connection state;

[0007] According to a preset monitoring cycle, second TCP communication connection information is obtained, where the second TCP communication connection information includes a client identifier corresponding to each client and a second TCP communication connection state; the client connection identifier is associated with the client identifier;

[0008] Compare the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed;

[0009] Execute the connection close instruction to close the TCP communication connection between the server and the target client.

[0010] A second aspect of an embodiment of the present application provides a TCP communication connection management device, including:

[0011] A collection and recording module is configured to collect and record first TCP communication connection information when the server establishes a TCP communication connection with multiple clients, the first TCP communication connection information including a client connection identifier corresponding to each client and a first TCP communication connection state;

[0012] The monitoring acquisition module is configured to acquire the second TCP communication connection information according to a preset monitoring period, wherein the second TCP communication connection information includes a client identifier corresponding to each client and a second TCP communication connection state; the client connection identifier is associated with the client identifier;

[0013] A comparison module is configured to compare the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed;

[0014] The closing module is configured to execute a connection closing instruction to close the TCP communication connection between the server and the target client.

[0015] A third aspect of an embodiment of the present application provides a server, comprising the TCP communication connection management device of the second aspect.

[0016] According to a fourth aspect of an embodiment of the present application, a readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.

[0017] Compared with the prior art, the beneficial effects of the embodiment of the present application include at least: collecting and recording the first TCP communication connection information when the server and multiple clients establish a TCP communication connection through the server socket monitoring thread deployed on the server, and obtaining the second TCP communication connection information according to the preset monitoring cycle; then, comparing the first TCP communication connection information with the second TCP communication connection information to determine the target client of the TCP communication connection to be closed, and then executing the connection closing instruction to close the TCP communication connection between the server and the target client. In this way, the client's connection shutdown request can be processed in time, preventing the server from appearing in large quantities in a short period of time in the "CLOSE_WAIT" state, causing resource waste or downtime due to heavy load, or even system crash, thereby greatly saving CPU resources and memory resources, and ensuring the success rate and performance of ECU upgrade flashing. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 It is a schematic diagram of an application scenario of an embodiment of the present application;

[0020] Figure 2 This is a schematic diagram of a data communication transmission method in the TCP communication connection management method provided in an embodiment of the present application;

[0021] Figure 3 This is a schematic diagram of a message conversion method in the TCP communication connection management method provided in an embodiment of the present application;

[0022] Figure 4 This is a schematic diagram of a process for disconnecting a TCP communication connection between a client and a server provided in an embodiment of the present application;

[0023] Figure 5 It is a flowchart of a TCP communication connection management method provided in an embodiment of the present application;

[0024] Figure 6 This is a schematic diagram of a communication method between a server and a client in a TCP communication connection management method provided in an embodiment of the present application;

[0025] Figure 7 This is a schematic diagram of the connection relationship between the relevant functional modules of the server and the data sending center provided in one embodiment of the present application;

[0026] Figure 8 It is a structural diagram of a TCP communication connection management device provided in an embodiment of the present application;

[0027] Fig. 9 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0029] A TCP communication connection management method and device according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0030] Figure 1 It is a scenario diagram of an application scenario of an embodiment of the present application. The application scenario may include an OTA cloud platform 101, a data sending center 102 and a server 103. The data sending center 102 may be an intelligent cockpit controller (Cockpit Domain Controller, referred to as "CDC"), or it may be a vehicle-mounted TBOX (or vehicle-mounted VBOX). When the ECU component to be upgraded and flashed is an ECU component that does not support Ethernet (ETH), the server 103 is a vehicle gateway (VGW). When the ECU component to be upgraded and flashed is an ECU component to be upgraded and flashed that supports Ethernet, the server 103 is the ECU component to be upgraded and flashed. One or more ECU components can be mounted under the vehicle gateway (VGW). The OTA cloud platform 101 can be connected to the data sending center 102 through a 4G / 5G network; the data sending center 102 can be connected to the server 103 through Ethernet (ETH). The vehicle gateway (VGW) is connected to each ECU component that can be mounted thereunder through a CAN (Controller Area Network) bus or Ethernet (ETH).

[0031] The server 103 is deployed with a server socket monitoring thread (or server SOCKET monitoring program) and an OTA upgrade agent (abbreviated as "UA"). Each ECU carries an OTA upgrade slave controller (abbreviated as "US").

[0032] One or more clients can be created and deployed in the data sending center 102, wherein the number of clients can be determined according to the number of ECU components that need to be upgraded and flashed in parallel. Specifically, the number of clients deployed in the data sending center 102 is the same as the number of ECU components that need to be upgraded and flashed in parallel. One client corresponds to one ECU component that is upgraded and flashed. For example, assuming that the ECU components that are upgraded and flashed are ECU2-1, ECU2-2, and ECU2-n, then client 2-1, client 2-2, and client 2-n corresponding to ECU2-1, ECU2-2, and ECU2-n, respectively, can be deployed in the data sending center 102.

[0033] In the first case, see Figure 1 , Figure 2 When the ECU components that need to be upgraded and flashed in parallel are all ECU components that support Ethernet (for example, ECU1-2, ECU1-n), the data sending center 102 can deploy clients (socket clients) corresponding to each ECU component (such as ECU1-2, ECU1-n). Each client performs link layer (i.e., MAC layer) transparent transmission through the vehicle gateway (VGW) and establishes a TCP communication connection with the corresponding ECU component (as a server (socket server)), and uses the DOIP protocol for data communication transmission and upgrade flashing.

[0034] In the second case, please refer to Figure 1 , Figure 2 When the ECUs that need to be flashed in parallel are all ECUs that do not support Ethernet (for example, ECU2-1...ECU2-n), the data transmission center 102 can deploy clients corresponding to each ECU, and each client establishes a TCP communication connection with the vehicle gateway (as the server). The OTA upgrade agent (UA) parses the ECU target address (TA) of the message and converts it into a UDS message through the ETH message format (such as Figure 3 As shown), the message is forwarded to the ECU to be upgraded and flashed for data communication and upgrade and flashing.

[0035] For the third case, see Figure 1 , Figure 2, when the ECUs that need to be flashed in parallel include ECUs that support Ethernet and ECUs that do not support Ethernet (for example, ECU1-2, ECU1-n, ECU2-1, ECU2-n), the client corresponding to each ECU can be deployed in the data transmission center 102. For ECUs that support Ethernet (such as ECU1-2, ECU1-n), their corresponding clients can perform link layer (i.e., MAC layer) transparent transmission through the vehicle gateway and establish a TCP communication connection with the corresponding ECU (as the server), and use the DOIP protocol for data communication transmission and upgrade flashing. For ECUs that do not support Ethernet (such as ECU2-1, ECU2-n), their corresponding clients can establish a TCP communication connection with the vehicle gateway (as the server), and the OTA upgrade agent (UA) parses the ECU target address (TA) of the message, converts the UDS message through the ETH message format, and forwards the message to the ECU to be upgraded and flashed for data communication and upgrade flashing.

[0036] It should be noted that the specific types, quantities and combinations of the OTA cloud platform 101, the data sending center 102 and the server 103 can be adjusted according to the actual needs of the application scenario, and the embodiments of the present application do not limit this.

[0037] Figure 4 This is a schematic diagram of a process for disconnecting a TCP communication connection between a client and a server provided in an embodiment of the present application. Figure 4 The release of a TCP communication connection must be actively released by one party and passively released by the other party, and usually requires four handshakes. Figure 4 The process of the client (SOCKET CLIENT) actively initiating the release (disconnection) of the TCP communication connection is shown. Before the client actively releases the TCP communication connection with the server (SOCKET SERVER) by waving, the ESTABLISHED phase is ended, and then the "four waves" are started.

[0038] 1) If the client wants to release the TCP communication connection with the server, it can send a TCP message to the server, where the mark bit of the TCP message is FIN, indicating "request to release the connection"; then the client enters the FIN_WAIT1 stage, that is, the half-closed stage, and stops sending data from the client to the server, but the client can still receive data transmitted from the server. It is worth noting that what is not sent here is the data transmitted during the normal connection (non-confirmation message), not all data, so the client can still send an ACK confirmation message.

[0039] 2) After the server receives the TCP message sent from the client, it confirms that the client wants to release the connection. Then the server ends the ESTABLISHED phase, enters the CLOSE_WAIT phase (semi-closed state), and returns a TCP message, in which the mark bit of the TCP message is ACK, indicating "received the request to release the connection sent by the client". After the client receives the TCP message sent from the server, it confirms that the server has received the request to release the connection (disconnect request) sent by it. Then the client ends the FIN_WAIT1 phase and enters the FIN_WAIT2 phase. The first "two waves" let the server know that the client wants to release the connection, and also let the client know that the server understands its request to release the connection. Therefore, it can be confirmed that the connection from the client to the server is closed.

[0040] 3) After the server sends the ACK confirmation message, it goes through the CLOSED_WAIT phase and is ready to release the connection from the server to the client. It sends another TCP message to the client, in which the mark bit of the TCP message is FIN, indicating "ready to release the connection". The server then ends the CLOSE_WAIT phase and enters the LAST-ACK phase, and stops sending data from the server to the client, but the server can still receive data transmitted from the client.

[0041] 4) The client receives the TCP message sent from the server, confirms that the server is ready to release the connection, ends the FIN_WAIT2 phase, enters the TIME-WAIT phase, and sends a TCP message to the server, where the message is marked as ACK, indicating "received the signal from the server that it is ready to release the connection." The client then begins to wait for 2MSL (Maximum Segment Lifetime, the maximum lifetime of a message, which is the maximum time any message can exist on the network. Messages exceeding this time will be discarded) in the TIME-WAIT phase. After the server receives the TCP message sent from the client, it ends the LAST_ACK phase and enters the CLOSED phase. This formally confirms the closure of the connection from the server to the client. After the client waits for 2MSL, it ends the TIME_WAIT phase and enters the CLOSED phase, thus completing the "four waves". At this time, the TCP communication connection between the client and the server is disconnected.

[0042] In the above example, the "passive closing party" is the server, and the CLOSE_WAIT state is a state that only the "passive closing party" will have. If the "passive closing party" does not call the close function in time to close the TCP communication connection between it and the client when the "active closing party" (client) initiates a connection release request, it will not be able to send a TCP message with the FIN flag bit to the client, and thus the CLOSE_WAIT state cannot be changed to the LAST_ACK state. When a large number of CLOSE_WAIT states appear on the server, it means that the server did not call the close function in time to close the TCP communication connection with the client that initiated the connection release request for some reason. When the server has too many CLOSE_WAIT states, it will cause the occupation of file descriptors, memory resources, CPU resources, and thread resources. When the CPU resources and memory are exhausted, it will cause downtime or restart, and even cause the system to crash.

[0043] When multiple ECU components are upgraded and flashed in parallel, multiple clients can be created and deployed in the data sending center 102, one client corresponds to one ECU component, and each client is connected to the server through TCP communication. When there are many clients created and the data transmitted to the server is large, the load on the server increases sharply. After the ECU component corresponding to the client completes the upgrade and flashing, it is necessary to release and close the TCP communication connection between the client and the server, or there are other ECU components to be upgraded and flashed waiting to be created for the client to be upgraded and flashed. This is a dynamically changing process, which is very challenging for the load and timely response of the server. When the server is heavily loaded, if one or more clients (CLIENT) in the data sending center 102 actively initiate the closure of the TCP communication connection with the server, and send a TCP message with the flag bit as FIN to the server, the server replies ACK to these clients. If the server is busy processing message conversion, forwarding and receiving data, and does not call the close function in time to close the TCP communication connection between itself and these clients, a large number of "CLOSE_WAIT" states may appear in a short period of time, resulting in the occupation of file descriptors, memory resources, CPU resources and thread resources. When CPU resources and memory are exhausted, it will cause downtime or restart, and even cause system crash, which will cause the failure of ECU upgrade and flashing, greatly reducing the performance of upgrade and flashing.

[0044] Based on this, the embodiment of the present application proposes a TCP communication connection management method, which collects and records the first TCP communication connection information when the server and multiple clients establish a TCP communication connection through a server socket monitoring thread deployed on the server, and obtains the second TCP communication connection information according to a preset monitoring period; then, the first TCP communication connection information and the second TCP communication connection information are compared to determine the target client of the TCP communication connection to be closed, and then the connection closing instruction is executed to close the TCP communication connection between the server and the target client. In this way, the client's connection shutdown request can be processed in time, preventing the server from appearing in a large number of "CLOSE_WAIT" states in a short period of time, causing resource waste or downtime due to heavy load, or even system crash, thereby greatly saving CPU resources and memory resources, and ensuring the success rate and performance of ECU upgrade flashing.

[0045] Figure 5 It is a flow chart of a TCP communication connection management method provided in an embodiment of the present application. Figure 5 The TCP communication connection management method can be deployed in the server socket monitoring thread in the server 103 to execute. Figure 5 As shown, the TCP communication connection management method comprises the following steps:

[0046] Step S501, collecting and recording first TCP communication connection information when a server establishes a TCP communication connection with multiple clients, the first TCP communication connection information including a client connection identifier corresponding to each client and a first TCP communication connection state.

[0047] The client connection identifier is the identification information used by the server to distinguish different clients. The identification information can be numbers, text or other symbols. The client connection identifier corresponding to each client is unique.

[0048] The first TCP communication connection state represents the connection state of the TCP communication connection established between the server and the client. For example, the number "1" can be set to indicate the maintained connection state, and the number "0" can be set to indicate the closed state.

[0049] The first TCP communication connection information may also include a server ID, a source address, a destination address, a source port, a destination port, a system occupancy rate, a connection creation timestamp when the server establishes a TCP communication connection with the client, a connection closing timestamp when the server closes the TCP communication connection with the client, etc. The server ID may specifically be a SOCKET ID of the server. The system occupancy rate indicates the occupancy rate of the CPU and memory of the system.

[0050] As an example, the first TCP communication connection information of the embodiment of the present application may be recorded as a first TCP communication connection information table as shown in Table 1. The first TCP communication connection information may be recorded by the server socket monitoring thread and stored in the server 103 .

[0051] Table 1 First TCP communication connection information table

[0052]

[0053]

[0054] Step S502: acquiring second TCP communication connection information according to a preset monitoring cycle, wherein the second TCP communication connection information includes a client identifier corresponding to each client and a second TCP communication connection state; the client connection identifier is associated with the client identifier.

[0055] The client identifier is the identification information of the client that establishes a TCP communication connection with the server, such as the client ID. The identification information can be a number, text, or other symbol. The client identifier corresponding to each client is unique and corresponds to the client connection identifier one by one. The client identifier and the client connection identifier can be the same identifier or different identifiers with a mapping relationship. For example, for client 1, its client identifier and client connection identifier can both be "C ID_1 "; or, its client identifier is "C ID_1 ", the client connection identifier is "C con_1 ”, “C ID_1 ” and “C con_1 " have a mapping relationship (which can be understood as a binding relationship or an association relationship between the two).

[0056] The second TCP communication connection state is used to represent the connection state of the TCP communication connection established between the client and the server. Exemplarily, the number "1" can be set to indicate the maintained connection state, and the number "0" can be set to indicate the closed state.

[0057] The second TCP communication connection information may also include the source address, destination address, source port, destination port, a connection creation timestamp when the client establishes a TCP communication connection with the server, a connection closing timestamp when the client actively closes the TCP communication connection with the server, etc.

[0058] As an example, the second TCP communication connection information of the embodiment of the present application may be recorded as a second TCP communication connection information table as shown in Table 2. The second TCP communication connection information may be recorded by the client socket monitoring thread and stored in the data sending center 102 .

[0059] Table 2 Second TCP communication connection information table

[0060]

[0061] As an example, the client connection identifier is associated with the client identifier, specifically referring to the client connection number C in Table 1 above. con_1 , C con_2 ......C con_n Respectively with the client identifier C in Table 2 above ID_1 , C ID_ 2......C ID_n One-to-one correspondence (i.e., there is an association relationship). That is, C con_1 With C ID_1 Corresponding, C con_2 With C ID_2 Correspondingly, ... and so on, C con_n With C ID_n correspond.

[0062] Step S503: compare the first TCP communication connection information and the second TCP communication connection information to determine the target client of the TCP communication connection to be closed.

[0063] Step S504, executing a connection closing instruction to close the TCP communication connection between the server and the target client.

[0064] The technical solution provided by the embodiment of the present application is to collect and record the first TCP communication connection information when the server and multiple clients establish a TCP communication connection through the server socket monitoring thread deployed on the server, and then obtain the second TCP communication connection information according to the preset monitoring cycle; compare the first TCP communication connection information and the second TCP communication connection information to determine the target client of the TCP communication connection to be closed; finally, execute the connection closing instruction to close the TCP communication connection between the server and the target client. In this way, the connection shutdown request actively initiated by the client can be processed in time, preventing the server from appearing in large numbers in the "CLOSE_WAIT" state in a short period of time, causing resource waste or downtime due to heavy load, or even system crash, thereby greatly saving CPU resources and memory resources, and ensuring the success rate and performance of ECU upgrade flashing.

[0065] In some embodiments, comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed includes:

[0066] Find out the candidate client whose second TCP communication connection state is closed in the second TCP communication connection information;

[0067] Extracting a second candidate TCP communication connection state corresponding to the candidate client from the second TCP communication connection information, and extracting a first candidate TCP communication connection state corresponding to the candidate client from the first TCP communication connection information;

[0068] If the first candidate TCP communication connection state is a connected state and the second candidate TCP communication connection state is a closed state, the candidate client is determined as a target client.

[0069] As an example, see Figure 6 , assuming that the n ECUs being upgraded are all ECUs that do not support Ethernet (such as Figure 1 ECU2-1, ECU2-2...ECU2-n) shown, first, n clients can be created in the OTA upgrade master control (UMC) of the data sending center 102 (such as CDC), namely client 1 (CLIENT1), client 2 (CLIENT2)...client n (CLIENTn), wherein clients 1 to n are all connected to the server 103 (such as VGW) through Ethernet. The server socket monitoring thread deployed in the server 103 obtains the second TCP communication connection information sent by the data sending center 102, and the second TCP communication connection information includes the client identifier corresponding to client 1 to client n and the second TCP communication connection status. The server socket monitoring thread collects and records the first TCP communication connection information when the server 103 and client 1 to client n establish a TCP communication connection, and the first TCP communication connection information includes the client connection identifier corresponding to client 1 to client n and the first TCP communication connection status.

[0070] Exemplarily, assuming that the server socket monitoring thread queries and finds that the second TCP communication connection states of client 1, client 2, client 3, client n-1 and client n are all closed, then client 1, client 2, client 3, client n-1 and client n can be determined as candidate clients. Next, the second candidate TCP communication connection states corresponding to client 1, client 2, client 3, client n-1 and client n are extracted from the second TCP communication connection information. The first candidate TCP communication connection states corresponding to client 1, client 2, client 3, client n-1 and client n are extracted from the first TCP communication connection information. If the second candidate TCP communication connection states of client 1, client 2, client 3, client n-1 and client n are closed 1, closed 2, closed 3, closed n-1 and closed n respectively; the first candidate TCP communication connection states are closed 1, connected 2, connected 3, connected n-1 and connected n respectively. Then the candidate clients of client 2, client 3, client n-1 and client n can be determined as target clients.

[0071] In some other embodiments, comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed includes:

[0072] Extracting a client connection identifier corresponding to each client from the first TCP communication connection information, and extracting a client identifier corresponding to each client from the second TCP communication connection information;

[0073] If the number of client connection identifiers is greater than the number of client identifiers, a client for which no client identifier corresponding to the client connection identifier is found is determined as a target client.

[0074] For the sake of convenience, the above example is continued, and the second TCP communication connection information also includes the connection closing timestamp when the client 1 to the client n actively closes the TCP communication connection with the server 103. In order to save the memory space of the second TCP communication connection information, the relevant information of the client can be deleted automatically after a preset time (which can be flexibly set according to actual conditions, for example, 90 to 120 seconds) from the connection closing timestamp when the client actively closes the TCP communication connection with the server 103. If the TCP message with the mark bit FIN sent by the server is still not received after the preset time after the client actively closes the TCP communication connection with the server 103, and the relevant information of the client has been deleted in the second TCP communication connection information, then it is possible that the relevant information with the client cannot be found in the second TCP communication connection information, while the relevant information of the client is still retained in the first TCP communication connection information. Therefore, the server socket monitoring thread can find out the clients corresponding to the deleted client identifiers by querying the number of client connection identifiers in the first TCP communication connection information and the number of client identifiers in the second TCP communication connection information, and determine these clients as target clients.

[0075] Specifically, the server socket monitoring thread can extract the client connection identifiers of client 1 to client n from the first TCP communication connection information collected and recorded, and extract the client identifiers of client 1 to client n from the acquired second TCP communication connection information. If the number of client connection identifiers is n, and the number of client identifiers is m, and m<n, that is, the number of client connection identifiers is greater than the number of client identifiers, then the client for which the client identifier corresponding to the client connection identifier is not found is determined as the target client. If the client identifiers corresponding to client 2, client 3, client n-1 and client n are not found, then client 2, client 3, client n-1 and client n can be determined as the target client.

[0076] In some embodiments, the server is also deployed with an OTA upgrade agent; multiple clients are deployed in a data transmission center, and the data transmission center is also deployed with a client socket monitoring thread and an OTA upgrade master control;

[0077] The OTA upgrade agent and the OTA upgrade master exchange data by establishing a TCP communication channel to receive the upgrade data packets corresponding to each client transmitted by the OTA upgrade master;

[0078] The server socket monitoring thread and the client socket monitoring thread communicate and interact by establishing a link channel, so as to obtain the second TCP communication connection information transmitted by the client socket monitoring thread through the link channel according to a preset monitoring period.

[0079] Figure 7 1 is a schematic diagram of the connection relationship between the server and the relevant functional modules of the data transmission center provided in an embodiment of the present application. For the convenience of explanation, only the parts related to the embodiment of the present application are shown in the figure.

[0080] See also Figure 7 The server of the embodiment of the present application is the vehicle gateway (VGW), and the data transmission center is the intelligent cockpit controller (CDC). The CDC is deployed with the client socket monitoring thread (or client SOCKET monitoring program), OTA upgrade master (or OTA master), DOIP layer, TCP / IP layer and link layer (MAC layer). The VGW is deployed with the server socket monitoring thread (or server SOCKET monitoring program), OTA upgrade agent, DOIP layer, TCP / IP layer and link layer (MAC layer).

[0081] The OTA upgrade agent (UA) on the server side establishes a TCP communication channel with the OTA upgrade master through its DOIP layer, TCP / IP layer, the DOIP layer, TCP / IP layer of the data transmission center. The OTA upgrade master sends the upgrade data packets corresponding to each client (the client corresponding to the ECU being upgraded) to the server through the TCP communication channel. The server socket monitoring thread deployed in the server establishes a link channel with the client socket monitoring thread through its link layer (MAC layer) and the link layer (MAC layer) of the data transmission center.

[0082] By adopting the above-mentioned dual-channel communication method, the communication interaction process between the server socket monitoring thread and the client socket monitoring thread can be made independent of the data interaction process between the OTA upgrade master and the OTA upgrade agent, thereby avoiding the inability to exchange data and commands due to abnormal conditions in the TCP communication channel, which affects the communication interaction between the server socket monitoring thread and the client socket monitoring thread. This can ensure that the server socket monitoring thread can periodically monitor the TCP communication connection status between the client and the server, execute the closing command in time, and close the redundant invalid links in which the client's TCP communication connection status is already in the closed state while its own TCP communication connection status is still in the connected state, thereby avoiding waste of resources or downtime due to excessive load.

[0083] The server socket monitoring thread can obtain the second TCP communication connection information transmitted by the client socket monitoring thread through the link channel through the link channel according to the preset monitoring period. Among them, the preset monitoring period can be flexibly set according to actual conditions, for example, it can be set to 30 seconds, 60 seconds, etc.

[0084] In some preferred embodiments, a preset monitoring period is set shorter than a preset duration for the client socket monitoring thread to automatically delete the relevant information of the client that has initiated the active closure of the TCP communication connection with the server in the second TCP communication connection information. For example, when the client initiates the active closure of the TCP communication connection with the server, after a preset duration (such as 90 seconds), the client socket monitoring thread automatically deletes the relevant information of the client in the second TCP communication connection information; then the preset monitoring period can be set to within 90 seconds, for example, 30 seconds, 60 seconds, 80 seconds, etc. In this way, before the client socket monitoring thread automatically deletes the relevant information of the client that has initiated the active closure of the TCP communication connection with the server in the second TCP communication connection information, the client that actively closes the TCP communication connection can be detected, and the close function can be called in time to close the TCP communication connection with the client, so as to avoid establishing multiple redundant invalid links, resulting in waste of resources or downtime due to excessive load.

[0085] In some embodiments, the above method further includes:

[0086] Real-time monitoring of the system occupancy rate of the server;

[0087] If the system occupancy rate is greater than or equal to the first occupancy rate and less than the second occupancy rate, sending a first flow control instruction to the client socket monitoring thread through the link channel;

[0088] Client socket monitoring thread:

[0089] Execute the first flow control instruction to control the transmission volume and / or transmission time interval of the TCP / IP layer of the data sending center to transmit the upgrade data packet to the server; wherein the first occupancy rate is less than the second occupancy rate.

[0090] In the embodiment of the present application, the first occupancy rate is usually set to 80%, and the second occupancy rate is usually set to 90%.

[0091] See also Figure 7 , the server socket monitoring thread can monitor the system occupancy of the server in real time. If it is determined that the system occupancy of the server is greater than or equal to the first occupancy (such as 80%) and less than the second occupancy (such as 90%), a first flow control instruction can be sent to the client socket monitoring thread of the data sending center through the link channel. The first flow control instruction includes the system occupancy of the server. After receiving the first flow control instruction, the client socket monitoring thread counts the total amount of data to be transmitted of the upgrade data packet to be sent temporarily stored in the TCP / IP layer of the data sending center; then, according to the system occupancy of the server, the preset drop target value (which can be flexibly set according to actual conditions, for example, 5%, 10%, 15%, etc.), and the total amount of data to be transmitted, determine the transmission time interval for transmitting the upgrade data packet to the server and the transmission amount of the upgrade data packet transmitted in each transmission time interval (the transmission amount is less than the total amount of data to be transmitted); then, according to the transmission time interval and the transmission amount, the upgrade data packet is intermittently transmitted to the server, so that the system occupancy of the server gradually decreases to the target system occupancy, thereby ensuring the normal operation of the server. The target system occupancy rate = the current system occupancy rate - the preset reduction target value. For example, if the current system occupancy rate is 85% and the preset reduction target value is 10%, then the target system occupancy rate is 85% - 10% = 75%.

[0092] In some embodiments, after real-time monitoring of the system occupancy rate of the server, the method further includes:

[0093] If the system occupancy rate is greater than or equal to the second occupancy rate, sending a second flow control instruction to the client socket monitoring thread through the link channel, so that the client socket monitoring thread forwards the second flow control instruction to the OTA upgrade master control;

[0094] OTA upgrade master control:

[0095] Receive and execute the second flow control instruction to determine the data communication priority of each client;

[0096] Based on the data communication priority and system occupancy, low-priority clients are determined, and the transmission of upgrade data packets corresponding to the low-priority clients to the OTA upgrade agent is suspended.

[0097] To make it easier to understand, continue using the above example, see Figure 7, if the server socket monitoring thread detects that its current system occupancy is greater than or equal to the second occupancy (such as 90%), then a second flow control instruction can be sent to the client socket monitoring thread through the link channel, and the second flow control instruction includes the current system occupancy of the server. The client socket monitoring thread forwards the received second flow control instruction to the OTA upgrade master. The OTA upgrade master receives and executes the second flow control instruction, and determines the amount of data that needs to be suspended according to the current system occupancy, the preset drop target and the total amount of data to be transmitted. For example, the current system occupancy is 95%, the preset drop target is 20%, and the total amount of data to be transmitted is y0MB, then the target system occupancy is 75% (95%-20%=75%). Further, according to the current system occupancy, the target system occupancy, and the total amount of data to be transmitted, the amount of data to be suspended is calculated. Specifically, the amount of transmittable data corresponding to the target system occupancy can be calculated first, and then the difference between the total amount of data to be transmitted and the amount of transmittable data is calculated, which is the amount of data that needs to be suspended. Exemplarily, assuming that the amount of transmittable data corresponding to the target system occupancy rate is y1, the amount of data that needs to be temporarily suspended from transmission is (y0-y1).

[0098] Next, the server socket monitoring thread calls out the pre-set data communication priority for each client, and then determines the low-priority client according to the amount of data to be suspended and the amount of data to be transmitted corresponding to the client with a lower priority in the data communication priority. As an example, assume that there are 5 clients deployed in the CDC, which are respectively recorded as clients 1, 2, 3, 4 and 5; the data communication priorities of clients 1 to 5 are (priority from high to low): client 1> client 4> client 2> client 3> client 5. Among them, the amount of data to be transmitted corresponding to clients 1 to 5 is A1, A2, A3, A4 and A5 respectively. Next, in the order from client 5→client 3→client 2→client 4→client 1, find the low-priority client that meets the amount of data that needs to be suspended. Specifically, first determine whether the amount of data to be transmitted corresponding to client 5 A5≥y0-y1 is established; if established, then determine client 5 as a low-priority client; if not established, that is, A5<(y0-y1), then continue to determine whether A5+A3≥y0-y1 is established. If A5+A3≥y0-y1 holds, client 5 and client 3 are determined as low priority clients; if A5+A3<y0-y1 does not hold, then continue to determine whether A5+A3+A2≥y0-y1 holds. If A5+A3+A2≥y0-y1 holds, client 5, client 3 and client 2 are determined as low priority clients.

[0099] After determining the low-priority client, the OTA upgrade master controller suspends transmitting the upgrade data packets corresponding to the low-priority client to the server to avoid too many clients transmitting data to the server at the same time, causing excessive load and abnormalities. At the same time, it can ensure that clients with higher data communication priority can still upgrade and flash normally.

[0100] In some embodiments, after executing the connection closing instruction to close the TCP communication connection between the server and the target client, the method further includes:

[0101] Get the connection closing timestamp corresponding to the target client;

[0102] Starting from the connection closing timestamp, after a preset period of time, the relevant information corresponding to the target client in the first TCP communication connection information is cleared.

[0103] Specifically, after closing the TCP communication connection corresponding to the server and the target client, the server socket monitoring thread can extract the recorded connection closing timestamp corresponding to the target client from the first TCP communication connection information. Then, starting from the connection closing timestamp, after a preset time (which can be flexibly set according to actual conditions, for example, 90 seconds, 120 seconds, etc.), the relevant information corresponding to the target client in the first TCP communication connection information is cleared, thereby saving space in the first TCP communication connection information.

[0104] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0105] In summary, the technical solution provided in the embodiment of the present application supports monitoring the TCP communication connection status between the client and the server through the server socket monitoring thread, so as to promptly close the TCP communication connection from the server to the client when the server is in the "CLOSE_WAIT" state, thereby avoiding establishing multiple redundant invalid links, causing resource waste or causing downtime due to excessive load, and greatly saving CPU resources and memory resources; supporting the server socket monitoring thread to communicate and interact with the client socket monitoring program through the link channel, thereby avoiding the inability to exchange data and commands due to abnormal conditions in the TCP communication channel, which affects the communication and interaction between the server socket monitoring thread and the client socket monitoring thread; supporting the adjustment of the number of clients according to the current system occupancy rate of the server, thereby avoiding too many clients transmitting data to the server at the same time, resulting in excessive load and abnormalities, which is beneficial to improving the reliability of data transmission.

[0106] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0107] Figure 8 Schematic diagram of the structure of a TCP communication connection management device provided in an embodiment of the present application. Figure 8 As shown, the TCP communication connection management device includes:

[0108] The collection and recording module 801 is configured to collect and record first TCP communication connection information when the server establishes a TCP communication connection with multiple clients, the first TCP communication connection information including a client connection identifier corresponding to each client and a first TCP communication connection state;

[0109] The monitoring acquisition module 802 is configured to acquire the second TCP communication connection information according to a preset monitoring period, wherein the second TCP communication connection information includes a client identifier corresponding to each client and a second TCP communication connection state; the client connection identifier is associated with the client identifier;

[0110] A comparison module 803 is configured to compare the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed;

[0111] The closing module 804 is configured to execute a connection closing instruction to close the TCP communication connection between the server and the target client.

[0112] In some embodiments, the comparison module 803 includes:

[0113] A searching unit configured to search for a candidate client whose second TCP communication connection state is a closed state in the second TCP communication connection information;

[0114] A first extraction unit is configured to extract a second candidate TCP communication connection state corresponding to the candidate client from the second TCP communication connection information, and extract a first candidate TCP communication connection state corresponding to the candidate client from the first TCP communication connection information;

[0115] The first determining unit is configured to determine the candidate client as the target client if the first candidate TCP communication connection state is a connected state and the second candidate TCP communication connection state is a closed state.

[0116] In some other embodiments, the comparison module 803 includes:

[0117] A second extraction unit is configured to extract a client connection identifier corresponding to each client from the first TCP communication connection information, and extract a client identifier corresponding to each client from the second TCP communication connection information;

[0118] The second determining unit is configured to determine a client for which no client identifier corresponding to the client connection identifier is found as a target client if the number of the client connection identifiers is greater than the number of the client identifiers.

[0119] In some embodiments, the server is also deployed with an OTA upgrade agent; multiple clients are deployed in a data transmission center, and the data transmission center is also deployed with a client socket monitoring thread and an OTA upgrade master control;

[0120] The OTA upgrade agent and the OTA upgrade master exchange data by establishing a TCP communication channel to receive the upgrade data packets corresponding to each client transmitted by the OTA upgrade master;

[0121] The server socket monitoring thread and the client socket monitoring thread communicate and interact by establishing a link channel, so as to obtain the second TCP communication connection information transmitted by the client socket monitoring thread through the link channel according to a preset monitoring period.

[0122] In some embodiments, the above apparatus further comprises:

[0123] A monitoring module, configured to monitor the system occupancy rate of the server in real time;

[0124] A first sending module is configured to send a first flow control instruction to the client socket monitoring thread through a link channel if the system occupancy rate is greater than or equal to the first occupancy rate and less than the second occupancy rate;

[0125] Client socket monitoring thread:

[0126] Execute the first flow control instruction to control the transmission volume and / or transmission time interval of the TCP / IP layer of the data sending center to transmit the upgrade data packet to the server; wherein the first occupancy rate is less than the second occupancy rate.

[0127] In some embodiments, the above apparatus further comprises:

[0128] A second sending module is configured to send a second flow control instruction to the client socket monitoring thread through the link channel if the system occupancy rate is greater than or equal to the second occupancy rate, so that the client socket monitoring thread forwards the second flow control instruction to the OTA upgrade master control;

[0129] OTA upgrade master control:

[0130] Receive and execute the second flow control instruction to determine the data communication priority of each client;

[0131] Based on the data communication priority and system occupancy, low-priority clients are determined, and the transmission of upgrade data packets corresponding to the low-priority clients to the OTA upgrade agent is suspended.

[0132] In some embodiments, the above apparatus further comprises:

[0133] A time acquisition module is configured to obtain a connection closing timestamp corresponding to a target client;

[0134] The cleaning module is configured to clean up the relevant information corresponding to the target client in the first TCP communication connection information after a preset time period, starting from the connection closing timestamp.

[0135] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0136] The embodiment of the present application also provides a server, which includes: Figure 8 The TCP communication connection management device shown.

[0137] Fig. 9 Schematic diagram of an electronic device 9 provided in an embodiment of the present application. Fig. 9 As shown, the electronic device 9 of this embodiment includes: a processor 901, a memory 902, and a computer program 903 stored in the memory 902 and executable on the processor 901. When the processor 901 executes the computer program 903, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 901 executes the computer program 903, the functions of the modules / units in the above-mentioned device embodiments are implemented.

[0138] The electronic device 9 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 9 may include, but is not limited to, a processor 901 and a memory 902. Those skilled in the art will appreciate that Fig. 9 The electronic device 9 is merely an example and does not limit the electronic device 9 , and may include more or less components than those shown in the figure, or different components.

[0139] The processor 901 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0140] The memory 902 may be an internal storage unit of the electronic device 9, for example, a hard disk or memory of the electronic device 9. The memory 902 may also be an external storage device of the electronic device 9, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 9. The memory 902 may also include both an internal storage unit of the electronic device 9 and an external storage device. The memory 902 is used to store computer programs and other programs and data required by the electronic device.

[0141] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0142] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium (e.g., a computer-readable storage medium). Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. Computer-readable storage media may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.

[0143] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A TCP communication connection management method, characterized in that: Applied to a server socket monitoring thread, the server socket monitoring thread is deployed on the server; the method comprises the following steps: Collecting and recording first TCP communication connection information when the server establishes a TCP communication connection with multiple clients, the first TCP communication connection information including a client connection identifier corresponding to each of the clients and a first TCP communication connection state; According to a preset monitoring cycle, second TCP communication connection information is obtained, where the second TCP communication connection information includes a client identifier corresponding to each of the clients and a second TCP communication connection state; the client connection identifier is associated with the client identifier; Comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed; Execute a connection closing instruction to close the TCP communication connection between the server and the target client.

2. The method according to claim 1, characterized in that Comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of a TCP communication connection to be closed includes: Find out the candidate client whose second TCP communication connection state is closed in the second TCP communication connection information; Extracting a second candidate TCP communication connection state corresponding to the candidate client from the second TCP communication connection information, and extracting a first candidate TCP communication connection state corresponding to the candidate client from the first TCP communication connection information; If the first candidate TCP communication connection state is a connected state and the second candidate TCP communication connection state is a closed state, the candidate client is determined as a target client.

3. The method according to claim 1, characterized in that Comparing the first TCP communication connection information with the second TCP communication connection information to determine a target client of a TCP communication connection to be closed includes: Extracting a client connection identifier corresponding to each of the clients from the first TCP communication connection information, and extracting a client identifier corresponding to each of the clients from the second TCP communication connection information; If the number of the client connection identifiers is greater than the number of the client identifiers, a client for which no client identifier corresponding to the client connection identifier is found is determined as a target client.

4. The method according to claim 1, characterized in that: The server is also deployed with an OTA upgrade agent; multiple clients are deployed in a data sending center, and the data sending center is also deployed with a client socket monitoring thread and an OTA upgrade master control; The OTA upgrade agent and the OTA upgrade master control exchange data by establishing a TCP communication channel to receive upgrade data packets corresponding to each of the clients transmitted by the OTA upgrade master control; The server socket monitoring thread and the client socket monitoring thread communicate and interact by establishing a link channel to obtain the second TCP communication connection information transmitted by the client socket monitoring thread through the link channel according to a preset monitoring period.

5. The method according to claim 4, characterized in that The method further comprises: Real-time monitoring of the system occupancy rate of the server; If the system occupancy rate is greater than or equal to the first occupancy rate and less than the second occupancy rate, sending a first flow control instruction to the client socket monitoring thread through the link channel; The client socket monitoring thread: Execute the first flow control instruction to control the transmission volume and / or transmission time interval of the upgrade data packet transmitted by the TCP / IP layer of the data sending center to the server; wherein the first occupancy rate is less than the second occupancy rate.

6. The method according to claim 5, characterized in that After real-time monitoring of the system occupancy rate of the server, the method further includes: If the system occupancy rate is greater than or equal to the second occupancy rate, sending a second flow control instruction to the client socket monitoring thread through the link channel, so that the client socket monitoring thread forwards the second flow control instruction to the OTA upgrade master control; The OTA upgrade master control: receiving and executing the second flow control instruction to determine the data communication priority of each of the clients; Based on the data communication priority and the system occupancy rate, a low-priority client is determined, and transmission of an upgrade data packet corresponding to the low-priority client to the OTA upgrade agent is suspended.

7. The method according to claim 1, characterized in that After executing the connection closing instruction to close the TCP communication connection between the server and the target client, the method further includes: Obtain the connection closing timestamp corresponding to the target client; Starting from the connection closing timestamp, after a preset time period, the relevant information corresponding to the target client in the first TCP communication connection information is cleared.

8. A TCP communication connection management device, characterized in that: include: A collection and recording module is configured to collect and record first TCP communication connection information when a server establishes a TCP communication connection with multiple clients, wherein the first TCP communication connection information includes a client connection identifier corresponding to each of the clients and a first TCP communication connection state; A monitoring acquisition module is configured to acquire second TCP communication connection information according to a preset monitoring period, wherein the second TCP communication connection information includes a client identifier corresponding to each of the clients and a second TCP communication connection state; The client connection identifier is associated with the client identifier; A comparison module, configured to compare the first TCP communication connection information with the second TCP communication connection information to determine a target client of the TCP communication connection to be closed; The closing module is configured to execute a connection closing instruction to close the TCP communication connection between the server and the target client.

9. A server, characterized in that: It comprises the TCP communication connection management device as described in claim 8.

10. A readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images