Data processing method and device

Abstract

The invention provides a data processing method and device, and the method comprises the steps: obtaining the transmission demand information of a plurality of data, one of the plurality of data being a data stream or a data packet set, and the data packet set comprising at least one data packet; according to the transmission demand information of the multiple pieces of data, QUIC packaging identifiers of the multiple pieces of data are determined, and a corresponding relation exists between the transmission demand information of the multiple pieces of data and the QUIC packaging identifiers of the multiple pieces of data; and sending the QUIC packaging identifiers of the multiple pieces of data to a first network element, wherein the QUIC packaging identifiers of the multiple pieces of data are used for determining identifiers of QoS flows corresponding to the QUIC packaging identifiers of the multiple pieces of data. According to the data processing method and device provided by the invention, differentiated QoS control and processing can be carried out on the QUIC data packet, so that network resources can be reasonably utilized and scheduled, and the application experience is improved.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly, to a method and apparatus for data processing. Background Art

[0002] Currently, there are two changing trends in the data transmitted on the Internet. One is that due to the sensitivity of many data to latency, there are more and more low-latency applications. The other is that due to the increasing attention paid to security and privacy issues, the proportion of encrypted traffic is increasing, and the proportion of encrypted traffic has increased to nearly 90%. Traditional Internet traffic transmission based on the Transmission Control Protocol (TCP) has problems such as large connection establishment latency and head-of-line blocking, and it is difficult to meet the low-latency requirements of current Internet applications.

[0003] Therefore, the Quick UDP Internet Connection (QUIC) emerged as the times require. Based on UDP as the protocol foundation, it has the advantages of low connection latency, multi-stream multiplexing without head-of-line blocking, packet header protection and encryption, and seamless connection migration. In the process of QUIC data transmission, how to achieve reasonable scheduling of network resources is one of the problems to be solved urgently at present. Summary of the Invention

[0004] This application provides a method and apparatus for data processing, which can perform differentiated QoS control and processing on QUIC packets, so as to reasonably utilize and schedule network resources and improve the experience of applications.

[0005] In a first aspect, a method for data processing is provided, including: obtaining transmission requirement information of multiple data, where one of the multiple data is a data stream or a packet set, and the packet set includes at least one 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.

[0006] In an embodiment of the present application, the QUIC encapsulation identifiers corresponding to multiple data can be determined according to the transmission requirement information of the multiple data, and then the QUIC encapsulation identifiers of the multiple data are sent to a 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 differential QoS control and processing can be performed on the QUIC data packets. For example, priority scheduling is performed for QUIC data with high transmission requirements, and the scheduling priority of QUIC data packets with low transmission requirements is low, or selective packet loss processing can be performed under network congestion. It can reasonably utilize and schedule network resources and improve the application experience when network resources are limited.

[0007] In combination with the first aspect, in some implementation manners of the first aspect, the multiple data include a first service flow and a second service flow. 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.

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

[0009] In combination with the first aspect, in some implementation manners of the first aspect, the multiple data include a first data packet set and a second data packet set of the same service flow. 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 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 a first encapsulation identifier; or, when the transmission requirement information of the first data 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 a second encapsulation identifier and a third encapsulation identifier respectively.

[0010] In an embodiment of the present application, the QUIC encapsulation identifiers of multiple data packet sets can be determined according to the transmission requirement information of multiple data packet sets in a single data stream, so as to perform differential QoS control and processing on the multiple data packet sets, which can be applicable to the transmission scenarios of multiple data packet sets with different transmission requirements in a single service flow.

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

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

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

[0014] In combination with the first aspect, in certain implementations of the first aspect, determining the QUIC encapsulation identifier of multiple data according to the transmission requirement information of multiple data includes: determining the QUIC encapsulation identifier of multiple data according to the transmission requirement information of multiple data and first connection information; or, determining the QUIC encapsulation identifier of multiple data according to the transmission requirement information of multiple data and second connection information; or, determining the QUIC encapsulation identifier of multiple data according to the transmission requirement information of multiple data, first connection information, and second connection information, where the first connection information is information that can be assigned by a 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 representing a QUIC connection, and the second connection information is information that can be assigned by a 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 identifiers representing a QUIC connection.

[0015] In combination with the first aspect, in some implementations of the first aspect, before determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of the multiple data and the second connection information, or before determining the QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data, the first connection information, and the second connection information, the method further includes: receiving the second connection information sent by the transmission client.

[0016] In combination with the first aspect, in some implementations of the first aspect, determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of the multiple data includes: determining the QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data and the first IP information; or determining the QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data and the second IP information; or determining the QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data, the first IP transmission information, and the second IP information, where the first IP information includes the IP address and port number that can be allocated by the transmission server, and the second IP information includes the IP address and port number that can be allocated by the transmission client.

[0017] In combination with the first aspect, in some implementations of the first aspect, before determining the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of the multiple data and the second IP information, or before determining the QUIC encapsulation identifiers of the multiple data based on the transmission requirement information of the multiple data, the first IP information, and the second IP information, the method further includes: receiving the second IP information sent by the transmission client.

[0018] In combination with the first aspect, in some implementations of the first aspect, the QUIC encapsulation identifiers of multiple data include the information in the QUIC tunnel header.

[0019] In the embodiments of the present application, the identification information can also be the information in the QUIC tunnel header, and different methods can be flexibly selected as the QUIC encapsulation identifiers, which improves the diversity of the QUIC encapsulation identifiers.

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

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

[0022] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending the encapsulated multiple data to a second network element to map the encapsulated multiple data into QoS flows corresponding to the QUIC encapsulation identifiers of the multiple data, where the second network element includes a network element responsible for the user plane function.

[0023] In the embodiments of the present application, by sending the encapsulated multiple data to the second network element, the second network element can determine the QoS flow corresponding to the data according to the QUIC encapsulation identifier in the encapsulated data, thereby realizing differential QoS control and processing for multiple data with different transmission requirements.

[0024] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending the QUIC encapsulation identifiers of the multiple data to a transport client so that the transport client encapsulates the multiple data by using the QUIC encapsulation identifiers of the multiple data, where the multiple data are uplink data.

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

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

[0027] In combination with the first aspect, in some implementations of the first aspect, the method further 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 the multiple data is determined by the first network element.

[0028] In combination with the first aspect, in some implementations of the first aspect, the first network element includes a network element responsible for network capability open or a network element responsible for policy control.

[0029] In a second aspect, a data processing method is provided, including: receiving the QUIC encapsulation identifiers of multiple data sent by a transport server, where the QUIC encapsulation identifiers of the multiple data are 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 identifiers of the multiple data, and one data of the multiple data includes a service flow or a packet set, and the packet set includes at least one packet; determining 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.

[0030] In combination with the second aspect, in some implementations of the second aspect, the multiple data includes a first service flow and a second service flow. The QUIC encapsulation identifiers of the first service flow and the second service flow are the first encapsulation identifier, and the transmission requirement information of the first service flow and the second service flow is the same. Alternatively, the QUIC encapsulation identifiers of the first service flow and the second service flow are the second encapsulation identifier and the third encapsulation identifier respectively, and the transmission requirement information of the first service flow and the second service flow is different. In combination with the first aspect, in some implementations of the first aspect, the multiple data includes a first data packet set and a second data packet set of the same service flow. 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 is the same. Alternatively, 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.

[0031] In combination with the second aspect, in some implementations of the second aspect, the information of the multiple data includes the transmission requirement information of the multiple data, and the information of the multiple data comes from the application server; or, the transmission requirement information of the multiple data is determined according to the information of the multiple data, and 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.

[0032] In combination with the second aspect, in some implementations of the second aspect, the QUIC encapsulation identifier of the multiple data includes the information that can be assigned by the transmission server and / or the transmission client for representing the QUIC connection; or, the QUIC encapsulation identifier of the multiple data includes 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; or, the QUIC encapsulation identifier of the multiple data includes the information in the QUIC tunnel header.

[0033] In combination with the second aspect, in some implementations of the second aspect, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data and the first connection information; or, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data and the second connection information; or, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data, the first connection information and the second connection information, where the first connection information is the information that can be assigned by the transmission server for representing 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 the information that can be assigned by the transmission client for representing 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.

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

[0035] In combination with the second aspect, in some implementations of the second aspect, the QUIC encapsulation identifier of multiple data is determined according to the transmission requirement information of the multiple data and the first IP information; or, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data and the second IP information; or, the QUIC encapsulation identifier of the multiple data is determined according to the transmission requirement information of the multiple data, the first IP information and the second IP information, where the first IP information includes the IP address and port number that can be allocated by the transport server, and the second IP information includes the IP address and port number that can be allocated by the transport client.

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

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

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

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

[0040] In combination with the second aspect, in some implementations of the second aspect, the method further includes: sending the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of multiple data to a second network element, where the second network element includes a network element responsible for the user plane function.

[0041] In a third aspect, a method for data processing is provided, including: receiving multiple encapsulated data sent by a transport server, where the multiple encapsulated data is obtained by encapsulating 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, and one piece of data in the multiple data includes a service flow or a packet set, and the packet set includes at least one packet; mapping the multiple encapsulated data into the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

[0042] In combination with the third aspect, in some implementation manners 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 further includes: receiving the identifier of the QoS flow corresponding to the QUIC encapsulation identifier of the multiple data from a first network element, where the first network element includes a network element responsible for session management.

[0043] In combination with the third aspect, in some implementation manners of the third aspect, the multiple data includes a first service flow and a second service flow, the QUIC encapsulation identifiers of the first service flow and the second service flow are a first encapsulation identifier, and the transmission requirement information of the first service flow and the second service flow is the same, or, the QUIC encapsulation identifiers of the first service flow and the second service flow are a second encapsulation identifier and a third encapsulation identifier respectively, and the transmission requirement information of the first service flow and the second service flow is different. In combination with the first aspect, in some implementation manners of the first aspect, the multiple data includes a first data packet set and a second data packet set of the same service flow, the QUIC encapsulation identifiers of the first data packet set and the second data packet set are 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 identifiers 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.

[0044] In combination with the third aspect, in some implementation manners of the third aspect, the transmission requirement information of the multiple data is determined according to the information of the multiple data, the information of the multiple data includes the description information of the multiple data, or, 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, the description information includes descriptor information and / or protocol description information, and the information of the multiple data comes from an application server.

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

[0046] In combination with the third aspect, in some implementation manners of the third aspect, the QUIC encapsulation identifiers of multiple data are determined according to the transmission requirement information of the multiple data and the first connection information; or, the QUIC encapsulation identifiers of the multiple data are determined according to the transmission requirement information of the multiple data and the second connection information; or, the QUIC encapsulation identifiers of the multiple data are determined according to the transmission requirement information of the multiple data, the first connection information and the second connection information, where the first connection information is the information that can be allocated by the transmission server and is used to represent the QUIC connection, the first connection information includes the QUIC connection identifier that can be allocated by the transmission server and / or other information representing the QUIC connection, the second connection information is the information that can be allocated by the transmission client and is used to represent the QUIC connection, and the second connection information includes the QUIC connection identifier that can be allocated by the transmission client and / or other identifiers representing the QUIC connection.

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

[0048] In combination with the third aspect, in some implementation manners of the third aspect, the QUIC encapsulation identifiers of multiple data are determined according to the transmission requirement information of the multiple data and the first IP information; or, the QUIC encapsulation identifiers of the multiple data are determined according to the transmission requirement information of the multiple data and the second IP information; or, the QUIC encapsulation identifiers of the multiple data are determined according to the transmission requirement information of the multiple data, the first IP information and the second IP information, where the first IP information includes the IP address and port number that can be allocated by the transmission server, and the second IP information includes the IP address and port number that can be allocated by the transmission client.

[0049] In combination with the third aspect, in some implementation manners of the third aspect, the second IP information comes from the transmission client.

[0050] In combination with the third aspect, in some implementation manners of the third aspect, the application server includes a VAL server.

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

[0052] Fourth aspect, a data processing method is provided, including: obtaining a plurality of data, where 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; obtaining the QUIC encapsulation identifier of the plurality of data, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data, and there is a corresponding relationship between the transmission requirement information of the plurality of data and the QUIC encapsulation identifier of the plurality of data; encapsulating the plurality of data according to the QUIC encapsulation identifier of the plurality of data to obtain the encapsulated plurality of data; sending the encapsulated plurality of data to a user device to map the encapsulated plurality of data into the QoS flow corresponding to the QUIC encapsulation identifier of the plurality of data.

[0053] In an embodiment of the present application, based on the QUIC encapsulation identifier corresponding to a plurality of data that has a corresponding relationship with the transmission requirement information, the plurality of data can be encapsulated, and then the encapsulated data can be mapped to the QoS flow corresponding to the QUIC encapsulation identifier, so that differential QoS control and processing of QUIC data packets can be realized. For example, priority scheduling can be performed for QUIC data with high transmission requirements, and the scheduling priority of QUIC data packets with low transmission requirements is low, or selective packet loss processing can be performed under network congestion. It can reasonably utilize and schedule network resources and improve the application experience when network resources are limited.

[0054] Combined with the fourth aspect, in some implementation manners of the fourth aspect, obtaining a plurality of data includes: receiving a plurality of data from an application client.

[0055] Combined with the fourth aspect, in some implementation manners of the fourth aspect, obtaining the QUIC encapsulation identifier of the plurality of data includes: receiving the QUIC encapsulation identifier of the plurality of data from a transmission server.

[0056] Combined with the fourth aspect, in some implementation manners of the fourth aspect, the application client includes a VAL client.

