Communication method and device

By establishing a QUIC or MP-QUIC connection between the terminal device and the UPF network element, the problem that UDP service flow cannot be diverted through multiple access technology in the prior art is solved, and efficient UDP service flow transmission is achieved.

CN113365369BActive Publication Date: 2025-02-25HUAWEI TECH CO LTD

Patent Information

Application Number
CN202010152386.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-03-06
Publication Date
2025-02-25
Estimated Expiration
2040-03-06

AI Technical Summary

Technical Problem

The prior art cannot realize the diversion of the User Datagram Protocol (UDP) service flow through multi-access technology, which limits the transmission efficiency of the UDP protocol service flow.

Method used

Fast UDP Internet connection (QUIC) or multi-path QUIC connection (MP-QUIC) is established between the network-side control terminal device and the user plane function (UPF) network element to realize the flow-grained data transmission of UDP service flow.

Benefits of technology

The flow-grained shunt and convergence of UDP service flow is realized, the service transmission bandwidth is improved, and the problem of low UDP service flow transmission efficiency in the prior art is solved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113365369B_ABST
    Figure CN113365369B_ABST
Patent Text Reader

Abstract

The embodiments of the present application provide a communication method and apparatus, and relate to the field of communication. The method of the embodiments of the present application can be controlled by the network side to establish a QUIC connection or an MP‑QUIC link between the terminal device and the UPF network element, so that the data transmission of the flow granularity can be realized based on the QUIC connection or the MP‑QUIC link for the service flow of UDP. 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 second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted by the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted by the MP‑QUIC method.
Need to check novelty before this filing date? Find Prior Art

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, service flows using the User Datagram Protocol (UDP) cannot be split through the multi-access technology. 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 user datagram protocol (quick UDP internet connection, QUIC) connection or a multi-path quick UDP internet connection (multi-path quick UDP internet connection, MP-QUIC) connection between a terminal device and a UPF network element, thereby realizing data transmission based on the QUIC connection or the MP-QUIC connection as a UDP business flow.

[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, and the first message includes first indication information, and the first indication information is used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or is used to indicate that the terminal device supports the multi-channel Internet transmission protocol MP-QUIC capability. The SMF network element determines that the service flow in the PDU session is transmitted using the QUIC method or the MP-QUIC method. The SMF network element sends a second message to the terminal device, and the second message is used to indicate that the PDU session is successfully established or updated. The second message includes second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0007] Usually, UE and UPF network elements need to use transmission control protocol (TCP) or multi-path TCP (MPTCP) to achieve packet granularity diversion, which also requires that the service flow diverted by packet granularity must support MPTCP or TCP. In existing services, although TCP or MPTCP is one of the important and widely used transmission technologies, most service flows, such as video services, still use user datagram protocol (UDP) transmission technology, resulting in service flows using UDP protocol cannot be transmitted through multiple access technology. Therefore, in an embodiment of the present application, the network side can control the establishment of a QUIC connection or MP-QUIC link between the terminal device and the UPF network element, so that data transmission with flow granularity can be achieved based on the QUIC connection or MP-QUIC link for the UDP service flow.

[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 and a first indication information from a terminal device. The first message is used to request the establishment or update of a protocol data unit PDU session, and the first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or is used to indicate that the terminal device supports the multi-channel Internet transmission protocol MP-QUIC capability. The SMF network element determines that the service flow in the PDU session is transmitted using the QUIC method or the MP-QUIC method. The SMF network element sends a second message and a second indication information to the terminal device, the second message is used to indicate that the PDU session is established or updated successfully, and the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[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 first indication information is not included in the first message, and the second indication information is 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 second indication information includes QUIC functional parameters or MP-QUIC functional parameters, and the method also includes: the SMF network element obtains the QUIC functional parameters or MP-QUIC functional parameters.

[0012] In a possible implementation, the SMF network element obtains the QUIC function parameter or the MP-QUIC function parameter, including: the SMF network element sends, to the user plane function UPF network element, indication information for indicating that the service flow in the PDU session is transmitted by the QUIC method, or indication information for indicating that the service flow in the PDU session is transmitted by the MP-QUIC method. The SMF network element receives the QUIC function parameter or the MP-QUIC function parameter from the UPF network element.

[0013] In a possible implementation, the SMF network element acquires the QUIC function parameter or the MP-QUIC function parameter, including: the SMF network element allocates the QUIC function parameter or the MP-QUIC function parameter. The method also includes: the SMF network element sends the QUIC function parameter or the MP-QUIC function parameter to the UPF network element.

[0014] In one possible implementation, the indication information used to indicate that the terminal device supports QUIC capabilities includes one or more of the following: a QUIC omitted connection identifier indication parameter, a QUIC first connection identifier, a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information. Among them, the QUIC first connection identifier is a connection identifier assigned by the terminal device to the QUIC connection. Alternatively, the indication information used to indicate that the terminal device supports MP-QUIC capabilities includes one or more of the following: an MP-QUIC omitted connection identifier indication parameter, a MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter, or a first MP-QUIC version information. Among them, the MP-QUIC first connection identifier is a connection identifier assigned by the terminal device to the MP-QUIC connection.

[0015] In one possible implementation, the QUIC function parameters include one or more of the following: QUIC function IP address, QUIC function port number, QUIC second connection identifier, QUIC connection identifier omitted indication parameter, second QUIC version information, security parameters, or transport parameters. Alternatively, the MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC connection identifier omitted indication, second MP-QUIC version information, security parameters, or transport parameters.

[0016] In a possible implementation, the MP-QUIC function parameter further includes one or more of the following: a sub-connection identifier or an access technology indication parameter or tunnel identification information, wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter or the tunnel identification information.

[0017] In a possible implementation, the SMF network element determines whether a service flow in a PDU session is transmitted using the QUIC method or the MP-QUIC method, including: the SMF network element receives QUIC method indication information or MP-QUIC method indication information from a policy control function PCF network element. The QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method. The MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[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 a protocol data unit to establish or update a protocol data unit PDU session. The first message includes first indication information. The first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability. 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. The second message includes second indication information. The second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0019] In a fourth aspect, an embodiment of the present application provides a communication method, comprising: a terminal device sends a first message and a first indication information to a session management function SMF network element. The first message is used to request a protocol data unit to establish or update a protocol data unit PDU session, and the first indication information is an indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or an indication information used to indicate that the terminal device supports the multi-channel Internet transmission protocol MP-QUIC capability. The terminal device receives a second message and a second indication information from the SMF network element. The second message is used to indicate that the PDU session is established or updated successfully, and the second indication information is used to indicate that the service flow of the PDU session is transmitted using the QUIC method, or to indicate that the service flow of the PDU session is transmitted using the MP-QUIC method.

[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 first indication information is not included in the first message, and the second indication information is not included in the second message, which will not be repeated here.

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

[0022] The specific contents of the indication information used to indicate that the terminal device supports QUIC capability, the indication information used to indicate that the terminal device supports MP-QUIC capability, the second indication information, the QUIC functional parameters and the MPQUIC functional 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 QUIC connection or an MP-QUIC connection with a user plane function UPF network element based on the second message. The terminal device uses the QUIC connection or the MP-QUIC connection for data transmission.

[0024] In one possible implementation, the second message also includes a service flow identifier or an application identifier, and the terminal device uses a QUIC connection or an MP-QUIC connection to transmit data, including: the terminal device uses a QUIC connection or an MP-QUIC connection to transmit a service flow data packet corresponding to the service flow identifier or the application identifier.

[0025] In a possible implementation, a terminal device uses a QUIC connection or an MP-QUIC connection for data transmission, including: the terminal device performs QUIC header encapsulation or MP-QUIC header encapsulation on the data packet to be transmitted. The QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters. The terminal device sends the encapsulated QUIC packet or the encapsulated MP-QUIC packet to the UPF network element.

[0026] In a fifth aspect, an embodiment of the present application provides a communication method, including: a user plane function UPF network element receives QUIC method indication information or MP-QUIC method indication information from a session management function SMF network element. The QUIC method indication information is used to indicate that the service flow in the protocol data unit PDU session is transmitted using the QUIC method. The MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method. The UPF network element establishes a QUIC connection or MP-QUIC connection with the terminal device based on the QUIC method indication information or the MP-QUIC method indication information.

[0027] In one possible implementation, the UPF network element establishes a QUIC connection or MP-QUIC connection with a terminal device based on QUIC method indication information or MP-QUIC method indication information, including: the UPF network element allocates QUIC functional parameters or MP-QUIC functional parameters based on the QUIC method indication information or MP-QUIC method indication information. The UPF network element uses the QUIC functional parameters or MP-QUIC functional parameters to establish a QUIC connection or MP-QUIC connection with the terminal device. The method also includes: the UPF network element sends the QUIC functional parameters or MP-QUIC functional parameters to the SMF network element.

[0028] In one possible implementation, the UPF network element establishes a QUIC connection or an MP-QUIC connection with a terminal device based on the QUIC method indication information or the MP-QUIC method indication information, including: the UPF network element receives the QUIC function parameters or the MP-QUIC function parameters from the SMF network element. The QUIC function parameters or the MP-QUIC function parameters are allocated by the SMF network element. The UPF network element uses the QUIC function parameters or the MP-QUIC function parameters to establish a QUIC connection or an MP-QUIC connection with the terminal device.

[0029] In one possible implementation, the QUIC function parameters include one or more of the following: QUIC function IP address, QUIC function port number, QUIC second connection identifier, QUIC connection identifier omitted indication parameter, second QUIC version information, security parameters, or transport parameters. Alternatively, the MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC connection identifier omitted indication, second MP-QUIC version information, security parameters, or transport parameters.

[0030] In a possible implementation, the MP-QUIC function parameter further includes one or more of the following: a sub-connection identifier or an access technology indication parameter or tunnel identification information, wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter or the tunnel identification information.

[0031] In a possible implementation, the method further includes: a UPF network element receiving a data packet from a terminal device, wherein the data packet is a data packet encapsulated by a QUIC header or an MP-QUIC header, wherein the QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters.

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

[0033] 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, and the first message includes first indication information, and the first indication information is used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or used to indicate that the terminal device supports the multi-channel Internet transmission protocol MP-QUIC capability. The processing unit is used to determine whether the service flow in the PDU session is transmitted using the QUIC method or the MP-QUIC method. The communication unit is also used to send a second message to the terminal device, and the second message is used to indicate that the PDU session is successfully established or updated, and the second message includes second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0034] Alternatively, exemplarily, a communication unit is used to receive a first message and first indication information from a terminal device. The first message is used to request the establishment or update of a protocol data unit PDU session, and the first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transmission protocol MP-QUIC capability. The processing unit is used to determine whether the service flow in the PDU session is transmitted using the QUIC method or the MP-QUIC method. The communication unit is also used to send a second message and second indication information to the terminal device, the second message is used to indicate that the PDU session is successfully established or updated, and the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0035] In a possible implementation, the second indication information includes QUIC functional parameters or MP-QUIC functional parameters. The communication unit is further used to obtain QUIC functional parameters or MP-QUIC functional parameters.

[0036] In a possible implementation, the communication unit is specifically used to send indication information for indicating that the service flow in the PDU session is transmitted by the QUIC method, or for indicating that the service flow in the PDU session is transmitted by the MP-QUIC method to the user plane function UPF network element. And, receive the QUIC function parameter or MP-QUIC function parameter from the UPF network element.

[0037] In a possible implementation, the processing unit is further used to allocate QUIC functional parameters or MP-QUIC functional parameters. The communication unit is further used to send QUIC functional parameters or MP-QUIC functional parameters to the UPF network element.

[0038] The specific contents of the indication information used to indicate that the terminal device supports QUIC capability, the indication information used to indicate that the terminal device supports MP-QUIC capability, the second indication information, the QUIC functional parameters and the MPQUIC functional parameters involved in the sixth aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0039] In a possible implementation, the communication unit is further configured to receive QUIC method indication information or MP-QUIC method indication information from a policy control function PCF network element. The QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method. The MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0040] 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.).

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

