Downlink transmission method for application metadata, related device, and communication system

Abstract

The present application relates to the field of communications. Specifically, the present application relates to a downlink transmission method for application metadata, a related device, and a communication system. The method comprises: an application server sending a first downlink message to a proxy device by means of a QUIC between the proxy device and the application server, the first downlink message comprising application metadata and a payload; the proxy device sending the application metadata in the first downlink message to an access network device, the application metadata being used by the access network device to adjust connection parameters between the access network device and user equipment; and the proxy device sending a second downlink message to the user equipment, the second downlink message comprising the payload, and the payload being parsed from the first downlink message. The solution of the present application helps to solve the issue of an application server performing downlink transmission of application metadata.

Description

Downlink transmission method, related equipment and communication system for application metadata

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 21, 2023, with application number 202311227720.7 and invention name “Downlink transmission method, related equipment and communication system for application metadata”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a downlink transmission method, related equipment, and a communication system using metadata. Background Art

[0003] With the development of 5G, video is gradually evolving from flat, high-definition video to immersive interaction. Weakly interactive services like 360-degree virtual reality (VR) and free-viewing, as well as highly interactive services like gaming, education, social networking, and remote collaboration, will mature over the next two to five years. Users interact with their virtual or real environments in real time through interactive devices, gestures, or body sensors, and edge XR servers respond in real time based on these interactions. To ensure a superior XR user experience, and with the continuous improvement of image quality, interactivity, and immersion, XR immersive interactive services are placing comprehensive quality of service (QoS) demands on the network, including requirements for bandwidth, latency, and packet reliability.

[0004] Wireless networks are affected by factors such as signal coverage, interference, and load, as well as the uncertainty of the air interface channel itself. They have large bandwidth and delay jitter and high burst packet loss, making it difficult to provide stable, low-latency, large-bandwidth transmission.

[0005] On the other hand, the transmission form of XR services is also quite different from that of traditional videos. Traditional videos are usually single media streams, transmitted using a single connection of the Transmission Control Protocol (TCP); XR videos and mixed reality (MR) scenes usually have one or more forms of multiple media types in the uplink and downlink. For example, the uplink usually contains uplink requests, interactive instructions, uplink video streams or auxiliary information, etc., and the downlink usually contains one or more real-scene rendering streams, virtual model rendering streams, spatial auxiliary information, etc. Due to the temporal or content correlation between the above-mentioned uplink and downlink media streams, multiple streams need to be transmitted concurrently and synchronously.

[0006] Limited by wireless channel theory and its instability, achieving low latency and simultaneous multi-stream transmission on wireless networks is difficult or expensive. To address the new challenges of large bandwidth, stable low-latency transmission, and simultaneous multi-stream transmission brought about by XR video transmission, the 3GPP Release 18 standard proposes network-industry collaboration. This allows applications to carry service metadata, enabling wireless networks / air interfaces to perceive content and traffic characteristics for pre-scheduling or refined scheduling. Furthermore, 5GS proactively exposes network-related capabilities in real time, such as L4S ECN congestion marking information, enabling applications to adapt to rapid fluctuations in wireless networks.

[0007] Currently, there are two ways for applications to carry metadata: one is to carry application metadata via TCP extension headers based on the standard CONNECT method. Specifically, a TCP connection is established between the user device and the proxy, and another between the proxy and the application server. After these two TCP connections are established, the proxy operates at the TCP transport layer, transparently transmitting received request or response packets bidirectionally. A single TCP extension header is only 40 bytes, and the TCP standard makes it difficult to increase the size of the extension field. Existing networks often enable extensions such as the TCP timestamps option (TSOPT) and selective ACK (SACK) to optimize TCP performance, making it difficult to carry application metadata information carried in TCP extension headers. The other method is to carry metadata via the MASQUE (Multiplexed Application Substrate over QUIC Encryption) extended CONNECT method based on QUIC. Specifically, the user device and application server communicate via a tunnel, using two layers of connection. The outer layer connection of the tunnel is between the user device and the proxy, and the inner layer connection of the tunnel is between the user device and the application server. After the outer layer connection is successful, the user device initiates a tunnel negotiation request to the proxy to the application server. If the negotiation between the two parties is successful, the inner layer connection between the user device and the application server is established. After the tunnel is established, the proxy is responsible for the connection and flow mapping of different hypertext transfer protocol (HTTP) versions between the two layers of connection, the encapsulation and format conversion of the payload, and other functions. However, for the application server, this method only supports the uplink transmission of application metadata. In summary, the above two methods cannot solve the problem of the application server transmitting application metadata downlink.

[0008] Summary of the Invention

[0009] The embodiments of the present application provide a method for downlink transmission of application metadata, related equipment, and a communication system. Adoption of the embodiments of the present application is conducive to solving the problem of downlink transmission of application metadata by an application server.

[0010] In a first aspect, an embodiment of the present application provides a method for downlink transmission of application metadata, which is applied to a proxy device. The method includes:

[0011] The proxy device receives a first downlink message sent by the application server through QUIC between the application server and the proxy device, where the first downlink message includes application metadata and a payload; the proxy device sends the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user device; the proxy device sends a second downlink message to the user device, where the second downlink message includes a payload, which is parsed from the first downlink message.

[0012] The first downlink message is a QUIC message, and the application metadata is carried in an extension header of the QUIC message.

[0013] The application server and proxy device transmit data via QUIC between the proxy device and the application server, which improves data transmission efficiency compared to the TCP connection used in the prior art. By carrying application metadata via the QUIC message extension header, the application server transmits application metadata to the proxy gateway, i.e., transmits application metadata downlink. Furthermore, since the QUIC message extension header is encrypted, carrying application metadata via the QUIC message extension header ensures the security of the application metadata and prevents tampering.

[0014] In conjunction with the first aspect, in one possible implementation, the first downlink message includes a first identifier, where the first identifier is used to indicate that the first downlink message carries application metadata. The method of this embodiment further includes:

[0015] The proxy gateway obtains application metadata from the first downlink message according to the first identifier.

[0016] By carrying the first identifier in the downlink message from the application server to the proxy gateway, the proxy gateway can know whether the received downlink message carries the application metadata.

[0017] In conjunction with the first aspect, in one possible implementation, the method of this embodiment further includes:

[0018] The proxy gateway converts the application metadata.

[0019] The proxy gateway sends the application metadata in the first downlink message to the access network device, including: the proxy gateway sends the converted application metadata to the access network device, so that the access network device adjusts the connection parameters between the access network device and the user equipment based on the converted application metadata.

[0020] In combination with the first aspect, in one possible implementation, when the connection between the proxy device and the user device is based on the QUIC protocol, the second downlink message is obtained by stream mapping the third downlink message, and the third downlink message is obtained by removing the application metadata in the first downlink message; when the connection between the proxy device and the user device is not based on the QUIC protocol, the second downlink message is obtained by encapsulating the payload using the protocol on which the connection between the proxy device and the user device is based.

[0021] In conjunction with the first aspect, in one possible implementation, the method of this embodiment includes:

[0022] The proxy device receives a first tunnel negotiation request from a user device, where the first tunnel negotiation request is used to request the establishment of a QUIC between the proxy device and the application server; the proxy device sends a connection creation request to the application server, where the connection creation request is used to request the establishment of a connection between the proxy device and the application server based on the QUIC protocol; upon receiving a connection creation response message sent by the application server in response to the connection creation request, the proxy device sends a first tunnel negotiation response message to the user device in response to the first tunnel negotiation request.

[0023] In conjunction with the first aspect, in one possible implementation, the method of this embodiment includes:

[0024] When the first tunnel negotiation request includes the second identifier, the proxy device sends a connection creation request to the application server, where the connection creation request is used to request the creation of a QUIC-based connection between the proxy device and the application server; the second identifier is used to indicate that the tunnel between the proxy device and the application server is a Hypertext Transfer Protocol / 3 (HTTP / 3)-based tunnel; upon receiving a connection creation response message sent by the application server in response to the connection creation request, the proxy device sends a second tunnel negotiation request to the application server, where the second tunnel negotiation request is used to request the creation of an HTTP / 3-based tunnel between the proxy device and the application server; upon receiving a first tunnel negotiation response message sent by the application server in response to the second tunnel negotiation request, the proxy device sends a first tunnel negotiation response message to the user equipment in response to the first tunnel negotiation request.

[0025] By establishing a tunnel based on the HTTP / 3 protocol between the proxy device and the application server, the application server can add application metadata to the downlink message, and the proxy device can perceive the application metadata in the downlink message sent by the application server.

[0026] In a second aspect, an embodiment of the present application provides another method for transmitting application metadata. The method is applied to a user device. The method includes:

[0027] The user device sends a first tunnel negotiation request to the proxy device, where the first tunnel negotiation request is used to request the creation of a QUIC between the proxy device and the application server; the QUIC is used by the application server to send a first downlink message to the proxy device; the first downlink message includes application metadata and a payload; the user device receives a second downlink message sent by the proxy device, where the second downlink message is obtained based on the payload in the first downlink message.

