Data processing method and apparatus

Abstract

Provided in the present application are a data processing method and an apparatus. The method comprises: acquiring transmission requirement information of multiple pieces of data, one of the multiple pieces of data being a data stream or a data packet set, and the data packet set comprising at least one data packet; on the basis of the transmission requirement information of the multiple pieces of data, determining a QUIC encapsulation identifier of the multiple pieces of data, there being a corresponding relation between the transmission requirement information of the multiple pieces of data and the QUIC encapsulation identifier of the multiple pieces of data; and sending to a first network element the QUIC encapsulation identifier of the multiple pieces of data, the QUIC encapsulation identifier of the multiple pieces of data being used for determining an identifier of a QoS stream corresponding to the QUIC encapsulation identifier of the multiple pieces of data. The data processing method and the apparatus provided by the present application can perform differentiated QoS control and processing on QUIC data packets, thereby reasonably using and scheduling network resources and improving the use experience of applications.

Description

Data processing method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 25, 2023, with application number 202311800910.3, and priority to the Chinese patent application entitled “Method and Apparatus for Data Processing”, all contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and more specifically, to a method and apparatus for data processing. Background Art

[0003] Currently, there are two trends in the data sent over the internet. First, because much data is latency-sensitive, low-latency applications are increasingly being used. Second, due to growing concerns about security and privacy, encrypted traffic is becoming increasingly common, reaching nearly 90%. Traditional internet traffic transmission based on the Transmission Control Protocol (TCP) suffers from long connection establishment delays and head-of-line blocking, making it difficult to meet the low-latency requirements of current internet applications.

[0004] Therefore, the Quick UDP Internet Connection (QUIC) was born. Based on UDP, it offers advantages such as low connection latency, multi-stream multiplexing without head-of-line blocking, header protection and encryption, and seamless connection migration. During QUIC data transmission, ensuring the proper scheduling of network resources is a pressing issue. Summary of the Invention

[0005] The present application provides a data processing method and apparatus that can perform differentiated QoS control and processing on QUIC data packets, thereby rationally utilizing and scheduling network resources and improving the application experience.

[0006] In a first aspect, a method for data processing is provided, including: obtaining transmission requirement information of multiple data, one of the multiple data is a data stream or a data packet set, and the data packet set includes at least one data packet; determining QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data; sending the QUIC encapsulation identifiers of the multiple data to a first network element, and the QUIC encapsulation identifiers of the multiple data are used to determine the identifiers of the QoS flows corresponding to the QUIC encapsulation identifiers of the multiple data.

[0007] In an embodiment of the present application, the QUIC encapsulation identifiers corresponding to the multiple data can be determined based on the transmission requirement information of the multiple data, and then the QUIC encapsulation identifiers of the multiple data can be sent to the first network element to determine the identifiers of the QoS flows of the multiple data through the QUIC encapsulation identifiers of the multiple data, so that differentiated QoS control and processing can be performed on the QUIC data packets, such as priority scheduling for QUIC data with high transmission requirements, low priority scheduling for QUIC data packets with low transmission requirements, or selective packet loss processing can be performed under network congestion, so that network resources can be reasonably utilized and scheduled when network resources are limited, and the application experience can be improved.

[0008] In combination with the first aspect, in certain implementations of the first aspect, the multiple data include a first business flow and a second business flow, and the QUIC encapsulation identifiers of the multiple data are determined based on the transmission requirement information of the multiple data, including: when the transmission requirement information of the first business flow and the second business flow is the same, determining the QUIC encapsulation identifiers of the first business flow and the second business flow to be the first encapsulation identifier; or, when the transmission requirement information of the first business flow and the second business flow is different, determining the QUIC encapsulation identifiers of the first business flow and the second business flow to be the second encapsulation identifier and the third encapsulation identifier, respectively.

[0009] In an embodiment of the present application, the QUIC encapsulation identifiers of multiple business flows can be determined based on the transmission requirement information of multiple data flows, so as to perform differentiated QoS control and processing on the multiple business flows, which can be applicable to transmission scenarios of business flows with multiple different transmission requirements.

[0010] In combination with the first aspect, in certain implementations of the first aspect, multiple data include a first data packet set and a second data packet set of the same business flow, and the QUIC encapsulation identifiers of the multiple data are determined based on the transmission requirement information of the multiple data, including: when the transmission requirement information of the first data packet set and the second data packet set is the same, determining the QUIC encapsulation identifiers of the first data packet set and the second data packet set as the first encapsulation identifier; or, when the transmission requirement information of the first data packet set and the second data packet set is different, determining the QUIC encapsulation identifiers of the first data packet set and the second data packet set as the second encapsulation identifier and the third encapsulation identifier, respectively.

[0011] In an embodiment of the present application, the QUIC encapsulation identifiers of multiple data packet sets can be determined based on the transmission requirement information of multiple data packet sets in a single data stream, so as to perform differentiated QoS control and processing on the multiple data packet sets, which can be applicable to the transmission scenario where there are multiple data packet sets with different transmission requirements in a single business stream.

[0012] In combination with the first aspect, in certain implementations of the first aspect, determining the transmission requirement information of multiple data includes: receiving information about multiple data from an application server, the information about the multiple data includes transmission requirement information of the multiple data; or receiving information about multiple data from an application server, the information about the multiple data includes description information of the multiple data and / or transmission requirement information corresponding to the description information; determining the transmission requirement information of the multiple data based on the information about the multiple data.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the QUIC encapsulation identifiers of the multiple data include information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or, the QUIC encapsulation identifiers of the multiple data include an IP address and port number that can be assigned by the transmission server, and / or, an IP address and port number that can be assigned by the transmission client.

[0014] In the embodiments of the present application, the QUIC encapsulation identifier can be represented by information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or the QUIC encapsulation identifier can be represented by the QUIC encapsulation identifier including the IP address and port number that can be assigned by the transmission server and / or the IP address and port number that can be assigned by the transmission client. In this way, different methods can be flexibly selected as the QUIC encapsulation identifier, thereby increasing the diversity of the QUIC encapsulation identifier.

[0015] In combination with the first aspect, in certain implementations of the first aspect, determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of multiple data includes: determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of multiple data and the first connection information; or determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of multiple data and the second connection information; or determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of multiple data, the first connection information, and the second connection information, wherein the first connection information is information that can be assigned by the transmission server to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be assigned by the transmission server and / or other information representing the QUIC connection, and the second connection information is information that can be assigned by the transmission client to represent the QUIC connection, the second connection information includes the QUIC connection identifier that can be assigned by the transmission client and / or other identifiers representing the QUIC connection.

[0016] In combination with the first aspect, in certain implementations of the first aspect, before determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the second connection information, or before determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data, the first connection information and the second connection information, the method also includes: receiving the second connection information sent from the transmission client.

[0017] In combination with the first aspect, in certain implementations of the first aspect, determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data includes: determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the first IP information; or determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the second IP information; or determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data, the first IP transmission information, and the second IP information, wherein the first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0018] In combination with the first aspect, in certain implementations of the first aspect, before determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the second IP information, or before determining the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data, the first IP information and the second IP information, the method also includes: receiving the second IP information sent from the transmission client.

[0019] In combination with the first aspect, in certain implementations of the first aspect, the QUIC encapsulation identifier of multiple data includes information in the QUIC tunnel header.

[0020] In an embodiment of the present application, the identification information can also be used through the information in the QUIC tunnel header, and different methods can be flexibly selected as the QUIC encapsulation identifier, thereby improving the diversity of the QUIC encapsulation identifier.

[0021] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending transmission requirement information of multiple data to the first network element.

[0022] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: receiving multiple data from an application server, where the multiple data are downlink data; encapsulating the multiple data using QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: sending the encapsulated multiple data to a second network element to map the encapsulated multiple data to a QoS flow corresponding to the QUIC encapsulation identifier of the multiple data, and the second network element includes a network element responsible for user plane functions.

[0024] In an embodiment of the present application, by sending multiple encapsulated data to the second network element, the second network element can determine the QoS flow corresponding to the data based on the QUIC encapsulation identifier in the encapsulated data, thereby providing differentiated QoS control and processing for multiple data with different transmission requirements.

[0025] In combination with the first aspect, in certain implementations of the first aspect, the method further includes: sending a QUIC encapsulation identifier of multiple data to the transmission client, so that the transmission client uses the QUIC encapsulation identifier of the multiple data to encapsulate the multiple data, and the multiple data are uplink data.

[0026] In combination with the first aspect, in some implementations of the first aspect, the application server includes a VAL server.

[0027] In combination with the first aspect, in some implementations of the first aspect, the transmission client includes a SEALDD client, and the transmission server includes a SEALDD server.

[0028] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: the first network element includes a network element responsible for session management, and the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of multiple data is determined by the first network element.

[0029] With reference to the first aspect, in certain implementations of the first aspect, the first network element includes a network element responsible for network capability exposure or a network element responsible for policy control.

[0030] According to a second aspect, a method for data processing is provided, including: receiving QUIC encapsulation identifiers of multiple data sent by a transmission server, the QUIC encapsulation identifiers of the multiple data are determined based on transmission requirement information of the multiple data, there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data, one of the multiple data includes a service flow or a data packet set, and the data packet set includes at least one data packet; according to the QUIC encapsulation identifiers of the multiple data, determining the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0031] In combination with the second aspect, in certain implementations of the second aspect, the multiple data include a first business stream and a second business stream, the QUIC encapsulation identifiers of the first business stream and the second business stream are the first encapsulation identifier, and the transmission requirement information of the first business stream and the second business stream are the same, or the QUIC encapsulation identifiers of the first business stream and the second business stream are the second encapsulation identifier and the third encapsulation identifier, respectively, and the transmission requirement information of the first business stream and the second business stream are different. In combination with the first aspect, in certain implementations of the first aspect, the multiple data include a first data packet set and a second data packet set of the same business stream, the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the first encapsulation identifier, and the transmission requirement information of the first data packet set and the second data packet set are the same, or the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the second encapsulation identifier and the third encapsulation identifier, respectively, and the transmission requirement information of the first data packet set and the second data packet set is different.

[0032] In combination with the second aspect, in certain implementations of the second aspect, the information of multiple data includes transmission requirement information of multiple data, and the information of multiple data comes from the application server; or, the transmission requirement information of multiple data is determined based on the information of multiple data, and the information of multiple data includes description information of multiple data and / or transmission requirement information corresponding to the description information.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the QUIC encapsulation identifier of multiple data includes information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or, the QUIC encapsulation identifier of multiple data includes an IP address and port number that can be assigned by the transmission server, and / or, an IP address and port number that can be assigned by the transmission client; or, the QUIC encapsulation identifier of multiple data includes information in the QUIC tunnel header.

[0034] In combination with the second aspect, in certain implementations of the second aspect, the QUIC encapsulation identifier of multiple data is determined based on the transmission requirement information of the multiple data and the first connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first connection information, and the second connection information, wherein the first connection information is information that can be assigned by the transmission server to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be assigned by the transmission server and / or other information representing the QUIC connection, and the second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes the QUIC connection identifier that can be assigned by the transmission client and / or other identifiers representing the QUIC connection.

[0035] In combination with the second aspect, in some implementations of the second aspect, the second connection information comes from the transmission client.

[0036] In combination with the second aspect, in certain implementations of the second aspect, the QUIC encapsulation identifier of multiple data is determined based on the transmission requirement information of the multiple data and the first IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first IP information and the second IP information, wherein the first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0037] In combination with the second aspect, in some implementations of the second aspect, the second IP information comes from the transmission client.

[0038] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving transmission requirement information of multiple data sent by the transmission server.

[0039] In combination with the second aspect, in some implementations of the second aspect, the application server includes a VAL server.

[0040] In combination with the second aspect, in some implementations of the second aspect, the transmission client includes a SEALDD client, and the transmission server includes a SEALDD server.

[0041] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: sending an identifier of the QoS flow corresponding to the QUIC encapsulation identifier of multiple data to a second network element, and the second network element includes a network element responsible for user plane functions.

[0042] According to a third aspect, a method for data processing is provided, including: receiving encapsulated multiple data sent by a transmission server, the encapsulated multiple data are obtained by encapsulating the multiple data using the QUIC encapsulation identifier of the multiple data, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the transmission requirement information of the multiple data corresponds to the QUIC encapsulation identifier of the multiple data, one data of the multiple data includes a business flow or a data packet set, and the data packet set includes at least one data packet; mapping the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0043] In combination with the third aspect, in certain implementations of the third aspect, before mapping the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data, the method also includes: receiving the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data from the first network element, wherein the first network element includes a network element responsible for session management.

[0044] In combination with the third aspect, in certain implementations of the third aspect, the multiple data include a first business stream and a second business stream, the QUIC encapsulation identifiers of the first business stream and the second business stream are the first encapsulation identifier, and the transmission requirement information of the first business stream and the second business stream are the same, or the QUIC encapsulation identifiers of the first business stream and the second business stream are the second encapsulation identifier and the third encapsulation identifier, respectively, and the transmission requirement information of the first business stream and the second business stream are different. In combination with the first aspect, in certain implementations of the first aspect, the multiple data include a first data packet set and a second data packet set of the same business stream, the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the first encapsulation identifier, and the transmission requirement information of the first data packet set and the second data packet set are the same, or the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the second encapsulation identifier and the third encapsulation identifier, respectively, and the transmission requirement information of the first data packet set and the second data packet set is different.

[0045] In combination with the third aspect, in certain implementations of the third aspect, the transmission requirement information of multiple data is determined based on the information of multiple data, the information of multiple data includes the description information of multiple data, or the information of multiple data includes the description information of multiple data and / or the transmission requirement information corresponding to the description information, the description information includes descriptor information and / or protocol description information, and the information of multiple data comes from the application server.

[0046] In combination with the third aspect, in certain implementations of the third aspect, the QUIC encapsulation identifier of multiple data includes information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or, the QUIC encapsulation identifier of multiple data includes an IP address and port number that can be assigned by the transmission server, and / or, an IP address and port number that can be assigned by the transmission client; or, the QUIC encapsulation identifier of multiple data includes information in the QUIC tunnel header.

[0047] In combination with the third aspect, in certain implementations of the third aspect, the QUIC encapsulation identifier of multiple data is determined based on the transmission requirement information of the multiple data and the first connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first connection information, and the second connection information, wherein the first connection information is information that can be assigned by the transmission server to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be assigned by the transmission server and / or other information representing the QUIC connection, and the second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes the QUIC connection identifier that can be assigned by the transmission client and / or other identifiers representing the QUIC connection.

[0048] In combination with the third aspect, in some implementations of the third aspect, the second connection information comes from the transmission client.

[0049] In combination with the third aspect, in certain implementations of the third aspect, the QUIC encapsulation identifier of multiple data is determined based on the transmission requirement information of the multiple data and the first IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first IP information and the second IP information, wherein the first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0050] In combination with the third aspect, in certain implementations of the third aspect, the second IP information comes from the transmission client.

[0051] In combination with the third aspect, in some implementations of the third aspect, the application server includes a VAL server.

[0052] In combination with the third aspect, in some implementations of the third aspect, the transmission client includes a SEALDD client, and the transmission server includes a SEALDD server.

[0053] In a fourth aspect, a method for data processing is provided, including: obtaining multiple data, one of the multiple data is a service flow or a data packet set, the data packet set includes at least one data packet, and the multiple data are uplink data; obtaining QUIC encapsulation identifiers of the multiple data, the QUIC encapsulation identifiers of the multiple data are determined based on the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data; encapsulating the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data; sending the encapsulated multiple data to the user device to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifiers of the multiple data.

[0054] In an embodiment of the present application, multiple data can be encapsulated based on the QUIC encapsulation identifier corresponding to the multiple data that have a corresponding relationship with the transmission demand information, and then the encapsulated data can be mapped to the QoS flow corresponding to the QUIC encapsulation identifier, so as to achieve differentiated QoS control and processing of QUIC data packets, such as priority scheduling for QUIC data with high transmission requirements, low priority scheduling for QUIC data packets with low transmission requirements, or selective packet loss processing under network congestion, which can reasonably utilize and schedule network resources when network resources are limited and improve the application experience.

[0055] In combination with the fourth aspect, in certain implementations of the fourth aspect, obtaining multiple data includes: receiving multiple data from an application client.

[0056] In combination with the fourth aspect, in certain implementations of the fourth aspect, obtaining the QUIC encapsulation identifier of multiple data includes: receiving the QUIC encapsulation identifier of multiple data from a transmission server.

[0057] In combination with the fourth aspect, in some implementations of the fourth aspect, the application client includes a VAL client.

[0058] In a fifth aspect, a method for data processing is provided, including: receiving encapsulated multiple data sent by a transmission client, the encapsulated multiple data are obtained by encapsulating the multiple data using the QUIC encapsulation identifier of the multiple data, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data, one of the multiple data is a service flow or a data packet set, the data packet set includes at least one data packet, and the multiple data are uplink data; mapping the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0059] In combination with the fifth aspect, in certain implementations of the fifth aspect, before mapping the encapsulated multiple data into the QoS flow of multiple data, the method also includes: receiving the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data from the first network element, and the first network element includes a network element responsible for network capability opening.

[0060] In a sixth aspect, a data processing device is provided, including: a processing unit, used to determine transmission requirement information of multiple data, one of the multiple data is a service flow or a data packet set, and the data packet set includes at least one data packet; and, based on the transmission requirement information of the multiple data, determining the QUIC encapsulation identifier of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data; a sending unit, used to send the QUIC encapsulation identifier of the multiple data to the first network element, and the QUIC encapsulation identifier of the multiple data is used to determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0061] In the seventh aspect, a data processing device is provided, including: a receiving unit, used to receive QUIC encapsulation identifiers of multiple data sent by a transmission server, the QUIC encapsulation identifiers of the multiple data are determined based on the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data, one data of the multiple data includes a business flow or a data packet set, and the data packet set includes at least one data packet; a processing unit, used to determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data based on the QUIC encapsulation identifier of the multiple data.

[0062] In an eighth aspect, a data processing device is provided, including: a receiving unit for receiving encapsulated multiple data sent by a transmission server, the encapsulated multiple data are obtained by encapsulating the multiple data using the QUIC encapsulation identifier of the multiple data, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data, one data of the multiple data includes a business flow or a data packet set, and the data packet set includes at least one data packet; a processing unit for mapping the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0063] In the ninth aspect, a data processing device is provided, including: an acquisition unit, used to acquire multiple data, one of the multiple data is a service flow or a data packet set, the data packet set includes at least one data packet, and the multiple data are uplink data; and, obtaining QUIC encapsulation identifiers of the multiple data, the QUIC encapsulation identifiers of the multiple data are determined according to the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data; a processing unit, used to encapsulate the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data; a sending unit, used to send the encapsulated multiple data to the user equipment to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifiers of the multiple data.

