WO2022228011A1

WO2022228011A1 - Method and apparatus for data transmission using quic, client, and server

Info

Publication number: WO2022228011A1
Application number: PCT/CN2022/084139
Authority: WO
Inventors: 梁乾灯; 康娇
Original assignee: 华为技术有限公司
Priority date: 2021-04-26
Filing date: 2022-03-30
Publication date: 2022-11-03
Also published as: CN115334138A; CN115334138B

Abstract

The present application is applicable to the technical field of terminals, and provides a method and apparatus for data transmission using QUIC, a client, and a server. The method comprises: when performing data transmission with a server in response to a second data request, a client determining a second application layer protocol used by the second data request; and when the second application layer protocol is an application layer protocol in an application layer protocol list corresponding to a first QUIC session, establishing a second data stream in the first QUIC session. The second data stream is used to carry the data requested to be transmitted in the second data request, the first QUIC session is a QUIC session established with the server by the client in response to the first data request, and the application layer protocol list corresponding to the first QUIC session comprises an application layer protocol that is supported by the client and the server at the same time. Since multiple QUIC sessions do not need to be established, the first QUIC session is multiplexed to transmit the data requested to be transmitted in the second data request, thus network bandwidth can be saved and QUIC session resources are saved, while data transmission delay is reduced, and link efficiency is improved.

Description

QUIC data transmission method, device, client and server

This application claims the priority of the Chinese patent application filed with the State Intellectual Property Office on April 26, 2021, the application number is 202110456892.6, and the application name is "QUIC data transmission method, device, client and server". Reference is incorporated in this application.

technical field

The present application relates to the field of terminals, and in particular, to a QUIC data transmission method, device, client and server.

Background technique

Quick UDP Internet Connection (QUIC) is a low-latency Internet transport layer protocol based on UDP. QUIC can be used in scenarios that require data transmission, such as web pages or applications.

The QUIC protocol can multiplex the transport layer, that is, after establishing a session between the client and the server, for each element that needs to be transmitted, a reliable data stream (stream) or an unreliable data stream (flow) can be used separately. ) for data transfer.

However, different application layer protocols may be used to transport different elements. When there are multiple application layer protocols, an independent session needs to be established for each application layer protocol to transmit corresponding elements. Establishing multiple sessions will waste network bandwidth, waste QUIC session resources, and reduce the efficiency of QUIC session chain building.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a QUIC data transmission method, device, client and server, which can improve the waste of network bandwidth caused by the need to establish an independent session for each application layer protocol when there are multiple application layer protocols. , waste QUIC session resources and reduce the efficiency of QUIC session chain building.

In a first aspect, an embodiment of the present application provides a QUIC data transmission method applied to a client, the method comprising:

The client determines the second application layer protocol used by the second data request when performing data transmission between the client and the server in response to the second data request. When the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, a second data stream is established in the first QUIC session, and the second data stream is used to carry the data requested to be transmitted in the second data request. Data, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the list of application layer protocols corresponding to the first QUIC session includes the application layer protocols supported by both the client and the server.

In the first aspect, the client may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, transportation safety ), wireless terminals in smart cities, wireless terminals in smart homes, wearable devices, in-vehicle devices, ultra-mobile personal computers (UMPCs), netbooks , personal digital assistant (personal digital assistant, PDA) and other electronic equipment.

The QUIC data transmission method provided by the first aspect obtains the application layer protocol list corresponding to the first QUIC session through negotiation when the client and the server establish the first QUIC session. When the client responds to the second data request and performs data transmission between the server, if the second application layer protocol used by the second data request is in the application layer protocol list corresponding to the first QUIC session, there is no need to create QUIC again. Instead, a second data stream using the second application layer protocol is established under the first QUIC session to carry the data requested to be transmitted in the second data request. Since there is no need to establish multiple QUIC sessions, the first QUIC session is reused, which can save network bandwidth and QUIC session resources, reduce data transmission delay, and improve chain construction efficiency.

In some embodiments, establishing a second data stream with the server in the first QUIC session includes: the client generating a first type of data frame in response to the second data request, where the first type of data frame includes a second application layer protocol, a second The identification information of the data stream and the data information corresponding to the second data request are recorded, and the corresponding relationship between the identification information of the second data stream and the second application layer protocol is recorded. The client sends the first type of data frame to the server, instructing the server to establish a second data stream according to the second application layer protocol in the first type of data frame.

In some embodiments, after the client sends the first type of data frame to the server, the method further includes: the client receives the first type of data frame from the server. When the client determines that the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol is consistent with the correspondence between the identification information of the second data stream recorded by the client and the second application layer protocol , and send the first type of data frame to the processing module corresponding to the second application layer protocol for processing.

In this embodiment, by associating the identification information of the data stream with the application layer protocol, it is achieved that the application layer protocol corresponding to the second type of data frame can be accurately obtained when the first type of data frame is not used, so that the data Subsequent use of the second type of data frame frame can also transmit data streams of different application layer protocols under a QUIC session.

In some embodiments, the second type of data frame includes identification information of the second data stream and data information corresponding to the second data request.

After the client sends the first type of data frame to the server, the method further includes: the client receives the second type of data frame from the server. The client sends the second type of data frame to the processing corresponding to the second application layer protocol according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol module for processing.

The client establishing the second data stream with the server in the first QUIC session includes: the client determining that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The client generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The client sends the second type of data frame to the server, instructing the server to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In this embodiment, it is agreed that the data stream established by the second type of data frame uses the first application layer protocol in the application layer protocol list, so that when the second application layer protocol is the first application layer protocol in the application layer protocol list , the client can establish a second data stream through the second type of data frame, adding the application scenario of the QUIC data transmission method.

In some embodiments, the QUIC data transmission method further includes: after establishing the first QUIC session, the client records the number of citations of the first QUIC session, where the number of citations is the number of data streams in the first QUIC session. When a data stream is established in the first QUIC session, the reference count is incremented by one. When a stream in the first QUIC session is closed, the reference count is decremented by one.

In some embodiments, the QUIC data transmission method further includes: when the number of references is reduced to zero, and the number of references does not change after a preset duration, the client closes the first QUIC session.

In this embodiment, by recording the number of data streams in the first QUIC session, when there is no data stream in the first QUIC session and no new data stream is created within the preset time period, the first QUIC session can be closed, saving energy Network resources and QUIC session resources.

In some embodiments, before the client responds to the second data request, the method further includes: establishing a first QUIC session with the server in response to the first data request, and generating an application layer protocol list corresponding to the first QUIC session. A first data stream is established in the first QUIC session, the first data stream is used to carry the data requested to be transmitted in the first data request, the first data request uses the first application layer protocol, and the first application layer protocol corresponds to the first QUIC session The application layer protocol in the list of application layer protocols.

In some embodiments, establishing a first QUIC session with the server in response to the first data request, and generating a list of application layer protocols corresponding to the first QUIC session, includes: the client responding to the first data request and sending the server to establish the first QUIC session. The session handshake request for the session. The client receives a handshake message from the server, the handshake message is generated by the server according to the session handshake request, and the handshake message includes the application layer protocol supported by the server. Generate an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server. The client establishes the first QUIC session according to the handshake message, and sends the application layer protocol list corresponding to the first QUIC session and the confirmation message for establishment of the first QUIC session to the server through the first QUIC session.

In some embodiments, the QUIC data transmission method further includes: the client receives a first notification frame or a second notification frame from the server, where the first notification frame is used to instruct the client to send an application corresponding to the first QUIC session stored in the client. At least one application layer protocol is added to the layer protocol list, and the second notification frame is used to instruct the client to remove at least one application layer protocol stored in the application layer protocol list corresponding to the first QUIC session in the client. The client updates the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the QUIC data transmission method further includes: the client responds to an update instruction of the application layer protocol list, and updates the application layer protocol list stored in the client. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the client, a first notification frame is generated, and the first notification frame is used to instruct the server to correspond to the first QUIC session stored in the server Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the client, a second notification frame is generated, and the second notification frame is used to instruct the server to remove the first QUIC stored in the server. At least one application layer protocol in the application layer protocol list corresponding to the session. The client sends the first notification frame or the second notification frame to the server.

In some embodiments, the QUIC data transmission method further includes: when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the client generates an update instruction of the application layer protocol list, and the update instruction uses for writing the second application layer protocol into the application layer protocol list corresponding to the first QUIC session stored in the client. The client responds to the update instruction and generates the first notification frame. After the client sends the first notification frame to the server through the first QUIC session, a second data stream is established with the server in the first QUIC session.

In this embodiment, through the first notification frame and the second notification frame, the server and the client can also dynamically negotiate the application layer protocol carried by the bearer. When the application layer protocol used by the data request is not in the application layer protocol list, the Establishing a data stream increases the application scenarios of the QUIC data transmission method.

In the second aspect, the embodiments of the present application provide a QUIC data transmission method applied to a server, the method comprising:

The server determines the second application layer protocol used by the second data request when performing data transmission between the server and the client in response to the second data request. When the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, a second data stream is established in the first QUIC session, and the second data stream is used to carry the data requested to be transmitted in the second data request. Data, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the list of application layer protocols corresponding to the first QUIC session includes the application layer protocols supported by both the client and the server.

In the second aspect, the server may be a device serving the client, and the server may provide resources to the client, save data from the client, and the like. For example, the server can be a server or a network device, the server can be a blade server, a rack server, a cloud server, etc., and the network device includes a Layer 3 switch, a router, a broadband gateway, a firewall, a load balancer, and the like.

The QUIC data transmission method provided by the second aspect obtains the application layer protocol list of the first QUIC session through negotiation when the server and the client establish the first QUIC session. When the server responds to the second data request, if the second application layer protocol used by the second data request is in the application layer protocol list, there is no need to create a QUIC session, but a bearer is established under the first QUIC session using the first QUIC session. The second data stream of the second application layer protocol. Since there is no need to establish multiple QUIC sessions, the first QUIC session is reused, which can save network bandwidth and QUIC session resources, reduce data transmission delay, and improve chain construction efficiency.

In some embodiments, the server establishes a second data stream with the client in the first QUIC session, including: the server responds to the second data request to generate a first type of data frame, and the first type of data frame includes the second application layer protocol, The identification information of the second data stream and the data information corresponding to the second data request are recorded, and the correspondence between the identification information of the second data stream and the second application layer protocol is recorded. The server sends the first type of data frame to the client, and instructs the client to establish a second data stream according to the second application layer protocol in the first type of data frame.

In some embodiments, after the server sends the first type of data frame to the client, the method further includes: the server receives the first type of data frame from the client. When the server determines that the corresponding relationship between the identification information of the second data stream in the first type of data frame and the second application layer protocol is consistent with the corresponding relationship between the identification information of the second data stream recorded by the server and the second application layer protocol , and send the first type of data frame to the processing module corresponding to the second application layer protocol for processing.

After the server sends the first type of data frame to the client, the method further includes: the server receives the second type of data frame from the client. The server sends the second type of data frame to the processing corresponding to the second application layer protocol according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol module for processing.

The server establishing the second data stream with the client in the first QUIC session includes: the server determining that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The server generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The server sends the second type of data frame to the client, instructing the client to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, the QUIC data transmission method further includes: after establishing the first QUIC session, the server records the number of citations of the first QUIC session, where the number of citations is the number of data streams in the first QUIC session. When a data stream is established in the first QUIC session, the reference count is incremented by one. When a stream in the first QUIC session is closed, the reference count is decremented by one.

In some embodiments, the QUIC data transmission method further includes: when the number of references decreases to zero and the number of references does not change after a preset time period, the server closes the first QUIC session.

In some embodiments, before the server responds to the second data request, the method further includes: establishing a first QUIC session between the server and the client. The server responds to the first data request from the client, and establishes a first data stream with the client, where the first data stream is used to carry the data requested to be transmitted in the first data request, and the first data request uses the first application layer protocol, The first application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, establishing the first QUIC session between the server and the client includes: receiving a session handshake request from the client, where the session handshake request is used to instruct the server and the client to establish the first QUIC session. A handshake packet is generated according to the session handshake request and sent to the client. The handshake packet includes the application layer protocol supported by the server. Receive the application layer protocol list from the client and the confirmation message for the establishment of the first QUIC session. The server confirms the establishment of the first QUIC session according to the confirmation message.

In some embodiments, the QUIC data transmission method further includes: the server receiving a first notification frame or a second notification frame from the client, where the first notification frame is used to instruct the server to send the application corresponding to the first QUIC session stored in the server. At least one application layer protocol is added to the layer protocol list, and the second notification frame is used to instruct the server to remove at least one application layer protocol in the application layer protocol list corresponding to the first QUIC session stored in the server. The server updates the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the QUIC data transmission method further includes: the server responds to an update instruction of the application layer protocol list, and updates the application layer protocol list stored in the server. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the server, a first notification frame is generated, and the first notification frame is used to instruct the client to correspond to the first QUIC session stored in the client Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the server, a second notification frame is generated, and the second notification frame is used to instruct the client to remove the first QUIC stored in the client At least one application layer protocol in the application layer protocol list corresponding to the session. The server sends the first notification frame or the second notification frame to the client.

In some embodiments, the QUIC data transmission method further includes: when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the server generates an update instruction of the application layer protocol list, and the update instruction uses for writing the second application layer protocol into the application layer protocol list corresponding to the first QUIC session stored in the server. The server responds to the update instruction and generates a first notification frame. After the server sends the first notification frame to the client through the first QUIC session, a second data stream is established with the client in the first QUIC session.

In a third aspect, an embodiment of the present application provides a QUIC data transmission device applied to a client, including:

The determining module is configured to determine the second application layer protocol used by the second data request in response to the data transmission between the second data request and the server.

The establishment module is configured to establish a second data stream in the first QUIC session when the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, and the second data stream is used to carry the second data The data requested to be transmitted in the request. The first QUIC session is the QUIC session established with the server when the client responds to the first data request. The list of application layer protocols corresponding to the first QUIC session includes the application layer supported by both the client and the server. protocol.

In some embodiments, the establishment module is specifically configured to generate a first type of data frame in response to the second data request, where the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the data corresponding to the second data request. information, recording the correspondence between the identification information of the second data stream and the second application layer protocol. The first type of data frame is sent to the server, and the server is instructed to establish a second data stream according to the second application layer protocol in the first type of data frame.

