Communication method, communication apparatus, chip, computer-readable storage medium, and computer program product

By receiving and sending session establishment requests in the core network element, carrying specific functions to establish multi-access PDU sessions, the problem of traffic guidance and path selection between the UE and the UPF network element is solved, and effective communication in roaming scenarios is realized.

WO2026233104A1PCT designated stage Publication Date: 2026-11-12HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/091923
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-04-21
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In wireless communication systems, how to establish a Multiple Access Protocol Data Unit (PDU) session between a User Equipment (UE) and a User Plane Function (UPF) network element, especially when the UE supports the Multipath Fast User Datagram Protocol Internet Connection (MPQUIC-E) function, to achieve effective traffic steering and path selection.

Method used

The first core network element receives the session establishment request, carries the Multipath Fast User Datagram Protocol Internet Connection (MPQUIC-E) function and the lower layer (ATSSS lower layer) function, and sends the policy association establishment request, which only includes the lower layer function, to ensure that the MPQUIC-E function is not activated in roaming or evolved packet system (EPS) scenarios, thereby establishing a multi-access PDU session.

Benefits of technology

It enables the effective establishment of multiple access PDU sessions in roaming scenarios, avoids unnecessary function activation, simplifies the network architecture, and reduces the need for enhancements to other network elements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026091923_12112026_PF_FP_ABST
    Figure CN2026091923_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present application provides a communication method, a communication apparatus, a chip, a computer-readable storage medium, and a computer program product. The method comprises: a first core network element receiving a first session establishment request, wherein the first session establishment request comprises an ATSSS capability, the ATSSS capability comprises a multipath quick UDP Internet connections (MPQUIC)-E functionality and an ATSSS low layer functionality, and a PDU session type is Ethernet; and sending a policy association establishment request, wherein the policy association establishment request comprises a second ATSSS capability, and the second ATSSS capability is an ATSSS low layer functionality. When a UE associated with the first session establishment request is in a roaming or EPS scenario, the MPQUIC-E functionality may not be activated (enabled), and an MA PDU session is then established.
Need to check novelty before this filing date? Find Prior Art

Description

Communication methods, communication devices, chips, computer-readable storage media, and computer program products

[0001] This application claims priority to Chinese Patent Application No. 202510595259.3, filed with the State Intellectual Property Office of China on May 8, 2025, entitled “Communication Method, Communication Device, Chip, Computer-readable Storage Medium and Computer Program Product”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and in particular to communication methods, communication devices, chips, computer-readable storage media, and computer program products. Background Technology

[0003] In wireless communication systems, such as new radio (NR) systems, user equipment (UE) establishes a protocol data unit (PDU) session with the data network (DN) through user plane function (UPF) network elements. The PDU session provides data transmission services between the terminal equipment and the DN.

[0004] Currently, multiple access (MA) PDU sessions (also known as multiple PDU sessions) can be established between the UE and the UPF network element. For example, the UE and the UPF network element can establish an MA PDU session based on access technology 1 and access technology 2. Then, the UE's service flow can be transmitted to the UPF network element through access technology 1 and / or access technology 2. A MA PDU session is in contrast 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, while a multiple access PDU session refers to a PDU session that accesses the UPF network element through multiple access technologies (at least two).

[0005] The traffic offloading functions of an MA PDU session include: Multipath Transmission Control Protocol (MPTCP) function, Multipath Quick UDP Internet Connections (MPQUIC)-Ethernet(E) function, and Access Traffic Steering, Switching, Splitting (ATSSS) Low Layer (ATSSS-LL) function. MPTCP function is for multiplexing Transmission Control Protocol (TCP) traffic. MPQUIC-E function is a QUIC-based steering function that allows the transport of Ethernet frames over multiple access between the UE and UPF. The UE's ATSSS-LL function can be used to steer, switch, and split all types of traffic, including TCP traffic, UDP traffic, Ethernet traffic, etc. The ATSSS-LL function can be used by terminal equipment or UPF network elements to select transmission paths for data packets based on traffic splitting modes and link states, supporting multiplexing of TCP and UDP services.

[0006] When the UE or DN supports the MPQUIC-E function, how to establish a MAPDU session is an urgent problem to be solved. Summary of the Invention

[0007] This application discloses a communication method, communication device, chip, computer-readable storage medium, and computer program product; it can establish an MA PDU session when the UE or DN supports the MPQUIC-E function.

[0008] Firstly, embodiments of this application provide a communication method applied to a first core network element. This method can be implemented by the first core network element or a component on the first core network element side. The following description uses the implementation by the first core network element as an example. The method includes: the first core network element receiving a first session establishment request, the first session establishment request including a first access traffic steering, switching, splitting (ATSSS) capability and a protocol data unit (PDU) session type. The first ATSSS capability includes multipath quick UDP internet connections (MPQUIC)-E functionality and ATSSS low-layer functionality, and the PDU session type is Ethernet; sending a policy association establishment request, the policy association establishment request including a second ATSSS capability, the second ATSSS capability being an ATSSS low-layer function. In this application, an equivalent description of the second ATSSS capability as an ATSSS low-layer function is: the second ATSSS capability only includes ATSSS low-layer functionality. UDP is short for User Datagram Protocol. An equivalent description of a PDU session type as Ethernet is: PDU Session Type: Ethernet.

[0009] In this embodiment, when the first ATSSS capability carried in the first session establishment request includes MPQUIC-E functionality and ATSSS lower-layer functionality, the policy association establishment request includes a second ATSSS capability, which only includes ATSSS lower-layer functionality. This allows the establishment of an MA PDU session without activating (enabling) the MPQUIC-E function when the UE associated with the first session establishment request is in a roaming or evolved packet system (EPS) scenario. In this application, the UE associated with the first session establishment request can be the UE that triggered the first session establishment request. For example, the UE is the UE that sent a PDU session establishment request, which ultimately triggers the transmission of the aforementioned first session establishment request.

[0010] In one possible implementation, the first core network element is the session management function (SMF) element in the home public land mobile network (HPLMN) associated with the user equipment (UE) that established the first session request; receiving the first session establishment request includes: the first core network element receiving the first session establishment request from the SMF element in the visited public land mobile network (VPLMN) of the UE; thereby, it can be determined that the UE is in a roaming scenario.

[0011] In one possible implementation, sending a policy association establishment request includes: sending a policy association establishment request when the UE associated with the first session establishment request is in a roaming scenario; so as to establish an MA PDU session when the UE is in a roaming scenario.

[0012] In one possible implementation, the first session establishment request comes from the serving gateway, and the first core network element has the control plane functions of the SMF network element and the packet data network gateway (PGW) so that the UE can establish an MA PDU session in the EPS scenario.

[0013] Secondly, this application provides another communication method. This method is applied to a first core network element and can be implemented by the first core network element or a component on the first core network element side. The following description uses the implementation of the first core network element as an example. The method includes: the first core network element receiving a first session establishment request, the first session establishment request including a first ATSSS capability and a PDU session type, the first ATSSS capability including MPQUIC-E function and ATSSS low-level function, and the PDU session type being Ethernet; determining whether to enable the MPQUIC-E function for the MA PDU session associated with the first session establishment request based on whether the second core network element supports providing the PDU session type as IP in the N2 interface session management (SM) information; thus, if the second core network element does not support providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is not enabled for the PDU session, and if the second core network element supports providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is enabled for the PDU session, thereby successfully establishing the MA PDU session.

[0014] In one possible implementation, the method further includes: when the first core network element determines that the MPQUIC-E function is not enabled for the PDU session, it sends a policy association establishment request, the policy association establishment request including a second ATSSS capability, the second ATSSS capability being a low-level ATSSS function; this can enable the establishment of an MA PDU session when the second core network element does not support providing the PDU session type as IP in the N2 SM information without activating (enabling) the MPQUIC-E function.

[0015] In one possible implementation, the method further includes: when the first core network element determines that the MPQUIC-E function is enabled for the PDU session, it sends a first session establishment response to the second core network element, wherein the PDU session type carried in the first session establishment response is IP; thereby, it is possible to indicate to the access network device that the PDU session type is IP, and thus establish a MAPDU session.

[0016] In one possible implementation, the method further includes: the first core network element determining, through a network repository function (NRF) element, whether the second core network element supports providing PDU session type IP in the N2SM information; the NRF element can be reused, minimizing the impact on the network architecture. Furthermore, the second core network element does not need to carry a feature indication to the first core network element every time it establishes an MA PDU session (PDU session type Ethernet), which indicates that the second core network element supports providing PDU session type IP in the N2SM information.

[0017] In one possible implementation, the first core network element is the SMF network element in the HPLMN of the UE associated with the first session establishment request, and the second core network element is the SMF network element in the VPLMN of the UE; receiving the first session establishment request includes: receiving the first session establishment request from the second core network element; thereby, it can be determined that the UE is in a roaming scenario.

[0018] Thirdly, this application provides another communication method applied to a second core network element. This method can be implemented by the second core network element or a component on its side. The following description uses the implementation by the second core network element as an example. The method includes: the second core network element sending a first session establishment request, the first session establishment request including a first ATSSS capability and a PDU session type. The first ATSSS capability includes MPQUIC-E functionality and ATSSS lower-layer functionality, and the PDU session type is Ethernet; receiving a first session establishment response from the first core network element, the first session establishment response carrying a PDU session type of IPv4 or IPv6; thereby enabling the indication to the access network device that the PDU session type is IP, and thus establishing an MA PDU session.

[0019] In one possible implementation, the method further includes: when the PDU session type from the UE is Ethernet and the PDU session type from the first core network element is IP, the second core network element sends an N1N2 message transmission message (e.g., Namf_Communication_N1N2MessageTransfer), the N1N2 message transmission message including N2 SM information, where the PDU session type in the N2 SM information is IPv4 or IPv6; to indicate to the access network device that the PDU session type is IP. The N2 SM information needs to be sent to the access network device.

[0020] In one possible implementation, the N1N2 message transmission also includes an N1 SM container, in which the PDU session type is Ethernet. The N1 SM container needs to be sent to the UE.

[0021] In one possible implementation, IPv4 or IPv6 is received from the SMF network element in the HPLMN of the UE associated with the first session establishment request.

[0022] Fourthly, this application provides another communication method applied to a UE. This method can be implemented by the UE or its components, and the following description uses UE implementation as an example. The method includes: The UE generating a first attach request when a first condition is met. The first attach request includes a packet data network (PDN) type and ATSSS capability. The PDN type is non-IP, and the ATSSS capability includes MPQUIC-E functionality and ATSSS lower-layer functionality. The first condition includes the UE supporting MPQUIC-E functionality; sending the first attach request to the access network device; enabling MPQUIC-E functionality in EPS scenarios, thereby establishing an MA PDU session. Furthermore, this method enhances the UE's functionality without requiring enhancements to other network elements, making it simple to implement.

[0023] In one possible implementation, the first condition also includes: the UE is in an EPS scenario.

[0024] Fifthly, this application provides another communication method. This method is applied to a second core network element and can be implemented by the second core network element or a component on the second core network element side. The following description uses the implementation of the second core network element as an example. The method includes: the second core network element receiving a session context request from an access and mobility management function (AMF) element, the session context request including a first identifier; determining that the MA PDU session type corresponding to the first identifier is Ethernet; sending a session context response, the session context response including an SM context container, the SM context container including a PDU session type, the PDU session type being IPv4 or IPv6; thereby enabling the MPQUIC-E function when switching from a 5G roaming scenario to an EPS scenario, and thus establishing a MADU session.

[0025] In one possible implementation, the PDU session type is determined based on the PDU session type from the first core network element; or, the PDU session type is determined based on the transmission resource type from the first core network element, where the first core network element is the SMF element in the HPLMN of the UE associated with the session context request.

[0026] Sixthly, embodiments of this application provide another communication method. This method is applied to a first core network element and can be implemented by the first core network element or a component on the first core network element side. The following description uses the implementation by the first core network element as an example. The method includes: the first core network element receiving a first message; determining, based on the first message, that in the case of a UE switching from EPS to a roaming scenario, if the second core network element does not support providing the PDU session type as IP in the N2SM information, initiating the deactivation of the 3rd Generation Partnership Project (3GPP) side user plane connection process; and, in the scenario where the MAPDU session established through 3GPP access in the evolved packet core (EPC) enables MPQUIC-E, specifying network behavior for the EPS to roaming handover.

[0027] In one possible implementation, the method further includes: the first core network element determines whether the second core network element supports providing PDU session type as IP in N2SM information through the NRF network element; the NRF network element can be reused, and the impact on the network architecture is small.

[0028] In one possible implementation, the first core network element has the control plane functions of both the SMF network element and the PGW.

[0029] In a seventh aspect, embodiments of this application provide a communication device that has the function of implementing the behavior described in the first aspect method embodiment. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first session establishment request, the first session establishment request including a first ATSSS capability and a PDU session type, the first ATSSS capability including MPQUIC-E function and ATSSS low-level function, and the PDU session type being Ethernet; and to send a policy association establishment request, the policy association establishment request including a second ATSSS capability, the second ATSSS capability being an ATSSS low-level function. Optionally, the processing module is used to generate a policy association establishment request.

[0030] In one possible implementation, the first core network element is the SMF network element in the HPLMN of the UE associated with the first session establishment request; the transceiver module is specifically used to receive the first session establishment request from the SMF network element in the HPLMN of the UE.

[0031] For possible implementations of the communication method in the seventh aspect, please refer to the various possible implementations in the first aspect.

[0032] For the technical effects of the various possible implementations of the seventh aspect, please refer to the introduction of the technical effects of the first aspect or the various possible implementations of the first aspect.

[0033] Eighthly, embodiments of this application provide another communication device that has the function of implementing the behavior described in the second aspect of the method embodiments. This communication device can be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first session establishment request, the first session establishment request including a first ATSSS capability and a PDU session type, the first ATSSS capability including MPQUIC-E function and ATSSS low-level function, and the PDU session type being Ethernet; the processing module is used to determine whether to enable the MPQUIC-E function for the MA PDU session associated with the first session establishment request based on whether the second core network element supports providing the PDU session type as IP in the N2 SM information.

