Communication method and device

Abstract

The embodiment of the present application provides a communication method and device, which relates to the field of communication. The embodiment of the present application can control the network side to establish a connection between the terminal device and the UPF network element that allows multiple service flows to be used together, thereby saving the connection link establishment process. It includes: the SMF network element receives a first message from the terminal device for requesting to establish or a PDU session, and the SMF network element sends a second message to the terminal device, the second message is used to indicate that the PDU session is successfully established or updated, and the second message includes a multi-stream connection parameter, which is used to indicate that multiple service flows in the PDU session share the same connection transmission.

Description

Technical Field

[0001] The present application relates to communication technology, and in particular to a communication method and device. Background Art

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

[0003] In the prior art, between the UE and the UPF network element, the establishment of a multi-access PDU session (also referred to as a multi-PDU session) can be supported, for example, Figure 1 As shown, the UE and the UPF network element can establish a multi-access PDU session A based on access technology 1 and access technology 2, and the UE's service flow can be transmitted to the UPF network 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 network element through one access technology, and a multi-access PDU session refers to a PDU session that accesses the UPF network element through multiple access technologies (at least two).

[0004] However, in the prior art, the above-mentioned multi-access PDU session must be established in the UE and the UPF network element to realize the multi-PDU session. The method of realizing the multi-PDU session in the prior art is relatively complicated. Summary of the invention

[0005] The embodiments of the present application provide a communication method and apparatus, which can control the network side to establish a connection between a terminal device and a UPF network element that allows multiple service flows to be used together, thereby saving the connection establishment process and improving transmission efficiency.

[0006] 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 multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an 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 PDU session is successfully established or updated, and the second message includes multi-stream connection parameters, which are used to indicate that multiple service flows in the PDU session share the same connection transmission.

[0007] When 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 complicated. In the embodiment of the present application, the network side can control the establishment of a connection between the terminal device and the UPF network element that allows multiple service flows to be used together, thereby saving the connection link establishment process and improving transmission efficiency.

[0008] 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 multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection. The SMF network element sends a second message and multi-stream connection parameters to the terminal device. The second message is used to indicate that the PDU session is successfully established or updated, and the multi-stream connection parameters are used to indicate that multiple service flows in the PDU session share the same connection transmission.

[0009] The embodiment of the second aspect is different from the embodiment of the first aspect in that, in the embodiment of the second aspect, the multi-stream 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 repeated here.

[0010] For the embodiments of the first aspect and the second aspect of the present application:

[0011] In one 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, QUIC aggregate flow connection information, MP-QUIC connection information, MP-QUIC aggregate flow connection information or SCTP connection information related to the service flow.

[0012] In a possible implementation, the service flow description parameter includes at least one of the following: one or more service flow description information, an application identifier, one or more quality of service QoS flow identifiers, and a PDU session identifier.

[0013] In one possible implementation, the multi-stream multiplexing parameters include at least one of the following: QUIC method indication information or MP-QUIC method indication information or SCTP method indication information, 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, and 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, and the QoS flow granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows one or more QoS flows to share service flows. The PDU session granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows the service flows of the PDU session to share service flows.

[0014] 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: 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 service flow, and diversion 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 a policy control function PCF network element or indication information from a UPF network element.

[0015] In one possible implementation, the SMF network element sends multi-stream connection parameters to the user plane function UPF network element.

[0016] In a possible implementation, the SMF network element determines that multiple service flows in a PDU session share the same connection, including: when multiple service flows in the PDU session have the same encryption and / or integrity protection requirements, the SMF network element determines that the multiple service flows share the same connection. Alternatively, when multiple service flows in the PDU session have the same encryption security level, the SMF network element determines that the multiple service flows share the same connection. Alternatively, when multiple service flows in the PDU session belong to the same QoS flow, the SMF network element determines that the multiple service flows share the same connection. Alternatively, when multiple service flows in the PDU session are non-GBR service flows with non-guaranteed code rate, the SMF network element determines that the multiple service flows share the same connection. Alternatively, when multiple service flows in a PDU session have the same destination IP address or the same DNN, or multiple service flows in a PDU session use the same transmission protocol, or multiple service flows in a PDU session belong to the same PDU session, or multiple service flows in a PDU session use the same diversion mode, or multiple service flows in a PDU session are of the same type, the SMF network element determines that multiple service flows share the same connection.

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

[0018] In a third aspect, an embodiment of the present application provides a communication method, comprising: 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 is successfully established or updated, and the second message includes a multi-stream connection parameter, which is used to indicate that multiple service flows in the PDU session share the same connection transmission. The connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection.

[0019] In a fourth aspect, an embodiment of the present application provides a communication method, comprising: 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 and a multi-stream connection parameter from the SMF network element. The second message is used to indicate that the PDU session is established or updated successfully, and the multi-stream connection parameter is used to indicate that multiple service flows in the PDU session share the same connection transmission. The connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection.

[0020] The embodiment of the fourth aspect is different from the embodiment of the third aspect in that, in the embodiment of the fourth aspect, the multi-stream connection parameters are not included in the second message, which will not be described in detail here.

[0021] For the embodiments of the third aspect and the fourth aspect of the present application:

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

[0023] In a possible implementation, the method further includes: the terminal device establishes a connection shared by multiple service flows with a user plane function UPF network element. The terminal device transmits the first service flow using the connection shared by multiple service flows.

[0024] In a possible implementation, the terminal device determines whether the second service flow is allowed to be shared with the connection for transmitting the first service flow according to the multi-stream multiplexing parameter. If the second service flow is allowed to be shared with the connection for transmitting the first service flow, the terminal device transmits the second service flow using the connection for transmitting the first service flow.

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

[0026] In a fifth aspect, an embodiment of the present application provides a communication method, including: a user plane function UPF network element receives a multi-stream connection parameter from a session management function SMF network element. The multi-stream connection parameter is used to indicate that multiple service flows in a PDU session share the same connection transmission. The UPF network element establishes a connection with a terminal device based on the multi-stream connection parameter that allows multiple service flows to be shared. The connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection.

[0027] The specific contents of the multi-stream connection parameters, service flow description parameters and multi-stream multiplexing parameters involved in the fifth aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0028] In one possible implementation, the UPF network element transmits the first service flow using a connection that allows multiple service flows to share. The UPF network element determines whether the second service flow is allowed to share with the connection that transmits the first service flow based on the multi-stream multiplexing parameter. If the second service flow is allowed to share with the connection that transmits the first service flow, the UPF network element transmits the second service flow using the connection that transmits the first service flow.

[0029] In one 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 integrity protects the service flow according to the encryption and / or integrity protection indication information, or does not encrypt and / or integrity protect the service flow.

[0030] In a sixth aspect, an embodiment of the present application provides a communication device, including: the communication device can be an SMF network element, or a chip or chip system in an 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 also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit so that the SMF network element implements a communication method described in the first aspect or any possible implementation of the first aspect, or so that the SMF network element implements a communication method described in the second aspect or any possible implementation of the second aspect.

[0031] Exemplarily, a communication unit is used 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. The processing unit is used to determine that multiple service flows in the PDU session share the same connection. Among them, the connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregate stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregate stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection. The communication unit is also used to send a second message to the terminal device. The second message is used to indicate that the PDU session is successfully established or updated, and the second message includes multi-stream connection parameters, which are used to indicate that multiple service flows in the PDU session share the same connection transmission.

[0032] Alternatively, exemplarily, the communication unit is used 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. The processing unit is used to determine that multiple service flows in the PDU session share the same connection. Among them, the connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregate stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregate stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection. The communication unit is also used to send a second message and multi-stream connection parameters to the terminal device. The second message is used to indicate that the PDU session is successfully established or updated, and the multi-stream connection parameters are used to indicate that multiple service flows in the PDU session share the same connection transmission.

[0033] The specific contents of the multi-stream connection parameters, service flow description parameters and multi-stream multiplexing parameters involved in the sixth aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0034] In a possible implementation, the processing unit is specifically used to determine that the service flows share the same connection based on one or more of the following: 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, transmission protocol of the service flow, type of the service flow, and diversion mode of the service flow. Alternatively, the processing unit is specifically used to determine that the service flows share the same connection based on PCF indication information from a policy control function PCF network element or indication information from a UPF network element.

[0035] In a possible implementation, the communication unit is further used to send multi-stream connection parameters to the user plane function UPF network element.

[0036] In one possible implementation, the processing unit is specifically used to: when multiple service flows in a 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 a PDU session have the same encryption security level, determine that the multiple service flows share the same connection. Or, when multiple service flows in a PDU session belong to the same QoS flow, determine that the multiple service flows share the same connection. Or, when multiple service flows in a PDU session are non-GBR service flows with non-guaranteed code rate, determine that the multiple service flows share the same connection. Or, when multiple service flows in a PDU session have the same destination IP address or the same DNN, or multiple service flows in a PDU session use the same transmission protocol, or multiple service flows in a PDU session belong to the same PDU session, or multiple service flows in a PDU session use the same diversion mode, or multiple service flows in a PDU session are of the same type, determine that the multiple service flows share the same connection.

[0037] In one possible implementation, the communication unit is also used to send encryption and / or integrity protection indication information to the UPF network element and / or terminal device.