[0042] 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 a protocol data unit to establish or update a protocol data unit PDU session. The first message includes first indication information. The first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability. 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. The second message includes second indication information. The second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0043] Alternatively, exemplarily, the communication unit is used to send a first message and a first indication information to a session management function SMF network element. The first message is used to request a protocol data unit to establish or update a protocol data unit PDU session, and the first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability. The communication unit is also used to receive a second message and a second indication information from the SMF network element. The second message is used to indicate that the PDU session is established or updated successfully, and the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0044] The specific contents of the indication information used to indicate that the terminal device supports QUIC capability, the indication information used to indicate that the terminal device supports MP-QUIC capability, the second indication information, the QUIC functional parameters and the MPQUIC functional parameters involved in the seventh aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0045] In a possible implementation, a processing unit is further included. The processing unit is configured to establish a QUIC connection or an MP-QUIC connection with a user plane function UPF network element based on the second message. The processing unit is also configured to use the QUIC connection or the MP-QUIC connection for data transmission.

[0046] In one possible implementation, the second message also includes a service flow identifier or an application identifier, and a processing unit is specifically used to transmit the service flow data packet corresponding to the service flow identifier or the application identifier using a QUIC connection or an MP-QUIC connection.

[0047] In one possible implementation, the communication unit is specifically used to perform QUIC header encapsulation or MP-QUIC header encapsulation on the data packet to be transmitted. The QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters. The communication unit is also used to send the encapsulated QUIC packet or the encapsulated MP-QUIC packet to the UPF network element.

[0048] 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.).

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

[0050] Exemplarily, a communication unit is used to receive QUIC method indication information or MP-QUIC method indication information from a session management function SMF network element. The QUIC method indication information is used to indicate that the service flow in the protocol data unit PDU session is transmitted using the QUIC method. The MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method. The processing unit is used to establish a QUIC connection or MP-QUIC connection with the terminal device based on the QUIC method indication information or the MP-QUIC method indication information.

[0051] In one possible implementation, the processing unit is specifically used to allocate QUIC functional parameters or MP-QUIC functional parameters based on the QUIC method indication information or the MP-QUIC method indication information. A QUIC connection or MP-QUIC connection with a terminal device is established using the QUIC functional parameters or the MP-QUIC functional parameters. The communication unit is also used to send the QUIC functional parameters or the MP-QUIC functional parameters to the SMF network element.

[0052] In one possible implementation, the communication unit is further used to receive QUIC functional parameters or MP-QUIC functional parameters from the SMF network element. The QUIC functional parameters or MP-QUIC functional parameters are allocated by the SMF network element. The processing unit is specifically used to establish a QUIC connection or MP-QUIC connection with the terminal device using the QUIC functional parameters or MP-QUIC functional parameters.

[0053] The specific contents of the indication information used to indicate that the terminal device supports QUIC capability, the indication information used to indicate that the terminal device supports MP-QUIC capability, the second indication information, the QUIC functional parameters and the MPQUIC functional parameters involved in the eighth aspect can refer to the specific contents of the first aspect and will not be repeated here.

[0054] In a possible implementation, the communication unit is further configured to receive a data packet from a terminal device, where the data packet is a data packet encapsulated by a QUIC header or an MP-QUIC header, wherein the QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters.

[0055] 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.).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0076] In the twenty-eighth aspect, the present application provides a chip or a chip system, which includes at least one processor and a communication interface, the communication interface and 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 fourth aspect to the fourth aspect.

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

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

[0079] 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.).

[0080] 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

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

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

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

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

[0085] Figure 5 A flowchart of another communication method provided in an embodiment of the present application;

[0086] Figure 6 A flowchart of another communication method provided in an embodiment of the present application;

[0087] Figure 7 A flowchart of another communication method provided in an embodiment of the present application;

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

[0089] Fig. 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0090] Fig.10 A schematic diagram of the structure of a terminal provided in an embodiment of the present application;

[0091] Fig.11 A schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

[0095] The embodiments of the present application provide a communication method. The method of the embodiments of the present application can be applied in a long term evolution (LTE) system, in a fifth generation mobile communication (5G) system, or in a future mobile communication system.

[0096] For example, Figure 2 A 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).

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

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

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

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

[0101] 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).

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

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

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

[0105] 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).

[0106] The method processing of the embodiment of the present application can be applied to the above-mentioned 5G 3GPP access architecture, or non3GPP access architecture, or 3GPP and non3GPP simultaneous access architecture, and can also be applied to 5G cellular (NG-RAN) and 4G cellular (LTE) simultaneous access architecture, etc. The embodiment of the present application does not specifically limit the network architecture. Figure 2 , Figure 3 This is only an exemplary architecture diagram. Figure 2 , Figure 3 In addition to the functional units shown in , the network architecture may also include other functional units.

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

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

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

[0110] The terminal device involved in the embodiments of the present application may support QUIC capability or MP-QUIC capability. If the terminal device supports QUIC capability, the subsequent terminal device can use the QUIC protocol to establish 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. The MP-QUIC connection can use the various parameters in the QUIC connection. The difference between the MP-QUIC connection and the QUIC connection is that the MP-QUIC connection contains multiple sub-connections. The establishment method of the sub-connection will be described in the subsequent part corresponding to the MP-QUIC connection, and will not be repeated here.

[0111] 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 process the data to be transmitted. A QUIC connection can support one or more access technologies or tunnels.

[0112] MP-QUIC is a low-latency multi-channel 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 process the data to be transmitted. The MP-QUIC connection contains multiple sub-connections, each of which can correspond to a sub-connection identifier, and each sub-connection can support different access technologies or tunnels.

[0113] In one possible implementation, the QUIC connection may be a stream-granular QUIC connection, for example, a QUIC connection is established for a service flow, or a QUIC connection can only be used by one service flow. The MP-QUIC connection may be a stream-granular MP-QUIC connection, for example, a QUIC connection is established for a service flow, or a QUIC connection can only be used by one service flow.

[0114] The first indication information involved in the embodiment of the present application may be included in the first message and sent. The first indication information may also be sent without being included in the first message. For example, the first indication information and the first message may both be encapsulated in a non-access stratum (NAS) transmission message and sent. The embodiment of the present application does not specifically limit this.

