CN115134553A - Data transmission method and device, electronic equipment and storage medium - Google Patents

Abstract

The application provides a data transmission method, device, electronic device and storage medium; it relates to the field of cloud technology and communication technology, and the method includes: creating a first data connection with a terminal for data transmission, and the first data connection is A connection identifier, which remains unchanged when the Internet Protocol address or port of the terminal changes; receives a data packet transmitted by the terminal based on the first data connection; parses the data packet to determine the data The data type corresponding to the packet; when it is determined that the data type of the data packet is an unreliable data type, the control does not return a reception response message corresponding to the data packet to the terminal; through this application, unnecessary network resources can be reduced Occupy, improve the utilization of network resources.

Description

Data transmission method, device, electronic device and storage medium

technical field

The present application relates to the field of cloud technology and communication technology, and in particular, to a data transmission method, apparatus, electronic device, and storage medium.

Background technique

In the related art, unreliable data that does not require reliable transmission, such as audio and video data and frequently moving coordinate data, is often multiplexed and transmitted on the same channel as reliable data that requires reliable transmission, that is, both are transmitted in a reliable transmission mode. When the network is poor, the retransmission strategy of the reliable transmission method will bring greater pressure to the network, and will affect the normal transmission of reliable data such as signaling.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a data transmission method, apparatus, electronic device, and storage medium, which can reduce unnecessary occupation of network resources and improve the utilization rate of network resources.

The technical solutions of the embodiments of the present application are implemented as follows:

The embodiment of the present application provides a data transmission method, including:

Create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes;

receiving a data packet transmitted by the terminal based on the first data connection;

Analyzing the data packet to determine the data type corresponding to the data packet;

When it is determined that the data type of the data packet is an unreliable data type, the control does not return a reception response message corresponding to the data packet to the terminal.

The embodiment of the present application provides a data transmission method, including:

Create a first data connection with the server for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the server changes;

sending a data packet to the server based on the first data connection;

The data type of the data packet includes an unreliable data type, and the unreliable data type is used to control not to return the corresponding data when the server determines that the data type of the data packet is an unreliable data type Packet receive response message.

The embodiment of the present application also provides a data transmission device, including:

A creation module is used to create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes;

a receiving module, configured to receive a data packet transmitted by the terminal based on the first data connection;

a parsing module, configured to parse the data packet to determine the data type corresponding to the data packet;

A control module, configured to control not to return a reception response message corresponding to the data packet to the terminal when it is determined that the data type of the data packet is an unreliable data type.

In the above scheme, the device also includes:

a connection state control module, configured to obtain a heartbeat packet sending cycle, and send a heartbeat packet to the terminal through the first data connection according to the heartbeat packet sending cycle;

When the heartbeat response information for the heartbeat packet is received, the connection state corresponding to the first data connection is controlled to be an active state.

In the above solution, when the first data connection is established for the first time, the creation module is further configured to receive a first inquiry data packet sent by the terminal for requesting to establish a data connection;

based on the first inquiry data packet, sending a corresponding response data packet to the terminal;

When receiving the second inquiry data packet sent by the terminal, a first data connection for data transmission with the terminal is established.

In the above solution, when the first data connection is not established for the first time, the creation module is further configured to receive an inquiry data packet sent by the terminal for requesting to establish a data connection;

Based on the inquiry data packet, a first data connection for data transmission with the terminal is established.

In the above scheme, the parsing module is also used to extract the header part of the data packet;

The packet header part is parsed to obtain a message field for indicating the data type;

The data type indicated by the packet field is determined as the data type corresponding to the data packet.

In the above scheme, the device also includes:

The first migration module is configured to establish a second data connection with the terminal through the first socket interface of the terminal when the Internet Protocol address of the terminal is changed, so as to connect the terminal with the terminal. migrating the data connection from the first data connection to the second data connection;

Wherein, the connection identifier of the second data connection is consistent with the connection identifier of the first data connection.

In the above solution, the first migration module is further configured to send a probe data packet including the first verification information to the terminal through the second data connection based on the connection identifier;

receiving a response data packet returned by the terminal for the probe data packet, where the response data packet includes second verification information;

The first verification information is verified based on the second verification information, and when a verification result indicating that the verification is passed is obtained, data transmission with the terminal is performed based on the second data connection.

In the above solution, the first migration module is further configured to receive a probe data packet including third verification information that is transmitted by the terminal through the second data connection based on the connection identifier;

sending a response data packet to the terminal for the probe data packet, where the response data packet includes fourth verification information;

The fourth verification information is used for the terminal to verify the fourth verification information based on the third verification information, and when a verification result indicating that the verification is passed is obtained, the verification is performed based on the second data connection. data transmission.

In the above scheme, the device also includes:

A second migration module, configured to monitor whether the target Internet Protocol address is changed, and obtain a monitoring result, where the target Internet Protocol address belongs to the server that establishes the first data connection with the terminal;

When the monitoring result indicates that the target Internet Protocol address is changed, create a second socket interface for the changed target Internet Protocol address, and

establishing a third data connection with the terminal based on the second socket interface, so as to migrate the data connection with the terminal from the first data connection to the third data connection;

Wherein, the connection identifier of the third data connection is consistent with the connection identifier of the first data connection.

In the above solution, the second migration module is further configured to perform at least one of the data transmission failure event of the original socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address. monitor;

When at least one of the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address are monitored, a monitoring indicating that the target Internet Protocol address is changed is obtained. result.

In the above solution, the second migration module is further configured to verify the data reachability of the third data connection based on the connection identifier to obtain a verification result;

When the verification result indicates that the data of the third data connection is reachable, perform data transmission with the terminal based on the third data connection.

The embodiment of the present application also provides a data transmission device, including:

a connection creation module for creating a first data connection with a server for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the server changes;

a sending module, configured to send a data packet to the server based on the first data connection;

The data type of the data packet includes an unreliable data type, and the unreliable data type is used to control not to return the corresponding data when the server determines that the data type of the data packet is an unreliable data type Packet receive response message.

The embodiment of the present application also provides an electronic device, including:

memory for storing executable instructions;

The processor is configured to implement the data transmission method provided by the embodiment of the present application when executing the executable instructions stored in the memory.

Embodiments of the present application further provide a computer-readable storage medium storing executable instructions, and when the executable instructions are executed by a processor, the data transmission method provided by the embodiments of the present application is implemented.

The embodiment of the present application has the following beneficial effects:

Create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is detected, the data packet is parsed to determine the data type corresponding to the data packet; when the data type of the data packet is determined to be an unreliable data type, the control does not return a reception response message corresponding to the data packet to the terminal. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

Description of drawings

FIG. 1 is a schematic structural diagram of a data transmission system 100 provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of an electronic device 500 according to a data transmission method provided by an embodiment of the present application;

3A is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

3B is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application;

5 is a schematic flowchart of a method for creating a persistent connection for data transmission provided by an embodiment of the present application;

6 is a schematic diagram of an application of a client provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of the establishment of a TCP connection provided by an embodiment of the present application;

8 is a schematic flowchart of a TLS connection establishment provided by an embodiment of the present application;

9 is a schematic diagram of the performance of a client when an Internet Protocol address is changed according to an embodiment of the present application;

FIG. 10 is a schematic flowchart of the establishment of a QUIC connection provided by an embodiment of the present application;

11 is a schematic flowchart of a method for creating a persistent connection for data transmission provided by an embodiment of the present application;

12 is a schematic flowchart of connection migration of a data connection provided by an embodiment of the present application;

13 is a schematic flowchart of connection migration provided by an embodiment of the present application;

14 is a schematic flowchart of path verification provided by an embodiment of the present application;

15 is a schematic diagram of a reliable frame format and an unreliable frame format provided by an embodiment of the present application;

16 is a schematic flowchart of data transmission applied to remote control provided by an embodiment of the present application;

17A is a schematic diagram of a picture-in-picture mode provided by an embodiment of the present application;

17B is a schematic diagram of sound level display provided by an embodiment of the present application;

FIG. 18 is a schematic diagram of optimization of client indicators provided by an embodiment of the present application;

19 is a schematic structural diagram of a data transmission device 555 provided by an embodiment of the present application;

FIG. 20 is a schematic structural diagram of a data transmission apparatus 2000 provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings. All other embodiments obtained under the premise of creative work fall within the scope of protection of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" can be the same or a different subset of all possible embodiments, and Can be combined with each other without conflict.

In the following description, the term "first\second\third" is only used to distinguish similar objects, and does not represent a specific ordering of objects. It is understood that "first\second\third" Where permitted, the specific order or sequence may be interchanged to enable the embodiments of the application described herein to be practiced in sequences other than those illustrated or described herein.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application, and are not intended to limit the present application.

Before further describing the embodiments of the present application in detail, the terms and terms involved in the embodiments of the present application are described, and the terms and terms involved in the embodiments of the present application are suitable for the following explanations.

1) A client, an application program running in the terminal for providing various services, such as an instant messaging client and a video playing client.

2) In response, used to represent the condition or state on which the executed operation depends, when the dependent condition or state is satisfied, the executed one or more operations may be real-time or may have a set delay; Unless otherwise specified, there is no restriction on the order of execution of multiple operations to be executed.

