Method and user equipment for wireless communication

Abstract

Methods for handling the conflict of UE requested PDU session establishment procedure and network requested PDU session modification procedure are proposed. When the PDU session establishment request message indicates that the UE requested PDU session establishment request procedure is for handover of an existing PDU session between 5G 3GPP access and 5G non-3GPP access, the UE and the NW can continue the UE requested PDU session establishment procedure and abort the NW requested PDU session modification procedure. When the PDU session establishment request message indicates that the UE requested PDU session establishment request procedure is for establishing user plane resources for a MA PDU session, the UE and the NW can continue the UE requested PDU session establishment procedure and the NW requested PDU session modification procedure. By utilizing the present application, wireless communication can be better performed.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to wireless communications, and more particularly, to a method for handling protocol data unit (PDU) session establishment procedure and PDU session modification procedure conflict. BACKGROUND

[0002] Wireless communication networks have grown exponentially over the years. Long-Term Evolution (LTE) systems can provide high peak data rates, low latency, higher system capacity, and low operating cost due to simplified network architecture. LTE systems (also referred to as 4G systems) also provide seamless integration with older wireless networks, such as Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), and Universal Mobile Telecommunications System (UMTS). In LTE systems, Evolved Universal Terrestrial Radio Access Network (E-UTRAN) includes multiple evolved Node-Bs (eNodeBs or eNBs) communicating with multiple mobile stations, referred to as User Equipment (UE). Third Generation Partnership Project (3GPP) networks typically include a mix of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) Board has decided to focus future NGMN activities on defining end-to-end requirements for the Fifth Generation (5G) New Radio (NR) system (5G System, 5GS). th

[0003] ​In 5G / NR, a PDU session can define an association between a UE and a data network that provides PDU connectivity service. The PDU session establishment is a parallel procedure to the Packet Data Network (PDN) connectivity (bearer) procedure in 4G / LTE. Each PDU session can be identified by a PDU session identity (ID) (PDU Session ID, PSI), and can include multiple Quality of Service (QoS) flows and QoS rules. Each PDU session can be established over a 5G access network (e.g., over a 3GPP Radio Access Network (RAN), or over a non-3GPP RAN). Different PDU session procedures can be initiated by the network and the UE to manage a PDU session, such as a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure.

[0004] A PDU session establishment procedure can be used to establish a new PDU session, to handover an existing PDU session, or to establish a second leg for an existing Multi-Access PDU (MAPDU) session. If there is an existing PDU session, the network can initiate a PDU session modification procedure to modify the PDU session, and the UE can initiate a PDU session establishment procedure to handover / establish a second leg of the PDU session. The handling of the above-mentioned conflict by the UE / network is not defined.

[0005] A solution is needed. SUMMARY

[0006] A method to handle the conflict of a UE requested PDU session establishment procedure and a network requested PDU session modification procedure can be proposed. If the UE receives a PDU session modification command message after sending a PDU session establishment request message to the network, and the PDU session ID (PSI) in the PDU session modification command message is the same as the PSI in the PDU session establishment request message, the conflict can be detected. When the PDU session establishment request message indicates that the UE requested PDU session establishment request procedure can be used to handover an existing PDU session between 5G 3GPP access and 5G non-3GPP access, the UE and the NW can continue the UE requested PDU session establishment procedure and abort the NW requested PDU session modification procedure. When the PDU session establishment request message indicates that the UE requested PDU session establishment request procedure can be used to establish user plane resources for a MA PDU session, the UE and the NW can continue both the UE requested PDU session establishment procedure and the NW requested PDU session modification procedure.

[0007] A method for wireless communication, comprising: transmitting, by a user equipment, a protocol data unit session setup request message to initiate a user equipment requested protocol data unit session setup procedure for a protocol data unit session; receiving a protocol data unit session modification command message for a network requested protocol data unit session modification procedure, wherein the user equipment detects a conflict between the setup procedure and the modification procedure when a protocol data unit session identity, PSI, in the received protocol data unit session modification command message is the same as a PSI in the transmitted protocol data unit session setup request message; determining that the user equipment requested protocol data unit session setup procedure is to switch the protocol data unit session between a third generation partnership project access and a non-third generation partnership project access; and the user equipment continuing the user equipment requested protocol data unit session setup procedure and aborting the network requested protocol data unit session modification procedure.