[0028] The first downlink message is a QUIC message. The first downlink message includes application metadata and a payload. The application metadata is carried in an extension header of the QUIC message.

[0029] By using the QUIC message extension header to carry application metadata, the application server can transmit application metadata to the proxy device, that is, transmit application metadata downlink. And because the QUIC message extension header is encrypted, carrying application metadata through the QUIC message extension header ensures the security of application metadata and prevents tampering.

[0030] In conjunction with the second aspect, in one possible implementation, when determining to start the tunnel establishment function, the first tunnel negotiation request includes a second identifier, and the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the http / 3 protocol.

[0031] In a third aspect, an embodiment of the present application provides a method for transmitting application metadata, which is applied to an application server. The method includes:

[0032] The application server receives a connection creation request sent by the proxy device, where the connection creation request is used to request the creation of a QUIC protocol connection between the proxy device and the application server; the application server creates a QUIC protocol-based connection between the proxy device and the application server; the application server sends a first downlink message to the proxy device through the QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload.

[0033] The first downlink message is a QUIC message, and the application metadata is carried in an extension header of the QUIC message.

[0034] By using the QUIC message extension header to carry application metadata, the application server can transmit application metadata to the proxy device, that is, transmit application metadata downlink. And because the QUIC message extension header is encrypted, carrying application metadata through the QUIC message extension header ensures the security of application metadata and prevents tampering.

[0035] In conjunction with the third aspect, in one possible implementation, the method of this embodiment further includes:

[0036] The application server receives a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the establishment of a tunnel based on the HTTP / 3 protocol between the proxy device and the application server; the application server sends a second tunnel negotiation response message to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

[0037] By establishing a tunnel based on the HTTP / 3 protocol between the proxy device and the application server, the application server can add application metadata to the downlink message, and the proxy device can perceive the application metadata in the downlink message sent by the application server.

[0038] In a fourth aspect, an embodiment of the present application provides a downlink data transmission method, applied to a proxy device, the method comprising:

[0039] The proxy device receives a first tunnel negotiation request sent by a user device, where the first tunnel negotiation request is used to request the establishment of a QUIC between the proxy device and the application server; the proxy device sends a connection creation request to the application server, where the connection creation request is used to request the establishment of a connection between the proxy device and the application server based on the QUIC protocol; the proxy device receives a downlink message sent by the application server through the QUIC between the proxy device and the application server, and the proxy device sends a downlink message to the user device obtained according to the downlink message sent by the application server to the proxy gateway.

[0040] The downlink message sent by the proxy device to the user equipment includes the payload in the downlink message sent by the application server to the proxy gateway.

[0041] By establishing QUIC between the proxy device and the application server, the application server and the proxy device transmit data through QUIC, which is beneficial to improving data transmission efficiency compared to the TCP connection in the existing technology.

[0042] In conjunction with the fourth aspect, in one possible implementation, the method of this embodiment includes:

[0043] When the first tunnel negotiation request includes the second identifier, the proxy device sends a connection creation request to the application server, where the connection creation request is used to request the creation of a QUIC protocol-based connection between the proxy device and the application server; the second identifier is used to indicate that the tunnel between the proxy device and the application server is a HTTP / 3 protocol-based tunnel; upon receiving a connection creation response message sent by the application server in response to the connection creation request, the proxy device sends a second tunnel negotiation request to the application server, where the second tunnel negotiation request is used to request the creation of a HTTP / 3 protocol-based tunnel between the proxy device and the application server; upon receiving a first tunnel negotiation response message sent by the application server in response to the second tunnel negotiation request, the proxy device sends a first tunnel negotiation response message to the user equipment in response to the first tunnel negotiation request.

[0044] In existing solutions, there is no tunnel between the proxy device and the application server, but only between the application server and the user device. Therefore, when the application server sends data to the user device, if there is a long round-trip time (RTT) or packet loss, the application server can only resend the data directly to the user device. By establishing a QUIC and http / 3-based tunnel between the proxy device and the application server, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can resend the data to the proxy device through the QUIC between the proxy device and the application server due to the tunnel between the proxy device and the application server. Compared with existing solutions, the application server resends data directly to the proxy device, which is conducive to improving the efficiency of data retransmission.

[0045] In a fifth aspect, an embodiment of the present application provides a downlink data transmission method, applied to a user equipment, the method comprising:

[0046] The user device sends a first tunnel negotiation request to the proxy device, where the first tunnel negotiation request is used to request the establishment of a QUIC between the proxy device and the application server; the user device receives a downlink message sent by the proxy device, and the downlink message received by the user device from the proxy device is obtained based on the downlink message sent by the application server to the proxy device through QUIC.

[0047] The downlink message received by the user equipment from the proxy device includes the payload in the downlink message sent by the application server to the proxy device through QUIC.

[0048] By establishing QUIC between the proxy device and the application server, the application server and the proxy device transmit data through QUIC, which is beneficial to improving data transmission efficiency compared to the TCP connection in the existing technology.

[0049] In conjunction with the fifth aspect, in one possible implementation, when determining to start the function of establishing a tunnel, the first tunnel negotiation request includes a second identifier, and the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the http / 3 protocol.

[0050] In existing solutions, there is no tunnel between the proxy device and the application server, but only between the application server and the user device. Therefore, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can only resend the data directly to the user device. By instructing the establishment of a QUIC and http / 3-based tunnel between the proxy device and the application server, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can resend the data to the proxy device through the QUIC between the proxy device and the application server due to the tunnel between the proxy device and the application server. Compared with existing solutions, the application server resends data directly to the proxy device, which is conducive to improving the efficiency of data retransmission.

[0051] In a sixth aspect, an embodiment of the present application provides a downlink data transmission method, applied to an application server, the method comprising:

[0052] The application server receives a connection creation request sent by the proxy device, which is used to request the creation of a connection between the proxy device and the application server based on the QUIC protocol; sends a connection creation response message to the proxy device to respond to the connection creation request; and the application server sends a downlink message to the proxy device via QUIC.

[0053] By establishing QUIC between the proxy device and the application server, the application server and the proxy device transmit data through QUIC, which is beneficial to improving data transmission efficiency compared to the TCP connection in the existing technology.

[0054] In conjunction with the sixth aspect, in one possible implementation, the method of this embodiment further includes:

[0055] The application server receives a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the establishment of a tunnel based on the HTTP / 3 protocol between the proxy device and the application server; the application server sends a second tunnel negotiation response message to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

[0056] In existing solutions, there is no tunnel between the proxy device and the application server, but only between the application server and the user device. Therefore, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can only resend the data directly to the user device. By instructing the establishment of a QUIC and http / 3-based tunnel between the proxy device and the application server, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can resend the data to the proxy device through the QUIC between the proxy device and the application server due to the tunnel between the proxy device and the application server. Compared with existing solutions, the application server resends data directly to the proxy device, which is conducive to improving the efficiency of data retransmission.

[0057] In the seventh aspect, an embodiment of the present application provides a proxy device, which includes a module or unit for executing the method provided by the first aspect or any possible implementation method of the first aspect, or the method provided by the fourth aspect or any possible implementation method of the fourth aspect.

[0058] In an eighth aspect, an embodiment of the present application provides a user device, which proxy device includes a module or unit for executing the method provided in the second aspect or any possible implementation method of the second aspect, or the method provided in the fifth aspect or any possible implementation method of the fifth aspect.

[0059] In the ninth aspect, an embodiment of the present application provides an application server, wherein the proxy device includes a module or unit for executing the method provided in the third aspect or any possible implementation method of the third aspect, or the method provided in the sixth aspect or any possible implementation method of the sixth aspect.

[0060] In a tenth aspect, an embodiment of the present application provides a proxy device comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the first aspect or any possible implementation of the first aspect, or the method provided in the fourth aspect or any possible implementation of the fourth aspect.

[0061] In an eleventh aspect, an embodiment of the present application provides a user equipment comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the second aspect or any possible implementation of the second aspect, or the method provided in the fifth aspect or any possible implementation of the fifth aspect.

[0062] In a twelfth aspect, an embodiment of the present application provides an application server comprising a processor and a memory. The memory is configured to store program code. The processor is configured to invoke the program code stored in the memory to execute the method provided in the third aspect or any possible implementation of the third aspect, or the method provided in the sixth aspect or any possible implementation of the sixth aspect.

[0063] In the thirteenth aspect, an embodiment of the present application provides a computer storage medium comprising computer instructions, which, when the computer instructions are run on an electronic device, enable the electronic device to execute a method provided in any possible implementation of the first aspect, or a method provided in any possible implementation of the second aspect, or a method provided in any possible implementation of the third aspect, or a method provided in any possible implementation of the fourth aspect, or a method provided in any possible implementation of the fifth aspect, or a method provided in any possible implementation of the sixth aspect.