[0038] When the communication device is a chip or chip system in an 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 or a circuit, etc. The processing unit executes the instructions stored in the storage unit so that the SMF network element implements a communication method described in the first aspect or any possible implementation of the first aspect, or so that the SMF network element implements a communication method described in the second aspect or any possible implementation of the second aspect. The storage unit may be a storage unit in the chip (for example, a register, a cache, etc.), or it may be a storage unit in the SMF network element that is located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0039] In a seventh aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a chip or chip system in a 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 or an interface circuit or a transceiver. The communication device may also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit so that the terminal device implements a communication method described in the third aspect or any possible implementation of the third aspect, or so that the terminal device implements a communication method described in the fourth aspect or any possible implementation of the fourth aspect.

[0040] Exemplarily, a communication unit is used 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. The communication unit is also used to receive a second message from the SMF network element. The second message is used to indicate that the PDU session is successfully established or updated, and the second message includes a multi-stream connection parameter, which is used to indicate that multiple service flows in the PDU session share the same connection transmission. The connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection.

[0041] Or, exemplarily, the communication unit is used to send a first message to the 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 communication unit is also used to receive a second message and a multi-stream connection parameter from the SMF network element. The second message is used to indicate that the PDU session is successfully established or updated, and the multi-stream connection parameter is used to indicate that multiple service flows in the PDU session share the same connection transmission. The connection shared by multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection.

[0042] The specific contents of the multi-stream connection parameters, service flow description parameters and multi-stream multiplexing parameters involved in the seventh aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0043] In a possible implementation, the system further includes a processing unit, which is used to establish a connection shared by multiple service flows of a user plane function UPF network element, and is also used to transmit the first service flow using the connection shared by multiple service flows.

[0044] In a possible implementation, the processing unit is further configured to determine whether the second service flow is allowed to be shared with the connection for transmitting the first service flow according to the multi-stream multiplexing parameter. The processing unit is further configured to transmit the second service flow using the connection for transmitting the first service flow when the second service flow is allowed to be shared with the connection for transmitting the first service flow.

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

[0046] When the communication device is a chip in 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. 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. The storage unit may be a storage unit in the chip (e.g., a register, a cache, etc.), or a storage unit in the terminal device located outside the chip (e.g., a read-only memory, a random access memory, etc.).

[0047] In an eighth aspect, an embodiment of the present application provides a communication device, including: the communication device can be a UPF network element, or a chip or chip system in 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 also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit so that the UPF network element implements a communication method described in the fifth aspect or any possible implementation of the fifth aspect.

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

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

[0050] In a possible implementation, the processing unit is further configured to transmit the first service flow by using a connection that allows multiple service flows to share. The processing unit is further configured to determine, based on the multi-stream multiplexing parameter, whether the second service flow is allowed to share with the connection that transmits the first service flow. The processing unit is further configured to transmit the second service flow by using the connection that transmits the first service flow if the second service flow is allowed to share with the connection that transmits the first service flow.

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

[0052] When the communication device is a chip or chip system in a 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 or a circuit, etc. The processing unit executes the instructions stored in the storage unit so that the UPF network element implements a communication method described in the fifth aspect or any possible implementation of the fifth aspect. The storage unit may be a storage unit in the chip (for example, a register, a cache, etc.), or it may be a storage unit in the UPF network element located outside the chip (for example, a read-only memory, a random access memory, etc.).

[0053] In the 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 is executed on a computer, the computer executes the communication method described in any possible implementation method of the first aspect to the first aspect.

[0054] In the 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 is executed on a computer, the computer executes the communication method described in any possible implementation method of the second aspect to the second aspect.

[0055] In the 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 is run on a computer, the computer executes the communication method described in any possible implementation method of the third aspect to the third aspect.

[0056] In the 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 is run on a computer, the computer executes the communication method described in any possible implementation method of the fourth aspect to the fourth aspect.

[0057] In the 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 is run on a computer, the computer executes the communication method described in any possible implementation method of the fifth aspect to the fifth aspect.

[0058] In a fourteenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a communication method described in the first aspect or various possible implementations of the first aspect.

[0059] In a fifteenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a communication method described in the second aspect or various possible implementations of the second aspect.

[0060] In the sixteenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a communication method described in the third aspect or various possible implementations of the third aspect.

[0061] In the seventeenth aspect, the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a communication method described in the fourth aspect or various possible implementations of the fourth aspect.

[0062] In the eighteenth aspect, an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a communication method described in the fifth aspect or various possible implementations of the fifth aspect.

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

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

[0065] In the twentieth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the communication method described in the first aspect or various possible implementation methods of the first aspect is implemented.

[0066] In the twenty-first aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the communication method described in the second aspect or various possible implementation methods of the second aspect is implemented.

[0067] In the twenty-second aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the communication method described in the third aspect or various possible implementation methods of the third aspect is implemented.

[0068] In the twenty-third aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the communication method described in the fourth aspect or various possible implementation methods of the fourth aspect is implemented.

[0069] In the twenty-fourth aspect, an embodiment of the present application provides a communication device, which includes a processor and a storage medium, wherein the storage medium stores instructions, and when the instructions are executed by the processor, the communication method described in the fifth aspect or various possible implementation methods of the fifth aspect is implemented.

[0070] In the 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 at least one processor are interconnected through lines, and the at least one processor is used to run computer programs or instructions to perform the communication method described in any one of the possible implementation methods of the first aspect to the first aspect.

[0071] In the 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 at least one processor are interconnected by lines, and the at least one processor is used to run computer programs or instructions to perform the communication method described in any one of the possible implementation methods of the second aspect to the second aspect.

[0072] In the twenty-seventh aspect, the present application provides a chip or a chip system, which chip or chip system includes at least one processor and a communication interface, the communication interface and at least one processor are interconnected through lines, and the at least one processor is used to run computer programs or instructions to perform the communication method described in any one of the possible implementation methods of the third aspect to the third aspect.

[0073] In aspect twenty-eight, the present application provides a chip or a chip system, which chip or chip system includes at least one processor and a communication interface, the communication interface and at least one processor are interconnected by lines, and the at least one processor is used to run computer programs or instructions to perform the communication method described in any one of the possible implementation methods of aspect four to aspect four.

[0074] In the 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 at least one processor are interconnected through lines, and the at least one processor is used to run computer programs or instructions to perform the communication method described in any one of the possible implementation methods of the fifth aspect to the fifth aspect.

[0075] The communication interface in the chip may be an input / output interface, a pin or a circuit, etc.

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

[0077] It should be understood that the second to twenty-ninth aspects of the embodiments of the present application correspond to the technical solutions of the first aspect of the embodiments of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 A schematic diagram of an existing multi-PDU session access;

[0079] Figure 2 A schematic diagram of a network architecture provided in an embodiment of the present application;

[0080] Figure 3 Another schematic diagram of a network architecture provided in an embodiment of the present application;

[0081] Figure 4 A flow chart of a communication method provided in an embodiment of the present application;

[0082] Figure 5 A schematic diagram of a communication device provided in an embodiment of the present application Figure 1 ;

[0083] Figure 6 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0084] Figure 7 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

[0085] Figure 8 A schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0086] In order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. For example, the first network and the second network are only used to distinguish different networks, and their order is not limited. Those skilled in the art can understand that the words "first" and "second" do not limit the quantity and execution order, and the words "first" and "second" do not necessarily limit them to be different.

[0087] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0088] In the present application, "at least one" means one or more, and "plurality" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0089] 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 (5 generation, 5G) system, and can also be applied in a long term evolution (long term evolution, LTE). The 5G system is also called a new wireless communication system, a new access technology (new radio, NR) or a next generation mobile communication system.

[0090] For example, Figure 2A schematic diagram of a network architecture provided for an embodiment of the present application. The architecture not only supports wireless technologies (such as LTE, 5G radio access network (RAN), etc.) defined by the third generation partnership project (3rd generation partnership project, 3GPP) standard group to access the core network (core network, CN), but also supports non-3GPP access technologies to access the core network through non-3GPP interworking function (N3IWF) or next generation packet data gateway (ngPDG).

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

[0092] 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, which can include: 3GPP access network, non-3GPP access network such as WiFi network access point (AP), next-generation base station (collectively referred to as new generation radio access network node (NG-RAN node), where the next-generation base station includes new air interface base station (NR nodeB, gNB), new generation evolved base station (NG-eNB), central unit (CU) and distributed unit (DU) separated gNB, etc.), transmission receive point (TRP), transmission point (TP) or other nodes.

[0093] The 5G core network (5G core / new generation core, 5GC / NGC) includes multiple functional units such as 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 function (UDM) network element, network slice selection function (NSSF) network element, and network function (NEF) network element.

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

[0095] The functional units in the 5G system can communicate with each other through the next generation network (NG) interface, such as: the terminal device can transmit control plane messages with the AMF network element through the NG interface 1 (N1 for short), the RAN device can establish a user plane communication connection channel with the UPF through the NG interface 3 (N3 for short), the AN / RAN device can establish a control plane signaling connection with the AMF network element through the NG interface 2 (N2 for short), the UPF can exchange information with the SMF network element through the NG interface 4 (N4 for short), the UPF can exchange user plane data with the data network DN through the NG interface 6 (N6 for short), the AMF network element can exchange information with the SMF network element through the NG interface 11 (N11 for short), the SMF network element can exchange information with the PCF network element through the NG interface 7 (N7 for short), and the AMF network element can exchange information with the AUSF through the NG interface 12 (N12 for short).

