WO2024093284A1

WO2024093284A1 - Data transmission method and apparatus, and device

Info

Publication number: WO2024093284A1
Application number: PCT/CN2023/103045
Authority: WO
Inventors: 虞学伦; 王凡钊; 池越可; 胡水海
Original assignee: 华为技术有限公司
Priority date: 2022-11-04
Filing date: 2023-06-28
Publication date: 2024-05-10
Also published as: CN116132503A

Abstract

The present application relates to the technical field of communications, and in particular relates to a data transmission method and apparatus, and a device. The method comprises: a first terminal device sending first information to a first server device, the first information comprising first historical link information, wherein the first historical link information represents the state of a historical link, and the historical link is a historical link between the first server device and the first terminal device, or is a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are located in the same local area network; the first server device configuring an initial sending policy of a first link between a first server and the first terminal device according to the state of the historical link; and the first server device sending service data to the first terminal device by means of the first link according to the initial sending policy. By means of the method, the risk of congestion occurring in a newly-built link between a terminal device and a server device can be reduced, or the bandwidth waste of the newly-built link can be reduced.

Description

Data transmission method, device and equipment

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 4, 2022, with application number 202211376517.1 and application name “Data Transmission Method, Device and Equipment”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a data transmission method, device and equipment.

Background technique

In recent years, new streaming services such as live broadcast and short video have emerged, and users' requirements for streaming services are developing in the direction of ultra-high definition, ultra-high fluency, and ultra-low latency. In the scenarios where users actually use the services, users often switch between live broadcast rooms or videos frequently, resulting in a high proportion of short connections, and the terminal needs to frequently establish new links with the server. After the new link is established, the server needs to push the first frame data of the video to the terminal again. The terminal starts to play the picture only after receiving the first frame data. Among them, the delay of the first frame is a key factor affecting the user experience. If the delay of the first frame is too large, users will lose interest in continuing to browse because they have to wait too long for the picture to play, which will affect the user experience and the business revenue of the streaming media vendor.

The current network transmission protocol needs to go through a slow start process when transmitting data through a newly established link. It takes several round-trip times (RTT) to reach the transmission rate that matches the real network. Therefore, each time the link is reestablished, the first frame transmission delay is large due to the slow start process, which affects the user experience.

Summary of the invention

The embodiments of the present application provide a data transmission method, apparatus, and device, which can reduce the risk of congestion in a newly created link between a terminal device and a server device or reduce the bandwidth waste of the newly created link.

In a first aspect, a data transmission method is provided, which is applied to a business system, wherein the business system includes at least one terminal device and at least one server device; the method includes: a first terminal device among the at least one terminal device sends a first information to a first server device among the at least one server device, wherein the first information includes a first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network; the first server device sets an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link; and the first server device sends business data to the first terminal device through the first link according to the initial sending strategy.

Through this method, the terminal device sends the historical link information to the server device. Even if the IP address of the terminal device changes, the server device can obtain the information recording the status of the historical link between the terminal device and the server device, that is, the correct historical link information, so that the server device can obtain the status of the historical link between the terminal device and the server device based on the historical link information, and then the server device can set the initial sending strategy for the newly created link between the server device and the terminal device based on the historical link between the terminal device and the server device. Since the initial sending strategy is set based on the status of the historical link between the terminal device and the server device, the initial sending strategy is highly consistent with the actual network status of the newly created link between the terminal device and the server device, which allows the newly created link to skip the slow start while reducing the risk of congestion in the newly created link between the terminal device and the server device or reducing the bandwidth waste of the newly created link.

In a possible implementation manner, the first information is a handshake message used to establish the first link.

In this implementation, when the terminal device and the server device exchange handshake messages to establish a first link, the historical link information can be carried in the handshake message, thereby sending the historical link information to the server device without additional signaling or message transmission.

In one possible implementation, the state of the historical link includes a first transmission rate, and the initial sending strategy includes an initial rate set based on the first transmission rate; or, the state of the historical link includes a second transmission rate and a round-trip delay RTT, and the initial sending strategy includes an initial rate calculated based on the second transmission rate and the round-trip delay; or, the state of the historical link includes a packet loss rate, and the initial sending strategy includes a data message sending redundancy rate set based on the packet loss rate.

In a possible implementation, there are multiple at least one server device, and the multiple server devices correspond one-to-one to multiple historical link information; the method also includes: the terminal device determines the first historical link information from multiple historical link information based on the identifier of the first server device.

In this implementation, the historical link information is identified by the identifier of the server device. The server device is relatively fixed, and the identifier of the server device is also relatively fixed. The identifier of the server device is used to indicate the historical link information, so that the status of the link recorded in the historical link information and the device corresponding to the link have a high degree of consistency.

In a possible implementation manner, when the historical link is a historical link between the first server device and the first terminal device When the historical link is a historical link between the first server device and the second terminal device, the first historical link information is detected by the first terminal device when the first server device sends service data to the first terminal device through the historical link; when the historical link is a historical link between the first server device and the second terminal device, the first historical link information is detected by the second terminal device when the first server device sends service data to the first terminal device through the historical link.

In a possible implementation, the business system also includes an intermediate device, and the method also includes: when the first terminal device or the second terminal device detects the first historical link information, the first terminal device or the second terminal device sends the first historical link information to the intermediate device; the first terminal device sends the first information to the first server device among the at least one server device, including: the first terminal device obtains the first historical link information from the intermediate device, and includes the first historical link information in the first information sent to the first server device.

In this implementation, the historical link information can be stored in the intermediate device, so that different terminal devices connected to the intermediate device can obtain the historical link information from the intermediate device, thereby achieving sharing of the historical link information among different terminal devices connected to the intermediate device.

In a possible implementation, when the historical link is a historical link between the first server device and the second terminal device, and the second terminal device and the first terminal device have different requirements for link quality, the method further includes: the intermediate device modifies the first historical link information detected by the second terminal device according to the link quality of the first terminal device; the first terminal device obtains the first historical link information from the intermediate device, including: the first terminal device obtains the modified first historical link information from the intermediate device.

In this embodiment, when the terminal device that generates the historical link information (i.e., the second terminal device) and the terminal device that uses the historical link information (i.e., the first terminal device) are different, the link state represented by the historical link information can be adjusted according to the quality requirements of the terminal device that uses the link information, that is, the historical link information can be modified so that the link state represented by the modified historical link information matches the quality requirements of the terminal device that uses the link information, thereby making the initial sending strategy determined by the server device based on the modified historical link information more consistent with the actual network state of the newly created link.