In some embodiments, the apparatus further includes a receiving module for receiving the first type of data frame from the server. The device further includes a processing module for determining the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identification information of the second data stream recorded by the client and the second application layer protocol. When the corresponding relationship between the layer protocols is consistent, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.

The receiving module is further configured to receive the second type of data frame from the server. The processing module is further configured to send the second type of data frame to the second application layer according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol The processing module corresponding to the protocol performs processing.

The establishment module is specifically configured to determine that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The client generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The client sends the second type of data frame to the server, instructing the server to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, the apparatus further includes a recording module configured to record the number of citations of the first QUIC session after the first QUIC session is established, where the number of citations is the number of data streams in the first QUIC session. When a data stream is established in the first QUIC session, the reference count is incremented by one. When a stream in the first QUIC session is closed, the reference count is decremented by one.

In some embodiments, the recording module is further configured to close the first QUIC session when the number of references is reduced to zero and the number of references does not change after a preset duration.

In some embodiments, the establishment module is further configured to establish a first QUIC session with the server in response to the first data request, and generate a list of application layer protocols corresponding to the first QUIC session. A first data stream is established in the first QUIC session, the first data stream is used to carry the data requested to be transmitted in the first data request, the first data request uses the first application layer protocol, and the first application layer protocol corresponds to the first QUIC session The application layer protocol in the list of application layer protocols.

In some embodiments, the establishment module is specifically configured to send a session handshake request for establishing the first QUIC session to the server in response to the first data request. The client receives a handshake message from the server, the handshake message is generated by the server according to the session handshake request, and the handshake message includes the application layer protocol supported by the server. Generate an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server. The client establishes the first QUIC session according to the handshake message, and sends the application layer protocol list corresponding to the first QUIC session and the confirmation message for establishment of the first QUIC session to the server through the first QUIC session.

In some embodiments, the receiving module is further configured to receive a first notification frame or a second notification frame from the server, where the first notification frame is used to instruct the client to send the application layer protocol list corresponding to the first QUIC session stored in the client. At least one application layer protocol is added in the second notification frame, and the second notification frame is used to instruct the client to remove at least one application layer protocol stored in the application layer protocol list corresponding to the first QUIC session in the client. The apparatus further includes an update module, configured to update the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the update module is further configured to update the application layer protocol list stored in the client in response to the update instruction of the application layer protocol list. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the client, a first notification frame is generated, and the first notification frame is used to instruct the server to correspond to the first QUIC session stored in the server Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the client, a second notification frame is generated, and the second notification frame is used to instruct the server to remove the first QUIC stored in the server. At least one application layer protocol in the application layer protocol list corresponding to the session. Send the first notification frame or the second notification frame to the server.

In some embodiments, the update module is further configured to generate an update instruction of the application layer protocol list when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, and the update instruction is used to update the first QUIC session. The second application layer protocol is written into the application layer protocol list corresponding to the first QUIC session stored in the client. Respond to the update instruction and generate a first notification frame. The establishing module is further configured to establish a second data stream with the server in the first QUIC session after the client sends the first notification frame to the server through the first QUIC session.

In a fourth aspect, an embodiment of the present application provides a QUIC data transmission device applied to a server, including:

The determining module is configured to determine the second application layer protocol used by the second data request when performing data transmission between the client and the second data request in response to the second data request.

In some embodiments, the establishment module is specifically configured to generate a first type of data frame in response to the second data request, where the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the data corresponding to the second data request. information, recording the correspondence between the identification information of the second data stream and the second application layer protocol. The server sends the first type of data frame to the client, and instructs the client to establish a second data stream according to the second application layer protocol in the first type of data frame.

In some embodiments, the apparatus further includes a receiving module for receiving the first type of data frame from the client. The device further includes a processing module for determining the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identification information of the second data stream recorded by the server and the second application layer protocol. When the corresponding relationship between the layer protocols is consistent, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.

The receiving module is further configured to receive the second type of data frame from the client. The processing module is further configured to send the second type of data frame to the second application layer according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol The processing module corresponding to the protocol performs processing.

The establishment module is specifically configured to determine that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The server generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The server sends the second type of data frame to the client, instructing the client to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, the establishing module is further configured to establish the first QUIC session between the server and the client. The server responds to the first data request from the client, and establishes a first data stream with the client, where the first data stream is used to carry the data requested to be transmitted in the first data request, and the first data request uses the first application layer protocol, The first application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, the establishment module is specifically configured to receive a session handshake request from the client, where the session handshake request is used to instruct the server and the client to establish a first QUIC session. A handshake packet is generated according to the session handshake request and sent to the client. The handshake packet includes the application layer protocol supported by the server. Receive the application layer protocol list from the client and the confirmation message for the establishment of the first QUIC session. The server confirms the establishment of the first QUIC session according to the confirmation message.

In some embodiments, the receiving module is further configured to receive the first notification frame or the second notification frame from the client, where the first notification frame is used to instruct the server to send the application layer protocol list corresponding to the first QUIC session stored in the server. At least one application layer protocol is added in the second notification frame, and the second notification frame is used to instruct the server to remove at least one application layer protocol stored in the application layer protocol list corresponding to the first QUIC session in the server. The apparatus further includes an update module, configured to update the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the update module is further configured to update the application layer protocol list stored in the server in response to the update instruction of the application layer protocol list. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the server, a first notification frame is generated, and the first notification frame is used to instruct the client to correspond to the first QUIC session stored in the client Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the server, a second notification frame is generated, and the second notification frame is used to instruct the client to remove the first QUIC stored in the client At least one application layer protocol in the application layer protocol list corresponding to the session. The server sends the first notification frame or the second notification frame to the client.

In some embodiments, the update module is further configured to, when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the server generates an update instruction of the application layer protocol list, and the update instruction is used to Write the second application layer protocol into the application layer protocol list corresponding to the first QUIC session stored in the server. The server responds to the update instruction and generates the first notification frame. The establishing module is further configured to establish a second data stream with the client in the first QUIC session after the server sends the first notification frame to the client through the first QUIC session.

In a fifth aspect, an embodiment of the present application provides a QUIC client, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the method provided in the first aspect is implemented when the processor executes the computer program .

In a sixth aspect, an embodiment of the present application provides a QUIC server, including a memory, a processor, and a computer program stored in the memory and running on the processor, and the method provided in the second aspect is implemented when the processor executes the computer program.

In a seventh aspect, an embodiment of the present application provides a data transmission system, including at least one QUIC client provided by the fifth aspect and at least one QUIC server provided by the sixth aspect, where the QUIC client and the QUIC server are connected through network communication , the QUIC client and the QUIC server in the data transmission system can transmit data through the QUIC data transmission methods provided in the first aspect and the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method provided in the first aspect is implemented.

In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein the method provided in the second aspect is implemented when the computer program is executed by a processor.

In a tenth aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a client, enables the client to execute the method provided in the first aspect.

In an eleventh aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a server, causes the server to execute the method provided in the second aspect.

In a twelfth aspect, an embodiment of the present application provides a chip system, the chip system includes a memory and a processor, and the processor executes a computer program stored in the memory to implement the method provided in the first aspect.

In a thirteenth aspect, an embodiment of the present application provides a chip system, where the chip system includes a memory and a processor, and the processor executes a computer program stored in the memory to implement the method provided in the second aspect.

In a fourteenth aspect, an embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled to the computer-readable storage medium provided in the eighth aspect, and the processor executes a computer program stored in the computer-readable storage medium , so as to realize the method provided by the first aspect.

In a fifteenth aspect, an embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled to the computer-readable storage medium provided in the ninth aspect, and the processor executes a computer program stored in the computer-readable storage medium , so as to realize the method provided by the first aspect.

It can be understood that, for the beneficial effects of the foregoing second aspect to the fifteenth aspect, reference may be made to the relevant description in the foregoing first aspect, and details are not described herein again.

Description of drawings

Figure 1 shows an application scenario of QUIC data transmission;

FIG. 2 is a schematic structural diagram of a client according to an embodiment of the present application;

3 is a schematic diagram of a software structure of a client according to an embodiment of the present application;

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

FIG. 5 is a schematic flowchart of another QUIC data transmission method provided by an embodiment of the present application;

FIG. 6 is a schematic flowchart of another QUIC data transmission method provided by an embodiment of the present application;

FIG. 7 is a schematic flowchart of another QUIC data transmission method provided by an embodiment of the present application;

FIG. 8 is a data flow diagram provided by an embodiment of the present application when the data transmission method provided by the present application is used;

9 is a structural block diagram of a QUIC data transmission apparatus provided by an embodiment of the present application;

10 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application;

FIG. 11 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the application;

FIG. 12 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application;

13 is a structural block diagram of a QUIC data transmission apparatus provided by an embodiment of the present application;

FIG. 14 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application;

15 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the application;

FIG. 16 is a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the application;

FIG. 17 is a schematic structural diagram of a QUIC client provided by an embodiment of the application;

FIG. 18 is a schematic structural diagram of a QUIC server provided by an embodiment of the present application.

Detailed ways

In the following description, for the purpose of illustration rather than limitation, specific details such as a specific system structure and technology are set forth in order to provide a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that, as used in this specification and the appended claims, the term "and/or" refers to and including any and all possible combinations of one or more of the associated listed items.

As used in the specification of this application and the appended claims, the term "if" may be contextually interpreted as "when" or "once" or "in response to determining" or "in response to detecting ". Similarly, the phrases "if determined" or "if detected" may be interpreted contextually to mean "once determined" or "in response to determining" or "once detected" or "in response to detecting."

In addition, in the description of the specification of the present application and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the description, and should not be construed as indicating or implying relative importance.

References in this specification to "one embodiment" or "some embodiments" and the like mean that a particular feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in other embodiments," etc. in various places in this specification are not necessarily All refer to the same embodiment, but mean "one or more but not all embodiments" unless specifically emphasized otherwise. The terms "including", "including", "having" and their variants mean "including but not limited to" unless specifically emphasized otherwise.

Figure 1 shows an application scenario of QUIC data transmission.

Referring to FIG. 1 , the scenario includes a client 11 and a server 12 , and the client 11 and the server 12 previously performed data transmission through the network.

The network may be a wired network or a wireless network. As an example, the wireless network may include a global system for mobile communications (GSM), a general packet radio service (GPRS), a code division multiple access ( code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE) ), New Radio (NR), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi-zenith) satellite system, QZSS) and/or satellite based augmentation systems (SBAS). The wired network may include a Local Area Network (LAN), a Wide Area Network (WAN), and the like.

When exchanging data between the client 11 and the server 12, the QUIC protocol can be used. QUIC is a transport layer protocol based on UDP, which can replace Transmission Control Protocol (TCP) to improve problems such as head-of-line blocking. The QUIC protocol implements multiplexing at the transport layer for the protocol packets carried on it. For example, the client 11 runs a browser program, and the webpage browsed by the browser program includes multiple elements, such as text, images, and videos. A QUIC session can be established between the client 11 and the server 12, and multiple data streams can be established under each QUIC session, and each data stream is used to transmit the data requested by one element. Under a QUIC session, multiple data streams can transmit data requested by multiple elements at the same time.

In the prior art, each QUIC session can only support one application layer protocol. For elements using different application layer protocols, multiple QUIC sessions need to be established for transmission.

For example, elements such as text and images can be transmitted using Hyper Text Transfer Protocol (HTTP) 3.0, while live video elements can be transmitted through Real-time Transport Protocol (RTP) or Real-time Transport Control Protocol ( Real-time Transport Control Protocol, RTCP) for transmission. In this case, in order to transmit elements using different application layer protocols at the same time, a QUIC session needs to be established between the client 11 and the server 12 for each application layer protocol for transmitting elements using the corresponding application layer protocol. For example, a QUIC session can be used between the client 11 and the server 12 to transmit elements using the HTTP 3.0 protocol, and another QUIC session can be established to transmit elements using the RTP/RTCP protocol.

However, each time a QUIC session is established between the client 11 and the server 12, a handshake needs to be performed, and multiple handshakes are required to establish multiple QUIC sessions, resulting in increased data transmission delay and low chain building efficiency.

In this regard, please provide a QUIC data transmission method, which, when applied to the client, includes:

When this method is applied to the server, it includes:

The QUIC data transmission method provided in this application obtains the application layer protocol list corresponding to the first QUIC session through negotiation when the client and the server establish the first QUIC session. When the client or server responds to the second data request and performs data transmission between the server, if the second application layer protocol used by the second data request is in the list of application layer protocols corresponding to the first QUIC session, no need The QUIC session is created again, but a second data stream using the second application layer protocol is established under the first QUIC session to carry the data requested to be transmitted in the second data request. Since there is no need to establish multiple QUIC sessions, the first QUIC session is reused, which can save network bandwidth and QUIC session resources, reduce data transmission delay, and improve chain construction efficiency.

The client of the data transmission method provided in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a transceiver function, a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) ) terminal equipment, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, transportation Wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable devices, in-vehicle devices, ultra-mobile personal computers, UMPC), netbook, personal digital assistant (personal digital assistant, PDA), the embodiment of this application does not impose any limitation on the specific type of the client.

The server can be a device serving the client. The server can provide resources to the client and save the data from the client. For example, the server may be a server or a network device, the server may be a blade server, a rack server, a cloud server, etc., and the network device includes a three-layer switch, a router, a broadband gateway, a firewall, a load balancer, and the like. The specific type of the server does not impose any restrictions.

FIG. 2 shows a schematic structural diagram of a client, where the client is an electronic device 200 . The electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charge management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2 , mobile communication module 250, wireless communication module 260, audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, sensor module 280, buttons 290, motor 291, indicator 292, camera 293, display screen 294, and Subscriber identification module (subscriber identification module, SIM) card interface 295 and so on. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, an air pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, and ambient light. Sensor 280L, Bone Conduction Sensor 280M, etc.

It can be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 200 . In other embodiments of the present application, the electronic device 200 may include more or less components than shown, or combine some components, or separate some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

As an example, when the electronic device 200 is a mobile phone or a tablet computer, it may include all the components in the figure, or only some components in the figure.

The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller may be the nerve center and command center of the electronic device 200 . The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in processor 210 is cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 210 . If the processor 210 needs to use the instruction or data again, it can be called directly from memory. Repeated accesses are avoided, and the waiting time of the processor 210 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 210 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal asynchronous transmitter) receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (SIM) interface, and / or universal serial bus (universal serial bus, USB) interface, etc.

