Communication method and device

Abstract

The embodiment of the invention provides a communication method and device, and relates to the field of communication. According to the embodiment of the invention, the network side control terminal equipment and the UPF network element can establish the connection which allows multiple service flows to be commonly used, so that the link establishment process of the connection is saved. Comprises: an SMF network element receiving a first message from a terminal device for requesting establishment or PDU session, the SMF network element sending a second message to the terminal device, the second message being used for indicating success of establishment or update of the PDU session, the second message comprising a multi-stream connection parameter, and the multi-stream connection parameter being used for indicating that multiple service streams in the PDU session share the same connection transmission.

Description

[0001] This application is a divisional application. The application number of the original application is 202010152389.7, and the original application date is March 6, 2020. The entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to communication technologies, and in particular, to a communication method and apparatus. Background Art

[0003] In the next-generation wireless communication system, for example, in the new radio (NR) system, a user equipment (UE) establishes a protocol data unit (PDU) session with a data network (DN) element through a user plane function (UPF) element. The PDU session provides a data transmission service between the terminal device and the DN element.

[0004] In the prior art, between the UE and the UPF element, the establishment of a multi-access PDU session (which can also be referred to as a multi-PDU session) can be supported. For example, Figure 1 As shown, the UE and the UPF element can establish a multi-access PDU session A based on access technology 1 and access technology 2. Then, the traffic flow of the UE can be transmitted to the UPF element through access technology 1 and / or access technology 2. A multi-access PDU session is relative to a single-access PDU session. A single-access PDU session refers to a PDU session that accesses the UPF element through one access technology, and a multi-access PDU session refers to a PDU session that accesses the UPF element through multiple access technologies (at least two).

[0005] However, in the prior art, the above multi-access PDU session must be established between the UE and the UPF element to implement a multi-PDU session. The method for implementing a multi-PDU session in the prior art is relatively complex. Summary of the Invention

[0006] Embodiments of this application provide a communication method and apparatus, which can control a connection that allows multiple traffic flows to be shared between a terminal device and a UPF element by the network side, thereby saving the link establishment process of the connection and improving the transmission efficiency.

[0007] In a first aspect, an embodiment of the present application provides a communication method, including: a Session Management Function (SMF) network element receives a first message from a terminal device. The first message is used to request the establishment or update of a Protocol Data Unit (PDU) session. The SMF network element determines that multiple service flows in the PDU session share the same connection. Among them, the connection shared by the multiple service flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in the QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in the MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection. The SMF network element sends a second message to the terminal device. The second message is used to indicate that the establishment or update of the PDU session is successful, and the second message includes multi-flow connection parameters, which are used to represent that multiple service flows in the PDU session share the same connection for transmission.

[0008] When usually implementing a multi-access PDU session, it is necessary to re-establish the multi-access PDU session, and the process of implementing the multi-access PDU session is relatively complex. In the embodiment of the present application, the network side can control the establishment of a connection that allows multiple service flows to be used in common between the terminal device and the User Plane Function (UPF) network element, thereby saving the connection establishment process and improving the transmission efficiency.

[0009] In a second aspect, an embodiment of the present application provides a communication method, including: a Session Management Function (SMF) network element receives a first message from a terminal device. The first message is used to request the establishment or update of a Protocol Data Unit (PDU) session. The SMF network element determines that multiple service flows in the PDU session share the same connection. Among them, the connection shared by the multiple service flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in the QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in the MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection. The SMF network element sends a second message and multi-flow connection parameters to the terminal device. The second message is used to indicate that the establishment or update of the PDU session is successful, and the multi-flow connection parameters are used to represent that multiple service flows in the PDU session share the same connection for transmission.

[0010] The difference between the embodiment of the second aspect and the embodiment of the first aspect is that in the embodiment of the second aspect, the multi-flow connection parameters are not included in the second message. The beneficial effects of the embodiment of the second aspect can refer to the beneficial effects of the embodiment of the first aspect, and will not be elaborated here.

[0011] Regarding the embodiments of the first aspect and the second aspect of the present application:

[0012] In a possible implementation, the multi-stream connection parameters include service flow description parameters and multi-stream multiplexing parameters. The multi-stream multiplexing parameters are used to represent QUIC connection information related to the service flow, QUIC aggregated flow connection information, MP-QUIC connection information, MP-QUIC aggregated flow connection information, or SCTP connection information.

[0013] In a possible implementation, the service flow description parameters include at least one of the following: one or more pieces of service flow description information, an application identifier, one or more quality of service (QoS) flow identifiers, and a PDU session identifier.

[0014] In a possible implementation, the multi-stream multiplexing parameters include at least one of the following: QUIC method indication information, MP-QUIC method indication information, or SCTP method indication information, a connection identifier, multi-stream multiplexing indication information, QoS flow granularity indication information, and PDU session granularity indication information. Among them, the QUIC method indication information is used to indicate that the service flow is transmitted using a QUIC connection, the MP-QUIC indication information is used to indicate that the service flow is transmitted using an MP-QUIC connection, the SCTP method indication information is used to indicate that the service flow is transmitted using an SCTP connection, the connection identifier is used to indicate the connection identifier corresponding to the service flow, the QoS flow granularity indication information is used to indicate that one or more QoS flow service flows can share a QUIC connection, an MP-QUIC connection, or an SCTP connection, and the PDU session granularity indication information is used to indicate that the service flows of a PDU session can share a QUIC connection, an MP-QUIC connection, or an SCTP connection.

[0015] In a possible implementation, the SMF network element determines that multiple service flows in a PDU session share the same connection, including: the SMF network element determines that the service flows share the same connection based on one or more of the following: the security or encryption information of the service flow, the QoS parameters of the service flow, the destination address of the service flow, the data network name (DNN) of the service flow, the transport protocol of the service flow, the type of the service flow, and the traffic splitting mode of the service flow. Alternatively, the SMF network element determines that the service flows share the same connection based on PCF indication information from the policy control function (PCF) network element or indication information from the UPF network element.

[0016] In a possible implementation, the SMF network element sends the multi-stream connection parameters to the user plane function (UPF) network element.

[0017] In a possible implementation, the SMF network element determines that multiple traffic flows in a PDU session share the same connection, including: when multiple traffic flows in a PDU session have the same encryption and / or integrity protection requirements, the SMF network element determines that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session have the same encryption security level, the SMF network element determines that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session belong to the same QoS flow, the SMF network element determines that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session are non-guaranteed bit rate (non-GBR) traffic flows, the SMF network element determines that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session have the same destination IP address or the same DNN, or multiple traffic flows in a PDU session use the same transport protocol, or multiple traffic flows in a PDU session belong to the same PDU session, or multiple traffic flows in a PDU session use the same traffic splitting mode, or multiple traffic flows in a PDU session have the same type, the SMF network element determines that the multiple traffic flows share the same connection.

[0018] In a possible implementation, the SMF network element sends encryption and / or integrity protection indication information to the UPF network element and / or the terminal device.

[0019] In a third aspect, an embodiment of the present application provides a communication method, including: a terminal device sends a first message to a session management function (SMF) network element. The first message is used to request the establishment or update of a protocol data unit (PDU) session. The terminal device receives a second message from the SMF network element. The second message is used to indicate that the PDU session establishment or update is successful. The second message includes multi-flow connection parameters, and the multi-flow connection parameters are used to indicate that multiple traffic flows in the PDU session share the same connection for transmission. The connection shared by the multiple traffic flows is: a QUIC connection of the Internet transport layer protocol, or an aggregated flow connection in the QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in the MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection.

[0020] Fourthly, an embodiment of the present application provides a communication method, including: a terminal device sending a first message to a session management function (SMF) network element. The first message is used to request the establishment or update of a protocol data unit (PDU) session. The terminal device receives a second message and multi-flow connection parameters from the SMF network element. The second message is used to indicate the successful establishment or update of the PDU session, and the multi-flow connection parameters are used to indicate that multiple service flows in the PDU session share the same connection for transmission. The connection shared by the multiple service flows is: an Internet transport layer protocol (QUIC) connection, or an aggregated flow connection in the QUIC connection, or a multi-path Internet transport protocol (MP-QUIC) connection, or an aggregated flow connection in the MP-QUIC connection, or a stream control transmission protocol (SCTP) connection.

[0021] The difference between the embodiment of the fourth aspect and the embodiment of the third aspect is that in the embodiment of the fourth aspect, the multi-flow connection parameters are not included in the second message, which will not be elaborated here.

[0022] Regarding the embodiments of the third aspect and the fourth aspect of the present application:

[0023] The specific contents of the multi-flow connection parameters, service flow description parameters, and multi-flow multiplexing parameters involved in the third aspect and the fourth aspect can refer to the specific contents of the first aspect, which will not be elaborated here.

[0024] In a possible implementation manner, it further includes: the terminal device establishing a connection shared by multiple service flows with a user plane function (UPF) network element. The terminal device uses the connection shared by the multiple service flows to transmit a first service flow.

[0025] In a possible implementation manner, the terminal device determines whether a second service flow is allowed to share the connection for transmitting the first service flow according to the multi-flow multiplexing parameters. When the second service flow is allowed to share the connection for transmitting the first service flow, the terminal device uses the connection for transmitting the first service flow to transmit the second service flow.

[0026] In a possible implementation manner, the terminal device receives encryption and / or integrity protection indication information from the SMF network element. The terminal device performs encryption and / or integrity protection on the service flow according to the encryption and / or integrity protection indication information, or does not perform encryption and / or integrity protection on the service flow.