3) TCP: Transmission Control Protocol, is a connection-oriented, reliable, byte stream-based transport layer communication protocol, defined by RFC 793 of the IETF (Internet Engineering Task Force).

4) TLS: Transport Layer Security, is a security protocol, the purpose is to provide security and data integrity guarantee for Internet communication

5) QUIC: Quick UDP Internet Connection, is a low-latency and reliable Internet transport layer protocol based on UDP formulated by Google. It was standardized by the IETF (International Internet Engineering Task Force) in November 2016. It is expected to start from the foundation in 2021. The draft is published as an RFC.

6) Cellular: Cellular technology, a wireless communication technology, also known as GPRS/3G/4G/5G network.

7) Long connection: a long-term effective and reliable data transmission channel established and maintained between the client and the background.

8) XMPP: XMPP is a protocol based on the subset XML of standard universal markup speech, which inherits the flexible development in the XML environment. Can be used for streaming of XML data elements in service class real-time communication, presentation and demand response services. Therefore, the application based on XMPP has super extensibility, which is defined by RFC3920 of IETF (Internet Engineering Task Force).

9) RTT: Round-Trip Time, round-trip delay. It is an important performance indicator in computer networks, indicating the total delay experienced from the time the sender sends data until the sender receives an acknowledgment from the receiver (the receiver sends an acknowledgment immediately after receiving the data).

Based on the above explanations of terms and terms involved in the embodiments of the present application, the data transmission system provided by the embodiments of the present application is described below. Referring to FIG. 1, FIG. 1 is a schematic structural diagram of a data transmission system 100 provided by an embodiment of the present application. In order to support an exemplary application, a terminal (exemplarily shows a terminal 400-1) is connected to the server 200 through the network 300, and the network 300 It can be a wide area network or a local area network, or a combination of the two, using wireless or wired links for data transmission.

a terminal (such as terminal 400-1), used to create a first data connection with the server 200 for data transmission; send data packets to the server 200 based on the first data connection;

The server 200 is configured to create a first data connection with the terminal for data transmission; receive a data packet transmitted by the terminal based on the first data connection; parse the data packet to determine the data type corresponding to the data packet; When it is determined that the data type of the data packet is an unreliable data type, the control does not return a reception response message corresponding to the data packet to the terminal.

The embodiments of the present application can be implemented with the help of cloud technology. Cloud technology refers to a kind of hosting that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize data computing, storage, processing, and sharing. technology.

Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, and application technology based on cloud computing business models. Cloud computing technology will become an important support. Background services of technical network systems require a lot of computing and storage resources.

In practical applications, the server 200 may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud service, cloud database, cloud computing, cloud function, cloud storage, network Cloud servers for basic cloud computing services such as services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal (eg, terminal 400-1) may be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart TV, a smart watch, etc., but is not limited thereto. The terminal (eg, the terminal 400-1) and the server 200 may be directly or indirectly connected through wired or wireless communication, which is not limited in this application.

Referring to FIG. 2 , FIG. 2 is a schematic structural diagram of an electronic device 500 according to a data transmission method provided by an embodiment of the present application. In practical applications, the electronic device 500 may be the server or terminal shown in FIG. 1 . Taking the electronic device 500 as the terminal shown in FIG. 1 as an example, the electronic device implementing the data transmission method of the embodiment of the present application will be described. The electronic device 500 provided by the embodiment of the application includes: at least one processor 510 , a memory 550 , at least one network interface 520 and a user interface 530 . The various components in electronic device 500 are coupled together by bus system 540 . It can be understood that the bus system 540 is used to implement the connection communication between these components. In addition to the data bus, the bus system 540 also includes a power bus, a control bus and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 540 in FIG. 2 .

The processor 510 may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where a general-purpose processor may be a microprocessor or any conventional processor or the like.

User interface 530 includes one or more output devices 531 that enable presentation of media content, including one or more speakers and/or one or more visual display screens. User interface 530 also includes one or more input devices 532, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, and other input buttons and controls.

Memory 550 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. Memory 550 optionally includes one or more storage devices that are physically remote from processor 510 .

Memory 550 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory. The non-volatile memory may be Read Only Memory (ROM, Read Only Memory), and the volatile memory may be Random Access Memory (RAM, Random Access Memory). The memory 550 described in the embodiments of the present application is intended to include any suitable type of memory.

In some embodiments, memory 550 is capable of storing data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.

The operating system 551 includes system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;

A network communication module 552 for reaching other computing devices via one or more (wired or wireless) network interfaces 520, exemplary network interfaces 520 including: Bluetooth, Wireless Compatibility (WiFi), and Universal Serial Bus ( USB, Universal Serial Bus), etc.;

A presentation module 553 for enabling presentation of information (eg, a user interface for operating peripherals and displaying content and information) via one or more output devices 531 associated with the user interface 530 (eg, a display screen, speakers, etc.) );

An input processing module 554 for detecting one or more user inputs or interactions from one of the one or more input devices 532 and translating the detected inputs or interactions.

In some embodiments, the data transmission apparatus provided by the embodiments of the present application may be implemented in software. FIG. 2 shows the data transmission apparatus 555 stored in the memory 550, which may be software in the form of programs and plug-ins, including the following Software modules: creation module 5551, receiving module 5552, parsing module 5553 and control module 5554, these modules are logical, so they can be combined arbitrarily or further split according to the functions implemented, and the functions of each module will be explained below .

In some other embodiments, the data transmission apparatus provided by the embodiments of the present application may be implemented by a combination of software and hardware. As an example, the data transmission apparatus provided by the embodiments of the present application may be processors in the form of hardware decoding processors. It is programmed to execute the data transmission method provided by the embodiments of the present application. For example, the processor in the form of a hardware decoding processor may adopt one or more application specific integrated circuits (ASIC, Application Specific Integrated Circuit), DSP, programmable logic device (PLD, Programmable Logic Device), Complex Programmable Logic Device (CPLD, Complex Programmable Logic Device), Field Programmable Gate Array (FPGA, Field-Programmable Gate Array) or other electronic components.

Based on the above description of the data transmission system and the electronic device provided by the embodiment of the present application, the data transmission method provided by the embodiment of the present application is described below. In some embodiments, the data transmission method provided by the embodiments of the present application may be implemented by a server or a terminal alone, or by a server and a terminal in cooperation. The data transmission method provided by the embodiments of the present application is described below by taking the server implementation as an example. Referring to FIG. 3A, FIG. 3A is a schematic flowchart of a data transmission method provided by an embodiment of the present application. The data transmission method provided by an embodiment of the present application includes:

Step 101: The server creates a first data connection with the terminal for data transmission.

The connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes.

Here, before the server performs data communication with the terminal, a first data connection for data transmission between the server and the terminal may be created in advance. After the first data connection is created, the server and the terminal send and receive data packets through the first data connection. In practical applications, the terminal may be provided with an application client, such as a conference client, a learning client, etc., and the server may be a background server of the corresponding application client.

In the embodiment of the present application, the connection identifier of the first data connection remains unchanged when the Internet Protocol address (that is, the IP address) or the port of any one of the terminal and the server is changed, that is, the connection between the terminal and the server is changed. When the IP address or port changes, the data channel between the terminal and the server will not be interrupted, and both parties can transmit data packets based on the connection identifier of the first data connection. In this way, when the IP address of the terminal or server is changed, it does not affect the data transmission between the two parties, and for the user, the change of the IP address is insensitive, and there will be no network disconnection, need to reconnect, etc. Happening.

In practical applications, the first data connection is established based on the QUIC protocol, and the connection identifier of the QUIC connection is a 64-bit connection ID. When the address or port (Port) changes, the connection ID in the QUIC connection remains unchanged, and both the terminal and the server can still transmit data packets based on the connection identifier of the QUIC connection, so there is no need to re-create the connection through the protocol handshake and other processes. In this way, QUIC connection migration can achieve the technical effect of network type switching without user perception.

In some embodiments, when the first data connection is established for the first time, the server may create a first data connection with the terminal for data transmission in the following manner: receiving the first inquiry data sent by the terminal for requesting to establish a data connection packet; based on the first inquiry data packet, send a corresponding response data packet to the terminal; when receiving the second inquiry data packet sent by the terminal, create a first data connection with the terminal for data transmission.

In practical applications, the first data connection may be implemented based on the QUIC protocol. Specifically, when the first data connection is established for the first time, the first data connection may be established between the server and the terminal in the following manner: when the terminal needs to establish a data connection with the server, it sends a first question requesting the establishment of the data connection to the server. After receiving the first query data packet, the server sends a corresponding response data packet to the terminal based on the first query data packet, and the response data packet may include the public key information of the key exchange algorithm, Algorithm information, certificate information, protocol available version information, etc.; the terminal receives the response data packet sent by the server and stores the information contained therein, and then sends a second inquiry data packet to the server, which can carry the terminal The encrypted information, such as the public key information of the client running on the terminal; after the server receives the second query data packet, if it accepts the establishment of a data connection, it will create a first data connection with the terminal, and if not, it will return to reject the establishment response information. Here, the encryption information corresponding to the terminal and the server is used to encrypt the data transmitted in the first data connection, so as to ensure the security of data transmission.