In one possible implementation, the first link is a Quick UDP Internet Connection Protocol (QUIC) link, and the historical link is a QUIC link or a Transmission Control Protocol (TCP) link; or, the first link is a TCP link, and the historical link is a QUIC link or a Transmission Control Protocol (TCP) link.

In a second aspect, a data transmission method is provided, which is applied to a first terminal device in a business system, wherein the business system further includes at least one server device; the method includes:

The first terminal device sends first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

Among them, the state of the historical link is used by the first server device to set an initial sending strategy for the first link between the first server and the first terminal device, and the initial sending strategy is used by the first server device to send service data to the first terminal device through the first link.

In a possible implementation, there are multiple at least one server device, and the multiple server devices correspond one-to-one to multiple historical link information; the method also includes: the terminal device determines the first historical link information from the multiple historical link information based on the identifier of the first server device.

In a third aspect, a data transmission method is provided, which is applied to a first server device in a business system, wherein the business system further includes at least one terminal device; the method includes:

The first server device receives first information sent by a first terminal device among the at least one terminal device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

The first server device sets an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The first server device sends service data to the first terminal device through the first link according to the initial sending strategy.

In a possible implementation manner, the state of the historical link includes a first transmission rate, and the initial sending strategy includes an initial rate set based on the first transmission rate; or,

The state of the historical link includes a second transmission rate and a round-trip time RTT, and the initial sending strategy includes an initial rate calculated based on the second transmission rate and the round-trip time RTT; or

The state of the historical link includes a packet loss rate, and the initial sending strategy includes a data message sending redundancy rate set based on the packet loss rate.

In a fourth aspect, a business system is provided, the business system comprising at least one terminal device and at least one server device; wherein:

The first terminal device among the at least one terminal device is used to send first information to the first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates the state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

The first server device is used to set an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The first server device is used to send service data to the first terminal device through the first link according to the initial sending strategy.

In a fifth aspect, a data transmission device is provided, the device being used as a first terminal device in a service system, the service system further comprising at least one server device; the device comprising:

A communication unit, configured to send first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

In a sixth aspect, a data transmission device is provided, the device being used as a first server device in a business system, the business system further comprising at least one terminal device; the device comprising:

a receiving unit, configured to receive first information sent by a first terminal device among the at least one terminal device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

A setting unit, configured to set an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

A sending unit is used to send service data to the first terminal device through the first link according to the initial sending strategy.

In the seventh aspect, a terminal device is provided, comprising a memory and a processor; the memory is used to store computer instructions; the processor is used to execute the computer instructions stored in the memory to implement the method described in the second aspect.

In an eighth aspect, a server-side device is provided, comprising a memory and a processor; the memory is used to store computer instructions; the processor is used to execute the computer instructions stored in the memory to implement the method described in the third aspect.

In a ninth aspect, a computer storage medium is provided, wherein the computer storage medium includes computer instructions, and when the computer instructions are executed on a computing device, the computing device executes the method described in the second aspect or the method described in the third aspect.

In the tenth aspect, a chip is provided, wherein the chip is used to execute the method described in the second aspect or the method described in the third aspect.

In the eleventh aspect, a computer program product is provided, which, when the program code contained in the computer program product is executed by a processor in a computing device, implements the method described in the second aspect or the method described in the third aspect.

The data transmission method, apparatus and equipment provided in the embodiments of the present application can enable the server device to determine an initial sending strategy that is highly consistent with the actual network status of the newly created link between the terminal device and the server device, and send service data to the terminal device through the newly created link according to the initial sending strategy, thereby reducing the risk of congestion in the newly created link between the terminal device and the server device or reducing the bandwidth waste of the newly created link.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

FIG2 is a schematic diagram of a system architecture provided in an embodiment of the present application;

FIG3 is a schematic diagram of software results of a server device provided in an embodiment of the present application;

FIG4A is a flow chart of a data transmission solution provided in an embodiment of the present application;

FIG4B is a flow chart of a data transmission scheme provided in an embodiment of the present application;

FIG5 is a schematic diagram of a message structure provided in an embodiment of the present application;

FIG6 is a flow chart of a data transmission method provided in an embodiment of the present application;

FIG7 is a schematic diagram of the structure of a data transmission device provided in an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a data transmission device provided in an embodiment of the present application;

FIG9 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

FIG. 10 is a schematic diagram of the structure of a server device provided in an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments.

In the description of this specification, "one embodiment" or "some embodiments" etc. means that one or more embodiments of this specification include a specific feature, structure or characteristic described in conjunction with the embodiment. Therefore, the phrases "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways.

In the description of this specification, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this article is only a description of the association relationship of related objects, indicating that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this specification, "multiple" means two or more than two.

In the description of this specification, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. The terms "include", "comprises", "has" and their variations all mean "including but not limited to", unless otherwise specifically emphasized.

With the development of streaming media services, users' experience requirements for streaming media services are also developing towards ultra-high definition, ultra-high fluency, and ultra-low latency. Among them, ultra-high definition requires the video bit rate to be increased to 4K resolution, 8K resolution or even higher, and the frame rate to be increased to 120fps. Ultra-high fluency requires the user experience to be free of lag and the transmission network to have a packet loss rate of less than 0.3%; ultra-low latency requires the real-time interaction between the client and the server to have a latency of less than 50ms.

In order to meet the user experience requirements, the industry continues to invest in the fields of media application processing, transmission network, transmission protocol, etc. to develop related technologies. In the field of media application processing, the user's picture quality experience is improved by developing codec and cloud collaborative processing technologies. In the field of transmission network, streaming media service providers reduce end-to-end latency by building or renting content delivery networks (CDN).

Among them, CDN is a network infrastructure widely used on the Internet, which can provide cheap cross-regional large-scale data distribution and caching capabilities for streaming media services. The transmission of streaming media service data from the CDN edge node as the server to the client needs to follow the transmission protocol. Among them, the commonly used transmission protocols for streaming media services are the transmission control protocol (TCP) and the quick UDP internet connection protocol (QUIC) based on the user datagram protocol (UDP). Among them, QUIC is a transport layer protocol running in user mode, which can be multiplexed and is more secure and reliable than the TCP protocol.