[0115] In the case where the terminal device supports QUIC capability, the first indication information may include indication information for indicating that the terminal device supports Internet transport layer protocol QUIC capability. The indication information for indicating that the terminal device supports QUIC capability may be any form of parameters, etc., which is not specifically limited in the embodiments of the present application.

[0116] Exemplarily, the indication information used to indicate that the terminal device supports QUIC capability includes one or more of the following: a QUIC first connection identifier (connection ID), a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information.

[0117] The QUIC first connection identifier is a QUIC connection identifier assigned by the terminal device to the QUIC connection. When the first indication information includes the QUIC first connection identifier, it can indicate that the terminal device not only has the ability to support QUIC, but also assigns a connection identifier to the QUIC connection that may be established. If a QUIC connection is established later, the terminal device can use the QUIC first connection identifier to perform QUIC header encapsulation on the service flow. In specific applications, the QUIC first connection identifier can be characters, numbers, etc.

[0118] The QUIC capability indication parameter can be used to indicate that the terminal device has the ability to support QUIC. For example, if the terminal device supports the QUIC protocol, it is considered that the terminal device has the ability to support QUIC. When the QUIC capability indication parameter is included in the first indication information, it can be indicated that the terminal device has the ability to support QUIC. If the QUIC capability indication parameter is included in the first indication information, if a QUIC connection is established later, the terminal device can use the connection identifier assigned by the network side to the QUIC connection to perform QUIC header encapsulation on the service flow, etc. In specific applications, the QUIC capability indication parameter can specifically be characters, numbers, etc.

[0119] The QUIC request indication parameter can be used to indicate that the terminal device requests a QUIC connection. When the QUIC request indication parameter is included in the first indication information, it can indicate that the terminal device has the ability to support QUIC. If the first indication information only includes the QUIC request indication parameter, if a QUIC connection is established later, the terminal device can use the connection identifier assigned by the network side to the QUIC connection to perform QUIC header encapsulation on the service flow, etc. In specific applications, the QUIC request indication parameter can specifically be characters, numbers, etc.

[0120] The first QUIC version information can be used to indicate the version number of QUIC supported by the terminal device, etc. When the first QUIC version information is included in the first indication information, it can be indicated that the terminal device not only has the ability to support QUIC, but also supports a version of QUIC corresponding to the first QUIC version information. The first QUIC version information may include one or more QUIC version information, that is, the terminal device may support one or more QUIC versions. If a QUIC connection is established later, the network side and the terminal device can negotiate to use any QUIC version corresponding to the first QUIC version information. In specific applications, the QUIC version information can specifically be characters, numbers, etc.

[0121] In one possible implementation, in the case where the indication information used to indicate that the terminal device supports QUIC capability includes one of the QUIC first connection identifier, the QUIC omitted connection identifier, the QUIC capability indication parameter, or the first QUIC version information, other information required to establish a QUIC connection may be subsequently configured by the network side based on the performance of the terminal device, etc., or may be subsequently determined by negotiation between the network side and the terminal device, or other processing methods may be adopted, so that the terminal device can ultimately establish a QUIC connection. In the case where the indication information used to indicate that the terminal device supports QUIC capability includes only multiple of the QUIC first connection identifier, the QUIC capability indication parameter, or the first QUIC version information, the terminal device may establish a QUIC connection based on multiple pieces of information.

[0122] In one possible implementation, when the indication information used to indicate that the terminal device supports QUIC capability may include a QUIC first connection identifier, a QUIC capability indication parameter, or multiple parameters in the first QUIC version information, the terminal device may establish a QUIC connection based on multiple information.

[0123] In one possible implementation, when the indication information used to indicate that the terminal device supports QUIC capability may include a QUIC omitted connection identifier, a QUIC capability indication parameter, or multiple parameters in the first QUIC version information, the terminal device can establish a QUIC connection based on multiple information.

[0124] The QUIC omitted connection identifier indication parameter indicates that the QUIC connection does not use a connection identifier. In one possible implementation, if the first indication information includes the QUIC omitted connection identifier indication parameter, then after the subsequent terminal device establishes a QUIC connection, the connection identifier may not be used when the QUIC header is encapsulated for the service flow. In specific applications, the QUIC omitted connection identifier indication parameter may be a character, a number, etc.

[0125] In a possible implementation, in the first indication information, the QUIC first connection identifier and the QUIC omitted connection identifier indication parameter may not be carried at the same time. When the QUIC first connection identifier is carried in the first message, the connection identifier can be used for subsequent establishment of a QUIC connection. When the QUIC omitted connection identifier indication parameter is carried in the first message, the connection identifier may not be used for subsequent establishment of a QUIC connection.

[0126] In one possible implementation, the first indication information may include one or more of a QUIC omitted connection identifier indication parameter, a QUIC capability indication parameter, or the first QUIC version information. It can also be understood that the QUIC omitted connection identifier indication parameter and the QUIC capability indication parameter or the first QUIC version information may be included in the first indication information at the same time.

[0127] When the terminal device supports MP-QUIC capability, the indication information used to indicate that the terminal device supports MP-QUIC capability includes one or more of the following: an MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter or a first MP-QUIC version information; wherein the MP-QUIC first connection identifier is a QUIC connection identifier assigned by the terminal device to the MP-QUIC connection.

[0128] The MP-QUIC first connection identifier is the MP-QUIC connection identifier assigned by the terminal device to the MP-QUIC connection. When the MP-QUIC first connection identifier is included in the first indication information, it can be indicated that the terminal device not only has the ability to support MP-QUIC, but also assigns a connection identifier to the MP-QUIC connection that may be established. If an MP-QUIC connection is established subsequently, the terminal device can use the MP-QUIC first connection identifier to perform MP-QUIC header encapsulation on the service flow. In specific applications, the MP-QUIC first connection identifier can be characters, numbers, etc.

[0129] The MP-QUIC capability indication parameter can be used to indicate that the terminal device has the ability to support MP-QUIC. For example, if the terminal device supports the MP-QUIC protocol, it is considered that the terminal device has the ability to support MP-QUIC. When the MP-QUIC capability indication parameter is included in the first indication information, it can be indicated that the terminal device has the ability to support MP-QUIC. If the MP-QUIC capability indication parameter is included in the first indication information, if an MP-QUIC connection is established subsequently, the terminal device can use the connection identifier allocated by the network side for the MP-QUIC connection to encapsulate the service flow in the MP-QUIC header, etc. In specific applications, the MP-QUIC capability indication parameter can specifically be characters, numbers, etc.

[0130] The MP-QUIC request indication parameter can be used to indicate that the terminal device requests an MP-QUIC connection. When the MP-QUIC request indication parameter is included in the first indication information, it can indicate that the terminal device has the ability to support MP-QUIC. If the first indication information only includes the MP-QUIC request indication parameter, if an MP-QUIC connection is established subsequently, the terminal device can use the connection identifier allocated by the network side for the MP-QUIC connection to encapsulate the service flow in the MP-QUIC header, etc. In specific applications, the MP-QUIC request indication parameter can specifically be characters, numbers, etc.

[0131] The first MP-QUIC version information can be used to indicate the version number of MP-QUIC supported by the terminal device, etc. In the case where the first indication information includes the first MP-QUIC version information, it can be indicated that the terminal device not only has the ability to support MP-QUIC, but also supports the MP-QUIC version corresponding to the first MP-QUIC version information. The first MP-QUIC version information may include one or more MP-QUIC version information, that is, the terminal device may support one or more MP-QUIC versions. If an MP-QUIC connection is established subsequently, the network side and the terminal device can negotiate to use any MP-QUIC version corresponding to the first MP-QUIC version information. In specific applications, the MP-QUIC version information may specifically be characters, numbers, etc.

[0132] In one possible implementation, in a case where the indication information used to indicate that the terminal device supports the MP-QUIC capability includes one of the MP-QUIC first connection identifier, the MP-QUIC omitted connection identifier, the MP-QUIC capability indication parameter, or the first MP-QUIC version information, other information required to establish the MP-QUIC connection may be subsequently configured by the network side based on the performance of the terminal device, etc., or may be subsequently determined by negotiation between the network side and the terminal device, or other processing methods may be adopted, so that the terminal device can ultimately establish the MP-QUIC connection. In a case where the indication information used to indicate that the terminal device supports the MP-QUIC capability includes only multiple MP-QUIC first connection identifier, MP-QUIC capability indication parameter, or the first MP-QUIC version information, the terminal device may establish the MP-QUIC connection based on multiple information.

[0133] In one possible implementation, when the indication information used to indicate that the terminal device supports MP-QUIC capability may include a first MP-QUIC connection identifier, an MP-QUIC capability indication parameter, or multiple parameters in the first MP-QUIC version information, the terminal device may establish an MP-QUIC connection based on multiple information.

[0134] In one possible implementation, when the indication information used to indicate that the terminal device supports MP-QUIC capability may include an MP-QUIC omitted connection identifier, an MP-QUIC capability indication parameter, or multiple parameters in the first MP-QUIC version information, the terminal device may establish an MP-QUIC connection based on multiple information.

[0135] The MP-QUIC omitted connection identifier indication parameter indicates that the MP-QUIC connection does not use a connection identifier. In one possible implementation, if the first indication information includes the MP-QUIC omitted connection identifier indication parameter, then after the subsequent terminal device establishes an MP-QUIC connection, the connection identifier may not be used when the service flow is encapsulated in the MP-QUIC header. In specific applications, the MP-QUIC omitted connection identifier indication parameter may be a character, a number, etc.