[0096] For example, Figure 3 As shown, Figure 3 FIG. 1 is a schematic diagram of a specific network architecture when the core network supports untrusted non3GPP access. The network architecture in the home public land mobile network (HPLMN) is similar to Figure 2 The implementation in will not be repeated here. Non-trusted non3GPP access can be non-trusted wireless local area networks (WLAN) access. In this architecture, the terminal device can also interact with the AMF through non-trusted non3GPP access, Non3GPP conversion function / non3GPP access gateway (Non3GPP interworking function, N3IWF), and the N3IWF network element can interact with the UPF through N3.

[0097] In addition, the core network can also support trusted non3GPP access and / or fixed network access. Among them, the trusted non3GPP network includes a trusted WAN network, and the fixed network includes a fixed home network access, etc. The network side architecture is similar to the non-trusted non3GPP network architecture, replacing the N3IWF and the non-trusted access network with a trusted Non-3GPP access network, or the N3IWF is replaced with a trusted Non-3GPP access gateway, and the non-trusted access network is replaced with a trusted access network. Among them, the access network equipment between the terminal device and the trusted Non-3GPP access gateway may include WLAN AP, fixed network access network equipment (fixed Access network, FAN), switches, routers, etc.

[0098] Whether it is trusted Non-3GPP access or untrusted Non-3GPP access, the core network side can adopt the following Figure 2 The point-to-point interface protocol shown, or the service-oriented interface architecture consistent with the 3GPP access core network architecture. This embodiment of the application does not make specific limitations on this.

[0099] In one possible implementation, 3GPP access technology and non3GPP access technology may include multiple access standards or frequency bands, and may be used simultaneously. For example, 3GPP access includes 4G LTE and 5G NG-RAN access technologies to 5GC at the same time. Non3GPP wifi access also includes simultaneous access to two frequency bands, such as 5GHz and 2.4GHz wifi bands to 5GC at the same time. In one possible implementation, the UE can access the 5GC architecture through at least two of the above four access methods (including four simultaneous uses).

[0100] The method processing of the embodiments of the present application can be applied to the above-mentioned 5G 3GPP access architecture, or non3GPP access architecture, or architecture of simultaneous access of 3GPP and non3GPP, and can also be applied to architecture of simultaneous access of 5G cellular (NG-RAN) and 4G cellular (LTE), etc. The embodiments of the present application do not specifically limit the network architecture.

[0101] Some terms in the embodiments of the present application are explained below.

[0102] The data transmission involved in the embodiments of the present application may include data transmission, data reception, or data interaction processes. For example, data transmission between a terminal device and a UPF network element may include the terminal device sending data to a 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.

[0103] The connection that allows multiple service flows to share (also referred to as a service flow multiplexing connection, etc.) involved in the embodiments of the present application may be: a user datagram protocol (quick UDP internet connection, QUIC) connection, or an aggregate stream connection in a QUIC connection (an aggregate stream may be referred to as a stream), or a multi-path Internet transport protocol (multi-path quickUDP internet connection, MP-QUIC) connection, or an aggregate stream connection in an MP-QUIC connection, or a stream control transmission protocol (stream control transmission protocol, SCTP) connection, etc. The embodiments of the present application do not specifically limit the connection that allows multiple service flows to share.

[0104] QUIC is a low-latency Internet transport layer protocol based on UDP. When the sender needs to use a QUIC connection to transmit data, 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 stream connection in the QUIC connection. The QUIC connection or the aggregated stream connection in the QUIC connection can support one or more access technologies or tunnels.

[0105] The QUIC connection involved in the embodiments of the present 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, this QUIC connection can be considered as a QUIC connection at the granularity of the terminal device. If a QUIC connection can be shared by one or more PDU sessions, this QUIC connection can be considered as a QUIC connection at the granularity of a PDU session. If a QUIC connection can be shared by all service flows in one or more Quality of Service (QoS flow) flows of the same PDU session, this QUIC connection can be a connection at the granularity of a QoS flow. If a QUIC connection can only be used by one service flow, the QUIC connection can be a QUIC connection at the granularity of a flow.

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

[0107] MP-QUIC is a low-latency multi-path 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.

[0108] MP-QUIC related connections can use various parameters in QUIC related connections. The difference between MP-QUIC related connections and QUIC related connections is that MP-QUIC related connections can contain 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.

[0109] The MP-QUIC connection involved in the embodiments of the present application can be multiplexed by multiple service flows. For example, if an MP-QUIC connection can be shared by different service flows of all PDU sessions of a terminal device, this MP-QUIC connection can be considered as an MP-QUIC connection at the terminal device granularity. If an MP-QUIC connection can be shared by one or more PDU sessions, this MP-QUIC connection can be considered as an MP-QUIC connection at the PDU session granularity. If an MP-QUIC connection can be shared by all service flows in one or more QoS flows of the same PDU session, 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 flow, the MP-QUIC connection can be an MP-QUIC connection at the flow granularity.

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

[0111] SCTP is a connection-oriented stream transmission protocol that can provide stable and orderly data transmission services between two endpoints. When the sender needs to use SCTP connection to transmit data, it needs to first establish an SCTP connection with the receiver and then process the data to be transmitted. SCTP connection can be shared by multiple service flows.

[0112] The service flow involved in the embodiments of the present application may be a service flow using the user datagram protocol (UDP) or other protocols. For example, the service flow of a PDU session may be: a PDU session established between a terminal device and a 5G core network (5G core, 5GC) or a UDP service flow in this session; or, a PDN connection established between a terminal device and an EPC network or a UDP service flow in this PDN connection; or, an IP connection for non-seamless WLAN offload by a terminal device through a non-3GPP access network (such as WLAN access) or a UDP service flow in this connection.

[0113] In an embodiment of the present application, the terminal device may support QUIC capability or MP-QUIC capability or SCTP capability. If the terminal device supports QUIC capability, the subsequent terminal device can use the QUIC protocol to establish a QUIC connection or an aggregate stream connection in a QUIC connection. If the terminal device supports MP-QUIC capability, the subsequent terminal device can use the MP-QUIC protocol to establish an MP-QUIC connection or an aggregate stream connection in an MP-QUIC connection. If the terminal device supports SCTP capability, the subsequent terminal device can use the SCTP protocol to establish an SCTP connection.

[0114] The multi-flow connection parameters involved in the embodiments of the present application can be used to indicate that the connection between the terminal device and the UPF network element allows multiple service flows to be shared. 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 be shared, or to indicate that the connection between the terminal device and the UPF network element allows multiple PDU sessions to be shared, or to indicate that the connection between the terminal device and the UPF network element allows multiple service flows of one PDU session to be shared, 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 be shared, etc.

[0115] Exemplarily, the multi-stream connection parameters may include one or more of service flow description parameters or multi-stream multiplexing parameters.

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

[0117] The service flow description information may be at least one of the five-tuple description information of the service flow network Internet protocol (IP), and the five-tuple description information may be: source IP address, destination IP address, source port number, destination port number and protocol type; or the service flow description information may be a PDU session identifier (when all service flows in this PDU session are transmitted using a connection); or the service flow description information may be at least one of the Ethernet header information, for example, a source media access control (MAC) address and a destination MAC address, a virtual local area network (VLAN) identifier; etc. Then, the subsequent terminal device may share the same connection for transmission of the service flow containing the service flow description information. The number of service flow description information may be one or more, and the embodiments of the present application do not specifically limit this.

[0118] The application identifier can be used to identify the service flow of a specific application program. Then, the subsequent terminal device can share the same connection to transmit the service flow containing the application identifier. The number of application identifiers can be one or more, and the embodiment of the present application does not specifically limit this.

[0119] The QoS flow identifier (QFI) can be the identifier of multiple service flows whose QoS meets a certain relationship. Then the subsequent terminal device can share the same connection for transmission of multiple service flows containing the QoS flow identifier. For example, the service flow description parameters include QFI 1 and QFI 2, indicating that the service flow in QFI 1 and the service flow in QFI 2 can share the same connection for data transmission.

[0120] The PDU session identifier can be the identifier of the established or updated PDU. Then the subsequent terminal device can share the same connection for transmission of multiple service flows containing the PDU session identifier. In a possible implementation, the service flow description parameters are transmitted between the terminal device and the UPF network element, and the service flow description parameters may include one or more N4 session identifiers or PDU session identifiers, indicating that multiple service flows corresponding to the N4 session identifier or the PDU session identifier share the same connection for transmission, and the N4 session identifier and the PDU session identifier may have a one-to-one correspondence.

[0121] The terminal device identifier may be a symbol or number used to identify the terminal device, such as an IP address or ID of the terminal device, which is not specifically limited in the present application. Subsequently, multiple service flows containing the terminal device identifier may share the same connection for transmission.

[0122] In one possible implementation, the multi-stream multiplexing parameters may be used to represent QUIC connection information related to a service flow, QUIC aggregate flow connection information related to a service flow, MP-QUIC connection information related to a service flow, MP-QUIC aggregate flow connection information related to a service flow, or SCTP connection information related to a service flow.