In the scenario where users actually use streaming media services, they may frequently switch between live broadcast rooms or videos, resulting in a high proportion of short connections, requiring the terminal device to frequently re-establish links with the server. After the new link is established, the server needs to push the first frame of video data to the terminal again. Among them, the first frame data refers to the first frame of video stream data transmitted by the server to the terminal device after the link is established, when the video stream data is encoded and decoded at the granularity of frames and transmitted in the network. The terminal starts to play the picture only after receiving the first frame data. Among them, the delay of the first frame is a key factor affecting the user experience. If the delay of the first frame is too large, the user will lose interest in continuing to browse because he has to wait too long for the picture to play, which will affect the user experience and the business revenue of the streaming media manufacturer.

In current transmission protocols (e.g., TCP protocol, QUIC protocol), data transmission on a newly created link needs to go through slow start. Slow start is a congestion control mechanism used by transmission protocols to avoid network congestion caused by sending data that exceeds the network's carrying capacity. During the slow start process, the sender will increase the congestion window (CWND) every time it receives an acknowledgment character (ACK) sent by the receiver, until the packet loss rate reaches a certain level. Therefore, it takes several RTTs to reach a transmission rate that matches the actual network conditions. Prior to this, service data is sent at a transmission rate lower than that that matches the actual network conditions. Therefore, the slow start mechanism seriously affects the transmission of the first frame of data, thereby affecting the user experience.

In one solution, a destination metrics mechanism is used to make the newly created link skip the slow start phase. The destination metrics mechanism refers to the link status represented by the historical link information cached by the server, which initializes the initial sending strategy of the newly created link so that the server does not go through the slow start phase and directly sends data to the client through the newly created link according to the initial sending strategy. The historical link information records the status of the historical links between the server and the client, and is generated by the client's Internet protocol (IP). In this scheme, when the link between the server and the client is established, the server queries the historical link information according to the IP address of the client, and uses the link status identified by the historical link information to initialize the initial sending strategy of the newly created link.

Although this solution allows the newly created link to skip the slow start phase. However, in business scenarios such as streaming media, due to technologies such as network address translation (NAT), the IP address of the client observed by the server may be shared by multiple clients, and the IP address of the client may change with time or location (for example, an IP address is first used by client A1 and then by client A2), resulting in the historical link information queried by the server through the client IP address may not actually be information recording the status of the historical link between the client and the server. Therefore, according to the historical link information (for example, the historical link information recording the status of the historical link between client A1 and the server) queried through the client IP address (for example, the historical link information recording the status of the historical link between client A1 and the server), the initialization of the initial sending strategy of the newly created link between the client (using client A2) and the server may result in a large difference between the initialized initial sending strategy and the actual network status of the newly created link, which may cause congestion or bandwidth waste when sending data according to the initial sending strategy. In addition, since the server establishes links with many clients, in this solution, the server needs to cache a lot of historical link information, resulting in a large cache pressure on the server. In particular, the server currently usually adopts a server cluster architecture, under which historical link information needs to be synchronized between different servers, and the synchronization of a lot of historical link information between different servers is highly complex.

In another solution, the server caches the actual maximum transmission rate of the historical link between the server and the client. The actual maximum transmission rate is still identified by the IP address of the client. When a client with the same IP address requests to establish a link with the server, the server uses the actual maximum transmission rate of the historical link to set the starting transmission rate of the new link. Although this solution allows the new link to skip the slow start phase. However, due to the sharing of IP addresses between different clients and the change of client IP addresses, the starting transmission rate of the new link and the actual network status of the new link are quite different, which may cause congestion or bandwidth waste when sending data according to the initial sending strategy. In addition, since the server establishes links with many clients, in this solution, the server needs to cache a lot of historical link information, resulting in a large cache pressure on the server. In particular, the server currently usually adopts a server cluster architecture, under which historical link information needs to be synchronized between different servers, and the synchronization of many historical link information between different servers is complex.

An embodiment of the present application provides a data transmission scheme. In this scheme, a terminal device can cache historical link information and send the historical link information to a server device. The server device can set the initial transmission strategy for the newly created link between the server device and the terminal device according to the state of the historical link represented by the historical link information sent by the terminal device, and send service data to the terminal device through the newly created link according to the initial transmission strategy. Among them, the terminal device can also be called a client, or a device running a client. The link state includes the actual transmission rate of the link, round-trip delay, congestion window, packet loss rate, etc. The sending strategy refers to the strategy of the server to send service data to the client. The initial sending strategy refers to the service data sending strategy adopted by the sender when it starts to send service data to the receiver through the link after the link is established.

In this solution, the terminal device sends the historical link information to the server device. Even if the IP address of the terminal device changes, the server device can obtain the information recording the status of the historical link between the terminal device and the server device, that is, the correct historical link information, so that the server device can obtain the status of the historical link between the terminal device and the server device based on the historical link information, and then the server device can set the initial sending strategy for the newly created link between the server device and the terminal device based on the historical link between the terminal device and the server device. Since the initial sending strategy is set based on the status of the historical link between the terminal device and the server device, the initial sending strategy is highly consistent with the actual network status of the newly created link between the terminal device and the server device, which allows the newly created link to skip the slow start while reducing the risk of congestion or bandwidth waste in the newly created link.

Moreover, in this solution, the terminal device sends the historical link information to the server device, that is, the historical link information does not need to be cached in the server device, thereby alleviating the cache pressure of the server device and reducing the complexity of synchronizing data between servers.

Next, the data transmission scheme provided in the embodiment of the present application is described in detail.

FIG1 shows a system architecture 100. The system architecture 100 can be used to implement the data transmission solution provided in the embodiment of the present application. As shown in FIG1, the system architecture 100 may include at least a server device 111 and a terminal device 121. That is, the system architecture 100 includes at least one server device and at least one terminal device.

In some embodiments, the system architecture 100 may include multiple server devices. As shown in FIG1 , the system architecture 100 includes a server device 111 and a server device 112, etc. The system architecture 100 may include multiple terminal devices. As shown in FIG1 , the system architecture 100 includes a terminal device 121 and a terminal device 122, a terminal device 123, a terminal device 124, etc.

In the embodiment of the present application, when no special distinction is made between the server devices 111, 112, etc., they may be referred to as server devices for short. When no special distinction is made between the terminal devices 121, 122, 123, 124, etc., they may be referred to as terminal devices for short.