[0034] In one possible implementation, the transceiver module is further configured to send a policy association establishment request if it is determined that the MPQUIC-E function is not enabled for the PDU session. The policy association establishment request includes a second ATSSS capability, which is a low-level ATSSS function.

[0035] In one possible implementation, the transceiver module is further configured to send a first session establishment response to the second core network element when it is determined that the MPQUIC-E function is enabled for the PDU session. The PDU session type carried in the first session establishment response is IP.

[0036] In one possible implementation, the processing module is also used to determine, via the NRF network element, whether the second core network element supports providing the PDU session type as IP in the N2SM information.

[0037] In one possible implementation, the first core network element is the SMF network element in the HPLMN of the UE associated with the first session establishment request, and the second core network element is the SMF network element in the VPLMN of the UE; the transceiver module is specifically used to receive the first session establishment request from the second core network element.

[0038] For possible implementations of the communication method in the eighth aspect, please refer to the various possible implementations in the second aspect.

[0039] For the technical effects of the various possible implementations of the eighth aspect, please refer to the introduction of the technical effects of the second aspect or the various possible implementations of the second aspect.

[0040] Ninthly, embodiments of this application provide another communication device that has the function of implementing the behavior described in the third aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to send a first session establishment request, the first session establishment request including a first ATSSS capability and a PDU session type, the first ATSSS capability including MPQUIC-E function and ATSSS low-level function, and the PDU session type being Ethernet; and to receive a first session establishment response from a first core network element, the first session establishment response carrying a PDU session type of IPv4 or IPv6. Optionally, the processing module is used to generate and send the first session establishment request.

[0041] In one possible implementation, the transceiver module is further configured to send an N1N2 message transmission message when the PDU session type from the UE is Ethernet and the PDU session type from the first core network element is IP. The N1N2 message transmission message includes N2 SM information, and the PDU session type in the N2 SM information is IPv4 or IPv6.

[0042] For possible implementations of the communication method in the ninth aspect, please refer to the various possible implementations in the third aspect.

[0043] For the technical effects of the various possible implementations of the ninth aspect, please refer to the introduction of the technical effects of the third aspect or the various possible implementations of the third aspect.

[0044] Tenthly, embodiments of this application provide another communication device that has the function of implementing the behavior described in the fourth aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the processing module is used to generate a first attach request when a first condition is met, the first attach request including a PDN type and ATSSS capability, the PDN type being non-IP, the ATSSS capability including MPQUIC-E function and ATSSS lower-layer function, the first condition including UE supporting MPQUIC-E function; the transceiver module is used to send the first attach request to the access network equipment.

[0045] For possible implementations of the communication method in aspect ten, please refer to the various possible implementations in aspect four.

[0046] For the technical effects of the various possible implementations of the tenth aspect, please refer to the introduction of the technical effects of the fourth aspect or the various possible implementations of the fourth aspect.

[0047] Eleventhly, embodiments of this application provide another communication device that has the function of implementing the behavior described in the fifth aspect of the method embodiments. The communication device may be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The function of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a session context request from an AMF network element, the session context request including a first identifier; the processing module is used to determine that the MA PDU session type corresponding to the first identifier is Ethernet; the transceiver module is further used to send a session context response, the session context response including an SM context container, the SM context container including a PDU session type, the PDU session type being IPv4 or IPv6.

[0048] For possible implementations of the communication method in the eleventh aspect, please refer to the various possible implementations in the fifth aspect.

[0049] For the technical effects of the various possible implementations of the eleventh aspect, please refer to the introduction of the technical effects of the fifth aspect or the various possible implementations of the fifth aspect.

[0050] In a twelfth aspect, embodiments of this application provide another communication device that has the function of implementing the behavior described in the sixth aspect method embodiment. This communication device can be a communication equipment, a component of a communication equipment (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the communication equipment. The function of the communication device can be implemented by hardware or by hardware executing corresponding software, the hardware or software including one or more modules or units corresponding to the above functions. In one possible implementation, the communication device includes a transceiver module and a processing module, wherein: the transceiver module is used to receive a first message; the processing module is used to, based on the first message, determine that if the second core network element does not support providing the PDU session type as IP in the N2 SM information when the UE switches from EPS to a roaming scenario, initiate the deactivation of the 3GPP-side user plane connection process.

[0051] In one possible implementation, the processing module is also used to determine, via the NRF network element, whether the second core network element supports providing the PDU session type as IP in the N2SM information.

[0052] For possible implementations of the communication method in aspect 12, please refer to the various possible implementations in aspect 6.

[0053] For the technical effects of the various possible implementations of the twelfth aspect, please refer to the introduction of the technical effects of the sixth aspect or the various possible implementations of the sixth aspect.

[0054] In a thirteenth aspect, embodiments of this application provide another communication device, the communication device including a processor coupled to a memory for storing a program or instructions, which, when executed by the processor, cause the communication device to perform the methods shown in any one of the first to sixth aspects above.

[0055] In this embodiment of the application, during the execution of the above method, the process of sending information (or signals) can be understood as a process of outputting information based on processor instructions. When outputting information, the processor sends the information to the transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, it may require further processing before being input into the processor.

[0056] Unless otherwise specified, or unless their actual function or internal logic in the relevant description is contradicted, the sending and / or receiving operations involved by the processor can generally be understood as processor instruction output.

[0057] In implementation, the processor described above can be a processor specifically designed to execute these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. For example, the processor can also be used to execute a program stored in memory, which, when executed, causes the communication device to perform the methods as shown in the first aspect or any possible implementation thereof.

[0058] In one possible implementation, the memory is located outside the aforementioned communication device. In another possible implementation, the memory is located inside the aforementioned communication device.

[0059] In one possible implementation, the processor and memory may be integrated into a single device; that is, the processor and memory may be integrated together.

[0060] In one possible implementation, the communication device further includes a transceiver for receiving or transmitting signals, etc.

[0061] In a fourteenth aspect, this application provides another communication device, which includes a processing circuit and an interface circuit, the interface circuit being used to acquire or output data; the processing circuit being used to perform the methods shown in any one of the first to sixth aspects above.

[0062] In a fifteenth aspect, this application provides a computer-readable storage medium storing a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method as described in any one of the first to sixth aspects above.

[0063] In a sixteenth aspect, this application provides a computer program product comprising a computer program including program instructions that, when executed, cause a computer to perform the method as described in any one of the first to sixth aspects above.

[0064] In a seventeenth aspect, this application provides a chip including a processor and a communication interface, the communication interface being used for signal transmission and reception of the chip; the processor being used to execute computer program instructions, causing a communication device including the chip to perform the method shown in any one of the first to sixth aspects above. Attached Figure Description

[0065] Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture;

[0066] Figure 2 is a schematic diagram illustrating one possible, non-limiting system;

[0067] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0068] Figure 4 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0069] Figure 5 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0070] Figure 6 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0071] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0072] Figure 8 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0073] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0074] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0075] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0076] Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0077] Figure 13 is a structural schematic diagram of a communication device 1300 provided in an embodiment of this application;

[0078] Figure 14 is a schematic diagram of another device 140 provided in an embodiment of this application. Detailed Implementation

[0079] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are only used to distinguish different objects and not to describe a specific order. It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers does not imply the order of execution; the execution order of each process should be determined by its function and inherent logic. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0080] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. Those skilled in the art will understand, explicitly and implicitly, that the embodiments described herein can be combined with other embodiments. In this application, message names are used only to distinguish different messages and should not be construed as limiting. That is, any message name in this application can be replaced with other names, and this application does not impose any limitations.

[0081] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to and includes any or all possible combinations of one or more of the listed items. For example, “A and / or B” can mean: the presence of only A, the presence of only B, and the presence of both A and B, where A and B can be singular or plural. The term “multiple” as used in this application refers to two or more. In the textual description of this application, the character “ / ” generally indicates that the preceding and following objects are in an “or” relationship.

[0082] It is understood that in the various embodiments of this application, "B corresponding to A" means that there is a correspondence between A and B, and B can be determined based on A. However, it should also be understood that determining (or generating) B based on (or on) A does not mean that B is determined (or generated) solely based on (or on) A; B can also be determined (or generated) based on (or on) A and / or other information.

[0083] It should be understood that in this application, the indication includes direct indication (also known as explicit indication) and implicit indication. Direct indication information A refers to information A being included; implicit indication information A refers to information A being indicated through the correspondence between information A and information B, and through direct indication information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured.

[0084] It should be understood that in this application, information C is used to determine information D, including both situations where information D is determined solely based on information C and situations where it is determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, where information D is determined based on information E, and information E is determined based on information C.

[0085] Furthermore, in the embodiments of this application, "network element A sends information A to network element B" can be understood as network element B being the destination of information A or an intermediate network element in the transmission path between the destination and network element B, which may include sending information directly or indirectly to network element B. "Network element B receives information A from network element A" can be understood as network element A being the source of information A or an intermediate network element in the transmission path between the source and network element A, which may include receiving information directly or indirectly from network element A. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be understood in a similar way and will not be elaborated further here.

[0086] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, future communication systems such as 6th generation (6G) mobile communication systems, or integrated systems of multiple systems, etc., without limitation. 5th generation system is short for 5th generation mobile communication system. 5th generation mobile communication system can also be abbreviated as 5G system (5GS).

[0087] In this application, a cellular system related to the 3rd Generation Partnership Project (3GPP) is used as an example to describe the technical solution of this application, but this should not constitute any limitation on this application. The communication systems to which the technical solutions provided in the embodiments of this application are applicable are merely illustrative examples, and the communication systems to which the technical solutions provided in this application are applicable are not limited thereto. These are uniformly described here and will not be repeated below. The application of the technical solutions of this application in 5G network architecture is described below.

[0088] Figure 1 is a schematic diagram of a 5G network architecture based on a service-oriented architecture. As shown in Figure 1, the 5G network architecture (i.e., 5GS) includes: an access network (AN) and a core network (CN), and may also include: terminal devices.

[0089] A terminal device can be a device with wireless communication capabilities, such as a handheld device or an in-vehicle device with wireless connectivity. Terminal devices communicate with access network devices using some air interface technology (such as NR or LTE). Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE). In vehicle-to-everything (V2X) communication, the communication terminal on the vehicle is a type of terminal device, as can a roadside unit (RSU). The communication terminal carried by a drone can also be considered a type of terminal device.Currently, examples of terminal devices include: mobile phones, satellite mobile terminals, cellular phones, smartphones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smartwatches, smart bracelets, pedometers, smart glasses, etc.), in-vehicle equipment (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), satellite terminals, virtual reality (VR) devices, augmented reality (AR) devices, smart point-of-sale (POS) machines, customer-premises equipment (CPE), wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. Wireless terminals in the home (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes), terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMNs), etc., are not limited to these in this application embodiment. As an example and not a limitation, in this application embodiment, the terminal device can also be an integrated access and backhaul (IAB) node mobile termination (MT). When an IAB node faces its parent node, it can be regarded as a terminal device, in which case the IAB node plays the role of MT.The following example uses UE as a terminal device. UE can be replaced with any other terminal device or other examples of terminal devices in any subsequent instances.

[0090] The aforementioned Access Network (AN) is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission links of different quality based on user level and service requirements to transmit user data. The AN can forward control signals and user data between terminal equipment and the Network Controller (CN). The AN may include access network equipment, also known as radio access network (RAN) equipment.

[0091] Access network equipment can be devices that provide access for terminal devices. Access network equipment is mainly responsible for functions such as radio resource management, quality of service management, data compression, and encryption on the air interface side. The access network equipment can include various forms of base stations, such as macro base stations, micro base stations, relay stations, and access points (APs). In systems employing different radio access technologies, the names of devices with base station functions may differ. For example, in 5G systems, they are called RAN or next-generation Node base stations (gNBs). In LTE systems, they are called evolved Node Bs (eNBs or eNodeBs). Access network equipment can also include: base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), wireless relay node, wireless backhaul node, relay station, transmitting and receiving point (TRP), IAB node, transmitting point (TP), master station, auxiliary station, motor slide retainer (MSR) node, network controller, access node, wireless node, transmission node, transceiver node, remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), radio unit (RU), positioning node, vehicle-mounted equipment, etc.

[0092] A Domain Provider (DN) is a network located outside of the carrier's network. A carrier's network can connect to multiple DNs. Various services can be deployed on a DN, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices, and a control server for these sensors is deployed within the DN. The control server provides services to the sensors. Sensors can communicate with the control server, receive instructions from it, and transmit the collected sensor data back to the control server accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources on the company's internal office network.

[0093] The Network Controller (CN) is primarily responsible for maintaining the subscription data of the mobile network and providing terminal devices with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following: User Plane Function (UPF) network elements, Authentication Server Function (AUSF) network elements, Access and Mobility Management Function (AMF) network elements, Session Management Function (SMF) network elements, Network Slice Selection Function (NSSF) network elements, Network Exposure Function (NEF) network elements, Network Repository Function (NRF) network elements, Policy Control Function (PCF) network elements, Unified Data Management (UDM) network elements, and Application Function (AF) network elements. Optionally, the CN may also include Unified Data Repository (UDR) network elements and other network elements; this is not limited here.

[0094] As shown in Figure 1, the UE accesses the 5G network through the RAN device. The UE communicates with the AMF network element through the N1 interface (N1); the RAN communicates with the AMF network element through the N2 interface (N2); the RAN communicates with the UPF network element through the N3 interface (N3); the SMF network element communicates with the UPF network element through the N4 interface (N4); and the UPF network element accesses the DN through the N6 interface (N6). Furthermore, the control plane functions of the AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, and AF network elements shown in Figure 1 interact using service-oriented interfaces. For example, the service interfaces provided by the AUSF network element include Nausf; the service interfaces provided by the AMF network element include NAMF; the service interfaces provided by the SMF network element include NSMF; the service interfaces provided by the NSSF network element include Nnssf; the service interfaces provided by the NEF network element include Nnef; the service interfaces provided by the NRF network element include Nnrf; the service interfaces provided by the PCF network element include NPCF; the service interfaces provided by the UDM network element include Nudm; and the service interfaces provided by the AF network element include Naf.

[0095] The functions of each network element in the CN are described below.