[0027] Fifth aspect, an embodiment of the present application provides a communication method, including: a User Plane Function (UPF) network element receives multi-flow connection parameters from a Session Management Function (SMF) network element. The multi-flow connection parameters are used to indicate that multiple service flows in a PDU session share the same connection for transmission. The UPF network element establishes a connection that allows multiple service flows to share with a terminal device based on the multi-flow connection parameters. The connection shared by multiple service flows is: a Quick UDP Internet Connections (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection.

[0028] For the specific content of the multi-flow connection parameters, service flow description parameters, and multi-flow multiplexing parameters involved in the fifth aspect, reference may be made to the specific content of the first aspect, which will not be elaborated here.

[0029] In a possible implementation, the UPF network element uses the connection that allows multiple service flows to share to transmit a first service flow. The UPF network element determines whether a second service flow is allowed to share the connection transmitting the first service flow according to the multi-flow multiplexing parameters. When the second service flow is allowed to share the connection transmitting the first service flow, the UPF network element uses the connection transmitting the first service flow to transmit the second service flow.

[0030] In a possible implementation, the UPF network element receives encryption and / or integrity protection indication information from the SMF network element. The UPF network element encrypts and / or protects the integrity of the service flow according to the encryption and / or integrity protection indication information, or does not encrypt and / or protect the integrity of the service flow.

[0031] Sixth aspect, an embodiment of the present application provides a communication device, including: the communication device may be an SMF network element, or a chip or a chip system within the SMF network element. The communication device may include a processing unit and a communication unit. When the communication device is an SMF network element, the processing unit may be a processor, and the communication unit may be a communication interface or an interface circuit. The communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the SMF network element to implement a communication method described in the first aspect or any possible implementation manner of the first aspect, or to enable the SMF network element to implement a communication method described in the second aspect or any possible implementation manner of the second aspect.

[0032] Exemplarily, a communication unit is configured to receive a first message from a terminal device. The first message is used to request the establishment or update of a protocol data unit (PDU) session. A processing unit is configured to determine that multiple traffic flows in the PDU session share the same connection. The connection shared by the multiple traffic flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection. The communication unit is further configured to send a second message to the terminal device. The second message is used to indicate that the establishment or update of the PDU session is successful, and the second message includes multi-flow connection parameters, which are used to indicate that multiple traffic flows in the PDU session share the same connection for transmission.

[0033] Alternatively, exemplarily, a communication unit is configured to receive a first message from a terminal device. The first message is used to request the establishment or update of a protocol data unit (PDU) session. A processing unit is configured to determine that multiple traffic flows in the PDU session share the same connection. The connection shared by the multiple traffic flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection. The communication unit is further configured to send a second message and multi-flow connection parameters to the terminal device. The second message is used to indicate that the establishment or update of the PDU session is successful, and the multi-flow connection parameters are used to indicate that multiple traffic flows in the PDU session share the same connection for transmission.

[0034] For the specific contents of the multi-flow connection parameters, traffic flow description parameters, and multi-flow multiplexing parameters involved in the sixth aspect, reference may be made to the specific contents of the first aspect, which will not be elaborated here.

[0035] In a possible implementation, the processing unit is specifically configured to determine that traffic flows share the same connection according to one or more of the following: security or encryption information of the traffic flow, traffic flow QoS parameters, traffic flow destination address, data network name (DNN) of the traffic flow, transport protocol of the traffic flow, type of the traffic flow, traffic flow splitting mode. Alternatively, the processing unit is specifically configured to determine that traffic flows share the same connection based on Policy Control Function (PCF) indication information from a PCF network element or indication information from a User Plane Function (UPF) network element.

[0036] In a possible implementation, the communication unit is further configured to send multi-flow connection parameters to a User Plane Function (UPF) network element.

[0037] In a possible implementation, the processing unit is specifically configured to: when multiple traffic flows in a PDU session have the same encryption and / or integrity protection requirements, determine that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session have the same encryption security level, determine that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session belong to the same QoS flow, determine that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session are non-guaranteed bit rate (non-GBR) traffic flows, determine that the multiple traffic flows share the same connection. Or, when multiple traffic flows in a PDU session have the same destination IP address or the same DNN, or multiple traffic flows in a PDU session use the same transport protocol, or multiple traffic flows in a PDU session belong to the same PDU session, or multiple traffic flows in a PDU session use the same traffic splitting mode, or the types of multiple traffic flows in a PDU session are the same, determine that the multiple traffic flows share the same connection.

[0038] In a possible implementation, the communication unit is further configured to send encryption and / or integrity protection indication information to the UPF network element and / or the terminal device.

[0039] When the communication device is a chip or a chip system within the SMF network element, the processing unit may be a processor, and the communication unit may be a communication interface. For example, the communication interface may be an input / output interface, a pin, a circuit, etc. The processing unit executes the instructions stored in the storage unit to enable the SMF network element to implement a communication method described in the first aspect or any possible implementation of the first aspect, or to enable the SMF network element to implement a communication method described in the second aspect or any possible implementation of the second aspect. The storage unit may be a storage unit within the chip (e.g., a register, a cache, etc.), or a storage unit outside the chip within the SMF network element (e.g., a read-only memory, a random access memory, etc.).

[0040] In a seventh aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a chip or a chip system within the terminal device. The communication device may include a processing unit and a communication unit. When the communication device is a terminal device, the processing unit may be a processor, and the communication unit may be a communication interface, an interface circuit, or a transceiver. The communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the terminal device to implement a communication method described in the third aspect or any possible implementation of the third aspect, or to enable the terminal device to implement a communication method described in the fourth aspect or any possible implementation of the fourth aspect.

[0041] Exemplarily, a communication unit is configured to send a first message to a Session Management Function (SMF) network element. The first message is used to request the establishment or update of a Protocol Data Unit (PDU) session. Among them, the communication unit is further configured to receive a second message from the SMF network element. The second message is used to indicate the successful establishment or update of the PDU session, and the second message includes multi-flow connection parameters, which are used to indicate that multiple service flows in the PDU session share the same connection for transmission. The connection shared by multiple service flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection.

[0042] Alternatively, exemplarily, a communication unit is configured to send a first message to a Session Management Function (SMF) network element. The first message is used to request the establishment or update of a Protocol Data Unit (PDU) session. Among them, the communication unit is further configured to receive a second message and multi-flow connection parameters from the SMF network element. The second message is used to indicate the successful establishment or update of the PDU session, and the multi-flow connection parameters are used to indicate that multiple service flows in the PDU session share the same connection for transmission. The connection shared by multiple service flows is: an Internet Transport Layer Protocol (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a Multipath QUIC (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection.

[0043] For the specific content of the multi-flow connection parameters, service flow description parameters, and multi-flow multiplexing parameters related to the seventh aspect, reference can be made to the specific content of the first aspect, which will not be elaborated here.

[0044] In a possible implementation manner, it further includes a processing unit. The processing unit is configured to establish a connection shared by multiple service flows with a User Plane Function (UPF) network element. The processing unit is further configured to transmit a first service flow using the connection shared by multiple service flows.

[0045] In a possible implementation manner, the processing unit is further configured to determine whether a second service flow is allowed to share the connection for transmitting the first service flow according to the multi-flow multiplexing parameters. The processing unit is further configured to, when the second service flow is allowed to share the connection for transmitting the first service flow, transmit the second service flow using the connection for transmitting the first service flow.

[0046] In a possible implementation manner, the communication unit is further configured to receive encryption and / or integrity protection indication information from the SMF network element. The processing unit is further configured to encrypt and / or perform integrity protection on the service flow according to the encryption and / or integrity protection indication information, or not perform encryption and / or integrity protection on the service flow.

[0047] When the communication device is a chip within a terminal device, the processing unit may be a processor, and the communication unit may be a communication interface, such as an input / output interface, a pin, or a circuit, etc. The processing unit executes the instructions stored in the storage unit to enable the terminal device to implement a communication method described in the third aspect or any possible implementation manner of the third aspect, or to enable the terminal device to implement a communication method described in the fourth aspect or any possible implementation manner of the fourth aspect. The storage unit may be a storage unit within the chip (e.g., a register, a cache, etc.), or may be a storage unit outside the chip within the terminal device (e.g., a read-only memory, a random-access memory, etc.).

[0048] In an eighth aspect, an embodiment of the present application provides a communication device, including: the communication device may be a UPF network element, or a chip or a chip system within a UPF network element. The communication device may include a processing unit and a communication unit. When the communication device is a UPF network element, the processing unit may be a processor, and the communication unit may be a communication interface or an interface circuit. The communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the UPF network element to implement a communication method described in the fifth aspect or any possible implementation manner of the fifth aspect.

[0049] Exemplarily, the communication unit is used to receive multi-flow connection parameters from a session management function (SMF) network element. The multi-flow connection parameters are used to indicate that multiple service flows in a PDU session share the same connection for transmission. The processing unit is used to establish a connection that allows multiple service flows to share with a terminal device based on the multi-flow connection parameters. The connection shared by multiple service flows is: an Internet transport layer protocol (QUIC) connection, or an aggregated flow connection in a QUIC connection, or a multi-path Internet transport protocol (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a stream control transmission protocol (SCTP) connection.

[0050] The specific contents of the multi-flow connection parameters, service flow description parameters, and multi-flow multiplexing parameters involved in the eighth aspect may refer to the specific contents of the first aspect, and will not be elaborated here.

[0051] In a possible implementation manner, the processing unit is further used to transmit a first service flow using the connection that allows multiple service flows to share. The processing unit is further used to determine whether a second service flow is allowed to share the connection for transmitting the first service flow according to the multi-flow multiplexing parameters. The processing unit is further used to transmit the second service flow using the connection for transmitting the first service flow when the second service flow is allowed to share the connection for transmitting the first service flow.

[0052] In a possible implementation, the communication unit is further configured to receive encryption and / or integrity protection indication information from the SMF network element. The processing unit is further configured to perform encryption and / or integrity protection on the service flow according to the encryption and / or integrity protection indication information, or not perform encryption and / or integrity protection on the service flow.

[0053] When the communication device is a chip or a chip system in the UPF network element, the processing unit may be a processor, and the communication unit may be a communication interface. For example, the communication interface may be an input / output interface, a pin, a circuit, etc. The processing unit executes the instructions stored in the storage unit to enable the UPF network element to implement a communication method described in the fifth aspect or any possible implementation of the fifth aspect. The storage unit may be a storage unit within the chip (e.g., a register, a cache, etc.), or a storage unit outside the chip within the UPF network element (e.g., a read-only memory, a random access memory, etc.).

[0054] In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is enabled to execute the communication method described in the first aspect or any possible implementation of the first aspect.

[0055] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is enabled to execute the communication method described in the second aspect or any possible implementation of the second aspect.

[0056] In an eleventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is enabled to execute the communication method described in the third aspect or any possible implementation of the third aspect.

[0057] In a twelfth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is enabled to execute the communication method described in the fourth aspect or any possible implementation of the fourth aspect.

[0058] In a thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction runs on a computer, the computer is enabled to execute the communication method described in the fifth aspect or any possible implementation of the fifth aspect.

[0059] In a fourteenth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, cause the computer to execute a communication method described in the first aspect or any of the various possible implementations of the first aspect.

[0060] In a fifteenth aspect, the present application provides a computer program product including instructions that, when run on a computer, cause the computer to execute a communication method described in the second aspect or any of the various possible implementations of the second aspect.

[0061] In a sixteenth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, cause the computer to execute a communication method described in the third aspect or any of the various possible implementations of the third aspect.

[0062] In a seventeenth aspect, the present application provides a computer program product including instructions that, when run on a computer, cause the computer to execute a communication method described in the fourth aspect or any of the various possible implementations of the fourth aspect.

[0063] In an eighteenth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, cause the computer to execute a communication method described in the fifth aspect or any of the various possible implementations of the fifth aspect.

[0064] In a nineteenth aspect, an embodiment of the present application provides a communication system that includes any one or more of the following: an SMF network element described in the sixth aspect and various possible implementations thereof, and a UPF network element described in the eighth aspect and various possible implementations thereof.

[0065] In a possible implementation, the communication system may further include: a terminal device described in the seventh aspect and various possible implementations thereof.

[0066] In a twentieth aspect, an embodiment of the present application provides a communication device that includes a processor and a storage medium. The storage medium stores instructions that, when run by the processor, implement the communication method described in the first aspect or any of the various possible implementations of the first aspect.

[0067] In a twenty-first aspect, an embodiment of the present application provides a communication device that includes a processor and a storage medium. The storage medium stores instructions that, when run by the processor, implement the communication method described in the second aspect or any of the various possible implementations of the second aspect.

[0068] In a twenty-second aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium. The storage medium stores instructions that, when run by the processor, implement the communication method described in the third aspect or any possible implementation of the third aspect.

[0069] In a twenty-third aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium. The storage medium stores instructions that, when run by the processor, implement the communication method described in the fourth aspect or any possible implementation of the fourth aspect.

[0070] In a twenty-fourth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium. The storage medium stores instructions that, when run by the processor, implement the communication method described in the fifth aspect or any possible implementation of the fifth aspect.

[0071] In a twenty-fifth aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instructions to perform the communication method described in any one of the first aspect to any possible implementation of the first aspect.

[0072] In a twenty-sixth aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instructions to perform the communication method described in any one of the second aspect to any possible implementation of the second aspect.

[0073] In a twenty-seventh aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instructions to perform the communication method described in any one of the third aspect to any possible implementation of the third aspect.

[0074] In a twenty-eighth aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instructions to perform the communication method described in any one of the fourth aspect to any possible implementation of the fourth aspect.

[0075] In a twenty-ninth aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface. The communication interface and the at least one processor are interconnected by a line. The at least one processor is configured to run a computer program or instruction to perform the communication method described in any one of the possible implementation manners of the fifth aspect to the fifth aspect.

[0076] Among them, the communication interface in the chip can be an input / output interface, a pin, a circuit, etc.

[0077] In a possible implementation, the chip or the chip system described above in the present application further includes at least one memory, and instructions are stored in the at least one memory. The memory can be a storage unit inside the chip, such as a register, a cache, etc., or it can be a storage unit of the chip (such as a read-only memory, a random access memory, etc.).

[0078] It should be understood that the technical solutions of the second aspect to the twenty-ninth aspect of the embodiments of the present application correspond to those of the first aspect of the embodiments of the present application. The beneficial effects obtained by each aspect and the corresponding feasible implementation manners are similar and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0079] Figure 1 FIG. is a schematic diagram of an existing multi-PDU session access;

[0080] Figure 2 FIG. is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0081] Figure 3 FIG. is another schematic diagram of a network architecture provided by an embodiment of the present application;

[0082] Figure 4 FIG. is a schematic flowchart of a communication method provided by an embodiment of the present application;

[0083] Figure 5 FIG. is a schematic structural diagram of a communication device provided by an embodiment of the present application Figure 1 ;

[0084] Figure 6 FIG. is a schematic structural diagram of a communication device provided by an embodiment of the present application;

[0085] Figure 7 FIG. is a schematic structural diagram of a terminal device provided by an embodiment of the present application;

[0086] Figure 8 FIG. is a schematic structural diagram of a chip provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0087] For the convenience of clearly describing the technical solutions of the embodiments of the present application, in the embodiments of the present application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions and roles. For example, the first network and the second network are only used to distinguish different networks, and do not limit their sequence. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and the terms "first" and "second" do not necessarily mean different.

[0088] It should be noted that in the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific manner.

[0089] In the present application, "at least one" means one or more, and "a plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after. "At least one (item)" or its similar expression refers to any combination of these items, including any combination of single item (item) or plural items (items). For example, at least one (item) of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0090] The embodiments of the present application provide a communication method. The method of the embodiments of the present application can be applied in a fifth-generation mobile communication (5G) system, or can also be applied in a Long-Term Evolution (LTE). The 5G system is also referred to as a new radio communication system, a new access technology (NR), or a next-generation mobile communication system.

[0091] Exemplarily, Figure 2A schematic diagram of the network architecture provided by the embodiments of this application. This architecture not only supports the access of radio technologies (such as LTE, 5G radio access network (RAN), etc.) defined by the 3rd generation partnership project (3GPP) standard group to the core network (CN), but also supports the access of non-3GPP access technologies to the core network through the non-3GPP interworking function (N3IWF) or the next generation packet data gateway (ngPDG).

[0092] Among them, the network architecture includes a terminal device, an access network (AN), a core network, and a data network (DN). Among them, the access network device is mainly used to implement functions such as wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management; the core network device can include a management device and a gateway device. The management device is mainly used for device registration, security authentication, mobility management, and location management of the terminal device, etc. The gateway device is mainly used to establish a channel with the terminal device and forward data packets between the terminal device and the external data network on this channel; the data network can include network devices (such as servers, routers, etc.), and the data network is mainly used to provide various data service services for the terminal device. Exemplarily, the access network, core network, and data network in 5G are taken as examples for illustration.

[0093] The access network in 5G can be a radio access network ((R)AN). The (R)AN device in the 5G system can be composed of multiple 5G-(R)AN nodes. The 5G-(R)AN node can include: the access network of 3GPP, the access network of non-3GPP such as the access point (AP) of the WiFi network, the next generation base station (which can be collectively referred to as the new generation radio access network node (NG-RAN node). Among them, the next generation base station includes the new air interface base station (NR nodeB, gNB), the new generation evolved base station (NG-eNB), the central unit (CU), and the gNB in the separated form of the distributed unit (DU), etc.), the transmission receive point (TRP), the transmission point (TP), or other nodes.

[0094] The 5G core network (5G core / new generation core, 5GC / NGC) includes multiple functional units such as the access and mobility management function (AMF) network element, session management function (SMF) network element, user plane function (UPF) network element, authentication server function (AUSF) network element, policy control function (PCF) network element, application function (AF) network element, unified data management (UDM) network element, network slice selection function (NSSF) network element, network element function (NEF) network element, etc.

[0095] The AMF network element is mainly responsible for services such as mobility management and access management. The SMF network element is mainly responsible for session management, Dynamic Host Configuration Protocol function, selection and control of user plane functions, etc. The UPF network element is mainly responsible for connecting to the data network (DN) externally and functions such as routing and forwarding of user plane data packets, packet filtering, and execution of quality of service (QoS) control related functions. The DN mainly provides services for user equipment, such as providing mobile operator services, Internet services or third-party services, etc. The AUSF network element is mainly responsible for the authentication function of terminal equipment, etc. The PCF network element is mainly responsible for providing a unified policy framework for network behavior management, providing policy rules for control plane functions, obtaining registration information related to policy decisions, etc. It should be noted that these functional units can work independently or be combined to implement certain control functions, such as access control and mobility management functions such as access authentication, security encryption, and location registration of terminal equipment, as well as session management functions such as establishment, release, and change of user plane transmission paths. The UDM network element is for unified user data management and is mainly used to store user equipment subscription data.

[0096] In the 5G system, each functional unit can communicate through the Next Generation (NG) interface. For example, the terminal device can transmit control plane messages to the AMF network element through the NG interface 1 (abbreviated as N1), the RAN device can establish a user plane communication connection channel with the UPF through the NG interface 3 (abbreviated as N3), the AN / RAN device can establish a control plane signaling connection with the AMF network element through the NG interface 2 (abbreviated as N2), the UPF can interact with the SMF network element through the NG interface 4 (abbreviated as N4), the UPF can interact with the data network DN for user plane data through the NG interface 6 (abbreviated as N6), the AMF network element can interact with the SMF network element through the NG interface 11 (abbreviated as N11), the SMF network element can interact with the PCF network element through the NG interface 7 (abbreviated as N7), and the AMF network element can interact with the AUSF through the NG interface 12 (abbreviated as N12).

[0097] Exemplarily, such as Figure 3 shown Figure 3 is a schematic diagram of a specific network architecture when the core network supports untrusted non-3GPP access. Among them, the network architecture in the Home Public Land Mobile Network (HPLMN) is similar to Figure 2 the implementation in, which will not be elaborated here. Untrusted non-3GPP access can be untrusted Wireless Local Area Networks (WLAN) access. In this architecture, the terminal device can also interact with the AMF through untrusted non-3GPP access and the Non-3GPP Interworking Function / Non-3GPP Access Gateway (N3IWF), and the N3IWF network element can interact with the UPF through N3.

[0098] In addition, the core network can also support trusted non-3GPP access and / or fixed network access. Among them, the trusted non-3GPP network includes the trusted WALN network, and the fixed network includes fixed home network access, etc. The network side architecture is similar to the untrusted non-3GPP network architecture, replacing the N3IWF and the untrusted access network with a trusted Non-3GPP access network, or replacing the N3IWF with a trusted Non-3GPP access gateway and the untrusted access network with a trusted access network. Among them, the access network devices between the terminal device and the trusted Non-3GPP access gateway can include WLAN APs, Fixed Access Networks (FANs), switches, routers, etc.

[0099] For both trusted Non-3GPP access and untrusted Non-3GPP access, the core network side can adopt a point-to-point interface protocol as shown in Figure 2 the following, or adopt a service-based interface architecture that is consistent with the 3GPP access core network architecture. The embodiments of the present application do not make specific limitations in this regard.

[0100] In a possible implementation, 3GPP access technology and non-3GPP access technology can include multiple access systems or frequency bands and may be used simultaneously. For example, 3GPP access includes two access technologies, namely LTE of 4G and NG-RAN of 5G, accessing 5GC simultaneously. The wifi access of non-3GPP also includes two frequency bands accessing simultaneously. For example, the 5GHz and 2.4GHz wifi frequency bands access 5GC simultaneously. In a possible implementation, the UE can access the 5GC architecture through at least two (including all four used simultaneously) of the above four access methods.

[0101] The method processing of the embodiments of the present application can be applied to the above 5G 3GPP access architecture, or non-3GPP access architecture, or the architecture with 3GPP and non-3GPP accessing simultaneously, and can also be applied to the architecture with 5G cellular (NG-RAN) and 4G cellular (LTE) accessing simultaneously, etc. The embodiments of the present application do not make specific limitations on the network architecture.

[0102] Some terms in the embodiments of the present application are described below.

[0103] The data transmission involved in the embodiments of the present application can include the processes of data sending, data receiving, or data interaction. For example, when the terminal device performs data transmission with the UPF network element, it can include the terminal device sending data to the UPF network element, or the UPF network element sending data to the terminal device, or the terminal device sending data to the UPF network element and receiving data from the UPF, or the UPF network element sending data to the terminal device and receiving data from the UPF network element.

[0104] The connection that allows multiple service flows to share (which can also be referred to as the connection for service flow multiplexing, etc.) in the embodiments of this application can be: a Quick UDP Internet Connection (QUIC) connection, or an aggregated flow connection in a QUIC connection (the aggregated flow can be referred to as a stream), or a Multi-Path Quick UDP Internet Connection (MP-QUIC) connection, or an aggregated flow connection in an MP-QUIC connection, or a Stream Control Transmission Protocol (SCTP) connection, etc. The embodiments of this application do not specifically limit the connection that allows multiple service flows to share.

[0105] QUIC is a low-latency Internet transport layer protocol based on UDP. When the sender needs to transmit data using a QUIC connection, it needs to first establish a QUIC connection with the receiver, and then transmit the data to be transmitted based on the QUIC connection or the aggregated flow connection in the QUIC connection. The QUIC connection or the aggregated flow connection in the QUIC connection can support one or more access technologies or tunnels.

[0106] The QUIC connection involved in the embodiments of this application can be multiplexed by multiple service flows. For example, if a QUIC connection can be shared by different service flows of all PDU sessions of a terminal device, then this QUIC connection can be considered as a QUIC connection at the terminal device granularity. If a QUIC connection can be shared by one or more PDU sessions, then this QUIC connection can be considered as a QUIC connection at the PDU session granularity. If a QUIC connection can be shared by all service flows in one or more Quality of Service (QoS) flows of the same PDU session, then this QUIC connection can be a connection at the QoS flow granularity. If a QUIC connection can only be used by one service flow, then this QUIC connection can be a QUIC connection at the flow granularity.

[0107] The aggregated stream connection in the QUIC connection involved in the embodiments of this application can be multiplexed by multiple service streams. For example, if the aggregated stream connection in a QUIC connection can be shared by different service streams of all PDU sessions of a terminal device, then the aggregated stream connection in this QUIC connection can be considered as the aggregated stream connection in the QUIC connection at the terminal device granularity. If the aggregated stream connection in a QUIC connection can be shared by one or more PDU sessions, then the aggregated stream connection in this QUIC connection can be considered as the aggregated stream connection in the QUIC connection at the PDU session granularity. If the aggregated stream connection in a QUIC connection can be shared by all service streams in one or more QoS flows of the same PDU session, then the aggregated stream connection in this QUIC connection can be a connection at the QoS flow granularity. If the aggregated stream connection in a QUIC connection can only be used by one service stream, then the aggregated stream connection in this QUIC connection can be the aggregated stream connection in the QUIC connection at the stream granularity.

[0108] MP-QUIC is a low-latency multiplexed Internet transport layer protocol based on UDP. When the sender needs to use an MP-QUIC connection to transmit data, it needs to first establish an MP-QUIC connection with the receiver, and then transmit the data to be transmitted based on the MP-QUIC connection or the aggregated stream connection in the MP-QUIC connection.

[0109] The connection related to MP-QUIC can use the parameters in the connection related to QUIC. The difference between the connection related to MP-QUIC and the connection related to QUIC is that the connection related to MP-QUIC can include multiple sub-connections, each sub-connection can correspond to a sub-connection identifier, and each sub-connection can support or correspond to different access technologies or tunnels.

[0110] The MP-QUIC connection involved in the embodiments of this application can be multiplexed by multiple service streams. For example, if an MP-QUIC connection can be shared by different service streams of all PDU sessions of a terminal device, then this MP-QUIC connection can be considered as the MP-QUIC connection at the terminal device granularity. If an MP-QUIC connection can be shared by one or more PDU sessions, then this MP-QUIC connection can be considered as the MP-QUIC connection at the PDU session granularity. If an MP-QUIC connection can be shared by all service streams in one or more QoS flows of the same PDU session, then this MP-QUIC connection can be a connection at the QoS flow granularity. If an MP-QUIC connection can only be used by one service stream, then this MP-QUIC connection can be the MP-QUIC connection at the stream granularity.

[0111] The aggregated flow connection in the MP-QUIC connection involved in the embodiments of this application can be multiplexed by multiple service flows. For example, if the aggregated flow connection in an MP-QUIC connection can be shared by different service flows of all PDU sessions of a terminal device, then the aggregated flow connection in this MP-QUIC connection can be considered as the aggregated flow connection in the MP-QUIC connection at the terminal device granularity. If the aggregated flow connection in an MP-QUIC connection can be shared by one or more PDU sessions, then the aggregated flow connection in this MP-QUIC connection can be considered as the aggregated flow connection in the MP-QUIC connection at the PDU session granularity. If the aggregated flow connection in an MP-QUIC connection can be shared by all service flows in one or more QoS flows of the same PDU session, then the aggregated flow connection in this MP-QUIC connection can be a connection at the QoS flow granularity. If the aggregated flow connection in an MP-QUIC connection can only be used by one service flow, then the aggregated flow connection in this MP-QUIC connection can be the aggregated flow connection in the MP-QUIC connection at the flow granularity.

[0112] SCTP is a connection-oriented stream transport protocol that can provide stable and ordered data transfer services between two endpoints. When the sending end needs to use the SCTP connection to transmit data, it needs to first establish an SCTP connection with the receiving end, and then process the data to be transmitted. The SCTP connection can be shared by multiple service flows.

[0113] The service flows involved in the embodiments of this application can be service flows using the User Datagram Protocol (UDP) or other protocols. For example, the service flows of a PDU session can be: the PDU session established between the terminal device and the 5G Core Network (5GC) or the UDP service flow in this session; or, the PDN connection established between the terminal device and the EPC network or the UDP service flow in this PDN connection; or, the IP connection for non-seamless WLAN offload (such as WLAN access) by the terminal device through a non-3GPP access network or the UDP service flow in this connection.

[0114] In the embodiments of this application, the terminal device may support QUIC capabilities or MP-QUIC capabilities or SCTP capabilities. If the terminal device supports QUIC capabilities, then the subsequent terminal device can use the QUIC protocol to establish a QUIC connection or an aggregated flow connection in the QUIC connection. If the terminal device supports MP-QUIC capabilities, then the subsequent terminal device can use the MP-QUIC protocol to establish an MP-QUIC connection or an aggregated flow connection in the MP-QUIC connection. If the terminal device supports SCTP capabilities, then the subsequent terminal device can use the SCTP protocol to establish an SCTP connection.

[0115] The multi-flow connection parameters involved in the embodiments of this application can be used to indicate that the connection between the terminal device and the UPF network element allows multiple service flows to share. For example, the multi-flow connection parameters can be used to indicate that the connection between the terminal device and the UPF network element allows different service flows of all PDU sessions of the terminal device to share, or to indicate that the connection between the terminal device and the UPF network element allows multiple PDU sessions to share, or to indicate that the connection between the terminal device and the UPF network element allows multiple service flows in one PDU session to share, or to indicate that the connection between the terminal device and the UPF network element allows all service flows in one or more QoS flows to share, etc.

[0116] Exemplarily, the multi-flow connection parameters can include one or more of service flow description parameters or multi-flow multiplexing parameters.

[0117] In a possible implementation manner, the service flow description parameters can include one or more of the following: one or more pieces of service flow description information, application identifier, one or more QoS flow identifiers (QoS flow ID, QFI), one or more PDU session identifiers, and terminal device identifier.

[0118] The service flow description information can be at least one of the service flow network interconnection protocol (internet protocol, IP) five-tuple description information, and the five-tuple description information can be: source IP address, destination IP address, source port number, destination port number, and protocol type; or the service flow description information can be the PDU session identifier (when all service flows in this PDU session use connection transmission); or the service flow description information can be at least one of the ethernet header information, for example, source media access control (media access control, MAC) address and destination MAC address, virtual local area network (virtual local area network, VLAN) identifier; etc. Then, the subsequent terminal device can transmit the service flows containing this service flow description information using the same connection. The number of pieces of service flow description information can be one or more, and the embodiments of this application do not make specific limitations on this.

[0119] The application identifier can be used to identify the service flow of a specific application program. Then, the subsequent terminal device can transmit the service flows containing this application identifier using the same connection. The number of application identifiers can be one or more, and the embodiments of this application do not make specific limitations on this.

[0120] The QoS flow identifier (QFI) can be an identifier for multiple service flows that satisfy a certain relationship for QoS. Subsequently, the terminal device can use the same connection to transmit multiple service flows that include the QoS flow identifier. For example, the service flow description parameter includes QFI 1 and QFI 2, indicating that the service flows in QFI 1 and the service flows in QFI 2 can share the same connection for data transmission.

[0121] The PDU session identifier can be an identifier for the established or updated PDU. Subsequently, the terminal device can use the same connection to transmit multiple service flows that include the PDU session identifier. In a possible implementation, the service flow description parameter is transmitted between the terminal device and the UPF network element. Then, the service flow description parameter can include one or more N4 session identifiers or PDU session identifiers, indicating that the same connection is used to transmit multiple service flows corresponding to the N4 session identifier or the PDU session identifier. The N4 session identifier and the PDU session identifier can have a one-to-one correspondence.

[0122] The terminal device identifier can be a symbol, number, etc. used to identify the terminal device. For example, it can be the IP address or ID of the terminal device. The embodiments of the present application do not make specific limitations on this. Subsequently, the same connection can be used to transmit multiple service flows that include the terminal device identifier.

[0123] In a possible implementation, the multi-flow multiplexing parameter can be used to represent the QUIC connection information related to the service flow, the QUIC aggregated flow connection information related to the service flow, the MP-QUIC connection information related to the service flow, the MP-QUIC aggregated flow connection information related to the service flow, or the SCTP connection information related to the service flow.

[0124] Exemplarily, the multi-flow multiplexing parameter can include one or more of the following: protocol indication information, multi-flow multiplexing indication information, connection identifier, QoS flow granularity indication information, PDU session granularity indication information, terminal device granularity indication information.

[0125] The protocol indication information can be QUIC method indication information or MP-QUIC method indication information or SCTP method indication information. The QUIC method indication information can be used to indicate that the service flow of the PDU session is transmitted using a QUIC connection or an aggregated flow connection in the QUIC connection. The QUIC method indication information can be a character, number, etc. The MP-QUIC method indication information can be used to indicate that the service flow of the PDU session is transmitted using an MP-QUIC connection or an aggregated flow connection in the MP-QUIC connection. The MP-QUIC method indication information can be a character, number, etc. The SCTP method indication information can be used to indicate that the service flow of the PDU session is transmitted using an SCTP connection. The SCTP method indication information can be a character, number, etc.

[0126] The multi-stream multiplexing indication information can be used to indicate that a QUIC connection is allowed to be shared by multiple service flows. The multi-stream multiplexing indication information can be a character, a string, a number, etc. For example, when the multi-stream multiplexing indication information is set to True, it means that the service flow can share a QUIC connection with other service flows; when the multi-stream multiplexing indication information is set to False, it means that the service flow cannot share a QUIC connection with other service flows. For another example, when the multi-stream multiplexing indication information is set to False, it means that the service flow can share a QUIC connection with other service flows; when the multi-stream multiplexing indication information is set to True, it means that the service flow cannot share a QUIC connection with other service flows. For another example, the multi-stream multiplexing indication information can be a specified character, string, number, etc. When the multi-stream multiplexing indication information is included in the multi-stream multiplexing parameter, it means that the service flow can share a QUIC connection with other service flows; when the multi-stream multiplexing indication information is not included in the multi-stream multiplexing parameter, it means that the service flow cannot share a QUIC connection with other service flows. For another example, the multi-stream multiplexing indication information can be a specified character, string, number, etc. When the multi-stream multiplexing indication information is included in the multi-stream multiplexing parameter, it means that the service flow cannot share a QUIC connection with other service flows; when the multi-stream multiplexing indication information is not included in the multi-stream multiplexing parameter, it means that the service flow can share a QUIC connection with other service flows.

[0127] The connection identifier is used to indicate the connection identifier corresponding to the service flow. For example, the connection identifier can be at least one of a QUIC connection identifier, an aggregated flow connection identifier in a QUIC connection, an MP-QUIC connection identifier, an aggregated flow connection identifier in an MP-QUIC connection, or an SCTP connection identifier, or other values that identify a connection. For example, when service flows share an MP-QUIC connection, the connection identifier is the MP-QUIC connection identifier, or the connection identifier is used to represent the MP-QUIC connection. When service flows share an aggregated flow connection in an MP-QUIC connection, the connection identifier is the aggregated flow connection identifier, or the connection identifier is the MP-QUIC connection identifier (or the value used to identify the MP-QUIC connection) and the aggregated flow connection identifier. The connection identifier can be used to implement flow aggregation at multiple granularities, including flow aggregation at the service flow granularity (for example, if multiple service flows have the same connection identifier, then multiple service flows share the connection), or flow aggregation at the QoS flow granularity (for example, if one or more service flows of QoS flows have the same connection identifier, then one or more QoS flows share the connection), or flow aggregation at the PDU granularity (for example, if one or more service flows of PDU sessions have the same connection identifier, then one or more PDU sessions share the connection). In a possible implementation, the multi-flow connection parameters can include service flow description information and a connection identifier. When different service flows (for example, service flows including different service flow description information) correspond to the same connection identifier, it can indicate that these different service flows can share the same connection.

[0128] The QoS flow granularity indication information is used to indicate that the connection allows one or more service flows of QoS flows (QoS flow) to share. The connection can be a QUIC connection, an aggregated flow connection in a QUIC connection, an MP-QUIC connection, an aggregated flow connection in an MP-QUIC connection, or an SCTP connection, etc. Subsequently, the terminal device or the UPF network element can select one or more service flows of QoS flows and use the shared connection for transmission.

[0129] The PDU session granularity indication information is used to indicate that the connection allows service flows of PDU sessions to share. The connection can be a QUIC connection, an aggregated flow connection in a QUIC connection, an MP-QUIC connection, an aggregated flow connection in an MP-QUIC connection, or an SCTP connection, etc. Subsequently, the terminal device or the UPF network element can select multiple service flows of one or more PDU sessions and use the shared connection for transmission.

[0130] The terminal device granularity indication information is used to indicate that the business flows of a terminal device are allowed to share a QUIC connection. This connection can be a QUIC connection, an aggregated flow connection in a QUIC connection, an MP-QUIC connection, an aggregated flow connection in an MP-QUIC connection, or an SCTP connection, etc. Subsequently, any business flow in the terminal device can be transmitted using the shared connection by the terminal device or the UPF network element.

[0131] The first message sent by the terminal device involved in the embodiments of this application to the SMF network element can be a PDU session establishment or update request message, or a PDU session establishment or update request message sent for establishing a multi-access PDU (MA PDU) session, or any other arbitrary message. The embodiments of this application do not make specific limitations on this. Sending the first message by the terminal device to the SMF network element can be used to request the establishment or update of a PDU session.

[0132] The second message received by the terminal device involved in the embodiments of this application from the SMF network element can be a message indicating the successful establishment of a PDU session, or a message indicating the successful update of a PDU session, or any other arbitrary message. The embodiments of this application do not make specific limitations on this. Receiving the second message by the terminal device from the SMF network element can be used to indicate the successful establishment or update of a PDU session.

[0133] The following uses specific embodiments to elaborate in detail on the technical solutions of this application and how the technical solutions of this application solve the above technical problems. These several specific embodiments below can be implemented independently or in combination with each other. Concepts or processes that are the same or similar may not be repeated in some embodiments.

[0134] Figure 4 The flowchart of a communication method provided for the embodiments of this application includes the following steps:

[0135] S401: The terminal device sends a message to the session management function SMF network element for requesting the establishment or update of a PDU session.

[0136] In a possible implementation manner, the terminal device can encapsulate the above message for requesting the establishment or update of a PDU session in a non-access stratum (NAS) transport message and send it to the AMF network element, and the AMF network element forwards the message for requesting the establishment or update of a PDU session to the SMF network element.

[0137] In a possible implementation, the terminal device may send a NAS transport message to the AMF network element through the RAN. The NAS transport message includes a message requesting the establishment or update of a PDU session, and the message requesting the establishment or update of the PDU session carries indication information for indicating the protocol capabilities supported by the terminal device. The AMF network element further forwards the message requesting the establishment or update of the PDU session to the SMF network element. The indication information of the protocol capabilities may be: indication information of the QUIC capability, indication information of the MP-QUIC capability, indication information of the SCTP capability, etc.

[0138] In a possible implementation, the terminal device sends a NAS transport message to the AMF network element. The NAS transport message includes indication information of the protocol capabilities supported by the terminal device and a message requesting the establishment or update of a PDU session. The AMF network element forwards the message requesting the establishment or update of the PDU session and the protocol capability indication to the SMF network element.

[0139] In a possible implementation, the NAS transport message includes a message requesting the establishment or update of a PDU session and indication information of the protocol capabilities supported by the terminal device. The AMF network element selects an SMF network element that supports the protocol function based on the indication information of the protocol capabilities, and further forwards the message requesting the establishment of the PDU session and the indication information of the protocol capabilities supported by the terminal device to the SMF network element.

[0140] The SMF network element may receive a first message from the terminal device, or the first message and the indication information of the protocol capabilities supported by the terminal device.

[0141] S402: The SMF network element determines that multiple service flows related to the PDU session share the same connection.

[0142] In the embodiments of the present application, the SMF network element may determine that multiple service flows related to the PDU session share the same connection based on local policies and / or parameters received from other devices (such as the terminal device, the PCF network element, the UDM network element, etc.). The SMF network element may also determine that multiple service flows related to the PDU session share the same connection based on the policy information (which may also be referred to as PCF indication information) sent by the PCF network element. etc.

[0143] In a possible implementation, the SMF network element may use one or more of the following to determine that multiple service flows related to the PDU session share the same connection: security or encryption information of the service flow, QoS parameters of the service flow, destination address of the service flow, data network name (DNN) of the service flow, transport protocol of the service flow, type of the service flow, splitting mode of the service flow.

[0144] In the embodiments of the present application, the security or encryption information of a service flow can be used to represent the security and encryption requirements of the service flow. For example, the security or encryption information of a service flow can include one or more of: indication information for indicating whether encryption is required, indication information for indicating whether integrity protection is required, security level information, or encryption algorithms.

[0145] Exemplarily, if the security and encryption requirements of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection. For example, if multiple service flows carry the same indication information for indicating that encryption is required, the SMF network element can determine that the multiple service flows can share the same connection. For another example, if multiple service flows carry the same indication information for indicating that integrity protection is required, the SMF network element can determine that the multiple service flows can share the same connection. For another example, if multiple service flows carry the same security level information, the SMF network element can determine that the multiple service flows can share the same connection. For another example, if multiple service flows carry the same encryption algorithm, the SMF network element can determine that the multiple service flows can share the same connection.

[0146] Exemplarily, the SMF network element can determine whether service flows can be aggregated into the same QoS flow based on the security or encryption information of the service flows. When multiple service flows have the same security or encryption information, the multiple service flows can be mapped to the same QoS flow to achieve security encryption at the QoS flow granularity.

[0147] Exemplarily, the SMF network element can determine whether the service flows of a PDU session can be aggregated into the same connection based on the security or encryption information of the service flows. When all the service flows of a PDU session have the same security or encryption information, the multiple service flows can be mapped to the same connection to achieve security encryption at the PDU session granularity.

[0148] The security or encryption information of a service flow can be obtained by the SMF network element from the subscription data of the terminal device, or received by the SMF network element from the PCF network element, or locally configured by the SMF network element. Alternatively, the SMF receives an indication that the service flow needs encryption and / or integrity protection from the PCF network element, and the SMF network element determines encryption between the UE and the UPF network element for the service flow based on the access technology for transmitting the service flow. The above access technologies include 3GPP access technologies, non-3GPP access technologies, wifi access technologies, or fixed network or wired access technologies, etc. For example, when the service flow accesses from non-3GPP or wifi or fixed network or wired access and the SMF network element receives an indication that encryption and / or integrity protection is required sent by the PCF network element, the SMF network element determines that encryption and / or integrity protection is implemented between the UE and the UPF network element for the service flow. The embodiments of the present application do not make specific limitations on the source of the security or encryption information of the service flow.

[0149] In the case where the service flow carries security or encryption information, the subsequent SMF network element can send the security or encryption information to the UPF network element and the terminal device respectively, so that when the UPF network element and the terminal device perform service flow transmission, the service flow is encrypted, enhancing the security of service flow transmission.

[0150] In the embodiments of this application, the service flow QoS parameter can be used to represent the QoS parameter of the service flow. If the QoS parameters of multiple service flows are the same or satisfy a certain relationship, the SMF network element can determine that the multiple service flows can share the same connection. For example, the QoS parameter of the service flow can include at least one of 5QI (5G QoS Identifier), allocation and retention priority (ARP), bandwidth, delay, and packet loss rate parameter. When one or more of the QoS parameters of multiple service flows are the same, the same connection can be shared. For example, if the 5QI of service flow 1 is 1 and the 5QI of service flow 2 is 1, then service flow 1 and service flow 2 can share the same connection.

[0151] In the embodiments of this application, it can also be determined whether multiple service flows can share the same connection based on the QoS type of the service flow. For example, if multiple service flows are all non-guaranteed bit rate (non-GBR) service flows, the SMF network element can determine that the multiple service flows can share the same connection.

[0152] In the embodiments of this application, the service flow destination address can be the destination IP address or the destination MAC address of the service flow. If the destination addresses of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection.

[0153] In the embodiments of this application, the data network name (DNN) of the service flow can be obtained by the SMF network element from the subscription data of the terminal device. If the DNNs of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection. This solution can enable one or more PDU sessions to share the same connection. For example, if the DNN corresponding to PDU1 is Internet and the DNN corresponding to PDU session 2 is Internet, then all service flows of PDU session 1 and PDU session 2 can share the same connection.

[0154] In the embodiments of the present application, the transport protocol of the service flow can be UDP or Transmission Control Protocol (TCP). If the transport protocols of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection. For example, if service flow 1 is a service flow transmitted by UDP and service flow 2 is also a service flow transmitted by UDP, then service flow 1 and service flow 2 share the connection.

[0155] In the embodiments of the present application, the types of service flows can include video services, voice services, game services, web browsing services, etc. If the types of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection.

[0156] In the embodiments of the present application, the traffic splitting mode of the service flow can be a load balancing traffic splitting mode, a priority traffic splitting mode (for example, preferentially using an access technology with a high priority to transmit the service flow), a primary / backup traffic splitting mode, a minimum latency traffic splitting mode (for example, using a link with the minimum latency to transmit the service flow), etc. If the traffic splitting modes of multiple service flows are the same, the SMF network element can determine that the multiple service flows can share the same connection.

[0157] In addition, in the embodiments of the present application, connection sharing at the granularity of multiple PDU sessions or UE granularity can also be implemented based on at least one of slice information or session and service continuity (SSC) mode information. For example, if multiple PDU sessions belong to the same slice, all service flows of the above PDU sessions can share the same connection. Or if the SSC modes of multiple PDUs are the same, all service flows of the above PDU sessions can share the same connection.

[0158] In the implementation manner where the SMF network element determines that multiple service flows related to a PDU session share the same connection based on the PCF indication information of the PCF network element, the SMF network element needs to interact with the PCF network element, which will be described in subsequent embodiments and will not be elaborated here.

[0159] In a possible implementation manner, the SMF network element can combine multiple policies among the subscription data of the terminal device, the local configuration policy, or the policy information obtained from the PCF network element, and then the SMF network element can comprehensively determine that multiple service flows in the PDU session share the same connection.

[0160] For example, the SMF network element can determine that multiple service flows in the PDU session share the same connection when multiple policies among the subscription data of the terminal device, the local configuration policy, or the policy information obtained from the PCF network element indicate consistency.

[0161] For another example, when there is consistency among multiple indications in the subscription data of the terminal device, the local configuration policy, or the policy information obtained from the PCF network element, the information with a higher priority can be selected to determine that multiple service flows in the PDU session share the same connection. The priorities of the subscription data of the terminal device, the local configuration policy, and the policy indication information obtained from the PCF network element can be set according to the actual application scenario. For example, it can be defined that the priorities of the three types of information increase or decrease in sequence, or it can be defined that the policy information of the PCF has the highest priority, etc.

[0162] In the embodiment of this application, when the SMF network element determines that multiple service flows related to the PDU session share the same connection, the multi-flow connection parameters can be determined based on the parameters and the like on which the determination that multiple service flows related to the PDU session share the same connection is based, and the multi-flow connection parameters are sent to the UPF network element.

[0163] S403: The SMF network element sends the multi-flow connection parameters to the UPF network element.

[0164] The UPF network element can establish a same connection shared by multiple service flows for the service flows based on the multi-flow connection parameters configured by the SMF network element.

[0165] For example, the UPF network element can store the multi-flow connection parameters sent by the SMF network element. Then, when the UPF network element performs service flow transmission, it can transmit the same connection shared by multiple service flows. In a possible implementation manner, the SMF network element sends the correspondence between the flow description parameters and the encryption and / or integrity protection indication information to the UPF network element, which is used to indicate that the above service flows need to perform encryption and / or integrity protection. For example, when the encryption and / or integrity protection indication information is included, it means that the relevant service flows need to perform encryption and / or integrity protection. For those that do not include the encryption and / or integrity protection indication, it means that the relevant service flows do not need to perform encryption and / or integrity protection.

[0166] S404: The UPF network element sends an N4 session reply message to the SMF network element. The N4 session reply message can be used to indicate that the N4 session is successfully established.

[0167] Optionally, the UPF network element may modify the multi-flow connection parameters sent by the SMF network element. For example, the UPF network element updates the connection identifier in the multi-flow multiplexing parameters sent by the SMF network element, or when the UPF network element determines that multiple service flows share the connection, the UPF network element updates the connection identifier in the multi-flow multiplexing parameters sent by the SMF network element. If the UPF network element updates the multi-flow connection parameters, the UPF network element sends the updated multi-flow connection parameters to the SMF network element in the N4 session reply message.

[0168] In another possible implementation, the SMF network element does not need to configure multi-flow connection parameters in step S402 above. The SMF network element can determine that multiple service flows related to the PDU session share the same connection based on the indication information sent by the UPF network element in S404. For example, the UPF network element determines that multiple service flows in the PDU session share the same connection and sends it to the SMF network element through multi-flow connection parameters. The indication information sent by the UPF network element can be multi-flow connection parameters. This process will be described in detail in subsequent embodiments and will not be elaborated here.

[0169] S405: The SMF network element sends a second message and multi-flow connection parameters to the terminal device. The second message is a message indicating the successful establishment or update of the PDU session. Optionally, the SMF sends encryption and / or integrity protection indication information to the UE.

[0170] In one possible implementation, the above encryption and / or integrity protection indication information is used to indicate encryption and / or integrity protection of the service flow, or the above encryption and / or integrity protection indication information is used to indicate that the service does not require encryption and / or integrity protection.

[0171] In the embodiments of the present application, the multi-flow connection parameters can be sent in the second message. For example, the second message carrying the multi-flow connection parameters can be encapsulated in the NAS transport message and sent. The multi-flow connection parameters can also be sent separately from the second message. For example, the multi-flow connection parameters and the second message can be encapsulated in the NAS transport message and sent separately. The embodiments of the present application do not make specific limitations on this.

[0172] The multi-flow connection parameters sent by the above SMF network element to the terminal device can be the same as or different from the multi-flow connection parameters sent by the SMF network element to the UPF network element in S403. For example, the multi-flow connection parameters sent by the SMF network element to the terminal device include service flow description information and connection identifiers, and the multi-flow connection parameters sent by the SMF network element to the UPF network element include service flow description information and protocol indication information.

[0173] In one possible implementation, the SMF network element sends the correspondence between the flow description parameters and the encryption and / or integrity protection indication information to the terminal device to indicate that the above service flow needs to be encrypted and / or integrity protected. For example, when the encryption and / or integrity protection indication information is included, it indicates that the relevant service flow needs to be encrypted and / or integrity protected. For those without the encryption and / or integrity protection indication, it indicates that the relevant service flow can be not encrypted and / or integrity protected.

[0174] S406: The terminal device and the UPF network element perform data transmission according to the connection shared by multiple service flows.

[0175] In summary, in the embodiments of the present application, the network side can control the establishment of a connection that allows multiple service flows to be shared between the terminal device and the UPF network element, thereby saving the connection establishment process and improving the transmission efficiency.

[0176] For Figure 4 the corresponding embodiment, in a possible implementation, the implementation of S402 can be: The SMF network element can determine that multiple service flows in the PDU session share the same connection according to the PCF indication information (which can also be referred to as PCF policy information) obtained from the PCF network element.

[0177] Exemplarily, as Figure 4 shown, S402 may include: S4021, the SMF network element sends a policy request to the PCF network element. S4022, the PCF network element determines that multiple service flows in the PDU session share the same connection (which can also be referred to as the PCF policy). S4023, the PCF network element sends the PCF policy information to the SMF network element, and the PCF policy information may include one or more of the above-mentioned service flow description parameters or multi-flow multiplexing parameters.

[0178] In the embodiments of the present application, the basis for the PCF network element to determine that multiple service flows in the PDU session share the same connection is similar to the basis for the SMF network element to determine that multiple service flows in the PDU session share the same connection. Exemplarily, the PCF network element can use one or more of the following to determine that multiple service flows related to the PDU session share the same connection: the security or encryption information of the service flow, the service flow QoS parameters, the service flow destination address, the data network name (DNN) of the service flow, the transport protocol of the service flow, the type of the service flow, the splitting mode of the service flow. Details are not described herein again.

[0179] In a possible implementation, the policy request sent by the SMF network element to the PCF network element may include indication information for indicating the protocol capabilities supported by the terminal device (such as indication information of QUCI capabilities or MP-QUIC capabilities or SCTP capabilities), indicating the protocol that can be used when the service flows in the PDU session are split and aggregated. The PCF network element can determine whether multiple service flows in the PDU session can share the same connection according to the indication information of the protocol capabilities supported by the terminal device, as well as the PCF network element's local policy or the terminal subscription data, etc. When the PCF network element determines that multiple service flows in the PDU session share the same connection, it can send the PCF policy information to the SMF network element, and the PCF policy information includes information for indicating that multiple service flows in the PDU session share the same connection.

[0180] In a possible implementation, the PCF network element may also determine the granularity of the connection that allows multiple traffic flows to share. For example, whether the connection is allowed to be shared by traffic flows in different PDU sessions or by different traffic flows in the same PDU session. When the connection allows multiple PDU sessions to share, the PCF indication information may include at least one of the terminal device granularity indication information and the identifiers of other PDU sessions allowed to share the connection. When the connection allows multiple traffic flows in a PDU session to share, the PCF policy may include PDU session granularity indication information.

[0181] In a possible implementation, the PCF network element receives a policy request from the SMF network element. When the traffic flows in the PDU session are UDF traffic flows, the PCF network element may determine whether multiple traffic flows in the PDU session can share the same connection based on the local policy of the PCF network element or the terminal subscription data, etc. When the PCF network element determines that multiple traffic flows in the PDU session share the same connection, it may send PCF policy information to the SMF network element, and the PCF indication information includes information indicating that multiple traffic flows in the PDU session share the same connection.

[0182] In a possible implementation, the PCF network element sends the correspondence between traffic flow description parameters and encryption and / or integrity protection indication information to the SMF network element to indicate whether the above-mentioned traffic flows need or do not need encryption and / or integrity protection. Subsequently, the SMF network element may determine whether multiple traffic flows can converge to the same connection based on the security or encryption information of the traffic flows. When multiple traffic flows have the same encryption and / or integrity protection indication information, the multiple traffic flows can be mapped to the same connection, which will not be elaborated here. For example, the PCF network element may determine whether a traffic flow needs encryption and / or integrity protection based on at least one of the local policy, user subscription data, or the access technology through which the traffic flow is transmitted. The above access technologies include 3GPP access technology, non-3GPP access technology, wifi access technology, or fixed network or wired access technology, etc. For example, when the PCF network element senses that the traffic flow is transmitted through non-3GPP access technology or through fixed network or wired access technology, the PCF network element issues an indication of the need for encryption and / or integrity protection, or the PCF network element issues an indication of the non-need for encryption and / or integrity protection.

[0183] For Figure 4 In a corresponding embodiment, in a possible implementation manner, the implementation of S402 may be: The SMF network element may determine that multiple traffic flows in the PDU session share the same connection according to the indication of the UPF network element.

[0184] In the embodiments of the present application, the basis for the UPF network element to determine that multiple traffic flows in a PDU session share the same connection is similar to the basis for the SMF network element to determine that multiple traffic flows in a PDU session share the same connection. Exemplarily, the UPF network element may use one or more of the following to determine that multiple traffic flows related to a PDU session share the same connection: security or encryption information of the traffic flow, QoS parameters of the traffic flow, destination address of the traffic flow, data network name (DNN) of the traffic flow, transport protocol of the traffic flow, type of the traffic flow, and splitting mode of the traffic flow. Details are not described herein again.

[0185] In the embodiments of the present application, the SMF network element in S403 may not send multi-flow connection parameters. In a possible implementation, S403 may be replaced by the SMF network element sending traffic flow description parameters and QUIC method indication information or MP-QUIC method indication information or SCTP method indication information to the UPF network element, indicating the protocol that can be used when traffic flows in a PDU session are split and aggregated. In addition, the SMF network element may send QoS parameters related to the traffic flow, etc., to the UPF network element. The UPF network element may determine whether multiple traffic flows in a PDU session can share the same connection based on the above information sent by the SMF network element and / or local policies, etc. When the UPF network element determines that multiple traffic flows in a PDU session share the same connection, it may send information (such as multi-flow connection parameters) for indicating that multiple traffic flows in the PDU session share the same connection to the SMF network element.

[0186] In a possible implementation, the UPF network element may also determine the granularity of the connection that allows multiple traffic flows to share. For example, whether the connection is allowed to be shared by traffic flows in different PDU sessions or by different traffic flows in the same PDU session. When the connection allows multiple PDU sessions to share, the UPF network element may send at least one of terminal device granularity indication information and identification of other PDU sessions allowed to share the connection to the SMF network element. When the connection allows multiple traffic flows in a PDU session to share, the UPF network element may send PDU session granularity indication information to the SMF network element.

[0187] In a possible implementation, the PCF network element sends the correspondence between traffic flow description parameters and encryption and / or integrity protection indication information to the SMF network element, indicating whether the above traffic flow needs or does not need encryption and / or integrity protection. Subsequently, the SMF network element sends the correspondence between traffic flow description parameters and encryption and / or integrity protection indication information to the UPF network element. The UPF network element may determine whether multiple traffic flows can converge to the same connection based on the security or encryption information of the traffic flow. When multiple traffic flows have the same encryption and / or integrity protection indication information, the multiple traffic flows may be mapped to the same connection. Details are not described herein again.

[0188] In a possible implementation, Figure 4 In the corresponding embodiment, the connection shared by multiple service flows is a QUIC connection.

[0189] Exemplarily, the SMF network element may further determine QUIC function parameters and send the QUIC function parameters to the terminal device and the UPF network element, so that the terminal device and the UPF network element can establish a QUIC connection according to the QUIC function parameters. The QUIC function parameters may include one or more of the following: QUIC function IP address, QUIC function port number, QUIC connection identifier, QUIC omitted connection identifier indication parameter, QUIC version information, security parameter or transmission parameter.

[0190] The QUIC function IP address is the IP address used for the QUIC connection. For example, the IP address of the QUIC function on the network side (or called the QUIC proxy function), such as the IP address corresponding to the QUIC function (or QUIC proxy function) implemented on the UPF network element. For example, when the terminal device performs QUIC encapsulation on the service flow, the QUIC function IP address may be encapsulated. In a specific application, the QUIC function IP address may be data such as characters or numbers for identifying the address.

[0191] The QUIC function port can be used to indicate the port number corresponding to the QUIC connection, including the port number corresponding to the QUIC function on the network side and / or the QUIC function on the terminal side. In a specific application, the QUIC function port may be data such as characters or numbers for identifying the port number.

[0192] The QUIC connection identifier is the connection identifier assigned by the SMF network element or the UPF network element for a QUIC connection. It can jointly identify a QUIC connection with the QUIC connection identifier assigned to the terminal device, or identify a QUIC connection based on the connection identifier assigned by the SMF network element or the UPF network element. In a possible implementation, if the UPF network element receives the QUIC first connection identifier, the UPF network element may store the above QUIC first connection identifier. Subsequently, the UPF network element may encapsulate the service data packet using at least one of the QUIC first connection identifier or the QUIC second connection identifier assigned by the SMF network element or the UPF network element. For example, encapsulate the service data packet using the QUIC protocol header and carry the QUIC first connection identifier, or the QUIC second connection identifier, or both the QUIC first connection identifier and the QUIC second connection identifier in the above QUIC protocol header.

[0193] The QUIC version information is the QUIC version used by the QUIC connection. The QUIC version information can be the QUIC version information supported by the SMF network element or the UPF network element, or the QUIC version information determined by the SMF network element or the UPF network element according to the version information supported by the terminal device.

[0194] The security parameters can be used to encrypt the data transmitted in the QUIC connection. For example, the security parameters can include encryption algorithm information, encryption indication, or non-encryption indication (for example, indicating an empty encryption algorithm means no encryption), or security certificates, etc. In a specific application, the security parameters can be characters, numbers, etc.

[0195] The transmission parameters can be used to control the transmission process of the QUIC connection. The transmission parameters can be, for example, idle_timeout, stateless_reset_token, max_packet_size, etc. For specific details, reference can be made to the definition of transmission parameters in the QUIC protocol, which will not be elaborated here.

[0196] The QUIC omit connection identifier indication parameter indicates that the QUIC connection does not use a connection identifier. If the QUIC function parameters include the QUIC omit connection identifier indication parameter, then after the subsequent terminal device establishes a QUIC connection and performs QUIC packet header encapsulation on the service flow, the connection identifier can be not used. When the UPF network element receives the QUIC omit connection identifier indication parameter, the UPF network element can not carry the connection identifier in the QUIC packet header when encapsulating data using the QUIC protocol header.

[0197] The terminal device and the UPF network element can transmit multiple service flows using the same QUIC connection.

[0198] Exemplarily, in the uplink, when the terminal device initiates a QUIC connection based on the multi-stream multiplexing parameters and sends service flow data packets transmitted using the QUIC connection to the UPF network element, QUIC packet header encapsulation can be performed on the service flow data packets, and one or more of the QUIC function parameters can be carried in the QUIC packet header. For example, the QUIC connection identifier can be carried in the QUIC packet header. The destination IP address or port number in the QUIC packet header can be set to the IP address or port number of the QUIC function. Based on the security parameters, the service flow data packets can be securely encrypted. If a QUIC connection with the QUIC omit connection identifier indication parameter is used, the QUIC connection identifier is not carried in the QUIC packet header.

[0199] When there is a new service flow transmitted based on a QUIC connection, the terminal device can determine whether there is an existing QUIC connection available based on the multi-flow multiplexing parameters. If so, the UE uses the existing QUIC connection to transmit service data packets. For example, if the new service flow belongs to QFI 1 and QFI 1 shares the same QUIC connection, the new service flow can be transmitted using the QUIC connection of the service flow of QFI 1. In an alternative implementation, if the above QUIC connection has a QUIC connection identifier, the terminal device can use this QUIC connection identifier to encapsulate the service flow data packet.

[0200] Exemplarily, in the downlink, when the UPF network element initiates a QUIC connection based on the multi-flow multiplexing parameters to send service flow data packets transmitted using the QUIC connection to the terminal device, it can perform QUIC header encapsulation on the service flow data packets, and one or more of the QUIC function parameters can be carried in the QUIC header.

[0201] If the QUIC connection is a QUIC connection at the PDU session granularity, the UPF network element can use this QUIC connection to transmit multiple service flows of this PDU session. If this QUIC connection uses a connection identifier, the UPF uses the above connection identifier to encapsulate the service flow data packets of this PDU session.

[0202] If the QUIC connection is a QUIC connection at the QoS flow granularity, the UPF network element can use different QUIC connections to transmit the service data packets of the QoS flow. For example, the UPF network element can establish a QUIC connection 1 for QoS flow1, and establish a QUIC connection 2 for QoS flow2 and QoS flow3. The service flow data packets of QoS flow1 are transmitted using QUIC connection 1. The service flow data packets of QoS flow2 or QoS flow3 are transmitted using QUIC connection 2. If this QUIC connection uses a connection identifier, the UPF uses the relevant connection identifier to encapsulate the service data packets of this QoS flow.

[0203] In a possible implementation, if the QoS flow corresponding to the QUIC connection is selected by the UPF network element, the UPF network element can send the QFI bound to the QUIC connection to the SMF network element. For example, if the UPF network element establishes the same QUIC connection for QFI1 and QFI2, the UPF notifies the SMF that this QUIC connection corresponds to QFI1 and QFI2. If this QUIC connection uses a connection identifier and is allocated by the UPF network element, the UPF network element can notify the connection identifier to the SMF network element. For example, for service flows transmitted using the same QUIC connection, the UPF network element returns the same connection identifier to the SMF network element.

[0204] If the QUIC connection is a terminal device - granularity QUIC connection, the UPF network element can transmit some or all of the traffic data packets of the PDU session through this QUIC connection.

[0205] In a possible implementation, Figure 4 In the corresponding embodiment, the connection shared by multiple traffic flows is an MP - QUIC connection.

[0206] Exemplarily, the SMF network element can also determine MP - QUIC function parameters, and send the MP - QUIC function parameters to the terminal device and the UPF network element, so that the terminal device and the UPF network element can establish an MP - QUIC connection according to the MP - QUIC function parameters. The MP - QUIC function parameters can include one or more of the following: MP - QUIC function IP address, MP - QUIC function port number, MP - QUIC connection identifier, MP - QUIC omitted connection identifier indication parameter, MP - QUIC version information, security parameter, or transmission parameter.

[0207] The MP - QUIC function IP address is the IP address used for the MP - QUIC connection. For example, the IP address of the MP - QUIC function on the network side (or called the MP - QUIC proxy function), such as the IP address corresponding to the MP - QUIC function (or MP - QUIC proxy function) implemented on the UPF network element. For example, when the terminal device performs MP - QUIC encapsulation on the traffic flow, the MP - QUIC function IP address can be encapsulated. In a specific application, the MP - QUIC function IP address can be data such as characters or numbers for identifying the address.

[0208] The MP - QUIC function port can be used to indicate the port number corresponding to the MP - QUIC connection, including the port numbers corresponding to the MP - QUIC function on the network side and / or the MP - QUIC function on the terminal side. In a specific application, the MP - QUIC function port can be data such as characters or numbers for identifying the port number.

[0209] The MP-QUIC connection identifier is the connection identifier allocated by the SMF network element or the UPF network element for an MP-QUIC connection. It can jointly identify an MP-QUIC connection with the MP-QUIC connection identifier allocated by the terminal device, or identify an MP-QUIC connection based on the connection identifier allocated by the SMF network element or the UPF network element. In a possible implementation, if the UPF network element receives the MP-QUIC first connection identifier, the UPF network element can store the above MP-QUIC first connection identifier. Subsequently, the UPF network element can encapsulate service data packets using at least one of the MP-QUIC first connection identifier or the MP-QUIC second connection identifier allocated by the SMF network element or the UPF network element. For example, the service data packets are encapsulated using the MP-QUIC protocol header, and the MP-QUIC first connection identifier, or the MP-QUIC second connection identifier, or both the MP-QUIC first connection identifier and the MP-QUIC second connection identifier are carried in the above MP-QUIC protocol header.

[0210] The MP-QUIC version information is the MP-QUIC version used by the MP-QUIC connection. The MP-QUIC version information can be the MP-QUIC version information supported by the SMF network element or the UPF network element, or the MP-QUIC version information determined by the SMF network element or the UPF network element according to the version information supported by the terminal device.

[0211] The security parameters can be used to encrypt the data transmitted in the MP-QUIC connection. For example, the security parameters can include encryption algorithm information, encryption indication, or non-encryption indication (for example, indicating an empty encryption algorithm means no encryption), or security certificates, etc. In specific applications, the security parameters can be characters, numbers, etc.

[0212] The transmission parameters can be used to control the transmission process of the MP-QUIC connection. The transmission parameters can be, for example, idle_timeout, stateless_reset_token, max_packet_size, etc. For details, reference can be made to the definition of transmission parameters in the MP-QUIC protocol, which will not be elaborated here.

[0213] The MP-QUIC omit connection identifier indication parameter indicates that the MP-QUIC connection does not use a connection identifier. If the MP-QUIC function parameters include the MP-QUIC omit connection identifier indication parameter, then after the subsequent terminal device establishes an MP-QUIC connection and performs MP-QUIC packet header encapsulation on the service flow, a connection identifier can be not used. When the UPF network element receives the MP-QUIC omit connection identifier indication parameter, the UPF network element can not carry a connection identifier in the MP-QUIC packet header when encapsulating data using the MP-QUIC protocol header.

[0214] The terminal device and the UPF network element can transmit multiple service flows using the same MP-QUIC connection.

[0215] Exemplarily, in the uplink, when the terminal device initiates an MP-QUIC connection based on multi-flow multiplexing parameters to send service flow data packets transmitted using the MP-QUIC connection to the UPF network element, it can perform MP-QUIC header encapsulation on the service flow data packets. One or more of the MP-QUIC function parameters can be carried in the MP-QUIC header. For example, the MP-QUIC connection identifier can be carried in the MP-QUIC header. The destination IP address or port number in the MP-QUIC header can be set to the IP address or port number of the MP-QUIC function. The service flow data packets can be encrypted securely based on security parameters. If an MP-QUIC connection that omits the connection identifier indication parameter is used, the MP-QUIC connection identifier is not carried in the MP-QUIC header.

[0216] When there is a new service flow to be transmitted based on the MP-QUIC connection, the terminal device can determine whether there is an existing MP-QUIC connection available based on the multi-flow multiplexing parameters. If so, the UE uses the existing MP-QUIC connection to transmit the service data packets. For example, if the new service flow belongs to QFI 1 and QFI 1 shares the same MP-QUIC connection, the new service flow can be transmitted using the MP-QUIC connection of the service flow of QFI 1. In an optional implementation, if the above MP-QUIC connection has an MP-QUIC connection identifier, the terminal device can use this MP-QUIC connection identifier to encapsulate the service flow data packets.

[0217] Exemplarily, in the downlink, when the UPF network element initiates an MP-QUIC connection based on multi-flow multiplexing parameters to send service flow data packets transmitted using the MP-QUIC connection to the terminal device, it can perform MP-QUIC header encapsulation on the service flow data packets. One or more of the MP-QUIC function parameters can be carried in the MP-QUIC header.

[0218] If the MP-QUIC connection is an MP-QUIC connection at the PDU session granularity, the UPF network element can transmit multiple service flows of this PDU session using this MP-QUIC connection. If this MP-QUIC connection uses a connection identifier, the UPF uses the above connection identifier to encapsulate the service flow data packets of this PDU session.

[0219] If the MP-QUIC connection is an MP-QUIC connection at the QoS flow granularity, the UPF network element can use different MP-QUIC connections to transmit the service data packets of the QoS flow. For example, the UPF network element can establish MP-QUIC connection 1 for QoS flow1 and establish MP-QUIC connection 2 for QoS flow2 and QoS flow3. The service flow data packets of QoS flow1 are transmitted using MP-QUIC connection 1. The service flow data packets of QoS flow2 or QoS flow3 are transmitted using MP-QUIC connection 2. If this MP-QUIC connection uses a connection identifier, the UPF encapsulates the service data packets of this QoS flow with the relevant connection identifier.

[0220] In a possible implementation, if the QoS flow corresponding to the MP-QUIC connection is selected by the UPF network element, the UPF network element can send the QFI bound to the MP-QUIC connection to the SMF network element. For example, if the UPF network element establishes the same MP-QUIC connection for QFI1 and QFI2, the UPF notifies the SMF that this MP-QUIC connection corresponds to QFI1 and QFI2. If this MP-QUIC connection uses a connection identifier and is allocated by the UPF network element, the UPF network element can notify the connection identifier to the SMF network element. For example, for the service flows transmitted using the same MP-QUIC connection, the UPF network element returns the same connection identifier to the SMF network element.

[0221] If the MP-QUIC connection is an MP-QUIC connection at the terminal device granularity, the UPF network element can transmit some or all of the service flow data packets of the PDU session through this MP-QUIC connection.

[0222] Different from the QUIC connection, the MP-QUIC connection includes multiple sub-connections, and each sub-connection has a sub-connection identifier. For example, the UPF network element assigns the connection identifier a to the sub-connection of the MP-QUIC for 3GPP access, or the UPF network element assigns the connection identifier b to the MP-QUIC sub-connection for non-3GPP access. Then when the service flow data packet is transmitted in 3GPP, the terminal device carries the sub-connection identifier corresponding to the 3GPP access technology (such as identifier a) in the MP-QUIC header. If the data packet is transmitted in non-3GPP, the terminal device carries the sub-connection identifier corresponding to the non-3GPP access technology (such as identifier b) in the MP-QUIC header.

[0223] In the embodiments of this application, when encapsulating data using the MP-QUIC header, the sub-connection link can be clearly identified. If the packet loss rate is statistically calculated subsequently, it can be known which specific link has a serious packet loss.

[0224] In a possible implementation,Figure 4 In the corresponding embodiment, the connection shared by multiple service flows is an SCTP connection.

[0225] Exemplarily, the SMF network element may further determine SCTP function parameters and send the SCTP function parameters to the terminal device and the UPF network element, so that the terminal device and the UPF network element can establish an SCTP connection according to the SCTP function parameters. Thus, the method of the embodiment is implemented. Figure 4 of the embodiment.

[0226] As described above in conjunction with Figure 4 , the method of the embodiment of the present application has been described. Next, the communication device for executing the above method provided by the embodiment of the present application will be described. Those skilled in the art can understand that the method and the device can be combined and cited with each other. A communication device provided by an embodiment of the present application can execute the steps performed by the SMF network element in the above communication method. Another communication device can execute the steps performed by the UPF network element in the communication method in the above embodiment. Still another communication device can execute the steps performed by the terminal device in the communication method in the above embodiment.

[0227] Next, taking the division of each functional module according to the corresponding functions as an example for description:

[0228] As Figure 5 shown, Figure 5 FIG. shows a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device may be the SMF network element, the UPF network element or the terminal device in the embodiment of the present application, or may be a chip applied to the SMF network element, the UPF network element or the terminal device. The communication device includes: a processing unit 101 and a communication unit 102. Among them, the communication unit 102 is used to support the communication device to execute the steps of information sending or receiving. The processing unit 101 is used to support the communication device to execute the steps of information processing.

[0229] In one example, taking the communication device as the SMF network element or a chip or a chip system applied to the SMF network element as an example, the communication unit 102 is used to support the communication device to execute S401, S403, S404 and S405 in the above embodiment. The processing unit 101 is used to support the communication device to execute S402 in the above embodiment.

[0230] In a possible embodiment, the communication unit 102 is further used to support the communication device to execute S4021 and S40213 in the above embodiment.

[0231] Another example, taking the communication device as a UPF network element or a chip or chip system applied in a UPF network element as an example, the communication unit 102 is used to support the communication device to execute steps S403 and S404 in the above embodiments. The processing unit 101 is used to support the communication device to execute S406 in the above embodiments.

[0232] Another example, taking the communication device as a terminal device or a chip or chip system applied in a terminal device as an example, the communication unit 102 is used to support the communication device to execute S401 and S405 in the above embodiments. The processing unit 101 is used to support the communication device to execute S406 in the above embodiments.

[0233] In a possible embodiment, the communication device may further include: a storage unit 103. The processing unit 101, the communication unit 102, and the storage unit 103 are connected through a communication bus.

[0234] The storage unit 103 may include one or more memories, and the memory may be a device or a component in a circuit for storing programs or data.

[0235] The storage unit 103 may exist independently and be connected to the processing unit 101 of the communication device through a communication bus. The storage unit 103 may also be integrated with the processing unit.

[0236] The communication device may be used in a communication device, a circuit, a hardware component, or a chip.

[0237] Taking the communication device as a chip or chip system of the SMF network element, UPF network element, or terminal device in the embodiments of the present application as an example, the communication unit 102 may be an input or output interface, a pin, or a circuit, etc. Exemplarily, the storage unit 103 may store computer-executable instructions of the methods on the SMF network element, UPF network element, or terminal device side, so that the processing unit 101 executes the methods on the SMF network element, UPF network element, or terminal device side in the above embodiments. The storage unit 103 may be a register, a cache, or a RAM, etc., and the storage unit 103 may be integrated with the processing unit 101. The storage unit 103 may be a ROM or other types of static storage devices that can store static information and instructions, and the storage unit 103 may be independent of the processing unit 101.

[0238] An embodiment of the present application provides a communication device, which includes one or more modules for implementing the methods in S401 - S406 above, and the one or more modules may correspond to the steps of the methods in S401 - S406 above. Specifically, for each step in the method executed by the SMF network element in the embodiment of the present application, there are units or modules in the SMF network element that execute each step in the method. For each step in the method executed by the UPF network element, there are units or modules in the UPF network element that execute each step in the method. For each step in the method executed by the terminal device, there are units or modules in the terminal device that execute each step in the method. For example, a module that executes to control or process the actions of the communication device may be called a processing module. A module that executes the steps of message or data processing on the communication device side may be called a communication module.

[0239] Figure 6 The following shows a schematic diagram of the hardware structure of the communication device provided by the embodiment of the present application. The hardware structures of the SMF network element and the UPF network element in the embodiment of the present application can both refer to the schematic diagram of the hardware structure of the communication device as shown in Figure 6 The communication device includes a processor 41, a communication line 44, and at least one communication interface ( Figure 6 exemplarily taking the communication interface 43 as an example for illustration).

[0240] The processor 41 may be a general - purpose central processing unit (CPU), a microprocessor, an application - specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the solution of the present application.

[0241] The communication line 44 may include a path for transmitting information between the above - mentioned components.

[0242] The communication interface 43 uses any transceiver - like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0243] Possibly, the communication device may further include a memory 42.