In actual implementation, when the terminal sends the second query data packet, the encrypted information of the terminal may be sent together with the application data; when the server receives the second query data packet, it establishes an The first data connection between the terminals can accordingly respond to the application data in the second query data packet. In this way, the first data connection can complete the protocol handshake and data encryption operations within one RTT, which not only reduces the time-consuming handshake of the data connection, but also completes the encrypted data transmission, ensuring data security.

In some embodiments, when the first data connection is not established for the first time, the server may create a first data connection with the terminal for data transmission in the following manner: receiving an inquiry data packet sent by the terminal for requesting to establish a data connection ; Create a first data connection with the terminal for data transmission based on the query data packet.

In practical applications, the first data connection may be implemented based on the QUIC protocol. Specifically, when the first data connection is not established for the first time, the first data connection can be established between the server and the terminal in the following manner: Since the data connection between the terminal and the server is not established for the first time, the terminal side stores relevant information of the server, That is, the public key information, algorithm information, certificate information, protocol available version information, etc. of the key exchange algorithm in the second query data packet stored when the data connection is first established. At this time, when the terminal needs to establish a data connection with the server again, the terminal only needs to send a query data packet requesting to establish a data connection to the server, and the query data packet can directly carry encrypted application data; the server receives the query After the data packet is received, if the establishment of the connection is accepted, the first data connection with the terminal is directly established, so that a corresponding response can be made to the application data in the query data packet. In this way, the first data connection can be established within 0 RTTs, which not only reduces the time-consuming handshake of the data connection, but also completes the encrypted data transmission and ensures the security of the data.

In some embodiments, after creating the first data connection with the terminal for data transmission, the server may maintain the connection state of the first data connection as an active state by obtaining the heartbeat packet sending cycle, and according to the heartbeat packet sending cycle , send a heartbeat packet to the terminal through the first data connection; when receiving heartbeat response information for the heartbeat packet, control the connection state corresponding to the first data connection to be an active state.

Here, after establishing the first data connection with the terminal, the server also needs to maintain the connection state of the first data connection as an active state. That is, a heartbeat mechanism is set, and by sending a heartbeat packet to the terminal, it is judged whether the heartbeat response information of the heartbeat packet is received within a preset duration threshold, so as to determine whether it is necessary to maintain the connection state of the first data connection as an active state, thereby maintaining The first data connection between the server and the terminal is a persistent connection. Specifically, a heartbeat packet sending cycle and a duration threshold can be preset; then, according to the heartbeat packet sending cycle, send a heartbeat packet to the terminal through the first data connection; determine whether the terminal receives the heartbeat packet within the preset duration threshold and returns a response to the heartbeat packet The heartbeat response information; when it is determined that the heartbeat response information returned by the terminal for the heartbeat packet is received within the preset duration threshold, the connection state corresponding to the first data connection is controlled to be an active state, and when it is determined to be within the preset duration threshold. If the heartbeat response information returned by the terminal for the heartbeat packet is not received, the connection state corresponding to the first data connection is controlled to be a disconnected state, that is, the first data connection with the terminal is disconnected to reduce waste of network resources.

Step 102: Receive a data packet transmitted by the terminal based on the first data connection.

Here, after the server establishes a first data connection with the terminal for data transmission, data packets are transmitted through the first data connection. In this embodiment of the present application, the first data connection can support both reliable data transmission and unreliable data transmission. When reliable data needs to be sent (such as data during handshake, signaling data after successful handshake, etc.), the data can be encapsulated into data packets of reliable data type; when unreliable data needs to be sent (such as audio and video data, frequently moving coordinate data, etc.), the data can be encapsulated into packets of unreliable data types. Specifically, the data packets of the reliable data type and the data packets of the unreliable data type adopt different packet formats, and the data packets carry a message field used to indicate the data type, and the message field is used to store the data used to indicate the data type. , that is, the data identifiers of data packets of different data types are different.

Here, the data packet of the reliable data type is the data that cannot be discarded strictly required in the transmission process (such as the data during the handshake period, the signaling data after the handshake is successful, etc.), and specifically the data that needs to be transmitted by a reliable transmission method. ; The data packet of the unreliable data category is the data that can be partially discarded during the transmission process (such as audio and video data, frequently moving coordinate data, etc.), specifically the data that needs to be transmitted in an unreliable transmission mode. Here, for the data transmitted by the reliable transmission method, if the receiver does not receive the data due to network jitter or congestion, etc., the sender needs to retransmit the data. Whether the data is received depends on whether the receiver responds with ACK or not. The unreliable transmission method is a transmission method corresponding to the reliable transmission method. The sender of the unreliable transmission method just sends the data regardless of whether the receiver receives the data or not.

Step 103: Analyze the data packet to determine the data type corresponding to the data packet.

Here, after receiving the data packet sent by the terminal based on the first data connection, the server parses the data packet to determine the data type corresponding to the data packet. Therefore, different data processing methods are used for processing data packets of different data types.

In some embodiments, the server may determine the data type corresponding to the data packet by: extracting the packet header part of the data packet; parsing the packet header part to obtain a packet field indicating the data type; The data type is determined as the data type corresponding to the data packet.

In practical applications, the data packets of the reliable data type and the data packets of the unreliable data type use different packet formats, and the data packets carry a message field used to indicate the data type, and the message field is used to store the data used to indicate the data type. Data identifiers of data types, that is, data identifiers of data packets of different data types are different. When the server receives the data packet sent by the terminal, it extracts the packet header part of the data packet, and then parses the packet header part to obtain a message field for indicating the data type, and the message field stores the data identifier for indicating the data type. . At this time, the data type indicated by the data identifier in the message field is determined as the data type corresponding to the received data packet.

Step 104: when it is determined that the data type of the data packet is an unreliable data type, control not to return a reception response message corresponding to the data packet to the terminal.

Based on the above embodiment, when it is determined that the data type of the received data packet is an unreliable data type, the server controls not to return a reception response message corresponding to the data packet to the terminal. Correspondingly, the terminal may send data packets of unreliable data types as long as they are.

When it is determined that the data type of the received data packet is a reliable data type, the server returns a reception response message corresponding to the data packet to the terminal to notify the terminal that the data packet has been received. Correspondingly, if the terminal does not receive a reception response message for the data packet, the terminal resends the data packet to the server.

In some embodiments, when the Internet Protocol address of the terminal is changed, a second data connection with the terminal is established through the first socket interface of the terminal, so as to migrate the data connection with the terminal from the first data connection to the second data connection; wherein the connection identifier of the second data connection is consistent with the connection identifier of the first data connection.

Here, when the IP address of the terminal is changed, for example, when the network type of the terminal is changed from Wi-Fi to cellular network, because the socket interface (ie socket) bound to the original IP address can no longer be used, at this time, Then it is necessary to re-create the corresponding first socket interface for the changed IP address, and bind the re-created first socket interface with the changed IP address, so as to pass the re-created first socket interface. The interface is used for data packet transmission.

Based on this, the terminal can perform data transmission with the server through the re-created first socket interface based on the connection identifier of the first data connection to establish a second data connection; similarly, the server also communicates with the server based on the second data connection. terminal for data transmission. In this way, the data connection between the terminal and the server is migrated from the first data connection to the second data connection.

Here, the connection identifier of the second data connection is consistent with the connection identifier of the first data connection, which ensures that when the IP address changes, data transmission between the terminal and the server can still be performed through the connection identifier, so as to avoid the occurrence of data transmission caused by the change of the IP address. The connection is disconnected. The second data connection and the first data connection are actually multiple network paths corresponding to the data connection established between the terminal and the server. Here, the data connection between the terminal and the server is migrated from the first data connection to the second data connection In fact, through the connection identifier, the data connection between the terminal and the server is migrated from the original network path to the new network path, and the data can be transmitted normally during the data connection migration process, thereby realizing the non-aware switching of IP addresses.

Here, the terminal can determine whether the IP address of the terminal is changed by the following methods: monitor at least one of the data transmission failure event of the original socket interface corresponding to the IP address of the terminal and the change notification message of the IP address; When at least one of the data transmission failure event to the raw socket interface corresponding to the IP address and the change notification message of the IP address, it is determined that the IP address of the terminal has changed.

In practical applications, under each operating system (including Windows/Mac/Android/iOS system), according to the code logic of each operating system, the monitoring of IP address change notification messages can be implemented separately. Therefore, when the terminal monitors the change notification message of the IP address, it is determined that the IP address of the terminal is changed.

In practical applications, a general IP address change monitoring method can also be set for each operating system, that is, monitoring the data transmission failure event of the raw socket interface corresponding to the IP address. When the data transmission failure event of the raw socket interface corresponding to the IP address is monitored, it is determined that the IP address of the terminal has changed. In this way, it is not necessary to implement monitoring of corresponding IP address change notification messages for different operating systems, thereby reducing the complexity of implementation logic and improving efficiency.

In some embodiments, after establishing the second data connection with the terminal, the server may perform path verification on the established second data connection in the following manner: based on the connection identifier, through the second data connection, send information including the first verification information The detection data packet sent by the terminal is sent to the terminal; the response data packet returned by the terminal for the detection data packet is received, and the response data packet includes the second verification information; the first verification information is verified based on the second verification information, and the verification result indicating that the verification is passed is obtained. At the time, data transmission with the terminal is performed based on the second data connection.

