MA PDU session processing method and user equipment thereof

Abstract

A method for handling a request for reactivation from a network for an MA PDU session with SSC mode 3 is proposed. When a UE receives a PDU session modification command message including 5GSM cause #39 "reactivation requested" for an existing MA PDU session, the UE processes the PDU session modification procedure requested by the network, and the UE re-initiates the UE-requested PDU session establishment procedure using a new MA PDU session ID. The UE determines how to proceed with the PDU session reestablishment procedure for a new MA PDU session based on different scenarios of UE registration and user plane resources of the existing MA PDU session, and / or also based on whether the PDU session modification command message is sent via a 3GPP access type or a non-3GPP access type. The present invention achieves the beneficial effect of ensuring service continuity.

Description

Technical Field

[0001] Embodiments of the present invention generally relate to wireless communications and, more particularly, to processing of multiple access PDU session reactivation requests. Background Art

[0002] Wireless communication networks have grown exponentially over the years. Long-term evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs due to a simplified network architecture. LTE systems, also known as 4G systems, also offer seamless integration with legacy wireless networks, such as GSM, CDMA, and universal mobile telecommunication systems (UMTS). In LTE systems, the evolved universal terrestrial radio access network (E-UTRAN) includes multiple evolved Node Bs (eNodeBs or eNBs) that communicate with multiple mobile stations, known as user equipment (UE). The 3rd generation partner project (3GPP) networks typically include a mix of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) committee has decided to focus future NGMN activities on defining the end-to-end requirements for 5G new radio (NR) systems.

[0003] In 5G / NR, a protocol data unit (PDU) session defines the association between the UE and the data network that provides the PDU connection service. In 4G / LTE, PDU session establishment is a parallel process to the PDN connection (bearer) process. Each PDU session is identified by a PDU session ID (PSI) and can include multiple QoS flows and QoS rules. Each PDU session can be established via a 5G access network (e.g., a 3GPP radio access network (RAN)) or via a non-3GPP access. The network / UE can initiate different PDU session processes, such as PDU session establishment, PDU session modification, and PDU session release, to manage PDU sessions.

[0004] Operators are looking for ways to balance data traffic between mobile networks and non-3GPP accesses in a way that is transparent to users and reduces mobile network congestion. In 5GS, UEs can be connected to 3GPP accesses and non-3GPP accesses simultaneously (using NAS signaling), so 5GS is able to take advantage of these multiple accesses to improve user experience and optimize traffic distribution across various accesses. Therefore, 3GPP introduced Multiple-Access (MA) PDU sessions in 5GS. MAPDU sessions can be configured to use one 3GPP access network or one non-3GPP access network at a time, or to use one 3GPP access network and one non-3GPP access network at the same time.

[0005] The support for session and service continuity (SSC) in the 5G system architecture enables addressing various continuity requirements of different applications / services of the UE. The SSC mode associated with a PDU session does not change during the life cycle of the PDU session. With SSC mode 3, changes in the user plane are visible to the UE and the network ensures that the UE does not lose connectivity. A connection is established through a new PDU session anchor point before terminating the previous connection for better service continuity. For IPv4 or IPv6 or IPv4v6 type cases, the IP address is not retained in this mode when the PDU session anchor changes. When the UE receives a PDU SESSION MODIFICATION COMMAND message including 5GSM cause #39 "reactivation requested", the session ID re-initiates the UE-requested PDU session establishment process. However, for an MA PDU session, after the UE processes a network-requested PDU session modification procedure (eg, processes a PDU SESSION RELEASE MODIFICATION message), it is not defined how the UE should re-initiate a UE-requested PDU session establishment procedure.

[0006] Seek solutions. Summary of the Invention

[0007] A method for handling a requested reactivation from the network for an MA PDU session with SSC mode 3 is proposed. Support for SSC in the 5G system architecture enables addressing various continuity requirements for different applications / services of the UE. With SSC mode 3, changes in the user plane are visible to the UE and the network ensures that the UE does not lose connectivity. A connection is established through a new PDU session anchor before terminating the previous connection for better service continuity. When the UE receives a PDU session modification command message including 5GSM cause #39 "reactivation requested" for an existing MA PDU session, the UE processes the network requested PDU session modification procedure and the UE re-initiates the UE requested PDU session establishment procedure using the new MA PDU session ID. The UE determines how to proceed with the PDU session reestablishment procedure for the new MA PDU session based on the different scenarios registered by the UE and the user plane resources of the existing MA PDU session, and / or also based on whether the PDU session modification command message is sent via a 3GPP access type or a non-3GPP access type.