[0008] A method for wireless communication, comprising: transmitting, by a user equipment, a protocol data unit session setup request message to initiate a user equipment requested protocol data unit session setup procedure for an established multiple access protocol data unit session; receiving a protocol data unit session modification command message for a network requested protocol data unit session modification procedure, wherein the user equipment detects a conflict between the setup procedure and the modification procedure when a protocol data unit session identity, PSI, in the received protocol data unit session modification command message is the same as a PSI in the transmitted protocol data unit session setup request message; determining that the user equipment requested protocol data unit session setup procedure is to request establishment of user plane resources for the multiple access protocol data unit session; and the user equipment continuing the user equipment requested protocol data unit session setup procedure and continuing the network requested protocol data unit session modification procedure.

[0009] A method for wireless communication includes sending, by a network entity, a protocol data unit (PDU) session modification command message to a user equipment (UE) to initiate a network requested PDU session modification procedure for a PDU session, receiving a PDU session establishment request message for a UE requested PDU session establishment procedure, detecting, by the network entity, a conflict between the establishment procedure and the modification procedure when a PDU session identity (PSI) indicated in the received PDU session establishment request message is the PSI of the network requested PDU session modification, determining that the UE requested PDU session establishment procedure is for a handover of the PDU session between a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access, and continuing, by the network entity, the UE requested PDU session establishment procedure and aborting the network requested PDU session modification procedure.

[0010] By utilizing the present application, wireless communication can be better performed.

[0011] Other embodiments and advantages will be described in the following detailed description. This summary is not intended to define the application. The application is defined by the claims. BRIEF DESCRIPTION OF DRAWINGS

[0012] The accompanying drawings, which are incorporated herein to provide a further understanding of the application, illustrate embodiments of the application and together with the description

[0013] Figure 1 An exemplary 5G network supporting PDU session management and PDU session procedure conflict handling methods according to one novel aspect can be illustrated.

[0014] Figure 2 A simplified block diagram of a UE and a network entity according to embodiments of the present application can be illustrated.

[0015] Figure 3 One embodiment of PDU session establishment handling for handover when the UE also receives a PDU session modification command from the network according to one novel aspect can be illustrated.

[0016] Figure 4 Another embodiment of PDU session establishment handling for an established MA PDU session when the UE also receives a PDU session modification command from the network according to one novel aspect can be illustrated.

[0017] Figure 5 One embodiment of network behavior when the network receives a PDU session establishment request during a network requested PDU session modification procedure can be illustrated.

[0018] Figure 6is a flow chart of a method for handling PDU session procedure conflict for handover from a UE perspective according to one novel aspect of the present application.

[0019] Figure 7 is a flow chart of a method for handling PDU session procedure conflict for MA PDU from a UE perspective according to one novel aspect of the present application.

[0020] Figure 8 is a flow chart of a method for handling PDU session procedure conflict from a network (NW) perspective according to one novel aspect of the present application. DETAILED DESCRIPTION

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