In practical applications, after the data connection between the terminal and the server is migrated, that is, after the data connection is migrated from the first data connection to the second data connection, it is necessary to perform path verification on the second data connection, that is, to verify that the data of the second data connection can be verified. reachability. Here, the verification of data reachability is to verify whether the second data connection can support data transmission between the terminal and the server, that is, whether the terminal or the server can receive the data sent by the sender when the terminal or the server is the receiver respectively.

Specifically, based on the connection identifier of the data connection between the terminal and the server, the server may send a probe data packet containing the first verification information to the terminal through the second data connection. In actual implementation, the first verification information is an unpredictable After receiving the probe packet containing the first verification information, the terminal obtains the first verification information contained therein, and carries the first verification information as the second verification information in the response packet for the probe packet and returns to the server. The server receives the response data packet, obtains the second verification information contained in the data packet, and then verifies the second verification information through the first verification information, that is, determines whether the second verification information is consistent with the first verification information; When the second verification information is consistent with the first verification information, a verification result indicating that the verification is passed is obtained, and at this time, it is considered that the data of the second data connection is reachable. In the subsequent data transmission process, data transmission with the terminal is performed based on the second data connection.

In some embodiments, after establishing the second data connection with the terminal, the terminal may perform path verification on the established second data connection in the following manner: after receiving the terminal based on the connection identifier, the data transmitted through the second data connection includes the first Three detection data packets of verification information; send a response data packet for the detection data packet to the terminal, and the response data packet includes fourth verification information; wherein, the fourth verification information is used for the terminal to verify the fourth verification information based on the third verification information The information is verified, and when a verification result indicating that the verification is passed is obtained, data transmission is performed based on the second data connection.

In practical applications, not only the server needs to verify the data reachability of the second data connection, but the terminal also needs to verify the data reachability of the second data connection after the IP address is changed. Specifically, based on the connection identifier of the data connection between the terminal and the server, the terminal sends a probe data packet containing third verification information to the server through the second data connection. In actual implementation, the third verification information is an unpredictable Random value; after receiving the probe packet containing the third verification information, the server obtains the third verification information contained therein, and carries the third verification information as the fourth verification information in the response packet for the probe packet and returns to terminal. The terminal receives the response data packet, obtains the fourth verification information contained in the data packet, and then verifies the fourth verification information through the third verification information, that is, determines whether the fourth verification information is consistent with the third verification information; When the fourth verification information is consistent with the third verification information, a verification result indicating that the verification is passed is obtained, and at this time, it is considered that the data of the second data connection is reachable. In the subsequent data transmission process, data transmission with the terminal is performed based on the second data connection.

In some embodiments, the server also monitors whether the target Internet Protocol address is changed, and obtains a monitoring result, where the target Internet Protocol address belongs to the server that establishes the first data connection with the terminal; when the monitoring result indicates that the target Internet Protocol address is changed When the target Internet Protocol address is changed, a second socket interface is created, and based on the second socket interface, a third data connection with the terminal is established, so as to change the data connection with the terminal from the first data connection Migrating to a third data connection; wherein, the connection identifier of the third data connection is consistent with the connection identifier of the first data connection.

Here, the server may also monitor whether its own IP address, that is, the target Internet Protocol address, has changed, and obtain the monitoring result. When the target IP address of the server changes, the socket interface (ie socket) bound to the original IP address cannot be used. At this time, it is necessary to recreate the corresponding second socket for the changed IP address. word interface, and bind the re-created second socket interface with the changed target IP address, so as to transmit data packets through the re-created second socket interface.

Based on this, the server can perform data transmission with the terminal based on the connection identifier of the first data connection through the re-created second socket interface to establish a third data connection; similarly, the terminal also communicates with the terminal based on the third data connection. server for data transfer. In this way, the data connection between the terminal and the server is migrated from the first data connection to the third data connection.

Here, the connection identifier of the third data connection is consistent with the connection identifier of the first data connection, which ensures that when the IP address changes, data transmission between the terminal and the server can still be performed through the connection identifier, so as to avoid the occurrence of data transmission caused by the change of the IP address. The connection is disconnected. The third data connection and the first data connection are actually multiple network paths corresponding to the data connection established between the terminal and the server. Here, the data connection between the terminal and the server is migrated from the first data connection to the third data connection In fact, through the connection identifier, the data connection between the terminal and the server is migrated from the original network path to the new network path, and the data can be transmitted normally during the data connection migration process, thereby realizing the non-aware switching of IP addresses.

In some embodiments, the server may monitor whether the target Internet Protocol address has changed, and obtain the monitoring result: the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address, and the data transmission failure of the target Internet Protocol address. At least one of the change notification messages is monitored; when at least one of the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address are monitored, a representative target Internet Protocol address is obtained. Changed monitoring results.

In some embodiments, after the server establishes the third data connection with the terminal, the data reachability of the third data connection may be verified in the following manner: based on the connection identifier, the data reachability of the third data connection is verified. After verification, a verification result is obtained; when the verification result indicates that the data of the third data connection is reachable, data transmission with the terminal is performed based on the third data connection.

In practical applications, after the data connection between the terminal and the server is migrated, that is, after the data connection is migrated from the first data connection to the third data connection, it is necessary to perform path verification on the third data connection, that is, to verify that the data of the third data connection can be verified. reachability. Here, the verification of data reachability is to verify whether the third data connection can support data transmission between the terminal and the server, that is, whether the terminal or the server can receive the data sent by the sender when the terminal or the server is respectively the receiver. Specifically, the path verification method of the third data connection may also adopt the path verification method of the second data connection, which will not be repeated in the embodiments of the present application.

By applying the above embodiments of the present application, a first data connection for data transmission with the terminal is created, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is transmitted based on the first data connection, the data packet is parsed to determine the data type corresponding to the data packet; when it is determined that the data type of the data packet is an unreliable data type, the control is not to return the corresponding data type to the terminal. Packet receive response message. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

The following continues to describe the data transmission method provided by the embodiments of the present application. In some embodiments, the data transmission method provided by the embodiments of the present application may be implemented by the server or the terminal alone, or by the server and the terminal in cooperation. The data transmission method provided by the embodiments of the present application is described below by taking the terminal implementation as an example. Referring to FIG. 3B , FIG. 3B is a schematic flowchart of a data transmission method provided by an embodiment of the present application. The data transmission method provided by an embodiment of the present application includes:

Step 201: The terminal creates a first data connection with the server for data transmission.

The connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the server changes.

Here, before the terminal performs data communication with the server, a first data connection for data transmission between the server and the terminal may be created in advance. After the first data connection is created, the server and the terminal send and receive data packets through the first data connection. In practical applications, the terminal may be provided with an application client, such as a conference client, a learning client, etc., and the server may be a background server of the corresponding application client.

In the embodiment of the present application, the connection identifier of the first data connection remains unchanged when the Internet Protocol address (that is, the IP address) or the port of any one of the terminal and the server is changed, that is, the connection between the terminal and the server is changed. When the IP address or port changes, the data channel between the terminal and the server will not be interrupted, and both parties can transmit data packets based on the connection identifier of the first data connection. In this way, when the IP address of the terminal or server is changed, it does not affect the data transmission between the two parties, and for the user, the change of the IP address is insensitive, and there will be no network disconnection, need to reconnect, etc. Happening.

In practical applications, the first data connection is established based on the QUIC protocol, and the connection identifier of the QUIC connection is a 64-bit connection ID. When the address or port (Port) changes, the connection ID in the QUIC connection remains unchanged, and both the terminal and the server can still transmit data packets based on the connection identifier of the QUIC connection, so there is no need to re-create the connection through the protocol handshake and other processes. In this way, QUIC connection migration can achieve the technical effect of network type switching without user perception.

Step 202: Based on the first data connection, send a data packet to the server.

The data type of the data packet includes an unreliable data type, and the unreliable data type is used to control not to return a reception response message corresponding to the data packet when the server determines that the data type of the data packet is an unreliable data type.

After the first data connection between the terminal and the server is established, the terminal sends a data packet to the server through the first data connection. In this embodiment of the present application, the first data connection can support both reliable data transmission and unreliable data transmission. When reliable data needs to be sent (such as data during handshake, signaling data after successful handshake, etc.), the data can be encapsulated into data packets of reliable data type; when unreliable data needs to be sent (such as audio and video data, frequently moving coordinate data, etc.), the data can be encapsulated into packets of unreliable data types. Specifically, the data packets of the reliable data type and the data packets of the unreliable data type adopt different packet formats, and the data packets carry a message field used to indicate the data type, and the message field is used to store the data used to indicate the data type. , that is, the data identifiers of data packets of different data types are different.

Here, the data packet of the reliable data type is the data that cannot be discarded strictly required in the transmission process (such as the data during the handshake period, the signaling data after the handshake is successful, etc.), and specifically the data that needs to be transmitted by a reliable transmission method. ; The data packets of the unreliable data category are the data that can be partially discarded during the transmission process (such as audio and video data, frequently moving coordinate data, etc.), specifically the data that needs to be transmitted in an unreliable transmission mode. Here, for the data transmitted by the reliable transmission method, if the receiver does not receive the data due to network jitter or congestion, etc., the sender needs to retransmit the data. Whether the data is received depends on whether the receiver responds with ACK or not. The unreliable transmission method is a transmission method corresponding to the reliable transmission method. The sender of the unreliable transmission method just sends the data regardless of whether the receiver receives the data or not.