[0064] In the tenth aspect, a data processing device is provided, including: a receiving unit, receiving multiple encapsulated data sent by a transmission client, the encapsulated multiple data are obtained by encapsulating the multiple data using the QUIC encapsulation identifier of the multiple data, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data, one of the multiple data is a service flow or a data packet set, the data packet set includes at least one data packet, and the multiple data are uplink data; a processing unit, used to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0065] In the eleventh aspect, a computer-readable medium is provided, wherein the computer-readable medium stores a program code. When the computer program code runs on a computer, the computer executes the method described in any possible implementation of the first to fifth aspects above.

[0066] In the twelfth aspect, a communication device is provided, comprising: at least one processor, wherein the at least one processor is coupled to a memory, and is used to read and execute instructions in the memory to execute a method as described in any possible implementation of the first to fifth aspects of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] FIG1 is a diagram of the 5G mobile communication system architecture provided in an embodiment of the present application.

[0068] FIG2 is a schematic diagram of the 5G QoS architecture provided in an embodiment of the present application.

[0069] Figure 3 is a schematic diagram of the mapping of 5G QoS flows provided in an embodiment of the present application.

[0070] Figure 4 is a schematic diagram of the encryption of the QUIC protocol provided in an embodiment of the present application.

[0071] FIG5 is a schematic diagram of an architecture for performing QoS processing at a granularity of PDU Set provided in an embodiment of the present application.

[0072] FIG6 is a schematic diagram of the architecture of the SEALDD enhancement layer provided in an embodiment of the present application.

[0073] FIG7 is a schematic diagram of data processing of a SEALDD enhancement layer provided in an embodiment of the present application.

[0074] 8 to 15 are flowcharts of the data processing method provided in the embodiments of the present application.

[0075] 16 to 21 are schematic diagrams of data processing devices provided in embodiments of the present application. DETAILED DESCRIPTION

[0076] The technical solution in this application will be described below with reference to the accompanying drawings.

[0077] Figure 1 shows a 5G mobile communication system architecture diagram, including user equipment (UE) 110, access network (AN) 120, core network (CN) and data network (DN) 140. Among them, the architecture mainly includes UE 110, AN 120, and CN. Logically, they can be divided into two parts: the user plane and the control plane. The control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data. In the figure, the N2 reference point is located between the access network control plane and the core network control plane, the N3 reference point is located between the access network user plane and the core network user plane, and the N6 reference point is located between the core network user plane and the data network. The network architecture shown in Figure 1 may specifically include the following components:

[0078] UE 110: It is the entry point for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to users, and accepts user input. UE 110 uses new air interface technologies to establish signaling and data connections with AN 120, transmitting control signals and service data to the mobile network.

[0079] The user equipment in the embodiments of the present application may be referred to as a terminal device, terminal, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user apparatus. UE 110 may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a future 5G network, or a terminal device in a future evolved public land mobile network (PLMN), etc. It may also be an end device, a logical network element, an intelligent device such as a mobile phone, an intelligent terminal, or a communication device such as a server, a gateway, a base station, or a controller, or an Internet of Things (IoT) device such as a sensor, an electricity meter, or a water meter. UE may also be a wired device such as a computer or a laptop. The embodiments of the present application are not limited to this.

[0080] AN 120: Similar to a base station in a traditional network, it is deployed near UE 110 and provides network access for authorized users in a specific area. It also determines transmission tunnels of varying quality to transmit user data based on user level and service requirements. AN 120 manages its own resources, utilizing them effectively, providing access services to UE 110 on demand, and forwarding control signals and user data between the UE and the core network.

[0081] The access network can be an access network that adopts different access technologies. There are two types of current wireless access technologies: 3rd Generation Partnership Project (3GPP) access technology (such as the wireless access technology adopted in 3G, 4G or 5G systems) and non-3GPP access technology. 3GPP access technology refers to access technology that complies with 3GPP standards and specifications. The access network that adopts 3GPP access technology is called Radio Access Network (RAN), among which the access network equipment in the 5G system is called next generation Node Base station (gNB). Non-3GPP access technology refers to access technology that does not comply with 3GPP standards and specifications, for example, the air interface technology represented by the access point (AP) in WiFi.

[0082] An access network that implements access network functions based on wired communication technology can be called a wired access network.

[0083] An access network that implements network access functions based on wireless communication technologies is called a radio access network (RAN). The RAN manages radio resources, provides access services to terminals, and forwards control signals and user data between terminals and the core network.

[0084] The wireless access network device can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an AP in a WiFi system, etc. It can also be a wireless controller in a cloud radio access network (CRAN) scenario, or the access network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, or a network device in a future evolved PLMN network, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the wireless access network device. It can be understood that all or part of the functions of the wireless access network device in the present application can also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).

[0085] CN: Responsible for maintaining mobile network subscription data, managing mobile network elements, and providing session management, mobility management, policy management, security authentication, and other functions for UE 110. It provides network access authentication for UE 110 when it is attached; allocates network resources for UE 110 when it has a service request; updates network resources for UE 110 when it moves; provides a fast recovery mechanism for UE 110 when it is idle; releases network resources for UE 110 when it detaches; and provides data routing for UE 110 when it has service data, such as forwarding uplink data to DN 140; or receiving downlink data from UE 110 from DN 140 and forwarding it to AN 120 for transmission to UE 110.

[0086] DN 140: This is the data network that provides business services to users. Typically, the client is located in the UE, and the server is located in the data network. The data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by operators, such as the network that provides IP multimedia subsystem (IMS) services.

[0087] In order to understand the 5G network architecture, the core network of the 5G network architecture is further explained below.

[0088] The core network control plane adopts a service-oriented architecture. The interaction between control plane network elements adopts the service call method, replacing the point-to-point communication method in the traditional architecture. In the service-oriented architecture, the control plane network elements will open services to other control plane network elements for other control plane network elements to call. In point-to-point communication, the communication interface between control plane network elements will have a specific set of messages, which can only be used by the control plane network elements at both ends of the interface when communicating. The functions of the functional network elements in the core network (network elements) are as follows:

[0089] User plane function (UPF) network element 130: This is also known as a data plane gateway. It can be used for packet routing and forwarding, or for quality of service (QoS) processing of user plane data. User data can be connected to DN 140 through this network element. In this embodiment of the present application, it can be used to implement the functions of a user plane gateway.

[0090] Session Management Function (SMF) network element 150: This is primarily used for session management, Internet Protocol (IP) address allocation and management for UE 110, selection of endpoints for manageable user plane functions, policy control, or charging function interfaces, and downlink data notification. In embodiments of the present application, this can be used to implement the functions of a session management network element. It is primarily used for user plane network element selection, user plane network element redirection, IP address allocation for terminal devices, and session establishment, modification, and release, as well as QoS control.

[0091] Access and mobility management function (AMF) network element 160: This is primarily used for mobility management and access management, and can be used to implement other functions of the mobility management entity (MME) besides session management, such as lawful interception or access authorization (or authentication). In the embodiment of the present application, it can be used to implement the functions of the access and mobility management network element.

[0092] Authentication server function (AUSF) network element 170: mainly used for user authentication, etc.

[0093] Network slice selection function (NSSF) network element 180: used to select the set of network slice instances serving UE 110, determine the allowed network slice selection assistance information (NSSAI), etc.

[0094] Network exposure function (NEF) network element 190: used to securely expose services and capabilities provided by 3GPP network functions to the outside world.

[0095] Network repository function (NRF) NE 1100: used to store descriptions of network function NEs and the services they provide, and to support service discovery, NE discovery, etc.

[0096] Policy control function (PCF) network element 1110: a unified policy framework used to guide network behavior, providing policy rule information, etc. to control plane function network elements (such as AMF network element 160, SMF network element 150, etc.).

[0097] Unified data management (UDM) network element 1120: used to process user identification, access authentication, registration, or mobility management, etc.

[0098] Application function (AF) network element 1130: used for data routing affected by applications, accessing network open function network elements, or interacting with the policy framework to perform policy control, etc.

[0099] The network architecture involved in Figure 1 may also include other network elements, such as NRF network element 1100 or devices, etc., which are not specifically limited in this application. Of course, in future communication systems, each functional network element can have the above names or other names, which are not limited in this application.

[0100] In this network architecture, the N1 interface is the reference point between the UE 110 and the AMF network element 160; the N2 interface is the reference point between the AN 120 and the AMF network element 160, which is used for sending non-access stratum (NAS) messages, etc.; the N3 interface is the reference point between the AN 120 and the UPF network element 130, which is used for transmitting user plane data, etc.; the N4 interface is the reference point between the SMF network element 150 and the UPF network element 130, which is used to transmit information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages; the N6 interface is the reference point between the UPF network element 130 and the DN 140, which is used for transmitting user plane data, etc.

[0101] In order to ensure the quality of service (QoS) of services in 5G networks, a 5G QoS architecture based on QoS flow is proposed.

[0102] The following introduces the architecture of the 5G QoS provided by this application in conjunction with Figure 2.

[0103] QoS is a mechanism to ensure the quality of service transmission. Its purpose is to provide end-to-end service quality assurance for various services based on their different needs. In a protocol data unit (PDU) session, QoS flow is the smallest granularity for distinguishing QoS. In the 5G system, a QoS flow identifier (QFI) is used to identify QoS flows, and the QFI must be unique within a PDU session. In other words, a PDU session can have multiple (up to 64) QoS flows, but the QFI of each QoS flow is different. In a PDU session, user-plane service flows with the same QFI use the same service forwarding processing method (such as scheduling).

[0104] In terms of configuration granularity, a PDU session can correspond to multiple data radio bearers (DRBs), and a DRB can contain multiple QoS flows.

[0105] For each PDU session, there is still a single NG-U channel between 5GC and AN, and DRB is used between AN and UE. AN controls which DRB to map the QoS flow to.

[0106] Figure 3 is a schematic diagram of 5G QoS flow mapping provided by an embodiment of the present application. 5GC and AN ensure quality of service by mapping data packets to appropriate QoS flows and DRBs.

[0107] The UPF implements the mapping of Internet Protocol (IP) flows to QoS flows, and the AN implements the mapping of QoS flows to DRBs. QoS mapping can include three parts: UPF mapping, AN mapping, and UE mapping:

[0108] UPF Mapping: After receiving downlink data, the UPF maps it to the corresponding QoS flow using packet detection rules (PDR) and QoS enforcement rules (QER). It then performs QoS control for the QoS flow and marks the data with a QFI. The data is then sent to the AN via the N3 interface corresponding to the QoS flow.

[0109] AN Mapping: After receiving downlink data, the AN determines the DRB corresponding to the QFI. It then performs QoS control corresponding to the QoS flow and sends the data to the UE via the DRB. Alternatively, after receiving uplink data, the AN determines the QoS flow corresponding to the QFI. It then performs QoS control corresponding to the QoS flow and sends the data to the UPF via the corresponding N3 interface.

[0110] UE mapping: When a UE wants to send uplink data, it is mapped to the corresponding QoS flow according to the QoS rules. The uplink data is then sent through the DRB corresponding to the QoS flow.

[0111] It should be understood that the SMF is responsible for controlling QoS flows. When establishing a PDU session, the SMF can configure the corresponding QoS parameters for the UPF, AN, and UE. QoS flows can be established and modified through PDU sessions or defined through pre-configuration. The corresponding parameters for configuring a QoS flow include three parts:

[0112] 1. QoS profile: The SMF can provide the QoS profile to the AN via the N2 interface, or it can be pre-configured in the AN.

[0113] It should be understood that the QoS configuration of a QoS flow can also be called a QoS profile. The specific parameters of the QoS configuration are shown in Table 1.

[0114] Table 1 Specific parameters for QoS configuration

[0115] Specific description of QoS flow parameters

[0116] 5G QoS identifier

[0117] (5G QoS identity, 5QI) indicates the wireless characteristics of the QoS flow.

[0118] Each QoS flow has 5QI.

[0119] Assigning and retaining priorities

[0120] (allocation and retention priority, ARP) indicates the priority of the QoS flow on the NG interface.

[0121] Each QoS flow has ARP.

[0122] Applicable between different UEs or between QoS flows of a UE.

[0123] Guaranteed streaming bitrate

[0124] (Guaranteed flow bit rate, GFBR) indicates the guaranteed data rate.

[0125] Only Guaranteed Bit Rate (GBR) QoS is provided. Flows have GFBR, including both upstream and downstream transmissions.

[0126] Maximum streaming bitrate

[0127] (maximum flow bit rate, MFBR) indicates the maximum data rate.

[0128] Only GBR QoS flows have MFBR, including both uplink and downlink transmission.

[0129] Notification control indicates whether the gNB reports to the 5GC when QoS cannot be met.

[0130] Only GBR QoS flows have notification control.

[0131] Maximum packet loss rate

[0132] Maximum packet loss rate (MPLR) indicates the maximum packet loss rate that a QoS flow can tolerate.

[0133] Only GBR QoS flows may be provided with MPLR.

[0134] Reflective QoS attributes

[0135] (Reflective qos attribute, RQA) Whether the uplink transmission obeys the mirror mapping.

[0136] Only non-guaranteed bit rate (non-GBR) QoS flows have RQA.

[0137] 5QI is a scalar that indexes a 5G QoS feature. 5QI can be standardized, pre-configured, or dynamically defined. The attributes of 5QI are shown in Table 2 below.

[0138] Table 2 Attribute parameters of 5QI

[0139] 5QI attribute description

[0140] Resource type: GBR, Delay Critical GBR, or Non-GBR.

[0141] Priority Radio interface scheduling priority.

[0142] Applicable to between UEs or between QoS flows of UEs.

[0143] Packet delay budget GBR QoS flow: Under the premise of meeting GFBR, 98% of the data packets should not exceed the maximum delay threshold GBR; under the premise of meeting GBER, the data packets that exceed the data delay are considered lost.

[0144] GBR: Packet error rate of the QoS flow.

[0145] The averaging window is the time period over which the GFBR and MFBR of a GBR QoS flow are calculated.

[0146] The maximum data burst is the maximum amount of data that needs to be served within the air interface packet delay budget of the next generation-radio access network (NG-RAN).

[0147] 2. QoS rules: The SMF can provide QoS rules to the UE through the N1 interface. Alternatively, the UE can derive them through the QoS mechanism.

[0148] It should be understood that the UE performs classification and marking of uplink user plane data services, that is, mapping uplink data to corresponding QoS flows according to QoS rules. These QoS rules can be explicitly provided to the UE (that is, explicitly configured to the UE through signaling during the PDU session establishment / modification process); or, they can be pre-configured on the UE; or, they can be implicitly derived by the UE using the reflective QoS mechanism. QoS rules have the following characteristics:

[0149] A QoS rule includes: QFI associated with the QoS flow, packet filter set (a filter list), and priority.

[0150] A QoS flow can have multiple QoS rules.

[0151] Each PDU session must be configured with a default QoS rule, which is associated with a QoS flow.

[0152] 3. Uplink and downlink packet detection rule (PDR): The SMF network element provides PDR(s) to the UPF network element through the N4 interface.

[0153] Currently, there are two changing trends in network data transmission. First, due to the increasing sensitivity of many data types to latency, low-latency applications are becoming increasingly popular. Second, due to growing concerns about security and privacy, the proportion of encrypted data is increasing, reaching nearly 90%. Traditional Internet traffic transmission based on the Transmission Control Protocol (TCP) suffers from long connection establishment delays and head-of-line blocking, making it difficult to meet the low-latency requirements of current Internet applications.

[0154] Therefore, the Quick UDP Internet Connection (QUIC) protocol was developed. Using UDP as its protocol foundation, it aims to address the issues of high latency and head-of-line blocking associated with traditional TCP-based connections. The QUIC protocol has the following advantages:

[0155] Low connection latency: The traditional TCP protocol requires a round-trip time (RTT) when initially establishing a connection, followed by a second RTT for key exchange negotiation with transport layer security (TLS) protocols such as TLS 1.2. The QUIC protocol, based on the UDP transport protocol and TLS 1.3, performs key exchange negotiation during the initial connection. As a result, the QUIC protocol only requires one RTT for initial connection establishment and key exchange, and zero RTT for subsequent connections, reducing connection latency.

[0156] Multi-stream multiplexing without head-of-line blocking: The traditional TCP protocol is connection-oriented and needs to ensure that data packets can be sent to the receiving end in an orderly and accurate manner. However, if a TCP data packet is lost, the subsequent arriving TCP data packets need to wait for the retransmission of the lost data packet, resulting in head-of-line blocking of the data packets at the receiving end until the lost data packet is restored. The QUIC protocol is based on the UDP protocol and does not need to guarantee the timing of the data packets. There is no waiting for recovery when the data packet is lost, and thus there is no head-of-line blocking problem for the data packets. In the QUIC protocol, there is no dependency between multiple data packets, and it has the characteristics of multi-stream multiplexing, that is, there can be multiple business streams (streams) on a QUIC connection, and there is no dependency between the multiple business streams.

[0157] Header protection and encryption: As shown in Figure 4, the QUIC protocol follows the principle of payload encryption and header encryption as much as possible to avoid problems such as data parsing and interception by network middleware, thereby enhancing the security of data processing.

[0158] Connection Migration Invisibility: The QUIC protocol is based on connectionless UDP and QUIC connections represented by connection IDs, which supports connection migration without application awareness. For example, when an application client switches from a cellular network to a Wi-Fi network, the application connection quintuple changes, but the application connection ID remains unchanged. Therefore, the application client can maintain the connection state on the new quintuple, achieving connection migration awareness.

[0159] In the 5G QoS architecture, the UPF network element or UE is required to detect data packets and map QoS flows based on packet filters. For example, a packet filter is an IP five-tuple, which includes the source / destination IP address, source / destination port number, and transport layer protocol type. For data packets of the same service flow (corresponding to the same five-tuple), QoS flow mapping is performed in the 5G network. The same service flow corresponds to the QoS flow of the same QFI and has the same QoS control and processing.

[0160] For QUIC transmission data, due to the existence of multi-stream multiplexing, the data packet of the same IP five-tuple contains multiple different business flows. Generally, different business flows have different transmission requirements for the 5G network. This makes the current packet filtering and QoS flow mapping based on the above-mentioned IP five-tuple unable to provide differentiated QoS control and processing for QUIC data transmission.

[0161] In addition, the currently emerging extended reality (XR) services such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and cloud gaming have strict requirements on end-to-end latency, and the corresponding data processing of upper-layer media services during encoding and transmission is no longer based on the granularity of data packets. For example, when encoding at the media layer, media frames, fragments, etc. can be encoded independently; at the same time, the receiving side will also perform decoding and display processing at the same granularity of media frames, fragments, etc. Basic data units such as media frames and fragments often contain multiple IP data packets (due to the limitation of IP data packet size). This basic data unit of the media service layer is called a protocol data unit set (PDU Set), which is the basic unit that the upper service layer can process independently. Once a PDU packet is lost or damaged, the entire PDU Set may be difficult to decode and display correctly.

