Method and equipment for enhancing session continuity of system interaction work

Abstract

The invention provides a method and equipment for enhancing session continuity of system interaction work. When the UE performs an inter-system handover from an A / Gb mode or an Iu mode to an S1 mode, the UE identifies some PDN connections that are not associated with a PDU session ID (PSI). In one novel aspect, the UE locally deactivates all EPS bearer contexts for such a PDN connection, includes an EPS bearer context state IE in a tracking area update request message for a tracking area update (TAU) procedure at the time of an inter-system handover from an A / Gb mode or Iu mode to an S1 mode, and then initiates a UE requested PDN connection procedure for such a PDN connection. Moreover, if there is no EPS bearer after local deactivation and the UE does not support EMM registration without PDN connection, the UE initiates a reattach procedure subsequent to a UE requested PDN connection procedure for that PDN connection.

Description

[0001] This application is a divisional application of the invention patent filed on February 8, 2023, with application number 202310101783.1, entitled "Method and apparatus for enhancing the session continuity of system interaction".

[0002] Cross-reference to related applications

[0003] This application claims priority to U.S. Provisional Application No. 63 / 308,178, entitled “Enhanced Handling for Session Continuity,” filed February 9, 2022, pursuant to 35 USC §119, the subject matter of which is incorporated herein by reference. Technical Field

[0004] The disclosed implementations generally relate to wireless communication, and more particularly to methods for supporting session continuity when a UE performs system interaction operations from A / Gb or Iu mode to S1 mode. Background Technology

[0005] Over the years, wireless communication networks have grown exponentially. Long-Term Evolution (LTE) systems offer high peak data rates, low latency, improved system capacity, and low operating costs due to their simpler network architecture. LTE systems, also known as 4th Generation (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, the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) comprises multiple evolved Node-Bs (eNodeBs / eNBs) that communicate with multiple mobile stations called User Equipment (UEs). 3rd Generation Partner Project (3GPP) networks typically include a hybrid of 2G / 3G / 4G systems. The Next Generation Mobile Network (NGMN) Board has decided to focus future NGMN activities on defining the end-to-end requirements for 5G New Radio (NR) systems (5GS).

[0006] In 4G Evolved Packet System (EPS), the PDN connection process is a crucial step when an LTE communication system accesses the Packet Data Network (PDN). The purpose of the PDN connection process is to establish a default EPS bearer between the UE and the PDN. In 5G, Protocol Data Unit (PDU) session establishment is a parallel process to the PDN connection process in 4G. The PDU session defines the association between the UE and the data network providing the PDU connection service. If the UE supports interactive operation and performs an intersystem change from S1 mode to A / Gb (2G) or Iu (3G, UMTS) mode, the UE uses parameters from the respective active EPS bearer contexts to enable the corresponding PDP context.

[0007] During system handover from A / Gb or Iu mode to S1 mode, for PDN connections that do not support 5GS interaction, the UE can initiate a PDN disconnection procedure and then initiate a UE-requested PDN connection procedure. However, this procedure may incur unnecessary signaling overhead, especially in cases where multiple PDN connections need to be re-established.

[0008] Seeking solutions. Summary of the Invention

[0009] A method to enhance session continuity in system interaction is proposed. During inter-system handover from A / Gb or Iu mode to S1 mode, for any transferred PDN connection, if the PDN connection is not associated with a PDU Session ID (PSI), and the UE supporting N1 mode decides to transfer the PDN connection from S1 mode to N1 mode, the UE can first initiate a UE-requested PDN disconnection procedure, and then initiate a UE-requested PDN connection procedure for such a PDN connection. In a novel aspect, the UE locally deactivates all EPS bearer contexts for such PDN connections, includes the EPS bearer context state (IE) in the Tracking Area Update (TAU) request message during inter-system handover from A / Gb or Iu mode to S1 mode, and then initiates a UE-requested PDN connection procedure for such PDN connections. Furthermore, if there is no EPS bearer after local deactivation and the UE does not support EMM-REGISTERED without PDN connection, the UE initiates a reattachment procedure for the subsequent UE-requested PDN connection procedure for such PDN connection.

[0010] In one implementation, the UE performs an inter-system handover from A / Gb or Iu mode to S1 mode in a mobile communication network, wherein the UE maintains multiple Packet Data Network (PDN) connections in S1 mode. The UE identifies one or more PDN connections that do not support 5GS interoperability. The UE locally releases the one or more PDN connections and disables the evolved packet system (EPS) bearer contexts associated with the one or more PDN connections. The UE performs a tracking area update (TAU) procedure with the network to disable all EPS bearer contexts associated with the one or more PDN connections. The UE initiates one or more UE-requested PDN connection procedures to establish PDN connections that support 5GS interoperability.