After receiving the data packet sent by the terminal based on the first data connection, the server parses the data packet to determine the data type corresponding to the data packet. Therefore, different data processing methods are used for processing data packets of different data types. When it is determined that the data type of the received data packet is an unreliable data type, the server controls not to return a reception response message corresponding to the data packet to the terminal. Correspondingly, the terminal may send data packets of unreliable data types as long as they are.

When it is determined that the data type of the received data packet is a reliable data type, the server returns a reception response message corresponding to the data packet to the terminal to notify the terminal that the data packet has been received. Correspondingly, if the terminal does not receive a reception response message for the data packet, the terminal resends the data packet to the server.

By applying the above embodiments of the present application, a first data connection for data transmission with the terminal is created, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is transmitted based on the first data connection, the data packet is parsed to determine the data type corresponding to the data packet; when it is determined that the data type of the data packet is an unreliable data type, the control is not to return the corresponding data type to the terminal. Packet receive response message. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

Next, the data transmission method provided by the embodiment of the present application will be described. The data transmission method provided by the embodiment of the present application may be implemented by the terminal and the server in cooperation. Referring to FIG. 4, FIG. 4 is a schematic flowchart of a data transmission method provided by an embodiment of the present application. The data transmission method provided by an embodiment of the present application includes:

Step 301: The terminal and the server establish a first data connection for data transmission.

Step 302: The terminal sends a data packet to the server based on the first data connection.

Step 303: The server receives the data packet transmitted by the terminal based on the first data connection, parses the data packet, and determines the data type corresponding to the data packet.

Step 304: Determine whether the data type corresponding to the data packet is an unreliable data type, if not, go to Step 305; if yes, go to Step 306.

Step 305: Return a reception response message corresponding to the data packet to the terminal.

Step 306: Control not to return a reception response message corresponding to the data packet to the terminal.

Step 307: The terminal receives a reception response message corresponding to the data packet.

By applying the above embodiments of the present application, a first data connection for data transmission with the terminal is created, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is transmitted based on the first data connection, the data packet is parsed to determine the data type corresponding to the data packet; when it is determined that the data type of the data packet is an unreliable data type, the control is not to return the corresponding data type to the terminal. Packet receive response message. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

An exemplary application of the embodiments of the present application in a practical application scenario will be described below.

Next, before describing the data transmission method provided by the embodiment of the present application, the method for creating a persistent connection for data transmission provided by the embodiment of the present application is first described. As shown in FIG. 5 , FIG. 5 is a schematic flowchart of a method for creating a persistent connection for data transmission provided by an embodiment of the present application, including:

Step 401: The client sends a SYN handshake signal to the server.

Step 402: The server returns a response signal SYN+ACK to the client to indicate that the SYN handshake signal is received.

Step 403: The client sends an ACK response signal to the server to establish a TCP connection with the server.

Here, in practical applications, the client can be a conference client, and the user can install and run the client through the terminal to implement corresponding client functions. As an example, referring to FIG. 6, FIG. 6 is a schematic diagram of an application of a client provided by an embodiment of the present application. Here, the client is a conference client, including functional scenarios such as booking a conference, joining a conference, and turning on a camera and a microphone during the conference. In each scenario, the client and the server need to establish a long connection for data interaction and transmission. Therefore, the client needs to establish a long connection with the server, and in this embodiment of the present application, the long connection can be realized by jointly establishing TCP+TLS+XMPP, wherein the above steps 401-403 are the handshake process of the TCP protocol. After steps 401-403, a TCP connection is established between the client and the server.

Specifically, referring to FIG. 7 , FIG. 7 is a schematic flowchart of the establishment of a TCP connection provided by an embodiment of the present application, including:

Step 501: The client sends a SYN handshake signal to the server; Step 502: The server returns a response signal SYN+ACK to the client to indicate that the SYN handshake signal is received; Step 503: The client sends an ACK response signal to the server to establish a connection with the server Step 504: The client sends application data (Application Data) to the server; Step 505: The server returns the application data (Application Data) to the client. In this way, data transmission based on a TCP connection is realized.

Step 404: The client sends a query packet (XMPP Stream Start) to the server to request the stream feature field of the server.

Here, after a TCP connection is established between the client and the server, the XMPP handshake process begins.

Step 405: The server returns a response data packet ACK carrying the session ID.

Here, the session ID is an identifier allocated by the server to the client for this session.

Step 406: The server delivers the feature field Server Feature (TLS) to the client.

Step 407: The client sends a handshake request (TLS start) of the TLS handshake to the server.

Step 408: The server sends the response information ACK of the handshake request for the TLS handshake to the client.

Step 409: The client sends a client query data packet Client Hello to the server.

Here, the Client Hello data packet carries information such as the random number random of the client, the cipher suite ciphers, and the available protocol version number.

Step 410: The server returns the server query data packet Server Hello to the client.

Here, the Server Hello data packet carries information such as random number random, cipher suite ciphers, and certificate cert of the server.

Step 411: The client sends a client query end packet Client Hello Finish to the server.

Step 412: The server returns the server query end packet Server Hello Finish to the client.

Here, a standard TLS handshake is performed between the client and the server, and after the handshake is completed, a TLS connection is established to implement TLS encryption of the channel.

Specifically, referring to FIG. 8, FIG. 8 is a schematic diagram of a TLS connection establishment process provided by an embodiment of the present application, including: Step 601: the client sends a client query data packet Client Hello to the server; Step 602: the server returns a server query The data packet Server Hello is sent to the client; Step 603: The client sends the client query end packet ClientHello Finish to the server; Step 604: The server returns the server query end packet Server HelloFinish to the client; Step 605: The client sends the application data to the server; Step 606: the server returns the application data to the client. In this way, data encryption transmission based on TLS connection is implemented to ensure data security.

Step 413: The client sends a query data packet Stream Request to the server, so as to request the server to deliver the stream feature field and perform SASL authentication.

Step 414: The server sends a response packet ACK containing the flow flag to the client.

Step 415: The server sends a stream feature field Server Feature (SASL) to the client, and carries the supported SASL encryption mode.

Step 416: The client selects an encryption method, and sends a SASL verification start packet (SASL challenge start) carrying user information to the server.

Here, in practical applications, the client selects the PLAIN encryption method from the supported SASL encryption methods.

Step 417: The server sends a SASL verification end packet (SA SLchallenge end) for the received packet to the client.

Here, the authentication of the server against SASL is successful.

Step 418: The client sends an initial stream Stream Request to the server.

Step 419: The server sends a stream flag to the client as a response packet ACK.

Step 420: The server responds and returns the supported stream feature field Server Feature to indicate that the client needs to start the bind resource process.

Step 421: The client sends a Bind Rosource Request to the server.

Step 422: The server judges and returns the binding resource result Bind Resource Response to the client.

Step 423: The client sends Application Data to the server.

Step 424: The server returns Application Data to the client.

In this way, the above-mentioned persistent connection for data transmission is based on the TCP+TLS protocol and the persistent connection communication technology. Among them, the TCP protocol provides a reliable transmission channel, and the TLS encryption protocol provides a security guarantee for the channel. However, with regard to the above-mentioned method for creating a long connection for data transmission provided by the embodiment of the present application, the applicant further analyzes and finds that, as can be seen from FIG. 7 and FIG. 8 , before the data communication is officially started, it takes 1.5 RTTs for TCP to establish a connection , 2 RTTs are required to complete the TLS encryption of the channel, and a total of 11 RTTs are required to establish a long connection for data transmission (ie, a long connection between the client and the server) based on the above process.

Statistics show that under normal network conditions, only 69.9% of users can complete the handshake process within 1s and start other conference functions on the client side. During the whole handshake process, considering the user experience, the connection establishment timeout is 30s. Among all the users who failed to log in, 41.53% of the users failed to log in because the connection establishment timed out. Because the RTT is large in the case of weak network, if the connection establishment process is complicated, it will inevitably lead to more time consuming to complete the handshake and timeout. Therefore, simplifying the handshake process, reducing the login time, and improving the login success rate and weak network resistance are urgent problems to be solved.

Moreover, the current persistent connection between the client and the server is based on the TCP protocol, and the TCP protocol uses a four-tuple (source IP address, destination IP address, source port and destination port) to identify a persistent connection. When the user equipment network switches between wifi and cellular, the source IP address will change, so the TCP protocol connection cannot support seamless switching between wifi and cellular, which means that once the user switches the network, the entire long connection must be disconnected Reconnect, otherwise the data cannot continue to be transmitted, which means that on the client side, there will be a disconnection and reconnection situation such as "the network is unstable and the connection is in progress", see Figure 9, Figure 9 is the Internet Protocol address change provided by the embodiment of this application Schematic diagram of the client's performance. During the long connection disconnection and reconnection period, all command data cannot be sent and received. Due to the daily use of elevators, etc., or the occasional poor WiFi signal, it is very common for WiFi and cellular to frequently switch to each other. It needs to be disconnected and reconnected every time, which will greatly affect the user experience.

Based on this, an embodiment of the present application further provides a method for creating a persistent connection for data transmission, where the method for creating a persistent connection for data transmission is established based on the QUIC protocol. Next, the establishment process of the QUIC connection provided by this application will be described first. As shown in FIG. 10, FIG. 10 is a schematic diagram of the establishment process of the QUIC connection provided by the embodiment of this application, including:

Step 701: The client sends an initial query data packet Inchoate Client Hello to the server.

Step 702: The server returns the Inchoate Client Hello response data packet Rejection to the client for the initial query data packet.

Step 703: The client sends a complete query data packet Complete Client Hello to the server.

Here, the Complete Client Hello can carry the encrypted information of the client and send it to the server together with the encrypted application data Encript Application Data, which means that the operations of QUIC handshake and data encryption are completed within one RTT.

Step 704: The server returns the encrypted application data Encript Application Data based on Complete Client Hello.

As shown in Figure 10, it can be seen that when the QUIC connection is established, only 1 RTT is required. After the client receives the Rejection for the query packet sent by the server, it will bring the encrypted information of the client when sending the packet next time, and communicate with it. The application data is sent to the server together to complete the QUI C handshake and data encryption operations in one RTT, which saves 2.5 RTTs compared to TCP+TLS.

In this way, the persistent connection between the conference client and the server can be implemented based on the QUIC protocol. Referring to FIG. 11 , FIG. 11 is a schematic flowchart of a method for creating a persistent connection for data transmission provided by an embodiment of the present application, including:

Step 801: The client sends an initial query data packet Inchoate Client Hello to the server.

Step 802: The server returns the Inchoate Client Hello response data packet Rejection to the client.

Step 803: The client sends an inquiry data packet to the server to request the flow characteristic field of the server; and at the same time sends a complete inquiry data packet Complete Client Hello to the server.

Step 804: The server returns a response data packet ACK carrying the session ID; at the same time, the encrypted application data Encript Application Data is returned based on Complete ClientHello.

Step 805: The client sends a query data packet Stream Request to the server to request the stream feature field of the server.

Step 806: The server sends a flow flag as a response packet ACK to the client.

Step 807: The server sends the stream feature field Server Feature (SASL) to the client, and carries the supported SASL encryption mode.

Step 808: The client selects an encryption method, and sends a SASL verification start packet (SASL challenge start) carrying user information to the server.

Here, in practical applications, the client selects the PLAIN encryption method from the supported SASL encryption methods.

Step 809: The server sends a SASL verification end packet (SA SLchallenge end) for the received packet to the client.

Here, the authentication of the server against SASL is successful.

Step 810: The client sends an initial stream Stream Request to the server.

Step 811: The server sends a flow flag to the client as a response packet ACK.

Step 812: The server responds and returns the supported stream feature field, Server Feature, to indicate that the client needs to start the bind resource process.

Step 813: The client sends a Bind Rosource Request to the server.

Step 814: The server judges and returns the binding resource result Bind Resource Response to the client.

Step 815: The client sends Application Data to the server.

Step 816: The server returns Application Data to the client.

It can be seen that the process of establishing a long-term connection with the introduction of the QUIC protocol has been reduced to 7 RTTs, which is 4 RTTs less than the process of establishing a long-term connection shown in Figure 5 above. 36% reduction.

At the same time, since the QUIC protocol uses the connection ID (ConnectionID) to uniquely identify a connection, when the client source IP address changes (such as when the network switches between wifi and cellular), the connection ID of the long connection based on the QUIC protocol Unchanged, thus keeping the data channel between client and server constant. Specifically, referring to FIG. 12, FIG. 12 is a schematic flowchart of connection migration of a data connection provided by an embodiment of the present application, including:

Step 901: The client establishes a first socket interface socket for IP1, and binds the first socket interface socket with IP1.

Step 902: The client sends an Application Data Request to the server.

Step 903: The server returns an application data response Application DataResponse to the application data request to the client.

Step 904: The client monitors the network state change notify, and changes from IP1 to IP2.

Step 905: The client establishes a second socket interface socket for IP2, and binds the second socket interface socket with IP2.

Here, when the client's network switches between wifi and cellular, the client will receive the system's network status change notification. At this time, IP1 is changed to IP2, and the first socket interface socket bound to the original IP1 can no longer continue. communication. Therefore, it is necessary to create a new socket and bind the changed IP2 to continue to send and receive network data packets. At the same time, it also retransmits the failed data packets in the socket buffer of the first socket interface, so as to complete the client and server. Migration of network channels between data connections. In practical applications, under each operating system (including Windows/Mac/Android/iOS system), according to the code logic of each operating system, the monitoring of the network state change notification of the IP address can be realized respectively. Therefore, when the client monitors the network state change notification of the IP address, it is determined that the IP address of the client has changed, so that a new socket is created in time to complete the migration of the data connection.

Step 906: Implement connection migration of the data connection based on the second socket interface socket.

Step 907: The client retransmits the failed data packets in the socket buffer of the first socket interface.

Step 908: The server returns an application data response to the client.

Further, referring to FIG. 13, FIG. 13 is a schematic flowchart of connection migration provided by an embodiment of the present application, including:

Step 1001: The client establishes a first socket interface socket for IP1, and binds the first socket interface socket with IP1.

Step 1002: The client sends an Application Data Request to the server.

Step 1003: The server returns an application data response Application Data Response to the application data request to the client.

Step 1004: The client sends an application data request to the server.

At this point, the client's network switches between wifi and cellular, and changes from IP1 to IP2.

Step 1005: The server returns the application data response sending failure, and the client listens to the socket read failure event.

Step 1006: The client establishes a second socket interface socket for IP2, and binds the second socket interface socket with IP2.

Step 1007: The connection migration of the data connection is implemented based on the second socket interface socket.

Step 1008: The client retransmits the failed data packets in the socket buffer of the first socket interface.

Step 1009: The server returns an application data response to the client.

Here, the client no longer monitors the network status change notification of the physical network of the operating system, but monitors the socket read and write failure events, thereby judging whether it is currently necessary to rebuild the socket and bind a new ip for network data transmission. . In this way, it is not necessary to monitor the physical network changes of the four platforms (Windows/Mac/Android/iOS) separately, but also can successfully monitor the socket read and write failure caused by network switching, and establish a new transmission channel in time to complete the connection migration.

Continuing, after the connection between the client and the server is migrated, it is also necessary to perform data reachability verification on the migrated network path. Referring to FIG. 14, FIG. 14 is a schematic flowchart of a path verification provided by an embodiment of the present application, including:

Step 1101 : Before connection migration, the client uses a non-probing packet (Non-probing Packet) to communicate with the server through IP1.

Here, a non-probing packet (Non-probing Packet) is a data packet related to the transmitted application data.

Step 1102: The IP of the client becomes IP2, and the client sends a Probing Packet containing a path verification frame PATH_CHALLENGE frame to the server, and the PATH_CHALLENGE frame contains an unpredictable random value.

Here, when the IP address of the client is changed and the connection migration is completed, the client starts path verification on the new network path after the migration to verify the data reachability (ie reachability) of the new network path.

Step 1103: The server receives the probe packet including the PATH_CHALLENGE frame sent by the client, returns a Probing Packet to the client, and carries the random value received through the PATH_CHALLENGE in the PATH_RESPONSE frame included in the response probe packet.

Here, the client receives the response detection packet containing PATH_RESPONSE, and verifies whether the random value in the data body payload of the response detection packet is consistent with the random value of the PATH_CHALLENGE frame. If they are consistent, the data representing the path is reachable.

Step 1104: The server sends a Probing Packet containing a PATH_CHALLENGE frame to the client, and the PATH_CHALLENGE frame contains an unpredictable random value.

Here, the server also needs to send a PATH_CHALLENGE frame to verify the path of the client.

Step 1105: The client receives the probe packet including the PATH_CHALLENGE frame sent by the client, returns a response probe packet (Probing Packet) to the server, and carries the random value received through the PATH_CHALLENGE in the PATH_RESPONSE frame included in the response probe packet.

Here, the server receives the response probe packet containing PATH_RESPONSE, and verifies whether the random value in the data body payload of the response probe packet is consistent with the random value of the PATH_CHALLENGE frame. If they are consistent, the data representing the path is reachable.

Step 1106 : After the connection is migrated, the client uses a non-probing packet (Non-probing Packet) to communicate with the server through IP2.

It can be seen that the long connection based on the QUIC protocol can achieve connection migration when the IP address changes, that is, to achieve seamless switching between network wifi and cellular without having to re-establish the connection. In practical applications, if a network switching scenario occurs during the user's use of the conference client, audio and video data and network operations such as switching the microphone/camera can be directly resumed, and the user is completely unaware, which improves the user experience.

After the description of the method for creating a persistent connection for data transmission provided by the embodiment of the present application is completed, the data transmission method provided by the embodiment of the present application is described next. In this embodiment of the present application, the data transmission method is implemented based on the persistent connection of the QUIC protocol.

In the related art, for signaling and other data that cannot be discarded, reliable transmission is used for transmission; while for other unreliable data that can be partially discarded (such as volume display data, frequently moving coordinate data, etc.), The same channel is also used for reliable data multiplexing for reliable transmission; then when the network is poor, the retransmission strategy of the reliable transmission channel will bring greater pressure to the network, and will affect the normal transmission of reliable data such as signaling. If another unreliable channel, such as a UDP channel, is specially established for this kind of unreliable data, the client and the server need to maintain the states of the two channels at the same time, which leads to an increase in the handshake delay of the new channel, and the implementation logic is complex and maintenance. high cost.