The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 210 may contain multiple sets of I2C buses. The processor 210 can be respectively coupled to the touch sensor 280K, the charger, the flash, the camera 293 and the like through different I2C bus interfaces. For example, the processor 210 can couple the touch sensor 280K through the I2C interface, so that the processor 210 communicates with the touch sensor 280K through the I2C bus interface, so as to realize the touch function of the electronic device 200 .

The I2S interface can be used for audio communication. In some embodiments, the processor 210 may contain multiple sets of I2S buses. The processor 210 may be coupled with the audio module 270 through an I2S bus to implement communication between the processor 210 and the audio module 270 . In some embodiments, the audio module 270 may communicate audio signals to the wireless communication module 260 through the I2S interface.

The PCM interface can also be used for audio communications, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 270 and the wireless communication module 260 may be coupled through a PCM bus interface.

In some embodiments, the audio module 270 may also transmit audio signals to the wireless communication module 260 through the PCM interface. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication.

In some embodiments, a UART interface is typically used to connect the processor 210 with the wireless communication module 260 . For example, the processor 210 communicates with the Bluetooth module in the wireless communication module 260 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 270 can transmit audio signals to the wireless communication module 260 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.

The MIPI interface can be used to connect the processor 210 with peripheral devices such as the display screen 294 and the camera 293 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 210 communicates with the camera 293 through a CSI interface, so as to implement the photographing function of the electronic device 200 . The processor 210 communicates with the display screen 294 through the DSI interface to implement the display function of the electronic device 200 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface may be used to connect the processor 210 with the camera 293, the display screen 294, the wireless communication module 260, the audio module 270, the sensor module 280, and the like. The GPIO interface can also be configured as I2C interface, I2S interface, UART interface, MIPI interface, etc.

The USB interface 230 is an interface that conforms to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like. The USB interface 230 can be used to connect a charger to charge the electronic device 200, and can also be used to transmit data between the electronic device 200 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other electronic devices, such as AR devices.

It can be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration, and does not constitute a structural limitation of the electronic device 200 . In other embodiments of the present application, the electronic device 200 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The charging management module 240 is used to receive charging input from the charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 240 may receive charging input from the wired charger through the USB interface 230 . In some wireless charging embodiments, the charging management module 240 may receive wireless charging input through the wireless charging coil of the electronic device 200 . While the charging management module 240 charges the battery 242, it can also supply power to the electronic device through the power management module 241.

The power management module 241 is used to connect the battery 242 , the charging management module 240 and the processor 210 . The power management module 241 receives input from the battery 242 and/or the charging management module 240, and supplies power to the processor 210, the internal memory 221, the external memory, the display screen 294, the camera 293, and the wireless communication module 260. The power management module 241 can also be used to monitor parameters such as battery capacity, battery cycle times, battery health status (leakage, impedance).

In some other embodiments, the power management module 241 may also be provided in the processor 210 . In other embodiments, the power management module 241 and the charging management module 240 may also be provided in the same device.

The wireless communication function of the electronic device 200 may be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, the modulation and demodulation processor, the baseband processor, and the like.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 may be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, the antenna 1 can be multiplexed as a diversity antenna of the wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 250 may provide a wireless communication solution including 2G/3G/4G/5G, etc. applied on the electronic device 200 . The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), and the like. The mobile communication module 250 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modulation and demodulation processor, and then convert it into electromagnetic waves for radiation through the antenna 1 .

In some embodiments, at least part of the functional modules of the mobile communication module 250 may be provided in the processor 210 . In some embodiments, at least part of the functional modules of the mobile communication module 250 may be provided in the same device as at least part of the modules of the processor 210 .

The modem processor may include a modulator and a demodulator. Wherein, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and passed to the application processor. The application processor outputs sound signals through audio devices (not limited to the speaker 270A, the receiver 270B, etc.), or displays images or videos through the display screen 294 . In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 210, and may be provided in the same device as the mobile communication module 250 or other functional modules.

The wireless communication module 260 can provide applications on the electronic device 200 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellites Wireless communication solutions such as global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared technology (IR). The wireless communication module 260 may be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2 , modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210 . The wireless communication module 260 can also receive the signal to be sent from the processor 210 , perform frequency modulation on the signal, amplify the signal, and then convert it into an electromagnetic wave for radiation through the antenna 2 .

In some embodiments, the antenna 1 of the electronic device 200 is coupled with the mobile communication module 250, and the antenna 2 is coupled with the wireless communication module 260, so that the electronic device 200 can communicate with the network and other devices through wireless communication technology. Wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband code division Multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM , and/or IR technology, etc. GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi-zenith) satellite system, QZSS) and/or satellite based augmentation systems (SBAS).

The electronic device 200 implements a display function through a GPU, a display screen 294, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or alter display information.

Display screen 294 is used to display images, videos, and the like. For example, in the teaching video and the user action picture video in the embodiment of the present application, the display screen 294 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light). emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on. In some embodiments, the electronic device 200 may include one or N display screens 294 , where N is a positive integer greater than one.

The electronic device 200 can realize the shooting function through the ISP, the camera 293, the video codec, the GPU, the display screen 294 and the application processor.

The ISP is used to process the data fed back by the camera 293 . For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, converting it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin tone. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 293 .

Camera 293 is used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The focal length of the lens can be used to indicate the viewing range of the camera. The smaller the focal length of the lens, the larger the viewing range of the lens. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals.

In this application, the electronic device 200 may include cameras 293 with two or more focal lengths.

A digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 200 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, and the like.

Video codecs are used to compress or decompress digital video. The electronic device 200 may support one or more video codecs. In this way, the electronic device 200 can play or record videos in various encoding formats, such as: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, and so on.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information and can continuously learn by itself. Applications such as intelligent cognition of the electronic device 200 can be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

In this embodiment of the present application, the NPU or other processors may be used to perform operations such as analysis and processing on images in the video stored by the electronic device 200 .

The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to realize the data storage function. For example to save files like music, video etc in external memory card.

Internal memory 221 may be used to store computer executable program code, which includes instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by executing the instructions stored in the internal memory 221 . The internal memory 221 may include a storage program area and a storage data area. The storage program area can store an operating system and an application program required for at least one function (such as a sound playback function, an image playback function, etc.). The storage data area can store data (such as audio data, phone book, etc.) created during the use of the electronic device 200 .

In addition, the internal memory 221 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like.

The electronic device 200 may implement audio functions through an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, and an application processor.

The audio module 270 is used for converting digital audio signals into analog audio signal outputs, and also for converting analog audio inputs into digital audio signals. Audio module 270 may also be used to encode and decode audio signals. In some embodiments, the audio module 270 may be provided in the processor 210 , or some functional modules of the audio module 270 may be provided in the processor 210 .

Speaker 270A, also referred to as a "speaker", is used to convert audio electrical signals into sound signals. The electronic device 200 can listen to music through the speaker 270A, or listen to a hands-free call. For example, the speaker can play the comparison analysis result provided by the embodiment of the present application.

The receiver 270B, also referred to as an "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 200 answers a call or a voice message, the voice can be answered by placing the receiver 270B close to the human ear.

The microphone 270C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by approaching the microphone 270C through the human mouth, and input the sound signal into the microphone 270C. The electronic device 200 may be provided with at least one microphone 270C. In other embodiments, the electronic device 200 may be provided with two microphones 270C, which may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 200 may further be provided with three, four or more microphones 270C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The headphone jack 270D is used to connect wired headphones. The earphone interface 270D can be a USB interface 230, or can be a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.

The pressure sensor 280A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 280A may be provided on the display screen 294 . There are many types of pressure sensors 280A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, and the like. The capacitive pressure sensor may be comprised of at least two parallel plates of conductive material. When a force is applied to pressure sensor 280A, the capacitance between the electrodes changes. The electronic device 200 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 294, the electronic device 200 detects the intensity of the touch operation according to the pressure sensor 280A. The electronic device 200 may also calculate the touched position according to the detection signal of the pressure sensor 280A.

In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example, when a touch operation whose intensity is less than the first pressure threshold acts on the short message application icon, the instruction for viewing the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

The gyro sensor 280B may be used to determine the motion attitude of the electronic device 200 . In some embodiments, the angular velocity of electronic device 200 about three axes (ie, x, y, and z axes) may be determined by gyro sensor 280B. The gyro sensor 280B can be used for image stabilization. Exemplarily, when the shutter is pressed, the gyro sensor 280B detects the shaking angle of the electronic device 200, calculates the distance that the lens module needs to compensate according to the angle, and allows the lens to counteract the shaking of the electronic device 200 through reverse motion to achieve anti-shake. The gyro sensor 280B can also be used for navigation and somatosensory game scenarios.

Air pressure sensor 280C is used to measure air pressure. In some embodiments, the electronic device 200 calculates the altitude through the air pressure value measured by the air pressure sensor 280C to assist in positioning and navigation.

Magnetic sensor 280D includes a Hall sensor. The electronic device 200 can detect the opening and closing of the flip holster using the magnetic sensor 280D. In some embodiments, when the electronic device 200 is a flip machine, the electronic device 200 can detect the opening and closing of the flip according to the magnetic sensor 280D. Further, according to the detected opening and closing state of the leather case or the opening and closing state of the flip cover, characteristics such as automatic unlocking of the flip cover are set.

The acceleration sensor 280E can detect the magnitude of the acceleration of the electronic device 200 in various directions (generally three axes). The magnitude and direction of gravity can be detected when the electronic device 200 is stationary. It can also be used to identify the posture of electronic devices, and can be used in applications such as horizontal and vertical screen switching, pedometers, etc.

Distance sensor 280F for measuring distance. The electronic device 200 can measure the distance through infrared or laser. In some embodiments, when shooting a scene, the electronic device 200 can use the distance sensor 280F to measure the distance to achieve fast focusing.

Proximity light sensor 280G may include, for example, light emitting diodes (LEDs) and light detectors, such as photodiodes. The light emitting diodes may be infrared light emitting diodes. The electronic device 200 emits infrared light to the outside through the light emitting diode. Electronic device 200 uses photodiodes to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it may be determined that there is an object near the electronic device 200 . When insufficient reflected light is detected, the electronic device 200 may determine that there is no object near the electronic device 200 . The electronic device 200 can use the proximity light sensor 280G to detect that the user holds the electronic device 200 close to the ear to talk, so as to automatically turn off the screen to save power. Proximity light sensor 280G can also be used in holster mode, pocket mode automatically unlocks and locks the screen.

The ambient light sensor 280L is used to sense ambient light brightness. The electronic device 200 can adaptively adjust the brightness of the display screen 294 according to the perceived ambient light brightness. The ambient light sensor 280L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 280L can also cooperate with the proximity light sensor 280G to detect whether the electronic device 200 is in the pocket, so as to prevent accidental touch.

The fingerprint sensor 280H is used to collect fingerprints. The electronic device 200 can use the collected fingerprint characteristics to realize fingerprint unlocking, accessing application locks, taking pictures with fingerprints, answering incoming calls with fingerprints, and the like.

The temperature sensor 280J is used to detect the temperature. In some embodiments, the electronic device 200 utilizes the temperature detected by the temperature sensor 280J to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 280J exceeds a threshold value, the electronic device 200 reduces the performance of the processor located near the temperature sensor 280J in order to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the electronic device 200 heats the battery 242 to avoid abnormal shutdown of the electronic device 200 caused by the low temperature. In some other embodiments, when the temperature is lower than another threshold, the electronic device 200 boosts the output voltage of the battery 242 to avoid abnormal shutdown caused by low temperature.

Touch sensor 280K, also called "touch panel". The touch sensor 280K may be disposed on the display screen 294, and the touch sensor 280K and the display screen 294 form a touch screen, also called a "touch screen". The touch sensor 280K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to touch operations may be provided through display screen 294 . In other embodiments, the touch sensor 280K may also be disposed on the surface of the electronic device 200 , which is different from the location where the display screen 294 is located.

The bone conduction sensor 280M can acquire vibration signals. In some embodiments, the bone conduction sensor 280M can acquire the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor 280M can also contact the pulse of the human body and receive the blood pressure beating signal.

In some embodiments, the bone conduction sensor 280M can also be disposed in the earphone, combined with the bone conduction earphone. The audio module 270 can analyze the voice signal based on the vibration signal of the vocal vibration bone mass obtained by the bone conduction sensor 280M, so as to realize the voice function. The application processor can analyze the heart rate information based on the blood pressure beat signal obtained by the bone conduction sensor 280M, and realize the function of heart rate detection.

The keys 290 include a power-on key, a volume key, and the like. Keys 290 may be mechanical keys. It can also be a touch key. The electronic device 200 may receive key inputs and generate key signal inputs related to user settings and function control of the electronic device 200 .