[0096] AMF network elements are primarily responsible for signaling processing, such as access control, mobility management, attach and detach, and gateway selection. When an AMF network element provides services to a session in a terminal device, it provides control plane storage resources for that session to store the session identifier and the SMF network element identifier associated with the session identifier.

[0097] SMF network elements are responsible for user plane network element selection, user plane network element redirection, Internet Protocol (IP) address allocation, bearer establishment, modification and release, and QoS control.

[0098] UPF network element: Responsible for forwarding and receiving user data in terminal devices. UPF network element can receive user data from the data network and transmit it to the terminal device through access network equipment. UPF network element can also receive user data from the terminal device through access network equipment and forward it to the data network. The transmission resources and scheduling functions providing services to the terminal device within the UPF network element are managed and controlled by the SMF network element.

[0099] NEF network elements primarily support secure interaction between 3GPP networks and third-party applications.

[0100] AF network element: mainly supports interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side.

[0101] PCF network element: Responsible for policy control decisions, providing policy rules for control plane functions, and traffic-based billing control functions.

[0102] NSSF network element: mainly responsible for network slice selection, determining the network slice instance that the UE is allowed to access based on the UE's slice selection auxiliary information, subscription information, etc.

[0103] UDM network element: mainly responsible for the management of UE subscription data, including the storage and management of UE identifiers, UE access authorization, etc.

[0104] AUSF network element: Supports 3GPP and non-3GPP access authentication.

[0105] NRF network elements: support the registration and discovery of network functions.

[0106] UDR network element: Stores and retrieves subscription data used by UDM and PCF network elements.

[0107] It should be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in future communication networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc.

[0108] The aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). As one possible implementation, the aforementioned network element or function can be implemented by a single device, by multiple devices working together, or as a functional module within a single device; this application does not specifically limit this.

[0109] Figure 2 illustrates a possible, non-limiting system diagram. As shown in Figure 2, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. Optionally, the communication system 10 also includes an Internet 300. The RAN 100 includes at least one RAN node (110a and 110b in Figure 2, collectively referred to as 110) and at least one terminal (120a-120j in Figure 2, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 2). The terminal 120 is wirelessly connected to the RAN node 110. The RAN node 110 is wirelessly or wired connected to the core network 200. The core network equipment in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

[0110] RAN100 can be a cellular system related to the 3rd Generation Partnership Project (3GPP), such as 4G, 5G mobile communication systems, or future-oriented evolution systems. RAN100 can also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN100 can also be a communication system that integrates two or more of the above systems.

[0111] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 2 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 2 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0112] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system. The RAN node can be a macro base station (as shown in Figure 2, 110a), a micro base station or indoor station (as shown in Figure 2, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node can also be equipped with communication modules, circuits, or chips that perform corresponding communication functions. The RAN node can also be configured with program instructions for performing corresponding communication functions, as well as corresponding program instructions. The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node's functions.

[0113] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with each RAN node performing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be separate entities or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0114] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0115] To facilitate understanding of the embodiments of this application, the terms involved in this application will be briefly explained below.

[0116] 1) Protocol Data Unit (PDU) Session:

[0117] Currently, 3GPP supports the establishment of single-access PDU sessions or multiple-access (MA) PDU sessions. A single-access PDU session supports only one access technology, such as 3GPP access or non-3GPP access; that is, the PDU session can only transmit data from UEs accessing the network through that single access technology. A multi-access PDU session supports multiple access technologies. For example, PDU session A can transmit data from UEs accessing the network through a first access technology as well as data from UEs accessing the network through a second access technology. This application does not limit the first / second access technology; it can be 3GPP access, non-3GPP access (trusted non-3GPP access or untrusted non-3GPP access), LTE access, 5G RAN access, WLAN access, fixed network access, etc. When a UE accesses the network through two different access types, the UE can establish an MA PDU session to obtain services.

[0118] 2) Access traffic steering, switching, splitting (ATSSS):

[0119] ATSSS technology supports Multipath Transmission Control Protocol (MPTCP), Multipath Quick UDP Internet Connections (MPQUIC), and ATSSS Low Layer (ATSSS-LL). Both MPQUIC-E and ATSSS-LL enable Ethernet sessions.

[0120] Among them, MPTCP is for multiplexing Transmission Control Protocol (TCP) traffic. MPQUIC is for multiplexing User Datagram Protocol (UDP) traffic. ATSSS-LL is for multiplexing Internet Protocol (IP) packets. ATSSS-LL can be used by terminal devices or UPF network elements to select transmission paths for data packets based on traffic splitting modes and link states, supporting multiplexing of both TCP and UDP traffic.

[0121] ATSSS technology supports the following steering modes: active-standby, smallest delay, load balancing, priority-based, redundancy, or future possible steering modes.

[0122] As described in the background section, establishing an MA PDU session is a pressing issue when the UE or DN supports the MPQUIC-E function. This application provides several technical solutions for establishing MA PDU sessions, each applicable to at least one scenario, and capable of establishing an MA PDU session when the UE or DN supports the MPQUIC-E function.

[0123] The technical solutions of this application will now be described with reference to the accompanying drawings. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. In case of any inconsistency, the meaning as set forth in this specification or derived from the content described herein shall prevail.

[0124] In this application, the operations performed by any network element (including the UE) can be implemented by that network element or its components (such as chips or functional modules). The following description uses the implementation of that arbitrary network element as an example. Functional modules can be processors, processing units, communication modules, etc.

[0125] In the embodiments of this application, "when," "if," and "if" all refer to the device taking corresponding actions under certain objective circumstances, not a time limit, nor do they require the device to perform a judgment action, nor do they imply any other limitations. "If" and "if" are interchangeable. Unless otherwise specified, "when" and "in the case of" are interchangeable. The steps indicated by dashed lines in the flowcharts involved in the embodiments of this application are optional steps, that is, steps that can be omitted.

[0126] Figure 3 is a flowchart illustrating a communication method provided in an embodiment of this application. The method in Figure 3 is applicable to UEs in roaming or EPS scenarios. As shown in Figure 3, the method includes:

[0127] 301. The second core network element sends a first session establishment request to the first core network element.

[0128] Accordingly, the first core network element receives the first session establishment request. The first session establishment request includes the first ATSSS capability and the PDU session type. The first ATSSS capability includes the MPQUIC-E function and the ATSSS lower layer (i.e., ATSSS-LL) function. The PDU session type is Ethernet. An equivalent description of the PDU session type as Ethernet is the PDU session type: Ethernet. In this application, any request can be replaced by a request message; for example, the first session establishment request can be replaced by a first session establishment request message.

[0129] In one possible implementation, the second core network element is the SMF (Super Segmented Mobile Network) element in the visited public land mobile network (VPLMN) associated with the UE requesting the first session establishment; the first core network element is the SMF element in the home public land mobile network (HPLMN) associated with the UE. In this application, the SMF element in the HPLMN can be referred to as an H-SMF element, and the SMF element in the VPLMN can be referred to as a V-SMF element. The first core network element can be an H-SMF element, and the second core network element can be a V-SMF element. In this implementation, after receiving the first session establishment request from the second core network element (i.e., the V-SMF element), the first core network element can determine that the UE associated with the first session establishment request is in a roaming scenario.

[0130] In another possible implementation, the second core network element is a serving gateway, meaning the first session establishment request originates from the serving gateway. The first core network element possesses the control plane functions of both an SMF (Super Serving Function) element and a Packet Data Network Gateway (PGW). For example, the first core network element could be an SMF+PGW-C (i.e., PGW control plane functions) element. In this implementation, after receiving the first session establishment request from the serving gateway, the first core network element can determine that the UE associated with the first session establishment request is establishing an MA PDU session in an EPS (Electronic Power Flow) scenario.

[0131] 302. The first core network element sends a policy association establishment request to the PCF network element.

[0132] Correspondingly, the PCF network element receives the policy association establishment request. The policy association establishment request includes a second ATSSS capability. The second ATSSS capability is a low-level ATSSS function, meaning it only includes low-level ATSSS functions. The method flow in Figure 3 can be applied to roaming or EPS scenarios. If the MA PDU session of type Ethernet is established in home-routed roaming or is established with 3GPP access leg in EPC, only ATSSS-LL functionality is enabled.

[0133] In this embodiment of the application, when the first ATSSS capability carried in the first session establishment request includes the MPQUIC-E function and the ATSSS low-level function, the policy association establishment request sent includes the second ATSSS capability, which only includes the ATSSS low-level function; thereby, it is possible to establish an MA PDU session when the UE associated with the first session establishment request is in a roaming or EPS scenario without activating (enabling) the MPQUIC-E function.

[0134] Figure 4 is a flowchart illustrating another communication method provided in this application embodiment. The method in Figure 4 is an example of the method in Figure 3 in a roaming scenario. The main idea of ​​Figure 4 is: in a roaming scenario, regardless of whether the UE and DN support the MPQUIC-E function, the H-SMF network element sends the ATSSS capability of the PDU session to the H-PCF network element based on the PDU session type: Ethernet, and the capability only includes ATSSS-LL. As shown in Figure 4, the method includes:

[0135] S401, The UE sends a PDU session establishment request to the AMF network element.

[0136] Correspondingly, the AMF network element receives a PDU Session Establishment Request. The English names of the messages used in this application can be found in relevant standards and will not be elaborated upon here. The PDU Session Establishment Request is a non-access stratum (NAS) message. Optionally, the PDU Session Establishment Request carries parameters such as request type, ATSSS capability, and PDU session type: ethernet. The ATSSS capability includes MPQUIC-E and ATSSS-LL functions.

[0137] S402, AMF network element selection: V-SMF network element and H-SMF network element that support MA PDU sessions.

[0138] The S403a and AMF network elements send a PDU session creation session context request to the V-SMF network element.

[0139] Correspondingly, the V-SMF network element receives a PDU session creation session context request. For example, this PDU session creation session context request is named Nsmf_PDUSession_CreateSMContext Request. Optionally, this PDU session creation session context request carries parameters such as MA PDU request, ATSSS capability, and PDU session type: ethernet. The ATSSS capability includes MPQUIC-E and ATSSS-LL functions.

[0140] The S403b and V-SMF network elements send a PDU session creation session context response to the AMF network element.

[0141] Correspondingly, the AMF network element receives a PDU session creation session context response from the V-SMF network element. For example, this PDU session creation session context response is an Nsmf_PDUSession_CreateSMContext Response. In this application, any response can be replaced with a response message. For example, the PDU session creation session context response can be replaced with a PDU session creation session context response message.

[0142] The S404a and V-SMF network elements send an N4 session establishment request to the V-UPF network element.

[0143] Correspondingly, the V-UPF network element receives an N4 session establishment request from the V-SMF network element. This N4 session establishment request may include rules such as packet detection rule (PDR), forwarding action rule (FAR), and multiaccess rule (MAR). The MAR rule may include information such as traffic splitting mode and traffic splitting function.

[0144] The S404b and V-UPF network elements send an N4 session establishment response to the V-SMF network element.

[0145] Correspondingly, the V-SMF network element receives the N4 sessionestablishment response from the V-UPF network element.

[0146] S404a and S404b are the steps for establishing an N4 connection between a V-SMF network element and a V-UPF network element.

[0147] S405, V-SMF network element sends first session establishment request to H-SMF network element.

[0148] Correspondingly, the H-SMF network element receives the first session establishment request from the V-SMF network element. S405 can be an example of step 301 in Figure 3. The V-SMF network element is the second core network element in Figure 3, and the H-SMF network element is the first core network element in Figure 3. The first session establishment request can be Nsmf_PDUSession_Create Request. The first session establishment request includes the first ATSSS capability and the PDU session type. The PDU session type is Ethernet. The first ATSSS capability includes the MPQUIC-E function and the ATSSS lower layer. The first session establishment request may also include parameters such as MA PDU request indication.

[0149] S406, H-SMF network element sends a policy association establishment request to H-PCF network element.

[0150] Accordingly, the H-PCF network element receives a policy association establishment request. For example, this policy association establishment request is an SM Policy Association Establishment Request. If the H-SMF network element requires dynamic PCC rules, the H-SMF network element can select another H-PCF network element and establish a session policy association with that H-PCF. S406 and S407 are the steps for the H-SMF network element to establish a session policy association with the H-PCF.

[0151] S406 can be an example of step 302 above. The policy association establishment request is the policy association establishment request in Figure 3. The H-SMF network element is the first core network element in Figure 3. The policy association establishment request includes a second ATSSS capability. The second ATSSS capability is a low-level ATSSS function, meaning it only includes low-level ATSSS functions. After receiving the first session establishment request from the V-SMF network element, the H-SMF network element can determine that the UE associated with the first session establishment request is in a roaming scenario. S406 can be understood as follows: When the UE is in a roaming scenario, regardless of whether the UE and DNN support MPQUIC-E functionality, the ATSSS capability of the MA PDU session that the H-SMF sends to the PCF based on the PDU session type of Ethernet includes only the ATSSS-LL functionality, regardless of whether the UE and DNN support or allow the MPQUIC-E functionality. This policy association establishment request may also include MA PDU requests. DNN refers to the DN.

[0152] S407, H-PCF network element sends a policy association establishment response to H-SMF network element.

[0153] Correspondingly, the H-SMF network element receives a policy association establishment response from the H-PCF network element. For example, this policy association establishment response is an SM Policy Association Establishment Response. This response may contain Multi-Access Session Control (MA PDU) information. This MA PDU information includes information such as steering mode and steering functionality (ATSSS-LL functionality). The steering mode and steering functionality information in this MA PDU information belong to PCC rules.

[0154] The S408a and H-SMF network elements send an N4 session establishment request to the H-UPF network element.

[0155] Correspondingly, the H-UPF network element receives the N4 sessionestablishment request from the H-SMF network element.

[0156] The S408b and H-UPF network elements send an N4 session establishment response to the H-SMF network element.

[0157] Correspondingly, the H-SMF network element receives the N4 sessionestablishment response from the H-UPF network element.

[0158] S408a and S408b are the steps for establishing an N4 connection between an H-SMF network element and an H-UPF network element.

[0159] S409, H-SMF network element sends first session establishment response to V-SMF network element.

[0160] Correspondingly, the V-SMF network element receives the first session establishment response from the H-SMF network element. The first session establishment response includes the PDU session type: ethernet. As an example, the first session establishment response is Nsmf_PDUSession_Create Response.