[0162] Figure 5 shows an architecture diagram for QoS processing at the PDU Set granularity. The AF network element 510 provides the 5G network with the protocol format corresponding to the current XR service transmission. This protocol format includes the format indicating the transport layer protocol (such as RTP, SRTP, etc.), the transport layer extension header (such as RTP extension header, etc.), and the payload (such as H.264, H.265, etc.). The UPF network element 520 receives the protocol description of the XR service sent by the AF network element 510 through the NEF network element 530, PCF network element 540, and SMF network element 550 network elements, and then identifies the PDU set. The identified PDU set information includes information such as the PDU set sequence number, the end of the PDU data packet within the PDU set, the sequence number of the PDU data packet within the PDU set, the size of the PDU set data packet, and the importance of the PDU set. The PDU set information is transmitted to the RAN 560 via the GTP-U (user plane part of GPRS tunneling protocol) header. The SMF network element 550 can send the QoS parameters corresponding to the PDU set to the RAN 560 through the AMF network element 570. The RAN 560 can perform QoS processing at the PDU set granularity, such as integrity transmission of the PDU set (if a data packet in the PDU set is discarded, the entire PDU set can be discarded, thereby reducing the waste of transmission resources at the air interface), differentiated transmission of the PDU set (different QoS processing is selected based on the importance difference between the PDU sets. For example, PDU set data packets with high importance are scheduled first at the air interface, and PDU set data packets with low importance are scheduled with low priority at the air interface; or when the base station air interface network is congested, PDU set data packets with low importance can be selectively discarded, thereby reducing network congestion), etc.

[0163] There is an assumption in the UPF's identification and marking of PDU sets through the transport protocol format, that is, the transport protocol (such as the transport layer protocol or payload) required for the XR service is not encrypted. Therefore, the UPF network element can identify the PDU set through the transport protocol format. However, the QUIC service flow has data encryption properties, that is, there are features such as header protection and payload encryption. Therefore, the QoS control method based on the XR service transmission protocol format makes it difficult for the 5G network UPF network element to identify the characteristics of data packets with encryption attributes (such as the difference in importance of different data packets), and therefore, it cannot be applied to QUIC data transmission.

[0164] In summary, due to the data encryption and multi-stream multiplexing of QUIC data packets, it is difficult for 5G networks to determine the characteristics of data packets, such as the importance of data packets, and thus it is impossible to provide differentiated QoS control and processing for QUIC data packets.

[0165] To address the above issues, the embodiments of the present application provide a data processing method and device that can perform differentiated QoS control and processing on QUIC data packets, thereby rationally utilizing and scheduling network resources and improving the application experience.

[0166] The service enabler architecture layer data delivery (SEALDD) enhancement layer can be used to carry the processing and transmission of QUIC data packets. The architecture of the SEALDD enhancement layer is introduced below in conjunction with Figure 6.

[0167] The SEALDD enhancement layer (or data processing enhancement layer) includes the SEALDD client and the SEALDD server. The SEALDD client is deployed on the UE as software or a system component, while the SEALDD server is deployed as a standalone or integrated server between the UPF network element and the application server (AS) or vertical application layer server (VAL server).

[0168] Regarding the SEALDD interface, the SEALDD client communicates with the VAL client through the SEALDD-C interface, and the SEALDD server communicates with the VAL server through the SEALDD-S interface. The SEALDD client and server process user plane data through the SEALDD-UU interface, which is carried over the user plane session established by the 3GPP network system. SEALDD servers interact with each other through the SEALDD-E interface, providing control plane context transfer and user plane data forwarding.

[0169] AF network elements, such as SEALDD servers, can exchange control plane messages with PCF network elements in the 3GPP network system via the N33 / N5 interface. N33 represents the interface between AF and NEF network elements, while N5 represents the interface between AF and PCF network elements. AF network elements can communicate indirectly with PCF network elements via NEF network elements. SEALDD servers can send AF network element requests or subscriptions to PCF network elements via the N33 / N5 interface. SealDD servers can also process user plane data with UPF network elements via the N6 interface.

[0170] As a data processing enhancement layer, the SEALDD enhancement layer provides communication connections and data processing functions (such as the transmission of applications, media data, and signaling data) for VAL applications. The data processing of the SEALDD enhancement layer is shown in Figure 7.

[0171] For uplink data processing, the VAL client transmits the data packet to the SEALDD client via the SEALDD-C interface. The SEALDD client encapsulates the data packet and sends it to the SEALDD server via the SEALDD-UU interface. The SEALDD server parses / decapsulates the data packet and sends it to the VAL server via the SEALDD-S interface. Downlink data processing is similar to uplink data processing. The VAL server transmits the data packet to the SEALDD server via the SEALDD-S interface. The SEALDD server encapsulates the data packet and sends it to the SEALDD client via the SEALDD-UU interface. The SEALDD client parses / decapsulates the data packet and sends it to the VAL client via the SEALDD-C interface.

[0172] Figure 8 is a schematic diagram of the QUIC data processing method provided in an embodiment of the present application.

[0173] S801: The transmission server obtains transmission requirement information of multiple data.

[0174] One of the multiple data is a service flow or a data packet set, and the data packet set includes at least one data packet.

[0175] That is, the multiple data may include multiple service flows, or may include multiple data packet sets, or may include multiple service flows and at least one data packet in at least one other service flow.

[0176] Exemplarily, the multiple data may include multiple business flows, such as a first business flow and a second business flow.

[0177] Exemplarily, the multiple data may include multiple data packet sets in a service flow, such as a first data packet set and a second data packet set.

[0178] In some embodiments, the data may include uplink data or downlink data.

[0179] For example, the first service flow and the second service flow may both be uplink service flows, or may both be downlink service flows.

[0180] For another example, the multiple data packet sets in the above-mentioned one business flow may be multiple data packet sets in an uplink business flow or multiple data packet sets in a downlink business flow.

[0181] In some embodiments, the transmission server may receive information about multiple data sent by the application server, where the information about the multiple data includes transmission requirement information about the multiple data.

[0182] For example, for a set of data packets in the same service flow, the transmission server may receive information of multiple data sent by the application server, such as protocol description information. The protocol description information may include transmission requirement information of the multiple data, such as importance information of the multiple data.

[0183] For example, the protocol description information can be an RTP extension header, and the extension header can mark data packets with higher importance. For the PDU set importance (PSI) in the RTP extension header, a value of 0-15 can be used to represent the importance of the data packet set. The smaller the value, the higher the importance of the data packet. The data packet set corresponding to a PSI of 0 has the highest importance. In this way, based on the RTP extension header, the transmission server can obtain the transmission requirement information of multiple data packets. For example, data packets with the same PSI value can be determined as data packets with the same transmission requirement information, or data packets with PSI values ​​within a certain range (such as 0-3) can be determined as data packets with the same transmission requirement.

[0184] In some embodiments, the transmission server can receive information about multiple data sent by the application server. The information about the multiple data may include description information of the multiple data and / or transmission requirement information corresponding to the description information. The transmission server can then determine the transmission requirement information of the multiple data based on the information about the multiple data.

[0185] In some embodiments, the description information of the plurality of data includes descriptor information of the plurality of data and / or protocol description information of the plurality of data.

[0186] Exemplarily, for multiple business flows, the transmission server can receive description information of multiple data sent by the application server, such as descriptor information and transmission requirement information corresponding to the description information, and then determine the transmission requirement information of the multiple data based on the description information of the multiple data and the transmission requirement information corresponding to the description information.

[0187] For example, the descriptor information for service flow #1 is IP quintuple #1, which corresponds to transmission requirement #1; the descriptor information for service flow #2 is IP quintuple #2, which corresponds to transmission requirement #2; and the descriptor information for service flow #3 is IP quintuple #3, which corresponds to transmission requirement #1. Therefore, it can be determined that service flows #1 and 3 both correspond to transmission requirement #1, and service flow #2 corresponds to transmission requirement #2.

[0188] For different service flows, transmission requirements may include QoS requirement information, such as latency information or packet loss rate information. For example, service flows with the same QoS requirement information value have the same QoS requirement information; or service flows with QoS requirement information values ​​within a certain range have the same QoS requirement information.

[0189] For example, for multiple data packet sets of the same service flow, the transmission server may receive description information of the multiple data packet sets, such as the flow protocol description information, and transmission requirement information corresponding to the description information, such as characteristic parameter information of the data packet sets corresponding to the flow protocol description information, from the application server. The transmission server may then determine the transmission requirement information for the multiple data packet sets based on the description information of the multiple data packets, such as the flow protocol description information, and the transmission requirement information corresponding to the description information, such as the characteristic parameter information of the data packet sets.

[0190] S802, the transmission server determines the QUIC encapsulation identifier of the multiple data according to the transmission requirement information of the multiple data.

[0191] There is a corresponding relationship between the transmission requirement information of multiple data and the QUIC encapsulation identifiers of multiple data.

[0192] In some embodiments, multiple data include a first business stream and a second business stream. When the transmission requirement information of the first business stream and the second business stream is the same, the QUIC encapsulation identifier of the first business stream and the second business stream is determined to be the first encapsulation identifier; or, when the transmission requirement information of the first business stream and the second business stream is different, the QUIC encapsulation identifiers of the first business stream and the second business stream are determined to be the second encapsulation identifier and the third encapsulation identifier, respectively.

[0193] Service flows with the same transmission requirement information have the same QUIC encapsulation identifier; service flows with different transmission requirement information have different QUIC encapsulation identifiers. For example, service flow #1 corresponds to transmission requirement information #1; service flow #2 corresponds to transmission requirement information #2; and service flow #3 corresponds to transmission requirement information #1. The QUIC encapsulation identifiers for service flows #1 and #3 can be Encapsulation Identifier #1, and the QUIC encapsulation identifier for service flow #2 can be Encapsulation Identifier #2.

[0194] In some embodiments, the multiple data include a first packet set and a second packet set in the same service flow. If the transmission requirement information of the first packet set and the second packet set is the same, the QUIC encapsulation identifiers of the first packet set and the second packet set are determined to be the first encapsulation identifier; or, if the transmission requirement information of the first packet set and the second packet set is different, the QUIC encapsulation identifiers of the first packet set and the second packet set are determined to be the second encapsulation identifier and the third encapsulation identifier, respectively.

[0195] Packet sets with the same transmission requirement information within the same service flow have the same QUIC encapsulation identifier. Packet sets with different transmission requirement information within the same service flow have different QUIC encapsulation identifiers. For example, Packet Set #1 corresponds to Transmission Requirement Information #1; Packet Set #2 corresponds to Transmission Requirement Information #1; and Packet Set #3 corresponds to Transmission Requirement Information #2. The QUIC encapsulation identifiers for Packet Set #1 and Packet Set #2 can be Encapsulation Identifier #1, and the QUIC encapsulation identifier for Packet Set #3 can be Encapsulation Identifier #2.

[0196] In some embodiments, the QUIC encapsulation identifier may include: information used to represent the QUIC connection, information in the QUIC tunnel header, information in the IP triplet, or information in the IP quintuple.

[0197] That is, the information used to represent the QUIC connection can be used as the QUIC encapsulation identifier, or the information in the QUIC tunnel header can be used as the QUIC encapsulation identifier, or the information in the IP triplet can be used as the QUIC encapsulation identifier, or the information in the IP quintuple can be used as the QUIC encapsulation identifier.

[0198] The information used to represent the QUIC connection includes at least one of the following: the allocatable QUIC connection identifier of the transmission server, other identifiers used to represent the QUIC connection other than the allocatable QUIC connection identifier of the transmission server, the allocatable QUIC connection identifier of the transmission client, or other identifiers used to represent the QUIC connection other than the allocatable QUIC connection identifier of the transmission server.

[0199] An IP triplet may include information of an IP address, protocol, and port.

[0200] The IP quintuple may include source IP address, source port, destination IP address, destination port, and transport layer protocol information.

[0201] Exemplarily, the QUIC encapsulation identifier includes information that can be assigned by a transport server and / or a transport client to represent a QUIC connection.

[0202] That is, the information that can be assigned by the transport server and / or the transport client to represent the QUIC connection can be used as the QUIC encapsulation identifier.

[0203] In some embodiments, the transmission server determines the QUIC encapsulation identifier of the multiple data based on the transmission requirement information of the multiple data, and the first connection information and / or the second connection information.

[0204] The first connection information is information that can be assigned by the transmission server to represent the QUIC connection, and the first connection information includes a QUIC connection identifier that can be assigned by the transmission server and / or other information used to represent the QUIC connection. The second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes a QUIC connection identifier that can be assigned by the transmission client and / or other information used to represent the QUIC connection.

[0205] Exemplarily, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data and the first connection information.

[0206] Exemplarily, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data and the second connection information.

[0207] Exemplarily, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data, the first connection information and the second connection information.

[0208] For example, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of multiple data, the QUIC connection identifier that can be assigned by the transmission server, and the QUIC connection identifier that can be assigned by the transmission client.

[0209] Take the QUIC encapsulation identifier of the following data as an example. For example, for different QUIC connections, the QUIC connection identifiers that the transmission server can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#1> 、<connection ID#2> 、<connection ID#1,connection ID#3> 、<connection ID#1,connection ID#4> 、<connection ID#2,connection ID#3> 、<connection ID#2,connection ID#4> The first two QUIC encapsulation identifiers are composed of the source connection identifier (corresponding to downlink data, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission server); the next four QUIC encapsulation identifiers are composed of the source connection identifier and the destination connection identifier (for downlink data, the destination connection is the QUIC connection identifier that can be assigned by the transmission client).

[0210] If multiple downlink service flows correspond to multiple different transmission requirement information, such as downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 can be<connection ID#1> , the QUIC encapsulation identifier corresponding to downlink service flow #2 can be<connection ID#2> .

[0211] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 can be<connection ID#1,connection ID#3> , the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be<connection ID#1,connection ID#4> .

[0212] Taking the QUIC encapsulation identifier of the uplink data as an example, for different QUIC connections, the QUIC connection identifiers that the transmission client can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#3> 、<connection ID#4> 、<connection ID#3,connection ID#1> 、<connection ID#4,connection ID#1> 、<connection ID#3,connection ID#2> 、<connection ID#4,connection ID#4> . The first two encapsulation identifiers are composed of the source connection identifier (corresponding to uplink data, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission client); the next four identifiers are composed of the source connection identifier and the destination connection identifier (for uplink data, the destination connection is the QUIC connection identifier that can be assigned by the transmission server).

[0213] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and downlink service flow #3 can be<connection ID#3> , the QUIC encapsulation identifier corresponding to the upstream service flow #2 can be<connection ID#4> .

[0214] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 can be<connection ID#3,connection ID#1> , the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be<connection ID#4,connection ID#1> .

[0215] Within the same QUIC connection, there is only one identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client. Therefore, it is necessary to introduce a new identifier, such as other information used to represent the QUIC connection, in combination with the identifier, to be used as the QUIC encapsulation identifier for multiple data with different transmission requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifiers of multiple data can be determined based on the transmission requirement information of the multiple data, the QUIC connection identifier that can be assigned by the transmission server and other information representing the QUIC connection, and the QUIC connection identifier that can be assigned by the transmission client and other information representing the QUIC connection.

[0216] Taking the QUIC encapsulation identifier of the following data as an example, for example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and the transmission client is the connection ID, the other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and the other identifiers that can be assigned by the transmission client are ID#3 and ID#4, then the encapsulation identifier can be<connection ID+ID#1> 、<connection ID+ID#2> 、 <connection ID+<ID#1,ID#3> >、 <connection ID+<ID#1,ID#4> >、 <connection ID+<ID#2,ID#3> >、 <connection ID+<ID#2,ID#4> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (for downlink data, other source connection identifiers are other information that can be assigned by the transmission server to represent the QUIC connection); the last four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for downlink data, other destination connection identifiers are other information that can be assigned by the transmission client to represent the QUIC connection).

[0217] If multiple downlink service flows correspond to multiple different transmission requirement information, for example, downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 can be<connection ID+ID#1> , the QUIC encapsulation identifier corresponding to downlink service flow #2 can be<connection ID+ID#2> .

[0218] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 can be <connection ID+<ID#1,ID#3> >, the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be <connection ID+<ID#1,ID#4> >.

[0219] Taking the QUIC encapsulation identifier of the above data as an example, for example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client is the connection ID. Other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and other identifiers that can be assigned by the transmission client are ID#3 and ID#4. Then the encapsulation identifier can be<connection ID+ID#3> 、<connection ID+ID#4> 、 <connection ID+<ID#3,ID#1> >、 <connection ID+<ID#4,ID#1> >、 <connection ID+<ID#3,ID#2> >、 <connection ID+<ID#4,ID#2> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (for uplink data, other source connection identifiers are other information assigned by the transmission client to represent the QUIC connection); the last four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for uplink data, other destination connection identifiers are other information assignable by the transmission server to represent the QUIC connection).

[0220] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and uplink service flow #3 can be<connection ID+ID#3> , the QUIC encapsulation identifier corresponding to the upstream service flow #2 can be<connection ID#4> .

[0221] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 can be <connection ID+<ID#3,ID#1> >, the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be <connection ID+<ID#4,ID#1> >.

[0222] In some embodiments, the QUIC encapsulation identifiers of the multiple data can be determined based on the transmission requirement information of the multiple data, and the first IP information and / or the second IP information. The first IP information includes the IP address and port number that can be assigned by the transmission server, and the second IP information includes the IP address and port number that can be assigned by the transmission client.

[0223] That is, the IP address and port number assignable by the transmission server and / or the IP address and port number assignable by the transmission client may be used as the encapsulation identifier.

[0224] For example, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data and the first IP information.

[0225] For example, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data and the second IP information.

[0226] For example, the QUIC encapsulation identifier of multiple data can be determined based on the transmission requirement information of the multiple data, the first IP information and the second IP information.

[0227] Taking the QUIC encapsulation identifier of the following data as an example, the IP address and port number that the transmission server can assign are<IP#1,port#1> 、<IP#1,port#2> , the IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#1,port#1], [IP#1,port#2], [<IP#1,port#1> ,<IP#2,port#3> ]、[<IP#1,port#1> ,<IP#2,port#4> ]、[<IP#1,port#2> ,<IP#2,port#3> ]、[<IP#1,port#2> ,<IP#2,port#4> ]. The first two identifiers consist of the source address and source port number (for downlink data, the source address and source port number are the IP address and port number that can be assigned by the transmission server); the next four identifiers consist of the source address and source port number, and the destination address and destination port number (for downlink data, the destination address and destination port number are the address and port number that can be assigned by the transmission client).