[0244] The memory 42 can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or it can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory can exist independently and be connected to the processor through the communication line 44. The memory can also be integrated with the processor.

[0245] Among them, the memory 42 is used to store computer execution instructions for implementing the solution of this application, and is controlled by the processor 41 for execution. The processor 41 is used to execute the computer execution instructions stored in the memory 42, so as to implement the policy control method provided in the following embodiments of this application.

[0246] Possibly, the computer execution instructions in the embodiments of this application can also be referred to as application program code, and the embodiments of this application do not make specific limitations on this.

[0247] In a specific implementation, as an embodiment, the processor 41 can include one or more CPUs, such as Figure 6 CPU0 and CPU1 in

[0248] In a specific implementation, as an embodiment, the communication device can include multiple processors, such as Figure 6 the processor 41 and the processor 45 in

[0249] For example, taking this communication device as an SMF network element or a chip applied in an SMF network element as an example, this communication interface is used to support this communication device to execute S401, S403, S404, and S405 in the above embodiments. The processor 41 or the processor 45 is used to support the communication device to execute S402 in the above embodiments.

[0250] In another example, taking the communication device as a UPF network element or a chip or chip system applied in the UPF network element as an example, the communication interface is used to support the communication device to execute S403 and S404 in the above embodiments. The processor 41 or the processor 45 is used to support the communication device to execute step S406 in the above embodiments.