[0022] Figure 1 An exemplary 5G network 100 supporting PDU session management and PDU session procedure conflict handling method according to one novel aspect can be illustrated. The 5G NR network 100 can include a UE 101, a 3GPP access 102 (e.g., 3GPP RAN), a non-3GPP access 103 (e.g., 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 can communicate with base stations 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 can mainly be responsible for interacting with a decoupled data plane, creating, updating, and removing PDU sessions, and managing session contexts with the UPF 113. The N3IWF 112 can interface with 5G core network control plane functions and be responsible for routing messages outside of the 5G RAN.

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

[0024] 5GS network can be a packet-switched (PS) Internet Protocol (IP) network. When a UE joins an Evolved Packet System (EPS) network, the UE can be allocated a PDN address (i.e., an address usable on a PDN) to connect to a PDN. In 4G, EPS can define a default EPS bearer to provide always-on IP connectivity. In 5G, a PDU session establishment procedure can be a parallel procedure to the PDN connection procedure in 4G. A PDU session can define an association between a UE and a data network that provides PDU connectivity service. Each PDU session can be identified by a PDU session ID (or PSI), and a PDU session can be established over a 3GPP RAN and / or over a non-3GPP RAN for radio access. 5G Session Management (5GSM) for PDU sessions over 3GPP access and non-3GPP access can be managed by an AMF and an SMF through NAS signaling. In 5G, a MA PDU session can use one 3GPP access network or one non-3GPP access network at a time, or can use one 3GPP access network and one non-3GPP access network at the same time.

[0025] Networks and UEs can initiate different PDU session procedures to manage PDU sessions, such as a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure. When a UE-requested PDU session establishment procedure and a network-requested PDU session modification procedure conflict, the UE / network handling of the above conflict is not defined. Further, a PDU session establishment procedure can be used for different purposes, including an initial request, an existing PDU session (handover), an initial emergency request, an existing emergency PDU session (handover), a MA PDU request, etc. The corresponding handling of a detected conflict in different scenarios can be distinguished.

[0026] According to one novel aspect, UE and network behavior when a UE-requested PDU session establishment procedure and a network-requested PDU session modification procedure (as shown in 130) collide can be proposed. If the UE 101 receives a PDU session modification command message after sending a PDU session establishment request message to the network, and the PDU session ID in the PDU session modification command message is the same as the PDU session ID in the PDU session establishment request message, a collision can be detected. In a first example, if the UE-requested PDU session establishment procedure is for switching an existing PDU session between 5G 3GPP and 5G non-3GPP access, the UE 101 can continue the UE-requested PDU session establishment procedure and abort the NW-requested PDU session modification procedure, as shown in 140. In a second example, if the UE-requested PDU session establishment procedure is for establishing user plane resources on a second access type for an existing MA PDU session that is already established on a first access type, the UE 101 can continue both the UE-requested PDU session establishment procedure and the NW-requested PDU session modification procedure, as shown in 150. In a third example, if the UE-requested PDU session establishment procedure is for switching an existing PDU session between 5G 3GPP and 5G non-3GPP access, the network can continue the UE-requested PDU session establishment procedure and abort the NW-requested PDU session modification procedure, as shown in 160.

[0027] Figure 2 A simplified block diagram of a wireless device (e.g., UE 201 and network entity 211) according to embodiments of the present application can be illustrated. The network entity 211 can be a base station and / or an AMF / SMF. The network entity 211 can have an antenna 215 to transmit and receive radio signals. An RF transceiver module 214 coupled with the antenna 215 can receive RF signals from the antenna 215, convert the RF signals to baseband signals, and send the baseband signals to the processor 213. The RF transceiver 214 can also convert baseband signals received from the processor 213, convert the baseband signals to RF signals, and send the RF signals to the antenna 215. The processor 213 can process the received baseband signals and invoke different functional modules to perform features in the base station 211. The storage medium 212 can store program instructions and data 220 to control the operation of the base station 211. In Figure 2In the example of network entity 211, network entity 211 can also include a protocol stack 280 and a set of control functions modules and circuits 290. Protocol stack 280 can include a NAS layer for communication with an AMF / SMF / MME entity connected to a core network, a Radio Resource Control (RRC) layer for upper layer configuration and control, a Packet Data Convergence Protocol / Radio Link Control (PDCP / RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. In one example, control functions modules and circuits 290 can include PDU session handling circuits 291 for handling PDU establishment, modification, and release procedures, and configuration and control circuits 292 for providing different parameters to configure and control the UE, including mobility management and PDU session management.

[0028] Similarly, UE 201 can have a storage medium 202, a processor 203, and RF transceiver modules 204. RF transceiver 204 can be coupled with an antenna 205, receive RF signals from antenna 205, convert the RF signals to baseband signals, and send the baseband signals to processor 203. RF transceiver 204 can also convert baseband signals received from processor 203, convert the baseband signals to RF signals, and send the RF signals to antenna 205. Processor 203 can process the received baseband signals and invoke different function modules and circuits to perform features in UE 201. Storage medium 202 can store data and program instructions 210 for execution by the processor to control the operation of UE 201. Suitable processors can include, for example, a general purpose processor, a Digital Signal Processor (DSP), multiple microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, and other types of integrated circuits (ICs) and / or state machines. The processor associated with software can be used to implement and configure the features of UE 201.

[0029] The UE 201 can also include a protocol stack 260 and a set of control function modules and circuitries 270. The protocol stack 260 can include a NAS layer for communication with an AMF / SMF / MME entity connected to a core network, an RRC layer for upper layer configuration and control, a PDCP / RLC layer, a MAC layer, and a PHY layer. The control function modules and circuitries 270 can be implemented and configured through software, firmware, hardware, and / or combinations of both. The control function modules and circuitries described above, when executed by the processor through program instructions contained in the storage medium, can cooperate with each other to allow the UE 201 to perform embodiments of the present application as well as functional tasks and features.

[0030] In one example, the control function modules and circuitries 270 can include a PDU session handling circuitry 271 for performing PDU session establishment, modification, and release procedures with the network, and a configuration and control circuitry 272 for handling configuration and control parameters for mobility management and session management. Upon detecting a conflict between a UE-requested PDU session establishment procedure and a network-requested PDU session modification procedure, the UE and the network can decide whether to continue the UE-requested PDU session establishment procedure and abort the NW-requested PDU session modification procedure, or continue both procedures, according to a request type of the PDU session establishment request.

[0031] Figure 3 An embodiment of PDU session establishment handling when the UE also receives a PDU session modification command from the network according to one novel aspect can be illustrated. At step 311, the UE 301 can establish and / or maintain one or more PDU sessions. For example, one of the one or more PDU sessions, a PDU session with PSI = 5, can be established between the UE 301 and the 5GS network over a 3GPP access type (or over a non-3GPP access type). At step 321, the UE 301 can decide to handover the existing PDU session with PSI = 5 from a 3GPP access to a non-3GPP access (or from a non-3GPP access to a 3GPP access). Then at step 322, the UE 301 can trigger a UE-requested PDU session establishment procedure by sending an UL NAS TRANSPORT message, which can contain a PDU session establishment request message for the PDU session (PSI = 5) with a request type set to “existing PDU session” or “existing emergency PDU session”.

[0032] In step 323, after the UE-requested PDU session establishment procedure is triggered, but before the UE-requested PDU session establishment procedure is completed, the UE 301 can receive a DL NAS transport message, which can contain a PDU session modification command message for the same PDU session (PSI = 5). Accordingly, the UE 301 can detect a conflict between the UE-requested PDU session establishment procedure and the network-requested PDU session modification procedure. The conflict can be detected when the UE 301 receives the PDU session modification command message after sending the PDU session establishment request message to the network, and the PDU session ID in the PDU session modification command message is the same as the PDU session ID in the PDU session establishment request message (PSI = 5).

[0033] Then, the UE 301 can determine the handling corresponding to the detected conflict. In the above scenario, the UE 301 can intend to switch an existing PDU session from one access type to another access type, and can send the PDU session establishment request message with the request type set to “existing PDU session” or “existing emergency PDU session” to switch the existing PDU session (e.g., PSI = 5) between 3GPP access and non-3GPP access. Accordingly, the UE 301 can continue the UE-requested PDU session establishment procedure and abort the NW-requested PDU session modification procedure. In step 331, the UE can abort the NW-requested PDU session modification procedure, e.g., the UE 301 can not send a 5GSM message (such as PDU session modification complete or PDU session modification command reject) to respond to the network. In step 341, the UE 301 can continue the UE-requested PDU session establishment procedure to switch the PDU session (PSI = 5), e.g., wait to receive a PDU session establishment accept message from the network.

[0034] Figure 4Another embodiment of performing PDU session establishment for a MA PDU session when the UE also receives a PDU session modification command from the network can be exemplified according to one novel aspect. In step 411, the UE 401 can establish and / or maintain one or more PDU sessions. For example, one of the one or more PDU sessions has a PSI of 5, and the PDU session can be a MA PDU session established between the UE 401 and the 5GS network over a 3GPP access type (or over a non-3GPP access type). In step 421, the UE 401 can decide to establish user plane resources for the existing MA PDU session with PSI = 5 over other non-3GPP access (or over other 3GPP access). Then in step 422, the UE 401 can trigger a UE-requested PDU session establishment procedure by sending a UL NAS transport message, which can contain a PDU session establishment request message for the PDU session (PSI = 5), and the request type can be set to “MA PDU request”.

[0035] In step 423, after triggering the UE-requested PDU session establishment procedure, but before the UE-requested PDU session establishment procedure is completed, the UE 401 can receive a DL NAS transport message, which can contain a PDU session modification command message for the same PDU session (PSI = 5). Accordingly, the UE 401 can detect a conflict between the UE-requested PDU session establishment procedure and the network-requested PDU session modification procedure. The conflict can be detected when the UE 401 receives the PDU session modification command message after sending the PDU session establishment request message to the network, and the PDU session ID in the PDU session modification command message is the same as the PDU session ID in the PDU session establishment request message (PSI = 5).

[0036] Then, the UE 401 can determine the handling corresponding to the detected conflict. In the above scenario, the UE 401 can intend to establish user plane resources for the existing PDU session through the other access type, and can send a PDU session establishment request message with the request type set to “MA PDU Request”. Accordingly, the UE 401 can continue the UE-requested PDU session establishment procedure and can also continue the NW-requested PDU session modification procedure. In step 431, the UE can continue the NW-requested PDU session modification procedure for the PDU session (PSI=5), e.g., the UE 401 can send a PDU session modification complete or PDU session modification command reject message to the network. In step 441, the UE 401 can continue the UE-requested PDU session establishment procedure to establish user plane resources for the PDU session (PSI=5), e.g., the UE 401 can wait to receive a PDU session establishment accept message from the network.

[0037] Figure 5 One embodiment of network behavior when the network receives a PDU session establishment request during a network-requested PDU session modification procedure can be exemplified. In step 511, the UE 501 can establish and / or maintain one or more PDU sessions. For example, one of the one or more PDU sessions, a PDU session with PSI=5, can be established between the UE 501 and the 5GS network through a 3GPP access type (or through a non-3GPP access type). In step 521, the UE 501 can decide to handover the existing PDU session PSI=5 from a 3GPP access to a non-3GPP access (or from a non-3GPP access to a 3GPP access). Then in step 522, the UE 501 can trigger a UE-requested PDU session establishment procedure by sending an UL NAS transport message, which can contain a PDU session establishment request message for the PDU session (PSI=5) with the request type set to “existing PDU session” or “existing emergency PDU session” for handover purpose.

[0038] In step 523, the network can send a DL NAS transport message, which can contain a PDU session modification command message for the same PDU session (PSI=5), and the network can also start timer T3591. Meanwhile, the UE requested PDU session establishment procedure can be triggered, but the UE requested PDU session establishment procedure has not been completed. Accordingly, the network can detect the conflict between the UE requested PDU session establishment procedure and the network requested PDU session modification procedure. The conflict can be detected when the network receives the PDU session establishment request message after sending the PDU session modification command message to the UE, and the PDU session ID in the PDU session modification command message is the same as the PDU session ID in the PDU session establishment request message (PSI=5).

[0039] Then, the network can determine the handling corresponding to the detected conflict. In the above scenario, the network can know that the UE 501 intends to switch the existing PDU session from one access type to another access type, and can send a PDU session establishment request message with the request type set to “existing PDU session” or “existing emergency PDU session” to switch the existing PDU session (e.g., PSI=5) between 3GPP access and non-3GPP access. Therefore, the network can continue the UE requested PDU session establishment procedure and abort the NW requested PDU session modification procedure. In step 531, the network can abort the NW requested PDU session modification procedure, for example, can stop timer T3591 and not send a 5GSM message (such as PDU session establishment accept or PDU session establishment reject) to respond to the UE. In step 541, the network can continue the UE requested PDU session establishment procedure to switch the PDU session (PSI=5) to the other access type, for example, can send a PDU session establishment accept message to the UE 501.

[0040] Figure 6is a flowchart of a method for handling PDU session procedure conflict for handover from a UE perspective according to a novel aspect of the present application. In step 601, the UE can send a PDU session establishment request message in the 5GS to initiate a UE requested PDU session establishment procedure for a PDU session. In step 602, the UE can receive a PDU session modification command message for a network requested PDU session modification procedure. When the PDU session ID (PSI) in the received PDU session modification command message is the same as the PSI in the sent PDU session establishment request message, the UE can detect a conflict between the establishment procedure and the modification procedure. In step 603, the UE can determine that the UE requested PDU session establishment procedure is available for handover of the PDU session between 3GPP and non-3GPP. In step 604, the UE can continue the UE requested PDU session establishment procedure and abort the network requested PDU session modification procedure.

[0041] Figure 7 is a flowchart of a method for handling PDU session procedure conflict for a MAPDU from a UE perspective according to a novel aspect of the present application. In step 701, the UE can send a PDU session establishment request message in the 5GS to initiate a UE requested PDU session establishment procedure for an established MAPDU session. In step 702, the UE can receive a PDU session modification command message for a network requested PDU session modification procedure. When the PDU session ID (PSI) in the received PDU session modification command message is the same as the PSI in the sent PDU session establishment request message, the UE can detect a conflict between the establishment procedure and the modification procedure. In step 703, the UE can determine that the UE requested PDU session establishment procedure is available for requesting establishment of user plane resources for the MAPDU session. In step 704, the UE can continue the UE requested PDU session establishment procedure and can continue the network requested PDU session modification procedure.

[0042] Figure 8is a flowchart of a method for handling PDU session procedure conflict for handover from a NW perspective according to a novel aspect of the present application. In step 801, a network entity can send a PDU session modification command message to a UE in a 5GS to initiate a NW requested PDU session modification procedure for a PDU session. In step 802, the network entity can receive a PDU session establishment request message for a UE requested PDU session establishment procedure, wherein the network entity can detect a conflict between the establishment procedure and the modification procedure when a PDU session ID (PSI) in the received PDU session establishment request message is the PSI of the network requested modified PDU session. In step 803, the network entity can determine that the UE requested PDU session establishment procedure can be used for a PDU session handover between 3GPP access and non-3GPP access. In step 804, the network entity can proceed with the UE requested PDU session establishment procedure and abort the network requested PDU session modification procedure.

[0043] It is understood by those skilled in the art that although embodiments of the present application can be described with 5GS as an example, the present application is not limited to the 5G network environment. For example, the spirit and technical solutions of the present application can also be applicable to future sixth generation (6G) networks and / or any other suitable network environment. th

[0044] The present application is disclosed above in conjunction with specific embodiments for the purpose of guidance, but the present application is not limited thereto. Accordingly, various modifications, adjustments and combinations of various features of the above-described embodiments can be made without departing from the scope set forth in the claims of the present application.​

Claims

1. A method for wireless communication, comprising: The user equipment sends a protocol data unit session establishment request message to initiate a protocol data unit session establishment process requested by the user equipment for the protocol data unit session; receiving a protocol data unit session modification command message for a protocol data unit session modification process requested by a network, wherein when a protocol data unit session identifier (PSI) in the received protocol data unit session modification command message is the same as the PSI in the sent protocol data unit session establishment request message, the user equipment detects a conflict between the establishment process and the modification process; determining that the protocol data unit session establishment procedure requested by the user equipment is for handing over the protocol data unit session between a 3GPP access and a non-3GPP access; and The user equipment continues the protocol data unit session establishment process requested by the user equipment and terminates the protocol data unit session modification process requested by the network.

2. The method for wireless communication according to claim 1, wherein The protocol data unit session establishment request message carries a request type, and the request type is set to "existing protocol data unit session".

3. The method for wireless communication according to claim 1, wherein The protocol data unit session establishment request message carries a request type, and the request type is set to "existing emergency protocol data unit session".

4. The method for wireless communication according to claim 1, wherein The conflict is detected when the user equipment receives the protocol data unit session modification command message before receiving a protocol data unit session setup accept message from the network.

5. The method for wireless communication according to claim 1, wherein: The user equipment continues the protocol data unit session establishment process requested by the user equipment and waits for a fifth generation session management response message from the network.

6. The method for wireless communication according to claim 1, wherein: The user equipment terminates the protocol data unit session modification process requested by the network and does not send a fifth generation session management response message to the network.

7. A method for wireless communication, comprising: The user equipment sends a protocol data unit session establishment request message to initiate a protocol data unit session establishment process requested by the user equipment for the established multi-access protocol data unit session; receiving a protocol data unit session modification command message for a protocol data unit session modification process requested by a network, wherein when a protocol data unit session identifier (PSI) in the received protocol data unit session modification command message is the same as the PSI in the sent protocol data unit session establishment request message, the user equipment detects a conflict between the establishment process and the modification process; determining that the protocol data unit session establishment process requested by the user equipment is for requesting establishment of user plane resources for the multiple access protocol data unit session; and The user equipment continues the protocol data unit session establishment process requested by the user equipment, and continues the protocol data unit session modification process requested by the network.

8. The method for wireless communication according to claim 7, wherein: The protocol data unit session establishment request message carries a request type, and the request type is set to "multiple access protocol data unit request".

9. The method for wireless communication according to claim 8, wherein: The protocol data unit session establishment request process requested by the user equipment is used to request establishment of user plane resources for the multiple access protocol data unit session on a second access, wherein the multiple access protocol data unit session is established on a first access.

10. The method for wireless communication according to claim 7, wherein: The conflict is detected when the user equipment receives the protocol data unit session modification command message before receiving a protocol data unit session setup accept message from the network.

11. The method for wireless communication according to claim 7, wherein: The user equipment continues the protocol data unit session establishment process requested by the user equipment and waits for a fifth generation session management response message from the network.

12. The method for wireless communication according to claim 7, wherein: The user equipment continues the protocol data unit session modification process requested by the network and sends a fifth generation session management response message to the network.

13. A method for wireless communication, comprising: The network entity sends a protocol data unit session modification command message to the user equipment to initiate a network-requested protocol data unit session modification process for the protocol data unit session; receiving a protocol data unit session establishment request message for a protocol data unit session establishment process requested by a user equipment, wherein when a protocol data unit session identifier (PSI) indicated in the received protocol data unit session establishment request message is a PSI of the protocol data unit session that the network requests to modify, the network entity detects a conflict between the establishment process and the modification process; determining that the protocol data unit session establishment process requested by the user equipment is used to switch the protocol data unit session between a 3GPP access and a non-3GPP access; and The network entity continues the protocol data unit session establishment process requested by the user equipment and terminates the protocol data unit session modification process requested by the network.

14. The method for wireless communication according to claim 13, wherein: The protocol data unit session establishment request message carries a request type, and the request type is set to "existing protocol data unit session".

15. The method for wireless communication according to claim 13, wherein: The protocol data unit session establishment request message carries a request type, and the request type is set to "existing emergency protocol data unit session".

16. The method for wireless communication according to claim 13, wherein: The conflict is detected when the network entity receives the protocol data unit session establishment request message before receiving a protocol data unit session modification complete message from the user equipment.

17. The method for wireless communication according to claim 13, wherein: The network entity continues the protocol data unit session establishment process requested by the user equipment and sends a response message to the user equipment.

18. The method for wireless communication according to claim 13, wherein: The network entity terminates the network-requested protocol data unit session modification process and stops the T3591 timer.

19. A user equipment for wireless communication, comprising: A processor, wherein when executing program instructions stored in a storage medium, the processor performs the steps of the method for wireless communication according to any one of claims 1 to 12.

20. A network entity for wireless communication, comprising: A processor, wherein when executing program instructions stored in a storage medium, the processor performs the steps of the method for wireless communication according to any one of claims 13 to 18.

21. A storage medium storing program instructions, wherein when the program instructions are executed by a processor, the processor is caused to perform the steps of the method for wireless communication according to any one of claims 1 to 12.

22. A storage medium storing program instructions, wherein when the program instructions are executed by a processor, the processor is caused to perform the steps of the method for wireless communication according to any one of claims 13 to 18.

Images