[0228] If multiple downlink service flows correspond to multiple different transmission requirement information, for example, downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above-mentioned QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 can be [IP#1, port#1], and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be [IP#1, port#2].

[0229] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 may be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers may be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 may be [<IP#1,port#1> ,<IP#2,port#3> ], the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be [<IP#1,port#1> ,<IP#2,port#4> ].

[0230] Taking the QUIC encapsulation identifier of the uplink data as an example, the IP address and port number that the transmission server can assign are<IP#1,port#1> 、<IP#1,port#2> The IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#2,port#3], [IP#2,port#4], [<IP#2,port#3> ,<IP#1,port#1> ]、[<IP#2,port#4> ,<IP#1,port#1> ]、[<IP#2,port#3> ,<IP#1,port#2> ]、[<IP#2,port#4> ,<IP#1,port#2> ]. The first two identifiers consist of the source address and source port number (for uplink data, the source address and source port number are the IP address and port number that can be assigned by the transmission client); the next four identifiers consist of the source address and source port number, and the destination address and destination port number (for uplink data, the destination address and destination port number are the address and port number that can be assigned by the transmission server).

[0231] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above-mentioned QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and uplink service flow #3 can be [IP#2, port#3], and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be [IP#2, port#4].

[0232] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 may be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers may be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 may be [<IP#2,port#3> ,<IP#1,port#1> ], the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be [<IP#2,port#4> ,<IP#1,port#1> ].

[0233] In an embodiment of the present application, all QUIC encapsulation identifiers may be determined first, and then, based on data of different transmission requirements, a corresponding QUIC encapsulation identifier may be selected and determined from all QUIC encapsulation identifiers. Alternatively, the corresponding QUIC encapsulation identifier may be directly determined based on the data of different transmission requirements.

[0234] Exemplarily, the encapsulation identifier includes information in a QUIC tunnel header.

[0235] The encapsulation identifier can be encapsulated in the QUIC tunnel header (also known as the N6 tunnel header). For example, the QUIC tunnel header carries the transmission requirement information of the data, and the transmission requirement information of the data is directly used as the QUIC encapsulation identifier of the data.

[0236] If multiple downlink service flows correspond to multiple different transmission requirement information, for example, downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement information #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers for downlink service flows #1 and #3 may be transmission requirement information #1, and the QUIC tunnel header carries transmission requirement information #1; the QUIC encapsulation identifier for downlink service flow #2 may be transmission requirement information #2, and the QUIC tunnel header carries transmission requirement information #2.

[0237] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 may be transmission requirement information #1, and the QUIC tunnel header carries transmission requirement information #1; the QUIC encapsulation identifier corresponding to downlink data packet set #3 may be transmission requirement information #2, and the QUIC tunnel header carries transmission requirement information #2.

[0238] S803: The transmission server sends a QUIC encapsulation identifier of multiple data to the first network element.

[0239] Correspondingly, the first network element receives the QUIC encapsulation identifier of multiple data.

[0240] In some embodiments, the transmission server may further send transmission requirement information of multiple data to the first network element.

[0241] In some embodiments, the first network element determines the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data based on the QUIC encapsulation identifier of the multiple data.

[0242] The first network element may include a network element responsible for session management, such as an SMF network element.

[0243] Optionally, the first network element can also determine the identifier of the QoS flow of the multiple data based on the QUIC encapsulation identifier of the multiple data and the transmission requirement information of the multiple data.

[0244] For example, the identifier of the QoS flow may include a QoS class identifier (QCI), a QFI, and the like.

[0245] In some embodiments of the present application, the QUIC encapsulation identifiers of multiple data may include a first encapsulation identifier and a second encapsulation identifier, then the identifiers of the QoS flows of the data corresponding to the first encapsulation identifier and the second encapsulation identifier are respectively determined to be the first QoS flow identifier and the second QoS flow identifier; or, the QUIC encapsulation identifiers of multiple data only include the first encapsulation identifier, then the identifiers of the QoS flows of the data corresponding to the first encapsulation identifier are all determined to be the first QoS flow identifier.

[0246] For example, the QUIC encapsulation identifiers for service flow #1 and service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 can be encapsulation identifier #2. The QFIs for the QoS flows of service flow #1 and service flow #3 are both QFI #1, meaning that service flow #1 and downstream service flow #3 have the same QoS flow. The QFIs for the QoS flow of service flow #2 are both QFI #2, meaning that service flow #1 and service flow #3 are different QoS flows from the QoS flow of service flow #2.

[0247] For example, the QUIC encapsulation identifiers for packet set #1 and downlink packet set #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to packet set #2 can be encapsulation identifier #2. The QFIs for the QoS flows of packet set #1 and packet set #3 are both QFI #1, meaning that the QoS flows of packet set #1 and downlink packet set #3 are the same QoS flow; the QFIs for the QoS flow of packet set #2 are both QFI #2, meaning that packet set #1 and packet set #3 are different QoS flows from the QoS flow of packet set #2.

[0248] In some embodiments, the first network element may include a network element responsible for policy control, a network element responsible for network capability exposure, and the like.

[0249] For example, the first network element may be a PCF network element or an NEF network element. The PCF network element may generate a policy and charging control (PCC) rule based on the QUIC encapsulation identifier corresponding to the multiple data and the transmission requirement information of the multiple data.

[0250] In some embodiments, if the first network element is a network element responsible for policy control, such as a PCF network element, the transmission server can directly send the QUIC encapsulation identifiers of multiple data to it, or can also indirectly send the QUIC encapsulation identifiers of multiple data to it. For example, if the transmission server is an entity trusted by the operator network, it can interact directly with the PCF network element; if the transmission server is an entity not trusted by the operator network, it needs to first interact with the network element responsible for network capability exposure, such as the NEF network element, and then the network element responsible for network capability exposure interacts with the PCF network element.

[0251] Figure 9 is a schematic diagram of a method for QUIC data processing provided by an embodiment of the present application. In the method shown in Figure 9, the first network element may include a network element responsible for session management, such as an SMF network element, a network element responsible for policy control, such as a PCF network element, etc.

[0252] S901: The transmission server receives information about a plurality of data from the application server.

[0253] One of the multiple data is a service flow or a data packet set, and the data packet set includes at least one data packet.

[0254] That is, the multiple data may include multiple service flows, or may include multiple data packet sets, or may include multiple service flows and at least one data packet in at least one other service flow.

[0255] Exemplarily, the multiple data may include multiple business flows, such as a first business flow and a second business flow.

[0256] Exemplarily, the multiple data may include multiple data packet sets in a service flow, such as a first data packet set and a second data packet set.

[0257] In some embodiments, the data may include uplink data or downlink data.

[0258] For example, the first service flow and the second service flow may both be uplink service flows, or may both be downlink service flows.

[0259] For another example, the multiple data packet sets in the above-mentioned one business flow may be multiple data packet sets in an uplink business flow or multiple data packet sets in a downlink business flow.

[0260] In some embodiments, the information of the plurality of data may include transmission requirement information of the plurality of data.

[0261] Exemplarily, the information of the multiple data may be protocol description information, and the protocol description information may include transmission requirement information of the multiple data, such as importance information of the multiple data.

[0262] For example, the protocol description information can be an RTP extension header, which can mark packets of higher importance. The PDU set importance (PSI) in the RTP extension header can use a value from 0 to 15 to represent the importance of a packet set. A smaller value indicates a higher importance, and a PSI of 0 indicates the highest importance packet set. Thus, based on this RTP extension header, a transmission server can obtain transmission requirement information for multiple packets.

[0263] In this way, based on the RTP extension header, the transmission server can obtain the transmission requirement information of multiple data packets. For example, data packets with the same PSI value can be determined as data packets with the same transmission requirement information, or data packets with PSI values ​​within a certain range (such as 0-3) can be determined as data packets with the same transmission requirement information.

[0264] In some embodiments, the information of the multiple data may include description information of the multiple data and / or transmission requirement information corresponding to the description information.

[0265] Exemplarily, the information of the multiple data may include descriptive information of the multiple data, such as descriptor information, and transmission requirement information corresponding to the descriptive information, such as QoS requirement information. For example, the descriptor information of service flow #1 is IP quintuple #1, and IP quintuple #1 corresponds to transmission requirement #1; the descriptor information of service flow #2 is IP quintuple #2, and IP quintuple #2 corresponds to transmission requirement #2; and the descriptor information of service flow #3 is IP quintuple #3, and IP quintuple #1 corresponds to transmission requirement #1.

[0266] For different service flows, transmission requirement information may include QoS requirement information, such as latency information or packet loss rate information. For example, service flows with the same QoS requirement information value have the same QoS requirement information; or service flows with QoS requirement information values ​​within a certain range have the same QoS requirement information.

[0267] Exemplarily, the information of the plurality of data may include description information of the plurality of data, such as stream protocol and characteristic parameter information of a set of data packets corresponding to the description information.

[0268] S902: The transmission server determines transmission requirement information of the plurality of data according to information of the plurality of data.

[0269] In the case where the information of the multiple data includes transmission requirement information of the multiple data, S902 may be omitted.

[0270] In some embodiments, the transmission server can receive description information of multiple data and / or transmission requirement information corresponding to the description information sent by the application server, and then determine the transmission requirement information of multiple data based on the description information of the multiple data and / or the transmission requirement information corresponding to the description information.

[0271] For example, for multiple service flows, transmission requirement information for multiple data can be determined based on the descriptive information of the multiple service flows, such as the descriptor information and the transmission requirement information corresponding to the descriptive information. For example, the descriptor information for service flow #1 is IP quintuple #1, and IP quintuple #1 corresponds to transmission requirement #1; the descriptor information for service flow #2 is IP quintuple #2, and IP quintuple #2 corresponds to transmission requirement #2; and the descriptor information for service flow #3 is IP quintuple #3, and IP quintuple #1 corresponds to transmission requirement #1. Therefore, it can be determined that service flow #1 and service flow 3 both correspond to transmission requirement #1, and service flow #2 corresponds to transmission requirement #2.

[0272] For example, for multiple data packet sets of the same service flow, the transmission server may receive description information of the multiple data packet sets, such as the flow protocol description information, and transmission requirement information corresponding to the description information, such as characteristic parameter information of the data packet sets corresponding to the flow protocol description information, from the application server. The transmission server may then determine the transmission requirement information for the multiple data packet sets based on the description information of the multiple data packets, such as the flow protocol description information, and the transmission requirement information corresponding to the description information, such as the characteristic parameter information of the data packet sets.

[0273] S903a, the transmission server determines the QUIC encapsulation identifier of the multiple data based on the transmission requirement information of the multiple data, and the first connection information and / or the second connection information.

[0274] In some embodiments, the transport server determines the first connection information.

[0275] The first connection information is information that can be assigned by the transmission server to represent the QUIC connection. The first connection information includes a QUIC connection identifier that can be assigned by the transmission server and / or other information used to represent the QUIC connection.

[0276] In some embodiments, the transmission server receives the second connection information sent by the transmission client.

[0277] The second connection information is information that can be assigned by the transmission client to represent the QUIC connection. The second connection information includes a QUIC connection identifier that can be assigned by the transmission client and / or other identifiers used to represent the QUIC connection.

[0278] In some embodiments, the transport server may receive a QUIC connection or handshake request message sent by the transport client, and the request message may include second connection information.

[0279] The first connection information, the second connection information, and the QUIC encapsulation identifier for determining multiple data in S903a can be referred to the relevant description in S802, and this application will not go into details here.

[0280] 903b, determine the QUIC encapsulation identifier of the multiple data based on the transmission requirement information of the multiple data, and the first IP information and / or the second IP information.

[0281] In some embodiments, the transport server may receive a QUIC connection or handshake request message sent by the transport client, and the request message may include the second IP information.

[0282] In some embodiments, the transport server determines the first IP information.

[0283] The first IP information includes an IP address and a port number assignable by the transmission server.

[0284] In some embodiments, the transmission server receives the second IP information sent from the transmission client.

[0285] The second IP information includes the IP address and port number that can be assigned by the transmission client

[0286] The first IP information, the second IP information and the content of the QUIC encapsulation identifier for determining multiple data in S903b can refer to the relevant description in S802, and this application will not go into details here.

[0287] It should be understood that S903a and S903b are two different ways of determining the package identifier, and generally one of them is selected to perform the QUIC data processing provided in the embodiments of this application. That is, S901 to S902, S903a, and S904 to S913 are executed, or S901 to S902, S903b, and S904 to S913 are executed.

[0288] S904, the transmission server sends the QUIC encapsulation identifier of multiple data and transmission requirement information to the PCF network element.

[0289] Accordingly, the PCF network element receives the QUIC encapsulation identifier of multiple data.

[0290] The QUIC encapsulation identifier of multiple data is used to determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of multiple data.

[0291] For example, the identifier of the QoS flow may include QCI, QFI, etc.

[0292] If the multiple data are multiple downlink service flows, the transmission server can send the QUIC encapsulation identifiers and transmission requirement information of the multiple downlink service flows to the PCF network element. If the multiple data are multiple downlink data packet sets in the same downlink service flow, the transmission server can send the QUIC encapsulation identifiers and transmission requirement information of the multiple downlink data packet sets to the PCF network element.

[0293] If the multiple data are multiple uplink service flows, the transmission server can send the QUIC encapsulation identifiers and transmission requirement information of the multiple uplink service flows to the PCF network element. If the multiple data are multiple uplink data packet sets in the same uplink service flow, the transmission server can send the QUIC encapsulation identifiers and transmission requirement information of the multiple uplink data packet sets to the PCF network element.

[0294] The transmission server can directly send the QUIC encapsulation identifiers of multiple data to the PCF network element, or it can also indirectly send the QUIC encapsulation identifiers of multiple data to the PCF network element, such as through the NEF network element. For example, if the transmission server is trustworthy for the 5G network, the transmission server can directly send the QUIC encapsulation identifier corresponding to the service flow and the corresponding transmission requirement information to the PCF network element. If the transmission server is not trustworthy for the 5G network, it is necessary to send the QUIC encapsulation identifier corresponding to the service flow and the corresponding transmission requirement information to the PCF network element through the NEF network element.

[0295] S905, the PCF network element determines the PCC rules based on the QUIC encapsulation identifiers and transmission requirement information of the multiple data.

[0296] For example, if multiple data are uplink data, including uplink service flow #1, uplink service flow #2, and uplink service flow #3, the PCF network element can obtain: uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1; uplink service flow #1 and uplink service flow #3 correspond to encapsulation identifier #1, and uplink service flow #2 corresponds to encapsulation identifier #2. The PCF network element can generate PCC rules based on this information.

[0297] For another example, if multiple data sets are downlink data, including downlink data packet set #1, downlink data packet set #2, and downlink data packet set #3 for the same downlink service flow, the PCF network element can obtain: downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement #2, and downlink data packet set #3 corresponds to transmission requirement information #1; downlink data packet set #1 and downlink data packet set #3 correspond to encapsulation identifier #1, and downlink data packet set #2 corresponds to encapsulation identifier #2. The PCF network element can generate PCC rules based on this information.

[0298] S906, the PCF network element sends the QUIC encapsulation identifier of multiple data and transmission requirement information to the SMF network element.

[0299] For example, the PCF network element sends a PCC rule to the SMF network element. The PCC rule includes a QUIC encapsulation identifier of multiple data and transmission requirement information of multiple data.

[0300] S907, the SMF network element determines the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data based on the QUIC encapsulation identifier of the multiple data.

[0301] In some embodiments, if the QUIC encapsulation identifiers of multiple data include a first encapsulation identifier and a second encapsulation identifier, then the identifiers of the QoS flows of the data corresponding to the first encapsulation identifier and the second encapsulation identifier are determined to be the first QoS flow identifier and the second QoS flow identifier, respectively; or, if the QUIC encapsulation identifiers of multiple data only include the first encapsulation identifier, then the identifiers of the QoS flows of the data corresponding to the first encapsulation identifier are determined to be the first QoS flow identifier, respectively.

[0302] For example, the QUIC encapsulation identifiers for upstream service flow #1 and upstream service flow #3 are Encapsulation Identifier #1, and the QUIC encapsulation identifier for upstream service flow #2 is Encapsulation Identifier #2. The QFIs for the QoS flows of upstream service flow #1 and upstream service flow #3 are both QFI#1, meaning that the QoS flows of upstream service flow #1 and upstream service flow #3 are the same QoS flow. The QFI for the QoS flow of upstream service flow #2 is QFI#2, meaning that upstream service flow #1 and upstream service flow #3 are different QoS flows from the QoS flow of upstream service flow #2.

[0303] For example, the QUIC encapsulation identifiers of downlink packet set #1 and downlink packet set #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of downlink packet set #2 is encapsulation identifier #2. The QFIs of the QoS flows of downlink packet set #1 and downlink packet set #3 are both QFI#1, meaning that the QoS flows of downlink packet set #1 and downlink packet set #3 are the same QoS flow. The QFI of the QoS flow of downlink packet set #2 is QFI#2, meaning that downlink packet set #1 and downlink packet set #3 are different QoS flows from the QoS flow of downlink packet set #2.

[0304] In some embodiments, the SMF network element may generate a PDR rule based on the QUIC encapsulation identifier and transmission requirement information of multiple data. The PDR rule includes the QUIC encapsulation identifier and transmission requirement information of multiple data.

[0305] S908, the SMF network element sends the QoS flow identifier corresponding to the QUIC encapsulation identifier of multiple data to the second network element.

[0306] The multiple data are downlink data.

[0307] In some embodiments, the second network element includes a network element responsible for user plane functions, such as a UPF network element.

[0308] In some embodiments, the SMF network element may also send a QUIC encapsulation identifier of multiple data to the second network element. For example, the SMF network element sends the PDR rules of multiple data and the identifier of the corresponding QoS flow to the UPF network element.

[0309] S911: The transmission server receives multiple data sent by the application server.

[0310] Among them, a plurality of data are downlink data.

[0311] In some embodiments, the plurality of data includes a plurality of downlink service flows. For example, the transmission server may receive a plurality of downlink service flows from the application server.

[0312] In some embodiments, the multiple data packets are multiple sets of downlink data packets in the same downlink service flow, each set of data packets including at least one data packet. The transmission server may receive multiple data packets from the application server. For example, the transmission server may receive multiple sets of downlink data packets in the same downlink service flow from the application server.

[0313] S912. The transmission server encapsulates the multiple downlink data using the QUIC encapsulation identifiers of the multiple downlink data to obtain the encapsulated multiple downlink data.

[0314] When the transmission server receives the downlink data, it encapsulates the downlink data according to the QUIC encapsulation identifier corresponding to the downlink data, that is, the QUIC encapsulation identifier determined in S903a or S903b.

[0315] For example, the QUIC encapsulation identifier corresponding to downlink service flow #2 (IP quintuple #2) can be<connection ID#2> The transport server encapsulates the downlink service flow #2 from the application server, and the encapsulated data carries the QUIC connection identifier<connection ID#2> .

[0316] S913: The transmission server sends the encapsulated multiple downlink data to the second network element.

[0317] Correspondingly, the second network element receives the encapsulated multiple downlink data.

[0318] In some embodiments, the second network element may include a network element responsible for user plane functions such as a UPF network element.

[0319] S914. The second network element maps the encapsulated multiple downlink data to the corresponding QoS flow according to the QUIC encapsulation identifier in the encapsulated multiple downlink data.

[0320] Exemplarily, when the second network element receives encapsulated downlink data, such as a downlink service flow, it can determine the QUIC encapsulation identifier in the downlink service flow. Then, the second network element can map the encapsulated downlink service flow to the QoS flow corresponding to the encapsulation identifier based on the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the downlink service flow sent by the network element responsible for session management, such as the SMF network element (the identifier of the QoS flow in S908).

[0321] In some embodiments, the second network element can perform data packet detection of downlink data such as downlink service flow and marking of corresponding QoS flow identifier based on the PDR rules and QoS flow identifier corresponding to the encapsulation identifier sent by the network element responsible for session management, such as the SMF network element.

[0322] For example, multiple downlink data are service flow #1, service flow #2, and service flow #3. The QUIC encapsulation identifier of service flow #1 and service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 can be encapsulation identifier #2. Then the QFI of the QoS flow with encapsulation identifier #1 is QFI #1, and the QFI of the QoS flow with encapsulation identifier #2 is QFI #2. The UPF network element can determine that the QUIC encapsulation identifier in the encapsulated service flow #1 and service flow #3 is encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated service flow #2 is encapsulation identifier #2, then map service flow #1 and service flow #3 to the QoS flow of QFI #1, and map service flow #2 to the QoS flow of QFI #2.

[0323] For example, multiple downlink data are packet set #1, packet set #2, and packet set #3 in the same service flow. The QUIC encapsulation identifier of packet set #1 and packet set #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to packet set #2 can be encapsulation identifier #2. Then the QFI of the QoS flow with encapsulation identifier #1 is QFI #1, and the QFI of the QoS flow with encapsulation identifier #2 is QFI #2. The UPF network element can determine that the QUIC encapsulation identifier in the encapsulated packet set #1 and packet set #3 is encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated packet set #2 is encapsulation identifier #2, then map packet set #1 and packet set #3 to the QoS flow of QFI #1, and map packet set #2 to the QoS flow of QFI #2.

[0324] S915, the transmission server sends a QUIC encapsulation identifier of multiple data to the transmission client.

[0325] The transmission server sends a plurality of QUIC encapsulation identifiers of uplink data to the transmission client.

[0326] The transmission server can use the QUIC encapsulation identifier of multiple uplink data to encapsulate multiple uplink data.

[0327] In some embodiments, the application server comprises a VAL server.

[0328] In some embodiments, the transport client comprises a SEALDD client.

[0329] In some embodiments, the transport server comprises a SEALDD server.

[0330] It should be understood that in steps S901 to S907, the plurality of data may be uplink data or downlink data. In steps S907 to S912, the plurality of data is downlink data. In step S913, the plurality of data is uplink data.

[0331] The following is an exemplary introduction to the uplink QUIC data processing of the transmission client and user equipment in conjunction with Figures 10 and 11.

[0332] Figure 10 is a schematic diagram of the method for uplink QUIC data processing provided in an embodiment of the present application.

[0333] S1001: The transmission client obtains multiple data.

[0334] Among them, one data of the multiple data is a business flow or a data packet set, the data packet set includes at least one data packet, and the multiple data are multiple uplink data.

[0335] In some embodiments, the plurality of data includes a plurality of uplink service flows.

[0336] In some embodiments, the multiple data packets are multiple uplink data packet sets in the same uplink service flow, and each data packet set includes at least one data packet.

[0337] In some embodiments, the transmission client may obtain a plurality of data from the application client.

[0338] 1002. The transmission client obtains the QUIC encapsulation identifier of multiple data.

[0339] In some embodiments, the transmission client receives a QUIC encapsulation identifier of multiple data sent by the transmission server. The QUIC encapsulation identifier of the multiple data is determined by the transmission server. The content of the encapsulation identifier determined by the transmission server can refer to the relevant description in S802, and this application will not repeat it here.

[0340] S1003, the transmission client encapsulates the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data.

[0341] When the transmission client receives the uplink data, it encapsulates the uplink data according to the QUIC encapsulation identifier corresponding to the uplink data.

[0342] For example, the QUIC encapsulation identifier corresponding to upstream service flow #2 (IP quintuple #2) is<connection ID#2> The transmission client encapsulates the uplink service flow #2 from the application client, and the encapsulated data carries the QUIC connection identifier<connection ID#2> .

[0343] S1004: The transmission client sends the encapsulated multiple data to the user equipment.

[0344] Accordingly, the user equipment receives the encapsulated multiple data.

[0345] S1005. The user equipment uses the QUIC encapsulation identifier in the encapsulated multiple data to map the encapsulated multiple data to the corresponding QoS flow.

[0346] When the user equipment receives encapsulated uplink data, such as an uplink service flow, it can determine the QUIC encapsulation identifier in the uplink service flow. Then, the user equipment can map the encapsulated uplink service flow to the QoS flow corresponding to the encapsulation identifier based on the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the uplink service flow sent by the first network element, such as the SMF network element.

[0347] In some embodiments, the user equipment can perform data packet detection of uplink data such as uplink service flow and marking of corresponding QoS flow identifier based on the PDR rules and encapsulation identifier corresponding to the QoS flow sent by the first network element, such as the SMF network element.

[0348] For example, multiple uplink data are service flow #1, service flow #2, and service flow #3. The QUIC encapsulation identifier of service flow #1 and service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 can be encapsulation identifier #2. Then the QFI of the QoS flow with encapsulation identifier #1 is QFI #1, and the QFI of the QoS flow with encapsulation identifier #2 is QFI #2. The user equipment can determine that the QUIC encapsulation identifier in the encapsulated service flow #1 and service flow #3 is encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated service flow #2 is encapsulation identifier #2, then map service flow #1 and service flow #3 to the QoS flow of QFI #1, and map service flow #2 to the QoS flow of QFI #2.

[0349] For example, multiple uplink data are packet set #1, packet set #2, and packet set #3 in the same service flow. The QUIC encapsulation identifier of packet set #1 and packet set #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to packet set #2 can be encapsulation identifier #2. Then the QFI of the QoS flow with encapsulation identifier #1 is QFI #1, and the QFI of the QoS flow with encapsulation identifier #2 is QFI #2. The user equipment can determine that the QUIC encapsulation identifier in the encapsulated packet set #1 and packet set #3 is encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated packet set #2 is encapsulation identifier #2, then map packet set #1 and packet set #3 to the QoS flow of QFI #1, and map packet set #2 to the QoS flow of QFI #2.

[0350] Figure 11 is a schematic diagram of the method for uplink QUIC data processing provided in an embodiment of the present application.

[0351] S1101: The transmission client receives multiple data from the application client.

[0352] In some embodiments, the application client comprises a VAL client.

[0353] In some embodiments, the transport client comprises a SEALDD client.

[0354] In some embodiments, the plurality of data includes a plurality of uplink service flows. For example, the transmission client may receive a plurality of uplink service flows from the response client.

[0355] In some embodiments, the multiple data packets are multiple uplink data packet sets in the same uplink service flow, and each data packet set includes at least one data packet. For example, the transmission client can receive multiple uplink data packet sets in the same uplink service flow from the application client.

[0356] S1102, the transmission client receives a QUIC encapsulation identifier of multiple data from the transmission server.

[0357] The QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, and there is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data.

[0358] The content of the package identifier determined by the transmission server can refer to the relevant description in S802, and this application will not go into details here.

[0359] S1103, the transmission client encapsulates the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data.

[0360] When the transmission client receives the uplink data, it encapsulates the uplink data according to the QUIC encapsulation identifier corresponding to the uplink data.

[0361] For example, the QUIC encapsulation identifier corresponding to the upstream service flow #2 (IP quintuple #2) can be<connection ID#2> The transmission client encapsulates the uplink service flow #2 from the application client, and the encapsulated data carries the QUIC connection identifier<connection ID#2> .

[0362] S1104: The transmission client sends the encapsulated multiple data to the user equipment.

[0363] Accordingly, the user equipment receives the encapsulated multiple data.

[0364] S1105. The first network element sends the QoS flow identifier corresponding to the QUIC encapsulation identifier of multiple data to the user equipment.

[0365] In some embodiments, the first network element is a network element responsible for session management, such as an SMF network element. The first network element can determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data based on the QUIC encapsulation identifier of the multiple data.

[0366] For example, the identifier of the QoS flow may include QCI, QFI, etc.

[0367] S1106: The user equipment maps the encapsulated multiple data to the QoS flow of the multiple data according to the QUIC encapsulation identifier in the encapsulated multiple data.

[0368] Figure 12 is a schematic diagram of a QUIC data processing method provided in an embodiment of the present application. Figure 12 is a scenario of multiple business flows.

[0369] S1201, the UE establishes a PDU session with the 5G core network.

[0370] The network connection between UE, RAN, UPF network elements and DN is achieved through the establishment of PDU session.

[0371] S1202: The VAL server sends a service subscription request message to the SEALDD server.

[0372] The request message includes information about multiple service flows, for example, the service flow information may include service flow descriptor information (such as IP 5-tuple information) and QoS information corresponding to the descriptor information, etc. The QoS information may include QoS requirement information and / or QoS importance information.

[0373] For example, the multiple service flows include service flow #1 and service flow #2. The descriptor information (IP quintuple #1) of service flow #1 corresponds to QoS information #1, and the descriptor information (IP quintuple #2) of service flow #2 corresponds to QoS information #2.

[0374] S1203: The SEALDD server sends a service subscription request response message to the VAL server.

[0375] S1204: The VAL client and the VAL server perform signaling negotiation to determine a data processing method between the VAL client and the VAL server.

[0376] For example, in an embodiment of the present application, after signaling negotiation, it is determined to use the SEALDD enabling layer to perform QUIC data processing.

[0377] S1205: The VAL client sends a service request message to the SEALDD client.

[0378] S1206: The SEALDD client sends a connection or handshake request message to the SEALDD server.

[0379] In some embodiments, the request message content includes identification information that can be assigned by the SEALDD client for the QUIC connection, such as connection ID(s) that can be assigned, or other identification information that can be assigned.

[0380] In some embodiments, the request message content includes an IP address and / or port number assignable by the SEALDD client.

[0381] S1207, the SEALDD server determines the QUIC encapsulation identifier corresponding to the service flow based on the QoS information corresponding to the service flow.

[0382] In some embodiments, the QUIC encapsulation identifier may include: information used to represent the QUIC connection, information in an IP triplet, or information in an IP quintuple.

[0383] That is, the information used to represent the QUIC connection can be used as the encapsulation identifier, or the information in the IP triplet can be used as the encapsulation identifier, or the information in the IP quintuple can be used as the encapsulation identifier.

[0384] The information used to represent the QUIC connection includes the allocatable QUIC connection identifier and other identifiers used to represent the QUIC connection other than the allocatable QUIC connection identifier.

[0385] An IP triplet may include information of an IP address, protocol, and port.

[0386] The IP quintuple may include source IP address, source port, destination IP address, destination port, and transport layer protocol information.

[0387] Exemplarily, the encapsulation identifier includes information that can be assigned by a transport server and / or a transport client to represent a QUIC connection.

[0388] That is, the information that can be assigned by the transport server and / or the transport client to represent the QUIC connection can be used as an encapsulation identifier.

[0389] In some embodiments, the transmission server can determine the QUIC encapsulation identifiers of multiple business flows based on the transmission requirement information of the multiple business flows, as well as the first connection information and / or the second connection information.

[0390] The first connection information is information that can be assigned by the transmission server to represent the QUIC connection, and the first connection information includes a QUIC connection identifier that can be assigned by the transmission server and / or other information used to represent the QUIC connection. The second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes a QUIC connection identifier that can be assigned by the transmission client and / or other information used to represent the QUIC connection.

[0391] For example, the QUIC encapsulation identifiers of multiple business flows can be determined based on the transmission requirement information of multiple business flows, the QUIC connection identifiers that can be assigned by the transmission server, and the QUIC connection identifiers that can be assigned by the transmission client.

[0392] Take the QUIC encapsulation identifier of the downstream business flow as an example. For example, for different QUIC connections, the QUIC connection identifiers that the transmission server can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#1> 、<connection ID#2> 、<connection ID#1,connection ID#3> 、<connection ID#1,connection ID#4> 、<connection ID#2,connection ID#3> 、<connection ID#2,connection ID#4> . The first two encapsulation identifiers are composed of the source connection identifier (corresponding to the downlink business flow, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission server); the next four identifiers are composed of the source connection identifier and the destination connection identifier (for the downlink business flow, the destination connection is the QUIC connection identifier that can be assigned by the transmission client).

[0393] If multiple downlink service flows correspond to multiple different transmission requirement information, such as downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 are

[0394] Taking the QUIC encapsulation identifier of the uplink service flow as an example, for different QUIC connections, the QUIC connection identifiers that the transmission client can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#3> 、<connection ID#4> 、<connection ID#3,connection ID#1> 、<connection ID#4,connection ID#1> 、<connection ID#3,connection ID#2> 、<connection ID#4,connection ID#4> . The first two encapsulation identifiers are composed of the source connection identifier (corresponding to the uplink business flow, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission client); the next four identifiers are composed of the source connection identifier and the destination connection identifier (for the uplink business flow, the destination connection is the QUIC connection identifier that can be assigned by the transmission server).

[0395] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and downlink service flow #3 can be<connection ID#3> , the QUIC encapsulation identifier corresponding to the upstream service flow #2 can be<connection ID#4> .

[0396] Within the same QUIC connection, there is only one identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client. Therefore, it is necessary to introduce a new identifier, such as other information used to represent the QUIC connection, in combination with the identifier, to be used for the QUIC encapsulation identifier of multiple business flows with different transmission requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifiers of multiple business flows can be determined based on the transmission requirement information of multiple business flows, the QUIC connection identifier that can be assigned by the transmission server and other information representing the QUIC connection, and the QUIC connection identifier that can be assigned by the transmission client and other information representing the QUIC connection.

[0397] Taking the QUIC encapsulation identifier of the downstream service flow as an example, for example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and the transmission client is the connection ID, the other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and the other identifiers that can be assigned by the transmission client are ID#3 and ID#4, then the encapsulation identifier can be<connection ID+ID#1> 、<connection ID+ID#2> 、 <connection ID+<ID#1,ID#3> >、 <connection ID+<ID#1,ID#4> >、 <connection ID+<ID#2,ID#3> >、 <connection ID+<ID#2,ID#4> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (corresponding to the downlink business flow, the other source connection identifiers are other information that can be assigned by the transmission server to represent the QUIC connection); the last four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for the downlink business flow, the other destination connection identifiers are other information that can be assigned by the transmission client to represent the QUIC connection).

[0398] If multiple downlink service flows correspond to multiple different transmission requirement information, for example, downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 can be<connection ID+ID#1> , the QUIC encapsulation identifier corresponding to downlink service flow #2 can be<connection ID+ID#2> .

[0399] Taking the QUIC encapsulation identifier of the uplink service flow as an example, for example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client is the connection ID. Other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and other identifiers that can be assigned by the transmission client are ID#3 and ID#4. Then the encapsulation identifier can be<connection ID+ID#3> 、<connection ID+ID#4> 、 <connection ID+<ID#3,ID#1> >、 <connection ID+<ID#4,ID#1> >、 <connection ID+<ID#3,ID#2> >、 <connection ID+<ID#4,ID#2> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (corresponding to the uplink business flow, the other source connection identifiers are other information assigned by the transmission client to represent the QUIC connection); the last four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for the uplink business flow, the other destination connection identifiers are other information assignable by the transmission server to represent the QUIC connection).

[0400] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and uplink service flow #3 can be<connection ID+ID#3> , the QUIC encapsulation identifier corresponding to the upstream service flow #2 can be<connection ID#4> .

[0401] In some embodiments, the QUIC encapsulation identifiers of multiple business flows can be determined based on the transmission requirement information, first IP information and / or second IP information of the multiple business flows. The first IP information includes the IP address and port number that can be assigned by the transmission server, and the second IP information includes the IP address and port number that can be assigned by the transmission client.

[0402] That is, the IP address and port number assignable by the transmission server and / or the IP address and port number assignable by the transmission client may be used as the encapsulation identifier.

[0403] Taking the QUIC encapsulation identifier of the downstream service flow as an example, the IP address and port number that can be allocated by the transmission server are<IP#1,port#1> 、<IP#1,port#2> , the IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#1,port#1], [IP#1,port#2], [<IP#1,port#1> ,<IP#2,port#3> ]、[<IP#1,port#1> ,<IP#2,port#4> ]、[<IP#1,port#2> ,<IP#2,port#3> ]、[<IP#1,port#2> ,<IP#2,port#4> ]. The first two identifiers consist of the source address and source port number (for downlink data, the source address and source port number are the IP address and port number that can be assigned by the transmission server); the next four identifiers consist of the source address and source port number, and the destination address and destination port number (for downlink business flows, the destination address and destination port number are the address and port number that can be assigned by the transmission client).

[0404] If multiple downlink service flows correspond to multiple different transmission requirement information, for example, downlink service flow #1 corresponds to transmission requirement information #1, downlink service flow #2 corresponds to transmission requirement #2, and downlink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downlink service flow #1 and downlink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be encapsulation identifier #2. In this way, two of the above-mentioned QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers of downlink service flow #1 and downlink service flow #3 can be [IP#1, port#1], and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be [IP#1, port#2].

[0405] Taking the QUIC encapsulation identifier of the uplink service flow as an example, the IP address and port number that can be allocated by the transmission server are<IP#1,port#1> 、<IP#1,port#2> The IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#2,port#3], [IP#2,port#4], [<IP#2,port#3> ,<IP#1,port#1> ]、[<IP#2,port#4> ,<IP#1,port#1> ]、[<IP#2,port#3> ,<IP#1,port#2> ]、[<IP#2,port#4> ,<IP#1,port#2> ] The first two identifiers consist of the source address and source port number (for the upstream business flow, the source address and source port number are the IP address and port number that can be assigned by the transmission client); the next four identifiers consist of the source address and source port number, and the destination address and destination port number (for the upstream business flow, the destination address and destination port number are the address and port number that can be assigned by the transmission server).

[0406] If multiple uplink service flows correspond to multiple different transmission requirement information, for example, uplink service flow #1 corresponds to transmission requirement information #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to uplink service flow #1 and uplink service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be encapsulation identifier #2. In this way, two of the above-mentioned QUIC encapsulation identifiers can be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers of uplink service flow #1 and uplink service flow #3 can be [IP#2, port#3], and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be [IP#2, port#4].

[0407] In an embodiment of the present application, all QUIC encapsulation identifiers may be determined first, and then, based on the service flows with different transmission requirements, the corresponding QUIC encapsulation identifier may be selected and determined from all QUIC encapsulation identifiers. Alternatively, the corresponding QUIC encapsulation identifier may be directly determined based on the service flows with different transmission requirements.

[0408] S1208: The SEALDD server sends a connection / handshake response message to the SEALDD client.

[0409] In some embodiments, the response message content may include uplink business flow information and its corresponding uplink QUIC encapsulation identifier, which is used by the SEALDD client to process the uplink business flow from the VAL client.

[0410] S1209, the SEALDD server sends the QUIC encapsulation identifier corresponding to the business flow and the corresponding QoS information to the PCF.

[0411] The SEALDD server sends the QUIC encapsulation identifier and corresponding QoS information (such as QoS importance information) corresponding to the upstream business flow to the PCF, and / or the QUIC encapsulation identifier and corresponding QoS information (such as QoS importance information) corresponding to the downstream business flow.

[0412] If the SEALDD server is trustworthy for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow to the PCF network element. If the SEALDD server is untrustworthy for the 5G network, the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow need to be sent to the PCF network element through the NEF network element.

[0413] Correspondingly, the PCF network element receives the QUIC encapsulation identifier and QoS information corresponding to the service flow.

[0414] S1210, the PCF network element can generate PCC rules based on the QUIC encapsulation identifier and QoS information corresponding to the service flow.

[0415] The PCC rule may include the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information.

[0416] S1211, UE initiates a PDU session establishment or modification request to the SMF network element.

[0417] S1212, the SMF network element sends a policy request message to the PCF network element to request the QUIC encapsulation identifier corresponding to the service flow.

[0418] In some embodiments, the policy request message may also be used to request QoS information corresponding to the service flow.

[0419] S1213, the SMF network element receives the policy response message sent by the PCF network element, and determines the QFI of the QoS flow corresponding to the service flow.

[0420] The policy response message includes the QUIC encapsulation identifier corresponding to the service flow. The SMF network element can determine the QFI of the QoS flow corresponding to the service flow based on the QUIC encapsulation identifier corresponding to the service flow, that is, the QoS flows of service flows with the same QUIC encapsulation identifier have the same QFI.

[0421] In some embodiments, the policy response message also includes QoS information corresponding to the service flow.

[0422] In some embodiments, the SMF network element may also generate a PDR rule based on the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information, etc. The PDR rule includes the QUIC encapsulation identifier corresponding to the service flow.

[0423] S1214, the SMF network element sends the QUIC encapsulation identifier corresponding to the downlink service flow and the QFI of the corresponding QoS flow to the UPF network element.

[0424] In some embodiments, the SMF network element can also send QoS information corresponding to the downlink service flow to the UPF network element.

[0425] For example, the SMF network element sends the PDR rules corresponding to the downlink service flow and the QFI of the corresponding QoS flow to the UPF network element.

[0426] S1215, the SMF network element sends the QUIC encapsulation identifier corresponding to the uplink service flow and the QFI of the corresponding QoS flow to the UE.

[0427] In some embodiments, the SMF network element sends QoS information corresponding to the uplink service flow to the UE.

[0428] For example, the SMF network element sends the QoS implementation rule information of the uplink service flow to the UE. The QoS implementation rule information includes the PDR rule corresponding to the uplink service flow (such as the corresponding QUIC encapsulation identifier and the corresponding QoS information) and the QFI of the corresponding QoS flow.

[0429] S1216, the SEALDD server encapsulates the downstream service flow based on the downstream QUIC encapsulation identifier.

[0430] After the PDU session is established or modified, when a downlink service flow from the VAL server arrives, the SEALDD server encapsulates the downlink service flow based on the downlink QUIC encapsulation identifier determined by S1207.

[0431] For example, the QUIC encapsulation identifier corresponding to downlink service flow #1 is<connection ID#1> , the SEALDD server can be based on<connection ID#1> The service flow of IP quintuple #1 from the VAL server is encapsulated into a downlink QUIC data packet. That is, the QUIC data packet of the encapsulated downlink service flow carries the QUIC connection identifier.<connection ID#1> .

[0432] S1217, the SEALDD server sends the encapsulated downlink service flow to the UPF network element.

[0433] Correspondingly, the UPF network element receives the downlink service flow sent by the SEALDD server.

[0434] S1218, the UPF network element maps the downlink service flow to the QoS flow based on the QUIC encapsulation identifier in the downlink service flow and the QFI of the QoS flow corresponding to the downlink service flow.

[0435] For example, when the UPF network element receives a downstream service flow, it can perform QUIC data packet detection and corresponding QFI marking of the downstream service flow based on the PDR rule, that is, it can determine the downstream QUIC encapsulation identifier in the downstream service flow, and map the downstream service flow with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0436] S1219, the SEALDD client encapsulates the uplink service flow based on the uplink QUIC encapsulation identifier.

[0437] After the PDU session is established or modified, when an uplink service flow from a VAL client arrives, the SEALDD client encapsulates the uplink service flow based on the uplink QUIC encapsulation identifier obtained in S1208.

[0438] For example, the uplink QUIC encapsulation identifier corresponding to uplink service flow #3 is<connection ID#3> , the SEALDD client can be based on<connection ID#3> The service flow from the VAL client is encapsulated into an uplink QUIC data packet. That is, the encapsulated uplink service flow QUIC data packet carries the QUIC connection identifier<connection ID#3> .

[0439] S1220: The SEALDD client sends the encapsulated uplink service flow to the UE.

[0440] Correspondingly, the UE receives the encapsulated uplink service flow sent by the SEALDD client.

[0441] S1221. The UE maps the uplink service flow to the QoS flow based on the QUIC encapsulation identifier in the uplink service flow and the QFI of the QoS flow corresponding to the uplink service flow.

[0442] For example, when the UE receives an uplink service flow, it can perform QUIC data packet detection and QFI marking corresponding to the uplink service flow, that is, it can determine the QUIC encapsulation identifier in the uplink service flow and the QFI of the QoS flow corresponding to the uplink service flow, and map the uplink service flow with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0443] Figure 13 is a schematic diagram of a QUIC data processing method provided by an embodiment of the present application. Figure 13 is an application scenario of a single service flow. For example, a single service flow includes a set of data packets with different QoS information.

[0444] S1301, the UE has established a PDU session with the 5G core network.

[0445] Realize network connection from UE to RAN to UPF to DN.

[0446] S1302: The VAL server sends a service subscription request message to the SEALDD server.

[0447] The request message may include service flow information, for example, the service flow information may include protocol description information of the service flow (the service flow is transmitted using the RTP protocol), or the service flow information may include protocol description information of the service flow and QoS information of a set of data packets corresponding to the protocol description information. The QoS information may include QoS requirement information and / or QoS importance information.

[0448] For example, the QoS information corresponding to the data packet set #1 is QoS information #1; and the QoS information corresponding to the data packet set #2 is QoS information #2.

[0449] S1303: The SEALDD server sends a service subscription request response message to the VAL server.

[0450] S1304: The VAL client and the VAL server perform signaling negotiation to determine a data processing method between the VAL client and the VAL server.

[0451] For example, in an embodiment of the present application, after signaling negotiation, it is determined to use the SEALDD enabling layer to perform QUIC data processing.

[0452] S1305: The VAL client sends a service request message to the SEALDD client.

[0453] S1306: The SEALDD client sends a connection or handshake request message to the SEALDD server.

[0454] In some embodiments, the request message content includes identification information that can be assigned by the SEALDD client for the QUIC connection, such as connection ID(s) that can be assigned, or other identification information that can be assigned.

[0455] S1307, the SEALDD server determines the QUIC encapsulation identifier corresponding to the data packet set based on the QoS information corresponding to the data packet set.

[0456] In some embodiments, the encapsulation identifier may include: information used to represent a QUIC connection, information in a QUIC tunnel header, information in an IP triplet, or information in an IP quintuple.

[0457] That is, the information used to represent the QUIC connection can be used as the encapsulation identifier, or the information in the QUIC tunnel header can be used as the encapsulation identifier, or the information in the IP triplet can be used as the encapsulation identifier, or the information in the IP quintuple can be used as the encapsulation identifier.

[0458] The information used to represent the QUIC connection includes the allocatable QUIC connection identifier and other identifiers used to represent the QUIC connection other than the allocatable QUIC connection identifier.

[0459] An IP triplet may include information of an IP address, protocol, and port.

[0460] The IP quintuple may include source IP address, source port, destination IP address, destination port, and transport layer protocol information.

[0461] Exemplarily, the encapsulation identifier includes information that can be assigned by the transport server and / or the transport client to represent a QUIC connection.

[0462] That is, the information that can be assigned by the transport server and / or the transport client to represent the QUIC connection can be used as an encapsulation identifier.

[0463] In some embodiments, the transmission server determines the QUIC encapsulation identifiers of the multiple data packet sets based on the transmission requirement information of the multiple data packet sets, and the first connection information and / or the second connection information.

[0464] The first connection information is information that can be assigned by the transmission server to represent a QUIC connection, and the first connection information includes a QUIC connection identifier that can be assigned by the transmission server and / or other information used to represent a QUIC connection. The second connection information is information that can be assigned by the transmission client to represent a QUIC connection, and the second connection information includes a QUIC connection identifier that can be assigned by the transmission client and / or other information used to represent a QUIC connection.

[0465] For example, the QUIC encapsulation identifiers of multiple data packet sets can be determined based on the transmission requirement information of the multiple data packet sets, the QUIC connection identifiers that can be assigned by the transmission server, and the QUIC connection identifiers that can be assigned by the transmission client.

[0466] Take the QUIC encapsulation identifier of the following packet set as an example. For example, for different QUIC connections, the QUIC connection identifiers that the transmission server can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#1> 、<connection ID#2> 、<connection ID#1,connection ID#3> 、<connection ID#1,connection ID#4> 、<connection ID#2,connection ID#3> 、<connection ID#2,connection ID#4> . The first two encapsulation identifiers are composed of the source connection identifier (corresponding to the downlink data packet set, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission server); the next four identifiers are composed of the source connection identifier and the destination connection identifier (for the downlink data packet set, the destination connection is the QUIC connection identifier that can be assigned by the transmission client).

[0467] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 can be<connection ID#1,connection ID#3> , the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be<connection ID#1,connection ID#4> .

[0468] Taking the QUIC encapsulation identifier of the uplink data packet set as an example, for different QUIC connections, the QUIC connection identifiers that the transmission client can assign are connection ID#1 and connection ID#2, and the QUIC connection identifiers that the transmission client can assign are connection ID#3 and connection ID#4. The QUIC encapsulation identifier may include<connection ID#3> 、<connection ID#4> 、<connection ID#3,connection ID#1> 、<connection ID#4,connection ID#1> 、<connection ID#3,connection ID#2> 、<connection ID#4,connection ID#4> . The first two encapsulation identifiers are composed of the source connection identifier (corresponding to the uplink data packet set, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission client); the next four identifiers are composed of the source connection identifier and the destination connection identifier (for the uplink data packet set, the destination connection is the QUIC connection identifier that can be assigned by the transmission server).

[0469] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 can be<connection ID#3,connection ID#1> , the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be<connection ID#4,connection ID#1> .

[0470] Within the same QUIC connection, there is only one identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client. Therefore, it is necessary to introduce a new identifier, such as other information used to represent the QUIC connection, in combination with the identifier, to be used as the QUIC encapsulation identifier for multiple data packet sets with different transmission requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifiers of multiple data packet sets can be determined based on the transmission requirement information of the multiple data packet sets, the QUIC connection identifier that can be assigned by the transmission server and other information representing the QUIC connection, and the QUIC connection identifier that can be assigned by the transmission client and other information representing the QUIC connection.

[0471] Take the QUIC encapsulation identifier of the following data packet set as an example. For example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and the transmission client is the connection ID. Other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and other identifiers that can be assigned by the transmission client are ID#3 and ID#4. Then the encapsulation identifier can be<connection ID+ID#1> 、<connection ID+ID#2> 、 <connection ID+<ID#1,ID#3> >、 <connection ID+<ID#1,ID#4> >、 <connection ID+<ID#2,ID#3> >、 <connection ID+<ID#2,ID#4> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (corresponding to the downlink data packet set, the other source connection identifiers are other information that can be assigned by the transmission server to represent the QUIC connection); the next four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for the downlink data packet set, the other destination connection identifiers are other information that can be assigned by the transmission client to represent the QUIC connection).

[0472] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 can be <connection ID+<ID#1,ID#3> >, the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be <connection ID+<ID#1,ID#4> >.

[0473] Taking the QUIC encapsulation identifier of the uplink data packet set as an example, for example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be assigned by the transmission server and / or the transmission client is the connection ID. Other identifiers that can be assigned by the transmission server are ID#1 and ID#2, and other identifiers that can be assigned by the transmission client are ID#3 and ID#4. Then the encapsulation identifier can be<connection ID+ID#3> 、<connection ID+ID#4> 、 <connection ID+<ID#3,ID#1> >、 <connection ID+<ID#4,ID#1> >、 <connection ID+<ID#3,ID#2> >、 <connection ID+<ID#4,ID#2> >. The first two encapsulation identifiers are composed of the connection ID and other assignable source connection identifiers (corresponding to the uplink data packet set, the other source connection identifiers are other information assigned by the transmission client to represent the QUIC connection); the next four identifiers are composed of the connection ID, other source connection identifiers and other destination connection identifiers (for uplink data, the other destination connection identifiers are other information assignable by the transmission server to represent the QUIC connection).

[0474] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be encapsulation identifier #2. In this way, two can be selected from the above-mentioned QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 can be <connection ID+<ID#3,ID#1> >, the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be <connection ID+<ID#4,ID#1> >.

[0475] In some embodiments, the QUIC encapsulation identifiers of the plurality of data packets may be determined based on the transmission requirement information of the plurality of data packet sets, and the first IP information and / or the second IP information. The first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0476] That is, the IP address and port number assignable by the transmission server and / or the IP address and port number assignable by the transmission client may be used as the encapsulation identifier.