Based on this, an embodiment of the present application provides a data transmission method, which establishes a data connection between a terminal and a server (ie, a client and a server) based on the QUIC protocol, and uses the same data connection channel to perform reliable transmission and unreliable transmission at the same time. Specifically, in this embodiment of the present application, the data connection between the client and the server can support both reliable data transmission and unreliable data transmission. When reliable data needs to be sent (such as data during the handshake period, signaling data after a successful handshake, including switch operation instructions for cameras and microphones during the conference, etc.), the data can be encapsulated into data packets of reliable data types; When there is unreliable data (such as volume display data, frequently moving coordinate data, etc.), the data can be encapsulated into data packets of unreliable data type. Specifically, the data packets of the reliable data type and the data packets of the unreliable data type adopt different packet formats, and the data packets carry the identifier used to indicate the data type (including the reliable data type and the unreliable data type), that is, the reliable data The identification of the type of data packet is different from the identification of the data type-independent packet. As shown in FIG. 15 , FIG. 15 is a schematic diagram of a reliable frame format and an unreliable frame format provided by an embodiment of the present application, wherein picture A in FIG. 15 is a reliable frame format, and picture B in FIG. 15 is an unreliable frame format.

Here, the data packet of the reliable data type is the data that cannot be discarded strictly required in the transmission process (such as the data during the handshake period, the signaling data after the handshake is successful, etc.), and specifically the data that needs to be transmitted by a reliable transmission method. ; The data packets of the unreliable data category are data that can be partially discarded during the transmission process (such as volume display data, frequently moving coordinate data, etc.), specifically the data that needs to be transmitted in an unreliable transmission mode. Here, for the data transmitted by the reliable transmission method, if the receiver does not receive the data due to network jitter or congestion, etc., the sender needs to retransmit the data. Whether the data is received depends on whether the receiver responds with ACK or not. The unreliable transmission method is a transmission method corresponding to the reliable transmission method. The sender of the unreliable transmission method just sends the data regardless of whether the receiver receives the data or not.

Specifically, when the server determines that the data type of the received data packet is an unreliable data type, the server does not return a reception response message corresponding to the data packet to the terminal. Correspondingly, the terminal may send data packets of unreliable data types as long as they are. When the server determines that the data type of the received data packet is a reliable data type, the server returns a reception response message corresponding to the data packet to the terminal to notify the terminal that the data packet has been received. Correspondingly, if the terminal does not receive a reception response message for the data packet, the terminal resends the data packet to the server.

Taking remote control as an example, see FIG. 16 . FIG. 16 is a schematic flowchart of data transmission applied to remote control provided by an embodiment of the present application, including:

Step 1201: Both the first client and the second client establish a QUIC long connection with the server.

Here, the first client corresponds to user A, and the second client corresponds to user B. The QUIC long connection may be jointly established based on the QUIC protocol and the XMPP protocol.

Step 1202: The first client sends a Remote Control Request to the server.

Here, the first client uses the QUIC long connection to send the remote control request signaling, which carries the identification information of the destination user B, and requests to enable the remote control service to remotely control the second client of user B.

Step 1203: The server returns ACK to receive the response information to the first client.

Step 1204: The server sends the remote control request of the first client to the second client through remote control push information RemoteControl Push.

Step 1205: The second client returns a first remote control response to the server, where the first remote control response carries a notification message of refusing to accept the remote control.

Step 1206: The server sends a remote control response message to the first client to notify the first client that the remote control connection fails.

Step 1207: The second client returns a second remote control response to the server, where the second remote control response carries a notification message of agreeing to accept the remote control.

Step 1208: The server sends a remote control response message to the first client to notify the first client that the remote control connection is successful.

Here, the remote control response message carries an authentication token, which is used for subsequent specific instruction control data authentication.

Step 1209: The first client sends a remote control start request to the server to request to start the remote control.

Step 1210: The server sends a remote control start request to the second client.

Step 1211: Return a remote control start response message with a successful instruction delivery to the first client.

Here, the server receives the remote control start signaling from the first client, sends a push command to start remote control to the destination user B through the persistent connection channel, and then sends a notification message of success to user A by returning the packet instruction.

Step 1212: The first client terminal intercepts mouse and keyboard operations after receiving the remote control start response message that the instruction is issued successfully.

Step 1213: The second client receives the remote control start request, and intercepts mouse and keyboard operations.

Step 1214: The first client encapsulates the control command data into an unreliable data packet, and sends it to the server through the QUIC long connection channel, carrying the authentication token and destination user information at the same time.

Step 1215: The server forwards the control command data to the second client through the QUIC persistent connection channel.

Here, the control instruction data may include mouse coordinates, mouse operation instructions, keyboard operation instructions, and the like. However, these data do not need to be guaranteed to be 100% reliable. For example, during the mouse movement process, even if the current network status is poor, some coordinate information is lost, as long as the coordinates of the movement stop are sent successfully, or by re-operating, re-sending, remote control can also succeed. Therefore, the control command data in the remote control can be encapsulated into unreliable data packets, and transmitted through the established QUIC long connection that supports both reliable transmission and unreliable transmission.

Here, the data of the unreliable data type also includes the picture-in-picture mode of the conference client (that is, the screen sharing is turned on and the camera is turned on at the same time, and the camera picture can be placed in the window, as shown in FIG. 17A , which is a picture provided by an embodiment of the present application. The data involved in the schematic diagram of the medium picture mode), such as any place specified by the user, that is, the user can adjust the size of the camera screen, drag the screen position, the coordinates and size data of the screen, and this type of data can also be transmitted through unreliable transmission methods. of unreliable data. In addition, there is volume data in the conference client, that is, display data indicating the volume of the user's voice (as shown in FIG. 17B , which is a schematic diagram of the volume display provided by the embodiment of the present application), and the amount of these data is relatively large, and When the network is poor, losing some will not have much impact, and this type of data can also be transmitted through unreliable transmission methods.

By applying the above embodiments of the present application, by introducing the QUIC protocol into the process of establishing a long connection between the client and the server, and utilizing the fast handshake and channel encryption characteristics and connection migration characteristics of QUIC, a great optimization effect is achieved. As shown in FIG. 18, FIG. 18 is a schematic diagram of the optimization of client indicators provided by the embodiment of the present application. Here, establishing a long connection based on TCP+TLS+XMPP is compared with establishing a long connection based on QUIC+XMPP, as shown in Figure 18 A As shown in the figure, the login time was successfully reduced. According to online data statistics, the average login time was reduced from 1224ms to 555ms, and the optimization effect reached 54.6%. As shown in Figure B in Figure 18, the timeout occurred due to the high login time. The problem has also been optimized, and the login success rate has increased from 99.89% to 99.98%, an increase of 0.09%; as shown in Figure C in Figure 18, the success rate of switching the microphone in the conference client has increased from 98.59% to 99.84%, and the optimization effect has reached 1.26 %.

The following continues to describe the data transmission apparatus 555 provided by the embodiments of the present application. In some embodiments, the data transmission apparatus may be implemented in the form of a software module. Referring to FIG. 19, FIG. 19 is a schematic structural diagram of a data transmission device 555 provided by an embodiment of the present application. The data transmission device 555 provided by an embodiment of the present application includes:

The creation module 5551 is used to create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes;

a receiving module 5552, configured to receive a data packet transmitted by the terminal based on the first data connection;

A parsing module 5553, configured to parse the data packet to determine the data type corresponding to the data packet;

The control module 5554 is configured to control not to return a reception response message corresponding to the data packet to the terminal when it is determined that the data type of the data packet is an unreliable data type.

In some embodiments, the apparatus further includes:

a connection state control module, configured to obtain a heartbeat packet sending cycle, and send a heartbeat packet to the terminal through the first data connection according to the heartbeat packet sending cycle;

When the heartbeat response information for the heartbeat packet is received, the connection state corresponding to the first data connection is controlled to be an active state.

In some embodiments, when the first data connection is established for the first time, the creation module 5551 is further configured to receive a first inquiry data packet sent by the terminal for requesting to establish a data connection;

based on the first inquiry data packet, sending a corresponding response data packet to the terminal;

When receiving the second inquiry data packet sent by the terminal, a first data connection for data transmission with the terminal is established.

In some embodiments, when the first data connection is not established for the first time, the creation module 5551 is further configured to receive an inquiry data packet sent by the terminal for requesting to establish a data connection;

Based on the inquiry data packet, a first data connection for data transmission with the terminal is established.

In some embodiments, the parsing module 5553 is further configured to extract the header part of the data packet;

The packet header part is parsed to obtain a message field for indicating the data type;

The data type indicated by the packet field is determined as the data type corresponding to the data packet.

In some embodiments, the apparatus further includes:

The first migration module is configured to establish a second data connection with the terminal through the first socket interface of the terminal when the Internet Protocol address of the terminal is changed, so as to connect the terminal with the terminal. migrating the data connection from the first data connection to the second data connection;

Wherein, the connection identifier of the second data connection is consistent with the connection identifier of the first data connection.

In some embodiments, the first migration module is further configured to send a probe data packet including the first verification information to the terminal through the second data connection based on the connection identifier;