The server device refers to the service server, which stores service data and can send service data to the service client so that users can In one example, the service may be a streaming service. In another example, the service may be a live broadcast service. In another example, the service may be a short video service. And so on. In another example, the service may be a cloud rendering service, such as cloud rendering of three-dimensional image rendering. The image is rendered on the server device, and then the server device sends the image to the client in the form of a video stream.

In some embodiments, the server device may be implemented by hardware, for example, as a server or a server cluster. For another example, the server device may be one or more computing nodes in a cloud computing data center. In some embodiments, the server device may be implemented by software. For example, the server device may be implemented as a virtual machine (VM). In a specific example, the server device may be a content delivery network (CDN) node.

The terminal device is a user-side device that can run the client of the service so that the user can use the service provided by the server device through the terminal device. The terminal device can be a mobile phone, tablet computer, personal computer (PC), smart wearable device, smart TV, car terminal, aerial photography drone, etc. Among them, the terminal device can provide a hardware environment for the operation of the service client.

Continuing to refer to FIG. 1 and FIG. 2 , the terminal device and the server device can be connected via the Internet. Wherein, via the Internet, the terminal device and the server device can establish a communication link between them according to a transmission protocol. The server device can send service data, such as a video stream, to the terminal device via the communication link.

When a new communication link is established between a terminal device and a server device, the terminal device may send historical link information between the terminal device and the server device to the server device. The historical link information indicates the state of the historical link between the terminal device and the server device. The historical link refers to the communication link between the terminal device and the server device in history. That is, the historical link refers to the communication link between the terminal device and the server device before the new communication link is established between the terminal device and the server device.

After receiving the historical link information and successfully establishing a new link between the server device and the terminal device, the server device can set the initial transmission strategy of the new link according to the state of the historical link represented by the historical link information. Then, the server device can send service data to the terminal device according to the initial transmission strategy, thereby skipping the slow start phase, improving the service data transmission efficiency, especially improving the transmission efficiency of the first frame data.

In some embodiments, the software structure of the server device may be as shown in FIG3, including an application layer module 310, a transport layer module 320, and an IP layer module 300. The application layer module 310 is used to transfer service data to the transport layer module 320 according to the application layer protocol. The transport layer module 320 may encapsulate the service data into a data message of the transport layer according to the transport layer protocol (e.g., TCP protocol, QUIC protocol, etc.), and transfer the data message of the transport layer to the IP layer module 330. The IP layer module 330 may further encapsulate the data message and then transfer it to the next layer.

The transport layer module 320 includes a connection management unit 321 , a link status information management unit 322 , a congestion control unit 323 , a redundancy recovery unit 324 , a message encapsulation and parsing unit 325 , and a transceiver unit 326 .

The transceiver unit 326 is used to receive information sent by the terminal device, such as historical link information. The message encapsulation and parsing unit 325 can encapsulate the service data into a data message of the transport layer, or parse the transport layer message header of the message from the IP layer module 330, thereby extracting the information carried by the message header, such as historical link information.

The link state information management unit 322 can obtain historical link information, and set the initial sending strategy of the newly created link according to the state of the historical link represented by the historical link information. The state of the historical link may include RTT and CWND, and the set initial sending strategy may include an initial transmission rate. Specifically, the link state information management unit 322 may calculate the initial transmission rate according to the RTT and the CWND. The link state information management unit 322 may pass the calculated initial transmission rate to the congestion control unit 323, so that the congestion control unit 323 may control the rate at which the server device sends data packets based on the initial transmission rate. The state of the historical link may include a packet loss rate, and the link state information management unit may determine a redundancy rate according to the packet loss rate, and pass the redundancy rate to the redundancy recovery unit 324. The redundancy recovery unit 324 may enable forward error correction (FEC) according to the redundancy rate, and send data packets to the terminal device according to the redundancy rate to combat network packet loss.

In some embodiments, the system architecture 100 may include an intermediate device in the same local area network as the terminal device. The terminal device is connected to the Internet through the intermediate device, and can then be connected to the server device through the Internet. In some embodiments, the intermediate device may include multiple access devices such as access device 131 and access device 132, and at least one aggregation device such as aggregation device 141.

The access device is a network access device close to the terminal device. The terminal device accesses the network by connecting to the access device. Typical access devices include modems, routers, or wireless base stations.

The aggregation device is a device located on the terminal side that is used to connect access devices to the network. The aggregation device can be used to forward data from multiple access devices to the server device, and forward data from the server device to multiple access devices. Typical aggregation devices include core routers, core switches, etc.

The above example introduces a system architecture that can be used to implement the data transmission solution provided in the embodiment of the present application. The structure takes the terminal device 121 and the server device 111 as examples to introduce the execution process of the data transmission solution provided in the embodiment of the present application.

4A and 4B, in step 401, the terminal device 121 may determine that a link B1 needs to be established with the server device 111. When step 401 is executed, there is no link between the terminal device 121 and the server device 111. In other words, the link B1 is a new link that needs to be established, rather than an existing link between the terminal device 121 and the server device 111.

The link can also be called a communication link, which refers to a channel for data transmission between devices. The link can be a link defined by a transmission protocol, such as a link defined by the TCP protocol, a link defined by the QUIC protocol, etc.

In some embodiments, the terminal device 121 can actively establish a link B1 between the terminal device 121 and the server device 111. Taking the live broadcast service as an example, the user can switch the live broadcast room through the terminal device 121. Taking short videos as an example, the user can switch short videos through the terminal device 121. In these cases, the terminal device 121 needs to switch the connection between the terminal device 121 and other server devices to the connection between the terminal device 121 and the server device 111. In this way, the terminal device 121 can actively establish a link B1 between the terminal device 121 and the server device 111, so that it can be determined that the link B1 needs to be established with the server device 111.

In some embodiments, the terminal device 121 can passively establish a link between the terminal device 121 and the server device 111. Exemplarily, the terminal device 121 can determine that it is necessary to establish a link B1 with the server device 111 when receiving a handshake request message sent by the server device 111. When the terminal device and the server device establish a link, several handshake messages are required to shake hands before the link can be successfully established. When the server device 111 needs to establish a link with the terminal device 121, the server device 111 sends a handshake request message to the terminal device 121 to request or notify the terminal device 121 to perform a link establishment operation. Therefore, when the terminal device 121 receives the handshake request message sent by the server device 111, the terminal device 121 can passively establish a link B1 between the terminal device 121 and the server device 111, thereby determining that it is necessary to establish a link B1 with the server device 111.