[0477] Taking the QUIC encapsulation identifier of the following packet set as an example, the IP address and port number that the transmission server can assign are<IP#1,port#1> 、<IP#1,port#2> The IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#1,port#1], [IP#1,port#2], [<IP#1,port#1> ,<IP#2,port#3> ]、[<IP#1,port#1> ,<IP#2,port#4> ]、[<IP#1,port#2> ,<IP#2,port#3> ]、[<IP#1,port#2> ,<IP#2,port#4> ]. The first two identifiers are composed of the source address and source port number (for the downstream data packet set, the source address and source port number are the IP address and port number that can be assigned by the transmission server); the next four identifiers are composed of the source address and source port number, and the destination address and destination port number (for the downstream data packet set, the destination address and destination port number are the address and port number that can be assigned by the transmission client).

[0478] If multiple downlink data packet sets in a downlink service flow correspond to multiple different transmission requirements, for example, downlink data packet set #1 corresponds to transmission requirement information #1, downlink data packet set #2 corresponds to transmission requirement information #1, and downlink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and downlink data packet set #2 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 may be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers may be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers corresponding to downlink data packet set #1 and data packet set #2 may be [<IP#1,port#1> ,<IP#2,port#3> ], the QUIC encapsulation identifier corresponding to the downlink data packet set #3 can be [<IP#1,port#1> ,<IP#2,port#4> ].