[0064] In a fourteenth aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the method provided in any possible implementation of the first aspect, or the method provided in any possible implementation of the second aspect, or the method provided in any possible implementation of the third aspect, or the method provided in any possible implementation of the fourth aspect, or the method provided in any possible implementation of the fifth aspect, or the method provided in any possible implementation of the sixth aspect.

[0065] In a fifteenth aspect, an embodiment of the present application further provides a method for downlink transmission of application metadata, which is applied to a communication system including a user device, an access network device, a proxy device, and an application server, and the method includes:

[0066] The application server sends a first downlink message to the proxy device through the QUIC between the proxy device and the application server. The first downlink message includes application metadata and a payload. The proxy device sends the application metadata in the first downlink message to the access network device. The application metadata is used by the access network device to adjust the connection parameters between the access network device and the user device. The proxy device sends a second downlink message to the user device. The second downlink message includes a payload, which is parsed from the first downlink message.

[0067] In a sixteenth aspect, an embodiment of the present application further provides a communication system, which includes a user device, an access network device, a proxy device, and an application server.

[0068] The application server is configured to send a first downlink message to the proxy device through QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload;

[0069] The proxy device is configured to send the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment;

[0070] The proxy device is configured to send a second downlink message to the user equipment, where the second downlink message includes a payload, and the payload is parsed from the first downlink message.

[0071] In a seventeenth aspect, an embodiment of the present application further provides a method for downlink transmission of application metadata, which is applied to a communication system including a user device, an access network device, a proxy device, and an application server, and the method includes:

[0072] The user device sends a first tunnel negotiation request to the proxy device, where the first tunnel negotiation request is used to request the establishment of QUIC between the proxy device and the application server; the proxy device sends a connection creation request to the application server, where the connection creation request is used to request the establishment of a connection based on the QUIC protocol between the proxy device and the application server; the application server sends a downlink message to the proxy device through the QUIC between the proxy device and the application server, and the proxy device sends a downlink message to the user device obtained based on the downlink message sent by the application server to the proxy gateway.

[0073] In an eighteenth aspect, an embodiment of the present application further provides a communication system, the communication system including a user device, an access network device, a proxy device, and an application server, the method including:

[0074] The user equipment is configured to send a first tunnel negotiation request to the proxy device, where the first tunnel negotiation request is used to request establishment of a QUIC between the proxy device and the application server;

[0075] The proxy device is configured to send a connection creation request to the application server, where the connection creation request is used to request the establishment of a QUIC protocol-based connection between the proxy device and the application server.

[0076] The application server is configured to send a downlink message to the proxy device via QUIC between the proxy device and the application server;

[0077] The proxy device is configured to send a downlink message to the user equipment, obtained according to the downlink message sent by the application server to the proxy gateway.

[0078] It is understood that the detailed description of the proxy device, user device, and application server described in the fifteenth aspect, the sixteenth aspect, the seventeenth aspect, or the eighteenth aspect can be found in the method described in any one of the first aspect, the method described in any one of the second aspect, and the method described in any one of the third aspect, and will not be repeated here. The proxy device described in the seventh aspect or the tenth aspect is used to execute any one of the methods provided in the first aspect, or any one of the methods provided in the fourth aspect; the user device described in the eighth aspect or the eleventh aspect is used to execute any one of the methods provided in the second aspect or any one of the methods provided in the fifth aspect; the application server described in the ninth aspect or the twelfth aspect is used to execute any one of the methods provided in the third aspect or any one of the methods provided in the sixth aspect; the computer storage medium described in the thirteenth aspect and the computer program product described in the fourteenth aspect are both used to implement any one of the methods provided in the first aspect, or any one of the methods provided in the second aspect, or any one of the methods provided in the third aspect, or any one of the methods provided in the fourth aspect, or any one of the methods provided in the fifth aspect, or any one of the methods provided in the sixth aspect. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] FIG1 is a schematic diagram of a system architecture provided by an embodiment of the present application;

[0080] FIG2 is a flow chart of a method for downlink transmission of application metadata provided in an embodiment of the present application;

[0081] FIG3 is a flow chart of a method for downlink transmission of application metadata provided in an embodiment of the present application;

[0082] FIG4 is a schematic diagram of a flow chart of a method for downlink transmission of application metadata provided in an embodiment of the present application;

[0083] FIG5 is a schematic diagram of an interactive flow of a method for downlink transmission of application metadata provided in an embodiment of the present application;

[0084] FIG6 is a schematic diagram of an interactive process of another downlink transmission method of application metadata provided in an embodiment of the present application;

[0085] FIG7 is a schematic diagram of the structure of a proxy device provided in an embodiment of the present application;

[0086] FIG8 is a schematic structural diagram of a user equipment provided in an embodiment of the present application;

[0087] FIG9 is a schematic diagram of the structure of an application server provided in an embodiment of the present application;

[0088] FIG10 is a schematic diagram of the structure of another proxy device provided in an embodiment of the present application;

[0089] FIG11 is a schematic structural diagram of another user equipment provided in an embodiment of the present application;

[0090] FIG12 is a schematic diagram of the structure of another application server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0091] The terms "first", "second", "third" and "fourth" in the specification, claims and drawings of this application are used to distinguish different objects rather than to describe a specific order.

[0092] "Multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating the existence of three relationships. For example, "A and / or B" means: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0093] The embodiments of the present application are described below with reference to the accompanying drawings.

[0094] 1 , which is a schematic diagram of a system architecture provided by an embodiment of the present application. As shown in FIG1 , the system includes a user device 101 , an access network device 102 , a proxy device 103 , and an application server 104 .

[0095] Among them, the user device 101 is a user device that can support XR services, such as a smart phone, VR device, smart glasses, etc.

[0096] For wireless network scenarios, the access network device 102 is a base station that can provide high-speed data transmission, such as a 4G base station, a 5G base station, a 6G base station, etc. For fixed networks, the access network device 102 is an access gateway.

[0097] The proxy device 103 can be a MASQUE-based proxy, a gateway, a wireless network edge node such as a user plane function (UPF) entity, or a relay defined based on QUIC media transmission (media over QUIC, MOQ), etc.

[0098] The application server 104 is a server that can provide application services, such as a single server, a server cluster, a cloud server, a cloud computing service center, etc.

[0099] The implementation process of this application is described in detail below.

[0100] Referring to FIG2 , FIG2 is a flow chart of a method for downlink transmission of application metadata provided by an embodiment of the present application. The method is applied to the user equipment 101 in FIG1 . As shown in FIG2 , the method includes:

[0101] S201: User equipment sends a first tunnel negotiation request to a proxy device.

[0102] The first tunnel negotiation request is used to request the establishment of a QUIC between the proxy device and the application server. The QUIC is used by the application server to send a first downlink message to the proxy device; the first downlink message includes application metadata and a payload.

[0103] Among them, since the first downlink message is sent through QUIC between the proxy device and the application server, the first downlink message can be regarded as a QUIC message, and the application metadata is carried in the extension header of the QUIC message.

[0104] By using the QUIC message extension header to carry application metadata, the application server can transmit application metadata to the proxy gateway, that is, transmit application metadata downlink. And because the QUIC message extension header is encrypted, carrying application metadata through the QUIC message extension header ensures the security of application metadata and prevents tampering.

[0105] Specifically, before the user device sends the first tunnel negotiation request to the proxy device, a connection needs to be established between the user device and the proxy device. The user device sends a first connection creation request to the proxy device, where the first connection creation request is used to request the establishment of a connection between the user device and the proxy device. Optionally, the connection between the user device and the proxy device is based on the TCP protocol, the QUIC protocol, or another protocol. The proxy device sends a first connection creation response message to the user device in response to the first connection creation request. At this point, the connection between the user device and the proxy device is established. The user device can send the first tunnel negotiation request to the proxy device via the connection between the user device and the proxy device.

[0106] When a user device needs to hide its IP address or access restricted websites, the proxy device generally only needs to proxy the HTTP traffic of a single application in the user device. The relevant information of the proxy device (such as the address of the proxy device) is configured in the single application. In this case, the user device sends a first tunnel negotiation request to the proxy device, and the first tunnel negotiation request includes a third identifier, which is used to indicate that the connection between the proxy device and the application server is a connection based on the QUIC protocol.

[0107] In a possible implementation, when it is determined that the tunnel establishment function is started, the first tunnel negotiation request includes a second identifier, where the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the HTTP / 3 protocol.

[0108] Among them, the function of establishing a tunnel is used to create a tunnel between the proxy device and the application server. In one example, the activation of the tunnel establishment function of the user device refers to the user device activating an opposing tunnel or activating a proxy application, such as a virtual private network (VPN) application. The user device activates the function of establishing a tunnel, mainly for the user device to realize an end-to-end encrypted channel through the tunnel on the public network in addition to hiding the user IP. For the proxy device, the proxy device proxies the HTTP traffic of all applications in the user device, thereby realizing secure communication between the user device and the proxy server. Before the user device sends the first tunnel negotiation request to the proxy device, the user device has started an independent tunnel or proxy application.