[0161] The S410 and V-SMF network elements send N1N2 messages to the AMF network element to transmit messages.

[0162] Correspondingly, the AMF network element receives the N1N2 message transfer message from the SMF network element. For example, the N1N2 message transfer message is Namf_Communication_N1N2MessageTransfer.

[0163] Optionally, the N1N2 message transmission message includes information such as a session identifier, N2 SM information, and an N1 interface session management container. This N2 SM information can be sent from the SMF network element to the access network device via the AMF network element. The information in the N1 interface session management container is sent from the SMF network element to the UE via the AMF network element (and subsequently from the AMF network element to the UE via NAS messages). Optionally, the N2 SM information includes the tunnel endpoint identifier of the UPF network element and information such as the PDU session type: Ethernet. Optionally, the N1 interface session management container includes session-related parameter information such as a PDU session establishment acceptance message and an ATSS rule. The PDU session establishment acceptance message includes the PDU session type: Ethernet. The ATSSS rule can include information such as traffic splitting mode, traffic splitting function, and threshold value. Optionally, in the N1N2 message transmission message sent by the V-SMF network element to the AMF network element, the V-SMF network element may also instruct the AMF network element on which access type path the message is transmitted through (e.g., via 3GPP access or non-3GPP access), thereby enabling the AMF network element to send the N1N2 message transmission message to the access network device corresponding to that access type path. For example, if the V-SMF network element instructs the AMF network element to send the message via 3GPP access, in S411, the AMF network element can send the content included in the message to the access network device.

[0164] S411, the AMF network element sends an N2 PDU session request to the access network device.

[0165] Correspondingly, the access network device receives an N2 PDU session request from an AMF network element. Optionally, the N2 PDU session request carries N2SM information (PDU session type: Ethernet, CN tunnel information), and a NAS message to be sent to the UE. This NAS message may include a session identifier and an N1 interface session management container. The session identifier is used to identify the N2 PDU session request.

[0166] S412. The access network device establishes air interface resources with the UE and sends NAS messages to the UE.

[0167] The NAS message can carry session-related parameters such as PDU session establishment and acceptance messages (PDU session type) and ATSSS rules. The ATSSS rules can include information such as traffic splitting mode, traffic splitting function, and threshold values.

[0168] S413. The access network device sends an N2 PDU session response to the AMF network element.

[0169] Correspondingly, the AMF network element receives the N2 PDU session response from the access network device. Optionally, the N2 PDU session response carries the tunnel endpoint identifier on the access network device side (which can subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through the 3GPP access path).

[0170] S414, the AMF network element sends a PDU session update session context request to the V-SMF network element.

[0171] Correspondingly, the V-SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes information from RAM, i.e., information sent by the access network device in S413.

[0172] S415 and V-SMF network elements execute the N4 session modification process.

[0173] V-SMF network elements can send AN tunnel endpoint identification information from the access network device side to UPF network elements through the N4 session modification procedure.

[0174] S416, V-SMF network element sends PDU session update session context response to AMF network element.

[0175] Correspondingly, the AMF network element receives the PDU session update session context response from the V-SMF network element.

[0176] S417, V-SMF network element sends N1N2 message to AMF network element to transmit message.

[0177] Correspondingly, the AMF network element receives the N1N2 message transmission message from the SMF network element. Optionally, the N1N2 message transmission message includes information such as a session identifier and N2 SM information. This N2 SM information can be sent by the V-SMF network element to a non-3GPP access gateway device (e.g., the N3IWF network element in Figure 4) through the AMF network element. In this application, N3IWF is short for non-3GPP interworking function. The N2 SM information may include information such as the tunnel endpoint identifier of the UPF network element, which is sent to the N3IWF network element to tell it where the uplink data should be sent (which can be understood as the destination address of the uplink data). This message may not include the N1 session management container (because the information to be sent to the UE has already been sent through the access network device).

[0178] S418, AMF network element sends N2 PDU session request to N3IWF network element.

[0179] Correspondingly, the N3IWF network element receives an N2 PDU session request from the AMF network element. This N2 PDU session request may carry N2SM information.

[0180] The S419 and N3IWF network elements establish an IPSec Child SA with the UE for transmitting user plane data.

[0181] During this process, the N3IWF network element will assign the UE an IP address (UP_IP_ADDRESS) associated with the IP security sub-security. That is, when the UE needs to send uplink data, the destination IP address should be set to this UP_IP_ADDRESS in the inner IP protocol stack, while the source IP address is the "inner" address assigned during registration. The number of IPSec Child SAs established between the UE and the N3IWF network element, and the quality of service (QoS) flows transmitted in each IPSec Child SA, are determined by the N3IWF network element's policies and configuration.

[0182] The S420 and N3IWF network elements send N2 PDU session responses to the AMF network element.

[0183] Correspondingly, the AMF network element receives the N2 PDU session response from the N3IWF network element. This N2 PDU session response may carry the tunnel endpoint identifier on the N3IWF network element side (which will subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through a non-3GPP access path).

[0184] S421, the AMF network element sends a PDU session update session context request to the V-SMF network element.

[0185] Correspondingly, the V-SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes messages sent by the N3IWF network element, i.e., messages sent by the N3IWF network element in S420.

[0186] S422 and V-SMF network elements execute the N4 session modification process.

[0187] V-SMF network elements can send the AN tunnel endpoint identification information from the N3IWF network element side to UPF network elements through the N4 session modification procedure.

[0188] S423, V-SMF network element sends PDU session update session context response to AMF network element.

[0189] Since the MA PDU session requires separate session establishment procedures on both the 3GPP access side and the non-3GPP access side (i.e., the UE needs to send session establishment requests on both the 3GPP and non-3GPP sides respectively), Figure 4 only shows an example diagram of establishing the user plane path first on the 3GPP side and then on the non-3GPP side. However, establishing an MA PDU session does not necessarily require it to be established on the 3GPP side first; therefore, the schematic diagram for establishing the user plane first on the non-3GPP side and then on the 3GPP side is similar to the above diagram, the difference being that the user plane path is first established through the non-3GPP access gateway, and then through the 3GPP access network equipment.

[0190] In this embodiment of the application, in a roaming scenario, regardless of whether the UE and DN support the MPQUIC-E function, the H-SMF network element sends the ATSSS capability of the PDU session to the H-PCF network element based on the PDU session type: ethernet, which only includes the ATSSS-LL function; thereby, it is possible to establish an MA PDU session without activating the MPQUIC-E function when the UE that requested the association in the first session is in a roaming scenario.

[0191] Figure 5 is a flowchart illustrating another communication method provided in this application embodiment. The method in Figure 5 is an example of the method in Figure 3 when the UE is in an EPS scenario. The main idea of ​​Figure 5 is: when the UE is in an EPS scenario, regardless of whether the UE and DN support the MPQUIC-E function, the SMF+PGW-C network element, based on the PDU session type (Ethernet), sends the MA PDU session's ATSSS capability to the PCF network element, which only includes ATSSS-LL. As shown in Figure 5, the method includes:

[0192] S501, the UE sends an attach request to the access network device.

[0193] Correspondingly, the access network device (e.g., eNodeB) receives an attach request from the UE. Optionally, this attach request carries an EPS session management (ESM) message container. This ESM message container may include parameters such as request type, ATSSS capability, and PDN type (e.g., ethernet). The ATSSS capability includes MPQUIC-E and ATSSS-LL functions.

[0194] S502, The access network device initiates an attach request to the MME.

[0195] The S1-MM control message carried in the attach request may include an ESM message container. MME is short for Mobility Management Entity.

[0196] S503, MME sends a session creation request to the service gateway.

[0197] Accordingly, the service gateway receives a create session request from the MME. Optionally, this create session request carries the packet data network (PDN) type: Ethernet and ATSSS capability. The ATSSS capability includes MPQUIC-E and ATSSS-LL functions.

[0198] S504. The service gateway sends a session creation request to the SMF+PGW-C network element.

[0199] Correspondingly, the SMF+PGW-C network element receives a create session request from the serving gateway. Optionally, this create session request carries the PDN type: ethernet and ATSSS capability. S504 can be an example of step 301 in Figure 3. The serving gateway network element is the second core network element in Figure 3, and the SMF+PGW-C network element is the first core network element in Figure 3. The aforementioned first session establishment request can be this create session request.

[0200] The S505 and SMF+PGW-C network elements send a policy association establishment request to the PCF network element.

[0201] Correspondingly, the PCF network element receives a policy association establishment request (e.g., SM Policy Association Establishment Request) from the SMF+PGW-C network element. If the SMF+PGW-C network element requires dynamic PCC rules, it can select the PCF network element (i.e., the PCF network element in Figure 5) and establish a session policy association with that PCF network element.

[0202] S505 can be an example of step 302 above. The policy association establishment request is the policy association establishment request in Figure 3. The SMF+PGW-C network element is the first core network element in Figure 3. This policy association establishment request includes the second ATSSS capability. The second ATSSS capability is a low-level ATSSS function, meaning the second ATSSS capability only includes low-level ATSSS functions. S505 can be understood as follows: In an EPS scenario, regardless of whether the UE and DN support the MPQUIC-E function, the ATSSS capability of the MA PDU session that the PGW-C+SMF sends to the PCF based on the PDN type of Ethernet (i.e., PDN type: ethernet) only includes the ATSSS-LL functionality. This policy association establishment request may also include an MA PDU request.

[0203] S506, PCF network element sends a policy association establishment response to SMF+PGW-C network element.

[0204] Correspondingly, the SMF+PGW-C network element receives a policy association establishment response (e.g., SM Policy Association Establishment Response) from the PCF network element. This policy association establishment response may contain multi-access session control information (MA PDU session control information). This multi-access control information includes information such as steering mode and steering functionality (ATSSS-LL functionality).

[0205] The S507, SMF+PGW-C network element and the UPF+PGW-C network element establish an N4 connection.

[0206] Specifically, the SMF+PGW-C network element sends N4 rules to the UPF+PGW-C network element, including PDR, forwarding action rules, and multi-access rules. The MAR rule can include information such as traffic splitting mode and traffic splitting function.

[0207] The S508 and SMF+PGW-C network elements send a session creation response to the service gateway.

[0208] Accordingly, the service gateway receives a Create Session Response from the SMF+PGW-C network element. This Create Session Response may include a PDN type of ethernet.

[0209] S509, The service gateway sends a session creation response to the MME.

[0210] Accordingly, the MME receives a create session response from the service gateway. This create session response may include the PDN type: ethernet.

[0211] The S510 and MME send an initial context setting request to the access network equipment.

[0212] Accordingly, the access network device receives an Initial Context Setup Request from the MME. This Initial Context Setup Request includes the PDN type: ethernet.

[0213] S511. The access network device sends an RRC connection reconfiguration message to the UE.

[0214] Accordingly, the UE receives an RRC connection reconfiguration message from the access network device. This RRC connection reconfiguration message may contain an attach accept message. This attach accept message may include the PDU session type: ethernet.

[0215] S512, the UE sends an RRC connection reconfiguration complete message to the access network device.

[0216] Correspondingly, the access network device receives an RRC Connection Reconfiguration Complete message from the UE.

[0217] S513, The access network device sends an initial context setting response to the MME.

[0218] Accordingly, the MME receives an Initial Context Setup Response from the access network device. This Initial Context Setup Response includes the access network device's tunnel endpoint identifier (TEID) and the access network device address for downlink traffic on the S1-user plane (S1_U) reference point.

[0219] S514, the UE sends a direct transmission message to the access network device.

[0220] Accordingly, the access network device receives a Direct Transfer message from the UE. This Direct Transfer message may include an Attach Complete message. This Attach Complete message may include the EPS bearer identity, NAS serial number, NAS-MAC, etc.

[0221] S515, the access network device forwards the attach complete message to the MME.

[0222] Optionally, the access network device forwards the attach completion message to the MME via uplink NAS transmission messages.

[0223] S516, MME sends a modify bearer request to the service gateway.

[0224] Correspondingly, the serving gateway receives a modify bearer request from the MME. The MME can send the modify bearer request after receiving the initial context response in S513 and the attach completion message in S515. This modify bearer request may include the EPS bearer identity, access network device address, access network device TEID, handover indication, presence reporting area information, RAT type, and a message reporting the LTE-M RAT type to the PGW, etc.

[0225] S517a: The service gateway sends a modify bearer request to the SMF+PGW-C network element.

[0226] Correspondingly, the SMF+PGW-C network element receives a modify bearer request from the serving gateway.

[0227] The S517b and SMF+PGW-C network elements send a modified bearer response to the serving gateway.

[0228] Correspondingly, the service gateway receives the modified bearer response from the SMF+PGW-C network element.

[0229] S518, The service gateway sends a modified bearer response to the MME.

[0230] S519, SMF network element sends N1N2 message to AMF network element to transmit message.

[0231] Correspondingly, the AMF network element receives the N1N2 message transmission message from the SMF network element. Optionally, the N1N2 message transmission message includes information such as a session identifier and N2 SM information. This N2 SM information can be sent by the V-SMF network element to a non-3GPP access gateway device (e.g., the N3IWF network element in Figure 4) through the AMF network element. In this application, N3IWF is short for non-3GPP interworking function. The N2 SM information may include information such as the tunnel endpoint identifier of the UPF network element, which is sent to the N3IWF network element to tell it where the uplink data should be sent (which can be understood as the destination address of the uplink data). This message may not include the N1 session management container (because the information to be sent to the UE has already been sent through the access network device).

[0232] The S520 and AMF network elements send an N2 PDU session request to the N3IWF network element.

[0233] Correspondingly, the N3IWF network element receives an N2 PDU session request from the AMF network element. This N2 PDU session request may carry N2SM information.

[0234] The S521 and N3IWF network elements establish an IP security sub-security association with the UE for transmitting user plane data.

[0235] During this process, the N3IWF network element will assign the IP address (UP_IP_ADDRESS) of the IPSec Child SA to the UE. That is, when the UE needs to send uplink data, the destination IP address should be set to this UP_IP_ADDRESS in the internal IP protocol stack, while the source IP address is the "inner" address assigned during registration. The number of IPSec Child SAs established between the UE and the N3IWF network element, and which QoS flow data is transmitted in each IPSec Child SA, are determined based on the N3IWF network element's policies and configuration.

