Patent Application
20230078814
This application claims priority to Chinese Patent Application No. 202111017185.3, filed on Aug. 31, 2021, which is hereby incorporated by reference in its entirety.
The embodiments relate to the field of data transmission technologies, a data transmission method and a related device.
QUIC is an Internet transport layer protocol. For related descriptions of the QUIC transport protocol, refer to the RFC 9000 document. Details are not described.
In current QUIC transport protocol-based data transmission, data between a transmit end and a receive end is transmitted in a form of a byte stream. Application messages submitted by an application of the transmit end to a QUIC entity of the transmit end are usually combined, then combined data is segmented into data frames based on a factor such as a network status of a QUIC connection, and then the data frames are transmitted to the receive end. When receiving the data frames, the receive end does not know an application message or even application messages to which data in the data frames belongs. Therefore, after receiving the data frames, the receive end needs to combine the received data frames and traverse the data in the combined data frames, to identify boundaries of each application message, so as to obtain the application message submitted by the application of the transmit end. An operation of identifying the boundaries of the application message in the received data may also be referred to as boundary check. Because the receive end needs to perform boundary check each time the receive end receives data frames, an information processing process is complex, and processing overheads are high.
The embodiments may provide a data transmission method, to resolve a problem in current QUIC transport protocol-based data transmission that a processing process is complex because an application of a receive end needs to perform boundary check each time the receive end receives data. The embodiments may further provide a corresponding apparatus, device, communication system, computer-readable storage medium, computer program product, and the like.
A first aspect may provide a data transmission method, including: obtaining a first application message generated by a target application, where the target application runs on a transmit end; encapsulating the first application message to obtain a first data frame, where the first data frame includes a first frame type identifier, and the first frame type identifier indicates that an application message included in the first data frame is a complete application message; transmitting the first data frame to a receive end based on an established QUIC connection to the receive end, to enable the receive end to determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, where a target application runs on the receive end.
The solution provided in the first aspect may be applied to a transmit end in a communication system. The communication system includes the transmit end and a receive end. The transmit end is a communication device that sends data, and the transmit end may be a server, a terminal device, a virtual machine (VM), or a container. The receive end is a communication device that receives data, and the receive end may be a server, a terminal device, a virtual machine, or a container. A QUIC connection may be established between the transmit end and the receive end, and a data frame encapsulated with an application message is transmitted based on the established QUIC connection. The transmit end and the receive end may each include an application layer and a transport layer. A target application may run at the application layer, and the target application may perform data transmission based on an application layer protocol such as a Hypertext Transfer Protocol (HTTP). A QUIC entity may run at the transport layer of the transmit end. An entity represents any hardware or software process that can send or receive information and may be a software module. The QUIC entity may be an entity that executes a QUIC transport protocol.
A first application message needs to be encapsulated in a form of a complete application message. That the first application is encapsulated in a form of a complete application message means: the corresponding first application message is not segmented during encapsulation but is completely encapsulated into a data frame. In this solution, complete encapsulation of the first application message is implemented based on the first data frame. In an actual application, the transmit end may determine, based on a first frame type identifier, whether a corresponding data frame is the first data frame, and the receive end may determine, by identifying whether a received data frame includes the first frame type identifier, whether the data frame is the first data frame. A quantity of complete application messages included in the first data frame is not limited herein. One first data frame may include only one first application message or may include a plurality of first application messages. “A plurality or includes two or more, or may be described as at least two.
In the solution provided in the first aspect, a process of” establishing the QUIC connection between the transmit end and the receive end may be based on related content in the RFC 9000 document. In addition, a new transport parameter may be further added, and the transmit end and the receive end negotiate, based on the new transport parameter, whether the receive end has a capability of processing the first data frame. For example, if a new transport parameter is added to the QUIC transport protocol as a first parameter, in the process of establishing the QUIC connection between the transmit end and the receive end, if the transmit end receives first parameter information (for example, a value of the first parameter) sent by the receive end, the transmit end determines that the receive end has the capability of processing the first data frame. Therefore, after the QUIC connection is established, the transmit end may encapsulate the first application message to obtain the first data frame and may transmit the first data frame to the receive end.
In the solution provided in the first aspect, after obtaining the first application message generated by the target application of the transmit end, the transmit end encapsulates the first application message to obtain the first data frame, where the first data frame includes the first frame type identifier, and the first frame type identifier indicates that the application message included in the first data frame is a complete application message, that is, the first application message may be completely encapsulated into the first data frame, so that completeness of the first application message can still be maintained after the first application message is encapsulated into the first data frame. Therefore, when the first data frame is sent to the receive end based on the QUIC connection, complete information of the first application message is transmitted based on the first data frame. After receiving the first data frame, the receive end may determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, so as to conveniently obtain the complete first application message in the first data frame, and the receive end does not need to combine data frames and traverse combined information to search for boundaries of an application message to obtain the corresponding application message. In this way, information processing overheads can be reduced, and an information processing process of the receive end can be optimized.
In a possible implementation of the first aspect, the obtaining a first application message generated by a target application in the foregoing step includes: obtaining the first application message based on a target threshold and application data generated by the target application, where a size of the first application message does not exceed the target threshold.
In this possible implementation, the target threshold may be preset, and used to limit the size of the first application message, so as to ensure completeness of the first application message in a transmission process as much as possible and meet a requirement of the target application of the receive end for processing an application message. The target threshold may be determined by the QUIC entity of the transmit end, and then transferred to the target application of the transmit end.
In a possible implementation of the first aspect, the method further includes: receiving first parameter information sent by the receive end, where the first parameter information includes a maximum data amount of an application message that the target application of the receive end expects to receive; and determining the target threshold based on the first parameter information.
The first parameter may be preconfigured in the QUIC transport protocol as a transport parameter in the QUIC transport protocol, and the first parameter information may include a name and a value of the first parameter. The receive end may assign a value to the first parameter, so that the value of the first parameter is obtained, and then the receive end sends the value of the first parameter to the transmit end. The receive end may send the first parameter information to the transmit end in a process of establishing the QUIC connection between the receive end and the transmit end or may send the first parameter information to the transmit end after the QUIC connection between the receive end and the transmit end is established. The value of the first parameter may be a fixed value or may dynamically change based on a change status of a data processing resource of the target application. In an example, in the process of establishing the QUIC connection between the receive end and the transmit end, the receive end may send the first parameter information to the transmit end, to negotiate the capability of processing the first data frame and determine the first parameter information, so that the first application message generated by the transmit end meets the requirement of the target application of the receive end for processing the application message.
In a possible implementation of the first aspect, the method further includes: determining the target threshold based on second parameter information, where the second parameter information includes at least one of information about a flow control parameter, information about a path maximum transmission unit parameter of the transmit end, and information about a congestion window parameter of the transmit end.
In this possible implementation, the target threshold is determined based on at least one of the information about the flow control parameter, the information about the path maximum transmission unit parameter of the transmit end, and the information about the congestion window parameter of the transmit end, so that the transmit end can limit the size of the first application message based on the target threshold. In this way, the size of the first application message can meet a requirement on a data transmission capability in the QUIC connection, and a possibility of segmentation during transmission through the QUIC connection is reduced.
In a possible implementation of the first aspect, the method further includes: obtaining an updated target threshold; and obtaining a second application message based on the updated target threshold and the application data generated by the target application, where a size of the second application message does not exceed the updated target threshold, and the size of the second application message is different from the size of the first application message.
In this possible implementation, because the updated target threshold is different from the target threshold before the update, the size of the second application message is also different from the size of the first application message. The second application message obtained based on the updated target threshold also needs to be encapsulated in a form of a complete application message. Therefore, a data frame including the first frame type identifier may also be obtained by encapsulating the second application message. In this possible implementation, the target threshold may be dynamically updated, so that a size of an application message that needs to be completely encapsulated can also be dynamically adjusted, to improve a possibility that the application message remains complete in a data transmission process.
In a possible implementation of the first aspect, the foregoing step of encapsulating the first application message to obtain a first data frame includes: if the size of the first application message is not greater than that of a send window, encapsulating the first application message to obtain the first data frame, where the send window indicates an amount of data that can be sent by the transmit end based on the QUIC.
In this possible implementation, the size of the send window may be determined based on at least one of the flow control parameter, the path maximum transmission unit, and the congestion window. If the size of the send window is less than that of the first application message, even though the first application message is encapsulated in a form of a complete application message, the first application message is segmented due to limitation of the send window in a QUIC connection-based transmission process, and then segments are separately transmitted. Therefore, in this possible implementation, if the size of the first application message is not greater than that of the send window, the first application message is encapsulated to obtain the first data frame. In this case, in the QUIC connection-based transmission process, the first data frame is not limited by the send window, and therefore is not segmented, so that completeness of an application message in the first data frame can be ensured in the transmission process.
In a possible implementation of the first aspect, the first application message includes a first message identifier, and the first message identifier indicates to encapsulate the first application message in a form of a complete application message.
In this possible implementation, the first message identifier may be set in a header structure of the first application message, so that the QUIC entity of the transmit end identifies the first message identifier. Other application information different from the first application information may include a message identifier different from the first message identifier or may not include a message identifier. This possible implementation provides a feasible method for identifying the first application message.
In a possible implementation of the first aspect, the first application message is transferred from the target application to a QUIC entity at a transport layer through a first programming interface, and an application message transferred through the first programming interface is encapsulated in a form of a complete application message.
Layers in a network hierarchy of the transmit end usually interact with each other and provide services through interfaces. The target application is located at the application layer in the network hierarchy, and the QUIC entity that performs an operation related to the QUIC transport protocol is located at the transport layer in the network hierarchy. The first programming interface may be configured between the target application at the application layer and the QUIC entity at the transport layer, and the QUIC entity of the transmit end may use the application message received through the first programming interface as the first application message. An application message received by invoking the first programming interface once may be used as one first application message, and the size of the first application message is a size of the application message received by the QUIC entity through the first programming interface in the invoking. This possible implementation provides a feasible method for identifying the first application message.
In a possible implementation of the first aspect, the method further includes: obtaining a third application message generated by the target application; encapsulating the third application message to obtain a second data frame, where the second data frame does not include the first frame type identifier; and transmitting the second data frame to the receive end based on the established QUIC connection, to enable the receive end to identify boundaries of the third application message from the second data frame, to obtain the third application message.
In this possible implementation, the third application message may be segmented in the QUIC connection-based transmission process. That the second data frame does not include the first frame type identifier may mean: The second data frame does not include a frame type identifier, or the second data frame includes a second frame type identifier, where the second frame type identifier is different from the first frame type identifier. In this possible implementation, based on the QUIC connection established between the transmit end and the receive end, not only the first data frame but also the second data frame can be sent. Therefore, the target application of the transmit end may generate the first application message and the third application message based on scenario requirements, obtain the first data frame based on the first application message, and obtain the second data frame based on the third application message. This improves flexibility of processing the application messages by the target application and can meet requirements of the target application in different application scenarios.
In a possible implementation of the first aspect, the first data frame includes a first number, the second data frame includes a second number, and the first number and the second number correspond to a sequence in which the first application message included in the first data frame and the third application message included in the second data frame are generated by the target application.
In this possible implementation, to ensure that the application messages can be correctly restored by the receive end without byte disorder or the like after the application messages are encapsulated into the data frames and received by the receive end, correctness of a sequence between bytes of the first application message and bytes of the second application message needs to be ensured. In this case, the first number of the first data frame corresponding to the first application message and the second number of the second data frame corresponding to the second application message are obtained based on the sequence in which the first application message and the second application message are generated by the target application, so that the receive end can accurately determine the sequence between the bytes of the first application message and the bytes of the second application message, to obtain corresponding sequential application data.
In a possible implementation of the first aspect, the first data frame and the second data frame are included in a same QUIC packet.
The QUIC connection between the transmit end and the receive end transmits data such as a data frame by using a QUIC packet. For descriptions of the packet in the QUIC transport protocol, refer to the RFC 9000 document. In this possible implementation, a feasible manner of sending the first data frame and the second data frame is provided. In some scenarios, the first data frame and the second data frame may be included in the same QUIC packet for sending. Each time the transmit end sends a QUIC packet based on the QUIC connection, a size of the QUIC packet may be determined based on the size of the send window. In an example, the size of the send window is 200 bytes, a size of a first data frame A is 150 bytes, and a size of a second data frame B is 50 bytes. In this scenario, the first data frame A and the second data frame B may be included in a same QUIC packet for sending.
A second aspect may provide a data transmission method, including: receiving, based on an established QUIC connection to a transmit end, a first data frame sent by the transmit end, where the first data frame is obtained by the transmit end by encapsulating a first application message generated by a target application, the first data frame includes a first frame type identifier, the first frame type identifier indicates that an application message included in the first data frame is a complete application message, and target applications run on the transmit end and a receive end; and obtaining the first application message from the first data frame based on the first frame type identifier.
The solution provided in the second aspect is applied to a receive end corresponding to the transmit end in the first aspect. The receive end may be a physical machine (for example, a terminal device or a server), or may be a virtual machine or a container. For a feature that is in the second aspect and that is the same as that in the first aspect, refer to the descriptions of the first aspect for understanding.
In the solution provided in the second aspect, after receiving the first data frame, the receive end may determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, so as to conveniently obtain the complete first application message in the first data frame, and the receive end does not need to combine data frames and traverse combined information to search for boundaries of an application message to obtain the corresponding application message. In this way, information processing overheads can be reduced, and an information processing process of the receive end can be optimized.
In a possible implementation of the second aspect, the method further includes: sending first parameter information to the transmit end, where the first parameter information includes a maximum data amount of an application message that the target application of the receive end expects to receive, the first parameter information is used by the transmit end to determine a target threshold, and a size of the first application message does not exceed the target threshold.
In this possible implementation, a first parameter may be preconfigured in a QUIC transport protocol as a transport parameter in the QUIC transport protocol, and the first parameter information may include a name and a value of the first parameter. The receive end may assign a value to the first parameter, so that the value of the first parameter is obtained, and then the receive end sends the value of the first parameter to the transmit end. The receive end may send the first parameter information to the transmit end in a process of establishing the QUIC connection between the receive end and the transmit end or may send the first parameter information to the transmit end after the QUIC connection between the receive end and the transmit end is established. The value of the first parameter may be a fixed value or may dynamically change based on a change status of a data processing resource of the target application. In an example, in the process of establishing the QUIC connection between the receive end and the transmit end, the receive end may send the first parameter information to the transmit end, to negotiate the capability of processing the first data frame and determine the first parameter information, so that the first application message generated by the transmit end meets the requirement of the target application of the receive end for processing the application message.
In a possible implementation of the second aspect, after the obtaining the first application message from the first data frame based on the first frame type identifier, the method further includes: transferring the obtained first application message to the target application of the receive end through a first programming interface.
In this possible implementation, the first programming interface may be configured between the target application at an application layer of the receive end and a QUIC entity at a transport layer of the receive end, and the target application of the receive end may determine data obtained through the first programming interface as the received first application message. The first programming interface of the receive end may be configured to transfer only the first application message, so that the target application of the receive end can determine that the information received through the first programming interface is a complete application message and does not need to search the information for boundaries of the application message. In this way, efficiency of processing the application message by the receive end can be improved.
In a possible implementation of the second aspect, the method further includes: receiving, based on the established QUIC connection, a second data frame sent by the transmit end, where the second data frame is obtained by encapsulating a third application message generated by the target application of the transmit end, and the second data frame does not include the first frame type identifier; and identifying boundaries of the third application message from the second data frame, to obtain the third application message.
The third application message may be segmented in a QUIC connection-based transmission process. That the second data frame does not include the first frame type identifier may mean: The second data frame does not include a frame type identifier, or the second data frame includes a second frame type identifier, where the second frame type identifier is different from the first frame type identifier. In this possible implementation, based on the QUIC connection established between the transmit end and the receive end, not only the first data frame but also the second data frame can be sent. Therefore, the target application of the transmit end may generate the first application message and the third application message based on scenario requirements, obtain the first data frame based on the first application message, and obtain the second data frame based on the third application message. This improves flexibility of processing the application messages by the target application and can meet requirements of the target application in different application scenarios.
In a possible implementation of the second aspect, the first data frame and the second data frame each include a frame type identifier field, the frame type identifier field of the first data frame includes the first frame type identifier, the frame type identifier field of the second data frame includes a second frame type identifier, and the second frame type is different from the first frame type identifier.
In the QUIC transport protocol, a structure of a frame may include a plurality of fields. For example, fields that respectively indicate a length, content, a frame type of a corresponding frame, and an ID of a stream (stream) in which the frame is located may exist. A frame type identifier field may exist. A value of the frame type identifier field is used to determine the frame type of the corresponding frame, and the value of the frame type identifier field may be used as a corresponding frame type identifier. In the embodiments, structures of the first data frame and the second data frame may be the same, in other words, structures (for example, field meanings, locations in the data frames, and field lengths) of included fields may be the same, but values of frame type identifier fields used to determine frame types are different. In this possible implementation, the frame type of the data frame may be identified based on the value of the frame type identifier field.
A third aspect may provide a transmit end apparatus for data transmission. The transmit end apparatus has a function of implementing the method in any one of the first aspect or the possible implementations of the first aspect. The function may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the foregoing function, for example, an application module and a QUIC module.
A fourth aspect may provide a receive end apparatus for data transmission. The receive end apparatus has a function of implementing the method in any one of the second aspect or the possible implementations of the second aspect. The function may be implemented by hardware or may be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the foregoing function, for example, an application module and a QUIC module.
A fifth aspect may provide a non-transitory computer-readable storage medium storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor performs the method according to any one of the first aspect or the possible implementations of the first aspect.
A sixth aspect may provide a non-transitory computer-readable storage medium storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor performs the method according to any one of the second aspect or the possible implementations of the second aspect.
A seventh aspect may provide a computer program product storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor performs the method according to any one of the first aspect or the possible implementations of the first aspect.
An eighth aspect may provide a computer program product storing one or more computer-executable instructions. When the computer-executable instructions are executed by a processor, the processor performs the method according to any one of the second aspect or the possible implementations of the second aspect.
For effects brought by any one of the third aspect, the fifth aspect, and the seventh aspect or the possible implementations thereof, refer to effects brought by the first aspect or the different possible implementations of the first aspect. For effects brought by any one of the fourth aspect, the sixth aspect, and the eighth aspect or the possible implementations thereof, refer to effects brought by the second aspect or the different possible implementations of the second aspect. Details are not described herein again.
The following describes embodiments with reference to the accompanying drawings. It is clear that the described embodiments are merely some but not all of embodiments. A person of ordinary skill in the art may understand that, with the emergence of a new scenario, the embodiments are also applicable to a similar problem.
In the embodiments and accompanying drawings, the terms “first”, “second”, and the like are intended to distinguish between similar objects but do not necessarily indicate an order or sequence. It should be understood that the data termed in such a way are interchangeable in an appropriate circumstance, so that embodiments described herein can be implemented in another order other than the order illustrated or described herein. In addition, the terms “include” and “have,” and any other variants, are intended to cover the non-exclusive inclusion. For example, a process, method, system, product, or device that includes a list of steps or units is not necessarily limited to those expressly listed steps or units but may include other steps or units not expressly listed or inherent to such a process, method, product, or device.
The embodiments may provide a data transmission method, to resolve a problem in current QUIC transport protocol-based data transmission that a processing process is complex because a receive end may need to perform a boundary check each time the receive end receives data. The embodiments may further provide a corresponding apparatus, computer device, computer-readable storage medium, computer program product, and the like. Details are separately described below.
A QUIC transport protocol is an Internet transport layer protocol. For related descriptions of the QUIC transport protocol, refer to the RFC 9000 document.
The data transmission method provided in the embodiments may be applied to various QUIC transport protocol-based communication systems, for example, a computer network, a global system for mobile communications (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunications system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, and a 5G communication system.
The communication system includes a transmit end and the receive end. A QUIC connection may be established between the transmit end and the receive end.
The transmit end is a communication device that sends data, and the receive end is a communication device that receives data. The transmit end may be a terminal device, or may be a server, a virtual machine (VM), or a container. The receive end may be a terminal device, or may be a server, a virtual machine (VM), or a container.
For example, the terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wireless terminal in an internet of things (IoT), or the like.
It should be noted that the transmit end and the receive end are relative concepts. For example, when a first communication device sends data to a second communication device, the first communication device is a transmit end, and the second communication device is a receive end. When the second communication device sends data to the first communication device, the second communication device is a transmit end, and the first communication device is a receive end. When the first communication device sends data to the second communication device and receives data sent by the second communication device, both the first communication device and the second communication device are a transmit end and a receive end. The data sent by the transmit end may include application data generated by a target application.
In an example, the transmit end and the receive end may be connected via an intermediate device. For example, in a scenario shown in
In another example, as shown in
A network architecture of the transmit end and receive end generally complies with a hierarchical model, for example, an open systems interconnection (OSI) reference model. As shown in
An embodiment of the data transmission method may be applied to the foregoing communication system. The following describes the data transmission method n with reference to the accompanying drawings. As shown in
101: A transmit end obtains a first application message generated by a target application.
The target application is an application running at an application layer. A type of the target application, a used application protocol, and the like are not limited herein. Target applications may run on the transmit end and a receive end. Application information of the target application of the transmit end may be sent to the target application of the receive end through a QUIC connection established between the transmit end and the receive end.
A type of data included in the first application message is not limited herein.
In embodiments, the target application may generate the first application message based on application data, and then a QUIC entity of the transmit end obtains the first application message from the target application. An entity represents any hardware or software process that can send or receive information and may be a software module. The QUIC entity may be an entity that executes a QUIC transport protocol.
In the embodiments, the first application message may need to be encapsulated in a form of a complete application message. That the first application is encapsulated in a form of a complete application message means: the corresponding first application message is not segmented during encapsulation but is completely encapsulated into a data frame. The target application may identify, based on a particular identifier, an application message that needs to be encapsulated in a form of a complete application message, so that when receiving the application message, the QUIC entity may determine, based on the particular identifier, that the first application message is received. In addition, the target application may further transfer, to the QUIC entity through a particular interface, the application message that needs to be encapsulated in a form of a complete application message, so that when receiving the application message through the particular interface, the QUIC entity may determine, based on the particular interface, that the first application message is received. In addition, the QUIC entity may determine, in another manner, that the first application message is received. For example, the target application may transfer notification information to the QUIC entity in advance, where the notification information is used to notify the QUIC entity that all application messages sent by the target application are first application messages.
The target application may determine, based on factors such as a scenario, a size of an application message, and a type of an application message, messages that each need to be encapsulated in a form of a complete application message. For example, the target application may use a control message as the first application message and use application messages obtained by segmenting a large file such as an image, a video, or a document as application messages that do not need to be encapsulated in a form of complete application messages. Alternatively, the target application may use application data whose size is less than a specified threshold as the first application message and use application data whose size is greater than the specified threshold as an application message that does not need to be encapsulated in a form of a complete application message. A manner in which the target application generates the first application message is not limited herein.
Obtaining the first application message from the target application may be a general description. Other processing may be further performed on the first application message. For example, in an actual processing process, the first application message generated by the target application may be stored in a send buffer, and the QUIC entity may read the first application message from the send buffer. In addition, in this example, when the first application message is stored in the send buffer, different first application messages may be separately stored in different storage nodes. For example, if a storage structure of the send buffer is a linked storage structure, each first application message may be stored in the send buffer as an independent linked list node, and different first application messages correspond to different linked list nodes.
102: The transmit end encapsulates the first application message to obtain a first data frame.
The first data frame includes a first frame type identifier, and the first frame type identifier indicates that an application message included in the first data frame is a complete application message.
The first frame type identifier may indicate that the application message included in the first data frame is a complete application message. Therefore, the first application information included in the first data frame is complete and is not segmented into different data frames. A quantity of complete application messages included in the first data frame is not limited herein. One first data frame may include only one first application message or may include a plurality of first application messages. Complete encapsulation of the first application message may be implemented based on the first data frame.
If one first application message is correspondingly encapsulated into one first data frame so that one first data frame corresponds to one first application message, when the receive end detects the first frame type identifier, an application message obtained by decapsulating the first data frame is a complete first application message, and the receive end does not need to obtain the first application message by identifying boundary information of the included application message from the decapsulated data.
If one first data frame includes a plurality of first application messages, the first data frame may not only include the first frame type identifier, but also record, in a specified field of a header structure of the first data frame, an offset (offset) of each first application message in the first data frame and/or length information of each first application message. After receiving the first data frame, if identifying the first frame type identifier, the receive end may read the offset of each first application message in the first data frame and/or the length information from the specified field in the header structure, so that the receive end completely extracts each first application message in the first data frame based on the offset and/or the length information.
For a data structure of the first data frame, refer to a structure of a frame in the RFC 9000 document. A frame type in the RFC 9000 document may include a data frame (for example, a STREAM frame) and a control frame (for example, an ACK frame, a PADDING frame, an RST_STREAM frame, or a PING frame). In an example, the data structure of the first data frame may be the same as that of the STREAM frame in the RFC 9000 document, field meaning, locations in the data frame, field lengths, and the like of fields in the first data frame may be the same as those of the STREAM frame. Values of the fields in the first data frame may be the same as or different from those in the STREAM frame. For example, values of frame type identifier fields used to determine frame types may be different. Additionally, in another example, the data structure of the first data frame may alternatively be another structure different from that of the STREAM frame.
103: The transmit end transmits the first data frame to the receive end based on the established QUIC connection to the receive end.
For a process of establishing the QUIC connection between the transmit end and the receive end, refer to the RFC 9000 document. In the embodiments, the transmit end and the receive end may establish the QUIC connection based on related content in the RFC 9000 document. In addition, a new transport parameter may be further added, and the transmit end and the receive end negotiate, based on the new transport parameter, whether the receive end has a capability of processing the first data frame. For example, if a new transport parameter is added to the QUIC transport protocol as a first parameter, in the process of establishing the QUIC connection between the transmit end and the receive end, if the transmit end receives first parameter information (for example, a value of the first parameter) sent by the receive end, the transmit end determines that the receive end has the capability of processing the first data frame. Therefore, after the QUIC connection is established, the transmit end may encapsulate the first application message to obtain the first data frame and may transmit the first data frame to the receive end.
The transmit end may directly transmit the first data frame to the receive end or may transmit the first data frame to the receive end via an intermediate device such as a router.
104: The receive end receives, based on the established QUIC connection to the transmit end, the first data frame sent by the transmit end.
The first data frame sent by the transmit end may be received by the QUIC entity of the receive end.
105: The receive end obtains the first application message from the first data frame based on the first frame type identifier.
The receive end may determine, based on the first frame type identifier, that the received data frame is the first data frame, so as to determine that an application message included in the received data frame is a complete application message.
The first application message may be obtained from the first data frame via the QUIC entity of the receive end.
After receiving the first data frame, the receive end may decapsulate the first data frame based on the data structure corresponding to the first data frame, to obtain the application message encapsulated in the first data frame. When decapsulating the first data frame, the receive end may read the first frame type identifier that is in the first data frame. Therefore, the receive end may determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, so that the corresponding first application message can be conveniently obtained from the first data frame. For example, if one first data frame corresponds to one first application message, the application message obtained by decapsulating the first data frame may be determined as one first application message. If the first data frame includes a plurality of complete first application messages, each corresponding first application message may be conveniently obtained from the first data frame based on the offset of each first application message in the header structure of the first data frame.
In some examples, after obtaining the first application message, the receive end may store the obtained first application message in a receiving buffer. If the first application message and an application message that is recently transferred to the target application of the receive end are consecutive application messages, the QUIC entity of the receive end reads the first application message from the receiving buffer and transfers the first application message to the target application of the receive end. That the first application message and an application message that is recently transferred to the target application of the receive end are consecutive application messages means: the transmit end generates the first application message in a sequence next to generating the application message that is recently transferred to the target application of the receive end.
In this example, when the first application message obtained by the receive end is stored in the receiving buffer, different first application messages may be separately stored in different storage nodes. For example, if a storage structure of the receiving buffer is a linked storage structure, each received first application message may be stored in the receiving buffer as an independent linked list node, and different first application messages correspond to different linked list nodes.
In some other examples, if the QUIC entity of the receive end receives indication instructions of the target application of the receive end, each time the QUIC entity of the receive end obtains the first application message, the QUIC entity of the receive end may directly send the obtained first application message to the target application of the receive end, and does not need to store the first application message in a receiving buffer. The indication instructions may instruct the QUIC entity of the receive end to directly transmit the first data frame to the target application of the receive end after obtaining the first application message. In this way, processing efficiency can be improved in a scenario in which a requirement on ensuring a data packet sequence is low, for example, a video live broadcast scenario.
When the QUIC entity of the receive end transfers the obtained first application message to the target application of the receive end, to maintain completeness of the first application message, the QUIC entity of the receive end may transfer each first application message by using a different event, or may transfer different first application messages by using a same event, where the different first application messages are distinguished based on different identifiers in the same event. Alternatively, the target application of the receive end may obtain different first application messages by invoking a callback function.
After obtaining the first application message generated by the target application of the transmit end, the transmit end may completely encapsulate the first application message into the first data frame, so that completeness of the first application message can still be maintained after the first application message is encapsulated into the first data frame. Therefore, when the first data frame is sent to the receive end based on the QUIC connection, complete information of the first application message is transmitted based on the first data frame. After receiving the first data frame, the receive end may determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, so as to conveniently obtain the complete first application message in the first data frame, and the receive end does not need to combine data frames and traverse combined information to search for boundaries of an application message to obtain the corresponding application message. In this way, information processing overheads can be reduced, and an information processing process of the receive end can be optimized.
Optionally, step 101 may include:
obtaining the first application message based on a target threshold and application data generated by the target application, where a size of the first application message does not exceed the target threshold.
A type and a generation manner of the application data are not limited herein. For example, the application data may include at least one of control information, text information, image information, and audio information. The application data may be data generated in a running process of the target application of the transmit end, may be data locally obtained by the target application from the transmit end, or may be data obtained by the target application of the transmit end from another device.
In embodiments of this application, to ensure completeness of the first application message in a subsequent transmission process as much as possible and meet a requirement of the target application of the receive end for processing an application message, the target threshold may be preset to limit the size of the first application message.
The target threshold may be determined by the QUIC entity of the transmit end, and then transferred to the target application of the transmit end.
A manner of determining the target threshold may include but is not limited to at least one of the following two manners.
1. In an embodiment, the target threshold is determined based on the first parameter information.
The first parameter information includes a maximum data amount of an application message that the target application of the receive end expects to receive.
The first parameter information may be information preconfigured in the target application of the receive end or may be determined based on information such as a size of a processing resource allocated by the target application of the receive end to the application message.
Optionally, as shown in
201: The receive end sends the first parameter information to the transmit end.
202: The transmit end receives the first parameter information sent by the receive end.
203: The transmit end determines the target threshold based on the first parameter information.
In some examples, the first parameter may be preconfigured in the QUIC transport protocol as a transport parameter in the QUIC transport protocol, and the first parameter information may include a name and a value of the first parameter. The receive end may assign a value to the first parameter, so that the value of the first parameter is obtained, and then the receive end sends the value of the first parameter to the transmit end. The receive end may send the first parameter information to the transmit end in a process of establishing the QUIC connection between the receive end and the transmit end or may send the first parameter information to the transmit end after the QUIC connection between the receive end and the transmit end is established. The value of the first parameter may be a fixed value or may dynamically change based on a change status of a data processing resource of the target application. Each time the receive end detects that the value of the first parameter changes, the receive end may send an updated value of the first parameter to the transmit end.
In the process of establishing the QUIC connection between the receive end and the transmit end, the receive end may send the first parameter information to the transmit end, to negotiate the capability of processing the first data frame and determine the first parameter information, so that the first application message generated by the transmit end meets the requirement of the target application of the receive end for processing the application message.
For the process of establishing the QUIC connection between the receive end and the transmit end, refer to the RFC 9000 document. In this example, the first parameter may be a transport parameter newly defined in the QUIC transport protocol. In the QUIC transport protocol, a definition and a processing rule of the first parameter may be preconfigured. For example, an occasion and a manner of declaring the first parameter in the process of establishing the QUIC connection between the receive end and the transmit end are configured. In an example, the receive end may send, to the transmit end in an encryption handshake phase, a declaration carrying the first parameter. The declaration may include the value of the first parameter of the receive end. If the transmit end receives the declaration of the first parameter, the transmit end may determine that the receive end has a capability of identifying and processing a data frame including the first frame type identifier, and the transmit end may determine the value of the first parameter of the receive end, and determine the target threshold based on the value of the first parameter, so that the target application of the transmit end can limit a size of application information based on the value of the first parameter, and the application message can be encapsulated into a first data frame that meets the requirement of the target application of the receive end.
2. In an embodiment, the target threshold is determined based on second parameter information.
The second parameter information includes at least one of information about a flow control parameter, information about a path maximum transmission unit parameter of the transmit end, and information about a congestion window parameter of the transmit end.
The flow control parameter is a parameter related in a flow control (flow control) process. The flow control parameter may include a size, namely, an amount of data that can be received in the receiving buffer, of an idle space in the receiving buffer corresponding to the QUIC entity of the receive end. Information such as a value of the flow control parameter may be sent by the receive end to the transmit end. The receive end may dynamically send the value of the flow control parameter to the transmit end based on a change of a size of the receiving buffer. It can be understood that the information about the flow control parameter in the transmit end may be dynamically updated.
In a network connection, in a period of time, if a requirement on resources (such as a link capacity, and a buffer and a processor in a switching node such as a router) in a network is greater than an available resource, congestion is caused. Therefore, in the QUIC transport protocol, a congestion control algorithm is used to avoid network congestion. The congestion control algorithm may be used to control a size of a congestion window, to control a data sending amount based on the size of the congestion window, so that congestion control is implemented. In embodiments, the congestion control algorithm used in the QUIC transport protocol is not limited. For example, the congestion control algorithm may be a NewReno congestion control algorithm described in RFC 5681 or RFC 6582 or may be a cubic congestion control algorithm described in RFC 8312. Further, another algorithm may be selected as the congestion control algorithm based on a scenario requirement. The congestion control algorithm may be executed by the transmit end, and the size of the congestion window determined based on the congestion control algorithm may be considered as information about a local parameter of the transmit end.
The path maximum transmission unit (PMTU) may refer to a maximum size of an internet protocol (IP) packet. In the embodiments, to avoid fragmentation of a QUIC packet in a transmission process at a network layer, a data link layer, or the like, the size of the first application message generated by the target application needs to be limited based on the path maximum transmission unit, so as to ensure that the first application message is not fragmented and is completely encapsulated into the first data frame in the transmission process. The path maximum transmission unit may be determined based on a maximum transmission unit (MTU) of each of at least one transmission node on a transmission path on which the application message is transmitted from the transmit end to the receive end. The at least one transmission node may include at least one of the application layer of the transmit end, a data transport layer of the transmit end, and an intermediate device such as a router on a QUIC connection-based transmission path between the transmit end and the receive end. A size of the path maximum transmission unit may be determined based on a characteristic of the transmission path. Therefore, generally, the size of the path maximum transmission unit may dynamically change based on a change of the transmission path.
Because the flow control parameter, the path maximum transmission unit parameter of the transmit end, and the congestion window of the transmit end can reflect a data transmission capability in the QUIC connection, the target threshold is determined based on at least one of the information about the flow control parameter, the information about the path maximum transmission unit parameter of the transmit end, and the information about the congestion window parameter of the transmit end, so that the transmit end can limit the size of the first application message based on the target threshold. In this way, the size of the first application message can meet a requirement on the data transmission capability in the QUIC connection, and a possibility of segmentation during transmission through the QUIC connection is reduced.
It should be noted that the target threshold may be determined only based on the first parameter information, or may be determined only based on at least one of the information about the flow control parameter, the information about the path maximum transmission unit parameter of the transmit end, and the information about the congestion window parameter of the transmit end, or may be determined based on at least one of the first parameter information, the information about the flow control parameter, the information about the path maximum transmission unit parameter of the transmit end, and the information about the congestion window parameter of the transmit end. In addition, a factor for determining the target threshold is not limited thereto. In some examples, the target threshold may be alternatively determined based on a factor such as limitation on an encapsulation format of the QUIC packet.
Optionally, in an embodiment, the method further includes:
obtaining an updated target threshold; and
obtaining a second application message based on the updated target threshold and the application data generated by the target application, where a size of the second application message does not exceed the updated target threshold, and the size of the second application message is different from the size of the first application message.
The target threshold may be dynamically updated. The transmit end may actively and periodically obtain parameter information (for example, the first parameter information and/or the second parameter information) related to the target threshold, to determine whether to update the target threshold based on the parameter information related to the target threshold. Alternatively, the transmit end may passively update the target threshold based on updated first parameter information and/or updated second parameter information after receiving an update message of, for example, the first parameter information and/or the second parameter information. After obtaining the updated target threshold, the transmit end may obtain the second application message based on the updated target threshold and the application data generated by the target application. Because the updated target threshold is different from the target threshold before the update, the size of the second application message is also different from the size of the first application message. The second application message obtained based on the updated target threshold also needs to be encapsulated in a form of a complete application message. Therefore, a data frame including the first frame type identifier may also be obtained by encapsulating the second application message. For processing of the second application message, refer to processing of the first application message in another embodiment Details are not described herein again. In embodiments, the target threshold may be dynamically updated, so that a size of an application message that needs to be completely encapsulated can also be dynamically adjusted, to improve a possibility that the application message remains complete in a data transmission process.
Optionally, in some embodiments, the foregoing step 102 may include:
if the size of the first application message is not greater than that of a send window, encapsulating the first application message to obtain the first data frame, where the send window indicates an amount of data that can be sent by the transmit end based on the QUIC.
The size of the send window may be determined based on at least one of the flow control parameter, the path maximum transmission unit, and the congestion window.
In actual application, the size of the send window may dynamically change in real time with parameters such as the flow control parameter, the path maximum transmission unit, and the congestion window. In addition, update frequency of the parameters such as the flow control parameter, the path maximum transmission unit, and the congestion window may be high. In some cases, when the first application message is generated, the size of the first application message is limited based on the parameter related to the send window. However, because the update frequency of the parameter related to the send window is high, a size of a send window that exists before the first application message is generated may be different from a size of a send window that exists when the first application message is encapsulated. If the size of the send window is less than that of the first application message, even though the first application message is encapsulated in a form of a complete application message, the first application message is segmented due to limitation of the send window in a QUIC connection-based transmission process, and then segments are separately transmitted. Therefore, in this possible implementation, if the size of the first application message is not greater than that of the send window, the first application message is encapsulated to obtain the first data frame. In this case, in the QUIC connection-based transmission process, the first data frame is not limited by the send window, and therefore is not segmented, so that completeness of an application message in the first data frame can be ensured in the transmission process.
In some examples, if the size of the first application message is greater than that of the send window, the first application information cannot be completely sent in current data transmission due to limitation of the send window. Consequently, the first application message cannot be encapsulated into the first data frame. Instead, the first application message is encapsulated into data frames of another frame type. When the first application message is encapsulated into the data frames of another frame type, to meet a limitation condition of the send window, the first application message needs to be segmented, and different parts of the first application message are encapsulated into different data frames for transmission.
Optionally, a manner of identifying the first application message may include but is not limited to the following two types.
1. In an embodiment, the first application message includes a first message identifier, and the first message identifier indicates to encapsulate the first application message in a form of a complete application message.
The first message identifier may be set in a header structure of the first application message, so that the QUIC entity of the transmit end identifies the first message identifier. Other application information different from the first application information may include a message identifier different from the first message identifier or may not include a message identifier.
2. In another embodiment, the first application message is transferred from the target application to the QUIC entity at the transport layer through a first programming interface, and an application message transferred through the first programming interface is encapsulated in a form of a complete application message.
Layers in a network hierarchy of the transmit end usually interact with each other and provide services through interfaces. The target application is located at the application layer in the network hierarchy, and the QUIC entity that performs an operation related to the QUIC transport protocol is located at the transport layer in the network hierarchy. The first programming interface may be configured between the target application at the application layer and the QUIC entity at the transport layer, and the QUIC entity of the transmit end may use the application message received through the first programming interface as the first application message. An application message received by invoking the first programming interface once may be used as one first application message, and the size of the first application message is a size of the application message received by the QUIC entity through the first programming interface in the invoking.
It should be noted that the first message identifier or the first programming interface represents an indication of an encapsulation manner of the target application of the transmit end for the first application message, and the indication indicates that the target application of the transmit end expects the first application message to be encapsulated in a form of a complete application message. However, generally, there is no limited requirement that the first application message can be encapsulated only in a form of a complete application message. For example, when the first application message is encapsulated, if it is detected that the size of the send window is updated to a value less than the size of the first application message, the first application message may be encapsulated in a form of another data frame different from the first data frame, and the first application message is no longer required to be encapsulated in a form of a complete application message.
Optionally, in some embodiments, the transmit end may further send another data frame other than the first data frame.
As shown in
301: A transmit end obtains third application messages generated by a target application.
The third application messages may be obtained through segmentation in a QUIC connection-based transmission process.
The target application of the transmit end may determine, based on information such as a type and a size of application information, whether to generate a first application message based on application data or generate the third application message based on application data, or generate both the first application message and the third application message.
For example, in a scenario, if current to-be-transmitted application data is a large file, image, or video, in a transmission process, the application data needs to be segmented into a plurality of application messages for transmission, and each segmented application message is a string of bytes without another data structure. After receiving the plurality of application messages, a receive end needs to combine the plurality of application messages to obtain the corresponding file, image, or video. In this case, completeness of each application message does not need to be specially maintained during transmission. In this case, the target application of the transmit end may obtain the third application messages based on the application data corresponding to the large file, image, or video.
If current to-be-transmitted application data is a control message of the target application of the transmit end, the target application may obtain the first application message based on the control message, to expect to maintain a complete data structure of the control message and maintain completeness of the control message in a QUIC transmission process, so that a target application of a receive end can conveniently obtain a complete application message, thereby reducing processing overheads.
302: The transmit end encapsulates the third application messages to obtain second data frames.
The second data frame does not include a first frame type identifier. This may mean that the second data frame does not include a frame type identifier, or the second data frame includes a second frame type identifier, where the second frame type identifier is different from the first frame type identifier.
For example, a frame type of the second data frame may be a frame type defined in the QUIC transport protocol, for example, a STREAM frame. Alternatively, the second data frame may be of another frame type extended based on the QUIC transport protocol. This is not limited in the embodiments.
Before the transmit end encapsulates the third application messages, the third application messages may be combined and stored in a send buffer of the transmit end. The “combined and stored” may mean that the third application messages are stored in a same storage node. After the plurality of third application messages are combined and stored, the combined and stored data is segmented based on a constraint condition such as a send window, to obtain the second data frames.
303: The transmit end transmits the second data frames to the receive end based on an established QUIC connection.
304: The receive end receives, based on the established QUIC connection, the second data frames sent by the transmit end.
305: The receive end identifies boundaries of the third application messages from the second data frames, to obtain the third application messages.
After obtaining the second data frames, a QUIC entity of the receive end may store the second data frames in a receiving buffer. In the receiving buffer, based on a sequence in which the third application messages respectively corresponding to the second data frames are generated on the transmit end, an arrangement sequence of the second data frames during combination may be determined, and a sequence in which the second data frames in the receiving buffer are sent to the target application of the receive end may be determined. Generally, the sequence in which the second data frames in the receiving buffer are sent to the target application of the receive end is consistent with the generation sequence of the third application messages corresponding to the second data frames. In other words, the second data frames in the receiving buffer are generally uploaded strictly in the generation sequence of the third application messages.
After receiving the third data frame transferred by the QUIC entity of the receive end, the target application of the receive end identifies the boundaries of the third application messages from the second data frames, to obtain the third application messages. The second data frames are obtained by segmenting the combined and stored data based on the constraint condition such as the send window after the plurality of third application messages are combined and stored. In this case, it is difficult to record segmentation manners of the third application messages in the second data frames. Therefore, after receiving the second data frames, the receive end needs to identify the boundaries of the included third application messages in the second data frames, so as to obtain the corresponding third application messages.
Based on a QUIC connection established between a transmit end and a receive end, not only a first data frame but also a second data frame can be sent. Therefore, a target application of the transmit end may generate a first application message and a third application message based on scenario requirements, obtain the first data frame based on the first application message, and obtain the second data frame based on the third application message. This improves flexibility of processing the application messages by the target application and can meet requirements of the target application in different application scenarios.
In some embodiments, the first data frame includes a first number, the second data frame includes a second number, and the first number and the second number correspond to a sequence in which the first application message included in the first data frame and the third application message included in the second data frame are generated by the target application.
The target application may generate the first application message and the third application message. To help the receive end identify a sequence of the application information and help the target application of the receive end process the application messages, the first data frame corresponding to the first application message and the second data frame corresponding to the third application message may be numbered based on the generation sequence of the first application message and the third application message, to obtain the first number of the first data frame and the second number of the second data frame.
To ensure that the application messages can be correctly restored by the receive end without byte disorder or the like after the application messages are encapsulated into the data frames and received by the receive end, correctness of a sequence between bytes of the first application message and bytes of the second application message needs to be ensured. In this case, the first number of the first data frame corresponding to the first application message and the second number of the second data frame corresponding to the second application message are obtained based on the sequence in which the first application message and the second application message are generated by the target application, so that the receive end can accurately determine the sequence between the bytes of the first application message and the bytes of the second application message, to obtain corresponding sequential application data.
In some examples, the first application message and the third application message may be associated information. For example, the first application message and the second application message may be different parts in a file. In this case, the first application message and the second application message are messages that are associated with each other. Therefore, after receiving the first application message and the second application message, the receive end needs to determine the sequence between the bytes of the first application message and the bytes of the second application message, to determine an association between the first application message and the second application message. To help the receive end identify the first application message and the third application message that are associated with each other, the first data frame corresponding to the first application message and the second data frame corresponding to the third application message that are associated with the first application message may be included in a same stream. In addition, correctness of a sequence relationship between the bytes of the first application message and the bytes of the second application message is ensured based on numbers in the same stream. Each stream may be identified based on an ID field in the stream. For details about a stream, refer to the RFC 9000 document.
Optionally, the first data frame and the second data frame are included in a same QUIC packet.
The QUIC connection between the transmit end and the receive end transmits data such as a data frame by using a QUIC packet. For descriptions of the packet (packet) in the QUIC transport protocol, refer to the RFC 9000 document. In embodiments, a feasible manner of sending the first data frame and the second data frame is provided. In some scenarios, the first data frame and the second data frame may be included in the same QUIC packet for sending. Each time the transmit end sends a QUIC packet based on the QUIC connection, a size of the QUIC packet may be determined based on a size of the send window. In an example, the size of the send window is 200 bytes, so that the size of the QUIC packet cannot exceed 200 bytes. A size of a first data frame A1 is 150 bytes, and a size of a second data frame B1 is 50 bytes. In this scenario, the first data frame A1 and the second data frame B1 may be included in a same QUIC packet for sending.
Additionally, in some other scenarios, a QUIC packet may include only the first data frame or only the second data frame. For example, if the size of the send window is 200 bytes, the size of the QUIC packet cannot exceed 200 bytes. However, a size of a first data frame A2 is 150 bytes, and a size of a second data frame B2 is 80 bytes. In this scenario, if the first data frame A2 and the second data frame B2 are included in a same QUIC packet, a size of the QUIC packet exceeds that of the send window. Consequently, the QUIC packet is segmented during transmission, and completeness of an application message in the first data frame A2 cannot be ensured. Therefore, in this scenario, a QUIC packet C1 may include the first data frame for sending, and when a QUIC packet C2 is sent next time based on the QUIC connection, the QUIC packet C2 includes the second data frame B2 for sending.
Optionally, after the receive end obtains the first application message from the first data frame based on the first frame type identifier, the method further includes the following step.
The receive end transfers the obtained first application message to the target application of the receive end through a first programming interface.
The first programming interface may be configured between the target application at an application layer of the receive end and a QUIC entity at a transport layer of the receive end, and the target application of the receive end may determine data obtained through the first programming interface as the received first application message. The first programming interface of the receive end may be configured to transfer only the first application message, so that the target application of the receive end can determine that the information received through the first programming interface is a complete application message and does not need to search the information for boundaries of the application message. In this way, efficiency of processing the application message by the receive end can be improved. In addition, another programming interface different from the first programming interface may be further configured between the QUIC entity of the receive end and the target application of the receive end, to transmit a data frame that does not include the first frame type identifier.
Optionally, in some embodiments, the first data frame and the second data frame each include a frame type identifier field, the frame type identifier field of the first data frame includes the first frame type identifier, the frame type identifier field of the second data frame includes a second frame type identifier, and the second frame type is different from the first frame type identifier.
In the QUIC transport protocol, a structure of a frame may include a plurality of fields. For example, fields that respectively indicate a length, content, a frame type of a corresponding frame, and an ID of a stream in which the frame is located may exist. A frame type identifier field may exist. A value of the frame type identifier field is used to determine the frame type of the corresponding frame, and the value of the frame type identifier field may be used as a corresponding frame type identifier. In embodiments, structures of the first data frame and the second data frame may be the same, in other words, structures (for example, field meanings, locations in the data frames, and field lengths) of included fields may be the same, but values of frame type identifier fields used to determine frame types are different. In this way, the frame type of the data frame may be identified based on the value of the frame type identifier field.
For example, if the second data frame is a STREAM frame (STREAM Frame) in the QUIC, an example structure of the second data frame is as follows:
“Type” is a frame type identifier field that describes a frame type, and a second frame type identifier of the second data frame may be 0x08 . . . 0x0f. “Stream ID” is a field describing an ID of a stream in which the frame is located. “Stream Data” is a field describing an application message included in the frame. “Offset” is a field describing a number of “Stream Data”, namely, a field describing the second number corresponding to the second data frame. “Length” is a field describing a byte length of “Stream Data”.
In an example, the first data frame may be preconfigured, to enable the structure of the first data frame to be the same as the structure of the second data frame, but the values of the frame type identifier fields to be different.
If a frame type corresponding to the first frame type identifier is named as an ATOM frame, an example structure of the first data frame is as follows:
“Type” is a frame type identifier field. In this example, the first frame type identifier of the first data frame is 0x1f. It may be understood that, the frame type corresponding to the first data frame may also be named in another manner, and the ATOM frame is merely used as an example of the name; and a value of the first frame type identifier of the first data frame may also be another value. These are not limited herein.
The foregoing embodiments describe the data transmission method from a plurality of aspects. The following describes a transmit end apparatus for data transmission and a receive end apparatus for data transmission with reference to the accompanying drawings.
As shown in
An embodiment of the transmit end apparatus 40 for data transmission includes an application module 401 and a QUIC module 402.
The application module 401 is configured to:
transfer a first application message generated by a target application to the QUIC module 402, where the target application runs on a transmit end.
The QUIC module 402 is configured to:
receive the first application message;
encapsulate the first application message to obtain a first data frame, where the first data frame includes a first frame type identifier, and the first frame type identifier indicates that an application message included in the first data frame is a complete application message; and transmit the first data frame to a receive end based on an established QUIC connection to the receive end, to enable the receive end to determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, where a target application runs on the receive end.
The application module 401 may be located at an application layer of the transmit end, and the target application of the transmit end may run in the application module. The QUIC module 402 may be located at a transport layer of the transmit end, and the QUIC module 402 may include a QUIC entity.
After obtaining the first application message generated by the target application of the transmit end, the QUIC module 402 of the transmit end encapsulates the first application message to obtain the first data frame, where the first data frame includes the first frame type identifier, and the first frame type identifier indicates that the application message included in the first data frame is a complete application message, that is, the first application message may be completely encapsulated into the first data frame, so that completeness of the first application message can still be maintained after the first application message is encapsulated into the first data frame. Therefore, when the first data frame is sent to the receive end based on the QUIC connection, complete information of the first application message is transmitted based on the first data frame. In this way, after receiving the first data frame, the receive end may determine, based on the first frame type identifier, that the application message included in the first data frame is a complete application message, so as to conveniently obtain the complete first application message in the first data frame, and the receive end does not need to combine data frames and traverse combined information to search for boundaries of an application message to obtain the corresponding application message. In this way, information processing overheads can be reduced, and an information processing process of the receive end can be optimized.
Optionally, the first application message includes a first message identifier, and the first message identifier indicates to encapsulate the first application message in a form of a complete application message.
Optionally, the first application message is transferred from the target application to the QUIC entity at the transport layer through a first programming interface, and an application message transferred through the first programming interface is encapsulated in a form of a complete application message.
Optionally, the application module 401 is further configured to:
obtain the first application message based on a target threshold and application data generated by the target application, where a size of the first application message does not exceed the target threshold.
Optionally, the QUIC module 402 is further configured to:
receive first parameter information sent by the receive end, where the first parameter information includes a maximum data amount of an application message that the target application of the receive end expects to receive;
determine the target threshold based on the first parameter information; and
transfer the target threshold to the application module 401.
The application module 401 is further configured to:
receive the target threshold.
Optionally, the QUIC module 402 is further configured to:
determine the target threshold based on second parameter information, where the second parameter information includes at least one of information about a flow control parameter, information about a path maximum transmission unit parameter of the transmit end, and information about a congestion window parameter of the transmit end; and transfer the target threshold to the application module 401.
The application module is further configured to:
receive the target threshold.
Optionally, the QUIC module 402 is further configured to:
obtain an updated target threshold; and
obtain a second application message based on the updated target threshold and the application data generated by the target application, where a size of the second application message does not exceed the updated target threshold, and the size of the second application message is different from the size of the first application message.
Optionally, the QUIC module 402 is configured to:
if the size of the first application message is not greater than that of a send window, encapsulate the first application message to obtain the first data frame, where the send window indicates an amount of data that can be sent by the transmit end based on the QUIC.
Optionally, the application module 401 is further configured to:
send a third application message generated by the target application to the QUIC module 402.
The QUIC module 402 is further configured to:
receive the third application message;
encapsulate the third application message to obtain a second data frame, where the second data frame does not include the first frame type identifier; and
transmit the second data frame to the receive end based on the established QUIC connection, to enable the receive end to identify boundaries of the third application message from the second data frame, to obtain the third application message.
Optionally, the first data frame includes a first number, the second data frame includes a second number, and the first number and the second number correspond to a sequence in which the first application message included in the first data frame and the third application message included in the second data frame are generated by the target application.
Optionally, the first data frame and the second data frame are included in a same QUIC packet.
As shown in
An embodiment of the receive end apparatus 50 for data transmission includes a QUIC module 502.
The QUIC module 502 is configured to:
receive, based on an established QUIC connection to a transmit end, a first data frame sent by the transmit end, where the first data frame is obtained by the transmit end by encapsulating a first application message generated by a target application, the first data frame includes a first frame type identifier, the first frame type identifier indicates that an application message included in the first data frame is a complete application message, and target applications run on the transmit end and a receive end; and obtain the first application message from the first data frame based on the first frame type identifier.
The QUIC module 502 may be located at a transport layer of the receive end, and the QUIC module 502 may include a QUIC entity.
Optionally, the QUIC module 502 is further configured to:
send first parameter information to the transmit end, where the first parameter information includes a maximum data amount of an application message that the target application of the receive end expects to receive, the first parameter information is used by the transmit end to determine a target threshold, and a size of the first application message does not exceed the target threshold.
Optionally, the QUIC module 502 is further configured to:
transfer the obtained first application message to the target application of the receive end through a first programming interface.
Optionally, the receive end apparatus further includes an application module 501.
The QUIC module 502 is further configured to:
receive, based on the established QUIC connection, a second data frame sent by the transmit end, where the second data frame is obtained by encapsulating a third application message generated by the target application of the transmit end, and the second data frame does not include the first frame type identifier; and transmit the second data frame to the application module 501.
The application module 501 is configured to:
identify boundaries of the third application message from the second data frame, to obtain the third application message.
The application module 501 may be located at an application layer of the receive end, and the target application of the receive end may run in the application module.
Optionally, the first data frame and the second data frame each include a frame type identifier field, the frame type identifier field of the first data frame includes the first frame type identifier, the frame type identifier field of the second data frame includes a second frame type identifier, and the second frame type is different from the first frame type identifier.
The memory 601 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 601 may store a program. When the program stored in the memory 601 is executed by the processor 602, the processor 602 and the communication interface 603 are configured to perform steps 101 to 103, steps 202 and 203, and steps 301 to 303 in the foregoing data transmission method embodiments.
The processor 602 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof. The processor 602 is configured to execute a related program to implement functions that need to be performed by the application module and the QUIC module in the transmit end apparatus for data transmission in the embodiments, or perform steps 101 to 103, steps 202 and 203, and steps 301 to 303 in the data transmission method in the method embodiments. The steps of the method with reference to embodiments may be directly performed and completed by a hardware decoding processor or may be performed and completed by using a combination of hardware in a decoding processor and a software module. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory 601. The processor 602 reads information in the memory 601, and performs steps 101 to 103, steps 202 and 203, and steps 301 to 303 in the foregoing data transmission method embodiments by using hardware of the processor 602.
The communication interface 603 uses a transceiver apparatus, for example, including but not limited to a transceiver, to implement communication between the transmit end 60 and another device or a communication network. For example, a first data frame may be sent to a receive end through the communication interface 603.
The bus 604 may implement a path for transmitting information between components (for example, the memory 601, the processor 602, and the communication interface 603) of the transmit end 60. The bus 604 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. Buses may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus in
A non-transitory computer-readable storage medium may be further provided. The non-transitory computer-readable storage medium stores computer-executable instructions. When a processor of a transmit end executes the computer-executable instructions, the transmit end performs the steps performed by the processor in
A computer program product may be further provided. The computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a non-transitory computer-readable storage medium. When a processor of a transmit end executes the computer-executable instructions, the transmit end performs the steps performed by the processor in
In another embodiment, a chip system may be further provided. The chip system includes a processor. The processor is configured to support a transmit end in implementing steps 101 to 103, steps 202 and 203, and steps 301 to 303 in the foregoing data transmission method embodiments. The chip system may further include a memory. The memory is configured to store program instructions and data that are necessary for a data write apparatus. The chip system may include a chip or may include a chip and another discrete component.
The memory 701 may be a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 701 may store a program. When the program stored in the memory 701 is executed by the processor 702, the processor 702 and the communication interface 703 are configured to perform steps 104 and 105, step 201, and steps 304 and 305 in the foregoing data transmission method embodiments.
The processor 702 may be a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof. The processor 702 is configured to execute a related program to implement functions that need to be performed by the application module and the QUIC module in the receive end apparatus for data transmission in the embodiments, or perform steps 104 and 105, step 201, and steps 304 and 305 in the data transmission method in the method embodiments. The steps of the method may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware in a decoding processor and a software module. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory 701. The processor 702 reads information in the memory 701, and performs steps 104 and 105, step 201, and steps 304 and 305 in the foregoing data transmission method embodiments by using hardware of the processor 702.
The communication interface 703 uses a transceiver apparatus, for example, including but not limited to a transceiver, to implement communication between the receive end 70 and another device or a communication network. For example, a first data frame may be received from a transmit end through the communication interface 703.
The bus 704 may implement a path for transmitting information between components (for example, the memory 701, the processor 702, and the communication interface 703) of the receive end 70. The bus 704 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. Buses may be classified into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is used to represent the bus in
In another embodiment, a non-transitory computer-readable storage medium may be further provided. The non-transitory computer-readable storage medium stores computer-executable instructions. When a processor of a receive end executes the computer-executable instructions, the receive end performs the steps performed by the processor in
In another embodiment, a computer program product may be further provided. The computer program product includes computer-executable instructions, and the computer-executable instructions are stored in a non-transitory computer-readable storage medium. When a processor of a receive end executes the computer-executable instructions, the receive end performs the steps performed by the processor in
In another embodiment, a chip system may be further provided. The chip system includes a processor. The processor is configured to support a receive end in implementing steps 104 and 105, step 201, and steps 304 and 305 in the foregoing data transmission method embodiments. The chip system may further include a memory. The memory is configured to store program instructions and data that are necessary for a data write apparatus. The chip system may include a chip or may include a chip and another discrete component.
As shown in
A person of ordinary skill in the art may be aware that, in combination with the examples described in embodiments, units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether functions are performed by hardware or software depends on particular applications and constraints of the solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but it should not be considered that the implementation goes beyond the scope of the embodiments=.
It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatuses, and units, refer to corresponding processes in the foregoing method embodiments. Details are not described herein again.
In the several embodiments, it should be understood that the system, apparatuses, and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, the unit division is merely logical function division and may be other division in actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one position or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the embodiments.
In addition, functional units in the embodiments may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.
When functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the embodiments, the part contributing to a conventional technology, or some of the solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the method described in the embodiments. The foregoing storage medium includes: any medium that can store program code, for example, a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc.
The foregoing descriptions are merely implementations of the embodiments but are not intended to limit the scope of the embodiments.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202111017185.3 | Aug 2021 | CN | national |