[0109] The user device instructs the creation of QUIC between the proxy device and the application server, so that the application server can send application metadata to the proxy device through QUIC; the user device instructs the creation of a tunnel based on the http / 3 protocol between the proxy device and the application server, so that the application server can add application metadata in the downlink message, and at the same time, the proxy device can perceive the application metadata in the downlink message sent by the application server.

[0110] S202: The user equipment receives a second downlink message sent by the proxy device.

[0111] The second downlink message includes the payload in the first downlink message.

[0112] As can be seen, in this embodiment, the application server and the proxy device transmit data via QUIC between the proxy device and the application server, which is beneficial for improving data transmission efficiency compared to the TCP connection in the prior art. By carrying application metadata via the QUIC message extension header, the application server transmits application metadata to the proxy device, that is, transmits application metadata downlink. Furthermore, because the QUIC message extension header is encrypted, carrying application metadata via the QUIC message extension header ensures the security of the application metadata and prevents tampering.

[0113] Referring to FIG3 , FIG3 is a flow chart of a method for downlink transmission of application metadata provided by an embodiment of the present application. The method is applied to a proxy device. As shown in FIG3 , the method includes:

[0114] S301. The proxy device receives a first downlink message sent by the application server through QUIC between the application server and the proxy device. The first downlink message includes application metadata and a payload.

[0115] The first downlink message is a QUIC message, and the application metadata is carried in an extension header of the QUIC message.

[0116] By using the QUIC message extension header to carry application metadata, the application server can transmit application metadata to the user device, that is, transmit application metadata downlink. And because the QUIC message extension header is encrypted, carrying application metadata through the QUIC message extension header ensures the security of application metadata and prevents tampering.

[0117] In one possible implementation, the first downlink message includes a first identifier, which is used to indicate that the first downlink message carries application metadata. The proxy device obtains the application metadata from the first downlink message based on the first identifier. Specifically, upon receiving the first downlink message, the proxy device determines whether the first downlink message includes the first identifier. If the first downlink message includes the first identifier, the proxy device parses the first downlink message to obtain the application metadata. If the first downlink message does not include the first identifier, the proxy device does not perform the above operation.

[0118] By adding a first identifier to the downlink message to indicate that the downlink message carries application metadata, the user equipment does not need to parse each received downlink message to determine whether the downlink message carries application metadata, thereby reducing the workload of the user equipment.

[0119] S302: The proxy device sends the application metadata in the first downlink message to the access network device.

[0120] The application metadata is used by the access network device to adjust the connection parameters between the access network device and the user equipment. The connection parameters here include resources used for data transmission between the access network device and the user equipment, and interface parameters between the access network device and the user equipment.

[0121] Specifically, when the access network device is a base station, the proxy device sends a general packet radio service (GPRS) user plane tunneling protocol (GPRS Tunnelling Protocol for the user plane, GTP-U) message to the base station, and an extension header of the GTP-U message carries application metadata.

[0122] In one possible implementation, the proxy device converts the application metadata to obtain converted application metadata. The application metadata sent by the proxy device to the access network device is the converted application metadata. The extension header of the GTP-U message carries the converted application metadata.

[0123] S303: The proxy device sends a second downlink message to the user equipment. The second downlink message includes a payload, which is parsed from the first downlink message.

[0124] Specifically, there is a connection between the proxy device and the user device; optionally, the connection is a QUIC or TCP connection or a connection based on other protocols. When the connection between the proxy device and the user device is QUIC, the proxy device discards the application metadata in the first downlink message to obtain a third downlink message; the proxy device performs stream mapping on the third downlink message to obtain a second downlink message; when the connection between the proxy device and the user device is not QUIC, the proxy device parses the payload from the first downlink message and encapsulates the payload based on the protocol on which the connection between the proxy device and the user device is based to obtain a second downlink message. For example, if the connection between the proxy device and the user device is a TCP connection, the proxy device encapsulates the payload based on TCP to obtain a second downlink message, which is a TCP packet. After obtaining the second downlink message, the proxy device sends the second downlink message to the user device.

[0125] In one possible implementation, a proxy device receives a first tunnel negotiation request from a user device, where the first tunnel negotiation request is used to request the establishment of a tunnel between the proxy device and an application server. The proxy device sends a connection creation request to the application server, where the connection creation request is used to request the establishment of a QUIC-based connection between the proxy device and the application server. Optionally, the first tunnel negotiation request includes a first identifier, where the first identifier indicates that the connection type between the proxy device and the application server is a QUIC-based connection. Upon receiving a connection creation response message sent by the application server in response to the connection creation request, the proxy device sends a first tunnel negotiation response message to the user device in response to the first tunnel negotiation request.

[0126] By instructing the creation of QUIC between the proxy device and the application server, the application server can add application metadata in the downlink message. The downlink message here is a QUIC message. The application metadata is carried in the extension header of the QUIC message, ensuring the security of the application metadata and preventing it from being tampered with.

[0127] In one possible implementation, when the first tunnel negotiation request includes the second identifier, the proxy device, upon receiving a connection creation response message sent by the application server in response to the connection creation request, sends a second tunnel negotiation request to the application server based on the second identifier, where the second tunnel negotiation request is used to request establishment of a tunnel between the proxy device and the application server based on the HTTP / 3 protocol. Upon receiving a second tunnel negotiation response message sent by the application server in response to the second tunnel negotiation request, the proxy device sends a first tunnel negotiation response message to the user equipment in response to the first tunnel negotiation request, where the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the HTTP / 3 protocol.

[0128] It should be understood that the prerequisite for creating a tunnel based on the http / 3 protocol between the proxy device and the application server is that QUIC has been established between the proxy device and the application server. Therefore, when QUIC has not been established between the proxy device and the application server, if the proxy device receives a first tunnel negotiation request carrying the second identifier, the application server and the proxy device will first create a QUIC between the application server and the proxy device, and then create a tunnel based on the http / 3 protocol between the application server and the proxy device.

[0129] By establishing a tunnel based on the HTTP / 3 protocol between the proxy device and the application server, the application server can add application metadata to downlink messages, and the proxy device can also perceive the application metadata in downlink messages sent by the application server. In existing solutions, there is no tunnel between the proxy device and the application server, only between the application server and the user device. Therefore, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can only resend the data directly to the user device. By establishing a tunnel based on QUIC and the HTTP / 3 protocol between the proxy device and the application server, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can resend the data to the proxy device through the QUIC tunnel between the proxy device and the application server. Compared with existing solutions, the application server resends data directly to the proxy device, which helps improve the efficiency of data retransmission.

[0130] Referring to FIG4 , FIG4 is a flow chart of a method for downlink transmission of application metadata provided by an embodiment of the present application. The method is applied to an application server. As shown in FIG4 , the method includes:

[0131] S401: An application server receives a connection creation request sent by a proxy device.

[0132] Among them, the connection creation request is used to request the creation of a QUIC protocol-based connection between the proxy device and the application server, that is, the second connection creation request is used to request the creation of QUIC between the proxy device and the application server.

[0133] S402: The application server creates a QUIC protocol-based connection between the proxy device and the application server.

[0134] The application server and the proxy device establish QUIC, which ends with the application server sending a connection creation response message to the proxy device in response to the connection creation request.

[0135] In one possible implementation, the method of this embodiment further includes:

[0136] The application server receives a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the establishment of a tunnel based on the HTTP / 3 protocol between the proxy device and the application server; the application server sends a second tunnel negotiation response message to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

[0137] By establishing a tunnel based on the HTTP / 3 protocol between the proxy device and the application server, the application server can add application metadata to downlink messages, and the proxy device can also perceive the application metadata in downlink messages sent by the application server. In existing solutions, there is no tunnel between the proxy device and the application server, only between the application server and the user device. Therefore, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can only resend the data directly to the user device. By establishing a tunnel based on QUIC and the HTTP / 3 protocol between the proxy device and the application server, when the application server sends data to the user device, if there is a long RTT or packet loss, the application server can resend the data to the proxy device through the QUIC tunnel between the proxy device and the application server. Compared with existing solutions, the application server resends data directly to the proxy device, which helps improve the efficiency of data retransmission.

[0138] S403. The application server sends a first downlink message to the proxy device through QUIC.

[0139] The first downlink message carries application metadata and a payload. The first downlink message is a QUIC message. The application metadata is carried in an extension header of the QUIC message.

[0140] By using the QUIC message extension header to carry application metadata, the application server can transmit application metadata to the proxy device, that is, transmit application metadata downlink. And because the QUIC message extension header is encrypted, carrying application metadata through the QUIC message extension header ensures the security of application metadata and prevents tampering.

[0141] Referring to FIG5 , FIG5 is a schematic diagram of an interactive process of a method for downlink transmission of application metadata provided by an embodiment of the present application. The method is applied to the system shown in FIG1 . As shown in FIG5 , the method includes:

[0142] S501: A user device sends a first connection creation request to a proxy device.