Motor 291 can generate vibrating cues. The motor 291 can be used for vibrating alerts for incoming calls, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, playing audio, etc.) can correspond to different vibration feedback effects. The motor 291 can also correspond to different vibration feedback effects for touch operations on different areas of the display screen 294 . Different application scenarios (for example: time reminder, receiving information, alarm clock, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

The indicator 292 can be an indicator light, which can be used to indicate the charging status, the change of power, and can also be used to indicate messages, missed calls, notifications, and the like.

The SIM card interface 295 is used to connect a SIM card. The SIM card can be contacted and separated from the electronic device 200 by inserting into the SIM card interface 295 or pulling out from the SIM card interface 295 . The electronic device 200 may support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 295 can support Nano SIM card, Micro SIM card, SIM card and so on. The same SIM card interface 295 can insert multiple cards at the same time. Multiple cards can be of the same type or different. The SIM card interface 295 can also be compatible with different types of SIM cards. The SIM card interface 295 is also compatible with external memory cards. The electronic device 200 interacts with the network through the SIM card to implement functions such as call and data communication. In some embodiments, the electronic device 200 employs an eSIM, ie: an embedded SIM card. The eSIM card can be embedded in the electronic device 200 and cannot be separated from the electronic device 200 .

FIG. 3 is a schematic diagram of a software structure of a client according to an embodiment of the present application. The operating system in the client can be Android (Android) system, Microsoft Windows system (Windows), Apple mobile operating system (iOS) or Harmony OS (Harmony OS). Here, the operating system of the client is Hongmeng system as an example for description.

In some embodiments, the Hongmeng system can be divided into four layers, including a kernel layer, a system service layer, a framework layer, and an application layer, and the layers communicate with each other through a software interface.

As shown in Figure 3, the kernel layer includes a kernel abstraction layer (Kernel Abstract Layer, KAL) and a driver subsystem. There are multiple kernels under KAL, such as Linux Kernel of Linux system, LiteOS of lightweight IoT system kernel, etc. The driver subsystem may include a hardware driver framework (Hardware Driver Foundation, HDF). The hardware driver framework can provide unified peripheral access capability and driver development and management framework. The multi-kernel kernel layer can select the corresponding kernel for processing according to the needs of the system.

The system service layer is the core capability set of the Hongmeng system, and the system service layer provides services to applications through the framework layer. This layer can include:

System Basic Capability Subsystem Set: Provides basic capabilities for the operation, scheduling, and migration of distributed applications on multiple devices in the HarmonyOS system. It can include subsystems such as distributed soft bus, distributed data management, distributed task scheduling, Ark multi-language runtime, common base library, multi-mode input, graphics, security, artificial intelligence (AI), user program framework, etc. . Among them, Ark multi-language runtime provides C or C++ or JavaScript (JS) multi-language runtime and basic system class library, and it can also be used for static Java programs using Ark compiler (that is, using Java in the application or framework layer). part of the language development) to provide the runtime.

Basic software service subsystem set: Provide public and general software services for Hongmeng system. It can include subsystems such as event notification, telephony, multimedia, Design For X (DFX), MSDP&DV, etc.

Enhanced software service subsystem set: Provide Hongmeng system with differentiated capability-enhanced software services for different devices. It can include smart screen proprietary business, wearable proprietary business, and Internet of Things (Internet of Things, IoT) proprietary business subsystems.

Hardware service subsystem set: Provide hardware services for Hongmeng system. It can include subsystems such as location services, biometric identification, wear-specific hardware services, and IoT-specific hardware services.

The framework layer provides multi-language user program frameworks and ability (Ability) frameworks such as Java, C, C++, JS, etc. for Hongmeng system application development, and two user interface (User Interface, UI) frameworks (including Java UI for Java language). framework, JS UI framework for JS language), as well as a variety of software and hardware services open to the outside world, the multi-language framework application programming interface (Application Programming Interface, API). According to the degree of componentization and tailoring of the system, the APIs supported by Hongmeng system devices will also be different.

The application layer includes system applications and third-party non-system applications. System applications may include applications that are installed by default on electronic devices such as the desktop, control bar, settings, and phone. Extended applications can be non-essential applications developed and designed by manufacturers of electronic equipment, such as applications such as electronic equipment housekeeper, replacement migration, sticky notes, weather and other applications. And third-party non-system applications can be developed by other manufacturers, but can run applications in the Hongmeng system, such as games, navigation, social or shopping applications.

The application of Hongmeng system consists of one or more meta-programs (Feature Ability, FA) or meta-services (Particle Ability, PA). Among them, FA has a UI interface that provides the ability to interact with users. While PA has no UI interface, it provides the ability to run tasks in the background and a unified data access abstraction. PA mainly provides support for FA, such as providing computing power as a background service, or providing data access capabilities as a data warehouse. Applications developed based on FA or PA can implement specific business functions, support cross-device scheduling and distribution, and provide users with a consistent and efficient application experience.

Multiple electronic devices running the Hongmeng system can achieve hardware mutual assistance and resource sharing through distributed soft bus, distributed device virtualization, distributed data management and distributed task scheduling.

FIG. 4 shows a schematic flowchart of the QUIC data transmission method provided by the present application. As an example and not a limitation, the method can be applied to the above-mentioned client and server.

S301. Obtain an application layer protocol supported by a client.

In some embodiments, the client can obtain the application layer protocol supported by the client by querying the application layer protocol recorded in the protocol stack (Protocol Stack). The application layer protocol in the protocol stack can be recorded through static configuration or through application startup registration of an application layer protocol (Application Layer Protocol, ALP). Application layer protocols define how application processes running on different end systems pass messages to each other. The application layer protocol is implemented based on the application layer, and the application layer is the seventh layer in the Open Systems Interconnection reference (OSI) model. , SASE) and one or more common application service elements (Computer Application Service Element, CASE). Each SASE can provide specific application services, such as File Transfer Access Method (FTAM), Message Handling System (MHS), Virtual Terminal Protocol (VAP), etc. CASE can provide a set of common application services, such as Association Control Service Element (ACSE), Reliable Transfer Service Element (RTSE) and Remote Operations Service Element (ROSE) )Wait.

Common application layer protocols include HTTP, RTP/RTCP, Domain Name System (DNS), File Transfer Protocol (FTP), Simple Mail Transfer Protocol (Simple Mail Transfer Protocol, SMTP), Simple Network Management Protocol (simple Network Management Protocol, SNMP), Remote Login Protocol (Telnet), Routing Information Protocol (Routing Information Protocol, RIP) and Network File System (Network File System, NFS), etc.

Among them, static configuration means that when QUIC is deployed in the client, the application layer protocol that the client can support is written in the QUIC protocol stack through configuration instructions.

The ALP application startup registration is that when an application in the client supports QUIC as its transport layer protocol, it actively registers the protocol type used by itself with the local QUIC protocol stack module. The QUIC protocol stack module records the protocol registration information according to the application. The corresponding protocol type.

S302. Obtain an application layer protocol supported by the server.

In some embodiments, referring to the example in S301, the server can also obtain the application layer protocol supported by the server by querying the application layer protocol recorded in the protocol stack. The acquisition method is the same as that in S301, and will not be repeated here.

S303. The client responds to the first data request, initiates a handshake to the server, and requests to establish a first QUIC session.

In some implementations, the first data request may come from an application in the client. As an example, when the client starts the shopping application in response to the user operation, the first data request may be a data request sent by the client to the server corresponding to the shopping application to obtain data in the starting interface of the shopping application. The application-side protocol used by the first data request may be determined according to the type of data obtained by the first data request. For example, for text and picture data, HTTP3.0 can be used, and for live video data, RTP/RTCP can be used.

In some embodiments, before the client responds to the first data request, a socket (Socket) connection corresponding to each application layer protocol of QUIC may be created. Request the Socket connection corresponding to the application layer protocol used, initiate a handshake to the server, and request to establish the first QUIC session.

When shaking hands with the server through a socket connection, you can use a 0-round-trip time (RTT) handshake or a 1-RTT handshake. For example, when using the 1-RTT handshake, the handshake request sent by the client to the server can be an initial (Initial) data packet. The Initial data packet contains a long header (type value 0x0), data packet length and packet number fields, It can carry the first CRYPTO frame sent by the client and the server for key exchange, and carry the two-way Acknowledge character (ACK) between the client and the server.

As an example, the packet number of the Initial data packet is 0, the CRYPTO frame of ClientHello is carried in the packet, and the CRYPTO frame (type=0x06) is used to transmit an encryption handshake message. It can be represented by Initial[0]:CRYPTO[CH].

S304, the server responds to the handshake request, and returns a handshake packet, where the handshake packet includes the application layer protocol supported by the server.

In some embodiments, referring to S303, after the server receives the Initial[0]:CRYPTO[CH], it generates an Initial data packet, a handshake (Handshake) data packet and a 0.5-RTT data packet of the server according to the COPYTO frame, and converts these The data packets are combined into a handshake message and sent to the client.

The structure of the initial data packet of the server is consistent with that of the server. As an example, the packet number of the initial data packet of the server is 0, which includes the COPYTO frame of ServerHello and the ACK of Initial[0]:CRYPTO[CH]. It can be represented by Initial[0]:CRYPTO[SH]ACK[0].

The Handshake packet contains a long header (type value 0x2), packet length and packet number fields to carry encrypted handshake messages and ACKs from the server and client. The encrypted handshake message includes an application layer protocol negotiation (Application Layer Protocol Negotiation, ALPN) field, and the application layer protocol supported by the server can be recorded in the ALPN field. When recording, it can be recorded through the string corresponding to each application layer protocol in the "ALPN Protocol Identity Document (ID)" registry specified by the Internet Engineering Task Force (IETF). For example, "the ALPN protocol ID corresponding to HTTP3.0 is h3", the ALPN protocol ID corresponding to DNS is "Doq", and the ALPN protocol ID corresponding to RTP/RTCP is "qrt", etc.

As an example, the packet number of the Handshake data packet is 0, and the packet carries a CRYPTO frame. It can be represented by Handshake[0]:CRYPTO[EE,CERT,CV,FIN]. The EE is an extension element (Extend Element, EE), and the EE can carry additionally advertised parameters. For example, ALPN can be carried through the EE and advertised in the EE.

CERT refers to the certificate (Certificate, CERT), CV refers to the check code, and FIN is the end mark. Among them, CERT and CV can be used for verification when the QUIC session is established.

The 0.5-RTT data packet refers to the 1-RTT data packet that is only sent from the server to the client. Since it is sent from the 0.5th RTT cycle, it is called 0.5-RTT data. 0.5-RTT data packets include reliable data stream (Stream) frames, STREAM frames can implicitly create data streams and carry stream data. Implicitly creating a data stream means that when the client or server creates a STREAM frame, if the stream ID indicated in the STREAM frame does not exist, a data stream using the stream ID is created, and the STREAM frame is sent through the data stream. It can be represented by 1-RTT[0]: STREAM[1, "..."].

S305. The client generates an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server.

In some embodiments, after receiving the handshake message sent by the server, the client obtains the application layer protocol supported by the server in the Handshake data packet. Then, the client determines the application layer protocols supported by both the server and the client, records these application layer protocols, and generates an application layer protocol list. For example, if the application layer protocols supported by the client include HTTP3.0, RTP/RTCP, and DND, and the application layer protocols supported by the server include HTTP3.0, RTP/RTCP, and FTP, the application layer protocol list includes HTTP3.0 and RTP /RTCP.

S306. A first QUIC session is established between the client and the server, and the client sends the application layer protocol list corresponding to the first QUIC session to the server.

In some embodiments, the client generates a corresponding data packet according to the data in each data packet of the handshake message.

For example, from Initial[0]:CRYPTO[SH]ACK[0], Initial[1]:ACK[0] can be generated. That is, the Initial data packet with the packet number 1 includes the ACK of the received Initial data packet.

According to Handshake[0]:CRYPTO[EE,CERT,CV,FIN], the client can generate Handshake[0]:CRYPTO[FIN],ACK[0].

Among them, the client can obtain the application layer protocol supported by the server according to the EE field in the CRYPTO in Handshake[0]. Then, according to the application layer protocol supported by the local end and the application layer protocol supported by the server, a list of application layer protocols corresponding to the first QUIC session is generated. The list of application layer protocols corresponding to the first QUIC session includes the protocols supported by both the client and the server. Application layer protocol.

It should be noted that the generated application layer protocol list corresponding to the first QUIC session may be recorded in the protocol stacks of the client and the server. Recording the application layer list corresponding to the first QUIC session may be implemented by establishing a first application layer list in the protocol stack, and associating the first QUIC session with the first application layer list. For example, when the first QUIC session and the first application layer list are "h3" and "qrt", it can be recorded as the first QUIC session corresponding to the first application layer list, and "h3" and "qrt" are recorded in the first application layer list .

Alternatively, recording the application layer list corresponding to the first QUIC session may also be implemented by associating the first QUIC session with the application layer protocol. For example, application layer protocols such as "h3", "qrt", and "Doq" are recorded in the protocol stack. When the first QUIC session and the first application layer list are "h3" and "qrt", the first QUIC session can be Associated with "h3" and "qrt".

In a possible implementation manner, the application layer protocol list corresponding to the first QUIC session may be based on at least two application layer protocols supported by the client and the server at the same time. For example, when the client does not use DNS for a long time, the client and server support "h3", "qrt" and "Doq" at the same time, the generated application layer list corresponding to the first QUIC session can only include "h3" and "Doq" qrt".

In this implementation, the application layer protocols that are supported by both the client and the server but are used infrequently are ignored, and only commonly used application layer protocols are recorded in the application layer protocol list corresponding to the first QUIC session. It can reduce the storage load for the server to record the application layer protocol list and save resources.

As an example, the client can generate the ACK of Handshake[0], and write the application layer protocol list corresponding to the first QUIC session into the ALPN field in the Handshake encrypted handshake message to obtain Handshake[0]:CRYPTO[FIN],ACK[ 0].

Then, the client can also generate 1-RTT[0]:STREAM[0,"..."],ACK[0] according to 1-RTT[0]:STREAM[1,"..."], which includes STREAM frame and ACK for STREAM[0, "..."].

Finally, the client sends the plurality of correspondingly generated data packets to the server as one message. After receiving the message, the server generates Handshake[1]:ACK[0] and 1-RTT[1]:HANDSHAKE_DONE,STREAM[3,"..."],ACK[ 0], confirm the completion of the handshake, and return the ACK of the completion of the handshake to the client, and the establishment of the first QUIC session is completed.

After the first QUIC session is established, it includes a first data stream, and the first data stream is used to carry data corresponding to the first data request. Among them, the data stream includes a reliable data stream (Stream) or an unreliable data stream (Flow). The specific form of the data stream needs to be determined according to the data type carried by the data stream. For example, if the data of live video needs to be reliable, then It can be transmitted in the form of Stream. In some scenarios, DNS data does not need to be reliable and can be transmitted in the form of Flow.

Taking Stream as an example, the first data stream is a unidirectional or bidirectional data stream initiated by the client. Each data stream corresponds to a fixed stream ID, and the stream ID is a 62-bit number, that is, 0 to 2 ⁶² -1 in decimal. The lowest bit (0x1) of the stream ID identifies the originator of the stream. The stream ID of the stream initiated by the client is even (the bit is set to 0), and the stream ID of the stream initiated by the server is odd (the bit is set to 1). The second low-order bit (0x2) of the stream ID is used to distinguish bidirectional data streams (bits set to 0) and unidirectional data streams (bits set to 1). Each stream corresponds to a stream ID space, which is used to record the corresponding stream ID. Each type of stream space records the stream ID from the minimum value (that is, the third low-order bit starts from 0), and each type of continuous stream is is created with a numerically increasing stream ID. For example, the bidirectional data stream initiated by the client starts to record the stream ID from 0x0 (the first three low-order bits are all 0), and the bidirectional data stream initiated by the server starts to record the stream ID from 0x1 (the first low-order 1 is 1, the second and The third low-order bit is 0), the unidirectional data stream initiated by the client starts from 0x2 (the first and third low-order bits are 0, and the second low-order bit is 1) to record the stream ID, and the one-way data flow initiated by the server starts from 0x2 0x3 (the first and second low-order bits are 1, and the third low-order bit is 0) to start recording the stream ID.