[0236] The S522 and N3IWF network elements send N2 PDU session responses to the AMF network element.

[0237] Correspondingly, the AMF network element receives the N2 PDU session response from the N3IWF network element. This N2 PDU session response may carry the tunnel endpoint identifier on the N3IWF network element side (which will subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through a non-3GPP access path).

[0238] S523, the AMF network element sends a PDU session update session context request to the SMF network element.

[0239] Correspondingly, the SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes messages sent by the N3IWF network element, i.e., messages sent by the N3IWF network element in S420.

[0240] S524 and SMF network elements execute the N4 session modification process.

[0241] The SMF network element can send the AN tunnel endpoint identification information from the N3IWF network element side to the UPF network element through the N4 session modification procedure.

[0242] S525, SMF network element sends PDU session update session context response to AMF network element.

[0243] Since the MA PDU session requires separate session establishment procedures on both the 3GPP access side and the non-3GPP access side (i.e., the UE needs to send session establishment requests on both the 3GPP and non-3GPP sides respectively), Figure 5 only shows an example diagram of establishing the user plane path first on the 3GPP side and then on the non-3GPP side. Establishing an MA PDU session does not necessarily require it to be established on the 3GPP side first; therefore, the schematic diagram for establishing the user plane first on the non-3GPP side and then on the 3GPP side is similar to the above diagram, the difference being that the user plane path is first established through the non-3GPP access gateway, and then through the 3GPP access network equipment.

[0244] In this embodiment, when the UE is in an EPS scenario, regardless of whether the UE and DN support the MPQUIC-E function, the SMF+PGW-C network element sends the ATSSS capability of the MA PDU session to the PCF based on the PDN type: ethernet. This enables the UE that made the first session establishment request to be associated to be in an EPS scenario without activating (enabling) the MPQUIC-E function, thereby establishing the MA PDU session.

[0245] Figure 6 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 6 is applicable to a UE in a roaming scenario. As shown in Figure 6, the method includes:

[0246] 601. The second core network element sends a first session establishment request to the first core network element.

[0247] Accordingly, the first core network element receives a first session establishment request from the second core network element. The first session establishment request includes a first ATSSS capability and a PDU session type. The first ATSSS capability includes MPQUIC-E functionality and ATSSS lower-level functions. The PDU session type is Ethernet.

[0248] In one possible implementation, the first core network element is the SMF network element in the HPLMN of the UE associated with the first session establishment request, i.e., the H-SMF network element, and the second core network element is the SMF network element in the VPLMN of the UE, i.e., the V-SMF network element. The first core network element receives the first session establishment request from the second core network element; thus, it can be determined that the UE is in a roaming scenario.

[0249] 602. The first core network element determines whether to enable the MPQUIC-E function for the MA PDU session associated with the first session establishment request based on whether the second core network element supports providing the PDU session type as IP in the N2 SM information.

[0250] Optionally, the method in Figure 6 may further include steps 603A or 603B1 to 603B2.

[0251] Optionally, before the first core network element executes step 602, the following operation can be performed: The first core network element determines whether the second core network element supports providing the PDU session type as IP in the N2SM information through the network repository function (NRF) element. In one possible implementation, the first core network element is an H-SMF element. The H-SMF element can obtain a V-SMF policy by sending a V-SMF ID to the NRF element. This V-SMF ID is used to identify the V-SMF element. According to the V-SMF policy, the H-SMF can determine whether it supports providing the PDU session type as IP in the N2SM information when the MA PDU session type is Ethernet.

[0252] 603A. If the first core network element determines that the MPQUIC-E function will not be enabled for the MA PDU session, it sends a policy association establishment request to the H-PCH network element.

[0253] Correspondingly, the PCF network element receives a policy association establishment request from the first core network element. This policy association establishment request includes a second ATSSS capability. This second ATSSS capability is a low-level ATSSS function, meaning it only includes low-level ATSSS functions.

[0254] 603B1. When the first core network element determines that the MPQUIC-E function is enabled for the MA PDU session, it sends a first session establishment response to the second core network element.

[0255] Correspondingly, the second core network element receives the first session establishment response from the first core network element. The PDU session type carried in the first session establishment response is IP. The PDU session type carried in the first session establishment response can be IPv4 or IPv6. In other words, the PDU session type carried in the first session establishment response is: IPv4, IPv6, or IPv4v6.

[0256] Optionally, after the first core network element performs step 603B1, it may also perform the following step 603B2: When the PDU session type from the UE is Ethernet and the PDU session type from the first core network element is IP, the second core network element sends an N1N2 message transfer message (e.g., Namf_Communication_N1N2MessageTransfer). This N1N2 message transfer message includes N2 SM information. The PDU session type in the N2 SM information is IPv4 or IPv6. This IPv4 or IPv6 is received by the second core network element from the SMF network element (i.e., the first core network element) in the HPLMN of the UE associated with the first session establishment request. By sending the N1N2 message transfer message carrying this N2 SM information, the access network device is informed that the PDU session type is IP. Step 603B2 can be understood as follows: If the second core network element receives a PDU session type of ethernet from the UE and a PDU session type of IPv4 or IPv6 from the first core network element, then the second core network element sets the value of "PDU session type" in the N2 SM information to IPv4 or IPv6 received from the first core network element.

[0257] In this embodiment, the first core network element determines whether to enable the MPQUIC-E function for the MA PDU session associated with the first session establishment request based on whether the second core network element supports providing the PDU session type as IP in the N2 SM information. Thus, if the second core network element does not support providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is not enabled for the MA PDU session; and if the second core network element supports providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is enabled for the MA PDU session, thereby successfully establishing the MA PDU session.

[0258] Figure 7 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 7 is an example of the method in Figure 6. Figure 7 shows the complete process of a UE establishing an MA PDU session in a roaming scenario. As shown in Figure 7, the method includes:

[0259] S701, the UE sends a PDU session establishment request to the AMF network element.

[0260] Correspondingly, the AMF network element receives the PDU Session Establishment Request.

[0261] S701 to S705 can be referred to as S401 to S405 in Figure 4, and will not be described again here.

[0262] S702, AMF network element selection supports V-SMF network elements and H-SMF network elements for MA PDU sessions.

[0263] The S703a and AMF network elements send a PDU session creation session context request to the V-SMF network element.

[0264] Correspondingly, the V-SMF network element receives a PDU session creation session context request. Optionally, this PDU session creation session context request carries parameters such as MA PDU request, ATSSS capability, and PDU session type: ethernet. The ATSSS capability includes MPQUIC-E and ATSSS-LL functions.

[0265] The S703b and V-SMF network elements send a PDU session creation session context response to the AMF network element.

[0266] Correspondingly, the AMF network element receives the PDU session creation session context response (Nsmf_PDUSession_CreateSMContext Response) from the V-SMF network element.

[0267] The S704a and V-SMF network elements send an N4 session establishment request to the V-UPF network element.

[0268] Correspondingly, the V-UPF network element receives the N4 sessionestablishment request from the V-SMF network element.

[0269] The S704b and V-UPF network elements send an N4 session establishment response to the V-SMF network element.

[0270] Correspondingly, the V-SMF network element receives the N4 sessionestablishment response from the V-UPF network element.

[0271] S704a and S704b are the steps for establishing an N4 connection between a V-SMF network element and a V-UPF network element.

[0272] The S705 and V-SMF network elements send the first session establishment request to the H-SMF network element.

[0273] Correspondingly, the H-SMF network element receives the first session establishment request from the V-SMF network element. S705 can be an example of step 601 in Figure 6. The V-SMF network element is the second core network element in Figure 6, and the H-SMF network element is the first core network element in Figure 6. The first session establishment request can be Nsmf_PDUSession_Create Request. The first session establishment request includes the first ATSSS capability and the PDU session type. The PDU session type is Ethernet. The first ATSSS capability includes the MPQUIC-E function and the ATSSS lower layer. The first session establishment request may also include parameters such as MA PDU request indication.

[0274] S706 and H-SMF network elements determine whether to enable the MPQUIC-E function for the MA PDU session associated with the first session establishment request based on whether the V-SMF network element supports providing the PDU session type as IP in the N2 SM information.

[0275] Optionally, the H-SMF network element determines the V-SMF network element capability through the NRF network element, that is, whether it supports providing the PDU session type as IP in the N2 SM information when the PDU session type is Ethernet.

[0276] The S707a and H-SMF network elements send a policy association establishment request to the H-PCF network element.

[0277] Correspondingly, the H-PCF network element receives a policy association establishment request (e.g., SM Policy Association Establishment Request). If the H-SMF network element requires dynamic policy control and charging (PCC) rules, it can select an H-PCF network element and establish a session policy association with that H-PCF.

[0278] Figure 7 illustrates the process of establishing an MA PDU session when the V-SMF network element supports providing the PDU session type as IP in the N2 SM information. When the V-SMF network element does not support providing the PDU session type as IP in the N2 SM information, after S707a, the MA PDU session can be established through the processes S407 to S423 in Figure 4 above. In other words, when the V-SMF network element does not support providing the PDU session type as IP in the N2 SM information, a possible process for establishing an MA PDU session includes: the steps before S707a in Figure 7 (including S707a) and the steps after S407 in Figure 4 (including S407).

[0279] In some possible embodiments, the V-SMF network element supports providing PDU session type as IP in the N2 SM information; the policy association establishment request includes ATSSS capability, which includes MPQUIC-E function and ATSSS-LL function.

[0280] In some possible embodiments, the V-SMF network element does not support providing the PDU session type as IP in the N2 SM information; the policy association establishment request includes a second ATSSS capability. This second ATSSS capability is a low-level ATSSS function, meaning it only includes low-level ATSSS functions. In these possible embodiments, S707a can be an example of step 603A described above. The H-SMF network element is the first core network element in Figure 6. After receiving the first session establishment request from the V-SMF network element, the H-SMF network element can determine that the UE associated with the first session establishment request is in a roaming scenario. In these embodiments, S706 and S707a can be understood as follows: For an Ethernet type MA PDU session, the H-SMF determines whether the V-SMF supports providing PDU Session type as "IP" in the N2 SM information to NG-RAN via the NRF. If the V-SMF does not support providing PDU Session type as IP in the N2 SM information to NG-RAN, then MPQUIC-E functionality is not enabled for the MA PDU Session (i.e., the H-SMF does not include MPQUIC-E in the ATSSS capabilities of the PDU Session sent to H-PCF, regardless of whether the UE supports the MPQUIC-E functionality).NG-RAN is short for next generation radio access network.

[0281] The S707b and H-PCF network elements send a policy association establishment response to the H-SMF network element.

[0282] Correspondingly, the H-SMF network element receives a policy association establishment response (e.g., SM Policy Association Establishment Response) from the H-PCF network element. This policy association establishment response may contain multiple access session control information (MA PDU session control information). This MA PDU session control information includes information such as traffic splitting mode and traffic splitting function (MPQUIC-E function).

[0283] The S708a and H-SMF network elements send an N4 session establishment request to the H-UPF network element.

[0284] Correspondingly, the H-UPF network element receives the N4 sessionestablishment request from the H-SMF network element.

[0285] The S708b and H-UPF network elements send an N4 session establishment response to the H-SMF network element.

[0286] Correspondingly, the H-SMF network element receives the N4 sessionestablishment response from the H-UPF network element.

[0287] S708a and S708b are the steps for establishing an N4 connection between an H-SMF network element and an H-UPF network element.

[0288] The S709a and H-SMF network elements send the first session establishment response to the V-SMF network element.

[0289] Correspondingly, the V-SMF network element receives a first session establishment response from the H-SMF network element. The PDU session type carried in the first session establishment response is IP. Alternatively, the first session establishment response carries a PDU session type of IPv4 or IPv6. As an example, the first session establishment response is an Nsmf_PDUSession_Create Response. Optionally, the H-SMF network element sends an "MA PDU session Accepted" indication to the V-SMF network element in the Nsmf_PDUSession_Create Response message. The H-SMF network element indicates to the V-SMF the relationship between the UL N9 tunnel CN ​​information and the access type. S709a is an example of step 603B1 in Figure 6.

[0290] For Ethernet MAPDU session types, if the Steering function parameter in the received PCC rule's MAPDU session control information is set to MPQUIC-E, then H-SMF will indicate the IPv4 or IPv6 PDU session type as V-SMF.

[0291] S709a can be understood as follows: For an Ethernet-type MA PDU session, if the Steering function parameter in the MA PDU session control information of the received PCC rule(s) is set to MPQUIC-E, then the H-SMF indicates the PDU session type of IPv4 or IPv6 to the V-SMF.

[0292] When the PDU session type from the H-SMF network element is IPv4 or IPv6, the S709b and V-SMF network elements will set the value of "PDU session type" in the N2 SM information to IPv4 or IPv6.

[0293] In one possible implementation, for an Ethernet-type MA PDU session (i.e., the V-SMF receives the PDU session type as Ethernet from the UE), if the V-SMF receives the PDU session type as IPv4 or IPv6 from the H-SMF, then the V-SMF sets the value of the PDU session type in the N2 SM information to IPv4 or IPv6 accordingly. Alternatively, if the V-SMF network element receives a PDU session type of ethernet from the UE and a PDU session type of IPv4 or IPv6 from the H-SMF network element, then the V-SMF network element will set the value of "PDU session type" in the N2 SM information to the IPv4 or IPv6 received from the H-SMF network element.

[0294] The S710 and V-SMF network elements send N1N2 messages to the AMF network element to transmit messages.

[0295] Correspondingly, the AMF network element receives N1N2 message transmission messages from the V-SMF network element. For example, the N1N2 message transmission message is Namf_Communication_N1N2MessageTransfer.