[0011] According to the method and apparatus for enhancing session continuity in system interaction provided by the present invention, the TAU procedure can be used to disable all EPS bearer contexts that do not support PDN connections for 5GS interaction, thereby reducing signaling overhead.

[0012] Other embodiments and advantages are described in the detailed description below. This invention is not intended to be limited. The invention is defined by the claims. Attached Figure Description

[0013] The accompanying drawings illustrate embodiments of the invention, wherein the same numbers denote the same components.

[0014] Figure 1 illustrates an exemplary mobile communication network and inter-system handover for multiple packet data network (PDN) connections with session continuity, according to a novel aspect.

[0015] Figure 2 illustrates a simplified block diagram of user equipment (UE) and network entities according to an embodiment of the present invention.

[0016] Figure 3 illustrates a novel first implementation of UE behavior during system handover from 2G / 3G to 4G for a PDN connection that does not support 5GS interoperability.

[0017] Figure 4 illustrates a novel second implementation of UE behavior during system handover from 2G / 3G to 4G for a PDN connection that does not support 5GS interoperability.

[0018] Figure 5 illustrates the sequential flow for PDN connection establishment, EPS bearer activation, and deactivation between the UE and PLMN1 and PLMN2 during inter-system handover with session continuity.

[0019] Figure 6 is a flowchart of a method for supporting interactive operation from 2G / 3G to 4G with session continuity for multiple PDN connections, according to a novel aspect of the present invention. Detailed Implementation