In this embodiment, if the first data stream is a unidirectional data stream initiated by the client, its stream ID is 0x2, and if the first data stream is a bidirectional data stream initiated by the client, its stream ID is 0x0.

In some embodiments, when the client initiates a Stream with the server, the first frame sent to the server may be an ALP_STREAM frame, and the ALP_STREAM frame is used to implicitly create a Stream and carry the data of the Stream. In this embodiment, the ALP_STREAM frame is the first type of data frame, and the STREAM frame is the second type of data frame.

Compared with the STREAM frame, the ALP_STREAM frame has an increased ALP field. The ALP field is used to carry the ALP field, and the ALP field is a structure used to indicate the application layer protocol corresponding to the ALP_STREAM frame.

As an example, the ALP field could be:

Among them, Alp length identifies the length of the Alp field field. Alp next Protocol(...) is the application layer protocol identification string, which records the ALPN protocol ID corresponding to the application layer protocol.

As an example, the format of an ALP_STREAM frame could be:

The ALP_STREAM frame type field may be assigned by the Internet Assigned Numbers Authority (IANA). As an example, 0b00 can be used? ? ? XXX, for example, a set of values from 0x20 to 0x27 shown in the example above.

When using the ALP_STREAM frame to create a Stream, the application layer protocol used by the Stream is the protocol declared in the ALP domain, and the protocol declared in the ALP domain must be the protocol supported by the QUIC session ALPN negotiation (that is, the list of application layer protocols corresponding to the first QUIC session). The application layer protocol in ), otherwise the creation of Stream fails and STREAM_ALP_ERROR is generated. Discard the ALP_STREAM frame or notify to close the Stream, and clear the associated information of the corresponding Stream ID and application layer protocol.

After the Stream is created, the client and server associate the Stream ID of the Stream with the application layer protocol corresponding to the Stream. Since ALP_STREAM frames and STREAM frames share the Stream ID space, ALP_STREAM frames and STREAM frames with the same Stream ID are frame data under the same Stream. Therefore, the subsequent packets of the Stream may not use the ALP_STREAM frame, but only carry the STREAM frame. When the client or server receives the STREAM frame, the STREAM frame can be sent to the corresponding application layer protocol according to the Stream ID in the STREAM frame. The protocol application or module further parses and processes.

In this embodiment, by associating the Stream ID with the application layer protocol, it is realized that the application layer protocol corresponding to the STREAM frame can be accurately obtained without using the ALP_STREAM frame, so that the Stream can also use the STREAM frame in a QUIC frame subsequently. Data streams of different application layer protocols are transmitted under the session.

As an example, assuming that the Stream ID created by the ALP_STREAM frame is 0x2, and the string recorded in the ALP field is "h3", it means that the application layer protocol carried by the Stream whose Stream ID is 0x2 is HTTP3.0. When a STREAM frame with a stream ID of 0x2 is subsequently received, the STREAM frame is sent to a protocol application or module corresponding to HTTP 3.0 for further analysis and processing.

If the subsequent packets of the Stream are carried by the ALP_STREAM frame, the protocol declared in the ALP field must be the same as the application-layer protocol identified when the Stream is created. If inconsistent, the client or server MAY generate a "STREAM_ALP_ERROR" error indicating an application-layer protocol error, and log STREAM_ALP_ERROR.

It should be noted that STREAM_ALP_ERROR can be suppressed. For example, multiple STREAM_ALP_ERROR occurring within a preset duration can be recorded only 5 times, and the method of suppressing STREAM_ALP_ERROR error is not limited in this application.

In still other implementations, Streams can also be created using STREAM frames.

When a Stream is created using a STREAM frame, the default application carried by the Stream is the first application layer protocol in the ALPN negotiation when the QUIC session is created, that is, the first application layer protocol in the application layer protocol list.

As an example, if the order of the application layer protocols in the application layer protocol list is "h3", "qrt". When a Stream with a Stream ID of 0x3 is created through a STREAM frame, the application layer protocol carried by the Stream is "h3". When a STREAM frame with a Stream ID of 0x3 is subsequently received, the STREAM frame is sent to the corresponding HTTP3.0 The protocol application or module further parses and processes.

The lower three bits of the ALP_STREAM frame type determine the fields present in the frame.

The OFF bit (0x04) in the ALP_STREAM frame type is used to indicate whether there is an Offset field. The Offset field is used to indicate the offset of the ALP_STREAM frame. When the OFF bit is set to 1, the Offset field ([Offset(i)] in the ALP_STREAM frame) is present. When the OFF bit is set to 0, the Offset field does not exist. When the Offset field is not present, the stream data starts with an offset of 0 (ie an ALP_STREAM frame contains the first byte of the stream, or the end of a stream that contains no data).

The LEN bit (0x02) in the ALP_STREAM frame type is used to indicate whether there is a Length field. The Length field is used to indicate the length of Stream Data(..) in the ALP_STREAM frame. When the LEN bit is set to 1, the Length field ([Length(i)] in the ALP_STREAM frame) is present. When the LEN bit is set to 0, the Length field is absent. When the Length field does not exist, the Stream Data field extends to the end of the message.

The FIN bit (0x01) in the ALP_STREAM frame type is used to indicate that the ALP_STREAM frame identifies the end of the code stream. The final size of the Stream is the sum of the offset and the length of this frame.

In other embodiments, when the client initiates a Flow with the server, the first frame sent to the server may be an ALP_DATAGRAM frame, and the ALP_DATAGRAM frame is used to implicitly create a Flow and carry the data of the Flow. In this embodiment, the ALP_DATAGRAM frame is the first type of data frame, and the DATAGRAM frame is the second type of data frame.

Compared with the DATAGRAM frame, the ALP_DATAGRAM frame has an increased ALP field. The ALP field is the same as in the ALP_STREAM frame.

As an example, the format of an ALP_DATAGRAM frame could be:

The ALP_DATAGRAM frame type field may be allocated by IANA. As an example, 0b00 can be used? ? ? ? ? X in the form of, for example, a set of values from 0x40 to 0x41 shown in the example above.

When creating a Flow with an ALP_DATAGRAM frame, the application layer protocol used by the Flow is the protocol declared in the ALP domain, and the protocol declared in the ALP domain must be a protocol supported by the QUIC session ALPN negotiation (that is, the application layer protocol in the application layer protocol list) , otherwise the flow creation fails and DATAGRAM_ALP_ERROR is generated. Discard the ALP_DATAGRAM frame or notify to close the Flow.

In some possible implementations, according to the QUIC protocol standard, the DATAGRAM frame may not include the Flow ID, and accordingly, the ALP_DATAGRAM frame does not include the Flow ID. In this case, when transmitting subsequent data through the Flow, the ALP_DATAGRAM frame needs to be used , to ensure that the application layer protocol used by the transmitted data can be accurately obtained. The packets under each Flow are carried by the same type of frame, that is, the packets of the same Flow are all carried by the ALP_DATAGRAM frame or all of them are carried by the DATAGRAM frame.

In other possible implementations, the DATAGRAM frame may contain the Flow ID. In this case, after the Flow is created, the client and the server can associate the Flow ID of the Flow with the application layer protocol corresponding to the Flow. Since the ALP_DATAGRAM frame and the DATAGRAM frame share the Flow ID space, it can be determined that the ALP_DATAGRAM frame and the DATAGRAM frame using the same Flow ID are frame data under the same Flow. Therefore, the subsequent packets of the Flow may not use the ALP_DATAGRAM frame, but only carry the DATAGRAM frame. When the client or server receives the DATAGRAM frame, the DATAGRAM frame can be sent to the corresponding application layer protocol according to the Flow ID in the DATAGRAM frame. The protocol application or module further parses and processes.

In this implementation, by associating the Flow ID with the application layer protocol, the application layer protocol corresponding to the DATAGRAM frame can be accurately obtained without using the ALP_DATAGRAM frame, so that the DATAGRAM frame can also be used in a QUIC session. Transport data streams of different application layer protocols.

As an example, assuming that the Flow ID created by the ALP_DATAGRAM frame is 0x2, and the string recorded in the ALP field is "h3", it means that the application layer protocol carried by the Flow whose Flow ID is 0x2 is HTTP3.0. When a DATAGRAM frame with a stream ID of 0x2 is subsequently received, the DATAGRAM frame is sent to a protocol application or module corresponding to HTTP3.0 for further analysis and processing.

If the subsequent packets of the Flow are carried by the ALP_DATAGRAM frame, the protocol declared in the ALP field must be consistent with the application layer protocol identified when the Flow is created. If inconsistent, the client or server can generate a "DATAGRAM_ALP_ERROR" error indicating an application layer protocol error, and log DATAGRAM_ALP_ERROR.

It should be noted that DATAGRAM_ALP_ERROR can be suppressed, for example, multiple DATAGRAM_ALP_ERROR occurring within a preset time period can be recorded only 5 times, and the method of suppressing DATAGRAM_ALP_ERROR error is not limited in this application.

In still other embodiments, the Flow may also be created using the DATAGRAM frame.

When a Flow is created using a DATAGRAM frame, the application carried by the default Flow is the first application layer protocol in the ALPN negotiation when the QUIC session is created, that is, the first application layer protocol in the application layer protocol list.

As an example, if the order of the application layer protocols in the application layer protocol list is "h3", "qrt". When a DATAGRAM with a Flow ID of 0x3 is created through a DATAGRAM frame, the application layer protocol carried by the DATAGRAM is "h3". When a DATAGRAM frame with a Flow ID of 0x3 is subsequently received, the DATAGRAM frame is sent to the corresponding HTTP3.0 The protocol application or module further parses and processes.

The least significant bits of the ALP_DATAGRAM frame type determine the fields present in the frame. The LEN bit (0x01) in the ALP_DATAGRAM frame type is used to indicate whether there is a Length field. The Length field is used to indicate the length of the Datagram Data(..) in the ALP_DATAGRAM frame. When the LEN bit is set to 1, the Length field ([Length(i)] in the ALP_DATAGRAM frame) is present. When the LEN bit is set to 0, the Length field is absent. When the Length field does not exist, the Datagram Data field extends to the end of the message.

In still other embodiments, after the QUIC session is established, the server and the client may also dynamically negotiate the bearer application layer protocol.

In a possible implementation, a new extension frame may be created to implement dynamic negotiation of the application layer protocol of the bearer. For example, a first notification frame for notifying the client or the server to add at least one application layer protocol to the locally stored application layer protocol list is created.

Alternatively, a second notification frame for notifying the client or the server to add at least one application layer protocol to the locally stored application layer protocol list is created.

In this embodiment, the first notification frame may be a NEW_ALPN frame. For example, after adding at least one application layer protocol to the application layer protocol list in the local QUIC protocol stack of the client, by sending a NEW_ALPN frame to the server, The application layer protocols supported by the notification server have been added.

The second notification frame may be a REMOVE_ALPN frame. For example, after removing at least one application layer protocol in the application layer protocol list in the local QUIC protocol stack of the client, send a REMOVE_ALPN frame to the server to notify the server that the local end supports application layer protocols are reduced.

It should be noted that the client and the server also record the application layer protocols that the local end can support.

In some embodiments, when adding at least one application layer protocol to the application layer protocol list, if the added at least one application layer protocol is an application layer protocol not yet supported by the local end, the application layer protocol may also be recorded as this The application layer protocol that the terminal can support. When at least one application layer protocol in the application layer protocol list is removed, the application layer protocol may also be removed from the application layer protocols that the local end can support.

As an example, the format of a NEW_ALPN frame could be:

Among them, the type field of the NEW_ALPN frame may be allocated by IANA, which is represented by "to be done (TBD) 1" in the example.

The NEW_ALPN frame can include two fields, namely the [Length(i)] field and the [Alp list(i)] field, the [Length(i)] field is used to indicate the length of the NEW_ALPN frame, and the [Alp list(i)] field At least one application layer protocol added to the application layer protocol list is recorded in . Recording the application layer protocol in [Alp list(i)] can be achieved by recording the ALPN protocol ID corresponding to the application layer protocol.

The format of the REMOVE_ALPN frame can be:

Among them, the type field of the REMOVE_ALPN frame can be allocated by IANA, which is represented by "TBD2" in the example.

REMOVE_ALPN frame can include two fields, namely [Length(i)] field and [Alp list(i)] field, [Length(i)] field is used to indicate the length of REMOVE_ALPN frame, and [Alp list(i)] At least one application-layer protocol removed from the application-layer protocol list is recorded in . Recording the application layer protocol in [Alp list(i)] can be achieved by recording the ALPN protocol ID corresponding to the application layer protocol.

It should be noted that when both ends of the QUIC protocol remove the application layer protocol through the REMOVE_ALPN frame, if the receiving end finds that there is a corresponding Stream or Flow, it should actively revoke the corresponding Stream or Flow. After receiving a STREAM frame or ALP_SREAM frame corresponding to the Stream ID, or receiving a DATAGRAM frame or ALP_DATAGRAM frame corresponding to the Flow ID, the corresponding frame should be discarded, and a corresponding error code should be generated. This error code can also suppress the frequency of generation. . In this embodiment, the method of suppressing the generation frequency may refer to the method of suppressing the generation frequency of STREAM_ALP_ERROR or suppressing the generation frequency of DATAGRAM_ALP_ERROR.

It should be noted that the NEW_ALPN or REMOVE_ALPN frame is generally advertised to the client by the QUIC server, but the QUIC client is also allowed to notify the server, which is not limited in this application.

In other embodiments, other extension frames can also be used to implement, for example, the corresponding relationship between Stream ID or Flow ID and application layer protocol (application layer protocol not recorded in the application layer protocol list) is recorded by the extension frame. When the receiver receives the extended frame, the corresponding relationship is recorded. When the STREAM or DATAGRAM frame of the Stream ID or Flow ID is received again, the data frame is sent to the corresponding protocol application or module for further analysis and processing according to the recorded correspondence.