[0057] Fifth aspect, a data processing method is provided, including: receiving the encapsulated plurality of data sent by a transmission client, the encapsulated plurality of data is obtained by encapsulating a plurality of data using the QUIC encapsulation identifier of the plurality of data, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data, and there is a corresponding relationship between the transmission requirement information of the plurality of data and the QUIC encapsulation identifier of the plurality of data, 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; mapping the encapsulated plurality of data into the QoS flow corresponding to the QUIC encapsulation identifier of the plurality of data.

[0058] In combination with the fifth aspect, in some implementations of the fifth aspect, before mapping the encapsulated multiple data into the QoS flows 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 a first network element, where the first network element includes a network element responsible for network capability open.

[0059] In a sixth aspect, there is provided an apparatus for data processing, including: a processing unit, configured to determine the transmission requirement information of multiple data, where one of the multiple data is a service flow or a packet set, and the packet set includes at least one packet; and, according to the transmission requirement information of the multiple data, determine the QUIC encapsulation identifier 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; a sending unit, configured to send the QUIC encapsulation identifier of the multiple data to a 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.

[0060] In a seventh aspect, there is provided an apparatus for data processing, including: a receiving unit, configured to receive the QUIC encapsulation identifier of multiple data sent by a transmission server, where the QUIC encapsulation identifier of the multiple data is determined 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 identifier of the multiple data, and one of the multiple data includes a service flow or a packet set, and the packet set includes at least one packet; a processing unit, configured to 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.

[0061] In an eighth aspect, there is provided an apparatus for data processing, including: a receiving unit, configured to receive the encapsulated multiple data sent by a transmission server, where the encapsulated multiple data is obtained by encapsulating the multiple data by using the QUIC encapsulation identifier of the multiple data, and the QUIC encapsulation identifier of the multiple data is determined 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 identifier of the multiple data, and one of the multiple data includes a service flow or a packet set, and the packet set includes at least one packet; a processing unit, configured to map the encapsulated multiple data into the QoS flows corresponding to the QUIC encapsulation identifier of the multiple data.

[0062] In a ninth aspect, a data processing apparatus is provided, including: an acquisition unit configured to acquire a plurality of data, one of the plurality of data being a service flow or a packet set, the packet set including at least one packet, and the plurality of data being uplink data; and, acquire a QUIC encapsulation identifier of the plurality of data, the QUIC encapsulation identifier of the plurality of data being determined according to transmission requirement information of the plurality of data, there being a corresponding relationship between the transmission requirement information of the plurality of data and the QUIC encapsulation identifier of the plurality of data; a processing unit configured to encapsulate the plurality of data according to the QUIC encapsulation identifier of the plurality of data to obtain the encapsulated plurality of data; a sending unit configured to send the encapsulated plurality of data to a user equipment, so as to map the encapsulated plurality of data into a QoS flow corresponding to the QUIC encapsulation identifier of the plurality of data.

[0063] In a tenth aspect, a data processing apparatus is provided, including: a receiving unit configured to receive the encapsulated plurality of data sent by a transmission client, the encapsulated plurality of data being obtained by encapsulating the plurality of data by using the QUIC encapsulation identifier of the plurality of data, the QUIC encapsulation identifier of the plurality of data being determined according to transmission requirement information of the plurality of data, there being a corresponding relationship between the transmission requirement information of the plurality of data and the QUIC encapsulation identifier of the plurality of data, one of the plurality of data being a service flow or a packet set, the packet set including at least one packet, and the plurality of data being uplink data; a processing unit configured to map the encapsulated plurality of data into a QoS flow corresponding to the QUIC encapsulation identifier of the plurality of data.

[0064] In an eleventh aspect, a computer-readable medium is provided, the computer-readable medium storing program code, when the computer program code runs on a computer, causing the computer to execute the method described in any possible implementation manner of the first aspect to the fifth aspect as described above.

[0065] In a twelfth aspect, a communication apparatus is provided, which includes: at least one processor, the at least one processor being coupled to a memory and configured to read and execute instructions in the memory to execute the method described in any possible implementation manner of the first aspect to the fifth aspect as described above. Description of the Drawings

[0066] Figure 1 is an architecture diagram of a 5G mobile communication system provided by an embodiment of the present application.

[0067] Figure 2 is a schematic diagram of an architecture of 5G QoS provided by an embodiment of the present application.

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

[0069] Figure 4 It is a schematic diagram of the encryption of the QUIC protocol provided by an embodiment of the present application.

[0070] Figure 5 It is a schematic diagram of the architecture for QoS processing with PDU Set as the granularity provided by an embodiment of the present application.

[0071] Figure 6 It is a schematic diagram of the architecture of the SEALDD enhancement layer provided by an embodiment of the present application.

[0072] Figure 7 It is a schematic diagram of the data processing of the SEALDD enhancement layer provided by an embodiment of the present application.

[0073] Figures 8 to 15 It is a schematic diagram of the flow of the data processing method provided by an embodiment of the present application.

[0074] Figures 16 to 21 It is a schematic diagram of the device for data processing provided by an embodiment of the present application. Detailed implementation manners

[0075] Next, the technical solutions in the present application will be described with reference to the accompanying drawings.

[0076] Figure 1 It shows an architecture diagram of a 5G mobile communication system, including a user equipment (UE) 110, an access network (AN) 120, a core network (CN), and a data network (DN) 140. Among them, the main components of the architecture include the UE 110, the AN 120, and the 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. Figure 1 The shown network architecture may specifically include the following components:

[0077] UE 110: It is the entry point for the mobile user to interact with the network, capable of providing basic computing capabilities and storage capabilities, displaying service windows to the user, and accepting user operation inputs. The UE 110 will adopt the new air interface technology to establish a signal connection and a data connection with the AN 120, so as to transmit control signals and service data to the mobile network.

[0078] The user equipment in the embodiments of the present application may be referred to as a terminal device, a terminal, an access terminal, a user unit, a user station, a mobile station, a mobile device, a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. 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 devices connected to a wireless modem, a vehicle-mounted 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, etc., or a communication device such as a server, a gateway, a base station, a controller, or an Internet of Things (IoT) device, such as a sensor, a water meter, a water meter, etc. UE may also be a wired device, such as a computer, a laptop, etc. The embodiments of the present application do not limit this.

[0079] AN 120: Similar to the base station in a traditional network, it is deployed close to UE 110, provides network access functions for authorized users in a specific area, and can determine different quality transmission tunnels to transmit user data according to the user level, service requirements, etc. AN 120 can manage its own resources, make reasonable use of them, provide access services for UE 110 on demand, and is responsible for forwarding control signals and user data between the UE and the core network.

[0080] The access network can be an access network adopting different access technologies. There are currently two types of wireless access technologies: 3rd Generation Partnership Project (3GPP) access technologies (such as the wireless access technologies adopted in 3G, 4G, or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that comply with 3GPP standard specifications. An access network adopting 3GPP access technologies is called a Radio Access Network (RAN). Among them, the access network devices in the 5G system are called next generation Node Base stations (gNBs). Non-3GPP access technologies refer to access technologies that do not comply with 3GPP standard specifications. For example, the air interface technology represented by access points (APs) in Wi-Fi.

[0081] An access network that realizes the access network function based on wired communication technology can be called a wired access network.

[0082] An access network that realizes the access network function based on wireless communication technology can be called a radio access network (RAN). The radio access network can manage radio resources, provide access services for terminals, and then complete the forwarding of control signals and user data between the terminals and the core network.

[0083] Wireless access network devices can be, for example, base stations (NodeB), evolved NodeBs (eNB or eNodeB), base stations (gNB) in 5G mobile communication systems, base stations in future mobile communication systems, or APs in Wi-Fi systems, etc. It can also be a wireless controller in the scenario of a cloud radio access network (CRAN), or the access network device can be a relay station, access point, in-vehicle device, wearable device, and network devices in future 5G networks or network devices in future evolved PLMN networks, etc. The embodiments of the present application do not limit the specific technologies and specific device forms adopted by the wireless access network devices. It can be understood that all or part of the functions of the wireless access network devices in the present application can also be realized by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform).

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

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

[0086] To facilitate the understanding of the 5G network architecture, the core network of the 5G network architecture will be further elaborated below.

[0087] The control plane of the core network adopts a service-based architecture, and the interaction between control plane network elements uses the method of service invocation to replace the point-to-point communication method in the traditional architecture. In the service-based architecture, a control plane network element will open services to other control plane network elements for other control plane network elements to invoke; in point-to-point communication, there will be a set of specific messages for the communication interface between control plane network elements, which can only be used by the control plane network elements at both ends of the interface during communication. The functions of the functional network elements in the core network are as follows:

[0088] User plane function (UPF) network element 130: That is, the data plane gateway. It can be used for packet routing and forwarding, or quality of service (QoS) processing of user plane data, etc. User data can access DN 140 through this network element. In the embodiments of the present application, it can be used to implement the function of the user plane gateway.

[0089] Session Management Function (SMF) network element 150: It is mainly used for session management, allocation and management of the Internet Protocol (IP) address of UE 110, selection of manageable User Plane Functions, termination of policy control or charging function interfaces, and downlink data notification, etc. In the embodiments of this application, it can be used to implement the functions of the session management network element. It is mainly used for user plane network element selection, user plane network element redirection, IP address allocation of the terminal device, and establishment, modification and release of sessions as well as QoS control.

[0090] Access and Mobility Management Function (AMF) network element 160: It is mainly used for mobility management and access management, etc., and can be used to implement other functions of the Mobility Management Entity (MME) function except session management, such as lawful interception or access authorization (or authentication), etc. In the embodiments of this application, it can be used to implement the functions of the access and mobility management network element.

[0091] Authentication Server Function (AUSF) network element 170: It is mainly used for user authentication, etc.

[0092] Network Slice Selection Function (NSSF) network element 180: It is used to select a set of network slice instances serving UE 110, determine the allowed Network Slice Selection Assistance Information (NSSAI), etc.

[0093] Network Exposure Function (NEF) network element 190: It is used to securely expose the services and capabilities provided by 3GPP network functions to the outside.

[0094] Network Repository Function (NRF) network element 1100: It is used to save the description information of network function network elements and the services they provide, and support service discovery, network element discovery, etc.

[0095] Policy Control Function (PCF) network element 1110: It is a unified policy framework for guiding network behavior and provides policy rule information for control plane function network elements (such as AMF network element 160, SMF network element 150, etc.).

[0096] Unified Data Management (UDM) network element 1120: It is used to process user identification, access authentication, registration, or mobility management, etc.

[0097] Application Function (AF) network element 1130: It is used to perform data routing affected by applications, access network open function network elements, or interact with the policy framework for policy control, etc.

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

[0099] 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, and is used for the transmission of non-access stratum (NAS) messages, etc.; the N3 interface is the reference point between the AN 120 and the UPF network element 130, and is used for the transmission of user plane data, etc.; the N4 interface is the reference point between the SMF network element 150 and the UPF network element 130, and is used for the transmission of information such as tunnel identification information of the N3 connection, data caching indication information, and downlink data notification messages, etc.; the N6 interface is the reference point between the UPF network element 130 and the DN 140, and is used for the transmission of user plane data, etc.

[0100] In the 5G network, in order to ensure the Quality of Service (QoS) of services, a 5G QoS architecture based on QoS flows is proposed.

[0101] The following combines Figure 2 to introduce the 5G QoS architecture provided by this application.

[0102] QoS is a guarantee mechanism for service transmission quality. Its purpose is to provide end-to-end service quality assurance for different requirements of various services. In a protocol data unit (PDU) session, a QoS flow is the smallest granularity for differentiating QoS. In the 5G system, a QoS flow is identified by a QoS flow identifier (QFI), and the QFI must be unique within a PDU session. That is to say, 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 traffic flows with the same QFI use the same traffic forwarding processing method (such as scheduling).

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

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

[0105] Figure 3 It is a schematic diagram of the mapping of 5G QoS flows provided by the embodiments of this application. The 5GC and the AN ensure service quality by mapping data packets to appropriate QoS flows and DRBs.

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

[0107] UPF mapping: After receiving downlink data, the UPF uses a packet detection rule (PDR) and a QoS enforcement rule (QER) to map it to the corresponding QoS flow. Then it executes the QoS control of the QoS flow and marks the data with the QFI. The data is sent to the AN through the N3 interface corresponding to the QoS flow.

[0108] AN mapping: After receiving downlink data, the AN determines the DRB corresponding to the QFI. Then it executes the QoS control corresponding to the QoS flow and sends the data to the UE through the DRB. Alternatively, after receiving uplink data, the AN determines the QoS flow corresponding to the QFI. Then it executes the QoS control corresponding to the QoS flow and sends the data to the UPF through the N3 interface corresponding to the QoS flow.

[0109] UE Mapping: When the UE needs to send uplink data, it maps the data to the corresponding QoS flow according to the QoS rules. Then, the uplink data is sent through the DRB corresponding to the QoS flow.

[0110] It should be understood that the SMF is responsible for the control of 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 configuration of the corresponding parameters for a QoS flow includes three parts:

[0111] 1. QoS Configuration (QoS profile): The SMF can provide the QoS configuration to the AN through the N2 interface or it can also be pre-configured in the AN.

[0112] It should be understood that the QoS configuration of a certain QoS flow can also be referred to as a QoS configuration file. The specific parameters of the QoS configuration are shown in Table 1.

[0113] Table 1 Specific Parameters of QoS Configuration

[0114] Specific Description of QoS Flow Parameters

[0115] 5G QoS Identifier

[0116] (5G QoS identity, 5QI) represents the radio characteristics of the QoS flow.