[0251] As Figure 7 shown, it is a schematic structural diagram of a terminal device (hereinafter referred to as a terminal) provided by an embodiment of the present application.

[0252] The terminal includes at least one processor 1211 and at least one transceiver 1212. In a possible example, the terminal may further include at least one memory 1213, an output device 1214, an input device 1215, and one or more antennas 1216. The processor 1211, the memory 1213, and the transceiver 1212 are connected. The antenna 1216 is connected to the transceiver 1212, and the output device 1214 and the input device 1215 are connected to the processor 1211.

[0253] The memory in the embodiment of the present application, such as the memory 1213, may include at least one of the following types: read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (EEPROM). In some scenarios, the memory may also be a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto.

[0254] The memory 1213 may exist independently and be connected to the processor 1211. In another example, the memory 1213 may also be integrated with the processor 1211, for example, integrated within a chip. Among them, the memory 1213 can store the program code for executing the technical solution of the embodiment of the present application and is controlled by the processor 1211 to be executed. The various computer program codes executed can also be regarded as the driver programs of the processor 1211. For example, the processor 1211 is used to execute the computer program code stored in the memory 1213, so as to implement the technical solution in the embodiment of the present application.

[0255] The transceiver 1212 can be used to support the reception or transmission of radio frequency signals between terminals or between a terminal and an access device. The transceiver 1212 can be connected to the antenna 1216. The transceiver 1212 includes a transmitter Tx and a receiver Rx. Specifically, one or more antennas 1216 can receive radio frequency signals. The receiver Rx of the transceiver 1212 is used to receive radio frequency signals from the antenna, convert the radio frequency signals into digital baseband signals or digital intermediate frequency signals, and provide the digital baseband signals or digital intermediate frequency signals to the processor 1211 so that the processor 1211 can further process the digital baseband signals or digital intermediate frequency signals, such as demodulation processing and decoding processing. In addition, the transmitter Tx in the transceiver 1212 is also used to receive the modulated digital baseband signals or digital intermediate frequency signals from the processor 1211, convert the modulated digital baseband signals or digital intermediate frequency signals into radio frequency signals, and transmit the radio frequency signals through one or more antennas 1216. Specifically, the receiver Rx can selectively perform one or more levels of down-conversion processing and analog-to-digital conversion processing on the radio frequency signals to obtain digital baseband signals or digital intermediate frequency signals, and the order of the down-conversion processing and the analog-to-digital conversion processing can be adjusted. The transmitter Tx can selectively perform one or more levels of up-conversion processing and digital-to-analog conversion processing on the modulated digital baseband signals or digital intermediate frequency signals to obtain radio frequency signals, and the order of the up-conversion processing and the digital-to-analog conversion processing can be adjusted. The digital baseband signals and digital intermediate frequency signals can be collectively referred to as digital signals.