receiving a response data packet returned by the terminal for the probe data packet, where the response data packet includes second verification information;

The first verification information is verified based on the second verification information, and when a verification result indicating that the verification is passed is obtained, data transmission with the terminal is performed based on the second data connection.

In some embodiments, the first migration module is further configured to receive a probe data packet including third verification information transmitted by the terminal through the second data connection based on the connection identifier;

sending a response data packet to the terminal for the probe data packet, where the response data packet includes fourth verification information;

The fourth verification information is used for the terminal to verify the fourth verification information based on the third verification information, and when a verification result indicating that the verification is passed is obtained, the verification is performed based on the second data connection. data transmission.

In some embodiments, the apparatus further includes:

A second migration module, configured to monitor whether the target Internet Protocol address is changed, and obtain a monitoring result, where the target Internet Protocol address belongs to the server that establishes the first data connection with the terminal;

When the monitoring result indicates that the target Internet Protocol address is changed, create a second socket interface for the changed target Internet Protocol address, and

establishing a third data connection with the terminal based on the second socket interface, so as to migrate the data connection with the terminal from the first data connection to the third data connection;

Wherein, the connection identifier of the third data connection is consistent with the connection identifier of the first data connection.

In some embodiments, the second migration module is further configured to respond to at least one of the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address a monitoring;

When at least one of the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address are monitored, a monitoring indicating that the target Internet Protocol address is changed is obtained. result.

In some embodiments, the second migration module is further configured to verify the data reachability of the third data connection based on the connection identifier to obtain a verification result;

When the verification result indicates that the data of the third data connection is reachable, perform data transmission with the terminal based on the third data connection.

By applying the above embodiments of the present application, a first data connection for data transmission with the terminal is created, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is transmitted based on the first data connection, the data packet is parsed to determine the data type corresponding to the data packet; when it is determined that the data type of the data packet is an unreliable data type, the control is not to return the corresponding data type to the terminal. Packet receive response message. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

The following continues to describe the data transmission device 2000 provided by the embodiment of the present application. Referring to FIG. 20, FIG. 20 is a schematic structural diagram of the data transmission device 2000 provided by the embodiment of the present application. The data transmission device 2000 provided by the embodiment of the present application includes:

A connection creation module 2010, configured to create a first data connection with the server for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the server changes;

a sending module 2020, configured to send a data packet to the server based on the first data connection;

The data type of the data packet includes an unreliable data type, and the unreliable data type is used to control not to return the corresponding data when the server determines that the data type of the data packet is an unreliable data type Packet receive response message.

By applying the above embodiments of the present application, a first data connection for data transmission with the terminal is created, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; When the data packet is transmitted based on the first data connection, the data packet is parsed to determine the data type corresponding to the data packet; when it is determined that the data type of the data packet is an unreliable data type, the control is not to return the corresponding data type to the terminal. Packet receive response message. In this way, by analyzing the data type of the data packet, for the data packet of the unreliable data type, the corresponding reception response message is not returned, thereby avoiding the situation that the terminal retransmits the data packet of the unreliable data type and reducing unnecessary network resources. Occupy, improve the utilization of network resources.

The embodiment of the present application also provides an electronic device, the electronic device includes:

memory for storing executable instructions;

The processor is configured to implement the data transmission method provided by the embodiment of the present application when executing the executable instructions stored in the memory.

Embodiments of the present application also provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the data transmission method provided by the embodiment of the present application.

Embodiments of the present application further provide a computer-readable storage medium storing executable instructions, and when the executable instructions are executed by a processor, the data transmission method provided by the embodiments of the present application is implemented.

In some embodiments, the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories of various equipment.

In some embodiments, executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and which Deployment may be in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

As an example, executable instructions may, but do not necessarily correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, in a Hyper Text Markup Language (HTML) document One or more scripts of a , stored in a single file dedicated to the program in question, or in multiple cooperating files (eg, files that store one or more modules, subroutines, or code sections).

As an example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or alternatively, distributed across multiple sites and interconnected by a communication network execute on.

The above descriptions are merely examples of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent substitutions and improvements made within the spirit and scope of this application are included within the protection scope of this application.

Claims (15)

1. a data transmission method, is characterized in that, described method comprises: Create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; receiving a data packet transmitted by the terminal based on the first data connection; Analyzing the data packet to determine the data type corresponding to the data packet; When it is determined that the data type of the data packet is an unreliable data type, the control does not return a reception response message corresponding to the data packet to the terminal. 2. The method according to claim 1, wherein after the first data connection for data transmission with the terminal is established, the method further comprises: Obtain the heartbeat packet sending period, and send the heartbeat packet to the terminal through the first data connection according to the heartbeat packet sending period; When the heartbeat response information for the heartbeat packet is received, the connection state corresponding to the first data connection is controlled to be an active state. 3. The method according to claim 1, wherein when the first data connection is established for the first time, the creating a first data connection with the terminal for data transmission comprises: receiving a first inquiry data packet sent by the terminal and requesting to establish a data connection; based on the first inquiry data packet, sending a corresponding response data packet to the terminal; When receiving the second inquiry data packet sent by the terminal, a first data connection for data transmission with the terminal is established. 4. The method according to claim 1, wherein when the first data connection is not established for the first time, the creating a first data connection with the terminal for data transmission comprises: receiving an inquiry data packet sent by the terminal for requesting to establish a data connection; Based on the inquiry data packet, a first data connection for data transmission with the terminal is established. 5. The method according to claim 1, wherein the analyzing the data packet to determine the data type corresponding to the data packet comprises: extracting the header part of the data packet; The packet header part is parsed to obtain a message field for indicating the data type; The data type indicated by the packet field is determined as the data type corresponding to the data packet. 6. The method of claim 1, wherein the method further comprises: When the Internet Protocol address of the terminal is changed, a second data connection with the terminal is established through the first socket interface of the terminal, so as to transfer the data connection with the terminal from the first socket interface to the terminal. A data connection is migrated to the second data connection; Wherein, the connection identifier of the second data connection is consistent with the connection identifier of the first data connection. 7. The method according to claim 6, wherein after establishing the second data connection with the terminal, the method further comprises: Based on the connection identifier, send a probe data packet including the first verification information to the terminal through the second data connection; receiving a response data packet returned by the terminal for the probe data packet, where the response data packet includes second verification information; The first verification information is verified based on the second verification information, and when a verification result indicating that the verification is passed is obtained, data transmission with the terminal is performed based on the second data connection. 8. The method according to claim 6, wherein after establishing the second data connection with the terminal, the method further comprises: receiving, based on the connection identifier, the probe data packet including the third verification information transmitted by the terminal through the second data connection; sending a response data packet to the terminal for the probe data packet, where the response data packet includes fourth verification information; The fourth verification information is used for the terminal to verify the fourth verification information based on the third verification information, and when a verification result indicating that the verification is passed is obtained, the verification is performed based on the second data connection. data transmission. 9. The method of claim 1, further comprising: Monitoring whether the target Internet Protocol address has changed, and obtaining a monitoring result, the target Internet Protocol address belongs to the server that establishes the first data connection with the terminal; When the monitoring result indicates that the target Internet Protocol address is changed, create a second socket interface for the changed target Internet Protocol address, and establishing a third data connection with the terminal based on the second socket interface, so as to migrate the data connection with the terminal from the first data connection to the third data connection; Wherein, the connection identifier of the third data connection is consistent with the connection identifier of the first data connection. 10. The method of claim 9, wherein the monitoring of whether the target Internet Protocol address is changed to obtain a monitoring result, comprising: monitoring at least one of the data transmission failure event of the raw socket interface corresponding to the target internet protocol address and the change notification message of the target internet protocol address; When at least one of the data transmission failure event of the raw socket interface corresponding to the target Internet Protocol address and the change notification message of the target Internet Protocol address are monitored, a monitoring indicating that the target Internet Protocol address is changed is obtained. result. 11. The method according to claim 9, wherein after establishing the third data connection with the terminal, the method further comprises: Based on the connection identifier, verifying the data reachability of the third data connection to obtain a verification result; When the verification result indicates that the data of the third data connection is reachable, perform data transmission with the terminal based on the third data connection. 12. A data transmission method, characterized in that the method comprises: Create a first data connection with the server for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the server changes; sending a data packet to the server based on the first data connection; The data type of the data packet includes an unreliable data type, and the unreliable data type is used to control not to return the corresponding data when the server determines that the data type of the data packet is an unreliable data type Packet receive response message. 13. A data transmission device, wherein the device comprises: A creation module is used to create a first data connection with the terminal for data transmission, and the connection identifier of the first data connection remains unchanged when the Internet Protocol address or port of the terminal changes; a receiving module, configured to receive a data packet transmitted by the terminal based on the first data connection; a parsing module, configured to parse the data packet to determine the data type corresponding to the data packet; A control module, configured to control not to return a reception response message corresponding to the data packet to the terminal when it is determined that the data type of the data packet is an unreliable data type. 14. An electronic device, characterized in that the electronic device comprises: memory for storing executable instructions; The processor is configured to implement the data transmission method according to any one of claims 1 to 12 when executing the executable instructions stored in the memory. 15. A computer-readable storage medium, characterized by storing executable instructions, which, when executed, are used to implement the data transmission method according to any one of claims 1 to 12.

Images