[0008] In one embodiment, the UE maintains a first multi-access protocol data unit (MA PDU) session in a 5G system (5GS). The first MA PDU session has a first PDU session ID (PDU session ID, PSI). The selected session and service continuity (SSC) mode of the first MA PDU session is SSC mode 3. The UE receives a PDU session modification command message for the first MAPDU session. The PDU session modification command message indicates a request for reactivation and is received by the UE through a first access type. The UE sends a PDU session modification complete message in response to the PDU session modification command message. The UE determines one or more access types based on UE registration, user plane resources of the first MAPDU session and the first access type. The UE establishes a second MA PDU session with a second PSI. The UE initiates one or more PDU session establishment processes respectively through the determined one or more access types for establishing a second MAPDU session.

[0009] In another embodiment, a user equipment (UE) includes a PDU session processing circuit for maintaining a first MAPDU session in a 5G system. The first MA PDU session has a first PDU session ID, and the selected SSC of the first MA PDU session is SSC mode 3. The UE also includes a receiver for receiving a PDU session modification command message for the first MAPDU session. The PDU session modification command message indicates a request for reactivation and is received by the receiver via a first access type. The UE also includes a transmitter for sending a PDU session modification completion message in response to the PDU session modification command message. The UE further includes a control and configuration circuit for determining one or more access types based on UE registration, user plane resources of the first MAPDU session, and the first access type. The PDU session processing circuit is also used to establish a second MAPDU session with a second PSI, wherein the UE initiates one or more PDU session establishment processes respectively through the determined one or more access types to establish the second MAPDU session.

[0010] The present invention proposes a processing method for MAPDU session modification and a user equipment thereof, achieving the beneficial effect of ensuring service continuity.

[0011] Other embodiments and advantages are described in the detailed description below. This summary is not intended to define the invention. The invention is defined by the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings illustrate embodiments of the present invention, wherein like numerals indicate like components.

[0013] Figure 1 An exemplary 5G network supporting MA PDU session management and a method for handling MA PDU session modification with requested reactivation are shown according to one novel aspect.

[0014] Figure 2 A simplified block diagram of a UE and a network entity is shown according to an embodiment of the present invention.

[0015] Figure 3 The present invention provides a sequence flow between a UE and a 5GS for an MA PDU session modification procedure with a request for reactivation according to a novel aspect.

[0016] Figure 4 A first embodiment of a procedure for handling a MAPDU session modification with a request for reactivation is shown in accordance with one novel aspect.

[0017] Figure 5 A second embodiment of handling an MA PDU session modification procedure with a requested reactivation is shown in accordance with one novel aspect.

[0018] Figure 6 A third embodiment of handling an MA PDU session modification procedure with a requested reactivation is shown according to one novel aspect.

[0019] Figure 7 is a flow chart of a method for handling an MA PDU session modification procedure with a requested reactivation according to one novel aspect of the present invention. DETAILED DESCRIPTION

[0020] Reference will now be made in detail to some embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

[0021] Figure 1 An exemplary 5G network supporting MA PDU session management and a method for handling MA PDU session modification with a request for reactivation are shown according to one novel aspect. A 5G New Radio (NR) network 100 includes a user equipment (UE) 101, a 3GPP access 102 (e.g., a 3GPP radio access network (RAN)), a non-3GPP access 103 (e.g., a non-3GPP RAN), an access and mobility management function (AMF) 110, a session management function (SMF) 111, a non-3GPP interworking function (N3IWF) 112, a user plane function (UPF) 113, and a 5G core (5GC) data network 120. The AMF 110 communicates with a base station in the 3GPP access 102, the SMF 111, and the UPF 113 for access and mobility management of wireless access devices in the 5G network 100. The SMF 111 is primarily responsible for interacting with the decoupled data plane, creating, updating, and deleting PDU sessions, and managing session content with the UPF. The N3IWF 112 interfaces with the 5G core network control plane functions and is responsible for routing messages outside the 5G RAN.