[0123] Exemplarily, the multi-stream multiplexing parameters may include one or more of the following: protocol indication information, multi-stream multiplexing indication information, connection identifier, QoS flow granularity indication information, PDU session granularity indication information, and terminal device granularity indication information.

[0124] The protocol indication information may be QUIC method indication information, MP-QUIC method indication information, or SCTP method indication information. The QUIC method indication information may be used to indicate that the service flow of the PDU session is transmitted using a QUIC connection or an aggregated stream connection in a QUIC connection. The QUIC method indication information may be characters, numbers, etc. The MP-QUIC method indication information may be used to indicate that the service flow of the PDU session is transmitted using an MP-QUIC connection or an aggregated stream connection in an MP-QUIC connection. The MP-QUIC method indication information may be characters, numbers, etc. The SCTP method indication information may be used to indicate that the service flow of the PDU session is transmitted using an SCTP connection. The SCTP method indication information may be characters, numbers, etc.

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

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

[0127] The QoS flow granularity indication information is used to indicate that the connection allows one or more QoS flows to share service flows. 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. Subsequent terminal devices or UPF network elements can select one or more QoS flows and use a shared connection for transmission.

[0128] The PDU session granularity indication information is used to indicate that the connection allows the sharing of service flows of the PDU session. The connection can be a QUIC connection, an aggregated stream connection in a QUIC connection, an MP-QUIC connection, an aggregated stream connection in an MP-QUIC connection, or an SCTP connection, etc. Subsequent terminal devices or UPF network elements can select multiple service flows of one or more PDU sessions and use a shared connection for transmission.

[0129] The terminal device granularity indication information is used to indicate that the QUIC connection allows the service flow of a terminal device to be shared. The connection can be a QUIC connection, an aggregated stream connection in a QUIC connection, an MP-QUIC connection, an aggregated stream connection in an MP-QUIC connection, or an SCTP connection, etc. Subsequent terminal devices or UPF network elements can use a shared connection to transmit any service flow in the terminal device.

[0130] The first message sent by the terminal device to the SMF network element involved in the embodiment of the present application can be a PDU session establishment or update request message, or a PDU session establishment or update request message sent to establish a multi-access PDU (multi-access PDU, MA PDU) session, or any other message, which is not specifically limited in the embodiment of the present application. The terminal device sends a first message to the SMF network element to request the establishment or update of a PDU session.

[0131] The second message received by the terminal device from the SMF network element in the embodiment of the present application may be a message indicating that the PDU session is successfully established, or a message indicating that the PDU session is successfully updated, or any other message, which is not specifically limited in the embodiment of the present application. The second message received by the terminal device from the SMF network element may be used to indicate that the PDU session is successfully established or updated.

[0132] The following specific embodiments are used to describe in detail the technical solution of the present application and how the technical solution of the present application solves the above technical problems. The following specific embodiments can be implemented independently or in combination with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0133] Figure 4 A flow chart of a communication method provided in an embodiment of the present application includes the following steps:

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

[0135] In one possible implementation, the terminal device may encapsulate the message requesting to establish or update a PDU session in a non-access stratum (NAS) transmission message and send it to an AMF network element, and the AMF network element forwards the message requesting to establish or update a PDU session to the SMF network element.

[0136] In one possible implementation, the terminal device may send a NAS transmission message to the AMF network element through the RAN, including 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 that the terminal device supports the protocol capability, and 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 capability may be: indication information of the QUIC capability, indication information of the MP-QUIC capability, or indication information of the SCTP capability, etc.

[0137] In one possible implementation, the terminal device sends a NAS transmission message to the AMF network element, which includes an indication of the terminal device's support for protocol capabilities and a message requesting to establish or update a PDU session. The AMF network element forwards the message requesting to establish or update a PDU session and the protocol capability indication to the SMF network element.

[0138] In one possible implementation, the NAS transmission message includes a message requesting the establishment or update of a PDU session and indication information that the terminal device supports the protocol capabilities. 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 that the terminal device supports the protocol capabilities to the SMF network element.

[0139] The SMF network element may receive a first message from a terminal device, or a first message and indication information that the terminal device supports protocol capabilities.

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

[0141] In the embodiment 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 terminal devices or PCF network elements or UDM network elements, etc.). The SMF network element may also determine that multiple service flows related to the PDU session share the same connection based on policy information (also referred to as PCF indication information) sent by the PCF network element. Etc.

[0142] In one possible implementation, the SMF 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: security or encryption information of the service flow, service flow QoS parameters, service flow destination address, data network name (Data Network Name, DNN) of the service flow, transmission protocol of the service flow, type of service flow, and diversion mode of the service flow.

[0143] In the embodiment of the present application, the security or encryption information of the service flow can be used to indicate the security encryption requirements of the service flow. For example, the security or encryption information of the service flow may include: indication information for indicating whether encryption is required, indication information for indicating whether integrity protection is required, security level information or encryption algorithm, etc.

[0144] Exemplarily, if the security 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 that requires encryption, 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 that requires integrity protection, 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.

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

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

[0147] The security or encryption information of the service flow can be obtained by the SMF network element from the contract data of the terminal device, or it can be received by the SMF network element from the PCF network element, or it can be locally configured by the SMF network element, or the SMF needs to indicate encryption and / or integrity protection when accessing the service flow from the PCF network element, and the SMF network element determines that the service flow is encrypted between the UE and the UPF network element based on the access technology of the transmission service flow. The above access technology includes 3GPP access technology, non3GPP access technology, wifi access technology, or fixed network or wired access technology. For example, when the service flow is accessed from non3GPP or wifi or fixed network or wired, and the SMF network element receives an indication sent by the PCF network element that encryption and / or integrity protection is required, the SMF network element determines that the service flow implements encryption and / or integrity protection between the UE and the UPF network element. The embodiment of the present application does not specifically limit the source of the security or encryption information of the service flow.

[0148] When the service flow carries security or encryption information, the subsequent SMF network element can send security or encryption information to the UPF network element and terminal equipment respectively, which is used by the UPF network element and the terminal equipment to encrypt the service flow when transmitting the service flow, thereby increasing the security of the service flow transmission.

[0149] In an embodiment of the present application, a service flow QoS parameter can be used to represent the QoS parameters of a 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 multiple service flows can share the same connection. For example, the QoS parameters of a service flow may include at least one of 5QI (5G QoS Identifier), allocation and retention priority (ARP), bandwidth, latency, and packet loss rate parameters. When one or more of the QoS parameters of multiple service flows are the same, the same connection can be shared. If 5QI=1 for service flow 1 and 5QI=1 for service flow 2, service flow 1 and service flow 2 can share the same connection.

[0150] The embodiment of the present application can also determine 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 non-guaranteed bit rate (non-GBR) service flows, the SMF network element can determine that multiple service flows can share the same connection.

[0151] In the embodiment of the present application, the service flow destination address can be the service flow destination IP address or destination MAC address. 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.

[0152] In an embodiment of the present application, the data network name (Data Network Name, DNN) of the service flow can be obtained by the SMF network element from the contract data of the terminal device. If the DNN of multiple service flows is the same, the SMF network element can determine that multiple service flows can share the same connection. This solution can enable one or more PDU sessions to share the same connection. For example, the DNN corresponding to PDU1 = Internet, and the DNN corresponding to PDU session 2 = Internet, then all service flows of PDU session 1 and PDU session 2 can share the same connection.

[0153] In the embodiment of the present application, the transmission protocol of the service flow may be UDP or transmission control protocol (TCP). If the transmission protocols of multiple service flows are the same, the SMF network element may determine that the multiple service flows may share the same connection. For example, service flow 1 is a service flow transmitted by UDP, and service flow 2 is also a service transmitted by UDP, then service flow 1 and service flow 2 share a connection.

[0154] In the embodiment of the present application, the types of service flows may 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 may determine that the multiple service flows can share the same connection.

[0155] In the embodiment of the present application, the diversion mode of the service flow can be a load balancing diversion mode, a priority diversion mode (for example, preferentially using a high-priority access technology to transmit the service flow), a primary-backup diversion mode, a minimum delay diversion mode (for example, using a link with the minimum delay to transmit the service flow), etc. If the diversion modes 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 addition, in an embodiment of the present application, the connection sharing of multiple PDU session granularity or UE granularity can also be realized based on slice information, or at least one of 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 mode of multiple PDUs is the same, all service flows of the above PDU sessions can share the same connection.

[0157] In the implementation method in which 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 explained in subsequent embodiments and will not be repeated here.

[0158] In one possible implementation, the SMF network element can determine that multiple service flows in a PDU session share the same connection based on the contract data of the terminal device, local configuration policies, or multiple policy information obtained from the PCF network element. The SMF network element can then combine multiple policies to determine that multiple service flows in a PDU session share the same connection.

[0159] For example, the SMF network element can determine that multiple service flows in a PDU session share the same connection when multiple indications in the terminal device's subscription data, local configuration policy, or policy information obtained from the PCF network element are consistent.

[0160] For another example, when there are consistency in 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 higher priority can be selected to determine that multiple service flows in the PDU session share the same connection. The priority of the three types of information, namely, 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, the priority of the three types of information can be defined to increase or decrease in sequence, or the PCF policy information can be defined to have the highest priority, etc.