[0479] Taking the QUIC encapsulation identifier of the uplink data packet set as an example, the IP address and port number that the transmission server can assign are<IP#1,port#1> 、<IP#1,port#2> , the IP address and port number that can be assigned to the transmission client are<IP#2,port#3> 、<IP#2,port#4> . Then the QUIC encapsulation identifier may include [IP#2,port#3], [IP#2,port#4], [<IP#2,port#3> ,<IP#1,port#1> ]、[<IP#2,port#4> ,<IP#1,port#1> ]、[<IP#2,port#3> ,<IP#1,port#2> ]、[<IP#2,port#4> ,<IP#1,port#2> ]. The first two identifiers are composed of the source address and source port number (for the uplink data packet set, the source address and source port number are the IP address and port number that can be assigned by the transmission client); the next four identifiers are composed of the source address and source port number, and the destination address and destination port number (for the uplink data packet set, the destination address and destination port number are the address and port number that can be assigned by the transmission server).

[0480] If multiple uplink data packet sets in an uplink service flow correspond to multiple different transmission requirements, for example, uplink data packet set #1 corresponds to transmission requirement information #1, uplink data packet set #2 corresponds to transmission requirement information #1, and uplink data packet set #3 corresponds to transmission requirement information #2, then the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and uplink data packet set #2 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 may be encapsulation identifier #2. In this way, two of the above QUIC encapsulation identifiers may be selected as encapsulation identifier #1 and encapsulation identifier #2, respectively. For example, the QUIC encapsulation identifiers corresponding to uplink data packet set #1 and data packet set #2 may be [<IP#2,port#3> ,<IP#1,port#1> ], the QUIC encapsulation identifier corresponding to the uplink data packet set #3 can be [<IP#2,port#4> ,<IP#1,port#1> ].

[0481] In an embodiment of the present application, all QUIC encapsulation identifiers may be determined first, and then, based on a set of data packets with different transmission requirements, a corresponding QUIC encapsulation identifier may be selected and determined from all QUIC encapsulation identifiers. Alternatively, a corresponding QUIC encapsulation identifier may be directly determined based on a set of data packets with different transmission requirements.

[0482] S1308: The SEALDD server sends a connection / handshake response message to the SEALDD client.

[0483] In some embodiments, the response message content may include information about the uplink business flow and a QUIC encapsulation identifier corresponding to the data packet set of the uplink business flow, which is used by the SEALDD client to process the data packet set of the uplink business flow from the VAL client.

[0484] S1309, the SEALDD server sends the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set of the business flow to the PCF.

[0485] The SEALDD server sends the QUIC encapsulation identifier and corresponding QoS information (such as QoS importance information) corresponding to the data packet set of the upstream service flow to the PCF network element, and / or the QUIC encapsulation identifier and corresponding QoS information (such as QoS importance information) corresponding to the data packet set of the downstream service flow.