S307. The client responds to the second data request, and obtains the second application layer protocol used by the second data request.

In some embodiments, the second data request may be generated by the client in response to a user operation, and the second data request is the same as the Internet Protocol (Internet Protocol, ip) address of the destination end of the first data request. The second application layer protocol may be the same as or different from the first application layer protocol, which is not limited herein.

For example, referring to S303, when the client receives an operation instruction from the user indicating to enable live video in the shopping application, the shopping application responds to the user's operation instruction, generates a second data request, and requests the server for live video resources. The live video resource may be transmitted using the RTP protocol, that is, the second application layer protocol may be the RTP protocol.

S308. The client determines whether the second application layer protocol used by the second data request is in the application layer protocol list corresponding to the first QUIC session. If the second application layer protocol is in the application layer protocol list corresponding to the first QUIC session, then Go to S310, otherwise go to S309.

S309, the client establishes a second QUIC session with the server.

In some embodiments, referring to the example in S307, if the RTP protocol is not in the application layer protocol list corresponding to the first QUIC session, the second data request cannot reuse the first QUIC session, and a re-handshake is required to establish a second QUIC session to Bearing the RTP protocol data corresponding to the second data request.

S310. The client establishes a second data stream in the first QUIC session.

In some embodiments, referring to the example in S307, if the RTP protocol is in the application layer protocol list corresponding to the first QUIC session, the second data request may multiplex the first QUIC session, and the client generates and sends an ALP_STREAM frame to the server. . The ALP_STREAM frame instructs the client and the server to generate a new Stream (ie, the second data stream). The Stream ID of the Stream is associated with the RTP protocol. When the server or client receives the STREAM frame of the Stream ID, it will The received STREAM frame is sent to the protocol application or module corresponding to RTP for further analysis and processing.

In some other implementations, the number of data streams in each QUIC session in the protocol stack may be recorded, and the change in the number of data streams may be recorded when a data stream is generated or destroyed under the QUIC session. When the number of data streams in the QUIC session is 0, and there is no new data stream in the QUIC session after a preset duration, the QUIC session can be disconnected and the connection is no longer maintained.

As an example, referring to the examples in S303 and S307, when the first QUIC session is established and the first data stream is established, the number of data streams in the first QUIC session is 1. When the second data stream is established under the first QUIC session, add 1 to the number of data streams in the first QUIC session, that is, the number of data streams in the first QUIC session is 2.

After the data transmission in the first data stream is completed (the FIN bit in the received STREAM frame is 1), the first data stream may be destroyed, and the number of data streams in the first QUIC session becomes 1. When the data in the second data stream is also transmitted and the second data stream is destroyed, the number of data streams in the first QUIC session becomes 0. If the number of data streams in the first QUIC session is 0 for more than 60 seconds, the first QUIC session can be disconnected.

FIG. 5 shows a schematic flowchart of another QUIC data transmission method provided by the present application. In the process shown in FIG. 5, when the second application layer protocol is not in the application layer protocol list, the second application layer protocol can be The layer protocol is added to the application layer protocol list, and then the first QUIC session is multiplexed to transmit the data corresponding to the second data request.

Referring to FIG. 5 , since S301 to S307 of the data transmission method in this embodiment are the same as those in the above-mentioned embodiment, details are not described here. Therefore, starting from S308, the method in this embodiment will be described.

S308. The client determines whether the second application layer protocol used by the second data request is in the application layer protocol list corresponding to the first QUIC session. If the second application layer protocol is in the application layer protocol list corresponding to the first QUIC session, then Go to S310, otherwise go to S311.

S310. The client establishes a second data stream in the first QUIC session.

In this embodiment, S310 is consistent with the above-mentioned embodiment, and details are not described here.

S311. The client adds the second application layer protocol to the application layer protocol list corresponding to the first QUIC session.

In this embodiment, when the second application layer protocol is not in the application layer protocol list corresponding to the first QUIC session, the second QUIC session between the client and the server is not established, but the second application layer protocol is not established. Added to the application layer protocol list corresponding to the first QUIC session stored locally on the client. For example, if the current client's local application layer protocol list includes "h3" and "qrt", and the second application layer protocol is DNS, then "Doq" can be written into the client's local application layer protocol list. The local application layer protocol list includes "h3", "qrt" and "Doq".

S312: After the client sends the application layer protocol list update instruction corresponding to the first QUIC session to the server, execute S310.

S313. The server adds the second application layer protocol to the application layer protocol list corresponding to the first QUIC session according to the application layer protocol list update instruction corresponding to the first QUIC session.

In some embodiments, after updating the application layer protocol list corresponding to the local first QUIC session, the client can send the NEW_APLN frame shown in S306 to the server, where the [Alp list(i)] field in the frame includes the first Two application layer protocols. Referring to the example of S311, the [Alp list(i)] field in the frame may include "Doq".

After receiving the NEW_APLN frame, the server writes "Doq" into the application layer protocol list corresponding to the first QUIC session stored locally on the server side. After the update, the server side writes "Doq" into the application layer protocol list corresponding to the first QUIC session locally on the server side. Includes "h3", "qrt", and "Doq".

It should be noted that, although shown in the drawings of the present application, S311 , S312 and S313 are consecutive steps. However, S311, S312 and S313 can be deployed and executed separately. For example, S311 can be executed after S307, S312 needs to be executed after S311, but the remaining steps can be inserted between S311. Similarly, S313 needs to be executed after S312, but other steps can be inserted between S313.

As an example, the sequence of steps of the QUIC data transmission method may be: S301, S302, S303, S304, S305, S306, S307, S311, S312, S308, S313, S310. Alternatively, the sequence of steps of the QUIC data transmission method may also be: S301, S302, S303, S304, S305, S306, S307, S311, S308, S312, S313, and S310, which are not limited here.

In this case, both the client and the server can dynamically negotiate the application layer protocol carried, so that both the client and the server support the second application layer protocol, and the client executes S310 to establish the first QUIC session in the first QUIC session. The second data stream is used to transmit the data corresponding to the second data request.

In this embodiment, when the second application layer protocol is not in the application layer protocol list corresponding to the first QUIC session, the client can also multiplex the first QUIC session to transmit data corresponding to the second data request, and a data transmission method is added. It can further reduce the data transmission delay and improve the efficiency of chain construction.

FIG. 6 shows a schematic flowchart of another QUIC data transmission method provided by the present application. In the process shown in FIG. 6 , the second data request is initiated by the server.

Referring to Figure 6, the method includes:

S401. Obtain an application layer protocol supported by a client.

S402. Obtain an application layer protocol supported by the server.

S403. The client responds to the first data request, initiates a handshake to the server, and requests to establish a first QUIC session.

S404, the server responds to the session establishment request, and returns a handshake request, where the handshake request includes an application layer protocol supported by the server.

S405. The client generates an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server.

S406. A first QUIC session is established between the client and the server, and the client sends the application layer protocol list corresponding to the first QUIC session to the server.

In this embodiment, the implementation manners of S401 to S406 are the same as those of S301 to S306, which will not be repeated here.

S407. The server responds to the second data request, and obtains the second application layer protocol used by the second data request.

In some embodiments, the second data request may be initiated by the server to the client based on the requirements of the application. For example, when the server dynamically pushes a broadcast or unicast notification or message (such as a live video scene) to the client, the server will initiate a second data request to the client.

For example, referring to S303, when the server needs to push the live video to the client based on the requirements of the application, the server may generate a second data request, and request the client to transmit the live video resource. Since the live video resource can be transmitted using the RTP protocol, that is, the second application layer protocol can be the RTP protocol.

S408. The server determines whether the second application layer protocol used by the second data request is in the application layer protocol list corresponding to the first QUIC session. If the second application layer protocol is in the application layer protocol list corresponding to the first QUIC session, then Go to S410, otherwise go to S409.

S409, the server establishes a second QUIC session with the client.

In some embodiments, referring to the example in S407, if the RTP protocol is not in the application layer protocol list corresponding to the first QUIC session, the second data request cannot reuse the first QUIC session, and needs to re-handshake with the client to establish the second QUIC session. session to carry the RTP protocol data corresponding to the second data request.

S410. The server establishes a second data stream in the first QUIC session.

In some embodiments, referring to the example in S407, if the RTP protocol is in the application layer protocol list corresponding to the first QUIC session, the second data request may multiplex the first QUIC session, and the server generates and sends the client an ALP_STREAM frame. . The ALP_STREAM frame instructs the server and the client to generate a new Stream (ie, the second data stream). The Stream ID of the Stream is associated with the RTP protocol. When the server or client receives the STREAM frame of the Stream ID, it will The received STREAM frame is sent to the protocol application or module corresponding to RTP for further analysis and processing.

In still other implementations, the number of data streams in each QUIC session in the protocol stack can be recorded, and when a data stream is generated or destroyed under the QUIC session, the change in the number of data streams is recorded. When the number of data streams in the QUIC session is 0, and there is no new data stream in the QUIC session after a preset duration, the QUIC session can be disconnected and the connection is no longer maintained. For a specific implementation manner, reference may be made to the example in S310, which is not repeated here.

FIG. 7 shows a schematic flowchart of another data transmission method provided by the present application. In the process shown in FIG. 7, it shows that the server initiates a second data request, and when the second application layer protocol is not in the application layer protocol list, the second application layer protocol is added to the application layer protocol list, and then reused The step of transmitting the data corresponding to the second data request in the first QUIC session.

Referring to FIG. 7 , since S401 to S407 of the data transmission method in this embodiment are the same as those in the above-mentioned embodiment, detailed descriptions are omitted here. Therefore, starting from S408, the method in this embodiment will be described.

S408. The server determines whether the second application layer protocol used by the second data request is in the application layer protocol list corresponding to the first QUIC session. If the second application layer protocol is in the application layer protocol list corresponding to the first QUIC session, then Go to S310, otherwise go to S311.

S410. The server establishes a second data stream in the first QUIC session.

In this embodiment, S410 is consistent with the above-mentioned embodiment, and details are not described here.

S411. The server adds the second application layer protocol to the application layer protocol list corresponding to the first QUIC session.

In this embodiment, when the second application layer protocol is not in the application layer protocol list corresponding to the first QUIC session, the server does not establish a second QUIC session with the client, but uses the second application layer protocol Added to the application layer protocol list corresponding to the first QUIC session stored locally on the server. For example, if the current server's local application layer protocol list includes "h3" and "qrt", and the second application layer protocol is DNS, then "Doq" can be written into the server's local application layer protocol list, and the updated service The local application layer protocol list includes "h3", "qrt" and "Doq".

S412: After the client sends an application layer protocol list update instruction to the server, execute S410.

S413. The server adds the second application layer protocol to the application layer protocol list according to the application layer protocol list update instruction.

In some embodiments, after updating the application layer protocol list corresponding to the local first QUIC session, the server can send the NEW_APLN frame shown in S306 to the client, where the [Alp list(i)] field in the frame includes the first Two application layer protocols. Referring to the example of S311, the [Alp list(i)] field in the frame may include "Doq".

After receiving the NEW_APLN frame, the client writes "Doq" into the application layer protocol list corresponding to the first QUIC session stored in the client's local area. After the update, the client's local application layer protocol list includes "h3", "" qrt" and "Doq".

It should be noted that, although shown in the drawings of the present application, S411 , S412 and S413 are consecutive steps. However, S411, S412 and S413 can be deployed and executed separately. For example, S411 can be executed after S407, S412 needs to be executed after S411, but the remaining steps can be inserted between S411. Similarly, S413 needs to be executed after S412, but other steps can be inserted between S413.

As an example, the sequence of steps of the QUIC data transmission method may be: S401, S402, S403, S404, S405, S406, S407, S411, S412, S408, S413, S410. Alternatively, the sequence of steps of the QUIC data transmission method may also be: S401, S402, S403, S404, S405, S406, S407, S411, S408, S412, S413, and S410, which are not limited here.

In this case, both the server and the client can dynamically negotiate the application layer protocol carried, so that both the client and the server support the second application layer protocol, and the server executes S410 to establish the first QUIC session in the first QUIC session. The second data stream is used to transmit the data corresponding to the second data request.

In this case, both the server and the client can support the second application layer protocol, and the server then executes S410 to establish a second data stream in the first QUIC session for transmitting the data corresponding to the second data request.

In this embodiment, when the second application layer protocol is not in the application layer protocol list corresponding to the first QUIC session, the server can also multiplex the first QUIC session to transmit the data corresponding to the second data request, and a data transmission method is added. It can further reduce the data transmission delay and improve the efficiency of chain construction.

FIG. 8 shows a data flow diagram when using the data transmission method provided by the present application, and the application of the data transmission method is described here according to the scenario shown in FIG. 8 .

In the scenario shown in FIG. 8 , the multiplexing of the QUIC session between the HTTP 3.0 session request and the RTP session request is taken as an example for description. The client is connected to the Internet through a wireless network, and the server is connected to the Internet through the Ethernet, so as to realize the communication connection between the client and the server.

When the QUIC server starts the service of the application (Application, APP) 1, it triggers the start of the QUIC server monitoring, and obtains the application layer protocols supported by the server. In this scenario, the server supports HTTP3.0 and RTP.

When a user operation is received on the QUIC client, the QUIC client is instructed to start APP1, and use HTTP3.0 to access the World Wide Web (Web) service on the QUIC server to browse web pages. The module corresponding to APP1 creates the HTTP 3.0 socket (Socket) application program interface (Application Programming Interface, API). The Socket API triggers the QUIC protocol module to initiate the creation of a QUIC session to the QUIC server through the client's local protocol stack, and starts handshake negotiation. During the handshake process, both parties also notify each other of the supported application-layer protocols, and determine the application-layer protocol list. In this scenario, the application layer protocol list indicates that the QUIC session supports HTTP 3.0 and RTP. After the handshake is successful, a QUIC session (Session) 51 is generated.

The QUIC client and the QUIC server continue to complete the handshake of the HTTP 3.0 protocol session HTTP 3.0 data stream 52 on the basis of the QUIC session 51 (that is, to create a Stream for carrying HTTP 3.0 data).