[0161] In an embodiment of the present application, when the SMF network element determines that multiple service flows related to a PDU session share the same connection, multi-flow connection parameters can be determined based on the parameters used to determine that multiple service flows related to the PDU session share the same connection, and the multi-flow connection parameters can be sent to the UPF network element.

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

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

[0164] For example, the UPF network element can store the multi-stream connection parameters sent by the SMF network element, so that when the UPF performs service flow transmission, multiple service flows can share the same connection transmission. 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 UPF network element to indicate that the above-mentioned service flow needs to be encrypted and / or integrity protected. For example, when encryption and / or integrity protection indication information is included, it indicates that encryption and / or integrity protection needs to be performed on the relevant service flow. For those that do not contain encryption and / or integrity protection indications, it means that encryption and / or integrity protection may not be performed on the relevant service flow.

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

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

[0167] In another possible implementation, the SMF network element does not need to configure the multi-stream connection parameters in the above step S402. 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 the multi-stream connection parameters. The indication information sent by the UPF network element can be a multi-stream connection parameter. This process will be described in detail in subsequent embodiments and will not be repeated here.

[0168] S405: The SMF network element sends a second message and multi-stream connection parameters to the terminal device, where the second message is a message indicating that the PDU session is successfully established or updated. Optionally, the SMF sends encryption and / or integrity protection indication information to the UE.

[0169] In one possible implementation, the encryption and / or integrity protection indication information is used to indicate that encryption and / or integrity protection is to be performed on the service flow, or the encryption and / or integrity protection indication information is used to indicate that encryption and / or integrity protection is not required for the service.

[0170] In the embodiment of the present application, the multi-stream connection parameter may be carried in the second message and sent, for example, the second message carrying the multi-stream connection parameter may be encapsulated in a NAS transmission message and sent. The multi-stream connection parameter may also be sent separately from the second message, for example, the multi-stream connection parameter and the second message may be respectively encapsulated in a NAS transmission message and sent. This embodiment of the present application does not specifically limit this.

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

[0172] In a possible implementation, the SMF network element sends a flow description parameter and a corresponding relationship between encryption and / or integrity protection indication information to the terminal device to indicate that the above-mentioned service flow needs to be encrypted and / or integrity protected. For example, when 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 that do not contain encryption and / or integrity protection indication, it indicates that encryption and / or integrity protection may not be performed on the relevant service flow.

[0173] S406: The terminal device and the UPF network element transmit data based on the connection shared by multiple service flows.

[0174] To sum up, in the embodiments of the present application, the network side can control the establishment of a connection between the terminal device and the UPF network element that allows multiple service flows to be used together, thereby saving the connection establishment process and improving transmission efficiency.

[0175] for Figure 4 In a corresponding embodiment, in a possible implementation method, S402 may be implemented as follows: the SMF network element may determine that multiple service flows in a PDU session share the same connection based on PCF indication information (also referred to as PCF policy information) obtained from the PCF network element.

[0176] For example, Figure 4 As 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 (also referred to as PCF policy). S4023, the PCF network element sends 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.

[0177] In the embodiment of the present application, the basis on which the PCF network element determines that multiple service flows in a PDU session share the same connection is similar to the basis on which the SMF network element determines that multiple service flows in a PDU session share the same connection. Exemplarily, the PCF network element may use one or more of the following to determine that multiple service flows related to a PDU session share the same connection: security or encryption information of the service flow, service flow QoS parameters, service flow destination address, data network name (Data Network Name, DNN) of the service flow, transmission protocol of the service flow, type of service flow, and diversion mode of the service flow. I will not go into details here.

[0178] In one possible implementation, the policy request sent by the SMF network element to the PCF network element may include indication information for indicating the capabilities of the protocols supported by the terminal device (e.g., indication information of the QUCI capability, or indication information of the MP-QUIC capability, or indication information of the SCTP capability), indicating the protocols 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 based on the indication information of the capabilities of the protocols supported by the terminal device, as well as the local policy of the PCF network element or the terminal subscription data. When the PCF network element determines that multiple service flows in the PDU session share the same connection, it can send 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.

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

[0180] In one possible implementation, the PCF network element receives a policy request from the SMF network element. When the service flow in the PDU session is a UDF service flow, the PCF network element can determine whether multiple service flows in the PDU session can share the same connection based on the PCF network element local policy or terminal subscription data. When the PCF network element determines that multiple service flows in the PDU session share the same connection, it can send PCF policy information to the SMF network element. The PCF indication information includes information for indicating that multiple service flows in the PDU session share the same connection.

[0181] In a possible implementation, the PCF network element sends the corresponding relationship between the service flow description parameter and the encryption and / or integrity protection indication information to the SMF network element to indicate whether the above service flow needs to be encrypted and / or integrity protected. The SMF network element can then determine whether multiple service flows can be converged to the same connection based on the security or encryption information of the service flow. When multiple service flows have the same encryption and / or integrity protection indication information, the multiple service flows can be mapped to the same connection, which will not be repeated here. For example, the PCF network element can determine whether the service flow needs encryption and / or integrity protection based on local policies, user subscription data, or at least one of the access technologies for service flow transmission. The above access technologies include 3GPP access technology, non3GPP access technology, wifi access technology, or fixed network or wired access technology. For example, when the PCF network element perceives that the service flow is transmitted from non3GPP access technology, or from fixed network or wired access technology, the PCF network element sends an indication that encryption and / or integrity protection is required, or the PCF network element sends an indication that encryption and / or integrity protection is not required.

[0182] for Figure 4 In a corresponding embodiment, in a possible implementation method, S402 may be implemented as follows: the SMF network element may determine, based on the instruction of the UPF network element, that multiple service flows in the PDU session share the same connection.

[0183] In the embodiment of the present application, the basis on which the UPF network element determines that multiple service flows in a PDU session share the same connection is similar to the basis on which the SMF network element determines that multiple service 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 service flows related to a PDU session share the same connection: security or encryption information of the service flow, service flow QoS parameters, service flow destination address, data network name (Data Network Name, DNN) of the service flow, transmission protocol of the service flow, type of service flow, and diversion mode of the service flow. I will not go into details here.

[0184] In an embodiment of the present application, the SMF network element in S403 may not send multi-stream connection parameters. In a possible implementation, S403 may be replaced by the SMF network element sending service 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 the service flows in the PDU session are split and aggregated. In addition, the SMF network element may send service flow-related QoS parameters to the UPF network element. The UPF network element may determine whether multiple service flows in a PDU session can share the same connection based on the above information and / or local policies sent by the SMF network element. When the UPF network element determines that multiple service flows in a PDU session share the same connection, it may send information (such as multi-stream connection parameters) to the SMF network element to indicate that multiple service flows in the PDU session share the same connection.

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

[0186] In one possible implementation, the PCF network element sends the correspondence between the service flow description parameters and the encryption and / or integrity protection indication information to the SMF network element to indicate whether the above-mentioned service flow needs or does not need to be encrypted and / or integrity protected. Subsequently, the SMF network element sends the correspondence between the service flow description parameters and the encryption and / or integrity protection indication information to the UPF network element. The UPF network element can determine whether multiple service flows can be converged to the same connection based on the security or encryption information of the service flows. When multiple service flows have the same encryption and / or integrity protection indication information, the multiple service flows can be mapped to the same connection, which will not be repeated here.

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

[0188] Exemplarily, the SMF network element may also determine QUIC function parameters, and send 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 parameters, or transmission parameters.

[0189] The QUIC function IP address is the IP address used for the QUIC connection, such as the IP address of the QUIC function (or QUIC proxy function) on the network side, 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 can be encapsulated. In specific applications, the QUIC function IP address can be data such as characters and numbers used to identify the address.

[0190] The QUIC function port can be used to indicate the port number corresponding to the QUIC connection, including the port number corresponding to the network-side QUIC function and / or the terminal-side QUIC function. In specific applications, the QUIC function port can be data such as characters and numbers used to identify the port number.

[0191] The QUIC connection identifier is a connection identifier assigned by the SMF network element or the UPF network element to a QUIC connection, and can be used together with the QUIC connection identifier assigned by the terminal device to identify a QUIC connection, or a QUIC connection can be identified based on the connection identifier assigned by the SMF network element or the UPF network element. In one possible implementation, if the UPF network element receives a QUIC first connection identifier, the UPF network element can store the above-mentioned QUIC first connection identifier. The subsequent UPF network element can use 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 to encapsulate service data packets, for example, using the QUIC protocol header to encapsulate service data packets, 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-mentioned QUIC protocol header.

[0192] 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 based on the version information supported by the terminal device.

[0193] Security parameters can be used to encrypt data transmitted in a QUIC connection. For example, security parameters can include encryption algorithm information, encryption indication, or non-encryption indication (for example, an empty encryption algorithm indication indicates non-encryption), or security certificates, etc. In specific applications, security parameters can be characters, numbers, etc.

[0194] The transmission parameters can be used to control the transmission process of the QUIC connection. For example, the transmission parameters can be idle_timeout, stateless_reset_token, max_packet_size, etc. For details, please refer to the definition of transmission parameters in the QUIC protocol, which will not be repeated here.