[0256] The processor 1211 can be a baseband processor or a CPU. The baseband processor and the CPU can be integrated or separated.

[0257] The processor 1211 can be used to implement various functions for the terminal, such as processing communication protocols and communication data, or controlling the entire terminal device, executing software programs, and processing data of software programs; or assisting in completing computing processing tasks, such as graphic image processing or audio processing, etc.; or the processor 1211 is used to implement one or more of the above functions

[0258] The output device 1214 communicates with the processor 1211 and can display information in various ways. For example, the output device 1214 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector, etc. The input device 1215 communicates with the processor 1211 and can accept user input in various ways. For example, the input device 1215 can be a mouse, a keyboard, a touch screen device, or a sensing device, etc.

[0259] Specifically, at least one processor 1211 is used to execute S406. At least one transceiver 1212 is used to execute S401 and S405.

[0260] Figure 8 It is a schematic structural diagram of the chip 150 provided by an embodiment of the present invention. The chip 150 includes one or more than two (including two) processors 1510 and a communication interface 1530.

[0261] In a possible embodiment, as Figure 8 shown, the chip 150 further includes a memory 1540. The memory 1540 can include a read-only memory and a random access memory, and provides operation instructions and data to the processor 1510. A part of the memory 1540 can also include a non-volatile random access memory (NVRAM).