The server can encapsulate the first HTTP 3.0 SETTINGS frame (the SETTINGS frame is used to transmit HTTP 3.0 configuration parameters that affect the communication method between the client and the server) in the establishment of the HTTP 3.0 session into an ALP_STREAM frame with an application Stream ID of 4 In the Stream Data field of the ALP_STREAM frame, the protocol string in the ALP field of the ALP_STREAM frame is "h3". After the QUIC server receives the ALP_STREAM frame, it creates a Stream with a Stream ID of 4, and caches the corresponding relationship between the Stream ID of the Stream and HTTP 3.0. The server sends the HTTP 3.0 SETTINGS frame parsed from the ALP_STREAM frame to the server HTTP 3.0 protocol module for processing.

When the QUIC server subsequently receives a STREAM frame with a Stream ID of 4, it sends the parsed payload data to the HTTP 3.0 protocol module of the server for processing according to the corresponding relationship between the Stream ID and HTTP 3.0. Implement the QUIC client and QUIC server based on the QUIC session 51 to complete the handshake of the HTTP 3.0 data stream 52 and subsequent resource access.

When the QUIC client receives a user instruction and instructs APP1 to start live video, the module corresponding to APP1 creates an RTP socket interface. The Socket API checks and finds that the QUIC client has a QUIC session 51 that supports the RTP protocol, and the QUIC session 51 can carry the RTP protocol. RTP data stream 53 of the session.

Therefore, the client no longer triggers a new QUIC session handshake, but directly reuses the QUIC session 51, and performs the handshake of the RTP data stream 53 based on the QUIC session 51 (ie, creates a Stream for carrying RTP or RTCP data).

The server can encapsulate the first RTP or RTCP packet into the Stream Data field of the ALP_STREAM frame with the applied Stream ID of 8. The protocol string in the ALP field in the ALP_STREAM frame is "qrt", and the QUIC server receives the ALP_STREAM frame. Then, create a Stream with a Stream ID of 8, and cache the correspondence between the Stream ID of the Stream and the RTP.

Then, the server sends the RTP or RTCP session handshake message parsed from the ALP_STREAM frame to the RTP/RTCP protocol module of the server for processing.

When the QUIC server subsequently receives a STREAM frame with a Stream ID of 8, it sends the parsed payload data to the RTP/RTCP protocol module of the QUIC server for processing according to the correspondence between the Stream ID and RTP. Implement the QUIC client and QUIC server to complete the RTP/RTCP handshake and subsequent resource access based on the QUIC session 51.

It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Corresponding to the QUIC data transmission method applied to the client provided by the above embodiment, FIG. 9 shows a structural block diagram of the QUIC data transmission device provided by the embodiment of the present application. For the convenience of description, it only shows the relevant embodiments of the present application. part.

Referring to Figure 9, the device is applied to a client, including:

The determining module 61 is configured to determine the second application layer protocol used by the second data request in response to the data transmission between the second data request and the server.

The establishment module 62 is configured to establish a second data stream in the first QUIC session when the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, and the second data stream is used to carry the second data stream The data requested to be transmitted in the data request. The first QUIC session is the QUIC session established with the server when the client responds to the first data request. The list of application layer protocols corresponding to the first QUIC session includes the applications supported by both the client and the server. layer protocol.

In some embodiments, the establishment module 62 is specifically configured to generate a first type of data frame in response to the second data request, and the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the corresponding data of the second data request. The data information records the correspondence between the identification information of the second data stream and the second application layer protocol. The first type of data frame is sent to the server, and the server is instructed to establish a second data stream according to the second application layer protocol in the first type of data frame.

FIG. 10 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, referring to FIG. 10 , the apparatus further includes a receiving module 63 for receiving the first type of data frame from the server. The apparatus further includes a processing module 64, configured to determine the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identification information of the second data stream recorded by the client and the second data stream. When the corresponding relationship between the application layer protocols is consistent, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.

The receiving module 63 is further configured to receive the second type of data frame from the server. The processing module 64 is further configured to send the second type of data frame to the second application according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol The processing module corresponding to the layer protocol performs processing.

The establishing module 62 is specifically configured to determine that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The client generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The client sends the second type of data frame to the server, instructing the server to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

FIG. 11 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, referring to FIG. 11 , the apparatus further includes a recording module 65 for recording the number of citations of the first QUIC session after the first QUIC session is established, where the number of citations is the number of data streams in the first QUIC session. When a data stream is established in the first QUIC session, the reference count is incremented by one. When a stream in the first QUIC session is closed, the reference count is decremented by one.

In some embodiments, the recording module 65 is further configured to close the first QUIC session when the number of citations decreases to zero and the number of citations does not change after a preset period of time.

In some embodiments, the establishing module 62 is further configured to establish a first QUIC session with the server in response to the first data request, and generate a list of application layer protocols corresponding to the first QUIC session. A first data stream is established in the first QUIC session, the first data stream is used to carry the data requested to be transmitted in the first data request, the first data request uses the first application layer protocol, and the first application layer protocol corresponds to the first QUIC session The application layer protocol in the list of application layer protocols.

In some embodiments, the establishment module 62 is specifically configured to send a session handshake request for establishing the first QUIC session to the server in response to the first data request. The client receives a handshake message from the server, the handshake message is generated by the server according to the session handshake request, and the handshake message includes the application layer protocol supported by the server. Generate an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server. The client establishes the first QUIC session according to the handshake message, and sends the application layer protocol list corresponding to the first QUIC session and the confirmation message for establishing the first QUIC session to the server through the first QUIC session.

FIG. 12 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, the receiving module 63 is further configured to receive the first notification frame or the second notification frame from the server, where the first notification frame is used to instruct the client to send the application layer protocol corresponding to the first QUIC session stored in the client. At least one application layer protocol is added to the list, and the second notification frame is used to instruct the client to remove at least one application layer protocol stored in the application layer protocol list corresponding to the first QUIC session in the client. Referring to FIG. 12, the apparatus further includes an update module 66, configured to update the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the update module 66 is further configured to update the application layer protocol list stored in the client in response to the update instruction of the application layer protocol list. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the client, a first notification frame is generated, and the first notification frame is used to instruct the server to correspond to the first QUIC session stored in the server Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the client, a second notification frame is generated, and the second notification frame is used to instruct the server to remove the first QUIC stored in the server. At least one application layer protocol in the application layer protocol list corresponding to the session. Send the first notification frame or the second notification frame to the server.

In some embodiments, the update module 66 is further configured to generate an update instruction of the application layer protocol list when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, and the update instruction is used to update the application layer protocol list. The second application layer protocol is written into the application layer protocol list corresponding to the first QUIC session stored in the client. Respond to the update instruction and generate a first notification frame. The establishing module 62 is further configured to establish a second data stream with the server in the first QUIC session after the client sends the first notification frame to the server through the first QUIC session.

Corresponding to the QUIC data transmission method applied to the server provided by the above embodiment, FIG. 13 shows a structural block diagram of the QUIC data transmission device provided by the embodiment of the present application. For the convenience of description, it only shows the relevant embodiments of the present application. part.

Referring to Figure 13, the device is applied to the server, including:

The determining module 71 is configured to determine the second application layer protocol used by the second data request during data transmission between the client and the second data request in response to the second data request.

The establishment module 72 is configured to establish a second data stream in the first QUIC session when the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, and the second data stream is used to carry the second data stream The data requested to be transmitted in the data request. The first QUIC session is the QUIC session established with the server when the client responds to the first data request. The list of application layer protocols corresponding to the first QUIC session includes the applications supported by both the client and the server. layer protocol.

In some embodiments, the establishment module 72 is specifically configured to generate a first type of data frame in response to the second data request, and the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the corresponding data of the second data request. The data information records the correspondence between the identification information of the second data stream and the second application layer protocol. The server sends the first type of data frame to the client, and instructs the client to establish a second data stream according to the second application layer protocol in the first type of data frame.

FIG. 14 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, referring to FIG. 14 , the apparatus further includes a receiving module 73 for receiving the first type of data frame from the client. The device further includes a processing module 74, configured to determine the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identification information of the second data stream recorded by the server and the second data stream. When the corresponding relationship between the application layer protocols is consistent, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.

The receiving module 73 is further configured to receive the second type of data frame from the client. The processing module 74 is further configured to send the second type of data frame to the second application according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol The processing module corresponding to the layer protocol performs processing.

The establishing module 72 is specifically configured to determine that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session. The server generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol. The server sends the second type of data frame to the client, instructing the client to respond to the second type of data frame and establish the second data stream according to the first application layer protocol in the application layer protocol list corresponding to the first QUIC session.

FIG. 15 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, the apparatus further includes a recording module 75, configured to record the number of citations of the first QUIC session after the first QUIC session is established, where the number of citations is the number of data streams in the first QUIC session. When a data stream is established in the first QUIC session, the reference count is incremented by one. When a stream in the first QUIC session is closed, the reference count is decremented by one.

In some embodiments, the recording module 75 is further configured to close the first QUIC session when the number of citations decreases to zero and the number of citations does not change after a preset duration.

In some embodiments, the establishing module 72 is further configured to establish the first QUIC session between the server and the client. The server responds to the first data request from the client, and establishes a first data stream with the client, where the first data stream is used to carry the data requested to be transmitted in the first data request, and the first data request uses the first application layer protocol, The first application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session.

In some embodiments, the establishment module 72 is specifically configured to receive a session handshake request from the client, where the session handshake request is used to instruct the server and the client to establish a first QUIC session. A handshake packet is generated according to the session handshake request and sent to the client. The handshake packet includes the application layer protocol supported by the server. Receive the application layer protocol list from the client and the confirmation message for the establishment of the first QUIC session. The server confirms the establishment of the first QUIC session according to the confirmation message.

FIG. 16 shows a structural block diagram of another QUIC data transmission apparatus provided by an embodiment of the present application.

In some embodiments, the receiving module 73 is further configured to receive the first notification frame or the second notification frame from the client, where the first notification frame is used to instruct the server to send the application layer protocol corresponding to the first QUIC session stored in the server. At least one application layer protocol is added to the list, and the second notification frame is used to instruct the server to remove at least one application layer protocol in the application layer protocol list corresponding to the first QUIC session stored in the server. Referring to FIG. 16 , the apparatus further includes an update module 76 for updating the application layer protocol list according to the received first notification frame or the second notification frame.

In some embodiments, the update module 76 is further configured to update the application layer protocol list stored in the server in response to the update instruction of the application layer protocol list. When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the server, a first notification frame is generated, and the first notification frame is used to instruct the client to correspond to the first QUIC session stored in the client Add at least one application layer protocol to the list of application layer protocols. When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the server, a second notification frame is generated, and the second notification frame is used to instruct the client to remove the first QUIC stored in the client At least one application layer protocol in the application layer protocol list corresponding to the session. The server sends the first notification frame or the second notification frame to the client.

In some embodiments, the update module 76 is further configured to, when the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the server generates an update instruction of the application layer protocol list, and the update instruction uses for writing the second application layer protocol into the application layer protocol list corresponding to the first QUIC session stored in the server. The server responds to the update instruction and generates a first notification frame. The establishing module 72 is further configured to establish a second data stream with the client in the first QUIC session after the server sends the first notification frame to the client through the first QUIC session.

It should be noted that the information exchange, execution process and other contents between the above modules are based on the same concept as the method embodiments of the present application, and the specific functions and technical effects brought by them can be found in the method embodiments section for details. Repeat.

Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit, and the above-mentioned integrated units may adopt hardware. It can also be realized in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above-mentioned system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

FIG. 17 is a schematic structural diagram of a QUIC client provided by an embodiment of the present application. As shown in FIG. 17 , the QUIC client 800 of this embodiment includes: at least one processor 801 (only one is shown in FIG. 17 ), a memory 802 , and a processor 802 stored in the memory 802 and available on the at least one processor 801 The running computer program 803, when the processor 801 executes the computer program 803, implements the steps in the above-mentioned embodiment of the QUIC data transmission method applied to the client.

The QUIC client 800 may be a server, such as a computing device such as a desktop server, a rack server, a rack server, a blade server, and the like. The electronic device may include, but is not limited to, the processor 801 and the memory 802 . Those skilled in the art can understand that FIG. 17 is only an example of the QUIC client 800, and does not constitute a limitation on the QUIC client 800, and may include more or less components than the one shown, or combine some components, or different components, for example, may also include input and output devices, network access devices, and so on.

The so-called processor 801 may be a central processing unit (Central Processing Unit, CPU), and the processor 801 may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuits) , ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 802 may in some embodiments be an internal storage unit of the QUIC client 800, such as a hard disk or memory of the QUIC client 800. The memory 802 may also be an external storage device of the QUIC client 800 in other embodiments, such as a pluggable hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory 802 may also include both an internal storage unit of the QUIC client 800 and an external storage device. The memory 802 is used to store an operating system, application programs, a boot loader (Boot Loader), data, and other programs, such as program codes of computer programs, and the like. The memory 802 may also be used to temporarily store data that has been or will be output.

FIG. 18 is a schematic structural diagram of a QUIC server provided by an embodiment of the present application. As shown in FIG. 18 , the QUIC server 900 of this embodiment includes: at least one processor 901 (only one is shown in FIG. 18 ), a memory 902 , and a processor 902 stored in the memory 902 and available on the at least one processor 901 The running computer program 903, when the processor 901 executes the computer program 903, implements the steps in the foregoing embodiment of the QUIC data transmission method applied to the server.

The QUIC server 900 may be a server, such as a computing device such as a desktop server, a rack server, a rack server, and a blade server. The electronic device may include, but is not limited to, a processor 901 and a memory 902 . Those skilled in the art can understand that FIG. 18 is only an example of the QUIC server 900, and does not constitute a limitation on the QUIC server 900. It may include more or less components than the one shown, or combine some components, or different components, for example, may also include input and output devices, network access devices, and so on.

The so-called processor 901 may be a central processing unit (Central Processing Unit, CPU), and the processor 901 may also be other general-purpose processors, digital signal processors (Digital Signal Processors, DSP), application specific integrated circuits (Application Specific Integrated Circuits) , ASIC), off-the-shelf programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 902 may be an internal storage unit of the QUIC server 900 in some embodiments, such as a hard disk or a memory of the QUIC server 900 . In other embodiments, the memory 902 may also be an external storage device of the QUIC server 900, such as a pluggable hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, flash memory card (Flash Card), etc. Further, the memory 902 may also include both an internal storage unit of the QUIC server 900 and an external storage device. The memory 902 is used to store an operating system, application programs, a boot loader (Boot Loader), data, and other programs, such as program codes of computer programs, and the like. The memory 902 may also be used to temporarily store data that has been or will be output.