The terminal device 121 may execute step 402, and the terminal device 121 obtains historical link information C1. The historical link information refers to information recording the status of the historical link between the terminal device and the server device. The link status refers to the actual status of the link, including the actual transmission rate, round-trip delay, congestion window, packet loss rate, etc. of the link. The historical link information C1 refers to information recording the status of the historical link between the terminal device D and the server device 111. The terminal device D may be the terminal device 121, or a terminal device (such as the terminal device 122) in the same local area network as the terminal device 121. When the terminal device D is the terminal device 121, the historical link between the terminal device D and the server device 111 refers to the link between the terminal device 121 and the server device 111 in history, and the historical link has been disconnected in step 401. When the terminal device D is not the terminal device 121, that is, when the terminal device D is another terminal device in the same local area network as the terminal device 121, the historical link between the terminal device D and the server device 111 refers to the historical link or the most recently established link between the terminal device D and the server device 111. The historical links and the recently established links are relative to the execution time of step 401 .

In an embodiment of the present application, the historical link information C1 and the identifier of the server device 111 have a mapping relationship. Exemplarily, the identifier of the server device 111 can be the network address of the server device 111, such as an IP address. The identifier of the server device 111 can also be other information that can distinguish the server device 111 from other server devices. It is not difficult to understand that the location of the server device is relatively fixed, so the identifiers such as the network address of the server device 111 are also relatively fixed. The identifier of the server device is used to indicate the historical link information, so that the status of the link recorded by the historical link information and the device corresponding to the link have a high degree of consistency.

When storing the historical link information C1, the identifier of the server device 111 can be used as the key of the historical link information C1. The terminal device 121 can query the historical link information C1 based on the identifier of the server device 111, thereby obtaining the historical link information C1. In particular, when the system architecture 100 includes multiple server devices, there may be multiple historical link information on the terminal device side, wherein multiple server devices correspond to multiple historical link information one by one. According to the identifier of the server device, the historical link information corresponding to the corresponding server device can be queried from the multiple historical link information. Among them, the terminal device side includes the terminal device itself and other devices in the same local area network as the terminal device.

In some embodiments, when there is a link between a terminal device and a server device, the terminal device can detect the state of the link and obtain historical link information. The terminal device can store or cache historical link information. Exemplarily, the terminal device can periodically detect the state of the link according to a preset period T1 to periodically obtain historical link information. Among them, the historical link information has a life cycle, for example, the life cycle of the historical link information can be N periods T1. When the storage time of the historical link information reaches N periods T1, the historical link information becomes invalid. The historical link information after expiration can be deleted. Among them, N is an integer greater than or equal to 1. The duration of period T1 can be preset based on experience or experiment. In one example, the duration of period T1 can be 5 seconds. In another example, the duration of period T1 can be 10 seconds. And so on.

In addition, the historical link information C1 acquired in step 402 is historical link information that has not been invalidated.

In some embodiments, the terminal device may store or cache the obtained historical link information locally. In step 402 , the terminal device 111 may query the historical link information C1 in the information stored or cached locally according to the identification of the server device 111 .

In some embodiments, the terminal device may send the historical link information to an intermediate device in the same local area network (ie, the intermediate device and the terminal device are in the same local area network) so that the intermediate device stores or caches the historical link information. When the historical link information C1 needs to be obtained, the terminal device 121 can execute step 402a to send the identifier of the server device 111 to the intermediate device. The intermediate device can query the historical link information C1 in the information stored or cached by the intermediate device according to the identifier of the server device 111. When the intermediate device queries the historical link information C1, it can execute step 402b to send the historical link information C1 to the terminal device 121.

In this embodiment, historical link information can be shared by different terminal devices in the same local area network. Specifically, there is a link or has historically existed a link between the terminal device 122 and the server device 111, and the terminal device 122 generates historical link information C1, and the historical link information C1 is indicated by the identifier of the server device. The terminal device 122 can send the historical link information C1 to the intermediate device. When the terminal device 121 needs to obtain the historical link information (i.e., historical link information C1) indicated by the identifier of the server device 111, it can query the intermediate device based on the identifier of the server device 111 to obtain the historical link information C1 generated by the terminal device 122 and indicated by the identifier of the server device 111, thereby obtaining the historical link information C1. In this way, the sharing of historical link information between different terminal devices is achieved.

In an example of this embodiment, in the system architecture 100, the intermediate device includes an access device and an aggregation device. The terminal device can send the historical link information to the access device to which the terminal device is connected, so that the historical link information is stored or cached in the access device. The access device can also send the historical link information it has received to the aggregation device to which the access device is connected, so that the historical link information is stored or cached in the aggregation device. When the terminal device needs to obtain the historical link information, it can query the corresponding historical link information in the information stored or cached in the access device or aggregation device to which the terminal device is connected according to the identification information of the server device. In one example, when the terminal device needs to obtain the historical link information, it can query the corresponding historical link information (historical link information indicated by the identification of the server device) in the information stored or cached in the access device to which the terminal device is connected according to the identification of the server device, so as to preferentially obtain the historical link information generated by the terminal device under the same access device. When the corresponding historical link information is not queried in the information stored or cached in the access device to which the terminal device is connected, the terminal device then queries the corresponding historical link information in the information stored or cached in the corresponding aggregation device according to the identification of the server device. Among them, the corresponding aggregation device of the terminal device refers to the aggregation device connected to the access device to which the terminal device is connected.

In some embodiments, the terminal device may store or cache the obtained historical link information locally, and at the same time, send the historical link information to the intermediate device. When the terminal device needs to obtain the historical link information, it can first query the corresponding historical link information (historical link information indicated by the identification of the server device) in the information stored or cached by the terminal device according to the identification of the server device, so as to preferentially obtain the historical link information generated by the same terminal device. When the corresponding historical link information is not queried in the information stored or cached by the terminal device, the terminal device then queries the corresponding historical link information in the information stored or cached by the intermediate device according to the identification of the server device.

In some embodiments, as described above, the historical link information C1 is information that records the status of the historical link between the terminal device D and the server device 111. The terminal device D is the terminal device 121 or other terminal devices in the same local area network as the terminal device 121. The other terminal device in the same local area network as the terminal device 121 can be set as the terminal device 122. When the terminal device D is a device other than the terminal device 121, that is, when the terminal device D is the terminal device 122, that is, when the historical link information C1 is detected by the terminal device 122, if the terminal device 121 and the terminal device 122 have different requirements for the link quality, the original historical link information C1 can be modified or adjusted according to the link quality requirements of the terminal device 121. The modified or adjusted original historical link information C1 is used as the historical link information C1 acquired by the terminal device 121.