[0022] In the Access Stratum (AS) layer, the RAN provides radio access to the UE 101 via a RAT. In the Non-Access Stratum (NAS) layer, the AMF 110 and SMF 111 communicate with the RAN and 5GC for PDU session management and access mobility management of wireless access devices in the 5G network 100. The 3GPP access 102 may include base stations (gNBs or eNBs) that provide radio access to the UE 101 via various 3GPP RANs, including 5G, 4G, and 3G / 2G. The non-3GPP access 103 may include access points (APs) that provide radio access to the UE 101 via non-3GPP RATs, including WiFi. The UE 101 can obtain access to the data network 120 through the 3GPP access 102, the AMF 110, the SMF 111, and the UPF 113. UE 101 can obtain access to data network 120 through non-3GPP access 103, N3IWF 112, AMF 110, SMF 111 and UPF 113. UE 101 can be equipped with a single radio frequency (RF) module or transceiver or multiple RF modules or transceivers (including receivers and transmitters) for services via different RATs / CNs. In some examples, UE 101 can be a smartphone, a wearable device, an Internet of Things (IoT) device, a tablet, etc.

[0023] In 5G, a PDU session defines the association between a UE and a data network that provides PDU connection services. Each PDU session is identified by a PDU session ID, and each PDU session can include multiple QoS flows and QoS rules. Each PDU session can be established over 3GPP RAN or non-3GPP access. 5G Session Management (5GSM) for PDU sessions over both 3GPP access and non-3GPP access is managed by AMF and SMF through NAS signaling. In 5GS, the UE can be connected to 3GPP access and non-3GPP access at the same time (using NAS signaling), so 5GS is able to take advantage of these multiple accesses to improve user experience and optimize traffic distribution across various accesses. Therefore, 3GPP introduced MA PDU sessions in 5GS. A MAPDU session uses one 3GPP access network or one non-3GPP access network at a time, or one 3GPP access network and one non-3GPP access network at the same time.

[0024] The support for SSC in the 5G system architecture can address the various continuity requirements of different applications / services of the UE. The SSC mode associated with a PDU Session does not change during the lifetime of the PDU Session. With SSC Mode 3, changes in the user plane are visible to the UE, and the network ensures that the UE does not lose connectivity. A connection is established through a new PDU Session Anchor before terminating the previous connection to achieve better service continuity. For IPv4 or IPv6 or IPv4v6 types, the IP address is not retained in this mode when the PDU Session Anchor changes. When the UE receives a PDU Session Modification Command message including 5GSM cause #39 "reactivation requested", the UE processes the network-requested PDU Session Modification procedure, and the UE re-initiates the UE-requested PDU Session Establishment procedure using the new PDU Session ID. However, for MA PDU Sessions, it is unclear how the UE should re-initiate the UE-requested PDU Session Establishment procedure after the network-requested PDU Session Modification procedure.

[0025] According to one novel aspect, when UE 101 receives a PDU session modification command with "reactivation request" via a first access type (130), UE 101 determines how to proceed with the PDU session reestablishment process based on different scenarios. In a first scenario (141), the MA PDU has user plane resources established in both 3GPP and non-3GPP, and UE 101 is registered in the same Public Land Mobile Network (PLMN) via 3GPP and non-3GPP, so UE 101 sends a PDU session establishment request (PDU SESSION ESTABLISHMENT REQUEST) message (151) via the first access type. In a second scenario (142), the MA PDU has user plane resources established in both 3GPP and non-3GPP, and UE 101 is registered in different PLMNs via 3GPP and non-3GPP, so UE 101 sends a first PDU session establishment request message via the first access type and a second PDU session establishment request message (152) via the second access type. In the third scenario (143), the MA PDU has user plane resources established through a single access type, so the UE 101 sends a PDU Session Establishment Request message (153) through the same single access type (which may be the same as or different from the first access type).