[0296] Optionally, the N1N2 message transmission message includes information such as a session identifier, N2 SM information, and an N1 interface session management container. The N2 SM information is sent from the SMF network element to the access network device via the AMF network element. The information in the N1 interface session management container is sent from the SMF network element to the UE via the AMF network element (subsequently sent to the UE by the AMF network element via NAS messages). Optionally, the N2 SM information includes the tunnel endpoint identifier of the UPF network element and information such as the PDU session type: IPv4 or IPv6. Optionally, the N1 interface session management container includes session-related parameter information such as a PDU session establishment acceptance message (PDU session establishment Accept (PDU sessiontype:Ethernet)) and ATSSS rules. The ATSSS rules may include information such as traffic splitting mode, traffic splitting function, and threshold values. Optionally, in the N1N2 message transmission message sent by the V-SMF network element to the AMF network element, the V-SMF network element may also instruct the AMF network element on which access type path the message is transmitted through (e.g., via 3GPP access or non-3GPP access), thereby enabling the AMF network element to send the N1N2 message transmission message to the access network device corresponding to that access type path. For example, if the V-SMF network element instructs the AMF network element to send the message via 3GPP access, in S411, the AMF network element can send the content included in the message to the access network device.

[0297] The S711 and AMF network elements send N2 PDU session requests to the access network equipment.

[0298] Correspondingly, the access network device receives an N2 PDU session request from the AMF network element. Optionally, the N2 PDU session request carries N2SM information (PDU session type: IPv4 or IPv6, CN tunnel information) and a NAS message to be sent to the UE. This NAS message includes a session identifier and an N1 interface session management container.

[0299] S712, The access network device establishes air interface resources with the UE, and the access network device sends NAS messages to the UE.

[0300] This NAS message can carry PDU session establishment and acceptance messages (PDU session type: Ethernet) and session-related parameter information such as ATSSS rules. ATSSS rules can include information such as traffic splitting mode, traffic splitting function, and threshold values.

[0301] S713, The access network device sends an N2 PDU session response to the AMF network element.

[0302] Accordingly, the AMF network element receives the N2 PDU session response from the access network device. Optionally, the N2 PDU session response carries the tunnel endpoint identifier on the access network device side (which will subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through the 3GPP access path).

[0303] S714, the AMF network element sends a PDU session update session context request to the V-SMF network element.

[0304] Correspondingly, the V-SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes information from RAM, i.e., information sent by the access network device in S713.

[0305] The S715 and V-SMF network elements send the AN tunnel endpoint identification information from the access network device side to the UPF network element through the N4 session modification procedure.

[0306] The S716 and V-SMF network elements send a PDU session update session context response to the AMF network element.

[0307] Correspondingly, the AMF network element receives the PDU session update session context response from the V-SMF network element.

[0308] The S717 and V-SMF network elements send N1N2 messages to the AMF network element to transmit messages.

[0309] Correspondingly, the AMF network element receives the N1N2 message transmission message from the SMF network element. Optionally, the N1N2 message transmission message includes information such as a session identifier and N2 SM information. This N2 SM information can be sent by the V-SMF network element to a non-3GPP access gateway device (e.g., the N3IWF network element in Figure 7) through the AMF network element. In this application, N3IWF is short for non-3GPP interworking function. The N2 SM information may include information such as the tunnel endpoint identifier of the UPF network element, which is sent to the N3IWF network element to tell it where the uplink data should be sent (which can be understood as the destination address of the uplink data). This message may not include the N1 session management container (because the information to be sent to the UE has already been sent through the access network device).

[0310] The S718 and AMF network elements send an N2 PDU session request to the N3IWF network element.

[0311] Correspondingly, the N3IWF network element receives an N2 PDU session request from the AMF network element. This N2 PDU session request may carry N2SM information.

[0312] The S719 and N3IWF network elements establish an IPSec Child SA with the UE for transmitting user plane data.

[0313] During this process, the N3IWF network element will assign the IP address (UP_IP_ADDRESS) of the IPSec Child SA to the UE. That is, when the UE needs to send uplink data, the destination IP address should be set to this UP_IP_ADDRESS in the inner IP protocol stack, while the source IP address is the "inner" address assigned during registration. The number of IPSec Child SAs established between the UE and the N3IWF network element, and the quality of service (QoS) flows transmitted by each IPSec Child SA, are determined by the N3IWF network element's policies and configuration.

[0314] The S720 and N3IWF network elements send N2 PDU session responses to the AMF network element.

[0315] Correspondingly, the AMF network element receives the N2 PDU session response from the N3IWF network element. This N2 PDU session response may carry the tunnel endpoint identifier on the N3IWF network element side (which will subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through a non-3GPP access path).

[0316] S721, the AMF network element sends a PDU session update session context request to the V-SMF network element.

[0317] Correspondingly, the V-SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes messages sent by the N3IWF network element, i.e., messages sent by the N3IWF network element in S720.

[0318] The S722 and V-SMF network elements send the AN tunnel endpoint identification information from the N3IWF network element side to the UPF network element through the N4 session modification procedure.

[0319] The S723 and V-SMF network elements send a PDU session update session context response to the AMF network element.

[0320] Since the MA PDU session requires separate session establishment procedures on both the 3GPP access side and the non-3GPP access side (i.e., the UE needs to send session establishment requests on both the 3GPP and non-3GPP sides respectively), Figure 7 only shows an example diagram of establishing the user plane path first on the 3GPP side and then on the non-3GPP side. Because establishing an MA PDU session does not necessarily require it to be established on the 3GPP side first, the schematic diagram for establishing the user plane first on the non-3GPP side and then on the 3GPP side is similar to the above diagram, the difference being that the user plane path is first established through the non-3GPP access gateway, and then through the 3GPP access network equipment.

[0321] In this embodiment of the application, if the V-SMF network element does not support providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is not enabled for the PDU session; and if the V-SMF network element supports providing the PDU session type as IP in the N2 SM information, the MPQUIC-E function is enabled for the PDU session, thereby successfully establishing the MA PDU session.

[0322] Figure 8 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 8 is applicable to the UE in an EPS scenario. As shown in Figure 8, the method includes:

[0323] S801. If the first condition is met, the UE generates a first attach request.

[0324] The first condition includes that the UE supports MPQUIC-E functionality. Optionally, the first condition also includes that the UE is in an EPS scenario. The first attach request includes the PDN type and ATSSS capability. The PDN type is Non-IP. The ATSSS capability includes MPQUIC-E functionality and ATSSS lower-level functionality. As an example, the first attach request carries an ESM message container. The ESM message container includes parameters such as request type, ATSSS capability, and PDN type: Non-IP.

[0325] S801 can be replaced with: If the UE is capable of supporting the MPQUIC-E functionality, then the PDN type is set to Non-IP. Setting the PDN type to Non-IP can be achieved by sending an attach request carrying the PDN type: Non-IP, such as the first attach request mentioned above.

[0326] S802, the UE sends a first attach request to the access network device.

[0327] Accordingly, the access network device receives the first attach request.

[0328] S803, The access network device sends an attach request to the MME.

[0329] The S1-MME control message carried in the attach request includes an ESM message container.

[0330] Optionally, the method in Figure 8 further includes the following steps S804 to S825.

[0331] S804, MME sends a session creation request to the service gateway.

[0332] Accordingly, the service gateway receives a Create Session Request from the MME. This Create Session Request carries the PDN type: Non-IP and ATSSS capabilities.

[0333] S805, the service gateway sends a session creation request to the SMF+PGW-C network element.

[0334] Correspondingly, the SMF+PGW-C network element receives a session creation request from the serving gateway. This session creation request carries the PDN type: Non-IP and ATSSS capabilities.

[0335] The S806a and SMF+PGW-C network elements send a policy association establishment request to the PCF network element.

[0336] Correspondingly, the PCF network element receives a policy association establishment request (e.g., SM Policy Association Establishment Request) from the SMF+PGW-C network element. If the SMF+PGW-C network element requires dynamic PCC rules, it can select the PCF network element (i.e., the PCF network element in Figure 5) and establish a session policy association with it. Optionally, the policy association establishment request includes an MA PDU request and ATSSS capability. The ATSSS capability includes the MPQUIC-E function and the ATSSS-LL function.

[0337] The S806b and PCF network elements send a policy association establishment response to the SMF+PGW-C network element.

[0338] Correspondingly, the SMF+PGW-C network element receives a policy association establishment response (e.g., SM Policy Association Establishment Response) from the PCF network element. This policy association establishment response may contain multi-access session control information, including information such as traffic splitting mode and traffic splitting function.

[0339] The S807, SMF+PGW-C network element and the UPF+PGW-C network element establish an N4 connection.

[0340] The S808 and SMF+PGW-C network elements send a session creation response to the service gateway.

[0341] Correspondingly, the service gateway receives a Create Session Response from the SMF+PGW-C network element. This Create Session Response may include a PDU session type of Non-IP.

[0342] S809, The service gateway sends a session creation response to the MME.

[0343] Accordingly, the MME receives a session creation response from the service gateway. This session creation response may include a PDN type of Non-IP.

[0344] The S810 and MME send an initial context setting request to the access network equipment.

[0345] Accordingly, the access network device receives an Initial Context Setup Request from the MME. This Initial Context Setup Request includes the PDN type: Non-IP.

[0346] S811, The access network device sends an RRC connection reconfiguration message to the UE.

[0347] Accordingly, the UE receives an RRC connection reconfiguration message from the access network device. This RRC connection reconfiguration message may contain an attach accept message. This attach accept message may include a PDN type of Non-IP.

[0348] S812, the UE sends an RRC connection reconfiguration complete message to the access network device.

[0349] Correspondingly, the access network device receives an RRC Connection Reconfiguration Complete message from the UE.

[0350] S813, The access network device sends an initial context setting response to the MME.

[0351] Accordingly, the MME receives an Initial Context Setup Response from the access network device. This Initial Context Setup Response includes the TEID of the access network device and the access network device address used for downlink traffic on the S1_U reference point.

[0352] S814, the UE sends a direct transmission message to the access network device.

[0353] Accordingly, the access network device receives a Direct Transfer message from the UE. This Direct Transfer message may include an Attach Complete message. This Attach Complete message may include the EPS holder identity, NAS serial number, NAS-MAC, etc.

[0354] S815, the access network device forwards the attach complete message to the MME.

[0355] Optionally, the access network device forwards the attach completion message to the MME via uplink NAS transmission messages.

[0356] S816, MME sends a modify bearer request to the service gateway.

[0357] Correspondingly, the serving gateway receives a modify bearer request from the MME. The MME can send the modify bearer request after receiving the initial context response in S813 and the attach completion message in S815. This modify bearer request may include the EPS bearer identity, access network device address, access network device TEID, handover indication, presence reporting area information, RAT type, and a message reporting the LTE-M RAT type to the PGW, etc.

[0358] S817a: The service gateway sends a modify bearer request to the SMF+PGW-C network element.

[0359] Correspondingly, the SMF+PGW-C network element receives a modify bearer request from the serving gateway.

[0360] The S817b and SMF+PGW-C network elements send a modify bearer response to the serving gateway.

[0361] Correspondingly, the service gateway receives the modified bearer response from the SMF+PGW-C network element.

[0362] S818, The service gateway sends a modified bearer response to the MME.

[0363] S819, SMF network element sends N1N2 message to AMF network element to transmit message.

[0364] Correspondingly, the AMF network element receives the N1N2 message transmission message from the SMF network element. Optionally, the N1N2 message transmission message includes information such as a session identifier and N2 SM information. This N2 SM information can be sent by the V-SMF network element to a non-3GPP access gateway device (e.g., the N3IWF network element in Figure 4) through the AMF network element. In this application, N3IWF is short for non-3GPP interworking function. The N2 SM information may include information such as the tunnel endpoint identifier of the UPF network element, which is sent to the N3IWF network element to tell it where the uplink data should be sent (which can be understood as the destination address of the uplink data). This message may not include the N1 session management container (because the information to be sent to the UE has already been sent through the access network device).

[0365] The S820 and AMF network elements send an N2 PDU session request to the N3IWF network element.

[0366] Correspondingly, the N3IWF network element receives an N2 PDU session request from the AMF network element. This N2 PDU session request may carry N2SM information.

[0367] The S821 and N3IWF network elements establish an IP security sub-security association with the UE for transmitting user plane data.

[0368] During this process, the N3IWF network element will assign the IP address (UP_IP_ADDRESS) of the IPSec Child SA to the UE. That is, when the UE needs to send uplink data, the destination IP address should be set to this UP_IP_ADDRESS in the internal IP protocol stack, while the source IP address is the "inner" address assigned during registration. The number of IPSec Child SAs established between the UE and the N3IWF network element, and which QoS flow data is transmitted in each IPSec Child SA, are determined based on the N3IWF network element's policies and configuration.

[0369] The S822 and N3IWF network elements send N2 PDU session responses to the AMF network element.

[0370] Correspondingly, the AMF network element receives the N2 PDU session response from the N3IWF network element. This N2 PDU session response may carry the tunnel endpoint identifier on the N3IWF network element side (which will subsequently be sent to the UPF network element via the AMF and SMF network elements). This information is used to tell the UPF network element where the downlink data should be sent (which can be understood as the destination address of the downlink data through a non-3GPP access path).

[0371] S823, the AMF network element sends a PDU session update session context request to the SMF network element.

[0372] Correspondingly, the SMF network element receives a PDU session update session context request from the AMF network element. This PDU session update session context request includes messages sent by the N3IWF network element, i.e., messages sent by the N3IWF network element in S420.

[0373] S824 and SMF network elements send the AN tunnel endpoint identification information from the N3IWF network element side to the UPF network element through the N4 session modification procedure.

[0374] S825, SMF network element sends PDU session update session context response to AMF network element.

[0375] Since the MA PDU session requires separate session establishment procedures on both the 3GPP access side and the non-3GPP access side (i.e., the UE needs to send session establishment requests on both the 3GPP and non-3GPP sides respectively), Figure 8 only shows an example diagram of establishing the user plane path first on the 3GPP side and then on the non-3GPP side. Establishing an MA PDU session does not necessarily require it to be established on the 3GPP side first; therefore, the schematic diagram for establishing the user plane first on the non-3GPP side and then on the 3GPP side is similar to the above diagram, the difference being that the user plane path is first established through the non-3GPP access gateway, and then through the 3GPP access network equipment.

[0376] In this embodiment, the UE generates a first attach request when a first condition is met; this enables the MPQUIC-E function in EPS scenarios, thereby establishing an MA PDU session. Furthermore, this method enhances the UE's functionality without requiring enhancements to other network elements, making it simple to implement.