[0143] In one example, a user device sends a first connection creation request to a proxy device based on the HTTP / X protocol. The first connection creation request is used to request the establishment of a connection between the user device and the proxy device. Optionally, the connection between the user device and the proxy device is a TCP-based connection, a QUIC-based connection, or a connection based on another protocol.

[0144] S502: The proxy device sends a first connection creation response message to the user equipment.

[0145] The first response message is used to respond to the first connection creation request. It should be understood that the user equipment receiving the first response message indicates that the connection between the user equipment and the proxy device has been established.

[0146] S503: The user equipment sends a first tunnel negotiation request to the proxy device.

[0147] Specifically, the user device sends a first tunnel negotiation request to the proxy device based on the CONNECT method defined by HTTP / 1, HTTP / 2, or HTTP / 3, wherein the first tunnel negotiation request includes a third identifier, and the third identifier indicates that the connection between the proxy device and the application server is QUIC.

[0148] In one example, taking the case where a tunnel negotiation request is sent to a proxy device using the CONNECT method defined in HTTP / 1.1, and the connection between the proxy device and the application server is a connection based on the QUIC protocol, the format of the first tunnel negotiation request is:

[0149] CONNECT target.example.com:80HTTP / 1.1

[0150] host:target.example.com

[0151] proxy-protocol:QUIC

[0152] In the above example, the third identifier is proxy-protocol.

[0153] S504: The proxy device sends a second connection creation request to the application server.

[0154] The second connection creation request is used to request the creation of QUIC between the proxy device and the application server.

[0155] Specifically, when the proxy device receives the first tunnel negotiation request, it sends a second connection creation request to the application server based on the application server information indicated by the host or authority in the first tunnel negotiation request and the third identifier, requesting to create a QUIC between the proxy device and the application server.

[0156] S505: The application server sends a second connection creation response message to the proxy device.

[0157] The second connection creation response message is used to respond to the second connection creation request. It should be understood that the user equipment receiving the second connection creation response message indicates that the QUIC between the application server and the proxy device has been established.

[0158] S506: The proxy device sends a first tunnel negotiation response message to the user equipment.

[0159] The first tunnel negotiation response message is used to respond to the first tunnel negotiation request.

[0160] After the tunnel between the user device and the application server is successfully established, the proxy device works at the connection layer. Based on maintaining the TCP\QUIC connection and the mapping relationship between QUIC sub-streams, HTTP / 2 streams, and HTTP requests on both sides of the proxy device, the proxy device performs bidirectional transparent forwarding of uplink or downlink messages.

[0161] S507: The application server sends a first downlink message to the proxy device.

[0162] Specifically, the application server sends a first downlink message to the proxy device through the second connection. The first downlink message includes application metadata and a payload. Optionally, the first downlink message is a QUIC DATAGRAM frame or a Datagram Capsule message. The application metadata is carried by the newly defined Context Payload in the QUIC DATAGRAM frame or the Datagram Capsule message.

[0163] The first downlink message includes a first identifier, and the first identifier is used to indicate that the first downlink message carries application metadata.

[0164] In an example, the encapsulation format of a QUIC DATAGRAM frame is:

[0165] In another example, the encapsulation format of the Datagram Capsule message is:

[0166] Among them, Context ID(i) is the above-mentioned first identifier.

[0167] S508: The proxy device sends a second downlink message to the user equipment.

[0168] Specifically, after receiving the first downlink message sent by the application server via QUIC, the proxy device uses the payload of the application carried in the first downlink message as the payload of the second downlink message, and sends the second downlink message to the user device. The second downlink message is a TCP message or a QUIC message. When the connection between the proxy device and the user device is QUIC, the proxy device discards the application metadata in the first downlink message to obtain a third downlink message; the proxy device performs stream mapping on the third downlink message to obtain a second downlink message; when the connection between the proxy device and the user device is not QUIC, the proxy device parses the payload from the first downlink message and encapsulates the payload based on the protocol on which the connection between the proxy device and the user device is based to obtain a second downlink message. For example, if the connection between the proxy device and the user device is a TCP connection, the proxy device encapsulates the payload based on TCP to obtain a second downlink message, which is a TCP message.

[0169] The proxy device converts the application metadata carried in the first downlink message to obtain converted application metadata; then, the converted metadata is sent to the access network device via a GTP-U message, where the converted metadata is carried in an extension header of the GTP-U message. The proxy device forwards the converted application metadata to the access network device so that the access network device can adjust the connection parameters between the access network device and the user equipment. These connection parameters include resources used for data transmission between the access network device and the user equipment, and interface parameters between the access network device and the user equipment.

[0170] It can be seen that in the embodiment, by establishing a connection based on the QUIC protocol between the proxy device and the application server, the application server sends application metadata to the proxy device through QUIC. Compared with TCP messages, QUIC messages have enough extension headers to carry application metadata, and can adapt to the future trend of TCP evolving to QUIC. This method has little impact on user devices and application servers. For user devices, it is only necessary to carry an identifier (such as proxy-protocol) in the connection creation request sent to the proxy device to indicate that the connection between the proxy device and the application server is based on the QUIC protocol. For the application server, it is only necessary to support the QUIC protocol. The user device, proxy device and application server adopt a two-segment connection method. Since the proxy device and the application server transmit data based on QUIC, this method has the ability to accelerate transmission compared to the TCP connection method.

[0171] Referring to FIG6 , FIG6 is a schematic diagram of an interactive process of another downlink transmission method for application metadata provided by an embodiment of the present application. The method is applied to the system shown in FIG1 . As shown in FIG6 , the method includes:

[0172] S601: A user device sends a first connection creation request to a proxy device.

[0173] In one example, a user device sends a first connection creation request to a proxy device via the HTTP / X protocol. The first connection creation request is used to request the establishment of a connection between the user device and the proxy device. Optionally, the connection between the user device and the proxy device is a TCP-based connection, a QUIC-based connection, or a connection based on another protocol.

[0174] S602: The proxy device sends a first connection creation response message to the user equipment.

[0175] The first response message is used to respond to the first connection creation request. It should be understood that the user equipment receiving the first response message indicates that the first connection between the user equipment and the proxy device has been established.

[0176] S603: The user equipment sends a first tunnel negotiation request to the proxy device.

[0177] Specifically, the user device sends a first tunnel negotiation request to the proxy device using the CONNECT-EXT2 method defined in HTTP / X. The first tunnel negotiation request includes a second identifier that indicates that the tunnel between the proxy device and the application server is based on the HTTP / 3 protocol. The syntax and semantics of tokens such as protocol, scheme, path, and authority in the first tunnel negotiation request are the same as those in the MASQUE EXT-CONNECT method.

[0178] In one example, taking the tunnel type between the proxy device and the application server as a tunnel based on the HTTP / 3 protocol, the format of the first tunnel negotiation request is:

[0179] :method=CONNECT

[0180] :protocol=connect-udp

[0181] :scheme=https

[0182] :path= / target.example.com / 443 /

[0183] :authority=proxy.example.com

[0184] :proxy-tunnel=h3

[0185] S604: The proxy device sends a second connection creation request to the application server.

[0186] Specifically, after the proxy device receives the first tunnel negotiation request, the proxy device sends a second connection creation request to the application server, where the second connection creation request is used to request the creation of an outer layer QUIC protocol-based connection between the proxy device and the application server.

[0187] S605: The application server sends a second connection creation response message to the proxy device.

[0188] The second connection creation response message is used to respond to the second connection creation request. It should be understood that the receipt of the second connection creation response message by the proxy device indicates that the outer layer QUIC protocol-based connection between the application server and the proxy device has been established.

[0189] S606: The proxy device sends a second tunnel negotiation request to the application server.

[0190] Specifically, the proxy device sends a second tunnel negotiation request to the application server based on the second identifier, wherein the second tunnel negotiation request is used to request the creation of a tunnel between the proxy device and the application server, and the tunnel is a tunnel based on the http / / 3 protocol.

[0191] S607: The application server sends a second tunnel negotiation response message to the proxy device.

[0192] The second tunnel negotiation response message is used to secondly respond to the tunnel negotiation request. The receipt of the second tunnel negotiation response message by the proxy device indicates that the tunnel between the proxy device and the application server is successfully established.

[0193] S608: The proxy device sends a first tunnel negotiation response message to the user equipment.

[0194] The first tunnel negotiation response message is used to first respond to the tunnel negotiation request. After the tunnel between the user device, proxy device, and application server is successfully established, the proxy device operates at the connection layer, maintaining the connection between the two sides or the QUIC and HTTP / 2 stream mapping relationship, and performs format parsing, encapsulation, and bidirectional transparent forwarding of uplink or downlink messages.

[0195] S609: The application server sends a first downlink message to the proxy device.

[0196] Specifically, the application server sends a first downlink message to the proxy device through the outer QUIC between the application server and the proxy device, wherein the first downlink message includes application metadata and a payload. Optionally, the first downlink message is a QUIC DATAGRAM frame or a Datagram Capsule message. The encapsulation format can be found in the relevant description of S507 and will not be described here. The application metadata is carried by the QUIC DATAGRAM frame or the newly defined Context Payload in the Datagram Capsule message. The first downlink message includes a first identifier, which is used to indicate that the first downlink message carries application metadata.