[0195] The QUIC Omitted Connection Identifier Indication Parameter indicates that the QUIC connection does not use a connection identifier. If the QUIC function parameters include the QUIC Omitted Connection Identifier Indication Parameter, then after the subsequent terminal device establishes a QUIC connection, it may not use the connection identifier when performing QUIC header encapsulation on the service flow. When the UPF network element receives the QUIC Omitted Connection Identifier Indication Parameter, the UPF network element may not carry a connection identifier in the QUIC header when encapsulating data using the QUIC protocol header.

[0196] Terminal devices and UPF network elements can share the same QUIC connection for transmission of multiple service flows.

[0197] Exemplarily, in the uplink, when the terminal device initiates a QUIC connection based on the multi-stream multiplexing parameters to send a service flow data packet transmitted by the QUIC connection to the UPF network element, the service flow data packet can be encapsulated in a QUIC header, and the QUIC header can carry one or more of the QUIC function parameters. For example, a QUIC connection identifier can be carried in the QUIC header. The destination IP address or port number in the QUIC header can be set to the IP address or port number of the QUIC function. The service flow data packet can be securely encrypted based on security parameters. If a QUIC connection in which QUIC omits the connection identifier indication parameter is used, the QUIC header does not carry the QUIC connection identifier.

[0198] When a new service flow is transmitted based on a QUIC connection, the terminal device can determine whether an existing QUIC connection is available based on the multi-stream 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 optional implementation, if the above-mentioned QUIC connection has a QUIC connection identifier, the terminal device can use this QUIC connection identifier to encapsulate the service flow data packet.

[0199] Exemplarily, in the downlink, when the UPF network element initiates a QUIC connection based on the multi-stream multiplexing parameters to send service flow data packets transmitted by the QUIC connection to the terminal device, the service flow data packets can be encapsulated in a QUIC header, and the QUIC header can carry one or more of the QUIC functional parameters.

[0200] If the QUIC connection is a PDU session-sized QUIC connection, the UPF network element can use the QUIC connection to transmit multiple service flows of the PDU session. If the QUIC connection uses a connection identifier, the UPF uses the above connection identifier to encapsulate the service flow data packet of the PDU session.

[0201] 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 QUIC connection 1 for QoS flow1, and QUIC connection 2 for QoS flow2 and QoSflow3. The service flow data packets of QoS flow1 are transmitted using QUIC connection 1. The service flow data packets of QoS flow2 or QoSflow3 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.

[0202] In one 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, the UPF network element establishes the same QUIC connection for QFI1 and QFI2, and 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 SMF network element of the connection identifier. 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.

[0203] If the QUIC connection is a QUIC connection at the terminal device granularity, the UPF network element can transmit part or all of the service flow data packets of the PDU session through the QUIC connection.

[0204] In one possible implementation, Figure 4 In the corresponding embodiment, the connection shared by multiple service flows is an MP-QUIC connection.

[0205] Exemplarily, the SMF network element may also determine MP-QUIC functional parameters, and send the MP-QUIC functional 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 functional parameters. The MP-QUIC functional parameters may include one or more of the following: MP-QUIC functional IP address, MP-QUIC functional port number, MP-QUIC connection identifier, MP-QUIC omitted connection identifier indication parameter, MP-QUIC version information, security parameters, or transmission parameters.

[0206] The MP-QUIC function IP address is the IP address used for the MP-QUIC connection, such as the IP address of the MP-QUIC function (or MP-QUIC proxy function) on the network side, 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 service flow, the MP-QUIC function IP address can be encapsulated. In specific applications, the MP-QUIC function IP address can be data such as characters and numbers used to identify the address.

[0207] The MP-QUIC function port can be used to indicate the port number corresponding to the MP-QUIC connection, including the port number corresponding to the network-side MP-QUIC function and / or the terminal-side MP-QUIC function. In specific applications, the MP-QUIC function port can be data such as characters and numbers used to identify the port number.

[0208] The MP-QUIC connection identifier is a connection identifier assigned by the SMF network element or the UPF network element to an MP-QUIC connection, and can be used together with the MP-QUIC connection identifier assigned by the terminal device to identify an MP-QUIC connection, or an MP-QUIC connection can be identified 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 MP-QUIC first connection identifier, the UPF network element can store the above-mentioned MP-QUIC first connection identifier. The subsequent UPF network element can use at least one of the MP-QUIC first connection identifier or the MP-QUIC second connection identifier assigned by the SMF network element or the UPF network element to encapsulate the service data packet, for example, using the MP-QUIC protocol header to encapsulate the service data packet, and carry 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 in the above-mentioned MP-QUIC protocol header.

[0209] 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 based on the version information supported by the terminal device.

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

[0211] The transmission parameters can be used to control the transmission process of the MP-QUIC connection. For example, the transmission parameters can be idle_timeout, stateless_reset_token, max_packet_size, etc. For details, please refer to the definition of transmission parameters in the MP-QUIC protocol, which will not be repeated here.

[0212] The MP-QUIC omitted 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 omitted connection identifier indication parameter, then after the subsequent terminal device establishes an MP-QUIC connection, it may not use the connection identifier when performing MP-QUIC header encapsulation on the service flow. When the UPF network element receives the MP-QUIC omitted connection identifier indication parameter, the UPF network element may not carry a connection identifier in the MP-QUIC header when encapsulating data using the MP-QUIC protocol header.

[0213] Terminal devices and UPF network elements can share the same MP-QUIC connection for transmission of multiple service flows.

[0214] Exemplarily, in the uplink, when the terminal device initiates an MP-QUIC connection based on the multi-stream multiplexing parameters to send a service flow data packet transmitted by the MP-QUIC connection to the UPF network element, the service flow data packet can be encapsulated in an MP-QUIC header, and the MP-QUIC header can carry one or more of the MP-QUIC function parameters. 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 packet can be securely encrypted based on security parameters. If an MP-QUIC connection in which the MP-QUIC connection identifier indication parameter is omitted is used, the MP-QUIC connection identifier is not carried in the MP-QUIC header.

[0215] When a new service flow is transmitted based on an MP-QUIC connection, the terminal device can determine whether an existing MP-QUIC connection is available based on the multi-stream multiplexing parameters. If so, the UE uses the existing MP-QUIC connection to transmit 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-mentioned 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 packet.

[0216] Exemplarily, in the downlink, when the UPF network element initiates an MP-QUIC connection based on multi-stream multiplexing parameters to send service flow data packets transmitted by the MP-QUIC connection to the terminal device, the service flow data packets can be encapsulated in an MP-QUIC header, and the MP-QUIC header can carry one or more of the MP-QUIC functional parameters.

[0217] If the MP-QUIC connection is a PDU session-granular MP-QUIC connection, the UPF network element can use the MP-QUIC connection to transmit multiple service flows of the PDU session. If the MP-QUIC connection uses a connection identifier, the UPF uses the above connection identifier to encapsulate the service flow data packet of the PDU session.

[0218] 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 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 uses the relevant connection identifier to encapsulate the service data packets of this QoS flow.

[0219] In one 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, the UPF network element establishes the same MP-QUIC connection for QFI1 and QFI2, and 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 SMF network element of the connection identifier, for example, for service flows transmitted using the same MP-QUIC connection, the UPF network element returns the same connection identifier to the SMF network element.

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

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

[0222] In the embodiment of the present application, when the MP-QUIC header is used to encapsulate data, the sub-connection link can be clearly identified. If the packet loss rate is subsequently counted, it can be known which specific link has the most serious packet loss.

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

[0224] Exemplarily, the SMF network element can also 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. Figure 4 The method of an embodiment.

[0225] Combined with the above Figure 4 , the method of the embodiment of the present application is explained, and the communication device for executing the above method provided in the embodiment of the present application is described below. Those skilled in the art can understand that the method and the device can be combined and referenced with each other. A communication device provided in the embodiment of the present application can execute the steps executed by the SMF network element in the above communication method. Another communication device can execute the steps executed by the UPF network element in the communication method in the above embodiment. Still another communication device can execute the steps executed by the terminal device in the communication method in the above embodiment.

[0226] The following is an example of dividing each functional module into corresponding functions:

[0227] like Figure 5 As shown, Figure 5 The schematic diagram of the structure of the communication device provided in the embodiment of the present application is shown. The communication device can be the SMF network element, UPF network element or terminal device in the embodiment of the present application, or can be a chip applied to the SMF network element, UPF network element or terminal device. The communication device includes: a processing unit 101 and a communication unit 102. The communication unit 102 is used to support the communication device to perform the steps of sending or receiving information. The processing unit 101 is used to support the communication device to perform the steps of processing information.

[0228] In one example, taking the communication device as an SMF network element or a chip or chip system used in an 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.

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

[0230] In another example, taking the communication device as a UPF network element or a chip or chip system used in a UPF network element, the communication unit 102 is used to support the communication device to execute steps S403 and S404 in the above embodiment. The processing unit 101 is used to support the communication device to execute S406 in the above embodiment.

[0231] In another example, taking the communication device as a terminal device or a chip or chip system used 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 embodiment. The processing unit 101 is used to support the communication device to execute S406 in the above embodiment.

[0232] 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 via a communication bus.

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

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

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