[0136] In a possible implementation, in the first indication information, the MP-QUIC first connection identifier and the MP-QUIC omitted connection identifier indication parameter may not be carried at the same time. When the MP-QUIC first connection identifier is carried in the first message, the connection identifier may be used for subsequent establishment of an MP-QUIC connection. When the MP-QUIC omitted connection identifier indication parameter is carried in the first message, the connection identifier may not be used for subsequent establishment of an MP-QUIC connection.

[0137] In one possible implementation, the first indication information may include one or more of an MP-QUIC omitted connection identifier indication parameter, an MP-QUIC capability indication parameter, or first MP-QUIC version information. It can also be understood that the MP-QUIC omitted connection identifier indication parameter and the MP-QUIC capability indication parameter or the first MP-QUIC version information may be included in the first indication information at the same time.

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

[0139] The second indication information involved in the embodiment of the present application may be included in the second message and sent. The second indication information may also be sent without being included in the second message. For example, the second indication information and the second message may both be encapsulated in a NAS transmission message and sent. The embodiment of the present application does not specifically limit this.

[0140] The second indication information may include QUIC method indication information or MP-QUIC method indication information. The QUIC method indication information is used to indicate that the service flow of the PDU session is transmitted using the QUIC method. The MP-QUIC method indication information is used to indicate that the service flow of the PDU session is transmitted using the MP-QUIC method.

[0141] The QUIC method indication information can be characters, numbers, etc.

[0142] Specifically, when the service stream of a PDU session is transmitted using the QUIC method, one or more service streams in the PDU session are transmitted, the service streams are encapsulated using a QUIC header and then transmitted in a QUIC connection.

[0143] The MP-QUIC method indication information can be characters, numbers, etc.

[0144] Specifically, when one or more service flows in a PDU session are transmitted using the MP-QUIC method, the service flows are encapsulated using an MP-QUIC header and then transmitted in the MP-QUIC connection.

[0145] In a possible implementation, the second message may also include a service flow identifier and / or an application identifier, where the service flow identifier may be a five-tuple of the Internet Protocol (IP) (source and destination IP addresses, source and destination port numbers, and protocol type), or a PDU session identifier (when all service flows in this PDU session are transmitted using a QUIC connection), etc. The application identifier is used to identify the service flow of a specific application. The subsequent terminal device may transmit the service flow corresponding to the service flow identifier or the application identifier using a QUIC connection or an MP-QUIC connection.

[0146] In one possible implementation, after receiving the QUIC method indication information or the MP-QUIC method indication information, the terminal device may further send a QUIC message or an MP-QUIC message to the UPF network element to obtain the parameters required to establish a QUIC connection or an MP-QUIC connection from the UPF network element, and then establish a QUIC connection or an MP-QUIC connection with the UPF network element.

[0147] In one possible implementation, the second indication information may include QUIC function parameters (QUIC function information) or MP-QUIC function parameters (MP-QUIC function information), and the terminal device may establish a QUIC connection or MP-QUIC connection with the UPF network element when establishing a PDU session. In specific applications, the QUIC function parameters or MP-QUIC function parameters may be configured by the SMF network element or the UPF network element for the terminal device. QUIC function parameters may also be referred to as QUIC connection-related parameters, or QUIC connection parameters, etc. MP-QUIC function parameters may also be referred to as MP-QUIC connection-related parameters, or MP-QUIC connection parameters, etc.

[0148] In one possible implementation, the QUIC function parameters may include one or more of the following: QUIC function IP address, QUIC function port number, QUIC second connection identifier, second QUIC version information, security parameters, or transmission parameters.

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

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

[0151] The QUIC second 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 above-mentioned QUIC first connection identifier assigned by the terminal device to jointly identify a QUIC connection, or identify a QUIC connection based on the above-mentioned second connection identifier. In a possible implementation, if the UPF network element receives the 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 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.

[0152] The second QUIC version information is the QUIC version used for the QUIC connection. The second QUIC version information may be the QUIC version information supported by the SMF network element or the UPF network element, or the QUIC version information determined by the SMF network element or the UPF network element according to the version information supported by the terminal device, such as selecting any version information supported by the network side from the version information supported by the terminal device as the second QUIC version information. Exemplarily, the second QUIC version information may be any one of the first QUIC version information.

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

[0154] The transmission parameters can be used to control the transmission process of the QUIC connection. The transmission parameters can be, for example, original_connection_id, max_idle_timeout, initial_max_data, initial_max_stream_data_bidi_local, initial_max_stream_data_bidi_remote, initial_max_stream_data_uni, initial_max_streams_bidi, initial_max_streams_uni, ack_delay_exponent, max_ack_delay, disable_active_migration, preferred_address, active_connection_id_limit, 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.

[0155] In one possible implementation, the QUIC function parameters include one or more of the following: a QUIC function IP address, a QUIC function port number, a QUIC omitted connection identifier indication parameter, a second QUIC version information, a security parameter, or a transport parameter.

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

[0157] In one possible implementation, in the QUIC function parameters, the QUIC second connection identifier and the QUIC omitted connection identifier indication parameter may not be carried at the same time. When the QUIC second connection identifier is carried in the QUIC function parameters, the connection identifier can be used for subsequent establishment of a QUIC connection. When the QUIC omitted connection identifier indication parameter is carried in the QUIC function parameters, the connection identifier may not be used for subsequent establishment of a QUIC connection.

[0158] In one possible implementation, the QUIC function parameters may carry one or more of a QUIC omitted connection identifier indication parameter, a QUIC function IP address, a QUIC function port number, a second QUIC version information, a security parameter, or a transmission parameter, or it can be understood that the QUIC omitted connection identifier indication parameter and the QUIC function IP address, the QUIC function port number, the second QUIC version information, the security parameter, or the transmission parameter may be carried in the QUIC function parameters at the same time.

[0159] The MP-QUIC function parameters may include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, second MP-QUIC version information, security parameters or transmission parameters.

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

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

[0162] The MP-QUIC second 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 above-mentioned MP-QUIC first connection identifier assigned by the terminal device to jointly identify an MP-QUIC connection, or identify an MP-QUIC connection based on the above-mentioned second connection identifier. 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 to encapsulate service data packets, for example, use the MP-QUIC protocol header to encapsulate service data packets, and carry the MP-QUIC first connection identifier, or the MP-QUIC second connection identifier, or carry both the MP-QUIC first connection identifier and the MP-QUIC second connection identifier in the above-mentioned MP-QUIC protocol header.

[0163] The second MP-QUIC version information is the MP-QUIC version used for the MP-QUIC connection. The second MP-QUIC version information may be the MP-QUIC version information supported by the SMF network element or the UPF network element, or the MP-QUIC version information determined by the SMF network element or the UPF network element according to the version information supported by the terminal device, such as selecting any version information also supported by the network side from the version information supported by the terminal device as the second MP-QUIC version information. Exemplarily, the second MP-QUIC version information may be any one of the first MP-QUIC version information.

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

[0165] The transmission parameters can be used to control the transmission process of the MP-QUIC connection. The transmission parameters can be, for example, original_connection_id, max_idle_timeout, initial_max_data, initial_max_stream_data_bidi_local, initial_max_stream_data_bidi_remote, initial_max_stream_data_uni, initial_max_streams_bidi, initial_max_streams_uni, ack_delay_exponent, max_ack_delay, disable_active_migration, preferred_address, active_connection_id_limit, 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.

[0166] In one possible implementation, the MP-QUIC function parameters include one or more of the following: an MP-QUIC function IP address, an MP-QUIC function port number, an MP-QUIC omitted connection identifier indication parameter, second MP-QUIC version information, security parameters, or transport parameters.

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

[0168] In one possible implementation, in the MP-QUIC function parameters, the MP-QUIC second connection identifier and the MP-QUIC omitted connection identifier indication parameter may not be carried at the same time. When the MP-QUIC second connection identifier is carried in the MP-QUIC function parameters, the connection identifier may be used for subsequent establishment of the MP-QUIC connection. When the MP-QUIC omitted connection identifier indication parameter is carried in the MP-QUIC function parameters, the connection identifier may not be used for subsequent establishment of the MP-QUIC connection.

[0169] In a possible implementation, the MP-QUIC function parameters may carry one or more of the MP-QUIC omitted connection identifier indication parameter, the MP-QUIC function IP address, the MP-QUIC function port number, the second MP-QUIC version information, the security parameters or the transmission parameters, or it can be understood that the MP-QUIC omitted connection identifier indication parameter and the MP-QUIC function IP address, the MP-QUIC function port number, the second MP-QUIC version information, the security parameters or the transmission parameters may be carried in the MP-QUIC function parameters at the same time. In a possible implementation, the MP-QUIC function parameters may also include one or more of the following: a sub-connection identifier or an access technology indication parameter or a tunnel identifier; wherein the sub-connection identifier is the connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter.