[0197] S610: The proxy device sends a second downlink message to the user equipment.

[0198] Specifically, after receiving the first downlink message sent by the application server via QUIC, the proxy device uses the payload of the application carried in the first downlink message as the payload of the second downlink message, and sends the second downlink message to the user device. The second downlink message is a TCP message or a QUIC message. When the connection between the proxy device and the user device is QUIC, the proxy device discards the application metadata in the first downlink message to obtain a third downlink message; the proxy device performs stream mapping on the third downlink message to obtain a second downlink message; when the connection between the proxy device and the user device is not QUIC, the proxy device parses the payload from the first downlink message and encapsulates the payload based on the protocol on which the connection between the proxy device and the user device is based to obtain a second downlink message. For example, if the connection between the proxy device and the user device is a TCP connection, the proxy device encapsulates the payload based on TCP to obtain a second downlink message, which is a TCP message.

[0199] The proxy device converts the application metadata carried in the first downlink message to obtain converted application metadata; then, the converted metadata is sent to the access network device via a GTP-U message, where the converted metadata is carried in an extension header of the GTP-U message. The proxy device forwards the converted application metadata to the access network device so that the access network device can adjust the connection parameters between the access network device and the user equipment. These connection parameters include resources used for data transmission between the access network device and the user equipment, and interface parameters between the access network device and the user equipment.

[0200] As can be seen, in this embodiment, a layered, two-stage tunnel connection is employed for the proxy device, enabling the carrying of application metadata in both upstream and downstream messages. This approach has minimal impact on user devices and application servers. The user device only needs to include a "Proxy-Tunnel" header field in the connection establishment request sent to the proxy device, indicating that the tunnel type between the proxy device and the application server is HTTP / 3. The application server only needs to support standard HTTP / 3 tunnel negotiation capabilities. The user device, proxy device, and application server utilize a two-stage back-to-back connection, resulting in higher transmission efficiency than the EXT-CONNECT approach.

[0201] 7, which is a schematic diagram of the structure of a proxy device provided in an embodiment of the present application. The proxy device is the proxy device 103 in FIG1. ​​As shown in FIG7, the proxy device 103 includes:

[0202] A receiving unit 701 is configured to receive a first downlink message sent by an application server to a proxy device via QUIC, where the first downlink message includes application metadata and a payload.

[0203] A sending unit 702 is configured to send the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment;

[0204] The sending unit 702 is further configured to send a second downlink message to the user equipment, where the second downlink message includes a payload, which is parsed from the first downlink message.

[0205] In one possible implementation, the first downlink message includes a first identifier, where the first identifier is used to indicate that the first downlink message carries application metadata; and the proxy device 103 further includes:

[0206] The acquiring unit 703 is configured to acquire application metadata from the first downlink message according to the third identifier.

[0207] In one possible implementation, the proxy device 103 further includes:

[0208] The conversion unit 704 is used to convert the application metadata.

[0209] In terms of sending the application metadata in the first downlink message to the access network device, the sending unit 702 is specifically configured to:

[0210] Send the converted application metadata to the access network device.

[0211] In one possible implementation, when the connection between the proxy device and the user device is based on the QUIC protocol, the second downlink message is obtained by stream mapping the third downlink message, and the third downlink message is obtained by removing the application metadata in the first downlink message; when the connection between the proxy device and the user device is not based on the QUIC protocol, the second downlink message is obtained by encapsulating the payload using the protocol on which the connection between the proxy device and the user device is based.

[0212] In one possible implementation, the receiving unit 701 is further configured to receive a first tunnel negotiation request from a user device, where the first tunnel negotiation request is used to request establishment of a QUIC between the proxy device and the application server;

[0213] The sending unit 702 is further configured to send a connection creation request to the application server, where the connection creation request is used to request the establishment of a QUIC protocol-based connection between the proxy device and the application server.

[0214] The sending unit 702 is further configured to send a first tunnel negotiation response message for responding to the first tunnel negotiation request to the user equipment when the receiving unit 701 receives the connection creation response message sent by the application server for responding to the connection creation request.

[0215] In one possible implementation, the sending unit 702 is further configured to, when the first tunnel negotiation request includes the second identifier, send a connection creation request to the application server, where the connection creation request is used to request establishment of a QUIC protocol-based connection between the proxy device and the application server; the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the HTTP / 3 protocol;

[0216] The sending unit 702 is further configured to send a second tunnel negotiation request to the application server when the receiving unit 701 receives the connection creation response message sent by the application server in response to the connection creation request, where the second tunnel negotiation request is used to request the establishment of a tunnel based on the HTTP / 3 protocol between the proxy device and the application server;

[0217] The sending unit 702 is further configured to send a first tunnel negotiation response message for responding to the first tunnel negotiation request to the user equipment when the receiving unit 701 receives the first tunnel negotiation response message for responding to the second tunnel negotiation request sent by the application server.

[0218] It is worth noting that the specific functional implementation of the proxy device 103 is described in the description of the method shown in FIG3 above. Each unit or module in the proxy device 103 can be individually or completely combined into one or more other units or modules to form a structure, or one (or more) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0219] 8, which is a schematic diagram of the structure of a user device provided in an embodiment of the present application. The proxy device is the user device 101 in FIG1. ​​As shown in FIG8, the user device 101 includes:

[0220] A sending unit 801 is configured to send a first tunnel negotiation request to a proxy device, where the first tunnel negotiation request is used to request establishment of a QUIC connection between the proxy device and the application server; the QUIC connection is used by the application server to send a first downlink message to the proxy device; the first downlink message includes application metadata and a payload;

[0221] The receiving unit 802 is configured to receive a second downlink message sent by the proxy device, wherein the second downlink message is obtained according to the payload in the first downlink message.

[0222] In conjunction with the fifth aspect, in one possible implementation, when determining to start the function of establishing a tunnel, the first tunnel negotiation request includes a second identifier, and the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the http / 3 protocol.

[0223] It is worth noting that, for the specific functional implementation of the user device 101, please refer to the description of the method shown in Figure 2 above. Each unit or module in the user device 101 can be individually or completely merged into one or several other units or modules to form a unit, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a unit, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0224] 9 is a schematic diagram of the structure of an application server provided in an embodiment of the present application. The proxy device is the application server 104 in FIG1 . As shown in FIG9 , the application server 104 includes:

[0225] A receiving unit 901 is configured to receive a connection creation request sent by a proxy device, where the connection creation request is used to request the establishment of a QUIC protocol-based connection between the proxy device and the application server;

[0226] A creating unit 902 is configured to create a QUIC protocol-based connection between the proxy device and the application server;

[0227] The sending unit 903 is configured to send a first downlink message to the proxy device through the QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload.

[0228] In conjunction with the sixth aspect, in one possible implementation, the receiving unit 901 is further configured to receive a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the creation of a tunnel based on the HTTP / 3 protocol between the proxy device and the application server;

[0229] The sending unit 903 is further configured to send a second tunnel negotiation response message to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

[0230] It is worth noting that, for the specific functional implementation of the application server 104, please refer to the description of the method shown in Figure 4 above. The various units or modules in the application server 104 can be individually or completely merged into one or several other units or modules to form a structure, or one (or some) of the units or modules can be further divided into multiple functionally smaller units or modules to form a structure, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present invention. The above-mentioned units or modules are divided based on logical functions. In actual applications, the functions of one unit (or module) are implemented by multiple units (or modules), or the functions of multiple units (or modules) are implemented by one unit (or module).

[0231] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 10 , which shows a schematic diagram of the structure of a proxy device 1000 provided in an embodiment of the present invention. The proxy device 1000 shown in Figure 10 includes a memory 1001, a processor 1002, a communication interface 1003, and a bus 1004. The memory 1001, processor 1002, and communication interface 1003 are interconnected via bus 1004.

[0232] Optionally, the memory 1001 is a read-only memory (ROM), a static storage device, a dynamic storage device or a random access memory (RAM).

[0233] The memory 1001 can store programs. When the program stored in the memory 1001 is executed by the processor 1002, the processor 1002 and the communication interface 1003 are used to execute the various steps of the downlink transmission method of application metadata in the embodiment shown in FIG. 3 .

[0234] The processor 1002 uses a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a graphics processing unit (GPU) or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the proxy device 103 in the embodiment of the present application, or to execute the various steps of the downlink transmission method of the application metadata in the embodiment shown in Figure 3.

[0235] Processor 1002 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the downlink transmission method of application metadata of the present application can be completed by hardware integrated logic circuits or software instructions in processor 1002. Optionally, processor 1002 is a general-purpose processor, a digital signal processor (DSP), an ASIC, a field programmable gate array (FPGA), or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. Processor 1002 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor is a microprocessor or any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory 1001, and the processor 1002 reads the information in the memory 1001 and combines its hardware to complete the functions required to be performed by the units included in the proxy device 103 of the embodiment of the present application, or executes the various steps of the downlink transmission method of the application metadata of the embodiment shown in Figure 3.