[0026] Figure 2A simplified block diagram of a wireless device (e.g., UE 201 and network entity 211) according to an embodiment of the present invention is shown. The network entity 211 can be a base station and / or an AMF / SMF. The network entity 211 has an antenna 215 for sending and receiving radio signals. The RF transceiver module 214 coupled to the antenna receives an RF signal from the antenna 215, converts the RF signal into a baseband signal and sends the baseband signal to the processor 213. The RF transceiver module 214 also converts the baseband signal received from the processor 213 into an RF signal and sends it to the antenna 215. The processor 213 processes the received baseband signal and calls different functional modules to perform functions in the base station 211. The memory 212 stores program instructions and data 220 to control the operation of the base station 211. In Figure 2 In the example of FIG, the network entity 211 further includes a protocol stack 280 and a set of control function modules and circuit sets 290. The protocol stack 280 includes a NAS layer for communicating with the AMF / SMF / MME entity connected to the core network, a Radio Resource Control (RRC) layer for high-layer configuration and control, a Packet Data Convergence Protocol (PDCP) / Radio Link Control (RLC) layer, a Media Access Control (MAC) and a Physical (PHY) layer. In one example, the control function modules and circuits 290 include a PDU session processing circuit 291 for handling PDU establishment, modification and release processes, and a configuration and control circuit 292 for providing different parameters to configure and control relevant functions of the UE (including mobility management and PDU session management).

[0027] Similarly, UE 201 has memory 202, processor 203, and RF transceiver module 204. RF transceiver module 204 is coupled to antenna 205, receives RF signals from antenna 205, converts the RF signals to baseband signals, and transmits the baseband signals to processor 203. RF transceiver module 204 also converts baseband signals received from processor 203 into RF signals and transmits them to antenna 205. Processor 203 processes the received baseband signals and invokes various functional modules and circuits to perform the functional features of UE 201. Memory 202 stores data and program instructions 210 to be executed by the processor to control the operation of UE 201. Suitable processors include, for example, special-purpose processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and other types of integrated circuits (ICs), and / or state machines. The processor in association with software may be used to implement and configure the features of UE 201 .

[0028] UE 201 also includes a protocol stack 260 and a set of control functional modules and circuits 270. Protocol stack 260 includes a NAS layer for communicating with the AMF / SMF / MME entity connected to the core network, an RRC layer for high-level configuration and control, a PDCP / RLC layer, a MAC layer, and a PHY layer. The control functional modules and circuits 270 can be implemented and configured using software, firmware, hardware, and / or a combination thereof. When executed by a processor using program instructions contained in a memory, the control functional modules and circuits cooperate to enable UE 201 to perform the embodiments and functional tasks and features in the network.

[0029] In one example, the control function module and circuit 270 includes a PDU session processing circuit 271 that performs MA PDU session establishment, modification, and release procedures with the network, and a configuration and control circuit 272 that processes configuration and control parameters for mobility management and session management. When the UE receives a "reactivate request" PDU session modification command for an existing MA PDU, the UE completes the network-requested PDU session modification procedure and also initiates a UE-requested PDU session establishment procedure to establish a new MA PDU session for service continuity.