[0377] Figure 9 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 9 is applicable to 5G roaming scenarios switching EPS scenarios. As shown in Figure 9, the method includes:

[0378] 901. The AMF network element sends a session context request to the second core network element.

[0379] Correspondingly, the second core network element receives a session context request from the AMF network element. For example, the session context request is an Nsmf_PDUSession_Context Request. The session context request includes a first identifier. Optionally, the first identifier is an SM context ID. The second core network element can be a V-SMF network element or an SMF+PGW-C network element.

[0380] 902. The second core network element determines that the MA PDU session type corresponding to the first identifier is Ethernet.

[0381] The second core network element determines that the MA PDU session type corresponding to the first identifier is Ethernet by: the second core network element searching for the corresponding MA PDU session type based on the first identifier.

[0382] 903. The second core network element sends a session context response to the AMF network element.

[0383] The session context response includes an SM context container. This SM context container contains a PDU session type. The PDU session type is either IPv4 or IPv6.

[0384] Step 903 can be replaced by: If MPQUIC-E is enabled for the MA PDU Session, the SMF+PGW-C (in non-roaming case) or the V-SMF (in roaming case) sets the value of PDU Session Type to IPv4 or IPv6 in the SM Context container sent to the AMF.

[0385] In one possible implementation, the second core network element can be a V-SMF network element; the PDU session type in the SM context container sent by the V-SMF network element to the AMF network element is set to the PDU session type received from the H-SMF network element: IPv4 or IPv6.

[0386] In one possible implementation, the second core network element can be a V-SMF network element; the PDU session type in the SM context container sent by the V-SMF network element to the AMF network element is set to the PDU session type converted from the transport resource type received from the H-SMF network element: IPv4 or IPv6: IPv4 or IPv6.

[0387] In one possible implementation, the second core network element can be an SMF+PGW-C network element; the SMF+PGW-C network element directly puts the PDU session type: IPv4 or IPv6 into the SM context container.

[0388] In this embodiment, the second core network element sends a session context response, which includes a PDU session type of IPv4 or IPv6; thereby enabling the MPQUIC-E function to be enabled when switching from a 5G roaming scenario to an EPS scenario, and thus establishing an MA PDU session.

[0389] Figure 10 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 10 is an example of the method in Figure 9. Figure 10 shows the complete process of establishing an MA PDU session in a 5G roaming scenario handover EPS scenario. As shown in Figure 10, the method includes:

[0390] S1000 establishes PDU sessions and QoS flows in the 5G core network.

[0391] S1000 is optional.

[0392] S1001 and NG-RAN send handover requests to AMF network elements.

[0393] Correspondingly, the AMF network element receives a handover required request from the NG-RAN. Optionally, this handover required request includes the target eNB ID, SM N2 Info(list), and PDU session IDs. In one possible implementation, the NG-RAN sends this handover required request to the AMF network element after determining that the UE is to hand over to the evolved universal terrestrial radio access network (E-UTRAN).

[0394] S1002a, the AMF network element sends a PDU session context request to the V-SMF network element.

[0395] Correspondingly, the V-SMF network element receives a PDU session context request from the AMF network element. For example, this PDU session context request is an Nsmf_PDUSession_Context Request. This PDU session context request includes the SM context ID, i.e., the first identifier mentioned above. S1002a is an example of step 901 in Figure 9, the V-SMF network element is an example of the second core network element in Figure 9, and the PDU session context request is an example of the session context request in Figure 9.

[0396] S1002a can be replaced by: The AMF network element sending a PDU session context request to the SMF+PGW-C network element. This PDU session context request includes the SM context ID, i.e., the first identifier mentioned above.

[0397] The S1002b and V-SMF network elements determine the corresponding MA PDU session type as Ethernet based on the SM context ID.

[0398] S1002b is an example of step 902 in Figure 9.

[0399] S1002c and V-SMF network elements send PDU session context responses to AMF network elements.

[0400] Correspondingly, the AMF network element receives a PDU session context response from the V-SMF network element. This PDU session context response includes an SM context container. The SM context container includes the PDU session type. The PDU session type is either IPv4 or IPv6. S1002c is an example of step 903 in Figure 9, the V-SMF network element is an example of the second core network element in Figure 9, and the PDU session context response is an example of the session context response in Figure 9.

[0401] In one possible implementation, in a 5G roaming to 4G scenario, the PDU session type in the SM context container sent by the V-SMF network element to the AMF network element is set to the PDU session type received from the H-SMF network element: IPv4 or "IPv6".

[0402] In one possible implementation, in a 5G roaming to 4G scenario, the PDU session type in the SM context container sent by the V-SMF network element to the AMF network element is set to the PDU session type converted from the transport resource type received from the H-SMF network element: IPv4 or IPv6: IPv4 or IPv6.

[0403] The S1002c can be replaced by the SMF+PGW-C network element sending a PDU session context response to the AMF network element. This PDU session context response includes an SM context container. The PDU session type included in this SM context container is either IPv4 or IPv6. The SMF+PGW-C network element can directly place the PDU session type (IPv4 or IPv6) into the SM context container.

[0404] S1003 and AMF network elements send migration requests to MME.

[0405] Accordingly, the MME receives a relocation request from the AMF network element. Optionally, the relocation request includes the parameter MME UE context. The MME UE context may include the UE context and the bear context. The bear context includes the PDN type.

[0406] S1004, MME sends a session creation request to the service gateway.

[0407] Accordingly, the service gateway receives a Create Session Request from the MME. For example, the MME sends a Create Session Request for each PDN connection to the service gateway. Optionally, this Create Session Request includes the bear context.

[0408] S1005, The service gateway sends a session creation response to the MME.

[0409] Correspondingly, the MME receives a Create Session Response from the Serving Gateway. For example, the Serving Gateway sends a Create Session Response to the MME for each PDN connection. The Serving Gateway can assign a Serving Gateway address and TEID (one TEID per bearer) to uplink traffic on the S1_U reference point. The Serving Gateway sends a Create Session Response (Serving Gateway address and uplink TEID(s)) message to the MME.

[0410] S1006, MME sends a handover request to E-UTRAN.

[0411] Accordingly, the E-UTRAN receives a handover request from the MME. This handover request may include parameters such as the UE context.

[0412] S1007, E-UTRAN sends a handover response to MME.

[0413] Correspondingly, the MME receives a handover request ACK from the E-UTRAN.

[0414] S1008 and MME send migration responses to AMF network elements.

[0415] Correspondingly, the AMF network element receives a migration response from the MME. This migration response may include one or more of the following: cause, target to source transparent container, serving gateway change indication, EPS bearer setup list, addresses, and TEIDs.

[0416] S1009a and AMF network elements send a handover command to the source NG-RAN.

[0417] Correspondingly, the source NG-RAN receives a handover command from the AMF network element. Optionally, this handover command includes a transparent container, data forwarding tunnel information, and QoS flows for data forwarding. The transparent container may include radio aspect parameters established by the target access network device during the preparation phase.

[0418] S1009b: The source NG-RAN sends a handover command to the UE.

[0419] Accordingly, the UE receives a handover command from the source NG-RAN. This handover command instructs the UE to switch to the target access network.

[0420] S1010a, the UE sends a handover completion message to the source E-UTRAN.

[0421] Correspondingly, the E-UTRAN receives a handover completion message from the UE.

[0422] S1010b and E-UTRAN send handover notification messages to the MME.

[0423] Accordingly, the MME receives a Handover Notify message. Optionally, this handover notification message includes the Tracking Area Identity (TAI) + E-UTRAN Cell Global Identifier (ECGI) and the local home network identifier.

[0424] S1010c and MME send migration completion notification messages to AMF network elements.

[0425] Correspondingly, the AMF network element receives a Relocation Complete Notification message from the MME.

[0426] S1010d and AMF network elements send migration completion confirmation messages to MME.

[0427] Correspondingly, the MME receives a Relocation Complete Ack message from the AMF network element. Optionally, a timer in the AMF network element starts to monitor when resources in the NG-RAN are released.

[0428] S1010e: When roaming on the home route, the AMF network element sends a session release request to the V-SMF network element.

[0429] Correspondingly, the V-SMF network element receives a session release request from the AMF network element. For example, this session release request is an Nsmf_PDUSession_ReleaseSMContext Request (V-SMF network element only indication).

[0430] S1011, MME sends a Modify Bearer Request to the Target Serving Gateway for each PDN connection (including PDN connections that need to be released).

[0431] Correspondingly, the target service gateway receives a Modify Bearer Request from the MME.

[0432] S1012. The service gateway sends a modify bearer request to the SMF+PGW-C network element.

[0433] S1013, SMF+PGW-C network element executes N4 session modification procedure.

[0434] S1014, the SMF+PGW-C network element sends a modify bearer response to the serving gateway.

[0435] Correspondingly, the service gateway receives a Modify Bearer Response from the SMF+PGW-C network element.

[0436] S1015, The service gateway returns a modified bearer response to the MME.

[0437] Accordingly, the MME receives a Modify Bearer response from the serving gateway. This Modify Bearer response may include the address of the serving gateway and the uplink service TEID.

[0438] S1016, UE initiates the tracking area update process.

[0439] S1017, PCF network element triggers SMF+PGW-C network element to initiate dedicated bearer activation process.

[0440] If PCC is deployed, the PCF network element can decide to re-provide the previously deleted PCC rules to the SMF+PGW-C network element, thereby triggering the SMF+PGW-C network element to initiate the dedicated bearer activation process.

[0441] S1018, the AMF network element sends a UE context release command / completion to the NG-RAN.

[0442] In this embodiment, if the V-SMF network element receives a PDU session type of Ethernet from the UE, the V-SMF network element sets the value of "PDU session type" in the N2 SM information to IPv4 or IPv6. Switching EPS in 5G / roaming scenarios can enable MPQUIC-E.

[0443] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 11 is applicable to a UE switching from an EPS scenario to a roaming scenario. As shown in Figure 11, the method includes:

[0444] 1101. The AMF network element sends the first message to the first core network element.

[0445] Correspondingly, the first core network element receives the first message from the AMF network element. For example, the first message is Nsmf_PDUSession_CreateSMComtext Required. Optionally, the first message carries the UE EPS PDN connection.

[0446] 1102. If the first core network element determines that the UE is switching from EPS to a roaming scenario based on the first message, and the second core network element does not support providing the PDU session type as IP in the N2 SM information, it initiates the deactivation of the 3GPP side user plane connection process.

[0447] For MA PDU sessions of type "Ethernet", when a UE hands over from E-UTRAN / EPS to NR / 5GS in a roaming scenario, if the V-SMF does not support providing PDU Session type as "IP" in the N2 SM information to NG-RAN (for ROHC), then the SMF+PGW-C network element shall initiate the CN-initiated deactivation of UP connection procedure over 3GPP access.

[0448] In one possible implementation, when the first core network element determines that the UE is switching from EPS to a roaming scenario based on the first message, it further determines whether the second core network element supports providing PDU session type as IP in the N2 SM information when determining the second condition. If the second core network element does not support providing PDU session type as IP in the N2 SM information, it initiates the deactivation of the 3GPP-side user plane connection process. Optionally, the second condition includes: before the handover (i.e., before the UE switches from EPS to a roaming scenario); the 4G leg accesses via 3GPP; the MPQUIC-E offloading function has been started before the handover; and the 3GPP leg switches from EPS to a roaming scenario.

[0449] In this embodiment of the application, when MPQUIC-E is enabled in the MA PDU session established through 3GPP access in EPC, network behavior is specified for EPS to roaming handover.

[0450] Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application. The method in Figure 12 is an example of the method in Figure 11. As shown in Figure 12, the method includes:

[0451] S1200 and UE establish PDN connection in 4G EPC.

[0452] S1201, E-UTRAN decision initiates the switch from EPS to roaming.

[0453] S1202, E-UTRAN sends a handover request to MME.

[0454] Correspondingly, the MME receives a handover requirement from the E-UTRAN.

[0455] S1203, MME sends a forward migration request to the initial AMF network element.

[0456] Accordingly, the initial AMF network element receives a forward relocation request from the MME. This forward relocation request includes the MME UE context. The MME UE context may include EPS bearer contexts. These EPS bearer contexts may include PDN type: ethernet, ATSSS capability: MPQUIC-E function.

[0457] S1204. The initial AMF network element sends the first message to the SMF+PGW-C network element.

[0458] Accordingly, the SMF+PGW-C network element receives the first message from the initial AMF network element. For example, this first message is Nsmf_PDUSession_CreateSMContext Required. This first message may include the UE EPS PDN connection. S1204 is executed for each PDN Connection and corresponding SMF+PGW-C address / ID in the UE context of the initial AMF network element received in S1203. The SMF network element finds the corresponding PDU session based on the EPS bearer context.

[0459] If the S1205 and SMF+PGW-C network elements determine that the UE is switching from EPS to a roaming scenario based on the first message, and if the V-SMF network element does not support providing the PDU session type as IP in the N2 SM information, it will initiate the deactivation of the 3GPP side user plane connection process.

[0460] The SMF+PGW-C network element can determine whether the V-SMF network element supports providing PDU session type as IP in the N2 SM information through the NRF network element.

[0461] S1205 can be replaced with: For MA PDU sessions of type "Ethernet", when a UE hands over from E-UTRAN / EPS to NR / 5GS in a roaming scenario, if the V-SMF does not support providing PDU Session type as "IP" in the N2 SM information to NG-RAN (for ROHC), then the SMF+PGW-C shall initiate the CN-initiated deactivation of UP connection procedure over 3GPP access.

[0462] In this embodiment of the application, when MPQUIC-E is enabled in the MA PDU session established through 3GPP access in EPC, network behavior is specified for EPS to roaming handover.

[0463] It should be understood that, unless otherwise specified or logically conflicting, the terminology and / or descriptions in the various embodiments of this application are consistent and can be referenced interchangeably. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships. The above embodiments describe how the network (core network) determines the associated UE policy and AM policy for the two UEs included in a dual-directional device under different scenarios. The technical solution provided by this application can be applied to scenarios where one or both UEs in a dual-directional device access the device through roaming, as well as scenarios where both UEs in a dual-directional device access the device through non-roaming. In practical applications, the above embodiments can be combined with each other.