The original historical link information C1 refers to the historical link information C1 detected by the terminal device 122. The terminal device detecting the historical link information refers to the terminal device detecting the state of the link and generating the historical link information based on the detection result. Link quality can refer to quality of service (QoS) or other forms of network link quality.

As described above, the intermediate device stores or caches the historical link information detected by the terminal device connected to the intermediate device. It can be set that in the system architecture 100 shown in Figure 1, the access device 131 or the aggregation device 141 stores or caches the original historical link information C1 detected by the terminal device 122. It can also be set that the terminal device 121 and the terminal device 122 have different requirements for link quality. The state of the link is affected by the requirements of the terminal device 122 for link quality and the performance of the link itself. For example, the theoretical bandwidth of the link is 20MB, and the requirements of the terminal device 122 for link quality are: high requirements for packet loss rate and low requirements for transmission rate. Therefore, in actual transmission, in order to ensure a lower packet loss rate, a transmission rate lower than the theoretical bandwidth, such as 10MB, may be used for data transmission. This results in the data transmission rate recorded by the original historical link information C1 detected by the terminal device 122 being 10MB. The requirements of the terminal device 121 for link quality are: high requirements for transmission rate and low requirements for packet loss rate. When the terminal device 121 obtains the historical link information C1 from the access device 131 or the aggregation device 141, the access device 131 or the aggregation device 141 may adjust or modify the original historical link information C1 according to the link quality requirements of the terminal device 121. For example, the data transmission rate recorded in the original historical link information C1 is modified from 10MB to the theoretical bandwidth (i.e., 20MB), etc. The access device 131 or the aggregation device 141 sends the modified original historical link information C1 as the historical link information C1 to the terminal device 121.

4A and 4B , after the terminal device 121 obtains the historical link information C1 , the terminal device 121 may execute step 403 to send the historical link information C1 to the server device 111 .

In some embodiments, step 403 may be performed during or before the establishment of link B1. The establishment of link B1 requires several information handshakes, that is, several handshake messages need to be exchanged between the terminal device 121 and the server device 111. The handshake message is used to A link B1 is established between the device 121 and the server device 111. The terminal device 121 may carry the historical link information C1 in a handshake message sent to the server device 121 to send the historical link information C1 to the server device 111. Exemplarily, the handshake message may be a handshake request message or a handshake response message.

In an example of this embodiment, the historical link information C1 can be carried in a reserved field or an extended field of a handshake message, that is, the reserved field or the extended field is used to carry the historical link information C1. For example, the historical link information C1 is carried in a reserved field or an extended field of a message header of a transport layer protocol. In an example, taking link B1 as a QUIC protocol link as an example, the handshake message supports carrying transport parameter extension information. The historical link information can be added on the basis of the transport parameter already defined in the QUIC protocol. Specifically, as shown in FIG. 5, the added historical link information includes transmission rate, round-trip delay, packet loss rate, etc. In an example, taking link B1 as a TCP protocol link as an example, the historical link information C1 can be carried in a reserved field of the TCP header of the message of the handshake message. Thus, the historical link information C1 can be sent to the server device 111 along with the handshake message.

In some embodiments, step 403 may be performed after the link B1 is established and before the server device 111 sends service data to the terminal device 121 through the link B1.

4A and 4B , after receiving the historical link information C1 , the server device 111 may execute step 404 to set an initial sending strategy for the link B1 .

In some embodiments, the state of the historical link recorded in the historical link information C1 includes a transmission rate. In step 404, the initial rate of the link B1 can be set according to the transmission rate recorded in the historical link information C1. For example, the transmission rate recorded in the historical link information C1 is used as the initial rate. The initial rate is or is included in the initial sending strategy.

In some embodiments, the state of the historical link recorded in the historical link information C1 includes a transmission rate and an RTT. In step 404, the congestion window of the link B1 can be calculated based on the transmission rate and the RTT recorded in the historical link information C1, and then, based on the calculated congestion window, the initial rate of the link B1 is set. The initial rate is or is included in the initial sending strategy.

In some embodiments, the historical link information C1 includes a packet loss rate. In step 404, the data message sending redundancy rate of link B1 can be set according to the packet loss rate recorded in the historical link information C1. The data message sending redundancy rate is or is included in the initial sending strategy to counteract the packet loss rate.

Next, the server device 111 may execute step 405 to send service data to the terminal device 121 through the link B1 according to the initial sending strategy. In other words, the server device 111 directly sends service data to the terminal device 121 through the link B1 according to the initial sending strategy without the slow start link B1. Thus, the data transmission efficiency is improved.

When the initial sending strategy includes or is the initial rate, the server device 111 directly sends service data to the terminal device 121 through the link B1 at the initial rate without the slow start link B1. When the initial sending strategy includes or is the data message sending redundancy rate, the server device 111 directly sends service data to the terminal device 121 through the link B1 at the data message sending redundancy rate without the slow start link B1.

4A and 4B , the terminal device 121 may execute step 406 to detect the state of the link B1 and generate historical link information C2 , wherein the identifier of the historical link information C2 is the identifier of the server device 111 , or in other words, the historical link information C2 is indicated by the identifier of the server device 111 .

Exemplarily, the terminal device 121 may periodically detect the state of the link B1 according to a preset period T1 to periodically obtain the historical link information C2. The historical link information has a life cycle. For example, the life cycle of the historical link information may be N periods T1. When the storage period of the historical link information reaches N periods T1, the historical link information becomes invalid. The invalid historical link information may be deleted. N is an integer greater than or equal to 1. The duration of the period T1 may be preset based on experience or experiment. In one example, the duration of the period T1 may be 5 seconds. In another example, the duration of the period T1 may be 10 seconds. And so on.

In some embodiments, the terminal device 121 may store or cache the historical link information C2 locally. In some embodiments, as shown in FIG4B , the terminal device 121 may execute step 407 to send the historical link information C2 to the intermediate device, and the intermediate device may store or cache the historical link information C2.