[0486] If the SEALDD server is trustworthy for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set to the PCF network element. If the SEALDD server is untrustworthy for the 5G network, the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set need to be sent to the PCF network element through the NEF network element.

[0487] Correspondingly, the PCF network element receives the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set of the service flow.

[0488] S1310, the PCF network element can generate PCC rules based on the QUIC encapsulation identifier corresponding to the data packet set of the service flow and the corresponding QoS information.

[0489] That is, the PCC rule may include the QUIC encapsulation identifier and QoS information corresponding to the data packet set.

[0490] S1311, UE initiates a PDU session establishment or modification request to the SMF network element.

[0491] S1312, the SMF network element sends a policy request message to the PCF network element to request the QUIC encapsulation identifier corresponding to the data packet set of the service flow.

[0492] In some embodiments, the policy request message may also be used to request QoS information corresponding to a set of data packets of a service flow.

[0493] S1313, the SMF network element receives the policy response message sent by the PCF network element, and determines the QFI of the QoS flow corresponding to the data packet set of the service flow.

[0494] The policy response message includes the QUIC encapsulation identifier corresponding to the data packet set of the service flow. The SMF can determine the QFI of the QoS flow corresponding to the data packet set based on the QUIC encapsulation identifier corresponding to the data packet set. That is, the QFI of the QoS flow of the data packet set with the same QUIC encapsulation identifier is the same.

[0495] In some embodiments, the policy response message further includes QoS information corresponding to the data packet set.

[0496] In some embodiments, the SMF network element may also generate a PDR rule based on the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set. The PDR rule includes the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set.

[0497] S1314, the SMF network element sends the QUIC encapsulation identifier corresponding to the data packet set of the downlink service flow and the QFI of the corresponding QoS flow to the UPF network element.

[0498] In some embodiments, the SMF network element can also send QoS information corresponding to the data packet set to the UPF.

[0499] For example, the SMF network element sends the PDR rule corresponding to the data packet set and the QFI of the corresponding QoS flow to the UPF network element. The PDR rule includes the QUIC encapsulation identifier corresponding to the data packet set and the corresponding QoS information.

[0500] S1315, the SMF network element sends the QUIC encapsulation identifier corresponding to the data packet set of the uplink service flow and the QFI of the corresponding QoS flow to the UE.

[0501] In some embodiments, the SMF network element sends QoS information corresponding to a set of data packets of an uplink service flow to the UE.

[0502] For example, the SMF sends the QoS implementation rule information of the data packet set to the UE. The QoS implementation rule information includes the PDR rule corresponding to the data packet set (such as the corresponding QUIC encapsulation identifier and the corresponding QoS information) and the QFI of the corresponding QoS flow.

[0503] S1316, the SEALDD server encapsulates the data packet set of the downstream business flow based on the downstream QUIC encapsulation identifier.

[0504] For example, after a PDU session is established or modified, when a downlink service flow arrives from a VAL server, the SEALDD server can determine the packet set of the downlink service flow (e.g., determine that certain packets belong to packet set #1) based on the service flow protocol description information of the VAL server. The SEALDD server then encapsulates the packet set of the downlink service flow based on the downlink QUIC encapsulation identifier.

[0505] For example, determine the QUIC encapsulation identifier corresponding to packet set #1 is<connection ID#1> , the SEALDD server can be based on<connection ID#1> The data packet set from the VAL server is encapsulated as a downlink QUIC data packet. That is, the encapsulated downlink data packet set #1 carries the QUIC connection identifier<connection ID#1> .

[0506] S1317, the SEALDD server sends the encapsulated downlink data packet set to the UPF network element.

[0507] Correspondingly, the UPF network element receives the downlink data packet set sent by the SEALDD server.

[0508] S1318, the UPF network element maps the downlink / data packet set to the QoS flow based on the QUIC encapsulation identifier in the downlink data packet set in S1314 and the QFI of the QoS flow corresponding to the downlink data packet set.

[0509] For example, when the UPF network element receives a downlink data packet set, it can perform QUIC data packet detection and corresponding QFI marking of the downlink data packet set based on the PDR rule, that is, it can determine the QUIC encapsulation identifier in the downlink data packet set, and project the downlink data packet set with the same QUIC encapsulation identifier into the QoS flow with the same QFI.

[0510] S1319, the SEALDD client encapsulates the uplink data packet set based on the uplink QUIC encapsulation identifier.

[0511] After the PDU session is established or modified, when an uplink packet set arrives from the VAL client, the SEALDD client can determine the packet or packet set based on the VAL client's service flow protocol description information (e.g., determining that certain packets belong to packet set #3). The SEALDD client then encapsulates the uplink packet set based on the uplink QUIC encapsulation identifier.

[0512] For example, the uplink QUIC encapsulation identifier corresponding to uplink data packet set #3 is<connection ID#3> , the SEALDD client can be based on<connection ID#3> The uplink QUIC data packet set #3 from the VAL client is encapsulated. That is, the encapsulated uplink data packet set #3 carries the QUIC connection identifier.<connection ID#3> .

[0513] S1320: The SEALDD client sends the encapsulated uplink data packet set to the UE.

[0514] Correspondingly, the UE receives the uplink data packet set sent by the SEALDD client.

[0515] S1321, the UE maps the uplink service flow to the QoS flow according to the QUIC encapsulation identifier in the uplink data packet set in S1315 and the identifier of the QoS flow corresponding to the uplink data packet set.

[0516] For example, when the UE receives an uplink data packet set, it can perform QUIC data packet detection on the uplink data packet set and mark the QoS flow identifier, that is, it can determine the QUIC encapsulation identifier in the uplink data packet set and the QFI of the corresponding QoS flow, and map the uplink data packet set with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0517] Figure 14 is a schematic diagram of a QUIC data processing method provided in an embodiment of the present application. For example, Figure 14 is a transmission scenario of multiple downlink service flows.

[0518] S1401: The VAL server sends a service subscription request message to the SEALDD server.

[0519] The request message includes information about multiple service flows. For example, the service flow information may include service flow descriptor information (such as IP 5-tuple) and QoS information corresponding to the descriptor information. The QoS information may include QoS requirement information and / or QoS importance information.

[0520] For example, the multiple service flows include service flow #1 and service flow #2. The descriptor information of service flow #1 is P quintuple #1, corresponding to QoS information #1; the descriptor information of service flow #2 is IP quintuple #2, corresponding to QoS information #2.

[0521] S1402: The SEALDD server sends a service subscription request response message to the VAL server.

[0522] S1403, the SEALDD server determines the QUIC encapsulation identifier corresponding to the service flow based on the QoS information corresponding to the service flow.

[0523] In an embodiment of the present application, service flows with the same QoS information, such as QoS parameters / importance, have the same corresponding QUIC encapsulation identifiers; service flows with different QoS information, such as QoS requirement information / importance information, have different corresponding QUIC encapsulation identifiers.

[0524] For example, service flow #1 corresponds to QoS information #1; service flow #2 corresponds to QoS information #2; and service flow #3 corresponds to QoS information #1. The QUIC encapsulation identifiers corresponding to service flow #1 and service flow #3 can be QoS information #1 or encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 can be QoS information #2 or encapsulation identifier #2.

[0525] In some embodiments, the QUIC encapsulation identifier may include information in the QUIC tunnel header. For example, some information in the QUIC tunnel header may be used as the QUIC encapsulation identifier, or QoS information may be encapsulated in the QUIC tunnel header.

[0526] S1404, the SEALDD server sends the QUIC encapsulation identifier and corresponding QoS information of the service flow to the PCF network element.

[0527] If the SEALDD server is trustworthy for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow to the PCF network element. If the SEALDD server is untrustworthy for the 5G network, the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow need to be sent to the PCF network element through the NEF network element.

[0528] Correspondingly, the PCF network element receives the QUIC encapsulation identifier and QoS information corresponding to the service flow.

[0529] S1405, the PCF network element can generate PCC rules based on the QUIC encapsulation identifier and QoS information corresponding to the service flow.

[0530] PCC rules may include the QUIC encapsulation identifier and QoS information corresponding to the service flow.

[0531] S1406, the UE initiates a PDU session establishment or modification request to the SMF network element.

[0532] S1407, the SMF network element sends a policy request message to the PCF network element to request the QUIC encapsulation identifier corresponding to the service flow.

[0533] In some embodiments, the policy request message may also be used to request QoS information corresponding to the service flow.

[0534] S1408, the SMF network element receives the policy response message sent by the PCF network element, and determines the QFI of the QoS flow corresponding to the service flow.

[0535] The policy response message includes the QUIC encapsulation identifier corresponding to the service flow. The SMF network element can determine the QFI of the QoS flow corresponding to the service flow based on the QUIC encapsulation identifier corresponding to the service flow, that is, the QoS flows of service flows with the same QUIC encapsulation identifier have the same QFI.

[0536] In some embodiments, the policy response message also includes QoS information corresponding to the service flow.

[0537] In some embodiments, the SMF network element may also generate a PDR rule based on the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow. The PDR rule includes the QUIC encapsulation identifier and corresponding QoS information corresponding to the service flow.

[0538] S1409, the SMF network element sends the QUIC encapsulation identifier of the service flow and the QFI of the corresponding QoS flow to the UPF network element.

[0539] In some embodiments, the SMF network element sends QoS information corresponding to the service flow to the UPF network element.

[0540] For example, the SMF network element sends the PDR rule corresponding to the service flow and the QFI of the corresponding QoS flow to the UPF network element. The PDR rule includes the QUIC encapsulation identifier corresponding to the service flow.

[0541] S1410: The UE completes the remaining PDU session establishment or modification process.

[0542] S1411, a QUIC tunnel is established between the UPF network element and the SEALDD server.

[0543] S1412: The VAL server sends the service flow to the SEALDD server.

[0544] S1413, the SEALDD server encapsulates the business flow according to the QUIC encapsulation identifier corresponding to the business flow.

[0545] S1414, the SEALDD server sends the encapsulated service flow to the UPF network element.

[0546] S1415, the UPF network element maps the service flow to the QoS flow based on the QUIC encapsulation identifier in the service flow of S1409 and the QFI of the QoS flow corresponding to the service flow.

[0547] When the UPF network element receives a service flow, it can perform QUIC data packet detection and QFI marking of the service flow based on the PDR rules, that is, it can determine the QUIC encapsulation identifier in the service flow and map the service flow with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0548] Figure 15 is a schematic diagram of a QUIC data processing method provided in an embodiment of the present application. For example, Figure 15 is a scenario of a single downlink service flow, which includes a set of downlink data packets with different QoS information.

[0549] S1501: The VAL server sends a service subscription request message to the SEALDD server.

[0550] The request message may include service flow information, for example, the service flow information may include protocol description information of the service flow (the service flow is transmitted using the RTP protocol), or the service flow information may include protocol description information of the service flow and QoS information of a set of data packets corresponding to the protocol description information. The QoS information may include QoS requirement information and / or QoS importance information.

[0551] For example, the service flow includes data packet set #1 and data packet set #2, wherein data packet set #1 corresponds to QoS information #1, and data packet set #2 corresponds to QoS information #2.

[0552] S1502: The SEALDD server sends a service subscription request response message to the VAL server.

[0553] S1503, the SEALDD server determines the QUIC encapsulation identifier corresponding to the data packet set based on the QoS information corresponding to the data packet set.

[0554] In an embodiment of the present application, a set of data packets with the same QoS information, such as QoS requirement information and / or importance information, have the same corresponding QUIC encapsulation identifier; a set of data packets with different QoS information, such as QoS requirement information / importance information, have different corresponding QUIC encapsulation identifiers.

[0555] For example, packet set #1 corresponds to QoS information #1; packet set #2 corresponds to QoS information #2; and packet set #3 corresponds to QoS information #1. Then the QUIC encapsulation identifiers corresponding to packet set #1 and packet set #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to packet set #2 can be encapsulation identifier #2.

[0556] In some embodiments, the QUIC encapsulation identifier may include information in the QUIC tunnel header. For example, some information in the QUIC tunnel header may be used as the QUIC encapsulation identifier.

[0557] S1504, the SEALDD server sends the QUIC encapsulation identifier corresponding to the data packet set and the corresponding QoS information to the PCF network element.

[0558] If the SEALDD server is trustworthy for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set to the PCF network element. If the SEALDD server is untrustworthy for the 5G network, the QUIC encapsulation identifier and corresponding QoS information corresponding to the data packet set need to be sent to the PCF network element through the NEF network element.

[0559] Correspondingly, the PCF network element receives the QUIC encapsulation identifier and QoS information corresponding to the data packet set.

[0560] S1505, the PCF network element can generate PCC rules based on the QUIC encapsulation identifier and QoS information corresponding to the data packet set.

[0561] The PCC rule may include the QUIC encapsulation identifier and QoS information corresponding to the data packet set.

[0562] S1506, the UE initiates a PDU session establishment or modification request to the SMF network element.

[0563] S1507, the SMF network element sends a policy request message to the PCF network element to request the QUIC encapsulation identifier corresponding to the data packet set.

[0564] In some embodiments, the policy request message can also be used to request the QoS information corresponding to the data packet set.

[0565] S1508, the SMF network element receives the policy response message sent by the PCF network element, and determines the QFI of the QoS flow corresponding to the data packet set.

[0566] The policy response message includes the QUIC encapsulation identifier corresponding to the data packet set. The SMF network element can determine the QFI of the QoS flow corresponding to the data packet set based on the QUIC encapsulation identifier corresponding to the data packet set, that is, the QoS flows of data packet sets with the same QUIC encapsulation identifier have the same QFI.

[0567] In some embodiments, the policy response message further includes QoS information corresponding to the data packet set.

[0568] In some embodiments, the SMF network element may also generate a PDR rule based on the QUIC encapsulation identifier corresponding to the data packet set and the corresponding QoS information, etc. The PDR rule includes the QUIC encapsulation identifier corresponding to the data packet set.

[0569] S1509, the SMF network element sends the QUIC encapsulation identifier of the data packet set and the QFI of the corresponding QoS flow to the UPF network element.

[0570] In some embodiments, the SMF network element sends the data packet / QoS information corresponding to the data packet to the UPF network element.

[0571] For example, the SMF network element sends the PDR rule corresponding to the data packet / data packet and the QFI of the corresponding QoS flow to the UPF network element. The PDR rule includes the QUIC encapsulation identifier corresponding to the data packet / data packet and the corresponding QoS information.

[0572] S1510: The UE completes the remaining PDU session establishment or modification process.

[0573] S1511, a QUIC tunnel is established between the UPF network element and the SEALDD server.

[0574] S1512: The VAL server sends a data packet set to the SEALDD server.

[0575] S1513, the SEALDD server encapsulates the data packet set according to the QUIC encapsulation identifier of the data packet set.

[0576] For example, the SEALDD server can determine the data packet set of the downlink service flow (such as determining which data packets belong to data packet set #1) based on the service flow protocol description information of the VAL server, and then encapsulate the data packet set based on the QUIC encapsulation identifier of the data packet set.

[0577] S1514, the SEALDD server sends the encapsulated data packet set to the UPF network element.

[0578] S1515, the UPF network element maps the data packet set to the QoS flow based on the QUIC encapsulation identifier in the data packet set and the QFI of the corresponding QoS flow.

[0579] When the UPF network element receives a data packet set, it can perform QUIC packet detection and QFI marking on the data packet set based on the PDR rule, that is, it can determine the QUIC encapsulation identifier in the data packet set, and map the data packet set with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0580] In the embodiments of the present application, the message carrying multiple data information, such as service flow information, QUIC encapsulation identifier, QoS flow identifier, second connection information, second IP information, etc., is only used as an example and is not limited thereto. For example, in S1202, the service flow information can be carried by the VAL server sending a service subscription request message to the SEALDD server; or, the service flow information can be carried by other messages.

[0581] The above description of the data transmission method provided by the embodiment of the present application is described in conjunction with Figures 1 to 15. The following description of the device embodiment of the embodiment of the present application is described in conjunction with Figures 16 to 21. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, please refer to the description above.

[0582] Figure 16 is a schematic block diagram of a data processing device provided in an embodiment of the present application. The device 2000 includes an acquisition unit 2010, a processing unit 2010, and a sending unit 2020. The acquisition unit 2010 is used to acquire data, the processing unit 2020 is used to process data, and the sending unit 2030 can implement corresponding communication functions.

[0583] An acquiring unit 2010 is configured to acquire transmission requirement information of a plurality of data, wherein one of the plurality of data is a service flow or a data packet set, and the data packet set includes at least one data packet;

[0584] A processing unit 220 is configured to determine a QUIC encapsulation identifier for the plurality of data based on the transmission requirement information of the plurality of data, where the transmission requirement information of the plurality of data corresponds to the QUIC encapsulation identifier of the plurality of data;

[0585] The sending unit 2030 is used to send the QUIC encapsulation identifier of the multiple data to the first network element, and the QUIC encapsulation identifier of the multiple data is used to determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0586] In some embodiments, the multiple data include a first business flow and a second business flow, and the processing unit 2020 is further used to: when the transmission requirement information of the first business flow and the second business flow is the same, determine that the QUIC encapsulation identifier of the first business flow and the second business flow is the first encapsulation identifier; or, when the transmission requirement information of the first business flow and the second business flow is different, determine that the QUIC encapsulation identifiers of the first business flow and the second business flow are the second encapsulation identifier and the third encapsulation identifier, respectively.

[0587] In some embodiments, the multiple data include a first data packet set and a second data packet set of the same business flow, and the processing unit 2020 is further used to: when the transmission requirement information of the first data packet set and the second data packet set is the same, determine that the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the first encapsulation identifier; or, when the transmission requirement information of the first data packet set and the second data packet set is different, determine that the QUIC encapsulation identifiers of the first data packet set and the second data packet set are the second encapsulation identifier and the third encapsulation identifier, respectively.

[0588] In some embodiments, the device 2000 also includes a receiving unit 2040, which is used to: receive information about the multiple data from the application server, the information about the multiple data includes transmission requirement information of the multiple data; or, the receiving unit 2040 is used to receive information about the multiple data from the application server, the information about the multiple data includes description information of the multiple data and / or transmission requirement information corresponding to the description information; the processing unit 2030 is used to determine the transmission requirement information of the multiple data based on the information about the multiple data.

[0589] In some embodiments, the QUIC encapsulation identifier of multiple data includes information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or, the QUIC encapsulation identifier of multiple data includes an IP address and port number that can be assigned by the transmission server, and / or, an IP address and port number that can be assigned by the transmission client.

[0590] In some embodiments, the processing unit 2020 is used to: determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the first connection information; or determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the second connection information; or determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data, the first connection information and the second connection information, wherein the first connection information is information that can be assigned by the transmission server to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be assigned by the transmission server and / or other information representing the QUIC connection, and the second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes the QUIC connection identifier that can be assigned by the transmission client and / or other identifiers representing the QUIC connection.