[0464] It should also be understood that the above embodiments are mainly illustrated using devices in existing network architectures as examples. It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0465] It is understood that the methods and operations implemented by devices (such as AMF1, AMF2, UDM, PCF, etc.) in the above-described method embodiments can also be implemented by components (such as chips or circuits) that can be used in the devices.

[0466] It is also understood that some optional features in the various embodiments of this application may not depend on other features in some scenarios, or may be combined with other features in some scenarios, without limitation.

[0467] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0468] The structure of a communication device that can implement the communication method provided in the embodiments of this application is described below with reference to the accompanying drawings. Only a brief description of the communication device is given below; for details of the implementation, please refer to the description of the method embodiments above, which will not be repeated hereafter.

[0469] Figure 13 is a schematic diagram of a communication device 1300 provided in an embodiment of this application. This communication device 1300 can correspondingly implement the functions or steps implemented by the first core network element in the above-described method embodiments, the functions or steps implemented by the second core network element in the above-described method embodiments, and the functions or steps implemented by the UE in the above-described method embodiments. The communication device may include a processing module 1310 and a transceiver module 1320. In one possible implementation, a storage unit may also be included, which can be used to store instructions (code or program) and / or data. The processing module 1310 and the transceiver module 1320 can be coupled to the storage unit. For example, the processing module 1310 can read instructions (code or program) and / or data from the storage unit to implement the corresponding method. The above-described units can be set independently, or partially or completely integrated. For example, the transceiver module 1320 may include a transmitting module and a receiving module. The transmitting module can be a transmitter, and the receiving module can be a receiver. The entity corresponding to the transceiver module 1320 can be a transceiver circuit, such as a transceiver or a communication interface.

[0470] In some possible implementations, the communication device 1300 can correspondingly implement the behavior and functions of the first core network element in the above method embodiments. For example, the communication device 1300 can be the first core network element, or it can be a component (e.g., a chip or circuit) applied in the first core network element. It should be noted that the H-SMF network element and SMF+PGW-C network element mentioned above belong to the first core network element. The transceiver module 1320 can, for example, be used to execute all the receive or transmit operations performed by the first core network element in the embodiments of Figures 3 to 12. The processing module 1310 can, for example, be used to execute all the operations performed by the first core network element in the embodiments of Figures 3 to 12 except for the receive and transmit operations.

[0471] In some possible implementations, the communication device 1300 can correspondingly implement the behavior and functions of the second core network element in the above method embodiments. For example, the communication device 1300 can be a second core network element, or it can be a component (e.g., a chip or circuit) applied in the second core network element. It should be noted that the above-mentioned V-SMF network element belongs to the first core network element. The transceiver module 1320 can, for example, be used to perform all the receive or transmit operations performed by the second core network element in the embodiments of Figures 3 to 12. The processing module 1310 can, for example, be used to perform all the operations performed by the second core network element in the embodiments of Figures 3 to 12 except for the receive and transmit operations.

[0472] In some possible implementations, the communication device 1300 can correspondingly implement the behavior and functions of the UE in the above method embodiments. For example, the communication device 1300 can be the UE, or it can be a component (e.g., a chip or circuit) applied in the UE. The transceiver module 1320 can, for example, be used to perform all the receive or transmit operations performed by the UE in the embodiments of FIG4 to FIG12. The processing module 1310 can, for example, be used to perform all the operations performed by the UE in the embodiments of FIG4 to FIG12 except for the receive and transmit operations.

[0473] Figure 14 is a schematic diagram of another device 140 provided in an embodiment of this application. The device in Figure 14 can be the first core network element or a chip used in the first core network element, or it can be the second core network element or a chip used in the second core network element, or it can be the UE or a chip used in the UE. As shown in Figure 14, the device 140 includes a processing circuit 1410 and a transceiver circuit 1420.

[0474] In some embodiments of this application, the processing circuit 1410 and the transceiver circuit 1420 can be used to perform functions or operations performed by the AMF1. For example, the transceiver circuit 1420 is used to perform all receive or transmit operations performed by the AMF1 in the embodiments of Figures 2 to 10. For example, the processing circuit 1410 is used to perform all operations performed by the AMF1 in the embodiments of Figures 2 to 10, except for the receive / transmit operations.

[0475] In some embodiments of this application, the processing circuit 1410 and the transceiver circuit 1420 can be used to perform functions or operations performed by the first core network element. For example, the transceiver circuit 1420 is used to perform all receive or transmit operations performed by the first core network element in the embodiments of Figures 3 to 12. For example, the processing circuit 1410 is used to perform all operations performed by the first core network element in the embodiments of Figures 3 to 12, except for the receive / transmit operations.

[0476] In some embodiments of this application, the processing circuit 1410 and the transceiver circuit 1420 can be used to perform functions or operations performed by the second core network element. For example, the transceiver circuit 1420 is used to perform all receive or transmit operations performed by the second core network element in the embodiments of Figures 3 to 12. For example, the processing circuit 1410 is used to perform all operations performed by the second core network element in the embodiments of Figures 3 to 12, except for the receive / transmit operations.

[0477] In some embodiments of this application, the processing circuit 1410 and the transceiver circuit 1420 can be used to perform functions or operations performed by the UE. For example, the transceiver circuit 1420 is used to perform all the receive or transmit operations performed by the UE in the embodiments of FIG3 to FIG12. For example, the processing circuit 1410 is used to perform all operations performed by the UE in the embodiments of FIG3 to FIG14, except for the receive / transmit operations.

[0478] In one possible implementation, the transceiver circuit 1420 includes at least one transceiver, and the processing circuit 1410 includes at least one processor, or at least one processor with circuitry for processing or control.

[0479] A transceiver is used for communication with other devices / appliances via a transmission medium. The processor utilizes the transceiver to send and receive data and / or signaling, and to implement the methods described in the above-described method embodiments. The processor can implement the functions of processing module 1310, and the transceiver can implement the functions of transceiver module 1320. Optionally, the transceiver may include radio frequency (RF) circuitry and an antenna. The RF circuitry is primarily used for converting baseband signals to RF signals and processing RF signals. The antenna is primarily used for sending and receiving RF signals in the form of electromagnetic waves.

[0480] Optionally, device 140 may further include at least one memory for storing program instructions and / or data. The memory and processor are coupled. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor may operate in conjunction with the memory. The processor may execute program instructions stored in the memory. At least one of the at least one memory may be included in the processor.

[0481] The processor can read software programs from memory, interpret and execute the instructions of the software programs, and process the data of the software programs. When data needs to be transmitted wirelessly, the processor performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit then performs RF processing on the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to device 140, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal back into data and processes the data.

[0482] In another implementation, the aforementioned radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of device 140.

[0483] The specific connection medium between the transceiver, processor, and memory described above is not limited in the embodiments of this application.

[0484] In the embodiments of this application, the processor can be one of the following devices: a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or all or part of the circuitry in the aforementioned devices used for processing functions. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules within the processor.

[0485] In one possible implementation, the processing circuit 1410 includes at least one logic circuit, and the transceiver circuit 1420 includes at least one interface. The processing module 1310 in FIG. 13 can be implemented using logic circuits, and the transceiver module 1320 in FIG. 13 can be implemented using an interface. The logic circuit can be a chip, processing circuit, integrated circuit, or system-on-chip (SoC) chip, etc., and the interface can be a communication interface, input / output interface, etc. In this embodiment, the logic circuit and the interface can also be coupled to each other. The specific connection method of the logic circuit and the interface is not limited in this embodiment.

[0486] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed on a computer, cause the computer to perform the methods described in the above embodiments.

[0487] This application also provides a computer program product, which includes instructions or a computer program that, when run on a computer, causes the methods in the above embodiments to be executed.

[0488] This application also provides a communication system, including the aforementioned first core network element and the aforementioned second core network element.

[0489] This application also provides a chip, which includes: a communication interface and a processor; the communication interface is used for signal transmission and reception of the chip; the processor is used to execute computer program instructions, causing a communication device including the chip to perform the methods as described in the above embodiments.

[0490] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0491] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0492] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0493] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A communication method characterized by comprising: The method is applied to a first core network element, and the method comprises: receiving a first session establishment request, the first session establishment request comprising first access traffic steering, switching, splitting, ATSSS, capability and a protocol data unit, PDU, session type, the first ATSSS capability comprising a multi-path quick user datagram protocol internet connection, MPQUIC-E, function and an ATSSS lower layer function, the PDU session type being Ethernet; sending a policy association establishment request, the policy association establishment request comprising second ATSSS capability, the second ATSSS capability being the ATSSS lower layer function. The method of claim 1, wherein The first core network element is a session management function, SMF, network element in a home public land mobile network, HPLMN, of a user equipment, UE, to which the first session establishment request is associated; and the receiving the first session establishment request comprises: receiving the first session establishment request from a SMF network element in a visited public land mobile network, VPLMN, of the UE. The method of claim 1, wherein The first session establishment request is from a service gateway, and the first core network element has a session management function, SMF, network element and a control plane function of a packet data network gateway, PGW. A communication method characterized by comprising: The method is applied to a first core network element, and the method comprises: receiving a first session establishment request, the first session establishment request comprising first access traffic steering, switching, splitting, ATSSS, capability and a protocol data unit, PDU, session type, the first ATSSS capability comprising a multi-path quick user datagram protocol internet connection, MPQUIC-E, function and an ATSSS lower layer function, the PDU session type being Ethernet; determining whether to enable the MPQUIC-E function for a multi-access, MA, PDU session associated with the first session establishment request according to whether a second core network element supports providing a PDU session type as Internet Protocol, IP, in session management, SM, information on an N2 interface. The method according to claim 4, characterized in that The method further comprises: in a case where it is determined not to enable the MPQUIC-E function for the PDU session, sending a policy association establishment request, the policy association establishment request comprising second ATSSS capability, the second ATSSS capability being the ATSSS lower layer function. The method according to claim 4 or 5, characterized in that The method further comprises: in a case where it is determined to enable the MPQUIC-E function for the PDU session, sending a first session establishment response to the second core network element, the PDU session type carried in the first session establishment response being Internet Protocol, IP. The method according to any one of claims 4 to 6, characterized in that The method further comprises: determining, by a network storage function, NRF, network element, whether the second core network element supports providing a PDU session type as IP in session management, SM, information on an N2 interface. The method according to any one of claims 4 to 7, characterized in that The first core network element is a session management function, SMF, network element in a Home Public Land Mobile Network, HPLMN, of a user equipment, UE, to which the first session establishment request, and the second core network element is a SMF network element in a visited public land mobile network, VPLMN, of the user equipment, UE; The receiving the first session establishment request comprises: receiving the first session establishment request from the second core network element. A communication method characterized by comprising: The method is applied to a second core network element, and the method comprises: sending a first session establishment request, the first session establishment request comprising first access traffic steering, switching, splitting ATSSS capability and a protocol data unit, PDU, session type, the first ATSSS capability comprising multi-path fast user datagram protocol internet connection, MPQUIC-E, function and ATSSS low layer function, and the PDU session type being Ethernet; receiving a first session establishment response from a first core network element, the PDU session type carried in the first session establishment response being IPv4 or IPv6. The method of claim 9, wherein The method further comprises: in a case where the PDU session type from a user equipment, UE, is Ethernet and the PDU session type from the first core network element is internet protocol, IP, sending an N1N2 messaging message, the N1N2 messaging message comprising N2 SM information, the PDU session type in the N2 SM information being IPv4 or IPv6. The method of claim 10, wherein The N1N2 messaging message further comprises an N1 SM container, the PDU session type in the N1 SM container being Ethernet. The method according to claim 10 or 11, characterized in that The first core network element is a session management function, SMF, element in a home public land mobile network, HPLMN. A communication method characterized by comprising: The method is applied to a user equipment, UE, and the method comprises: in a case where a first condition is met, generating a first attach request, the first attach request comprising protocol data unit, PDN, type and access traffic steering, switching, splitting, ATSSS, capability, the PDN type being non-IP, and the ATSSS capability comprising multi-path fast user datagram protocol internet connection, MPQUIC-E, function and ATSSS low layer function, the first condition comprising that the UE supports the MPQUIC-E function; sending the first attach request to an access network device. A communication method characterized by comprising: comprises: receiving a session context request from an access and mobility management function, AMF, element, the session context request comprising a first identity; determining that a multi-access, MA, protocol data unit, PDU, session type corresponding to the first identity is Ethernet; sending a session context response, the session context response comprising a session management, SM, context container, the SM context container comprising a PDU session type, the PDU session type being IPv4 or IPV6. The method of claim 14, wherein The PDU session type is determined according to a PDU session type from a first core network element; or The PDU session type is determined according to a transmission resource type from a first core network element; The first core network element is a session management function, SMF, element in a home public land mobile network, HPLMN, of a user equipment, UE, associated with the session context request. A communication method characterized by comprising: comprises: receiving a first message; According to the first message, if a second core network element does not support providing a protocol data unit (PDU) session type as Internet Protocol (IP) in N2 interface session management (SM) information in a case where a user equipment (UE) is handed over from an evolved packet system (EPS) to a roaming scenario, deactivation of a 3rd generation partnership project (3GPP) side user plane connection procedure is initiated. The method of claim 16, wherein The method further includes: Determining, by a network repository function (NRF) network element, whether the second core network element supports providing a PDU session type as IP in N2 interface session management (SM) information. A communication device, characterized by The apparatus includes a module or unit for implementing the method of any one of claims 1-17. A computer-readable storage medium, characterized by The computer readable storage medium stores a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method of any one of claims 1-17. A communication device, characterized by The apparatus includes a processor coupled with a memory, the memory to store a program or instructions that, when executed by the processor, cause the communication device to perform the method of any one of claims 1-17. A chip characterized by The apparatus includes: A communication interface for signal transceiving of the chip; A processor for executing computer program instructions, causing a communication device including the chip to perform the method of any one of claims 1-17. A computer program product, characterized in that The computer program product includes a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method of any one of claims 1-17. The computer program product includes a computer program, the computer program including program instructions that, when executed, cause a computer to perform the method of any one of claims 1-17.