In the data transmission scheme provided in the embodiment of the present application, the terminal device sends historical link information to the server device. Even if the IP address of the terminal device changes, the server device can obtain information recording the status of the historical link between the terminal device and the server device, that is, the correct historical link information, so that the server device can obtain the status of the historical link between the terminal device and the server device based on the historical link information, and then the server device can set the initial sending strategy for the newly created link between the server device and the terminal device based on the historical link between the terminal device and the server device. Since the initial sending strategy is set based on the status of the historical link between the terminal device and the server device, the initial sending strategy is highly consistent with the actual network status of the newly created link between the terminal device and the server device, which reduces the risk of congestion or bandwidth waste in the newly created link while allowing the newly created link to skip slow start.

Based on the data transmission scheme described above, the present application embodiment provides a data transmission method. The method can be applied to a business system. The business system includes at least one terminal device and at least one server device. As shown in FIG6 , the method includes the following steps.

Step 601, a first terminal device in at least one terminal device sends a first message to a first server device in at least one server device, wherein the first message includes first historical link information; wherein the first historical link information indicates the state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network. For details, please refer to the above description of steps 401 to 403 in FIG. 4A, or refer to the above description of steps 401, 402a, 402b, and 403 in FIG. 4B.

Step 602: The first server device sets an initial transmission strategy for the first link between the first server and the first terminal device according to the state of the historical link. For details, please refer to the above description of step 404 in FIG. 4A or FIG. 4B.

Step 603: The first server device sends service data to the first terminal device through the first link according to the initial sending strategy. For details, please refer to the above description of step 405 in FIG. 4A or FIG. 4B.

In some embodiments, the first information is a handshake message for establishing the first link. For details, reference may be made to the above description of step 403 in FIG. 4A or FIG. 4B .

In some embodiments, the state of the historical link includes a first transmission rate, and the initial sending strategy includes an initial rate set based on the first transmission rate; or, the state of the historical link includes a second transmission rate and a round-trip delay RTT, and the initial sending strategy includes an initial rate calculated based on the second transmission rate and the round-trip delay; or, the state of the historical link includes a packet loss rate, and the initial sending strategy includes a data message sending redundancy rate set based on the packet loss rate. For details, please refer to the above introduction to step 404 in Figure 4A or Figure 4B.

In some embodiments, the at least one server device is multiple, and the multiple server devices correspond to multiple historical link information one by one; the method further includes: the terminal device determines the first historical link information from the multiple historical link information according to the identifier of the first server device. For details, please refer to the above introduction to step 401-step 402 in Figure 4A, or refer to the above introduction to step 401, step 402a, and step 402b in Figure 4B.

In some embodiments, when the historical link is a historical link between the first server device and the first terminal device, the first historical link information is detected by the first terminal device when the first server device sends service data to the first terminal device through the historical link; when the historical link is a historical link between the first server device and the second terminal device, the first historical link information is detected by the second terminal device when the first server device sends service data to the first terminal device through the historical link.

In one example of these embodiments, the business system further includes an intermediate device, and the method further includes: when the first terminal device or the second terminal device detects the first historical link information, the first terminal device or the second terminal device sends the first historical link information to the intermediate device; the first terminal device sends the first information to the first server device of the at least one server device, including: the first terminal device obtains the first historical link information from the intermediate device, and includes the first historical link information in the first information sent to the first server device. Refer to the above description of step 401, step 402a, step 402b, and step 403 in Figure B.

In one example of this example, when the historical link is a historical link between the first server device and the second terminal device, and the second terminal device and the first terminal device have different requirements for link quality, the method further includes: the intermediate device modifies the first historical link information detected by the second terminal device according to the link quality of the first terminal device; the first terminal device obtains the first historical link information from the intermediate device includes: the first terminal device obtains the modified first historical link information from the intermediate device. Refer to the above introduction to step 401, step 402a, step 402b and step 403 in Figure B.

In some embodiments, the first link is a Quick UDP Internet Connection Protocol (QUIC) link, and the historical link is a QUIC link or a Transmission Control Protocol (TCP) link; or, the first link is a TCP link, and the historical link is a QUIC link or a Transmission Control Protocol (TCP) link.

The data transmission method provided in the embodiment of the present application can enable the server device to determine an initial sending strategy that is highly consistent with the actual network status of the newly created link between the terminal device and the server device, and send business data to the terminal device through the newly created link according to the initial sending strategy, thereby reducing the risk of congestion in the newly created link between the terminal device and the server device or reducing the bandwidth waste of the newly created link.

The embodiment of the present application also provides a data transmission device, which is used as a first terminal device in a business system, and the business system also includes at least one server device. As shown in FIG7 , the device includes:

The communication unit 710 is configured to send first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; and the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device. The second terminal device and the first terminal device are in the same local area network; wherein the state of the historical link is used by the first server device to set an initial sending strategy for the first link between the first server and the first terminal device, and the initial sending strategy is used by the first server device to send service data to the first terminal device through the first link.

The functions of each functional unit of the device can be implemented by referring to the above description of the operations performed by the terminal device 121, and will not be repeated here.

The embodiment of the present application also provides a data transmission device, which is used as a first server device in a business system, and the business system also includes at least one terminal device. As shown in FIG8 , the device includes:

The receiving unit 810 is configured to receive first information sent by a first terminal device among the at least one terminal device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

A setting unit 820, configured to set an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The sending unit 830 is used to send service data to the first terminal device through the first link according to the initial sending strategy.

The functions of each functional unit of the device can be implemented by referring to the above description of the operations performed by the server device 111, and will not be repeated here.

The embodiment of the present application provides a terminal device. Referring to FIG9 , the terminal device may include a memory 910 and a processor 920; wherein the memory 910 is used to store computer instructions; the processor 920 is used to run the computer instructions stored in the memory, so that the terminal device can perform the operations performed by the terminal device 121 in the embodiment shown in FIG4A or FIG4B, or perform the operations performed by the first terminal device in the embodiment shown in FIG6 .

The embodiment of the present application provides a server device. Continuing with FIG10 , the server device may include a memory 1010 and a processor 1020; wherein the memory 1010 is used to store computer instructions; the processor 1020 is used to run the computer instructions stored in the memory, so that the server device can perform the operations performed by the server device 111 in the embodiment shown in FIG4A or FIG4B, or perform the operations performed by the first server device in the embodiment shown in FIG6 .

The embodiment of the present application also provides a chip, which is used to execute the method described above, such as executing the operations performed by the terminal device 121 or the server device 111, and for example, the operations performed by the first terminal device or the first server device.