[0262] In some embodiments, the memory 1540 stores the following elements, executable modules, or data structures, or subsets thereof, or extended sets thereof:

[0263] In the embodiments of the present invention, by invoking the operation instructions stored in the memory 1540 (the operation instructions can be stored in the operating system), corresponding operations are executed.

[0264] A possible implementation is that the structures of the chips used by the SMF network element, the UPF network element, or the terminal device are similar, and different devices can use different chips to implement their respective functions.

[0265] The processor 1510 controls the operations of the SMF network element, the UPF network element, or the terminal device. The processor 1510 may also be referred to as a central processing unit (CPU). The memory 1540 may include a read-only memory and a random access memory, and provide instructions and data to the processor 1510. A part of the memory 1540 may also include a non-volatile random access memory (NVRAM). For example, in an application, the memory 1540, the communication interface 1530, and the memory 1540 are coupled together through a bus system 1520. The bus system 1520 may include, in addition to a data bus, a power bus, a control bus, a status signal bus, etc. However, for the sake of clarity, in Figure 8 all kinds of buses are labeled as the bus system 1520.

[0266] The above communication unit may be an interface circuit or a communication interface of the device, and is used to receive signals from other devices. For example, when the device is implemented in the form of a chip, the communication unit is an interface circuit or a communication interface of the chip for receiving signals from other chips or devices or sending signals.