The embodiment of the present application also provides a data transmission system, including at least one QUIC client provided by the fifth aspect and at least one QUIC server provided by the sixth aspect, where the QUIC client and the QUIC server are connected through network communication. The QUIC client and QUIC server in the data transmission system can transmit data through the QUIC data transmission method provided in this application.

Embodiments of the present application further provide a computer-readable storage medium, and embodiments of the present application provide a computer program product, when the computer program product runs on a client, the client executes the above-mentioned QUIC data transmission applied to the client method.

Embodiments of the present application also provide a computer-readable storage medium, and embodiments of the present application provide a computer program product, which, when the computer program product runs on a server, enables the server to perform the above-mentioned QUIC data transmission applied to the server method.

The embodiments of the present application provide a computer program product, when the computer program product runs on a mobile terminal, the steps in the above-mentioned QUIC data transmission method applied to a client can be implemented when the mobile terminal executes the computer program product.

The embodiment of the present application provides a computer program product, when the computer program product runs on a mobile terminal, the steps in the above-mentioned QUIC data transmission method applied to a server can be implemented when the mobile terminal is executed.

An embodiment of the present application provides a chip system, the chip system includes a memory and a processor, and the processor executes a computer program stored in the memory to implement the steps in the above-mentioned QUIC data transmission method applied to a client.

An embodiment of the present application provides a chip system, where the chip system includes a memory and a processor, and the processor executes a computer program stored in the memory to implement the steps in the above-mentioned QUIC data transmission method applied to a server.

An embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled to a computer-readable storage medium, and the processor executes a computer program stored in the computer-readable storage medium, so as to realize the above-mentioned QUIC data applied to a client Steps in the transfer method.

An embodiment of the present application provides a chip system, the chip system includes a processor, the processor is coupled to a computer-readable storage medium, and the processor executes a computer program stored in the computer-readable storage medium, so as to realize the above-mentioned QUIC data applied to the server Steps in the transfer method.

If the QUIC data transmission method provided in this application is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application realizes all or part of the processes in the methods of the above-mentioned embodiments, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program is stored in a computer-readable storage medium. When executed by the processor, the steps of the foregoing method embodiments may be implemented. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form. The computer-readable medium may include at least: any entity or device capable of carrying computer program codes to an electronic device, a recording medium, a computer memory, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access). Memory), electrical carrier signals, telecommunications signals, and software distribution media. For example, U disk, mobile hard disk, disk or CD, etc. In some jurisdictions, under legislation and patent practice, computer readable media may not be electrical carrier signals and telecommunications signals.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed method, apparatus, client and server may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

Units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

Finally, it should be noted that: the above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this, and any changes or replacements within the technical scope disclosed in the present application should be covered by the present application. within the scope of protection of the application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A QUIC data transmission method, applied to a client, characterized in that the method comprises:

When the client performs data transmission with the server in response to the second data request, determining the second application layer protocol used by the second data request;

When the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, a second data stream is established in the first QUIC session, and the second data stream is used to carry the The data requested to be transmitted in the second data request, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the list of application layer protocols corresponding to the first QUIC session Including the application layer protocols supported by the client and the server at the same time.
The method according to claim 1, wherein the establishing the second data flow in the first QUIC session comprises:

The client generates a first type of data frame in response to the second data request, where the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the second data request Corresponding data information, recording the corresponding relationship between the identification information of the second data stream and the second application layer protocol;

The client sends the first type of data frame to the server, and instructs the server to establish a second data stream according to the second application layer protocol in the first type of data frame.
The method according to claim 2, wherein after the client sends the first type of data frame to the server, the method further comprises:

the client receives the first type of data frame from the server;

When the client determines the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identifier of the second data stream recorded by the client When the information is consistent with the corresponding relationship of the second application layer protocol, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.
The method according to claim 2 or 3, wherein the second type of data frame includes identification information of the second data stream and data information corresponding to the second data request;

After the client sends the first type of data frame to the server, the method further includes:

the client receives the second type of data frame from the server;

The client, according to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol, assigns the second type of data to the second type of data stream. The data frame is sent to the processing module corresponding to the second application layer protocol for processing.
The method according to claim 1, wherein the second type of data frame includes identification information of the second data stream and data information corresponding to the second data request;

The client establishes a second data stream with the server in the first QUIC session, including:

The client determines that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session;

The client generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol;

The client sends the second type of data frame to the server, instructing the server to respond to the second type of data frame, according to the first application in the application layer protocol list corresponding to the first QUIC session The layer protocol establishes the second data stream.
The method according to any one of claims 1-5, wherein the method further comprises:

After the first QUIC session is established, the client records the number of citations of the first QUIC session, where the number of citations is the number of data streams in the first QUIC session;

When a data stream is established in the first QUIC session, add one to the number of references;

When a data stream in the first QUIC session is closed, the reference count is decremented by one.
The method according to claim 6, wherein the method further comprises:

When the number of references is reduced to zero and the number of references does not change after a preset time period, the client closes the first QUIC session.
The method according to any one of claims 1-7, wherein before the client responds to the second data request, the method further comprises:

establishing a first QUIC session with the server in response to the first data request, and generating an application layer protocol list corresponding to the first QUIC session;

A first data flow is established in the first QUIC session, where the first data flow is used to carry the data requested to be transmitted in the first data request, the first data request uses a first application layer protocol, and the first data flow An application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session.
The method according to claim 8, wherein establishing a first QUIC session with a server in response to the first data request, and generating an application layer protocol list corresponding to the first QUIC session, comprising:

The client sends a session handshake request for establishing a first QUIC session to the server in response to the first data request;

The client receives a handshake message from the server, the handshake message is generated by the server according to the session handshake request, and the handshake message includes an application layer protocol supported by the server;

generating an application layer protocol list corresponding to the first QUIC session according to the application layer protocol supported by the client and the application layer protocol supported by the server;

The client establishes the first QUIC session according to the handshake message, and passes the application layer protocol list corresponding to the first QUIC session and the confirmation message established by the first QUIC session through the first QUCI The session is sent to the server.
The method according to any one of claims 1-9, wherein the method further comprises:

The client receives a first notification frame or a second notification frame from the server, where the first notification frame is used to instruct the client to send an application corresponding to the first QUIC session stored in the client At least one application layer protocol is added to the layer protocol list, and the second notification frame is used to instruct the client to remove at least one application stored in the application layer protocol list corresponding to the first QUIC session in the client layer protocol;

The client updates the application layer protocol list according to the received first notification frame or the second notification frame.
The method according to any one of claims 1-9, wherein the method further comprises:

The client responds to the update instruction of the application layer protocol list, and updates the application layer protocol list stored in the client;

When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the client, a first notification frame is generated, and the first notification frame is used to instruct the server to send adding at least one application layer protocol to the application layer protocol list corresponding to the first QUIC session stored in the server;

When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the client, a second notification frame is generated, and the second notification frame is used to instruct the server removing at least one application layer protocol in the application layer protocol list corresponding to the first QUIC session stored in the server;

The client sends the first notification frame or the second notification frame to the server.
The method according to claim 11, wherein the method further comprises:

When the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the client generates an update instruction of the application layer protocol list, where the update instruction is used to update the The second application layer protocol is written into the application layer protocol list corresponding to the first QUIC session stored in the client;

the client responds to the update instruction and generates the first notification frame;

After the client sends the first notification frame to the server through the first QUIC session, a second data stream is established with the server in the first QUIC session.
A QUIC data transmission method, applied to a server, characterized in that the method comprises:

When the server performs data transmission with the client in response to the second data request, determining the second application layer protocol used by the second data request;

When the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, a second data stream is established in the first QUIC session, and the second data stream is used to carry the The data requested to be transmitted in the second data request, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the application layer corresponding to the first QUIC session The protocol list includes the application layer protocols supported by the client and the server at the same time.
The method according to claim 13, wherein the establishing the second data flow in the first QUIC session comprises:

The server generates a first type of data frame in response to the second data request, where the first type of data frame includes the second application layer protocol, the identification information of the second data stream, and the second data request Corresponding data information, recording the corresponding relationship between the identification information of the second data stream and the second application layer protocol;

The server sends the first type of data frame to the client, and instructs the client to establish a second data stream according to the second application layer protocol in the first type of data frame.
The method according to claim 13, wherein after the server sends the first type of data frame to the client, the method further comprises:

receiving, by the server, the first type of data frame from the client;

When the server determines the correspondence between the identification information of the second data stream in the first type of data frame and the second application layer protocol, and the identifier of the second data stream recorded by the server When the information is consistent with the corresponding relationship of the second application layer protocol, the first type of data frame is sent to the processing module corresponding to the second application layer protocol for processing.
The method according to claim 14 or 15, wherein the second type of data frame includes identification information of the second data stream and data information corresponding to the second data request;

After the server sends the first type of data frame to the client, the method further includes:

The server receives the second type of data frame from the client;

According to the identification information of the second data stream in the second type of data frame and the corresponding relationship between the identification information of the second data stream and the second application layer protocol, the server The data frame is sent to the processing module corresponding to the second application layer protocol for processing.
The method according to claim 13, wherein the second type of data frame includes identification information of the second data stream and data information corresponding to the second data request;

The server establishes a second data stream with the client in the first QUIC session, including:

The server determines that the second application layer protocol is the first application layer protocol in the application layer protocol list corresponding to the first QUIC session;

The server generates a second type of data frame in response to the second data request, and records the correspondence between the identification information of the second data stream and the second application layer protocol;

The server sends the second type of data frame to the client, instructing the client to respond to the second type of data frame, according to the first application in the application layer protocol list corresponding to the first QUIC session The layer protocol establishes the second data flow.
The method according to any one of claims 13-17, wherein the method further comprises:

After the first QUIC session is established, the server records the number of citations of the first QUIC session, where the number of citations is the number of data streams in the first QUIC session;

When a data stream is established in the first QUIC session, add one to the number of references;

When a data stream in the first QUIC session is closed, the reference count is decremented by one.
The method of claim 18, wherein the method further comprises:

When the number of references is reduced to zero and the number of references does not change after a preset time period, the server closes the first QUIC session.
The method according to any one of claims 13-19, wherein before the server responds to the second data request, the method further comprises:

establishing a first QUIC session between the server and the client;

In response to the first data request from the client, the server establishes a first data stream with the client, where the first data stream is used to carry the data requested to be transmitted in the first data request, and the first data stream is used to carry the data requested to be transmitted in the first data request. A data request uses a first application layer protocol, where the first application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session.
The method according to claim 20, wherein establishing the first QUIC session between the server and the client comprises:

receiving a session handshake request from the client, where the session handshake request is used to instruct the server and the client to establish a first QUIC session;

Generate a handshake message according to the session handshake request and send it to the client, where the handshake message includes an application layer protocol supported by the server;

receiving the application layer protocol list from the client and the confirmation message of the establishment of the first QUIC session;

The server confirms the establishment of the first QUIC session according to the confirmation message.
The method according to any one of claims 13-21, wherein the method further comprises:

The server receives the first notification frame or the second notification frame from the client, where the first notification frame is used to instruct the server to send the application corresponding to the first QUIC session stored in the server At least one application layer protocol is added to the layer protocol list, and the second notification frame is used to instruct the server to remove at least one application stored in the application layer protocol list corresponding to the first QUIC session in the server layer protocol;

The server updates the application layer protocol list corresponding to the first QUIC session according to the received first notification frame or the second notification frame.
The method according to any one of claims 13-21, wherein the method further comprises:

The server responds to the update instruction of the application layer protocol list, and updates the application layer protocol list stored in the server;

When the update instruction instructs to add at least one application layer protocol to the application layer protocol list stored in the server, a first notification frame is generated, and the first notification frame is used to instruct the client to send adding at least one application layer protocol to the application layer protocol list corresponding to the first QUIC session stored in the client;

When the update instruction instructs to remove at least one application layer protocol in the application layer protocol list stored in the server, a second notification frame is generated, and the second notification frame is used to instruct the client removing at least one application layer protocol stored in the application layer protocol list corresponding to the first QUIC session in the client;

The server sends the first notification frame or the second notification frame to the client.
The method of claim 23, wherein the method further comprises:

When the second application layer protocol is not an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the server generates an update instruction of the application layer protocol list, and the update instruction is used to update the The second application layer protocol is written into the application layer protocol list corresponding to the first QUIC session stored in the server;

The server responds to the update instruction and generates the first notification frame;

After the server sends the first notification frame to the client through the first QUIC session, a second data stream is established with the client in the first QUIC session.
A QUIC data transmission device, applied to a client, characterized in that the device comprises:

a determining module, configured to determine the second application layer protocol used by the second data request in response to the data transmission between the second data request and the server;

An establishment module, configured to establish a second data stream in the first QUIC session when the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the second data stream The stream is used to carry the data requested to be transmitted in the second data request, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the first QUIC session corresponds to The application layer protocol list includes the application layer protocols supported by the client and the server at the same time.
A QUIC data transmission device, applied to a server, characterized in that the device comprises:

a determining module, configured to determine the second application layer protocol used by the second data request when performing data transmission with the client in response to the second data request;

An establishment module, configured to establish a second data stream in the first QUIC session when the second application layer protocol is an application layer protocol in the application layer protocol list corresponding to the first QUIC session, the second data stream The stream is used to carry the data requested to be transmitted in the second data request, the first QUIC session is the QUIC session established with the server when the client responds to the first data request, and the first QUIC session corresponds to The application layer protocol list includes the application layer protocols supported by the client and the server at the same time.
A QUIC client, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the computer program, the implementation of claim 1 The method of any one of to 12.
A QUIC server, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the computer program, the implementation of claim 13 The method of any one of to 24.
A data transmission system, characterized in that it includes at least one QUIC client according to claim 27 and at least one QUIC server according to claim 28, wherein the QUIC client and the QUIC server are connected through network communication .
A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.
A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the method according to any one of claims 13 to 24 is implemented.