[0236] The communication interface 1003 uses a transceiver, such as but not limited to a transceiver, to implement communication between the proxy device 103 and other devices (such as the user device 101 and the application server 104 shown in FIG1 ) or a communication network. For example, the proxy device 1000 can receive downlink messages from the application server 104 via the communication interface 1003 .

[0237] The bus 1004 may include a path for transmitting information between various components of the agent device 1000 (eg, the memory 1001 , the processor 1002 , and the communication interface 1003 ).

[0238] It should be noted that although the proxy device 1000 shown in FIG10 only shows a memory, a processor, and a communication interface, in a specific implementation, those skilled in the art will understand that the proxy device 1000 also includes other components necessary for normal operation. Furthermore, those skilled in the art will understand that the proxy device 1000 may also include hardware components that implement other additional functions, depending on specific needs. Furthermore, those skilled in the art will understand that the proxy device 1000 may only include the components necessary to implement the embodiments of the present application, and does not necessarily need to include all of the components shown in FIG10.

[0239] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 11, which shows a schematic diagram of the structure of a user device 1100 provided in an embodiment of the present invention. The user device 1100 shown in Figure 11 includes a memory 1101, a processor 1102, a communication interface 1103, and a bus 1104. The memory 1101, processor 1102, and communication interface 1103 are connected to each other via bus 1104.

[0240] Optionally, the memory 1101 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0241] The memory 1101 can store programs. When the program stored in the memory 1101 is executed by the processor 1102, the processor 1102 and the communication interface 1103 are used to execute the various steps of the downlink transmission method of application metadata in the embodiment shown in FIG. 2 .

[0242] The processor 1102 uses a general-purpose CPU, microprocessor, ASIC, GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the user equipment 101 of the embodiment of the present application, or to execute the various steps of the downlink transmission method of the application metadata of the embodiment shown in Figure 2.

[0243] Processor 1102 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the downlink transmission method of application metadata of the present application can be completed by hardware integrated logic circuits or software instructions in processor 1102. Optionally, processor 1102 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. Processor 1102 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other storage media well-known in the art. The storage medium is located in the memory 1101, and the processor 1102 reads the information in the memory 1101, and combines its hardware to complete the functions required to be performed by the units included in the user equipment 101 of the embodiment of the present application, or executes the various steps of the downlink transmission method of the application metadata of the embodiment shown in Figure 3.

[0244] The communication interface 1103 uses a transceiver, such as but not limited to a transceiver, to implement communication between the user device 1100 and other devices (such as the proxy device 103 shown in FIG1 ) or a communication network. For example, the user device 1100 can receive downlink messages from the master proxy device 103 via the communication interface 1103 .

[0245] The bus 1104 may include a path for transmitting information between various components of the user equipment 1100 (eg, the memory 1101 , the processor 1102 , and the communication interface 1103 ).

[0246] It should be noted that although the user equipment 1100 shown in FIG11 only shows a memory, a processor, and a communication interface, in a specific implementation, those skilled in the art will understand that the user equipment 1100 also includes other components necessary for normal operation. Furthermore, those skilled in the art will understand that the user equipment 1100 may also include hardware components for implementing other additional functions, depending on specific needs. Furthermore, those skilled in the art will understand that the user equipment 1100 may also include only the components necessary to implement the embodiments of the present application, and does not necessarily need to include all of the components shown in FIG11.

[0247] Based on the description of the above method embodiments and related device embodiments, please refer to Figure 12 , which shows a schematic diagram of the structure of an application server 1200 provided in an embodiment of the present invention. The application server 1200 shown in Figure 12 includes a memory 1201, a processor 1202, a communication interface 1203, and a bus 1204. The memory 1201, processor 1202, and communication interface 1203 are interconnected via bus 1204.

[0248] Optionally, the memory 1201 is a ROM, a static storage device, a dynamic storage device or a RAM.

[0249] The memory 1201 can store programs. When the program stored in the memory 1201 is executed by the processor 1202, the processor 1202 and the communication interface 1203 are used to execute the various steps of the downlink transmission method of application metadata in the embodiment shown in FIG. 4 .

[0250] The processor 1202 uses a general-purpose CPU, microprocessor, ASIC, GPU or one or more integrated circuits to execute relevant programs to implement the functions required to be performed by the units in the application server 104 of the embodiment of the present application, or to execute the various steps of the downlink transmission method of the application metadata of the embodiment shown in Figure 4.

[0251] Processor 1202 can also be an integrated circuit chip with signal processing capabilities. During implementation, each step of the downlink transmission method of application metadata of the present application can be completed by hardware integrated logic circuits or software instructions in processor 1202. Optionally, processor 1202 is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component. Processor 1202 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module is located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other storage media well-known in the art. The storage medium is located in the memory 1201, and the processor 1202 reads the information in the memory 1201, and combines its hardware to complete the functions required to be performed by the units included in the application server 104 of the embodiment of the present application, or executes the various steps of the downlink transmission method of the application metadata of the embodiment shown in Figure 4.

[0252] The communication interface 1203 uses a transceiver, such as but not limited to a transceiver, to implement communication between the application server 1200 and other devices (such as the proxy device 103 shown in FIG1 ) or a communication network. For example, the application server 1200 can obtain a connection establishment request from the proxy device 103 through the communication interface 1203.

[0253] The bus 1204 may include a path for transmitting information between various components of the application server 1200 (eg, the memory 1201 , the processor 1202 , and the communication interface 1203 ).

[0254] It should be noted that although the application server 1200 shown in FIG12 only shows a memory, a processor, and a communication interface, in a specific implementation, those skilled in the art will understand that the application server 1200 also includes other components necessary for normal operation. Furthermore, those skilled in the art will understand that the application server 1200 may also include hardware components that implement other additional functions, depending on specific needs. Furthermore, those skilled in the art will understand that the application server 1200 may only include the components necessary to implement the embodiments of the present application, and does not necessarily need to include all of the components shown in FIG8 .

[0255] An embodiment of the present application further provides a chip, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to implement the downlink transmission method of application metadata in an embodiment of the present application.

[0256] Optionally, as an implementation method, the chip also includes a memory, in which instructions are stored, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the downlink transmission method of the application metadata.

[0257] An embodiment of the present application also provides a computer-readable storage medium, which stores instructions. When the computer-readable storage medium is executed on a computer or a processor, the computer or processor executes one or more steps in any of the above methods.

[0258] The present application also provides a computer program product comprising instructions, which, when executed on a computer or processor, causes the computer or processor to execute one or more steps in any of the above methods.

[0259] Those skilled in the art will appreciate that the functions described in conjunction with the various illustrative logic blocks, modules, and algorithm steps disclosed herein can be implemented by hardware, software, firmware, or any combination thereof. If implemented in software, the functions described by the various illustrative logic blocks, modules, and steps may be stored or transmitted as one or more instructions or codes on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to tangible media, such as data storage media, or communication media including any media that facilitates the transfer of computer programs from one place to another (e.g., based on a communication protocol). In this manner, computer-readable media may generally correspond to (1) non-transitory tangible computer-readable storage media, or (2) communication media, such as signals or carrier waves. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, codes, and / or data structures for implementing the techniques described in this application. A computer program product may include computer-readable media.

[0260] By way of example, and not limitation, such computer-readable storage media include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection is properly referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of media. However, it should be understood that the computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transient media, but are actually directed to non-transitory tangible storage media. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), and Blu-ray disc. Disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also intended to be included within the scope of computer-readable media.

[0261] Instructions may be executed by one or more processors, such as one or more DSPs, general-purpose microprocessors, ASICs, FPGAs, or other equivalent integrated or discrete logic circuits. Thus, the term "processor," as used herein, may refer to any of the aforementioned structures or any other structure suitable for implementing the techniques described herein. Additionally, in some aspects, the functionality described by the various illustrative logical blocks, modules, and steps described herein is provided within dedicated hardware and / or software modules configured for encoding and decoding, or incorporated into a combined codec. Furthermore, the techniques may be fully implemented in one or more circuits or logic elements.

[0262] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the division of the unit is only a logical function division, and there are other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Optionally, the mutual coupling, direct coupling, or communication connection shown or discussed is an indirect coupling or communication connection through some interfaces, devices or units, such as electrical, mechanical or other forms.

[0263] Optionally, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., located in one place, or distributed across multiple network units. Some or all of the units may be selected based on actual needs to achieve the purpose of the solution of this embodiment.

[0264] In the above embodiments, all or part of the embodiments can be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.

[0265] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for downlink transmission of application metadata, characterized in that: Applied to a proxy device, the method comprises: Receiving a first downlink message sent by the application server through a fast user datagram protocol UDP network connection QUIC between the application server and the proxy device, the first downlink message including application metadata and a payload; Sending the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment; A second downlink message is sent to the user equipment, where the second downlink message includes the payload, and the payload is parsed from the first downlink message.