[0267] The method disclosed in the embodiments of the present invention above can be applied to the processor 1510 or implemented by the processor 1510. The processor 1510 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method can be completed by the integrated logic circuit in the hardware of the processor 1510 or instructions in software form. The above-mentioned processor 1510 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present invention can be directly embodied as being executed by a hardware decoding processor or executed by a combination of hardware and software modules in the decoding 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 1540, and the processor 1510 reads the information in the memory 1540 and combines its hardware to complete the steps of the above method.

[0268] In a possible implementation, the communication interface 1530 is used to execute Figure 4 the receiving and sending steps of the SMF network element, UPF network element, or terminal device in the embodiments shown. The processor 1510 is used to execute Figure 4 the processing steps of the SMF network element, UPF network element, or terminal device in the embodiments shown.

[0269] In the above embodiments, the instructions stored in the memory for the processor to execute can be implemented in the form of a computer program product. The computer program product can be pre-written in the memory or downloaded and installed in the memory in software form.

[0270] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD), etc.).

[0271] Embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. The computer-readable medium may include a computer storage medium and a communication medium, and may also include any medium that can transmit a computer program from one place to another. The storage medium may be any target medium accessible by a computer.

[0272] As a possible design, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM, or other optical disk memories, magnetic disk memories, or other magnetic storage devices, or any other medium targeted to carry or store the required program code in the form of instructions or data structures and accessible by a computer. Moreover, any connection is properly referred to as a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of the medium. As used herein, disk and optical disk include optical disk (CD), laser disk, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically, while optical disks use lasers to optically reproduce data. The above combinations should also be included within the scope of the computer-readable medium.

[0273] The embodiments of the present application also provide a computer program product. The methods described in the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on a computer, the processes or functions described in the method embodiments above are generated in whole or in part. The above computer can be a general-purpose computer, a special-purpose computer, a computer network, a base station, a terminal, or other programmable devices.

[0274] The above specific embodiments further elaborate on the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above are only specific embodiments of the present invention and are not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solution of the present invention shall be included in the protection scope of the present invention.