[0591] In some embodiments, the receiving unit 2040 is further configured to receive second connection information sent from the transmission client.

[0592] In some embodiments, the processing unit 2020 is used to: determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the first IP information; or, determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data and the second IP information; or, determine the QUIC encapsulation identifier of multiple data based on the transmission requirement information of multiple data, the first IP transmission information and the second IP information, wherein the first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0593] In some embodiments, the receiving unit 2040 is further configured to receive second IP information sent from the transmission client.

[0594] In some embodiments, the QUIC encapsulation identification of the plurality of data includes information in a QUIC tunnel header.

[0595] In some embodiments, the sending unit 2030 is used to: send transmission requirement information of multiple data to the first network element.

[0596] In some embodiments, the receiving unit 2040 is further used to: receive multiple data from the application server, where the multiple data are downlink data; and encapsulate the multiple data using the QUIC encapsulation identifier of the multiple data to obtain the encapsulated multiple data.

[0597] In some embodiments, the sending unit 2030 is used to: send the encapsulated multiple data to the second network element to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data, and the second network element includes a network element responsible for the user plane function.

[0598] In some embodiments, the sending unit 2030 is used to: send a QUIC encapsulation identifier of multiple data to the transmission client, so that the transmission client uses the QUIC encapsulation identifier of the multiple data to encapsulate the multiple data, and the multiple data are uplink data.

[0599] In some embodiments, the application server comprises a VAL server.

[0600] In some embodiments, the transport client comprises a SEALDD client and the transport server comprises a SEALDD server.

[0601] In some embodiments, the first network element includes a network element responsible for session management, and the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of multiple data is determined by the first network element.

[0602] In some embodiments, the first network element includes a network element responsible for network capability exposure or a network element responsible for policy control.

[0603] Figure 17 is a schematic block diagram of a data processing device provided in an embodiment of the present application. The device 3000 includes a receiving unit 3010 and a processing unit 3020. The receiving unit 3010 can implement corresponding communication functions, and the processing unit 3020 is used to perform data processing.

[0604] a receiving unit 3010, configured to receive QUIC encapsulation identifiers of the multiple data sent by a transport server, where the QUIC encapsulation identifiers of the multiple data are determined based on transmission requirement information of the multiple data, where the transmission requirement information of the multiple data corresponds to the QUIC encapsulation identifiers of the multiple data, where one of the multiple data includes a service flow or a data packet set, and the data packet set includes at least one data packet;

[0605] A processing unit is used to determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data based on the QUIC encapsulation identifier of the multiple data.

[0606] In some embodiments, the multiple data include a first business flow and a second business flow, the QUIC encapsulation identifier of the first business flow and the second business flow is a first encapsulation identifier, and the transmission requirement information of the first business flow and the second business flow is the same, or the QUIC encapsulation identifier of the first business flow and the second business flow is a second encapsulation identifier and a third encapsulation identifier respectively, and the transmission requirement information of the first business flow and the second business flow is different.

[0607] In some embodiments, the multiple data include a first data packet set and a second data packet set of the same business flow, the QUIC encapsulation identifier of the first data packet set and the second data packet set is a first encapsulation identifier, and the transmission requirement information of the first data packet set and the second data packet set is the same, or the QUIC encapsulation identifier of the first data packet set and the second data packet set are a second encapsulation identifier and a third encapsulation identifier respectively, and the transmission requirement information of the first data packet set and the second data packet set is different.

[0608] In some embodiments, the information of multiple data includes transmission requirement information of multiple data, and the information of multiple data comes from an application server; or, the transmission requirement information of multiple data is determined based on the information of multiple data, and the information of multiple data includes description information of multiple data and / or transmission requirement information corresponding to the description information.

[0609] In some embodiments, the QUIC encapsulation identifiers of the multiple data include information that can be assigned by the transmission server and / or the transmission client to represent the QUIC connection; or, the QUIC encapsulation identifiers of the multiple data include an IP address and port number that can be assigned by the transmission server, and / or, an IP address and port number that can be assigned by the transmission client; or, the QUIC encapsulation identifiers of the multiple data include information in the QUIC tunnel header.

[0610] In some embodiments, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the first connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second connection information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first connection information and the second connection information, wherein the first connection information is information that can be assigned by the transmission server to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be assigned by the transmission server and / or other information representing the QUIC connection, and the second connection information is information that can be assigned by the transmission client to represent the QUIC connection, and the second connection information includes the QUIC connection identifier that can be assigned by the transmission client and / or other identifiers representing the QUIC connection.

[0611] In some embodiments, the second connection information comes from the transmission client.

[0612] In some embodiments, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the first IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data and the second IP information; or, the QUIC encapsulation identifier of the multiple data is determined based on the transmission requirement information of the multiple data, the first IP information and the second IP information, wherein the first IP information includes the IP address and port number assignable by the transmission server, and the second IP information includes the IP address and port number assignable by the transmission client.

[0613] In some embodiments, the second IP information comes from the transmission client.

[0614] In some embodiments, the receiving unit 3020 is further used to: receive transmission requirement information of the multiple data sent by the transmission server.

[0615] In some embodiments, the application server comprises a VAL server.

[0616] In some embodiments, the transport client comprises a SEALDD client and the transport server comprises a SEALDD server.

[0617] In some embodiments, the apparatus 3000 further includes a sending unit 3030 for sending an identifier of a QoS flow corresponding to the QUIC encapsulation identifier of the multiple data to a second network element, where the second network element includes a network element responsible for user plane functions.

[0618] Figure 18 is a schematic block diagram of a data processing device provided in an embodiment of the present application. The device 4000 includes a receiving unit 4010 and a processing unit 4020. The receiving unit 4010 can implement corresponding communication functions, and the processing unit 4020 is used to perform data processing.

[0619] a receiving unit 4010 configured to receive the encapsulated multiple data sent by a transport server, where the encapsulated multiple data are obtained by encapsulating the multiple data using QUIC encapsulation identifiers of the multiple data, where the QUIC encapsulation identifiers of the multiple data are determined based on transmission requirement information of the multiple data, where the transmission requirement information of the multiple data corresponds to the QUIC encapsulation identifiers of the multiple data, where one of the multiple data includes a service flow or a data packet set, and where the data packet set includes at least one data packet;

[0620] The processing unit 4020 is used to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0621] In some embodiments, the receiving unit 4010 is further used to: receive an identifier of a QoS flow corresponding to a QUIC encapsulation identifier of the multiple data from a first network element, wherein the first network element includes a network element responsible for session management.

[0622] Figure 19 is a schematic block diagram of a data processing device provided in an embodiment of the present application. The device 5000 includes an acquisition unit 5010, a processing unit 5020, and a sending unit 5030. The acquisition unit 5010 is used to acquire the required data information, the processing unit 5020 is used to process the data, and the sending unit 5030 can implement the corresponding communication function.

[0623] An acquiring unit 5010 is configured to acquire a plurality of data, wherein one of the plurality of data is a service flow or a data packet set, the data packet set includes at least one data packet, and the plurality of data is uplink data; and

[0624] Obtaining QUIC encapsulation identifiers of multiple data, where the QUIC encapsulation identifiers of the multiple data are determined based on transmission requirement information of the multiple data, and there is a correspondence between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data;

[0625] The processing unit 5020 is configured to encapsulate the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data;

[0626] The sending unit 5030 is used to send the encapsulated multiple data to the user equipment to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0627] In some embodiments, the apparatus 5000 further includes a receiving unit 5040 for receiving the plurality of data from an application client.

[0628] In some embodiments, the receiving unit 5040 is further used to: receive the QUIC encapsulation identifier of the multiple data from the transmission server.

[0629] In some embodiments, the application client comprises a VAL client.

[0630] Figure 20 is a schematic block diagram of a data processing device provided in an embodiment of the present application. The device 6000 includes a receiving unit 6010 and a processing unit 6020. The receiving unit 6010 can implement corresponding communication functions, and the processing unit 6020 is used to perform data processing.

[0631] A receiving unit 6010 is configured to receive encapsulated multiple data sent by a transmission client, where the encapsulated multiple data are obtained by encapsulating the multiple data using QUIC encapsulation identifiers of the multiple data, where the QUIC encapsulation identifiers of the multiple data are determined based on transmission requirement information of the multiple data, where the transmission requirement information of the multiple data corresponds to the QUIC encapsulation identifiers of the multiple data, where one of the multiple data is a service flow or a data packet set, where the data packet set includes at least one data packet, and where the multiple data are uplink data;

[0632] The processing unit 6020 is used to map the encapsulated multiple data to the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0633] In some embodiments, the receiving unit 6010 is further used to: receive an identifier of a QoS flow corresponding to a QUIC encapsulation identifier of the multiple data from a first network element, where the first network element includes a network element responsible for network capability opening.

[0634] Figure 21 is a schematic block diagram of another data processing device according to an embodiment of the present application. The communication device 7000 shown in Figure 21 may include a communication interface 7100, a processor 7200, and a memory 7300. The communication interface 7100, the processor 7200, and the memory 7300 communicate with each other via an internal connection path. The memory 7300 is used to store instructions, and the processor 7200 is used to execute the instructions stored in the memory 7300 to control the communication interface 7100 to send and / or receive signals.

[0635] Optionally, the memory 7300 may be coupled to the processor 7200 via an interface, or may be integrated with the processor 7200 .

[0636] It should be noted that the communication interface 7100 uses a transceiver device such as, but not limited to, a transceiver to implement communication between the data processing device and other devices or a communication network. The communication interface 7100 may also include an input / output interface.

[0637] In some embodiments, the data processing device may be a transmission server.

[0638] In some embodiments, the data processing device may be the first network element mentioned above.

[0639] In some embodiments, the data processing device may be a second network element.

[0640] In some embodiments, the data processing device can transmit the client.

[0641] In some embodiments, the data processing device may be a user equipment.

[0642] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 7200 or by instructions in the form of software. The method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a storage medium mature in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 7300, and the processor 7200 reads the information in the memory 7300 and completes each step of the above method in conjunction with its hardware. To avoid repetition, it will not be described in detail here.

[0643] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0644] It should also be understood that in the embodiments of the present application, the memory may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the processor may also include non-volatile random access memory. For example, the processor may also store device type information.

[0645] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0646] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0647] As used in this specification, the terms "component," "module," "system," and the like are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or a computer. By way of illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. Components can communicate, for example, via local and / or remote processes based on signals having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and / or a network, such as the Internet interacting with other systems via signals).

[0648] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0649] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0650] 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 device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0651] 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, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

Claims

1. A method for data processing, characterized in that Including: Obtaining transmission requirement information of multiple data, where one of the multiple data is a data stream or a set of data packets, and the set of data packets includes at least one data packet; Determining QUIC encapsulation identifiers of the multiple data according to the transmission requirement information of the multiple data, and there is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data; Sending the QUIC encapsulation identifiers of the multiple data to a first network element, and the QUIC encapsulation identifiers of the multiple data are used to determine identifiers of QoS flows corresponding to the QUIC encapsulation identifiers of the multiple data.

2. The method according to claim 1, characterized in that, The multiple data includes a first service flow and a second service flow, and the determining the QUIC encapsulation identifiers of the multiple data according to the transmission requirement information of the multiple data includes: When the transmission requirement information of the first service flow and the second service flow is the same, determining the QUIC encapsulation identifiers of the first service flow and the second service flow as a first encapsulation identifier; or, When the transmission requirement information of the first service flow and the second service flow is different, determining the QUIC encapsulation identifiers of the first service flow and the second service flow as a second encapsulation identifier and a third encapsulation identifier respectively.

3. The method according to claim 1, wherein The multiple data includes a first set of data packets and a second set of data packets of the same service flow, and the determining the QUIC encapsulation identifiers of the multiple data according to the transmission requirement information of the multiple data includes: When the transmission requirement information of the first set of data packets and the second set of data packets is the same, determining the QUIC encapsulation identifiers of the first set of data packets and the second set of data packets as a first encapsulation identifier; or, When the transmission requirement information of the first set of data and the second set of data packets is different, determining the QUIC encapsulation identifiers of the first set of data packets and the second set of data packets as a second encapsulation identifier and a third encapsulation identifier respectively.

4. The method according to any one of claims 1 to 3, characterized in that, The obtaining the transmission requirement information of the multiple data includes: Receiving the information of the multiple data from an application server, where the information of the multiple data includes the transmission requirement information of the multiple data; or, Receiving the information of the multiple data from the application server, where the information of the multiple data includes the description information of the multiple data and / or the transmission requirement information corresponding to the description information; Determining the transmission requirement information of the multiple data according to the information of the multiple data.

5. The method according to any one of claims 1 to 4, characterized in that, The QUIC encapsulation identifiers of the multiple data include information that can be assigned by a transmission server and / or a transmission client to represent a QUIC connection; or, The QUIC encapsulation identifiers of the multiple data include the IP address and port number that can be assigned by the transmission server, and / or the IP address and port number that can be assigned by the transmission client.

6. The method according to claim 5, characterized in that, The determining the QUIC encapsulation identifiers of the multiple data according to the transmission requirement information of the multiple data includes: Determining the QUIC encapsulation identifiers of the multiple data according to the transmission requirement information of the multiple data and first connection information; or, Determine the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data and the second connection information; or, Determine the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data, the first connection information, and the second connection information, wherein the first connection information is information that can be allocated by the transmission server and is used to represent a QUIC connection, and the first connection information includes a QUIC connection identifier that can be allocated by the transmission server and / or other information representing a QUIC connection; the second connection information is information that can be allocated by the transmission client and is used to represent a QUIC connection, and the second connection information includes a QUIC connection identifier that can be allocated by the transmission client and / or other identifiers representing a QUIC connection.

7. The method according to claim 6, wherein Before determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data and the second connection information, or, before determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data, the first connection information, and the second connection information, the method further includes: Receiving the second connection information sent by the transmission client.

8. The method according to claim 5, characterized in that, The determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data includes: Determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data and the first IP information; or; Determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data and the second IP information; or, Determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data, the first IP information, and the second IP information, wherein the first IP information includes an IP address and a port number that can be allocated by the transmission server, and the second IP information includes an IP address and a port number that can be allocated by the transmission client.

9. The method according to claim 8, wherein Before determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data and the second IP information, or, before determining the QUIC encapsulation identifier of the multiple pieces of data according to the transmission requirement information of the multiple pieces of data, the first IP information, and the second IP information, the method further includes: Receiving the second IP information sent by the transmission client.

10. The method according to any one of claims 1 to 4, characterized in that The QUIC encapsulation identifier of the multiple pieces of data includes information in the QUIC tunnel header.

11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Sending the transmission requirement information of the multiple pieces of data to the first network element.

12. The method according to any one of claims 1 to 11, characterized in that, The method further includes: Receiving the multiple pieces of data from the application server, where the multiple pieces of data are downlink data; Encapsulating the multiple pieces of data by using the QUIC encapsulation identifier of the multiple pieces of data to obtain the encapsulated multiple pieces of data.

13. The method according to claim 12, characterized in that, The method further includes: Sending the encapsulated multiple pieces of data to a second network element to map the encapsulated multiple pieces of data into a QoS flow corresponding to the QUIC encapsulation identifier of the multiple pieces of data, where the second network element includes a network element responsible for user plane functions.

14. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Send the QUIC encapsulation identifier of the multiple data to the transport client, so that the transport client encapsulates the multiple data by using the QUIC encapsulation identifier of the multiple data, and the multiple data are uplink data.

15. The method according to claim 4 or 12, characterized in that The application server includes a VAL server.

16. The method according to any one of claims 5 to 9, characterized in that The transport client includes a SEALDD client, and the transport server includes a SEALDD server.

17. The method according to any one of claims 1 to 16, characterized in that, The first network element includes a network element responsible for session management, and the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data is determined by the first network element.

18. The method according to any one of claims 1 to 16, characterized in that The first network element includes a network element responsible for network capability opening or a network element responsible for policy control.

19. A method for data processing, characterized in that, Including: Receive the QUIC encapsulation identifier of the multiple data sent by the transport server. The QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data. There is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data. One piece of data in the multiple data includes a traffic flow or a packet set, and the packet set includes at least one packet. Determine the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data according to the QUIC encapsulation identifier of the multiple data.

20. The method according to claim 19, wherein The method further includes: Receive the transmission requirement information of the multiple data sent by the transport server.

21. The method according to claim 19 or 20, characterized in that, The method further includes: Send the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data to a second network element, and the second network element includes a network element responsible for user plane function.

22. A method for data processing, characterized in that, Including: Receive the encapsulated multiple data sent by the transport server. The encapsulated multiple data are obtained by encapsulating the multiple data by using the QUIC encapsulation identifier of the multiple data. The QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data. There is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data. One piece of data in the multiple data includes a traffic flow or a packet set, and the packet set includes at least one packet. Map the encapsulated multiple data into the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

23. The method according to claim 22, wherein Before mapping the encapsulated multiple data into the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data, the method further includes: Receive the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data from the first network element, where the first network element includes a network element responsible for session management.

24. A method for data processing, characterized in that, Including: Obtain multiple data. One piece of data in the multiple data is a traffic flow or a packet set, the packet set includes at least one packet, and the multiple data are uplink data. Obtain the QUIC encapsulation identifier of the multiple data. The QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data. There is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data. Encapsulate the multiple data according to the QUIC encapsulation identifier of the multiple data to obtain the encapsulated multiple data. Send the encapsulated multiple data to the user equipment to map the encapsulated multiple data into the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

25. The method according to claim 24, wherein The obtaining of the multiple data includes: Receiving the multiple data from the application client.

26. The method according to claim 24 or 25, characterized in that, The obtaining of the QUIC encapsulation identifier of the multiple data includes: Receiving the QUIC encapsulation identifier of the multiple data from the transport server.

27. The method according to claim 26, wherein The application client includes a VAL client.

28. A method for data processing, characterized in that, Including: Receiving the encapsulated multiple data sent by the transport client, where the encapsulated multiple data is obtained by encapsulating the multiple data using the QUIC encapsulation identifier of the multiple data, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data, there is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifier of the multiple data, one of the multiple data is a traffic flow or a packet set, the packet set includes at least one packet, and the multiple data is uplink data; Mapping the encapsulated multiple data into the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

29. The method according to claim 28, wherein Before mapping the encapsulated multiple data into the QoS flow of the multiple data, the method further includes: Receiving the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data from the first network element, where the first network element includes a network element responsible for network capability opening.

30. A data processing device, characterized in that, Including: At least one processor, where the at least one processor is coupled to the memory and is configured to read and execute instructions in the memory to perform the method according to any one of claims 1 to 29.

Images