[0170] The access technology indication parameter can indicate the access technology corresponding to the sub-connection in the MP-QUIC connection. For example, the access technology can be 3GPP access technology, non3GPP access technology, or 4G cellular access technology, 5G cellular access technology, trusted or untrusted wifi access technology, fixed network or wired access technology, etc. It should be noted that in specific applications, if on the UPF network element side, it includes a sub-connection identifier and a technical access indication, or a sub-connection identifier and a corresponding tunnel identifier. If on the terminal device side, it includes a sub-connection identifier and a technical access indication. The access technology indication parameter or tunnel identifier can be characters, numbers, etc.

[0171] The sub-connection identifier is the connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter. For example, the sub-connection identifier can be, for example, a UPF network element or an SMF network element assigns a connection identifier a to a sub-connection of an MP-QUIC accessed by 3GPP, or a UPF network element or an SMF network element assigns a connection identifier b to a sub-connection of an MP-QUIC accessed by non3GPP. If the terminal device subsequently uses an MP-QUIC header to encapsulate a service data packet, the MP-QUIC header may contain a sub-connection identifier. For example, when a 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. In specific applications, the sub-connection identifier can be characters, numbers, etc.

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

[0173] Figure 4 A flow chart of a communication method provided in an embodiment of the present application is provided. Figure 4 The corresponding embodiment is a flow chart of establishing a QUIC connection between a terminal device and a UPF network element, including the following steps:

[0174] S401: The terminal device sends a message to the session management function SMF network element for requesting to establish or update a PDU session, as well as indication information indicating that the terminal device supports QUIC capabilities.

[0175] In a specific implementation, the message requesting to establish or update a PDU session may be the first message mentioned above.

[0176] In a possible implementation, the terminal device may encapsulate the first message in a NAS transmission message and send it to an AMF network element, and the AMF network element forwards the first message to the SMF network element.

[0177] In one possible implementation, the terminal device may send a NAS transmission message to the AMF network element through the RAN, which includes a message requesting the establishment or update of a PDU session. The message requesting the establishment or update of the PDU session carries indication information for indicating that the terminal device supports QUIC capabilities. The AMF network element further forwards the message requesting the establishment or update of the PDU session to the SMF network element.

[0178] In one possible implementation, the terminal device sends a NAS transport message to the AMF network element, which includes an indication that the terminal device supports QUIC 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 QUIC capability indication to the SMF network element.

[0179] 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 QUIC capabilities. The AMF network element selects an SMF network element that supports the QUIC function based on the indication information of the QUIC capability, and further forwards the message requesting the establishment of the PDU session and the indication information that the terminal device supports QUIC capabilities to the SMF network element.

[0180] The SMF network element can receive a first message from a terminal device, or a first message and indication information that the terminal device supports QUIC capabilities.

[0181] S402: The SMF network element determines that the service flow in the PDU session is transmitted using the QUIC method.

[0182] In one possible implementation, the SMF network element may determine that the service flow using UDP in the PDU session is transmitted using the QUIC method.

[0183] Exemplarily, S402 may include: S4021, the SMF network element sends a policy request (policyrequest) to the PCF network element, and the policy request may include indication information for indicating that the terminal device supports QUIC capabilities. S4022, the PCF network element determines that the service flow in the PDU session is transmitted by the QUIC method (also referred to as the QUIC policy). For example, the PCF network element may determine that the service flow in the PDU session is transmitted by the QUIC method when the service flow in the PDU session is a UDF service flow. S4023, the PCF network element sends an indication to the SMF network element that the service flow in the PDU session is transmitted by the QUIC method (also referred to as the QUIC policy indication).

[0184] In an embodiment of the present application, the SMF network element can determine that the service flow in the PDU session is transmitted using the QUIC method based on the policy indication of the PCF network element.

[0185] In one possible implementation, the PCF network element may also send a service flow identifier and / or an application identifier to the SMF network element, indicating that the service flow corresponding to the service flow identifier or the application identifier is transmitted using the QUIC method, that is, the QUIC protocol is used for flow aggregation. It can be understood that if the PCF network element does not send a service flow identifier or an application identifier to the SMF network element, all service flows in the PDU session may be transmitted using the QUIC method, or the service flows transmitted using the QUIC method in the PDU session may be determined based on other policies (such as local configuration policies), etc., and the embodiments of the present application do not specifically limit this.

[0186] S403: The SMF network element sends QUIC method indication information to the UPF network element.

[0187] In an embodiment of the present application, the SMF network element may send QUIC method indication information to the UPF network element. The UPF network element may allocate QUIC function parameters to the terminal device based on the QUIC method indication information, and establish a QUIC connection based on the QUIC function parameters.

[0188] In one possible implementation, the SMF network element may also send a service flow identifier to the UPF network element, and then establish a QUIC connection for the service flow corresponding to the service flow identifier based on the QUIC functional parameters.

[0189] In one possible implementation, if the SMF network element receives a QUIC first connection identifier or a QUIC omitted connection identifier indication parameter, a QUIC capability indication parameter, or a first QUIC version information from a terminal device, the SMF network element may also send this information to the UPF network element so that the UPF network element can configure the QUIC function parameters based on this information.

[0190] S404: The UPF network element sends QUIC function parameters to the SMF network element.

[0191] In an embodiment of the present application, the UPF network element can send an N4 reply message to the SMF network element, and the N4 reply message carries QUIC function parameters.

[0192] In one possible implementation, the UPF network element can send QUIC function parameters to the SMF network element through QUIC container parameters.

[0193] In one possible implementation, if the UPF network element cannot support the QUIC version supported by the terminal device, the terminal device and the UPF network element may not be able to establish a QUIC connection. The UPF network element may send a version unsupported indication to the SMF network element, and the SMF network element may not send a QUIC method indication to the terminal device, thereby terminating the establishment of the QUIC connection.

[0194] S405: The SMF network element sends a second message to the terminal device, where the second message is a message indicating that the PDU session is established or updated successfully.

[0195] As described above for the second message, the second message may include at least one of a service flow identifier, an application identifier, a QUIC functional parameter, or a QUIC method indication.

[0196] In one possible implementation, the SMF network element can send the QUIC function parameters to the terminal device through the QUIC container parameters. The QUIC function parameters can also be sent to the terminal device in any other way. The terminal device receives the QUIC function parameters from the SMF network element and can establish a QUIC connection based on the QUIC parameters. Then, data can be transmitted with the UPF network element based on the QUIC connection.

[0197] In another possible implementation, the SMF network element can send at least one of a service flow identifier, an application identifier, or a QUIC method indication to the terminal device, and the terminal device can further send a QUIC message to the UPF network element to obtain the parameters required to establish a QUIC connection from the UPF network element, and then establish a QUIC connection with the UPF network element.

[0198] S406: The terminal device and the UPF network element perform data transmission based on the established QUIC connection.

[0199] In an embodiment of the present application, in the uplink, when the terminal device sends a service flow data packet transmitted using a QUIC connection to a UPF network element, a QUIC packet header can be encapsulated for the service flow data packet, and the QUIC packet header can carry one or more of the QUIC functional parameters.

[0200] For example, a QUIC first connection identifier or a QUIC second connection identifier may be carried in a QUIC header. The destination IP address or port number in the QUIC header may be set to the IP address or port number of the QUIC function. The service flow data packet may be securely encrypted based on the security parameters. If a QUIC connection in which the QUIC connection identifier indication parameter is omitted is used, the QUIC connection identifier is not carried in the QUIC header.

[0201] In the downlink, when the UPF network element sends a service flow data packet transmitted using a QUIC connection to a terminal device, it can encapsulate the service flow data packet in a QUIC header, and the QUIC header can carry one or more QUIC functional parameters.

[0202] In a possible implementation, the encapsulated service flow data packet can be placed on the 3GPP side or the non-3GPP side based on other policy decisions, which is not specifically limited in the embodiments of the present application.

[0203] To sum up, in the embodiments of the present application, the network side can control the establishment of a QUIC connection between the terminal device and the UPF network element, so that the flow granularity can be realized based on the QUIC connection as the UDP service flow, thereby improving the service transmission bandwidth.

[0204] Figure 5 A flow chart of a communication method provided in an embodiment of the present application is provided. Figure 5 The corresponding embodiment is a flow chart of establishing a QUIC connection between a terminal device and a UPF network element, including the following steps:

[0205] S501: The terminal device sends a message to the session management function SMF network element for requesting to establish or update a PDU session, as well as indication information indicating that the terminal device supports QUIC capabilities.

[0206] S502: The SMF network element determines that the service flow in the PDU session is transmitted using the QUIC method.

[0207] In one possible implementation, S502 may include: S5021, the SMF network element sends a policy request to the PCF network element, and the policy request may include indication information for indicating that the terminal device supports QUIC capabilities. S5022, the PCF network element determines that the service flow in the PDU session is transmitted using the QUIC method (also referred to as the QUIC policy). S5023, the PCF network element sends an indication to the SMF network element that the service flow in the PDU session is transmitted using the QUIC method (also referred to as the QUIC policy indication).

[0208] S503: The SMF network element sends QUIC function parameters to the UPF network element.

[0209] S504: The UPF network element sends an N4 session reply message to the SMF network element.

[0210] S505: The SMF network element sends a second message to the terminal device, where the second message is a message indicating that the PDU session is established or updated successfully.