[0117] Each QoS flow has a 5QI.

[0118] Allocation and Retention Priority

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

[0120] Each QoS flow has an ARP.

[0121] It can be applied between different UEs or between QoS flows of a single UE.

[0122] Guaranteed Flow Bit Rate

[0123] (guaranteed flow bit rate, GFBR) represents the guaranteed data rate.

[0124] Only the Guaranteed Bit Rate (GBR) QoS flow has a GFBR, including uplink transmission and downlink transmission.

[0125] Maximum Flow Bit Rate

[0126] (maximum flow bit rate, MFBR) represents the maximum data rate.

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

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

[0129] Only GBR QoS flows have notification control.

[0130] Maximum packet loss rate

[0131] (maximum packet loss rate, MPLR) represents the maximum packet loss rate that a QoS flow can tolerate.

[0132] Only GBR QoS flows may provide MPLR.

[0133] Reflective QoS attribute

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

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

[0136] 5QI is a scalar used to index a 5G QoS characteristic. 5QI can be standardized, pre-configured, or dynamically defined. The attributes of 5QI are shown in Table 2 below.

[0137] Table 2 Attribute parameters of 5QI

[0138] 5QI attribute description

[0139] Resource type GBR, latency-critical GBR, or Non-GBR.

[0140] Priority Radio interface scheduling priority.

[0141] Applicable between UEs, or between individual QoS flows of a UE.

[0142] Packet delay budget For GBR QoS flows: Under the premise of meeting GFBR, the maximum delay that 98% of the packets should not exceed; For latency-critical GBR: Under the premise of meeting GBER, packets exceeding the data delay are considered lost.

[0143] Packet error rate The packet loss rate of GBR QoS flows.

[0144] The time period for the average window to calculate the GFBR and MFBR of the GBR QoS flow.

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

[0146] 2. QoS rule: The SMF can provide the QoS rule to the UE through the N1 interface. Alternatively, the UE can derive it through the QoS mechanism.

[0147] It should be understood that the UE performs the classification and marking of uplink user-plane data services, that is, maps the uplink data to the corresponding QoS flow according to the QoS rule. These QoS rules can be explicitly provided to the UE (that is, explicitly configured for the UE through signaling in the PDU session establishment / modification process); alternatively, they can also be pre-configured on the UE; or they can also be implicitly derived by the UE using the reflective QoS mechanism. The QoS rule has the following characteristics:

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

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

[0150] Each PDU session needs to be configured with a default QoS rule, and the default QoS rule is associated with a QoS flow.

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

[0152] Currently, there are two changing trends in the data transmitted by the network. One is that due to the sensitivity of many data to latency, there are more and more low-latency applications; the other is that due to the increasing attention paid to security and privacy issues, the proportion of encrypted data is getting larger and larger, and the traffic proportion of encrypted data has increased to nearly 90%. The traditional Internet traffic transmission based on the Transmission Control Protocol (TCP) has problems such as large connection establishment latency and head-of-line blocking, and it is difficult to meet the low-latency requirements of current Internet applications.

[0153] Therefore, the Quick UDP Internet Connection (QUIC) emerged as the times require, with UDP as the protocol foundation, aiming to solve problems such as large connection latency and head-of-line blocking in traditional TCP connections. The QUIC protocol has the following advantages:

[0154] Low connection latency: The traditional TCP protocol requires one round-trip time (RTT) when establishing a connection for the first time, and then a second RTT for key exchange negotiation of transport layer security (TLS), such as TLS 1.2. The QUIC protocol is based on the UDP transport protocol and the TLS 1.3 protocol, and conducts key exchange negotiation during the process of establishing a connection for the first time. Therefore, the QUIC protocol only requires 1 RTT for the first connection establishment and key exchange, and 0 RTT for subsequent connections, which can reduce the connection latency.

[0155] 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 orderly and accurately. However, if a certain 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 ensure the sequence of data packets, so there is no waiting for restoration when a data packet is lost, and thus there is no head-of-line blocking problem for data packets. In the QUIC protocol, there is no dependency relationship between multiple data packets, and it has the multi-stream multiplexing feature, that is, multiple traffic streams can exist on a QUIC connection, and there is no dependency relationship between multiple traffic streams.

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

[0157] Connection migration without awareness: The QUIC protocol is based on the connectionless UDP and the QUIC connection represented by the connection ID, and can support connection migration without awareness of the application. For example, when the application client switches from the cellular network to the wifi network, the five-tuple of the application connection changes, but the application connection ID remains unchanged. Therefore, the application client can maintain the connection state on the new five-tuple and achieve connection migration without awareness.

[0158] In the 5G QoS architecture, it is necessary for the UPF network element or the UE to detect data packets according to a data packet filter (filter) and perform QoS flow mapping. For example, the data packet filter is an IP quintuple, which includes the source / destination IP address, source / destination port number, and transport layer protocol type. For data packets of the same traffic flow (corresponding to the same quintuple), QoS flow mapping is performed in the 5G network. The same traffic flow corresponds to a QoS flow with the same QFI and has the same QoS control and processing.

[0159] For the transmission data of QUIC, due to multi-stream multiplexing, there are multiple different traffic flows in the data packets of the same IP quintuple. Generally, different traffic flows have different transmission requirements for the 5G network. This makes the current method of packet filtering and QoS flow mapping based on the above IP quintuple unable to provide differentiated QoS control and processing for the data transmission of QUIC.

[0160] In addition, emerging extended reality (XR) such as virtual reality (VR), augmented reality (AR), mixed reality (MR), and cloud gaming services have strict requirements for end-to-end latency, and the data processing corresponding to the upper-layer media service during encoding and transmission is no longer at the granularity of data packets. For example, when encoding at the media layer, media frames, slices, 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, slices, etc. Basic data units such as media frames and slices often contain multiple IP data packets (due to the limitation of the size of IP data packets). This basic data unit at the media service layer is called a protocol data unit set (PDU Set), which is the basic unit that the upper-layer service layer can process independently. Once a PDU data packet is lost or damaged, the entire PDU Set may be difficult to decode and display correctly.