[0030] Figure 3is a sequence flow between a UE and a 5GS for a MA PDU session modification procedure with requested reactivation according to a novel aspect. In step 311, UE 301 registers with the 5GS network via a 3GPP access type. In step 312, UE 301 registers with the 5GS network via a non-3GPP access type. Note that UE 301 can be registered in the same PLMN via 3GPP and non-3GPP or in two different PLMNs via 3GPP and non-3GPP, respectively. In step 313, UE 301 initiates a UE-requested PDU session establishment procedure, and an MA PDU session with PSI=1 is established between UE 301 and the 5GS network (e.g., using UPF#1). User plane resources for the MAPDU can be established on both 3GPP access and non-3GPP access, or only on 3GPP access, or only on non-3GPP access. In step 321, UE 301 performs uplink and downlink data communication through UPF#1 through 3GPP access or non-3GPP access, or both 3GPP and non-3GPP access types.

[0031] The support for session and service continuity in the 5G system architecture can address the various continuity requirements of different applications / services of the UE. The SSC mode associated with the PDU session will not change during the life cycle of the PDU session. Using SSC mode 3, changes in the user plane are visible to the UE, and the network ensures that the UE does not lose connection. In step 331, UE 301 receives a PDU session modification command message from 5GS via the first access type, which PDU session modification command message includes 5GSM cause #39 "reactivation request". In step 332, UE301 sends a PDU session modification complete (PDU SESSIONMODIFICATION COMPLETE) message to 5GS.

[0032] In step 341, UE 301 initiates a UE-requested PDU session establishment process to establish another MA PDU session with PSI=2 between UE 301 and the 5GS network (e.g., using UPF#2). The new MA PDU session with PSI=2 should be associated with the current MA PDU session with PSI=1, and the PDU session type, SSC mode, Data Network Name (DNN) and Single-Network Slice Selection Assistance Information (S-NSSAI) should be set the same as the current MA PDU session with PSI=1. In step 351, UE 301 performs uplink and downlink data communication through 3GPP access or non-3GPP access, or both 3GPP and non-3GPP access types through UPF#2. In step 361, the current MA PDU session with PSI=1 is released. In one novel aspect, in step 341, UE 301 determines how to initiate a PDU session establishment process, e.g., determining on which access type to send one or more corresponding PDU session establishment request messages, based on 1) UE registration information, 2) current MA PDU user plane resources, and / or 3) the first access type of the PDU session modification command message received by the UE in step 331.

[0033] Figure 4 According to one novel aspect, a first embodiment of processing a MA PDU session modification procedure with a request for reactivation is shown. Figure 4In an embodiment, in step 411, a MAPDU session (PSI=1) (and its user plane resources) is established through both 3GPP and non-3GPP accesses, and UE 401 is registered in the same PLMN1 through 3GPP and non-3GPP. In step 412, UE 401 receives a PDU SESSION MODIFY COMMAND message through the first access (e.g., 3GPP), wherein the PDU SESSION MODIFY COMMAND message includes 5GSM cause #39 "reactivation requested". In step 413, UE 401 sends a PDU SESSION MODIFY COMPLETE message to the network. UE 401 then initiates a UE-requested PDU session establishment process based on the determined access type, e.g., 3GPP. In step 421, UE 401 sends a PDU SESSION ESTABLISHMENT REQUEST message to the network through 3GPP for establishing a MA PDU with PSI=2. In step 422, UE 401 receives a PDU SESSION ESTABLISHMENT ACCEPT message from the network. In step 431, a new MA PDU with PSI = 2 is established with the same parameters as the MA PDU with PSI = 1, and then the MA PDU with PSI = 1 is released. Note that since UE 401 is registered in the same PLMN1 via 3GPP and non-3GPP, new MAPDU sessions and user plane resources based on both access types can be established in a single step.

[0034] Figure 5 According to one novel aspect, a second embodiment of processing a MA PDU session modification procedure with a request for reactivation is shown. Figure 5In an embodiment, in step 511, an MA PDU session (PSI=1) (and its user plane resources) are established through both 3GPP and non-3GPP accesses, and UE 501 is registered in PLMN1 through 3GPP and in PLMN2 through non-3GPP. In step 512, UE 501 receives a PDU session modification command message through the first access (e.g., 3GPP), wherein the PDU session modification command message includes 5GSM cause #39 "reactivation requested". In step 513, UE 501 sends a PDU session modification complete message to the network. UE 501 then initiates a UE-requested PDU session establishment process based on the determined access type (e.g., 3GPP). In step 521, UE 501 sends a first PDU session establishment request (PDUSESSION ESTABLISHMENT REQUEST) message to the network through 3GPP to establish an MA PDU with PSI=2 and user plane resources in PLMN1. In step 522, UE 401 receives a PDU Session Establishment Accept message from the network. In step 523, UE 501 sends a second PDU Session Establishment Request message to the network via non-3GPP to establish a MA PDU with PSI = 2 and user plane resources in PLMN2. In step 524, UE 501 receives a PDU Session Establishment Accept message from the network. In step 531, a new MA PDU with PSI = 2 is established, which has the same parameters as the MA PDU with PSI = 1, and then the MA PDU with PSI = 1 is released.

[0035] Figure 6 A third embodiment of handling a MA PDU session modification procedure with a request for reactivation is shown according to one novel aspect. Figure 6In an embodiment, in step 611, an MA PDU session (PSI=1) (and its user plane resources) is established only through one access type (e.g., 3GPP), and UE 601 is registered in PLMN1. In step 612, UE 601 receives a PDU session modification command message through the access type (e.g., 3GPP or non-3GPP), wherein the PDU session modification command message includes 5GSM cause #39 "reactivation requested". In step 613, UE 601 sends a PDU session modification complete message to the network. UE 601 then initiates a UE-requested PDU session establishment process only through 3GPP based on the fact that the user plane resources of the current MA PDU session are established only through 3GPP access. In step 621, UE 601 sends a PDU session establishment request message to the network through 3GPP for establishing a new MA PDU with PSI=2 and user plane resources only through 3GPP. In step 622, UE 601 receives a PDU session establishment accept message from the network. In step 631, a new MA PDU with PSI=2 is created, which has the same parameters as the MA PDU with PSI=1, and then the MA PDU with PSI=1 is released.

[0036] Figure 7 7 is a flowchart of a method for processing an MA PDU session modification procedure with a request for reactivation according to a novel aspect of the present invention. In step 701, the UE maintains a first multiple access protocol data unit (MAPDU) session in a 5G system (5GS). The first MA PDU session has a first PDU session ID (PSI). The selected session and service continuity (SSC) mode of the first MA PDU session is SSC mode 3. In step 702, the UE receives a PDU session modification command message for the first MA PDU session. The PDU session modification command message indicates that reactivation is requested and the UE receives the PDU session modification command message via a first access type. In step 703, the UE sends a PDU session modification complete message in response to the PDU session modification command message. In step 704, the UE determines one or more access types based on UE registration, user plane resources of the first MA PDU session, and the first access type. In step 705, the UE establishes a second MA PDU session with a second PSI. The UE initiates one or more PDU session establishment procedures via the determined one or more access types, respectively, to establish the second MA PDU session.

[0037] Although the present invention has been described in conjunction with specific embodiments for illustrative purposes, it is not limited thereto. Therefore, various modifications, adaptations and combinations of the various features of the described embodiments may be implemented without departing from the scope of the invention as set forth in the appended claims.

Claims

1. A method for processing a multiple access protocol data unit session, comprising: The user equipment maintains a first multiple access protocol data unit session in the 5G system, wherein the first multiple access protocol data unit session has a first protocol data unit session identifier, and a session and service continuity mode selected by the first multiple access protocol data unit session is session and service continuity mode 3; receiving a protocol data unit session modification command message for the first multiple access protocol data unit session, wherein the protocol data unit session modification command message indicates a request for reactivation and is received by the user equipment via a first access type; sending a protocol data unit session modification complete message in response to the protocol data unit session modification command message; determining one or more access types based on user equipment registration, user plane resources of the first multiple access protocol data unit session, and the first access type; as well as A second multiple access protocol data unit session having a second protocol data unit session identifier is established, wherein the user equipment initiates one or more protocol data unit session establishment processes respectively through the determined one or more access types to establish the second multiple access protocol data unit session.

2. The method for processing a multiple access protocol data unit session according to claim 1, wherein: The second multiple access protocol data unit session is associated with the first multiple access protocol data unit session and has the same protocol data unit session type, session and service continuity mode, data network name, and single network slice selection assistance information as the first multiple access protocol data unit session.

3. The method for processing a multiple access protocol data unit session according to claim 2, wherein: Once the second MAC session is established, the user equipment releases the first MAC session and maintains session and service continuity.

4. The method for processing a multiple access protocol data unit session according to claim 1, wherein: The user plane resources of the first MPDU session are established in both 3GPP access type and non-3GPP access type.

5. The method for processing a multiple access protocol data unit session according to claim 4, wherein: The user equipment is registered with a single public land mobile network via both the 3GPP access type and the non-3GPP access type, wherein the determined one or more access types is the first access type, and wherein the user equipment initiates a single protocol data unit session establishment procedure via the first access type.

6. The method for processing a multiple access protocol data unit session according to claim 4, wherein: The user equipment is registered with a first public land mobile network via the first access type and is registered with a second public land mobile network via a second access type, wherein the determined one or more access types are the first access type and the second access type, and wherein the user equipment initiates a first protocol data unit session establishment procedure via the first access type and initiates a second protocol data unit session establishment procedure via the second access type.

7. The method for processing a multiple access protocol data unit session according to claim 6, wherein: Before the user equipment initiates the second protocol data unit session establishment process through the second access type, the user equipment initiates the first protocol data unit session establishment process through the first access type.

8. The method for processing a multiple access protocol data unit session according to claim 1, wherein: The user plane resources of the first multiple access protocol data unit session are established through a single access type.

9. The method for processing a multiple access protocol data unit session according to claim 8, wherein: The determined one or more access types is the single access type, and wherein the user equipment initiates a single protocol data unit session establishment procedure through the single access type.

10. The method for processing a multiple access protocol data unit session according to claim 8, wherein: The single access type is the same as or different from the first access type.

11. A user equipment for multiple access protocol data unit session processing, comprising: a protocol data unit session processing circuit configured to maintain a first multiple access protocol data unit session in a 5G system, wherein the first multiple access protocol data unit session has a first protocol data unit session identifier, and a session and service continuity mode selected by the first multiple access protocol data unit session is session and service continuity mode 3; a receiver configured to receive a protocol data unit session modification command message for the first multiple access protocol data unit session, wherein the protocol data unit session modification command message indicates a request for reactivation and is received by the user equipment via the first access type; a transmitter, configured to send a protocol data unit session modification complete message in response to the protocol data unit session modification command message; as well as control and configuration circuitry for determining one or more access types based on user equipment registration, user plane resources of the first multiple access protocol data unit session, and the first access type; The protocol data unit session processing circuit is further used to establish a second multiple access protocol data unit session with a second protocol data unit session identifier, wherein the user equipment initiates one or more protocol data unit session establishment processes respectively through the determined one or more access types to establish the second multiple access protocol data unit session.

12. The user equipment for multiple access protocol data unit session processing according to claim 11, characterized in that: The second multiple access protocol data unit session is associated with the first multiple access protocol data unit session and has the same protocol data unit session type, session and service continuity mode, data network name, and single network slice selection assistance information as the first multiple access protocol data unit session.

13. The user equipment for multiple access protocol data unit session processing according to claim 12, characterized in that: Once the second MAC session is established, the user equipment releases the first MAC session and maintains session and service continuity.

14. The user equipment for multiple access protocol data unit session processing according to claim 11, characterized in that: The user plane resources of the first MPDU session are established in both 3GPP access type and non-3GPP access type.

15. The user equipment for multiple access protocol data unit session processing according to claim 14, characterized in that: The user equipment is registered with a single public land mobile network via both the 3GPP access type and the non-3GPP access type, wherein the determined one or more access types is the first access type, and wherein the user equipment initiates a single protocol data unit session establishment procedure via the first access type.

16. The user equipment for multiple access protocol data unit session processing according to claim 14, characterized in that: The user equipment is registered with a first public land mobile network via the first access type and is registered with a second public land mobile network via a second access type, wherein the determined one or more access types are the first access type and the second access type, and wherein the user equipment initiates a first protocol data unit session establishment procedure via the first access type and initiates a second protocol data unit session establishment procedure via the second access type.

17. The user equipment for multiple access protocol data unit session processing according to claim 16, characterized in that: Before the user equipment initiates the second protocol data unit session establishment process through the second access type, the user equipment initiates the first protocol data unit session establishment process through the first access type.

18. The user equipment for multiple access protocol data unit session processing according to claim 11, characterized in that: The user plane resources of the first multiple access protocol data unit session are established through a single access type.

19. The user equipment for multiple access protocol data unit session processing according to claim 18, characterized in that: The determined one or more access types is the single access type, and wherein the user equipment initiates a single protocol data unit session establishment procedure through the single access type.

20. The user equipment for multiple access protocol data unit session processing according to claim 18, characterized in that The single access type is the same as or different from the first access type.

21. A storage medium storing a program, wherein when the program is executed, the user equipment executes the steps of the multiple access protocol data unit session processing method according to any one of claims 1 to 10.

Images