[0211] S506: The terminal device and the UPF network element perform data transmission based on the established QUIC connection.

[0212] In the embodiment of the present application, S501, S502, S505 and S506 can refer to Figure 4 S401, S402, S405 and S406 in the corresponding embodiments are not described in detail here.

[0213] and Figure 4 The difference of the embodiment is that Figure 4The QUIC parameters of the corresponding embodiment are configured by the UPF network element, and the QUIC parameters of the embodiment of the present application are configured by the SMF network element.

[0214] In S503, the SMF network element sends the QUIC function parameters to the UPF network element. In one possible implementation, if the SMF network element receives the QUIC first connection identifier sent by the terminal device, the SMF network element can send the QUIC first connection identifier to the UPF network element. If the SMF network element receives the QUIC omitted connection identifier indication parameter sent by the terminal device, the SMF network element can send the QUIC omitted connection identifier indication parameter to the UPF network element.

[0215] The UPF network element can establish a QUIC connection for the service flow based on the QUIC parameters configured by the SMF network element.

[0216] For example, the UPF network element can store the QUIC second connection identifier, QUIC first connection identifier, security parameters, or transmission parameters sent by the SMF network element. If the UPF network element receives a QUIC omitted connection identifier indication parameter, the UPF does not carry the connection identifier in the QUIC header when encapsulating the user downlink data packet using the QUIC protocol header. Otherwise, the UPF network element can carry at least one of the second connection identifier or the first connection identifier in the QUIC header. The UPF network element can encrypt the data transmitted in the QUIC connection based on the received security parameters. The UPF network element can control the QUIC connection based on the transmission parameters.

[0217] In S504, the UPF network element can send an N4 session reply message to the SMF network element, indicating that the N4 session is established successfully.

[0218] To sum up, in the embodiments of the present application, the network side can control the establishment of a QUIC connection between the terminal device and the UPF network element, so that the flow granularity can be realized based on the QUIC connection as the UDP service flow, thereby improving the service transmission bandwidth.

[0219] Figure 6 A flow chart of a communication method provided in an embodiment of the present application is provided. Figure 6 The corresponding embodiment is a flow chart of establishing an MP-QUIC connection between a terminal device and a UPF network element, including the following steps:

[0220] S601: The terminal device sends a message to the session management function SMF network element for requesting to establish or update a PDU session, and includes indication information for indicating that the terminal device supports MP-QUIC capabilities.

[0221] In a specific implementation, the message requesting to establish or update a PDU session may be the first message mentioned above.

[0222] In a possible implementation, the terminal device may encapsulate the first message in a NAS transmission message and send it to an AMF network element, and the AMF network element forwards the first message to the SMF network element.

[0223] In one possible implementation, the terminal device may send a NAS transmission message to the AMF network element through the RAN, which includes a message requesting the establishment or update of a PDU session. The message requesting the establishment or update of the PDU session carries indication information for indicating that the terminal device supports the MP-QUIC capability. The AMF network element further forwards the message requesting the establishment or update of the PDU session to the SMF network element.

[0224] In one possible implementation, the terminal device sends a NAS transport message to the AMF network element, where the NAS transport message includes an indication that the terminal device supports MP-QUIC capabilities, as well as 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, as well as the MP-QUIC capability indication to the SMF network element.

[0225] 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 MP-QUIC capabilities. The AMF network element selects an SMF network element that supports the MP-QUIC function based on the indication information of the MP-QUIC capability, and further forwards the message requesting the establishment of the PDU session and the indication information that the terminal device supports the MP-QUIC capability to the SMF network element.

[0226] 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 MP-QUIC capabilities.

[0227] S602: The SMF network element determines that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0228] In one possible implementation, the SMF network element may determine that the service flow using UDP in the PDU session is transmitted using the MP-QUIC method.

[0229] Exemplarily, S602 may include: S6021, the SMF network element sends a policy request (policyrequest) to the PCF network element, and the policy request may include indication information for indicating that the terminal device supports MP-QUIC capabilities. S6022, the PCF network element determines that the service flow in the PDU session is transmitted by the MP-QUIC method (also referred to as the MP-QUIC policy). For example, the PCF network element may determine that the service flow in the PDU session is transmitted by the MP-QUIC method when the service flow in the PDU session is a UDF service flow. S6023, the PCF network element sends an indication to the SMF network element that the service flow in the PDU session is transmitted by the MP-QUIC method (also referred to as the MP-QUIC policy indication).

[0230] In an embodiment of the present application, the SMF network element can determine that the service flow in the PDU session is transmitted using the MP-QUIC method based on the policy indication of the PCF network element.

[0231] In one possible implementation, the PCF network element may also send a service flow identifier and / or an application identifier to the SMF network element, indicating that the service flow corresponding to the service flow identifier or the application identifier is transmitted using the MP-QUIC method, that is, the MP-QUIC protocol is used for flow aggregation. It can be understood that if the PCF network element does not send a service flow identifier or an application identifier to the SMF network element, all service flows in the PDU session may be transmitted using the MP-QUIC method, or the service flows transmitted using the MP-QUIC method in the PDU session may be determined based on other policies (such as local configuration policies), etc., and the embodiments of the present application do not specifically limit this.

[0232] S603: The SMF network element sends MP-QUIC method indication information to the UPF network element.

[0233] In an embodiment of the present application, the SMF network element may send MP-QUIC method indication information to the UPF network element. The UPF network element may allocate MP-QUIC function parameters to the terminal device based on the MP-QUIC method indication information, and establish an MP-QUIC connection based on the MP-QUIC function parameters.

[0234] In one possible implementation, the SMF network element may also send a service flow identifier to the UPF network element, and then establish an MP-QUIC connection for the service flow corresponding to the service flow identifier based on the MP-QUIC functional parameters.

[0235] In one possible implementation, if the SMF network element receives the MP-QUIC first connection identifier or the MP-QUIC omitted connection identifier indication parameter, the MP-QUIC capability indication parameter, or the first MP-QUIC version information from the terminal device, the SMF network element may also send this information to the UPF network element so that the UPF network element can configure the MP-QUIC functional parameters based on this information.

[0236] S604: The UPF network element sends MP-QUIC function parameters to the SMF network element.

[0237] In an embodiment of the present application, the UPF network element may send an N4 reply message to the SMF network element, and the N4 reply message carries the MP-QUIC function parameters. Alternatively, the UPF network element may send the MP-QUIC function parameters to the SMF network element through the MP-QUIC container parameters.

[0238] In one possible implementation, if the UPF network element cannot support the MP-QUIC version supported by the terminal device, the terminal device and the UPF network element cannot establish an MP-QUIC connection. The UPF network element may send a version unsupported indication to the SMF network element, and the SMF network element may not send an MP-QUIC method indication to the terminal device, thereby terminating the establishment of the MP-QUIC connection.

[0239] S605: The SMF network element sends a second message to the terminal device, where the second message includes a message indicating that the PDU session is established or updated successfully.

[0240] In one possible implementation, as described above for the second message, the second message may include at least one of a service flow identifier, an application identifier, an MP-QUIC functional parameter, or an MP-QUIC method indication.

[0241] In one possible implementation, the SMF network element can send the MP-QUIC function parameters to the terminal device through the MP-QUIC container parameters. The MP-QUIC function parameters can also be sent to the terminal device in any other way. The terminal device receives the MP-QUIC function parameters from the SMF network element and can establish an MP-QUIC connection based on the MP-QUIC parameters. Then, data can be transmitted with the UPF network element based on the MP-QUIC connection.

[0242] In another possible implementation, the SMF network element may send at least one of a service flow identifier, an application identifier, or an MP-QUIC method indication to the terminal device, and the terminal device may further send an MP-QUIC message to the UPF network element to obtain the parameters required to establish an MP-QUIC connection from the UPF network element, and then establish an MP-QUIC connection with the UPF network element.

[0243] S606: The terminal device and the UPF network element perform data transmission based on the established MP-QUIC connection.

[0244] In an embodiment of the present application, in the uplink, when the terminal device sends a service flow data packet transmitted using an MP-QUIC connection to a UPF network element, it can perform MP-QUIC packet header encapsulation for the service flow data packet, and the MP-QUIC packet header can carry one or more of the MP-QUIC functional parameters.

[0245] For example, the MP-QUIC first connection identifier or the MP-QUIC second connection identifier may be carried in the MP-QUIC header. The destination IP address or port number in the MP-QUIC header may be set to the IP address or port number of the MP-QUIC function. The service flow data packet may be securely encrypted based on the 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.

[0246] In the downlink, when the UPF network element sends a service flow data packet transmitted using an MP-QUIC connection to a terminal device, it can encapsulate the service flow data packet in an MP-QUIC header, and the MP-QUIC header can carry one or more of the MP-QUIC functional parameters.

[0247] In a possible implementation, the encapsulated service flow data packet can be placed on the 3GPP side or the non-3GPP side based on other policy decisions, which is not specifically limited in the embodiments of the present application.

[0248] In one possible implementation, unlike a QUIC connection, in an MP-QUIC connection, the UPF network element allocates a connection identifier for a sub-connection of the MP-QUIC. The MP-QUIC functional parameters may include one or more of a sub-connection identifier, access technology knowledge information, or a tunnel identifier.