[0275] It should be noted that in specific applications, each network element in the embodiments of the present application may also adopt other definitions or names. Exemplarily, the SMF network element may be referred to as the first core network element, the UPF network element may be referred to as the second core network element, the PCF network element may be referred to as the third core network element, the AMF network element may be referred to as the fourth core network element, etc. Or, the above network elements may also be collectively referred to as core network elements. Or the above network elements may also be defined with other names according to their actual functions, and the embodiments of the present application do not make specific limitations thereto.

Claims

1. A communication method, characterized in that, it includes: A session management function network element receives a first message from a communication device; The first message is used to request the establishment or update of a protocol data unit (PDU) session; The network element determines that multiple traffic flows in the PDU session share the same connection; wherein, the connection shared by the multiple traffic flows is a Multipath QUIC (MPQUIC) connection; The determining that multiple traffic flows in the PDU session share the same connection includes: The session management function network element determines that traffic flows share the same connection based on indication information from a policy control function network element; The session management function network element sends a second message to the communication device; the second message is used to indicate that the PDU session establishment or update is successful, and the second message includes multi-flow connection parameters, and the multi-flow connection parameters are used to indicate that multiple traffic flows in the PDU session share the same connection for transmission.

2. The method according to claim 1, characterized in that, The multi-flow connection parameters include traffic flow description parameters and multi-flow multiplexing parameters; the multi-flow multiplexing parameters are used to indicate MPQUIC transmission information or MPQUIC aggregated flow transmission information.

3. The method according to claim 2, characterized in that, The traffic flow description parameters include at least one of the following: One or more traffic flow description information, application identifier, one or more Quality of Service (QoS) flow identifiers, PDU session identifier.

4. The method according to claim 2 or 3, characterized in that, The multi-flow multiplexing parameters include at least one of the following: QUIC method indication information or MPQUIC method indication information or SCTP method indication information, connection identifier, multi-flow multiplexing indication information, QoS flow granularity indication information, PDU session granularity indication information; wherein, the QUIC method indication information is used to indicate that the traffic flow is transmitted using a QUIC connection, the MPQUIC indication information is used to indicate that the traffic flow is transmitted using an MPQUIC connection; the SCTP method indication information is used to indicate that the traffic flow is transmitted using an SCTP connection, the connection identifier is used to indicate the connection identifier corresponding to the traffic flow, the QoS flow granularity indication information is used to indicate that one or more QoS flow traffic flows are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection; the PDU session granularity indication information is used to indicate that the traffic flows of the PDU session are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection.

5. The method according to any one of claims 1-4, characterized in that, The session management function network element determining that multiple traffic flows in the PDU session share the same connection further includes: The session management function network element determines that the traffic flows share the same connection according to one or more of the following: security or encryption information of the traffic flow, QoS parameters of the traffic flow, destination address of the traffic flow, data network name (DNN) of the traffic flow, transport protocol of the traffic flow, type of the traffic flow, traffic flow splitting mode.

6. The method according to any one of claims 1-5, characterized in that, It further includes: The session management function network element sends the multi-flow connection parameters to the user plane function network element.

7. The method according to any one of claims 1-6, characterized in that The session management function network element determining that multiple service flows in the PDU session share the same connection further includes: When multiple service flows in the PDU session have the same encryption and / or integrity protection requirements, the session management function network element determines that the multiple service flows share the same connection; Or, when multiple service flows in the PDU session have the same encryption security level, the session management function network element determines that the multiple service flows share the same connection; Or, when multiple service flows in the PDU session belong to the same QoS flow, the session management function network element determines that the multiple service flows share the same connection; Or, when multiple service flows in the PDU session are non-guaranteed bit rate non-GBR service flows, the session management function network element determines that the multiple service flows share the same connection; Or, when multiple service flows in the PDU session have the same destination IP address or the same DNN, or multiple service flows in the PDU session use the same transport protocol, or multiple service flows in the PDU session belong to the same PDU session, or multiple service flows in the PDU session use the same traffic splitting mode, or the types of multiple service flows in the PDU session are the same, the session management function network element determines that the multiple service flows share the same connection.

8. The method according to any one of claims 1-7, characterized in that It further includes: The session management function network element sends encryption and / or integrity protection indication information to the user plane function network element and / or the communication device.

9. A communication method, characterized in that it includes: The communication device sends a first message to the session management function network element; The first message is used to request the establishment or update of a protocol data unit PDU session; The communication device receives a second message from the session management function network element; the second message is used to indicate that the PDU session establishment or update is successful, and the second message includes multi-flow connection parameters, and the multi-flow connection parameters are used to represent that multiple service flows in the PDU session share the same connection for transmission; the connection shared by the multiple service flows is a multi-path QUIC (MPQUIC) connection.

10. The method according to claim 9, characterized in that The multi-flow connection parameters include service flow description parameters and multi-flow multiplexing parameters; the multi-flow multiplexing parameters are used to represent MPQUIC transmission information or MPQUIC aggregated flow transmission information.

11. The method according to claim 10, characterized in that The service flow description parameters include at least one of the following: One or more service flow description information, application identifier, one or more QoS flow identifiers, PDU session identifier.

12. The method according to claim 10 or 11, characterized in that The multi-stream multiplexing parameters include at least one of the following: QUIC method indication information or MPQUIC method indication information or SCTP method indication information, connection identifier, multi-stream multiplexing indication information, QoS flow granularity indication information, PDU session granularity indication information; Wherein, the QUIC method indication information is used to indicate that the service flow is transmitted using a QUIC connection, and the MPQUIC indication information is used to indicate that the service flow is transmitted using an MPQUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted using an SCTP connection, the connection identifier is used to indicate the connection identifier corresponding to the service flow, and the QoS flow granularity indication information is used to indicate that one or more QoS flow service flows are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection; the PDU session granularity indication information is used to indicate that the service flows of the PDU session are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection.

13. The method according to claim 12, characterized in that, further comprising: The communication device establishes a connection shared by multiple service flows with a user plane function network element; The communication device transmits a first service flow using the connection shared by the multiple service flows.

14. The method according to claim 13, characterized in that, further comprising: The communication device determines whether a second service flow is allowed to share the connection transmitting the first service flow according to the multi-stream multiplexing parameters; When the second service flow is allowed to share the connection transmitting the first service flow, the communication device transmits the second service flow using the connection transmitting the first service flow.

15. The method according to any one of claims 9-14, characterized in that, further comprising: The communication device receives encryption and / or integrity protection indication information from a session management function network element; The communication device encrypts and / or performs integrity protection on the service flow according to the encryption and / or integrity protection indication information, or does not perform encryption and / or integrity protection on the service flow.

16. A communication device, characterized in that, comprising: A processing unit and a communication unit; Wherein, the communication unit is used to receive a first message from the communication device; the first message is used to request the establishment or update of a protocol data unit (PDU) session; The processing unit is used to determine that multiple service flows in the PDU session share the same connection; Wherein, the connection shared by the multiple service flows is a multi-path Internet transmission protocol (MPQUIC) connection; The determining that multiple service flows in the PDU session share the same connection includes: The communication unit determines that the service flows share the same connection based on indication information from a policy control function network element; The communication unit is further used to send a second message to the communication device; the second message is used to indicate that the PDU session establishment or update is successful, and the second message includes multi-stream connection parameters, and the multi-stream connection parameters are used to represent that multiple service flows in the PDU session are transmitted sharing the same connection.

17. The device according to claim 16, characterized in that, The multi-flow connection parameters include service flow description parameters and multi-flow multiplexing parameters; the multi-flow multiplexing parameters are used to represent MPQUIC transmission information and MPQUIC aggregated flow transmission information.

18. The apparatus according to claim 17, wherein, the service flow description parameters include at least one of the following: one or more service flow description information, application identifier, one or more Quality of Service (QoS) flow identifiers, PDU session identifier.

19. The apparatus according to claim 17 or 18, wherein, the multi-flow multiplexing parameters include at least one of the following: QUIC method indication information or MPQUIC method indication information or SCTP method indication information, connection identifier, multi-flow multiplexing indication information, QoS flow granularity indication information, PDU session granularity indication information; wherein, the QUIC method indication information is used to indicate that the service flow is transmitted using a QUIC connection, and the MPQUIC indication information is used to indicate that the service flow is transmitted using an MPQUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted using an SCTP connection, the connection identifier is used to indicate the connection identifier corresponding to the service flow, the QoS flow granularity indication information is used to indicate that one or more service flows of the QUIC connection or the MPQUIC connection or the SCTP connection are shared; the PDU session granularity indication information is used to indicate that the service flows of the PDU session are shared by the QUIC connection or the MPQUIC connection or the SCTP connection.

20. The apparatus according to any one of claims 16-19, wherein, the processing unit is specifically configured to further determine that the service flows share the same connection according to one or more of the following: security or encryption information of the service flow, service flow QoS parameters, service flow destination address, data network name (DNN) of the service flow, transmission protocol of the service flow, type of the service flow, traffic splitting mode of the service flow.

21. The apparatus according to any one of claims 16-20, wherein, the communication unit is further configured to send the multi-flow connection parameters to a user plane function network element.

22. The apparatus according to any one of claims 16-21, wherein, the processing unit is specifically configured to: when multiple service flows in the PDU session have the same encryption and / or integrity protection requirements, determine that the multiple service flows share the same connection; or, when multiple service flows in the PDU session have the same encryption security level, determine that the multiple service flows share the same connection; or, when multiple service flows in the PDU session belong to the same QoS flow, determine that the multiple service flows share the same connection; or, when multiple service flows in the PDU session are non-guaranteed bit rate (non-GBR) service flows, determine that the multiple service flows share the same connection; Alternatively, when multiple traffic flows in the PDU session have the same destination IP address or the same DNN, or multiple traffic flows in the PDU session use the same transport protocol, or multiple traffic flows in the PDU session belong to the same PDU session, or multiple traffic flows in the PDU session use the same traffic splitting mode, or the types of multiple traffic flows in the PDU session are the same, it is determined that the multiple traffic flows share the same connection.

23. The apparatus according to any one of claims 16-22, wherein, the communication unit is further configured to send encryption and / or integrity protection indication information to the user plane function network element and / or the communication device.

24. A communication apparatus, wherein, it includes a communication unit; wherein, the communication unit is configured to send a first message to the session management function network element; the first message is used to request the establishment or update of a protocol data unit (PDU) session; wherein, the communication unit is further configured to receive a second message from the session management function network element; the second message is used to indicate that the PDU session establishment or update is successful, the second message includes multi-flow connection parameters, and the multi-flow connection parameters are used to indicate that multiple traffic flows in the PDU session share the same connection transmission; the connection shared by the multiple traffic flows is a multi-path QUIC (MPQUIC) connection.

25. The apparatus according to claim 24, wherein, the multi-flow connection parameters include traffic flow description parameters and multi-flow multiplexing parameters; the multi-flow multiplexing parameters are used to indicate MPQUIC transmission information and MPQUIC aggregated flow transmission information.

26. The apparatus according to claim 25, wherein, the traffic flow description parameters include at least one of the following: one or more traffic flow description information, application identifier, one or more QoS flow identifiers, PDU session identifier.

27. The apparatus according to claim 25 or 26, wherein, the multi-flow multiplexing parameters include at least one of the following: QUIC method indication information or MPQUIC method indication information or SCTP method indication information, connection identifier, multi-flow multiplexing indication information, QoS flow granularity indication information, PDU session granularity indication information; wherein, the QUIC method indication information is used to indicate that the traffic flow is transmitted using a QUIC connection, the MPQUIC indication information is used to indicate that the traffic flow is transmitted using an MPQUIC connection; the SCTP method indication information is used to indicate that the traffic flow is transmitted using an SCTP connection, the connection identifier is used to indicate the connection identifier corresponding to the traffic flow, the QoS flow granularity indication information is used to indicate that one or more QoS flow traffic flows are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection; the PDU session granularity indication information is used to indicate that the traffic flows of the PDU session are allowed to share the QUIC connection or the MPQUIC connection or the SCTP connection.

28. The apparatus according to claim 27, wherein, it further includes a processing unit; The processing unit is configured to establish a connection shared by multiple service flows with a user plane function network element; The processing unit is further configured to transmit a first service flow by using the connection shared by the multiple service flows.

29. The apparatus according to claim 28, wherein, The processing unit is further configured to determine whether a second service flow is allowed to share the connection for transmitting the first service flow according to the multi-flow multiplexing parameter; The processing unit is further configured to transmit the second service flow by using the connection for transmitting the first service flow when the second service flow is allowed to share the connection for transmitting the first service flow.

30. The apparatus according to any one of claims 24-29, wherein, further comprising: The communication unit is further configured to receive encryption and / or integrity protection indication information from a session management function network element; The processing unit is further configured to perform encryption and / or integrity protection on the service flow according to the encryption and / or integrity protection indication information, or not perform encryption and / or integrity protection on the service flow.

31. A communication apparatus, wherein, comprising: a processor and a communication interface; wherein, the communication interface is configured to perform operations of message sending and receiving in a session management function network element in the communication method according to any one of claims 1-8, or perform operations of message sending and receiving in the communication apparatus in the communication method according to any one of claims 9-15; the processor runs instructions to perform operations of processing or control in the session management function network element in the communication method according to any one of claims 1-8, or perform operations of processing or control in the communication apparatus in the communication method according to any one of claims 9-15.

32. A chip, wherein, the chip comprises at least one processor and a communication interface, the communication interface is coupled to the at least one processor, and the at least one processor is configured to run a computer program or instruction to implement the communication method according to any one of claims 1-8, or implement the communication method according to any one of claims 9-15; the communication interface is configured to communicate with other modules outside the chip.

33. A computer-readable storage medium, wherein, instructions are stored in the computer-readable storage medium, and when the instructions are run, the communication method according to any one of claims 1-8 is implemented, or the communication method according to any one of claims 9-15 is implemented.

Images