2. The method according to claim 1, characterized in that The first downlink message includes a third identifier, and the third identifier is used to indicate that the first downlink message carries the application metadata; the method also includes: The application metadata is acquired from the first downlink message according to the first identifier.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: converting the application metadata, The sending the application metadata in the first downlink message to the access network device includes: The converted application metadata is sent to the access network device.

4. The method according to any one of claims 1 to 3, characterized in that: When the connection between the proxy device and the user equipment is based on the QUIC protocol, the second downlink message is obtained by performing stream mapping on the third downlink message, and the third downlink message is obtained by removing application metadata from the first downlink message; When the connection between the proxy device and the user equipment is not based on the QUIC protocol, the second downlink message is obtained by encapsulating the payload using the protocol on which the connection between the proxy device and the user equipment is based.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: receiving a first tunnel negotiation request from a user device, where the first tunnel negotiation request is used to request to establish a QUIC between the proxy device and the application server; Sending a connection creation request to the application server, wherein the connection creation request is used to request to create a connection between the proxy device and the application server based on the QUIC protocol, When receiving the connection creation response message sent by the application server to respond to the connection creation request, a first tunnel negotiation response message to respond to the first tunnel negotiation request is sent to the user equipment.

6. The method according to claim 5, characterized in that The method further comprises: When the first tunnel negotiation request includes a second identifier, sending a connection creation request to the application server, the connection creation request is used to request to create a connection between the proxy device and the application server based on the QUIC protocol; the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the Hypertext Transfer Protocol / 3 protocol; When receiving a connection creation response message sent by the application server to respond to the connection creation request, sending a second tunnel negotiation request to the application server, where the second tunnel negotiation request is used to request to create a tunnel based on the Hypertext Transfer Protocol / 3 protocol between the proxy device and the application server; When receiving the first tunnel negotiation response message sent by the application server for responding to the second tunnel negotiation request, sending the first tunnel negotiation response message for responding to the first tunnel negotiation request to the user equipment.

7. A method for downlink transmission of application metadata, characterized in that: Applied to user equipment, the method comprises: Sending a first tunnel negotiation request to the proxy device, where the first tunnel negotiation request is used to request the creation of a fast user datagram protocol (UDP) network connection (QUIC) between the proxy device and the application server; the QUIC is used by the application server to send a first downlink message to the proxy device; the first downlink message includes application metadata and a payload; receiving a second downlink message sent by the proxy device, The second downlink message is obtained according to the payload in the first downlink message.

8. The method according to claim 7, characterized in that When determining that the function of establishing a tunnel is started, the first tunnel negotiation request includes a second identifier, and the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the Hypertext Transfer Protocol / 3 protocol.

9. A method for downlink transmission of application metadata, characterized in that: Applied to an application server, the method comprises: Receiving a connection creation request sent by a proxy device, wherein the connection creation request is used to request to create a connection between the proxy device and the application server based on a fast user datagram protocol UDP network connection QUIC protocol; Creating a QUIC protocol-based connection between the proxy device and the application server; A first downlink message is sent to the proxy device via QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload.

10. The method according to claim 9, characterized in that The method further comprises: receiving a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the creation of a tunnel based on the Hypertext Transfer Protocol / 3 protocol between the proxy device and the application server; A second tunnel negotiation response message is sent to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

11. A proxy device, characterized in that: include: A receiving unit, configured to receive a first downlink message sent by the application server through a fast user datagram protocol UDP network connection QUIC between the application server and the proxy device, wherein the first downlink message includes application metadata and a payload; A sending unit, configured to send the application metadata in the first downlink message to an access network device, wherein the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment; The sending unit is further configured to send a second downlink message to the user equipment, where the second downlink message includes the payload, and the payload is parsed from the first downlink message.

12. The proxy device according to claim 11, characterized in that: The first downlink message includes a third identifier, and the third identifier is used to indicate that the first downlink message carries the application metadata; and the proxy device further includes: An acquiring unit is configured to acquire the application metadata from the first downlink message according to the third identifier.

13. The treatment device according to claim 11 or 12, characterized in that: The proxy device also includes: a conversion unit, configured to convert the application metadata, In the aspect of sending the application metadata in the first downlink message to the access network device, the sending unit is specifically used to: The converted application metadata is sent to the access network device.

14. The processing device according to any one of claims 11 to 13, characterized in that: When the connection between the proxy device and the user equipment is based on the QUIC protocol, the second downlink message is obtained by performing stream mapping on the third downlink message, and the third downlink message is obtained by removing application metadata from the first downlink message; When the connection between the proxy device and the user equipment is not based on the QUIC protocol, the second downlink message is obtained by encapsulating the payload using the protocol on which the connection between the proxy device and the user equipment is based.

15. The processing device according to any one of claims 11 to 14, characterized in that: The receiving unit is further configured to receive a first tunnel negotiation request from a user device, where the first tunnel negotiation request is used to request to establish a QUIC between the proxy device and the application server; The sending unit is further used to send a connection creation request to the application server, wherein the connection creation request is used to request to create a connection between the proxy device and the application server based on the QUIC protocol, The sending unit is further configured to send a first tunnel negotiation response message for responding to the first tunnel negotiation request to the user equipment when the receiving unit receives the connection creation response message sent by the application server for responding to the connection creation request.

16. The method according to claim 15, characterized in that The sending unit is further configured to, when the first tunnel negotiation request includes a second identifier, send a connection creation request to the application server, wherein the connection creation request is used to request to create a connection between the proxy device and the application server based on the QUIC protocol; the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the Hypertext Transfer Protocol / 3 protocol; The sending unit is further configured to send a second tunnel negotiation request to the application server when the receiving unit receives a connection creation response message sent by the application server to respond to the connection creation request, wherein the second tunnel negotiation request is used to request the creation of a tunnel based on the Hypertext Transfer Protocol / 3 protocol between the proxy device and the application server; The sending unit is further configured to send a first tunnel negotiation response message for responding to the first tunnel negotiation request to the user equipment when the receiving unit receives the first tunnel negotiation response message sent by the application server for responding to the second tunnel negotiation request.

17. A user equipment, characterized in that: include: A sending unit, configured to send a first tunnel negotiation request to a proxy device, wherein the first tunnel negotiation request is used to request to establish a fast user datagram protocol UDP network connection QUIC between the proxy device and the application server; The QUIC is used by the application server to send a first downlink message to the proxy device; the first downlink message includes application metadata and a payload; a receiving unit, configured to receive a second downlink message sent by the proxy device, The second downlink message is obtained according to the payload in the first downlink message.

18. The user equipment according to claim 17, characterized in that When determining that the function of establishing a tunnel is started, the first tunnel negotiation request includes a second identifier, and the second identifier is used to indicate that the tunnel between the proxy device and the application server is a tunnel based on the Hypertext Transfer Protocol / 3 protocol.

19. An application server, characterized in that: include: A receiving unit, configured to receive a connection creation request sent by a proxy device, wherein the connection creation request is used to request to create a connection between the proxy device and the application server based on a fast user datagram protocol UDP network connection QUIC protocol; A creating unit, configured to create a connection between the proxy device and the application server based on the QUIC protocol; A sending unit is used to send a first downlink message to the proxy device through the QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload.

20. The application server according to claim 19, characterized in that: The receiving unit is further configured to receive a second tunnel negotiation request sent by the proxy device, where the second tunnel negotiation request is used to request the creation of a tunnel based on the Hypertext Transfer Protocol / 3 protocol between the proxy device and the application server; The sending unit is further configured to send a second tunnel negotiation response message to the proxy device, where the second tunnel negotiation response message is used to respond to the second tunnel negotiation request.

21. A method for downlink transmission of application metadata, characterized in that: The method is applied to a communication system, the communication system comprising a user device, an access network device, a proxy device and an application server, and the method comprises: The application server sends a first downlink message to the proxy device through a fast user datagram protocol UDP-based network connection QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload; The proxy device sends the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment; The proxy device sends a second downlink message to the user equipment, where the second downlink message includes the payload, and the payload is parsed from the first downlink message.

22. A communication system, characterized in that: The communication system includes user equipment, access network equipment, proxy equipment and application server, The application server is used to send a first downlink message to the proxy device through a fast user datagram protocol UDP-based network connection QUIC between the proxy device and the application server, where the first downlink message includes application metadata and a payload; The proxy device is configured to send the application metadata in the first downlink message to the access network device, where the application metadata is used by the access network device to adjust connection parameters between the access network device and the user equipment; The proxy device is configured to send a second downlink message to the user equipment, where the second downlink message includes the payload, and the payload is parsed from the first downlink message.

23. A proxy device, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 1 to 6.

24. A user equipment, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 7 to 8.

25. A user equipment, characterized in that: The method comprises a processor and a memory, wherein the memory is used to store program codes, and the processor is used to execute the program codes to implement the method according to any one of claims 9 to 10.

26. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

Images