[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 illustrates an exemplary mobile communication network 100 and inter-system handover for a PDN connection with session continuity according to a novel aspect. The mobile communication network 100 includes: a user equipment (UE) 101, a base station gNB / eNB 102, an Access and Mobility Management Function (AMF), a Session Management Function (SMF), or a Mobility Management Entity (MME) 103, and a 5G / 4G core network 5GC / EPC 104. In the example of Figure 1, UE 101 and its serving base station gNB 102 are part of a Radio Access Network (RAN) 120. In the Access Stratum (AS), RAN 120 provides radio access for UE 101 via Radio Access Technology (RAT). In the Non-Access Stratum (NAS), AMF / SMF / MME 103 communicates with gNB 102 and 5GC / EPC 104 for access and mobility management of radio access devices in network 100, as well as PDU session management. UE 101 may be equipped with a single Radio Frequency (RF) transceiver, or multiple RF transceivers via different RAT / CNs for different application services. UE 101 can be a smartphone, wearable device, Internet of Things (IoT) device, tablet computer, etc.

[0022] EPS networks are packet-switched (PS) Internet Protocol (IP) networks. This means the network delivers all data traffic in IP packets and provides IP connectivity to users. When a UE joins a 5GS network, a Packet Data Network (PDN) address (i.e., an address that can be used on the PDN) is assigned to the UE to connect it to the PDN. In 4G, the PDN connection process is a crucial step in establishing a default EPS bearer between the UE and the packet data network. EPS has defined a default EPS bearer to provide IP connectivity. In 5G, the Protocol Data Unit (PDU) session establishment process is a parallel process to the PDN connection process in 4G. The PDU session defines the association between the UE and the data network providing PDU connectivity services.

[0023] If the UE supports interactive operation and performs an inter-system handover from S1 (4G) mode to A / Gb (2G) or Iu (3G, UMTS) mode, the UE uses parameters from the respective active EPS bearer contexts to enable the corresponding PDP context. During an inter-system handover from A / Gb or Iu mode to S1 mode, for PDN connections that do not support 5GS interactive operation (e.g., without PSI association), the UE can initiate a PDN disconnection procedure and then initiate a UE-requested PDN connection procedure. However, this procedure may incur unnecessary signaling overhead, especially in cases where multiple PDN connections need to be re-established.

[0024] In the example of Figure 1, UE 101 maintains multiple PDN connections in EPS, each associated with a default EPS bearer identified by an EPS bearer ID (EBI). If UE 101 loses 4G signal and only has 2G / 3G signal, UE 101 can perform an inter-system handover from S1 mode to A / Gb mode (2G) or Iu mode (3G) (141). Therefore, UE 101 can enable the 2G / 3G PDP context by using parameters from the EPS bearer context of multiple PDN connections (142). Later, UE 101 can perform an inter-system handover from A / Gb mode (2G) or Iu mode (3G) back to S1 mode (143), and the enabled PDP context is converted back to multiple PDN connections (131). If some of the PDN connections do not support working with 5GS (e.g., no PSI association), UE 101 may want to switch the PDN connections from S1 mode to N1 mode.

[0025] According to a novel aspect, UE 101 performs the following steps to transition a PDN connection from S1 mode to N1 mode (151). First, UE 101 locally disables all EPS bearer contexts of PDN connections that do not have PSI associations. Second, during inter-system handover from A / Gb mode or Iu mode to S1 mode, UE 101 includes the EPS bearer context state IE in the tracking area update request message of the TAU procedure. The EPS bearer state IE indicates which EPS bearer contexts should be disabled by the network. Third, UE 101 initiates one or more UE-requested PDN connection procedures for those PDN connections. Moreover, if no EPS bearer exists after local disabling and the UE does not support EMM registration without PDN connections, UE 101 initiates a reattach procedure, followed by one or more UE-requested PDN connection procedures for those PDN connections. As a result, UE 101 does not need to disconnect each PDN connection individually, which reduces signaling overhead. When switching between systems from S1 mode to N1 mode (161), the newly established PDN connection (132) can be transferred to the corresponding PDU session (162).

[0026] Figure 2 illustrates a simplified block diagram of a wireless device (e.g., UE 201) and a network entity 211 according to an embodiment of the present invention. The network entity 211 may be a base station and / or an AMF / SMF / MME / SGSN / RAN. The network entity 211 has an antenna 215 for transmitting and receiving radio signals. An RF transceiver module 214, coupled to the antenna, receives RF signals from the antenna 215, converts the RF signals into baseband signals, and transmits the baseband signals to a processor 213. The RF transceiver 214 also converts the baseband signals received from the processor 213, converts the baseband signals into RF signals, and transmits them to the antenna 215. The processor 213 processes the received baseband signals and invokes different functional modules to perform functions in the base station 211. The memory 212 includes volatile computer-readable storage media and non-volatile computer-readable storage media, storing program instructions and data 220 for controlling the operation of the base station 211. In the example of Figure 2, network entity 211 also includes a protocol stack 280 and a set of control function modules and circuits 290. PDU session or PDN connection or PDP context processing circuit 231 handles the establishment and modification of PDU / PDN / PDP. QoS and EPS bearer management circuit 232 creates, modifies, and deletes QoS and EPS bearers for the UE. Configuration and control circuit 233 provides various parameters to configure and control relevant UE functions, including mobility and session management, as well as PDU / PDN / PDP management.

[0027] Similarly, UE 201 has a memory 202, a processor 203, and a radio frequency (RF) transceiver module 204. The RF transceiver 204 is connected to an antenna 205, receives RF signals from the antenna 205, converts the RF signals into baseband signals, and sends the baseband signals to the processor 203. The RF transceiver 204 also converts the baseband signals received from the processor 203, converts the baseband signals into RF signals, and sends them to the antenna 205. The processor 203 processes the received baseband signals and invokes different functional modules and circuits to perform functions in UE 201. The memory 202 includes volatile computer-readable storage media and non-volatile computer-readable storage media, storing data and program instructions 210 to be executed by the processor to control the operation of UE 201. For example, suitable processors include: dedicated 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 functionality of UE 201 can be implemented and configured using software-associated processors.

[0028] UE 201 also includes a set of functional modules and control circuitry for performing the functional tasks of UE 201. Protocol stack 260 includes: a Non-Access-Stratum (NAS) layer for communicating with AMF / SMF / MME / SGSN entities connected to the 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. System modules and circuitry 270 can be implemented and configured through software, firmware, hardware, and / or combinations thereof. When executed by a processor via program instructions contained in memory, these functional modules and circuitry interact with each other to enable UE 201 to perform implementations and functional tasks and functions within the network.

[0029] In one example, system module and circuit 270 includes: PDU session, PDN connection, and PDP context processing circuitry 221 that performs the PDU session and PDN connection establishment and modification process with the network; session and mobility management circuitry 222 that manages session and mobility parameters; inter-system handover processing circuitry 223 that handles inter-system handover functions; and configuration and control circuitry 224 that handles configuration and control parameters for session and mobility management. In a novel aspect, during inter-system handover from 2G / 3G to 4G, UE 201 utilizes the TAU procedure to disable all EPS bearer contexts of PDN connections that do not support 5GS interoperability, thereby reducing signaling overhead.

[0030] Figure 3 illustrates a novel aspect of UE behavior during inter-system handover from 2G / 3G to 4G for PDN connections that do not support 5GS interoperability. In step 311, UE 301 maintains multiple PDP contexts in UMTS 303. In step 312, UE 301 performs an inter-system handover from UMTS 303 to EPS 302 (from 2G / 3G to 4G). Multiple PDP contexts are transferred to the EPS bearer of the corresponding PDN connection in the EPS (step 321). In step 331, UE 301 determines which PDN connections do not support 5GS interoperability, for example, PDN connections not associated with a PDU session ID (PSI). For example, UE 301 may find at least three PDN connections (Internet, IMS, other services, etc.) that do not support 5GS interoperability. Since UE 301 supports N1 mode, UE 301 decides to transfer those PDN connections from S1 mode to N1 mode by first releasing those PDN connections and then re-establishing PDN connections with interactive working capabilities.

[0031] Traditionally, during system handover from A / Gb or Iu mode to S1 mode, for any transferred PDN connections, if the PDN connection is not associated with a PDU session ID, the UE can first initiate a UE-requested PDN disconnection procedure, followed by a UE-requested PDN connection procedure for each PDN connection within those connections. For example, as depicted in box 340, in step 341, UE 301 initiates a first PDN disconnectivity procedure to disconnect the PDN connection for Internet services. In step 342, UE 301 initiates a second PDN disconnectivity procedure to disconnect the PDN connection for IMS services. In step 343, UE 301 initiates a third PDN disconnectivity procedure to disconnect the PDN connections for other services. After disconnecting the PDN connection, in step 343, UE 301 initiates a first UE-requested PDN connection procedure for Internet services. In step 344, UE 301 initiates a second UE-requested PDN connection procedure for IMS services. In step 345, UE 301 initiates a third UE-requested PDN connection procedure for other services. It can be seen that for each PDN connection that does not support interaction with 5GS, UE 301 needs to initiate both a PDN disconnection procedure and a PDN connection procedure.

[0032] According to a novel aspect, the UE can locally disable all EPS bearer contexts for such PDN connections, include the EPS bearer context state IE in the tracking area update request message during inter-system handover from A / Gb mode or Iu mode to S1 mode, and then initiate a UE-requested PDN connection procedure for such PDN connections. As depicted in Figure 3, in step 351, UE 301 locally disables all EPS bearer contexts for those PDN connections that do not support 5GS interoperability. In step 361, UE 301 initiates a tracking area update procedure by sending a TAU request message to EPS 302 during / after inter-system handover to S1 mode to synchronize with the EPS bearer context state of EPS 302. The TAU request message includes the EPS bearer context state IE, which contains all EBIs of the EPS bearer contexts of those PDN connections to be disconnected. After the PDN connection is disconnected (e.g., the EPS bearer context is disabled), in step 362, UE 301 initiates a first UE-requested PDN connection procedure for the Internet service. In step 363, UE 301 initiates a second UE-requested PDN connection procedure for the IMS service. In step 364, UE 301 initiates a third UE-requested PDN connection procedure for other services. It can be seen that compared to three separate PDN disconnection procedures, UE 301 only requires one Tracking Area Update Synchronization (TAU SYNC) procedure, which reduces signaling overhead.

[0033] Figure 4 illustrates a novel second implementation of UE behavior during inter-system handover from 2G / 3G to 4G for PDN connections that do not support 5GS interaction. Steps 411 to 451 in Figure 4 are similar to steps 311 to 351 in Figure 3. In the example of Figure 3, some PDN connections do not support 5GS interaction, while the remaining PDN connections do. However, in the example of Figure 4, all PDN connections do not support 5GS interaction. As a result, after step 451, UE 401 has locally disabled all EPS bearer contexts, and UE 401 determines that there are no EPS bearers (e.g., all PDN connections are released) (step 452). If the UE does not support EMM registration without PDN connections (EMM-RESIGERED), the UE needs to reattach to the EPS network to establish a first PDN connection. In step 461, UE 401 reattaches to EPS 402 to establish a first PDN connection for Internet services. In step 462, UE 401 initiates a UE-requested PDN connection procedure for IMS services. In step 463, UE 301 initiates another UE-requested PDN connection procedure for other services. It can be seen that compared to three separate PDN disconnection procedures, UE 401 only requires one reattachment procedure, and signaling overhead is reduced.

[0034] Figure 5 illustrates the sequential flow for PDN connection establishment, EPS bearer activation, and deactivation between the UE and PLMN1 and PLMN2 during inter-system handover with session continuity. In the example in Figure 5, UE 501 selects a RAT (4G) in PLMN1 that does not support 5G (step 510). In step 511, UE 501 initiates a UE-requested PDN connection procedure for Internet service, for example, by sending a PDN connection request message (APN: Internet) in PLMN1. In step 512, in response to this PDN connection procedure, UE 501 receives an ACTIVATE DEFAULT_EPS_BEARER_CONTEXT_REQUEST message (APN: Internet, EBI = 5). In step 513, UE 501 sends an ACTIVATE DEFAULT_EPS_BEARER_CONTEXT_ACCEPT message to PLMN1 to complete the PDN connection procedure for Internet services in PLMN1. Similarly, in step 521, UE 501 initiates a UE-requested PDN connection procedure for IMS services, for example, by sending a PDN connection request message (APN: IMS) to PLMN1. In step 522, in response to this PDN connection procedure, UE 501 receives an ACTIVATE DEFAULT_EPS_BEARER_CONTEXT_REQUEST message (APN: IMS, EBI = 6). In step 523, UE 501 sends an ACTIVATE_DEFAULT_EPS_BEARER CONTEXT_ACCEPT message to PLMN1 to complete the PDN connection procedure for IMS services. UE 501 can follow the same process to establish more PDN connections for other services in PLMN1.

[0035] In step 531, UE 501 reselects the RAT from 4G (PLMN1) to 2G / 3G. For inter-system handover from S1 mode to A / Gb mode or Iu mode, the UE uses parameters from each active EPS bearer context to enable the corresponding PDP context. For example, the SM uses the following parameters from each active EPS bearer context: EPS bearer identifier for mapping to NSAPI; linked EPS bearer identifier for mapping to linked TI (if available); PDP address and APN of the default EPS bearer context for mapping to the PDP address and APN of the default PDP context; TFT of the default EPS bearer context for mapping to the TFT of the default PDP context (if available); TFT of the dedicated EPS bearer context for mapping to the TFT of the secondary PDP context; and GERAN / UTRAN parameters provided by the MME during E-UTRAN access. The MME performs the mapping from EPS to R99QoS parameters.

[0036] In the example in Figure 5, PLMN2 supports 5G (540). Later, in step 541, UE 501 reselects from 2G / 3G back to 4G with 5G capability (PLMN2). During the inter-system handover to 4G, the PDP context in 2G / 3G is transferred to the EPS bearer of the PDN connection in 4G. Since some PDN connections may not support interaction with 5GS, UE 501 needs to transfer those PDN connections from S1 mode to N1 mode. In step 551, UE 501 locally disables the EPS bearer context corresponding to those PDN connections that do not support interaction with 5GS. In a novel aspect, instead of initiating a PDN disconnection procedure to individually release each PDN connection, UE 501 initiates a tracking area update procedure, for example, sending a TAU request message to the network (step 561). The TAU request message includes an EPS bearer context state IE, which indicates that all EPS bearer contexts corresponding to those PDN connections need to be deactivated (e.g., EPS bearers with EBI = 5 and EBI = 6). Then, UE501 establishes a PDN connection by sending a PDN connection request message (APN: Internet) in step 562 and a PDN connection request message (APN: IMS) in step 563.

[0037] Figure 6 is a flowchart of a method for supporting session continuity for multiple PDN connections from 2G / 3G to 4G interoperability according to a novel aspect of the present invention. In step 601, the UE performs an inter-system handover from A / Gb or Iu mode to S1 mode in the mobile communication network, wherein the UE maintains multiple PDN connections in S1 mode. In step 602, the UE identifies one or more PDN connections that do not support interoperability with 5GS. In step 603, the UE locally releases the one or more PDN connections and disables the EPS bearer context associated with the one or more PDN connections. In step 604, the UE performs a TAU procedure with the network to disable all EPS bearer contexts associated with the one or more PDN connections. In step 605, the UE initiates one or more UE-requested PDN connection procedures to establish PDN connections that support interoperability with 5GS. In one implementation, after the UE locally disables the EPS bearer context associated with the one or more PDN connections, there is no EPS bearer, and the UE initiates a reattachment procedure to establish a first PDN connection that supports 5GS interaction.

[0038] Although the invention has been described in conjunction with certain specific embodiments for guiding purposes, the invention is not limited thereto. Therefore, various modifications, adjustments, and combinations of features of the described embodiments can be made without departing from the scope of the invention as set forth in the claims.

Claims

1. A method for enhancing session continuity in system interaction, the method comprising: The user equipment (UE) performs an inter-system handover from A / Gb or Iu mode to S1 mode in the mobile communication network, wherein the UE maintains multiple packet data network (PDN) connections in S1 mode; The identifier does not support one or more PDN connections that interact with 5GS; Locally release one or more PDN connections that do not support 5GS interoperability and disable the Evolved Packet System (EPS) bearer context associated with the one or more PDN connections; Perform a Tracking Area Update (TAU) procedure with the network to disable all EPS bearer contexts associated with the PDN connections of the one or more identified entities; and Initiate one or more PDN connection procedures requested by the UE to establish a PDN connection that supports interaction with 5GS.

2. The method according to claim 1, wherein, One or more PDN connections identified do not have a PDN Session ID (PSI) associated with them.

3. The method according to claim 1, wherein, Each of the identified one or more PDN connections is associated with a corresponding EPS bearer having an EPS bearer ID EBI.

4. The method according to claim 1, wherein, The UE sends a TAU request message, which includes the EPS bearer ID EBI of all EPS bearer contexts associated with the one or more PDN connections.

5. The method according to claim 4, wherein, The UE releases the one or more PDN connections without sending a separate PDN disconnect request for each of the one or more PDN connections.

6. The method according to claim 1, wherein, After the UE locally disables the EPS bearer context associated with the one or more PDN connections, there is no EPS bearer.

7. The method according to claim 6, wherein, The UE initiates a reattachment process to establish a first PDN connection that supports interaction with 5GS.

8. The method according to claim 1, wherein, During the system handover from A / Gb mode or Iu mode to S1 mode, the UE performs the TAU procedure.

9. The method according to claim 1, wherein, After the system handover from A / Gb mode or Iu mode to S1 mode is completed, the UE executes the TAU procedure.

10. A user equipment (UE) for enhancing session continuity in system interaction, the UE comprising: Inter-system handover processing circuit, which performs inter-system handover from A / Gb or Iu mode to S1 mode in a mobile communication network, wherein the UE maintains multiple packet data network (PDN) connections in S1 mode; Configuration and control circuitry, wherein the control circuitry identifies one or more PDN connections that do not support 5GS interoperability, wherein the UE locally releases the one or more PDN connections that do not support 5GS interoperability and disables the Evolved Packet System EPS bearer context associated with the one or more PDN connections; Session and mobility management circuitry, the mobility management circuitry performing a Tracking Area Update (TAU) procedure with the network to disable all EPS bearer contexts associated with the PDN connections of the one or more identified entities; and The PDN connection processing circuit initiates one or more PDN connection procedures requested by the UE to establish a PDN connection that supports interaction with 5GS.

11. The UE according to claim 10, wherein, One or more PDN connections identified do not have a PDN Session ID (PSI) associated with them.

12. The UE according to claim 10, wherein, Each of the identified one or more PDN connections is associated with a corresponding EPS bearer having an EPS bearer ID EBI.

13. The UE according to claim 10, wherein, The UE sends a TAU request message, which includes the EPS bearer ID EBI of all EPS bearer contexts associated with the one or more PDN connections.

14. The UE according to claim 13, wherein, The UE releases the one or more PDN connections without sending a separate PDN disconnect request for each of the one or more PDN connections.

15. The UE according to claim 10, wherein, After the UE locally disables the EPS bearer context associated with the one or more PDN connections, there is no EPS bearer.

16. The UE according to claim 15, wherein, The UE initiates a reattachment process to establish a first PDN connection that supports interaction with 5GS.

17. The UE according to claim 10, wherein, During the system handover from A / Gb mode or Iu mode to S1 mode, the UE performs the TAU procedure.

18. The UE according to claim 10, wherein, After the system handover from A / Gb mode or Iu mode to S1 mode is completed, the UE executes the TAU procedure.

19. A non-volatile computer-readable storage medium storing program instructions and data that, when executed by a processor of a user equipment used to enhance session continuity of system interaction, cause the user equipment to perform operations according to any one of claims 1 to 9.

Images