[0249] For example, the UPF network element assigns connection identifier a to the MP-QUIC sub-connection accessed by 3GPP, or the UPF network element assigns connection identifier b to the MP-QUIC sub-connection accessed by non3GPP. 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.

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

[0251] To sum up, in the embodiments of the present application, the network side can control the establishment of an MP-QUIC connection between the terminal device and the UPF network element, so that the flow granularity can be realized based on the MP-QUIC connection for the UDP service flow, thereby improving the service transmission bandwidth.

[0252] Figure 7 A flow chart of a communication method provided in an embodiment of the present application is provided. Figure 7 The corresponding embodiment is a flow chart of establishing an MP-QUIC connection between a terminal device and a UPF network element, including the following steps:

[0253] S701: The terminal device sends a message to the session management function SMF network element to request the establishment or update of a PDU session, as well as indication information indicating that the terminal device supports MP-QUIC capabilities.

[0254] S702: The SMF network element determines that the service flow in the PDU session is transmitted using the MP-QUIC method.

[0255] In one possible implementation, S702 may include: S7021, the SMF network element sends a policy request to the PCF network element, and the policy request may include indication information for indicating that the terminal device supports MP-QUIC capabilities. S7022, the PCF network element determines that the service flow in the PDU session is transmitted using the MP-QUIC method (also referred to as the MP-QUIC policy). S7023, the PCF network element sends an indication to the SMF network element that the service flow in the PDU session is transmitted using the MP-QUIC method (also referred to as the MP-QUIC policy indication).

[0256] S703: The SMF network element sends MP-QUIC function parameters to the UPF network element.

[0257] S704: The UPF network element sends an N4 session reply message to the SMF network element.

[0258] S705: The SMF network element sends a second message to the terminal device, where the second message includes a message indicating that the PDU session is established or updated successfully.

[0259] S706: The terminal device and the UPF network element perform data transmission based on the established MP-QUIC connection.

[0260] In the embodiment of the present application, S701, S702, S705 and S706 can refer to Figure 6 S601, S602, S605 and S606 in the corresponding embodiments are not described in detail here.

[0261] and Figure 6 The difference of the embodiment is that Figure 6 The MP-QUIC parameters of the corresponding embodiment are configured by the UPF network element, and the MP-QUIC parameters of the embodiment of the present application are configured by the SMF network element.

[0262] In S703, the SMF network element sends the MP-QUIC function parameters to the UPF network element. In one possible implementation, if the SMF network element receives the MP-QUIC first connection identifier sent by the terminal device, the SMF network element may send the MP-QUIC first connection identifier to the UPF network element. If the SMF network element receives the MP-QUIC omitted connection identifier indication parameter sent by the terminal device, the SMF network element may send the MP-QUIC omitted connection identifier indication parameter to the UPF network element.

[0263] The UPF network element can establish an MP-QUIC connection for the service flow based on the MP-QUIC parameters configured by the SMF network element.

[0264] In S706, the UPF network element can send an N4 session reply message to the SMF network element, indicating that the N4 session is established successfully.

[0265] To sum up, in the embodiments of the present application, the network side can control the establishment of an MP-QUIC connection between the terminal device and the UPF network element, so that the flow granularity can be realized based on the MP-QUIC connection for the UDP service flow, thereby improving the service transmission bandwidth.

[0266] Combined with the above Figures 4 to 7 , 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.

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

[0268] like Figure 8 As shown, Figure 8The 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.

[0269] 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. Alternatively, the communication unit 102 is used to support the communication device to execute S501, S503, S504 and S505 in the above embodiment. The processing unit 101 is used to support the communication device to execute S502 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute S601, S603, S604 and S605 in the above embodiment. The processing unit 101 is used to support the communication device to execute S602 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute S701, S703, S704 and S705 in the above embodiment. The processing unit 101 is used to support the communication device to execute S702 in the above embodiment.

[0270] In a possible embodiment, the communication unit 102 is further used to support the communication device to execute S4021 and S40213 in the above embodiment. Alternatively, the communication unit 102 is further used to support the communication device to execute S5021 and S50213 in the above embodiment. Alternatively, the communication unit 102 is further used to support the communication device to execute S6021 and S60213 in the above embodiment. Alternatively, the communication unit 102 is further used to support the communication device to execute S7021 and S70213 in the above embodiment.

[0271] In another example, taking the communication device as a UPF network element or a chip or chip system applied in a UPF network element as an example, the communication unit 102 is used to support the communication device to execute steps S403 and S404 in the above embodiment. The processing unit 101 is used to support the communication device to execute S406 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute steps S503 and S504 in the above embodiment. The processing unit 101 is used to support the communication device to execute S506 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute steps S603 and S604 in the above embodiment. The processing unit 101 is used to support the communication device to execute S606 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute steps S703 and S704 in the above embodiment. The processing unit 101 is used to support the communication device to execute S706 in the above embodiment.

[0272] 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. Alternatively, the communication unit 102 is used to support the communication device to execute S501 and S505 in the above embodiment. The processing unit 101 is used to support the communication device to execute S506 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute S601 and S605 in the above embodiment. The processing unit 101 is used to support the communication device to execute S606 in the above embodiment. Alternatively, the communication unit 102 is used to support the communication device to execute S701 and S705 in the above embodiment. The processing unit 101 is used to support the communication device to execute S706 in the above embodiment.

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

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

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

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

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

[0278] The embodiment of the present application provides a communication device, which includes one or more modules for implementing the method in S401-S406, or S501-S506, or S601-S606, or S701-S706, and the one or more modules may correspond to the steps of the method in S401-S406, or S501-S506, or S601-S606, or S701-S706. 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 for controlling or processing the action of the communication device can be called a processing module. A module for performing steps of processing messages or data on the communication device side can be called a communication module.

[0279] Fig. 9 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. Fig. 9 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 ( Fig. 9 The communication interface 43 is used as an example for explanation).

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

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

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

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

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

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

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

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

[0288] In a specific implementation, as an embodiment, the communication device may include multiple processors, such as Fig. 941 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).

[0289] 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, or S501, S503, S504 and S505, or S601, S603, S604 and S605, or S701, S703, S704 and S705 in the above embodiments. The processor 41 or the processor 45 is used to support the communication device to execute S402, or S502, or S602, or S702 in the above embodiments.

[0290] In another example, taking the case where the communication device may be a UPF network element or a chip or chip system applied in a UPF network element as an example, the communication interface is used to support the communication device to execute S403 and S404, or S503 and S504, or S603 and S604, or S703 and S704 in the above embodiment. The processor 41 or the processor 45 is used to support the communication device to execute step S406 or S506 or S606 or S706 in the above embodiment.

[0291] like Fig.10 , 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.

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

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

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

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

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

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

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

[0299] Specifically, at least one processor 1211 is used to execute S406 or S506 or S606 or S706. At least one transceiver 1212 is used to execute S401 and S405, or S501 and S505, or S601 and S605, or S701 and S705.

[0300] Fig.11 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 .

[0301] In a possible embodiment, Fig.11 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).

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

[0303] 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).

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

[0305] 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 Fig.11 Various buses are labeled as bus system 1520.

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

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

[0308] In one possible implementation, the communication interface 1530 is used to execute Figure 4-Figure 7 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-Figure 7 The processing steps of the SMF network element, UPF network element or terminal equipment in the illustrated embodiment.

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

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

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

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

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

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

[0315] 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, and the first message includes first indication information, where the first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability; The SMF network element determines that the service flow using UDP in the PDU session is transmitted using the QUIC method or the MP-QUIC method; 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, the second message includes second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted by the QUIC method, or to indicate that the service flow in the PDU session is transmitted by the MP-QUIC method The indication information for indicating that the terminal device supports QUIC capability includes one or more of the following: a QUIC omitted connection identifier indication parameter, a QUIC first connection identifier, a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information; wherein the QUIC first connection identifier is a connection identifier assigned by the terminal device to the QUIC connection; or, The indication information used to indicate that the terminal device supports MP-QUIC capability includes one or more of the following: an MP-QUIC omitted connection identifier indication parameter, an MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter or a first MP-QUIC version information; wherein the MP-QUIC first connection identifier is a connection identifier assigned by the terminal device to the MP-QUIC connection.

2. The method according to claim 1, characterized in that: The second indication information includes a QUIC functional parameter or an MP-QUIC functional parameter, and the method further includes: The SMF network element obtains the QUIC functional parameters or the MP-QUIC functional parameters.

3. The method according to claim 2, characterized in that The SMF network element obtaining the QUIC functional parameter or the MP-QUIC functional parameter includes: The SMF network element sends indication information for indicating that the service flow in the PDU session is transmitted by the QUIC method, or indication information for indicating that the service flow in the PDU session is transmitted by the MP-QUIC method to the user plane function UPF network element; The SMF network element receives the QUIC functional parameters or the MP-QUIC functional parameters from the UPF network element.

4. The method according to claim 2, characterized in that: The SMF network element obtains the QUIC function parameter or the MP-QUIC function parameter including: The SMF network element allocates the QUIC functional parameters or the MP-QUIC functional parameters; The method further comprises: The SMF network element sends the QUIC functional parameters or the MP-QUIC functional parameters to the UPF network element.