[0161] Figure 5The figure shows an architecture diagram for QoS processing at the PDU Set granularity. The AF network element 510 provides the protocol format corresponding to the current XR service transmission to the 5G network. This protocol format includes the formats indicating the transport layer protocol (such as RTP, SRTP, etc.), the transport layer extension header (such as the 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, the PCF network element 540, and the SMF network element 550, and then performs the identification of 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 through the GTP-U (user plane part of GPRS tunnelling 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 the integrity transmission of the PDU set (if a certain data packet within the PDU set is discarded, the entire PDU set can be discarded, thereby reducing the waste of radio interface transmission resources), and the differential transmission of the PDU set (for the importance difference between PDU sets, different QoS processing is selected. For example, for PDU set data packets with high importance, they are preferentially scheduled at the radio interface, and for PDU set data packets with low importance, the scheduling priority at the radio interface is low; or when the radio interface network of the base station is congested, data packets of PDU sets with low importance can be selectively discarded, thereby reducing network congestion), etc.

[0162] There are assumed conditions for the UPF to identify and mark the PDU set through the transport protocol format, that is, the transport protocol (such as the transport layer protocol or the payload) of the XR service needs to be unencrypted. Therefore, the UPF network element can identify the PDU set through the transport protocol format. However, the QUIC service flow has data encryption attributes, that is, there are features such as header protection and payload encryption. Therefore, based on the QoS control method of the XR service transport protocol format, it is difficult for the UPF network element in the 5G network to identify the characteristics of data packets with encryption attributes (such as the importance difference between different data packets). Therefore, it is not applicable to the data transmission of QUIC.

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

[0164] In view of the above problems, the embodiments of the present application provide a method and device for data processing, which can perform differential QoS control and processing on QUIC data packets, so as to reasonably utilize and schedule network resources and improve the application experience.

[0165] The enhanced layer of service enabler architecture layer data delivery (SEALDD) can be applicable to the processing and transmission of QUIC data packets. The architecture of the SEALDD enhanced layer is introduced as follows. Figure 6 The architecture of the SEALDD enhanced layer is introduced.

[0166] The SEALDD enhanced layer (or data processing enhanced layer) includes a SEALDD client and a SEALDD server. Among them, the SEALDD client is deployed on the UE in the form of software or a system component, and the SEALDD server is deployed between the UPF network element and the application server (AS) or the vertical application layer server (VAL server) in the form of an independent or integrated server.

[0167] 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 the SEALDD server perform user plane data processing through the SEALDD-UU interface, and the SEALDD-UU interface is carried on the user plane session constructed by the 3GPP network system. The SEALDD servers interact through the SEALDD-E interface, such as providing control plane context transmission and forwarding of user plane data.

[0168] An AF network element, such as a SEALDD server, can perform control plane message interaction with the PCF network element of the 3GPP network system through the N33 / N5 interface. Among them, N33 is the interface between the AF network element and the NEF network element, and N5 is the interface between the AF network element and the PCF network element. The AF network element can achieve indirect communication with the PCF network element through the NEF network element. The SEALDD server can send an AF network element request or subscribe to notifications to the PCF network element through the N33 / N5 interface. On the other hand, the SEALDD server can perform user plane data processing with the UPF network element through the N6 interface.

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

[0170] For uplink data processing, the VAL client transmits data packets to the SEALDD client through the SEALDD-C interface. After the SEALDD client encapsulates the data packets, it sends them to the SEALDD server through the SEALDD-UU interface. After the SEALDD server parses / de-encapsulates the data packets, it sends them to the VAL server through the SEALDD-S interface. Downlink data processing is similar to uplink data processing. The VAL server transmits data packets to the SEALDD server through the SEALDD-S interface. After the SEALDD server encapsulates the data packets, it sends them to the SEALDD client through the SEADD-UU interface. After the SEALDD client parses / de-encapsulates the data packets, it sends them to the VAL client through the SEALDD-C interface.

[0171] Figure 8 It is a schematic diagram of the QUIC data processing method provided by the embodiment of this application.

[0172] S801, the transmission server obtains the transmission requirement information of multiple data.

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

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

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

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

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

[0178] For example, the above-mentioned first traffic flow and second traffic flow may both be uplink traffic flows, or may both be downlink traffic flows.

[0179] For another example, the multiple packet sets in one traffic flow may be multiple packet sets in an uplink traffic flow or multiple packet sets in a downlink traffic flow.

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

[0181] Exemplarily, for a set of data packets in the same traffic flow, the transmission server may receive information about multiple data sent by the application server, such as protocol description information, and the protocol description information may include transmission requirement information for the multiple data, such as importance information for the multiple data.

[0182] For example, the protocol description information may be an RTP extension header, and packets with higher importance may be marked in the extension header. For the PDU set importance (PSI) in the RTP extension header, values 0 - 15 may 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 PSI = 0 has the highest importance. Thus, based on this RTP extension header, the transmission server can obtain the transmission requirement information for 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.

[0183] In some embodiments, the transmission server may receive information about multiple data sent by the application server, and the information about the multiple data may include description information for the multiple data and / or transmission requirement information corresponding to the description information. Then, the transmission server may determine the transmission requirement information for the multiple data based on the information about the multiple data.

[0184] In some embodiments, the description information for the multiple data includes descriptor information for the multiple data and / or protocol description information for the multiple data.

[0185] Exemplarily, for multiple traffic flows, the transmission server may receive description information for multiple data sent by the application server, such as descriptor information and transmission requirement information corresponding to the description information. Then, based on the description information for the multiple data and the transmission requirement information corresponding to the description information, the transmission server may determine the transmission requirement information for the multiple data.

[0186] For example, the descriptor information for traffic flow #1 is IP quintuple #1, and IP quintuple #1 corresponds to transmission requirement #1; the descriptor information for traffic flow #2 is IP quintuple #2, and IP quintuple #2 corresponds to transmission requirement #2; the descriptor information for traffic flow #3 is IP quintuple #3, and IP quintuple #1 corresponds to transmission requirement #1. Then, it can be determined that both traffic flow #1 and traffic flow 3 correspond to transmission requirement #1, and traffic flow #2 corresponds to transmission requirement #2.

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

[0188] Exemplarily, for multiple data packet sets of the same service flow, the transmission server may receive description information of multiple data packet sets sent by the application server, such as flow protocol description information, and transmission requirement information corresponding to the description information, such as characteristic parameter information of the data packet set corresponding to the flow protocol description information. Then, based on the description information of multiple data, such as flow protocol description information, and transmission requirement information corresponding to the description information, such as characteristic parameter information of the data packet set, determine the transmission requirement information of multiple data packet sets.

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

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

[0191] In some embodiments, multiple data includes a first service flow and a second service flow. When the transmission requirement information of the first service flow and the second service flow is the same, determine the QUIC encapsulation identifier of the first service flow and the second service flow as the first encapsulation identifier; or, when the transmission requirement information of the first service flow and the second service flow is different, determine the QUIC encapsulation identifiers of the first service flow and the second service flow as the second encapsulation identifier and the third encapsulation identifier respectively.

[0192] 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 #2; service flow #3 corresponds to transmission requirement information #1. Then, the QUIC encapsulation identifiers corresponding to service flow #1 and service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 is encapsulation identifier #2.

[0193] In some embodiments, multiple data includes a first data packet set and a second data packet set in the same service flow. When the transmission requirement information of the first data packet set and the second data packet set is the same, determine the QUIC encapsulation identifier 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 set and the second data packet set is different, determine 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.

[0194] In the same service flow, the QUIC encapsulation identifiers of data packet sets with the same transmission requirement information are the same; the QUIC encapsulation identifiers of data packet sets with different transmission requirement information in the same service flow are different. For example, data packet set #1 corresponds to transmission requirement information #1; data packet set #2 corresponds to transmission requirement information #1; data packet set #3 corresponds to transmission requirement information #2. Then the QUIC encapsulation identifiers corresponding to data packet set #1 and data packet set #2 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to data packet set #3 can be encapsulation identifier #2.

[0195] In some embodiments, the QUIC encapsulation identifier may include: information for representing a QUIC connection, information in a QUIC tunnel header, information in an IP triple, or information in an IP quintuple.

[0196] That is to say, the information for representing a 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 triple can be used as the QUIC encapsulation identifier, or the information in the IP quintuple can be used as the QUIC encapsulation identifier.

[0197] The information for representing a QUIC connection includes at least one of the following: an assignable QUIC connection identifier of a transmission server, other identifiers for representing a QUIC connection other than the assignable QUIC connection identifier of the transmission server, an assignable QUIC connection identifier of a transmission client, or other identifiers for representing a QUIC connection other than the assignable QUIC connection identifier of the transmission server.

[0198] An IP triple may include information on an IP address, a protocol, and a port.

[0199] An IP quintuple may include information on a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol.

[0200] Exemplarily, the QUIC encapsulation identifier includes information for representing a QUIC connection that can be assigned by a transmission server and / or a transmission client.

[0201] That is, the information for representing a QUIC connection that can be assigned by a transmission server and / or a transmission client can be used as the QUIC encapsulation identifier.

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

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

[0204] Exemplarily, the QUIC encapsulation identifier of multiple data can be determined according to the transmission requirement information of the multiple data and the first connection information.

[0205] Exemplarily, the QUIC encapsulation identifier of multiple data can be determined according to the transmission requirement information of the multiple data and the second connection information.

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

[0207] For example, the QUIC encapsulation identifier of multiple data can be determined according to the transmission requirement information of the multiple data, the QUIC connection identifier allocated by the transmission server, and the QUIC connection identifier allocated by the transmission client.

[0208] Taking the QUIC encapsulation identifier of the following line data as an example, for different QUIC connections, the QUIC connection identifiers allocated by the transmission server are connection ID#1 and connection ID#2, and the QUIC connection identifiers allocated by the transmission client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifier can 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 the downstream data, the source connection identifier is the QUIC connection identifier allocated by the transmission server); the latter four QUIC encapsulation identifiers are composed of the source connection identifier and the destination connection identifier (for the downstream data, the destination connection is the QUIC connection identifier allocated by the transmission client, and the destination connection identifier).

[0209] 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 is encapsulation identifier #2. In this way, two can be selected from the above QUIC encapsulation identifiers 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>, and the QUIC encapsulation identifier corresponding to downlink service flow #2 can be <connection ID#2>.

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

[0211] Taking the QUIC encapsulation identifier of the uplink data as an example. For instance, for different QUIC connections, the QUIC connection identifiers that can be allocated by the transport client are connection ID#1 and connection ID#2, and the QUIC connection identifiers that can be allocated by the transport client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifier can 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 (for the uplink data, the source connection identifier is the QUIC connection identifier that can be allocated by the transport client); the latter four identifiers are composed of the source connection identifier and the destination connection identifier (for the uplink data, the destination connection is the QUIC connection identifier that can be allocated by the transport server).

[0212] If multiple uplink service flows correspond to multiple different transport requirement information, for example, uplink service flow #1 corresponds to transport requirement information #1, uplink service flow #2 corresponds to transport requirement #2, and uplink service flow #3 corresponds to transport 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 is encapsulation identifier #2. In this way, two can be selected from the above QUIC encapsulation identifiers as encapsulation identifier #1 and encapsulation identifier #2 respectively. For example, the QUIC encapsulation identifier of uplink service flow #1 and downlink service flow #3 can be <connectionID#3>, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be <connection ID#4>.

[0213] 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 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>, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be <connection ID#4,connection ID#1>.

[0214] Within the same QUIC connection, there is only one identifier obtained based on the QUIC connection identifiers that can be allocated by the transmission server and / or the transmission client. Therefore, new identifiers such as other information used to represent the QUIC connection need to be introduced and combined with this identifier for the QUIC encapsulation identifiers of data with multiple different transmission requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifiers of multiple data can be determined according to the transmission requirement information of multiple data, the QUIC connection identifiers that can be allocated by the transmission server and other information representing the QUIC connection, and the QUIC connection identifiers that can be allocated by the transmission client and other information representing the QUIC connection.

[0215] Taking the QUIC encapsulation identifier of the following line data as an example. For instance, within the same QUIC connection, the identifier obtained based on the QUIC connection identifiers that can be allocated by the transmission server and the transmission client is the connection ID. Other identifiers that the transmission server can allocate are ID#1 and ID#2, and other identifiers that the transmission client can allocate are ID#3 and ID#4. Then the encapsulation identifiers 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 source connection identifiers that can be allocated (for the downstream data, the other source connection identifiers are other information that the transmission server can allocate to represent the QUIC connection); the latter four identifiers are composed of the connection ID, other source connection identifiers, and other destination connection identifiers (for the downstream data, the other destination connection identifiers are other information that the transmission client can allocate to represent the QUIC connection).

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

[0217] 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 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>>, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be <connection ID + <ID#1, ID#4>>.

[0218] Taking the QUIC encapsulation identifier of uplink data as an example. For instance, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier assignable by the transmission server and / or transmission client is connection ID. Other identifiers that the transmission server can assign are ID#1 and ID#2, and other identifiers that the transmission client can assign are ID#3 and ID#4. Then the encapsulation identifiers 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 connection ID and other assignable source connection identifiers (for uplink data, the other source connection identifiers are other information assigned by the transmission client for representing the QUIC connection); the latter four identifiers are composed of connection ID, other source connection identifiers, and other destination connection identifiers (for uplink data, the other destination connection identifiers are other information assigned by the transmission server for representing the QUIC connection).

[0219] 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 is encapsulation identifier #2. In this way, two can be selected from the above QUIC encapsulation identifiers 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 <connectionID+ID#3>, and the QUIC encapsulation identifier corresponding to uplink service flow #2 can be <connection ID#4>.

[0220] 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 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>>, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be <connection ID+<ID#4,ID#1>>.

[0221] In some embodiments, the QUIC encapsulation identifiers of multiple data can be determined according to the transmission requirement information of the multiple data, as well as 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

[0222] That is, 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, can be used as the encapsulation identifier.

[0223] For example, the QUIC encapsulation identifiers of multiple data can be determined according to the transmission requirement information of the multiple data and the first IP information.

[0224] For example, the QUIC encapsulation identifiers of multiple data can be determined according to the transmission requirement information of the multiple data and the second IP information.

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

[0226] Taking the QUIC encapsulation identifier of the following line data as an example, the IP addresses and port numbers that can be allocated by the transmission server are <IP#1, port#1> and <IP#1, port#2>, and the IP addresses and port numbers that can be allocated by the transmission client are <IP#2, port#3> and <IP#2, port#4>. Then the QUIC encapsulation identifier can 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>], and [<IP#1, port#2>, <IP#2, port#4>]. The first two identifiers are composed of the source address and the source port number (for the downstream data, the source address and the source port number are the IP addresses and port numbers that can be allocated by the transmission server); the latter four identifiers are composed of the source address and the source port number, and the destination address and the destination port number (for the downstream data, the destination address and the destination port number are the addresses and port numbers that can be allocated by the transmission client).

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

[0228] 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 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 [<IP#1,port#1>,<IP#2,port#3>], and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be [<IP#1,port#1>,<IP#2,port#4>].

[0229] Taking the QUIC encapsulation identifier of uplink data as an example, the IP addresses and port numbers that can be allocated by the transmission server are <IP#1,port#1> and <IP#1,port#2>, and the IP addresses and port numbers that can be allocated by the transmission client are <IP#2,port#3> and <IP#2,port#4>. Then the QUIC encapsulation identifiers can 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 uplink data, the source address and source port number are the IP addresses and port numbers that can be allocated by the transmission client); the latter four identifiers are composed 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 addresses and port numbers that can be allocated by the transmission server).

[0230] If multiple uplink service flows correspond to multiple different transmission requirement messages, for example, uplink service flow #1 corresponds to transmission requirement message #1, uplink service flow #2 corresponds to transmission requirement #2, and uplink service flow #3 corresponds to transmission requirement message #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 can be selected from the above QUIC encapsulation identifiers 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].

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

[0232] In the embodiments of the present application, all QUIC encapsulation identifiers can be determined first, and then the corresponding QUIC encapsulation identifiers can be selected and determined from all the QUIC encapsulation identifiers based on data with different transmission requirements. Or, the corresponding QUIC encapsulation identifiers can also be directly determined based on data with different transmission requirements.

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

[0234] The encapsulation identifier can be encapsulated in the QUIC tunnel header (which can also be called the N6 tunnel header). For example, the transmission requirement message of the data is carried in the QUIC tunnel header, and the transmission requirement message of the data is directly used as the QUIC encapsulation identifier of the data.

[0235] 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 identifier for downlink service flow #1 and downlink service flow #3 can be transmission requirement information #1, and transmission requirement information #1 is carried in the QUIC tunnel header; the QUIC encapsulation identifier corresponding to downlink service flow #2 can be transmission requirement information #2, and transmission requirement information #2 is carried in the QUIC tunnel header.

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

[0237] S803, the transmission server sends the QUIC encapsulation identifiers of multiple data to the first network element.

[0238] Correspondingly, the first network element receives the QUIC encapsulation identifiers of multiple data.

[0239] In some embodiments, the transmission server can also send the transmission requirement information of multiple data to the first network element.

[0240] In some embodiments, the first network element determines 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.

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

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

[0243] For example, the identifier of the QoS flow may include a QoS level identifier (QoS class identifier, QCI), QFI, etc.

[0244] 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 corresponding to the data corresponding to the first encapsulation identifier and the second encapsulation identifier are determined to be a first QoS flow identifier and a second QoS flow identifier respectively. Alternatively, if the QUIC encapsulation identifier of the multiple data only includes the first encapsulation identifier, it is determined that the identifier of the QoS flow corresponding to the first encapsulation identifier is the first QoS flow identifier.

[0245] For example, the QUIC encapsulation identifiers of traffic flow #1 and traffic flow #3 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to traffic flow #2 may be encapsulation identifier #2. Then, the QFIs of the QoS flows of traffic flow #1 and traffic flow #3 are both QFI #1, that is, the QoS flows of traffic flow #1 and downlink traffic flow #3 are the same QoS flow; the QFIs of the QoS flow of traffic flow #2 are both QFI #2, that is, the QoS flows of traffic flow #1 and traffic flow #3 are different from the QoS flow of traffic flow #2.

[0246] For example, the QUIC encapsulation identifiers of packet set #1 and downlink packet set #3 may be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to packet set #2 may be encapsulation identifier #2. Then, the QFIs of the QoS flows of packet set #1 and packet set #3 are both QFI #1, that is, the QoS flows of packet set #1 and downlink packet set #3 are the same QoS flow; the QFIs of the QoS flow of packet set #2 are both QFI #2, that is, the QoS flows of packet set #1 and packet set #3 are different from the QoS flow of packet set #2.

[0247] In some embodiments, the first network element may include a network element responsible for policy control, a network element responsible for network capability opening, and so on.

[0248] For example, the first network element may be a PCF network element or a NEF network element. The PCF network element may generate policy and charging control (PCC) rules according to the QUIC encapsulation identifiers corresponding to multiple data and the transmission requirement information of the multiple data.

[0249] 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 may directly send the QUIC encapsulation identifiers of multiple data to it, or may 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 directly interact with the PCF network element; if the transmission server is an entity not trusted by the operator network, it needs to first interact with a network element responsible for network capability opening such as a NEF network element, and then the network element responsible for network capability opening interacts with the PCF network element.

[0250] Figure 9 Schematic diagram of the method for QUIC data processing provided by an embodiment of this application. Figure 9 In the method shown, 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.

[0251] S901, the transmission server receives information of multiple data from the application server.

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

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

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

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

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

[0257] For example, the above-mentioned first traffic flow and second traffic flow may both be uplink traffic flows, or may both be downlink traffic flows.

[0258] For another example, the multiple packet sets in one traffic flow may be multiple packet sets in an uplink traffic flow or multiple packet sets in a downlink traffic flow.

[0259] In some embodiments, the information of the multiple data may include transmission requirement information of the multiple data.

[0260] 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.

[0261] For example, the protocol description information may be an RTP extension header, and important packets may be marked in the extension header. For PDU set importance (PSI) in the RTP extension header, numerical values 0-15 may be used to represent the importance of the packet set. The smaller the numerical value, the higher the importance of the packet. The packet set corresponding to PSI being 0 has the highest importance. Thus, based on the RTP extension header, the transmission server can obtain the transmission requirement information of multiple packets.

[0262] In this way, based on this 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.

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

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

[0265] For different traffic flows, the transmission requirement information can include QoS requirement information, such as delay information or packet loss rate information, etc. For example, traffic flows with the same numerical value of QoS requirement information have the same QoS requirement information; or traffic flows with numerical values of QoS requirement information within a certain range have the same QoS requirement information.

[0266] Exemplarily, the information of multiple data can include the description information of multiple data such as the flow protocol and the characteristic parameter information of the data packet set corresponding to the description information.

[0267] S902. The transmission server determines the transmission requirement information of multiple data according to the information of multiple data.

[0268] For the case where the information of multiple data includes the transmission requirement information of multiple data, S902 can be omitted.

[0269] In some embodiments, the transmission server can receive the description information of multiple data and / or the 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 multiple data and / or the transmission requirement information corresponding to the description information.

[0270] Exemplarily, for multiple service flows, the transmission requirements information of multiple data can be determined according to the description information of the multiple service flows, such as descriptor information and the transmission requirements information corresponding to the description 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; the descriptor information of service flow #3 is IP quintuple #3, and IP quintuple #1 corresponds to transmission requirement #1. Then it can be determined that both service flow #1 and service flow 3 correspond to transmission requirement #1, and service flow #2 corresponds to transmission requirement #2.

[0271] Exemplarily, for multiple data packet sets of the same service flow, the transmission server can receive the description information of the multiple data packet sets sent by the application server, such as flow protocol description information and the transmission requirements information corresponding to the description information, such as the characteristic parameter information of the data packet set corresponding to the flow protocol description information. Then, based on the description information of the multiple data, such as flow protocol description information and the transmission requirements information corresponding to the description information, such as the characteristic parameter information of the data packet set, the transmission requirements information of the multiple data packet sets is determined.

[0272] S903a. The transmission server determines the QUIC encapsulation identifier of the multiple data according to the transmission requirements information of the multiple data, as well as the first connection information and / or the second connection information.

[0273] In some embodiments, the transmission server determines the first connection information.

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

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

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

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

[0278] The content of the first connection information, the second connection information, and determining the QUIC encapsulation identifier of the multiple data in S903a can refer to the relevant description in S802, and details are not described herein in this application.

[0279] 903b determines the QUIC encapsulation identifiers of multiple data based on the transmission requirement information of the multiple data, as well as the first IP information and / or the second IP information.

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

[0281] In some embodiments, the transmission server determines the first IP information.

[0282] The first IP information includes the IP address and port number that can be assigned by the transmission server.

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

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

[0285] The content of the first IP information, the second IP information in S903b, and the determination of the QUIC encapsulation identifiers of multiple data can refer to the relevant descriptions in S802, and the present application will not elaborate herein.

[0286] It should be understood that S903a and S903b are two different ways of determining the encapsulation identifier, and generally one of them is selected for the QUIC data processing provided by the embodiments of the present application. That is, execute S901 to S902, S903a, and S904 to S913, or execute S901 to S902, S903b, and S904 to S913.

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

[0288] Correspondingly, the PCF network element receives the QUIC encapsulation identifiers of multiple data.

[0289] The QUIC encapsulation identifiers of multiple data are used to determine the identifiers of the QoS flows corresponding to the QUIC encapsulation identifiers of multiple data.

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

[0291] If the multiple data are multiple downlink service flows, the transmission server may 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 a set of multiple downlink data packets in the same downlink service flow, the transmission server may send the QUIC encapsulation identifiers and transmission requirement information of the set of multiple downlink data packets to the PCF network element.

[0292] If multiple data are multiple uplink service flows, the transmission server may send the QUIC encapsulation identifiers and transmission requirement information of the multiple uplink service flows to the PCF network element. If multiple data are a set of multiple uplink data packets in the same uplink service flow, the transmission server may send the QUIC encapsulation identifiers and transmission requirement information of the set of multiple uplink data packets to the PCF network element.

[0293] The transmission server may directly send the QUIC encapsulation identifiers of multiple data to the PCF network element, or may 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 trusted for the 5G network, the transmission server may 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 trusted 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.

[0294] S905. The PCF network element determines the PCC rule according to the QUIC encapsulation identifiers and transmission requirement information of multiple data.

[0295] 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 may obtain: transmission requirement information #1 corresponding to uplink service flow #1, transmission requirement #2 corresponding to uplink service flow #2, and transmission requirement information #1 corresponding to uplink service flow #3; encapsulation identifier #1 corresponding to uplink service flow #1 and uplink service flow #3, and encapsulation identifier #2 corresponding to uplink service flow #2. The PCF network element may generate a PCC rule based on this information.

[0296] For another example, if multiple data are downlink data, including downlink data packet set #1, downlink data packet set #2, and downlink data packet set #3 of the same downlink service flow, the PCF network element may obtain: transmission requirement information #1 corresponding to downlink data packet set #1, transmission requirement #2 corresponding to downlink data packet set #2, and transmission requirement information #1 corresponding to downlink data packet set #3; encapsulation identifier #1 corresponding to downlink data packet set #1 and downlink data packet set #3, and encapsulation identifier #2 corresponding to downlink data packet set #2. The PCF network element may generate a PCC rule based on this information.

[0297] S906. The PCF network element sends the QUIC encapsulation identifiers and transmission requirement information of multiple data to the SMF network element.

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

[0299] S907. The SMF network element determines the identifiers of the QoS flows corresponding to the QUIC encapsulation identifiers of multiple data based on the QUIC encapsulation identifiers of the multiple data.

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

[0301] For example, the QUIC encapsulation identifiers of the uplink service flow #1 and the uplink service flow #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of the uplink service flow #2 is encapsulation identifier #2. Then, the QFIs of the QoS flows of the uplink service flow #1 and the uplink service flow #3 are both QFI #1, that is, the QoS flows of the uplink service flow #1 and the uplink service flow #3 are the same QoS flow; the QFI of the QoS flow of the uplink service flow #2 is QFI #2, that is, the QoS flows of the uplink service flow #1 and the uplink service flow #3 are different from the QoS flow of the uplink service flow #2.

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

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

[0304] S908. The SMF network element sends the identifiers of the QoS flows corresponding to the QUIC encapsulation identifiers of the multiple data to a second network element.

[0305] Among them, the multiple data are downlink data.

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

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

[0308] S911. The transport server receives multiple data sent by the application server.

[0309] Among them, the multiple data are downlink data.

[0310] In some embodiments, the multiple data include multiple downlink service flows. For example, the transport server may receive multiple downlink service flows from the application server.

[0311] In some embodiments, the multiple data packets are a set of multiple downlink data packets in the same downlink service flow, and each data packet set includes at least one data packet. The transport server may receive multiple data from the application server. For example, the transport server may receive a set of multiple downlink data packets in the same downlink service flow from the application server.

[0312] S912. The transport server encapsulates the multiple downlink data by using the QUIC encapsulation identifiers of the multiple downlink data to obtain the encapsulated multiple downlink data.

[0313] When the transport 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.

[0314] For example, the QUIC encapsulation identifier corresponding to the downlink service flow #2 (IP quintuple #2) may 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>.

[0315] S913. The transport server sends the encapsulated multiple downlink data to the second network element.

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

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

[0318] S914. The second network element maps the encapsulated multiple downlink data to the corresponding QoS flows according to the QUIC encapsulation identifiers in the encapsulated multiple downlink data.

[0319] Exemplarily, when the second network element receives the 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 QUIC 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).

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

[0321] For example, multiple downlink data are service flow #1, service flow #2, and service flow #3. The QUIC encapsulation identifiers 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 QFIs of the QoS flow with encapsulation identifier #1 are all QFI #1, and the QFIs of the QoS flow with encapsulation identifier #2 are all QFI #2. The UPF network element can determine that the QUIC encapsulation identifiers in the encapsulated service flow #1 and service flow #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated service flow #2 is encapsulation identifier #2. Then, service flow #1 and service flow #3 are mapped to the QoS flow with QFI #1, and service flow #2 is mapped to the QoS flow with QFI #2.

[0322] For example, multiple downlink data are packet set #1, packet set #2, and packet set #3 in the same service flow. The QUIC encapsulation identifiers 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 QFIs of the QoS flow with encapsulation identifier #1 are all QFI #1, and the QFIs of the QoS flow with encapsulation identifier #2 are all QFI #2. The UPF network element can determine that the QUIC encapsulation identifiers in the encapsulated packet set #1 and packet set #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated packet set #2 is encapsulation identifier #2. Then, packet set #1 and packet set #3 are mapped to the QoS flow with QFI #1, and packet set #2 is mapped to the QoS flow with QFI #2.

[0323] S915, the transport server sends the QUIC encapsulation identifiers of multiple data to the transport client.

[0324] The transport server sends the QUIC encapsulation identifiers of multiple uplink data to the transport client.

[0325] The transmission server can encapsulate multiple uplink data by using the QUIC encapsulation identifiers of the multiple uplink data.

[0326] In some embodiments, the application server includes a VAL server.

[0327] In some embodiments, the transmission client includes a SEALDD client.

[0328] In some embodiments, the transmission server includes a SEALDD server.

[0329] It should be understood that in steps S901 to S907, the multiple data can be uplink data, or can also be downlink data. In steps S907 to S912, the multiple data are downlink data. In step S913, the multiple data are uplink data.

[0330] The following combines Figure 10 and Figure 11 to give an exemplary introduction to the uplink QUIC data processing of the transmission client and the user equipment.

[0331] Figure 10 It is a schematic diagram of the method for uplink QUIC data processing provided by the embodiments of the present application.

[0332] S1001, the transmission client obtains multiple data.

[0333] Wherein, 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 are multiple uplink data.

[0334] In some embodiments, the multiple data include multiple uplink traffic flows.

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

[0336] In some embodiments, the transmission client can obtain multiple data from the application client.

[0337] 1002, the transmission client obtains the QUIC encapsulation identifiers of the multiple data.

[0338] In some embodiments, the transmission client receives the QUIC encapsulation identifiers of the multiple data sent by the transmission server. The QUIC encapsulation identifiers of the multiple data are determined by the transmission server. The content for the transmission server to determine the encapsulation identifiers can refer to the relevant description in S802, which is not elaborated herein.

[0339] S1003. The transport client encapsulates multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data.

[0340] When the transport client receives uplink data, it encapsulates the uplink data according to the corresponding QUIC encapsulation identifier of the uplink data.

[0341] For example, the QUIC encapsulation identifier corresponding to the uplink traffic flow #2 (IP five-tuple #2) is <connection ID#2>. The transport client encapsulates the uplink traffic flow #2 from the application client, and the encapsulated data carries the QUIC connection identifier <connection ID#2>.

[0342] S1004. The transport client sends the encapsulated multiple data to the user equipment.

[0343] Correspondingly, the user equipment receives the encapsulated multiple data.

[0344] S1005. The user equipment uses the QUIC encapsulation identifiers in the encapsulated multiple data to map the encapsulated multiple data to the corresponding QoS flows.

[0345] When the user equipment receives the encapsulated uplink data such as an uplink traffic flow, it can determine the QUIC encapsulation identifier in the uplink traffic flow. Then, the user equipment can map the encapsulated uplink traffic 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 traffic flow sent by the first network element such as the SMF network element.

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

[0347] For example, the multiple uplink data are traffic flow #1, traffic flow #2, and traffic flow #3. The QUIC encapsulation identifiers of traffic flow #1 and traffic flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to traffic flow #2 can be encapsulation identifier #2. Then, the QFIs of the QoS flows with encapsulation identifier #1 are all QFI#1, and the QFIs of the QoS flows with encapsulation identifier #2 are all QFI#2. The user equipment can determine that the QUIC encapsulation identifiers in the encapsulated traffic flow #1 and traffic flow #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated traffic flow #2 is encapsulation identifier #2. Then, it maps traffic flow #1 and traffic flow #3 to the QoS flow with QFI#1, and maps traffic flow #2 to the QoS flow with QFI#2.

[0348] For example, multiple uplink data are a set of packets #1, a set of packets #2, and a set of packets #3 in the same traffic flow. The QUIC encapsulation identifiers of the set of packets #1 and the set of packets #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to the set of packets #2 can be encapsulation identifier #2. Then, the QFIs of the QoS flow with encapsulation identifier #1 are all QFI #1, and the QFIs of the QoS flow with encapsulation identifier #2 are all QFI #2. The user equipment can determine that the QUIC encapsulation identifiers in the encapsulated set of packets #1 and the set of packets #3 are encapsulation identifier #1, and the QUIC encapsulation identifier of the encapsulated set of packets #2 is encapsulation identifier #2. Then, the set of packets #1 and the set of packets #3 are mapped to the QoS flow with QFI #1, and the set of packets #2 is mapped to the QoS flow with QFI #2.

[0349] Figure 11 It is a schematic diagram of the method for processing uplink QUIC data provided by the embodiments of the present application.

[0350] S1101. The transport client receives multiple data from the application client.

[0351] In some embodiments, the application client includes a VAL client.

[0352] In some embodiments, the transport client includes a SEALDD client.

[0353] In some embodiments, the multiple data include multiple uplink traffic flows. For example, the transport client can receive multiple uplink traffic flows from the application client.

[0354] In some embodiments, the multiple packets are multiple sets of uplink packets in the same uplink traffic flow, and each set of packets includes at least one packet. For example, the transport client can receive multiple sets of uplink packets in the same uplink traffic flow from the application client.

[0355] S1102. The transport client receives the QUIC encapsulation identifiers of the multiple data from the transport server.

[0356] The QUIC encapsulation identifiers of the multiple data are determined 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.

[0357] For the content determined by the transport server for the encapsulation identifier, reference can be made to the relevant description in S802, which will not be elaborated herein.

[0358] S1103. The transport client encapsulates the multiple data according to the QUIC encapsulation identifiers of the multiple data to obtain the encapsulated multiple data.

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

[0360] For example, the QUIC encapsulation identifier corresponding to the uplink 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>.

[0361] S1104, the transmission client sends the encapsulated multiple data to the user equipment.

[0362] Correspondingly, the user equipment receives the encapsulated multiple data.

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

[0364] 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 according to the QUIC encapsulation identifier of the multiple data.

[0365] For example, the identifier of the QoS flow can include QCI, QFI, etc.

[0366] S1106, the user equipment maps the encapsulated multiple data to the QoS flows of the multiple data according to the QUIC encapsulation identifier in the encapsulated multiple data.

[0367] Figure 12 It is a schematic diagram of the method for QUIC data processing provided by the embodiments of the present application. Among them, Figure 12 It is a scenario of multiple service flows.

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

[0369] Through the establishment of the PDU session, the network connection between the UE, RAN, UPF network element and DN is realized.

[0370] S1202, the VAL server sends a service subscription request message to the SEALDD server.

[0371] The request message includes information of multiple service flows. For example, the information of the service flow can include descriptor information of the service flow (such as IP quintuple information) and QoS information corresponding to the descriptor information, etc. Among them, the QoS information can include QoS requirement information and / or QoS importance information.

[0372] For example, 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; the descriptor information (IP quintuple #2) of service flow #2 corresponds to QoS information #2.

[0373] S1203, the SEALDD server sends a service subscription request response message to the VAL server.

[0374] S1204, the VAL client and the VAL server perform signaling negotiation to determine the data processing method between the VAL client and the VAL server.

[0375] For example, in the embodiments of this application, after signaling negotiation, it is determined to use the SEALDD enabling layer for QUIC data processing.

[0376] S1205, the VAL client sends a service request message to the SEALDD client.

[0377] S1206, the SEALDD client sends a connection or handshake request message to the SEALDD server.

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

[0379] In some embodiments, the content of the request message includes an IP address and / or port number that can be assigned by the SEALDD client.

[0380] S1207, the SEALDD server determines the QUIC encapsulation identifier corresponding to the service flow according to the QoS information corresponding to the service flow.

[0381] In some embodiments, the QUIC encapsulation identifier may include: information for representing a QUIC connection, information in an IP triple, or information in an IP quintuple.

[0382] That is to say, the information for representing a QUIC connection can be used as the encapsulation identifier, or the information in the IP triple can be used as the encapsulation identifier, or the information in the IP quintuple can be used as the encapsulation identifier.

[0383] The information for representing a QUIC connection includes an assignable QUIC connection identifier and other identifiers for representing a QUIC connection other than the assignable QUIC connection identifier.

[0384] An IP triple may include information on an IP address, a protocol, and a port.

[0385] The IP five-tuple may include information on the source IP address, source port, destination IP address, destination port, and transport layer protocol.

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

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

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

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

[0390] For example, the QUIC encapsulation identifiers of multiple traffic flows can be determined based on the transmission requirement information of the multiple traffic flows, the QUIC connection identifier assigned by the transport server, and the QUIC connection identifier assigned by the transport client.

[0391] Taking the QUIC encapsulation identifier of the following service flow as an example. For instance, for different QUIC connections, the QUIC connection identifiers that can be assigned by the transmission server are connection ID#1 and connection ID#2, and the QUIC connection identifiers that can be assigned by the transmission client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifiers can 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 (for the downstream service flow, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission server); the latter four identifiers are composed of the source connection identifier and the destination connection identifier (for the downstream service flow, the destination connection is the QUIC connection identifier that can be assigned by the transmission client).

[0392] If multiple downstream service flows correspond to multiple different transmission requirement information, such as downstream service flow #1 corresponding to transmission requirement information #1, downstream service flow #2 corresponding to transmission requirement #2, and downstream service flow #3 corresponding to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to downstream service flow #1 and downstream service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to downstream service flow #2 is 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 of downstream service flow #1 and downstream service flow #3

[0393] Taking the QUIC encapsulation identifier of the above upstream service flow as an example. For instance, for different QUIC connections, the QUIC connection identifiers that can be assigned by the transmission client are connection ID#1 and connection ID#2, and the QUIC connection identifiers that can be assigned by the transmission client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifiers can 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 upstream service flow, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission client); the latter four identifiers are composed of the source connection identifier and the destination connection identifier (for the upstream service flow, the destination connection is the QUIC connection identifier that can be assigned by the transmission server, the destination connection identifier).

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

[0395] 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, new identifiers such as other information representing the QUIC connection need to be introduced and combined with this identifier for the QUIC encapsulation identifiers of multiple service flows with different transmission requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifiers of multiple service flows can be determined according to the transmission requirement information of multiple service 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.

[0396] Taking the QUIC encapsulation identifier of the following service flow as an example. For instance, within the same QUIC connection, the identifier obtained based on the QUIC connection identifiers that can be allocated by the transmission server and the transmission client is the connection ID. Other identifiers that the transmission server can allocate are ID#1 and ID#2, and other identifiers that the transmission client can allocate are ID#3 and ID#4. Then the encapsulation identifiers 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 source connection identifiers that can be allocated (for the downstream service flow, the other source connection identifiers are other information that the transmission server can allocate to represent the QUIC connection). The following four identifiers are composed of the connection ID, other source connection identifiers, and other destination connection identifiers (for the downstream service flow, the other destination connection identifiers are other information that the transmission client can allocate to represent the QUIC connection).

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

[0398] Taking the QUIC encapsulation identifier of the above upstream service flow as an example, for instance, within the same QUIC connection, the identifier obtained based on the QUIC connection identifier that can be allocated by the transmission server and / or the transmission client is the connection ID. Other identifiers that the transmission server can allocate are ID#1 and ID#2, and other identifiers that the transmission client can allocate are ID#3 and ID#4. Then the encapsulation identifiers 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 source connection identifiers that can be allocated (for the upstream service flow, the other source connection identifiers are other information used by the transmission client to represent the QUIC connection); the latter four identifiers are composed of the connection ID, other source connection identifiers, and other destination connection identifiers (for the upstream service flow, the other destination connection identifiers are other information used by the transmission server to represent the QUIC connection).

[0399] If multiple upstream service flows correspond to multiple different transmission requirement information, for example, upstream service flow #1 corresponds to transmission requirement information #1, upstream service flow #2 corresponds to transmission requirement #2, and upstream service flow #3 corresponds to transmission requirement information #1, then the QUIC encapsulation identifiers corresponding to upstream service flow #1 and upstream service flow #3 can be encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to upstream service flow #2 can be encapsulation identifier #2. Thus, 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 of upstream service flow #1 and upstream service flow #3 can be <connectionID + ID#3>, and the QUIC encapsulation identifier corresponding to upstream service flow #2 can be <connection ID#4>.

[0400] In some embodiments, the QUIC encapsulation identifiers of multiple service flows can be determined according to the transmission requirement information, the first IP information, and / or the second IP information of the multiple service flows. Among them, the first IP information includes the IP address and port number that can be allocated by the transmission server, and the second IP information includes the IP address and port number that can be allocated by the transmission client

[0401] That is, the IP address and port number that can be allocated by the transmission server, and / or, the IP address and port number that can be allocated by the transmission client can be used as the encapsulation identifier.

[0402] Taking the QUIC encapsulation identifier of the following industry service flow as an example, the IP addresses and port numbers that can be allocated by the transmission server are <IP#1, port#1> and <IP#1, port#2>, and the IP addresses and port numbers that can be allocated by the transmission client are <IP#2, port#3> and <IP#2, port#4>. Then the QUIC encapsulation identifier can 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 the source port number (for downlink data, the source address and the source port number are the IP address and port number that can be allocated by the transmission server); the last four identifiers are composed of the source address and the source port number, and the destination address and the destination port number (for the downlink service flow, the destination address and the destination port number are the address and port number that can be allocated by the transmission client).

[0403] 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 is encapsulation identifier #2. In this way, two can be selected from the above QUIC encapsulation identifiers 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].

[0404] Taking the QUIC encapsulation identifier of the above upstream service flow as an example, the IP addresses and port numbers that the transmission server can allocate are <IP#1, port#1> and <IP#1, port#2>, and the IP addresses and port numbers that the transmission client can allocate are <IP#2, port#3> and <IP#2, port#4>. Then the QUIC encapsulation identifiers can 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>], and [<IP#2, port#4>, <IP#1, port#2>]. The first two identifiers are composed of the source address and source port number (for the upstream service flow, the source address and source port number are the IP addresses and port numbers that the transmission client can allocate); the latter four identifiers are composed of the source address and source port number, as well as the destination address and destination port number (for the upstream service flow, the destination address and destination port number are the addresses and port numbers that the transmission server can allocate).

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

[0406] In the embodiments of the present application, all QUIC encapsulation identifiers can be determined first, and then based on the service flows with different transmission requirements, the corresponding QUIC encapsulation identifiers are selected and determined from all the QUIC encapsulation identifiers. Alternatively, the corresponding QUIC encapsulation identifiers can also be directly determined based on the service flows with different transmission requirements.

[0407] S1208, the SEALDD server sends a connection / handshake response message to the SEALDD client.

[0408] In some embodiments, the content of the response message may include the upstream service flow information and its corresponding upstream QUIC encapsulation identifier, which are used for the SEALDD client to process the upstream service flow from the VAL client.

[0409] S1209, The SEALDD server sends the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information to the PCF.

[0410] The SEALDD server sends the QUIC encapsulation identifier corresponding to the uplink service flow and the corresponding QoS information (such as QoS importance information), and / or the QUIC encapsulation identifier corresponding to the downlink service flow and the corresponding QoS information (such as QoS importance information) to the PCF.

[0411] If the SEALDD server is trusted for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information to the PCF network element. If the SEALDD server is not trusted for the 5G network, it needs to send the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information to the PCF network element through the NEF network element.

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

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

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

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

[0416] 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.

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

[0418] 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.

[0419] 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 according to the QUIC encapsulation identifier corresponding to the service flow, that is, the QFI of the QoS flows of the service flows with the same QUIC encapsulation identifier is the same.

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

[0421] 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.

[0422] 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.

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

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

[0425] 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.

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

[0427] 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.

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

[0429] After the PDU session establishment or modification is completed, when the downlink service flow of the VAL server arrives, the SEALDD server encapsulates the downlink service flow based on the downlink QUIC encapsulation identifier determined by S1207.

[0430] For example, if the QUIC encapsulation identifier corresponding to the downlink service flow #1 is <connection ID#1>, the SEALDD server may encapsulate the service flow of IP quintuple #1 from the VAL server based on <connection ID#1> for the downlink QUIC data packet. That is, the QUIC connection identifier <connection ID#1> is carried in the QUIC data packet of the encapsulated downlink service flow.

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

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

[0433] S1218. The UPF network element maps the downstream service flow to a QoS flow according to the QUIC encapsulation identifier in the downstream service flow and the QFI of the QoS flow corresponding to the downstream service flow.

[0434] For example, when the UPF network element receives a downstream service flow, it can perform QUIC packet detection on the downstream service flow and the corresponding QFI marking 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 flows with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0435] S1219. The SEALDD client encapsulates the upstream service flow based on the upstream QUIC encapsulation identifier.

[0436] After the PDU session establishment or modification is completed, when the upstream service flow of the VAL client arrives, the SEALDD client encapsulates the upstream service flow based on the upstream QUIC encapsulation identifier obtained in S1208.

[0437] For example, if the upstream QUIC encapsulation identifier corresponding to the upstream service flow #3 is <connection ID#3>, the SEALDD client can encapsulate the service flow from the VAL client based on <connection ID#3> for the upstream QUIC packets. That is, the QUIC connection identifier <connection ID#3> is carried in the QUIC packets of the encapsulated upstream service flow.

[0438] S1220. The SEALDD client sends the encapsulated upstream service flow to the UE.

[0439] Correspondingly, the UE receives the encapsulated upstream service flow sent by the SEALDD client.

[0440] S1221. The UE maps the upstream service flow to a QoS flow according to the QUIC encapsulation identifier in the upstream service flow and the QFI of the QoS flow corresponding to the upstream service flow.

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

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

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

[0444] Implement the network connection from the UE to the RAN, to the UPF, and then to the DN.

[0445] S1302, the VAL server sends a service subscription request message to the SEALDD server.

[0446] The request message may include information about the service flow. For example, the information about the service flow may include the protocol description information of the service flow (the service flow uses the RTP protocol for transmission), or the information about the service flow may include the protocol description information of the service flow and the QoS information of the packet set corresponding to the protocol description information, etc. Among them, the QoS information may include QoS requirement information and / or QoS importance information.

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

[0448] S1303, the SEALDD server sends a service subscription request response message to the VAL server.

[0449] S1304, the VAL client and the VAL server perform signaling negotiation to determine the data processing method between the VAL client and the VAL server.

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

[0451] S1305, the VAL client sends a service request message to the SEALDD client.

[0452] S1306, the SEALDD client sends a connection or handshake request message to the SEALDD server.

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

[0454] S1307, the SEALDD server determines the QUIC encapsulation identifier corresponding to the packet set according to the QoS information corresponding to the packet set.

[0455] In some embodiments, the encapsulation identifier may include: information for representing a QUIC connection, information in a QUIC tunnel header, information in an IP triple, or information in an IP quintuple.

[0456] That is, the information for representing a QUIC connection may be used as the encapsulation identifier, or the information in the QUIC tunnel header may be used as the encapsulation identifier, or the information in the IP triple may be used as the encapsulation identifier, or the information in the IP quintuple may be used as the encapsulation identifier.

[0457] The information for representing a QUIC connection includes an assignable QUIC connection identifier and other identifiers for representing a QUIC connection other than the assignable QUIC connection identifier.

[0458] An IP triple may include information on an IP address, a protocol, and a port.

[0459] An IP quintuple may include information on a source IP address, a source port, a destination IP address, a destination port, and a transport layer protocol.

[0460] Exemplarily, the encapsulation identifier includes information assignable by a transport server and / or a transport client for representing a QUIC connection.

[0461] That is, the information assignable by a transport server and / or a transport client for representing a QUIC connection may be used as the encapsulation identifier.

[0462] In some embodiments, the transport server determines the QUIC encapsulation identifier of the multiple packet sets according to the transmission requirement information of the multiple packet sets, and the first connection information and / or the second connection information.

[0463] Wherein, the first connection information is information assignable by the transport server for representing a QUIC connection, and the first connection information includes an assignable QUIC connection identifier of the transport server and / or other information for representing a QUIC connection. The second connection information is information assignable by the transport client for representing a QUIC connection, and the second connection information includes an assignable QUIC connection identifier of the transport client and / or other information for representing a QUIC connection.

[0464] For example, the QUIC encapsulation identifier of the multiple packet sets may be determined according to the transmission requirement information of the multiple packet sets, the assignable QUIC connection identifier of the transport server, and the assignable QUIC connection identifier of the transport client.

[0465] Taking the QUIC encapsulation identifier of the following set of downlink data packets as an example. For different QUIC connections, the QUIC connection identifiers that can be assigned by the transmission server are connection ID#1 and connection ID#2, and the QUIC connection identifiers that can be assigned by the transmission client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifier can include <connectionID#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 set of downlink data packets, the source connection identifier is the QUIC connection identifier that can be assigned by the transmission server); the latter four identifiers are composed of the source connection identifier and the destination connection identifier (for the set of downlink data packets, the destination connection is the QUIC connection identifier that can be assigned by the transmission client).

[0466] If multiple sets of downlink data packets 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 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>, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be <connection ID#1,connection ID#4>.

[0467] Taking the QUIC encapsulation identifier of the above uplink data packet set as an example. For instance, for different QUIC connections, the QUIC connection identifiers that can be allocated by the transport client are connection ID#1 and connection ID#2, and the QUIC connection identifiers that can be allocated by the transport client are connection ID#3 and connection ID#4. Then the QUIC encapsulation identifiers can include <connectionID#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, and the source connection identifier is the QUIC connection identifier that can be allocated by the transport client); the latter 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 allocated by the transport server, the destination connection identifier).

[0468] 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 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>, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be <connection ID#4,connection ID#1>.

[0469] Within the same QUIC connection, there is only one identifier obtained based on the QUIC connection identifier assignable by the transport server and / or the transport client. Therefore, it is necessary to introduce a new identifier, such as other information used to represent the QUIC connection, to be combined with this identifier for the QUIC encapsulation identifier of multiple sets of packets with different transport requirements within the same QUIC connection. Therefore, the QUIC encapsulation identifier of multiple sets of packets can be determined based on the transport requirement information of multiple sets of packets, the QUIC connection identifier assignable by the transport server and other information representing the QUIC connection, and the QUIC connection identifier assignable by the transport client and other information representing the QUIC connection.

[0470] Taking the QUIC encapsulation identifier of the following set of downlink packets as an example. For example, within the same QUIC connection, the identifier obtained based on the QUIC connection identifiers assignable by the transport server and the transport client is the connection ID. Other identifiers that the transport server can assign are ID#1 and ID#2, and other identifiers that the transport client can assign are ID#3 and ID#4. Then the encapsulation identifiers 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 the set of downlink packets, the other source connection identifiers are other information used to represent the QUIC connection assignable by the transport server); the last four identifiers are composed of the connection ID, other source connection identifiers, and other destination connection identifiers (for the set of downlink packets, the other destination connection identifiers are other information used to represent the QUIC connection assignable by the transport client).

[0471] 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 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>>, and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be <connection ID+<ID#1,ID#4>>.

[0472] 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 allocated by the transmission server and / or the transmission client is connection ID. Other identifiers that the transmission server can allocate are ID#1 and ID#2, and other identifiers that the transmission client can allocate are ID#3 and ID#4. Then the encapsulation identifiers 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 connection ID and other source connection identifiers that can be allocated (corresponding to the uplink data packet set, and the other source connection identifiers are other information used to represent the QUIC connection allocated by the transmission client); the latter four identifiers are composed of connection ID, other source connection identifiers, and other destination connection identifiers (for uplink data, the other destination connection identifiers are other information used to represent the QUIC connection allocated by the transmission server).

[0473] 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>>, and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be <connection ID+<ID#4,ID#1>>.

[0474] In some embodiments, the QUIC encapsulation identifiers of the multiple data can be determined according to the transmission requirement information of the multiple data packet sets, as well as the first IP information and / or 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

[0475] 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 can be used as the encapsulation identifier.

[0476] Taking the QUIC encapsulation identifiers of the downlink data packet set as an example, the IP address and port number assignable by the transmission server are <IP#1,port#1>, <IP#1,port#2>, and the IP address and port number assignable by the transmission client are <IP#2,port#3>, <IP#2,port#4>. Then the QUIC encapsulation identifiers can 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 downlink data packet set, the source address and source port number are the IP address and port number assignable by the transmission server); the latter four identifiers are composed of the source address and source port number, and the destination address and destination port number (for the downlink data packet set, the destination address and destination port number are the address and port number assignable by the transmission client).

[0477] 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 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 [<IP#1,port#1>,<IP#2,port#3>], and the QUIC encapsulation identifier corresponding to downlink data packet set #3 can be [<IP#1,port#1>,<IP#2,port#4>].

[0478] Taking the QUIC encapsulation identifiers of the uplink data packet set as an example, the IP addresses and port numbers that can be allocated by the transmission server are <IP#1,port#1> and <IP#1,port#2>, and the IP addresses and port numbers that can be allocated by the transmission client are <IP#2,port#3> and <IP#2,port#4>. Then the QUIC encapsulation identifiers can 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 addresses and port numbers that can be allocated by the transmission client); the latter 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 addresses and port numbers that can be allocated by the transmission server).

[0479] 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 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 [<IP#2, port#3>, <IP#1, port#1>], and the QUIC encapsulation identifier corresponding to uplink data packet set #3 can be [<IP#2, port#4>, <IP#1, port#1>].

[0480] In the embodiments of the present application, all QUIC encapsulation identifiers can be determined first, and then the corresponding QUIC encapsulation identifiers are selected and determined from all the QUIC encapsulation identifiers based on the data packet sets with different transmission requirements. Alternatively, the corresponding QUIC encapsulation identifiers can also be directly determined based on the data packet sets with different transmission requirements.

[0481] S1308, the SEALDD server sends a connection / handshake response message to the SEALDD client.

[0482] In some embodiments, the content of the response message may include information about the uplink service flow and the QUIC encapsulation identifiers corresponding to the data packet sets of the uplink service flow, which are used by the SEALDD client to process the data packet sets of the uplink service flow from the VAL client.

[0483] S1309, the SEALDD server sends the QUIC encapsulation identifiers corresponding to the data packet sets of the service flow and the corresponding QoS information to the PCF.

[0484] The SEALDD server sends the QUIC encapsulation identifiers corresponding to the data packet sets of the uplink service flow and the corresponding QoS information (such as QoS importance information), and / or the QUIC encapsulation identifiers corresponding to the data packet sets of the downlink service flow and the corresponding QoS information (such as QoS importance information) to the PCF network element.

[0485] If the SEALDD server is trusted for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier corresponding to the data packet set and the corresponding QoS information to the PCF network element. If the SEALDD server is not trusted for the 5G network, it needs to send the QUIC encapsulation identifier corresponding to the data packet set and the corresponding QoS information to the PCF network element via the NEF network element.

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

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

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

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

[0490] 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.

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

[0492] 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.

[0493] 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 according to the QUIC encapsulation identifier corresponding to the data packet set, that is, the QFIs of the QoS flows of the data packet sets with the same QUIC encapsulation identifier are the same.

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

[0495] In some embodiments, the SMF network element can also generate a PDR rule according to 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 and the corresponding QoS information.

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

[0497] In some embodiments, the SMF network element may also send the QoS information corresponding to the set of data packets to the UPF.

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

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

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

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

[0502] S1316. The SEALDD server encapsulates the set of data packets of the downlink service flow based on the downlink QUIC encapsulation identifier.

[0503] For example, after the PDU session establishment or modification is completed, when the downlink service flow of the VAL server arrives, the SEALDD server may determine the set of data packets of the downlink service flow according to the service flow protocol description information of the VAL server (such as determining that certain data packets belong to the data packet set #1). Then, the SEALDD server encapsulates the set of data packets of the downlink service flow based on the downlink QUIC encapsulation identifier.

[0504] For example, if the QUIC encapsulation identifier corresponding to the data packet set #1 is <connection ID#1>, the SEALDD server may perform downlink QUIC data packet encapsulation on the data packet set from the VAL server based on <connection ID#1>. That is, the QUIC connection identifier <connection ID#1> is carried in the encapsulated downlink data packet set #1.

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

[0506] Accordingly, the UPF network element receives the set of downlink data packets sent by the SEALDD server.

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

[0508] For example, when the UPF network element receives the downlink packet set, it can perform QUIC packet detection on the downlink packet set and the corresponding QFI marking based on the PDR rule, that is, it can determine the QUIC encapsulation identifier in the downlink packet set and map the downlink packet sets with the same QUIC encapsulation identifier to the QoS flow with the same QFI.

[0509] S1319, the SEALDD client encapsulates the set of uplink data packets based on the uplink QUIC encapsulation identifier.

[0510] After the PDU session establishment or modification is completed, when the set of uplink data packets of the VAL client arrives, the SEALDD client can determine the data packet or data packet set according to the service flow protocol description information of the VAL client (such as determining that some data packets belong to data packet set #3). Then, the SEALDD client encapsulates the set of uplink data packets based on the uplink QUIC encapsulation identifier.

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

[0512] S1320, the SEALDD client sends the encapsulated set of uplink data packets to the UE.

[0513] Accordingly, the UE receives the set of uplink data packets sent by the SEALDD client.

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

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

[0516] Figure 14 It is a schematic diagram of the method for QUIC data processing provided by the embodiments of the present application. For example, Figure 14 It is a transmission scenario for multiple downlink service flows.

[0517] S1401, the VAL server sends a service subscription request message to the SEALDD server.

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

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

[0520] S1402, the SEALDD server sends a service subscription request response message to the VAL server.

[0521] S1403, the SEALDD server determines the QUIC encapsulation identifier corresponding to the service flow according to the QoS information corresponding to the service flow.

[0522] In the embodiments of the present application, for service flows with the same QoS information, such as QoS parameters / importance, their corresponding QUIC encapsulation identifiers are the same; for service flows with different QoS information, such as QoS requirement information / importance information, their corresponding QUIC encapsulation identifiers are different.

[0523] For example, service flow #1 corresponds to QoS information #1; service flow #2 corresponds to QoS information #2; service flow #3 corresponds to QoS information #1. Then the QUIC encapsulation identifiers corresponding to service flow #1 and service flow #3 may be QoS information #1 or encapsulation identifier #1, and the QUIC encapsulation identifier corresponding to service flow #2 is QoS information #2 or encapsulation identifier #2.

[0524] 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 also be encapsulated in the QUIC tunnel header.

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

[0526] If the SEALDD server is trusted for the 5G network, the SEALDD server can directly send the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information to the PCF network element. If the SEALDD server is not trusted for the 5G network, it is necessary to send the QUIC encapsulation identifier corresponding to the service flow and the corresponding QoS information to the PCF network element via the NEF network element.

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

[0528] S1405. The PCF network element may generate a PCC rule based on the QUIC encapsulation identifier corresponding to the service flow and the QoS information.

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

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

[0531] 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.

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

[0533] 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.

[0534] The policy response message includes the QUIC encapsulation identifier corresponding to the service flow. The SMF network element may determine the QFI of the QoS flow corresponding to the service flow according to the QUIC encapsulation identifier corresponding to the service flow, that is, the QFIs of the QoS flows of the service flows with the same QUIC encapsulation identifier are the same.

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

[0536] 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 and the corresponding QoS information.

[0537] 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.

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

[0539] 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.

[0540] S1410, the UE completes the remaining PDU session establishment or modification process.

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

[0542] S1412, the VAL server sends the service flow to the SEALDD server.

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

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

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

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

[0547] Figure 15 This is a schematic diagram of the QUIC data processing method provided by the embodiments of the present application. For example, Figure 15 For the scenario of a single downlink service flow, the single downlink service flow includes a set of downlink data packets with different QoS information.

[0548] S1501, the VAL server sends a service subscription request message to the SEALDD server.

[0549] The request message may include information about the service flow. For example, the information about the service flow may include protocol description information of the service flow (the service flow uses the RTP protocol for transmission), or the information about the service flow may include protocol description information of the service flow and QoS information of the packet set corresponding to the protocol description information, etc. Among them, the QoS information may include QoS requirement information and / or QoS importance information.

[0550] For example, the service flow includes packet set #1 and packet set #2. Among them, packet set #1 corresponds to QoS information #1; packet set #2 corresponds to QoS information #2.

[0551] S1502, the SEALDD server sends a request response message for service subscription to the VAL server.

[0552] S1503, the SEALDD server determines the QUIC encapsulation identifier corresponding to the packet set according to the QoS information corresponding to the packet set.

[0553] In the embodiments of the present application, for packet sets with the same QoS information, such as QoS requirement information and / or importance information, the corresponding QUIC encapsulation identifiers are the same; for packet sets with different QoS information, such as QoS requirement information / importance information, the corresponding QUIC encapsulation identifiers are different.

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

[0555] 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.

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

[0557] If the SEALDD server is trusted for the 5G network, the SEALDD server may directly send the QUIC encapsulation identifier corresponding to the packet set and the corresponding QoS information to the PCF network element. If the SEALDD server is not trusted for the 5G network, it is necessary to send the QUIC encapsulation identifier corresponding to the packet set and the corresponding QoS information to the PCF network element through the NEF network element.

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

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

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

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

[0562] S1507, the SMF network element sends policy request information to the PCF network element, for requesting to obtain the QUIC encapsulation identifier corresponding to the data packet set.

[0563] In some embodiments, the policy request message may also be used to request to obtain the QoS information corresponding to the data packet set

[0564] 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.

[0565] 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 according to the QUIC encapsulation identifier corresponding to the data packet set, that is, the QFIs of the QoS flows of the data packet sets with the same QUIC encapsulation identifier are the same.

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

[0567] In some embodiments, the SMF network element can also generate a PDR rule according to 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.

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

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

[0570] For example, the SMF network element sends the PDR rule corresponding to the data packet / data packet and the corresponding QFI of the 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.

[0571] S1510, The UE completes the remaining PDU session establishment or modification process.

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

[0573] S1512, The VAL server sends a packet set to the SEALDD server.

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

[0575] For example, the SEALDD server can determine the packet set of the downlink traffic flow (such as determining which packets belong to packet set #1) according to the service flow protocol description information of the VAL server. Then, the packet set is encapsulated based on the QUIC encapsulation identifier of the packet set.

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

[0577] S1515, The UPF network element maps the packet set to the QoS flow according to the QUIC encapsulation identifier in the packet set and the QFI of the corresponding QoS flow.

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

[0579] In the embodiments of the present application, the bearer messages for information such as information of multiple data, such as service flow information, QUIC encapsulation identifier, QoS flow identifier, second connection information, second IP information, etc. are only examples and are not limited. For example, in S1202, the service subscription request message can be used to bear the service flow information by the VAL server to the SEALDD server; or, other messages can also be used to bear the service flow information.

[0580] As described above in conjunction with Figures 1 to 15 the method for data transmission provided by the embodiments of the present application is described. Below, in conjunction with Figures 16 to 21 , the apparatus embodiments of the present application are described. It should be understood that the descriptions of the method-side embodiments correspond to the descriptions of the apparatus embodiments. Therefore, the parts not described in detail can refer to the above descriptions.

[0581] Figure 16It is a schematic block diagram of a data processing device provided by 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 perform data processing, and the sending unit 2030 can implement corresponding communication functions.

[0582] The acquisition unit 2010 is used to acquire transmission requirement information of multiple data, where one of the multiple data is a service flow or a packet set, and the packet set includes at least one packet;

[0583] The processing unit 2020 is used to determine a QUIC encapsulation identifier 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 identifier of the multiple data;

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

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

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

[0587] In some embodiments, the apparatus 2000 further includes a receiving unit 2040 configured to: receive information about the plurality of data from an application server, where the information about the plurality of data includes transmission requirement information of the plurality of data; or, the receiving unit 2040 is configured to receive the information about the plurality of data from the application server, where the information about the plurality of data includes description information of the plurality of data and / or transmission requirement information corresponding to the description information; and a processing unit 2030 configured to determine the transmission requirement information of the plurality of data according to the information about the plurality of data.

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

[0589] In some embodiments, the processing unit 2020 is configured to: determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data and first connection information; or, determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data and second connection information; or, determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data, the first connection information, and the second connection information, where the first connection information is information that can be assigned 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 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 and is used 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 identifiers representing the QUIC connection.

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

[0591] In some embodiments, the processing unit 2020 is configured to: determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data and first IP information; or, determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data and second IP information; or, determine the QUIC encapsulation identifier of the plurality of data according to the transmission requirement information of the plurality of data, the first IP transmission information, and the second IP information, where the first IP information includes an IP address and a port number that can be assigned by the transmission server, and the second IP information includes an IP address and a port number that can be assigned by the transmission client.

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

[0593] In some embodiments, the QUIC encapsulation identifier of multiple data includes the information in the QUIC tunnel header.

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

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

[0596] In some embodiments, the sending unit 2030 is configured to: send 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, where the second network element includes a network element responsible for the user plane function.

[0597] In some embodiments, the sending unit 2030 is configured to: send the QUIC encapsulation identifier of multiple data to a transmission client so that the transmission client encapsulates the multiple data by using the QUIC encapsulation identifier of the multiple data, where the multiple data are uplink data.

[0598] In some embodiments, the application server includes a VAL server.

[0599] In some embodiments, the transmission client includes a SEALDD client, and the transmission server includes a SEALDD server.

[0600] 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 the multiple data is determined by the first network element.

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

[0602] Figure 17 It is a schematic block diagram of a data processing apparatus provided by an embodiment of the present application. The apparatus 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 for data processing.

[0603] A receiving unit 3010, configured to receive the QUIC encapsulation identifiers of the multiple data sent by a transmission server, where the QUIC encapsulation identifiers of the multiple data are 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 identifiers of the multiple data, and one piece of data of the multiple data includes a traffic flow or a data packet set, and the data packet set includes at least one data packet.

[0604] A processing unit, configured to determine, according to the QUIC encapsulation identifiers of the multiple data, the identifier of a QoS flow corresponding to the QUIC encapsulation identifiers of the multiple data.

[0605] In some embodiments, the multiple data includes a first traffic flow and a second traffic flow, the QUIC encapsulation identifiers of the first traffic flow and the second traffic flow are a first encapsulation identifier, and the transmission requirement information of the first traffic flow and the second traffic flow is the same; or, the QUIC encapsulation identifiers of the first traffic flow and the second traffic flow are a second encapsulation identifier and a third encapsulation identifier respectively, and the transmission requirement information of the first traffic flow and the second traffic flow is different.

[0606] In some embodiments, the multiple data includes a first data packet set and a second data packet set of the same traffic flow, the QUIC encapsulation identifiers of the first data packet set and the second data packet set are 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 identifiers 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.

[0607] In some embodiments, the information of the multiple data includes the transmission requirement information of the multiple data, and the information of the multiple data comes from an application server; or, the transmission requirement information of the multiple data is determined according to the information of the multiple data, and 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.

[0608] In some embodiments, 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 an IP address and a port number that can be assigned by a transmission server, and / or an IP address and a port number that can be assigned by a transmission client; or, the QUIC encapsulation identifiers of the multiple data include information in a QUIC tunnel header.

[0609] In some embodiments, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data and the first connection information; or, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data and the second connection information; or, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data, the first connection information and the second connection information, where the first connection information is information that can be allocated by the transmission server for representing 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, and the second connection information is information that can be allocated by the transmission client for representing 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.

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

[0611] In some embodiments, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data and the first IP information; or, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data and the second IP information; or, the QUIC encapsulation identifier of the plurality of data is determined according to the transmission requirement information of the plurality of data, the first IP information and the second IP information, where 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.

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

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

[0614] In some embodiments, the application server includes a VAL server.

[0615] In some embodiments, the transmission client includes a SEALDD client, and the transmission server includes a SEALDD server.

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

[0617] Figure 18It is a schematic block diagram of a data processing device provided by 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 for data processing.

[0618] The receiving unit 4010 is configured to receive the 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 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 includes a traffic flow or a packet set, and the packet set includes at least one packet.

[0619] The processing unit 4020 is configured to map the encapsulated multiple data into QoS flows corresponding to the QUIC encapsulation identifiers of the multiple data.

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

[0621] Figure 19 It is a schematic block diagram of a data processing device provided by an embodiment of the present application. The device 5000 includes an obtaining unit 5010, a processing unit 5020, and a sending unit 5030. The obtaining unit 5010 is configured to obtain required data information, the processing unit 5020 is used for data processing, and the sending unit 5030 can implement corresponding communication functions.

[0622] The obtaining unit 5010 is configured to obtain 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 are uplink data; and

[0623] obtain the 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. There is a corresponding relationship between the transmission requirement information of the multiple data and the QUIC encapsulation identifiers of the multiple data;

[0624] 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;

[0625] A sending unit 5030, configured to send the encapsulated multiple data to a user equipment, so as to map the encapsulated multiple data into a QoS flow corresponding to a QUIC encapsulation identifier of the multiple data.

[0626] In some embodiments, the apparatus 5000 further includes a receiving unit 5040, configured to receive the multiple data from an application client.

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

[0628] In some embodiments, the application client includes a VAL client.

[0629] Figure 20 It is a schematic block diagram of a data processing apparatus provided by an embodiment of the present application. The apparatus 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 configured to perform data processing.

[0630] The receiving unit 6010 is configured to receive multiple encapsulated data sent by a transmission client. The encapsulated multiple data are obtained by encapsulating the multiple data by using a QUIC encapsulation identifier of the multiple data. The QUIC encapsulation identifier of the multiple data is determined according to 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 service flow or a data packet set. The data packet set includes at least one data packet. The multiple data are uplink data;

[0631] The processing unit 6020 is configured to map the encapsulated multiple data into a QoS flow corresponding to the QUIC encapsulation identifier of the multiple data.

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

[0633] Figure 21 It is a schematic block diagram of another data processing apparatus according to an embodiment of the present application. Figure 21The illustrated communication device 7000 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 through 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 signals and / or receive signals.

[0634] Optionally, the memory 7300 can be coupled to the processor 7200 through an interface or integrated with the processor 7200.

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

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

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

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

[0639] In some embodiments, the data processing device may be a transmission client.

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

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

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

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

[0644] It should be understood that the term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this article generally represents an "or" relationship between the associated objects before and after.

[0645] It should be understood that in various embodiments of the present application, the sequence numbers of the above processes do 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 to the implementation process of the embodiments of the present application.

[0646] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. For example, a component may 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, an application running on a computing device and the computing device may both be components. One or more components may reside in a process and / or an execution thread, and the components may be located on one computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media storing various data structures. The components may communicate, for example, through local and / or remote processes according to signals having one or more data packets (such as data from two components interacting with another component between a local system, a distributed system, and / or a network, such as the Internet interacting with other systems through signals).

[0647] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0648] Those skilled in the art can 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 foregoing method embodiments, and will not be elaborated herein.

[0649] In 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 illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, 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 displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of devices or units can be electrical, mechanical, or other forms.

[0650] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

Claims

1. A method for data processing, characterized in that, Including: Obtain 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; Determine 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; Send 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. 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, determine that the QUIC encapsulation identifiers of the first service flow and the second service flow are a first encapsulation identifier; or, When the transmission requirement information of the first service flow and the second service flow is different, determine that the QUIC encapsulation identifiers of the first service flow and the second service flow are a second encapsulation identifier and a third encapsulation identifier respectively.

3. The method according to claim 1, characterized in that The multiple data includes a first set of data packets and a second set of data packets of the same service flow. 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, determine that the QUIC encapsulation identifiers of the first set of data packets and the second set of data packets are 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, determine that the QUIC encapsulation identifiers of the first set of data packets and the second set of data packets are 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 allocated 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 allocated by the transmission server, and / or the IP address and port number that can be allocated 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 for representing 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 for representing 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, characterized in that, 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 transmission 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, wherein 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 the user plane function.

14. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Sending a QUIC encapsulation identifier of the multiple data to a 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 an identifier of a 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 open or a network element responsible for policy control.

19. A method for data processing, characterized in that, It includes: Receiving the QUIC encapsulation identifier of the multiple data sent by a transport server, where the QUIC encapsulation identifier of the multiple data is determined according to 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 of the multiple data includes a traffic flow or a packet set, and the packet set includes at least one packet; Determining an identifier of a 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: Receiving 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: Sending the identifier of the 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 function.

22. A method for data processing, characterized in that, It includes: Receiving the encapsulated multiple data sent by a transport server, where 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 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 of the multiple data includes a traffic flow or a packet set, and the packet set includes at least one packet; Mapping the encapsulated multiple data into a 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 a QoS flow corresponding to the QUIC encapsulation identifier 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 a 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, It includes: Obtaining multiple data, where one piece of data of 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; Obtaining a QUIC encapsulation identifier of the multiple data, where the QUIC encapsulation identifier of the multiple data is determined according to 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; Encapsulate the multiple pieces of data according to the QUIC encapsulation identifier of the multiple pieces of data to obtain the encapsulated multiple pieces of data; Send the encapsulated multiple pieces of data to a user device to map the encapsulated multiple pieces of data into a QoS flow corresponding to the QUIC encapsulation identifier of the multiple pieces of data.

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

26. The method according to claim 24 or 25, characterized in that, The obtaining of the QUIC encapsulation identifier of the multiple pieces of data includes: Receiving the QUIC encapsulation identifier of the multiple pieces of data from a transmission 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 pieces of data sent by a transmission client, where the encapsulated multiple pieces of data are obtained by encapsulating the multiple pieces of data by using the QUIC encapsulation identifier of the multiple pieces of data, the QUIC encapsulation identifier of the multiple pieces of data is determined according to the transmission requirement information of the multiple pieces of data, there is a corresponding relationship between the transmission requirement information of the multiple pieces of data and the QUIC encapsulation identifier of the multiple pieces of data, one piece of data of the multiple pieces of data is a service flow or a packet set, the packet set includes at least one packet, and the multiple pieces of data are uplink data; Map the encapsulated multiple pieces of data into a QoS flow corresponding to the QUIC encapsulation identifier of the multiple pieces of data.

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

30. A data processing device, characterized in that, Including: At least one processor, where the at least one processor is coupled to a 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