[0236] Taking the communication device as an example, the chip or chip system of the SMF network element, UPF network element or terminal device in the embodiment of the present application, 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 execution instructions of the method on the SMF network element, UPF network element or terminal device side, so that the processing unit 101 executes the method on the SMF network element, UPF network element or terminal device side in the above embodiment. 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 type of static storage device that can store static information and instructions, and the storage unit 103 may be independent of the processing unit 101.

[0237] 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 performed by the SMF network element in the embodiment of the present application, there is a unit or module in the SMF network element that performs each step in the method. For each step in the method performed by the UPF network element, there is a unit or module in the UPF network element that performs each step in the method. For each step in the method performed by the terminal device, there is a unit or module in the terminal device that performs each step in the method. For example, a module that performs control or processing of the actions of the communication device may be referred to as a processing module. A module that performs steps of processing messages or data on the communication device side may be referred to as a communication module.

[0238] Figure 6 FIG. 1 is a schematic diagram of the hardware structure of the communication device provided in 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 refer to FIG. Figure 6 The hardware structure diagram of the communication device shown in FIG. The communication device includes a processor 41, a communication line 44 and at least one communication interface ( Figure 6 The communication interface 43 is used as an example for explanation).

[0239] 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 present application.

[0240] The communication link 44 may include a pathway for transmitting information between the above-mentioned components.

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

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

[0243] The memory 42 may 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 an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, 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 may be independent and connected to the processor via a communication line 44. The memory may also be integrated with the processor.

[0244] The memory 42 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 41. The processor 41 is used to execute the computer-executable instructions stored in the memory 42, thereby implementing the policy control method provided in the following embodiments of the present application.

[0245] Possibly, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, and the embodiments of the present application do not specifically limit this.

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

[0247] In a specific implementation, as an embodiment, the communication device may include multiple processors, such as Figure 6 41 and processor 45 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

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

[0249] In another example, taking the case where the communication device can be a UPF network element or a chip or chip system used in a UPF network element, the communication interface is used to support the communication device to execute S403 and S404 in the above embodiment. The processor 41 or the processor 45 is used to support the communication device to execute step S406 in the above embodiment.

[0250] like Figure 7 , which is a schematic diagram of the structure of a terminal device (hereinafter referred to as terminal) provided in an embodiment of the present application.

[0251] The terminal includes at least one processor 1211 and at least one transceiver 1212. In a possible example, the terminal may also 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.

[0252] The memory in the embodiment of the present application, such as 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, and may also be 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 compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), magnetic disk storage medium or other magnetic storage device, 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 to this.

[0253] The memory 1213 may be independent and connected to the processor 1211. In another example, the memory 1213 may also be integrated with the processor 1211, for example, integrated into a chip. The memory 1213 can store program codes for executing the technical solutions of the embodiments of the present application, and the execution is controlled by the processor 1211. The various types of computer program codes executed may also be regarded as drivers of the processor 1211. For example, the processor 1211 is used to execute the computer program codes stored in the memory 1213, thereby realizing the technical solutions in the embodiments of the present application.

[0254] The transceiver 1212 can be used to support the reception or transmission of radio frequency signals between terminals or between terminals and access devices, and 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, and the receiver Rx of the transceiver 1212 is used to receive radio frequency signals from the antennas, 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 further processes the digital baseband signals or digital intermediate frequency signals, such as demodulation and decoding. In addition, the transmitter Tx in the transceiver 1212 is also used to receive 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 send the radio frequency signals through one or more antennas 1216. Specifically, the receiver Rx can selectively perform one or more stages of down-mixing and analog-to-digital conversion processing on the RF signal to obtain a digital baseband signal or a digital intermediate frequency signal, and the order of the down-mixing and analog-to-digital conversion processing is adjustable. The transmitter Tx can selectively perform one or more stages of up-mixing and digital-to-analog conversion processing on the modulated digital baseband signal or digital intermediate frequency signal to obtain a RF signal, and the order of the up-mixing and digital-to-analog conversion processing is adjustable. The digital baseband signal and the digital intermediate frequency signal can be collectively referred to as a digital signal.

[0255] The processor 1211 may be a baseband processor or a CPU. The baseband processor and the CPU may be integrated together or separated.

[0256] 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 software program data; or assisting in completing computing tasks, such as graphics and image processing or audio processing, etc.; or the processor 1211 is used to implement one or more of the above functions.

[0257] The output device 1214 communicates with the processor 1211 and can display information in a variety of 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. The input device 1215 communicates with the processor 1211 and can accept user input in a variety of ways. For example, the input device 1215 can be a mouse, a keyboard, a touch screen device, or a sensor device.

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

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

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

[0261] In some embodiments, the memory 1540 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof:

[0262] In the embodiment of the present invention, the corresponding operation is performed by calling the operation instruction stored in the memory 1540 (the operation instruction may be stored in the operating system).

[0263] One possible implementation is that the structures of the chips used in the SMF network element, UPF network element or terminal equipment are similar, and different devices can use different chips to implement their respective functions.

[0264] The processor 1510 controls the operation 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 provides instructions and data to the processor 1510. A portion 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 the bus system 1520, wherein the bus system 1520 may include a power bus, a control bus and a status signal bus in addition to a data bus. However, for the sake of clarity, in Figure 8 Various buses are labeled as bus system 1520.

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

[0266] The method disclosed in the above embodiment of the present invention 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. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 1510 or the instructions in the form of software. The above processor 1510 can be a general processor, a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present invention can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiment of the present invention can be directly embodied as a hardware decoding processor to execute, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 1540, and the processor 1510 reads the information in the memory 1540 and completes the steps of the above method in combination with its hardware.

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

[0268] In the above embodiments, the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product. The computer program product may be pre-written in the memory, or may be downloaded and installed in the memory in the form of software.

[0269] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server, or data center. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server, a data center, etc. that includes one or more available media integration. Available media can be magnetic media, (e.g., floppy disk, hard disk, tape), optical media (e.g., DVD), or semiconductor media (e.g., solid state hard disk solid statedisk, SSD), etc.

[0270] The present application embodiment also provides a computer-readable storage medium. The method described in the above embodiment can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media may include computer storage media and communication media, and may also include any medium that can transfer a computer program from one place to another. The storage medium may be any target medium that can be accessed by a computer.

[0271] As a possible design, the computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage 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 can be accessed by the computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), 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. Disks and optical disks as used herein include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks and blue-ray disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically using lasers. The combination of the above should also be included in the scope of computer-readable media.

[0272] 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, they 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 process or function described in the above method embodiment is 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 device.

[0273] The above specific implementation methods further illustrate the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present invention should be included in the scope of protection of the present invention.

[0274] It should be noted that, in the embodiments of the present application, each network element may also adopt other definitions or names in a specific application. For example, the SMF network element may be called the first core network network element, the UPF network element may be called the second core network network element, the PCF network element may be called the third core network network element, and the AMF network element may be called the fourth core network network element, etc. Alternatively, the above network elements may also be collectively referred to as core network network elements. Alternatively, the above network elements may also be defined by other names according to actual functions, which is not specifically limited in the embodiments of the present application.

Claims

1. A communication method, characterized in that: include: The session management function SMF network element receives a first message from the terminal device; The first message is used to request to establish or update a protocol data unit (PDU) session; The SMF network element determines that multiple service flows in the PDU session share the same connection; wherein the connection shared by the multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an 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 PDU session is successfully established or updated, and the second message includes multi-stream connection parameters, and the multi-stream connection parameters are used to indicate that multiple service flows in the PDU session share the same connection transmission; the multi-stream connection parameters include service flow description parameters and multi-stream multiplexing parameters; the multi-stream multiplexing parameters are used to indicate QUIC connection information, QUIC aggregate flow connection information, MP-QUIC connection information, MP-QUIC aggregate flow connection information or SCTP connection information related to the service flow.

2. The method according to claim 1, characterized in that The service flow description parameter includes at least one of the following: One or more service flow description information, application identifier, one or more quality of service QoS flow identifiers, and PDU session identifier.

3. The method according to claim 1 or 2, characterized in that: The multi-stream multiplexing parameter includes at least one of the following: QUIC method indication information or MP-QUIC method indication information or SCTP method indication information, 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 by a QUIC connection, and the MP-QUIC indication information is used to indicate that the service flow is transmitted by an MP-QUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted by 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 the QUIC connection or the MP-QUIC connection or the SCTP connection allows one or more QoS flows to share service flows; the PDU session granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows PDU session service flows to share.

4. The method according to claim 1 or 2, characterized in that: The SMF network element determines that multiple service flows in the PDU session share the same connection, including: The SMF network element determines 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, and diversion 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 a policy control function PCF network element or indication information from a UPF network element.

5. The method according to claim 1 or 2, characterized in that: Also includes: The SMF network element sends the multi-stream connection parameters to the user plane function UPF network element.