The embodiment of the present application also provides a computer program product including instructions. The computer program product may be a software or program product including instructions that can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device performs the operations performed by the terminal device 121 or the server device 111 described above, or performs the operations performed by the first terminal device or the first server device described above.

The embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that can be stored by the computing device or a host migration device such as a data center that includes one or more available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid-state hard disk), etc. The computer-readable storage medium includes instructions that instruct the computing device to perform the operations performed by the terminal device 121 or the server device 111 above, or to perform the operations performed by the first terminal device or the first server device above.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of the present invention.

Claims

A data transmission method, characterized in that it is applied to a business system, wherein the business system includes at least one terminal device and at least one server device; the method comprises:

A first terminal device among the at least one terminal device sends first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

The first server device sets an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The first server device sends service data to the first terminal device through the first link according to the initial sending strategy.
The method according to claim 1 is characterized in that the first information is a handshake message used to establish the first link.
The method according to claim 1 or 2, characterized in that

The state of the historical link includes a first transmission rate, and the initial sending strategy includes an initial rate set based on the first transmission rate; or,

The state of the historical link includes a second transmission rate and a round-trip time RTT, and the initial sending strategy includes an initial rate calculated based on the second transmission rate and the round-trip time RTT; or

The state of the historical link includes a packet loss rate, and the initial sending strategy includes a data message sending redundancy rate set based on the packet loss rate.
The method according to any one of claims 1-3 is characterized in that there are multiple at least one server-side devices, and the multiple server-side devices correspond one-to-one to multiple historical link information; the method also includes: the terminal device determines the first historical link information from multiple historical link information based on the identifier of the first server-side device.
The method according to any one of claims 1 to 4, characterized in that

When the historical link is a historical link between the first server device and the first terminal device, the first historical link information is detected by the first terminal device when the first server device sends service data to the first terminal device through the historical link;

When the historical link is a historical link between the first server device and the second terminal device, the first historical link information is detected by the second terminal device when the first server device sends service data to the first terminal device through the historical link.
The method according to claim 5, characterized in that the service system further includes an intermediate device, and the method further includes: when the first terminal device or the second terminal device detects the first historical link information, the first terminal device or the second terminal device sends the first historical link information to the intermediate device;

The first terminal device sending the first information to the first server device among the at least one server device includes: the first terminal device acquiring the first historical link information from the intermediate device, and including the first historical link information in the first information sent to the first server device.
The method according to claim 6 is characterized in that, when the historical link is a historical link between the first server device and the second terminal device, and the second terminal device and the first terminal device have different requirements for link quality, the method further comprises: the intermediate device modifies the first historical link information detected by the second terminal device according to the link quality of the first terminal device;

The first terminal device acquiring the first historical link information from the intermediate device includes: the first terminal device acquiring the modified first historical link information from the intermediate device.
The method according to any one of claims 1 to 7, characterized in that

The first link is a Quick UDP Internet Connection Protocol (QUIC) link, and the historical link is a QUIC link or a Transmission Control Protocol (TCP) link; or,

The first link is a TCP link, and the historical link is a QUIC link or a Transmission Control Protocol TCP link.
A data transmission method, characterized in that it is applied to a first terminal device in a business system, wherein the business system further includes at least one server device; the method comprises:

The first terminal device sends first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

Among them, the state of the historical link is used by the first server device to set an initial sending strategy for the first link between the first server and the first terminal device, and the initial sending strategy is used by the first server device to send service data to the first terminal device through the first link.
The method according to claim 9 is characterized in that there are multiple at least one server-side devices, and the multiple server-side devices correspond one-to-one to the multiple historical link information; the method also includes: the terminal device determines the first historical link information from the multiple historical link information according to the identifier of the first server-side device.
A data transmission method, characterized in that it is applied to a first server device in a business system, wherein the business system also includes at least one terminal device; the method comprises:

The first server device receives first information sent by a first terminal device among the at least one terminal device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

The first server device sets an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The first server device sends service data to the first terminal device through the first link according to the initial sending strategy.
The method according to claim 11, characterized in that

The state of the historical link includes a first transmission rate, and the initial sending strategy includes an initial rate set based on the first transmission rate; or,

The state of the historical link includes a second transmission rate and a round-trip time RTT, and the initial sending strategy includes an initial rate calculated based on the second transmission rate and the round-trip time RTT; or

The state of the historical link includes a packet loss rate, and the initial sending strategy includes a data message sending redundancy rate set based on the packet loss rate.
A business system, characterized in that the business system includes at least one terminal device and at least one server device; wherein,

The first terminal device among the at least one terminal device is used to send first information to the first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates the state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

The first server device is used to set an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

The first server device is used to send service data to the first terminal device through the first link according to the initial sending strategy.
A data transmission device, characterized in that the device is used as a first terminal device in a business system, and the business system also includes at least one server device; the device comprises:

A communication unit, configured to send first information to a first server device among the at least one server device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

Among them, the state of the historical link is used by the first server device to set an initial sending strategy for the first link between the first server and the first terminal device, and the initial sending strategy is used by the first server device to send service data to the first terminal device through the first link.
A data transmission device, characterized in that the device is used as a first server device in a business system, and the business system also includes at least one terminal device; the device comprises:

a receiving unit, configured to receive first information sent by a first terminal device among the at least one terminal device, wherein the first information includes first historical link information; wherein the first historical link information indicates a state of a historical link; the historical link is a historical link between the first server device and the first terminal device, or a historical link between the first server device and a second terminal device, and the second terminal device and the first terminal device are in the same local area network;

A setting unit, configured to set an initial sending strategy for the first link between the first server and the first terminal device according to the state of the historical link;

A sending unit is used to send service data to the first terminal device through the first link according to the initial sending strategy.
A terminal device, characterized in that it comprises a memory and a processor; the memory is used to store computer instructions; the processor The computer instructions stored in the memory are used to execute the method according to claim 9 or 10.
A server device, characterized in that it includes a memory and a processor; the memory is used to store computer instructions; the processor is used to execute the computer instructions stored in the memory to implement the method described in claim 11 or 12.
A computer storage medium comprising computer instructions, which, when executed on a computing device, causes the computing device to execute the method of claim 9 or 10 or the method of claim 11 or 12.
A computer program product, characterized in that when the program code contained in the computer program product is executed by a processor in a computing device, the method of claim 9 or 10 or the method of claim 11 or 12 is implemented.