5. The method according to any one of claims 2 to 4, characterized in that: The QUIC function parameters include one or more of the following: a QUIC function IP address, a QUIC function port number, a QUIC second connection identifier, a QUIC omitted connection identifier indication parameter, a second QUIC version information, a security parameter, or a transmission parameter; or, The MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC omitted connection identifier indication, second MP-QUIC version information, security parameters or transmission parameters.

6. The method according to claim 5, characterized in that The MP-QUIC functional parameters also include one or more of the following: a sub-connection identifier or an access technology indication parameter or tunnel identification information; wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter or tunnel identification information.

7. The method according to any one of claims 1 to 4 and 6, characterized in that: The SMF network element determines that the service flow in the PDU session is transmitted using the QUIC method or the MP-QUIC method, including: The SMF network element receives QUIC method indication information or MP-QUIC method indication information from the policy control function PCF network element; the QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted by the QUIC method; the MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted by the MP-QUIC method.

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 a protocol data unit to establish or update a protocol data unit PDU session, and the first message includes first indication information, where the first indication information is indication information used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or indication information used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability; 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 second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted by the QUIC method, or to indicate that the service flow in the PDU session is transmitted by the MP-QUIC method; The indication information for indicating that the terminal device supports QUIC capability includes one or more of the following: a QUIC omitted connection identifier indication parameter, a QUIC first connection identifier, a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information; wherein the QUIC first connection identifier is a connection identifier assigned by the terminal device to the QUIC connection; or, The indication information used to indicate that the terminal device supports MP-QUIC capability includes one or more of the following: an MP-QUIC omitted connection identifier indication parameter, an MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter or a first MP-QUIC version information; wherein the MP-QUIC first connection identifier is a connection identifier assigned by the terminal device to the MP-QUIC connection.

9. The method according to claim 8, characterized in that The second indication information includes QUIC functional parameters or MPQUIC functional parameters; The QUIC function parameters include one or more of the following: a QUIC function IP address, a QUIC function port number, a QUIC second connection identifier, a QUIC omitted connection identifier indication parameter, a second QUIC version information, a security parameter, or a transmission parameter; or, The MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC omitted connection identifier indication, second MP-QUIC version information, security parameters or transmission parameters.

10. The method according to claim 9, characterized in that The MP-QUIC functional parameters also include one or more of the following: a sub-connection identifier or an access technology indication parameter; wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter.

11. The method according to any one of claims 8 to 10, characterized in that: Also includes: The terminal device establishes a QUIC connection or an MP-QUIC connection with a user plane function UPF network element based on the second message; The terminal device uses the QUIC connection or the MP-QUIC connection to transmit data.

12. The method according to claim 11, characterized in that The second message also includes a service flow identifier or an application identifier, and the terminal device uses the QUIC connection or the MP-QUIC connection to transmit data, including: The terminal device uses the QUIC connection or the MP-QUIC connection to transmit the service flow data packet corresponding to the service flow identifier or the application identifier.

13. The method according to claim 11, characterized in that The terminal device uses the QUIC connection or the MP-QUIC connection to transmit data, including: The terminal device performs QUIC header encapsulation or MP-QUIC header encapsulation on the data packet to be transmitted; wherein the QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters; The terminal device sends the encapsulated QUIC packet or the encapsulated MP-QUIC packet to the UPF network element.

14. A communication device, characterized in that: include: a processing unit and a communication unit; 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, and the first message includes first indication information, and the first indication information is used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or is used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability. The processing unit is used to determine whether the service flow using UDP in the PDU session is transmitted using the QUIC method or the MP-QUIC method; The communication unit is further used to send a second message to the terminal device, where the second message is used to indicate that the PDU session is successfully established or updated, and the second message includes second indication information, where the second indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method, or to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method; The indication information for indicating that the terminal device supports QUIC capability includes one or more of the following: a QUIC omitted connection identifier indication parameter, a QUIC first connection identifier, a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information; wherein the QUIC first connection identifier is a connection identifier assigned by the terminal device to the QUIC connection; or, The indication information used to indicate that the terminal device supports MP-QUIC capability includes one or more of the following: an MP-QUIC omitted connection identifier indication parameter, an MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter or a first MP-QUIC version information; wherein the MP-QUIC first connection identifier is a connection identifier assigned by the terminal device to the MP-QUIC connection.

15. The device according to claim 14, characterized in that The second indication information includes QUIC functional parameters or MP-QUIC functional parameters, and the communication unit is also used to obtain the QUIC functional parameters or the MP-QUIC functional parameters.

16. The device according to claim 15, characterized in that The communication unit is specifically used to send indication information to the user plane function UPF network element to indicate that the service flow in the PDU session is transmitted using the QUIC method, or to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method; and to receive the QUIC function parameters or the MP-QUIC function parameters from the UPF network element.

17. The device according to claim 15, characterized in that The processing unit is further used to allocate the QUIC functional parameters or the MP-QUIC functional parameters; The communication unit is also used to send the QUIC function parameters or the MP-QUIC function parameters to the UPF network element.

18. The device according to any one of claims 15 to 17, characterized in that: The QUIC function parameters include one or more of the following: a QUIC function IP address, a QUIC function port number, a QUIC second connection identifier, a QUIC omitted connection identifier indication parameter, a second QUIC version information, a security parameter, or a transmission parameter; or, The MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC omitted connection identifier indication, second MP-QUIC version information, security parameters or transmission parameters.

19. The device according to claim 18, characterized in that The MP-QUIC functional parameters also include one or more of the following: a sub-connection identifier or an access technology indication parameter or tunnel identification information; wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter or tunnel identification information.

20. The device according to any one of claims 14 to 17 and 19, characterized in that: The communication unit is also used to receive QUIC method indication information or MP-QUIC method indication information from a policy control function PCF network element; the QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the QUIC method; the MP-QUIC method indication information is used to indicate that the service flow in the PDU session is transmitted using the MP-QUIC method.

21. A communication device, characterized in that: include: Communication unit; 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 a protocol data unit to establish or update a protocol data unit PDU session, and the first message includes first indication information, and the first indication information is used to indicate that the terminal device supports the Internet transport layer protocol QUIC capability, or is used to indicate that the terminal device supports the multi-channel Internet transport protocol MP-QUIC capability. The communication unit is further 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 second indication information, and the second indication information is used to indicate that the service flow in the PDU session is transmitted by the QUIC method, or to indicate that the service flow in the PDU session is transmitted by the MP-QUIC method; The indication information for indicating that the terminal device supports QUIC capability includes one or more of the following: a QUIC omitted connection identifier indication parameter, a QUIC first connection identifier, a QUIC capability indication parameter, a QUIC request indication parameter, or a first QUIC version information; wherein the QUIC first connection identifier is a connection identifier assigned by the terminal device to the QUIC connection; or, The indication information used to indicate that the terminal device supports MP-QUIC capability includes one or more of the following: an MP-QUIC omitted connection identifier indication parameter, an MP-QUIC first connection identifier, an MP-QUIC capability indication parameter, an MP-QUIC request indication parameter or a first MP-QUIC version information; wherein the MP-QUIC first connection identifier is a connection identifier assigned by the terminal device to the MP-QUIC connection.

22. The device according to claim 21, characterized in that The second indication information includes QUIC functional parameters or MPQUIC functional parameters; The QUIC function parameters include one or more of the following: a QUIC function IP address, a QUIC function port number, a QUIC second connection identifier, a QUIC omitted connection identifier indication parameter, a second QUIC version information, a security parameter, or a transmission parameter; or, The MP-QUIC function parameters include one or more of the following: MP-QUIC function IP address, MP-QUIC function port number, MP-QUIC second connection identifier, MP-QUIC omitted connection identifier indication, second MP-QUIC version information, security parameters or transmission parameters.

23. The device according to claim 22, characterized in that The MP-QUIC functional parameters also include one or more of the following: a sub-connection identifier or an access technology indication parameter; wherein the sub-connection identifier is a connection identifier of the MP-QUIC sub-connection corresponding to the access technology indication parameter.

24. The device according to any one of claims 21 to 23, characterized in that Also includes a processing unit; The processing unit is used to establish a QUIC connection or an MP-QUIC connection with a user plane function UPF network element based on the second message; The processing unit is also used to use the QUIC connection or the MP-QUIC connection to transmit data.

25. The device according to claim 24, characterized in that The second message also includes a service flow identifier or an application identifier, and the processing unit is specifically used to transmit the service flow data packet corresponding to the service flow identifier or the application identifier using the QUIC connection or the MP-QUIC connection.

26. The device according to claim 24, characterized in that The processing unit is specifically configured to perform QUIC header encapsulation or MP-QUIC header encapsulation on the data packet to be transmitted; wherein the QUIC header contains at least one of the QUIC functional parameters, or the MP-QUIC header contains at least one of the MP-QUIC functional parameters; The communication unit is also used to send encapsulated QUIC packets or encapsulated MP-QUIC packets to the UPF network element.

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.

Citation Information

Patent Citations

  • Service flow transmission method, communication method and device

    CN110830429A

Cited By

  • Communication method and apparatus

    EP4633285A2

  • Communication method and apparatus

    WO2021174884A1