6. The method according to claim 1 or 2, characterized in that: The SMF network element determines that multiple service flows in the PDU session share the same connection, including: When multiple service flows in the PDU session have the same encryption and / or integrity protection requirements, the SMF network element determines that the multiple service flows share the same connection; Alternatively, when multiple service flows in the PDU session have the same encryption security level, the SMF network element determines that the multiple service flows share the same connection; Alternatively, when multiple service flows in the PDU session belong to the same QoS flow, the SMF network element determines that the multiple service flows share the same connection; Alternatively, when the multiple service flows in the PDU session are non-GBR service flows with a non-guaranteed code rate, the SMF network element determines that the multiple service flows share the same connection; Alternatively, 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 transmission 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 diversion mode, or multiple service flows in the PDU session are of the same type, the SMF network element determines that the multiple service flows share the same connection.

7. The method according to claim 1 or 2, characterized in that: Also includes: The SMF network element sends encryption and / or integrity protection indication information to the UPF network element and / or the terminal device.

8. A communication method, characterized in that: include: The terminal device sends a first message to the session management function SMF network element; The first message is used to request to establish or update 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 is established or updated successfully, and the second message includes multi-stream connection parameters, and the multi-stream connection parameters are used to indicate that multiple service flows in the PDU session share the same connection transmission; the multi-stream connection parameters include service flow description parameters and multi-stream multiplexing parameters; the multi-stream multiplexing parameters are used to indicate service flow-related QUIC connection information, QUIC aggregate flow connection information, MP-QUIC connection information, MP-QUIC aggregate flow connection information or SCTP connection information; the connection shared by multiple service flows is: Internet Transport Layer Protocol QUIC connection, or aggregate flow connection in QUIC connection, or Multi-channel Internet Transport Protocol MP-QUIC connection, or aggregate flow connection in MP-QUIC connection, or Stream Control Transmission Protocol SCTP connection.

9. The method according to claim 8, characterized in that The service flow description parameter includes at least one of the following: One or more service flow description information, application identifier, one or more QoS flow identifiers, and PDU session identifier.

10. The method according to claim 8 or 9, characterized in that: The multi-stream multiplexing parameter includes at least one of the following: QUIC method indication information or MP-QUIC method indication information or SCTP method indication information, 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 by a QUIC connection, and the MP-QUIC indication information is used to indicate that the service flow is transmitted by an MP-QUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted by 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 the QUIC connection or the MP-QUIC connection or the SCTP connection allows one or more QoS flows to share service flows; the PDU session granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows PDU session service flows to share.

11. The method according to claim 10, characterized in that Also includes: The terminal device establishes a connection shared by multiple service flows with a user plane function UPF network element; The terminal device transmits the first service flow using the connection shared by the multiple service flows.

12. The method according to claim 11, characterized in that Also includes: The terminal device determines, according to the multi-stream multiplexing parameter, whether the second service stream is allowed to be shared with the connection transmitting the first service stream; In the case where the second service flow is allowed to be shared with the connection for transmitting the first service flow, the terminal device transmits the second service flow using the connection for transmitting the first service flow.

13. The method according to any one of claims 8-9, 11-12, characterized in that: Also includes: The terminal device receives encryption and / or integrity protection indication information from the SMF network element; The terminal device encrypts and / or integrity protects the service flow according to the encryption and / or integrity protection indication information, or does not encrypt and / or integrity protect the service flow.

14. A communication device, characterized in that: include: a processing unit and a communication unit; Wherein, the communication unit is used to receive a first message from a terminal device; the first message is used to request to establish or update a protocol data unit PDU session; The processing unit is configured to determine that multiple service flows in the PDU session share the same connection; wherein the connection shared by the multiple service flows is: an Internet transport layer protocol QUIC connection, or an aggregated stream connection in a QUIC connection, or a multi-channel Internet transport protocol MP-QUIC connection, or an aggregated stream connection in an MP-QUIC connection, or a stream control transmission protocol SCTP connection; The communication unit is also used to send a second message to the terminal device; the second message is used to indicate that the PDU session is successfully established or updated, and the second message includes multi-stream connection parameters, and the multi-stream connection parameters are used to indicate that multiple service flows in the PDU session share the same connection transmission; the multi-stream connection parameters include service flow description parameters and multi-stream multiplexing parameters; the multi-stream multiplexing parameters are used to indicate QUIC connection information, QUIC aggregate stream connection information, MP-QUIC connection information, MP-QUIC aggregate stream connection information or SCTP connection information related to the service flow.

15. The device according to claim 14, characterized in that The service flow description parameter includes at least one of the following: One or more service flow description information, application identifier, one or more quality of service QoS flow identifiers, and PDU session identifier.

16. The device according to claim 14 or 15, characterized in that The multi-stream multiplexing parameter includes at least one of the following: QUIC method indication information or MP-QUIC method indication information or SCTP method indication information, 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 by a QUIC connection, and the MP-QUIC indication information is used to indicate that the service flow is transmitted by an MP-QUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted by 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 the QUIC connection or the MP-QUIC connection or the SCTP connection allows one or more QoS flows to share service flows; the PDU session granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows PDU session service flows to share.

17. The device according to claim 14 or 15, characterized in that The processing unit is specifically used to 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, and diversion mode of the service flow; Alternatively, the processing unit is specifically used to determine that the service flows share the same connection based on PCF indication information from a policy control function PCF network element or indication information from a UPF network element.

18. The device according to claim 14 or 15, characterized in that The communication unit is also used to send the multi-stream connection parameters to the user plane function UPF network element.

19. The device according to claim 14 or 15, characterized in that The processing unit is specifically used for: When multiple service flows in the PDU session have the same encryption and / or integrity protection requirements, determining that the multiple service flows share the same connection; Alternatively, when multiple service flows in the PDU session have the same encryption security level, determining that the multiple service flows share the same connection; Alternatively, when multiple service flows in the PDU session belong to the same QoS flow, determining that the multiple service flows share the same connection; Alternatively, when the multiple service flows in the PDU session are non-GBR service flows, determining that the multiple service flows share the same connection; Alternatively, 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 transmission 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 diversion mode, or multiple service flows in the PDU session are of the same type, it is determined that the multiple service flows share the same connection.

20. The device according to claim 14 or 15, characterized in that The communication unit is also used to send encryption and / or integrity protection indication information to the UPF network element and / or the terminal device.

21. A communication device, characterized in that: including a communication unit; Wherein, the communication unit is used to send a first message to a session management function SMF network element; the first message is used to request to establish or update a protocol data unit PDU session; Among them, the communication unit is also used to receive a second message from the SMF network element; the second message is used to indicate that the PDU session is established or updated successfully, and the second message includes multi-stream connection parameters, and the multi-stream connection parameters are used to indicate that multiple business flows in the PDU session share the same connection transmission; the multi-stream connection parameters include business flow description parameters and multi-stream multiplexing parameters; the multi-stream multiplexing parameters are used to indicate business flow-related QUIC connection information, QUIC aggregate flow connection information, MP-QUIC connection information, MP-QUIC aggregate flow connection information or SCTP connection information; the connection shared by multiple business flows is: Internet Transport Layer Protocol QUIC connection, or aggregate flow connection in QUIC connection, or Multi-channel Internet Transport Protocol MP-QUIC connection, or aggregate flow connection in MP-QUIC connection, or Stream Control Transmission Protocol SCTP connection.

22. The device according to claim 21, characterized in that The service flow description parameter includes at least one of the following: One or more service flow description information, application identifier, one or more QoS flow identifiers, and PDU session identifier.

23. The device according to claim 21 or 22, characterized in that The multi-stream multiplexing parameter includes at least one of the following: QUIC method indication information or MP-QUIC method indication information or SCTP method indication information, 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 by a QUIC connection, and the MP-QUIC indication information is used to indicate that the service flow is transmitted by an MP-QUIC connection; the SCTP method indication information is used to indicate that the service flow is transmitted by 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 the QUIC connection or the MP-QUIC connection or the SCTP connection allows one or more QoS flows to share service flows; the PDU session granularity indication information is used to indicate that the QUIC connection or the MP-QUIC connection or the SCTP connection allows PDU session service flows to share.

24. The device according to claim 23, characterized in that Also includes a processing unit; The processing unit is used to establish a connection shared by multiple service flows of a user plane function UPF network element; The processing unit is further used to transmit the first service flow by using the connection shared by the multiple service flows.

25. The device according to claim 24, characterized in that The processing unit is further used to determine whether the second service flow is allowed to be shared with the connection transmitting the first service flow according to the multi-stream 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 be shared with the connection for transmitting the first service flow.

26. The device according to any one of claims 24-25, characterized in that Also includes: The communication unit is further used 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.

27. A communication device, characterized in that: include: Processor and communication interface; The communication interface is used to execute the operation of sending and receiving messages in the SMF network element in the communication method as described in any one of claims 1-7, or to execute the operation of sending and receiving messages in the terminal device in the communication method as described in any one of claims 8-13; the processor runs instructions to execute the operation of processing or controlling in the SMF network element in the communication method as described in any one of claims 1-7, or to execute the operation of processing or controlling in the terminal device in the communication method as described in any one of claims 8-13.

28. A chip, characterized in that: The chip includes 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 used to run a computer program or instruction to implement the communication method as described in any one of claims 1 to 7, or to implement the communication method as described in any one of claims 8 to 13; the communication interface is used to communicate with other modules outside the chip.

29. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed, the communication method according to any one of claims 1 to 7 is implemented, or the communication method according to any one of claims 8 to 13 is implemented.

Images